Deprecation/inactivation of run_Fastq_Multx

Changed run_Fastq_Multx to inactive category through spec.json and added deprecation announcement to the display.yaml. RELEASE_NOTES were updated as well; according to the major change of status in the module.

@sychan based on Travis-CI failure, looks like we need to update Dockerfile base image to eliminate jars dependency?


onAttachedToActivity method of ActivityAware not called

Good morning,
I am currently developing a flutter plugin on Android and iOS platforms. The main problem is that all the callbacks of ActivityAware are never called.
Steps to Reproduce

Execute flutter run on the code sample (see "Code sample" section below)
Wait until the app is loaded inside Android simulator Pixel_3a_API_33_arm64-v8a

Expected results:
See log onAttachedToActivity on console.
Actual results:
The expected log onAttachedToActivity is never printed to console.

Code sample
Here you can find my git repository with all the code
project

Logs
flutter run --verbose
log.txt
flutter analyze
Analyzing example...
No issues found! (ran in 1.5s)

flutter doctor -v
doctor.txt

Thanks for filing the issue, @lukluca. I can reproduce this issue on the latest stable and master channels.
Minimal sample code (only contains ActivityAware's methods): https://github.com/huycozy/reproduce-plugin-template

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.7.7, on macOS 13.0.1 22A400 darwin-x64, locale en-EE)
    • Flutter version 3.7.7 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2ad6cd72c0 (10 hours ago), 2023-03-08 09:41:59 -0800
    • Engine revision 1837b5be5f
    • Dart version 2.19.4
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

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

[!] Android Studio
    • Android Studio at /Applications/Android Studio Preview.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
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] Android Studio (version 2022.1)
    • 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.15+0-b2043.56-8887301)

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • 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

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

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 110.0.5481.177

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[!] Flutter (Channel master, 3.9.0-11.0.pre.6, on macOS 13.0.1 22A400 darwin-x64, locale en-VN)
    • Flutter version 3.9.0-11.0.pre.6 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 0dd46a33e7 (6 hours ago), 2023-03-19 18:21:21 -0400
    • Engine revision dc6e389aea
    • Dart version 3.0.0 (build 3.0.0-339.0.dev)
    • DevTools version 2.22.2
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

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

[✓] Android Studio (version 2022.1)
    • 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.15+0-b2043.56-8887301)

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • 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

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

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 111.0.5563.64

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

@huycozy Does it reproduce with a Java plugin? We use onAttachedToActivity in many of the 1P plugins, and they are not all broken, so there must be something about these examples that is different from the existing, working plugins.

Yes. It actually works (on both Kotlin and Android). Thank @stuartmorgan for the hint.
@lukluca You should check the log from Logcat, for eg:
2023-03-22 10:59:58.471  3642-3642  ReproduceP...latePlugin com...oduce_plugin_template_example  V  onAttachedToActivity

I will close this issue because it is working as intended. If you disagree, please write in the comments and I will reopen it. Thanks!

Hi @huycozy,
I found some defects on my git project, and I fixed them. I saw that the logs are displayed only if I run the example app as a standalone android project, but if I run the app as a flutter project, the logs are not displayed. So the onAttachedToActivity is called, but on console I am not able to see the logs.
Thanks!


ExtracteurDeJus should handle class methods decoration

Minimum reproducible example required

The problem is deeper then what I firstly thought : it comes from the fact that the ExtracteurDeJus is instanciated with the class and not at each instance. A quick fix would be to move the decoration step during the construction of the instance
`class Test:
def __init__(self):
    self.method = falzar(self._method)

def _method(self, *args, **kwargs):
    pass`

A way to handle this properly would be to manually create a Decorator class, see #9


Button causes error

Hey,
the form button produces an error:
Call to undefined function _(), did you mean d()?
File: [.../FrontendForms/Formelements/Miscellaneous/Button.php:27]
27:            $this->setAttribute('value', _('Send')); // default is "Send"
I think it must be __('Send)

Hello pmichaelis
Thanks for reporting this issue. I have added the missing $this in front of the translatable string (of course you can also write it with 2 underscores as you suggested).
Have a nice day


FR: Make client_max_body_size customizable

It's very important to have some limitations on request size, but I think it shouldn't be hard-coded:
https://github.com/saltcorn/saltcorn/blob/0720870401d7a2c7ce9638588d4a5b6a2d649075/packages/server/app.js#L99-L108

Fixed in #2053 and #2091.


flutter logs should notice when the engine crashes and output a symbolic stack trace

I noticed that sometimes an app I have crashes, both using the flutter tool and when deloyed.
This is the produced error message: https://gist.github.com/stevenroose/f46a481a534eb3e6d652
I can't pull the tombstone, since adb says it doesnt exist.
Of course, I don't know if this is a Flutter bug or a bug in my app, no Dart stack trace is provided.

We can get symbols for the backtrace if we have your flutter version.
Also I suspect you don't have a "user debug" build of Android, so adb root doesn't work? In which case i'm not sure how to pull tombstones, but the internet likely knows:
https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#safe=off&q=how+to+pull+tombstone+android

Ideally flutter logs should know how to show you symbols for your backtraces, and probably should know how to pull tombstones if that's possible.

$ flutter --version
Flutter
Repository: https://github.com/flutter/flutter.git
Branch: master
Revision: 884c8e9e3585a55f89c5d414010d3ebcbaf2f8c1 (3 days ago)

This hasn't come up in a long time (the engine doesn't crash much in my experiance).  I suspect we can punt this a later milestone.

It mostly doesn't happen much because the framework carefully walks around the landmines. But I agree it's not critical for the near future.

We've started becoming much more crashy and we have no good way to handle crash reports from the wild so I'm upping this one's priority.

Current process is that folks find them, pull them with the respective tools (adb logcat or XCode's log viewer/Console.app) and file a bug.  I've been slowly iterating on a process for symbolicating reports we get from the field: https://github.com/flutter/engine/wiki/Symbolicating-production-crash-stacks

Really I wish that flutter run and flutter logs did the equivalent of:
~/Android/Sdk/platform-tools/adb logcat | ~/dev/engine/src/third_party/android_tools/ndk/ndk-stack -sym ~/dev/engine/src/out/android_debug_unopt/


Escape case where password ends with '$'.

postgresql_escape returns an invalid string if the password end in '$'.
postgres=# alter role "postgres" password $$foo$$$;
ERROR:  syntax error at or near "$"
LINE 1: alter role "postgres" password $$foo$$$;

Thanks for contributing, the ticket is here https://tickets.puppetlabs.com/browse/MODULES-3025


Giving basic education about NFT to new users.

Is your feature request related to a problem? Please describe.
As Non-Fungible Tokens (NFTs) are an emerging form of investment, many new users would not be able to understand the concept behind it and how KodaDot is working on this as a platform.
Describe the solution you'd like
While many users do their own research, it would be a great idea to add literature about NFTs in the FAQs and Tutorials.
To start with, hyperlinking other articles on NFT would be a great start, we can always come up with our own write-up in the future. The same can be applied to videos and other media.
Describe alternatives you've considered
We can also have ambassadors and influencers talking about NFT and KodaDot but that can be done in a later milestone.

Basic NFT explanation and workflow is running in the documentation under
https://docs.kodadot.xyz/how-to-make-nft.html#create-a-piece-of-art

There will be an ambassador program

#2040


pull request for e2e test at 01/03/2017 12:56:13

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Stub out type hierarchy

Towards https://github.com/hubmapconsortium/portal-ui/issues/1688.
Don't think it makes sense to move this forward until #268 is resolved.

Nils will bring this up in the HIVE meeting on 2021-08-25.

@ngehlenborg -- Is this area of work still a priority?

@pecan88 has been collecting input on a possible hierarchy/groupings of assays but I don't know if this has been finalized. @pecan88 could you briefly comment on the status of that effort?

(Zhou asked if this could be closed. Just pinged Peter on Slack.)

@mccalluc - here's the latest (G-Drive pw protected).  This is pretty much final and the next step is for @computationdoc to pull this in via the ontology tool / Knowledge Graph for eventual display.  Beyond a basic understanding of "the ontology tool will handle it", I'm not sure about next steps and will check in with JCS.  In the meantime, I'd say we can either close this if you think it addresses and track separately or we can leave open and come back to update.

Is this PR still relevant? Please close if not.

Close this PR for now, reopen if needed.


feat: Add support gruf 2.19

Update appraise for gruf 2.19 and old versions

Please remove the following to re-enable the tests in CI:
https://github.com/open-telemetry/opentelemetry-ruby-contrib/blob/a005a987c74f1dd0958aae9e4d47ad84cf34a611/.github/workflows/ci-instrumentation.yml#L55
https://github.com/open-telemetry/opentelemetry-ruby-contrib/blob/a005a987c74f1dd0958aae9e4d47ad84cf34a611/.github/workflows/ci-instrumentation-canary.yml#L64


Sidhant prs

Have you read the [Contributing Guidelines on Pull Requests]
Yes,I have read.
(Write your answer here.)
Description
Dutch National Flag Algorithm- Implemented in C++.
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] Dutch National Flag algo -Implemented

Related Issues or Pull Requests
(Write your answer here.)

Hello @Sidhant-Gupta
If you are picking problems for CP/DS-Algo Portals, please add their link.
The above problem is from a LeetCode Problem.

I've made the desired changes. Please review it.

I've made all the requested changes. Kindly review @HarshCasper


Merge master branch to prTesting1_201907021210 branch

Docs Build status updates of commit 6c9f874:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestCon1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


OffroadHome: merge stylesheets

Want to fix #21266 too?

Ok, let me check

Hmm, think it's also fine to separate the update and alert buttons.

I'll fix it in another PR


Feature: Bidirectional(ish) inference

Move to a pseudo-bidirectional type system algorithm, similar to the
one described for Damas-Milner inference in [0]. This isn't sound at
all, yet, particularly because of fiddlyness around the subsumption
check.b
We reuse most of the infrastructure, but the core judgement is
Γ ⊢ x <= t instead of Γ ⊢ x => t (i.e. checking instead of
synthesis).
You can recover inference from checking in a unification-based
system (like ours) like this:
infer e = do
  x <- fresh
  check e x
  pure (e, x)

I've moved over both expression and pattern type inference (the two which used to suck the most) to the new bidirectional system, but kinds are pretty much the same.

I'm still working on some things, actually. Somehow we type less programs now.

The latest commit makes one change that allows for some level of higher-rankedness: Variables checked against a polymorphic type use the subsumption relationship, while variables synthesising their type use the previous instancing behaviour.
We could previously type this program:
let higher_rank (f : forall 'a. 'a -> 'a) =
  (f 1, f "foo")
(* higher_rank : (∀ 'a. 'a -> 'a) -> int * string

We can now type some uses of this function. Namely:
let foo =
  let id : forall 'a. 'a -> 'a =
    fun x -> x
  in higher_rank_id id ;;
(* main : int * string *)

let id x = x
and bar = higher_rank id ;;
(* bar : int * string *)

but not:
higher_rank (fun x -> x)

as functions never synthesise a polymorphic type.


Bitkeeper fails to build under LLVM16

LLVM16 enables c++17 by default. The tcl/tk bindings fail to build due to incompatible pointer types and throw exceptions are no longer supported under c++17.

Does it build with --std=c++11 or c++14?

No. It's C code (not C++) in your src/gui/tcltk/tcl.


Tapsigner

It appears when using a Tapsigner, BK has no way of changing from the starting pin.  This is a problem because it creates a single point of failure for that key.  It should prompt or at least give the option to change the pin.

[x] Will need option to change pin of Tapsigner on Setting @AreejKhalid21

[x] Once key(Tapsigner) is added successfully. On that modal also user can change pin
“Change PIN” CTA and some text above it @AreejKhalid21

Tapsigner Pin reset Flow:
https://www.figma.com/design/m5eMFTKD391AiJAXaEzgxB/Bitcoin-Keeper?node-id=1502-4150&t=vTtvaWFXVqcu5B5g-1

The Tapsigner Key addition Modal:
https://www.figma.com/design/m5eMFTKD391AiJAXaEzgxB/Bitcoin-Keeper?node-id=1502-4150&t=vTtvaWFXVqcu5B5g-1

The Tapsigner doesn't allow to change the PIN code until the user backs up the card's key. The backup is an encrypted version of the private key that is on the card, which can be decrypted using the Backup Password written on the card itself. We don't need to worry about allowing to restore from Keeper for now, but we do need a UI that allows the user to save a backup file. And in the change card if the user didn't save a backup before we should show the user an error message when they scan the card that they need to do the backup first. (We can aslo show it on the PIN reset itself as a warning in general).
@AreejKhalid21 we will need a design for saving the backup file flow and the warning on the change PIN.


auto retry inflight pipeline requests?

So if we send e.g. 3 pipelined requests to the server, the first one fails e.g. due to socket failure, then we should probably fail the first one, reconnect and automatically retry the two following ones since the server never processed them?

I think just makes things more complicated? Leave to user space.

That’s my take.


refactor: being able to run Examples app without manual prerequisite …

…step
add the package as a local dependency to Xcode project which still allows contributors to easily
test local changes
fix #90

Merged with https://github.com/SAP/cloud-sdk-ios-fiori/pull/91


Change: Add Single Argument

Description
On application, one (wildcard) argument should be added
Example
In the case of
const 1

We would be suggested to do
const 1 undefined
const undefined 1

Closed with b4cdf8a

Closed with b4cdf8a


Can't use the decade filter

Movies.yml:
templates:
  Year:
    decade: <<decade>>
    summary: A collection of movies released in the <<collection_name>>
    sort_title: '*<<num>>'
    collection_mode: default

collections:
  1970s:
    template: {name: Year, decade: 1970, num: '000'}

Logs:
|====================================================================================================|
|                                          1970s Collection                                          |
|====================================================================================================|
|                                                                                |
| Scanning 1970s Collection                                                                          |
|                                                                                |
| Method: template                                                                                |
| Value: ordereddict([('name', 'Year'), ('decade', 1970), ('num', '000')])                           |
|                                                                                |
| Method: decade                                                                                |
| Value: 1970                                                                                |
|                                                                                |
| Method: summary                                                                                |
| Value: A collection of movies released in the 1970s                                                |
|                                                                                |
| Method: sort_title                                                                                |
| Value: *000                                                                                |
|                                                                                |
| Method: collection_mode                                                                            |
| Value: default                                                                                |
|                                                                                |
| Sync Mode: append                                                                                |
|                                                                                |
| Method: plex_search                                                                                |
| Values: [{'decade': 1970}]                                                                         |
|                                                                                |
| Value: {'decade': 1970}                                                                            |
| Traceback (most recent call last):                                                                 |
|   File "D:\Documents\Plex Meta Manager\modules\config.py", line 462, in update_libraries           |
|     builder.run_methods(collection_obj, collection_name, rating_key_map, movie_map, show_map)      |
|   File "D:\Documents\Plex Meta Manager\modules\builder.py", line 824, in run_methods               |
|     for o, param in enumerate(search_data):                                                        |
| TypeError: 'int' object is not iterable                                                            |
|                                                                                |
| Unknown Error: 'int' object is not iterable                                                        |
|                                                                                |
|====================================================================================================|

I get the same error. It seems to work if you do one year at a time instead of decade, obviously that wouldn't be ideal though.

fix is in develop

I pulled from develop and that seemed to fix it. Thanks for resolving it.


Make logging configurable

I'm using the generate() API in my own tooling and it would be nice if one could intercept or disable the default log outputs.
The generate function could either accept optional logger parameter that matches https://github.com/kallaspriit/ts-log etc and defaults to the winston implementation you're already using. This way the log messages could be intercepted and either ignored or piped elsewhere.
Simpler alternative would be to just accept a "silent": true parameter that does not call the log statements.

Sounds good. I'm on it :)

Done in https://github.com/dotansimha/graphql-code-generator/commit/c26606593d1a97dc61750dfc29f85ef7dd6bc006

Done in 0.12.0


Create AWS CloudFormation Template to Deploy Prefect Agent on EC2

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-instance.html
Create a single cloudformation template + bootstrap script to deploy the prefect agent onto an ec2 instance

Upvote this, need for POP (POC-lite) process. @gabcoyne Tentative due date: Aug 29


微信安装

🚨 The issue tracker is not for questions 🚨
If you have a question, please ask it on https://stackoverflow.com/questions/tagged/wechaty
[question]这是怎么安装的有详细加成没有？

详细的教程

See:

http://github.com/wechaty/wechaty-getting-started
http://wechaty.js.org/


Inconsistent APPEND: The Append cmd on dicedb cli isn't producing same output as redis-cli

Steps to reproduce

APPEND ts "0043"
APPEND ts "0035"
GETRANGE ts 0 3
GETRANGE ts 4 7

Expected output

The above output is coming from redis-cli
Observed output

The observed output when the above set of commands when run on DiceDB
Expectations for resolution
This issue will be considered resolved when the following things are done

changes in the dice code to meet the expected behavior
addition of relevant test case to ensure we catch the regression

You can find the tests under the integration_tests directory of the dice repository and the steps to run are in the README file. Refer to the following links to set up DiceDB and Redis 7.2.5 locally

setup DiceDB locally
setup Redis 7.2.5 locally
setup DiceDB CLI

@JyotinderSingh @lucifercr07 I would like to work on this issue
thanks

@JyotinderSingh @lucifercr07 I have raise a PR for this #1107 pls review


How to get an instance from injector, with non-default ctor?

Hello,
I've defined a binding, like this one: bind<Smth>().to<BestSmth(int,int)>().
Now, I've created a Modules and an Injector, and I want to create an instance of Smth according to the binding above, how could I do this?
Because:
shared_ptr<Smth> s = an_injector->get<BestSmth>(42, 42);

is an error, get does not takes args for BestSmth ctor.
Thanks!

Closing as stale.


[CARBONDATA-3466] Fix NPE for carboncli command

if no options specified, like "carboncli for table source", NPE will occur when running commandOptions.split("\\s+") in CarbonCliCommand#processData.
Since option, as a role of command, is a must in CarbonCli, we require it when parsing command in this PR.
FYI, if user give options(''), carboncli can check and throw like this:
0: jdbc:hive2://<IP_ADDRESS>:10000> carboncli  for table testtbl options('');
Error: java.lang.RuntimeException: Parsing failed. Reason: Missing required option: cmd (state=,code=0)

Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3757/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3969/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/12033/

whether it is better define
case class CarbonCliCommand(
databaseNameOp: Option[String],
tableName: String,
commandOptions: Opiton[String]) instead of .

whether it is better define
case class CarbonCliCommand(
databaseNameOp: Option[String],
tableName: String,
commandOptions: Opiton[String]) instead of .

And then? I don't get you.
carboncli requires a command which is set in option.

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3839/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/4044/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/12112/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/270/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/266/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/267/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/276/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/273/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/272/

@kevinjmh Please try to add the testcase

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/298/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/294/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/294/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/308/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/304/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/304/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/313/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/309/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/309/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/319/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/316/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/315/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/323/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/320/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/319/

LGTM


Category field should not change to capitals every time a space is typed

Every time I add a space when typing categories, the letter case is changed to capitals. Many categories do not start each letter in capitals so this is quite frustrating. What do you think?

Hmm, sorry @VojtechDostal , I'm not clear on that the issue is. Do you mean that your phone keyboard auto-corrects your input to a capital for each new word when you are searching for categories in the Categories screen?
If so, firstly I don't know if we can do anything about it - it seems to be a keyboard setting on your device. Secondly I'm not sure if it makes a difference - our categories SHOULD show up when searched regardless of capitals (ie case should be irrelevant). And the categories that are saved at the end of the day are the categories that you select by tapping the "tick" at the end, the textbox above them is just for searching for them and does not affect the final output.

It seems to be really specific to this one text field though...
But if the search algorithm disregards letter case, then it's all right for me :-)

This is might be because of the pull-request #1099 which fixed the issue #1098

Wow, I just noticed #1098 ! I really wonder why the search issue mentioned in that issue would occur, when AFAIK our MediaWiki query is case-insensitive? For instance, I searched https://commons.wikimedia.org/w/api.php?action=query&list=search&srwhat=text&srnamespace=14&srlimit=10&srsearch=four storeys house for Four Storeys House and four storeys house and got exactly the same results.
@neslihanturan are you sure that lowercase affected the results that you obtained? Even if it did though, lots of categories do not use Camel Case, it is a bit of a mix between the two.

Hmm, at the time we merged that PR, category search was a little problematic. I remember, several times I had to write exactly same category name to see results. So maybe I misunderstood the root cause of this issue. Do you think it is better to use capital for only first letter? Because I think weight of categories that start with capital is higher. There is no a balanced mixture.

This does not happen anymore, from my experience. If you disagree, feel free to reopen. Thanks all! :-)


[QMAPS-2039] Normalized PJ addresses

Transform uncomplete word such as r -> rue or bd -> boulevard
Normalize capitalization for each PJ endpoints

I totally agree by using Squash and Merge feature. About avoiding Github tools, do you mean using only cli or can I click on the big green button ?


Release version 1.3

This is a component issue for release 1.3.0.
Coming from opensearch-build#889, release version 1.3. Please follow the following checklist.
Preparation

[x] Assign this issue to a release owner.
[x] Finalize scope and feature set and update the Public Roadmap.
[x] Create, update, triage and label all features and issues targeted for this release with v1.3.0.

CI/CD

[x] Increment version on main to <IP_ADDRESS>.
[x] Ensure working and passing CI.
[x] Re(add) this repo to the (if not exist) manifest.

Pre-Release

[x] Branch and build from a 1.3 branch.
[x] Update your branch in the manifest.
[x] Feature complete, pencils down.
[x] Fix bugs that target this release.

Release

[ ] Complete documentation.
[x] Gather, review and publish release notes.
[x] Verify all issued labeled for this release are closed or labelled for the next release.

Post Release

[ ] Create a release tag.
[ ] Suggest improvements to this template.
[ ] Conduct a postmortem, and publish its results.

I believe this needs to stay open until the tag is made on March 14/15


Dependabot updates caddy:2.4.5-alpine to caddy:2.4.6-builder instead of caddy:2.4.6-alpine

Package ecosystem
docker
Package manager version

Language version

Manifest location and content prior to update

dependabot.yml content
https://github.com/SkynetLabs/skynet-webportal/blob/master/.github/dependabot.yml#L27-L30
Updated dependency
https://hub.docker.com/_/caddy
What you expected to see, versus what you actually saw
One Dockerfile contains 2 image dependencies: caddy:2.4.5-builder and caddy:2.4.6-alpine.
caddy:2.4.5-builder got updated to caddy:2.4.6-builder => correct
caddy:2.4.6-alpine for updated to caddy:2.4.6-builder => incorrect, should be caddy:2.4.6-alpine
Native package manager behavior

Images of the diff or a link to the PR, issue or logs
https://github.com/SkynetLabs/skynet-webportal/pull/1366/commits/c25618cd7607b18002306b74aa6a54daf25464fa
🕹 Bonus points: Smallest manifest that reproduces the issue

I'm pretty sure this is a dupe of #5538 which was recently resolved in https://github.com/dependabot/dependabot-core/pull/5560.


Support for $main and $aux built-ins in boundary constraints

Related issue: #26
Implement column access by index as it described in related issue for boundary constraints.

I think we may want to look at this after #106

Closing this as no longer relevant.


'Date' support

Feature Request
I'd like dates to be supported, but I can't seem to get it to work.  Here's what I've tried:
console.log("Date test 1", TSON.is<Date>(new Date()));
console.log("Date test 2", TSON.is<{x: Date}>({x: new Date()}));
console.log("Date test 3", TSON.is<{x: number}>({x: 123}));

The output is:
Date test 1 false
Date test 2 false
Date test 3 true

Update to latest version, then it works.


Upload all user research for the 2024 workshop

Done! https://github.com/sprblm/The-Design-We-Open/tree/main/user-research


Lots of clicks to make a new node

To create a new node you must:

right click
double click node type
drag pin to previous node
select new node

If you could drag off a pin to open a node, you could simplify to:

drag off pin and release
double click node type

Now (v1.3.0+) we have it.
You can drag and quick insert nodes from any of the incoming or outgoing slots.

There is also a setting for even faster node creation :
QUICK_INSERT_NODES_ON_SINGLE_CLICK (false in official releases)


K8SPXC-1165 - Cleanup some old or duplicate diff files in the tests

CHANGE DESCRIPTION
Problem:
We have some old diff files for versions for which we no longer support operator and also there are some diff files which have the same content.
Solution:
Remove the old ones and in case of duplicates use just one.
CHECKLIST
Jira

[ ] Is the Jira ticket created and referenced properly?
[ ] Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
[ ] Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

[ ] Is an E2E test/test case added for the new feature/change?
[ ] Are unit tests added where appropriate?
[ ] Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

Config/Logging/Testability

[ ] Are all needed new/changed options added to default YAML files?
[ ] Are the manifests (crd/bundle) regenerated if needed?
[ ] Did we add proper logging messages for operator actions?
[ ] Did we ensure compatibility with the previous version or cluster upgrade process?
[ ] Does the change support oldest and newest supported PXC version?
[ ] Does the change support oldest and newest supported Kubernetes version?

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

pitr-gap-errors-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1462/commits/84240cd5a710e90d3ce8c18a0849d9f3aec009a6
image: perconalab/percona-xtradb-cluster-operator:PR-1462-84240cd5

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

pitr-gap-errors-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
failure

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1462/commits/98cafb4fd7d77af65fdc25ffd33eed44d4291f08
image: perconalab/percona-xtradb-cluster-operator:PR-1462-98cafb4f

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

pitr-gap-errors-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
failure

smart-update2-8-0
failure

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1462/commits/ad2cedc20448d8b430c2468ab83a721b7f3a2490
image: perconalab/percona-xtradb-cluster-operator:PR-1462-ad2cedc2

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

pitr-gap-errors-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1462/commits/ad2cedc20448d8b430c2468ab83a721b7f3a2490
image: perconalab/percona-xtradb-cluster-operator:PR-1462-ad2cedc2


unable to build with minify_css activated

$ bundle show middleman
/usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/middleman-3.3.7

$ grep minify_css config.rb -B 1 -A 1
configure :build do
  activate :minify_css

stack trace

Looks like an issue in either your Sass or in the Sass or Compass projects:
(sass):3830: Invalid CSS after "    filter: progid": expected "}", was ": DXImageTransf..." (Sass::SyntaxError)

thanks, bootstrap 3.3.2 is broken, upgraded to bootstrap 3.3.4 and minifying is working nicely.


Document relationship between available OT Collector Docker images

Hi, there are currently at least three different images for the OpenTelemetry Collector:

otel/opentelemetry-collector
otel/opentelemetry-collector-dev
otel/opentelemetry-collector-contrib

The difference between these three images does not seem to be clearly documented anywhere.
It would be good to see a section of documentation with a comparison between all available OTel Collector images. This would aid users in selecting the correct collector for their use case.
It might also be worth documenting the relationship of the three images above to platform-specific images such as aws-observability/aws-otel-collector.

We need a better place to document this, and the current state isn't the final, but here's a short description:

open-telemetry/opentelemetry-collector has the core code, that serves as library for all distributions
open-telemetry/opentelemetry-collector-releases produces the main official distribution and publishes the container image otel/opentelemetry-collector
open-telemetry/opentelemetry-collector-contrib has other non-official components at varying states of maturity and quality. They are all bundled into the "contrib" distribution and published as the container otel/opentelemetry-collector-contrib. Eventually, the building of the distribution will be moved to this repository here.


Initial review of the code

The purpose of this review is to be able to run the program as it was originaly created  This means I should only fix the errors that I get when I try to run it. (Probably I only need to check the connections to the database and tor network).

After reviewing the code there will need to be some reworks on the code.


Add support for nested documents

Currently ElasticSplunk doesn't handle nested documents in search hits from Elastic (it does handle searches although - object.object.attr:value in query argument).
This can be handled as it is done in resultd by Kibana, by flattening nested documents like:
{
  "l1": {
    "l2": {
     "attr1": "value"
    }
  }
}

Into:
l1.l2.attr1:value
The same structure can be used for searches.
Thanks @heipei for bringing this up.

@heipei
Can you please test f432f916d57c52dc1493cf04e3e935fbd10382c6  ?
Thanks!


Don't silently fail on junit2jira

Description
Currently when junit2jira fails we skip it and continue normal flow. Since we now rely on this tool for our day to day job let's not ignore failures and get slca notifications for them as a part of CI trap.
Checklist

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

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

How about making it like slack notifications but include nightly runs?

Whatabout only ignoring failures from the curl (as well as moving below the cp)? That is probably where the most 'weakness' lies from github rate limiting. If the tool or jira access is a problem we have more control and can always spin a quick fix. Another option is put junit2jira in the repo or the ci image (with the usual image update pain).


Client Allocation Request for: monkdharma

Client Allocation Questions
Core Information

Name: monkdharma
Website / Social Media:
Region: Greater China
DataCap Requested: 10TiB
Addresses to be Notarized: f1oi265jelqmmzvku6g2po2yl6lsauyyorciqahei
Notary Requested: Joss-Hua

@monkdharma Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

hi friend i re-initiated the request

Unfortunately, an error occurred during the signing process.
Could you help the request to check the reason? @galen-mcandrew @Kevin-FF-USA

Friends, is there something wrong with my request? If your datacap quota is insufficient, I can apply like other notaries

I saw another request in the list, but this one is not available. There must be an unknown exception, but I haven't received any feedback yet.
Suggest you make a request to another notary, good luck.

OK, thanks


Make sure we don't hide exceptions from waitUntilContainerStarted

This adds the original exception as the cause. It also adds the text "Wait strategy threw an exception." to each exception message.
This addresses two issues:

The original exception from waitUntilContainerStarted was not being included as the cause in newly thrown exceptions in tryStart. The exceptions were not completely hidden because they were being logged, however, but the initial cause was less visible.

The exception messages focused on state that was found at the time the exception was received but did not mention that the waitUntilContainerStarted method threw an exception.

Because of these two issues, unless you look at the source or see the logs, it isn't clear that this was caused by an exception from waitUntilContainerStarted. In test failure reports, CI systems, etc. that might highlight the failure message and not logs, this makes it harder to debug these issues.
Here is an example why including these details is useful:

An example a failure in the CircleCI test view: https://app.circleci.com/pipelines/github/OpenNMS/opennms/25469/workflows/5af07488-d835-4b46-91e9-0bbb6ee70940/jobs/198804/tests
The cause can be found in logs in test-results/junit/TEST-org.opennms.smoketest.OpenShiftCompatIT.xml artifact if you search for the first instance of ERROR, but this is, uh, not the best user experience. ;-) https://app.circleci.com/pipelines/github/OpenNMS/opennms/25469/workflows/5af07488-d835-4b46-91e9-0bbb6ee70940/jobs/198804/artifacts

thanks for your contribution @deejgregor ! This is now in main branch


Add getting started section to readme

README update
Please add README

Added Getting started section in README file.


2690: Fix ical export

Short description

Fix description in ical export.
Proposed changes

Strip carriage returns (\r) of excerpts
Encode new lines (\n) with \\n

Side effects

None.
Resolved issues

Fixes: #2690.

👍 Nice, tested in Firefox on Mac OS but the bug only happened on Windows. Does anybody have a Windows machine on which we could test this?

Happened for me on linux as well :)


Crash on C# exception while reloading assemblies

Godot version
v4.0.alpha.mono.custom_build [0b8a63e47]
System information
Windows 11, Vulkan, 3080
Issue description
When I build a C# project that generates an exception in the editor, it crashes the editor inside of godotsharp_internal_script_debugger_send_error because EngineDebugger::get_script_debugger() returns null, and this is not checked.

Steps to reproduce

Open the reproduction project
Make sure the "crash_test" addon is enabled
You should see a gizmo drawing a line in the 3D view
In addons/crash_test/CrashGizmoPlugin.cs, change if (true) { to if (false) {
Click "Build" in Godot

Minimal reproduction project
CrashTest20220829.zip

EngineDebugger::get_script_debugger() returns null, and this is not checked.

You are not entirely correct about this, it's true that this method can return null but we do guard calls to this method with a call to EngineDebugger::is_active() which would return false if the debugger is null so it would never call that method:
https://github.com/godotengine/godot/blob/8c7be63588bf3e4ef4b780ff57936c68db5939c7/modules/mono/glue/GodotSharp/GodotSharp/Core/NativeInterop/ExceptionUtils.cs#L106-L109
The NativeFuncs.godotsharp_internal_script_debugger_is_active method calls EngineDebugger::is_active() to check that the script debugger is not null, then we call the SendToScriptDebugger method which ends up calling EngineDebugger::get_script_debugger() but this only happens if the previous check passed.

I have been unable to reproduce the crash (with Godot built from commit 3cf16c959) but I do get an error in the console with the C# exception:
modules/mono/glue/runtime_interop.cpp:1241 - System.InvalidCastException: Unable to cast object of type 'Godot.EditorNode3DGizmoPlugin' to type 'CrashGizmoPlugin'.
     at crash_test.RestoreGodotObjectData(GodotSerializationInfo info) in /media/raulsntos/Data/GodotProjects/TESTS/CrashGizmo/Godot.SourceGenerators/Godot.SourceGenerators.ScriptSerializationGenerator/crash_test_ScriptSerialization_Generated.cs:line 15
     at Godot.Bridge.CSharpInstanceBridge.DeserializeState(IntPtr godotObjectGCHandle, godot_dictionary* propertiesState, godot_dictionary* signalEventsState) in /media/raulsntos/Data/Godot/src/godot/modules/mono/glue/GodotSharp/GodotSharp/Core/Bridge/CSharpInstanceBridge.cs:line 239

This is caused by the generated code that handles the restoring of a class when reloading assemblies. This may be expected since the class being reloaded has been modified but I'm not sure.

@codecat Are you still able to reproduce this issue in the latest release (RC2)?

I am not working on the particular project that I was anymore, but I just tested the reproduction project on RC2 and it doesn't seem to crash anymore for me. 👍


Treat all PR links the same as fixes

Heya, at the moment when raising a PR that fixes an issue, the issue is pulled across to the Needs Review column and not shown anywhere else e.g:

If it has any other relationship type, e.g. Required by, Depends on etc, the issue remains where it is with the PR below it and the PR appears in the Needs Review column with the issue below it e.g.

Would you be open to make all link types behave the same as fixes? The advantage then being that the issues and pr's are only shown once rather then twice. It also makes this the same as what Waffle used to do.
Also, once the PR has been merged/closed, we could make the issues return to the In Progress column.

Agreed on the fact that PRs should always be collapsed under the issue rather than appearing as embedded links :+1:.
Not sure about moving an issue if the state of a non-closing linked PR changes. If you got a couple of Related to #someIssue links from different PRs, would you expect the issue to move into the review column, each time one of these PRs is put into review? I'd rather expect the issue remains where it is and that the linked PRs appear separated on the boards needs review column.

Implemented that all linked PRs are always shown collapsed under the given card:

Note that issues and PRs (83 in the screenshot) are still shown in the review column as a separate card. From my point of view, this is already an improvement.

One improvement to consider here could be to not show PR cards, if these PRs are already attached to issues in the same column. That gives users the freedom to move issue + PR around and benefit from no card duplication in the standard cases.

Happy to hear your feedback on this.

yes, that is done. I just need to rebase my branch which has those changes already

From: Nico Rehwaldt<EMAIL_ADDRESS>Sent: 05 July 2019 22:04
To: nikku/wuffle
Cc: Subscribed
Subject: [EXTERNAL] Re: [nikku/wuffle] Treat all PR links the same as fixes (#28)
One improvement to consider here could be to not show PR cards, if these PRs are already attached to issues in the same column. That gives users the freedom to move issue + PR around and benefit from no card duplication in the standard cases.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnikku%2Fwuffle%2Fissues%2F28%3Femail_source%3Dnotifications%26email_token%3DADQ6CODKM7BNA4LEICKMK53P56ZOBA5CNFSM4H4SGJJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZKJ4EQ%23issuecomment-508861970&data=02|01|joanne.nolan%40sky.uk|83d6460db04d4341e4fb08d7018c615e|68b865d5cf184b2b82a4a4eddb9c5237|0|0|636979574748713914&sdata=0Wy7QfZvbNjVDkn0YNiB5qcKeHMVvPwDD4Pw1AelzR0%3D&reserved=0, or mute the threadhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADQ6CODPXCQIOFW3FAQI4SLP56ZOBANCNFSM4H4SGJJQ&data=02|01|joanne.nolan%40sky.uk|83d6460db04d4341e4fb08d7018c615e|68b865d5cf184b2b82a4a4eddb9c5237|0|0|636979574748723907&sdata=EjTjxe39C9KKswJdVAJwz6ZQY5pLNng%2FxCxyNAdzmgM%3D&reserved=0.

This email is from an external source. Please do not open attachments or click links from an unknown or suspicious origin. Phishing attempts can be reported by sending them to<EMAIL_ADDRESS>as attachments. Thank you

Information in this email including any attachments may be privileged, confidential and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you have received it in error, please notify the sender by return e-mail and delete it from your system. You should not reproduce, distribute, store, retransmit, use or disclose its contents to anyone. Please note we reserve the right to monitor all e-mail communication through our internal and external networks. SKY and the SKY marks are trademarks of Sky Limited and Sky International AG and are used under licence.
Sky UK Limited (Registration No. 2906991), Sky-In-Home Service Limited (Registration No. 2067075), Sky Subscribers Services Limited (Registration No. 2340150) and Sky CP Limited (Registration No. 9513259) are direct or indirect subsidiaries of Sky Limited (Registration No. 2247735). All of the companies mentioned in this paragraph are incorporated in England and Wales and share the same registered office at Grant Way, Isleworth, Middlesex TW7 5QD


[BUG] setForcedDecision does not work after update to version 3.0.1

Is there an existing issue for this?

[X] I have searched the existing issues

SDK Version
@optimizely/react-sdk: 3.0.1
Current Behavior
After calling setForcedDecision, useDecision(name, { autoUpdate: true }) is updated.
Expected Behavior
useDecision returns the latest data
Steps To Reproduce

Initialise Optimizely instance

optimizelyInstance = createInstance({
        sdkKey: env.OPTIMIZELY_SDK_KEY,
        odpOptions: {
               disabled: true,
        },
        logLevel: env.IS_VERBOSE ? 1 : 4,
});

optimizelyInstance.onUserUpdate((a) => {
      optimizely.setForcedDecision({ flagKey: "flag1" }, { variationKey: "variation1" });
});

In React

const [decision] = useDecision("flag1", {
    autoUpdate: true
});

React Framework
No response
Browsers impacted
No response
Link
No response
Logs
No response
Severity
Blocking development
Workaround/Solution
No response
Recent Change
No response
Conflicts
No response

Let me loop back to this.  I'm working to finalise #255

Hey there! Was going to write up an issue about this same topic. Currently on v3.1.0 and was running into issues forcing a user into a variation and wasn't sure if this is related to the same bug or not, but thought I would post it here.
We are currently writing a light wrapper around the useDecision react hook so that we do things like pass overrides and also have logic to force decisions before calling the useDecision hook.
Here is a simplified version of what our wrapper looks like:
function useDecisionWrapper(featureKey, options, overrides){
  const { optimizely } = useContext(OptimizelyContext);

  const [decisionContext, forcedDecision] = getForcedDecisionOverrides(featureKey); // grabs data from cookies to force a decision
  if(decisionContext && forcedDecision){
      const user = optimizely.getUserContext();
      user?.setForcedDecision(decisionContext, forcedDecision);
  }

  return useDecision(featureKey, options, overrides);
}

I'd assume that since we called setForcedDecision for the current user, calling useDecision would respect the forced decision but it seems to be not. Would love some feedback or suggestions if I am doing something wrong!  I will also test v3.1.0 tomorrow! Thank you :)

I did a quick code dive and see that in the JS SDK, decide() finds and should use a matched forced decision.
I've created an internal ticket (FSSDK-10120) to trace.

Hey there @mikechu-optimizely! Just wanted to follow up on some findings I did today.
While playing around with the APIs, one interesting thing I found was that calling .decide() from the userContext object seems to force users into a decision as expected, but calling .decide() from the optimizely instance does not.
Example below shows us calling both user.decide() and optimizely.decide() and seeing different results
 optimizely = createOptimizelyInstance({
    sdkKey,
    datafile,
    datafileOptions: {
      autoUpdate: isServerSide ? false : true,
      ...datafileOptions,
    },
    logLevel: 'DEBUG',
    eventDispatcher: IS_PROD || enableTracking ? eventDispatcher : logOnlyEventDispatcher, // always enable tracking in prod
    odpOptions: { disabled: true }, // only needed if advanced audience targeting is on
    ...config,
  });

    const user = optimizely.getUserContext();
    user.setForcedDecision({ flagKey: "migration_initial_flag", ruleKey: 'initial_experiment' }, { variationKey: "off" });
    optimizely.setForcedDecision({ flagKey: "migration_initial_flag", ruleKey: 'initial_experiment' }, { variationKey: "off" });

    const optimizelyDecision = optimizely.decide('migration_initial_flag');
    const userDecision = user.decide('migration_initial_flag');

    console.log('optimizelyDecision', optimizelyDecision);
    console.log('userDecision:', userDecision);

The results of the console log are as followed:
optimizelyDecision:
{
    "variationKey": "on",
    "enabled": true,
    "variables": {},
    "ruleKey": "initial_experiment",
    "flagKey": "migration_initial_flag",
    "userContext": {
        "id": "e9b20618-732d-478e-9a9e-237496274489",
        "attributes": {
            "grx_internal_user": false,
            "location": "",
            "$opt_user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36",
            "environment": "dev",
            "url_path": "/feature"
        }
    },
    "reasons": []
}

userDecision

{
  "variationKey": "off",
  "enabled": false,
  "variables": {},
  "ruleKey": "initial_experiment",
  "flagKey": "migration_initial_flag",
  "userContext": {
      "_qualifiedSegments": null,
      "optimizely": {}, //removed because its too big
      "userId": "e9b20618-732d-478e-9a9e-237496274489",
      "attributes": {
          "grx_internal_user": false,
          "location": "",
          "$opt_user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36",
          "environment": "dev",
          "url_path": "/feature"
      },
      "forcedDecisionsMap": {
          "migration_initial_flag": {
              "initial_experiment": {
                  "variationKey": "off"
              }
          }
      }
  },
  "reasons": [
      "Variation (off) is mapped to flag (migration_initial_flag), rule (initial_experiment) and user (e9b20618-732d-478e-9a9e-237496274489) in the forced decision map."
  ]
}

As we can see, calling user.decide() respects the call to setForcedDecision but optimizely.decide() does not respect the setForcedDecision call. This is important because the underlying implementation of the useDecision react hook uses optimizely.decide() (Reference in Hooks.ts)
Any guidance or insight to successfully getting the useDecision hook to respect forced decisions would definitely be appreciated 🙏🏽

Thanks for code diving with me.
I see in the underlying JS SDK that the OptimizelyUserContext.decide snags a copy of the current userContext with the forced decisions (if present) on its way into the client's decide() method.
So yeah, that's our difference.
🤔: React SDK's use of the client decide() instead of the user context's method means that forced decisions are not returned by the useDecision hook.   I think this may have been by design at some point.  I need to talk with our architect on this point since it's a public facing design.

forced decisions is very important for automated tests and other quality assurance processes to make sure feature is working in production manually before starting gradual rollout. its been more than 5 months since issue was filed and last communication on the matter.
Its frustrating and disappointing as a paying corporate customer to see important feature being broken for months without end in sight
@mikechu-optimizely do you mind to prioritise the fix for this once working feature?

I've pulled this Issue into today's stand-up.  I'll update here by COB.
cc @junaed-optimizely

We've pulled this issue & work ticket into this sprint.

A new release v3.2.1 is out with the fix.
@iamstarkov, @byron-ino let us know if an upgrade fix the issue for you.
Thanks for your patience.

I was also following this bug ^.^, I just tested my local project with the new version and works as expected 👍🏼 I hope others have the same outcome.  Thanks for the quick fix.

@junaed-optimizely @mikechu-optimizely thank you for a quick fix, we can confirm it works now

Thanks for the confirmation update. 🙏

The issue has been resolved and confirmed by the clients. Closing this issue now. Thanks everyone!


Extension causes high cpu load

Issue Type: Performance
Extension Name: vsliveshare-audio
Extension Version: 0.1.48
OS Version: Windows_NT x64 10.0.17134
VSCode version: 1.31.1

:warning: Make sure to attach this file from your home-directory: C:\Users\rajp4\ms-vsliveshare.vsliveshare-audio-unresponsive.cpuprofile.txt :warning:
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

@raj-pat Thanks for reporting this issue,
To help us investigate, can you please attach this file from your home-directory: C:\Users\rajp4\ms-vsliveshare.vsliveshare-audio-unresponsive.cpuprofile.txt to this issue?
Thanks

We believe this issue is fixed by a combination of 2 changes:

We switched to webpack to avoid excessive loading of many small modules.
We resolved an issue related to the use of the source-map-support module that made some errors result in an infinite loop processing the stack.

The first fix is already available in the latest version of the extension in the marketplace. The second fix will be available in the update to be published tomorrow.


Issue with other routes when adding links to the blogit template.

Firstly, great gem! However, I'm currently having trouble with my routes when I use the Gem. I'm trying to add paths to link the blog to other parts of my app but am getting errors such as;
     undefined local variable or method `destroy_user_session_path'

Not sure if this is definitely the BlogIt gem but it only seems to be happening in these views.
Suggestions would be great!
James


Add an .htaccess to the example for proper routing

This won't work for every web server, but there are options for many platforms. https://link.medium.com/Ng3zMVCYn9

Actually, never mind. Client side routing is just fine, and simpler to deploy.


Remove 'Phase 1' and 'Phase 2' from asynchrony support docs

When people search or want to read about async await in Dart, they find this page:
https://www.dartlang.org/articles/language/await-async
It says  "Dart Language Asynchrony Support: Phase 1" and is dated 2014. It looks like we're not done yet. I think the 'Phase' is an implementation detail at the moment, as we have full async support.
The second 'phase' is here:
https://www.dartlang.org/articles/language/beyond-async
Let's definitely remove the 'Phase', and either rename to something else (async/await vs */yield) or merge the two phases into one doc. The resulting doc(s) should probably be in the language tour.
Alternately, just add a big link to https://www.dartlang.org/guides/language/language-tour#asynchrony-support from the top of both these articles.

cc @kwalrath

This has been updated in the docs. Phase 1 is now a codelab. Phase 2 is gone. Neither mention phases. Closing.


Added Service Point Manager call to force Tls12.

PR Summary
Calls [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 during bootstrap to download PowerShell core to avoid following error.
PS C:\Users\dlbm3\source\repos\PowerShell> Start-PSBootstrap
Installing PowerShell build dependencies
dotnet is already installed.  Skipping installation.
pwsh.exe not found. Install latest PowerShell Core release and add it to Path
VERBOSE: Destination: C:\Users\dlbm3\AppData\Local\Microsoft\powershell
VERBOSE: About to download package from 'https://github.com/PowerShell/PowerShell/releases/download/v6.0.1/PowerShell-6.0.1-win-x64.zip'
Invoke-WebRequest : The request was aborted: Could not create SSL/TLS secure channel.
At C:\Users\dlbm3\source\repos\PowerShell\tools\install-powershell.ps1:139 char:9
+         Invoke-WebRequest -Uri $downloadURL -OutFile $packagePath
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] User-facing Documentation needed

[ ] Issue filed - Issue link:

Testing - New and feature

[x] Not Applicable or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

I think I have addressed all the review comments.

Please note that there is another Invoke-WebRequset call at line 181:
Invoke-WebRequest -OutFile "~/.rcedit/rcedit-x64.exe" -Uri $rceditUrl

This call downloads rcedit-x64.exe from github.

@daxian-dbw comments still need to be addressed.

Moved the code to the outer try and finally block as requested.


[🔥] Internal tools redesign and config feature flags display

📲 What
An absolutely fantastic redesign of the Internal tools screen, if I say so myself.
Displaying the config's feature flags in the Feature Flags screen.
🤔 Why
So we know what the current config's feature flags are and for fun.
🛠 How

build.gradle had a method that allegedly was the commitTime but it just got the current date and cached it? So I made it actually return the time the build was created. It doesn't get cached because we want the most recent build date.
Renamed FeatureFlagActivity to FeatureFlagsActivity.
FeatureFlagsActivity now displays all the config's Android flags with a cute lil decoration and any overrides.
InternalToolsActivity got a redesign.

It now properly displays the Build Date.
It now displays the API Endpoint.

I wrote tests but we don't run tests on the internal builds in Circle 🤕

👀 See

Internal tools after 🦋
Internal tools before 🐛

Feature flags after 🦋
Feature flags before 🐛

📋 QA
Plz note
The android_native_checkout flag is not currently being read because the feature isn't done 🙂
Check out the Internal Tools from the drawer of an Internal build!
Story 📖
NT-345

@yatriks should creating an internal release run the internal tests? right now it runs the external tests only


[AutoPR adhybridhealthservice/resource-manager] [Portal Generated] Review request for Microsoft.ADHybridHealthService to add version 2014-01-01

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4880

This PR has been merged into https://github.com/Azure/azure-sdk-for-java/pull/2775


refactor:support inspecting envelope

Codecov Report

Merging #349 (f97951f) into cose (f88bb1b) will increase coverage by 0.42%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##             cose     #349      +/-   ##
==========================================
+ Coverage   30.11%   30.53%   +0.42%
==========================================
  Files          25       26       +1
  Lines        1647     1657      +10
==========================================
+ Hits          496      506      +10
  Misses       1138     1138
  Partials       13       13

Impacted Files
Coverage Δ

cmd/notation/push.go
21.91% <0.00%> (ø)

cmd/notation/verify.go
17.92% <0.00%> (ø)

internal/envelope/envelope.go
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Cannot post https request on run release flutter

Steps to Reproduce

Run flutter in debug mode http/https call get/post works fine
Run Flutter in Release mode it will never send any nework request.
only to find-out that I need to add <uses-permission android:name="android.permission.INTERNET"/> in AndroidManifest.xml

my question is if that is mandatory, why that is not made mandatory for debug release as well and it can spit an exception/error that it is required.
I waste my whole 1day to find the issue.
if everything works in debug-mode without any error as a developer/user I will assume that everything is okay to build the same for release mode.

my question is if that is mandatory, why that is not made mandatory for debug release as well and it can spit an exception/error that it is required.

this issue doesn't seem to describe a bug or a feature request

then what it describes, if it is not a bug, if the app runs fine in debug mode, it should work the same in release mode. [...]

@pkjoshisbp
I believe that the situation you are describing is intended and not a bug,
it seems to me that your original post you are asking why this is intended

I waste my whole 1day to find the issue.
if everything works in debug-mode without any error as a developer/user I will assume that everything is okay to build the same for release mode.

I'm sorry you "wasted a day", but this is clearly stated in the documentation

Additionally, in your AndroidManifest.xml file, add the Internet permission.
<!-- Required to fetch data from the internet. -->
<uses-permission android:name="android.permission.INTERNET" />

Hi @pkjoshisbp
This issue doesn't seem to describe a bug or a feature request. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


[WebAPI] Test Integration for Upstream Batterystatus

BUG=https://crosswalk-project.org/jira/browse/CTS-309
Impacted tests(approved): new 11, update 4, delete 2
Unit test platform: Crosswalk for Android 21.51.544.0
Unit test result summary: pass 12, fail 3, block 0
Delete Reason: Split the two files into eight new test files.
Fail Reason: Test result is the same as Upstream result and https://bugs.chromium.org/p/chromium/issues/detail?id=401553

LGTM


Compose-Desktop: When a TextField exceeds 300 lines, there is a noticeable lag when editing

The current TextField isn't designed for big texts. If you need to show a lot of lines, you should write/find another implementation, use LazyList + TextField, or wait for TextField2 (it may solve the issue, we are not sure yet)
One of the reasons - it stores the state in immutable String. For large texts, the state should be represented by something like a gap buffer.
Only reproduced lags with 3000 lines:
import androidx.compose.material.TextField
import androidx.compose.runtime.getValue
import androidx.compose.runtime.mutableStateOf
import androidx.compose.runtime.remember
import androidx.compose.runtime.setValue
import androidx.compose.ui.window.Window
import androidx.compose.ui.window.application

fun main() = application {
    Window(onCloseRequest = ::exitApplication) {
        var state by remember { mutableStateOf(
                (1..3000).map { "aaaaaaa aaaaaaaaaa a aasdgfsd gdsg dsfg dfagfd gsdfg sfd gdsfg dsfg sdgdfs gdsfg sdfg sdg dzfg df gdfg" }
                        .joinToString("\n")
            )
        }
        TextField(
            state,
            { state = it }
        )
    }
}

3000 lines:
https://github.com/JetBrains/compose-multiplatform/assets/5963351/001d880f-0662-43f5-8aba-d39f76545e1c
100 lines:
https://github.com/JetBrains/compose-multiplatform/assets/5963351/e9488c61-3f7a-4b1f-bc34-ab561e16464c
(Windows 11, OpenJDK 20, Intel i9 13900K)
Leave the issue open, until Compose has a widget capable to work with a large amount of text

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Implement a package "REPL" like Julia has

Julia has this feature in the REPL where you press ] to enter the package mode, and then you can modify your environment.
It would be quite easy to do something similar for mamba, where instead of one-shot commands one would stay in a REPL and execute the same commands in the REPL.
The benefit is that we don't need to reload package / repository data into memory so everything will feel super-snappy.

@certik 's https://github.com/certik/terminal has the necessary features for this so we're definitely going to make the switch.

Cool! I can help polish it.  Please report any bugs, or if you want to change any design or API.
On Thu, May 14, 2020, at 1:54 AM, Wolf Vollprecht wrote:

Screenshot from 2020-05-14 09-50-55
https://user-images.githubusercontent.com/885054/81908001-e834e580-95c8-11ea-95ac-55b07dca9452.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/QuantStack/mamba/issues/234#issuecomment-628460785, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAFAWGNVAKCCT5ZIIYBZFDRROPURANCNFSM4M7RJAFA.

Also let me know if you want to move it to some organization at github rather than my username.


Add a user-friendly client

There's a client implementation which we use in tests but it requires creating the async bind to the local server object. Would be better to introduce a first-class client capable of remote connection.

would love to see a client, claude is so expensive


HTML Entity

The line numbers are incorrect when using HTML entitys such as  .
Test.md
| github‑token | Token to use to authorize. | ${{ github.token }} |
| file‑json | JSON file containing the list of files to check. | ${{ file-json }} |
| files‑changed | List of files to check. | ${{ files-changed }} |

spellchecker test.md --reports test.json

test.json
[
    {
        "data": {},
        "messages": [
            {
                "message": "`github‑token` is misspelt",
                "name": "test.md:1:3-1:15",
                "reason": "`github‑token` is misspelt",
                "line": 1,
                "column": 3,
                "location": {
                    "start": {
                        "line": 1,
                        "column": 3,
                        "offset": 2
                    },
                    "end": {
                        "line": 1,
                        "column": 15,
                        "offset": 14
                    }
                },
                "source": "retext-spell",
                "ruleId": "github-token",
                "file": "test.md",
                "fatal": false,
                "actual": "github‑token",
                "expected": [],
                "url": "https://github.com/retextjs/retext-spell#readme"
            },
            {
                "message": "`file‑json` is misspelt",
                "name": "test.md:1:72-1:81",
                "reason": "`file‑json` is misspelt",
                "line": 1,
                "column": 72,
                "location": {
                    "start": {
                        "line": 1,
                        "column": 72,
                        "offset": 71
                    },
                    "end": {
                        "line": 1,
                        "column": 81,
                        "offset": 80
                    }
                },
                "source": "retext-spell",
                "ruleId": "file-json",
                "file": "test.md",
                "fatal": false,
                "actual": "file‑json",
                "expected": [],
                "url": "https://github.com/retextjs/retext-spell#readme"
            },
            {
                "message": "`JSON` is misspelt; did you mean `JASON`, `JON`, `SON`?",
                "name": "test.md:1:84-2:2",
                "reason": "`JSON` is misspelt; did you mean `JASON`, `JON`, `SON`?",
                "line": 1,
                "column": 84,
                "location": {
                    "start": {
                        "line": 1,
                        "column": 84,
                        "offset": 83
                    },
                    "end": {
                        "line": 2,
                        "column": 2,
                        "offset": 87
                    }
                },
                "source": "retext-spell",
                "ruleId": "json",
                "file": "test.md",
                "fatal": false,
                "actual": "JSON",
                "expected": [
                    "JASON",
                    "JON",
                    "SON"
                ],
                "url": "https://github.com/retextjs/retext-spell#readme"
            },
            {
                "message": "`file-json` is misspelt",
                "name": "test.md:2:53-2:62",
                "reason": "`file-json` is misspelt",
                "line": 2,
                "column": 53,
                "location": {
                    "start": {
                        "line": 2,
                        "column": 53,
                        "offset": 138
                    },
                    "end": {
                        "line": 2,
                        "column": 62,
                        "offset": 147
                    }
                },
                "source": "retext-spell",
                "ruleId": "file-json",
                "file": "test.md",
                "fatal": false,
                "actual": "file-json",
                "expected": [],
                "url": "https://github.com/retextjs/retext-spell#readme"
            }
        ],
        "history": [
            "test.md"
        ],
        "cwd": "C:\\Users\\auste\\source\\spellchecker-cli-action-summary",
        "contents": "| github‑token | Token to use to authorize. | ${{ github.token }} |\r\n| file‑json | JSON file containing the list of files to check. | ${{ file-json }} |\r\n| files‑changed | List of files to check. | ${{ files-changed }} |",
        "value": "| github‑token | Token to use to authorize. | ${{ github.token }} |\r\n| file‑json | JSON file containing the list of files to check. | ${{ file-json }} |\r\n| files‑changed | List of files to check. | ${{ files-changed }} |\n"
    }
]

Result
Word
Line Start
Line End
Line Start Expected
Line End Expected

✅
github‑token
1
1
1
1

❌
file‑json
1
1
2
2

❌
JSON
1
2
2
2

✅
file-json
2
2
2
2

Thank you for reporting this!
I won't have time to investigate this in the near future. Feel free to dig into it if you're interested.
I expect this is a problem with one of the libraries that Spellchecker CLI uses to spell-check Markdown files, namely remark, remark-retext, and retext-spell.


Add enable link to Status > UPnP & NAT-PMP error message if disabled (Todo #6689)

@doktornotor please do not update .pot file manually. When it's required, just add a note on PR and I can run script to re-generate it after merge

Oh, you have a script now? Great to know, I'd rather never touch the giant blob again, it's a big pain.

@doktornotor yes, it's on ./tools/scripts/update_pot.sh :)

@rbgarga - Grrrh... should have known earlier. Definitely will avoid touching the pot thing in future, thanks for the pointer.


Split the JSInterop Blazor topic

Currently, the JavaScript Interop topic is quite long and has two main subsections:

Invoke .NET methods from JavaScript functions
Invoke JavaScript functions from .NET methods

It would be great to turn these into separate articles under JavaScript Interop node in the TOC.
@guardrex I know we've talked in a separate thread that a flat list under Blazor would be fine, but treat that as a the first step. So let's turn these two into separate topics.

There's common content, so we need an overview topic to go with them. It's also best if we create the TOC node (folder) now because I can't change the UID later when topics are moved into a node (folder) without a lot of pushback from the docs cats. No worries if we just set it up with a node/folder now. Because the advanced scenarios and common content require a simple/quick explanation first, the node could go something like this ...

JS interop

Overview

Introduction
Simple/quick example of invoking .NET method
Simple/quick example of invoking JS FN
Common JS interop content

Invoke .NET methods from JavaScript functions
Invoke JavaScript functions from .NET methods


React Native Support

Hi Holowaychuk ,
I dont know how to use heatmap in react native android and ios.Can you please help me to solve this.If i any related link that may be useful for me.Thanks in advance.

Unlike web browsers, React Native does not support SVGs natively. You will need to use another vector graphic library, like ReactNative SVG.
There a few good articles there that talk about using d3 in react native. Unfortunately, you will not be able to use this library but you can mimic the source code with another SVG library.


DRAFT ONLY PR to merge mepblockcodemilo fix for useblockcode into meppostlcp

DRAFT ONLY
Test URLs:

Before: https://main--milo--adobecom.hlx.page/?martech=off
After: https://mepblockcodemilo--milo--adobecom.hlx.page/?martech=off

will wait until after meppostlcp is merged to create a pr for this branch.


Add Lwt jobs bindings

Add Lwt job variants of the functions in Osx_attr.
These are implemented by abstracting over the monad in the module that wraps the generated bindings, which leads to less duplication (but perhaps not more clarity) than a more direct implementation.
This PR also changes the existing bindings to use the new errno support in Ctypes 0.6.0.

Cool! Thanks!


19/lp

rough draft of passive lp
a few things i still need to clean up

use all checked_add/sub/mul/div ...
burn a portion of lp tokens
decompose remove_liquidity to settle_liquidity for settling without burning tokens
change OpenPosition ctx
checking margin requirements
impl js sdk functions
more js tests
....

still todo

lp can add additional tokens to an already open lp position
lp can burn a portion of their tokens
js tests + sdk functions

test settle fcn


Access AC and AdminServer with private IPs

When the dashboard is acting as a client, it shouldn't assume that the controller and AdminServer are accessible via the public internet.

http://ocd.appscale.net:8080/job/Daily Build/6121/


Add HorizontalPodAutoscaling behavior fields to UI form

Is your feature request related to a problem? Please describe.
Kubernetes added additional functionality to HorizontalPodAutoscalers to configure the autoscaling behavior. This has been stable since Kubernetes 1.23.
These new fields should also be configurable through the HPA edit form and displayed on the HPA detail page
Describe the solution you'd like

Add form fields to edit the autoscaling behavior in the HPA edit form
Add autoscaling behavior information on the HPA detail page

Additional context
Documentation https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#configurable-scaling-behavior
API Reference https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/horizontal-pod-autoscaler-v2/#HorizontalPodAutoscalerSpec

Confirmed the expected Behavior-related form and detail views were visible.
Was able to:

Create an HPA with Behavior fields
Modify Behavior fields on an existing HPA
Create an HPA outside of Rancher and view the full details in Rancher's UI

HPA Create:

HPA Detail:

HPA Edit:


On iOS 11 (chrome and safari) the cursor jumps out of a form field in a tiny modal

***This probably needs to be moved to Semantic-Org/Semantic-UI ***
Steps
Create a tiny form with two fields in a tiny modal
https://codesandbox.io/s/x93kj2pn3p
Expected Result
User can edit the field and the cursor is visible within the field (works on desktop)

Actual Result
On a phone, the field cursor is displayed outside of the field input field (you have to try it form an actual phone, resizing chrome or safari to fit the phone's screen dimensions won't work). Also, this issue doesn't seem to occur as often on simulators (however, I always get it on my iphone and my coworkers' iphones).
This might be related to https://hackernoon.com/how-to-fix-the-ios-11-input-element-in-fixed-modals-bug-aaf66c7ba3f8

Workaround
Hide components behind modal to ensure body size < modal height
Version
0.75.1
Testcase

Hi @arsanjea have you tried putting your Button inside a Modal.Actions component instead of inside the Modal.Content? Structurally with the markup/styles I think this is causing some of your issues.
      <Button type="submit" content="I'm in!" color="orange" />
    </Modal.Actions>```

Hm, seems the blog post you've linked shows the root issue.  Being that this is both a CSS issue and an iOS issue, I'll close this for now.  We don't have control over either of those here.

***This probably needs to be moved to Semantic-Org/Semantic-UI ***

Yes sir 😉

@levithomason
Where is the equivalent issue on Semantic-Org/Semantic-UI?
Not found at least in searching https://github.com/Semantic-Org/Semantic-UI/search?utf8=✓&q=modal+ios&type=Issues
Is this fixed in the framework side?

@karak I have not looked in SUI for a similar issue for this, but this is actually a bug in Mobile Safari in iOS 11.2 which means unfortunately that we are waiting for Apple to fix it. Here's a link to the relevant Webkit bug report for anyone else landing here: https://bugs.webkit.org/show_bug.cgi?id=176896
The good news is that from what I've been seeing, people are verifying that this is resolved in the iOS 11.3 release, which is still currently in beta. We're basically waiting for that to come out. There are ways to hack around this but they are pretty messy, and they will likely not display the way you want after this is fixed.


Night CI 2023-07-16: Failed

action url: https://github.com/spidernet-io/egressgateway/actions/runs/5569528480

dup https://github.com/spidernet-io/egressgateway/issues/592


Add support for using existing LA workspace

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description
Is your feature request related to a problem?
Several customers have reported that they want the module to work with an existing LA workspace ID. This is cumbersome to override using either archetype extensions or archetype_config_overrides.
The following policies need parameters changing:

Deploy-ASC-Monitoring
Deploy-MDFC-Config
Deploy-AzActivity-Log
Deploy-LX-Arc-Monitoring
Deploy-Resource-Diag
Deploy-VM-Monitoring
Deploy-VMSS-Monitoring
Deploy-WS-Arc-Monitoring

And then there's the role assignments on the LA workspace...
Describe the solution you'd like
Provide input variables to allow use of an existing workspace, which would simplify the policy parameters here.
Also optionally create role assignments on the LA workspace (as it may be outside the scope of the intermediate root MG)
Additional context

Possible with
``terraform
module "enterprise_scale" {
#...
configure_management_resources = {
advanced = {
existing_log_analytics_workspace_id = "/providers..."
}
}
}


Improve localization guide

This PR improves localization guide.

Introduce two parts

Initiate a new localization team
Get involved in an existing localization team

More examples
Note regarding permission
...

Preview for review
https://github.com/cncf/glossary/blob/38bf7501dc9aea02696a1a6e8d48b74074c670c1/LOCALIZATION.md


Weird Background behind some text

Issue description
Don't know why but some badges have weird backgrounds behind them
Only affects the compact badges

[x] C
[x] C++
[x] C#
[x] Kotlin
[x] PHP
[x] Tauri
[x] TypeScript
[x] docs.rs
[x] Jira

Issue priority
Low (slightly annoying)

Will be pushed soon


Installing on osx with homebrew libgroove fails

I tried installing libgroove using homebrew with
brew install libgroove
This installs fine, but when I tried to install waveform it kept complaining about the missing groove.h. It seems like node-gyp wants these libraries to be linked into /usr/X11 for some reason and they are not there by default after installing via brew. After running these commands
sudo ln -s /usr/local/Cellar/libgroove/4.3.0/lib/libgroove.dylib /usr/X11/lib/
sudo ln -s /usr/local/Cellar/libgroove/4.3.0/include/groove /usr/X11/include/

npm install waveform ran without a problem.
Maybe a mention in the readme for installing on osx via homebrew? or leave this issue in case someone else has this problem.
Thanks!

/usr/X11 is a strange place for libgroove files to go. I'm guessing that is just one of many directories that your build environment is searching for headers. Ideally it would also be searching Cellar and when homebrew installs libgroove it would put the headers and libraries in the appropriate place. This seems like a problem with homebrew or the libgroove homebrew package.

I'm having the same problem but for a missing png.h. I definitely installed libpng. How'd you find out where node-gyp wants the libraries to be linked into?

I'm getting errors once I run npm install waveform --save too. After installing libgroove via homebrew. I get the error Requiring unknown module "path". I am also trying to use this package for a React Native project, so I'm not sure if that is causing an issue as well. Below are some screenshots.


Fix form component support non fieldset HubSpot forms

Fixes: https://github.com/pulumi/docs/issues/4905
The form component was throwing an error because the Newsletter form doesn't have a fieldset element on it so the code thought it never existed. Fortunately, this did not cause any user interruption outside of an error being logged to the console. This PR fixes up the selector that is used to wait for the form to load so that both types of HubSpot forms are supported.
Also while I was in here, Wendy had suggested we order our events in ascending order on the resources page so that is included here as well.

@cnunciato I added some javascript to support only order in ascending order on the upcoming tab. I was initially hesitant to add JS to the page that was not in a stencil component, but I think if we want this sort of logic to be in a stencil component we should file a separate issue. I think for this PR (and for the sake of progress) this is fine as-is.

@cnunciato I added some javascript to support only order in ascending order on the upcoming tab. I was initially hesitant to add JS to the page that was not in a stencil component, but I think if we want this sort of logic to be in a stencil component we should file a separate issue. I think for this PR (and for the sake of progress) this is fine as-is.


Catlin Corrales

{
     "preferred_name": "Cat",
     "csulb_email"<EMAIL_ADDRESS>     "pronouns": "she/her/hers",
     "previous_gis_experience": "B.S. in Environmental Spatial Analysis from the University of North Georgia, GIS Intern for the Chattahoochee Riverkeeper, GIS Intern for Golden State Water Company",
     "previous_remote_sensing_experience": "Undergraduate coursework and research projects",
     "previous_programming_experience": "Introduction to Python course",
     "github_repo_link": "https://github.com/CMCcat/CmcRepo",
     "github_project_link": "https://github.com/users/CMCcat/projects/1",
     "what_you_hope_to_get_out_of_this_class": "I would like to learn more about data acquisition, Deep learning OBIA, and Python programming for RS",
 }

Lab 1: https://github.com/CMCcat/CmcRepo/blob/main/Corrales_GISC606_Lab1.ipynb

Lab 2: https://colab.research.google.com/drive/1-T-Wq8yzvD3UYCOFh5UDTM0gm4p9aRoL?usp=sharing

Lab 4: https://github.com/CMCcat/CmcRepo/blob/main/Corrales_L4.ipynb

Lab 5: https://cmccat.github.io/lab5/


Component Design Audit v1.1

Date Picker

Update icons in calendar

Time Picker

text-03 for placeholder text

Space should be 2px

Should be 16px on both sides of chevron

Light

should be using field-02 color

Dropdown

Update padding to 16px on left/right, vertically centered text

Needs hover state

Rulers need to not show on hover

When open, label should change color to match spec

focus outline should be against the sides of the menu

remove bottom margin from label when helper text is present

should return back to field-01 when not hovered

should keep field-01 rule when open

border bottom color should persist (gray-20, not gray-50) ui-03

show selected state (selected-ui token)

busted focus (react)

change height to 320px(ish)

look into shadow colors

Inline

No bar should be present

should have hover state

15px on left-hand side

height should be 32px

text alignment between field and options

Link

Focus should be box

Should use visited color token

link should not navigate if disabled

Inline Loading

Loading icon needs update

Text should be 8px away from loader

Weird issue with gray, it disappears after changing loading state

Search

Close icon should be icon-01

background color on x on hover (hover-ui)

Overflow Menu

menu color should be ui-01

menu options should overflow with ellipsis

change to text-01 on hover (should be in dropdown too?), text should be text-02 (darken on hover)

Radio Button

Focus state on un-selected needs to not have black stroke

double-check that vertical has 8px of spacing between each

Select

Select should have hover state

Tabs

Update width of bottom portion of tab (border-bottom) to 3px

2px space between tabs (versus 1px)

See if we can keep type alignment between tabs and content

Tile

square icon in corner

--
Misc

Change examples to sentence case

👍 🌮

[ ] Date picker
[ ] Dropdown
[ ] Link
[ ] Inline loading
[ ] Search
[ ] Overflow menu
[ ] Radio button
[ ] Select
[ ] Tabs
[ ] Tile

@asudoh I will be updating your comment with links to PRs as I open them

I think there needs to be clearer distinction between React component issues and vanilla component issues. It takes a nontrivial amount of time to make comparisons between the two implementations when it is ambiguous which variant the issues are referring to, especially for those who were not present during the auditing session

all comments addressed in https://github.com/IBM/carbon-components/issues/1749#issuecomment-461706343 or superseded by Feb/Mar 2019 audits