 Therefore some processes remains after stop terminate the running script.

Cleanup seems to be failing after syncing this change:
I get the following output:
Cleaning up...

Options:
 <pid> [...]            send signal to every <pid> listed
 -<signal>, -s, --signal <signal>
                        specify the <signal> to be sent
 -l, --list=[<signal>]  list all signal names, or convert one to a name
 -L, --table            list all signal names in a nice table

 -h, --help     display this help and exit
 -V, --version  output version information and exit

For more details see kill(1).

Note that ./hack/local-up-cluster is broken right now (https://github.com/GoogleCloudPlatform/kubernetes/pull/7101#issuecomment-101816043), so you can easily reproduce this on head.
@nak3 : Can you please take a look?

It looks like ps --pid=PID --pid=PID doesn't work depending on the environment. I will fix them ASAP.

Just ran into this and created #8227

I sent pull/8234


bug: Unable to set the navigation back programatically in ionic 5 (no transition animation)

Hi,
Below Api's were in ionic 3. can I use it in ionic 5 . Please find the screenshot. Below screenshot is showing the below api's are available in ionic 5.

this.navCtrl.navigateForward('/route');
this.navCtrl.navigateBack('/route');
Below api working fine forward transition but not working for backward transition.
this.router.navigateByUrl('/tabs/tab1');
Please suggest us how to do "back" transition without nav controller api in ionic 5.

Thanks for the issue.

Hi,
Thanks for your reply.
I don't want do any custom navigation. I just want to use this below mentioned ionic api to forward/back animations through programatically.
this.router.navigateByUrl('/tabs/tab1');
By using above mentioned API, could you please help me to navigate forward/back animations through programatically with consistent animations.

Thanks for the follow up. The navigateBack method for NavController still exists in Ionic 4/5 and does use the "backwards" navigation transition.
navigateByUrl on Router does not have any options for animations because that is a method within Angular and not within Ionic.
If you want to control the direction of the transition you will need to use the Ionic-supplied methods. Does this answer your question?

Hi,
Thanks for your reply.
We thought like this NavController API is deprecated in IONIC4/5.
There is no document is available for NavController API in IONIC4/5. Could you please update the documentation and it will be helpful for everybody. Going forward will use the same.

The NavController is not deprecated in Ionic 4+. It looks like the documentation is missing and that there is already an open issue: https://github.com/ionic-team/ionic-docs/issues/506.
I am going to close this issue in favor of the one I linked to. Thanks!

Thanks.


Remove win2016 jvm github action test.

It's constantly failing on PR with network errors.  After the removal we still have win-latest.  Suggestions are welcomed.

Thanks! Using the latest Windows looks reasonable to me.


Promote kueue apis to V1

What would you like to be added:
Promote the core Kueue APIs to V1.
Why is this needed:
We would need to use Kueue in more of our products. Many customers would like a stable API to build on top of.
We would like to start the discussion for what it would take to promote the v1beta1(2) APIs to v1 and stablize the API.
Completion requirements:
This enhancement requires the following artifacts:

[ ] Design doc
[ ] API change
[ ] Docs update

The artifacts should be linked in subsequent comments.

It is not clear to me if https://github.com/kubernetes-sigs/kueue/issues/768 must be satisfied before we promote to V1 or not.

Actually, we use in Kueue both alpha and beta.
I'm wondering if we could migrate to v1 only a subset of API which we consider already stable (like Workload, LQ, CQ and so on), while keeping the other still in alpha or beta (like Topology or MultiKueue, or other new features).
This would give us more flexibility and serial that we promote APIs which aren't battle tested yet. In any case new features to Kueue will start in Alpha.
WDYT @kannon92 @tenzen-y ?

It is not clear to me if https://github.com/kubernetes-sigs/kueue/issues/768 must be satisfied before we promote to V1 or not.

This is whitelist for v1beta2, so yes, this should happen before  v1

This would give us more flexibility and serial that we promote APIs which aren't battle tested yet. In any case new features to Kueue will start in Alpha.

I don't think we need features to start in alpha API fields. Unless we are introducing a new API field entirely. One can always add a new field to v1 or v1beta API.

This is whitelist for v1beta2, so yes, this should happen before v1

My concern is not there isn't really a hard and fast rule on this one so I worry that it will stay as a wishlist with this API in beta while we add more items to it.

When I was talking about new features I was thinking that the API objects, like recently introduced Topology or Cohort, should go via API. For extending existing objects, sure we have no choice than extend them.
As for the whitelist, I'm with you, I would like to promote the APIs, but the list is long and so think it will be safer and with less friction if we move via interim step of v1beta2 than directly to v1.

As I commented in https://github.com/kubernetes-sigs/kueue/issues/3192#issuecomment-2396510965, I would like to wait any API graduation (even v1beta2) for the graduation of the TAS and HirarchyCohort since both are still alpha stage and potentially plan API change.

I'm wondering if we could migrate to v1 only a subset of API which we consider already stable (like Workload, LQ, CQ and so on), while keeping the other still in alpha or beta (like Topology or MultiKueue, or other new features).

@tenzen-y is there room to do something like this?
I would really like to see some kind of stabilization of the API for at least the core resources.


How to clear the cache manually

In our use case, there are occasions where we have very large objects and the cache is close to full.
I think the behavior I am seeing in this case is the object failing to get put into the cache successfully.

Bazel-remote manages the disk usage itself, as long as clients aren't requesting a blob, it will eventually reach the top of the LRU index and be removed. You should not need to manually clear the cache directory, if you do then that would be considered a bug (but if you really want to do this, the only way is to stop bazel-remote, and restart it once you have finished removing cache files).
Is there a specific problem you're seeing?

We are seeing this issue as well. Log shows lots of error messages like
GRPC BYTESTREAM WRITE FAILED: uploads/ac41810c-982d-4f02-aa19-3153f94eb3f2/compressed-blobs/zstd/d16c7416a6d6d6da53c93ee45726403c1c7d291ba942e24aac19967d09e47a73/148 Cache Put failed: Failed to write compressed CAS blob to disk: write /data/cas.v2/d1/d16c7416a6d6d6da53c93ee45726403c1c7d291ba942e24aac19967d09e47a73-148-481930764: no space left on device

@apipe: it looks like you have run out of disk space: no space left on device. You should either try to free up some disk space outside of bazel-remote's data directory, or restart bazel-remote with a lower --max_size value.

Closing this issue, I think I answered everyone here.
In summary: don't try to delete cache items from disk while bazel-remote is running, and ensure that you have enough disk space allocated and a suitable --max_size / BAZEL_REMOTE_MAX_SIZE setting.


update syn 2.0

Thanks very much! Left one review comment regarding literal validation in derive_serde

clap, tokio-serde, console-subscriber, all of them upgrade to new version, since they use syn 1.0, which cause the ci error.
After upgrading new version, the ci is ok now.

https://github.com/carllerche/tokio-serde/pull/31
I found this pr， but it does not be merged.

@tikue
Everything is ok now

Thank you!


Consider hiding deletion events in CVN channels

There are sometimes many deletion log actions by an admin, that is not a bot. Maybe it is scripted, or maybe there is just a lot to delete.
(From #countervandalism earlier today)

loftyabyss: bots could possibly handle repeated actions better... bswiki has had deletions for hours, so -sw can't be used for much else in the meantime...

loftyabyss: Krinkle: deleter wasn't a bot, but was clearly running some kind of script, but I thought maybe the cvn bots could ignore repeated actions, or perhaps ignore those on the whitelist, I tried adding them but they still appeared in the channel

Current state:

CVNBot hides all actions by users on its bot list by default.
CVNBot hides all actions made with a "flood" or "bot" flag by default.
CVNBot supports showing block actions, delete actions and other log actions by admins.
For each type of action (edit, new page, new account, delete page, protect page, block user, etc.) it is possible to decide when to show it:

1= Show always.
2= Hide for trusted users (local admins, local bots, global whitelist), but show the rest.
3= Hide always.

For log actions like "delete page" the different ways to show it does not make much difference since the only kind of user with the ability to delete pages (generally) are admins. So if we want to hide them for trusted users, that is almost the same as hiding always.
So the questions are:

Is it sometimes useful for CVNBot to report page deletions?
Is it useful in #cvn-sw?
Is it useful in other channels?

The bot is configured for each channel separately, so we can change this one at a time. There is no need for all channels to agree :)

Moved to https://phabricator.wikimedia.org/T327137.


Update Stylis in PostCSS benchmark

Hi. I was n able to update preprocessors and prefixers benchamarks in postcss/benchmark because of the ck of the docs.
Can you help me with it to promote your awesome parser?

Yes, i think it's missing the serialize to string step: The compile function itself only returns the AST.
import {serialize, compile, stringify} from 'stylis'

var ast = compile(`h1{all:unset}`)

import {serialize, compile, stringify} from 'stylis'

var string = serialize(compile(`h1{all:unset}`), stringify)

and prefixing is done as follows:
import {serialize, compile, prefixer, stringify} from 'stylis'

var string = serialize(compile(`h1{all:unset}`), middleware([prefixer, stringify]))

Thanks. Fixed.

That was fast(pun intended).


read functional syntax

I like to provide test ontologies in OWL functional syntax. For this we need to include horned-functional. @jdr0887 I can't remember—was there a problem including this in the build?

Horned-functional only supports horned-owl up to version 0.11.  The latest horned-owl is version 0.14 & it is the version we are using.


Broken Link on Core team participation page

Pertinent section of the Wagtail docs

Core Participation Team
Details

Under the 'Core team onboarding' title, where it says 'Add to Github Team ', but the link is broken.

Thanks for the report @jmgutu! This section of the wiki is directed towards existing members of the core team, and I can confirm that the link does work for members with the relevant permissions, so no action needs to be taken here.

Thanks @gasman  Well noted!


Publishing to maven central

Since we're using jbwa as a dependency for gatk4, we'd like to make jbwa available through maven central at some point in the not to distant future.  We currently published a version on our own artifactory repository to enable us to use it during development, but we can't rely on that when we make releases to maven central.
Would you be willing to publish it to central?  We could offer help but there would be some work you'd have to do to get accounts set up.
Alternatively, we could publish it ourselves under whatever name you prefer (com.github.lindenb:jbwa being one possible option), or we could fork the repo and publish our fork under our own name.  (org.broadinstitute:jbwa)
Would any of these options work for you?

Would you be willing to publish it to central?

@lbergelson yes, I don't have any problem with that.
Your favorite choice will be mine (as long as I'm credited somewhere :-) [ ego.. ego.. ] ). Things will go faster for the gatk team if you  manage the whole transition to maven.
Just in case, I'll add you as a collaborator in jbwa if it can help.
P

Thanks for the response.  I think the best thing to do would be for me to set it up so that it can be published under you're name.  We definitely want you credited!  What package name do you prefer?  com.github.lindeb would be one option, but if you have a personal domain you'd rather use we can do that instead.

com.github.lindeb would be one option

"com.github.lindenb" is ok :-)     lindenb not lindeb please :-) )

Ack!   Sorry about that typo.  I'll be sure to get it right on maven :)

I've created an issue on the OSS sonatype jira for them to create a new project for publishing jbwa.  Feel free to create an account and comment on the ticket so you can be given ownership of the project. ( https://issues.sonatype.org/browse/OSSRH-23336. )  Once they approve it then we can upload artifacts.

Closing because this is completed.


Implemented weavertest multiprocess deployer.

Before this PR, weaver multi and weavertest shared the same babysitter. Both weaver multi and weavertest deployed applications across multiple processes, so it made sense not to duplicate the code.
However, while we weren't duplicating code, we were also muddying the abstractions of the babysitter, as everything had to work for both weaver multi and weavertest. A good example of this is how we dealt with pipes. For a multiprocess weavertest, the main component runs in the same process as the babysitter. The babysitter doesn't expect this, so weavertest created its own EnvelopeConn and used a babysitter as an EnvelopeHandler. This worked but it wasn't easy to understand why. It really broke the abstraction of the babysitter.
This PR implements a new weavertest multiprocess deployer. The deployer does duplicate some code from the old babysitter, but much of the babysitter's implementation wasn't needed (e.g., code for handling metrics, routing, tracing). The new weavertest deployer has a number of improvements:

Cleaner handling of pipes. Now, the deployer is very much aware that the main component is running in the same process. I also reworked the Bootstrap API to avoid a particularly nasty garbage collection bug we were facing with pipes.
Better teardown. The weaver multi babysitter doesn't expect to get shut down, but a weavertest deployer does. The new deployer is more careful about killing all subprocesses and stopping all goroutines when a unit test ends.
We're in the process of cleaning up the deployer API. As I was implementing some of these changes, I realized they made it very hard to share code between weaver multi and weavertest. This was again because the abstractions were being tortured to work across the two.
Enables future testing innovations. We've been toying with the idea of implementing more sophisticated testing. For example, we may randomly fail a component. Now that weavertest has its own deployer, these changes will be much easier to make.

@spetrovic77 I'm fixing some bugs I found.


avg_slippage_pct should be used for taker orders

It looks like original code had
https://github.com/DeviaVir/zenbot/issues/1109#issuecomment-357411767
but later this changed
https://github.com/DeviaVir/zenbot/pull/1378
@DeviaVir , @glennfu , @krystophv  can you guys review my fix. I feel this can be important.

I'm wondering if both taker and maker don't have to deal with slippage to some extent? I'd guess a taker more than a maker so your PR makes sense.

Taker orders are "market" orders. They should not have slippage at all, unless you have a very large bulky order that causes the price to drop. Makers however are more affected by slippage, since they start at a certain point and with high volatility can get a lot of slippage.
https://www.investopedia.com/terms/s/slippage.asp


:globe_with_meridians: Add malagasy language

I'd like to add my natal language in this module. As I use this libs in almost all of my projects.

No Problem. Glad to know that you love this date picker.
I will update the package in a minute. Thank you for your contribution😄

Hi @chrys-elrak
New version 1.4.5 is available 🎉


Fix Codename Engine description

i noticed the codename description didnt really describe the engine correctly lol

Looks good to me, had trouble trying to describe it exactly so a description from the author is perfect.
I'd add a "Famous for" but it hasn't been used for any important mods yet

Looks good to me, had trouble trying to describe it exactly so a description from the author is perfect.
I'd add a "Famous for" but it hasn't been used for any important mods yet

Cam might remove the "Famous for" as he did that for Forever and Psych.
Well, not remove, but might request for it not the be added I guess.


mongomock map_reduce shows "KeyError: 'value'" (works fine in pymongo)

I'm creating my fake_collection as follows. Then I want to map the primary_key with 'duration'. I want to calculate the median of all 'duration' values so I can not use reduce function (since it can not calculate median). This test fails at the map_reduce call because the mapped_list does not contain 'values' key. This error only occurs when I'm using my fake mongomock database. This error does not occur when I provide my real mongoDB client.
from unittest import TestCase
import mongomock
from aggregateCtaStatuses import AggregateCtaStatuses
from bson.code import Code

 def test_mongomock_map_reduce(self):
    # Arrange
    fake_etap = mongomock.MongoClient().db
    fake_statuses_collection = fake_etap.create_collection('statuses')
    fake_config_id = "this_is_config_id"
    test_name = "this_is_test_name"
    fake_statuses_objects = [
        {
            "testID": test_name,
            "kind": "Test",
            "duration": 8392,
            "configID": fake_config_id
        },
        {
            "testID": test_name,
            "kind": "Test",
            "duration": 8393,
            "configID": fake_config_id
        },
        {
            "testID": test_name,
            "kind": "Test",
            "duration": 8394,
            "configID": fake_config_id
        }
    ]
    fake_statuses_collection.insert_many(fake_statuses_objects)

    map_function = Code("function(){emit(this._id, this.duration);}")
    reduce_function = Code("function() {}")
    search_query = {'configID': fake_config_id, 'kind': 'Test', 'testID': test_name}

    # Act
    result = fake_etap.statuses.map_reduce(map_function, reduce_function, "my_collection", query=search_query)

    # Assert
    self.assertEqual(result.__len__(), 3)

Same problem here. My map_reduce code works fine in pymongo, but my tests break because of mongomock.

Same problem here.

same probem here. Don't work.

@singh2005 seems the travis skip the map_reduce tests
I added your example and it seems to have been fixed in master
pytest tests/test__mongomock.py::CollectionMapReduceTest
======================================================================================= test session starts =======================================================================================
platform darwin -- Python 3.5.2, pytest-3.0.5, py-1.4.31, pluggy-0.4.0
rootdir:/mongomock, inifile:
plugins: cov-2.4.0, celery-4.0.2
collected 10 items

tests/test__mongomock.py ..........

==================================================================================== 10 passed in 1.63 seconds ====================================================================================


Incorrect Hessian of vector 2-norm using jax.numpy.linalg.norm

Merry Christmas! I was a previous autograd user and new to jax. I run into this issue when I tried to compute the Hessian of a vector 2-norm using jax.numpy.linalg.norm.
Let f(x)=||x||^2, then we know the Hessian should be 2I, where I is the identity matrix.
Here is the repro:
import jax.numpy as jnp
from jax import grad, hessian
from jax.numpy import linalg

f = lambda x: linalg.norm(x)**2
a = jnp.array([1.,2.,3.])
hessian(f)(a)

The output is not correct.
DeviceArray([[ 2.0000000e+00, -2.9802322e-08,  2.9802322e-08],
             [-2.9802322e-08,  2.0000000e+00,  5.9604645e-08],
             [-4.4703484e-08, -8.9406967e-08,  2.0000000e+00]],            dtype=float32)

However, if I rewrite the 2-norm in the following way, then I could get the expected output:
g = lambda x: jnp.sum(x**2)
hessian(g)(a)

DeviceArray([[2., 0., 0.],
             [0., 2., 0.],
             [0., 0., 2.]], dtype=float32)

I also tried autograd, which works perfectly with autograd.numpy.linalg.norm.
import autograd.numpy as np
from autograd import grad, jacobian
from autograd.numpy import linalg

f = lambda x: linalg.norm(x)**2
a = np.array([1.,2.,3.])
hessian = jacobian(grad(f))
hessian(a)

array([[2., 0., 0.],
       [0., 2., 0.],
       [0., 0., 2.]])

Thank you!

Hello - your first attempt is computing the correct result up to floating point accuracy: by default JAX works in 32-bit floating point precision; a good rule-of-thumb is that in float32 precision, values of a few times 10^-8 are effectively zero.
If you want to instead compute in 64-bit precision, you can set the enable_x64 flag; see https://jax.readthedocs.io/en/latest/notebooks/Common_Gotchas_in_JAX.html#Double-(64bit)-precision

@jakevdp Thanks!


bizarre NTI warning "Cannot access property foo_ of non-object type bottom"

Compiling with new type inference (NTI) get a strange warning which does not make sense:
src/lab/view/DisplayPath.js:264: WARNING - Cannot access property myImage_ of non-object
type bottom.
  if (this.redraw_ && this.myImage_ != null) {
                      ^

The this is the DisplayPath class, and there is nothing named bottom here that I'm aware of.  Here is the code for the constructor and the method in question.  The warning happens about 2/3 thru the draw method.
/**
* @constructor
* @struct
* @implements {myphysicslab.lab.view.DisplayObject}
*/
myphysicslab.lab.view.DisplayPath = function() {
  /**
  * @type {?HTMLCanvasElement}
  * @private
  */
  this.myImage_ = null;
  /**
  * @type {!Array.<!myphysicslab.lab.model.PhysicsPath>}
  * @private
  */
  this.paths_ = new Array(0);
  /**  tells when need to redraw the bitmap from the paths
  * @type {boolean}
  * @private
  */
  this.redraw_ = true;
  /**
  * @type {!myphysicslab.lab.view.ScreenRect}
  * @private
  */
  this.screenRect_ = ScreenRect.EMPTY_RECT;
  /** to detect when redraw needed;  when the coordmap changes, we need to redraw.
  * @type {?myphysicslab.lab.view.CoordMap}
  * @private
  */
  this.lastMap_ = null;
  /**
  * @type {boolean}
  * @private
  */
  this.debug_ = false;
  /**
  * @type {boolean}
  * @private
  */
  this.dragable_ = false;
  /**  a CSS3 color value
  * @type {string}
  * @private
  */
  this.color_ = DisplayPath.color;
  /**  line thickness in pixels
  * @type {number}
  * @private
  */
  this.thickness_ = DisplayPath.thickness;
};

/** @inheritDoc */
DisplayPath.prototype.draw = function(context, map) {
  var r = this.screenRect_;
  if (r.isEmpty()) {
    // don't bother if the screen isn't visible yet
    return;
  }
  goog.asserts.assert( r.getX() == 0);
  goog.asserts.assert( r.getY() == 0);
  context.save();
  if (this.lastMap_ == null || this.lastMap_ != map) {
    this.lastMap_ = map;
    if (goog.DEBUG && this.debug_)
      window.console.log("DisplayPath: redraw because coordmap changed");
    this.redraw_ = true;
  }
  // compare size of image to that of the screen rect; reallocate if different
  if (this.myImage_ != null)  {
    if (this.myImage_.width != r.getWidth() || this.myImage_.height != r.getHeight())  {
      this.flush();
    }
  }

  if (this.myImage_ == null)  {
    // For now, bitmaps are always size of the simulation area.
    // In future we could make them any desired size, though the 'screen sized'
    // would be a special mode, because we don't know the size until
    // the draw() happens (since applets are zero sized when created).
    this.myImage_ = /** @type {!HTMLCanvasElement} */(document.createElement('canvas'));
    this.myImage_.width = r.getWidth();
    this.myImage_.height = r.getHeight();
    this.redraw_ = true;
    if (goog.DEBUG && this.debug_)
      window.console.log("DisplayPath: redraw because image reallocated");
  }
  if (this.redraw_ && this.myImage_ != null) {
    // draw the paths into the bitmap
    var ctx = /** @type {!CanvasRenderingContext2D} */(this.myImage_.getContext('2d'));
    // Clear image with transparent alpha by drawing a rectangle
    // "clearRect fills with transparent black"
    ctx.clearRect(0, 0, r.getWidth(), r.getHeight());
    ctx.strokeStyle = this.color_;
    ctx.lineWidth = this.thickness_;
    // draw the paths
    goog.array.forEach(this.paths_, function(path) {
        this.path_draw(path, ctx, map);
      }, this);
    this.redraw_ = false;
  }
  context.drawImage(this.myImage_, 0, 0, r.getWidth(), r.getHeight());
  context.restore();
};

Here is the interface for the draw method
/** Draws this {DisplayObject} using the given coordinate mapping.
@method
@param {!CanvasRenderingContext2D} context the canvas's context to draw this object into
@param {!myphysicslab.lab.view.CoordMap} map the mapping to use for translating between
simulation and screen coordinates
*/
DisplayObject.prototype.draw;

The bottom is a type that comes from NTI. If something has type bottom, it basically means that it can't have any type. For example, if NTI finds that x must have type number and type string at the same time, the type of x goes to bottom because the constraints are impossible to satisfy.
I need to know what is the type of this right before the IF to debug this. Can you add the following line
var /** number */ n = this;

right before
if (this.redraw_ && this.myImage_ != null) {

You will get a warning with the new line. Tell me what the warning says.

Here are all the errors I'm getting on that file after adding the line you suggested:
src/lab/view/DisplayPath.js:264: WARNING - The right side in the assignment is not a
subtype of the left side.
left side  : number
right side : myphysicslab.lab.view.DisplayPath{lastMap_:myphysicslab.lab.view.CoordMap,
myImage_:HTMLCanvasElement{height:number, width:number}, redraw_:boolean}

  var /** number */ n = this;
                        ^

src/lab/view/DisplayPath.js:265: WARNING - Cannot access property myImage_ of non-object
type bottom.
  if (this.redraw_ && this.myImage_ != null) {
                      ^

src/lab/view/DisplayPath.js:275: WARNING - dangerous use of the global this object
        this.path_draw(path, ctx, map);
        ^

Alright, I reproduced it. For some reason I can't reproduce it in the debugger. Maybe it's a regression after the debugger was last updated. Code snippet:
/** @constructor */
function Foo() {}
/** @constructor */
function Bar() {
  /** @type {?Foo} */
  this.obj = null;
}
Bar.prototype.f = function() {
  if (this.obj == null) {
    this.obj = new Foo;
  }
  if (this.obj != null) {}
};

I have a fix pending for this. The error was uncovered by a condition that is always true in your code. Specifically, this.myImage_ is guaranteed to be non-null (and non-undefined) where the NTI bug is happening, so you can simplify your IF test if you want.

confirmed fixed in Version: v20150505-85-ga1488d5.  Also confirmed that I can change the if statement to be just
  if (this.redraw_) {


Bonnie prior ruby travis 2.3.7

Pull requests into Bonnie Bundler require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[x] This pull request describes why these changes were made.
[x] This PR is into the correct branch.
[x] JIRA ticket for this PR: https://jira.mitre.org/browse/BONNIE-1772 https://jira.mitre.org/browse/BONNIE-1780
[x] JIRA ticket links to this PR
[x] Code diff has been done and been reviewed (it does not contain: additional white space, not applicable code changes, debug statements, etc.)
[x] Tests are included and test edge cases
[x] Tests have been run locally and pass (remember to update Gemfile when applicable)

Reviewer 1:
Name:

[x] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[x] The tests appropriately test the new code, including edge cases
[x] You have tried to break the code

Closing due to 2.3.8 release


Feature to assign a particular file name to appear first in a directory listing

In NodeJS, a file named index.js in a directory can very often have special meaning.
But if you have a directory with a many files (or even just a few), the index.js can be buried in the middle of that list in the Explorer view because files in a directory are sorted alphabetically.
It would be useful to be able to configure a file name like index.js to appear at the top of a directory, that way index.js would be at the top and then the remaining files would be sorted alphabetically.

This feature request will not be considered in the next 6-12 months roadmap and as such will be closed to keep the number of issues we have to maintain actionable. Thanks for understanding and happy coding!


when i run flutter create app in the flutter console.bat it gives an error

Steps to Reproduce

...
...
...

Logs

@osunkoyadavid Please follow the guidelines while creating an issue report.
Can you provide your flutter doctor -v and specify please what kind of error (logs)? Currently it's not possible to help without that kind of information.

Sorry, thank you but I'm now running Flutter Apps, don't bother
On Tue, 3 Sep 2019 at 18:11, Stanislav Bondarenko<EMAIL_ADDRESS>wrote:

Closed #39704 https://github.com/flutter/flutter/issues/39704.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/39704?email_source=notifications&email_token=AM2YJJ4PKPTQ46I75FFQA2DQH2LEDA5CNFSM4ITAMQFKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOTM5SH6Y#event-2604344315,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM2YJJ4W5VZNPFAN4XP6BH3QH2LEDANCNFSM4ITAMQFA
.


Update WMS/WMTS/WCS default URLs ?

Consider updating URLs to reference local GeoServer installations by default? (<IP_ADDRESS>:8080/geoserver/)

No we don't need to update those.  They are correct for the target MFOCS hardware.  The container IP is set by the build.


FR: Open periodic notes regardless of whether a new note is needing to be created.

Current behavior: Periodic notes are only opened and pinned if a new note was created.
Feature Request: An option to open and pin a note regardless of whether it was needed to be created by the plugin or not. Maybe make it toggle-able per note type.
Awesome plugin, definitely did not know I needed this until now. Kudos!

Thanks! This is definitely something that should be added, I'm also going to add a companion feature that closes any open and existing pins if you want, which means you'd only be left with the latest period's note open and pinned.


Confused timeout in pipelinerun

At the beginning, I define timeout in pipelinerun and expect the pipeline will end after a certain time and release the resource, but it's not.
After pipelinerun mark it as timeout, the task still keep running for a while.
Now I know the pipelinerun will share the timeout with tasks, that's means in a linear scenario, if the task is render by pipelinerun it will keep running no matter its owner pipelinerun is timeout.
That's means the really max duration for a pipelinerun is timeout x 2.
I still have no idea if it's a correct behavior, but at least we need mark it in the document.
Another solution is set timeout of child task as start-time + timeout - now, but it will make user confuse if he/she is not read the document.

So, is the issue here we do not cancel the taskruns when we cancel a pipelinerun? And so the taskruns keep running until they complete?

@dibyom
Right, it's current behavior.


allow to enable debug logging from an environment variable

It'd be great if we could enable debug logging of LWA using an environment variable such as AWS_LWA_LOG_VERBOSITY.
Context: I recently investigated a possible bug of a system using LWA, and building a binary for my own and bundling it to a docker image was a bit too troublesome just to enable debug logging.
i.e. change log level here depending on an envvar.
https://github.com/awslabs/aws-lambda-web-adapter/blob/c5f55e7a02b94b6af3200754dad7c238275131bd/src/main.rs#L10-L12
p.s. the possible bug was actually not caused by LWA, but http header log in debug verbosity helped a lot to find the root cause 😄

@tmokmss this is already supported: just use RUST_LOG to figure the log level.

TIL about that! I confirmed ENV RUST_LOG=debug in Dockerfile worked, thanks. @bnusunny


initial place_details work

I wasn't 100% sure how we wanted to handle the place_details.
Leveraging what we have for the spec for place_id and what we use for geocode, I wrote a few methods.
place_details({:place_id, place_id})
place_details("place_id:" <> place_id)
place_details(place_id)
I am not sure if this is the best way to go about it, but I wanted to get the documentation in a good spot.
I also fixed one of my tests, and we have another test that keeps changing it's value that we will have to address.
Thanks!

This looks good. Would you mind updating the README with the new function?

Of course! I totally forgot about that.
On Fri, Dec 15, 2017, 5:37 PM Sơn Trần-Nguyễn<EMAIL_ADDRESS>wrote:

This looks good. Would you mind updating the README with the new function?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sntran/ex_maps/pull/8#issuecomment-352129381, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AF9FI_89BlCqL4jisQgSBIm6YJ1OtkVGks5tAvSpgaJpZM4RD-Df
.

👍  Thank you!

Of course 👍


In Markdown language, list of fenced code block does not have syntax highlighting

From @EFanZh on June 2, 2018 7:23

VSCode Version: 1.23.1
OS Version: Windows 10 64-bit

Steps to Reproduce:

Create a new text document;
Change the document’s language to Markdown;
Copy the following text into the document:```python
def f():
    pass
```

1. ```python
   def f():
       pass
   ```

You should notice that the second code block doesn’t get syntax highlighting.

Does this issue occur when all extensions are disabled?: Yes
Related: #22185
Copied from original issue: Microsoft/vscode#50993

From @jcphua on June 19, 2018 5:30
Have observed the same issue, however I believe the issue relates more generally to the incorrect closure of styles for the first code block, which affects styling of all subsequent content that appears below it:
# Correctly styled Heading 1

Correct lorem ipsum

## Correctly styled Heading 2

Correct lorem ipsum

՝՝՝
hello world
՝՝՝

Incorrect lorem ipsum

## Incorrectly styled Heading 2

Incorrect lorem ipsum

(backtick characters above have been substituted with unicode equivalents for demo purposes)
Latest Insider edition currently still afflicted:

Confirmation that issue still remains with all extensions disabled.

Version: 1.25.0-insider
Commit: 7dc9539a421c9c33e57e2ce0b718f183bb44c756
Date: 2018-06-15T05:17:41.405Z
Electron: 2.0.2
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64


ACRA crash reports do not work again in 2.8.2

Summary:
When the app crashes, there should be an option to "send feedback" so that users can send their stack trace to us along with comments about what they were doing at the time of the crash.
We already have ACRA for this purpose which used to work, but stopped working again at some point.
If anyone takes this up, please ensure that the logs are sent to the PRIVATE google group, not the public one, due to privacy concerns.
Steps to reproduce:
Trigger a crash on 2.8.2. Not sure how far back this problem goes.
Add System logs:
Device and Android version:
8.0 Samsung Galaxy s7
Commons app version:
2.8.2 Play Store version
Would you like to work on the issue?
Pref not

Hello,
I'm a bit rusty to java and would like to take a look at this issue.

@Bambam905 thanks for showing interest. Am already working on a fix for this issue. :)

I was unable to fix ACRA crash reporting but have made an attempt to migrate to the latest version and use a custom log sender in #1916. Anyone feel free to take up this task. It would be great if someone is able to reuse the changes made in #1916 as using a custom log sender will give us much more control on the crash reports.

I will try to fix it i am a little bit busy but i can find some free time to put into this.

It's yours, thanks @A-Hassan-M . :)

sorry guys i have some problems with my laptop and i can't even run the project :''''D so anyone is free to take it.

I'll pick this up.

Is there a branch this is working on @misaochan so I can compare behavior?

Update: still working on this


Application fail without logs

Hi,
I've made a small app using this (great) tool, and I get a strange bug.
If I build the app and start the executable (go build && ./client-macos), there's a prompt that open, with all the log in, and the real app (with nice macos UI). Application work well and logs are also stored in log file.

Troubles start when I start using macpack (go build && macpack build). App doesn't start and I get no logs in my logfile. I don't understand why.
Is there a special tricks to have logs? Many thanks!
GO-ENV
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/thomasp/Golang"
GORACE=""
GOROOT="/usr/local/opt/go/libexec"
GOTOOLDIR="/usr/local/opt/go/libexec/pkg/tool/darwin_amd64"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/2n/1p_pny6x2p180gcj7kkbwz0c0000gn/T/go-build479332264=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
![Uploading Capture d’écran 2017-02-28 à 21.26.59.png…]()

what command do you try to start the ?

Can you copy/paste the macpack output and how you try to launch the app?

Here's the mac.json file content:
{
  "name": "Updemia",
  "id": "updemia.client",
  "version": "1.0",
  "build-number": 1,
  "icon": "logo2.png",
  "dev-region": "en",
  "deployment-target": "10.12",
  "copyright": "Copyright © 2017 scullwm. All rights reserved",
  "role": "None",
  "category": "",
  "sandbox": true,
  "capabilities": {
    "network": {
      "in": false,
      "out": true
    },
    "hardware": {
      "camera": false,
      "microphone": false,
      "usb": false,
      "printing": false,
      "bluetooth": false
    },
    "app-data": {
      "contacts": false,
      "location": false,
      "calendar": false
    },
    "file-access": {
      "user-selected": "/Users/thomasp/updemia/",
      "downloads": "",
      "pictures": "",
      "music": "",
      "movies": ""
    }
  },
  "store": false,
  "sign-id": "",
  "supported-files": []
}

I think that it can be a folder access restriction that block app from launch...
Note that the application is currently using github.com/howeyc/fsnotify to check events that happen in the folder /Users/thomasp/updemia/. This folder is so declared in the file-access.user-selected node.

the app is running in sandbox box mode right now, which allow to access only restricted area.
try by setting  "sandbox": true,  in your mac.json.

Hey @ScullWM,
Was you able to fix that?

close this one, reopen if needed.


[v1] feat(content-item-horizontal): add shadow parts

Related Ticket(s)
Jira ticket
Description
Adds shadow parts to the <dds-content-item-horizontal> family of components in order to allow for slight design adjustments in AEM.
Changelog
New

Added shadow parts for <dds-content-item-horizontal> family of components.

Thanks @emyarod . Do you have the powers to pass Percy? The issues look unrelated to adding part attributes here 😕 .

@m4olivei done!


getComputedStyle fails with shadow dom

I'm trying to use focus-trap in a StencilJS component and the various checks that rely on getComputedStyle fail when it hits a shadow root.
Pretty sure this could be fixed with a simple check, I'll take a crack at a PR. Thanks!
7vfqzmxv.entry.js:formatted:2 Uncaught TypeError: Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element'.
    at p.hasDisplayNone (7vfqzmxv.entry.js:formatted:2)
    at p.hasDisplayNone (7vfqzmxv.entry.js:formatted:2)
    at p.hasDisplayNone (7vfqzmxv.entry.js:formatted:2)
    at p.hasDisplayNone (7vfqzmxv.entry.js:formatted:2)
    at p.isUntouchable (7vfqzmxv.entry.js:formatted:2)
    at l (7vfqzmxv.entry.js:formatted:2)
    at s (7vfqzmxv.entry.js:formatted:2)
    at i (7vfqzmxv.entry.js:formatted:2)
    at w (7vfqzmxv.entry.js:formatted:2)
    at Object.activate (7vfqzmxv.entry.js:formatted:2)

Sure, @snaptopixel. Open to seeing what a PR to fix it would be 👍

Thanks @davidtheclark I went with a simpler version, so I'll close this


how does your dataset in adaptec3 : n_edges_710 generated?

So how do I generate the macro netlist as you generate n_edges_710.dat?

Hi! did you solve the problem? I have the same problem.

I have the same problem,did you solve it?


Implement ln

I'm working on this!

I'd like to work on this if you aren't currently.

Sure! You can work on it.

Thanks!


Can't scan for hardware wallets

Sparrow isn't able to scan for hardware wallets. If the 'scan'-button is hit Sparrow shows 'scanning' and nothing else happens.
Problem is the same with BitBox02 and Ledger Nano S, both hardware wallets work fine with their native software.
Due to a successful test on another Laptop it seems to be a problem of the specific combination of Sparrow wallet and my (self build) computer.
All softwares are up to date (I run on Windows 10 home), I tested with and without USB-cable. The settings of my pc and the tested laptop (also W10 home) are identical (defender/system security...), no problems in device-manager.
In the Sparrow Wallet telegram channel someone instructed me to delete hwi folder -> no change.
Then I was supposed to run 'hwi-xxx enumerate' on command line in hwi folder but the cursor only jumps in the next row and stays there blinking.
He said that that's the problem, something on my system appears to be hanging when queried. I disconnected all USB-peripherals except keyboard and mouse, deleted hwi folder again and gave it another try -> same as before.
Something seems to prevent hwi from scanning for USB devices...

Thanks for this, but as our testing determined, it's actually a problem with HWI, the utility Sparrow uses to communicate with connected USB devices. So I can't help with this directly - it needs to reported to the HWI project.
I suggest the following:

Download the latest HWI release (which Sparrow uses, but just to be sure): https://github.com/bitcoin-core/HWI/releases/tag/2.1.1 (see hwi-2.1.1-windows-amd64.zip)
Extract the .zip and attempt to run the extracted hwi.exe on the command line
If the same behaviour occurs, report it at https://github.com/bitcoin-core/HWI/issues

Oh yes, that's exactly what you told me on telegram. But unfortunately I didn't read it proper and thought you meant an issue on Sparrow, sorry for that!
It shows the same behaviour, I will report it to HWI-issue then...

To bring this to an end:
I was told to check if anything is listening on ports 2222, 21324, 11044 or 9999.
And realy, I found out that port 9999 was listed several times with "aakore.exe" wich is a process from Acronics True Image. After uninstalling this program sparrow finaly found my BitBox02!


[DO NOT MERGE YET] Rename cosigned chart to policy-controller chart

Signed-off-by: hectorj2f<EMAIL_ADDRESS>
Description of the change
I am creating a draft PR to rename cosigned helm chart to policy-controller chart.
IMPORTANT: PR Blocked until we release a new version of sigstore/cosign.

Checklist

[x] Chart version bumped in Chart.yaml according to semver. Where applicable, update and bump the versions in any associated umbrella chart
[x] Variables are documented in the values.yaml and added to the README.md. THe helm-docs utility can be used to generate the necessary content. Use helm-doc --dry-run to preview the content
[ ] JSON Schema generated
[ ] List tests pass for Chart using the Chart Testing tool and the ct lint command

@vaikas i will update this PR asap.


OSX 10.11.4 Crash

siad repeatedly crashes while 'syncing', tried deleting and reinstalling it still seems to happen.
attached said crash dump, if you want any more detail you can find me on siatalk slack with same username.
sia-crash-log.txt

can you run the bolt test suite and see if it fails?

Travelling at the moment but I will try to do it in the next day or so
Ian
Sent from my iPhone
On 13 Jun 2016, at 02:49, Luke Champine <notifications<EMAIL_ADDRESS>wrote:
can you run the bolthttps://github.com/NebulousLabs/bolt test suite and see if it fails?

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/NebulousLabs/Sia/issues/1237#issuecomment-225467623, or mute the threadhttps://github.com/notifications/unsubscribe/AHGiWLEUd-JY1mCfiTXGI-C2h0BaM5Jyks5qLJsSgaJpZM4Iz27d.

this is the bolt-test log
bolt-test.txt

From the forum:

I am getting the following error when starting the siad daemon (v0.6.0) on Debian.
From what I can tell it cannot fully load the blockchain, therefore I cannot use the wallet, host etc.

Below are the first messages I get when executing ./siad -M gc

Loading...
(1/2) Loading gateway...
(2/2) Loading consensus...
Finished loading in 0.442046251 seconds
unexpected fault address 0x77697040
fatal error: fault
[signal 0xb code=0x1 addr=0x77697040 pc=0x82f8bf6]

After that, I get a lot of goroutine messages until it exits the program.

Here are the first four goroutines:

goroutine 26 [running]:
runtime.throw(0x860c088, 0x5)
/usr/local/go/src/runtime/panic.go:530 +0x7f fp=0x18da916c sp=0x18da9160
runtime.sigpanic()
/usr/local/go/src/runtime/sigpanic_unix.go:27 +0x27c fp=0x18da9198 sp=0x18da916c
github.com/NebulousLabs/bolt.(*Tx).rollback(0x19006a80)
/home/luke/go/src/github.com/NebulousLabs/bolt/tx.go:245 +0x66 fp=0x18da91b8 sp=0x18da9198
github.com/NebulousLabs/bolt.(*Tx).Commit(0x19006a80, 0x0, 0x0)
/home/luke/go/src/github.com/NebulousLabs/bolt/tx.go:163 +0x1f2 fp=0x18da9274 sp=0x18da91b8
github.com/NebulousLabs/bolt.(*DB).Update(0x18c7d8c0, 0x18da92cc, 0x0, 0x0)
/home/luke/go/src/github.com/NebulousLabs/bolt/db.go:580 +0xf4 fp=0x18da92a0 sp=0x18da9274
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).addBlockToTree(0x18c6f080, 0x0, 0xe80e0000, 0x177d340d, 0xcbb749aa, 0x475fa958, 0xe93e48cf, 0x57d54dac, 0xd5733133, 0x3d0a09c8, ...)
/home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/accept.go:183 +0xde fp=0x18da9328 sp=0x18da92a0
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).managedAcceptBlock(0x18c6f080, 0x0, 0xe80e0000, 0x177d340d, 0xcbb749aa, 0x475fa958, 0xe93e48cf, 0x57d54dac, 0xd5733133, 0x3d0a09c8, ...)
/home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/accept.go:259 +0x108 fp=0x18da9408 sp=0x18da9328
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).threadedReceiveBlocks(0x18c6f080, 0xb769d2a8, 0x18c53508, 0x0, 0x0)
/home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/synchronize.go:215 +0x72e fp=0x18da9d98 sp=0x18da9408
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).(github.com/NebulousLabs/Sia/modules/consensus.threadedReceiveBlocks)-fm(0xb769d2a8, 0x18c53508, 0x0, 0x0)
/home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/consensusset.go:146 +0x3c fp=0x18da9db0 sp=0x18da9d98
github.com/NebulousLabs/Sia/modules/gateway.(*Gateway).RPC(0x18d22600, 0x865d8f0, 0x11, 0x863ba70, 0xa, 0x18c534f8, 0x0, 0x0)
/home/luke/go/src/github.com/NebulousLabs/Sia/modules/gateway/rpc.go:53 +0x3d5 fp=0x18da9e58 sp=0x18da9db0
github.com/NebulousLabs/Sia/modules/consensus.(*ConsensusSet).threadedInitialBlockchainDownload(0x18c6f080)
/home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/synchronize.go:479 +0x580 fp=0x18da9fa0 sp=0x18da9e58
github.com/NebulousLabs/Sia/modules/consensus.New.func1(0x18c6f080, 0xb7665970, 0x18d22600)
/home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/consensusset.go:138 +0x25 fp=0x18da9fb8 sp=0x18da9fa0
runtime.goexit()
/usr/local/go/src/runtime/asm_386.s:1585 +0x1 fp=0x18da9fbc sp=0x18da9fb8
created by github.com/NebulousLabs/Sia/modules/consensus.New
/home/luke/go/src/github.com/NebulousLabs/Sia/modules/consensus/consensusset.go:152 +0x617

goroutine 1 [IO wait]:
net.runtime_pollWait(0xb7666898, 0x72, 0x0)
/usr/local/go/src/runtime/netpoll.go:160 +0x55
net.(*pollDesc).Wait(0x18ec8db8, 0x72, 0x0, 0x0)
/usr/local/go/src/net/fd_poll_runtime.go:73 +0x35
net.(*pollDesc).WaitRead(0x18ec8db8, 0x0, 0x0)
/usr/local/go/src/net/fd_poll_runtime.go:78 +0x33
net.(*netFD).accept(0x18ec8d80, 0x0, 0xb7666bd0, 0x18c10280)
/usr/local/go/src/net/fd_unix.go:426 +0x20b
net.(*TCPListener).AcceptTCP(0x18c53348, 0x1, 0x0, 0x0)
/usr/local/go/src/net/tcpsock_posix.go:254 +0x47
net.(*TCPListener).Accept(0x18c53348, 0x0, 0x0, 0x0, 0x0)
/usr/local/go/src/net/tcpsock_posix.go:264 +0x39
net/http.(*Server).Serve(0x18d2ef00, 0xb7665ab8, 0x18c53348, 0x0, 0x0)
/usr/local/go/src/net/http/server.go:2117 +0x100
github.com/NebulousLabs/Sia/api.(*Server).Serve(0x18d2c850, 0x0, 0x0)
/home/luke/go/src/github.com/NebulousLabs/Sia/api/server.go:91 +0x1ed
main.startDaemon(0x8652f00, 0xe, 0x86057a0, 0x5, 0x86057a8, 0x5, 0xbfeec9f6, 0x2, 0x0, 0x863bd40, ...)
/home/luke/go/src/github.com/NebulousLabs/Sia/siad/daemon.go:181 +0x1e59
main.startDaemonCmd(0x18c98300, 0x18ca3500, 0x0, 0x2)
/home/luke/go/src/github.com/NebulousLabs/Sia/siad/daemon.go:204 +0x1bd
github.com/spf13/cobra.(*Command).execute(0x18c98300, 0x18c58088, 0x2, 0x3, 0x0, 0x0)
/home/luke/go/src/github.com/spf13/cobra/command.go:565 +0x678
github.com/spf13/cobra.(*Command).ExecuteC(0x18c98300, 0x18c98300, 0x0, 0x0)
/home/luke/go/src/github.com/spf13/cobra/command.go:651 +0x43b
github.com/spf13/cobra.(*Command).Execute(0x18c98300, 0x0, 0x0)
/home/luke/go/src/github.com/spf13/cobra/command.go:610 +0x2b
main.main()
/home/luke/go/src/github.com/NebulousLabs/Sia/siad/main.go:172 +0x762

goroutine 18 [syscall]:
os/signal.signal_recv(0x0)
/usr/local/go/src/runtime/sigqueue.go:116 +0x11e
os/signal.loop()
/usr/local/go/src/os/signal/signal_unix.go:22 +0x1a
created by os/signal.init.1
/usr/local/go/src/os/signal/signal_unix.go:28 +0x36

goroutine 19 [sleep]:
time.Sleep(0xf8475800, 0xd)
/usr/local/go/src/runtime/time.go:59 +0xe6
github.com/NebulousLabs/Sia/sync.(*RWMutex).threadedDeadlockFinder(0x18d225c0)
/home/luke/go/src/github.com/NebulousLabs/Sia/sync/lock.go:78 +0x468
created by github.com/NebulousLabs/Sia/sync.New
/home/luke/go/src/github.com/NebulousLabs/Sia/sync/lock.go:47 +0xb0

I am getting similar errors, siad is therefore stuck at block 41674 and cannot sync any further. I attached the console output below. Just to add a few more data points:

I am using an i686 Debian 8.5 (3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17) i686 GNU/Linux)
The Sia release is 1.0, but I received a similar error (at I think the same block) with v0.6

./siad
Loading...
(1/7) Loading gateway...
(2/7) Loading consensus...
(3/7) Loading transaction pool...
(4/7) Loading wallet...
(5/7) Loading miner...
(6/7) Loading host...
(7/7) Loading renter...

We no longer support 386 platforms. Our blockchain database is mmap'd, which seems to be a problem on 32-bit systems when the database grows larger than the 32-bit address space.

But OSX is 64bit - has been longer than windows?
Mac’s are intel core i7 64bit
So where is the 32bit?
Also Go is supposed to be platform independent
Are you saying that Sia no longer runs on OSX?
On 1 Jul 2016, at 13:24, Luke Champine <notifications<EMAIL_ADDRESS>wrote:
We no longer support 386 platforms. Our blockchain database is mmap'd, which seems to be a problem on 32-bit systems when the database grows larger than the 32-bit address space.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/NebulousLabs/Sia/issues/1237#issuecomment-229933485, or mute the threadhttps://github.com/notifications/unsubscribe/AHGiWFvBvHIxgMlA5CrlRGTOZAgxPzfuks5qRQblgaJpZM4Iz27d.

sorry, I was only looking at @tophensen's comment.

Can you confirm that you are still having issues syncing with the latest 1.0 darwin release? I noticed the occurrence of /usr/local/go/src/runtime/asm_386.s, which points to a 32-bit binary.

Only got a chance to start 1.0 today.
I’ve suspend/resumed the mac while its syncing and its synced with no issues so far :))
So it looks like this build it working well.
On 1 Jul 2016, at 13:51, Luke Champine <notifications<EMAIL_ADDRESS>wrote:
sorry, I was only looking at @tophensenhttps://github.com/tophensen's comment.

Can you confirm that you are still having issues syncing with the latest 1.0 darwin release? I noticed the occurrence of /usr/local/go/src/runtime/asm_386.s, which points to a 32-bit binary.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/NebulousLabs/Sia/issues/1237#issuecomment-229938559, or mute the threadhttps://github.com/notifications/unsubscribe/AHGiWAomurC5eIq-g1SOELH2aBtr_AgAks5qRQ09gaJpZM4Iz27d.


[Bug]: Unable to read data written from Log Store to File Store, when more than 1 parallel

What happened?

When I open the parallelism to 3, I cannot trigger the check point and write the data to the file store of the target table.
But when I change it back to 1, the job works fine.
Affects Versions
0.4.x
What engines are you seeing the problem on?
No response
How to reproduce
1.Construct the following flink sql and set the number of parallelism to 3
2.Start the flink job
Relevant log output
No response
Anything else
SQL as follows
CREATE CATALOG arctic_test WITH (
'type' = 'arctic',
'metastore.url' = 'thrift://xxxx:xxxxx/arctic_test'
);
CREATE TABLE source_table(
time TIMESTAMP(3),
WATERMARK FOR time AS time
) LIKE arctic_test.arctic_test.arctic_test;
INSERT INTO arctic_test.arctic_test.arctic_test/*+ OPTIONS('arctic.emit.mode' = 'auto', 'arctic.emit.auto-write-to-logstore.watermark-gap' = '5s', 'metrics.event-latency.enabled' = 'true', 'metrics.enabled' = 'true') /
SELECT
xxxxxxx
FROM source_table/+ OPTIONS('properties.group.id' = 'xxxxxx', 'scan.startup.mode' = 'timestamp', 'scan.startup.timestamp-millis' = '1684643919991', 'log-store.enabled' = 'true', 'log-store.consistency-guarantee.enabled' = 'true', 'properties.bootstrap.servers' = 'xxxxxxx', 'format' = 'json', 'topic' = 'xxxxxxx', 'properties.key.serializer' = 'org.apache.kafka.common.serialization.ByteArraySerializer', 'properties.value.serializer' = 'org.apache.kafka.common.serialization.ByteArraySerializer', 'properties.key.deserializer' = 'org.apache.kafka.common.serialization.ByteArrayDeserializer', 'properties.value.deserializer' = 'org.apache.kafka.common.serialization.ByteArrayDeserializer', 'arctic.read.mode' = 'log') */
Code of Conduct

[X] I agree to follow this project's Code of Conduct

What is the partition number of the logstore topic of this table:arctic_test.arctic_test.arctic_test @shendanfengg

A table with primary key and no partition

And topic's partition is 1

The bug limits the concurrency setting of user tasks, so I have classified it as critical.

Flink 1.14 has resolved this case by it:
when the source's parallelism exceeds your logstore topic partitions number, some tasks will show completion because it doesn't have the data, which would abort a checkpoint.
And also, I checked the below codes, and it's runnable in the flink-1.14:

create catalog arctic with (
    'type'='arctic',
    'metastore.url'='thrift://...'
    );
create table datagen(
    s_w_id int
) with (
    'connector'='datagen'
, 'rows-per-second'='1'
);
insert into arctic.flink_test.logs/*+ OPTIONS('log-store.catch-up'='true') */ select * from datagen;

create table printSink(
    s_w_id int
) with (
    'connector'='print'
);

insert into printSink select * from arctic.flink_test.logs/*+ OPTIONS('arctic.read.mode'='log','log-store.consistency-guarantee.enabled' = 'true') */;

So I will suggest:

Change the flink1.12 source parallelism to less than or equal to the topic's partitions number.
Upgrade to the flink1.14 version or a lager version.

@shendanfengg Another method to avoid this scenario:
Add auto-discover new topic partitions policy to LogStore Source. 'scan.topic-partition-discovery.interval'='1000'.
For example:
select * from arctic.flink_test.local_logstore
/*+ OPTIONS(
 'arctic.read.mode'='log',
 'scan.topic-partition-discovery.interval'='1000',
 'scan.startup.mode'='earliest') */


DateTimePicker Update

I am using the DateTimePicker control allowing both user entry directly into the control, and an "injected" value based on a menu selection.  When the menu selection sets the "dateTimeValue" the display is only updated (apparently) if the date changes.  If just the time changes, the control does not show the change.
For instance, if the control is currently showing "06/30/2017 12:15" and my menu item sets "dateTimeValue" to LocalDateTime().now() then the field will not show the change all day on 6/30.  If I set a LocalDateTime where the date is different into dateTimeValue then the field updates correctly.

Thanks for reporting. I have committed a fix for it now. Can you check if this resolves the issue for you?

Thanks, this does fix the problem.

Great! Can you use the snapshot in your project for now or do you need a release?

I'm fine using the snapshot I made locally, thanks!

Perfect! Thanks for getting back to me.


Favorite 1 and 2 implementation.

Hey, this is merely a request to add two buttons controlling the favorite buttons.
Thanks in advance 😌

Hey,
The 2 favorite buttons are buttons from the app itself. and are (I think) synced to the smart m-air cloud.
As far as I know and can see is this not present in the WF-RAC module.
So if we want to implement this it needs to be created as an preset or something alike.
If I have time I will check if the is a simple/nice solution for this.
note: If it will be implemented it will not sync with the favorite settings in your app.


[BEAM-684] pom.xml: replace dataflow.javadoc_opts with beam.javadoc_opts

R: @jbonofre

R: @kennknowles for careful reading of legacy Dataflow javadoc. (low priority, I will keep appending to this PR over time if not reviewed ;).

(136 -> 95 Dataflows in SDK core after changes so far)

LGTM but weird travis failed (I'm checking).

Since it requires careful reading, I may not get to it until after Strata is over.

Ping @kennknowles

LGTM. There's a conflict with master (presumably in javadoc). If you want another round after resolving conflicts, LMK.

Thanks, resolved conflict; confirmed compile; and merged


⚰ remove unncessary if condition at the beginning

Removed the unnecessary if True condition at the beginning of the main_program.py file.

lemme check this


Document nginx controller configuration tweaks

This PR contains many small tweaks to the nginx controller configuration documentation.
Some of these changes are perhaps personal taste. I am happy to change or to delete entirely.
I have another PR to follow for config map additions but I think this is un-reviewable enough.

This change is

Coverage increased (+0.04%) to 42.563% when pulling b81a49cdfdc335a5f2d77534b95c622efa103ac5 on pedrosland:docs/nginx-controller-config-1 into 2eb9ab58bc99312863b2599906206bf8999b3905 on kubernetes:master.

Thanks for the feedback.

Coverage increased (+0.02%) to 42.543% when pulling 9e94863db25ab927d393f7118a3007c44217ca41 on pedrosland:docs/nginx-controller-config-1 into 2eb9ab58bc99312863b2599906206bf8999b3905 on kubernetes:master.

Overall looks much cleaner, thanks a ton! ✏ ✏ ✏

@euank Thanks for the feedback. I've changed all of these except for this which I'm not sure about. Perhaps we should discuss this and leave it for another PR.

/lgtm

@pedrosland thanks!

Coverage increased (+0.8%) to 43.285% when pulling 292375e8b4e0d7d0d76d5048e95f22142a045756 on pedrosland:docs/nginx-controller-config-1 into 2eb9ab58bc99312863b2599906206bf8999b3905 on kubernetes:master.


Filtering criteria in apt-sm-plugin output

Proposed changes
This PR adds two features:

option to filter packages by name and maintainer in apt plugin. User have to set filters manually using tedge.toml.
limit of software list output to given number of lines using tedge config. Default value is set to 1000 and 0 means no limit to the output (STC).

Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue
#1926

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA (in all commits with git commit -s)
[x] I ran cargo fmt as mentioned in CODING_GUIDELINES
[x] I used cargo clippy as mentioned in CODING_GUIDELINES
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

Filtering the output of software-package lists must be addressed at two levels.

At the global level, by the tedge-agent, the filtering can be done only on the generic attributes as the number of entries or the package names.
At the plugin level, in this precise case the apt-plugin, the filtering can be more specific using for instance the package maintainers.

This means for this PR:

The change adding a filter parameter to the Plugin::list() method must be reverted, as this would impact all the plugins while used only by one.
What has been done to filter out the number of packages per plugin, can be kept as proposed here (I have some disagreements but minor).
Its a good idea to add  - --name and --maintainer parameters to the apt-plugin command. These parameters will be ignored by the tedge-agent but will be useful for testing purposes.
As the  - --name and --maintainer parameters are ignored by the tedge-agent, one needs to add some configuration for these parameters in tedge_config.toml. However, it's not mandatory to have these parameter managed by the tegde config command. One can add a specific stanza for the apt-plugin in tedge_config.toml. Doing so the apt-plugin will need no dependency on the tedge_config crate and can simply use serde to read the relevant parts of the config.

@reubenmiller is this okay for you that the apt-plugin read its config from tedge_config.toml, but using free settings not managed by the tedge config command? Such support can be added later and starting with something simpler would make this PR more independent of the tegde-config refactoring.

@reubenmiller is this okay for you that the apt-plugin read its config from tedge_config.toml, but using free settings not managed by the tedge config command? Such support can be added later and starting with something simpler would make this PR more independent of the tegde-config refactoring.

Yes I'm ok with this proposal for now. We might be a bit silent about the feature/docs until the support of the tedge config get/set is supported out of the box using the config refactoring PR.

Config settings have now to be added to crates/common/tedge_config/src/tedge_config_cli/new.rs.
I acknowledge that the current status is confusing as there are still some pending cleaning tasks to finalize https://github.com/thin-edge/thin-edge.io/pull/1936.
_=> I will take the time tomorrow to help you and see what needs to be cleaned.
error[E0609]: no field `max_packages` on type `TEdgeConfigDtoSoftware`
    --> crates/common/tedge_config/src/tedge_config_cli/tedge_config.rs:1072:14
     |
1072 |             .max_packages
     |              ^^^^^^^^^^^^ unknown field
     |
     = note: available fields are: `plugin`

error[E0609]: no field `max_packages` on type `TEdgeConfigDtoSoftware`
    --> crates/common/tedge_config/src/tedge_config_cli/tedge_config.rs:1082:28
     |
1082 |         self.data.software.max_packages = Some(value.into());
     |                            ^^^^^^^^^^^^ unknown field
     |
     = note: available fields are: `plugin`

error[E0609]: no field `max_packages` on type `TEdgeConfigDtoSoftware`
    --> crates/common/tedge_config/src/tedge_config_cli/tedge_config.rs:1087:28
     |
1087 |         self.data.software.max_packages = Some(self.config_defaults.default_max_packages.into());
     |                            ^^^^^^^^^^^^ unknown field
     |
     = note: available fields are: `plugin`

Config settings have now to be added to crates/common/tedge_config/src/tedge_config_cli/new.rs.

I fixed that issue just before you posted the comment.
If we are after the tedge config refactor, should we now add one for name and maintainer filters?


Unable to authenticate at https://smart.vaillant... [401 NOT_AUTHORIZED]

Hey Thomas,
THANK YOU for this integration. It saves me real money since I can control my heating!
My issue:

The integration works quite well. I am (generally) authenticated, get all data points and can send service calls against the system
But the connection to the Vaillant system is not stable
I get 401 errors NOT_AUTHORIZED (~5-6 times per hour)
Sensor data then is "unavailable"
After reconnecting properly everything works smoothly until the next reconnect
You can see the reconnects in the history of one sensor history
The issue does apply to all connected devices
The multiMATIC app on my phone works well, no AUTH issues there

My setup:

Home Assistant 2022.2.1
Vaillant multiMATIC v3.9.3
VR921 FW 357.24.2

Do you have any idea how to fix this?
Thanks a lot!
Ingo
Sensor History displaying disconnects

Disconnects of all devices

Log entry of one issue
Logger: custom_components.multimatic.coordinator
Source: custom_components/multimatic/coordinator.py:99
Integration: Multimatic ([documentation](https://github.com/thomasgermain/vaillant-component), [issues](https://github.com/thomasgermain/vaillant-component/issues))
First occurred: 10:55:44 (1 occurrences)
Last logged: 10:55:44

Unexpected error fetching multimatic_outdoor_temperature data: Unable to authenticate at https://smart.vaillant.com/mobile/api/v4/account/authentication/v1/authenticate, status: 401, response: {"errorCode":"NOT_AUTHORIZED"},payload: None
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 147, in _async_update_data
    return await self.update_method()
  File "/config/custom_components/multimatic/coordinator.py", line 516, in _fetch_data_if_needed
    return await self._fetch_data()
  File "/config/custom_components/multimatic/coordinator.py", line 509, in _fetch_data
    return await getattr(self.api, self._method)()
  File "/config/custom_components/multimatic/coordinator.py", line 99, in get_outdoor_temperature
    return await self._manager.get_outdoor_temperature()
  File "/usr/local/lib/python3.9/site-packages/pymultimatic/systemmanager.py", line 43, in wrapper
    return await func(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/pymultimatic/systemmanager.py", line 227, in get_outdoor_temperature
    return mapper.map_outdoor_temp(await self._call_api(urls.system_status))
  File "/usr/local/lib/python3.9/site-packages/pymultimatic/systemmanager.py", line 80, in wrapper
    return await func(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/pymultimatic/systemmanager.py", line 857, in _call_api
    response = await self._connector.request(method, url, payload)
  File "/usr/local/lib/python3.9/site-packages/pymultimatic/api/connector.py", line 157, in request
    await self.login(True)
  File "/usr/local/lib/python3.9/site-packages/pymultimatic/api/connector.py", line 67, in login
    await self._authenticate(token)
  File "/usr/local/lib/python3.9/site-packages/pymultimatic/api/connector.py", line 125, in _authenticate
    raise ApiError(
pymultimatic.api.error.ApiError: Unable to authenticate at https://smart.vaillant.com/mobile/api/v4/account/authentication/v1/authenticate, status: 401, response: {"errorCode":"NOT_AUTHORIZED"},payload: None

Hello,
Are you using a dedicated user for the integration ?

Yes, I did - a dedicated user for Home Assistant


When i from main branch the sub page is blank.

The three option main page could be show , but i click any button to subpage is empty.
1st Chat Page will could choose the opanai model but other page also empty page

Same issue here - the first page loads well but the "import unstructured data" page is blank.
Have you managed to fix the issue?


Redirect to the new/domain website

Related Issue
Closes #415.
Describe the changes you've made

Redirect to the new/domain website.

Assuming that the GH page is built upon the main branch, this should automatically redirect to webxdao.xyz.

Type of change
What sort of change have you made:

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

How Has This Been Tested?
Tested on my fork of this repository, works.

Checklist

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[ ] I have commented on my code, particularly wherever it was hard to understand.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] Any dependent changes have been merged and published in downstream modules.

Code of Conduct

[x] I agree to follow this project's Code of Conduct

Hi David :wave:
You mean https://webxdao.github.io/ redirect to webxdao.xyz ?
I think we should favour disable the github page as we use Vercel as hosting... wdyt ?


Support synchronized methods in Haxe

Following fxzjshm work here: https://github.com/jtransc/jtransc/pull/210
We should implement synchronized methods in Haxe. Probably the best way would be to create two functions. One public with the same signature, and other private and without reflection with the actual body, the public version should call private version doing try + catch emulating finally. Private function should have access to super keyword when available.
The other option would be intercept returns inside synchronized bodies doing the mutex release before returning and catching a exception with rethrowing at the function level . That should work too (hopefully).

For support network in haxe for me need this construction
private Object lockObject = new Object();
void request() {
  synchronized(lockObject ) {
  }
}

I thought that synchronized blocks were already implemented in haxe and the only missing thing was synchronized methods.
It should be easy to implement synchronized blocks. But i wont be able to write any code until a couple of days (i just have my mobile phone).

Seems as not working synchronized blocks
{{ HAXE_METHOD_ANNOTATIONS }} static public inline function c<T, S> (value:T, c:Class<S>):S return cast value;
i do not understand how it work as sync =) i will wait you for help me =)) i think this will be hard for me =(

I have seen the code. Haxe target doesnt seem ti implement neither sync methods nor sync blocks. I will implement sync blocks first, and then sync methods. I will work on that maybe tomorrow or the day after tomorrow when i finally get home


Installation aborted / Permission denied

...
Remove old configuration, in case it was installed before
cat /etc/asound.conf |
tr '\n' '\r' |
sed 's|\r\r# For more info about this configuration see: https://github.com/scripple/alsa_cdsp\rpcm.camilladsp.*\r}\r# pcm.camilladsp||' |
tr '\r' '\n' > /tmp/asound.conf
cat /tmp/asound.conf > /etc/asound.conf
./install_cdsp.sh: line 100: can't create /etc/asound.conf: Permission denied

I will do some tests this week with a fresh picoreplayer installation, but i have the feeling you are right, the reasons are surely configuration changes via the gui...
i forgot to mention, you need to use sudo of course:
sudo chmod 664 /etc/asound.conf
sudo chown root:staff /etc/asound.conf

maybe also just adding sudo will work:
sudo cat /tmp/asound.conf > /etc/asound.conf
sudo echo '
For more info about this configuration see: https://github.com/scripple/alsa_cdsp
will work

Thank you for the suggestion.
I'll see, if I can do it with some special sudo command like here.
If that doesn't work, I'll just change the permissions.

I just fixed this.
Thank you for the very detailed reporting.

Interesting ...
If you're not sure, why CDSP is not starting, the GUI has a button "Show log file" that should show some information to get you further.

Today some more tests, CamillaDSP is running on a fresh picoreplayer installation, after configuring bluetooth outputs via the picoreplayer guy, camilladsp is not running any more. I am not sure if this is only related to asound.conf or if adding bluetooth something else is changed, because its not working any more.

Again some more investigation why this is not working for me: the permissions of asound.conf are really only a problem during installation, which you already fixed in your script.
Now i found out, why the camilladsp process is not starting anymore after using bluetooth devices:
the parameter "-C 5" is added automatically to the squeezelite parameters via the pcp gui.
This gives an error when starting camilladsp and there its not starting successfully, when i remove it manually its working again...

The CamillaDSP GUI should be always online.
With the -C 5 parameter, CamillaDSP should be stopped 5 seconds, after the last audio output.
However, as soon as you play some audio, it should start again.
If that doesn't work, is there any log output?

Thanks for the detailed explanation, now i understand.
I thought the camilladsp process is always running and not only if there is audio output.
I tested it again and its working (tested with 2.0 alpha version), probably also working with 1.0 then.
Thank you very much for your patience and support.


ui delete containers and resources can throw a lot of alerts if not refreshed

Hi,
From the ui when deleting content and not refreshing the page, can get an overwhelming blast of alerts

alert example
Error: Web error: 404 (Not Found) on DELETE of <https://roger.localhost:8443/public/tmp/solid-fs/.git/config>

the refresh shouldn't be necessary for one thing.  But using alerts for status info is a bit rough.
Is a status bar being considered for the ui?

Thanks, @RubenVerborgh, still learning the project organization

related and solved by: https://github.com/solid/solid-panes/issues/71


Routable panels cannot be opened by swiping

Framework7 version: [e.g. 3.2.0]
Platform and Target: all
Live Link or JSFiddle: https://jsfiddle.net/mryx47ef/

Describe the bug
Routable panel cannot be opened by swiping.
To Reproduce
Steps to reproduce the behavior:

Go to https://jsfiddle.net/mryx47ef/
Try swiping to reveal right panel (it works because it's NOT a routable panel)
Try swiping to reveal left panel (it does NOT work because it's a routable panel)

Expected behavior
We should be able to open a routable panel by swiping.
Actual Behavior
Only non-routable panels can be opened by swiping.

Routable panels can’t be opened with swipe, routable panels means it will be loaded and opened on route change


DFULibrary not loaded

Environment:
Xcode:8.0
objective-c
iPhone: 5s, iOS 8.1.3
and download dependencies
Installing Zip (0.6.0)
Installing iOSDFULibrary (2.1.2)
Xcode build succeeded, but running in iPhone fail.
I got the output log as following. Please tell me what should I do?

dyld: Library not loaded: @rpath/DFULibrary.framework/DFULibrary
Referenced from: /private/var/mobile/Containers/Bundle/Application/85488289-0B51-434C-ACAF-89C3D590D909/HealthCube.app/HealthCube
Reason: image not found

Have you had installed the legacy library before installing the Cocoapod version ? you might still have the old library lingering in the project settings somewhere

@mostafaberg
Thanks a lot for your help. My project can build and run after import library !
My next step, do DFU.

No worries, glad I could help , if you have any more problems just open an issue and we'll be here to help, good luck ! 👍


[V6] Field Arrays Example with immutablejs doesn't work.

I changed reducer. Instead of:
import { Field, FieldArray, reduxForm } from 'redux-form'

I put:
import { Field, FieldArray, reduxForm } from 'redux-form/immutable'

and example is displaying properly, but when I add club name and try type text into 'first name' field I get an error:
Uncaught Error: invalid keyPath

Is there any solution/work around for it?

Can you post a reproduction repo?

I got the very same issue, but in version 5.2.5.
As far as I can see, everything started with this commit 7b5cb0f64911dffd2ac80e254719ec75333cb8f4
and introduction of fieldValue.js.
makeFieldValue is assigning not enumerable property to field object, so when trying to make Immutable from such object, not-enumerable property is lost.
It does matter, because on store, there is no _isFieldValue property assigned to field object, and because of that isFieldValue is failing when used in src/getValuesFromState.
This is not only related to Immutable.js, but also to any form of state serialization, for example JSON.stringify.
I wanted to make a pull request with easy fix to make this prop enumerable, but it comes with loads of tests changes.
I think that makeFieldValue and isFieldValue should be rewritten in some way to get rid of using not enumerable props, or adding any props at all.
I hope it helps.

@kkwiatkowski Anything in v5 is unrelated to the original issue posted here.
@tdziezyk Are you remembering to use a special immutable-enabled version of combineReducers as well as the immutable version of the redux-form reducer?

I got the same issue in v6.0.0-rc.1.
@erikras I did use the combineReducers from 'redux-immutable' and the immutable version of redux-form reducer.

tl;dr
look at the onclick logic for adding new field under your renderArrayFields function.
it should be like this:
<button type="button" onClick={() => fields.push(Immutable.Map())}>Add new member</button>

instead of:
<button type="button" onClick={() => fields.push({})}>Add new member</button>

When you try to type text into one of the field in FieldArray, state.setIn(toPath(field), value) will be called.
https://github.com/erikras/redux-form/blob/v6.0.0-rc.1/src/structure/immutable/index.js#L10
for example:
state.setIn(["values", "members", "0", "first_name"], 1)
If your are using fields.push({}), Uncaught Error: invalid keyPath error will popup.
because of:
typeof state.getIn(['values', 'members', '0']) === "object"

@jccf091 It is working after you changes.
Thank you all :)

Seems like you'd also need to modify the way FieldArray removes fields
https://github.com/erikras/redux-form/blob/a68d1a92d76ab361b1d916d437f17f5c16e63a9f/examples/fieldArrays/src/FieldArraysForm.js#L49-L53
<button
  type="button"
  title="Remove Hobby"
  onClick={() => fields.remove(index)}/>

I get an VM362197:1 Uncaught TypeError: list.splice is not a function error when I remove a field.

@oakley808, do you have the solution?

@marcosideame Nope.

@oakley808
<button
  type="button"
  title="Remove Hobby"
  onClick={() => fields.remove(index)}/>

change to:
<button
  type="button"
  title="Remove Hobby"
  onClick={() => fields.remove(index + '')}/>

look at the "onClick" function, “index” convert to string


mopidy-argos: init at version 1.12.0

Description of changes

mopidy-argos: init at version 1.12.0
Things done

Built on platform(s)

[ ] x86_64-linux
[X] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

[ ] sandbox = relaxed
[X] sandbox = true

[X] Tested, as applicable:

Launched and confirmed functionality

[ ] 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
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 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.

Thank you for the feedback @FliegendeWurst

Figured out the new nixfmt requirement :+1:

Thank you for the feedback! I've incorporated it into a new revision and the package still builds and launches for me.


Fix for delete cache error on windows

Killed the nb process and the stopped the LSP client so that no process is using the cache  before deleting the directory .
Closed #221

Added a callback for error handling


fix panic: invalid SlotMap key used

Objective
Tight, in-frame generation, re-parenting, despawning, etc., UI operations could sometime lead taffy to panic (invalid SlotMap key used) when an entity with an invalid state later despawned.
Fixes #12403
Solution
Move the remove_entities call after children updates.
Testing
sickle_ui had a case that always caused the panic. Tested before this change, after this change, and before the change again to make sure the error is there without the fix. The fix worked. Test steps and used commit described in issue #12403.
I have also ran every bevy UI example, though none of them deal with entity re-parenting or removal. No regression detected on them.
Tested on Windows only.

Wish I had the time to create a proper test suite for this.

Looks good to me.

@nicoburns perhaps has a strong opinion?

I do not have strong opinions on this. I'm in a similar boat to:

not absolutely confident this doesn't have side effects, but I can't think of any and it makes sense to me

so this is likely the offending area triggering the crash https://github.com/bevyengine/bevy/blob/158ccc6d6a45eb048cc3f40388f9cff0fc633375/crates/bevy_ui/src/layout/ui_surface.rs#L128-L131
Because we are unwrapping the internalmap/taffy result with the parent entity who would have already been removed by the line this PR is moving.
I did a little sanity check to double check:
Index: crates/bevy_ui/src/layout/mod.rs
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/crates/bevy_ui/src/layout/mod.rs b/crates/bevy_ui/src/layout/mod.rs
--- a/crates/bevy_ui/src/layout/mod.rs	(revision Staged)
+++ b/crates/bevy_ui/src/layout/mod.rs	(date<PHONE_NUMBER>091)
@@ -276,7 +276,8 @@
     }

     // clean up removed nodes
-    ui_surface.remove_entities(removed_components.removed_nodes.read());
+    let removed_nodes = removed_components.removed_nodes.read().collect::<HashSet<_>>();
+    ui_surface.remove_entities(removed_nodes.clone().into_iter());

     // clean up removed cameras
     ui_surface.remove_camera_entities(removed_components.removed_cameras.read());
@@ -298,6 +299,9 @@
     }
     for (entity, children) in &children_query {
         if children.is_changed() {
+            if removed_nodes.contains(&entity) {
+                continue;
+            }
             ui_surface.update_children(entity, &children);
         }
     }

and this does in fact prevent the crash as well, but obviously (or at least imo) moving the line down below makes more sense.
The part that confuses me is the tests I made for this specific condition fail when run on main but pass in my PR, yet don't prevent the crash in your reproduction example.. So, I'm inclined to believe there is some kind of race condition, and moving the line is the way to go for 14.0.
If we want to have a test suite that covers this, I can extract my regression tests mentioned above into their own PR after this gets merged.

I can't create a regression test that mimics the slotkey error. It's likely related to moving a UI node to a new parent and despawning the old one.
Regardless, this is a good fix. Intuitively, you'd need to perform operations on all the children and ensure they are in sync on the taffy's side before removing the UI node.
IMO it's highly unlikely this will introduce any negative side effects. Especially considering how the layout system is already omitting the handling of other hierarchy changes that I've been meaning to open tickets for  :upside_down_face:

it does bother me to no end that I don't have the bare basic broken test case myself, but the slotmap ends up in the erroneous state way earlier than when the despawn trips it.


generator: Use types from evolution instead of defining them

This makes sure the widget types are as expected and defined in evolution. It removes unused fields in some default inputs for some types.
Tested with generated survey, it may cause compilation errors, easy to fix, on custom widgets.

I extracted the common string types


Various improvements in customizability etc.

Hey, here I have some changes to add customizability and some new mappings. I hope they are useful.

commit 90ff7b2 should read "make config window type customizable via variable", markdown has folds on some setups and 'sh' has already a default good highlight, you can set this to markdown if you want, but the variable adds options to the user.

I added C-c to hide config buffer, and x to test,  is my leader, so I thought having options would be good

I also added a hint mapping customization via variable as well.

the double escaping is no longer needed (?) at least it isn't on my system so I fixed the docs

Added a command that would propagate a global packet's pane selection to the three individual configs with changes to SelectPane when receiving a packet of type "global"

Added a command SlimuxSendKeys akin to SlimuxShellRun, that can send arbitrary keys directly from the command line.

Added a command SlimuxREPLSendParagraph and GetParagraph function to be able to send a paragraph

Made some stuff silent, as it may be verbose on some vim configurations.

Ah, of course, I forgot about the GetBuffer and GetVisual when I went to implement GetParagraph. But the idea is there.

PAM!  So I'm gonna trust your judgement for merging this. It's only reasonable way to move Slimux forward.
Feel free to checkout the other PRs too :)

Awesome, thanks. I also have limited time, but I'll do my best to improve on this code. I use it for work so it's only fair.

@dhoe @sunaku
Here's the change replicated from the #11


Add feature for true-false questions

This seems like a good enhancement for the next team.

I agree.


An Ember-CLI deprecation coming soon

With a recent change made to ember-cli, the usage of nodeModulesPath in this add-on will start throwing deprecation notices:

original issue (with a link to Ember Observer code search showing this add-on using nodeModulesPath)
PR that fixes the issue and adds the deprecation warning
EmberObserver code search showing problem lines

I'm not hitting the issue yet, but it's coming down the pipe 😀

@acorncom thanks a lot for the notice! I just created #507 that should fix this!


Free energy change as a function of time plot issue

It would be interesting to adjust the axis range in such a way that if the error associated to a point in the plot is bigger than, say, 1.0 free energy unit, the scripts only prints the graph within a reasonable range. This way plots like the one attached here wouldn't happen.
dF_t_5ns_acetaminophen.pdf

Can you provide a link to the .xvg files for this to make
troubleshooting/fixing easier? (i.e. Dropbox link)
On Wed, Jan 13, 2016 at 2:04 PM, Guilherme<EMAIL_ADDRESS>wrote:

It would be interesting to adjust the axis range in such a way that if the
error associated to a point in the plot is bigger than, say, 1.0 free
energy unit, the scripts only prints the graph within a reasonable range.
This way plots like the one attached here wouldn't happen.
dF_t_5ns_acetaminophen.pdf
https://github.com/MobleyLab/alchemical-analysis/files/89550/dF_t_5ns_acetaminophen.pdf
—
Reply to this email directly or view it on GitHub
https://github.com/MobleyLab/alchemical-analysis/issues/67.

--
David Mobley
Associate Professor
Department of Pharmaceutical Sciences
Department of Chemistry
3134B Natural Sciences I
University of California, Irvine
Irvine, CA 92697
<EMAIL_ADDRESS>work<PHONE_NUMBER>
cell<PHONE_NUMBER>

@gduarter - can you provide a link for the .xvg files for this?


[Coverity CID :187062] Incorrect expression in /samples/net/sockets/echo_server/src/udp.c

Static code scan issues seen in File: /samples/net/sockets/echo_server/src/udp.c
Category: Incorrect expression
Function: process_udp
Component: Samples
CID: 187062
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

This one looks like a false-positive to me. The code pointed by Coverity is valid and is not a copy paste.

False positive.


iOS: Add onScroll event to TextInput

Corresponding Android PR: https://github.com/facebook/react-native/pull/11001
This adds an onScroll event to TextInput which is useful when a multiline TextInput has so much content that it is scrollable.
Test plan (required)
Verified the event works properly in a test app. Also, my team uses this event in our app.
Adam Comella
Microsoft Corp.

Looks great, thanks for the addition!

@facebook-github-bot shipit


Draggable split pane

It should be possible to click and drag the dividing line between the sidebar and the main code editor view, like in VSCode.
There is some code that does this in VizHub here: https://github.com/vizhub-core/vizhub/blob/main/vizhub-v2/packages/neoFrontend/src/pages/VizPage/SplitPaneResizeContext/index.js

Closed by #162


add Xpresso to frameworks

@klen would you mind adding this one? :pray:

Hi @klen, anything I can do to move this along?


add heartbeat at task and run level

add sidecar for heartbeat on task and run
testing still required
Note the corresponding change needs to be made and deployed in the metadata-service (see https://github.com/Netflix/metaflow-service/pull/27) and the initialization of the sidecar should be gated based of what version of the metadata-service is deployed (old versions will not have the new heartbeat endpoints)

@ferras This PR doesn't handle attempt-level heartbeats. Do we want to consider introducing attempt-level heartbeats - it might simplify the UI implementation significantly.

@ferras This PR doesn't handle attempt-level heartbeats. Do we want to consider introducing attempt-level heartbeats - it might simplify the UI implementation significantly.

as the name implies this is only meant to handle task and run level heartbeats :)
Regarding the concept of attempt-level heartbeats I don't think it really makes sense to have them on an attempt level. The purpose of the heartbeat is to know if a task is currently running. If an attempt of a task failed and we were able to start a new attempt then we should use 'attempt-done' that was written to the metadata table for the purposes of rendering the UI. I don't think adding different heartbeats at the "attempt" level will simplify the UI implementation in that regard. Much of the complexity there actually comes from the need of handling legacy runs which are missing the 'attempt-done' metadata that was added in November of 2020.
If you do decide to implement a heartbeat at the attempt level, that will require changes to the data model in the underlying DB as well as the metaflow-service api which would need to happen before any changes within metaflow core


chore(scripts): add contributor list generation

This will automatically generate a contributor list as part of the pre-commit process. Once this is approved, it will be ported over to tds-community.
This should be squashed.
prepr output:
No components have been changed, nothing to do. Exiting.
lerna info versioning independent
lerna info ignore [ '*.md', '*.spec.jsx', '*.snap' ]
lerna info Checking for updated packages...
lerna info Comparing with<EMAIL_ADDRESS>lerna info Checking for prereleased packages...
lerna info No updated packages to publish.

🤔 If this is not what you expected, ensure that your commit messages follow the Conventional Commits specification (https://conventionalcommits.org) and try again.

🚀 Please paste the entire output of this task into the body of your Pull Request so that a maintainer can verify before merging/publishing.

Actually I thought of something here, if this happens during precommit or prepush, does it modify any files? Do those files then need to be added to the commit?

@ryanoglesby08 Oh right! Thinking back that’s actually why I put it there in the first place. I can move it back.

@marcod1419
Well, I don't know, if you do it precommit the changed file will still need to be git added. And its likely that we and contributors will forget that.
Maybe the script should make the change and then do the git add?


build:epub doesn't finish

When I run a build:epub I see it starts, but it never seems to complete:
$ softcover build:epub
Building EPUB...
Note I'm compiling the basic a_chapter book that was generated by the new command.
I see phantomjs is running, but at 0 CPU.
After hitting CTRL+C  I see the following trace:
^C/Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/softcover-1.0.beta17/lib/softcover/output.rb:36:in ``': Interrupt
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/softcover-1.0.beta17/lib/softcover/output.rb:36:in `system'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/softcover-1.0.beta17/lib/softcover/builders/epub.rb:176:in `block (2 levels) in html_with_math'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.19/lib/active_support/core_ext/kernel/reporting.rb:45:in `silence_stream'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/softcover-1.0.beta17/lib/softcover/builders/epub.rb:176:in `block in html_with_math'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/softcover-1.0.beta17/lib/softcover/utils.rb:220:in `block in silence'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.19/lib/active_support/core_ext/kernel/reporting.rb:45:in `silence_stream'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/softcover-1.0.beta17/lib/softcover/utils.rb:219:in `silence'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/softcover-1.0.beta17/lib/softcover/builders/epub.rb:176:in `html_with_math'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/softcover-1.0.beta17/lib/softcover/builders/epub.rb:144:in `block (2 levels) in write_html'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/softcover-1.0.beta17/lib/softcover/builders/epub.rb:130:in `open'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/softcover-1.0.beta17/lib/softcover/builders/epub.rb:130:in `block in write_html'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/softcover-1.0.beta17/lib/softcover/builders/epub.rb:128:in `each'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/softcover-1.0.beta17/lib/softcover/builders/epub.rb:128:in `each_with_index'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/softcover-1.0.beta17/lib/softcover/builders/epub.rb:128:in `write_html'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/softcover-1.0.beta17/lib/softcover/builders/epub.rb:54:in `build!'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/softcover-1.0.beta17/lib/softcover/commands/build.rb:12:in `for_format'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/softcover-1.0.beta17/lib/softcover/cli.rb:54:in `block (2 levels) in <class:CLI>'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/command.rb:27:in `run'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/invocation.rb:120:in `invoke_command'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor.rb:363:in `dispatch'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/thor-0.18.1/lib/thor/base.rb:439:in `start'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/gems/softcover-1.0.beta17/bin/softcover:4:in `<top (required)>'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/bin/softcover:19:in `load'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/bin/softcover:19:in `<main>'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/bin/ruby_noexec_wrapper:14:in `eval'
	from /Users/ivan/.rvm/gems/ruby-1.9.3-p194/bin/ruby_noexec_wrapper:14:in `<main>'

For general info, I'm on Mac OS 10.6, with the following versions of things:
$ softcover check
Checking Softcover dependencies...
Checking for LaTeX...         Found
Checking for GhostScript...   Found
Checking for ImageMagick...   Found
Checking for Node.js...       Found
Checking for PhantomJS...     Found
Checking for Inkscape...      Found
Checking for Calibre...       Found
Checking for KindleGen...     Found
Checking for Java...          Found
Checking for zip...           Found
Checking for EpubCheck...     Found
All dependencies satisfied.

$ phantomjs -v
1.9.8

$ tralics -v
This is tralics 2.15.1, a LaTeX to XML translator, running on probook

Is there a way to turn on "dubugging info" in builders/epub.rb ?

Thanks for the report. I'm unable to reproduce, but we'll keep our eye on
it. We're hoping to make a server-side version of the production system,
which would fix issues like this as a side-effect.
On Mon, Dec 29, 2014 at 9:42 AM, Ivan Savov<EMAIL_ADDRESS>wrote:

I did some more tests and changes, notably moved project to a directory
that does not contain spaces, and commented out the silence {
silence_stream(STDERR) { system cmd } } and now I see this appears after
some time:
Timed out waiting for MathJax
which seems to come from the code in builders/utils/page.js.
--
Reply to this email directly or view it on GitHub
https://github.com/softcover/softcover/issues/127#issuecomment-68279175.

--
Michael Hartl
Author, Rails Tutorial http://www.railstutorial.org/
Founder, Softcover http://www.softcover.io/

Followup: I believe I traced this problem to the Mac OS application security---the first time Inkscape runs it pops up a warning "This program was downloaded from the internet ... yada yada..." which was interfering with epub build.
Works great now, so closing.

:+1: