What is preferred? Single issue with list of related issues or multiple issues?

I opened

"psychiatrist" is not finding anything

at https://github.com/openstreetmap/id-tagging-schema/issues/778
Now with extra testing I discovered very similar ones:

psychology seems likewise missing
and psycholog
and dialysis (see https://wiki.openstreetmap.org/wiki/Tag:healthcare%3Ddialysis )
nurse ( https://wiki.openstreetmap.org/wiki/Tag:healthcare%3Dnurse )
OBGYN, ob/gyn should find gynecologist (which may be better named "obstetrician/gynecologist") - see https://osmus.slack.com/archives/C01BU04GW7L/p1675881005275539
"eye doctor" and "eye doctors" should find ophthalmologists and optometrists, I think
https://github.com/Helium314/SCEE/issues/408#issuecomment-1418611158 mentions dermatovenereology (no yet verified by me, linking so future me will remember it)

should I create separate issues for them?
Note to self: after any part of that issue or #778 is processed continue https://github.com/matkoniecz/Zazolc/commit/934d985d81ffbb7295c318b5958d214212485304

I'd say that a single issue for a bunch of closely related topics is fine in order to save you some work and not spam the issue inbox full. It also usually makes reviewing a bit more streamlined because typically background research tasks (e.g. looking up the OSM wiki, taginfo, ohsome stats, etc.) can be done in a single go for multiple related tags.
I'd however open a separate issue for different "tasks/problems", e.g. one issue for missing specializations of doctors, one issue for missing search terms, one issue for missing fields, etc.
That said, if you would however prefer to open individual issues for the various bullet points above, that's also fine for me.

thanks! So this is answered and I will open issues, maybe grouping multiple similar for what I listed here


Rust panic in 2.6.x

Describe the bug
Running Lage commands results in rust errors, e.g. when running npm run lint which calls lage lint, the lint pipelin in Lage config is just lint: {} I get this output:
thread '<unnamed>thread '' panicked at '<unnamed>Failed to read file: Failed to read file' panicked at '', Failed to read file: Failed to read filesrc\hasher.rs', :src\hasher.rs87::8748:
48stack backtrace:

thread '<unnamed>' panicked at 'Failed to read file: Failed to read file ',  src\hasher.rs 0:   : 87 :0x487fff1fbf7d45
 - napi_register_module_v1
   1:     0x7fff1faf773b - <unknown>
   2:     0x7fff1fbea7b1 - napi_register_module_v1
   3:     0x7fff1fbfa24b - napi_register_module_v1
   4:     0x7fff1fbf9e07 - napi_register_module_v1
   5:     0x7fff1fbfadbb - napi_register_module_v1
   6:     0x7fff1fbfa7f6 - napi_register_module_v1
   7:     0x7fff1fbfa749 - napi_register_module_v1
   8:     0x7fff1fbfa734 - napi_register_module_v1
   9:     0x7fff1fbfe255 - napi_register_module_v1
  10:     0x7fff1fbfe5b6 - napi_register_module_v1
  11:     0x7fff1fb060c4 - <unknown>
  12:     0x7fff1fb14475 - <unknown>
  13:     0x7fff1fc0aae6 - napi_register_module_v1
  14:     0x7fff1fb79510 - napi_register_module_v1
  15:     0x7fff1fb781fc - napi_register_module_v1
  16:     0x7fff1fbf714b - napi_register_module_v1
  17:     0x7fff75ec26ad - BaseThreadInitThunk
  18:     0x7fff76eca9f8 - RtlUserThreadStart
stack backtrace:
   0:     0x7fff1fbf7d45 - napi_register_module_v1
   1:     0x7fff1faf773b - <unknown>
   2:     0x7fff1fbea7b1 - napi_register_module_v1
   3:     0x7fff1fbfa24b - napi_register_module_v1
   4:     0x7fff1fbf9e07 - napi_register_module_v1
   5:     0x7fff1fbfadbb - napi_register_module_v1
   6:     0x7fff1fbfa7f6 - napi_register_module_v1
   7:     0x7fff1fbfa749 - napi_register_module_v1
   8:     0x7fff1fbfa734 - napi_register_module_v1
   9:     0x7fff1fbfe255 - napi_register_module_v1
  10:     0x7fff1fbfe5b6 - napi_register_module_v1
  11:     0x7fff1fb060c4 - <unknown>
  12:     0x7fff1fb19d6c - <unknown>
  13:     0x7fff1fb05d04 - <unknown>
  14:     0x7fff1fb14475 - <unknown>
  15:     0x7fff1fc0aae6 - napi_register_module_v1
  16:     0x7fff1fb79510 - napi_register_module_v1
  17:     0x7fff1fb781fc - napi_register_module_v1
  18:     0x7fff1fbf714b - napi_register_module_v1
  19:     0x7fff75ec26ad - BaseThreadInitThunk
  20:     0x7fff76eca9f8 - RtlUserThreadStart
stack backtrace:
   0:     0x7fff1fbf7d45 - napi_register_module_v1
   1:     0x7fff1faf773b - <unknown>
   2:     0x7fff1fbea7b1 - napi_register_module_v1
   3:     0x7fff1fbfa24b - napi_register_module_v1
   4:     0x7fff1fbf9e07 - napi_register_module_v1
   5:     0x7fff1fbfadbb - napi_register_module_v1
   6:     0x7fff1fbfa7f6 - napi_register_module_v1
   7:     0x7fff1fbfa749 - napi_register_module_v1
   8:     0x7fff1fbfa734 - napi_register_module_v1
   9:     0x7fff1fbfe255 - napi_register_module_v1
  10:     0x7fff1fbfe5b6 - napi_register_module_v1
  11:     0x7fff1fb060c4 - <unknown>
  12:     0x7fff1fab24fc - <unknown>
  13:     0x7fff1fb14752 - <unknown>
  14:     0x7fff1fc0aae6 - napi_register_module_v1
  15:     0x7fff1fb79510 - napi_register_module_v1
  16:     0x7fff1fb781fc - napi_register_module_v1
  17:     0x7fff1fbf714b - napi_register_module_v1
  18:     0x7fff75ec26ad - BaseThreadInitThunk
  19:     0x7fff76eca9f8 - RtlUserThreadStart

I'm currently using 2.6.2, and no commands work. on 2.6.1 the commands work but same error happens if I set up any custom workers
To Reproduce
Steps to reproduce the behavior:

Install lage 2.6.2 into a monorepo with existing npm run lint commands in each package
create a lage.config.js file containing:

module.exports = {
  pipeline: {
    lint: [],
  },
};

Run npm run lint
See error

Expected behavior
It runs the task in each project
Environment/Troubleshooting
Note, I'm on WIndows 11 (not 10 as envinfo thinks), and have tried on Node 16.20.0 and 18.15.0
  System:
    OS: Windows 10 10.0.22621
    CPU: (16) x64 AMD Ryzen 7 Microsoft Surface (R) Edition
    Memory: 3.06 GB / 15.45 GB
  Binaries:
    Node: 18.15.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.5.0 - C:\Program Files\nodejs\npm.CMD
  Managers:
    Maven: 3.8.1 - C:\dev\tools\maven\apache-maven-3.8.1\bin\mvn.CMD
  Utilities:
    Git: 2.36.1. - /mingw64/bin/git
  IDEs:
    VSCode: 1.78.2 - C:\Users\nicholj\AppData\Local\Programs\Microsoft VS Code\bin\code.CMD
  Languages:
    Bash: 4.4.23 - C:\Program Files\Git\usr\bin\bash.EXE
    Java: javac 17 - /c/Program Files/Common Files/Oracle/Java/javapath/javac
    Perl: 5.34.0 - C:\Program Files\Git\usr\bin\perl.EXE
  Browsers:
    Edge: Spartan (44.22621.1702.0), Chromium (113.0.1774.35)
    Internet Explorer: 11.0.22621.1

Version 2.6.5 does not appear to have these issues

I hit this as well. Clearing the cache fixed it for me. yarn lage cache --clear

I cannot reproduce this error, can you create a min-repro? Also, if 2.6.3 doesn't have these issues, then can you consider upgrading?

Appears to work in 2.6.6, maybe the cache was the issue

Ran into a panic on this exact line on upgrading lage from 2.7.8 -> 2.7.13. Seems unrelated to the lage cache, as our github builders start fresh with no pre-existing lage cache when they hit the issue.
I'm unable to min-repro, as it only triggers in our CI for whatever reason:
https://github.com/microsoft/ori/actions/runs/8622518854/job/23633806888?pr=1091


StateManagement issue

I've set stateManagement: false in PersistentTabView, but the state of each tab's screen are still being preserved(VideoHere)(edit: this issue has been fixed in newest beta version).
And weird things happend if I have set screenTransitionAnimation then every page will be rebuild when I press any bar item(VideoHere). I also tested stateManagement: true and  set screenTransitionAnimation will not make every page rebuild when I press any bar item.

If stateManagement: false is not bugged, then is there's any way I can refresh the page whenever I tap the specific bottom navigation item. For instance I have a login page which will check user's states to display different widget, but after I implement PersistentBottomNavBar to replace original bottom nav bar the login page is no longer re initialize when I tap the bar item.(edit: In newest beta version,  EVERY pages will still initialize then dispose immediately like second video above).

Hi, thank you for providing the videos, I can see the issues you are having. Sadly, with the code and configuration I could see in the videos, I could not reproduce the issue in your first point -> can you share a minimal code example that triggers the issue?

Hi, thank you for the reply. I create a minimal project to reproduce this bug, also record a video to show the issue.
Currently stateManagement: false whenever I navigate to any page, every "loaded" page will run initState() then suddenly dispose() check the video print log.
Videos below:
https://github.com/jb3rndt/PersistentBottomNavBarV2/assets/58425985/0cd51317-4191-4dcf-a655-728c8d06d8c6
Project libs and pubspec.yml:
code.zip
Version: persistent_bottom_nav_bar_v2: ^5.0.0-beta.6

Has this issue been resolved???

Sorry, yes this is fixed since version 5.0.0-beta.7.


move login/register into a form

It felt weird not having the expected behavior of enter to work on the login/register screen. I wrapped the inputs in a form and added an onSubmit handler. This way, both the actions of clicking the button and pressing enter will submit the post to login/register.

Thanks for contributing!!
I agree that enter not working is an unexpected behavior. Will review and merge hopefully late today!

Thanks again for contributing!

Not a problem, happy to contribute. You have a very nice boilerplate!


No array column but get "Array index out of range: 1048576"

Environment

OS version: Ubuntu 20.04.3 LTS
JDK version: 1.8.0_272
ClickHouse Server version: <IP_ADDRESS>
ClickHouse Native JDBC version: 2.5.6
(Optional) Spark version: 2.4
(Optional) Other components' version: N/A

Error logs
java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 1048576
	at net.jpountz.util.SafeUtils.checkRange(SafeUtils.java:24)

	at net.jpountz.util.SafeUtils.checkRange(SafeUtils.java:32)

	at net.jpountz.lz4.LZ4JavaSafeCompressor.compress(LZ4JavaSafeCompressor.java:141)

	at net.jpountz.lz4.LZ4Compressor.compress(LZ4Compressor.java:95)

	at com.github.housepower.jdbc.buffer.CompressedBuffedWriter.flushToTarget(CompressedBuffedWriter.java:75)

	at com.github.housepower.jdbc.serde.BinarySerializer.flushToTarget(BinarySerializer.java:112)

	at com.github.housepower.jdbc.connect.NativeClient.disconnect(NativeClient.java:153)

	at com.github.housepower.jdbc.ClickHouseConnection.close(ClickHouseConnection.java:141)

	at org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$.savePartition(JdbcUtils.scala:714)

	at org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$$anonfun$saveTable$1.apply(JdbcUtils.scala:838)

	at org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$$anonfun$saveTable$1.apply(JdbcUtils.scala:838)

	at org.apache.spark.rdd.RDD$$anonfun$foreachPartition$1$$anonfun$apply$28.apply(RDD.scala:980)

	at org.apache.spark.rdd.RDD$$anonfun$foreachPartition$1$$anonfun$apply$28.apply(RDD.scala:980)

	at org.apache.spark.SparkContext$$anonfun$runJob$5.apply(SparkContext.scala:2158)

	at org.apache.spark.SparkContext$$anonfun$runJob$5.apply(SparkContext.scala:2158)

	at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:90)

	at org.apache.spark.scheduler.Task.run(Task.scala:123)

	at org.apache.spark.executor.Executor$TaskRunner$$anonfun$10.apply(Executor.scala:409)

	at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1360)

	at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:415)

	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

	at java.lang.Thread.run(Thread.java:748)

Steps to reproduce
Using spark to ingest a large dataframe(> 100M rows) with many columns(>5000) into Clickhouse.
Here is the code I use:
df.write.format("jdbc").mode("append").
    option("driver","com.github.housepower.jdbc.ClickHouseDriver").
    option("url", jdbcUrl).
    option("user", "***").
    option("password", "***").
    option("dbtable", target_table).
    option("truncate", "true").
    option("batchsize", 100000).
    option("isolationLevel", "NONE").
    option("numPartitions", "128").save

Other descriptions
Based on this issue, this could be caused by inserting array column. But the dataframe I inserted contains only StringType, timestamp and LongType.
I've also tried to do some investigation on these source codes:

CompressedBuffedWriter.java
LZ4Compressor.java
SafeUtils.java

Unfortunately, I still couldn't find the cause.

Good search, can you try to modify the compression codes from:
 int res = lz4Compressor.compress(writtenBuf, 0, position, compressedBuffer, COMPRESSION_HEADER_LENGTH + CHECKSUM_LENGTH, compressedBuffer.length);

to
  int res = lz4Compressor.compress(writtenBuf, 0, position, compressedBuffer, COMPRESSION_HEADER_LENGTH + CHECKSUM_LENGTH, maxLen);

I think this may be the reason.

Re-ran the pipeline for the whole night with the new-built Jar, the problem seems to be persisted.
In fact, I found in the code of the latest release,  it used
int res = lz4Compressor.compress(writtenBuf, 0, position, compressedBuffer, 9 + 16);

Based on LZ4Compressor.java, it is an overloading method of compress:
public final int compress(byte[] src, int srcOff, int srcLen, byte[] dest, int destOff) {
    return compress(src, srcOff, srcLen, dest, destOff, dest.length - destOff);
}

So it's same as
int res = lz4Compressor.compress(writtenBuf, 0, position, compressedBuffer, 9 + 16, compressedBuffer.length - (9 + 16));

Since byte[] compressedBuffer = new byte[maxLen + 9 + 16]; , so Yes, maxDestLen must be maxLen. The code in master branch may need to be modified.
But still, we didn't find the root cause of "Array index out of range: 1048576"


WIP: Complete function inside trait impl

Implements #1046
Currently WIP because it doesn't trigger on fn yet, misses some whitespace and duplicates some helper functions.

Closing due to inactivity!


[Bug report]: Unable to manage voting power

Platform
Desktop
Version
2.1.2
Description
Firefly becomes unresponsive and blank after trying to open wallet - progress bar appears to finish loading.
Using ledger with all firmware and latest app.
Cannot print error logs or look at diagnostics because app becomes unresponsive.
Ubuntu desktop version.
Other wallets that are not linked to ledger work fine.

Expected behaviour
wallet should load and should be able to see balances. Worked fine on last version.
Actual behaviour
plug in ledger, wake ledger with pin, select shimmer app, Open firefly, select wallet, enter pin to log in - watch progress bars load and then see blank screen (attached image)
Can the issue reliably be reproduced?
Yes
Steps to reproduce the issue
No response
Operating System
Linux
Diagnostics
No response
Developer Profile
No
Profile Type
Hardware (Ledger)
Staking
None
Crash Status
White screen
Error Messages
No response
Error Logs
No response
Duplicate declaration

[X] I have searched the issues tracker this issue and there is none

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Thanks for the report, working on a fix

Fix released: https://github.com/iotaledger/firefly/releases/tag/desktop-2.1.3

not fixed!


Show Detailed Error Response from Browser Developer Tools

Is your feature request related to a problem? Please describe.
When I receive an Error during container creation the simple error codes reported are not useful and does not help solve the issue
Describe the solution you'd like
Display the detailed error that is available in Browser's developer tools
   -  Open developer tools in your browser (Ctrl+Shift+I usually),

    - Open network tab,

     -  Try whatever you were doing to get the error,

     - Click on the request that has an error

     - Click on 'Response' tab, there you'll see the actual docker/server error.
  This is clear information helpful in solving the problem and deploying container

Describe alternatives you've considered
N/A

Closing.  Related:  https://github.com/portainer/portainer/issues/8025
We are currently monitoring for further community feedback.
Thanks!


[Crash]: Farthest  Frontier Playtest v08.1 does not work with Melon Loader v0.5.7 Open-Beta any more = CTD

All of the following criteria must be met

[X] All Requirements must be installed.
[X] Full Latest.log file included. If no file exists then leave this unchecked and state so.

All of the following are optional to answer

[X] Tried reinstalling the Game.
[X] Tried reinstalling MelonLoader.
[X] Tried restarting PC.
[X] Was able to see the Start Screen.

Describe the issue.
Farthest  Frontier Playtest v08.1 does not work with Melon Loader v0.5.7 Open-Beta any more = CTD
For info only; anyone who so far has been choosing to run Farthest Frontier mods (from Nexus mods) using Melon Loader and successfully ran the game and all previous playtests with Melon Loader and mods from Nexus with NO ILL EFFECTs (in fact MANY improvements) be aware that this latest playtest v.08.01will NOT work if you have Melon Loader installed. It just crashes during load. Removing the mods folder has no effect at al. Melon Loader (latest version) crashes during its start up process and the game stops with it.
MelonLoader_23-01-19_20-58-34.157.log
[MelonLoader_23-01-19_20-59-02.296.log]
(https://github.com/LavaGang/MelonLoader/files/10461244/MelonLoader_23-01-19_20-59-02.296.log)
I guess this is a fundamental change somewhere in THIS new playtest or either Melon Loader needs an update or FF has chosen to nerf it so thatmods don't work  (I would hope that is not the case) if you have Melon Loader installed. My only solution to continue with mods was to stop using the playtest now and continue with the ordinary Farthest Frontier v 08.0 which still works perfectly...
Did you attach your log file?

[X] Yes, I attached my log file to the text box above.
[ ] No, I could not find a log file at {Game_Directory}\MelonLoader\Latest.log

unity 2021.3.15

Yeah they updated the unity version, use 0.6.0 alpha and it'll work.

For 0.6.0 alpha it's throwing an error when running the playtest:

[20:58:13.892] [Il2CppAssemblyGenerator] Error Generating Interop Assemblies!
System.NullReferenceException: Object reference not set to an instance of an object.
at Il2CppInterop.Generator.Contexts.AssemblyRewriteContext.RewriteTypeRef(TypeReference typeRef) in /home/runner/work/Il2CppInterop/Il2CppInterop/Il2CppInterop.Generator/Contexts/AssemblyRewriteContext.cs:line 133
at Il2CppInterop.Generator.Passes.Pass12FillTypedefs.DoPass(RewriteGlobalContext context) in /home/runner/work/Il2CppInterop/Il2CppInterop/Il2CppInterop.Generator/Passes/Pass12FillTypedefs.cs:line 33
at Il2CppInterop.Generator.Runners.InteropAssemblyGeneratorRunner.Run(GeneratorOptions options) in /home/runner/work/Il2CppInterop/Il2CppInterop/Il2CppInterop.Generator/Runners/InteropAssemblyGenerator.cs:line 79
at Il2CppInterop.Generator.Il2CppInteropGenerator.Start() in /home/runner/work/Il2CppInterop/Il2CppInterop/Il2CppInterop.Generator/Il2CppInteropGenerator.cs:line 30
at Il2CppInterop.Generator.Il2CppInteropGenerator.Run() in /home/runner/work/Il2CppInterop/Il2CppInterop/Il2CppInterop.Generator/Il2CppInteropGenerator.cs:line 47
at MelonLoader.Il2CppAssemblyGenerator.Packages.Il2CppInterop.ExecuteInterop() in D:\a\MelonLoader\MelonLoader\Dependencies\Il2CppAssemblyGenerator\Packages\Il2CppInterop.cs:line 97

Attempting to load a mod throws another error:

Failed to create an instance of the Melon.[21:00:48.913] System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
---> System.IO.FileNotFoundException: Could not load file or assembly 'Assembly-CSharp, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
File name: 'Assembly-CSharp, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'
at AutoFertilize.CompostAutomationService..ctor()
at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean wrapExceptions)
--- End of inner exception stack trace ---
at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean wrapExceptions)
at System.Activator.CreateInstance(Type type, Boolean nonPublic, Boolean wrapExceptions)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture)   at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at MelonLoader.MelonAssembly.LoadMelons() in D:\a\MelonLoader\MelonLoader\MelonLoader\Melons\MelonAssembly.cs:line 239

I would imagine the second error is due to the first one though.

Can I get a full log for that?

Latest.log

is er al een update

Farthest frontier should now work. No need to redownload anything, just launch the game with melonloader 0.6.0 and it should work.


Create a span with EmbraceSpanBuilder from factory

Goal

Testing

Release Notes

WHAT:
WHY:
WHO:

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#911
#910
#909
#908
#907  👈
#906
#903 : 1 other dependent PR (#867 )
#902
#897
#896
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @bidetofevil and the rest of your teammates on  Graphite


Looking up a deactivated widget's ancestor is unsafe. RESCUE NEEDED!!!!

Expected results:
I have two pages, HomePage and OtherPage.

When the app starts, it goes  homepage.
In homepage, in init function, it checks if userId exists in DB.
Then it shows the other page if there is no userId
After some form fill up, i want the page to go back to the homepage.

Actual results:
After filling up the form and pressing the button to trigger to go the homepage, it shows the following error.
Unhandled Exception: Looking up a deactivated widget's ancestor is unsafe.
E/flutter (20919): At this point the state of the widget's element tree is no longer stable.
E/flutter (20919): To safely refer to a widget's ancestor in its dispose() method, save a reference to the ancestor by calling dependOnInheritedWidgetOfExactType() in the widget's didChangeDependencies() method.

I have tried checking the issues and tried almost everything written in issues or stack overflow but still am not being able to solve it.
  Here is the code navigating to Home Screen and vice versa.
Navigator.pushNamed(context, '/home'); in the others page.
Navigator.pushNamed(context, '/others');  in the home page.

s] E/flutter ( 4419): [ERROR:flutter/lib/ui/ui_dart_state.cc(199)] Unhandled Exception: Looking up a deactivated widget's ancestor is unsafe.
[        ] E/flutter ( 4419): At this point the state of the widget's element tree is no longer stable.
[        ] E/flutter ( 4419): To safely refer to a widget's ancestor in its dispose() method, save a reference to the ancestor by calling dependOnInheritedWidgetOfExactType() in
the widget's didChangeDependencies() method.
[        ] E/flutter ( 4419): #0      Element._debugCheckStateIsActiveForAncestorLookup.<anonymous closure> (package:flutter/src/widgets/framework.dart:3944:9)
[        ] E/flutter ( 4419): #1      Element._debugCheckStateIsActiveForAncestorLookup (package:flutter/src/widgets/framework.dart:3958:6)
[        ] E/flutter ( 4419): #2      Element.findAncestorStateOfType (package:flutter/src/widgets/framework.dart:4005:12)
[        ] E/flutter ( 4419): #3      Navigator.of (package:flutter/src/widgets/navigator.dart:2727:40)
[        ] E/flutter ( 4419): #4      Navigator.pushNamed (package:flutter/src/widgets/navigator.dart:1735:22)
[        ] E/flutter ( 4419): #5      NextButton.build.<anonymous closure> (package:linkster/screens/userName/widgets/next_button.dart:46:23)
[        ] E/flutter ( 4419): <asynchronous suspension>
[        ] E/flutter ( 4419):

[✓] Flutter (Channel stable, 2.2.2, on macOS 11.3.1 20E241 darwin-x64, locale ja-JP)
    • Flutter version 2.2.2 at /Users/rujenshakya/development/flutter
    • Framework revision d79295af24 (3 months ago), 2021-06-11 08:56:01 -0700
    • Engine revision 91c9fc8fe0
    • Dart version 2.13.3

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/rujenshakya/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Users/rujenshakya/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5.1, Build version 12E507
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] VS Code (version 1.60.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.26.0

@Ruzen1
Not sure how your code structure is, but maybe try to separate your widget code to standalone method and see if it helps.
Also try to upgrade to latest stable and see if issue still persists.

@Ruzen1
From the info you gave, I guess you are calling the Navigator.push in the dispose() method of others page. If I remember correctly, dispose method is called after the previous screen is displayed. I don't think you need to call Navigator.pushNamed(context, '/home'); as the pages are stacked on top of each other. And on pressing back, it will just pop the others page.


[BUG] HTTP status code changed on 2.3.0 on querying for non-existing index

How can one reproduce the bug?
curl -v -s -XPOST "http://localhost:9200/_plugins/_sql" -H 'Content-Type: application/json' -d "{\"query\": \"select * from non-existed\"}"

OpenSearch 2.2.1:
HTTP/1.1 400 Bad Request
{
  "error": {
    "reason": "Error occurred in OpenSearch engine: no such index [non-existed]",
    "details": "org.opensearch.index.IndexNotFoundException: no such index [non-existed]\nFor more details, please send request for Json format to see the raw response from OpenSearch engine.",
    "type": "IndexNotFoundException"
  },
  "status": 404
}

2.3.0:
HTTP/1.1 503 Service Unavailable
{
  "error": {
    "reason": "Error occurred in OpenSearch engine: no such index [non-existed]",
    "details": "org.opensearch.index.IndexNotFoundException: no such index [non-existed]\nFor more details, please send request for Json format to see the raw response from OpenSearch engine.",
    "type": "IndexNotFoundException"
  },
  "status": 404
}

Payloads are same, but status codes are different.

This is probably because the approach of getting index mapping is changed. Previously the code on each OpenSearch node just read status in ClusterState object locally. In this way, we can avoid blocking operation during parsing, analyzing and planning and make all running on NIO thread. However, this is changed to calling OpenSearch API due to some other issue.
Previously index not found exception is thrown and handled by https://github.com/opensearch-project/sql/blob/2.2/legacy/src/main/java/org/opensearch/sql/legacy/plugin/RestSqlAction.java#L165 in NIO thread. Now it's thrown from worker thread and handled by https://github.com/opensearch-project/sql/blob/2.2/legacy/src/main/java/org/opensearch/sql/legacy/plugin/RestSQLQueryAction.java#L177 without isClientError check. We may need to check here as we move everything to worker thread.

Test skipped for change: https://github.com/opensearch-project/sql/blob/63c51377fbe6d3bbc0922242985b08f15801adc0/sql-cli/tests/test_opensearch_connection.py#L42

I found similar issue in metrics. In legacy engine, index not found is treated as client error. However, the issue reported here cause it treated as server error in v2 engine which may cause wrong alarm in monitor system from user side.


<Header as separated component

Hi! Could you pls help me to expose <header block in a separated component and just import it where it is necessary.
Now  block is copied in the each screen of the app

Yes, that is on our list for the upcoming release.

Fixed with v2.0


python3Packages.pydot_ng: moving pytest and mock to checkInputs

Motivation for this change
Fixing https://hydra.nixos.org/build/98961910
Disabling not working tests, given this is an archived project
by upstream, rest is passing.
Things done

[ ] 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)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @bcdarwin

@GrahamcOfBorg build pythonPackages.pydot_ng python3Packages.pydot_ng

@jonringer I was just trying to fix the broken build. Would you like to take over the package? @bcdarwin has been unresponsive for some time.

@mmahut I'll bump it, but I don't really have any interest in the package itself


Ability to specify packet payload

We need a way to specify the contents of the packet.  Say a packet is 1024 bytes and all I've done is added Ethernet and IP headers to it.  My understanding is that the rest of the packet is not specified in the API and will be implementation dependent.  Do we need a way for the user to describe the contents of the rest of the packet?

Custom packet header is meant to be used anywhere for as many times as you want.
Flow(name='custom 128 byte payload all zeroes',
    packet=[
	    Header(Ethernet()),
		Header(Ipv4()),
		Header(Custom(bytes='00' * 128))
	])


Segmentation fault after update to 4.11.1

After we updated to Gem version to 4.11.1 to work with Ruby 2.7.1 we started seeing sporadic segfaults, usually on shut downs of old workers while we spin up new ones in the deploy process. Seeing this in both when we run in heroku or docker on AWS, mostly around sidekiq swarm.
Upgrading to 4.12.1 makes the problem much worse, with the segfaults happening once every few seconds after the upgrade vs at the end of deploys (couple of times a day). The stack trace for the 4.12.1 are much more exotic, longer and difficult to understand.
OS: Heroku or Debian GNU/Linux 10 in Docker container on AWS
Ruby: ruby 2.7.1p83 + Rails <IP_ADDRESS> (with bootsnap 1.4.5)
Log
TID-1bno INFO: Booting Sidekiq 5.2.7 with redis options {:id=>"Sidekiq-server-PID-4", :url=>"redis://h:REDACTED@ec2-xxx.compute-1.amazonaws.com:xxx"}
Oct 28 23:58:06 app[worker] info /app/vendor/bundle/ruby/2.7.0/gems/sidekiq-ent-1.8.1/lib/sidekiq-ent/swarm.rb:191: [BUG] Segmentation fault at 0x0000000000000480
Oct 28 23:58:06 app[worker] info ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-linux]
Oct 28 23:58:06 app[worker] info
Oct 28 23:58:06 app[worker] info -- Machine register context ------------------------------------------------
Oct 28 23:58:06 app[worker] info  RIP: 0x00007f7d8d83ff76 RBP: 0x0000000000000000 RSP: 0x00007f7d5abfa650
Oct 28 23:58:06 app[worker] info  RAX: 0x0000000000000000 RBX: 0x00007f7d51386bb8 RCX: 0x00007f7d5abfaeb8
Oct 28 23:58:06 app[worker] info  RDX: 0x00007f7d7b7eeb90 RDI: 0x00007f7d51386bb8 RSI: 0x0000000000000013
Oct 28 23:58:06 app[worker] info   R8: 0x0000000000000000  R9: 0x00007f7d57407c60 R10: 0x000000000801ce00
Oct 28 23:58:06 app[worker] info  R11: 0x0000000000000000 R12: 0x0000000000000020 R13: 0x00007f7d8cbb5320
Oct 28 23:58:06 app[worker] info  R14: 0x00007f7d8cbb5520 R15: 0x00007f7d8cbb53a0 EFL: 0x0000000000010206
Oct 28 23:58:06 app[worker] info
Oct 28 23:58:06 app[worker] info -- C level backtrace information -------------------------------------------
Oct 28 23:58:06 app[worker] info /app/vendor/ruby-2.7.1/bin/../lib/libruby.so.2.7(rb_vm_bugreport+0x7ce) [0x7f7d8d9fc02e] vm_dump.c:755
Oct 28 23:58:06 app[worker] info /app/vendor/ruby-2.7.1/bin/../lib/libruby.so.2.7(rb_bug_for_fatal_signal+0xe7) [0x7f7d8d81b207] error.c:658
Oct 28 23:58:06 app[worker] info /app/vendor/ruby-2.7.1/bin/../lib/libruby.so.2.7(sigsegv+0x4b) [0x7f7d8d96007b] signal.c:946
Oct 28 23:58:06 app[worker] info /lib/x86_64-linux-gnu/libc.so.6(0x7f7d8d39dfd0) [0x7f7d8d39dfd0]
Oct 28 23:58:06 app[worker] info /app/vendor/ruby-2.7.1/bin/../lib/libruby.so.2.7(ruby_sized_xfree+0x3) [0x7f7d8d83ff76] gc.c:10164
Oct 28 23:58:06 app[worker] info /app/vendor/ruby-2.7.1/bin/../lib/libruby.so.2.7(ruby_xfree) gc.c:10171
Oct 28 23:58:06 app[worker] info /lib/x86_64-linux-gnu/libpthread.so.0(__nptl_deallocate_tsd.part.5+0x98) [0x7f7d8c9a1408]
Oct 28 23:58:06 app[worker] info /lib/x86_64-linux-gnu/libpthread.so.0(0x781b) [0x7f7d8c9a281b]
Oct 28 23:58:06 app[worker] info /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f7d8d480a3f]
Oct 28 23:58:06 app[worker] info
Oct 28 23:58:06 app[worker] info -- Other runtime information -----------------------------------------------

sorry to hear
Is it only the sidekiq workers that segfault or the whole app?
Only on shutdown?
Would you mind sending me more info so that I can try to reproduce and fix?

Full stack traces for both cases 4.11.1 and 4.12.1
Gemfile and Gemfile.lock
Probably best by email<EMAIL_ADDRESS>

I'm tempted to close this, because I'm not able to reproduce
Are you using grpc? The use of grpc is the main difference in the c-library

I'm tempted to close this, because I'm not able to reproduce
Are you using grpc? The use of grpc is the main difference in the c-library

No we’re not. I’ll have to make time to sit down and mail you the stack trace. Just got busy and it’s pretty long and pretty hard to figure out where to start and end

From: Maia Engeli<EMAIL_ADDRESS>Sent: Thursday, January 21, 2021 4:13:55 PM
To: appoptics/appoptics-apm-ruby<EMAIL_ADDRESS>Cc: Ike<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [appoptics/appoptics-apm-ruby] Segmentation fault after update to 4.11.1 (#111)
I'm tempted to close this, because I'm not able to reproduce
Are you using grpc? The use of grpc is the main difference in the c-library
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/appoptics/appoptics-apm-ruby/issues/111#issuecomment-764945465, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAACGHNUYQMBLSZTWP4GW5LS3CKJHANCNFSM4TDHIA6Q.

No we’re not. I’ll have to make time to sit down and mail you the stack trace. Just got busy and it’s pretty long and pretty hard to figure out where to start and end

From: Maia Engeli<EMAIL_ADDRESS>Sent: Thursday, January 21, 2021 4:13:55 PM
To: appoptics/appoptics-apm-ruby<EMAIL_ADDRESS>Cc: Ike<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [appoptics/appoptics-apm-ruby] Segmentation fault after update to 4.11.1 (#111)
I'm tempted to close this, because I'm not able to reproduce
Are you using grpc? The use of grpc is the main difference in the c-library
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/appoptics/appoptics-apm-ruby/issues/111#issuecomment-764945465, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAACGHNUYQMBLSZTWP4GW5LS3CKJHANCNFSM4TDHIA6Q.

ok, no worries, I'll wait ...

ok, no worries, I'll wait ...

I'm going to go ahead and close this. getting the entire stack trace is just a massive pain with our logging system, (hard to know where the stack starts and ends) and we're going to be moving off appoptics in a few days.
thanks for the helping out!

I'm going to go ahead and close this. getting the entire stack trace is just a massive pain with our logging system, (hard to know where the stack starts and ends) and we're going to be moving off appoptics in a few days.
thanks for the helping out!


Add inline comment syntax to liquid

This PR adds support for {% # inline comment %} syntax in Liquid.

Never mind, I should read READMEs 😛 this repository no longer accepts PR, at least not until v2 releases (if ever)


Microbadger upgrade

fix #339

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2
- Added 1

See the complete overview on Codacy


Immutable block header

This PR is motivated by the issue https://github.com/rust-bitcoin/rust-bitcoin/issues/52
Profiler showed that significant time was wasted recomputing bitcoin_hash for block headers.
After this change BlockHeader is immutable and its hash is pre-computed. The time inserting into in-memory blockchain is less than half of before.
2018-03-09 15:37:57 INFO  [bitcoin_spv::node] loading headers from database...
2018-03-09 15:37:57 INFO  [bitcoin_spv::node] reading headers ...
2018-03-09 15:38:37 INFO  [bitcoin_spv::node] building in-memory header chain ...
2018-03-09 15:39:16 INFO  [bitcoin_spv::node] loaded 512744 headers from database

closing this, rather a target for a new blockchain crate


Alphabetize metric dropdown

Alphabetize metric dropdown in explore and widen the dropdown menu to prevent wrapping, as per card.

 Alphabetize and widen the Trends dropdown menu


chore: Prepare v1.0.0 release

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #
Special notes for your reviewer:

Codecov Report

Merging #641 (3dd30ad) into main (7379955) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #641   +/-   ##
=======================================
  Coverage   15.43%   15.43%
=======================================
  Files          13       13
  Lines        1600     1600
=======================================
  Hits          247      247
  Misses       1325     1325
  Partials       28       28

Flag
Coverage Δ

unittests
15.43% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@ashnamehrotra  can we use the github action for this?

@sozercan it would create another release branch https://github.com/Azure/eraser/branches would we delete that one?

opened #642 for tracking release pr block
i think this pr needs to target release-1.0 branch

closing for #643 (pr to target release-1.0 branch)


remove config-trusted-resources

Changes
This commit removes config-trusted-resources. The deprecation is announced in release v0.45. The reason of removing is that config-trusted-resources is used to store public keys for verificaiton but Verification Policy has already covered all the functionalities and has more advanced features. Since there are not any other fields in trusted-resources-config we decided to remove it.
Closes #5852
Signed-off-by: Yongxuan Zhang<EMAIL_ADDRESS>
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs included if any changes are user facing
[ ] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
config-trusted-resources

/kind misc


(auto?)update the screenshots in the readme

just did an update for 1.0 but maybe auto update or some script like release/updateFlags.sh would be good


release candidate 1

1.8.1rc1
please may I have a tag following this commit?

Thanks for your patience & diligence @marqh !

Thanks for your patience & diligence

my pleasure :smile:


Improved the new campground page

📋 Description

Improved the new campground page

Hi @Vignesh025 you can merge it and add the same labels as issue #244 .Thanks!

Hey @itsadi-24,

here the green outline is not fully covering the box

completely removed the green line,the issue was caused because on getting focused the input boxes get green border,but as '₹' not being a part of input box was causing the issue.
@Vignesh025 @Sowmiyajayakumar now you can merge

Thankyou for Contributing!


passkeys/js/bootstrap-toggle.min.js.map not included

As of Django 4.0, Manifest storage searches for map files if they are referenced in the minified file.
Running collect static with Django 4.2.1 I get the following error:
 ValueError: The file 'passkeys/js/bootstrap-toggle.min.js.map' could not be found with <django.contrib.staticfiles.storage.ManifestStaticFilesStorage object at 0x7f4a1e289650>.
Can this map file either be included, or the reference to the map file removed from the bottom of the minified file?

FYI: I have left review comments on #27 in order to also fix this issue.


admin proto

Codecov Report

Merging #106 (9ca0a9b) into master (73c6f18) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #106   +/-   ##
=======================================
  Coverage   86.56%   86.56%
=======================================
  Files           3        3
  Lines          67       67
=======================================
  Hits           58       58
  Misses          8        8
  Partials        1        1

Flag
Coverage Δ

unittests
86.56% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Feature request: command palette support

Suppport for entering commands in the command palette via voice.
Not sure if all the vscode api is there but this would be great

@tmacwill
This is pretty important for workflow, but it would be great if we could just vocalize command shortcuts automagically.
Consider the following:
A vscode keybindings.json:
  [{
    "key": "cmd+p",
    "command": "vscodex.predict"
  }]

We could augment this to:
  [{
    "key": "cmd+p",
    "command": "vscodex.predict",
    "voice": "predict"
  }]

So, any time I say "predict", the command is run, and I get my OpenAI prediction!

Alright, I implemented this:
// setup:
// cd ~/.serenade/scripts
// npm install --save jsonc
// create `custom.js` with the contents below:
// add a "voice" property to any of your keybindings.json in vscode

custom.js
const command = "command";
const option = "option";
const shift = "shift";
const control = "control";
const alt = "alt";

let jsonc = require('jsonc');

let fs = require('fs');
let settings = fs.readFileSync(`${process.env.HOME}/Library/Application Support/Code/User/keybindings.json`).toString();
settings = jsonc.parse(settings);

const press = async (shortcut, api) => {
  const [key, modifiers] = shortcut;
  await api.pressKey(key, modifiers);
 };

settings.forEach(setting => {
  if(setting.voice){
    serenade.app("code").command(setting.voice, async (api, matches) => {
      await press(["t", [command]], api);
      await api.typeText(`> ${setting.command}`);
      setTimeout(async ()=>{
        await press(["enter", [command]], api);
      }, 2000);
    });
  }
});

this is awesome—thanks for posting! adding the voice key to the VS Code keybindings file is super cool.
since this issue has been opened, we've also added the evaluateInPlugin API method: https://serenade.ai/docs/api/#reference. I think you should be able to say:
api.evaluateInPlugin("vscodex.predict");

and that will execute the vscodex.predict command within VS Code, which should be a bit faster since you don't have to wait on the VS Code UI. let me know if that works for you, and happy to help debug + fix if not!

Thanks @tmacwill ! One thing I might look into is arguments, ex "predict 100", where 100 is passed as an argument to the vscode command. Note sure, api.evaluateInPlugin handles that?
Updated version:
// setup:
// cd ~/.serenade/scripts
// npm install --save jsonc
// create `custom.js` with the contents here:
// add a "voice" property to any of your keybindings.json in vscode
let jsonc = require('jsonc');
let fs = require('fs');
let settings = fs.readFileSync(`${process.env.HOME}/Library/Application Support/Code/User/keybindings.json`).toString();
settings = jsonc.parse(settings);

settings.forEach(setting => {
  if(setting.voice){
    serenade.app("code").command(setting.voice, async (api, matches) => {
      api.evaluateInPlugin(setting.command);
    });
  }
});

ah gotcha, good point. evaluateInPlugin uses the vscode.commands.executeCommand function from the VS Code API (https://code.visualstudio.com/api/references/vscode-api). it looks like that function can take arguments as well, so I think we should be able to add corresponding support to the Serenade API.

@tmacwill that would be really great, I'll post a repo with the update, once the API changes are out. I love it, gonna show this to some co-workers


Update About Us, UG and DG

Codecov Report

Merging #49 (59533e1) into master (b92d6b3) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #49   +/-   ##
=========================================
  Coverage     70.67%   70.67%
  Complexity      481      481
=========================================
  Files            85       85
  Lines          1514     1514
  Branches        161      161
=========================================
  Hits           1070     1070
  Misses          400      400
  Partials         44       44

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 b92d6b3...59533e1. Read the comment docs.


any reason for this?

i installed the bot with your tutorial and everytime it want to post a streaming message, this happens in console:

The error message suggests that some field in the live embed is empty when it shouldn't be. Could be a stream with an empty title, possibly. Are you still experiencing this / do you happen to know why this may have happened for this particular stream notification?

The error message suggests that some field in the live embed is empty when it shouldn't be. Could be a stream with an empty title, possibly. Are you still experiencing this / do you happen to know why this may have happened for this particular stream notification?


Saving .vscode/task.json should always refresh task list

Testing #19057

VSCode Version: Code - Insiders 1.9.0-insider (4265f5e35cb3ea8ba7e0cf6b14ec606b6f8647ea, 2017-01-24T10:29:13.076Z)
OS Version: Darwin x64 16.3.0
Extensions:

Extension
Author
Version

EditorConfig
EditorConfig
0.3.4

lorem-ipsum
Tyriar
1.0.0

sort-lines
Tyriar
1.2.0

theme-glacier
Tyriar
0.0.10

vscode-svgviewer
cssho
1.3.0

gitlens
eamodio
1.4.3

git-project-manager
felipecaputo
1.0.1

md-navigate
jrieken
0.0.1

vscode-scss
mrmlnc
0.6.0

seti-icons
qinjia
0.1.3

I have the following file saved, no errors show up but the task list still shows the old values, even when I close and open the file.
{
    // See https://go.microsoft.com/fwlink/?LinkId=733558
    // for the documentation about the tasks.json format
    "version": "0.1.0",
    "command": "npm",
    "isShellCommand": true,
    "showOutput": "always",
    "suppressTaskName": true,
    "_runner": "terminal",
    "tasks": [
        {
            "taskName": "install",
            "args": ["install"]
        },
        {
            "taskName": "lint",
            "args": ["run", "tslint"]
        },
        {
            "taskName": "test",
            "args": ["run", "test"]
        },
        {
          "taskName": "watch",
          "args": ["run", "dev"],
          "isBuildCommand": true
        }
    ]
}

After creating this issue the list refreshed (window focus?)

This now works for the _runner -> terminal. It does not for the old output task runner mainly because I can't hot swap the configuration due to state assigned to a running task. Since the output runner will fade out no further action is planned.

@dbaeumer Do you have verification steps?

@aeschli sorry for not adding them
{
    "version": "0.1.0",
    "echoCommand": true,
    "_runner": "terminal",
    "tasks": [
        {
            "taskName": "tsc",
            "command": "tsc -w",
            "isShellCommand": true,
            "isBackground": true,
            "problemMatcher": "$tsc-watch",
            "isBuildCommand": true
        },
        {
            "taskName": "dir",
            "command": "dir",
            "isShellCommand": true
        }
    ]
}

Start the watch task by pressing Ctrl+Shift+B.
Change the name of the dir task to something else.
F1 > Run Task  should show the new name.

Does "verified" mean still broken?
I am using the "terminal" runner and changes to tasks.json are not reflected unless I close/open the folder, or exit/restart Code.  Old versions of Code would auto update but I can't remember when this broke.
Software:

VS Code 1.13.1
Windows 10

@mattflix verified means it was testing in the version it was released in (Jan 2017). If you are seeing this again please create a new issue and reference this one.


Error running superset in docker with typing-extensions

We are unable to run superset with docker.
Steps to reproduce
Dockerfile:
FROM apache/superset
USER root
RUN pip install mysqlclient
RUN pip install elasticsearch-dbapi
RUN pip install psycopg2-binary
RUN pip install snowflake-sqlalchemy
RUN pip install "PyAthena>1.2.0"
RUN pip install pydruid
RUN pip install sqlalchemy-redshift
USER superset

Followed by commands
docker build -t org/superset2 .
docker run -d -p 8080:8088 --name superset org/superset2
docker exec -it superset superset fab create-admin \
              --username admin \
              --firstname Superset \
              --lastname Admin \
              --email<EMAIL_ADDRESS>\
              --password admin

Produces error
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 568, in _build_master
    ws.require(__requires__)
  File "/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 886, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 777, in resolve
    raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (typing-extensions 4.4.0 (/usr/local/lib/python3.8/site-packages), Requirement.parse('typing-extensions<4,>=3.10'), {'apache-superset'})

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/bin/superset", line 33, in <module>
    sys.exit(load_entry_point('apache-superset', 'console_scripts', 'superset')())
  File "/usr/local/bin/superset", line 25, in importlib_load_entry_point
    return next(matches).load()
  File "/usr/local/lib/python3.8/importlib/metadata.py", line 77, in load
    module = import_module(match.group('module'))
  File "/usr/local/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 843, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/app/superset/cli/main.py", line 28, in <module>
    from superset.cli.lib import normalize_token
  File "/app/superset/cli/lib.py", line 20, in <module>
    from superset import config
  File "/app/superset/config.py", line 46, in <module>
    import pkg_resources
  File "/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3243, in <module>
    def _initialize_master_working_set():
  File "/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3226, in _call_aside
    f(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3255, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 570, in _build_master
    return cls._build_from_requirements(__requires__)
  File "/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 583, in _build_from_requirements
    dists = ws.resolve(reqs, Environment())
  File "/usr/local/lib/python3.8/site-packages/pkg_resources/__init__.py", line 772, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'typing-extensions<4,>=3.10' distribution was not found and is required by apache-superset

Looks related to https://github.com/apache/superset/issues/20863#issuecomment-1252238140

It is not a bug.We were able to run Superset with Docker.
Screenshots:-

Superset deploys with Docker generally.  I agree that your link to that other comment looks relevant, that is, that this is resulting from one of the packages you have added to your Dockerfile.
Did you resolve this problem?

Hi @sfirke ,
I didn't add any packages specifically,I just followed whatever @vladaman provided the steps to reproduce the bug.
After followed the steps I didn't get any error.FYI I added screenshots in above comment.Please go through...

Doesn't look like we're seeing a response from the original author, and the issue is neither clear nor reproducible. Closing, but open to further discussion.


Provide a way to setup a separate frontend for proxy stats

Hi, I'm testing the proxy behind a proxy-protocol enabled LB (AWS ELB) and ran into an issue. Since the stats configuration is setup in the default frontend, scrapers of it would need to support using proxy-protocol when communicating to it. I don't think this is very common or easy to do. So It'd be nice if the possibility of defining a separate frontend (basically another port) which contained only the stats endpoint would be a nice addition. "Bonus points" if the default haproxy-exporter configuration reacted properly.

The implementation passed automated tests but I did not have time to try it out on a functional level. Can you please give me a hand and test the tag beta and report back whether it works as expected? You'll need to define environment variable STATS_PORT.

You seem to have missed a blank line there somewhere: ```
backend stats
mode http
stats enable
stats refresh 30s
stats realm Strictly\ Private
stats uri /proxyStats
stats auth admin:admin
frontend services
bind *:80 accept-proxy

haproxy_server_weight{backend="webs_www-be80_0",server="webs_www"} 1
but otherwise, it looks fine.

Empty lines between frontends and backends is mostly for cosmetic reasons. HAProxy ignores them. I put to my backlog the change to separate them further.
I made a release 17.09.06-7 with the changes required for this FR. Please reopen this issue if you experience any problems.


cherry-pick fix append_data_by_selector_impl reserve too mush useless memory (#39581)

Proposed changes
cherry-pick from master #39581

run buildall


Feature request: allow user to select which item to be downloaded

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

WARNING
All invalid issues will be rejected!!

Before going further

If your problem is a bug with youtube-dl or a request for new site support please report it here

Make sure you are using the latest yt-dlg version (Click the Settings icon and then About to view the current version)

Make sure you are using the latest youtube-dl version (Click the Settings icon and then Update to update to the latest youtube-dl version)

Make sure you searched the bugtracker for similar issues including closed ones

Make sure to read the FAQs file

[x] I think my problem is NOT with youtube-dl
[x] I've verified and i assure that I'm running yt-dlg 1.X.Y
[x] I assure that i am using the latest version of youtube-dl
[x] Searched bugtracker
[x] I've read the FAQs file

What is the purpose of your issue?

[ ] Bug report
[X] Feature request (request for a new functionality)
[ ] Question
[ ] Other

Please remove any sections between (---) if they are not related to your issue

Bug report
If the problem occurs when downloading a URL please provide the full verbose output as follows:

Restart yt-dlg
Go to Options > Extra tab
Enable Debug youtube-dl
Go to Options > Advanced tab and Clear your log content
Try to download the URL
Copy the whole log content and insert it between the ``` part below

delete me and insert your log content here

What operating system do you use ?
Windows 10
List of actions to perform to reproduce the problem:

..Paste a youtube channel link.
..Press "Add"
..Press "Start"

What is the expected behaviour ?

YT-DLG should display all of the listed clips of a channel (if the user paste the URL of a channel) with a check box of each item.
User can download the selected items to download
The channel could be update on daily basis to see if any newer video available.
Allow users to download newer video clips if possible. Allow an option for the program to update the channel new items (alike RSS news reader or podcast).

What happens instead ?
YT-DLG display only a link, the progress was only known as a tip when user hovers the mouse on the link. What item is being downloaded only known when user navigates to download folder. There is no progress or selectable things revealed.

Feature request (request for a new functionality)
I believe that this functionality is not currently available in the program. I have read the Todo section.
Please make sure that the requested feature is NOT already in the TODO list

[X] I've verified and i assure that my requested feature is NOT in the TODO list

What operating system do you use ?
Windows 10.

Thank you very much for considering the proposal

can it be added or it isnt even updated anymore? 🦓


DB: Denver SIDs & STARs dead links

Heya,
The links to airport charts from pages like https://zdvartcc.org/airports/DEN are dead links. Clicking "POWDR ONE" links to https://aeronav.faa.gov/d-tpp/2304/09077POWDR.PDF, when it should probably link to https://aeronav.faa.gov/d-tpp/2307/09077POWDR.PDF.

Means your chart parser did not complete successfully on the day the cycles changed and you'll need to review the logs of the job to determine why.

Looks good


No known route from 'multiband' to 'srgb' when using composite operation

Description
When trying to use composite operation in lua-vips, I'm getting an error about color space conversion: "no known route from 'multiband' to 'srgb'". This same operation works fine in pyvips.
Minimal Example
Here's a comparison between working pyvips code and problematic lua-vips code:
Working Python code (pyvips):
shadow_alpha = image[-1]
shadow_rgb = shadow_alpha.new_from_image([100, 100, 100])
shadow = shadow_rgb.bandjoin(shadow_alpha)
background = shadow.new_from_image([255, 255, 255])
final = background.composite([shadow, image], "over",
x=[offset1, offset2],
y=[offset1, offset2])

Problematic Lua code (lua-vips):
local shadow_alpha = img:extract_band(img:bands() - 1)
local shadow_rgb = shadow_alpha:new_from_image({100, 100, 100})
local shadow = shadow_rgb:bandjoin(shadow_alpha)
local background = shadow:new_from_image({255, 255, 255})
local result = background:composite({shadow, img}, "over", {
x = {offset1, offset2},
y = {offset1, offset2}
})

Error Message
Image core functions border effects should add shadow with custom dimensions
/opt/homebrew/share/lua/5.4/vips/voperation.lua:239: unable to call composite
vips_colourspace: no known route from 'multiband' to 'srgb'
Expected Behavior
The lua-vips code should work the same way as the pyvips code, automatically handling color space conversion when using composite operation.
Question
Is this a known limitation in lua-vips? Or is there a different way to handle color space conversion in lua-vips compared to pyvips?

Using a sample png image with some transparency the Lua code worked just fine (tested with Lua 5.3, lua-vips 1.1-11 and libvips 8.16). Can you share an image where it doesn't work?

The annoying "no known route" message was quite common with libvips 8.12 (I think?), but should be very rare with current libvips.
Perhaps your lua-vips install is picking up an older libvips version?

I apologize for the false alarm. The issue was with my auto-generated test image using vips.Image.black(), not with lua-vips itself. When using real image files (JPG/PNG), everything works as expected.
Thanks for your help. Closing this issue.


Hswish via ReLU

Which formula is preferred?  f(x) = x * min(max(x+3), 0), 6) / 6 or f(x) = x * min(ReLU(x+3), 6) / 6

Use ReLU; but also, note that the oplib relu has a max_value parameter so you can simplify this further

Also if you're working on Hswish assign https://github.com/plaidml/openvino/issues/62 to yourself so no one duplicates work


Fix copyWith's return type.

This is an attempt to fix an issue I am seeing in dart-services: https://github.com/dart-lang/dart-pad/issues/1712

@sigurdm as the fix is add yet another typecast I'm curious what sort of test you would like over this code?
I'm also conscious that I am patching the usage of a call point that is slated to go away, as indicated by the deprecated_member_use on that line, so I'm figuring this code will get deleted sooner or later.

@sigurdm as the fix is add yet another typecast I'm curious what sort of test you would like over this code?
I'm also conscious that I am patching the usage of a call point that is slated to go away, as indicated by the deprecated_member_use on that line, so I'm figuring this code will get deleted sooner or later.

Just a test that fails before (probably at compile time) because the return type is wrong - and succeeds after the fix.
In other words: a test that the issue you experienced was fixed, and ensuring we don't regress.

Just a test that fails before (probably at compile time) because the return type is wrong - and succeeds after the fix.
In other words: a test that the issue you experienced was fixed, and ensuring we don't regress.

Quick question, is there a way of generating code and then rolling the pedantic linters over it?

Quick question, is there a way of generating code and then rolling the pedantic linters over it?

Hmm - the linter should be run on generated code from the travis script - I don't think you need to do it programatically.

Hmm - the linter should be run on generated code from the travis script - I don't think you need to do it programatically.

How about I add the pedantic package to protobuf/analysis_options.yaml? That should be enough to prevent this regressing.

How about I add the pedantic package to protobuf/analysis_options.yaml? That should be enough to prevent this regressing.

Why wasn't this caught by the linter previously?

Good question.
Looking into this, the difference is to be that dartpad uses:
analyzer:
  strong-mode:
    implicit-casts: false

Why wasn't this caught by the linter previously?

Good question.
Looking into this, the difference is to be that dartpad uses:
analyzer:
  strong-mode:
    implicit-casts: false

I made the change to protoc_plugin entirely.
Question is if we should land this in master, or only on null_safety as this is a lint-only fix.
@iinozemtsev WDYT?

I made the change to protoc_plugin entirely.
Question is if we should land this in master, or only on null_safety as this is a lint-only fix.
@iinozemtsev WDYT?

Sorry, I somehow did not see this earlier. I think merging it into master is fine, I'm going to merge master into null safety in the next few days (I think since github squashes PRs before merge this won't be a real merge, rather a cherry-picking missing commits from master)

Sorry, I somehow did not see this earlier. I think merging it into master is fine, I'm going to merge master into null safety in the next few days (I think since github squashes PRs before merge this won't be a real merge, rather a cherry-picking missing commits from master)

@sigurdm do you need me to do anything w.r.t fixing up this PR such that all tests pass?

@sigurdm do you need me to do anything w.r.t fixing up this PR such that all tests pass?


Previous Value within connect callback.

Can we get the previous value of a key when working with connect? If not it would be great to have a feature like that to compare values to perform an update or not. Currently I'm handling it manually.
Like in @ changed
store.on("@changed", (state, change) => {
    // we can get the changes
})

I would expect something like this for connect:
connect("key", (previousState, state) => {
   // we can compare states
})

or
connect("key", (previousValueOfKey, state) => {
   // we can compare values only not all state
})

I think both would work.

Hello @loeiks
The connect is a method to render your data. You shouldn't check your state in connect callback, only the render logic.
connect('name', (state) => {
  $w('#name').value = state.name;
});

The idea of split your app: 1) state manage layer and 2) render layer. The connect will run only if the state is changed. The changing/check/update state you should manage in the modules.
store.on('add/item', (state, newItem) => {
  if (state.items.length > 100) {
    return; // the state won't be update, if you return nothing
  }

  return {
    items: [...state.items, newItem],
  };
});

In the module you have the current state and it should return partial of state that you want to update or undefined if you don't want to update state.
state.on('your/event', (state, data) => {
  const previousState = { ...state };
  const nextState = { ...state, ...data };

  if (businessLogic(previousState, nextState)) {
    return nextState;
  }
});


Create data structure that enforces the association between price and time category in Admin (Manager)

How to Demo:
Search for key (category or price) and find the proper corresponding value (price or category)

30 min


[Bug Bash 04/22] Composer window does not account well for varying window sizes

When the Composer window is not full screen, even when it's not particularly small it can still hide information. You can see in the screenshot that there are no scrollbars and nothing to indicate to the user that there's an error message that they need to enlarge the window in order to see.

related: #8319 -- cannot see the publish details chevron until you expand the window to a greater width


Implement new product naming scheme

container 2.0.7.dev20_g5992e11 passes a happy path test for v1 against the hyp3-test database

found a pathing problem applying slc orbit files, get_orb downloads to the root working directory, but applying the orbit file happens in a subdirectory at https://github.com/ASFHyP3/hyp3-lib/blob/develop/hyp3lib/par_s1_slc_single.py#L68 , so the orbit file isn't found


Project description

https://github.com/0sugo/tv-maze/projects/1.

Hello reviewer, this repository has two contributors: @rosemutai  and @0sugo

Hi @0sugo and @rosemutai,
Approved 🪄
Your project is complete! Congratulations! 🎉
Highlights

Kanban board setup correctly ✅
All tasks are assigned ✅

Cheers and Happy coding!🍻💻
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy, you have a limited number of reviews per project (check the exact number in your Dashboard). If you think the code review was unfair, you can request a second opinion using this form.


[BUG] Indents are single spaces since latest update

Describe the bug
Since latest update with new auto undent with multiple enter presses, the tab feature is now not working as expected - it is doing single spaces rather than full tabs. I can undent with shift+tab, but tab alone only indents a single space.
Desktop (please complete the following information):

OS: OSX
Obsidian Version: 0.11.9

I can confirm that it persist in Outline 1.0.14

Do you have steps to reproduce this behavior? It's working fine for me.

I saw in Discord that someone had an unrelated issue with this plugin and restarting Obsidian fixed it.
I just now closed and reopened Obsidian and it solved the issue for me.
So, there is something funny going on, but i think we can consider this closed with the caveat that it should be made clear that restarting Obsidian is sometimes required to clear little bugs like this.

I spoke too soon - looks like the issue is happening again.
https://www.loom.com/share/661706943ab54963b8865ca4f6566fd9

Ah, yeah this happened to me. Probably best to keep this open until it's addressed.

Same for me. For a temporary fix just downgrade  to the 1.0.13 (create a folder in .obsidian/plugins/ and put the main.js in there).

@Dreamsync Can't reproduce the issue. Could you please check your tabulation settings?

@vslinko I can repro it if I closed the option to use spaces rather than tabs, which is normal before 1.0.14. But things went normal if I open the option.

@Quorafind Looks like it's expected behaviour since I added indentation detector.
When your choice in Obsidian settings to use tabs, plugin adds tabs, otherwise it adds spaces.
Please close the issue If you agree.

@vslinko yes, but I didn't find an option to close issue.. Sorry

@Quorafind
Don't  you see any option  on the left to comment button?

in 1.0.16 Tab indenting after writiing any text in the bullet doesn't work

The issue persists.
I just now updated the outliner plugin to the most recent update, and double checked that the tab indentation setting is turned on in the Editor settings.
With outliner plugin activated, tabs are only creating single spaces.. if i turn off outliner plugin, tabs work properly.

With tab turned off only one space to indent is possible to produce in outline mode.
This is produced when I try to outline
- A
 - B
  - C
   - C
   - D
   - E
    - F

In 1.0.18 after update the behavior persisted, but turning on and off "Use Tab" in Obsidian Editor helped and Tab started working as expected, I will observe further

In 1.0.18, even if 'Use Tabs' is on, indent seems to consist of spaces, not tab.

Closing the issue. If problem still exists please reopen the issue or create a new one.

This plugin is amazing! however I've had the exact same issue.
The issue comes and goes almost randomly. I was about to record a video and all of the sudden the error disappeared. but it's the exact same thing where it creates spaces instead of indents.
I set things up in setting > editor as shown in screenshot above
It's after some times when I refresh Obsidian that the error goes away, but it comes back randomly.
If it returns I can record my screen with inspector to show
I'm on version 1.0.23
Linux Garuda
Obsidian 0.11.12

Found another invalid case.
If Obsidian "Use tab" setting never changed, Obsidian says to plugin it's undefined and in this case plugin assumes that it's 1 whitespace.

Should be fixed in https://github.com/vslinko/obsidian-outliner/releases/tag/1.0.25
Please check and report


Fix markdown image

For: https://github.com/microsoft/azuredatastudio/issues/24415
Remove extra call insertFormattedMarkdown, which is causing the duplicating issue.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.003%) to 41.576%

Files with Coverage Reduction
New Missed Lines
%

src/sql/workbench/contrib/notebook/browser/cellViews/markdownToolbar.component.ts
1
2.52%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
30788

Relevant Lines:
69355

💛  - Coveralls


Don't run if build fails

It's very confusing to see successful run output when compilation failed in fact

See upstream bug as well:
https://github.com/wasdk/WebAssemblyStudio/issues/260

Fixed here https://github.com/nearprotocol/NEARStudio/pull/40


Migration: Menu Layout and PLN section

As part of the migration of content from GitBook to Hugo, this PR includes:

Layout changes (curriculum menu, headr and single template)
PL Network content (based on the lotus-docs structure).
Perhaps just list the 'Intro' to each section (PLN, IPFS, IPLD, Libp2p, Filecoin), and maybe also have links to Pre-Requisites & Other Resources as well
Would be nice to have left-side nav populate here as well


Breaking change in 2.3.0 from ^2.2.12 - Icons not loading, Modal position incorrect

Setup:
semantic-ui-css: 2.3.0
node: 6.13.0
Problem:
Today i ran into an issue whereby none of the semantic ui icons would load also my modal elements were incorrectly positioned on the page.
Solution:
Downgrade and lock to version 2.2.12

same problem, can't find the icons, it appears that the default theme folder remains empty.
This is not related to semantic-ui-css 2.3, I missed them even when downgrading

Same problem here, had to downgrade to 2.2.14. Otherwise modal window position is wrong and icons not showing.

Having the same problem with the modal

Same problem with modal

Same here.

A CSS override in case you don't want to downgrade:
// Semantic UI modal position fix
.ui.active.dimmer.modals.transition {
    display: flex !important;
    display: -ms-flexbox !important;
}

+1 happens to me too. but downgrading exposes another bug which was fixed in 2.3.0, so I'm having a bug deadlock :)

Just adding my voice - got the same thing happening - modal showing in the top left corner after updating CSS to 2.3.0. Reverting to 2.2.14 fixes it.

I surprised, how long this issue in open state.

The issue is being caused by this styling, which uses !important and overiders the display:flex property on the modal dimmer.
.visible.transition {
    display: block!important;
    visibility: visible!important;
}

Surprised this wasn't caught in testing.

Modal broken for me too.

I don't think @jlukic is monitoring issues in this repo.
I advise all issues be reported to https://github.com/Semantic-Org/Semantic-UI
@jlukic , can we make this repo read-only being that it's only an automatically synced image of the main repo?


Would be great to add stats from "show lists".

Hi guys, thank you for you work!
Is it possible to add  metrics, something like that?
     list      | items
---------------+-------
 databases     |     4
 users         |     3
 pools         |     2
 free_clients  |   357
 used_clients  |   443
 login_clients |     0
 free_servers  |    18
 used_servers  |    32
 dns_names     |     1
 dns_zones     |     0
 dns_queries   |  -307
 dns_pending   |     0
(12 rows)

Hi @pracucci,
Sorry, Actually I mean two metrics for create the alerts:

free_clients;
free_servers;
(I have had the same triggers in the zabbix, it was useful for me)
Thank You!


Fixes log line for pod creation

Description of the change:
It looks like there was a copy-paste error in the logging.
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Bug fixes are accompanied by regression test(s)
[ ] e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
[ ] tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
[ ] Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
[ ] Docs updated or added to /doc
[ ] Commit messages sensible and descriptive
[ ] Tests marked as [FLAKE] are truly flaky and have an issue
[ ] Code is properly formatted

/approve
/lgtm


Noblecraft/1192

this is a proposed fix for issue #1192
sorry its a bit messy, first time contributing to ui-select.

This needs changes to dist reverted, rebasing, and tests added for this new feature.

Closing as I don't think this is a particular good solution to the problem. Let's see if anyone else is able to come up with something else.


Apply_tf.sh fails when targeting 'usgovtexas' in Azure Gov

Description
When the user targets their deployment to the 'usgovtexas' region in Azure Government, an error is thrown during the creation of the Log Analytics workspace.
Steps to Reproduce
Steps to reproduce the behavior:

Setup your global.tfvars so it points to the US Gov Texas region

# Copyright (c) Microsoft Corporation.
# Licensed under the MIT License.

Actual behavior
The saca hub deployment fails with the following error and the code performs 4 more retries, all failing the same way.
Error: operationalinsights.WorkspacesClient#CreateOrUpdate: Failure sending request: StatusCode=0 -- Original Error: Code="LocationNotAvailableForResourceType" Message="The provided location 'usgovtexas' is not available for resource type 'Microsoft.OperationalInsights/workspaces'. List of available regions for the resource type is 'usgovvirginia,usgovarizona'."

  on ../../modules/hub/main.tf line 24, in resource "azurerm_log_analytics_workspace" "loganalytics":
  24: resource "azurerm_log_analytics_workspace" "loganalytics" {

Screenshots

Additional context
Operating System:  Windows 10 with WSL (Ubuntu 20.04)
Terraform Version:
Cloud (public, Azure Government, etc.): Azure Government

This fix for this is part of #299