jumalauta's skinke demo doesn't animate properly

This may be releated to #15 and will probably be solved by solving #15 but whatever.
ROM: http://gameboy.modermodemet.se/en/demo/147

Possibly related to #12

This HAS to be vblank related... I disassembled the ROM: http://i.imgur.com/29YU8xc.png - I am positive the vblank timings are wrong now.

Possible duplicate of #22

This was NOT a duplicate. It was due to the demo abusing SB (serial in/out data) as a scratch register.
This has been fixed in c11c337 and now has a separate problem to be solved.


Various Fixes

Various fixes
This PR implements various fixes into the master branch.
Fixes #55 #56
Type of change
Please delete options that are not relevant.

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] This change is a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Coverage increased (+0.2%) to 51.89% when pulling 2fd89455a494411f95b6d34b6facdecc446f967e on fixes into a77e54e8dfe1ceaa1c918b836f3eeb86f0e7c170 on master.


[2.0] DataTransformer found twice

Not a problem, yet, but I'm configuring everything (working on another project) and i got the following warning as soon as I ran the command:
composer require yajra/laravel-datatables-buttons
Warning: Ambiguous class resolution, "Yajra\Datatables\Transformers\DataTransformer" was found in both "..vendor/yajra/laravel-datatables-oracle/src/Transformers/DataTransformer.php" and "..vendor/yajra/laravel-datatables-buttons/src\Transformers\DataTransformer.php", the first will be used.
System details

Operating System
PHP Version: 7.1
Laravel Version: 5.4
Laravel-Datatables Version: 7.9.3
Laravel-Datatables-Buttons: 2.02

Thanks, DataTransformer was removed on v8 of the main package so I moved it on the buttons table. I think I should rename the transformer on to something else to fix this warning.

Fixed on v2.0.3, kindly update and confirm. Thanks!


[c++, r] Update and refactor nanoarrow

Issue and/or context:
We rely on nanoarrow to take advantage of higher-level structures for the (otherwise 'naked' void * of the C API of Arrow.  nanoarrow helps here, and has made good strides in crecent releases.
Changes:
We update the 'vendored' nanoarrow to release 0.4.0, and make extended use of it.  This works well: simple examples work fine and show the desired memory behaviour.   However, on larger examples we see interactions with (local) handling of Arrow objects in libtiledbsoma so the scope of the PR will have to extended to handle allocating, releases and setting up Arrow objects via nanoarrow.
Notes for Reviewer:
~This PR is informational to run some CI; all local tests pass.  However, at present an invasice change in libtiledbsoma makes this unsuitable for a merge at present meaning it is also not yet fully ready for a review.~
The secret cabal powers of CI are currently smiling upon us (after a lot of help from several people, and a last minute bug fix) so the 'draft' label is now off.  There are remaining 'drafty' things here (such as a move of nanoarrow.* to a directory below external/ but we can do so in a later PR.

The dual nanoarrows (from inside the R package, and inside libtiledbsoma) can likely be remedied. The location in tiledbsoma should be in externals/ anyway -- a follow-up PR seems apt.

The dual nanoarrows (from inside the R package, and inside libtiledbsoma) can likely be remedied. The location in tiledbsoma should be in externals/ anyway -- a follow-up PR seems apt.

https://github.com/single-cell-data/TileDB-SOMA/issues/2362

@johnkerl One triplet of nanoarrow files is now gone.

Thanks @eddelbuettel !!
Just to set an expectation, this may not backport automatically to release-1.9 since apis/r/DESCRIPTION is touched and that differs between main and release-1.9 -- not to worry, I'll do a manual backport tomorrow morning if so


Fix python version for code coverage

Coverage reports are giving weird stochastic numbers. This may be a consequence of mixing results from different python versions. Regardless, we only report coverage for the highest python version we run tests for now.

Pull Request Test Coverage Report for Build c52476bc-9886-407a-b78d-51e3df04a5b5

0 of 0   changed or added relevant lines in 0 files are covered.
835 unchanged lines in 24 files lost coverage.
Overall coverage decreased (-15.9%) to 65.856%

Files with Coverage Reduction
New Missed Lines
%

bittensor/_endpoint/init.py
1
85.96%

bittensor/_metagraph/init.py
1
79.49%

bittensor/_wandb/init.py
1
48.53%

bittensor/_config/init.py
2
80.65%

bittensor/_dataset/init.py
2
88.57%

bittensor/_metagraph/metagraph_impl.py
2
63.41%

bittensor/_threadpool/priority_thread_pool_impl.py
2
73.88%

bittensor/_subtensor/subtensor_impl.py
3
79.35%

bittensor/_wallet/wallet_impl.py
3
75.56%

bittensor/_subtensor/init.py
5
75.61%

Totals

Change from base Build 304f61d9-f910-4eea-b1c2-82fc89eab0e6:
-15.9%

Covered Lines:
3410

Relevant Lines:
5178

💛  - Coveralls


Make public?

@andrewryh @lindsayad: How would you folks feel about developing this in the open (i.e. making the repository 'public') ?
With a nice attribution license and everything, I'd say you're safe to open it up. But, it's absolutely up to the two of you. Thoughts? Questions?

Good good. Public now!


Simplifies the count_ones definition.

Codecov Report

Merging #1742 (2f49a87) into main (45156fd) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1742      +/-   ##
==========================================
- Coverage   94.13%   94.13%   -0.01%
==========================================
  Files         267      267
  Lines       50903    50900       -3
==========================================
- Hits        47920    47913       -7
- Misses       2983     2987       +4

Impacted Files
Coverage Δ

fastfield_codecs/src/null_index/dense.rs
99.16% <100.00%> (-0.01%)
:arrow_down:

src/fieldnorm/writer.rs
96.96% <0.00%> (-1.52%)
:arrow_down:

src/fastfield/multivalued/mod.rs
97.29% <0.00%> (-1.16%)
:arrow_down:

fastfield_codecs/src/null_index/sparse.rs
95.27% <0.00%> (-0.19%)
:arrow_down:

stacker/src/expull.rs
98.88% <0.00%> (+0.55%)
:arrow_up:

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


bug: user feedback with attachment

Platform:

[ ]  Dart
[x]  Flutter Android or iOS
[ ]  Flutter Web

IDE:

[x]  VSCode
[ ]  IntelliJ/AS
[ ]  XCode
[ ]  Other, which one?

split-debug-info and obfuscate (Flutter Android or iOS) or CanvasKit (Flutter Web):

[ ]  Enabled
[x]  Disabled

Platform installed with:

[x] pub.dev
[ ] GitHub

Output of the command flutter doctor -v below:
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.0.1, on Microsoft Windows [Version 10.0.22000.739], locale en-US)
Checking Android licenses is taking an unexpectedly long time...[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.9.6)
[√] Android Studio (version 4.1)
[√] VS Code (version 1.68.1)
[√] Connected device (4 available)
[√] HTTP Host Availability

• No issues found!

The version of the SDK (See pubspec.lock):
^6.6.1

I have the following issue:
User feedback with attachments result in errors on the Sentry dashboard, but no errors get logged on the terminal.
Steps to reproduce:
Tap on a button with the following implementation:
	try {
      final id = await Sentry.captureMessage(
        message,
        level: SentryLevel.warning,
        withScope: (scope) {
          scope
            ..setTag('feedback', 'true')
            ..fingerprint = ['feedback-${uuid()}']
            ..addAttachment(
              SentryAttachment.fromUint8List(
                screenshot,
                'screenshot.png',
                contentType: 'image/png',
              ),
            );
        },
      );
      await Sentry.captureUserFeedback(
        SentryUserFeedback(
          eventId: id,
          comments: message,
        ),
      );
      print('User feedback sent');
    } catch (e, st) {
      print('Failed to send user feedback\n$e\n$st');
    }

Where message is a String and screenshot is the Uint8List representation of a PNG screenshot.
Actual result:

No error messages are logged
A new Sentry issue is created
No feedback entry is created nor linked to the issue
Plus, the Sentry dashboard displays the following:

Expected result:
A new event on the Sentry issues view and a new entry on the Sentry user feedback view.

@mrverdant13 thanks for the report, are you using sentry or sentry_flutter? What's the Flutter version? Android or iOS?

@marandaneto
I am using sentry_flutter and I've tested the package with a couple of Android devices.
PS I've updated the actual result in the bug report:

Actual result:

No error messages are logged
A new Sentry issue is created
No feedback entry is created nor linked to the issue
Plus, the Sentry dashboard displays the following:
...

Well I tested this again by sending two reports
As you can see here, both of them (khe and testing again) are listed within the issues page.
Also, they both include the user data, as expected.

However, the user feedback page only shows the khe feedback.

Here I include the issue event details

@mrverdant13 can you provide a minimal reproduction example? an empty project that shows the problem, I can't reproduce myself, thanks.

Closing the issue as a part of large repository cleanup, due to it being inactive and/or outdated.
Please do not hesitate to ping me if it is still relevant, and I will happily reopen and work on it.
Cheers!


Reset the cursor to the top of the infoview when updating.

Closes: #27
Bit hairy getting some testing in place, but @gebner care to review this does what you expect?

Hmm, unfortunately this does not work as well as I'd hoped.  The cursor jumps back to the top as soon as you switch back to the window for the lean file.  Maybe it just takes getting used to, but it is very counter-intuitive that switching windows moves the cursor.  The infoview moves to the top while I'm still reading it.
-- long trace message for testing
#eval let y := (List.range 100).map fun x => dbg_trace x; x + 1 dbg_trace "this is important" y.length

Maybe a better heuristic is to move the cursor to the top only when you move to a new line.
The behavior of scrolloff=10 would also be okay, but that doesn't seem to work for automatic updates.

Aha, ok, I think I follow, you want it to move just if the new contents are shorter than the window length? Or do you want it to move even if they're long but have changed? (Whereas now it moves always even if nothing whatsoever changes in the infoview contents, just CursorHold fires again and it repopulates)
I think I can imagine both of those other behaviors being the expected one in different scenarios, right?

Aha, ok, I think I follow, you want it to move just if there are some new infoview contents are shorter than the window length?

My main issue with the current (= main branch) behavior is that it is easy to miss errors: you scroll down a long trace message.
Then you move a line up, the infoview is empty, and now you think that everything is fine or that lean is still processing the file.
So for me it's only important to scroll up when the content changes and becomes shorter.

Or do you want it to move even if they're long but have changed?

Ideally not.  When I look at the middle of a long trace message and it's updated to similarly long message, then chances are I still want to see the same part, and see if anything's changed.

I think I can imagine both of those other behaviors being the expected one in different scenarios, right?

Good question, and I can't really tell.  That's why I'd like to keep the automatic movements to a minimum. Scrolling the infoview has never bothered me in vscode, but it's also never empty.

OK, I think I convinced myself this is actually likely a neovim bug, which I filed as neovim/neovim#14663.
I found a way to hack around it for now, which I pushed to this PR (it actually I think has nothing to do with the cursor position but I'm not 100% and didn't go off and read the neovim C source yet).
Feel free to have another look, hopefully this is closer to what you expect, though perhaps we could be even more sticky on restoring line position. But in trying your long trace example and adding some other lines around it, I suspect this is an improvement.

This is exactly what I wanted!  Thanks!


Lineage graph: guidance to upload a proper lineage file

Is your feature request related to a problem? Please describe.

Currently, if the lineage file is not suitable for our code implementation, users cannot understand why the lineage information has not uploaded.
They can't even tell if something is wrong or not.
Describe the solution you'd like
If a mandatory column is not found, show a gentle error and how-to message.
Describe alternatives you've considered
We can provide a feature to modify the lineage file directly.
It might be very helpful, but costive to implement.
Additional context
Please refer to LineageException and LINEAGE_COLUMN_IS_MISSING. (LineageEdgeServer.java)

Steps to reproduce the behavior:

Log in as admin.
Management - Explore Data - Metadata - "Create new metadata"
Find MySQL connection. (If none, make by Management - Data Storage - Data Connection - New)
Find polaris (polaris_v2, polaris_dev, etc.) DB
Check 5 tables: activity_stream, audit, common_code, dashboard, datasource.
Management - Explore Data - Metadata - Lineage (a.k.a. lineage tab)
Click "New"
Drag & drop polaris_lineage.csv.txt
Click "Done" -> Nothing happens.

When reproduce, you should rename .txt to .csv.
This will be fixed very soon. (Maybe by this issue)

This issue has been partially resolved by https://github.com/metatron-app/metatron-discovery/issues/2491 (refer the comments).
I've made another issue (https://github.com/metatron-app/metatron-discovery/issues/2496) to resolving the rest.
When https://github.com/metatron-app/metatron-discovery/issues/2496 is done, let's close https://github.com/metatron-app/metatron-discovery/issues/2496 and https://github.com/metatron-app/metatron-discovery/issues/2469 together.


增加對qwen1.5 1.8b的支持

I think the support is already there in terms of qwen 2 . Qwen 1.5 are just beta versions of qwen 2
But share same architecture


is it possible to make this completely independent from stremio servers?

I installed this in my server, but if I create an account for example it is not created on my server, but on stremio servers (in fact I can log in to the newly created account on https://web.stremio.com).
how can I force it to never connect to the stremio server, and to keep all data locally on my server?

you would need to change https://github.com/Stremio/stremio-web

you would need to change https://github.com/Stremio/stremio-web

thanks for the reply! Do you mean that it would be needed to fork stremio-web and modify it, or that this can be configured in stremio-web but it's not supported by stremio-docker?


fix show style

I fixed validation error on #13.
and I will fix referred objects on #27.
so I dispose this issue.


More accurate definition of the subscription limit

More than 50 (or 200) subscriptions can be created via EA portal - the sentence can be misunderstood.

@MaxMelcher : Thanks for your contribution! The author, @jureid, has been notified to review your proposed change.

@MaxMelcher - sorry this change was not addressed promptly. It looks like the subscription limit text has changed through another pull request. For that reason, I will close this PR, but will add similar text in a new PR.

#please-close


Version 1 - personal statement from the course selection tab

This updates the application flow so that, when adding a new course, the personal statement from the most recent application is automatically copied across. This saves users from having to do this manually. They could still edit the personal statement as they wish.
Additionally:

some text on the main applications page warns candidates that they'll be asked to write a personal statement
the max word count has been reduced from 1000 words to 500 words
the personal statement guidance has been reduced
a full-width summary card pattern is used to review the personal statement instead of a summary list, in order to have more space.

Screenshots
Applications page (no applications started yet)

First personal statement, with hint text saying you can save it as a draft and come back later.

Application review - personal statement drafted

Application review - personal statement left blank for now (cannot submit yet)

Second personal statement - previous one copied

 Design course flow + personal statement in Apply


Helm Operator error when parsing release yaml file

I'm getting an error when the Helm Operator tries to read this file.
prometheus_release.yaml
apiVersion: helm.integrations.flux.weave.works/v1alpha
  kind: FluxHelmRelease
  metadata:
    name: prometheus
    namespace: monitoring
    labels:
      chart: prometheus
  spec:
    chartGitPath: prometheus
    values:
      - name: alertmanager.service.loadBalancerSourceRanges
        value: ["<IP_ADDRESS>/32"]

In place of - 'value: ["<IP_ADDRESS>/32"]', I've also tried:
        value: "<IP_ADDRESS>/32"

        value:
          - "<IP_ADDRESS>/32"

I get the same error below.
ERROR: logging before flag.Parse: E0328 20:53:25.638434       7 reflector.go:205] github.com/weaveworks/flux/integrations/client/informers/externalversions/factory.go:73: Failed to list *v1alpha.FluxHelmRelease: v1alpha.FluxHelmReleaseList.Items: []v1alpha.FluxHelmRelease: v1alpha.FluxHelmRelease.Spec: v1alpha.FluxHelmReleaseSpec.Values: []v1alpha.HelmChartParam: v1alpha.HelmChartParam.Value: ReadString: expects " or n, but found [, error found in #10 byte of ...|,"value":["<IP_ADDRESS>|..., bigger context ...|anager.service.loadBalancerSourceRanges","value":["<IP_ADDRESS>/32"]},{"name":"server.service.loadBal|...
ERROR: logging before flag.Parse: E0328 20:53:26.640464       7 reflector.go:205] github.com/weaveworks/flux/integrations/client/informers/externalversions/factory.go:73: Failed to list *v1alpha.FluxHelmRelease: v1alpha.FluxHelmReleaseList.Items: []v1alpha.FluxHelmRelease: v1alpha.FluxHelmRelease.Spec: v1alpha.FluxHelmReleaseSpec.Values: []v1alpha.HelmChartParam: v1alpha.HelmChartParam.Value: ReadString: expects " or n, but found [, error found in #10 byte of ...|,"value":["<IP_ADDRESS>|..., bigger context ...|anager.service.loadBalancerSourceRanges","value":["<IP_ADDRESS>/32"]},{"name":"server.service.loadBal|...
ERROR: logging before flag.Parse: E0328 20:53:27.642489       7 reflector.go:205] github.com/weaveworks/flux/integrations/client/informers/externalversions/factory.go:73: Failed to list *v1alpha.FluxHelmRelease: v1alpha.FluxHelmReleaseList.Items: []v1alpha.FluxHelmRelease: v1alpha.FluxHelmRelease.Spec: v1alpha.FluxHelmReleaseSpec.Values: []v1alpha.HelmChartParam: v1alpha.HelmChartParam.Value: ReadString: expects " or n, but found [, error found in #10 byte of ...|,"value":["<IP_ADDRESS>|..., bigger context ...|anager.service.loadBalancerSourceRanges","value":["<IP_ADDRESS>/32"]},{"name":"server.service.loadBal|...
ERROR: logging before flag.Parse: E0328 20:53:28.644675       7 reflector.go:205] github.com/weaveworks/flux/integrations/client/informers/externalversions/factory.go:73: Failed to list *v1alpha.FluxHelmRelease: v1alpha.FluxHelmReleaseList.Items: []v1alpha.FluxHelmRelease: v1alpha.FluxHelmRelease.Spec: v1alpha.FluxHelmReleaseSpec.Values: []v1alpha.HelmChartParam: v1alpha.HelmChartParam.Value: ReadString: expects " or n, but found [, error found in #10 byte of ...|,"value":["<IP_ADDRESS>|..., bigger context ...|anager.service.loadBalancerSourceRanges","value":["<IP_ADDRESS>/32"]},{"name":"server.service.loadBal|...
ERROR: logging before flag.Parse: E0328 20:53:29.646676       7 reflector.go:205] github.com/weaveworks/flux/integrations/client/informers/externalversions/factory.go:73: Failed to list *v1alpha.FluxHelmRelease: v1alpha.FluxHelmReleaseList.Items: []v1alpha.FluxHelmRelease: v1alpha.FluxHelmRelease.Spec: v1alpha.FluxHelmReleaseSpec.Values: []v1alpha.HelmChartParam: v1alpha.HelmChartParam.Value: ReadString: expects " or n, but found [, error found in #10 byte of ...|,"value":["<IP_ADDRESS>|..., bigger context ...|anager.service.loadBalancerSourceRanges","value":["<IP_ADDRESS>/32"]},{"name":"server.service.loadBal|...
ERROR: logging before flag.Parse: E0328 20:53:30.648663       7 reflector.go:205] github.com/weaveworks/flux/integrations/client/informers/externalversions/factory.go:73: Failed to list *v1alpha.FluxHelmRelease: v1alpha.FluxHelmReleaseList.Items: []v1alpha.FluxHelmRelease: v1alpha.FluxHelmRelease.Spec: v1alpha.FluxHelmReleaseSpec.Values: []v1alpha.HelmChartParam: v1alpha.HelmChartParam.Value: ReadString: expects " or n, but found [, error found in #10 byte of ...|,"value":["<IP_ADDRESS>|..., bigger context ...|anager.service.loadBalancerSourceRanges","value":["<IP_ADDRESS>/32"]},{"name":"server.service.loadBal|...

@sebastianwth02 Does using a recent release of the helm-operator help? The format of spec.values changed to make this kind of value possible. (or did you move on ...)

Closing on the basis that the problem was the values format, which has been fixed since.


Problem in Raspberry pi 3

Hi!
I have try your code in raspberry pi 3 but the function gps_location() not work, you must change the PORTNAME in "serial.h" file with "/dev/ttyS0" for raspberry 3.
Many thanks for the great work!!

We have to try to redefine the PORTNAME definition during the compilation step. i will check this in the future

make CFLAGS="-g -Wall -O3 -D PORTNAME=/dev/ttyS0"

The current make structure probably is not suitable to support a configuration phase. Need a complete rewrite using a more common structure to support options and other configurations
Probably with automake or other things
./configure
make
make install


Bug fixes for listbox, treebox, and nana::any

treebox.cpp:  fixed a bug in trigger::dbl_click()
impl_->set_expanded() was called unconditionally, even if the node had no children. This caused the node icon to change to the "expanded" icon if the node had an icon scheme, even when the node didn't have children.
listbox.cpp:  listbox::sort_col doesn't update view
Calling listbox::sort_col to change the sort column doesn't update the viewport to reflect the change, forcing the user to call API::refresh_window or otherwise perform stupid tricks to force the listbox to refresh.
any.hpp: argument not forwarded
A constructor and an overload of the assignment operator each have a forwarding reference as a parameter, but they don't actually forward the argument.
treebox.cpp:  fixed buggy item_proxy postfix increment operator
The behavior of the postfix increment operator is not consistent with the increment operator concept (currently just returns the next sibling node).
listbox.cpp: nana::drawerbase::listbox::essence::where incorrectly calculates the position of checkboxes in the listbox content area (see the extensive description in the commit)

Thank you for fixing this issue.


barcodes_samples now accept files like:

Just doing this merge through pull request because it was quite big.
barcodes_samples now accept files like:
AAAAAAA,sample1
That will be used to name the cells from that sample in the final
tagcounts.mtx.metadata

Thank you for this! This is a useful feature.

I hope so, the singlecellexperiments is not on yet, but working on that.


[Bug]: Cannot handle null/empty values

Contact Details
<EMAIL_ADDRESS>What happened?
Report does not handle null or empty values for city details, which causes display issues.

Environment
MACOS
JDK Version
JDK 17
Where are you seeing the problem on?
Console
Relevant log output
Output uploaded as image above

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Implemented conditional statements to check these errors.


agent: do not quit on grpc serve errors

If any errors happens at that time, we should just tear down the
connection and start over again.

@sboeuf yes, I get the situation in case of vm factory w/ builtin proxy.


Add a way to access the wrapped component from reduxForm HoC

Thanks for you contribution. The overall logic seems good to me. However:

Could you revert the changes made to README.md and package.json?
Could you run npm run lint -- --fix and fix the remaining errors?

Thank you for your advice. I tried to correct it as you like. Best.

Tests don't pass. Could you fix the linting?

Ok, I am on it. I will also commit the tests for getWrappedInstance().

[Current coverage][cc-pull] is 96.75%

Merging [#1224][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.35%

@@             master      #1224   diff @@
==========================================
  Files            73         73
  Lines          4123       4163    +40
  Methods         770        766     -4
  Messages          0          0
  Branches        316        324     +8
==========================================
+ Hits           4004       4028    +24
- Misses          119        135    +16
  Partials          0          0

Powered by Codecov. Last updated by [636ea87...817ba5c][cc-compare]
[cc-base-branch]: https://codecov.io/gh/erikras/redux-form/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/erikras/redux-form/compare/636ea87d04a8f50f95addc615db027112e526f8b...817ba5ccebce07a06b453b4973888a85de7f8fdd?src=pr
[cc-pull]: https://codecov.io/gh/erikras/redux-form/pull/1224?src=pr

Nice addition I actually need this, how can I help to get this merge into the next release ?

Hey, thank you. I am having trouble to pass the codecov out of tests.

Hey @ooflorent, could you give some hints about how to pass tests while not losing from codecov?

Published in v5.3.4.


[PORT] Make cycle detection throw an exception instead of returning null

https://github.com/microsoft/botbuilder-dotnet/pull/4606
Remove the two-step passes and the cache logic. Just throw an exception when detecting the loop.

We cannot implement cycle detection feature right now because we don't have callstack support in js sdk, but cycle reference is supported.

Reviewed by the SDK team. Closing as Not Needed.


migrates aos_web from nickjalbert's github to main repo

Copies the contents of https://github.com/nickjalbert/aos_web into a directory called web

Would it make more sense to have the web dir live under the agentos dir?


Discrepancy Between Reported and Downloaded #Questions for HotpotQA and MS-MARCO Datasets

Hi, I have encountered an issue regarding the number of questions reported in the paper's Table 12 ("Statistics of Datasets") and the actual number of questions downloaded via the prepare_dataset.py script.

In the table, the number of questions for HotpotQA is listed as 7,405 and for MS-MARCO as 6,980.
However, when I download the datasets using the prepare_dataset.py script, I find the following numbers:

HotpotQA: 97,853 questions
MS-MARCO: 509,963 questions

This significant discrepancy between the reported and actual dataset question counts is confusing. Could you provide clarification on the cause of this difference? Is there an explanation for this discrepancy, or is there a potential issue with the dataset preparation process?
Thank you for your time and help in resolving this issue!

Hi! Thanks for pointing it out!
In our paper and code we used BEIR dataset.
We used test split for NQ and HotpotQA, and train split for MS-MARCO.
Based on the original BEIR dataset, HotpotQA and MS-MARCO put all of their splits in a single zip file. But for NQ, its train split is in another file named nq-train. That's why you saw a larger number for HotpotQA and MS-MARCO.
We followed the same way of loading BEIR dataset that uses a GenericDataLoader provided by BEIR.
And you could also see the following information on the BEIR website:

These numbers are consistent with what we reported in our paper.
I hope this could answer your question!
And thanks for your interest in our paper!


Updated marker to show picked pixel

Fixes Issue #267
The picked pixel is visible now.
Contributor Checklist:

[x] I have added myself to the creators.json file
[ ] I have added a changelog entry for my contribution
[ ] I have added/updated documentation for all user-facing changes

Hi @AnandBaburajan - this looks very nice, thank you! To get this PR merged, some things are still missing:

Some bookkeeping: adding yourself to the creators.json file, and adding a changelog entry (this item should go under the "features" category)
Updating the documentation: there is a screenshot of the pick mode in our GUI usage section - it should be updated to match the new look of the pick handle
Include rebuilt client js - this is done using the command tox -e build_client. See the bottom of this documentation section. If you are struggling with this step, let me know, this is also something I can do post-merge.

Thanks again for taking care of this!

Looks good, both code changes and the new screenshot. I added two comments about the documentation changes - when these are resolved, the pull request will be perfect

Thanks! I've made the requested changes. I'll include the rebuilt client js too in a while.

Thanks, merged! :tada:


Installing notes addon causes yarn run storybook to fail

If you are reporting a bug or requesting support, start here:
Bug or support request summary
On ubuntu, using create-react-app and getstorybook command, adding the 'notes' addon (just installing it) causes start-storybook to fail, was trying to follow along with https://storybook.js.org/addons/using-addons/
Steps to reproduce
install create-react-app
install storybook-cli
create new app with create-react-app
install storybook notes addon
attempt to 'yarn run storybook'
Please specify which version of Storybook and optionally any affected addons that you're running
<EMAIL_ADDRESS><EMAIL_ADDRESS>@storybook/react v3.3.15
<EMAIL_ADDRESS>Affected platforms
16.04.1-Ubuntu

install create-react-app
install storybook-cli
create new app with create-react-app
install storybook notes addon
attempt to 'yarn run storybook'

I assume it also includes running getstorybook after third step, right?

I can't reproduce the issue on Ubuntu 16.04

ah you're correct, yes.

I'm going back and double checking, and I think the main issue may be that I wasn't following the addons guide well -
I used npm install --save-dev @storybook/addon-notes instead of yarn add -D @storybook/addon-notes after trying with yarn it appears to work. do you want me to close, or make a PR for the addon help page? Thanks for taking a look

updated repro steps:

create-react-app test-app
cd test-app
getstorybook
(optional) yarn run storybook
npm i --save-dev @storybook/addon-notes
yarn run storybook
6.1. Expected: Storybook runs
6.2 Actual: Storybook fails to run

made a PR for docs, if that's acceptable - not certain why installing from NPM vs Installing from yarn causes it to fail. please let me know your thoughts, thanks again for all the hard work on this great software!

Looks like you need to run npm install in your project before adding any dependencies using npm

I'll double check that when I get time, thanks for looking at this, @Hypnosphi

Documentation fix published as 3.4.0


⚠ Bofrost.fr has degraded performance

In 24978a9, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1078 ms

Resolved: Bofrost.fr performance has improved in c03220c after 4 minutes.


Config Context Schemas don't allow local $refs

Environment

Nautobot version (Docker tag too if applicable): 1.4.7
Python version: 3.7
Database platform, version: postgres
Middleware(s):

Steps to Reproduce

Create a git repository with the following contents:

directory structure:
.
└── config_context_schemas
    ├── dns.json
    └── test.json

test.json:
{
    "_metadata": {
        "name": "Config Context Schema Data",
        "description": "General Schema."
    },
    "data_schema": {
        "title": "data",
        "type": "object",
        "properties": {
            "dns": {
                "$ref": "./dns.json"
            }
        },
        "additionalProperties": false
    }
}

dns.json:
{
    "_metadata": {
        "name": "Config Context Schema DNS",
        "description": "DNS Schema."
    },
    "data_schema": {
        "title": "dns",
        "type": "object",
        "properties": {
            "servers": {
                "type": "object",
                "properties": {
                    "ipv4": {
                        "type": "string",
                        "format": "ipv4"
                    },
                    "ipv6": {
                        "type": "string",
                        "format": "ipv6"
                    }
                }
            }
        }
    }
}

Add the gitrepo to Nautobot as providing config context schemas and sync
Create a config context with the following data:

{
        "dns": {
            "servers": {
                "ipv4": "<IP_ADDRESS>",
                "ipv6": "2606:4700:4700::1111"
            }
        }
}

Expected Behavior
The config context should validate.

Observed Behavior
a <class 'jsonschema.exceptions.RefResolutionError'> occurs.

 ERROR Internal Server Error: /extras/config-contexts/add/ - django.request - log - /usr/local/lib/python3.7/site-packages/django/utils/log.py:230
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/jsonschema/validators.py", line 850, in resolve_from_url
    document = self.store[url]
  File "/usr/local/lib/python3.7/site-packages/jsonschema/_utils.py", line 28, in __getitem__
    return self.store[self.normalize(uri)]
KeyError: './dns.json'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/jsonschema/validators.py", line 853, in resolve_from_url
    document = self.resolve_remote(url)
  File "/usr/local/lib/python3.7/site-packages/jsonschema/validators.py", line 959, in resolve_remote
    with urlopen(uri) as url:
  File "/usr/local/lib/python3.7/urllib/request.py", line 222, in urlopen
    return opener.open(url, data, timeout)
  File "/usr/local/lib/python3.7/urllib/request.py", line 510, in open
    req = Request(fullurl, data)
  File "/usr/local/lib/python3.7/urllib/request.py", line 328, in __init__
    self.full_url = url
  File "/usr/local/lib/python3.7/urllib/request.py", line 354, in full_url
    self._parse()
  File "/usr/local/lib/python3.7/urllib/request.py", line 383, in _parse
    raise ValueError("unknown url type: %r" % self.full_url)
ValueError: unknown url type: './dns.json'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", line 47, in inner
    response = get_response(request)
  File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 181, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 70, in view
    return self.dispatch(request, *args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/nautobot/core/views/generic.py", line 378, in dispatch
    return super().dispatch(request, *args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/nautobot/utilities/views.py", line 116, in dispatch
    return super().dispatch(request, *args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 98, in dispatch
    return handler(request, *args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/nautobot/core/views/generic.py", line 406, in post
    if form.is_valid():
  File "/usr/local/lib/python3.7/site-packages/django/forms/forms.py", line 175, in is_valid
    return self.is_bound and not self.errors
  File "/usr/local/lib/python3.7/site-packages/django/forms/forms.py", line 170, in errors
    self.full_clean()
  File "/usr/local/lib/python3.7/site-packages/django/forms/forms.py", line 374, in full_clean
    self._post_clean()
  File "/usr/local/lib/python3.7/site-packages/django/forms/models.py", line 413, in _post_clean
    self.instance.full_clean(exclude=exclude, validate_unique=False)
  File "/usr/local/lib/python3.7/site-packages/django/db/models/base.py", line 1236, in full_clean
    self.clean()
  File "/usr/local/lib/python3.7/site-packages/nautobot/extras/models/models.py", line 138, in clean
    self._validate_with_schema("data", "schema")
  File "/usr/local/lib/python3.7/site-packages/nautobot/extras/models/models.py", line 61, in _validate_with_schema
    Draft7Validator(schema.data_schema, format_checker=draft7_format_checker).validate(data)
  File "/usr/local/lib/python3.7/site-packages/jsonschema/validators.py", line 267, in validate
    for error in self.iter_errors(*args, **kwargs):
  File "/usr/local/lib/python3.7/site-packages/jsonschema/validators.py", line 242, in iter_errors
    for error in errors:
  File "/usr/local/lib/python3.7/site-packages/jsonschema/_validators.py", line 336, in properties
    schema_path=property,
  File "/usr/local/lib/python3.7/site-packages/jsonschema/validators.py", line 259, in descend
    for error in self.evolve(schema=schema).iter_errors(instance):
  File "/usr/local/lib/python3.7/site-packages/jsonschema/validators.py", line 242, in iter_errors
    for error in errors:
  File "/usr/local/lib/python3.7/site-packages/jsonschema/_validators.py", line 294, in ref
    scope, resolved = validator.resolver.resolve(ref)
  File "/usr/local/lib/python3.7/site-packages/jsonschema/validators.py", line 842, in resolve
    return url, self._remote_cache(url)
  File "/usr/local/lib/python3.7/site-packages/jsonschema/validators.py", line 855, in resolve_from_url
    raise exceptions.RefResolutionError(exc)
jsonschema.exceptions.RefResolutionError: unknown url type: './dns.json'

Is this relevant? https://python-jsonschema.readthedocs.io/en/stable/faq/#how-do-i-configure-a-base-uri-for-ref-resolution-using-local-files
As in have you tried to just use $ref": "dns.json"?

Use a file within the directory as your base URI rather than the directory itself, i.e. file://foo/bar/baz.json, which will of course cause baz.json to be removed while resolving relative URIs.

@jathanism thanks for the idea, however removing the './' does not work... you can test with my gitrepo https://github.com/nniehoff/scratch if you don't want to configure one by hand

I guess another way of asking is I wonder if we might need to be required to set the base_uri when processing the schemas?

This made it work:
https://github.com/jathanism/nautobot-scratch/blob/main/config_context_schemas/test3.json#L11
Basically providing a hard-coded absolute file path. So we need to makes sure that the validator is using the base_uri so that we can use relative paths there. Otherwise Nautobot has no way to tell from where to read that $ref file.

This is a good workaround, we'll have to figure out what the path is in the containers, looks like it's $NAUTOBOT_ROOT/git/$GIT_REPO_NAME but I feel like $ref to a relative path is a very common practice.

This is a good workaround, we'll have to figure out what the path is in the containers, looks like it's $NAUTOBOT_ROOT/git/$GIT_REPO_NAME but I feel like $ref to a relative path is a very common practice.

What you want is $GIT_ROOT/$REPO_NAME.

This is a good workaround, we'll have to figure out what the path is in the containers, looks like it's $NAUTOBOT_ROOT/git/$GIT_REPO_NAME but I feel like $ref to a relative path is a very common practice.

What you want is $GIT_ROOT/$REPO_NAME.
So for example in this case if we set the base_uri in the validator to $GIT_ROOT/$REPO_NAME/config_context_schemas/ then you would be able to use relative paths like dns.json or even subdir/foo.json, per that link I provided above.

I used "$ref": "file:///opt/nautobot/git/render-config-context/config_context_schemas/dns.json" and some other variations but with no luck. I once more receive
<urlopen error [Errno 2] No such file or directory: '/opt/nautobot/git/render-config-context/config_context_schemas/dns.json'>
It could be the case that I have something wrong on the URI however I found the relevant file in a worker container as shown below
nautobot@7e6d5bd8d7ed:~/git/render-config-context/config_context_schemas$ realpath dns.json
/opt/nautobot/git/render-config-context/config_context_schemas/dns.json
It looks as if the path is ok to me.

$GIT_ROOT can be found by the following:
$ nautobot-server shell
Python 3.7.14 (default, Sep 13 2022, 02:30:55)
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveConsole)
>>> from django.conf import settings
>>> settings.GIT_ROOT
'/opt/nautobot/git'

The default as you can see above is /opt/nautobot/git the $REPO_NAME we are referring to is the GitRepository slug from Nautobot for the git repo the config context schemas are stored in.  However, using this full path as suggested by @jathanism even in the demo environment doesn't seem to work for me either.  @jathanism could this be due to the fact our workers are on separate nodes and $GIT_ROOT is not a shared filesystem?

$GIT_ROOT can be found by the following:
$ nautobot-server shell
Python 3.7.14 (default, Sep 13 2022, 02:30:55)
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveConsole)
>>> from django.conf import settings
>>> settings.GIT_ROOT
'/opt/nautobot/git'

The default as you can see above is /opt/nautobot/git the $REPO_NAME we are referring to is the GitRepository slug from Nautobot for the git repo the config context schemas are stored in. However, using this full path as suggested by @jathanism even in the demo environment doesn't seem to work for me either. @jathanism could this be due to the fact our workers are on separate nodes and $GIT_ROOT is not a shared filesystem?

Yes, it's going to have to be something that is locally resolved and not hard-coded. In my case, obviously having the worker on the same system as the server obviates this problem.

Marking this as a feature since this would be new functionality.

@nniehoff I have a small tool that I build, that converts normal json schemas to the files you need to upload. I use it such that vscode can use the json schemas to verify the contexts local before uploading them. Would that be of any interest?

@KalleDK while that's an interesting work around and I believe what we are doing in this specific instance as a workaround I feel like $ref is a very common use case and should still be supported by Nautobot


Blazor WASM App + Azure Static Website + CosmosDB binding + Github Actions = 'cosmosDB' with missing or invalid direction

Bug Report
I used the Github action file that Azure auto generates with. I am using "Microsoft.NET.Sdk.Functions" Version="4.1.0"
My code:
        [FunctionName("ProductsGet")]
        public static IActionResult GetAllProducts(
    [HttpTrigger(AuthorizationLevel.Anonymous, "get", Route = "products")] HttpRequest req,
    [CosmosDB(
        databaseName: "productsdb",
        collectionName: "products",
        ConnectionStringSetting = "CosmosDBConnection")]
        IEnumerable<Product> products,
    ILogger log)
        {
            log.LogInformation("Getting products");
            return new OkObjectResult(products);
        }

It run fines locally, but when it gets to the Build and Deploy stage of the Github action it throws this error:

---End of Oryx build logs---
Function Runtime Information. OS: windows, Functions Runtime: ~4, dotnet version: 6.0
Finished building function app with Oryx
Error in processing api build artifacts: the file 'ProductsGet/function.json' specifies a binding of type 'cosmosDB' with missing or invalid direction ''. Visit https://github.com/Azure/azure-functions-host/wiki/function.json for more information.
For further information, please visit the Azure Static Web Apps documentation at https://docs.microsoft.com/en-us/azure/static-web-apps/
If you believe this behavior is unexpected, please raise a GitHub issue at https://github.com/azure/static-web-apps/issues/
Exiting

The project is like this one, except I tried to integrate CosmosDB

I'm running into a similar issue using the new beta package Microsoft.Azure.WebJobs.Extensions.Tables which generates this message for a table binding to a TableClient.
The code below (simplified) works fine locally, but errors out after building on Oryx.
[FunctionName("FUNCTION-NAME")]
public IActionResult Run(
    [HttpTrigger(AuthorizationLevel.Anonymous, "get")] HttpRequest req,
    [Table("ENTITIES")] TableClient tableClient, ILogger log)
{
    return new OkObjectResult(tableClient.Query<ENTITY>().ToList());
}

The actual message:

Error in processing api build artifacts: the file 'FUNCTION-NAME/function.json' specifies a binding of type 'table' with missing or invalid direction ''. Visit https://github.com/Azure/azure-functions-host/wiki/function.json for more information.

I have the same issue with importing SignalR
Function Runtime Information. OS: windows, Functions Runtime: ~4, dotnet version: 6.0
Finished building function app with Oryx
Error in processing api build artifacts: the file 'Negotiate/function.json' specifies a binding of type 'signalRConnectionInfo' with missing or invalid direction ''. Visit https://github.com/Azure/azure-functions-host/wiki/function.json for more information.

Repository

I am running into the same issue with CosmosDB after updating my .csproj to Target Framework net6.0 and Azure Functions Version v4. The Oryx build fails in a PR github action.
These are all the csproj changes I made.

The Error I see is:

I don't understand why function.json is mentioned. These should be inproc.

I think this might be an issue introduced by Microsoft.NET.Sdk.Functions 4.1.0. Can you try using 4.0.1 to see if the issue persists?

Thank you @anthonychu, that does the trick!
Downgraded the mentioned package Microsoft.NET.Sdk.Functions from version 4.1.0 to 4.0.1 and the build error on my GitHub actions workflow disappeared.

Issue is fixed and rolled out. Please let us know, if you still run into the same issue.


Lit element

I won't merge this yet as I'm still tracking one remaining place in a FRA that needs to be fixed, but it's ready for review with the hope of merging tomorrow!

All the places that were relying on iron-iconset-svg or setting custom properties from non-components have been fixed up. This is now ready to merge.


Synbols domain ids

Currently Synbols dataset returns a task ids array of None because it's only available for class incremental.
Although we could use it in instance incremental by adding new domains every time, those domains could be the font. I think it exists for Synbols but I'm not sure yet where this information can be gathered.

See #84

Merged in https://github.com/Continvvm/continuum/commit/9e15e1a15dd9071ee3ff721df85ce4592e7d7ec1


can i translate this into chinese and re upload it on Thunderstore?

I'll label the original plugin,and i already done the translate
SubtitlesAPI.zip

I'll label the original plugin,and i already done the translate SubtitlesAPI.zip

@S961 Alternatively you could open a PR to add a new Chinese localization file and set the locale to CN in the config. :) I can help out if needed.
This location would be where you'd add a new file ChineseSubtitleLocalization.cs and add the configuration there.

oops,Uploads are disabled.
ChineseSubtitleLocalization.zip

i can't add the file. Uploads are disabled.

@S961 I added the new localization pack and it should be available on SubtitlesAPI.
Once you have the version 0.0.5, you can go to Thunderstore Mod Manager's Edit config and look for BepInEx/config/JustJelly.SubtitlesAPI.cfg then you can set the locale to zh.

ok


Fix setstat response

Hello, hope you're going well.
I found out that the setstat methods return the wrong type according to the version 3 specification draft.
Also I added a doc link to help contributors to find specification for the Status type.
Hope this is good for you, and have a nice day!

Thank you, release will be within 2 weeks


Create container for app and deploy to Azure

The goal here is to automate and package our app using a container utility. For reference, use the following article - https://betterprogramming.pub/host-your-static-website-in-azure-as-a-docker-container-be127f00267d


add decode table annotation definition

Contributor Checklist

[ ] Did you add at least one test demonstrating the PR?
[x] Did you delete any extraneous printlns/debugging code?
[x] Did you specify the type of improvement?

Type of Improvement

new feature/API

I feel like we might get away without this change.
Afaik this annotation is essentially ignored by the firrtl compiler, thus we could just discard it at the bridge in chiseltest.


Image to Image?

Does the coreML SD2 version support image to image?

Not that I can tell, and does not look easy to add.
I see where it is initiated with noise, but that is done in the conversion script - not at run time...

Image2Image PR: https://github.com/apple/ml-stable-diffusion/pull/73


Tests fail running on ubuntu 22.04 container

Steps to reproduce

run in ubuntu 22.04 container

podman run -it ubuntu:22.04

follow the installation instructions from README

Tests that fail:

72% tests passed, 9 tests failed out of 32

Total Test time (real) =   8.21 sec

The following tests FAILED:
	  8 - gpuocelot_ir_TestLLVMInstructions (Failed)
	 15 - gpuocelot_cuda_TestCudaMalloc (Failed)
	 18 - gpuocelot_cuda_TestCudaTexture2D (Failed)
	 19 - gpuocelot_cuda_TestCudaTexture3D (Failed)
	 20 - gpuocelot_cuda_TestCudaTextureArray (Failed)
	 21 - gpuocelot_cuda_TestCudaTextureCube (Failed)
	 23 - gpuocelot_cuda_TestIndirectFunctionCall (Failed)
	 24 - gpuocelot_cuda_TestIndirectFunctionCallDriver (Failed)
	 26 - gpuocelot_cuda_TestPTXAssembly (Failed)

I'm not sure how much of the environment will help to debug. Here's the nvcc version:
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2021 NVIDIA Corporation
Built on Thu_Nov_18_09:45:25_PST_2021
Cuda compilation tools, release 11.5, V11.5.119
Build cuda_11.5.r11.5/compiler.30672275_0

Hi @ggeorgakoudis , thank you for your report. Please share the ctest -V log, not just ctest. I've added a README paragraph on this: https://github.com/gpuocelot/gpuocelot?tab=readme-ov-file#issue-reporting

ctest.log

Thanks! Most of the failures are with Initialization error:no CUDA-capable device is detected error, meaning that gpuocelot unexpectedly tries to reach out to a real CUDA device, instead of doing a GPUOcelot-based emulation.

I think this issue is related to this: https://github.com/gpuocelot/gpuocelot/discussions/5#discussioncomment-9174656


Enable touch using Hammer.js. Fire drag events on press

I am using angular2-grid in my angular2 web application and it is working prefectly. Now I need to enable touch so that drag and drop can be done using mobile devices as well. To this end I have integrated Hammer.js.
Now, I need to fire onDragStart and onDragStop events on the Hammer.js' press and pressup events. How do I achieve this?
Here is a sample of firing one event inside of another. What is the equivalent on MouseEvent in angular-grid?

I've fixed the grid so that it will work with touch events now so hopefully you can use the regular mouse event stuff. I'll do a publish when I'm done with my current batch of changes and you can give it a go :)

Ben, thanks very much for looking into this issue immediately.
I reviewed your commit and see the changes you have done with mouse and touch events. I am able to handle those events as well. I see you have updated your demo site (https://bmorton.co.uk/angular/) and that is functioning very nicely for mobile devices.
But, neither the mouse not the touch events are working in my application. As in, while I see they are being fired and I am able to handle them, the drag functionality is still not working. Can you please let me know what I am missing?

Yeah, there's a few other things I want to look into first, but I'll try and get it published by end of day today

This should be published. Is it working correctly for you now?


Update migrate-from-microsoft-365-business-to-microsoft-365-enterpris…

…e.md
Removed references of OUTlook customer manager as it has been deprecated

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/3384

@JoeDavies-MSFT Please merge this PR. Thanks.


Cascading File Loading

Now that the File Loader is up, the next milestone for that feature is to allow for cascading fileloading:
$manager->addFiles([
   ['some/file1.php', 'some/other/file1.php'],
   ['some/file2.php', 'some/other/file2.php'],
]);

This would mean that it first loads some/file1.php and then loads some/other/file1.php, overwriting any values from the first. This is useful for users who want to have defaults in one file and then load precedence over them.
They should be allowed to load as many cascades as they like.
It may also be worth looking at using the native loadDefaults() that is in ManagesItemsTrait
Related to #36 and #35

I think I'm shelving this for now. It's going to add a performance drag and I'm not sure people need it. I'll keep the issue open and see if any feedback rolls in.


[VAX-1074] Database does not exist / support running the generator twice

Running the generator twice to create two different projects runs into a database name not found error.
As per report at https://discord.com/channels/933657521581858818/1079688869852753981/1154842122571223091
From SyncLinear.com | VAX-1074

I am having a similar issue which makes it impossible (?) for me to start working with electric.
What I have done:
npx create-electric-app@latest capturing_electric_2
cd capturing_electric_2
npm i
npm run backend:start
npm run db:migrate

The result:
PS C:\Users\alexa\capturing_electric_2> npm run backend:start

><EMAIL_ADDRESS>backend:start
> docker compose --env-file backend/compose/.envrc -f backend/compose/docker-compose.yaml up

[+] Running 2/2
 ✔ Container compose-postgres-1  Created                                                                                0.4s
 ✔ Container compose-electric-1  Recreated                                                                                0.2s
Attaching to compose-electric-1, compose-postgres-1
compose-postgres-1  |
compose-postgres-1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
compose-postgres-1  |
compose-postgres-1  |
compose-postgres-1  | 2023-09-25 12:02:39.353 GMT [1] LOG:  starting PostgreSQL 14.9 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
compose-postgres-1  | 2023-09-25 12:02:39.353 GMT [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
compose-postgres-1  | 2023-09-25 12:02:39.353 GMT [1] LOG:  listening on IPv6 address "::", port 5432
compose-postgres-1  | 2023-09-25 12:02:39.382 GMT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
compose-postgres-1  | 2023-09-25 12:02:39.389 GMT [22] LOG:  database system was shut down at 2023-09-21 10:04:56 GMT
compose-postgres-1  | 2023-09-25 12:02:39.416 GMT [22] LOG:  recovered replication state of node 1 to 0/0
compose-postgres-1  | 2023-09-25 12:02:39.422 GMT [1] LOG:  database system is ready to accept connections
compose-postgres-1  | 2023-09-25 12:02:39.457 GMT [29] LOG:  logical replication apply worker for subscription "postgres_1" has started
compose-electric-1  | 12:02:40.058 pid=<0.2195.0> [info] Running Electric.Plug.Router with Bandit 1.0.0-pre.14 at <IP_ADDRESS>:5133 (http)
compose-electric-1  | 12:02:40.058 pid=<0.2812.0> origin=postgres_1 [info] connect: %{database: ~c"capturing_electric_2", host: ~c"postgres", port: 5432, ssl: false, timeout: 5000, username: ~c"postgres"}
compose-postgres-1  | 2023-09-25 12:02:40.061 GMT [29] ERROR:  could not connect to the publisher: connection to server at "electric" (<IP_ADDRESS>), port 5433 failed: FATAL:  Electric replication is not ready, missing schema for postgres_1
compose-postgres-1  | 2023-09-25 12:02:40.062 GMT [1] LOG:  background worker "logical replication worker" (PID 29) exited with exit code 1
compose-postgres-1  | 2023-09-25 12:02:40.066 GMT [30] FATAL:  database "capturing_electric_2" does not exist

log in docker, compose-electric-1:
2023-09-25 14:02:40 12:02:40.058 pid=<0.2195.0> [info] Running Electric.Plug.Router with Bandit 1.0.0-pre.14 at <IP_ADDRESS>:5133 (http)
2023-09-25 14:02:40 12:02:40.058 pid=<0.2812.0> origin=postgres_1 [info] connect: %{database: ~c"capturing_electric_2", host: ~c"postgres", port: 5432, ssl: false, timeout: 5000, username: ~c"postgres"}
2023-09-25 14:02:40 12:02:40.066 pid=<0.2812.0> origin=postgres_1 [error] initialization for postgresql failed with reason: {:error, {:error, :fatal, "3D000", :invalid_catalog_name, "database \"capturing_electric_2\" does not exist", [file: "postinit.c", line: "885", routine: "InitPostgres", severity: "FATAL"]}}

log in docker, compose-postgres-1:
2023-09-25 14:02:39
2023-09-25 14:02:39 PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-09-25 14:02:39
2023-09-25 14:02:39 2023-09-25 12:02:39.353 GMT [1] LOG:  starting PostgreSQL 14.9 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
2023-09-25 14:02:39 2023-09-25 12:02:39.353 GMT [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2023-09-25 14:02:39 2023-09-25 12:02:39.353 GMT [1] LOG:  listening on IPv6 address "::", port 5432
2023-09-25 14:02:39 2023-09-25 12:02:39.382 GMT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-09-25 14:02:39 2023-09-25 12:02:39.389 GMT [22] LOG:  database system was shut down at 2023-09-21 10:04:56 GMT
2023-09-25 14:02:39 2023-09-25 12:02:39.416 GMT [22] LOG:  recovered replication state of node 1 to 0/0
2023-09-25 14:02:39 2023-09-25 12:02:39.422 GMT [1] LOG:  database system is ready to accept connections
2023-09-25 14:02:39 2023-09-25 12:02:39.457 GMT [29] LOG:  logical replication apply worker for subscription "postgres_1" has started
2023-09-25 14:02:40 2023-09-25 12:02:40.061 GMT [29] ERROR:  could not connect to the publisher: connection to server at "electric" (<IP_ADDRESS>), port 5433 failed: FATAL:  Electric replication is not ready, missing schema for postgres_1
2023-09-25 14:02:40 2023-09-25 12:02:40.062 GMT [1] LOG:  background worker "logical replication worker" (PID 29) exited with exit code 1
2023-09-25 14:02:40 2023-09-25 12:02:40.066 GMT [30] FATAL:  database "capturing_electric_2" does not exist

We deliberately designed the create-electric-app package such that our docker compose creates a PG database with the name of the project, i.e. npx create-electric-app@latest foo expects PG to have a DB named foo.
How this works is:

the generator writes the name of the app as an environment variable APP_NAME to .envrc
(https://github.com/electric-sql/electric/blob/main/examples/starter/src/index.ts#L76)
our docker compose file creates a DB named after the APP_NAME environment variable. If that environment variable is absent it uses the default name electric, cf. https://github.com/electric-sql/electric/blob/main/examples/starter/template/backend/compose/docker-compose.yaml#L15

I believe that the DB is only created the first time that the Docker image is ran.
So next time you run it (e.g. for a different project) the volumes are still there and so it does not create your new database. So the problem comes from the fact that both projects are using the same Docker image for PG and thus sharing the same database.

Yes, basically the backend for the previous starter is still running.
@kevin-dp do you think the code for extracting the dynamic PG port could be a cause here -- i.e.: does it get there first matching port, when potentially multiple containers are running? If so that could actually be a simple practical fix?

@thruflo I don't think the port is the issue. For the above bug you don't need the backend of the previous starter to be running. It suffices that you have ran the backend of the previous starter at least once in the past. Because when you ran the backend, it created a PG DB named after the name of your app.
Now, when you run the starter again for a new project, it will re-use the same Docker image for PG, it will find the volume for that image and so it will re-use the volume and hence not create a new database for your app. As a result, your new app does not find its database on PG because it was never created.

The accepted answer in this thread is useful to understand the problem:
https://stackoverflow.com/questions/56657683/postgres-docker-image-is-not-creating-database-with-custom-name

Yup, got it, ta.
So it looks like we could avoid the clashes by prefixing the container name in the generated docker compose with the app name. I've raised #497 to address.

I'm closing this issue in favor of #497.

Being taken care of in VAX-1087


feat(create-rspack): add template react-ts

Related issue (if exists)

Summary
add react+typescript template for create-rspack.

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

!canary

sry.i don't understand your mean😂

!canary

sry.i don't understand your mean😂

just trigger a canary release

!canary

sry.i don't understand your mean😂

just trigger a canary release

ok,i'll change it.

@hardfist excuse me, do i need to change anything? can you help me? 🤣

@hardfist excuse me, do i need to change anything? can you help me? 🤣

no need, thanks

@hardfist excuse me, do i need to change anything? can you help me? 🤣

no need, thanks

ok, thanks. 👍


Job permanently running in 'preparing' status regardless of job or compute (cluster + instance)

Package Name: azure-ai-ml
Package Version:  1.4.0
Operating System: W11
Python Version: 3.8

Describe the bug
Running lab 2 from the course material in git (https://github.com/MicrosoftLearning/mslearn-azure-ml) which highlighted the issue. Tested it out using my own scripts. Lab is in perpetual status along with any other jobs proceeding it regardless of compute, or region (see image) or job command
Evidence this worked in the past:

To Reproduce
Steps to reproduce the behavior:

import the git repo shared in the 'describe the bug' and run lab 2 in Azure Machine learning
Create a storage account that matches the assets described in the jupyter notebook or clone directly from the instructions

Expected behavior
job should run and complete after 20-60 seconds
Screenshots

Additional context
Azure status declare AML to up and running. Is there something up with the compute?

@rytsang Could you please look into this for Execution Service?

closing as obsolete


[PE-D][Tester B] Loading corrupted data file doesn't show any error message

After putting invalid inputs inside the datafile, loading the app displays an empty page instead of informing the user that the data file is wrong.

Labels: type.FeatureFlaw severity.Low
original: QinHaichen12/ped#16

this behavior is inherited from ab3 and also explicitly mentioned in user guide here

Not important enough to be resolved in v1.6 since users shouldn't change the data file if they are not familiar with it as mentioned in UG


Scavengers: fix /scavengerstatus

I may or may not have accidentally deleted too much when going through add applying escapeHTML to everything...  oops, sorry!

I should probably mention in our code style guide; we shouldn't really ever treat a function as a variable (i.e. we should never take advantage of first-class functions). .map(a => toId(a)) is faster and probably more readable than .map(toId)

OMG so sorry, how did i omit the ' , ' in the join


Fix teleport command doc

There seems to be something wrong with the command docs for teleport and camera_set_zoom. It looks weird in the ESC reference.

Closed by #327


crystal browser does not shows begin ast node after a return

def m
  return begin
    puts "foo"
    1
  end
end

p m

shows
def m
  return   puts("foo")
  1

end
p(m)

This is also important because it should work well also for macros (they use the same to_s).


feat: include eslint

📑 Description
Added eslint configuration file.
✅ Checks

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

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


New version: Fabio286.antares version 0.7.15

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/115453&drop=dogfoodAlpha

@wingetbot run


export to onnx or torch jit?

If you are not using distributed experts, all the operators are implemented using PyTorch's native operators. I think it is possible to export FastMoE's model to ONNX or Torch Script. Otherwise, you may need to write a script and aggregate the experts together.
BTW, if you are looking for inference system for MoE, you may check out Harry Chen's work which is elastic and high-performance.


Journal the ephemeral DB data

The ephemeral database data should be journaled so that it can persist between runs.

Journalling the ephemeral database data is not necessary as the purpose of an ephemeral database is to store temporary data that is not meant to persist between runs. Ephemeral databases are typically used for caching or temporary storage purposes. If you need to persist data between runs, it is recommended to use a persistent database solution such as a relational database or a distributed ledger like Ethereum.


Show tag keys performance on 1.4.1 (tsi1)

Bug report
System info:
influxDB 1.4.1 with tsi1
Amazon Linux AMI release 2015.09 (centos based)
Machine type: r4.4xlarge
Description:
We have a high cardinality use case, as can be seen by:
SELECT numSeries FROM "_internal".."database" WHERE time > now() - 10s GROUP BY "database" ORDER BY desc LIMIT 1

name: database
tags: database=something
time                numSeries
----                ---------
1510849360000000000 31199677

This is mostly due to a specific measurement.
On 1.3.7 when running "show tag keys from measurement" it executes in a few seconds.
We tried to upgrade to 1.4.1, to do so we did the following:

stop influx
delete the previous index files - given that this version has incompatible indexes as stated on #8857
use influx_inspect inmem2tsi to create the new index files
start influx

Expected behavior:
Have similar performance between 1.3.7 and 1.4.1
Actual behavior:
"show tag keys from measurement"  takes around 10 minutes to execute.
Tried other lower cardinality measurements on the same database and the performance looks similar to 1.3.7
Additional info:
We are trying to build a way to reproduce the issue that we can share, possibly a script that generates similar cardinality but we haven't had time to finish it yet.

Hi @reistiago,
How many retention policies do you have? Could you provide SHOW RETENTION POLICIES ON "something"?
One of the bugs we fixed with SHOW TAG KEYS was previously it was only querying the default retention policy, where as in 1.4.0 it will query all retention policies in the database.
If you have other retention policies on your database that could be part of the reason why it's now taking longer than it did on 1.3.7. Especially if those retention policies contain the measurement.
P.S. we now have an explicit cardinality command, which is a bit easier to remember than the query for the _internal stats: SHOW SERIES CARDINALITY ON "something"

@reistiago Thanks for the bug report. Can you run a profile while the query is running? That will help us narrow down what the issue is.

Run the query.
Go to http://YOURHOST:8086/debug/pprof/all?cpu=1. This request can take 30s to execute.

This will return a profiles.tar.gz file. Can you post that to this issue?

@e-dard
Only the default (autogen):

> SHOW RETENTION POLICIES on something;
name    duration shardGroupDuration replicaN default
----    -------- ------------------ -------- -------
autogen 0s       168h0m0s           1        true

I know about SHOW SERIES CARDINALITY ON "something" but this is only available on 1.4.x right? We had to revert back to 1.3.7 otherwise the system was unusable (it relies on show tag keys).
@benbjohnson like I said above, we had to revert back to 1.3.7 so I can't really do that now, and it takes quite a long time (hours) to recreate the index based on our current dataset. I'll try to get it tomorrow.

@reistiago OK, we understand. We can try and reproduce our side. Roughly how many measurements do you have in "something"? Tens, hundreds, thousands?

@e-dard very few. Around 10 I would say.

@benbjohnson @e-dard
Attached a few pprof files while the query was executing, files name should be self explanatory.
Don't know how long did the query took to run because I got busy with something else in the meantime and didn't noticed when it finished. But it took longer then 23 minutes.
profiles-query-running-for-4-minutes.tag.gz
profiles-query-running-for-7-minutes.tar.gz
profiles-query-running-for-9-minutes.tar.gz
profiles-query-running-for-13-minutes.tar.gz
profiles-query-running-for-18-minutes.tar.gz
profiles-query-running-for-22-minutes.tar.gz
profiles-query-running-for-less-then-one-minute.tar.gz
In case this is useful, looking at the output of top, it looks like just one of the cores is being used, and it's spending most of the time waiting.

Influx log while the query was running was mostly:
...
[I] 2017-11-17T12:58:00Z compact id=2287 (0/0) (0/0) (0/0) (0/0) engine=tsm1
[I] 2017-11-17T12:58:01Z compact id=2083 (0/0) (0/0) (0/0) (0/0) engine=tsm1
[I] 2017-11-17T12:58:01Z compact id=2288 (0/0) (0/0) (0/0) (0/0) engine=tsm1
[I] 2017-11-17T12:58:01Z compact id=2287 (0/0) (0/0) (0/0) (0/0) engine=tsm1
[I] 2017-11-17T12:58:02Z compact id=2083 (0/0) (0/0) (0/0) (0/0) engine=tsm1
[I] 2017-11-17T12:58:02Z compact id=2288 (0/0) (0/0) (0/0) (0/0) engine=tsm1
[I] 2017-11-17T12:58:02Z compact id=2287 (0/0) (0/0) (0/0) (0/0) engine=tsm1
[I] 2017-11-17T12:58:03Z compact id=2083 (0/0) (0/0) (0/0) (0/0) engine=tsm1
[I] 2017-11-17T12:58:03Z compact id=2288 (0/0) (0/0) (0/0) (0/0) engine=tsm1
[I] 2017-11-17T12:58:03Z compact id=2287 (0/0) (0/0) (0/0) (0/0) engine=tsm1
[I] 2017-11-17T12:58:04Z compact id=2083 (0/0) (0/0) (0/0) (0/0) engine=tsm1
...

Using the new method to calculate the cardinality returns:
> SHOW SERIES CARDINALITY ON something;
cardinality estimation
----------------------
31211064

Space occupied in disk for that database data folder: 64G
I've kept an image of this machine, so running further tests should be quicker in case you need more information.

@reistiago do you have any idea how many tag keys you have in your database? Essentially:
$ influx -database "something" -exectute 'SHOW TAG KEYS FROM measurement' | wc -l

You could run it on 1.3.7; the answer would be the same. I'm trying to repro but after writing 30M series I still get almost instantaneous answers on 1.4.1. My working theory now is that you have many tag keys, rather than just many tag values.

@reistiago Ah I think I have reproduced it... It's the number of shards you have that's the problem.  It looks like you have around a 1,000 shards at the moment. I'll look into optimising the query when there are many shards.
However, (and this advice isn't merely to improve the performance of this query), you should really consider an alternative retention policy unless you're dropping data a lot.
Fewer shards are going to cause less stress on the system, and will significantly reduce the size of your data directory, because there will be fewer (but larger) tsi1 indexes. This results in an overall size reduction because there is less index overhead. Also, compression will likely be improved with fewer shards and there may well be a write performance improvement.
What's your current retention policy duration?

@e-dard assuming that shard equal the number of folders in /data/{database}/{retention-policy} your guess is correct about the number of shards: 1043.
Only 9 tag keys on that measurement, so you are likely correct that the problem is not here.
We are using the default retention policy, so infinite.
Increasing the shard size / duration will probably cause slower reads correct?

@e-dard sorry for the question, since it's only tangentially related with the issue.
If I alter the retention policy (autogen in this case) with:
alter retention policy "autogen" ON "something" SHARD DURATION 1000w
Is this retroactively applied to the shard already existent? Or this must be done on db creation?

@e-dard any news on this issue / pr?

@reistiago a fix has been merged for this. I believe it will be back-ported into a 1.4.3 release, though I don't know exactly when the release will ship. I would expect within weeks though.
Regarding your other question—yes ALTER RETENTION POLICY only applies to future shards. Currently, restructuring your old shards has to be done using alternative tooling, e.g., with an export using influx_inspect and then a reimport.

@e-dard  I still have the machine image with the problem so will give it a try when available.
Thanks for the reply regarding the shards configuration.

@e-dard this ended up not being back ported correct?
Also looking at the 1.5.0 change log it's not referenced yet (in master). I'm just confused on what's the status os this issue / pr.


cabal bench does not work

This wouldn't matter as much I guess if haskell-language-server didn't seem to prefer cabal. While trying to make progress looking into haskell-language-server/issues/286 I ran into an issue running ghcide benchmarks:
[nix-shell:/tmp/newfolder/haskell-language-server/ghcide]$ cabal bench
Build profile: -w ghc-8.8.4 -O1
In order, the following will be built (use -v for more details):
 - ghcide-0.2.0 (bench:benchHist) (first run)
Preprocessing benchmark 'benchHist' for ghcide-0.2.0..
Building benchmark 'benchHist' for ghcide-0.2.0..
Running 1 benchmarks...
Benchmark benchHist: RUNNING...
# git (for bench-hist/upstream/commitid)
fatal: ambiguous argument 'upstream/master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Error when running Shake build system:
  at want, called at bench/hist/Main.hs:92:3 in main:Main
* Depends on: all
  at need, called at bench/hist/Main.hs:113:7 in main:Main
* Depends on: bench-hist/results.csv
  at need, called at bench/hist/Main.hs:219:5 in main:Main
* Depends on: bench-hist/upstream/ghcide
  at &%>, called at bench/hist/Main.hs:149:3 in main:Main
* Depends on: bench-hist/upstream/ghcide bench-hist/upstream/ghc.path
  at readFile', called at bench/hist/Main.hs:155:19 in main:Main
  at need, called at src/Development/Shake/Internal/Derived.hs:118:15 in shake-0.19.1-86XfWjXkHUSERkTkeZ7DVQ:Development.Shake.Internal.Derived
* Depends on: bench-hist/upstream/commitid
  at command, called at bench/hist/Main.hs:133:26 in main:Main
* Raised the exception:
Development.Shake.command, system command failed
Command line: git rev-list -n 1 upstream/master
Exit code: 128
Stderr:
fatal: ambiguous argument 'upstream/master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

Benchmark benchHist: ERROR
cabal: Benchmarks failed for bench:benchHist from ghcide-0.2.0.

I'm trying to workaround it by redownloading everything with stack and running stack bench now.

Ah, it pulls "upstream/master" and I don't have that in my git repo. Should probably put a git remote add upstream https://github.com/digital-asset/ghcide.git before stack bench so things just work by default.

Hm, that's still not enough it seems. It looks like the benchmarks are expecting a branch called ghc.path?
[cody@nixos:~/code/ghcide]$ stack bench
ghcide-0.2.0: unregistering (local file changes: bench/hist/Main.hs)
ghcide> configure (lib + exe + bench)
Configuring ghcide-0.2.0...
ghcide> build (lib + exe + bench)
Preprocessing library for ghcide-0.2.0..
Building library for ghcide-0.2.0..
Preprocessing executable 'ghcide-test-preprocessor' for ghcide-0.2.0..
Building executable 'ghcide-test-preprocessor' for ghcide-0.2.0..
Preprocessing executable 'ghcide' for ghcide-0.2.0..
Building executable 'ghcide' for ghcide-0.2.0..
Preprocessing executable 'ghcide-bench' for ghcide-0.2.0..
Building executable 'ghcide-bench' for ghcide-0.2.0..
Preprocessing benchmark 'benchHist' for ghcide-0.2.0..
Building benchmark 'benchHist' for ghcide-0.2.0..
[1 of 1] Compiling Main
Linking .stack-work/dist/x86_64-linux-nix/Cabal-<IP_ADDRESS>/build/benchHist/benchHist ...
ghcide> copy/register
Installing library in /home/cody/code/ghcide/.stack-work/install/x86_64-linux-nix/1ab077909885cd27895e5c1ead5f46712849129d46e5ebc602e96382ea9b3779/8.6.5/lib/x86_64-linux-ghc-8.6.5/ghcide-0.2.0-HMXIvSD1KinKqA0E6bpsEd
Installing executable ghcide-test-preprocessor in /home/cody/code/ghcide/.stack-work/install/x86_64-linux-nix/1ab077909885cd27895e5c1ead5f46712849129d46e5ebc602e96382ea9b3779/8.6.5/bin
Installing executable ghcide in /home/cody/code/ghcide/.stack-work/install/x86_64-linux-nix/1ab077909885cd27895e5c1ead5f46712849129d46e5ebc602e96382ea9b3779/8.6.5/bin
Installing executable ghcide-bench in /home/cody/code/ghcide/.stack-work/install/x86_64-linux-nix/1ab077909885cd27895e5c1ead5f46712849129d46e5ebc602e96382ea9b3779/8.6.5/bin
Registering library for ghcide-0.2.0..
ghcide> benchmarks
Running 1 benchmarks...
Benchmark benchHist: RUNNING...
xxxxxxxxxxxxxxxxxxxxxxxxxxxx  1:
gitTHing is: upstream/master
# git (for bench-hist/upstream/commitid)
# git (for bench-hist/upstream/ghcide bench-hist/upstream/ghc.path)
Preparing worktree (detached HEAD 765967d)
HEAD is now at 765967d Add session-loader to hie.yaml (#714)
# stack (for bench-hist/upstream/ghcide bench-hist/upstream/ghc.path)
Error when running Shake build system:
  at want, called at bench/hist/Main.hs:92:3 in main:Main
* Depends on: all
  at need, called at bench/hist/Main.hs:113:7 in main:Main
* Depends on: bench-hist/results.csv
  at need, called at bench/hist/Main.hs:225:5 in main:Main
* Depends on: bench-hist/upstream/ghcide
  at &%>, called at bench/hist/Main.hs:155:3 in main:Main
* Depends on: bench-hist/upstream/ghcide bench-hist/upstream/ghc.path
* Raised the exception:
stack: createProcess: runInteractiveProcess: exec: does not exist (No such file or directory)

Benchmark benchHist: ERROR
Completed 2 action(s).

I can't say I understand the reasoning for these.

Thanks for reporting!
I'll take a look soon

The benchmarks do not assume a branch called ghc.path.
But they do assume stack is in the PATH, and that's the assumption that is unfulfilled here. Can you check and confirm?


[WIP] Return local insertions and deletions

This PR depends on https://github.com/3lvis/DATAFilter/pull/31. It adds support to return local insertions and deletions, for users that have two way communication with their remote storage.
All feedback is welcome!

I have not used this in a real application yet, but I have a pretty good idea of how I'm going to use it (See use case in DATAFilter PR). If you have any suggestion, feel free to comment.

This would be an excellent addition - two way sync open source is rare.

Hi Gerry, thanks for your comment! Do you have an idea how we can implement this without adding more requisites for users? Elvis likes the idea too, but is hesitant to pull this implementation into the library since it adds the need for a very specific attribute in the entity you want to have two way sync with. If you have any ideas on how to overcome this please comment in the DATAFilter pull request

Hi Gerry, thanks for your comment! Do you have an idea how we can implement this without adding more requisites for users? Elvis likes the idea too, but is hesitant to pull this implementation into the library since it adds the need for a very specific attribute in the entity you want to have two way sync with. If you have any ideas on how to overcome this please comment in the DATAFilter pull request

Hi @FrancisBehnen,
I'm sorry this took so long. I finally went through the article. In my current app I have a similar requirement and I'm using Sync.
Basically every local element has a needsUpload attribute, this is a Boolean. When I call Sync, I provide the predicate: NSPredicate(format: "needsUpload == %@", false), meaning, only sync items where the needsUpload item is false.
Later I will use a NSFetchRequest to fetch all the items with needsUpload == true and send them to the backend one by one. Once one upload is completed, the local item receives an remote ID, and the needsUpload attribute is set to false.

Gonna close this since, it could be achieved by using the predicate to skip attributes that should be ignored from the Sync process.


fix: Fix broken link in Markdown file

Description

Changes proposed in this pull request:

Fix broken link in Markdown file
Run link validation on pull_request event

Related Issues and Documents

Closes:
Related issues:
Traceability

[ ] The PR is linked to a GitHub Issue.
[ ] New features have a milestone label set.
[ ] New features have defined acceptance criteria in a corresponding GitHub Issue, and all criteria are satisfied with this PR.
[ ] The corresponding GitHub Issue has a respective area label.
[ ] The follow-up issues (if any) are linked in the Related Issues section.

Testability
The feature is unit-tested:

[ ] Yes.
[ ] No, because unit tests are not needed.
[ ] No, because of ...

The feature is e2e-tested:

[ ] Yes.
[ ] No, because e2e-tests are not needed.
[ ] No, because of ...

Tests conducted for the PR:

Codebase

[ ] My code follows the Effective Go style guidelines.
[ ] The code was planned and designed following the defined architecture and the separation of concerns.
[ ] The code has sufficient comments, particularly for all hard-to-understand areas.
[ ] This PR adds value and shows no feature creep.
[ ] I have augmented the test suite that proves my fix is effective or that my feature works.
[ ] Adjusted the documentation if the change is user-facing.

Fixed by https://github.com/kyma-project/telemetry-manager/pull/496


Added XDC Network MainNet & TestNet in TradeTrust Ecosystem

Addressing an issue with the synpress library, a temporary solution has been implemented in alt-blockchain-ci/networks/specs/xdcapothem/. The fix can be found in response to Synthetixio/synpress#795.


Adding HPC capabilites to brieflow

This workflow develops HPC capabilites for brieflow. This is optimized for use on the wibr cluster--through a bespoke cluster.yaml file in the slurm subfolder. I would imagine others would redevelop some aspects of this, but the general outline would remain the same.
Given the information we saw for sunbeam, I sought to make this fully slurm compatible. There are two general approaches to running on slurm:

A slurm job that calls multiple slurm jobs
A bash file that calls multiple slurm jobs

For a variety of reasons, in this PR we are doing option 1. This allows for the separate development of slurm files outside of the current workflow.
There isn't much to review here, but it works, and any renaming/organization conventions that you think would be useful would be much appreciated, as well as changes in the README if you'd like.

One more thought I want to add while this PR is going through.
The example analysis on this repo will probably start to get cluttered as we add more modules and functionality (tile vs well based, local vs on HPC, etc). Given that this repo is supposed to be a software repo for the Brieflow tool, we should move away from having analysis in this repo long term if possible.
To align with the Way Lab's GitHub strategy that we are following, we should have Brieflow as a software repo only and another repo that shows how to use Brieflow for useful OPS insights.
Of course, this is a long term change but I want to get it on the radar as the example analysis starts to get more cluttered.

I don't think that the Way lab strategy applies to what we are doing here, but it will apply long term to what we are doing. Once we have developed this approach, we should release it with the example_analysis directory as is. When we actually analyze a screen, I agree, we should have an analysis repo. If we are so confident that brieflow is working effectively, we could make it pip installable and have the example_analysis in another repo that would be cloned and be the setup of another analysis, but I think we are a ways from this.


add Contributor Covenant Code of Conduct

from https://docs.google.com/document/d/1GEwPPpdhFEZnf9xEgJm1PXYfznMbiTaPM3XWTLIEdrA/edit
closes #40

@eads Looks good to me!


feat(module): add support for Romanian, Turkish, Twin languages

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Send string with letters instead of numbers with new [pin] parameter - S instead of P or D

Everything sent or received from Involt is a converted string.
The custom string can be sent with custom-button, input-write, custom-write but sketch by default translate this to intiger.
Currently there is a tutorial(included with upcoming 1.0.3 website update) that explains how to send custom string to arduino and use it inside sketch but how about making this a default feature?
It's possible to create inside sketch additional String array and add elements with S parameter. For example: ard button S0 Hello_World. There can't be spaces between because it will be another css class. Maybe it's good idea to use attribute string="Hello World" and thread this as Value when the S letter is in pin:

Click Me

The reason why it's not default is limited sense of use only to button, toggle and maybe checkbox, radio.

It could be easily manipulated inside arduino sketch chromeReceive function. Instead of one S letter and index S0,S1,S2 etc this can define different variable with each letter other than A,P, and D. User need to declare this variable in sketch and edit the function.


Docstrings

Need to manually add each documented class to the toctree in /docs/source/api/.....
Can build docs locally (after installing pip install -e .[dev, docs] and/or isntalling sphinx and sphinx material theme) by running sphinx-build docs/source docs/dist and then view the website by opening docs/dist/index.html

Ready to be checked !

@rhoadesScholar  is not draft anymore


Graph Service demo video

Details,
Give an overview of graph service APIs and capabilities of graph service.

https://github.com/AmplicaLabs/graph-service/assets/61435908/3c70f3c0-0fc7-4a40-b26f-fa98a33d13ce

The demo to graph service video is linked here


chore: prep 0.10.1 release

Add CHANGELOG.md to readme

The release was made before this was merged?

recreated with -p angular option

@rokroskar can we merge this?


output.filename [file] is not working

Do you want to request a feature or report a bug?
bug

What is the current behavior?
I set output.filename to [file].js and came out ERROR: Path variable [file] not implemented in this context
If the current behavior is a bug, please provide the steps to reproduce.
I had two entry and wanted to custom the filenames
entry: {
    A: './main.js',
    B: './beta.js'
  },
output: {
    path: path.resolve(__dirname, './dist'),
    filename: '[file].bundle.js',
    library: ['[name]']
  },

What is the expected behavior?
output: main.bundle.js beta.bundle.js
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
webpack: 2.6.1
node.js: 6.10.1
OS: mac

Instead of [file] just use [name]. So config might look something like below
entry: {
bundle: "./App"
},
output: {
filename: "[name].js",
path: path.resolve(__dirname, "dist"),
publicPath: "/"
}
Which will generate bundle.js in dist

@RamYadlapalli @sokra  the expected behavior: main.bundle.js beta.bundle.js, why [file] not working


add Omkar0114

resolves #710

@Omkar0114 to fill this pull request, you need to have a repo called: Omkar0114/omkar0114. There, you have a README.md. In the readme, write about yourself and commit your changes. Now you have a readme! If you want examples, just press our profiles avatars, and you will see our readme profiles there.
After just do this:
What to do:

[x] Take a screenshot of your profile, up to where it says pinned repos.
[x] As you just took a screenshot, just ctrl v it into the issue. Or, save it to your computer and then upload it to GitHub, and it will generate a custom image URL, when you copy image address.
[x] Go to your forked copy of the repo, and go to data.json and add your name, paste in the image url and fill out the rest.

Now, just open a pull request with your changes!  🎉
Hope that helps, anymore questions feel free to ask. Thanks

okay I'm doing now

I updated the Image URL of the profile


Initial Bulk Subscribe functionality

Signed-off-by: Yash Nisar<EMAIL_ADDRESS>Description
Initial Bulk Subscribe implementation
Please explain the changes you've made
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: https://github.com/dapr/dotnet-sdk/issues/958
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Extended the documentation

@mukundansundar - Can you validate this to make sure we aren't missing anything?


Ask if you want to save when closing screen in Window

Currently prevents from closing without any prior notification, it just seems to "not close", although it needs to be saved first.

Duplicate of #116


Is it possible to change the certificate according to page accessed?

How could I do it in a script?
Regards.

You can close the issue, did not know that mitmproxy used an own root CA and the CA server generated automatically :) sorry.


Added blender

Great! Thanks for the contribution.  One thing I noticed, we changed the repository 7zip to 7-zip, and we added the 7z to the path for that image.  I'll update that quickly in the build.

Thanks guys, I wondered about that.  I'm still trying to get an image of Unity created.  Tried the snapshot method but get an error about error initializing license system on startup.  I saw a bunch of mentions about this for unix/wine but not on windows.  The one mention on windows mentioned adding a reg entry for ProductId under HKLM\Software\Microsoft\Windows NT\CurrentVersion which I added but it didn't fix it.  Still searching.

Cool, if you get stuck and need some help, just email our support team with the error message and they should be able to assist.


How to create my own dataset?

That's perfect work. I want to create my dataset, please give me on how to create it.

There are several steps.

Get fine-grained segmented part meshes.
Use our software to generate part graph.
Manually label part relations in part graph in our software.
Output part graph and transfer it into binary hierarchy structure.

I didn't clean codes for this part, but if you need them please let me know.

Thank you for your reply. I think I need them. Can you provide me with them?

Here is the software we used to do labeling, detect symmetries and generate obb files.
https://drive.google.com/file/d/1uqV2oOA_4-UQrjK82qFvTCtnD3WT5Gbp/view?usp=sharing
This is a brief instruction doc:
https://docs.google.com/document/d/12r0OH_Je9H4LXeczUg_nLt1m5Z3JwTyNt4rNQs2kM9A/edit?usp=sharing
Here is code we used to transfer obbs to our sym.mat and ops.mat file for PartNet. Btw, this matlab code is old and I don't clean this code, so it could be buggy.
https://drive.google.com/file/d/1GzvDtg_34uTC25S3FdWg0hAoQTnvzo1n/view?usp=sharing


[Question] Any plan for LTS?

I've just started to work on personal project, and wondering if I can lean on that library to perform JSON schema validation.
Hence any plans for LTS? also any plans to make that package open for contributions? :pray:

Yes. It is long term supported. And it is open for contributions as long as those make sense to project goal


Is it possible to introduce wepool as libuv Windows backend?

@piscisaureus released an epoll-like library for Windows, called wepoll, that wraps IOCP APIs. libevent has already use wepoll as Windows backend. (https://github.com/libevent/libevent/pull/1006)
With wepoll, we can

use epoll-like API achieve the same goal but with more readable code
avoid the tricky implementation on Windows
multiple threads can poll the same epoll port
sockets can be added to multiple epoll sets

libuv already uses IOCP and we have most of Windows kinks worked out - a lot was done by @piscisaureus himself. What would be the benefit of using this new library?

There's some overlap with #3008 (sharing code across operating systems) but the difference of course is in the popularity of the two platforms.

I know - I am one of the authors of libuv. However libuv is pretty big and imposes its own asynchronous i/o model onto your application.
Later I discovered that it is possible to do efficient epoll emulation on windows so then I wrote wepoll. With it you can just stick to the good ol' epoll/kqueue model and still support windows.

@piscisaureus himself gives an brief answer about libuv Windows backend and wepoll difference. See the comment: https://news.ycombinator.com/item?id=15978372

Right the main difference is that libuv is a complete library capable of much more, while wepoll only handles sockets.