ERR_CLEARTEXT_NOT_PERMITTED

Using webview_flutter: ^0.3.2+1
I get ERR_CLEARTEXT_NOT_PERMITTED for Android and blank page for iOS when I use
http://  urls. https:// urls seems to work.
The very same http:// urls works fine in Chrome.
I recall I had the same problem in native Android as well.
Is possible to tell webview "please use http://. I will take the risk"
Thanks in advanced

Open the android manifest file (android/app/src/main/AndroidManifest.xml) and add
android:usesCleartextTraffic="true"

to the application tag
<application
        android:name="io.flutter.app.FlutterApplication"
        android:label="tangerine_ui"
        android:icon="@mipmap/ic_launcher"
        android:usesCleartextTraffic="true">

Thanks for you replay.
I have tried that but got the same result and I guess it only help Android. iOS just shows a white screen.
My solution was to open HTTPS in webview and HTTP in an external browser.
Good enough

For IOS, you need to modify the info.plist (ios/Runner/info.plist)
Add the following:
<key>NSAppTransportSecurity</key>
<dict>
	<key>NSAllowsArbitraryLoads</key>
	<true/>
</dict>

You may need to be more explicit with the whitelist of http domains you need to support before releasing to the Apple Store.
<key>NSAppTransportSecurity</key>
<dict>
    <key>NSExceptionDomains</key>
    <dict>
        <key>yourdomain.com</key>
        <dict>
            <!--Include to allow subdomains-->
            <key>NSIncludesSubdomains</key>
            <true/>
            <!--Include to allow HTTP requests-->
            <key>NSTemporaryExceptionAllowsInsecureHTTPLoads</key>
            <true/>
            <!--Include to specify minimum TLS version-->
            <key>NSTemporaryExceptionMinimumTLSVersion</key>
            <string>TLSv1.1</string>
        </dict>
    </dict>
</dict>

+1
Using webview_flutter: ^0.2.0
device is PCT AL10  • 46HDU19403003831                     • android-arm64 • Android 9 (API 28)
when I use https://baidu.com   is Ok
when I use https://hao123.com  get ERR_CLEARTEXT_NOT_PERMITTED error
when I use  https://github.com is ok

As far as i can tell this is still an issue in flutter. The usesCleartextTraffic works in native development but with flutter the 'ERR_CLEARTEXT_NOT_PERMITTED' persists.

I am seeing the same issue as @fideldonson in my flutter application when trying to run on an android device

any solution for this?

@noninoraikhah @werainkhatri @chrispruitt @fideldonson
Try with this Medium article, it's working for me.
<EMAIL_ADDRESS>

In case you wish to resolve it from the website code side (For people with less hands-on with android coding) following tutorial helped :
err_cleartext_not_permitted
This basically explains the basic issue on why this error pops up rather than workaround with android code.

Same Problem but i simply put https:   rather than http
Now its Working Fine
Try it May be Helpful

check this out https://stackoverflow.com/questions/55592392/how-to-fix-neterr-cleartext-not-permitted-in-flutter


Not all base64-encoded strings are azure keys

https://github.com/djmitche/taskcluster/commit/508879f341d47fc55c64805f55e4fdcdfffb6719#diff-6bec6ff2931ad8ff63611cd4919dd43eL810 is a 64-byte base64-encoded value produced by hmac with sha512.  It's not an Azure storage account key, as is the case for the vast majority of 64-byte base64-encoded values.  This is a false positive.

Hi @djmitche ,
Thanks a lot for your feedback, I am sorry that you received an email for a false positive.
I am currently working with the secrets detection team to improve our algorithm based on your feedback. I can assure you that the algorithm was triggered by multiple elements and not only by the presence of a base64-encoded value.

For reference: #5 was also a false positive for an: azure storage account key.
Mozilla/sops had been used to encrypt a secret string.


[skywalking-terraform][Feature] Add cluster coordinator deployment

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Now we assume the user already has a cluster coordinator running (for example, zookeeper), and set the env var (for example, SW_CLUSTER_ZK_HOST_PORT) to the coordinator's address when deploying a SkyWalking cluster using https://github.com/apache/skywalking-terraform, it would be much more convenient if we have an config option to also deploy the cluster coordinator in the skywalking-terraform project, currently we can only support zookeeper.
Some possible approaches to achieve this:

If we can find cloud service available on AWS (such as https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-zookeeper.html, not sure whether this works in our case), we can directly apply the service on cloud vendor using terraform and use it as a coordinator in the deployment, otherwise,
we have to create necessary EC2 instances, and deploy our own coordinator service on the EC2 instances,

Use case
When users want to deploy a cluster from scratch, they have to deploy a cluster coordinator first, then use the skywalking-terraform to deploy the cluster, this just works but it needs some extra manual work, we can provide an option to also deploy an coordinator (Zookeeper) in our ansible playbook, and create necessary EC2 instances in our terraform module.
Related issues
No response
Are you willing to submit a pull request to implement this on your own?

[ ] Yes I am willing to submit a pull request on my own!

Code of Conduct

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

@rabajaj0509 FYI

I am going to go ahead and try the service available on AWS first and see if that works out for us.


Create requirements.txt based on 89z's list

This library makes use of the new pyproject.toml which supercedes requirements.txt. Dependencies can be found in there instead. Reference - https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/


Documentation Overhaul

As I've been working on updating and improving FSharp.Formatting I've had some thoughts about how we can improve the experience of writing F# documentation, consuming documentation, and building tools to provide documentation.

Parity with C# Features
Improving editor tooling support to the level currently enjoyed by C# in Visual Studio should be the bare minimum that we shoot for.

Syntax/Tag Highlighting within the documentation comment

Completions for xml tags and paramaters, args, etc.

Auto-close xml tags

Fix Rendering Inconsitencies

F# does not follow the conventions used by C# for how it presents text in the documentation comments

Granted what C# does regarding the tooltip size is pretty terrible (and we should at least address the size by allowing the user to set a max height and width for the intellisense tooltips), within XML style documentation comments we should at least follow the rules regarding line breaks
Properly Support Listed XML Tags
Currently of the tags listed in the F# documentation the
only ones that currently work properly are <summary>, <exception>, and <para>. We should extend support to the set of tags that C# Supports -
<c> 	<para> 	<see>*
<code> 	<param>* 	<seealso>*
<example> 	<paramref> 	<summary>
<exception>* 	<typeparam>*
<include>* 	<remarks> 	<typeparamref>
<list> 	<returns> 	<value>

( * denotes that the compiler verifies syntax.)
<b> & <i> should also be supported in summary, remarks, example, etc.

Improve FCS API for Consuming Tooltips
I think the model that is used for the documentation data could be improved using something like -
  type ConstructCategory =
      | Keyword | Identifier | Operator | Preprocessor | Class
      | ValueType | Union | Record | Property| Enumeration
      | UnionCase | TypeArgument | Interface | Function  | Pattern

  type DocsFormat = Xml | Markdown

  type DocData = {
      Category : ConstructCategory
      Paramaters : string list
      TypeParamaters : string list
      Exceptions : string list
      Returns : string
      Format : DocsFormat
      Summary : string
      Example : string
      See : string
      Value : string
      SeeAlso : string
  }

Creating an individual data record type for each construct category is another option
so they only contain the relevant data.
I realize this is simalr to FSharpMethodGroupItemParameters, FSharpMethodGroupItem, etc. but I
think that we could have a better set of types to model this data oriented toward external
consumption.

Markdown Styled Documentation Comments
We're already working in an environment where F# Documentation comments are being parsed
for markdown so we should take better advatage of it
VsCode already supports markdown to great effect

But in Visual Studio it looks terrible

DocFx ( which is used to generate the official F# help documentation ) also already supports markdown
FSharp.Formatting parses comments for markdown to build webpages.
There are several disadvatanges to the ///

it makes reformatting comment contents difficult (e.g. indents)
not great for cut & paste
makes markdown usage ambiguous

I don't think that markdown style and xml style should be mixed which is why
markdown styled documentation comments could follow conventions similar to [the
ones that OcamlDoc uses]  (https://caml.inria.fr/pub/docs/manual-ocaml/ocamldoc.html#sec349) (** **)
 XCode's scope goes further than what i think is necessary, especially the callouts if markdown is going to be supported
This new style of documentation comments wouldn't be supported by DocFx straight out of the gate, but we can easily extend it to support whatever conventions we decide upon

Detailed Info Tool Window
I totally understand that building this tool window is out of scope for the F# VS tooling, but the point I'm trying to make is that we should make it easy to build this kind of tool even if it's included with VisualFSharp.
this is the tooltip for Async.OnCancel

This is the documentation comment in the signature file containing Async.OnCancel

That's some really useful information, it'd be great if we were able to see it in VS somehow, especially since we already have it in FSharp.Core.xml

Async sure does have a lot of methods, it'd be nice if we could see all of them and their respective documentation comments
Between the content of the xml files for the libraries and the metadata in the .dlls we could do a lot more to surface useful information to F# devs that's right
under their fingertips if only they knew how to look.
It would be like a much improved version of the Quick Help Inspector in XCode

References

 C# Xml Documentation
 F# Xml Documentation
XCode Markup Functionality
DocFx /// Code Comment Support
OCamlDoc Syntax

(BTW these aren't "I hope someone else will do this" suggestions, I'm more than willing to implement all of this myself)

Agreed, one fundamental problem is that we have not decided on a syntax yet. Is it markdown or xml? If both then how/where do we tell/detect the difference?

@matthid i was thinking it'd be like
///  <summary>
///  xml doccoms
/// </summary>

(**
   markdown doccom
**)

Both would be parsed and stored as xml like normal though. The conversion is pretty simple, ionide already converts from xml to markdown to create the tooltips
would be for xml and (** **)

I really like how Javadocs work and appear in the most used editors. So I would vote for Javadoc like styling.

This is something I miss very much from VS tooling.

The Quick Help Inspector in XCode  is really nice.
lot of additional MSDN docs is never shown, and will be good to have with a shortcut (not F1 😄 )

Tool window for docs would be awesome!
About markdown: Since there already exists codebase which uses markdown with /// comments, can't we just support it by default wherever it makes sense. I'm thinking exclude ,  and parse all the rest for markdown, with an option to turn this off?
Another feature I'd love to see is some linebreaks and formatting of overly long type and member signatures.

@majocha the existing markdown codebases will markdown doccoms will just have to update. Once there's a standard they can adjust to it. I'm a maintainer of most of the projects that make the most extensive use of it, so I can just fix those myself 😉


Manga Tagger & FMD start process

Manga Tagger might not be able to start FMD if it's already been started. Also, Manga Tagger should always close FMD BEFORE doing the FMD setting initialization if FMD is open. I'm not sure if Manga Tagger does this already so this should be checked.

Just a thought, but there may be problems integrating this into docker later once Linux support exists if the software relies on knowing exactly where FMD is to autoconfigure settings as needed. I am not sure if FMD could be packaged with this in docker, especially with programs like Wine being necessary. It is possible that in order to make the jump to docker, the software would have to operate completely separate to FMD and just depend on the user to make the adjustments as necessary.

Just a thought, but there may be problems integrating this into docker later once Linux support exists if the software relies on knowing exactly where FMD is to autoconfigure settings as needed. I am not sure if FMD could be packaged with this in docker, especially with programs like Wine being necessary. It is possible that in order to make the jump to docker, the software would have to operate completely separate to FMD and just depend on the user to make the adjustments as necessary.

So - the issue with dockerizing Manga Tagger is that it is entirely dependent on Free Manga Downloader, and since FMD cannot be dockerized, it defeats the purpose of putting Manga Tagger into a Docker container. Granted, it can be something to explore in the future if/when I make Manga Tagger compatible with any download(er), whether automatic or manual, but that will require users to have a more control over the software and probably wouldn't make sense to dockerize anyways.

So - the issue with dockerizing Manga Tagger is that it is entirely dependent on Free Manga Downloader, and since FMD cannot be dockerized, it defeats the purpose of putting Manga Tagger into a Docker container. Granted, it can be something to explore in the future if/when I make Manga Tagger compatible with any download(er), whether automatic or manual, but that will require users to have a more control over the software and probably wouldn't make sense to dockerize anyways.

Resolved with release v1.1.4-alpha

Resolved with release v1.1.4-alpha


make dictionary explanation clearer

Points from Rui:
That dictionaries are not accessed position-wise (e.g. mydict[3] does not look for the key at position 3)
That two dictionaries need not have keys in the same order (this was for the imdb exercise)
That keys can be associated with any type of values (list, integers, etc)

Looking at the teaching materials of 2022, I see you've done this. Good job :+1:


Reforged versions

Hi, where are the specs for Reforged?
Object data seems to have version 3 and something might have changed.

Hi @tdauth, was there a specific data issue you encountered? I suppose there were some updates recently, so I will have to review if the data format changed.

I have found this: https://github.com/stijnherfst/HiveWE/wiki/war3map(skin).w3*-Modifications the sets are new in Reforged.


Chore: update build process

Proposed changes
Utilize Webpack to build library
Types of changes
What types of changes does your code introduce to TwitchJS?
Put an x in the boxes that apply

[x] Chore (change that does not fix an issue or add functionality, but improves TwitchJS in some other way)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] My PR is named according to CONTRIBUTING doc
[x] Lint and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)
[x] Any dependent changes have been merged and published in downstream modules

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

I don't have much experience with webpack. so I won't be of any help here.

@mBeierl Fair enough. Thanks for letting me know.

Changes Unknown when pulling 772cf5c9506a54eadac924bdc1f5a5e97abf56d7 on chore/update-build into ** on master**.


Styles lost when passing as prop to SC extending React component that renders another SC

I have a styled component...
const Text = styled.p`
  font-family: cursive;
  font-size: 20px;
  text-decoration: underline;
`

...which is rendered in a React component...
const TextComponent = ({ children, ...props }) => {
  return <Text {...props}>{children}</Text>
}

...which is extended by another styled component (spreading props to pass the className)...
const RedText = styled(TextComponent)`
  color: red;
`

...which is then rendered and passed an as prop.
<RedText as="h1">I'm a red h1 but lose my initial styles</RedText>

All of the original styles from the Text styled component are lost, but the as prop works and the extended styles are kept.
I realise that I'm supposed to use the forwardedAs prop, rather than the as prop in this case, but I don't think passing an as prop should be losing all of the original styles(?). I'm not sure if the as props is even meant to work in this case, but somehow it does (even if I explicitly don't pass it along in the TextComponent React component).
This was an issue for me because I needed to refactor an existing styled component to be wrapped by a React component, and everything seemed okay at first, but then every now and then I started seeing styles being off in various places, and it took a lot of debugging to work out that the cause was due to passing an as prop instead of a forwardedAs prop.
Environment
codesandbox
Reproduction
https://codesandbox.io/s/heuristic-forest-3epo2?file=/src/App.js
Steps to reproduce
Create a styled component with some styles, a React component that renders it, another styled component that extends that, and then render that and pass it an as prop.
Expected Behavior
The styles in the first styled component remain, regardless of whether or not the as prop works (I think it's not supposed to work)
Actual Behavior
The styles in the first styled component get lost and the as prop works

as replaces whatever is in styled(X). It replaces the target, so if that's your component then it won't be mounted any longer

@kitten shouldn't it then also lose the styles if I extend the original styled component (instead of the React component) in that case? This seems to still work:
const Text = styled.p`
  font-family: cursive;
  font-size: 20px;
  text-decoration: underline;
`

const RedText = styled(Text)`
  color: red;
`

<RedText as="h1">I'm a red h1 and keep my initial styles</RedText>

Not quite; in the case of "nesting" StyledComponents all styles cascade and are combined. If you look at the render output you can see that the original component disappears and instead the wrapper composes its styles and combines them with the inner's styles

@emilioheinz I think the answer is to use forwardedAs instead of as

Yess, I have tried it and it works fine. Just forgot to mention here. Thanks!


Add field conversion for Patient - photo

Hey Paul! I added the photo field in the patient model class


Enhancement: Show timer duration in tooltip in Windows system tray

When I have a timer in the Windows system tray, I'd like to be able to mouseover the timer and see how long is left and the name of the timer (if there is one).
Nice to have: overlay icon indicator that shows a visual and/or symbolic representation of the remaining duration à la Dropbox.

Similar to: https://github.com/Dziemborowicz/Hourglass/issues/73

Thank you! Works like a charm.


Run GCO_UnitTest in windows

Is it possible to use this library in windows? I got the following error when compiling the library.
`Error using mex
C:\gco\GCoptimization.cpp:18:0: warning: "NOMINMAX" redefined
#define NOMINMAX
^
In file included from C:/MATLAB/SupportPackages/R2015b/MW_MinGW_4_9/lib/gcc/x86_64-w64-mingw32/4.9.2/include/c++/x86_64-w64-mingw32/bits/c++config.h:430:0,
from C:/MATLAB/SupportPackages/R2015b/MW_MinGW_4_9/lib/gcc/x86_64-w64-mingw32/4.9.2/include/c++/bits/stl_algobase.h:59,
from C:/MATLAB/SupportPackages/R2015b/MW_MinGW_4_9/lib/gcc/x86_64-w64-mingw32/4.9.2/include/c++/vector:60,
from C:\gco\GCoptimization.cpp:8:
C:/MATLAB/SupportPackages/R2015b/MW_MinGW_4_9/lib/gcc/x86_64-w64-mingw32/4.9.2/include/c++/x86_64-w64-mingw32/bits/os_defines.h:45:0: note: this is the
location of the previous definition
#define NOMINMAX 1
^
C:\gco\GCoptimization.cpp:20:23: warning: 'GCO_CLOCKS_PER_SEC' initialized and declared 'extern'
extern "C" gcoclock_t GCO_CLOCKS_PER_SEC = 0;
^
In file included from C:\gco\GCoptimization.h:108:0,
from C:\gco\GCoptimization.cpp:4:
C:\gco\energy.h: In instantiation of 'int Energy<captype, tcaptype, flowtype>::get_var(Energy<captype, tcaptype, flowtype>::Var) [with captype = double;
tcaptype = double; flowtype = double; Energy<captype, tcaptype, flowtype>::Var = int]':
C:\gco\GCoptimization.cpp:197:20:   required from here
C:\gco\energy.h:328:91: error: 'what_segment' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of
instantiation [-fpermissive]
inline int Energy<captype,tcaptype,flowtype>::get_var(Var x) { return (int) what_segment(x); }
^
C:\gco\energy.h:328:91: note: declarations in dependent base 'Graph<double, double, double>' are not found by unqualified lookup
C:\gco\energy.h:328:91: note: use 'this->what_segment' instead
C:\gco\energy.h: In instantiation of 'void Energy<captype, tcaptype, flowtype>::add_term1(Energy<captype, tcaptype, flowtype>::Var, Energy<captype, tcaptype,
flowtype>::Value, Energy<captype, tcaptype, flowtype>::Value) [with captype = double; tcaptype = double; flowtype = double; Energy<captype, tcaptype,
flowtype>::Var = int; Energy<captype, tcaptype, flowtype>::Value = double]':
C:\gco\GCoptimization.cpp:280:22:   required from here
C:\gco\energy.h:207:22: error: 'add_tweights' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of
instantiation [-fpermissive]
add_tweights(x, B, A);
^
C:\gco\energy.h:207:22: note: declarations in dependent base 'Graph<double, double, double>' are not found by unqualified lookup
C:\gco\energy.h:207:22: note: use 'this->add_tweights' instead
C:\gco\energy.h: In instantiation of 'void Energy<captype, tcaptype, flowtype>::add_term2(Energy<captype, tcaptype, flowtype>::Var, Energy<captype, tcaptype,
flowtype>::Var, Energy<captype, tcaptype, flowtype>::Value, Energy<captype, tcaptype, flowtype>::Value, Energy<captype, tcaptype, flowtype>::Value,
Energy<captype, tcaptype, flowtype>::Value) [with captype = double; tcaptype = double; flowtype = double; Energy<captype, tcaptype, flowtype>::Var = int;
Energy<captype, tcaptype, flowtype>::Value = double]':
C:\gco\GCoptimization.cpp:304:42:   required from here
C:\gco\energy.h:220:22: error: 'add_tweights' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of
instantiation [-fpermissive]
add_tweights(x, D, A);
^
C:\gco\energy.h:220:22: note: declarations in dependent base 'Graph<double, double, double>' are not found by unqualified lookup
C:\gco\energy.h:220:22: note: use 'this->add_tweights' instead
C:\gco\energy.h:235:23: error: 'add_tweights' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of
instantiation [-fpermissive]
add_tweights(x, 0, B); /* first term /
^
C:\gco\energy.h:235:23: note: declarations in dependent base 'Graph<double, double, double>' are not found by unqualified lookup
C:\gco\energy.h:235:23: note: use 'this->add_tweights' instead
C:\gco\energy.h:236:24: error: 'add_tweights' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of
instantiation [-fpermissive]
add_tweights(y, 0, -B); / second term /
^
C:\gco\energy.h:236:24: note: declarations in dependent base 'Graph<double, double, double>' are not found by unqualified lookup
C:\gco\energy.h:236:24: note: use 'this->add_tweights' instead
C:\gco\energy.h:237:24: error: 'add_edge' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of
instantiation [-fpermissive]
add_edge(x, y, 0, B+C); / third term /
^
C:\gco\energy.h:237:24: note: declarations in dependent base 'Graph<double, double, double>' are not found by unqualified lookup
C:\gco\energy.h:237:24: note: use 'this->add_edge' instead
C:\gco\energy.h:245:24: error: 'add_tweights' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of
instantiation [-fpermissive]
add_tweights(x, 0, -C); / first term /
^
C:\gco\energy.h:245:24: note: declarations in dependent base 'Graph<double, double, double>' are not found by unqualified lookup
C:\gco\energy.h:245:24: note: use 'this->add_tweights' instead
C:\gco\energy.h:246:23: error: 'add_tweights' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of
instantiation [-fpermissive]
add_tweights(y, 0, C); / second term /
^
C:\gco\energy.h:246:23: note: declarations in dependent base 'Graph<double, double, double>' are not found by unqualified lookup
C:\gco\energy.h:246:23: note: use 'this->add_tweights' instead
C:\gco\energy.h:247:24: error: 'add_edge' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of
instantiation [-fpermissive]
add_edge(x, y, B+C, 0); / third term /
^
C:\gco\energy.h:247:24: note: declarations in dependent base 'Graph<double, double, double>' are not found by unqualified lookup
C:\gco\energy.h:247:24: note: use 'this->add_edge' instead
C:\gco\energy.h:251:22: error: 'add_edge' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of
instantiation [-fpermissive]
add_edge(x, y, B, C);
^
C:\gco\energy.h:251:22: note: declarations in dependent base 'Graph<double, double, double>' are not found by unqualified lookup
C:\gco\energy.h:251:22: note: use 'this->add_edge' instead
In file included from C:\gco\GCoptimization.h:109:0,
from C:\gco\GCoptimization.cpp:4:
C:\gco\graph.cpp: In instantiation of 'Graph<captype, tcaptype, flowtype>::Graph(int, int, void ()(char*)) [with captype = double; tcaptype = double;
flowtype = double]':
C:\gco\energy.h:187:189:   required from 'Energy<captype, tcaptype, flowtype>::Energy(int, int, void ()(char)) [with captype = double; tcaptype = double;
flowtype = double]'
C:\gco\GCoptimization.cpp:1230:33:   required from here
C:\gco\graph.cpp:21:83: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings]
if (!nodes || !arcs) { if (error_function) (error_function)("Not enough memory!"); exit(1); }
^
In file included from C:\gco\GCoptimization.h:110:0,
from C:\gco\GCoptimization.cpp:4:
C:\gco\maxflow.cpp: In instantiation of 'flowtype Graph<captype, tcaptype, flowtype>::maxflow(bool, Block) [with captype = double; tcaptype = double;
flowtype = double]':
C:\gco\energy.h:325:33:   required from 'Energy<captype, tcaptype, flowtype>::TotalValue Energy<captype, tcaptype, flowtype>::minimize() [with captype =
double; tcaptype = double; flowtype = double; Energy<captype, tcaptype, flowtype>::TotalValue = double]'
C:\gco\GCoptimization.cpp:1237:37:   required from here
C:\gco\maxflow.cpp:484:145: warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings]
if (maxflow_iteration == 0 && reuse_trees) { if (error_function) (error_function)("reuse_trees cannot be used in the first call to maxflow()!"); exit(1); }
^
C:\gco\maxflow.cpp:485:126: warning: deprecated conversion from string constant to 'char' [-Wwrite-strings]
if (changed_list && !reuse_trees) { if (error_function) (error_function)("changed_list cannot be used without reuse_trees!"); exit(1); }
^
In file included from C:\gco\GCoptimization.h:109:0,
from C:\gco\GCoptimization.cpp:4:
C:\gco\graph.cpp: In instantiation of 'void Graph<captype, tcaptype, flowtype>::reallocate_nodes(int) [with captype = double; tcaptype = double; flowtype =
double]':
C:\gco\graph.h:364:54:   required from 'Graph<captype, tcaptype, flowtype>::node_id Graph<captype, tcaptype, flowtype>::add_node(int) [with captype = double;
tcaptype = double; flowtype = double; Graph<captype, tcaptype, flowtype>::node_id = int]'
C:\gco\energy.h:198:30:   required from 'Energy<captype, tcaptype, flowtype>::Var Energy<captype, tcaptype, flowtype>::add_variable(int) [with captype =
double; tcaptype = double; flowtype = double; Energy<captype, tcaptype, flowtype>::Var = int]'
C:\gco\GCoptimization.cpp:1140:31:   required from here
C:\gco\graph.cpp:70:74: warning: deprecated conversion from string constant to 'char' [-Wwrite-strings]
if (!nodes) { if (error_function) (error_function)("Not enough memory!"); exit(1); }
^
In file included from C:\gco\graph.h:43:0,
from C:\gco\energy.h:77,
from C:\gco\GCoptimization.h:108,
from C:\gco\GCoptimization.cpp:4:
C:\gco\block.h: In instantiation of 'Type Block::New(int) [with Type = int]':
C:\gco\maxflow.cpp:110:36:   required from 'void Graph<captype, tcaptype, flowtype>::add_to_changed_list(Graph<captype, tcaptype, flowtype>::node*) [with
captype = double; tcaptype = double; flowtype = double]'
C:\gco\maxflow.cpp:520:27:   required from 'flowtype Graph<captype, tcaptype, flowtype>::maxflow(bool, Block) [with captype = double; tcaptype = double;
flowtype = double]'
C:\gco\energy.h:325:33:   required from 'Energy<captype, tcaptype, flowtype>::TotalValue Energy<captype, tcaptype, flowtype>::minimize() [with captype =
double; tcaptype = double; flowtype = double; Energy<captype, tcaptype, flowtype>::TotalValue = double]'
C:\gco\GCoptimization.cpp:1237:37:   required from here
C:\gco\block.h:124:76: warning: deprecated conversion from string constant to 'char' [-Wwrite-strings]
if (!next) { if (error_function) (error_function)("Not enough memory!"); exit(1); }
^
C:\gco\block.h: In instantiation of 'Type DBlock::New() [with Type = Graph<double, double, double>::nodeptr]':
C:\gco\maxflow.cpp:95:5:   required from 'void Graph<captype, tcaptype, flowtype>::set_orphan_rear(Graph<captype, tcaptype, flowtype>::node*) [with captype =
double; tcaptype = double; flowtype = double]'
C:\gco\maxflow.cpp:183:36:   required from 'void Graph<captype, tcaptype, flowtype>::maxflow_reuse_trees_init() [with captype = double; tcaptype = double;
flowtype = double]'
C:\gco\maxflow.cpp:487:44:   required from 'flowtype Graph<captype, tcaptype, flowtype>::maxflow(bool, Block) [with captype = double; tcaptype = double;
flowtype = double]'
C:\gco\energy.h:325:33:   required from 'Energy<captype, tcaptype, flowtype>::TotalValue Energy<captype, tcaptype, flowtype>::minimize() [with captype =
double; tcaptype = double; flowtype = double; Energy<captype, tcaptype, flowtype>::TotalValue = double]'
C:\gco\GCoptimization.cpp:1237:37:   required from here
C:\gco\block.h:223:76: warning: deprecated conversion from string constant to 'char' [-Wwrite-strings]
if (!first) { if (error_function) (*error_function)("Not enough memory!"); exit(1); }
^
Error in GCO_BuildLib (line 68)
eval(mexcmd);  % compile and link in one step
Error in GCO_UnitTest (line 48)
GCO_BuildLib; disp('BuildLib PASSED');
`

Active development of IRTK has now moved to the MIRTK project.


Getting list id

Running 'mc list lists' -> 'mc lists list' (arguments should be swapped).
The error is:
$HOME.gem/ruby/2.5.0/gems/mc-0.0.8/lib/mc/commands/campaigns.rb:117: warning: key :inline_css is duplicated and overwritten on line 123
Command 'lists' requires a subcommand group,grouping,merge-vars,webhook,abuse-reports,clients,growth,list,locations,member-activity,member-info,members,subscribe,static-segments,segments

A year too late, but thanks!


Formatting fails to include define enclosed in single quotes.

Thank you for providing an appropriate solution the other day.
We have noticed that constants cannot be formatted if they are enclosed in single quotes.
Input values
-module(cat).

-define('meow-1', "Meow").
    -define('meow-2', "Meow Meow").
-define('meow-3', "Meow Meow Meow").

-export([meow/1]).

meow(1) -> ?'meow-1';
meow(2) -> ?'meow-2';
meow(3) -> ?'meow-3'.

The actual formatting does not seem to fail and cause an error, but the formatting does not finish and times out.
Please let me know if there is a workaround.

Thank you for reporting this bug!
Fixed it in #106, and I will release the next version soon.

I was able to use the fixed version successfully :smile:
Thank you for responding so quickly!


HTTPs in HTTP CONNECT tunnel integration test.


GH-281 Improve rendering of math nodes in all actions

Fixes #281

So based on discussions on Discord, it seems the consensus would be to try and design these in a more generalized way, so that users can place a simple Multiply node and modify the types as needed.


execinfo.h does not exist in alpine linux 3.19

execinfo.h does not exist in alpine linux 3.19
Hence, in Types.hpp the #include <execinfo.h> could not be found. Is it possible to keep this optionally?

Sure. This is not required, since eMQTT5 doesn't include backtracing helpers. I've fixed it in #15. Let me know if it's ok for you.

yes, works for me.


check children recipe arguments

See #13

I'm not sure if we can test in a RewriteTest the actual problem of populating the fields with reflection with jackson.


3.0-snapshot - demodb - array item returned instead of string

OrientDB Version: 3.0-snapshot
Java Version: 1.8
OS: win 10 64bit
Hi,
I was working on the demodb integration tests and I found out that for this query:
Among Santo's Friends, find the top 3 Customers that placed the highest number of Orders:
SELECT
  OrderedId as Customer_OrderedId,
  in('HasCustomer').size() as NumberOfOrders,
  out('HasProfile').Name as Friend_Name,
  out('HasProfile').Surname as Friend_Surname
FROM (
  SELECT expand(customer)
  FROM (
    MATCH {Class: Profiles, as: profile, where: (Name='Santo' AND Surname='OrientDB')}-HasFriend-{Class: Profiles, as: friend}<-HasProfile-{class: Customers, as: customer}
    RETURN customer
  )
)
ORDER BY NumberOfOrders DESC
LIMIT 3

Friend_Name and Surname_Name are returned as array items, instead of strings
I wonder if this is expected and why it doesn't return "Luigi" instead of "["Luigi"]"
Thanks,

Hi @santo-it
This is an expected behavior: graph opeartors (out(), in() etc.) always return arrays, this is why you get an array in this case
Thanks
Luigi


Bioshock (2007) black squares on vending machine in DX10

Software information
Bioshock (2007), high settings
System information

GPU: GTK 760
Driver: NVIDIA 440.82
Wine version: Proton-GE-5.6-2
DXVK version: 1.6.1

Log files

d3d11.log: Bioshock_d3d11.log
Proton Log: steam-7670.log

At "Neptune's Bounty" in front of "Fontain Fisheries", that vending machine there will render black squares from a distance caused by the shimmering effect in DX10 mode.
This is apparently a NVIDIA issue, and it also happens on Windows as well. I just thought maybe you could spot something in the logs and see if its not fixable in DXVK. This bug also occurs when using "PROTON_USE_WINED3D=1".
https://www.youtube.com/watch?v=ZxajUUErvy4

Can you please provide an apitrace? I don't have the game so there's not much I can do here.

Can I use the Linux build of apitrace or does it have to be the Windows .dll build?
I’m running Bioshock through Steam, and I’m on Arch Linux.

Windows build, see https://github.com/lutris/docs/blob/master/Apitracing.md.

I tried to make an apitrace, but the game just crashes at launch.

When I find the time. I’ll install a copy of Windows 10 and try it on Windows.

I tried to make an apitrace under Linux, but the game kept crashing. It might have to do with Proton.
When I find the time, I’ll install Windows 10 and try another apitrace.

I tried to get apitrace to work with Proton-GE and vanilla Proton, and it did not work. I’m going to try apitrace with regular Wine now.

@shoober420 Friendly ping. Are you still having this issue with latest dxvk and driver? :slightly_smiling_face:

Just noting that i can reproduce this on Nvidia. Both with dxvk and with the native game on Windows.
I had issues getting a apitrace as the game crashes with it on Linux and when i tried on the Nvidia setup on Windows the game was so slow i had issues reproducing. But will try again later on amd windows.

Managed to make a trace on Windows AMD together with dxvk. Tho i dunno if it's useful since it still ran at like 1fps.
https://mega.nz/file/xkxhQa7R#s3FMiWKM2ZiV5swPE4hlljmBIEp_zI-hCSukclfU9UU

I can't actually reproduce this issue anymore with a RTX 4080 (on Linux with dxvk at least). Above when i said i reproduced i tested with a 960.
So either this seems to be some hardware quirk on older GPUs or a driver change did something.

@Blisto91
Cool to know DX10 mode works great with DXVK. I want to replay ASAP.


Exclusions, reports, and various bug fixes

A rather large PR which provides the implementation for the new (more advanced) exclusions support, as well as JUnit-friendly reports. There are some bug fixes in here as well.

Thanks for the feedback. Sorry for the delay it has been a busy couple of weeks. I expect to provide an update in the next couple of days.

BTW, thanks very much for the extra eyes, Markus. Very appreciated. I would like to point out this PR is a collaboration between myself and @museadmin , who has been invaluable not just in the coding but also in providing a significant amount of testing support.
Also a side note, I am working on a new PR which will hopefully be done this week, which will add OSS Index 3.0 API support. This new API provides access to a newer database of vulnerabilities, which has much more data already and has more vulnerabilities added on a near-daily basis.

Finally found a gap in the schedule and made the changes. I have also almost completed the 3.0 integration. I'll have a PR up for that shortly.


Optimal usage of the db schema name in GraphQL schema

A few days ago I switched to a named schema for my DB tables. So right now I ended up with prefixing all table references in my models with the DB schema name. However, I don't want my GraphQL schema to be prefixed with the DB schema name. Is there any workaround for this case?

Maybe you could use withSchema method instead of prefixing your table names:
  graphql(graphQlSchema, req.query.graph, {
    onQuery(builder) {
      builder.withSchema('yourSchema');
    }
  })

Actually nowadays objection-graphql could use the model name instead of table name to generate the api names since ES6 classes are a requirement, and I don't think anyone writes classes without names.

@nasushkov If you have multiple schemas, maybe you can use this workaround:
function makeSchemaQueryBuilder(schema) {
  return class extends Model.QueryBuilder {
    constructor(..args) {
      super(...args);
      this.withSchema(schema);
    }
  };
}

class Foo extends Model {
  static QueryBuilder = makeQueryBuilder('schema1');
}

class Bar extends Model {
  static QueryBuilder = makeQueryBuilder('schema2');
}

I'll change objection-graphql to use the model name instead of table name to create schema names.

@koskimas Thanks for all your tips. My temp solution was overriding getTableName in the base class (I used two base classes for each schema):
export default class BaseModel extends Model {
    static dbSchemaName = 'myschema'
    static getTableName(){
        const tableName = super.getTableName()
        return `${this.dbSchemaName}.${tableName}`
    }
}

Then I just set the tableName without prefix.
export default class Company extends BaseModel {
    static tableName = 'company'
}

Although that workaround worked for me, it seems that it's tightly coupled with the current internal implementation, so I'd better go with your solution.

@koskimas

I'll change objection-graphql to use the model name instead of table name to create schema names.

Was this change ever made? I'm running into the same issue and have solved it for now using the approach you gave here.


Not a valid bitmap when I try to preload SVG

Description
I have a content page where I am loading an SVG image.  The image loads and displays on screen - however the first time the app is loaded it takes a second or two for the image to appear.  So I tried using this:
ImageService.Instance.LoadEmbeddedResource("SVGImages.temp-circle.svg", typeof(App).GetTypeInfo().Assembly).Preload();
But using this I am getting the error below:
System.BadImageFormatException: Not a valid bitmap
Is there something different I have to do in order to preload the SVG and stop the screen flicker on the first load of the page?
Steps to Reproduce

Expected Behavior

Actual Behavior

Basic Information

Version with issue:
Last known good version:
Platform:

Screenshots

Reproduction Link / Code

It happens the same for me, although I'm referencing the image directly from XAML.

Hey! Got it working, double check the SVG appears in this way in your CSPROJ —try moving it to Android's Resources just the assure in this way works:
<AndroidResource Include="Resources\drawable\icon_nfc.svg" />
, and that you follow the guideline when installing the NuGet packages:
https://github.com/luberda-molinet/FFImageLoading/wiki/SVG-support#xamarinforms
It should work.


Opening a folder using vscode.workspace.updateWorkspaceFolders does not allow to execute rest of the code

OS Version: Windows 10

I am trying to render a UI on vscode after the user selects a workspace. The selected workspace is opened using vscode.workspace.updateWorkspaceFolders in my code.
vscode.workspace.updateWorkspaceFolders(
vscode.workspace.workspaceFolders ? vscode.workspace.workspaceFolders.length : 0,
0,
{ uri: vscode.Uri.file(usrDefaultPath) }
);
Once the above code is executed it shutdown the current extension host process. Even code can't stop at the breakpoint.

https://code.visualstudio.com/api/references/commands provides a detail on the behavior

Is there any workaround so that it doesn't terminate current host.
I also tried using vscode.openFolder but the behavior is same.

This is a known limitation and there is no workaround.


Documentation: docker provider and configuration parameter domain is not required

Do you want to request a feature or report a bug?
Bug
What did you do?
Read the documents at https://docs.traefik.io/configuration/backends/docker/#docker and https://docs.traefik.io/configuration/backends/docker/#docker-swarm-mode
In normal docker mode (link 1) it says that domain is mandatory. In docker swarm modle (link 2) it says it is optional.
I believe the correct answer is that both should be optional.

Closed by #4086.


electron-cash history is not creating proper JSON

Using single quotes (') instead of double quotes ("); presenting addresses as <Address 1Mz7153HMuxXTuR2R1t78mGSdzaAtNbBWX>
Version 3.1.2 in Docker with https://github.com/anth-ny/electroncash-docker

Will check if https://github.com/fyookball/electrum/commit/99ed623d140868d09bb325fcb247f79248cdfa0c or some other recent commit addresses this.

Fixed in git head by https://github.com/fyookball/electrum/commit/99ed623d140868d09bb325fcb247f79248cdfa0c


feat: Make IP Colocation configurable for pubsub parameters

Overview
Closes #1842
Checklist

[x] New and updated code has appropriate documentation
[x] New and updated code has new and/or updated testing
[ ] Required CI checks are passing
[x] Visual proof for any user facing features like CLI or documentation updates
[x] Linked issues closed with keywords

Codecov Report

Merging #1849 (51b9065) into main (233c9aa) will decrease coverage by 0.15%.
The diff coverage is 28.57%.

@@            Coverage Diff             @@
##             main    #1849      +/-   ##
==========================================
- Coverage   57.15%   57.00%   -0.15%
==========================================
  Files         242      242
  Lines       16141    16157      +16
==========================================
- Hits         9226     9211      -15
- Misses       5962     5990      +28
- Partials      953      956       +3

Impacted Files
Coverage Δ

libs/header/p2p/exchange.go
79.61% <0.00%> (-2.39%)
:arrow_down:

nodebuilder/p2p/config.go
81.08% <ø> (ø)

nodebuilder/p2p/pubsub.go
60.39% <25.00%> (-5.54%)
:arrow_down:

libs/header/sync/sync.go
67.48% <100.00%> (ø)

share/eds/byzantine/bad_encoding.go
66.00% <0.00%> (-3.00%)
:arrow_down:

share/eds/byzantine/pb/share.pb.go
32.88% <0.00%> (-1.97%)
:arrow_down:

libs/header/local/exchange.go
61.90% <0.00%> (+14.28%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Please also make the name feat(modp2p) and set the labels

Please also make the name feat(modp2p) and set the labels

Sorry didn't see that comment, thanks! @Wondertan

@derrandz, all our PRs have to have a kind: label, as there is CI rule check for this, which you can see it's broken


CAMEL-20986: implement LangChain4j document splitters as a DSL

FYI,
The checks are failing because the change is spread all over the code base:
There are too many projects to test so only the affected projects are tested
Jul 31, 2024 4:22:12 AM org.jline.utils.Log logr
WARNING: Unable to create a system terminal, creating a dumb terminal (enable debug logging for more information)
[main] WARN org.jline - Unable to create a system terminal, creating a dumb terminal (enable debug logging for more information)
Processing surefire and failsafe reports to create the summary
Error: Process completed with exit code 1.

So the incremental tester seems unable to run them.
However, looking at the logs, they all pass. This part is fine.

LGTM
It would be good to add javadoc to the new code in the core/camel-api as its the public API for end users.
Also it would be good to see a standalone example with camel-spring-boot and camel-jbang - but that surely can be done later.

LGTM
It would be good to add javadoc to the new code in the core/camel-api as its the public API for end users.

Done!

Also it would be good to see a standalone example with camel-spring-boot and camel-jbang - but that surely can be done later.

Tokenization + Camel JBang ... you are giving me some ideas here. I'll put that on my TODO, I think it would be cool to show this in other runtimes / ways.
Thanks!

All review points resolved. Tests passed on my CI. Let's merge and see how it goes. Thanks!


Make HTML decode configurable

I've run into an issue where the module "metalsmith-markdown" will escape the HTML characters within my code samples for me, turning < into <.  However, when "metalsmith-prism" comes along and processes the same code sample, it doesn't decode the HTML entities for prism.  The end result is that < turning into &lt;, which messes up the original code sample.
I'm sure this was probably written this way for a good reason, so that's why I'm suggesting that making it configurable would at least provide a workaround to others working this way.

Example:
Here is some code

```markup
<html>
```

Becomes (after metalsmith-markdown)

Here is some code

<html>

Then (after metalsmith-prism)

Here is some code

&lt;html&gt;

If I remove the check for language === 'markup' check that decides on decoding, it comes out the other end correctly.

i'll take a look by end of week.

:+1: cheers, I've worked around it locally for now, so no rush.

@misterdai was this the workaround?

const markdown = require('metalsmith-markdown')
const renderer = new marked.Renderer()

.use(markdown({
  langPrefix: 'language-',
  renderer: renderer
}))

My workaround was to just remove the ternary check for a language of markup from this line: https://github.com/Availity/metalsmith-prism/blob/b79a4e976ab11c1ee08a2e10f78b011dd6e48cd8/lib/index.js#L64
So it'd read var html = he.decode($this.html()); instead.  As I said, wasn't sure why you put that check in there, guessing you might not have had the source encoded in your usage.  Which is why I'm thinking that if it's configurable, it'll work for everyone ;)

yes you are correct! :smirk: I'll make the necessary adjustments.

@misterdai does #11 look reasonable?


Fix typos in documentation

Summary
Fix some typos that I've come across in the documentation.
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[x] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 54.389%. remained the same
when pulling 7f2087fb41118ae7c07503086cb35ae51e1e27e4 on eleftherias:fix-typos
into 899c6b4949fec2d54ad5d908d244ac885f7163da on stacklok:main.


DSRC-65: Call to action block

Ticket URL: DSRC-65 + DSRC-68
About these changes
Adds a CTA block (DSRC-65) and a button block (DSRC-68)
In the API:

In the CMS:

Before assigning to reviewer, please make sure you have

[x] Checked things thoroughly before handing over to reviewer
[x] Checked PR title starts with ticket number as per project conventions to help us keep track of changes
[x] Ensured that PR includes only commits relevant to the ticket
[x] Waited for all CI jobs to pass before requesting a review
[x] Added/updated tests and documentation where relevant

Merging PR guidance
Follow docs\developer-guide\contributing.md
Deployment guidance
Follow docs\infra\environments.md

Was there a requirement for the ability to have multiple CTA buttons next to one another?
We also need a boolean field for the button which is accented, defaulting to False. Setting to True would allow the editor to add an accented (coloured) button.
We also need an optional title field so editors can include a longer, more descriptive title of where the button goes.

Another thought - are these going into article pages or the yet-to-be-defined "standard page"?

Another thought - are these going into article pages or the yet-to-be-defined "standard page"?

I just had a chat with Lizzy and she said they will be in a "standard" page, so I'll make a PR before this one is merged to add a standard page, add these components to that, and remove them from Article pages.

Was there a requirement for the ability to have multiple CTA buttons next to one another?

Content haven't asked for it... But I think there could be a case for that (at some point). We can always allow this to add multiple buttons at a later point if that's the case 🙂

We also need a boolean field for the button which is accented, defaulting to False. Setting to True would allow the editor to add an accented (coloured) button.

👍

We also need an optional title field so editors can include a longer, more descriptive title of where the button goes.

They have the sub-heading feature at the minute, I think they would use that here instead of having a dedicated CTA "title"?

Was there a requirement for the ability to have multiple CTA buttons next to one another?

Content haven't asked for it... But I think there could be a case for that (at some point). We can always allow this to add multiple buttons at a later point if that's the case 🙂

Could we make it a list with a max of 1? I'm just thinking about the future - it would be more pain to change a dict to a list because the new format would "break" the frontend whereas adding more buttons, it might just not display them.

We also need an optional title field so editors can include a longer, more descriptive title of where the button goes.

They have the sub-heading feature at the minute, I think they would use that here instead of having a dedicated CTA "title"?

I was on about a specific title attribute on the button itself but looking at it more, I don't think this is needed. We'll just need give advice to devolved editors on how to properly write button text. Carry on!


how to support unicode/utf-8? like Chinese?

Sample code like this:
parser = Lark('''start: WORD "," WORD "!"
            %import common.WORD   // imports from terminal library
            %ignore " "           // Disregard spaces in text
         ''', parser='lalr')
print(parser.parse("Hello,世界!"))

I'm already try a long time, anyone can help on this, thanks!

Right now, WORD is defined for English only. Perhaps that needs to change.
Meanwhile, you can use the following definition:
WORD: /[^\W\d]+/

I could extract Unicode CHS letters  by  /u"[\u4e00-\u9fa5]"/.  however, looks this rule does not work
LCASE_LETTER: "a".."z"
UCASE_LETTER: "A".."Z"
SIMCH_LETTER: /u"[\u4e00-\u9fa5]"/
LETTER: UCASE_LETTER | LCASE_LETTER | SIMCH_LETTER
WORD: LETTER+
I think something in load_grammer.py may need to be changed

@ray-linn ok, thanks, I think this will help.

The correct rule is :
LCASE_LETTER: "a".."z"
UCASE_LETTER: "A".."Z"
CN_ZH_LETTER: /[u"\u4e00-\u9fa5"]/
LETTER: UCASE_LETTER | LCASE_LETTER | CN_ZH_LETTER
WORD: LETTER+

I find out how to code the rule for Unicode in grammer.g, here is the example
LCASE_LETTER: "a".."z"
UCASE_LETTER: "A".."Z"
CN_ZH_LETTER: /[u"\u4e00-\u9fa5"]/
LETTER: UCASE_LETTER | LCASE_LETTER | CN_ZH_LETTER
WORD: LETTER+

and it outputs:
Tree(start, [Token(WORD, 'Hello'), Token(WORD, '世界')])

 /[u"\u4e00-\u9fa5"]/  will include the quote marks. You can use /[\u4e00-\u9fa5]/ instead


this app is not supported with latest chrome anymore

any plans to make it work again ?
thanks

Same here getting CRX Invalid package


Show "X candidates found" on the "Detect and select" page

Overview
In order to help the end-user get a quick overview of the scale of the case, we should show a "X candidates found" message on the "Detect and select" step of the identification/analysis.
Expected Behavior
For example, "7 candidates found" as displayed here:

Technical details
If the backend does not provide summary num_candidates metadata, the value can be calculated by counting the number of candidates returned by the API. The test displayed should be pluralised, so "1 candidate found" vs "2 candidates", etc. in a reasonably clean manner.
Acceptance criteria
The "detect and select" page shows the number of candidates found via a "X candidates found" message.
Blocked by
Issues: #9

Closed in #92! Thanks!


[FEATURE] show base url when deploying on job cluster with EZDeployLight

I would like the base_url to show as output from deployment job.
base_url = get_ezdeploy_lite_openai_url(deployment_name)

This allows me to easily get the base_url needed to connect clients or model serving endpoints.
Today I have to run above code on separate notebook to get the base url . Instead I would prefer on every restart of the job task to get the latest base url.

completed as part of v0.15.0


How is hello world redirected to new tab

Is this because you are redirecting to image?

I think that's due to markdown ![] opens a new tab, but this only works for image content


fix(edgeclusters.sh): Workaround BZ 2073197 issue with signatures on containers

Description
Override for BZ 2073197 to override permissions https://bugzilla.redhat.com/show_bug.cgi?id=2073197#c19
Related: https://github.com/openshift/machine-config-operator/issues/1349
Apparently, by mistake,  a change in  RHCOS image does try to verify signatures for the images, which are not currently mirrored or even provided, and this causes an issue.
There's an upstream issue listed to get this solved, but as a workaround we're disabling verification in Edge clusters via an ignition file and might in addition require a change in the installer image being used until RHCOS has the changes reverted and the related tooling is updated to mirror signatures, etc.

/LGTM

Could you please add more info to the PR description? It would be useful to know how that BZ affects us, why it affects us, and what the contents of the override in this PR are.

maybe we should instead change the quay.io/ztpfw/pipeline:latest image.

[root@seal10 ~]# podman run  --name sasha4 quay.io/ztpfw/pipeline:latest cat /etc/containers/policy.json
{
    "default": [
        {
            "type": "insecureAcceptAnything"
        }
    ],
    "transports": {
        "docker": {
	    "registry.access.redhat.com": [
		{
		    "type": "signedBy",
		    "keyType": "GPGKeys",
		    "keyPath": "/etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release"
		}
	    ],
	    "registry.redhat.io": [
		{
		    "type": "signedBy",
		    "keyType": "GPGKeys",
		    "keyPath": "/etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release"
		}
	    ]
	},
        "docker-daemon": {
	    "": [
		{
		    "type": "insecureAcceptAnything"
		}
	    ]
	}
    }
}

Why doing only now when we can do both for the double of price (https://www.imdb.com/title/tt0118884/characters/nm0000457)

Same failure in 'deploy-metallb' as 'main'

https://github.com/rh-ecosystem-edge/ztp-pipeline-relocatable/runs/7018153911?check_suite_focus=true

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


Add Storybook 3.x definitions

From version 3.x storybook moved to a new org/scope and clarified addons.
Note:
Tests are passing locally, but the CI crashes on the package scope.
UNCAUGHT ERROR: Error: @storybook: '@storybook' is a malformed definitions/npm/ directory name! Expected the name to be formatted as <PKGNAME>_v<MAJOR>.<MINOR>.<PATCH>

The failing specs are unrelated to this PR. I'll take some time to fix 'em, and we'll rebase this afterwards.

I think I should improve those definitions, they don't cover the whole API range and plugins.
But should be enough to get started with FLow+Storybook.
Maybe in another PR.

@pascalduez Alright I've fixed the specs, want to rebase and we'll cross our fingers?


[WIP] help: Document new user setting for configuring email visibility.

This PR documents the changes in #22994.
The new page is closely modeled after parts of https://zulip.com/help/read-receipts.
The PR is not complete, as links to /help/restrict-visibility-of-email-addresses need to be changed to point to the new page.
Testing:

Manually tested links'

@drrosa Would you be up for taking over this PR from here? In addition to a review of the content, we need to update links as noted in the PR description, and add a redirect for the page we are removing.
We expect https://github.com/zulip/zulip/pull/22994 to be merged this week, so it would be great if you could put this at the top of your todo list.
We might want to make a tweak following #24310, but I think we can do that once there's a PR for that issue.
@sahil839 @timabbott FYI

@drrosa Would you be up for taking over this PR from here? In addition to a review of the content, we need to update links as noted in the PR description, and add a redirect for the page we are removing.

Yeah, I can do that!

Closing in favor of https://github.com/zulip/zulip/pull/24313, which has been merged.


Implement transpilation of List.sum into Spark code

i.e. like #794 but for List.sum instead of List.maximum.
This involves:

[ ] Write a simple as possible example using List.sum
[ ] Identifying the expression in Spark which does the same thing as a call to List.sum
[ ] Write transpilation rules for this in the Spark backend.
[ ] Write tests to verify this functionality works as expected.
[ ] Update documentation to reflect that List.sum is supported.

It will probably be helpful to refer to the changes that were made in https://github.com/finos/morphir-elm/pull/804


IntegerField doesn't prevent entering period on mobile

Tested on Android Chrome.

The mobile browser does fire keydown, but event.key is not defined.

Also, keyCode can't be used for detection at least on Android, as it seems to return 229 on every key.
Related discussion: https://stackoverflow.com/questions/36753548/keycode-on-android-is-always-229

There doesn't seem to be any way to distinguish keys on Android Chrome, all the keys have:
e.key: undefined
e.keyCode: 229
e.which: 229
e.code:
e.charCode: 0

On Android FireFox, the keydown event has the correct values for key, keyCode and which. BUT the keydown event fires only when pressing the number-keys, not when pressing the period-key... 🤦♀

The beforeinput event seems to be a solution for this issue.
Although it is experimental technology, it's well supported on mobile browsers: https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/beforeinput_event


'brightway examples' submodule and 'bw2io' directory not found during setup

I am trying to setup conda environment to start supporting the brightway documentation as intended by the https://github.com/brightway-lca/brightway-documentation/tree/main.
I run in to some issues, and I am not sure which is the actual issue and why it is happening, or if they're related or two separate issues.
First, when setting up the repository submodules with
git submodule update --init --recursive --remote --force
using git bash, it seems to work fine for all submodules except one:

/brightway-documentation` (main)
$ git submodule update --init --recursive --remote --force
fatal: No url found for submodule path 'source/content/gallery/brightway-examples' in .gitmodules

From here I just continued anyway with the setup guide. Until eventually in anaconda prompt from my activated sphinx environment I get the following error:

(sphinx) C:\Users\myuser\brightway-documentation>sphinx-build source _build/html -b singlehtml -a
Extension error:
AutoAPI Directory C:\Users\philipgj\Git\brightway-documentation\brightway2-io\bw2io not found. Please check your
autoapi_dirs setting.

Thank you for reporting this! I’m currently on holiday, but promise to take a look Wednesday next week.

Should be resolved with https://github.com/brightway-lca/brightway-documentation/commit/75358de1038e7b962d738f20cd82a09827408c16. Please confirm and close the issue if the build completes without errors.

Hi Michael, I tested it out and it works - amazing, thank you! I see you already closed the issue so I guess you expected that :)


chore: refactor

Current dependencies on/for this PR:

main

PR #92   👈

This comment was auto-generated by Graphite.


Remove outdated modeling conflict code + update dependencies

We had some outdated and not used code due to a not finished bachelor thesis.
I removed the code and updated the dependencies in this PR
Checklist

[x] I tested all changes and all related features with different users (student, tutor, instructor, admin) on the test server https://artemistest.ase.in.tum.de.

Motivation and Context
Cleanup
Description
Remove everything related to conflicting_result and model_assessment_conflict
Steps for Testing

Create, participate and assess modeling exercises
Everything should work normally

@tiffca not sure what the problem is, but for me this works. Might be an issue with your browser or Internet Connection?!?
Can you try the following. Open the developer tools, right click on the reload icon and choose Empty Cache and hard reload

I should have done that before, thanks for the hint! That worked (I couldn't figure out how to hard reload, but I opened incognito browser), however now it seems the assessments are not submitting.
Steps (test server 3)

create a model exercise, as instructor
participate as student
assess exercises as instructor
click submit. Expected: override/assess next should show. Actual: submit button still shows, and assessment is not submitted. Student cannot view the grade.

@tiffca @alexmardale thanks for testing. There was indeed an issue. I accidentally removed the flag submit=true when deleting the conflict code. I added it back, so it should work again correctly.
Would be great if you can give it another try (as soon as the yarnpkg build and deployment issues are resolved). Thanks!

@stefanwaldhauser @amahmario thanks for testing
Are the UI issues new? (i.e. introduced in this PR?)
Or do you also experience those in the develop branch (or on the production server or Artemis)?

@alexmardale which browser did you use?
Is this an issue on Chrome? Do you also have it on develop

@alexmardale which browser did you use?
Is this an issue on Chrome? Do you also have it on develop?
Can you check if this happens for other exercise types as well?

For me it's also on Firefox.
I'll check on develop for modeling and other exercise types.

I am using Chrome and dont experience this UI bug.

I'm deploying develop on TS3 now if anyone else wants to check

On develop it looks normal (no UI issue) for Firefox:

And same for Chrome.

On enhancement/cleanup-conflict-update-dependencies I checked for file upload and text exercises as well and the UI issue is present in Firefox, but in Chrome it looks ok.
Will check on develop now for other exercise types.

On develop modeling, file upload and text exercises look ok on both Chrome and Firefox.

I am having the same issue for Chrome, Safari and Firefox. Other than that it worked fine for me.

We will fix the issue in a follow up PR. Help is appreciated here!


SSH issue due to host key is known by the following other names/addresses.

Automation stuck at this stage. We may need to add -o StrictHostKeyChecking=no.
Code: https://github.com/IBM/ocp4-upi-compute-powervs-ibmcloud/blob/a9e3ede039bb66f3b5c6ad09ec7741b111c10f93/modules/4_pvs_support/files/static-route.sh#L113
module.support.null_resource.setup (remote-exec): Restarting NetworkManager at NODE_IP: <IP_ADDRESS>
module.support.null_resource.setup (remote-exec): The authenticity of host '<IP_ADDRESS> (<IP_ADDRESS>)' can't be established.
module.support.null_resource.setup (remote-exec): ED25519 key fingerprint is SHA256:RZOY5hSpICgBRdx5OLTLw6BQSSQEodMNfbHddARnChY.
module.support.null_resource.setup (remote-exec): This host key is known by the following other names/addresses:
module.support.null_resource.setup (remote-exec):     ~/.ssh/known_hosts:4: osa21-master-0
module.support.null_resource.setup (remote-exec): Are you sure you want to continue connecting (yes/no/[fingerprint])?
module.support.null_resource.setup: Still creating... [20s elapsed]

Added -o StrictHostKeyChecking=no
To reset your environment, remove this file /etc/dhcp/classless-static-routes.conf ... and edit the /etc/dhcp/dhcpd.conf to remove the include.


fix: use correct crypto unit names based on network

Description:
Currently, when switching between mainnet and testnet wallets at some point wrong units are displayed in the UI (BTC instead of tBTC etc. for the testnet wallets)

How Has This Been Tested?
Manually. Switch between wallets that use different networks

Types of changes:
Bugfix

Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage increased (+0.009%) to 20.106% when pulling 50bf79dbbcaaa967d3a3a63f22713b8288a05fbc on korhaliv:fix/crypto-units into b5c1964d1a768cef1c65359be0cc5f50d7edd7c3 on LN-Zap:next.


ability to increase bsb error window size

I'm on Mac 10.12.5, using 1.21.0-insider.
Currently when there is a compilation error, I can see it in a few places:

the problems tab, where it appears on a single line
hovering over an item in the problems tab, which shows a small tooltip, but not enough to view the whole error
hovering over a highlighted problem in the editor, which shows a small pop-up, but not enough to view the whole error
the F8 next problem view overlay, which has an unscrollable max height not high enough to view the whole error

Many type errors are too complex for the tiny windows above, so I have taken to compiling outside of the editor to get the full error. Is there a way to adjust the height and width of these error pop-ups? What are other users doing?
Related note: I would have attached screenshots, but most error windows disappear upon any keystroke

You can take a screenshot on macOS while showing the hover if you hold cmd+shift first, then mouse over the hover, then hit the 4 key (then space if you want to focus on the application). It would be helpful for me to see a concrete example.
However, if I understand the issue correctly there isn't a lot I can do about error visibility here. Extensions don't have much control over widgets in VS Code (in contrast to Atom or Emacs). I think the hovering over the error in the editor should show all of the content but you may have to scroll around a bit to see it. There is no way that I know of to adjust the dimensions with a setting or anything like that though.
You could try opening an issue in the vscode repo and giving them some feedback about this. I know that some people have requested the ability to better display multi-line errors and complex errors. Hearing from more users that want this might make it more likely to happen.
Since there's not much that can be done about this here I'm going to close the issue but feel free to continue the discussion.

@freebroccolo thank you for updating with instructions on how to take screenshots on pop ups; I did not know that technique.
For other users that have this issue: I've had some success keeping VS Code on the left half of my screen and my terminal console on the right half of the screen, running bsb manually in the terminal to get the full error text. Perhaps there is a way to do this inside of VS Code using a read-only editor tab with the complete output piped from bsb, but I am just starting out with VS Code, so I cannot say whether that is the case.
 We've found a bug for you!
  /Users/pnore/dev/django-react-chat/django_react_chat_example_project/django_react_chat_example_project/static/js/chat/rechat/src/RechatWindow.re 181:48-67

  179 ┆ | Loaded(result) =>
  180 ┆   let chatGroup = parse(result)##chatGroup;
  181 ┆   let parsedUsers = chatGroup >>= getUsersFromGroupOpt |? [||];
  182 ┆   <ul>
  183 ┆     (

  This has type:
    (option(Js.t(({.. edges : array(option(Js.t({.. abbreviation : option(
                                                                   string),
                                                  id : option(string),
                                                  isCurrentUser : option(
                                                                  string) }))) }
                  as 'a)))) =>
    array(string)
  But somewhere wanted:
    (Js.t({. id : string,
            messages : option(Js.t({. edges : array(option(Js.t({. node :
                                                                  option(
                                                                  Js.t(
                                                                  {. author :
                                                                    Js.t(
                                                                    {. id :
                                                                    string }),
                                                                    id :
                                                                    string,
                                                                    text :
                                                                    string })) }))) })),
            users : option(Js.t({. edges : array(option(Js.t({. node :
                                                               option(
                                                               Js.t({. abbreviation :
                                                                    option(
                                                                    string),
                                                                    id :
                                                                    string,
                                                                    isCurrentUser :
                                                                    option(
                                                                    Js.boolean),
                                                                    name :
                                                                    option(
                                                                    string),
                                                                    photoUrl :
                                                                    option(
                                                                    string) })) }))) })) })) =>
    option('b)

  The incompatible parts:
    option(Js.t('a))
    vs
    Js.t({. id : string,
           messages : option(Js.t({. edges : array(option(Js.t({. node :
                                                                 option(
                                                                 Js.t(
                                                                 {. author :
                                                                   Js.t(
                                                                   {. id :
                                                                    string }),
                                                                   id :
                                                                   string,
                                                                   text :
                                                                   string })) }))) })),
           users : option(Js.t({. edges : array(option(Js.t({. node :
                                                              option(
                                                              Js.t({. abbreviation :
                                                                    option(
                                                                    string),
                                                                    id :
                                                                    string,
                                                                    isCurrentUser :
                                                                    option(
                                                                    Js.boolean),
                                                                    name :
                                                                    option(
                                                                    string),
                                                                    photoUrl :
                                                                    option(
                                                                    string) })) }))) })) })

ninja: build stopped: subcommand failed.

Thanks for the response. I see what you mean now. It looks to me like part of the problem here is that the pretty printer is simply using too much horizontal space when printing errors. I think it might be a good idea to create an issue about this in the reason repository.


Open Release Request uses deprecated actions command set-output

Please review the blog post and update the action

The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

https://github.com/open-telemetry/opentelemetry-ruby-contrib/actions/runs/3231243639

opentelemetry-ruby-contrib on  main via 💎 v3.1.2
zsh ❯ git grep -c set-output
.github/actions/test_gem/action.yml:6
.github/workflows/ci.yml:39

opentelemetry-ruby-contrib on  main via 💎 v3.1.2
zsh ❯ cd ../opentelemetry-ruby

opentelemetry-ruby on  main via 💎 v3.1.2
zsh ❯ git grep -c set-output
.github/actions/test_gem/action.yml:6
.github/workflows/ci.yml:10

opentelemetry-ruby on  main via 💎 v3.1.2

Well, this will be fun...

Oh, actually not too bad., see #145 and open-telemetry/opentelemetry-ruby/pull/1389


SLSA verification failed: error searching rekor entries: no matching entries found

Hi,
I have created a Provence for test repo using below workflow.
name: SLSA go releaser
on:
  workflow_dispatch:
permissions: read-all
jobs:
  build:
    permissions:
      id-token: write # To sign the provenance.
      contents: write # To upload assets to release.
      actions: read # To read the workflow path.
    # needs: args
    uses<EMAIL_ADDRESS>    with:
      go-version: 1.18

However when i verify it using slsa-verifier it give me following error, any hint on this?
slsa-verifier % go run main.go -artifact-path ~/Downloads/binary-linux-amd64 -provenance ~/Downloads/binary-linux-amd64.intoto.jsonl -source <source-repo>
FAILED: SLSA verification failed: error searching rekor entries: no matching entries found
exit status 2

Hi!
Yes there was an issue in the rekor deployment that caused searching rekor entries to fail.
If you use the v1.1.1 builder and verifier at head, you should be able to verify successfully. Let me know!

Note: We are releasing a new version of the verifier later today to avoid this issue

zurrehma may I ask which repo you were trying it on?

@laurentsimon For now i am just teesting it on of my test repos.

Thanks! Should be working now, happy to check. Use https://github.com/slsa-framework/slsa-verifier/releases/tag/v1.1.1 please!

yes, that worked. Thanks!


Support for docx files (word documents)

Dosgpt parser already parses ".docx": DocxParser(),
But it looks like frontend does not know that
I just fixed it here #334


Update mockserver-netty to 5.13.1

Updates org.mock-server:mockserver-netty from 5.11.2 to 5.13.1.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.mock-server", artifactId = "mockserver-netty" } ]

labels: test-library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #1228.


RTT Programming and Virtual Collaboration

This PR adds in:

A primer on Virtual Collaboration
Information on how to think about setting up virtual collaboration
Information on Red Team Testing, a new method for working collaboratively across timezones and virtually

Thanks for the PR, i'll review in the next day or so!

Looks great, I added a couple of changes to make if possible :)


Exception on RunOnUIThread

Describe the bug
OutOfMemoryException Exception on RunOnUIThread, while logged memory usage was low and stable (25 MB).
To Reproduce
Steps to reproduce the behavior:

Run the application for several days and write exceptions to the log 😁

Expected behavior
No exception
Platform:

MAUI on Windows desktop

Stacktrace
[2023-02-17 00:54:18] A crash occurred:System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at System.Runtime.InteropServices.ComWrappers.<TryGetOrCreateComInterfaceForObjectInternal>g____PInvoke|7_0(ObjectHandleOnStack comWrappersImpl, Int64 wrapperId, ObjectHandleOnStack instance, CreateComInterfaceFlags flags, IntPtr* retValue)
   at System.Runtime.InteropServices.ComWrappers.TryGetOrCreateComInterfaceForObjectInternal(ComWrappers impl, Object instance, CreateComInterfaceFlags flags, IntPtr& retValue)
   at System.Runtime.InteropServices.ComWrappers.GetOrCreateComInterfaceForObject(Object instance, CreateComInterfaceFlags flags)
   at WinRT.ComWrappersSupport.CreateCCWForObjectForABI(Object obj, Guid iid)
   at ABI.Microsoft.UI.Dispatching.IDispatcherQueueMethods.TryEnqueue(IObjectReference _obj, DispatcherQueueHandler callback)
   at Mapsui.UI.Maui.MapControl.RunOnUIThread(Action action)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.TimerQueueTimer.Fire(Boolean isThreadPool)
   at System.Threading.TimerQueue.FireNextTimers()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()

Remarks

It is not certain that this is a Mapsui problem.
We can add a catch in RunOnUIThread.
We call SKGLView.InvalidateSurface in RunOnUIThread.
Not clear to me from the stack trace if the problem is with the method that is called (I don't see it in the stack trace) or in the dispatch method itself.

SKXamlCanvas already does invalidation on UI thread through dispatcher so it is not necessary to MapsUI to do it

Closing this issue because it could not be reproduced so far and I don't see a specific way to proceed on this. One improvement that has already been made is that the map exception are not synchronized on the main thread.
A more general solution is to rewrite some of our code to use less invalide calls.


Update README.md

Fix Azure Functions extension url

Thanks for catching this and submitting the fix! Merging now

Thanks for catching this and submitting the fix! Merging now


Component Library

High-level svelte library with components for charts that people can just use.

[ ] 0D total count
[ ] 1D Histogram
[ ] 2D Heatmap
[ ] 2D circle density

These charts will use the reimplementation of Falcon. For now, they can just take in some dummy data arguments.

Just to clarify, this means creating individual charts that people can just use with their data and it will automatically do the falcon stuff and connect them together for interactive brushing. Doing the histograms should be top priority because they would be used more.

Just use dummy data for now for each bin, but we'll need

[ ] categorical histogram (can draw brush)
[ ] continuous histogram (can select bar or bars)

We can save zooming for later on. Then we the core library gets along, they can easily be connected.

In svelte/components/VegaLiteHistogram.svelte I show a histogram implementation for continuous bins, this also needs to be updated to support categorical.


Adds support for Appbase

Branch of #166.
On node initialization, http_client will attempt to request the node_version from condenser_api.get_version.
All tests pass except account_history.

It seems the account history test might be failing partially because of a bug in steemd's ah pruning where the very first item in history is always present. The test is not very strict though, so it might actually pass if there wasn't some quirk in history_reverse which causes op 0 to be saved multiple times:
[0, 3909, 3910, 3911, 3912, 3913, 3914, 3915, 3916, 3917, 3918, 3919, 3920, 3921, 3922, 3923, 3924, 3925, 3926, 3927, 3928, 3929, 3930, 3931, 3932, 3933, 3934, 3935, 3936, 3937, 3938, 3939]
[0, 0, 0, 3909, 3910, 3911, 3912, 3913, 3914, 3915, 3916, 3917, 3918, 3919, 3920, 3921, 3922, 3923, 3924, 3925, 3926, 3927, 3928, 3929, 3930, 3931, 3932, 3933, 3934, 3935, 3936, 3937, 3938, 3939]

next step is to audit the appbase-switch logic, and run tests against:

raw appbase; as well as
jussi appbase-compat layer

use dev environment for both as it has all the steemd fixes for passing tests.
the main problem here is recursive loop because set_node now makes an API call -- which, upon failure, will again call set_node.

Also, we are not saving the appbase flag per endpoint, and we make a call every single time we switch to a new node (and I guess after each RPCError) -- resulting in extra complexity in the request failure flow (which is already too much).
How about this approach:

assume appbase/condenser_api by default
when we encounter an RPCError:

if error message signals the endpoint is pre-appbase,

add the current endpoint to a runtime downgrade list
if already in downgrade, raise exception (apparently, signal unreliable)

retry as usual (and assume appbase/condenser_api unless node is in downgrade)

If we can find a reliable error string from pre-appbase nodes this approach will be much cleaner.

Maintaining BC is not important for very long, as with HF20 everything will be appbase.

@sneak we have to maintain BC for the time being for devs hitting any non-appbase node.

Of course - I'm just saying that we probably shouldn't invest significant engineering into architecting a toggle that's going to be ripped out permanently in a few months.  I think it's as simple as branching on the presence of a STEEM_DONT_USE_APPBASE env var, and defaulting to appbase.

We certainly don't need to branch on a per-server level.  It can be processwide, and it can simply default to appbase.

Alternative implementation at #202


chore: bdd-spring-1587767049 to 0.0.1

chore: Promote bdd-spring-1587767049 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment