Defer all camel-casing to the Typescript client

I think it's confusing how some names are converted to camel case when being written to the IDL, and then the Typescript client adds some camel casing of its own. It means the IDL names don't match either the smart contract code or the client code.
This gets extra confusing when writing Python client code where the casing conventions line up with Rust conventions - if the camel casing was all deferred to Typescript then the Python names could match the Rust names and the IDL names.
I'd be willing to make a PR for this. The result would be that IDLs would change but there would be no breaking changes for Typescript client users.

I think this is worth changing, as the IDL casing isn't very consistent. But in regardless, clients should probably just change the case into whatever it wants and try to be agnostic to the IDL casing. The typescript client, for example, should always translate into the camel case.

Fixed in https://github.com/coral-xyz/anchor/pull/2824.


Single tap cause exception

In chrome v38, open dev tool, simulate touch screen.
When using swipe slide switch all right, but a single tap will cause the exception.
Uncaught TypeError: undefined is not a function
In code
self.events.on("tap", function(endX) {
*    if (endX < self.getContainerWidth() / 2) {
        self.slideshow.gotoPreviousSlide()
    } else {
        self.slideshow.gotoNextSlide()
    }
})

The line prefix with * is causing the exception.

Sorry for the late reply. The fix for this issue will be included in the next relase.

This has now been released in version 0.12.


[now-client] Use @zeit/fetch instead of node-fetch

We want to take advantage of the better defaults and retry policies (among others).
This bumps @zeit/fetch and replaces node-fetch with @zeit/fetch in now-client.
Also update retry policy for "uploading" files to:

base 10ms
5 retries
factor 6

which means the timeouts are 10, 60, 360, 2160, 12960

Codecov Report

Merging #3490 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3490      +/-   ##
==========================================
- Coverage   14.59%   14.55%   -0.04%
==========================================
  Files         267      267
  Lines       10779    10750      -29
  Branches     1483     1483
==========================================
- Hits         1573     1565       -8
+ Misses       9039     9018      -21
  Partials      167      167

Impacted Files
Coverage Δ

src/util/dev/server.ts
59.66% <0%> (+0.05%)
:arrow_up:

src/util/dev/builder.ts
65.88% <0%> (+0.59%)
:arrow_up:

src/util/get-update-command.ts
10% <0%> (+0.62%)
:arrow_up:

src/util/get-files.ts
90.5% <0%> (+0.88%)
:arrow_up:

src/util/output/create-output.ts
60% <0%> (+2.59%)
:arrow_up:

src/util/dev/yarn-installer.ts
83.33% <0%> (+3.64%)
:arrow_up:

src/util/dev/router.ts
73.23% <0%> (+3.9%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9deb5b3...26c0040. Read the comment docs.


[tool_crash] FileSystemException: Cannot create link, OS Error: Operation not permitted, errno = 1

Command
flutter pub get

Steps to Reproduce

...
...
...

Logs
FileSystemException: Cannot create link, OS Error: Operation not permitted, errno = 1
#0      _Link.throwIfError (dart:io/link.dart:263:7)
#1      _Link.createSync (dart:io/link.dart:184:5)
#2      ForwardingLink.createSync (package:file/src/forwarding/forwarding_link.dart:20:16)
#3      ForwardingLink.createSync (package:file/src/forwarding/forwarding_link.dart:20:16)
#4      _createPlatformPluginSymlinks (package:flutter_tools/src/flutter_plugins.dart:1057:12)
#5      createPluginSymlinks (package:flutter_tools/src/flutter_plugins.dart:987:5)
#6      refreshPluginsList (package:flutter_tools/src/flutter_plugins.dart:1089:5)
<asynchronous suspension>
#7      FlutterProject.ensureReadyForPlatformSpecificTooling (package:flutter_tools/src/project.dart:350:5)
<asynchronous suspension>
#8      PackagesGetCommand.runCommand (package:flutter_tools/src/commands/packages.dart:175:5)
<asynchronous suspension>
#9      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1209:27)
<asynchronous suspension>
#10     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#11     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
<asynchronous suspension>
#12     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#14     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
<asynchronous suspension>
#15     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)

[✓] Flutter (Channel stable, 3.3.10, on Ubuntu 22.04.2 LTS 5.19.0-32-generic, locale en_IN)
    • Flutter version 3.3.10 on channel stable at /home/krishna/snap/flutter/common/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 135454af32 (10 weeks ago), 2022-12-15 07:36:55 -0800
    • Engine revision 3316dd8728
    • Dart version 2.18.6
    • DevTools version 2.15.0

[!] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /home/krishna/Android/Sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/linux#android-setup for more details.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • clang version 10.0.0-4ubuntu1
    • cmake version 3.16.3
    • ninja version 1.10.0
    • pkg-config version 0.29.1

[✓] Android Studio (version 2021.3)
    • Android Studio at /snap/android-studio/125/android-studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] VS Code
    • VS Code at /snap/code/current
    • Flutter extension version 3.58.0

[✓] Connected device (3 available)
    • Android SDK built for x86 (mobile) • emulator-5554 • android-x86    • Android 11 (API 30) (emulator)
    • Linux (desktop)                    • linux         • linux-x64      • Ubuntu 22.04.2 LTS 5.19.0-32-generic
    • Chrome (web)                       • chrome        • web-javascript • Google Chrome 109.0.5414.119

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 135454af32477f815a7525073027a3ff9eff1bfd
Plugins
path_provider-2.0.12
path_provider_android-2.0.22
path_provider_foundation-2.1.1
path_provider_linux-2.1.8
path_provider_windows-2.1.3

@rajkumar20221 It looks like something goes wrong with permission. Can you try granting permission to Flutter SDK/project directory/pub cache directory and see if it works?


can't scroll on channel creation page when keyboard popped up

Keyboard covers available fields and you have to click in and out of the keyboard to get through the process

Fixed. The lower area should now be scrollable when the soft keyboard is displayed.


Laissez faire duedate parsing

Proposal for the duedate parser, as pseudocode that takes the urtext as a string and returns the timestamp of the duedate:

replace dashes and underscores and slashes in urtext with spaces
do some other handy substitutions like  by dec5 ->  by dec 5 and  by (.*)tmw(.*) ->  by $1tomorrow$2
run the thus-transformed urtext through Sherlock and return the timestamp

(Tagging as Mendoza because we need to address in some way the fact that a lot of promises currently don't adhere to the /by/ syntax.)

Collecting pros and cons of Laissez faire (LAI) vs Rigidity (RIG):

RIG: There probably exist cases we'll fail to parse without being able to throw away everything before /by/
RIG: Code that tried to be too clever for its own good is the worst.
LAI: Let's us punt on exactly what the rigid format should be.
LAI: There’s no rigidity with what comes after the /by/ anyway, it’s just "let Sherlock do its magic" so might as well let Sherlock do it on the whole urtext.
LAI: Empirically it seems to parse the whole urtext just as well as the post-/by/ text.

And reasons the status quo is no good:

It's kind of the worst of all worlds in that we expect /by/ as the format but basically silently fail if you don’t use it.
Current users are not being consistent and we don't have a good way to teach them to be.

Update: I didn't do it exhaustively but have sampled a bunch of promise URLs and could find none where laissez faire parsing would do worse than the status quo.


Create new test framework for atests

MVP of the new test framework for acceptance tests. I will update it in next PRs but this PR fully works.
The idea is to move from our automated framework (where tests are generated dynamically) to more DAMP design style tests.
Tests in the new design can be defined in following way:
from tests.atest.utils import RuleAcceptance

class TestRuleAcceptance(RuleAcceptance):
    def test_rule(self, capsys):
        self.check_rule(capsys, src_files=["test.robot"], expected_file="expected_output.txt")

(the capsys part will be removed in next PRs). Thanks to defining test method for each rule it's a lot easier to manage them, and run separetly.
Also custom tests are now moved from yaml file to the same class:
from tests.atest.utils import RuleAcceptance

class TestRule(RuleAcceptance):
    def test_rule(self, capsys):
        self.check_rule(capsys, src_files=["test.robot"], expected_file="expected_output.txt")

    def test_ignore_docs(self, capsys):
        self.check_rule(
            capsys,
            config="-c too-long-keyword:ignore_docs:True",
            src_files=["ignore_docs.robot"],
            expected_file="expected_output_ignore_docs.txt",
        )

    def test_severity_threshold(self, capsys):
        self.check_rule(
            capsys,
            config="-c too-long-keyword:severity_threshold:warning=40:error=50",
            src_files=["severity_threshold.robot"],
            expected_file="expected_output_severity_threshold.txt",
        )

In the scope of this PR I migrated tests for two rules - not all since it's still work in the progress and I didn't want to do monstrous code change in one go.

Another benefit is that it's now possible to run integrated tests, ie if you want to ensure that your rule X does not report at the same issue as rule Y:
    def test_integration(self, capsys):
        self.check_rule(capsys, expected_file="integration.txt", rule=["empty-arguments", "parsing-error"])

Codecov Report
Base: 97.23% // Head: 97.23% // No change to project coverage :thumbsup:

Coverage data is based on head (9f691af) compared to base (bf2747a).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #711   +/-   ##
=======================================
  Coverage   97.23%   97.23%
=======================================
  Files          24       24
  Lines        3007     3007
=======================================
  Hits         2924     2924
  Misses         83       83

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

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


.NET 5.0 Runtime can no longer be downloaded.

Describe the bug
I cannot run the application due to .NET 5.0 no longer being downloadable.
Expected behavior
When I try to launch MafiaToolkit.exe, a popup will appear "To run this application, you must Install .NET. Would you like to install it?"
I pressed yes and I'm greeted with this screen (Shown down below in Screenshots)
Screenshots

Desktop (please complete the following information):

OS: [ Windows 10 Home]
Browser [ Microsoft Edge ]
Version [ I don't quite understand this, 10 Home?  ]

Additional context
I wanted to extract the Policeman sounds for something, but I cannot access the toolkit since NET 5.0 is retired.

Link is here https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-5.0.17-windows-x86-installer
That message box is Microsoft's doing, it appears to be misleading

@szymonuwu I only had to install the latter on Windows 11 x86_64/amd64. @Greavesy1899 Would be nice to have these download links in a required dependencies section in the README.

Link is here https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-5.0.17-windows-x86-installer
That message box is Microsoft's doing, it appears to be misleading

Ah, not sure why Microsoft mislead me.


2fa with Authorization server

Hi Magnus,
Great book firstly.
Is there a sample code that we can rely on for 2fa on the authorization server.
Regards

Hello!
No, not that I'm aware of.
But you can checkout the Spring Auth Server project.
Here is for example a discussion on the subject: https://github.com/spring-projects/spring-authorization-server/issues/534


Figure and Caption Misalignment

As for the paper (id: 1808.02342), the figures and the captions are not correctly aligned.
The order of the figures is not wrong, however, still there are the following problems:

the captions of figures are not correct (it looks like the caption for Fig 2 is skipped; thus, for Fig n(>1), caption for Fig (n-1) is corresponding to)
Fig 15 is completely vanished from where it should be

This was a problem for the dataset and nothing to do with MioGatto itself. The problem is resolved anyway.


Update RequestInterceptorInjectionHandler.java

Added conditional check for content-length.
Changed scope when assigning next to avoid buffer conflict.

@KalevGonvick Thanks a lot for your help.


QuickStart.exe is not built and cannot be found.

At Build and Run - Google Cloud Speech API Samples.
I was able to proceed up to step four, but there is no QuickStart.exe to find after that.
What am I doing wrong?

You're looking in the vs2015 branch (last updated in 2017) - are you trying to use VS2015, or are you on a more modern version of Visual Studio? The documentation in the master branch shows using dotnet run to run the sample.

I'm using Visual Studio 2019 on my PC. I'm using Visual Studio for Mac on my Mac mini also. I'm trying whatever I can get to work.

Right. In that case you definitely don't want to be using the old vs2015 branch. You will need the .NET Core SDK installed though.
If you just run dotnet run from the QuickStart directory, it should work fine. (Even the dotnet restore step is unnecessary with recent versions of the .NET Core SDK.)

Closing as I believe just using the recent branch should be fine.


CupertinoDialogAction does not change color on press

CupertinoDialogAction does not change color when the user taps on it in a dialog.  A standard iOS dialog button gets darker when tapped.

related/dup: https://github.com/flutter/flutter/issues/14886

This issue was resolved with the CupertinoAlertDialog work that was merged.  There are still color issues with CupertinoAlertDialog related to the dividers and popup surface background color, but this particular issue is handled.


Question - How does this differ from manually settings kb/m bindings in-emulator?

I am genuinely curious what the difference is between using this program and manually setting in-emulator k/m bindings?

The emulator will map your mouse input to a virtual joystick, which is then interpreted by the game. This gives a nauseating experience.
KAMI instead calculates new angles for the active game camera and injects them into game memory. This gives a native mouse movement implementation feel.


Further improvements in Ace integration

The problem:

The Ace editor is trying to syntax check Saving changes... and Fetching changes... and it will show a big red [X] as a result. Which is confusing - "Was was that?" "Did it save?" "There was this.. thing like..a.. nevermind".
The problem has been introduced by yours truly in the initial Ace-kudu integration.
Proposed fix:
How about a status bar in the new Ace editor?
Cloudy glyphs for file save and file load

Status bar shows filename by default:

Clicking it switches to full path:

I'm totally open to new ideas on what we could do with this new status bar.
If it looks good i will go ahead with development and pull request.

I like it. Not sure it's worth doing the clickable thing to show full path. And if we don't then maybe it doesn't have to look like a clickable button (which it isn't anyway for fetching/saving). Not sure what the bootstrap convention is for status text that's clearly non-clickable.

Agreed.
The closest thing to a status bar styling in Bootstrap is the bs-callout class. Which isn't even part of Bootstrap, but can be added rather easily: http://cpratt.co/twitter-bootstrap-callout-css-styles/
bs-callout-info (no background):

bs-callout-info with gray background:

bs-callout-primary (no background):

bs-callout-primary with gray background:

bs-callout-so-minimal-much-wow:

bs-callout-so-minimal-much-wow-on-gray:

Any other attempt to style this bar by filling it with a solid color results in a unstoppable urge to click it. Which should not be the case. I also think it looks nicer in the same font as Save/Cancel and not monospaced.

I guess any of those would probably work, so pick your favorite one :)

Merged in https://github.com/projectkudu/kudu/pull/1635


Fix Webhook Issues

These fixes address the recent warning email sent by Stripe related to the high error rate we're having on our API.

Merging this as a hot-fix because Stripe imposed a deadline to fix this.


Bug in words count and minutes Read.

No increase in words count and minutes read.

Hi @Mitushi-23,
I'll like to work on this.

ok I am assigning to both.

@RuthChisom @bhattabhi013 this issue is resolved, so you can try to work on other issue.


[Feature] Hex-Float Support

it would be nice if the protocol would allow to send numbers encoded as hex-floats. All needed would be to change this line:
https://github.com/graphite-project/carbon/blob/9fad18df5731271aab6f5c81d32eddcecdc1a695/lib/carbon/protocols.py#L197
To this:
      datapoint = (
         float.fromhex(timestamp) if timestamp.startswith('0x') else float(timestamp),
         float.fromhex(value) if value.startswith('0x') else float(value)
      )

A metric line in the plain text protocol would then be e.g.:
math.pi 0x1.921fb54442d18p+1<PHONE_NUMBER>

Why? Because hex-floats enable exact transfer of floating-point numbers. Decimal doesn't exactly map to the in memory representation of IEEE doubles. But yeah, good float formatters/parsers add enough places to get the exact value across, and it isn't really a problem in practice. Just a nice to have, I think.

Hi @panzi
Yes, could be useful, for some applications, theoretically - but not sure if it's quite needed in practice. But thanks for suggestion!


Add Mergify integration to automatically merge PRs on approval

Does this not wait for the next reviewers after one has approved? I am just thinking what happens when you want more than one reviewers' approval.

@sahil-lakhwani you need to add hold-off-merging label to hold off merging

@sahil-lakhwani we can also add a condition if a particular label is added only then merge the PR. Let me do that


spaCy-like API

spaCy-pipeline:

Set Tokenizer
Set Processors (e.g. classification, NER, etc)

Automatic Batching
Document will use a "by" implementation that adds the typed data

Requirements:

[ ] Add Interfaces for Pipeline Plugins
[ ] Add Transformer Clf+NER
[ ] Add Simple NER
[ ] Add PoS (Part of Speech)
[ ] Dependency Parser
[ ] Add Different Default modes (small, medium, large)

// https://spacy.io/usage/processing-pipelines

First model to test, https://huggingface.co/textattack/albert-base-v2-imdb
Include a transform script for people to use.

https://stanfordnlp.github.io/CoreNLP/pos.html


Weird crash with servers.

Everytime I try to join my Bisect Hosting server, it crashes because the XP Storage Additions is failing to gather all the stripped logs from the Ecologics mod for the Staff Of Rebark, at least I think so, I have been trying to fix this for days. Any help would be appreciated.

Sad to hear that.
Can you provide the log file?
This bug should be already fixed with the latest version.


Add remi-php73

I've simply added the necessary changes to enable PHP 7.3 using remi repository

Thanks @MiLk! Changes applied. 👍

Published on galaxy as v1.3.2


Team dashboards

Fixes #13980
This adds the option to filter the organization "Activities" (heatmap, feed, repos), "Issues", "Pull Requests" and "Milestones" views by team.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@fe40372). Click here to learn what that means.
The diff coverage is 41.53%.

@@            Coverage Diff            @@
##             master   #14159   +/-   ##
=========================================
  Coverage          ?   42.03%
=========================================
  Files             ?      733
  Lines             ?    78697
  Branches          ?        0
=========================================
  Hits              ?    33080
  Misses            ?    40184
  Partials          ?     5433

Impacted Files
Coverage Δ

models/action.go
50.93% <0.00%> (ø)

models/repo_list.go
78.76% <0.00%> (ø)

routers/user/home.go
60.27% <32.25%> (ø)

models/org.go
72.51% <43.75%> (ø)

models/user_heatmap.go
81.57% <100.00%> (ø)

routers/api/v1/repo/repo.go
61.89% <100.00%> (ø)

routers/routes/macaron.go
93.17% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fe40372...d12ba02. Read the comment docs.


Revamp Your Website: Stylish Navbar Menu for Contributing to an Open-Source Project for a Sleek and Modern Design

Before Changes

After Changes

Hi @ANSHIKA-26
I recently updated the navbar menu for your project to make it more attractive and user-friendly. Enhance readability, improve navigation, and give your site a visually appealing touch that stands out with these simple yet impactful design updates. I've attached screenshots of the changes, and I'd love to contribute to this enhancement to improve the overall design.
Please assign me to this task. It would be a great opportunity to contribute while enhancing my skills.
I'm looking forward to hearing back from you!
Best regards,
@khurshed07
https://github.com/khurshed07

PR https://github.com/ANSHIKA-26/WordWise/pull/1210 is for same


High Severity: Prototype Pollution in vulnerable module<EMAIL_ADDRESS>

shvl version: 2.0.1
node version: 12.6.1
npm (or yarn) version: 6.13.4

Problem description:
Snyk reported recently about High Severity: Prototype Pollution in vulnerable module<EMAIL_ADDRESS>. The vuex-persistedstate project depends on shvl and therefore became listed as vulnerable primary dependency in our production project.
https://snyk.io/test/npm/shvl/2.0.1
Could you have a look and provide fix please?

I probably can, but what should be the fix?

I probably can, but what should be the fix?


Update to create 0.5.1-f-build.1417+mc1.20.1?

Describe the your request
Create Fabric 0.5.1-f-build.1417+mc1.20.1 has released for 6 months, could this mod have an update to support that latest version?

already works with it


Bug in numbering during retries encountered

For some reason this strange output can occur:
[       OK ] (231/279) FlexAlltoallTest on arolla:pn using PrgEnv-gnu [compile: 0.559s run: 21.334s total: 2072.256s]
[       OK ] (232/279) HaloCellExchangeTest on arolla:cn using PrgEnv-pgi [compile: 0.627s run: 21.459s total: 2083.825s]
[       OK ] (233/279) FlexAlltoallTest on arolla:pn using PrgEnv-pgi [compile: 0.777s run: 21.169s total: 2094.441s]
[       OK ] (234/279) HaloCellExchangeTest on arolla:cn using PrgEnv-gnu [compile: 0.435s run: 21.199s total: 2105.736s]
[       OK ] (235/279) DGEMMTest on arolla:pn using PrgEnv-gnu-nompi [compile: 0.451s run: 22.423s total: 2120.285s]
[       OK ] (236/279) KernelLatencyTest_sync on arolla:cn using PrgEnv-pgi [compile: 1.689s run: 15.531s total: 2125.056s]
[       OK ] (237/279) DGEMMTest on arolla:cn using PrgEnv-gnu-nompi [compile: 0.378s run: 10.441s total: 2136.125s]
[       OK ] (238/279) AllocSpeedTest_no on arolla:cn using PrgEnv-gnu [compile: 0.631s run: 10.444s total: 2147.662s]
[       OK ] (239/279) OpenaccCudaCpp on arolla:cn using PrgEnv-pgi [compile: 3.897s run: 5.305s total: 2157.925s]
[       OK ] (240/279) MultiDeviceOpenaccTest on arolla:cn using PrgEnv-pgi [compile: 1.740s run: 5.326s total: 2165.140s]
[       OK ] (241/279) GpuDirectCudaCheck on arolla:cn using PrgEnv-pgi [compile: 2.503s run: 5.313s total: 2173.099s]
[       OK ] (242/279) GpuDirectCudaCheck on arolla:cn using PrgEnv-gnu [compile: 1.761s run: 5.357s total: 2180.361s]
[       OK ] (243/279) GpuDirectAccCheck on arolla:cn using PrgEnv-pgi [compile: 0.542s run: 5.315s total: 2186.365s]
[       OK ] (244/279) CudaStressTest on arolla:cn using PrgEnv-pgi-nompi [compile: 1.473s run: 5.312s total: 2193.307s]
[       OK ] (245/279) CudaStressTest on arolla:cn using PrgEnv-gnu-nompi [compile: 1.604s run: 5.387s total: 2202.242s]
[       OK ] (246/279) CudaStressTest on arolla:cn using PrgEnv-gnu [compile: 1.621s run: 5.399s total: 2209.414s]
[     FAIL ] (247/279) HaloExchangeTest_nocomp on arolla:cn using PrgEnv-gnu [compile: 15.930s run: 5.384s total: 2230.874s]
[     FAIL ] (248/279) HaloExchangeTest_nocomm on arolla:cn using PrgEnv-gnu [compile: 13.805s run: 5.345s total: 2250.166s]
[     FAIL ] (249/279) HaloExchangeTest_default on arolla:cn using PrgEnv-gnu [compile: 13.870s run: 5.343s total: 2269.519s]
[     FAIL ] (250/279) AlltoallvTest_nocomp on arolla:cn using PrgEnv-gnu [compile: 14.785s run: 5.350s total: 2289.798s]
[     FAIL ] (251/279) AlltoallvTest_nocomm on arolla:cn using PrgEnv-gnu [compile: 14.555s run: 5.351s total: 2309.903s]
[     FAIL ] (252/279) AlltoallvTest_default on arolla:cn using PrgEnv-gnu [compile: 14.781s run: 5.345s total: 2330.184s]
[     FAIL ] (253/279) AutomaticArraysCheck on arolla:cn using PrgEnv-pgi-nompi [compile: 0.337s run: n/a total: 2330.644s]
[     FAIL ] (254/279) AutomaticArraysCheck on arolla:cn using PrgEnv-gnu [compile: 0.000s run: n/a total: 2333.403s]
[----------] all spawned checks have finished

[==========] Retrying 7 failed check(s) (retry 1/2)
[----------] started processing AutomaticArraysCheck (AutomaticArraysCheck)
[ RUN      ] AutomaticArraysCheck on arolla:cn using PrgEnv-gnu
[     FAIL ] (1/9) AutomaticArraysCheck on arolla:cn using PrgEnv-gnu [compile: 0.000s run: n/a total: 0.018s]
[ RUN      ] AutomaticArraysCheck on arolla:cn using PrgEnv-gnu-nompi
[     FAIL ] (2/9) AutomaticArraysCheck on arolla:cn using PrgEnv-gnu-nompi [compile: 0.000s run: n/a total: 0.015s]
[ RUN      ] AutomaticArraysCheck on arolla:cn using PrgEnv-pgi-nompi
[     FAIL ] (3/9) AutomaticArraysCheck on arolla:cn using PrgEnv-pgi-nompi [compile: 0.338s run: n/a total: 0.355s]
[----------] finished processing AutomaticArraysCheck (AutomaticArraysCheck)

[----------] started processing AlltoallvTest_default (AlltoallvTest_default)
[ RUN      ] AlltoallvTest_default on arolla:cn using PrgEnv-gnu
[----------] finished processing AlltoallvTest_default (AlltoallvTest_default)

[----------] started processing AlltoallvTest_nocomm (AlltoallvTest_nocomm)
[ RUN      ] AlltoallvTest_nocomm on arolla:cn using PrgEnv-gnu
[     HOLD ] AlltoallvTest_nocomm on arolla:cn using PrgEnv-gnu
[----------] finished processing AlltoallvTest_nocomm (AlltoallvTest_nocomm)

[----------] started processing AlltoallvTest_nocomp (AlltoallvTest_nocomp)
[ RUN      ] AlltoallvTest_nocomp on arolla:cn using PrgEnv-gnu
[     HOLD ] AlltoallvTest_nocomp on arolla:cn using PrgEnv-gnu
[----------] finished processing AlltoallvTest_nocomp (AlltoallvTest_nocomp)

[----------] started processing HaloExchangeTest_default (HaloExchangeTest_default)
[ RUN      ] HaloExchangeTest_default on arolla:cn using PrgEnv-gnu
[     HOLD ] HaloExchangeTest_default on arolla:cn using PrgEnv-gnu
[----------] finished processing HaloExchangeTest_default (HaloExchangeTest_default)

[----------] started processing HaloExchangeTest_nocomm (HaloExchangeTest_nocomm)
[ RUN      ] HaloExchangeTest_nocomm on arolla:cn using PrgEnv-gnu
[     HOLD ] HaloExchangeTest_nocomm on arolla:cn using PrgEnv-gnu
[----------] finished processing HaloExchangeTest_nocomm (HaloExchangeTest_nocomm)

[----------] started processing HaloExchangeTest_nocomp (HaloExchangeTest_nocomp)
[ RUN      ] HaloExchangeTest_nocomp on arolla:cn using PrgEnv-gnu
[     HOLD ] HaloExchangeTest_nocomp on arolla:cn using PrgEnv-gnu
[----------] finished processing HaloExchangeTest_nocomp (HaloExchangeTest_nocomp)

[----------] waiting for spawned checks to finish
[     FAIL ] (4/9) AlltoallvTest_default on arolla:cn using PrgEnv-gnu [compile: 14.916s run: 3.517s total: 18.465s]
[     FAIL ] (5/9) HaloExchangeTest_nocomp on arolla:cn using PrgEnv-gnu [compile: 13.807s run: 3.376s total: 20.070s]
[     FAIL ] (6/9) HaloExchangeTest_nocomm on arolla:cn using PrgEnv-gnu [compile: 13.856s run: 5.858s total: 39.930s]
[     FAIL ] (7/9) HaloExchangeTest_default on arolla:cn using PrgEnv-gnu [compile: 14.041s run: 4.898s total: 59.020s]
[     FAIL ] (8/9) AlltoallvTest_nocomp on arolla:cn using PrgEnv-gnu [compile: 14.736s run: 5.293s total: 79.192s]
[     FAIL ] (9/9) AlltoallvTest_nocomm on arolla:cn using PrgEnv-gnu [compile: 14.641s run: 5.331s total: 99.302s]
[       OK ] (10/9) NetCDFTest_f90_static on arolla:cn using PrgEnv-pgi-nompi [compile: 1.586s run: 5.413s total: 2455.413s]
[       OK ] (11/9) NetCDFTest_f90_static on arolla:cn using PrgEnv-gnu-nompi [compile: 0.841s run: 5.514s total: 2461.916s]
[       OK ] (12/9) NetCDFTest_f90_dynamic on arolla:cn using PrgEnv-pgi-nompi [compile: 0.727s run: 5.461s total: 2468.249s]
[       OK ] (13/9) NetCDFTest_f90_dynamic on arolla:cn using PrgEnv-gnu-nompi [compile: 0.586s run: 5.495s total: 2474.479s]
[       OK ] (14/9) NetCDFTest_c_static on arolla:cn using PrgEnv-pgi-nompi [compile: 0.669s run: 5.464s total: 2480.763s]
[       OK ] (15/9) NetCDFTest_c_static on arolla:cn using PrgEnv-gnu-nompi [compile: 0.621s run: 5.471s total: 2486.995s]
[       OK ] (16/9) NetCDFTest_c_dynamic on arolla:cn using PrgEnv-pgi-nompi [compile: 0.629s run: 5.462s total: 2493.234s]
[       OK ] (17/9) NetCDFTest_c_dynamic on arolla:cn using PrgEnv-gnu-nompi [compile: 0.579s run: 5.496s total: 2499.461s]
[       OK ] (18/9) NetCDFTest_cpp_static on arolla:cn using PrgEnv-pgi-nompi [compile: 1.403s run: 5.542s total: 2506.552s]
[       OK ] (19/9) NetCDFTest_cpp_static on arolla:cn using PrgEnv-gnu-nompi [compile: 1.092s run: 5.543s total: 2513.355s]
[       OK ] (20/9) NetCDFTest_cpp_dynamic on arolla:cn using PrgEnv-pgi-nompi [compile: 1.292s run: 5.560s total: 2520.358s]
[       OK ] (21/9) NetCDFTest_cpp_dynamic on arolla:cn using PrgEnv-gnu-nompi [compile: 0.926s run: 5.562s total: 2526.992s]
[       OK ] (22/9) GpuBandwidthCheck on arolla:cn using PrgEnv-gnu-nompi [compile: 2.199s run: 92.328s total: 2621.801s]
[       OK ] (23/9) CudaSimpleMPICheck on arolla:cn using PrgEnv-gnu [compile: 2.000s run: 5.400s total: 2629.342s]
[       OK ] (24/9) CudaConcurrentKernelsCheck on arolla:cn using PrgEnv-pgi-nompi [compile: 1.732s run: 5.306s total: 2636.522s]
[       OK ] (25/9) CudaConcurrentKernelsCheck on arolla:cn using PrgEnv-pgi [compile: 1.715s run: 5.302s total: 2643.677s]
[       OK ] (26/9) CudaConcurrentKernelsCheck on arolla:cn using PrgEnv-gnu-nompi [compile: 1.865s run: 5.389s total: 2651.071s]
[       OK ] (27/9) CudaConcurrentKernelsCheck on arolla:cn using PrgEnv-gnu [compile: 1.862s run: 5.385s total: 2658.462s]
[       OK ] (28/9) CudaDeviceQueryCheck on arolla:cn using PrgEnv-pgi-nompi [compile: 1.680s run: 5.309s total: 2665.592s]
[       OK ] (29/9) CudaDeviceQueryCheck on arolla:cn using PrgEnv-pgi [compile: 1.660s run: 5.309s total: 2672.714s]
[       OK ] (30/9) CudaDeviceQueryCheck on arolla:cn using PrgEnv-gnu-nompi [compile: 1.841s run: 5.391s total: 2680.085s]
[       OK ] (31/9) CudaDeviceQueryCheck on arolla:cn using PrgEnv-gnu [compile: 1.798s run: 5.388s total: 2687.407s]
[       OK ] (32/9) CudaMatrixmulCublasCheck on arolla:cn using PrgEnv-pgi-nompi [compile: 1.799s run: 5.308s total: 2694.655s]
[       OK ] (33/9) CudaMatrixmulCublasCheck on arolla:cn using PrgEnv-pgi [compile: 1.841s run: 5.300s total: 2701.934s]
[       OK ] (34/9) CudaMatrixmulCublasCheck on arolla:cn using PrgEnv-gnu-nompi [compile: 1.933s run: 5.437s total: 2709.481s]
[----------] all spawned checks have finished

It seems that the first run ended prematurely and the 34 remaining cases were considered for the next retry. I don't know the root cause of this, but it's certainly a bug.
More details here: https://jenkins.cscs.ch/blue/organizations/jenkins/reframe-arolla-validation/detail/reframe-arolla-validation/4/pipeline/

@vkarak Have you seen this happen more recently? Maybe it would help to have a look at the stage/output directories and the reframe.log.
There are two ways I see this bug happening. In the exit method of the policy we check only for running and waiting tasks. The 34 remaining cases might have been either on the _completed_tasks list or the _ready_tasks dictionary. If they were in the _completed_tasks then they run on the first try but were finalized on the second. I think we can fix the bug by adding a more strict check in the while loop but I haven't found yet how to reproduce the error.

@ekouts I haven't seen that happening anywhere else. You could potentially construct a series of test to trigger this artificially.

The 34 remaining cases might have been either on the _completed_tasks list or the _ready_tasks dictionary. If they were in the _completed_tasks then they run on the first try but were finalized on the second.

If this is happening, it's because we don't clean up the lists after we finish, right? Shouldn't we clean them or assert that they are indeed empty?

In this particular case where this happened, max_job was set to 1, so it is quite likely that the _running_tasks and _waiting_tasks were empty.

Prior to #1022 we were also checking for the "retired tasks," which is equivalent to the current "completed tasks." So it's certainly something wrong there. I don't if there is any easy way to reproduce, but we could certainly improve the check there.

If this is happening, it's because we don't clean up the lists after we finish, right? Shouldn't we clean them or assert that they are indeed empty?

I agree with you, I think we should assert that _completed_tasks and _ready_tasks are empty, although I didn't find how they won't be cleaned. The _retired_tasks could be non empty because of failing dependencies and they might be cleaned up in a later retry or not at all.

Reopening since we found a fix in #1673.

Reopening since we found a fix in #1673.


Tokio 0.2 integration

As soon as tokio = "0.2" will be released (see v0.2 milestone), it would be nice to integrate it into a heim-runtime crate, so there would be at least one fully async runtime shim in heim.

Partial (in a "seems to be working" state) implementation is in runtime-tokio branch

Closed by 1c3f514545baad2ca3019f69e64261fc187923dc


build: cleanup duplication

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 59.684%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
302

Relevant Lines:
506

💛  - Coveralls

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


moduo length round off error?

Reported by Steven C Hankin on 30 Jan 2008 19:18 UTC
Is this a problem in Ferret?  Or in the data file?
What is the best solution?
yes? use
"http://dods.jpl.nasa.gov/opendap/GHRSST/data/L4/GLOB/UKMO/OSTIA/2008/029/20080129-UKMO-L4HRfnd-GLOB-v01-fv02-OSTIA.nc.bz2"
*** NOTE: Ignored modulo length exceeding axis length: lon
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1559

Comment by<EMAIL_ADDRESS>on 30 Jan 2008 22:34 UTC
This is a Ferret precision problem. The axis is regularly-spaced, with no
specific modulo attribute given. The coordinates in the file are
single-precision float.
float lon(lon) ;
	lon:long_name = "longitude" ;
	lon:standard_name = "longitude" ;
	lon:axis = "X" ;
	lon:units = "degrees_east" ;

...
lon = -179.975, -179.925, ..., 179.925, 179.975 ;
Ferret correctly detects this as a regularly-spaced axis. It then computes the
axis length, to be compared with 360 degrees. This is in a call to TM_WW_AXLIMS
which has this for a regular axis.
  lo = line_start(axis) - 0.5*line_delta(axis)
  hi = lo + line_dim(axis)*line_delta(axis)

line_start(), line_delta() and lo and hi are all double precision. The
computation of lo and hi results in this
lo = -180.0000061
hi =<PHONE_NUMBER>
and so the length is computed as slightly more than 360.  (Making the 0.5 in the
expression for lo= above does not affect this; it's the conversion from float to
double that has added the extra stuff in the low-order bits.)
Possible fix: check the attributes of the axis, and see whether the coordinates
are single precision. If so, after computing the axis length, do the check for >
360 in single precision.

Comment by<EMAIL_ADDRESS>on 31 Jan 2008 15:16 UTC
The spirit of this fix is right on:  if the coordinates are only provided in the
file at single precision, then the tests for exactness of fit on modulo length,
constancy of delta, etc. must all be restricted to single precision.  In fact,
when these coordinates are written back out to a file, they should ideally be
written as single precision -- saving space and retaining better the character
of the input data.
Here is a suggested list for implementing a fix -- (1-3, only, as short term tasks):

add a new attribute for all coordinate axes  axis: dataType = 'float' (or
'double' or other)  This attribute should be set based upon the data type of the
coordinate axis on input files.  It should default to 'double' on all axes
created by DEFINE AXIS.
The attribute can be viewed and altered by the user through the normal
means of working with attributes.
The attribute will be used to determine the appropriate tests of precision
-- modulo length, constant delta, etc.
(Note: this item should be postponed for a separate Bugzilla ticket.) The
attribute will control the data type used in output files.  (Postpone for
another Bugzilla entry because it is a big-ish job -- e.g. think about appending
into an existing file or about "long" as a data type in conjunction with scale
and offset attributes.)


Fix/git

This should resolve https://github.com/krzysztof-miemiec/lemmy/issues/14 issue with error occurring when trying to get another branch having uncommitted changes

Version
:tada: Package version has been updated properly.
Changelog
:tada: Changelog has been updated properly.
Lint
:tada: No lint warnings were reported!

Summary
Value

:octocat: Commit
6b78d89aea0dd002a0c5e566eae92f548782c2bc

Comparing against
master branch

Build number
52

Job number
52.1

System
linux


Allow specifying reporters with nyc directly

To get a report I currently run
nyc node test/index.js && nyc report --reporter text --reporter html

It would be great to just run
nyc node test/inedx.js --reporter text --reporter html

Also note I'm relying on the "--reporter" can appear multiple times feature which may be accidental :)

@Raynos I love this idea. I will start looking into adding the option this week; it's not trivial because I need to be able to handle commands like:
nyc ./node_modules/.bin/mocha --check-globals, so I'll need to add some logic to intelligently munge process.argv.

@bcoe
The way istanbul does this is nyc --reporter text --reporter html -- node test/index.js
It can also be handled like node where flags after nyc and before the binary belong to nyc and all other flags belong to the binary.

@Raynos, I've got a testing branch that adds this support. I use yargs to parse process.argv and then I use the information I extract to slice the original arguments:
NYC.prototype.mungeArgs = function (yargv) {
  return process.argv.slice(
    process.argv.indexOf(yargv._[0])
  )
}

Works great, but I'm waiting to land this pull, or something similar on one of the dependent libraries:
https://github.com/isaacs/foreground-child/pull/3
CC: @isaacs this was the feature request I was talking about, I think it's pretty cool.

Nice work :) I'll try it out once it's ready. Thanks @bcoe appreciate it.


Fix toolchain

Always use the go binary from the local toolchain, ensure GOROOT is correct everywhere. Also adds the locally built flynn and flynn-host to the PATH.

Closing until I've sorted out some toolchain issues.


chore(main): release 1.0.8

:robot: I have created a release beep boop
1.0.8 (2023-06-19)
Bug Fixes

minor chart fix (#31) (f538110)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Rookout/piper/releases/tag/v1.0.8 :sunflower:


Is there any way to support class auto import ?

If a preset has somthing like 'export class Test{}',how to auto import it?

Nothing prevents you from doing that. Just like how you config other imports.


updates to imaging schema based on conversations with adam

Ongoing WIP on imaging schemas

@camilolaiton @adamkglaser
I made an array for the axes that combines a variety of other features - eg. Camilo had asked for reference and voxel size and these are now the dimension and voxel size within this array. Can you both take a look at this and let me know if this will work for your purposes?


Include Ignored Checks in Azure DevOps Pipeline Test Results When Using the --include-ignored Command

Is your feature request related to a problem? Please describe.
When running TFSec in an Azure DevOps pipeline, and using the --include-passed command (along with the appropriate output format), the passed tests are also visible in the pipeline test results. However, when using the --include-ignored command, those tests are not included in the pipeline test results.
Describe the solution you'd like
It would be nice to have the 'ignored' checks appear in the "Others" category for Azure pipeline test results. That way, we can easily review if an ignored check should be re-included.
Describe alternatives you've considered
No alternatives were explored.
Additional context
Add any other context or screenshots about the feature request here.

Hey @AErmie - can you clarify what you mean by the pipeline test results? Is that something specific to Azure Pipelines, I'm guessing so as you mention "Others" category
If I run with --format json --include-ignored then the ignore results are included in the json.

Hey @owenrumney, yes I'm referring to the Azure Pipeline test results.
What I meant was... when you include the --include-passed command, the JUnit XML file that's produced (and published to Azure Pipelines via the Publish Test Results task), will rightfully show the passed and failed tests.

What I would also like to include in the output (using the --include-ignored command), is all ignored/suppressed checks, but categorize them as "other" (in reference to Azure Pipeline test results).
That way it allows us to also track if the number of suppressed checks changes as well.

If I understand the docs correctly, you can only do failure, skipped, error or anything else and anything else equates to passed. So I'm not clear that this would be achievable without artificially setting the outcome to skipped.
Outcome | Failed: if exists /Testsuites/testsuite/testcase/failure Or /Testsuites/testsuite/testcase/error
                 Not Executed: if exists Testsuites/testsuite/testcase/skipped
                 Passed: for all other cases

Or does it use a different element of the XML to do this?

Hey @owenrumney, I tried to do some digging around, and the only thing I could find is this article About pipeline tests. I'm not sure if it's linked to one of the 15 outcome types (maybe None, Not applicable, Not executed, or Not impacted).

It would be good to talk about this in discussions if still required, then we can reopen an issue once we have a concrete idea of what this would look like.


Can't change back from sentence case

Within first minute after installing your awesome plugin I discovered a small bug. I was editing a python script and started playing around with method names switching case styles from snake to camel to sentence. After my method's name became a sentence i.e. had a space between each word I couldn't change it back to other cases using your plugin. I was highlighting it, went to command pallet and tried various cases but nothing worked, it didn't respond at all making me think Atom window was not in focus.

@AlexanderMer Can this still be reproduced with the latest version?

The bug can't be reproduced as far as I can see. I tried switching from case to case and it worked flawlessly.


[WIP] - create a base theme for Text component

As we will want to create new themes and most of the themes will have commonalities, there is a need to create a base theme that will keep the variables and styles interfaces/ base implementation.
Starting with Text component - the Default theme is nicely following the base implementation while there are no visible changes in the other existing themes.

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS

Totally agree with @miroslavstastny points. If something is in the API then it should be handled in the base theme (by providing variables for it, and basic styles). Other themes can extend or change the variables describing some prop and can add additional styling forthem. If we have the important property for example, the base theme can for example make it just bold, and the teams theme can add additional variable for the color etc. The Text is pretty simple component, so not sure how many variables will be added in the teams theme, but if we take a look into the Chat for example, we will have base theme that can create some black-gray-white chat, and teams theme can change the variables to use the specific colors and maybe add additional ones for customizing the styles further.
Agreed that the atMention and timestamp props maybe should be removed from the API, but that is not the scope of this PR for sure...


Fix/add row invalid response handling

I observed that sometimes Google Sheets API returns an unexpected response such as "302: Moved Temporarily". Retrying often succeeds though. Even though I don't know the root cause of this issue, I have added some error handling here. I was able to retry after a failure without a crash. Thanks!

I've just a published a new version of this module which is a complete rewrite using Google's V4 Sheets API (v3 is being deprecated on March 3, 2020).
Docs available here - https://theoephraim.github.io/node-google-spreadsheet
I do believe this issue should be fixed in the new version.
Please test it out and if you find that there is still a problem, reopen the issue.
Thanks! 😄


Wiz Connection Issue Very similar to Issue #916

Originally (yesterday), I posted the following into Issue #916 . After successfully posting, I then realized that 916 was closed. duh...
Through the magic of copy/paste, I created this bug report and have pasted my information below.
I have the same issue, so I uninstalled the app, rebooted and reinstalled. But the issue persists. When I select Wiz light, the app eventually locks up.
It is worth mentioning, I am not a developer.  I'm vaguely familiar with YAML and attempting to provide you with some relevant information.
As to the Wiz light I am working with, here's the Amazon link for what I purchased.
https://www.amazon.com/dp/B09G6TJVVC?ref=ppx_pop_mob_ap_share
OS - Win 11
AppPackage 5.8.9
Downloaded fromMicrosoft Store
All following logs/screenshots were generated AFTER:

uninstalling the app
rebooting
reinstalling the app

Here's a portion of my log. Is the log referencing "D" drive? If it is, I don't have a "D" drive, only "C".
"Properties":{"SourceContext":"PresenceLight.MainWindow","LineNumber":180,"FilePath":"D:\a\presencelight\presencelight\src\DesktopClient\PresenceLight
Screenshots follow

Live logs, prior to selecting Wiz light

Next screenshot, I select Wiz light, eventually the app locks up, as it never ack the existence of my Wiz light, which is on my /24 network.

The next screenshot of logs, this is after I have killed the task (via Task manager), then launched the task.

Thank you for developing and sharing this app!
I look forward to getting it functional. I certainly do not mind purchasing a different smart bulb, if you can recommend a brand & model that might resolve my issues.
Happy Holidays!

I am still having the issue I first posted about with issue #916. As others were able to get it working I was diving into 365 permissions and such on my  email to see if something there was blocking it. Nothing was blocking it. I would like to see what is found here and if needed I can provide further logs if needed.
Thanks, Happy Holidays


[UWP] Click of Button with Flyout crashes when built with NativeToolchain AND app project references an unused library project that contains a XAML page

Describe the bug
If you have a UWP application with the following conditions:

Contains a Button with a MenuFlyout as its Flyout
Compiled with Native Toolchain
References another project that contains a XAMLPage

... the app will crash when the Button is pressed.

Some notes:

Many attempts have made to address this via editing the app's Default.rd.xml file.  If there is something that could be added that actually address this crash, I would be very grateful as, for the project I am working on, there is no workaround for the consequences of this bug.
The app won't crash if the project with the XAMLPage is not referenced
The app won't crash if the Page class is all code (no XAML)

Steps to reproduce the bug
TO REPLICATE

Get demo project: https://github.com/baskren/UWP_UnusedXamlPageInUnusedLibraryCrash
Do either a Release build or a Debug build with Native Toolchain enabled
Click on the Button labeled XAML

Expected behavior
Use of Libraries with XAML Page elements should not cause a Button with a MenuFlyout to crash.
As an aside (and me just venting), what makes this particularly egregious is:

The bug happens even when the library isn't actually used in the application (and thus should have been removed by the NativeToolchain linking).
Because of this bug, for my application there there just isn't a work around for this issue.

Screenshots
No response
NuGet package version
No response
Packaging type
No response
Windows version
May 2019 Update (18362)
IDE
Visual Studio 2019
Additional context
No response

@Scottj1s is this a cswrint issue?

keep alive

Thanks for filing!  Unfortunately we are not currently investigating WinUI2 issues that are not business or security critical (more on the policy here).


Create PipelineCacheEvent to report changes to pipelines in PipelineCache.

Objective
Previously, the only way to tell if a pipeline had been loaded was by polling for the CachedPipelineState, and there was no way to know if a pipeline had been reloaded (for example because of hot-reloading a shader). Now, youcan listen for PipelineCacheEvents to know when a Pipeline has been created or invalidated (or even failed to create)!
Fixes #9616.
Solution

Describe the solution used to achieve the objective above.

Changelog

Added PipelineCacheEvent to notify users of changes to pipelines stored in the PipelineCache.

Extra notes
I tested this on my personal project, and was able to reset my render_graph::Node to its "loading" state whenever I updated my shader through the filewatcher feature! Now playing with compute shaders is a ton easier!

Code looks fine to me, and I don't think I have any objections to adding the feature.
Curious to know what the use case for this is though. Why does your node care about when the pipeline gets reloaded?

TL;DR graph nodes with "setup" stages may need to be reset when a shader reloads (or more generally a pipeline reloads) so the setup stages reruns. Not strictly necessary, but quite nice!

I feel like this is easier to solve by just storing the last pipeline id in the node, and when you get the pipeline from the cache in your node, just compare it to the last stored id. Like I said I'm not against this feature in general though.
Would like to hear what kind of setup your doing in more concrete terms though. I'm curious what kind of data or whatever you need to reset.

I guess "easier" is in the eye of the beholder haha. I was actually able to make this work, so that seems to be a valid workaround, thank you! It does mean having to keep track of the PipelineId which are completely distinct from the CachedPipelineId (it would be nice to note in the CachedPipelineId docs that the PipelineId can change underneath it). I was able to do that with this function (including just for interest):
fn update_pipeline(
  cached_pipeline_id: CachedComputePipelineId,
  last_pipeline_id: &mut Option<ComputePipelineId>,
  pipeline_cache: &PipelineCache,
) -> bool {
  let mut require_reset = false;

  match pipeline_cache.get_compute_pipeline(cached_pipeline_id) {
    None => {
      *last_pipeline_id = None;
      require_reset = true;
    }
    Some(pipeline) => match *last_pipeline_id {
      None => {
        *last_pipeline_id = Some(pipeline.id());
      }
      Some(current_pipeline) => {
        if pipeline.id() != current_pipeline {
          *last_pipeline_id = Some(pipeline.id());
          require_reset = true;
        }
      }
    },
  }

  require_reset
}

As for my concrete case: I am trying to make an ocean "simulation" compute shader. This involves roughly 3 steps (simplified because I'm not fully done): 1) generate random noise on startup (on the CPU), 2) use the noise to determine the amplitudes of waves on startup (or whenever params change), 3) use FFTs to turn "frequency-space" wave amplitudes into the actual heights of the waves every frame.
I have a render graph node:
enum OceanSimulationNode {
  Loading,
  InitWaveAmplitudes,
  UpdateWaterHeight,
}

In my render_graph::Node::update (is_ready just checks if all CachedComputePipelineIds have an Ok status in the PipelineCache):
match self {
  Self::Loading => {
    if self.is_ready(world) {
      *self = OceanSimulationNode::InitWaveAmplitudes;
    }
  }
  Self::InitWaveAmplitudes => {
    *self = OceanSimulationNode::UpdateWaterHeight;
  }
  Self::UpdateWaterHeight => {}
};

With hot-reloading shaders, I can change the FFT shader and see changes immediately. However, if I change the "step 2" shader, the OceanSimulationNode is already in the UpdateWaterHeight state, and so the pipeline never runs.

But as I said above, this can be worked around with keeping track of the PipelineId in additional to the CachedPipelineId. Personally I like the event scheme since A) it involves less bookkeeping by users (e.g., me), and B) it's more inline with Bevy as a whole I'd say? One disadvantage is this kinda requires two "flushes" as I have in the code - one for when shader events are extracted, and one after the render system, so it is less nice to render in response to a pipeline being ready (there will likely be a 1 frame delay).
I'm not sure which is the better solution! What are your thoughts?

I'm gonna just close this because it's been inactive and there's a fine workaround. I'll also close the issue and add the workaround there.


feat(firebase_storage): add useEmulator support

Description
Initial work for Storage emulator on the web platform.
Related Issues
none.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

Blocked pending iOS SDK 8 landing.

@googlebot I consent.

Update:

Emulator reports wrong error when a ref is not found AND not readable.
read rule on emulator isn't working.
Update metadata is throwing a dart error on web.

Fixed the metadata issue, there was an implicit cast issue on web. Update the tests to work around emulator issues and commented out those which cannot be fixed until a fix lands on the emulator.

@googlebot I consent.


Add http client support in Ballerina Shell

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues.

Fixes #39893
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

@DamithaSenevirathne Shall we close this PR for now, since we are differing it for now?


v4 signatures not supported in query params, only http headers

We sign some S3 URLs using query params, since we return them as 301 redirects. When upgrading to the newest fog, we noticed that s3ninja is now rejecting these signed URLs, because fog is now signing them with v4 and s3ninja appears to only support v4 in headers.
Working around it for now by telling fog to use v2 signatures.

A PR finxing this would be very welcome :)

Fixed in the latest release.


Optimize a[n]; n++ inside loopings

Describe the feature
In cases where we manipulate a number using ++ or -- after its use, it may be possible to use it inline, reducing a few bytes (~2 bytes per use). Currently, this feature works outside of looping.
For instance:
const a = [1, 2, 3];
let n = 0;

while (n < a.length) {
  x(a[n]);
  n++;
}

Will be (prettified):
const a = [1, 2, 3];
let n = 0;

for (; n < a.length; )
  x(a[n]), n++;

Could be:
const a=[1,2,3];
let n=0;

for(;n<a.length;)
  x(a[n++]);

So n will be post-incremented, but it will return the old value to access the index at a anyway.
It is possible to think of other variations to this rule, although most cases will be simple like the first example.
const a = [1, 2, 3];

let n = 0;
let m = 0;

while (n + m < a.length) {
  x(a[n + m]); // after: x(a[n+++m++]
  n++;
  m++;
}

// My (almost) real case:
const a = [1, 2, 3, 4, 5];

let n = 0;
let m = 2;

while (m < a.length) {
  a[m] = a[n]; // after: a[m++] = a[n++]
  m++;
  n++;
}

// My real case:
const a = [1, 2, 3, 4, 5];

let m = 2;

while (m < a.length) {
  a[m] = a[m - 2]; // after: a[m] = a[m++-2]
  m++;
}

Note: currently Terser does not support this kind of optimization.
Babel plugin or link to the feature description
No response
Additional context
No response

Here is a bad Case:
const a = [1, 2, 3];
let n = 0;

const x = (i) => {
  if(n !== 0) {
    console.log("---");
  }
  console.log(i);
}

for (; n < a.length; )
  x(a[n]), n++;

Result:
1
---
2
---
3

"minified":
const a = [1, 2, 3];
let n = 0;

const x = (i) => {
  if(n !== 0) {
    console.log("---");
  }
  console.log(i);
}

for (; n < a.length; )
  x(a[n++]);

Result:
---
1
---
2
---
3

You are right! Maybe it can check if function has scope greater then the variable.

You also need to take account exceptions/try..catch statements:
function x(a: number) {
    throw "Error";
}

let n = 5;
try {
  x(n);
  n++;
} catch { }

console.log(n);

Output: 5
function x(a: number) {
    throw "Error";
}

let n = 5;
try {
  x(n++);
} catch { }

console.log(n);

Output: 6


Webpack bundle analyzer

Tossed in webpack-bundle-analyzer and corresponding cli commands to start it up in either dev or prod. This tool is pretty awesome, and allows you to view in localhost without having to upload. I left the regular analyze script in tact.
Not sure if this is something that could/should be pulled in now, or for a future release. Open to either!

Coverage remained the same at 100.0% when pulling 078d491a249333e69176fcaf35228558031abd21 on gretzky:webpack-bundle-analyzer into af6b322929353de501c74c36603b433bc281180d on react-boilerplate:dev.

Coverage remained the same at 100.0% when pulling 078d491a249333e69176fcaf35228558031abd21 on gretzky:webpack-bundle-analyzer into af6b322929353de501c74c36603b433bc281180d on react-boilerplate:dev.

@gretzky RBP always has it`s analyze, how should their respective responsibilities be divided? Or allow them to repeat?

@blling This PR pulls in the bundle analyzer that loads in the browser, so the responsibilities are really just divided over wanting a hard copy (stats.json) of your bundle, or just being able to look at it while developing / for quick insight

This PR pulls in the bundle analyzer that loads in the browser, so the responsibilities are really just divided over wanting a hard copy (stats.json) of your bundle, or just being able to look at it while developing / for quick insight

Get it, i`m sorry, my stupid.

I'm going to close this for now in favor of reopening with some changes inspired by @avdeev


support cocoapods

Hi,
Please support installation via cocoapods, this method can solve the compatibility problem of m1 chip. Thank you.

Hi, which compatibility problems did you experience with M1 chip? Regarding integration we actively support Package Manager and Carthage. To keep the maintenance effort low we do not plan to add cocoa pods support - if you like you can open a PR for that.


Document SubscriptionIds element

Fixes #123
I left ms.assetid empty because I don't know the correct value for this attribute.

Docs Build status updates of commit 32309be:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/web-service-reference/subscriptionids.md
:bulb:Suggestion
View
Details

docs/web-service-reference/getstreamingevents-operation.md
:white_check_mark:Succeeded
View

docs/web-service-reference/subscriptionids.md

Line 61, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Cc @lindalu-MSFT

@ecederstrand Do we need to add this link anywhere in the navigation files such as landing pages or the TOC?

I'm not familiar with the structure of the docs, but that's probably a good idea. Here's an attempt: https://github.com/MicrosoftDocs/office-developer-exchange-docs/pull/154


url(..) calls

Hi, thank you so much for this library.
I am using this because I need auto-prefixing on my css, and I'm chaining postcss-loader before this. It's not working right now, and I don't really understand why.
Could we maybe document a known-good webpack config to do this?

Hey i have the same issue, I know that the url(...) inside of css literals can be resolved using
something like :

import logo from "./src/images/logo.png

.image {
   background: url(${ unsafeCss( logo ) });
}

yourFile.d.ts
declare module "*.png" {
    const val : any;
    export default val;
}

When the loader transpile the code to  const style = css... ; the url is ommited  and the problem is there i think

@MartinEmanuelMaldonado93 can you use the transform config property to transform those calls?

Hey ! has been past few days and I realize that the loader works very well actually, i make the mistake because i misunderstood the webpack url behaviour when compiles.
In my webpack.common.js i wrote that the output of my assets be written to the absolute path called "./assets" and in all of my css styles when i required i write url("./assets/myimage.png") and i solve the problem, i don't know if i was clear, but that is the solution i used for my little issue with url's thank you for your answers!


Travis CI builds failing with Ruby 1.9.3

The new Chef client requires Ruby 2+ so all PRs are failing on the 1.9.3 build.

@geerzo can you move this to https://github.com/chef-brigade/mongodb-cookbook/issues and close?


Fix building rmp_abc_library when USE_SYSTEM_ABC is set

(Small change)

I'm a bit confused by this.  USE_SYSTEM_ABC is not mentioned anywhere in the PR beyond the title.  What issue is being solved?

When USE_SYSTEM_ABC is set to true, ABC_LIBRARY is set to a non-null value. Things that require abc link against ABC_LIBRARY so ABC symbols won't be missing for those who set USE_SYSTEM_ABC to true.
rmp_abc_library was just missing ABC_LIBRARY.

rmp already links against it https://github.com/The-OpenROAD-Project/OpenROAD/blob/f0cc0ee1a62d7a6c35b43bd46a20980969eeb9a2/src/rmp/src/CMakeLists.txt#L73 - why does rmp_abc_library also need it (or should it just be moved)?

Because otherwise rmp_abc_library which is I believe compiled as a standalone unit will complain about being unable to find things in the abc:: namespace.


How to run this repository on my local environment?

I am going to run this repo on my local environment.
I already installed the npm packages.
And what should I do now?

@RisingStar-Web , here is a guide

Thanks.
One more question is that how can I run this repository on web browser?

I am going to change some source code and rebuild it.

Thanks.
One more question is that how can I run this repository on web browser?

You can't run atom on the web browser

Thanks.
One more question is that how can I run this repository on web browser?

You can't run atom on the web browser


Enhance prompts to ask the LLM to plan things ahead

I find it helpful to include in my initial prompt to first ask the LLM to make a detailed plan about the task and then follow its steps.
In this context, it'd be to create steps for whatever is set out in an issue's description.
Some rejection/exclusion criteria could minimize the LLM run away with hours of work without an unreachable goal.
In case of rejection, the LLM could be allowed to post a GitHub comment for that issue with its reasoning that lead to rejection.
It first needs to e.g. recognize whether the issue is actually about the repo itself and not about e.g. ideas how other software is doing something or to integrate a totally different software that would be in the "huge effort" category (in our understanding).
In addition, have it write the plan to an actual text file (with issue number in it), so it can reference it throughout the process ("Let's deal with step 6...").
In case of failure (or hard restrictions/limits), it could be asked to resume on it later.
TL;DR tell the LLM to not go wild, but make a plan first.

Did you try adding a .openhands_instructions file in the root folder of your repository? That file appears to be read and injected into the initial prompt.

That file is only used by the openhands resolver package and was only recently added (2 weeks ago).
It is not being read by OH or its agents, last I checked

That file is only used by the openhands resolver package and was only recently added (2 weeks ago). It is not being read by OH or its agents, last I checked

I ran a resolver GitHub action just today and it did read the file + injected it into the task description for the agent, verified by looking at the logs.

Yes, that's what I wrote: only the resolver uses it, not if you use OH itself.

Yes, that's what I wrote: only the resolver uses it, not if you use OH itself.

Ah sorry, didn't parse that correctly

I think this is a good idea, but on second thought I think it probably belongs in OpenHands proper? If planning is useful we should be using it regardless of the modality through which OpenHands is called, and we should evaluate to make sure that planning is helping out. So maybe we can close it here and discuss more on the main OpenHands repo as necessary.


Remove hungarian notation

FC used Systems Hungarian throughout the codebase, which in a strongly typed language like java using any sort of modern IDE serves no purpose except to decrease code readability.

Finished for fields. Needs to still be done for parameters and local variables but that can be done incrementally as it will not affect addons.


Because of a security error, the client could not connect to the remote computer. Verify that you are logged on to the network, and then try connecting again.

I used xrdp version 0.6.1-2 on Ubuntu 16.04 and connected to it using win10 remote desktop connection.
I had two problems with it:

environment variables differed in local/ssh session with remote session.
sometimes when I reconnect to the server remotely it make a new session and did not connect to the previous session.

So I tried to install 0.9.x version. I make and install it but its service did not start. So I reinstall 0.6.x version using apt and after some effort its service started but the new error appeared. When I try to connect to the server the following error appears:

Because of a security error, the client could not connect to the remote computer. Verify that you are logged on to the network, and then try connecting again.

I reinstalled it many times but the error did not fix.
How can I resolve the error?
Thanks a lot.

Can you show me xrdp.log and xrdp-sesman.log?

No feedback from the reporter, closing.


An error occurs when saving a memory without entering a name

https://github.com/user-attachments/assets/948df134-3b81-4932-9694-71cfe449936f
(This text is machine translated, so I apologize if it is difficult to understand or strange.)
As in this video, if you create a memory without entering a name, an error will occur.
The console will output TypeError: t.name is null.
When this happens, you will not be able to use this tool because you will not be able to delete the memory.

Thanks for reporting. I've deployed a fix.
Can you confirm if it's working for you too?
https://github.com/user-attachments/assets/f5e4dfe7-8e77-467b-8a33-32d7d000e69d

It works! thank you.


AsyncSub Messages lost during reconnect

I’m doing some advanced unit tests.
I have a 3 nodes cluster
I create 2 connections

1 for sending messages on node 1 on subject foo
1 for receiving messages on node 2 on subject foo

I start sending messages every 50 ms
I stop node 2 (the one that is used by the AsyncSub)
The AsyncSubscription is loosing all the messages that have been sent before it get reconnected to another node.
Is is the expected behavior ?
Here is a unit test that can be put in UnitTestReconnect.cs
[Fact]
public void TestIntensivePublishShouldNotFail()
{
List<byte[]> msgs = new List<byte[]>();
List sentMsgs = new List();
List receivedMsgs = new List();
        ManualResetEvent recvReconnected = new ManualResetEvent(false);

        // one connection for receiving
        Options recvOptions = ConnectionFactory.GetDefaultOptions();
        recvOptions.Servers = new [] { "nats://localhost:1222", "nats://localhost:1223", "nats://localhost:1224" };
        recvOptions.NoRandomize = true;
        recvOptions.AsyncErrorEventHandler += (sender, args) => { Debug.WriteLine("Receive Error " + args.Error + " Dropped=" + args.Subscription.Dropped); };
        recvOptions.ClosedEventHandler += (sender, args) => { Debug.WriteLine("Receive Closed "); };
        recvOptions.DisconnectedEventHandler += (sender, args) => { Debug.WriteLine("Receive Disconnected "); };
        recvOptions.ReconnectedEventHandler += (sender, args) => { recvReconnected.Set();Debug.WriteLine("Receive Reconnected "); };

        ManualResetEvent sendReconnected = new ManualResetEvent(false);

        // one connection for sending (better for sending big amount of data
        Options sendOptions = ConnectionFactory.GetDefaultOptions();
        sendOptions.Servers = new [] { "nats://localhost:1223", "nats://localhost:1222", "nats://localhost:1224" };
        sendOptions.NoRandomize = true;
        sendOptions.AsyncErrorEventHandler += (sender, args) => { Debug.WriteLine("Send Error " + args.Error); };
        sendOptions.ClosedEventHandler += (sender, args) => { Debug.WriteLine("Send Closed "); };
        sendOptions.DisconnectedEventHandler += (sender, args) => { Debug.WriteLine("Send Disconnected "); };
        sendOptions.ReconnectedEventHandler += (sender, args) => { sendReconnected.Set();Debug.WriteLine("Send Reconnected "); };

        // create server
        NATSServer ns = utils.CreateServerWithArgs("-p 1222 -cluster nats://localhost:1422 -routes nats://localhost:1423,nats://localhost:1424 -D");
        NATSServer ns2 = utils.CreateServerWithArgs("-p 1223 -cluster nats://localhost:1423 -routes nats://localhost:1422,nats://localhost:1424 -D");
        NATSServer ns3 = utils.CreateServerWithArgs("-p 1224 -cluster nats://localhost:1424 -routes nats://localhost:1422,nats://localhost:1423 -D");
        Thread.Sleep(1000);

        using (IConnection sendConn = new ConnectionFactory().CreateConnection(sendOptions))
        using (IConnection rcvConn = new ConnectionFactory().CreateConnection(recvOptions))
        {
            int receivedMessages = 0;
            int sentMessages = 0;
            int sentFailure = 0;

            IAsyncSubscription s = rcvConn.SubscribeAsync("foo");
            s.MessageHandler += (sender, args) =>
            {
                Interlocked.Increment(ref receivedMessages);
                ThreadPool.QueueUserWorkItem(o =>
                {
                    var str = Encoding.UTF8.GetString(args.Message.Data);
                    int j = Int32.Parse(str.Split(' ')[0]);
                    lock(receivedMsgs)
                        receivedMsgs[j]++;
                });
            };

            s.Start();
            rcvConn.Flush();
            sendConn.Flush();

            bool serverRestarted = false;
            ManualResetEvent sendFinished = new ManualResetEvent(false);
            ThreadPool.QueueUserWorkItem(o =>
            {
                while (!serverRestarted)
                {
                    try
                    {
                        Thread.Sleep(50);
                        byte[] msg = Encoding.UTF8.GetBytes(String.Format("{0} additionnalPayload", sentMessages));
                        msgs.Add(msg);
                        sentMsgs.Add(true);
                        lock(receivedMsgs)
                             receivedMsgs.Add(0);
                        sendConn.Publish("foo", msg);
                        sentMessages++;
                    }
                    catch (NATSConnectionClosedException)
                    {
                        // we are dead, we will never reconnect. Shall we retry ?
                        //sendConn.Dispose();
                        //sendConn = new ConnectionFactory().CreateConnection(sendOptions);
                        throw;

                    }
                    catch (Exception)
                    {
                        sentFailure++;
                    }
                }

                // after server is restarted, send more messages to check reconnect is ok
                for (int i = 0; i < 20; i++)
                {
                    try
                    {
                        Thread.Sleep(50);
                        byte[] msg = Encoding.UTF8.GetBytes(String.Format("{0} additionnalPayload", sentMessages));
                        msgs.Add(msg);
                        sentMsgs.Add(true);
                        lock (receivedMsgs)
                            receivedMsgs.Add(0);
                        sendConn.Publish("foo", msg);
                        sentMessages++;
                    }
                    catch (NATSConnectionClosedException)
                    {
                        // we are dead, we will never reconnect. Shall we retry ?
                        //sendConn.Dispose();
                        //sendConn = new ConnectionFactory().CreateConnection(sendOptions);
                        throw;
                    }
                    catch (Exception)
                    {
                        sentFailure++;
                    }
                }
                sendFinished.Set();
            });

            Thread.Sleep(500);
            // kill the server !
            int indexBeforeRestart = sentMessages;
            ns.Shutdown();

            // Wait for receiver to reconnect...
            //Assert.Equal(true, sendReconnected.WaitOne(10000));
            Assert.Equal(true, recvReconnected.WaitOne(10000));
            int indexAfterRestart = sentMessages;
            // sender will be in the second part
            serverRestarted = true;

            // wait for sending finished
            Assert.True(sendFinished.WaitOne(Int32.MaxValue));

            rcvConn.Flush();
            sendConn.Flush();

            // maybe give time to receive messages
            //Thread.Sleep(1000);

            // now check failures
            Assert.Equal(0, sentFailure);
            Assert.Equal(0, s.QueuedMessageCount);
            Assert.Equal(0, s.PendingMessages);
            Assert.Equal(0, s.Dropped);
            Assert.Equal(s.Delivered, receivedMessages);
            Assert.Equal(sendConn.Stats.OutMsgs, sentMessages); // on compte bien ?
            Assert.Equal(rcvConn.Stats.InMsgs, receivedMessages); // on compte bien ?
            Assert.Equal(sentMessages, receivedMessages);

            Assert.Equal(rcvConn.Stats.Reconnects, 1);
            //Assert.Equal(sendConn.Stats.Reconnects, 1);
        }
        ns.Shutdown();
        ns2.Shutdown();
        ns3.Shutdown();
    }

@stephenjannin, Thank you for the test case to illustrate the behavior.  What you are seeing is expected   - a subscriber will miss messages published on its topic while it is in the process of reconnecting.  Core NATS provides a quality of service that is is at most once delivery.  If you need a more reliable quality of service, we provide NATS streaming, which guarantees at least once delivery.  Alternatively, you can add logic into your application detect and resend any missed messages.


Have Instance deploy its contents in a different namespace

What happened: Expect the ability to deploy an Instance in one namespace (default or kudo-system) that runs in a different namespace taken in as a argument.
Currently this is not a feature so my operator attempts to create a namespace first and then start it self there. By taking in a parameter
tasks:
  - name: create-namespace
    kind: Apply
    spec:
      resources:
        - namespace.yaml

namespace.yaml contents
apiVersion: v1
kind: Namespace
metadata:
  {{- if (ne .Params.namespace "") }}
  name: {{ .Params.namespace | lower }}
  {{- else }}
  name: {{ .Namespace }}
  {{- end }}

This works fine since Kustomize does not manage Namespace yamls by default, but fails for the rest of my yamls because of the enhancer logic below.
https://github.com/kudobuilder/kudo/blob/90f5f925a07987aa0287659ee8533c035452b8b0/pkg/engine/renderer/enhancer.go#L55
Additional information:
https://github.com/kudobuilder/kudo/issues/945#issuecomment-545859140
What you expected to happen:
Do not enhance namespace for each yaml
Environment:

Kubernetes version (use kubectl version): 1.15.3
Kudo version (use kubectl kudo version):  0.8.0
Operator: custom
operatorVersion: custom

@latchmihay would your use case be covered by specifying a namespace in install and KUDO having the ability to create the namespace if it does not exist?

Yes, I think if we were to specify the namespace as part of the install command, Kudo could create the namespace and have kustomize enhance each following yaml with the given namespace from the install command.
This will solve the need for users to create and manage the namespace them self (like I am trying to do)

Have Instance deploy its contents in a different namespace

This is a recently documented limitation.


Remove DOTNET45 compilation symbol

If we still need the conditional code then we should use a symbol that explains its use.
@alinapopa Logging this one for you since you brought it up, let me know if you can't get to it.

Okay, that is annoying.
I was trigger happy on pushing to origin(which is my fork) and then using repeated git reset head~ && git push --force but then github thought it would be a good idea to troll this issue with non-existent commits in my fork????

Deep linking of issues a bit far perhaps?

Thanks guys, merged.


forbidden contract configuration upgrade

Description
What is the purpose of the change?
support forbidden contract configuration upgrade which makes forbidden contract more usable.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

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

Brief of your solution
Use the second contract framework and the proposal mechanism to implement the function.
I have to implement runUpdateForbiddenContract and rollbackUpdateForbiddenContract.
How Has This Been Tested?
Regression Test & Unit Test

Closing this.


Simple string expansion

Hello,
According to https://datatracker.ietf.org/doc/html/rfc6570#section-3.2.2 a uri template kan contain a single variable encompassed by curly braces ie {var}. It should be able to resolve this variable with a value.
The use case for this is to make mandatory query parameters in a link. This is for instance how spring builds up a link with a mandatory query parameter ie http://localhost/path?mandatory={value}

Thanks for the issue report. I agree that this should be fixed. Do you feel like opening a PR?

@just-paja sure, I'll try and do that somewhere this week.

@just-paja in order to achieve this functionality, the code has to change quite a lot. I'm trying to make it so the code will be expandable to future requirements that meet the URI template spec. Just so you know I'm working on it, but it takes a bit of time :D

@SBylemans oh. Sorry to hear that :-D If you need any help we can schedule a call and take a look at it together. Hope you don't need this to quickly fix a bug in your production app.

Hey @just-paja no it's rather a nice to have. The code is complete, just testing now. I was able to remove the dependency on qsm.
I have a question though, why is an array of links not translated? Ie:
    [
      {
        href: 'http://example.com/api/users/{bar}/{foo}?param={param}',
        rel: 'edit'
      }
    ]

    getHalLink(links, 'edit',
      { bar: 'bar', foo: 'foo', param: ['multiple', 'params'] }) // returns http://example.com/api/users/{bar}/{foo}?param={param}

@just-paja my bad about the array stuff, forgot the templated: true property.
I made a PR here : https://github.com/just-paja/hateoas-hal-link-resolver/pull/10

I think this is resolved. Please reopen if necessary ;-)

@SBylemans thank you for your contribution


Update aws_poly_voice_id.dart

added more Polly voice ids

Pleae accept my changes. I found the package usefull but it doesn't have the most up-to-date voice ids list


Request: Close SwipeRow programmatically

I need to make SwipeRow close programmatically.
My use case (which may apply to many others):
onRowDidOpen triggers -> Perform action "e.g delete message" -> Close the swipe menu
^ Specific to SwipeRows with only one option rather than multiple buttons

If you get a reference to the SwipeRow using useRef called myRef then you should be able to call myRef.current.combinedOnPress()
If you get a reference the old fashioned way I think it would be this.refs.myRef.combinedOnPress() or this.myRef.combinedOnPress()

Hey @2JJ1, @dcenatiempo's option might work. How about this:

  onRowDidOpen = (rowKey, rowMap) => {
    const row = rowMap[rowKey];
    // do whatever actions you need to do here
    row.closeRow();
  };

  render() {
    <SwipeListView
      data={this.state.listViewData}
      onRowDidOpen={this.onRowDidOpen}
      renderItem={data => (
        <TouchableHighlight
          onPress={() => console.log('You touched me')}
          style={styles.rowFront}
          underlayColor={'#AAA'}
        >
          ...
        </TouchableHighlight>
      )}
      renderHiddenItem={(data, rowMap) => (
        <View style={styles.rowBack}>

@jemise111 Thank you for your reply, but I was looking for a solution with the SwipeRow component API

@2JJ1 oops! Missed that part. In that case how about just:

onRowDidOpen = () => {
  // Do whatever actions are needed
  this.swipeRowRef.closeRow();
}

render() {
  return (
    <SwipeRow
      ref={ref => this.swipeRowRef = ref}
      onRowDidOpen={this.onRowDidOpen}
      leftOpenValue={75}
      rightOpenValue={-75}
    >

@2JJ1 oops! Missed that part. In that case how about just:

onRowDidOpen = () => {
  // Do whatever actions are needed
  this.swipeRowRef.closeRow();
}

it should be :
onRowDidOpen = () => {
	if (this.swipeRowRef != null) this.swipeRowRef.closeRow();
};


iframe vs. native webview to host EPUB content documents (spine items)

Discussion started at:
https://github.com/readium/readium-2/issues/10#issuecomment-256211323

@winniequinn said:
I'm just starting to play with the idea of not using iframes at all. They cause issues with paged-x (at least on mobile), they can get in the way when using VoiceOver or TalkBack (as the browser sees the iframe as another container to be navigated into), et cetera.
The whole point of using an iframe, at least as far as I know, is to be able to maintain an outer container for the reading system with the iframe being responsible for holding the contents of the book. This certainly makes sense if the goal is to be able to move between different chapters of a book all within the browser as is presently the case with Readium.
At least on mobile though, I think another solution is possible. We could get rid of the iframe, make the browser responsible only for showing a single chapter, and then load up other chapters in different web views that are then swapped into view as appropriate by the application-layer code written in Java, Swift, et cetera. This approach would seem to eliminate the need for an iframe, would make precaching adjacent spine items very simple, and would allow more work to be lifted out of the land of JavaScript and brought into the application layer.
It may well be possible to use the same approach on the desktop as well. Electron has a web view component that presumably could be used to the same effect as WKWebKit and android.webkit.WebView. I need to look into this a bit further.

@rkwright replies:
@winniequinn This is not a bad idea (at all).  Iframes are certainly not ideal.  However, trying to put separate spine items in separate containers has been tried more than once.  See the prefetch branch in shared-js.  One of the major problems encountered is NOT playing audio and video (as well as scripting) before the web-view is "brought into view". Both EvidentPoint and Bluefire experimented with it, but were unable to resolve it satisfactorily.  But YMMV...  It WOULD be a good approach if the problems can be resolved.

@HadrienGardeur replied:
This feels like two separate discussions:

what the reader/container is and how we inject CSS/JS
how we handle navigation between spine items

I'm also in favour of either dropping the iframe or offering an alternative, as I've said before in https://github.com/readium/readium-2/issues/12#issuecomment-255015051
How we actually handle different spine items is another question, probably worth having its own issue here.

@danielweck replied:
@winniequinn this is how other "i"-named reading systems do it.
In Readium-1 we have reader.html that effectively bootstraps the entire readium-shared-js subsystem (rendering engine), which lays out the EPUB content iframe hosts, and is responsible for injecting behaviours into spine items (Media Overlays, link hijacking, keyboard / input device intercept and forwarding, CSS styling, epubReadingSystem, MathJax, etc.).
Using native webviews instead of iframes would mean writing a large portion of the rendering code in native per-platform code, which I think is acceptable in the context of Readium-2.
Note that we did look into using Electron's special web frame, but this is basically an extended iframe with special features (still in the renderer process though).

Electron webframe:
https://github.com/electron/electron/blob/master/docs/api/web-frame.md

@danielweck
There's also this:
 component in electron
https://github.com/electron/electron/blob/master/docs/api/web-view-tag.md

Oh thanks! :)

Part of my comment at https://github.com/readium/readium-2/issues/12#issuecomment-255015051 is also relevant here:
3. Serving content
Ideally, I'd like each implementation to support the following things:

expose a manifest in a format where a single document can contain all the information that we'll need (this covers metadata, spine, manifest and table of contents), which means that I can do a single request and cache it
serve each resource in the publication in a way that doesn't require to rewrite links and URIs for images/audio/video/CSS/JS, which means that all paths will be relative to the manifest
allow the ability to inject JS/CSS in HTML documents without using an iframe and injecting in JS (for example using query parameter such as GET /chapter1.html?js=paginate.js&css=paginate.css instead of a plain GET /chapter1.html) and expose this ability via a URI template in the manifest
support media fragments, for example when I need to start audio/video at a specific timestamp
serve a number of static resources that are useful (HTML reader, JS, CSS)

With all these, I think it would provide a lot of flexibility in what could be achieved by implementers:

Reading System A can use the default implementation (currently reader.html + iframe)
Reading System B decides instead that it would prefer to simply use our native implementation with its HTTP server + decryption, get the manifest (and cache it) and handle pagination and the rest itself (for example using the WKWebview APIs for pagination)
Reading System C only streams EPUB files, and handles the HTTP part on their own server, but uses our JS to handle everything else in a native app with a Webview


Change Colour Discover/Read more messages in Front-end

The PR aims to replace yellow background for Discover/Explore more text.

Thanks @acocac!


feat: add TS snippets to the docs

Implements this https://github.com/lightbend/akkaserverless-javascript-sdk/issues/174.

@pvlugter

Realise these are existing issues with the JS docs. If we don't care, then fine to merge as is.

Totally understand that, I'd go with "let's merge now and make progressive updates after that". We need a bunch of updates in the doc anyway :)


Due date shown 1 day earlier again

I'm having trouble again with due dates not showing correctly.
Here is my selective bin collection entry in devtools, showing 11.20 (which is good)

But then in the todo list it shows 11.19 (which is wrong)

In the meanwhile we went from DST to non-DST, so perhaps something about time zones may impact this?

Did you change your timezone to match on ha

I didn't change anything, it is set based on geography.

Can you try adjusting the code at line 243 in classes/todo_integration as follows:
            if item.due:
                if item.due.time() != time(0, 0, 0):
                    due = item.due.astimezone(self._ha_timezone)
                    if due.time() != time(0, 0, 0) and due.time() > time(12, 0, 0):
                        due = due.date() + timedelta(days=1)
                    else:
                        due = due.date()
                else:
                    due = item.due.date()

                todo[ATTR_DUE] = due

It's difficult for me to test because I'm now at GMT+0.

My error, I'd missed the point (in both sets of changes) of where it provides tasks for the in built HA core todo panel, as opposed to as an attribute on the entity.
todo_integration.py.zip
Please replace todo_integration.py with the attached version.

With the changes, it looks like dates appear fine. At least at the moment. :) Any other cases I should try/test?

I don’t think so. I’m in the process of adding formal testing to the integration which I hope will cover it.

Issue fixed with v1.0.0


Update the CostError to modify the weights instead of the outputs

I think that the current approach of subtracting the output by the costError is cheating. Fix this to create an matrix to subtract from the current weights after the hidden layer.


How to get the status bar sample to work?

I quite new to both JS and TS, and am trying to get the first sample to work.
I've gone with npm install, but when I press F5 nothing happens apart from the debugging being run. I thought that maybe a new VS instance would open like in an example from of the Youtube tutorial videos, but that is not happening. Only the debugging tab shows up.
The main issue here is not so much that the sample does not work, but that everything is so complex that I do not know where to even begin fixing it. I wish I knew how to trace the program from start to finish. I might need this in order to get a feel for how all of this works. Do you have any advice for how this might be done?

I've tried a few other samples and all of them launch a VS Code instance, so the problem is definitely with the status bar sample. I've gone through the .json files in the .code folder and tried overwriting them with the completion sample files. That seems to have done nothing.
Could the problem be in package.json, package-lock.json or tsconfig.json? I've gone through them and I can't see anything out of the ordinary. I have no idea at this point.
At any rate, did manage to get the example to run by pasting the extension.ts code into a template and triggering the command, so I can confirm that there is nothing wrong with the extension itself.

helloworld-sample has the same VS Code launch issue as well.

lsp-log-streaming-sample gets stuck launching the VS Code instance as well. Also, I find the instructions for it ambiguous.
"languageServerExample.trace.server": {
  "format": "json",
  "verbosity": "verbose"
},

Where should this be added? There is a languageServerExample.trace.server in package.json. Should that be overwritten?

fsp-sample worked for me yesterday, but it does not today. I thought there was something wrong with the project, but now it seems like this is some VS Code specific bug.

Since this seems to be a VS Code specific bug rather than being related to the plugins themselves, I am closing this here.


Portal file access is confused after using this

Feel free to just close this as it's a pretty unusual use case but I'm raising it for the record.
So I installed and ran this in the Azure portal Functions Console (because I could) and then wanted to look at the files using the Functions Files UI - mainly to figure out what had been done. I had a single functions
When the Functions panel is opened the .funcpack/index.js is open which make sense I guess. However if you use the Files UI to explore other files it is impossible to get back the .funcpack/index.js

@lindydonna - any idea why this would be?

File viewer only allows access to function folder and below I think. .funcpack is in wrong place.

@christopheranderson Can you tell me the layout that funcpack produces?
Note that the API for listing the functions within an app is in Kudu.

So this produces a structure like:
-/.funcpack/index.js
-/foo/index.js
-/foo/function.json
-/bar/index.js
-/bar/function.json

I think the problem here is that you can't navigate back to .funcpack/index.js once you navigate away. If the file's tool in the portal let you navigate down the root of the Function App, that might help with this and other issues like shared libraries/node modules/etc.

@christopheranderson Great point. I'll add this to the portal backlog. I'll have to work with the designer to find the right UX.


Error occurred when executing LivePortraitProcess

Hello. I'm getting an error like this.
Comfyui current
requirements loaded
Thank you from now

Make sure this file is in the right place:
https://github.com/kijai/ComfyUI-LivePortraitKJ/blob/main/liveportrait/utils/resources/mask_template.png