Pubsub with IAM [DO NOT MERGE]

Generated using cl/227621162.

@andreamlin, is this PR still active?

No, we can close it
On Thu, Feb 7, 2019, 6:44 PM Solomon Duskis<EMAIL_ADDRESS>wrote:

@andreamlin https://github.com/andreamlin, is this PR still active?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/googleapis/google-cloud-java/pull/4288#issuecomment-461672155,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD1KskBekj2got3AN14Ebc8P84F96cvlks5vLOSngaJpZM4Zo9sb
.


introducing onExternalPlaybackChange

adds possiblity to get AVPlayer.externalPlaybackActive flag

Hi @arturjaworski, this looks great and appears to being pretty close to being ready to merge.
Can you document this in the README file including what the event payload looks like and also provide instructions on how to test this. I'm ordering an Apple TV for testing which should arrive late next week where I can test this.

@cobarx updated :)

What do I need to do to test this, I'm not too familiar with doing external playback.

Please try to connect/disconnect to AirPlay. Some AirPlay server should be enough (eg. Reflector 3). onExternalPlaybackChange will be called on connection/disconnection. Just let me know if you'll have any problem! :)

Tested this with my new AppleTV and it worked great. Thanks!


Use 'throw' expression

Sorry, we despise this new language feature, and have chosen not to use it.

Ok, no problem


add an empty /sys to stack images

This allows users of read-only base stack images to mount a sysfs inside their containers.

:+1:

Looks good to me, but can you add a comment documenting the purpose in the script?

@tt done.

Do you still need this, @fabiokung? I'm sorry for forgetting about this.

Yes, without it we can't mount a sysfs filesystem inside dynos/containers. Right now it requires me to manually patch the stack image before using it.


Toil in singleMachine mode not loading the same module versions in worker processes as in master process

I have my own Python installation, meaning the Python global site packages directory, writable by me, is ~/python/lib/python2.7/site-packages. I also have ~/.local/lib/python2.7/site-packages where things installed with pip install --user go.
I recently set up a new Toil-using pipeline, which requires Toil and some certain version of other packaged, and gets run via the setup.py entry points system. I installed it with python setup.py develop, which downloaded and installed the appropriate versions of all the dependencies.
The dependencies ended up in ~/python/lib/python2.7/site-packages, but it turns out I had older versions of some dependencies in ~/.local/lib/python2.7/site-packages. When invoking my pipeline through the entry point system, it would load the appropriate versions of all the dependencies from one directory, but then when Toil spins up its child processes in single machine mode, they end up loading the old versions of the dependencies from the other directory, leading to my code running with the wrong versions of some dependencies.
Just importing in python -i gives the old versions, and not the versions that were specifically installed as dependencies of this pipeline. I am pretty sure that the entry point system wrappers are doing something to provide my master script with exactly the versions of the modules it asked for in setup.py. But that's not happening in the worker processes.
Toil should integrate with the entry points system and crib off of the specific module version pointers it is using to load the exact module versions that were asked for in the pipeline's setup.py. Alternately, it should look at the module versions (or paths?) it is actually getting in the workers and make sure that they are in agreement with what it had on the master, to at least fail before some subtle module version difference causes a problem for the user script.
This might be solved by a virtualenv for this particular pipeline, but if you really do want to provide a global command-line tool to people through the entry points system, having people need to activate a virtualenv every time they log in, just because the tool internally uses Toil, is kind of a dealbreaker.

Toil should integrate with the entry points system

It does.

and crib off of the specific module version pointers

AFAIK, it can't. I think this is not a bug in Toil but inherent in Python's module lookup mechanism. We work around all of those issues by only supporting virtualenv. The documentation for this was just merged. If you think Toil is doing something wrong or something is missing, could you be more specific on what concrete behavior is wrong or missing?
IOW, show me your sys.path and prove that something that appears later in sys.path is loaded in favor of sth that appears earlier.

having people need to activate a virtualenv every time they log in

You don't need to activate a virtualenv explicitly, just running an entry point (or any other executable) from the venv's bin directory will activate it on the fly.
My general approach to this is this: Python's software deployment system sucks. I can back this up with facts if necessary. It's a can of worms and we can't support every possible scenario, especially considering the fact that we have to replicate software to each worker. We have a set of supported deployment scenarios and that's it. I'm not convinced that what you are proposing (if I understand what you are proposing because it's a little bit unspecific) is a use case with general utility.

These are the docs I was referring to:
http://toil.readthedocs.io/en/latest/developing.html#deploying-a-workflow

More thoughts:

I am pretty sure that the entry point system wrappers are doing something to provide my master script with exactly the versions of the modules it asked for in setup.py

That's not my experience. The entry point's wrapper script (but I only know about console script entry points) only verifies the specific version of the package defining the entry point. Dependencies are not verified. So at best you get an error, but only an error (it does  not magically load the correct version if it appears somewhere else on sys.path) or no error at all if the wrong version of a dependency is loaded.

I think the real problem is that setup.py (through setuptools?) and pip
can't agree on where packages should be installed. If they did agree, I
would only have one version anyway, I think, and this wouldn't be a problem.
On Fri, Oct 21, 2016 at 5:10 AM, Hannes Schmidt<EMAIL_ADDRESS>wrote:

More thoughts:
I am pretty sure that the entry point system wrappers are doing something
to provide my master script with exactly the versions of the modules it
asked for in setup.py
That's not my experience. The entry point's wrapper script (but I only
know about console script entry points) only verifies the specific version
of the package defining the entry point. Dependencies are not verified. So
at best you get an error, but only an error (it does not magically load the
correct version if it appears somewhere else on sys.path) or no error at
all if the wrong version of a dependency is loaded.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/BD2KGenomics/toil/issues/1220#issuecomment-255363833,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE0_XycLcx-iycQCbxVvaxk_2JZKJRbBks5q2KuzgaJpZM4Kbcvf
.


Xdebug Console Error When Reading Context

The Xdebug Context is never populated because there is an error (xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 2, column 572) when trying to read the context value from Xdebug. I see the issue https://github.com/martomo/SublimeTextXdebug/issues/172, but I tried turning off super globals as well as switching to three different versions of Xdebug. None of those seemed to do the trick.
I've done my best to debug this myself, but after many hours I've come up short. If anyone has any suggestions I'd love to hear them. I've included the details of my setup below.
Environment
Sublime Text
Operating system:
Windows 10
Installed version/build:
Version 3.1.1, Build 3176
Python version:
3.3.6
Server
Operating system:
I'm trying to run the script locally using Wamp.
PHP/Xdebug version:
PHP: 7.0.10
Xdebug: I have tried 2.5.5, 2.6.0 and 2.7.0alpha
Configuration
php.ini/xdebug.ini
[xdebug]
;zend_extension = c:\wamp\bin\php\php7.0.10\ext\php_xdebug-2.5.5-7.0-vc14-x86_64.dll
;zend_extension = c:\wamp\bin\php\php7.0.10\ext\php_xdebug-2.6.0-7.0-vc14-x86_64.dll
zend_extension = c:\wamp\bin\php\php7.0.10\ext\php_xdebug-2.7.0alpha1-7.0-vc14-x86_64.dll

xdebug.remote_enable = 1
xdebug.remote_host = "localhost"
xdebug.remote_port = 9000
xdebug.remote_handler = "dbgp"
xdebug.remote_mode = req
xdebug.remote_connect_back = 0
xdebug.remote_autostart = 0
xdebug.remote_log = C:/wamp/logs/xdebug.log

xdebug.profiler_enable = 0
xdebug.profiler_enable_trigger = On
xdebug.profiler_output_name = cachegrind.out.%t.%p
xdebug.profiler_output_dir ="c:/wamp/tmp"
xdebug.show_local_vars=0
# ...

Packages/User/Xdebug.sublime-settings
{

    "debug": true,
    "super_globals": false,

}

*.sublime-project
{
	"folders":
	[
		{
			"path": "."
		}
	],
	"settings": {
        "xdebug": {
             "url": "http://localhost/wiredwebsites/",
             "path_mapping": {
             	"C:\\wamp\\www\\wiredwebsites\\" : "C:/wamp/www/wiredwebsites/",
   	      },
        }
    }
}

Logs
Console output:
Traceback (most recent call last):
  File "./python3.3/threading.py", line 901, in _bootstrap_inner
  File "C:\Users\......\AppData\Roaming\Sublime Text 3\Installed Packages\Xdebug Client.sublime-package\xdebug/session.py", line 148, in run
    self.execute(self.get_option('command'))
  File "C:\Users\......\AppData\Roaming\Sublime Text 3\Installed Packages\Xdebug Client.sublime-package\xdebug/session.py", line 240, in execute
    context = self.get_context_values()
  File "C:\Users\......\AppData\Roaming\Sublime Text 3\Installed Packages\Xdebug Client.sublime-package\xdebug/session.py", line 276, in get_context_values
    response = S.SESSION.read()
  File "C:\Users\......\AppData\Roaming\Sublime Text 3\Installed Packages\Xdebug Client.sublime-package\xdebug/protocol.py", line 195, in read
    document = ET.fromstring(data)
  File "./python3.3/xml/etree/ElementTree.py", line 1356, in XML
  File "<string>", line None
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 2, column 572

Packages/User/Xdebug.log:
I'm not including this because the contents is huge, but let me know if you need this information.

I'm getting the same error.
@jg314 Did you manage to get it working?

@RajeebTheGreat, sadly I haven't been able to solve it. It seems like a bug with the package itself, so the developer would most likely need to get involved.
If you haven't already I'd recommend checking out issue #172. There are some other suggestions in there that are worth trying.
Good luck and let me know if you find a solution.

Exact same error here. Tried with Xdebug 2.5.5, 2.60 and 2.7.0-alpha. macOS HS.

@martomo come back , please(

protocol.py after line 135 paste this:
elif text[1:-1] == 'quot':
text = "'"

@mercurykd if you really, really need to do some debugging and cannot wait for the maintainers of this repo to fix this issue, I suggest you try pugdebug, it's really cool.
Granted, you will have to change windows to Pugdebug to set breakpoints and debug the code, but it's a complete, proper front-end for Xdebug. 👍

@donotnoot I myself fixed, sublime-package is the same zip-archive. everything is working

@mercurykd Thanks a lot!

@mercurykd , thanks
tried to insert your code into protocol.py :
135                  pass
136                             elif text[1:-1] == 'quot':
137                             text = "'"
138                   else:
but after SublimeTextXdebug not working at all(even menu is grey)
what i didnt got?

@mercurykd, i tested on Window7x64,  could you please describe with more details witch file you edited ? I edited "Xdebug Client.sublime-package" in ...\Sublime Text 3\Installed Packages"

@RM4LA
I renamed the extension to zip from Xdebug Client.sublime-package, unpacked it, inserted the changes in the xdebug / protocol.py file, packed it back into zip, and renamed it back to Xdebug Client.sublime-package. Move to sublime folder

I've made PR based on @mercurykd code https://github.com/martomo/SublimeTextXdebug/pull/186

@mercurykd
xdebug client doesn't work when the source code to debug is symlinked to the project folder

Working Fine To me!

@RM4LA
I renamed the extension to zip from Xdebug Client.sublime-package, unpacked it, inserted the changes in the xdebug / protocol.py file, packed it back into zip, and renamed it back to Xdebug Client.sublime-package. Move to sublime folder

@mercurykd I changed the file as what you said. The menu turned grey. I'm running on Ubuntu 16.04. What might be a possible syntax error?

protocol.py after line 135 paste this:
elif text[1:-1] == 'quot':
text = "'"

@mercurykd what's your BTC address for donations 😂 This worked! After a restart of Sublime Text

Closing this issue as this should be resolved with release 1.1.2, in case the issue was not resolved please let me know.


Change the task steps

...to fix RWStore.properties destination

@DigitLib I believe I fixed this issue in #5, can you check?

@jonathangreen problem on CentOS was not defined $JAVA_OPT  after defining this in tomcat role it installed OK. I didn't know how to remove this PR and other connected with it...
I'll test #5 now and report it.

Think this one is good to close


regarding storing CA bundle in a secret to populate route certificates in openshift

so as mentioned in the readme file two annotations can point to different secrets to populate route certs.
one secret would contain the cert and the private key with annotations
cert-utils-operator.redhat-cop.io/certs-from-secret: ""
and another secret would contain only the CA bundle with annotation
cert-utils-operator.redhat-cop.io/destinationCA-from-secret: "" .
so the second tls secret should also contain the private key along with ca bundle or only the latter is enough?

and what if the route type is  edge, can the tls.cert , tls.key and the ca.cert be stored in a single secret to populate the route certificates?
or the ca.cert be stored in a diffferent tls secret than the tls.cert and tls.key ?
the CA bundle is a third party

how to use this operator to populate the route certificates in openshift if their is a third party ca bundle along with the cert and the private key?


Deletable codons.

Are the commands not supposed to be able to operate on as many things as possible? I think deleting and repairing codons (rgl values) is pretty obvious, but what about removing ugos, digesting waste, stuff like that.

removing ugos is possible apparently.


feat: included network_id as part of the primary key for fare_leg_rules.txt

Summary:
Closes #1889
gtrans-ca-us.zip
Expected behavior:
test dataset:
Before:

After:

Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Run the unit tests with gradle test to make sure you didn't break anything
[ ] Add or update any needed documentation to the repo
[x] Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
[x] Linked all relevant issues
[x] Include screenshot(s) showing how this pull request works and fixes the issue(s)

LGTM!


Feat | dark mode feature added

Hi!, I've just pushed a little contribution. Please, any comments just let me know.
I hope it could be helpful.
Regards.

Thanks @francosauchelli  for working on the issue. Sorry for late reply.
Also, apart from working on above comments , can you please resolve all prettier issues vercel is reporting issue while deploying.


Android group call throwing exception

Hi Thomas,
I am able to use your demo and able to do a video call but when I am using the same code with all the packages in another project solution then after generating token when I click on Call Group button, it is asking for permission, and after granting permission for everything, it throws this exception at this line:
_localVideoStream = new LocalVideoStream(camera, MainActivity.Instance);
Exception details:
{Java.Lang.NullPointerException: Attempt to invoke virtual method 'void android.app.Activity.requestPermissions(java.lang.String[], int)' on a null object reference
at Java.Interop.JniEnvironment+StaticMethods.CallStaticVoidMethod (Java.Interop.JniObjectReference type, Java.Interop.JniMethodInfo method, Java.Interop.JniArgumentValue* args) [0x0006e] in <94b04e1756104d1fa1d144932ae2720c>:0
at Java.Interop.JniPeerMembers+JniStaticMethods.InvokeVoidMethod (System.String encodedMember, Java.Interop.JniArgumentValue* parameters) [0x00018] in <94b04e1756104d1fa1d144932ae2720c>:0
at AndroidX.Core.App.ActivityCompat.RequestPermissions (Android.App.Activity activity, System.String[] permissions, System.Int32 requestCode) [0x00057] in D:\a\1\s\generated\androidx.core.core\obj\Release\monoandroid9.0\generated\src\AndroidX.Core.App.ActivityCompat.cs:529
at EiMMessenger.Droid.ACS.CallingManager.JoinGroup (System.Guid groupID) [0x00002] in C:\Data\ChatApp\SmallBusinessApp(Chat App)\EMiChatAPP\EiMMessenger\EiMMessenger.Android\ACS\CallingManager.cs:46
--- End of managed Java.Lang.NullPointerException stack trace ---
java.lang.NullPointerException: Attempt to invoke virtual method 'void android.app.Activity.requestPermissions(java.lang.String[], int)' on a null object reference
at androidx.core.app.ActivityCompat.requestPermissions(ActivityCompat.java:502)
at crc64ee486da937c010f4.ButtonRenderer.n_onClick(Native Method)
at crc64ee486da937c010f4.ButtonRenderer.onClick(ButtonRenderer.java:104)
at android.view.View.performClick(View.java:7125)
at android.view.View.performClickInternal(View.java:7102)
at android.view.View.access$3500(View.java:801)
at android.view.View$PerformClick.run(View.java:27336)
at android.os.Handler.handleCallback(Handler.java:883)
at android.os.Handler.dispatchMessage(Handler.java:100)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7356)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
}
All the project setting and versions are exactly same as the demo project but it's still not working.
Do you have any idea, how to fix it?

Hi @NeerajRai111
Could you check your manifest file against the demo and see if you are missing something ?

Hi @tompi,
I have copied everything from demo to the new project manifest. The only difference is the name of the package.

Sorry, I didnt read the stacktrace properly last time. The problem is most likely that you are not setting the MainActivity.Instance on start. Check usages of that in my app and copy it in yours, it should be set when you start calling.

Thanks @tompi,
I missed to write "Instance = this;" in OnCreate() function. It is working now!


Trie Search Prefix and delete code added

PR Checklist:

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is on refer on the language README.md file
[ ] My addition does not have a spelling problem
[x] My submission has a proper and user-friendly description of the algorithm
[] My submission has the time complexity of the algorithm
[ ] My submission has sample input-output of the program (NOT FOR PYTHON)

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] New algorithm
[ ] Optimization in previous algorithms
[ ] Code style update
[ ] Refactor
[ ] Documentation
[ ] Other, please describe:

Briefly describe the changes in this PR
Trie implementation with prefix search is added in the C++ folder.

Other information:

Hi @ashwath462,
Could you separate the algorithm in different pull request?

Sure Sir
On Wed, Oct 12, 2022 at 6:58 AM Ming Tsai @.***> wrote:

Hi @ashwath462 https://github.com/ashwath462,
Could you separate the algorithm in different pull request?
—
Reply to this email directly, view it on GitHub
https://github.com/MakeContributions/DSA/pull/1006#issuecomment-1275467688,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS4ZZOG5HJIV5V2L3AD2QXTWCYH43ANCNFSM6AAAAAARA3ADU4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Member

Sir i have done the changes Kindly look into it.


google-cloud-ops-agent-diagnostics service [Windows and Linux]

Description
The changes presented implement a new binary in the folder cmd/google_cloud_ops_agent_diagnostics that will run after the google_cloud_ops_agent_engine binary successfully generates and validates the required configurations for  fluent-bit and otelopscol. This binary will run as a service, in Windows and Linux, along side the execution of fluent-bit and otelopscol.
The purpose of the google-cloud-ops-agent-diagnostics service is to have a place to run diagnostics checks and actions during the execution of the Ops Agent. A non exhaustive list of this are :

Report Ops Agent Self Metrics related to the currently set configuration :

agent.googleapis.com/agent/ops_agent/enabled_receivers (Implemented in this PR)
agent.googleapis.com/agent/ops_agent/feature_tracking (Future Work)

Log Rotation for Fluent-bit Logs (Possible use case)
Report Ops Agent Health Metrics (Possible use case)

Related issue
b/232815588 | b/245344014
How has this been tested?

Integration Tests

Implemented a new test TestDiagnosticsCrashRestart to verify the diagnostics service restarts after manually stopping (pkill) the binary.
Added agent.googleapis.com/agent/ops_agent/enabled_receivers to the expected metrics verified by the TestDefaultMetricsNoProxy test.
In a following PR we can add the diagnosticsLivenessChecker to the opsAgentLivenessChecker. It can't be done in the same PR since it's used in TestUpgradeOpsAgent which compares to a previous version that doesn't have the diagnostics service.

Unit Tests

Added TestEnabledReceiversDefaultConfig unit test to verify the count of receivers in the default configurations is what we expect.

Manual Verification

Verified the correct functionality of the Diagnostics Service in a Windows VM ( windows-2019 ) and a Linux VM ( debian 10 ). The metrics were sent to the Monitoring API correctly and the service executes correctly.

Windows 2019

Debian 10

Checklist:

Unit tests

[ ] Unit tests do not apply.
[x] Unit tests have been added/modified and passed for this PR.

Integration tests

[ ] Integration tests do not apply.
[x] Integration tests have been added/modified and passed for this PR.

Documentation

[ ] This PR introduces no user visible changes.
[x] This PR introduces user visible changes and the corresponding documentation change has been made.

Minor version bump

[ ] This PR introduces no new features.
[ ] This PR introduces new features, and there is a separate PR to bump the minor version since the last release already.
[x] This PR bumps the version.

Current status:

The upstream otel SDK feature request has been fixed. (@franciscovalentecastro Is there a link to that if it's in GitHub?)
Design wise, the decision is to use a separate service and use otel SDK to ingest metrics.
The PR is now unblocked for code review. Braydon will be the primary approver for this PR. Other reviewers are welcome to add feedback. Please resolve the threads once your feedback is addressed to help us keep track of any open conversations that still need attention.

@qingling128 Adding elements to the current status update :

Discussed with @dashpole about sending metrics at different time intervals (e.g. one metric every minute, one metric every hour) and having different MeterProviders share the the same metric Exporter. Considering this for future addition of metrics. Solved an issue in https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/issues/499
Recurrent failure on integration tests tracked by b/240564518 shows in this PR. Discussed with @martijnvans and its unrelated to addition of a Diagnostics Service.

Most of the integration tests in https://github.com/GoogleCloudPlatform/ops-agent/pull/852/commits/b1b375625f9d2b6b94bc83217ccc855e1df833e5 and https://github.com/GoogleCloudPlatform/ops-agent/pull/852/commits/31e9b21039cf4bf5aa8ed05562d63c6de6cb662a PASS. Some details :

Build (SLES 12) failure is due to failure to get OSS Update repository.
Recurrent failure b/240564518 in Windows.


speculator: Tool to preview spec pull requests

Not the prettiest thing in the world, and horribly unperformant, but
useful :)

Otherwise LGTM


mock-client: 👀 implement ViewClient (work in progress)

see #3913, and #3588.
NB: this branch is based upon #3902.
this is a speculative hack at providing a ViewClient implementation for the mock client.
for now, only todo!() stubs are provided.

i'm going to close this, based on some conversation from yesterday. we would like to keep the mock client minimal, and using the "real" view server means we'll gain additional assurance that's working properly.


(Review Only)

Standby for real PR desription.

Coverage decreased (-0.5%) to 51.963% when pulling 453434d3e5367ce3714dac8040c600834c82622e on RickCarlino:webcam_feed_updates into 32f6733ec0f5d11b94ea41304713212e562004b3 on FarmBot:master.

Coverage increased (+1.007%) to 53.501% when pulling fe8cd05929373eb9c3e7cb3cd7aba545c3ad48e2 on RickCarlino:webcam_feed_updates into 32f6733ec0f5d11b94ea41304713212e562004b3 on FarmBot:master.

Coverage increased (+1.007%) to 53.501% when pulling cb1ce78a674f344664195716fa5eb673d483d138 on RickCarlino:webcam_feed_updates into 32f6733ec0f5d11b94ea41304713212e562004b3 on FarmBot:master.

Coverage increased (+1.007%) to 53.501% when pulling d90bfeba1f7a8a71b4fa978a4a86d00e89746b5a on RickCarlino:webcam_feed_updates into 32f6733ec0f5d11b94ea41304713212e562004b3 on FarmBot:master.

Coverage increased (+1.007%) to 53.501% when pulling d90bfeba1f7a8a71b4fa978a4a86d00e89746b5a on RickCarlino:webcam_feed_updates into 32f6733ec0f5d11b94ea41304713212e562004b3 on FarmBot:master.

Coverage increased (+1.007%) to 53.501% when pulling ae53684871ed8122a73339a261185ac15a054e7d on RickCarlino:webcam_feed_updates into 32f6733ec0f5d11b94ea41304713212e562004b3 on FarmBot:master.


[10.x] Remove unused variable in getClosure

It's for readability.

@taylorotwell
return $container->resolve(
    $concrete, $parameters, raiseEvents: false
);

Maybe this is better!
If this is approved, reopen.


Version 2.1 backport is incomplete

The master README says about Version 2.1

Backport of the 3.x.x changes to work on stable until Rust 2018 hits stable.

So I just tried to use generate_cargo_keys, but that does not seem to exist on that branch.

It was a backport of the 3.x changes into the 2.0 API, so that method won't exist.

Okay. The README sounds to me like the API is also backported (it's part of the "changes" sine it got, well, changed). Might be worth clarifying.

Sure, I can clarify.


Pin AWS CDK dependencies at 1.65.0

When trying to set the AWS Power Tuner UI up without the updated / pinned CDK versions, the deploy-infra operation fails with:

unable to determine cloud assembly output directory. Assets must be defined indirectly within a "Stage" or an "App" scope

From looking into the issue, I discovered that this is typically due to mismatched versions on CDK dependencies.

Apologies for the noise -- closing this PR, and will open a new one from a different branch from the forked repo


[WIP] Envoy v2 API support

What this PR does / why we need it:
Moving to Envoy V2 API
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #1257
Special notes for your reviewer:
Release note:

NONE

This is a WIP and long ways to go.

@rshriram: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
8fb8de112f6795e12eae37c5cf0c93692e494f8d
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

The .protos are from here, right?: https://github.com/envoyproxy/data-plane-api
Is there a way we can reference them instead of copying them?

I think @rshriram is nudging in my direction to set-up bazel for that ;)

Hey man, I am just trying to get things working in my gogland IDE. :P. And I did my due diligence on bazel for 2 hrs and failed as expected :P.

@rshriram: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
ff7cdba58f70230a17bdd905ca062939eeed60af
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


add failure metadata in upgrade tests

Part of the dtest failure audit. Adds metadata to the upgrade_tests module.

+1

Thanks, merging. (I should note that I've run these changes locally and they're fine.


Crash involving Valarian Conquest

When I summon a specific valarian warrior via spawn egg, or when this same sentity is dismounted from thoe horse he ussualy spawns with, the game just crashes and I get an:
java.lang.NullPointerException: Cannot invoke "net.minecraft.world.entity.Entity.m_20185_()" because "p_61926_" is null.
Suspected Mods:
Mine Cells (minecells), Version: 1.8.5
Mixin class: com.github.mim1q.minecells.mixin.entity.MineCellsBorderEntityMixin
Target: net.minecraft.world.entity.Entity
at TRANSFORMER/minecraft@1.20.1/net.minecraft.world.entity.Entity.handler$eik000$minecells$cancelStartRiding(Entity.java:15610)
Valarian Conquest (valarian_conquest), Version: 2.4
	at TRANSFORMER/valarian_conquest@2.4/net.mcreator.valarian_conquest.procedures.GuardValarianNoblemanProcedure.execute(GuardValarianNoblemanProcedure.java:16)

I don't know what any of these means but it only happens when minecells is present, so I assumed is not Valarian's fault
crash-2024-10-14_21.49.06-client.txt

Thanks for the report!
That mod seems to be made in MCreator, so I wouldn't be surprised if that was what caused the issue. I can't be sure since the code is now public.
This should also be fixable on my side though, I'll try to do that, reply here again and I'd appreciate a verification whether it works now


🐞 [BUG] - Blog card of home page not redirecting to Blog page.

Description
I'm in GSSOC'23
When clicking on Blog card of home page, it's not redirecting to Blog Page.
Current behaviour
It is linked to the home page and moving to the top of home page.
Expected behaviour
It should display Blogs Page.
Reproduction steps
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Screenshots

Logs
No response
Browsers
Chrome
OS
Windows
Are you contributing for a program ?
GSSoC2023
Code of Conduct

[X] I have read and agree to the Contributing Guidelines of this project.

@AmanJain18  Here

@AmanJain18  Here

Yes there I know backend work is going on that why and in my local it is already fixed.

Take up other issues or create new meaningful issue


Implement Function generate_count_score

For lines https://github.com/eeriemyxi/glowl/blob/main/glowl%2F__main__.py#L197 and
https://github.com/eeriemyxi/glowl/blob/main/glowl%2F__main__.py#L191, implement function generate_count_score.

Fixed with https://github.com/eeriemyxi/glowl/commit/0f0351da7d6daffc9b9a9da887a3e41ac38d61aa.

Fixed with https://github.com/eeriemyxi/glowl/commit/0f0351da7d6daffc9b9a9da887a3e41ac38d61aa.


Print console logs only when debug flag is set

Hi,
this adapter is working great and i am really enjoy using it. However it produces loads of logs. I thinkt it would be good to only print them, when the core has set the DEBUG flag.
If you want, I can only to a PR.
Best

The DeepstreamHub service is discontinued.


FIX: Invalid signature generation

This commit fixes an issue were the library is incorrectly normalizing and adding the request body when the content type is not form-encoded.  This results in an invalid signature being generated for the request.
The OAuth 1.0a specs states this about normalizing request parameters:

9.1.1.  Normalize Request Parameters
The request parameters are collected, sorted and concatenated into a normalized string:

Parameters in the OAuth HTTP Authorization header excluding the realm parameter.
Parameters in the HTTP POST request body (with a content-type of application/x-www-form-urlencoded).
HTTP GET parameters added to the URLs in the query part (as defined by [RFC3986] section 3).

Source: OAuth 1.0a Spec: Normalize Request Parameters
[FIX] Check the content type when preparing the signature parameters.

Thanks, could you please provide tests, this could also break some providers implementations I fear.

It might take me a while to get to writing some tests. FYI, I was integrating with MasterCard's MoneySend API when I hit the issue this PR solves. I've been trying to find other examples of public OAuth 1.0a APIs with non-form-encoded POST endpoints—even going through your own API directory—and I'm coming up empty.


Paper Structure

Identify the key points to put in the paper :
a. IDA for data quality explained in many papers  and documented clearly.
b. Going from Open Data to text book data or data example for research paper.
c. Raising awareness of tidy form of the data
d. Instead of wild data, more emphasise on Open Data and how to transfrom the open data to be text book data.
e. Linked to establish of data validation tecniques, e.g validate package.
The primary audience for the paper is someone who is going to use the open data. Secondary audience is the data curator itself.
Rethink the title regarding the primary audience of the paper.
In addition to introduction, Add example of the books using the data
Section 4 : Flow chart of the changes in data from raw to final data
Section 5: EDA examples of the tidy and clean data
Section 6: Summary , discussion

Section 2 The NLSY79 might be better with two subsections
2.1 Database
2. 2 Target data
where this section gives a brief overview of the wages data as used in singer and willet, that we are aiming to refresh

Hide some of the code. For example in 3.1.1, show the block on tidying the birth data, and gender/race but outline only the tidying of grade. The reader can be pointed to the supplementary code.
Similarly in 3.1.2, maybe just the first block, and bullet point the steps for the other blocks of code.

There are a couple of ?? in the paper which means the references/figures didn't get calculated properly. (eg in 3.2.1)

Fig 2, probably only needs 5 individuals shown, as example - with the caption pointing to the total number of subjects identified to have this type of pattern.
Section 3.2.1 could flow better, in terms of plot chosen and sequence of plots shown, to demonstrate the handling of extremes.
And maybe a little less code - outlined in the text, and referred to be in supplementary.

Hi Prof.Di,
I have made revisions based on your comments. However, for the flow of section 3.2.1, I am not quite sure, since I only changed the sequence of the two plots corresponding to the extreme values. Or should I compare more weights in a plot?
Best regards,
Dewi


Migrate off the deprecated setup.py

/usr/lib/python3.12/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!

        ********************************************************************************
        Please avoid running ``setup.py`` directly.
        Instead, use pypa/build, pypa/installer or other
        standards-based tools.

        See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
        ********************************************************************************

!!
  self.initialize_options()

The error in OP was actually on me for running setup.py directly when packaging it in AUR (now using build+install), but migrating to pyproject.toml is still a good idea.
Random (more complex) project as an example -
https://github.com/C0rn3j/sc-controller/blob/python3/pyproject.toml


fix: url not passed to transformStyle when using styleUrls

Fixed bug when url is not passed to transformStyle function when using styleUrls.

Thanks for the PR!


step 7 of tutorial 1

By running
"$ genie server --nlu-model file://OUTPUTDIR --thingpedia thingpedia.tt -l en-US"
output is coming as:
"
I 220118 16:31:25 transformer_lstm:79] Initializing encoder and decoder embeddings
[I 220118 16:31:26 transformer_lstm:108] Vocabulary has 28997 tokens
[I 220118 16:31:27 util:555] TransformerLSTM has 125,656,333 parameters
"
After that when "localhost:8400" is tried to open in browser then  "{"error":"Invalid endpoint"}" is coming. Can someone tell what to do??
Will it take too much time to deploy?? or some issue is there in my side??

It won't take long to deploy.
The only endpoint opened for the nlu server is /en/query. For example, if you want to get the result for utterance "get restaurants", you would go to localhost:8400/en/query?q=get restaurants

/en/query endpoint not working. Can you send any link where there is a discussion about api call

Here is some documentation about the API provided in our production server: https://wiki.genie.stanford.edu/en/api-references/nlp - it is the same as the one provided here. And the endpoint is implemented here: https://github.com/stanford-oval/genie-toolkit/blob/235171b1d1610a2b02a5a979d43a27e7ec6b9528/tool/server.ts#L222.
Both en and en-US should work as the locale. An example on our production server: https://nlp.genie.stanford.edu/en/query?q=get restaurants

I was asking for http://localhost:8400 as it is giving error and not using https://nlp.genie.stanford.edu/

Both localhost and our production server share the same implementation of the API call. We don't have separate documentation for API for genie-server at the moment, but simply replace the URL from nlp.genie.stanford.edu to localhost:8400, everything else should be the same.


check range of parameters

Codecov Report

Merging #2195 (28e6613) into main (a2969cb) will decrease coverage by 0.07%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##             main    #2195      +/-   ##
==========================================
- Coverage   61.78%   61.70%   -0.08%
==========================================
  Files         137      137
  Lines       24856    24907      +51
==========================================
+ Hits        15357    15370      +13
- Misses       7727     7756      +29
- Partials     1772     1781       +9

Impacted Files
Coverage Δ

cmd/mount.go
63.53% <0.00%> (-1.47%)
:arrow_down:

cmd/warmup.go
62.96% <0.00%> (-1.44%)
:arrow_down:

pkg/sync/config.go
83.33% <28.57%> (-8.98%)
:arrow_down:

cmd/format.go
60.30% <50.00%> (+0.24%)
:arrow_up:

cmd/gc.go
78.26% <60.00%> (-0.67%)
:arrow_down:

pkg/sync/sync.go
46.47% <100.00%> (ø)

pkg/vfs/reader.go
77.18% <0.00%> (-3.11%)
:arrow_down:

pkg/meta/tkv_etcd.go
76.21% <0.00%> (-0.89%)
:arrow_down:

cmd/mdtest.go
28.65% <0.00%> (-0.72%)
:arrow_down:

pkg/object/sftp.go
53.60% <0.00%> (-0.23%)
:arrow_down:

... and 7 more

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 a2969cb...28e6613. Read the comment docs.


Never had it to run and access it

Describe the bug
I have been trying to have this running on my Synology, but never with success
Environment Details (please complete the following information):

OS: Synology DSM 6.2.4
Browser Chrome on LinuxMint
Jellystat Version 1.0.8
Jellyfin Version 10.8.12

To Reproduce
my docker-compose looks like:
  jellystat:
    container_name: jellystat
    restart: always
    volumes:
      - $PERSIST/jellyfin/stat/data:/app/backend/backup-data
    environment:
      POSTGRES_USER: jellystat
      POSTGRES_PASSWORD: $DB_PASSWORD
      POSTGRES_IP: jellystat-postgres
      POSTGRES_PORT: 5432
      JWT_SECRET: $APP_KEY
    ports:
      - 6555:3000 #Server Port
      - 6556:3004 #Websocket port
    depends_on:
      jellystat-postgres:
        condition: service_started
    image: 'cyfershepard/jellystat:latest'

  jellystat-postgres:
    container_name: jellystat-postgres
    restart: always
    volumes:
      - $PERSIST/jellyfin/stat/db:/var/lib/postgresql/data
    environment:
      POSTGRES_DB: 'jfstat'
      POSTGRES_USER: jellystat
      POSTGRES_PASSWORD: $DB_PASSWORD
    security_opt:
      - no-new-privileges:true
    user: $PUID:$PGID
    healthcheck:
      test: ["CMD", "pg_isready", "-q", "-d", "jfstat", "-U", "jellystat"]
      timeout: 45s
      interval: 10s
      retries: 10
    image: 'postgres:alpine'

Expected behavior
be able to access the webui
Screenshots
If applicable, add screenshots to help explain your problem.
Task Logs
If applicable, add Task Logs for your problem.
Container Logs
2023-11-27T02:03:33.935314578Z
2023-11-27T02:03:33.936650350Z ><EMAIL_ADDRESS>start-app
2023-11-27T02:03:33.936918562Z > concurrently "npm run start-server" "npm start"
2023-11-27T02:03:33.937192341Z
2023-11-27T02:03:44.673281589Z | 0=0
2023-11-27T02:03:44.674294767Z [0] ><EMAIL_ADDRESS>start-server
2023-11-27T02:03:44.674519449Z [0] > cd backend && node server.js
2023-11-27T02:03:44.674683910Z | 0=0
2023-11-27T02:03:45.429832546Z | 0=1
2023-11-27T02:03:45.430731029Z [1] ><EMAIL_ADDRESS>start
2023-11-27T02:03:45.430948309Z [1] > react-scripts start
2023-11-27T02:03:45.431157089Z | 0=1
2023-11-27T02:04:01.067060658Z [0] error: database "jellystat" does not exist
2023-11-27T02:04:01.068209718Z [0]     at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:287:98)
2023-11-27T02:04:01.068520294Z [0]     at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:126:29)
2023-11-27T02:04:01.068766810Z [0]     at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:39:38)
2023-11-27T02:04:01.068986838Z [0]     at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42)
2023-11-27T02:04:01.069279685Z [0]     at Socket.emit (node:events:514:28)
2023-11-27T02:04:01.069547701Z [0]     at addChunk (node:internal/streams/readable:376:12)
2023-11-27T02:04:01.069799650Z [0]     at readableAddChunk (node:internal/streams/readable:349:9)
2023-11-27T02:04:01.070001606Z [0]     at Readable.push (node:internal/streams/readable:286:10)
2023-11-27T02:04:01.070283517Z [0]     at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
2023-11-27T02:04:01.106778349Z [0] FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
2023-11-27T02:04:01.111894735Z [0] FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
2023-11-27T02:04:12.120274671Z [0] Server listening on http://<IP_ADDRESS>:3003
2023-11-27T02:04:12.125463574Z [0] Activity Interval: 1000
2023-11-27T02:04:37.849236050Z [1] Browserslist: caniuse-lite is outdated. Please run:
2023-11-27T02:04:37.850185349Z [1]   npx update-browserslist-db@latest
2023-11-27T02:04:37.850435858Z [1]   Why you should do it regularly: https://github.com/browserslist/update-db#readme
2023-11-27T02:04:44.331587348Z [1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
2023-11-27T02:04:44.335524218Z [1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
2023-11-27T02:04:44.337795774Z [1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
2023-11-27T02:04:44.339446950Z [1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
2023-11-27T02:04:44.340942988Z [1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
2023-11-27T02:04:44.341289529Z [1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
2023-11-27T02:04:44.342232911Z [1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
2023-11-27T02:04:44.342516596Z [1] Proxy middleware applied
2023-11-27T02:04:44.979353874Z [1] (node:66) [DEP_WEBPACK_DEV_SERVER_ON_AFTER_SETUP_MIDDLEWARE] DeprecationWarning: 'onAfterSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option.
2023-11-27T02:04:45.054237027Z [1] (Use `node --trace-deprecation ...` to show where the warning was created)
2023-11-27T02:04:45.054525866Z [1] (node:66) [DEP_WEBPACK_DEV_SERVER_ON_BEFORE_SETUP_MIDDLEWARE] DeprecationWarning: 'onBeforeSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option.
2023-11-27T02:04:53.054114835Z [1] Starting the development server...
2023-11-27T02:04:53.422728881Z | 0=1
2023-11-27T02:09:57.971337144Z [1] Compiled with warnings.
2023-11-27T02:09:58.432913408Z | 0=1
2023-11-27T02:09:58.433257987Z [1] [eslint]
2023-11-27T02:09:58.433451034Z [1] src/pages/components/item-info.js
2023-11-27T02:09:58.433668306Z [1]   Line 105:4:  React Hook useEffect has a missing dependency: 'fetchData'. Either include it or remove the dependency array  react-hooks/exhaustive-deps
2023-11-27T02:09:58.433955927Z | 0=1
2023-11-27T02:09:58.434190748Z [1] Search for the keywords to learn more about each warning.
2023-11-27T02:09:58.434425780Z [1] To ignore, add // eslint-disable-next-line to the line before.
2023-11-27T02:09:58.434635278Z | 0=1
2023-11-27T02:09:58.434791919Z [1] WARNING in [eslint]
2023-11-27T02:09:58.434948113Z [1] src/pages/components/item-info.js
2023-11-27T02:09:58.435141983Z [1]   Line 105:4:  React Hook useEffect has a missing dependency: 'fetchData'. Either include it or remove the dependency array  react-hooks/exhaustive-deps
2023-11-27T02:09:58.435345387Z | 0=1
2023-11-27T02:09:58.435498698Z [1] webpack compiled with 1 warning
2023-11-27T02:10:01.162711483Z [1] Compiling...
2023-11-27T02:10:21.263216492Z [1] Compiled with warnings.
2023-11-27T02:10:21.264197200Z | 0=1
2023-11-27T02:10:21.265179461Z [1] [eslint]
2023-11-27T02:10:21.265447981Z [1] src/pages/components/item-info.js
2023-11-27T02:10:21.265650565Z [1]   Line 105:4:  React Hook useEffect has a missing dependency: 'fetchData'. Either include it or remove the dependency array  react-hooks/exhaustive-deps
2023-11-27T02:10:21.265871657Z | 0=1
2023-11-27T02:10:21.266186586Z [1] Search for the keywords to learn more about each warning.
2023-11-27T02:10:21.266405452Z [1] To ignore, add // eslint-disable-next-line to the line before.
2023-11-27T02:10:21.266598710Z | 0=1
2023-11-27T02:10:21.407729876Z [1] WARNING in [eslint]
2023-11-27T02:10:21.427413563Z [1] src/pages/components/item-info.js
2023-11-27T02:10:21.427588400Z [1]   Line 105:4:  React Hook useEffect has a missing dependency: 'fetchData'. Either include it or remove the dependency array  react-hooks/exhaustive-deps
2023-11-27T02:10:21.427784074Z | 0=1
2023-11-27T02:10:21.427917547Z [1] webpack compiled with 1 warning

Additional context
Add any other context about the problem here.

Can you try changing the postgres image to postgres:15.2. It could be that the image your using postgres:alpine isnt compatible or is a newer version of postgres

Same issue, I also changed the DB user to postgres this time, and it is still stuck as below till I sent you this reply
2023-11-27T06:51:11.034287559Z
2023-11-27T06:51:11.047640067Z ><EMAIL_ADDRESS>start-app
2023-11-27T06:51:11.047853629Z > concurrently "npm run start-server" "npm start"
2023-11-27T06:51:11.048145960Z
2023-11-27T06:51:34.724423266Z | 0=0
2023-11-27T06:51:35.139562888Z [0] ><EMAIL_ADDRESS>start-server
2023-11-27T06:51:35.139817325Z [0] > cd backend && node server.js
2023-11-27T06:51:35.140064643Z | 0=0
2023-11-27T06:51:35.140270084Z | 0=1
2023-11-27T06:51:35.140435094Z [1] ><EMAIL_ADDRESS>start
2023-11-27T06:51:35.140615363Z [1] > react-scripts start
2023-11-27T06:51:35.140801083Z | 0=1
2023-11-27T06:52:08.371841844Z [0] FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
2023-11-27T06:52:08.375136129Z [0] FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
2023-11-27T06:52:34.447186552Z [0] Server listening on http://<IP_ADDRESS>:3003
2023-11-27T06:52:34.450834206Z [0] Activity Interval: 1000
2023-11-27T06:53:28.169811136Z [1] Browserslist: caniuse-lite is outdated. Please run:
2023-11-27T06:53:28.202723589Z [1]   npx update-browserslist-db@latest
2023-11-27T06:53:28.203025875Z [1]   Why you should do it regularly: https://github.com/browserslist/update-db#readme
2023-11-27T06:53:38.352515968Z [1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
2023-11-27T06:53:38.357820362Z [1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
2023-11-27T06:53:38.366936965Z [1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
2023-11-27T06:53:38.367246338Z [1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
2023-11-27T06:53:38.420833061Z [1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
2023-11-27T06:53:38.421144246Z [1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
2023-11-27T06:53:38.421367274Z [1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
2023-11-27T06:53:38.421532931Z [1] Proxy middleware applied
2023-11-27T06:53:38.865906585Z [1] (node:66) [DEP_WEBPACK_DEV_SERVER_ON_AFTER_SETUP_MIDDLEWARE] DeprecationWarning: 'onAfterSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option.
2023-11-27T06:53:38.866500257Z [1] (Use `node --trace-deprecation ...` to show where the warning was created)
2023-11-27T06:53:38.908444009Z [1] (node:66) [DEP_WEBPACK_DEV_SERVER_ON_BEFORE_SETUP_MIDDLEWARE] DeprecationWarning: 'onBeforeSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option.
2023-11-27T06:53:57.630368402Z [1] Starting the development server...
2023-11-27T06:53:57.631705701Z | 0=1

can you try using image: 'cyfershepard/jellystat:unstable' and let me know?

The container does look like it started up correctly from your new logs, maybe the front end was still starting up, but try the unstable image, its much faster

and btw, it is really faster :)

Now I am getting this error when I enter the Jellyfin server info
http://<IP_ADDRESS>:8096/web/index.html#!/dashboard.html
and this is the log of it
2023-11-27T07:38:28.870459708Z INSERT INTO app_config ("JF_HOST","JF_API_KEY","APP_USER","APP_PASSWORD") VALUES (null,null,$1,$2)
2023-11-27T07:39:07.964837637Z {
2023-11-27T07:39:07.966119215Z   isValid: false,
2023-11-27T07:39:07.966431272Z   errorMessage: 'Error: TypeError: axios.get is not a function'
2023-11-27T07:39:07.966678244Z }
2023-11-27T07:39:21.478169152Z {
2023-11-27T07:39:21.479517365Z   isValid: false,
2023-11-27T07:39:21.479816749Z   errorMessage: 'Error: TypeError: axios.get is not a function'
2023-11-27T07:39:21.480095029Z }
2023-11-27T07:39:26.054332020Z {
2023-11-27T07:39:26.056630442Z   isValid: false,
2023-11-27T07:39:26.056923872Z   errorMessage: 'Error: TypeError: axios.get is not a function'
2023-11-27T07:39:26.057204437Z }

okay so seems like a corrupted database install, what youl need to do is delete the database container, delete the folders/volumes for the database, and start it again, itl recreate the database and it should work

Same error, same logs

also found this in the `postgres' container logs
2023-11-27T07:54:45.850333396Z 2023-11-27 07:54:45.849 UTC [1] LOG:  database system is ready to accept connections
2023-11-27T07:55:02.396993240Z 2023-11-27 07:55:02.396 UTC [81] ERROR:  relation "app_config" does not exist at character 15
2023-11-27T07:55:02.473895209Z 2023-11-27 07:55:02.396 UTC [81] STATEMENT:  SELECT * FROM app_config where "ID"=1
2023-11-27T07:55:02.474260495Z 2023-11-27 07:55:02.398 UTC [82] ERROR:  relation "app_config" does not exist at character 15
2023-11-27T07:55:02.474503477Z 2023-11-27 07:55:02.398 UTC [82] STATEMENT:  SELECT * FROM app_config where "ID"=1
2023-11-27T07:55:02.474721291Z 2023-11-27 07:55:02.401 UTC [80] ERROR:  relation "app_config" does not exist at character 15
2023-11-27T07:55:02.474948503Z 2023-11-27 07:55:02.401 UTC [80] STATEMENT:  SELECT * FROM app_config where "ID"=1
2023-11-27T07:55:02.527901337Z 2023-11-27 07:55:02.527 UTC [83] ERROR:  relation "app_config" does not exist at character 15
2023-11-27T07:55:02.528252510Z 2023-11-27 07:55:02.527 UTC [83] STATEMENT:  SELECT * FROM app_config where "ID"=1

huh, thats strange, this is clearly a postgres issue. Did the jellystat logs say if it created the database or if it skipped it because it already exists?

Logs for Jelly stat:
2023-11-27T08:42:09.959541288Z
2023-11-27T08:42:10.007426165Z ><EMAIL_ADDRESS>start
2023-11-27T08:42:10.007662144Z > cd backend && node server.js
2023-11-27T08:42:10.007777169Z
2023-11-27T08:42:32.890623644Z Error occurred while executing query: error: relation "app_config" does not exist
2023-11-27T08:42:32.891669085Z     at /app/node_modules/pg-pool/index.js:45:11
2023-11-27T08:42:32.891928740Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-11-27T08:42:32.892220275Z     at async Object.query (/app/backend/db.js:139:20)
2023-11-27T08:42:32.892443762Z     at async Config.getConfig (/app/backend/classes/config.js:7:36) {
2023-11-27T08:42:32.892671966Z   length: 109,
2023-11-27T08:42:32.892867265Z   severity: 'ERROR',
2023-11-27T08:42:32.893075624Z   code: '42P01',
2023-11-27T08:42:32.893313385Z   detail: undefined,
2023-11-27T08:42:32.893533747Z   hint: undefined,
2023-11-27T08:42:32.893740309Z   position: '15',
2023-11-27T08:42:32.893937905Z   internalPosition: undefined,
2023-11-27T08:42:32.894183192Z   internalQuery: undefined,
2023-11-27T08:42:32.894382747Z   where: undefined,
2023-11-27T08:42:32.894561147Z   schema: undefined,
2023-11-27T08:42:32.894758502Z   table: undefined,
2023-11-27T08:42:32.894948110Z   column: undefined,
2023-11-27T08:42:32.895176773Z   dataType: undefined,
2023-11-27T08:42:32.895377158Z   constraint: undefined,
2023-11-27T08:42:32.895593318Z   file: 'parse_relation.c',
2023-11-27T08:42:32.895803590Z   line: '1392',
2023-11-27T08:42:32.895999291Z   routine: 'parserOpenTable'
2023-11-27T08:42:32.896264465Z }
2023-11-27T08:42:32.896465659Z TypeError: Cannot read properties of undefined (reading 'length')
2023-11-27T08:42:32.896688386Z     at Config.getConfig (/app/backend/classes/config.js:12:20)
2023-11-27T08:42:32.896894001Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-11-27T08:42:32.902480300Z Error occurred while executing query: error: relation "app_config" does not exist
2023-11-27T08:42:32.902784553Z     at /app/node_modules/pg-pool/index.js:45:11
2023-11-27T08:42:32.902976769Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-11-27T08:42:32.903259842Z     at async Object.query (/app/backend/db.js:139:20)
2023-11-27T08:42:32.903454411Z     at async Config.getConfig (/app/backend/classes/config.js:7:36) {
2023-11-27T08:42:32.903613571Z   length: 109,
2023-11-27T08:42:32.903747532Z   severity: 'ERROR',
2023-11-27T08:42:32.903895903Z   code: '42P01',
2023-11-27T08:42:32.904133822Z   detail: undefined,
2023-11-27T08:42:32.904323282Z   hint: undefined,
2023-11-27T08:42:32.904486052Z   position: '15',
2023-11-27T08:42:32.904621678Z   internalPosition: undefined,
2023-11-27T08:42:32.904753000Z   internalQuery: undefined,
2023-11-27T08:42:32.904879924Z   where: undefined,
2023-11-27T08:42:32.905020167Z   schema: undefined,
2023-11-27T08:42:32.905244307Z   table: undefined,
2023-11-27T08:42:32.905444456Z   column: undefined,
2023-11-27T08:42:32.905641394Z   dataType: undefined,
2023-11-27T08:42:32.905818332Z   constraint: undefined,
2023-11-27T08:42:32.905928346Z   file: 'parse_relation.c',
2023-11-27T08:42:32.906020789Z   line: '1392',
2023-11-27T08:42:32.906177798Z   routine: 'parserOpenTable'
2023-11-27T08:42:32.906275583Z }
2023-11-27T08:42:32.906366782Z TypeError: Cannot read properties of undefined (reading 'length')
2023-11-27T08:42:32.906602915Z     at Config.getConfig (/app/backend/classes/config.js:12:20)
2023-11-27T08:42:32.906769680Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-11-27T08:42:32.911108518Z Error occurred while executing query: error: relation "app_config" does not exist
2023-11-27T08:42:32.911439346Z     at /app/node_modules/pg-pool/index.js:45:11
2023-11-27T08:42:32.911680407Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-11-27T08:42:32.911919213Z     at async Object.query (/app/backend/db.js:139:20)
2023-11-27T08:42:32.912205184Z     at async Config.getConfig (/app/backend/classes/config.js:7:36) {
2023-11-27T08:42:32.912473757Z   length: 109,
2023-11-27T08:42:32.912707157Z   severity: 'ERROR',
2023-11-27T08:42:32.912933072Z   code: '42P01',
2023-11-27T08:42:32.913183088Z   detail: undefined,
2023-11-27T08:42:32.913392673Z   hint: undefined,
2023-11-27T08:42:32.913604614Z   position: '15',
2023-11-27T08:42:32.913839416Z   internalPosition: undefined,
2023-11-27T08:42:32.914190789Z   internalQuery: undefined,
2023-11-27T08:42:32.914433704Z   where: undefined,
2023-11-27T08:42:32.914658581Z   schema: undefined,
2023-11-27T08:42:32.914882842Z   table: undefined,
2023-11-27T08:42:32.915319519Z   column: undefined,
2023-11-27T08:42:32.915551182Z   dataType: undefined,
2023-11-27T08:42:32.915755447Z   constraint: undefined,
2023-11-27T08:42:32.915962655Z   file: 'parse_relation.c',
2023-11-27T08:42:32.916223980Z   line: '1392',
2023-11-27T08:42:32.916411320Z   routine: 'parserOpenTable'
2023-11-27T08:42:32.916601078Z }
2023-11-27T08:42:32.916787847Z TypeError: Cannot read properties of undefined (reading 'length')
2023-11-27T08:42:32.916984683Z     at Config.getConfig (/app/backend/classes/config.js:12:20)
2023-11-27T08:42:32.917292988Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-11-27T08:42:32.917573050Z Error occurred while executing query: error: relation "app_config" does not exist
2023-11-27T08:42:32.917819382Z     at /app/node_modules/pg-pool/index.js:45:11
2023-11-27T08:42:32.918108958Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-11-27T08:42:32.918360144Z     at async Object.query (/app/backend/db.js:139:20)
2023-11-27T08:42:32.918585829Z     at async Config.getConfig (/app/backend/classes/config.js:7:36) {
2023-11-27T08:42:32.918796309Z   length: 109,
2023-11-27T08:42:32.919008998Z   severity: 'ERROR',
2023-11-27T08:42:32.919253939Z   code: '42P01',
2023-11-27T08:42:32.919456806Z   detail: undefined,
2023-11-27T08:42:32.919663909Z   hint: undefined,
2023-11-27T08:42:32.919860122Z   position: '15',
2023-11-27T08:42:32.920125450Z   internalPosition: undefined,
2023-11-27T08:42:32.920340722Z   internalQuery: undefined,
2023-11-27T08:42:32.920550130Z   where: undefined,
2023-11-27T08:42:32.920749940Z   schema: undefined,
2023-11-27T08:42:32.920950130Z   table: undefined,
2023-11-27T08:42:32.921191564Z   column: undefined,
2023-11-27T08:42:32.921416159Z   dataType: undefined,
2023-11-27T08:42:32.921637856Z   constraint: undefined,
2023-11-27T08:42:32.921833272Z   file: 'parse_relation.c',
2023-11-27T08:42:32.922018796Z   line: '1392',
2023-11-27T08:42:32.922323109Z   routine: 'parserOpenTable'
2023-11-27T08:42:32.922549460Z }
2023-11-27T08:42:32.922745733Z TypeError: Cannot read properties of undefined (reading 'length')
2023-11-27T08:42:32.922962438Z     at Config.getConfig (/app/backend/classes/config.js:12:20)
2023-11-27T08:42:32.923255927Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-11-27T08:42:32.927253648Z [JELLYSTAT] Database exists. Skipping creation
2023-11-27T08:42:32.939243033Z FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
2023-11-27T08:42:32.939951785Z FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
2023-11-27T08:42:41.410647221Z [JELLYSTAT] Server listening on http://<IP_ADDRESS>:3000
2023-11-27T08:42:41.450973953Z Activity Interval: 1000

Logs for Postgres
2023-11-27T08:40:00.007876270Z chmod: changing permissions of '/var/run/postgresql': Operation not permitted
2023-11-27T08:40:02.249689182Z The files belonging to this database system will be owned by user "postgres".
2023-11-27T08:40:02.250801468Z This user must also own the server process.
2023-11-27T08:40:02.251108559Z
2023-11-27T08:40:02.630519058Z The database cluster will be initialized with locale "en_US.utf8".
2023-11-27T08:40:02.630797799Z The default database encoding has accordingly been set to "UTF8".
2023-11-27T08:40:02.630985640Z The default text search configuration will be set to "english".
2023-11-27T08:40:02.631230818Z
2023-11-27T08:40:02.631378113Z Data page checksums are disabled.
2023-11-27T08:40:02.631530296Z
2023-11-27T08:40:02.631680847Z fixing permissions on existing directory /var/lib/postgresql/data ... ok
2023-11-27T08:40:02.642246020Z creating subdirectories ... ok
2023-11-27T08:40:02.642419067Z selecting dynamic shared memory implementation ... posix
2023-11-27T08:40:02.821004245Z selecting default max_connections ... 100
2023-11-27T08:40:02.911518181Z selecting default shared_buffers ... 128MB
2023-11-27T08:40:03.080829930Z selecting default time zone ... Australia/Melbourne
2023-11-27T08:40:03.145100762Z creating configuration files ... ok
2023-11-27T08:40:04.387661910Z running bootstrap script ... ok
2023-11-27T08:40:11.888138035Z performing post-bootstrap initialization ... ok
2023-11-27T08:40:26.770365695Z syncing data to disk ... ok
2023-11-27T08:40:26.771321814Z
2023-11-27T08:40:26.771526706Z
2023-11-27T08:40:26.771648758Z Success. You can now start the database server using:
2023-11-27T08:40:26.771802990Z
2023-11-27T08:40:26.771918146Z     pg_ctl -D /var/lib/postgresql/data -l logfile start
2023-11-27T08:40:26.772107378Z
2023-11-27T08:40:26.770694162Z initdb: warning: enabling "trust" authentication for local connections
2023-11-27T08:40:26.772496671Z initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
2023-11-27T08:40:28.895487839Z waiting for server to start....2023-11-27 19:40:28.895 AEDT [50] LOG:  starting PostgreSQL 15.2 (Debian 15.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-11-27T08:40:28.978297459Z 2023-11-27 19:40:28.978 AEDT [50] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-11-27T08:40:29.195233497Z 2023-11-27 19:40:29.194 AEDT [53] LOG:  database system was shut down at 2023-11-27 19:40:11 AEDT
2023-11-27T08:40:29.601102639Z 2023-11-27 19:40:29.600 AEDT [50] LOG:  database system is ready to accept connections
2023-11-27T08:40:29.695310653Z  done
2023-11-27T08:40:29.695545229Z server started
2023-11-27T08:40:31.137578108Z CREATE DATABASE
2023-11-27T08:40:31.139646746Z
2023-11-27T08:40:31.173006068Z
2023-11-27T08:40:31.173623171Z /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
2023-11-27T08:40:31.173898886Z
2023-11-27T08:40:31.177336695Z 2023-11-27 19:40:31.177 AEDT [50] LOG:  received fast shutdown request
2023-11-27T08:40:31.893904807Z waiting for server to shut down....2023-11-27 19:40:31.893 AEDT [50] LOG:  aborting any active transactions
2023-11-27T08:40:32.046280640Z 2023-11-27 19:40:31.910 AEDT [50] LOG:  background worker "logical replication launcher" (PID 56) exited with exit code 1
2023-11-27T08:40:32.046463161Z 2023-11-27 19:40:31.911 AEDT [51] LOG:  shutting down
2023-11-27T08:40:32.083228660Z 2023-11-27 19:40:31.952 AEDT [51] LOG:  checkpoint starting: shutdown immediate
2023-11-27T08:40:34.209006426Z ..2023-11-27 19:40:34.208 AEDT [51] LOG:  checkpoint complete: wrote 918 buffers (5.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.466 s, sync=1.029 s, total=2.297 s; sync files=250, longest=0.600 s, average=0.005 s; distance=4217 kB, estimate=4217 kB
2023-11-27T08:40:34.243252002Z 2023-11-27 19:40:34.240 AEDT [50] LOG:  database system is shut down
2023-11-27T08:40:34.295812564Z  done
2023-11-27T08:40:34.296230451Z server stopped
2023-11-27T08:40:34.352808860Z
2023-11-27T08:40:34.353146399Z PostgreSQL init process complete; ready for start up.
2023-11-27T08:40:34.353367445Z
2023-11-27T08:40:34.878747234Z 2023-11-27 19:40:34.878 AEDT [1] LOG:  starting PostgreSQL 15.2 (Debian 15.2-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-11-27T08:40:35.444260993Z 2023-11-27 19:40:35.443 AEDT [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2023-11-27T08:40:35.444568351Z 2023-11-27 19:40:35.443 AEDT [1] LOG:  listening on IPv6 address "::", port 5432
2023-11-27T08:40:35.522350808Z 2023-11-27 19:40:35.522 AEDT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-11-27T08:40:35.561299523Z 2023-11-27 19:40:35.560 AEDT [66] LOG:  database system was shut down at 2023-11-27 19:40:34 AEDT
2023-11-27T08:40:35.611715053Z 2023-11-27 19:40:35.611 AEDT [1] LOG:  database system is ready to accept connections
2023-11-27T08:42:32.867744387Z 2023-11-27 19:42:32.801 AEDT [154] ERROR:  relation "app_config" does not exist at character 15
2023-11-27T08:42:32.907482538Z 2023-11-27 19:42:32.801 AEDT [154] STATEMENT:  SELECT * FROM app_config where "ID"=1
2023-11-27T08:42:32.907677235Z 2023-11-27 19:42:32.800 AEDT [157] ERROR:  relation "app_config" does not exist at character 15
2023-11-27T08:42:32.907785655Z 2023-11-27 19:42:32.800 AEDT [157] STATEMENT:  SELECT * FROM app_config where "ID"=1
2023-11-27T08:42:32.907903376Z 2023-11-27 19:42:32.836 AEDT [158] ERROR:  database "jfstat" already exists
2023-11-27T08:42:32.908015266Z 2023-11-27 19:42:32.836 AEDT [158] STATEMENT:  CREATE DATABASE jfstat
2023-11-27T08:42:32.908183069Z 2023-11-27 19:42:32.801 AEDT [156] ERROR:  relation "app_config" does not exist at character 15
2023-11-27T08:42:32.908314263Z 2023-11-27 19:42:32.801 AEDT [156] STATEMENT:  SELECT * FROM app_config where "ID"=1
2023-11-27T08:42:32.908417540Z 2023-11-27 19:42:32.800 AEDT [155] ERROR:  relation "app_config" does not exist at character 15
2023-11-27T08:42:32.908518126Z 2023-11-27 19:42:32.800 AEDT [155] STATEMENT:  SELECT * FROM app_config where "ID"=1

I'm having the same issue after following all the steps from this thread

hi @mihaif7 , do you mind sharing your compose file and logs?

PS, when the image is up, once you setup jellystat and are taken to the dashboard, just restart your container, theres a bug i discovered while i was building that causes nothing to load from jellyfin. Restarting after you completed the setup fixes it but il put it a proper fix later as im about to leave work.

PS, when the image is up, once you setup jellystat and are taken to the dashboard, just restart your container, theres a bug i discovered while i was building that causes nothing to load from jellyfin. Restarting after you completed the setup fixes it but il put it a proper fix later as im about to leave work.

Same error I got, logs show that I have restart as well
2023-11-28T00:14:09.486902743Z
2023-11-28T00:14:09.488458521Z ><EMAIL_ADDRESS>start
2023-11-28T00:14:09.488739492Z > cd backend && node server.js
2023-11-28T00:14:09.488969881Z
2023-11-28T00:14:35.860573574Z [JELLYSTAT] Database exists. Skipping creation
2023-11-28T00:14:36.041450164Z FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
2023-11-28T00:14:36.041781484Z FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
2023-11-28T00:14:36.116815964Z Error occurred while executing query: error: relation "app_config" does not exist
2023-11-28T00:14:36.117257794Z     at /app/node_modules/pg-pool/index.js:45:11
2023-11-28T00:14:36.117500777Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-11-28T00:14:36.117713016Z     at async Object.query (/app/backend/db.js:139:20)
2023-11-28T00:14:36.117972915Z     at async Config.getConfig (/app/backend/classes/config.js:7:36) {
2023-11-28T00:14:36.118221338Z   length: 109,
2023-11-28T00:14:36.118469132Z   severity: 'ERROR',
2023-11-28T00:14:36.118683822Z   code: '42P01',
2023-11-28T00:14:36.118880117Z   detail: undefined,
2023-11-28T00:14:36.119129156Z   hint: undefined,
2023-11-28T00:14:36.119357236Z   position: '15',
2023-11-28T00:14:36.119535791Z   internalPosition: undefined,
2023-11-28T00:14:36.119719368Z   internalQuery: undefined,
2023-11-28T00:14:36.119941697Z   where: undefined,
2023-11-28T00:14:36.120209668Z   schema: undefined,
2023-11-28T00:14:36.120447297Z   table: undefined,
2023-11-28T00:14:36.120668528Z   column: undefined,
2023-11-28T00:14:36.120830538Z   dataType: undefined,
2023-11-28T00:14:36.120973438Z   constraint: undefined,
2023-11-28T00:14:36.121199481Z   file: 'parse_relation.c',
2023-11-28T00:14:36.121462388Z   line: '1449',
2023-11-28T00:14:36.121706589Z   routine: 'parserOpenTable'
2023-11-28T00:14:36.121881102Z }
2023-11-28T00:14:36.122720008Z TypeError: Cannot read properties of undefined (reading 'length')
2023-11-28T00:14:36.123019069Z     at Config.getConfig (/app/backend/classes/config.js:12:20)
2023-11-28T00:14:36.123344186Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-11-28T00:14:36.140497536Z Error occurred while executing query: error: relation "app_config" does not exist
2023-11-28T00:14:36.140786172Z     at /app/node_modules/pg-pool/index.js:45:11
2023-11-28T00:14:36.141003993Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-11-28T00:14:36.141283209Z     at async Object.query (/app/backend/db.js:139:20)
2023-11-28T00:14:36.141518334Z     at async Config.getConfig (/app/backend/classes/config.js:7:36) {
2023-11-28T00:14:36.141735276Z   length: 109,
2023-11-28T00:14:36.141939804Z   severity: 'ERROR',
2023-11-28T00:14:36.142231150Z   code: '42P01',
2023-11-28T00:14:36.142464908Z   detail: undefined,
2023-11-28T00:14:36.142668248Z   hint: undefined,
2023-11-28T00:14:36.142857077Z   position: '15',
2023-11-28T00:14:36.143282945Z   internalPosition: undefined,
2023-11-28T00:14:36.143560641Z   internalQuery: undefined,
2023-11-28T00:14:36.143768775Z   where: undefined,
2023-11-28T00:14:36.143949464Z   schema: undefined,
2023-11-28T00:14:36.144475410Z   table: undefined,
2023-11-28T00:14:36.145171107Z   column: undefined,
2023-11-28T00:14:36.251687010Z   dataType: undefined,
2023-11-28T00:14:36.252203479Z   constraint: undefined,
2023-11-28T00:14:36.252442495Z   file: 'parse_relation.c',
2023-11-28T00:14:36.252669005Z   line: '1449',
2023-11-28T00:14:36.252863736Z   routine: 'parserOpenTable'
2023-11-28T00:14:36.253095327Z }
2023-11-28T00:14:36.253362156Z TypeError: Cannot read properties of undefined (reading 'length')
2023-11-28T00:14:36.253543669Z     at Config.getConfig (/app/backend/classes/config.js:12:20)
2023-11-28T00:14:36.253725017Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-11-28T00:14:36.253946345Z Error occurred while executing query: error: relation "app_config" does not exist
2023-11-28T00:14:36.254222004Z     at /app/node_modules/pg-pool/index.js:45:11
2023-11-28T00:14:36.254412683Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-11-28T00:14:36.254610523Z     at async Object.query (/app/backend/db.js:139:20)
2023-11-28T00:14:36.254806938Z     at async Config.getConfig (/app/backend/classes/config.js:7:36) {
2023-11-28T00:14:36.254985850Z   length: 109,
2023-11-28T00:14:36.255227731Z   severity: 'ERROR',
2023-11-28T00:14:36.255417094Z   code: '42P01',
2023-11-28T00:14:36.255591010Z   detail: undefined,
2023-11-28T00:14:36.255754016Z   hint: undefined,
2023-11-28T00:14:36.255908243Z   position: '15',
2023-11-28T00:14:36.256111403Z   internalPosition: undefined,
2023-11-28T00:14:36.256304360Z   internalQuery: undefined,
2023-11-28T00:14:36.256460129Z   where: undefined,
2023-11-28T00:14:36.256579271Z   schema: undefined,
2023-11-28T00:14:36.256713784Z   table: undefined,
2023-11-28T00:14:36.256860802Z   column: undefined,
2023-11-28T00:14:36.257020450Z   dataType: undefined,
2023-11-28T00:14:36.257267892Z   constraint: undefined,
2023-11-28T00:14:36.257453995Z   file: 'parse_relation.c',
2023-11-28T00:14:36.257598625Z   line: '1449',
2023-11-28T00:14:36.257754846Z   routine: 'parserOpenTable'
2023-11-28T00:14:36.257904145Z }
2023-11-28T00:14:36.258140846Z TypeError: Cannot read properties of undefined (reading 'length')
2023-11-28T00:14:36.258347231Z     at Config.getConfig (/app/backend/classes/config.js:12:20)
2023-11-28T00:14:36.258479226Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-11-28T00:14:36.258635908Z Error occurred while executing query: error: relation "app_config" does not exist
2023-11-28T00:14:36.258818437Z     at /app/node_modules/pg-pool/index.js:45:11
2023-11-28T00:14:36.259021179Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-11-28T00:14:36.259311041Z     at async Object.query (/app/backend/db.js:139:20)
2023-11-28T00:14:36.259594237Z     at async Config.getConfig (/app/backend/classes/config.js:7:36) {
2023-11-28T00:14:36.259920403Z   length: 109,
2023-11-28T00:14:36.260453624Z   severity: 'ERROR',
2023-11-28T00:14:36.260657591Z   code: '42P01',
2023-11-28T00:14:36.260991577Z   detail: undefined,
2023-11-28T00:14:36.262421029Z   hint: undefined,
2023-11-28T00:14:36.262619895Z   position: '15',
2023-11-28T00:14:36.262789319Z   internalPosition: undefined,
2023-11-28T00:14:36.262957073Z   internalQuery: undefined,
2023-11-28T00:14:36.263170458Z   where: undefined,
2023-11-28T00:14:36.263364561Z   schema: undefined,
2023-11-28T00:14:36.263554138Z   table: undefined,
2023-11-28T00:14:36.263758997Z   column: undefined,
2023-11-28T00:14:36.263941285Z   dataType: undefined,
2023-11-28T00:14:36.264152858Z   constraint: undefined,
2023-11-28T00:14:36.264341333Z   file: 'parse_relation.c',
2023-11-28T00:14:36.264503287Z   line: '1449',
2023-11-28T00:14:36.264677063Z   routine: 'parserOpenTable'
2023-11-28T00:14:36.264874949Z }
2023-11-28T00:14:36.265070195Z TypeError: Cannot read properties of undefined (reading 'length')
2023-11-28T00:14:36.265328636Z     at Config.getConfig (/app/backend/classes/config.js:12:20)
2023-11-28T00:14:36.265532660Z     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-11-28T00:14:42.144206210Z [JELLYSTAT] Server listening on http://<IP_ADDRESS>:3000
2023-11-28T00:14:42.146424270Z Activity Interval: 1000
2023-11-28T00:16:17.311882404Z
2023-11-28T00:16:17.313471671Z ><EMAIL_ADDRESS>start
2023-11-28T00:16:17.313735318Z > cd backend && node server.js
2023-11-28T00:16:17.313934527Z
2023-11-28T00:16:39.197426400Z [JELLYSTAT] Database exists. Skipping creation
2023-11-28T00:16:39.210877001Z FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
2023-11-28T00:16:39.211924667Z FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
2023-11-28T00:16:39.814476622Z [JELLYSTAT] Server listening on http://<IP_ADDRESS>:3000
2023-11-28T00:16:40.417897169Z Activity Interval: 1000
2023-11-28T00:17:26.104804963Z INSERT INTO app_config ("JF_HOST","JF_API_KEY","APP_USER","APP_PASSWORD") VALUES (null,null,$1,$2)
2023-11-28T00:17:53.907009074Z {
2023-11-28T00:17:53.928890787Z   isValid: false,
2023-11-28T00:17:53.929192949Z   errorMessage: 'Error: TypeError: axios.get is not a function'
2023-11-28T00:17:53.929411432Z }

reset your database one remembering to delete any volumes/files more time and that will fix it

Pull the latest unstable image one more time to be safe

if you see this error then its not the latest image. 'Error: TypeError: axios.get is not a function'

Pull the latest unstable image one more time to be safe

Yaaaaay, it worked now

and this is the log for the container, as simple as this :)
2023-11-28T05:18:11.850897470Z
2023-11-28T05:18:11.906354408Z ><EMAIL_ADDRESS>start
2023-11-28T05:18:11.906578334Z > cd backend && node server.js
2023-11-28T05:18:11.906693946Z
2023-11-28T05:18:47.629583180Z [JELLYSTAT] Database exists. Skipping creation
2023-11-28T05:18:47.654070207Z FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
2023-11-28T05:18:47.656634751Z FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
2023-11-28T05:18:56.169707980Z [JELLYSTAT] Server listening on http://<IP_ADDRESS>:3000
2023-11-28T05:18:56.171168132Z Activity Interval: 1000
2023-11-28T05:19:14.358189861Z INSERT INTO app_config ("JF_HOST","JF_API_KEY","APP_USER","APP_PASSWORD") VALUES (null,null,$1,$2)
2023-11-28T05:19:26.747902205Z { isValid: true, errorMessage: '' }

and by the way, I used with postgres:alpine

awesome, wasnt sure if alpine worked thats why i recommended 15.2 but glad it works with that aswell


Support for hybrid (mixed discrete-continuous) systems

https://github.com/patrick-kidger/diffrax/issues/343 seems somewhat related but not quite the same.
It would be great to support discrete mode transitions between time steps. We can of course use the example in https://docs.kidger.site/diffrax/usage/manual-stepping/, but it seems that doesn't directly allow usage of adjoints?
To be honest, I'm not sure what the theory of adjoints is for hybrid systems is either.
Would be great to get thoughts on both fronts.

Probably this can/should be done using events (#387, an upcoming feature!) to detect whenever you want a discrete transition, and halting the solve. You can apply whatever change you would like, and then kick off another diffeqsolve afterwards (perhaps by placing the whole solve inside of a lax.while_loop or lax.scan).
Does that sound about right?

Yup.
I think this is the main resource on differentiable events: https://arxiv.org/abs/2011.03902

Yup. I think this is the main resource on differentiable events: https://arxiv.org/abs/2011.03902

Gotcha thanks. Revisiting this cause I have been finding the practical need to generally support states that aren't differential in time but transition from time step to time step. So sorta like an event is happening at every time step.
x_{t+1} = f(x_t)

Wondering if you have thoughts/guidance on handling this?

It's not clear to me that this is even a differential equation? You seem to have a discrete system.


Training speed

I was wondering how fast this is supposed to run? Over 6 hours it only trained 2k steps according to the wandb output and I have an A6000.
I want to run it for 1 million env steps. I believe that in metaworld max time steps per episode is 150. What does the parallel_actors argument doing? Maybe thats slowing it.
python ./examples/07_metaworld.py --run_name metaworld_ml45 --benchmark ml45 --buffer_dir buffer --parallel_actors 40 --memory_size 320 --timesteps_per_epoch 150 --agent_type multitask --max_seq_len 256 --memory_layers 3 --dset_max_size 25000 --epochs 6667 --val_interval 40

Hi @Lan131, the wandb link i put in the other issue (#62) has a full history of the command already done for you.
https://wandb.ai/jakegrigsby/amago-v3-reference/runs/gq9s8vxs?nw=nwuserjakegrigsby
The default x-axis of wandb "Step" doesn't mean anything useful --- it's the number of times wandb.log has been called. Instead, you want to display results by Wall Time, total_frames, Epoch, or the total frames of any particular task name (just search "total_frames" and you'll see 45 extra options).
The original meta-world RL^2 results are listed at 400M total timesteps (summing over the 45 tasks). The result in our paper Figure 4 goes for 100M. The wandb above happens to go to 200M before I stopped it. If you're looking for 1M total timesteps with an RL^2-like algo... I wouldn't recommend that... but I assume your paper is specifically about sample efficiency. It would take a totally different set of hparams to give that a reasonable shot.

The data collection process per epoch is described in a new tutorial here.

The parallel actors (40 in the command you're using), are sampling randomly from the 45 tasks each meta-reset. The ratio of experience collected to learning updates is the main factor in sample efficiency. You'd probably want to use fewer actors and do more gradient steps. Also, you'd probably want to use a shorter policy sequence length than the 256 used in the command. The "meta" aspect of MetaWorld ML45 actually doesn't take much memory and shorter policy lengths are generally more sample efficient. Something like 32 or even 16 might learn faster.
Episodes last for 500 timesteps, which is based on the garage max_pax_length.  Shorter would probably be better for sample efficiency because the way success rates are computed in Meta-World means that the agent is just kinda sitting there wasting steps once it's finished with most of the tasks.

Quick question, I thought val/Average Total Successes in peg-unplug-side-v2
was a success rate, but its 3 on that plot. Is it the average number of
successes in an episode?
Thanks,
Michael Lanier
On Sun, Nov 17, 2024 at 3:41 PM Jake Grigsby @.***>
wrote:

Hi @Lan131 https://github.com/Lan131, the wandb link i put in the other
issue (#62 https://github.com/UT-Austin-RPL/amago/issues/62) has a full
history of the command already done for you.
https://wandb.ai/jakegrigsby/amago-v3-reference/runs/gq9s8vxs?nw=nwuserjakegrigsby
The default x-axis of wandb "Step" doesn't mean anything useful --- it's
the number of times wandb.log has been called. Instead, you want to
display results by Wall Time, total_frames, Epoch, or the total frames of
any particular task name (just search "total_frames" and you'll see 45
extra options).
The original meta-world RL^2 results are listed at 400M total timesteps
(summing over the 45 tasks). The result in our paper Figure 4 goes for
100M. The wandb above happens to go to 200M before I stopped it. If you're
looking for 1M total timesteps with an RL^2-like algo... I wouldn't
recommend that... but I assume your paper is specifically about sample
efficiency. It would take a totally different set of hparams to give that a
reasonable shot.
Screen.Shot.2024-11-17.at.3.23.50.PM.png (view on web)
https://github.com/user-attachments/assets/a24baa79-7380-4ab8-8877-445806358a2a
The data collection process per epoch is described in a new tutorial here
https://github.com/UT-Austin-RPL/amago/blob/refactor-gc/tutorial.md.
Screen.Shot.2024-11-17.at.3.29.09.PM.png (view on web)
https://github.com/user-attachments/assets/4441fcab-50ef-4b3e-9a12-b62fb01195b6
The parallel actors (40 in the command you're using), are sampling
randomly from the 45 tasks each meta-reset. The ratio of experience
collected to learning updates is the main factor in sample efficiency.
You'd probably want to use fewer actors and do more gradient steps. Also,
you'd probably want to use a shorter policy sequence length than the 256
used in the command. The "meta" aspect of MetaWorld ML45 actually doesn't
take much memory and shorter policy lengths are generally more sample
efficient. Something like 32 or even 16 might learn faster.
Episodes last for 500 timesteps, which is based on the garage
max_pax_length.  Shorter would probably be better for sample
efficiency because the way success rates are computed in Meta-World means
that the agent is just kinda sitting there wasting steps once it's finished
with most of the tasks.
—
Reply to this email directly, view it on GitHub
https://github.com/UT-Austin-RPL/amago/issues/63#issuecomment-2481606715,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEGCGAQYBIPHWAI7N6VXIIL2BEEPVAVCNFSM6AAAAABR3JPBD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBRGYYDMNZRGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Oh never mind I see, there's a separate plot for the success rate.
ML
On Sun, Nov 17, 2024 at 6:49 PM michael lanier @.***> wrote:

Quick question, I thought val/Average Total Successes in
peg-unplug-side-v2 was a success rate, but its 3 on that plot. Is it the
average number of successes in an episode?
Thanks,
Michael Lanier
On Sun, Nov 17, 2024 at 3:41 PM Jake Grigsby @.***>
wrote:

Hi @Lan131 https://github.com/Lan131, the wandb link i put in the
other issue (#62 https://github.com/UT-Austin-RPL/amago/issues/62) has
a full history of the command already done for you.
https://wandb.ai/jakegrigsby/amago-v3-reference/runs/gq9s8vxs?nw=nwuserjakegrigsby
The default x-axis of wandb "Step" doesn't mean anything useful --- it's
the number of times wandb.log has been called. Instead, you want to
display results by Wall Time, total_frames, Epoch, or the total frames of
any particular task name (just search "total_frames" and you'll see 45
extra options).
The original meta-world RL^2 results are listed at 400M total timesteps
(summing over the 45 tasks). The result in our paper Figure 4 goes for
100M. The wandb above happens to go to 200M before I stopped it. If you're
looking for 1M total timesteps with an RL^2-like algo... I wouldn't
recommend that... but I assume your paper is specifically about sample
efficiency. It would take a totally different set of hparams to give that a
reasonable shot.
Screen.Shot.2024-11-17.at.3.23.50.PM.png (view on web)
https://github.com/user-attachments/assets/a24baa79-7380-4ab8-8877-445806358a2a
The data collection process per epoch is described in a new tutorial here
https://github.com/UT-Austin-RPL/amago/blob/refactor-gc/tutorial.md.
Screen.Shot.2024-11-17.at.3.29.09.PM.png (view on web)
https://github.com/user-attachments/assets/4441fcab-50ef-4b3e-9a12-b62fb01195b6
The parallel actors (40 in the command you're using), are sampling
randomly from the 45 tasks each meta-reset. The ratio of experience
collected to learning updates is the main factor in sample efficiency.
You'd probably want to use fewer actors and do more gradient steps. Also,
you'd probably want to use a shorter policy sequence length than the 256
used in the command. The "meta" aspect of MetaWorld ML45 actually doesn't
take much memory and shorter policy lengths are generally more sample
efficient. Something like 32 or even 16 might learn faster.
Episodes last for 500 timesteps, which is based on the garage
max_pax_length.  Shorter would probably be better for sample
efficiency because the way success rates are computed in Meta-World means
that the agent is just kinda sitting there wasting steps once it's finished
with most of the tasks.
—
Reply to this email directly, view it on GitHub
https://github.com/UT-Austin-RPL/amago/issues/63#issuecomment-2481606715,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEGCGAQYBIPHWAI7N6VXIIL2BEEPVAVCNFSM6AAAAABR3JPBD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBRGYYDMNZRGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Any shot you could invite me to this workspace? mlan is my user name. If I
am a collaborator I can make a custom graph (which is the average of all
the val/ average Trial success ) for the following tasks:
assembly, basketball, bin picking, box close, button press topdown,
button press topdown-wall, button press, button press wall, coffee button,
coffee pull, coffee push,
dial turn, disassemble, door close, door lock, door open, door unlock,
drawer close, drawer open ,
and faucet close
For the first 1 million frames.
But I don't seem to be able to add new graphs. Or if you make a view maybe
I can mess with it.
Thanks
ML
On Sun, Nov 17, 2024 at 6:50 PM michael lanier @.***> wrote:

Oh never mind I see, there's a separate plot for the success rate.
ML
On Sun, Nov 17, 2024 at 6:49 PM michael lanier @.***>
wrote:

Quick question, I thought val/Average Total Successes in
peg-unplug-side-v2 was a success rate, but its 3 on that plot. Is it the
average number of successes in an episode?
Thanks,
Michael Lanier
On Sun, Nov 17, 2024 at 3:41 PM Jake Grigsby @.***>
wrote:

Hi @Lan131 https://github.com/Lan131, the wandb link i put in the
other issue (#62 https://github.com/UT-Austin-RPL/amago/issues/62)
has a full history of the command already done for you.
https://wandb.ai/jakegrigsby/amago-v3-reference/runs/gq9s8vxs?nw=nwuserjakegrigsby
The default x-axis of wandb "Step" doesn't mean anything useful --- it's
the number of times wandb.log has been called. Instead, you want to
display results by Wall Time, total_frames, Epoch, or the total frames of
any particular task name (just search "total_frames" and you'll see 45
extra options).
The original meta-world RL^2 results are listed at 400M total timesteps
(summing over the 45 tasks). The result in our paper Figure 4 goes for
100M. The wandb above happens to go to 200M before I stopped it. If you're
looking for 1M total timesteps with an RL^2-like algo... I wouldn't
recommend that... but I assume your paper is specifically about sample
efficiency. It would take a totally different set of hparams to give that a
reasonable shot.
Screen.Shot.2024-11-17.at.3.23.50.PM.png (view on web)
https://github.com/user-attachments/assets/a24baa79-7380-4ab8-8877-445806358a2a
The data collection process per epoch is described in a new tutorial
here
https://github.com/UT-Austin-RPL/amago/blob/refactor-gc/tutorial.md.
Screen.Shot.2024-11-17.at.3.29.09.PM.png (view on web)
https://github.com/user-attachments/assets/4441fcab-50ef-4b3e-9a12-b62fb01195b6
The parallel actors (40 in the command you're using), are sampling
randomly from the 45 tasks each meta-reset. The ratio of experience
collected to learning updates is the main factor in sample efficiency.
You'd probably want to use fewer actors and do more gradient steps. Also,
you'd probably want to use a shorter policy sequence length than the 256
used in the command. The "meta" aspect of MetaWorld ML45 actually doesn't
take much memory and shorter policy lengths are generally more sample
efficient. Something like 32 or even 16 might learn faster.
Episodes last for 500 timesteps, which is based on the garage
max_pax_length.  Shorter would probably be better for sample
efficiency because the way success rates are computed in Meta-World means
that the agent is just kinda sitting there wasting steps once it's finished
with most of the tasks.
—
Reply to this email directly, view it on GitHub
https://github.com/UT-Austin-RPL/amago/issues/63#issuecomment-2481606715,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEGCGAQYBIPHWAI7N6VXIIL2BEEPVAVCNFSM6AAAAABR3JPBD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBRGYYDMNZRGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yeah the average total successes is [0, k], and we use k=3 by default. The success rate by episode is [0, 1].
If you're talking about 1M frames/timesteps per task (so 45M total) that's a lot more feasible with some minor tweaks to this command. I'd still recommend cutting the --max_seq_len from 256 to 128 or maybe lower.


feat: implement 0x3d - RETURNDATASIZE

Since
Byzantium
Group
Environmental Information
Description
0x3d - RETURNDATASIZE
Index 1 is top of the stack. See PUSH.NotesA sub context can be created with CALL, CALLCODE, DELEGATECALL or STATICCALL.Stack outputsize: byte size of the return data from the last executed sub context.Example
| Input | Output
-- | -- | --
1 |   | 32
Reproduce in playgroundError casesThe state changes done by the current context are reverted in those cases:Not enough gas.Stack overflow.

I can do this one


Auto enable filters and columns based on vcf header

Would be nifty to check at least header (best existence of actual tag for any variant) to see what filters and display columns to enable. Empty ones, or filters for non-annotated properties, make little sense.

Question is what to look for...

Precisely! #162?

Yes I know, we have tried to go down that road before and i'm a bit scared for that...

What went wrong then? Anything we can mitigate?
Options? Keep code dependent on particular annotation programs and versions ranges, and implement different annotator conventions as needed in various places, while keeping the number of things to read at a minimum?

Ideally, annotation programs would reach a concensus on field names in INFO ANN/CSQ..


ran clang-format-9 through repo

Summary of proposed changes:

Changed clang formatter to /opt/rocm/hcc/bin/clang-format, which is clang-format-9
Needs to pass CI
Format check still turned off

CI is failing with the PR. Can you check if this is due to change of header include order, similar to rocSPARSE?

CI is failing with the PR. Can you check if this is due to change of header include order, similar to rocSPARSE?

Yes, it's definitely failing due to the change of header include order. I can fix this when I get a moment.


get ride of the annoying replacement work by using envs

…n of brpc by using envs
What problem does this PR solve?
Issue Number:
Problem Summary:
What is changed and the side effects?
Changed:
Side effects:

Performance effects(性能影响):

Breaking backward compatibility(向后兼容性):

Check List:

Please make sure your changes are compilable(请确保你的更改可以通过编译).
When providing us with a new feature, it is best to add related tests(如果你向我们增加一个新的功能, 请添加相关测试).
Please follow Contributor Covenant Code of Conduct.(请遵循贡献者准则).

这样是不是搞个脚本更省事

这样是不是搞个脚本更省事

确实。

建议也同时修改下官网文档


zustand error

Describe the Bug
Hi,
on latest. When I try to use useReactFlow as describde in save and restore example on your website. I got this error below:
Error
Seems like you have not used zustand provider as an ancestor.
let me know if I'm missing something thanks
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
I followed the save/restore example here: https://reactflow.dev/docs/examples/save-and-restore/
when i try to use useReactFlow() I got this error.
Expected behavior
As User I expect to not have error when using some feature of the lib
Screenshots or Videos

Platform

OS: [macOS,  Linux]
Browser: [Chrome, Safari, Firefox]
Version: [latest v10.0.4]

Additional context
No response

Don't know of this is relevant, but I just had the same error after upgrading to 10.0.6. Completely rebuilding the app fixed it.

Is the component where you want to use useReactFlow a child component of <ReactFlow /> or wrapped with the <ReactFlowProvider /> ?

@moklick  yes it's wrapped with ReactFlowProvider

The component where you are using the hook needs to be wrapped with the ReactFlowProvider. You need to move it one level up.
<ReactFlowProvider>
  <ComponentWhereYouAreUsingTheHook />
</ReactFlowProvider>

Ah ok thanks i will try that
Le jeu. 24 mars 2022 à 11:39, Moritz Klack @.***> a
écrit :

The component where you are using the hook needs to be wrapped with the
ReactFlowProvider. You need to move it one level up.

—
Reply to this email directly, view it on GitHub
https://github.com/wbkd/react-flow/issues/2013#issuecomment-1077766761,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADQ42474HJJNLY2XZJ2RSKLVBSECNANCNFSM5RPZ45KQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Yasmine Bouchakour
Étudiante a l'École Polytechnique de Montréal
Département Génie Informatique
e-mail: @.***
Cell :(514)-638-6497

moving it a level up works thanks again

Here' s a link to the relevant docs for anyone who comes across this in the future.

"I also encountered this error while upgrading from V11 to V12. I tried using wrapping, but it’s not working. error : [React Flow]: Seems like you have not used zustand provider as an ancestor. Help: https://reactflow.dev/error#001"


Using SmartScraperGraph in a JupyterNotebook or within async functions raises RuntimeError: asyncio.run() cannot be called from a running event loop

Describe the bug
When using the SmartScraperGraph in environments that already have an active event loop, such as Jupyter Notebooks or within other async functions, the following error occurs: RuntimeError: asyncio.run() cannot be called from a running event loop
This error is caused by the asyncio.run() function being invoked inside the ScrapeGraphAI library's internals (e.g., within the document loaders). This results in a conflict when an active event loop is already running.
To Reproduce
Steps to reproduce the behavior:

Use SmartScraperGraph in a Jupyter Notebook or any environment where an event loop is already running (such as inside another async function).
Create a SmartScraperGraph instance and call the run() method.
Observe the RuntimeError.

Expected behavior
SmartScraperGraph should work seamlessly in environments where an event loop is already running. It should await async calls directly or provide alternatives that are compatible with environments that have active event loops (like Jupyter Notebooks or async frameworks).
Additional context

The error originates from calls to asyncio.run() inside the library, particularly when handling web sources (e.g., in scrapegraphai/docloaders/chromium.py).
A potential fix could involve checking if an event loop is already running and using await instead of asyncio.run() in such cases. I would be happy to make a PR with this implementation.

Pleas at the example notebook in the readme

Thanks @VinciGit00 for the quick response and the nest_asyncio suggestion. While it resolves the issue in Jupyter Notebooks, I believe it's more of a temporary workaround than a proper fix.

nest_asyncio is a patch, not a fix: It allows nested event loops, but it's not ideal for environments with multiple concurrent async tasks. It can introduce complexity and conflicts, especially in larger applications.

Proper Async integration will help the framework: Native async support without blocking the event loop is essential. The asyncio.run() call in https://github.com/ScrapeGraphAI/Scrapegraph-ai/blob/27ae896cb7f5046c4f5239bd4a072c265ce950e9/scrapegraphai/docloaders/chromium.py#L111 blocks the current event loop, which is contrary to the nature of asynchronous execution. This will negate the benefits of async IO, which is inefficient for apps with concurrent tasks.

Many developers work in fully async environments and expect libraries to behave consistently. I think native async support would enhance the usability and adoption of your library across diverse projects.

ok, can you suggest the modification in a pr?


BOM missing items

The BOM is missing the reference designators, micro USB cable, getting started guide, box, serial number sticker, 5V sticker and antennas.

Solved by https://github.com/beagleboard/beaglebone-black-wireless/commit/d2577b6cbad684950803ce611c8869a89bde5592