Make Shpaml usable outside of Django

I'm making a simple static site now, and it would be great if I could write it in Shpaml and have a script to build the HTML. I don't want anything that requires a complex setup since this is a simple site. It would be nice if we had a solution for this. I saw there's a package shpaml on PyPI: https://pypi.python.org/pypi/shpaml But it seems to not have been updated for years, and there isn't a clear entry point to using it. In fact its "docs" don't mention at all how to use it.

Hi James,
Have you made a release with this feature?

v1.3.0 (as of today)

Thanks!
On Fri, Mar 6, 2015 at 7:18 PM, James Robert<EMAIL_ADDRESS>wrote:

Closed #14 https://github.com/Rootbuzz/shpaml/issues/14.
—
Reply to this email directly or view it on GitHub
https://github.com/Rootbuzz/shpaml/issues/14#event-247641353.


merge from arlac77/npm-package-template-esm-only

package.json

chore(package): add ^16.0.0 remove ^15.14.0 (devDependencies.semantic-release)

:tada: This PR is included in version 1.5.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Unable to use Metrics endpoint with HTTPS

Summary
TLDR;
Requesting the enabled /metrics endpoint via HTTPs seems not to work as expected
curl --user "klaus:password"  https://IP-of-remote-server:9090/metrics

resource name must be a SHA256 hash in hex. got '/metrics'
Details
Local
I've created a very simple local Bazel Remote Cache server with
docker run -u 1000:1000 -v $(pwd)/bzl-cache:/data -p 9090:8080 -p 9092:9092 buchgr/bazel-remote-cache --max_size 5 --enable_endpoint_metrics

and can request the data of the /status and /metrics endpoints with
curl <IP_ADDRESS>:8080/status
curl <IP_ADDRESS>:8080/metrics

{
 "CurrSize": 127442944,
 "UncompressedSize": 312782848,
 "ReservedSize": 0,
 "MaxSize":<PHONE_NUMBER>,
 "NumFiles": 74,
 "ServerTime":<PHONE_NUMBER>,
 "GitCommit": "dc4aeace0af5b893c96bd994a816dfbaba9b18c2",
 "NumGoroutines": 10
}

# HELP bazel_remote_azblob_cache_hits The total number of azblob backend cache hits
# TYPE bazel_remote_azblob_cache_hits counter
bazel_remote_azblob_cache_hits 0
...
promhttp_metric_handler_requests_total{code="500"} 0
promhttp_metric_handler_requests_total{code="503"} 0

nice, as expected :partying_face:
Remote
After that I've used a real server with HTTPs (of course) and a Docker compose file.
version: '3.6'

services:
  bazel-cache:
    image: buchgr/bazel-remote-cache:latest
    container_name: bazel-remote-cache
    restart: always
    volumes:
    - /volumes/bazel/cache:/data
    - /volumes/bazel/config/htpasswd:/etc/bazel-remote/htpasswd
    - /etc/letsencrypt/fullchain.cer:/etc/bazel-remote/server_cert # need all.pem because it doesn't have an option for intermediates
    - /etc/letsencrypt/*.xxx.key:/etc/bazel-remote/server_key
    ports:
    - 9090:8080
    - 9092:9092
    # - 6060:6060 # for pprof
    environment:
      BAZEL_REMOTE_TLS_CERT_FILE: /etc/bazel-remote/server_cert
      BAZEL_REMOTE_TLS_KEY_FILE: /etc/bazel-remote/server_key
      BAZEL_REMOTE_GRPC_PORT: 9092
      BAZEL_REMOTE_HTPASSWD_FILE: /etc/bazel-remote/htpasswd
      BAZEL_REMOTE_DIR: /data
      BAZEL_REMOTE_MAX_SIZE: 480
      BAZEL_REMOTE_ENABLE_ENDPOINT_METRICS: 1
      # BAZEL_REMOTE_PROFILE_ADDRESS: :6060
    logging:
      driver: "json-file"
      options:
        max-size: "500m"

With that up an running, I requested the data of the two endpoints again
curl https://IP-of-remote-server:9090/status
curl https://IP-of-remote-server:9090/metrics

{
 "CurrSize":<PHONE_NUMBER>,
 "UncompressedSize":<PHONE_NUMBER>8,
 "ReservedSize": 0,
 "MaxSize":<PHONE_NUMBER>,
 "NumFiles": 271670,
 "ServerTime":<PHONE_NUMBER>,
 "GitCommit": "4855aff6edf290d75fb54cc7a3f0c9656f5075fa",
 "NumGoroutines": 10
}

resource name must be a SHA256 hash in hex. got '/metrics'
This feels like the cache server interpreted this endpoint like a request to it's content
From Bazel point of view everything is working as expected, the remote cache is used, filled with new data and so on.
Expectation
I would expect that either none of the two endpoins /status and /metrics is working or both, but not a mix of it.

Hi, thanks for the bug report.
I think this might actually turn out be a misconfiguration, but it's not great that bazel-remote doesn't give a good error message.
To help debug this, I added a few changes and uploaded a new docker image: log on startup whether or not endpoint metrics are enabled, and provide a 404 error when clients request /metrics and it is disabled. Could you try this out, and report back the Endpoint metrics: log line when running your test case?

I've pulled your recently published latest image, commented the BAZEL_REMOTE_ENABLE_ENDPOINT_METRICS: 1 out, restarted the bazel remote and got Endpoint metrics are not enabled on this server. as I requested /metrics, as expected :+1: , the /status endpoint still worked (as expected). The log reports confirms this with  bazel-remote-cache  | 2023/08/10 09:34:29 Endpoint metrics: disabled
I've then uncommented the  BAZEL_REMOTE_ENABLE_ENDPOINT_METRICS: 1 line again, to have it as mentioned above, restarted bazel remote again, requested the metrics and got bazel-remote-cache  | 2023/08/10 09:35:39 Endpoint metrics: enabled from the log, and the /metrics endpoint provided the metrics.
I've reverted everything back to have the system as before and saw that we did not use a pinned version of the buchgr/bazel-remote-cache:latest image, so I've pinned it to v2.4.1, started everything again and it worked :joy: I believe we used somehow a version that had a glitch or most likely a so old version that /metrics was just not there.
Sorry for the inconvenience, nevertheless the improved log output and report is really a benefit, thanks for that!

No problem :)


size function calls with one argument attempt to use the span .size() call

The way .size() is implemented is a hack, which results in calls like size(2) failing with OH NO MY TYPE rather than being unable to find the function. This is because it assumes the variable is a span and tries to get the inner type, which fails.

No longer a problem, member function lookup is done properly now and .size() has been replaced with len() anyway


Research Spike: Volar

Initial checklist

[X] I read the support docs
[X] I read the contributing guide
[X] I agree to follow the code of conduct
[X] I searched issues and couldn’t find anything (or linked relevant results below)

Problem
There is a fair amount of boilerplate code to integrate MDX, TypeScript, and the language server together.
This boilerplate may not be necessary with some abstraction.
Solution
Research Volar https://blog.vuejs.org/posts/volar-a-new-beginning.html
Formerly the vue language server, which has now split out it's abstractions for other language servers to use.

Volar.js is architected to support any file format that involves embedded languages - not just Vue, but also Astro, Svelte, or even Angular. It is also capable of implementing regular single-language LSP servers such as TypeScript, CSS, and HTML.
Another major focus of Volar.js is performance. It aims to minimize the overhead to achieve the performance of a native embedded language service. There are many issues and optimization opportunities that could only be discovered over time with a sizable user base, and Volar.js is optimized based on the learnings we have accumulated from millions of downloads.

The abstractions appear to center around low level details:

we abstract all the places you don't need to care about, such as virtual code mapping, formatting edits merge etc.

We may be able to rebase our server on top of that foundational work.
Alternatives
Volar is new, and may or may not suit vscode-mdx.
This is mostly an issue to explore feasibility and practicality of leveraging it.
If none of it matches, "we shouldn't use it", is a perfectly valid outcome.
Or a more piecemeal approach of leveraging concepts and reusing some functions could also be taken.

I recognize a lot of the ideas and troubles mentioned in that blog post. I’ll contact them and see if we can work together. :smile:

Released in<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>:tada:


Nub of rendering challenge

Given
  {{#eg-body}}
    {{my-component value="name"}}
  {{/eg-body}}

We need to render
    {{my-component value="name"}}

In the context of the individual row. So:

look up contents of "eg-body" for given column
render contents in a custom wrapper component

What is relevant "contents of 'eg-body'? The dom nodes aren't sufficient. What we really want is the template (template string)? The question is, is that available?

Yes that's the nub I was heading towards but you found the detail. Hmm...

Wonder if we can yield it in somehow. Set the render context to off screen then yield

In theory, layout of eg-body looks like
{{yield}}
anyway. The question will be, does instance of eg-body have a "template" attribute which we can simply assign to a dynamically created component whose purpose is to pass in the context to template.

Isn't this exactly what #each has to do?

Yes! It has layout property. See eg-body component def

#each has a static template... we have to do the same thing but dynamically. So can we do:
{{#ember-list as |column|}}
   {{display-cell tempate=column.cellTemplate}}
{{/ember-list}}

layout is for the wrapper, template is for the contents of the wrapper.

So task 1 is to write a little test w/
{{#x-foo}}
something
{{/x-foo}}
{{#ember-list as |foo|}}
{{render-it template=foo.template}}
{{#ember-list}}
... [will try it out -- now I'm being called away from the keyboard :)]

hmm... so in a block component, template is null, and layout contains an already compiled htmlbars structure, which itself just contains the "yield". Of course, the DOM is present, but to get back to the actual template we would need to reverse compile.
What we really want (or at least what I was thinking about) is an htmlbars block helper that would grab the unrendered template callback, and save it for us to call back once we have set up the context.
However, the interfaces to this were called private and unstable. I think that (e.g.) in eg-body we actually have to iterate over the data and pass it in. If necessary we can use ember-wormhole to rearrange the content. I'll tweak the readme slightly and try to get an example of this working.

Yes we definitely need it before rendering. How does #each do it? Isn't that doing the same thing, repeatedly rendering the same template with different injected data?

Gotcha.
Can't use block helpers any more so we have to use wormhole technique. Can't use wormhole as it requires an elementId. So I've used the same technique in eg-render/eg-header-cell and eg-render/eg-footer-cell. Works beautifully.
Default header is column.header. Default footer is column.footer.
Now we just need to get the body working. I suggest you do that as you know ember-collection better than me. I'll get header and footer rows looking nice and getting column resize to work.

#each -- I looked at the code and is pretty simple. It wouldn't be hard to copy. The problem is whenever they change the private APIs and #each breaks, they have to fix it. But they don't have to fix ember-grid.
I think we can use wormhole: we can create an id from row*column. And I think we have to to keep the current form, as if we keep the bodies inside the columns, they won't render in the right order.
This is my plan:

Render data fields in columns (with display = none)

Render a sheet of divs with ids

Both of the above with ember-collection.

Teleport the data fields into place with wormhole.
I naively believe that if a row*column doesn't exist in the destination grid, the wormhole will simply fail without bad side effects.

If you have a better idea tell me.. possibly we could leave as columns and render the whole as a column table, but it won't be what users would expect at least.

#each can't work. We can't do our own block helpers any more.
#wormhole can't work as we need unique ids - what happens if the user wants two tables?
I've used the same technique as wormhole, and made it work nicely for headers and footers (including fallback to default string)

take a look at the currently checked in code and see what you think.

A random string would do as a prefix ... but checking out the code now.

Ok .... yes that is good for headers and footers. We can move things around "relatively" rather than absolutely using parent. ... but that isn't the hard part with the body (unique ids per se aren't a problem): here body cells can render a column of fields, but we can't leave them like that -- for instance we need a scrollbar for whole sheet rather than one for each column, so we have to undertake more transformative surgery.
I didn't get as much done as I expected as we have guests, but will consider both techniques. Right now I'm just getting to the point where I have two structures: one with fields in columns, and another with an empty grid of rows & columns. I'll rebase based on your work before I continue --  no need for teleportation when normal transportation already works. Another part I haven't quite worked out yet is sequencing: I can't move elements into the grid before it exists.

Its gotten late and I didn't get done as much as I hoped as a few other things came up. I haven't merged body work yet. Just pushed version with your components in pod structure so we don't diverge too much. Tomorrow have "real work" until evening; hopefully can push something then. Thanks!

I think we should find a way to use ember container for the body. It's
huge and we shouldn't rewrite it.

ember-collection, you mean?

Ok -- have pushed a version -- shows body rendering. It is still quite buggy: I and ember-collection are both fiddling with contents dynamically and the interference shows. But illustrates the basic technique.

I've cleaned up jshint and simplified some of the structure.
Wondering if we can eliminate ember.run.next to speed up rendering

I'll see if I can get drag-resize headers next

Great -- I'll check it out. I've found a few bugs in ember-collection which might or might not help on scroll. (Still fixing now....) One more complex thing thing we need to get working is horizontal scroll if the columns push beyond the viewport. What is your npm username so I can add you as npm owner?

bcrotaz

(added in npm)

horiz scroll needs to be on all three zones, so ember-collection and hread and footer row should have min-width = sum(column widths) + borders

yes... I was also thinking of using ember-collection in definition with horizontal window so that we don't have to draw all the columns but only those that fit.
As for borders, I'm wondering if we can get away with leaving that to the user - just render the cells absolutely with no gaps. and let them style eg-cell-body (for example) and and/or whatever else the have actually rendered.

no, css is king here. we can query css params to see how much space to leave.  Take a look at ember-split-view in the minSize computed property.
Then the user can just use css to style and we use whatever they used.

yes -- very good. Btw perhaps its time to start adding tests? Seems like we have "proof of concept".

I think we need to prototype a couple more things first.
It's very slow to start up - all the run.next cycles - can we get involved in the rendering so it renders correctly first time?

One thing I'm going to try now is to eliminate the per-column ember-collections body definitions -- no need to use frame animation inside of display==None. Instead we should just render just a slice. ...but its already getting to have non-trivial complexity so lets at least try not to add too many more features before working on the tests.

That's weird - the divs in the collection are in reverse order/
Not at all sure what your latest comment means

made some nice progress. We need to think about how body cells are laid out - I think your method is about to hit a brick wall when we try and have the column know about styling to calc offsets. What's wrong with inline-block?

merging changes -- about to check in (so you can see what it means).
I thought about inline-block ... but if we really want to use ember-collection, it places everything absolutely and would be quite difficult to get around.
wrt to:
classNames: ['eg-body-cell'],

Can we make sure to namespace our css (it doesn't have to be eg-body-cell -- could be eg-cell for instance if you want.

wrt to  the divs in the collection are in reverse order/ -- there is a scrolling bug now. Problem is that ember-collection keeps a hash of elements -- not necessarily in order and then places them and tells them to render as needed. However, render for me means "take your content from the definition" and now if another cell has already taken it I'm stuck with the old content. I need to create another map.

wrt
classNames: ['cell']
nevermind... I guess thats ok.

My thinking is that we're namespaced within ember-grid and by using less we enforce that

Also wondering whether the grid should have two drawing modes. One for a normal table where columns are all visible and one spreadsheet style where a subset of cols are visible. Former doesn't need an ember-collection per row

Yes -- I decided that it was ok. The only thing is if user drops in a table inside something styled #my-div .cell { ... } but is easy to fix and OTOH convenient to use. Just I currently use selector to look up cell, and will add eg-body-cell as well.
WRT to css styling of cells. how do you want to do it? It seems to me that column.width has to govern here...?

You can look up cell with '.ember-grid .body .cell' or you can start find within body or row for speed

I've already set cell width from column width

Former doesn't need an ember-collection per row

The idea would 2 ember collections: one large one which ranges over whole including definitions and governs horizontal styling, and one internal one over rows which governs vertical scrolling. However, we could leave out the large one possibly -- lets get the vertical scrolling working and then consider.

I've already set cell width from column width

what do you see as the problem w/ absolute positioning?

I've bodged it quickly with a style binding but need to do it properly later to stay within CSP rules

ok -- but that isn't a problem with absolute position per se, right -- we need to do it right however? (btw you might have noticed I tossed in "unsafe-self" in dev to get rid of annoying reports)

The problem with absolute positioning is to bring in CSS padding margins and borders. CSS might be overridden in app. The way to do that is in the cell component. Maybe col width is just the content width of the column. Then the cell component adds on CSS widths

I thought of "eg-body-cell" as a wrapper around the "real cell" which is whatever the user wants it to be (and would be best target of css).

we could explicitly render a wrapper and also a cell perhaps, and use the cell for positioning?

Given the number of cells we ought to minimise dom complexity. And just do what is necessary.

I wonder if we should start with body rows using the same technique as header rows

In my branch here I've replaced the "hidden" ember-collections with simple slices (which helps with speed)... (no longer working after merge). Thus the body rows from the definition are in order. However, the ones from ember-collection are still an unordered map. Do you have something concrete in mind by " body rows using the same technique as header rows"?

btw -- does getting rid of run.next in "willInsertElement" actually work for you? I tried and got lots of warnings about modifying properties during render cycle.

I think it worked for header and footer but not body. I don't understand the glimmer life cycle yet.
By same as header, I mean a simple each...header-cell with inline-block positioning.
Worth speed testing?

I'll give inline-block a whirl ... let me get merged and at least push a branch so you can see what I'm doing at least. After that I want to dive in to this annoying scrolling problem. For me it already renders faster without the hidden ember-collections in the definitions.

Aha!

I'll start doing the draggable column boundaries

If we can get what we have plus resize columns then we just need tests for a first release

:)

ok -- pushed; now on to scrolling

default headers are broken. investigating

column resize worked first time. The architecture seems to be working.
You can mark a column as resizable: false

age is marked as not resizable in the dummy app

excellent -- pulled and had fund resizing. How is rendering speed for you now?

Much faster. But row ordering is completely broken and some rows have no data in them. Startup speed is slow (about 1 second on my machine to fully render)

Just got booked to do a talk on this component on 10th Sept at Ember London. There's some really interesting techniques in here.

Wow -- great!
I'm working on ordering now. VS startup speed perhaps we should try turning off rendering of display table until definitions have been processed.

Ordering I should be able to get working but won't be ideal. For further improvement make want to derive from ember-collection so we can take advantage of the same map it is using.

hmm. Can we not have a body-row component which deals with laying out the row so that ember-collection only deals with row ordering?

I have added and then deleted a body-row three times. :) ... it doesn't really help the situation. Currently ember-collection is already only dealing with row ordering. Just that it expects rows to "re-render" when it remaps, and as for me rerendering means taking DOM notes off the shelf from the definition, I also have to put them back on the shelf when I'm done with them -- that is what I'm working on now.

aha - they were dissappearing down the worm-plug-hole?

Yes -- and so the old contents is still there out of order.

I've implemented min and max column widths both in column def and in css. I'm going to make styling behave properly re CSP and then I think rendering rows is the only thing left

Speed-wise -- we'll see how it looks. It could be further improved if (a subclass of) ember-collection moved the nodes itself rather than asking for a rerender.

I wonder if having body-row makes your problem neater if not easier as it's a clean place to put the wormhole behaviour

I think slightly slow if fine for now - let's build tests once we have a v1 functionality. I'm amazed at how fast this has come together. Liking component-style building

right now I've got it pretty well encapsulated:
The definition cell is responsible for getting node:
getCellElement(rowIndex) {
  var element = this.element;
  if (element == null || element.childNodes == null) {
    return null;
  }
  var {'_body.offset': offset, '_body.limit': limit } = this.getProperties(
    '_body.offset', '_body.limit');
  if (rowIndex < offset || rowIndex >= offset + limit) { return null; }
  return element.getElementsByClassName('eg-body-cell')[rowIndex - offset];
},

The rendering cell asks for the contents and moves into place
didInsertElement: function() {
this._super.apply(this, arguments);
var source = this.get('column._zones.body.source');
var sourceElement = source.getCellElement(this.get('rowIndex'));
this.moveChildren(sourceElement, this.element);
},
moveChildren: function (source, target) {
if (source == null || target == null) { return; }
while (source.childNodes.length > 0) {
target.appendChild(source.childNodes[0]);
}
}

blue header is defined in dummy app styling to confirm that app can override styling

feels a bit dodgy that the definition cell is dealing with offsets and class names. shouldn't it just grab its entire block?

I'm sorry -- thats not the definition cell. Thats the definition body. Your right that I could break it into two steps -- definition body gets cell component, then cell component gets contents. But currently there is no cell component and as this would be the only logic in it its not so bad I think but can clean up if you like. However, first I have to finish up the "put the nodes back" code.

if you look at how I've done the header,
parentView.set('_column._zones.header.element', this.get('element'));

I'm just grabbing the whole element in the definition
Then eg-render/eg-header-cell moves its children:
  renderHeader: function() {
  	var header = this.get('_header');
  	if (header)
  	{
	    var sourceElement = header.element;
	    var destinationElement = this.get('element');
	    var node = sourceElement.firstChild;
	    var lastNode = sourceElement.lastChild;
	    while(node) {
	      destinationElement.insertBefore(node, null);
	      node = node !== lastNode ? lastNode.parentNode.firstChild : null;
	    }
	  }
  },

probably
moveChildren: function (source, target) {
if (source == null || target == null) { return; }
while (source.childNodes.length > 0) {
target.appendChild(source.childNodes[0]);
}

should be in a mixin as the header and footer could reuse the same code

(We would need to add a (say) eg-body/eg-cell ... marginal if you ask me)

mixin: +1

ok, let's review when you're done

ok -- there you go. header looks good.  Simplest way to fix would probably to draw the table a few rows larger than it was then put sentinels at top and bottom.

I'm also very surprised it works so well already. One ceveat is its pointing at my private copy of ember-collection, which has some bug fixes still sitting in a PR. Still very good -- I think you've done a great job filling out the architecture.
Take a look at what I've done. I can put in eg-render/body-row and/or  eg-body/eg-cell if you think its worthwhile.

btw -- should we remove eg-render components from app/ as they are not part of the public interface?

one small thing with header drag: how to resize last cell

I tried removing eg-render components, but then they're not found by the resolver. Would be nice to find a way around that.
I forgot about the last cell! Do you think the last cell should fill remaining space? That would make sense in a normal table view. min-width settings would work to make the next column collapse when it reached its limit.
Header resize also lags behind a little - much more than in ember-split-view. I'm not too concerned right now.

list-view had functionality for providing a scroll buffer either side of the visible window. Does ember-collection not have that?

scroll is broken with your new code. First page renders correctly, then nothing else as I scroll down

hmm.. not what I see... perhaps  -- can you pull the latest shaunc/ember-collection?

can you change package.json to point to the correct branch?

ah! I see - you've fixed ember-collection since I last npm installed.
npm updating...

buffer: it keeps a buffer of old nodes, but tells to rerender just as approaches screen. Arguably a bug.

and our rerender is slow?

I think its rather that ember executes the hooks with a lag

so it's already on screen when the hook kicks in?

yes -- exactly. Is it working for you now? (My son awaits my reading to him :)) Just pushed a small fix to give cells height.

scrolling slowly is fine after update, but fast scroll gives lots of empty rows

go and read!

:) -- leave any ideas -- back in an hour

(I may be able to fix this in ember-collection)

I would prefer that rowheight (& anything non interactive) was done in css. Way more efficient, and user can easily override.

hmm... well ember-collection needs rowheight to know how the rows fill out the space... will consider

we can read it from css? Look at minwidth of header cell to see how. Otherwise it's a grid property. No real problem with it being that, just css is nicer if possible.
Currently body cells are 1 px too narrow from col 2 onwards. Can't see why.

rowHeight -- to read from css we'll need a row to style. Maybe I can put an option in ember-collection to pass in a class name for the item wrapper.

Ah yes of course. Ok leave as is then

added alternate row colours and horiz align for default column layouts.
eg-body and eg-render/eg-body-cell differ in structure from equivalent header and footer. See which you think is best of the two. We should consolidate the design so it's the same everywhere.

do we still need column.offset?

I’ll take a look — busy today but have time in eve.

On Aug 19, 2015, at 1:51 AM, Bryan<EMAIL_ADDRESS>wrote:
added alternate row colours and horiz align for default column layouts.
eg-body and eg-render/eg-body-cell differ in structure from equivalent header and footer. See which you think is best of the two. We should consolidate the design so it's the same everywhere.
—
Reply to this email directly or view it on GitHub https://github.com/shaunc/ember-grid/issues/2#issuecomment-132393467.

I have committed a buffering fix to shaunc/ember-collection -- if you pull it should scroll better; we can tweak a little to improve this further now that buffering is working.  Haven't looked at our code yet today but will consider the architecture questions you brought up later on this eve.

:( Rendering still broken on scroll. On slow scroll it's fine, but scrolling fast results in empty rows.

:( for me too -- though I've been fooling with the parameters.  I'm beginning to worry that the requestAnimationFrame isn't (easily) compatible with our swapping out domain nodes. Still have a few more ideas but we may have to take closer control -- e.g. insuring that during scroll elements are rendered before they seen.

update -- even if I get rid of the slice in eg-body and render all the data (which hurts startup and isn't realistic for large datasets) its better but still not perfect. I'll check in this mode in a branch. If you think its ok, we might be able to approach this performance by filling out the buffer incrementally in the background.
If not, though, we'll have to take more direct control of rendering, perhaps explicitly instantiating elements in the buffer rather than letting animation simply call "rerender" for async rerender as its now done.

I've push something into the "slow-load" branch.
In it I've completely disabled slicing the original content rendering (hence the "slow-load"). I wanted to see how much of the problem is unavoidable with ember-collection, as we are ways to optimize the slicing.
On the front page in the slow-load branch is our table and below it a raw "ember-collection" table for comparison. You can see the ember-collection table also has flicker; with ours its certainly worse.
In console you can see log as it renders.  Even if the rows are long offscreen, they are still gumming up the queue.
If we are ok with the following, doing approximately the same with incremental slices of content wouldn't be too hard. What do you think?
I am leaning toward the thought that we may have to take over from ember-collection. If we could respond to scroll directly and move a whole chunk of rows at once (keeping in order) we'd be a lot better off than the current randomly ordered & absolutely placed, where even if you are already offscreen when you get control its hard to figure out what to do instead.

@BryanCrotaz My plan is currently to derive from ember-collection and override the updateCells method. Instead of just deciding which cells will display, and allowing rerender to lazily take care of it, I will greedily get the content from the body buffer.
Do you know how to include one addon from another? I am having trouble including the component so that I can extend from it.

when scroll happens, what do you get given in the args?
Don't know how to include an addon, but I'm about to add in a mixin from an addon so I'll hit the same problem

Currently, when scroll happens, ember-collection marks the "cells" property as changed, which triggers re-render. In "update-cells", ember reassigns which cells display what (from a map), updates their properties and re-renders them. The cell is an ember-collection place-holder, with underlying row & index as data elements, as well as style info for abs position ec uses it to render the block content:
{{~#each cells as |cell|~}}
  <div style={{{cell.style}}}>{{#unless cell.hidden}}{{yield cell.item cell.index }}{{/unless}}</div>
{{~/each~}}

So the row gets the data and index as args. However, the rerender is lazy and in fast scroll it will engage in rendering elements that have already scrolled by.
Instead I'd like to override updateCells to check the actual scrollTop currently, and copy the data in for the displayed slice immediately without waiting for re-render.
(I just had one more thought, though, before i do this -- perhaps I can get a PR into ec that at least reupdates offset given current scrollTop when the async rerender happens. May help to be only one async rerender away from current scroll rather than current two -- first for rerender of EC and 2nd for rerender of content cells.)

these issues do seem like generic ember-collection issues rather than specific to us

our part should be limited to deciding what to render in each row

They are difficult to deal with generically: generically, asking subcomponent to rerender is the best you can do. A few possible optimizations I could try to get into ember-collection:

Possibly you could also anticipate scroll by looking at several datapoints and try to calculate velocity, but that would be tricky to do well.

You could keep cells in an ordered ring rather than in a map. In this case, when we get a rerender in the row, we could decide -- "you asked me to rerender for row X but I know that row X has already scrolled off, and my position in the ring means I should really render row Y"

However, the former is tricky and bug-prone (and would be hard to get into official repo I think). The latter is really cheating anyway.
I will soon push another copy of my own EC -- see what you think. This will probably be the best we can do with limiting ourselves to

deciding what to render in each row

isn't the latter saying:

child cell is being reused so kick off a lazy rerender
when rerender comes around cell might have been repurposed so render the correct contents

Your update sounds about right. in slow scroll you're updating off screen rows. In fast scroll you're updating on screen rows so lazy is not important.

UPDATE and both of these feel like generic ember-collection issues

Ember collection will have a hard time doing better though. In our case if we know we need an immediate update we could do a low-level grab from the body-def buffers. Generically, an async rerender is only possibility.
My plan for this now is to create a new component -- "ember-scroll-ring" which uses the layout-bin-packer to allow virtual scroll of a fixed ring of divs, and allows user to register a callback to do something to an element when it appears or disappears. Then we (in this project) can concentrate on rerendering rows as you say, but we'd be able to do it synchronously with scroll (modulo having to render the body defs in the background).
However, I am currently going to leave this, and go on to cleanup, testing, and then data-driven columns.

cleanup - have you had a chance to compare your cell declaration/rendering with mine and choose which is best?
I'm looking at the best way to achieve CSP friendly styling - two addons to choose from which have a mixing to do it.
I have a dev here who's finishing up some low level Raspberry Pi stuff, then I'll put him onto writing some tests for this.
What do you think of the doc style I've started in the readme? Could you add docs for the features of the body cells that you've created (eg rowheight)?

cleanup - have you had a chance to compare your cell declaration/rendering with mine and choose which is best?

I like yours. Will rearrange.

I'm looking at the best way to achieve CSP friendly styling - two addons to choose from which have a mixing to do it.

Good

I have a dev here who's finishing up some low level Raspberry Pi stuff, then I'll put him onto writing some tests for this.

Excellent! :)

What do you think of the doc style I've started in the readme? Could you add docs for the features of the body cells that you've created (eg rowheight)?

I like the style in general. The "incremental buildup" is nice at the start. It may get complex later though.
I will want to put in a column definition iterator that iterates over columns provided as data once I cleanup my stuff. We will probably want to add other stuff as well.
Perhaps e.g. where we have "add a custom footer" we drop the code for custom header?

The "incremental buildup"

It's not strictly observed - I've stripped out some earlier features as I demo the next ones

columns provided as data
Not sure how we'll do the block content when providing columns as data...

Perhaps e.g. where we have "add a custom footer" we drop the code for custom header?
Don't know what you mean here

| Perhaps e.g. where we have "add a custom footer" we drop the code for custom header?
In your custom footer example, the example also includes a custom header. I didn't notice the earlier drops; I was suggesting we drop the custom header in the custom footer example.

I was suggesting we drop the custom header in the custom footer example.

I deliberately put both in so that it doesn't look as though you can only have one or the other

I've put in documentation for body and for overall window. (Some of it is aspirational -- have ability to call accessor in my branch; the ability to look up width, height and rowWidth` are still not present.)

For the moment to get going I'm in the process of writing one test per component... a little bit more than the default "it renders" but not much.

vs ember-collection, we have to land https://github.com/emberjs/ember-collection/issues/26 in some form before we can stop using my branch of ember-collection. Do you want me to merge in those commits you proposed? They look like they are on the fast track anyway.
I am expanding the demo app to include a gallery showing different templates containing ember grids and their results.
+1 for restructure to fully use pods

I had intended my pr to go against your repo but couldn't work out how

No idea why tests are failing. I'm getting different results on first and subsequent runs!
Integration | Component | eg render/eg body cell: it renders (4, 0, 4)Rerun38 ms
Uncaught Error: you must set a resolver with `testResolver.set(resolver)`@ 6 ms
Source:
http://localhost:7357/assets/vendor.js:39469
Died on test #2     at Object.test (http://localhost:7357/assets/test-support.js:1947:11)
    at http://localhost:7357/assets/dummy.js:1221:15
    at mod.state (http://localhost:7357/assets/vendor.js:150:29)
    at tryFinally (http://localhost:7357/assets/vendor.js:30:14)
    at requireModule (http://localhost:7357/assets/vendor.js:148:5)
    at Object.TestLoader.require (http://localhost:7357/assets/test-loader.js:29:9)
    at Object.TestLoader.loadModules (http://localhost:7357/assets/test-loader.js:21:18): Cannot read property 'set' of undefined@ 19 ms
Source:
TypeError: Cannot read property 'set' of undefined
    at http://localhost:7357/assets/dummy.js:1226:9
    at Object.wrapper (http://localhost:7357/assets/test-support.js:1929:29)
    at Object.Test.run (http://localhost:7357/assets/test-support.js:3696:28)
    at http://localhost:7357/assets/test-support.js:3825:11
    at process (http://localhost:7357/assets/test-support.js:3384:24)
    at begin (http://localhost:7357/assets/test-support.js:3429:2)
    at http://localhost:7357/assets/test-support.js:3445:4
Uncaught TypeError: Cannot read property 'subject' of undefined@ 24 ms
Source:
http://localhost:7357/assets/vendor.js:39469
Expected 2 assertions, but 3 were run@ 38 ms
Source:
    at Object.test (http://localhost:7357/assets/test-support.js:1947:11)
    at http://localhost:7357/assets/dummy.js:1221:15
    at mod.state (http://localhost:7357/assets/vendor.js:150:29)
    at tryFinally (http://localhost:7357/assets/vendor.js:30:14)
    at requireModule (http://localhost:7357/assets/vendor.js:148:5)
    at Object.TestLoader.require (http://localhost:7357/assets/test-loader.js:29:9)
    at Object.TestLoader.loadModules (http://localhost:7357/assets/test-loader.js:21:18)

vis ember-collection -- will get into my repo
vis tests -- I stepped back for a bit from tests. Apparently the new ember-cli release this week will resolve some problems with ember-cli-mocha and wanted to delay final decision about using it until that hits. In the meantime I have been filling out some examples in "gallery" in dummy app that won't replace tests, but will illustrate features in conjunction with documentation (and have already led me to a few bugs).


HDDS-4127. Components with web interface should depend on hdds-docs.

What changes were proposed in this pull request?
@ChenSammi  reported the problem that the ozone-0.6.0 branch couldn't be compiled after changing the version to 1.0.0.
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.0.2:unpack (copy-common-html) on project hadoop-hdds-container-service: Unable to find/resolve artifact.: Could not find artifact org.apache.hadoop:hadoop-hdds-docs:jar:1.0.0 in apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots) -> [Help 1]
[ERROR]

Web components include the compiled docs (in case of hugo is on the path)
  <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-dependency-plugin</artifactId>
        <executions>
          <execution>
            <id>copy-common-html</id>
            <phase>prepare-package</phase>
            <goals>
              <goal>unpack</goal>
            </goals>
            <configuration>
              <artifactItems>
                <artifactItem>
                  <groupId>org.apache.hadoop</groupId>
                  <artifactId>hadoop-hdds-server-framework</artifactId>
                  <outputDirectory>${project.build.outputDirectory}
                  </outputDirectory>
                  <includes>webapps/static/**/*.*</includes>
                </artifactItem>
                <artifactItem>
                  <groupId>org.apache.hadoop</groupId>
                  <artifactId>hadoop-hdds-docs</artifactId>
                  <outputDirectory>${project.build.outputDirectory}/webapps/ozoneManager</outputDirectory>
                  <includes>docs/**/*.*</includes>
                </artifactItem>
              </artifactItems>
              <overWriteSnapshots>true</overWriteSnapshots>
            </configuration>
          </execution>
        </executions>
      </plugin>

But the explicit dependency between the container-service and hdds-docs accidentally missing. With adding a provided dependency, it can be fixed (maven will compile hdds-docs first)
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4127
How was this patch tested?
git checkout ozone-0.6.0
find . -name pom.xml -type f | xargs sed -i 's/0.6.0-SNAPSHOT/1.0.0/g'
# apply this patch
mvn clean install -DskipTests

Verified locally.  +1.  Thanks @elek for the quick fix and @bharatviswa504 for the review.


ENum Fied issue

How we generate enum fields for paramater

I want Display paramater and value 0 or 1 in enum api call swagger documenattaion? help req

@pakcybershagufta I have added enum example here. http://labs.infyom.com/laravelgenerator/docs/5.7/getting-started
I will add support into swagger soon for that.

Right now, you can manually update swagger docs to support that. Here is an example: http://petstore.swagger.io/#/pet/findPetsByStatus

Right now, you can manually update swagger docs to support that. Here is an example: http://petstore.swagger.io/#/pet/findPetsByStatus

How manually steps please ?Advance thanks

I m asking for swagger not for migration?

@pakcybershagufta the same example is there. Check the swagger doc in above link. https://petstore.swagger.io/v2/swagger.json

One more help required how define Authorization: Bearer token
Header (in :header )
Authorization: Bearer token

I think you should ask this into swagger repo. you will better answer from there.

One more help required how define Authorization: Bearer token
Header (in :header ) Authorization: Bearer token

you can refer this tutorial https://youtu.be/ytXsvPR0IBA


Contributing fmu.nim

Hi,
I created fmu.nim. I think it is usable in its current stage. I think the code could be cleaned and make it more like Nim. On the other hand:

it supports Model Exchange and Co-Simulation
it is capable of creating multiplatform FMU
it has better ergonomics than the original fmusdk

I am happy to contribute it to SciNim. Let me know if it is good enough and how I should contribute it (I am not very knowledgable about Github -and many other things-).

I will send you an invite to the SciNim org :)


disable TCMalloc

Checklist before submitting

[x] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Fixes https://github.com/open-ce/open-ce/issues/261.
Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

Is there any other package that uses tcmalloc?

Is there any other package that uses tcmalloc?


Failed to fetch tree from registry while using npx shadcn-ui@latest add

I am getting the following error while using npx shadcn-ui@latest add {component name} or using shadcn-ui CLI
can someone help me, stuck for a while ?
 npx shadcn-ui@latest add table
SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
    at JSON.parse (<anonymous>)
    at Response.json (file:///home/udaya/.npm/_npx/125ee17d583c4e03/node_modules/node-fetch/src/body.js:150:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async file:///home/udaya/.npm/_npx/125ee17d583c4e03/node_modules/shadcn-ui/dist/index.js:2:4266
    at async Promise.all (index 0)
    at async j (file:///home/udaya/.npm/_npx/125ee17d583c4e03/node_modules/shadcn-ui/dist/index.js:2:4233)
    at async D (file:///home/udaya/.npm/_npx/125ee17d583c4e03/node_modules/shadcn-ui/dist/index.js:2:3956)
    at async Command.<anonymous> (file:///home/udaya/.npm/_npx/125ee17d583c4e03/node_modules/shadcn-ui/dist/index.js:3:1965)

Failed to fetch tree from registry.

with little bit of debugging found that content returned form the API is '404 html page'
Tried following but did't work

change the network and use vpn
Update npm and node
Clear npm Cache
shadcn-ui CLI

Project config

nextjs v14.0.4
node v20.10.0
npx v10.2.5
shadcn-ui CLI v0.1.0

I can provide more details if needed

sorry my bad while editing components.json file I accidentally changes style filed to empty string
I changed back to "default" it started working

I am also getting the same error.
the error code is
npx shadcn-ui@latest add popover
SyntaxError: Unexpected token '<', ")
at Response.json (file:///home/abdus-salam/.npm/_npx/125ee17d583c4e03/node_modules/node-fetch/src/body.js:149:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async file:///home/abdus-salam/.npm/_npx/125ee17d583c4e03/node_modules/shadcn-ui/dist/index.js:2:4419
at async Promise.all (index 0)
at async N (file:///home/abdus-salam/.npm/_npx/125ee17d583c4e03/node_modules/shadcn-ui/dist/index.js:2:4386)
at async S (file:///home/abdus-salam/.npm/_npx/125ee17d583c4e03/node_modules/shadcn-ui/dist/index.js:2:3644)
at async Command. (file:///home/abdus-salam/.npm/_npx/125ee17d583c4e03/node_modules/shadcn-ui/dist/index.js:3:1986)
my components.json is like this

{

"$schema": "https://ui.shadcn.com/schema.json",
"style": "new-york",
"rsc": true,
"tsx": true,
"tailwind": {
"config": "tailwind.config.js",
"css": "app/globals.css",
"baseColor": "",
"cssVariables": false,
"prefix": ""
},
"aliases": {
"components": "@/components",
"utils": "@/lib/utils"
}
}

not sure  @kmasalam ,
if you need help you can re-open the issue tagging maintainers

@kmasalam try initializes the shadcn-ui configuration in your project, by using "npx shadcn-ui@latest init" it might fixed it, i was also facing the some issue.

i  deleted the components/ui folder, that disrupted the expected structure. Reinitializing the shadcn/ui configuration with npx shadcn-ui@latest init restores the necessary setup, and resolved the issue for me


Support HTTP/2.0

Hi,
Do You have any WIP for this, plans, ideas how to implement this? Or maybe a good point of start will be after 1.0 release when internal API and classes will be stabilized? Any info appreciated :)

The main focus is currently on getting the v1.0.0 out. As such, there are currently no immediate plans to build this from our end (no demand at the moment), but I suppose we would be really happy to accept PRs :+1:

@clue I would like to see HTTP/2 support after 1.0.0 is out. But we need certain features for that first.

Ok, so i will get back to topic after 1.0 :)

how does this have to do with version 2? i thought version 2 is an nginx thing rather?

@cordoval Yes, there are a number of use cases where you can use this project without requiring HTTP/2.0. For example, if you're using this project behind a reverse proxy (such as nginx) that is capable of speaking HTTP/2.0 to the client and forwards this as HTTP/1.x to this library, then you can probably live without native HTTP/2.0 support here.
However, we still want to look into implementing HTTP/2.0 here as well so that this can also be used without a reverse proxy 👍  In the meantime, there are plenty of HTTP/2.0 proxies that can be used as above 👍

@clue && @cordoval in fact most of my own sites are running react/http behind nginx that handles HTTP/2.0 and certificates for all the different sites hosted on that box.

nice man, good to know
hey have you news where is igorw? 👴 just curious

Are there any plans to support HTTP/3?

@valzargaming I can definitely see us implementing HTTP/3 in the future, but baby steps first! In the meantime, using a reverse proxy to handle HTTP/2 and HTTP/3 is perfectly reasonable for many uses, but we definitely welcome contributions to help us land full support here as well :+1:

It seems like this ticket is open for quite a while now. I want to avoid issues and pull request laying around for too long, but this depends on each topic. I think HTTP/2 support will come in the future, but I don't think there's something scheduled yet.
With that said we could close this ticket for now and reopen it once there are more detailed plans for HTTP/2 support, or we could leave it open, I will leave this decision to @clue as he opened this up :+1:

It seems like this ticket is open for quite a while now. I want to avoid issues and pull request laying around for too long, but this depends on each topic. I think HTTP/2 support will come in the future, but I don't think there's something scheduled yet.

IMHO we still want to do this but need to do some internal refactoring first. It is very much on my list of things to add.


Public Rooms are officially broken

Maybe we sould immplement a way to disable bots from protobowl chat or have them detect if another is running and stop because its crazy

I heard they're banning people. Do you know if it's permanent?


Detect GPU and import cupy as np

I could not find an example how to detect if GPU is present and swap numpy for cupy during import. Is that possible?
from cupy import gpu
if gpu:
  import cupy as np
else:
  import numpy as np

cupy.cuda.is_available() returns True if 1 or more devices are available.
import numpy as np
try:
    import cupy
    if cupy.cuda.is_available():
        np = cupy
except:
    pass

I expect linters complain on except everything pattern. What kind of exceptions can be thrown here?

And I want to use cupy on AMD. Will cupy.cuda.is_available() detect it?

I expect linters complain on except everything pattern. What kind of exceptions can be thrown here?

except Exception: should work.

And I want to use cupy on AMD. Will cupy.cuda.is_available() detect it?

Yes, we provide the same API for both CUDA / AMD builds.

except Exception: should work.

I am afraid that doesn't answer the question, and it is still the catch everything antipattern.

Yes, we provide the same API for both CUDA / AMD builds.

If there a plan to move non-specific functions into cupy.gpu namespace?

The code would still be more readable with cupy.gpu namespace hiding internal details. The namespace could also by used to query information about hardware and possible bugs.


dhall-render: Added support for YAML stream documents

Kubernetes and yaml stream/multi documents sitting in a 🌴
Support writing this type if the contents input is a list, with each document encoded.
I'm not sure if psych is the right module to work here, but it worked out of the box for me.
Feel free to use some other module if there's any you prefer.

Thanks, I've tweaked this a bit in https://github.com/timbertson/dhall-render/commit/f10494d09ebec352ca7a22888e6401e4d28ae8db.
I figure an actual single-document yaml with a toplevel array is rare enough that we can just always treat it as a multi-doc rather than calling it a different format. You can always print a JSON doc with a .yaml extension if you really need a raw toplevel array 🤷
I did have to use Psych.dump_stream(*contents) (note the *), otherwise I just got a single-document with an array in it. But with the star, you get this which I assume is what you're after.


Higher phpunit version required for assertObjectHasProperty

Fix failing test with lower deps.
Caused by https://github.com/mongodb/mongo-php-library/pull/1432 and https://github.com/mongodb/mongo-php-library/pull/1405

@GromNaN I updated your patch to test the lowest dependencies variant as well: https://spruce.mongodb.com/task/mongo_php_library_test_debian92_php_8.1_local_lowest_test_mongodb_4.0_replicaset_noauth_nossl_patch_62dd5ff087fcffe9d5f8c5dff6e6c6f6c6e58028_66f512bf8f75530007446997_24_09_26_07_52_35/logs?execution=0


Parse arguments into properties of args.

Coverage increased (+0.1%) to 93.461% when pulling 747c468964d0f596243fdeac88e2cf23ba2c827e on parse-arguments into 007bf80168280c954b2d78f2c3c7bd330347cac0 on master.


feat: add --single-active-backend to allow only one backend active at the time

Description
This PR fixes #909 by adding a simple mechanisms to manage single devices. It adds a single-active-backend (SINGLE_ACTIVE_BACKEND) CLI flag: when enabled LocalAI will make sure to use only one backend - and automatically stop the ones in use only if idleing if there is a new request (otherwise it will wait). This allows for instance, to generate an image with one GPU, and then start chatting right after with an LLM using the same GPU. This is fundamental when having two consecutive requests to different backends targeting the same GPU or LocalAI will just crash as for now.
In scenarios with multiple-GPUs, for Llama, it is possible to specify already a CUDA device - this allows fine-grained control over the devices being used, however multi-GPU management is out of scope of this PR (as it focuses only on the specific, single case).
It also lowers down the grpc server workers for python to 1 - this allows only one request per time (it automatically queues them, as it seems) bringing back the old behavior. I just tried with diffusers, and parallel requests didn't seem to work well here at all.
Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

This should improve how the models are handled when idling ! i'm going to test it this week to see how the interaction with different backend goes, and report back with more info.


fail to get pictures when getting thumb picture first.

 int defaultWidth = 640;
    if (self.showThumbFirst) {
        //load small pic first.
        defaultWidth = 640 / 4;
    }
    NSString * defineUrl = [[HGUtils sharedInstance] cloudinaryLink:imageLink width:defaultWidth height:0];

    NSURL * imageURL = [NSURL URLWithString:defineUrl];
    [cell.webImageView sd_setImageWithURL:imageURL placeholderImage:self.placeholderImage completed:^(UIImage *image, NSError *error, SDImageCacheType cacheType, NSURL *imageURL)
    {

        else{
            if (self.showThumbFirst) {
                //load big pic
                NSString * defineUrl_big = [[HGUtils sharedInstance] cloudinaryLink:imageLink width:640 height:0];

                NSURL * imageURL_big = [NSURL URLWithString:defineUrl_big];
                [cell.webImageView sd_setImageWithURL:imageURL_big placeholderImage:nil completed:^(UIImage *image, NSError *error, SDImageCacheType cacheType, NSURL *imageURL) {

                    if (error) {
                        NSLog(@"get big image fail error: %@", error);
                    }
                }];
            }
        }
    }];
}

================================
hi, I am using SDwebimage to download pics, first download the thumb of the picture (size 160, ) , then in the complete block , will download the big size of the same pic with a different url,
most of the cases, this functions work ok , but , there are 10% of the cases, the big picture fail to download,which make a smaller display all the time, and if this happen , this is always repeated,
I have traced inside , it seems that, if the first small url is found in the cache, the download operation is cancled,
but it should not effected a different url,
so may be this bug, should be fixed. in later version ...
please try, it is quite easy to repeat this bug.

there might be issues with the code you have pasted. In the completion block of the sd_setImageWithURL... you have an else statement which does not belong there...or you have forgotten some code on top of that.
anyway...can you replicate the bug using the demo project?

nothing todo with the code," else", i try a demo, but much harder to repeat the bug,
may be it is the network's problem, please close this, will give your more information if i can  repeat any cases.
Thx


updated doc figures

work in progress

waiting for #466

updated all the figures generated by tests with new matplotlib version.


Use dynamic variable for columnMapping

I'm trying to drive my column mapping from a database configuration table. IN my copy activity's mapping tab I am using a dynamic expression like @json(activity('Lookup1').output.value[0].ColumnMapping)
I don't know what to put for the value of this expression. I've tried several options but my mapping always seems to be ignored. For example, I've tried:
{
"view.url": "url",
"view.name": "name"
}
and
"columnMappings": {
"view.url": "url",
"view.name": "name"
}
Nothing seems to work

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

ID: 75402f01-c53e-25e0-6f1c-bc94d797dda1
Version Independent ID: a3dfb190-a12d-37cf-2dfe-034becd60e39
Content: Schema mapping in copy activity
Content Source: articles/data-factory/copy-activity-schema-and-type-mapping.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@jeffhebrank Thanks for the feedback. We are actively investigating and will get back to you soon.

@linda33wj could this be evaluated to add to the documentation?

@jeffhebrank I think this question has been answered in StackOverflow https://stackoverflow.com/questions/51142783/using-adf-copy-activity-with-dynamic-schema-mapping. Kindly let know if more issue.

@linda33wj  It doesn't seem to be working, even as per StackOverflow comments, it doesn't work for him as well. "For JSON path not support dynamic content, I think that could be an UI issue. You could have a try with json code directly"

@linda33wj, it still doesn't work

Hi, there is any dynamic way of adding/removing columns in the pipeline? For example: If I add a new column to the source table how could I make to display the new column in the destination without have to modify the pipeline? Thanks!

Did you able to get any solution. I am also into same situation where I want to copy only required columns from ADLS Gen2 RAW file to ADLS Gen2 Stage File. I have to define schema for every file separately which means 1 activity, 2 dataset per file and not an elegant solution if we talk 1000+ file. I need it dynamically.

@sanjusanjeet yes I was able to use dynamic mapping via passing dynamic schema stored into a SQL table as below format :
{
"type": "TabularTranslator",
"columnMappings": {
"Id": "ContactId",
"CreatedDate": "CreatedDate",
"LastModifiedDate": "LastModifiedDate"
}
}
and later us this in Copy activity , mapping like "@json(string(item().columnMappings))"
also make sure to use "Get Metadata" activity before copy to get structure for source and sink.

Thanks Gaurav, is your source and sink both ADLS gen2. Somewhere I read that you need to create separate dataset for fixed schema of data lake files.

In my solution, it's from ADL Gen1 to SQL or ADL Gen1 to Blob.

Is there any way to map pipeline parameter value to sink dataset column in copy activity?

gaurav7961, I am still struggling with it.. would it be possible for your to guide. i need to supply schema of source and sink before using this. How can we leverage get metadata activity and use its output to make it work?

@iamnarendhar : It is not supported, I am not from microsoft but may be this is not the right place to put this question. Dataflows does have support for this, but if you really dont care of the content of the file like header being mapped to all columns for details rows, move to folder level processing it is much quicker.

@iamnarendhar I was able to do it using set variable and then using @json(variables('dynamicMapping'))

@linda33wj for awareness
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply.
We will gladly continue the discussion, and we will reopen the issue.
To see what the community is wanting, please visit the UserVoice site.

#please-close

I think we should open this issue. I use the expression language for column mapping with using get metadata to get the structure, but ADF ignores the expression for schema. Any help?

@markingmyname


Publish page

Updated layout for EPND
Created export preview page
Switched off inferencing to reduce workload

@matthijssloep agreed ;-)


feature: added codecov badge to readme

Codecov Report

Merging #17 (f43b43c) into main (0418f65) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #17   +/-   ##
=======================================
  Coverage   97.36%   97.36%
=======================================
  Files           9        9
  Lines         228      228
=======================================
  Hits          222      222
  Misses          6        6


Automatic checkout on save not working

I have VS2015 and it's connected to our TFS server (in case there's anything else I need to configure). I don't know if it matters but the TFS workspace for my branch is on the server rather than local.
If I edit a file in VS Code and hit save, I get an Error:
"Failed to save 'your-file.js': File is write protected. Select 'Overwrite' to remove protection"
Thanks

The same is happen to me

im facing the same problem as well, but after i update my nodejs to latest version v7.7.4, then it works.
could it because of nodejs?

After update to latest version of plugin it was solved. Just take a while to unlock the file, but works great

I have the same problem, working off a fresh VM with Team Explorer installed. Using Azure Repo extension with connection to TFS server


build:prod and error:MIME type ('text/html') is not a supported stylesheet MIME type

Bug report（问题描述）
Steps to reproduce（问题复现步骤）

npm run build:prod
run server
access index.html

Refused to apply style from 'http://localhost:63342/static/css/chunk-libs.3dfb7769.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
Refused to apply style from 'http://localhost:63342/static/css/app.ae89c2cc.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.

Screenshot or Gif（截图或动态图）

Other relevant information

Your OS: macOs
Node.js version: v11.8.0
vue-element-admin version:v4.0.1

same issue, but my version is 3.10.0

你改过什么？
感觉像 publicPath设置的不对。


apps are not auto updating on Pixel 6 running with GOS

I am using GOS on Pixel 6 running with GMS as sandboxed apps. However my apps are not autoupdating. Any solution please?

Play Store updates apps in the background automatically. It works fine on GrapheneOS. It prefers only doing updates when the device is not being used and has been idle for a while. It will often delay them for a long time if the device is in active use. Not specific to GrapheneOS in any way

There's nothing special about the releases of Google Play in our app repository and this repository is for our app repository client software so this is the wrong place to file this.


[3/3] Graph RIP: multi: RPC GraphSource

Depends on https://github.com/lightningnetwork/lnd/pull/9243
With this PR, an LND node can be be given an external GraphSource to rely on.

A grpc implementation of GraphSource is added which purely relies on a remote graph source.

A Mux impl of GraphSource is also added which uses a combination of a remote GraphSource along with the local GraphSource to provide a more complete & efficient GraphSource implementation.

A new --gossip.no-sync config option is added which results in the gossip
queries feature bit not being advertised and also means that we dont send
any gossip queries. The result is that we dont populate our local graph DB
with any info other than our own channels/channel peers. If an external graph
source is provided as the GraphSource, then it makes sense to use the new
configoption since we will use the external source for gossip data.

See the itest for how to test this on regtest :)

2 follow ups to address (potentially in a separate PR):

channel updates received on payment errors should be pushed to the remote graph
the graph cache should be moved a layer up from ChannedGraph so that this is addressed before querying the remote source. A more complex follow up from this would then to let the remote source send stale-cache signals to various dependents so that they know when to update their cache for a given channel

!lightninglabs-deploy mute


Tester feedback: language
(respondent_has_other_children)

Question ID
respondent's other children

Variable sought
respondent_has_other_children

Package version
playground

Form
docassemble.playground4PPO:ppo_and_proposed_order.yml

Details:
again, this question feels odd when I said respondent was my parent

removed word "other" since it seems confusing either way


Camera zoom broken?

Camera zoom seems to have been broken with the recent update from jagex. I have reset runelite to see if this would fix it but it does not.

Fixed with the latest update.


wip phone prefix

this should remove some of the yield farming earn rewards, and sms flooding attacks
let me know what you think about the approach. I'll do some tests if this sounds good.

I dont think this is a good solution.. we will end with a really long list in the config and also this does not protect against voip or temp phone number providers

I dont think this is a good solution.. we will end with a really long list in the config and also this does not protect against voip or temp phone number providers

voip can be dealt with another way: those phone type can be removed from the rewards program. temp phone number providers also typically give back voip number.


Serve different port?

I changed the build config's port reference to 8000 but gulp sill serves up on port 3000 (or 3001 if it's in use)..    I'm doing an OAuth callback so for dev I need this port locked to 8000. . Any clue how to change it?    Big Thanks for this project..  helped "kickstart" my angular learning..

found it..   realized it was browser-sync not gulp I needed to tell about it..   for future reference I used:
gulp.task('serve', ['build'], function() {
  browserSync({
    port: config.port,
    ui: {
      port: config.uiPort
    },
    notify: false,
    logPrefix: pkg.name,
    server: ['build', 'client']
  });
...

and put a setting in the build/build.config.js file

Actually you raised a good point.
Do you mind a PR?


Add GUI page

Add a WebApp with GUI to control the five free parameters and see results live

Working on this now

Adding a interactive graphical plot (using Bokeh)
Todo list:

[ ] Create a docker-compose.yml
[ ] Add pyproject.toml
[ ] Add bokeh server container
[ ] Test deploy locally
[ ] Deploy on AWS EC2


Make LLPhant compatible with the new Embeddings endpoint from OpenAI

done with : https://github.com/theodo-group/LLPhant/pull/74


README.md and documentation shortcomings

Does the README.md provide enough documentation to install the system from scratch? For example:
"Copy the file config/config.example.json to config/config.json and modify it as required."
This seems like there's a lot that needs to be done here in terms of database setup, and I'm not sure what the right directions would be here. Thanks.

The documentation is insufficient, it was not modified from the forked repo.
We need to make the documentation better, it is definitely in the todo list

I added a small update to the readme, right now only the app part is complete, I still need to finalize the services part


[RFC] Aligning Access and Visibility in OpenSearch

Problem Statement
When a OpenSearch cluster admin Alice creates and then shares a Quarterly Sales dashboard with user Bill; Alice does not know if Bill will see the same data.
How can this be?
In the Security Plugin there are several permissions rules that are computed based on the user sending the query.  These alter the query results and are invisible to the user Bill.

Permissions for indexes are additive, to read an index a user need to have a role that grants them permission to that index.  Sales data could be in indices named sales-na-YYYY-MM & sales-eu-YYYY-MM, Bill might only have access to the EU region.
Document level security features (incl. row, columns, field-masking) are additive, if a user has a role with these features enabled it adds a restriction on the data.  Sensitive sale data is filtered out by a DLS rule, customer-name == Frodo Baggins
Security supports operating in a mode where queries are edited in flight to remove indexes the user does not have permissions to access.  Bill does not have access to the NA region sales data and those results are silently filtered out

Bill's view of the dashboard would be missing data and he would not be unaware.  Even if he brought this to Alice's attention she does not have a straight forward way to know what Bill data is missing nor if he needs more permissions to sales-na-* or less permissions so the sensitive sales data filter is not applied.
flowchart TB
    A["Quarterly Sales Dashboard Query: sales-*"] -->B1["Alice: Expand Query Indices
sales-na-jan, sales-na-feb, sales-eu-jan, sales-eu-feb"]
    A -->B2["Bill: Expand Query Indices
sales-na-jan, sales-na-feb, sales-eu-jan, sales-eu-feb"]

    subgraph Alice ["Alice's Flow"]
    B1 --> C1{"Resolve User Permissions"}
    C1 -->|No Filters Applied| E1["Filtered Indices:
sales-na-jan, sales-na-feb, sales-eu-jan, sales-eu-feb"]
    E1 --> F1{Apply DLS Rules}
    F1 -->|No DLS Rules Applied| G1["Final Query:
sales-na-jan, sales-na-feb, sales-eu-jan, sales-eu-feb"]
    G1 --> H1["Run Query"]
    end

    subgraph Bill ["Bill's Flow"]
    B2 --> C2{"Resolve User Permissions"}
    C2 -->|Filters Applied| E2["Filtered Indices:
sales-eu-jan, sales-eu-feb"]
    E2 --> F2{Apply DLS Rules}
    F2 -->|Exclude 'Frodo Baggins'| G2["Final Query:
sales-eu-jan, sales-eu-feb Exclude 'Frodo Baggins'"]
    G2 --> H2["Run Query"]
    end

    H1 --> I["All Indices Data"]
    H2 --> I

    style A fill:#f9f,stroke:#333,stroke-width:2px
    style I fill:#bff,stroke:#333,stroke-width:2px

Proposal
There should be a resource that combines these different access control rules together so that if access is grant to that resource Alice has confidence that Bill sees exactly the same view of the data.  If Bill does not have access, there is a clear path to resolve the access question - "Alice could you grant me access to 'Company wide sales data' resource so I can see the Quarterly Sales dashboard?"
This resource would be fundamentally different from existing index/index pattern/alias/datastream that require explicit permissions. Administration of the setting of resources would require permissions of the 'targeted' indexes.
This resource would need a new way to be granted / reviewed since the existing permissions model only allows for cluster wide, index and tenants permissions.
I suggest this is called a View, as in "Alice could you grant me access to the 'Company wide sales view'".
Additional Context
Related issues

https://github.com/opensearch-project/security/issues/3773
https://github.com/opensearch-project/security/issues/3274
https://github.com/opensearch-project/security/issues/3963

@varun-lodaya Thanks for taking a look - the utility of fine vs course is dependent on what resource is being permissioned.  The problem raised by this issue is that it can be unclear how different levels of fine grain control operate.  I don't think there is a requirement for a single permissions model; the existing model creates these problems and the question is if we should address it.
We've had many issues reported to back up this problem statement and I'll collect more and update the description to include them.

https://github.com/opensearch-project/security/issues/3773
https://github.com/opensearch-project/security/issues/3274
https://github.com/opensearch-project/security/issues/3963

Do you agree with the premise of the problem, it sounds like you might have an alternative proposal in mind?

I've been trying to think about how to use the "views" concept to support multi-tenant clusters.
I wrote up a straw API call example to create a view, specify who can access it, and provide a series of processors that limit the requests/responses on the views: https://docs.google.com/document/d/1AUEPXw5-P7UxW_UhdLdXw_LZTkCVyQdYEnh676WGlC4/edit?usp=sharing
The analogy I gave on another issue is that your cluster is an amusement park and a view is an entrance. The entrance you use determines which credentials are required and what wrist-band you're issued (which determines what rides/amenities you can access).
@peternied -- I don't know if this is in line with what you had in mind, but it makes sense to me.

@msfroh Thanks for writing up that doc.  I like many of the ideas you proposed.  As 'views' has an implication in the DB space, I wouldn't mind an alternative, along the lines of data_park_entrance_gate_name 🤣


08_atmosphere_Mars_global

Need to include this for release paper

We think this is close to being done, but will need merging


use tsv spawn and goal filtering

testing done:

checked that only approved points show up in lists
checked a bunch of random resets to see that only approved points are used
set a static index into the list that should result in a dream zone point, confirmed it skipped to the next valid point


Utilities to work with parseSimpleArray/string conversion methods

This PR adds methods to serialize/de-serialize data to work with parseSimpleArray/string conversion methods of game engine.
This can be useful to create extensions, or parse logs.

Thx for further contributions. Just one remark: Do you think it makes sense to add BIS.TXT as a namespace? Dont really feel that TXT files are a particular BIS file format. I think your code would be best suited in Utils or BIS.Core. What do you think?

I was hesitating. You are right, it does not make sense.
I think it will be better in BIS.Core like config, in a "Serialization" namespace. What do you think ?

Yeah, I also think it is closely related to Configs so it could go there.

LGTM! Shall I merge or are you still working on it?


Fix for FileSystem dock going blank on certain actions

Fixes for #59236 and #58911.
Sometimes the dock is cleared and updated but never drawn so added some calls to show().
Similar problem in the floating dock.
Bugsquad edit: Fixes #59236 Fixes #58911

Seems to work fine, but the filesystem dock is still cleared for a brief moment:

I wonder if something can be done about it.

See https://github.com/godotengine/godot/pull/61435

Superseded by #61435.


Installing Tensorflow, verifying

Please go to Stack Overflow for help and support:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\Fritz>pip install "C:\tensorflow\tensorflow\contrib\cmake\build\tf_pyth
on\dist\tensorflow_gpu-1.5.0-cp35-cp35m-win_amd64.whl"
Requirement 'C:\tensorflow\tensorflow\contrib\cmake\build\tf_python\dist
\tensorflow_gpu-1.5.0-cp35-cp35m-win_amd64.whl' looks like a filename, but the f
ile does not exist
tensorflow_gpu-1.5.0-cp35-cp35m-win_amd64.whl is not a supported wheel on this p
latform.
You are using pip version 9.0.1, however version 10.0.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' comm
and.
C:\Users\Fritz>pip install "C:\tensorflow\tensorflow\contrib\cmake\build\tf_pyth
on\dist\tensorflow_gpu-1.5.0-cp35-cp35m-win_amd64.whl"
C:\Users\Fritz>pip install --upgrade --no-deps --force-reinstall tensorflow-gpu
Collecting tensorflow-gpu
Cache entry deserialization failed, entry ignored
Using cached https://files.pythonhosted.org/packages/51/bc/29202147b513f0ed5fb
dd40f05c6bc2a19722cfb4dd24d77a7c2080a06b4/tensorflow_gpu-1.9.0-cp36-cp36m-win_am
d64.whl
Installing collected packages: tensorflow-gpu
Found existing installation: tensorflow-gpu 1.9.0
Uninstalling tensorflow-gpu-1.9.0:
Successfully uninstalled tensorflow-gpu-1.9.0
Successfully installed tensorflow-gpu-1.9.0
You are using pip version 9.0.1, however version 10.0.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' comm
and.
C:\Users\Fritz>python
Python 3.5.2 (v3.5.2:4def2a2901a5, Jun 25 2016, 22:18:55) [MSC v.1900 64 bit (AM
D64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

import tensorflow as tf
Traceback (most recent call last):
File "C:\Users\Fritz\AppData\Local\Programs\Python\Python35\lib\site-packages
tensorflow\python\pywrap_tensorflow_internal.py", line 18, in swig_import_helper

return importlib.import_module(mname)

File "C:\Users\Fritz\AppData\Local\Programs\Python\Python35\lib\importlib_in
it_.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 986, in _gcd_import
File "", line 969, in _find_and_load
File "", line 958, in _find_and_load_unlocked
File "", line 666, in _load_unlocked
File "", line 577, in module_from_spec
File "", line 906, in create_module
File "", line 222, in _call_with_frames_removed
ImportError: DLL load failed: Das angegebene Modul wurde nicht gefunden.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\Fritz\AppData\Local\Programs\Python\Python35\lib\site-packages
tensorflow\python\pywrap_tensorflow.py", line 58, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Users\Fritz\AppData\Local\Programs\Python\Python35\lib\site-packages
tensorflow\python\pywrap_tensorflow_internal.py", line 21, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Users\Fritz\AppData\Local\Programs\Python\Python35\lib\site-packages
tensorflow\python\pywrap_tensorflow_internal.py", line 20, in swig_import_helper
return importlib.import_module('_pywrap_tensorflow_internal')

File "C:\Users\Fritz\AppData\Local\Programs\Python\Python35\lib\importlib_in
it_.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
ImportError: No module named '_pywrap_tensorflow_internal'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\Fritz\AppData\Local\Programs\Python\Python35\lib\site-packages
tensorflow_init_.py", line 24, in
from tensorflow.python import *
File "C:\Users\Fritz\AppData\Local\Programs\Python\Python35\lib\site-packages
tensorflow\python_init_.py", line 49, in
from tensorflow.python import pywrap_tensorflow
File "C:\Users\Fritz\AppData\Local\Programs\Python\Python35\lib\site-packages
tensorflow\python\pywrap_tensorflow.py", line 74, in
raise ImportError(msg)
ImportError: Traceback (most recent call last):
File "C:\Users\Fritz\AppData\Local\Programs\Python\Python35\lib\site-packages
tensorflow\python\pywrap_tensorflow_internal.py", line 18, in swig_import_helper
return importlib.import_module(mname)

File "C:\Users\Fritz\AppData\Local\Programs\Python\Python35\lib\importlib_in
it_.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 986, in _gcd_import
File "", line 969, in _find_and_load
File "", line 958, in _find_and_load_unlocked
File "", line 666, in _load_unlocked
File "", line 577, in module_from_spec
File "", line 906, in create_module
File "", line 222, in _call_with_frames_removed
ImportError: DLL load failed: Das angegebene Modul wurde nicht gefunden.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\Fritz\AppData\Local\Programs\Python\Python35\lib\site-packages
tensorflow\python\pywrap_tensorflow.py", line 58, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Users\Fritz\AppData\Local\Programs\Python\Python35\lib\site-packages
tensorflow\python\pywrap_tensorflow_internal.py", line 21, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Users\Fritz\AppData\Local\Programs\Python\Python35\lib\site-packages
tensorflow\python\pywrap_tensorflow_internal.py", line 20, in swig_import_helper
return importlib.import_module('_pywrap_tensorflow_internal')

File "C:\Users\Fritz\AppData\Local\Programs\Python\Python35\lib\importlib_in
it_.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
ImportError: No module named '_pywrap_tensorflow_internal'
Failed to load the native TensorFlow runtime.
See https://www.tensorflow.org/install/install_sources#common_installation_probl
ems
for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.

What is wrong ?

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce
Mobile device

What is your CPU make and model?
I suspect this is a duplicate of https://github.com/tensorflow/tensorflow/issues/19584

It has been 15 days with no activity and the awaiting response label was assigned. Is this still an issue?


Allow the kubelet configuration to define swap behaviour for k8s >= 1.22

How to categorize this PR?

/area os
/kind enhancement
What this PR does / why we need it:
Allow the kubelet configuration to define swap behaviour for k8s >= 1.22. This is important for cgroupsv2 hosts, as swap is managed differently compared to cgroupsv1. In cgroupsv1, using the failSwapOn: false flag,  a container can use use swap up to memory working set + swap <= memory.limit_in_bytes). In cgroupsv2, containers cannot use swap by default and require the swap behaviour UnlimitedSwap to be enabled in the kubelet config.
Does not include documentation, just like there is no documentation for the failSwapOn flag configurable in the Shoot.  I assumed that we don't want to advertise this feature as it's currently in alpha state. The example Shoot is updated though.
Which issue(s) this PR fixes:
Fixes #7745
Special notes for your reviewer:
Helpful Links:

KEP: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/2400-node-swap/README.md
OCI: https://github.com/opencontainers/runtime-spec/blob/main/config-linux.md?plain=1#L349
CRI: https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/cri-api/pkg/apis/runtime/v1/api.proto#L804
cgroupsv2 swap settings: https://facebookmicrosites.github.io/cgroup2/docs/memory-controller.html

To test this PR it is not necessary to have swap enabled as the container runtime simply reflects the swap settings on the cgroupfs.
To configure a Shoot to use swap
kubelet:
  failSwapOn: false
  memorySwap:
    swapBehavior: LimitedSwap
  featureGates:
    NodeSwap: true

When using LimitedSwap on cgroupsv2, the memory.max setting on the containers (not pods) cgroup should be set to 0 (disable swap usage). When using cgroupsv2 and UnlimitedSwap, the memory.max setting should be max.
Release note:

 Allow the kubelet configuration to define swap behaviour {LimitedSwap / UnlimitedSwap} for k8s >= 1.22

/retest-required

/lgtm
/approve
/milestone v1.71

/retest

Not related to this PR.
/test pull-gardener-integration


python310Packages.pyialarm: 1.9.0 -> 2.0.0

Description of changes
https://github.com/RyuzakiKK/pyialarm/releases/tag/v2.0.0

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 180965 run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.ialarm
python310Packages.pyialarm
python39Packages.pyialarm


Update Makefile

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 72.092%

Files with Coverage Reduction
New Missed Lines
%

pkg/engine/operation/parser/parser.go
3
75.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
4593

Relevant Lines:
6371

💛  - Coveralls


2.3.0: Update dependencies to new hapi scope

Hey,
I updated your hapi plugin since I need it. There is a problem with the tests code coverage but I think it comes from the update of lab.

Hey @drouarb! Thanks for this PR - there are a few issues that would need to be fixed before it can be merged. First is the drop in coverage you mentioned. That should be bumped back up to 100%. Second, this specifies a peerdep of hapi @18.3.1, which is latest. This module is compatible with v17 and v18, which makes this peerdep of "latest" much too strict.

Works for me. I was planning on getting to this later today if no one else
had completed this PR.
On Thu, Jul 11, 2019 at 8:56 AM Frank Thelen<EMAIL_ADDRESS>wrote:

@frankthelen commented on this pull request.
In package.json
https://github.com/p-meier/hapi-api-version/pull/30#discussion_r302526752
:

@@ -23,17 +23,17 @@
"node": ">=8.0.0"
},
"peerDependencies": {

"hapi": ">=17.x.x"

"@hapi/hapi": "^18.3.1"

Woudn't make it that strict in peerDependencies. What about this one:
"@hapi/hapi": ">=17.x.x"
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/p-meier/hapi-api-version/pull/30?email_source=notifications&email_token=AA54FVNSA6CNF2STOPO6I4LP64UW3A5CNFSM4HOI7DZ2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB6EZRLQ#pullrequestreview-260675758,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA54FVISGPVHZAUBBR3JWTTP64UW3ANCNFSM4HOI7DZQ
.

Closing in favor of #33, as this PR hasn't had activity from its owner in some time.


Changes For Alarm Display

Remove CLEAR from green banner.
for PIP MAX (Red) "Peak Patient Inspiratory pressure exceeded. Check PIP Valve"
Vol Low Alarm (Red) "Low Tidal Volume. Check Ventilator, patient circuit"
12 V (Red) "Electrical power lost"
9 V (Yellow) "Alarm battery low. Replace soon"
Pressure Low (Red) "Patient Inspiratory Pressure Low, Check patient circuit"
Peep Min (Yellow) "Pressure below PEEP. Check patient circuit"

@marty-pmr currently only one alarm condition is displayed on the banner. How do the alarm and warning condition rank?
alarms have a higher display priority than warnings, but we would need to sort alarm and warning conditions.

Hi Matthias,
I would like to try scrolling through alarms and warnings, say 2 second shots…
Thanks,
Marty
From: mwittgen
Sent: Wednesday, June 24, 2020 11:27 AM
To: slaclab/pabv_control<EMAIL_ADDRESS>Cc: Breidenbach, Martin<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [slaclab/pabv_control] Changes For Alarm Display (#92)
@marty-pmrhttps://github.com/marty-pmr currently only one alarm condition is displayed on the banner. How do the alarm and warning condition rank?
alarms have a higher display priority than warnings, but we would need to sort alarm and warning conditions.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/slaclab/pabv_control/issues/92#issuecomment-648989961, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APB4OBVUPLOJZZD4SALHJHLRYJAPRANCNFSM4OAY3WBA.

Addressed in latest devel


Now that this is merged upstream, I would prefer this point to the upstream repository (and eventually, the upstream release when there is one)

Done. There is no release to which I can point.


Test svgo for images of mathematical formulae

We tried to use svgo for SVG images displaying of mathematical formulae generated by MathJax.
While this leads go good results in many cases, it fails for at least one case.
Thus, we need to understand in which cases svgo guarantees to keep the spatial alignment of the glyphs used in the formulae and in which cases, this cannot be guaranteed.
Disclaimer: I'm aware that SVGs are not a good format for mathematical formulae and MathML should be used instead. However, the svg fallback images are required at the moment since not all browsers support MathML reasonably well.

Quite a bug! Thanks for reporting!


drawer doesn't close when you open it via gesture  and not swiping to the end and leave it half way

Current Behavior
when I open a drawer via gesture and I don't swipe to the end, I can't close it by clicking the outside screen.
but when I swipe the drawer fully to the end  (even after it has opened), clicking outside would close it.
currently using "react-navigation-drawer": "^2.1.0"

Hey! Is it still happening to you? If so, it would be nice if you could provide runnable repo.


first custom build

This is not the place to push your custom changes, assuming this was a mistake and you meant to open a PR elsewhere or didn't mean to open one
Closing

Oh, yes, this was a complete accident, it seems I somehow unintentionally created a pull request while fiddling with vscode addons. My apologies.

Easy mistake! Thank you for clarifying


feat: Automate release

Untested. You'll need to set up an NPM_TOKEN secret for this to work.
Should fix #44 once triggered.

I prefer to do them manually and also don't like package-lock.json files in the repository, sorry.

I don't understand why though. Automated releases are more reliable, and easier to fix when something like this inevitably goes wrong. There are heaps of articles explaining why committing lock files are a good idea; do you have any particular issues with it? One argument I've heard against NPM lock files in particular is that diffs are ugly, which can be fixed by using Yarn instead.


Add persistence tests using "malicious" skops files

We designed the skops persistence format with the intent of being safe against maliciously crafted skops files. Right now, however, there are not tests that explicitly check that loading these kinds of files. Those tests should be added. Of course, nothing actually malicious should happen, but they should serve as a proof of concept.
Ideally, these tests should also help to increase code coverage, as we currently have some uncovered lines that exist as a safeguard against malicious files (see discussion starting here).

Hey! I'll jump on this, starting to feel a lot better now and I think this would be a good warm up :)


Prometheus rework dicussion

Discussion
Prometheus has a limitation of just scrapping data that is "new" (max of 2 hours old?). We should define/document how we want to store/use data from exporters.

Today, some exporters send data with defined timestamp, some do not. We should standardize this behavior.

allow user to choose between the behavior he wants? (document differences, pros and cons)

easy to maintain different use cases?

not specifying timestamp in metric

we can collect old data at any time (using it as the value of the metric, which does not use the benefices of Prometheus timeseries database store usage and stores unnecessary data)
more storage usage

specifying timestamp in metric

optimizes store usage
if data is not send fast (the 2 hours windows), then Prometheus will not store it.

Allow Pelorus to be deployed using a standard database?

we would be able to send data at any time, but would not have Prometheus timeseries database store usage optimization
easy to integrate with grafana?
easy to maintain different use cases?

also think about webhook use cases, if some workflow must be different

Related to
#932, #933, #934
Requirements

[x] discussion between team members
[x] create issues for next steps

Closing as https://github.com/dora-metrics/pelorus/issues/961 was created and accepted by team members

I don't know if you welcome third party feedback, but just in case:

Allow Pelorus to be deployed using a standard database?

we would be able to send data at any time, but would not have Prometheus timeseries database store usage optimization
easy to integrate with grafana?
easy to maintain different use cases?

Have you guys considered using InfluxDB as the backend to store metrics? Using a database (compatible with Grafana!) has the added advantage that metrics can be imported/exported so it is easier to showcase Pelorus to potential customers without having to keep it running for long periods of time.
When I install Pelorus I don't have a way to measure past DORA metrics before Pelorus was installed, but if I manage to process that information and load it in the DB I can visualize it now with Grafana
It would also solve the workarounds you are building around Prometheus limitation of ingesting metrics with older timestamps.
#933
#943
#961

Yes, we do welcome third party feedback, @PabloHiro :smile: Thanks for sharing this with us
We have talked about using InfluxDB and another one that are compatible with Prometheus and Grafana.
For now, I believe we will keep using Prometheus, because some or the users trust it and use it. We should start adding the possibility to use another DB gradually.


Conflicting with xamarin.forms.maps

When I install this it messes up my Google Play Services saying:
error APT0000: Attribute "imageAspectRatioAdjust" has already been defined
error APT0000: Attribute "imageAspectRatio" has already been defined
error APT0000: Attribute "circleCrop" has already been defined

We are looking into this, most probably a conflict with another package you have referencing a different version of google play services. A patch will be released shortly.

Everything works well until I added this Admob package.
These are the googleplayservices that I have installed (when admob is removed):

Thanks :-)

Fixed on version 1.0.3 please follow next steps:

Remove both Xamarin.Forms.Maps and Xamarinos.AdMob.FormsPlugin
Remove all Xamarin.GooglePlayServices.* dependencies
Add Xamarinos.AdMob.FormsPlugin Ver. 1.0.3
Add Xamarin.Forms.Maps Ver. <IP_ADDRESS>05


Usage splash

Fixes #141
Usage splash screen shows up before home/help buttons.
After it's been answered, it never shows up again.

relaunching the app again just shows home/help buttons
uninstalling the app removes the cookie and would re-prompt if re-installed.

The usage tag gets added to the category (as a suffix) on the the call to tabletInterface.analyticsEvent in iOS.js
[Ignore the fact that it's called iOS.js, it really should have been renamed when we added support for Android]
We're already using all the elements of an analytics event:

category: where in the app (lobby, editor, samples)
action: what they're doing, e.g. new_character
label: data specific to the action, e.g. the name of the character if it's from the library

With this change the categories will have the usage data: e.g. lobby_home, lobby_other, lobby_school
This seemed the least disruptive to existing data, but other suggestions are welcome!

@thisandagain ^^^

Hmm. I wonder if we may want to put it in the label with a delimiter (e.g. home::cat). Putting it in the category or the action will greatly increase dimensionality of the dataset and make it difficult parse / produce navigation flows / goal funnels.

@thisandagain the new version includes all the changes.


Customize syntax groups

Hey man,
Great job with the port!
I do have a feature request, inspired by other themes: can we get a way to customize (in my case, italicize) certain syntax groups?
Here's an example of how Catpuccin does it:
styles = {
    comments = { "italic" },
    conditionals = { "italic" },
    loops = {},
    functions = {},
    keywords = {},
    strings = {},
    variables = {},
    numbers = {},
    booleans = {},
    properties = {},
    types = {},
    operators = {},
},

Hope this makes sense!
Cheers
–LF

  dracula.setup {
        soft = false,
        transparent = false,
        override = {
          ['@comment']= { italic = true },
          ['@function']= { italic = true },
          ['@keyword']= { italic = true },
          ['@field']= { italic = true },
          ['@variable']= { italic = true },
          ['@string'] = { italic = true, bold = true }
          -- ...
        }
      }