Propagate cluster s3 bucket information to the compute nodes

This is required to fetch config from S3 if for some reason the config file is no longer available in the shared storage.
As part of cookbook refactoring I wrongly moved the fetch_config.rb before the mount of the shared storage. Since the config was not available from the shared storage, the compute node was trying to download it from s3 but the cluster/cluster_s3_bucket node attribute was unavailable.
I'm going to restore the order to avoid fetching from s3 every time but in any case it's useful to add robustness to the compute nodes fetch_config logic.

This patch is incomplete, s3 key is missing.


Built-in support for HOA: Leave or Stay?

Should we keep built-in support for HOAs (higher order apps) or shall we encourage you to roll your own DIY solution? For example using a right to left function reducer like compose or good old f(g(..)).
The tradeoff is more flexibility & less bytes for one less selling point.

Some facts about HOAs:

99% users will never need to author a HOA.
You don't even need to use a HOA, but some of you may want to in order to facilitate debugging.
HOAs are ought to be used primarily for adding debugging functionality to your apps, enable logging of actions / state updates, add Developer Console support (devtools), TimeTravel, HMR, bypass the VDOM to target a different renderer, e.g., a terminal. Other valid uses, but not strongly encouraged include augmenting Hyperapp "core features", e.g., introducing new app props to enable pre-wired component views, etc.
HOA is not a unique Hyperapp cooncept. You can create a higher order function of any function in the universe. Hyperapp does go out of its way to make slightly more convenient for you if you want to author a HOA, but we are not bending the laws of physics or being too unique.
You can do and abuse HOAs as much as you want with this feature built-in or not (in case we decide to remove it).

/cc @pspeter3 @okwolf @zaceno

Do we need built-in support for HOA or shall we encourage you to roll your own DIY solution? For example using a right to left function reducer like compose?
/cc @pspeter3 @okwolf @zaceno

@JorgeBucaran would you be opposed to publishing an official @hyperapp/compose so less wheel reinventing would occur?

That's one option to keep in mind. Let's see what everyone else thinks.
This issue was brought about from this discussion.
After realizing that to use multiple HOAs each HOA needs to be coded in a way that doesn't break the middleware chain, @pspeter3 commented:

I feel like the HOA abstraction is great but the API feels really awkward when you need to consider all the other higher order apps.

...and...

That's exactly what I'm thinking. It seems even less necessary now that there are modules.

Question: does HOAs need access to the app()'s returned actions/modify app()'s return type?
If not, then we could instead support HOP/props enhancer: (appProps) => enhance(appProps). This would be easily composable and we may want to keep support for that in core?

@Mytrill They may need to access the actions returned by app() as well as enhance props and create a closure. Can you show an example of what you are saying?

The main proposal were to compose HOA in a curried way, is this really prerequisite to this feature ?
I mean we are not stuck at the use of this curried way app(HOA1)(HOA2)(HOA3)({ ... }).
Maybe it would be good to compose from an array of HOA app([HOA1, HOA2, HOA3])({ ... }).
HOA will still need to be aware of the returned value of the previous HOA.

@Swizz Reminds me of mixins! 😉

I like @Swizz's idea of an array, it makes it easier to dynamically add HOAs (e.g. depending on the environment)
Here is something that could work if we want to support it in core and access to app()'s result:
// general pattern
const doSomethingWithAppResult = actions => actions
const doSomethingWithProps = props => props

const AppEnhancer = next => props => {
  // returns the enhanced app
  return doSomethingWithAppResult(
    // calls the next HOA/app enhancer
    next(
      // enhance the props
      doSomethingWithProps(props)
    )
  )
}

// example hoas
const hoa1 = next => props => {
  console.log('HOA 1 received props: ' + JSON.stringify(props))
  const result = next({ ...props, hoa1: true })
  console.log('HOA 1 returns app: ' + JSON.stringify(result))
  return result
}

const hoa2 = next => props => {
  console.log('HOA 2 received props: ' + JSON.stringify(props))
  const result = next({ ...props, hoa2: true })
  console.log('HOA 2 returns app: ' + JSON.stringify(result))
  return result
}

// implementation of app()
function app(appProps) {
  if (Array.isArray(appProps)) {
    return appProps.reduce(function(prev, curr) {
      return curr(prev)
    }, app)
  }
  // rest of app()'s implementation...
  // just wrap the props for this example
  return { props: appProps }
}

console.log('Final app: ' + JSON.stringify(app([hoa1, hoa2])({})))

The snippet above logs:
HOA 2 received props: {}
HOA 1 received props: {"hoa2":true}
HOA 1 returns app: {"props":{"hoa2":true,"hoa1":true}}
HOA 2 returns app: {"props":{"hoa2":true,"hoa1":true}}
Final app: {"props":{"hoa2":true,"hoa1":true}}

We could also reverse the array so they are called in the intuitive order...

@JorgeBucaran You meant ?
app({
  ehancers: [HOA1, HOA2, HO3]
})

Looking at a basic example of what a HOA actually is supposed to do,
function hoa(app) {
  return props => {
    return app(enhance(props))

    function enhance(props) {
      // Enhance your props here.
    }
  }
}

We're not doing anything with app, we are manipulating the props we pass in.
It feels quite logical to do that before calling app, so that your props are all good and ready by then.
Basically, one or many function (props) functions are what people really need.
And manipulating an object is like the simplest thing you can do.
So I feel that the need for app in all of this is a cause for initial confusion more than anything,
and forces the developer to have to consider something they shouldn't have to,
const myHOA = app => props => typeof props === "function"
  ? props(app)
  : enhanceTheApp(props)

Documenting that to enhance the application, all you need is a function (props) seems like the easiest thing to do both for Hyperapp but also users of Hyperapp?

Now with init and modules landed in core and with the recent realization that the built-in support for authoring a HOA is not particularly that helpful, I propose we remove this from core and encourage users to DIY! 🔥

@johanalkstal in this case, you are removing the ability for HOAs to enhance the value returned by app()

@Mytrill I was just using the examples provided by @JorgeBucaran to explain what HOAs are.
Are those examples incorrect?
Also, why would you want to manipulate the returned actions from app? I can't see why?
Or did I missunderstand you?

Modifying an object before passing it to a function (in this case, app) is a very common thing to do (at least for me, but I would think for most people). It's so common, in fact, that I arrived at the same solution as modules, but called it components instead.  So perhaps we won't need HOAs in the next release.

@Mytrill All I am saying is let's compose HOAs outside core, not veto the bill 😉
Instead of app(logger)({ ... }):
logger(app)({ ... })

I agree that we take out the support for passing a HOA into app, and let people compose their enhanced apps however is appropriate for their use case. Because use cases  range from simple (just using one HOA or none always) to complex (multiple HOA, some must be switched on or off depending on NODE_ENV, etc)
And as long as HOA can just be regular functions with no special tricks built in, everyone will know how to use them and have their own preferred way of dealing with them.
Besides, I think the most common scenario is zero HOA anyway, as @JorgeBucaran pointed out.

@zaceno I rewrote the HOA tests and didn't need to touch the implementation of the HOA functions (as you'd expect) and the difference is only in how you apply it to app. No need for compose and the result is more functional buddy. Having said that, a utility function to help compose multiple HOAs in particular ways as you described could be handy.
B(A(app))({
  state: {
    value: 0
  },
  init(state) {
    expect(state).toEqual({
      value: 2
    })

    done()
  }
})

Ah ok, got it, thanks!
I'm all for removing the support then!

Changed my mind too. The following A(B(app))({ ... }) is better for users, community developers and remove complexity in core.


[eslint-plugin-lit-a11y]: implement control-has-associated-label

See: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/master/docs/rules/control-has-associated-label.md
From the docs:

Enforce that a control (an interactive element) has a text label.
There are two supported ways to supply a control with a text label:

Provide text content inside the element.
Use the aria-label attribute on the element, with a text value.
Use the aria-labelledby attribute on the element, and point the IDREF value to an element with an accessible label.
Alternatively, with an img tag, you may use the alt attribute to supply a text description of the image.

Succeed
html`
  <button type="button" class="icon-save">Save</button>
  <button type="button" aria-label="Save" class="icon-save"></button>
`;

Fail
html`
  <button type="button" class="icon-save"></button>
`;

Proposed Options
{
  "rules": {
    "lit-a11y/control-has-associated-label": ["error", {
      "labelAttributes": ["label"],
      "customElements": [
        { "tagName": "mwc-textfield", "attribute": "label" },
        { "pattern": "mwc-(\\w+)-button", "attribute": "label" },
        { "pattern": "vaadin-(.*)button", "attribute": "label" },
        { "tagName": "label-slot", "slot": ["label"] }
      ],
      "ignoreElements": [
        "audio",
        "canvas",
        "embed",
        "input",
        "textarea",
        "tr",
        "video",
      ],
      "ignoreRoles": [
        "grid",
        "listbox",
        "menu",
        "menubar",
        "radiogroup",
        "row",
        "tablist",
        "toolbar",
        "tree",
        "treegrid",
      ],
      "depth": 3,
    }],
  }
}

labelAttributes is a list of attributes to check on the control element and its children for a label. Use this if you have a custom element that uses an attribute to render and internal <label>, for example.
customElements is a list of objects that specifies either a tag name or a RegExp pattern with an associated attribute which, if present and non-empty, validates the control as being labeled, or a required slot for the label content.
ignoreElements is an array of elements that should not be considered control (interactive) elements and therefore they do not require a text label.
ignoreRoles is an array of ARIA roles that should not be considered control (interactive) roles and therefore they do not require a text label.
depth (default 2, max 25) is an integer that determines how deep within an element's children the rule should look for text content or an element with a label to determine if the interactive element will have an accessible label.

not stale

What do we do about
const content = html`<span slot="label">haha</span>`;
render(html`<label-slot>${content}</label-slot>`;

Do we just pass any control CE that has a node-position interpolation?


Make mathjax available on more sections

I tried using mathjax in logotitle and it worked well.

However, after switching to other sections (e.g. Archieves, etc.) mathjax doesn't work.

How can I make it works on other sections?

An upstream(mathjax) issue. I guess not all html element will be pick up.

An upstream(mathjax) issue. I guess not all html element will be pick up.

only when section showing article content, mathjax appear to work. Maybe the code loading mathjax is within article, is that right? Then by picking it out from article and puting in in the head tag do solve the problem.

only when section showing article content, mathjax appear to work. Maybe the code loading mathjax is within article, is that right? Then by picking it out from article and puting in in the head tag do solve the problem.

An upstream(mathjax) issue. I guess not all html element will be pick up.

My new pull request fixed this problem and add new features to your theme.
I'll be appreciate if you can review and merge it to your project. :)

An upstream(mathjax) issue. I guess not all html element will be pick up.

My new pull request fixed this problem and add new features to your theme.
I'll be appreciate if you can review and merge it to your project. :)


Upgrade binaryen and fix some trans errors

This upgrades binaryen since some of our debug/release validation
behaviors have improved on master (and a bit of the handling around
validation and tracing has been improved to investigate those
differences).
This made our tests fail validation because of some seemingly invalid
BinaryenDrops and BinaryenTeeLocals. I’m not exactly sure what the
purpose behind those was, so I just removed the (I think) invalid ones
creating the errors with our tests.

Thanks!


Timo/vectors

A proposal for an interface to vectors and linear spaces.

Operators are defined by giving input and output linear spaces.
Linear Spaces are vector factories, but also have routines for inner products, norms, etc.
An implementation would provide a default Euclidian Space templated on just the Item type. For complex scenarios (e.g. the norm requires a mass matrix, etc.) we would override this.
Vectors do not have direct getter methods. Rather, they return a View class. The reason is that a vector might live on a compute device. So by having to call a view method the implementor for the vector can make sure that the data is first transferred to the CPU, and when the view methods goes out of scope it can be synced back to the device.

I am not yet happy with how we define vectors and spaces. If we think about a new library it may be useful to get away from classical thinking. What do I mean with this?
Classically, a vector space element is always represented as a vector with a certain number of scalars inside it representing R^n or C^n.
However, in a traits based design, why do we think about vectors in such a restrictive way? We already have a VectorSpace object, which is quite generic. And this vector space object produces vectors.
Could a vector be a function, and a matrix an operator on those functions? There is nothing in the traits design that would contradict such a generalized view (apart from us thinking in terms of vectors as arrays of numbers).
Is this relevant? Yes! This is exactly what for example Chebfun in Matlab is doing. Internally, the implementation eventually uses numerical values. But the choice of this implementation should not guide our traits design.
We don't need to change much around for this to work nicely. We just need to be a little more careful, e.g. the type Item does not make sense as associated type for Vectors, and we should only have a Field type as part of the function space.

Okay, this is like ContinuumArrays.jl and the way I have students construct the Legendre polynomials in my class (without that package). But if a Vector can be functions, why does it need an Item? They can't be "indexed", but algorithms like Gram-Schmidt work fine.
ContinuumArrays.jl allows functions to be indexed at real values, but that's really syntactic sugar for pairing with the dual space. So $f(x_i) = \langle n_i, f \rangle = \int \delta(x - x_i) f(x) dx$ in terms of the Dirac $\delta$ function. In Ciarlet's finite element formalism, the $n_i$ are called "nodes", and they can be more creative (derivatives at points, surface integrals and moments, etc.). If we pursue this, I think we'd need a trait for dual spaces. One can't rely on Riesz representation to handle things like point sampling ($\delta$ functions) of polynomials.

Just playing around with this and trying to come up with a good generalization that lets catch discrete and continuous objects. We need to do it though that the 90% of cases in which users want standard vectors, does not become more complicated. But should be possible with the right traits structure.
I am not convinced though that we need a separate dual space type. A dual space is also a space. What we may need though is a dual method that pairs an element of the space with the dual space. It might be workable that the dual space is by default the space itself but can be redefined by the user.

One reason for a dual space is dealing with x[i] meaning $\langle \bm e_i, \bm x\rangle$ where $\bm e_i$ is the column of the identity. If these are just normal elements of the space, then you'd be doing lots of extra work.
If dealing with polynomials of max degree, then point evaluation (an element of the dual space) can be represented by an inner product, but it's a lot of work to do that and requires evaluating basis functions at the point and solving a linear system (if I'm thinking about it correctly). Anyway, the point is that these Riesz-type representations are really cumbersome if you need to form them explicitly. I recognize this is getting far afield of the basic linear algebra goal, but if we want a library for semi-continuous linear algebra, I think dual spaces are necessary.

Next version of the interfaces. We now have a basic LinearSpace interface, from which various specialisations derive. Similar with the element of a space.
A difficulty is the notion of matvec_h. This does not make sense in the continuos context unless we also specify dual spaces by default, which is getting messy.
My suggestion is for operators to define a new trait AsDual, which defines a method `pub fn dual(&self), which returns the dual operator. The meaning of this is then left to the implementor.
For matrices living in finite dimensional spaces we may want to have a specialisation of OperatorBase that defines matvec, mathvec_h, etc (matvec would then refer back to the general apply method of OperatorBase).

Are you happy for us to merge this version? We started working on some core implementations of the data structures for concrete sparse matrices. I think the the interface is slowly beginning to converge. But we will get more insight by trying out some concrete implementations.


Localhost should refresh when editing a javascript file when running "grunt server"

This works fine for the grunt serverall command when the tests are also run but grunt server should refresh the page when editing javascript without running tests.

Resolved in #36


Tracking of 5.1 update seems unreliable

After calibrating properly in 5.0, my controllers worked fine with very little need to adjust.  Using this with Riftcat, I only had to recenter riftcat on very rare occasions.
Since 5.2, and the need to press the controllers to your face and hit the 2 buttons, I've had really bad controller drift.  They would end up far out of place within a couple minutes of playing, and no matter how often I reset using the buttons, the controllers would always be pretty out of wack.  Once they drifted, only restarting PS move service would correct it, albeit for a short period of time again.
A few things that would happen when using the 2 button hotkey:

Controllers would center properly again, but would have a bad rotation on one or 2 of the controllers
Controllers would not center properly
Controllers would center properly, but move at a 90 degree angle

I switched back to 5.0 to see if it was perhaps my 2 year old who dropped the controllers too much, but once calibrated again in 5.0, it worked perfectly again, and for long periods of time.  I really want to go back up to 5.2 for the 5% drop in CPU performance, but it's unplayable for me due to the drift.
Is this normal, or am I missing some configuration steps in 5.1?
Thanks,

-When you say "drift" you mean position drift or or orientation drift? (or both?).
-After you notice the drift, if you lauch the "test tracking" tool in PSMoveConfig is that off as well? Or is it only off in steam?

The answer is "both" on both accounts.
While calibrating the controllers, if I calibrated them in sequence, by the time I finished the 3rd controller and came back, it was off by about 60-70 degrees in rotation.  I checked specifically by laying the controller 0 down on a surface pointing directly toward the front at 0 degrees along the green line.  Without touching it, it would stray on its own.
In game, it would demonstrate the same thing.  It would also stray about the same degree in direction.  So if I held the controller horizontal pointing directly forwards, and extended forwards, it would move forwards in the direction it was pointing in game along that same offset angle.
I'd be happy to do any further testing you want, but I just have a question how to maintain my current settings and calibration of the 5.0 setup I'm running.  Just to be certain, am I able to just rename my appdata folder and run the 5.2 download in a seperate folder?  This way I just need to name it back correctly in appdata to restore my previous setup?  Or is there something else that I would need to change as well?
Thanks for your attention on this.  I can't stress enough how much I appreciate your work.

Interesting. It's possible the orientation drift is affecting the ability to align the tracking spaces correctly. I just did a test locally on the new 5.3 release (https://github.com/cboulay/PSMoveService/releases/tag/v0.9-alpha5.3) and I'm not seeing the same issue. Not that I think that's fixed, just that I think the drift is dependent on local conditions. I think I need to expose a setting for the magnetometer that effects how much we attempt to blend in the magnetometer reading. I think for some people it's too low, which leads to yaw drift.

Just to be certain, am I able to just rename my appdata folder and run the 5.2 download in a seperate folder? This way I just need to name it back correctly in appdata to restore my previous setup? Or is there something else that I would need to change as well?

Yup that should be fine. All settings are stored in %appdata%\PSMoveService so backing up and restoring that folder between version is fine. Also, always make sure to re-run SteamVR_ReinstallDriverWin64.bat when switching back and forth between release (the client API used by the steamvr plugin can vary per release as new features are added).

Quick update -
This issue may have been partly user error.  I tested this again using 5.3 this morning and my first controller calibrated without yaw drift, then the next 2 failed and had the same results as above.  I recalibrated those 2 controllers a few more times, and restarted the service after each calibration and finally had all 3 controllers stable.
Controller 0 - 1 attempt to get stable
Controller 1 - 3 attempts to get stable
Controller 2 - 5 attempts to get stable
I don't think 5.2 - 5.3 fixed the issue since I had such trouble getting it done right. But I'm happy to report it seems to be working correctly in the config tool.
I will test this out with real use later tonight, but I wanted to update you that I did manage to get it right, so it's not broken.  It may be just a bit finicky, but correctable with some perseverance.
If there is anything else I can do or test, let me know!
Thanks,

I don't think 5.2 - 5.3 fixed the issue since I had such trouble getting it done right.

Agreed. Sounds like there are some improvements that could be made to the magnetometer calibration. Would you mind attaching the %appdata%\PSMoveService\xx_xx_xx_xx_xx_xx.json config file for a controller with a config attempt that didn't work and then a second version for when it does. I'm curious if there is a notable difference in the magnetometer calibration values between attempts.
In case your curious the magnetometer values in question look like this:
        "Magnetometer": {
            "Center": {
                "X": "65",
                "Y": "-121",
                "Z": "92"
            },
            "BasisX": {
                "X": "1",
                "Y": "0",
                "Z": "0"
            },
            "BasisY": {
                "X": "0",
                "Y": "1",
                "Z": "0"
            },
            "BasisZ": {
                "X": "0",
                "Y": "0",
                "Z": "1"
            },
            "Extents": {
                "X": "146",
                "Y": "146",
                "Z": "140"
            },

Where the "center" is the midpoint of the bounding box that encloses the magnetometer readings, the extents are the half-widths of the bounding box (should be close to the same value across each axis), and the "identity" is the direction of magnetic north recorded in the second step of the magnetometer calibration (i.e. when your controller is aligned with the axes of the calibration mat).

I'm updating the bug title to be about fixing the controller drift issue specifically.

I ended up getting lucky and first calibration went poorly with some mild, but consistant yaw, and second calibration went well with a stable controller.  Here are the 2 calibrations of the same controller.
Controller Calibrations.zip

Thanks for taking the time to record those! It looks like the biggest difference is in the magnetometer extents. In the good config file:
            "Extents": {
                "X": "168",
                "Y": "171",
                "Z": "170.5"
            },

And in the bad config file:
                "X": "168.5",
                "Y": "175",
                "Z": "155"

Note in the good case that the extents are about the same. This is typically what they should be in an environment with little to no magnetic distortions. In the bad calibration (which isn't that bad) the z-axis is a bit smaller than the true extents. This distorts the magnetometer readings a bit from their true direction, which will lead to drift.
In the mean time, you can prevent drift by making sure you're getting even coverage of the magnetometer sample points (try and maximize the extents). You can tell you have this if the extent values are within around +/- 5 of each other. I have the extent numbers circled in this diagram (from another thread):

Now all that said, it sucks that this calibration is that finicky. This can actually be fixed by computing a best fit ellipsoid of the sample points to get the true magnetometer readings shape. I have one algorithm I wrote a while for this, this "min volume fitting", but that turned out to be the non ideal fit. I need to instead implement a "least squared error fit". Then this wont be so sensitive. I'm going to update the title of the bug to reflect this issue.

That helps a lot, thanks!  What's happening makes a lot of sense now.
I knew when I calibrated that it wasn't all that horrible, but it did continue to drift so I figured it would show.
Can any of those values be manually adjusted in that json file?  For example, could we tweak the extents say from 168-170 to tighten it up?  Also, and more importantly, are you able to adjust the yaw angle of the controller in there?  This way I can ensure that all 3 controllers are lined up 100%.  Or would this just cause issues down the road?
In closing, I would consider this issue resolved for myself now.  But the work your doing and this software absolutely fascinates me! lol

Yeah you can manually tweak values in there (the config file is the authority on the controller settings).
You can tweak the yaw, but it's not intuitive. It's effectively stored as the direction of the magnetic field that was recorded when the controller was aligned with the calibration mat as the "indentity" entry. For example here is mine:
"X": "-0.389402121",
"Y": "0.914950252",
"Z": "-0.105981141"

You can manually compute this direction if you know the yaw and pitch of the identity direction:
x = cos(yaw)*cos(pitch)
y = sin(pitch)
z = sin(yaw)*cos(pitch)

Conversely if you want to get the yaw and pitch of your current magnetometer direction:
pitch = asin(y)
yaw = acos(x / cos(pitch))

It would be pretty easy to add a function to the controller config panel to let you tweak the yaw so that you don't have to do this manual trig.


[SPARK-39392][SQL][3.3] Refine ANSI error messages for try_* function hints

What changes were proposed in this pull request?

Refine ANSI error messages and remove 'To return NULL instead'.
This PR is a backport of https://github.com/apache/spark/pull/36780 from master
Why are the changes needed?

Improve error messaging for ANSI mode since the user may not even aware that query was returning NULLs.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Unit tests

Can one of the admins verify this patch?

+1, LGTM. Merging to 3.3.
Thank you, @vli-databricks and @HyukjinKwon for review.


[feature] Load MRAOs

I already have everything implemented for using MRAO textures, however the material loading code currently doesnt populate the fields in the material
They'll probably be stored along with any future PBR maps in materials/vistrace

Added in 4269232b69168d69539e8fe2a7ac7937a538f701


.json updates

fixes old lock files

that's not how to use package lock files. package lock files are there to record the working state while features were added or changes were made. If you ask me lock files should never be recommited unless dependecies are changed or nested dependency versions are being changed because of fixing security issues.
Yes, the version specified in the package json files changed but that's not changing anything about the dependencies and the version is not being used for npm publishing anyway.


Test that zcashd and Zebra can sync from Zebra

Once we've merged GetBlocks and GetHeaders support #1347 , Zebra should be able to serve blocks to other nodes.
We should test that zcashd and Zebra can sync from genesis, using a fully synced Zebra.
This is a network integration test, so its out of scope for the first alpha. But it would be nice to make sure there isn't any really bad behaviour.

@ZcashFoundation/zebra-team  has anyone tried this already?

This would be a useful test, but it's partly covered by our other tests.


[SPARK-10825][Core][Tests]Fix race conditions in StandaloneDynamicAllocationSuite

Fix the following issues in StandaloneDynamicAllocationSuite:

It should not assume master and workers start in order
It should not assume master and workers get ready at once
It should not assume the application is already registered with master after creating SparkContext
It should not access Master.app which is not thread safe

The changes includes:

Use eventually to wait until master and workers are ready to fix 1 and 2
Use eventually  to wait until the application is registered with master to fix 3
Use askWithRetry[MasterStateResponse](RequestMasterState) to get the application info to fix 4

Merged build triggered.

Merged build started.

I will send a new PR to include #6457 and #8905 once this one gets merged.

/cc @andrewor14 since you wrote the original codes.

Test build #43005 has started for   PR 8914 at commit e6657e9.

Merged build triggered.

Merged build started.

Test build #43006 has started for   PR 8914 at commit 89e72fb.

Test build #43005 has finished for   PR 8914 at commit e6657e9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43005/
Test PASSed.

Test build #43006 has finished for   PR 8914 at commit 89e72fb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43006/
Test PASSed.

Merged build triggered.

Merged build started.

Test build #43026 has started for   PR 8914 at commit d06d476.

Test build #43026 has finished for   PR 8914 at commit d06d476.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43026/
Test PASSed.

LGTM but Andrew should take a look. I looked at this code recently and really found it odd that it expected things to just be updated "atomically", so good thing I was not crazy.

Thanks for fixing this! I'm surprised that it hasn't been flaky until recently. It must be due to the increase on Jenkins load. Merged into master and 1.5.


Chemkin compatible interface

Would you consider to provide a Chemkin compatible routine to compute the species production rates.

Hi, we're currently in the process of a rewrite to exploit SIMD/SIMT parallelism on both the CPU/GPU.  We would welcome a pull request for a Chemkin wrapper for species production (and potentially even the Jacobian) but it is not a priority right now

I will create a PR with the wrapper.
Talking about your optimization effort. Any plans to support vector (for multiple thermodynamic states) evaluations? This could help to improve the vectorization cache line utilization. That's what I do in my hand-tuned kernels (which is about 2x faster than pyJac).

Yes, we are specifically targeting:
A) a 'deep' implementation in which the evaluation of the species rates / jacobian will be vectorized for a single state (e.g., evaluation of multiple species rates in vector form) and
B) a 'wide' implementation, that vectorizes species rates / jacobian evaluation across multiple states (as you mention)
This vectorized version will also be sparse (to improve factorization) and will target both the CPU and GPU

@stgeke we are still working on this; if you are interested in updates on the project, please join the SLACKHA (larger project that includes pyJac) users' group: https://groups.io/g/slackha-users


[gRPC] Missing generated code

In the section Generated C# assets, the generated code for server-side gRPC is missing.

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

ID: 7223e694-85ba-4b95-96c8-68ae14753e7c
Version Independent ID: 28ec8399-ba0e-c995-3ac2-b1f28e93331b
Content: gRPC services with C#
Content Source: aspnetcore/grpc/basics.md
Product: aspnet-core
GitHub Login: @JunTaoLuo
Microsoft Alias: johluo

Thanks @psmorandi ... I'll see about getting that code back in there.


Windows?

Please offer an alternative or workaround to get this running on Windows?

tmate has unfortunately no support for windows.

Closed due its not in the scope of this project

Hey @maximveksler.
FYI: I've released version 2 which will skip Windows by default.a


libzmq 4.3.5 removed proxy_steerable for license reasons

@minrk FYI proxy_steerable has been re-added, before the latest release


[UIST] Update: Replace Base Template Id with Merge Id

We replace a Field for Base Template ID wit a Merge ID. This is only one correction.

Can be still changed incompatible without updating the format version


MLflow backed MLCatalog

This patch is continue from https://github.com/eto-ai/rikai/pull/346

This patch contains a slightly hacked Mlflow Java client, because the official java client doesn't support DELETE with body in HTTP, which Python client support and needed in rest API https://www.mlflow.org/docs/1.21.0/rest-api.html#delete-registeredmodel
Mlflow has more concepts than our current trait Catalog, like versions and stages, if Mlflow would be the de facto standard in the future, maybe we need to add those in trait. Currently, it only picks the latest version in all stages.
Filter by ArtifactPathKey temporarily disabled because we need apply https://github.com/eto-ai/rikai/pull/351 first.

Tips: use make fix to do formatting.

I found some errors in the tests can be fixed by a longer limit time in my local machine. And CI shows the different error logs from my local computer, adding more commits for testing.

R API has the impl of delete registered model: https://github.com/mlflow/mlflow/pull/4483


Windows LspInstall clangd not working

When i try to install clangd server with LspInstall clangd it doesn't finish installing never and after restart neovim it lsp says that the exe is not executable.
After LspInstall clangd command:
Pending servers (1)
◍ clangd (running) PS D:\Code\Configurations\nvim\nvim-data\lsp_servers\clangd>
Never change ^
Config: clangd
filetypes:         c, cpp, objc, objcpp
root directory:    D:\Code
cmd:               D:\Code\Configurations\nvim\nvim-data\lsp_servers\clangd\clangd
cmd is executable: Unable to find executable. Please check your path and ensure the server is installed
autostart:         true
custom handlers:

It worked after changing this default_options to this executable path:
default_options = {
cmd = { path.concat { root_dir, "clangd_12.0.1/bin/clangd" } },
},

Hey! This seems to be an issue when creating the symlink, the callback is never called so the installer hangs. When you restart neovim (or launch a new instance) it'll think clangd was successfully installed because the directory exists - but the cmd will be pointing to a symlink that was never created.
I think I found a fix for it, could you try the windows-clangd branch?

it worked! Thank you!


Feature configurable cql logging

contains updates to facilitate turning CQL debug logging on and off via a new 'cql.debugLogging.enabled' property in hapi.properties.
also added a logger config to logback.xml to turn DEBUG logging on for org.opencds.cqf.cql.engine.debug.DebugUtilities, the class that's responsible for writing CQL debug logs (this simplifies configuration by not requiring modifications to both hapi.properties and logback.xml when CQL debug logging is desired, now it only needs to be adjusted in one place).

Hi Matt! Thanks so much for the contribution. This is something folks have asked for for a while. I merged your commits, and made a small change to the property name:
hapi.fhir.cql_logging_enabled=false
That naming pattern makes it slightly easier to promote to the upstream HAPI server since they have their own naming convention.

Documentation for the logging setting:
https://github.com/DBCG/cqf-ruler/wiki/Deployment#cql-logging


WIP (DO NOT CHECK IN) ISSUE-4934: Local dependency cache validation

Signed-off-by: Bill Lin<EMAIL_ADDRESS>Context
https://github.com/gradle/gradle/issues/4934
Design doc in #osp-linkedin slack channel.
This is a WIP. I still need to do some code cleanup + add unit tests. Currently all existing tests pass for ./gradlew :dependencyManagement:check.
Added local file last modified + file size to CachedItem.
Refactored by creating AbstractCachedItem and removed fields from DefaultCachedExternalResource and DefaultCachedArtifact in order to reduce code duplication
Added checks to make sure that local file last modified + file size match with what is specified in the cache metadata
Because we are adding fields to the metadata, I bumped the metadata cache version
Contributor Checklist

[ ] Review Contribution Guidelines
[ ] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[ ] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

Hey @bslin, you can create drafts now for changes that shouldn't be merged yet: https://github.blog/2019-02-14-introducing-draft-pull-requests :)

@ljacomet is this something we're still interested in?  If not, I think we should close it.

Closing as this is not something planned right now. In addition it would need way more work before being merged.


feat: useDataProvider hook (alternative)

As an alternative to #1910, this implements a hook that returns a data provider function that can be passed to the grid:
const { dataProvider } = useDataProvider(MyListService);

<Grid dataProvider={dataProvider} />

It supports the same filter + refresh functionality as the implementation in #1910. In order to make this work, the hook returns a new data provider function reference when the filter changes or refresh is called, which in turn causes grid to reload.
This also requires making some changes to the data provider implementation itself, as it currently requires the grid element for a number of features. In order to remove the grid reference the following changes were necessary:

The infinite data provider now uses its cached filtered count instead of the grid's cache size for detecting whether to shrink the size or not. Those values should be equivalent, as long as reset is called on the data provider whenever the grid should be reloaded or the filter changes.
Removed the refresh functionality from the data provider itself. Instead, whatever uses the data provider needs to both reset the data provider and trigger a reload of the grid.
Removed the automatic reload of the grid when the filter changes in the data provider. Instead, whatever uses the data provider needs to both update the filter in the data provider and then trigger a reload of the grid.

The last two points don't concern developers really, as these automatisms are provided by AutoGrid and useDataProvider.
The hook is currently lacking test coverage which needs to be added to finalize the PR.

Thanks @sissbruecker for this alternative implementation. IMO, both the usage and the implementation are more conventional this way. The refactoring done for removing the dependency of the DataProvider on the Grid makes it more clear and less coupled. I'm in favor of this implementation the one suggested in #1910.


Bug fixes for Network resources and add find method for Network Storage

Closes #64, I dont think anything else should be needed at this point.

Coverage remained the same at 99.76% when pulling 87ced5cc5168c67f5ffe390a63cad892e0d82f1b on ju2wheels:sl_pw_man_find_mod into 0bb0f073110338a859d48185b03de67b21bd6291 on softlayer:master.


Preview (and the jpg endpoint) doesn't work in the new webui at some resolutions.

After firmware upgrade <IP_ADDRESS> lite -> <IP_ADDRESS> lite
For example:
2592x1944@20fps at both profiles works
2560x1440@20fps at both profiles doesn't work
2560x1440@25fps at 4M profile doesn't work (5M profile doesn't support 25fps at any resolution)
Preview doesn't work

And the error for the image.jpg endpoint after authorization is: "500 Internal Server Error".
At the same time, video0/1  feeds are working.
So, it looks like webui and/or the jpeg engine doesn't like the resolution. [that had worked before I made the upgrade and officially fits this camera model]
ISP: doesn't matter - any for IMX355 (in the new webui there are just 2 profiles for IMX355).
But, the bug doesn't seem to be dependent on either the camera model or the ISP profile.
The hardware: gk7205v300 (gk7205v200 family), imx335, 16 MB nor flash, <IP_ADDRESS>-lite, openipc-gk7205v300

500 error means that underlying hardware doesn't respond to the request
Please check streamer logs while you're making a request

500 error means that underlying hardware doesn't respond to the request
Please check streamer logs while you're making a request

How do I switch on the debug log in the new webui? There is no "Majestic > Majestic Debugging" as mentioned in the FAQ. And there are no *.log files in /var/log/, including subfolders.
p.s. requests to video endpoints works well, as I mentioned earlier... (from VLC for example, authorized through login+pwd in url)

Updated to <IP_ADDRESS> lite, problem still here.


[#174576563] Add ZNS support to swift resolution library

ready for review

@DeRain please review it again


segmentation fault at make_msa.sh

So I have been trying for a while now to get RoseTTAFold to work with no actual success besides a 20 amino acid peptide that I tried just for the sake of trouble shooting my current issue.
The error I'm getting with both run scripts (e2e and pyrosetta) is this :
"line 26: 869232 Segmentation fault      (core dumped) $HHBLITS -i $prev_a3m -oa3m $tmp_dir/t000_.$e.a3m -e $e -v 2"
I tried using both the conda static hhblits and a binary of hhblits I compiled from source as suggested in the github and got the same issue in both cases. I tried changing the available number of threads from 1-8 and that didn't affect as well as the max available number of ram from 4-500 GB (again with the same error recurring). Ran an md5sum on both the bfd and uniref databases only to verify that they're accurate and they are indeed correct. Important to note here - this issue only happens when I query the bfd database and not the uniref one, so apparently size of the db might be an issue here. Tried different values of -maxres including 15000, 2000,1500,500 and 50 which lead to another set of issues in the lower numbers and segfaulted as described for 2000 and 15000.
I have a commercial lic. of pyrosetta and it works flawlessly in any other task so I don't think its a licensing issue either.
I've also tried reversing the order of the values in line 26 of make_msa.sh and that didn't help either, so I truly have no idea why this is happening. Please advise,

So I have been trying for a while now to get RoseTTAFold to work with no actual success besides a 20 amino acid peptide that I tried just for the sake of trouble shooting my current issue. The error I'm getting with both run scripts (e2e and pyrosetta) is this : "line 26: 869232 Segmentation fault (core dumped) $HHBLITS -i $prev_a3m -oa3m $tmp_dir/t000_.$e.a3m -e $e -v 2" I tried using both the conda static hhblits and a binary of hhblits I compiled from source as suggested in the github and got the same issue in both cases. I tried changing the available number of threads from 1-8 and that didn't affect as well as the max available number of ram from 4-500 GB (again with the same error recurring). Ran an md5sum on both the bfd and uniref databases only to verify that they're accurate and they are indeed correct. Important to note here - this issue only happens when I query the bfd database and not the uniref one, so apparently size of the db might be an issue here. Tried different values of -maxres including 15000, 2000,1500,500 and 50 which lead to another set of issues in the lower numbers and segfaulted as described for 2000 and 15000. I have a commercial lic. of pyrosetta and it works flawlessly in any other task so I don't think its a licensing issue either. I've also tried reversing the order of the values in line 26 of make_msa.sh and that didn't help either, so I truly have no idea why this is happening. Please advise,
@yoavatsmonraz Have you solved the problem? I think I'm having the same problem as you, thanks in advance for your advice

I got the same problem. Wish there were any solution.

I got the same problem. Wish there were any solution.

have you resolve？ I got the same thing，always core dump


Any helpful scripts in any language

Any scripts made by you or used by you on linux

I would like to work on this issue

Go on @Srinjoycode


How to give padding between bars and can make it scrollable?

Hi,
Thank for creating this library.
Is there anyway to give padding between bars? Also If I can make this chart scrollable.
There is an issue when I have large number of data to show then all the bars get overlapped each other.

Hello,
You are welcome,
The bars are added inside a LinearLayout by weight, each bar frame will have 1 as a weight,
So this feature isn't supported, you can sure send me a PR and we will see.
Also i don't think a mobile app should have a chart with a lot of bars, you can use a Spinner for example.
Thank you

Use Horizontal scroll view than implement this chart it scrollbar :)


Testerina is not reading config files

Description:
Original issue : https://github.com/ballerina-lang/testerina/issues/162
Steps to reproduce:
Affected Versions:
0.962
Related Issues (optional):
https://github.com/ballerina-lang/testerina/issues/162

This issue is fixed in the latest master, hence closing this issue.


[useMediaQuery] Iframe support

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
When using react-frame-component to render useMediaQuery in an iframe, the media query is relative to the parent window, not the nested frame.
Expected Behavior 🤔
It should be possible to use the component with the contentWindow of the iframe.
Steps to Reproduce 🕹

Steps:

Open /docs/src/pages/components/app-bar/BottomAppBar.tsx
Edit it the demo with:

import React from 'react';
import useMediaQuery from '@material-ui/core/useMediaQuery';

export default function SimpleMediaQuery(props) {
  const matches = useMediaQuery('(min-width:600px)');

  return {`(min-width:600px) matches: ${matches}`};
}

Open the page (http://<IP_ADDRESS>:3000/components/app-bar) and resize the window to 700px.
It shouldn't match.

Context 🔦
The issue was first reported by @siriwatknp on Twitter.
Your Environment 🌎

Tech
Version

Material-UI
v4.7.1

I believe we could solve the problem with:
diff --git a/docs/src/pages/components/use-media-query/use-media-query.md b/docs/src/pages/components/use-media-query/use-media-query.md
index 51f68bca3..dd06c96c9 100644
--- a/docs/src/pages/components/use-media-query/use-media-query.md
+++ b/docs/src/pages/components/use-media-query/use-media-query.md
@@ -162,12 +162,13 @@ You can reproduce the same behavior with a `useWidth` hook:
   - `options.defaultMatches` (*Boolean* [optional]):
   As `window.matchMedia()` is unavailable on the server,
   we return a default matches during the first mount. The default value is `false`.
+  - `options.matchMedia` (*Function* [optional]) You can provide your own implementation of *matchMedia*. This especially useful for handling an iframe content window.
   - `options.noSsr` (*Boolean* [optional]): Defaults to `false`.
   In order to perform the server-side rendering reconciliation, it needs to render twice.

   This double pass rendering cycle comes with a drawback. It's slower.
   You can set this flag to `true` if you are **not doing server-side rendering**.
-  - `options.ssrMatchMedia` (*Function* [optional]) You can provide your own implementation of *matchMedia*. This especially useful for [server-side rendering support](#server-side-rendering).
+  - `options.ssrMatchMedia` (*Function* [optional]) You can provide your own implementation of *matchMedia* in a [server-side rendering context](#server-side-rendering).

 Note: You can change the default options using the [`default props`](/customization/globals/#default-props) feature of the theme with the `MuiUseMediaQuery` key.

diff --git a/packages/material-ui/src/useMediaQuery/useMediaQuery.js b/packages/material-ui/src/useMediaQuery/useMediaQuery.js
index e969caa2f..b17054efe 100644
--- a/packages/material-ui/src/useMediaQuery/useMediaQuery.js
+++ b/packages/material-ui/src/useMediaQuery/useMediaQuery.js
@@ -34,14 +34,19 @@ function useMediaQuery(queryInput, options = {}) {
   const supportMatchMedia =
     typeof window !== 'undefined' && typeof window.matchMedia !== 'undefined';

-  const { defaultMatches = false, noSsr = false, ssrMatchMedia = null } = {
+  const {
+    defaultMatches = false,
+    matchMedia = supportMatchMedia ? window.matchMedia : null,
+    noSsr = false,
+    ssrMatchMedia = null,
+  } = {
     ...props,
     ...options,
   };

   const [match, setMatch] = React.useState(() => {
     if ((hydrationCompleted || noSsr) && supportMatchMedia) {
-      return window.matchMedia(query).matches;
+      return matchMedia(query).matches;
     }
     if (ssrMatchMedia) {
       return ssrMatchMedia(query).matches;
@@ -60,7 +65,7 @@ function useMediaQuery(queryInput, options = {}) {
       return undefined;
     }

-    const queryList = window.matchMedia(query);
+    const queryList = matchMedia(query);
     const updateMatch = () => {
       // Workaround Safari wrong implementation of matchMedia
       // TODO can we remove it?

So people can use it like this:
import React from 'react';
import useMediaQuery from '@material-ui/core/useMediaQuery';

export default function SimpleMediaQuery(props) {
  console.log('props.window.matchMedia');
  const matches = useMediaQuery('(min-width:600px)', { matchMedia: props.window().matchMedia });

  return {`(min-width:600px) matches: ${matches}`};
}

Sounds good, will send PR soon.

@siriwatknp Thanks :)


def keyword(func: Any = None) is broken in Python 3.11.

there is something strange happening with Python 3.11 and type hints and auto conversion.
When you have a Type Hint Any  and default Value is None  in 3.11 'none' is always converted to None while in 3.10. it stays a string.
Given that Test:
*** Settings ***
Library    mylib.py

*** Test Cases ***
Test
    Myfunc    none    none

Test 2
    Myfunc    Hello    Hello

And That Library
from typing import Any, Optional, Union

def myfunc(value, assertion_expected: Any = None):
    assert value == assertion_expected, (
        "Assertion failed: "
        f"{value} ({type(value)}) != {assertion_expected} ({type(assertion_expected)})"
    )

It fails in Python 3.11 and passes in 3.10
def myfunc(value, assertion_expected: Optional[Any] = None):
The Optional[Any] fixes it.
Also Libdoc behaves differently and only shows  as Type hint.

The root cause for this issue is pretty interesting. First some details about the conversion process:

Type Any has no converter.
None conversion works so that string NONE, case-insensitively, is converted to None object.
If conversion done based on a type hint fails, a type hint has no converter, or there's no type hint in the first place, Robot tries conversion based on possible default value.
Robot has special CombinedConverter for unions. It tries converters for each nested type separately. If a converter can handle the value, the converted value is returned. If a type doesn't have a converter, the value is returned as-is. If all types have a converter and they all fail, the whole CombinedConverter fails.
Prior to Python 3.11, typing.get_type_hints that we use for getting type information returned same info with arg: X = None and arg: Optional[X] = None. The latter is just syntactic sugar for arg: Union[X, None] = None.
With Python 3.11, arg: X = None has no special handling and typing.get_type_hints returns just X.

Taking the above into account, this is what happens with Python 3.10 when you use arg: Any = None:

The syntax is handled the same way as arg: Union[Any, None] = None.
CombinedConverter is used.
Any´ has no converter so ConbinedConverter` returns the used value as-is.
Conversion succeeded so the default value is not used for anything.

And this is what happens with Python 3.11:

The syntax isn't anymore considered same as using Union.
Conversions is done using Any directly.
Any has no converter so Robot look for default value.
None conversion converts string none to None object.

This issue makes it clear that conversion based on default values works differently when the type is a union compared to when there's just a single type:

If you use just arg: T = default and T has no converter, conversion is attempted based on the type of the default value.
If you use arg: Union[T, S] = default and T has no converter, the value is always used without conversion.

This inconsistency could be fixed so that CombinedConverter ignores types that don't have a converter. That would make the behavior with arg: Any = None consistent with different Python versions so that also older versions would work like Python 3.11. That would be a backwards incompatible change and thus not something we'd like to do in RF 6.1. I'm also not sure would that change be a good idea in general.
Another way to handle this inconsistency would be not looking at default values at all if an argument has a type hint, regardless does that type have a converter or not. Also this would make the behavior with  arg: Any = None consistent, but now Python 3.11 would work the same way as older versions. I think that's a better solution than the earlier, but also it is backwards incompatible and thus not desirable in RF 6.1.
I believe the best way to handle this particular issue now is handling None as default value specially with Python 3.11+ so that it works the same way as with earlier Python versions. We could also consider not looking at default values at all if there's a type hint, but that requires a separate issue and a deprecation period.

Good thing with this issue is that changing arg: Any = None to arg: Optional[Any] = None, arg: Union[Any, None] = None or arg: Any|None = None (my favorite but requires Python 3.10) fixes the issue and works the same way with all Python versions. I thus don't consider this issue high priority. Needs to be fixed in RF 6.1. anyway.

Should we assign milestone 6.1?

Yeah, inconsistency in behavior with different Python versions can, and should, be fixed in 6.1. I already looked at that and it doesn't look too hard.
Inconsistency in conversion based on default values needs a separate issue and due to backwards incompatibility reasons needs to wait until RF 7. It also require deprecation latest in RF 6.2, preferably already in RF 6.1.

This ought to be fixed now. Needed to also take it into account that with arg: T = None we actually do None conversion, also with older Python versions, if T is a known type but conversion fails. For example, arg: list = None works that way and breaking it would be backwards incompatible.
As I wrote earlier, it probably would be best if we didn't look at default values at all if an argument has type information. That would obviously mean that behavior with the aforementioned arg: list = None would change, and thus the change could only be done in a major version and with a deprecation period. Users basically needed to change that syntax to arg: Union[list, None] = None or, if they use Python 3.10+, to arg: list|None = None. I personally don't like the former syntax too much and it also requires adding from typing import Union. Perhaps we should go with the current functionality now and think about this again later.


Links should open in webbrowser by default

Right now, if you click on a link in Dioxus Desktop, the webview will try to link within the webview. However, that's not at all how Dioxus apps should work: all external links should open in the web browser.

Closed by #133


Generate libraries instead of parts?

Just curious about the motivation for choosing generated parts instead of libraries.
For hand-written code I generally prefer using export to part.  It gets rid of all the ugly _s and allows one to import or export the sub-libraries elsewhere, such as tests.  Could then either import or export (or both) the generated lib depending on use case.

@seaneagan great question. The big reason: you can generate and access private "stuff".
For instance, you could access a private constructor for a json factory.
I'm absolutely game to add options for creating helper libraries, too. Just a matter of priority.

I also went with part of for my code generation because this is currently the only way to combine generated and hand-crafted code closely (private access) without worrying about overwriting hand-crafted code.
C# added partial classes exactly for this reason AFAIR which goes beyond part of, it would be nice to have in Dart as well.
Be able to choose is even better :)

We now have the isStandalone option to GeneratorBuilder which allows you to do this.


Docker updates for macOS High Sierra

Despite turning off automatic updates

Docker keeps telling me updates aren't available. It sends these warnings in pairs, and they don't even mention they are for Docker.

Can you make just one more update to fix the automatic updates feature so it doesn't check when the option is turned off? The pairs of system modal dialog boxes come up more than once a day.

You should be reporting this in https://github.com/docker/for-mac/issues. This repository is for the open source registry and it's related spec as described here

Created https://github.com/docker/for-mac/issues/4996
I'll close this one.


fix: unset the default value of totallimit

Signed-off-by: lowzj<EMAIL_ADDRESS>Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Could you please add more descriptions about why to submit this PR?

Codecov Report

Merging #1121 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #1121      +/-   ##
=========================================
- Coverage   47.23%   47.2%   -0.03%
=========================================
  Files         116     116
  Lines        7205    7204       -1
=========================================
- Hits         3403    3401       -2
  Misses       3535    3535
- Partials      267     268       +1

Impacted Files
Coverage Δ

dfget/config/config.go
89.41% <ø> (-0.13%)
:arrow_down:

supernode/daemon/mgr/scheduler/manager.go
21.91% <0%> (-0.69%)
:arrow_down:

Continue to review full report at Codecov.

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

The total limit is used to limit downloading speed of all the tasks on the same host. It's designed to be set by user explicitly, it should not be set by default. Otherwise it doesn't work if users only set flag locallimit but not set totallimit.

In fact, dfdaemon will set a default totalLimit value for dfget. Should it be deleted?

The total limit is used to limit downloading speed of all the tasks on the same host. It's designed to be set by user explicitly, it should not be set by default. Otherwise it doesn't work if users only set flag locallimit but not set totallimit.

In fact, dfdaemon will set a default totalLimit value for dfget. Should it be deleted?

It's unnecessary to delete it from dfdaemon. The dfdaemon is a specific usage scenario of dfget, it will start serval dfget processes at the same time when pulling an image, so the totallimit should be set. And the flag ratelimit of dfdaemon will set the totallimit and locallimit of dfget at the same time.

LGTM.


Outdated files in the dev-1.18-ko.1 branch

This is a Bug Report
Problem
Outdated files in the upstream/dev-1.18-ko.1 branch.
37 files to be modified

[ ] content/en/docs/concepts/architecture/nodes.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/concepts/cluster-administration/cluster-administration-overview.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/concepts/configuration/assign-pod-node.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/concepts/containers/container-lifecycle-hooks.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/concepts/containers/runtime-class.md 1 file changed, 17 insertions(+), 52 deletions(-)
[ ] content/en/docs/concepts/overview/working-with-objects/annotations.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/concepts/overview/working-with-objects/labels.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/concepts/overview/working-with-objects/names.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/concepts/services-networking/ingress.md 1 file changed, 79 insertions(+)
[ ] content/en/docs/concepts/services-networking/network-policies.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/concepts/services-networking/service.md 1 file changed, 11 insertions(+)
[ ] content/en/docs/concepts/storage/volume-pvc-datasource.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/concepts/storage/volumes.md 1 file changed, 5 insertions(+), 11 deletions(-)
[ ] content/en/docs/concepts/workloads/controllers/cron-jobs.md 1 file changed, 3 insertions(+), 8 deletions(-)
[ ] content/en/docs/concepts/workloads/controllers/deployment.md 1 file changed, 22 insertions(+), 22 deletions(-)
[ ] content/en/docs/concepts/workloads/pods/ephemeral-containers.md 1 file changed, 17 insertions(+), 36 deletions(-)
[ ] content/en/docs/concepts/workloads/pods/init-containers.md 1 file changed, 2 insertions(+), 2 deletions(-)
[ ] content/en/docs/concepts/workloads/pods/pod-topology-spread-constraints.md 1 file changed, 45 insertions(+), 6 deletions(-)
[ ] content/en/docs/home/_index.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/reference/_index.md 1 file changed, 3 insertions(+), 1 deletion(-)
[ ] content/en/docs/reference/glossary/kube-scheduler.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/reference/glossary/replication-controller.md 1 file changed, 11 insertions(+), 5 deletions(-)
[ ] content/en/docs/setup/_index.md 1 file changed, 1 insertion(+), 58 deletions(-)
[ ] content/en/docs/setup/learning-environment/minikube.md 1 file changed, 9 insertions(+), 7 deletions(-)
[ ] content/en/docs/setup/production-environment/container-runtimes.md 1 file changed, 36 insertions(+), 15 deletions(-)
[ ] content/en/docs/setup/production-environment/windows/user-guide-windows-containers.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/tasks/administer-cluster/cluster-management.md 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/docs/tasks/manage-kubernetes-objects/declarative-config.md 1 file changed, 23 insertions(+), 23 deletions(-)
[ ] content/en/docs/tasks/manage-kubernetes-objects/imperative-command.md 1 file changed, 3 insertions(+), 3 deletions(-)
[ ] content/en/docs/tasks/manage-kubernetes-objects/kustomization.md 1 file changed, 6 insertions(+)
[ ] content/en/docs/tasks/run-application/horizontal-pod-autoscale.md 1 file changed, 148 insertions(+)
[ ] content/en/docs/tasks/tools/install-minikube.md 1 file changed, 5 insertions(+), 5 deletions(-)
[ ] content/en/examples/application/deployment.yaml 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/examples/application/simple_deployment.yaml 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/examples/application/update_deployment.yaml 1 file changed, 1 insertion(+), 1 deletion(-)
[ ] content/en/examples/controllers/daemonset.yaml 1 file changed, 2 insertions(+)
[ ] content/en/examples/controllers/nginx-deployment.yaml 1 file changed, 1 insertion(+), 1 deletion(-)

1 files to be renamed

[ ] R098 content/en/docs/concepts/containers/container-environment-variables.md -> content/en/docs/concepts/containers/container-environment.md

1 files to be deleted

[ ] content/en/docs/setup/production-environment/windows/user-guide-windows-nodes.md

Proposed Solution
Use git diff to check what is changed in the upstream. And apply the upstream changes manually
to the content/ko of upstream/dev-1.18-ko.1 branch.
For example:
# checkout `upstream/dev-1.18-ko.1`
...
# check what is updated in the upstream
git diff upstream/dev-1.17-ko.7 upstream/dev-1.18-ko.1 -- content/en/docs/concepts/architecture/nodes.md
# apply changes to content/ko
vi content/ko/docs/concepts/architecture/nodes.md
...
# commit and push
...
# make PR to `upstream/dev-1.18-ko.1`

Pages to Update
/language ko

/assign

/close


Integrate advanced visualizations for Zeppelin/Scala/Spark using Netflix's Vegas-Viz OSS project

https://github.com/vegas-viz/Vegas

defer for nowz


Support backup/restore installation on hardened cluster

Support backup/restore installs on hardened cluster

This is a requirement for 2.6.

can be tested on rancher-backup:2.0.0+up2.0.0-rc2 in rancher:master-head

On master-head commit id: d44698d and backup version rancher-backup:2.0.0+up2.0.0-rc2

Able to deploy and take a backup on the local cluster - RKE1 which is hardened using this doc


[flutter_tools]  Reland: simplify pub cache logic

Description
There have been some more additional reports of a missing 'package:characters' import after upgrading flutter. This has me concerned that our pub caching logic is incorrect. Instead of the tool attempting to guess when pub should be run, always delegate to pub.
Also takes an opportunity to fix the kernel snapshot depending on the .packages or package_config. Due to the generated: date field this causes extra rebuilds. Instead when pub get is run, write out an additional file with just the package contents and version.
Fixes #66777
Fixes https://github.com/flutter/flutter/issues/65723

I failed to remove some .packages dependencies from the iOS rules. Re-added the ios build to presubmit

@jonahwilliams What broke with https://github.com/flutter/flutter/pull/67572?


Question about Reversal Curse Experiment

Appreciate the great work! I have two questions:

Is the ability to solve reversal curse an emergent ability as you scale up the MDM?
I am trying to replicate your result for reversal curse but I was originally referring to https://github.com/louaaron/Score-Entropy-Discrete-Diffusion for implementation. Not sure if you have referred to their code exactly but are you using the same implementation?

Thank you for your interest in our work!

We haven't conducted a systematic study on this issue, but a smaller MDM can still effectively break the reversal curse. I provide the results of MDM with 220M parameters as follows.

Our implementation is entirely different from SEDD. However, as a representative MDM, I believe SEDD can also break the reversal curse.

Thanks for the clarification! As a follow-up, could you briefly explain the difference between MDM and SEDD? I thought SEDD is the only implementation that allows diffusion model to be used for text generation. Could you guide me to any materials of MDM's foundation?

I recommend reading Section 2 of our paper. To the best of my knowledge, it offers the simplest introduction to masked diffusion models for text.
Regarding SEDD, it introduces a novel formulation for discrete diffusion models, distinguishing between two types: masked diffusion models and uniform diffusion models. Since masked diffusion models significantly outperform uniform diffusion models, we focus on the masked diffusion models.
Even though both SEDD and our models are masked diffusion models, we follow RADD and adopt a loss function that differs slightly from SEDD’s. The difference is as follows:

You can read SEDD, RADD, MDLM and our paper for more details about masked diffusion models.

Appreciate the thorough response!


[Navigation] isSkipHalfExpanded for bottomSheetNavigator

Description
jetpack compose version 1.2.0-alpha01 now has ModalBottomSheetState that has an isSkipHalfExpanded flag. It can be either set through the constructor or updated later on by setting ModalBottomSheetState's isSkipHalfExpanded property to true.
I need that feature in the accompanist with bottomSheetNavigator.
does someone working on it or in the near future plan it is to be done?

This issue should be re-opened


Release 0.19.0

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@ocefpaf @msarahan the linux build on CircleCI fails at end with:

Using Anaconda API: https://api.anaconda.org
Traceback (most recent call last):
  File "/feedstock_root/ci_support/upload_or_check_non_existence.py", line 124, in <module>
    main()
  File "/feedstock_root/ci_support/upload_or_check_non_existence.py", line 104, in main
    exists = built_distribution_already_exists(cli, meta, owner)
  File "/feedstock_root/ci_support/upload_or_check_non_existence.py", line 24, in built_distribution_already_exists
    fname = bldpkg_path(meta)
TypeError: bldpkg_path() missing 1 required positional argument: 'config'

./ci_support/run_docker_build.sh returned exit code 1

Is that something to worry about? (I would expect that it does not upload in any case on a PR, but it fails to upload on master as well, that is of course a problem)

I am traveling with limited internet but that looks the conda-inspect
failure. Just comment that test out until conda-forge updates to
conda-build 2.
On Oct 2, 2016 12:53 PM, "Joris Van den Bossche"<EMAIL_ADDRESS>wrote:

@ocefpaf https://github.com/ocefpaf @msarahan
https://github.com/msarahan the linux build on CircleCI fails at end
with:
Using Anaconda API: https://api.anaconda.org
Traceback (most recent call last):
File "/feedstock_root/ci_support/upload_or_check_non_existence.py", line 124, in
main()
File "/feedstock_root/ci_support/upload_or_check_non_existence.py", line 104, in main
exists = built_distribution_already_exists(cli, meta, owner)
File "/feedstock_root/ci_support/upload_or_check_non_existence.py", line 24, in built_distribution_already_exists
fname = bldpkg_path(meta)
TypeError: bldpkg_path() missing 1 required positional argument: 'config'
./ci_support/run_docker_build.sh returned exit code 1
Is that something to worry about? (I would expect that it does not upload
in any case on a PR, but it fails to upload on master as well, that is of
course a problem)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/conda-forge/pandas-feedstock/pull/9#issuecomment-250978188,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6BL5GRW28vB0bOYYsv3sYMBaC8k5-7ks5qv9NhgaJpZM4KMBZq
.

I did comment that out (before I got another error message related to the linking), but so now still an error message related to uploading

I'll be back next Tuesday and I can take a better look then  (only phone
and 3g until then).
Btw did you try rerendering? You'll need to install conda-smithy and type
'conda smithy rerender' from the feedstock root.
On Oct 2, 2016 1:43 PM, "Joris Van den Bossche"<EMAIL_ADDRESS>wrote:

I did comment that out (before I got another error message related to the
linking), but so now still an error message related to uploading
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/conda-forge/pandas-feedstock/pull/9#issuecomment-250980947,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6BL4zZwP71Q0EY1G2WF8sAuAb_HSjoks5qv98bgaJpZM4KMBZq
.

Aha, rerendering seems to do the trick. Thanks!

Awesome. Do you have merge rights? If not I can merge this for you.
On Oct 2, 2016 3:32 PM, "Joris Van den Bossche"<EMAIL_ADDRESS>wrote:
Aha, rerendering seems to do the trick. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/conda-forge/pandas-feedstock/pull/9#issuecomment-250986897,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6BL_pTFReeppjwCLM2cx30GmAYHlidks5qv_irgaJpZM4KMBZq
.


Detach last animation exported

Requested by @swift502
When there is no active action, after export, the last exported action is not removed from action editor

Yeah, I have many animations stacked in the NLA editor, but none attached to the skeleton itself.
Every time I export I have to detach the animation myself now.
Here's a video for clarification


conflict of name 'name'

dat.guiVR uses a function name() to set the label.
This conflicts with the pre-existing 'name' field in THREE objects.
This causes some issues, including breaking threejs inspector when inspecting dat.guiVR objects.
I suggest it be replaced by a get/set property 'label'; or (smaller change) renamed to 'label' or 'setName'.
I can't see an easy way to do this without breaking upward compatibility.

As I recall, this is not the only way in which dat.guiVR alters the properties of three objects, which could in general lead to issues like this emerging at unexpected times.
I somewhat considered refactoring so that the THREE objects would be members of the dat.guiVR objects, rather than changing them directly. I might still consider this, but I'm not sure how the original authors feel about it.

I would suggest using Object3D's userData instead.

The library also redefines add  function as well, for example, in a way that would break the similarity to regular dat.gui interface if it were changed.

I stumbled over both naming-conflicts while working with dat.guiVR, causing me some headache.
I'd prefer prioritizing threejs-compliance over maintaining datgui-similarity.

I agree threejs compliance might be more important than similarity to the other API, especially given they're unlikely to remain completely equivalent.
However, my proposed refactor would probably not take a massive amount of work to implement and would reduce the extent to which existing code using dat.guiVR was broken. Apart from the effort required to implement and test it, that might be the best of both worlds.


Building on mac

Good Day,
I couldn't get this to build on my Mac. I'm not experienced enough with Go so I'm sure its something I'm doing wrong. Here is a screenshot:

im having a problem and it is error 127

Hey there! Golang expects you to have the source in a specific path.
Try moving it to: $HOME/go/src/github.com/jhead/phantom
This doesn't happen with the new Go modules, but I haven't gotten around to using them yet.


cmd/vet/all: re-enable AIX checks

https://go-review.googlesource.com/c/go/+/138715/2 disabled aix/ppc64 vet checks.
This is a tracking bug to re-enable them before Go 1.12 ships with any AIX support.
/cc @trex58

Clément is in charge of the port of golang to AIX now.
/cc @Helflym


Improving the readme file

This is a(n):

[ ] Update to an existing Animated Button
[ ] Any Error
[ ] Proposal to the Repository
[x] Documentation / README.md changes

Details:

I would like to improve the readme file of this project and make it more expressive and engaging for the user.

I would like to work on this issue, assign this issue to me under GSSoC'23.

I would like to work on this issue. Kindly assign it to me...

@harshsingh32 You can work on this.
Just make separate PR for each of your contribution
@divyanshiet  Create another issue. I will assign it to you.
You can try making an animated button.
Make sure to ⭐ the repo and follow me.
I would love to connect with you all. ❤
https://www.linkedin.com/in/om-gawande/

@harshsingh32  are you working on this right now , if not I request @Spyware007  to please assign  me this Issue
as we are working in GSSOC event we need to change the readme file with relevant titles and links of GSSOC-23.
@Spyware007  can you look over it now ????

I am working on this issue, would update.

what changes are you making @harshsingh32

I would update and improve the readme and would provide you the update.

I have made pr #351 under this issue.


fp8 - renaming for SWAB recommend

gfx1201
[----------] Global test environment tear-down
[==========] 22565 tests from 13 test suites ran. (1353217 ms total)
[  PASSED  ] 22565 tests.
hipBLASLt version: 1000


Add cp/export/history/save integration test

Add cp/export/history/save integration test
Signed-off-by: Xian Chaobo<EMAIL_ADDRESS>

Test passes successfully and overall LGTM.
/cc @aluzzardi

Related to #492

@aluzzardi
Modified by the comments:  use checksum and exec -i

ping @aluzzardi

LGTM


improvement Support where, group by, having, order by clause without from clause in query statement

Proposed changes
Support where, group by, having, order by clause without from clause in query statement.
For example as following:
SELECT 1 AS a, COUNT(), SUM(2), AVG(1), RANK() OVER() AS w_rank
WHERE 1 = 1
GROUP BY a, w_rank
HAVING COUNT() IN (1, 2) AND w_rank = 1
ORDER BY a;
this will return result:
a|count(*)|sum(2)|avg(1)|w_rank|
-+--------+------+------+------+
1|       1|     2|   1.0|     1|

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

run buildall

run buildall

run buildall

this pr is removed to https://github.com/apache/doris/pull/27006, so close this


Nock match header regex

https://github.com/pgte/nock/blob/master/README.md#request-headers-matching, I really hope the second example in the readme is relying on automatic string -> number conversion or something otherwise I don't really know how this should be represented.

@Nemo157 thanks mate!


Added name properties to pre defined keymaps

cm.removeKeyMap(), as per documentation, depends on the name property of the active keymap in order to remove it if a string is passed as an argument. Most predefined keymaps did not have a name property, leading to unexpected behaviour.

cm.removeKeyMap(map: object)
Disable a keymap added with addKeyMap. Either pass in the key map object itself, or a string, which will be compared against the name property of the active key maps.

The keymaps in the distribution are meant to be used as base keymaps (the keyMap option). Using them with addKeyMap is probably not what you want.

Ok, I see.
So,  what would be the best way to enable and disable the sublime keymap, for example?

You probably want a select, not a checkbox, for choosing a base keymap. You can do editor.setOption("keymap", "default") to go back to the default map.


[Fix-11031] AccessToken can only be used by the creator.

Purpose of the pull request
AccessToken can only be used by the creator.
Brief change log
close #11031
Verify this pull request
Manually verified the change by testing locally.

Codecov Report

Merging #11032 (01dbb76) into dev (6bf80f7) will decrease coverage by 0.03%.
The diff coverage is 40.00%.

:exclamation: Current head 01dbb76 differs from pull request most recent head 8a948a1. Consider uploading reports for the commit 8a948a1 to get more accurate results

@@             Coverage Diff              @@
##                dev   #11032      +/-   ##
============================================
- Coverage     40.36%   40.32%   -0.04%
+ Complexity     4865     4864       -1
============================================
  Files           943      943
  Lines         37061    37068       +7
  Branches       4068     4071       +3
============================================
- Hits          14959    14949      -10
- Misses        20599    20610      +11
- Partials       1503     1509       +6

Impacted Files
Coverage Δ

...duler/api/service/impl/AccessTokenServiceImpl.java
78.65% <40.00%> (-10.38%)
:arrow_down:

...erver/master/processor/queue/TaskEventService.java
75.00% <0.00%> (-5.36%)
:arrow_down:

...dolphinscheduler/remote/future/ResponseFuture.java
81.96% <0.00%> (-1.64%)
:arrow_down:

...r/plugin/task/sqoop/parameter/SqoopParameters.java
53.33% <0.00%> (-1.34%)
:arrow_down:

...permission/ResourcePermissionCheckServiceImpl.java
66.66% <0.00%> (-0.78%)
:arrow_down:

...e/dolphinscheduler/remote/NettyRemotingClient.java
52.08% <0.00%> (-0.70%)
:arrow_down:

Continue to review full report at Codecov.

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


About the code and dataset

Dear author,
This is a wonderful work! And I want to ask when will you release the code and how can I get the dataset of style? Can you release the related code and dataset processing method about the 100STYLE?

Thanks for your attention! We will gradually release the code and the dataset within this week.


fixing the navbar UI

Currently, the navbar design doesn't look appealing. Please assign this issue to me, and I will update the navbar styling and UI to make it more user-friendly and interactive.
here is the S.S:

Assign under the HacktoberFest.

@Luson045 assign this issue to me under the hacktoberfest24.

issue #118 covers this @AnkitLuhar

@Luson045 okay let them finish ,afterwards if the work is not satisfied then,i will work on  the navbar ui under the  modern-aesthics.


How to start the cameraview again after stop?

When i stop the camera one time, and try to start it again,the cameraview can see notting with black background .  How can i start the cameraview again after stop?
Thank`s

I had the same problem and couldn't figure out why.  I tried invalidating/redrawing layouts but just couldn't get it to work. My work around for now is programmatically new up the CameraView each time - works pretty well. When you call camera.stop() make sure to call removeView(camera) on it's parent view.

Thank's eth0izzle.I also  resolution the problem with remove the cameraView befor stop it.


Apply script of automatic gh-pages deployment

DESC

e.g. use https://www.npmjs.com/package/gh-pages

TODOs

[x] create deployment script
[x] add in deployment script to npm scripts e.g. like 'deploy'
[x] document

implemented


phonopy projection

Dear Eugene:
I've read the code writen by you, jarvist/Julia-Phonons: Julia codes to play with Phonons (github.com), which is a really excellent work!

Here I have two problems:

I wonder if I want to compare atomic contributions at all irreducible points, is it necessary to normalize all atomic contributions?
atomiccontribution=[species[i]=>0.0 for i in 1:length(species)]
for i=1:NATOMS
atomiccontribution[atomnames[i]]+= norm(realeigenvector[i,:])
end
totallength=sum(values(atomiccontribution)) # Now weight every object
for contri in keys(atomiccontribution) # Surely a better way that iterating over?
atomiccontribution[contri]/=totallength
end
2.Does the weight of the q-point need to be considered? Although in most cases the weight is 1.
Looking for your suggestion！
Wish,
Xin Liu

Hi!
It was always a long term goal to support none Gamma-point modes, but (as you might have noticed) very little development has been done recently.

I suspect you can do the weighting after integrating over the Brillouin zone (iterating over q).
Yes, it should do - but as you've noted, the weights are usually quite simple. It will just be when you are on a symmetry line that you get a different weight, and if you turn off point group symmetry, this is just where f(k)=f(-k), so you can avoid it by using a Monkhorst-Pack grid which isn't commensurate with the boundary.

Good luck! Very happy to consider any push requests.

Hi,
Thank you very much for your reply, I have done this work initially based on your code. I am currently following your idea to implement it, which is to calculate the weight of each element at different points in the Brillouin zone, following the Gamma point algorithm. Then I followed a similar process in the way of the energy band element projection map. Surprisingly, the results obtained by this method are very similar to the results of the element distribution in the phonon spectral density of states map, and I'm not quite sure if I'm thinking correctly. If it's OK, I will compile my code and upload it to GitHub later, and I look forward to your reply!
Sincerely,
Xin Liu


Image not showing

I used that extension but after scroll Product images not showing, I am using SM-Market theme.

It was theme issue, fixed


pull request for e2e test at 12/14/2016 08:15:04

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


hit input type and weigh type runtimeerror while exporting onnx model

当代码执行到：pruner.export_model('model.pth', 'mask.pth', 'model.onnx', [1, 3, 224, 224])出错
RuntimeError: Input type (torch.FloatTensor) and weight type (torch.cuda.FloatTensor) should be the same

@205418367 thanks for reporting this issue. I guess you are exporting onnx file. This is a bug in export_model, which will be fixed in the next release.
In detail, https://github.com/microsoft/nni/blob/v1.3/src/sdk/pynni/nni/compression/torch/compressor.py#L252 , here, input_data should be put on the same device as your model. Could add input_data = input_data.to('cuda') below that line if you are using gpu.

The fix (add device argument in export_model) has been included in master branch and will be released in v1.4: https://github.com/microsoft/nni/blob/master/src/sdk/pynni/nni/compression/torch/compressor.py#L304


Slide prev/next transition is not working

In swiper directive after invoking nextSlide() or prevSlide() transition is not working.
What I noticed in source code that parameters are switched.
In swiper.directive.ts silent parameter is first parameter and speed is second
this.instance.slideNext(!silent, speed);
but according to the swiper spec speed should be first
mySwiper.slideNext(speed, runCallbacks);

So it seems that there is a small typo :) Thanks, will fix and release a new version.

Thanks :)


Improve handling of blueslip errors in our node tests

Ideally, in our node tests, we'd consistently have a setup where (1) any blueslip error that we aren't specifically looking for in a test crashes the test and (2) We have a clean way to declare specific blueslip errors that we're looking for in tests.
We have a version of that in some sense, in that by default blueslip isn't imported, so blueslip errors will crash, but we have several tests that check for specific blueslip errors, and do so in a way that sorta overrides blueslip for the rest of the test.
Might make sense to have a mock blueslip sorta like we have a mock jquery that we use in the node tests; not sure.
This issue requires significant skill working with our unit test system.

@zulipbot claim

WIP. On hold due to release blocker stuff.


Filtering results using summary.* returns a HTTP.Error

Weights and Biases version: 0.8.29
Python version: 3.7.3
Operating System: Linux

Description
I have been enjoying using Weight and Biases, and started using it daily!
However, I have bumped into some problems. After training a series of deep learning models, I am now trying to get one of the best results via python. Through this API (https://docs.wandb.com/library/reference/wandb_api#api`.), I figured I could use MongoDB to get one of the top results like this:
api = wandb.Api()
for batch_size in batch_size_list:
  runs = api.runs(
    path="my_entity/my_project",
    {'summary.train_loss': {'$lt': 0.01}, '$sort': {'summary.train_loss': 1}}
  )
...

However, I get this error message.
Traceback (most recent call last):
...
File "~/lib/python3.7/site-packages/wandb/apis/public.py", line 404, in __getitem__
  loaded = self._load_page()
File "~/lib/python3.7/site-packages/wandb/apis/public.py", line 397, in _load_page
  self.QUERY, variable_values=self.variables)
File "~/lib/python3.7/site-packages/wandb/retry.py", line 130, in wrapped_fn
  return retrier(*args, **kargs)
File "~/lib/python3.7/site-packages/wandb/retry.py", line 95, in __call__
  result = self._call_fn(*args, **kwargs)
File "~/lib/python3.7/site-packages/wandb/apis/public.py", line 91, in execute
  return self._client.execute(*args, **kwargs)
File "~/lib/python3.7/site-packages/gql/client.py", line 52, in execute
  result = self._get_result(document, *args, **kwargs)
File "~/lib/python3.7/site-packages/gql/client.py", line 60, in _get_result
  return self.transport.execute(document, *args, **kwargs)
File "~/lib/python3.7/site-packages/gql/transport/requests.py", line 39, in execute
  request.raise_for_status()
File "~/lib/python3.7/site-packages/requests/models.py", line 941, in raise_for_status
  raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://api.wandb.ai/graphq

I was expecting a list of runs with a train_loss that is less than 0.01 and is sorted in ascending order by train_loss. I was able to get a list of runs if I filtered it using config.*.
Is this an expected output? If so, it would be generous to change the error message to something more informational than requests.exception.HTTPError.
Thank you in advance, and hope if somebody can help me out!

I might have figured this out.
Instead of specifying the summary elements as summary.*, we might have to use summary_metrics.*. This to worked out for me.
However, this is different from the API document, so it would make sense to fix it.

Hi @sff1019, thanks for reporting this! @vanpelt could you take a look.

Hey @sff1019
In the past year we've majorly reworked the CLI and UI for Weights & Biases. We're closing issues older than 6 months. Please comment to reopen.


TypeScript integer enum objects can be assigned any integer value

I have enum as follows.
const enum Mode{
Add=1,
Edit=22
}
let currentMode:Mode=222222;
Above code is considered as valid code by compiler.

It should throw compile because it is directly assigned integer. It should enforce to assign Value as
let currentMode:Mode=Mode.Add; //Direct int should not be allowed

it should throw compile error because only allowed values should be 1 and 22.

Its Typed Script.

I understand why TS enums behave as above (They are not types). But the Typescript documentation says:

The other change is that enum types themselves effectively become a union of each enum member. While we haven’t discussed union types yet, all that you need to know is that with union enums, the type system is able to leverage the fact that it knows the exact set of values that exist in the enum itself. Because of that, TypeScript can catch silly bugs where we might be comparing values incorrectly. For example:
enum E {
    Foo,
    Bar,
}

function f(x: E) {
    if (x !== E.Foo || x !== E.Bar) {
        //             ~~~~~~~~~~~
        // Error! This condition will always return 'true' since the types 'E.Foo' and 'E.Bar' have no overlap.
    }
}
In that example, we first checked whether x was not E.Foo. If that check succeeds, then our || will short-circuit, and the body of the ‘if’ will run. However, if the check didn’t succeed, then x can only be E.Foo, so it doesn’t make sense to see whether it’s equal to E.Bar.

But running the following seems to contradict that.
enum E {
    Foo,
    Bar,
}

function f(x: E) {
    if (x !== E.Foo || x !== E.Bar) {
        // Error! This condition will always return 'true' since the types 'E.Foo' and 'E.Bar' have no overlap.
        console.log(`Is ${x} the sign of the apocalypse?`)
    }
}

let x: E
x = 666
f(x)

yes exactly, the whole idea of using enum getting failed here.
In case of string enums its not the case.
const enum Mode{
Add="Add1".
Edit="Edit1"
}
let currentMode:Mode="Add1"; // It will  fail
it enforce us to do
let currentMode:Mode=Mode.Add
which seems fair, why such enforcement is not added for integers. It supposed to be.

Duplicate #26362 and others; please search before logging new issues when the behavior you're describing has been present since TypeScript first shipped 7 years ago.


Return view after disconnecting from WiFi

returns to

Expectation would be to return to

Reported by Henri.

I've tested it, it works as expected in the current version.


[question]Is it possible to switch background image between dark mode or light mode?

Is it possible to switch background image between dark mode or light mode?

No as far as I know. Even setting a HEIC with dark mode support does not make any change.


Versioned S3 buckets leak keys

A left-over from #5551
$ python -Wall
Python 3.9.12 (main, Oct  8 2022, 00:52:50)
[Clang 14.0.0 (clang-14<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import gc
>>> from moto.s3.models import S3Backend
>>> s3 = S3Backend('us-west-1', '1234')
>>> s3.create_bucket('my-bucket','us-west-1')
<moto.s3.models.FakeBucket object at 0x104bb6520>
>>> s3.put_bucket_versioning('my-bucket', 'Enabled')
>>> s3.put_object('my-bucket','my-key', 'x')
<moto.s3.models.FakeKey object at 0x10340a1f0>
>>> s3.put_object('my-bucket','my-key', 'y')
<moto.s3.models.FakeKey object at 0x105c36970>
>>> s3.reset()
/Users/hannes/workspace/hca/azul/.venv/lib/python3.9/site-packages/moto/s3/models.py:347: ResourceWarning: S3 key was not disposed of in time
  warnings.warn("S3 key was not disposed of in time", ResourceWarning)
>>> gc.collect()
14311
>>>

Nice catch @hannes-ucsc


Fix case of overdetermined equality constraints

This PR to fix bugs relating to handling of active sets and equality constraints that would induce active sets that are not full rank, both in problem definitions and in subproblem solvers.
This does change the behavior of active set reporting when there is primal degeneracy, where as there are multiple active sets that can describe a point, then it will pick the one that is supported by the multipliers begin non-zero.

This fixes #30 and some resident problems in how active sets and equality constraints are structured in ppopt.


Use elasticnutch package instead of source Nutch

cc @chrismattmann - should be easier to run the example now.


GUIs do not work on blocks? (not sure if intentional)

Basically what the title says, item GUI does not work while using 'block start'. It works just fine while using 'NPC start' however. I'm wondering if this is intentional or I'm doing something wrong. If it is the latter, I will give some more info on my configuration, but if not I'll just close the issue.

This is intentional, although that could be an interesting option for the future.


FileNotFoundError: [Errno 2] No such file or directory: './data/YAGO3-10/vocab_e1'

While running the preprocess_num_lit.py, I got this error.
I couldn't find this file in the data folders, nor any script to create this file.
Can you please let me know how can I get this file?
Thanks,
Chandrahas

Hi,
Thanks for notifying us the error.
I've added step 3.2 in the readme, i.e. you need to run: python main_literal.py dataset {FB15k, FB15k-237, YAGO3-10} epochs 0 process True.
Please let us know if you encounter any other difficulties.

I also couldn't find this file in the data folders, nor any script to create this file.And when I run python main_literal.py dataset {FB15k, FB15k-237, YAGO3-10} epochs 0 process True.It occurs another error