Virtual Machine Specification not available

Dear Authors @rohitgirdhar ,
I tried to download and use the VM Spec but the downloaded spec_v0.img file is corrupted.
May I ask whether the link to download the VM spec is updated?
Could you kindly share the working URL to download the VM spec for CATER?
I used the download link in this webpage: https://cmu.box.com/s/krg7ehliaidruxjk21nfxsa0gge2uf2o, as provided in CATER-master/generate/README.md. However, when I tried to open the downloaded 3.0 GB spec_v0.img file, it says “The disc image file is corrupted”. If I specify the directory of the downloaded spec_v0.img file in launch.py and run launch.py, it prompts “singularity: not found”, as if there weren’t any spec_v0.img file. I have tried downloading and opening the spec_v0.img file on MacOS, Windows and Ubuntu, but all led to the same issue. I have tried using “wget” command to download the spec_v0.img file, but I didn’t find the specific URL for downloading.
I'm interested in your work and would like to learn from it.
Thank you very much!

Hi @ziqihuangg thanks for your interest and apologies for the delay in responding.
The link should be correct, nevertheless I updated the link to a direct download link that should make it easier to download on a headless server. You can use something like
$  wget https://cmu.box.com/shared/static/krg7ehliaidruxjk21nfxsa0gge2uf2o.im -O spec_0.img
$ singularity run spec_0.img

I just tried it using the img file downloaded from Box, and it seems to work for me on a different machine from where it was created. Perhaps there is some other issue in terms of your singularity installation? Maybe try running some standard singularity img file to see if this issue is specific to this img file?

Hi @rohitgirdhar, thank you for the direct download link. Now the singularity run spec_0.img command works well.
However, when running launch.py, prompt was that 'no such file or directory' for blender. I have replaced blender_path in launch.py with the absolute directory to blender. I'm using blender 2.78c, and the same blender_path works for CLEVR. May I ask whether it might be due to the VM, or there might be some other causes? Thank you again!

Hi @rohitgirdhar thank you for the direct download link. Both singularity and the img work now :)


Fix more misc. issues

Enhancements

Resolve #711 - Add rarity filter to new weapon popup

Fixes

Resolve #719 - Allow enemy editor to wrap
Resolve #726 - Don't allow optimizing for empty targets
Update wording for graph target selector
Resolve #711 - Add rarity filter to new weapon popup
Resolve #727 - Move unowned arti sets to bottom of config
Resolve #730 - Disable partial builds toggle while optimizing

This should Resolve #733, right?

This should Resolve #733, right?

I'm moving the fix to #733 to a different PR since there are a few changes to go with that


🌱 Remove duplicate healthcheck test trigger file

healthcheck test is called from remediation_based_feature_test.go the file healthcheck_test.go is not needed

/test-ubuntu-e2e-feature-main

/test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/keep-test-ubuntu-e2e-feature-main

/test-ubuntu-e2e-feature-main

/test-ubuntu-e2e-feature-main

/test-ubuntu-e2e-feature-main

/test-ubuntu-e2e-feature-main

/test-ubuntu-e2e-feature-main

/test-centos-e2e-integration-main
/test-ubuntu-integration-main

/override keep-test-ubuntu-e2e-feature-main
Non required keep test.


added missing com.intellij.modules.java dependency / 1.6.4 release / bumped to 1.6.5

I would recommend adding "Closes #70" to the PR description so that it will close that issue automatically on merge.

I would recommend adding "Closes #70" to the PR description so that it will close that issue automatically on merge.

That is already in the commit message.

@firewave 1.6.4 has been uploaded to JetBrains for moderation.
Thanks again for your work!

No problem. Let's hope it goes through this time.
The really big tasks are still to come ... 😫

1.6.4 has been approved and released.

Something is wrong here:

It is not compatible with several IDEs including CLion.
And I once again forgot the newline in the release notes:

Perhaps the way compatibility is declared had changed?
https://github.com/johnthagen/clion-cppcheck/blob/10341182f5760d92f6200b67cb5de9ceb5ff6d90/resources/META-INF/plugin.xml#L30

Unlikely as that is the version of the underlying platform. I have the feeling it might be related to the added com.intellij.modules.java dependency.
I will do some local tests later on and contact the support if necessary.

Yes, I can confirm that is it:

Since that compatibility issue only dealt with 2019.x, why don't we simply bump our minimum idea-version to the corresponding build version for 2020.x? We could probably go even higher given that it's unlikely many users will be using anything older than 2022.x.


Remove version: FengHe.FocusNote version 2.15.1-670

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://download.kirakuapp.com/FN_PC/Focus Note Setup 2.15.1-670.exe
Response Error: The remote server returned an error: (403) Forbidden.
(Automated message - build 912)


Type mistake in README

I was going through the readme file.  There is some typing mistake in the README.md file.
Attaching screenshot for reference.

Thanks, @garg-Megha I will push the fix in the next version. Do let me know if you find anything else too.


fix: [#294] Validator cant check the param of url

Closes #
📑 Description

✅ Checks

[x] My pull request adheres to the code style of this project
[x] My code requires changes to the documentation
[x] I have updated the documentation as required
[x] All the tests have passed

ℹ Additional Information

Codecov Report
Attention: 4 lines in your changes are missing coverage. Please review.

Files
Coverage Δ

context_request.go
63.17% <50.00%> (+0.25%)
:arrow_up:

:loudspeaker: Thoughts on this report? Let us know!.


Adding option for creating template of Positron (Django or Static)

Added option to create a project using Django or Static Position (supported by Toga). I will be using it for my tutorial but I don't know if it is useful to push back upstream - feel free to have a look and discuss.

PR Checklist:

[x] All new features have been tested
[ ] All new features have been documented
[x] I have read the CONTRIBUTING.md file
[x] I will abide by the code of conduct

Happy to add tests and docs if it is desired upstream, let's talk about it.

I am using this for the quick demo for now, will open a new PR when there is a solution for the GUI framework plug-in described in https://github.com/beeware/briefcase/issues/1288


Clarify what "additional languages" means when importing projects

Description of the feature request:
The .bazelproject that is generated when choosing "Create from scratch" in the import wizard currently contains
additional_languages:
  # Uncomment any additional languages you want supported
  # dart
  # javascript
  # python
  # typescript

It is unclear what the default languages are (C++? Java?), and if this list is the complete list of possible additional languages, or if not, where to find the correct spelling of any other additional languages.
It would also be good to explain further what this setting does. E.g. will a project fail to import if it contains code in a non-supported language, or will certain features (which ones?) be simply unavailable? There is currently no mention on https://ij.bazel.build/docs/import-project.html either.
What underlying problem are you trying to solve with this feature?
Avoid user confusion.
What operating system, Intellij IDE and programming languages are you using? Please provide specific versions.
Ubuntu 20.04, CLion 2023.2
Have you found anything relevant by searching the web?
No.
Any other information, logs, or outputs that you want to share?
No response

There is an explanation for all project view sections in https://ij.bazel.build/docs/project-views.html including additional_languages: https://ij.bazel.build/docs/project-views.html#additional_languages. We can add more details to it as you described.


Elysium: Unable to download enbseries_skyrimse_v0454.zip (Please update)

Hello,
I have been trying to download 'Elysium' -Modpack, and i keep getting this error message below:
Error message:
926,4 - Cannot continue, was unable to download one or more archives
It looks like the "enbseries_skyrimse_v0454.zip"-file has been updated from Version v0454.to version 0460 on the website: http://enbdev.com/mod_tesskyrimse_v0460.htm
I hope @TitansBane (the creator of Elysium) reads this message, and fixes/updates Elysium.
Many thanks!

Its be resolved!
Thx!


how to change the language to english?

does it support english language?
if yes, how to change it to?

No


The TypeScript for SPFX is so out of date.... ( 2.4 ) really MS

How are we expected to use SPFX with all of the vulnerabilities, in the out of date versions of open source JS.   Microsoft if your going to go open source.... then go open source and keep up. bottom line.

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

ID: c43fab8f-85bf-e577-317b-a71dada5c865
Version Independent ID: 4d041f90-2cc7-ed20-c007-d2a36f9c7c7b
Content: Update SharePoint Framework packages
Content Source: docs/spfx/toolchain/update-latest-packages.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

Second this a thousand times. We have had to fight the framework constantly due to typescript versioning issues. React 16 is still not sorted too!

@CPritch See this article. They are upgrading Sharepoint Online to React 16.
Unfortunately the old TypeScript version with SPFx still remains.

To make matters worse: If you have to develop for SharePoint 2019, the version is frozen in time and you have to use really old versions. Currently, it's only semi-bad but it will get much, much worse over the lifecycle of SharePoint 2019 if Microsoft does not invest in updating the tooling for SPFx.

To make matters worse: If you have to develop for SharePoint 2019, the version is frozen in time and you have to use really old versions. Currently, it's only semi-bad but it will get much, much worse over the lifecycle of SharePoint 2019 if Microsoft does not invest in updating the tooling for SPFx.

We've had a response that MSFT is NOT updating SharePoint 2019's SPFx version until the next major content update. Ridiculous, why is the Enterprise version of the software supposed to remain out of step?!

This isn't intended to be excuses, but to clarify some points made in this thread. If you'd like to request MSFT change their stance (such as not updating on-prem SPFx in SP2016 & SP2019), that falls into a feature request which would best be submitted to user voice: https://aka.ms/sp-dev-uservoice.
I don't see anything actionable in this issue to flag as a bug or a question, so I will close the issue after responding.
@darkriderdesign said:

How are we expected to use SPFX with all of the vulnerabilities, in the out of date versions of open source JS.

Fair point that some existing packages leveraged in the build toolchain are old, such as TypeScript (v2.4 vs. the current v3.x) and webpack (v3.x vs the current v4.x) in the current in SPFx release (v1.7.1), to be clear the only thing you deploy to your SharePoint environment is a JavaScript bundle that includes YOUR code, not code from other packages. None of the dependencies in a base package are shipped with your deployment... the only thing in the resulting JS bundle is your code.
If you elect to use other 3rd party libraries such as lodash, underscore, jquery, jquery plugins, moment, etc, the versions used are managed by you and can be deployed in the bundle or referenced from a CDN. IOW, you have full control here.
@CPritch said:

We've had a response that MSFT is NOT updating SharePoint 2019's SPFx version until the next major content update. Ridiculous, why is the Enterprise version of the software supposed to remain out of step?!

Microsoft has said for many years and two SharePoint releases now that the focus is to build for SharePoint Online first, then to have the on-premises version of SharePoint to be a snapshot from a point in time from what's in SPO. This has been true for both SharePoint Server 2016 & SharePoint Server 2019. Going back to SharePoint 2013, they've been pretty clear that the recommendation is to move to SharePoint Online where they can not just innovate quicker, but to also address vulnerabilities much quicker as well.
Again... this isn't meant to be an excuse. There's just nothing actionable in this issue hence why I'm closing it.
With all that being said...
Personally, I've been annoyed with the toolchain as I too want to use the latest version of React in production, leverage the best features & performance improvements from the latest versions of TypeScript & webpack in my builds, but I can't find fault with the on-prem stance. They've been more than clear about their plans & goals for well over 5 years... you could argue nearly 7 going back to their public statements at the SharePoint Conference in 2012 where they initially stated, but later rolled back, that SharePoint 2013 would be the last on-prem version.

The point of my comment wasn't to express, to "not" use SPFX the point was to express, that the community needs quicker updates.  That's all...  I love working in the new SPFX framework.  But when I go to incorporate something from NPM and what I'm trying to incorporate is 3 versions newer in the code base it just raises eyebrows.  So again, I'm glad the thread is being closed, and Microsoft is doing a great job, keep up the good work.
Thanks,
Darkriderdesign

@darkriderdesign
Second this a thousand times. Apologies for my rant as it was not fair. SPFx has revolutionised what we can produce and the time we can do it in. I am very excited to see how the platform progresses.
I truly believe that this is the future of the modern intranet and along with Teams we're seeing all the puzzle pieces fall into place for the vision MS has here.

BTW... take a look at v1.8.0. Includes TypeScript v2.7.2, React v16.7 (but be aware of #3605) & Fabric React v6.156.

BTW... take a look at SPFx v1.8.0. Includes TypeScript v2.7.2, React v16.7 (but be aware of #3605) & Fabric React v6.156.

But that does not remove the issues that exist on SharePoint 2019 as this is fixed on 1.4.1 with lots of issues in the corresponding tooling. In my opinion, it is one thing to freeze the platform but a different thing to also freeze the tooling required to build stuff for the platform. In the past, it was possible to use the newest Visual Studio Version and newest C# version to write Full Trust Solutions even for pretty old SharePoint versions (I can still write a Full Trust Solution for SharePoint 2013 with VS 2017 and C# 7.3...). The same should be true for SharePoint on premises even though the platform will not get any new Features.

The SPFX team created a tooling that makes it very easy for a sharepoint developer to get started.
While the first steps are achieved without great effort, it becomes clear that "making things easy" comes at a great cost in the long run.
The tooling is very interwoven and full of dependencies.
From the first moment of setting up a SPFX Project, i already lost a great amount of control and flexiblity to move things forward during the next months of my project.
Sorry, this is not very constructive.
I would love to see some documentation on how to setup a minimal project template.  Without ANY yeoman and without any advanded dependencies or build-tasks.  And then let the some develpers start from there. And maybe the SPFX-team can discover that there is real value in a simple solution.


possible to implement "select" db?

possible to implement "select" db like redis?

Not possible. It is recommended to use multiple instance instead of multiple databases.

how to do multiple instance?


Log errors when calculation fails even though FD is running in "silent"

It seems as if log file for fdscript does not always add a error or warning when FD is running in "silent".

Reproduce error and send feedback to BP.

https://strusoft.fogbugz.com/f/cases/120466/Log-messages


overflow of int issue in startup

If the tick count is too large the calculation overflows the signed int and therefore becomes a large positive number, this means the system hangs indefinitely.
This was causing a few issues as myself and my friends tend to hibernate between coding sessions.

I suggest simply setting getTicks to 0 on application startup
unsigned int Win32Core::getTicks() {
    LARGE_INTEGER li;
    QueryPerformanceCounter(&li);
    if (PerfInitial == 0) // Define this variable somewere, preferably a private in Win32Core
        PerfInitial = li.QuadPart;
    return (unsigned int)((li.QuadPart - PerfInitial) / pcFreq);
}


Vcpkg port

As promised, a vcpkg port that allows consuming Scope as vcpkg package.

Could you add a license header comment?
Do I understand correctly that the hash sums will require updating whenever new commits are made?

Also, Boost.Scope requires Boost 1.84 (i.e. the current master or develop).

Could you add a license header comment?

Will do.

Do I understand correctly that the hash sums will require updating whenever new commits are made?

Yes. Normally vcpkg ports aren't parts of the packaged project, but are parts of a separate "repository" project.

Do I understand correctly that the hash sums will require updating whenever new commits are made?

Yes. Normally vcpkg ports aren't parts of the packaged project, but are parts of a separate "repository" project.

In that case I won't be able to maintain it. It would be ok to keep it for the sake of the review (provided that the 1.84 requirement can be managed), but after that I will probably remove it. If the library is accepted, that shouldn't be a problem, as the library would be packaged as part of Boost.

Yes, the intention is for this to be temporary, because vcpkg team makes Boost packages for vcpkg by themselves.

Thanks.


Total Economy crashes (at the restart) after installing GriefProtection

Sponge Version:  1.12.2-2611-7.1.0-BETA-2931
Forge Version:  1611
Total Economy Version:  1.8.0
Description of issue
I have done something in the steps to reproduce (see below).
It seems to be a problem relating to GP as well. However when I removed all GP's jar, the problem persists. It seems that GP has changed the property of the chest. Since it is the TE crashing, I just open an issue here.
Console errors
At the final stage of loading:
https://hastebin.com/nefibiwopo.hs
After user connects:
https://hastebin.com/ubohonereq.hs
Crash report:
https://hastebin.com/hoxavakuze.sql
Steps to reproduce

Set up a chest shop
Stop server, installed GriefProtection build 504, restart server, everything works ok
Stop server, delete GP b504, replace with GP b555, restart server, connect from client, crashed
Stop server, delete GP b555, replace with GP b560, restart server, connect from client, crashed
Stop server, delete all GP's jar, restart server, connect from client, crashed
Stop server, using back GP b504, restart server, connect from client, crashed
the above crash reports/logs are obtained at step 5

Have you tried replacing the Total Economy jar?

@Erigitic I checked the checksum of the file one on my disk and the one released, they have the same checksum.
Maybe this is a permission problem, but my server is booted under Admin permission. I tried to delete the file and download again, the problem persists.
Updating Sponge to 1.12.2-2611-7.1.0-BETA-2970 does not fix this problem.

Let's move future discussion on this issue to #262


Move everything around

This PR refactors the codebase to give blueprints their own folders and template folders. It also separates database operations into a database package with modules corresponding to database tables.

In terms of structure everything looks good, much more manageable compared to what we had before. I haven't had a chance to test things out but given how it's mostly refactoring I'd say it's good to go.
That being said, I'm not looking forward to the merge conflicts on my pull request :(


Add plugin README template

Add a default plugin readme template
I thought it may be helpful to have a template for plugin README's
then plugins can be required to have a readme before being merged.
Does anyone else think is a good idea?
Comments on format or content?

As commented on https://github.com/robbyrussell/oh-my-zsh/issues/7175#issuecomment-425757996, it might be a good idea to make several kinds of readme templates for different kinds of plugins. It's a great start, though. 👍

I'm hesitant to merge this because it would mean having another file in the OMZ directory, I'd rather have this in the wiki. But I like the template! I think it covers most plugin types. Thanks!

Is this on the wiki ?

No its not i kinda forgot about it sorry, What section should it go in?


App loses hover while moving mouse along top and left edges

When a tauri app is in fullscreen mode (or otherwise positioned at 0,0) moving the cursor along the top or left edges results in flickering hover state.
OS: Linux
E.g.
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <style>
      html {
        height: 100%;
        background-color: black;
      }
      html:hover {
        background-color: white;
      }
    </style>
  </head>
</html>

"windows": [
  {
    ...
    "fullscreen": true
  }
]

Demo seizure warning!: https://user-images.githubusercontent.com/11533746/189830715-c6c036f8-0300-4318-8d49-fea0998401c3.mp4

I wouldn't consider this as a bug, since the cursor on most Operating Systems can move to a position outside of the monitor bounds and thus won't be hovering over the fullscreen window.


GeneralGraph class needs export to adj matrix

Hi there,
I really hope you could add an additional method to produce the adjacency matrix.
Here's a use case very common in GCastle:
from castle.metrics import MetricsDAG
from castle.common import GraphDAG
from causallearn.search.ConstraintBased.PC import pc
import matplotlib.pyplot as plt

cg = pc(dataset,alpha=0.001,indep_test='mv_fisherz',mvpc=True,stable=True)

GraphDAG(est_dag=cg.G.adj_matrix(),true_dag=true_matrix)
plt.show()

We need a method for example adj_matrix() that returns a numpy adjacency matrix.
That way we can perform the metrics calculations.

For the record this doesn't work because of some numpy broken dependency:
cg_full.to_nx_graph() nx.adjacency_matrix(cg_full.nx_graph)

It seems that this is working:
nx.to_numpy_array(cg_full.nx_graph)
let me test it more.

Hi, thanks for your suggestions. Did you happen to try cg.G.graph? It returns an 'adjacency matrix' with its semantics documented here  (Returns).

That also worked, here's the output:
cg.G.graph

array([[ 0, -1,  0,  1,  0,  0,  0,  0,  1],
       [ 1,  0,  0,  1,  0,  0,  0,  0,  0],
       [ 0,  0,  0,  1,  0,  0,  0,  1,  1],
       [-1, -1, -1,  0,  0,  0,  0,  0,  0],
       [ 0,  0,  0,  0,  0, -1,  1,  0,  1],
       [ 0,  0,  0,  0, -1,  0,  1,  0,  1],
       [ 0,  0,  0,  0, -1, -1,  0,  0,  0],
       [ 0,  0, -1,  0,  0,  0,  0,  0, -1],
       [-1,  0, -1,  0, -1, -1,  0, -1,  0]])

This is with the other approach:
cg.to_nx_graph()
nx.to_numpy_array(cg.nx_graph)
array([[0., 1., 0., 0., 0., 0., 0., 0., 0.],
       [0., 0., 0., 0., 0., 0., 0., 0., 0.],
       [0., 0., 0., 0., 0., 0., 0., 0., 0.],
       [1., 1., 1., 0., 0., 0., 0., 0., 0.],
       [0., 0., 0., 0., 0., 1., 0., 0., 0.],
       [0., 0., 0., 0., 1., 0., 0., 0., 0.],
       [0., 0., 0., 0., 1., 1., 0., 0., 0.],
       [0., 0., 1., 0., 0., 0., 0., 0., 1.],
       [1., 0., 1., 0., 1., 1., 0., 1., 0.]])

As you can see they are different, for the simple reason that the second is producing a directed graph, so it's all Out Edges, but then I don't know if it just ignores the undirected edges?
cg.nx_graph.nodes()
NodeView((0, 1, 2, 3, 4, 5, 6, 7, 8))

It is kind of hard to debug without assigning proper labels.
I am creating another issue for the labelling is driving me mad.

I also noticed something strange: there is an undirected edge between REVENUE_USD and NUM_ORDERS but the matrix index(4,5) = -1
array(['IMPRESSIONS', 'CLICKS', 'CONVERSIONS', 'AD_SPEND_USD',
       'REVENUE_USD', 'NUM_ORDERS', 'AOV_USD', 'VISITORS', 'SESSIONS'],
array([[ 0, -1,  0,  1,  0,  0,  0,  0,  1],
       [ 1,  0,  0,  1,  0,  0,  0,  0,  0],
       [ 0,  0,  0,  1,  0,  0,  0,  1,  1],
       [-1, -1, -1,  0,  0,  0,  0,  0,  0],
       [ 0,  0,  0,  0,  0, -1,  1,  0,  1],
       [ 0,  0,  0,  0, -1,  0,  1,  0,  1],
       [ 0,  0,  0,  0, -1, -1,  0,  0,  0],
       [ 0,  0, -1,  0,  0,  0,  0,  0, -1],
       [-1,  0, -1,  0, -1, -1,  0, -1,  0]])

cg.G.graph[4,5] = -1

I think we should use another value to represent the undirected, otherwise it looks like is an inward arrow.

Thanks for the question. In this case, cg.G.graph[5,4] is also -1, which represents that there exists an undirected edge between 4 and 5. I agree with you that this is not as intuitive as the common adjacency graph. That design is mainly for consistency with more complex graphical representations, e.g., PAGs.

What about we could let the user decide the meaning of the labels and pass it as a dictionary? This should be a couple of code line changes in the library.

Thanks for the suggestion. I'm not fully sure what would be the best reason to incorporate it as a hyper-parameter of the function. It seems that this type of dictionary could also be easily created by users if they have some specific needs for the meaning of endpoints? We will think about it.


Add additional context to logs

Feature
Feature description
When looking at the logs generated via the --debug flag or the log file, it can be challenging to know where the logs was generated from.  It would be useful to have additional context, such as the file, line number, and function that generated the log message.
Who will this benefit?
This will benefit anyone who needs to deeply debug logs, possibly looking at dbt source code.
Proposed solution
This can be fairly simply added by updating the default_formatter in logger.py.  Here's a sample change:
def default_formatter():
    return logging.Formatter(
        '%(asctime)-18s (%(threadName)s) '
        '%(filename)s:%(lineno)s in %(funcName)s: %(message)s')

This does a pretty good job, except for cases where the log messages are generated by helper functions, such as those found in printer.py (e.g. print_run_result_error, print_end_of_run_summary, etc).  To handle those cases, it could be possible to override the findCaller implementation in the logger (possibly by extending the logger implementation) and have this function traverse up the call stack an additional level if it finds a blacklisted file (such as printer.py).  I haven't fully figured out this implementation, but have been gathering some inspiration from this Stack Overflow post:  https://stackoverflow.com/questions/19615876/showing-the-right-funcname-when-wrapping-logger-functionality-in-a-custom-class
If this general approach sounds good, I'm happy to create a pull request.
Thanks!
-Matt

If there is some desire to keep dbt internal implementation details out of the logs by default, then maybe this feature could be controlled via the --debug flag, or perhaps a new --verbose flag.

Hey @heisencoder - I'm not opposed to this, but I do agree that we might want to tuck it behind a --verbose flag (or similar). Most dbt users out there aren't familiar with the codebase, and I think showing dbt filenames/functions/line numbers might be more confusing than helpful!
I totally buy that this would be really helpful in development. So sure, happy to merge a PR for this. Unsure how important it is for us to override findCaller though - I'm not sure that showing the parent function call is going to be helpful enough to be worth the additional complexity. Let me know if you feel differently.
Thanks!

Sounds good! -- I'll look into flag controlling the output and see whether the findCaller implementation can be simple enough to not add too much code complexity.  Based on my vacation schedule, I should have something in the next couple weeks.

After considering this more, I'm going to leave this as-is because the context provided by the standard logging output is good enough for what we're doing.


How to use utility functions within external functions in DLLs

Reported by jochenkoehler on 20 Sep 2013 12:45 UTC
In Modelica 3.3 specification chapter 12.9.6 some utility functions are desribed that can be used from self-written external functions. This works fine, if you're adding your code as C-source code or static library.
But how can you use these functions, when you want to use your code linked as a DLL? I see no way to successfully do that, because you can't link the needed code into the DLL.
is there any possibility do do that?

Migrated-From: https://trac.modelica.org/Modelica/ticket/1280

Comment by sjoelund.se on 23 Sep 2013 07:29 UTC
I just do this in Linux:
#include <ModelicaUtilities.h>

char* f() {
  char *res = ModelicaAllocateString(2);
  res[0] = 'a';
  res[1] = '\0';
  return res;
}

gcc -Wall -o f.so -fPIC -shared f.c -I/usr/include/omc
I can then link it using (for example) the OpenModelica implementation of the functions, and some C code:
#include <stdio.h>

char* f();

int main()
{
  printf("%s\n",f());
}

Is Windows so incapable it cannot dynamically link in unresolved symbols when the dll is loaded?
The following suggests it is possible to do in Windows as well (and is thus mainly a tool issue): http://stackoverflow.com/questions/9950607/unresolved-external-symbol-when-creating-a-dll

Comment by beutlich on 21 May 2014 21:19 UTC
In the Visual Studio Command Prompt (2010) you can simply call
cl /MD /I"%ALLUSERSPROFILE%/Documents/SimulationX 3.6/Modelica/Modelica 3.2.1/Resources/C-Sources" f.c /link /DEFAULTLIB:ModelicaExternalC.lib /DLL /OUT:f.dll
to compile and link the external function code f.c
#include <ModelicaUtilities.h>

char* f() {
  char *res = ModelicaAllocateString(2);
  res[0] = 'a';
  res[1] = '\0';
  return res;
}

as a dynamic link library f.dll to be used with SimulationX. The SimulationX specific library ModelicaExternalC.lib is part of the installation of SimulationX or, for example, can also be obtained as part of the official ITI-GmbH repository from GitHub.
See also your ticket #1323 where I summarized some best-practice recommendation.

Modified by beutlich on 20 Jun 2014 11:05 UTC

Modified by dietmarw on 13 Nov 2014 14:38 UTC


Improve performance of frost-select

This project uses semver, please check the scope of this pr:

[ ] #none# - documentation fixes and/or test additions
[x] #patch# - backwards-compatible bug fix
[ ] #minor# - adding functionality in a backwards-compatible manner
[ ] #major# - incompatible API change

CHANGELOG

Fixed performance regression in frost-select that was introduced when adding text trimming.

LGTM :+1:

Changes Unknown when pulling a9e07e17d8b5f42795c230e74a9dfc7c8eee98b5 on sandersky:master into ** on ciena-frost:master**.

Changes Unknown when pulling a9e07e17d8b5f42795c230e74a9dfc7c8eee98b5 on sandersky:master into ** on ciena-frost:master**.

Changes Unknown when pulling a9e07e17d8b5f42795c230e74a9dfc7c8eee98b5 on sandersky:master into ** on ciena-frost:master**.

Changes Unknown when pulling 1592408accf17b6d6bdd2528093712da03f70df7 on sandersky:master into ** on ciena-frost:master**.

Changes Unknown when pulling 1592408accf17b6d6bdd2528093712da03f70df7 on sandersky:master into ** on ciena-frost:master**.

Changes Unknown when pulling 1592408accf17b6d6bdd2528093712da03f70df7 on sandersky:master into ** on ciena-frost:master**.


Build succeeds but all routes return 500 status with ENOENT error

Reproduction
I can confirm this error came out of the blue. The server was up an running when I got this:
Error: ENOENT: no such file or directory, open 'E:\E:\SaaS%20King\boilerplate-one\build\index.js.map'
    at Object.readFileUtf8 (node:internal/fs/sync:25:18)
    at Object.readFileSync (node:fs:441:19)
    at Array.retrieveSourceMap (E:\SaaS King\boilerplate-one\node_modules\@remix-run\serve\dist\cli.js:49:37)
    at E:\SaaS King\boilerplate-one\node_modules\source-map-support\source-map-support.js:85:24
    at mapSourcePosition (E:\SaaS King\boilerplate-one\node_modules\source-map-support\source-map-support.js:216:21)
    at wrapCallSite (E:\SaaS King\boilerplate-one\node_modules\source-map-support\source-map-support.js:397:20)
    at Function.prepareStackTrace (E:\SaaS King\boilerplate-one\node_modules\source-map-support\source-map-support.js:446:39)
    at maybeOverridePrepareStackTrace (node:internal/errors:141:29)
    at prepareStackTrace (node:internal/errors:115:5)
    at getStackString (node:internal/util/inspect:1239:16)
GET / 500 - - 1.971 ms

Why are there two E:\ in the path?
My route structure (which had been working totally fine earlier):

System Info
System:
    OS: Windows 11 10.0.22631
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
    Memory: 785.61 MB / 7.86 GB
  Binaries:
    Node: 20.9.0 - D:\Node\node.EXE
    npm: 10.2.4 - ~\AppData\Roaming\npm\npm.CMD
    pnpm: 8.11.0 - ~\AppData\Local\pnpm\pnpm.EXE
  Browsers:
    Edge: Chromium (120.0.2210.77)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    @remix-run/css-bundle: ^2.4.0 => 2.4.0
    @remix-run/dev: ^2.4.0 => 2.4.0
    @remix-run/node: ^2.4.0 => 2.4.0
    @remix-run/react: ^2.4.0 => 2.4.0
    @remix-run/serve: ^2.4.0 => 2.4.0

Used Package Manager
npm
Expected Behavior
Pages should be showing up fine.
Actual Behavior
Pages don't load because of the error.

I think this is a duplicate of https://github.com/remix-run/remix/issues/8309.  Want to try the latest nightly and see if it's fixed there?  0.0.0-nightly-6a1c4ff-20231219

I think this is a duplicate of #8309. Want to try the latest nightly and see if it's fixed there? 0.0.0-nightly-6a1c4ff-20231219

I am running 2.4.1 and still having this issue. Looks like its duplicating the drive letter still.

Hello, I would like to add to @CaseyLemieux that I am also still experiencing this issue even after 2.4.1, as also outlined in #8309

I've noticed that mine is primarily occurring if there is an issue with a line of code at runtime. For example, if I put this line of code in my loader it will cause the error to appear: const test = await db.$queryRawSELECT * FROM arrest TAKE 5; If I remove the code the page will run as expected.

I've noticed that mine is primarily occurring if there is an issue with a line of code at runtime. For example, if I put this line of code in my loader it will cause the error to appear: const test = await db.$queryRaw"SELECT * FROM arrest TAKE 5"; If I remove the code the page will run as expected.

I had this same issue, and it was due to missing .env lines causing an error in the loader. I think the error is just being misreported rather than the program not working.

I don't have evidence to second this but assuming this is a misreporting of error, even if I fix the original error, I ended up with the duplicate drive letter. Talking about 2.4.0 here, haven't tried 2.4.1.


Replace pry-debugger with pry-byebug

It seems that pry-byebug is the successor of pry-debugger. It seems to fix the "next erroneously behaves like step" bug:
https://github.com/nixme/pry-debugger/issues/34#issuecomment-36779480
You should consider to replace pry-debugger.

@nixme shouldn't this issue still be open until the changes you mentioned about removing pry-debugger from the dependencies is done. This would be useful for me tracking this so I know when we can switch back to the release version.
As it stands, the bring-your-own-debugger depends on outdated pry versions, whereas master has been updated.

@jeremyhaile take a look at my fork. plribeiro3000/jazz_fingers. it has updated versions os the dependencies.

@plribeiro3000 Thanks. I'll use your fork for now, although I'd love to see the official version get updated.
Have you submitted a pull request?

Nope. There are a lot of open PR's already. I've opened a new issue to ask
about the project but i got no answer so i forked. See #32 .
Em dom, 22 de fev de 2015 17:26, Jeremy Haile<EMAIL_ADDRESS>escreveu:


'Resolving your shell environement is taking very long' shown in every window

Suggest to show the warning only in the active window and not in every window

It will now be shown in the active window and also only ever once per session.
Note that there is also an error notification that shows when we give up to resolve the shell environment (after 10s). That one will still show in each window because it basically means the window has no shell environment to use which can result in all kinds of issues.

It will now be shown in the active window and also only ever once per session.
Note that there is also an error notification that shows when we give up to resolve the shell environment (after 10s). That one will still show in each window because it basically means the window has no shell environment to use which can result in all kinds of issues.


[ ] Run load tests.
[ ] Update documentation if needed.
[ ] Update CHANGELOG.md.

Closing


Implement 3D textures as import and resource format.

To import a 3D texture, select import type Texture3D and the slicing:

New resource types have been added, Texture3D( base), ImageTexture3D, and StreamTexture3D.

And a previewer:

Could someone tell me what this is used for? I'm not getting it yet

@menip 3D textures have many uses, I personally use them to store noise data for volumetric clouds.

3D textures are also often used as LUTs (look-up textures) for color correction.

This is great. Can it be backported to Godot 3 ?

@vitorbalbio Godot 3.x already supports 3D textures, but the import options are different.


Error on opening co-op replays in 1.6.0

Using the latest version of sc2reader available on PIP, sc2reader chokes when opening co-op replays that use factions besides the standard multiplayer ones. I did not encounter this error previously on version 1.5.0.
Here is a sample replay.
Here is a simple test script that uses that replay to demonstrate the issue:
#!/usr/bin/env python3

import sc2reader

replay = sc2reader.load_replay('./Miner Evacuation (64).SC2Replay', load_level=2)

It gives me the following error when executed:
Traceback (most recent call last):
  File "./test.py", line 5, in <module>
    replay = sc2reader.load_replay('./Miner Evacuation (64).SC2Replay', load_level=2)
  File "/Users/jcfields/Library/Python/3.8/lib/python/site-packages/sc2reader/factories/sc2factory.py", line 85, in load_replay
    return self.load(Replay, source, options, **new_options)
  File "/Users/jcfields/Library/Python/3.8/lib/python/site-packages/sc2reader/factories/sc2factory.py", line 143, in load
    return self._load(cls, resource, filename=filename, options=options)
  File "/Users/jcfields/Library/Python/3.8/lib/python/site-packages/sc2reader/factories/sc2factory.py", line 152, in _load
    obj = cls(resource, filename=filename, factory=self, **options)
  File "/Users/jcfields/Library/Python/3.8/lib/python/site-packages/sc2reader/resources.py", line 301, in __init__
    self._read_data(data_file, self._get_reader(data_file))
  File "/Users/jcfields/Library/Python/3.8/lib/python/site-packages/sc2reader/resources.py", line 902, in _read_data
    self.raw_data[data_file] = reader(data, self)
  File "/Users/jcfields/Library/Python/3.8/lib/python/site-packages/sc2reader/readers.py", line 303, in __call__
    result = [
  File "/Users/jcfields/Library/Python/3.8/lib/python/site-packages/sc2reader/readers.py", line 304, in <listcomp>
    Attribute(
  File "/Users/jcfields/Library/Python/3.8/lib/python/site-packages/sc2reader/objects.py", line 80, in __init__
    self.value = lookup[value.strip("\x00 ")[::-1]]
KeyError: 'InfT'

The problem seems to be that the "InfT" (Infested Terran) race used on the Miner Evacuation mission is not in the "attributes.json" file (which only has the standard Terran, Zerg, Protoss, and Random), so its presence in the replay file causes a key look-up error.
I looped through all of my co-op replays and found the following non-standard races that cause read errors:

InfT
ProZ
PZrg
TerH
TerT

I don't know if this is an exhaustive list, but it's a pool of over 1,000 co-op replays.
I would guess that either adding these races to "attributes.json" or implementing some sort of fallback to prevent a fatal error if a non-standard race can't be identified would fix this issue.
Edit: Using sc2reader 1.6.0, Python 3.8.5, Mac OS 10.14.6.

Thanks for sharing the detailed report.
Just to confirm, you said this wasn't happening on 1.5.0 for you, right? I tried running this same replay on v1.5.0 2ee6974f8a9572bfc8460c4f5b5e0243d4f614b3 and got this
>>> import sc2reader
>>> sc2reader.load_replay('./github-126.SC2Replay')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/kevin/sc2reader/sc2reader/factories/sc2factory.py", line 85, in load_replay
    return self.load(Replay, source, options, **new_options)
  File "/home/kevin/sc2reader/sc2reader/factories/sc2factory.py", line 143, in load
    return self._load(cls, resource, filename=filename, options=options)
  File "/home/kevin/sc2reader/sc2reader/factories/sc2factory.py", line 152, in _load
    obj = cls(resource, filename=filename, factory=self, **options)
  File "/home/kevin/sc2reader/sc2reader/resources.py", line 301, in __init__
    self._read_data(data_file, self._get_reader(data_file))
  File "/home/kevin/sc2reader/sc2reader/resources.py", line 893, in _read_data
    self.raw_data[data_file] = reader(data, self)
  File "/home/kevin/sc2reader/sc2reader/readers.py", line 274, in __call__
    for i in range(data.read_bits(5))
  File "/home/kevin/sc2reader/sc2reader/readers.py", line 274, in <listcomp>
    for i in range(data.read_bits(5))
  File "/home/kevin/sc2reader/sc2reader/readers.py", line 212, in <listcomp>
    for i in range(
  File "/home/kevin/sc2reader/sc2reader/decoders.py", line 210, in read_uint32
    data = self._buffer.read_uint32()
  File "/home/kevin/sc2reader/sc2reader/decoders.py", line 91, in read_uint32
    return self._unpack_int(self.read(4))[0]
struct.error: unpack requires a buffer of 4 bytes

Obviously we still need to fix this, but I just want to make sure we're seeing the same regression

Yes, that's correct, I got the same error when trying to open 5.0.x co-op replays in sc2reader 1.5.0 (though 4.x.x replays worked fine, so I assume it was due to whatever changes in the replay format were introduced by that update).

Interesting. It looks like sc2reader/data/attributes.json may be woefully out-of-date. We updated it by hand based on easily discoverable properties, but we probably need to generate it from Blizzard data again.
Thankfully, the original maintainer wrote a script to do this for us https://github.com/ggtracker/sc2reader/commit/fe2a3769ad6b345302782cad2de054b415e12e0e
The next step would be to get a .s2gs file, with instructions for that at https://tl.net/forum/starcraft-2/330926-s2gs-file-a-fun-little-mystery-for-us
Unfortunately I don't have access to the StarCraft 2 client at this very moment to do this, but I'll give it a shot later when I do

Potential fix in #129. Does that work for you?

Yup, that did it, scanned 1,139 co-op replays with no errors. Thanks!


Game crashes when loading the mods

Describe the bug
Game crashes when I try to launch the game, despite not having any mods besides the connector and the fabric api
Steps to reproduce
1.Add the connector and forgefied fabric api into the mods folder
2.Launch game
3.Wait
4.Crash
Logs
https://pastebin.com/VQckUKZJ
Additional context
Literally no other mods, the mod files are:
-.connector folder, that is empty
-Connector-1.0.0-beta.21+1.20.1-full.jar
-fabric-api-0.90.0+1.9.28+1.20.1.jar
and the forge version I am using is 1.20.1-forge-47.2.0

Use Forge version 47.1.3 as instructed in the README. FFAPI is currently not compatible with newer forge versions.

Thanks, it works now. Btw, the mod seems to be incompatible with the fabric mod "Icarus"

Did you had trinkets installed?


Ng fix

This makes a few adjustments based on @nateabele's feedback in #22. There's still more to do, but these are the quickest changes.

Gonna merge so I can keep working, but feel free to comment here / on the issue (which will remain open) if there's any errors in these changes, Nate!


Committed files for existing code review.

This is the code for a fluid component that wraps around express.

I got to everything but the distributeOptions refactor and the test refactor, which are likely to take longer.  I have pushed my changes if you want to review the work so far.

The distributeOptions refactor is complete, working on the tests now.

Closing this request in favor of the second pull request, which was created from my branch.


Usability check

For more information see the link below.
https://github.com/ballerina-platform/ballerina-standard-library/blob/main/docs/library-development-process.md#usability-check

Following usability improvements were added.

https://github.com/ballerina-platform/ballerina-standard-library/issues/2741
https://github.com/ballerina-platform/ballerina-standard-library/issues/2525


test engine logging and headless

Hi again!
I looked at the example for exporting the results and wanted to reproduce the same behavior in python with the following line:
imgui.test_engine.get_io(hello_imgui.get_imgui_test_engine()).export_results_filename = "output_file.xml"
However, it does not seem to be accessible at the moment. Is there a way to use the native logging with imgui_bundle?
Also, I'd be really interested in a way to run the test engine headless, but I was not quite sure how to achieve that when using hello_imgui, so if you have any advice on this topic, I'd be very thankful.
Thanks a lot!

Hi,

export_results_filename: this recent commit enables you to call export_results_filename_set(...)

headless: this commit lets you use a "null" backend

Example:
runner_params.platform_backend_type = hello_imgui.PlatformBackendType.null
runner_params.renderer_backend_type = hello_imgui.RendererBackendType.null

Please tell me if that helps

Hi,
To get a successful export, you will need to do this:
    engine = hello_imgui.get_imgui_test_engine()

    engine.io.export_results_filename_set("output.xml")
    engine.io.export_results_format = imgui.test_engine.TestEngineExportFormat.j_unit_xml

This issue took me half a day of work. Can you give me more information about the context in which you are using the test engine?
Thanks!

Hey there,
thank you very much for the effort, I really appreciate it. I'll test it as soon as I can next week when I'm back from my vacation, but this looks like it should do the trick.
For context: we have built a simple 3d viewer for debug purposes using just the pure python OpenGL backends. With the time, we have added more and more functionality, but are prone to regressions as we don't have any tests at the moment. That's why I'm experimenting with a prototype in hello-imgui to see if a migration to it would be feasible. I currently imagine some sort of headless automatized ui Tests and manual viewer tests whenever we changed something, as it probably still needs our OpenGL context. This is something I'll have to look into next week.
Again, thank you very much for your dedication to this project.

I just tried out the newest version and this is working pretty well. Thanks a lot!🥇


Api/issue attachment

Backlog has updated their api.
One of the useful api is Get Issue Attachment
https://developer.nulab.com/docs/backlog/api/2/get-issue-attachment/
I've added that one.
I had to add a new method getFile, as the get method returns the content only.
To download/process the file we need headers and body both. That's why the getFile method returns the whole response object.

@itigoppo Would you mind to review this PR?

Thanks.

@biplobice
I'm sorry!
Merged!
The release tag is 1.3.0


RunnableDevEnvironment is export from .d.ts as class, but it's not exported from .js

Describe the bug
import { RunnableDevEnvironment } from 'vite';
console.log(RunnableDevEnvironment);

failed to load config from /home/projects/vitejs-vite-zmc8qxuk/vite.config.ts
error when starting dev server:
file:///home/projects/vitejs-vite-zmc8qxuk/node_modules/.vite-temp/vite.config.ts.timestamp-1734498569035-d5fc4179877e1.mjs:2
import { RunnableDevEnvironment } from "file:///home/projects/vitejs-vite-zmc8qxuk/node_modules/vite/dist/node/index.js";
         ^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: The requested module 'file:///home/projects/vitejs-vite-zmc8qxuk/node_modules/vite/dist/node/index.js' does not provide an export named 'RunnableDevEnvironment'

This is exported as type in the source, but it looks like this is somehow dropped in packaged dts.
https://github.com/vitejs/vite/blob/96f123a9ee816ff9a182ab70da1f24520913ccfb/packages/vite/src/node/index.ts#L24-L29

<EMAIL_ADDRESS>
export { ..., RunnableDevEnvironment, type RunnableDevEnvironmentContext, ... };

This probably makes IDE to autocomplete RunnableDevEnvironment without type and that got me runtime errors several times.
Reproduction
https://stackblitz.com/edit/vitejs-vite-zmc8qxuk?file=vite.config.ts
Steps to reproduce

open stackblitz

System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    vite: ^6.0.3 => 6.0.3

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I think it's caused by https://github.com/Swatinem/rollup-plugin-dts/issues/311.
If I change RunnableDevEnvironment in dist/node/index.d.ts to type RunnableDevEnvironment, then TypeScript correctly shows an error.


feat: support external sections in foundry.toml

Component
Forge
Describe the feature you would like
There are various requests and use cases for adding support for custom sections to foundry.toml:

scopelint is a tool for linting forge projects. Instead of having it's own config file, it would be nice to just let users define the settings directly in the forge config file
In https://github.com/foundry-rs/foundry/issues/4808, there's requests to support parsing the config file so it can be extended to contain settings for forge deploy or Noir circuits

Currently, you can add a custom section to the config file, but it will trigger a warning:
$ forge test
warning: Unknown section [scopelint] found in foundry.toml. This notation for profiles has been deprecated and may result in the profile not being registered in future versions. Please use [profile.scopelint] instead or run `forge config --fix`.

Therefore, I'd suggest requiring that unknown sections are prefixed with something like external., which makes it clear they are for other tools that extend foundry and we'd suppress the warning for those sections.
For example:
# Default foundry configuration
[profile.default]
optimizer = false

[profile.ci]
optimizer = true

# Custom sections for other tools
[external.scopelint]
some_flag = 1

[external.forge_deploy]
another_setting = 123

Additional context
No response

Upvote 💯


Harmonize opencv and numpy coordinate conversions

Type of Issue
OpenCV
0/0---X--->
 |
 |
 Y
 |
 |
 v

Numpy
0/0---column--->
 |
 |
row
 |
 |
 v

We deal with this conversion in the perception stack to make things work but don't have clear types or boundaries defined which creates a minefield for bugs that you have to tread about carefully. Fix this.
Select the type of issue:

[ ] Bug report (to report a bug)
[x] Feature request (to request an additional feature)
[ ] Tracker (I am just using this as a tracker)
[ ] Refactor request
[ ] Documentation Ask

from the diagram, are you saying that they are the same co-ordinate system?

from the diagram, are you saying that they are the same co-ordinate system?

the axis ordering is different because of how indexing works in each - a point at (a,b) in one is at (b,a) in the other.

oh i see, OpenCV returns[x,y] and numpy returns[row, column], got it. I'd have expected OpenCV to return [y, x]. Actually I quickly googled, and they say OpenCV is indeed row-major and returns accessors as [y, x]: https://stackoverflow.com/questions/8184053/accessing-elements-of-a-cvmat-with-atfloati-j-is-it-x-y-or-row-col

right, that is part of the problem - the order of image coordinate system is the reverse of what you would need for row-major access. So, if you have (x,y) in opencv image coordinates (as in the diagram above), row-major access means you'll need to still use (y,x) to access it (see one of the answers from above https://stackoverflow.com/a/42327350)

that's also what I'm saying.
Whether you use numpy or OpenCV, you use row-major. So they are consistent.


Expression2 Effects

Added effects. This is my first e2 customization so let me know if anything is wrong. I haven't encountered any bugs so far. The module also defaults to disabled so server owners can choose whether or not to have to deal with effect grief.

:+1: Code looks sensible and clean to me.
It'd probably be worth a look over from somebody who actually uses E2 though :) @Divran maybe?

Crap, I meant to open a new pull request. How do I undo this.

I guess I can leave it as one pull request. I need some help with this commit. It works, but I can't find a way to update the egp once the loading is done so I have to create the egp again after all the textures are downloaded. Also I think I may need to add a way to clean/limit the textures that aren't used.

Added support to play url sounds and added the convar wire_expression2_sound_allowurl

Okay I found out how to do different pull requests. I'll do that instead of putting them all here.

Seems useful; its certainly a better designed approach than the 10 parameter behemoth function I've been using so far.
Example E2 code:
@name Water Effect Test
@persist Plays Water:effect

if(first()) {
    Water = effect()
    Water:setOrigin(entity():pos())
    Water:setNormal(vec(0,0,1))
    Water:setScale(350)
    Plays = 4
}
if(Plays > 0) {
    Plays--
    Water:play("watersplash")
    interval(250)
}

Just a thought, it might be handy to return this in each of the modifier functions to enable method chaining, which could shorten that init function to:
if(first()) {
    Water = effect():setOrigin(entity():pos()):setNormal(vec(0,0,1)):setScale(350)
    Plays = 4
}

Either way I approve.

Sure, I can do that real quick.

Just one concern. Wouldn't it be pretty easy to FPS rape everyone on the server with this? There are currently no limits to how fast you can spam effects. Maybe you should consider adding a replenishing buffer, like many other E2 extensions have. What it does is this
* On E2 initialize, set a number to its max amount.
* Every time you use the play function, subtract one from this number.
* If the number is zero, don't allow the user to use the play function.
* Every interval (pick a good interval, maybe 0.1 seconds or something), add 1 to the number, until it reaches its max amount again.

This allows you to create many effects at the same time, until the number is zero, or it allows you to create effects at a steady rate, as long as you do it at the same rate as the number is increased.
Here's an example of this: https://github.com/wiremod/wire/blob/master/lua/entities/gmod_wire_expression2/core/debug.lua#L15 (lines 15 to 55) This implementation, used by most print functions in E2, also allows the users to set their own max limit clientside, but since effect creation is serverside, I don't think you could do that in this case, unless there's a way to create effects for specific players.

Should also add a large ops cost to ef:play(), possibly 30 to bring it in line with propSpawn.

propSpawn should have a cost of at least 300. Can't believe it's so low.

I could make the limit for individual e2s, same way the sound plugin is.

Whether or not it's per-E2 or per player is a good point. I suppose it's up to you, but just remember that If you make it per-E2, then you can get twice as many effects by having twice as many E2s.

Yeah, I think per-player makes more sense.

Okay I can do that. Should I change the sound system to be the same way?


Automatic installation device

On devices with more than one hdd /dev/sda and /dev/sdb (and other devices) are prone to change places. It's also a pain to have one MachineRegistration for /dev/sda and one for /dev/nvme0.
I propose to make the device field in MachineRegistration.elemental.install optional (or default to 'auto') and pick the smallest block device that is larger than our minimum required specs.
If a device is specified it will be used, keeping backwards compatibility.

If device enumeration isn't consistent, that's a (kernel/udev) bug or a hardware problem.

@kkaempf agreed, but if we can make a simple workaround that also brings other benefits it sounds like a win-win to me.

Yes this is something we could try to improve. Some time ago I was thinking about that and was wondering if shouldn't we follow udev rules spirit for that, I mean, letting users define some sort of selection criteria to find a matching device. Never matured any of these ideas though.
I think having some guess with an static criteria is hard as it will always leave some use cases behind. Having some way to let users define the criteria would be the key IMHO, but it might not be easy to find an easy and nice way to express it.

I think having some guess with an static criteria is hard as it will always leave some use cases behind. Having some way to let users define the criteria would be the key IMHO, but it might not be easy to find an easy and nice way to express it.

@davidcassany  Yep, I would also like to see something like a dynamic ruleset for picking the device, probably a bit like the nodeSelectorTerms but with block-device specific operations instead.
I will sketch a bit on how that might look!

Here is an example to pick any of /dev/sda and /dev/vda:
apiVersion: elemental.cattle.io/v1beta1
kind: MachineRegistration
metadata:
  name: fire-nodes
  namespace: fleet-default
spec:
  config:
    elemental:
      install:
        deviceSelectorTerms:
          - key: blockdevice.name
            operator: In
            values:
            - /dev/sda
            - /dev/vda

And here to pick the first block-device with size between 20GB and 800GB:
apiVersion: elemental.cattle.io/v1beta1
kind: MachineRegistration
metadata:
  name: fire-nodes
  namespace: fleet-default
spec:
  config:
    elemental:
      install:
        deviceSelectorTerms:
          - key: blockdevice.size
            operator: Lt
            values:
            - 800Gb
          - key: blockdevice.size
            operator: Gt
            values:
            - 20Gb

If device enumeration isn't consistent, that's a (kernel/udev) bug or a hardware problem.

Well, turns out I was wrong.
Device enumeration is expected to be inconsistent since device detection happens in parallel and not sequentially. 😕

I'm in for adding some flexibility in the selection of the block device. But honestly a selector looks overkill to me... let's keep the config simple!
While the "auto" looks dangerous to me, it is a better option for usage simplicity.
Since the "device" field is already a string, why not using comma separated values, e.g., "sda,vda" ? That would give all the needed flexibility without going into more elaborated rules based on the storage details (and for the implementation, if we deal with it in the elemental-registration binary should be as easy as checking a device file exists).

Here's a concrete use case that's not covered by comma separated values:

A machine has two storage devices, one small (for OS), one large (for storage)
Devices appear as /dev/sda and /dev/sdb - but due to the parallel probing, you don't know which is which

Using /dev/disk/by-path/... is currently the only way for deterministic device names.
deviceSelectorTerms seems to be a good solution.

I see, good point. Does that mean that users will be required to have the deviceSelector thing mandatory or would that be another option? If mandatory, I would argue we are sacrificing simplicity to support corner cases.

I would say we keep the device field but make it optional, and if device is not set and deviceSelector is an empty array we just let it pick the first block-device it finds.


Why is there an offset

I love your tool, however this offset is annoying. I have to change it in the gradient_icons.dart, but of course when someone else gets my code they have to change it too.
Can you make this option toggleable? Why is there an offset in the first place? I think your tool works best when just replacing an icon without any layout changes

Thank you for connecting we will fix this in new update or version 👍
On Fri, 19 Jan 2024 at 3:04 AM, KonstSchob @.***> wrote:

I love your tool, however this offset is annoying. I have to change it in
the gradient_icons.dart, but of course when someone else gets my code they
have to change it too.
Can you make this option toggleable? Why is there an offset in the first
place? I think your tool works best when just replacing an icon without any
layout changes
grafik.png (view on web)
https://github.com/MohamedAshraf701/gradient-icon/assets/151203822/d24895d4-8f1f-4377-9d0a-2f22cf7b43e2
—
Reply to this email directly, view it on GitHub
https://github.com/MohamedAshraf701/gradient-icon/issues/4, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AWCCCSUHYHWX3CQUZZXEV5DYPGIP7AVCNFSM6AAAAABCA6Z7MSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA4DSMBYGMZTINQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks a lot


Add Basic Development Mode and Patient Context

Added ngrx library to project.  Coded State, Actions, Reducers and Effects.
Got Developer mode working where you can select between Betsy and Patricia.
The ngrx Selectors are not working.  As a workaround, selecting directly from the Ngrx store in the patient-selector component.
Need to figure out why selectors not working.

Fixed issue Ngrx store.  Had to define the State in /reducers/index.ts as follows using the "topLevel".   Ngrx was adding topLevel when creating the store, but the coding (from examples prior to latest release of Ngrx) was not taking into account this extra layer of the State hierarchy.
export interface State {
topLevel: {
patient: fromPatient.State;
devmode: fromDevMode.State;
};
}
Creating separate feature story to incoporate Http services into the project.
This feature focused on adding Ngrx plumbing to the project.

I referenced this link in working on this story:
https://kimsereyblog.blogspot.com/2017/07/managing-global-state-with-ngrx-store.html


[fix][test] Fix flaky test RawReaderTest

Motivation
https://github.com/apache/pulsar/actions/runs/5877094886/job/15945999791?pr=20990
Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Codecov Report

Merging #21008 (84beb1f) into master (0cb1c78) will increase coverage by 3.35%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master   #21008      +/-   ##
============================================
+ Coverage     33.56%   36.92%   +3.35%
- Complexity    12198    12238      +40
============================================
  Files          1621     1698      +77
  Lines        126970   129864    +2894
  Branches      13857    14162     +305
============================================
+ Hits          42618    47949    +5331
+ Misses        78748    75591    -3157
- Partials       5604     6324     +720

Flag
Coverage Δ

inttests
24.23% <ø> (-0.01%)
:arrow_down:

systests
25.15% <ø> (?)

unittests
32.18% <ø> (+0.09%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 412 files with indirect coverage changes


Reduce _move_columns_to_obs and move_to_obs to one method

Is your feature request related to a problem? Please describe.
I noticed that there are two methods for moving to obs: _move_columns_to_obs and move_to_obs that are slightly different: the former one is used for internal purposes and the latter is exposed via API to users.
Describe the solution you would like
I would like to merge those two methods to a single one to reduce redundancy in the code. move_to_obs would then accept not only an AnnData object, but a pd.DataFrame.

Good question! I mean from a users perspective it wouldn't make muche sense to move sth. to obs since there is no obs in a pandas dataframe.
That said, I'd prefer having two functions (one accepting anndata, the other one a pandas dataframe), but let them share their body (a single function that does the moving) with a quick type check in both functions to ensure they are of type anndata/pandas dataframe.
Sounds good? Any other ideas?

Yes, please go for it :)

@Imipenem what about dispatching this function? Once for AnnData and once for Pandas DF?

Turns out that the Pandas DF method is only used once and therefore singledispatching this and making it public would only increase the complexity. Hence, I removed the Pandas version.


chore: backport all vim.health api calls for v0.9

:tada: This PR is included in version 2.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


I have added one python based project.

Description 📜
I have built a human-like calculator that responds to text prompts using Python.

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise, Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations, and regular explanatory films are all possibilities, etc)
[ ] Doc#umentation (Content Creation in the form of codes or tutorials)
[x] Other (If you choose other, Please mention changes below)
[x] Project added

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] JavaScript_#Domain
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[x] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm a GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@adityabisoi Close this pr


Trigger an update to the build-image-index task

This task was never added to the trusted tasks.

Look for any open pull requests in the repository with the title "e2e-tests update" and
see if there are recent e2e-tests updates that will be applicable to your change.

/retest


Refactor type hint in '_get_coils' func

Breaking change
Proposed change
Replaced with the correct type hint (Generator) in the '_get_coils' function to improve maintainability and better readable code.
Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[ ] New feature (which adds functionality to an existing integration)
[ ] Deprecation (breaking change to happen in the future)
[ ] Breaking change (fix/feature causing existing functionality to break)
[x] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:

Checklist

[x] The code change is tested and works locally.
[x] Local tests pass. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[ ] I have followed the development checklist
[ ] I have followed the perfect PR recommendations
[x] The code has been formatted using Black (black --fast homeassistant tests)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly.
Updated and included derived files by running: python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt.
Updated by running python3 -m script.gen_requirements_all.
[ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
[ ] Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

[ ] I have reviewed two other open pull requests in this repository.

Waled Mohammad Group 10
Rule 2: This issue/code smell is relevant because its a type hint issue and can lead to potential errors in code maintenance.
Rule 3: First was Generator library imported and then replaced with the correct type hint (Generator) in the '_get_coils'. This improves the maintainability and now its more readable code due to the right type hint has been assigned to the function.

looks good


(doc) Add documention of new hook rule

Description Of Changes
This adds a new page for the upcoming rule about not allowing non-hook
packages taking a dependency on a hook package.
Motivation and Context
We need to document all rules that we have in package validator.
Testing

[x] I have previewed these changes using the Docker Container or another method before submitting this pull request.

Change Types Made

[ ] Minor documentation fix (typos etc.).
[ ] Major documentation change (refactoring, reformatting or adding documentation to existing page).
[x] New documentation page added.
[ ] The change I have made should have a video added, and I have raised an issue for this.

Change Checklist

[ ] Requires a change to menu structure (top or left-hand side)/
[ ] Menu structure has been updated

Related Issue

https://app.clickup.com/t/8687xvy17
https://app.clickup.com/t/8687xvxxy

@AdmiringWorm thanks for getting that added!


Implement initial-resize-group-by feature

https://github.com/topolvm/pvc-autoresizer/pull/174

@cupnes Thank you for your investigation. I let ct install test work only when the source branch name starts with bump-chart-.

I will squash the commits after I get approve from all of reviewers.
Please do not merge it until that.


Add note on Autopilot admission controller

What does this PR do?
Using the admission controller in socket mode will not work, updating public docs to note this.
Motivation
Work on this ticket: https://datadoghq.atlassian.net/browse/CONS-5299; we were able to reproduce issues with the admission controller when using socket mode.
Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] If the PR doesn't need to be tested during QA, please add a qa/skip-qa label.

lgtm, but plz address Cecilia's comments

Applied suggestion, merging.
Thanks


Implement select.encode

Following discussion on https://github.com/reklatsmasters/binary-data/issues/35

Pull Request Test Coverage Report for Build 220

12 of 12 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 90.78%

Totals

Change from base Build 218:
0.1%

Covered Lines:
767

Relevant Lines:
827

💛  - Coveralls

travis-ci tests are green - https://travis-ci.org/github/reklatsmasters/binary-data/builds/704240220

this might help unblock the wrong travis status message - https://github.com/travis-ci/travis-ci/issues/10204


Being able to create new sheets using templates

Hi, We are looking to use carbone in one of our projects and are going through evaluating different features, We are trying to customize the number of sheets and sheet names using the templates but not sure how to do this, Can someone please help if you think this is achievable or we are trying something that is not in scope for the library

Hi @JVaghela-Fintech,
The behavior of creating dynamic sheets is possible but it's not documented yet.
The use of variables is the only way to generate new sheets on ODS files. Before continuing, checkout documentation about Carbone variables.
You have to define 2 variables on the template:
{#sheet1 = d.fruits[i].name}
{#sheet2 = d.fruits[i+1].name}

then insert on the sheet names navigator the variables:
{$sheet1} // for sheet number 1
{$sheet2}  // for sheet number 2

During the rendering, CarboneJS replace the variables by the repetition markers {d.fruits[i].name}and {d.fruits[i+1].name} to generate new sheets that inherit content from the first sheet.
Following this text is an example of an ODS template, a JSON data, the javascript and a screenshot of the generated document. The goal is to generate sheets with fruit nutritional values.
template.ods:

The JSON data to inject, data.json:
{
  "fruits": [
    {
      "name": "apple",
      "nutrients": [
        {
          "type": "energy",
          "value": 52,
          "unit": "Kcal"
        },
        {
          "type": "Carbohydrates",
          "value": 13.81,
          "unit": "g"
        },
        {
          "type": "Protein",
          "value": 0.26,
          "unit": "g"
        },
        {
          "type": "Fats",
          "value": 0.17,
          "unit": "g"
        },
        {
          "type": "Cholesterol",
          "value": 0,
          "unit": "g"
        },
        {
          "type": "Dietary Fiber",
          "value": 2.4,
          "unit": "g"
        }
      ]
    },
    {
      "name": "banana",
      "nutrients": [
        {
          "type": "energy",
          "value": 89,
          "unit": "Kcal"
        },
        {
          "type": "Carbohydrates",
          "value": 22.84,
          "unit": "g"
        },
        {
          "type": "Protein",
          "value": 1.09,
          "unit": "g"
        },
        {
          "type": "Fats",
          "value": 0.33,
          "unit": "g"
        },
        {
          "type": "Cholesterol",
          "value": 0,
          "unit": "g"
        },
        {
          "type": "Dietary Fiber",
          "value": 2.6,
          "unit": "g"
        }
      ]
    },
    {
      "name": "strawberry",
      "nutrients": [
        {
          "type": "energy",
          "value": 53,
          "unit": "Kcal"
        },
        {
          "type": "Carbohydrates",
          "value": 12.75,
          "unit": "g"
        },
        {
          "type": "Protein",
          "value": 1.11,
          "unit": "g"
        },
        {
          "type": "Fats",
          "value": 0.33,
          "unit": "g"
        },
        {
          "type": "Cholesterol",
          "value": 0,
          "unit": "g"
        },
        {
          "type": "Dietary Fiber",
          "value": 3.3,
          "unit": "g"
        }
      ]
    }
  ]
}

index.js
const fs = require("fs");
const carbone = require("carbone");

// function to generate reports
const generateFileWithCarbone = (templateFileName, buildFileName, data) => {
  carbone.render(templateFileName, data,  async (err, result) => {
    if (err) {
      return console.error(err);
    }
    await fs.writeFileSync(buildFileName, result);
  });
};

// Files
const FILE_INPUT = "./template.ods";
const FILE_OUTPUT = "./result.ods";

// Data to inject
const DATA = require("./data.json");

// Call the function
generateFileWithCarbone(FILE_INPUT, FILE_OUTPUT, DATA);

Finally the generated document. result.ods:

Reach me if you need help.

@steevepay Thank you very much for the explanation.


Make "Illustration of SPR" figure MCMC

This needs Numbers-at-age from M and Numbers-at-age from Z, which are not extracted by the extra-mcmc code. We need to do this for 2023 or this plot won't work anymore.
It is currently MLE from 2021.

Fixed for 2022 in #834 with c5ef0886.

I believe Chris has fixed this with 3c85451cd01bad074f6345881fd40e5bda73a3df
So closing now as I remove the ** in the caption.


document deploying a controller on Linux

@dovholuknf Feedback from @emoscardini was move the "Bring Your Own State" section to a separate page instead of cramming everything into one page.

On the whole, there feels like a fair bit of reference-type-words mixed throughout that probably don't belong in a guide-type document. Would you go through and find anything that feels reference-ish and unecessary and remove? IPC Agent is not necessary to understand, SNI and ALPN seem to be reference-related not guide-related to me. There might be other stuff that could be trimmed out as well but as I read through those sorts of things are striking me as not really being inline with what a 'guide' is. some bit of it, is necessary but this should focus more bringing it up and how, not the details under it. it does make me feel like there's some kind of related reference material here that could be exctracted and moved to reference

aggregating changes in #820


How long does it take to train this model?

How long does it take to train this model with 32 V100?

About 4 days.

So quick! I am waiting for you ckpt with more training data & video!

About 4 days.

4 days for train 128128 resolution(imagenet_lfqgan_128_L.yaml) or 256 256(imagenet_lfqgan_256_L.yaml)?


Refactor CellIndex, FastList and Formula

Replace assert check with non-null constraints
Avoid unnecessary use of late keyword
Avoid unnecessary use of private variables

Looks good, but there seem to be some breaking changes to the API?
Could you document them?

Where should I document them?


Magnetometer examples broken

All 3 mag3110 examples appear to block before being able to get and print data.
#0  0x00004180 in <nrf51_hal::i2c::I2c<nrf51::TWI1>>::send_byte (self=0x20003e9c, byte=0x20003d7c "\020\000")
    at /home/droogmic/.cargo/registry/src/github.com-1ecc6299db9ec823/nrf51-hal-0.5.1/src/i2c.rs:88
#1  0x00004ae2 in <nrf51_hal::i2c::I2c<nrf51::TWI1> as embedded_hal::blocking::i2c::Write>::write (self=0x20003e9c, addr=14, bytes=...)
    at /home/droogmic/.cargo/registry/src/github.com-1ecc6299db9ec823/nrf51-hal-0.5.1/src/i2c.rs:213
#2  0x0000091a in <mag3110::Mag3110<I2C>>::write_register (self=0x20003e9c, reg=mag3110::CTRL_REG1, byte=0)
    at /home/droogmic/.cargo/registry/src/github.com-1ecc6299db9ec823/mag3110-0.1.3/src/lib.rs:154
#3  0x000007ac in <mag3110::Mag3110<I2C>>::stop_sampling (self=0x20003e9c) at /home/droogmic/.cargo/registry/src/github.com-1ecc6299db9ec823/mag3110-0.1.3/src/lib.rs:140
#4  0x00000946 in <mag3110::Mag3110<I2C>>::set_sampling_mode (self=0x20003e9c, dr=mag3110::HZ80, ov=mag3110::OV16)
    at /home/droogmic/.cargo/registry/src/github.com-1ecc6299db9ec823/mag3110-0.1.3/src/lib.rs:110
#5  0x00000bda in <mag3110::Mag3110<I2C>>::new (i2c=...) at /home/droogmic/.cargo/registry/src/github.com-1ecc6299db9ec823/mag3110-0.1.3/src/lib.rs:103
#6  0x00001706 in i2c_haldriver_printmagserial::main::{{closure}} (cs=0x20003fcc) at examples/i2c_haldriver_printmagserial.rs:80
#7  0x0000285c in cortex_m::interrupt::free (f=...) at /home/droogmic/.cargo/registry/src/github.com-1ecc6299db9ec823/cortex-m-0.5.2/src/interrupt.rs:69
#8  0x00001242 in i2c_haldriver_printmagserial::main () at examples/i2c_haldriver_printmagserial.rs:47

Can't confirm. They all work "fine"(*) for me.
(*) The only one that kind of makes sense is the: i2c_hal_printmagserial, the i2c_haldriver_printmagserial waits for an interrupt which never occurs while i2c_direct_printmagserialdelivers exactly one (wonky) result.

Interesting, I wonder what is different.

I have the same problem. First time I ran i2c_hal_printmagserial got only Welcome to the magnetometer reader! Then I tried to play with I2C addresses, and  I started to get some values, but all of them were the same and never changed despite of moving the board
for example, if i change this
            let _ = i2c.write(0x19, &[0x33, 0x32]);
//            let _ = i2c.write(0xE, &[0x11, 0x7f]);
and this
 if i2c.write_read(0x19, &[0x32], &mut data).is_ok() {
I get this
x: 13107, y: 13107, z: 13107
x: 13107, y: 13107, z: 13107
x: 13107, y: 13107, z: 13107
x: 13107, y: 13107, z: 13107
x: 13107, y: 13107, z: 13107
x: 13107, y: 13107, z: 13107
x: 13107, y: 13107, z: 13107
x: 13107, y: 13107, z: 13107
x: 13107, y: 13107, z: 13107
x: 13107, y: 13107, z: 13107
x: 13107, y: 13107, z: 13107
x: 13107, y: 13107, z: 13107
x: 13107, y: 13107, z: 13107
x: 13107, y: 13107, z: 13107
x: 13107, y: 13107, z: 13107
x: 13107, y: 13107, z: 13107       ```

I find it rather likely that this is caused by different sensors used in different revisions of the board. Rev 1.3 (and below) use MAG3110 (cf. https://tech.microbit.org/hardware/previous-revision/), while Rev 1.5 uses LSM303AGR and potentially in the future FXOS8700CQ, cf. https://tech.microbit.org/hardware/

I still can’t get, why I have always the same values? Am I doing something wrong? I am using addresses from here https://tech.microbit.org/hardware/i2c/

The driver you're using is MAG3110 only, I don't know how much the LSM303AGR register interface differs but it's highly likely to not work with the unmodified MAG3110 driver.

there is now a magnetometer example that runs on V1.5 and V2


chore: 🔧 change to new synergy icon

Pull Request
📖 Description

🎫 Issues
Closes #578

👩💻 Reviewer Notes

📑 Test Plan

✅ DoD

[x] I have tested my changes manually.
[x] I have added automatic tests for my changes (unit- and visual regression tests).
[x] I have updated the project documentation to reflect my changes (e.g. CHANGELOG, Storybook, ...).
[x] I have added documentation to the DaVinci migration guide (if need be)
[x] I have made sure to follow the projects coding and contribution guides.
[x] I have made sure that the bundle size has changed appropriately.
[x] I have validated that there are no accessibility errors.
[x] I have used design tokens instead of fix css values

Can somebody check my latest changes please :)

I have just updated the branch to the latest version and fixed a broken link. Otherwise, technically I would be fine. @klaarseSICKAG Do you want to have another look for the adjusted wording (e.g. in the Vision chapters).


Buffer size mismatch in tensorflow/lite/kernels/stablehlo_pad.cc

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
2.16
Custom code
No
OS platform and distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
Pointers this->edge_pad_low_, this->edge_pad_high_, this->interior_pad_ reference memory locations of size 48 bytes as they point to arrays of int64_t of kMaxDims elements, where kMaxDims == 6:
https://github.com/tensorflow/tensorflow/blob/bd1c3bf880a103425cfa5dd49ab3d1bf84857d13/tensorflow/lite/kernels/stablehlo_pad.cc#L36
https://github.com/tensorflow/tensorflow/blob/bd1c3bf880a103425cfa5dd49ab3d1bf84857d13/tensorflow/lite/kernels/stablehlo_pad.cc#L221-L224
These pointers are passed as parameters to function 'memcpy' with a size parameter TFLITE_STABLEHLO_PAD_PARAMS_MAX_DIMENSION_COUNT * 8 that is always equal to 64 bytes:
https://github.com/tensorflow/tensorflow/blob/bd1c3bf880a103425cfa5dd49ab3d1bf84857d13/tensorflow/lite/kernels/stablehlo_pad.cc#L98-L108
https://github.com/tensorflow/tensorflow/blob/b19a54c0d9739f9c548222d625c1413628b3a43f/tensorflow/lite/core/c/builtin_op_data.h#L38
This can lead to a buffer overflow.
It's worth noting that in tensorflow/lite/core/api/flatbuffer_conversions_test.cc
var kMaxDims is explicitly assigned the value of the constant TFLITE_STABLEHLO_PAD_PARAMS_MAX_DIMENSION_COUNT:
https://github.com/tensorflow/tensorflow/blob/b19a54c0d9739f9c548222d625c1413628b3a43f/tensorflow/lite/core/api/flatbuffer_conversions_test.cc#L737-L738
Standalone code to reproduce the issue
Bug was found by Svace static analysis tool.

Relevant log output
No response

Will wait for PR review to see how that goes.


build-support/go: fix eval of vendorSha256 accesses

Description of changes
Before the change there was no way to poll for presence of vendorSha256 attribute:
$ nix-instantiate --strict --eval --expr 'with import ./. {}; _3mux.vendorSha256 or "no hash"'
   error: attribute 'vendorSha256' missing
      292|     passthru = passthru // { inherit go goModules vendorHash; } // { inherit (args') vendorSha256; };
         |                                                                     ^

After the change the poll happens as expected:
$ nix-instantiate --strict --eval --expr 'with import ./. {}; _3mux.vendorSha256 or "no hash"'
"no hash"

(cherry picked from commit a1422a7f8f12b68e307b92b7daa254f412e9ff96)

still having errors of
Run cat <<EOF
The nixos-* and nixpkgs-* branches are pushed to by the channel
release script and should not be merged into directly.
Please target the equivalent release-* branch or master instead.
Error: Process completed with exit code 1.


:bug: config_url is saved as part of the config during netboot

Kairos version:
1.5
CPU architecture, OS, and Version:

Describe the bug
When doing automated installs from network, for instance with AuroraBoot, the cloud config file used for bootstrapping it is passed as a config_url, which ends up to be saved into the /oem/90_custom.yaml file. The problem is that if we kill AuroraBoot, kairos will try to fetch the URL again and fail, preventing the agent to start
To Reproduce
Use auroraboot, like the following, and after the machine installation completes,  kill the auroraboot process:
cat <<EOF | docker run --rm -i --net host quay.io/kairos/auroraboot \
                    --cloud-config - \
                    --set "container_image=quay.io/kairos/kairos-opensuse-leap:v1.5.1-k3sv1.21.14-k3s1"
#cloud-config
install:
 auto: true
 device: "auto"
 reboot: true

hostname: kairoslab-{{ trunc 4 .MachineID }}
users:
- name: kairos
  passwd: kairos
  ssh_authorized_keys:
  # Replace with your github user and un-comment the line below:
  - github:mudler
  - github:mauromorales

p2p:
 # Disabling DHT makes co-ordination to discover nodes only in the local network
 disable_dht: true #Enabled by default

 # network_token is the shared secret used by the nodes to co-ordinate with p2p.
 # Setting a network token implies auto.enable = true.
 # To disable, just set auto.enable = false
 network_token: "YOUR_TOKEN_HERE"
EOF

To workaround, add config_url to the supplied cloud config, like so:
cat <<EOF | docker run --rm -i --net host quay.io/kairos/auroraboot \
                    --cloud-config - \
                    --set "container_image=quay.io/kairos/kairos-opensuse-leap:v1.5.1-k3sv1.21.14-k3s1"
#cloud-config

config_url: ""
#### WORKAROUND ^^^

install:
 auto: true
 device: "auto"
 reboot: true

hostname: kairoslab-{{ trunc 4 .MachineID }}
users:
- name: kairos
  passwd: kairos
  ssh_authorized_keys:
  # Replace with your github user and un-comment the line below:
  - github:mudler
  - github:mauromorales

p2p:
 # Disabling DHT makes co-ordination to discover nodes only in the local network
 disable_dht: true #Enabled by default

 # network_token is the shared secret used by the nodes to co-ordinate with p2p.
 # Setting a network token implies auto.enable = true.
 # To disable, just set auto.enable = false
 network_token: "YOUR_TOKEN_HERE"
EOF

Expected behavior
The kairos-agent should at least ignore such errors and print a warning instead so the deployment is not stopped. If there is something going wrong, a user having issues will already look into logs.
Open question What about the config_url by itself? does it make sense to save it at all from the cmdline?

ux as it doesn't block anything (workaround is known)

As agreed during planning, we will make the agent print a warning when the config_url is not accessible and continue booting.
Ideally it can retry a couple of times before giving up.
Ideally, these kind of warnings should be printed in the boot messages (not journalctl and rd.shell hacks should be needed) but we will do that on a separate issue because it also affects other kind of failures (e.g. bad kcrypt configuration etc).

I tried to reproduce it but although the auroraboot server is not reachable, system eventually boots. These are the relevant logs from sudo journaldctl :
Feb 21 13:38:18 localhost systemd-logind[1353]: Removed session 1.
Feb 21 13:38:19 localhost kairos-agent[1545]: could not merge configs: All attempts fail:
Feb 21 13:38:19 localhost kairos-agent[1545]: #1: Get "http://<IP_ADDRESS>:8090/_/file?name=other-1": dial tcp <IP_ADDRESS>:8090: connect: connection refused
Feb 21 13:38:19 localhost kairos-agent[1545]: #2: Get "http://<IP_ADDRESS>:8090/_/file?name=other-1": dial tcp <IP_ADDRESS>:8090: connect: connection refused
Feb 21 13:38:19 localhost kairos-agent[1545]: #3: Get "http://<IP_ADDRESS>:8090/_/file?name=other-1": dial tcp <IP_ADDRESS>:8090: connect: connection refused
Feb 21 13:38:19 localhost kairos-agent[1545]: #4: Get "http://<IP_ADDRESS>:8090/_/file?name=other-1": dial tcp <IP_ADDRESS>:8090: connect: connection refused
Feb 21 13:38:19 localhost kairos-agent[1545]: #5: Get "http://<IP_ADDRESS>:8090/_/file?name=other-1": dial tcp <IP_ADDRESS>:8090: connect: connection refused
Feb 21 13:38:19 localhost kairos-agent[1545]: #6: Get "http://<IP_ADDRESS>:8090/_/file?name=other-1": dial tcp <IP_ADDRESS>:8090: connect: connection refused
Feb 21 13:38:19 localhost kairos-agent[1545]: #7: Get "http://<IP_ADDRESS>:8090/_/file?name=other-1": dial tcp <IP_ADDRESS>:8090: connect: connection refused
Feb 21 13:38:19 localhost kairos-agent[1545]: #8: Get "http://<IP_ADDRESS>:8090/_/file?name=other-1": dial tcp <IP_ADDRESS>:8090: connect: connection refused
Feb 21 13:38:19 localhost kairos-agent[1545]: #9: Get "http://<IP_ADDRESS>:8090/_/file?name=other-1": dial tcp <IP_ADDRESS>:8090: connect: connection refused
Feb 21 13:38:19 localhost kairos-agent[1545]: #10: Get "http://<IP_ADDRESS>:8090/_/file?name=other-1": dial tcp <IP_ADDRESS>:8090: connect: connection refused
Feb 21 13:38:19 localhost systemd[1]: kairos-agent.service: Main process exited, code=exited, status=1/FAILURE
Feb 21 13:38:19 localhost systemd[1]: kairos-agent.service: Failed with result 'exit-code'.
Feb 21 13:38:24 localhost systemd[1]: kairos-agent.service: Scheduled restart job, restart counter is at 1.
Feb 21 13:38:24 localhost systemd[1]: Stopped kairos agent.
Feb 21 13:38:24 localhost systemd[1]: Started kairos agent.

It tried 10 times and then quit.

The system boots, but the service exists, so it doesn't end up the first-boot deployment code

The fix was simple: https://github.com/kairos-io/kairos/tree/885-flexible-config-url
but I'll check if we can have a test for this.

A manual test for now:
[  OK  ] Finished Record Runlevel Change in UTMP.

The config.yaml:
#cloud-config

config_url: https://doesnotexist.com/testestest

users:
- name: "kairos"
  passwd: "kairos"
  lock_passwd: true
  groups: "admin"
  ssh_authorized_keys:
  - github:jimmykarily

and the command was: kairos-agent manual-install --device auto config.yaml
I will try to create an automated test for this now.


update vpc version for AWS stacks

The specified version for the terraform vpc provider in AWS stacks uses an older version
This causes issues later on when using deprecated parameters, namely the arguments "enable_classiclink" and "enable_classiclink_dns_support" are no longer used.
This caused the AWS stacks not to work, but with this change they do

Thank you so much for the catch and the fix, @MarkusSagen! LGTM 🚀


FIR designer remez exchange algorithm

Incorporate this into the filter designer
https://github.com/hooleyhoop/HooleyBits/blob/master/FFT Explore/remez-19980711/remez.c

I have C++ code for Remez from spuc library, that I could probably import over/into Pothos. I'll take a look after finishing up IIR stuff

Cool, sounds good!

I've pushed support for Remez filters in FIRDesigner. New parameter weight was also added. Please take a look and try out. Let me know if there are issues

Done. And with your recent rewrite, the FIR designer is even more elegant. Thanks @audiofilter