Hard to read in the metro

I was able to use the app but I tried resizing thebhelpntonmake it bigger but it centered off the page so after a few clicks I hitnthe minimize button and then couldn't get the help back to its normal size, dragging it down caused my browser to refresh. I will try to help with this but I'm not sure jquery ui is mobile friendly

Yes, I don't know what to do about mobile yet. Dative only really works on desktop browsers right now. Suggestions/contributions on making it mobile-friendly would be very much appreciated...


Column Summary (Footer)

Hi, Summary columns are used to represent calculations of specific data from a dataTable.
For example, the "Invoices" table displays the total amount for all invoice items stored in the "Items" table.
As a result, the Total summary column, calculating the total items amount
https://www.teamdesk.net/help/img/image-93.png

Hi @kitesoft!
There is currently no footer. You can get a little closer by using custom cell sorting. In any case, it wouldn't be left out of the scroll. Depending on the case, it won't work. :disappointed:
The footer is in the TODO list.


Awesome app!

First of all, good job! Been looking for something like this! I'm having some issues getting it to work though.
I'm using Windows 10, and the QR code pops open in chrome and i use my phone to scan it. Then, the chrome tab just loads messages.google.com, instead of the app. The app remains white the whole time.

I get the same issue on mac

I think it is an issue with the URL. I'll release a new build shortly. Just dealing with a few issues with my computer at the moment :)

Updated in releases! Enjoy!


[AutoPR cosmos-db/resource-manager] Add SQL API for Cosmos DB

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5487

(message created by the CI based on PR content)

Codecov Report

Merging #4694 into restapi_auto_cosmos-db/resource-manager will increase coverage by 0.86%.
The diff coverage is 36.56%.

@@                             Coverage Diff                             @@
##           restapi_auto_cosmos-db/resource-manager    #4694      +/-   ##
===========================================================================
+ Coverage                                    55.07%   55.94%   +0.86%
===========================================================================
  Files                                        10106     9442     -664
  Lines                                       206146   189510   -16636
===========================================================================
- Hits                                        113541   106014    -7527
+ Misses                                       92605    83496    -9109

Impacted Files
Coverage Δ

...s/database_account_create_update_parameters_py3.py
100% <ø> (ø)
:arrow_up:

...odels/database_account_create_update_parameters.py
100% <ø> (ø)
:arrow_up:

...osmosdb/operations/database_accounts_operations.py
39.29% <10.23%> (-17.45%)
:arrow_down:

...mt-cosmosdb/azure/mgmt/cosmosdb/models/__init__.py
100% <100%> (ø)
:arrow_up:

...osdb/azure/mgmt/cosmosdb/models/cosmos_db_enums.py
100% <100%> (ø)
:arrow_up:

...mgmt/cosmosdb/models/sql_container_resource_py3.py
26.31% <26.31%> (ø)

...ure/mgmt/cosmosdb/models/sql_container_resource.py
26.31% <26.31%> (ø)

...zure/mgmt/cosmosdb/models/sql_database_resource.py
38.46% <38.46%> (ø)

.../mgmt/cosmosdb/models/sql_database_resource_py3.py
38.46% <38.46%> (ø)

...cosmosdb/models/extened_resource_properties_py3.py
44.44% <44.44%> (ø)

... and 760 more

Continue to review full report at Codecov.

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

Restpr was closed


[daftsex] Fix yt-dlp#2637

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Fix daftsex extractor
Explanation of your pull request in arbitrary form goes here. Please make sure the description explains the purpose and effect of your pull request and is worded well enough to be understood. Provide as much context and examples as possible.

What's with the massive try block?

Please do desired changes yourself if you can.

What's with the massive try block? It's not clear from which lines the errors are expected to be from

Sorry about that, can you check again?


Connection issues

Hi there,
Just wanted to let you know: after upgrading from 2.0.14 to 2.1.7 we started seeing errors as follows:
MongoError: connection 2427 to <host:port> timed out
    at Function.MongoError.create (/app/node_modules/mongodb-core/lib/error.js:29:11)
    at Socket.<anonymous> (/app/node_modules/mongodb-core/lib/connection/connection.js:186:20)
    at Socket.g (events.js:291:16)
    at emitNone (events.js:86:13)
    at Socket.emit (events.js:185:7)
    at Socket._onTimeout (net.js:339:8)
    at ontimeout (timers.js:365:14)
    at tryOnTimeout (timers.js:237:5)
    at Timer.listOnTimeout (timers.js:207:5)

Downgrading back to 2.0.14 solved the problem*.
Unfortunately, I could not bisect exact version where the problem appears since it takes 6-20 hours to make sure that problem is or is not happening anymore.
Some stats: we have ~30k requests per day, for two weeks we saw ~600 occurrences of this error.
Please, let me know if I can help you with the investigation.

at least we can't see timeout errors anymore.

You should move to the 2.2.22 or higher driver not to the 2.1.x series. 2.2.23 will be out today with some minor improvements so hold off until tomorrow.

Hello,
I'm having random timeouts problem too with 2.2.22 (mongoose 4.8.1 -> mongodb 2.2.22 -> mongodb-core 2.1.7). Running aggregation on large collection (70 million records) times out after random periods of time, typically between 10 and 30 seconds. Here is the stack trace:
MongoError: connection 2 to /tmp/mongodb-27017.sock:27017 timed out
at /home/test/src/app/test_modules/lib/background_jobs/test.js:133:27
at /home/test/src/node_modules/async/lib/async.js:251:17
at /home/test/src/node_modules/async/lib/async.js:148:21
at /home/test/src/node_modules/async/lib/async.js:248:21
at /home/test/src/node_modules/async/lib/async.js:612:34
at /home/test/src/node_modules/mongoose/lib/aggregate.js:658:15
at handleCallback (/home/test/src/node_modules/mongodb/lib/utils.js:95:56)
at /home/test/src/node_modules/mongodb/lib/collection.js:2689:7
at handleCallback (/home/test/src/node_modules/mongodb/lib/utils.js:95:56)
at Object.cb (/home/test/src/node_modules/mongodb/lib/db.js:311:20)
at null. (/home/test/src/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:243:32)
at g (events.js:260:16)
at emitTwo (events.js:87:13)
at emit (events.js:172:7)
at Socket. (/home/test/src/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:185:10)
Timeout (socketTimeoutMS) is set to 0, connection is established via unix socket, code is running in docker container (with mongo db stored in mounted docker volume). Both docker and the host are running debian. I would appreciate your could help resolving this issue. A quick web search shows a lot of people affected by this problem.
Thank you!
Andrey Mikhalchuk

There is a fix that improves scheduling of long running aggregations coming in 2.2.23. Other than that 0 is not some sort of magic option, all it does it delegate the timeout setting to the OS level or in your case docker container. I would suggest setting socket timeout to 2-3x the longest running query time and also adjust the os/docker container default socket timeout.

Christian, appreciate your lightning fast response!
I doubt the problem is in the OS/docker since it occurs randomly. Also web search shows reports from people running into the same issue without docker, unix sockets etc. So I'll be waiting for mongoos to eventually upgrade to 2.2.23 which was released 22 minutes ago.
Really appreciate your hard work.
Sincerely,

Hi @christkv ,
I'm having difficulties setting a socket timeout. In our production system it's much more likely to have a stable connection running a very long query (15min +).
During the deploy I'm applying this patch to get it work:
diff -Naur node_modules/mongodb-core/lib/topologies/server.js ../../node_modules/mongodb-core/lib/topologies/server.js
--- node_modules/mongodb-core/lib/topologies/server.js	2016-12-08 22:48:44.000000000 +0100
+++ ../../node_modules/mongodb-core/lib/topologies/server.js	2016-12-23 17:49:01.000000000 +0100
@@ -215,7 +215,7 @@
     var start = new Date().getTime();
     // Execute the ismaster query
     self.s.pool.write(query, {
-      socketTimeout: self.s.options.connectionTimeout || 2000,
+      socketTimeout: (typeof self.s.options.connectionTimeout !== 'number') ? 2000 : self.s.options.connectionTimeout,
     }, function(err, result) {
       // Set initial lastIsMasterMS
       self.lastIsMasterMS = new Date().getTime() - start;

This allows me to set connectionTimeout to 0, which by convention means no timeout (https://nodejs.org/api/net.html#net_socket_settimeout_timeout_callback).
I think this behaviour should be allowed..

Just set up a PR and I'll have a look at it. However don't be fooled 0 does not mean no timeout, it just defers to the os which will timeout the connection at some point. I think linux default is mostly 30 minutes.

Ah thanks, I didn't know it. Ok, I'll setup a PR :)

merged PR

In my case, the problem was file security on the new server and mongdb npm module files, so I had to use "chown" command to own all files and then run "npm install", after that MongoDB client worked properly.


WriteMessage to write on console as well

Currently the write message output is given in the reports only. It would be helpful if this would reflect on the console as well.
Gauge version
Gauge version: 0.5.1.nightly-2016-06-16

Plugins
-------
html-report (2.1.1.nightly-2016-06-02)
java (0.4.1.nightly-2016-06-16)
xml-report (0.1.2.nightly-2016-05-27)

Duplicate of #503. Closing this.


run_all_experiments: set introspector endpoint as early as possible

Otherwise we will use the default endpoint when we also generate benchmarks during the run (happens inside of get_experiment_configs). This commit ensures we use the right endpoint in both local and cloud-based runs.

/gcbrun exp -n dk

For some reason the result HTML page is blank, and I'm not sure why.

/gcbrun exp -n dk

/gcbrun exp -n dk100

/gcbrun exp -n dk102


The pre-trained model file is corrupted?

I have downloaded the pre-trained model file several times and tried to extract the tar file. But it always shows "An error occurred while loading the archive"

You should just load the model instead of extracting it.

Thanks!


Cannot install into Unity

I am trying to install, I use assets>packages>install>install custom package.... everything seems to run fine and I can see RoadArchitect in my assets folder but I have no menu option to use RoadArchitect.
Am I missing something?

I have reinstalled Unity completely now, re-installed and now it works as it should. I didn't choose Android and iOS support options this time though. Maybe that was the issue. Thank you all for your time and support.


Layers Icons too confusing

As title says

the above icons are too confusing, I can't get my head around them and I need to hover every time on them to see what they are.
Can we have simpler icons maybe something similar to Icons as tlDraw has

We used to have it colorized to be more obvious:

Perhaps we should go back to doing it.
Otherwise, we use these icons because it's a de facto standard. I worry that using arrows in the UI will make people think it's somehow related to arrows.

Colors are much better than what I see right now, but honestly I think the arrows makes the most sense at it reminds me (at least) of the video players navigation (first, previous, next, last). I'm not sure what is the process or whether you do user interviews or surveys. Maybe do a poll on twitter?

I would suggest this idea (5) with an explanation of the design change:
Black, white, argue with each other, causing doubt as to which one is the main one, so there is difficulty in understanding how these buttons work.

If you color them, doubts remain if you don't know which color is the accent color.

Because of this, I put even more emphasis on the main element with the scale.

But I don't like how it looks "at the very bottom", too "noisy".
The lowest or the highest usually marks the border of the canvas, so I replaced the square with a silhouette.

And if we have border markings on the left and right I would change their placement to this:

Thanks for your attention!

@anatoliibakhtin I love your designs!
That said,  the (4)/(5)/(6) are not obvious to me. I could easily explain the (4.1) to both mean either "send to back" or "send backward". And I don't think that (3.1) looking noisy is the issue — it's actually conveying that the selected element (purple) will be hidden behind all the other elements.
I agree on the ordering though.
So we should:

go back to using colors
order as: send to back send backward send forward send to front

Great stuff above. Honestly still I think the arrows is one of the best in conveying the message

@sedghi let's dream? If it were possible (I also find arrows to be a faster-reading symbol – it's a simpler figure), which option would you vote for: from 1-6, between A-C ?

Hmmm, great options here.
This is my opinion:
1, 2 => too confusing
3 => too video playery
4 => all looks great and simple. My preference is 4c then 4A then 4B
5 => looks great, I guess 5c then 5B then 5A (too narrow)

In terms of UX the current icons have 2 flaws:

icon "flow" is counter intuitive with commonly understood left-to-right, top-to-bottom order. The icons are on a bottom-left -> top right diagonal which makes them more obscure
the "bottom" and "top" element is in the middle of the "stack". It may not look like a stack, but it is.

Here is my proposal:

The advantages of that approach:

reads like a stack, you know what is top and what is bottom
the longer arrows indicate longer moves, i.e. move to bottom/top.
the bars at the end of an arrow indicate the "edge"
the "bring to top/bottom" show moving past 2 elements, indicating that it's a longer move
the "move down/up" show a shorter arrow and only one element
it is curved to indicate moving it past one object, aka "1 step"
the active element is clearly indicated with a color
no diagonal confusion, reads well in both RTL and LTR modes
colored element indicates the active element and dotted outline indicate previous location

😍🎉❤

@T3sT3ro looks cool, but super complex for icons. Bear in mind that when scaled down to the button size, you'd be barely able to see anything:

In the end we went with the simple arrows:

@anatoliibakhtin thanks for reminding we should close this :)


Ignore columns is creating a crazy ML model

System Information (please complete the following information):

Model Builder Version (available in Manage Extensions dialog):  any version
Visual Studio Version 2019 or 2022

Describe the bug
The model is generated wrongly with incorrect Label when ignoring some columns from the table.

Clear description of the problem:
To Reproduce
Steps to reproduce the behavior:

Train the ML model for multiclass text classification using a database table and ignore some columns.
The generated code will contain the ignored columns
The model generated will contain invalid labels

Expected behavior
Ignored columns should not be in the generated code (ex: ModelInput.cs) and should not be used for model training.
Additional context
Workaround: Create a view with only the columns required for the ML model. But this is a high severity issue.

Possibly related https://github.com/dotnet/machinelearning/issues/5919

I believe, most of the time at least, the ignored columns are ignored correctly. I tried reproduce in Model Builder with a file that had the label column copied as "ignore_this" colomn. "ignore_this" would reveal the result so trees should give perfect scores if not ignored. If there is a chance this might happen it may need to be tested with automated tools since manual reproducability seems difficult.
Anyway, even if the ignored values would not be used for training, just having the ignored values in the model schema can cause minor issues. I have some old models but the ignored field is now dropped from the new dataset and live data. I still need to have a property for the dropped field to be able to consume the model. Worst case is 2+ models trained at different times; both have the ignored col but with different data types.
However, minor benefit from having the properties generated to ModelInput.cs is that I can use same class for all models, which may have different fields ignored (for comparison purposes, mostly)

Thanks for reporting, it's expected that the code will include ignored columns as ignoring column will only affect how training pipeline created, rather than how dataset get loaded. You can check on the generated training pipeline and you should find out that the ignored column is not used to train the model.
Can you give an example on invalid lable as well?

Sorry, I can't provide the data I was using for training because it is company confidential. Thank you!

Sorry, I can't provide the data I was using for training because it is company confidential. Thank you!

@LittleLittleCloud
Some thoughts for consideration:
The columns are included in ModelInputSchema and ModelInput.cs. I have some few months old models, which include ignored columns in the schema. Ignored columns are removed from newer dataset files so I no longer have the data. This may be confusing (per original issue) but also cause minor issues in consuming the models:
ITransformer model = mlContext.Model.Load(ModelZipPath, out DataViewSchema ModelInputSchema);
=> ModelInputSchema includes ignored columns. In my case, secondary labels which are highly correlated with the primary label so they are not used to train the model - otherwise I should get near perfect scores.
This causes small issues:

First, it tells me the fields are not included.
Trying to manually add the columns, gives me errors like  Column 'PredictedIsValid' is supposed to have item type System.ReadOnlyMemory1[System.Char], but associated field has type System.Boolean (Parameter 'userSchemaDefinition')`.
Rare cases may have problems that the same columns has different types, even if it was ignored.

It seems the ignored columns have, in my case, Single or ReadOnlyMemory for ignored Boolean fields. Reason might be that some were 1/0 and some were "true"/"false".
It would be helpful if they were inferred with same way as non-ignored fields (original datatype boolean), or if they always had a specific data type (maybe object).


style(corda): linter fix deploy contract

Signed-off-by: Youngone Lee<EMAIL_ADDRESS>pinged @petermetz because I don't have review section 😢

@Leeyoungone The semantic PR check is failing because you are missing a space character from the commit message after the : (we need to adhere to these strict formats so that we can auto-generate the release notes from the commit messages)

@petermetz re-pinging!

Just to confirm, does this PR includes file changing? There seems to be nothing on the tab of "File changed".

Just to confirm, does this PR includes file changing? There seems to be nothing on the tab of "File changed".

@takeutak Strange indeed. My best guess is that the same PR was accidentally submitted twice, first one got merged, second one became an empty diff after the rebase.
@Leeyoungone If the above theory is correct then this can be closed as a no-op given that it was already merged. Please let us know and then we can proceed accordingly.

@petermetz I think your theory is correct, I apologize for the confusion. I'll make sure to be more thorough in my other PRs next time.
@takeutak Thank you for pointing this out, I appreciate it ⭐ !!

@Leeyoungone Absolutely no worries, stuff like this happens all the time. I once accidentally bought a plane ticket twice to the same day and destination, but with different airlines... :-)


Once breaks if moved

Here's a test that illustrates the bug:
#[test]
fn once_test() {
    crate::check_dfs(
        || {
            let once = Once::new();
            once.call_once(|| {});
            assert_eq!(is_completed_borrowed(&once), true);
            assert_eq!(is_completed_owned(once), true); // FAILS
        },
        None,
    );
}

fn is_completed_borrowed(once: &Once) -> bool {
    once.is_completed()
}

fn is_completed_owned(once: Once) -> bool {
    once.is_completed()
}

The issue is that we use the address of the Once to compute a storage key, which changes when the Once is moved.
https://github.com/awslabs/shuttle/blob/2ac1fae623daa18d3947c16da22361b9287eed1b/src/sync/once.rs#L166-L170

Hmm, yeah, that's pretty silly. Once should just use a static counter or something to generate unique storage keys. Or I guess a Box<usize> if we wanted to keep using addresses for some reason.


Improve warning for ExportViewFormMixin

Problem
The existing warning added in #1667 did not reveal which class used the deprecated mixin.
Solution
Transform this warning to run at class definition time using object.__init_subclass__. Then the deprecated line is shown as the point of class definition.
Acceptance Criteria
Tested in my own project. Modified the tests here, though none check the warning message.

coverage: 100.0%. remained the same
when pulling a9ca23fd8f3794f89d87b4733d4a4c1b40107a7c on adamchainz:improve_mixin_warning
into afd099f70e50a3e0f694ae1e31ac18be1b9fa341 on django-import-export:main.


reported structure, not displayed

https://www.pombase.org/reference/PMID:12018481

Also
PMID:16138082 Structure
papers trisaged as "structure" should be treated as "curatable".
"Structure " is just a triage class to group these to curate.

https://www.pombase.org/reference/PMID:12018481

The structures will be on the publication pages on the main site on Wednesday morning.  Currently they're only on the dev site.

PMID:16138082 Structure
papers trisaged as "structure" should be treated as "curatable".

I've changed the Canto config so that Structure papers are exported to Chado even if they aren't approved.  So all Structure papers from Canto will get a publication page on the main site on Thursday morning.

ok!


Add indexer to the tenant service

Indexer was added to the urm service in the kv system and we need to roll it in to the tenant urm's to avoid a regression.

We need the index definition: https://github.com/influxdata/influxdb/blob/master/kv/service.go#L69-L81 the result of this is used to insert, delete and read the index.
Insert into index when creating a URM https://github.com/influxdata/influxdb/blob/master/kv/urm.go#L220-L223
Delete from index when deleting a URM https://github.com/influxdata/influxdb/blob/master/kv/urm.go#L390-L393
When reading by user ID walk the index https://github.com/influxdata/influxdb/blob/master/kv/urm.go#L129-L148 the visit func will get called for each thing in the index.

Finally, reading just returns nothing until https://github.com/influxdata/influxdb/blob/master/kv/service.go#L113 this option is passed to the index on creation. Or called explicitly.


[question/feature request] Uploading of content of generated files

Hello,
is it possible include content of generated files to a report?
I do have some some generated files in my project https://coveralls.io/builds/25742378/source?filename=src/verilogPreproc/verilogPreprocParser/verilogPreprocLexer.cpp
I do not know how to add them to https://docs.coveralls.io/api-reference /  SOURCE FILE / source in report so coveralls can visualize it.
Thanks

AFAIK, coveralls-lcov command sends the content of the source file always.
Could you ask it to coveralls.io?

coveralls-lcov command sends the content of the source file always.

I should have look at report first. That is true.

Could you ask it to coveralls.io?

OK I will check if output is entirely correct and then ask coveralls.

Actually coveralls never responded.


TypeError when displaying the tracking analytics

Got this issue when trying to displaying the tracking analytics with ?analytics=on. Any clues to fix this issue?
TypeError: metric() got an unexpected keyword argument 'help'
Traceback:
File "/usr/local/lib/python3.6/dist-packages/streamlit/scriptrunner/script_runner.py", line 554, in _run_script
    exec(code, module.__dict__)
File "/home/ubuntu/SE_github/streamlit_apps/dev_pages/csv_merger.py", line 22, in <module>
    "...and now add `?analytics=on` to the URL to see the analytics dashboard 👀"
File "/usr/lib/python3.6/contextlib.py", line 88, in __exit__
    next(self.gen)
File "/usr/local/lib/python3.6/dist-packages/streamlit_analytics/main.py", line 440, in track
    verbose=verbose,
File "/usr/local/lib/python3.6/dist-packages/streamlit_analytics/main.py", line 405, in stop_tracking
    display.show_results(counts, reset_counts, unsafe_password)
File "/usr/local/lib/python3.6/dist-packages/streamlit_analytics/display.py", line 44, in show_results
    help="Every time a user (re-)loads the site.",

Found a clue on #23.
It it a version issue, from version >= 1.11, st.metric() accepts a help attribute. Since I am on streamlit==1.10 I had to comment out the help attribute on the display.py file.


Toggle permission columns on/off

I've had to work with lots of permissions in groups lately and found checking each box for an entire column was a bit painful as a user.
This PR adds 3 check boxes to toggle all Add/Change/Delete column checkboxes to the Group Edit and Create views.
Tested on:

[x] Chrome 78
[x] Firefox 72
[x] Safari 12
[x] Edge 80 (for MacOS)
[ ] Internet Explorer (did not test)

This is a preview of the feature.

I've re-written some of the JavaScript to be more IE11 friendly so this feature now works. But there seems to be a checkbox issue with IE11. I've opened a bug report in #5903. May need to fix that bug before this work can be merged in.

Great idea! Would it be possible to duplicate the "Check all" row at the top of the table, as well?

@Scotchester Yeah I don't see why we couldn't do that.

Might be a good candidate for a future refactoring to use our w-bulk Stimulus controller.
See https://github.com/wagtail/wagtail/pull/10613 for a more recent usage in a PR. Should be mostly adding the check all boxes and some data attributes.
The Controller may need to be updated to work better with sets of checkboxes though.
I'll add this to the Stimulus project for now & update this with the needs work label.

Replaced by https://github.com/wagtail/wagtail/pull/10867
Same behaviour but using the new Stimulus shared implementation for bulk checkboxes.


Won't Punch / Question

We have compiled the client and server examples.
We have a server (A) with a public ip behind a restricted cone nat.
Our client (B) is behind a restricted cone as well.
We have the Punch Server Host set to the public ip of (A) and we even opened the firewall port to 6776
On our client when we run the compiled console app, we get asked:
[CONNECTOR] Enter the address of the listener you want to punch:
Which ip is this referencing?
Our goal is to simply create a punch / connection from B to A so that we can then proxy services from B to A as requested by A.

Hi, any update on this?

You call ListenForPunches on one computer behind one network.
Then you call Punch on another computer on a different network, you pass the IP of the network where the "ListenForPunches" computer is located. This will punch a hole in the listeners NAT with the help of the punch server.


Add a disclaimer note to readers that current How-Tos for Grafana and Prometheus

What content needs to be created or modified?
Grafana and Prometheus how-to needs a warning note.
Describe the solution you'd like
Add note to both pages
AB#9830

not a warning, just a disclaimer :)

Closing as no longer the solution wanted instead will be using #918


Update s3, sdk-core, sqs to 2.16.17

Updates

software.amazon.awssdk:s3
software.amazon.awssdk:sdk-core
software.amazon.awssdk:sqs

from 2.15.82 to 2.16.17.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, semver-minor

Superseded by #110.


Update Composer dependencies (2021-03-25-00-05)

Visual regression test passed!
View the visual regression test report


bring back rubyLibs, as people are still using it.

Do you know any solution how could we migrate this to some other better solution in a long run?

@offlinehacker I'm not sure I follow. Are you asking how to keep the rubyLibs approach - while cleaning up the code - in tandem with the Bundler/Bundix/Gemfile approach from #4677?

Yes, i'm asking what could be better alternative to current generation using "gem nix" and rubyLibs? Could be bundix used for that?

I'm proposing that people use bundix for packaging applications going forward, using a Gemfile.lock to specify the specific versions of the dependencies they need. No one expressed any interest in keeping the rubyLibs model of packaging for Ruby back when I was wrapping up the "pleasant ruby" PR, but if someone can provide a compelling argument for keeping it around as a first class citizen, I think it would be fairly trivial to both keep that old model of packaging and move it forward.
I'd really like to hear from Ruby∩NixOS developers, and know how they feel about rubyLibs vs the Gemfile-centric approach that bundix takes. Do people really want rubyLibs, or is it just that people still need time to migrate over?
Personally, I think the rubyLibs approach just doesn't work too well in practice. For development of a Ruby project, Gemfiles are the de facto way to specify dependencies. The rubyLibs approach can't be used during development, because the Gemfile/Gemfile.lock demand specific versions (although, I suppose we could offer a utility analogous to our "cabal jailbreak", allowing one to at least patch up their Gemfile.lock to match the versions in rubyLibs. Any thoughts here?). Therefore the bundix approach is necessary if we want to support developers, so I figure it might as well be "the" way.

Bundix approach is good for developers, but what about users/developers that only use ruby packages as tools and not as libraries. For example i use compass in nodejs.

One issue I'm still running into with the bundix approach is that it seems like it is not possible to install more than one bundix-created ruby package into an environment, because the Gemfile/Gemfile.lock files from the two of them conflict.
rubyLibs made it very cumbersome to maintain ruby-based nix packages in a tree outside of nixpkgs, but it was at least possible to do so.

I'm also using bundix now, but i also have same problem as @benley

I'm fairly confused by the whole bundix thing as someone who just wants to use existing ruby gems for other stuff. It seems quite substantially different from all the other nix package ecosystems and I don't really see compelling reason for it to be. It doesn't seem like the common case is someone developing new ruby stuff using nix, but rather wanting nix to be a package manager and thus finding a bunch of existing ruby packages floating around pre-packaged so they don't have to worry about where they come from or what they depend on.

@copumpkin From my point of view, bundix is for Ruby applications (during development and for packaging). There's quite a lot of software in the Ruby ecosystem that's not necessarily available as a gem. So basically bundix is supposed to be a wrapper around Bundler (to piggyback on its dependency management), but bundix itself should reuse nixpkgs existing buildRubyGem infrastructure. If you just want to use an existing gem, you shouldn't need bundix.

One issue I'm still running into with the bundix approach is that it seems like it is not possible to install more than one bundix-created ruby package into an environment, because the Gemfile/Gemfile.lock files from the two of them conflict.

Interesting, I thought the out drvPath was the only thing to be linked in user environments... I'll have to an alternative way of handling this, but I don't have a solution in mind just yet...

I'm fairly confused by the whole bundix thing as someone who just wants to use existing ruby gems for other stuff. It seems quite substantially different from all the other nix language ecosystems and I don't really see compelling reason for it to be. It doesn't seem like the common case is someone developing new ruby stuff using nix, but rather wanting nix to be a package manager and thus finding a bunch of existing ruby packages floating around pre-packaged so they don't have to worry about where they come from or what they depend on.

The main impetus was supporting Rails web apps, which almost always depend on Bundler to automatically require all necessary gems (via Bundler#setup). Making Rails apps work in Nix would otherwise require patching out a lot of Bundler related stuff, and manually keeping up-to-date a huge list of require <gem-name-here>.
The second motivator being that Ruby libs are terrible about maintaining compatibility across minor version bumps, as well as keeping up to date with the API changes of their dependencies. Coupled with the fact that, unlike the package managers for Python/Haskell/etc, Rubygems doesn't provide any way to run tests for a given gem, so you have to either

cross your fingers and hope that all the gem versions are compatible,
manually checkout the source for every gem, read the README, setup the gem's special-snow-flake test environment, run the tests, install the gem, and rinse-and-repeat,
depend on the app author to have done QA with the versions given in the Gemfile they distribute.

The last bullet point is the only sane way to ensure stuff works in the Ruby/Rails world.
So, those are my reasons. I'd like to have just one static set of versions, as we have with other languages. It's just that I assume Ruby libs to be broken until proven otherwise, and I certainly wouldn't trust any packaged Ruby applications to work unless they used precisely the versions the author(s) tested with. Perhaps others are more trusting than me, or perhaps I'm overly bitter, in which case I'll understand if Bundix isn't accepted as default way to package Ruby applications.

Ping. This is claimed to solve a blocker issue. No comments from interested people (who know something about ruby)?

@vcunat Which issue are you talking about?

#6340

@vcunat I unfortunately don't have the time to look into this (vacation), but I can see that a curated set of rubyLibs might be useful for packages that depend on one or more gem. With some additional effort we could run tests of these gems too. For packaging full Ruby applications, Bundix would be the way to go. Both approaches should share the same mechanism to package gems though.

Would be nice to get this back in, I need for example sass compiler that is gone now.

Closing as Bundix and the whole ruby ecosystem is now in a good shape


refactor: SplunkRestClient initialization

Removed check_css_params function from net_utils and replaced it with validate_scheme_host_port.

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

v4.3.5
GitHub release

Your semantic-release bot :package::rocket:


Avoid deprecated methods in Collection

I rewrote the code by replacing calls to deprecated methods.
I also:

removed this line and this line since it doesn't seem to be used in the code (just assigned)
fixed the result of reindexPendingPages (this line was missing).

PS: I double checked every change.

I'm going to close this and create multiple pull requests.


uxTaskGetSystemState example in latest docs with IDF 5.1.2 does not compile (IDFGH-11707)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/freertos_idf.html#_CPPv420uxTaskGetSystemStatePC12TaskStatus_tK11UBaseType_tPC27configRUN_TIME_COUNTER_TYPE
Code given in the above link results in a compile error even when configUSE_TRACE_FACILITY is enabled
error: unknown type name 'configRUN_TIME_COUNTER_TYPE'
Adding configGENERATE_RUN_TIME_STATS  does not change the compile error either
According to https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/freertos_idf.html#_CPPv427ulTaskGetIdleRunTimeCounterv
configGENERATE_RUN_TIME_STATS + configUSE_STATS_FORMATTING_FUNCTIONS + INCLUDE_xTaskGetIdleTaskHandle must all be enabled for these functions to be available. However there is no obvious way to enable INCLUDE_xTaskGetIdleTaskHandle

configRUN_TIME_COUNTER_TYPE was only introduced recently, so the new example won't work as is with an older version of IDF. In general, try the examples bundled with the version of IDF you are using.

@igrr the documentation refers to the latest 5.1.2 which is the version I am running. Please advise ...

That's not the case, latest docs (i.e. https://docs.espressif.com/projects/esp-idf/en/latest/) are for the master branch. Please take a look here for instructions on finding the docs for your version: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/versions.html#releases.
(Github also labels the most recent stable release as "Latest" on the release page, the Readthedocs docs URL for the latest stable release is https://docs.espressif.com/projects/esp-idf/en/stable/  — which at the time of writing points to 5.1.2 docs.)

My Mistake, thanks for the help.


app icon any size not support

[VERBOSE-2:dart_vm_initializer.cc(41)] Unhandled Exception: 'package:awesome_notifications/src/awesome_notifications_core.dart': Failed assertion: line 169 pos 13: 'BitmapUtils().getMediaSource(defaultIcon!) == MediaSource.Resource': is not true.
awesome_notifications_core.dart:169
#0      _AssertionError._doThrowNew (dart:core-patch/errors_patch.dart:51:61)
#1      _AssertionError._throwNew (dart:core-patch/errors_patch.dart:40:5)
#2      AwesomeNotifications.initialize
awesome_notifications_core.dart:169
#3      LocalNotificationService.initialize
localnotifiction.dart:19
#4      main

so you can insert another icon, at least on Android I did it like this: I removed all "ic_launcher.png", because I wasn't using it as the default for my app's icon and it was precisely that that didn't let the resource:// work. After that, I reinstalled the application and set the directory for another icon that I wanted to use, for example: resource://drawable/icon_app, then it worked, I didn't test it for icons in the lib/assets folder, but it probably also works.


DigiROM type display + battery monitor

Show "X1" etc / "paused" / "RTB" on WiFi/Serial/Punchbag screens.
Show battery meter or "(On USB)" on WiFi/Punchbag screens if set in board_config (awkward to make it refresh at a reasonable rate on Serial, and Serial is always on USB anyway)

TODO: Change turn-1 prompt to "wait for start"


[Bug]: "Message: should have dependency id"

System Info
System:
OS: Linux Debian Bookworm
CPU: x64 13th Gen Intel(R) Core(TM)
Container: Yes
Shell: 5.2.15
Binaries:
Node: 21.7.0
Yarn: 1.22.22
npm: 10.8.2
pnpm: 9.9.0
Browsers:
Chromium
Details
Tried to run an app with NodeJS and got this error.
Panic occurred at runtime. Please file an issue on GitHub with the backtrace below: https://github.com/web-infra-dev/rspack/issues
Message:  should have dependency id
Location: crates/rspack_plugin_javascript/src/dependency/context/require_context_dependency.rs:108
Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Reproduce link
No response
Reproduce Steps
npm start

Can you give us a demo repository to reproduce it?

Can you give us a demo repository to reproduce it?

I am unsure of what is was but i am not experiencing this error anymore

Can you give us a demo repository to reproduce it?

I am unsure of what is was but i am not experiencing this error anymore

Got it, I closed this issues firstly.
You can open other issues,  If you meet it again.


Finalized the responsiveness of office.html plus other minor updates

Finalized the responsiveness of office.html plus other minor updates

Finalized the responsiveness of office.html plus other minor updates


Redis TagDB refactor

This PR refactors the redis TagDB implementation to increase performance by evaluating a single "selector" expression and then treating any remaining expressions as filters on that set, rather than evaluating each expression separately and intersecting the results.  This makes a big difference in cases where previously a large number of values would have had to be read from redis and tested in Python (expressions using !=, =~ or !=~).
It also adds an optimization in the prefetch code so that extractPathExpressions isn't called if there are no remote stores enabled.  In a future PR we'll want to add some caching to the TagDB lookups to avoid the duplicated TagDB lookups when using prefetch.

Codecov Report

Merging #2047 into master will decrease coverage by 0.19%.
The diff coverage is 57.77%.

@@            Coverage Diff            @@
##           master    #2047     +/-   ##
=========================================
- Coverage   69.76%   69.56%   -0.2%
=========================================
  Files          78       78
  Lines        7418     7475     +57
  Branches     1432     1454     +22
=========================================
+ Hits         5175     5200     +25
- Misses       1963     1986     +23
- Partials      280      289      +9

Impacted Files
Coverage Δ

webapp/graphite/render/datalib.py
64.97% <0%> (-0.75%)
:arrow_down:

webapp/graphite/finders/remote.py
48.97% <100%> (+0.7%)
:arrow_up:

webapp/graphite/tags/redis.py
71.21% <58.13%> (-18.67%)
:arrow_down:

Continue to review full report at Codecov.

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


Dynamically defined pie chart with function displays as black

From the examples:
$(".pie-colours-1").peity("pie", {
  fill: ["cyan", "magenta", "yellow", "black"]
})

But this doesn't work:
$(".pie-colours-1").peity("pie", {
  fill: function() { return ["cyan", "magenta", "yellow", "black"]; }
})

SVG produced for all paths: fill="cyan", "magenta", "yellow", "black", instead of one color per path.

When setting a fill with a function it is called for each value of the chart (with the value, its index, and the full array of values) and should return a single value each time.
So with the following HTML:
4,7,6,5

Your fill function would be called four times with the following arguments:
4, 0, [4,7,6,5]
7, 1, [4,7,6,5]
6, 2, [4,7,6,5]
5, 3, [4,7,6,5]

Here's a editable example: https://jsbin.com/recizo/1/edit?html,js,output
Hope this solves your problem.

Thanks! I was confused by the format of the values in the HTML. I was actually using x/100, not a list.


Add sw/fw hashes/ids to get_metadata

Add more info to the standard meta data output functions get_metadata. In particular the following info could be added:
import pysmurf
print(f'pysmurf Client version: {pysmurf.__version__}')
epics_prefix="smurf_server_s4"
print(f"Rogue Version: {S._caget(f'{epics_prefix}:AMCc:RogueVersion', as_string=True)}")
print(f"SMuRF Core Version: {S._caget(f'{epics_prefix}:AMCc:SmurfApplication:SmurfVersion', as_string=True)}")
print(f"FPGA git hash: {S.get_fpga_git_hash_short()}")
print(f"Cryocard fw version: {S.C.get_fw_version()}")

I've been adding this to my notebooks and the standard output looks like this:
pysmurf Client version: 6.0.0
Rogue Version: v4.11.10
SMuRF Core Version: 6.0.0
FPGA git hash: 02ed52a
Cryocard fw version: (10, 188, 222)

just getting around to this, but nice suggestion. I'll make a PR and test it next opportunity. If you can test beforehand just lmk and we can merge!


[NM-24] Calibration plot updates

Description
This PR makes a few small UI changes to the calibration plot shown in the "Calibrate model" step:

Adds a max width of 175px (for all indicators)
Adds a dashed line at 1 (for ratio indicators)
Extends the y axis up to 2 (for ratio indicators)

Also updated Playwright screenshots for the calibration plot and updated bar chart utils tests to account for the newly added max bar width.
Type of version change
Need to discuss versioning changes with Rob before merging.
Major - Minor - Patches - None
Checklist

[ ] I have incremented version number, or version needs no increment
[ ] The build passed successfully, or failed because of ADR tests

/update-snapshots


[#650] Replace document type with document categories

opentrials/opentrials#650

The Travis build is terminated because make test stalled, just as in #109, but I have no idea why. Any hypothesis would be appreciated.

About the upserts, we already have that functionality thanks to the dataset package. Upgrading postgres, as far as I can see, would only make it easier for dataset (actually, sqlalchemy) to implement this under the hood.

@georgiana-b try rebasing master onto this branch and force push, see if it fixes your travis builds.


Fix workflow and update_parameter_sets.py

Description
Add 'develop' branch in the workflow
Add extra indentation in docstring
Fixes #1386

The docstring test was failing due to indentation, I have fixed that and also updated the update_parameter_sets tests. If all checks pass successfully, I guess it's good to merge.


Update Dropify.vue

possibilité de supprimer une image qui n'a pas été uploadé mais séléctionné

Hi @Thalad , can you explain more and give me a use case if possile ?
because setImageSrc is only to set an image passed via src props  when the component mounts,
Thanks

Hi @khofaai,
the setImageSrc() function is also used in the watch for src key.
In my case I want to be able to delete an image displayed via the src props and not uploaded and that is impossible for me

my bad, yes in that case we can make it shorter like
const src = this.src === undefined || this.src === null ? '' : this.src;
this.images = { src }

in the case the props is null or undefined we pass an empty string otherwise we take src value,
what do you think ?

perfect that suits me ! thank you for your reactivity

the same for you :)

@Thalad i can't publish the new version in npm for the moment, i will do it later today, Thanks

ok thanks !


New indicator status page revisions from approval process

Prerequisites:

[x] Unless it is a hotfix it should be merged against the dev branch
[x] Branch is up-to-date with the branch to be merged with, i.e. dev
[ ] Build is successful
[x] Code is cleaned up and formatted

Summary

All text approved by Roni.


ContainerInfoWorker fixes

worker starts to send container info only after websocket is connected
coroner now sweeps all containers and sends list of removed containers to master

@jnummelin did changes based on your review.

@SpComb @jnummelin now coroner is working around the clock.


Uplift BMMs to support slicing along in0 HEIGHT

Branch is: aknezevic/batch_height_sharded
Test is:
pytest -svv tests/ttnn/integration_tests/stable_diffusion/test_sharded_attention.py::test_time_sharded_attnention

Produces a PCC error (0.5 on the 4k case, 0.125 on the 1k)

Works now with 6f3fbc8c950686ea7ab36e92a389ad916e585b62


To Do list: add & remove

This is a PR for To Do list: add & remove project.

Update template.html file
Update main.css file
Update index.js file
Update modules folder

Thank you for approving my project


Profile added

Added my Profile info and picture
issue no. : #2

Hey @iamdevvalecha , Please review this pr under hactoberfest'21.


python312Packages.py3langid: pyproject, relax numpy

needs back port label added
allow use of numpy < 2.0.0
https://hydra.nixos.org/build/277972045
ZHF: https://github.com/NixOS/nixpkgs/issues/352882

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

I think we’re about to get NumPy 2 via python-updates?

I think we’re about to get NumPy 2 via python-updates?

in 24.11?

No, true. Though perhaps it would make more sense to just use numpy_2 here? I’m not sure what the conventions are. cc @mweinelt @natsukium

No, true. Though perhaps it would make more sense to just use numpy_2 here? I’m not sure what the conventions are. cc @mweinelt @natsukium

this is fine. see changelog. nothing changed other than swapping a setup.py to a pyproject.toml when they bumped to numpy 2.0 and python 3.8 is still at an old numpy. IIRC, bumping to a new numpy just means that the wheel can load either numpy 2 or numpy < 2.
https://github.com/adbar/py3langid/commits/master/


Connect this DevOps pipeline to the GitHub repository

As a Developer
I need to connect my pipeline to the GitHub repo
So that when I merge branches then it will go to the repo and test immediately.
Assumptions:

...

Acceptance Criteria:
Given ...
When ...
Then ...

This has to have been done with the two stage delivery pipeline owo.


Swap to uri type

So I meant to just figure out why my GitHub URL was wrong and not finding my project. Pulled a string and well you know the story. I ended up making a basic unit test for URL parsing. Though it should be extendable to other unit tests as well.
You can run the unit tests using: nim test in the main Atlas project folder.
There's a few oddities like finding the Atlas test dirs, but I like to be able to run the tests.nim file from my editor and have it work. Let me know if that works or should be redone.
Also, I saw the MockRun but it had a slightly different intent and faked a lot of things. For example I mocked the github search API rather than just skipping it.

Ah looks like @ringabout already added a tester.nim. I could rename my tests.nim into a turl.nim and have tester run it instread.
I can do that later, but I'll leave the PR up.

Oh, and I tweaked the logic in fillPackageLookupTable so it doesn't try and refresh the package list every time if there's already a packages.json. Helpful for tests and speeding up general usage.

Sorry, please rebase this and fix the regressions.


doc(.github): add pr template

This adds a template for pull requests.
It is meant to be to standardize the process of pull requests and to
help the author and the reviewer during this process.

Hello @csvtuda,
this is the implementation of the checklists for PRs that you have already reviewed. Could you please check the implementation and accept the PR? Many thanks in advance.

@csvtuda If there aren't any more changes required, please confirm the PR. Thanks for your help.


feat(quantic): update facets look and functionality

Related issue
[SFINT-3826[(https://coveord.atlassian.net/browse/SFINT-3826)
Proposed changes
Update look and functionality of facets based on these mockups. Facets included are:

facets
numerical facets
date facets

N.B) In this PR I also changed the search bar a bit so that the clear button does not show on focus if the query is empty. It now only shows when the user starts typing something in the search bar or on focus if the query is non-empty.
Examples

Without Search (toggled visibility)

With search: < 8 matches

With search: many matches ( > 8)

With search: no matches

Nice!
A few points however regarding the look which does not appear to be consistent with the mock ups.

Search bar should be the same width as the facet items.
The facets appear to be a little wider than in the mock ups
The font weight looks a little too high.
The checkboxes don't seem to be vertically aligned with the labels.
The checkboxes seem too small

Mock up

PR Screenshot

Regarding the changes to the searchbox. I think the clear button should show if there is text to clear. Not on focus or anything like that. If there is text in the searchbox, then there should be a button to clear it. After the clear the focus should be on the searchbox text input element.

Nice!
A few points however regarding the look which does not appear to be consistent with the mock ups.

Search bar should be the same width as the facet items.
The facets appear to be a little wider than in the mock ups
The font weight looks a little too high.
The checkboxes don't seem to be vertically aligned with the labels.
The checkboxes seem too small

On it! Thank you for the super fast review

It turns out we will need the search functionality for the date and numeric facets as well. As discussed with @nathanlb , I will change the code by creating a new quanticFacetSearch, mainly so as to avoid repetition. As this will change a lot of the code, I converted this PR back to a draft. @lbergeron  and @nathanlb I take good note of your requested changes and will apply them before re-opening the PR with the new component. Thank you both for the reviews

Noticed also that the show more should look different


Does not start properly

The Fluent Xaml theme editor does not get past the SplashScreen.
It simply hangs - no error, no other change.
Installed via Microsoft Store on Windows Insider build 19025.1.

Were you on my branch or master?

Installed from the Microsoft store, so I did not build it from source.
There is somebody else who had the same issue and put it as a review in the store.

Hmm, I'm not seeing that review, which is troubling...
As a side note, have you pulled from master on this repo and tested the app? If that's working for you, but the store one isn't I should probably push an update to the store sooner than planned to fix that.

The review is probably in the Dutch part of the store? See below:

The master branch works fine for me!

Thanks! It's probably due to being in a different language that I cannot see it...
That being said - good to know the repo works for you! I'm going to be updating the app soon with the same version as on here. Hopefully it'll fix the store issue too.

Yes I understand, thanks for picking this up!
BTW I assumed that app publishers would be able to see all reviews for their application?

We can, I'm just new the app publishing arena, so I wasn't sure where I could do that. I've figured it out since 😄

hey, before and after the last update, the app don't work after the splash screen ...
my pc: win 10 home, v.1903 and the latest updates, localization: french ...
installed in the Store ...
if this help you ...

@FJduFou Thank you for following up!
Sorry you're still running into this - I'll attempt to connect with someone on the store team about this as the app appears to run just fine when not installed from the store...

Yes, I alway have this problem

Wanted to keep you updated @fjdufou - still working on trying to locate this failure. It appears to be a XAML issue with failing to load when localization files are involved. I'm attempting to try and get a repo on my machine so I can get a dump on where it's having issues.
Thank you for your patience!

Wanted to keep you updated @FJduFou - still working on trying to locate this failure. It appears to be a XAML issue with failing to load when localization files are involved. I'm attempting to try and get a repo on my machine so I can get a dump on where it's having issues.
Thank you for your patience!

If this help you: my W10 is in French ...

I've set it French (France) and I am not able to reproduce the issue - do you have more specifics about the French mode you're in? As in French (Guinea) or French (French Polynesia)?

I've set it French (France) and I am not able to reproduce the issue - do you have more specifics about the French region mode you're in? As in French (Guinea) or French (French Polynesia)?

fr-fr, not region ...
i'm download from the store, the latest version, i have verify and i don't have more updates ...

Hey @fjdufou - since I'm still not able to repo this - would you be interested in following some short steps I'll walk you through that creates a dump file and attaching it here as a zip? That way I can take a look at the source of your failure directly from where you can repo it.
If you can, please follow these steps:

Launch the fluent theme editor
Open task manager and click the "More Details" dropdown if not already enabled:

Expand the app with the drop down arrow
Right click on the app and click "Create dump file"

Once the dumping process is finished click "open file location"

Once file explorer has opened, right click on the .DMP file and click Send To > Compressed (zipped) folder

Click and drag the zipped file to a reply comment here on this thread

Thank you!

@kikisaints The file is too big for upload this in the comment, but I have add in my OneDrive, the link is this:
https://1drv.ms/u/s!AuacpD9VeMSygaldc4a-DT2AUJDHrA?e=2Qonmc

Works from France on Windows 10 1909. Can I do anything to help with the project?

Don't works from France on Windows 10 1909.
^^

Hi @FJduFou it's looking like this might be a Store issue that I'm still trying to track down. Unfortunately this cannot be replicated even with a clean machine set to the French region. MS is also under a "work from home quarantine" right now, so I might not be able to spend cycles on this until a little while.
In the meantime - does cloning the repo and running the app work for you? If not maybe in debug mode you might get some runtime information.

@kikisaints it's works in debug mode

yes! I'm not only.

I can confirm that with the app installed from Microsoft Store, the app works without issue when the Windows display language is set to English (Australia) and does not progress past the splash screen with the Windows display language set to French (France), with all other settings remaining the same.

Still same problem. Setting Windows display language to english (i used en-GB) is only way to get the app past the splash screen (on Windows 10.0.19042) when downloaded from the app store.
More issues:

the app crashes when you are foolish enough to try to input .5 as a value for border width,
you can't modify system accent colors (but they are exported); only base, alt and primary
font editing is still ' coming soon!'

The Fluent Xaml theme editor does not get past the SplashScreen. I have installed the editor from the Microsoft store.

Does not work in French, stick on the first screen with no menu visible. How to get it in English ?


Gated, experimental upgrade command + uber AzureClient + generate can --deploy

Import AzureClient from azkube. Refactor and clean it up further to handle OAuthConfig, automatic tenant ID and to stop stashing things on the client that shouldn't really be necessary to persist. Remove need for create of AzureClient to know the tenantID ahead of time. The client ctors will auto-discover it.

Add UberClient interface, TemplateDeployer interface, along with a VMClient interface. Now the UberClient can have a mock implementation, and the real code can use the AzureClient implementation that is backed by real Azure SDK clients.

Add ./test/upgrade.sh script that wraps the CLI... this is really not necessary at all with the device auth support though, especially with the token caching. I might remove this anyway.

Add device auth support. It means you can upgrade or generate --deploy with only supplying the --subscription-id. TenantID is auto-discovered and the user can auth the same way they do with az login. The token is also cached, so they only need to interactive login once!

Along with that, move all of the auth flags / client creation to root.go so that generate and upgrade can share that code (and eventually scale, etc).

Improve UX for the --upgrademodel-flag file.

Change all instances of logrus.Logger to logrus.Entry as that's the more appropriate thing to pass around.

This change is

Closing to send smaller PRs.


The slider doesn't display and work properly on first display

Hi
First of all, check my live demo https://ui.mofect.com/moblog  the top slider doesn't display properly, I have set slidesPerView to 2, but it only displays 1 and can't be scrolled. But when I resize the window size, it works like a charm.
I have read this similar issue https://github.com/kidjp85/react-id-swiper/issues/185 but no solution for me. Here are my codes:
import React, { Component } from 'react';
import { Link } from 'react-router-dom';
import Swiper from 'react-id-swiper';
import SliderItem from '../../components/slider-dom';
import { Pagination } from 'swiper/dist/js/swiper.esm'

/* SlideShow */
class Slider extends Component{

  constructor(props){
    super(props);
    this.state = {
       data: [],
    }
  }

  componentDidMount() {
     this.loadSlider();
  }

  loadSlider = () => {
     const { data } = this.state;

     const url = `https://xxxxxxxxxxx/`;
     fetch(url)
       .then((response) => {
          return response.json()
        })
       .then(json => {
         this.setState({
           data: json,
         });

       })
       .catch(function() {
     });
  };

  loop = () => {
    let loop = [];

    this.state.data.length > 0 && this.state.data.map((slide, i) => {

          loop.push(
            <SliderItem
              key={ i }
              id={ slide.id }
              postType={ slide.post_type }
              postID={ slide.post_id }
              pageID={ slide.page_id }
              productID={ slide.product_id }
              title={ slide.title }
              image={ slide.image }
              description={ slide.description }
            />
         );
    });
    return loop;
  }

  render() {
    const params = {
      slidesPerView: 2,
      loop: true,
      spaceBetween: 10,
      modules: [Pagination],
      shouldSwiperUpdate: true,
      rebuildOnUpdate: true,
      pagination: {
        el: '.swiper-pagination',
        type: 'bullets',
        clickable: true
      }
    }

    return(

          { this.state.data &&
            <Swiper { ...params} >
              { this.loop() }
            </Swiper>
          }

    );
  }
}

export default Slider;

Anything I missed?

 형식이 아닌 컴포넌트 형식은 작동하지 않습니다.  형식으로 랜더링 되게 작성하면 해결 됩니다.
Component formats other than  will not work. You can do this by creating a rendering in the  format.
Use translation app.

NOT:
<Swiper>
    <SliderItem />
</Swiper>

YES:
<Swiper>

Something

</Swiper>

컴포넌트 형태로 랜더링 하면 실제 마크업은 div로 표시되지만 스와이퍼는 div로 인식하지 않습니다. SliderItem 이라는 엘리먼트로 인식하는거 같습니다.
저도 같은 문제가 있었는데 div로 랜더링 되게 하면 동작합니다..
When render in component form, the actual markup is displayed as div, but the swipe is not recognized as div. It is recognized as an element called SliderItem.
I had the same problem. However, it works when it is render with div.
I'm sorry to use the translator.

Looks like rebuildOnUpdate: true, should always be set true

any help please, I m having the same issue,

I had the same issue und found a workaround.
I think the problem is that the swiper initialization happens before it is rendered to the DOM and thus it sets wrong values for width and hight etc.
You can manually update the swiper when you are sure that everything is renderd to the DOM like so:
useEffect(() => {     let timeout ;     if (swiper !== null) {       timeout = setTimeout(() => swiper.update(), 500)     }     return () => {       clearTimeout(timeout)     }   },[swiper])
More elegant solutions are very welcome.

I have that issue too. Some one help me plz...

For anyone that is still searching for the solution, just make sure the length of the array of items is bigger than 0, here is how it is solved in one of the issues: https://github.com/kidjp85/react-id-swiper/issues/185`

Tuve el mismo problema y encontré una solución.
Creo que el problema es que la inicialización de swiper ocurre antes de que se procese en el DOM y, por lo tanto, establece valores incorrectos para ancho y altura, etc.
Puede actualizar manualmente el swiper cuando esté seguro de que todo se procesa en el DOM de la siguiente manera:
useEffect(() => {
    let timeout ;
    if (swiper !== null) {
      timeout = setTimeout(() => swiper.update(), 500)
    }
    return () => {
      clearTimeout(timeout)
    }
  },[swiper])

Las soluciones más elegantes son muy bienvenidas.
Sistema:
"gatsby": "^ 2.13.29"
"react-id-swiper": "^ 2.3.2"

What's swiper ??  Maybe you could put the complete code? :-)

I think here is the issue
 return(

          { this.state.data &&
            <Swiper { ...params} >
              { this.loop() }
            </Swiper>
          }

    );

You should set the condition to this.state.data.length > 1

in my case, the problem was resolved using the parameter "observer" ( Set to true to enable Mutation Observer on Swiper and its elements. In this case Swiper will be updated (reinitialized) each time if you change its style (like hide/show) or modify its child elements (like adding/removing slides))
src: https://swiperjs.com/swiper-api
      <Swiper
            // className='swiper-container'
            tag='section'
            wrapperTag='ul'
            spaceBetween={30}
            slidesPerView='5'
            autoplay= {true}
            centeredSlides= 'true'
            //loop = 'false'
            navigation
            pagination
            onInit={swiper => { console.log('Swiper initialized!', swiper) }}
            effect='coverflow'
            onSwiper={(swiper) => console.log(swiper)}
            onSlideChange={() => console.log('slide change')}
            className = 'swiper-container'
            //shouldSwiperUpdate
            //rebuildOnUpdate
            observer
        >

In my case its worked as soon as i passed key props as attribute.


BUG: scipy-1.11.z.tar.gz file missing in 1.11.z releases

Describe your issue.
I want to create an update for python3-scipy fedora package, but source code with initialized submodules is missing for 1.11.z release: https://github.com/scipy/scipy/releases/download/v1.11.1/scipy-1.11.1.tar.gz
It was present in previous releases. Is it intentionally ommited?
As a workaround for testing  I have cloned the repo, initialized the submodules myself and created the tarball myself.
Reproducing Code Example
exists: https://github.com/scipy/scipy/releases/download/v1.10.1/scipy-1.10.1.tar.gz
does not exist: https://github.com/scipy/scipy/releases/download/v1.11.1/scipy-1.11.1.tar.gz

Error message
-

SciPy/NumPy/Python version and system information
scipy-1.11.1

It was not intentional, let me see what I can do about it.

scipy-1.11.1.tar.gz should now be available on the appropriate GitHub release page--it will have a newer timestamp than the other assets, but should otherwise be "ok--" I used the same version of Cython and NumPy that were used to produce the rest of the assets there.
If it looks "ok" to you, feel free to close the ticket.

Thank you! Different timestamp is not an issue.


Add orchrefs to libcalico-go

Description
Add a new field to libcalico-go called orchRefs. This field will allow for association between a k8s node and the etcdNode object that matches it, and allow for cleanup of stale nodes.
Release Note

Add the orchRef field to the Node data model.

@ozdanborne changes look good to me - could you add a really simple test here: https://github.com/projectcalico/libcalico-go/blob/master/lib/client/node_e2e_test.go#L48
This will verify that the data can be read back from the datastore once written.

Closing as work was done in #614


Canadian address with left-hyphenated unit/suite

Are there any plans to be able to parse Canadian addresses like "#401-43 HANNA AVE" where the street number is 43 and unit number is 401?

No, sorry. Libpostal tags each token in the string with a label, and tries not to modify the user input too much. As far as our tokenizer is concerned "401-43" is one atomic token and cannot be broken down further. Also, libpostal is an international parser and that format isn't used in the same way in all countries. There's a lot of ambiguity in what a hyphen means around the world. Sometimes a hyphen means a range or house numbers, even within Canada (perhaps "401-403 HANNA AVE"). In the US, Queens addresses contain hyphens as part of the house number. In Japan the house number is composed of neighborhood-block-building. In Malaysia there's no consistent format for what the various hyphenated parts mean.
Luckily, that problem's not one that libpostal necessarily needs to solve. If you know a priori that your addresses are in Canada, it should be easy enough to use a regex on the output from libpostal to break our house_number component down in to unit and house number respectively. Libpostal's NLP-based model can handle the many other types of ambiguities in a free-form address, and the regex can be used to handle house numbers that match that specific pattern.


In provisioning of storages, set public containers to False by default

Figure out what is the setting to turn off public containers by default in all storage accounts we provision.
Add it to all provisioning scripts.

Resolved in #132


fix(minimal-slp-wallet): Specing v4.5+ for peer minimal-slp-wallet

:tada: This PR is included in version 2.1.1 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


PulseAudio doesn't start because of malloc assertion failure after 21.11 update

Describe the bug

Assertion 'size <<PHONE_NUMBER>)' failed at pulse/xmalloc.c:72, function pa_xmalloc0(). Aborting.

Steps To Reproduce
Steps to reproduce the behavior:

Upgrade to latest 21.11
Reboot

Expected behavior
PulseAudio should start.
Additional context
Log
Notify maintainers
@lovek323
Metadata
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.106, NixOS, 21.11 (Porcupine)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.16`
 - channels(root): `"nixos-21.11.336619.01e87b327aa"`
 - channels(username): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

After looking around, I saw two similar issues

https://www.odi.ch/weblog/posting.php?posting=721. They used strace to determine that pulse was failing while opening a file under $HOME/.pulse. They removed that directory and it solved the issue
https://together.jolla.com/question/144623/solved-no-more-sound-nor-microphone-pulseaudio-problem/. They removed everything under $HOME/.config/pulse to solve their issue

The issue is likely one of state being corrupted. Do you have a folder $HOME/.config/pulse containing what appears to be some state files? If so, try removing them (or temporarily renaming the directory. Idk what exactly it is that is stored there) and then rebooting

@hqurve I have the same issue and I tried your tip and moved $HOME/.config/pulse to $HOME/.config/pulse.old but did not solve the issue. any other suggestions?

Okay, for what its worth. I made a vm with kde and pulseaudio and I experience no such issue. Are you using a desktop environment or are you using a wm only?
I could propose a quick sanity check. If you create a new user, does the issue translate there as well?

@hqurve Thank you! The following (or a subset of it; the daemon-reload was probably unnecessary) fixed my system:
mv ~/.config/pulse{,.old}
systemctl --user daemon-reload
systemctl --user restart pulseaudio

I can also confirm that pulseaudio works now after the upgrade from Gnome 41 to Gnome 42.
I propose to close this issue.


Provider integration is broken for serverless >2.30.3

The search for error message contents from the provider call at https://github.com/deliveryhero/serverless-aws-documentation/blob/master/src/documentation.js#L107 is broken in serverless > 2.30.3 by the change here https://github.com/serverless/serverless/commit/89b813da51cedf80ca66ae4b4ad269edf8614ec0

The actual error object thrown by the serverless awss provider has changed in the above mentioned versions.
The message of the thrown error includes this strings 'Invalid Documentation version specified' and 'NotFoundException'
We published a fix and we plan to maintain the package.
https://www.npmjs.com/package/@kakkuk/serverless-aws-apigateway-documentation


Deprecate Piranha Nano and steer folks to Piranha Embedded

What's the reason for this? I thought that Piranha Nano is suitable for cloud functions (e.g. AWS lambda) because it doesn't support HTTP session, for example. Is it possible to tweak Piranha Embedded to strip it down to what is absolutely necessary for cloud functions?

@OndroMih Simplification of the overall offerings. In reality if you look at Piranha Nano and Piranha Embedded the only place they are different is the processing pipeline. So the intent here is to show how folks can migrate their code from Nano to Embedded by using Embedded and customizing the processing pipeline.

In that case, I think it's better to rather migrate fro Embedded to Nano, as this would follow the Piranha philosophy to make it possible to "strip away all these features until only the bare libraries remain". I think that the functionality of Piranha Embedded should be achieved by starting with Piranha Nano and adding building upon it. I'm afraid Piranha Embedded is already too much for AWS Lambdas and if we don't offer a smaller distribution, there would be no way to achieve the same thing as with Nano nowadays. Besides that, I think that Nano is much better name than Embedded ;-)

Eventually I think I would like to even deprecate Piranha Embedded and just describe how you would use the core Piranha API / implementation (2 Jars really) and then have a PiranhaBuilder API. And then demonstrate how to use that to deliver the equivalents of what Piranha Nano and Piranha Embedded do at the moment?  Thoughts? @OndroMih @arjantijms @Thihup

Yes, I agree @mnriem. Having just one thing is always better and straightforward. I would call everything just Piranha or Piranha Cloud. I think that even Piranha Micro and Server can be distributed as a set of dependencies plus a maven plugin that builds everything together. But sometimes having a downloadable runtime like Piranha Micro and Piranha Server may more convenient than having to build them from a maven project so I'm not against keeping Micro and Server.

@OndroMih That is indeed the vision ;) So I will now go ahead and deprecate Piranha Nano .... so we can start that process. Note that generally speaking I like to deprecate first. Then in the next cycle deliver what folks should migrate to. And then in the cycle thereafter remove the deprecated code it gives folks 2-3 months if they are tracking the current branch ;)


Remove obsolete define in the iOS buildsystem code

Follow-up to https://github.com/godotengine/godot/pull/57822.
This define was used by the WebM/libvpx code, but it's now removed in master. There is no reference to LIBYUV_DISABLE_NEON anywhere in the codebase (including third-party files).
Note: Not cherry-pickable to 3.x as WebM code is still present there.

Thanks!


Adding art replacement file

Adding a file for ART so that replacement of values in the CSV and package files can be completed

/lgtm


XY grid - Margin issue with fixed position

When I add "grid-margin-x" to grid, my fixed div(which has no connection to grid) just go up/down out of the window when scrolling. Why this happens and how to fix it?
Simple code proof:

    Lorem ipsum dolor sit amet, consectetur adipisicing elit. Voluptates, ducimus.

   .cell*15

NOTES: look on small size screen, it's easier to realize the problem

@johnylaravel I've setup a CodePen with your code example: https://codepen.io/brettsmason/pen/MvOdWp
Could you explain the issue in more detail? I'm not understanding your problem.

I'm 15 commits away from that, so now when I add "grid-margin-x" it give me scroll x, like whole website can move right and left. Website is out of window.
You can see that example in your pen, look at bottom scroll X.
That problem can be solved for large screens by adding ".grid-container" as a wrapper. But the problem is now on small screen size, it don't work on small screen.. Do you have any solution for that?
Thanks for reply!

@johnylaravel, can you provide a new test link and an explanation of what you're trying to do?

Closing as we did not receive further feedback.
Please let us know if there is new feedback and we will reopen the issue.


[DOC] fix autodoc for spurrious toggles

Right now toggles appears everywhere, it should only appear in sections that have classes and functions. This does that.
Can be tested for a while here: http://<IP_ADDRESS>/api/python/docs/api/gluon/index.html
@sojiadeshina @aaronmarkham

Aaron. Ould you retrigger centros gpu and Unix gpu?

Aaron. Ould you retrigger centros gpu and Unix gpu?

Yep... restarted.


Typo in PowerShell Functions Template Code  ("Porperty" instead of "Property")

The run.ps1 powershell template code for a timer-triggered function has a typo, "porperty" instead of "property":
https://github.com/microsoft/vscode-azurefunctions/blob/aef35edeaac21748bd8e37186aa7c5d2bfb52a4b/resources/backupTemplates/script/~3/templates/templates.json#L3523
https://github.com/microsoft/vscode-azurefunctions/blob/aef35edeaac21748bd8e37186aa7c5d2bfb52a4b/resources/backupTemplates/script/~4/templates/templates.json#L3523

Thanks for reporting this. Could you file the issue here: https://github.com/Azure/azure-functions-templates/
We don't actually control the templates, that's done by this team.

Thanks. Looks like it's already been fixed there: https://github.com/Azure/azure-functions-templates/blob/dev/Functions.Templates/Templates/TimerTrigger-PowerShell/run.ps1#L7


Type error in group decorator

Whenever I try to create a group which uses decorator for database access the following problem happens:
The group is working as intended as long as I don't need to access the database.
When it comes to the database access, the instance (in this example the BooksDatabase instance) produces the following error:
TypeError: db.getBooks is not a function. (In 'db.getBooks()', 'db.getBooks' is undefined)
The error only happens in groups, when I try the same with a db decorator on the main Elysia instance it works without any issues.
Is there any workaround for this, or any step I missed?
Thanks for the help! :)
Demo code for the issue:
import { swagger } from "@elysiajs/swagger";
import Database from "bun:sqlite";
import { Elysia, t } from "elysia";

interface Book {
  id?: number;
  name: string;
  author: string;
}

class BooksDatabase {
  private db: Database;

  constructor() {
    this.db = new Database("books.db");
    this.init()
      .then(() => console.log("Database initialized"))
      .catch(console.error);
  }

  async getBooks() {
    return this.db.query("SELECT * FROM books").all();
  }

  async init() {
    return this.db.run(
      "CREATE TABLE IF NOT EXISTS books (id INTEGER PRIMARY KEY AUTOINCREMENT, name TEXT, author TEXT)"
    );
  }
}

const bookService = new Elysia({ prefix: "/books" })
  .model({
    book: t.Object({
      name: t.String(),
      author: t.String(),
    }),
  })
  .decorate("db", new BooksDatabase())
  .get("/", async ({ db }) => await getAllBooks(db));

const getAllBooks = async (db: BooksDatabase) => {
  try {
    const books = await db.getBooks();
    return { success: true, books };
  } catch (e) {
    console.log(e);
    return { success: false };
  }
};

const app = new Elysia()
  .model({
    book: t.Object({
      name: t.String(),
      author: t.String(),
    }),
  })
  .use(swagger())
  .group("/v1", (app) => app.use(bookService))
  .listen(8080);

package.json:
  "name": "elysiaTest",
  "version": "1.0.50",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "dev": "bun run --watch src/index.ts"
  },
  "dependencies": {
    "@elysiajs/cookie": "^0.6.1",
    "@elysiajs/cors": "^0.6.0",
    "@elysiajs/swagger": "^0.6.2",
    "elysia": "latest"
  },
  "devDependencies": {
    "bun-types": "latest"
  },
  "module": "src/index.js"
}```

This is the same issue as #143

Should be fixed in https://github.com/elysiajs/elysia/pull/103.
Let me know if the problem stills persists

Tested with example above on "elysia": "^0.7.1" and i still have the same issue @SaltyAom

Can't replicate with above code on my end, maybe Bun doesn't update the cache?
This is specifically resolved in 0.7.1, can you try running:

@SaltyAom my bad, slight confusion on my end. The above example working but i notice the issue persists when adding the decorator outside the group.
this works:
const bookService = new Elysia({ prefix: '/books' })
  .decorate('db', new BooksDatabase())
  .get('/', async ({ db }) => await getAllBooks(db))
const app = new Elysia()
  .group('/v1', app => app.use(bookService))
  .listen(8080)

this don't:
const bookService = new Elysia({ prefix: '/books' })
  .get('/', async ({ db }) => await getAllBooks(db))
const app = new Elysia()
  .decorate('db', new BooksDatabase())
  .group('/v1', app => app.use(bookService))
  .listen(8080)

But maybe thats not suppose to work in the first place? Or are we suppose to add the decorator to every group? If created seperatly?

@SaltyAom it works now, thank you!


Demo

Is there a reason that the demo is not included in the distribution?

Yes, that definitely must be mentioned because Drop won't work without Tether and that isn't mentioned anywhere...

Hm, now I see that is mentioned on Github (in readme.md) but I was trying with instructions from a website.

@milanstosic Sorry about the confusion. We are in the process of updating all of the documentation (so the website), but first wanted to tackle updating the code in the tether based projects first. But yes, Tether must be included in your project to use Drop. Tether used to come bundled with Drop, but we have decided to drop the bundling (for now) in favor of providing proper UMD.

Ok, thanks.


Restructured files.

Refactored and restructured nimsuggest.
The main changes are in how command-line arguments are parsed, and how modes are internally handled.
The command line is now split into 4 distinct parts: global switches, mode, mode switches, and project file. Global switches affect the running of Nimsuggest, and are mode-agnostic. Mode switches are specific to each mode, and control operation of that mode. Compiler switches are supported through 'nim.' prefixed switches in the global switches section. These changes allow for a more formulaic construction of command line invocations by editors, and help prevent possible switch collisions.
Modes are now comprised of a set of methods acting on a sub-type of ModeData. At runtime, a ModeData initializer corresponding to each mode is added into a table keyed to the mode's name. This table is then searched for the mode given on the command line, and the various methods attached to the underlying ModeData type are used to handled parts of Nimsuggest. Though there is a run time cost associated with the change in models, this new architecture allows clean separation between core and mode-specific logic, and makes adding new modes much simpler.
This is a backwards incompatible change, however given the fact that this is primarily a tool used by other programs, the changes aren't as severe as they normally would be - it's quite a bit easier to change program code than to change someone's habits.

Well sorry, but I don't like it. I don't understand which problem it solves and objectively you doubled the code (" 709 additions and 351 deletions") and made it incompatible with existing tools. Constantly requiring people to update their nimsuggest support is mean. Refactorings shouldn't produce larger code and it definitely should not break the exposed protocol.

Keep in mind that a portion of the additions are actual comments and whitespace additions, as well as input validation and checking for command line arguments. I can add some compatibility logic for the old command line syntax, as well as a --version switch so that editors can distinguish between versions.


Fixes small Powershell' loader issues

Seems like there's not really anything anyone is waiting for, is there?

@thor What do you mean? :smile:


Recipes: Raise Exception on Previous Version parsing/resolution failure

https://github.com/NYCPlanning/data-engineering/blob/90497a2886a411a71e4746016b31ed09f838b18e/dcpy/lifecycle/builds/plan.py#L87-L101
We should only try to resolve the previous version when we need to, and not by bypass errors.

One counterpoint to the "when we need to" - several builds rely on this env var existing in bash. I think having a standard VERSION_PREV env var that gets output during plan makes sense to that end

@fvankrieken that makes sense. Maybe we should just set VERSION_PREV before we plan? And here we'd just raise an exception if the recipe type requires that var but it's missing?

I think that makes sense. Depends what we want to the scope of planning to be - in some sense, it makes sense to go be looking up versions for both sources and past builds at the same time, it's a very similar operation in that sense

Also this is not relevant to this issue but how did you get the code to display inline?? I have been trying on another issue with no luck

Also this is not relevant to this issue but how did you get the code to display inline?? I have been trying on another issue with no luck

I think I just copied the permalink to a range of lines, and GH took care of the rest.


Failing to detect when the payload contains single byte or alternate utf-8 encoding

Description
Coraza doesn't detect the attacks when the payload contains single byte or alternate utf-8 encoding.
Steps to reproduce
Test Case 1:
test_title: 941310-1
desc: Positive test using single byte
stages:
  - stage:
      input:
        dest_addr: <IP_ADDRESS>
        headers:
          Host: localhost
          Content-Type: "application/x-www-form-urlencoded; charset=us-ascii"
          User-Agent: OWASP ModSecurity Core Rule Set
          Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
        method: POST
        port: 80
        uri: /
        data: var=\xbcscript\xbealert(\xa2XSS\xa2)\xbc/script\xbe
output:
  log_contains: id "941310"

Test Case 2:
test_title: 941310-3
desc: Positive test using alternate utf-8
stages:
  - stage:
      input:
        dest_addr: <IP_ADDRESS>
        headers:
          Host: localhost
          Content-Type: "application/x-www-form-urlencoded; charset=us-ascii"
          User-Agent: OWASP ModSecurity Core Rule Set
          Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
        method: POST
        port: 80
        uri: /
        data: var=\xd0\xbcscript\xd0\xbealert(\xc2\xa2XSS\xc2\xa2)\xd0\xbc/script\xd0\xbe
output:
  log_contains: id "941310"

Expected result
"id: 941310, rule_msg: US-ASCII Malformed Encoding XSS Filter - Attack, match_msg: Matched Data: ¼script¾ found within ARGS:var: ¼script¾alert(¢xss¢)¼"
"id: 941310, rule_msg: US-ASCII Malformed Encoding XSS Filter - Attack, match_msg: Matched Data: ¼scriptо found within ARGS:var: мscriptоalert(¢xss¢)м/script"
Actual result
Coraza does not detect it.

Hi @soujanyanmbri, thanks for coming by. Indeed this test isn't passing yet but we are working towards that (see this list which include all the CRS test not supported yet). In the mean time, are you up to come by with a fix for this?

I think using invalid utf8 with go regex may be tricky if not possible as it only affects Unicode.
I wonder if any such rules should be edited in CRS to alway apply url encoding or escaping transformation so the regex can be against ascii. @M4tteoP any thoughts on that?

In one hand converting user input could be an issue in the long term
because God knows what users can pass and how could that screw us. One
option is to detect such strings, do the conversion and add a warn log so
user is aware of the problem.
Also I think wasilibs-re2 wont have this problem so probably we want to
provide a build tag with this regex package to offer this alternative
solution (which I think is more performant aswell) if we can't get it right
away with pure go.
On Tue, 7 Mar 2023, 10:50 Anuraag Agrawal, @.***> wrote:

I think using invalid utf8 with go regex may be tricky if not possible as
it only affects Unicode.
I wonder if any such rules should be edited in CRS to alway apply url
encoding or escaping transformation so the regex can be against ascii.
@M4tteoP https://github.com/M4tteoP any thoughts on that?
—
Reply to this email directly, view it on GitHub
https://github.com/corazawaf/coraza/issues/688#issuecomment-1457867042,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYASFHPSKGOLD3ZWJ64TW24AETANCNFSM6AAAAAAVQXL67Q
.
You are receiving this because you commented.Message ID:
@.***>

In one hand converting user input could be an issue in the long term because God knows what users can pass and how could that screw us.

Do you mean about applying a transform like url encoding? These are used all over the place in CRS and are well understood transforms so not sure how a user could cause problems with it.

What about changing the native go regex engine with a different one? I think someone mentioned that there is an actual better-performing alternative that might also solve this problem...

Maybe we can try the transformation first before jumping into the wasilibs

We should also start normalizing transformations, I think we should ignore the concept of runes and start working only with []byte. But right now some transformations relies on runes and some on []byte

I agree with @jptosso. If you want to detect encoding confusion attacks you can't rely on runes.

I think using invalid utf8 with go regex may be tricky if not possible as it only supports Unicode.

The regular expression compiles with re2 (we use re2 as backend for generating regular expressions now). Are you saying that the expression doesn't match? That must mean Coraza treats the input as runes, not bytes, is that correct?

I wonder if any such rules should be edited in CRS to alway apply url encoding or escaping transformation so the regex can be against ascii.

I think that might actually work. There are two transformations that look promising (from a quick scan of the documentation): hexEncode and urlEncode, I favour the former.
The downside is that the input length will increase ~2x and readability will suffer even more. But I think that would be acceptable.

I think we should ignore the concept of runes and start working only with []byte

I looked through many operators when understanding #550 - IIRC, modsec has some locations that operate on unicode (lowercase I think is unicode, others mostly aren't?) and others that don't. We probably wouldn't be able to do this if prioritizing matching the behavior of modsec.

That must mean Coraza treats the input as runes, not bytes, is that correct?

Indeed - regexes with invalid runes would fail to compile completely but all the expressions are fine. Input have invalid bytes treated as unicode replacement character by the Go regexp library
https://pkg.go.dev/regexp#pkg-overview
Applying a transformation would allow this rule to be more compatible with languages where strings are expected to have valid bytes (other languages would include Java).
That being said, there are a lot of variables there so a heavyweight transform may not be worth it from a perf standpoint - Coraza has some logic to ensure a transformation is only applied once per phase, but I don't think we have this sort of encoding transform anywhere right now so it would be adding the overhead.
Perhaps we can go ahead and add some within Coraza itself to handle this - we can scan the operator string for regex for \xb* indicating arbitrary byte match, and either replace with hardcoded efficient logic for known strings, like the current one for rule 941310, or otherwise add the encoding transform and rewrite the expression automatically.

...\xb*...

Did you mean (?:\x[\da-f])+?
It would be better if CRS didn't have to care. No one will remember to apply such a transformation in a future rule, and even if we had failing test for Coraza it wouldn't be obvious why the test would fail only for Coraza.

Yeah I think that's what I meant, got confused since coincidentally all the characters in the CRS rule started with \xb
I think whether CRS cares or not is mostly about how broadly it is supposed to be applicable. For example, if someone wrote an implementation of CRS in Rust, I think it would have the same problem as Go as all strings in Rust must be valid utf-8 and the regex package only works on strings
https://docs.rs/regex/latest/regex/struct.Regex.html
If CRS is really only meant for ModSec and Coraza, then we can probably hardcode something into Coraza to workaround it

Well, ideally we would have a "universal SecLang" with "universal regular expressions". Then we could "compile" for different engines, and one such "compile step" could be to add the hexEncode transformation in such a case.
But you're right, it's not a simple problem. For now, I think, we need to be realistic: there's only ModSecurity and Coraza at the moment, and that's what we need to support.

I think it makes sense to address this issue specifically in coraza for now
as any other change would not be implemented in a timely manner. Do you
want to take a stab on this @anuraaga? Otherwise I can work it out.
On Wed, 22 Mar 2023, 07:19 Max Leske, @.***> wrote:

Well, ideally we would have a "universal SecLang" with "universal regular
expressions". Then we could "compile" for different engines, and one such
"compile step" could be to add the hexEncode transformation in such a
case.
But you're right, it's not a simple problem. For now, I think, we need to
be realistic: there's only ModSecurity and Coraza at the moment, and that's
what we need to support.
—
Reply to this email directly, view it on GitHub
https://github.com/corazawaf/coraza/issues/688#issuecomment-1478978402,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYATQ2ADHYLNH65YL4Q3W5KKYXANCNFSM6AAAAAAVQXL67Q
.
You are receiving this because you commented.Message ID:
@.***>


earlyoom: 1.2 -> 1.3

Motivation for this change
https://github.com/rfjakob/earlyoom/blob/v1.3/README.md#changelog
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Built and tested locally :+1:

@dtzWill @mmahut thanks!


Provide network when restoring accounts

This PR

replaces #1979
provides mainnet with default node for the source to lookup names during account restoring. Depending on the resolution of names a different stx address is used in the account so that the username is always owned by the address of the account.

cc/ @kyranjamie @fbwoolf @pradel

Will push another branch of this to trigger build

Superseded by #2196


Feat. #77878 - trim git clone

According to #77878 , I add a feature that can trim 'git clone '.

Thanks! :beers: