Tree Grid breaks if we change recid to something else

Short description
Chrome breaks (oh snap!) if we expand then collapse a tree row when:

a) there are a large number of records (200?)
b) we change the recid field to something else

What is current behavior

set recid to use some other field.
expand a row (with a large number of children)
try to collapse the row.

result -> Chrome crashes
If we use recid then it works fine
What is desired behaviour
It should work with recid field changed to something else
Link to jsfidle/codepan with sample code
FAILS:     http://jsfiddle.net/32Ljbomz/1/
WORKS: http://jsfiddle.net/32Ljbomz/2/
Steps to reproduce or sample
Expand Motzart -> Franson -> Franson
Try to collapse - using recid works, using id fails.

here is an example where recid has been changed, but it works (I have reduced the number of records)
http://jsfiddle.net/32Ljbomz/3/

Hello @peterchavasse.
I have the same problem when expanding/collapsing rows with large number of records, did you find a solution?

I tried all 3 jsfiddles and all 3 seem to work. I expanded all possible nested items. When it fails, what exactly happens. Also, I did not understand what it means "fails". Also, recid must be unique. If it is not unique, it will not select record right.

Hello @vitmalina
Thanks for replying.
I will try to be more clear : if you try on the first fiddle to expand and collapse the node Motzart->Franson->Franson your navigator will crash (out of memory). It might be due to the fact that ids are not unique in this case as you mentionned.
However, I got the exact same problem on my app (I use the last version of your library) on big nodes ( +-500 entry and deeply nested). The navigator falls into out of memory when you try to collapse nodes with lot of datas. All my ids are different in my case.
I finally got access to the entry flux and changing "id" into "recid" solved my problem.
I hope it's more clear.
Great work on this library!

Hi,
Sorry for late reply.  The failure was chrome crashing - with oh, Snap! message. Like antoninmeunier, I was also able to change "id" in to "recid" and all was well.
Having said that, I see the jsfiddles are both working - I am wondering if it was a specific issue in a nightly build some time ago, which has been fixed. @antoninmeunier  - are you using the latest nightly or even official 1.5?
Anyway @vitmalina , great to know you are still looking - the grid control is amazing!  I see 1.5 is now official - that is good news.
Have you got a roadmap of new features/ideas?

Hello,
My version is w2ui 1.5.x (nightly). This is a build downloaded from the website 4 months ago I would say

@peterchavasse new features mostly around new things that JS/CSS can do now. I want to rewrite with let arrorw functions flex grid. Some styling visual updates. Will drop support for old browsers. I don't think there will be too many "new" features, just making current features use modern JS/CSS

Since looks like it is resolved. I am closing the issue

Cannot reproduce if I provide unique ids for the children: http://jsfiddle.net/3sf1wknq/
Closing issue. Feel free to re-open if the issue still exists.


Overflow and segmentation fault

On nyquist we get segmentation fault on the very first simulation. (regressiontest.sh)
On shannon, the same code gives an overflow warning and subsequent error exception trying to convert NaN to to int; this happens on the first point mass image.

The overflow happens in centreImage()

The cause seems to be the new code to transfer floating point cv::Mat to python.  See #102

The problem was the wrong bitwise operation, changing OR to AND solved the problem.


Updated files

Unique theme has been given and clear button specifies 'clear'. Fixes #28

No thanks, this is not a web site.  Any changes to button theme have to occur across hundreds of repositories.


linux-51 is dead.

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
linux-51 is dead.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

Machine was hung and require power recycle to restore machine.


Remove some special casing of vendoring, update from prometheus master

Tests are failing. Will wait until they are green before reviewing.


Elements created using ng-Repeat in datepicker have the wrong parent hierarchy

I need to display a uib-datepicker in a dropdown for various custom directives; i.e., entering of a date/time OR a date range w/ various shortcuts. I need the dropdown to have auto-close="outsideClick". When I open the dropdown and select a date the first time, the dropdown remains open as expected. However, if I then click on another date, the dropdown automatically closes. After this any time the dropdown is opened and a date is clicked, it is automatically closed.
The problem is the check for the dropdownElement[0].contains is failing. It looks like when the ng-repeat data model changes, if you trace the evt.target.parentElement hierarchy, it is no longer contained by the dropdown element.
var dropdownElement = openScope.getDropdownElement();
if (evt && openScope.getAutoClose() === 'outsideClick' &&
dropdownElement && dropdownElement[0].contains(evt.target)) {
return;
}
Here is a plunker:
https://plnkr.co/edit/lqpt2UBIP1xkmziQxcV1?p=preview

closing this as this project is no longer being maintained, per the README and the ISSUE_TEMPLATE.


Apple M1 support

Quoracle does not work out of the box on the new Apple M1s because it depends on numpy which does not have M1 support. After trying various workaround (including running terminal through rosetta), this solution worked for me.
No action needed, I just wanted to document this workaround until numpy is updated.

Oh wow, thanks for figuring this out and finding a solution Heidi! Hopefully numpy gets updated soon.
Outside of some code that makes plots, quoracle only really uses numpy in one spot, so we can probably rewrite the code a little to use pure Python and remove numpy as a dependency entirely. I'll add that to my TODO list :)

In commits 6bb6eb29143827d0db2701426d3a14a2cde69278, 9f0532a7d53f96dc25bdcde9c56d2fea9bfa6f4f, and a4dfc6f7515f332b5eafd32f737778120c822ea0, I removed the dependency on numpy. We still depend on matplotlib, though, and I think matplotlib depends on numpy, so trying to pip install quoracle on an Apple M1 will probably still fail I'm guessing. For that though, I think we just have to wait for things to get fixed upstream :)

Agreed, it should just be a matter of time before numpy is updated for M1 :)


Fix problems deleting layers

Solve PR #930 and #931 and other problems.

Solve PR #930 and #931 and other problems.

LGTM


Hiding html characters

https://plnkr.co/edit/gWFKX34woucJRgDrJCdd?p=preview
It is hiding html paragraph tags in text box.
How can I show them.

This is the material 2 rep. Your Plunker is about 1.4. Doesn't seem related.


[super_native_extensions] compiler error

* Where:
Script '/Users/hatemragap/flutter/.pub-cache/hosted/pub.dartlang.org/super_native_extensions-0.1.6/toolbox/gradle/plugin.gradle' line: 129

* What went wrong:
A problem occurred evaluating script.
> Failed to apply plugin class 'ToolboxPlugin'.
   > It is too late to set ndkVersion
     It has already been read to configure this project.
     Consider either moving this call to be during evaluation,
     or using the variant API.

How to set the ndk

Did you read the "Android Support" section of the readme?

I reopened this. The error message should be better. Instead of trying to set ndkVersion (which clearly fails) toolbox should fail with error message.

Should be fixed in cargokit.


Support for nodejs12.x runtime

Hi @antmanler,
As refunc aims to provide all AWS runtimes -- I was wondering if support could be added for nodejs12.x:
https://aws.amazon.com/blogs/compute/node-js-12-x-runtime-now-available-in-aws-lambda/

Refunc embrace the aws lambda ecosystem, you can just use the lambci/docker-lambda's image to run nodejs12.x. This repo also really base on lambci/docker-lambda.

nodejs12.x runtime already support by https://github.com/refunc/lambda-runtimes/pull/3.


EltwiseReduceMod fails on EltwiseReduceModAVX512 operation with a modulus that is between 51 and 52 bits.

The library does not reduce properly for any modulus between 51 and 52 bits. See this test:
TEST(ReduceFailure, ReduceFailure) {
std::vector<uint64_t> tst = {
41834706795195925,
4670328046076965,
17760383643480343,
49435670237278413,
24379914680392825,
33362919182756282,
14501318335168678,
31183658415687847
};
auto mod =<PHONE_NUMBER>175441;
auto chk  = tst;
intel::hexl::EltwiseReduceMod(chk.data(), tst.data(), tst.size(),
mod,
mod, 1);
auto exp = tst;
for (auto & elem : exp) {
elem %= mod;
}
ASSERT_EQ(exp, chk);
}
This is just an example. I have tried several different moduli of the same bit width and several different inputs. The reduction function does not match the modulus operation.

Hello @jcalafato1 I have reproduced this issue with a modulus size of 52 bits but not 51 bits. Do you have a 51 bits case that you can share? I think this is a limitation of the IFMA algorithm on big inputs.

Hey @joserochh thanks for getting back to me, is a fix available or is it just a limitation of the library? I have a workaround in my projects to prevent 52 bit moduli from being generated right now, but I'd rather not have the restriction.
I also misspoke, it is a 52 bit number that doesn't work, so no worries with 51 bits.

There will be a fix so you don't need to avoid 52 bit moduli. In the worst case, the library will have to use AVX512-DQ intrinsic functions instead of AVX512-IFMA for this scenario. When input values are not that big, say only up to 4 times modulus value (input_mod_factor), then reduction works fine with 52 bit moduli on IFMA as the algorithm is way simpler.

Sounds good, thanks! I'll watch for a new version.

Fix is on dev branch.


Lua blocks cannot coexist with proxy_pass, only proxy_pass is executed when proxy_pass is present

when I write lua at stream, I found lua blocks cannot coexist with proxy_pass, only proxy_pass is executed when proxy_pass is present.
Env:
openresty-<IP_ADDRESS>
stream-lua-nginx-module-0.0.8
Code:
stream {      lua_add_variable $url;      server {         listen 8000;         set $url "ddddddddddddd";         content_by_lua_block {             ngx.say("========== Start to ");             ngx.say(ngx.var.url);             ngx.var.url="<IP_ADDRESS>:22";             ngx.say(ngx.var.url);         }         proxy_pass $url;     } }

Do you found any solution I 've similar problem #295.
Please resolve if you can.


Fix and re-enable CI build of Linux / LLVM 3.8

The Linux / LLVM 3.8 matrix item in the CI build was disabled in #674 because it was broken.
We need to fix that build item and re-enable it.

This is working again. Closing.


Leaves behind an unused manifest file

Love this plugin!! Thank you for making this. I just noticed one issue and that is it leaves behind the manifest.json file in the build directory. It would really nice if it cleaned up the file after it had injected the contents into index.

Great that it comes to use, @outdooricon!
I've added the config option { dropAsset: true } (defaults to false). Instructions in readme are updated.
Published to npm as v0.2.1.

awesome, thank you!


Multiple Notifications are sent to Slack

Hi,
I just tried using this library and in a suite of 17 tests I got 4 notifications, seems like a progress notifications.

I'd like to have only one single notification at the end of all tests. Any way I can configure that?

Hi @Benzer1406 ,
Basically 1 pytest exec command generates 1 report.
Could you please share you command line ?

@ArseniyAntonov Thanks for the answer.
The command I run is the following: pytest -n 3 --dist=loadscope code_admin --slack_hook=https://hooks.slack.com/services/T03KN3..... --slack_username="Daily Pipeline"
Running that command yield in the following notifications:

Running it with many modules like this:
pytest -n 3 --dist=loadscope code_admin api user devices --slack_hook=https://hooks.slack.com/services/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 --slack_username="Daily Pipeline"
Results in:

Seems like there are always 4 notifications triggered.
Here a screenshot of my command line (just took out the sensitive data):

Looks like the issue with Xdist test repot, i will check it and try to fix till the EOW.
Am i understand it right that
single command :
pytest -n3 ...
generates 4 reports?

Yes, that's what's happening to me. One single command pytest -n3 ... results in 4 reports.
The command line screenshot is a summary of the two commands I ran before. So in total I got 8 reports from these 2 commands.
Thanks for the help!

Will fix it till the EOW.
It's annoying bug )

@Benzer1406 Bug fixed and released, please update pytest-slack up to 2.2.4 version.

@ArseniyAntonov  Thanks a lot man! Receive one single notification now! Thanks for the quick fix.


Collection vs Generator

Hi,
First of all, congrats for the outstanding work with Anserini project. I am a bit confused about the difference between some indexing parameters. In concrete, collection and generator.
To my understanding, I need to set collection to the dataset that I am using, in my case C4Collection, but I don't know if it needs a specific generator or it can be anyone, e.g., DefaultLuceneDocumentGenerator or WarcGenerator.
I would appreaciate any help, and thank you again.
Best,
Marcos

A Collection is responsible for reading the text from disk in a particular format (JSON, WARC, TREC, etc.).
A Generator is responsible for generating a Lucene document, e.g., populating the right fields to index.

Over time, we've tried to make DefaultLuceneDocumentGenerator "do the right thing", so in most case, if you use it, it'll be okay. Every time we get a new corpus in a different format, though, we need to build a new Collection.
Specifically, in our case, to index C4, I use:
nohup sh ./target/appassembler/bin/IndexCollection -collection C4Collection \
 -generator C4Generator -threads 96 -input /store/collections/c4/en.clean-train-json \
 -index indexes/c4-all.compact -storeRaw >& logs/log.c4.compact &

It is because we're indexing "custom" fields for C4.
Make sense?

Dear @lintool,
Thank you very much for your clear explanation. It makes perfect sense. However, I was wondering if DefaultLuceneDocumentGenerator will also populate the right fields to index for the C4 collection.
Best,
Marcos

Mostly, since C4 generator subclasses default Lucene generator:
https://github.com/castorini/anserini/blob/master/src/main/java/io/anserini/index/generator/C4Generator.java#L53
You won't be able to fetch based on URLs and time, I think.

Perfect, thanks for your assistance :) I am closing the issue


test IO Demobug

Test
ID: #0002
URL: http://www.test.io/
Further instructions: MyText
Bug
ID: #0002
Feature: no feature
Date: 2023-01-24 12:08:58 UTC
Tester: 2whitney_romaguera
Steps

This is a demo Bug from the test IO system. If you see this bug, the export interface has been successfully implemented to your bug tracker and is ready for use.

Actual result
Necessitatibus possimus in. Debitis quos quo. Reprehenderit doloribus iure.
Expected result
Ullam doloremque id. Sed sed et. Dignissimos maiores ut.
Attachments
Screenshots

deleted user: Quibusdam at accusantium. Qui et omnis. Rerum eveniet dolore. Et eius nobis. Non aut aut. Et vero quam. Rerum aut nihil.


ESP32 BT-HID Mouse arduino

HI, I used the sketch you attached BLE_Mouse.ino and it is working fine with android phone but its not working when connected to windows10. Please can you help on this
BLE_Mouse.ino.txt

@senthilkumarh
Could you tell me what are the hardware connection for this HID mouse?
I just uploaded this code to my ESP32 device. But I don't know how to what are the pin connection for ESP32, arduino and othre requie hardware.
Could you tell me soe steps for this which can be appreciated.
looking forward to your response.

Just read code:
const int button1Pin = 39;     // the number of the pushbutton pin
const int button2Pin = 38;     // the number of the pushbutton pin
const int ledPin =     5;      // the number of the LED pin

I have m5stack with 3 buttons connected to pins 37, 38, 39. I am using button 1 (pin 39) and button 2 (pin 38) to test and move mouse cursor.


Feature request: Delete runs interactively in guild compare

If possible, I think it would be very useful to be able to delete runs from inside guild compare

Thank you! Great idea - we'll make this happen for 0.7!

Update - this will unfortunately not happen in 0.7. But this remains on the roadmap.


tmEval lazy is slow

I've noticed that even with the fastest reduction strategy available - lazy - running tmEval within the TemplateMonad is still much slower than vm_compute. I have an example for which tmEval lazy takes around 22 sec, and vm_compute finishes in 4.5 sec.
Is there a way of using vm_compute for reduction?

That's to be expected indeed. We should indeed have a way to call vm_compute and not just vm_cast.


Add AsRef<[u64]> trait bound to GroupAffine/GroupProjective ScalarField

This allows mul to take in an AsRef<[u64]>, and allows one to naturally multiply by a scalar field element.
This does restrict the set of fields that can be scalar fields, since it would have to use u64 as its data type, precluding dalek-style f32 backend optimizations for scalar fields. (Dalek has an f32 backend for the base field, not the scalar field AFAIK) This restriction does feel natural in the elliptic curve context, since there you really do want the bit-wise representation of a scalar field element for scalar multiplication. (At least until we consider endomorphism optimizations) The base field can still have an arbitrary representation for efficient MSM's.
In the case of doing an elliptic curve based SNARK, and wanting to do FFTs with the fastest scalar field representation, you would have to do a conversion between the FFT/polynomial representation and the ScalarField representation. This conversion would have to exist regardless of API decision. However before, you could just push this conversion into the Into<BigInt> method. I suspect this would be handled by making the field representation you implement polynomials with also implement Into
So doing this would be a trade-off between allowing easy scalar multiplications by an integer at the expense of making non-u64 backed implementations of scalar fields (for FFT/polynomial arithmetic speedups) more complex to integrate into elliptic curve based polynomial commitments.
I think this is a fine trade-off to make right now until we have preliminary understandings of how much of a speedup we stand to gain from non-u64 based arithmetic in scalar fields. (We can learn this independently, since you can still use FFTs with any FFTField)
This issue is a transcription of the result of a conversation with @Pratyush.

(Dalek has an f32 backend for the base field, not the scalar field AFAIK)
It does have it for the scalar field as well.


multiregion AKS clusters is just a concept?

[Enter feedback here]
multiregion AKS clusters is just a concept?
In essential, 2+ standalone AKS instance in different region with some shared region-local resource like container registry.
Does my understanding correct?

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

ID: af2806b1-1264-2775-4cce-083303e75b49
Version Independent ID: 68218fb5-2335-183a-8469-9101a2d8a0ef
Content: AKS baseline for multiregion clusters - Azure Architecture Center
Content Source: docs/reference-architectures/containers/aks-multi-region/aks-multi-cluster.yml
Service: architecture-center
Sub-service: reference-architecture
GitHub Login: @martinekuan
Microsoft Alias: architectures

@JeffreyVIP
Thanks for your feedback! We will investigate and update as appropriate.

In essential, 2+ standalone AKS instance in different region with some shared region-local resource like container registry.
Does my understanding correct?

Yes, @JeffreyVIP, your understanding is correct. If you run into any issues while implementing this, feel free to post on the MS Q&A channel instead. Since we didn't determine any faulty steps/changes to this doc upon reviewing your feedback, we will now proceed to close this thread for now. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Renovate doesn't works with CRD directory

Describe the bug
CRD kustomization is not renovated.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Configuration (please complete the following information):

Kubernetes: [e.g. GKE]
Version [e.g. 22]

Additional context
Migrate to use CRDs charts:

Prometheus Operator CRDs: https://artifacthub.io/packages/helm/prometheus-community/prometheus-operator-crds
OpenTelemetry CRDs: https://github.com/open-telemetry/opentelemetry-helm-charts/issues/677
Certmanager CRDs: https://artifacthub.io/packages/helm/wiremind/cert-manager-crds

We try to use CRD Helml charts, so Renovate works fine with these


Unexpected type

The issue line here.
apply_gradients expects a list, but receives an iterator (from call to zip, which returns an iterator). Should we convert to list for Python 3 compatibility?

Hi, and thank you for the suggestion!  I had to refactor this method wholesale to be consistent with the latest version of gpflow, so I think this issue is moot, but if that's not the case, feel free to reopen and let us know.

Hi, and thank you for the suggestion!  I had to refactor this method wholesale to be consistent with the latest version of gpflow, so I think this issue is moot, but if that's not the case, feel free to reopen and let us know.


Fix typo and formats in README.md

Two things are changed.

Fix typo
Re-format for better readability

Coverage remained the same at 67.938% when pulling 892db037d38e662a4a5173f0e38a5334f4118281 on jung-hunsoo:patch-1 into 85ee14feed16ac7ce7827ac6bbdb10471c107141 on bitwalker:master.

Thanks!


Solved incompatibility issues for up to date libraries.

Solved some incompatibility issues for updated libraries.

Wanings popped up for h5py.File function without explicitly designate the access level. Add 'r'
hyperspy map function will convert namedtuple "IndexingResult" to np.ndarray. All the attributes are lost. Use np.recarray to solve this issue.

Hi @Taimin ,nice work! Do you think it is possible to make the hyperspy requirement optional since it is only used for a single statement? Last time I tried it, it is quite a beast to install, and I would like to avoid depending on it.

Hi @stefsmeets, indeed hypderspy has a lot of dependencies. I can have a look at hyperspy to see if it is possible to adapt Signal2D class to problematic.


Android 14 support

Android 14 is not out yet on the market but we can already get ready for it with the Android emulator.
I have tested awesome_notifications with it and it seems that it is kind of not working.
I sent notifications for the current time and most of them didn't arrive, one arrived in the next minute but the other didn't arrive at all.
This issue is in general test awesome_notifications for Android 14 and follows its status, not a specific bug.

The last version now supports Flutter 3.13, Android 14 and iOS 17. You just need to add the pubspec.yaml below:
  # Awesome plugins
  awesome_notifications_core: ^0.7.6 # use the latest available
  awesome_notifications: any # <- this version will be managed by core plugin
  awesome_notifications_fcm: any # <- this version will be managed by core plugin


Consider declaring Minimum Supported Rust Version

I noticed that with clippy for an older Rust release (warning: this expression creates a reference which is immediately dereferenced by the compiler):
#[derive(BinWrite)]
struct Foo {
    value: i32,
    value2: i32,
}

$ cargo +1.71 clippy
    Checking binrw-demo v0.1.0 (/home/marxin/Programming/binrw-demo)
warning: this expression creates a reference which is immediately dereferenced by the compiler
 --> src/main.rs:8:5
  |
8 |     value: i32,
  |     ^^^^^ help: change this to: `value`
  |
  = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow
  = note: `#[warn(clippy::needless_borrow)]` on by default

warning: this expression creates a reference which is immediately dereferenced by the compiler
 --> src/main.rs:9:5
  |
9 |     value2: i32,
  |     ^^^^^^ help: change this to: `value2`
  |
  = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow

Hi, thanks for your report! MSRV for binrw is already defined, and CI runs tests against the MSRV to make sure that binrw compiles and works correctly.
At this point I can’t justify ever spending time on fixing lints from old versions of clippy, so I’m going to close this ticket as ‘not planned’. Presumably there is some reason this code doesn’t emit warnings in newer versions, but I don’t have time to look and try to figure out why. However, if you do have the time, and you want to submit some patch that resolves the lints in the version of Rust you are using, without suppressing true positives in newer versions of Rust, and without adding extra dependencies (i.e. please don’t add some version detection library dependency just so old Rust versions don’t get warnings), please go for it. Thanks!

Thanks for the reply. Apparently, it's already fixed in clippy, so it does not make sense to investigate that further.


Color argument is wrong for noms cmd log

noms log --color command  does not do what the help says.  Turning color off should use 0 vs 2 according to the code. I can either change the help comment or change the logic. Which is preferred here ?
should work:
noms log --color 2 http://demo.noms.io/cli-tour::sf-film-locations
does work:
noms log --color 0 http://demo.noms.io/cli-tour::sf-film-locations
Happy to tackle this either way

@willhite is probably the right person to answer

I think the only thing that needs to change is the help message here. It look like '--color 0' forces the color off, and '--color 1' forces it to be on. That seems like the right behavior to me. Feel free to fix, @zcstarr

merged in https://github.com/attic-labs/noms/pull/2520


Sharing with Unet: spawned objects rotation and position based on user starting position

Project Summary
I basically have gotten the Sharing with unet example and added a different command to spawn an object into the scene as well as add a script to move the object around the scene. This works correctly when hosting with HoloLens and Unity editor as client.
Problem
The only problem I have is when I add another HoloLens as a client the spawned objects are offset in rotation and position based on where the client started the application in reference to the host. For example, if the host starts the application facing one way and the client faces 180 degrees in the opposite direction to start their application when they spawn an object it is offset by 180 degrees. Could this be something wrong on my end or something else entirely? Am I missing something?
Note
The players and text mesh import fine when starting the application and are in the correct position. It is only the spawned objects that their positions are offset.

Have you tried it without the editor connected? I had a similar problem recently at that seemed to help

Yes I have tried without the editor connected. It was just quicker to develop with deploying to only one HL instead of deploying to two every time. That's why I only noticed something wrong when I tried to do just the two HL.

I have a partner that is trying to do basically the same thing and we both have ran into this problem.

Are you using the sync object base class for you data model, or are you using the custom messages class?

neither. All I did is basically copy the net bullet prefab from the example except made it a capsule instead and got rid of the velocity so that it  just spawns in front of the player. The only thing that I can tell is that the clients anchor is not the same as the host's anchor. Because if I spawn the capsule with the same transform as the parent (Hologram Collection) after the import is completed it spawns on top of where the clients initial text mesh was located before import.

Oh sorry I read the issue wrong. I know nothing about the uNet stuff.

I found this on the Microsoft website:
After a GameObject is locked via the LockObject call, it will have a WorldAnchor which will keep it in the same physical position in the world, but it may be at a different location in the Unity coordinate space than other users.
Is there a way around this in order to make it have the same Unity coordinate space?
https://developer.microsoft.com/en-us/windows/mixed-reality/shared_experiences_in_unity

So I eventually figured this out, I feel like this was a noob mistake but, just like when calculating the player's transform via the shared anchor transform using inverse transform point. I had to do the same with the object that I spawned whenever I moved it.

That's great to hear!
So is this issue resolved then?

Yes


Prepare release 0.1.6

This PR prepares the release of OG-USA version 0.1.6.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 75.29%.  Consider uploading reports for the commit b19b5db to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #108      +/-   ##
==========================================
- Coverage   75.35%   75.29%   -0.06%
==========================================
  Files          11       11
  Lines         852      850       -2
==========================================
- Hits          642      640       -2
  Misses        210      210

Flag
Coverage Δ

unittests
75.29% <ø> (-0.06%)
:arrow_down:

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

@jdebacker.  I've gotten all the GH Action CI tests to pass except for Mac Python 3.9. I keep getting a Dask error of one of the workers quitting on the second-to-last test of test_get_micro_data.py::test_get_data[Reform].
All the tests in test_get_micro_data.py passed on my local machine, including the tests marked local. But my local machine is a Mac, and the ogusa-dev conda environment has Python 3.11, which is not tested in our CI.

@jdebacker.  The last worker that attempt to run the task was tcp://<IP_ADDRESS>:49266. Inspecting worker logs is often a good next step to diagnose what went wrong. For more information see https://distributed.dask.org/en/stable/killed.html.
../../../miniconda3/envs/ogusa-dev/lib/python3.9/site-packages/distributed/client.py:2232: KilledWorker
----------------------------- Captured stderr call -----------------------------
2024-05-08 16:42:21,876 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 1.76 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:42:27,405 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 1.68 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:42:35,874 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 1.65 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:42:45,901 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 1.79 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:42:52,863 - distributed.worker.memory - WARNING - Worker is at 80% memory usage. Pausing worker.  Process memory: 1.88 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:42:53,033 - distributed.worker.memory - WARNING - Worker is at 69% memory usage. Resuming worker. Process memory: 1.62 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:42:55,968 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 1.67 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:42:56,666 - distributed.worker.memory - WARNING - Worker is at 80% memory usage. Pausing worker.  Process memory: 1.87 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:42:56,967 - distributed.worker.memory - WARNING - Worker is at 76% memory usage. Resuming worker. Process memory: 1.79 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:43:03,868 - distributed.worker.memory - WARNING - Worker is at 80% memory usage. Pausing worker.  Process memory: 1.87 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:43:09,847 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 1.67 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:43:11,903 - distributed.worker.memory - WARNING - Worker is at 80% memory usage. Pausing worker.  Process memory: 1.87 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:43:11,949 - distributed.worker.memory - WARNING - Worker is at 79% memory usage. Resuming worker. Process memory: 1.84 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:43:12,246 - distributed.worker.memory - WARNING - Worker is at 80% memory usage. Pausing worker.  Process memory: 1.87 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:43:12,553 - distributed.worker.memory - WARNING - Worker is at 77% memory usage. Resuming worker. Process memory: 1.80 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:43:13,309 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 1.65 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:43:19,948 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 1.65 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:43:23,458 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 1.64 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:43:26,320 - distributed.worker.memory - WARNING - Worker is at 81% memory usage. Pausing worker.  Process memory: 1.89 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:43:33,866 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 1.49 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:43:36,648 - distributed.worker.memory - WARNING - Worker is at 89% memory usage. Pausing worker.  Process memory: 2.09 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:43:51,880 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 1.72 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:43:52,675 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 1.74 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:44:01,925 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 1.74 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:44:03,763 - distributed.worker.memory - WARNING - Worker is at 81% memory usage. Pausing worker.  Process memory: 1.91 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:44:13,740 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 1.74 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:44:14,064 - distributed.worker.memory - WARNING - Worker is at 82% memory usage. Pausing worker.  Process memory: 1.93 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:44:14,543 - distributed.worker.memory - WARNING - Worker is at 78% memory usage. Resuming worker. Process memory: 1.84 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:44:14,640 - distributed.worker.memory - WARNING - Worker is at 80% memory usage. Pausing worker.  Process memory: 1.89 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:44:14,899 - distributed.worker.memory - WARNING - Worker is at 71% memory usage. Resuming worker. Process memory: 1.67 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:44:14,977 - distributed.worker.memory - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker-memory.html#memory-not-released-back-to-the-os for more information. -- Unmanaged memory: 1.74 GiB -- Worker memory limit: 2.33 GiB
2024-05-08 16:44:15,287 - distributed.worker.memory - WARNING - Worker is at 80% memory usage. Pausing worker.  Process memory: 1.87 GiB -- Worker memory limit: 2.33 GiB
------------------------------ Captured log call -------------------------------
WARNING  distributed.nanny.memory:worker_memory.py:425 Worker tcp://<IP_ADDRESS>:49233 (pid=11391) exceeded 95% memory budget. Restarting...
INFO     distributed.nanny:nanny.py:804 Worker process 11391 was killed by signal 15
INFO     distributed.core:core.py:[10](https://github.com/PSLmodels/OG-USA/actions/runs/9004787859/job/24740433767?pr=108#step:5:11)29 Connection to tcp://<IP_ADDRESS>:49237 has been closed.
INFO     distributed.scheduler:scheduler.py:5204 Remove worker <WorkerState 'tcp://<IP_ADDRESS>:49233', name: 1, status: paused, memory: 0, processing: 2> (stimulus_id='handle-worker-cleanup-1715186585.977865')
WARNING  distributed.nanny:nanny.py:566 Restarting worker
INFO     distributed.scheduler:scheduler.py:4424 Register worker <WorkerState 'tcp://<IP_ADDRESS>:49260', name: 1, status: init, memory: 0, processing: 0>
INFO     distributed.scheduler:scheduler.py:5929 Starting worker compute stream, tcp://<IP_ADDRESS>:49260
INFO     distributed.core:core.py:1019 Starting established connection to tcp://<IP_ADDRESS>:49262
WARNING  distributed.nanny.memory:worker_memory.py:425 Worker tcp://<IP_ADDRESS>:49234 (pid=[11](https://github.com/PSLmodels/OG-USA/actions/runs/9004787859/job/24740433767?pr=108#step:5:12)392) exceeded 95% memory budget. Restarting...
INFO     distributed.nanny:nanny.py:804 Worker process 11392 was killed by signal 15
INFO     distributed.core:core.py:1029 Connection to tcp://[12](https://github.com/PSLmodels/OG-USA/actions/runs/9004787859/job/24740433767?pr=108#step:5:13)<IP_ADDRESS>:49238 has been closed.
INFO     distributed.scheduler:scheduler.py:5204 Remove worker <WorkerState 'tcp://<IP_ADDRESS>:49234', name: 2, status: paused, memory: 1, processing: 2> (stimulus_id='handle-worker-cleanup-1715186607.671854')
WARNING  distributed.scheduler:scheduler.py:5280 Removing worker 'tcp://<IP_ADDRESS>:49234' caused the cluster to lose already computed task(s), which will be recomputed elsewhere: {'taxcalc_advance-7d35ab75-dabd-4ece-957d-0957879a2ccc'} (stimulus_id='handle-worker-cleanup-1715186607.671854')
WARNING  distributed.nanny:nanny.py:566 Restarting worker
INFO     distributed.scheduler:scheduler.py:4424 Register worker <WorkerState 'tcp://<IP_ADDRESS>:49266', name: 2, status: init, memory: 0, processing: 0>
INFO     distributed.scheduler:scheduler.py:5929 Starting worker compute stream, tcp://<IP_ADDRESS>:49266
INFO     distributed.core:core.py:1019 Starting established connection to tcp://<IP_ADDRESS>:49268
WARNING  distributed.nanny.memory:worker_memory.py:425 Worker tcp://<IP_ADDRESS>:49251 (pid=[13](https://github.com/PSLmodels/OG-USA/actions/runs/9004787859/job/24740433767?pr=108#step:5:14)099) exceeded 95% memory budget. Restarting...
INFO     distributed.nanny:nanny.py:804 Worker process 13099 was killed by signal 15
INFO     distributed.core:core.py:1029 Connection to tcp://<IP_ADDRESS>:49253 has been closed.
INFO     distributed.scheduler:scheduler.py:5204 Remove worker <WorkerState 'tcp://<IP_ADDRESS>:49251', name: 0, status: paused, memory: 1, processing: 2> (stimulus_id='handle-worker-cleanup-1715186622.4045131')
WARNING  distributed.scheduler:scheduler.py:5280 Removing worker 'tcp://<IP_ADDRESS>:49251' caused the cluster to lose already computed task(s), which will be recomputed elsewhere: {'taxcalc_advance-7b151cc7-c9ac-42c3-a774-cbb782c9e6f8'} (stimulus_id='handle-worker-cleanup-1715186622.4045131')
WARNING  distributed.nanny:nanny.py:566 Restarting worker
INFO     distributed.scheduler:scheduler.py:4424 Register worker <WorkerState 'tcp://<IP_ADDRESS>:49272', name: 0, status: init, memory: 0, processing: 0>
INFO     distributed.scheduler:scheduler.py:5929 Starting worker compute stream, tcp://<IP_ADDRESS>:49272
INFO     distributed.core:core.py:1019 Starting established connection to tcp://<IP_ADDRESS>:49274
WARNING  distributed.nanny.memory:worker_memory.py:425 Worker tcp://<IP_ADDRESS>:49260 (pid=[14](https://github.com/PSLmodels/OG-USA/actions/runs/9004787859/job/24740433767?pr=108#step:5:15)391) exceeded 95% memory budget. Restarting...
INFO     distributed.core:core.py:1029 Connection to tcp://<IP_ADDRESS>:49262 has been closed.
INFO     distributed.scheduler:scheduler.py:5204 Remove worker <WorkerState 'tcp://<IP_ADDRESS>:49260', name: 1, status: paused, memory: 0, processing: 2> (stimulus_id='handle-worker-cleanup-17[15](https://github.com/PSLmodels/OG-USA/actions/runs/9004787859/job/24740433767?pr=108#step:5:16)186646.0573041')
INFO     distributed.nanny:nanny.py:804 Worker process 14391 was killed by signal 15
WARNING  distributed.nanny:nanny.py:566 Restarting worker
INFO     distributed.scheduler:scheduler.py:4424 Register worker <WorkerState 'tcp://<IP_ADDRESS>:49277', name: 1, status: init, memory: 0, processing: 0>
INFO     distributed.scheduler:scheduler.py:5929 Starting worker compute stream, tcp://<IP_ADDRESS>:49277
INFO     distributed.core:core.py:1019 Starting established connection to tcp://<IP_ADDRESS>:49279
WARNING  distributed.nanny.memory:worker_memory.py:425 Worker tcp://<IP_ADDRESS>:49266 (pid=14739) exceeded 95% memory budget. Restarting...
INFO     distributed.core:core.py:1029 Connection to tcp://<IP_ADDRESS>:49268 has been closed.
INFO     distributed.scheduler:scheduler.py:5204 Remove worker <WorkerState 'tcp://<IP_ADDRESS>:49266', name: 2, status: paused, memory: 0, processing: 2> (stimulus_id='handle-worker-cleanup-[17](https://github.com/PSLmodels/OG-USA/actions/runs/9004787859/job/24740433767?pr=108#step:5:18)15186656.506249')
ERROR    distributed.scheduler:scheduler.py:5259 Task taxcalc_advance-f47d516e-0d21-4d41-be0e-7d93d8be05fc marked as failed because 4 workers died while trying to run it
INFO     distributed.nanny:nanny.py:804 Worker process 14739 was killed by signal 15
WARNING  distributed.nanny:nanny.py:566 Restarting worker
=========================== short test summary info ============================
FAILED tests/test_get_micro_data.py::test_get_data[Reform] - distributed.scheduler.KilledWorker: Attempted to run task 'taxcalc_advance-f47d516e-0d21-4d41-be0e-7d93d8be05fc' on 4 different workers, but all those workers died while running it. The last worker that attempt to run the task was tcp://<IP_ADDRESS>:49266. Inspecting worker logs is often a good next step to diagnose what went wrong. For more information see https://distributed.dask.org/en/stable/killed.html.
===== 1 failed, 29 passed, 7 deselected, 66 warnings in 536.37s (0:08:56) ======

@jdebacker. I recommend that we stop testing Python 3.9 in build_and_test.yml and only test Python 3.10 and 3.11, as we do in OG-Core (see OG-Core build_and_test.yml line 29). I submitted a PR to your branch that makes these changes.

@jdebacker. Looks great. Thanks for this. Merging now.


Outparams are not utilized for all public methods that take them in as parameters?

Hopefully I'm misunderstanding, but I can't seem to get updates to my outParams to work when utilizing either the strong typed or dynamic QueryFromProcedure.
This is how I'm performing my call:
var db = new MightyOrm<MyType>(_connectionString);
var outParam = new
{
	TotalRecords = (long)0
};

var data = db.QueryFromProcedure("myProc",
	new
	{
		param.PageSize,
		param.Page,
	}, outParam);

Console.WriteLine(outParam.TotalRecords);

I would have expected the above outParam to be updated as a result of the execution of the stored procedure, but I'm not sure if that's actually happening.
I did see that QueryFromProcedure eventually gets to a method called CreateCommandWithParams:
public override DbCommand CreateCommandWithParams(
      string sql,
      object inParams = null,
      object outParams = null,
      object ioParams = null,
      object returnParams = null,
      bool isProcedure = false,
      DbConnection connection = null,
      params object[] args)
    {
      return this.CreateCommandWithParamsAndRowCountCheck(sql, inParams, outParams, ioParams, returnParams, isProcedure, connection, args).Item1;
    }

Where the return from CreateCommandWithParamsAndRowCountCheck is a value tuple, where item 2 is a boolean that indicates if out params are used.  In this particular method (CreateCommandWithParams) that flag is not used.
Drilling further into the code under a separate public method such as ExecuteProcedure, you eventually get to:
Tuple<DbCommand, bool> andRowCountCheck = this.CreateCommandWithParamsAndRowCountCheck(spName, inParams, outParams, ioParams, returnParams, true, (DbConnection) null, args);

Which actually makes use of the flag returned from the Tuple<DbCommand, bool> in:
if (andRowCountCheck.Item2)
        {
          // ISSUE: reference to a compiler-generated field
          if (MightyOrm<T>.\u003C\u003Eo__296.\u003C\u003Ep__0 == null)
          {
            // ISSUE: reference to a compiler-generated field
            MightyOrm<T>.\u003C\u003Eo__296.\u003C\u003Ep__0 = CallSite<Action<CallSite, MightyOrm<T>, int, object, object>>.Create(Microsoft.CSharp.RuntimeBinder.Binder.InvokeMember(CSharpBinderFlags.InvokeSimpleName | CSharpBinderFlags.ResultDiscarded, "AppendRowCountResults", (IEnumerable<Type>) null, typeof (MightyOrm<T>), (IEnumerable<CSharpArgumentInfo>) new CSharpArgumentInfo[4]
            {
              CSharpArgumentInfo.Create(CSharpArgumentInfoFlags.UseCompileTimeType, (string) null),
              CSharpArgumentInfo.Create(CSharpArgumentInfoFlags.UseCompileTimeType, (string) null),
              CSharpArgumentInfo.Create(CSharpArgumentInfoFlags.UseCompileTimeType, (string) null),
              CSharpArgumentInfo.Create(CSharpArgumentInfoFlags.None, (string) null)
            }));
          }
          // ISSUE: reference to a compiler-generated field
          // ISSUE: reference to a compiler-generated field
          MightyOrm<T>.\u003C\u003Eo__296.\u003C\u003Ep__0.Target((CallSite) MightyOrm<T>.\u003C\u003Eo__296.\u003C\u003Ep__0, this, num, outParams, obj);
        }

I'm having trouble understanding what the above call actually does, but I'm guessing it's involved with the actual population of the outParams object from OUTPUT parameters from the stored procedure?
The originally mentioned QueryFromProcedure does not seem to share this similar block of code, I'm only assuming that is why I'm not getting my outParams object populated.
Can you confirm this behavior? and is there a way to get around it?
In the end, I was trying to return a "total" row count via an output param declared @TotalRows BIGINT OUTPUT from my sp, using it in parallel with the strong typed QueryFromProcedure.
I have confirmed that:
declare @TotalRecords bigint
exec myProc
20, -- page size
1, -- page number
@TotalRecords OUTPUT
SELECT @TotalRecords

does in fact return me my value, but I have not had luck doing the same with QueryFromProcedure and using outParams.

Background: outParams can't be updated, as it's not officially supported to update members of an anonymous object (in C#... it IS in VB): https://stackoverflow.com/questions/17441420/how-to-set-value-for-property-of-an-anonymous-object .
So, for the purposes of a library which hopefully might get used other than by me... I decided not to directly modify outParams (as I did in my original SP params code which I wrote before ever encountering Massive).
So, if you Query, you get the query results but not the param results. If you Execute you get the param results, but not the query results.
It's a bit fiddly, but you can also get both. I need to document this in the documentation.
List<ImportantItem> GetItemsBelongingToParent(int parentId)
{
	List<ImportantItem> items;
	dynamic results;

	// this is the way to get query results AND output param results in Mighty
	using (var cmd = db.CreateCommandWithParams(
		"GetImportantItems",
		inParams: new { ParentID = parentId },
		returnParams: new { RETVAL = (int?)null },
		isProcedure: true
	))
	{
		// because Mighty/Massive always uses delayed execution (query never executed until you
		// enumerate the enumerable), we need to use .ToList() to force execution...
		items = db.Query(cmd).ToList();

		// ... _before_ reading back the param results
		// (this does not re-execute the command, it just gathers up the results)
		results = db.ResultsAsExpando(cmd);
	}

	if (results.RETVAL != 0)
	{
		throw new ApiNotFoundException($"ParentID={parentID} not found");
	}

	return items;
}

PS I'm looking into providing a .snupkg so that you can debug into Mighty.
 But, until I produce a .snupkg (or even when/if I have, if you'd prefer to debug into the debug-compiled version), it's up to you, but my favourite way to debug into OS projects is to clone a local copy and temporarily make my project which needs debugging depend directly on the local copy (checked out at the tag corresponding to the current release) instead of on the NuGet package - then you can step into the original code instead of release-version compiler-generated code.

Yeah I was planning on poking around with using a project reference of a clone rather than the nuget package for a bit, after having digested your response ;)
what is the difference between output params and return params? I don't know if I saw them defined. return params isn't just "the result sets" is it?

Background: outParams can't be updated, as it's not officially supported to update members of an anonymous object

But aren't you effectively updating them by inlining the creation of the anonymous object in your example? (though from the returnParams perspective rather than outParams?)
What about some sort of Wrapper<T> object that would allow for the additional return values to be just pushed onto the Wrapper as members, while keeping the T either the IEnumerable<T>, dynamic, or IEnumerable<dynamic> ? I guess I'm just hoping for an API and return that would allow me easy access to my SPs OUTPUT parameters, while still sticking with the strong typing of MyObjectType.
Also thanks for the update from #16, I was able to confirm that as working this morning (prior to realizing that my outParam was not getting its value updated :D)

I have now added the above instructions and example to the documentation 430ebd9a03bac09ce37a506c5fee37bb31e3d1f0

Oh gotcha, did not realize there was such a difference between:
returnParams: new { RETVAL = (int?)null }

and
var returnParam = new
{
   RETVAL = (int?)null
}
// ...
returnParams: returnParam

I had tried the former as well, but I guess this goes back to your comment from https://github.com/MightyOrm/Mighty/issues/18#issuecomment-590409939:

So, if you Query, you get the query results but not the param results. If you Execute you get the param results, but not the query results.

input, output, input-output and return parameter directions are defined by System.Data.Common, not by me - I just wrap 'em!
The return param gives a name to the value from RETURN n in SQL Server. The distinction as I recall makes less sense on some other DB platforms - but in any event these will do whatever they would do if you had manually created a DbParameter with the equivalent ParamaterDirection against the command, on the underlying driver.

Just from looking quickly, I don't think there is any important distinction between your two examples just above. What were you thinking is the difference?

Just from looking quickly, I don't think there is any important distinction between your two examples just above. What were you thinking is the difference?

This was in reference to anonymous objects not being able to be updated from your comment:

Background: outParams can't be updated, as it's not officially supported to update members of an anonymous object

is that (the updating of an anon object) not what is occurring in your sample code in the docs:
var db = new MightyOrm(connectionString);
dynamic result = db.ExecuteWithParams(
    "set @a = @b + 1",
    inParams: new { b = 1233 },
    outParams: new { a = 0 });
Assert.AreEqual(1234, result.a);

... nevermind, writing it out I know see the property "a" from the anon object has been projected onto the dynamic result, rather than from the anon object, in your Assert.

Yes, exactly!
In many ways I think this:
var db = new MightyOrm(connectionString);
var outObj = new new { a = 0 };
db.ExecuteWithParams(
    "set @a = @b + 1",
    inParams: new { b = 1233 },
    outParams: outObj);
Assert.AreEqual(1234, outObj.a);

would be a nicer UI - but even though it is possible to do this (I've done it, it works!) it's not officially supported, as it involves change the value of what is (ostensibly) a read-only property on outObj.

Sorry - one more thing - there is no reason at all not to slightly modify the example of query with params in order to use strong typing; that shouldn't need to be a worry.

Quick test to the reader (by which I mean, I made a mistake...! ;) ): What is the problem with the above nicer UI? Answer: It wouldn't be possible with Mighty/Massive queries anyway - since Massive/Mighty queries are always 'contracts' to do the underlying work, which won't actually access the db until you start to consume results.
So there's no way that the output, io and return params could be filled out immediately on return from a Query (even though they could from Execute) - at least, not without changing that pretty fundamental decision. So that nicer UI, while it is possible in the example I showed just above, couldn't actually be used where it matters (combining Mighty queries with params) anyway.
Equally, it wouldn't be possible to use C# 7 multiple return values, or a manual wrapper type, to combine out parameters into the return value from queries, for just the same reason (the query hasn't happened by the time we return, and won't happen at all until the IEnumerable is enumerated).
So - just to document it here! - that's another reason (along with the non-writeability of anonymous objects) why the approach now written up in the docs is pretty much required, I think.

Interesting... so I guess this brings me to a few questions:

For Query types, is there a reason for the method to include the outParams and returnParams at all? since they can be passed in, but not accessed?
Would it be possible for a new public method that has a Wrapper<T> that does what you mentioned in the docs and https://github.com/MightyOrm/Mighty/issues/18#issuecomment-590409939 ? I'm guessing what could be worked with would be limited, but perhaps something to the effects of:

public class QueryWithOutputWrapper<T>
{
   public T data { get; set; }
   public dynamic OutParam { get; set; }
   public dynamic ReturnParam { get; set; }
}

I saw your response come in while I was writing this, so perhaps my response is moot ;)

Equally, it wouldn't be possible to use C# 7 multiple return values, or a manual wrapper type, to combine out parameters into the return value from queries, for just the same reason (the query hasn't happened by the time we return, and won't happen at all until the IEnumerable is enumerated).

Ah I guess the nature of writing a wrapper would require no longer having a deferred execution, which seems to go against the library in general.
Would you be opposed to introducing perhaps an extension or static method, something that made it clear you are opting out of deferred execution for something like this?  If not, I can just write something for my own code.

For Query types, is there a reason for the method to include the outParams and returnParams at all? since they can be passed in, but not accessed?

Please, look carefully at https://github.com/MightyOrm/Mighty/issues/18#issuecomment-590409939 - they can be accessed!

For Query types, is there a reason for the method to include the outParams and returnParams at all? since they can be passed in, but not accessed?

Please, look carefully at #18 (comment) - they can be accessed!

Sorry sorry, I meant mutated, from the response:

So, if you Query, you get the query results but not the param results. If you Execute you get the param results, but not the query results.

Of course the updates you did to the documentation and https://github.com/MightyOrm/Mighty/issues/18#issuecomment-590409939 allow me to get the information i need.

Actually - catching up with what you meant! - for the variant of Query that doesn't take a DbCommand, it is true that output params can be passed in but can't be accessed, you're right. I tend to think of all the versions of Query as different versions of the 'the same thing', but yes you're right, there are specific variants that take these output params and yet, because you don't have a link to the underlying command afterwards, you can never read back the values.
In fact, it did occur to me whether or not I needed to include these in the API, but I thought that it was better to have a consistent API for everything which takes params, which always does include all the available types. The fact that they are present might - for instance - be required by what is being called; even when the user knows that they don't need the values. And if they DO need the values, they can use the more complex version which I've now documented.

for your and anyone else's info, this is what I ended up going with (heavily based on your https://github.com/MightyOrm/Mighty/issues/18#issuecomment-590409939, just an extension method).
public class MightyResultsWithExpando<T>
    {
        public List<T> Data { get; }
        public dynamic ResultsExpando { get; }

        public MightyResultsWithExpando(List<T> data, dynamic resultsExpando)
        {
            Data = data;
            ResultsExpando = resultsExpando;
        }
    }

public static class MightyOrmExtensionMethods
    {
        public static MightyResultsWithExpando<T> QueryWithExpando<T>(this MightyOrm<T> db,
            string sql, object inParams = null, object outParams = null, bool isProcedure = true)
            where T : class, new()
        {
            var items = new List<T>();
            dynamic resultsExpando;

            using (var cmd = db.CreateCommandWithParams(sql, inParams: inParams, outParams: outParams, isProcedure: isProcedure))
            {
                items = db.Query(cmd).ToList();
                resultsExpando = db.ResultsAsExpando(cmd);
            }

            return new MightyResultsWithExpando<T>(items, resultsExpando);
        }
    }

Obviously the above is specifically for using the strongly typed query from proc, expecting multiple results, and placing the dynamic into a property that can be accessed via the caller.
To bring it all home from the opening of the issue, the calling code now looks like:
var db = new MightyOrm<MyType>(_connectionString);

var result = db.QueryWithExpando("myProc",
    new
    {
        param.PageSize,
        param.Page,
    },
    new
    {
        totalRecords = (long)0
     });

var data = result.Data; // strongly typed List<MyType>

Console.WriteLine((long)result.ResultsExpando.totalRecords);

That does look neat. Nice job. Hmmm.... processing.
It is certainly more convenient - for when you do need this. I guess I thought that that wouldn't be very often for most people... but I admit that I do use the long-hand solution in my current work project (the 'dogfooding' project) from time to time. If guess anyone who uses stored procedures a lot (I think not many people do, even if they 'should' 😉 !) is likely to need this a non-zero amount.


Add custom breadcrumbs in theme

As the content of sql reference is generated dynamically, it has no breadcrumbs. Modify the theme, to provide default breadcrumbs if none is set


Windows support?

I've been using z on both Linux and Mac. Indispensable. Would be nice to have support for Windows. Perhaps as .bat, or at least .ps1 (powershell).

Just found https://github.com/vincpa/z which seems a good PowerShell fork.
BTW Thanks for "z", using it for years on my Mac.


Add support for multiple apps

service.ts shares container, node and instance between usages. This causes problems if the plugin is installed on multiple apps. e.g.:
import { createApp } from 'vue'
import { VueMountable } from 'vue-mountable'
import App from './App.vue'

const app = createApp(App)
app.use(VueMountable)
app.provide('msg', 'app1')
app.mount('#app')

const app2 = createApp(App)
app2.use(VueMountable)
app2.provide('msg', 'app2')
app2.mount('#app2')

The functions provided by useComponent will then be bound to the second app in both cases. So, for example, attempting to inject the msg from inside a component mounted by VueMountable will always show app2, irrespective of which app it is in.

Thanks for reporting this! Havent looked into multiple instance support by now, but should be fairly easy to resolve!

fixed with version v0.0.5


RFC: Show Specific Major restriction and timeline

More clear Major restriction Info
For a course like the one below has a specific major restriction:

Time Line of restriction release
I think it is better to include a TIMELINE of when I can register for this class and also show on the Antalmanac result the current acceptable major or school.

Adding profile setting - Major/School
For every user, they can choose the major and school they are in, and it will help to determine the register time for every class

Scraping would be hard but I think we could include links to these pages for each school somewhere on our site. But, it's a lot of work to track down the links for every single school. Maybe only implement this for school of ICS classes? I'm gonna look at the statistics for class searches to see if any other departments are really popular.

Most schools will have this information as part of their comment in WebSOC, which we display. I think that searching all the school websites would be an excessive PITA.


I have registered a package under

Hi,
I update the package for run on 0.8 and have registered it with bower under purescript-csv-rk so you can register yours under purescript-csv still.
Would you be so kind to accept the pull request (if its up to your liking of course) and the register your package?
best regards
Robert

As per the PR comments, sorry for the delay.
I've registered purescript-csv on bower. Happy to add you as collaborator if that would be useful, but I should be more responsive now.

Closing this as PR has been accepted and package registered as suggested.


How to ignore file:/// paths?

Hi
I am trying to add this action on the https://github.com/GitCredentialManager/git-credential-manager project.
The project includes some HTML files that are auto-generated by build tools that contain references to the local filesystem using paths like file:///....
Of course these links fail for the link checker.
On https://github.com/GitCredentialManager/git-credential-manager/pull/700 see the "Lint documentation / Check for broken links (pull_request)" job.
I have tried using --exclude-path "file:///" (See https://github.com/GitCredentialManager/git-credential-manager/pull/700/commits/7304c593522d5fb70b63d846178815399bb3588a) but it has not had the desired affect - probably I am not using it correctly.
How can I tell Lychee to ignore such paths without ignoring the whole file?
Thanks!

I think I misunderstood the purpose of the --exclude-path argument; it is for the setting of files within the repo that should not be checked rather than setting a path link within any file that it should ignore.
Instead I have tried adding a .lycheeignore file with the regex `file:///.*
(https://github.com/GitCredentialManager/git-credential-manager/pull/700/commits/3a8767caf7c8419717693acc355e29d5447175ae)

Alternatively lychee --scheme http https -- example.com.


Remove dead code from MetricsContainer

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[*] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[*] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[*] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[*] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @tgroh
CC: @pabloem

Jenkins failure seems unrelated: https://builds.apache.org/job/beam_PreCommit_MavenVerify/org.apache.beam$beam-runners-apex/5034/testReport/junit/org.apache.beam.runners.apex.translation/ParDoBoundTranslatorTest/testAssertionFailure/


Custom wake-words and open source projects

Porcupine seems to be more targeted towards companies than open source projects and I was curious if there are going to be ways for open source projects to acquire custom wake-words for all (in my case specifically raspberry) platforms.
Given that the only way of acquiring such wake-words currently is through the "Contact Enterprise Team"-Form I assume those don't come cheap.

The license section clearly states what is available to open-source. Please check here https://github.com/Picovoice/Porcupine#license

Not really... It says:

...for non-commercial and evaluation purposes.

As such I was hopeful buuut I get the message...

What happens when personal custom keyword model expires? Is it still usable after 30 days non-commercially?


Bottom Navigation Bar - iOS v8 default selected tab

I'm having some issues with BottomNavigationBar when using v8 on iOS, it does not select a default tab and sometimes it actually crashes my app with a related error.

Can you reproduce it with one of the demo apps?

Yeah, just run the vue demo. It uses "tns-ios": "6.5.3" by default so the problem doesn't exist. Switch to "@nativescript/ios": "7.0.5" and the problem will be there under the Bottom Navigation demo. It doesn't crash, but the problem is there (there is no default selected tab).

I think this is related to https://github.com/nativescript-community/ui-material-components/issues/198
It doesn't work for me either on iOS (doesn't select first tab by default) and now I'm pretty sure it has to do something with tns-ios 6.5.3


addressing Ignored files in subdirectories not being ignored

By expanding the file via the calling path, we can match more clearly the file as it is specified in the ignore files.
https://github.com/abdoohossamm/djcompiler/issues/14

Additionally fixing a file copy error: https://github.com/abdoohossamm/djcompiler/issues/16


Clarify Waypoint: Nest an Anchor Element Description Text

Added some clarification to the position of the new p tag in Waypoint: Nest an Anchor Element within a Paragraph description text.  For some reason some users were adding it to the end of the HTML which broke one of the tests in a way that seemed unrelated to position.
Tested locally.
Closes #4426

:+1:


MAINT: documentation and metadata update for repo fork

Also:

enable tests for all supported Python version
add setup.py develop and setup.py bdist_wheel support

3.5 tests failing on no nose available, will fix. Also need to figure out why the tests run twice.

Okay, this passes now except for the added pep8/pyflakes test which needs gh-74 to pass.

Don't merge this one yet. The PyPi access rights got resolved, so it's now clear that we'll continue under the PyWavelets name.

This is good to go now.

Thanks, all comments addressed in last commit.


Claim: Tenant Expulsion

Description
As a user, I would like the system to predict whether or not tenant expulsion is justified
Scope of Work

[x] Create supervised learning algorithm benchmark for evaluating predictions
[x] Implement supervised learning algorithm that can evaluate whether or not tenant expulsion is justified based on facts present in the case .
[x] Extract using regex, or similar technique whether or not the tenant was expulsed in a specific case.

Demo requirement

The user selects the facts that are relevant to their case
The user sends the facts to the system
The system displays "Tenant expulsion is justified" or "Tenant expulsion is not justified"

Acceptance Criteria

The user is able perform demo steps
The F1 score of the supervised learning algorithm is >50%.

Documentation, files, diagrams, etc. relating to this feature:
Url, books, etc.
Changes:

[Optional]

This is covered by lease termination.

Prediction
f1

additional_indemnity_date
[ 0.87275506  0.87743835]

additional_indemnity_money
[ 0.87868732  0.74466434]

declares_housing_inhabitable
[ 0.999875  0.      ]

declares_resiliation_is_correct
[ 0.95337609  0.69552941]

orders_expulsion
[ 0.97162192  0.9619883 ]

orders_immediate_execution
[ 0.91473297  0.81991443]

orders_resiliation
[ 0.97318436  0.9659671 ]

orders_tenant_pay_first_of_month
[ 0.99673981  0.        ]

rejects_landlord_demand
[ 0.98689956  0.5255814 ]

rejects_tenant_demand
[ 0.98617865  0.42245989]

tenant_ordered_to_pay_landlord
[ 0.72910864  0.68399675]

tenant_ordered_to_pay_landlord_legal_fees
[ 0.80152357  0.69338422]

it's a different category @mihaiqc .

Was not integrated with NLP. Need to go over fact specifics with Sam prior to integration.

@Samuel-Campbell I understand, contextually speaking it shouldn't be.
The outcome is the same. You can't NOT be expelled out of the apartment if your lease is terminated in court.
So I don't understand the purpose of this category. It makes little sense to me and I have no idea how to differentiate it from lease termination in the problem category classifier.

This will likely not require any additional work once #186 is merged. The changes in that PR will make it so that any outcome returned from a prediction will be shown to the user.
As I understand it this is simply an add-on outcome, thus it is already covered by the "orders_resiliation" outcome being mapped to the "lease_termination" claim category.


Resize container images

Add support for virtual appliance resize in container images.

We need to test this with one 5.4.6 as an issue regarding this was solved here.

Not on 5.4.6, we need OpenNebula 5.4.7.
Basic algorithm:
if loop_device is beeing used:
- "losetup -c loopdev"
resize2fs "block"


Theme inheritance with Bootstrap Framework

Hey, it is not possible to inherit variables like $primary from my custom theme. Also the bootstrap mixins/function don't have to be in variables. Every theme need to have two entrypoints:

Load Variables
Load Mixins/Bootstrap and Shopware Custom Classes

in theme.json it have to be like:
{"style-variables": {   "@Storefront":,   "Resources/frontend/style/variables.scss" }}
and
{"style-base": {   "@Storefront":,   "Resources/frontend/style/base.scss" }}
This is just one of many possible suggestions to fix this Problem. It would be also be enought to re-split the script-inludes in Storefront to two entrypoints (variables, base or main), so i could include them from my custom Style.

In my case i didnt notice, that the variables of the storefront also override the plugin scss. In other cases i need to use the BS mixins in my plugin scss, so i can't wait to include the storefronts style at last.
So now the question is: should i copy the whole style setup from the storefront or should i define a own include-order in my theme - what is more complex?
i will try out some cases and reopen this issue again then.


[rookie] getRenderPanel() in humble

I have the below code snippets where I wish to init the ViewportMouseEvent before passing into void UpdateNodePosition::processMouseEvent(rviz_common::ViewportMouseEvent& event).
Question: How do I getRenderPanel() in humble? I have tried several ways and I dont see such function in the repo. Thanks!

Hi @h3ngy1ng, What type of RViz plugin are you creating? Have you seen this guide? https://github.com/ros2/rviz/blob/rolling/docs/plugin_development.md . Please ask follow up questions on https://robotics.stackexchange.com/?tags=ros
If you're creating a Display plugin you can use this->context_->getViewManager()->getRenderPanel()
In the future, please post text instead of pictures or screenshots of text. It makes it easier for others with the same question to find this issue in the future.


Session Manager Plugin in docker container along with AWS CLI on my local machine

Hi team,
I've built the docker image with Session Manager Plugin based on alpine without installing aws cli in the container.
Is it possible to use the containerized plugin along with aws cli installed on my local machine?
For example to execute this command:
aws ssm send-command --document-name "AWS-RunShellScript" --instance-ids ${instance_ID}

Hi @alexinfoblox,
Session manager plugin is needed when client side want to build a session to target instance/container with AWSCLI. e.g. https://docs.aws.amazon.com/cli/latest/reference/ssm/start-session.html#examples
It works only when AWSCLI can access the session-manager-plugin binary file, this should be a blocker I think.
Send command is another service, it no need to install session-manager-plugin if that is only what you need.
Thanks,
Yangtao


Fix Windows build

bzip.org is down :-/

@marek-safar Can you merge pls? The CI is broken without it unfortunately.


Clarification on Java 8  support

Thanks for creating this project.
Document says java version 13 and above. but pom.xml compiled against java 8.  https://github.com/IBM/java-iceberg-toolkit/blob/b8be05efc48a208eafce1146cd78e8b460b28988/tools/java-iceberg-cli/pom.xml#L10
does this work java 8?. if yes, better to update document.

@rshanmugam1, thank you for raising the issue.
Yes, the code can be packaged with java 8, however, java 13 and above is required for running the unit tests. I have created a pull request that lists the dependencies separately in the readme file.

👍


implement stop words & count most commonly occurring words

From @weAllWeGot on December 6, 2016 19:19
this can then be the basis of the categories. this probably a new branch but an interesting one. i wouldnt get rid of the predefined categories but i would add to them with what the analysis comes up with kind of more smartly/automatically.
Copied from original issue: weAllWeGot/kbai_chat_bot3#20

tried this. lmao, it took 25 minutes to get the count of all of the words in the reviews... will have to look into this again. i should have sorted the output list... grr

http://stackoverflow.com/questions/9953619/technique-to-remove-common-wordsand-their-plural-versions-from-a-string
from nltk.corpus import stopwords
s=set(stopwords.words('english'))

txt="a long string of text about him and her"
print filter(lambda w: not w in s,txt.split())

maybe use the words file at a next iteration, its in the repo

Add extra stop words
Add cleaning data function
In cleaning data function
Make list into set
Then cut it out of set if the first character is punctuation
Then cut it out of set if last character is punctuation
Write the word counts out to a file. The file can just be stored in the local directory since this takes a couple minutes to run usually. Although this will reduce running time by a little. If it's under 3 total seconds then we will add it


Syntax Highlighting gets weird when I use optional chaining

Prerequisites

[ ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
As the title says, the syntax highlighting doesn't get it right when i use feaatures from es2020 like optional chaining

It works again as expected when i remove it

Steps to Reproduce

write code
attempt to use optional chaining
expect the wrong syntax highlighting

Expected behavior:
Correct syntax highlighting
Actual behavior:
Wrong syntax highlighting
Reproduces how often:
100%
Versions
atom version: 1.53.0 x64
OS: Windows 10 Version 10.0.18363.1256

I can reproduce.
Atom 1.53.0
Electron 6.1.12
Chrome 76.0.3809.146
Node v12.4.0
My code uses node v14.15.3

I can reproduce.
Atom 1.53.0
Electron 6.1.12
Chrome 76.0.3809.146
Node v12.4.0
My code uses node v14.15.3

This should be in the language-JavaScript package, no?

This should be in the language-JavaScript package, no?

This should be in the language-JavaScript package, no?

yes, i found a pr there that seems to fix this issue at https://github.com/atom/language-javascript/pull/686

This should be in the language-JavaScript package, no?

yes, i found a pr there that seems to fix this issue at https://github.com/atom/language-javascript/pull/686


Decouple API (un)marshaling types from internal models

Right now, we have multiple classes that are used both as the (versioned) API representation and as the canonical internal representation of the resource.
The best example of this is mesosphere.marathon.state.AppDefinition.
This is a problem because it limits our ability to update the API while minimizing impact on parts of the codebase that should be unaffected by such changes.  It also hinders our ability to maintain concurrent versions of the API during a period of transition.  Ideally we'd be able to introduce a /v3 API, gradually move it from experimental to stable, and then eventually deprecate the current /v2 API.

+1 we already talked about that. Probably, we will not be able to do it soon, though.


regeneration for https://github.com/Azure/autorest.csharp/pull/2986

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Building up a Contact Channel in Readme.md

Is there an existing feature request for this?

[X] I have searched the existing feature requests

Describe the feature you would like to request

To enhance communication and provide direct access to Project Guidance, I plan to include a dedicated Contact section 👤. This section will feature the LinkedIn and GitHub profiles of each mentors and Admin⚡ enabling contributors to readily connect with them and address any project-related queries.

Additionally, to improve readability and organization, I Planned to implement clear visual separations between each section of the contributor documentation, ensuring a user-friendly and easily navigable 🚏 experience.

Finally, to foster a welcoming 🙏🏻 and inclusive environment, I will incorporate personalized welcome messages for our Repository.

To effectively convey the essence of our project and its objectives, I propose creating a customized cover image for the repository.

What problem does this feature solve?
Problem: A poorly structured or visually unappealing README can create confusion and hinder user engagement with a project.

This can lead to:

Difficulty understanding the project: Newcomers may struggle to grasp

Reduced contributions: Potential contributors may be deterred by a lack of clear information

Negative first impression: An unprofessional README can reflect poorly on the project and discourage users from
exploring further.

Alternative solutions
Kindly Assign me this Issue . I'm grateful to work with Talented Crews
Confirmation

[X] I have read the Bitbox Contributing Guidelines
[X] I am a GSSOC-EXT contributor
[X] I am a HACKTOBERFEST contributor
[X] I have starred the Bitbox repository
[X] I would like to help implement this feature

Hyy @Varunshiyam, I'm assigning this issue to you.

Can you give star to the repo?


Added new open source themes: AstroSAAS, QuickStore and SwissFolio

Hi @michael-andreuzza,
Apologize for the delay in responding. We were recently very busy with client projects, and the teammate responsible for reviewing themes before publishing couldn't check them.
We have now added the themes to our directory. Check here - https://statichunt.com/astro-themes . We truly appreciate your contributions to the open-source community.
Thank you.

Hey @tffarhad, it wasn't a rush mate. Thank you so much, very appreciated that you took the time to feature them too.
Keep up the stunning work!


Updating ipfs-coord-esm for bch-coinjoin pubsub

:tada: This PR is included in version 4.0.5 :tada:
Your semantic-release bot :package::rocket:


Add Azure App Analytics, refactor again.

This adds code to push logs and events to Azure Monitor (but not metrics yet).  The code was also refactored (again) , because I wanted to build code that didn't rely on monumental base classes.   I did this because I want a sample app which can easily be copy/pasted and base classes make that difficult to accomplish.


add .txt version of all transcriptions and translations

from the existing .docx files, convert to .txt files and add them to the texts/ directory

done


support multiple LoRAs in batched inference scenario

What does this PR do?

Support multiple LoRAs in batched inference setting. Here, we create sub-batches via logic groupby(adapter_name).

How to use:
[To Do]
ToDos:

[ ] Tests
[ ] Example Notebook
[ ] Documentation
[ ] Support all the layers types such as Conv, Embedding, Quantized 8-bit and 4-bit layers.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Thank you for tackling this Sourab. I think this is a feature that many users would find useful and having support for this being added should be high priority.
I'm just leaving some early comments for now, so that we can discuss the design:
I was also thinking about how to solve this problem. Especially, how to pass the information about which adapter to use for which sample to the forward method of the respective adapters. The solution presented here is that this information is part of the kwargs when calling the PeftModel/LoraModel, then it is immediately removed from the kwargs and saved as an attribute on the adapter layer, where it is retrieved during the forward call.
I'm not a big fan of this approach, as it works via side-effects. This makes it hard to reason about and more difficult debug. Furthermore, it requires a lot of care to handle correctly. As an example, say a user calls generate with adapter_indices, then they are set as an attribute. Let's assume that somewhere in the call, there is an error. The adapter_indices won't be cleaned up. Next time the user calls without adapter_indices, the attribute is still set, thus they get incorrect outputs without any indication that something went wrong. So at the very least, we have to take more care of doing the clean up correctly.
Another potential issue is that at the moment, adapter_indices is cleaned up at the end of the forward call of the adapter layer. But what happens if a single forward or generate call on the LoraModel/PeftModel requires multiple forward calls for each layer? Then only the first call is correct and the subsequent ones ignore the information.
Overall, this approach looks very brittle to me and if possible, I would like to find a better approach.
I assume that you also considered just passing down the kwargs with the adapter_indices but that this wouldn't work, because transformers/some model architectures cannot handle arbitrary arguments being added. So this more straightforward way is not possible.
An alternative idea could be to work with pre-forward hooks using with_kwargs=True, as they should allow us to add more arguments to the kwargs before they are passed to forward. This is still a side-effect with all the associated problems, and it would still require us to ensure that the hooks are properly cleaned up, but at least we get the handles, which only require a .remove() call to be cleaned up.
Other than that, I'm open for ideas and discussions, maybe there is a better solution we just haven't considered yet.

No, bad bot!


[FEATURE REQ] Add OpenTimestamps client guide

What & why
Since v0.15.0 LND timestamps the manifest file along with its signature with OpenTimestamps. Would be good that RaspiBolt users could also check these before installation.
How
See https://github.com/opentimestamps/opentimestamps-client for OTS client installation info.

What & why
Since v0.15.0 LND timestamps the manifest file along with its signature with OpenTimestamps. Would be good that RaspiBolt users could also check these before installation.
How
See https://github.com/opentimestamps/opentimestamps-client for OTS client installation info.

I had a look and it should be easy to add to the instructions.
Just out of curiosity, I tried to find an example of when this time stamp check would actually prevent something bad to run on my node but couldn't really find any use case.. could you ELI5 the main use case of such a timestamp check for node operators? (assuming the binary checksum has been checked and the signature of the checksum file has also been checked)

could you ELI5 the main use case of such a timestamp check for node operators? what bad scenario does it protect against?

You can check that signature was made at release date (or before that), not forged later with different binaries (for example, somebody could gain access to private keys used for signing after original release was made).

(assuming the binary checksum has been checked and the signature of the checksum file has also been checked)

Yes, this kinda is enough, but extra security checks never hurts. What if all Github accounts with commit access to RaspiBolt master have been compromised?

could you ELI5 the main use case of such a timestamp check for node operators? what bad scenario does it protect against?

You can check that signature was made at release date (or before that), not forged later with different binaries (for example, somebody could gain access to private keys used for signing after original release was made).

(assuming the binary checksum has been checked and the signature of the checksum file has also been checked)

Yes, this kinda is enough, but extra security checks never hurts. What if all Github accounts with commit access to RaspiBolt master have been compromised?

Ok so an example would be a checksum and signature that works but the timestamps would not meaning that the release has been modified since its release, right?
Anyways, let's add it for sure! And also for Bitcoin Core. Do you want to have a go at the PR?

Reopening this issue?

@VajraOfIndra #1087 is not yet merged into master.

@VajraOfIndra #1087 is not yet merged into master.

Gee, I thought it was, sorry.

@VajraOfIndra You planning to reopen that PR?

@VajraOfIndra You planning to reopen that PR?

Yes, will reopen a PR


Organisations users with CREATE_FEATURE permission are unable to create MV features

To reproduce:

Create a user with VIEW_PROJECT, CREATE_FEATURE permissions at the project level and admin at the environment level for at least one environment
Sign in with that user and attempt to create a feature with at least one multivariate variation

Expected behaviour: Multivariate feature is created
Actual behaviour: an error occurs and the feature is created without the variation(s)

From what I can tell, we have 2 solutions here:

Remove the option to create MV features from the frontend if the user isn't a project admin
Allow users with CREATE_FEATURE permission to create MV options when they first create a feature (but not subsequently modify them)
Allow users with CREATE_FEATURE permission to create and modify MV options
Create a new permission to handle the modification of MV options
Create a new permission to handle the modification of features across a project (this one will be a bit fiddly as we then have some overlap between it, the create feature and delete feature permissions)

I am leaning towards option #3. Maybe the FE should be updated to state Create / Modify Features here:

Thoughts please @gagantrivedi @kyle-ssg


How to use it?

Hi,
Thanks for this wonderful project  not many project at github that can combine vcloud director metrics into prometheus.
But i still wondering how to use it? since, my prometheus can't read any information from output.log.
It can only read data like this. There's no info in output.log such as __meta_vcd_metadata_apps, __meta_vcd_num_cores_per_socket that listed in vcd-sd result page (http://localhost:9000/metrics)

are there any possibilities to read whatever in output.log said into Prometheus, coz output.log data is accurate but somehow can't be injected into vcd-sd metrics data (http://localhost:9000/metrics)
Thanks

The metrics of this tool are only related to this tool, it doesn't include any vcloud metrics. This is meant to provide a dynamic inventory of the virtual machines launched on vcloud director.

noted on this. Thanks


Makefile: parametrize vw args; also mention --multitask

For reference, this is the issue I opened in the official vw repo
https://github.com/VowpalWabbit/vowpal_wabbit/issues/4614
My guess is that the leak happens through the full-connectivity of the features via the hidden layer.
Since the full connectivity is a done-deal (imposed at the start of run by the fact we want a fully-connected NN.
It seems to me that the SGD update should somehow skip updates to weights that have nothing to do with the ones in the example. IOW the skips should be in run-time (rather than initialization time) and should update only those target nodes that are present in the current example.
Ideally, this skip vs non-skip (like it is today) should be controlled by a CLI switch.
--respect_namespaces --restricted_update or something like this.


When building vLabeler from source code on Arch Linux, the menu bar cannot display properly.

Describe the bug
After building the project according to the documentation, the menu bar displays incorrectly.
To Reproduce
Steps to reproduce the behavior:

cd vLabeler
./gradlew createDistributable
cd build/compose/binaries/main/app/vLabeler/bin/
./vLabeler

Expected behavior
The menu bar displays correctly.
Screenshots
https://github.com/sdercolin/vlabeler/assets/55609004/0188e4e2-3d79-448c-b5c3-442369f3c2c6
App runtime Info
App version: 1.2.0
Runtime version: 17.0.11+9
OS: Linux 6.6.28-2-lts amd64
System locale: zh_CN
Debug mode: false
User directory: /home/lfh/vLabeler
Resource directory: /media/sda1/data/code/vlabeler-1.2.0/build/compose/binaries/main/app/vLabeler/lib/app/resources
Tracking id: null
Logs
error.log
info.log

Is it necessary to have other dependencies besides needing JDK 17+ to build successfully? I tried directly unpacking the Ubuntu deb package from the release and it runs normally.

How about ./gradlew run ?

./gradlew run

Coping with the same problem.

./gradlew packageDistributionForCurrentOS

Output:

Task :packageDeb FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':packageDeb'.

External tool execution failed:

Command: [/usr/lib/jvm/java-17-openjdk/bin/jpackage, @/media/sda1/data/code/vlabeler-1.2.0/build/compose/tmp/packageDeb.args.txt]
Working dir: []
Exit code: 1
Standard output log: /media/sda1/data/code/vlabeler-1.2.0/build/compose/logs/packageDeb/jpackage-2024-04-29-08-00-03-out.txt
Error log: /media/sda1/data/code/vlabeler-1.2.0/build/compose/logs/packageDeb/jpackage-2024-04-29-08-00-03-err.txt

BUILD FAILED in 3s
9 actionable tasks: 2 executed, 7 up-to-date

out.txt
err.txt
I think it might be because I'm not using an Ubuntu system, so I can't build a .deb package.

I tried installing a GNOME desktop environment for my system and rebuilt vLabeler. vLabeler runs fine under GNOME, perhaps this is a bug with KDE.

Sorry I'm not familiar with linux systems and I'm glad you find a solution!


Add support for user-controlled CTE materialization

Why the new feature should be added
Hi! Looking for support for WITH some_table AS MATERIALIZED and WITH some_table AS NOT MATERIALIZED as highlighted in PostgreSQL 12 changes to default CTE materialization here.
https://www.postgresql.org/docs/current/queries-with.html#id-<IP_ADDRESS>.7
How the new feature should work
Ideas:
...
.with(someQuery)
.asMaterialized() // OR .asNotMaterialized()
...

🪦

@shadforth did you ever find a workaround? is there global postgres property to ensure that all ctes are materialized? like prior to version 12?

nvm .. https://github.com/sqlalchemy/sqlalchemy/pull/5043

@shadforth  query.addFlag(QueryFlag.Position.WITH, String.format(""%s" as materialized", "cte_name"), cte);

@shadforth query.addFlag(QueryFlag.Position.WITH, String.format("\"%s\" as materialized", "cte_name"), cte);

Currently our workaround is adding random() to select to force the materialized view.


[6.5.x] JBPM 5236 - EJB Migration Tests

Hi,
this is the same as #540, but for the 6.5.x branch.
Marián

Jenkins retest this


refactor(relm): migrate to ListStore

Codecov Report

Merging #65 (7d63e7e) into master (8178365) will decrease coverage by 0.13%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #65      +/-   ##
==========================================
- Coverage   91.02%   90.88%   -0.14%
==========================================
  Files          57       56       -1
  Lines        2952     2940      -12
  Branches       33       33
==========================================
- Hits         2687     2672      -15
- Misses        265      268       +3

Impacted Files
Coverage Δ

crates/relm/src/lib.rs
100.00% <ø> (ø)

crates/relm/src/chapter_list.rs
98.30% <100.00%> (+0.34%)
:arrow_up:

crates/relm/src/download.rs
100.00% <100.00%> (ø)

crates/relm/src/list_model.rs
95.74% <100.00%> (+0.74%)
:arrow_up:

crates/relm/src/list_store.rs
96.93% <100.00%> (+0.27%)
:arrow_up:

crates/relm/src/manga_info.rs
100.00% <100.00%> (ø)

crates/relm/src/task_list.rs
100.00% <100.00%> (ø)

crates/relm/src/gobject.rs
86.66% <0.00%> (-4.45%)
:arrow_down:

crates/relm/src/task.rs
98.50% <0.00%> (-0.75%)
:arrow_down:

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


Adapter cloudflare

Adds an adapter for cloudflare pages with functions.
cc @lukeed

Failing tests are unrelated
I ported this adapter over into a test repo and its deployment was successful. Verified it all works and so this is ready to go IMO

@benmccann resolved all comments in the linked PR

So close to having this available! Is there a process for performing releases? https://github.com/sveltejs/kit/pull/2818


Error Handling Concept #125

Added the error-handling concepts along with the examples. Crosschecked the details. Ready to merge.

Thanks for the detailed review, I updated the file according to the comment.

Made changes according to your instructions. Let me know if any changes are still needed.

Spellcheck the text again, there are still spelling issues within. You can use this online tool to do this for you
https://languagetool.org/

Thanks for your kind reviews.
Here are the results:
All were compiled and checked. ✅
Spell checked ✅
markdown-lint (markdownlint v0.34.0) ✅


use byte array temp buffer for copying the image data from the response

use the ByteArrayOutputStream's internal buffer to skip creating a second array in memory

run CI

:+1:


.slice() for String and Array

You mean slice()->ArrayView or slice()->Array?

Not sure. ArrayView seems better