Issue on pre-training

I ran mini-ImageNet/FRN/ResNet-12_pretrain/train.sh according to the instructions but got this error, which I think is caused by the network outputting the inf value. Reducing the initial learning rate to 1e-3 can avoid this error.
Traceback (most recent call last):
File "train.py", line 35, in
tm.train(model)
File "../../../../trainers/trainer.py", line 185, in train
iter_counter=iter_counter)
File "../../../../trainers/frn_train.py", line 97, in pre_train
log_prediction = model.forward_pretrain(inp)
File "../../../../models/FRN.py", line 136, in forward_pretrain
beta=beta)  # wayquery_shotresolution, way
File "../../../../models/FRN.py", line 75, in get_recon_dist
m_inv = (sts + torch.eye(sts.size(-1)).to(sts.device).unsqueeze(0).mul(lam)).inverse()  # way, d, d
RuntimeError: CUDA error: an illegal memory access was encountered
Looking forward to your reply!

Hi, thanks for ur interest in our work!
In my experience, I never encounter such errors for my pre-training experiments on either our internal codebase or this public one.
Since my current internship hasn't finished, it might be hard for me to do the debugging for this issue this week. But I'll definitely let u know as soon as we have any updates on it. Meanwhile, feel free to provide updates if u have any new findings (or new errors lol).
Thanks!

Thanks for your prompt reply!
I can pre-train normally after setting Woodbury to False in line 54 of model/FRN.py, and the results look reasonable.😀
Not sure if Woodbury Identity is causing the problem.

Hi thanks for your updates!
My colleague helped me run a preliminary check on pretraining using our lab's machine. Looks like without changing any hyper-parameters, the current pretraining code runs well without errors. This also matches my impression.  But I'll also take a double-check on the pretraining by myself after I return to school.
Btw, just wondering are you using the same Conda environment we provided in the README? Not sure whether this error is due to pytorch's version, but worth taking a check.
And thanks for letting us know the non-Woodbury implementation works well on ur side! Just as you can find in the paper, although all of our results are using the Woodbury one for consistency, these two implementations are indeed mathematically equivalent. And also as you can find in the speed analysis section in our paper, for this specific pretraining case, the non-Woodbury form should be slightly faster than the Woodbury one. Since pretraining on ImageNet gonna take quite a long time, I personally didn't re-do the pre-training using the non-Woodbury implementation, but only checked the inference consistency. Not sure whether the current hyper-parameters also works best for the non-Woodbury pre-training, but good to know its results look reasonable on your side. Thanks!

I also encountered the same problem. After setting Woodbury to False according to the above suggestions, the pre-training no longer reported an error. However, the problem reappeared when running the fine-tuning part of train.sh.

What needs to be added is that the error I got is inverse_cuda: For batch 2: U(24,24) is zero, singular U. Looking forward to your reply!

Hi all, thanks for the updates and information. I'm still unable to reproduce this issue on our lab machine using the current hyperparameters. From what I can tell though, it looks like learning is diverging for the learned parameter alpha and sending the corresponding regularization term lambda to zero (or possibly infinity, in @AmethystZeroAtwell's case). I can think of a few possible fixes beyond changing the Woodbury parameter:

Add a floor value of 1e-6 to lambda for safety (FRN.py, line 66)
Scale down the initialized support pool values (FNR.py, line 43) by a factor of sqrt(num_channels) when using a resnet backbone (so that support and query feature distributions align, hopefully preventing divergent learning on the regularization parameter)
Artificially slow down the learning rate for alpha by replacing alpha.exp() (FRN.py, line 66) with alpha.div(10).exp()

I have pushed fix #1 since that's just good practice, but in the interest of faithfully reproducing the results in the paper we'll probably leave #2 and 3 to the user's discretion. I was unable to observe any differences in pretraining performance for fix #2, but I also couldn't finish the entire run so I can't say with any certainty that implementing fix #2 will actually reproduce the results of the paper. Same disclaimer for #3: shouldn't affect performance, but still might.
Hope that helps, let me know if the floor value fails to eliminate these errors.

Thanks to Davis!
And thanks to @walker1207  for bringing up the issues on your side.
Just a quick followup question here, @AmethystZeroAtwell @walker1207, have you tried using the provided conda environment provided in the readme? Not sure whether these issues are related to the package versions, but given that we cannot reproduce this error on our machines, it might worth taking a double-check on this.
Thanks!

Hi @walker1207 , I found that running the code on PyTorch 1.7.1 causes this problem, on PyTorch 1.7.0 it works fine.
Thanks to @Tsingularity @daviswer for your complete response and wonderful work!

@walker1207 just a quick followup: would the upgrade on pytorch solve the error on ur side?
thanks!

closing this for now. feel free to re-open it if this issue happens again and cannot be solved using the solution above.


Improved config feature

@ipapandinas What do you think? If an account was created outside the project dir, should it be merged into this.swankyConfig from the system config when we call the command from the project dir?

@prxgr4mm3r I do not think so, if it's a personal dev account you do not want to share it publicly.
Here is how I see it:

Account created/set outside the project dir: Update Swanky system config only
Account created/set in the project dir: Update both Swanky project + system config
Account created/set passing an env Swanky config variable: Update Swanky env config only

When setting the default account we can check if the alias belongs to the current account list.
For example:
Scenario 1

I created an "hello" dev account outside a project dir => Swanky system config only is updated
I navigate to a project dir and I set change "hello" as default => Swanky system config only is updated, the default account in the Swanky local project dir config is unchanged

Scenario 2

I created a "bye" dev account inside a project dir => Swanky system config + project dir config are updated
I set "bye" as default account => Swanky system config + project dir config are updated

Scenario 3

I use account create command with an env Swanky config => Swanky env config only is updated
I use account default command with an env Swanky config => Swanky env config only is updated

@prxgr4mm3r good question but I don't think so. System account are personal accounts and project accounts are shared with project contributors.

@prxgr4mm3r I created this commit https://github.com/inkdevhub/swanky-cli/commit/3a70313dc7ae46c1b832b80c8cb55ab5621d34ce on another branch to explore the possibility of using a config builder. The goal is to streamline the process of updating the configuration in a safe and controlled manner. What do you think? If you agree, you can cherry pick my commit and go from there.

@ipapandinas I like this idea! Will work on that.


resolve error

raulkong898@fedora:~$ sudo dnf -y install faugus-launcher
Updating and loading repositories:
Repositories loaded.
Failed to resolve the transaction:
Problem: conflicting requests

package faugus-launcher-1.0-76.fc40.noarch from copr:copr.fedorainfracloud.org:faugus:faugus-launcher requires umu-launcher, but none of the providers can be installed
package faugus-launcher-1.0-77.fc40.noarch from copr:copr.fedorainfracloud.org:faugus:faugus-launcher requires umu-launcher, but none of the providers can be installed
package faugus-launcher-1.1-1.fc40.noarch from copr:copr.fedorainfracloud.org:faugus:faugus-launcher requires umu-launcher, but none of the providers can be installed
package faugus-launcher-1.1-2.fc40.noarch from copr:copr.fedorainfracloud.org:faugus:faugus-launcher requires umu-launcher, but none of the providers can be installed
nothing provides python(abi) = 3.12 needed by umu-launcher-1.1.2-1.20241012.b34df64.fc40.noarch from copr:copr.fedorainfracloud.org:faugus:faugus-launcher
nothing provides python3.12dist(filelock) >= 3.9 needed by umu-launcher-1.1.2-1.20241012.b34df64.fc40.noarch from copr:copr.fedorainfracloud.org:faugus:faugus-launcher
nothing provides python3.12dist(python-xlib) >= 0.33 needed by umu-launcher-1.1.2-1.20241012.b34df64.fc40.noarch from copr:copr.fedorainfracloud.org:faugus:faugus-launcher
nothing provides python(abi) = 3.12 needed by umu-launcher-1.1.3-1.20241023.8bc37bb.fc40.noarch from copr:copr.fedorainfracloud.org:faugus:faugus-launcher
nothing provides python3.12dist(filelock) >= 3.9 needed by umu-launcher-1.1.3-1.20241023.8bc37bb.fc40.noarch from copr:copr.fedorainfracloud.org:faugus:faugus-launcher
nothing provides python3.12dist(python-xlib) >= 0.33 needed by umu-launcher-1.1.3-1.20241023.8bc37bb.fc40.noarch from copr:copr.fedorainfracloud.org:faugus:faugus-launcher
You can try to add to command line:
--skip-broken to skip uninstallable packages

Thanks for reporting.
I can't reproduce.
I have Fedora fresh installed in a VM and it installs just fine.
What distro are you running?

distro fedora

Please make sure your system is up to date.
sudo dnf update -y --refresh

I tried and it doesn't go. It doesn't function.

I just reinstalled Fedora on a VM and it's working fine.
There's something wrong with your system.
If you are using Fedora 40 and it's up to date, it should be pulling the dependencies.

I just reinstalled Fedora on a VM and it's working fine.
There's something wrong with your system.
If you are using Fedora 40 and it's up to date, it should be pulling the dependencies.


flake8 cleanup

Thank you
Usually I just run flake8 with flake8 --ignore=E501 and I'm thus not too keen on merging all these changes that affect the layout of the code (the 80 columns limit is a bit too restrictive imho)
Also, the changes to update_args_dict break everything that relies on args.get(... anyhow I fixed all other issues discovered by flake8
Feel free to create another PR with some style corrections (but hopefully not hundreds of line changes just to stick inside 80 cols)
Thanks again


Link is dead

link is dead. https://docs.microsoft.com/en-us/user/azure-stack-vm-sizes.md link is from part Use Av2 and F series virtual machines. Azure Stack can now use virtual machines based on the Av2-series and F-series virtual machine sizes. For more information see "and then the link"

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

ID: b6cabd0e-e2f8-fd37-04d0-0343f3d03122
Version Independent ID: 1fa6f945-092f-4cb0-24a8-b85fd64307af
Content: Azure Stack 1804 Update
Content Source: articles/azure-stack/azure-stack-update-1804.md
Service: azure-stack
Product: unspecified
GitHub Login: @Brenduns
Microsoft Alias: brenduns

@RedBa We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Incorrect query count in admin footer if debug false

I was sure there was an issue for this but cannot find it, so I'm filing another one. I hope I'm not submitting a duplicate.
The query count in the admin footer is wrong : always shows 0 when YOURLS_DEBUG is false, shows correct count if YOURLS_DEBUG is true

After consideration, instead of fixing that bug, I changed the logic a bit: showing a query count is in itself a debug information. So, for people who don't need debug information, let's just make things simpler. No debug information.


manifest.json version not updated

The manifest is running few releases behind:
https://github.com/jeatheak/Mitsubishi-WF-RAC-Integration/blob/main/custom_components/mitsubishi_wf_rac/manifest.json#L10
Which results in:

while this is the real version installed:

merged in release 2024.6


Otel Collector does not support metric receiver although docs advertise that it does.

Describe the bug
OTel Lambda Collector docs say that the collector extension allows lambdas to use the OpenTelemetry Collector Exporter to send traces and metrics to any configured backend while Telemetry API Receiver document says.
The receiver is configured only for traces as seen here
Is this a miss or intentional? And why is it advertised like it is, if this is intentional.
I do see a PR in progress to add support for Logs
Steps to reproduce
Added python proto layer. Added otel collector layer. There is manual instrumentation of custom metrics from the lambda code.
config.yaml looks like:
receivers:
  otlp:
    protocols:
      http:

exporters:
  logging:
    loglevel: debug
  otlp:
    endpoint: enterprise.otelcollector.gateway.com

service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [logging, otlp]
    metrics:
      receivers: [otlp]
      exporters: [logging, otlp]

processors:
  batch:
    send_batch_max_size: 100
    send_batch_size: 10
    timeout: 2s

What did you expect to see?
Per the documentation, we expected it to work for both traces and metrics (custom metrics)
What did you see instead?
Only traces were exported and collector threw clear error on endpoint /v1/metrics saying it has reached max number of retries.
What version of collector SDK version did you use?
Version
What language layer did you use?
Python
Additional context
No

@tylerbenson @nslaughter can you please help on my above query?

I'm a bit confused,

threw clear error on endpoint /v1/metrics saying it has reached max number of retries.

This indicates that enterprise.otelcollector.gateway.com does not have an metrics pipeline with an OTLP receiver and that the lambda layer is trying to export the metrics.
One simple way to verify this is the case is to only have the logging exporter in the collector lambda configuration metrics pipeline and then verify in the logs that the metrics are being generated.


Combine similar notifications mentions three parts of the API without explaining them [EN] Feedback for: /web/fundamentals/engage-and-retain/push-notifications/handling-messages?hl=en

The interplay between all three API's is pretty convoluted and I had to work out why it was done this way. I think this needs to be exaplined up front, but also that the APIs tag, getNotifications etc need to be explained about what they do first and then why they are being used this way.

I believe Joe has addressed.


web: switch to using sqlocal transaction method to ensure transaction isolation

fixes tlon-3302
Adds a transaction proxy system that's called within withTransactionCtx that allows the Drizzle ORM to work with SQLocal's SQLite transactions in the browser, which allows us to pass drizzle queries to the handler param and have them processed using the SQLocal transaction function.
In order to access the transaction method I added a new SQLocal client instance that's exported from the client module that we then pass to queryFn in withCtxOrDefault.
If we don't have the sqlocal.transaction method (as we wouldn't on native), we fall back to our manual transaction building process.
Copilot description:
This pull request introduces support for SQLocal transactions and improves the handling of SQLite database operations. The most important changes include adding a new setSqlocal function, modifying transaction handling to support SQLocal, and updating query functions to work with SQLocal proxies.
SQLocal Integration:

packages/app/lib/webDb.ts: Added setSqlocal function to initialize SQLocal instance and updated setupDb function to call setSqlocal. [1] [2]
packages/shared/src/db/client.ts: Introduced SQLocalDrizzle import, added sqlocalInstance variable, and created setSqlocal function. [1] [2]
packages/shared/src/db/client.ts: Added sqlocal proxy to handle SQLocal transactions.
packages/shared/src/db/index.ts: Exported setSqlocal function.

Query and Transaction Handling:

packages/shared/src/db/query.ts: Updated query context to include optional sqlocal property and modified withCtxOrDefault function to pass sqlocal to query functions. [1] [2]
packages/shared/src/db/query.ts: Added createTransactionProxyDb function to create a proxy for handling SQLocal transactions.
packages/shared/src/db/query.ts: Enhanced withTransactionCtx function to support SQLocal transaction API and handle SQLocal-specific transaction logic. [1] [2]

These changes ensure that the database operations can utilize SQLocal transactions, providing more flexibility and improved transaction handling capabilities.

I think maybe we should hold off on this for now? I think we should find a solution that involves configuring this in webDb so that we don't have to pull in all of sqlocal in the shared package, but that makes other things more complicated, and it probably makes sense to figure out what we're going to do to make the database persistent first.
If we just want to silence the warnings, I think we could just make our own driver to pass into drizzle. It'd be extremely simple, just copy https://github.com/DallasHoff/sqlocal/blob/main/src/drizzle/client.ts and remove the warning.

fine by me, def feels like overkill if we're just gonna rip out sqlocal anyway

Closing for now


Upgrade to Chromium 79.0.3945.88

Chromium 79.0.3945.88 resolves CVE-2019-13767. I will let you know once I have a successful build.
The only changes to the patches were some line-number changes that quilt handled automatically.

The build succeeded. Feel free to merge.


Use Casters instead of Presenters as of PsySH ~0.5

PsySH ~0.5 is replacing the presenter system by symfony/var-dumper, so ezsh needs an update, here it is :)
Sorry, I didn't test this PR, but still, this should do the work. Please tell me if I did anything wrong.

Thanks @nicolas-grekas !
I'll give it a try :)

Many thanks @nicolas-grekas !
I'll fix the dependency number.


Allow specifying statusline truncation character

Currently, when the statusline overflows, the truncation character is a < character (or > character):

It would be nice to be able to specify alternatives, may be via the fillchars option.

The 'listchars' option is clearly only for 'list' option and has nothing to do with the statusline. Perhaps we need an extra entry for the 'fillchars' option.

@chrisbra Makes sense, I updated the issue title and description.

I personally don't care about this anymore as I consider this an extremely minor issue, so I am closing.

Reopening since I care about it again :)


fix use of predefined nimbleLists

This PR:

Adds predefined nimbleList SEXP functions to dynamicRegistrations.h, so they will be compiled into the sessionSpecificDll

Updates nimbleList interface system to handle the case that the dll where relevant functions are (in a predefined list) may not be the same as the one other parts of a compiled project are in.

Managing the registrations and dlls correctly will be important since CRAN is moving towards enforcement of registration, and we are generally in good shape as we do use registration extensively.

So this PR should fix the nimbleList test failures we're seeing on OS X?
On Wed, May 31, 2017 at 11:44 AM, perrydv<EMAIL_ADDRESS>wrote:

This PR:

Adds predefined nimbleList SEXP functions to dynamicRegistrations.h,
so they will be compiled into the sessionSpecificDll
2.
Updates nimbleList interface system to handle the case that the dll
where relevant functions are (in a predefined list) may not be the same as
the one other parts of a compiled project are in.
Managing the registrations and dlls correctly will be important since CRAN
is moving towards enforcement of registration, and we are generally in good
shape as we do use registration extensively.
You can view, comment on, or merge this pull request online at:
https://github.com/nimble-dev/nimble/pull/396
Commit Summary

fix use of predefined nimbleLists

File Changes

M packages/nimble/R/cppInterfaces_nimbleFunctions.R
https://github.com/nimble-dev/nimble/pull/396/files#diff-0 (31)
M packages/nimble/R/nimbleProject.R
https://github.com/nimble-dev/nimble/pull/396/files#diff-1 (9)
M packages/nimble/inst/include/nimble/dynamicRegistrations.h
https://github.com/nimble-dev/nimble/pull/396/files#diff-2 (15)

Patch Links:

https://github.com/nimble-dev/nimble/pull/396.patch
https://github.com/nimble-dev/nimble/pull/396.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nimble-dev/nimble/pull/396, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACYr3oCIi-R-nIr9CUNZxWtwotu_v2AUks5r_bUCgaJpZM4NsCIr
.

whoops, just saw Nick's slack message. I can test on OS X if no one else
has.
On Wed, May 31, 2017 at 12:12 PM, Chris Paciorek<EMAIL_ADDRESS>
wrote:

So this PR should fix the nimbleList test failures we're seeing on OS X?
On Wed, May 31, 2017 at 11:44 AM, perrydv<EMAIL_ADDRESS>wrote:

This PR:

Adds predefined nimbleList SEXP functions to dynamicRegistrations.h,
so they will be compiled into the sessionSpecificDll
2.
Updates nimbleList interface system to handle the case that the dll
where relevant functions are (in a predefined list) may not be the same as
the one other parts of a compiled project are in.
Managing the registrations and dlls correctly will be important since
CRAN is moving towards enforcement of registration, and we are generally in
good shape as we do use registration extensively.
You can view, comment on, or merge this pull request online at:
https://github.com/nimble-dev/nimble/pull/396
Commit Summary

fix use of predefined nimbleLists

File Changes

M packages/nimble/R/cppInterfaces_nimbleFunctions.R
https://github.com/nimble-dev/nimble/pull/396/files#diff-0 (31)
M packages/nimble/R/nimbleProject.R
https://github.com/nimble-dev/nimble/pull/396/files#diff-1 (9)
M packages/nimble/inst/include/nimble/dynamicRegistrations.h
https://github.com/nimble-dev/nimble/pull/396/files#diff-2 (15)

Patch Links:

https://github.com/nimble-dev/nimble/pull/396.patch
https://github.com/nimble-dev/nimble/pull/396.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nimble-dev/nimble/pull/396, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACYr3oCIi-R-nIr9CUNZxWtwotu_v2AUks5r_bUCgaJpZM4NsCIr
.


Add (automated) tests for the interface

Closes #30, closes #56

Do you want a more general reset function that removes sections, sets the temperature to the default, turns off variable step, turns off second order, sets the default time step, ...

@ramcdougal @AljenU All example scripts work in isolation, but:

Running all tests causes a crash; I commented out the problematic tests and the remaining ones run without crashing
Running MATLAB's memory usage increases each time I run all tests, so it looks like we have a memory leak

Stack traces for crashes below. It seems to be a problem with spFactor() and NetCvode::init_events().
example_intfires
Stack Trace (from fault):
[  0] 0x00007ff8388b5a6c                            C:\nrn\bin\libnrniv.dll+01661548 Z8spFactorPc+00000108
[  1] 0x00007ff83883589a                            C:\nrn\bin\libnrniv.dll+01136794 Z9nrn_solveP9NrnThread+00000074
[  2] 0x00007ff83882e19d                            C:\nrn\bin\libnrniv.dll+01106333 Z23nrn_fixed_step_lastpartP9NrnThread+00000221
[  3] 0x00007ff83882c814                            C:\nrn\bin\libnrniv.dll+01099796 Z14nrn_fixed_stepv+00000228
[  4] 0x00007ff83882cb26                            C:\nrn\bin\libnrniv.dll+01100582 Z8fadvancev+00000070
[  5] 0x00007ff8388441f7                            C:\nrn\bin\libnrniv.dll+01196535 Z8hoc_callv+00000199
[  6] 0x00007ff838843fa3                            C:\nrn\bin\libnrniv.dll+01195939 Z11hoc_executeP4Inst+00000067
[  7] 0x00007ff8388442a2                            C:\nrn\bin\libnrniv.dll+01196706 Z8hoc_callv+00000370
[  8] 0x00007ff838843fa3                            C:\nrn\bin\libnrniv.dll+01195939 Z11hoc_executeP4Inst+00000067
[  9] 0x00007ff83884e130                            C:\nrn\bin\libnrniv.dll+01237296 Z12hoc_shortforv+00000368
[ 10] 0x00007ff838843fa3                            C:\nrn\bin\libnrniv.dll+01195939 Z11hoc_executeP4Inst+00000067
[ 11] 0x00007ff83884d992                            C:\nrn\bin\libnrniv.dll+01235346 Z10hoc_ifcodev+00000130
[ 12] 0x00007ff838843fa3                            C:\nrn\bin\libnrniv.dll+01195939 Z11hoc_executeP4Inst+00000067
[ 13] 0x00007ff8388442a2                            C:\nrn\bin\libnrniv.dll+01196706 Z8hoc_callv+00000370
[ 14] 0x00007ff838843fa3                            C:\nrn\bin\libnrniv.dll+01195939 Z11hoc_executeP4Inst+00000067
[ 15] 0x00007ff83884dc60                            C:\nrn\bin\libnrniv.dll+01236064 Z11hoc_forcodev+00000208
[ 16] 0x00007ff838843fa3                            C:\nrn\bin\libnrniv.dll+01195939 Z11hoc_executeP4Inst+00000067
[ 17] 0x00007ff8388442a2                            C:\nrn\bin\libnrniv.dll+01196706 Z8hoc_callv+00000370
[ 18] 0x00007ff838843fa3                            C:\nrn\bin\libnrniv.dll+01195939 Z11hoc_executeP4Inst+00000067
[ 19] 0x00007ff83884ddbc                            C:\nrn\bin\libnrniv.dll+01236412 Z13hoc_call_funcP6Symboli+00000060

example_patternstim
Stack Trace (from fault):
[  0] 0x00007ff8354aed44                            C:\nrn\bin\libnrniv.dll+00519492 ZN8NetCvode11init_eventsEv+00000484
[  1] 0x00007ff83553dc6e                            C:\nrn\bin\libnrniv.dll+01105006 Z15nrn_finitializeid+00000974
[  2] 0x00007ff83553de57                            C:\nrn\bin\libnrniv.dll+01105495 Z11finitializev+00000039
[  3] 0x00007ff8355541f7                            C:\nrn\bin\libnrniv.dll+01196535 Z8hoc_callv+00000199
[  4] 0x00007ff835553fa3                            C:\nrn\bin\libnrniv.dll+01195939 Z11hoc_executeP4Inst+00000067
[  5] 0x00007ff83555ddbc                            C:\nrn\bin\libnrniv.dll+01236412 Z13hoc_call_funcP6Symboli+00000060

example_savestate
Stack Trace (from fault):
[  0] 0x00007ff835595a6c                            C:\nrn\bin\libnrniv.dll+01661548 Z8spFactorPc+00000108
[  1] 0x00007ff83551589a                            C:\nrn\bin\libnrniv.dll+01136794 Z9nrn_solveP9NrnThread+00000074
[  2] 0x00007ff83550e19d                            C:\nrn\bin\libnrniv.dll+01106333 Z23nrn_fixed_step_lastpartP9NrnThread+00000221
[  3] 0x00007ff83550c814                            C:\nrn\bin\libnrniv.dll+01099796 Z14nrn_fixed_stepv+00000228
[  4] 0x00007ff83550cb26                            C:\nrn\bin\libnrniv.dll+01100582 Z8fadvancev+00000070
[  5] 0x00007ff8355241f7                            C:\nrn\bin\libnrniv.dll+01196535 Z8hoc_callv+00000199
[  6] 0x00007ff835523fa3                            C:\nrn\bin\libnrniv.dll+01195939 Z11hoc_executeP4Inst+00000067
[  7] 0x00007ff83552ddbc                            C:\nrn\bin\libnrniv.dll+01236412 Z13hoc_call_funcP6Symboli+00000060

example_acpot (after example_netcon)
Stack Trace (from fault):
[  0] 0x00007ff83556ed44                            C:\nrn\bin\libnrniv.dll+00519492 ZN8NetCvode11init_eventsEv+00000484
[  1] 0x00007ff8355fdc6e                            C:\nrn\bin\libnrniv.dll+01105006 Z15nrn_finitializeid+00000974
[  2] 0x00007ff8355fde57                            C:\nrn\bin\libnrniv.dll+01105495 Z11finitializev+00000039
[  3] 0x00007ff8356141f7                            C:\nrn\bin\libnrniv.dll+01196535 Z8hoc_callv+00000199
[  4] 0x00007ff835613fa3                            C:\nrn\bin\libnrniv.dll+01195939 Z11hoc_executeP4Inst+00000067
[  5] 0x00007ff83561ddbc                            C:\nrn\bin\libnrniv.dll+01236412 Z13hoc_call_funcP6Symboli+00000060

example_netcon
Stack Trace (from fault):
[  0] 0x00007ff835685a6c                            C:\nrn\bin\libnrniv.dll+01661548 Z8spFactorPc+00000108
[  1] 0x00007ff83560589a                            C:\nrn\bin\libnrniv.dll+01136794 Z9nrn_solveP9NrnThread+00000074
[  2] 0x00007ff8355fe19d                            C:\nrn\bin\libnrniv.dll+01106333 Z23nrn_fixed_step_lastpartP9NrnThread+00000221
[  3] 0x00007ff8355fe23d                            C:\nrn\bin\libnrniv.dll+01106493 Z23nrn_fixed_step_lastpartP9NrnThread+00000381
[  4] 0x00007ff8355fcd10                            C:\nrn\bin\libnrniv.dll+01101072 Z20nrn_fixed_step_groupi+00000368
[  5] 0x00007ff83557a3a2                            C:\nrn\bin\libnrniv.dll+00566178 Z17ncs2nrn_integrated+00000450
[  6] 0x00007ff8355b29fc                            C:\nrn\bin\libnrniv.dll+00797180 ZN3BBS12netpar_solveEd+00000300
[  7] 0x00007ff8355d09cc                            C:\nrn\bin\libnrniv.dll+00920012 ZN5OcBBSD2Ev+00004428
[  8] 0x00007ff835629437                            C:\nrn\bin\libnrniv.dll+01283127 Z16hoc_call_ob_procP6ObjectP6Symboli+00000503

example_patternstim
Stack Trace (from fault):
[  0] 0x00007ff835685a6c                            C:\nrn\bin\libnrniv.dll+01661548 Z8spFactorPc+00000108
[  1] 0x00007ff83560589a                            C:\nrn\bin\libnrniv.dll+01136794 Z9nrn_solveP9NrnThread+00000074
[  2] 0x00007ff8355fe19d                            C:\nrn\bin\libnrniv.dll+01106333 Z23nrn_fixed_step_lastpartP9NrnThread+00000221
[  3] 0x00007ff8355fe23d                            C:\nrn\bin\libnrniv.dll+01106493 Z23nrn_fixed_step_lastpartP9NrnThread+00000381
[  4] 0x00007ff8355fcd10                            C:\nrn\bin\libnrniv.dll+01101072 Z20nrn_fixed_step_groupi+00000368
[  5] 0x00007ff83557a3a2                            C:\nrn\bin\libnrniv.dll+00566178 Z17ncs2nrn_integrated+00000450
[  6] 0x00007ff8355b29fc                            C:\nrn\bin\libnrniv.dll+00797180 ZN3BBS12netpar_solveEd+00000300

I have isolated the problem to the n.reset_sections() call, which just runs clib.neuron.hoc_oc("forall delete_section()") in the background. If I omit it, there are no crashes. However, we do need some way to reset the topology between tests.

It seems like the crash has something to do with Section.delete(), n.reset_sections() and n.allsec().
All problematic examples have in common that they do not define any sections. If I run example_intfires.m (or any of the other problematic examples) everything is fine, but if I run afterwards as = n.allsec(); disp(as{1}); I get a crash:
[  0] 0x000000006f5e01d4     Z:\Git\matlabneuron\neuron\neuronInterface.dll+00393684 cppGetPassThrough+00382196
[  1] 0x000000006f591ead     Z:\Git\matlabneuron\neuron\neuronInterface.dll+00073389 cppGetPassThrough+00061901

If I run only the following script, I also get a crash:
% Try to cause a crash while running NEURON in MATLAB
n = neuron.Neuron();
n.reset_sections();
as = n.allsec();
disp(as{1});

If I add soma = n.Section("soma"); at the top of every problematic example, they behave fine, as far as I can tell.

@ramcdougal ready for review


Farming Guild Plug?

Either in the Chat box or On Screen, Displays current Farming Contract
Would it be possible to have a plugin in or something like it?

Duplicate of #7634


feat(auth): entity level authentication

Summary:
Build & Testing:

[ ] I ran cargo test successfully.
[ ] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[ ] I have added relevant unit & integration tests.
[ ] I have updated the documentation accordingly.
[ ] I have performed a self-review of my code.
[ ] PR follows the naming convention of <type>(<optional scope>): <title>

Summary by CodeRabbit

New Features

Introduced and integrated comprehensive support for basic and JWT authentication methods.
Added GraphQL schemas for authentication settings and data retrieval with authentication.
Enhanced configuration handling to include authentication settings and protection levels for data.

Improvements

Streamlined HTTP handling to accommodate authentication contexts and JSON response modifications.
Updated lambda expressions and path handling to support authentication validation and protected expressions.

Bug Fixes

Fixed issues related to string borrowing across the application by utilizing Cow<'_, str> for more efficient string handling.

Tests

Added a suite of test scenarios for basic and JWT authentication methods, covering various configurations and access control for protected data.

Documentation

Included new documentation for configuring and utilizing authentication within the application.

Created new pr - https://github.com/tailcallhq/tailcall/pull/1579


Plug memory leaks.

 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.mander207 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report

Merging #38 into master will increase coverage by 0.12%.
The diff coverage is 75%.

@@            Coverage Diff             @@
##           master      #38      +/-   ##
==========================================
+ Coverage   71.51%   71.64%   +0.12%
==========================================
  Files           4        4
  Lines         323      328       +5
  Branches       54       56       +2
==========================================
+ Hits          231      235       +4
+ Misses         52       51       -1
- Partials       40       42       +2

Impacted Files
Coverage Δ

libseshat/src/libseshat.c
68.9% <75%> (+1.08%)
:arrow_up:

libseshat/tests/simple.c
73.77% <75%> (-1.23%)
:arrow_down:

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 4161cb4...59a075b. Read the comment docs.


Add guidance on what error message to show for a text input if the input uses characters that are not allowed and the set of allowed characters is very large

From comment on text input backlog by @terrysimpson99
An issue was recently raised on slack that has cropped up before. The guidance says "If the input uses characters that are not allowed and you do not know what the characters are. Say ‘[whatever it is] must only include [list of allowed characters]’."
Challenging example 1: A designer pointed out that following guidance would result in "Business name must only include letters, numbers, hyphens, spaces, apostrophes, exclamation marks, commas, quotation marks, ampersand, underscore, full stop, round brackets and forward slash". The consensus appeared to be that it was not desirable.
Challenging example 2: A service I worked on allowed ~180 char (it was the entire ISO-8859-15 char set). We also believed that listing the characters as per guidance wasn't desirable.
In both examples, the conclusion was to use the example from guidance ‘[whatever it is] must only include letters a to z, hyphens, spaces and apostrophes’.
This scenario is likely to happen again. Can the guidance be updated to indicate that this is acceptable, or suggest a different approach?
Related documentation
Guidance on error message if the input uses characters that are not allowed and you do not know what the characters are, in the file src/components/text-input/index.md.njk
Suggestion
Add guidance on what to do if the set of allowed characters is very large and/or difficult to show to the user.

Challenging example 1: A designer pointed out that following guidance would result in "Business name must only include letters, numbers, hyphens, spaces, apostrophes, exclamation marks, commas, quotation marks, ampersand, underscore, full stop, round brackets and forward slash". The consensus appeared to be that it was not desirable.
Challenging example 2: A service I worked on allowed ~180 char (it was the entire ISO-8859-15 char set). We also believed that listing the characters as per guidance wasn't desirable.
In both examples, the conclusion was to use the example from guidance ‘[whatever it is] must only include letters a to z, hyphens, spaces and apostrophes’.
Re example 1 and its solution - does this mean users ended up being told they couldn't include numbers, exclamation marks, etc., even though they could have?

@terrysimpson99 Thanks for the context - it really helped with understanding this issue!
@leona-creator Thanks for sharing your solution! We've updated our guidance to suggest a similar approach.


Using v-for with a

Platform: Win
Vetur version: 0.8.5
VSCode version: 1.13.1

Problem
When you have v-for as an attribute to <template>, the linter (presumably?) throws an error stating that you must also have a v-bind:key attribute. When using v-for on <template> however, it isn't possible to also have a key directive - instead, you add the key to the children elements of the <template>.
Reproducible Case
<template v-for="i in 10">
	<div v-if="i < 5" :key="i">
		Under 5
	</div>
	<div v-else :key="i">
		5 or over
	</div>
</template>

Will result in red squiggles under "<template>"

Dup of #261 and #266.
Please search through existing issues next time before posting.

From: https://vuejs.github.io/vetur/linting-error.html

Set ESLint rules in .eslintrc. An example:

{
  "extends": [
    "eslint:recommended",
    "plugin:vue/recommended"
  ],
  "rules": {
    "vue/html-self-closing": "off" // Fix v-for/template/key bug
  }
}

asa

From: https://vuejs.github.io/vetur/linting-error.html

Set ESLint rules in .eslintrc. An example:

{
  "extends": [
    "eslint:recommended",
    "plugin:vue/recommended"
  ],
  "rules": {
    "vue/html-self-closing": "off" // Fix v-for/template/key bug
  }
}

没有用处


feat(backend): added login, signup and onboard UI

Ready for Review. No major backend logic implemented yet.
Feat originally for login page only but I forgot, pull request consists of login. signup and onboard UI.

Fixed Conflict + All PR Issues here. Awaiting Re-request.

Closing this PR as it has gotten too messy to track.


test(cloudstorage): Add remaining GCP tests for CloudStorage checks

Context
There was some checks without tests for CloudStorage in GCP provider.
Description
Added new tests for:

[x] cloudstorage_bucket_log_retention_policy_lock check
[x] cloudstorage_bucket_public_access check
[x] cloudstorage_bucket_uniform_bucket_level_access check

License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This is awesome @danibarranqueroo , congrats on your first PR! But please, instead of using re.search, always assert the whole string. Could you change it for the status_extended? The rest of it is perfect 😄

Thank you Sergio, I've just made the changes that you suggested :tada:

This is awesome @danibarranqueroo , congrats on your first PR! But please, instead of using re.search, always assert the whole string. Could you change it for the status_extended? The rest of it is perfect 😄

Thank you @sergargar, I've just made the changes that you suggested 🎉

Since changing that something failed, I'll fix it now and come back when it's done


I won't accept any PRs before rewriting is done

yes... i won't merge any new features PRs before rewriting the website is done. Any PRs after #17 will be closed...

we are done here ig


[MBUILDCACHE-99] Project checksum fails to identify moved files in certain cases

Input files checksum is calculated by sorting all files and using their content (but not their path) to update a checksum. This means that if a file is moved or renamed in a way that doesn't change its location in the list of sorted files, the input files checksum will not change. This change adds the file's path to the checksum.
Following this checklist to help us incorporate your
contribution quickly and easily:

[X] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

Maybe you could add an IT test? Thanks


show subdomain on whoami command

we show subdomain when running wrangler subdomain by itself. Do we still want this or should it be closed? Would be a pretty easy addition


Run tests in debug mode

Previously, crate2nix tests were run equivalently to cargo test --release, which is a somewhat unusual default configuration.
It might be worth having a flag to tweak this behaviour, similar to Cargo. A more ambitious version yet would permit running both debug and release versions of the tests. I'm not sure what the best interface for either of those is.

Hi @edef1c!
I also think it should be configurable. Usually, I execute tests locally with cargo in debug mode but then in CI in release mode. Depends quite on the test. Obviously, model tests or the like profit from release mode more than others.
I haven't worked on crate2nix for a while and will first invest in flakifying it and making it work on Mac OS again (which I am using currently). But I'd be interested in hearing how such an interface could look like!


Procfile doesn't fix heroku H10-App Crashed Error

Hi, you included in the Readme file for the server instructions on how to deploy to heroku.  But you didn't give specifics on how to for client.  I did basically the same thing, but get the h10 erros.  I also added a Procfile, but that didn't fix it.  See the logs:
Logged in as<EMAIL_ADDRESS>Brads-MBP-2% git add .

Delta compression using up to 4 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 287 bytes | 287.00 KiB/s, done.
Total 3 (delta 1), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Building on the Heroku-20 stack
remote: -----> Node.js app detected
remote:
remote: -----> Creating runtime environment
remote:
remote:        NPM_CONFIG_LOGLEVEL=error
remote:        NODE_VERBOSE=false
remote:        NODE_ENV=production
remote:        NODE_MODULES_CACHE=true
remote:
remote: -----> Installing binaries
remote:        engines.node (package.json):  unspecified
remote:        engines.npm (package.json):   unspecified (use default)
remote:
remote:        Resolving node version 12.x...
remote:        Downloading and installing node 12.20.1...
remote:        Using default npm version: 6.14.10
remote:
remote: -----> Restoring cache
remote:        - node_modules
remote:
remote: -----> Installing dependencies
remote:        Installing node modules
remote:
remote:        ><EMAIL_ADDRESS>postinstall /tmp/build_815875c8/node_modules/babel-runtime/node_modules/core-js
remote:        > node -e "try{require('./postinstall')}catch(e){}"
remote:
remote:
remote:        ><EMAIL_ADDRESS>install /tmp/build_815875c8/node_modules/webpack-dev-server/node_modules/fsevents
remote:        > node install.js
remote:
remote:
remote:        Skipping 'fsevents' build as platform linux is not supported
remote:
remote:        ><EMAIL_ADDRESS>install /tmp/build_815875c8/node_modules/watchpack-chokidar2/node_modules/fsevents
remote:        > node install.js
remote:
remote:
remote:        Skipping 'fsevents' build as platform linux is not supported
remote:
remote:        ><EMAIL_ADDRESS>postinstall /tmp/build_815875c8/node_modules/core-js
remote:        > node -e "try{require('./postinstall')}catch(e){}"
remote:
remote:
remote:        ><EMAIL_ADDRESS>install /tmp/build_815875c8/node_modules/jest-haste-map/node_modules/fsevents
remote:        > node install.js
remote:
remote:
remote:        Skipping 'fsevents' build as platform linux is not supported
remote:
remote:        ><EMAIL_ADDRESS>postinstall /tmp/build_815875c8/node_modules/core-js-pure
remote:        > node -e "try{require('./postinstall')}catch(e){}"
remote:
remote:        added 1721 packages in 27.414s
remote:
remote: -----> Build
remote:        Running build
remote:
remote:        ><EMAIL_ADDRESS>build /tmp/build_815875c8
remote:        > CI= react-scripts build
remote:
remote:        Creating an optimized production build...
remote: Browserslist: caniuse-lite is outdated. Please run:
remote: npx browserslist@latest --update-db
remote:        Compiled with warnings.
remote:
remote:        ./src/components/EditProfile.js
remote:          Line 6:10:  'SignoutIcon' is defined but never used  no-unused-vars
remote:
remote:        ./src/App.js
remote:          Line 6:10:  'darkTheme' is defined but never used  no-unused-vars
remote:          Line 10:8:  'Navbar' is defined but never used     no-unused-vars
remote:
remote:        Search for the keywords to learn more about each warning.
remote:        To ignore, add // eslint-disable-next-line to the line before.
remote:
remote:        File sizes after gzip:
remote:
remote:          224.37 KB  build/static/js/2.f1016167.chunk.js
remote:          21.94 KB   build/static/js/main.7f033cf6.chunk.js
remote:          11.56 KB   build/static/css/2.3a60762f.chunk.css
remote:          786 B      build/static/js/runtime-main.9c408c88.js
remote:
remote:        The project was built assuming it is hosted at /.
remote:        You can control this with the homepage field in your package.json.
remote:
remote:        The build folder is ready to be deployed.
remote:        You may serve it with a static server:
remote:
remote:          npm install -g serve
remote:          serve -s build
remote:
remote:        Find out more about deployment here:
remote:
remote:          bit.ly/CRA-deploy
remote:
remote:
remote: -----> Caching build
remote:        - node_modules
remote:
remote: -----> Pruning devDependencies
remote:        audited 1721 packages in 12.082s
remote:
remote:        62 packages are looking for funding
remote:          run npm fund for details
remote:
remote:        found 5000 vulnerabilities (4996 low, 4 high)
remote:          run npm audit fix to fix them, or npm audit for details
remote:
remote: -----> Build succeeded!
remote: -----> Discovering process types
remote:        Procfile declares types -> web
remote:
remote: -----> Compressing...
remote:        Done: 75.4M
remote: -----> Launching...
remote:        Released v9
remote:        https://floating-fortress-68904.herokuapp.com/ deployed to Herok
remote:
remote: Verifying deploy... done.
To https://git.heroku.com/floating-fortress-68904.git
bcf0d2f..7b7ee66  master -> master
Brads-MBP-2% heroku logs --tail
2021-01-16T02:08:33.927064+00:00 app[web.1]: ℹ ｢wds｣: Project is running at http://<IP_ADDRESS>/
2021-01-16T02:08:33.927587+00:00 app[web.1]: ℹ ｢wds｣: webpack output is served from
2021-01-16T02:08:33.927703+00:00 app[web.1]: ℹ ｢wds｣: Content not from webpack is served from /app/public
2021-01-16T02:08:33.927811+00:00 app[web.1]: ℹ ｢wds｣: 404s will fallback to /
2021-01-16T02:08:33.928060+00:00 app[web.1]: Starting the development server...
2021-01-16T02:08:33.928061+00:00 app[web.1]:
2021-01-16T02:08:34.025661+00:00 heroku[web.1]: Process exited with status 0
2021-01-16T02:08:45.802909+00:00 heroku[web.1]: Starting process with command npm start
2021-01-16T02:08:49.706568+00:00 app[web.1]:
2021-01-16T02:08:49.706643+00:00 app[web.1]: ><EMAIL_ADDRESS>start /app
2021-01-16T02:08:49.706644+00:00 app[web.1]: > react-scripts start
2021-01-16T02:08:49.706645+00:00 app[web.1]:
2021-01-16T02:08:54.758151+00:00 app[web.1]: ℹ ｢wds｣: Project is running at http://<IP_ADDRESS>/
2021-01-16T02:08:54.759220+00:00 app[web.1]: ℹ ｢wds｣: webpack output is served from
2021-01-16T02:08:54.759570+00:00 app[web.1]: ℹ ｢wds｣: Content not from webpack is served from /app/public
2021-01-16T02:08:54.759732+00:00 app[web.1]: ℹ ｢wds｣: 404s will fallback to /
2021-01-16T02:08:54.760354+00:00 app[web.1]: Starting the development server...
2021-01-16T02:08:54.760356+00:00 app[web.1]:
2021-01-16T02:08:54.949507+00:00 heroku[web.1]: Process exited with status 0
2021-01-16T02:08:55.012817+00:00 heroku[web.1]: State changed from starting to crashed
2021-01-16T02:08:56.279196+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=floating-fortress-68904.herokuapp.com request_id=f19b20e1-5177-48d8-84d3-752a0dac4fe9 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2021-01-16T02:08:56.847505+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=floating-fortress-68904.herokuapp.com request_id=c88b11be-a789-4023-b401-33be40dc7238 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2021-01-16T02:08:59.051406+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=floating-fortress-68904.herokuapp.com request_id=3cc72829-f861-43b4-885c-9143c0e613c1 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2021-01-16T02:08:59.347323+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=floating-fortress-68904.herokuapp.com request_id=a608c666-61a6-4032-9481-f45f771e04a9 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2021-01-16T02:16:53.000000+00:00 app[api]: Build started by user<EMAIL_ADDRESS>2021-01-16T02:18:53.552901+00:00 app[api]: Release v8 created by user<EMAIL_ADDRESS>2021-01-16T02:18:53.552901+00:00 app[api]: Deploy bcf0d2f1 by user<EMAIL_ADDRESS>2021-01-16T02:18:54.445583+00:00 heroku[web.1]: State changed from crashed to starting
2021-01-16T02:19:02.000000+00:00 app[api]: Build succeeded
2021-01-16T02:19:04.026566+00:00 heroku[web.1]: Starting process with command npm start
2021-01-16T02:19:06.982699+00:00 app[web.1]:
2021-01-16T02:19:06.982717+00:00 app[web.1]: ><EMAIL_ADDRESS>start /app
2021-01-16T02:19:06.982718+00:00 app[web.1]: > react-scripts start
2021-01-16T02:19:06.982718+00:00 app[web.1]:
2021-01-16T02:19:09.316390+00:00 app[web.1]: ℹ ｢wds｣: Project is running at http://<IP_ADDRESS>/
2021-01-16T02:19:09.317216+00:00 app[web.1]: ℹ ｢wds｣: webpack output is served from
2021-01-16T02:19:09.317331+00:00 app[web.1]: ℹ ｢wds｣: Content not from webpack is served from /app/public
2021-01-16T02:19:09.317438+00:00 app[web.1]: ℹ ｢wds｣: 404s will fallback to /
2021-01-16T02:19:09.317703+00:00 app[web.1]: Starting the development server...
2021-01-16T02:19:09.317704+00:00 app[web.1]:
2021-01-16T02:19:09.439317+00:00 heroku[web.1]: Process exited with status 0
2021-01-16T02:19:09.492187+00:00 heroku[web.1]: State changed from starting to crashed
2021-01-16T02:19:09.496377+00:00 heroku[web.1]: State changed from crashed to starting
2021-01-16T02:19:17.221806+00:00 heroku[web.1]: Starting process with command npm start
2021-01-16T02:19:19.338363+00:00 app[web.1]:
2021-01-16T02:19:19.338380+00:00 app[web.1]: ><EMAIL_ADDRESS>start /app
2021-01-16T02:19:19.338385+00:00 app[web.1]: > react-scripts start
2021-01-16T02:19:19.338385+00:00 app[web.1]:
2021-01-16T02:19:21.365309+00:00 app[web.1]: ℹ ｢wds｣: Project is running at http://<IP_ADDRESS>/
2021-01-16T02:19:21.365654+00:00 app[web.1]: ℹ ｢wds｣: webpack output is served from
2021-01-16T02:19:21.365733+00:00 app[web.1]: ℹ ｢wds｣: Content not from webpack is served from /app/public
2021-01-16T02:19:21.365801+00:00 app[web.1]: ℹ ｢wds｣: 404s will fallback to /
2021-01-16T02:19:21.365975+00:00 app[web.1]: Starting the development server...
2021-01-16T02:19:21.365976+00:00 app[web.1]:
2021-01-16T02:19:21.473384+00:00 heroku[web.1]: Process exited with status 0
2021-01-16T02:19:21.509923+00:00 heroku[web.1]: State changed from starting to crashed
2021-01-16T02:19:22.477912+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=floating-fortress-68904.herokuapp.com request_id=11e9d785-a529-4199-b725-6c61338581e0 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2021-01-16T02:19:23.052918+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=floating-fortress-68904.herokuapp.com request_id=c956620a-46dd-4979-bd1b-057e89080dad fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2021-01-16T02:19:46.791586+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=floating-fortress-68904.herokuapp.com request_id=240b5d7e-4413-48d8-91cd-f93b50188b74 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2021-01-16T02:19:46.978251+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=floating-fortress-68904.herokuapp.com request_id=2d9e9c7a-faae-4047-8330-8573d0c4ecdc fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2021-01-16T02:34:16.509806+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=floating-fortress-68904.herokuapp.com request_id=1dd51568-cfd4-446b-98b5-d0305b105697 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2021-01-16T02:34:16.687752+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=floating-fortress-68904.herokuapp.com request_id=cf3fba58-a2d6-4d68-b9f5-6ff2789df7b5 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2021-01-16T03:27:20.637069+00:00 heroku[web.1]: State changed from crashed to starting
2021-01-16T03:27:31.868446+00:00 heroku[web.1]: Starting process with command npm start
2021-01-16T03:27:34.939611+00:00 app[web.1]:
2021-01-16T03:27:34.939668+00:00 app[web.1]: ><EMAIL_ADDRESS>start /app
2021-01-16T03:27:34.939669+00:00 app[web.1]: > react-scripts start
2021-01-16T03:27:34.939669+00:00 app[web.1]:
2021-01-16T03:27:38.331932+00:00 app[web.1]: ℹ ｢wds｣: Project is running at http://<IP_ADDRESS>/
2021-01-16T03:27:38.332439+00:00 app[web.1]: ℹ ｢wds｣: webpack output is served from
2021-01-16T03:27:38.332551+00:00 app[web.1]: ℹ ｢wds｣: Content not from webpack is served from /app/public
2021-01-16T03:27:38.332642+00:00 app[web.1]: ℹ ｢wds｣: 404s will fallback to /
2021-01-16T03:27:38.332889+00:00 app[web.1]: Starting the development server...
2021-01-16T03:27:38.332891+00:00 app[web.1]:
2021-01-16T03:27:38.470345+00:00 heroku[web.1]: Process exited with status 0
2021-01-16T03:27:38.526515+00:00 heroku[web.1]: State changed from starting to crashed
2021-01-16T03:34:30.000000+00:00 app[api]: Build started by user<EMAIL_ADDRESS>2021-01-16T03:36:21.448635+00:00 app[api]: Release v9 created by user<EMAIL_ADDRESS>2021-01-16T03:36:21.448635+00:00 app[api]: Deploy 7b7ee669 by user<EMAIL_ADDRESS>2021-01-16T03:36:21.700557+00:00 heroku[web.1]: State changed from crashed to starting
2021-01-16T03:36:30.000000+00:00 app[api]: Build succeeded
2021-01-16T03:36:33.423178+00:00 heroku[web.1]: Starting process with command node index.js
2021-01-16T03:36:36.789327+00:00 app[web.1]: internal/modules/cjs/loader.js:818
2021-01-16T03:36:36.789364+00:00 app[web.1]: throw err;
2021-01-16T03:36:36.789365+00:00 app[web.1]: ^
2021-01-16T03:36:36.789365+00:00 app[web.1]:
2021-01-16T03:36:36.789366+00:00 app[web.1]: Error: Cannot find module '/app/index.js'
2021-01-16T03:36:36.789367+00:00 app[web.1]: at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
2021-01-16T03:36:36.789368+00:00 app[web.1]: at Function.Module._load (internal/modules/cjs/loader.js:667:27)
2021-01-16T03:36:36.789369+00:00 app[web.1]: at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
2021-01-16T03:36:36.789369+00:00 app[web.1]: at internal/main/run_main_module.js:17:47 {
2021-01-16T03:36:36.789370+00:00 app[web.1]: code: 'MODULE_NOT_FOUND',
2021-01-16T03:36:36.789370+00:00 app[web.1]: requireStack: []
2021-01-16T03:36:36.789370+00:00 app[web.1]: }
2021-01-16T03:36:36.888310+00:00 heroku[web.1]: Process exited with status 1
2021-01-16T03:36:36.954018+00:00 heroku[web.1]: State changed from starting to crashed
2021-01-16T03:36:50.960064+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=floating-fortress-68904.herokuapp.com request_id=d69ebd12-9228-49eb-b064-7d98e2dd28ef fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2021-01-16T03:36:51.154347+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=floating-fortress-68904.herokuapp.com request_id=959b0c39-e0e9-4fcd-bf25-4d885db3922d fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2021-01-16T03:36:54.893743+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=floating-fortress-68904.herokuapp.com request_id=81d6d11d-a4c6-4bf5-894d-967451d14721 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
2021-01-16T03:36:55.045087+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=floating-fortress-68904.herokuapp.com request_id=0c22bfbf-a5ee-4f41-93a6-506c35165e93 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https

I use netlify for hosting the frontend. I am not familiar on how to host the frontend on heroku.
If you are choosing the host your frontend, all you need to do is point your git repo to the netlify client, it will do the rest. Also, make sure to include your environmental variables using the netlify UI.
If you are not familiar with these process, just google 'how to host react frontend on netlify'.

I use netlify for hosting the frontend. I am not familiar on how to host the frontend on heroku.
If you are choosing the host your frontend, all you need to do is point your git repo to the netlify client, it will do the rest. Also, make sure to include your environmental variables using the netlify UI.
If you are not familiar with these process, just google 'how to host react frontend on netlify'.

Ok thx!   I did that.  https://funniestpets.netlify.app
but it's not working with the backend.  I set the env config files on netlify
REACT_APP_BE=https://morning-lake-57360.herokuapp.com
REACT_APP_CLOUDINARY_ENDPOINT=https://api.cloudinary.com/v1_1/funniestpets
and still not working.  I'm pretty sure the backend is working - seems to be...

Ok thx!   I did that.  https://funniestpets.netlify.app
but it's not working with the backend.  I set the env config files on netlify
REACT_APP_BE=https://morning-lake-57360.herokuapp.com
REACT_APP_CLOUDINARY_ENDPOINT=https://api.cloudinary.com/v1_1/funniestpets
and still not working.  I'm pretty sure the backend is working - seems to be...

the variable REACT_APP_BE should be 'https://morning-lake-57360.herokuapp.com/api/v1'

the variable REACT_APP_BE should be 'https://morning-lake-57360.herokuapp.com/api/v1'

That worked thanks!
Another question - the video limit appears to be 30MB.  How can it be increased?  Is that in the code or is it cloudinary that sets the limit?  30MB isn't a very big video.

That worked thanks!
Another question - the video limit appears to be 30MB.  How can it be increased?  Is that in the code or is it cloudinary that sets the limit?  30MB isn't a very big video.

you can change the value by editing this file
https://github.com/manikandanraji/youtubeclone-frontend/blob/2b0f73004ed9bc5c6513a4f351229ce7d109c7e1/src/components/UploadVideo.js#L22

you can change the value by editing this file
https://github.com/manikandanraji/youtubeclone-frontend/blob/2b0f73004ed9bc5c6513a4f351229ce7d109c7e1/src/components/UploadVideo.js#L22


Using intrinsic-left & intrinsic-top throws an error

When using:
top: == &[intrinsic-top];
left: == &[intrinsic-left];

I get the following error:
Uncaught Bad initializer to c.Equation
Using x, y works fine:
x: == &[intrinsic-x];
y: == &[intrinsic-y];

I look in the parser and everything seems ok.

Fix on 2.1.x branch. Though it doesn't de-duplicate those two things, and binding to intrinsic-x may not reset "left" property. It would be a good time to drop x/y properties and move to left/top by default.

Per discussion with @d4tocchini we will remove x/y properties and make things be left/top instead. This way only computed-top/intrinsic-top will work and follow logic of computed-height/intrinsic-height.
I also added computed-bottom/computed-height, but computed-size won't work this way. I didnt add intrinsic-bottom/right though, as it's a very dangerous sugar. Do you think we should apply 2d unpacking for size: == intrinsic-size work.

Another issue was that using intrinsic-top & intrinsic-left assigned still assigned position: absolute. I fixed that, but I better write more tests


Versioned tags removed from DockerHub

I've been using the 2.1.0 tag of the drone-email image in my Drone builds, but recently I noticed that all of the tags besides latest have been removed from DockerHub: https://hub.docker.com/r/drillster/drone-email/tags
Was that intentional? With only the latest tag available, any erroneous pushes will break everyone using this plugin until the next successful push.

I haven't removed them myself... Maybe they were removed by Docker when they removed the automated build? Either way I'll look into re-adding tags when I re-automate things using GitHub Actions.


Pull link information from Dockerfile

If I use a Dockerfile in my build configuration, with a link specified, it does not trigger a link-dependency during startup.
It should, in my oppinion, be such that Dockerfile settings get parsed from the dockerfile and gets overridden by build-settings that in turn get overridden by run-settings.
Want me to look into a solution for this? I think this applies to more settings than just linking.

can you post an example of such a Dockerfile? is this fig/compose related (which is not yet supported and probably a larger discussion)?

You are right. Was porting from a fig-file and forgot that link is a Run-parameter and not a Build-parameter. Are compose-support planned? I would really like having as little dependency on maven config as possible (for increased portability).

Yes, compose support is planned (see #57). Closing this this ticket, feel free to reopen it if you still need support here.


[Fix]Fixed the issue where the directory level of the youtubevis2coco…

… script was changed but the document was not changed.
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Fixed the issue where the directory level of the youtubevis2coco script was changed but the document was not changed.
Modification
Modified the Chinese and English documentation of tracking_dataset_prepare.
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
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 MMPreTrain.
The documentation has been modified accordingly, like docstring or example tutorials.

 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.


Re-work API

Currently the API requires the user to pass a closure for synthesis.
I'd like to re-work this to be data-oriented (savable and loadable as a file), and synthesis constructable with the builder pattern.  Users must be able to pass in their own variables, and still be able to get step events in custom closures for flexibility and backwards-compatibility.

Update
I have thought about the right way to do this probably too way much without writing code.  I want to avoid writing a VM within Twang due to performance concerns.  So how should a synthesis format work?
API
The new API will heavily use the type system.
use twang::Synth::{Sig, Mix};

let mut audio = Audio::<Ch16, 2>::with_silence(48_000, 48_000 * 5);
// Two sine oscillators, an octave apart
let oscs = [
    Sig(440.0).sine(),
    Sig(880.0).sine(),
];
// Mix the two together
let synth = Mix(&oscs);

synth.stream(audio.sink());

Format
For the format, twang will attempt to use postcard (as an optional feature).  An intermediate MuON based format for human-readable/writeable will be able to be used with it.


JavaScript Tip Calculator

Hi ! I am Malavika R Vikraman, a GSSOC'21 participant.
I will like to contribute to this project by adding a a simple tip calculating  app. It will take the total amount, and ask you haw the service was .Depending on which a tip will be calculated and displayed.
Please , kindly assign this task to me

I want to contribute to this please assign me

Hey, I am Divita Gulati, a participant of GSSOC'21.
I would like to contribute to this, please assign this task to me.

I'm Closing this issue as it's duplicate
Who ever is interested comment on #347


Fixes #142 : composer update --no-dev got PHP Fatal error: Class 'ZF\AssetManager\AssetInstaller' not found

move some require-dev to require:

"zfcampus/zf-asset-manager": "^1.0",
 "zfcampus/zf-composer-autoloading": "^1.0",

move Apiglity constant to require

"files": [
     "src/Apigility/constants.php"
 ]

I don't agree with any of these changes.
zf-asset-manager is only intended for use in development; the approach it uses is only geared towards development, and, to be honest, was added essentially only because AssetManager wasn't yet at a stable version that would work with v3 components from ZF. While I understand that running composer update --no-dev would potentially break, I'd argue you shouldn't run that; instead, remove your vendor directory, and run composer install --no-dev.
Second, zf-composer-autoloading, like zf-asset-manager, is a development tool, and should not be required in production.
Finally, the constants in src/Apigility/constants.php are meant for consumption by zf-apigility-admin and zf-apigility-admin-ui... which are, again, development tools.
As such, I'm closing this issue. The placement of each component and the autoloading definitions was very much purposeful.

on my experience, in production, it shows error if the welcome page is current welcome Application/view/index/index.phtml that used the layout/layout.phtml that shows:

                Apigility version <?= \Apigility\VERSION ?>

@weierophinney @webimpress @ezimuel could you please double check if what @samsonasik says is happening ? In production I also see that the default view that is rendered tries to print \Aigility\VERSION which is not loaded when --no-dev is used in composer.


Test case and potential fix for #15.

Test case and potential fix for issue #15.

I am not sure this is a suitable fix but it clears the test case I have although master currently seems to fail 9 tests and hits an error on one of them.


Bug: dropdown of "boats over 24m" is not fully populated

Discovered by @OlamideA
The list for "boats over 24m" is not complete. All items after "One (1) magnetic compass that meets the requirements set out in the Navigation Safety Regulations" are missing.

fixed by https://github.com/uoForms/quickforms3/commit/58e5c3f4715baa23af89b879e20b249e55d3e370


elasticsearch error unknown parameter [refresh]

Hi,
I get this in my transporter log:
transporter: CRITICAL: elasticsearch error (2015-08-04 07:36:12.483817364 +0000 UTC: Error [IllegalArgumentException[Action/metadata line [1] contains an unknown parameter [refresh]]] Status [500] [500])

I searched the transporter repo for refresh, but could not find anything. Any idea who is using the refresh param? I found this issue at ES when digging around for answers: https://github.com/elastic/elasticsearch/issues/11690

I think it came from our node tests. Closing.