Large json import in .js file causes 100% CPU + autocomplete stops working

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.63.2
OS Version: macOS 11.6.2

Steps to Reproduce:

Put a large json file in a directory, e.g. data.json (mine is 2 MB)
Edit a file in the same directory, e.g. index.js
Add import data from './data.json' to the top of the file
CPU jumps to 100% (but VS Code is mostly still usable)

If I comment the import and then reload the window, CPU goes back to normal
Some other stuff that coincides with this:
If I reload the window with the import uncommented:

CPU goes up right away
Semantic styling is slightly off e.g. unused variables are not darkened
After about a minute, semantic styling corrects itself, and at the same time all autocomplete suggestions stop working.

(Autocomplete not working is the main thing making life difficult)
Some stuff I've tried, but did not help:
{
  "files.watcherExclude": {
    "**/*.json": true,
    "**/src/data/**": true
  },
  "search.exclude": {
    "**/src/data/**": true,
    "**/data/**": true
  },
  "npm.exclude": "**/src/data/**",
  "timeline.excludeSources": ["**/src/data/**"],
  "editor.unicodeHighlight.ambiguousCharacters": false,
  "json.maxItemsComputed": 50,
  "workbench.settings.enableNaturalLanguageSearch": false,
  "editor.wordBasedSuggestions": false
}

Happy to provide any other info.

Hi,
I added the following to a jsconfig.json at the root of my project, and that fixed it:
{
  "exclude": ["**/src/data/**"]
}

Maybe there's a useful place to document this?  (I only figured it out with some help on reddit).  Otherwise feel free to close this.

Can you please share a minimal example project that demonstrates this issue so we can investigate?


Auto-upgrade to <IP_ADDRESS>

Base PullRequest
default branch (https://github.com/http4k/http4k-connect/tree/master)
Command results

Details:

add path
/home/runner/work/_actions/technote-space/create-pr-action/v2/node_modules/npm-check-updates/build/src/bin

./upgrade_http4k.sh <IP_ADDRESS>

Changed files

Changed file:

gradle.properties

:octocat: Repo | :memo: Issues | :department_store: Marketplace

Codecov Report

Merging #223 (1bc48bc) into master (5abb006) will increase coverage by 71.86%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@              Coverage Diff              @@
##             master     #223       +/-   ##
=============================================
+ Coverage          0   71.86%   +71.86%
- Complexity        0     1141     +1141
=============================================
  Files             0      572      +572
  Lines             0     6302     +6302
  Branches          0      514      +514
=============================================
+ Hits              0     4529     +4529
- Misses            0     1469     +1469
- Partials          0      304      +304

see 572 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Scala Language Support – Counter Sample Straw Man [NO MERGE]

First draft on some rough ideas around how scala language support could look. This only intended to serve as a discussion piece.
This example takes on a certain implementation style where behavior is organized by state. We can look at other styles in another discussion PR.
Opening this up early for comments, I'll try to flesh things out as questions and comments come in, and can continue to elaborate if there's something of interest here.

@ryanhanks great for exploring ideas regarding the code generation with already built-in patterns. i like the way the state is always passed in the handler methods.

Having the built-in pattern for resource-style responses, automatically returning the updated state, is an interesting simplification. Do you think we would still need a way to specify other responses as well? (could be something like CommandEffects.accept(event).thenReply(newState => response))

How do you mean by specify other responses? The example here isn't intended to convey that mapping might be entirely automated, you'll notice that each state handler implements a mapper object that's assumed to be used in the default execution by the underlying implementation:
  /*
  * Response object mapper
  * */

  override def mapDomainCounterToApiCounter(activeCounter: ActiveCounter): CounterApi.Counter =
    CounterApi.Counter.activeCounter(activeCounter.value, activeCounter.maxValue)

The assumption here is that each state handler can provide a default mapping from one of the internal states to some external response, but that each state handler is responsible for providing a reply if it is the resultant state.
If further customization is desired, one of the underlying buildResponse methods could be overridden (these would have different default behavior that calls the mapper method rather than throwing, just copying and pasting from the example as it exists now):
  /*
  * Response builders
  * */

  def buildInitializeResponse(activeCounter: ActiveCounter, initializeRequest: InitializeRequest): InitializeResponse = throw new UnsupportedOperationException("No response")

  def buildStartResponse(activeCounter: ActiveCounter, startRequest: StartRequest): StartResponse = throw new UnsupportedOperationException("No response")

  def buildIncrementResponse(activeCounter: ActiveCounter, incrementRequest: IncrementRequest): IncrementResponse = throw new UnsupportedOperationException("No response")

  def buildStopResponse(activeCounter: ActiveCounter, stopRequest: StopRequest): StopResponse = throw new UnsupportedOperationException("No response")

  def buildGetCounterResponse(activeCounter: ActiveCounter, getCounterRequest: GetCounterRequest): GetCounterResponse = throw new UnsupportedOperationException("No response")

The assumption here is that each state handler can provide a default mapping from one of the internal states to some external response, but that each state handler is responsible for providing a reply if it is the resultant state.
If further customization is desired, one of the underlying buildResponse methods could be overridden

Yes, makes sense. That would provide all the customisation needed. And I think returning the updated state in a RESTful resource style is a good default 👍

@ryanhanks, I'll close this straw man PR now. Ideas for code generation and type-safe APIs are definitely interesting. Any more work on Scala language support can go in https://github.com/cloudstateio/scala-support


feat(container): overriding container width when login / not login(app bar & navigation)

Overriding container width when login / not login , by adding condition and setting the
max-width=false and then setting the wanted width. You can see the custom breakpoints in src/theme

Comparison when login / not login

View when is login

Breakpoints
I added xl2 to be used when overriding the container

If you want to match up what is the width of your navigation and appbar to your body's width you can do this approach


Lime-68, Wrong emergencyWithdraw logic

Description
Stacked pull request on #204
In AaveYield.sol the functions:

liquidityToken
_withdrawETH
_depositETH
Make a conditional call to IWETHGateway(wethGateway).getAWETHAddress()

This function does not exist in the wethGateway contract, causing these function to fail with the error "Fallback not allowed".
The function they should be calling is getWethAddress() without the "A".
Small yet dangerous typo.
Integrations Checklist

[ ]  Have any function signatures changed? If yes, outline below.
[ ]  Have any features changed or been added? If yes, outline below.
[ ]  Have any events changed or been added? If yes, outline below.
[ ]  Has all documentation been updated?

Changelog

Updated function call for AaveYield.sol contract(https://github.com/code-423n4/2021-12-sublime-findings/issues/42)

Event Signature Changes
Function Signature Changes
Features
Events

Codecov Report

Merging #205 (f7bd715) into lime-133 (20d2bea) will not change coverage.
The diff coverage is 0.00%.

@@            Coverage Diff            @@
##           lime-133     #205   +/-   ##
=========================================
  Coverage     15.94%   15.94%
=========================================
  Files            16       16
  Lines          1737     1737
  Branches        321      321
=========================================
  Hits            277      277
  Misses         1460     1460

Impacted Files
Coverage Δ

contracts/yield/AaveYield.sol
17.52% <0.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 20d2bea...f7bd715. Read the comment docs.

Aave is not being used. Hence closing the PR.


Fix typo ez

Some of the few typos through grammarly's vscode extension. Just modified some of the obvious ones.

🚀 Deployed on https://63f7f847a665190cc67d4924--cozy-fox-0defec.netlify.app


Showing a special workspace may reveal all of them

Using today's git version (but it happened with the last release).
Having a couple of windows in two different special workspaces:
❯ hyprctl clients |grep special |grep -v grep
	workspace: -99 (special:scratch)
	workspace: -98 (special:minimized)
	workspace: -98 (special:minimized)

Showing the minimized workspace (hyprctl dispatch togglespecialworkspace minimized) sometimes shows the scratch workspace.
If I explicitly show and hide the scratch workspace then the bug can't be reproduced for some time, showing and hiding special workspaces will work as expected, until an undefined action/amount of time.

any updates?

I'm not sure it's happening anymore... I didn't experience it recently.

closing then, feel free to reopen if it happens


fix: de-duplicate all entry names to clarify duplicate names

Before you open a pull request, note that this repository is forked from here.
Unless the issue you're trying to solve is unique to this specific repository,
please file an issue and/or send changes upstream to the original as well.

Using the de-duplicated names from the disambiguate_toc_name function, updating entries of all disambiguated names other than just the TOC file. This includes entries on Overview pages as well as for references.
Instead of outputting the file content each time yaml_data is pulled, wait until names are disambiguated. The function is updated to keep track of all names that are disambiguated.
For each of the yaml data entry and reference, cross-check with the names that were disambiguated and make necessary updates. Then, with the updated names, output the file content at the end.
There is a minor side effect of longer entry names, for example from client to bigquery_storage_v1.client and possibly longer if necessary; but I think we can live with slightly longer name for clarity.
Updates internally filed issue

It's a good idea to open an issue first for discussion.

[x] Tests pass
[ ] Appropriate changes to README are included in PR

Confirming the output looks good using bigquery-storage and aiplatform first.

Verified that it looks good!


Allow value-less prop assignments

What problem does this feature solve?
I'm not too sure how common this is, but here's my use case:
I'm using Vue pretty frequently to create wrapper components of all kinds. When doing so, it happens regularly that several individual props need to be passed down to child components.
As an example, a RangeSlider component accepts the props min, max, step, disabled and value and passes them to an underlying <input>. The template might look like this:
<input
    type="range"
    :value.sync="value"
    :min="min"
    :max="max"
    :step="step"
    :disabled="disabled">

This adds quite a lot of visual noise.
What does the proposed API look like?
I'd like to propose the possibility to omit the value from prop assignments. An assigned prop p without a value will use the component's p property as its value.
This will be much clearer by example:
Basic example
Suggested:
<input :min :max>

equals current:
<input :min="min" :max="max">

Modifiers are ignored
Suggested:
<input :value.sync>

equals current:
<input :value.sync="value">

With that, the introducing example could be reduced to this:
<input type="range" :value.sync :min :max :step :disabled>

I'd consider that a much more elegant and concise, however possibly a little less obvious, syntax.
What do you think?

See https://github.com/vuejs/vue/pull/2877#issuecomment-226618510

Thanks for clarification, didn't find that original issue.


[AutoPR automation/resource-manager] New tag for 2018-06 APIs for Automation

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3906

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/3125

(message created by the CI based on PR content)


Inconsistent scrypt output with .NET 8

Program.cs:
using System;

using Org.BouncyCastle.Crypto.Generators;

byte[] secret = "secret"u8.ToArray();
byte[] salt = "salt"u8.ToArray();

for (int i = 0; i < 3; i += 1)
{
    byte[] hash = SCrypt.Generate(
        P: secret,
        S: salt,
        N: (int)Math.Pow(2, 17),
        r: 8,
        p: 1,
        dkLen: 64);

    Console.WriteLine(Convert.ToBase64String(hash));
}

ScryptTest.csproj:
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net8.0</TargetFramework>
    <Nullable>enable</Nullable>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="BouncyCastle.Cryptography" Version="2.2.1" />
  </ItemGroup>

</Project>

Expected Result (when <TargetFramework> is net7.0):
TQ/d9EkSgAn+BqwPDyKgp5AY4wNNEk96g6yMh3DeZ3L0f+MvHWMpgpNfH6Kmk4ItOFUSVbxY8HLUgpdPlSy++Q==
TQ/d9EkSgAn+BqwPDyKgp5AY4wNNEk96g6yMh3DeZ3L0f+MvHWMpgpNfH6Kmk4ItOFUSVbxY8HLUgpdPlSy++Q==
TQ/d9EkSgAn+BqwPDyKgp5AY4wNNEk96g6yMh3DeZ3L0f+MvHWMpgpNfH6Kmk4ItOFUSVbxY8HLUgpdPlSy++Q==

Actual result (when <TargetFramework> is net8.0):
QyWiiA4Lx83+uIa7yXoCeP5aG3MFVmlnTYQVw5Z2AJYEno1rfMpLb7+BtppRg9DO0ATcQ3xkod7B+rYXoh7xbw==
Lysd/+QvSLOlygtIDqLl++5n+4c2Yn42zHlI2DY9pvzMnHq4iLMb0rqvwhb9dEDql2h+lm4UFUVjmEHXB/EBug==
Lysd/+QvSLOlygtIDqLl++5n+4c2Yn42zHlI2DY9pvzMnHq4iLMb0rqvwhb9dEDql2h+lm4UFUVjmEHXB/EBug==

The result of the first run is different every time, and the rest doesn't match the output of .NET 7.
>dotnet --info
.NET SDK:
 Version:   8.0.100-rc.2.23502.2
 Commit:    0abacfc2b6

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.19044
 OS Platform: Windows
 RID:         win-x64
 Base Path:   C:\Program Files\dotnet\sdk\8.0.100-rc.2.23502.2\

.NET workloads installed:
There are no installed workloads to display.

Host:
  Version:      8.0.0-rc.2.23479.6
  Architecture: x64
  Commit:       0b25e38ad3

.NET SDKs installed:
  6.0.414 [C:\Program Files\dotnet\sdk]
  7.0.111 [C:\Program Files\dotnet\sdk]
  8.0.100-rc.2.23502.2 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.22 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 7.0.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 8.0.0-rc.2.23480.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.22 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 7.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.0-rc.2.23479.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 6.0.22 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 7.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 8.0.0-rc.2.23479.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
  None

Environment variables:
  Not set

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download

Thanks for the report. I am able to reproduce it in small examples like this, though our scrypt tests pass as part of a full test suite run (but test vectors fail if run in isolation). The problem persists even when the library itself is compiled for net8.0. It doesn't seem to happen with debug builds.
From a brief investigation it appears related to the intrinsics-based code in Salsa20Engine.SalsaCore (commenting that out lets everything work normally). Given all the above I would suspect some sort of bug in the runtime (probably the JIT), but I will look into it a bit further.

@peterdettman do you have any update on this?
we have the same issue

We were also able the reproduce this issue and tried to solve it via an initial static call to the generator function inside a utility class. This seems to somewhat consolidate the output, although it is still inconsistent in automated test context. We are looking forward to any update regarding this issue.

I ran into this issue and was able to reproduce it on a test deployment computer and not on a development machine, but it seems to have been resolved in a .net 8 runtime update somewhere between 8.0.2 and 8.0.10, I didn't go through each version to see when it was fixed
Host:
  Version:      8.0.2
  Architecture: x64
  Commit:       1381d5ebd2
  RID:          win-x64

.NET SDKs installed:
  No SDKs were found.

.NET runtimes installed:
  Microsoft.AspNetCore.All 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 8.0.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

Other architectures found:
  x86   [C:\Program Files (x86)\dotnet]
    registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

M:\test>scrypttest.exe
gsvwevYggrm41nIWhCENIJdcopkJ/AfVxhrmdkS/GEnFVlq96CZKXMHR87uF3shXT9TzNHjTJaWaW8V6YEngrw==
Lysd/+QvSLOlygtIDqLl++5n+4c2Yn42zHlI2DY9pvzMnHq4iLMb0rqvwhb9dEDql2h+lm4UFUVjmEHXB/EBug==
Lysd/+QvSLOlygtIDqLl++5n+4c2Yn42zHlI2DY9pvzMnHq4iLMb0rqvwhb9dEDql2h+lm4UFUVjmEHXB/EBug==

so replicated the random result, then after installing the .net 8.0.10 web hosting bundle in my instance:

M:\test>dotnet --info

Host:
  Version:      8.0.10
  Architecture: x64
  Commit:       81cabf2857
  RID:          win-x64

.NET SDKs installed:
  No SDKs were found.

.NET runtimes installed:
  Microsoft.AspNetCore.All 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 8.0.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

Other architectures found:
  x86   [C:\Program Files (x86)\dotnet]
    registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

M:\test>scrypttest.exe
TQ/d9EkSgAn+BqwPDyKgp5AY4wNNEk96g6yMh3DeZ3L0f+MvHWMpgpNfH6Kmk4ItOFUSVbxY8HLUgpdPlSy++Q==
TQ/d9EkSgAn+BqwPDyKgp5AY4wNNEk96g6yMh3DeZ3L0f+MvHWMpgpNfH6Kmk4ItOFUSVbxY8HLUgpdPlSy++Q==
TQ/d9EkSgAn+BqwPDyKgp5AY4wNNEk96g6yMh3DeZ3L0f+MvHWMpgpNfH6Kmk4ItOFUSVbxY8HLUgpdPlSy++Q==

My testing with 8.0.10 confirms that the issue no longer occurs.


kernel: remove unix sys calls;

One might use / build with gosoline on windows ... :-D

You are replacing the unix package with a deprecated package:
https://golang.org/pkg/syscall/
"Deprecated: this package is locked down. Callers should use the corresponding package in the golang.org/x/sys repository instead. That is also where updates required by new systems or versions should be applied. See https://golang.org/s/go1.4-syscall for more information."
Does it actually build on windows with the syscall package instead of the unix package?


[EAK-330]: Website updates

Add H1 tag and breadcrumb to the content pages
Update content navigation according to semantic
Fix external links attributes
Fix external links detection
Fix content directory watch
NPM dependencies updated for both CI Lint and Site

PS: will be merged via squash as usual

@smiakchilo , thank you!
Yep, sure, the squashed result will have a message according project guide.


Floating IP - Why LB?

[Can you please share more details on why does the ASCS and ERS Floating IP needs to be under Load Balancer? if the pacemaker cluster can plumb the IP on the node where we need it to be as per required sequence and dependencies then DNS will take care of the name resolution. About IP's health, assuming pacemaker can do that as it does support floating IP. any additional information will be very helpful. ]

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

ID: 5d2a9d09-f0f0-f02a-dfc6-f9562c0d66ec
Version Independent ID: f7c0b99d-daae-5616-ab57-ff256d65bc2a
Content: Azure VMs high availability for SAP NetWeaver on SLES - Azure Virtual Machines
Content Source: articles/virtual-machines/workloads/sap/high-availability-guide-suse.md
Service: virtual-machines-sap
GitHub Login: @rdeltcheva
Microsoft Alias: radeltch

Thanks for the feedback! We are currently investigating and will update you shortly.

Thanks for the feedback! We are currently investigating and will update you shortly.

Any luck on this?

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. If you are still experiencing a problem, you might want to move this question to Microsoft Q&A: https://learn.microsoft.com/en-us/answers/tags/112/azure-sap  #please-close

This is not a question / answer, so any reason we are being redirected to Microsoft Q&A rather than Subject Matter Expert in this area looking into this? This has very big impact on the availability of the critical systems.

ALso this question is not specific to SAP Applications, it is for any pacemaker cluster in case of IaaS usage on Azure.


Error when filter string contains "#"

When filtering against field with values that include "#" datashader could not render layer.
Example: "#1234 -- Brown Fox"
When the query criteria was changed to "*Fox" datashader rendered/returned results with no errors.
The following errors were seen. (List is not exhaustive.)
JSONDecodeError('Unterminated string starting at line 1 column 236 (char 235'))
JSONDecodeError('Unterminated string starting at line 1 column 491 (char 490'))
JSONDecodeError('Unterminated string starting at line 1 column 728 (char 727'))

@maihde This issue is resolved in the application using datashader, but I'm not seeing any changes to datashader itself to resolve the issue. Do you  have insight?

I do not see this error either. I am going to close this out.


QUnit Example error

In fetch-api-lab/app/test/test.html Line:71 error is a string so
assert.ok(error.message.indexOf('File not found'),
          'bad responses throw error that contains response.statusText');

is a TypeError is it cannot read property indexOf of undefined which is breaking all subsequent tests.
Removing message.indexOf from the assert.ok prevents the error.

Hi @dipscom
Thanks for filing a bug!
It looks like this test assumed that an Error object would be thrown in validateResponse, rather than a string. I've made the test more robust by checking for string errors as well in 05bbdac.
I also found a typo in a method call (assert.ok was being called as assert.okay) within the same test, which was also causing a TypeError. I have corrected that in 6a018d5. So thanks for helping me find that as well! ;)
Let me know if you find anything else!


Subcomponent unmounts on changing data

What version of React-Table are you using?
6.7.6
What bug are you experiencing, or what feature are you proposing?
I'm not sure I'd call it a bug, but I have a subcomponent that hosts a form that allows you to change the data server-side. When the client updates, the subcomponent unmounts, which is undesired behavior. I think this can be resolved by manually providing a key to the table's row
Minimal reproduction
https://codesandbox.io/s/zky7m7vl0l
What are the steps to reproduce the issue?

Open up a subcomponent
Click "upd8"
Watch as the subcomponent disappears!

Apologies if this is actually already addressed somewhere... There's a lot of documentation, so I may have missed it. I looked through all of it and didn't see anything I found relevant.

Looks like freezeWhenExpanded works, but it doesn't really solve my problem because I would actually like the data to update without unmounting the subcomponent.

Does something like collapseOnDataChange fix your problem?

I quickly checked your example and collapseOnDataChange={false} does work.
Closing this.

@gary-menzel This is not working for me in version 6.8.6, collapseOnDataChange={false} is in place on the parent table and as a SubComponent i have a container component that triggers an async fetch that retrieves records from the back-end and changes SubComponent props...
The result is infinit ComponentDidMount calls on the SubComponent which leads me to think that the SubComponent is constantly unmounted and re-mounted. Code:
<CheckboxTable
                  className={classnames('-striped -highlight', { disabled: loading })}
                  columns={columns(props)}
                  collapseOnDataChange={false}
                  collapseOnSortingChange={false}
                  data={records.toArray()}
                  defaultPageSize={10}
                  filterable
                  loading={loading}
                  LoadingComponent={TableLoader}
                  manual
                  NoDataComponent={NoDataComponent}
                  noDataText={loading ? '' : I18n.t('table.no-data', { model: I18n.t('models.product.model_name', { count: 0 }) })}
                  onFilteredChange={debounce(props.onFilteredChange, 700)}
                  onPageChange={props.onPageChange}
                  onPageSizeChange={props.onPageSizeChange}
                  onSortedChange={props.onSortedChange}
                  sorted={sort}
                  SubComponent={row => {
                    const Consumables = ConsumablesContainer(row.original.id)
                    return <Consumables product={row.original} />
                  }}
                  {...paginationConfig(pagination)}
                  {...props.checkboxProps}
                />

SubComponent
class ConsumablesContainer extends Component {
    static propTypes = {
      fetchRecords: PropTypes.func.isRequired,
      loading: PropTypes.bool,
      product: PropTypes.object.isRequired,
      updateRecord: PropTypes.func.isRequired
    }

    static defaultPropTypes = {
      loading: false
    }

    componentDidMount () {
      this.props.fetchRecords(this.props.product.id)
    }

    onUpdateConsumable = (consumableId, values) => {
      return this.props.updateRecord(consumableId, values).then((res) => {
        if (!res.error) {
          toastr.success(I18n.t(`views.consumables.edit.toastr.success.title`))
        } else {
          toastr.error(I18n.t(`views.consumables.edit.toastr.error.title`), I18n.t(`views.consumables.edit.toastr.error.message`))
          throw new SubmissionError(toReduxFormErrors(res.payload.response))
        }
      })
    }

    render () {
      return (
        <Consumables {...this.props}
          onUpdateConsumable={this.onUpdateConsumable} />
      )
    }
  }


Coasting planes don't get deleted sometimes

Not sure what's going on here. Planes get marked as coasting but never deleted. Restarting the server works and they coast again. Maybe it's caching set somewhere?

Seems to happen when you connect a client after it's been a long time (and there are a LOT of updates to apply).

It's because the default in the production deployment compose file is 5 minutes instead of 2 like I thought. Doh.


[BUG] Dialog Box unexpectedly close when Toaster auto close timer run out

Describe the bug
When Dialog and Toaster are open together. Auto close toaster force dialog to close too.
To Reproduce

Having a Dialog and Toaster open together.
Wait until Toaster automatically close
Dialog will be force close together with Toaster

Expected behavior

Toaster should close without effecting Dialog Box

Desktop

OS: Window
Browser: Chrome

Can you provide the TSX/JSX for this issue?

Sorry for the late reply here's the link to the stackblitz replica of the part I found the bug
https://stackblitz.com/edit/stackblitz-starters-vegkfd?file=app%2Fcomponents%2FConfirmDialog.tsx
Setup Step:

cd app
npm I

Step to reproduce:

click on either button on the datatable, this will open a Dialog or open and AlertDialog for CONFIRM
click on any button at the DialogFooter, this will close the Modal and open a Toast
before Toast disappear, click on any of the button on the datatable again.
wait until the toaster timer run out for it to disappear, this will close the toast and also the Dialog

I have the same problem. Toast on closing also closes the Dialog and DropDownMenu :/

Facing similar issue with Sheet component and Toast. Whenever Toast is auto closing, it closes Sheet component too. If anyone has any workaround for this kindly share.

I have a similar issue, when I click close icon on the toast, the dialog also closes.

Same issue with Sheet and Toast.
Is there a way to make them work together?

I fixed it by removing all const { toasts } = useToast(); from the code (except the one from component itself) and use toast exported by use-toast.ts . If you use <Toaster /> in Layout as docs suggest - const { toasts } = useToast(); is already called there (and toast's state is initialized) - so toast will work globally.
The problem with calling useToast() inside components - I think it can trigger rerender and child dialog closing

I had this issue, a portion of the page refreshed when calling toast(), and when it got dismissed.
Fixed by using @lefelys suggestion, removed
import { useToast } from "@/components/ui/use-toast"
//...
const { toast } = useToast()

and instead used the toast object from
import { toast } from "@/components/ui/use-toast"

I have the same problem

Shadcn provides another toast component, sonner, that can replace this toaster. It fixes the problem mentioned above.

Thanks for your reply, but I have another question. When I use sonner , the color of sonner's status such as success or error is not shown.Do I need to set something up in sonner?

that would be the correct default behavior  for sonner toaster, add richColors to the Toaster props and you it should enable color. see the official documentation for more info https://sonner.emilkowal.ski/

i have the same problem

I had this issue, a portion of the page refreshed when calling toast(), and when it got dismissed.
Fixed by using @lefelys suggestion, removed
import { useToast } from "@/components/ui/use-toast"
//...
const { toast } = useToast()

and instead used the toast object from
import { toast } from "@/components/ui/use-toast"

A portion on my page is refreshes too and its super annoying.

Hi
I have the same problem when using Toast inside Sheet. I also tried to replace useToast with toast from "@/components/ui/use-toast" but it not working for me.

I solved this problem by follow:
https://github.com/radix-ui/primitives/issues/2690#issuecomment-1945449832
In sheet.tsx add onPointerDownOutside
onPointerDownOutside={(e) => {
        // don't dismiss dialog when clicking inside the toast
        if (
          e.target instanceof Element &&
          e.target.closest('[data-sonner-toast]')
        ) {
          e.preventDefault();
        }
        // if you are wrapping this component like shadcn, also call the caller's onPointerDownOutside method
        // onPointerDownOutside?.(e);
      }}

And in toaster.tsx, add data-sonner-toast.

I just migrated all toasts with sonner component. Work fine and sonner is better than toast for me.

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.

I had this issue, a portion of the page refreshed when calling toast(), and when it got dismissed.
Fixed by using @lefelys suggestion, removed
import { useToast } from "@/components/ui/use-toast"
//...
const { toast } = useToast()

and instead used the toast object from
import { toast } from "@/components/ui/use-toast"

A portion on my page is refreshes too and its super annoying.
And replacing custom hook with import didn't solved the issue

I recently encountered this issue too, and after some troubleshooting, I found that the key to fixing it was removing all instances of:
const { toast } = useToast()

in the components that were causing the page to refresh unexpectedly.
The solution wasn’t immediately obvious because I had multiple nested components, and removing the hook from just one component didn’t resolve the issue.
Instead, I kept only the one toast import that’s exported from use-toast.ts:
import { toast } from "@/components/ui/use-toast"

Once I removed the other instances of useToast(), the page refresh issue stopped, and everything worked as expected.


compose-app-handson: Adding Tutorial

Docs for f88e419647a1c00bd33b755b5e209bfd68d1e1b9 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/894/docs/artifacts/html/index.html

Is there any reason this can't be merged? I need it in master so I can rebase #218.

Docs for 424becbbd0b5c84bedcc02f5e67b586ecd66242e are browesable at: https://ci.foundries.io/projects/fio-docs/builds/919/docs/artifacts/html/index.html

Docs for c38930e9fe6bb5a9061d255f2a2a3cb7386ff391 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/926/docs/artifacts/html/index.html

Docs for 35fc832c39969d30e83311e1f90b6a2f75577308 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/934/docs/artifacts/html/index.html

Docs for afaf15c13d70e94895a6eaaeef39be38a43bbf6f are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1003/docs/artifacts/html/index.html

@mike-scott, I just synced it with the latest fio master and tested it again. I think this is a very important one once Switch-EV could use it to get started with FF.

Docs for 927e73faca6050a94d97a3706e8a587caac23500 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1025/docs/artifacts/html/index.html

Docs for c83716611794d04cc0138f4958f176c4b9f64232 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1027/docs/artifacts/html/index.html

Docs for af5d8ac3b53e12a6352001ad50e243b240575da2 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1038/docs/artifacts/html/index.html

Docs for dda089ffb9279faacdab359ef5621cfcdd019278 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1039/docs/artifacts/html/index.html


SchemaMigrator/SchemaValidator - add tests for corner cases

There are some corner cases that are covered by ORM tests. They should be migrated to Reactive to make sure they work properly.
Here are some ORM SchemaMigrator tests that should be reviewed for possible inclusion in Hibernate Reactive:
SchemaUpdateTableBackedSequenceTest
CrossSchemaForeignKeyGenerationTest
UniqueConstraintDropTest
MySQLDropConstraintThrowsExceptionTest
SchemaMigrationTargetScriptCreationTest
SchemaMigrationToOutputScriptTest     -> @RequiresDialect(H2Dialect.class)
SchemaMigratorHaltOnErrorTest        -> skip DB2 & Derby
SchemaUpdateProceedOnErrorTest
SchemaUpdateSchemaNameTest     ->  @RequiresDialect(MySQL5Dialect.class)

Here are some ORM SchemaValidator tests that should be reviewed for possible inclusion in Hibernate Reactive:
LongVarcharValidationTest
NumericValidationTest
GroupedSchemaValidatorImplTest       -> @RequiresDialect(H2Dialect.class)
IndividuallySchemaValidatorImplConnectionTest       -> @RequiresDialect(H2Dialect.class)
IndividuallySchemaValidatorImplTest       -> @RequiresDialect(H2Dialect.class)
SchemaToolTransactionHandlingTest

I don't think they all need to be added. I'll take a look at these and see which ones we need.

I think we cover these cases, we will fix errors when they present themselves


Fix Table for Contrast React Bootstrap SidebarCTA Props

There was an extra Line which caused the Table to show the last Line in it.

bump

Great catch @jnthn-b . Thanks for updating!


Communication Content Validation Issue for github.io website

Section link1, link2, link3, link4, link5, link6, link7, link8, link9, link10:

Format validation issue: Extra symbols _.

Section link1:

link2, link3, link4, link5, link6, link7, link8
Reason:
Format validation issue: Extra symbols - or ~.(Note: Multiple occurrences)

Section link1:

link2, link3, link4, link5, link6, link7, link8
Reason:
Format validation issue: Text exceeds page size.

Section link1:

link2:

link3:

link4:

link5:

link6:

Reason:
Link validation issue: Target Link Service not match.

Section link1:

link2:

link3:

link4, link5, link6, link7
Reason:
Typing annotation issue: Please unify the format, update to **kwargs:Any or **kwargs.(Note: Multiple occurrences).

Section link1:

link2, link3
Reason:
Typing annotation issue: Please unify the format, update to *args:Any, **kwargs:Any or *args, **kwargs.(Note: Multiple occurrences)

Section link:

https://azuresdkdocs.blob.core.windows.net/$web/python/azure-communication-administration/1.0.0b4/azure.communication.administration.html#azure.communication.administration.CommunicationUser

Reason:
Typing annotation issue: Missing type annotation for identifier and value.
@rohit-ganguly, @lmazuel, @lfraleigh, @mayurid for notification.

Close this issue as we'll put it into a summarzied one.


New approach to peer config

Make peer config independent of the network instance as it might be that the peer is not configured on the NF.
In this proposal the peerconfig is a list of peers:

the name represent the name of the peer
the labels can be used as metadata for additional information on the peer, like NF, location, etc
The network Instance is still there if this information is relevant for the peer.

@s3wong could you have a look at this?

@henderiw

@s3wong could you have a look at this?

I still have question on how do we get to the N3 IP address from SMF controller?
So SMF controller is supposed to get a list of PeerConfig --- each of them representing a UPF?
And the attachment is N4, so the Peers[i].IPv4 will contain to N4 IP address
How do we get to the N3 on this peer UPF? I noticed you added Labels and NetworkInstance, not sure if either is useful. What is your plan on how we (operator team) can use these fields?

@s3wong
So the way this is supposed to work is this.
Lets assume we have 2 upf(s) : 1 on edge1 and 1 on edge2.
The smf package is augmented with the UPF with the additional IPAllocation objects:

important is the query annotation

UPF-edge1: this info should be available in the topology + fanout -> sites info you get from topology, network-instance from top and kind you could get from interface (I can provide the logic for that as this is also used in if-fn).
IPAllocation query for UPF on edge1
apiVersion: ipam.alloc.nephio.org/v1alpha1
kind: IPAllocation
metadata:
name: n3
annotations:
specializer.nephio.org/query: true
spec:
kind: network
selector:
matchLabels:
nephio.org/site: edge1
networkInstance:
name: vpc-ran
apiVersion: ipam.alloc.nephio.org/v1alpha1
kind: IPAllocation
metadata:
name: n4
annotations:
specializer.nephio.org/query: true
spec:
kind: network
selector:
matchLabels:
nephio.org/site: edge1
networkInstance:
name: vpc-internal
Same for UPF on edge2
IPAllocation query for UPF on edge1
apiVersion: ipam.alloc.nephio.org/v1alpha1
kind: IPAllocation
metadata:
name: n3
annotations:
specializer.nephio.org/query: true
spec:
kind: network
selector:
matchLabels:
nephio.org/site: edge2
networkInstance:
name: vpc-ran
apiVersion: ipam.alloc.nephio.org/v1alpha1
kind: IPAllocation
metadata:
name: n4
annotations:
specializer.nephio.org/query: true
spec:
kind: network
selector:
matchLabels:
nephio.org/site: edge2
networkInstance:
name: vpc-internal
During specialization we use this information to resolve the IP(s) that were allocated to these UPFs.
The nf-deploy function add this information in the SMFdeployment.
peers:

name: n3
labels:
nephio.org/site: edge1
network-instance:
name: vpc-ran
ipv4:
address: <IP_ADDRESS>/24
gateway: <IP_ADDRESS>
name: n4
labels:
nephio.org/site: edge1
network-instance:
name: vpc-internal
ipv4:
address: <IP_ADDRESS>/24
gateway: <IP_ADDRESS>
name: n3
labels:
nephio.org/site: edge2
network-instance:
name: vpc-ran
ipv4:
address: <IP_ADDRESS>/24
gateway: <IP_ADDRESS>
name: n4
labels:
nephio.org/site: edge2
network-instance:
name: vpc-internal
ipv4:
address: <IP_ADDRESS>/24
gateway: <IP_ADDRESS>

@s3wong @tliron could you please check if this is OK to be merged so that I can use it for SMF CRDs generation
cc// @henderiw

To understand the (free5gc) SMF config for this, the layout is:

  userplaneInformation: # list of userplane information
    upNodes: # information of userplane node (AN or UPF)
      UPF:  # the name of the node
        type: UPF # the type of the node (AN or UPF)
        nodeID: <IP_ADDRESS> # the IP/FQDN of N4 interface on this UPF (PFCP).  <---- N4 IP for UPF

[snip]
interfaces: # Interface list for this UPF
- interfaceType: N3 # the type of the interface (N3 or N9).
endpoints: # the IP address of this N3/N9 interface on this UPF
- <IP_ADDRESS>                                                       <---- N3 IP for UPF
So, logically, we group by peer NF, and identify the connected point (N4 IP on the connected UPF in this case), and N3 and N9 IP addresses under that one UPF

Even ignoring free5gc's needs, the structure of "peer" is the peer NF connected, or even pointed to via "n4", but SMF has NO "n3", "n9"...etc, and the logical structure should be "name of my neighbor NF", then "the IP we are connected", and "all the other interfaces and IPs on this peer". This is much more structural than what is proposed here. If the SMF is connected to a bunch of UPFs, and all of them reports "n3", then on the operator side we are extracting all the "n3"s first and THEN internally grouping them under a peer? This seems to make parsing a lot more convoluted.

Package specialization modules get topology information from NFTopology, and NFTopology also starts from NFInstance before browsing through the attachments... so I am not sure this way to organize peers would help even at that level.

in specialisation we do not get topology, since a package it per NF. What we agreed is we get a request for an IP. So what is proposed here is a list with the info. The receiving end just have to go through it to provide the structure. I believe not everyone need this structure and seems specific to the free5gc. I don't want to build just for free5gc.
So here we just need to run through the list and get the info but the structure how you consume it is the job of the receiver


Ensure stdout/stderr are logged when using debug mode logging.

Relates to gh-1600.
As you can see in the changes, if javaexec were to exit with a return code of 1 an exception was raised and the stdout/stderr that we may have collected during debug logging would have been lost. By usage of the finally block we can now ensure that the stdout/stderr from the different forked processes we will create can be captured for debugging information.

@marcingrzejszczak, just to make sure that it's clear this just cleans up the debug output, so that getting to the exception listed in the linked ticket will be easier in the future (eg: the stdout/stderr isn't gobbled up and thrown away).
Given the real issue with the linked ticket is that the kotlin-scripting-compiler-embeddable fell out of sync with the overall project's Kotlin version, there's not really anything that I think we can do from a SC-contract standpoint given the finicky nature of Kotlin itself (as illustrated).
Just wanting to make sure that it's clear that this isn't "fixing" that issue, but making the discrepancy easier to identify. wdyt?

Makes sense @shanman190


can't access contraller with docker-1.12.6 on centos7.3

hi all :
i'm install docker on centos7.3 with yum . docker version is 1.12.6, and i used auto deploy method to install shipyard ,when done, can't access web contraller .
setlinux is enforcing , firewalld is off , iptables is running.
that's some infomation:
[root@localhost ~]# docker exec -it shipyard-controller /bin/sh
/ # ps aux
PID   USER     TIME   COMMAND
1 root       0:00 /bin/controller --debug server --listen :8080 -d tcp://swarm:3375
11 root       0:00 /bin/sh
17 root       0:00 ps aux
/ # netstat -tnlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
/ #
anybody can help me ?
thanks ...

i resolve this question.
step:
vi /etc/resolv.conf
set dns:
nameserver <IP_ADDRESS>
deploy again.


Use ExceptT instead of ErrorT and update for GHC 7.10

I'm submitting this as one PR so you don't have to deal with the merge conflicts, but the changes are available separately on the nathan:mtl-except and nathan:ghc710 branches.

@nathan, I think the imports from Control.Applicative need to be left in so the code can continue compiling on ghc-7.6 and ghc-7.8.
Maybe you could use CPP macros like described here for checking whether or not it's being compiled with ghc-7.10.

Everything has been updated in the warnings branch, which will get merged into master soon. I need to fix a couple more things first, but it's on the way!


CSS animations

Hi there. Has anyone else reported that animations aren't playing out propely when contained in react-responsive?
I commented on issue 81 (https://github.com/contra/react-responsive/issues/81) about bootstrap Navbar animation not working but it seems ALL my css animations aren't working. They should the start and end state but not the frames in between.
Maybe I am missing something?

Closing, no response.


feat(v2): Support swizzling TypeScript components

Motivation
In #2470, I discussed my plan to implement support for TypeScript theme components. In the original issue theme, one concern of a maintainer is that people might not want TypeScript components. To address that concern, we must maintain the ability to emit JavaScript code when swizzling.
My proposal is to use babel to strip away type annotations in TypeScript components, and make swizzle still emit JS by default, but make swizzle emit TS when --typescript flag has been passed. This pull request implements this proposal.
Implementation Notes
Generating JS theme components from TS theme components
I did a proof-of-concept implementation in #2614. I found that the JS code emitted by Babel doesn't respect the original code style. There is an easy fix: we run prettier on those babel-generated files, so that we get back our original style.
Swizzling Strategy
To support swizzling TS components, an optional getTypeScriptThemePath() method is added to the plugin API. It's not used for module resolution, but purely for swizzling. If --typescript flag is added, then swizzling will read from getTypeScriptThemePath() instead and fallback to getThemePath() if getTypeScriptThemePath() is undefined.
Type Checking
Since JS code is generated by Babel, the TS theme code won't be type checked. Currently, there are some type errors in the code, but as you can see it doesn't block you from launching the website. I will fix these errors once the maintainer thinks the general strategy is good.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots and videos!)

Run yarn workspace docusaurus-2-website swizzle @docusaurus/theme-classic --typescript, you will see the entire packages/docusaurus-theme-classic/src/theme folder is copied to website/src/theme.
Run yarn workspace docusaurus-2-website swizzle @docusaurus/theme-classic, you will see the entire packages/docusaurus-theme-classic/src/theme folder is copied to website/src/theme, except that all the TS files are replaced by their corresponding JS code.
Run yarn workspace docusaurus-2-website swizzle @docusaurus/theme-classic NotFound --typescript, you will see a website/src/theme/NotFound.tsx
Run yarn workspace docusaurus-2-website swizzle @docusaurus/theme-classic NotFound, you will see a website/src/theme/NotFound.js
Run yarn workspace docusaurus-2-website swizzle @docusaurus/theme-classic TabItem --typescript, you will see a website/src/theme/TabItem/index.tsx
Run yarn workspace docusaurus-2-website swizzle @docusaurus/theme-classic TabItem, you will see a website/src/theme/TabItem/index.js

Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

Your implementation looks good to me, thank you @SamChou19815!

@yangshun @lex111 @slorber I updated the implementation to make swizzle TS components rely on less hacky methods. I would like to get your thoughts before fixing the last few devx issues.

Hey,
That's really great, I really hope to work in theme with TS soon :)
Also had this similar idea to use Babel, but thought about using babel at swizzle time without reusing the /lib js output.
Was wondering, is the babel compiled code of /lib readable enough?
Because as they'll serve as source file for the user, it should be easy to modify them.
For example, it can be annoying if the swizzled file has common-js and Object.assign() instead ES imports/exports and spread? (didn't try in theme classic, but it seems to be the case in other plugins)
According to the webpack config, all our packages + swizzled comps will be transpiled anyway
export function excludeJS(modulePath: string): boolean {
  // always transpile client dir
  if (modulePath.startsWith(clientDir)) {
    return false;
  }
  // Don't transpile node_modules except any docusaurus npm package
  return (
    /node_modules/.test(modulePath) &&
    !/(docusaurus)((?!node_modules).)*\.jsx?$/.test(modulePath)
  );
}

Maybe we could try to see if our TS compilation process (via tsc) can output more modern ES code?

Didn't find much informations on the advantages of tsc vs babel ts preset, but I think we should rather stick to tsc for now, just to keep the setup uniform, and maybe migrate later.
Also I think things like incremental compilation works better in tsc. But maybe we have more options to control the output JS with babel?
Hard to find quality information on this...

@slorber

Maybe we could try to see if our TS compilation process (via tsc) can output more modern ES code? Keeping newest ES features instead of downgrading them.
The idea for me would be that swizzling a theme classic comp today should give the same output as tomorrow when theme classic will be written in TS (or quite similar).

TS can be configured to produce nice ES code, but the biggest blockers is that it doesn't preserve empty lines. See https://github.com/microsoft/TypeScript/issues/843 (And you can see a real example in the compiled packages/docusaurus/lib/client/exports/ComponentCreator.js)

Also had this similar idea to use Babel, but thought about using babel at swizzle time without reusing the /lib js output.

It means we need to bundle babel, which might not be a big problem since we already included babel in docusaurus core. But to have a more readable code I also automatically run prettier after babel, then we also need to bundle prettier...

Was wondering, is the babel compiled code of /lib readable enough?

Yes, here is an example of the compiled CodeBlock
/**
 * Copyright (c) Facebook, Inc. and its affiliates.
 *
 * This source code is licensed under the MIT license found in the
 * LICENSE file in the root directory of this source tree.
 */

/* eslint-disable jsx-a11y/no-noninteractive-tabindex */
import React, {useEffect, useState, useRef} from 'react';
import clsx from 'clsx';
import Highlight, {defaultProps} from 'prism-react-renderer';
import copy from 'copy-text-to-clipboard';
import rangeParser from 'parse-numeric-range';
import useDocusaurusContext from '@docusaurus/useDocusaurusContext';
import usePrismTheme from '@theme/hooks/usePrismTheme';
import styles from './styles.module.css';
const highlightLinesRangeRegex = /{([\d,-]+)}/;

const getHighlightDirectiveRegex = (
  languages = ['js', 'jsBlock', 'jsx', 'python', 'html'],
) => {
  // supported types of comments
  const comments = {
    js: {
      start: '\\/\\/',
      end: '',
    },
    jsBlock: {
      start: '\\/\\*',
      end: '\\*\\/',
    },
    jsx: {
      start: '\\{\\s*\\/\\*',
      end: '\\*\\/\\s*\\}',
    },
    python: {
      start: '#',
      end: '',
    },
    html: {
      start: '',
    },
  }; // supported directives

  const directives = [
    'highlight-next-line',
    'highlight-start',
    'highlight-end',
  ].join('|'); // to be more reliable, the opening and closing comment must match

  const commentPattern = languages
    .map(
      (lang) =>
        `(?:${comments[lang].start}\\s*(${directives})\\s*${comments[lang].end})`,
    )
    .join('|'); // white space is allowed, but otherwise it should be on it's own line

  return new RegExp(`^\\s*(?:${commentPattern})\\s*$`);
}; // select comment styles based on language

const highlightDirectiveRegex = (lang) => {
  switch (lang) {
    case 'js':
    case 'javascript':
    case 'ts':
    case 'typescript':
      return getHighlightDirectiveRegex(['js', 'jsBlock']);

    case 'jsx':
    case 'tsx':
      return getHighlightDirectiveRegex(['js', 'jsBlock', 'jsx']);

    case 'html':
      return getHighlightDirectiveRegex(['js', 'jsBlock', 'html']);

    case 'python':
    case 'py':
      return getHighlightDirectiveRegex(['python']);

    default:
      // all comment types
      return getHighlightDirectiveRegex();
  }
};

const codeBlockTitleRegex = /title=".*"/;
export default ({children, className: languageClassName, metastring}) => {
  const {
    siteConfig: {
      themeConfig: {prism = {}},
    },
  } = useDocusaurusContext();
  const [showCopied, setShowCopied] = useState(false);
  const [mounted, setMounted] = useState(false); // The Prism theme on SSR is always the default theme but the site theme
  // can be in a different mode. React hydration doesn't update DOM styles
  // that come from SSR. Hence force a re-render after mounting to apply the
  // current relevant styles. There will be a flash seen of the original
  // styles seen using this current approach but that's probably ok. Fixing
  // the flash will require changing the theming approach and is not worth it
  // at this point.

  useEffect(() => {
    setMounted(true);
  }, []);
  const button = useRef(null);
  let highlightLines = [];
  let codeBlockTitle = '';
  const prismTheme = usePrismTheme();

  if (metastring && highlightLinesRangeRegex.test(metastring)) {
    const highlightLinesRange = metastring.match(highlightLinesRangeRegex)[1];
    highlightLines = rangeParser
      .parse(highlightLinesRange)
      .filter((n) => n > 0);
  }

  if (metastring && codeBlockTitleRegex.test(metastring)) {
    codeBlockTitle = metastring
      .match(codeBlockTitleRegex)[0]
      .split('title=')[1]
      .replace(/"+/g, '');
  }

  let language =
    languageClassName && languageClassName.replace(/language-/, '');

  if (!language && prism.defaultLanguage) {
    language = prism.defaultLanguage;
  } // only declaration OR directive highlight can be used for a block

  let code = children.replace(/\n$/, '');

  if (highlightLines.length === 0 && language !== undefined) {
    let range = '';
    const directiveRegex = highlightDirectiveRegex(language); // go through line by line

    const lines = children.replace(/\n$/, '').split('\n');
    let blockStart; // loop through lines

    for (let index = 0; index < lines.length; ) {
      const line = lines[index]; // adjust for 0-index

      const lineNumber = index + 1;
      const match = line.match(directiveRegex);

      if (match !== null) {
        const directive = match
          .slice(1)
          .reduce((final, item) => final || item, undefined);

        switch (directive) {
          case 'highlight-next-line':
            range += `${lineNumber},`;
            break;

          case 'highlight-start':
            blockStart = lineNumber;
            break;

          case 'highlight-end':
            range += `${blockStart}-${lineNumber - 1},`;
            break;

          default:
            break;
        }

        lines.splice(index, 1);
      } else {
        // lines without directives are unchanged
        index += 1;
      }
    }

    highlightLines = rangeParser.parse(range);
    code = lines.join('\n');
  }

  const handleCopyCode = () => {
    copy(code);
    setShowCopied(true);
    setTimeout(() => setShowCopied(false), 2000);
  };

  return (
    <Highlight
      {...defaultProps}
      key={String(mounted)}
      theme={prismTheme}
      code={code}
      language={language}>
      {({className, style, tokens, getLineProps, getTokenProps}) => (
        <>
          {codeBlockTitle && (

              {codeBlockTitle}

          )}

            <button
              ref={button}
              type="button"
              aria-label="Copy code to clipboard"
              className={clsx(styles.copyButton, {
                [styles.copyButtonWithTitle]: codeBlockTitle,
              })}
              onClick={handleCopyCode}>
              {showCopied ? 'Copied' : 'Copy'}
            </button>

                {tokens.map((line, i) => {
                  if (line.length === 1 && line[0].content === '') {
                    line[0].content = '\n'; // eslint-disable-line no-param-reassign
                  }

                  const lineProps = getLineProps({
                    line,
                    key: i,
                  });

                  if (highlightLines.includes(i + 1)) {
                    lineProps.className = `${lineProps.className} docusaurus-highlight-code-line`;
                  }

                  return (

                      {line.map((token, key) => (

                      ))}

                  );
                })}

        </>
      )}
    </Highlight>
  );
};

Thanks, that looks readable :)
Asked the question on twitter and getting some interesting answers: https://twitter.com/sebastienlorber/status/1275067106254393347
Seems like Babel might be faster to build and provide more flexibility on output. Some recommend TSC but without strong arguments apart being more easy to setup (not sure I agree anyway).

It means we need to bundle babel

You mean bundle in the swizzle cli? I'm not sure it's a big deal but if we can avoid that's not bad either.

What bothers me is that we use tsc on all others projects and that this one will be the only one using Babel. I really like babel + TSC, but when I use it I use it everywhere, and also run tsc --noEmit on the side for typechecking.
Can this serve as a poc, eventually leading to migrating other projects from tsc to babel?
Or are we going to stay with tsc + babel?

Also something to consider: do we need to emit typedefs for the theme?
What's the story, when a TS user wants to override a theme component, importing original theme components with the aliases?
Like import Footer from '@theme-original/Footer'

What bothers me is that we use tsc on all others projects and that this one will be the only one using Babel. I really like babel + TSC, but when I use it I use it everywhere, and also run tsc --noEmit on the side for typechecking.

I do plan to add tsc --noEmit once I finished everything. It's not added for now because things don't type check at the moment.

Also something to consider: do we need to emit typedefs for the theme?

This is on my future plan. Actually that's one of the reasons why I'm very passionate about this PR.

Everything passes the type checker. I think it's good for review now.

Hey @SamChou19815 , the classic theme conversion to TS looks great to me and seems ready to merge (just did a few subjective TS suggestions).
About the swizzling experience, I tried to see what would be the experience of an user trying to use TS on his docusaurus site, so I tried: yarn workspace docusaurus-2-website swizzle @docusaurus/theme-classic Footer --typescript
The swizzling did work fine but the experience wasn't so great, because I ended up with IDE errors in D2 website project 🤪

What do you think about splitting your work in multiple PRs to make it simpler to review/merge?

convert theme to TS (this part seems ready to merge)
ability to easily swizzle ts + dogfood some TS on D2 website + try to import things like '@theme-original/Footer'
support TS in docusaurus-init so that it's easy to start a D2 TS-based website?

The swizzling did work fine but the experience wasn't so great, because I ended up with IDE errors in D2 website project

It turns out it's very easy to fix. I just added tsconfig.json and types.d.ts that refers to the @docusaurus/module-type-aliases to unbreak IDE experience. Let me know if it's good.

Added declare module '@theme-original/*';. Not sure what's happening in github actions. The same command can run smoothly yesterday.


Aliasing affects assignability of indexed mapped types

🔎 Search Terms
type alias, interface, assignability, indexed access type, mapped type
🕗 Version & Regression Information

The core issue has existed in every version I tried since 3.3.
Before 4.2, indirect type aliases worked while indirect interfaces did not.
In 4.2, both produced errors.
Since 4.3, indirect type aliases give errors, but indirect interfaces do not.

⏯ Playground Link
https://www.typescriptlang.org/play/?ts=5.6.3#code/C4TwDgpgBAyg9gVwE4GMIGkIigXigZ2CQEsA7AcwChRIoAVAQyXImE2zwCJgJDPLq4aADUGAGwTQ8CUgGtScAO6kBNaAFkQAJQgo4SACYAedFAgAPHqQP4osrHABmUBqRAA+XFADeUANoAClBkUOgAugBcUKIS0AC+grSaAPLAABYQSDp6hiZmlhDWtvYgTi5unni+gcGkoZHR4pJQCZQGumJM0HqkhASIqBAA+uLEDPgQBlGa2frG8Mho7O5tHV1QPX34A2gjYmMTBkNw6ZnTIKkZWbpzRguDy6sonUjdcL3A-YvDALYMYJApj5-EEQvcllgGjFmgl2s91ptPttvkMyO1zJMotUAlFwRhIVFofEBGQeEhHAw0FAAJLWYivFDAWlkilUixWGxQGY3XKMZisZY+BJqGl0hnAACC+3GXm5OWMfJYbCwK0opMyrOgtIM9N0TNILMpEEumXyHNsKVO13lRkVApVQsSWrFeqlBxNSFlFyts15TCVjyeL2gYlYUGA-tYewOkyGOvF519Csjyo8QfWoc+Ef5wGj41j8b1xyt5w9SdtKcecODUEz4ZTecOqJdjMbUW1usZbvG6detbD2aVjdjaM7udG42LV3bLcl0vwHt7IYHDYnTdH4ubhrQM8LjOZGqNS-7WdX85Hs63h92J2nor3+u3xqtx7rg6jfwBmOBNRCdtTUJNMS1YZiuOZDPsZLiFi4a8MAhJAS0qhnjGRwPl4yKDMOBhQAA9LhUDJOg1AofmaFjhhOzDGusa3pkJHgTR5HipRKKfoCDFDkxcYUXgmG7GiFiTMhjHnsxRZ0Z6fFUdhnFRtxD5Tqa0kotxkl4QRRFyeOYk8Zu6kqVh7HCe+OmoXpElWqxWGCRiBgiVxukbkWa7WbsTHadhzaKa5hnubpkmedxzmtr5XxGf8HGmV5IVmTKfnDLZwlBU5l5rkpUnhf5qEpeZsWNhlbnUQFL7RcFaXzoVCVDMZ9llalPmVQZWWJdYQn2blZHeWOV7kkaRXYRphHEfVeWXuqfVUtVamlaR67jQa15SC1NWRSZc0XopE2agNSUdaNXX5dtRpVStHkHfNW2LZNwzNfxxXmep+HDZ1l09cdN5WdVtWvZt73XZqp33d57UOR+a04dNYmebVA0zVcMMQwNP3RbD1V7WDuaQZk4hw9D0XY0guNQ49s3gYTxMrSjDYU2Iu1tXZlBAA
💻 Code
Simple example:
type F<T> = T extends Record<"test", unknown> ? true : false

type A = Record<string, unknown>
type t1 = F<A>
//   ^? type t1 = false

type t2 = F<Record<string, unknown>>
//   ^? type t2 = true

Assignability testing:
type SourceKey = string
type TargetKey = "test"

type Value = unknown

type MyRecord<K extends keyof any> = { [P in K]: Value }
type MyOtherRecord<K extends keyof any> = { [P in K]: Value }

declare const source_aliased: MyRecord<SourceKey>
declare const source_aliased_other: MyOtherRecord<SourceKey>
declare const source_mapped: { [P in SourceKey]: Value }
declare const source_indexed: { [P: SourceKey]: Value }

interface IndirectInterface extends MyRecord<TargetKey> {}
type IndirectAlias = MyRecord<TargetKey>

interface IndirectInterfaceOther extends MyOtherRecord<TargetKey> {}
type IndirectAliasOther = MyOtherRecord<TargetKey>

declare let target_aliased_direct: MyRecord<TargetKey>
declare let target_aliased_direct_other: MyOtherRecord<TargetKey>
declare let target_aliased_indirect_alias: IndirectAlias
declare let target_aliased_indirect_alias_other: IndirectAliasOther
declare let target_aliased_indirect_interface: IndirectInterface
declare let target_aliased_indirect_interface_other: IndirectInterfaceOther
declare let target_mapped: { [P in TargetKey]: Value }
declare let target_literal: { test: Value }

target_aliased_direct = source_aliased // OK
target_aliased_direct = source_aliased_other
target_aliased_direct = source_mapped
target_aliased_direct = source_indexed

target_aliased_direct_other = source_aliased
target_aliased_direct_other = source_aliased_other // OK
target_aliased_direct_other = source_mapped
target_aliased_direct_other = source_indexed

target_aliased_indirect_alias = source_aliased
target_aliased_indirect_alias = source_aliased_other
target_aliased_indirect_alias = source_mapped
target_aliased_indirect_alias = source_indexed

target_aliased_indirect_alias_other = source_aliased
target_aliased_indirect_alias_other = source_aliased_other
target_aliased_indirect_alias_other = source_mapped
target_aliased_indirect_alias_other = source_indexed

target_aliased_indirect_interface = source_aliased // OK
target_aliased_indirect_interface = source_aliased_other
target_aliased_indirect_interface = source_mapped
target_aliased_indirect_interface = source_indexed

target_aliased_indirect_interface_other = source_aliased
target_aliased_indirect_interface_other = source_aliased_other // OK
target_aliased_indirect_interface_other = source_mapped
target_aliased_indirect_interface_other = source_indexed

target_mapped = source_aliased
target_mapped = source_aliased_other
target_mapped = source_mapped
target_mapped = source_indexed

target_literal = source_aliased
target_literal = source_aliased_other
target_literal = source_mapped
target_literal = source_indexed

🙁 Actual behavior
It seems that an indexed mapped type is only assignable to an object if each is either a direct instantiation of the same type alias or an interface extending from such an instantiation.
🙂 Expected behavior
I don't expect aliasing to affect assignability, nor do I expect such differences between type aliases and interfaces.
Additional information about the issue
No response

https://github.com/microsoft/TypeScript/issues/43374#issuecomment-807109391

https://github.com/Microsoft/TypeScript/wiki/FAQ#structural-vs-instantiation-based-inference
This is one of the few cases where it matters and you're not doing anything "wrong" per se. Depending on interpretation, the correct result is either.


Upscale x4

New Midjourney feature
Upscale x4
Maybe worth to add?

For sure, It is slow but will be fast in the future, for me would be nice to add it. I can help If you want! I am starting to code and these things are a little complex, I would love to learn more tho.


Support all YAML Camel EIP

Add support for all the EIP listed here:
https://camel.apache.org/camel-k/1.9.x/languages/yaml.html#_supported_eip

[ ] Aggregate
[x] Bean
[x] #129
[ ] Circuit Breaker
[ ] Claim Check
[ ] Convert Body To
[ ] Delay
[ ] Dynamic Router
[ ] Enrich
[x] https://github.com/KaotoIO/kaoto-backend/pull/137
[x] From
[ ] Idempotent Consumer
[ ] Load Balance
[ ] Log
[ ] Loop
[ ] Marshal - @Delawen is on it
[ ] Multicast
[ ] Pipeline
[ ] PollEnrich
[ ] Process
[ ] Recipient List
[x] https://github.com/KaotoIO/kaoto-backend/pull/148/
[ ] Remove Headers
[x] Remove Property
[ ] Remove Properties
[ ] Resequence
[ ] Rest DSL
[ ] Rollback
[ ] Routing Slip
[ ] Saga
[ ] Sample
[ ] Script
[ ] ServiceCall
[x] Set Body
[ ] Set Exchange Pattern
[x] Set Header
[x] https://github.com/KaotoIO/kaoto-backend/pull/131
[ ] Sort
[ ] Split
[ ] #124
[ ] Stop
[ ] Threads
[ ] Throttle
[ ] Throw Exception
[x] To
[ ] To Dynamic
[ ] Transacted
[x] https://github.com/KaotoIO/kaoto-backend/pull/132
[ ] Try Catch Finally
[ ] Unmarshal- @Delawen is on it
[ ] Validate
[ ] Wire Tap

Child: #124

I'd like to take transform and filter

I'd like an Oktoberfest shirt so I'll take a look to create one of those :)))). I'm still reading about EIPs so I'll think first before picking one. That there is some EIPs already merged is a big help to use them as an example

I think Aggregate would need some kind of DSL? It's heavily tied to having Aggregation Strategy java beans to execute it.
Maybe create some kind of mapper to tell how should stuff be agregated. Doing so is not hard, but it will be a bit of a deviation with camel.


Calling StorageHelper.listStorageAccounts method generates error: "SubscriptionNotFound" even though subscription does exist

I edited my local copy of ServicePrincipalExample with the relevant details and got it to run OK, however when I replaced the main code in ServicePrincipalExample with:
    	Configuration config = createConfiguration();
    	StorageManagementClient storageClient = StorageManagementService.create(config);
    	List<StorageAccount> storageAccounts = StorageHelper.listStorageAccounts(storageClient, null);
    	for (StorageAccount storAcc : storageAccounts) {
    		System.out.println(storAcc.getName());
    	}

I always get the following stacktrace:
Exception in thread "main" java.util.concurrent.ExecutionException: com.microsoft.windowsazure.exception.ServiceException: SubscriptionNotFound: Subscription e4002xxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx was not found.
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.util.concurrent.FutureTask.get(FutureTask.java:188)
	at com.microsoft.azure.utility.StorageHelper.listStorageAccounts(StorageHelper.java:186)
	at com.company.azure.auth.ServicePrincipalExample.main(ServicePrincipalExample.java:82)
Caused by: com.microsoft.windowsazure.exception.ServiceException: SubscriptionNotFound: Subscription e4002xxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx was not found.
	at com.microsoft.windowsazure.exception.ServiceException.createFromJson(ServiceException.java:290)
	at com.microsoft.azure.management.storage.StorageAccountOperationsImpl.list(StorageAccountOperationsImpl.java:1355)
	at com.microsoft.azure.management.storage.StorageAccountOperationsImpl$6.call(StorageAccountOperationsImpl.java:1284)
	at com.microsoft.azure.management.storage.StorageAccountOperationsImpl$6.call(StorageAccountOperationsImpl.java:1281)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)

The subscription does exist and my service principal has been granted the contributor role for the subscription. I've even added 'Classic Storage Account Contributor' as well as 'Storage Account Contributor' roles but they have had no effect.

I've granted the same Service Principal access to a more recently created Subscription (Contributor role), updated the subscription ID in the code and run it again. This time I don't receive an error but I don't get a list of storage accounts printed out either. The original block of code to print out the names of ResourceGroupExtended works though.

@jonbullock were the storage account created using Azure Resource Manager (the new portal) or were they created in Azure Service Management (the old portal)?

@devigned they were created using the Azure Service Management (the old portal).

@jonbullock the package we use in the example makes a request to Azure Resource Manager (com.microsoft.azure). The (com.microsoft.windowsazure) packages are Service Management based. This is terribly confusing, I know. We'll address this in an upcoming release.
Please make a storage account in the new portal and verify you can list it with the example.

@devigned Now I've created a storage account using the new portal my original code works.
I assumed that it didn't matter which portal I used to create the resources in, but I guess it does.

@jonbullock it's the disconnect between the V1 apis (Service management) and the V2 apis (Resource manager). It's pretty confusing. Stick to one, preferably V2, and you should be much happier.


Work Package wp-be.csv

I would like to work on this please!

Hi @XiaoLing941212 . Is there an update on this work package?

wp-be-results.txt
Results for phase 1.

I completed this work package.

I would like to work on this please!

I completed this work package.
i48.csv

@XiaoLing941212 Your file for phase 1 is using tabs for separators and currently cannot be processed. Could you recheck?

@bhermann updated result for this package
wp-be-results.csv.txt

@XiaoLing941212 You seem to have added a column called sect_num here. I will remove this column as it is not compatible with @afonsohfontes 's results. Please do not add columns or inform the next person of that fact so they don't produce an incompatible result.

Thanks for your work on this package. I included it into the repository. It will appear soon on the website.
I had only to correct some whitespaces in DOIs and Links. Watch out for those in the future. ;)


Add SDEProblem to StochSystem struct

It can be a good Idea to add the SDEProblem struct (used to compute the trajectories) into StochSystem. This makes it possible to make you own SDEProblem which can be highly optimised with tools like ModelingToolkit by adding a Jacobian to the system, etc.
We can redefine simulate to be a solve wrapper and define remake to remake the StochSystem with new parameters or ic.
That way we can also rewrite the transitions function to use the highly optimized EnsembleProblem from the SciML ecosystem. Something, we could aim for together with issue #1.
using CriticalTransitions, StaticArrays, ModelingToolkit, BenchmarkTools
using ModelingToolkit, OrdinaryDiffEq

σ = 0.03;
γ, α, ω₀, ω, λ = 0.01, 1.0, 1.0, 1.0, 0.6
@variables t u(t) v(t)
D = Differential(t)

eqs = [D(u) ~ -γ*u/2 - (3*α*(u^2 + v^2)/8 + (ω₀^2-ω^2)/2 + λ/4)*v/ω,
       D(v) ~ -γ*v/2 + (3*α*(u^2 + v^2)/8 + (ω₀^2-ω^2)/2 - λ/4)*u/ω]

noiseeqs = [0.1*u,
            0.1*v]

@named sys = ODESystem(eqs)
sys = structural_simplify(sys)
@named sdesys = SDESystem(sys, noiseeqs)

u0 = [u => 0.2,
      v => 0.3]
init = getindex.(u0, 2);

function KPO!(dx, x, p, t) # in-place
    u, v = x
    dx[1] = -γ*u/2 - (3*α*(u^2 + v^2)/8 + (ω₀^2-ω^2)/2 + λ/4)*v/ω
    dx[2] = -γ*v/2 + (3*α*(u^2 + v^2)/8 + (ω₀^2-ω^2)/2 - λ/4)*u/ω
end
function KPO(x, p, t) # out-of-place
    u, v = x
    du = -γ*u/2 - (3*α*(u^2 + v^2)/8 + (ω₀^2-ω^2)/2 + λ/4)*v/ω
    dv = -γ*v/2 + (3*α*(u^2 + v^2)/8 + (ω₀^2-ω^2)/2 - λ/4)*u/ω
    SA[du, dv]
end
init = getindex.(u0,2);
stochsys = StochSystem(KPO, init, zeros(2), σ, idfunc, nothing, I(2), "WhiteGauss")
stochsys! = StochSystem(KPO!, init, zeros(2), σ, idfunc, nothing, I(2), "WhiteGauss")
coupledODE = CoupledODEs(stochsys)
coupledODE! = CoupledODEs(stochsys!)

tmax = 1000.0; tspan = (0.0, tmax); dt = 5
prob_od = ODEProblem{false}(stochsys.f, SVector{2}(init), (0, tmax), CriticalTransitions.p(stochsys))
prob_od! = ODEProblem{true}(stochsys!.f, init, (0, tmax), CriticalTransitions.p(stochsys!))
prob_mt_jac = ODEProblem{false}(sys, u0, tspan, []; jac=true, u0_constructor=x -> SVector(x...))
prob_mt_jac! = ODEProblem{true}(sys, u0, tspan, []; jac=true)
prob_mt = ODEProblem{false}(sys, u0, tspan, []; jac=false, u0_constructor=x -> SVector(x...))
prob_mt! = ODEProblem{true}(sys, u0, tspan, []; jac=false)

@btime trajectory($coupledODE, $tmax, Δt = $dt); # 84.700 μs (2915 allocations: 61.86 KiB)
@btime trajectory($coupledODE!, $tmax, Δt = $dt); # 46.100 μs (2102 allocations: 49.14 KiB)
@btime solve($prob_od, Tsit5(), saveat=5); # 3.076 ms (108533 allocations: 2.14 MiB)
@btime solve($prob_od!, Tsit5(), saveat=5); # 1.359 ms (70165 allocations: 1.10 MiB)
@btime solve($prob_mt_jac, Tsit5(), saveat=5); # 102.900 μs (25 allocations: 16.91 KiB)
@btime solve($prob_mt_jac!, Tsit5(), saveat=5); # 121.600 μs (243 allocations: 32.34 KiB)
@btime solve($prob_mt, Tsit5(), saveat=5); # 103.500 μs (25 allocations: 16.91 KiB)
@btime solve($prob_mt!, Tsit5(), saveat=5); # 139.300 μs (253 allocations: 33.31 KiB)

Could you sketch how you would change the StochSystem struct? I don't fully understand the proposed change.
The idea is that StochSystem is an SDE analogue to CoupledODEs with fields corresponding to the terms you would have in a general SDE equation, but indeed it should be closely linked to SDEProblem because we would always turn the StochSystem into an SDEProblem to simulate it. I agree that simulate should just be a solve wrapper (we could rename it trajectory in line with DS.jl).
How about adding a function SDEProblem(sys::StochSystem, kwargs...) that turns a StochSystem into an SDEProblem?

Resolved by #76


[FEATURE REQUEST]: Remove disabling unique volume ids

Is your feature request related to a problem?
Volume services team added the ability to enable unique volume ids while keeping the ability to disable them via the property. "enable_unique_volume_ids". Turning this feature on is more reliable so we would like to stop support for disabling unique volume ids.
Describe the solution you'd like
Cleanup of code in Diego and hardcoding to enable unique volume ids.
Ideally, this refactor would allow volume services team to stop specifying the property from  the dockerdriver https://github.com/cloudfoundry/dockerdriver.
Diego repo
Volman
Describe alternatives you've considered
We considered supporting both enabled and disabled unique_volume_ids, but thought it would be better to reduce the surface area for support, and enabling unique volume ids is more reliable.
Provide additional context
See tracker story from cf volume services team:
https://www.pivotaltracker.com/story/show/170986312
Original story to enable unique volume ids (while keeping the disabled option configurable).
https://www.pivotaltracker.com/story/show/160356605

@lisamcho - seems like a good improvement/simplification. Would you be willing to submit a PR?

@lisamcho - bumping this thread again regarding my question above: "Would the Volume Services team be willing to submit a PR for this?"

Hey @heyjcollins Volume Services is focusing on other priorities and closed out this story, feel free to drop in our slack channel if you want to chat about it.

Thanks @lisamcho - Under the circumstances, I'm going to go ahead and close this out


Try reverting part of the previous change to see if it's what's breaking lldb, part 2

@swift-ci please test


PF_Community_v1.784

Small layout adjustments to the spell class sections.(thanks Tranquwil)
Slightly reduced header and field label font-size.
In compact/readonly mode the header and field label font-size have been reduced to help with the layout.

Changes / Comments
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.


Update :utc_datetime handling

This changes the handling of :utc_datetime to not write offsets to the db and ignore them when fetching.
I'm wondering if this one should be changed as well though.
https://github.com/elixir-sqlite/exqlite/blob/a173dc87e6094a7beb535773b989d596461a3a75/lib/exqlite/sqlite3.ex#L170
It seems neither postgrex nor myxql support %DateTime{}s not being supplied in UTC:
Postgrex:
https://github.com/elixir-ecto/postgrex/blob/60abc91d7d64155e9d5fe587178e063b1083f668/lib/postgrex/extensions/timestamptz.ex#L52-L54
MyXQL:
https://github.com/elixir-ecto/myxql/blob/fdb147dba07d7699c4af23448996ae7f4663bce6/lib/myxql/protocol/values.ex#L341-L343
The mssql/tds driver seems to have a type for datetimes with offsets.
https://github.com/livehelpnow/tds/blob/36f228275c2bfde2baa45fe70d29d1eb1d44379b/lib/tds/types.ex#L1775-L1788
Usable with custom ecto types it seems: https://github.com/livehelpnow/tds/pull/111#issuecomment-675193597
This PR will currently ignore any offsets, given there's no clear path on how to handle the offset if there is one.
Closes #46

I'm wondering if this one should be changed as well though.
https://github.com/elixir-sqlite/exqlite/blob/a173dc87e6094a7beb535773b989d596461a3a75/lib/exqlite/sqlite3.ex#L170

Yes we should probably alter that there as well.

This PR will currently ignore any offsets, given there's no clear path on how to handle the offset if there is one.

In theory SQLite3 should shift the offsets upon writing the record to UTC. Not 100% certain on that, but I swear I remember reading it in the sqlite documentation.

Maybe here:

Formats 2 through 10 may be optionally followed by a timezone indicator of the form "[+-]HH:MM" or just "Z". The date and time functions use UTC or "zulu" time internally, and so the "Z" suffix is a no-op. Any non-zero "HH:MM" suffix is subtracted from the indicated date and time in order to compute zulu time. For example, all of the following time values are equivalent:

https://www.sqlite.org/lang_datefunc.html

Yea that's where I saw it. 👍🏻

@LostKobrakai if you can, will you go update the exqlite handling of datetimes?

I can do that, I'm just not sure if I should go with an Exception for non UTC datetimes like the other adapters, or an error tuple like everything else seems to be.

I modeled both this adapter and the client library to be close to how MyXQL handles things. If either postgrex or myxql raise an exception for that, let's do that to keep parity.


fix(Buffer): update buffer constructors to use from and alloc

No longer throws DeprecationWarning as described in #1140
Not sure whats up but fails the same tests as master branch so I assume that is okay?
https://nodejs.org/docs/latest/api/buffer.html#buffer_buffer_from_buffer_alloc_and_buffer_allocunsafe

@Ethan-Arrowood there was a regression so we had to revert the change. I’ll release a new version 10.0.0 shortly which will include your fix for the deprecation warnings


Multiple assertions on the same contract

Contract execution is pretty time consuming, so we want to avoid having to run the same contract with exactly the same parameters just to be able to assert multiple properties of it (this might become more obvious with features like #49, and this could also solve #47).
However, we also should avoid having too many assertions inside one test case (it could cause ambiguity about the reason of a test failure), so we need a mechanism, to reuse the contract result across many test cases.

There are some technical difficulties with this regarding to how tasty test cases work.
Each test case is an IsTest a with a run :: OptionSet -> t -> (Progress -> IO ()) -> IO Result. This means that each test case must be able to run in isolation from the others, cannot depend on others.
The closest thing we can get is withResource, we could use this in a similar manner as we did with withCluster
Interface (draft)
  withCluster
    "Tests inside one cluster"
    [ withContract "Get utxos contract" (const getUtxos) (initAda 100)
        [ shouldSucceed "Get utxos", shouldYield "Hello World" ]

Problems:

how to handle multiple contracts in sequence
do we keep the current way of asserting wallet results


[AJV] Add option to run ajv with ajv-formats

Add option to extend the ajv resolver with ajv-formats
ajv-formats makes it easy and secure to validate emails, urls, uuids, and many others string formats.

Hi 👋🏻 thank you for your PR. We can't add a such option because it's inconsistent across all of the resolvers. factoryOtions is not designed for this need.
@bluebill1049  what do you think?

Hi. Thanks for the response.
I looked at other resolvers and some of them have rawValues?: boolean, so it is not that consistent. It is an optional property anyway.
In any case, I'm happy to consider other approaches. Do you have a recommendation for my case?
Thanks.

yea, unless it's something generic across all the schemas. The point of this lib is to create a standard for all custom resolvers, if this causes an issue for you, maybe it's worth creating a custom resolver.  Yes, rawValues is optional and we want to apply to all resovlers so the result will returned before the transformation.

It's something possible but I prefer to open an issue and wait to see if others users have the same need

Thanks guys,

I'm closing this PR in favour of: https://github.com/react-hook-form/resolvers/pull/431
I also created an issue as agreed: https://github.com/react-hook-form/resolvers/issues/432


Sophia error

Hello again, @farag2 . Hope you are doing well.
I'm having an issue when running the latest Sophia script (unchanged) on a fresh win10pro x64 install on Oracle VM VirtualBox.
It happens right after the script starts to run as you can see on picture below:

The script finishes itself. I didn't notice any other red text. I couldn't see the final lines because PowerShell window closes automatically.
Thank you, friend.

You may ignore it. There is no error actually. There is no just a rey in registry. I'll add -ErrorAction Ignore parameter to this registry key.


Request GetMedia Api that get the error response : MissingAuthenticationTokenException

Describe the issue
I am using Amazon Connect services, and I have used Lambda function blocks, as well as Start Media Streaming and Stop Media Streaming blocks in my contact flow. My goal is to capture real-time voice stream during phone conversations. The official documentation suggests using the GetMedia API for this purpose. However, I encountered an error in the response.
The exception is MissingAuthenticationTokenException.
So how do get the  voice stream in real-time？
Links

done


Ensure Javy is always installed before running it

WHY are these changes introduced?
If shopify app function build is run for a JS Function extension before shopify app build is executed, then Javy is not installed before trying to execute it. This used to work when using the javy-cli NPM package to execute Javy because that package would implicitly install Javy if it was not already installed. But now that the CLI doesn't use that package, installation needs to be explicitly performed. I've chosen to do it in the runJavy function to ensure a check is always performed to see if Javy is installed and install if it isn't.
WHAT is this pull request doing?
Ensuring Javy is installed before trying to run it. The installBinary method performs a check to see if the binary is installed before attempting an install so this won't result in any attempts to redownload the binary if it's already present.
How to test your changes?
Ensure you don't have the javy binary present by running rm packages/app/dist/cli/services/bin/javy and rm packages/app/dist/cli/services/bin/javy.
Then run:
pnpm shopify app function build --path <path-to-js-function-extension>

Measuring impact
How do we know this change was effective? Please choose one:

[x] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[ ] Existing analytics will cater for this addition
[ ] PR includes analytics changes to measure impact

Checklist

[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes

Does this also cover the auto-builds that happen during the replay command?

Does this also cover the auto-builds that happen during the replay command?

Yes it will. However I did notice a bug with how function-runner is being invoked that I'll put up a separate PR to address.


refactor(FilterBar): Filter bar accessibility

SUMMARY
Refactored the relationship between labels and their form controls in the filterBar
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

Fixes #25859

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up


chore: workaround test flakiness until a proper fix

Closed in favor of https://github.com/fedimint/fedimint/pull/2903


[EmbeddingApi] Add autocase to implement XWalkView.getUserAgentString

-Add autocase to implement XWalkView.getUserAgentString
-Cover the XWalkActivity and XWalkInitializer two ways
Impacted tests(approved): new 4, update 0, delete 0
Unit test platform: [Android]
Unit test result summary: pass 4, fail 0, block 0
BUG=https://crosswalk-project.org/jira/browse/XWALK-4825

@jennycao please help to review it.

LGTM


Need to implement backup of data

must be encrypted, options could be s3, dropbox... @chrisfilo do you have suggestions for what you do for NeuroVault? Is it encrypted?

We use RDS built in backup and regular EBS snapshots. Plus every half a
year everything with DOI goes to Stanford digital library.
On Jan 22, 2016 5:23 PM, "Vanessa Sochat"<EMAIL_ADDRESS>wrote:

must be encrypted, options could be s3, dropbox... @chrisfilo
https://github.com/chrisfilo do you have suggestions for what you do
for NeuroVault? Is it encrypted?
—
Reply to this email directly or view it on GitHub
https://github.com/expfactory/expfactory-docker/issues/21.

cool thanks :)

Another question - I see the RDS instance on AWS, but I don't understand how you are using that for NeuroVault given that the docker-compose specifies a container "db" to be run on the local instance. Did you do something custom to deploy it that is not represented in the NeuroVault repo?

@chrisfilo see above!

I'm production we are not using a dockerized postgres instance but directly
connect to RDS. This configured in local_settings.py on the production
server.
On Jan 24, 2016 4:51 PM, "Vanessa Sochat"<EMAIL_ADDRESS>wrote:

@chrisfilo https://github.com/chrisfilo see above!
—
Reply to this email directly or view it on GitHub
https://github.com/expfactory/expfactory-docker/issues/21#issuecomment-174360104
.

ah ok, understood. Did you just manually edit the docker-compose in production to remove db, and then change local_settings.py to specify the aws instance? That seems pretty reasonable. We want to do something like that for experiment factory.

Yes for now it's just a manual edit. There must be a cleaner way of doing
this though.
On Jan 24, 2016 5:03 PM, "Vanessa Sochat"<EMAIL_ADDRESS>wrote:

ah ok, understood. Did you just manually edit the docker-compose in
production to remove db, and then change local_settings.py to specify the
aws instance? That seems pretty reasonable. We want to do something like
that for experiment factory.
—
Reply to this email directly or view it on GitHub
https://github.com/expfactory/expfactory-docker/issues/21#issuecomment-174363354
.

This will be done with amazon rds, figured out and encrypted, closing issue.


_mm_cmpeq_sd intrinsic is misleading

This is really nitpicky and rarely an issue, but for the CMPSD instruction (note there are two -- I'm talking about the floating-point comparison one), binja is lifting to a 3-operand intrinisic _mm_cmpeq_sd. This is misleading because the third operand determines the comparison condition (It is sometimes cmpeq_sd, but only when the third operand is 0). https://www.felixcloutier.com/x86/cmpsd
https://github.com/Vector35/arch-x86/blob/46061eb65bdc9cd7eddd6f400376895534d61f99/arch_x86_intrinsics.cpp#L4730-L4731
000da6f6  f20fc2d806         cmpsd   xmm3, xmm0, 0x6

lifts to
_mm_cmpeq_sd(zmm1.q, zmm0.q, 6)

But the condition for this instruction is actually NLE rather than EQ. Capstone gives
0x0000000000000000:  F2 0F C2 D8 06    cmpnlesd xmm3, xmm0

which would also be an improvement. But the dream would be if these just lifted to proper floating point operations in IR rather than intrinsics :)

I don't think this is nitpicky at all we're really just not supporting the pseudo op:


feat: add ConfigMap support for static configuration

This adds support for a ConfigMap with configurable content to be used for e.g. a config file for a tool running as CronJob.

Good idea. I opened #82 for the generic chart.


XMLHttpRequest and fetch()

This is mostly a reminder that if this is accepted, someone should make sure that there's web-platform-tests that test this change for XMLHttpRequest and fetch(). Hope that's okay to track here.

@annevk What do you mean by this? This proposal simply expands the string grammar in ECMAScript. It's not detectable at runtime.

I wonder what happens if you have a JSON resource that contains U+2028 or U+2029 in a JSON value string. Whether browsers do the right thing or trip up somehow.

And what does that have to do with this proposal? This doesn't change JSON in any way.

Mostly as a reminder to double check browsers haven't taken weird shortcuts in their JSON parser.

@annevk Then we should do that regardless of whether this proposal is accepted, right?

Agreed; this proposal explicitly avoids observable effects on JSON parsing.


Add shape properties in Dialog Widget to customize border radius

In my case, I have an issue with the dialog. When changing the properties roundedCornersRadius, it only changes the radius of the header and picker section but the border radius of the background Dialog still be the radius.circular(4)

Can you send some images of the error?

this is my issue, do you have any solution
Regard,

I won't have time to look at this issue until next week. But gonna try to solve the issue

@DucHuySET are you changing the theme of your app/dialogs?
If so, can you send me the ThemeData that results in this problem?

The problem happens because the Dialog that holds the widget uses the theme of the app. You can set the dialog theme of the app to be the same as showMonthPicker roundedCornersRadius property:
theme: ThemeData(
  colorScheme: ColorScheme.fromSwatch(primarySwatch: Colors.indigo)
      .copyWith(secondary: Colors.pinkAccent),
  //Changing the global dialog border
  dialogTheme: DialogTheme(
    shape: RoundedRectangleBorder(
      borderRadius: BorderRadius.all(
        //here
        Radius.circular(20),
      ),
      side: BorderSide(color: Colors.blue)
    ),
  ),
),


Poor contrast between bg and text when coalition color is light.

I noticed that for coalitions that have a light background color, always using white for the text doesn't create the right contrast.
I decided to implement a simple function in the Stats component that determines which text color should be used based on the brightness of the coalition background color.

That's a very good idea! 👍
But, after testing the code, some of the results are not harmonious.
It seems that some code conditions need to be changed.

I'm working on ways to add shadow effect to characters while solving the "svg safari blurry" issue.

Thanks @GlaceCoding for the advice now it should work, maybe the only thing is the white text on the layer bar, but if I change that based on the background too, the black text on the black/transparent background create the same problem of poor contrast.

@raccoman
I'm sorry for the delay. I couldn't proceed because I was preparing for a job and working on a project.
Currently, SVG image rendering is being reorganized to solve the Poor Contrast problem.

@JaeSeoKim No problem.
To solve the problem of low contrast, are you more inclined to add shadows to the text or to use my solution, in the case of the first I can see if I can give you a hand if you want.

Currently, we added shadows through the first method.
It seems good to add a function that reverses the shadow color and font color through the method you suggested!


[python] add a new parameter epoch_size in model.py for kvstore dist_sync

also added example/distributed_training

One comment, seems the inception net construction code was copied over in too many places. We should consider to put them somewhere and do import @antinucleon

@antinucleon @tqchen it seems that there are something within the inception (no problem with lenet) we are not synced to the server, so even using the same model pulled from the servers, each worker may output different results for the same validation data. is that due to the BN layer?


feat: add util to diff ssz objects

Motivation
Had some challenges debugging an invalid state root and built this util to help with diffing states.  Is useful for diffing any deeply nested ssz object.

:tada: This PR is included in v1.22.0 :tada:


Updating Dockerfiles From Docker Directory and get_started.md to Reach Last Stable Version of Python, PyTorch and MMCV

Motivation
My master thesis project was developed using MMDetection and MMSegmentation and I'm very interested in OpenMMLab projects. I particularly like the latest version of the technology. For 3 months, PyTorch did not support Python3.10. However, version 1.11.0 of PyTorch adds Python3.10 support.
Modification
The Dockerfile in the docker directory has been updated to reach the latest versions of MMCV and PyTorch. In dockerfiles, some commands were added to gain a smaller docker image. In documents, 'get_started.md' contains updates to the last version of Python, MMCV, and PyTorch with respect to BC.
BC-breaking (Optional)
No, this version of MMCV and PyTorch have fully backward compatibility. This is good for moving forward by safe backward compatibility.
Use cases (Optional)
Nothing changed in providing new use cases.
Checklist
Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects, like MMDet or MMDet3D.
The documentation has been modified accordingly, like docstring or example tutorial

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