About Chamfer Distance.

I trained a model only with catagorty 'Car' and test Chamfer Distance with your code 'show_CD'.
It reported an average CD: 0.003873.
Is that right? Because I think it is an unreasonble result. Some state-of-the-art work(e.g. PCN, Top-Net) report its 3D completion task CD around 0.0008.
I didn't see any quantitative results in your paper so I asked here.
Looking for your reply :)

Sorry, but I don't know why you don't answer the question and just close it?

i have answer your questions by senting you an email on 4.6

My github link to my mobile phone email app. I use it to sent you  emails directly many times. Have you received them?

Sorry, I don't recive any of them.

Maybe you could forward those emails to<EMAIL_ADDRESS>if convenient.
Thanks ~

Since this question is not about the code but about the paper. I have sent you an emails to explain my ideas of your questions.

It looks like many of my answers lost lolllll

I find that you lost 3-4 emails.

I have recived your emails! Thank you!

@SkyeFromKindergarten
Hello, I also encountered the same problem. How did you understand this problem in the end?

@SkyeFromKindergarten
Hello, I also encountered the same problem. How did you understand this problem in the end?


Minimal, simple example usage.

Hello There,
Is it possible to provide a minimal, beginner-friendly example usage. I have carefully examined the code samples available in the repository, but as a beginner, I still find it challenging to comprehend the implementation details.
Thank you for the efforts

Hi! Is your app a packaged app (default) ? or a non-packaged app?

It's is packaged app sir, Generated with Template Studio.

I'm working on a sample app generated with the TemplateStudio. Just give me a few days🔥

Thanks, appreciated so much 🙏

Sorry for the delay.
This is a sample app is created with the TemplateStudio. Let me know if you have any questions.
TemplateStudioWinUI3LocalizerSampleApp

Sir,
When i try to initialize the localizer, strangely this exception will throw. any idea why?
WinUI3Localizer.LocalizerException: 'Failed to set language. [{PreviousLanguage} -> {NextLanguage}]'

Sorry. That exception message is going to be fixed in the next version.
You might get this message when the SetLanguage(string language) method is called but failed to find the language.
This is how the SetLanguage method is implemented inside the WinUI3Localizer.
    public async Task SetLanguage(string language)
    {
        string previousLanguage = CurrentDictionary.Language;

        try
        {
            if (this.languageDictionaries.TryGetValue(
                language,
                out LanguageDictionary? dictionary) is true &&
                dictionary is not null)
            {
                CurrentDictionary = dictionary;
                await LocalizeDependencyObjects();
                OnLanguageChanged(previousLanguage, CurrentDictionary.Language);
                return;
            }
        }
        catch (LocalizerException)
        {
            throw;
        }
        catch (Exception exception)
        {
            ThrowLocalizerException(exception, "Exception setting language. [{PreviousLanguage} -> {NextLanguage}]", previousLanguage, language);
        }

        ThrowLocalizerException(innerException: null, "Failed to set language. [{PreviousLanguage} -> {NextLanguage}]", previousLanguage, language);
        return;
    }

My first guess is that you are not setting the DefaultLanguage in the options:
ILocalizer localizer = await new LocalizerBuilder()
    .SetOptions(options =>
    {
        options.DefaultLanguage = "YOUR DEFAUL LANGUAGE";
    }
    .Build();

You also need to make sure that your default language is added as a LanguageDictionary.


different CI builds of python always build with 3.8

Should be building with 3.7, 3.6, 2.7.
Looks like cmake is always picking up 3.8 from somewhere else....

Fixed.


Image resizer should also allow for disk size.

Description of the new feature / enhancement
Currently, one can only select the dimensions of the to be generated image. Sometimes, the disk size is what is needed. So provide this as an option.
Scenario when this would be used?
When putting images on a website, one wants to limit the amount of bytes that is used (and also transmitted).
Supporting information
No response

/dup https://github.com/microsoft/PowerToys/issues/8790


Fixed _DER_multi calls in DER

The print_speaker_map and verbose arguments are now passed correctly.
Fixes #18

LGTM. Thanks!


🐛 [Bug] Firefox cannot properly authenticate due to policy errors

🐛 Bug

Firefox cannot properly authenticate due to policy errors
The loading of “https://auth.dreammall.earth/if/flow/stage1-dreammallearth-authorization/?client_id=XXX&redirect_uri=https%3A%2F%2Fstage1.app.dreammall.earth%2Fsilent-refresh&response_type=code&scope=openid+profile+email&state=XXX&code_challenge=XXX&code_challenge_method=S256&prompt=none” in a frame is denied by “X-Frame-Options“ directive set to “deny“.stage1-dreammallearth-authorization

https://github.com/goauthentik/authentik/issues/5762#issuecomment-2254179740

seems to be fixed


Drag n' Drop! 👆💧

This commit adds support and fixes for several things. Here's the changes:

Dock now looks more proper iOS 11 (yay! 📱)
Settings look cleaner (removed emojis for more space)
Finalized settings for icon input
Added Dran n' Drop for the floating dock and a toggle in settings.
Overall speed and improvements. 🐙

This should be pushed in my beta group in a few minutes.

The commit '🐙 Slicker Drag n' Drop' improves the 'Drag n' Drop' feature from the last version, as well as actually allowing you to drop the dock and start dragging again. :P
Enjoy!

Added some small changes to Drag n' Drop that makes the code a little better.


Clarification on how Bitoftrust is different/similar to BrightID

BrightID White Paper: https://www.brightid.org/whitepaper

The paper mentions the following sentence in its introduction.

BrightID is a social identity network that allows people to prove to applications that they aren’t
using multiple accounts. It solves the unique identity problem through the creation and analysis
of a social graph.

This is not the use case of Bit of Trust, since we are not concerned with proving to the outside world that we are not using multiple accounts. We are inherently allowing users to have a membership in multiple trust relationships, this is a big fundamental difference.
Of course, there may be similarities in how they do things, but it is currently not a focus to differentiate ourselves from other identification schemes.


Screenshot

Is there any way to take a screenshot for inspection?

Zombie doesn't render anything, so there's no way to take a screenshot.


Uncovered branches are reported if generator iterators are not exhausted

Describe the bug
Given this program as test.py:
def func():
    val = next((c for c in "abc"), None)
    print(val)

func()

Branch coverage claims that there is an uncovered arc from line 2 (the val = next(...)) to exit. As far as I can see, there is no branch there.
To Reproduce
$ python -V
Python 3.11.2
$ coverage --version
Coverage.py, version 7.2.4 with C extension
Full documentation is at https://coverage.readthedocs.io/en/7.2.4
$ coverage run --branch test.py
a
$ coverage report --show-missing
Name      Stmts   Miss Branch BrPart  Cover   Missing
-----------------------------------------------------
test.py       4      0      2      1    83%   2->exit
-----------------------------------------------------
TOTAL         4      0      2      1    83%

Interestingly, if you change line 2 to:
    val = next(iter("abc"), None)

Coverage no longer believes there is an uncovered branch, despite the fact that (c for c in "abc") and iter("abc") both return iterators over the same 3 elements.
Expected behavior
There should not be a branch detected from line 2 to exit, as the only line that can follow 2 is 3. I suspect the issue may perhaps be that Coverage doesn't understand that 2-argument next will never raise a StopIteration.
Additional context
This may be the same issue as https://github.com/nedbat/coveragepy/issues/605#issuecomment-1470759557 - I started to add this as a comment there, but then thought I'd err on the side of a new issue.

I suspect the issue may perhaps be that Coverage doesn't understand that 2-argument next will never raise a StopIteration.

Actually, that doesn't make sense, given that it doesn't happen with next(iter("abc"), None). It must not be two-argument next that's provoking it - maybe something related to generator expressions?

@nedbat helped me understand what's happening here, and it's much simpler than I was imagining. I wasn't correctly interpreting what the ->exit is trying to tell me: Coverage is reporting that the generator expression did not run to completion, because we didn't advance the returned iterator until StopIteration was raised. That's totally true.
It's possible to provoke a similar report with list comprehensions - for instance, this test program:
try:
    [x / 0 for x in (1, 2, 3)]
except ZeroDivisionError:
    pass

reports 2->exit as missing, because the exception stops the list comprehension from running to completion.
Having gathered my thoughts a bit after my conversation with Ned, I think that this isn't a helpful thing for Coverage to report.
Coverage doesn't complain about failures to exhaust other iterators, like iter("abc"). You'll say "but those aren't functions, like generators and list comprehensions are", but the language doesn't guarantee that comprehensions and generator expressions are implemented as functions, only that they have their own scope. And PEP 709 is proposing to stop generating list comprehensions as nested functions in CPython (with a similar change for generator expressions left as a future improvement).
But moreover, Coverage doesn't complain when you fail to exhaust other iterators that are functions. There's no missing branch reported if you call iter(map(int, "123")) then don't advance the iterator until map.__next__ raises StopIteration.
You might say "but that uncovered branch is inside the implementation of map", but that's the case for generator expressions as well - the uncovered branch is where the implementation conditionally raises StopIteration if the user-provided iterable has been exhausted.
You might say "the difference is that the code running inside a generator expression is user-provided, not part of the interpreter's implementation like map", but that's only partly true. The uncovered branch isn't in the code provided by the user, it's in the interpreter's implementation of the generator expression machinery that's wrapping the user's code, which will return from the nested function and raise a StopIteration after the user-provided iterable has been exhausted. The Coverage user isn't trying to exercise the interpreter's generator expression implementation, so they don't gain any useful information from being told that there's a branch inside it that isn't taken.
I'm pretty convinced that this report isn't useful to or actionable by users - what do you think, @nedbat?

I don't often require 100% branch coverage, so I don't know that I have a strong opinion on this, but one point in favor of the "this is not useful" might be the question of what happens when you have infinite iterators?
Do you get the same kind of branch miss in this situation?
a = (x.upper() for x in itertools.repeat("Spam"))

print("\n".join(itertools.islice(a, 0, 100)))

On the other hand, if you have a situation like this:
def my_func(n, a=(1, 2, 3.0, 4, "five")):
    it = (int(x) for x in a)
    return next(itertools.islice(it, n, n+1))

@pytest.mark.parameterize("n", [0, 1, 2, 3])
def test_my_func(n):
    assert isinstance(my_func(n), int)

It would be nice to recognize that you have missed the failing cases my_func(4) and my_func(5). Of course, by this logic, you would also want to make sure that coverage is emitting branch misses for next(iter("abc"), None) as well.

Another point for consideration: PEP 709 proposes changing the generated byte code for comprehensions, to avoid the extra code object. I would guess that would affect Coverage's ability to even measure if a comprehension completes or not.
(The PEP currently awaits Steering Council input: https://github.com/python/steering-council/issues/179.)

one point in favor of the "this is not useful" side might be the question of what happens when you have infinite iterators?

I thought about bringing infinite generators up, but Coverage already requires you to add a # pragma: no branch on infinite loops, so if it's ever worth reporting the "generator exhausted" branch being unreached, it would be consistent to expect people to explicitly mark cases where the generator can never be exhausted.


Terminal opens but blank screen

Any idea?

It's not the clickable-links bug. I don't even have the plugin, and even after installing latest version the issue still persists.

Please capture DevTools console logs at the time of the issue: https://github.com/Eugeny/terminus/wiki/Debug-logs

Which windows build are you on? Try disabling ConPTY in the Settings -> Shell

Where's ConPTY? On 10.0.18922 N/A Build 18922

Added:
useConPTY: false
To the Config file. Same issue, didn't fix it.

I am having the same issue when swapping between tabs:

Version: 1.0.85
Platform: win32 10.0.18362
Plugins: none

I can confirm that this issue was resolved for me with ALPHA 86.

The same problem :-(


Updating azk-dev and other related dependencies

The main contribution on this PR is updating the azk-dev lib. This brings, among other improvements, babel 6.x version. In few words, those changes on babel make the source code transpilation process more modular.

Updating azk-dev:

Changes on azk-dev modules calls, from azk/gulp to azk/lib/gulp, as instance. The former pattern is still supported but has been deprecated:<PHONE_NUMBER>7a94ebc6e50e1cccfe2f1e4d569861;
The order in which the chai plugins are loaded was changed. Now, it's possible to combine chai-as-promised and chai-subset. This is not part of azk anymore: 03658bc09c4d2c390b650cd5e9709075386bc475;
Replacing the system of support to generators  (directly in the it methods) with a system from azk-dev, which is simpler and better supported 03658bc09c4d2c390b650cd5e9709075386bc475;
In bluebird > 3.0, the method promisify was changed and no longer supports the return of multiple actions (aka: Array expansion). This has caused a big impact and led to replacing many nfcall and nbind by direct calls to promisify with the option { multiArgs: true } ec5f0e6998f7ce13f8e41aa84c2c5182caff97ea;
While solving the previous problem, we've noticed a problem with the error handling during the VM start on agent. It was fixed, so now it's easier to identify them e67e8e360e0d5232aa3366166602eeb0d8f7a87e;
Finally, for a matter of simplification and better support to the modules scheme from ES6, the use of the instructions export, export default and import was improved<PHONE_NUMBER>7a94ebc6e50e1cccfe2f1e4d569861;

Updating lodash:

template now generates a "compiled template", returning a method to expand it. The src/utils was updated to attend this new API. More at c5f532f60c2d636520ce42f5b80c517c2c33718f;
By default, flatten no longer does deep flaten. To do so, the option true must be passed. In this case, the change was bigger once the problem occured in src/cmd/start.js and it was noticed there were better approaches in the class Manifest to get the system list and its dependencies. More at 318c9bead11023c5fa18699bd056799e3f329120;
While solving the problem with template, it was identified an issue on the specification of ManifestError which turned the debbuging process more harsh. To solve this, a type was added to the error in order to identify it adc9e5f12bcd473ec643fe5c00ae7d442e316a1f;

Updating insight-keen-io, removing support to promises. Instead, default node callbacks are used b60247a3a9e7f8ce93bd3ce9249310f4282efd17;

Other updates with minor impact: archiver, crash-report-sender, docker-registry-downloader, file-async and inquirer f25e06736fc66bf3ccc552cd431bd050b8e4804b;

LGTM

LGTM :ok:

LGTM

LGTM


various fixes

Issue being fixed or feature implemented

Various fixes
What was done?

How Has This Been Tested?

Breaking Changes

Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation

For repository code-owners and collaborators only

[ ] I have assigned this pull request to a milestone

Approved by @ClaudeHangui in jira


Fix typo : build-in -> built-in

I signed it

/check-cla

there appears to be a problem with the CLA.
try contacting the CNCF help desk.

/check-cla

Hi @eriksjolund, thanks for the PR.
If you signed the CLA, here's some steps to try:

If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
If you have done the above and are still having issues with the CLA being reported as unsigned, please email the CNCF helpdesk<EMAIL_ADDRESS>

Hey there, just another reminder to please sign the CLA.

Sorry, I just realized I have not yet signed the CLA. I plan to do it over the weekend.

See https://github.com/kubernetes/community/blob/master/CLA.md#troubleshooting for help signing the CLA, and feel free to reopen this PR once you've done so by clicking the Reopen button.


Ignoring super long lines

One thing that often gets in my way when I'm searching for things is that I'll get matches for random json and xml files that are rendered as one line. I never want to see these, so I looked through the man page and found an interesting flag:
--print-long-lines:
     Print matches on very long lines (> 2k characters by default)

Cool. But there are two problems. The first one is a functional issue (or maybe just my ignorance) and the second is a feature request.

The man page entry seems to indicates that by default this flag is off by default. But it isn't. When I run ag on my computer, it prints a match on a line with 1368810 characters. And I don't see a way to turn this flag off either. There isn't a --noprint-long-lines flag mentioned in the man page. So basically, I don't see how to actually get the actually get the line-filtering behavior that the man page indicates is possible.
Can we configure what is considered a "very long line"? In my case, it's really the lines with more than 100 characters that I would like to filter out. I would like to see a flag `--long-line-length=2000' so that I could have more control over this.

Regardless, thanks for all the hard work on this awesome tool. It is enormously helpful in my workflow, and I hope that it can become even more so.

Duplicate of #189, I think.

It appears so. I guess since that issue has been open two years and seems unlikely to get fixed, maybe my request could instead be to remove --print-long-lines from the documentation, since it only confuses people who expect it to work.

@andrewthad I agree with that. I've submitted https://github.com/ggreer/the_silver_searcher/pull/706 to do that.


[Bug]: Do not render editor action buttons (save/discard) when displaying non-code files (e.g., images)

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Describe the bug and reproduction steps
Editor action buttons are rendered even when displaying images.
Follow-up issue to #4898
OpenHands Installation
Docker command in README
OpenHands Version
main
Operating System
None
Logs, Errors, Screenshots, and Additional Context
No response

Resolved


Excel a wrong row or column can be marked red, with a red background, can be positioned.

Excel a wrong row or column can be marked red, with a red background, can be positioned.

We offer this in the Pro compendium.  Since companies have paid for the features already, it would be unfair to them if we turned around and made it available as open source.  We have a longer comment in a gist.


Question about Performance: Processed block per second

Hi. I'm Denver.
TLDR:

Is there any tips for maximizing performance(processing blocks more fast) when do check:data?

Description
I'm currently implementing rosetta-klaytn for Klaytn.
Actually rosetta-klaytn implementation has been completed (but not yet published to public), so I'm currently doing check:data test for it.
Klaytn's current block number is 91,145,672 which is nine times bigger than Ethereum.
Recently processed block number by check:data is 14,145,672 (There are still a lot of blocks left.)
The processing of check:data is 10 blocks per sec and I'm trying to maximize this performance by optimizing configuration values and fix some source codes.
Please give me some tips or advices if you know something.
Machine SPEC I'm currently using
AWS c5a.8xlarge

32 vCPU
64 GiB RAM

Config I'm currently using
{
  "network": {
    "blockchain": "Klaytn",
    "network": "Mainnet"
  },
  "online_url": "http://localhost:8080",
  "data_directory": "cli-data-cypress",
  "http_timeout": 120,
  "max_retries": 15,
  "max_online_connections": 256,
  "max_sync_concurrency": 256,
  "tip_delay": 300,
  "max_reorg_depth": 100,
  "log_configuration": false,
  "compression_disabled":true,
  "memory_limit_disabled":false,
  "error_stack_trace_disabled": false,
  "coin_supported": false,
  "construction": null,
  "data": {
    "active_reconciliation_concurrency": 16,
    "inactive_reconciliation_concurrency": 32,
    "inactive_reconciliation_frequency": 250,
    "log_blocks": true,
    "log_transactions": true,
    "log_balance_changes": true,
    "log_reconciliations": true,
    "ignore_reconciliation_error": false,
    "reconciliation_disabled": false,
    "reconciliation_drain_disabled": false,
    "inactive_discrepancy_search_disabled": false,
    "balance_tracking_disabled": false,
    "coin_tracking_disabled": false,
    "status_port": 8081,
    "results_output_file": "",
    "pruning_disabled": false,
    "initial_balance_fetch_disabled": false,
    "historical_balance_disabled": false,
    "bootstrap_balances": "bootstrap_balances.json"
  }
}

And I changed DefaultCacheSize from 2000 << 20 to 8000 << 20 to increase cache size to get much blocks from Block Fetcher.

To

To investigate how can I improve the performance of rosetta-cli on Klaytn, I'm drawing Architecture of rosetta-cli like below.
If you guys are interested in this diagram, I'll upgrade the current diagram to help rosetta community to understand rosetta-cli better.

Hey @aeharvlee
thanks for the detailed diagram. We know there are performance issues with check:data on larger blockchains. We are trying to explore options on how to improve them.  One way we are trying is doing concurrent validation per block ranges. Another way we are trying is to see if badger is a right choice or if we can use any another key value db to improve perf. There are certainly some more improvements which can be made in the rosetta-cli code (faster json encoding/decoding), feel free to explore that.
We will take a look at this diagram and see if we can put it in the rosetta-api website and here for future reference

@shrimalmadhur
Sorry for late reply. Thanks for your reply :) Currently I'm trying to update the diagram with more details.
I'll show you after I updated it! Hope this will be included in the rosetta-api website :)

Hey @aeharvlee, Did you try turning off logging? sometimes excessive logging slows down the check:data,
    "log_blocks": true,
    "log_transactions": true,
    "log_balance_changes": true,
    "log_reconciliations": true,


[BUG] Hydra doesn't open some game's tab, only opens a tab to close it instantly

Hydra doesn't open some game's tab, only opens a tab to close it instantly
So, as the title says, my Hydra client refuses to open some game's "window" or tab, clicking on any game results in it loading as intended but shutting itself down when loaded.
https://github.com/hydralauncher/hydra/assets/39568103/69fbe56f-2c3f-48bb-90e2-ae4f232e0895

Hydra currently uses info from the Steam page of the game. If the game is not available in your country, this bug happens.
We are trying to fix this.
For now, you can try to use a VPN to access the game page once. And after the first time, the game page will be cached and a VPN will not be needed anymore for that game


Remove redux and reselect. Note: azureResource folder and iotHub folder are removed.  When need to bring them back, this is the commit to refer to

remove react-redux


[sketch] dragging a sketch with freehand into a stack fails

create a stack
create a sketch
scribble some freehand in the sketch
drag the sketch into the stack
the sketch will temporarily show up, but the drag actually failed - refresh and it's not there
the sketch file is now un-openable

Here's the error from the console:

probably related to #6099

doing this on main triggers the performance issues we were seeing that completely lock up the tab for 30+ seconds


How to use utf-8 charset for csv?

In Vaadin directory, Sezim Satybaldieva asked:

How to use utf-8 charset for csv?

Currently the charset cannot be customized. CsvInputStreamFactory uses the default character encoding:
https://github.com/FlowingCode/GridExporterAddon/blob/e4cd1ceec8cc41526d2a840ebae3188e80b39104/src/main/java/com/flowingcode/vaadin/addons/gridexporter/CsvInputStreamFactory.java#L75-L75


Ios Exception

Hi
I tried to share an image with Snapchat
it works in android but I got an exception in ios
I already add user demo & bundle id
[VERBOSE-2:ui_dart_state.cc(199)] Unhandled Exception: PlatformException(SendMediaSendError, Optional(Error Domain=SCSDKCreativeKitErrorDomain Code=10 "error_description_malformed_url" UserInfo={NSLocalizedRecoverySuggestion=recovery_suggestion_check_documentation, NSLocalizedDescription=error_description_malformed_url, NSLocalizedFailureReason=}), null, null)
#0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:597:7)
#1      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:158:18)

#2      Snapkit.share (package:snapkit/snapkit.dart:193:5)

The problem from the image provider.
why in android accept sharing images from file but ios gave an exception as showing above
  snapkit.share(SnapchatMediaType.PHOTO,                         image: Image.file(                           imageFile                         ).image,                         sticker: SnapchatSticker(                           image:                               AssetImage("assets/images/shared_sarahah_ar.png"),                         ),                         attachmentUrl: Constants.sarahahUrl);

Sorry for the delay, have you tried loading the image the same way you're loading the Sticker's Image ie thru AssetImage("path/to/image.png") ?

Thanks, it works very well


Improve log when live patching fails

Description
This PR improves error log message when scp fails during system VM live patching

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?
Before Fix:
2022-04-27 12:02:22,647 ERROR [c.c.s.ManagementServerImpl] (API-Job-Executor-1:ctx-f000200b job-40 ctx-161ff677) (logid:52d49a16) Failed to patch systemVM v-1-VM due to Failed to scp files to system VM, retrying, retrying, retrying

After Fix:
2022-04-27 13:15:16,189 ERROR [c.c.s.ManagementServerImpl] (API-Job-Executor-1:ctx-4cfd7ab1 job-62 ctx-23bea220) (logid:dffe10d7) Failed to patch systemVM s-2-VM due to Failed to scp files to system VM due to, Remote scp terminated with error (scp: /tmp//agent.zip: No space left on device).

@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

@blueorangutan package

@nvazquez a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@blueorangutan test

@Pearl1594 a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

^ test failed due to dns issue in the lab

@blueorangutan test

@Pearl1594 a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests


Fix LBA compatibility

Tested against simple pipes, it seems to work now... although I've only tested inserting and extracting water.

Works perfectly; thank you!


draw negative bars at proper location

in GraphClass > Bar graph, change yPos+Height-2, to yPos+Height/2-2, (in all instances?) and the bars will draw from zero downward for negative values.

Sorry I don't understand the issue. Sorry for not monitoring the issue board. I will close the issue, but please reopen and attach a screenshot of the issue.


Balance Format

How about adding a format for the balance with a separator for better readability?
                balance_usd = float(data_response['balance_USD'])
                balance_btc = int(data_response['balance_BTC']) / 100000
                balance_cexp = float(data_response['balance_CEXP'])

                self.coin_balance = balance_usd
                logger.info(
                    f"Account name: {data_response['first_name']} - "
                    f"Balance: <yellow>{balance_usd:,.2f}</yellow> - "
                    f"Btc balance: <green>{balance_btc:,.2f}</green> - "
                    f"Power: <blue>{balance_cexp:,.2f}</blue> CEXP"
                )

Ex: Account name: Account_1 - Balance: 1,234,567.89 - Btc balance: 1,234.30324 - Power: 577,177 CEXP

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/6mkbh6xhau31g
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

i already did


ghc-head branch

I find it quite difficult to use ghc-head branch which requires ghc-9.7 (which one probably needs to install from ghc source repo, rather than with something like ghcup).  The CONTRIBUTING file mentioned that PRs should be opened against that branch, is this correct? Why then we have the main branch?  It is quite confusing which branch should be used when trying to do something which actually works (currently ghc-9.{4,6} works fine, bug ghc-{head,9.8} require ghc-9.7 for some reason, while the main branch has quite old version of haddock:

branch
haddock-api version

main
2.27.0

ghc-9.6
2.28.0

ghc-9.8
2.28.0

ghc-head
2.28.0

This is also confusing when compared to which haddock versions are published with ghc:

ghc version
haddock version

9.6.4
2.29.2

9.8.1
2.30.0

The CONTRIBUTING.md file should explain it better to make it much less confusing.

It even seems that the ghc-9.6 branch is not compatible with ghc-9.6 right now :frowning_face:.

The CONTRIBUTING.md file should mention that the preferred way of building haddock is using the  ghc repo & hadrian build system.

Now that Haddock lives in GHC I'm not sure if this issue is still relevant. Your opinion?


Possible Memory Leak From C.malloc(0)

Hello! I was playing around with gotch and ran a few tests to make sure I was dropping tensors and freeing memory correctly. However, even when I ran MustDrop(), memory usage always slowly creeped up. I'm running go 1.20 on Ubuntu 22.04 in WSL2. Here is a minimal example of when this happens.
func main() {
	for i := 0; i < 100000000; i++ {
		a := ts.MustRand([]int64{1}, gotch.Float, gotch.CPU)
		a.MustDrop()
	}
}

I took a look at the underlying interface with libtorch and saw that most functions handled outputs of C functions by calling C.malloc(0).
func Rand(...) (...) {
	ptr := (*lib.Ctensor)(unsafe.Pointer(C.malloc(0)))
	// Some C call that stores an allocated tensor at *ptr.
	retVal = &Tensor{ctensor: *ptr}
	return retVal, err
}

However, while we do free *ptr using MustDrop(), ptr is not freed. I think this is what is causing the memory leak.
By changing the above function to one of the two versions below, I was able to run the simple example without any memory leaks. I think the second one results in less Cgo calls, but I'm not sure if the usage is safe.
func Rand(...) (...) {
	ptr := (*lib.Ctensor)(unsafe.Pointer(C.malloc(0)))
	defer func() { C.free(unsafe.Pointer(ptr)) }()
	// Some C call that stores an allocated tensor at *ptr.
	retVal = &Tensor{ctensor: *ptr}
	return retVal, err
}

func Rand(...) (...) {
	var untypedPtr uintptr
	ptr := (*lib.Ctensor)(unsafe.Pointer(&untypedPtr))
	// Some C call that stores an allocated tensor at *ptr.
	retVal = &Tensor{ctensor: *ptr}
	return retVal, err
}

Same problem

Seems to be a problem. Do we know how those x-generated.go are generated? 🤔 Maybe we can help create a fix?

upgraded with a new switch to use Go garbage collection.


Smoothline - Memory Leak

I'm frequently updating the points of a line to animate it (using kivy's clock). I have no problems when using the default line but when i use a smoothline instead, the used memory is slowly but steadily increasing. There is some kind of memory leak in the smoothline implementation, whenever the points-list gets changed. Would like to use smoothline because it looks much nicer.

uh, that does seem likely indeed…
https://github.com/kivy/kivy/blob/a2fca89bf67291aef11b1d5f88a6ad8fd52e08d3/kivy/graphics/vertex_instructions_line.pxi#L1484-L1485 (current master)
        #free(vertices)
        #free(indices)


Middleware for route groups are not validated as being valid

Laravel Version: 5.8.x
PHP Version: 7.x
Database Driver & Version: MySQL (MariaDB)

Description:
Not sure if this is necessarily a bug or not, but rather a suggestion to help prevent against possible security vulnerabilities or other issues.
When defining routes, you can set a group and pass in a key of 'middlware' but a value of null and no exception is thrown.
This led to an issue recently for a project I was working on.  A developer changed the name of a config key in the middleware itself, but forgot to change it in the routes.
For example, this code was defined originally:
Route::group([
    'namespace' => 'something',
    'middleware' => config("auth-guard")
], function () {
    Route::resource('something', 'SomeController');
});

However, after the change was made where the config name was changed to package-auth-guard, config("auth-guard") was returning null without us knowing, which means that in this case, our routes were not protected at all and open to unauthenticated users.
Is there any use case where a null value could be passed to a route middleware group intentionally?  Or is this something that should be changed to prevent others from having this same type of issue in the future?
My apologies in advance if this does not qualify as a bug or if I should not be posting this here.  This is my first time reporting a potential issue for Laravel.

The code you run actually as below:
Route::group([
    'namespace' => 'something',
    'middleware' => null
], function () {
    Route::resource('something', 'SomeController');
});

In my computer, this will crash.

@boyleninc it's perfectly possible to unset middleware. In this case I recommend to write tests that verify the expected behavior so you know that the functionality keeps on working. We cannot unfortunately account for config changes as that's done in userland.


[WIP] chore: add undocumented BYTES type to SQLite

Describe this PR
This PR updates the documentation to show that the SQLite adapter actually supports the BYTES type as stated in  #10537
Changes

Updated the database-connector docs for SQLite by updating the compatibility table
Update prisma-schema-reference docs

What issue does this fix?

#1747
closes #10537

Referenced wrong issue? Seems that one is a closed unrelated one.

Referenced wrong issue? Seems that one is a closed unrelated one.

Sorry, I copied the issue ids from the main repo thinking this was same, updated the links

Ah, now things make sense 👍 Left a few comments for details.


Search manager returning max of 10 results

Question:
I'm currently implementing a search functionality using the searchmanager. I initlize the class like this:
using var client = GetPlatformClient();             return client.SearchManager.Search(new QueryParameters             {                 Query = query,                 Pipeline = Settings.Pipeline,                 ViewAllContent = true             }, cancellationToken);
But this is only returning a max result of 10 items.
Thing I've tried:

Looked for a property in the Query Parameters class
Set the page size on the CoveoPlatformConfig after initlizing it
Add 'numberOfResults' in the query parameter

When I do the same request via postman I see more results, so I don't think the issue is with the settings on the Coveo platform.
Can you please give more insight on how I should tackle this?

Try setting the PageSize in the config before creating the CoveoPlatformClient. The default page size is a 100, so if you have more than 100, you should get 100?
One thing to note is that the SearchManager does not support paginated queries, so if your results do not fit on a single page, it's not supported right now. How many results are you expecting?
What was the postman query you performed that worked?


CMake build is needed to make it cross-platform.

I don't see obstacles to compile and run it on Linux or macOS. So would be good to have a CMake build instead of VS solution files  to make it easier.

Fixed by #2


Godot V3.2.alpha2 does not honor Scene Instancing with Edit Children for CollisionShape2D

Godot version:
Godot V3.2.alpha2
OS/device including version:
Mac OS X, Mojave
Linux Mint 19.1
Issue description:
If you have a scene that is instanced, and you select and checkoff Editable Children for that instanced scene, then changing the size of the subnode CollisionShape2D, changes it for all other scene instances.

Expected behavior should only change the selected subnode of an instanced scene, in this case CollisionShape2D. Workaround would be to manually create each node/subnode instead of using an instanced scene, which would defeat the purpose of instancing.
Steps to reproduce:

Install Scene Instancing Demo from Godot Project Templates tab.
Right Click on any ball node and checkmark Editable Children.
Select and Resize sprite node. Notice only the that sprite is changed.
Select and Resize 'collision'  node. Notice that it resizes all on-screen collisions.

shape needs to be made unique
right click your shape property in the inspector, select "make unique"

Or enable "Local To Scene" option.

Where is Local To Scene option?

Under Resource section, when you click the CircleShape2D in the inspector. The thing is that your circle is a Resource, so it can be shared by multiple nodes.

Why do I have to make it Unique?

Here is some more info

Even if you save a built-in resource, when you instance a scene multiple times, the engine will only load one copy of it.

https://docs.godotengine.org/en/latest/getting_started/step_by_step/resources.html

Ok thank you.


New command: Get the number of Microsoft Teams daily unique users by device type

@waldekmastykarz,
Could you please review this command(Issue #1011)  and merge?
Thank you.

Coverage remained the same at 100.0% when pulling ef331d911f51d244c1047ada35e65884524a3837 on sprider:teamsdeviceusageusercounts into c7ad6cf12f5fa947fc2ab60e0257ee1bff9bd789 on pnp:dev.

@VelinGeorgiev
Generally @waldekmastykarz resolves the src/o365/graph/commands.ts file manually. Do you still want me to do something on this?

Very well done @sprider ! Almost perfect command. I added minor comments to it.
@sprider could you please pull and rebase with the latest dev branch from upstream since there are merge conflicts in the pull request and it will be easier for you to solve them with rebase than to me.
@waldekmastykarz , @sprider here is a consideration we have to make. The output of that command is CSV . We have to make a decision weather we leave it as terminal output or have the option to generate CSV file as well. Maybe optional option for --filePath will generate a CSV file instead of outputting the results on the screen. Another concern I have is because it comes as CSV format, when I specify --output json, it does not look pretty and it does not look as json. We have to decide how to parse that to json. @waldekmastykarz , @sprider I am waiting for your input here.

@VelinGeorgiev
Generally @waldekmastykarz resolves the src/o365/graph/commands.ts file manually. Do you still want me to do something on this?

Very well done @sprider ! Almost perfect command. I added minor comments to it.
@sprider could you please pull and rebase with the latest dev branch from upstream since there are merge conflicts in the pull request and it will be easier for you to solve them with rebase than to me.
@waldekmastykarz , @sprider here is a consideration we have to make. The output of that command is CSV . We have to make a decision weather we leave it as terminal output or have the option to generate CSV file as well. Maybe optional option for --filePath will generate a CSV file instead of outputting the results on the screen. Another concern I have is because it comes as CSV format, when I specify --output json, it does not look pretty and it does not look as json. We have to decide how to parse that to json. @waldekmastykarz , @sprider I am waiting for your input here.

@VelinGeorgiev
Generally @waldekmastykarz resolves the src/o365/graph/commands.ts file manually. Do you still want me to do something on this?

@VelinGeorgiev
Regarding csv, Its a good idea. I will wait for @waldekmastykarz's response.

Both good suggestions @VelinGeorgiev and I'd suggest to implement them as improvements on both report commands. So right now, we keep them as-is and in the next round, we add support for filePath and json output.

@sprider can you please do a new PR where you pull the latest changes from the dev branch and then add your files on top. Otherwise I cannot keep your name in the logs for that PR since your first action is merge with dev and when I rebase and squash your name is being removed from the logs.

@VelinGeorgiev,
Sure, I will delete this branch and create a new pull request with the new branch and changes you have suggested. Please close this pull request.


Usage doc needed: How to use labels to select external host IPs

Regularly it is asked how to define IPs that can be referenced with labels.  This can be done by defining a host endpoint (with one per IP address or multiple IPs in a host endpoint) with a label and then selecting that label.
It would be good to have a Usage doc explaining this.

I'd love to see this done generically as it is very applicable to Mesos as well.

Could be, though it's fairly well explained here: https://docs.projectcalico.org/v3.1/reference/calicoctl/resources/globalnetworkset


Updated prokka workflow to newest tool versions

Updated tool versions to prokka 1.14.5 and jbrowse 1.16.5+galaxy6. Workflow created from history in Galaxy 20.01

looks good @almahmoud! could you resolve the conflict? (let me know if you need help with that)

Done! Thank you!!

@almahmoud Sorry for the Travis error again. Since #1724 and #1715  it is mandatory for a workflow on GTN to have the correct tags and annotation (This started during this PR). I am planning to update planemo this week so it has the same linting capabilities and you can test it easily in advance. The only thing you have to add is to the annotation attribute is the title of the tutorial (like in the original workflow):
"annotation": "Genome annotation with Prokka"

Sorry for these details, but we hope that if these workflows are than added to an instance, people will find them back easier.

Thanks for all the reviews. Wondering if any other changes are needed or if we can get this merged!


HID implementation?

Looking to build a BLE based game controller.
I didn't see any examples for HID, just wanted to verify this is implemented.

This is a HAP library designed to integrate physical appliances with Apple HomeKit for use in the Home App on an iPhone, iPad, or Mac.   I don't think there is anything in HAP that would be relevant to game controllers.  Also, it's WiFi only (no BLE).


⚠ Bofrost.es has degraded performance

In 5040525, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1598 ms

Resolved: Bofrost.es performance has improved in ffceea5 after 9 minutes.


photon: support countrycode

Expose the countrycode attribute from the Photon backend

Thanks for this! Will be deployed shortly. Seems like the tests pass in master.

mån 2021-04-26 klockan 00:46 -0700 skrev Peter:

Thanks for this! Will be deployed shortly. Seems like the tests pass
in master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Great, thanks!
Seems to work fine!
Started working on using this information in Maps to be able to get
more accurate region detection for search results (which will improve
rendering of transliterated names and some other things in some border
areas for example).
Hopefully I will be able to utilize this also in the next stable patch
release 40.1 to be released on Saturday!
//Marcus


Why is there so many open PR's with no conflicts and resolved discussion

Just like the title says, it's concerning that there are so many open PR's that solve performance or compliance problems, like #102  #218 . It's really strange to see discussion about a PR then not merge or deny it.
edit: Grammar was bad

Hello @aaahrens
I can assure you that the library is now actively maintained again and all future issues/PR will be responded promptly. I am sorry for the huge delay on some existing PRs.
It will take some time to go through all the old issues/PRs. Thank you for your patience.
Any feedback and contributions are highly appreciated.
P.S. The current priority is subscriptions


Extra indentation in matches! macros when many patterns

Code with matches! macros:
matches!(
    expr,
    Enum::Variant1
        | Enum::Variant2
        | Enum::Variant3
        | Enum::Variant4
        | Enum::Variant5
        | Enum::Variant6
);

The same code without macros (correctly formatted):
match expr {
    Enum::Variant1
    | Enum::Variant2
    | Enum::Variant3
    | Enum::Variant4
    | Enum::Variant5
    | Enum::Variant6 => true,
    _ => false,
}

Thanks for the report @UltraMachine. This is the expected/correct formatting per the Style Guide (also a dup of #3208) so I'm going to close this.
In the former/matches! snippet, it's a binop expression as an arg, and binop expressions must be indendented when multilined.
In the latter/match case, match arm patterns are not indented

If required to break the pattern, put each clause of the pattern on its own line with no additional indent, breaking before the |


Please clarify source code license

It's hard to impossible to use this project without license specified.
Thanks in advance!

License specified


ImportError：undefined symbol: _ZN2at4_ops10select_int4callERKNS_6TensorEll

ImportError: /root/miniconda3/envs/myconda/lib/python3.10/site-packages/MultiScaleDeformableAttention-1.0-py3.10-linux-x86_64.egg/MultiScaleDeformableAttention.cpython-310-x86_64-linux-gnu.so: undefined symbol: _ZN2at4_ops10select_int4callERKNS_6TensorEll
my environment：
ubuntu20.04
python 3.10
cuda11.8
pytorch2.1.1
mmdet2.7.0
How to solve this error？Thanks！

This seems to be a dino issue, we are not using that anyway...


Fixed spelling when companion to PDB is missing

 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.:x: mgnslndh sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Need help with underscore support in TS/JS?

👋! Our team at Graphite would love to get underscore support in the official TypeScript/JS library.
Do you need help implementing this? If it's straightforward we might be able to land a patch and accelerate to the v0.3 spec, like you did for Go: https://github.com/jetify-com/typeid/commit/5ffabce2e339d4f390b4672711f29d22d34dd27c

@LucilleH Are you already working on this? Or can the graphite team send us a PR? (if they can send us a PR, let's give them a few pointers)

@savil We just started using it as a default for our IDs :) and we had a thread today where we were struggling with naming:

for the new prefix-ed db ids, is there a standard we want to apply for prefixes? I'm trying to come up with a prefix for SelfTestRunTest. selftestruntest seems a bit long and strange without separators and strt seems semi random and may overlap something else long term

so I'm glad to see that underscore support just landed in time!

@dbalatero I’m planning to implement it tomorrow. If you already have a patch feel free to put out a PR in the jetify-com/opensource repo under typeid/typeid-js folder. If not, rest assured it will be out soon 😃

Closing

@dbalatero love Graphite - thank you for making it 🙏🏾


ACCESS-CM2-tasmax.yaml fails cleaning validation with missing timesteps

From workflow https://argo.cildc6.org/workflows/default/e2e-tasmax-jobs-tv4q6. Blocking progress on run #211.
Both ssp126 and ssp585 failed cleaning validation.
From log of errored validation from ssp126:
Validating gs://clean-b1dbca25/cmip6/ScenarioMIP/CSIRO-ARCCSS/ACCESS-CM2/ssp126/r1i1p1f1/day/tasmax/gn/v20210317.zar
r
Traceback (most recent call last):
  File "/argo/staging/script", line 18, in <module>
    _test_timesteps(ds, data_type, time_period)
  File "/opt/dodola/dodola/core.py", line 645, in _test_timesteps
    assert (
AssertionError: projection cmip6 file is missing timesteps, only has 108405

ssp585 gives the same error:
Validating gs://clean-b1dbca25/cmip6/ScenarioMIP/CSIRO-ARCCSS/ACCESS-CM2/ssp585/r1i1p1f1/day/tasmax/gn/v20210317.zar
r
Traceback (most recent call last):
  File "/argo/staging/script", line 18, in <module>
    _test_timesteps(ds, data_type, time_period)
  File "/opt/dodola/dodola/core.py", line 645, in _test_timesteps
    assert (
AssertionError: projection cmip6 file is missing timesteps, only has 108405

Similar problem to https://github.com/ClimateImpactLab/downscaleCMIP6/issues/345

Nudging @dgergel

Closed with PR #365


Update the Tornjak with consistent naming conventions

Make sure all the mTLS references are changed to client instead of user.
Update the port names to be consistent with other helm charts

See #393 #392


When multiple of the same cargo package are used, dependabot doesn't try to update all of them

Repo: https://github.com/alex/ct-tools
If you look at Cargo.lock, you'll see that bytes is depended on multiple times (one at 0.4.12 and the other at 0.5.2).
However, looking at the update log from dependabot (https://app.dependabot.com/accounts/alex/update-logs/18434808) you can see that it only checks for an update for bytes 0.4.12, not 0.5.2.
You can see the same pattern with smallvec in the same repository.

Has any progress been made on this? Having multiple crate versions in a project is fairly common due to the overall dependency tree.

👋 Sorry for the slow follow-up.
The last comments on this ticket are 2.5 years old, and we've shipped a lot of fixes / improvements since then.
Is this still a reproducible issue or should this be closed?

@jeffwidman Yes, this is still a problem.

I was able to reproduce this with the given repo at https://github.com/alex/ct-tools/commits/b8df336. That revision has indeed two versions of bytes locked, 0.5.6 and 1.0.0.
Dependabot gives this:
$ bin/dry-run.rb cargo alex/ct-tools --commit b8df336 --dep bytes
=> fetching dependency files
=> dumping fetched dependency files: ./dry-run/alex/ct-tools/
=> parsing dependency files
=> updating 1 dependencies: bytes

=== bytes (0.5.6)
 => checking for updates 1/1
🌍 --> GET https://crates.io/api/v1/crates/bytes
🌍 <-- 200 https://crates.io/api/v1/crates/bytes
 => latest available version is 1.4.0
 => latest allowed version is 0.5.6
 => requirements to unlock: update_not_possible
 => requirements update strategy: bump_versions
    (no update possible 🙅♀)
🌍 Total requests made: '1'

However, with native cargo, I learnt the following and was able to update cargo 1.0.0 to 1.4.0:
$ cargo update -p bytes
error: There are multiple `bytes` packages in your project, and the specification `bytes` is ambiguous.
Please re-run this command with `-p <spec>` where `<spec>` is one of the following:
<EMAIL_ADDRESS><EMAIL_ADDRESS>
$ cargo update -p<EMAIL_ADDRESS>-p<EMAIL_ADDRESS>    Updating crates.io index
    Updating bytes v1.0.0 -> v1.4.0

Kudos to cargo by the way for great CLI output clarify, both on error and success.

Here's an example from March 2024:
[[package]]
name = "regex-syntax"
version = "0.6.29"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f162c6dd7b008981e4d40210aca20b4bd0f9b60ca9271061b07f78537722f2e1"

[[package]]
name = "regex-syntax"
version = "0.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c08c74e62047bb2de4ff487b251e4a92e24f48745648451635cec7d591162d9f"

Dependabot run:
updater | 2024/03/29 15:18:08 INFO <job_807284237> Checking if regex-syntax 0.6.29 needs updating
  proxy | 2024/03/29 15:18:08 [021] GET [https://crates.io:443/api/v1/crates/regex-syntax](https://crates.io/api/v1/crates/regex-syntax)
  proxy | 2024/03/29 15:18:09 [021] 200 [https://crates.io:443/api/v1/crates/regex-syntax](https://crates.io/api/v1/crates/regex-syntax)
updater | 2024/03/29 15:18:09 INFO <job_807284237> Latest version is 0.8.3

Does not create PR from 0.8.2 to 0.8.3. The issue is that dependabot checks the first, lower version, which effectively disables dependabot for any crate that is pinned to a lower version.


Get role assignment by ID Example Go code does not work

Link to sample
https://learn.microsoft.com/en-us/rest/api/authorization/role-assignments/get-by-id?tabs=Go
Library name and version
github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/authorization/armauthorization/v2 v2.1.1
Language of the Sample

[ ] C#/.NET
[ ] Java
[ ] JavaScript/TypedScript
[ ] Python
[X] Golang
[ ] Other - Please specify in Issue details field

Sample Issue Type

[X] Sample not working
[ ] Sample missing
[ ] Do not understand sample

Issue details
The Get role assignment by ID example code does not work. As any request using a valid role assignment ID returns in an HTTP 404 response. The strange thing is that it seems to work if I pass in a valid role definition ID (/providers/Microsoft.Authorization/roleDefinitions/<role-definition-ID>).
Does not work
res, err := clientFactory.NewRoleAssignmentsClient().GetByID(ctx, "/subscriptions/<retracted-SubscriptionID>/providers/Microsoft.Authorization/roleAssignments/<retracted-ID>", &armauthorization.RoleAssignmentsClientGetByIDOptions{TenantID: nil})

This works:
res, err := clientFactory.NewRoleAssignmentsClient().GetByID(ctx, "/subscriptions/<retracted-SubscriptionID>/providers/Microsoft.Authorization/roleDefinitions/<retracted-ID>", &armauthorization.RoleAssignmentsClientGetByIDOptions{TenantID: nil})

Expected behavior
I expect to receive an HTTP 200 response, and not a 404.
Actual behavior
Failed to finish the request  GET https://management.azure.com/subscriptions/<retracted-SubscriptionID>/providers/Microsoft.Authorization/roleAssignments/<retracted-ID>
--------------------------------------------------------------------------------
RESPONSE 404: 404 Not Found
ERROR CODE: RoleAssignmentNotFound
--------------------------------------------------------------------------------
{
  "error": {
    "code": "RoleAssignmentNotFound",
    "message": "The role assignment '<retracted-ID>' is not found."
  }
}

Reproduction Steps
Run the Go example code using any role assignment ID
Environment
github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/authorization/armauthorization/v2 v2.1.1
github.com/Azure/azure-sdk-for-go/sdk/azidentity v1.2.2

Closing, it looks like I was running the lookup immediately after creating the role assignment. This is behavior is somewhat expected. I was able to successfully do a lookup if I added some additional retry logic.


yupResolver typescript error

Describe the bug
If I substitute resolver: yupResolver(schema) with resolver: yupResolver<UseForm>(schema) it works as it should.
Codesandbox link (Required)
-Yup resolver
Screenshots

Never mind. I've read that the fix was done in this release: 3.1.1


Build name does not reflect Game Name

The build will always be named "Sample GameLift Build".

Hey! This should be resolved with the latest release, v2.0.0.


Wrong icon button color in code lab screen dump

Building Beautiful UIs with Flutter, step 5, last Simulator screen dump. The > send button icon in the iOS view is black, but should be blue.

cc @LarkAscending

Fixed in early Sept... The black icon was a transient product issue, which got fixed post-I/O!
https://codelabs.developers.google.com/codelabs/flutter/#4


Should "use strict"; always be applied to user code?

Currently all user submitted code is evaluated in strict mode, even if their code does not contain "use strict";.  One challenge discusses strict mode, others make use of it in the description and some fail because of strict mode (see #37534) despite the user code seeming to be correct.
Is it necessary for everything to be evaluated in strict mode or should it go?

If we're evaluating all coding in strict mode, I think we should have it in all challenges

One advantage to evaluating the challenges in strict mode is that it enforces the best practice of defining variables before use.  As long as a "Reference Error" gets displayed to both the FCC console and the browser console, I am happy to explain on the forum that we use strict mode which forces users to define variables at all times.  The problem currently is, code is silently failing for errors like this and users are confused and not understanding what is wrong with their code (see #37534).
My vote is keep strict mode on for all challenges.

The strict mode is enforced (from a very long time) for various reasons as mentioned in comments above, I understand this can be a bit of challenge on specific use cases while we are actually teaching concepts around it.
My vote is to just pass a flag internally (defaulting to something like isStrictMode=true) to the test runner and make use of it in special circumstances like you cited.
A PR is welcome :)

@raisedadead could you elaborate on where this flag should be coming from?  Are you thinking it should be added to the challenge front matter to turn strict mode off for some challenges?

Closing as stale.


Inactive component shows the current buffer's filename

Update to latest version it was fixed in #97. Thanks for reporting :)

Thanks @shadmansaleh


Octave modules

Motivation for this change
This PR would fulfill the request in Issue #65398.
Much of the code mirrors that of lua and python, and not insignificant portions were built out of that.
This is a very messy branch, I know. I attempted a naive approach the first time, which really did not work in my favor.
Things done

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

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

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

No tests were present in nixos/tests for Octave, so there is nothing to do on that front.

@KarlJoad please fix the merge conflict.

@KarlJoad please fix the merge conflict.

@KarlJoad please fix the merge conflict.

Fixed! :smile:

@KarlJoad please fix the merge conflict.

Fixed! :smile:

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108562 run on x86_64-linux 1

2 packages marked as broken and skipped:

octavePackages.level-set
octavePackages.ltfat

5 packages built:

octavePackages.control
octavePackages.io
octavePackages.linear-algebra
octavePackages.signal
octavePackages.symbolic

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108562 run on x86_64-linux 1

2 packages marked as broken and skipped:

octavePackages.level-set
octavePackages.ltfat

5 packages built:

octavePackages.control
octavePackages.io
octavePackages.linear-algebra
octavePackages.signal
octavePackages.symbolic

I have a branch sitting locally right now where I have defined all the packages listed on Octave's Community Packages page. I have been rebasing it to keep it up to speed with the work done on this branch. Once we have reached agreement with how this looks, I want to merge those into here, before merging into master.
The reason I haven't added them here yet is because many of them have runtime dependencies that I need to account for, and I haven't gotten around to those yet.

I have a branch sitting locally right now where I have defined all the packages listed on Octave's Community Packages page. I have been rebasing it to keep it up to speed with the work done on this branch. Once we have reached agreement with how this looks, I want to merge those into here, before merging into master.
The reason I haven't added them here yet is because many of them have runtime dependencies that I need to account for, and I haven't gotten around to those yet.

To simplify the postBuild in wrapper.nix, I want to define a wrap.sh as well, which would be brought into scope with a wrap-octave.nix file. I was looking through both Python's and Lua's examples, and couldn't figure out how to make it work. I know there needs to be a call to makeSetupHook, but when I was working with that, bash functions would only accept a single argument, and completely ignore a second one. My first pass at this is here and the shell script
If I can properly define a wrap.sh file, then that simplifies the building of the path to octave_packages, and will allow me to more easily add packages as run-time dependencies (using propagatedBuildInputs). Doing this would allow me to remove the overrideAttrs that is currently going on in symbolic/default.nix.
See here to see what Python does in wrap.sh.

To simplify the postBuild in wrapper.nix, I want to define a wrap.sh as well, which would be brought into scope with a wrap-octave.nix file. I was looking through both Python's and Lua's examples, and couldn't figure out how to make it work. I know there needs to be a call to makeSetupHook, but when I was working with that, bash functions would only accept a single argument, and completely ignore a second one. My first pass at this is here and the shell script
If I can properly define a wrap.sh file, then that simplifies the building of the path to octave_packages, and will allow me to more easily add packages as run-time dependencies (using propagatedBuildInputs). Doing this would allow me to remove the overrideAttrs that is currently going on in symbolic/default.nix.
See here to see what Python does in wrap.sh.

The nixpkgs contribution manual states that tests should be run (if they don't take too long). An undocumented (in the manual) change to Octave was the introduction of a pkg test built-in function. The only requirement for this is that the package be installed.
An octave package is installed in the build-env.nix file, which becomes problematic. First, the buildEnv function doesn't have a checkPhase defined in its function definition. So, that means it will be part of the postBuild hook. Meaning, there must be a boolean value somewhere for an option to run tests. I have already determined the correct bash/octave code needed to run the tests for every package as well. However, I am not sure about how to inform the system which packages should be tested.

The nixpkgs contribution manual states that tests should be run (if they don't take too long). An undocumented (in the manual) change to Octave was the introduction of a pkg test built-in function. The only requirement for this is that the package be installed.
An octave package is installed in the build-env.nix file, which becomes problematic. First, the buildEnv function doesn't have a checkPhase defined in its function definition. So, that means it will be part of the postBuild hook. Meaning, there must be a boolean value somewhere for an option to run tests. I have already determined the correct bash/octave code needed to run the tests for every package as well. However, I am not sure about how to inform the system which packages should be tested.

There are some packages that are quite old and haven't been updated for quite some time and are quite difficult to build. Is there a rule-of-thumb for how old a package should be before we consider dropping it?
For instance, the secs2d package hasn't received a release update since 2009. There are some others like this as well.

There are some packages that are quite old and haven't been updated for quite some time and are quite difficult to build. Is there a rule-of-thumb for how old a package should be before we consider dropping it?
For instance, the secs2d package hasn't received a release update since 2009. There are some others like this as well.

Is there a rule-of-thumb for how old a package should be before we consider dropping it?

If it is broken for a longer time, patching the build failure is non trivial and upstream has no commits for a year or two would be a pretty good indication to drop it.

For instance, the secs2d package hasn't received a release update since 2009. There are some others like this as well.

If there is activity on the repo you can try to fetch the latest commit. If that is from 2009 or 2010 than I wouldn't feel bad removing it if it is not vital for the ecosystem.

Is there a rule-of-thumb for how old a package should be before we consider dropping it?

If it is broken for a longer time, patching the build failure is non trivial and upstream has no commits for a year or two would be a pretty good indication to drop it.

For instance, the secs2d package hasn't received a release update since 2009. There are some others like this as well.

If there is activity on the repo you can try to fetch the latest commit. If that is from 2009 or 2010 than I wouldn't feel bad removing it if it is not vital for the ecosystem.

If there is activity on the repo you can try to fetch the latest commit. If that is from 2009 or 2010 than I wouldn't feel bad removing it if it is not vital for the ecosystem.

The sourceforge repo for that project doesn't even exist any more, so I think it's safe to assume secs2d (along with is sibling packages secs1d and secs3d are not actively maintained either.
What would be the best way to remove them from the PR? A revert seems excessive. Rebase and drop the relevant commits?

If there is activity on the repo you can try to fetch the latest commit. If that is from 2009 or 2010 than I wouldn't feel bad removing it if it is not vital for the ecosystem.

The sourceforge repo for that project doesn't even exist any more, so I think it's safe to assume secs2d (along with is sibling packages secs1d and secs3d are not actively maintained either.
What would be the best way to remove them from the PR? A revert seems excessive. Rebase and drop the relevant commits?

@KarlJoad In general, I think this PR should have only roughly these commits:
octave.pkgs: init

Add attributes to passthru of octave, add wrap-octave.nix etc.

And then:
octave.pkgs.symbolic: init at ...
octave.pkgs.io: init at ...
...

When you change something in the design of all of octave.pkgs, you can commit that with --fixup for the first octave.pkgs: init commit, see this. The same goes for any other later change you do with a certain octave package.
All of the information about how this PR got evolved doesn't have much meaning IMO.

@KarlJoad In general, I think this PR should have only roughly these commits:
octave.pkgs: init

Add attributes to passthru of octave, add wrap-octave.nix etc.

And then:
octave.pkgs.symbolic: init at ...
octave.pkgs.io: init at ...
...

When you change something in the design of all of octave.pkgs, you can commit that with --fixup for the first octave.pkgs: init commit, see this. The same goes for any other later change you do with a certain octave package.
All of the information about how this PR got evolved doesn't have much meaning IMO.

I have also managed to fix almost all of the packages that were marked as broken before.
I will need to open PRs for the last 4 that are broken.

Well done for all the work so far @KarlJoad. Overall this looks good to me though I will not be able to test this thoroughly until the end of the month. I still think though that the commit history could be squashed a bit further. The following could be squashed into one octave.pkgs: init IMHO:
octave: add predicate to check if a package is an octave package
octave: define self for this derivation
octave-packages: add octavePackages to all-packages.nix
octave-packages: use new requiredOctavePackages build list
octave-packages: write a withPackages function
octave.pkgs: unpack octave packages
octave.pkgs: use inherit packages (implicitly when possible)
octave.pkgs: use nativeBuildInputs and buildInputs appropriately
octave.pkgs: with stdenv.lib; in meta -> with lib;
octave.pkgs: write buildOctavePackage function
octave.pkgs: write function build environment with octave packages
octave: remove second evaluation of pkgs inside octave's build
octave: start a wrapper.nix, mirroring python's
octave: start working on building environment to use everything with
octave: start work on top-level file for octave packages

You can write some implementation details inside the commit message I guess, but besides that I personally see them all as part of the same thing.
Also this commit:
octave.pkgs: change src.url octave.sourceforge -> mirror://sourceforge

Could be part of the init's of every new octave package added.

How should I go about running tests, if at all?
Octave requires a package be built and installed before being able to run tests on it.
This means that there is no way to run the tests during the compilation of the packages. I already have a script that runs tests for all packages that have been installed, but I'm not sure that we want to run tests on all packages specified every time someone creates an new environment with new octave packages.
Is there a way to have these tests always be run on hydra, and the end-user can specify if they want to run tests on their package/environment?

How should I go about running tests, if at all?

What I meant by "tests" is just running an octave interpreter with those packages available, and testing a few examples from these packages' docs - very manual, not necessarily putting it into the Nix expressions.

I already have a script that runs tests for all packages that have been installed, but I'm not sure that we want to run tests on all packages specified every time someone creates an new environment with new octave packages.

I agree. Could you perhaps share that script?

Is there a way to have these tests always be run on hydra, and the end-user can specify if they want to run tests on their package/environment?

Perhaps that would be nice to get done in the future, but it shouldn't block the PR IMO.

Besides that, everything looks good to me now :] with the commit history rewritten. I'll test some packages manually at the end of the month and I'll give my approval if all looks well. Thanks for all the hard work @KarlJoad !

With Octave 6.x a new command pkg test <package name>, or pkg("test", "package-name"). was created. It runs all the tests in a package's test suite.
This test suite is included when the author of the package is writing it, so it tests most major functionalities (some packages have lackluster testing suites, but that's a different issue).
The "script" to test all packages currently installed into this Octave environment.
pkgs = pkg ("list");
for pkgNum = 1:numel (pkgs)
  thisPkg = pkgs{pkgNum}.name
  pkg ("load", thisPkg)
  pkg ("test", thisPkg)
  rename ("fntests.log", strcat (thisPkg, "-fntests.log"))
endfor

Thanks once more @KarlJoad for all the work. I took the liberty to shorten the commit messages even further to include only necessary information. I tested symbolic which I intend to use in my default octave interpreter and I also tested strings (as a random example) and it proved to be functional enough. Will merge once CI is green! :tada: .
The next step is to document how Octave packages are handled in Nixpkgs... :book:.

Hey, @doronbehar. Sorry for the ping, and i know this isn't exactly the right place to ask, but i've looked around and couldn't get symbolic working using nix at all.

I'd love to help document this if at all possible, too.

Got it working using octave.withPackages, just in case someone stumbles upon this
{ pkgs ? import <nixpkgs> {} }:
pkgs.mkShell {
  nativeBuildInputs = with pkgs; [
    (octave.withPackages (ps: with ps; [symbolic]))
  ];
}

@Misterio77, while technically possible open a shell with the octave package completely standalone, there is some trickery with text-based database files when using withPackages that is required to make packages usable with the actual octave package. If you specify just the package, then the package will be downloaded, compiled, and saved as an output tarball for later installation. If you want to actually use the package, then you must specify octave.withPackages, much like you must with Python.

That makes a lot more sense! Thanks for helping a newbie understand it haha :))


Update extension name

SQL Server 2019 extension has been renamed to Data Virtualization

@Charles-Gagnon : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


penumbra-ibc: handle evidence in MsgUpdateClient

Is your feature request related to a problem? Please describe.
With the 0.7.0 release of ibc-go, misbehavior evidence handling via MsgSubmitMisbehavior has been deprecated.
Describe the solution you'd like
Misbehavior submission happens as an in-band client update. When we detect it, we should freeze the associated client.

Discussed at ibc sync today. @avahowell claims this is already implemented, but some code comments should be added to make it clear we're handling this use case.

We're already freezing the client in the case of equivocation in MsgUpdateClient:
https://github.com/penumbra-zone/penumbra/blob/efb45653031e7f9a2ea16e93afbedd744a44b4f3/crates/core/component/ibc/src/component/msg_handler/update_client.rs#L121
https://github.com/penumbra-zone/penumbra/blob/efb45653031e7f9a2ea16e93afbedd744a44b4f3/crates/core/component/ibc/src/component/client.rs#L45

Closing this for now since we already do it

I agree this isn't a huge deal, but we don't actually do this. We do detect duplicate headers, and freeze clients accordingly, but we don't allow relayers to submit evidence via MsgClientUpdate. The reason why this isn't a huge deal is because we can just make hermes forward the equivocating headers in a regular update. However, it seems like a low hanging fruit to just peek at the client updates for a client_message that corresponds to misbehavior.

I guess the emphasis of this ticket is on detecting and validating evidence, rather than detecting equivocation.


new clang nullability-completeness build warns

There are 783 new build warns all resulting from -Wnullability-completeness in VulkanMemoryAllocator commit f9921aefddee2437cc2e3303d3175bd8ef23e22c, clang 9.0.1 hosted by Visual Studio 2017. I've turned off that warning as a workaround. vk_mem_alloc.cpp is a file consisting of "#define VMA_IMPLEMENTATION #include "vk_mem_alloc.h" as recommended by https://gpuopen-librariesandsdks.github.io/VulkanMemoryAllocator/html/quick_start.html#quick_start_project_setup.
The attached vma-build-warns.txt file contains the build log as including it here would push this message body past github's 65536 character limit.
vma-build-warns.txt

I'm sorry but I'm not going to add the nullability annotations to all internal functions of the library. Having them on the public interface adds enough obfuscation to the code.
As the documentation says in the "Features not supported" chapter, being free of any compiler warnings on any version of any compiler is out of scope of the library.


[SchemaRegistry] update release date 1.3.0b1

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


Simple shared memory model yields unfoldCTbranch: Not unique

The following model consists of a process which reads an integer existing in a list synced with another process reading the same integer uncoditionally and outputting it through channel A.

TYPEDEF List_Int
    ::= NilList_Int
    |   List_Int { head :: Int; tail :: List_Int }
ENDDEF

CONSTDEF
    numbers :: List_Int ::= List_Int(1, List_Int(2, List_Int(3, NilList_Int)))
ENDDEF

FUNCDEF in (x :: Int; list :: List_Int) :: Bool
    ::= IF isNilList_Int(list) THEN False
        ELSE IF head(list) == x THEN True
        ELSE in(x, tail(list))
        FI FI
ENDDEF

PROCDEF ListState [Read :: Int] (state :: List_Int)
    ::= Read ? y [[ in(y, state) ]] >-> ListState [Read] (state)
ENDDEF

PROCDEF StartPs [A :: Int] ()
    ::= HIDE [ Read :: Int ] IN
        ListState [ Read ] (numbers)
    |[ Read ]|
        Do [A, Read] ()
    NI
ENDDEF

PROCDEF Do [A :: Int; Read :: Int] ()
    ::= Read ? y >-> A ! y >-> Do [A, Read] ()
ENDDEF

CHANDEF Chans ::=
    A :: Int
ENDDEF

MODELDEF Model ::=
    CHAN IN
    CHAN OUT A
    BEHAVIOUR StartPs [A] ()
ENDDEF

yields
➜  prl-model-based-tester git:(master) ✗ torxakis model/memory.txs

TXS >>  TorXakis :: Model-Based Testing

TXS >>  txsserver starting: "localhost" : 33801
TXS >>  Solver "cvc4" initialized : cvc4 [1.6-prerelease]
TXS >>  TxsCore initialized
TXS >>  input files parsed:
TXS >>  model/memory.txs
TXS >> stepper Model
TXS >>  unfoldCTbranch: Not unique
TXS >>  Stepper started
TXS >> step 100
TXS >>  no state or deadlock
TXS >>  FAIL: No Output (Quiescence)

While I would expect the model to constantly yield either 1, 2, or 3.  The sample is greatly inspired by the shared memory example. I'm probably missing something here, but I cannot figure out what.
It worth noting that not using shared memory (i.e. A ? x [[ in(x, numbers) ]] ) works fine.
The same behaviour can be seen in both z3 as cvc4.

I think you want:
PROCDEF Do [A :: Int; Read :: Int] ()
    ::= Read ? y | A ! y >-> Do [A, Read] ()
ENDDEF

Since in this case, the externally read value makes the internal/ hidden read value unique.

Your proposed solution yields an Undefined Entity for y communicated over A. Could this be a bug in the latest linux version (0.7) fixed in the latest releases (0.8+) ?

If I replace A ! y with A ! 20, which is not the desired behaviour; since I want a value from the state list. It yields another runtime error.
TXS >> stepper Model
TXS >>  Stepper started
TXS >> step 4
TXS >>  .....1: Act { { ( A, [ 20 ] ) } }
TXS >>  after: cannot find unique value for hidden variables
TXS >>  stepN - cannot do action
TXS >>  FAIL: Act { { ( A, [ 20 ] ) } }

Are there some resources available on the topic of the uniqueness of values? What are the specific constraints here? Why must it find a unique value? Any value from the state [1,2,3] should be fine.

Sorry i was too fast:
'Read ? y1| A ? y2 [[y1 ==y2]] >-> Do [A, Read] ()'
TorXakis requires that all hidden communication is unique to ensure the number of states to be considered remains finite. The wiki should contain this info. Please complain / submit an issue when you can't find it or it is not sufficient for you.
I can't promise we will solve it quickly, but it is archived....

BTW
Why don't you simplify
PROCDEF ListState [Read :: Int] (state :: List_Int)
    ::= Read ? y [[ in(y, state) ]] >-> ListState [Read] (state)
ENDDEF

PROCDEF StartPs [A :: Int] ()
    ::= HIDE [ Read :: Int ] IN
        ListState [ Read ] (numbers)
    |[ Read ]|
        Do [A, Read] ()
    NI
ENDDEF

PROCDEF Do [A :: Int; Read :: Int] ()
    ::= Read ? y >-> A ! y >-> Do [A, Read] ()
ENDDEF

to just
PROCDEF StartPs [A :: Int] ()
    ::= A ? x [[ in(x,numbers) ]] >-> StartPs [A]()
ENDDEF

It was part of a larger model, where I need to synchronise state updates between processes.  There I ran into the lack of uniqueness. When recreating the issue in a smaller model I found that the Write did not cause issues; hence I left it out of the example in this issue.
Your suggestion Read ? y1| A ? y2 [[y1 ==y2]] >-> Do [A, Read] () resolved the issue in the example, thanks! I'm integrating it into the larger model right now.
I will close the issue for now.


Electron Crashing Inside IPC call on face-api.js call

Preflight Checklist

[x] I have read the Contributing Guidelines for this project.
[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

Electron Version:

v9.0.4

Operating System:

Ubuntu 20.04.1 LTS

Last Known Working Electron version:

not applicable

Node Version:

v14.6.0

NPM Version:

6.14.6

Node Library Versions:

package.json

Expected Behavior

line 21 of my example project in recognition.ts should run
faceapi.detectAllFaces(...)
Actual Behavior

Crashed with almost no information about why the process has failed.
To Reproduce

Please see below for a working example.

Recommended platform Linux
Recommended OS Ubuntu 20.04.1 LTS
$ sudo apt install make g++ libpixman-1-dev libcairo2-dev libpango1.0-dev libjpeg8-dev libgif-dev
$ sudo npm i -g node-gyp
$ git clone https://github.com/a93h/electron-quick-start-typescript
$ cd electron-quick-start-typescript
$ npm i
$ ./node_modules/.bin/electron-rebuild
$ export ELECTRON_ENABLE_LOGGING=true
$ npm start

Screenshots

Additional Information

Was hoping somebody could show me why or why this is not a face-api.js problem.
Thanks,

Really new to electron and not entirely certain if this is an electron issue or face-api.js
I assume I don't fully comprehend how the electron library works and since face-api.js was working before I put it inside an ipc call I believe I am not integrating electron and face-api.js properly.

I found a proprietary replacement in the meantime but getting this working would be nice.


[backport v1.0] [Question] VM image management for productive environment: best practices

backport the issue https://github.com/harvester/harvester/issues/2174

duplicated with  https://github.com/harvester/harvester/issues/2474 ，  close this issue


Presence offline while still connected

We have a couple of devices that are 24/7 connected with the deepstream server.
The first couple of days when we ask the presence of these devices they show up online, after 3 days or so they suddenly all go offline in presence.
They are 100% still online because they provide a unique rpc call and when you use this rpc call they just respond, but presence still acts as if they are offline.
From what I can gather from the code, "client-connected" and "client-disconnected" events are used to determine the presence. The disconnected event is emitted in _onSocketClosed of "uws-connection-endpoint.js" so it leads me to believe this function is called while the socket is in fact still open?

Hi @bartpeeters - thanks for raising,happy to look into it asap. Could I ask you for a few more details though:

are you using deepstream to gather metrics from electricity meters? If so, what kind of operating system/client are you running?
it is possible for a client to count as offline without invoking _onSocketClosed if multiple consecutive heartbeats are missed - are you using any special settings for heartbeatinterval or timeout?
do you have any server logs that show how the clients disconnect?

Thanks so much,
Wolfram

We are also experiencing the same problem. Using these settings for our clients:
maxReconnectAttempts: Infinity,
reconnectIntervalIncrement: 1500,
heartbeatInterval: 10000,
maxReconnectInterval: 5000

This night it happened again. I checked the logs but there is nothing out of the ordinary. I'm using the default log level though. I'll change it to DEBUG and report back if I find something.

Thank you for the updates. We'll also add some more debug lines in the upcoming release to see if we can find out where the issue is coming from

Any news on this? This is real for us and we rolled back to our own solution counting connections manually until this is solved.

Closing due to inactivity

I have absolutely the same issue with latest Deepstream(linux, node.js)
My microservices always disappeared from presence after few days of work. But microservices is alive and connected and RPCs is accessible.
No interesting in logs at all 🤔

Hi,  without some code to reproduce it's hard to fix...can you ran your server on DEBUG log level to see if anything shows?
There is a caveat with the presence.query call on the client (I think it's not properly documented):

client.presence.getAll() : will return all connected clients leaving out the client who is making the query.
client.presence.getAll([userIds]) : will return the answer to the presence of the given userIds

Here is the presence handler source if you can find anything: https://github.com/deepstreamIO/deepstream.io/blob/master/src/handlers/presence/presence-handler.ts
Are your services being authenticated ? Because if not, they will not show in presence...They must have a userId assigned to the socket after authentication.
Let me know if this helps..

Thanks for response.
Can't reproduce the issue right now because often restart server due active development.
Changed log level to DEBUG.

Still have a problem. No micro services in presence after 3 days of work. But RPCs inside microservices is accessible and records API seem to be work fine.
Only record.listen('/my-path/.*', async (topic, response) => {}) in some cases didn't send changes but I don't localize problem yet.
Nothing interesting in logs (DEBUG mode) except
| CLUSTER_LEAVE | kw0i5urp-1jtvcphl7clc0
| CLUSTER_SIZE | The cluster size is now 0
| CLUSTER_JOIN | kw0i5urp-1jtvcphl7clc0
| CLUSTER_SIZE | The cluster size is now 1

Maybe it happens after that?

Did your server restarted in that cluster size change?

Did your server restarted in that cluster size change?

I think no
I have 2 development and 1 production servers running on the same host but at different subdomains with Docker/Traefik. Maybe I need different ports for each server?
I don't need any clustering right now.
Why cluster size is changed? What does it mean?

I also noticed that record listen is stop working after Presence stopped
my code
client.record.listen('microservice#'+endpoint+'/list/.*', async (topic, response) => {
    const match = topic.match(`${endpoint}/list/(.*)`);
    if(!match) return response.reject(); // ??????
    const hash = match[1];

    const snapshot = filterHashes[hash];
    if(!snapshot) return response.reject();  // Hash not found ????
    const { filters, noDeleted } = snapshot;

    let myCursor;
    const recordName = `${endpoint}/list/${hash}`;

    r.table(COLLECTION)
       .filter(filterFn(filters))
       .pluck('id','_deleted',...GRID.filter(i => i.hidden !== true)
       .changes()
       .run(connection, async (err, cursor) => {
           if (err) throw err;
           myCursor = cursor;
           cursor.each(async (err, row) => {
               if (err) throw err;
               const data = await getList(filters, noDeleted);
               const previousResults = await client.record.snapshot('microservice#'+recordName);

               console.log('Changed', recordName); // <------- This not happened after Presence API stop working

               if(!iris.deepEqual(data, previousResults)) {
                   client.record.setData('microservice#'+recordName, { data, schema, options });
               }
           });
       });

    response.onStop(async () => {
        myCursor && myCursor.close && myCursor.close();
        client.record.setData('microservice#'+recordName, {}); // Clear record
    });

    response.accept();
});

I noted that when I kick out users with using
server.services.httpService.getSocketWrappersForUserId(user_id)
      .forEach(socketWrapper => socketWrapper.close());

presence also not updated☝

Hi, if you close the socket directly, you won't be calling the onsocket close callback, I think you should do something like this:
server.services.httpService.getSocketWrappersForUserId(user_id)
      .forEach(socketWrapper => {
    server.services.connectionEndpoints.forEach(endpoint=> {
         endpoint.onSocketClose.call(endpoint, socketWrapper)
        this.connections.delete(socketWrapper.socket)})
    })
});

Take a look at how connections are closed here for example: https://github.com/deepstreamIO/deepstream.io/blob/master/src/services/http/uws/uws-http.ts#L216

Since presence register a connection listener:
https://github.com/deepstreamIO/deepstream.io/blob/master/src/deepstream.io.ts#L298

Authenticated socket calls onClientConnected:
https://github.com/deepstreamIO/deepstream.io/blob/master/src/deepstream.io.ts#L345

If you close the socket directly, the onSocketClose callbacks wont be called, and presence depends on that in order to update the distributed state. onSocketClose calls socket.close() and also all other services that are registered to that event.

Hi, if you close the socket directly, you won't be calling the onsocket close callback, I think you should do something like this:

Thanks for response.🙂
connections.delete(socketWrapper.socket)}) breaks the execution
This code looks like working well. Presence also updated
    server.services.httpService.getSocketWrappersForUserId(user_id)
        .forEach(socketWrapper => {
            server.services.connectionEndpoints.forEach(endpoint=> {
                if(endpoint.onSocketClose)
                    endpoint.onSocketClose.call(endpoint, socketWrapper);
            });
            socketWrapper.close();
        })

About subject of this issue...
I think I found the problem and it's not a deepstream.io problem.
It's a bug in my code for working with RethinkDB.
You can close the issue.

ok glad it worked


Check autocomplete combo box for a keyboard trap bug

Testing of Notfiy's autocomplete combo box uncovered an edge case bug. Let's check our implementation to make sure the issue is resolved:
Steps to reproduce:
So this seems to happen in Firefox, and the steps to replicate are very precise. I’m not on voiceover, just doing keyboard navigation:

Tab until the autocomplete box
Escape
Shift-tab to move focus upwards
Shift once to focus the autocomplete box again
The next shift will focus at the top of the page, and you will be trapped within the top and autocomplete box elements.

@muoyopopo This should have been tested during the fabel test. Did we see any evidence of a key trap when users used the typeahead feature?

We did this in the last round of fable testing. No keyboard trap was found.


Improve csv export

Exclude 'id', 'created_at', 'updated_at' and 'publishing_consent' from csv file (see issue #18).
I also added tests for an attribute that requires publishing consent to see if it is included in the csv or not according to the publishing consent given.

thanks @lisbethmarianne ! Sorry it took me a bit to look at this. Next time pls feel free to ping me either in the JAA chat or here. :)


Refactor and add unit tests for error checks

Highly recommended to view diffs with whitespace ignored (this link is a shortcut to view diffs with that setting turned on).

Refactors repeated logic which checks for various ARM template deployment errors into its own unit-tested function.
Adds unit tests for individual ARM template deployment error checking functions.
Removes some unnecessary blocks.
Standardizes the logging in a couple of other tests.
Fixes a bug in which a nil error would be returned after waiting for an ARM template to be deployed.

thanks! will merge on green


Files On-Demand?

The current MacOS-OneDrive-KFM works great, but is there a supported way to enable Files On-Demand?
Currently I see the option to enable Files On-Demand, but when I click on Enable the OneDrive clients signs in again and the option is then not enabled.  I would like this in the plist so that it is enabled by default.
Thank you.

This is also frustrating to me. Files on demand works until we run this script, but then after it's not just that it's turned off, but users can no longer turn it on. Very frustrating. I haven't been able to identify what causes this in the script.

That would be frustrating.  We haven't seen this issue with our users.  The script is not intended to "mess" with any FilesOnDemand settings.  Are you using the AppStore version or the stand alone app?  I have not tested the AppStore version.  Also work validating you don't have a policy turning off FOD checking the output of:  defaults read ~/Library/Preferences/com.microsoft.OneDrive.plist  Maybe the AppStore version keeps preferences in a different location?

Also using the standalone version. No clues to be found in the plist. Even tried adding a setting to forcefully enable and it's still disabled and won't be enabled. The feature works before running the OneDrive-KFM script and then refuses to enable afterward. I've duplicated this on numerous systems running Mojave and Catalina.
Settings reference:
https://docs.microsoft.com/en-us/onedrive/deploy-and-configure-on-macos
Commands and results (private info x'd out):
defaults read ~/Library/Preferences/com.microsoft.OneDrive.plist
{
BITApplicationDidEnterBackgroundTime = "1583525979.913621";
BITApplicationWasLaunched = 1;
HockeySDKAutomaticallySendCrashReports = 0;
HockeySDKCrashReportActivated = 1;
IsBusinessProvisioned = 1;
NSOpenGLContextReplaceViewLayer = 0;
OpenAtLogin = 1;
Tenants =     {
"xxxxx" =         {
DefaultFolder = "xxxxx";
};
};
UpdateRingSettingsLastSuccess = 18327;
}
defaults write ~/Library/Preferences/com.microsoft.OneDrive.plist FilesOnDemandEnabled 1
defaults read ~/Library/Preferences/com.microsoft.OneDrive.plist
{
BITApplicationDidEnterBackgroundTime = "1583525979.913621";
BITApplicationWasLaunched = 1;
FilesOnDemandEnabled = 1;
HockeySDKAutomaticallySendCrashReports = 0;
HockeySDKCrashReportActivated = 1;
IsBusinessProvisioned = 1;
NSOpenGLContextReplaceViewLayer = 0;
OpenAtLogin = 1;
Tenants =     {
"xxxxx" =         {
DefaultFolder = "xxxxx";
};
};
UpdateRingSettingsLastSuccess = 18327;
}

The only area that the script touches is setting the tenant ID in the plist.  Maybe worth testing is a machine that has FOD working just fine, then close OneDrive and from a terminal run these commands (filling in the variables as appropriate).  Then launch OneDrive again and see if the error is reproduced.
defaultTenantID="XXXXX"
defaultOneDriveFolder="/Users/joeuser/OneDrive - TennantName"
userHomeDirectory="/Users/joeuser"

/usr/libexec/PlistBuddy -c "Add :Tenants:$defaultTenantID:DefaultFolder string '$defaultOneDriveFolder'" "$userHomeDirectory/Library/Preferences/com.microsoft.OneDrive.plist"

Thanks for the tip! I was just looking at that very line and wondering how I could easily test it for culpability when you posted!

Clean system, no OneDrive KFM config profile or package or outset or anything
Signed into OneDrive (standalone)
FoD is functional, Finder extensions and everything
Restarted, logged out/in, very consistently working
Checked plist before:

defaults read ~/Library/Preferences/com.microsoft.OneDrive.plist
{
    BITApplicationDidEnterBackgroundTime = "1583528824.533716";
    BITApplicationWasLaunched = 1;
    HockeySDKAutomaticallySendCrashReports = 0;
    HockeySDKCrashReportActivated = 1;
    IsBusinessProvisioned = 1;
    NSOpenGLContextReplaceViewLayer = 0;
    OpenAtLogin = 1;
}

Set variables and ran the command you shared
Checked plist after:

defaults read /Users/lseth/Library/Preferences/com.microsoft.OneDrive.plist
{
    BITApplicationDidEnterBackgroundTime = "1583528824.533716";
    BITApplicationWasLaunched = 1;
    HockeySDKAutomaticallySendCrashReports = 0;
    HockeySDKCrashReportActivated = 1;
    IsBusinessProvisioned = 1;
    NSOpenGLContextReplaceViewLayer = 0;
    OpenAtLogin = 1;
    Tenants =     {
        "xxxxx" =         {
            DefaultFolder = "xxxxx";
        };
    };
}

FoD still working
Restarted, logged out/in, very consistently working

I don't know. I've got my eye on the "chown" commands in the login-privileged-every script. I'll try to test that next, but it may take me a while to read through the script and understand what all it's doing.
Please let me know if you have other suspicions I can test.

I have confirmed that the culprit is the rsync command, which merges files from the backup path into the OneDrive location. After you run that, close and re-open OneDrive, you can no longer turn on FoD. I'm looking at the syntax to see if I can figure out why it's the problem and hopefully figure out a way to fix it.

It looks like the issue is that FoD uses extended attributes (source: https://www.reddit.com/r/onedrive/comments/dk8hcx/onedrive_on_macos_is_adding_extendedfile/). By using rsync with the -E option, those extended attributes are stripped from the root OneDrive folder. I was able to solve it by breaking out the rsync into two commands, one for Desktop and one for Documents, instead of simply running it at the root folder.
Original:
            rsyncResults=$(rsync --checksum --remove-source-files --ignore-existing -avhE "$backupPath/" "$defaultOneDriveFolder/")
Fixed:
            rsyncResults=$(rsync --checksum --remove-source-files --ignore-existing -avhE "$backupPath/Desktop/" "$defaultOneDriveFolder/Desktop/"; rsync --checksum --remove-source-files --ignore-existing -avhE "$backupPath/Documents/" "$defaultOneDriveFolder/Documents/")

Great find! #

Great find.  This has been tested and updated.