High battery draining even in flight mode (iOS 13.6)

Power consumption of CoronaWarnApp has drastically increased - I guess with install of iOS 13.6. Main topic has been that even in flight mode, my battery got drained from 50% down to 0% - phone shut down completely. I always have my phone in flight mode over night, that usually takes almost no battery.
Battery consumption:

Health Exposure Logging 37% (has been around 15-20% in the past I believe)
Mail (next in statistic) 16%

I did review #671 - my issue surfaced with iOS13.6 - #671 is about general consumption with iOS13.5.1
https://github.com/corona-warn-app/cwa-app-ios/issues/671
Steps to reproduce the issue
Turn on flight mode and watch some thing suck your battery dry - but also happens during normal operation.
Technical details

iOS Version: 13.6
Device: iPhone 7
Managed corporate device
C Warn app 1.1.1 (3)

Duplicate of #671

I did review #671 - my issue surfaced with iOS13.6 - #671 is about general consumption with iOS13.5.1
So I expect this  is a different / new issue - thus opened this ticket.

I did review #671 - my issue surfaced with iOS13.6 - #671 is about general consumption with iOS13.5.1
So I expect this  is a different / new issue - thus opened this ticket.

Okay, good point, my fault.
We will see how the Admins handle this.

Battery consumption:

Health Exposure Logging 37% (has been around 15-20% in the past I believe)

One more question:
How are you able to see the battery consumption for the Health Exposure Logging in iOS 13.6?

I only got indicators

I did watch the battery consumption statistics right  after I installed the warn app. I do recall that it was acceptable.
Recently (I guess with iOS 13.6) I observed that I need to charge my device a lot more - even being in home office
Battery statistic showed an increase of consumption for the warn app / apple health so I started to observe more closely
I also noticed that my battery was heavily drained over night - that was very unusual
Last night, I did check my battery - was at 50%. Turned on flight mode. Phone was dead in the morning - 7h time window in flight mode.
Corona / Apple Health shows 37% of battery consumption this morning => Settings => Battery => Battery usage per app

I did not install any other software nor did I change my device setup (knowingly). Not sure if any silent update to any other app have been rolled out. Let me know if a screen shot helps.

Okay thank you.
We will wait for the admins and see.

Recently (I guess with iOS 13.6) I observed that I need to charge my device a lot more - even being in home office

This I also noticed with iOS 13.6, the other points I can't confirm.

Thanks for reporting this issue. This is really unusual as we've received some reports that it got better with 13.6. However, we'd anyway ask you follow-up in #671. Only the last comment references a difference between 13.5 and 13.6 - the rest was more or less generic (as only 13.5 existed when they were written). Let's collect all reports concerning battery consumption there.
One remark though before we close this one: We've also received reports that a restart of the device has mitigated battery consumption. Sounds a little strange to write it here, but have you tried turning it off and on again? ;)
Mit freundlichen Grüßen/Best regards,
SW
Corona Warn-App Open Source Team

I will keep watching and then report into #671  As the device turned off this morning "automatically" I will know soon enough. Sad to see that this "reboot tut gut" thing keeps chasing us - lol


🚀 Feature Request: Change how we detect modules/service-workers

Describe the solution
We currently use esbuild to detect whether a Worker is in service-worker format or module-worker format. This is fairly heavyweight, and can sometimes be wrong. We should shift to something like https://www.npmjs.com/package/es-module-lexer, which is what the Cloudflare dashboard uses.

In the meantime, could you respect the user-configured build.upload.format? / cc #2767

I think it's reasonable to respect build.upload.format if provided by the user, but we should not require it since that would be a big breaking change at this point, and also not aligned with our long term direction.
Once service worker syntax is deprecated, we can safely default to module syntax without heuristics.

When I had a brief look:

--format is a hidden flag only on publish, not dev - so it'd need adding to dev and potentially unhiding

build.upload.format is currently deleted during config validation so messaging would need updating in-case users still have it in their config (ignoring the deprecation notices) & suddenly a new Wrangler update breaks their dev/publish

Wrangler currently sends metrics for various events, would it be worth adding one for when the hint supplied by --format or build.upload.format is different to the 'guessed' format from the heuristics? There may be an uptick at first where users remove build.upload.format now that it is considered by Wrangler, but after that I suspect it'll work nicely in showing if changes (i.e esbuild upgrade) change trends.

There's already a discussion open from October requesting that this is re-added, albeit with no replies: https://github.com/cloudflare/workers-sdk/discussions/2020
I like that Wrangler is able to automatically figure out what I'm using which makes for a pretty seamless init -> publish workflow but I'm sure advanced users would love the escape hatch.

In practice, this isn't a huge performace problem, so closing for now. At the time this was opened Wrangler did many esbuild passes per build, but we've since cleaned that up and so the inital esbuild pass when parsing a user's config is negligible.


[URGENT] Change “preferred” full name to legal full name

People shouldn’t have a preferred full name, change text to “As written in your identification documents” or similar. Upon registration

Don't agree with this one.

When checking IDs, we don't need to be dicks and say "well the photo and surname seems to match, but your forename is different, so go away."

For Scotland (where the event is being held) Section 43 of the Registration of Births, Deaths and Marriages (Scotland) Act 1965 will point out that it is perfectly fine to change your name in Scotland both with and without documentation. The identification documents are slightly more formal to change. This can be read in more simpler terms if you prefer here and here This applies for both your forename and surname.
People are fully entitiled to have a prefered name regardless of the documentation to support it legally or not in any country, not just in Scotland.
Unless official ID is being checked at the event I do not see why this is necessary. As far as I'm aware only student ID is checked which at Edinburgh does not even have your forename on the card.
In my opinion, I see this as your own personal issue with prefered names which is not applicable to this event.

Unless official ID is being checked at the event I do not see why this is necessary. As far as I'm aware only student ID is checked which at Edinburgh does not even have your forename on the card.
Yes, we will check official IDs, and so do most hackathons, definitely Hack Cambridge, all of international hackathons. There are legitimate reasons we have to do this: firstly, we need to make sure they are not under 18, and also, we need to know exactly who is in the building. The way to do it is to check what name is written on their official IDs. This has been made very clear to us.
In my opinion, I see this as your own personal issue with prefered names which is not applicable to this event.
:) I changed my name 2 years ago and boy did I wish I could have started using it earlier. This isn't personal at all, this is a requirement we have to fulfill.

@alistairmackenzie

Unless official ID is being checked at the event I do not see why  this is necessary. As far as I'm aware only student ID is checked which  at Edinburgh does not even have your forename on the card.

Yes, we will check official IDs, and so do most hackathons, definitely  Hack Cambridge, all of international hackathons. There are legitimate  reasons we have to do this: firstly, we need to make sure they are not  under 18, and also, we need to know exactly who is in the building. The  way to do it is to check what name is written on their official IDs. This has been made very clear to us.

In my opinion, I see this as your own personal issue with prefered names which is not applicable to this event.

:) I changed my name 2 years ago and boy did I wish I could have started  using it earlier. This isn't personal at all, this is a requirement we  have to fulfill.

@qaisjp

When checking IDs, we don't need to be dicks and say "well the photo and surname seems to match, but your forename is different, so go away."

Sure, if you know them personally it's not an issue at all. But let's keep things official.

One way to do this, if you really need to check IDs is ask for the full legal name, stating that this will only be used to check for age/identity on their ID, and not be public; and ask for a preferred name that will be used in profile/communications. Not allowing people to specify their preferred name isn't very inclusive (trans individuals) or usable (eg. people with complicated names that are recognised by friends through a shorter version).

@vaidap

One way to do this, if you really need to check IDs is ask for the full legal name, stating that this will only be used to check for age/identity on their ID, and not be public; and ask for a preferred name that will be used in profile/communications. Not allowing people to specify their preferred name isn't very inclusive (trans individuals) or usable (eg. people with complicated names that are recognised by friends through a shorter version).

Agree with this comment, just wondering how to not overload the registration form. Can we have legal name and then preferred name? @qaisjp

we need to make sure they are not under 18 [.. ] Sure, if you know them personally it's not an issue at all. But let's keep things official.

Having both student ID (confirms they are a student perfectly well, regardless of forename), and legal documents (perfectly easy to check birthdate and cross reference photo/surname).
I don't think being reasonable is something we should limit to people we know. The university is not going to turn around and ban us for using someone's preferred name.

we need to know exactly who is in the building. The way to do it is to check what name is written on their official IDs. This has been made very clear to us.

I have just checked with Neil Heatley and he says he has never heard of this requirement for full legal name @ the venue. Are you sure school office is requesting this?

ask for both legal and preferred name

Vaida's suggestion is possible, but a pain to do now. There is the problem of dealing with the 100 (yes, exactly 100) accounts that have already registered. I still think this issue is unnecessary.
This has never been a problem in the past, even at other hackathons. I can't see any reason to be rigid.

@qaisjp Uhh... "Of course we need to know. Qais asked me a question out of context"
I'll check with the School Office though. However, we still need an ID verification for the age...

Migration on this should be super easy btw. Just add getter on name, if the preferred name is defined, return that. Otherwise default to legal name

@elenalape I was clear to him that I was talking about hackathon attendees. I've also confirmed with him, in person, that he has never heard about this requirement.
@visgean the idea would be to keep preferred name as it is now, and add an extra "legal_name" field. Problem here is that we can't just set legal name to preferred name for existing accounts because they could be different. There's also no existing way for users to update their account details atm. We could write an extra tab but then we can't (well, we shouldn't) really email everyone saying "please set your legal name".
All in all, on the day, if we find a name mismatch, a volunteer can just write it down on paper.

At the end of the day, having their legal name is a risk control measure. People are coming in from all over the UK -- we need to know their full names, and we will be checking their government IDs.
Please add the government ID legal name field. Not for the current applicants, let's assume most of them are the same, but for the next 400.

Hi,
Please don't quote private correspondace with me. I was not given a full explained question to speak and at all times pointed to say questions should be directed to the School Office who act as 'the venue'.
I am alsways happy to try and help resolve issues, however do not act as a representative of 'the venue'.
Neil

Given that the UK has no Government issued photo ID that people would be required to have, is there a plan for people who don't have a passport or driving licence? 24% of people born in the UK have no passport, and 10 million UK nationals don't have a driving licence. It seems likely that there would be some overlap between those two groups, and that overlap is likely to be mostly poorer.
It's not the intention, but this policy has the possibility of excluding people who would otherwise meet all of the requirements of taking part.

@JammyStuff I'd like to know how you can make it to the University to study computer science without having an ID, and also how as a uni student you never encounter a situation where you'd need an ID other than your birth certificate. Come on man.

@elenalape I'm not sure how I'm supposed to answer that. What would stop someone who was born in the UK and didn't drive from getting in to University to study Computer Science? You're making it sound like it's an impossible scenario, but last time I checked doing well enough at your exams to get in to University didn't require travel out of the country or the ability to drive. Pretty much everything else offers an alternative.

Thank you everybody for your input, I think we have covered enough and the issue of adding a single extra field or modifying the current one has turned into something completely different, so I am closing it.
The adding of the extra field will be discussed within the actual organising committee.

(oops)


doc building should be more robust

In GitLab by @perarnau on Oct 1, 2020, 14:21
https://github.com/spack/spack/issues/18196
Since 0.1.0 release at least, the doc building seems to be fragile, either for high values of N in -jN, or because configure is not detecting properly that it should not be building something.
I think it's a case of bad use of automake variables, in particular docdir, pkgdocdir, pkghtmldir. We should able to do better.
Bonus points if the patch can be cherry-picked on top of v0.1.x for a bugfix release.

In GitLab by @perarnau on Oct 1, 2020, 17:53
mentioned in commit 89a4ac483a4f47dac410d1c355c8c290b82c97b0

In GitLab by @perarnau on Oct 1, 2020, 17:54
mentioned in merge request !160

In GitLab by @perarnau on Oct 1, 2020, 18:22
mentioned in commit 3844b9b5491c3b6680fbaddf01d9e5f4013f800f

In GitLab by @perarnau on Oct 1, 2020, 18:23
mentioned in merge request !161

In GitLab by @perarnau on Oct 2, 2020, 15:46
mentioned in commit 6d29f26fccbeac0ebac87387995859c65b82730e

In GitLab by @perarnau on Dec 9, 2020, 15:38
closed


Skip run if project has no ABIs

Skip typechain run if all ABIs in a project are empty (which can occur if the project has a single empty contract).
Fixes #717
Fixes #728

Hi @krzkaczor, can you please review this?
This is needed for a feature in OpenZeppelin's tooling, in which users may encounter this scenario if they create an empty contract to start with (therefore resulting in no ABI).
Thanks!


Nicer error message if dependencies are not installed

added a note that running composer install is required.

Thank you @cebe.


Updates to What's New

These are the release notes for https://github.com/dotnet/efcore/releases/.

The team has been working primarily on EF Core internals, so there are no new big features in EF Core 9 (EF9) Preview 2. However, this means we really need people like you to run your code on these new internals and report back what you find. We want to fix bugs in the new internals as soon as possible in order to have a strong GA release later in the year.
That being said, there are several smaller enhancements included in preview 2, many contributed by our community. For full details,
see What's new in EF Core 9. To discuss the EF9 release, go to Try EF Core 9 now! on GitHub.
Improved queries

Inlined uncorrelated subqueries

In EF8, an IQueryable referenced in another query may be executed as a separate database roundtrip.
See Inlined uncorrelated subqueries for full details.

New ToHashSetAsync methods

The ToHashSet methods have existed since .NET Core 2.0. In EF9, the equivalent async methods have been added.
See New ToHashSetAsync<T> methods for full details.

Improved model building

Specify caching for sequences

EF9 allows setting the caching options for database sequences for any relational database provider that supports this.
See Specify caching for sequences for full details.

Specify fill-factor for keys and indexes

EF9 supports specification of the SQL Server fill-factor when using EF Core Migrations to create keys and indexes.
See Specify fill-factor for keys and indexes for full details.

Improved tooling

Fewer rebuilds when using dotnet ef tools

EF9 invalidates build caches less often, resulting in faster re-builds.
See Specify fill-factor for keys and indexes for full details.

Everything else in Preview 2
Preview 2 contains:

8 enhancements
10 bug fixes

EF Core 9 Preview 2 (and Microsoft.Data.Sqlite) contains work from the EF Team at Microsoft (@roji @AndriySvyryd @maumar @ajcvickers) as well as contributions from the EF Core community. The community PRs in EF9 Preview 1 are:

@Poppyto: stackalloc for BytesToDecimal
@francopettinari: Microsoft.Data.Sqlite.Core issue with multiple Blob colums
@wertzui: Added ToHashSetAsync<T> Extension methods on IQueryable<T>
@Suchiman: Fix incremental builds
@btecu: Cleanup asserts
@EngincanV: Fix typos on DeleteBehavior.cs
@petterh: Fix typos, doubled words
@deano-hunter: Add fill factor to keys and unique constraints
@lauxjpn: Cleanup duplicate tests (same test ID)

@ajcvickers The link for improved tooling section seems wrong

Love the new release notes! It also really neatly solves the problem of understanding what was introduced in which previews, without cluttering the "9.0 what's new" docs with per-preview info that most viewers probably don't need when reading it.

Also love the contributor PR mentions!


Does not compile with IW 14.1

Obviously a lot of reorganization has been made with Intraweb 14.1, some methods are private instead of protected and cannot be accessed in classes derived by IWBootstrap.

As it is easy to go back to Intraweb 14.0.63 just by installing this version over 14.1 there should be no pressure on fixing the issues.

Do you have an archive for IW 14.0.63 cannot find it on atozed site

Please ask Atozed - I don't want to run into license issues.
Herzliche Grüße – Kind regards
Michael Schumann, Dipl.-Ing. (FH)
http://itc-ms.de
Tel.  +49 6421 948 0430
Fax  +49 6421 948 0431
------ Originalnachricht ------
Von: "khemebuen"<EMAIL_ADDRESS>An: "kattunga/IWBootstrapFramework"
<EMAIL_ADDRESS>Cc: "michaschumann"<EMAIL_ADDRESS>"Author"<EMAIL_ADDRESS>Gesendet: 23.11.2016 07:21:03
Betreff: Re: [kattunga/IWBootstrapFramework] Does not compile with IW
14.1 (#27)

Do you have an archive for IW 14.0.63 cannot find it on atozed site
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kattunga/IWBootstrapFramework/issues/27#issuecomment-262441636,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWj-WMZRQSl7eAFa0I55x_7g6QjIO2QBks5rA9tPgaJpZM4K5brO.

http://downloads.atozed.com/intraweb/iw14.0.63.exe
On Tue, Nov 22, 2016 at 10:21 PM, khemebuen<EMAIL_ADDRESS>wrote:

Do you have an archive for IW 14.0.63 cannot find it on atozed site
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kattunga/IWBootstrapFramework/issues/27#issuecomment-262441636,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMs_ajNCGmTKdp_xuTEvZs92WCR66C-Pks5rA9tPgaJpZM4K5brO
.

Fixed in latest beta

Great work. I wish I could work with professional people like you in my day to day work! In Germany many people hide behind rules to protect them from doing their job and move forward. Thanks god IT an my job is international...


Suggester component graphical | UX redesign

While users spend most of the time in the suggested component, it may need some new fresh ideas to make it look fresh and user-friendly.
@pondrejk maybe you can start with some analysis of existing libraries, implementations...?

Easier selecting of suggestion - now only the small "play" icon on the left. Allow cursor keys (PgDn/Up, arrow up/down) to select, and perhaps larger select area.

I agree with selection by keyboard, good thing.

display "home" entities (already used elsewhere in T) on text field focus (without the need to type)
I.e. on focus of suggester's text field? Problem: there will be hundreds, rather thousands of entities used in each T.


Support for rowSize

The trouble with chunkSize is that the number of rows are changing based on the CSV row size. When batching data to the server it would be good to have a fixed number of rows.
Could a  rowSize option be added too? (rowSize would be superseded by chunkSize upper limit of course)

You're right, it can be done quite easily by batching inside the dataHandler. Here's how I implemented it.
dataHandler={ async (rows) => {
   // required, receives a list of parsed objects based on defined fields and user column mapping;
   // may be called several times if file is large
   // (if this callback returns a promise, the widget will wait for it before parsing more data)
    console.log("Received batch of rows dataHandler", rows);

    const batchSize: number = 300; // Maximum number of rows per batch
    const batches: any[] = [];
    for (let i = 0; i < rows.length; i += batchSize) {
        batches.push(rows.slice(i, i + batchSize));
    }
    for (const batch of batches) {
        try {
            // Make the API call for each batch
            const res = await axios.post('/importer', {data: batch});
            console.log('Server response', res.data);
        } catch (error) {
            console.error('Error processing batch:', error);
            // return; // return to exit out of 'batch' loop in case of error
            // Or Handle error // Retry or notify the user
        }
    }
}}


Atomic update types only accept one argument

Bug description

The following will not raise an error when static type checking, however it will raise an error at runtime as only one argument can be passed to the atomic update query:
updated = await client.post.update(
    where={
        'id': 1,
    },
    data={
        'views': {
            'divide': 1,
            'multiply': 2,
        },
    },
)

Expected behavior

An error should be raised by pyright and mypy
Prisma information

N/A, internal test setup
Environment & setup

N/A, internal test setup

Fixed in 5cf9ec12fcda08b6ae2d8d5b3a926bc0d9024c6a


Bump E/App and Onyx to use NodeJS 18.17.1 LTS

Problem
Both E/App and Onyx repos currently enforces developers to use NodeJS 16.15.1. As of September, NodeJS 16.x will reach its End-of-life (EOL), meaning there will be no more updates, patches, or security fixes. Additionally, the future React Native 0.73 version will require using NodeJS 18.x.
Using an outdated version of NodeJS not only exposes the application to potential security vulnerabilities, compatibility issues, and prevents developers from leveraging the latest features, optimizations, and improvements available in newer versions of NodeJS, but it will also block us from updating the App to RN 0.73 or higher versions.
Solution
Upgrade both repos to require NodeJS 18.17.1 (or 18.x) and NPM 9.6.7. This will ensure that the application remains secure, compliant, in line with best practices for software development and will allows us to continue updating our app to latest RN versions.
Plan
For react-native-onyx:

Change package.json to require NodeJS 18.17.1 and NPM 9.6.7.

Alternatively, since this is a open-source library we could relax the version enforcement to only 18.x, in this way developers/companies who uses Onyx don't need to use a strict version, just the LTS release.

Change .nvmrc to require 18.17.1 (or v18).
Change publish.yml, test.yml and lint.yml to use the node version from .nvmrc file instead of hardcoded version.

For E/App:

Change package.json to require NodeJS 18.17.1 and NPM 9.6.7.
Change .nvmrc to require 18.17.1.
Change TestSpec.yml to use .nvmrc (if possible) or 18.17.1.
Fix build-desktop.sh to drop npm bin usage since it was removed in NPM 9.x, and use npx instead.

Tests
I forked Onyx to use 18.17.1 and used my own release in E/APP in order to test the changes and I was able to install the dependencies and build for all platforms. When running tests I got some dependency errors about node version mismatched in installed packages, was able to resolve the issues by running npm rebuild (probably just removing node_modules and reinstalling would work as well).
I also didn't have any issues with dependencies auto-updating or changing package-lock.json.

@AndrewGable @roryabraham Based on this idea posted here: https://expensify.slack.com/archives/C01GTK53T8Q/p1692277812800739

Looks great!

Hey, I would love to work on the issue. Can I get assigned? Do I need to post proposal?

@fabioh8010 is assigned and will be working on this one. 👍

@AndrewGable
@pac-guerreiro Will take the issue over! Could you assign him?

On HOLD until after the merge freeze

@fabioh8010 - Can you have him comment here? Thanks.

Hi @AndrewGable, I can take this 😄

BTW, I think this issue is a bit lower urgency, so due of the backlog of issues that we have been HOLDing the last couple weeks, I suggest that we wait until a few days after the merge freeze is lifted to take this off HOLD. That way we don't have a huge amount of PRs merged all on the same day and end up with a massive release that's very hard to ship

What's the latest here @pac-guerreiro ?

What's the status here?

Looks like I just forgot to take this off HOLD after the merge freeze. Let's get this one finished up. co-assigning myself to help track progress

Also, I'm wondering if we should beat around the bush or should go straight to the newest LTS version. Node.js 20 just became active LTS today, so I'm going to update the issue title to say we should standardize on the latest LTS.

Sounds good to me, I can work on these changes. I'll have to apply the changes to onyx first.

Github actions started supporting node20 last week

@roryabraham I just created two draft PRs with the changes applied to both react-native-onyx and expensify-app 😄

Let us know when they're ready for review

@dylanexpensify @roryabraham The PR for Onyx is now open! The one for the app will remain in draft until the Onyx one is merged because until this happens, the app will throw compatibility errors with Onyx because of node version

@DylanDylann @roryabraham
I addressed the feedback on the PR for Onyx! Let me know if there is anything else that needs to be taken care of and sorry for the time this has been taking to be merged.

This is done now, just awaiting deploy to production (even though it mostly affects dev/test environments)

Looks like none of the PRs underwent C+ review, so we can close this.

No regression tests needed

Can you send an action required email to internal engineers on this?

I think @arosiclair sent one


react-component needs to be in array

Currently react-hyperscript requires children react components to be in an array even when there is only one child. Support passing in one child component without having to wrap it in an array.

I might be a bit of the niave side of this, but is there any huge performance hit by not enforcing an array at all?
h('div', {}, firstChild, secondChild, thirdChild);

You can grab all of these children internally using arguments, and build an array.
My main cause is that I have been using react with coffeescript, and with this syntax, it would read similar to:
h 'ol', {},
  h 'li', {}, 'First Item'
  h 'li', {}, 'Second Item'

Internally, you'd have to do something like:
childArray = Array.prototype.slice.call(arguments, 2);

I think it offers a good compromise.  Backwards compatibility would have to be checked;
if typeof(arguments[2]) == 'array'
  childArray = arguments[2];
else
  childArray = Array.prototype.slice.call(arguments, 2);

I don't know if that's a big performance hit, either.  Just a thought.

@mrozbarry +1

@mrozbarry
if typeof(arguments[2]) == 'array'
  childArray = arguments[2];
else
  childArray = Array.prototype.slice.call(arguments, 2);

Is a performance hit. And it even doesn't account for cases in which you wouldn't have the second argument as props.

I think if it doesn't have a negative impact on performance it'd be good to support this.  Other libraries with similar api's (e.g. mithril) support variadic children.  I often jump between frameworks for different projects and it'd be nice to be able to re-use templates with minimal effort and surprise.

found that is easier to use React.createElement() since it doesn't require an array:

True, but it doesn't support css selector syntax, so it's not compatible with some pretty compelling work flows like e.g. bss.
If variadics are supported by React.createElement, then that's another reason to support it in react-hyperscript.


Server crash

http://pastebin.com/mrj75sZN
Getting this crash when our server is on an auto-startup script.  everytime.

That error makes 0% sense to me, the method shown in the stack trace is a 1 liner that shouldn't even be capable of throwing any exceptions. That's either coremod shenanigans or a something borked in the JVM.
What was the last thing you changed in your setup before it started?

Actually looking into it some more it looks like the server watchdog is causing the shutdown...
What is max-tick-time set to in your properties file?
Also there should be a line like that in the log:

A single server tick took ___ seconds (should be max ___)

What does it say?

max-tick-time=60000
We don't see a line in our log that looks like what you described, fyi.

Hm, then i still don't have any idea what might be going on here.
I did a bit of googling and the only instance of that error that i found was this crash report that looks like the same weird error but doesn't involve any of my mods. That log seems to be from this issue but it doesn't really have anything helpful.

Is there anything we can do on our end to try to help figure this out?

No idea at this moment, sorry. If i think of something i'll let you know.

We are going to update our wrapper "MARK2" and  java just to make sure.

http://paste.ubuntu.com/23598970/
Updated to latest BDLib, getting this crash on server startup now.

@bdew , I could zip up the server and drop it here if you like. To try to reproduce the problem.

Another crash on server reboot.
http://pastebin.com/rvxjGFLS

@bdew , I could zip up the server and drop it here if you like. To try to reproduce the problem.

Sure, go ahead

I'm closing this issue as part of a spring cleaning of my issue trackers from old stuff.
If you believe it's a bug that is still relevant in Minecraft 1.12 - Feel free to reopen it.


docs: integrations reference updates 13

Added missed provider pages and links. Fixed inconsistent formatting.
Added arxiv references to docstirngs.

@ccurme Can you, please, copy-paste the Vercel error? I don't have access to it and cannot fix it. :( Thanks!

some sort of content hashing problem

@efriis I was trying to rerun checks with rebasing merged PRs, but I had no luck.

@efriis
Is that possible that checks failed on this (in templates/rag-aws-bedrock/README.md)?

langchain serve

This will start the FastAPI app with a server running locally at http://localhost:8000
You can see all templates at http://<IP_ADDRESS>:8000/docs and access the playground at
http://<IP_ADDRESS>:8000/rag-aws-bedrock/playground.

@hwchase17 Thanks!


bsRecord on inline fragment

Hi,
I am trying to write a query containing union types. I first wrote a separated fragment and got a clear message: only inline fragments are supported with union types. So I wrote my query like this:
module Search = [%graphql
  {|
    query Search($query: String!, $searchType: SearchType!) {
      search(first: 10, query: $query, searchType: $searchType) @bsRecord {
        edges @bsRecord {
          node {
            ... on Dataset @bsRecord {
              id
              dataType
            }
          }
        }
      }
    }
  |}
];

But the bsRecord on the ... on Dataset @bsRecord does not work: the fragment is parsed as an object instead of a record. Is this a bug or am I doing something wrong?
Thanks :)

Don't you also need @bsRecord on node?

Adding or removing @bsRecord from node does not change the parsing either.

This is a bug in the current limitation, thanks for reporting this.

Fixed in 0.2.8.

Hi @mhallin! The bug seems to be fixed in 0.2.8 for union types, but I still have the bug for interfaces :/


Farm run reminder

Is your feature request related to a problem? Please describe.
Missed farm runs due to lack of attention to the widget
Describe the solution you'd like
A clear OSD reminding to do farm runs
Ability to choose its location/size
Ability to choose which patches you are interested in
Ability to group patches (or do by default) to remind when ALL have grown
Describe alternatives you've considered
Tray notification instead of OSD (if selected should override default setting)
Additional context
Basically a very clear and simple reminder to do your farm run or herb run.

Duplicate #2212


Story 103 documentation logo broken

Done.

A new inspection was created.

The inspection completed: 1359 new issues


Changing configuration with docker

Hi !
I just started to experiment with gekko and launched it using docker on my ubuntu 16.04 NAS. How can I adjust now the configuration (except those which are done using the web interface) ?
thanks for your help!
yours
arnold

Hey, what specific settings did you have in mind? The UI allows you to configure all the strategy settings and such without touching a configuration file.
There is a PR open for adding postgresql to the docker files, see #947.

how can I configure gekko as an autotrade bot without touching the config file ?
yours
Arnold
Am 13. Aug. 2017, 17:17 +0200 schrieb Mike van Rossum<EMAIL_ADDRESS>
Hey, what specific settings did you have in mind? The UI allows you to configure all the strategy settings and such without touching a configuration file.
There is a PR open for adding postgresql to the docker files, see #947.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

First you install Gekko as explained here: https://gekko.wizb.it/docs/installation/installing_gekko.html
After that start the UI, go to live gekkos, configure it how you want it (in the UI) and click "tradebot"!

ok - I have now a tradebot - but how can I delete it again ?

As in stop the bot? Will be part of the next release, see here: #911!

yes stopping the bot so that I can configure a new one. thats why I asked where to modify config files. also how does the hot decide which amount he is tradibg with ?
sorry for maybe dumb questions
yours
Arnold
Am 13. Aug. 2017, 22:13 +0200 schrieb Mike van Rossum<EMAIL_ADDRESS>
As in stop the bot? Will be part of the next release, see here: #911!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Gekko will always use the full balance available!


Rename NoType to VoidType and print it as "void".

We have been using void in the "theoretical" type system since Scala.js 1.0.0, but for historical, NoType kept its old name.
We now officially rename it to VoidType, and print it as void instead of <notype>, giving it a true Type status.

I've been wanting to do this for a while now. I finally took it up. :sweat_smile:

Regarding the PR title: I'm not a fan that the PR title suggests this is a merely a rename / printer change, but there is (quite deeply hidden) a rather fundamental change of how we type record types.
To someone looking through a changelog / commit history, I think it would be quite difficult to identify that this change sequence has changed subtyping relationships.
(then again, records are internal, and any attempt to actually return a record type somewhere to JS would likely fail).

Right, good point. I extracted that functional change in a separate PR #5065.

Rebased and fixed the commit message typo.


Prevent deletion of setting or config if it is not empty

Is your feature request related to a problem? Please describe.
We use the provider in a multiple environment model. With every deployment of an app to each environment, a set of settings and initial_values are created.
The provider does not care if we try to define an existing setting or config multiple times. If the target exists, it basically links it to the resource.
Now, if we delete a setting in our demo deployment, it will remove that setting no matter if it has values for other environments, for example staging or live.
Describe the solution you'd like
Upon deleting request for setting/config, the provider should check if there is any child objects in the config (i.e. other settings) or in the setting (i.e. values for other environments). If it is not empty, it should raise an error that you cannot programmatically delete the target unless all the child resources are deleted.
This prevents the config/setting from being deleted and impacts other environments.
To make this some how opt-in for user, you can enable a controlling flag in the provider configuration.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context about the feature request here.

Hello @ksaffarian ,
Thanks for reaching out.
Could you please send us some snippets of your terraform configuration files? The provider doesn't link existing settings or configs, so it would be awesome to see how do you define your configs and settings.
What do you mean on "we delete a setting in our demo deployment" and "if it has values for other environments"?
Cheers,
Lali

Hey Lali
Thanks for confirming that it should not work, with existing resources.
After you said so, I went and re-checked this myself and you are right. I created this issue based on our developer experience, which I should have vetted myself first.
You can disregard this request for now.
I believe we should follow the pattern suggested here: https://registry.terraform.io/providers/configcat/configcat/latest/docs/guides/multi_environments to make sure things work correctly.
Thanks again.


Error: spawn pycodestyle ENOENT

Error: spawn pycodestyle ENOENT
Error: spawn pycodestyle ENOENT
    at exports._errnoException (util.js:1026:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
    at onErrorNT (internal/child_process.js:359:16)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

I think this could ba conflict between some of my installed packages, but this just started happening after my update.
I have disabled all the other python related packages and this error still pops up.
I have now disabled this package and will provide more feedback if you require any.
ommunity Packages (15) /home/aaron/.atom/packages
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

I guess since the package was renamed we have to install the pycodestyle package like it's written in the README file.
pip install pycodestyle
I had the same issue and solved it by installing the package pycodestyle. I hope this comment will help you.

pep8 was replaced with pycodestyle back in June. If for some reason you still need to use the outdated pep8 versions you can simply specify that in the Executable Path setting.


--v4 flag

The slogan:
"Run your BP3 project with --v4 and if it works, it will work with BP4."

Yes.  My plan is to remove everything except deprecated.py (which we might use in the future).
That fscking UDP test is timing out again.  I have to figure out a better way...

Ping!!!

Sorry, yeah... this is fine. Merge away.


[WIP] Update Istio Performance Grafana Dashboard to the latest

https://github.com/istio/istio/issues/27907
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ x] Performance and Scalability
[x ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@carolynhu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio
f27e70ce3aa243bb5cb7e5bd112221f1d2a86e84
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

https://snapshot.raintank.io/dashboard/snapshot/zaNQqc3pO0DnBY5CVkfjuEoUscjSSFW4

https://snapshot.raintank.io/dashboard/snapshot/zaNQqc3pO0DnBY5CVkfjuEoUscjSSFW4

@howardjohn should we rename anything Pilot to Istiod ?  what's our policy around that moving forward?

@douglas-reid I would rename everything to Istiod except the actual metrics since those need to be backwards compatible

@douglas-reid I would rename everything to Istiod except the actual metrics since those need to be backwards compatible

@carolynhu since you are already touching this dashboard, can you change the row name with Pilot to use Istiod instead?

@douglas-reid @howardjohn you mean rename the chart name to Istiod resource usage, but keep legendform to be pilot-xx?


grafana-watcher is stuck on Waiting for Grafana to be available

What did you do?
I have deployed all default manifests with deploy script .
What did you expect to see?
Expect to see grafana up and dashboards loaded
What did you see instead? Under which circumstances?
Dashboards are not loaded
Environment
prometheus-opetrator  = Latest

Kubernetes version information:
Kubernetes = 1.5.2
insert output of kubectl version here
-bash-4.2$ kubectl version
Client Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.1", GitCommit:"82450d03cb057bab0950214ef122b67c83fb11df", GitTreeState:"clean", BuildDate:"2016-12-14T00:57:05Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.0", GitCommit:"58b7c16a52c03e4a849874602be42ee71afdcab1", GitTreeState:"clean", BuildDate:"2016-12-12T23:31:15Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
insert how you created your cluster: kops, bootkube, tectonic-installer, etc.

Manifests:

insert manifests relevant to the issue

kubectl -n monitoring logs grafana-3997532808-3pvd5 grafana
t=2017-03-22T19:58:46+0000 lvl=info msg="Executing migration" logger=migrator id="add index alert dashboard_id"
t=2017-03-22T19:58:46+0000 lvl=info msg="Executing migration" logger=migrator id="create alert_notification table v1"
t=2017-03-22T19:58:46+0000 lvl=info msg="Executing migration" logger=migrator id="Add column is_default"
t=2017-03-22T19:58:46+0000 lvl=info msg="Executing migration" logger=migrator id="add index alert_notification org_id & name"
t=2017-03-22T19:58:46+0000 lvl=info msg="Executing migration" logger=migrator id="Drop old annotation table v4"
t=2017-03-22T19:58:46+0000 lvl=info msg="Executing migration" logger=migrator id="create annotation table v5"
t=2017-03-22T19:58:46+0000 lvl=info msg="Executing migration" logger=migrator id="add index annotation 0 v3"
t=2017-03-22T19:58:46+0000 lvl=info msg="Executing migration" logger=migrator id="add index annotation 1 v3"
t=2017-03-22T19:58:46+0000 lvl=info msg="Executing migration" logger=migrator id="add index annotation 2 v3"
t=2017-03-22T19:58:46+0000 lvl=info msg="Executing migration" logger=migrator id="add index annotation 3 v3"
t=2017-03-22T19:58:46+0000 lvl=info msg="Executing migration" logger=migrator id="add index annotation 4 v3"
t=2017-03-22T19:58:46+0000 lvl=info msg="Created default admin user: [admin]"
t=2017-03-22T19:58:46+0000 lvl=info msg="Starting plugin search" logger=plugins
t=2017-03-22T19:58:46+0000 lvl=warn msg="Plugin dir does not exist" logger=plugins dir=/var/lib/grafana/plugins
t=2017-03-22T19:58:46+0000 lvl=info msg="Plugin dir created" logger=plugins dir=/var/lib/grafana/plugins
t=2017-03-22T19:58:46+0000 lvl=info msg="Initializing CleanUpService" logger=cleanup
t=2017-03-22T19:58:46+0000 lvl=info msg="Initializing Alerting" logger=alerting.engine
t=2017-03-22T19:58:46+0000 lvl=info msg="Initializing HTTP Server" logger=server address=<IP_ADDRESS>:3000 protocol=http subUrl=
-bash-4.2$ kubectl -n monitoring logs grafana-3997532808-3pvd5 grafana-watcher
2017/03/22 19:58:45 Waiting for Grafana to be available.
2017/03/22 19:59:16 Waiting for Grafana to be available.
2017/03/22 19:59:47 Waiting for Grafana to be available.
2017/03/22 20:00:18 Waiting for Grafana to be available.
2017/03/22 20:00:49 Waiting for Grafana to be available.
2017/03/22 20:01:20 Waiting for Grafana to be available.
2017/03/22 20:01:51 Waiting for Grafana to be available.
2017/03/22 20:02:22 Waiting for Grafana to be available.
2017/03/22 20:02:53 Waiting for Grafana to be available.
2017/03/22 20:03:24 Waiting for Grafana to be available.
2017/03/22 20:03:55 Waiting for Grafana to be available.

Prometheus Operator Logs:

insert Prometheus Operator logs relevant to the issue here

Thanks for reporting! Very interesting. Are you able to reproduce this?

Appeared to be K8s DNS issue . My bad :-(

No problem! Could you explain what happened? It would be great if we could start collecting everything we see in a troubleshooting document. If you want to you can create a PR to the docs with a new document called troubleshooting.md. :slightly_smiling_face:


Switch Target Framework version to .NET 4.5 / 4.5.2

Hi,
I saw that the target .NET Framework for Jurassic was changed from 3.5 to 4.0.
However, according to Microsoft .NET Framework Support Lifecycle Policy FAQ, Support for .NET 4.0, 4.5 and 4.5.1 has ended at January 12, 2016.
Therefore, I think it makes sence to not only switch to 4.0 but instead to 4.5 (or even 4.5.2).
Thanks!

I needed to switch to v4.0 because that's the first version that has the ConditionalWeakTable class.  Is there any benefit for a class library to switch to v4.5?

Hi,
If there is currently no need to use a type that is available in v4.5 or higher, then there is no immediate benefit in switching to v4.5.
My thinking was, since this is going to be a new major version (Jurassic 3.0) where a higher .NET version than v3.5 is required anyway (with using of the ConditionalWeakTable), it might make sense to switch to v4.5 instead of to v4.0, because then if in the lifetime of the Jurassic 3.0 version a change or new feature is required that is only available in v4.5, you can just start using it (and if someone has the v4 CLR installed, we can except the BCL to be at least v4.5.2 as this is the minimum supported version).
However, of course it is up to you if you want to make that change, I can live with the library targeting v4.0. :-)

I'm closing this issue as Jurassic now targets .NET Standard 2.0.


Changed OE repo to prepare for TrustZone merge.

@gupta-ak Looks good to me. Can we make sure we get the approval of all concerned parties before merging this in?

@gupta-ak Should we merge this now while the repo is quiet?

Going for it.
bors r+

@andschwa I think it is better to let @gupta-ak drive this. I think he is waiting for a review from @HernanGatta

Taking another pass over this.
It is not clear what the install story is in the merged repository.
When the user types:
make install
where do the Open Enclave SGX and Optee libraries live?
Can the same installation support both SGX and Optee development?

@anakrish I'm not sure how the make install story works on TZ. I generally see packages split based off arch when looking at the ubuntu package repo. The current changes only change the source files and not the package output directory, so the process should be identical if we want to go that way.

Ok. Sounds good. Approving.

bors r+

Thanks @gupta-ak!


add scalafmt and apply it

I use scalastyle from, I believe, google imported into Intellij, it looks good to me. overall I don't like to many "new line" if there no particular reason.

OK, thanks @macchiatow , I now use scalafmt, I learn scalastyle later on.

close it, if need reopen.


⚠ Samsung has degraded performance

In 84b8bc5, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2815 ms

Resolved: Samsung performance has improved in 4f02950.


Unable to delete an image

If you are reporting a problem, please make sure the following information are provided:
1)Version of docker engine and docker-compose
2)Config files of harbor, you can get them by packaging "Deploy/config" directory
3)Log files, you can get them by package the /var/log/harbor/

There's nothing we can do with such information

thanks for the reply. then how can we delete the old images pushed in to the projects

docker engine - 1.11.1
docker compose - 1.7
Harbor - 0.1.1 package

@manginkr The deletion of repositories and tags is supported in the latest code. You can use the API of Harbor to delete them for now. About the details of Harbor API, please see docs/swagger.yaml. And the issue #112 explains the implements.

The deletion of projects is not supported for now.

How about deletion of repositories
On May 14, 2016 6:25 PM, "Deshi Xiao"<EMAIL_ADDRESS>wrote:

The deletion of projects is not supported for now.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/vmware/harbor/issues/208#issuecomment-219218908

https://github.com/vmware/harbor/blob/master/api/repository.go#L113
it works


Windows performance profiling

Where's all the IO coming from, yo?
Update this with our plan and learnings for profiling Windows performance.

So I did a bunch of work on this with simple timing on windows/unix awhile back and strace on unix.  That led to:
https://github.com/rubygems/rubygems/issues/2762
Which led to:
https://bugs.ruby-lang.org/issues/15856
Which led to:
https://github.com/chef/omnibus-software/pull/1113

I also found that stat-vs-open doesn't make much of a different on either windows or unix.  I don't know why ruby tends to use open rather than stat to check if a file exists, i suspect that helps with resolving complicated acl issues so that you validate that it both exists and is readable at the same time.  Either way it seems to not make a difference.

And on unix what I've mostly done is just:
time /opt/chef/bin/chef-client
strace -c /opt/chef/bin/chef-client
strace trace=open,stat /opt/chef/bin/chef-client

And the top calls typically looks like this:
Chef Infra Client: 15.0.276
/opt/chef/bin/chef-client --version  2.43s user 0.90s system 83% cpu 4.011 total

% strace -f -c /opt/chef/bin/chef-client --version
strace: Process 44180 attached
Chef Infra Client: 15.0.276
% time     seconds  usecs/call     calls    errors syscall
------ ----------- ----------- --------- --------- ----------------
 47.55    0.360709           3    138777    134075 stat
 39.71    0.301194           3    105846    102814 open
  5.87    0.044508           2     18266           lstat

100,000-ish stat+open calls is typical.
So the TL;DR of fixing it looks like:

investigate how to make all that I/O go away entirely
investigate why that I/O is so slow on windows in particular (and maybe our way of building windows in particular?)

Using RubyInstaller 2.6.5p114 with non-appbundled chef-client binstub:
2.96 2.98 2.91 2.88
Using RubyInstaller 2.6.5p114 with appbundled chef-client binstubs:
3.14 3.25 3.17 3.36

Chef 15.4.45 with non-appbundled chef-client binstubs:
4.15 4.42 4.21 4.09
Chef 15.4.45 with appbundled chef-client binstubs:
4.27 3.98 4.14 4.23

So 22% speed improvement from using RubyInstaller over our homegrown builds

Chef 15.5.4 performance with appbundled chef-client binstubs (chef-client --version timing):
3.77 3.62 3.56 3.91 = 3.7150 seconds
Compared to the prior 4.15500 seconds, so 10% net speedup between the -O2 to -O3 fix and the patch to ruby


MDCA - Update URL API logic selection

When evaluating the tenant region, exlude the response "tenant is disabled" from the possible selection.
Fixes #236

Add to review the logic. And eventually fail early if no valid URL are found.
@briandelmsft give it a try, I tried 100 attempts and they all ✅

Success!! 🎉 💥


Calendar extender not selecting years

When StartDate is setting for Calendar extender (in Properties or in program)  you cannot select other page in Year mode.  Version 16.0

I cannot reproduce the described behavior.
Would you please provide a sample project that illustrates this issue?

I Cannot attach ZIP file! Bug! Bug!

How I can send project ?

Maybe it's too large?

17 Mb

I believe you can remove the packages folder to get rid of binaries that can be restored by NuGet during compilation.

IE11, Edge cannot work, filesize 6Mb

https://cloud.mail.ru/public/GcHv/3eD5RkkuL


[Draft] create listener to refresh search thread resource usage

Description
[Describe what this change achieves]
Related Issues
Resolves #[Issue number to be closed when this PR is merged]

Check List

[ ] Functionality includes testing.
[ ] API changes companion pull request created, if applicable.
[ ] Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Closing as new PR created with the changes : https://github.com/opensearch-project/OpenSearch/pull/14832


SDK iOS build script

It's more of an SDK feature request, but I didn't find a better place to post it. Hopefully, it's ok.
In the BL_BuildPostProcess there is a line with an assumed base path:
const string defaultLocationInProj = "AgoraEngine/Plugins/iOS";
I think, the assumption here is that AgoraEngine is placed directly in the Assets folder, which is not always the case, at least for the commercial projects, that I've worked on.
Usually, any dependencies are stored in a subfolder like Assets/3rdParty/ or Assets/ThirdParty/.
It would be nice if the script would actually read the base path allowing more flexibility (if possible, I don't have much experience with writing editor scripts).
It's definitely not critical, but I'm sure it would save at least a few people from debugging their iOS build errors, so it might be worth considering :)

Thanks for your suggestion.

We will try to improve the expercience of our sdk.

Thank you! :)


[Question] How to have global parameters

I was hoping that someone will be able to help me, with what I am referring to as global parameters, but this might be known under a different name.
When parsing my input arguments, I want to have an option to include things like a -v argument, which version parsed, will print out the version number of my command line tool.  In addition, I want to be able to have verbs for doing specific pieces of functionality, like transform, and then have additional arguments for this command.
Individually, I can get this to work, i.e. have an Option for -v, and have a VerbOption for transform, however, I don't seem to be able to combine them.  Am I missing something?
So to recap, what I would like to be able to do is:
my.exe -v
my.exe transform -i "c:/temp/input.xml" -o "c:/temp/output.html"
Is this possible?
Each time I try it, my Version Option is always false.
NOTE: I am using CommandLineParser 1.9.71.

I have just looked at the pre-release version of this project, and it looks like it included a default --version which is exactly what I am looking for :+1:  Is there any way to alter this so that it also supports -v?

#250 explains why I'm replying late...
@gep13, for the moment 2.0.*-beta (very close to be promoted RC and than STABLE), doesn't support short options name for built-in --help and --version.
This choice is conventional based on standard *nix utility based that implements getopt() conventions.
I don't think this will be changed, but you can do this in a custom fork with easy.
In Text/HelpText.cs two private methods handle these built-in options MakeHelpEntry() and MakeVersionEntry().
I can link one of it but if sources change the line number may vary.
Let's take MakeVersionEntry: just replace string.Empty with "v" as first parameter of OptionSpecification.NewSwitch and you'll be able to print out version as you ask.
I hope this helped. :)

@gsscoder yip, I had already read that issue, so I appreciate you taking the time to get back to me!
I guess the reason that I was asking was that with some other tools, like node, npm, gulp, bower, etc, I can run the -v parameter, and get some immediate information about the version of that tool:

So, for the sake of consistency, I wanted to add the same to my console applications.
I am a Windows guy, so I am not clear on what you are referring to when you say:

*nix utility based that implements getopt() conventions.

But I will take your word for it :smile:
I will have a think about whether I want to take a fork for commandline to get what I want.  Thanks again.

@gep13, consistency is always a good thing, nowadays a lot of terminal commands mix a lot of styles allowing long options with a single dash and other things.
Requesting version with a short option is not really so out-of-standard and after 2.0 reaches STABLE status this choice can be re-evaluated.
There's another "philosophical" choice in implementing built-in --help and --version without short option character defined and this is to allowing user commands with h and v.
Now we can open a discussion about if this makes sense or not... For what I can observe, more a terminal command stick to "common standard" and more exposes these two commands only as long options.
Thanks for starting an interesting discussion, not only code submission allow a project to grow... :)
So we can rethink this after 2.0 reaches STABLE status, as said.
Thank you again.

Sounds like a plan to me :-)
As a side note, if I wanted to add some additional top level arguments, similar to --help and --version how can I do this, without re-compiling commandline?  Or can I? Everything I tried didn't seem to work.
Thanks again!

You could add a new verb for each. --help and --version are just built-in verbs.

@nemec said...
You could add a new verb for each. --help and --version are just built-in verbs.

Ah, of course, thank you!  I think I was overthinking the problem :smile:

Problem solved, closing this. :)


SystemJS

Hi there,
is there a possibility to get this webpack-module as SystemJS-module?

resolved with webpack-system-register


Having to often repeat command

I think I've seen this issue before in the past.  I have to repeat a command before it actually gets executed.  I will say Alexa, Turn on TV..it'll say OK but then nothing happens.  If I say it again then it works.  This happens more often than not.  When I had this issue before I was running two HABridges and was told to kill one and that would solve my problem.  That didn't work.  Any ideas?

Since you were running two bridges did you go into your Alexa app and check for and  remove the extra TV and other devices  it maybe seeing?

seems like this issue got forgotten #671

@tuicemen ...I did go through and made sure Alexa "forgot" all the devices that were attached to the removed HABridge.  Those devices were marked in the Alexa app as "Offline".  I am running only single instances of my devices.

@pickeld The #671 is very specific to Home Assistant and the way it handles http requests. Currently, it is an issue on the HA side.

@lemrock So, you had devices show offline before you did a forget and discover?

@bwssytems... Alexa app showed devices offline after I removed the second HABridge.  That made sense to me because they were removed with the HABridge.  Then I forgot all the offine devices and then discovered.
Maybe this can help in troubleshooting.  The repeat of commands when it happens is with any device that "On-Dims-Off".  It doesn't seem to happen on "On-Off" devices.  Also If I say Alexa "Turn on Lights 100 percent" it works everytime,  but if I say Alexa "Turn on Lights"  it will most likely say OK but nothing happens until I say it again.

could you send me your device.db please

Try forget all then rediscover.
It is possible everything wasn't wiped on the amazon side of things or something got corrupt.

@tuicemen ..I did forget everything and rediscovered and the problem was still there.
@bwssytems ...my device.db file is attached.
device.db.txt

So I assume you are trying to turn on "Living Room TV" and it is a harmony device. Does this happen with all Harmony devices? Does this happen with your Vera?

None of my Harmony devices are affected by the issue I described.  I control Harmony through the Vera via Scenes and the Harmony Hub via the Alexa HArmony Skill. Devices that are affected are anything that has Dim control.  That is obviously lights and I have Vents that have position (Dim) control.  My shade shave a position (Dim) control but that function has never worked.

Well, that is more specific.

@lemrock What version are you running? Also, I see that your device.db has not been updated recently. Hit the renumber devices button on the config page and then have alexa forget and discover your devices.

I have a similar issue.
I use Homseer and with the bridge I notice if I have to reinitialize the bridge, it then takes 2 subsequent commands to turn on a light that has a dim capability. A way around this I have found is if I go to the bridge webpage and manually turn on the light, then click the dim setting button, the next command from alexa will then turn the light on and off appropriately. Something about the dim setting pop up window seems to hold up the process. Any of my harmony activities or lights that cannot dim work fine first try.

@bwssytems ...I am running your version 4.5.6.  I also did what you suggested (renumber, forget, discover) and the issue is still there.  I see that JJAZ reported a similar issue (DIM devices).

You'll need to turn on debug for me https://github.com/bwssytems/ha-bridge#the-logs-tab and post your log.

Turned on Debug for the Huemulator.  In this log you should see the issue I described for 2 devices Ceiling Lights 2 and Entryway Lights. Ask to turn on but doesn't, ask a second time and it does.  Problem only appears for devices that DIm.
BridgeLog.docx

Well, ha-bridge is calling your vera without error for the 2 calls to each device that you are requesting. My only concern is that in the startup of your bridge, there is a network error for multicast upnp. That may be an issue of network setup with your machine you run the ha-bridge on.

I'm running the habridge on a Raspberry Pi 2 and over wifi. Any suggestions about what I could look at and is there another DEBUG parameter I could turn on.

Unfortunately, it is not ha-bridge debug related. It is your Pi 2 network config. The issue is from an error when trying to reply to the multicast request. That may or may not have any effect on your issue.

Any update on this?

No update.  I’ve done everything recommended but I still have to ask Alexa twice before any command is executed.  I’ve just decided to live with it. The clue i think to solve this is it only happens on devices with dim control.
Sent from my iPhone

On Oct 19, 2017, at 9:17 AM, BWS Systems<EMAIL_ADDRESS>wrote:
Any update on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hopefully the new http handling in 5.0.0 will make this a non issue.


Update gpt2.cpp - the current code does not accept -q8 with any model due to conditional OR

Corrected the logic to ensure that -q8 is called with -lg or -xl

Hi @rahulraj80, I fixed the issue. Thanks for the correction.


New error since today

http://image.noelshack.com/fichiers/2018/47/2/1542723528-error.jpg

Hi, thank you for your help. I close this because your resource isn't the problem and sorry for this!

All right no problem, that's why it is important to show the beginning of the error log ;) (a crashing module can crash the others as they loads)


Fix file mode of README.md

Summary
README.md should not be executable - fix the mode bits.
Category (place an x in each of the [ ])

[ ] slack_sdk.web.WebClient (sync/async) (Web API client)
[ ] slack_sdk.webhook.WebhookClient (sync/async) (Incoming Webhook, response_url sender)
[ ] slack_sdk.socket_mode (Socket Mode client)
[ ] slack_sdk.signature (Request Signature Verifier)
[ ] slack_sdk.oauth (OAuth Flow Utilities)
[ ] slack_sdk.models (UI component builders)
[ ] slack_sdk.scim (SCIM API client)
[ ] slack_sdk.audit_logs (Audit Logs API client)
[ ] slack_sdk.rtm_v2 (RTM client)
[ ] /docs-src (Documents, have you run ./scripts/docs.sh?)
[ ] /docs-src-v2 (Documents, have you run ./scripts/docs-v2.sh?)
[ ] /tutorial (PythOnBoardingBot tutorial)
[ ] tests/integration_tests (Automated tests for this library)
[x] none of the above

Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[ ] I've run python3 -m venv .venv && source .venv/bin/activate && ./scripts/run_validation.sh after making the changes.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Get Appveyor to build GEOS and pygeos whl files for Windows

This PR builds binary .whl files for Windows on AppVeyor, and the artefacts should be suitable to be uploaded to PyPi as discussed on #98
GEOS static and dynamic libraries are built with MSVC 2017 for Python 3.5-3.8, and the *.dll files (required by lib.cp38-win_amd64.pyd) are copied to the .whl file.
See working example at https://ci.appveyor.com/project/mwtoews/pygeos
It's currently draft as I'm uncertain that this repo is the best place to put this code. Is https://github.com/pygeos/pygeos-wheels a better home? (I'll admit I'm not 100% certain what's going on with multibuild)

This is great, thanks for pushing this. I enabled appveyor on pygeos-wheels, so could you instead move the PR there?
When committing you could just put [skip travis] in your commit messages so that only appveyor is triggered.

Closing through https://github.com/pygeos/pygeos-wheels/pull/1


Test for valid mime type is too simple, fails for some

In League\Uri\Components\DataPath, mime is tested for validity with the simple regex ',^[a-z-\/+]+$,i'; which fails for valid mime types that contain a digit. e.g. video/mp4

@smuriu I've made an update to the mimetype filter validation method tell me what you think about it


Programmatic control

Hello,
I don't see anywhere in your documentation any way to control cards programmatically.
Is there any way to do it?
Thanks a lot :-)

The component exposes cards property which can be used to manipulate the cards. The examples show one way of using it.

Thanks for your answer. :-)


fix: card padding-x in mobile view

📑 Description
Fix for #357

x-padding adjustments for Card.svelte
x-padding adjustment for ListgroupItem

✅ Checks

[x] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[x] All the tests have passed
[x] My pull request is based on the latest commit (not the npm version).

ℹ Additional Information

Card with list is fixed but E-commerce card is not.
https://github.com/themesberg/flowbite-svelte/issues/357#issuecomment-1267819566


QUESTION: Loading status support for streams?

I'd like our store to be able to tell its observer when a resource is being loaded.
Use case: Multiple views on screen subscribe to the same stream or refreshable. When one of the views calls fetch() the other views subscribed to the same observable should be notified that the resource is being loaded so we can display some sort of loading indicator.
I suppose one way of doing this would be to wrap the result in a class containing the loading status and emit that instead. We could subclass the store to provide that functionality. Do you think that's achievable?
And a quick follow up: Say we implemented the above loading functionality. Same use case, but the stream / refreshable returns an error. Does the observable complete and unsubscribe all subscribers or will a subsequent call to fetch() work for all subscribers?

I've had similar idea to you of propagating state during loading. I haven't had time to this this functionality but it is something I'm interested in. I think it's reasonable for stream/refreshing to encapsulate itself in a wrapper that emits.
I would prefer not to do this feature on the current development branch as we are depreciating the current develop branch shortly in preparation of our release of store containing rx2 and a few other improvements. I'd be open to making a breaking change on the rx2 branch to have the wrapping loading state be the default. Maybe all results from store should be wrapped even for get/fetch so that we can always emit the state.

Makes perfect sense to do it across the board, agreed.
Thanks for your reply. Do you have a timeline for the rx2 release?

We need to update docs and now do the. Hopefully within the month.

Happy to help out with this feature.

We haven't had a chance to look into this issue ourselves but would be open to an external contributions.  Ideally this would be done in a manner where it can be a separate module or by adding minimal bloat to those that do not want this feature

@digitalbuddha and @Rosomack please let me know if you need any additional help. Will be happy to help

@digitalbuddha @sanchay-nyt Unfortunately looks like we're putting off implementing the caching layer in our project. This means that I probably won't have the time I thought I would for implementing this in the near future. Will let you know if that changes, but definitely not over the next couple of months!

Here's what I was thinking from an implementation standpoint:
We introduce a new subject you can subscribe to loadingSubject then anytime we make a network request we can propogate a key  through this loadingSubject users are then free to combine or use the loadingSubject and stream/get in any way they want.  I can see a use case of a loading indicator being subscribed to loadingSubject to know when to show a progress indicator.  Since this is not a feature we need internally I'd be happy to hear external comments about the pattern.

We encountered a similar issue with our caching layer and I actually came to this repo to see how you solved it. Too bad to see you haven't yet :)
In our app, each UI component is responsible for retrieving its own data. Sometimes this leads to a situation where the same data is retrieved at the same time by two different UI components. When you can't figure out if the data is already being requested from the server at that moment, the data call will be done two times.
Another situation where this occurs is when we retrieve a batch of items. At the same time the batch is retrieved, cards with loading state are already shown on screen and each card retrieves the corresponding item.
At the moment we're working with a simple in-memory key-value cache, that is updated when data is retrieved from the server. We're thinking about rewriting this to map keys to BehaviorRelays. Then, when retrieving a value from memory, you'll either directly get the value or the listener that will give you the value after a while.
We're not sure how using BehaviorRelays will impact performance though, or if there is an easier way out. Also not sure if this helps you in any way, since I'm not really familiar with the implementation details of Store.
Can you comment on how the loadingSubject would work in the two situations I mentioned?


Git's annotations are not readable

Steps to reproduce:

Open file with huge commits history
Right mouse click on gutter -> Annotate (or Ctrl+Shift+A -> VCS: Git Annotate)
Behold!

Closed as duplicate of #31

Thanks for submitting this issue, I will prioritize this higher, so it gets done sooner!


Fix Indent/Unindent without a selection not causing a redraw

Closes #71794
The caret had to blink in order to redraw. And yes, Indent also has the problem (but people rarely use this functionality)

Thanks!

Thanks!

Oh, huh, so I wasn't imagining it.


Fix using SCRIPT_NAME when not mounted on root

See middleman/middleman#1394. This fixes Middleman assets when not mounted on root. Requires config[:http_prefix] to be set.

Nice! Thank you.


Paste keyboard shortcut doesn't work in search bar.

I frequently copy and paste coordinates into the search bar, but the keyboard shortcuts don't work (Command+V), so I need to right-click and select paste. not a show-stopper but makes my workflow very frustrating.

Noted.  The same issue was present when entering latitude and longitude values.  I hope to resolve this issue with the next release.  I'll keep this issue open until I know I have a working fix.

Fixed in version 5.2


Fix Log Analytics data export CLIs

Resource Provider
operationalinsights
Description of Feature or Work Requested
Log Analytics data export CLI includes '--all' and '--export-all-tables' which were removed in swaggers.

Removed these in CLI.
The example in CLI doesn't include Tables as required parameter. Tables should be added to required parameters:
az monitor log-analytics workspace data-export create --tables --destination
--name
--resource-group
--workspace-name
[--all {false, true}]
[--enable {false, true}]
[--subscription]

Minimum API Version Required
2020-08-01
Swagger Link
https://github.com/Azure/azure-rest-api-specs/tree/master/specification/operationalinsights/resource-manager/Microsoft.OperationalInsights/stable/2020-08-01
Target Date
We get support cases for it, please do at the first update iteration you can.

add to S179

Could you add the date, since I'm not familiar with sprint count?

https://github.com/Azure/azure-cli/milestones


Logback configuration error detected with logback 1.1.7

An unexpected error happened while adding "additionalField" into logback.xml file

It seems that it is a bug in logback 1.1.7, it doesn't produce those errors when I downgrade to logback 1.1.6. If there is no "additionalField" in the logback.xml file, the version 1.1.7 works as well.

The error
ERROR in ch.qos.logback.core.joran.action.NestedBasicPropertyIA - Unexpected aggregationType AS_BASIC_PROPERTY_COLLECTION

was introduced in logback 1.1.7, and appears to be the same as LOGBACK-1158, which has been fixed for logback 1.1.8 (not released yet).
Until this error is fixed in logback, I can only recommend using logback 1.1.6.

I had the same issue, and the downgrade to logback 1.1.6 worked.

@Kaiyuanliu @mrsarm Logback 1.1.7 is released.

Upgraded to logback 1.1.8. Released logback-gelf 1.1.10.

Tested with logback 1.1.8 and logback-gelf 1.1.10: works OK.


Enable lcov 1.12 and 1.13 for gRPC PHP

Enable lcov 1.12 and 1.13 in favor of create a Docker image for issue #17198

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,020,494      Total (=)      2,020,494

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,175,622      Total (>)     11,175,620

 No significant differences in binary sizes


Feature Request - Include Field

I apologize if this is my lack of finding the feature in the examples or code but I believe it's not currently supported to have the inversion of -h which is to include only certain fields.
This would be very valuable for me so I can tail specific fields coming from some json logs.
I see the headline for Hiding or Revealing selected fields
https://github.com/pamburus/hl?tab=readme-ov-file#hiding-or-revealing-selected-fields
But the example doesn't include a flag that could be utilized to select fields to be display.
Edit: Also I'd love to try and help contribute to solve this use-case if it's an easy implementation. I'll spend some time later trying to look into it myself.

Sometimes it takes making  the issue to see the right documentation smh.
Maybe a different way of highlighting  this feature because it got a bit lost in the sauce for me despite its importance.
See https://github.com/pamburus/hl?tab=readme-ov-file#hiding-or-revealing-selected-fields again.
Command

hl example.log --hide '*' --hide '!provider'
Hides all fields except provider.


Update language to refer to u8s instead of bytes

As this discussion demonstrates, there is a lot of subtlety around what constitutes a "byte" in Rust's abstract machine. By contrast, it is sufficient to define the bit validity of most types in reference to u8s without actually specifying much about the bit validity of u8 itself. Since most of our conversions operate in terms of existing u8 types (usually [u8]), this isn't a problem for us. We should replace most uses of "byte sequence" with a similar phrase involving u8s.

For the curious, we now have a definition of "byte" in the UCG glossary. This is not normative though, it is a WIP definition.


⚠ Bofrost.be has degraded performance

In dc22314, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1736 ms

Resolved: Bofrost.be performance has improved in 9dc7469.


New alert route in alertmanager money to prisoners

What:
This relates to ticket:
https://waffle.io/ministryofjustice/cloud-platform/cards/5c7e4abffa9ad9029d060a9f

@pwyborn It seems there are merge conflicts. Could you fix those, and then resubmit for review please?


Add Mac to FFmpeg build CI

Adds a Mac build of the FFmpeg non-GPL libraries. The code is lifted almost verbatim from TorchAudio's setup, which reuses pytorch/test-infra. Note there are subtle differences between our current Linux job spec and this new one for Mac - those differences are necessary to work with pytorch/test-infra's setup.
Since this action will only execute once a week on Sunday, I tested it by temporarily hacking it to run on a pull request. See the result of one of those runs to see successful execution: https://github.com/pytorch/torchcodec/actions/runs/10730119629

As I look forward to how to how we'll want to pull these artifacts to use in builds, I think it will actually be easier if we build Linux and Mac ffmpeg non-GPL binaries using the same infra, and upload them together in the same tar file. I'm going to change this PR to reflect that. I'll request a re-review.
@NicolasHug, please let me know if you think we should prioritize alignment with PyTorch's support, or keep the repo in a state we can all locally test.

how we'll want to pull these artifacts to use in builds

We won't be pulling those artifacts into other builds. We'll manually download those artifacts to S3, and other builds will pull from S3.

it will actually be easier if we build Linux and Mac ffmpeg non-GPL binaries using the same infra

I was going to suggest that we add a "TODO: we should migrate the linux job to pytorch infra as well". This doesn't need to happen now, but if you think it makes more sense, that's perfectly fine too!

I moved Linux over to PyTorch infra as well. All binaries now get uploaded into a single tar file. Example: https://github.com/pytorch/torchcodec/actions/runs/10744678413

The failing test is unrelated to these changes, see Issue #203. Merging to unblock; we can remove macos-12 after the entire Mac wheel flow works.


Running SNCOAT

Hi there,
I am attempting to run the SNCOAT script, and ran into the following problem:

Traceback (most recent call last):
File "SNCOAT_Env_v2.py", line 11, in
from pyrep import PyRep
ImportError: cannot import name 'PyRep'

I am running SNCOAT in a newly created environment with only the following packages installed (Only python default or used in your script).

Package            Version

certifi            2021.5.30
cloudpickle        2.2.1
cycler             0.11.0
dataclasses        0.8
gym                0.26.2
gym-notices        0.0.8
imageio            2.15.0
importlib-metadata 4.8.3
kiwisolver         1.3.1
matplotlib         3.3.4
numpy              1.19.5
Pillow             8.4.0
pip                21.2.2
psutil             5.9.4
pylocker           3.1.0
pyparsing          3.0.9
pyrep              3.2.0
python-dateutil    2.8.2
setuptools         58.0.4
six                1.16.0
typing_extensions  4.1.1
wheel              0.37.1
zipp               3.6.0

My guess is that I have the wrong package versions, could you please help me out by letting me know what your pip list displays?
Thank you very much in advance!

Based on the error messages, it seems that your Python interpreter have not installed the PyRep library. However, the output info of pip list show the PyRep library(version: 3.2.0) is existed. I think the interpreter used for the SNCOAT.py program may be inconsistent to the interpreter used for pip list. This is often caused by the negligence of conda activate [env] when you install the PyRep Library or run the .py program.
In addition, the version of PyRep you have installed seems to be wrong. My PyRep version as shown in pip list is <IP_ADDRESS>. I suggest you re-install the PyRep library under the guidance of install instructions. (Notice, please activate the right conda environment during installation)

Hello, I am trying to reproduce the code, but I can't find the "trackers" package. Do you have a link to download it


Batch PPA - Rationalise the API endpoints

The current API endpoints for the respective ISO20022 messages are:
pain.001 - execute
pain.013 - quoteReply
pacs.008 - transfer
pacs.002 - transfer-response
Acceptance criteria:

Create v1 of the TMS API
Rationalise the names to be less Mojaloop and more ISO20022
Standardise the names to have some sort of consistent pattern (i.e. use the anticipated TxTp value as the name of the endpoint)
Remove the validation of the TxTp object from the API endpoint
Add the TxTp object (key and value) to the incoming message based on the end-point where the message is received.
Update documentation
Update swagger doc
Decommission previous end points

Please rename as follows


delete_server to return status code 202 or 204 (or await a full deletion which is more complicated)

JupyterHub REST API to delete a server can respond with 202 or 204 where 202 means that the server is being deleted, and 204 means it has been deleted successfully at this point.
https://github.com/Quansight/jhub-client/blob/16e3d981f6d56d654a005242b1d6c334ffa92d68/jhub_client/api.py#L149-L153
It would be reasonable for delete_server to return the response code to not loose this relevant information. It would also be helpful if there was a clean way to await the full deletion of the server - but that is a bit more tricky.
Me and @sgibson91 ran into an error related to this when we ran execute_code multiple times in sequence where later executions resulted in a response from the JupyterHub API server saying that the server is already running when a new server was being created by execute_code. execute_code calls delete_server and awaits it, but that can be a 202 status code.

@consideRatio thanks for the issue. This makes perfect sense and I agree it would be nice to support.
Many of the api methods currently return the json response so it makes sense that the delete server endpoint would return something as well.

It would also be helpful if there was a clean way to await the full deletion of the server - but that is a bit more tricky

I think this could be supported similar to https://github.com/Quansight/jhub-client/blob/master/jhub_client/api.py#L134-L148. And we just have a method ensure_deleted_server with a timeout.

@consideRatio or @sgibson91 would you mind reviewing #15 if this is the functionality that you are looking for?


Small clipping on previews

I'm submitting a...

[X] Bug report

Current behavior

There's a small clipping appearing within the preview pictures when clicking on the second preview, or, if we reached the last picture, when clicking on the preview before-the-last.
Fast snapshots of this behavior show this when we click on the second preview:

(sorry, the snapshots have been taken on the PR with the description on top of the previews; behavior is the same on the branch with no description on top of the previews)
The click triggers the load of following resources:

I haven't dived yet into the code, but if time allows, I'll check it out.
In the meantime, any hint about why the first preview would disappear for a very short time?

No idea. It's weird because it should be cached by the browser when loaded the first time.
When you open the gallery without clicking anything, all visible images should be downloaded and cached by the browser.
I'll investigate a bit to understand if the browser is downloading the same image multiple times without caching or is something different.
I'm open to other approaches to debug this.

I got it ! = )
I'll do a PR, but tell me: each commit I push goes on my previous PR... do you know how to proceed to do otherwise and assign such commit to such PR?

If your fix doesn't change anything about look and feel of previews, so it could be considered as backward compatible, I think you could add it to the same PR. Otherwise, for breaking changes we need a different PR and the fix will be part of versione 10.0.0.
How did you fix this?

I had a solution, but the system is much more complex so I'll have to work on it further.
I write here my current analysis for your information, but I'll dig through it.
The problem
The previews are systematically shifted back or forth, in previous() and next(). The thing is that, when coming from the 1st preview to the second by clicking on it, the previews /shouldn't change/, due to their disposition. Same when coming from the last to the before-the-last.
So they are shifted for a few frames, but then, due to an update of the 'images' input, the previews are recalculated correctly, hence the good 'final' result we obtain, yet resulting in a short flickering.
A non-solution
I had this fix in mind (here: for next()):
...
if (this.end === this.images.length) {
  return;
}

const currentIndex = this.currentImage ? getIndex(this.currentImage, this.images) : undefined;
if(currentIndex === 1) {
  // We're coming from index 0, the first image:
  // the previews don't change then, only the active preview changes.
  return;
}

this.start++;
...

This fix works when clicking on the previews themselves, but clicking on the preview arrows makes it another problem. The fact that both clicking the preview (and updating currentImage) and clicking the preview arrow (not updating currentImage) go through next() with no distinction could be a problem.
Many more questions
Additionnally, there are many little things that I can't get straight and should be investigated:

why do the 'images' input change occur? it's currently making things right for this issue, but we are entering block 178-181 of previews.component.ts where we shouldn't, as the situation does not fit the cases described in the comments and 'images' values (previous, next) are the same.
how come my suggested fix works when we only render one preview?
often, the number of previews will oscillate depending on the active image, between n-1 and n+1 (only n=1 and n=3 seem stable)
how come in previews, end - start = (previewsNumber + 1)?
there's an existing little quirk: when opening the modal and navigating to the last preview by clicking on the right preview arrow, it's impossible to then click on the left preview arrow: isPreventSliding() prevents it.


climacell v4 api

merged working climacell v4 api.  need to run over the next few days to debug.

It seems to run clean.  Closing


Automatically close stale issues and PRs

GitHub action to mark issues and PRs as stale after 90 days on inactivity unless they are labelled accepted.
Fixes #119.

I also think we should have a internal discussion on how to manage our issues before merging this.

I assume you mean that a PR discussion is insufficient. What sort of forum would you prefer?

I think most of our issues shouldn't be deleted after 90 days since I still think they are relevant ...

The PRs and issues are not deleted tho? They are simply closed. Given that you should always search existing issues before creating a new one, I'm not sure I see how closing them is a big thing?


HTTPie always uses full timeout period before printing results

Hi all!
First off, keep up the good work with HTTPie. It's an amazing tool!
Unfortunately, I just installed HTTPie on a new machine and it's showing some behavior I'm not used to. When doing requests to the API we're developing it always takes the full 30 second timeout before responding in the CLI.
At first I thought something in our API was causing the slow down as we're in the middle of development. This turned out not to be the case however as it's fast when using cURL. When looking in the app logs of our API it seems that the actual request isn't sent until the timeout expires.
This is the request we're doing (obfuscated the URL for our client's sake).
$ http --debug --timeout=5 PUT https://rest-api-acc.example.com/v1/just/some/resource interval=900
HTTPie 0.9.9
Requests 2.12.3
Pygments 2.1.3
Python 3.6.3 (default, Oct  4 2017, 06:09:15)
[GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.37)]
/usr/local/Cellar/httpie/0.9.9/libexec/bin/python3.6
Darwin 16.7.0

<Environment {
    "colors": 256,
    "config": {
        "__meta__": {
            "about": "HTTPie configuration file",
            "help": "https://httpie.org/docs#config",
            "httpie": "0.9.9"
        },
        "default_options": "[]"
    },
    "config_dir": "/Users/dennislaumen/.httpie",
    "is_windows": false,
    "stderr": "<_io.TextIOWrapper name='<stderr>' mode='w' encoding='UTF-8'>",
    "stderr_isatty": true,
    "stdin": "<_io.TextIOWrapper name='<stdin>' mode='r' encoding='UTF-8'>",
    "stdin_encoding": "UTF-8",
    "stdin_isatty": true,
    "stdout": "<_io.TextIOWrapper name='<stdout>' mode='w' encoding='UTF-8'>",
    "stdout_encoding": "UTF-8",
    "stdout_isatty": true
}>

>>> requests.request(**{
    "allow_redirects": false,
    "auth": "None",
    "cert": "None",
    "data": "{\"interval\": \"900\"}",
    "files": {},
    "headers": {
        "Accept": "application/json, */*",
        "Content-Type": "application/json",
        "User-Agent": "HTTPie/0.9.9"
    },
    "method": "put",
    "params": {},
    "proxies": {},
    "stream": true,
    "timeout": "5.0",
    "url": "https://rest-api-acc.example.com/v1/just/some/resource",
    "verify": true
})

HTTP/1.1 204 No Content
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Content-Type: application/json
Date: Tue, 14 Nov 2017 17:05:09 GMT
Expires: 0
Pragma: no-cache
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block

When sending this request with the --debug added the initial debug output is displayed immediately. The response takes the whole timeout.
Any help would be appreciated.
Some details:

Running on macOS.
Installed with Homebrew.
Debug output:

$ http --debug
HTTPie 0.9.9
Requests 2.12.3
Pygments 2.1.3
Python 3.6.3 (default, Oct  4 2017, 06:09:15)
[GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.37)]
/usr/local/Cellar/httpie/0.9.9/libexec/bin/python3.6
Darwin 16.7.0

<Environment {
    "colors": 256,
    "config": {
        "__meta__": {
            "about": "HTTPie configuration file",
            "help": "https://httpie.org/docs#config",
            "httpie": "0.9.9"
        },
        "default_options": "[]"
    },
    "config_dir": "/Users/dennislaumen/.httpie",
    "is_windows": false,
    "stderr": "<_io.TextIOWrapper name='<stderr>' mode='w' encoding='UTF-8'>",
    "stderr_isatty": true,
    "stdin": "<_io.TextIOWrapper name='<stdin>' mode='r' encoding='UTF-8'>",
    "stdin_encoding": "UTF-8",
    "stdin_isatty": true,
    "stdout": "<_io.TextIOWrapper name='<stdout>' mode='w' encoding='UTF-8'>",
    "stdout_encoding": "UTF-8",
    "stdout_isatty": true
}>

I found out what the problem was. I'll leave it up to you to close this issue as my problem is solved but something might be able to be improved in HTTPie around this.
So the issue was that the domain I was connecting to had AAAA (IPv6) DNS records but the firewall wasn't allowing traffic on port 443 for the IPv6 address. cURL and other tools work around this by falling back to IPv4 in case of problems. HTTPie also seems to do this, but only after the timeout has expired.
I'd think that the cURL behavior is bit more user friendly, especially as most HTTPie users probably don't care whether they're using IPv4 and IPv6. This sounds simple enough, but that is probably easier said than done 😉.

@dennislaumen thanks!!! for this hint about ipv6! I had exactly the same issue.


cmd/compile: no write barrier for stores to reflect.{Slice,String}Header

Package unsafe's godocs explicitly state this is safe:
hdr.Data = uintptr(unsafe.Pointer(p))              // case 6 (this case)

But compiling this code does not produce any write barriers:
package p

import (
	"reflect"
	"unsafe"
)

func F(hdr *reflect.SliceHeader, p *byte) {
	hdr.Data = uintptr(unsafe.Pointer(p))
}

func G(hdr *reflect.StringHeader, p *byte) {
	hdr.Data = uintptr(unsafe.Pointer(p))
}

We should probably change needwritebarrier(l) to return true when l is an ODOTPTR for accessing reflect.{Slice,String}Header.Data.
This should probably be backported to 1.8 too?
/cc @aclements @rsc

Actually, I think the fix is slightly more involved than that. This program is valid:
package main

import "reflect"

func main() {
    var hdr reflect.SliceHeader
    p := &hdr
    p.Data = 42
}

but writebarrierptr will complain about 42 being in the range (0, minPhysPageSize).
Perhaps add a writebarrieruintptr variant for assigning to runtime.{Slice,String}Header.Data that just omits that check?

I'm not sure we guarantee that SliceHeader actually works any more.  Its documentation wording is quite strong:

It cannot be used safely or portably and its representation may change in a later release.

I'm not sure you can ever reliably detect writes to it.
var hdr reflect.SliceHeader
p = &hdr.Data
some_crazy_function_that_ends_up_writing_to_its_arg(p)

The unsafe package docs provide specific guarantees for reflect.SliceHeader and reflect.StringHeader that must continue to work.  I think @mdempsky is right that this will require special handling in the compiler.

That said, I think we can modify the unsafe package docs to reject the case you mention: I think we can forbid modifying the Data field in any way other than x.Data = uintptr(p) where p is some pointer type (meaning that if p is not unsafe.Pointer it must be converted to unsafe.Pointer to support the conversion to uintptr).

@ianlancetaylor I'm okay with forbidding assigning to x.Data through a pointer (that's how I currently interpret the docs already), but I don't think we should restrict the RHS. E.g., I think x.Data = uintptr(p) + 1 should be valid.

The doc of unsafe package also says (at the end)

A program should not declare or allocate variables of these struct types.
// INVALID: a directly-declared header will not hold Data as a reference.
var hdr reflect.StringHeader
hdr.Data = uintptr(unsafe.Pointer(p))
hdr.Len = n
s := *(*string)(unsafe.Pointer(&hdr)) // p possibly already lost

So I don't think it needs write barrier, which is to hold Data as reference.

@cherrymui The distinction there is memory is being allocated for a variable of type reflect.StringHeader, so Data's memory slot doesn't get marked as containing a pointer.
In the valid example, memory is allocated for a variable of type string, and only modified indirectly through a *reflect.StringHeader pointer.

@mdempsky Oh, I see the difference. But I still think that hdr.Data = uintptr(unsafe.Pointer(p)) doesn't mean to hold a reference to p.

I think the problem here is the hybrid write barrier - the old value of hdr.Data might need saving, even if you agree that p is not referred to.
@aclements

We discussed this internally:

Assignments of the precise form p.Data = u where p has type *reflect.SliceHeader or *reflect.StringHeader require a write barrier. We do not need to support q := &p.Data; *q = u.
The package unsafe docs already warn "A program should not declare or allocate variables of these struct types." so the p.Data = 42 example I posted above is invalid anyway.

1.8.1 material? Has the write barrier always been missing, or is this new to 1.8?

I could be wrong, but I think that is what is new to 1.8 is that missing the write barrier could conceivably actually matter in practice.  Before the hybrid write barrier, which is new in 1.8, it's pretty hard to imagine a real program that would fail.  With the hybrid write barrier, it's much easier to imagine that omitting the write barrier could leave a dangling reference on the stack.

For go 1.9, can we define in package unsafe:
type StringHeader struct {
    Data Pointer
    Len int
}

and encourage people to use that instead of the one in reflect.  Then in Go 2 we can drop the reflect ones.  Or even Go 1.10?

@randall77 I just filed #19367.

Re-opening for cherry-pick to 1.8.1

Cherry-picked to release.