Forecast ETL performance improvement - parallel interpolation

Seb's findings:

While looking at https://github.com/ECMWFCode4Earth/vAirify/issues/27 I found a potential way to reduce the processing time of the > forecast "transformation". Currently, this is done by using ThreadPoolExecutor to loop over all cities and therefore doing a separate > > interpolation for each city. But xarray does provide a way to interpolate all cities in parallel in a single call (see https://docs.xarray.dev/en/stable/user-guide/interpolation.html#advanced-interpolation).
Implementing this would require quite some code changes so I made a small proof-of-concept script first comparing both methods. > > On my computer, this reduces processing times from 19 to 0.6 seconds. Would probably be good to have a quick chat about how this > could be best implemented, but I think it is worth it

PoC here: https://github.com/ECMWFCode4Earth/vAirify/blob/parallel-int/air-quality-backend/scripts/test-parallel-interp.py
Acceptance Criteria

bilinear interpolation should be done for all cities in parallel

Test Checklist:

[x] Test Analysis & discussion with developer
[x] Write Test Cases / Charters
[x] Test Cases & Charters Reviewed
[x] Test Cases Executed
[x] Test Charters Executed
[ ] Regression tests executed
[ ] Write Automation tests for regression

Test Analysis
To test:
Test Case required:
Test Charter:
Regression candidate:
Yes

Previous exploratory testing notes from 28/05

Test notes from 04/06


fix(app): disable view error details button if run is cancelled without ER

closes RQA-3088
when a run is cancelled without ER we need to disable the button.
currently working on desktop app but not on odd.
Overview
enable button if the command errors are not as a result of a cancel run.
Test Plan and Hands on Testing

[x] explanation in ticket

Risk assessment
low.

Tested! worked as expected!


feat: set proposal app from query param

Summary

Toward https://github.com/snapshot-labs/workflow/issues/235
Discussion https://discord.com/channels/955773041898573854/1296435871431786587
The current code is passing a hardcoded snapshot-v2 as app, when creating an offchain proposal.
This PR will:

use the app query param from the Editor when available, and use snapshot-v2 as fallback.
reflect the same changes for ethereum and starknet propose action

How to test

Go to a proposal editor (try on offchain and onchain)
append the app query param to the url: ?app=test-pr
Create a proposal
In the signature payload, you should see the app property set to test-pr
View your proposal metadata
app should be set to test-pr
When missing, app should be set to snapshot-v2

Note

when app is too long (>128chars), it will be ignored, and default value will be used

@bonustrack We have set app to snapshot-v2 by default since the beginning for offchain proposal. Should we also add this default value for all onchain proposals ?

@Sekhmet requesting review again, since spec has changed to include onchain proposals.

Looks good to me, only issue I found is that most likely we will refer users to editor without draft ID, so URL like this:
http://localhost:8080/#/sn-sep:0x00a330d13703f0af4f87e65d95c898297f8ce6e88ac7e9bff3b3bd270d2f6d5b/create?app=someapp
but this gets redirected to specific draft and app is lost.

Looks good to me, only issue I found is that most likely we will refer users to editor without draft ID, so URL like this: http://localhost:8080/#/sn-sep:0x00a330d13703f0af4f87e65d95c898297f8ce6e88ac7e9bff3b3bd270d2f6d5b/create?app=someapp
but this gets redirected to specific draft and app is lost.

Fixed


[add] from_transmission: Add human-readable 'status_desc'

Motivation for changes:
Use more user-friendly textual torrent statuses instead of numbers.
Detailed changes:
This PR add 'transmission_status_desc' for entries from transmission. While maintaining backward compatibility with existing configurations by still using numeric 'transmission_status', new field greatly improve readability of flexget configuration.

Hmm, so right now it's returning an integer? I sorta thought we were already returning the text status. Is there a way to do this without adding the int to string mapping in flexget? Transmissionrpc should be doing that for us https://bitbucket.org/blueluna/transmissionrpc/src/2d0a22304f0c74fb537221c3c8b49a603a9480eb/transmissionrpc/torrent.py#lines-26:34

Sorry for buzz, actually status is string already.


Added multi-step forecsting and tutorial, handling of covariates, and refactored dropout code

I added multi-step forecasting capabilities, as well as the ability to handle covariates.
I modified the model builder to build dropout layers after every layer if necessary (performance is good).
Layer builder can now handle Concatenate layers and multiple parent layers.
Renamed a few variables and added most of Ken's asks.
Wrote a custom layer module.
Wrote a metrics module.
Wrote more tests.

Three things:

init.py has an import that should either be removed or commented out.
choosing a forecast horizon beyond the edge of the test data breaks the prediction. This can be reproduced by setting a horizon = 20 in the "multi-step-forecasting.ipynb"
it is difficult to see if the multi-step forecaster is producing a forecast 'cone' such as we would expect from vanilla time-series models...can we better demonstrate this?

Fixes init.py

The Forecaster actually throws an error when your input time series is too short.

I don't think the multi-step forecaster produces a guaranteed forecasting cone. That only happens when we predict recursively.

I think all points have been addressed so I'm merging this in.
Regarding uncertainty in the forecasts, Toby was referencing the plots in 'incorporating-uncertainty.ipynb' and 'multi-step-forecasting.ipynb', where the final plots have dashed intervals around the forecasted points.


How can we help?
I would like someone else to build the manifest.
Please read and ensure the following

[X] The installer meets the above requirements

Please provide the following information
Download Page Url: https://github.com/zhongfly/mpv-winbuild
Publisher: zhongfly
Package Name: mpv-nightly
Description: a free, open source, and cross-platform media player (nightly version)
Package Version: 2023-06-28
Installer URL: https://github.com/zhongfly/mpv-winbuild/releases/download/2023-06-28/mpv-x86_64-v3-20230628-git-c3781b2.7z

Blocked by https://github.com/microsoft/winget-cli/issues/2899


 doesn't build on command line

I've two projects:

ClassLibrary. A .NET Framework 4.6.1 class library (using the SDK-style project type). This library depends on JSON.NET.

WpfApp1. A .NET Framework 4.6.1 WPF app (using the regular MSBuild). The app depends on  ClassLibrary.

Here is the issue: when I'm using <PackagReference> from both projects to JSON.NET, I can build and run in the IDE, but when I build on the command line, I get the following error:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Microsoft\NuGet\15.0\Microsoft.NuGet.targets(197,5):
error : The project.json is referencing the project 'ClassLibrary\ClassLibrary.csproj',
but an output path was not specified on an item in the ProjectReferencesCreatingPackages property. [WpfApp1\WpfApp1.csproj]

However, when I'm converting the WPF app's <PackagReference> to packages.config, the project builds on both command line and IDE. I can also build in both environments if I remove the WPF app's dependency on JSON .NET entirely. So the root cause seems to be presence of the <PackagReference>.
I've uploaded the repro project here.

I too cannot build projects with  from the command line.
I am referencing

in a class library project.
It builds correctly in the IDE and copies the referenced library to the bin; however, when I go to build from the command line, it fails with the following errors which are all included in the referenced package:
error CS0234: The type or namespace name 'VisualStudio' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)
error CS0246: The type or namespace name 'ISetupConfiguration' could not be found (are you missing a using directive or an assembly reference?)
error CS0246: The type or namespace name 'ISetupInstance' could not be found (are you missing a using directive or an assembly reference?)
error CS0246: The type or namespace name 'ISetupHelper' could not be found (are you missing a using directive or an assembly reference?)
error CS0246: The type or namespace name 'ISetupConfiguration' could not be found (are you missing a using directive or an assembly reference?)

I think this is a problem with NuGet rather than core MSBuild, so I've moved it to https://github.com/NuGet/Home/issues/4804.


startController/router vs systemd confusion

Document the difference between the startController/startRouter helper functions from ziti cli functions vs using systemd

closing


Bug 1819246: Set service account issuer to internal dns name of kube apiserver

The default issuer for bound service account tokens is updated to point to the internal dns name of the kube apiserver to ensure compatibility with the ServiceAccountIssuerDiscovery feature [1] added in kube 1.18. This fix is intended to be backported to 4.4 (the release that added support for bound service account otkens) before GA to ensure that the default will be compatible from introduction with the discovery feature without having to update the issuer (which would involve reissuing all existing bound tokens).
1: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#service-account-issuer-discovery
Related change: https://github.com/openshift/api/pull/617

/cc @sttts @stlaz

/retest

Also updated the enhancement for consistency: https://github.com/openshift/enhancements/pull/281

/hold cancel
/lgtm

/retest

/approve
/retest

/cherry-pick release-4.4


clusterclaim updates spec.namespace

Just started looking at Hive, and it is indeed a very interesting project. I'm particularly interested in the new clusterpool feature.
However, looking at the current implementation, when I create a clusterclaim CR the controller signals back to me which cluster "I have received" by updating .spec.namespace However, this approach seems to break with the API convention as outlined for Kubernetes: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md
My intuitive expectation would be to declare my intents in .spec and find the "response" in .status, so in other words after creating a clusterclaim object I would expect to find the namespace in .status.namespace rather than .spec.namespace
Am I wrong in my understanding that the current implementation breaks with the api convention?

@dgoodwin @staebler any thoughts on this?

Yes Matthew's comment covers why we do this. We've struggled with this in earlier versions of our API and now use status only for what can be observed. It also helps when using backup tooling such as Velero for information that you cannot lose.

Right. It makes sense now that I understand these points. I guess the more simplistic use cases with the core primitives has set embedded a pattern of thinking that may not hold in the more complex scenarios.
Thanks for explaining. Pattern adjusted...


[Product Topics] social-media is missing on top of the topic detail page

https://stage.lifesciences.danaher.com/us/en/products/assay-kits/topics/how-are-assay-kits-installed.html

@sharanagoudapatil could you verify #440 if it fixes this issue too?

https://419--danaher-ls-aem--hlxsites.hlx.page/us/en/products/assay-kits/topics/how-are-assay-kits-installed - Here at the bottom not showing complete one. Please check.

This issue is fixed as part of #440. Hence closing this task. Thanks.


Fix devcontainer for latest Frigate and Home Assistant

Depends on https://github.com/blakeblackshear/frigate-hass-integration/pull/720

Also:

Make vscode automatically run yarn start on startup

@dermotduffy, it's working like a charm now (again). We just need to wait for the PR at the integration side to be merged.

@dermotduffy, it's working like a charm now (again). We just need to wait for the PR at the integration side to be merged.

Done!

Thank you, this one is ready to merge now too.

Thanks @felipecrs !


On the gene page in "All loss of function and missense variants" table, it says OR but reports beta

If we want to show odds ratio (OR), need to take OR=exp(beta). But for quantitative traits (BMI, height, weight) there is no OR so showing beta for all traits would be simple and consistent across binary and quantitative traits

@anastasia-shch if you can switch text to beta

Added as a part of https://github.com/FINNGEN/pheweb/commit/8740206845c5c926495d22eca14a3b02fc19a4dd


error： _multiprocessing.SemLock( FileNotFoundError: [Errno 2] No such file or directory

I successfully ran the pytorch example. But when i use datalaoder prefetch_factor in pytorch example.
like this
train_loader = torch.utils.data.DataLoader(
        datasets.MNIST('data', train=True, download=True,
                       transform=transforms.Compose([
                           transforms.ToTensor(),
                           transforms.Normalize((0.1307,), (0.3081,))
                       ])),
        batch_size=BATCH_SIZE, shuffle=True, num_workers=2, prefetch_factor=2)

i got this error:
Traceback (most recent call last):
  File "//./pytorchexample.py", line 112, in <module>
    train(model, DEVICE, train_loader, optimizer, epoch)
  File "//./pytorchexample.py", line 49, in train
    for batch_idx, (data, target) in enumerate(train_loader):
  File "/usr/local/lib/python3.9/dist-packages/torch/utils/data/dataloader.py", line 368, in __iter__
    return self._get_iterator()
  File "/usr/local/lib/python3.9/dist-packages/torch/utils/data/dataloader.py", line 314, in _get_iterator
    return _MultiProcessingDataLoaderIter(self)
  File "/usr/local/lib/python3.9/dist-packages/torch/utils/data/dataloader.py", line 900, in __init__
    self._worker_result_queue = multiprocessing_context.Queue()  # type: ignore[var-annotated]
  File "/usr/lib/python3.9/multiprocessing/context.py", line 103, in Queue
    return Queue(maxsize, ctx=self.get_context())
  File "/usr/lib/python3.9/multiprocessing/queues.py", line 43, in __init__
    self._rlock = ctx.Lock()
  File "/usr/lib/python3.9/multiprocessing/context.py", line 68, in Lock
    return Lock(ctx=self.get_context())
  File "/usr/lib/python3.9/multiprocessing/synchronize.py", line 162, in __init__
    SemLock.__init__(self, SEMAPHORE, 1, 1, ctx=ctx)
  File "/usr/lib/python3.9/multiprocessing/synchronize.py", line 57, in __init__
    sl = self._semlock = _multiprocessing.SemLock(
FileNotFoundError: [Errno 2] No such file or directory

Duplicate of https://github.com/gramineproject/graphene/issues/2689
Unfortunately, it is a known issue -- Gramine doesn't support the multiprocessing package of Python. This is because Gramine currently doesn't support Sys-V semaphores, which the multiprocessing package requires.


RC test: Coulomb's Law 1.0.0-rc.8

After a minor big was introduced in RC 7, I released the updated version. Below is a copy from the previous issue.
@KatieWoe, @arouinfar, @jessegreenberg, @ariel-phet  coulombs-law/1.0.0-rc.8 is ready for a final spot RC check. Document issues in https://github.com/phetsims/coulombs-law/issues and link to this issue.
There are a few issues discovered from the last RC that won't be addressed prior to this publication. They are noted below.
Assigning @ariel-phet for prioritization.

General RC Test

What to Test

Click every single button.
Play with the sim normally.
Try to break the sim.
Test all query parameters on all platforms. (See QA Book for a list of query parameters.)
Complete the test matrix.
Check this LoL spreadsheet and notify AR if it not there.

Issues to Verify
These issues should have the "status:fixed-pending-testing" label. Check these issues off and close them if they are fixed. Otherwise, post a comment in the issue saying that it wasn't fixed.

[ ] Text goes off screen
[x] Dilate touch areas on charge NumberControls
[x] Forces are not equal and opposite

iOS crashing is apparently no longer an issue, but we should still check to ensure it doesn't arise again.

[ ] Crash on iOS 10

The following issues won't be addressed prior to publication.

Legends of Learning page freeze
Moving one charge can move the other charge

inconsistently appears and is possibly a FF-specific issue

Jumpy distortion on Firefox while resizing window

appears to be another FF bug

Keyboard Nav Issues

issues witnessed are actually desired/standard behavior

Link(s)

Simulation
iFrame
XHTML
Test Matrix
Legends of Learning Harness

Accessibility (a11y) RC Test

What to Test

Specific instructions can be found below.
Make sure the a11y feature doesn't negatively affect the sim in any way.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.
Test all keyboard navigation inputs (if applicable).

Link(s)

a11y View
Simulation
Test Matrix

Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended.

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

[ ] Win 10 chrome Full
[ ] Win 10 firefox
[ ] Win 10 edge Full

[ ] Mac 10.14 chrome
[ ] Mac 10.14 firefox Full
[ ] Mac 10.14 safari Full

[ ] iOS 12 Full
[ ] iOS  10

[ ] Chrome OS

[ ] Win 7 IE Full
[ ] Win 7 chrome
[ ] Mac 10.11 safari
[ ] Mac 10.11 firefox

Keyboard nav seems to behave a bit oddly if you start in after manipulating one of the charge sliders.  I'm in firefox, but chrome was being a bit odd too.  I don't think its broken, but you might want to take a look for yourself.  It takes two key presses to start in firefox, and it starts in an unexpected location.
But it doesn't do this if you were manipulating anything but those sliders.  Chrome does something similar, but it starts at the beginning after manipulating the sliders.  Not sure if this is issue worthy.  Let me know.

I'll put it in an issue.


Example needed for monorepo with Azure pipeline

Please can you provide more details and an example of how to use Azure pipeline with a monorepo?

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

ID: b4cbd10e-57b8-de97-b84f-6e46f865c662
Version Independent ID: 533b11b0-5ada-f9c6-65f1-5966df142fa8
Content: Build configuration for Azure Static Web Apps
Content Source: articles/static-web-apps/build-configuration.md
Service: static-web-apps
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

@leonie-farmer Thanks for the feedback! We are currently investigating and will update you shortly.

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


Inline disable/enable linters are being ignored

Was working fine a couple of weeks back, we have since updated our dev environments and inline linters seem to be ignored
// scss-lint:disable PropertySortOrder
.page-wrapper {
  margin: 0 auto -200;
  min-height: 100%;
  height: auto;
}
// scss-lint:enable PropertySortOrder

Still returns:
PropertySortOrder:  Properties should be sorted according to the custom order specified by the configuration

I note the return message is now "according to the custom order..." whereas it used to tell us the custom order.

Hey @peavers, thanks for the report.
I can't reproduce this with the latest version of scss-lint. Running scss-lint 0.37.0 (latest version at time of writing) against the snippet you provided results in no lints reported.
However, it's possible that this is related to #429 which is fixed on master, but as I already mentioned I can't reproduce with version 0.37.0, which doesn't have that fix.
If you have any other information to provide, that would be extremely helpful; otherwise I'm going to have to close due to lack of reproducibility.

I just rebuilt the server again and can confirm I'm no longer having any issues so it must have been something unique to me, or I just incorrectly configured something at one point.
Confirmed working correctly with scss-lint 0.38.0


How to update npm?

What is the "correct way" to update NPM when using nvm?
Also.. is it possible to use yarn? If so, again, what would be the best way?

Thank in advance

nvm manages node, not npm. npm install -g npm is how you update npm, with or without nvm.
You can use yarn, if you like - npm install -g yarn. Just like you would without using nvm.

nvm install-latest-npm

Attempt to upgrade to the latest working npm on the current node version

Those instructions are a bit silly; you can npm install -g npm from anywhere.

@ljharb I ran npm install -g npm many times, and always worked fine. But the next time npm would suggest an update anyway. Turned out that npm install -g npm was updating /usr/bin/npm, not ~/.nvm/versions/node//bin/npm

@matteplus that command needs to be run while nvm using the proper node version; in other words, it will update whichever which npm is, which is expected. You don’t want to be using your system npm to update an nvm-managed npm.

That definitely seems strange. Glad you found a workaround, but the proper solution should work for the majority, ideally.

(It follows npm root -g in reality, so maybe you had a prefix set or something)

I tried to downgrade and upgrade again and now it works as you described. So yes, possibly something was wrongly set and now it's fixed. Thanks for your responses

I had this issue today.
However all of the proposed solutions didn't work for me.
running which npm returned /home/iamkratos/.nvm/versions/node/v9.11.1/bin/npm which is clearly the one managed by nvm, running npm i npm show a successful update but when I check with npm -v it returns the older version.
I looked into the nvm directory ~/.nvm/versions/node/v9.11.1/bin and ran ./npm -v now it returns the newer version.
I had to set an alias for npm in my ~/.bashrc'.  alias npm="~/.nvm/versions/node/v9.11.1/bin/npm"`
It works globally now.

I'm still running into this issue even with a fresh nvm install (moved ~/.nvm somewhere else, reinstalled via curl, installed node v10.0.0). None of the other methods mentioned here seem to work
~ npm -v
4.6.1
~ npm i -g npm
/home/user/.nvm/versions/node/v10.0.0/bin/npm -> /home/user/.nvm/versions/node/v10.0.0/lib/node_modules/npm/bin/npm-cli.js
/home/user/.nvm/versions/node/v10.0.0/bin/npx -> /home/user/.nvm/versions/node/v10.0.0/lib/node_modules/npm/bin/npx-cli.js
/home/user/.nvm/versions/node/v10.0.0/lib
└──<EMAIL_ADDRESS>
~ which npm
~/.nvm/versions/node/v10.0.0/bin/npm
~ npm -v
4.6.1

npm i -g npm is definitely the way to go. Just make sure to open a new terminal session, or else it will still report an older version enven after a successful upgrade.

@vspedr for npm, opening a new terminal session is not required.

@ljharb running npm -v right after npm i -g npm for some reason reports the same version it did before the upgrade. Not that it's a nvm issue, I'm only mentioning it because I lost a few minutes thinking npm did not upgrade successfully when it did

That sounds like a different, troubling issue, and implies your which npm would report the wrong one - in the typical case you shouldn’t have to restart the terminal to reflect changes in npm or node, only in nvm itself.

The only think that worked for me is to go nodejs\node_modules\npm and change the version ("version": "6.8.0") and then execute npm install from the current directory and delete the files that were marked as existing on error(only 2 files i think). With npm i -g npm@latest I deleted more files which broke it and then needed to reinstall the node.

@Tazzmanian on windows, you’d need WSL for this project to work; however, if npm install -g npm doesn’t work then it’s a bug with npm itself.

You might be running an old version of nvm; try reinstalling the latest.

Those using NVM for Windows will struggle to get this npm update feature. I have NVM 1.1.7 which is the latest version on Windows and nvm install-latest-npm does not work :(

@Seefer that’s because that’s not nvm, it’s nvm-windows, an entirely unrelated project. The latest version of nvm is v0.34.0 as of this writing.


sys: ring_buffer: ring_buf_peek() and ring_buf_size_get()

Add ring_buf_size_get() to get the number of bytes currently available in the ring buffer.
Add ring_buf_peek() to read data from the head of a ring buffer without removal.
Fixes #37145

Tests to follow later today.

minor update to tests to remove redundant asserts (where coverage exists in other tests) and to improve clarity of messages in assert messages.

minor whitespace fixups

@nordic-krch , @nashif - any additional thoughts about this one? Reviews?

Pulled this in to our local branch and it... seems to work.  Thanks!


Return error code on failed deployments

I've tested this new version of mup against my CI & CD containers but whenever a deployment verification fails my CI (using Gitlab CI) reports the "Deployment was successful!".
I'm guessing mup doesn't return a correct exit code yet when the command stops because of a failed deployment and Gitlab CI reports everything worked out fine because the script executed perfectly.
If I remember correctly this did work in MupX.

Can you post some logs?

This is what Gitlab CI returns at the end of the CI execution log. As you can see mup returns an error on verifying the deployment and at the bottom gitlab returns "build succesful" while it should not.
I checked the mup code and saw you do actually return exit codes on errors, do you think this is an issue with Gitlab CI rather then mup?
[luna.moonkin.space] - Start Meteor
[luna.moonkin.space] - Start Meteor: SUCCESS
[luna.moonkin.space] - Verifying Deployment
[luna.moonkin.space] x Verifying Deployment: FAILED```

	-----------------------------------STDERR-----------------------------------
	ges made to `npm run-script` and
	npm WARN deprecated semver behavior.
	npm WARN package.json<EMAIL_ADDRESS>No description
	npm WARN package.json<EMAIL_ADDRESS>No repository field.
	npm WARN package.json<EMAIL_ADDRESS>No README data
	npm WARN cannot run in wd<EMAIL_ADDRESS>node npm-rebuild.js (wd=/bundle/bundle/programs/server)
	=> Starting meteor app on port:80

	/bundle/bundle/programs/server/boot.js:324
	}).run();
	   ^
	Error: $ROOT_URL, if specified, must be an URL
	    at Error (<anonymous>)
	    at Meteor.absoluteUrl.options (packages/meteor/url_server.js:8:1)
	    at packages/meteor/url_server.js:19:1
	    at /bundle/bundle/programs/server/packages/meteor.js:1365:3
	    at /bundle/bundle/programs/server/boot.js:283:10
	    at Array.forEach (native)
	    at Function._.each._.forEach (/bundle/bundle/programs/server/node_modules/underscore/underscore.js:79:11)
	    at /bundle/bundle/programs/server/boot.js:133:5

	=> Redeploying previous version of the app

	-----------------------------------STDOUT-----------------------------------

	To see more logs type 'mup logs --tail=50'

	----------------------------------------------------------------------------

`Build succeeded.`

Another instance when it fails to report the right state, well at least, that's what it seems to look like, maybe it's gitlab, not sure.
Building App Bundle Locally
Errors prevented bundling:
While building for os.linux.x86_64:
imports/orders/emails/templates/index.js:3:25: Unexpected token (3:25)

=> Build Error. Check the logs printed above.

Build succeeded.

Where is this file do you think?
imports/orders/emails/templates/index.js:3:25: Unexpected token (3:25)

@MasterJames My apologies if I wasn't clear enough on the subject, but this issue is not about why my apps are failing to deploy. This issue is about why GitLab CI (and possibly other CI platforms) are reporting the build went well while in reality it failed.
Which errors are causing mup to fail in deploying the app are irrelevant to this issue, the error you are pointing out has been put there on purpose to demonstrate mup is failing to report the correct error code to my Gitlab CI runner instance.
The Build succeeded. line is not printed by mup, it is printed by Gitlab CI as the "result" of my build.
It is possible this is an error with Gitlab CI, but since this did seem to work fine with MupX I thought I'd report it here.


remove R&D calls

We haven't been running those for a while, and someone did ask me about it. Let's add it back when we actually start doing them again.

Codecov Report

Merging #267 (cbf53c5) into main (f4fed28) will decrease coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #267      +/-   ##
==========================================
- Coverage   54.81%   54.74%   -0.07%
==========================================
  Files          41       41
  Lines        2899     2899
==========================================
- Hits         1589     1587       -2
- Misses       1148     1149       +1
- Partials      162      163       +1

Impacted Files
Coverage Δ

opnode/rollup/driver/state.go
83.67% <0.00%> (-1.37%)
:arrow_down:

Continue to review full report at Codecov.

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


Looking at commits after update

Is there currently a mechanism for reviewing diffs from various plugin updates? For example, I would like to press  on the list of commit changes and view it. This would be an awesome feature IMO, and I may build it out if it isn't there.

@ianks PlugDiff I believe is what your looking for, shows you recent updates to plugins and their log messages.

I have related question to ask, so I thought I won't open separate issue. Can I load all patches in buffer? I know I can move cursor on commit hash and press <Enter>, but that's pretty tiresome. I would like to review all changes in all plugins since last update at once.


Confusion around io_uring-udp.c example

This line confuses me:
https://github.com/axboe/liburing/blob/63342497bec87b72d4b415c8bed930c15ff83b0d/examples/io_uring-udp.c#L255
Isn't that how you indicate EOF for SOCK_SEQPACKET? None of this seems documented anywhere which has been a struggle.

I also can't get auxiliary data to show up and I'm not sure what I'm doing wrong. This is the client syscall:
sendmsg(3, {msg_name={sa_family=AF_UNIX, sun_path="/tmp/asaveau.clipboard-history"}, msg_namelen=33, msg_iov=[{iov_base="\0", iov_len=1}], msg_iovlen=1, msg_control=[{cmsg_len=20, cmsg_level=SOL_SOCKET, cmsg_type=SCM_RIGHTS, cmsg_data=[0]}], msg_controllen=24, msg_flags=0}, 0) = 1

But at the other end after parsing out io_uring_recvmsg_out, controllen is zero. Is there anything I'm supposed to do to get it to work? Or an example

CC @DylanZA who wrote this example.

This line confuses me:
https://github.com/axboe/liburing/blob/63342497bec87b72d4b415c8bed930c15ff83b0d/examples/io_uring-udp.c#L255
Isn't that how you indicate EOF for SOCK_SEQPACKET? None of this seems documented anywhere which has been a struggle.

I don't believe so? validate validates that the structure of the single buffer is sane so you don't have buffer overruns

@SUPERCILEX did you increase the size of the CONTROLLEN? I suspect that is needed

BTW, sorry for not being clear: I'm trying to use the example as a starting point for my own code. I'm not running the example.

Ok, I'm thoroughly confused at this point. Let me explain the behavior I'm seeing:

First, the same buffer seems to be reused which doesn't make any sense. How can the kernel know I'm done with that buffer? Rather I think the flags aren't being set. Not sure what's going on there.
The result (aka size of the full buffer) is 16 + payload size on the first msg. Once the client closes the connection, the result is 16.

Ah! @DylanZA that's why I thought validation was wrong: because the kernel isn't giving me a new buffer, payload len is wrong and then validation rightfully fails because the buffer only includes space for the header.

Setting controllen doesn't do anything as far as I can tell

let mut hdr = unsafe { mem::zeroed::<libc::msghdr>() };
hdr.msg_controllen = 10;

---

[server/src/reactor.rs:132:21] &msg = RecvMsgOut {
    header: io_uring_recvmsg_out {
        namelen: 0,
        controllen: 0,
        payloadlen: 5,
        flags: 8,
    },
    msghdr_name_len: 0,
    msghdr_control_len: 10,
    name_data: [],
    control_data: [],

Control len works!!! Turns out it was silently being ignored because the buffer length was too small. That's deeply annoying if you ask me, why isn't controllen showing the true data size so I can tell that things were truncated?

Ok yeah truncation is totally broken in the sense that it doesn't happen at all. If I send 3 file descriptors (which requires 32 bytes), I silently only get 2 of them and io_uring_recvmsg_out says the size is 24. Is that expected?

Ok so I ran the example and it does put a new buffer in the flags. Maybe something is broken with SOCK_SEQPACKET?

Ok, the truncation stuff was just broken rust: https://github.com/tokio-rs/io-uring/pull/257
And I tweaked the udp example to use SOCK_SEQPACKET and the buffer management worked just fine, so I must have a bug in my code somewhere.

Ah yep for anyone wondering bgid and bid are different. :man_facepalming: bid is what's returned in the flags and I was setting it to bgid so obviously the buffers were broken.

Thanks for following up, always good to know what the issue was.  Is this something that could be improved in the man pages?

Thanks for asking for feedback, that's awesome! I don't think so:

The docs clearly state that bid is the buffer ID that will be returned in the CQE once consumed
The controllen truncation was a bug in library code, so not much to be done besides fix it

It was the usual lots of small bugs combining to make a big mess of debugging. :)


FPS drop and lags during streaming

Hi Thibault! First of all, thanks for the library!
Implementing streaming to my project I followed your experience as an example, but I ran into some difficulties. Do you mind if I ask few questions?
When you start the application, it is noticeable that the camera frame rate is below 30, although the value is set to 30, and when you start the stream, the fps drops even more. As far as I understood, this is due to the call to the holder.setFixedSize() method every time the surface changes.
I tried to call holder.setFixedSize() only in surfaceCreated() and then there are no problems with fps, but in this case, when the stream starts, the information about the set fps does not reach the server, which leads to errors and the stream does not play.
Can you please tell me how to fix this? I would be grateful for any advice!

Hi!
The first thing I can think of is that your CPU is overload. What is your device and Android version?
Do you have the same issue with the example application?
Do you have the logcat to see if anything wrong?
The preview has nothing to do with the live stream. Your camera device send frames to the preview and to the encoder. Changing something on the preview should not change anything on the live stream.

Thank you for the answer! I have Redmi Note 8 pro:
Android version - 11
MIUI - 12.5.3
CPU - MediaTek Helio G90T
RAM - 8GB
Yes, with your example application has the same issue.
Logs attached, also a screenshot Profiler. The application was launched with this SurfaceHolder.Callback::
    private val surfaceViewCallback = object : SurfaceHolder.Callback {
        var nbOnSurfaceChange = 0

        override fun surfaceCreated(holder: SurfaceHolder) {
            nbOnSurfaceChange = 0
        }

        override fun surfaceChanged(holder: SurfaceHolder, format: Int, width: Int, height: Int) {
            require(context != null)

            try {
                nbOnSurfaceChange++
                if (nbOnSurfaceChange == 2) {
                    viewModel.startPreview(holder.surface)

                } else {

                    val choices = context!!.getCameraOutputSizes(
                        SurfaceHolder::class.java,
                        viewModel.cameraId
                    )

                    chooseBigEnoughSize(choices, width, height)?.let { size ->
                        holder.setFixedSize(size.width, size.height)
                    }
                }
            } catch (e: Exception) {
                Log.e(TAG, "!!!Can't start preview due to ${e.message}!!!", e)
            }
        }

        override fun surfaceDestroyed(holder: SurfaceHolder) {
            viewModel.stopPreview()
            binding.surfaceView.holder.removeCallback(this)
        }
    }

LogsAfterStartingStream.txt
LogsAfterStoppingStream.txt

Hi,
Ok, everything seems alright. Your CPU is really low which is really good.
Anyway, I found this: https://stackoverflow.com/questions/57485050/how-to-increase-frame-rate-with-android-camerax-imageanalysis/57490987#57490987. It is for CameraX but the same settings apply to camera2.
As I only test on Nexus and Pixel, I might have miss something on other constructors. I want to be sure what setting really work on your phone.
It might take a while to test. Can you test on the sample of https://github.com/ThibaultBee/StreamPack/tree/bugfix/framerate?

I tested your example, fps is still low, but another problem has been added =).
The camera capture has become dark, although the room is light, there is also a problem with the aspect ratio, but it was there before too. I have attached screenshots.
I didn't change the video settings. They stood by default:
Encoder - AVC/H.264
Resolution - 1280x720
Framerate - 30
Video start bitrate - 2000
LogsAfterStartingStream.txt
LogsAfterStoppingStream.txt

Is there anything else I can be useful?

Ok.
The dark effect is because AE is disabled.
Anyway, I have changed https://github.com/ThibaultBee/StreamPack/tree/bugfix/framerate.
Can you retest it?

Hi Thibault!
Dark effect is gone, CPU does not overload, problems with fps remain, but I noticed that when switching to the front camera, fps does not drop.
I also wanted to clarify with you why call holder.setFixedSize () in surfaceChanged? Considering what you wrote: "The preview has nothing to do with the live stream. Your camera device send frames to the preview and to the encoder. Changing something on the preview should not change anything on the live stream". If it is needed for the correct aspect ratio of the surfaceView, then this doesn't work. I found this example https://github.com/android/camera-samples/blob/main/Camera2Video/utils/src/main/java/com/example/android/camera/utils/AutoFitSurfaceView.kt on google and it does a good job with aspect ratio. I don't have much development experience, so any advice from your side would be useful to me =).
LogsAfterStartingApp.txt
LogsAfterStartingStream.txt
LogsAfterStoppingStream.txt

The code in surfaceChanged comes from the former Android camera sample.
I replace this dirty mechanism by an AutoFitSurfaceView. Can you test again the sample of https://github.com/ThibaultBee/StreamPack/tree/bugfix/framerate?

Now there are no problems with fps, at least in SurfaceView, but the stream does not play. The same situation occurred when I called holder.setFixedSize () only in surfaceCreated (), which I wrote about earlier. As our backend developer explained to me, this happens because the fps information does not reach the server, which breaks the transcoding and leads to errors.
LogsAfterStartingApp.txt
LogsAfterStartingStream.txt
LogsAfterStoppingStream.txt

Now there are no problems with fps, at least in SurfaceView, but the stream does not play. The same situation occurred when I called holder.setFixedSize () only in surfaceCreated ()

Glad to hear. It's a good start :) but I don't understand why :(

As our backend developer explained to me, this happens because the fps information does not reach the server, which breaks the transcoding and leads to errors.

Which fps information are you talking about? Have you try with ffplay (ffplay -fflags nobuffer srt://<IP_ADDRESS>:9998?mode=listener)?

Which fps information are you talking about?

For example, if start stream using your library, the following information comes to the server:

Stream #0:0[0x100]: Video: hevc (Main) (HEVC / 0x43564548), yuv420p(tv), 720x1280, 30 tbr, 90k tbn, 90k tbc
Stream #0:1[0x101]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 48000 Hz, stereo, fltp, 130 kb/s

But the following information should come:

Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(tv, progressive), 1920x1080 [SAR 1:1 DAR 16:9], 50 fps, 50 tbr, 90k tbn, 100 tbc
Stream #0:1[0x101]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 48000 Hz, stereo, fltp, 122 kb/s

Have you try with ffplay (ffplay -fflags nobuffer srt://<IP_ADDRESS>:9998?mode=listener)?

Unfortunately not yet, but I want to try. As soon as I do this, I will inform you of the results :).

Oh, I guess your server expects the VUI in the SPS (especially the timing_info).
In H.264, VUI is not a mandatory field. vui_parameters_present_flag indicates if VUI is present in the SPS.
Both SPS and PPS are generated by the Android encoder API (aka MediaCodec) and MediaCodec chooses to not add VUI in the SPS.
You should consider to support incoming stream that does not have VUI.

Hi @BakhromMuydinov,
Have you fixed your issue?
By the way, I added AutoFixSurfaceView in the SDK instead of the sample.

Hi @ThibaultBee! I apologize for not getting in touch for a long time.
Yes, we fixed it, thank you very much!
But there is still a problem with the correct aspect ratio of the received stream. I also launched a stream on ffplay, there is the same problem.
What can be done about it?
Stream #0:0[0x20]: Video: hevc (Main) ([36][0][0][0] / 0x0024), yuv420p(tv, bt470bg/bt470bg/smpte170m), 720x1280, 29.58 tbr, 90k tbn
Stream #0:1[0x21]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 44100 Hz, stereo, fltp, 130 kb/s

Hi,
Glad you fixed your issue!
You are using StreamPack in portrait. Did you notice the same effect in landscape?
Regards,
Thibault

Hi!
The situation is better in landscape orientation, but still this effect is a little present in my opinion.
Stream #0:0[0x20]: Video: hevc (Main) ([36][0][0][0] / 0x0024), yuv420p(tv, bt470bg/bt470bg/smpte170m), 1280x720, 29.58 tbr, 90k tbn
Stream #0:1[0x21]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 44100 Hz, stereo, fltp, 131 kb/s

Hi!
Sorry for the delay, I have been really busy, + covid,...
Landscape seems alright on my side if you want to be sure, you should film a square and check if it is still a square on ffplay display.
Also, there is an issue in portrait but I try to fix it. Can you test https://github.com/ThibaultBee/StreamPack/tree/bugfix/portrait ?
Regards,
Thibault

Hi!
Ohh.. I wish you a speedy recovery!!
Now everything looks correct in portrait, landscape, and square =).
Thank you very much!!

Hello,
I merged the branch.
I am waiting for a last development before releasing 1.4.0. Are you okay to wait few days?
Also, could we have a chat on what you are going to do with this library, the features you are using, not using or missing? I am pretty sure you can find me on linkedin with my name.
Regards,
Thibaultt

I am waiting for a last development before releasing 1.4.0. Are you okay to wait few days?

No problem! I'm not in a hurry =).
Unfortunately, I'm not on LinkedIn, but if you want, we can chat on Telegram https://t.me/Scorpio1396.

Hi,
These issues are fixed. Fixes will be shipped with next release.
Best regards,
Thibault :)


feat: add protobuf 3.25.0 release

update protobuf with release 3.25.0

:tada: This PR is included in version 1.231.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Request:  New base 'simulate in time' algorithm

Right now, there's no base term for both LSODA-like and CVODE-like algorithms.  They are different from each other, but if one simulator uses one of them, a different simulator could probably use the other and obtain largely similar results.
This is in contrast to the other children of the 'modeling and simulation algorithm' base class that contains things like steady state solvers, or logical modeling analyses.
I think in general, the children of the 'modeling and simulation algorithm' term should be groups of algorithms that all take the same basic input and produce the same basic output.
Right now with SED-ML, it's the UniformTimeCourse' class itself that is fulfilling this role:  if a UniformTimeCourse object has an LSODA KiSAO term, the simulator knows it can probably use CVODE instead.  But for the 'Analysis' class, this is no longer the case:  if you wanted to define (say) a time course with no set end time, but instead a set number of variable steps, you would have to pick either LSODA or CVODE as your base , and there would be no programmatic way for another simulator to know they could probably use the other branch.

This information is encoded using characteristics, rather than the parent-child hierarchy. As I understand, this was by design to enable KiSAO to more flexibly capture information than what's possible with just parent-child relationships.

Ah, that makes sense.  However, I would still like a 'time course' KiSAO term, because then I can create more generic SED-ML files for the Analysis class (and the UniformTimeCourse class).

Time is not a special quantity to these algorithms. This is a mismatch between SED-ML UniformTimeCourse (where the variable of integration can only be time) and KiSAO (where the variable of integration can have any semantic meaning). While time is often the variable of integration, time is not always the variable of integration. In other words, time or time course is not a characteristic of these algorithms. If this information is encoded into KiSAO, it should encoded in a way that conveys that the variable of integration can, but does not have to be, time.

Sure, that works.  And then you could specify that you were integrating over time with a child term.


[Doc] Fix missing import and enhance httpClient data provider section

make description of the connecting httpClient to the data provider clearer

Thanks for your contribution :+1:


Add HoverConversion by @marty-suzuki to Table View / Collection View …

Project URL

https://github.com/marty-suzuki/HoverConversion
Description

Add HoverConversion by @marty-suzuki to Table View / Collection View …
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 8 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

…section

          1 Error

  :no_entry_sign:
  Found 4 link issues

Link issues by awesome_bot

Line
Status
Link

449
301
https://github.com/melvitax/AFDateHelper redirects tohttps://github.com/melvitax/DateHelper

1203
301
https://developer.apple.com/library/ios/documentation/DeveloperTools/Reference/UIAutomationRef/ redirects tohttp://developer.apple.com/reference

1929
301
https://github.com/neonichu/ThisCouldBeUsButYouPlaying redirects tohttps://github.com/segiddins/ThisCouldBeUsButYouPlaying

2137
301
http://code.tutsplus.com/categories/ios-sdk redirects tohttps://code.tutsplus.com/categories/ios-sdk

  Generated by :no_entry_sign: danger


Make calls through patchpoints in unopt functions.

This replaces the stackmap in the unoptimized version of the function which triggered the guard failure with  a patchpoint that takes a null callback. This is because all unoptimized functions must record the state using patchpoint calls, and not stackmap calls (as described in #14).

A couple of comments added.


The Raft Paper is not available.

the Raft Paper link in the Links for Further Research part is not available. the file is not found.

@YasinEnigma You can refer to https://raft.github.io/raft.pdf :)

@YasinEnigma You can refer to https://raft.github.io/raft.pdf :)
oh thanks :)

Lets leave this open until the link is fixed

opened https://github.com/tikv/raft-rs/pull/342, not sure how to link


the ptr-refactor

This PR refactors HVMC to use native pointers, rather than indices.
Due to scope creep, it also does lots of other things :)

Fixes #57
Fixes #56
Fixes #40
Closes #59
Closes #58
Closes #53

This is currently marked as draft, as merging it will be somewhat complicated (still need to fix merge conflicts & coordinate the sister PR higherorderco/hvm-lang#194), but the code itself is ready for review.

This looks like a great update. Very excited to see it land.


Add anyio.TaskGroup support to TRIO113

Stemming from #121
rewriting nursery detection to use type tracking - affecting TRIO105&TRIO113
Much of the diff is due to renaming eval_files/trio113.py to eval_files/trio113_trio.py with very minor changes, and having checks that aren't trio-specific in eval_files/trio113.py
I've realized that typing the eval files is often quite handy, and also to check pyright/mypy support for whatever check I'm writing. So I modified the config to longer blanket exclude eval_files, and added type: ignore at the top of all files except the ones I directly worked on in this one. Might gradually remove some of the other ones too.
Likewise got a couple # mypy: disable-error-code since I (still) am running that in my editor. It raises a lot more warnings than pyright, but most of the code in the repo passes it (without strict)

Haha, the perfect review comment :grin:


[BUG] Diff +/- are colored as punctuation (i.e: grey) instead of addition/deletions

Describe the bug

Open a diff file, observe that the +/- at the start of lines are grey.

When running Inspect I get:
  - @diff.minus.diff links to DiffDelete diff
  - @punctuation.special.diff links to Delimiter diff

Expected behaviour
It should show up as red/green instead of grey.
Screenshots
No response

I think this is related to https://github.com/nvim-treesitter/nvim-treesitter/commit/3aa2e2f3747ee11dc4460ad98b25e887c33bb610.

Correction: after applying https://github.com/ellisonleao/gruvbox.nvim/commit/20f90039564b293330bf97acc36dda8dd9e721a0, they are orange rather than grey. Arguably this is even more confusing.


"Users and Roles" is now called "Users and Access"

[Enter feedback here]

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

ID: babb7dd3-3eee-faa0-b4bc-d379428a004b
Version Independent ID: 41a95694-c39e-c16e-bb7b-f7df37862ff2
Content: StoreKit Overview and Retrieving Product Info in Xamarin.iOS - Xamarin
Content Source: docs/ios/platform/in-app-purchasing/store-kit-overview-and-retreiving-product-information.md
Product: xamarin
Technology: xamarin-ios
GitHub Login: @davidortinau
Microsoft Alias: daortin

Thanks for submitting an issue and we apologize for the delayed response. The requested updates haven't been made since the creation of the issue, and the timeline for resolution may vary based on resourcing, so the issue is being moved to an internal repo to better track it.


Connecting to custom back-end server

Hello, first of all: incredible project you have here!
I was hoping that someone could give me direction on hooking up this boilerplate to a custom REST API that I have being served by a Sails backend. It seems that the API server is quite hard-coded into the workflow and I am a bit newer to front-end.
Thanks!

Pretty common question. Some background reading: #135 #141 #159 #230 #432
Simple answer is here: https://github.com/erikras/react-redux-universal-hot-example/issues/432#issuecomment-151624780

Just exclude the API server part. (the api folder) If you want server-side rendering, you'll need the render server.

Actually doing it might be more complicated, but in general what you need to understand is that the rendering server (/src/server.js) does two things:

Render the React components, which may load data from an API server.
Proxy anything going to /api/* to an API server for client side data fetching. You can make the API server be whatever you want.

That's all the render server does. Session management is up to the API server. The render server will proxy cookies.
Hope that helps.

Thank you so much!

I'm attaching this excellent snippet from @korczis to aid future seekers of this path.
api-proxy.js
var httpProxy = require('http-proxy');
var https = require('https');
var apiProxy = httpProxy.createProxyServer();

app.get("/proxy/*", function(req, res){
  req.url = req.url.replace('/proxy/', '/');

  apiProxy.web(req, res, {
    target: 'https://api.github.com',
    agent  : https.globalAgent,
    headers: {
      host: 'api.github.com'
    }
  });
});

Why do we need to go thru proxy instead of directly talking to API end point?

@erikras not sure why but it sends the request to
{ Error: connect ECONNREFUSED <IP_ADDRESS>:80
[1]     at Object.exports._errnoException (util.js:953:11)
[1]     at exports._exceptionWithHostPort (util.js:976:20)
[1]     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1080:14)
[1]   code: 'ECONNREFUSED',
[1]   errno: 'ECONNREFUSED',
[1]   syscall: 'connect',
[1]   address: '<IP_ADDRESS>',
[1]   port: 80,
[1]   response: undefined }


Full view extension presentation on phosphorylation phenotypes

In these cases we could group
like
cdc2-33(A177T aa) affecting cdc18  modified residue T10A,T46A,T60AT104A,T134A
cdc2-33(A177T aa) affecting rap1 modified residue T378,S422,S513
etc

Yep, we can do that.  If I change the configuration so that residue extensions can be grouped together I get this:

https://desktop.kmr.nz/gene/SPBC11B10.09
We also have assay_using configured to group together so there are also summaries that look like this:

https://dev.pombase.org/gene/SPBC530.14c
Is that OK?

Not sure. @PCarme  is it clear  that the residue belongs to the preceding ID in the list?
Also in the first figure, by grouping be residue, we lose
cdc2-33(A177T aa) affecting cdc13, orc2, sld3
cdc2-L7(P208S aa) affecting cdc13, orc2
grouping
ideally it would be
allele  plus affecting + residue (when multiple residues, or single residue)
cdc2-33(A177T aa) affecting cdc18 modified residue T10A,T46A,T60AT104A,T134A
cdc2-33(A177T aa) affecting rap1 modified residue T378,S422,S513
cdc2-33(A177T aa) affecting xxx1 modified residue Txxx
THEN
all of the ones  for the same allele which have no residue
cdc2-33(A177T aa) affecting cdc13, orc2, sld3
then the same for each allele
Is that possible?
I think people will primarily want  the same allele together, then the most compacted version of that information.
At  the moment you need to look at the entire list to see the affects of a single allele.

is it clear that the residue belongs to the preceding ID in the list?

It is clear to me at least, although it feels a bit awkward.

ideally it would be allele plus affecting + residue (when multiple residues, or single residue)
cdc2-33(A177T aa) affecting cdc18 modified residue T10A,T46A,T60AT104A,T134A
cdc2-33(A177T aa) affecting rap1 modified residue T378,S422,S513
cdc2-33(A177T aa) affecting xxx1 modified residue Txxx
THEN all of the ones for the same allele which have no residue
cdc2-33(A177T aa) affecting cdc13, orc2, sld3
then the same for each allele

I agree, this would be a better solution overall

Sorry, I realise that I got this wrong.  The screenshot for cdc2 shows the residues grouped together but that was from when I had mis-configured my desktop site.
Adding the configuration to group by "modified residue" doesn't work in this case because (I now realise) it's not possible to group by two different extension relations in the same annnotation.  The code doesn't support that.  It's tricky code so I can't say how long this will take to fix.  I've having a look now.

Adding the configuration to group by "modified residue" doesn't work in this case because (I now realise) it's not possible to group by two different extension relations in the same annotation. The code doesn't support that.

I think I've fixed that, more or less.  There might still be some situations where the grouping doesn't happen, but I think most cases will be covered.  The change will be on pombase.org in the morning.

Fantastic. We will look it over and then we can also use the same configuration for other terms which have extensions and residues (if not already).
That would be all children of
abnormal protein modification (FYPO:0002494)
and
normal protein modification (FYPO:0002495)

So in the figure above I still see 3 rows for cdc2-33 affecting cdc18
ie
T104A, T10A, T134A
T46A, T60A
T374A

So in the figure above I still see 3 rows for cdc2-33 affecting cdc18

Yep, there are still have cases that aren't collected together.  It's tricky to get it working in all situations, but I'll have a look at that one tomorrow.

It's tricky to get it working in all situations, but I'll have a look at that one tomorrow.

I re-wrote the code to handle more cases.  This change will be on pombase.org soon:

This change will be on pombase.org soon

It's there now.  Let me know if you spot any problems.  It's new code which makes bugs more likely.

Amazing.  That's brillaint!

I'll close this.  Please open new issues if you see any bugs or other weirdness.


Fix time parsing

Do not parse time for emojis, where the id might have the same format as time

https://stackoverflow.com/a/7967113/4407321


Check backwards compatibility with old postgres provider

Describe the bug
https://astronomer.slack.com/archives/C03868KGF2Q/p1669131445686549?thread_ts=1669130287.404939&cid=C03868KGF2Q We should check the backwards compatibility with old Postgres provider.
Based on airflow version we should handle the database and schema

Closing this based on this slack thread: https://astronomer.slack.com/archives/C03868KGF2Q/p1669136191234039


feat: adds BUILD target to top-level BUILD file

Adds user-facing bazel build targets to the project's top-level BUILD
file. This file should list all of the BUILD targets that users are
allowed to use. In a future PR, visibility restrictions should prohibit
users from reaching down into google/cloud/spanner/BUILD.
This change will make things simpler for users since they'll have a
single, uncomplicated, top-level BUILD file that contains all the build
targets that they're allowed to use. It also gives us a place to put an
includes = ["."] directive, which will allow Bazel users to include
our headers using either double quotes or angle brackets.
Related to #1296

This change is

Note: a followup task for me after this PR is included in the next release is to update quickstart/ to use this new build target and using angle-bracket includes.
https://github.com/googleapis/google-cloud-cpp-spanner/issues/1416

FYI after this change I now get the following error.  I can work around it by doing bazel build google/... but still seems bad.
$ bazel build ...
ERROR: /home/salty/git/delete/BUILD:23:1: in includes attribute of cc_library rule //:spanner_client: '.' resolves to the workspace root, which would allow this rule and all of its transitive dependents to include any file in your workspace. Please include only what you need

Hmm.. ok, let me think about how best to fix that or whether to roll this back.
One fix would be to add tags = ["manual"] to the //:spanner_client build target.


[CardRenderer] dynamic variables in card data

Summary
Internal Watson-IoT/pal-tracking#379
Give cards the ability to have a prop of variable values that replace corresponding variables in the card data.
example:
{
size: 'LARGE',
title: 'Expanded {size} card',
type: 'IMAGE',
cardVariables: {
size: 'large',
},
content: { ... }
}
Would populate the card as if it was given a title of Expanded large card
Additional context
We have a request in Monitor to support this functionality. The user would specify a deviceId as a variable in their JSON file, which would get replaced by the value of that dimension.
Bringing it to the component level allows anyone that uses these cards access to this feature.
I have opened a PR with a non-invasive way to accommodate this feature for anyone that wants to use it.
PR: https://github.com/IBM/carbon-addons-iot-react/pull/1099

:tada: This issue has been resolved in version 2.73.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[WIP] This attempts to add an example of swapping SMIRNOFF for GAFF parameters for a protein-ligand complex

Some of our users (eg Dan McKay) could benefit from being able to easily drop SMIRNOFF parameters into existing workflows, such as by swapping out GAFF parameters for a ligand with OpenFF parameters.
This attempts to add an example of that, but it gets stalled on re-combining the parameterized protein with the OpenFF-parameterized ligand -- an issue with LJ ACOEFF parameters I haven't been able to sort out:

AmberError: FLAG LENNARD_JONES_ACOEF has 171 elements; expected 105

This odd, in that a very similar procedure works when setting up from scratch in one of our examples (https://github.com/openforcefield/openforcefield/blob/master/examples/using_smirnoff_with_amber_protein_forcefield/BRD4_inhibitor_benchmark.ipynb). I haven't been able to sort out what the critical difference is here, so I wanted to get this up in case someone can help.
Tagging @slochower and @j-wags who I think have touched some of these issues before.

Codecov Report

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

I might be missing something obvious, but I only see the topology in this PR. Can you post the code you tried?
Sent from my iPhone

On Dec 18, 2019, at 15:13, David L. Mobley<EMAIL_ADDRESS>wrote:

Some of our users (eg Dan McKay) could benefit from being able to easily drop SMIRNOFF parameters into existing workflows, such as by swapping out GAFF parameters for a ligand with OpenFF parameters.
This attempts to add an example of that, but it gets stalled on re-combining the parameterized protein with the OpenFF-parameterized ligand -- an issue with LJ ACOEFF parameters I haven't been able to sort out:
AmberError: FLAG LENNARD_JONES_ACOEF has 171 elements; expected 105
This odd, in that a very similar procedure works when setting up from scratch in one of our examples (https://github.com/openforcefield/openforcefield/blob/master/examples/using_smirnoff_with_amber_protein_forcefield/BRD4_inhibitor_benchmark.ipynb). I haven't been able to sort out what the critical difference is here, so I wanted to get this up in case someone can help.
Tagging @slochower and @j-wags who I think have touched some of these issues before.
You can view, comment on, or merge this pull request online at:
https://github.com/openforcefield/openforcefield/pull/476
Commit Summary
Try to prepare example of swapping SMIRNOFF for AMBER parameters. Encountered error.
File Changes
M examples/README.md (1)
A examples/swap_amber_parameters/tmp.top (305)
Patch Links:
https://github.com/openforcefield/openforcefield/pull/476.patch
https://github.com/openforcefield/openforcefield/pull/476.diff
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Ugh, sorry about that, missed the most important part, @slochower ! Should be here now.

I haven't dug in yet, but curiously, it seems like it's getting more LJ parameters than expected! Usually, it's less :)

Root cause is probably our lack of atom types -- ParmEd is expecting to fill a numerical array with the same number of pre-computed LJ interaction coefficients as the old ligand (apparently 14) [1].
However, since our new system has "more atom types", the size comparison fails. Oddly, the ligand has 26 atoms, not 18 (which should yield 171, per the formula in the code). My guess for the discrepancy is that ParmEd is clever enough not to pre-compute terms for atoms that only ever appear one or two bonds away from each other (since scale12 and scale13 are 0 in the normal FF)
[1]
>>> for i in range(14,20):
...     print(i, (i*(i+1))//2)
...
14 105
15 120
16 136
17 153
18 171
19 190

My suspicion is that pieces[0][0] still has ties to the full system that was loaded initially. Even though it should just have the protein, asking it for its LJ types returns 47 unique types.
print(pieces[0][0].LJ_types)
print(len(pieces[0][0].LJ_types))

{'N3': 1, 'H': 2, 'CX': 3, 'HP': 4, '2C': 3, 'HC': 5, 'C': 6, 'O': 7, 'N': 1, 'CT': 3, 'H1': 8, 'CO': 6, 'O2': 7, '3C': 3, 'OH': 9, 'HO': 10, 'C8': 3, 'N2': 1, 'CA': 6, 'HA': 11, 'C*': 6, 'CW': 6, 'H4': 12, 'NA': 1, 'CN': 6, 'CB': 6, 'CC': 6, 'NB': 1, 'CR': 6, 'H5': 13, 'S': 14, 'SH': 14, 'HS': 2, 'na': 1, 'nc': 1, 'nd': 1, 'cc': 6, 'cd': 6, 'c3': 3, 'ca': 6, 'ha': 11, 'hc': 5, 'h5': 13, 'Na+': 15, 'Cl-': 16, 'OW': 17, 'HW': 18}
47

I'm not all that familiar with ParmEd, but I think that what we need to do is to "truly" separate off pieces[0][0] into its own Structure (with no preconcieved notions of the ligand), and then combine the systems.

That's what split is SUPPOSED to do, as I understand it, @j-wags .
Do you have other ideas how to do this?

@nividic have you dealt with this?

I know this is old now, but this is how I did this exact thing before: https://github.com/slochower/smirnoff-host-guest/blob/master/01-convert-benchmarkset.ipynb I think some of the functions here could be useful: https://github.com/slochower/smirnoff-host-guest/blob/master/smirnovert/utils.py but I haven't cross-checked with @davidlmobley's notebook yet.

Might also be worthwhile to try remake_parm(): https://parmed.github.io/ParmEd/html/api/parmed/parmed.amber.html?highlight=remake_parm#parmed.amber.AmberParm.remake_parm if you are splitting and recombining topologies.

@slochower's code had the trick we needed. To combine them successfully, we can make a new Structure, and add the pieces we want to it a la carte. For example, like this:
complex_structure = parmed.Structure()
complex_structure += pieces[0][0]
complex_structure += ligand_structure

I've updated the notebook to produce the combined system, and run a brief minimization/simulation. So, there's still a lot of debug output, but this produces at least a system that doesn't explode immediately. It shouldn't be hard to carry the solvent through using the same method.
One thing I'd like another set of eyes on: I've also added paranoid checks to ensure that ParmEd is not incorrectly merging protein and ligand atom parameters when they have the same "atom type". The number of unique sigmas/epsilons DOES seem to be preserved, but we come up one "atom type" short after the merge. "H1" appears in both ligand and protein systems. I hope that's just cosmetic, and the number of unique params seems to indicate that everything is alright.

Let me take a quick look, @j-wags . Thanks for looking at this!

@j-wags -- this looks like this should be fine. It's just the atom NAMES, which are cosmetic, which collide. The number of atom types (sigmas and epsilons) is correct, indicating that indeed we're just seeing a cosmetic issue.
So, this looks good to go once we re-insert the documentation, etc. (most of it can be copied over from the other BRD4 example). Do you have a few minutes to do that? If not LMK and I may be able to squeeze it in tomorrow.
Also, we need to get the water back in too-- the goal of this one was to take the original system, pull out the ligand and re-parameterize it, and stick it back into the original system. LMK if you need me to do that. It should be just a matter of re-adding the water pieces too.

I'll take a shot at this tonight. My main goals will be to clean up and comment the code, and I'll draft the text fields as well. I find that polishing up wording and adding friendly links takes me unbounded amounts of time, so I'll leave the finalization to you.

Glad to help. Adding water back in should be in my notebook too.
Sent from my iPhone

On Dec 19, 2019, at 17:34, Jeff Wagner<EMAIL_ADDRESS>wrote:

I'll take a shot at this tonight. My main goals will be to clean up and comment the code, and I'll draft the text fields as well. I find that polishing up wording and adding friendly links takes me unbounded amounts of time, so I'll leave the finalization to you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Ok, I've polished up the documentation for the first half of the notebook, and I've figured out how to efficiently recombine the components to create the system.  Note that complex_structure += pieces[2][0] * pieces[2][1] doesn't work, since trying to use the * operator on whatever object is returned by structure.split()  yields the same error as we were getting initially (about a mismatched number of atom types).
The code is now all in place, and the resulting brief simulations look reasonable.  I want to get ChargeIncrementModel in reviewable shape before I head out, and I'm already pretty booked up tomorrow. @davidlmobley, could you take over from here? The remaining work is to document the second half of the notebook.

Yes, I'll document from here. Thanks, @j-wags !

@j-wags this is ready to go unless we want to also:
a) do something to enable testing on this notebook (or is it already/automatically enabled?)
b) Get the MyBinder stuff working as in (some of?) the other examples -- there's a link in the README.md for some of the other examples.
I'll go ahead and point Dan here, so that you can either merge now, or wait to get that info in before merging.
Once merged, LMK and I'll tweet about this. I imagine this is an example which will help a lot of people get started since this allows them to drop OpenFF ligands into existing workflows.

Oh, but maybe let's wait for tests. Something really strange happened in the last build.

Alright. Tests look good. Clear to merge.


Implementing Extended Code Suggestions Tool

PR Type:
Enhancement

PR Description:
This pull request introduces a new tool - "extended improve", which is an extension of the current "improve" tool. The new tool allows for no compression of diff files, generates multiple code suggestions for each group of changes, aggregates the code suggestions from different groups, and sorts the suggestions based on their importance. It also includes the ability to clip the least important suggestions.

PR Main Files Walkthrough:
pr_agent/tools/pr_extended_code_suggestions.py: This is a new file that implements the 'extended improve' tool. It includes methods for running the tool, preparing predictions, ranking suggestions, and pushing inline code suggestions.
pr_agent/algo/pr_processing.py: The 'get_pr_diff' function has been modified to return the tokens of the extended patches. A new function 'get_pr_multi_diffs' has been added to retrieve the diff files from a Git provider, sort them by main language, and generate patches for each file.
pr_agent/agent/pr_agent.py: The 'extended_improve' tool has been added to the list of available tools.
pr_agent/algo/ai_handler.py: The 'chat_completion' function has been modified to have a default temperature of 0.2.
pr_agent/algo/git_patch_processing.py: The 'convert_to_hunks_with_lines_numbers' function has been modified to add a newline before the filename. A new function 'get_pr_multi_diffs' has been added to retrieve the diff files from a Git provider, sort them by main language, and generate patches for each file.
pr_agent/config_loader.py: The 'pr_sort_code_suggestions_prompts.toml' file has been added to the list of settings files to load.
pr_agent/settings/pr_code_suggestions_prompts.toml: The prompts for the 'pr_code_suggestions' tool have been updated to be more clear and detailed.
pr_agent/settings/pr_sort_code_suggestions_prompts.toml: This is a new file that provides the prompts for the 'pr_sort_code_suggestions' tool.
pr_agent/settings/pr_reviewer_prompts.toml: The prompts for the 'pr_reviewer' tool have been updated to be more clear and detailed.
pr_agent/settings/configuration.toml: New configuration options have been added for the 'pr_extendeted_code_suggestions' tool.

/describe

Preparing review...

Preparing review...


LBRY About goes to https://

i think, IF i have LBRY installed,i probably know what is it...
thats Not what im looking for...,
im looking to know the build version number, like all other apps & browsers.
i dont want to close LBRY, open Synaptic or Muon, or App store, or Snap, or Terminal to know what version i have installed.
a waste of time.

I think the Help...About you're looking for is under Help in the top gear menu. We'll review those sidebar footer item.


Flutter-3.22.2 - Repeated launches of any application in the Android emulator freeze

Steps to reproduce

upgrade the Flutter to 3.22.2
create from scratch an any flutter app, for example "flutter create test_drive"

I try to do it with my old, flutter-3.13.x apps - they freeze too

I try to run my old flutter-3.13.x apps without the "https://docs.flutter.dev/release/breaking-changes/flutter-gradle-plugin-apply" updates - result is freeze
I try to run my old flutter-3.13.x apps with the "https://docs.flutter.dev/release/breaking-changes/flutter-gradle-plugin-apply" updates - result is freeze
I try to run a new app, created from scratch by command "flutter create test_drive" - result is freeze

open this project in any IDE  (Visual Studio Code or Android Studio)

I try to do it into Android Studio from 2022 year, with outdated Flutter & Dart plugins - result is freeze
I try to do it into Android Studio from 2022 year, with updated Flutter & Dart plugins - result is freeze
I try to do it into latest Android Studio-2<IP_ADDRESS>, with fresh Flutter & Dart plugins - result is freeze
I try to do it into latest Microsoft Visual Code, with fresh Flutter plugin - result is freeze

create any Virtual Mobile Device (I try API 29 and API 34)
build and run this app
First run will be OK, but if your project has the flutter_native_splash feature you will some slow motion switch between splash screen and main screen
Return the virtual mobile screen to Home page mode
Remove app from virtual mobile history cache (square button, find and remove the app screen)
Find app in your virtual mobile and Start it again
Application will freeze and you can't see the main screen of app.

I check it on real Andoid device:

I can't get this bug
But I see the slow motion switch between splash screen and main screen (my real developed app uses the flutter_native_splash feature

Expected results

Repeated launches of application in the Android emulator should run successfully,
No slow motion switch between splash screen mode and main screen

Actual results

Repeated launches of application in the Android emulator freeze,

if your app has a splash screen, the freeze will be after splash screen, on the Main page init phase
if your app hasn't a splash screen, the freeze will be on the Main page init phase

Slow motion switch between splash screen mode and main screen on first run in Android emulator
Slow motion switch between splash screen mode and main screen in any run on real Android device

Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[Paste your output here]

@progaman
I tried to replicate this using latest stable but was unable to. Can you provide a short video of the behavior ?

hi Darkshankawar,
short video is here: https://github.com/flutter/flutter/assets/22752489/fac43bfb-9f55-498d-89e6-8184f01e6569

Thanks for the detailed video @progaman
I see from it that you terminated the app and then trying to open it again shows a blank screen.
I tried the same with fresh flutter project using AS and pixel xl api 33 with which the app opens properly after terminating by showing the splash screen first and then the counter screen.
I tried above using mac and I see that you are on windows. Can you try the same scenario on different emulators and check if you still get same behavior ?

hi Darshankawar,
Yes, when I encountered this problem, I immediately created a new Android virtual mobile device... but happiness did not happen 8(  - this issue still reproduces on all new virtual devices.
I think the problem is on the Android emulator platform side. So, I'm going to try create a simple HelloWorld android app and  look how it will work.
I send message about result immediatelly

Hi again,
Below the results of my test with clear AndroidStudio, Java tests:

First of all, I created from scratch a simple android app from AndroidStudio start-pack catalog
1.2 And run it on same old virtual android device "Pixel 3 API 34" - start, work, terminate and open the app again in device - the Android app in all modes works correct
Then I created a new virtual android device "Pixel XL API 33" and run my android app here  - the Android app in all modes works correct
Then I created from scratch a new simple flutter app from AndroidStudio start-pack catalog
3.1 And run this flutter app on the same virtual device "Pixel XL API 33" - and I again have a problem the Flutter app at the Open after terminate phase. But now, the Flutter draw some parts of the main screen before freeze.

I attached a new movie here:
https://github.com/flutter/flutter/assets/22752489/bff5e49d-9ce9-4d83-9c0d-04df715dd56a

From Android triage: Assigning to @yaakovschectman to try to reproduce for now, and re-evaluate priority (P1 just for repro).

I have been able to observe this bug on an Android emulator running on Windows when running API 34. I also tried with API 27 and did not observe the bug. @darshankawar what platform(s) have you attempted to repro this bug on and not observed it?


fix custom mime type in out-display

This is a second attempt, i had to close the forst PR attempt and start over to make it cleaner :D.
Now it does not have any formatting problems, i hope.

hmm, still formatting issues ... :(


pushState works in ComponentWillReceiveProps. But doesn't work when I directly dispatch is as part of an action.

I want to using pushState to redirect user after he does something.
function someAction () {    return dispatch =>  {        dispatch(someOtherAction);  //this modifies the state.         dispatch(pushState('newroute');    } }
but the dispatch pushState doesn't seems to work. However, in ComponentWillReceiveProps (I do a pushState, it works.)
Any thoughts on why this is the case?

@xinghengwang what does your create store look like? One thing I could think of is that because you are using redux-thunk the order of the store enhancer with the middleware could cause the action not to get picked up. I'd be interested to know if you see the dispatched action in redux-logger when you use the action creator

I am using this template:
https://github.com/erikras/react-redux-universal-hot-example
I forked it a while ago (when it was still on redux router, even though latest version has updated to redux-react-router), but createStore is pretty much the same: https://github.com/erikras/react-redux-universal-hot-example/blob/master/src/redux/create.js

I think this is a duplicate of https://github.com/acdlite/redux-router/issues/191. Can you try some of the advice in https://github.com/acdlite/redux-router/issues/191#issuecomment-167249778


drone sign command doesn't exist

According to http://readme.drone.io/usage/secret-guide/, Drone does not expose secrets to your build unless the Yaml file is signed and verified. However the command to sign does not exist.
Using drone-cli 0.6.0 installed via Homebrew on OS X

drone sign was removed in version 0.6 of drone. You can see the release notes at http://docs.drone.io/release-0.6.0 and the updated 0.6 docs at http://docs.drone.io/


Admin Ghosts Chain Explosions

Description
Admin ghosts that have explosives in their bags of holding can have said explosives go off from bombs thrown by players
Reproduction
1- Be an admin Ghost
2- Run an event, have bag loaded with explosives
3- Random explosion from another source hits you
4- All the bombs in your bag have gone off
5- Cry, as now the station has a gaping hole where you were floating
Additional context
Discovered this on Delta-V while adminning for an event, had explosives that had been taken off a nukie shuttle we were using for the event. A sleeper agent threw a c4, I floated near it, and it set off the 6 C4 and 2 minibombs in my bag, spacing the area I was floating over

Hey, you posted this issue in our design docs repository. I transferred it to the correct one for the game itself.


VS Code cannot start without internet

VS Code Version: 1.55.1
OS Version: Windows 10

Steps to Reproduce:

When internet is on, VS Code detects an update.

Attempt to start VScode.

bleakley@LAPTOP-D2RUJG43:~$ code .
Updating VS Code Server to version 08a217c4d27a02a5bcde898fd7981bda5b49391b
Removing previous installation...
Installing VS Code Server for x64 (08a217c4d27a02a5bcde898fd7981bda5b49391b)
Downloading: 100%
Failed
--2021-04-10 10:29:11--  https://update.code.visualstudio.com/commit:08a217c4d27a02a5bcde898fd7981bda5b49391b/server-linux-x64/stable
Resolving update.code.visualstudio.com (update.code.visualstudio.com)... failed: Temporary failure in name resolution.
wget: unable to resolve host address ‘update.code.visualstudio.com’
ERROR: Failed to download https://update.code.visualstudio.com/commit:08a217c4d27a02a5bcde898fd7981bda5b49391b/server-linux-x64/stable to /home/bleakley/.vscode-server/bin/08a217c4d27a02a5bcde898fd7981bda5b49391b-1618072141.tar.gz

Try to start it without updating, realize you don't know what, if any, command line flag will launch it without updating.
Try code . --help
Realize you can't even view the view available options because you can't start it without updating.
Realize you can't google how to start it because the internet is disconnected.

This is 100% unambiguously a bug. I'm aware it's possible to disable this behavior within VS Code. The user needs to be able to disable this on the command line, and the user needs to be able to view the help on the command line whether or not the internet is available.
Does this issue occur when all extensions are disabled?: Yes/No
Yes

How did you install VS Code?

It was originally installed with the VSCodeUserSetup-x64-1.46.1.exe download from the website. I'm running it with WSL 2 on Windows 10.

Oh now I get it. Yes, it's correct: VS Code doesn't ship with VS Code Server, the latter needs to be downloaded from the internet. This needs to happen only the very first time you start VS Code after an update and connect to a WSL environment, in the case of WSL. Successive launches of the same VS Code version won't require being online.


ERROR: Failed to init storage factory

Steps to reproduce

git clone respository
edit values.yaml replicas=1
change templates stroageClass to local kuberneter default stroageClass
helm install

Expected behavior
all pod is running
Actual behavior
all pods are running but frontend
kelemetry-1689762474-collector-79f5c59df4-52q4z   1/1     Running            2 (16h ago)   16h
kelemetry-1689762474-consumer-b88789bb4-5kzbf     1/1     Running            0             16h
kelemetry-1689762474-etcd-0                       1/1     Running            0             10m
kelemetry-1689762474-frontend-755b8f47ff-rl4jl    0/2     CrashLoopBackOff   8 (8s ago)    2m14s
kelemetry-1689762474-informers-76fb5d4458-s5ftw   1/1     Running            0             16h
kelemetry-1689762474-storage-0                    1/1     Running            0             16h

error.log
{"level":"warn","ts":1689822124.0339894,"caller":"channelz/funcs.go:342","msg":"[core][Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {\n  \"Addr\": \"localhost:17271\",\n  \"ServerName\": \"localhost:17271\",\n  \"Attributes\": null,\n  \"BalancerAttributes\": null,\n  \"Type\": 0,\n  \"Metadata\": null\n}. Err: connection error: desc = \"transport: Error while dialing dial tcp [::1]:17271: connect: connection refused\"","system":"grpc","grpc_log":true}
{"level":"info","ts":1689822124.034001,"caller":"channelz/funcs.go:340","msg":"[core][Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE","system":"grpc","grpc_log":true}
{"level":"info","ts":1689822124.0340135,"caller":"grpclog/component.go:71","msg":"[core]pickfirstBalancer: UpdateSubConnState: 0xc000196540, {TRANSIENT_FAILURE connection error: desc = \"transport: Error while dialing dial tcp [::1]:17271: connect: connection refused\"}","system":"grpc","grpc_log":true}
{"level":"info","ts":1689822124.0340188,"caller":"channelz/funcs.go:340","msg":"[core][Channel #1] Channel Connectivity change to TRANSIENT_FAILURE","system":"grpc","grpc_log":true}
{"level":"info","ts":1689822126.1586947,"caller":"channelz/funcs.go:340","msg":"[core][Channel #1] Channel Connectivity change to SHUTDOWN","system":"grpc","grpc_log":true}
{"level":"info","ts":1689822126.1587367,"caller":"channelz/funcs.go:340","msg":"[core][Channel #1 SubChannel #2] Subchannel Connectivity change to SHUTDOWN","system":"grpc","grpc_log":true}
{"level":"info","ts":1689822126.1587467,"caller":"channelz/funcs.go:340","msg":"[core][Channel #1 SubChannel #2] Subchannel deleted","system":"grpc","grpc_log":true}
{"level":"info","ts":1689822126.1587508,"caller":"channelz/funcs.go:340","msg":"[core][Channel #1] Channel deleted","system":"grpc","grpc_log":true}
{"level":"fatal","ts":1689822126.1587627,"caller":"./main.go:107","msg":"Failed to init storage factory","error":"grpc-plugin builder failed to create a store: error connecting to remote storage: context deadline exceeded","stacktrace":"main.main.func1\n\t./main.go:107\ngithub.com/spf13/cobra.(*Command).execute\n\tgithub.com/spf13/cobra@v1.6.1/command.go:916\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tgithub.com/spf13/cobra@v1.6.1/command.go:1044\ngithub.com/spf13/cobra.(*Command).Execute\n\tgithub.com/spf13/cobra@v1.6.1/command.go:968\nmain.main\n\t./main.go:170\nruntime.main\n\truntime/proc.go:250"}

Kelemetry version
c42c0ff010c570a984663c8911568f3fa05e5ee7
Environment
kubernetes version:
Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.3", GitCommit:"9e644106593f3f4aa98f8a84b23db5fa378900bd", GitTreeState:"clean", BuildDate:"2023-03-15T13:40:17Z", GoVersion:"go1.19.7", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.0", GitCommit:"b46a3f887ca979b1a5d14fd39cb1af43e7e5d12d", GitTreeState:"clean", BuildDate:"2022-12-08T19:51:45Z", GoVersion:"go1.19.4", Compiler:"gc", Platform:"linux/amd64"}

cloud provider: local vm
Jaeger version: jaegertracing/jaeger-collector:1.42 use  deployment collector of Kelemetry
storage: custom nfs storage

Can you show the logs of the storage plugin container?
kubectl logs kelemetry-1689762474-frontend-755b8f47ff-rl4jl -c storage-plugin

By the way, if you already have an ElasticSearch cluster set up, you are encouraged to configure Kelemetry to use it instead of the single-instance Badger DB.

k -n kelemetry logs -f kelemetry-1689762474-frontend-755b8f47ff-rl4jl  -c storage-plugin
time="2023-07-20T05:00:57Z" level=error msg="unknown flag: --trace-server-enable"

and no ElasticSearch cluster set up my k8s cluster.

this pod is running when i move --trace-server-enable. Why is this incorrect parameter present in the official charts templates file?

What image version are you using for the frontend pod? The latest version has the --trace-server-enable flag.

kelemetry  images version: ghcr.io/kubewharf/kelemetry:0.1.0, and when i move --trace-server-enable flag, the jeager is not trace k8s deployment.

Try using 0.2.2 instead. 0.1.0 is an old version.

this work after instead image version, but have other issue
{"level":"info","ts":1689835956.4600453,"caller":"channelz/funcs.go:340","msg":"[core][Server #4 ListenSocket #7] ListenSocket created","system":"grpc","grpc_log":true}
{"level":"info","ts":1689835956.4600942,"caller":"app/server.go:282","msg":"Starting HTTP server","port":16686,"addr":":16686"}
{"level":"info","ts":1689835957.464222,"caller":"channelz/funcs.go:340","msg":"[core][Channel #5 SubChannel #6] Subchannel Connectivity change to IDLE","system":"grpc","grpc_log":true}
{"level":"info","ts":1689835957.4643304,"caller":"grpclog/component.go:71","msg":"[core]pickfirstBalancer: UpdateSubConnState: 0xc00059c078, {IDLE connection error: desc = \"transport: Error while dialing dial tcp :16685: connect: connection refused\"}","system":"grpc","grpc_log":true}
{"level":"info","ts":1689835957.4643457,"caller":"channelz/funcs.go:340","msg":"[core][Channel #5] Channel Connectivity change to IDLE","system":"grpc","grpc_log":true}

jeagerUi cannot get the tracing  deployment change.

Are you also using v0.2.2 of the helm chart?

Try using the latest version (v0.2.2).

how specific version(v0.2.2) When using helm install?

Set kelemetryImage.tag in values.yaml to 0.2.2 in the helm chart. Or just install oci://ghcr.io/kubewharf/kelemetry-chart:0.2.2 directly, which already indicates 0.2.2 image by default.

had specific kelemetryImage.tag was v0.2.2, and add --trace-server-enable .All pod are running ,but get error log
{"level":"info","ts":1689835956.4600453,"caller":"channelz/funcs.go:340","msg":"[core][Server #4 ListenSocket #7] ListenSocket created","system":"grpc","grpc_log":true}
{"level":"info","ts":1689835956.4600942,"caller":"app/server.go:282","msg":"Starting HTTP server","port":16686,"addr":":16686"}
{"level":"info","ts":1689835957.464222,"caller":"channelz/funcs.go:340","msg":"[core][Channel #5 SubChannel #6] Subchannel Connectivity change to IDLE","system":"grpc","grpc_log":true}
{"level":"info","ts":1689835957.4643304,"caller":"grpclog/component.go:71","msg":"[core]pickfirstBalancer: UpdateSubConnState: 0xc00059c078, {IDLE connection error: desc = \"transport: Error while dialing dial tcp :16685: connect: connection refused\"}","system":"grpc","grpc_log":true}
{"level":"info","ts":1689835957.4643457,"caller":"channelz/funcs.go:340","msg":"[core][Channel #5] Channel Connectivity change to IDLE","system":"grpc","grpc_log":true}

jeagerUi cannot get the tracing deployment change.

Can you check the frontend pod logs? Might be a duplciate of #127

frontend logs
{"level":"info","ts":1689835955.4305463,"caller":"grpclog/component.go:71","msg":"[core]Creating new client transport to \"{\\n  \\\"Addr\\\": \\\"localhost:17271\\\",\\n  \\\"ServerName\\\": \\\"localhost:17271\\\",\\n  \\\"Attributes\\\": null,\\n  \\\"BalancerAttributes\\\": null,\\n  \\\"Type\\\": 0,\\n  \\\"Metadata\\\": null\\n}\": connection error: desc = \"transport: Error while dialing dial tcp [::1]:17271: connect: connection refused\"","system":"grpc","grpc_log":true}
{"level":"warn","ts":1689835955.4305613,"caller":"channelz/funcs.go:342","msg":"[core][Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {\n  \"Addr\": \"localhost:17271\",\n  \"ServerName\": \"localhost:17271\",\n  \"Attributes\": null,\n  \"BalancerAttributes\": null,\n  \"Type\": 0,\n  \"Metadata\": null\n}. Err: connection error: desc = \"transport: Error while dialing dial tcp [::1]:17271: connect: connection refused\"","system":"grpc","grpc_log":true}

but storage-plugin is running not error

Can you check the frontend pod logs? Might be a duplciate of #127

not similar this


Don't display single flag icon at the bottom of the page if only one language is installed

https://www.boonex.com/forums/topic/Removing-bottom-flag-icon-in-UNA.htm