text:
rm seas_we

just removes seas_we. We have them in the git history, but put the routines also to this private repo
https://github.com/christophsax/bdfm-private/invitations

Codecov Report

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

@@            Coverage Diff             @@
##           master      #49      +/-   ##
==========================================
- Coverage   67.23%   60.01%   -7.22%
==========================================
  Files          11        8       -3
  Lines        1645     1408     -237
==========================================
- Hits         1106      845     -261
- Misses        539      563      +24

Impacted Files
Coverage Δ

src/BDFM.cpp
72.18% <0%> (-14.44%)
:arrow_down:

Continue to review full report at Codecov.

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

authors: christophsax codecov-io

repo: srlanalytics/bdfm


text:
Clan processes and adding friend is handled.

But I've made some chances in the database too,  so without them it
probably won't work.Plus , I added a features.txt so that we can easily
see what is working and what is not working, and the tests we've made,
which allows other people to contribute to the project even by just
testing the system.

Everything looks good here. In User.cpp you add a WIZ_NPC_SAY flag, I don't believe the client ever sends that packet but I could be wrong about this. What made you add the WIZ_NPC_SAY flag to the switch-statement?

Also, when you say that you made changes to the DB, what sort of changes are you talking about?

when you reach the end of the conversation with the npc, after pressing the OK button, source client sends the the packet with the number of 56 and it shows in the output tab of the VS.I just added there, so that it doesn't cause any confusion.

In database, I give knight user to the permissions like execute, insert, update etc. on KN_online.Moreover, I chanced 2 stored procedure. I will send images of them on skype.

This issue was moved to ApexKO/OpenKO#2

source: gharchive/pull-request

authors: onurcanbektas srmeier twostars

repo: srmeier/KnightOnline

license: MIT

license_type: permissive

license_source: github-api


text:
Files in Role Directory

Hi,
thank you for your great work an the fork. I'll switched to your fork and try to support this.
Currently I have a little problem. The Role uses the Playbookdir/files for the Java Files.
In my case i place it into the role dir/files, because I download it only once an use it for many systems.
Would it be possible to change this in the install.yml?
`
- name: copy RPM from local
copy:
src: "files/{{ jdk_tarball_file }}.rpm"
dest: "{{ java_download_path }}/{{ jdk_tarball_file }}.rpm"
when: use_rpm
- name: copy tarball from local
  copy:
    src: "files/{{ jdk_tarball_file }}.tar.gz"
    dest: "{{ java_download_path }}/{{ jdk_tarball_file }}.tar.gz"
  when: use_tarball

- name: copy .dmg from local
  copy:
    src: "files/{{ jdk_tarball_file }}.dmg"
    dest: "{{ java_download_path }}/{{ jdk_tarball_file }}.dmg"
  when: use_dmg

`
In my opinion, this should work for every user. If the file exists in role file/ then the file is pulled from there. If there is any file in playbook dir it will be used.

Thank you! I will look into this (and the other two issues) after I return from my vacation (July, 16th). All issues seem legit.

Hi @Tux12Fun, would you like to reuse the file, which is then in a different location than {{ playbook_dir }}/files or would you like to provide an alternative download url, which maybe points to a server in your local network?

Can you check if master fixes this issue for you?

source: gharchive/issue

repo: srsp/ansible-oracle-java


text:
I added .has functions, and added .is and .has functions for #

There was a bunch of functions of isTypeId
I needed hasTypeID, to scan whole messages for link types.
I then added a set of functions to test links for the "tag" sigil: #

Related: https://github.com/ssbc/secure-scuttlebutt/pull/135

it looks like you are running the regexp over the raw data - it would be better to traverse the parsed js object and then test each thing. checkout ssb-msgs#links https://github.com/ssbc/ssb-msgs/blob/master/index.js#L112-L120

does not this module work on strings of text?

@NHQ hmm I guess the links could be in markdown text... that isn't as bad... what kind of text are the links embedded in?

"data" is text, no matter what kind, markdown or plain.  The new functions
don't validate links, per se, they pluck them from texts.  The intended use
is between the textarea and the sbot post, for parsing plain texts and
getting ssb links.
On Mon, Jan 18, 2016 at 1:04 PM, Dominic Tarr notifications@github.com
wrote:

@NHQ https://github.com/NHQ hmm I guess the links could be in markdown
text... that isn't as bad... what kind of text are the links embedded in?
—
Reply to this email directly or view it on GitHub
https://github.com/ssbc/ssb-ref/pull/6#issuecomment-172653401.

That seems reasonable. Im going to post some code-review comments

Also, needs some test cases

yes, add test cases and we'll merge

authors: NHQ dominictarr pfraze

repo: ssbc/ssb-ref

license: mit

license_source: bigquery


text:
thegamedb API has changed?

Not sure, but I am a first time user of this scraper. I ran into the issue "It appears that thegamesdb.net isn't up". Looking at the code, it appears that the scraper attempts to GET http://thegamesdb.net/api/GetGame.php?id=1. After following the 302, a 404 is returned. From https://api.gamesdb.net , it appears the API has changed? Looks like one now needs to hit https://api.thegamesdb.net/Games/ByGameID?id=1&apikey=<API_KEY>.
Is this a recent change on gdb's side? Are there any plans to support the new API? I'm going to modify the code locally and hardcode an API Key temporarily and report back. Hopefully the endpoint paths (and addition of an API Key) is all that changed, and the scraper's parser can remain as-is.

Thanks for the heads-up. It looks like it has changed. I'll convert the
code over this weekend.
On Sat, Jul 14, 2018, 2:46 PM Paul Giblock notifications@github.com wrote:

Not sure, but I am a first time user of this scraper. I ran into the issue
"It appears that thegamesdb.net isn't up". Looking at the code, it
appears that the scraper attempts to GET
http://thegamesdb.net/api/GetGame.php?id=1. After following the 302, a
404 is returned. From https://api.gamesdb.net , it appears the API has
changed? Looks like one now needs to hit
https://api.thegamesdb.net/Games/ByGameID?id=1&apikey=<API_KEY>.
Is this a recent change on gdb's side? Are there any plans to support the
new API?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sselph/scraper/issues/230, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHwNVvmHz8t4SV0puzBSuZJOSf-MecQIks5uGjyhgaJpZM4VP9cK
.

Actually I may have to remove support for this service. The apiKey they mention is for the dev and is limited to something like 1000 queries per month. I think they designed the API quota for people running a web server or something that mirrors the data and not a scraper like mine.
Ideally they would reconsider and allow users to generate an API key and they'd use their own individual quota. The shared quota for an app like mine makes no sense.

Yeah. Batching sounds ideal to get the query count down. I haven't dug into the guts of the scraper enough to know how painful of a refactor that would be.

Good news: It seems that simply replace 'thegamedb.net' with 'legacy.thegamedb.net' is a usable stop-gap solution.

Nice.
Yeah the code today is my first Go code so not great to start and over the years has grown to become even less elegant. It does something roughly like the following so not laid out for batch processing in a single database.
for each rom found
for each DB:
if result:
break
else:
continue
It was more designed to try multiple databases to fill in gaps from that were missing. A refactor would probably need to do something like
for each DB:
for each batch of unscraped roms:
get results(batch)

Yeah, that makes sense, where unscraped roms is initially the full set. Then for each iteration of DB, it is only the set of unresolved roms from the previous iteration.

Thanks. Once I get an API key, I'll start working on it more seriously but if you have documentation of the response formats I can go ahead and have most of it ready. I'll start looking at refactoring the code to make batching a little easier since the new API seems to encourage that.

im afraid thats not available yet, as there are still few more things to implement, and they take priority over documentation.
and we hope that keys will be reissued by next weekend.

Hi, upon the change of the api it finds very little game images per system eg for nes in 400 roms it finds 200 for gameboy in 250 roms it finds 100 is this going to be fixed?

after updating the scraper the xml files has the same address : thegamesdb.net instead of the legacy.thegamesdb.net is this normal?

@symbios24 the legacy subdomain is the old site with only the domain change, so results returned shouldn't be any difference.
I changed any references I was able to find, but there is the possibility I missed some, which endpoint is still returning thegamesdb.net?

so far i tried the gameboy/nes/atari 2600 games and they have the thegamesdb.net to the xml

also atari 5200 is still returning thegamesdb.net i assume all the atari systems do the same

Thanks for the report. I may have forgotten to fix a url somewhere. I'll
also see if there was some change affecting images. I would expect them all
to work or to not work so it seems weird that it is hit or miss.
On Mon, Jul 23, 2018 at 8:45 AM symbios24 notifications@github.com wrote:

also atari 5200 is still returning thegamesdb.net i assume all the atari
systems do the same
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sselph/scraper/issues/230#issuecomment-407045371, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHwNVgxenne2LqkhqTnIpAhL6pCoYrj3ks5uJcVXgaJpZM4VP9cK
.

Another thing is the ps1-psx  pbp file extensions if barely finds any images is it possible to improve/fix this?

if you can change the scraper for pbp - psx files to download images/pictures based on the name of the game and not on the extension of the filename will be great.

It will require that this project (scraper) will request a API key, see this post.
So you can use the new API, eg: https://api.thegamesdb.net/#/Games/GamesByGameName

repo: sselph/scraper


text:
Use the tree-name from qastle rather than from the query

Currently, the tree-name comes from ServiceX in its query call. Ignore this - at let it come from the qastle that is passed in from the service.
This is part of getting https://github.com/ssl-hep/ServiceX/issues/186 finished.

This is actually secondary and can be completed at a later time - remove the tree_name_argument_name - when the generated func_adl` uproot stuff is cleaned up.


text:
main settings always return false?

when i save the timezone, it's always return false even given a correct timezone like "Asia/Shanghai"

Hi @hack2012,
This is indeed a bug. This will be fixed in a new release.

Fixed in new release.

repo: ssl/ezXSS


text:
Sonim XP3plus issues: status bar not visible, add-word shortcut and language switch shortcuts not available

This should probably be separate issues, but since they're all on the same device I'll just inventory them here.
In the Sonim XP3plus (XP3900), TT9 works, but there are several issues, which appear in every text field I've encountered so far:

The status bar with the predictive display, etc., does not show on the XP3plus. (Image attached). I've tried hitting "OK" as suggested in #429 and that doesn't seem to do anything. There's also no display of the current input method when switching with #. (In settings, "On screen layout" is set to "Suggestion list only".)
Pressing * does not bring up the add-word menu in any circumstance.
Long-pressing # does not bring up the language change menu, it just changes the input method like a short press.

It's entirely possible this is user error; I see there are other XP9plus users among the folks submitting issues and I don't see these reported yet. I'm happy to take suggestions or dig into the device settings on request if more information is needed.
This is a 3900 (P14301) from AT&T, unlocked.

You are experiencing #393 and maybe #490. Please, try the last APK posted in #393 and follow it for updates.

Long-pressing # does not bring up the language change menu, it just changes the input method like a short press.

There is no language menu. If you have enabled multiple languages, it just switches to the next one. This is probably confusing, when you can not see the UI.
I didn't know XP3900 and XP3800 behave so differently and rushed a bit with releasing v30.0. But now, I believe we have almost ironed the problems out.

Thanks!
For the language key, I guess I don't know what to expect since I don't see the interface (as you rightly understood!), but as far as I could tell, long pressing didn't change the language either (I have English and Spanish configured).
I'll try 30.14 and report back.

30.14 is a bit better -- I can get the interface to show! -- but the interaction to get it to show is unexpected. Hitting "OK" on the empty text field does nothing. Hitting OK after a typeahead has started gets the interface to display, and then through the end of the typing excursion it seems to work well, with the # and * buttons working precisely as described in the documentation.
It's a bit weird that i can hit "OK" to choose a typeahead suggestion and then hit "OK" again immediately to send the message, but if I recall there's a specific reason you can't or don't want to disable this functionality. (For what it's worth, the XP3900 has a "send" function coded to one of the dynamic keys in the messenger app but I'm not sure that there's the equivalent throughout the OS. If there were a way to disable the functionality just within the messenger app it could spare a user some premature message-sends. The default T9 implementation has this issue too, though!)
The behavior in other text fields is less predictable.  When composing a new message, in the "To" field, there doesn't seem to be a way to get the interface to show. Clicking "OK" before typing just moves to the message field. Clicking "OK" after you've started typing sets what you've typed so far as the intended contact (putting the typed text in an oval, etc.) even if the typed text doesn't match an existing contact or isn't a valid phone number or email. Then, pressing "Back" after that's happened causes the typeahead text to reappear in the contacts field (as though you'd started typing a new contact name) and must be cleared out before you can hit "back" to clear out the prematurely-created contact. When the typeahead does match a contact, you also need to hit "back" twice to backspace; the first "back" clears the display of the matched contacts, and the second "back" actually backspaces. This is probably a consequence of how the "back" button is assigned to both Clear and Backspace and I'm not sure there's much to be done about it, but thought it was worth sharing.
In the Contacts app, there also doesn't seem to be a way to get the UI to show. Hitting "OK" does nothing if no contacts match or selects the first contact that matches the current typeahead text. But the backspace behavior is better than  in the "to" field of the messenger composer.
I haven't tested  the web browser yet. The issues with the contacts and the "to" field of the messenger composer are less critical than the messenger text field, to be sure.
I can take a screencap of any of these interaction patterns if desired; let me know.

All I ask is to keep all communication about the OK key problem in one place. Let's continue the discussion in #393.
Btw, I've just posted a new beta APK in #393. Please try it out. I think I got it right this time.
As for your wish OK not to send messages at all, this is not a problem with TT9. The messaging app is designed to work this way. This is confirmed by the fact that the native keyboard does the same. I do not want to override the standard operation, because of many reasons, but I can add a compatibility setting, especially for the XP3900, just like there is "send with OK in Facebook Messenger" or "send with OK in Google Chat". If you like the idea, please create a new issue. I can do it at a later time.

I just tested your latest build from the xp3900-hacks-for-real branch and HOLY SMOKES IT WORKS!!!! No need to hit OK to get the suggestions to show, it just works in signal + the stock apps. Thank you so much!!!!

authors: neutralinsomniac sspanak wazroth


text:
fix: Sharp bundling install issue

The platform filter was in correct for npm thus it wasn't installing the optional dependencies for the new @img/sharp_* prebuilts but was actually installing the current platform specific ones (eg Darwin if running on Mac OS). Swapping to the os and libc flags fixes the issue as recommended in https://sharp.pixelplumbing.com/install#npm-v10
Fixes https://github.com/sst/ion/issues/197

@fwang looks like you might have the context from the original changes in this area

@thdxr Since I was on the same arch as the deployment target lambda I didn't notice that the arch flag also changed to cpu. So that needs updating looks like there is already a pr that has that fix and slightly more support for other packages https://github.com/sst/ion/pull/549/files might be worth merging otherwise ill make a pr that just fixes the flag for sharp

repo: sst/ion


text:
cannot even start a next.js project - user/amplify-dev is not authorized to perform: iot:DescribeEndpoint

First experience running SST for the first time.

sst bind next dev

Please enter a name you’d like to use for your personal stage. Or hit enter to use fabia:
Attention: SST now collects completely anonymous telemetry regarding usage. This is used to guide SST's roadmap.
You can learn more, including how to opt-out of this anonymous program, by heading over to:
https://docs.sst.dev/anonymous-telemetry
(node:22496) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use node --trace-warnings ... to show where the warning was created)
Error: User: arn:aws:iam::137541761544:user/amplify-dev is not authorized to perform: iot:DescribeEndpoint because no identity-based policy allows the iot:DescribeEndpoint action
Trace: AccessDeniedException: User: arn:aws:iam::137541761544:user/amplify-dev is not authorized to perform: iot:DescribeEndpoint because no identity-based policy allows the iot:DescribeEndpoint action
at throwDefaultError (C:\git\next\pime\node_modules@smithy\smithy-client\dist-cjs\default-error-handler.js:8:22)
at C:\git\next\pime\node_modules@smithy\smithy-client\dist-cjs\default-error-handler.js:18:39
at de_DescribeEndpointCommandError (C:\git\next\pime\node_modules@aws-sdk\client-iot\dist-cjs\protocols\Aws_restJson1.js:9968:20)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async C:\git\next\pime\node_modules@smithy\middleware-serde\dist-cjs\deserializerMiddleware.js:7:24
at async C:\git\next\pime\node_modules@aws-sdk\middleware-signing\dist-cjs\awsAuthMiddleware.js:14:20
at async StandardRetryStrategy.retry (C:\git\next\pime\node_modules@aws-sdk\middleware-retry\node_modules@smithy\middleware-retry\dist-cjs\StandardRetryStrategy.js:51:46)
at async C:\git\next\pime\node_modules@aws-sdk\middleware-logger\dist-cjs\loggerMiddleware.js:7:26
at async file:///C:/git/next/pime/node_modules/sst/iot.js:8:22
at async file:///C:/git/next/pime/node_modules/sst/iot.js:24:22
at async Object.handler (file:///C:/git/next/pime/node_modules/sst/cli/commands/bind.js:45:9)
at process. (file:///C:/git/next/pime/node_modules/sst/cli/sst.js:62:21)
at process.emit (node:events:525:35)
at process.emit (node:domain:489:12)
at process._fatalException (node:internal/process/execution:149:25)
at processPromiseRejections (node:internal/process/promises:288:13)
at process.processTicksAndRejections (node:internal/process/task_queues:96:32)
Need help with this error? Post it in #help on the SST Discord https://sst.dev/discord
Process finished with exit code 1

Can you post this on #help in Discord? It looks like your credentials aren't configured correctly?

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble

authors: jayair thdxr zurcacielos

repo: sst/sst


text:
Add flag for personal stage

Issue type
Request for feature addition
Requested change
Add a flag for personal stage like
   const isPersonalStage = $app.stage === process.env.USER ? true : false;
Reason for request
We are using RDS, VPC, CognitoUserPool and other resources in dev stage for personal stages. When onboarding new developer, sst.config.ts needs to be modified by the new developer to match personal stage name, if using ternary operator with matching personal stage name as suggested in get() functions. An out of the box flag like isPersonalStage combined with the get() function being able to reference resources in a specific stage like "dev", instead of hard-coding resource id would improve DX.

Oh that's an interesting point.

That said, how just checking if you are running in sst dev? Or are you running sst deploy on these personal stages?

running sst dev for personal stages. that still deploys AWS resources like RDS, VPC, etc, as expected.

additionally, I understand that referencing resources of a stage is within get() is probably difficult if the same resource type exists multiple types within same stage (like 2 or more RDS).
This function is optional but a flag for personal stage would be really great

So if you are only doing sst dev on these stages, you can $dev https://sst.dev/docs/reference/global#dev. Would that work?

Oh, I didn't even know that exists. Thanks!
Nevertheless, I do believe some form of safe referencing for stage names would be great. I am sure I am not the only who accidentally deployed to "productio" instead of "production" and went on a debugging spree before realizing the mistake.

I do believe some form of safe referencing for stage names

This is interesting. Do you mean having a restricted list of stages for your app?


text:
the documentation does not makes any sense

according to header files Ticker class does not even have update or start methods, the examples are not helpful enough to use this library

oh, I am looking an old version, my bad

repo: sstaub/Ticker


text:
Add configuration for zsh user

If zsh users add only this:
$ echo 'eval "$(rbenv init -)"' >> ~/.zshrc

you will get this error
/usr/local/Cellar/rbenv/0.4.0/libexec/../completions/rbenv.bash: command not found: complete

by adding zsh after -, we can solve this problem :)
$ echo 'eval "$(rbenv init - zsh)"' >> ~/.zshrc

Are you using latest version of rbenv from master? This parameter shouldn't be needed anymore.

oh really ? I just brew installed rbenv. Then I will update, Thanks

hmm I updated but still it shows me the error. So I think people who installed via brew and zsh users need to add - zsh.

@SamuraiT You really should install rbenv by cloning the repository. The last release (v0.4.0) was almost 2.5 years ago. AFAIK the recommended way to install rbenv is via git.

oh ok I didn't know it. Thank you I will install from git then.

Since installing rbenv via git is recommended, I will close this PR

authors: SamuraiT mislav thomasjo

repo: sstephenson/rbenv


text:
environment not properly cleaned up between build attempts?

a build failed, then when i cleared out /versions/2.2.0, it worked
Is that expected? Judging by the use of tmp directories and my previous anecdotal experience, I thought subsequent builds would be in totally different build directories.
➔ RUBY_CONFIGURE_OPTS="--with-readline-dir=/opt/local/include/readline" rbenv install 2.2.0; alert
rbenv: /Users/john/.rbenv/versions/2.2.0 already exists
continue with installation? (y/N) y
Downloading openssl-1.0.1j.tar.gz...
-> http://dqw8nmjcqpjn7.cloudfront.net/1b60ca8789ba6f03e8ef20da2293b8dc131c39d83814e775069f02d26354edf3
Installing openssl-1.0.1j...

BUILD FAILED (OS X 10.10.1 using ruby-build 20141225-7-g4aeeac2)

Inspect or clean up the working tree at /var/folders/rz/v9mzrh754gj87yv3wzt00d200000gp/T/ruby-build.20150107152934.72809
Results logged to /var/folders/rz/v9mzrh754gj87yv3wzt00d200000gp/T/ruby-build.20150107152934.72809.log

Last 10 log lines:
installing man7/des_modes.7
installing man3/dh.3
installing man3/dsa.3
installing man3/ecdsa.3
installing man3/engine.3
installing man3/err.3
installing man3/evp.3
installing man3/hmac.3
/bin/sh: /Users/john/.rbenv/versions/2.2.0/openssl/ssl/man/man3/hmac.3: Too many levels of symbolic links
make: *** [install_docs] Error 1
➔ mv /Users/john/.rbenv/versions/2.2.0 /tmp
➔ RUBY_CONFIGURE_OPTS="--with-readline-dir=/opt/local/include/readline" rbenv install 2.2.0; alert
Downloading openssl-1.0.1j.tar.gz...
-> http://dqw8nmjcqpjn7.cloudfront.net/1b60ca8789ba6f03e8ef20da2293b8dc131c39d83814e775069f02d26354edf3
Installing openssl-1.0.1j...
Installed openssl-1.0.1j to /Users/john/.rbenv/versions/2.2.0

Downloading ruby-2.2.0.tar.gz...
-> http://dqw8nmjcqpjn7.cloudfront.net/7671e394abfb5d262fbcd3b27a71bf78737c7e9347fa21c39e58b0bb9c4840fc
Installing ruby-2.2.0...
Installed ruby-2.2.0 to /Users/john/.rbenv/versions/2.2.0

  248.74s user 56.85s system 125% cpu 4:03.51 total
[3] 45935
[3]  + done       unicornleap > /dev/null

If ~/.rbenv/versions/2.2.0 didn't exist before installation, rbenv install would have removed it the installation failed. However, since it existed before, ruby-build will just try to install in the same location, and not remove the directory if installation failed.
Judging from your error message, it seems that Ruby's own make install is broken and you should report it with them. Ideally you would be able to reproduce this outside of ruby-build.

okay, closing this
(so it's not unexpected that the presence of versions/2.2.0 is causing the build to fail? builds happen directly in their ultimate destination directory?)

authors: jjb mislav

repo: sstephenson/ruby-build


text:
FCL - error

Dear all,
Pulling pinocchio from the repo master:master, I have an error with FCL when compiling:
include/pinocchio/multibody/geometry.hpp:144:36: error: no match for ‘operator==’ (operand types are ‘const fcl::CollisionResult’ and ‘const fcl::CollisionResult’)        return (fcl_collision_result == other.fcl_collision_result
README.md does not specify which fcl version to take and the dependency.
Best,
Olivier.

You're fully right.
The mandatory version of FCL is hpp-fcl (https://github.com/humanoid-path-planner/hpp-fcl/tree/devel) on the devel branch.
We have planed to put this version on the master branch of the repo and to push it on robotpkg.

I just pushed the devel on the master of hpp-fcl.

Thanks

authors: jcarpent olivier-stasse

repo: stack-of-tasks/pinocchio


text:
chore: updating copyright in LICENSE

Updating copyright in LICENSE from "Copyright (c) 2024 StackBlitz, Inc." to Copyright (c) 2024 StackBlitz, Inc. and bolt.diy contributors."
@patak-dev sorry for the multiple pings, I had to correct the pull request!

Should we just merge this?


text:
Cannot have anything generated in the "preview"

Describe the bug
Nothing was generated in the Preview
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-smiz49wq
Steps to reproduce

"preview" and only a white page output

Expected behavior
the code is not working and cannot resolve by ifself
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = 131.0.0.0
Major version = 131
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 82600186,
  "usedJSHeapSize": 78018890,
  "jsHeapSizeLimit": 4294705152
}
Username = domleungok
Chat ID = df3d6e9b681e

Additional context
No response

I am having similar issues and reported here 2 days ago but still no response from Bolt.  I am thinking of moving to a different tool....this is getting ridiculous as there seems to be zero support from bolt.new.  I am basically stuck...all the time I spent on this tool now seem to be a complete waste.

authors: Mike-Growx domleungok


text:
unable to fix the code

Describe the bug
So bolt is unable to fix the code and keeps showing this page after telling them to fix it for 3 times

Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-uqqmpaus
Validations

[X] Please make your project public or accessible by URL. This will allow anyone trying to help you to easily reproduce the issue and provide assistance.

Steps to reproduce

go to this website
and fix the error

Expected behavior
hopefully to fix the bug
so that i can keep working on the project
(sorry for noy being able to use the precise coding language)
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = 131.0.0.0
Major version = 131
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 70338678,
  "usedJSHeapSize": 68492450,
  "jsHeapSizeLimit": 2197815296
}
Username = Rebecca50603
Chat ID = cc5f96a75a13

Additional context
No response

Hi fixed your error
visit and click open in bolt
https://stackblitz.com/edit/sb1-hrgyn6yx

Hi thank you so much, it worked!
kind regards!
Labh @.***> 於 2024年12月17日 週二 下午6:11寫道：

Hi fixed your error
visit and click open in bolt
https://stackblitz.com/edit/sb1-hrgyn6yx
—
Reply to this email directly, view it on GitHub
https://github.com/stackblitz/bolt.new/issues/4332#issuecomment-2549234302,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDXT563M6AICR5VEJDJ7TAD2GBSN5AVCNFSM6AAAAABTYRXLLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBZGIZTIMZQGI
.
You are receiving this because you authored the thread.Message ID:
@.***>


text:
Make node analyzer return content sets, not cpes

Work in progress. For context, see #1053

We also must make sure that the GetNodeVulnerabilitiesRequest.Components from https://github.com/stackrox/scanner/blob/master/proto/scanner/api/v1/node_scan_service.proto contains the content_sets instead/additionally to CPEs.
Otherwise Central will not be able to pass the content_sets to Scanner through the GetNodeVulnerabilities API.

@vikin91:

I would love to see it in action on OpenShift to see that it works - we can make such test before of after this is merged as this feat is behind a feature flag, so I am leaving the choice to you.

I was planning to do that after working on the Scanner APIs. Glad you pushed towards it already. I will explore once that PR is merged.

repo: stackrox/scanner


text:
ROX-17183: Migrate persistent data #1 - scanner definition

Description
Add:

Large objects utilities in addition to the Gorm
Add migration to move scanner definition to blobstore with test.

Checklist

[ ] Investigated and inspected CI test results
[x] Unit test and regression tests added
~[ ] Evaluated and added CHANGELOG entry if required~
~[ ] Determined and documented upgrade steps~
~[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)~

If any of these don't apply, please comment below.
Testing Performed

Add unit test
Run a migration test to add a scanner bundle and then upgrade and then verify.
Run a migration without scanner bundle and upgrade and then verify.

In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

The discussions around why use Gorm was documented here. https://docs.google.com/document/d/1OLMylIIoPvqD0yqOdF6fJGF4kSCPznPjTse1pBjdkJE/edit#heading=h.bupciudrwmna
The scenarios are the same. Migrator needs to have backward compatibility to earlier versions while the schema and utilities evolving. The target is to have the schema stable while we still have the freedom to innovate and optimize the central without keep looking back.
Due to lack of facilities and experience, we are still copying codes of stores in addition to the schema in migrations which is cumbersome which IMHO are all feasible with Gorm. What is missing here is to have enough examples and utilities to show people how to create gorm-style migration. We only need to have a frozen schema instead of the whole store.
In this migration, large object is not supported by Gorm but it is easy to add it. This can be used in the future if any other migration may need it.

The discussions around why use Gorm was documented here. https://docs.google.com/document/d/1OLMylIIoPvqD0yqOdF6fJGF4kSCPznPjTse1pBjdkJE/edit#heading=h.bupciudrwmna
The scenarios are the same. Migrator needs to have backward compatibility to earlier versions while the schema and utilities evolving. The target is to have the schema stable while we still have the freedom to innovate and optimize the central without keep looking back.
Due to lack of facilities and experience, we are still copying codes of stores in addition to the schema in migrations which is cumbersome which IMHO are all feasible with Gorm. What is missing here is to have enough examples and utilities to show people how to create gorm-style migration. We only need to have a frozen schema instead of the whole store.
In this migration, large object is not supported by Gorm but it is easy to add it. This can be used in the future if any other migration may need it.

If you intend to use this as an example of a Gorm migration, it might be worth updating the README and pointing this out as an example.

/test ocp-4-10-qa-e2e-tests
/test ocp-4-13-qa-e2e-tests
/test gke-nongroovy-e2e-tests

repo: stackrox/stackrox


text:
Claims - GetClaim(s) API Response - CreatedDate

When fetching data using the GetClaims API endpoint, it's often useful to have information about when each claim was created. To facilitate this, I propose including a CreatedDate property in the response data.  This is part of the response from RB and easy to implement.
RB Documentation
CommencementDate - Stofndagur kröfu.

Meeting TN-FMÞ-VH7-16 saw this as an improvement that should be implemented.

Marked as processed in line with agreement on TN-FMÞ-VH7-18

authors: Kristinn-Stefansson thebingi

repo: stadlar/IST-FUT-FMTH


text:
Android Notifies of Mic activation

Not sure if there is a fix for this, but on my Google Pixel 2 every time the mix is turned on to record, and off to process the last statement my phone makes a noise to inform me the mic is being used. While useful, I find it to be distracting. If there was a way to even just turn off the "mic is turning off" noise, it would be less disruptive to the flow of recording for me.

I looked around and this is unsupported by the api. Hacking around it by trying to mute before and unmute after the voice rec beep proves annoying for the user and not working well. I always mute when the app is on. What I did was mute the mic on voice rec starting, but just not unmute

Alright. I figured that might be the case. I'll start doing the same.


text:
Allowing HPA behavior to be set

Adding the ability to set autoscaling behavior as per https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#configurable-scaling-behavior

@aslafy-z please review and merge

repo: stakater/application


text:
Port-For-Linux

Optimize Compatibility of Linux distributions (libdl). Considering the different versions of GCC, the portaudio library of the system is preferred. And added arm64 version of Linux file, adapted to Pi3 and Huawei&Pythom CPU

There will be native linux arm64 build soon

authors: mhbalthasar stakira

repo: stakira/OpenUtau


text:
integration tests for /api/studyplans + configure pipeline to run during pr

This PR:

implements integration tests for /api/study_plans endpoint - this will serve as a template for future tasks relating to API testing
configure CI Pipeline to run tests during pull requests

closes https://github.com/stamford-syntax-club/stamfordcenter-backend/issues/13

FFTM

FFTM

What does this mean XD? @Lxkas
Feel Fine To Me
OR
First Failure To Merge

FFTM

What does this mean XD? @Lxkas
Feel Fine To Me
OR
First Failure To Merge

Feel free to merge @chinathaip XD

FFTM

What does this mean XD? @Lxkas
Feel Fine To Me
OR
First Failure To Merge

Feel free to merge @chinathaip XD

555555555555555555555555555555 aight aight

authors: Lxkas chinathaip


text:
cholesky_corr_/cholesky_free_ etc. functions could use some TLC

Description
We call the cholesky functions pretty often, looking them over there may be some opportunities to spruce up and optimize them.

cholesky_corr_constrain
chol2inv
cholesky_corr_free
cholesky_factor_constrain
cholesky_factor_free

@syclik it looks like you were the last person to touch them meaningfully. Would you have any time to run through those and add docs?
Current Version:
v3.1.0

The docs should follow the discussion of transforms in the manual.
I think almost all of our transforms could be fruitfully vectorized.

On Feb 11, 2020, at 12:46 PM, Steve Bronder notifications@github.com wrote:
Description
We call the cholesky functions pretty often, looking them over there may be some opportunities to spruce up and optimize them.
• cholesky_corr_constrain
• chol2inv
• cholesky_corr_free
• cholesky_factor_constrain
• cholesky_factor_free
@syclik it looks like you were the last person to touch them meaningfully. Would you have any time to run through those and add docs?
Current Version:
v3.1.0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

authors: SteveBronder bob-carpenter

repo: stan-dev/math


text:
Bugfix/issue 1075 map rect fail

Summary
Fixes an issue with map_rect whenever threading is used.
Tests
There is a new test which triggers the issue:
test/unit/math/prim/mat/functor/map_rect_concurrent_threads_test.cpp
If you run this test on commit cb1f5b4 then it will fail as this has the current develop map_rect_concurrent with the failing behavior. The next commit then fixes the problem.
Side Effects
Nope.
Checklist

[X] Math issue #1075

[X] Copyright holder: Sebastian Weber
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[X] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[X] the code is written in idiomatic C++ and changes are documented in the doxygen

[X] the new changes are tested

Sorry, the EC2 Jenkins node became unavailable because the spot request gave us an instance type with not enough disk space 😓 Should be going again soon. Thanks for the fix! Will code review now...

This function is already refactored in the other parallel stl pr. Things are much cleaner there...and the code runs >30% faster.

Sounds good re: refactoring! I will take a look at that one next if no one else has.

Would you mind updating this with the related stuff from the parallel STL PR and also having the tests cycle through different job size / num thread combinations?

I can add a bit more cycling for varying the number of jobs (I think threads are already varied, but I can nest that in a loop for number of jobs).

They are, yep! Thanks, just figured we might as well be thorough given that we know the issues pop up with specific interactions there. And Daniel pointed out there was confusion between this and the other thread whether this had been tested with some specific job numbers that had failed the original fix, I think.
Which one of those two options regarding the parallel STL PR would you find easier? I think either would work (assuming the for_each stuff is left out of both versions and no new dependencies or compile flags are added, etc).

My preference ist the first one, but that would bring in the for each code...without any extra dependency or any extra compile time flag though.
Writing the code with for each makes it a lot cleaner to me.
If you want to avoid that for now, then that’s fine...your call.

Oh, I see what you mean. Let's keep this PR tiny and hope to get out a new Stan version with fixed threading ASAP. Perhaps just add the extra loop over job sizes to this one since it seems the rest of the nice-to-haves in the other PR are linked up with for_each? Thanks for fixing!

replaced by #1089


text:
Complex numbers get_real(), get_imag(), to_complex

Summary
Adding support for complex scalar functions get_real(), get_imag() and to_complex().
get_real() takes in a complex number and outputs its real component, get_imag() does the same but for the imaginary component.
to_complex() takes in either 0, 1, or 2 ints or doubles and returns a complex number with its real and imaginary component set to the inputs, and any unfilled components set to 0.
Tests
Test files are available in test/unit/math/mix/fun and are named get_real_test.hpp, get_imag_test.hpp and to_complex_test.hpp
Tests can be ran with:
./runTests.py test/unit/math/mix/fun/get_real_test.hpp
./runTests.py test/unit/math/mix/fun/get_imag_test.hpp
./runTests.py test/unit/math/mix/fun/to_complex_test.hpp
Side Effects
None
Release notes
Added complex scalar functions get_real(), get_imag(), and to_complex.
Checklist

[x] Copyright holder: Nicholas DiDio
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[x] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
dependencies checks pass, (make test-math-dependencies)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

So the tests for this are going to fail because it relies on Steve's apply-scalar-unary fix at https://github.com/stan-dev/math/pull/2549. I've tested both PR's together and it works. Not sure what to do about this, but it should work as soon as Steve's PR goes through.


text:
Improvements to unit tests

[ ] move class-level tests to class scope
[ ] investigate use of fixtures
[ ] naming convention for test input and output files to facilitate code reuse

http://pythontesting.net/framework/nose/nose-fixture-reference/#class
http://nose.readthedocs.org/en/latest/writing_tests.html

Not sure about all of these. Definitely need to move tests out of implementation files and into a testing directory.

Not really relevant or high-priority.

repo: standage/tag


text:
Fix constraint path issue

Fixes a crash that happens with the current shr_spec master branch.
Also adds a test for ConstraintsHistory, as suggested in the last PR review.

I actually refactored the target resolution code during the ballot push, so perhaps it was working before that and I broke it and now I'm fixing it again.  It only affects the case when you try to apply additional constraints on top of an includesType element -- which apparently we didn't do in the ballot material.

repo: standardhealth/shr-expand


text:
Release v2.0

Release v2.0
Scheduled Release Date: 22 August 2019
Daily Tasks
Mattermost Release Day
These are to be performed on the day Mattermost release is published.

[x] Code freeze to be done on this day. No more changes will be included in this release other than RC bug fixes.
[x] Create a new branch from master named release-x.y.z where x.y.z is the version being released.
[x] Create release issue on GitHub based on the release issue template.
[x] Update release issue with release cut date. This is the date when release branch is first created on remote.
[ ] Update release issue with scheduled release date.

Intermediate Days
These are to be performed starting as soon as Mattermost release day tasks are complete, until
Standup Raven scheduled release date.

[ ] Perform end to end testing on minimum up to the latest supported Mattermost version following recommended testing process.
[ ] Create GiHub issues for any bugs found.
[ ] Once testing is complete, begin with the bug fixes.
[ ] Cherrypick any bug fix which is applicable to master branch or other release.

Release Day
These are to be done on Standup Raven release day.

[ ] Generate release notes locally using what-the-changelog. Keep this handy as it will be needed later.
[ ] Create tag on release branch as vx.y.z. This will trigger the CircleCI release job.
[ ] Monitor the CircleCI job for success or faliure.
[ ] Once the CircleCI job is complete, verify that a new GitHub release has been created.
[ ] Verify that the GitHub release contains plugin distributions in attachments.
[ ] Use the changelog generated in earlier step along with changelog template, add the changelog to the GitHub release.
[ ] Update plugin version number on master for next release.
[ ] Close the release issue.

Release cut branch created - release-2.0.

repo: standup-raven/standup-raven


text:
intro.ipynb: Trial and Errors

First of all: I wish all papers came with step by step reproductions and iterative improvements like this one does. Kudos!
I attempted to run this on Colab and immediately ran into the problem of a missing OpenAI key. Easy enough, but conflicts with the statement in the notebook.  Then Programs 3 and 5 failed to complete -- no errors were reported but they ran much longer than reasonable so I eventually killed them.
I also noticed that when updating the LLM from text-davinci-002 to -003 most of the improvements provided by DSP went away: while -002 got a measly 23.1%, -003 was able to answer correctly 38.5% of the time in Program 1, and with -003 Program 2's score went DOWN to 30.8% while Program 4 "only" achieved 46.2%.  Certainly good, but not quite the improvement I hoped for. (Also, if using -002 shouldn't this be referred to as GPT3? IIRC the 3.5 moniker was introduced with -003? [My memory may be wrong, and Google wasn't helpful])  Since I could not make Program 5 run I'm not sure how much that improves things
I'd be interested in seeing how Turbo or 4 improves on the basic task, but have not myself attempted to change the API call.
FWIW this is my modestly forked version: https://gist.github.com/oaustegard/6edf2ed6f5b17a04d307a4593b6af3f7#file-intro-ipynb

Thanks for summarizing these findings!
I just opened the intro notebook in Colab and selected "Run all" and it works just fine without an API key. Notice you'll need an API key if you make changes to the models or examples. The original content doesn't need one.
GPT-3.5 includes text-davinci-002, -003, and the turbo model. See, e.g., https://platform.openai.com/docs/models/gpt-3-5
About the speed of runs, it seems that -003 (and possibly other models, I haven't check) is experiencing some load issues or throttling. I'm seeing much higher response times than usual (maybe 7x or more slower than usual), at least when generating many completions. You might want to try later, or reduce the n=20 setting that's doing self-consistency.
As for your evaluations, it's not unreasonable to look at these scores for some weak signal but keep in mind these are 13 examples and a % score here means very little. What they're useful for is the instructiveness of inspecting individual examples and seeing the patterns of mistakes in each program and LLM pair. We note in the notebook: "This tiny set is not meant to be a reliable benchmark, but it'll be instructive to use it for illustration." So don't read much into these scores.
If you're looking for a more reliable evaluation, check out the paper. It has tests at a much larger scale.
Anyway, I ran them for you with -003. Program 3 gets 46.2%, Program 4 gets 53.8%, and Program 5 gets a 69.2%. Seems reasonable to me: all scores are within 1-2 questions from the davinci-002 runs, as you'd expect from an LLM upgrade that's reported to lower academic benchmark scores.
As for Program 2 going down by one example from Program 1 with -003, that's not necessarily surprising. Indeed, they perform very close to one another in the original -002 run anyway. Program 2 isn't something we advise you to use. Indeed, this is the retrieve-then-read paradigm that we're advocating the need to go beyond in DSP. The goal of the notebook isn't to show some single best system; it's show the scope of thing you can implement and DSP and how it's done, and why it makes sense and what the tradeoffs are. That's why we don't have a UI demo of some cool program; we take you on the journey of building five different programs of varying complexity.
Think of DSP like PyTorch. We're not telling you Program 2 is a better program than program 1 (although, at large scale, it does work better on many tasks!). We're saying there's a natural program that can be built here with our primitives, and here's how it can be done. That's like a PyTorch tutorial saying here's how to do a CNN and here's how to do a Transformer. We're not endorsing the specific architecture of each program.
Hope this breakdown helps! Check out the compiler notebook too, while you're at it! Expect more large releases around the compiler quite soon.

My apologies: I realize a number of these issues are due to me running the notebook from Github: I started running into similar issues with compiler then thought; this can't be right and ran in the "native" environment instead and can confirm your results -- I had hoped to correct my findings before you noticed the errant issue-filing...
Again, I do wish every academic paper came with this type of iterative demonstration: now that I see Program 5 run to completion the results are very encouraging, and I'm surprised I haven't seen more discussion of this approach among the explosion of LangChain/LlamaIndex RAC use-cases and how-tos.
Closing this as a case of PEBCAK. Thanks again!

No worries at all! Always happy to help as issues arise. We do need to update a lot of the material and release more soon.

authors: oaustegard okhat

repo: stanfordnlp/dsp


text:
it dosen'y work

Description
whenever i try to open a show or a movie it says no extractore found an it just stay black
Provider
All
Reproduction steps
i open app
i choose an provider
i open a show
it says no extractor found
Operating system
All
Logs
No response
Please confirm the following

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] If related to a provider, I have checked the site and it works, but not the app.

Same issue Here on Android TV

repo: stantanasi/streamflix


text:
bump fontawesome to 4.3.0

for moar awesomeness

Meh, eff'ed this up somehow -.-


text:
Add exception mappers for grpc status runtime exception and ErrorCodes

What this PR does:
Which issue(s) this PR fixes:
Fixes #
Checklist

[x] Changes manually tested
[x] Automated Tests added/updated
[ ] Documentation added/updated
[ ] CLA Signed: DataStax CLA

@ivansenic I saw in the description of the ticket that an implementation was needed for io.stargate.web.impl.JerseyViolationExceptionMapper - but I'm not sure why that's the case, since that exception is only in dropwizard. Did you mean for there to be some other general exception that needed special handling?

@ivansenic I saw in the description of the ticket that an implementation was needed for io.stargate.web.impl.JerseyViolationExceptionMapper - but I'm not sure why that's the case, since that exception is only in dropwizard. Did you mean for there to be some other general exception that needed special handling?

@EricBorczuk yes I thought about the validation exception that would be raised in the Quarkus.. Not sure what that would be, maybe check the docs or the source code in Quarkus and implemented exception handlers.. we definitely do not need anything from dropwizard..

The Exception thrown by the validations in quarkus is just the plain javax.validation.ValidationException - I added a mapper for it!

With the ExceptionMapper, the nearest superclass of the Exception that's thrown is the mapper that's used - so I think a RuntimeException mapper should work for the generic case. Will add that!

authors: EricBorczuk ivansenic

repo: stargate/stargate


text:
dev: atty security advisory

There is a low-risk security advisory for atty which various cairo crates depend on indirectly via colored and env_logger. env_logger can be upgraded to remove the dep, but colored appears to be a bit slower moving.

Results for pathfinder: cargo tree --inverse atty
atty v0.2.14
├── colored v2.0.0
│   ├── cairo-lang-parser v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
│   │   ├── cairo-lang-compiler v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
│   │   │   └── cairo-lang-starknet v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
│   │   │       └── pathfinder v0.6.3 (/home/mirko/projects/starknet/pathfinder/crates/pathfinder)
│   │   ├── cairo-lang-defs v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
│   │   │   ├── cairo-lang-compiler v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   │   ├── cairo-lang-lowering v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
│   │   │   │   ├── cairo-lang-compiler v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   │   │   ├── cairo-lang-sierra-generator v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
│   │   │   │   │   ├── cairo-lang-compiler v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   │   │   │   └── cairo-lang-starknet v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   │   │   └── cairo-lang-starknet v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   │   ├── cairo-lang-plugins v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
│   │   │   │   ├── cairo-lang-compiler v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   │   │   ├── cairo-lang-sierra-generator v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   │   │   └── cairo-lang-starknet v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   │   ├── cairo-lang-semantic v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
│   │   │   │   ├── cairo-lang-compiler v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   │   │   ├── cairo-lang-lowering v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   │   │   ├── cairo-lang-plugins v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   │   │   ├── cairo-lang-sierra-generator v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   │   │   └── cairo-lang-starknet v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   │   ├── cairo-lang-sierra-generator v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   │   └── cairo-lang-starknet v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   ├── cairo-lang-lowering v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   ├── cairo-lang-plugins v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   ├── cairo-lang-semantic v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   ├── cairo-lang-sierra-generator v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   │   └── cairo-lang-starknet v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
│   ├── cairo-lang-parser v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
│   │   ├── cairo-lang-compiler v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
│   │   │   └── cairo-lang-starknet v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
│   │   │       └── pathfinder v0.6.3 (/home/mirko/projects/starknet/pathfinder/crates/pathfinder)
│   │   ├── cairo-lang-defs v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
│   │   │   ├── cairo-lang-compiler v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   │   ├── cairo-lang-lowering v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
│   │   │   │   ├── cairo-lang-compiler v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   │   │   ├── cairo-lang-sierra-generator v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
│   │   │   │   │   ├── cairo-lang-compiler v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   │   │   │   └── cairo-lang-starknet v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   │   │   └── cairo-lang-starknet v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   │   ├── cairo-lang-plugins v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
│   │   │   │   ├── cairo-lang-compiler v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   │   │   ├── cairo-lang-sierra-generator v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   │   │   └── cairo-lang-starknet v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   │   ├── cairo-lang-semantic v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
│   │   │   │   ├── cairo-lang-compiler v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   │   │   ├── cairo-lang-lowering v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   │   │   ├── cairo-lang-plugins v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   │   │   ├── cairo-lang-sierra-generator v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   │   │   └── cairo-lang-starknet v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   │   ├── cairo-lang-sierra-generator v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   │   └── cairo-lang-starknet v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   ├── cairo-lang-lowering v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   ├── cairo-lang-plugins v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   ├── cairo-lang-semantic v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   ├── cairo-lang-sierra-generator v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   │   └── cairo-lang-starknet v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
│   └── cairo-lang-parser v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66)
│       ├── cairo-lang-compiler v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66)
│       │   └── cairo-lang-starknet v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66)
│       │       └── pathfinder v0.6.3 (/home/mirko/projects/starknet/pathfinder/crates/pathfinder)
│       ├── cairo-lang-defs v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66)
│       │   ├── cairo-lang-compiler v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       │   ├── cairo-lang-lowering v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66)
│       │   │   ├── cairo-lang-compiler v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       │   │   ├── cairo-lang-sierra-generator v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66)
│       │   │   │   ├── cairo-lang-compiler v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       │   │   │   └── cairo-lang-starknet v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       │   │   └── cairo-lang-starknet v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       │   ├── cairo-lang-plugins v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66)
│       │   │   ├── cairo-lang-compiler v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       │   │   ├── cairo-lang-sierra-generator v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       │   │   └── cairo-lang-starknet v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       │   ├── cairo-lang-semantic v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66)
│       │   │   ├── cairo-lang-compiler v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       │   │   ├── cairo-lang-lowering v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       │   │   ├── cairo-lang-plugins v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       │   │   ├── cairo-lang-sierra-generator v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       │   │   └── cairo-lang-starknet v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       │   ├── cairo-lang-sierra-generator v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       │   └── cairo-lang-starknet v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       ├── cairo-lang-lowering v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       ├── cairo-lang-plugins v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       ├── cairo-lang-semantic v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       ├── cairo-lang-sierra-generator v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
│       └── cairo-lang-starknet v2.0.0-rc6 (https://github.com/starkware-libs/cairo?tag=v2.0.0-rc6#54bd0e66) (*)
└── env_logger v0.9.3
    ├── cairo-lang-utils v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
    │   ├── cairo-lang-casm v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
    │   │   ├── cairo-lang-sierra-to-casm v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
    │   │   │   └── cairo-lang-starknet v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   └── cairo-lang-starknet v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   ├── cairo-lang-compiler v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   ├── cairo-lang-defs v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   ├── cairo-lang-diagnostics v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
    │   │   ├── cairo-lang-compiler v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-defs v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-lowering v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-parser v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-plugins v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-semantic v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-sierra-generator v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   └── cairo-lang-starknet v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   ├── cairo-lang-eq-solver v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
    │   │   ├── cairo-lang-sierra-ap-change v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
    │   │   │   ├── cairo-lang-sierra-to-casm v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   │   └── cairo-lang-starknet v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   └── cairo-lang-sierra-gas v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
    │   │       ├── cairo-lang-sierra-to-casm v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │       └── cairo-lang-starknet v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   ├── cairo-lang-filesystem v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
    │   │   ├── cairo-lang-compiler v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-defs v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-diagnostics v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-lowering v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-parser v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-plugins v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-project v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
    │   │   │   └── cairo-lang-compiler v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-semantic v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-sierra-generator v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-starknet v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   └── cairo-lang-syntax v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
    │   │       ├── cairo-lang-compiler v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │       ├── cairo-lang-defs v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │       ├── cairo-lang-lowering v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │       ├── cairo-lang-parser v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │       ├── cairo-lang-plugins v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │       ├── cairo-lang-semantic v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │       ├── cairo-lang-sierra-generator v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │       └── cairo-lang-starknet v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   ├── cairo-lang-lowering v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   ├── cairo-lang-parser v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   ├── cairo-lang-plugins v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   ├── cairo-lang-semantic v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   ├── cairo-lang-sierra v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
    │   │   ├── cairo-lang-compiler v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-sierra-ap-change v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-sierra-gas v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-sierra-generator v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   ├── cairo-lang-sierra-to-casm v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   │   └── cairo-lang-starknet v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   ├── cairo-lang-sierra-ap-change v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   ├── cairo-lang-sierra-gas v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   ├── cairo-lang-sierra-generator v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   ├── cairo-lang-sierra-to-casm v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   ├── cairo-lang-starknet v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   ├── cairo-lang-syntax v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    │   └── cairo-lang-syntax-codegen v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a)
    │       └── cairo-lang-parser v1.0.0-alpha.6 (https://github.com/starkware-libs/cairo?tag=v1.0.0-alpha.6#439da05a) (*)
    └── cairo-lang-utils v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
        ├── cairo-lang-casm v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
        │   ├── cairo-lang-sierra-to-casm v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
        │   │   └── cairo-lang-starknet v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   └── cairo-lang-starknet v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        ├── cairo-lang-compiler v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        ├── cairo-lang-defs v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        ├── cairo-lang-diagnostics v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
        │   ├── cairo-lang-compiler v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-defs v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-lowering v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-parser v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-plugins v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-semantic v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-sierra-generator v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   └── cairo-lang-starknet v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        ├── cairo-lang-eq-solver v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
        │   ├── cairo-lang-sierra-ap-change v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
        │   │   ├── cairo-lang-sierra-to-casm v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   │   └── cairo-lang-starknet v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   └── cairo-lang-sierra-gas v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
        │       ├── cairo-lang-sierra-to-casm v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │       └── cairo-lang-starknet v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        ├── cairo-lang-filesystem v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
        │   ├── cairo-lang-compiler v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-defs v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-diagnostics v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-lowering v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-parser v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-plugins v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-project v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
        │   │   └── cairo-lang-compiler v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-semantic v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-sierra-generator v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-starknet v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   └── cairo-lang-syntax v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
        │       ├── cairo-lang-compiler v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │       ├── cairo-lang-defs v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │       ├── cairo-lang-lowering v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │       ├── cairo-lang-parser v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │       ├── cairo-lang-plugins v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │       ├── cairo-lang-semantic v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │       ├── cairo-lang-sierra-generator v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │       └── cairo-lang-starknet v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        ├── cairo-lang-lowering v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        ├── cairo-lang-parser v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        ├── cairo-lang-plugins v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        ├── cairo-lang-semantic v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        ├── cairo-lang-sierra v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
        │   ├── cairo-lang-compiler v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-sierra-ap-change v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-sierra-gas v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-sierra-generator v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   ├── cairo-lang-sierra-to-casm v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        │   └── cairo-lang-starknet v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        ├── cairo-lang-sierra-ap-change v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        ├── cairo-lang-sierra-gas v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        ├── cairo-lang-sierra-generator v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        ├── cairo-lang-sierra-to-casm v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        ├── cairo-lang-starknet v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        ├── cairo-lang-syntax v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)
        └── cairo-lang-syntax-codegen v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82)
            └── cairo-lang-parser v1.0.0-rc0 (https://github.com/starkware-libs/cairo?tag=v1.0.0-rc0#05867c82) (*)

Hmm, I wonder if it's not a high team to upgrade all dependencies in this repository. Or perhaps, to set up Dependabot (let's say monthly)?

colored got updated 2 weeks ago - we update afterward - no longer getting the error.

This doesn't really help us because we rely on multiple versions of the compiler in order to compile all sierra classes.. For us it would require point releases for all the compiler versions we are using to properly fix this.

For compilation of all sierra classes you only need the latest for each major version (where currently only 1 such exists) - so that should be fine.

That is not true :) Only true for mainnet. However we need to support integration, testnet etc.
We currently bundle:
casm-compiler-v1_0_0-alpha6 = { package = "cairo-lang-starknet", git = "https://github.com/starkware-libs/cairo", tag = "v1.0.0-alpha.6" }
casm-compiler-v1_0_0-rc0    = { package = "cairo-lang-starknet", git = "https://github.com/starkware-libs/cairo", tag = "v1.0.0-rc0" }
casm-compiler-v1_1_1        = { package = "cairo-lang-starknet", version = "=1.1.1" }
casm-compiler-v2            = { package = "cairo-lang-starknet", version = "=2.1.0-rc1" }

all of which are required afaik.

Got it.
Do note that the sierra-to-casm compiler does not use the color lib, so I don't really see how you actually are dependent on the 'atty' lib.
Oh, it is probably just the envlogger.

authors: Mirko-von-Leipzig mkaput orizi

repo: starkware-libs/cairo


text:
Improve transmission performance

PR #546 appears to slow down the sim by nearly 30% -- the benchmark takes 1.3 s to run instead of 1.0 s. Need to fix. Tried njit on ss.combine_rands(), doesn't help.
Compare SHA 4689698 (combine-rands, slow) with 43249e3 (main, fast).

Script:
import sciris as sc
import starsim as ss

kw = dict(n_agents=10e3, start=2000, end=2100, diseases='sis', plot=False)

prof = 1

if prof:
    context = sc.cprofile(sort='selfpct', mintime=1e-1)
else:
    context = sc.timer()

with context:
    sim = ss.demo(**kw)

Slow:
                          func    cumpct  selfpct  cumtime    selftime  calls                                        path
0                     add_edge   14.6439  14.3256   0.1165  1.1399e-01  51710                         multidigraph.py:416
1                set_prognoses   20.3468   3.1097   0.1619  2.4744e-02    102                               disease.py:94
2               make_new_cases   49.8485   2.4438   0.3967  1.9446e-02    101                              disease.py:247
3                       append   16.5239   1.8800   0.1315  1.4959e-02  51710                              disease.py:377
4                          rvs   17.2986   1.8735   0.1376  1.4908e-02    611                        distributions.py:520
5             _handle_fromlist   13.5303   0.3817   0.1077  3.0370e-03   4897          <frozen importlib._bootstrap>:1207
6   load_additional_registries   15.4045   0.2278   0.1226  1.8130e-03    248                                   cpu.py:60
7                         step   73.3433   0.1977   0.5836  1.5733e-03    101                                  sim.py:167
8                set_prognoses   23.9644   0.1740   0.1907  1.3842e-03    102                                  sir.py:128
9                   _set_cases   24.0492   0.1045   0.1914  8.3182e-04    101                              disease.py:305
10                         run  100.5591   0.0824   0.8002  6.5575e-04      1                                  sim.py:234
11              _find_and_load   13.0682   0.0316   0.1040  2.5143e-04     88          <frozen importlib._bootstrap>:1165
12                      update   13.2567   0.0308   0.1055  2.4541e-04    101                              network.py:499
13     _find_and_load_unlocked   13.0037   0.0307   0.1035  2.4405e-04     76          <frozen importlib._bootstrap>:1120
14                     refresh   19.5396   0.0271   0.1555  2.1549e-04    248                                 base.py:261
15              _load_unlocked   12.7827   0.0221   0.1017  1.7560e-04     75           <frozen importlib._bootstrap>:666
16                 exec_module   12.6857   0.0142   0.1009  1.1322e-04     74  <frozen importlib._bootstrap_external>:934
17   _call_with_frames_removed   12.9244   0.0092   0.1028  7.2965e-05    202           <frozen importlib._bootstrap>:233
18                  initialize   25.3744   0.0060   0.2019  4.7907e-05      1                                   sim.py:47
19                     compile   20.2575   0.0057   0.1612  4.5254e-05      2                           dispatcher.py:907
20                        demo  100.7041   0.0036   0.8013  2.8979e-05      1                                  sim.py:706
21                    set_seed   22.5082   0.0027   0.1791  2.1499e-05      1                                utils.py:196
22           _compile_for_args   22.8517   0.0022   0.1818  1.7664e-05      2                           dispatcher.py:388
23               load_overload   20.2238   0.0012   0.1609  9.2750e-06      2                              caching.py:627

Fast:
                          func    cumpct  selfpct  cumtime    selftime  calls                                path
0                     add_edge   16.1580  15.8075   0.1182  1.1560e-01  52196                 multidigraph.py:416
1               make_new_cases   45.8463   5.1804   0.3353  3.7882e-02    101                      disease.py:247
2                set_prognoses   22.4226   3.4457   0.1640  2.5197e-02    102                       disease.py:94
3                       append   18.1924   2.0344   0.1330  1.4877e-02  52196                      disease.py:379
4                          rvs   15.1250   2.0188   0.1106  1.4763e-02    611                distributions.py:520
5             _handle_fromlist   14.3934   0.4099   0.1053  2.9977e-03   4897  <frozen importlib._bootstrap>:1207
6   load_additional_registries   16.4687   0.2482   0.1204  1.8148e-03    248                           cpu.py:60
7                         step   71.3403   0.2157   0.5217  1.5773e-03    101                          sim.py:167
8                set_prognoses   26.4412   0.1851   0.1934  1.3538e-03    102                          sir.py:128
9                   _set_cases   26.5112   0.1045   0.1939  7.6395e-04    101                      disease.py:307
10                         run  100.5779   0.0867   0.7355  6.3400e-04      1                          sim.py:234
11              _find_and_load   13.8990   0.0332   0.1016  2.4308e-04     88  <frozen importlib._bootstrap>:1165
12                      update   14.4932   0.0330   0.1060  2.4125e-04    101                      network.py:499
13     _find_and_load_unlocked   13.8288   0.0319   0.1011  2.3337e-04     76  <frozen importlib._bootstrap>:1120
14                     refresh   20.9855   0.0296   0.1535  2.1681e-04    248                         base.py:261
15                  initialize   27.1852   0.0181   0.1988  1.3251e-04      1                           sim.py:47
16   _call_with_frames_removed   13.7409   0.0092   0.1005  6.7158e-05    202   <frozen importlib._bootstrap>:233
17                     compile   21.7269   0.0064   0.1589  4.7079e-05      2                   dispatcher.py:907
18                        demo  100.7380   0.0038   0.7367  2.7974e-05      1                          sim.py:706
19                    set_seed   24.2063   0.0028   0.1770  2.0501e-05      1                        utils.py:198
20           _compile_for_args   24.6252   0.0025   0.1801  1.8288e-05      2                   dispatcher.py:388
21               load_overload   21.6890   0.0013   0.1586  9.4950e-06      2                      caching.py:627

Strange - as an aside, I think it would be good if we had a couple of different sims in the benchmark so that we can get a wider cross section of different use cases. That's particularly important because bottlenecks could arise in different places depending on things like the number of agents. In some cases it might also help to identify where slow-downs are coming from, if some benchmarks are affected more than others

Closing for now, performance seems ok.

authors: RomeshA cliffckerr

repo: starsimhub/starsim


text:
release: 2.1.2

:robot: I have created a release beep boop
2.1.2 (2022-10-09)
Performance Improvements

perfect use go 1.19 (87090e0)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/starudream/clash-speedtest/releases/tag/v2.1.2 :sunflower:

repo: starudream/clash-speedtest


text:
求解使用方案

这个该怎么用呢？是不是放服务器上运行那种？能不能搞个pc端的自动化？米游社的奖励签到急需大佬支持！

README.md

authors: geniusNFIL starudream

repo: starudream/miyoushe-task


text:
Add server-wallet package

This PR is porting over work done externally. Most of the work was thought out, roughly up to https://github.com/statechannels/monorepo/commit/7ad029135a52debd77e4571123c652a8c1d807b3)
Some of it -- the "protocolEngine" -- was merely sketched out to see how it worked.
Due to the nature of getting the code building, and the tests running, within this monorepo, it is awkward to split up this PR into two.

@snario I created issues for non-trivial suggestions, to not increase the scope of this PR.

repo: statechannels/monorepo


text:
chore: remove reference to wallet-core signState

And all signing is now sync (not async)
SigningWallet.signState can take a State or StateWithHash, adds the hash if necessary

I'm not sure what caused the test failure on the first commit. I'm sure adding a test didn't fix it 😕

repo: statechannels/statechannels


text:
Bug: error TS2344: Type 'NonNullable<TStateValue[K]>' does not satisfy the constraint 'StateValue'

XState version
XState version 5
Description
When I transpile my project, I get an error regarding the xstate types:
`
node_modules/xstate/dist/declarations/src/State.d.ts:5:49 - error TS2344: Type 'NonNullable<TStateValue[K]>' does not satisfy the constraint 'StateValue'.
Type 'NonNullable<TStateValue[K]>' is not assignable to type 'StateValueMap'.
Index signature for type 'string' is missing in type '{}'.
  [K in keyof TStateValue]?: ToTestStateValue<NonNullable<TStateValue[K]>>;

`
Expected result
no type errors in transpilation
Actual result
type errors in transpilation
Reproduction
https://stackblitz.com/edit/github-9ms4pa?file=tsconfig.json
Additional context
No response

TypeScript's strict mode is required for XState v5 to typecheck correctly.

See here for all the TypeScript requirements: https://stately.ai/docs/typescript

I still get following messages when I import
"node_modules/xstate/dist/declarations/src/State.d.ts:5:49 - error TS2344: Type 'NonNullable<TStateValue[K]>' does not satisfy the constraint 'StateValue'.
Type 'NonNullable<TStateValue[K]>' is not assignable to type 'StateValueMap'.
Index signature for type 'string' is missing in type '{}'.
5     [K in keyof TStateValue]?: ToTestStateValue<NonNullable<TStateValue[K]>>;
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Found 1 error in node_modules/xstate/dist/declarations/src/State.d.ts:5
Can I run it as node app as backend console

authors: Andarist asheeshmathur autoscatto davidkpiano

repo: statelyai/xstate


text:
The 1 bug

Describe the bug
"1" is printed to stdout when it shouldn't be.
To Reproduce
make a call to staxapp.auth.ApiTokenAuth.requests_auth()
Expected behavior
No 1 home
Screenshots
I only have 1 screenshot available

Additional context
This line of code is the bug: https://github.com/stax-labs/lib-stax-python-sdk/blob/master/staxapp/auth.py#L155

💚

Thank you for raising this with us @jamesinc , this offending line has been removed as per https://github.com/stax-labs/lib-stax-python-sdk/pull/91

authors: boltdynamics jamesinc richardkeit

repo: stax-labs/lib-stax-python-sdk


text:
How to set cache storage location

Hi Guys, first up thanks for the images :)
I've just setup the images for steamcache and steamcache-DNS and they appear to be working.  However I want to change where the steamcache is putting it's cache.  The machine I'm using has an SSD for the OS (Ubuntu) and a 12TB raid 0 drive for the cache.
What is the best way to move the cache storage?  Is it easy to change the config within the docker image?
Regards
KF
LlamaLAN

Hi @kanonfodda
I'm not sure how you started your container, However, the best way to set the storage location is when you run the container, for instance running the following:
docker run -d --name steamcache -p 192.168.0.5:80:80 -v /bigdata/cache:/data/cache -v /bigdata/logs:/data/logs steamcache/steamcache:latest
Will result in the in the cache ending up in /bigdata/cache and the logs will be written to /bigdata/logs on the host system.
I will update the readme to make this a little more clear when initially starting the container.
That said; it's possibly better to look at the generic container which does more than only steam (it does also do steam), and also for LlamaLAN it might be worth looking at the steamcache-site-licence which @mintopia has written. This allows Steam to use P2P when installing a game  in which it will use any other steam client on the network (as I understand it) which can also lower load on a central cache and it's also officially supported by Valve.
Jason

Many thanks, figured it would be easy 😊 Ill take a look at the other containers too.
cheers for the quick response

authors: JasonRivers kanonfodda

repo: steamcache/steamcache


text:
Tornado base speed is incorrect

Symptoms:

Periodic jumps when flying a tornado on the test server

Expected Behaviour:

No jumps, server and client should be in sync

Fixed

repo: steamroller-airmash/airmash-server


text:
Pest + Dusk + Sail

I am trying to get this setup with a new Laravel App.
I am using Laravel sail to develop in docker and I have Pest and Laravel Dusk setup and working. (php artisan dusk --pest --without-percy works perfectly)
Now I wanted to add this but when I run php artisan dusk --pest I receive this error message:
[percy] Config file not found
[percy] created build #3: https://percy.io/1e6dcf4c/esg-radar/builds/12960345
    Error: Failed to launch the browser process!
    /var/www/html/node_modules/puppeteer/.local-chromium/linux-818858/chrome-linux/chrome: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

    TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

It seems that percy does not know anything about the remote selenium instance nor how to use it.
Do you see a way we could get this working? Or is this a lost cause?

I don't know offhand. I don't use sail personally (still happy with valet) and I haven't used Pest much either. I'd happily take a PR if someone is able to troubleshoot this and provide a solution, but it's not something I'm likely to get to anytime soon.

I think we can close this, unless anyone else wants this to stay open.
I realized that there is not really the need to execute percy locally as this makes more sense on a ci.
And with github actions, after some trial and error it works perfectly now.

That's great to hear. 👍

authors: TheFehr jszobody

repo: stechstudio/laravel-visual-testing


text:
HF20: Add missing methods

Determine what functionality may still be missing for HF20 support and add it.
Possibles:

witness_set_properties

Moved out of in-progress due to bandwidth constraints.

How about functionality to update the user json_metadata?

repo: steemit/steem-js


text:
Pulsar daemon crashed

When I finish to view or cancel a film, always need to restart Kodi because the daemon is crashed.
I've a powerfull PC (great processor and 4GB of memory).
What reasons could be cause the daemon crashed?
Thanks.

Upload your complete xbmc log file to pastebin.

authors: NoGood ysilvela


text:
How to monitor Windows workers

Not an issue but more of a question.....How do we monitor Windows workers in a hybrid swarm cluster?  Node-exporter, Cadvisor, and Dockerd-exporter will not run on my Windows worker nodes.  Has anyone come up with a solution to handle a hybrid environment?  Thank you!

There is WMI_Exporter and Telegraf can also be used. Not sure if they work well when ran as containers though...

repo: stefanprodan/swarmprom


text:
Node exporter not starting through docker service create

It's probably more of a question than a problem, but i don't understand why it happens. When i run the node-exporter through docker stack deploy everything works fine, but when i'm trying to use it through docker service create it does not work and spills out the following error:
time="2020-07-04T03:07:13Z" level=info msg="Starting node_exporter (version=0.16.0, branch=HEAD, revision=d42bd70f4363dced6b77d8fc311ea57b63387e4f)" source="node_exporter.go:82" time="2020-07-04T03:07:13Z" level=info msg="Build context (go=go1.9.6, user=root@a67a9bc13a69, date=20180515-15:52:42)" source="node_exporter.go:83" time="2020-07-04T03:07:13Z" level=fatal msg="Couldn't create collector: failed to open sysfs: could not read /host/sys: stat /host/sys: no such file or directory" source="node_exporter.go:88"
docker-compose.yml (works):
version: "3.3"

networks:
  net:
    driver: overlay

services:
  node-exporter:
    image: stefanprodan/swarmprom-node-exporter:v0.16.0
    networks:
      - net
    environment:
      - NODE_ID={{.Node.ID}}
    volumes:
      - /proc:/host/proc:ro
      - /sys:/host/sys:ro
      - /:/rootfs:ro
      - /etc/hostname:/etc/nodename
    command:
      - '--path.sysfs=/host/sys'
      - '--path.procfs=/host/proc'
      - '--collector.textfile.directory=/etc/node-exporter/'
      - '--collector.filesystem.ignored-mount-points="^/(sys|proc|dev|host|etc)($$|/)"'
      - '--no-collector.ipvs'
    deploy:
      mode: global
      resources:
        limits:
          memory: 128M
        reservations:
          memory: 64M

docker service create (does not work, spilling out the mentioned error):
#!/bin/bash

docker network create --driver overlay master --subnet 172.30.0.0/16

docker service create \
    --name node-exporter \
    --network master \
    --env NODE_ID={{.Node.ID}} \
    --mount type=bind,source=/proc,destination=/host/proc:ro \
    --mount type=bind,source=/sys,destination=/host/sys:ro \
    --mount type=bind,source=/,destination=/rootfs:ro \
    --mount type=bind,source=/etc/hostname,destination=/etc/nodename \
    --mode global \
    --limit-memory=128MB \
    --reserve-memory=64MB \
    stefanprodan/swarmprom-node-exporter:v0.16.0 \
    --path.sysfs=/host/sys \
    --path.procfs=/host/proc \
    --collector.textfile.directory=/etc/node-exporter/ \
    --collector.filesystem.ignored-mount-points="^/(sys|proc|dev|host|etc)($$|/)" \
    --no-collector.ipvs

Docker version:
Docker version 19.03.8, build afacb8b7f0
Thanks in advance.

Should run as su