Update and segment documentation

The documentation is being split-off into targeted sections, keeping the
landing page focused on deploying and configuring the argo-tunnel
controller.
Other changes of note:

removes helm chart
removes roadmap
updated examples: echo
adds a series of guides

I understand that removing the help chart is an awkward way to resolve
the request for a daemonset variant. With the updates to the documents,
the installation has been simplified and is not driven through helm.
Once the project is connected to CI the contributing instructions will
be added.
fixes #45
fixes #38
fixes #31

Removing the helm chart is a mistake. A very large number of people find helm to be a useful and simplifying tool in deploying applications. I'm very surprised that it would be removed without discussion.

I'm looking for ways to reduce the surface area of what people need to know to quickly deploy use the ingress controller. There is already a lot to grasp in terms of tunnels.
The previous documentation drove users directly into using helm at the expense of both familiarity with helm and complicating secret deployment. After flattening the charts templates into a pre-build argo-tunnel.yaml and updating the docs, it was hard to understand the value add.  The only item left to configure is the namespace for the rbac (and possibly enabling rbac).
I generally find that helm provides a good mechanism to template an initial manifest using, helm template, and then tailor the manifest to my environment or to support configurations not expressed by the helm chart.
I definitely don't want helm to be perceived as a requirement. Given the simplicity of this controller deployment, is there truly value in the helm chart? Was it widely used by the community?

Regarding helm in general, it is both in wide use and also disputed as the best way to manage application deployments.  Even if it is not the easiest path for absolute beginners (or the preferred path for intermediates cough ksonnet), it's a reasonable standard that many people expect.
The chart is certainly in use by some people, so I think it is very fair to steer the intro-level documentation toward a simple manifest, but leave the chart in place for people who want to configure rbac or loadbalancing.

Perfect!  I came to a similar conclusion (independently :P ... I've spent the morning recovering the helm chart and adding a guide).


mlx_lm.convert fails in the absence of a config.json file

Downloading a model using the hugging face cli and then trying to convert it doesn't seem to work:
python -m mlx_lm.convert --hf-path mistralai/Pixtral-12B-2409
[INFO] Loading
Fetching 3 files: 100%|████████████████████████████████████████████████████████████| 3/3 [00:00<00:00, 49344.75it/s]
ERROR:root:Config file not found in /Users/xxx/.cache/huggingface/hub/models--mistralai--Pixtral-12B-2409/snapshots/df119bf36c0cedc6ffdc9ca6c58ebf51f9771ef7
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/opt/homebrew/Caskroom/miniconda/base/envs/mlx/lib/python3.12/site-packages/mlx_lm/convert.py", line 62, in <module>
    main()
  File "/opt/homebrew/Caskroom/miniconda/base/envs/mlx/lib/python3.12/site-packages/mlx_lm/convert.py", line 58, in main
    convert(**vars(args))
  File "/opt/homebrew/Caskroom/miniconda/base/envs/mlx/lib/python3.12/site-packages/mlx_lm/utils.py", line 718, in convert
    model, config, tokenizer = fetch_from_hub(model_path, lazy=True)
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Caskroom/miniconda/base/envs/mlx/lib/python3.12/site-packages/mlx_lm/utils.py", line 502, in fetch_from_hub
    model = load_model(model_path, lazy)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Caskroom/miniconda/base/envs/mlx/lib/python3.12/site-packages/mlx_lm/utils.py", line 413, in load_model
    config = load_config(model_path)
             ^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Caskroom/miniconda/base/envs/mlx/lib/python3.12/site-packages/mlx_lm/utils.py", line 377, in load_config
    with open(model_path / "config.json", "r") as f:
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/Users/xxx/.cache/huggingface/hub/models--mistralai--Pixtral-12B-2409/snapshots/df119bf36c0cedc6ffdc9ca6c58ebf51f9771ef7/config.json'

The snapshot directory contains:
README.md                consolidated.safetensors params.json              tekken.json

Yes two problems here:

MLX LM only converts Hugging Face / Transformers format models which must have a config.json. So you should use this one instead: mlx-community/pixtral-12b-bf16.
MLX LM does not currently support multi model inputs. For that I suggest you check-out MLX VLM


Textarea has border while inputs have not

How to reproduce this bug:

Foundation custom with float grid only.
Put an input + textarea in an html page
The textarea has a border (3d appearance)

What should happen:
The textarea should stay plain as the input box
What happened instead:
The texarea is turned into 3d
Browser(s) and Device(s) tested on:
Firefox 58-60 on PC with Linux
Foundation Version(s) you are using:
6.4.2 (the only that comes in Custom mode)
The problem is in line 457
textarea {
  height: auto;
  min-height: 50px;
  border-radius: 3px; }  <--- THIS IS THE PROBLEM

3d?
I guess you mean the input-radius.
https://github.com/zurb/foundation-sites/blob/develop/scss/forms/_text.scss

$input-radius uses the $global-radius setting which defaults to 3 in the customizer. Change that to 0 before you download your custom Foundation.

Ah, saw your answer now @colin-marshall. Right, this should reset it.

I wonder why the global-radius defaults to 3 on the customizer, but defaults to 0 in the default settings file. Seems like there should be parity between default customizer settings and the default settings file.

The inputs have 3px border-radius, so this is correct.

With a setting of 0:

I was referring to this:
https://github.com/zurb/foundation-sites/blob/develop/scss/settings/_settings.scss#L92

I was referring to this:
https://github.com/zurb/foundation-sites/blob/develop/scss/settings/_settings.scss#L92

I know. I just wanted to show that changing the value to 0 "fixes" the "issue" of @riksoft

Ahhh. My bad, I misunderstood.

With border-radius:3px or 0px the problem is the same: the textarea get the 3d aspect. The only way to avoid it is not writing border-radius at all, because there is no way to override the behaviour (e.g. border-radius:0px or initial doesn't work).
As soon as Firefox find a mention of textarea{border-radius: }, even border-radius:0,  the old fashion 3d aspect comes out and there is not way to get rid of it.
That's why I have to delete the declaration manually from the custom download of Foundation.

To be more clear what I mean with "Old fashion 3D stryle/aspect"...
This is what I get with foundation.

This is what I want and what I get after removing textarea{border-radius:3px} from the Foundation css.

setting border-radius:0px doesn't solve the problem for Firefox, must be completely absent. Probably there is a workaround to override it? Let me know. It's quite inconvenient to remember to modify Foundation every time.

With border-radius:3px or 0px the problem is the same: the textarea get the 3d aspect. The only way to avoid it is not writing border-radius at all, because there is no way to override the behaviour (e.g. border-radius:0px or initial doesn't work).

Do you mean the box-shadow?

Which exact browser do you use?

This is Firefox 55:

And this is Firefox 58:

See https://developer.mozilla.org/en-US/docs/Web/CSS/-moz-appearance#Browser_compatibility and https://foundation.zurb.com/sites/docs/compatibility.html

Please, concentrate :-)
As I said: Firefox from 58 to 60 and custom download of float grid ONLY

Did you enable the forms component in the customizer?

See https://github.com/zurb/foundation-sites/blob/develop/scss/forms/_text.scss#L128

Using the form component with using the form styles make snot much sense ;-)
Left with the form component enabled in the customizer, right without:

And also see https://codepen.io/DanielRuf/pen/eMYaxJ

Make sens to me because I only want a grid, not form components. On the customizer I've deselected anything and selected float grid only.
I've tested also on Windows:
Same problem on Windows with FF 58.
Same problem on Windows 10 with edge and FF 58.
No problem instead on Windows Chrome 63 - 65.
No problem on Windows Opera 51.

I've tested also on Windows:
Same problem on Windows with FF 58.
Same problem on Windows 10 with edge and FF 58.
No problem instead on Windows Chrome 63 - 65.
No problem on Windows Opera 51.

This is Firefox specific and their default styling for the textarea and their behavior for its appearance by default.
Not a bug in Foundation Sites per se so I'm closing this here.
Chrome / Chromium (Opera also uses Chromium) has other appearance styles on form elements. Microsoft too. Only using the form component adds the resets and styles for form elements.

I've solved in a better way:
since I only want the float grid and the Fondation customizer wrongly insert also unwanted form modifications, I've removed the lines from the end of normalize to line 522
basically from
.foundation-mq {
to the line before
.row {
Now the pages keep my style and at the same time I have the grid.
What is the reason why the Fondation customizer adds half form component style when selecting a grid only?

By the way...

This is Mozilla Firefox (and MS) specific and their default styling for the textarea and their behavior for its appearance by default.

It's not true because the default style is runied only by foundation. That's why removing the unwanted lines from foundation, everything is fine now. The problem would be nicely solved, if the customizer didn't modify the form components when I select to download the grid only. This is the real bug.

since I only want the float grid and the Foundation customizer wrongly insert also unwanted form modifications

There is nothing form related added. Just the global styles from normalize I guess.

What is the reason why the Fondation customizer adds half form component style when selecting a grid only?

You mean the border-radius in general? Is is a global style and not tied to the form component as it seems. This might be the only issue here. Not the appearance of the vendors.

It's not true because the default style is runied only by foundation.

No, see my codepen, there is just that what you see in the html and css tab, nothing more.

It's not true because the default style is runied only by foundation. That's why removing the unwanted lines from foundation, everything is fine now.

Just set the border-radius to 0. This should "fix" it.

https://github.com/zurb/foundation-sites/blob/31a199666b13daacf317f1b96e098015e7615626/scss/_global.scss#L189

https://github.com/zurb/foundation-sites/commit/615d90ba5920879e6428727f9f95ab83a34e37da

@colin-marshall should we move this to the form component? But it seems the global styles set some styles for form elements so there are definitely more changes and not only the grid or something else.

In your case I would suggest the sass version where you can include just the grid without the global styles which are always included in the customizer and default import.

There is nothing form related added. Just the global styles from normalize I guess.

This is the part of Foundation CSS that is after Normalize and before the grid itself.
.foundation-mq {
  font-family: "small=0em&medium=40em&large=64em&xlarge=75em&xxlarge=90em"; }

html {
  box-sizing: border-box;
  font-size: 100%; }

*,
*::before,
*::after {
  box-sizing: inherit; }

body {
  margin: 0;
  padding: 0;
  background: #fefefe;
  font-family: "Helvetica Neue", Helvetica, Roboto, Arial, sans-serif;
  font-weight: normal;
  line-height: 1.5;
  color: #0a0a0a;
  -webkit-font-smoothing: antialiased;
  -moz-osx-font-smoothing: grayscale; }

img {
  display: inline-block;
  vertical-align: middle;
  max-width: 100%;
  height: auto;
  -ms-interpolation-mode: bicubic; }

textarea {
  height: auto;
  min-height: 50px;
  border-radius: 3px; }

select {
  box-sizing: border-box;
  width: 100%;
  border-radius: 3px; }

.map_canvas img,
.map_canvas embed,
.map_canvas object,
.mqa-display img,
.mqa-display embed,
.mqa-display object {
  max-width: none !important; }

button {
  padding: 0;
  -webkit-appearance: none;
     -moz-appearance: none;
          appearance: none;
  border: 0;
  border-radius: 3px;
  background: transparent;
  line-height: 1;
  cursor: auto; }
  [data-whatinput='mouse'] button {
    outline: 0; }

pre {
  overflow: auto; }

button,
input,
optgroup,
select,
textarea {
  font-family: inherit; }

.is-visible {
  display: block !important; }

.is-hidden {
  display: none !important; }

Just set the border-radius to 0. This should "fix" it.

That's the first thing I tried, but as I said in my 2nd post, it's impossibile to ovverride. It works in codepen because there is no foundation involved, but not in real case scenario because there is something else that influences such behaviour and I can't check the entire fondation css.  Removing the statement (textarea{border-radius}) is the only way to solve the problem. I haven't found any way to override it.

should we move this to the form component?

Should be nice.

In your case I would suggest the sass version

For me it's not a big problem to change the CSS manually, but for the sake of others, styling the world should be avoided when one choose only a grid, otherwise we loose the scope of choosing a single component.

That's the first thing I tried, but as I said in my 2nd post, it's impossibile to ovverride.

Huh? I set it to 0 in the customizer and I got the following in Firefox 58:

Removing the border-radius rule on this single textarea makes no difference in Firefox.

Weird, Firefox adds the shadow when it is also set to 0. When we remove the rule it does not add the shadow. For me it is a Firefox rendering bug in the normal appearance of the textarea element.

Adding border: 1px solid; fixes it.

There you go: https://bugzilla.mozilla.org/show_bug.cgi?id=1444396
We can not set none in the customizer. Even 0 produces this issue in Firefox.

I know, that's why I was saying there is no way to override the border-radius:3px you've set in Foundation.
However, I've just found a workaround:
border:1px solid
border-color: initial
but it only works without Foundation.
Probably there is something else that influence the behaviour of FF.

Uhm... no... I was wrong its a bug FF+Codepen: when I change something, codepen or FF remember the previous setting and that change the behaviour in the real world (that is, the first load of the page).
In other words, on codepen what you is IS NOT what you get in the first load of the page. In other words, a sequence of modification in the editor is not the same as the same code executed at page load. Bug of codepen or firefox... I don't know but it's a bug.
So my workaround is not working, was only a positive effect of the bug of codepen/FF.

Try the debug mode then: https://codepen.io/DanielRuf/debug/xWbxva

I must say that every browser is s..t!
Apart from my problem with border-radius, try to find a way to revert
textarea{border-style:inset}
I've tried everything. No way.
e.g.
textarea{
-webkit-border-radius: initial;
-moz-border-radius: initial;
-o-border-radius: initial;
border-radius: initial;
border: initial
Not working
Same with "unset" attribute: not working
Not on Firefox nor on Chrome (both latest versions).
On Chrome, border-style:initial remove the border completely.
Same for the border-color: there is not way to revert a change because initial turns to black both on FF and Chrome. Same usding unset instead of initial.
Chrome has the only advantage that border-radius:0 can revert border-radius:1px, but same problem for all other attributes of the border.

I must say that every browser is s..t!

Well, that is why we apply appearance: none in the forms component.

Yeah, in fact using the entire framework is not a problem. The problem arises in the half way, just like my case where I downloaded only the grid but the css also brings in some setting that I think should be in the form module only.
Basically the only 2 ways to go are:

Not touching the defaults because the attribute "initial" is useless on every browser on planet. Even the simple use of textarea{border: 1px solid} implicity add border-color:black both on Chrome and FF instead of keeping the initial value and cannot be reverted. It's a mess.

Setting everything to be sure of every value, just like BS, Foundation, and many other frameworks. The problem is that not eveyone want do that because there is already a project with it's own style.

In my case I need point 1, so I would benefit of a better separation of code in Foundation components.

In the customizer I've checked float grid + Forms. "Forms" remove the border so it solves the problem of the inset 3D, however introduces more complex problems to me. E.g.

I've lost the responsiveness: everything stay on "small" setting.
column small-12 medium-3 doesn't work anymore.

A  that was OK, centered in the page, is now has:
a) micro labels
b) the labels are still centered as they should
c) but the input are on the contrary all the way left

so I'd better to stick to my solution of downloading the grid and removing manually the code that damage the textarea.

I've lost the responsiveness: everything stay on "small" setting.
column small-12 medium-3 doesn't work anymore.

That should not be. Please open a new issue for this with a codepen.

Same for the other.

@colin-marshall what do you think should we do with the cudtomizer issue (border-radius: none not possible?

That should not be. Please open a new issue for this with a codepen.

About the point 1 (the loss of responsiveness)
probably is because the float grid is not included in the "Complete" download.
About the problem 2 (inputs that go on the left and micro labels that stays on the center)
it's only a matter of making the html form specific for Foundation in the first place. Adding "Forms" to the custom download now, for pages not specifically designed for Foundation, generates problems at every inputs.

probably is because the float grid is not included in the "Complete" download.

xy-grid is the new default grid. Was not clear enough that you used the normal download.

Well, forms should have the recommended and supported markup / structure.

xy-grid is the new default grid. Was not clear enough that you used the normal download.

There were 2 different problems. I tried the full download just to be sure the problem to the form was not due to the lack of something else.
However, in the end, I'm using the float-grid for maxi compatibility backwards and from the CSS I;ve removed the line about border-radius, and that's perfect for my need.
Thanks for your patience :-)
PS: this is the most interactive assistance I've ever seen! :+1:


MySQL's BINARY type being mapped to a JSON value instead of Vec

Bug Description
I am trying to build a small controller to a database, deliberately not using an ORM, and encountered some weird behavior when working with MySQL BINARY columns.
And even though I have searched the internet quite some time, it seems to me that noone else encountered this issue before, at least I was not able to find any other mentions of that, making me think (and hope) that I just did something wrong in my setup.
So I set up a test table only containing a column 'guid binary(16) not null' with the following statement: create table test(guid binary(16) not null);
I have also placed the necessary DATABASE_URL into a .env file, to get compile-time type checking in the query! and query_as! macros.
The problem is the following:
When i do
sqlx::query!(         "SELECT guid FROM test"     )     .fetch_all(&mut conn)     .await?;
and iterate over the rows, the attribute 'guid' is given to me as type 'serde_json::Value' by the rust-analyzer extension in VSCode.
When I instead do
sqlx::query!(         "SELECT CAST(guid AS BINARY) AS guid FROM test"     )     .fetch_all(&mut conn)     .await?;
that attribute suddenly becomes a 'Option<Vec<u8, Global>>'.
According to the documentation of the MySQL types here, a BINARY column should be mapped to either &[u8] or Vec.
What's confusing me is that 'guid' already is a BINARY column, so a cast to BINARY should not change anything concerning the type mapping.
What's also interesting is that when trying to use the query_as! macro, the results are similar.
When working with the TestOption struct (shown below in reproduction steps) and the CAST within the SELECT statement, it works wonderfully.
But when I use the simple Test struct with just a Vec, the type checker complains:
the trait bound Vec<u8>: From<JsonValue> is not satisfied
the following other types implement trait From<T>:
<Vec as Frombytes::bytes::Bytes>
<Vec as Frombytes::bytes_mut::BytesMut>
<Vec as From>
<Vec as Fromstd::string::String>
<Vec as From<&str>>
required for JsonValue to implement Into<Vec<u8>>
This shows again, that the binary column does not get interpreted as binary data, unless "being forced to" (I guess).
Furthermore, when inspecting the results of 'cargo sqlx prepare', the columns are actually reported differently.
For "SELECT guid FROM test", i get:
"columns": [       {         "ordinal": 0,         "name": "guid",         "type_info": {           "type": "String",           "flags": "NOT_NULL | BINARY | NO_DEFAULT_VALUE",           "char_set": 63,           "max_size": 16         }       }     ]
But for "SELECT CAST(guid AS BINARY) AS guid FROM test", i get:
"columns": [       {         "ordinal": 0,         "name": "guid",         "type_info": {           "type": "VarString",           "flags": "BINARY",           "char_set": 63,           "max_size": 16         }       }     ]
Yet both versions retain the 'BINARY' flag, indicating to me that it indeed gets recognized as binary data, but not necessarily treated as such.
I am not sure what exactly is going wrong. I sincerely hope that it's just a mistake on my side, but with a minimal setup like that and the docs not mentioning any more requirements to use BINARY columns, I don't think that's it.
Also, but just a side note: I have already tried working with SeaORM, which  did correctly map BINARY columns to Vec.
And just for completeness: Similar errors arise when enabling the 'uuid' feature and trying to parse the column as a Uuid, the problem being that apparently an Option<Vec> can not be parsed to a Uuid, but I don't care about that for now.
Minimal Reproduction
Contents of my main.rs (the singular source file):
`use sqlx::{self, prelude::FromRow, Connection, Error, MySqlConnection};
#[derive(FromRow)]
struct Test {
guid: Vec
}
#[derive(FromRow)]
struct TestOption {
guid: Option<Vec>
}
#[tokio::main]
async fn main() -> Result<(), Error> {
let mut conn = MySqlConnection::connect("mysql://[user]:[password]@localhost/test").await?; // The same path as in the .env file
// Repeated to show every different combination tried
let res = sqlx::query!(
    "SELECT guid FROM test"
)
.fetch_all(&mut conn)
.await?;

for _row in res {
    // type: serde_json::Value
    _row.guid; // Inspect at these points with rust-analyzer
}

// This one works
let res = sqlx::query!(
    "SELECT CAST(guid AS BINARY) AS guid FROM test"
)
.fetch_all(&mut conn)
.await?;

for _row in res {
    // type: Option<Vec<u8, Global>>
    _row.guid;
}

// This one errors out
let res = sqlx::query_as!(Test,
    "SELECT guid FROM test"
)
.fetch_all(&mut conn)
.await?;

for _row in res {
    _row.guid;
}

// This one is allowed
let res = sqlx::query_as!(TestOption,
    "SELECT CAST(guid AS BINARY) AS guid FROM test"
)
.fetch_all(&mut conn)
.await?;

for _row in res {
    _row.guid;
}

return Ok(());

}
`
And to that a local database 'test' containing the described table 'test':
create table test(guid binary(16) not null);
+-------+------------+------+-----+---------+-------+ | Field | Type       | Null | Key | Default | Extra | +-------+------------+------+-----+---------+-------+ | guid  | binary(16) | NO   |     | NULL    |       | +-------+------------+------+-----+---------+-------+
If I am missing anything here, I'll be glad to add that.
Info

SQLx version: 0.7.4
SQLx features enabled: (according to 'cargo add sqlx':) _rt-tokio, any, json, macros, migrate, mysql, runtime-tokio, sqlx-macros, sqlx-mysql, tls-rustls (["macros", "tls-rustls", "mysql", "runtime-tokio"] being the feature selection in Cargo.toml)
Tokio version 1.37.0 with features ["full"]
Database server and version: 8.0.36 MySQL Community Server - GPL
Operating system: Debian GNU/Linux 11 (bullseye)
rustc --version: rustc 1.76.0 (07dca489a 2024-02-04)

What I forgot to mention is that interestingly, it works if I don't use macros:
let res = sqlx::query_as::<_, Test>(         "SELECT guid FROM test"     )     .fetch_all(&mut conn)     .await?;
This gives me a Vec without complaining, and I am able to print results of that using the 'hex' crate as an additional dependency.
And this snippet also works, when I enable the 'uuid' feature and change the type of my guid attribute to uuid::Uuid.


Indentation Errors on Auto-Generated Binding Functions

Description
Some auto-generated binding functions have unnessary nested indentations, these indentations are causing some pages to load slowly, and some like 'funcref_collections' to not load at all.
To Reproduce
go to: funcref-collections
What was Expected
A well indented page that does not hang on any browser
Additional context
Upon investigation: this has to do with some patterns of code used in the automatically generated markdown that indicate an indentation to zola (some combinations of '>' with other characters)
*Screenshots

Resolved in PR #1198


work on buildcraft

want the Universal Cable to work whit buildcraft when they are moving back to MJ and don't get a simple way to keep all MJ you get over without a convertor and it's not simple to get a cnvertor mod to work whit 1.12.2

This looks more like a feature request. Please open an ticket, not a pull request with a totally unrelated commit from someone else.


afterRender instantMove

If I use this code to scroll to the second section after scrollify has rendered, the page jumps to the correct section and then immediately jumps to the top of the page.
             afterRender:function(number) {
                $.scrollify.instantMove(1);
              }
Is scrollify jumping the page to the top and is there a way for me to prevent this?
If I use .move instead of .instantMove this doesn't seem to be an issue.

If you set sectionName to false, do you still see the issue?

I had it set to false but I tested it both ways and saw the same issue. Strangely now that I've let it sit for  half an hour and came back to it, it's working as expected.
Thanks for the incredible plugin, it's really amazing. I'm assuming this was my error but I don't really know what I did to solve it.


Bower

Hi,
Would you consider putting this on bower? Since React is there also it would be great to have Baobab :-)
One strategy here is to create a separate repo that only contains the build files of Baobab, "baobab-bower".
Since it is based on "tags" the workflow can be a bit confusing when sharing repo. At least I tend to forget using tags ;-)

The library should be available through bower now.

Sweet stuff! Thanks :-)
I am writing up an article on using this with React in a flux architecture. Just have to do a bit more research, explore testing etc.


Mac OS installation error

Hi everyone!
Trying to install Devito on my machine I get an error that seems to be related to pytest. I get the following output from terminal:
installation_error_devito.pdf
My machine specs are:
macOS Mojave 10.14
2.2 GHz Intel Core i7
16 GB 1600 MHz DDR3 memory
and Intel Iris Pro 1536MB graphic card
Does anyone have an idea of why this might be happening? Cheers!

Hey dekape, try asking that on Devito's Slack.
There's an exclusive channel for problems with installation.
You can have yourself an invite through:
https://opesci-slackin.now.sh/

By the way, which installation method are you trying?
You can find installation instructions here:
https://www.opesci.org/devito/download.html

What happens if you type
pip install coverage
?

Hi @dekape , did you fix this eventually, and if yes, how?

I assume this was fixed, feel free to reopen otherwise


KAFKA-7000: update assignment in Consumer#position

Call ConsumerCoordinator.poll in Consumer.position to ensure we have
updated assignment metadata before potentially throwing an exception regarding
our assignment.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@guozhangwang @hachikuji ,
Do you mind taking a look at this?
It's the root cause of #5107 failing system tests.
More generally, this fixes a requirement to call poll(0) after subscribing, when there otherwise shouldn't be one.

I've synced with @vvcephei that leads to this JIRA. Compared with committed(), position() does not try to make sure coordinator is ready. So without poll() call the sequence subscribe(), position() will fail, but subscribe(), committed() will not. I think it is better to not enforce users calling poll() in between, since the new API can not pass in 0

retest this, please.

The failing test is a result of this change: The test calls position within a consumer rebalance listener, resulting in an infinite regression. Here's part of the stack trace:
...
	  at kafka.api.PlaintextConsumerTest$$anon$3.onPartitionsRevoked(PlaintextConsumerTest.scala:193)
	  at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.onJoinPrepare(ConsumerCoordinator.java:464)
	  at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.joinGroupIfNeeded(AbstractCoordinator.java:387)
	  at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureActiveGroup(AbstractCoordinator.java:331)
	  at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.poll(ConsumerCoordinator.java:330)
	  at org.apache.kafka.clients.consumer.KafkaConsumer.position(KafkaConsumer.java:1614)
	  at org.apache.kafka.clients.consumer.KafkaConsumer.position(KafkaConsumer.java:1581)
	  at kafka.api.PlaintextConsumerTest$$anon$3.onPartitionsRevoked(PlaintextConsumerTest.scala:193)
	  at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.onJoinPrepare(ConsumerCoordinator.java:464)
	  at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.joinGroupIfNeeded(AbstractCoordinator.java:387)
	  at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureActiveGroup(AbstractCoordinator.java:331)
	  at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.poll(ConsumerCoordinator.java:330)
	  at org.apache.kafka.clients.consumer.KafkaConsumer.updateAssignmentMetadataIfNeeded(KafkaConsumer.java:1215)
	  at org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:1178)
	  at org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:1112)
	  at kafka.api.PlaintextConsumerTest.testMaxPollIntervalMsDelayInRevocation(PlaintextConsumerTest.scala:208)

I have updated the test to avoid the recursion. I think the test still evaluates the same condition, namely that the commit occurs and succeeds.

Retest this, please.

Note to self: This will need a cherry-pick PR to 2.0 branch.

SUCCESS
9190 tests run, 8 skipped, 0 failed.
--none--

Jenkins is acting wacky. Both the builds passed.


Improved comments

Improved both .html and .py comments, to a better standard

Someone validate this please


Can't load any notebook

I created a new notebook using marimo edit test.py, then close marimo and I try to load it in vscode, both with Open as vscode notebook and Start in marimo editor, but both don't work.  Marimo is installed in the virtual environment using uv in the pyproject.toml.  But when I try to load the notebook
When I open it as a vscode notebook, it is stuck at loading:

Then here is the log in Output for marimo
2024-12-13 13:19:44.043 [info] marimo extension is now active!
2024-12-13 13:19:44.043 [info] [server-manager]: Could not recover any state
2024-12-13 13:19:44.043 [info] Opened notebook document marimo-notebook
2024-12-13 13:19:44.043 [info] Showing a new marimo notebook
2024-12-13 13:19:44.043 [info] Checking server...
2024-12-13 13:19:44.043 [info] [server-manager]: Starting server...
2024-12-13 13:19:44.043 [info] Using interpreter: c:\work\ML\notebooks\.venv\Scripts\python.exe
2024-12-13 13:19:44.043 [info] Using interpreter: c:\work\ML\notebooks\.venv\Scripts\python.exe
2024-12-13 13:19:47.923 [info] [server-manager]: Server started at port 2818

I tested in vscode normal and vscode insider.  Both have the same problem.

Hitting this error now... I've been working for a couple of hours without issues, but something made it "break".


adding license to populate fake data

The basic default license is now added for datasets created in populate fake data. This seemed good enough.

I pushed to fix formatting.


Support for modify transformer configurations in playground

We can write the configuration like this
{
  "plugins": ["transform-typescript", "transform-parameters"],
  "sourceType": "module"
}

We need to support the json syntax and then deserialize the configuration when running the transformer

Can we refactor this using a modern front-end framework before doing this? As more features are added I think a vanilla.js-based implementation would become more cumbersome and difficult to maintain.
Additionally, we should use monaco to replace it with codemirror. monaco has better API and is easy to support multiple languages. (this configuration needs json syntax)
We can refer to https://ast.sxzz.moe to complete the refactoring. Thank you for your amazing ast explorer for inspiring me! @sxzz

Let's dog food ourself, you know what to do ;-)

Should we also build the playground in the website repo? I see biome do this https://github.com/biomejs/website/blob/dfed531a1bea6f2bef648e7014f84e530c436627/package.json#L32

Should we also build the playground in the website repo? I see biome do this https://github.com/biomejs/website/blob/dfed531a1bea6f2bef648e7014f84e530c436627/package.json#L32

I don't think it's needed, I checked vue playground and swc playground neither of them is on the website. Let's keep the website purely static

Close as duplicate.


Ignoring certain prefixes?

Is there a way to ignore certain prefixes?
Use Case
In my postcss configuration, I run

postcss-unprefix
postcss-remove-prefixes
autoprefixer

However, certain prefixes like -webkit-font-smoothing should not be removed as they have no corresponding un-prefixed version.

Hey @mayani. There isn't a way to currently ignore certain prefixes, but I definitely think taking an optional array of regex/strings to ignore would be 👌 👍 . I've added it to my todo list for when I can get around to it, but if you wanted to take a stab at a PR that'd be great too!


clean does not convert 'true' to true or 'false' to false for booleans

Not sure if this was intended, but when cleaning a boolean field with a string of 'true' or 'false' , it does not convert it accordingly.
Example:
const schema =  new SimpleSchema({ test: { type: Boolean }});

let dataTrue = { test: 'true' };
schema.clean(dataTrue);
console.log(dataTrue); // { test: 'true' }
schema.validate(dataTrue); // throws error

let dataFalse = { test: 'false' };
schema.clean(dataFalse);
console.log(dataFalse); // { test: 'false' }
schema.validate(dataFalse); // throws error

Note only has a minor use case

Reason for converting 'true' to true / Use case:

If data is attached to the html using the data attribute, it will only accept a string. When parsing it later it would be convenient to have clean convert it properly.

I understand if it does not convert 'false' to false because Boolean('false') === true, but converting either non empty strings to true or at least 'true' to true would make sense in my opinion; however, if this is intentional that's okay I already have a workaround.

I actually started to write a patch for this, but realized that converting from String to Boolean is tricky because there isn't one obviously right way to do it, so you'd end up picking an arbitrary mapping if you only had one implementation inside SimpleSchema. For now you can either do the conversion before passing in to SimpleSchema, or use autoValue on a per-field basis to do type conversion.
An interesting and powerful way to solve this issue and similar ones in the future would be for SimpleSchema to provide a pluggable type conversion system. The user could provide an function at the global (all SimpleSchemas within my project), schema instance, or field level (more specific overriding for the same conversion type) for converting to the target field 'type'. SimpleSchema could ship with some sensible options for common type conversions like String -> Boolean and you could choose the ones you want to use at the scope you want them to apply, sort of the way error message overriding works now.
The system could use one function for each target value (ie Any -> Boolean, Any -> Number) or one function for each pair (ie String -> Boolean, String -> Number, Number -> Boolean).
@aldeed Any sense of whether a more general solution like this would be widely useful? Does the problem come up often enough to justify the extra work?

@ro6, yeah, cleaner plugins is something that has been on the nice-to-have list for some time. I didn't get it into v2, but hopefully eventually. If it's something you want to work on, let me know.
As for the original request, I think I'd be OK with having the exact strings "true" and "false" converted to their boolean values and with having the Numbers 1 and 0 converted to true and false respectively since those are pretty obvious and common conventions. If someone wants to add it, the code in v2 is here: https://github.com/aldeed/node-simple-schema/blob/master/lib/clean/convertToProperType.js

Created an issue for this in the NPM repo


Lots of noise versus 433Utils version...

I'm trying to run the Raspberry Pi GPIO RF Switch component on home-assistant but when trying to use rpi-rf_recieve, I get lots of noise when pressing down the remote button...

pi@raspberrypi:~ $ sudo rpi-rf_receive
2016-12-31 16:50:06 - [INFO] rpi-rf_receive: 505568 [pulselength 79, protocol 3]
2016-12-31 16:50:06 - [INFO] rpi-rf_receive: 243428 [pulselength 80, protocol 3]
2016-12-31 16:50:06 - [INFO] rpi-rf_receive: 131136 [pulselength 398, protocol 5]
2016-12-31 16:50:06 - [INFO] rpi-rf_receive: 521967 [pulselength 81, protocol 3]
2016-12-31 16:50:06 - [INFO] rpi-rf_receive: 505568 [pulselength 80, protocol 3]
2016-12-31 16:50:06 - [INFO] rpi-rf_receive: 131072 [pulselength 411, protocol 5]
2016-12-31 16:50:06 - [INFO] rpi-rf_receive: 15 [pulselength 80, protocol 3]
2016-12-31 16:50:06 - [INFO] rpi-rf_receive: 505568 [pulselength 79, protocol 3]

Here's what I get with RFSniffer included with 433Utils...

pi@raspberrypi:~/433Utils/RPi_utils $ sudo ./RFSniffer
Received 4543804
Received 4543804
Received 4543804
Received 4543804
Received 4543804
Received 4543804
Received 4543804

Likewise when sending the code via rpi-rf_send nothing happens, but it works with 433Utils send command.
Any help would be greatly appreciated!

Same problem here, same symptoms. Using this Transmitter and Reveiver on a Raspberry Pi 2 w. Home Assistant

Same, I also noticed it was chewing up about 60% cpu on my pi

+1

There may be some timing issues with using Python instead of bare C code.
Unfortunately, GPIO flipping is quite CPU intensive (especially on the Pi 1).
If I have some spare time left, I'll have a look at possible time/cpu tradeoff optimizations.

@milaq and about the filter (protocols) used by 433Utils? When I run ./RFSniffer the receive code is stable and continuos. How can I do the same through of rpi-rf_receive?

Try my solution: https://github.com/milaq/rpi-rf/pull/38

I think that in some cases it is better to watch for only one protocol. At least it is a very nice solution to let the user decide if sniffing is the main goal, or watching for only protocol 1. (passed by a parameter to init)
It looks a bit smoother:
2019-02-12 22:35:58 - [INFO] rectest: Listening for codes on GPIO 17
2019-02-12 22:36:03 - [INFO] rectest: 4593709 [pulselength 551, protocol 1]
2019-02-12 22:36:05 - [INFO] rectest: 4593709 [pulselength 549, protocol 1]
2019-02-12 22:36:07 - [INFO] rectest: 4593709 [pulselength 548, protocol 1]
2019-02-12 22:36:12 - [INFO] rectest: 4593709 [pulselength 548, protocol 1]

https://github.com/enesbcs/rpi-rf/commit/6f6018d933c1daefe4e0e5404e860f274a85cb39


Types deserialize differently during session in which they were written

E.g.
julia> using Arrow, UUIDs

julia> table = (;x = [uuid4() for _ = 1:5])
(x = UUID[UUID("03fec02f-3d33-4cf8-88e0-1e152faccff7"), UUID("a789baa7-9059-4bc4-b0d9-2af1dca4bf88"), UUID("2a4ecfd7-049e-
468d-8fed-8f967b732ee0"), UUID("91b9cad6-b84c-4ee8-aeaf-7448778fb1d5"), UUID("39edead7-1670-430a-8e4d-fefe3615c2d0")],)

julia> Arrow.write("uuids.arrow", table)
"uuids.arrow"

julia> Arrow.Table("uuids.arrow")
Arrow.Table: (x = UUID[UUID("03fec02f-3d33-4cf8-88e0-1e152faccff7"), UUID("a789baa7-9059-4bc4-b0d9-2af1dca4bf88"), UUID("2
a4ecfd7-049e-468d-8fed-8f967b732ee0"), UUID("91b9cad6-b84c-4ee8-aeaf-7448778fb1d5"), UUID("39edead7-1670-430a-8e4d-fefe361
5c2d0")],)

In a new session:
julia> using Arrow, UUIDs

julia> Arrow.Table("uuids.arrow")
┌ Warning: unsupported ARROW:extension:name type: "JuliaLang.UUID"
└ @ Arrow.ArrowTypes ~/.julia/packages/Arrow/CyJ4L/src/arrowtypes.jl:141
Arrow.Table: (x = NamedTuple{(:value,),Tuple{UInt128}}[(value = 0x03fec02f3d334cf888e01e152faccff7,), (value = 0xa789baa790594bc4b0d92af1dca4bf88,), (value = 0x2a4ecfd7049e468d8fed8f967b732ee0,), (value = 0x91b9cad6b84c4ee8aeaf7448778fb1d5,), (value = 0x39edead71670430a8e4dfefe3615c2d0,)],)

I believe this is due to the write-time registration of types at
https://github.com/JuliaData/Arrow.jl/blob/3ab2b18829c1656198a85759360389b6bbb22ab3/src/arraytypes/struct.jl#L86

(The workaround is to just call Arrow.ArrowTypes.registertype!(UUID, UUID) before deserializing. But I think the hidden statefulness is still confusing / problematic).

The UUID case is now fixed (defined by default in Arrow) and we've updated the docs to mention the need to call registertype!. I'm considering some larger changes to type serializing and such, so this might be something we make easier with that.

The UUID case is now fixed (defined by default in Arrow) and we've updated the docs to mention the need to call registertype!. I'm considering some larger changes to type serializing and such, so this might be something we make easier with that.

@quinnj what's the motivation behind https://github.com/JuliaData/Arrow.jl/blob/3ab2b18829c1656198a85759360389b6bbb22ab3/src/arraytypes/struct.jl#L86? Is it just to give the "convenience behavior" listed in the OP of 88 or is there a deeper reason? If it's just the former, I wonder if it's better just to remove it...I ran into another issue related to that just now.
I'm essentially implementing the following (which is also why I needed https://github.com/JuliaData/Arrow.jl/pull/150):
struct Foo ... end

struct _FooArrow ... end

Foo(::_FooArrow) = ...

Arrow.ArrowTypes.registertype!(Foo, _FooArrow)

Arrow.ArrowTypes.arrowconvert(::Type{_FooArrow}, f::Foo) = ...

the above in theory would allow me to have full control over Arrow <-> Julia conversion for my Foo type.
The problem is that Arrow.jl is automatically calling ArrowTypes.registertype!(_FooArrow, _FooArrow) even though I don't want it to :( as a caller I can't really think of a scenario where I would want auto-registration, but I could be missing something.
Even if we can't get rid of it in general, would it be possible to gate this behavior behind a flag passed to Arrow.write (autoregister=true)?

Just to add another reason in favor of removing it, mutating the global registration dict at write-time seems like it could be an issue for concurrent writing from different threads (ref https://github.com/JuliaData/Arrow.jl/issues/90#issuecomment-797516022 for other thread safety issues). Whereas the user could be sure to always manually register outside the threaded region of code.

Yeah, these are good points for removing the auto registering. The main reason for having it was convenience.

@jrevels , can you explain your use-case/example a bit more? What I dont' quite follow is how _FooArrow will be supported? The 2nd argument to registertype! should be a native arrow type that your custom type converts to.

Hold up, don't mind me. I'm digging back through all the code and in the structs.jl file we know how to serialize a _FooArrow, so yeah, I think I understand the example better now.

Wait, backsies again. So the problem with not autoregistering, is that without ArrowTypes.registertype!(_FooArrow, _FooArrow), we don't know how to deserialize the struct, it would just deserialize as a NamedTuple. Here's where my thinking is going, though I recognize the code itself doesn't currently reflect this vision:

Stop autoregistering StructTypes, we'd require users to call ArrowTypes.registertype! for custom types
By default, we'd assume that Arrow.Types.registertype!(::Type{T}) where {T} = registertype!(T, T), which means the custom struct would be serialized as-is, and when deserializing, we'd just call (essentially) T(serialized_fields...)
For more customizability when serializing/deserializing custom structs, you would do something like: ArrowTypes.registertype!(T, @NamedTuple{field1::Int, field2::String}), where, e.g., you only want to serialize field1 and field2 of your custom type. This would then require a corresponding definition like: ArrowTypes.arrowconvert(::Type{@NamedTuple{field1::Int, field2::String}}, x::T) = (field1=x.field1, field2=x.field2), though I think we could provide some kind of auto-convert fallback, like: ArrowTypes.arrowconvert(::Type{T}, x) where {T <: NamedTuple} = (; nm=>getfield(x, nm) for nm in names(T))
In addition, you'd be able to define a custom ArrowTypes.arrowconvert(::Type{T}, x::@NamedTuple{field1::Int, field2::Strong}) = T(x.field1, x.field2); this would allow "hooking" into deserialization, to fix cases like https://github.com/JuliaData/Arrow.jl/issues/135

So the problem with not autoregistering, is that without ArrowTypes.registertype!(_FooArrow, _FooArrow), we don't know how to deserialize the struct, it would just deserialize as a NamedTuple.

Ah, but for me this is the desired behavior :) I want it to deserialize as NamedTuple unless I, the caller, tell it explicitly not to. Right now it feels like Arrow.jl is making the decision for me, and it's making the wrong one (AFAICT).
Reopening this issue as it seems like the discussion may lead to some action items :)

ref https://github.com/beacon-biosignals/Onda.jl/pull/68 for a motivating example.
my thoughts are very rough/not super well-considered yet, but off the top of my head, here are my big "wants" (some of these might already be possible w/ existing behavior):

For the current Dict-based registertype! mechanism to somehow be replaced/augmented by method dispatch (motivation here: https://github.com/beacon-biosignals/Onda.jl/pull/68/files#diff-9d1b70fd041b1dbbe08ff4096cf1c68daa131b7d249d2ba3101e9079e129f44cR505 ; if there's another way to do this that I'm not seeing with the current system, that'd be dope). The barriers here AFAICT are a) dynamic dispatch might be slower than the current Dict look up during deserialization, so we'd have to amortize it by doing it up front based on the present extension metadata (I think this should work?) and b) this mechanism would be less dynamic than registertype! currently is (I would be happy to make it less dynamic, but maybe there's a use case where the extra dynamism is useful?).
For there to be very clear/well-named/well-documented/separate "pre-serialization hook" and "post-deserialization hook" transformations. I'm not overly concerned with names as long as the duality is clear, e.g. lower/raise, toarrow/fromarrow, etc. I wouldn't want to use a single function for both as, IME, doing so forces the caller to "do more than they intend to do" by overloading that function. Like, I want to be able to define a pre-serialization hook to go from A in Julia -> B in Arrow, without implying anything about the transformation behavior of A in Arrow -> B in Julia.
For me to be able to specify/toggle behavior at the callsite. i.e. turn off the pre/post-hooks for a specific type during a specific read/write operation. Overriding these sorts of global behaviors is really useful in practice for e.g. migrating data between different representation versions w/o needing to adjust your running environment.

preserving some relevant convo from the Julia Slack (https://julialang.slack.com/archives/C674VR0HH/p1615846377461400?thread_ts=1615681758.430500&cid=C674VR0HH)

Closing now that #156 is merged/tagged


"Baseline" community detection methods

Description
Create a demo of one known community detection algorithm on one  ground-truth dataset. Perform evaluation with ground truth. Visualise the results.
Done Checklist

[x] Produced Jupyter notebook for required functionality
[x] Code well commented
[x] Evaluation metric is calculated
[x] Results are visualised

@PantelisElinas can you review the notebook here: https://github.com/stellargraph/data-science/blob/devel/communities/Community detection.ipynb


Filter_urls

How do I get access to the array urls in the function detail_page ?
class Handler(BaseHandler):
#@config(age=0)
crawl_config = {
"age":0
}
urls = []
start_url = 'http://gilt.com'
domain = 'gilt.com'

#@every(minutes=60 * 60)

def on_start(self):
    self.get_page(  self.start_url  )

def get_page(self,url):

    self.urls.append(url)

    self.crawl(url=url, callback=self.detail_page, timeout=10)

@catch_status_code_error
def detail_page(self, response):
    print (self.urls)
    if response.status_code == 200:
        if self.domain in response.url:
            url = response.url
            body = response.text

            for each in response.doc('a[href^="http"]').items():

                if not (each.attr.href in self.urls):
                    self.get_page(each.attr.href)

Don't do it like that, pyspider is not scrapy, you don't have to manage and deduplicate the urls yourself. Just submit the urls via self.crawl and pyspider will take care the deduplicate things for you.
class Handler(BaseHandler):
    def on_start(self):
        self.crawl(start_url, callback=self.detail_page)

    def detail_page(self, response):
        for each in response.doc('a[href^="http"]').items():
            self.crawl(each.attr.href, callback=self.detail_page)
        return {
            ... # extract information here
        }

And don't use class member variables, pyspider is designed as distributed, member variables may not be visitable in other instance.


Compute density compensation for screen space blurring of tiny gaussians

Why
Current gaussian splatting (both Inria and nerfstudio) doesn't sufficiently deal with the case when rendering tiny gaussians at substantial different resolution than the captured one. The reason is caused by the 0.3 pix kernel screen space blurring applied to the tiny splats.
A tiny splat that has been enlarged by 0.3 pixel can block more gaussians behind it if rendering at lower resolution than the captured one, or looks much thinner than it should be if rendering at higher resolution than the captured one. One would easily observe this artifacts by changing the distance or resolution of rendering.
This issue is acknowledged by the original author of Gaussian splatting, and was addressed in another open source repo.
Addressing this issue has significant benefit in an interactive webviewer, where one zoom in/out to inspect a splat model, and see much less artifacts then before. Another simple quantitative experiment one can do is to train at 1/2 resolution and evaluation at the original resolution, addressing the issue expects to improve metrics.
Solution
The solution is rather simple. We will compute a compensation factor $\rho=\sqrt{\dfrac{Det(\Sigma)}{Det(\Sigma+ 0.3 I)}}$ for each splat and multiply it to the opacity of gaussian before rasterization. The same solution was also proposed in another research paper.
The PR will basically modify the output of rasterize_gaussians to return the compensation factor $\rho$ and  the change allows us to have two modes in nerfstudio's splatfacto: the classic mode which mimic the behavior of official GS, and the new mode which address the "aliasing-like" issue.
See results here (I had to upload the video to my own forked repo's issue due to file size limit).

Needs to run  the formatter black . gsplat/ tests/ examples/ for passing the core tests.

@jb-ye Really great improvement. Amazing work @jb-ye Can't wait to try it out.

Needs to run the formatter black . gsplat/ tests/ examples/ for passing the core tests.

I used a newer version of black. Now updated black with the same version used by devops and re-run the formatter.

Initial discovery of the issue:

https://github.com/graphdeco-inria/gaussian-splatting/issues/294#issuecomment-1772688093

Example showing the effect of the fix:

https://github.com/graphdeco-inria/gaussian-splatting/issues/294#issuecomment-1777782320


LeetCode 209 - Minimum Size Subarray Sum

Given an array of positive integers nums and a positive integer target, return the minimal length of a
subarray whose sum is greater than or equal to target. If there is no such subarray, return 0 instead.
Would like to implement it in Go
HACTOBERFEST2023
@sherigar

please assign it to me

@sherigar - PR - https://github.com/sherigar/HacktoberFest-2023/pull/188


Automate dependency-version selection

This uses the 2.0.x build tools to do what PackageLineup does in dev. (btw, this is also the way we'll do things in dev once we finish the 2.0.x patch).
Changes:

Updated to KoreBuild to 2.0.2-beta-15522
Renamed content/*/*.csproj files that have PackageReference in them to *.csproj.in
Replaced any hard-coded versions with MSBuild properties
Added targets to call GenerateFileFromTemplate on *.csproj.in to generate content**.csproj
Set TreatWarningsAsErrors to true in the projects generated during test to ensure default templates don't have build or restore warnings

@natemcmaster,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@SteveSandersonMS the tests fail for me, something to do with selenium. The test is able to make a new project, build, and launch the server, but fails attempting to launch a browser. What's required to make these pass?
Failed   Templates.Test.SpaTemplateTest.SpaTemplate_Works(targetFrameworkOverride: null, template: "react")
Error Message:
 OpenQA.Selenium.WebDriverException : Cannot start the driver service on http://localhost:49710/
Stack Trace:
   at OpenQA.Selenium.DriverService.Start()
   at OpenQA.Selenium.Remote.DriverServiceCommandExecutor.Execute(Command commandToExecute)
   at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
   at OpenQA.Selenium.Remote.RemoteWebDriver.StartSession(ICapabilities desiredCapabilities)
   at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(ICommandExecutor commandExecutor, ICapabilities desiredCapabilities)
   at Templates.Test.Helpers.WebDriverFactory.CreateWebDriver() in C:\dev\aspnet\templating\test\Templates.Test\Helpers\WebDriverFactory.cs:line 23
   at Templates.Test.Helpers.AspNetProcess.VisitInBrowser() in C:\dev\aspnet\templating\test\Templates.Test\Helpers\AspNetProcess.cs:line 102
   at Templates.Test.SpaTemplateTest.TestApplication(String targetFrameworkOverride, Boolean publish) in C:\dev\aspnet\templating\test\Templates.Test\SpaTemplateTest.cs:line 40
   at Templates.Test.SpaTemplateTest.SpaTemplate_Works(String targetFrameworkOverride, String template) in C:\dev\aspnet\templating\test\Templates.Test\SpaTemplateTest.cs:line 28

the tests fail for me, something to do with selenium

It tries to use Edge if you're on Windows 10, or Firefox if you aren't. Is it possible your system doesn't have the necessary browser?

I'm on the Windows 10 Fall Creators update. I'm guessing this means something in edge changed...

I'm guessing this means something in edge changed...

Sounds very likely.

Template the templateconfig file instead

@natemcmaster Perfect! This must have been a laborious commit to put together, but great job - that looks like it gives us the best result both for the build system and for the developer experience!

:up: :date:
Changes

deleted .template.config/template.json files
added a bunch of parameters to symbols.parameters for package version replacement
dotnet-build produces the template.config/template.json files with hard-coded versions

Still trying to verify this actually works, of course....seeing some weird errors.

Found it. I was using template.json wrong. Everything is working smoothly now. :)

New error, but only on Linux/macOS
 ==> /Users/namc/.dotnet/dotnet new web [/Users/namc/dev/aspnet/templating/test/Templates.Test/bin/Debug/netcoreapp2.0/TestTemplates/37025cf1fb724909ad785b6ef06a34ac]
 [ERROR] Unexpected end when reading JSON. Path 'TemplateInfo[19].Tags.language.Description', line 1365, position 26.
 [ERROR]    at Newtonsoft.Json.JsonTextReader.ParseValue()
 [ERROR]    at Newtonsoft.Json.JsonTextReader.Read()
 [ERROR]    at Newtonsoft.Json.Linq.JContainer.ReadContentFrom(JsonReader r, JsonLoadSettings settings)
 [ERROR]    at Newtonsoft.Json.Linq.JContainer.ReadTokenFrom(JsonReader reader, JsonLoadSettings options)
 [ERROR]    at Newtonsoft.Json.Linq.JObject.Load(JsonReader reader, JsonLoadSettings settings)
 [ERROR]    at Newtonsoft.Json.Linq.JObject.Parse(String json, JsonLoadSettings settings)
 [ERROR]    at Newtonsoft.Json.Linq.JObject.Parse(String json)
 [ERROR]    at Microsoft.TemplateEngine.Edge.Settings.SettingsLoader.EnsureTemplatesLoaded()
 [ERROR]    at Microsoft.TemplateEngine.Edge.Settings.SettingsLoader.WriteTemplateCache(IList`1 templates, String locale)
 [ERROR]    at Microsoft.TemplateEngine.Edge.Settings.TemplateCache.WriteTemplateCacheForLocale(String locale, String existingCacheVersion)
 [ERROR]    at Microsoft.TemplateEngine.Edge.Settings.TemplateCache.WriteTemplateCaches(String existingCacheVersion)
 [ERROR]    at Microsoft.TemplateEngine.Edge.Settings.SettingsLoader.Save(TemplateCache cacheToSave)

Any ideas? I'm stumped on this one.

Open https://github.com/aspnet/templating/issues/63 to follow up on the test failure. The tests pass when parallelization is disabled.

FYI - 2.0.3 preview builds are up now. https://dotnet.myget.org/feed/aspnet-2-0-2-october2017-patch/package/nuget/Microsoft.AspNetCore.SpaTemplates


Update version from 1.2 to 1.3

Update EquinoxProject version (footer) from 1.2 to 1.3

Accepted. Tks!


Sliding for opening the covers in HomeAssistant

Hi,
I do not exactly know if this is the right place, but I think here is the target audience :-) By accident I found out, that I could open the sliders in any opening percentage I want to use. In  another small project I am using "sliders" from here: https://github.com/thomasloven/lovelace-slider-entity-row
If you combine this, you can get something like

which is a card in HA that looks like: (Rolladen is one cover, Rolläden are more than one cover.
type: entities
state_color: true
title: Rolläden
show_header_toggle: true
entities:
  - entity: cover.rolladen
    name: links
    type: custom:slider-entity-row
    step: 1
    full_row: true
    toggle: false
    hide_state: false
    hide_when_off: false
    show_icon: false
    colorize: true
  - entity: cover.l1
    name: L1
    type: custom:slider-entity-row
    step: 1
    toggle: true
  - entity: cover.l2
    name: L2
    type: custom:slider-entity-row
    step: 1
    toggle: true
  - entity: cover.l3
    name: L3
    type: custom:slider-entity-row
    step: 1
    toggle: true
  - entity: cover.l4
    name: L4
    type: custom:slider-entity-row
    step: 1
    toggle: true
  - entity: cover.r1
    name: R1
    type: custom:slider-entity-row
    step: 1
    toggle: true
  - entity: cover.r2
    name: R2
    type: custom:slider-entity-row
    step: 1
    toggle: true
  - entity: cover.r3
    name: R3
    type: custom:slider-entity-row
    step: 1
    toggle: true
  - entity: cover.r4
    name: R4
    type: custom:slider-entity-row
    step: 1
    toggle: true

in ESPSSomfy I had to add a "repeat command" for every of my 8 covers. 2 was enough. Before not adding this, not all covers seem to get the commands.

I hope this helpy others as well. If you think there is a better place for this, than just tell me here, and I can put it somewhere else.
Have fun.
Juergen

Nice finding :) thanks for sharing. Maybe readers here https://community.home-assistant.io/t/esp-somfy-rts-integration/543401 would like it too.
PS: I wonder how you got such  precise timings for up and down.

Hi @alka79,
I just did the timing for each cover for up and down as described in the doc here in espsomfy.
setup -> somfy -> shades -> individual shade .   Than just use a stopwatch for timing, and put in the time in ms I think. Be sure to stop up and down individually, as at least my shades are way different in up and down.
works very accurat, but as the shades do not feedbak their position, it is not working in 100%, only 99,5 :-)
thanks
Juergen

I was surprised by your setting at 19180 ms. That is quite precise ! I was thinking you had some kind of electronic device to measure.
I use a stopwatch too on my smartphone. But I only trust my accuracy at half a second (at best) ;)

Hi @alka79,
that‘s true for sure and I was aware of it, but as I did not know if I was too fast or too slow, I simply took what was shown (for betterr results I should measure each cover 10 times each up and down :-) but still I have a life to live ). It works quit well as it is.


Add uniqueness to certain random values

Is this a regression?
No
Description
Heya! I'm using Falso in unit tests to generate randomized, yet plausible, data, but am sometimes faced with false negatives due to some methods not returning data that's reliably unique. For example if you use randFilePath, there's a chance that it'll return the same path multiple times as it just randomly picks from a fixed list: https://github.com/ngneat/falso/blob/main/packages/falso/src/lib/file-path.json
Would it be worth adding some (light) randomization to methods like this? For example, a random file-path could add a random hash at the end, so you'd end up with (assumed 'duplicate' output):
/usr/src/realbox-62d6d23.gif
/usr/src/realbox-51bd2b9.gif

(Similarly, when talking about file-path specifically, I think it'd be nice if randFilePath() would be a shortcut for randDirectoryPath() + randFileName(), and randFileName() using randFileExt() instead of defaulting to .pdf, but I digress. Happy to open a new issue for that tweak if you'd like to keep these two thoughts separate).
Please provide a minimal reproduction of the bug
Lets say you're in a unit test and mocking an external dependency that modifies a file path, for example:
import { expect, vi, test } from 'vitest';
import { join } from 'node:path';
import { randFilePath } from '@ngneat/falso'

vi.mock(join);

const myFunction = (input) => join('/root', input);

test('Uses join to prefix root to input', () => {
  const mockJoinOutput = randFilePath();
  vi.mocked(join).mockReturnValue(mockJoinOutput);

  const input = randFilePath();

  const output = myFunction(input);

  expect(join).toHaveBeenCalledWith('/root', input);
  expect(output).toBe(mockJoinOutput);
});

there's a decent chance that input and mockJoinOutput are identical, which causes the test to fail sporadically. Ensuring that the output of randFilePath() is unique—or at least more random—prevents that issue.
Please provide the environment you discovered this bug in
Node.js v18.12.1

Do you want to create a pull request?
Yes

Any reason you're not using seed?
https://github.com/ngneat/falso#setting-a-randomness-seed

@NetanelBasal I don't think that fully solves this particular issue does it? It allows repeat tests to get the same values back every time, but it doesn't insure that those individual values are unique from each other in the first place. If I were to rely on seeds as a solution for this, I'd have to go through a number of seeds first to find one that returns unique values, and then use that, whereas I'm hoping randFilePath() could return a unique path regardless of seed used.

Can you create a small stackblitz that explains your point, please?

The smallest explanation I have is:
import { randFilePath } from '@ngneat/falso';

const path1 = randFilePath();
const path2 = randFilePath();

path1 === path2; // This is sometimes true, should always be false

Not sure I agree that randFilePath always should be different, randomness can be the same sometimes. However randFilePath is rather lacking in the amount of return values. There should definitely be a less than 1 in a 100 chance to get the same output.
For your particular case I would just use seed like @NetanelBasal suggested, however I do realise it's unsatisfying.
The question of uniqueness was discussed briefly in #220, but the solution there seemed rather strange imho.

Agree with @PumpedSardines that randomness can be the same sometimes.

OK! Whatever you guys prefer. For my use cases, the high chance of collision is a big hindrance, so I'll rely on an alternative approach 👍🏻


Backend: cache all the remaining trees

With these changes, there are 0 invalidated tree in BasicLinkerBackend for the test suite, whether we use Fewest modules or Smallest modules.
Under Fewest modules, they bring about a 20% speedup. Under Smallest modules, about 7-8%.

LGTM.  But yes, I hope to come back to it.


Explicitly list out tsec exemption

This PR fixes #116459
This implies a few things:

tsec's output is empty so it can be included as a CI check
code introducing new violations need to update the exemption list,
making it clear there is something security-sensitive about the code

I am not sure how I can update tsec's version with the current checks

if I update yarn.lock, there is a check that says I shouldn't
on the other hand if I remove yarn.lock all the other checks fail because nothing builds

@jrieken Could you help ?

@engelsdamien We are now more strict wrt yarn.lock-modification. I have made the tsec update on master (ed10bfb7c4f8856c80d737a0ade60b8bea4ca18f) and things should work now

No worries, thanks. Going forward, I will avoid updating packages in PRs and file an issue instead.


Remove log line from support archive zip.

Description
cherry-pick #3342
How can this be tested?
see #3342

Codecov Report
Attention: Patch coverage is 33.33333% with 6 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-1.2@0d48847). Learn more about missing BASE report.

Files
Patch %
Lines

pkg/logd/logger.go
0.00%
3 Missing :warning:

cmd/csi/init/builder.go
0.00%
1 Missing :warning:

cmd/troubleshoot/builder.go
0.00%
1 Missing :warning:

cmd/webhook/builder.go
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@              Coverage Diff               @@
##             release-1.2    #3346   +/-   ##
==============================================
  Coverage               ?   58.75%
==============================================
  Files                  ?      326
  Lines                  ?    18175
  Branches               ?        0
==============================================
  Hits                   ?    10679
  Misses                 ?     6298
  Partials               ?     1198

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Is it possible to run with TPU on Colab?

It would be great if TPU is possible.

Not yet. Haven’t evaluated this yet but is on my radar.

seems to be the case with Google Colab Pro and GPU activated?

Warning:  multi_tensor_applier fused unscale kernel is unavailable, possibly because apex was installed without --cuda_ext --cpp_ext. Using Python fallback.  Original ImportError was: ModuleNotFoundError("No module named 'amp_C'",)


Feature: easier editing of Lambdas code

Hello,
As a user, I would like to be able to edit my Lambda's code, that were previously exported using this tool.
However it's not easy, because the code is zipped and needs to be unzipped and zipped again each time, I need to edit the code.

Please disable this stale bot, it doesn't make sense to use it, for tool that is not maintained and popular


Sometimes faucet mints 100000 tokens

@andfletcher experienced several times that he received 100k test tokens from the faucet. So he was able to quite easily drain the agent.

The reason was found. The faucet was recently increased to 100k.
As a countermeasurement we can always allocate the amount of tokens to the agent as the user gets from the faucet.

Reset the minted amount to 100, and made the faucet mint to the agent as well. However this is only on the base chain, so the L2 won't be minted for.


fix(nix): vendorHash

This pr fixes the vendor hash issue noted by https://github.com/charmbracelet/freeze/pull/59#issuecomment-2040149907

Thank you!


please unarchive https://github.com/gngpp/ninja

please unarchive https://github.com/gngpp/ninja and run actions please

It is closed source and no longer maintained. Only paid maintenance is done.


Repository for packaged games

@aidalgol, hi!
I have a similar fetcher that I’ve intended to submit to Nixpkgs, but looks like we’ve arrived at a similar implementation roughly at the same time, so I didn’t know that this repository existed 😅
It’d be nice to have a repository for packaged Steam games and game servers (nix-community/steam-games?) since most of them require non-trivial workarounds to run on NixOS, and having them in a single place is good for discoverability. E.g.
• https://github.com/aidalgol/valheim-server-flake
• https://github.com/NixOS/nixpkgs/compare/master...tie:nixpkgs:eco-game-server
• https://github.com/NixOS/nixpkgs/compare/master...tie:nixpkgs:satisfactory-game-server
Alternatively, what do you think about upstreaming Steam fetcher to Nixpkgs?

Yay, someone found this!  You're right, discoverability could be better.  I don't think that putting various packages Steam games (or game servers) into a single repository is necessary for discoverability, or worth the downsides of a monorepo.  I think a GitHub organisation dedicated to nix flakes for Steam games would be more flexible, or even a repo with just a README with links to personal repos (similar to those awesome-something repos for various topics and software).
What do you think about starting a "nix-steam-games" GitHub org?

Just discovered this issue. I had actually tenatively started setting up a repo that is more-or-less what is being talked about here. Right now it just has two games, but I wrote some modules as well for managing servers (including generating a server config file) through Nix.
I'm not sure if how much of that we would want to keep but at the very least I feel like there's some decent ideals that could be copied out of it (like perhaps the general system for servers that I setup). I be happy to transfer ownership of my repo to nix-community or just start fresh if we feel that is better.

Closing due to inactivity.

@aidalgol, sorry, I completely forgot about this issue. I’ve moved my implementation of steam fetcher (and game packages) from a Nixpkgs fork to a separate github:tie-infra/steam-games flake. I would love to use nix-community/steam-fetcher, however, I’m pretty skeptical because changes like #3 get merged without much consideration. That said, feel free to take inspiration from the code, it’s public domain.

@tie That looks like a good way to structure it!  #3 may look as if it was merged without much consideration, but there was discussion on the linked issue, #7.
For a bit of background, when I originally created this flake, along with https://github.com/aidalgol/valheim-server-flake, I received some conflicting advice around overlays from the wider Nix community when I sought assistance around nixpkgs.config.allowUnfree = true; not applying when I tried to use it in my server NixOS config.  Unfortunately, I am still not very confident when it comes to overlays, and so I did not spot the issues that you pointed out in #7.

IIRC nixpkgs.config.allowUnfree = true; is a convenience option in NixOS modules for importing Nixpkgs if it is not defined already. When possible, I prefer using inputs.nixpkgs.nixosModules.readOnlyPkgs and setting nixpkgs.pkgs = pkgs; explicitly to avoid re-evaluating Nixpkgs.
E.g.
https://github.com/tie-infra/nix-config/tree/2c440df032655570215c8d8f1d57907ded51a7f4/nixpkgs.nix
https://github.com/tie-infra/nix-config/blob/2c440df032655570215c8d8f1d57907ded51a7f4/parts/nixos-with-system/default.nix#L6-L8

Could this be re-opened? It still thinks it's a good idea.


feat: new data structure and database storage

This PR makes major changes to the app frontend and backend.

The top level item is now a Household rather than a GibsonsForm (collection). Respondents are nested inside Households and GibsonsForms nested inside each respondent. See the diagram below. (Survey level will be implemented in a future PR)
New screens for creating and editing Households and Respondents have been added.
All above data is now stored in an Isar database instance rather than SharedPreferences.
Import/export code has been updated to maintain compatibility with legacy CSV export format.

There are some outstanding bugs to fix and a lot of cleanup to do however this will be done in subsequent, smaller PRs rather than this one as this PR is already very large.

Known issue: household ID clashes are not handled when creating a new household

Known issue: when a household or respondent is edited and saved, the view household/respondent page doesn't update with new values unless going back and opening the household/respondent again. Reference in new issue upon merge.


Add files via upload

@MKKrisz First stage of verification passed, official domain is szilagyi-eger.hu as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.


[MM-770]: Added webapp testcase for create issue modal

Summary
Added webapp testcase for create issue modal

Created a PR with all these changes on MM remote, hence closing this one


[bug] FILL THIS IN

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
GUAC version
Are you using a released version of GUAC or one build from a commit in the
repository?
Additional context
Add any other context about the problem here.

empty template


CLI install

Looks like we have a problem with installation of CLI.

we are creating symbol-link to chipmunk to ~./ (home folder)
but if user has space in the account name (like Bred Pitt) it will give problems with the installation

Command line here (application/electron/src/services/service.cli.ts) should serialized as well

On linux and mac as soon as we have safely way to use /usr/local/bin we are creating symbol links. In the case of windows, we are modifying a PATH. Fixed with 2.16.2


[License issue?] Extension settings page not available when I publish my license

Hi,
As I have an extension which makes calls to external web services, I want to configure it in order to enable HTTPClient requests.
I pull the last Business Central image, and at the first run, I can access to the Extension Settings page:

At this time I have the Cronus license, and as it's not possible to publish my extension with these id range, I published my partner license.
First way: by Import-NavContainerLicense powershell command
When i click to Extension Setting Page I have this following error message:

Second way: changing license by the C-SIDE client:
The Extension Settings page doesn't appear anymore in the search results:

At this time I didn't yet publish any extensions, this is just the effect after publishing my license..!
So now, after publishing my extension I can't get rid of this window

Thanks for any help

AL Extension Version: 2.0.48254

Server Version: W1 13.0 (24844)

We are in the process of updating Cronus license. Stay tuned

By now this should have been fixed. Please log a new issue if this is still a problem in a license that is freshly obtained.


Fix for android touchmove bug

There is a bug with touch events on the default browser of some android devices:
https://code.google.com/p/android/issues/detail?id=5491
This fix adds a preventDefault() to the touchmove event when the user is not trying to scroll vertically.
The bug is not possible to reproduce on android emulator (don't know why :confused: ). Only with real devices

Hey @arcxyz,
thank you very much for the change request. I think I had a similar issue in the chrome emulator a few days ago. Can you explain me the bug a bit more specific just to understand if it`s the same problem (stuttering slider animation because too few move events ... )?
Are you sure it works if you put event.preventDefault() in the onTouchmove function? In the discussion above they talking about adding preventDefault in the onTouchstart function and as I remember I had it in the first time also in the onTouchstart function.
I will check this for HTC Desire and Samsung Galaxy s2. Did you check if the preventDefault solves the issue on a real device? Please tell me with which device you tested the bugfix.
I'll be in touch again soon
cheers Max

Finally, I was able to reproduce on the android emulator the same behaviour that I get with a Nexus S, changing the translate3d with a translateX

(you cannot complete the scroll)
If you put the preventDefault in the onTouchstart function it will affect to click events. Check this link:
https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Touch_events#Handling_clicks
With this bugfix I get it working for Nexus S. But I've also tested with a Galaxy S, Galaxy Mini and HTC Wildfire and does not work at all, but this is probably related by the lack of support of 3d transforms on android 2.2 and 2.3.
Do not merge, tomorrow I will try to get it working on these other devices.

It is working great now for Galaxy Mini, Galaxy S and HTC Wildfire. Could you check it with your HTC Desire or Galaxy S2?
http://arcxyz.github.io/fix-android-touchmove/

Hey @arcxyz,
thank you for your engagement! Honestly I didn´t change anything in the touchevent logic, but I`m very happy that it works now for you. As I can see, browser transitions are not supported in Android 2.x ... therefore it works on some devices but I can´t guarantee it for now. I will double check on which devices it works as expected and then I will put them in the documentation.
Thanks again
cheers Max


Object container selector- save history (data transfer, fk)

This affects data transfer wizard and foreign key creation wizard.
There is a "Container name" control which holds information about target container (schema or database).
In dat transfer wizard we save only last used container ,in FK creation we do not save anything.
This is not user-friendly. We need to save history of last N containers and let user to choose one.

We need to turn container name input into combobox with N elements.
Settings must be persistent between different DBeaver sessions.
Settings must be saved per-project (each project has separate list of last used containers)
We need to perform actual object search only when user selects a container (perform connection and object search).

Reopened.
User could choose connection as target container.
So when user exports table, everything looks ok

but as a result user gets an error

For Virtual FK user got next result

Fixed

verified


Try to fix dependabot missing user for "dependabot[bot]'

When running this script on dependabot PRs, we get the following error, which might be related to dealing with non-existing users:
  name: 'GraphqlError',
  request: {
    query: 'query($cursor: String, $org: String!, $userLogins: [String!], $username: String!)  {\n' +
      '            user(login: $username) {\n' +
      '                id\n' +
      '            }\n' +
      '            organization(login: $org) {\n' +
      '              teams (first:1, userLogins: $userLogins, after: $cursor) { \n' +
      '                  nodes {\n' +
      '                    name\n' +
      '                }\n' +
      '                pageInfo {\n' +
      '                  hasNextPage\n' +
      '                  endCursor\n' +
      '                }        \n' +
      '              }\n' +
      '            }\n' +
      '        }',
    variables: {
      cursor: null,
      org: 'elastic',
      userLogins: [Array],
      username: 'dependabot[bot]'
    }
  }
}
Error: Could not resolve to a User with the login of 'dependabot[bot]'.

Issue does not seem to happen anymore thus closing this PR as it has become stale.


chore(ci): update dependencies

This PR updates go-winio to v0.5.0.
This has been done with Dependabot, if the associated config is undesired here, I can remove it

@thaJeztah PTAL


Configure port without hardware offload option in case of virtio-net.

Currently rte_eth_tx_queue_setup() trying configure queue with hardware
offload option as default. lagopus failed to configure virtio tx queue at
rte_eth_tx_queue_setup(), because virtio does not support hardware offload
and virtio assumes given port supports hardware offload feature.
This fix adds ETH_TXQ_FLAGS_NOOFFLOADS option to rte_eth_tx_queue_setup()'s
arguments of virtio configuration explicitly.

Need to refine, I've close it. I will open new one soon.


docker-compose up: Cannot start services superset_init，uperset_worker_beat。。。

How to reproduce the bug
Removing superset_app
Removing superset_init
Removing superset_worker
Removing superset_worker_beat
superset_cache is up-to-date
superset_db is up-to-date
Starting superset_websocket ...
Recreating 4e80981fc5ad_superset_app ...
Starting superset_node               ...
Starting superset_websocket                  ... done
Recreating a10d3d77804a_superset_worker ...
Starting superset_node                       ... done
Recreating bc04ec33c40f_superset_init        ... error
ERROR: for 6c79d9ae2119_superset_tests_worker  Cannot start service superset-tests-worker: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: "/app/docker/docker-bootstrap.sh": permission denied: unknown
Recreating cc76d3717563_superset_worker_beat ... errorocess caused: exec: "/app/docker/docker-init.sh": permission denied: unknown
Recreating 4e80981fc5ad_superset_app         ... error
ERROR: for cc76d3717563_superset_worker_beat  Cannot start service superset-worker-beat: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: "/app/docker/docker-bootstrap.sh": permission denied: unknown
ERROR: for a10d3d77804a_superset_worker  Cannot start service superset-worker: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: "/app/docker/docker-bootstrap.sh": permission denied: unknown
ERROR: for 4e80981fc5ad_superset_app  Cannot start service superset: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: "/app/docker/docker-bootstrap.sh": permission denied: unknown
ERROR: for superset-tests-worker  Cannot start service superset-tests-worker: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: "/app/docker/docker-bootstrap.sh": permission denied: unknown
ERROR: for superset-init  Cannot start service superset-init: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: "/app/docker/docker-init.sh": permission denied: unknown
ERROR: for superset-worker-beat  Cannot start service superset-worker-beat: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: "/app/docker/docker-bootstrap.sh": permission denied: unknown
ERROR: for superset-worker  Cannot start service superset-worker: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: "/app/docker/docker-bootstrap.sh": permission denied: unknown
ERROR: for superset  Cannot start service superset: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: "/app/docker/docker-bootstrap.sh": permission denied: unknown
ERROR: Encountered errors while bringing up the project.
Expected results
All containers to be succesfully deployed by Docker-Compose.
Actual results
Superset containers failed to be deployed because of error "/app/docker/docker-bootstrap.sh": permission denied: unknown
How to reproduce the bug
cd incubator-superset-master
docker-compose up

same issue


🐞 Dice roller not parsed correctly in Black Pudding

Check for existing bug reports before submitting.

[X] I searched for existing Bug Reports and found no similar reports.

Expected Behavior
In the stat block for Black Pudding, here is the ability Corrosive Form :

Current behaviour
With Dice Roller enabled, there are dice appearing incorrectly before "cumulative -1" and "to -5":

Obsidian Version Check
1.4.5
Plugin Version
3.9.3
Confirmation

[X] I have disabled all other plugins and the issue still persists.

Unfortunately I don't think I can fix this without breaking Ability saves elsewhere.


Delay duration ignored for first slide when activity first started

When you start the activity with the slider and if this is set to auto-cycle, the first image will slide to the next almost instantly even though a delay is set. The .setDuration() delay will work after this initial slide.
Apart from that well done, very nice library!

Yep, I have a similar situation. Could you give advice how to solve this problem. Thanks a lot)

Same here :)

I have also same Problem.:)

try this
...
mSlider.setPresetTransformer(4);
mSlider.setDuration(8000);
mSlider.stopAutoCycle();
...
final Handler handler = new Handler();
handler.postDelayed(new Runnable() {
  @Override
  public void run() {
    mSlider.startAutoCycle();
  }
}, 5000);

I saw that the issue was fixed by the above commit. But for me, with version 1.1.5 it is not working. I had to implement the above solution to get this working. Anyone knows why?


Add XR SPI support to underwater post processing

Add changes to support XR SPI. It brings the XR helper class from downstream too to unify codebase.
The helper will probably require some changes if we switch to the post processing stack. Same goes with using the helper in URP. I am uncertain if the post processing stack will make things easier to worse for support XR.

As I'm working on porting post-process effect to the post-process stack - it might be worht holding-off on any post-process BIRP work until then as it changes quite a lot unfortunately :(

No worries. I'll leave this for now.


Installing hosting bundle seems to cause restart of application pools

While this is not an issue in itself, a mention of this in the docs under "Install the .NET Core Hosting Bundle" would be nice, since this can cause some hickups on (especially) older web applications that have special requirements for app pool recycling.

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

ID: ec484002-18c1-6a0d-00de-820d56f038d3
Version Independent ID: 7903ce53-2cbb-f083-7479-c8abc30211a0
Content: Host ASP.NET Core on Windows with IIS
Content Source: aspnetcore/host-and-deploy/iis/index.md
Product: aspnet-core
GitHub Login: @guardrex
Microsoft Alias: riande

Thanks @bernhof ... I can't speak to the current hosting bundle having this behavior (first that I've heard of this). Let's ask the engineers about it.
As a side-note: For the upcoming 2.2 release, they are going to make it so that the hosting bundle installer performs an IIS restart, which is going to have the same effect as what you're asking about. I'll use this issue to document that. For more info, see https://github.com/aspnet/IISIntegration/issues/1278.
@jkotalik @joeloff ... Does using the current hosting bundle installer cause some or all app pools to recycle?

The current hosting bundle can cause an iisreset (which stops all app pools) if the ANCM installers detect that IIS needs to reset to complete installation. We are working on making the installers reset no matter what because, as mentioned here: https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-2.1&tabs=aspnetcore2x#install-the-net-core-hosting-bundle, net start/stop are required to pick up the dotnet path changes. Once the feature is verified and in, I'll ping this thread again so we can collaborate on making the docs correct.

Once the feature is verified and in, I'll ping this thread again so we can collaborate on making the docs correct.

In the meantime, I'll add a short note that pertains to the current installer and just mark the PR as addressing this issue to keep it open after we merge. I'll ping u for review on it shortly.

Just wanted to put a quick thumbs up for responding so quickly to issues like this. Keep up the good work! 👍

Thanks @bernhof ........ just don't look at the backlog! 🙈 :smile: lol ... I think what will happen is that there will be a decent break after all of the 2.2 issues are resolved (and the samples are updated) and before 3.0 gets on us where we can dig into the backlog. Well ...... it's a prayer to the :pray: server gods :pray: anyway. :smile:

Fixed by https://github.com/aspnet/Docs/commit/4480bb13021dc33541e034bdcfaaa593f0b98c5e


local and open-source pipeline

Hi,
Do you plan on having a open-source that can be run locally ?

Yes, we already supported it! To use it locally and quickly, you can check out our [Docker guide(https://github.com/Shaunwei/RealChar)


pass autocompletion: append slash when applicable

When autocompleting file system paths in Zsh, a slash (/) is appended automatically so you can immediately continue typing the next path component.
When using pass edit with hierarchically stored items in pass, the slash has to be added manually. This reduces the amount of time/effort saved by the autocompletion feature.
It would be nice if this feature could be added. (If time permits I'll look into this myself.)
(If I understand correctly, I should also mention the plugin maintainer, @sanbor here.)

Try setopt AUTO_PARAM_SLASH? If that doesn't work try asking in the password-store mailing list.


brew install --quiet does not suppress warnings for casks

brew doctor output
% brew doctor
Your system is ready to brew.

Verification

[X] My "brew doctor output" above says Your system is ready to brew. and am still able to reproduce my issue.
[X] I ran brew update twice and am still able to reproduce my issue.
[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

brew config output
% brew config
HOMEBREW_VERSION: 4.3.10
ORIGIN: https://github.com/Homebrew/brew
HEAD: c3ae0327c01aab461531bfc0fcdfb4dd3a779205
Last commit: 10 days ago
Core tap JSON: 28 Jul 22:50 UTC
Core cask tap JSON: 28 Jul 22:50 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 10
Homebrew Ruby: 3.3.3 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.3/bin/ruby
CPU: 10-core 64-bit arm_firestorm_icestorm
Clang: 15.0.0 build 1500
Git: 2.45.2 => /opt/homebrew/bin/git
Curl: 8.6.0 => /usr/bin/curl
macOS: 14.5-arm64
CLT: <IP_ADDRESS>.1.1708646388
Xcode: N/A
Rosetta 2: false

What were you trying to do (and why)?
I'm trying to write an unattended install script to set up my mac - I want it to install all the brew formulae in a list, and not produce any output even if some of them are already installed.
What happened (include all command output)?
If I run brew install --quiet [already-installed-cask], then brew produces a warning:
% brew install --quiet firefox
Warning: Not upgrading firefox, the latest version is already installed

What did you expect to happen?
I expected that the --quiet option would silence this warning regarding upgrading casks, just as it does for normal formula in issue #9179.
Step-by-step reproduction instructions (by running brew commands)
brew install firefox
brew install --quiet firefox

What a coincidence, this was updated to match the behavior you describe last week and just hasn't made it into a release yet. We usually make a release every week or two so another one should show up soonish.
See https://github.com/Homebrew/brew/pull/17761


Support .in files (or just cmake.in)

A common pattern is a .in file, which should be identified as the inner type, that is, MyConfig.cmake.in should be a CMake file, and pytest.ini.in should be an ini file, etc. AFAICT, this is not currently supported?

the problem with .in is it usually implies some type of preprocessor, and almost always the preprocessor templating is incompatible with the end file format (you wouldn't lint a foo.py.in file the same as a foo.py files).   Additionally, .in could imply any sort of preprocessor (it may be autotools, it could be some simple sed, jinja, who really knows!)
As such, I don't think this should be implemented, what are your thoughts?

In my case, I want to identify files for formatting, so I definitely want to pick up cmake.in files and format them too. However, for a linter, I'd like to be much pickier, you are right. Would it be possible to add a modifier for file types? Such that X.in is a X file with an .in extension?

at that point I would probably revert to using types: [file] and implementing what you need in the files: regex

CMake-format is explicitly supporting *.cmake.in files in it's next release, so it would be very nice to be able to elegantly identify these (it actually caught me by surprise that they were not being picked up by default, since they are a very common file type in CMake).  (And an explicit regex is what I'm currently doing)

By the way, .cmake.in's might be a bit special here, since they are a very common CMake file type (pretty much every package has a *Config.cmake.in) and very well defined, with just one additional bit of syntax. Unlike most other cases, I'd even expect the pre-commit extension for cmake-format to find cmake.in files by default, actually. But I would think a general solution here would be better, as it would give the ability to easily identify other .in types, but I mostly care about cmake.in at the moment.

 I was using 0.6.10 since that was the last version out for pre-commit, but now that I've updated to 0.6.11 (thanks for releasing that), this works!


Future: Express 5

The corresponding PR of express:
https://github.com/expressjs/express/pull/2237
Related issue https://github.com/expressjs/express/issues/5205

need to change mime to mime-types here, in accordance with express and express#send dependencies

Too outdated, will make a new one


chore: Testing CLA

No need to merge this, it is to just test the CLA integration.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

CLA Assistant is working.  Closing our this PR.


Vulnerability fix for DockerComposeV0

Task name: DockerComposeV0
Description: Latest vulnerability fix for DockerComposeV0
Documentation changes required: (Y/N)
Added unit tests: (Y/N)
Attached related issue: (Y/N) https://dev.azure.com/mseng/PipelineTools/_componentGovernance/184/alert/79428?typeId=12858
Checklist:

[x] Task version was bumped - please check instruction how to do it
[x] Checked that applied changes work as expected
[x] node make.js build --task DockerComposeV0

/azp run

/azp run


Write script to migrate PWM password hashes to COmanage

The script should do the following:

Query registry database for all users with HCID org ids
Query PWM ldap for password hashes
Add those hashes to the registry database, probably though API call

The script should do the following:

Query registry database for all users with HCID org ids
Query PWM ldap for password hashes
Add those hashes to the registry database, probably though API call

Working script on dev-registry


Removed passing unused handler for setRepeatingRequest()

close https://github.com/android/camera-samples/issues/289

You are correct about your assessment here. That said, your PR has no effect on the code since the callback is never triggered. By having the handler set, it will be harder for future code maintainers to forget to use the appropriate handler.


OSD-12248 Fix typo

The secret name is avo-aws-creds (https://issues.redhat.com/browse/SDA-6264) also spelled correctly on line 64/66

/lgtm


[BugFix] change default_wg memory_limit to 1.0 and concurrency_limit = 0

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

There should no limit for default_wg.

@Mergifyio backport branch-2.2

Maybe default workgroup should use exec_mem_limit and query_mem_limit to limit memory?


rancher-compose build: Allow ability to authenticate against GHE to build

http://forums.rancher.com/t/deployment-options-using-github-enterprise-rancher/541/5
Currently rancher-compose does not support being able to build against GHE. If Rancher is configured against GHE, it'd be nice to also allow the ability to build against it in rancher-compose.

👍

👍

Any news on this issue? I think it is not nice to rely on public git repos when you want to avoid the S3 alternative...