Header block

This adds styles and markup for article title blocks and library item title blocks ~and discover landing block items~.
TODO:

[ ] Handle overflow display of long titles (library item specific).

This component was working too hard – I've removed the --c variant ('discover landing block') leaving the two page-description components (currently designed for articles and library items). This makes reasoning about styles easier. Renamed to page-description accordingly.
Variant stylings are now written long-hand (for ease of static analysis) and applied directly to the html that they modify (to be more BEM).
Will re-instate the removed --c variant as a block-description in a new PR.

Maybe I am not understanding properly - but what do the modifiers --wb and --hn mean?

what do the modifiers --wb and --hn mean?

'wellcome bold' and 'helvetica neue' (the font family of the heading)

It feels as though we're sitting in between two methodologies as I can see it.
We could move down the route of composing classes on the HTML element. e.g:
.page-description { /*...*/ }
/*...*/
.ff--hn { font-face: Helvetica Neue; }

Heading

Or we could go about composing this in the SASS:
.page-description {/*...*/}
.page-description--article { @extend .ff--hn }
/*...*/
.ff--hn { font-face: Helvetica Neue; }

Heading

In version 1 we leave styling and classes to do exactly that.
In 2 we add some semantics, offering what's special about this element and then decide to style it.
I personally don't like 2 as it couples semantics and style.
What we seem to have at the moment is a kind-of version of 1, but also coupled with other styles attached to it - and I can't see the reason why?

I agree – I don't think I like --article because it's a bit too prescriptive (we might want to use this title style on something other than an article in the future, even thought that's what it was originally designed for). So the modifier differential was to distinguish between the two based on the obvious difference between them stylistically (rather than --a and --b, as previously discussed).
This assumes that we're going to treat this page-description as a type of component which has a couple of variants. This is the approach that I had understood we were going to take – we split the designs up into bits that we agree make sense to share the same markup and styles with variants and code them up.
I would argue that having a class per font-style goes too far – I'd prefer that a e.g. page-description is responsible for its own styles.

I would argue that having a class per font-style goes too far – I'd prefer that a e.g. page-description is responsible for its own styles.

It might make more sense to have a different modifier then - not one that does more than it says on the tin - do we know what these states are going to be - or are we hypotheticalising about them?

Currently we know that they've been designed to handle the article and library item title blocks – but all of the naming issues we've raised before still stand (i.e. don't want to call them --article and --library because we might want to use them elsewhere; don't want to call them --a and --b because it doesn't describe styles).

So article and library are being handled differently?
I am assuming the reasoning for this is the idea behind metadata vs editorial content.
We could then have a --metadata modifier that turns it into Helvetica?

Although taking it a step further - we could completely decouple it and have:
.content-heading {}
.metadata-heading {}

?

I believe the difference is simply to set them apart, visually. One style for articles, another for library items. We're in danger of overthinking it.

it has the least potential to become out-of-date

My concern is not that - my concern is that it is doing more than that - there is padding etc being set too.

We're in danger of overthinking it

My problem thus far is I am still unclear what is going on - so I'm looking for clarity, not extra information. Let me think of how to explain my unclearness more clearly...

To add some clarity, the reason for the WB and HN difference between library content and everything else is because library content (specifically, items from the collections) contain titles that are 1) too long to be legible in WB and 2) may contain glyphs and diacritics not present in WB. 'Embellished' and 'plain' seem meaningful to me fwiw

@jennpb if that's the case - I would prefer to come up with a css name that conveys that.
heading--short, heading--long @davidpmccormick?

The trouble as I see it is I think e.g. --short/--long or --embellished/--plain run the risk of painting us into a corner really quickly (semantics-wise). Keeping it more abstract (--a/--b) doesn't create any problems as far as I'm aware? And when there's a third style of heading in the future that is a bit embellished, or longer-but-plainer, the more specific naming system breaks really quickly.


Link to AWS Deployment Wiki is Broken

Hello, the link under "AWS Cluster" in the deployment readme (https://github.com/ExpediaDotCom/haystack/blob/master/deployment/README.md) seems to be broken.
Broken link: https://expediadotcom.github.io/haystack/docs/deployment.html
Could anyone point me to where this is meant to be linking?

I found the proper link and updated the readme. Here's the PR: https://github.com/ExpediaDotCom/haystack/pull/752

Thanks @stepansubbotin !


Fixed metadata typo

Line 31 in /lib/connection/events.ts, data -> metadata

Not a problem,  thanks for the awesome library! 👍


Change ci machine type from e1 to f1

@OpsBotPrime merge on friday

Pull request approved for merge by @d-goncalves, rebasing now.

Rebased as c61036674d3a385523b38e5b30105148e91f6cfd, waiting for CI …

CI job :yellow_circle: started.


Add markdown rendering demo

This changes is an attempt to resolve #67
Also this PR add oninput event support to <textarea>.

It looks like the TextAreaElement piece of this was already merged, correct? So it is just the markdown example remaining?

@vitiral I have a working implementation of markdown -> HTML rendering based on a more recent version of Yew. I can't guarantee that it works with Yew 0.4.x at this very moment, but if you want a reasonable place to start, then this file may be of use.
Its based on updated code from the original author that inspired this PR, the source of which can be found here.
I don't have time to work this into an example at the moment, so I encourage you to take the lead on this if you wish.

I could not get pulldown_cmark to compile in wasm or emscripten so I just included the commonmark javascript library and used Node::from_html and VRef::Node. Works like a charm and is good enough for now IMO.
If you could get pulldown_cmark to compile you could still just use Node::from_html for now if you didn't want to do anythign special (which you shouldn't be... it's markdown. What special stuff I do I do by replacing specialized markdown syntax with html).

Sad to hear that you couldn't get pulldown_cmark to work, but glad to hear you found an alternative solution. I'm using a version of pulldown_cmark that points to a specific commit, likely from a while ago. A more recent version of that crate may not play well with WASM/JS targets.
I think there is demand for a yew-markdown crate, but given the current reliance on a non-published version of pulldown_cmark, it doesn't seem wise to invest the time in a separate crate before a known good WASM/JS compatible markdown parser is available. I think having an example for the moment is more than enough, but I will spend a little time investigating pulldown_cmark and other markdown parsing options.
I anticipate having some free time a week from now and will allocate some time towards getting an example built then.

That is strange to hear @vitiral  I have a working version of pulldown_cmark pointing to the latest master branch here: https://github.com/Istar-Eldritch/personal-page/blob/master/src/markdown.rs
It's basically the same implementation you have here with slight moditifcations.

Hey, I just want to let you know that I haven't forgotten about this. In light of the forthcoming significant changes to the framework, I'm going to wait to open a PR for markdown rendering until your changes land.

https://github.com/DenisKolodin/yew/pull/292 should now take precedence over this PR.

Closed in favour #292! Thank goes to @hgzimmerman :tada:


Docs: Change component usage inside inheritance example

Q
A

Bug fix?
yes

New feature?
no

Issues
See below...

License
MIT

I was following the guide for nested UX components and inheritance. Really cool stuff. 👍
Inheritance & Forwarding "Outer Blocks"
I was confused about this code example that re-uses the alert component and "passes through" the content text from the SuccessAlert component usage:
{# templates/components/SuccessAlert.html.twig #}
<twig:Alert type="success">
{% component Alert with {type: 'success'} %}
    {{ block(outerBlocks.content) }}
</twig:Alert>

Is it really supposed to be two nested alert components? Because this throws an error because of the missing {% endcomponent %} tag.
Should it be either this...
{# templates/components/SuccessAlert.html.twig #}
<twig:Alert type="success">
    {{ block(outerBlocks.content) }}
</twig:Alert>

or this syntax?
{# templates/components/SuccessAlert.html.twig #}
{% component Alert with {type: 'success'} %}
    {{ block(outerBlocks.content) }}
{% endcomponent %}

Is it really supposed to be two nested alert components?

With your fix it's more logic :)

Thank you @tobiasberge.


decode: Add support for Request enum variants without params

Duplicated also here: https://github.com/oasisprotocol/oasis-sdk/issues/995
It will be more convenient to have opportunity to use Request enums with no params. Example:
#[derive(Clone, Debug, cbor::Encode, cbor::Decode)]
pub enum Request {
    #[cbor(rename = "instantiate")]
    Instantiate,

    <...>
}

This example doesn't work, because we receive error when we try to instantiate. None of these variants work:
oasis contracts instantiate <code_id> 'instantiate'
oasis contracts instantiate <code_id> '{instantiate}'
oasis contracts instantiate <code_id> '{instantiate: {}}'
We receive error: Execution failed with error: module: contracts code: 12 message: execution failed: unreachable executed

This should already be supported (it uses just a CBOR text string, e.g. "instantiate" in this case unless you pass #[cbor(as_struct)] to the variant in which case it uses a map).
It could rather be an issue with the CLI that does something weird when parsing the arguments. Will close this issue and let's discuss in oasisprotocol/oasis-sdk#995.


Docker logs persist username and password

When the container first authenticates it places the username and password for authentication into the console log which is then captured by Docker. I'm not sure how much of an issue this is as the user needs access to the docker log command to read it, it would however also be residing on the file system which, may be secured or not. I suppose if there's only one user on the machine it's moot but if there was more than one I have concerns. I don't think Docker itself has any access control system - i.e. if you can run docker log you can run it on any container.

Closed. See: https://github.com/harleylang/hydroxide-docker/pull/20#issuecomment-1002132390


Ayo, you guys have forgotten to credit me for the GameJolt thingie

What needs to be documented?
Please guys, it's one of the requirements of use according to the license I assigned to my project :)

Nvm, just kidding lol

lol

Closed because I just noticed lmao @MemeHovy

it's okay lol


Docs link to old(?) github accounts

https://github.com/snapshot-labs/snapshot-docs/blob/master/contribute.md still contains links to repositories under https://github.com/balancer-labs and https://github.com/bonustrack
While these do redirect to the snapshot-labs account, it might be more straightforward to update the links to the new targets.

Created without template due to #3524.
Also, this file hasn't been updated since 2020, and is not accessible on the published docs site. It should probably just be archived or deleted.

Thanks for pointing this out @sparr. Yes @bonustrack we should archive that repo I guess

@samuveth You mean fix the links?

@bonustrack Hm not sure, is this our main docs repo? Why is contribute.md not up-to-date with https://docs.snapshot.org/guides/contribute

Probably should delete that file

Ok good catch yes, seem it's not being used anymore in the docs


MudTabs: Does not shrink / show arrows when placed inside MudAppBar

Bug type
Component
Component name
MudTabs
What happened?
Place a MudTabs inside MudAppBar and shrink the window
Expected behavior
MudTabs sizes decreases and shows arrows for tab changing when there is not enough space for all tabs
Reproduction link
https://try.mudblazor.com/snippet/GEQnFFwZsvPQhXZa
Reproduction steps

Shrink window / pane
AppBar MudTabs does not resize/show arrows
MudContent MudTabs does resize/show arrows

Relevant log output
No response
Version (bug)
6.11.0
Version (working)
No response
What browsers are you seeing the problem on?
Firefox, Chrome, Microsoft Edge
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

Any update or anyone know of a fix to this? I've been looking at this issue and would love to know what to change to get this to work.


Tweaks to improve these extensions

Thanks for this. It fixed a frustration that's been unaddressed for years in Sphinx. Great work!
One minor improvement: to avoid Sphinx errors about files not being included a toctree, you can add code in conf.py like:
if not tags.has("tag_used_in_only_directive"):
    exclude_patterns += [ "file_that_is_omitted_by_the_only_directive" ]

I saw this on SO, but can't remember exactly where. This seems like a nice docs improvement for this extension.
Also, an idea: I wonder if there's a way to to set env_version (see extension metadata) returned from setup based on the builder type, which (I think) would force a cache flush / rebuild if the builder changed? That is, set env_version to 0 for HTML, 1 for LaTeX, etc.

Thanks for the feedback and suggestions. I for a while no longer use sphinx_selective_exclude, so the project is effectively unmaintained. Feel free to fork and implement these ideas. Otherwise, keeping this open for other folks to be able to find it.


Dump PrettyStackTrace on Ctrl-T in a frontend job

It'll dump it for all the frontend jobs spawned from a driver, too, but then the driver will buffer the response, so it's not that useful.
Requires LLVM r365911.

@swift-ci Please smoke test

Cool!

David

On Jul 18, 2019, at 8:10 PM, Jordan Rose<EMAIL_ADDRESS>wrote:
It'll dump it for all the frontend jobs spawned from a driver, too, but then the driver will buffer the response, so it's not that useful.
Requires LLVM r365911.
You can view, comment on, or merge this pull request online at:
https://github.com/apple/swift/pull/26234
Commit Summary
Dump PrettyStackTrace on Ctrl-T in a frontend job
File Changes
M lib/FrontendTool/FrontendTool.cpp (1)
Patch Links:
https://github.com/apple/swift/pull/26234.patch
https://github.com/apple/swift/pull/26234.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Successfully built the compiler in both cases, which is all I was testing for.

but then the driver will buffer the response, so it's not that useful.

Could we arrange for SIGINFO to make the driver start flushing these more aggressively, or to have some other way to make this useful?

Sure, patches welcome. ;-) This was a spare-time project, and I have plenty of other spare-time projects to look at, so this is probably going back on the shelf after this.


HTML?

Hey,
I'm not sure if this has been answered a thousand times before, but I was wondering why HTML isn't picked up in any repo's language reporter, but CSS and JavaScript are.
One could debate if HTML really is a programming language, but I think that's beyond the point here. If I visit a repo that consists of HTML files and one CSS-file, I want that reflected in the colored bar at the top.
Regards,
Daniel

This issue still shows up on a google search of "html linguist", so for those looking you can mark languages not marked as "programming" as detectable -> https://github.com/github/linguist#detectable

@eReGeBe HTML is a markup language for Linguist. markup languages are already "detectable". What might happen however is that some of your files are marked documentation and not counted in statistics. You can change that with:
$ cat .gitattributes
path-to-html-files/* linguist-documentation=false


Update 06a-data-warehouse-load.md

the recommended separator is ',' , use '/n' get error message
Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Hello @sophiexu
Change was made in another commit, closing this one.
Thank you,
Mihai


Timedelta is not supported for Hijri dates

Hi Developer,
I am doing a project where I import and use Hijri calendar. But I have noticed that timedelta is not supported for Hijri dates. Please resolve the issue for next release.
Thank You for the calendar!!!

I appreciate your suggestion.
This feature is indeed on the roadmap, but understanding your specific use case would be extremely helpful.
Could you please share more details about how you plan to use timedelta with HijriDate?

For the time being, you can use the following code to calculate the difference between two Hijri dates in days:
from hijridate import Hijri

h1 = Hijri(1441, 1, 1).to_julian()
h2 = Hijri(1440, 1, 1).to_julian()

print(h1 - h2)
# 354


self signed certificates

Hi, is there an option for host auth to add certificates (root ca, ca, key ) and the possibility to add something like "validate_certs: false" ?

search across all issues got me this https://github.com/lmenezes/cerebro/issues/127
play.ws.ssl.loose.acceptAnyCertificate = true
Havent found a way to import my own CA yet.

https://github.com/lmenezes/cerebro/issues/6 describes how to add a self-signed CA.
Basically:
play.ws.ssl {
  trustManager = {
    stores = [
      { type = "PEM", path = "<cert>" }
    ]
  }
}

@screwyy did you try what @johnseekins suggests on #6?


[WIP] Add AWS iam role

AWS has the ability to assign an IAM role to your EC2 instance [1], and this will allow you to make API calls from the EC2 instance, without needing to provide credentials. This works by pinging the metadata service and pulling down some temp credentials and using those until they expire. Once expired, they will get new ones from the same meta data service.
The Go AWS sdk offers the ability to use this out of the box [2], if you use the correct credentials. The goal of this PR is to use those credentials for creating other EC2 instances, and thus, not having to provide your api key and secret in order to do so.
This is a work in progress, when I compile and run, I get an error, but not sure if the error is related to this change, or something else.
There also needs to have a better way to validate the missing AWS key/secret when not using an IAM role. The current way prevents you from going forward without those items, and thus the validation is removed from this PR for now, but a better way needs to get added before we can merge.
/cc @nathanleclaire
[1] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html
[2] http://docs.aws.amazon.com/sdk-for-go/api/aws/credentials/ec2rolecreds/EC2RoleProvider.html

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "add_aws_iam_role" git@github.com:kencochrane/machine.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "add_aws_iam_role" git@github.com:kencochrane/machine.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

@nathanleclaire are we no longer going to add this feature?


Convert audio to video

I have two questions:

Can I convert Audio files to Video files?
Can I add background to the Video file?

Yes
Yes

You will need two handy classes LiTr offers: MockVideoMediaSource and PassthroughDecoder. First will produce empty video frames, and second will pretend to decode them. To render a bitmap on top you can use BitmapOverlayFilter from litr-filters, or  FrameSequenceAnimationOverlayFilter if you want to change backgrounds. There is TransformationPresenter.createEmptyVideo method in demo app that should get you started.

Closing this issue for now. Feel free to re-open it if this doesn't work.


Top reviews section on the Home page

I want to add a section of reviews on the home page with the 3 or 4 top reviews being displayed..
please assign this issue to me under SWOC (Social Winter of Code)
I will be able to contribute after 1st of Jan if u don't mind

@KajalDeore04 Assigned


fix(byon): Visibility toggle only on Succeeded images

Resolves https://github.com/opendatahub-io/odh-dashboard/issues/181

/cc @dlabaj


Added specialized kernels to openmp.md

A few formatting changes and addition of specialized kernels section at the end.

@Maetveis can you please change the linter rules so that 80 column width and trailing whitespace is flagged as an issue.


Ingest user account data which have access to control.akamai.com

We need to monitor for users who have access to akamai.  We need to ingest the necessary data associated with detecting the following.

Do we allow non-sso enabled users?
Ingest users who have access to akamai (via control.akamai.com, or via api)
Identify if those accounts/api keys have been accessed
Identify if those keys need to be rotated (90 day policy)

#33

Closed by this PR: https://github.com/nodestream-proj/nodestream-plugin-akamai/pull/33


Tracking(approx_count_distinct): append-only approx_count_distinct

in discussion in #3414, we found the current design of detectable approx_count_distinct is too expensive to persist the state

add an append-only approx_count_distinct aggregator with memory state
design the schema of the append-only approx_count_distinct's state table
implement different agg state type other than ValueState and MaterializedInputState
investigate and explore the 2-phase agg of append-only approx_count_distinct

is too expensive to persist the state

I'm not sure I would agree with this. Its expensive in a group by with many groups. But it may be suitable to small groups or simple agg.

investigate and explore the 2-phase agg of append-only approx_count_distinct

Sounds like the approach here is to also maintain a hash table per vnode. One can do local agg in terms of in-memory state sharing the same hash buckets, then forward only differentials to the global agg.

One can do local agg in terms of in-memory state sharing the same hash buckets, then forward only differentials to the global agg.

Yes, but we need more detailed design here.

add an append-only approx_count_distinct aggregator with memory state
#5958
design the schema of the append-only approx_count_distinct's state table
#5976 The state is all the buckets in HLL.
implement different agg state type other than ValueState and MaterializedInputState
#5976 The new state type is named TableState.
Notice, all things above are just singleton for simple agg. So we need Investigate and explore the 2-phase agg of append-only approx_count_distinct
https://github.com/risingwavelabs/rfcs/pull/7
The change row will be too large.


Preflight checks improvements

This pull-request can be split in 2 different parts

first one improves the preflight checks related to libvirt crc network
second part improves the error messages which are shown to the user when preflight failures happen

It fixes #990 and #995.

retest this please.


Added property for disabling fisheye style including mask

Well, how does it differ from using AKPickerViewStyleFlat?

AKPickerViewStyleFlat didn't work for me, there was always mask.

I got it, indeed you should be able to disable the mask, but I think there's no relation between the masking and fisheyeFactor. It can be disabled simply by pickerView.fisheyeFactor = 0.0;. Do you have any reasons?

Well simple pickerView.fisheyeFactor = 0.0 doesn't work for me. No idea y.

Added maskDisabled property, I'm still not sure if it is what you mean however (ffc7a820a958af00bb0cf1abf80354dfd0a5d082 .)
Actually, there was a possibility that changing fisheyeFactor after initialization was not reflected. I also fixed this, so it might solve your problem, perhaps.

Ok then, in that case this pull is useless.

Anyway thank you for your cooperation.


Scrollbar widget renders in the middle when scroll direction is horizontal

Hello! I was implementing a SingleChildScrollView (horizontal direction) with a Row as a child. I tried to use the Scrollbar widget as a parent.
Scrollbar(
        isAlwaysShown: true,
        controller: _scrollController,
        child: SingleChildScrollView(
            scrollDirection: Axis.horizontal,
            controller: _scrollController,
            child: Padding(
              padding: const EdgeInsets.symmetric(horizontal: 8),
              child: Row(
                children: <Widget>[
// my widgets
                  ]
              ),
            )),
      )

Here is how it renders:

I expected I could tell the scrollbar to render on one side of the scroll view, below for example.
$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 1.20.1, on Mac OS X 10.15.4 19E287, locale es-ES)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.4)
[!] Android Studio (not installed)
[✓] VS Code (version 1.47.0)
[✓] Connected device (1 available)

! Doctor found issues in 1 category.

Hi @Rahuvich
I can reproduce similar effect but but it's not in middle

main.dart
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Material App',
      theme: ThemeData.dark(),
      home: Home(),
    );
  }
}

class Home extends StatefulWidget {
  @override
  _HomeState createState() => _HomeState();
}

class _HomeState extends State<Home> {
  ScrollController _scrollController = ScrollController();

  @override
  void dispose() {
    super.dispose();
    _scrollController.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Material App Bar'),
      ),
      body: Scrollbar(
        isAlwaysShown: true,
        controller: _scrollController,
        child: SingleChildScrollView(
            scrollDirection: Axis.horizontal,
            controller: _scrollController,
            child: Padding(
              padding: const EdgeInsets.symmetric(horizontal: 8),
              child: Row(children: <Widget>[
                Image.network('https://i.imgur.com/QCNbOAo.png')
              ]),
            )),
      ),
      floatingActionButton: FloatingActionButton(
        child: Icon(Icons.add),
        onPressed: () {},
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel stable, 1.20.2, on Mac OS X 10.15.6 19G2021, locale en-GB)
    • Flutter version 1.20.2 at /Users/tahatesser/Code/flutter_stable
    • Framework revision bbfbf1770c (22 hours ago), 2020-08-13 08:33:09 -0700
    • Engine revision 9d5b21729f
    • Dart version 2.9.1

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-30, build-tools 30.0.1
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.6, Build version 11E708
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 48.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

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

[✓] Connected device (2 available)
    • SM M305F (mobile)  • 32003c30dc19668f                     • android-arm64 • Android 10 (API 29)
    • iPhone 11 (mobile) • A63D6F51-59F3-4A75-961F-3769709F3A92 • ios           • com.apple.CoreSimulator.SimRuntime.iOS-13-6
      (simulator)

• No issues found!

Can you please provide your flutter doctor -v your flutter run --verbose and a complete reproducible minimal code sample that reproduces the issue like in your screenshot
Thank you
Related https://github.com/flutter/flutter/issues/57920

Hey. i have the same issue. But i only see that issue on the iphone 11 pro. iphone 8 works, and Android works as well.
[✓] Flutter (Channel master, 1.22.0-10.0.pre.65, on Mac OS X 10.15.6 19G2021, locale en-DE)
• Flutter version 1.22.0-10.0.pre.65 at /Users/kayfleischmann/development/flutter
• Framework revision 2032a448ed (5 hours ago), 2020-09-02 23:36:19 -0700
• Engine revision 165abef0a2
• Dart version 2.10.0 (build 2.10.0-77.0.dev)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at /Users/kayfleischmann/Library/Android/sdk
• Platform android-29, build-tools 29.0.2
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.4.1, Build version 11E503a
• CocoaPods version 1.9.1
[✓] Android Studio (version 4.0)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 48.1.2
• Dart plugin version 193.7361
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
[✓] IntelliJ IDEA Ultimate Edition (version 2019.2)
• IntelliJ at /Applications/IntelliJ IDEA.app
• Flutter plugin version 39.0.4
• Dart plugin version 192.6527
[✓] IntelliJ IDEA Community Edition (version 2019.1.3)
• IntelliJ at /Applications/IntelliJ IDEA CE.app
• Flutter plugin version 37.0.3
• Dart plugin version 191.7830
[✓] Connected device (2 available)
• Kay’s iPhone (mobile)  • 00008030-001670E41451802E            • ios • iOS 13.3.1
• iPhone 11 Pro (mobile) • 4A0FC080-8241-44AD-805A-9BCA1559E267 • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-4 (simulator)
• No issues found!

It depends on the size of the child  but the issue is reproducible only on iOS

code sample
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Material App',
      theme: ThemeData.dark(),
      home: Home(),
    );
  }
}

class Home extends StatefulWidget {
  @override
  _HomeState createState() => _HomeState();
}

class _HomeState extends State<Home> {
  ScrollController _scrollController = ScrollController();

  @override
  void dispose() {
    super.dispose();
    _scrollController.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Material App Bar'),
      ),
      body: Scrollbar(
        isAlwaysShown: true,
        controller: _scrollController,
        child: SingleChildScrollView(
            scrollDirection: Axis.horizontal,
            controller: _scrollController,
            child: Padding(
              padding: const EdgeInsets.symmetric(horizontal: 8),
              child: Row(children: <Widget>[
                Image.network('https://i.imgur.com/QCNbOAo.png')
              ]),
            )),
      ),
      floatingActionButton: FloatingActionButton(
        child: Icon(Icons.add),
        onPressed: () {},
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel master, 1.22.0-10.0.pre.82, on Mac OS X 10.15.6 19G2021,
    locale en-GB)
    • Flutter version 1.22.0-10.0.pre.82 at
      /Users/tahatesser/Code/flutter_master
    • Framework revision 9248fda410 (11 hours ago), 2020-09-03 16:08:01 -0700
    • Engine revision 3f05b521b9
    • Dart version 2.10.0 (build 2.10.0-86.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-29, build-tools 29.0.2
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.7)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.7, Build version 11E801a
    • CocoaPods version 1.9.3

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

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 48.1.2
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

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

[✓] Connected device (4 available)
    • iPhone 11 (mobile) • EDB19945-0B9F-4A6E-BAA1-425E68E3B6D6 • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-13-7 (simulator)
    • macOS (desktop)    • macos                                • darwin-x64
      • Mac OS X 10.15.6 19G2021
    • Web Server (web)   • web-server                           • web-javascript
      • Flutter Tools
    • Chrome (web)       • chrome                               • web-javascript
      • Google Chrome 85.0.4183.83

• No issues found!

Thank you for taking the time to file this issue. This appears to be a duplicate of https://github.com/flutter/flutter/issues/57920. Please track that issue for updates. If you believe I've made an error, please reply here with more details that explain the difference and we'll re-open this issue. :)


Cleaned the code

Cleaned the code and removed a few components. All errors are cleared. Need to integrate the services for the same.

Integrated i18n. I have added spanish and english in the home page for selection of languages. Everything seems to be working perfectly fine without any errors.


Maintainance

Hello,
Would you be interested in sharing / handing over the maintenance of this project? There are many published improvements and forks, and it would be nice to merge them into one active pdfminer project.
Cheers,
Chris

:+1:
With a popular project, it's too much for one person to review all incoming PRs. If @euske is willing, are some of the more active contributors/forkers interested? I'd like to see this project move forward, but unfortunately I'm unable to offer to do it myself.

Has euske ever responded to this?
Also,  where are the better forks located?

@euske responded in #23, and seemed happy enough to transfer ownership to someone capable; I'm not sure why the OP decided to close the issue instead of nominating someone for the job.
As for newer forks, check the fork network and look for those that branch from recent versions of the main repository and add non-trivial changes. It looks like @goulu has the strongest fork, with its own community of contributors, even if it's not based off of PDFMiner's latest commit.

Great!
Thanks for your response @goodmami

Returning to this issue a year later...
Can we now say that pdfminer.six is the official repo going forward? In that case, some issues and possibly PRs can be migrated over. Also see here (namely, "Close pull requests on unmaintained projects"): https://github.com/blog/2124-kindly-closing-pull-requests


License Clarification

Looks like some great stuff!
This repo doesn't appear to have a license associated; how about an Open Source one like MIT so it can be freely built upon?

Added the MIT license, thanks for you pointing out.


External terminal launches but fails to execute debuggee on macOS

OS: macOS Sequoia 15.0.1
VSCode version:  April 2024 (version 1.89.1)
CodeLLDB version: v1.11.0
Compiler: AppleClang <IP_ADDRESS>00026
Debuggee:

When I set the terminal to "terminal": "external" in CodeLLDB's launch configuration, the debugger does not complete the initialization correctly after launching an external terminal. The terminal opens and automatically inputs some environment variables, but does not proceed further. The debugger's progress bar shows that it is still loading, and the terminal remains unresponsive without any further actions. This issue only occurs when using an external terminal; using the integrated terminal works fine.
 Project directory structure
.
├── .vscode
│   ├── launch.json
│   └── settings.json
├── CMakeLists.txt
├── CMakePresets.json
├── build
│   ├── MyCMakeProject
├── cmake
└── main.cpp

 Users and Project Settings
// ~/Library/Application Support/Code/User/settings.json
{
}
// .vscode/settings.json
{
"lldb.verboseLogging": true, // verbose log can be viewed in OUTPUT/LLDB panel
}

 C++ Project with Visual Studio Extension CMake Tools
// ./main.cpp
#include
int main() {
std::cout << "Hello world!\n";
for (unsigned int i = 0; i < 5; ++i) {
std::cout << i << std::endl;
}
return 0;
}
// ./CMakeLists.txt
cmake_minimum_required(VERSION 3.0.0)
project(MyCMakeProject VERSION 0.1.0
LANGUAGES C CXX
)
include(CTest)
enable_testing()
add_executable(${PROJECT_NAME}
main.cpp
)
set_property(TARGET ${PROJECT_NAME}
PROPERTY CXX_STANDARD 17
)
// ./CMakePresets.json
{
"version": 3,
"configurePresets": [
{
"name": "macOS",
"description": "Default settings for my cmake project",
"hidden": false,
"generator": "Unix Makefiles",
"binaryDir": "${workspaceFolder}/build",
"cacheVariables": {
"CMAKE_BUILD_TYPE": "Debug",
"CMAKE_EXPORT_COMPILE_COMMANDS": "Yes"
}
}
]
}

// .vscode/lauch.json
{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "lldb",
      "request": "launch",
      "name": "Debug",
      "program": "${workspaceFolder}/build/MyCMakeProject",
      "args": [],
      "cwd": "${workspaceFolder}",
      "terminal": "external",
    }
  ]
}

And here is what I got on Terminal

Verbose log
Initial debug configuration: {
  type: 'lldb',
  request: 'launch',
  name: 'Debug',
  program: '${workspaceFolder}/build/MyCMakeProject',
  args: [],
  cwd: '${workspaceFolder}',
  terminal: 'external',
  __configurationTarget: 6
}
Resolved debug configuration: {
  type: 'lldb',
  request: 'launch',
  name: 'Debug',
  program: '${workspaceFolder}/build/MyCMakeProject',
  args: [],
  cwd: '${workspaceFolder}',
  terminal: 'external',
  __configurationTarget: 6,
  relativePathBase: '/Users/dehan/Desktop/CXX',
  _adapterSettings: {
    displayFormat: 'auto',
    showDisassembly: 'auto',
    dereferencePointers: true,
    suppressMissingSourceFiles: true,
    evaluationTimeout: 5,
    consoleMode: 'commands',
    sourceLanguages: null,
    scriptConfig: {},
    terminalPromptClear: null,
    evaluateForHovers: true,
    commandCompletions: true,
    reproducer: false
  }
}
liblldb: /Users/dehan/.vscode/extensions/vadimcn.vscode-lldb-1.11.0/lldb/lib/liblldb.dylib
environment: {}
settings: { evaluateForHovers: true, commandCompletions: true }
[DEBUG codelldb] Connecting to <IP_ADDRESS>:52074
[DEBUG codelldb] New debug session
[DEBUG codelldb::dap_codec] --> {"command":"initialize","arguments":{"clientID":"vscode","clientName":"Visual Studio Code","adapterID":"lldb","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en","supportsProgressReporting":true,"supportsInvalidatedEvent":true,"supportsMemoryReferences":true,"supportsArgsCanBeInterpretedByShell":true,"supportsMemoryEvent":true,"supportsStartDebuggingRequest":true},"type":"request","seq":1}
[DEBUG codelldb::dap_codec] <-- {"seq":1,"type":"response","request_seq":1,"success":true,"command":"initialize","body":{"exceptionBreakpointFilters":[{"default":true,"filter":"cpp_throw","label":"C++: on throw","supportsCondition":true},{"default":false,"filter":"cpp_catch","label":"C++: on catch","supportsCondition":true}],"supportTerminateDebuggee":true,"supportsCancelRequest":true,"supportsCompletionsRequest":true,"supportsConditionalBreakpoints":true,"supportsConfigurationDoneRequest":true,"supportsDataBreakpoints":true,"supportsDelayedStackTraceLoading":true,"supportsDisassembleRequest":true,"supportsEvaluateForHovers":true,"supportsExceptionFilterOptions":true,"supportsExceptionInfoRequest":true,"supportsFunctionBreakpoints":true,"supportsGotoTargetsRequest":true,"supportsHitConditionalBreakpoints":true,"supportsInstructionBreakpoints":true,"supportsLogPoints":true,"supportsReadMemoryRequest":true,"supportsSetVariable":true,"supportsSteppingGranularity":true,"supportsWriteMemoryRequest":true}}
[DEBUG codelldb::dap_codec] --> {"command":"launch","arguments":{"type":"lldb","request":"launch","name":"Debug","program":"/Users/dehan/Desktop/CXX/build/MyCMakeProject","args":[],"cwd":"/Users/dehan/Desktop/CXX","terminal":"external","__configurationTarget":6,"relativePathBase":"/Users/dehan/Desktop/CXX","_adapterSettings":{"displayFormat":"auto","showDisassembly":"auto","dereferencePointers":true,"suppressMissingSourceFiles":true,"evaluationTimeout":5,"consoleMode":"commands","sourceLanguages":null,"scriptConfig":{},"terminalPromptClear":null,"evaluateForHovers":true,"commandCompletions":true,"reproducer":false},"__sessionId":"4a189733-7aeb-4e58-9f92-e1003c8ddad9"},"type":"request","seq":2}
[DEBUG codelldb::dap_codec] <-- {"seq":2,"type":"event","event":"output","body":{"category":"console","output":"Console is in 'commands' mode, prefix expressions with '?'.\n"}}
[DEBUG codelldb::dap_codec] <-- {"seq":3,"type":"event","event":"initialized"}
[DEBUG codelldb::dap_codec] <-- {"seq":4,"type":"request","command":"runInTerminal","arguments":{"args":["/Users/dehan/.vscode/extensions/vadimcn.vscode-lldb-1.11.0/adapter/codelldb","terminal-agent","--connect=52078"],"cwd":"","kind":"external","title":"Debug"}}
[DEBUG codelldb::dap_codec] --> {"command":"setBreakpoints","arguments":{"source":{"name":"main.cpp","path":"/Users/dehan/Desktop/CXX/main.cpp"},"lines":[7],"breakpoints":[{"line":7}],"sourceModified":false},"type":"request","seq":3}
[DEBUG codelldb::dap_codec] --> {"command":"setFunctionBreakpoints","arguments":{"breakpoints":[]},"type":"request","seq":4}
[DEBUG codelldb::dap_codec] --> {"command":"setInstructionBreakpoints","arguments":{"breakpoints":[]},"type":"request","seq":5}
[DEBUG codelldb::dap_codec] --> {"command":"setExceptionBreakpoints","arguments":{"filters":[],"filterOptions":[{"filterId":"cpp_throw"}]},"type":"request","seq":6}
[DEBUG codelldb::dap_codec] --> {"command":"setDataBreakpoints","arguments":{"breakpoints":[]},"type":"request","seq":7}
[DEBUG codelldb::debug_session] Debug event: 0x7fbe39f42558 Event: broadcaster = 0x7fbe400b4220 (lldb.target), type = 0x00000001 (breakpoint-changed), data = {bkpt: 1 type: breakpoint added}
[DEBUG codelldb::dap_codec] <-- {"seq":5,"type":"response","request_seq":3,"success":true,"command":"setBreakpoints","body":{"breakpoints":[{"id":1,"line":7,"message":"Resolved locations: 0","verified":true}]}}
[DEBUG codelldb::dap_codec] <-- {"seq":6,"type":"response","request_seq":4,"success":true,"command":"setFunctionBreakpoints","body":{"breakpoints":[]}}
[DEBUG codelldb::dap_codec] <-- {"seq":7,"type":"response","request_seq":5,"success":true,"command":"setInstructionBreakpoints","body":{"breakpoints":[]}}
[DEBUG codelldb::dap_codec] <-- {"seq":8,"type":"response","request_seq":6,"success":true,"command":"setExceptionBreakpoints"}
[DEBUG codelldb::dap_codec] <-- {"seq":9,"type":"response","request_seq":7,"success":true,"command":"setDataBreakpoints","body":{"breakpoints":[]}}
[DEBUG codelldb::debug_session] Debug event: 0x7fbe39f56a88 Event: broadcaster = 0x7fbe400b4220 (lldb.target), type = 0x00000001 (breakpoint-changed), data = {bkpt: 2 type: breakpoint added}
[DEBUG codelldb::dap_codec] --> {"command":"configurationDone","type":"request","seq":8}
[DEBUG codelldb::dap_codec] --> {"type":"response","seq":9,"command":"runInTerminal","request_seq":4,"success":true,"body":{}}

After further exploration, I discovered that the initial problem was unrelated to the project itself. Setting the external terminal to /bin/bash worked without issue. However, when using /bin/zsh, functionality was impacted until I disabled the source $ZSH/oh-my-zsh.sh line in my .zshrc file. This change restored normal operation, indicating that the issue was likely due to configurations introduced by Oh My Zsh rather than any aspect of the project.
Thank you for your attention to this matter, and I apologize for any confusion my original report may have caused.


IndexError while making recursive function

IndexError was thrown while typing the following:
➜  ~  ptpython --vi
In [1]: def bez(cps, t):
    2.     if len(cps) < 2:
    3.         return cps[0]
    4.     p1 = bez(cps[0:
                        ^--- Exception happened here

Full output:
➜  ~  ptpython --vi
In [1]: def bez(cps, t):
     2.     if len(cps) < 2:
     3.         return cps[0]
     4.     p1 = bez(Traceback (most recent call last):
  File "/usr/local/bin/ptpython", line 80, in <module>
    _run_repl()       all
  File "/usr/local/bin/ptpython", line 77, in _run_repl
    startup_paths=startup_paths, always_multiline=always_multiline)
  File "/usr/local/lib/python2.7/dist-packages/prompt_toolkit/contrib/repl.py",d
    cli.start_repl(startup_paths=startup_paths)
  File "/usr/local/lib/python2.7/dist-packages/prompt_toolkit/contrib/repl.py",l
    on_exit=AbortAction.RAISE_EXCEPTION)
  File "/usr/local/lib/python2.7/dist-packages/prompt_toolkit/__init__.py", lint
    self._redraw()
  File "/usr/local/lib/python2.7/dist-packages/prompt_toolkit/__init__.py", linw
    self.renderer.render(self)
  File "/usr/local/lib/python2.7/dist-packages/prompt_toolkit/renderer.py", linr
    output = self.render_to_str(cli)
  File "/usr/local/lib/python2.7/dist-packages/prompt_toolkit/renderer.py", linr
    self.layout.write_to_screen(cli, screen, height)
  File "/usr/local/lib/python2.7/dist-packages/prompt_toolkit/layout/__init__.pn
    t.write(cli, screen)z(cps, t)
  File "/usr/local/lib/python2.7/dist-packages/prompt_toolkit/layout/toolbars.pe
    tokens = self.get_tokens(cli, width)
  File "/usr/local/lib/python2.7/dist-packages/prompt_toolkit/contrib/python_ins
    append((Signature, sig.full_name))
  File "/usr/local/lib/python2.7/dist-packages/jedi/api/classes.py", line 295, e
    path = [unicode(p) for p in self._path()]
  File "/usr/local/lib/python2.7/dist-packages/jedi/api/classes.py", line 170, h
    path.insert(0, par.name)
  File "/usr/local/lib/python2.7/dist-packages/jedi/api/interpreter.py", line 3_
    return getattr(self.parser_module, name)
  File "/usr/local/lib/python2.7/dist-packages/jedi/parser/fast.py", line 38, i_
    return getattr(self.parsers[0].module, name)
IndexError: list index out of range

Hi all, closing this ticket because ptpython was removed from prompt-toolkit and got its own repository: https://github.com/jonathanslenders/ptpython/ . Further, the Jedi library for ptpython has been upgraded and we handle all known exceptions already. Let's create a new ticket if it happens again.


181 fix table view when using fileClass alias or tag mapping

Interpolate fileClassAlias variable in the buildDvJSQuery() string builder instead of using fileClass

Build in an array the list of tags mapped to the current file class.

Then, check on each page we filter that it contains at least one tag that starts with one of the tags in the built array.

For the second point, I'm sure it's not ideal but it's the only way I've found to retrieve the tags associated with the current file class.

Thanks a lot!
And congrats for having found your way into the (quite complex) logic of FieldIndex 😅


demo: support other architecture that linux-amd64

Description
Make demo compatible with multiple platforms (eg darwin, linux-arm, windows...) the compatibility is limited by the binary compatibility of kind and `helm``
on mac os

install packages that contain gnu tool (eg grep, getopts...) because some options do not exist on BSD version

on windows (Mingw)

make extraction of helm compatible with windows

Fixes #352
How Has This Been Tested?

[X] Running demo on linux
[X] Running demo on macos
[X] Running demo in windows through Mingw  (git bash)

Pull Request Test Coverage Report for Build 383714389

0 of 0   changed or added relevant lines in 0 files are covered.
8 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.06%) to 47.966%

Files with Coverage Reduction
New Missed Lines
%

internal/liqonet/tunnelEndpointCreator-operator.go
8
65.09%

Totals

Change from base Build 383326690:
-0.06%

Covered Lines:
6875

Relevant Lines:
14333

💛  - Coveralls

/rebase

Just a minor comment, could you convert the install.sh indentation of your modifications to tabs for consistency with the rest of the script?

@giorio94  should be good

/rebase

/rebase


Fix/use get rate updates

This fixes a few issues with useGetRateUpdates.
Unfortunately for some reason it's in a inifinty loop, and the percentage change looks a bit off.
Didn't have time to resolve that today.. If someone wants to try to figure it out that would be great..

Infinity problem fixed.  Feel free to have a look at the recent commits if curious. TLDR in a few places we gave invalidated useMemo when we wanted it to be memoized. We have to be a bit careful with passing wei as a hook dependency


Failed to pull docker image.

您好，执行bash docker/scripts/dev_start.sh 这个命令时候出现### 【error】Failed to pull docker image.
应该怎么弄？

@guofengpeng could you give us more details - Apollo version, System specs, OS etc?

apollo 3.5 ,ubuntu 16.04
as follow:
guofengpeng@guofengpeng-Lenovo-G50-80:~/apollo$ bash docker/scripts/dev_start.sh[sudo] guofengpeng 的密码：
fetch: Fetching reference refs/heads/master
[INFO] Start pulling docker image apolloauto/apollo:dev-x86_64-20190128_1800 ...
Error response from daemon: manifest for apolloauto/apollo:dev-x86_64-20190128_1800 not found
[ERROR] Failed to pull docker image.
guofengpeng@guofengpeng-Lenovo-G50-80:~/apollo$

You can try update the codes (pull from master ) and try pull docker images from china use parameter -C  like bash docker/scripts/dev_start.sh -C

thank you much


SYNTH-3329 Remove info about credentials from webdriver logs

The selenium server logs all commands sent to the wendrivers. These
include the get commands which have the url being fetched and the
send keys command which might contain credentials. This creates a
possible security issue.
This patch will add logic which redacts whatever is being sent as
part of the send_keys command as well as remove any basic auth
credentials which might appear in the url when executing a get command.
Testing notes -

tested manually by running a URL and a scripted job and then
manually making sure that the webdriver-server.log does not contain
any information in the get log and the send key logs are REDACTED

@shashwatsrivastava94 Can you give some examples of the logs? They will help us understand your regex better.

Here are some examples of logs from before my change -
Executing: [get<EMAIL_ADDRESS>Done: [get<EMAIL_ADDRESS>Executing: [send keys: 0 [[ChromeDriver: chrome on WIN8 (c8e0a54ec8a91c07f34e8d75840c38f4)] -> id: lst-ib], [1, 2, ., 3, 4]])
Done: [send keys: 0 [[ChromeDriver: chrome on WIN8 (c8e0a54ec8a91c07f34e8d75840c38f4)] -> id: lst-ib], [1, 2, ., 3, 4]]

Same logs after my change -
Executing: [get: https://www.google.com])
Done: [get: https://www.google.com]
Executing: [send keys: REDACTED]
Done: [send keys: REDACTED]

Ran @sanity on Chrome and all passed


Model Marker Symbol is now Model Scene Symbol.

Assign to @nandinirao
Rename ModelMarkerSymbol to ModelSceneSymbol
Merging to v.next branch.

:+1:


Add guidebook for Station AI and Silicons in general

About the PR

Closes #31549

I've never written guidebook stuff before, let me know if anything needs improvement! 😊
Why / Balance
Gives helpful information on Station AI and silicons in general to new players
Media

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

Changelog

:cl:

add: Station AI now has a guidebook entry

I was looking for this because I think a couple things are worth mentioning, edit-wise:

Some rewording would be beneficial:
a. The AI can interact with MOST electronics, including computers. (The examples included are solid though)
b. It would be best if the AI-internal interfaces were listed out so people knew what each button meant ahead of time, if possible.

Also worth mentioning that because the AI has control over electronic equipment, it can (and should) help the station in a variety of ways beyond calling out suspicious or illegal behavior. I know you mention "acting as dispatcher", but giving specific examples (sealing off dangerous atmospheric areas, locating anomalies, ordering things for cargo if they're occupied, etc.) gives players new to AI the idea of versatility. At the moment, a big complaint about AI is how many players skew towards acting as security's "watchtower" because all they're thinking about doing is... Looking at things. Giving them encouragement to be proactive and supporting all the departments not only gives them flexibility, it also makes for interesting gameplay because it creates openings for antagonists to do illegal things/work on their objectives.

This seems more abstract, I realize, but the guidance does make a big difference. In SS13, AI typically requires a lot more playtime, and part of that comes with having versatility in your playing experience across all departments. Just something to keep in mind!

Yeah, thank you for the advice! I'm not sure what the standard policy is with guidebooks, but I really opted for just dipping the player's feet in. I figure, if AI requires more hours to play, then the guide for new players should reveal enough information that their ability to learn the rest isn't too hindered, but not so much that all the joy of discovery is spoiled for them.
Like, if I listed every single lawset or something including the one about squirrels, then that wouldn't be a funny moment of discovery for them later when it inevitably happens in a round they're in.
Or, if I described in detail the AI-A wire on electronics and that it can be cut, then it wouldn't be an interesting experience for the aspiring young hacker.
And, as part of that, I gave very basic examples to try to avoid telling the player specifically "This is what you SHOULD (tm) do", because it can vary based on server and RP level and laws, and plus it's just fun to explore the sandbox of the game and to develop (within reason) gimmicks of your own, especially when playing a silicon.
I considered doing the internal-AI things, but I thought that was more subject to rapid change so I hesitated and figured it could be added once AI is more stable
But yeah I mean if this doesn't get merged soon it's gonna be so out-of-date so fast anyway, probably should've waited longer to hop in on this. The "Station AI Announcement" thing in chat probably warranted some joke about "delivering PSAs" but that was added after the fact, and who knows what other awesome stuff is coming down the pipe next!

I think I might work on my own AI guidebook for this issue. If/when I make the PR I welcome your feedback.

I think I might work on my own AI guidebook for this issue. If/when I make the PR I welcome your feedback.

Yes! I would definitely say wait a little bit though, it was just stressing me out how outdated this PR was getting, I'd hoped for a faster merge and for it to be a temporary start while we waited on more features but pretty soon I realized I just jumped the gun on documenting something still being worked on loll
Take anything you want from my stuff! Or nothing at all!


[BUG] [3.5.0] Sample file download

Sample file download with openToken for a openResource shows unexpected behaviour

closed with #93


this is too gud

It let networking become super easy, thx!
(sorry for making a issue, i can't find where to post comment)

It let networking become super easy, thx!
(sorry for making a issue, i can't find where to post comment)

Thanks!


Allow the ACLs endpoint to accept 'clients' and 'users'

With this change ACLs endpoint will accept 'clients' and 'users'
in the request body when 'actors' is present and is an empty list.
This change provides provides improvements to error handling - in any
case where an invalid actor or group is specified, the name(s) of any
invalid entities are included in the response.

Can we get updates to the API docs as well?

Does this fix the mismatch between what you post and what the response looks like? I know that has long been an issue in our group related APIs.

@tylercloke it doesn't affect that

Note oc-chef-pedant chef-zero failures are expected, the PUTs with the new fields aren't yet supported.  That'll be wrapped up shortly.

Updates from review comments and walkthrough applied.
@tylercloke  raml docs have been updated - though I found that because of a [raml-org/raml-js-parser#115](known issue) the changes won't  render to index.html.

@tylercloke  @tduffield  could I get a :+1: if the edits are in good shape?

Other than minor comments above 👍

👍


cap flake8

Cap version of flake8
see option 1 https://github.com/openmicroscopy/omero-test-infra/issues/26
cc @joshmoore @sbesson

PR tested using https://travis-ci.org/jburel/omero-plugins/builds/455462210
The parade issue is not related to the flake8.
Merging and tagging


Fix broker acceptance test for newer cf-cli versions

Broker Acceptance test break for cf-cli version greater than 6.32

LGTM

LGTM


Use of mutable default values in HadoopJobRunner (and others)

Many of the arguments to the constructor of HadoopJobRunner use mutable default values: https://github.com/spotify/luigi/blob/master/luigi/hadoop.py#L312. This means, for example, if you kick off a job that depends on a bunch of other jobs, they'll all get the same jobconfs object, then if one of them updates its jobconfs property, they'll all be updated.
See: http://pylint-messages.wikidot.com/messages:w0102
I would suggest using something like:
    def __init__(self, streaming_jar, modules=None, streaming_args=None, libjars=None, libjars_in_hdfs=None, jobconfs=None, input_format=None, output_format=None):
        self.streaming_jar = streaming_jar
        self.modules = modules or []
        self.streaming_args = streaming_args or []
        self.libjars = libjars or []
        self.libjars_in_hdfs = libjars_in_hdfs or []
        self.jobconfs = jobconfs or {}
        self.input_format = input_format
        self.output_format = output_format
        self.tmp_dir = False

I would have submitted a diff, but since this same issue likely exists in other spots across the code base, I thought you might want to review whether, and where this should happen globally rather than just patching it in one spot.

I'm closing this issue.

[x] It has been inactive for +4 months.
[ ] It's not about luigi core, so not as many users are affected about this.
[ ] The change seems quite big, it's unlikely to be sporadically picked up.
[ ] The owner haven't responded or disappeared.
[ ] I don't understand what this issue is about.
[ ] There exists a reasonable workaround for this.
[ ] We need to check if this hasn't been fixed by now (for old issues).
[ ] This is kind of by design and not a bug.
[ ] Resolving this would probably add a lot of complexity.

Every open issue adds some clutter, and we try to make the issues fewer and make it easier for new collaborators to find. Currently we try to close any issue that meets the first checkbox + one other.
Feel free to reopen this issue at any point if you have the intent to continue to work this. :)


Add client-side autoloot

Add client-side autoloot

No longer required

Now required once more due to issues with server autoloot that are induced by lack of clientside autoloot


Data shortening issue when working with only one Waves file

The data shortening doesn't work when only one Waves file is loaded.
Need to add case for when i == 0 and i == len(filesWithInfo)-1

This will be fixed in branch feat/readBinaryPDS


Set not planned as the state_reason when automatically closing issues

The underlying octokit API (the latest version) has added a state_reason for specifying GitHub's new closing state.  (It's not entirely clear to me if the correct value would be not planned or not-planned).
The new GitHub Issues - May 19th update | GitHub Changelog
Opening this issue to track updating VS Code's actions to specify the state_reason when automatically closing issues.
We cloned the VS Code actions as the basis for actions in the vscode-cpptools repo.  Since using the latest octokit seems to require updating other dependencies, I figured I'd wait for you guys to address this first, then ingest your changes.  :)

The comamnds.json now accepts a "reason" entry which is either "complete" or "not_planned". It will default to complete just because that was the default behavior before


.p.eval errors on expressions containing assignments or function definitions

q)p)x=2

will work as expected, but run
q).p.eval "x=2"

and you'll get the error
  File "<string>", line 1
    x=2
     ^
SyntaxError: invalid syntax
'p.c:68 runs pyerr
  [0]  .p.eval "x=2"
       ^

The same error is thrown when running an expression that defines a function
q).p.eval "def square(x): return x * x"
  File "<string>", line 1
    def square(x): return x * x
      ^
SyntaxError: invalid syntax
'p.c:68 runs pyerr
  [0]  .p.eval "def square(x): return x * x"
       ^

Python differentiates between expressions and statements.  Variable assignments, function and class definitions are statements and .p.eval, which is similar to Python builtin eval does not work on these.  As far as I can tell, embedPy does not expose Python's exec to q yet.
Meanwhile, I see two work-arounds:
.p.set[`x] .p.eval"42"

or
q).p.eval"exec('x=42')"

To do this I think you'll need to use .p.e. not .p.eval`
.p.eval and p.e (used when prefixing code with p)) run the PyRun_String C API function internally, the difference is that .p.e run's it with Py_file_input allowing multiple expressions with side effects but not returning any value and .p.eval uses Py_eval_input which returns a value but is not allowed to have side effects.
.p.e is analogous to python's exec
.p.eval/pyeval are analogous to python eval
>>> eval('x=2')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<string>", line 1
    x=2
     ^
SyntaxError: invalid syntax
>>> y=exec('z=10')
>>> print(y,z)
None 10

There's a longer explanation at the link below here https://stackoverflow.com/questions/2220699/whats-the-difference-between-eval-exec-and-compile-in-python

Great explanation, thank you. It would be helpful if the difference between .p.e and .p.eval was mentioned in the readme.

Thanks, we'll add a note to the README for this


Nit: remove redundant structure tag

Motivation
Remove the redundant account struct tag in account_config.rs
Have you read the Contributing Guidelines on pull requests?
Yes, and have sent the CLA.
Test Plan
cargo test
Related PRs
N/A

@huitseeker Sure. I've sent out the signed individual CLA to<EMAIL_ADDRESS>before submitting this PR. It looks like still under reviewing. My email is h4x3rotab(at)gmail.com. I would appreciate it if the legal team can prioritize it :)

@h4x3rotab Your CLA is processed. Thanks for your contribution.


build: implement visual regression testing with @web/test-runner

This PR sets up the basic configuration for visual regression testing with @web/test-runner.
web-test-runner.config.js contains a new test group, which is only activated when explicitly called with yarn test:visual-regression. This test group introduces a new file pattern *.snapshot.spec.ts, which contains the visual regression tests.
Additionally, there is a new GitHub Actions workflow, which runs the visual regression tests and saves failed screenshots in an artifact. This artifact is then downloaded in the secure workflow, which add an in_progress check, if any failed screenshots exist.
TODO: Describe container usage.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.24%. Comparing base (e6397df) to head (c851fd2).
Report is 42 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2624      +/-   ##
==========================================
+ Coverage   93.18%   93.24%   +0.05%
==========================================
  Files         316      315       -1
  Lines       25389    25317      -72
  Branches     2063     2072       +9
==========================================
- Hits        23660    23606      -54
+ Misses       1696     1678      -18
  Partials       33       33

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Some elements are still obscure but I have a general idea of the implementation. I'm not sure how the remote baseline is used and why we need to use a container to run the diff locally (but I'm sure there is a reason)
Some discussion topics:

I'm a bit scared of the exponential nature of the number of cases (P1 * P2 * ... * Viewport * browsers * 3 (default, focus & hover))

Pro: covers almost every use case
Con: grows very quickly and requires an "implementation" for each component

Alternatively, we could reuse the stories template?

Pro: we would avoid most of the .snapshot.spec code
Con: not exhaustive like combining each case

Thanks for the review and feedback!
We have reduced the amount of snapshots by being a bit more selective.
Additionally I updated the PR comment to better describe the container use cases.
I think it makes sense to reuse story templates where it is reasonable, but I assume it will depend on the case.


WIP - Helm: Add option to enable k8s events handover.

Currently, there is no way to configure the operator to handle the CNP
status updates using Helm.
This PR adds the missing field in the Cilium's ConfigMap needed when
using the Helm side to allow CNP status updates: enable-k8s-event-handover
Fixes: #14547
Signed-off-by: Youssef Azrak<EMAIL_ADDRESS>Helm: Add k8s event handover field to the Cilium ConfigMap.

@reviewers not sure about the release note.

@reviewers not sure about the release note.

test-me-please

test-me-please


headless service update does not re-update listeners

After scaling a headless service, push logs look like:
2020-08-18T22:18:07.052723Z     info    ads     Push debounce stable[4] 1: 100.034787ms since last change, 100.034345ms since last push, full=true
2020-08-18T22:18:07.054045Z     info    ads     XDS: Pushing:2020-08-18T15:18:07-07:00/3 Services:7 ConnectedEndpoints:1

No LDS update here. config_dump shows no LDS update as well. Restart istiod results in proper LDS

This is broken in 1.6 and master

Have you tested it on 1.7?

I think I only tried master

OK, let me test it

Reprocuded on 1.7 and i guess the cause is https://github.com/istio/istio/blob/cea39bd56c982699bff071b77a9f54ba7f42b66f/pilot/pkg/serviceregistry/kube/controller/endpointcontroller.go#L72
Here we should pass svc's hostname

fixed by #26636


More explicit branch control when pushing

Add branch as an option on swoop deploy

This should look on which branch it came from so it will go onto the kestrel side


[Feature request] Specify the range of letters used for jumping (eg [asdfghj])

First of all, it is a great extension, thank you!
I would appreciate the possibility to limit/specify the range of letters used for jumping, as for example in the vimium extension for Chrome or Mozilla.
At the moment, the used range is [a-z]{2}.
What about [asdfghjkl]{1,3}, (eg one letter jumps to words/lines closest to the cursor)?
I just find that alphabetical order of jumps is not the most keyboard friendly.
Letters from middle keyboard row are easier to reach, imho.
Thanks!

Hi, are there any additional features you'd like to see along with ability to specify you'r own jump alphabet?
I've implemented what you've written here but I don't have an idea on how to make it user friendly in terms of settings.
I really like the idea of being combined line and word jump you mentioned.

Hi! Thanks for coming back on this topic!
No, for the moment I do not have any other ideas... but I am looking forward to try out specifying my own range of letters (if that is what you have just implemented, as I understood).
btw I use your extension along MetaGo, which also allows selecting text with a jump. I like both!
Thanks!

@PavelDvorak You can use Jump instead.

@PavelDvorak You can use Jump instead, it supports this feature.


8maheshw patch 4

trying to merge from one branch to another which is not default

defect#1
defect#2
defect#3
defect # 4

defect # 0


[RND-301] Harden the error detection in OpenSearch backend

Add a function to process opensearch errors.
Update Query and Update opensearch functions to use the new module.

Description
OpenSearch error handling classes are added to display messages returned by the client.

Connection error

023-02-07 09:33:18.236 debug 74467404-a8d8-40b5-a1c5-8051e28545c8 opensearch.repository.UpdateOpensearch.upsertToOpensearch OpenSearch Error processing the object 'tK-wwhRb-qoqblsPdjfNop2mddL30bCKEoOlkA': (ConnectionError) - connect ECONNREFUSED <IP_ADDRESS>:9200
2023-02-07 09:33:18.237 debug 74467404-a8d8-40b5-a1c5-8051e28545c8 core.handler.Upsert.upsert 200

Change in the data type of the index.

2023-02-07 09:41:27.641 debug 4eadffbb-d34e-4583-b0c1-cbd9e4d9ec1d opensearch.repository.UpdateOpensearch.upsertToOpensearch OpenSearch Error processing the object 'c4ak9D7jEwS-MCAYjzMFB-OQqFZi-w9DjSKm4A': (ResponseError) - Reason: failed to parse field [contentClassDescriptor] of type [integer] in document with id 'c4ak9D7jEwS-MCAYjzMFB-OQqFZi-w9DjSKm4A'.

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] I have signed all of the commits on this PR.
[x] I have agreed to the Ed-Fi Individual Contributors' License
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

OpenSearch Request Timeout
I started all containers, started Meadowlark. Connected to OpenSearch for a query successfully (local.33b.http, line 95). Then in Docker, I paused the OpenSearch container and tried again. After about a minute, I received a request timeout exception. It was logged properly. But this was too long to wait.
It looks like request time out is a parameter we can set in OpenSearch's Db.ts as part of the ClientOptions. Let's add a config string OPENSEARCH_REQUEST_TIMEOUT with default 10 seconds.
Query Response
Now that I've watched the behavior as if I were an end-user, it makes sense to have a server error response when querying OpenSearch and we're unable to connect, rather than returning an empty array. The best code in this case is 502 "Bad Gateway", though 500 would also be acceptable.

Now that I've watched the behavior as if I were an end-user, it makes sense to have a server error response when querying OpenSearch and we're unable to connect, rather than returning an empty array. The best code in this case is 502 "Bad Gateway", though 500 would also be acceptable.

502 makes the most sense to me.


Delete Capfile & deploy.rb after deployment

The deploy.rb usually contains private informations like passwords to the server and scm, scm addresses and server adresses. If you deploy other projects than Rails, these files may be published into the DOC_ROOT. There is no reason to keep the Capfile and config/deploy.rb on the live server, so it'll be the best solution to remove these files after the deployment.
Here a basic version (I don't know all the details of Capistrano):
namespace :deploy do
  task :remove_deployment_files do
    run "rm #{latest_release}/Capfile #{latest_release}/config/deploy.rb"
  end
end

after 'deploy:update_code', 'deploy:remove_deployment_files'

The deploy.rb and Capfile are part of your source repository, deleting them from the server leaves your <scm> status unclean.
The thin veil of security as an excuse for deleting them doesn't actually solve any security issues (if someone is reading code on your app server, they're already too far penetrated into your codebase. If you're speaking about security within your own team, it's not an open source Gem's responsibility to facilitate that.
I recommend not putting any passwords into the Capfile, if you're using Subversion, I know that can be tricky; but using a decent, modern SCM which has SSH as a transport, you can use SSH (with agent forwarding, or deploy keys) to make sure you don't need any deploy-time passwords to get at the code.
And regarding database passwords, or otherwise which can be in those files, they should be deployed to the server by a trusted member of staff, and symlinked from the deployment each time through.
Thanks for opening the issue, but it's not really a security improvement.


Non-Standard Behavior in Rewind Button (intentional?)

Describe the bug
When invoking the "rewind"/previous track command (either through the Spot UI or dedicated keyboard buttons), Spot will skip directly to the previous song in the playlist. AFAIK this is non-standard behavior for a music player; typically the rewind command skips to the start of the current song unless it's only a few seconds in, in which case then it goes to the previous song.
General information:

Distribution: Fedora 36
Installation method [e. g. built from source, installed from Flathub...]: Flathub
Version [e.g. 0.1.0]: 0.3.3
Device used [e. g. desktop, phone...]: Desktop

I'd also like to note that I'm willing to try my hand at changing this myself, as a way to get more familiar with Rust. I just wanted to open an issue first to ensure this wasn't an intentional design choice.

sorry for the late answer but yeah, you're right, this behaviour should be fixed!

Awesome, I'll fork it and give it a whirl. Any pointers as to where I should look first?

Sure! I see two possibilities right now
Solution 1:  in playback_state.rs you'll see the logic of how playback related actions are handled. If using the UI or controlling Spot via MPRIS (eg with your keyboard) a PlaybackAction::Previous will be issued.
Right now this updates the state to point to the previous song if there is one. Instead it could be changed to check whether something has been playing for "long enough", in which case the action should do the same thing as PlaybackAction::Seek(0).
This requires modifying the PlaybackState so that it knows the current track position (it does not at the moment), which could be implemented with a similar strategy as PositionMicros in the dbus part of the app (it's a struct that keeps track of the moment we hit play or pause to estimate how far along the track is).
Solution 2 : let various parts of the app handle this. The PlaybackWidget knows the current position, and would be able to issue a PlaybackAction::Seek(0) instead of PlaybackAction::Previous when appropriate. Same with the previous method in mpris.rs, it could choose to send the right action based on the position (estimated with PositionMicros).
It's probably better to go with the first solution, it should be easy to start by having something similar to PositionMicros in the PlaybackState and updating it for the relevant actions (see how MprisState updates the position estimation for instance).
Hope this helps!


Confusing the assembly is too slow.

I have the same issue with Catester. Please check this link https://github.com/yck1509/ConfuserEx/issues/600. I have been fix the issue in local code. Maybe it could merge to the current version.

I added the changes. You can get the modified version here. Let me know if this improves it for you.

I has tried this. It performs at least 10 times faster on my computer.
I have not yet verify whether the results are correct.

I put the output files on to my servers, they have been running for about a week.
And another desktop application are released to the public.
Both of those projects have used complicated design patterns in the source code.
Things are still OK. No one complains anything wrong.
I think #374 is safe to be merged.


Generate in seperate thread to boot gui immidiately

Description

Run the galaxy generation in a seperate thread.

Alternate Designs
N/A
Benefits
Allows the GUI to start immidiately instead of waiting for the generation to run.
Possible Drawbacks
N/A
Applicable Issues
N/A

Codecov Report

Merging #54 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #54   +/-   ##
=======================================
  Coverage   94.94%   94.94%
=======================================
  Files           3        3
  Lines          99       99
=======================================
  Hits           94       94
  Misses          5        5

Impacted Files
Coverage Δ

src/main.rs
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Minor issue with normativity in Section 7.2

The note beginning "A profile may place a upper limit on the maximum required index EEW ... in which case an illegal instruction exception can be raised if the EEW is not supported." seems to be confused about the role of requirements and profiles. The normative text should allow the load/store instruction to raise an exception for unsupported index EEWs, with profiles specifying what particular index EEWs (e.g. up to XLEN only) must be supported.

I too find that note confusing (upper limit on the maximum required?) or in need of copyediting ("a upper"). It probably should be reviewed in tandem with a related note below:

Note | In base V extension, only index widths up to XLEN must be supported.

I think this is one of several outstanding issues concerning the definition of the "base" V extension and its relationship with "profiles".


Unity Crash when switching pages

Hello,
I have encountered an issue using your pdfloader plugin :
With a multi pages pdf, with scripting backend .Net 4.X
start the sample scene and press the right arrow key to switch pages
Repeat several times, if quick enough, this will crash Unity

the bug has to do with async callback and the time to when Unity Update() function gets called to update the texture. If you do this too fast, the pointer becomes invalid because the plugin has replaced its texture with the new one.
To fix you will have to implement a cache of pages and their Texture2D/SRV's for that page and on the callback notifies the plugin to update its texture on the next Update, you would call the plugin at that time to get the valid pointer.
If you implement this change, be sure to submit a pull request so we can get that back into the repo


feat: allow for custom urls or html files on PhotinoBlazorApp.Run()

Description
Solves issue https://github.com/tryphotino/photino.Blazor/issues/62.
Adds an optional URL parameter to PhotinoBlazorApp.Run() which allows for different HTML files to be used. The previous behavior was hardcoded to use the application's provided index.html file, which has been retained as the default value for the new url parameter.
This change is useful for multi-window applications that want to target different HTML files for different layouts or purposes on a per-window basis, but I'm sure there are other use-cases that this enables as well.

Instead of incorporating this change, we instead now honor setting the StartUrl via the Load() extension method. Thanks for point this out.


Adding more retries for authentication issues.

This should fix #1015.

Merging this despite Travis slowness.


Fix lint config inconsistencies

It seems although we’re using the same .eslintrc, perhaps because we’re extending a base we have some inconsistencies. Let‘s find a way tot make sure everyone’s using the same listing rules.

Should be solved for pull requests with TravisCI, but let’s also carve out some time at our next retro to make sure everyone has what they need to fix linting errors locally


com.optimizely.ab.android.datafile_handler.DatafileService - ANR

Hi,
We found an issue in our production app. There are multiple occurrences of ANR being reported.
SDK version: 2.1.0
Below is the stack trace of the crash,
`
executing service com.myapp.prod/com.optimizely.ab.android.datafile_handler.DatafileService
com.optimizely.ab.android.datafile_handler.DatafileService
group="main" sCount=1 dsCount=0 obj=0x761a2298 self=0xb47a4500
sysTid=19837 nice=0 cgrp=apps sched=0/0 handle=0xb6f4eb4c
state=S schedstat=(<PHONE_NUMBER><PHONE_NUMBER> 7208 ) utm=151 stm=139 core=3 HZ=100
stack=0xbe0d6000-0xbe0d8000 stackSize=8MB
held mutexes=at java.lang.Object.wait! (Native method)waiting on <0x070ae6c0> (a java.lang.Object)at java.lang.Thread.parkFor$ (Thread.java:1220)locked <0x070ae6c0> (a java.lang.Object)at sun.misc.Unsafe.park (Unsafe.java:299)at java.util.concurrent.locks.LockSupport.park (LockSupport.java:158)at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt (AbstractQueuedSynchronizer.java:810)at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly (AbstractQueuedSynchronizer.java:970)at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly (AbstractQueuedSynchronizer.java:1278)at java.util.concurrent.CountDownLatch.await (CountDownLatch.java:203)at android.app.SharedPreferencesImpl$EditorImpl$1.run (SharedPreferencesImpl.java:366)at android.app.QueuedWork.waitToFinish (QueuedWork.java:88)at android.app.ActivityThread.handleServiceArgs (ActivityThread.java:4068)at android.app.ActivityThread.access$2400 (ActivityThread.java:221)at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1897)at android.os.Handler.dispatchMessage (Handler.java:102)at android.os.Looper.loop (Looper.java:158)at android.app.ActivityThread.main (ActivityThread.java:7225)at java.lang.reflect.Method.invoke! (Native method)at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1230)at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1120)"FinalizerWatchdogDaemon" tid=6 Sleeping "FinalizerWatchdogDaemon" daemon prio=5 tid=6 Sleeping
group="system" sCount=1 dsCount=0 obj=0x32c0d220 self=0xad918800
sysTid=19848 nice=0 cgrp=apps sched=0/0 handle=0xb341d930
state=S schedstat=( 1293228 15132450 9 ) utm=0 stm=0 core=0 HZ=100
stack=0xb331b000-0xb331d000 stackSize=1038KB
held mutexes=at java.lang.Thread.sleep! (Native method)sleeping on <0x0eee4d9f> (a java.lang.Object)at java.lang.Thread.sleep (Thread.java:1031)locked <0x0eee4d9f> (a java.lang.Object)at java.lang.Thread.sleep (Thread.java:985)at java.lang.Daemons$FinalizerWatchdogDaemon.sleepFor (Daemons.java:273)at java.lang.Daemons$FinalizerWatchdogDaemon.waitForFinalization (Daemons.java:284)at java.lang.Daemons$FinalizerWatchdogDaemon.run (Daemons.java:232)at java.lang.Thread.run (Thread.java:818)
`
Can someone shed some light on this ANR log?

@akhilmohan , thank you for reporting this.  A ANR is not a crash.  The app is not responding.  In this case, if there is a problem with your data connection and datafile polling is enabled, it could be that the data file service was waiting to long for the cdn response.  Right now, our timeout is 5 seconds.   Can you tell us anything else about the issue such as what other threads might be doing at the time or the state of your app at the time? Thank you again.
I would recommend updating to the latest version of the SDK.  Thanks.

We also have bunch of ANR's reported. Looks all are android 6.0 version.
SDK version: 2.1.2
Play console shows me this warning:
The "main" (tid=1) thread is in suspended state. This is likely due to garbage collection.

@pragyagrawal can you update to the latest SDK?  We are on 3.1 now and releasing 3.2 soon.

@thomaszurkan-optimizely I'm having issues with a similar looking ANR log. I've run it across Android 8, 9, and 10 with the same result. The app stalls out on an ANR when the app boots up while the phone is in Airplane mode.
To reproduce:

Put phone into Airplane mode
Run app that has Optimizely Android SDK 3.2.1

2019-09-13 14:44:51.142 19476-19503/? E/ActivityManager: ANR in com.weedmaps.app.android.internal
    PID: 20062
    Reason: executing service com.weedmaps.app.android.internal/com.optimizely.ab.android.datafile_handler.DatafileService
    Load: 1.24 / 0.93 / 0.72
    CPU usage from 110256ms to 0ms ago (2019-09-13 14:42:57.855 to 2019-09-13 14:44:48.111):
      11% 1814/surfaceflinger: 0.5% user + 11% kernel / faults: 115 minor 1 major
      5.6% 19476/system_server: 1.1% user + 4.4% kernel / faults: 18591 minor 63 major
      5.3% 19604/com.android.systemui: 1.2% user + 4.1% kernel / faults: 4420 minor 47 major
      1.6% 20000/com.google.android.gms.persistent: 0.6% user + 0.9% kernel / faults: 5039 minor 101 major
      1.6% 19896/com.google.android.apps.nexuslauncher: 0.4% user + 1.1% kernel / faults: 8057 minor 53 major
      1.6%<EMAIL_ADDRESS>0% user + 1.5% kernel / faults: 13 minor 2 major
      1.3% 20350/com.google.android.googlequicksearchbox:search: 0.3% user + 0.9% kernel / faults: 4408 minor 323 major
      1%<EMAIL_ADDRESS>0% user + 1% kernel
      0.8% 3259/adbd: 0% user + 0.7% kernel / faults: 102 minor 1 major
      0.6% 19323/com.google.android.gm: 0.2% user + 0.4% kernel / faults: 3975 minor 7 major
      0.6% 19409/audioserver: 0% user + 0.6% kernel / faults: 3 minor 1 major
      0.6%<EMAIL_ADDRESS>0% user + 0.6% kernel
      0.5% 20167/com.google.android.gms: 0.1% user + 0.3% kernel / faults: 2870 minor 56 major
      0.3% 1678/logd: 0% user + 0.3% kernel / faults: 1 minor
      0.2% 19711/com.android.phone: 0.2% user + 0% kernel / faults: 474 minor 16 major
      0.1% 559/kswapd0: 0% user + 0.1% kernel
      0.1% 17722/kworker/u8:2: 0% user + 0.1% kernel
      0.1% 1855/statsd: 0% user + 0% kernel / faults: 21 minor
      0.1% 1812/lmkd: 0% user + 0.1% kernel
      0.1% 1821/logcat: 0% user + 0.1% kernel
      0.1% 19753/kworker/u8:5: 0% user + 0.1% kernel
      0.1%<EMAIL_ADDRESS>0% user + 0.1% kernel / faults: 17 minor
      0.1% 19169/kworker/u8:0: 0% user + 0.1% kernel
      0% 19412/netd: 0% user + 0% kernel / faults: 691 minor
      0% 1701/jbd2/vdc-8: 0% user + 0% kernel
      0% 8/rcu_preempt: 0% user + 0% kernel
      0% 2006/dhcpclient: 0% user + 0% kernel
      0% 19314/kworker/u8:4: 0% user + 0% kernel
      0%<EMAIL_ADDRESS>0% user + 0% kernel
      0% 1808/ashmemd: 0% user + 0% kernel
      0% 12548/android.process.acore: 0% user + 0% kernel / faults: 377 minor
      0% 15947/com.android.providers.calendar: 0% user + 0% kernel / faults: 794 minor 1 major
      0%<EMAIL_ADDRESS>0% user + 0% kernel
      0% 15939/com.google.android.calendar: 0% user + 0% kernel / faults: 115 minor 39 major
      0% 18572/logcat: 0% user + 0% kernel
      0% 7/ksoftirqd/0: 0% user + 0% kernel
      0% 866/kworker/0:1H: 0% user + 0% kernel
      0% 1679/servicemanager: 0% user + 0% kernel
      0% 22529/com.android.chrome: 0% user + 0% kernel / faults: 24 minor 4 major
      0% 16413/kworker/0:0: 0% user + 0% kernel
      0% 18159/kworker/u8:1: 0% user + 0% kernel
      0% 19407/zygote64: 0% user + 0% kernel / faults: 192 minor 1 major
      0% 19676/com.google.android.networkstack: 0% user + 0% kernel / faults: 213 minor 5 major
      0% 13647/com.android.carrierdefaultapp: 0% user + 0% kernel / faults: 13 minor
      0% 19544/kworker/0:2: 0% user + 0% kernel
      0% 1/init: 0% user + 0% kernel / faults: 15 minor 1 major
      0% 9/rcu_sched: 0% user + 0% kernel
      0% 19397/kworker/u9:0: 0% user + 0% kernel
      0% 19866/com.google.android.inputmethod.latin: 0% user + 0% kernel / faults: 38 minor 9 major
      0% 20189/com.google.process.gservices: 0% user + 0% kernel / faults: 39 minor
      0% 15/watchdog/1: 0% user + 0% kernel
      0% 21/watchdog/2: 0% user + 0% kernel
      0% 1320/kworker/2:1H: 0% user + 0% kernel
      0% 1324/kworker/1:1H: 0% user + 0% kernel
      0% 1680/hwservicemanager: 0% user + 0% kernel / faults: 17 minor
      0% 1683/kworker/3:1H: 0% user + 0% kernel
      0%<EMAIL_ADDRESS>0% user + 0% kernel
      0%<EMAIL_ADDRESS>0% user + 0% kernel / faults: 3 minor
      0% 1825/traced: 0% u

@thomaszurkan-optimizely we are experiencing these ANRs with SDK 3.2.1 in our app. I noticed that the linked fix #295 for this will only modify the JobService scheduling on Oreo and later devices, not those using AlarmManager (see ServiceScheduler.schedule())
We have only started seeing these ANRs since we enabled datafile polling recently. It appears that on devices < Oreo our app process will be restarted every datafile polling period, even if the app has been terminated by the OS. There are some rare cases where our app will ANR during the initialisation of the app, and it seems that the frequency of these ANRs has increased because the datafile service is being triggered by AlarmManager, which is starting the app in the background.

@fingertricks we believe these should be completely cleared up with the latest release 3.5.2.


rail_segmentation: 0.1.15-1 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository rail_segmentation to 0.1.15-1:

upstream repository: https://github.com/GT-RAIL/rail_segmentation.git
release repository: https://github.com/gt-rail-release/rail_segmentation.git
distro file: melodic/distribution.yaml
bloom version: 0.8.0
previous version for package: 0.1.14-1

rail_segmentation
* Minor update to fix an incorrect declaration of a static const variable under certain compilers
* Contributors: David Kent

Holding for sync


chore: create release v1.31.1 [DO NOT MERGE]

c05fef9bbb68be96f9b9fe289de485e344916307 fix: zero out empty boardroom results

I assume that there isn't a test for this code?


Package

Hello,
Maybe you can package it to make it usable with npm

use npm install vue2-slot-calendar


Is it possible to retrieve the DataResponse object in .responseJSON().then?

Right now the responseJSON promise extension only returns response.result.value. Would it not make more sense to still somehow include the entire DataResponse object?
I'm trying to access response.response.statusCode, and it currently seems there's no way to handle that using the PromiseKit Alamofire extension

Yes, agreed. I'll take a look at this.

Thanks. For now I've updated my extension locally to fulfill(response) rather than fulfill(value). Happy to make that or a better fix in a PR if you've got any ideas

It doesn't make sense to provide the raw Response type as then consumers in PromiseKit will have to unwrap the result into a .success even though we already have guaranteed that it succeeded. So if we are to provide more we should bundle a custom type, or provide the other items in a tuple.
The other option is like what we do for CLLocationManager etc.

what about fulfill((value, response))

What about fulfill((value, response))?

Maybe this is best. Though I dislike the fact the response contains the result, it is perhaps better to just pass the whole thing than to be confusing and create a parallel object that has it removed. Undecided. Sorry this is not resolved yet. I haven't had any good ideas.

Sorry, I wasn't explicit enough, I meant the HTTPURLResponse one, not the DataResponse.
Like this:
    /// Adds a handler to be called once the request has finished.
    public func responseJSON(options: JSONSerialization.ReadingOptions = .allowFragments) -> Promise<(Any, HTTPURLResponse?)> {
        return Promise { fulfill, reject in
            responseJSON(queue: nil, options: options, completionHandler: { response in
                switch response.result {
                case .success(let value):
                    fulfill(value, response.response)
                case .failure(let error):
                    reject(error)
                }
            })
        }
    }

And maybe it doesn't have to be optional when the result was a success, I'm not sure

I added a PMKDataResponse that has everything that Alamofire.DataReponse<Any> has except result and value.


Are floats in scientific notations being handled?

Example:
a = 1e-8

It looks very similar to the #94, so I hope it's an easy fix too 😄  Thanks!

Oh, I checked this with the latest commit from the master and it works fine. Sorry, closing this.