Pending changes from O.S. Systems for merging

We made a small image for a demo and made use of this nice tool. We ended making few changes here which seems to be good to be send upstream, so here it goes...

It has been a while since we sent this PR and we did not get feedback. Is it possible one of maintainers to review it and ask for the needed changes?


Many user snippets overridden by suggestions and others do not operate as expected after updating to VS Code Version 1.75.0

Type: Bug

In a global user snippets file (Python), create the following snippet that wraps selected text with a try & except statement:

    "Try & Except": {
        "prefix": "try:",
        "body": [
            "try:",
            "\t$TM_SELECTED_TEXT",
            "   ",
            "except Exception as E:",
            "\t$0",
            "",
        ],
        "description": "Try & except statement with wrap.\nHighlight code to try to use."
    },

With Pylance enabled, attempt to use the snippet by selecting a block of code and typing the specified prefix

Result: The code is replaced by the prefix and cursor is tabbed

Repeat step 2 with the Pylance disabled

Result: The code is wrapped with the try & except statement with the correct indentation, and the cursor is auto-positioned correctly within the scope of the except statement.

Extension version: 2023.2.10
VS Code version: Code 1.75.0 (e2816fe719a4026ffa1ee0189dc89bdfdbafb164, 2023-02-01T15:23:45.584Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 x 3400)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: unavailable_offvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
15.89GB (6.69GB free)

Process Argv
C:\Programming\EVERYTHING\EVERYTHING.code-workspace --crash-reporter-id 5bf58387-f4a6-4b59-b3d3-da5638839151

Screen Reader
no

VM
0%

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vscaat:30438848
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
pyindex848:30577860
nodejswelcome1cf:30587006
2e4cg342:30602488
pyind779cf:30657577
f6dab269:30613381
pythonsymbol12:30657548
a9j8j154:30646983

This is working fine for me in both 1.75.0 and 1.76.0-insider. Can you provide a video of what you're seeing?

same happened with me also..
adding a link with proper photos..
https://stackoverflow.com/questions/75344463/why-are-the-user-defined-snippets-not-working

@sahil-1012, I get this message when I follow that stackoverflow link:

This is working fine for me in both 1.75.0 and 1.76.0-insider. Can you provide a video of what you're seeing?
I'd also be curious to see your settings.json in case there's something about your Python/Pylance settings that is impacting this.

Thank you verily for responding. My apologies, but I rolled back to the previous version of VS Code and Pylance which provided a temporary solution because, to my chagrin, I rely much more heavily on snippets for my workflow now than I had realized. As far as possible settings issues, upon experiencing the aforementioned issue, I looked for similar issues and checked/verified all settings containing the word "snip" as well as all Pylance and relevant Python settings, but it's possible I missed something. I'm including my settings file, which is probably a bit bloated, so my apologies.
Here is my settings file which was renamed as a text file as GitHub doesn't support uploading JSON files here.

Thanks, I'm able to repro this now. Not sure why I wasn't before.
I think this is the same as https://github.com/microsoft/pylance-release/issues/3911. Can you check if what you're seeing matches that behavior?

#3911 seems the same save for the fact that my user snippets didn't show with even just one letter typed.

@GigglePocket, #3911 is fixed in the latest VS Code Insiders build. Can you see if this issue is also fixed for you?

Will do. I have to re-upgrade to the latest version of VS Code & Pylance and I will follow up and let you know afterward.

This issue has been fixed. All user snippets now appear in suggestions and insert correctly upon tabbing. Additionally, an issue I believe to be unrelated to this where TM_SELECTED_TEXT failed to insert the selected text into a rendered snippet appears to be fixed as well.
I'm closing this issue as it has been resolved. Thank you verily for your help and efforts.


Remove pythonPackages.flask_cache

Motivation for this change

See the first commit (d3d1b88) for the original motivation

The second commit moves the graphite_api expression (which was changed previously) into its own file.

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

@Ma27 Btw, are you actually using the graphite_api package?

long story short, I wanted to try out flask_cache, found flask_caching (and it's outdated and broken), so I decided to drop it from my package set and contribute it back to upstream nixpkgs.
graphite_api was just a "fallout" as it depended on flask_cache, that's all :)


Colored boxes are missing

Since the base repo has change the nice boxes are missing.

closed

But they are not the same as before, aren't they?
If I remember correctly they were partially in equations. Currently two equations are red and two are blue.


Immediate mode GWSS calls are not MP/MT safe.

The following API calls are not MP/MT safe in cases when Find and Immediate mode calls are intermixed.
miopenConvolutionForwardGetSolutionWorkspaceSize()
miopenConvolutionBackwardDataGetSolutionWorkspaceSize()
miopenConvolutionBackwardWeightsGetSolutionWorkspaceSize()

Use case
process 1 --> Immediate GWSS -------x------> GetSolutions
                                    ^
                     find-db update |
                                    |
process 2 ----------------------> Find ---> ...

GetSolution may return solution that wants bigger WS than returned by Immediate mode GWSS.

These calls are optional. The obvious proposal is to remove them.

@pfultz2 @daniellowell @DrizztDoUrden FYI

These calls are optional. The obvious proposal is to remove them.

I am not sure I follow, why is removal the obvious solution ?
A simpler solution is to not store the workspace size in FDB ( I think we went over this earlier). Since the workspace size can be calculated by the solver without the perf params ( ie. a PDB access) GWSS calls should avoid the fdb access and just compute the workspace size from the problem and tensor descriptors.

GWSS must know solver id to do this calculation.

@atamazov  Which should be known in immediate mode, even if its not, it can be enumerated from the any-solver containers.

You are right. And I was a bit wrong in the description (partially fixed). I need to think about this...

[Informative] GetForwardSolutionWorkspaceSize() works independently of find-db. Actually it MUST work this way due to some find-db limitations imposed by Find API 1.0. So the use case scenario like this would never fail:
Use case
process 1 --> GetSolutions -------x------> GetSolutionWorkspaceSize(solution_id)
                                  ^
                   find-db update |
                                  |
process 2 --------------------> Find ---> ...

As GetSolutionWorkspaceSize does not read WS size from find-db but always computes it, it returns valid value workspace size regardless of any find-db updates that may happen in parallel.

@JehandadKhan I will update issue title & description, and hide or delete some irrelevant comments soon.


a11y traversal order top left to bottom right not always giving great results

Traversal order in this screen shot is currently:

Back button
Shopping cart button
Three dots button
"SHRINE" title

I would expect SHRINE to come after the back button. However, the shipping cart button's bounding box has its top higher than the SHRINE title and is therefore traversed first in the current top left to bottom right approach.

As an idea to make this better: we could see if we can find out how Android defines traversal order for native apps.

I think this is what Android uses.  It looks like they basically do left to right, top to bottom, but then allow the developer to move object hierarchies around by saying "this tree goes before this one" or "this tree goes after this one" in the traversal order.  The prioritize the "goes before" setting over the "goes after" setting (so "goes after" doesn't happen if "goes before" exists).

For the AppBar specifically, let's just use our ordering API to set the order correctly.

Similar bug for tab bar: https://github.com/flutter/flutter/issues/14375


Add Windows-specific intructions and badge for scoop

ctop is now in the scoop main bucket, so I added some windows-specific stuff to the README

merged; thanks @astelmachonak-nydig !


Added a template detective for future expansion

This adds a template detective and a test for the template.  The detective (BlankDetective) actually runs but takes no arguments and returns no results.
Some of the idosyncrosies of the detectives are documented in the file implementation.md.  The test runs under rake.  Lint has one complaint.
app/lib/blank_detective.rb:8:1: W: Lint/UnneededDisable: Unnecessary disabling of Metrics/ClassLength.
rubocop:disable Metrics/ClassLength
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Current coverage is 98.28% (diff: 100%)

Merging #488 into master will increase coverage by <.01%

@@             master       #488   diff @@
==========================================
  Files            37         38     +1
  Lines           926        931     +5
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            910        915     +5
  Misses           16         16
  Partials          0          0

Powered by Codecov. Last update 488528b...9605735


I wish the sort would indicate which sort is being used

Testing #6329

If I choose one of these, I expect there to be some indication as to which one is currently the primary sorting behavior.

Agreed, unfortunately the concept of a "checked" menu item is not currently supported through our extension API.

Perhaps this can be the catalyst for action on PR #214102 by @eamodio 🙏

Nice, thanks for connecting the dots @gjsjohnmurray!


my css emmet abrivation can't runing

Type: Bug
i try type value in css but emmet abrivation cant run,but in my html emmet abrivation still run
VS Code version: Code 1.85.1 (0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2, 2023-12-13T09:49:37.021Z)
OS version: Windows_NT x64 10.0.22621
Modes:

System Info

Item
Value

CPUs
AMD Ryzen 3 3250U with Radeon Graphics          (4 x 2600)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
5.94GB (0.97GB free)

Process Argv
--crash-reporter-id 1d4b08a1-8015-4734-ac24-460f9d29be18

Screen Reader
no

VM
0%

Extensions (18)

Extension
Author (truncated)
Version

codesnap
adp
1.3.4

vscode-tailwindcss
bra
0.10.3

path-intellisense
chr
2.8.5

postcss
css
1.0.9

dadroit-json-generator
Dad
1.1.7

vscode-html-css
ecm
1.13.1

prettier-vscode
esb
10.1.0

auto-close-tag
for
0.5.15

auto-complete-tag
for
0.1.0

auto-rename-tag
for
0.1.10

python
ms-
2023.22.1

vscode-pylance
ms-
2023.12.1

live-server
ms-
0.4.13

vscode-css-peek
pra
4.4.1

LiveServer
rit
5.7.9

open-in-browser
tec
2.0.0

errorlens
use
3.16.0

material-theme
zhu
3.16.2

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
py29gd2263:30899288
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
3biah626:30602489
f6dab269:30613381
2i9eh265:30646982
showlangstatbar:30737416
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
welcomedialog:30910333
pythonnosmt12:30797651
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
dsvsc013:30795093
dsvsc014:30804076
dsvsc015:30845448
pythontestfixt:30902429
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
accentitlementsc:30887149
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
aa_t_chat:30882232
cp7184t:30925682

type @disabled in your vs code extension search bar and then enable the extension if there is any disabled extension is there...

I'm also wondering in which file type you're trying to expand the abbreviation?
\gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

You did the step i mentioned?
On Wed, Dec 20, 2023, 10:05 PM Raymond Zhao @.***>
wrote:

I'm also wondering in which file type you're trying to expand the
abbreviation?
\gifPlease
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/201256#issuecomment-1864790061,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6CXWPM65VVY4IUN5WBVORTYKMHT3AVCNFSM6AAAAABA4EAUUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRUG44TAMBWGE
.
You are receiving this because you commented.Message ID:
@.***>

I was responding to @Fatmu-Saputra

Okk
On Wed, Dec 20, 2023, 10:10 PM Raymond Zhao @.***>
wrote:

I was responding to @Fatmu-Saputra https://github.com/Fatmu-Saputra
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/201256#issuecomment-1864797630,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6CXWPPQI2UAZKWQU6P4TOTYKMIIHAVCNFSM6AAAAABA4EAUUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRUG44TONRTGA
.
You are receiving this because you commented.Message ID:
@.***>

Hey @rzhao271, this issue might need further attention.
@Fatmu-Saputra, you can help us out by closing this issue if the problem no longer exists, or adding more information.

Closing for now. Feel free to comment if the issue is still occurring in the latest version of VS Code.


I need to scroll custom view to position so my element is visible when dialog is shown

What module does this apply to?
Core
Description what you'd like to happen:
I would like to be able to access scroll view to scroll to some position when dialog is shown
Describe alternatives you've considered:
fork library or just hack around to get the view from hierarchy

This is an implementation detail to your app, not really this library.
You'll want to get a reference to your ScrollView and manually scroll it as needed.

Well for sure and i did it already but you made it quite difficult and ugly to access that scrollview.


⚠ Bofrost.at has degraded performance

In 00c1017, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1820 ms

Resolved: Bofrost.at performance has improved in 071f32c after 6 minutes.


add name as optional param for loaded assets.

Hello,
I would like to express my gratitude for creating and continuously updating this outstanding package.
As my Flutter project grows in size and requires a large number of images to load, it would be convenient to access my assets by their names. For example:
ScalableImage.fromSIAsset(rootBundle, 'assets/logo.si', 'logo');
ScalableImage.fromSIAsset(rootBundle, 'assets/icon.si', 'icon');

By doing so, I can easily add them to a list and iterate through them by name.
Thank you.

I don't understand...  Why don't you just put them on a map that you maintain in your app, like this?
final myAssets = {
    'logo' : ScalableImage.fromSIAsset(rootBundle, 'assets/logo.si', 'logo'),
    'whateverNameIWant' : ScalableImage.fromSIAsset(rootBundle, 'assets/icon.si', 'icon'),
}```

I don't understand...  Why don't you just put them on a map that you maintain in your app, like this?
final myAssets = {
    'logo' : ScalableImage.fromSIAsset(rootBundle, 'assets/logo.si', 'logo'),
    'whateverNameIWant' : ScalableImage.fromSIAsset(rootBundle, 'assets/icon.si', 'icon'),
}```

Yes, you are absolutely correct.
Thank you.


update quickly

Hey...
I have a big problem with this plugin.
Can you repair it quickly?
Can you repair it quickly?
Can you repair it quickly?
Can you repair it quickly?
Can you repair it quickly?
Can you repair it quickly?
Can you repair it quickly?

please open an issue with details of your problem/feature and we can discuss there.


Fix/readme issue 209

What does this PR do?
1⃣  Typo and grammar fix
2⃣  Added License section at the bottom
What packages have been affected by this PR?
Types of changes
What types of changes does your code introduce to this project?
Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)

[ ] New feature (non-breaking change which adds functionality)

[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Package version increase in cli package?
Checklist before merging
Put an x in the boxes that apply

[x] These changes have been thoroughly tested.

[ ] Changes need to be immediately published on npm.

Hi @impratik7 would be able to help merge the changes as I don't have permission.

Last run CI run auto failed Deploy did not succeed: Deploy directory 'apps/docs/out' does not exist

Deployment Link

Previous

Latest

so removed some space and pushing again for approval

previous run

PR cleanup.


Landscape fullscreen rotation

Currently when you go fullscreen on a landscape video, the direction is locked. Meaning you can't change the video direction by rotating your phone 180 degree.
I think regular users do not expect that to be the case.
Youtube, Netflix and Chrome's HTML5 fullscreen video all do this by default. Regardless of the user's system "auto-rotate" settings:

On any of the above app, enter fullscreen.
Rotate your phone 180 degree. The video direction changes.
Rotate your phone back 180 degree. The video direction changes.

I propose:

Use sensor-based rotation by default for landscape fullscreen mode
Still allow developers to lock-in in one direction (Like current behavior)

I'm only talking about Android. I don't know how it works on iOS, so inputs are welcome.

in iOS, landscape video do not goes to full screen..

Guys this is already fixed and merged. Please update your chewie version. On v. 0.10.0 (we're now on 0.10.4) exactly this was published. I'll demonstrate it you

On default chewie calculates regarding the video aspect ratio, wether to go on landscape or portrait (landscape videos go to landscape and portrait videos to portrait -> exact same behavior like Youtube)
You can control all kind of DeviceOrientation while you're in fullscreen or not. Use these:

deviceOrientationsAfterFullScreen: [
        DeviceOrientation.portraitUp,
        DeviceOrientation.landscapeRight,
        DeviceOrientation.landscapeLeft,
],
deviceOrientationsOnEnterFullScreen: [
        DeviceOrientation.portraitUp,
],

Auto-Rotate: Example behavior if parameters above are not set:

Custom set DeviceOrientations (fixed to Portrait only):

Yes, that's how it should be. I guess on iOS it just works.
But on Android it's not. I'll attach GIF in a second.

For further informations please see this PR: https://github.com/brianegan/chewie/pull/289
I'll update the Readme file and maybe also add an API-Documentation explicitly (because not all parameters are likely known).
I'll close this issue because it's already fixed and developers can decide how their player is behaving (see PR and examples above). Download and test it with the latest chewie. Don't hesitate to reopen if you think It's not

Yes, that's how it should be. I guess on iOS it just works.
But on Android it's not. I'll attach GIF in a second.

It'n not an android think. Wait, I'll demonstrate again...

Ok, I can't upload videos above 100Mb, but here my explanation:
On Android and iOS you got the ability to lock or unlock device rotations. But as discussed here: https://github.com/brianegan/chewie/pull/289 we already decided to track the video aspect ratio and not the system settings for rotation. BUT on every device you can change this behavior yourself (without chewie!) by setting:
    this.systemOverlaysAfterFullScreen = SystemUiOverlay.values,
    this.deviceOrientationsAfterFullScreen = DeviceOrientation.values,

And that's why we gave developers these parameters to control this behavior yourself :)

On master branch, latest version, with default settings:
https://i.imgur.com/pFkwbSY.mp4
Youtube comparison:
https://i.imgur.com/vbax1Ct.mp4


FBP-87. Allow to change subrocess type

Fixes #87

Codecov Report

Merging #95 into master will decrease coverage by 0.19%.
The diff coverage is 27.58%.

@@             Coverage Diff              @@
##             master      #95      +/-   ##
============================================
- Coverage     56.71%   56.51%   -0.20%
- Complexity      568      571       +3
============================================
  Files            78       78
  Lines          2941     2962      +21
  Branches        553      558       +5
============================================
+ Hits           1668     1674       +6
- Misses         1054     1067      +13
- Partials        219      221       +2

Flag
Coverage Δ
Complexity Δ

#unittests
56.51% <27.58%> (-0.20%)
571.00 <1.00> (+3.00)
:arrow_down:

Impacted Files
Coverage Δ
Complexity Δ

...ij/plugin/flowable/parser/FlowableObjectFactory.kt
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...tellij/plugin/flowable/parser/nodes/FlowableXml.kt
93.79% <ø> (ø)
0.00 <0.00> (ø)

...plugin/flowable/parser/nodes/process/SubProcess.kt
85.71% <0.00%> (ø)
5.00 <0.00> (ø)

...lugin/flowable/parser/nodes/process/Transaction.kt
85.71% <0.00%> (ø)
4.00 <0.00> (ø)

.../valb3r/bpmn/intellij/plugin/state/CurrentState.kt
67.21% <23.52%> (-7.79%)
7.00 <0.00> (ø)

.../intellij/plugin/flowable/parser/FlowableParser.kt
65.92% <50.00%> (+0.12%)
50.00 <1.00> (+3.00)

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 94475d6...9802122. Read the comment docs.


Get a working build for the etcd operator

Summary
Update dependencies and upgrade to Go 1.17

Hi, thanks for putting this branch up. I'm trying to build some "app" etcd clusters, not for Kubernetes itself, but for hosting a custom internal service that uses etcd. This work has been very helpful to get me kicking the tires on etcd-in-kube.

I have code for an "out of cluster" config -- it lets me run the operator from my computer as a regular process, respecting my ~/.kube/config. It has made development very straight-forward. Should I open a PR against this branch?

I have code for an "out of cluster" config -- it lets me run the operator from my computer as a regular process, respecting my ~/.kube/config. It has made development very straight-forward. Should I open a PR against this branch?

@xrl Feel free, thanks!

Turns out the architecture is not compatible with running in local mode, the operator wants to use an etcd client against the replicas. I can't do that easily from an out of cluster process. So I'm just going to forget about it.

I am running this in a rancher cluster with some security constraints in place, I had to add this to the deployment.yaml:
      securityContext:
        runAsUser: 1000
        runAsGroup: 1000

might be good to make this a mountable object in the helm config, something like:
      securityContext:
        {{- toYaml .Values.securityContext | nindent 12 }}

what do you think?

@xrl Thank you for the catch.
Fixed the latest issue, the latest symlink is not even required it seems.
Also added the securityContext option under operator.securityContext
I have been keeping this PR open for a while in case issues crop up, but I am considering merging it soon

FYI, 3.5.2 is no longer considered "production ready"

https://github.com/ahrtr/etcd-issues/tree/master/issues/13766
https://groups.google.com/g/etcd-dev/c/sad9tgmKU7Y/m/vhArFVevBgAJ

Thanks for the heads up

I have hit a problem with the TLS example, I ran the example gen-cert.sh and then uploaded the certs/keys as kube secrets, the example tls cluster was marked as failed because:
time="2022-04-18T15:46:59Z" level=error msg="cluster failed to setup: stat /tmp: no such file or directory" cluster-name=example cluster-namespace=kv pkg=cluster
time="2022-04-18T15:46:59Z" level=warning msg="fail to handle event: ignore failed cluster (example). Please delete its CR" pkg=controller

I recommend changing pkg/apis/etcd/v1beta3/cluster.go to set DefaultEtcdVersion = "3.2.13" to DefaultEtcdVersion = "3.5.3". 3.5.3 is out now, by the way.

Awesome, thanks for the heads up!
Have you had any luck/progress with the TLS issues?

I think I will wait for https://github.com/etcd-io/etcd/issues/13948 to be resolved, and skip to 3.5.4 directly.

I did get TLS working! Now the next problem is how to automate the management the CA and generation the peer/server/client certs, but that's out of scope for this case. Here's the etcdcluster and the script for creating an appropriate set of secrets with all the files required:
kubectl create secret generic etcd-peer-tls --from-file=peer.crt --from-file=peer.key --from-file=peer-ca.crt
kubectl create secret generic etcd-client-tls --from-file=etcd-client.crt --from-file=etcd-client.key --from-file=etcd-client-ca.crt
kubectl create secret generic etcd-server-tls --from-file=server.crt --from-file=server.key --from-file=server-ca.crt

The fact that /tmp is implicitly required is intriguing to say the least. I wonder if one can get away with just making /tmp an emptyDir: {} volume on the operator deployment.

I went ahead and tried it, seems to be working OK. Would you mind trying it out?

Yeah, that does work but I'm not sure it's the deployment's responsibility to fix a flaw in the base image. I think the Dockerfile could be modified to include a tmp file but it would require ADD tmp.tar /tmp or similar with a magic tmp folder, we have to rely on the untar routine preserving permissions from the archive.

But I agree, it is curious the code was error about a tmp folder missing. Reading over the code it looks like the TLS config object is built from the secret and kept entirely in memory. I should break my cluster and get that exact error, sorry for the wild goose chase!

Yes, indeed. Perhaps an alpine image image could be a good middle ground. This would also give the operator image a basic sh and some busybox utils for simple debugging.


Fixed the virtual columns to be able to use in the API with filter[]

Primary use case is to be able to use filter[]=archived=true in the API, which was not possible before due to the ? in the virtual column name.
Also added the active attribute/virtual column
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1593890

@miq-bot add_label gaprindashvili/yes

@agrare Can you review/merge this?
We will need this change for gaprindashvili since we cannot directly query the deleted_on attribute in gaprindashvili

hey @AparnaKarve sorry I missed this because it wasn't assigned to me

@agrare Thank you!

@miq-bot add_label blocker

Gaprindashvili backport details:
$ git log -1
commit 518a0ae326e8d78c1a1c61e1ff037a0ab961975b
Author: Adam Grare<EMAIL_ADDRESS>Date:   Wed Jun 20 08:56:40 2018 +0200

    Merge pull request #17553 from AparnaKarve/fix_archived_api_attribute

    Fixed the virtual columns to be able to use in the API with `filter[]`
    (cherry picked from commit 58af1d2d7be4b6974accb8a47031c7aef3fc3591)

    https://bugzilla.redhat.com/show_bug.cgi?id=1594023


Update README.md

@hrsh7th I have already update the readme. I don't know if it is correct or not, but i tried my best. Sorry if it is wrong

This is general language server. So Icdon't want to contain neovim specific information. Sorry.

np


Incompatible to new UI of PyCharm 2023.1

This plugin does not seem to be compatible anymore with the new UI of PyCharm 2023.1. The icon of the day-and-night-plugin does not show up and also the automatic switch between the day and night theme does not work.

Hi @danschef! Thanks for your feedback and sorry for long delay: are you still experiencing issues?

Hi @iBavtovich, I was also concerned by the problem with PyCharm 2023.1, but I tested again with PyCharm 2023.2 and it works like a charm.
Thanks

Yes, I also can confirm that everything works well again with PyCharm 2024.2.1. Thanks!


Refactor riskcard & states; Chapter1 (EXPOSUREAPP-4049, EXPOSUREAPP-3834)

Removed RiskLevelConstants which we not useful anymore and just unnecessary complicated
Simplified RiskLevel to RiskState which just has 3 states now INCREASED_RISK, LOW_RISK, FAILED
Simplified state behavior of the risk cards on the homescreen.

Disabled tracing overrides all other cards, as it's a current state we want the user to fix
Otherwise if the last calculation failed (for any reason), we show the "tracing failed" card
If the last calculation did not fail we display either a high or low risk card

TODO

[x] No data yet, fresh install, airplane mode, manually press "restart", card seems to be just empty (light mode)
[x] No data yet, fresh install, airplane mode, manually press "restart", card seems to be just empty, now enable WIFI, card is empty then green card appears (light mode)
[x] Tracing disabled, light mode, divider is missing or invisible
[x] Missing "contacts" when displaying low risk card
[x] Negative days when time traveling backwards
[x] Remove "minimum tracing time active" restrictions which should be removed according to EXPOSUREAPP-3051 (moved to extra PR #1762)

Testing

Make sure all 4 cards look correct (compare with figma, though it's not 100% current)

Red card (high rish)
Green card (low risk)
Tracing stopped
Tracing failed

Check all designs in dark mode too

Coding LGTM, just one question, we did you choose such a dramatic title with: ... Chapter1? :D

The implementation is still not where it should be. It's still one multipurpose card doing everything, and I want to have separate cards and layouts, the home screen should be using a list with dynamic elements. Time did not allow me yet to do this, so Chapter 2: RiskCard states strike back! :tm: :wink:.

Is this a typo?
Begegnungen an 1 Tag mit erhöhtem Risiko
I would suggest Begegnungen an einem Tag mit erhöhtem Risiko <- also this sounds strange

I now have a flickering when navigating from home to risk details as the download tries to start.
As it's converted to a gif you only see the loading indicator as I navigate from home to details, but I see it one device every time.

I deactivated wifi during downloading got in the correct state, also disabled tracing and this was visible. Then I enabled tracing and wifi and the download started. as it was showing the download it turned from the failure to green, but still was in the loading state and displaying that it's downloading and the second state of the loading state for the calculation was visible but seemed to be executes.

@harambasicluka

Is this a typo?
Begegnungen an 1 Tag mit erhöhtem Risiko
I would suggest Begegnungen an einem Tag mit erhöhtem Risiko <- also this sounds strange
image

I would propose:
'An 1 Tag Begegnungen mit erhöhtem Risiko'
Or
'An einem Tag Begegnungen mit erhöhtem Risiko'
Or
'Sie hatten an einem Tag Begegnungen mit erhöhtem Risiko'
OT: What is the beautiful 'Corona-C' inside the snackbar in the screenshot? ForegroundService? Looks nice!

@harambasicluka

Is this a typo?
Begegnungen an 1 Tag mit erhöhtem Risiko
I would suggest Begegnungen an einem Tag mit erhöhtem Risiko <- also this sounds strange
image

I would propose:
'An 1 Tag Begegnungen mit erhöhtem Risiko'
Or
'An einem Tag Begegnungen mit erhöhtem Risiko'
Or
'Sie hatten an einem Tag Begegnungen mit erhöhtem Risiko'

Thank's for your proposal, we currently discussing it with our User Assistance colleagues :) But I think we'll stick to the structure, even if I would prefer your idea :)

OT: What is the beautiful 'Corona-C' inside the ~snack~statusbar in the screenshot? ForegroundService? Looks nice!

It's one of our notifications, so that's one of my test devices not sure if I got an reminder to update the more more frequently or my risk changed from low to high :) Both is already in production ;)

@harambasicluka

we currently discussing it with our User Assistance colleagues :) But I think we'll stick to the structure

Let's see, I found UA being quite exact wrt language, maybe they'll also see the need for a change :)

OT: What is the beautiful 'Corona-C' inside the ~snack~statusbar in the screenshot? ForegroundService? Looks nice!

It's one of our notifications, so that's one of my test devices not sure if I got an reminder to update the more more frequently or my risk changed from low to high :) Both is already in production ;)

Ha, never saw a notification yet, that's why I d didn't get it immediately ;)


Move benchmark configuration to database

Currently the benchmark is here:
https://github.com/neulab/explainaboard_web/tree/main/backend/src/impl/benchmark_configs
But it'd be nice to have it in the DB so it's easier to play with benchmark configurations without re-deploying the server.

I try to revisit this task (cc @OscarWang114 )
So far, benchmark configs are stored as JSON files that will be loaded through this function
To DBlize this process, we may have the following workflow:

Create a DB for benchmark configs based on their current schemas
Write an API that can post benchmark config file, validate its schema, and store it in DB
Write a very simple UI interface here for users to upload (e.g., create button) their benchmark config files

Hi, @neubig do you have any comments about the above workflow?

@pfliu-nlp Thanks for detailing the workflow! I think it looks great, and I'm planning to submit 2 PRs: PR1 will contain (1) and (2), and PR2 will contain (3). Basically the first focuses on the DB + backend, and the second focuses on the frontend.


Unable To Create Project

I am unable to create project using Expo XDE on my Mac.
The download timeout for creating a new project is too fast (60 seconds). I think you should change it to at least 600 seconds. My internet is fast enough (more than 500 KB/s download), a lot of people around the world will have internet that is much slower than mine.
When the download is more than 50% and it timeout, it retries from beginning again, so I will never be able to finish the download.

cc @fson / @charlesvinette

Hi @mssio! Thanks for the feedback, we will have a look and get back to
you. Have a good sunday!
On Sun, Nov 19, 2017 at 3:13 PM Brent Vatne<EMAIL_ADDRESS>wrote:

cc @fson https://github.com/fson / @charlesvinette
https://github.com/charlesvinette
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/expo/xde/issues/153#issuecomment-345545733, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AG3A94FfHvezDuxTZSqxwWayomuwcBBZks5s4IvTgaJpZM4Qjco4
.

Originally reported by Lokesh Agrawal as part of this stack overflow question https://stackoverflow.com/questions/47377240/expo-xde-timeout-of-60000-ms-exceeded

I also face the same issue

Facing the same issue as well while trying to create a new project. It repeatedly says, 'timeout of 60000ms exceeded'.

I hacked my way around this because it was extremely frustrating:

The URL for the tab project data is at https://s3.amazonaws.com/exp-starter-apps/tabs-23.0.0.tar.gz (you can figure this out by using the console inside the electron app that is xde)
Hit that URL in your web browser to download the file
Edit /etc/hosts to point s3.amazonaws.com to localhost
Run a web server on local host that serves that file when the url /exp-starter-apps/tabs-23.0.0.tar.gz is requested

Note that the request is being made over HTTPS so your local server will need to have a cert from a CA that identifies your server as being s3.amazonaws.com, but that is easy enough via the mac keychain to create a new CA and issue your own self-signed certs.

Any fix for this?

I've published an update to XDE that increases the timeout. If you continue to see the problem after upgrading to XDE v2.22.1, please let us know.


How to delete string "categories" and "tags" shown in the page,

Expected behavior

Actual behavior

Steps to reproduce the behavior
NexT Information
NexT Version:

[ ] Master
[x] Latest Release
[ ] Old version -

NexT Scheme:

[ ] All schemes
[ ] Muse
[x] Mist
[ ] Pisces

Other Information
I want to delete the string “categories” and "tags" to make the page look better, how to achieve it.. Thank you for your help!

@HZzzzB edit files in languages dir and what u want.

@ivan-nginx  Problem solved, Thank you!
I'm a beginner...So...I can' t recognize where problem should be.


Add  password support for import command

#41

Pull Request Test Coverage Report for Build 163

11 of 15 (73.33%) changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 82.035%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/address/logic/commands/ImportCommand.java
4
6
66.67%

src/main/java/seedu/address/logic/parser/ImportCommandParser.java
3
5
60.0%

Totals

Change from base Build 162:
-0.1%

Covered Lines:
1790

Relevant Lines:
2182

💛  - Coveralls


Indeterminate checkbox and ability to hide some checkboxes

To hide a checkbox for a node need to add the hidenCheckbox: true property.


Add transformer for optional callback properties

We currently transform closures into callbacks here: https://github.com/yewstack/yew/blob/master/src/virtual_dom/vcomp.rs#L143 but we should probably do the same for option wrapped closures so that callback properties can be optional

I created a PR :)

Fixed by https://github.com/yewstack/yew/pull/612


Allow wildcards for tracepoint categories

It is now possible to run e.g. this:
bpftrace -e 'tracepoint:kvm*:* { @[probe] = count(); }'

Resolves #1212.
Checklist

[x] Language changes are updated in docs/reference_guide.md
[x] User-visible and non-trivial changes updated in CHANGELOG.md

Embedded build failed on a uprobe test (cannot open mount ns), which shouldn't be affected by this PR. Not sure why the error occurred, it passed on my fork's branch build.
Also there are clang-format fails in a new test that I copied from an existing one (which contains the same format errors, too).

Embedded build failed on a uprobe test (cannot open mount ns), which shouldn't be affected by this PR. Not sure why the error occurred, it passed on my fork's branch build.

Some tests are still somewhat flaky and fail sporadically,  rerunning it usually  fixes it

Also there are clang-format fails in a new test that I copied from an existing one (which contains the same format errors, too).

We try to incrementally fix  the formatting errors. So if you touch code you format it. This way we can keep git blame useful.

I kicked off another round of embedded tests. Let's see if it passes this time.

We try to incrementally fix the formatting errors. So if you touch code you format it. This way we can keep git blame useful.

+1

I kicked off another round of embedded tests. Let's see if it passes this time.

Thanks, they all passed now.

We try to incrementally fix the formatting errors. So if you touch code you format it. This way we can keep git blame useful.

Sounds good, ok, fixed. I'll keep this in mind.


Test any server given its url

Hi Kuba,
I would like to use chaplain for testing an application that is written with Scala Play Framework - not an express js app. Is it a lot of effort to support this? I can help with coding if it's not in your priorities.
Thx,
Avgoustinos

Ideally I would like to be able to specify the app url through config & use relative urls inside the tests as it's done now.
config({app: 'http://localhost:9000'});

This is in fact pretty easy, and one of the things I intended to add pretty soon - so I can bump it up a little bit on the priority list. Expect it pretty soon on master, and then it'll go to the next npm release.
It'll probably look something like this:
config({
  server: 'http://localhost:9000'
});

In the current version, there are two different properties to give chaplain an HTTP server: app for testing against an app instance, and server for when you have an http.Server instance. I'm thinking of merging them into one server property to avoid forcing people to remember a lot of names - so this would fit right in as the third option for what that property can be.

Ok great! Thx. server property will be good.

The relevant commit has landed in master: https://github.com/krajzeg/chaplain/commit/c758e448c10b768ddbee037eb6a7d2ab5ec18160. You can just use {server: 'http://localhost:12345/'}, or any other URL prefix you want.
If you like, you can also use the newly added before() and after() to start/stop your test server with something like command-promise:
  before(function() { return Command('./server start'); });
  after(function() { return Command('./server stop'); });

Both accept a function that should return a promise to wait on. This is available on master, I still have to document all changes before releasing the next version on npm.

This functionality is now released as part of 0.3.2.

That was quick! Thx! Will give it a try this week. aK

Let me know if you run into any more issues - still very actively looking for areas to improve :)


FHIR Server replaces id with a generated one in the request body

Describe the bug
It's impossible to create a resource with a specific id. The server still generates an id and replaces the provided one with it.
Environment
Arch Linux & Docker & FHIR Server 5.1.0
To Reproduce
Create a resource (POST request) with the "id" field value specified in the body.
Expected behavior
The server should allow creating resources with an id provided by the client.

This is working as designed.  The only way to create a resource with a user-specified id is to use HTTP PUT.
From https://www.hl7.org/fhir/http.html#create

The resource does not need to have an id element (this is one of the few cases where a resource exists without an id element). If an id is provided, the server SHALL ignore it.

Hi @lmsurpre, thanks for the answer. I was a bit confused with a different fhir server implementation, now we're transferring to LinuxForHealth FHIR Server and in a few cases our old server doesn't follow the specification as it turned out.


FAQ section

We have to start a dedicated FAQ section which lists down common Gotchas.
(Like the one we have about the visualization affecting the observations).
@emilio-cartoni : Can you start a FAQ.md and link it to the README ?
We can populate it with the example you mentioned above.

First version added.


Made use of more AsyncKeyedLock features

@Kukks are you interested in such PRs? You will gain performance from this update. Furthermore 6.4.2 is out.

@Kukks are you interested in such PRs? You will gain performance from this update. Furthermore 6.4.2 is out.

There is no high performance requirement or enough pros to introduce a third party dependency for this plugin

@Kukks are you interested in such PRs? You will gain performance from this update. Furthermore 6.4.2 is out.

There is no high performance requirement or enough pros to introduce a third party dependency for this plugin

This repository already depends on AsyncKeyedLock and this PR is therefore not introducing new dependencies.

@Kukks are you interested in such PRs? You will gain performance from this update. Furthermore 6.4.2 is out.

There is no high performance requirement or enough pros to introduce a third party dependency for this plugin

This repository already depends on AsyncKeyedLock and this PR is therefore not introducing new dependencies.

Only some of the plugins do. You can see in the PR you added it to 3 plugins


Devise within Devise?!

So I have Devise log in working for dev_user (basically a wrapper around a prototype I'm building).
Once in the actual site, there is an option to sign up which I have called business_user (with a different user/email).
The log in for business_user is working fine, however, when they log out, they are also logged out at the top level (dev_user).
Anyone know a way around this? I have adjusted the log out link to destroy_business_user_session_path, :method => :delete
which I thought would be enough, but clearly I am missing something.
Any help greatly appreciated!

Please check the [sign_out_all_scopes](https://github.com/plataformatec/devise/blob/6dd444458258c27ad08f56151e74fe9998713818/lib/devise.rb#L223-L225) option.
Please use the mailing list or StackOverflow for questions/help, where a wider community will be able to help you. We reserve the issues tracker for issues only.

Thanks for this @lucasmazza I'm new to development so getting 'inside' of things is still not second nature yet. This has really helped. Have a good day!


Filtering measures by tags=core shows incorrect message

https://openprescribing.net/measure/?tags=core

Closed in #915


Regression in 21.1 regarding buffers

Here's a test:
  @Test
  public void regression() {
    Context context = Context.newBuilder("js")
      .allowIO(true)
      .allowCreateThread(false)
      .allowHostAccess(HostAccess.newBuilder(HostAccess.ALL).build())
      .allowPolyglotAccess(PolyglotAccess.NONE)
      .allowHostClassLookup(x -> true)
      .build();
    Source source = Source
      .newBuilder("js",
        "const ByteBuffer = Java.type('java.nio.ByteBuffer');\n" +
          "let bbuf = ByteBuffer.allocate(10);\n" +
          "let buffer = new ArrayBuffer(bbuf);\n" +
          "buffer.byteLength;\n",
        "main.js")
      .buildLiteral();

    // 19.3 true
    // 21.1 false
    assertEquals(
      10,
      context.eval(source).asInt());
  }

If I use a regular context (by this I mean without customizations), it passes in 21.1, but if I reproduce some tunnables I use in es4x it fails. It used to pass as is in 19.3

Thank you for the report. This is a bug in HostAccess.newBuilder(HostAccess) (resp. in HostAccess.Builder(HostAccess)). It fails to copy allowBufferAccess flag from its argument. So, your test-case will work if you add allowBufferAccess(true) explicitly:
.allowHostAccess(HostAccess.newBuilder(HostAccess.ALL).allowBufferAccess(true).build())

I run into this issue few days ago which made me realize that it is not fixed yet. So, I decided to fix it myself (fixed by https://github.com/oracle/graal/commit/f732c6ac98c8791a835eadfeb21f8c53536edbbd).


What does write complete mean?

Not so much a bug or issue but more of a question. Say for example for a TCP connection, when is a write regarded as complete? Is it when all the data has been ACKed by the peer, or before that?
Thanks!

To give some context, we have an epoll patch that notifies us when the TCP send buffer is empty (all data ACKed). We're now experimenting with switching to liburing and I wonder if we need to patch it as well, or if it has the functionality we need.

It's signaled as completed in the exact same fashion as an eg sendmsg() or similar regular system call would, there's no differences there.


update default for --projects-dir to current directory

Closes #125
Do we want to add an integration test for this?

@graciegoheen Heads up that there is a test failure on this one!


Spam issue

Content removed.

@marrykanty I'm still here, haha. If Kasper can delete your account that I want it!


Fix: the subscribe to our newsletter is inaccessible

The subscribe to our newsletter section in footer is inaccessible because of handled items. I will fix it .

Assign me.

Okay assigning to you!


Issue with sending Device Class C Downlinks (Packet Forwarding to Gateway with ChirpStack MQTT Bridge v4)

I have encountered an issue with downlink packet forwarding between a ChirpStack network server and a RAK gateway using the ChirpStack MQTT bridge. Below is a brief and detailed description of the problem, as well as the configuration used during testing.
Brief Description:
I am experiencing an issue where scheduling a downlink message with an application payload size greater than 177 bytes results in an invalid message being sent by the gateway. Specifically, the gateway transmits a null-type message with all fields set to null. This issue occurs when the gateway is operating in packet forwarder mode with WisGate OS 2.2.2 and ChirpStack MQTT Bridge v4 (Protobuf).
Detailed Description:
Hardware and Configuration Overview:

Affected LoRaWAN Gateway Products:

RAK Edge Lite (RAK7268CV2)
RAK Edge Pro (RAK7289V2)

Firmware: WisGateOS_2.2.2_RAK
LoRa Configuration:

Packet Forwarder Mode
Frequency Plan: Germany, EU868, Conform To LoRaWAN

Protocol:

LoRa Gateway MQTT Bridge
MQTT for ChirpStack 4.x (Protobuf)
Configuration mostly using default settings

ChirpStack Server Configuration:

ChirpStack v4 Network Server running on a Raspberry Pi 4
Setup using the ChirpStack Docker Compose (latest commit [50159c0](https://github.com/chirpstack/chirpstack-docker/commit/50159c0e19f31a5ae692bd42cfe2ff7dce516194))

Test Scenario:

Sending downlink messages to a Class C device with a payload size larger than 177 bytes.

Observations:

The issue is consistently reproducible with any application payload size greater than 177 bytes.

The problem appears independent of the rx2dr setting (tested with DR6 and DR4).

The issue was observed on both RAK Edge Lite and RAK Edge Pro gateways configured in packet forwarder mode using the ChirpStack v4 MQTT bridge.

Note that when using a RAK WisGate Developer Gateway (RAK7271), I was able to successfully send downlink packets with payload sizes larger than 177 bytes up to the maximum payload size according to LoRaWAN specifications (242 bytes). This also suggests that the issue lies within the ChirpStack MQTT Bridge, because if I understood correctly the Bridge is not used with the Developer Gateway (since it is directly conncted via USB).

In brief, for the setup of the developer gateway, I simply run on the raspberry:

sudo ./install.sh --chirpstack=not_install

and then adjust the ip in gateway_conf to localhost so that I could use my Chirpstack docker instance as usual.

Diagnostics:
The WisGate Diagnostics tab also suggests an error during parsing of the downlink message from ChirpStack:
Tue Aug 27 11:13:27 2024 user.warn lora_pkt_fwd[6775]: WARNING: [down] mismatch between .size and .data size once converted to binary

Steps to Reproduce:

Set up the ChirpStack server using Docker on a Raspberry Pi according to the official setup instructions.
Register an end-device and configure it as Class C for testing (LoRaWAN Spec. 1.0.3A).
Schedule a downlink with an application payload size greater than 177 bytes (e.g., 180 or 200 bytes).

Appendix: I have attached screenshots and packet captures comparing downlink transmissions with payload sizes of 177 and 178 bytes, both on the ChirpStack web interface and the WisGate gateway.

I reported this issue to [support<EMAIL_ADDRESS>and posted it on the community forum too ([Link](https://forum.rakwireless.com/t/issue-with-downlink-packet-forwarding-on-wisgate-os-2-2-2-with-chirpstack-mqtt-bridge-v4/13368)) but have not yet received any response. I would appreciate any advice or tips you may have. At least I want to understand whether the problem is within RAK's implementation of the Chirpstack-MQTT-Bridge, the bridge implementation in general, or, the problem may be caused on my side due to some misconfiguration.
Best regards,
Christian
Appendix

I don't think the WisGateOS firmware has the ChirpStack MQTT Forwarder embedded. They have implemented a forwarder which is compatible with the ChirpStack v4 msg. format. It might be better to report this to RAK.

Thanks for your quick response. I finally got confirmation from RAK that this is a bug in WisGate OS2 which will be fixed in an upcoming release.


Any particular reason why there is no member function to retrieve destinations list from session object?

Would that perhaps be unsafe for some reason or rather it just didn't seem like it's needed?
Or maybe i'm wrong and destination list can be retrieved, but some different way?

Probably because it didn't seem needed (and that I would need to implement it in all transmitters)


[BUG] Kyma instance cannot be created "User is unauthorized for this operation [Error: 11004/405]"

Is there an existing issue for this?

[X] I have searched the existing issues

What version of Terraform are you using?
1.5.6
What type of issue are you facing
bug report
Describe the bug
Showed this while on a call with @lechnerc77 and he confirmed I should probably add it here.
Background

I am in a global account administrator role
I am also in a sub-account administrator role
The sub-account already has a CloudFoundry environment (not sure if that's relevant)
I have enabled the Kyma entitlement via Terraform previously.
I can create a Kyma environment manually via the BTP Cockpit UI.

Problem
I am unable to create a Kyma resource, e.g.
resource "btp_subaccount_environment_instance" "kyma" {
  subaccount_id    = btp_subaccount.products.id
  name             = "sct-products-kyma"
  environment_type = "kyma"
  service_name     = "kyma"
  plan_name        = "aws"

  parameters = jsonencode({
    name   = "sct-products-kyma"
    region          = "us-east-1"
    machine_type    = "mx5.xlarge" #smallest option
    auto_scaler_min = 3
    auto_scaler_max = 20
  })
}

When I run terraform apply, I receive the error:

│ Error: API Error Creating Resource Environment Instance (Subaccount)
│
│   with module.product_environment.module.product_environment_btp.btp_subaccount_environment_instance.kyma,
│   on modules\product_environment_btp\main.tf line 92, in resource "btp_subaccount_environment_instance" "kyma":
│   92: resource "btp_subaccount_environment_instance" "kyma" {
│
│ User is unauthorized for this operation [Error: 11004/405]

Expected Behavior
I should be able to create a Kyma environment within a sub-account.
Steps To Reproduce

Terraform init
Create a resource/reference for a sub-account.
Already have a CF environment set up in the sub-account (mentioning here in case it's relevant)
Enable Kyma entitlement (in my case, I did this via Terraform)
Add a kyma resource, e.g. in the same I have above
Attempt terraform apply

Add screenshots to help explain your problem
No response
Additional context
No response

@SeanKilleen just cross-checked the parameters you mentioned above and the PR you referenced. Can you crosscheck that for  service_name  the value is "kymaruntime"?
As additional info based on our discussion you find the available parameters for Kyma here depending on your landscape and plan here : https://help.sap.com/docs/btp/sap-business-technology-platform/available-plans-in-kyma-environment

Hi @lechnerc77 -- just to confirm, you're saying that in my Terraform service instance definition, the environment_type should be kyma, and the service_name should be kymaruntime?
If so, that's the likely culprit. I didn't have the docs example so I assumed both values would be kyma, much as the other values were cloudfoundry. But I do see that in the service entitlement definition, it is called kymaruntime, so that could absolutely be the discrepancy.
I'm not in a position to teardown the Kyma cluster I'm working with currently, but as soon as I can, I will do so and then attempt to recreate it with this.

Yes that's right. The service name is kymaruntime (instead of kyma).

@lechnerc77 SUCCESS! 🎉 I'm so sorry that I missed that detail. After updating the service name (by making it a reference to the service entitlement's service name, so that it's clear), the operation appears to be in progress and I've received no errors.
Thank you for your support. I'll also update #430 to ensure it's correct.

Great to hear that - no worries I missed that too during our session. #430 is already in the right shape.


[Feature] Return on Equity Endpoint

Are you adding a new feature?

[x] YES
[ ] NO

Describe your feature/enhancement.
I want to add an endpoint to calculate return on equity.
Can you add the feature by yourself?

[x] YES
[ ] NO

Additional Information

Check once if your endpoint matches with this endpoint \roi_equity_funds

@ighoshsubho yes it seems it already exists. Will you please assign this issue to me #414


Add pipeline for testing with ruby-static feature in CI

Currently, the Ruby versions published by ruby/setup-ruby do not have libruby-static. So we'll need to compile our own version and test with the --features ruby-static flag.

Done.


Lingering region highlights after evil substitute on a visual selection

What did you expect to happen?
Somewhere in the last few weeks (if you want I can bisect the exact commit) region highlights from evil-traces when using evil's :s substitution operator on a visual (line) selection persisting after the edit is finished. The issue looks like this:
https://user-images.githubusercontent.com/748520/107850542-6dbd1e80-6e03-11eb-9d14-1dd4cb5e6bb4.mp4
What actually happened?
The lines will stay highlighted as if they're part of a visual selection until the next time you do an evil substitute on a visual selection.
Additional details:

I'm using gccemacs (the exact commit is in the doom/info dump below)
This also happens in doom/sandbox with my private config disabled.
Error in minibuffer-exit-hook (evil-ex-teardown): (wrong-type-argument window-live-p nil) is printed to *Messages* when this happens.

Steps to reproduce:

Open some file, I've used ~/.emacs.d/modules/editor/evil/config.el in the screencast above.
Select some text with v or V
Use :s/foo/bar to replace some text in the selection.

System information:

SYSTEM  info       ("Manjaro Linux" .  This appears to be an upstream bug with evil-traces, the package that powers these highlights, and should be reported to them. I'll follow up  if I find out more.

This issue mysteriously fixed itself at some point!


Feat/edit blog endpoint

API Endpoint: Edit Blog Post
Description
This API endpoint allows super admins to edit existing blog posts. It validates the input data and updates the blog post securely in the database.
Endpoint

Method: PUT
URL: /api/v1/blog/edit/:id

Request Body
{
  "title": "string", // Required
  "excerpt": "string", // Optional
  "tags": ["string"] // Optional
}

Response

Success (200 OK):

{
  "message": "Blog successfully updated",
  "id": "int",
  "title": "string",
  "excerpt": "string",
  "updated_at": "Datatime"
}

Acceptance Criteria

The endpoint allows only a super admin to edit an existing blog post.
The endpoint should be accessible at /api/v1/blog/edit/{blog_id}
The endpoint should accept HTTP PUT requests.
The API should validate the request payload to ensure the title and other necessary fields is
provided.
Upon successful validation of the input data, the blog post should be updated in the database securely.
Return a 200 OK status code on successful request.

Request body application/json
  "title": "string",
  "excerpt": "string",
  "tags": ["string"]
}

Success payload
  "message": "Blog successfully updated",
  "id": "int",
  "title": "string",
  "excerpt": "string",
  "updated_at": "Datatime"
}

Error payload
  "message": "Unauthorized request",
  "status_code": 401
}

Requirements

[ ] Implement server-side logic to handle blog post edit submissions.
[ ] Validate and sanitize incoming data.
[ ] Update the blog post securely in the database.
[ ] A 401 error should be sent if an unauthorized user tries to edit a blog

Expected Outcome

The API endpoint allows super admin to edit their blog posts via the provided data, ensuring all updates are securely stored and validated.

Test

[x] Write unit tests to ensure the blog post edit endpoint validates input correctly and updates the post securely.
[x] Test various scenarios for editing blog posts (e.g., missing title, empty content, invalid tags).
[x] Perform security test to ensure unauthorized user can not update a blog post.
[x] Test various scenarios:

Successful editing of an existing blog post
Attempting to edit a non existing blog post
Attempting to edit a blog post without authentication
Attempting to edit a blog post without proper permissions

Referrence Issue
Blog Edit

Fix your PR title

Fix your PR title


[WIP, Test] Updated introduction of manual - @open sesame 08/12 13:31

This commit is trivial. It is to update the existing introduction.
Signed-off-by: Geunsik Lim<EMAIL_ADDRESS>
[Template] PR Description
In general, github system automatically copies your commit message for your convenience.
Please remove unused part of the template after writing your own PR description with this template.
$ git commit -s filename1 filename2 ... [enter]

Summarize changes in around 50 characters or less

More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contexts, the first line is treated as the
subject of the commit and the rest of the text as the body. The
blank line separating the summary from the body is critical;
various tools like `log`, `shortlog` and `rebase` can get confused
if you run the two together.

Further paragraphs come after blank lines.

**Changes proposed in this PR:**
- Bullet points are okay, too
- Typically a hyphen or asterisk is used for the bullet, preceded
  by a single space, with blank lines in between, but conventions vary here.

Resolves: #123
See also: #456, #789

**Self evaluation:**
1. Build test: [ ]Passed [ ]Failed [*]Skipped
2. Run test: [ ]Passed [ ]Failed [* ]Skipped

**How to evaluate:**
1. Describe how to evaluate in order to be reproduced by reviewer(s).

Add signed-off message automatically by running **$git commit -s ...** command.

$ git push origin <your_branch_name>

I thought you are on vacation abroad. O.O

This hotel provides a free Wi-Fi service on the rooftop for customer convenience. :)


Reorganize/improve import tool

I have a hard time figuring out how to import data into qiime2 tools using the import tool. I guess the most frequently used data is demultiplexed fastq.gz (maybe + sample data tsv file), e.g https://data.qiime2.org/2022.8/tutorials/importing/casava-18-single-end-demultiplexed.zip. I failed to find the corresponding option in the import tool.

I guess I start with SampleData[PairedEndSequencesWithQuality]?
Then there are many options that allow to select either

1 dataset (e.g. Paired End Fastq Manifest Phred33)
or a collection (eg Casava One Eight Laneless Per Sample Directory Format) but the collection type is not set (I guess it should be collection_type="list:paired")
or individual files via a repeat where the number of elements can be anything between 1 and infinity

To get me started with exploring downstream tools it would be nice if someone could tell me for now how I could import data like the above (is there already a Galaxy specific tutorial that I did not notice so far?).
I guess the main problem is that the mapping between Galaxy concepts and qiime2 concepts needs a bit of improvement (e.g. that galaxy data types and collection types are not used yet). But probably its also because I'm unexperienced with qiime2 .. at the moment I'm just guessing that the goal of the import is to create a single qza dataset from all fastq files? Also I'm missing info in the help (like the definition of what a manifest is).
Since the tool is auto generated I'm unsure if this is easily possible. An alternative would be to handcraft an import tool covering the most frequently used types of input data that has a tight integration of the Galaxy concepts.
I imagine a tool that takes as input either

list:paired (for paired end data) or
list (for single end data)

with format fastq.gz plus (in addition simple data inputs with multiple="true" might be useful [because some users don't seem to like collections for some reason])

optional barcodes
optional tabular data set for metadata.

The tool then automatically knows about the phred encoding due to the specific Galaxy fastq.gz sub-datatypes.

Also I should mention that the Manifest style formats you mention for this particular type were a hack for importing which can basically never work in Galaxy, as they expect real filepaths to exist.
I have a rather informal proposal for modifying directory formats to better suite Galaxy as well, perhaps there is a way to indicate pair-ed-ness in this realm, which we could then automatically map to Galaxy's paired collections.

Hi @ebolyen is there some documentation on the expected file names for the different input types (which might be added to the Galaxy tool help)?
I'm (better a colleague) currently struggling to import data: I'm using Type of data to import: SampleData[PairedEndSequencesWithQuality]
With QIIME 2 file format to import from: CasavaOneEightLanelessPerSampleDirFmt
Unexpected error importing data:
Unrecognized file (/work/songalax/galaxy-dev/database/jobs_directory/020/20999/working/q2galaxy-importb4s4e8x1/metadata-hs-t1.txt) for CasavaOneEightLanelessPerSampleDirFmt.

With QIIME 2 file format to import from: | CasavaOneEightSingleLanePerSampleDirFmt
Unexpected error importing data:
Missing one or more files for CasavaOneEightSingleLanePerSampleDirFmt: '.+_.+_L[0-9][0-9][0-9]_R[12]_001\\.fastq\\.gz'

The latter is kind of clear from the error message since the regex does not match our file names: ids.txt
Could you give us some advice which import format we should choose, or if we should rename our data?

Hey @bernt-matthias,
Sorry for not getting back to you. For user-support the forum is much more closely observed.
Regarding the error. Yeah that's definitely an unhelpful error. Your IDs look ok, although I see
qiime2 metadata tabulate on data 142: visualization.qzv
metadata-hs-t1.txt

in your list, which I presume isn't actually in the collection.
I would try setting the append an extension option to fastq.gz if the IDs in your collection are something like:
29_4_S83_R1_001

as QIIME2 is trying to match the entire collection element identifier to the directory regex.

Sorry for not getting back to you.

No worries :)

For user-support the forum is much more closely observed.

Wondering if you want to add a link to the forum to the tool's help section?

Your IDs look ok, although I see

Oh, yes. That is probably it.

Just have read this again

Also I should mention that the Manifest style formats you mention for this particular type were a hack for importing which can basically never work in Galaxy, as they expect real filepaths to exist.

Would relative path work?

Unfortunately no, you would need to have an absolute path the the /some/galaxy/managed/path/001.dat file which you happen to know is a fastq.gz. If you can predict those paths then it would work... presuming the data was in fact on the same host as the job was on which is also not likely to be true.
I'm working on something right now that may clean this up, but no particular ETA. Until then, using the directory formats is your best bet as you have control over the element identifiers which can be made to match the expected relative path of the directory format (as tedious as that is).

Unfortunately no, you would need to have an absolute path the the /some/galaxy/managed/path/001.dat file which you happen to know is a fastq.gz. If you can predict those paths then it would work... presuming the data was in fact on the same host as the job was on which is also not likely to be true.

Indeed, this assumption does not hold in all Galaxy installations.

I'm working on something right now that may clean this up, but no particular ETA.

+1

Until then, using the directory formats is your best bet as you have control over the element identifiers which can be made to match the expected relative path of the directory format (as tedious as that is).

Thanks

Hi guys! Now that we have the tools on EU we get this problem as well :)
It there any workaround yet?


Clarify cumulative energy savings for Reporting Periods over 12 months

If possible we’d like some clarification on the cumulative savings calculation for projects with reporting periods over 12 months. Is the data annualized?
Sections 3.6 and 3.12 of the methods document describe how to calculate AEU for each period. Section 4.1.2 specifies that “CalTRACK does not explicitly support annualizing results”.  However, our OEE CalTRACK dashboard displays “Cumulative Savings” for kWhs, therms, and MMBTUs, so our question is regarding how this figure calculated.
Example: Assuming a project savings 100 kWh/month after the intervention:

After 3 months cumulative savings would be 300 kWhs.
After 12 months cumulative savings would be 1200 kWhs.
After 15 months… is the cumulative savings 1500 or 1200 kWhs?

We believe the answer for CalTRACK is 1500 kWhs but would like to clarify.
(HEA uses a rolling 12 month reporting period described in issue #74.)

You need to look at Aggregation. 4.1.1 describes how savings calculations are aggregated. In essence, neither of your answers is correct. If after 12 months you have 1200 kWh of savings, after 15 months your cumulative savings would be 1200 plus whatever you saved in months 13, 14, and 15.

Thanks McGee.
So in my example case of a reduction in electric base load of 100 kWh/month (compared to the baseline period), I believe 24 months after the intervention cumulative savings would be 2400 kWhs.


fix: flutter test fails on Fluter 3.16.0

Description
Running test fails on Flutter (3.16.0)
Steps To Reproduce

Run flutter tests:

# Run tests (from src/very_good_flame_game)
flutter test

See failures.

 Logs

00:00 +0: loading /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/cubit/preload/preload_state_test.dart
00:01 +0: loading /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/cubit/preload/preload_state_test.dart
00:01 +0: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/cubit/preload/preload_state_test.dart: PreloadState initial
00:01 +1: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/cubit/preload/preload_state_test.dart: PreloadState initial
00:01 +1: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/cubit/preload/preload_state_test.dart: PreloadState progress when not started is zero
00:01 +2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/cubit/preload/preload_state_test.dart: PreloadState progress when not started is zero
00:01 +2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/cubit/preload/preload_state_test.dart: PreloadState progress after started
00:01 +3: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/cubit/preload/preload_state_test.dart: PreloadState progress after started
00:01 +3: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/cubit/preload/preload_state_test.dart: PreloadState isComplete when not started is zero
00:01 +4: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/cubit/preload/preload_state_test.dart: PreloadState isComplete when not started is zero
00:01 +4: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/cubit/preload/preload_state_test.dart: PreloadState isComplete after started
00:01 +5: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/cubit/preload/preload_state_test.dart: PreloadState isComplete after started
00:01 +5: loading /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/cubit/preload/preload_cubit_test.dart
00:01 +5: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/cubit/preload/preload_cubit_test.dart: PreloadCubit loadSequentially loads assets
00:02 +5: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/cubit/preload/preload_cubit_test.dart: PreloadCubit loadSequentially loads assets
00:02 +6: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/view/loading_page_test.dart: LoadingPage basic layout
00:02 +7: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/view/loading_page_test.dart: LoadingPage basic layout
00:02 +8: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/view/loading_page_test.dart: LoadingPage basic layout
00:02 +9: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/view/loading_page_test.dart: LoadingPage basic layout
00:02 +10: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/app/view/app_test.dart: App renders AppView
00:02 +11: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/app/view/app_test.dart: App renders AppView
00:02 +12: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/title/view/title_page_test.dart: TitlePage renders TitleView
00:02 +13: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/view/loading_page_test.dart: LoadingPage redirects after loading
00:02 +13: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/view/loading_page_test.dart: LoadingPage redirects after loading
══╡ EXCEPTION CAUGHT BY FOUNDATION LIBRARY ╞════════════════════════════════════════════════════════
The following _TypeError was thrown while dispatching notifications for _History:
type 'Null' is not a subtype of type 'bool'

When the exception was thrown, this was the stack:
#0      MockNavigator.canPop (package:mockingjay/src/mock_navigator.dart:66:7)
#1      _MockNavigatorState.canPop (package:mockingjay/src/mock_navigator.dart:193:23)
#2      NavigatorState._handleHistoryChanged (package:flutter/src/widgets/navigator.dart:3489:34)
#3      ChangeNotifier.notifyListeners (package:flutter/src/foundation/change_notifier.dart:433:24)
#4      _History.addAll (package:flutter/src/widgets/navigator.dart:3406:7)
#5      NavigatorState.restoreState (package:flutter/src/widgets/navigator.dart:3608:18)
#6      RestorationMixin._doRestore (package:flutter/src/widgets/restoration.dart:924:5)
#7      RestorationMixin.didChangeDependencies (package:flutter/src/widgets/restoration.dart:910:7)
#8      NavigatorState.didChangeDependencies (package:flutter/src/widgets/navigator.dart:3656:11)
#9      StatefulElement._firstBuild (package:flutter/src/widgets/framework.dart:5620:11)
#10     ComponentElement.mount (package:flutter/src/widgets/framework.dart:5447:5)
...     Normal element mounting (220 frames)
#230    Element.inflateWidget (package:flutter/src/widgets/framework.dart:4326:16)
#231    MultiChildRenderObjectElement.inflateWidget (package:flutter/src/widgets/framework.dart:6871:36)
#232    MultiChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:6883:32)
...     Normal element mounting (453 frames)
#685    _InheritedProviderScopeElement.mount (package:provider/src/inherited_provider.dart:411:11)
...     Normal element mounting (7 frames)
#692    SingleChildWidgetElementMixin.mount (package:nested/nested.dart:222:11)
...     Normal element mounting (7 frames)
#699    SingleChildWidgetElementMixin.mount (package:nested/nested.dart:222:11)
...     Normal element mounting (7 frames)
#706    _NestedHookElement.mount (package:nested/nested.dart:187:11)
...     Normal element mounting (7 frames)
#713    SingleChildWidgetElementMixin.mount (package:nested/nested.dart:222:11)
#714    Element.inflateWidget (package:flutter/src/widgets/framework.dart:4326:16)
#715    Element.updateChild (package:flutter/src/widgets/framework.dart:3831:20)
#716    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:5496:16)
#717    Element.rebuild (package:flutter/src/widgets/framework.dart:5187:7)
#718    ProxyElement.update (package:flutter/src/widgets/framework.dart:5800:5)
#719    Element.updateChild (package:flutter/src/widgets/framework.dart:3815:15)
#720    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:5496:16)
#721    StatefulElement.performRebuild (package:flutter/src/widgets/framework.dart:5634:11)
#722    Element.rebuild (package:flutter/src/widgets/framework.dart:5187:7)
#723    StatefulElement.update (package:flutter/src/widgets/framework.dart:5657:5)
#724    Element.updateChild (package:flutter/src/widgets/framework.dart:3815:15)
#725    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:5496:16)
#726    Element.rebuild (package:flutter/src/widgets/framework.dart:5187:7)
#727    ProxyElement.update (package:flutter/src/widgets/framework.dart:5800:5)
#728    Element.updateChild (package:flutter/src/widgets/framework.dart:3815:15)
#729    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:5496:16)
#730    Element.rebuild (package:flutter/src/widgets/framework.dart:5187:7)
#731    ProxyElement.update (package:flutter/src/widgets/framework.dart:5800:5)
#732    Element.updateChild (package:flutter/src/widgets/framework.dart:3815:15)
#733    _RawViewElement._updateChild (package:flutter/src/widgets/view.dart:289:16)
#734    _RawViewElement.update (package:flutter/src/widgets/view.dart:376:5)
#735    Element.updateChild (package:flutter/src/widgets/framework.dart:3815:15)
#736    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:5496:16)
#737    Element.rebuild (package:flutter/src/widgets/framework.dart:5187:7)
#738    StatelessElement.update (package:flutter/src/widgets/framework.dart:5547:5)
#739    Element.updateChild (package:flutter/src/widgets/framework.dart:3815:15)
#740    RootElement._rebuild (package:flutter/src/widgets/binding.dart:1334:16)
#741    RootElement.update (package:flutter/src/widgets/binding.dart:1312:5)
#742    RootElement.performRebuild (package:flutter/src/widgets/binding.dart:1326:7)
#743    Element.rebuild (package:flutter/src/widgets/framework.dart:5187:7)
#744    BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2895:19)
#745    AutomatedTestWidgetsFlutterBinding.drawFrame (package:flutter_test/src/binding.dart:1409:19)
#746    RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:457:5)
#747    SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1325:15)
#748    SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1255:9)
#749    AutomatedTestWidgetsFlutterBinding.pump.<anonymous closure> (package:flutter_test/src/binding.dart:1264:9)
#752    TestAsyncUtils.guard (package:flutter_test/src/test_async_utils.dart:71:41)
#753    AutomatedTestWidgetsFlutterBinding.pump (package:flutter_test/src/binding.dart:1251:27)
#754    WidgetTester.pumpWidget.<anonymous closure> (package:flutter_test/src/widget_tester.dart:578:22)
#757    TestAsyncUtils.guard (package:flutter_test/src/test_async_utils.dart:71:41)
#758    WidgetTester.pumpWidget (package:flutter_test/src/widget_tester.dart:575:27)
#759    PumpApp.pumpApp (file:///Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/helpers/pump_app.dart:18:12)
#760    main.<anonymous closure>.<anonymous closure> (file:///Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/view/loading_page_test.dart:86:20)
#761    testWidgets.<anonymous closure>.<anonymous closure> (package:flutter_test/src/widget_tester.dart:168:29)
<asynchronous suspension>
#762    TestWidgetsFlutterBinding._runTestBody (package:flutter_test/src/binding.dart:1013:5)
<asynchronous suspension>
<asynchronous suspension>
(elided 5 frames from dart:async and package:stack_trace)

The _History sending notification was:
  [Instance of '_RouteEntry']
════════════════════════════════════════════════════════════════════════════════════════════════════

00:02 +13 -1: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/view/loading_page_test.dart: LoadingPage redirects after loading [E]
  Test failed. See exception logs above.
  The test description was: redirects after loading

To run this test again: /Users/alestiago/Developer/flutter/flutter/bin/cache/dart-sdk/bin/dart test /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/loading/view/loading_page_test.dart -p vm --plain-name 'LoadingPage redirects after loading'

00:02 +14 -1: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/title/view/title_page_test.dart: TitleView renders start button
00:02 +14 -1: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/title/view/title_page_test.dart: TitleView starts the game when start button is tapped
00:03 +14 -1: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/title/view/title_page_test.dart: TitleView starts the game when start button is tapped
00:03 +14 -1: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/title/view/title_page_test.dart: TitleView starts the game when start button is tapped
══╡ EXCEPTION CAUGHT BY FOUNDATION LIBRARY ╞════════════════════════════════════════════════════════
The following _TypeError was thrown while dispatching notifications for _History:
type 'Null' is not a subtype of type 'bool'

When the exception was thrown, this was the stack:
#0      MockNavigator.canPop (package:mockingjay/src/mock_navigator.dart:66:7)
#1      _MockNavigatorState.canPop (package:mockingjay/src/mock_navigator.dart:193:23)
#2      NavigatorState._handleHistoryChanged (package:flutter/src/widgets/navigator.dart:3489:34)
#3      ChangeNotifier.notifyListeners (package:flutter/src/foundation/change_notifier.dart:433:24)
#4      _History.addAll (package:flutter/src/widgets/navigator.dart:3406:7)
#5      NavigatorState.restoreState (package:flutter/src/widgets/navigator.dart:3608:18)
#6      RestorationMixin._doRestore (package:flutter/src/widgets/restoration.dart:924:5)
#7      RestorationMixin.didChangeDependencies (package:flutter/src/widgets/restoration.dart:910:7)
#8      NavigatorState.didChangeDependencies (package:flutter/src/widgets/navigator.dart:3656:11)
#9      StatefulElement._firstBuild (package:flutter/src/widgets/framework.dart:5620:11)
#10     ComponentElement.mount (package:flutter/src/widgets/framework.dart:5447:5)
...     Normal element mounting (220 frames)
#230    Element.inflateWidget (package:flutter/src/widgets/framework.dart:4326:16)
#231    MultiChildRenderObjectElement.inflateWidget (package:flutter/src/widgets/framework.dart:6871:36)
#232    MultiChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:6883:32)
...     Normal element mounting (453 frames)
#685    _InheritedProviderScopeElement.mount (package:provider/src/inherited_provider.dart:411:11)
...     Normal element mounting (7 frames)
#692    SingleChildWidgetElementMixin.mount (package:nested/nested.dart:222:11)
...     Normal element mounting (7 frames)
#699    SingleChildWidgetElementMixin.mount (package:nested/nested.dart:222:11)
...     Normal element mounting (7 frames)
#706    _NestedHookElement.mount (package:nested/nested.dart:187:11)
...     Normal element mounting (7 frames)
#713    SingleChildWidgetElementMixin.mount (package:nested/nested.dart:222:11)
#714    Element.inflateWidget (package:flutter/src/widgets/framework.dart:4326:16)
#715    Element.updateChild (package:flutter/src/widgets/framework.dart:3831:20)
#716    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:5496:16)
#717    Element.rebuild (package:flutter/src/widgets/framework.dart:5187:7)
#718    ProxyElement.update (package:flutter/src/widgets/framework.dart:5800:5)
#719    Element.updateChild (package:flutter/src/widgets/framework.dart:3815:15)
#720    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:5496:16)
#721    StatefulElement.performRebuild (package:flutter/src/widgets/framework.dart:5634:11)
#722    Element.rebuild (package:flutter/src/widgets/framework.dart:5187:7)
#723    StatefulElement.update (package:flutter/src/widgets/framework.dart:5657:5)
#724    Element.updateChild (package:flutter/src/widgets/framework.dart:3815:15)
#725    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:5496:16)
#726    Element.rebuild (package:flutter/src/widgets/framework.dart:5187:7)
#727    ProxyElement.update (package:flutter/src/widgets/framework.dart:5800:5)
#728    Element.updateChild (package:flutter/src/widgets/framework.dart:3815:15)
#729    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:5496:16)
#730    Element.rebuild (package:flutter/src/widgets/framework.dart:5187:7)
#731    ProxyElement.update (package:flutter/src/widgets/framework.dart:5800:5)
#732    Element.updateChild (package:flutter/src/widgets/framework.dart:3815:15)
#733    _RawViewElement._updateChild (package:flutter/src/widgets/view.dart:289:16)
#734    _RawViewElement.update (package:flutter/src/widgets/view.dart:376:5)
#735    Element.updateChild (package:flutter/src/widgets/framework.dart:3815:15)
#736    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:5496:16)
#737    Element.rebuild (package:flutter/src/widgets/framework.dart:5187:7)
#738    StatelessElement.update (package:flutter/src/widgets/framework.dart:5547:5)
#739    Element.updateChild (package:flutter/src/widgets/framework.dart:3815:15)
#740    RootElement._rebuild (package:flutter/src/widgets/binding.dart:1334:16)
#741    RootElement.update (package:flutter/src/widgets/binding.dart:1312:5)
#742    RootElement.performRebuild (package:flutter/src/widgets/binding.dart:1326:7)
#743    Element.rebuild (package:flutter/src/widgets/framework.dart:5187:7)
#744    BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2895:19)
#745    AutomatedTestWidgetsFlutterBinding.drawFrame (package:flutter_test/src/binding.dart:1409:19)
#746    RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:457:5)
#747    SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1325:15)
#748    SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1255:9)
#749    AutomatedTestWidgetsFlutterBinding.pump.<anonymous closure> (package:flutter_test/src/binding.dart:1264:9)
#752    TestAsyncUtils.guard (package:flutter_test/src/test_async_utils.dart:71:41)
#753    AutomatedTestWidgetsFlutterBinding.pump (package:flutter_test/src/binding.dart:1251:27)
#754    WidgetTester.pumpWidget.<anonymous closure> (package:flutter_test/src/widget_tester.dart:578:22)
#757    TestAsyncUtils.guard (package:flutter_test/src/test_async_utils.dart:71:41)
#758    WidgetTester.pumpWidget (package:flutter_test/src/widget_tester.dart:575:27)
#759    PumpApp.pumpApp (file:///Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/helpers/pump_app.dart:18:12)
#760    main.<anonymous closure>.<anonymous closure> (file:///Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/title/view/title_page_test.dart:30:20)
#761    testWidgets.<anonymous closure>.<anonymous closure> (package:flutter_test/src/widget_tester.dart:168:29)
<asynchronous suspension>
#762    TestWidgetsFlutterBinding._runTestBody (package:flutter_test/src/binding.dart:1013:5)
<asynchronous suspension>
<asynchronous suspension>
(elided 5 frames from dart:async and package:stack_trace)

The _History sending notification was:
  [Instance of '_RouteEntry']
════════════════════════════════════════════════════════════════════════════════════════════════════

00:03 +14 -2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/title/view/title_page_test.dart: TitleView starts the game when start button is tapped [E]
  Test failed. See exception logs above.
  The test description was: starts the game when start button is tapped

To run this test again: /Users/alestiago/Developer/flutter/flutter/bin/cache/dart-sdk/bin/dart test /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/title/view/title_page_test.dart -p vm --plain-name 'TitleView starts the game when start button is tapped'

00:03 +14 -2: loading /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/components/counter_component_test.dart
00:03 +14 -2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/components/counter_component_test.dart: CounterComponent has all components
00:03 +15 -2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/components/counter_component_test.dart: CounterComponent has all components
00:03 +15 -2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/components/counter_component_test.dart: CounterComponent changes text count correctly
00:03 +16 -2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/components/counter_component_test.dart: CounterComponent changes text count correctly
00:03 +16 -2: loading /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/view/game_page_test.dart
00:03 +16 -2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/view/game_page_test.dart: (setUpAll)
00:03 +16 -2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/view/game_page_test.dart: GamePage (setUpAll)
00:03 +16 -2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/view/game_page_test.dart: GamePage is routable
00:03 +17 -2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/view/game_page_test.dart: GamePage is routable
00:03 +18 -2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/view/game_page_test.dart: GamePage is routable
00:03 +19 -2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/view/game_page_test.dart: GamePage is routable
00:03 +20 -2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/view/game_page_test.dart: GamePage is routable
00:03 +21 -2: ... TappingBehavior when tapped, starts playing the animation
00:03 +22 -2: ... TappingBehavior when tapped, starts playing the animation
00:03 +23 -2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/view/game_page_test.dart: GameView toggles mute button correctly
00:03 +24 -2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/view/game_page_test.dart: GameView toggles mute button correctly
00:03 +24 -2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/view/game_page_test.dart: GameView calls correct method based on state
00:03 +25 -2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/view/game_page_test.dart: GameView calls correct method based on state
00:03 +25 -2: /Users/alestiago/Developer/workspace/oss/very_good_flame_game/src/very_good_flame_game/test/game/view/game_page_test.dart: (tearDownAll)
00:03 +25 -2: Some tests failed.

Expected Behavior
All test should pass on the latest Flutter version (ie 3.16.0)
Additional Context

https://github.com/VeryGoodOpenSource/mockingjay/issues/64

I think this is closed


[Tests] Mark TypeRoundTrip as unsupported on use_os_stdlib.

When use_os_stdlib is set, we use the system Swift libraries, rather than the ones we've just built.  Older Swift libraries don't have some of the required functions to run this test, and since the test is supposed to be testing the library rather than the compiler, it makes sense to just mark it as unsupported in that configuration.
rdar://82171600

@swift-ci Please smoke test and merge

@swift-ci Please smoke test and merge