Stuck on: the Lightning service needs to scan the Blockchain

Hi, first of all i would like to thank you for the well written document and effort you put in this project!
Since a week or two i'm trying to get this work on my pi. The biggest problem i had so far was downloading a copy of the bitcoin blockchain but eventually the torrent option got me a copy of the blockchain.
So i did move on but now i'm stuck at the phase where "the lightning service needs to scan the blockchain". It does say that it can take some time, but it's scanning for two days now and i keep getting this error:

*** Test if chainnetwork is ready ...
1543342443
result()
error(error: Could not connect to the server <IP_ADDRESS>:8332 Make sure the bitcoind server is running and that you are connecting to the correct RPC port.)

followed by 4 or 5 lines saying something like

2018-11-27T18:16:26Z UpdateTip: new best=0000000000000000001d1da5bf072a8d70e88c6ae72b10c7788c369dbe662fe0 height=550764 version=0x20000000 log2_work=90.03722 tx=358195175 date='2018-11-20T00:34:10Z' progress=0.995541 cache=51.4MiB(415215txo)
2018-11-27T18:16:26Z UpdateTip: new best=000000000000000000056190995d325d534ad4e4ff2e8e3ad81698d0c4b13a53 height=550765 version=0x20c00000 log2_work=90.037252 tx=358195176 date='2018-11-20T00:34:37Z' progress=0.995541 cache=51.4MiB(415216txo)
2018-11-27T18:16:44Z UpdateTip: new best=000000000000000000180f150713e04b91bff4fb14d9d308e7897dc7ab52b95b height=550766 version=0x20000000 log2_work=90.037284 tx=358197504 date='2018-11-20T00:38:34Z' progress=0.995542 cache=51.6MiB(416720txo)
2018-11-27T18:17:10Z UpdateTip: new best=00000000000000000014d747cf78bca4ab72b27bfaeab50328e1bb4798a18f4b height=550767 version=0x20800000 log2_work=90.037317 tx=358198611 date='2018-11-20T00:42:26Z' progress=0.995544 cache=51.5MiB(416270txo)
2018-11-27T18:17:39Z UpdateTip: new best=0000000000000000000a9cbc42c697f2e019bae3fd0e9866726e15be96387db9 height=550768 version=0x20000000 log2_work=90.037349 tx=358201516 date='2018-11-20T00:50:01Z' progress=0.995547 cache=52.1MiB(421452txo)
Waiting 1 minute and then trying again ...

So i have two questions:

does the "progress=0.995547" mean it's almost finished when reaching 1

can i ignore the testnet error (since i just want to go straight to live net)

yes - getting to 1 is the goal. You can see progress .. the blockchain is syncing from the downloaded state to the final actual state of the network
In the beginning - during setup/syncs - there can be times were the services need some time to get ready to be reachable and tresponding. We will see in the end if there is some more critical.

OK, thanks!
I'll just have to wait a little longer. That's no problem bitcoin won't leave either ;-)

I will close this issue fro now. Feel free to open up again or comment if you have further problems with this.

I'm still stuck:

*** Test if chainnetwork is ready ...
1543400259
result()
error(error: Could not connect to the server <IP_ADDRESS>:8332
Make sure the bitcoind server is running and that you are connecting to the correct RPC port.)
2018-11-28T09:51:12Z Syncing txindex with block chain from height 551729
2018-11-28T09:51:28Z txindex is enabled at height 551810
2018-11-28T09:51:28Z txindex thread exit
2018-11-28T09:56:23Z New outbound peer connected: version: 70015, blocks=551810, peer=65
2018-11-28T10:16:34Z UpdateTip: new best=0000000000000000000356f3ae64b14b601505199e1afd6921b750ce58dd8f61 height=551811 version=0x20000000 log2_work=90.070805 tx=360392682 date='2018-11-28T10:16:32Z' progress=1.000000 cache=107.8MiB(942756txo) warning='20 of last 100 blocks have unexpected version'
Waiting 1 minute and then trying again ...


Missing program_members package in release

Description
The moderngl.program_members package is not included in the distributions.

Optionally just use find_packages* to make it more future proof.

I reverted the find_packages just before making a release. :(

It's not supposed to be easy 😃


Fix keys for secretRef in CRD ClusterSecretStore

While testing I have found that the documentation was referencing to wrong key names:
provider.aws.auth.secretRef.accessKeyIDSecretRef
provider.aws.auth.secretRef.secretAccessKeySecretRef

/approve

/merge

Thank you @albertollamaso for your contribution! :dagger:


Fix route formatting in error message

This patch uses the route id in the error message rather than the route object ... (at [object Object])
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[x] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

Thanks! This certainly looks like an improvement. Though I'm a bit confused as to what the route ID in the error message is supposed to indicate. I first read it as saying that's where the setting needed to be set. I guess it's just saying which route was loaded, but I'm not sure why it's saying that instead of saying which URL was loaded (which we probably wouldn't need to do anyway as it should probably be done when the exception is caught). I'm just not really sure how the route is involved here.

Thanks!
@benmccann including the route ID just makes it slightly easier to find where the offending header is being read

ah crap, forgot a changeset


Azure Event Hubs Commitments for JS (July 2021-March 2022)

Azure Event Hubs is a highly scalable publish-subscribe service that can ingest millions of events per second and stream them to multiple consumers. This lets you process and analyze the massive amounts of data produced by your connected devices and applications.
The @azure/event-hubs package provides the SDK for JavaScript & TypeScript developers to write applications that use Azure Event Hubs. Version 5 of this package follows the latest guidelines for writing TypeScript SDKs for Azure services with the goal of being  a client library that is developer-friendly, idiomatic to the JavaScript ecosystem, and as consistent across different languages and platforms as possible.
This issue tracks the work we have planned for this package for the duration of July - December 2021
New features

[x] #17699
[ ] Add the idempotent producer feature as described in https://gist.github.com/jsquire/1cc4db6b3ca4ef13d26dc5315483555b to the new buffered producer
[ ] Release the package that has the checkpoint store that uses Azure Tables
[ ] If Service Bus plans on the backend redirect feature, design a common model if possible between that and the receiver redirect feature in Event Hubs

Testing improvements:

[ ] Update stress tests to use the new infrastructure where we now containerize the tests and have automation to run the tests on a scheduled basis
[ ] Update perf tests to use the perf test framework that will then allow them to be automated
[ ] Enable the min/max testing for Event Hubs blob checkpoint store
[ ] Use rhea to set up a mock server that can emulate Event Hubs in our tests

General improvements:

Fix incoming customer reported issues
Build Trouble Shooting Guides
Review and improve logging story
Review and improve tracing story

👋 I chatted with Alex and he mentioned it's safe to close these epics now.
But... there are a lot of open issues that are parented here. I am going to close this, but feel free to reopen if needed. Ideally we'd find a new home for them but that's up to the EH crew


Test settings

Codecov Report

Merging #9 (62fb6c0) into main (3f1bdad) will increase coverage by 63.63%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##            main       #9       +/-   ##
==========================================
+ Coverage   0.00%   63.63%   +63.63%
==========================================
  Files          3        3
  Lines         55       55
==========================================
+ Hits           0       35       +35
+ Misses        55       20       -35

Impacted Files
Coverage Δ

wagtailmakeup/management/commands/make_up.py
51.21% <100.00%> (+51.21%)
:arrow_up:

wagtailmakeup/api.py
100.00% <0.00%> (+100.00%)
:arrow_up:

wagtailmakeup/settings.py
100.00% <0.00%> (+100.00%)
:arrow_up:

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 3f1bdad...62fb6c0. Read the comment docs.


hi @iMountTai The two models can be different as long as the actor is same as the initial model (the one trained in SFT stage), and the critic is same as the reward model (the one trained in stage 2). They can use different tokenizers. We are preparing for revised version for stage 2&3 and keep being updated!

hi @iMountTai The two models can be different as long as the actor is same as the initial model (the one trained in SFT stage), and the critic is same as the reward model (the one trained in stage 2). They can use different tokenizers. We are preparing for revised version for stage 2&3 and keep being updated!

Which means, just change the tokenizer in lines 130 and 140 in train_prompts.py?
https://github.com/hpcaitech/ColossalAI/blob/d20dceb9a3d1bdcb2376201220f49fca7c7c1be9/applications/Chat/examples/train_prompts.py#L130
https://github.com/hpcaitech/ColossalAI/blob/d20dceb9a3d1bdcb2376201220f49fca7c7c1be9/applications/Chat/examples/train_prompts.py#L140C1-L140C1

Still unsolved?

I think so.


chore(package): rename script

:tada: This PR is included in version 1.6.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Use HeaderCollection to set installer caching

High-level description
Set the cache headers on Windows installers, so that they do not get cached in CloudFront.
This replaces the change made in https://github.com/dcos/dcos/pull/7051 which had no effect.
Corresponding DC/OS tickets (required)

D2IQ-65806 Windows Enterprise installer does not get updated after first commit

Related tickets (optional)

D2IQ-ID JIRA title / short description.

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot changelog-not-required release code

@mesosphere-mergebot label Ready For Review

@mesosphere-mergebot request-review @DominikDary

@mesosphere-mergebot request-review @orsenthil

@mesosphere-mergebot sync


in this project i have added animation on  heading water.

Closing because this doesn't seem to actually work, feel free to reopen.


Video/Audio storing option

Is there an option to record the Video/Audio while in the call?

@gunasekaran7 for audio take a look at sndfile module

audio: you can use the sndfile module to write WAV files:
http://www.creytiv.com/doxygen/baresip-dox/html/group__sndfile.html

video: you can implement a new vidfilt module that writes raw video
frames to a container, such as .y4m
https://wiki.multimedia.cx/index.php/YUV4MPEG2

Alfred

Thank you for the suggestion. Sounds like a good idea implementing through the

vidfilt


Reduce DI Allocations

Resolves #288

Hi @benaadams, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

Note: still need to implement unit test proposed by @rynowak, lost in outdated diff messages

See https://github.com/aspnet/HttpAbstractions/issues/402#issuecomment-140336990 for details on server run improvements (61.5k rps -> 1.49M rps)

:watch: - just waiting on a unit test for the scenario we discussed

Have the test, just trying to think of the right name XD

:+1:


1.0.0 release

Hi,
you have requested a release PR from me. Here it is!
This is the changelog I created:
Changes

Sending transactions, create exceptions.
create config file, create command for reading address balance
0.0.1 release
Update CHANGELOG.md
0.0.1 release
another config for first release
Config for first release

You can change it by editing CHANGELOG.md in the root of this repository and pushing to 1.0.0-release branch before merging this PR.
I didn't find any files where  __version__ is set.

I just released version 1.0.0 on Github


Merge David's work and architecture with the functional commands

@axlgithub Hi Alex! Do you have details where I can take a look? Or is it already in dev-branch?

@Bajger you can take a look at the merge-david-axel branch.

done in #11


Remove ERR_FAIL_COND that never happens in _draw_sky

In the conditional sky is always true.
resolve #65605

Thanks!


Add unhandled assemblyname characters

Fixes issue 4193, wherein it was discussed that the apostrophe, equals sign, and tilde are the last three visible en-us characters that are valid Windows file path characters but cause the assemblyname constructor to throw an error, thereby preventing scripts with class definitions from running when used in the script path. This effectively extends PR 4136 which did this for the comma.

@TimCurwick,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Before fixing the Issue I would prefer to open Issue-Question in CoreFX repo to find root codes and root rules - we should understand that we should fix. What if a char disallowed on first place but allowed on next places? Are there disallowed char combinations? Otherwise, we can fix this code indefinitely.

I agree that the permanent fix is in the .Net code. But in the mean time, I need my PowerShell 6.0 scripts to run on all of my Windows machines whether or not they have some future, fixed version of .Net installed. We probably can't find and workaround every problem character. We have to draw the line somewhere. I would be content if the consensus is for the line to be where it is at the moment, as it was the comma that we fixed a couple weeks ago that was personally impacting me. But a less arbitrary line would be to fix (or workaround) all affected characters in the base set of ASCII characters, which is what this PR does.

Before fixing the Issue I would prefer to open Issue-Question in CoreFX repo to find root cause

Totally agreed. @TimCurwick Can you please open an issue in dotnet/corefx repo?

We have to draw the line somewhere.

Yes, we should. Frankly speaking, it should be very rare to have chars like ,'=~ in a file path, but I agree that working around all affected chars in the base set of ASCII is a reasonable line. Even though adding '=~ would cover the base set of ASCII chars on Windows, it's not the case on Unix platforms. On Unix platforms, you can have any characters in a file path, and I guess at least " will cause the same problem.

Frankly speaking, it should be very rare to have chars like ,'=~ in a file path
I agree on '=~. The comma on the other hand (which we previously fixed and is not part of this PR), is becoming more common. As companies move to OneDrive for Business, they tend to embed their full legal company name in the path, often including commas.

On Unix platforms, you can have any characters in a file path, and I guess at least " will cause the same problem.
Can someone test this? I don't have simple access to such a test box. Copy, modify and run the pester test from this PR to test a double quote.

The comma, on the other hand, is becoming more common. As companies move to OneDrive for Business, they tend to embed their full legal company name in the path, often including commas.

Thanks for this info! I didn't know of this 👍

Can someone test this? I don't have simple access to such a test box. Copy, modify and run the pester test from this PR to test a double quote.

double quote raises the same exception:
PS:49> Get-Content './te"st.ps1'
class MyClass { static [string]$MyProperty = 'Some value' }
 [MyClass]::MyProperty
PS:50>
PS:50> . './te"st.ps1'
The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047)
At line:1 char:1
+ . './te"st.ps1'
+ ~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (:) [], FileLoadException
    + FullyQualifiedErrorId : System.IO.FileLoadException

But it works fine for these chars *?<>|.

From MSDN docs for AssemblyName Constructor (String):

The supplied assemblyName is parsed, and the appropriate fields of the new AssemblyName are initialized with values from the display name. This is the recommended way of parsing display names. Writing your own code to parse display names is not recommended.

BNF notation.
Sample: com.microsoft.crypto, Culture=en, PublicKeyToken=a5d015c7d5a0b012, Version=<IP_ADDRESS>
I guess the CoreFX parser is here:
https://github.com/dotnet/coreclr/blob/32f0f9721afb584b4a14d69135bea7ddc129f755/src/binder/assemblyname.cpp#L183
https://github.com/dotnet/coreclr/blob/32f0f9721afb584b4a14d69135bea7ddc129f755/src/binder/textualidentityparser.cpp#L236
I have no full understanding why it disallow some characters.
Another thoughts. Can we refactor the code:
string assemblyName = ClrFacade.FIRST_CHAR_PSASSEMBLY_MARK + (string.IsNullOrWhiteSpace(rootAst.Extent.File)
                                          ? "powershell"
                                          : rootAst.Extent.File

var assemblyObj = new AssemblyName(assemblyName);
assemblyObj.Name = assemblyName;

var assembly = AssemblyBuilder.DefineDynamicAssembly(assemblyObj,
                                                                   AssemblyBuilderAccess.RunAndCollect, GetAssemblyAttributeBuilders());
var module = assembly.DefineDynamicModule(assemblyName);

Another thoughts. Can we refactor the code

I was thinking the same thing and working on a build to test the idea. I'm not sure your code snippet will quite work as it would still send the unhandled characters to the AssemblyName constructor which is what throws the error. But this should work:
`string assemblyName = ClrFacade.FIRST_CHAR_PSASSEMBLY_MARK + (string.IsNullOrWhiteSpace(rootAst.Extent.File)
? "powershell"
: rootAst.Extent.File
var assemblyNameObj = new AssemblyName("dummy");
assemblyNameObj .Name = assemblyName;
var assembly = AssemblyBuilder.DefineDynamicAssembly(assemblyNameObj ,
AssemblyBuilderAccess.RunAndCollect, GetAssemblyAttributeBuilders()); `
At least, this would prevent the error when creating the AssemblyName. My question is whether creating the AssemblyName is the only place in the code that throws errors when the unhandled characters are used.

Sorry for my typo - we can remove "dummy":
var assemblyNameObj = new AssemblyName();

@TimCurwick Could you please continue?

@TimCurwick Please address two points:

Use var assemblyNameObj = new AssemblyName();
Use StringBuilder as Jason requested.

I have a completely different approach to addressing this problem and retaining the ability of mapping assembly to script - I'll be submitting a PR soon, so I'm closing this one.


data_flow_ops.FIFOQueue aborts with "Check failed: 1 == NumElements() (1 vs. 4)"

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
binary
TensorFlow version
tf-nightly  2.19.0-dev20241025
Custom code
Yes
OS platform and distribution
Linux Ubuntu 20.04.3 LTS
Mobile device
No response
Python version
3.10.14
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
I have confirmed that below code would crash on tf-nightly 2.19.0-dev20241025 (nightly-build)
Please find the gist to reproduce the issue.
Standalone code to reproduce the issue
from tensorflow.python.eager import context
from tensorflow.python.framework import dtypes as dtypes_lib
from tensorflow.python.ops import data_flow_ops
from tensorflow.python.eager import context
import tensorflow as tf
with context.graph_mode():
    q = data_flow_ops.FIFOQueue(10, dtypes_lib.float32, ())
    q.dequeue_many([1, 2, 3, 4])

Relevant log output
Check failed: 1 == NumElements() (1 vs. 4)Must have a one element tensor
Aborted (core dumped)

I was able to reproduce the issue on tensorflow 2.17, 2.18 and tf-nightly. Kindly find the gist of it here

The issue here is in the usage of FIFOQueue.dequeue_many(). The function expects a scalar or a scalar Tensor n corresponding to the number of elements to dequeue. Both dequeue_many() and dequeue_up_to() also expect all the queue elements to have a specific shape, which is set when the queue is initialized.
For example:
    >>> q = tf.queue.FIFOQueue(10, tf.int32, shapes=tf.TensorShape(2))
    >>> q.enqueue(tf.constant([1, 2], dtype=tf.int32, shape=(2)))
    >>> q.enqueue(tf.constant([3, 4], dtype=tf.int32, shape=(2)))
    >>> q.enqueue(tf.constant([5, 6], dtype=tf.int32, shape=(2)))
    >>> q.enqueue(tf.constant([7, 8], dtype=tf.int32, shape=(2)))
    >>> q.dequeue_many(3)
    <tf.Tensor: shape=(3, 2), dtype=int32, numpy=
    array([[1, 2],
       [3, 4],
       [5, 6]], dtype=int32)>

I can send out a PR to add this example, along with examples for the other functions of FIFOQueue, to the code.

The examples for FIFOQueue usage have been added to data_flow_ops.py through: https://github.com/tensorflow/tensorflow/commit/6337f9fb09a2b1b3da9a81d0aa7d65bea298d934. This should help clarify the usage of the FIFOQueue functions.

@Venkat6871 Can you please mark this as resolved?

Hi @cybersupersoap ,
Please take a look at the PR which was raised has been merged https://github.com/tensorflow/tensorflow/pull/83570. Also the examples were added for the FIFOQueue API.
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/ops/data_flow_ops.py#L504
Thank you!


Wrong output when using --force-sugar and output redirection together

Command used to run py.test
py.test --color=yes --force-sugar test_blah.py | tee output.txt
See also https://github.com/jenkinsci/ansicolor-plugin/issues/53

I believe this is the same problem people have been complaining with Docker.
PRs are welcome if someone finds a solution 🙂

Closing an old issue. Feel free to open a new issue if issue still persists.


SkyEye receives io.EOF error from real-time telemetry when using telemetry password

Fresh installation. All went well.
I am able to do radio checks and have received replies
One thing I am noting in the logs is an error about bullseye, is this safe to ignore?
Similarly reporting EOF of ACMI telemetry:
skyeye[46231]: 5:53PM INF log level set
skyeye[46231]: 5:53PM INF SkyEye GCI Bot version=v0.13.1
skyeye[46231]: 5:53PM INF setting up interrupt and TERM signal handler
skyeye[46231]: 5:53PM INF loading configuration
skyeye[46231]: 5:53PM INF setting GCI coalition coalition=blue
skyeye[46231]: 5:53PM INF GCI coalition set id=2
skyeye[46231]: 5:53PM INF loading whisper model path=models/ggml-medium.en-q8_0.bin
skyeye[46231]: whisper_init_from_file_with_params_no_state: loading model from 'models/ggml-medium.en-q8_0.bin'
skyeye[46231]: whisper_init_with_params_no_state: use gpu    = 1
skyeye[46231]: whisper_init_with_params_no_state: flash attn = 0
skyeye[46231]: whisper_init_with_params_no_state: gpu_device = 0
skyeye[46231]: whisper_init_with_params_no_state: dtw        = 0
skyeye[46231]: whisper_model_load: loading model
skyeye[46231]: whisper_model_load: n_vocab       = 51864
skyeye[46231]: whisper_model_load: n_audio_ctx   = 1500
skyeye[46231]: whisper_model_load: n_audio_state = 1024
skyeye[46231]: whisper_model_load: n_audio_head  = 16
skyeye[46231]: whisper_model_load: n_audio_layer = 24
skyeye[46231]: whisper_model_load: n_text_ctx    = 448
skyeye[46231]: whisper_model_load: n_text_state  = 1024
skyeye[46231]: whisper_model_load: n_text_head   = 16
skyeye[46231]: whisper_model_load: n_text_layer  = 24
skyeye[46231]: whisper_model_load: n_mels        = 80
skyeye[46231]: whisper_model_load: ftype         = 7
skyeye[46231]: whisper_model_load: qntvr         = 2
skyeye[46231]: whisper_model_load: type          = 4 (medium)
skyeye[46231]: whisper_model_load: adding 1607 extra tokens
skyeye[46231]: whisper_model_load: n_langs       = 99
skyeye[46231]: whisper_model_load:      CPU total size =   822.75 MB
skyeye[46231]: whisper_model_load: model size    =  822.75 MB
skyeye[46231]: whisper_init_state: kv self size  =  150.99 MB
skyeye[46231]: whisper_init_state: kv cross size =  150.99 MB
skyeye[46231]: whisper_init_state: kv pad  size  =    6.29 MB
skyeye[46231]: whisper_init_state: compute buffer (conv)   =   28.68 MB
skyeye[46231]: whisper_init_state: compute buffer (encode) =  594.22 MB
skyeye[46231]: whisper_init_state: compute buffer (cross)  =    7.85 MB
skyeye[46231]: whisper_init_state: compute buffer (decode) =  142.09 MB
skyeye[46231]: 5:53PM INF whisper model loaded languages=["en","zh","de","es","ru","ko","fr","ja","pt","tr","pl","ca","nl","ar","sv","it","id","hi","fi","vi","he","uk","el","ms","cs","ro","da","hu","ta","no","th","ur","hr","bg","lt","la","mi","ml","cy","sk","te","fa","lv","bn","sr","az","sl","kn","et","mk","br","eu","is","hy","ne","mn","bs","kk","sq","sw","gl","mr","pa","si","km","sn","yo","so","af","oc","ka","be","tg","sd","gu","am","yi","lo","uz","fo","ht","ps","tk","nn","mt","sa","lb","my","bo","tl","mg","as","tt","haw","ln","ha","ba","jw","su"] multilingual=false
skyeye[46231]: 5:53PM INF selected voice voice=voices.Voice
skyeye[46231]: 5:53PM INF selected callsign callsign="[Wizard]"
skyeye[46231]: 5:53PM INF parsed SRS frequency frequency=251000000.000000.3AM
skyeye[46231]: 5:53PM INF parsed SRS frequency frequency=133000000.000000.3AM
skyeye[46231]: 5:53PM INF parsed SRS frequency frequency=30000000.000000.3FM
skyeye[46231]: 5:53PM INF starting application
skyeye[46231]: 5:53PM INF constructing gRPC clients address=<IP_ADDRESS>:50051
skyeye[46231]: 5:53PM INF constructing chat listener
skyeye[46231]: 5:53PM INF constructing SRS client address=<IP_ADDRESS>:5002 clientName="GCI [Wizard] [BOT]" coalitionID=2 modulationID=0 timeout=10s
skyeye[46231]: 5:53PM INF connecting to SRS server TCP socket address=<IP_ADDRESS>:5002
skyeye[46231]: 5:53PM INF connecting to SRS server UDP socket address=<IP_ADDRESS>:5002
skyeye[46231]: 5:53PM INF constructing telemetry client address=<IP_ADDRESS>:42671
skyeye[46231]: 5:53PM INF constructing speech-to-text recognizer
skyeye[46231]: 5:53PM INF constructing text parser
skyeye[46231]: 5:53PM INF constructing radar scope
skyeye[46231]: 5:53PM INF constructing GCI controller
skyeye[46231]: 5:53PM INF constructing text composer
skyeye[46231]: 5:53PM INF constructing text-to-speech synthesizer
skyeye[46231]: 5:53PM INF constructing application
skyeye[46231]: 5:53PM INF starting subroutines
skyeye[46231]: 5:53PM INF starting speech recognition routine
skyeye[46231]: 5:53PM INF starting chat listener routines
skyeye[46231]: 5:53PM INF starting request parsing routine
skyeye[46231]: 5:53PM INF starting radar scope routine
skyeye[46231]: 5:53PM INF starting GCI controller routine
skyeye[46231]: 5:53PM INF starting response composer routine
skyeye[46231]: 5:53PM INF starting speech synthesis routine
skyeye[46231]: 5:53PM INF starting radio transmission routine
skyeye[46231]: 5:53PM INF starting exit timer routine duration=259200000
skyeye[46231]: 5:53PM INF streaming telemetry data to radar
skyeye[46231]: 5:53PM INF updating mission time and bullseye
skyeye[46231]: 5:53PM INF running telemetry client
skyeye[46231]: 5:53PM INF running SRS client
skyeye[46231]: 5:53PM INF SRS client starting
skyeye[46231]: 5:53PM INF syncing with SRS server
skyeye[46231]: 5:53PM INF running controller
skyeye[46231]: 5:53PM INF attaching callbacks
skyeye[46231]: 5:53PM INF composing brevity call params={"Frequencies":[251000000,133000000,30000000]} type=brevity.SunriseCall
skyeye[46231]: 5:53PM INF composed brevity call params={"Frequencies":[251000000,133000000,30000000]} speech="All players, GCI [WIZARD] sunrise on 2 5 1 point 0, 1 3 3 point 0 and 3 0 point 0" subtitle="All players: GCI [WIZARD] (bot) sunrise on 251.0, 133.0 and 30.0" type=brevity.SunriseCall
skyeye[46231]: 5:53PM INF synthesizing speech text="All players, GCI [WIZARD] sunrise on 2 5 1 point 0, 1 3 3 point 0 and 3 0 point 0"
skyeye[46231]: 5:53PM INF reconnecting to external AWACS mode
skyeye[46231]: 5:53PM INF starting pings interval=15s
skyeye[46231]: 5:53PM INF syncronizing clients count=2
skyeye[46231]: 5:53PM INF received host handshake highLevelProtocolVersion=0 hostname= lowLevelProtocolVersion=0
skyeye[46231]: 5:53PM INF sent client handshake hostname="[Wizard]"
skyeye[46231]: 5:53PM INF resetting ACMI client state
skyeye[46231]: 5:53PM INF sending mission start message
skyeye[46231]: 5:53PM INF clearing all trackfiles due to mission (re)start
skyeye[46231]: 5:53PM ERR error reading telemetry, retrying error="error reading updates: error reading ACMI stream: reached end of file: EOF"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM INF synthesized audio clockTime=2.853736059s
skyeye[46231]: 5:53PM INF transmitting audio traceID=b7Dx7k4MrW9Rw4qUEr3si3
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM INF received host handshake highLevelProtocolVersion=0 hostname= lowLevelProtocolVersion=0
skyeye[46231]: 5:53PM INF sent client handshake hostname="[Wizard]"
skyeye[46231]: 5:53PM INF resetting ACMI client state
skyeye[46231]: 5:53PM INF sending mission start message
skyeye[46231]: 5:53PM INF clearing all trackfiles due to mission (re)start
skyeye[46231]: 5:53PM ERR error reading telemetry, retrying error="error reading updates: error reading ACMI stream: reached end of file: EOF"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM INF received host handshake highLevelProtocolVersion=0 hostname= lowLevelProtocolVersion=0
skyeye[46231]: 5:53PM INF sent client handshake hostname="[Wizard]"
skyeye[46231]: 5:53PM INF resetting ACMI client state
skyeye[46231]: 5:53PM INF sending mission start message
skyeye[46231]: 5:53PM INF clearing all trackfiles due to mission (re)start
skyeye[46231]: 5:53PM ERR error reading telemetry, retrying error="error reading updates: error reading ACMI stream: reached end of file: EOF"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:53PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:54PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:54PM WRN error reading bullseye error="bullseye not found"
skyeye[46231]: 5:54PM WRN error reading bullseye error="bullseye not found"```

I can use Tacview to connect to the real-time telemetry and view what is happening realtime

Do you have a password enabled on your TacView exporter? (ChecktacviewRealTimeTelemetryPassword in Saved Games\<dcs server folder>\Config\options.lua)
If so, does the telemetry-password config option in SkyEye's config match that password?

Indeed I do have a password enabled for the remote telemetry. I have this configured properly.
For simplicity I removed the password from the tacview config and SkyEye's config and it started working correctly.
I've double checked, I use the same simple alphabetical lowercase password in tacview and Skyeye, it breaks again.

Hrmm, I tested on my machine with a simple alpha-lower password and had no issues 😕 not sure on this one.
Can you provide a password that has similar characteristics of the one you used? Does it have any characters other than ASCII letters or anything?

The password was:
zerosugar

I remove the password from both locations. It works.
I put the password back in both locations. It doesnt work.

You are also uncommenting the telemetry-password line in the config file, correct? It should be
telemetry-password: zerosugar

not
#telemetry-password: zerosugar

Yes... when I have it enabled I removed the comment. That was just a screenshot showing the password itself when I had the auth disabled.

I'm happy to run with no password for now... that port isnt exposed to the internet and only the network local to the DCS server can access it.
I've tested so many times with the password enabled and simply cant get it to work with a password configured.
Tacview v1.9.4
DCS OS: Windows Server 2022
SkyEye OS: Ubuntu 24.04.01 LTS

I reproduced the issue, and I think it may be a problem in TacView.
When I set the TacView password to empty string and start a DCS server, I see the telemetry port in the LISTENING state as expected:
> netstat -ano | findstr LISTENING | findstr 42674
  TCP    <IP_ADDRESS>:42674          <IP_ADDRESS>:0              LISTENING       12984
  TCP    [::]:42674             [::]:0                 LISTENING       12984
>

When I set the password to anything else I've tried, the telemetry port does not appear in the port list:
> netstat -ano | findstr 42674
>

I'll take this to the TacView Discord and see if they have any suggestions.

Actually, I think that's a separate issue from your issue because in your logs the initial connection succeeds but the client handshake fails... ☹

I looked at this for a few hours today, comparing SkyEye and the official client in Wireshark.

I did indeed have some bugs in handling password hashes
Regardless, there stills seems to be an issue. Weirdly, even if I copy the packets sent by the official client and modify my code to send the exact same packet, I still get an EOF from the server. So something really weird is happening here...

Poked around the client some more and I think I've found the problem!

I'll be building a new release with this fix for you to try out at some point this weekend.

@klinkeye can you give v0.14.0 a try?

@dharmab sure thing, I assume to upgrade its simply pulling latest archive and untar over the previous?


200, message='Invalid response status', url=URL('wss://sydney.bing.com/sydney/ChatHub')

How to solve the problem that just came up today?

It seems that New Bing has tightened its IP detection mechanism. We are currently using a random forward IP like this:
_FORWARDED_IP = f"1.0.0.{random.randint(0, 255)}"

However, it seems that this method is no longer working. Can you access New Bing in the browser with the same proxy IP that you use in the client? If not, please try a different proxy server that can bypass the New Bing restriction.

Commit 11c2c498f1fe8763b518fbc6ed38f6195811a799 fixed the issue. See README for new proxy setup with Cloudflare Workers.


Pandora mapping is slow

Placeholder as @Danderson123 keeps saying this and I don't want to lose it. Mapping reads from one sample to a
PRG (Ecoli + a few thousand AMR genes) taking 30 mins with 64 cores. I realise our performance stats in the pandora paper are
a) way out of date
b) end to end performance of doing pandora compare on 20 samples.
I don;t think mapping can ever be as fast as the subsequent steps @Danderson123 does with amira, so it's not realistic to expect that, but I do want to understand if this is true (and set my expectations on how fast mapping is), or something weird about Dan's setup.

Actually this might be a RAM/speed tradeoff - if we lazy load gene/PRGs into RAM only when we see them?

(Hope i'm not misrepresenting you @Danderson123 , I can delete this or update it)

This is correct, I will try to make plots of runtime vs number of reads after I have looked at the gene calling in more detail- without lazy loading the RAM usage was far higher than is reasonable for a laptop

I have to say @Danderson123 , first mapping to an AMR-only PRG and only keeping those reads, and then mapping just those to the big PRG, would probably make a significant difference


New problem found

This issue is pendant of resolution

[ ] Part 1
[ ] Part 2
[ ] Part 3

@hectorsector Sorry for mention you here, I just was practicing

[ ] FF


pageSplit:true leads to low quality

I used html2canvas to transfer html to img, and use jsPDF to import img to PDF
The problem is when img is too large the PDF need to be splited. so I use pagesplit:true here. But I found the output pdf is strenched and has a very low qulity. Someone konws how to fix this?
function getPDF2(){
var doc = new jsPDF();
initTemplate();
     var options = {
        pagesplit:false
     };

   var source=$("#tplW");
   source.addClass("cloned");
     doc.addHTML(source,options, function () {
           $("#wrap").empty();
           doc.save('Test.pdf');
         });
}

I also have this problem. When my html is small enough to fit one page it is much sharper than when it spans multiple pages.
The multiple page version streches each page vertically and also cuts the pages in the middle of images which is not useful in this case.

Hello @Coder2012 and @drizzt00s have either of you been able to identify a work around for this issue? We're experiencing this as well ( #707 )

Hi there,
There's now a html2pdf example which much better supports generating documents from HTML.
Get the latest master and try:
npm install
npm start

Then visit localhost:8000/examples/html2pdf/showcase.html
Hope this works well for you :)
Many thanks,
James

See https://github.com/MrRio/jsPDF/issues/944


Exception from analysis server (running from VSCode / Dart Code)

What I was doing
(please describe what you were doing when this exception occurred)
Versions

Flutter SDK 0.9.3-pre.14
Visual Studio Code 1.27.2
Dart Code 2.18.0

Analyzer Info
The analyzer was launched using the arguments:
/home/xxx/flutter/flutter/bin/cache/dart-sdk/bin/snapshots/analysis_server.dart.snapshot
--client-id=Dart-Code.dart-code
--client-version=2.18.0

Exception
Analysis failed: /home/xxx/flutter/flutter/packages/flutter/lib/src/widgets/dismissible.dart context: exception_20180921_093702_792
type 'ClassElementHandle' is not a subtype of type 'ClassElementImpl'
#0      InterfaceTypeImpl.lookUpInheritedMember.lookUpImpl (package:analyzer/src/dart/element/type.dart:1787:28)
#1      InterfaceTypeImpl.lookUpInheritedMember.lookUpImpl (package:analyzer/src/dart/element/type.dart:1816:24)
#2      InterfaceTypeImpl.lookUpInheritedMember.lookUpImpl (package:analyzer/src/dart/element/type.dart:1799:32)
#3      InterfaceTypeImpl.lookUpInheritedMember (package:analyzer/src/dart/element/type.dart:1828:24)
#4      ElementResolver.visitMethodInvocation (package:analyzer/src/generated/element_resolver.dart:599:40)
#5      MethodInvocationImpl.accept (package:analyzer/src/dart/ast/ast.dart:7807:49)
#6      ResolverVisitor.visitMethodInvocation (package:analyzer/src/generated/resolver.dart:5928:10)
#7      MethodInvocationImpl.accept (package:analyzer/src/dart/ast/ast.dart:7807:49)
#8      ExpressionStatementImpl.visitChildren (package:analyzer/src/dart/ast/ast.dart:4242:18)
#9      ResolverVisitor.visitNode (package:analyzer/src/generated/resolver.dart:5968:10)
#10     UnifyingAstVisitor.visitExpressionStatement (package:analyzer/dart/ast/visitor.dart:3052:59)
#11     ExpressionStatementImpl.accept (package:analyzer/src/dart/ast/ast.dart:4238:49)
#12     NodeListImpl.accept (package:analyzer/src/dart/ast/ast.dart:8304:20)
#13     BlockImpl.visitChildren (package:analyzer/src/dart/ast/ast.dart:1254:17)
#14     ResolverVisitor.visitNode (package:analyzer/src/generated/resolver.dart:5968:10)
#15     UnifyingAstVisitor.visitBlock (package:analyzer/dart/ast/visitor.dart:2966:31)
#16     ScopedVisitor.visitBlock (package:analyzer/src/generated/resolver.dart:6855:13)
#17     BlockImpl.accept (package:analyzer/src/dart/ast/ast.dart:1250:49)
#18     BlockFunctionBodyImpl.visitChildren (package:analyzer/src/dart/ast/ast.dart:1199:13)
#19     ResolverVisitor.visitNode (package:analyzer/src/generated/resolver.dart:5968:10)
#20     UnifyingAstVisitor.visitBlockFunctionBody (package:analyzer/dart/ast/visitor.dart:2969:55)
#21     ScopedVisitor.visitBlockFunctionBody (package:analyzer/src/generated/resolver.dart:6867:13)
#22     ResolverVisitor.visitBlockFunctionBody (package:analyzer/src/generated/resolver.dart:5214:13)
#23     BlockFunctionBodyImpl.accept (package:analyzer/src/dart/ast/ast.dart:1195:49)
#24     MethodDeclarationImpl.visitChildren (package:analyzer/src/dart/ast/ast.dart:7695:12)
#25     ResolverVisitor.visitNode (package:analyzer/src/generated/resolver.dart:5968:10)
#26     UnifyingAstVisitor.visitMethodDeclaration (package:analyzer/dart/ast/visitor.dart:3153:55)
#27     ScopedVisitor.visitMethodDeclarationInScope (package:analyzer/src/generated/resolver.dart:7333:11)
#28     ResolverVisitor.visitMethodDeclarationInScope (package:analyzer/src/generated/resolver.dart:5916:11)
#29     ScopedVisitor.visitMethodDeclaration (package:analyzer/src/generated/resolver.dart:7325:7)
#30     ResolverVisitor.visitMethodDeclaration (package:analyzer/src/generated/resolver.dart:5906:13)
#31     MethodDeclarationImpl.accept (package:analyzer/src/dart/ast/ast.dart:7686:49)
#32     NodeListImpl.accept (package:analyzer/src/dart/ast/ast.dart:8304:20)
#33     ScopedVisitor.visitClassMembersInScope (package:analyzer/src/generated/resolver.dart:6936:18)
#34     ScopedVisitor.visitClassDeclaration (package:analyzer/src/generated/resolver.dart:6913:11)
#35     ResolverVisitor.visitClassDeclaration (package:analyzer/src/generated/resolver.dart:5253:13)
#36     ClassDeclarationImpl.accept (package:analyzer/src/dart/ast/ast.dart:1765:49)
#37     ResolverVisitor.visitCompilationUnit (package:analyzer/src/generated/resolver.dart:5317:25)
#38     CompilationUnitImpl.accept (package:analyzer/src/dart/ast/ast.dart:2430:49)
#39     LibraryAnalyzer._resolveFile (package:analyzer/src/dart/analysis/library_analyzer.dart:592:10)
#40     LibraryAnalyzer._analyze.<anonymous closure> (package:analyzer/src/dart/analysis/library_analyzer.dart:102:9)
#41     __InternalLinkedHashMap&_HashVMBase&MapMixin&_LinkedHashMapMixin.forEach (dart:collection/runtime/libcompact_hash.dart:370:8)
#42     LibraryAnalyzer._analyze (package:analyzer/src/dart/analysis/library_analyzer.dart:101:13)
#43     LibraryAnalyzer.analyze.<anonymous closure> (package:analyzer/src/dart/analysis/library_analyzer.dart:78:14)
<asynchronous suspension>
#44     _PerformanceTagImpl.makeCurrentWhileAsync (package:analyzer/src/generated/utilities_general.dart:222:21)
<asynchronous suspension>
#45     LibraryAnalyzer.analyze (package:analyzer/src/dart/analysis/library_analyzer.dart:77:43)
<asynchronous suspension>
#46     AnalysisDriver._computeAnalysisResult.<anonymous closure> (package:analyzer/src/dart/analysis/driver.dart:1244:71)
<asynchronous suspension>
#47     PerformanceLog.runAsync (package:front_end/src/base/performance_logger.dart:52:21)
<asynchronous suspension>
#48     AnalysisDriver._computeAnalysisResult (package:analyzer/src/dart/analysis/driver.dart:1220:20)
<asynchronous suspension>
#49     AnalysisDriver.performWork (package:analyzer/src/dart/analysis/driver.dart:1046:39)
<asynchronous suspension>
#50     AnalysisDriverScheduler._run (package:analyzer/src/dart/analysis/driver.dart:1916:24)
<asynchronous suspension>
#51     AnalysisDriverScheduler.start (package:analyzer/src/dart/analysis/driver.dart:1857:5)
#52     new AnalysisServer (package:analysis_server/src/analysis_server.dart:389:29)
#53     SocketServer.createAnalysisServer (package:analysis_server/src/socket_server.dart:78:26)
#54     StdioAnalysisServer.serveStdio (package:analysis_server/src/server/stdio_server.dart:37:18)
#55     Driver.start.<anonymous closure> (package:analysis_server/src/server/driver.dart:487:21)
#56     _rootRun (dart:async/zone.dart:1124:13)
#57     _CustomZone.run (dart:async/zone.dart:1021:19)
#58     _runZoned (dart:async/zone.dart:1516:10)
#59     runZoned (dart:async/zone.dart:1463:12)
#60     Driver._captureExceptions (package:analysis_server/src/server/driver.dart:531:12)
#61     Driver.start (package:analysis_server/src/server/driver.dart:485:7)
#62     main (file:///b/build/slave/Linux_Engine/build/src/third_party/dart/pkg/analysis_server/bin/server.dart:12:11)
#63     _AsyncAwaitCompleter.start (dart:async/runtime/libasync_patch.dart:49:6)
#64     main (file:///b/build/slave/Linux_Engine/build/src/third_party/dart/pkg/analysis_server/bin/server.dart:10:10)
#65     _startIsolate.<anonymous closure> (dart:isolate/runtime/libisolate_patch.dart:287:32)
#66     _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:171:12)

Diagnostics requested after the error occurred are:
[
    {
        "name": "/home/xxx/flutter/flutter/dev/integration_tests/channels",
        "explicitFileCount": 6,
        "implicitFileCount": 970,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/examples/catalog",
        "explicitFileCount": 15,
        "implicitFileCount": 847,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/dev/integration_tests/ui",
        "explicitFileCount": 16,
        "implicitFileCount": 1247,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/dev/missing_dependency_tests",
        "explicitFileCount": 0,
        "implicitFileCount": 0,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/dev/integration_tests/external_ui",
        "explicitFileCount": 2,
        "implicitFileCount": 970,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/dev/integration_tests/android_semantics_testing",
        "explicitFileCount": 13,
        "implicitFileCount": 970,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/flutter_tools/test/data/dart_dependencies_test/good",
        "explicitFileCount": 0,
        "implicitFileCount": 0,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/flutter_tools/test/data/dart_dependencies_test/bad_package",
        "explicitFileCount": 0,
        "implicitFileCount": 0,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/dev/devicelab",
        "explicitFileCount": 97,
        "implicitFileCount": 801,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/flutter_driver",
        "explicitFileCount": 25,
        "implicitFileCount": -25,
        "workItemQueueLength": 25,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/dev/benchmarks/complex_layout",
        "explicitFileCount": 6,
        "implicitFileCount": 970,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/flutter_tools",
        "explicitFileCount": 221,
        "implicitFileCount": 129,
        "workItemQueueLength": 220,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/flutter_test",
        "explicitFileCount": 34,
        "implicitFileCount": -34,
        "workItemQueueLength": 34,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/dev/benchmarks/microbenchmarks",
        "explicitFileCount": 6,
        "implicitFileCount": 881,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/dev/docs/platform_integration",
        "explicitFileCount": 0,
        "implicitFileCount": 0,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/examples/hello_world",
        "explicitFileCount": 3,
        "implicitFileCount": 847,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/flutter_tools/test/data/dart_dependencies_test/changed_sdk_location",
        "explicitFileCount": 1,
        "implicitFileCount": -1,
        "workItemQueueLength": 1,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/flutter_tools/test/data/dart_dependencies_test/bad_path",
        "explicitFileCount": 0,
        "implicitFileCount": 0,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/examples/platform_channel",
        "explicitFileCount": 3,
        "implicitFileCount": 970,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/dev/integration_tests/android_views",
        "explicitFileCount": 3,
        "implicitFileCount": 980,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter",
        "explicitFileCount": 0,
        "implicitFileCount": 0,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/fuchsia_remote_debug_protocol",
        "explicitFileCount": 13,
        "implicitFileCount": -13,
        "workItemQueueLength": 13,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/flutter_tools/test/data/asset_test/main",
        "explicitFileCount": 0,
        "implicitFileCount": 0,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/flutter_tools/test/data/dart_dependencies_test/syntax_error",
        "explicitFileCount": 0,
        "implicitFileCount": 0,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/flutter_goldens",
        "explicitFileCount": 2,
        "implicitFileCount": -2,
        "workItemQueueLength": 2,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/examples/platform_view",
        "explicitFileCount": 1,
        "implicitFileCount": 585,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/examples/platform_channel_swift",
        "explicitFileCount": 3,
        "implicitFileCount": 970,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/dev/integration_tests/flavors",
        "explicitFileCount": 2,
        "implicitFileCount": 970,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/dev/tools",
        "explicitFileCount": 9,
        "implicitFileCount": 334,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/flutter",
        "explicitFileCount": 895,
        "implicitFileCount": 503,
        "workItemQueueLength": 92,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/flutter_goldens_client",
        "explicitFileCount": 1,
        "implicitFileCount": -1,
        "workItemQueueLength": 1,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/examples/flutter_gallery",
        "explicitFileCount": 105,
        "implicitFileCount": 998,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/dev/integration_tests/platform_interaction",
        "explicitFileCount": 4,
        "implicitFileCount": 970,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/dev/manual_tests",
        "explicitFileCount": 14,
        "implicitFileCount": 852,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/flutter_tools/test/data/asset_test/font",
        "explicitFileCount": 0,
        "implicitFileCount": 0,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/flutter_tools/test/data/dart_dependencies_test/bad_import",
        "explicitFileCount": 0,
        "implicitFileCount": 0,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/flutter_test/test/test_config/project_root",
        "explicitFileCount": 1,
        "implicitFileCount": -1,
        "workItemQueueLength": 1,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/dev/bots",
        "explicitFileCount": 11,
        "implicitFileCount": 444,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/examples/flutter_view",
        "explicitFileCount": 1,
        "implicitFileCount": 585,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/dev/tools/vitool",
        "explicitFileCount": 3,
        "implicitFileCount": 952,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/flutter_tools/test/data/dart_dependencies_test/asci_casing",
        "explicitFileCount": 0,
        "implicitFileCount": 0,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/packages/flutter_localizations",
        "explicitFileCount": 12,
        "implicitFileCount": -12,
        "workItemQueueLength": 12,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/examples/stocks",
        "explicitFileCount": 15,
        "implicitFileCount": 994,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/examples/layers",
        "explicitFileCount": 46,
        "implicitFileCount": 847,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    },
    {
        "name": "/home/xxx/flutter/flutter/dev/automated_tests",
        "explicitFileCount": 14,
        "implicitFileCount": 847,
        "workItemQueueLength": 0,
        "cacheEntryExceptions": []
    }
]

Fixed as https://github.com/dart-lang/sdk/issues/34546


Resurrect the "Interactive Resize Controls" experiment

@enidemi do you have the link to this one? Was it just one PR?

This was the original experiment: https://github.com/concrete-utopia/utopia/pull/530
This second version extends it to flex grow/shrink properties and also adds some other UI elements that as I remember were not useful https://github.com/concrete-utopia/utopia/pull/540 .
I think it's enough to use the first one.


how to pump streams into kvs?

hello,
playing with these boxes and they look appealing. i'm noticing that the current architecture is more for processing things on a frame by frame basis. i'm interested in pumping data into KVS, but KVS only accepts h264/encoded stream data. This is normally very easy when i have an RTSP url because I can use the KVS gstreamer sink to just pipe them together. However, since i don't have access to the underlying URL (i can get stream_url but no credentials), i have to work with single image frames.
the docs say:

AWS Panorama application results can be integrated with on-premises line of business applications for automation and can be routed to services such as Amazon Simple Storage Service (S3), Amazon Kinesis Video Streams, or Amazon CloudWatch for deriving actionable insights to drive process improvements.

is there a preferred approach to get data to pump into KVS?
thanks!

I definitely need this feature, there should way to encode video with overlayed info(rect, label and so on) to KVS by platform layer without performance issues.

@mattfeury, @jk1333,
Currently, Panorama doesn't have out of box integration with KVS, but customers can use the Kinesis Producer Library to do this.
Kinesis Producer Library expects the stream to be in MKV format so customers will have to create MKV data on the Panorama appliance device.

Closing this item.

Hello @mattfeury and @jk1333, I've just published my library and an article explaining it on how to stream the video output of your Panorama app to KVS or to a local RTSP server.

article: https://towardsdatascience.com/remote-view-your-computer-vision-models-running-on-aws-panorama-32922369ecf
library: https://github.com/Neosperience/backpack


handle gpkg GEOMETRY as unknown geometry

I would like geopakcage GEOMETRY type to not result in a startup error , but instead to be handled as an unknown type.
The layer type is used for rendering the capabilities json and styles. In the capabilities this layer will be set to unknown. A style will not be generated and a warning will be logged.

Pull Request Test Coverage Report for Build 03c8cb193-PR-845

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.007%) to 45.523%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

provider/gpkg/gpkg.go
0
2
0.0%

Totals

Change from base Build 7ac37b942:
-0.007%

Covered Lines:
5577

Relevant Lines:
12251

💛  - Coveralls

@roelarents I'm not coming up with a solution I'm happy with, so I want to outline my thinking, and see if we can work through things.
I don't like returning error values as a a geometry value (https://github.com/go-spatial/tegola/pull/845/files#diff-8fa7820d9f23e65780100996d1175d170ed1fa30b8930e52998f7aaf4dd84a0aR265) even if it's only limited to the gpkg provider.
I could see where someone would want to get the error if the mapping geo type is not supported.
I, almost, think it makes sense to add a switch here (https://github.com/go-spatial/tegola/blob/b1411adcb9e4e42b30657ebdc8bc92f5a40c51d5/provider/gpkg/gpkg_register.go#L194-L198) to check the error type returned and based on a flag set from the config ( https://github.com/go-spatial/tegola/blob/b1411adcb9e4e42b30657ebdc8bc92f5a40c51d5/provider/gpkg/gpkg_register.go#L222) and passed to the function (https://github.com/go-spatial/tegola/blob/b1411adcb9e4e42b30657ebdc8bc92f5a40c51d5/provider/gpkg/gpkg_register.go#L244) we could support both needs.
But I am unsure if this is the best way forward. I just know that to me passing an error value for a geometry smells.
thank you,
Gautam.

I understand your objections and I agree. Maybe a new type could be added to go-spatial/geom, called a "MultiGeometry" or "MixedGeometry" or "AnyGeometry" or something.  I also considered adding a type in the gpkg package and returning that.
For now, I've made a new try by just returning nil (without an error). Which still has the desired effect on capabilities json and styles.

@roelarents if you could please rebase this to master, I will get it merged in and ready for the next release.

@gdey done and thanks


Segmentation fault on render

Trying to open a specific scene, if I try to render ( window interactive preview or final render ) I get segmentation fault.
It is crashing both using Gpu or Cpu.
I'm on Debian Linux, Blender 2.90.1, LuxCore 2.3.
Attached the console and the crash file.
Thank you,
Riccardo
user@Bisonx:~/Progs/blender-2.90.1-linux64$ ./blender
Read prefs: /home/user/.config/blender/2.90/config/userpref.blend
found bundled python: /home/user/Progs/blender-2.90.1-linux64/2.90/python
Warning: class EXPORT_OT_svg contains a property which should be an annotation!
/home/user/Progs/blender-2.90.1-linux64/2.90/scripts/modules/bpy/utils/__init__.py:714
    assign as a type annotation: EXPORT_OT_svg.render_range
register_class(...):
Warning: 'PanelSVG' doesn't contain '_PT_' with prefix & suffix
BlendLuxCore 2.3 registered (with pyluxcore 2.3)
Read blend: /home/user/Blah/Lux/scena test_HD_LuxCore.blend
Updating OpenCL device list
Updating OpenCL device list
==================================================
[Engine/Viewport] New session
[Exporter] Creating session
[SDL][13.075] Camera type: perspective
[SDL][13.075] Camera position: Point[0, -2.39863, 0.680584]
[SDL][13.075] Camera target: Point[-7.5982e-11, -2.03779, 0.591554]
[SDL][13.075] Camera clipping plane disabled
Unpacking image "checker.png" to temp file "/tmp/tmpxp_fdpav.png"
Unpacking image "DirtWindowStains002_GLOSS_HIRES.jpg" to temp file "/tmp/tmpjoqqnpdu.jpg"
Unpacking image "RustMixedOnPaint012_NRM_6K.jpg" to temp file "/tmp/tmp5k6g694v.jpg"
Unpacking image "octabox.exr" to temp file "/tmp/tmpxh50bp4d.exr"
Unpacking image "sRGB_ColorChecker2005.exr" to temp file "/tmp/tmptlr6z3vm.exr"
Unpacking image "canada_montreal_nad_cafeteria_bright.exr" to temp file "/tmp/tmp2tq97tm1.exr"
[SDL][16.116] Texture definition:<PHONE_NUMBER>36040Color
[SDL][16.116] Reading texture map: /tmp/tmpxp_fdpav.png
[SDL][16.158] Texture definition:<PHONE_NUMBER>95784Color
[SDL][16.158] Reading texture map: /tmp/tmpjoqqnpdu.jpg
[SDL][17.765] Texture definition:<PHONE_NUMBER>93224Color
[SDL][17.765] Reading texture map: /tmp/tmp5k6g694v.jpg
[SDL][18.711] Texture definition:<PHONE_NUMBER>94760Bump
[SDL][18.711] Texture definition:<PHONE_NUMBER>91976Color
[SDL][18.711] Reading texture map: /tmp/tmpxh50bp4d.exr
Writing: /tmp/scena test_HD_LuxCore.crash.txt
Errore di segmentazione

scena test_HD_LuxCore.crash.txt

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Here is the scene:
https://we.tl/t-aUOEQz2xXG

I'm testing your scene with under development v2.5 and it is working fine here. Can you try with v2.5 (https://forums.luxcorerender.org/viewtopic.php?f=9&t=736) or at least v2.4 ?

Yes, with v2.4 it is working.
Thank you


"xcdevice" process never exits on macOS

Every time I launch my project directory with VS Code on macOS, a xcdevice process is started but it never exits when I'm done.
Over time, I have multiple processes running when I ps:

Is this something that need to be fixed?

Hi @zhouyifan0904
Can you please provide your flutter doctor -v? i can see that process but it's normal to see it running in the running for couple of hours, looks similar to android daemon process
Thank you

Hi @zhouyifan0904
Can you please provide your flutter doctor -v? i can see that process but it's normal to see it running in the running for couple of hours, looks similar to android daemon process
Thank you

Hi @zhouyifan0904
Looking. around, it doesn't look it's related to Flutter itself,  its part of Xcode , you can notice it without even using Flutter and xcdevice processes itself don't take much CPU and memory usage  when running in the background. If you uninstall Xcode and restart your Mac, it should go away
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Add Convenience node to emit preprocessor options

Hopefully this will address https://github.com/Fannovel16/comfyui_controlnet_aux/issues/289

One weird thing, at one point I had it properly suggesting the selector node when dragging from the input. Not sure what happened there.

I think I had the return type marked as "COMBO"

Yep, that does it. Breaks other things, but does it.


fix: disable source editor to avoid SWC bug

Due to https://github.com/swc-project/swc/issues/7640, the editor fails in production. The change here removes the plugin that causes the error.
There are two other alternatives:

disable the swc minification
upgrade to the latest Next.js version

Given the non-technical audience, I think that disabling the diff/source feature is the best option. Let me know if you think otherwise, though.

closing as it was fixed by updating next as per your recomendation in this PR: https://github.com/podkrepi-bg/frontend/pull/1576


Add "package schemas" to the repository

Now that we have clients and the ability to frame and send messages, it's time to start building out the "protocol messages" that together allow telemetry producers and consumers to coexist usefully.
It's useful to have "protocol messages" serialize into JSON to support a variety of implementations. This means two things:

An implementation is needed to convert serialized objects back into a matching object
We need to get organized about schemas for these messages and support easy schema documentation

For the first bullet, we can implement JSON loader classes for common things like type and channel registries (service as well?). For the second bullet, we need to both explicitly define and enforce that schema ahead of trying to load/parse it.
We have set precedent on this front already with datazen, we should carry that forward or otherwise leverage datazen's schema loading and enforcement machinery.

We should refactor the concept of "protocol framer" so that a function that frames a message can be written as top-level functions that take a message framer as an argument (and other necessary arguments).

We need to figure out how to build the interpreting/ingesting end of the message cache. Likely just a new object/entity that registers callbacks for given message types.

Refactor out "describe" and "describe_raw", make an abstract base class for anything that supports JSON serialization and ensure that base things like individual channels, user enum, registry etc implement it

We added a Serializable class, we need to add something so that "schemas" can be enforced on data provided in the constructor.
This can probably just be added to this base class.

Once we're satisfied with the above integration (i.e. some optional cerberus Validator probably), we need to port UserEnum to implement this class and also create a schema for it.

Now that we've added Validator support to Serializable and made some small refactors to use self.__class__ instead of Serializable itself in some cases, we need to move the needle forward on loading schemas from files (and then loading canned schemas from the package, maybe we can just use the class name as the file name?

We can now load schemas from files and directories (like datazen already does). We need to make a SchemaManager type of thing so that we can aggregate loaded schemas and then pair them to classes by name.

Now that we have a schema manager, we need to work on the implementation for converting UserEnum to be a Serializable and also figure out how to make a "factory" for classes / having the serializable class constructor take a schema manager as an argument

This is essentially complete, we can continue work on #25.


CMake create build option for using def file

I added a test to test_output.cpp to exercise the new feature allowing access to the binary output file prior to project close. The test builds and passes on 64 bit, but the build fails on 32 bit because it is unable to link with epanet2.dll that uses the def file.
I propose we create a build option for compiling with the def file.  Something like -DBUILD_USE_DEF=ON.  Rather than having the def file be the default for the MSVC 32 bit build. Thoughts?

@michaeltryby could you please post your test file. I'd like to see what the problem is before agreeing to add yet another build option.

@LRossman have a look at PR #416.

@LRossman As you can see on Appveyor the 32 bit build fails and the 64 bit build passes.

Appveyor indicates that test_output is calling functions with decorated names of the form _imp_EN_xxx whereas the toolkit's decorated function names are _EN_xxx. So where is the _imp coming from?
I also noticed that test_output is making calls to ENR_ init, ENR_open,  ENR_close. What are these ENR functions? Could they be the source of the problem?
Maybe it would be a better strategy (but less efficient) to add a EN_copyoutfile function to give client apps access to a copy of the output file (like was done for the report file) rather than the actual file being used by an open project.

@LRossman ENR is the prefix used for the output library.  That is the library under test in test_output.cpp. It ran fine before calls to epanet2.dll were added for the latest test. I don't know where the _imp is coming from.
I'm pretty sure this is a linking issue related to the def file, since it is running fine for 64 bit and the only difference between the two is the def file.
I should add that the output library is using cmake's generate_export_header command. So I guess def file dlls and a lib file dlls can't be linked in the same executable.

@michaeltryby from the link command it looks like the compiler is using the export library .lib file to link . The _imp is what it's looking for and it is complaining because it can't find it since the dll was compiled with the .def file.
How do you tell cmake to link using a .def file?

Here's a thought. Since you (@michaeltryby ) have already included all of the functions any app would need to access the output file in your output library, why don't we just incorporate those into the toolkit library and forget about manipulating the opening/closing of the output file. The functions I'm referring to are: EN_getenergyusage, EN_getnodeseries, EN_getlinkseries, EN_getnoderesults (your EN_getNodeAttribute), EN_getlinkresults, EN_getnoderesult, and EN_getlinkresult. I will volunteer to do so.
Regarding the cmake question, these lines are used to build the library using a .def file:
add_library(epanet2 SHARED ${EPANET_LIB_ALL} ${PROJECT_SOURCE_DIR}/include/epanet2.def)
set_source_files_properties(${PROJECT_SOURCE_DIR}/include/epanet2.def PROPERTIES_HEADER_FILE_ONLY TRUE)

@LRossman Yeah we have an output library for SWMM too. It's called by python for reg tests and being used in the new UIs.
Interesting thought. The only problem I see is that the toolkit API is already very large. It's not necessary to deliver all this functionality in one monolithic dll. Here is a thought that @samhatchett  proposed some time ago. Why don't we take the binary output file writing functions currently in the engine and move them out to the output library?
As far as cmake goes, that doesn't answer my question. We know how to build a dll using a .def file, the question is how to link against it using cmake?  Like why this test is failing right now.

@michaeltryby I sort of agree about the size of the toolkit API being too large (I believe I complained about that months ago, before we added even more functions to it). And I thought of another use case where the ablity to make a copy of the output file while keeping the project open is needed. That would be in a UI that wants to implement a scenario manager or simply be able to plot time series from two or more runs on the same graph. So I now think that an EN_copyoutfile is needed more than the output file access functions.
I can try taking one of the test files which I've linked successfully with the def file dll in the Visual Studio IDE and instead build it using cmake. Would that serve to answer your question?

@LRossman I have been trying to isolate this build problem so I can unambiguously attribute it to the .def file, but as of yet my attempts to do so have failed. My thinking now, is that it is an issue with Visual Studio 2017.

I can try taking one of the test files which I've linked successfully with the def file dll in the Visual Studio IDE and instead build it using cmake. Would that serve to answer your question?

Yes that would be helpful. But why don't you use test_output.cpp since that is the test we are having issues with.

@LRossman Figured it out. The DLLEXPORT definitions for epanet2.dll and epanet-output.dll were clobbering each other. Though, I'm not sure why this only affected the 32-bit build.

@michaeltryby I notice the DLLEXPORT definition for the toolkit includes __stdcall while the one for the output library doesn't. And #include "epanet2_2.h" comes after #include "epanet_output.h" in test_output.cpp, meaning DLLEXPORT is being defined without __stdcall. So I wonder if this means the linker is expecting the __cdecl convention for the toolkit functions when they were built using __stdcall?

Even if the problem with the test_output.cpp issue is resolved, there is still the issue if an app should be allowed to access an open project's output file or not. What if the app opens the file and then tries to use the toolkit to make another analysis before closing it. The toolkit function EN_initQ will fail since it can't re-open the output file. If instead the app simply gets a copy of the output file to work with then this situation is avoided. I'm leaning towards walking back this recent change and going with the EN_copyoutfile approach instead. Does anyone have an opinion on this?

@LRossman When weighing issues like this I think about when such an error would most likely get detected -- either during development or when in application is live and in the wild. If someone developing a client application didn't close the output file prior to running another analysis this would most likely be identified as an issue during development. Making it less serious in my mind.
The other thought I have is that the user may not want to use the same output file over again, they may want to work with several output files (imagining someone running and comparing scenarios). So we need a way to easily specify the creation of an output file for the current model run.
Lastly, unlike report files, output files can be very large. This makes copying them potentially expensive in terms of process time and storage space.
So I would stop second guessing it, I think the solution already checked in is a pretty decent one.


Plugin not working correctly when sniffs install depth is equal to "1"

Problem/Motivation
Since I use the "*" constraint in our projects, the package updated to 0.3.0 today. Right now, the default PHPCompatiblity sniff can not be found. I have not yet looked into it myself in the hope that you might know right away what the issue is.
Expected behaviour
PHPComptability sniff should still be installed
$ ./vendor/bin/phpcs -i
The installed coding standards are Zend, PHPCS, MySource, PSR2, PEAR, PSR1, Squiz and PHPCompatibility

Actual behaviour
Sniff is not installed:
$ vendor/bin/phpcs -i
The installed coding standards are Zend, PHPCS, MySource, PSR2, PEAR, PSR1 and Squiz

Steps to reproduce
composer.json:
  "require-dev": {
    "squizlabs/php_codesniffer": "^2",
    "dealerdirect/phpcodesniffer-composer-installer": "*",
    "frenck/php-compatibility": "*"
  }

Delete vendor folder (if 0.2.1 which still works was installed, the sniff is still there)
$ composer update
$ vendor/bin/phpcs
$ ./vendor/bin/phpcs --standard=PHPCompatibility --extensions=php ./src
$ ./vendor/bin/phpcs -i

Proposed changes
Is there a migration I missed or needs frenck/PHPCompatibility a new version too?
Thanks in advance for any help.

@bastianschwarz Thank you for this bug report.
There are no migrations needed, so nothing wrong on your end.
I will run test against the latest version asap and report back.

I was not successful in reproducing.
I've created an empty directory and place the following composer.json:
{
    "name": "frenck/test",
    "require": {
        "squizlabs/php_codesniffer": "^2",
        "dealerdirect/phpcodesniffer-composer-installer": "0.2.1",
        "frenck/php-compatibility": "^7.1"
    }
}

Ran composer install, and it worked as expected.
Next I've modified the version of this plugin in the composer.json to * and ran composer update.
$ ./vendor/bin/phpcs -i
The installed coding standards are MySource, PEAR, PHPCS, PSR1, PSR2, Squiz, Zend and PHPCompatibility

$ ./vendor/bin/phpcs --config-show
installed_paths: /Users/frenck/code/test/vendor/frenck/php-compatibility

I've also tried a version with a fresh install using the latest version directly, this also worked fine.
Some extra questions:

Did you update anything else? Like the PHP_CodeSniffer package?
Are having this issue in a public project I could take a look at?
Is this install global of localized in a project?

No, the PHP_CodeSniffer version was not updated and it's a local install, not a global one.
I'm at home now and have to wait for my food, so I'll see if I can repoduce the issue with any of my own projects which use the same setup.

Just reproduced it with one of my projects: https://github.com/codenamephp/platform.di
There is an ant build.xml in the project root that executes the compatiblity check, basically the same call I did in the issue description.
1. $ ant phpcomp -> works

$ composer update; ant phpcomp -> updates to 0.3.0 -> still works (sniff still in place from the previous install)
$ rm -rf vendor; composer update; ant phpcomp -> installs 0.3.0 again -> Exception
revert to 0.2.* -> $ composer update -> installs 0.2.1 again -> still exception
$ rm -rf vendor; composer update -> installs 0.2.1 -> works

Seems like there is something wrong when the components are already installed and the versions are switched?

I will check your project locally.
Note: You're talking about exceptions. It would be really useful if you'd include them in this issue report.

Sure, it's just the default "Sniff not found"
phpcomp:
  [phpcomp] PHP Fatal error:  Uncaught PHP_CodeSniffer_Exception: Referenced sniff "PHPCompatibility" does not exist in /home/bastian/workspace/codenamephp/platform.di/vendor/squizlabs/php_codesniffer/CodeSniffer.php:1167
  [phpcomp] Stack trace:
  [phpcomp] #0 /home/bastian/workspace/codenamephp/platform.di/vendor/squizlabs/php_codesniffer/CodeSniffer.php(780): PHP_CodeSniffer->_expandRulesetReference(Object(SimpleXMLElement), '/home/bastian/w...', 0)
  [phpcomp] #1 /home/bastian/workspace/codenamephp/platform.di/vendor/squizlabs/php_codesniffer/CodeSniffer.php(578): PHP_CodeSniffer->processRuleset('/home/bastian/w...')
  [phpcomp] #2 /home/bastian/workspace/codenamephp/platform.di/vendor/squizlabs/php_codesniffer/CodeSniffer/CLI.php(956): PHP_CodeSniffer->initStandard(Array, Array, Array)
  [phpcomp] #3 /home/bastian/workspace/codenamephp/platform.di/vendor/squizlabs/php_codesniffer/CodeSniffer/CLI.php(113): PHP_CodeSniffer_CLI->process()
  [phpcomp] #4 /home/bastian/workspace/codenamephp/platform.di/vendor/squizlabs/php_codesniffer/scripts/phpcs(25): PHP_CodeSniffer_CLI->runphpcs()
  [phpcomp] #5 {main}
  [phpcomp]   thrown in /home/bastian/workspace/codenamephp/platform.di/vendor/squizlabs/php_codesniffer/CodeSniffer.php on line 1167
  [phpcomp] Result: 255

@bastianschwarz I was able to reproduce the issue with this repository, thank you. I've actually pinpointed the situation where it goes wrong, let me explain.
Running a composer update on your repository actually causes 31 packages to update and 1 new dependency is installed newly. Including:

dealerdirect/phpcodesniffer-composer-installer (v0.2.1 => v0.3.0)
squizlabs/php_codesniffer (2.7.0 => 2.8.0)
frenck/php-compatibility (7.0.8 => 7.1.1)

I tried from scratch again, this time upgrading the 3 packages above in the order listed, running ant phpcomp between each package update.
After upgrading dealerdirect/phpcodesniffer-composer-installer (v0.2.1 => v0.3.0) it actually worked as expected.
After upgrading squizlabs/php_codesniffer (2.7.0 => 2.8.0) it broke down the way you described.
Lastly (while still being broken) I upgraded frenck/php-compatibility (7.0.8 => 7.1.1) and now it actually worked again! So the issue occurs when PHP_CodeSniffer is upgraded.
Updated issue description:
The plugin is unable to handle upgrades on the PHP_CodeSniffer package. It seems like the plugin is not triggered?
Since PHP_CodeSniffer actually stores its settings inside her own vendor directory, the setting are lost on upgrade. This is bad design on the PHP_CodeSniffer side. Nevertheless, since this plugin is not acting properly on this upgrade either, the configuration is not fixed / recreated.
Workaround:
You could easily work around this by triggering an extra composer update command, which will fix the configuration for you.
composer update
composer update nothing
ant phpcomp

Sadly, the workaround did not work for me, neither for the update nor a clean install so I had a look at the plugin.
What I found:
After a clean install, the installedPaths are empty. The "frenck/php-compatibility" package is found by getPHPCodingStandardPackages() but since the Finder in updateInstalledPaths() sets the depth to >1 (which is depth 2), but the ruleset.xml in the frenck/php-compatibility is in level 1 within the install path, the path is never added to the config.
Since I'm already kinda tired and I don't know if this is really just a "greater than vs greater than equals" issue or if I'm missing something in the big picture, I was kinda too lazy to fork, write a test and create a pull request. ;)
If I change the depth to >0, it worked for a clean install and for the update.
Maybe @christopher-hopper sees instantly if the >1 is acutally needed or if >0 is sufficent enough?

@bastianschwarz same here, needed to change minimal depth in order to properly install PHPCompatibility. Half an hour lost.

@bastianschwarz Thanks for the details, it is evening here, I will take a look at this issue in the morning.
@Wirone I'm sorry for your lost of time and any frustrations that might have caused.
@frenck I'll set up some test scenario's Friday to validate the various use-cases that the plugin is supposed to support. Maybe add those unit-tests we talked about.
I've you can all spare us a day or so, this issue will most likely be resolved.

I'm taking a look at the Finder depth method docs and testing some scenarios.
:+1: for some unit tests. I'll see if I can suggest a couple for this particular issue to prevent it ever reoccurring. I'll push that separately probably as it's part of the larger CI/Unit Testing push in #9
Apologise for not seeing this during development. Not sure how it fell through the cracks. Again, +1 for CI and  tests.

We've been debugging this issue and the Finder Depth does indeed seem to be the root of the issue.
However, it turns out that several other things coincide, causing some confusing behaviour:

When this plugin is installed globally, composer will load the global plugin
rather than the one from the local repository. Despite being documented behaviour,
this caused trouble for @frenck when trying to reproduce this issue, as another
version of the plugin was used than the one we thought we were looking at.

When working with an existing vendor directory, if composer update is run, composer loads the old plugin.  To clarify, the following steps occur:

The composer update command is run
A composer object is created
Version 0.2.1 of the plugin (which functions correctly) is loaded
Composer updates all dependencies (Updating the plugin code to v0.3.0)
The v0.2.1 plugin is triggered.

Unless PHP Codesniffer is updated, custom sniffs will not be installed as they
will still be triggered.
If PHP Codesniffer is updated, the custom sniffs will be removed. With the v0.2.1
version this is not a problem, as the sniffs will be installed again. With the v0.3.0
version (because of the finder-depth bug), custom sniffs are not installed.
The suggested solution is to change the >1 to  >=1 (as @bastianschwarz suggested),
document the (for us) unexpected behaviour surrounding updates and global installs and
make a new release as soon as possible.
There might possibly also be an issue with the logic that validates whether or
not PHP CodeSniffer is installed in relation with PHP Codesniffer updates. This
will be researched as a separate issue.

I've just released version v0.3.1, which includes a hotfix for the search depth issue.
Please note, as @Potherca wrote already, composer will use the previous installed plugin version while upgrading. If you still wind up with a broken setup after upgrading the plugin, please run composer update nothing in order to fix your configuration.

@frenck Just tested it in one of our projects, works! Thanks for the fix!

We also upgraded to 0.3.1 and it's working. Thanks!


E_UNDEFINED_METHOD: Method handle missing on App/Http/Middleware/RedirectLogin

I am having this error when I am trying to access middleware:
'use strict'
class RedirectLogin {

handle (request, response, next) {
const loggedIn = request.cookie('loggedIn');
if(!loggedIn){
response.route('login')
}
}
}

What you are trying to do? It seems that you are doing the same thing that the Official auth middleware.

Closing since no response from the issue reporter


Fix Youtube Seach

The library for searching on youtube is currently broken. Change it to the offical youtube search library

Will be fixed in https://github.com/linusromland/Velody/pull/88


Update docs requirements.

We're in a bit of dependency hell, but at least this cleanly installs for me.
Note that I was not actually able to test this out e2e; I never ended up getting docs generation to work on my mac even when I used a pipenv, and docs generation worked on my Linux box even when this failed.  So I am only claiming that pip install -r requirements.txt now works.  :)

UNEXPECTED EXCEPTION: ModuleNotFoundError("No module named 'opt_einsum'")

Not sure if that's me?

Sorry, I lost track of this. Is this good to go?

Sorry, I lost track of this. Is this good to go?

I think so!  Thanks!


error when following instructions in data preparation (Librispeech)

The following fails:
$ th MakeLMDB.lua -rootPath prepare_datasets/libri_dataset -lmdbPath prepare_datasets/libri_lmdb -windowSize 0.02 -stride 0.01 -sampleRate 16000 -processes 8
luajit: MakeLMDB.lua:62: attempt to index field 'file' (a nil value)
stack traceback:
        MakeLMDB.lua:62: in function 'code'
        MakeLMDB.lua:170: in function 'f'
        (command line):4: in main chunk
        [C]: at 0x00405d50
MakeLMDB.lua:127: attempt to index local 'vec' (a nil value)
<parallel#000>  closing session

because at some point it tries:
$ find -L prepare_datasets/libri_dataset/train -type f -name '*.sph'

and the file extension in libri_dataset is .flac not .sph. Adding the extension parameter solves the problem:
$ th MakeLMDB.lua -rootPath prepare_datasets/libri_dataset  -lmdbPath prepare_datasets/libri_lmdb -windowSize 0.02 -stride 0.01 -sampleRate 16000 -processes 8 -audioExtension flac

I also suggest changing the "-processes 8" to "-processes $(nproc)"

Do you have similar training/testing scripts (like AN4CTCTrain.lua/AN4CTCTest.lua) for Librispeech? I guess I can use the same script with different parameters but finding the correct parameters is the problem.
$ th AN4CTCTrain.lua -trainingSetLMDBPath ./prepare_datasets/libri_lmdb/train/ -modelTrainingPath ./models/libri/
.../luajit: ./Loader.lua:30: batchSize larger than lmdb size!
stack traceback:
        [C]: in function 'assert'
        ./Loader.lua:30: in function '__init'
        .../ML/torch/install/share/lua/5.1/torch/init.lua:91: in function <.../torch/install/share/lua/5.1/torch/init.lua:87>
        [C]: in function 'indexer'
        ./Network.lua:61: in function 'init'
        AN4CTCTrain.lua:40: in main chunk
        [C]: in function 'dofile'
        .../torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
        [C]: at 0x00405d50

Thanks so much! Done a few changes on the main branch using your suggestions. Usually if that's the case then the LMDB dataset wasn't found correctly or prepared correctly. I'll try to investigate further.

@SeanNaren: Could you respond to my question, please?
"Do you have similar training/testing scripts (like AN4CTCTrain.lua/AN4CTCTest.lua) for Librispeech?"

I've modified the main branch removing the AN4 convention. These scripts should be able to take an LMDB database in the correct format regardless if it's AN4. However you will need to update the parameters like below on run:
th Train.lua -trainingSetLMDBPath /path/to/lmdb/train/ -valSetLMDBPath /path/to/lmdb/test/

Hopefully this helps.


Enhancements in Filesystem Configuration

Re-submission of Enhancements in Filesystem Configuration after changing default branch (see https://github.com/dlt-hub/dlt/pull/856#pullrequestreview-1795937970)

Documentation on usage added to filesystem destination


Integrate web-config and http service discovery

Fixes #34
Fixes #35

sorry I don't know why my review was not sent yesterday

No problem, I will prepare a patch release to get the single issue resolved.


add park consideration

I was having some problems with my buildings within parks experiencing path fails. They would constantly not have enough goods to sell and keep matching against imports which cant reach them due to pedestrian roads.
I noticed some logic present in the decompiled code for the original Transfer Manager missing from this re-implementation. This logic skips potential matches depending on value of m_isLocalPark.
m_isLocalPark seems to be populated in AddIncomingOffer/AddOutgoingOffer for trades which should use a park service point for a delivery. I also added some logic to make their distance offers 0, since the goods are always just teleported to their destination.
After making this change I do not see any path fails in transfer logs for my building within pedestrian area.

Thanks for the PR - merged (as you can see), and will be included in the 0.7.7 update coming shortly.


Not possible to stop debug session if the Extension Host window was reloaded

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

VS Code Version: 1.86-1.88
OS Version: macOS 14 or Windows 10

Hello,
We keep experiencing this behaviour throughout multiple versions of VSCode already, starting approximately with 1.86. Every time the extension debug session started and Extension Host window is reloaded (using Developer: Reload Window command), the stop debug control in the command area becomes irresponsive. If to close the Extension Host window, the debug controls stays in the command area forever and the stop button still does not respond. Clicking on the Play button in the Run and Debug activity tab again, make the controls to disappear, but they are not going to be shown ever again, so the control on the just started debug session is lost completely. There is no way to restore the functionality except reloading the main window too.
This issue was noticed on both platforms: macOS and Windows.
Steps to Reproduce:

Go to Run and Debug activity tab and run the "extensionHost" debug launch configuration.
After Extension Host window appears, go back to the Main VSC window and make sure that Debug stop control is stopping the session correctly and the debug controls panel disappears from the command area.
Start the "extensionHost" session again and this time reload window using the "Developer: Reload Window" command from command palette, when the window appear. Return back to Main window and this time Debug stop Button is not responsive anymore.
Close the Extension Host window and notice that Debug controls did not disappear from the command area.
Start another debug session from the Run a Debug panel and notice that Debug controls now disappear, but when the Extension Host window appears and debug session started without any issues, the controls are not appear anymore, leaving the debug session totally uncontrolled.
Return to the Main windows and reload it. Repeat steps 1-3 and notice that the debug controls are available again till the next Extension Host window reload.

The launch configuration used:
// A launch configuration that compiles the extension and then opens it inside a new window
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Run E4E Extension",
      "type": "extensionHost",
      "request": "launch",
      "runtimeExecutable": "${execPath}",
      "args": [
        "--extensionDevelopmentPath=${workspaceFolder}/packages/explorer-for-endevor"
      ],
      "outFiles": [
        "${workspaceFolder}/packages/explorer-for-endevor/dist/*.js"
      ],
      "preLaunchTask": "build e4e"
    }
  ]
}

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.88.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Sorry for the slow response. Are you still seeing this?

I think this is the bug I fixed a little bit ago, please let us know.

Hi @roblourens @connor4312,
Thanks for the reminder. I can confirm that we do not experience this issue anymore since 1.89 release. Thank you very much for fixing it @connor4312 ❤
The issue can be closed. Cheers ✌


Preinstalled Scylla image has outdated packages after upgrade

When upgrading Scylla on preinstalled Scylla images, after upgrade we can see outdated packages. Example for upgrade from 5.0.3 to recent dev:
scyllaadm@rolling-upgrade--centos-db-node-30b489f7-2:~$ sudo apt list --upgradable
Listing... Done
intel-microcode/focal-updates,focal-security 3.20220809.0ubuntu<IP_ADDRESS> amd64 [upgradable from: 3.20220510.0ubuntu<IP_ADDRESS>]
scylla-machine-image/stable,stable 5.2.0~dev-20220914.04dc4b22edd-1 all [upgradable from: 5.0.3-20220908.86777998fad-1]
vim-common/focal-updates,focal-security 2:8.1.2269-1ubuntu5.8 all [upgradable from: 2:8.1.2269-1ubuntu5.7]
vim-runtime/focal-updates,focal-security 2:8.1.2269-1ubuntu5.8 all [upgradable from: 2:8.1.2269-1ubuntu5.7]
vim-tiny/focal-updates,focal-security 2:8.1.2269-1ubuntu5.8 amd64 [upgradable from: 2:8.1.2269-1ubuntu5.7]
vim/focal-updates,focal-security 2:8.1.2269-1ubuntu5.8 amd64 [upgradable from: 2:8.1.2269-1ubuntu5.7]
xxd/focal-updates,focal-security 2:8.1.2269-1ubuntu5.8 amd64 [upgradable from: 2:8.1.2269-1ubuntu5.7]

When upgrade starts from older version (e.g. 4.6) we can see even older packages.
It looks upgrading with use of scylla-packages file is not upgrading all the packages. Thus upgraded VM != VM from image.
This is an issue as we don't extensively test Scylla with older packages like this.
Also what I can see from above listing, scylla-machine-image is also not upgraded when using scylla-packages file.

I would argue there no much use for scylla machine image after the first boot of an instance.
Maybe if we ever want to upgrade the login "motd" and such.

I would argue there no much use for scylla machine image after the first boot of an instance.
Maybe if we ever want to upgrade the login "motd" and such.

Maybe we don't care about this one, but package like intel-microcode is important. It looks this packages file is not created properly. So upgrade of AMI does not result in the same packages like in VM created from version we upgrade to.

@soyacz the packages you are referring to, are not directly depended by any of scylla packages, if they are import enough for scylla they should be on it's dependency graph.
https://github.com/scylladb/scylla-machine-image/blob/e7e7daa0ced4d650013849711d7ced5ebb6ed569/packer/scylla_install_image#L224
I don't think it's a real issue, with one exception we might need to be more explicit about, is the kernel.

I opened this discussion to resolve my concern: should upgraded image contain the same list of packages as in VM created from upgraded version?
I was thinking that the whole idea of scylla-packages file was about that.  Otherwise, we don't need this file at all - apt can resolve dependencies by itself without this file.

I opened this discussion to resolve my concern: should upgraded image contain the same list of packages as in VM created from upgraded version?
I was thinking that the whole idea of scylla-packages file was about that.  Otherwise, we don't need this file at all - apt can resolve dependencies by itself without this file.

Again I don't know who initiated this whole change to the upgrade docs, and for what reasons... I don't really fully understand what the idea here...

I would argue there no much use for scylla machine image after the first boot of an instance.
Maybe if we ever want to upgrade the login "motd" and such.

Maybe we don't care about this one, but package like intel-microcode is important. It looks this packages file is not created properly. So upgrade of AMI does not result in the same packages like in VM created from version we upgrade to.

intel-microcode is not important for a VM on AWS, to the best of my knowledge.

@mykaul scylla-packages file was not filled properly, but anyway I think we drop this approach anyway as specific versions can't be installed after newer one appears in Ubuntu repositories. @yaronkaikov please correct me if I'm wrong. Possibly this bug can be closed.


Update README.md

We are adding a single line of header text to test out the job thing we did. Now we're making the pull request

There is no need for this merge. This branch was just to test the automated task.