Cesium JS: scaleToGeodeticSurface.js:34 Uncaught DeveloperError {name: "DeveloperError", message: "cartesian is required.", stack: "Error↵

I upgraded my cesium version from v1.59 to v1.77. I have also updated all the deprecated constructors to the latest, but I keep running into this issue when I try to draw on my asset. Does anyone know what's causing this? Here's a screenshot for more context:

Here's the full error:
`An error occurred while rendering. Rendering has stopped.
TypeError: Cannot read property 'length' of undefined
TypeError: Cannot read property 'length' of undefined
at Function.push../node_modules/cesium/Source/Core/PolygonGeometry.js.PolygonGeometry.createGeometry (http://<IP_ADDRESS>:8000/static/dist/npm.cesium-01ff433966601611e5b8.js:63652:22)
at loadSynchronous (http://<IP_ADDRESS>:8000/static/dist/npm.cesium-01ff433966601611e5b8.js:243718:46)
at Primitive.push../node_modules/cesium/Source/Scene/Primitive.js.Primitive.update (http://<IP_ADDRESS>:8000/static/dist/npm.cesium-01ff433966601611e5b8.js:244518:7)
at ClassificationPrimitive.push../node_modules/cesium/Source/Scene/ClassificationPrimitive.js.ClassificationPrimitive.update (http://<IP_ADDRESS>:8000/static/dist/npm.cesium-01ff433966601611e5b8.js:181841:19)
at GroundPrimitive.push../node_modules/cesium/Source/Scene/GroundPrimitive.js.GroundPrimitive.update (http://<IP_ADDRESS>:8000/static/dist/npm.cesium-01ff433966601611e5b8.js:203590:19)
at PrimitiveCollection.push../node_modules/cesium/Source/Scene/PrimitiveCollection.js.PrimitiveCollection.update (http://<IP_ADDRESS>:8000/static/dist/npm.cesium-01ff433966601611e5b8.js:245299:19)`

From the screenshot, it looks like a conversion from Cartesian to Cartographic is being performed but the input to the function is not Cartesian. Could you post the code snippet that is giving the error?

I'm closing this issue due to inactivity. If you believe this is still an issue, please feel free to re-open. Thanks!


A collaborator on a mirror repository can push changes

A collaborator on a mirror repository can push changes. Mirror repositories should have no write actions.
I also think issues should not be enabled for mirror repositories?
An owner can't push to a mirror repository, but get's an authentication failed error instead of something informative.

Fixed by https://github.com/gogits/gogs/pull/958


Refactor env

Added:

configurations for apps withe default values

Fixed:

Broken tests

Removed:

env variables from apps

NOTE!: couple of env variables still exist in ourvoice-api for database urls - needed for Prisma.

Hi @aarepuu can you have a look at Conflicts first? to resolve them before merging.


Email '' is invalid.

Hello
var user = new ApplicationUser { UserName = Input.Email, Email = Input.Email };
var result = await _userManager.CreateAsync(user, Input.Password);
always return "Email '' is invalid." error.
if i use opt.User.RequireUniqueEmail = false; its passes but i want to use unique emails.
What i am missing to do?
Thanks

@tugkan84 Strange it works well for me. Have you checked the email format ?

hi @7Kronos. mail is<EMAIL_ADDRESS>

That's weird. And by the way the store does not perform any check on the validity of the mail,
Have you checked inside Mongo if the mail is stored correctly ?

ps: i just tested your email on my website (which obviously runs on my identity system) and runs smooth as silk.
I hope you don't mind, i will delete the fake user asap (maybe the time to fix the issue)

@matteofabbri yes i checked from mongo and also i set NormalizeEmail too.
Username works perfect but Email not.I think only i face that problem so I will manualy control email before createAsync. By the way i can close the issue.
Thank you very much of your responses.

what you mean for "also i set NormalizeEmail too." ?

I want to say I try to set NormalizedEmail field too while working on.


[DOC] On mobile, mention the version in the "This documentation..."

What do you want to do?

[X ] Request a change to existing documentation
[ ] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
On mobile, out-of-date pages (e.g., Trace analytics) display the "This version of the OS doc is no longer maintained" message, but the actual version number is not shown by default (although you can display it by clicking on the Documentation panel at the top).
I'd recommend that that message include the version number (and maybe even the release date), something like this:

This documentation is for version 2.10 (9/2023). For current information, see the 2.12 documentation....

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

Hi Stavros, since there is a way to get the version number (clicking the Documentation link at the top), I don't see this as an issue. But let me check to see if there is an easy way to pull in the version, for example, by adding a variable.

@AMoo-Miki - Do you have any thoughts on this? Would it be straight forward to add a variable here?
https://github.com/opensearch-project/documentation-website/blob/9a6bb8a426bb0b1f9f4596e3235e4682ed11bc5f/_layouts/default.html#L170.
Thanks!

Showing the latest version will not be easy at all but we could at least show the current version that the user is viewing:
This version of the OpenSearch documentation, {{site.opensearch_major_minor_version}}, is no longer maintained ...

This will show:
This version of the OpenSearch documentation, 2.13, is no longer maintained ...

Nice improvement!

Awesome, thanks for implementing, @kolchfa-aws !


Add a NFT Preview Card

What would you like to share?
I want to add the NFT preview card that I did to practice my HTML and CSS skills. Please assign me this issue, I am a GSSoC'22 participant.
I am adding some screenshots of it.

Additional information
No response

If you can change the Theme and add animation to it then we can assign this issue

Done with the recommended changes:-
https://user-images.githubusercontent.com/75005433/159506876-26728c17-46ca-49d7-8cf6-3feb43f574b3.mp4

Hey @Abirpal202049 Done with the changes:-
https://user-images.githubusercontent.com/75005433/159507679-7ec1f472-e29f-4c0e-8c57-a9c5c2ba98ad.mp4

Can I make a PR of this ?


fix: Method paged automatic alternative

This is an alternative to pull request #9 which gives the same functionality but the default behaviour remains the same, as record_list_key by default is 'auto', and it has to be set to None explicitly if you want to get whole pages back.
I am mostly indifferent about which approach is taken, as long as I can actually get the full pages...

Look here for why this was closed.


Passwords

Description of the new feature / enhancement
Password for Always on top or Peek
Scenario when this would be used?
Add more privacy for Peek and Add like a screen lock to Always On Top
Supporting information
I lend my PC to my son with always on top so he can watch movie but he kept turn it off and mess up my document, password protect this and ... OK

How exactly would locking Peek add more privacy? If you can start Peek you can also open the file, right?
And for your son you might use Kiosk Mode (In Windows 11 Home or Windows 10 Pro): https://learn.microsoft.com/en-us/windows/configuration/kiosk-single-app#local . This locks your PC to one app only.

/needinfo


New user: omercelik

The check fails again. Here is the related part from README:
Create a new public repository called "my-links". (You can also fork this) This repository should contain two files:
page.json, which contains the content of your page.
[Optional] custom.css, which allows you to customize the look of your page.


Establish domain name and web host

FYI, I use dreamhost.com as my web hosting service.

Now with Heroku, we don't need this capability for quite a while.

Transferred to PCyl-Web issue #27.  Closing.


Fix 'examples' and their warnings

Some typos and depreacation warnings addressed.

hmm, let's ping @phlmn ;)


Fix issues #3 and #4

Check for the existence of a field to prevent accidentally adding an empty fieldref to events
where the fields directive is used.
Use a local variable instead of the instance variable to allow dynamic fields to be properly assessed.
fixes #3
fixes #4

@untergeek really minor comments address them and merge! :D
New tests seem to cover the described problems and they run locally.


colorspace patches break functionality

I think the patches in colorspace-patches-tmp-ltx.sty break much of the functionality of colorspace. Here's an example.
\DocumentMetadata
  {
    lang=en-US,
    pdfversion=2.0,
    pdfstandard=ua-2,
%    testphase={phase-III,title,math,table,firstaid}
  }
\documentclass{article}
\usepackage{colorspace}
\usepackage{kantlipsum}

\definespotcolor{foo}{BarTone 555 GN}{.8,.2,.5,.3}
\definespotcolor{registration}{All}{1,1,1,1}
\definecolorspace{fooshaded}{mixed}{foo,black}
\definecolor{darkfoo}{fooshaded}{.6,.3}

\begin{document}

text

\textcolor{red}{text}

\textcolor{foo}{text}

\textcolor{foo!50}{text}

\textcolor{registration}{text}

{\color[fooshaded]{.6,.3} text}

\textcolor{darkfoo}{text}

{\color{darkfoo}\kant[1-6]}

\newpage

{\color{foo}\kant[1-6]}
\end{document}

Without \DocumentMetadata{}, everything is as expected. With it, several of the colors are either wrong or don't appear at all. Also, odd things happen over pagebreaks. With {\color{darkfoo}\kant[1-6]} all the text appears but the color is wrong on the first page. With {\color{foo}\kant[1-6]} only the text on the second page appears.

Oh well, nice finding ;-). The patches are okay, but it would be better to apply them at the begin of the document and not only on the last page ;-(. Btw: if tikz or pgf are loaded it works as then the resources are added to all pages.
I will transfer the issue to the pdfresources.


Gene viz exon coverage

Update gene-viz exon coverage warning glyph on coverage threshold change.  Fixed bug where gene-viz was displaying warning glyph values for proband on otherTracks

quarantest build successful. Demo link at
http://71ede105.quarantest.iobio.io

@tonydisera @anderspitman I'm seeing some weird behavior when testing this on quarentest.  When the gene-viz is rendered, it is not always properly updated. I'm seeing these console errors when testing only inside quarentest, but everything looks normal when testing locally.  It looks like quarentest is struggling to decompress the cache.  I would recommend doing a local install to test this PR.  Let me know if you have any questions or run into any issues testing locally!

Hi Will.  This functionality is fixed!  Thank you.   One little thing is that it would be good to refresh the current gene when the new coverage cutoffs are applied.  That way the glyphs on the current gene would refresh without the user having to click it again.  Do you want me to submit a new issue?  I'll mark this pull request as approved and you can decide if you want to keep it open.  Thank you! - Tony

@WilliamRichards2017 now that this is merged can you check staging and verify you're no longer getting that error? They're might be additional differences in the way the quarantest server is hosting the files.


Fix error handling for uploading an invalid file for "Upload icon"

Here's what currently happens if you upload a .py file as the organization icon in organization settings:

@timabbott Instead Shall we show them below the  "Organization avatar"

@zulipbot  claim.

That, or under "Upload new icon"; not sure which will look better.


CLI entry point and download step testing during CI

The goal of this PR is to enable CI testing of the download step (other steps to follow). The main change is the addition of a command line interface (CLI) and a small refactoring of S0A_download_ASDF_MPI.py to allow the CLI to call it. With this change, it's easier to execute the steps by passing arguments on the command line instead of changing the code. E.g.:
usage: noisepy.py download [-h] [--path PATH] --start START --end END
                           [--stations STATIONS] [--channels CHANNELS]
                           [--inc_hours INC_HOURS]

optional arguments:
  -h, --help            show this help message and exit
  --path PATH           Directory for downloading files
  --start START         Start date in the format: %Y_%m_%d_%H_%M_%S
  --end END             End date in the format: %Y_%m_%d_%H_%M_%S
  --stations STATIONS   Comma separated list of stations or '*' (default)
  --channels CHANNELS   Comma separated list of channels
  --inc_hours INC_HOURS
                        Time increment size (hrs)

Currently I only made configurable the parameters needed to test the download, but others can be added too.

I think you might still need to specify at least "BH" since there are also other channels like EHZ, SLN. Actually, a station may have tens of channels.

I removed the argument to the CLI, which will use the default. I.e. default="BHE,BHN,BHZ". Does that work?

yes, sounds like default="BHE,BHN,BHZ" would be better.

yes, sounds like default="BHE,BHN,BHZ" would be better. After this commit, this PR should be considered ready for merge? @carlosgjs

Yes, it's ready now. The default was already in place (see noisepy.py:35), so by removing the --channels argument in test.yaml that's what it will use.


grepable output?

While colours are pretty, I can't grep them.  Is there an option, or will there be an option to produce an output that's easier to parse for errors on a large set of buckets?

Hey @craighurley, the colors should only show up for interactive sessions. If you pipe it to grep or write it to a file, there should be no colors. Let me know if you're seeing something different.

Sorry, I should have added more detail.  I would be nice if there were an indication of pass/fail in the outputted text.  While colours are pretty, they are of no use to me or grep.

Ah, I see. We could probably add ✔ and ✘ to each row.

That would work.  The downside to using those particular characters or similar is that they are not easily typed in a terminal.  Old school simple usually works best.


document RegistryAuthSupplier in the user manual

forgot to do this in #759 and #762

Codecov Report

Merging #781 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master    #781   +/-   ##
========================================
  Coverage      65.9%   65.9%
- Complexity      697     698    +1
========================================
  Files           158     158
  Lines          3021    3021
  Branches        346     346
========================================
  Hits           1991    1991
  Misses          876     876
  Partials        154     154


Storage Manager

This PR starts on refactoring the code such that all the code related to storing and retrieving items from disk is in the same location. It creates a StorageManager that is responsible for reading and writing XML, caching, and keeping track of modified assets. In the future this could be used to more easily change the storage backend to something other than XML files or to implement per-asset locking.

Will create an updated PR shortly.


chore(modules): extract markdownit module

Resolves #392

We need to also update awesome-nuxt / modules.nuxtjs.org

We need to also update awesome-nuxt / modules.nuxtjs.org

We need to also update awesome-nuxt / modules.nuxtjs.org

Yes indeed.
I already purpose a PR to change it for modules.nuxtjs.org
but i will for awesome-nuxt too, it make senses to uniformize all links.

We need to also update awesome-nuxt / modules.nuxtjs.org

Yes indeed.
I already purpose a PR to change it for modules.nuxtjs.org
but i will for awesome-nuxt too, it make senses to uniformize all links.

Here is the PR for awesome-nuxt

Here is the PR for awesome-nuxt


Bundle analyzer static reporting

Allows us to publish this somewhere static.
Options:

~cardigan~
[x] dash.wc.org

TODO

[x] Put into circle build

@wellcometrust/experience-dev out of WIP
https://dash.wellcomecollection.org/bundles/browser.latest.html


Execute statement with variable number of parameters?

How do I execute statements with a variable number of parameters? Let's say that the statement is:
"INSERT INTO TableName(ColumnA, ColumnB, ColumnC) VALUES (?1, ?2, ?3)"
But TableName, Columns, and number of columns are not known at compile time. Is there a way of coercing an iterator over a collection of strings into a &[&ToSql] type?

Hi @SolraBizna , this does not seem to work:
error[E0308]: mismatched types   --> src/load/mod.rs:61:34    | 61 |     conn.execute(&schema.insert, fields.as_slice())?; // THIS LINE FAILS    |                                  ^^^^^^^^^^^^^^^^^ expected trait load::rusqlite::types::ToSql, found str    |    = note: expected type '&[&load::rusqlite::types::ToSql]'               found type '&[&str]'
Here is my source:
  for record in rdr.records() {     let row = record?;     println!("{}", schema.insert);     let fields: Vec<&str> = row.iter().collect();     println!("            {:?}", fields);     conn.execute(&schema.insert, fields.as_slice())?; // THIS LINE FAILS   }

Not related to rusqlite but to Rust :
use std::fmt::Debug;
fn test(values: &[&Debug]) {
    println!("{:?}", values);
}
fn main() {
    let fields = vec!["field1", "field2"];
    test(fields.as_slice()); // THIS LINE FAILS
}

And I don't know the correct/idiomatic way to cast a &[&str] into a &[&Debug].

I suspect it is impossible, since the Rust compiler cannot determine the correct memory allocation at compile time.

This works:
use std::fmt::Debug;
fn test<T: Debug + ?Sized>(values: &[&T]) {
    println!("{:?}", values);
}
fn main() {
    let fields = vec!["field1", "field2"];
    test(fields.as_slice()); // THIS LINE FAILS
}

But I am not sure that we should apply this change wherever &[&ToSql] is used !

Hi, I'm just dropping by to say that I've also run into this problem, and as a work-around I'm just directly putting escaped values in SQL statements.
https://gitlab.com/zetok/ods2sql/blob/3871473fa88cfc274c15724e91cdf2ace9fa55f6/src/main.rs#L255
It only "works" because I'm dealing with text data, but it would be a deal breaker if one was to try to work with binary data.

https://github.com/sfackler/rust-postgres/issues/265
https://github.com/rust-lang/rust/issues/42499

The problem in your case is that there's no way to convert &[&T] to &[&Trait] without an allocation. Maybe your api should be generic or take an iterator?

rusqlite 0.15 released

What about for named parameters?


Increased Marker coverage

Signed-off-by: ahcorde<EMAIL_ADDRESS>🎉 New feature
Summary
Checklist

[x] Signed all commits for DCO
[x] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[x] codecheck passed (See contributing)
[x] All tests passed (See test coverage)
[x] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

oh some time ago I added more tests for this class but targeted at ign-rendering6, https://github.com/gazebosim/gz-rendering/pull/673. The changes look good here though. We'll just to make sure we combine these checks when merging forward.
FYI, there are other tests that got merged in fortress but not backported to citadel: #671, #670, #668


Difficulty with ingesting large files

I'm trying to ingest a 100+GB file of legal data into a Kernel Memory service. The data I would like to access are the "opinions" files from this link (https://com-courtlistener-storage.s3-us-west-2.amazonaws.com/list.html?prefix=bulk-data/). They are zipped .bz2 files.
To ingest the data, I use azcopy to get a file into a container. Then, I have a function which triggers on file ingestion in this container. The function unzips the .bz2 file and sends it to Kernel Memory for ingestion in the form of a stream. The zipped file is about 30GB, when I unzip it the size becomes 100+GB.
This is the error message I get when I try to ingest the files into Kernel Memory:

The repository to repro the issue is here: https://github.com/Gpadh/KMFileIngestion/tree/master
Please let me know if I can provide any more details to help.

Handling a file of over 100GB presents too many challenges, including network transfer limits, memory management constraints, VM capacity, and potential timeouts during processing.
To mitigate these issues, I recommend partitioning the data into smaller chunks, ideally between 10-20MB.
This approach will help reducing the likelihood of encountering errors related to memory allocation or network interruptions and make the ingestion process more manageable.


Uncaught ReferenceError: loadBcf is not defined

Hi all,
As the tile says, when running the example I'm getting:
Uncaught ReferenceError: loadBcf is not defined
    at main.js:58285
    at main.js:58313

I'm running on Opera but I don't think this the problem because it works fine when I'm running the online one. Any ideas ?

Hey, can you provide us with the code to take a look?

const bcfInputElement = document.createElement('input');
bcfInputElement.setAttribute('type', 'file');
bcfInputElement.classList.add('hidden');
bcfInputElement.addEventListener('change', loadBcf, false); <-- error thrown here
document.body.appendChild(bcfInputElement);

This causes the side menu to not appear, thus preventing me from importing ifc files in the view. Am i missing some resources ? I ran  npm run init-repo and npm / yarn install in all folders before running the server

I have just realized that the bcp importer / exporter is not implemented in the vanilla JS example. If you comment those lines, you should have it working. We will implement it asap!

Just tried it and it works perfectly, thanks !
Asking just for information, is it possible to display all elements and view their properties directly in the web-ifc view ?

The IFC is well loaded but it seems I can't really select the different elements composing the IFC.
I get this error after loading the IFC:
DevTools failed to load source map: Could not load content for http://<IP_ADDRESS>:5000/build/index.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

Maybe it's related ?

Ok I fixed the error but still not able to select elements, did I missed something ? I'm loading the IFC example file "IFC Schependomlaan.ifc"

We will push a new version these days. Once that happens, this should get solved!

Nice thanks for the info !


Application Freezes When Exporting

Description
When clicking on export, the export assistant opens but immediately closes. After this, the program freezes, and it is necessary to close it from the processes. This occurs with the Ubuntu 22.04.4 LTS operating system in DBeaver Community Edition Version <IP_ADDRESS>407071610.
DBeaver Version
<IP_ADDRESS>407071610
Operating System
Ubuntu 22.04.4 LTS
Database and driver
jdbc:mysql
Grabación de pantalla desde 15-07-24 19:11:49.webm
Steps to reproduce
No response
Additional context
No response

We would kindly ask you to reproduce the issue once again. After you reproduce the issue, please send us the DBeaver log files.
The log files are generated automatically and called .log and .dbeaver-debug.log exactly. Here is our wiki page on this matter: dbeaver.com/docs/wiki/Log-files/#log-files

I'm having the same issue, but I'm on a MacBook Pro M2 Pro running Sonoma 14.5. DBeaver version is <IP_ADDRESS>407071610. I was not having this problem with the previous version. I believe I updated last week.

FYI, I went back to the previous version (<IP_ADDRESS>406231636) and exporting is back working as expected.

@reger, could you send the log files? You can find instructions here https://dbeaver.com/docs/wiki/Log-files/.
Unfortunately, for now we can't reproduce the issue.

I'm facing the same issue too. Here are my log files
dbeaver-debug.log
hs_err_pid36678.log

@reger, could you send the log files? You can find instructions here https://dbeaver.com/docs/wiki/Log-files/. Unfortunately, for now we can't reproduce the issue.

I'll try to find time to update to the broken version again and get logs. I'm in the middle of something on my project where I need a working version of DBeaver right now.

@k4rl0sA @saroshmk
We made some changes that might fix the issue. However, we can't reproduce the issue to check, if it helps.
Could you try early access version and let me know about the results? You can download it here https://dbeaver.io/files/ea/

If the freezing issue has already been resolved, thank you very much.

@E1izabeth this seems to be fixed in Version <IP_ADDRESS>407211303, at least for me.

Thank you!


Drop .NET Standard 2.0 Target

Is there an existing issue for this?

[X] I have searched the existing issues

Task description
See #1040 for context. Given the performance penalty for using the netstandard2.0 target, and lack of currently-supported .NET implementations that support it but are not otherwise covered by our other targets, we should drop the netstandard2.0 target. This can be done independently of dropping netstandard2.1, which might remain around for Unity support.
Any libraries that depend on Lucene.NET via netstandard2.0 are encouraged to target net462 and net8.0 (at this time) for better performance. .NET Standard 2.0 lacks performance-optimized APIs and thus causes a performance penalty compared to other targets if you use Lucene.NET in this way.

I have this change ready to PR, as soon as #1052 is merged.

I am curious to what performance penalty a target that simply has no implementation has?.
Remember, this is just a contract target, .netstandard 2.0 is not an implementation.
The .netstandard 2.0 target greatly simplifies things for framework developers that develops around lucene.
Before we "Claim" any performance penalty, could we please prove those?

The .netstandard 2.0 target greatly simplifies things for framework developers that develops around lucene.

By "framework developers" do you mean developers of frameworks-as-libraries that depend on Lucene.NET, or ".NET Framework" developers? I suppose both apply, although note that we are still going to have our net462 build for .NET Framework users.
I'll let @NightOwl888 speak to the performance, since he mentioned it at #1040. One challenge with having to claim a performance penalty is because of the difficulty of actually using the netstandard2.0 target directly. Any .NET Framework version is going to prefer our net462 build over netstandard2.0, and any out-of-support .NET (Core) 3.0-7 is going to prefer our netstandard2.1 build (and then of course, .NET 8+ would use our net8.0 build). I suppose we could create some benchmarks that transitively depend on us through a netstandard2.0 library to force that, which would emulate some real-world transitive scenarios that could cause this.
In either case, after thinking through it more, I do think we can reconsider this for post-4.8. One scenario is that users may be consolidating their shared logic that uses Lucene.NET into a netstandard2.0 class library to i.e. ease a transition to modern .NET from .NET Framework, which was common practice several years ago in the early days of modern .NET, even though they would likely be better served today by multi-targeting instead (or, better yet, finishing the transition to modern .NET).

By "framework developers" do you mean developers of frameworks-as-libraries that depend on Lucene.NET, or ".NET Framework" developers? I suppose both apply, although note that we are still going to have our net462 build for .NET Framework users.

This only concerts developers that creates frameworks around Lucene, who wishes to target both a .NET 4.X and .NET 8+ Audience in a convinient way (To begin with). And to this date, using .netstandard 2.0 is still a thing to bridge the gap between .NET Framwork and .NET 8+ because it's still far from all tha has moved over. It's not something that was done years ago, it still happens because big businesses move slow or big solutions are not cheap to migrate but eventually I think teams does have plans to do so (I know we are still stuck on .NET 4.8 on projects and actively preparing hundred thounsand lines of code for the move, and .NET Standard is very usefull in that process.
Interestingly enough, Taken from one .NET Framework 4.8 Web application we have going, which targets a package that is developed against .netstandard 2.0 that uses Lucene, the target keeps the package in the middle easy to develop and allows it to be used from both .NET Framework AND .NET 8+. It's however not the .netstandard 2.0 version of lucene that ends up in the final build. So the package in the middle gains the convinience here but for .NET Framwork does not suffer any penalties (If there is any). I am not sure if the same thing would happen for .NET 8+ but it's an interesting observation.
Skimming compiler flags etc, I am having a very hard time figuring out what the differences is between the .NET 462 and .NET Standard 2.0 Build, And therefor where the performance penalty between the two are.

I'll let @NightOwl888 chime in on this one, but for now I think there's clear enough justification to punt on this regardless of performance. Moving to the Future milestone, but keeping open for discussion and to indicate that we do hope to drop it someday in a future version of Lucene.NET.
The idea of dropping the net462 target while keeping netstandard2.0 is an interesting one that I think is worth consideration as well. That would let us just run tests on .NET Framework once for the netstandard2.0 build.

Before we "Claim" any performance penalty, could we please prove those?

To qualify this, I am referring to the original conversation when we were talking about removing netstandard2.1.
First of all, netstandard2.0 shipped before there was a GetEnumerator() or AddOrUpdate() method on ConditionalWeakTable<TKey, TValue>. For GetEnumerator() we worked around by using Prism weak events (which we recently added to the Support namespace)  and for AddOrUpdate(), we are using a Remove() followed by Add(). During experimentation, it was clear that using WeakReference (which is how the Prism weak events are implemented) holds onto references longer than using purely a ConditionalWeakTable<TKey, TValue>. However, there is a WeakEventManager (from WPF) that exists only on .NET Framework that would probably perform better that uses another ConditionalWeakTable<TKey, TValue> along with some native code under the hood. The Prism weak events solution we have is the best we can do for netstandard2.0 without dropping to native code. Remove() followed by Add() is also less efficient than AddOrUpdate().
Note that the netstandard2.1 target primarily exists because of the missing APIs on ConditionalWeakTable<TKey, TValue>.
Secondly, and more importantly, when the netstandard2.0 target is chosen, all of its dependencies can only target netstandard2.0 or lower. If the runtime is net8.0 or net9.0 and Lucene.Net is netstandard2.0, it will no longer call the hardware intrinsics APIs that didn't exist until net6.0 because it will load System.Memory and J2N assemblies that target netstandard2.0. System.Memory and J2N both use hardware intrinsics only if the target is .NET Core. And this goes well beyond those two dependencies.
As for the difference between net462 and netstandard2.0, the performance advantage is not as significant in that case. Although, there are still a few optimizations with having a native runtime target over a .NET Standard target.
Do I think that we should drop netstandard2.0? Not at this time. But I think we should consider doing it before we drop netstandard2.1 because of the missing APIs on ConditionalWeakTable<TKey, TValue>. However, as long as Microsoft is still targeting netstandard2.0 it is a strong indicator that we should be, as well.
That being said, I think we should actively discourage anyone from using netstandard2.0 as a way to target both .NET Framework and .NET Core, because doing so loses several of the performance advantages of using .NET Core (at least for our class libraries and any class libraries we depend on). That is, unless you are swapping in the .NET Core assembly into the final build (although, there may be some minor API differences where you could get burned by doing that).

Secondly, and more importantly, when the netstandard2.0 target is chosen, all of its dependencies can only target netstandard2.0 or lower. If the runtime is net8.0 or net9.0 and Lucene.Net is netstandard2.0, it will no longer call the hardware intrinsics APIs that didn't exist until net6.0 because it will load System.Memory and J2N assemblies that target netstandard2.0. System.Memory and J2N both use hardware intrinsics only if the target is .NET Core. And this goes well beyond those two dependencies.

Please lets keep the talk about netstandard2.0 vs

As for the difference between net462 and netstandard2.0, the performance advantage is not as significant in that case. Although, there are still a few optimizations with having a native runtime target over a .NET Standard target.
Do I think that we should drop netstandard2.0? Not at this time. But I think we should consider doing it before we drop netstandard2.1 because of the missing APIs on ConditionalWeakTable<TKey, TValue>. However, as long as Microsoft is still targeting netstandard2.0 it is a strong indicator that we should be, as well.
That being said, I think we should actively discourage anyone from using netstandard2.0 as a way to target both .NET Framework and .NET Core, because doing so loses several of the performance advantages of using .NET Core (at least for our class libraries and any class libraries we depend on). That is, unless you are swapping in the .NET Core assembly into the final build (although, there may be some minor API differences where you could get burned by doing that).

No, this is not what happens. At least not in my testing. And I have teste both a .NET 8 and .NET 4.8 scenario.
Given I have a .NET 8 project that references a .NET Standard 2.0 Project or Package that references Lucene, I DON'T get the Lucene .NET Standard 2.0 image/dll, I get the one from .NET 8.0.
Given I have a .NET 4.8 project that references a .NET Standard 2.0 Project or Package that references Lucene, I DON'T get the Lucene .NET Standard 2.0 image/dll, I get the one from .NET 4.6.2.

I also did binary comparisons.
Yes, I WON'T say that I am not a little surprised my self >.<... But... Try it out your self.
Now

Okay, that is a bit puzzling.
If you have a completely different API that is conditionally compiled for netstandard2.0 vs net462, that would certainly break if it were the case.
public class SomeClass
{
#if NETSTANDARD2_0
    public static void SomeMethod()
    {
    }
#else
    public static void SomeMethod2()
    {
    }
#endif
}

If your ClassLibrary1 project targeting netstandard2.0 called a multi-targeted assembly with this class in it, does your call to SomeMethod() inside of ClassLibrary1 break?

Okay, that is a bit puzzling.
If you have a completely different API that is conditionally compiled for netstandard2.0 vs net462, that would certainly break if it were the case.
public class SomeClass
{
#if NETSTANDARD2_0
    public static void SomeMethod()
    {
    }
#else
    public static void SomeMethod2()
    {
    }
#endif
}

If your ClassLibrary1 project targeting netstandard2.0 called a multi-targeted assembly with this class in it, does your call to SomeMethod() inside of ClassLibrary1 break?

Yes, that was what I was refering to when I said you could certainly be malicious here. It could also happen unintentionally.
But if you think about the intention of NET Standard, and stick with that intention, the output targeting NET Standard SHOULD be the common subset that is shared between you NET 8 and NET 462 output, it should not add ADDITIONAL stuff.


chore: bdd-spring-1572628493 to 0.0.1

chore: Promote bdd-spring-1572628493 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Update matching to support tasklist isolation

What changed?
Update matching to support tasklist isolation

For domain with tasklist isolation enabled, tasks are only assigned to specific pollers from one isolation group which is calculated from partition config by using a partitioner library

Why?
To support worker isolation

How did you test it?
new test cases

Potential risks
If the feature is enabled, losing pollers from one isolation group can block the task processing of other isolation groups

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 01880bc3-4f85-4565-b207-0393b9c22f51

189 of 217 (87.1%)  changed or added relevant lines in 9 files are covered.
140 unchanged lines in 14 files lost coverage.
Overall coverage increased (+0.01%) to 57.353%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

service/matching/config.go
15
19
78.95%

service/matching/taskListManager.go
66
72
91.67%

service/matching/matcher.go
39
46
84.78%

service/matching/taskReader.go
29
40
72.5%

Files with Coverage Reduction
New Missed Lines
%

common/task/fifoTaskScheduler.go
2
85.57%

service/history/execution/mutable_state_util.go
2
35.95%

service/history/task/transfer_standby_task_executor.go
2
87.34%

common/persistence/nosql/nosqlplugin/cassandra/workflow.go
3
59.1%

common/persistence/statsComputer.go
3
94.64%

common/persistence/serialization/parser.go
4
63.91%

common/persistence/serialization/thrift_decoder.go
4
57.14%

service/history/task/fetcher.go
4
91.24%

common/persistence/nosql/nosqlplugin/cassandra/workflowUtils.go
8
74.32%

common/persistence/sql/workflowStateMaps.go
12
83.62%

Totals

Change from base Build 01880b9e-bbf9-49c4-a995-9ff42bca048d:
0.01%

Covered Lines:
86801

Relevant Lines:
151345

💛  - Coveralls


Fix quick-repo-deletion not aborting on Firefox

Fixes #4599
Test URLs
A fork you own or an empty repo with no stars
Screenshot
https://user-images.githubusercontent.com/46634000/128853508-fdde8f28-4786-465f-ac45-6f71d6178b5e.mp4
Turns out the z-index was not the problem, rather it was the controller that wasn't aborted.
Tested on Firefox only

Can we also just change it to a global click handler as I suggested in the issue? This should just never happen even if in the future z-index is the issue.

Can we also just change it to a global click handler as I suggested in the issue?

:+1:

because in the #4599’s screenshot it definitely is.

No, it's just what happens when the <details> element is closed but the controller isn't aborted (because the button style isn't reset properly).
https://user-images.githubusercontent.com/46634000/129029657-a0437bbb-9c66-4e88-b049-c1d9eeaeb0e8.mp4

I think we should preserve the previous toggle/abort state sync. The "close on click anywhere" should be on top of that, but also it should be excluded via "if (is not aborted), preventDefault"
In short now I see this problem:

if the user lets it complete, the first click after completion will be ignored, even if they click on the menu
if the overlay is closed in any way other than click (Enter, esc? Whatever closes the detail), the click might not be caught

The code might not end up super clean since we'll end up having several listeners all two-way-linked to an AbortController, but this feature is something we need to take extra care of.

This probably still works better than before. We can publish this in the upcoming version and improve it afterwards.


Not Found for url: https://pypi.org/simple/jarbas-utils/

Everytime I try to install the HiveMind-cli on my Pi 0 W, this happens:
Could not install packages due to an EnvironmentError: 404 Client Error: Not Found for url: https://pypi.org/simple/jarbas-utils/
EDIT:
I replaced all the "jarbas-utils" lines with "ovos-utils", but now I get:
  File "/usr/local/bin/HiveMind-cli", line 10, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.7/dist-packages/cli_satellite/__main__.py", line 59, in main
    args.name, args.access_key, args.crypto_key)
  File "/usr/local/lib/python3.7/dist-packages/cli_satellite/__main__.py", line 18, in connect_to_hivemind
    useragent=useragent)
  File "/usr/local/lib/python3.7/dist-packages/cli_satellite/__init__.py", line 24, in __init__
    super().__init__(*args, **kwargs)
TypeError: __init__() got multiple values for argument 'crypto_key'```

Nevermind, I see the problem. We're way outdated on pypi. Thank you kindly for the report!


[MM-22137] - Make RHS comment dropdown open down by default

Summary
In order to avoid bad UX for the dropdown in post thread, I only added this change when the user is located on the RHS thread.
Ticket Link
Fixes https://mattermost.atlassian.net/browse/MM-22137
Fix v5.21 (March 2020)

I think we need to define better how to handle this as now, on a regular window (maximized on the screenshot but would ha we cut the options on the bottom messages.
can you check with @esethna or @andrewbrown00 how should we solve this one?

True, thank you for spotting this. I guess we can add a vertical height check similar to
            if ((y + height) > (windowHeight - MENU_BOTTOM_MARGIN)) {
                this.setState({openUp: true});
            }

What do you think?

Perhaps we could add a listener to the window object and have it recalculate openUp when the window size changes as well as when the component re-renders?

I found that there was a consistent bug with calculating the ref of the menu position, because the y value was changing based on where the menu was previously rendered, so that was updating the openUp based on incorrect values. By calculating the y position based on the trigger we have a consistent value.

@nevyangelova thanks for digging in on this :smile:
I 5/5 agree we need to detect the view and open the menu in the direction the exposes as much of the menu as we can. Another thing we should consider here is what elevation (z-index) the menus open?
The example below has a reduced app height and the menu open up as I would expect but it opens below the RHS (Message Details) header rather than on top to show more options. Because of the app height and the content in the RHS the user can't scroll the RHS to show more of the menu like they could if more content was present.

I 100% agree that this should be refactored but I think it should be a separate ticket. I looked at the structure of the DOM and tried some in-browser changes to z-index and it looks like the stacking context are complicated because of how the menu is nested. It needs further investigation of the stacking context or introducing a React portal component - https://reactjs.org/docs/portals.html but either solutions would take a significant amount of work and I think its more suitable for a separate ticket. That way @esethna will be aware of whats going on and this fix will be merged on time.

PR Updated

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-4901.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

Test server destroyed


Group by Distance SOP

Distance to:

[ ] Position
[ ] Plane
[ ] Geometry Point
[ ] Geometry Primitive
[ ] Geometry Surface
[ ] Geometry Bounding Box
[ ] Geometry Point Bounding Box
[ ] Geometry Attribute

Waiting for #39

Waiting for #38

Switch doesn't work (expression missed)

Toolbox


运行Nonstationary_Transformer报维度错误

The size of tensor a (25) must match the size of tensor b (24) at non-singleton dimension 1

Hello, thank you for your comment, but could you please provide some more detailed information, such as the name of the script you executed, relevant configurations, and error location?

Hi, we have tried to run the default scripts of Non-stationary Transformer and there is no error. If you are using your own dataset, you should check the hyperparameters such as https://github.com/thuml/Time-Series-Library/blob/main/run.py#L66


[26.x] Pulls

#15583
#15595
#15655
#15747
#15751
#15837
#15865
#15908

/retest

/retest

All have been merged but #15747, which still has open discussion.


files.watcherExclude setting does not work without exact path - with multiple node_modules

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.74.3
OS Version: Windows_NT x64 10.0.19044

Steps to Reproduce:

Connect with microsoft Remote-SSH extension
Using open Folder project.
Project contains multiple node_modules directories with files.
path is relative to project root.

ui/my_app/node_modules/ ( file count: 119,000 )
ui/my_app/server/app/node_modules/ ( file count: 30,000 )
ui/my_app/client/node_modules/ ( file count: 17,000 )

warning message pops up: unable to watch for file changes in this large workspace .
I tried adding to files.watcherExclude in project level settings, all examples:

"/node_modules/": true,
"/node_modules/*/": true,
"**/node_modules/": true,
Reloading window would keep throwing warning.

fix: edit same settings to include each node_modules relative path individually.
reload window, problem fixed, no warning message.

I also verified that there is no links anywhere leading to the node_modules directories.
I cannot include project for reference.
Remote SSH OS info: Linux my-host 5.4.0-1096-gcp #105~18.04.2-Ubuntu SMP Tue Nov 29 11:33:58 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

https://github.com/microsoft/vscode/issues/137872 added support to use glob patterns, so it should be fine now, even with the default settings and nested node_modules folders. Can you verify using insiders?
You can give our preview releases a try from: https://code.visualstudio.com/insiders/

Hi thanks I will give it a try, I think it should be mentioned here docs, which clearly refers to the native linux problem but uses glob in it's solution.
Also looking at the issue you sent, we can see it "merged" a month ago, but it's actually only merged to the insiders build.
I think it's unnecessarily confusing to a newcomer, and should be better signposted.

This is still not working for me with the latest VSCode released today.
Local OS: Windows 11
Remote SSH host OS: centOS 7.5
I'm using a multi-root workspace through the Remote SSH extension. My multi-root workspace contains:

firstDir
secondDir
thirdDir

Where the file tree on disk is:

/home/scratch.tim/repo/rel/firmware/firstDir
/home/scratch.tim/repo/secondDir
/home/scratch.tim/repo/resource/thirdDir

This is a client view into a large perforce depot, so opening .../repo as a workspace is not an option.
I cannot exclude secondDir using any documented glob pattern. I must specify the absolute path to the directory, else I receive the unable to watch for file changes in this large workspace popup.

secondDir
**/secondDir
*/secondDir/
/secondDir/
/secondDir/*/
${workspaceFolder:secondDir}
${workspaceFolder:secondDir}/**
${workspaceFolder:secondDir}/*/**

Am I missing something? All the docs and comments on this thread as well as https://github.com/microsoft/vscode/issues/137872 state that at least one of the above patterns should work.


fix: merging of pipe groups when multiple rules are chained together via pipes

Related to: #975 (and #349)
The problem
In versions of Snakemake up to (and including) v5.26.1, workflows where chained pipe rules get aggregated across their wildcards could be executed successfully. Here's an example.
rule all:
    input: "test.out"

rule a:
    output: pipe("testa.{i}.txt")
    shell: "echo {wildcards.i} > {output}"

rule b:
    input: rules.a.output
    output: pipe("testb.{i}.txt")
    shell: "cat {input} > {output}"

rule c:
    input: expand(rules.b.output, i=range(2))
    output: "test.out"
    shell: "cat {input} > {output}"

However, in v5.27.0 (ie the next version), a change was introduced that led to the following failure.
$ snakemake -j
Building DAG of jobs...
WorkflowError in line 8 of Snakefile:
An output file is marked as pipe, but consuming jobs are part of conflicting groups.

The change in question?
    @property
    def needrun_jobs(self):
        """ Jobs that need to be executed. """
-        for job in filter(
-            self.needrun,
-            self.bfs(self.dependencies, *self.targetjobs, stop=self.noneedrun_finished),
-        ):
-            yield job
+        return filterfalse(self.finished, self._needrun)

As a result, the code that handles the grouping of piped jobs in dag.py no longer iterates over jobs in the same order:
https://github.com/snakemake/snakemake/blob/2e2c63a83f2511e5d79885036be1b9f2bf58f4db/snakemake/dag.py#L1164-L1167
It turns out that the order really matters. If the jobs are not sorted topologically, the groups that are created for the jobs from each of rules a and b will not get properly merged. Instead, the jobs will be in separate groups, resulting in a WorkflowError about conflicting groups.
Unfortunately, the error happens somewhat non-deterministically. Since self._needrun is an unordered set(), the jobs it contains might appear in the right order occasionally just by chance.
The proposed solution
This PR revises the handle_pipes() code to force jobs to be processed in BFS order, and thus, resolves #975.
def handle_pipes(self):
    """Use pipes to determine job groups. Check if every pipe has exactly
    one consumer"""
-    for job in self.needrun_jobs:
+    needruns = filterfalse(
+        self.finished,
+        self.bfs(self.dependencies, *self.targetjobs, stop=self.noneedrun_finished),
+    )
+    for job in needruns:

Feel free to let me know if there's a better way to accomplish this. For example, I also considered changing the self._needrun set into some sort of ordered set. But I don't want to break anything, and this seemed like the most straightforward solution.
QC

[x] I created a test case to cover the bug fix. The test is called test_pipes_multiple
[x] Changes to the documentation are not needed in this case. This pull request fixes the code so that it can be consistent with the docs.

Thank you! I have modified this PR a bit, using an approach that does not need the BFS needruns. The reason for avoiding the BFS there was performance.

Thanks Johannes and Arya - this fixed the problem I was having. I can run my workflow without problems in v 6.8.1


removed fixed_string.hpp and using string_literal

@jbbjarnason
I'm cleaning up the codebase and realized we had both string_literal and basic_fixed_string classes that did the same thing. I've replaced the basic_fixed_string with string_literal and deleted basic_fixed_string.hpp. The string_literal is slightly simpler because it is not templated on the char_type, but I think this is fine because everywhere we are using it we are using C++ char array literals.
Let me know if you think there are any downsides to this cleanup or if it will affect your code.

Great cleanup!


C++ version of shap

In README,
"Fast C++ implementations are supported for XGBoost, LightGBM, CatBoost, scikit-learn and pyspark tree models"
Do you reckon the current repo can be translated into a C++ version as well?

Hi @leannejdong, thank you for your interest!
This is an implementation of Shapley values implemented in Python. There are no plans to re-implement in C++. That would best be done as a new project and Github repository, and anyone is free to start such a project. If anyone does so, or knows of an existing project, please leave a comment here!
But since this is not in scope of this project, I am proposing to makr this issue  as closed. CC @slundberg


[DOC] Control over the webUI only works within the ETH network

... at least it seems to be the case, though I don't know whether it's intentional. Might want to rethink this, and at least document it (if it's not already somewhere...)

No. This should definitely not be the case.

Closing as can't reproduce. Please reopen this issue if it still occurs.


TypeError: this.updater.enqueueCallback is not a function

I followed Instruction given by the docs and when I try it using next.js

THIS IS WHAT HAPPENED...

AND WHEN I HOVER IT SECOND TIME IT WORKSSS

I have same problem


How many GIF parcellations are included in the SVT visualisation?

What is the total number of different GIF parcellations supported by our programme? per hemisphere and in total please
e.g. 80 per hemisphere = 160 in total.
I need this to calculate the naive baseline probability of a semiology to localise to a given brain region, as benchmark for summary forrest plots

According to the color table generated by NiftyWeb, of which we have an adaptation in this repo, there are 156 possible structures/parcels/segments (after discarding the first five).
That doesn't mean all are present in the parcellation/segmentation we are using. There is some information about this in my comments in #184.
The parcellation we are using seems to have 137 different structures, discarding the first five as before:
In [1]: import numpy as np

In [2]: import nibabel as nib

In [3]: data = nib.load('slicer/Resources/Image/MNI_152_gif.nii.gz').get_data()

In [4]: len(np.unique(data[data > 16]))
Out[4]: 137

I get different numbers depending on the exact query, but some of these GIF parcellations must be ignored then if we only have 137:
The below gives 146
from mega_analysis import Semiology, Laterality

patient = Semiology('Tonic',
    symptoms_side=Laterality.LEFT,
    dominant_hemisphere=Laterality.LEFT,
    normalise_to_localising_values=False,  # default is False
)

patient.granular = False
patient.top_level_lobes = True
heatmap = patient.get_num_datapoints_dict()

n = 0
for k,v in heatmap.items():
    n += 1
print(n)

Additionally, there are 115 parcellations when I looked at marginal probabilities for each GIF, of which the following are zero:

39
40
41
42
72
73
74

leaving around 108 non-zero


reading vcf files from a local filesystem

Hi,
First, I would like to say thank you for sharing this beautifully design application.
We downloaded the vcf.iobio from github. Everything is work good.
We want to visualize our own vcf files that we produce internally.  Could you instruct me how to go about doing this?  All vcf files are located on a network drive which the server has access to.
Thanks in advance.
Anney

Hi Anney
Just so that I understand your situation. Are you using the main site (http://vcf.iobio.io) or have you installed a local version of vcf.iobio on your own hardware?

Hi Chase,
I installed a local version of vcf.iobio.
thanks,
Aney
On Thu, May 19, 2016 at 6:57 PM, Chase Miller<EMAIL_ADDRESS>wrote:

Hi Anney
Just so that I understand your situation. Are you using the main site (
http://vcf.iobio.io) or have you installed a local version of vcf.iobio
on your own hardware?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/tonydisera/vcf.iobio.io/issues/23#issuecomment-220469694


use sets instead of lists in terraform schema

currently, lists are used in the provider's schema.  any change to the order of the workloads in lists will result in unexpected behavior on the grid.
Instead, sets should be used to uniquely identify workloads not just by their place in a list.

tried it with sets, it gave a weird behavior if for example have a 2 vms and modified one of them if shows that 4vms modified and need to deploy them, so we instead will use nestedMap feature in the new terraform framework, but this requires a lots of modifications to the current provider


User enrolles to course closes #20

currently we can see a button next to courses not enrolled by me.
clicking the button create an enrollment between current user and selected course.

you can check #20 to see the progress

[ ] Build is not passing.
[ ] when enrolling into a course, no status changes, nothing says that I was enrolled and it was successfull
[ ] No link to the course, I'd like to see the course before enrolling into it.


Drastic slowdown of task launches

Dear developers,
I am sorry for bombarding you with questions, but the issue I report here seems to completely block development of my project...
Let me consider the following problem. There is a chain (sequence) of N numbers. Each number, except the first one, is computed as a function of all previous numbers.
I want to store the sequence in a region, and launch a Legion task to compute each number.
Here is how I implement the algorithm:
chain_test.cpp
This program works but suffers from a visible slowdown between task launches as it proceeds along the chain.
By contrast, a similar program based on futures does not take visibly more time between launches for the latter tasks.
chain_futures_test.cpp
Could you explain me what's the reason for things getting slower? Is there a way to circumvent the problem? I guess it has something to do with the growing number of dependencies between tasks.
The chain example I am presenting here is a simplified version of my original two-dimensional problem.
In that program I have quadratic growth of read-only dependencies between tasks, which literary makes execution stop at some point.
Thanks in advance!

You are absolutely correct that the problem is stemming from the growing cost of the dependence analysis between tasks.  If the data being passed is actually individual numbers, futures are actually the best way to go.  Data should starting getting put into regions probably somewhere are the 100s to 1Ks+ of elements depending on the granularity of your tasks and the size of the data.  Legion's dependence analysis is really optimized for cases with coarse grain tasks and large chunks of data being stored in logical regions and subregions.  Let us know if you continue to see strange behavior and we'll try to explain it/fix it.

Many thanks!
I checked your suggestion to use futures, and it was much faster indeed. Now I know how to move on.

If the data being passed is actually individual numbers, futures are actually the best way to go.

Each data point is a structure with 10-20 numeric fields. Does this make much difference?

Futures on the order of a few hundred bytes seems reasonable in size to me.  When they start reaching ~10-100KB is probably when you want to start moving the data into a logical region.  The cross-over point will be depend on the granularity of your tasks and how expensive they are for the runtime to analyze.


update envoy 05102020

Description: brings in an envoy update. Relevant commits:

https://github.com/envoyproxy/envoy/pull/11127 which uses the construct on first use idiom for certain static variables in the histogram code which were causing #688.
Risk Level: low
Testing: fixed local repro of the crash.

Fixes #688
Signed-off-by: Jose Nino<EMAIL_ADDRESS>

I am going to merge this even if android CI is not working. The emulator script is not working, but I verified locally. I have opened https://github.com/lyft/envoy-mobile/issues/841 to fix today


Compilation error on windows (missing libraries)

On Windows 10 with Codeblocks and compiler MinGW-W64-builds-4.3.5, the compilation fails because of two missing libraries in distinct files. To fix this issue, I had to add
#include
in voxel.h
and
#include
in model_filereading.cpp

Fixed by your changes.


App not generating ICNS files in MacOS 15

I realize that MacOS 15 isn't officially supported, but I'm just making the note to share my experience. I was able to download and then install the app after opening the System Settings > Privacy & Security and opening the app through there. I opened a PNG image that loaded up correctly and tried to use the Generate .icns feature, but it doesn't create the files. The original file is in a subfolder of my home directory, so I have read/write access.

Thanks @indros for the feedback.
There is a problem with file save dialog. The generated files are saved to the source image directory. I will fix it asap.
You can clone the repo and compile the app by yourself. There are instructions for that. For now I do not think to update my system to mac OS 15.
Is your Mac M1-2 or Intel-based, btw?

I'm using the app on Mac OS 15 on an M1 Macbook Pro.
On Wed, Oct 2, 2024 at 1:04 AM alp tuğan @.***> wrote:

Thanks @indros https://github.com/indros for the feedback.
There is a problem with file save dialog. The generated files are saved to
the source image directory. I will fix it asap.
You can clone the repo and compile the app by yourself. There are
instructions for that. For now I do not think to update my system to mac OS
15.
Is your Mac M1-2 or Intel-based, btw?
—
Reply to this email directly, view it on GitHub
https://github.com/alptugan/icns-creator/issues/8#issuecomment-2387692909,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACCRBB4DZQH7LUAH6RNAJ3ZZOEHXAVCNFSM6AAAAABPDQYDYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBXGY4TEOJQHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Had the same problem on Macos 15, but it worked fine after removing the special symbols (the spaces) in the icon file name.
code solid.svg - failed.
code-solid.svg - success.


Remarks missing entry (not valid in 64-bit MASM)

Directive not valid in 64-bit MASM (ml64.exe).

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

ID: ac9f1ff8-7ca9-6e9e-a1cb-a1dd97bf1a55
Version Independent ID: 3232e1ab-ca00-110d-eefd-e2ca317f67a7
Content: .STACK
Content Source: docs/assembler/masm/dot-stack.md
Product: visual-cpp
Technology: cpp-masm
GitHub Login: @corob-msft
Microsoft Alias: corob

fix should appear in 1-2 days. Thanks @Player1UK !


Convolution with user provided data

This combination of settings doesnt work. Probably just need to check how this is done in the ground_truth case.

This was resolved by fixing how the data was being provided to the system internally.


Revert "update druid console version (#3189)"

This reverts commit 496b801bc39bec26a4084d6332a1da676091a5dd (#3189).
Issue originally reported in https://groups.google.com/d/msg/druid-user/zentMX_6Rh4/o1dBtBfPBAAJ, is reproducible for me (JS console gives errors like "d3 is not defined" and historical nodes don't show up). Rolling back druid-console fixes it for me.
imo, unless there is a reasonable workaround this should go in <IP_ADDRESS>.

👍


Add wallet classes

This is still a WIP but I wanted to get the ball rolling on this! Lots of basic functionality is now here, along with the first few tests and examples. See /examples/wallet.py for some examples of the most basic functionality.
Current capabilities:

[x] Generate keys
[x] Load keys
[x] Query utxos
[x] Send ada
[x] Send specific UTxOs
[x] Get senders of all UTxOs
[x] Get metadata for all held tokens
[x] Get utxo block times and sort utxos
[x] Mint / Burn tokens
[x] Automatically load in token polices where wallet is a signer
[x] Automatically create BlockFrost Chain Context (mainnet, preprod, and preview)
[x] Attach messages to transactions
[x] Sign messages
[x] Add custom metadata fields
[x] Multi-output transactions
[x] Register wallet
[x] Stake wallet
[x] Withdraw rewards
[x] Generate fully manual transactions that can do any / all of the above
[x] Integrate strict type checking
[ ] Write tests
[ ] Add more examples

Future additions (possibly later PRs):

[ ] Draft and sign multi-sig transactions
[ ] Interaction with native scripts
[ ] Interaction with plutus scripts
[ ] Load wallets with mnemonic phrase (integrating HDWallet)

Now currently figuring out how to write tests for the transaction methods, using test_transaction.py for inspiration.

Hi Jerry,
Thanks for the helpful review. I concur with everything suggested and I especially like using the decorator for blockfrost-only contexts. I'll make the changes soon.
And my apologies about the formatting, I often forget 😅
Thanks again!

Codecov Report
Base: 85.81% // Head: 85.73% // Decreases project coverage by -0.08% :warning:

Coverage data is based on head (c30fba1) compared to base (65e67d5).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #89      +/-   ##
==========================================
- Coverage   85.81%   85.73%   -0.09%
==========================================
  Files          22       22
  Lines        2433     2446      +13
  Branches      553      556       +3
==========================================
+ Hits         2088     2097       +9
- Misses        253      256       +3
- Partials       92       93       +1

Impacted Files
Coverage Δ

pycardano/key.py
86.61% <0.00%> (-1.71%)
:arrow_down:

pycardano/txbuilder.py
92.06% <0.00%> (-0.19%)
:arrow_down:

pycardano/backend/base.py
100.00% <0.00%> (ø)

pycardano/backend/blockfrost.py
30.00% <0.00%> (ø)

pycardano/transaction.py
94.23% <0.00%> (+0.01%)
:arrow_up:

pycardano/coinselection.py
91.73% <0.00%> (+0.13%)
:arrow_up:

pycardano/utils.py
94.82% <0.00%> (+0.38%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

In reference to commit c30fba1: @cffls I have the code generate wallet keys using the format:
name.skey
name.vkey
name.stake.skey
name.stake.vkey

This is to make it easy for a wallet to load unique staking keys. Let me know what you think of this format.
Thinking about this more I now realize I should also add kwargs so one can directly specify the path to each for the four keyfiles individually.

The naming looks good to me. Thank you!

Great, thanks! I believe I've addressed all the comments for now. Next step is to write more tests. I'll have to look in details at the ones you've already written for how to properly test functions that are meant to submit transactions to the chain.

Great, thanks! I believe I've addressed all the comments for now. Next step is to write more tests. I'll have to look in detail at the ones you've already written for how to properly test functions that are meant to submit transactions to the chain.

Nice! You can take a look at integration tests, where a local chain will be created through docker compose and you can run a bunch of real transactions on the chain.

FYI, the main branch now enforces stronger type hint in the Github ci/cd pipeline.
I would advise rebasing this branch on top of the latest main branch to ensure the newly added wallet.py module passes all static analyses.

Done! I will work on straightening out the type hints, thank you!

Hey Jarred,
thanks for the big chunk of new features! Looks very promising to me!
However, I'd like to bring one thing up for a discussion...
You are introducing a new class Wallet as part of the public API. I like that because it is abstracting a lot of things which makes it easy to use.
Now here is what caught my eye. For some weeks now we also have a class HDWallet https://github.com/Python-Cardano/pycardano/blob/88894e2cc97a8b01fed9a9fc99f2ff2861beac4b/pycardano/crypto/bip32.py#L78. Without looking into the details I would not understand why do we have Wallet and HDWallet and they don't provide the same / a similar interface.
First of all I am wondering what your thoughts are regarding the two in regards to the user/developer experience.
Secondly, I am wondering if it makes sense to extend the high-level Wallet class to support HDWallet.
Happy to hear what you're going to say :)

Hi @robinboening,
Thanks for pointing out the HDWallet class. I think it would be a really nice idea to integrate into Wallet. I think some might appreciate the option to create a wallet using a mnemonic or having full control over the generation of keys, so I don't think it's out of scope for this PR. I've updated the todo list above to specify the integration of HDWallet. In the end it might come in another PR later but I think it would be really nice to include.

Quick update-- I've finally managed to integrate mypy so that the checks do not fail anymore. In addition I've gotten coverage up to ~44%. Still some tests to write but I'm closing in on this.
🔜

How can I help with this? I can't see the logs for the failed checks as it was too long ago. I am working on a project that would benefit from having the wallet stuff abstracted away into PyCardano.

@KINGH242 that's great! This PR is staled and I completely forget about it.. I think a few type checks are failing. If those are fixed we should be able to merge it.

Hey all, I dropped the ball a bit on this one!
I think I got stuck with test writing-- I recall that I mainly had trouble with the mocking of the blockfrost API and tx submission as it's something I had no experience with.
Also happy to help out wherever possible and finally get this done.

Hey @astrojarred, I added some test and fixed a few things to allow it to work with the latest changes. I submitted a PR here https://github.com/astrojarred/pycardano/pull/33


#1810 Add HL7 Helper Methods to SDK

https://github.com/medplum/medplum/issues/1810

Coverage: 94.286% (+0.01%) from 94.274% when pulling 4b5a28e6bfb7e38166ee052e095339aa4b051464 on james-hl7-methods-to-sdk into 8c4f294e71b326caab3f5119d700620d61369a43 on main.


fixed cookie box

Fixed cookie box
Fixes:  #2060
Description
cookie box was not visible
issue no : - 2060
Type of PR

[ ✅] Bug fix

Screenshots / videos (if applicable)
before fixing the issue
Checklist:

after fixing the issue⤵

[ ✅ ] I have made this change from my own.
-[ ✅  I have taken help from some online resources.
-[ ✅  My code follows the style guidelines of this project.
-[ ✅  I have performed a self-review of my own code.
-[ ✅  I have commented my code, particularly in hard-to-understand areas.
-[ ✅  I have made corresponding changes to the documentation.
[ ✅  My changes generate no new warnings.
-[ ✅ I have tested the changes thoroughly before submitting this pull request.
-[ ✅  I have provided relevant issue numbers and screenshots after making the changes.

It is visible


Latest release is not on crates.io

0.1.3 was released here 4 days ago, but the latest version on crates.io is still 0.1.2.

Also relevant: #13.
We may not want to publish 0.1.3 and instead publish as 0.2.0.

Just published, closing this. Sorry for the delay!


Macro-support workaround breaks IntelliJ plugin

Apparently, the pattern bazel-deps uses to get around ijar+scala macros issue confuses the IntelliJ plugin. The problem is with using "//jar:file".
See the corresponding issue in the intellij plugin: https://github.com/bazelbuild/intellij/issues/142
I'm cross-posting between repos because it's not clear whether this issue should be fixed by bazel-deps, the intellij plugin or maybe even bazel core.
The discussion which points at bazel-deps as a source of problem is here: https://github.com/bazelbuild/intellij/issues/97#issuecomment-310906994

we have to do it this way until the scala rules can support macros in jars. maven_jar will not work.
The solution is in the scala rules to make a scala_jar repository rule which can not use ijar on the output, but give a sane java_provider.

I'll try and expedite the scala_import rule as fast as I can and once it's
in baze_deps will be able o use it
On Wed, 11 Oct 2017 at 21:49 P. Oscar Boykin<EMAIL_ADDRESS>wrote:

we have to do it this way until the scala rules can support macros in
jars. maven_jar will not work.
The solution is in the scala rules to make a scala_jar repository rule
which can not use ijar on the output, but give a sane java_provider.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/johnynek/bazel-deps/issues/81#issuecomment-335910397,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIF6tWh_j8qlr60eUQmyABSKrtnRVFks5srQ2tgaJpZM4P15a7
.

Ittai, Do you have a sense of how much work is left?
Our homegrown aspects that generate intellij project files are subtly broken by recent bazel/rules_scala upgrade and i'm trying to estimate whether i should dive into fixing them

I found a workaround for our internal issues so I'm not on fire anymore but still very interested in getting the official intellij plugin to work.

Excellent. I'll update as soon as I have progress
On Thu, 12 Oct 2017 at 0:57 Grzegorz Kossakowski<EMAIL_ADDRESS>wrote:

I found a workaround for our internal issues so I'm not on fire anymore
but still very interested in getting the official intellij plugin to work.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/johnynek/bazel-deps/issues/81#issuecomment-335960962,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIF_n1oIp6bHKRvML1gOOA1WWsgC3Nks5srTmwgaJpZM4P15a7
.

I believe #101 has fixed this -- scala deps work in intellij for me these days.

reopen if there is an issue.


Number of voxels in phase-encoding direction is not always equal to number of phase-encoding lines on Philips systems

Heya,
I was looking into the code that calculates the effective echo spacing for Philips scans. This uses the number of voxels in the phase-encoding dimension as a proxy for (EPI train length * acceleration factor).
https://github.com/poldracklab/fmriprep/blob/260872273a1f4ef02de2cae20dd7d6948b531c4b/fmriprep/interfaces/fmap.py#L327
However, especially on Philips systems, the "Acquisition matrix size" (corresponding to actual number of k-space lines), and the "Reconstruction matrix size" can sometimes be different, because Philips systems automatically select a reconstruction matrix size that is easy to reconstruct using the fast fourier transform (FFT; powers of 2). This is something we also sometimes do deliberately in our data because it might somewhat alleviate partial voluming.
Would it be an idea to first try to use the "epi_factor"-field (standard in Philips parrecs) to calculate the number of k-space lines before using the nifti dimensions?
(this is also reccomended here:
http://dbic.dartmouth.edu/pipermail/mrusers/attachments/20141112/eb1d20e6/attachment.pdf )

Yeah apparently they do not "trust" this field?
https://github.com/rordenlab/dcm2niix/blob/8fc0c514a7595d4afb8fac09091f5c54ecbf28ee/console/nii_dicom_batch.cpp#L829
In any case, if you have a different reconstruction vs acquisition matrix size, the DICOM will already have a different resolution from what was acquired. This should somehow be encoded in BIDS metadata I would argue.

Hi @Gilles86, would you like to submit a PR from your sketch?

Let's keep discussion on the new issue.


Feature Request: Override Webpage Colorscheme

Is your feature request related to a problem? Please describe.
Before Firefox 100, the browser would automatically paint websites (including settings) in a light or dark theme based on the color of the address bar (white background/black text vs back background/white text). With Firefox 100 however, themes must now be labeled as light or dark in their code, which means even if the browser is set to recognize light/dark mode based on the theme instead of the OS, it will ignore the theme and default to OS if the new label isn't in the code. This means that most themes must be updated with the labels, and themes that are unmaintained will not get the necessary update. Not to mention, most users probably built their themes out of the unmaintained Firefox Color extension, which effectively makes them unmaintained unless the users learned proper coding at a later date.
Describe the solution you'd like
Seeing as this extension is the best alternative to default theming options, I think it would be nice if this extension offered the option to override a theme's labels (or lack there-of) with Light/Dark depending on what time of day they are set for. So, for example, I could set the same theme for both day and night, but if I set "Override Webpage Colorsheme" on both Day and Night, then the extension will enforce Light Webpage Themes by day, Dark Webpage Themes by night, so long as in the browser settings I have Website Appearance set to "browser theme" instead of "System Theme", "Light", or "Dark". This would allow me, and plenty of other users, the freedom to mix and match whatever themes we like without any concern for if they'll be interpreted as light or dark, since the extension will do the interpreting.
Additional context
Thanks again for developing this great extension.

@skhzhang I second this, while I understand this change from Firefox, it will leave a lot of greate legacy themes unsuable as thoses will never be updated.
@MintMain21 Do you know if it's possible to overwrite a theme's label at all ?
Otherwise there is another workaround here, that is to ovewrite layout.css.prefers-color-scheme.content-override to 0 or 1 when changing theme to force them content theme, I tested it and it works, look at this thread https://support.mozilla.org/bm/questions/1365222.

The way this should work is by changing the actual Website Appearance selection directly. I don't think it makes sense to try messing with the data internal to a theme. To be clear, if this change is implemented, I would expect to have two new dropdowns in the addon settings page (analogous to the existing dropdowns) that would have each of these four options from the image below. Then I would expect the selected option in the firefox settings to change automatically according to the time of day. So for example, light could be selected during the day here, and dark during the night:

This is actually what I was looking for when I installed this addon. I tried setting this config to "firefox theme" and using this extension to switch between light and dark firefox themes--only because I wanted to change the webpage appearance. But frankly the light firefox theme looks ridiculous and I can't tolerate it even during full sunshine. So I just flip this switch manually twice a day instead of using the addon. Don't get me started on Dark Reader, its scope is limited. It cannot do the same thing as this firefox setting.

themes must now be labeled as light or dark in their code

If this is how firefox decides the webpage appearance from firefox theme, another way to accomplish what you're looking for would be to simply duplicate the theme you like, having one that announces itself as dark and one that announces itself as light. Then you could use the existing addon to toggle between them, with webpage appearance configured to "firefox theme."


created Aditya0049.md

What type of PR is this? (check all applicable)

[x] 🚀 Aditya Baban Kate
[x] ✨ Feature
[x] 🌟 stared the repo
[x] 🐛 Grammatical Error
[x] 📝 Documentation Update

Description
I’m an Open-Source enthusiast & a junior pursuing my Diploma in Information Technology & Engineering.
👨💻 I am passionate about Kubernetes, Web Dev, Machine Learning, DevOps & I enjoy learning new things.
Add Link of GitHub Profile
https://github.com/Aditya0049

Aditya0049.md Created


Use discard instead of saving unused variable for playspace

Overview
Clearing out old branches and found this commit leftover from some old PRs.
Small change, but there's no point in creating this variable since we don't use it and only need the property call to happen.

/azp run


How to get it working

Firstly, when activating the APP on Homey, I have to add "Access-Control-Allow-Origin" what value do I have to fill in
Then, if when ap enabled, I never get response via the suggested string http://[homey-ip]:[port]/key

You can set Access-Control-Allow-Origin to * to allow requests from every IP.
To receive a response you MUST set a Respond in flows (How-To point 6 and 7)
I've updated the readme:
How to use

Install the app
Set up the app in the settings page and restart it
Create a new flow with the Local API app: remember to add the trigger card
Personalize the flow as you like
End the flow with at least one of the following cards:
Respond with ... (remember to add the JSON response)
Respond with 200
Save the flow and test it with a browser. The URL is http://homey-ip:/endpoint-name

Disclaimer
Don't use this app to expose your Homey to the internet. Its use is intended for local network only.

How should the JSON response lookslike? As (even via telnet) the Homey does not respond.
Sent from Outlook for iOShttps://aka.ms/o0ukef

From: Paolo Dadda @.>
Sent: Wednesday, January 4, 2023 2:13:36 PM
To: ilpaolino/homeylocalapi @.>
Cc: remcovaal @.>; Author @.>
Subject: Re: [ilpaolino/homeylocalapi] How to get it working (Issue #3)
You can set Access-Control-Allow-Origin to * to allow requests from every IP.
To receive a response you MUST set a Respond in flows (How-To point 6 and 7)
I've updated the readme:
How to use

Install the app
Set up the app in the settings page and restart it
Create a new flow with the Local API app: remember to add the trigger card
Personalize the flow as you like
End the flow with at least one of the following cards:
Respond with ... (remember to add the JSON response)
Respond with 200
Save the flow and test it with a browser. The URL is http://homey-ip:/endpoint-name

Disclaimer
Don't use this app to expose your Homey to the internet. Its use is intended for local network only.
—
Reply to this email directly, view it on GitHubhttps://github.com/ilpaolino/homeylocalapi/issues/3#issuecomment-1370915001, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJNUDNHF3K5EZMFHJ7JFTL3WQVZQBANCNFSM6AAAAAATQBXEE4.
You are receiving this because you authored the thread.Message ID: @.***>

See crache reports. Hereby diagnostic ID 609baf60-439d-457e-8555-e6c220c41692
Sent from Outlook for iOShttps://aka.ms/o0ukef

From: Paolo Dadda @.>
Sent: Wednesday, January 4, 2023 2:13:36 PM
To: ilpaolino/homeylocalapi @.>
Cc: remcovaal @.>; Author @.>
Subject: Re: [ilpaolino/homeylocalapi] How to get it working (Issue #3)
You can set Access-Control-Allow-Origin to * to allow requests from every IP.
To receive a response you MUST set a Respond in flows (How-To point 6 and 7)
I've updated the readme:
How to use

Install the app
Set up the app in the settings page and restart it
Create a new flow with the Local API app: remember to add the trigger card
Personalize the flow as you like
End the flow with at least one of the following cards:
Respond with ... (remember to add the JSON response)
Respond with 200
Save the flow and test it with a browser. The URL is http://homey-ip:/endpoint-name

Disclaimer
Don't use this app to expose your Homey to the internet. Its use is intended for local network only.
—
Reply to this email directly, view it on GitHubhttps://github.com/ilpaolino/homeylocalapi/issues/3#issuecomment-1370915001, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJNUDNHF3K5EZMFHJ7JFTL3WQVZQBANCNFSM6AAAAAATQBXEE4.
You are receiving this because you authored the thread.Message ID: @.***>

Can you try to change the server port? (use in example 3300 and restart the app after save settings).
Can you set the flow like the example in this page: https://community.homey.app/t/app-pro-local-api/70840/5
Let me know
Paolo

App still craching
Sent from Outlook for iOShttps://aka.ms/o0ukef

From: Paolo Dadda @.>
Sent: Saturday, January 7, 2023 2:09:38 PM
To: ilpaolino/homeylocalapi @.>
Cc: remcovaal @.>; Author @.>
Subject: Re: [ilpaolino/homeylocalapi] How to get it working (Issue #3)
Can you try to change the server port? (use in example 3300 and restart the app after save settings).
Can you set the flow like the example in this page: https://community.homey.app/t/app-pro-local-api/70840/5
Let me know
Paolo
—
Reply to this email directly, view it on GitHubhttps://github.com/ilpaolino/homeylocalapi/issues/3#issuecomment-1374476446, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJNUDNCDLUM5ZPPMDS3JPKLWRFTJFANCNFSM6AAAAAATQBXEE4.
You are receiving this because you authored the thread.Message ID: @.***>

Are you sure you have changed the port and restart the app?
From homey's server I've got only this error in crash report:
    at emitErrorNT (node:net:1357:8)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  code: 'EACCES',
  errno: -13,
  syscall: 'listen',
  address: '<IP_ADDRESS>',
  port: 188

That error report me you're try using port 188 (which is already occupied by another service).
To restart the app you must go in settings and press "Restart App"

[Image.png]
Sent from Outlook for iOShttps://aka.ms/o0ukef

From: Paolo Dadda @.>
Sent: Sunday, January 8, 2023 7:56:01 PM
To: ilpaolino/homeylocalapi @.>
Cc: remcovaal @.>; Author @.>
Subject: Re: [ilpaolino/homeylocalapi] How to get it working (Issue #3)
Are you sure you have changed the port and restart the app?
From homey's server I've got only this error in crash report:
at emitErrorNT (node:net:1357:8)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {

code: 'EACCES',
errno: -13,
syscall: 'listen',
address: '<IP_ADDRESS>',
port: 188
That error report me you're try using port 188 (which is already occupied by another service).
To restart the app you must go in settings and press "Restart App"
—
Reply to this email directly, view it on GitHubhttps://github.com/ilpaolino/homeylocalapi/issues/3#issuecomment-1374903028, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJNUDNF756LXRXOQRDUGHEDWRMEUDANCNFSM6AAAAAATQBXEE4.
You are receiving this because you authored the thread.Message ID: @.***>

I can't see the attachment here on github, can you post it on the homey support forum? https://community.homey.app/t/app-pro-local-api/70840/5

That attachment was nothing more than a proof Inadjuster the port number
Sent from Outlook for iOShttps://aka.ms/o0ukef

From: Paolo Dadda @.>
Sent: Sunday, January 8, 2023 8:02:58 PM
To: ilpaolino/homeylocalapi @.>
Cc: remcovaal @.>; Author @.>
Subject: Re: [ilpaolino/homeylocalapi] How to get it working (Issue #3)
I can't see the attachment here on github, can you post it on the homey support forum? https://community.homey.app/t/app-pro-local-api/70840/5
—
Reply to this email directly, view it on GitHubhttps://github.com/ilpaolino/homeylocalapi/issues/3#issuecomment-1374904461, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJNUDNAXV2WDENEQC2YFTQDWRMFOFANCNFSM6AAAAAATQBXEE4.
You are receiving this because you authored the thread.Message ID: @.***>

I can only suggest you to uninstall and reinstall the app, because the crash report is related only to the server port.
If you need more support you can write me on the Homey Support forum, in the dedicated thread:
https://community.homey.app/t/app-pro-local-api/70840/5
Paolo


fix: take account of skipcol in screenpos

Fixes #12547

I think this will break other places where plines_m_win() is used. #12625 passes other tests.

Hmm, this also passes tests.

Oh I wasn't aware of that PR.


Add styling for blockquotes

Fixes #13, adding a $focus sidebar to blockquotes. I haven't looked at styling any nested elements.

We have ourselves a 2.01kb bundle :(

Closing in favor of #28 which is based on your styles. Thanks!

Hi, apologies I haven't had time to improve my initial attempt. Like the changes, looks great! Really like this project, I do a lot of quick prototype pages and will definitely be using this in future :-) Cheers!


 And you might want to join stackage so that you will be notified of these issues before your users notice.
Thanks,
Joachim

A merged PR fixed this issue, AFAIK.


c mine

its not farming c mine just atcking goblins
and showning login error

you got banned I guess, the cmine is not only concern.
Diego @.***> 於 2022年4月27日 週三 23:56 寫道：

its not farming c mine just atcking goblins
and showning login error
—
Reply to this email directly, view it on GitHub
https://github.com/hldh214/lok_bot/issues/41, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHMYSMF7SVTH5JNHNAUTOYTVHFPRNANCNFSM5UPTEKXQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


platform: Add GET /transactions/{id} and PATCH /transactions endpoints

PR Checklist
PR Structure

[ ] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[ ] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[ ] This PR's title starts with name of package that is most changed in the PR, ex.
paymentservice.stellar, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.

What
Add GET /transactions/{id} and PATCH /transactions endpoints.
Why
To support SEP-31 MVP flow.
Known limitations
GET /transactions is not implemented.

Reference Server Preview is available here:https://anchor-ref-pr176.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr176.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr176.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr176.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr176.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr176.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr176.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr176.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr176.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr176.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr176.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr176.previews.kube001.services.stellar-ops.com/


private key in logs

thank you for writing and publishing such a nice piece of software :+1:
however, I'd prefer to not see my private keys in the log, or at least not on info-lvl. could you please change this?
2016/09/16 ..:..:.. [INFO][my.host.name] Server responded with a certificate.
time="2016-09-16T...." level=info msg="Got certs={my.host.name https://acme-v01.api.letsencrypt.org/acme/cert/.....  https://acme-v01.api.letsencrypt.org/acme/reg/..... -----BEGIN RSA PRIVATE KEY-----\nMIIEowIBAAKCAQEAu4iFuMTP/YxdVeZBfbrbbAdyvm .......

i'm using version jetstack/kube-lego:0.1.2

Should be fixed by jetstack/kube-lego:0.1.3


Feature to automatically close TF2BD upon TF2 closing

A clear and concise description of what the problem is.

It's be nice to have TF2BD close whenever you exit TF2 as well so you don't have to do it manually each time. Sometimes I forget to close TF2BD after closing TF2 and it causes Steam and Discord Rich Presence to still say I'm playing TF2.

Describe the solution you'd like

Create a feature (as an optional setting) that closes TF2BD upon detecting the game also being closed after having been launched with the tool.

Additional Information

Might be helpful to avoid closing TF2BD upon a game crash and not a manual exit? Though I understand if that's simply not possible because there isn't a way to distinguish; I don't mind if the tool closes even upon a crash, it'd be a very nice QOL improvement either way.

Might be helpful to avoid closing TF2BD upon a game crash and not a manual exit?

It's not impossible, but I just can't be arsed to implement that lol.
like i have to listen to the exit code of tf2 exe and i have to code that for both platforms and yada yada...
For my time and sanity (and less complexity) sake, I've decided that I'll just make the user to just re-launch the application on that, sorry.


[BUG] overflow when ttl is large

The following panics:
#[tokio::test]
async fn large_ttl() {
    let cache: moka::future::Cache<(), ()> = moka::future::CacheBuilder::new(usize::MAX)
        .time_to_live(Duration::MAX)
        .build();
    cache.insert((), ()).await;
    cache.sync();
}

panicked at 'overflow when adding duration to instant',
.cargo/registry/src/github.com-1ecc6299db9ec823/quanta-0.9.3/src/instant.rs:142:14

Is this a good first issues for newcomers? I would like to try an contribute here

@barkanido — Sorry for not getting back to you sooner. Yes. I believe this is a good first issue.
Here are my initial thoughts. If you have better idea, please let me know.
I actually think Moka should panic when a Duration is too big to handle. Moka should not support such a big duration because giving Duration::MAX to time_to_live might be a programming error as it is about 584 billion yeas (doc). I think supporting up to 1,000 years will be far longer than required.
However, I think there some are rooms to improve:

Release build: I have not tried by myself but if you run the above code with --release flag, Moka will not panic but silently overflow. (So the time will wrap from future to past)

I think it should panic in release build too. We could use checked_add instead of + to ensure that overflow will be always detected.

Better panic message: We could make the panic message more informative (e.g. telling panicing is an intended behavior) than the current message: "panicked at 'overflow when adding duration to instant'".
Document panic (optional): It might be good if we mention about panic in the API doc.

Thanks!

sounds reasonable to me.
I now have a passing test:
    #[tokio::test]
    #[should_panic(expected = "overflow when adding duration to instant")]
    async fn ttl_overflow() {
        // https://github.com/moka-rs/moka/issues/52
        let cache:Cache<(),i32> = CacheBuilder::new(usize::MAX)
            .time_to_live(Duration::MAX)
            .build();
        cache.insert((), 42).await;
        cache.sync();
    }

thoughts:

So you think it is better to fail early in the build phase to totally prevent this? Or merely documenting this is a good enough user experience?
Is there a similar cache in the sync cache?

@barkanido — Thanks for working on it.

Do you think it is better to fail early in the build phase to totally prevent this? Or merely documenting this is a good enough user experience?

Yeah. Probably it is better to fail in build phase. e.g. Make CacheBuilder's time_to_live and time_to_idle to panic when the given Duration is longer than 1,000 years.
Then maybe we do not have to use checked_add anymore? Hmm. I am not sure.
I am not sure because Instant is not a real-time clock (wall clock), but a monotonically increasing clock from some unspecified point in the past. I think, on many major platforms including Linux, Instants represent nanoseconds that the system has been running since it was booted. So they will not be very big and will never overflow when adding a Duration <= 1,000 years. But this is not guaranteed on all platforms that Rust might support. So we would better to use checked_add?

however, testing this depends on a real-time clock and I think that since everything is so fast (less than a nanosecond) the addition does not overflow.

Oh. Sorry I did not tell, but please use a mocked clock from Quanta for testing (doc). Moka has support for it. See time_to_live test here for details.

sleep(Duration::from_millis(1000)); // funny changing this to 1 passes the test

It is because the eviction process will run at 500 milliseconds after the cache creation. Then it will run every 300 milliseconds. (code)
For testing, you want to stop the repeating eviction process by calling reconfigure_for_testing. Then run sync() twice after inserting a cache entry. See the time_to_live test above for details.

so maybe is it wiser to unify all additions to quanta::Instant checked somehow?

I think so. You can create a function in moka::common module or somewhere else. The function will do checked_add and panic! when fail. Then search the source code for ts + *ttl and ts + *tti (I believe there are four of them), and change them to call the function.

Then call sync() ~twice~ maybe once after inserting a cache entry.

It might help to read the Implementation Details section in the doc to understand how the expiration is handled.
Here is a summary:

When an entry (key-value) is inserted to the hash map, a recording of a write will be pushed to the write-log inter-thread channel.
When sync is called,

the recording will be popped from the channel, and entries will be created for the key on the write-order queue and access-order queue.
then, the entries in the write-order and access-order queues will be checked if they has been expired. The overflow can occur at the check.

Thanks, @tatsuya6502 .
I have implemented it type-driven by wrapping quanta::Instant in a wrapper type that only allows for checked additions. This both guarantees current implementations work on all platforms (as per your concerns) and also guards against future unchecked additions. currently, this forces the caller to handle the overflow issue (handling None), hence the panic code is implemented at the call site. A matter of style. Tell me if you want that to be changed.
About the max allowed value, Redis allows max int of seconds (which is 136 years) and Aerospike allows for a max of 10 years (just as a reference). So to me, 1000 years is a bit too much as a Durationbut it certainly fits in a Duration (only 35 bits):
    let year_secs: u64 = 365 * 24 * 3600;
    let d3 = Duration::from_secs(1000 * year_secs);

About the max allowed value, Redis allows max int of seconds (which is 136 years) and Aerospike allows for a max of 10 years (just as a reference).

Thank for the information. Good to know.