Identify and fix the most important missing BA/Util geometries

Many of the historical geometries that are generated using the EIA 861 + US Census data are very consistent with HIFLD in 2017-2018. Many of them are also self-consistent across the years for which we have data (2001-2018). However, there are some big holes that we need to fill in order to have workable territories for the major FERC 714 planning areas at least back to 2010.
Alter Geometries:
MISO (2009-2010)

MISO territory for 2010 is unreasonably small, and non-existent for 2009 and earlier years.
However, MISO reports demand for 2009-2010 in FERC 714.
However, based on this workshop report it looks like there's essentially no difference between the 2011+ years and 2009-2010.
Backfill 2009-2010 with the 2011 geometry.

Southwest Power Pool (2006-2013)

SWPP has demand for all years but is missing geometry for 2006-2013
SPS has demand and geometry for 2006-2013, but nothing later.
SPS and SWPP merged in 2014.
SWPP geometry grows a lot between 2014 & 2015, population and demand grows modestly.
They expanded into SD, ND, MT.
Seems legit, and unrelated to the SPS merger, which appears to have been handled.
Need to backfill 2006-2013 geometries for SWPP... is the pre-expansion 2014 geometry likely to work?
Demand is consistent as far back as 2010. 2009 is 10% lower, 2006-2008 another 15% lower.
Incorporated Nebraska utilities in 2009 (April 1st, hence the middling demand)
Backfill 2010-2013 with the 2014 geometry.
Backfill 2006-2009 with 2014 map minus Nebraska.

Louisville Gas & Electric and Kentucky Utilities (2006-2012)

Reports demand for all years, but lacks geometries in the early ones.
Demand reported is consistent across all years.
Population and service territory area in 2013 are almost 2x bigger than later years.
Backfill 2006-2013 with the 2014 geometry.

American Electric Power Company (2011-2013)

Identified as a BA
Has geometries through 2010, but not thereafter.
Appears in the BA assn table only as a BA.
Makes sense that it's only getting a geometry by virtue of its constituent utilities.
Demand reported 2006-2013 is pretty constant.
Big increase in territory (3x) and smaller increase in population (1.5x) between 2008 & 2009.
Early geometries are in the midwest.
Appears that AEP really did expand into those areas.
However, the FERC-714 demand doesn't change when those areas are integrated, so it seems like the demand being reported probably just pertains to the original service territory in the midwest & appalachia.
Limit service territory to counties in OH, IN, VA, WV, TN, KY, MI

Entergy Corporation/Services (2013)

Reports demand consistent with past years in 2013
However, geometry isn't present.
Forward fill 2013 with geometry from 2012

Treat as Utilities not Balancing Authorities:
PG&E (2006-2010)

PG&E shows up as a BA in the EIA-861 only in 2002.
It shows up in all years as a utility, with service territory, etc.
As a utility, it shows up within CISO.
Because it's showing up as a BA that one time, we're assuming it's a BA. But it never gets any territory associated with it outside of 2002, or as a utility.
This seems like a reporting irregularity.
Force PG&E to be treated as a utility by replacing it in 2002 with CISO in the BA table during ETL.
This should mean it gets categorized correctly across all years and gets a territory assigned automatically.

San Diego Gas & Electric Company (2011-2019)

Has a geometry in earlier years (2006-2010), but it's missing from 2011 forward.
Reports consistent demand across all years in FERC-714
EIA-861 service territory table shows it having the same counties for all years 2001-2019 (San Diego & Orange)
Why isn't it getting a service territory for the later years?
It's being identified as a BA because it shows up in the BA table from 2001-2010, but after that it's gone.
It also shows up in all the years of EIA 860 as a utility.
Force it to be treated as a utility

Dayton Power & Light (2011-2019)

Shows up as a BA in EIA-861 in 2001-2010
Also shows up as a utility in EIA-861 in 2005-2019
Has the same territory listed by its utility ID in all 19 years of service territory data.
Force it to be treated as a utility

Consumers Energy Company

Like PG&E it appears as a BA a few times (2003-2006) but really it appears to act like a utility.
Has service territory (counties) in all years, and shows up in other utility tables as a utility.
However, because it shows up at least once as a BA, we use the BA territory generation process, which doesn't work if you're really a utility. So it ends up getting no territory assigned (even though it's got counties)
Force Consumers Energy Company to be treated as a utility, not a BA

Unfixable Service Territories
Mid-Continent Area Power Pool (2006)

No eia_code is provided for this respondent,and it's unclear what it corresponds to.
Wikipedia suggests it's the predecessor to the Midwest Reliability Organization which is a NERC region.
Respondent only appears in 2002.

FirstEnergy (2006-2008)

Ohio-based IOU with several different utility_id_eia values over the years.
OH based sales are reported in PJM for 2013 and later years via EIA-861.
Listed as a Power Marketer / Retail Power Marketer in the EIA-861.
Never shows up as a utility in the BA associations.
Never shows up in the service territory table.
Doesn't appear to be fixable.

Westar Energy / KPL (2006-2008)

Several utilities named Westar
One in EIA-861 with complete geometries has sales that don't track with the FERC-714 demand.
No obvious reconciliation to be had.

Wholesalers Without Service Territories
There are 28 respondents that appear to be some kind of wholesale organization, mostly cooperative G&Ts and public power entities without their own service territories. They account for about 34% of the reported demand that's not associated with any service territory. A few are listed below from early investigation. The others were excluded if they:

Report demand in the FERC-714.
Never appear in the EIA-861 service territory table (with counties).
Are listed in EIA-860 or EIA-861 as a utility.
Appear to have a parent BA in the EIA-861 balancing_authority_assn_eia861 table.

Oglethorpe Power Corp (2006-2019)

Electricity supply cooperative in Georgia.
Has no geometry for any year, and doesn't show up in the EIA-861. Does appear in EIA-860.
Is it maybe just a supplier with no customers or service territory of its own?
Is it's demand being included already with Southern Company (SOCO) which covers all of Georgia?
In early years of EIA-861 which explicitly link utilities to the balancing authorities they are part of, Oglethorpe is associated with SOCO, but it has no counties associated with it in the service territory tables.

Northeast Utilities Service Company (2006-2014)

No geometry for any year in which it appears in FERC-714.
aka New England Hydro-Transmission Corp.
Eventually got bought out by Eversource.
Appears in early EIA-861 years in association with NE-ISO (in the BA table)
Does not show up anywhere within the service territory table.

Central Electric Power Cooperative (2006-2019)

Reports demand in all years, but never has a geometry.

Other Issues

PJM territory gets much smaller as you go back in time. Is that right?
Is the area near Houston being excluded from ERCOT?
PACE & PACW are separate balancing areas but a single utility. Need to merge them somehow. See #616

For 2013 and later, the list of counties for each territory is being compiled based on the utilities that show up in association with a given BA in the sales_eia861 table (in earlier years, the utilities associated with a given BA were listed explicitly in the balancing_authority_eia861 table). So what does it mean that a county shows up in one of these maps? I think it means that a utility that serves that county sold electricity to end users in the BA in question. Is that a good proxy here, or not? That makes these territories the union of all the counties served by all the utilities that participated in sales within the BA.
I think there's another level of geographic specificity available here if we want it, which is the state in which the sales took place -- for 2013 and later we have the state, BA code, and utility available in the sales_eia861 table, so rather than pulling in all of the counties associated with each utility, we could just pull in the counties associated with the utility that are inside the state(s) that show up in the sales_eia861 table.
Presumably the same kind of utility - BA associations will show up in many of the other EIA 861 tables. Should things like energy efficiency, demand response, and advanced metering infrastructure also be used to infer which counties are included in a BA territory?

Yup, it turns out using only the subset of counties that are in the states which are mentioned in the sales_eia861 table records cleans up pretty much all of these big territorial weirdnesses so yay!  A few examples (only for 2013-2018, since adding the state screws up the earlier years which don't have access to state information w/o separating the processes more)
ERCO

PJM

MISO

Is this map helpful?
https://www.wecc.org/Administrative/Balancing_Authorities_JAN17.pdf
For instance, according to that link, CISO should not include Sacramento (BANC), Los Angeles (LDWP), or the Turlock irrigation district. (These are geographically small, but probably a non-negligible number of MWh.)

Bringing the image in here for reference:

I could imagine a process where we subtract the small BAs from the large ones spatially -- for example to remove BANC, TIDC, & LDWP from the potentially overzealous CISO map, but I'm not sure how generalizable this is going to be. I wish there was some way to verify within the 714 hourly demand data that those demand curves were really reported separately, rather than the small BA demand showing up in both their own time series, and the time series of the larger enclosing BAs.  Is that a ridiculous concern?
Also in the particular application that we're looking at, I think we're going to end up layering these areas together, along with their hourly demand, and then having to choose at each location which of potentially several demand series to use.  So we could say something like "use the most geographically specific demand series available" which would mean in the areas where a small BA overlaps a large one, the small demand series would take precedence which might be functionally the same thing as excising those counties from larger BA in the input map.

@ezwelty as I think you've already seen, the code that builds these geometries is in pudl.analysis.service_territory and it gets specifically applied to the case of building the weird mishmash of FERC 714 utility + balancing authority / planning area geometries in the pudl.output.ferc714 module.

@zaneselvans

American Electric Power Company (2011-2013) [...]
Limit service territory to counties in OH, IN, VA, WV, TN, KY, MI

This doesn't seem quite right. In the earliest years (2006-2008) before the major expansion in 2009, the geometry spans the following states: ['OH', 'IN', 'VA', 'WV', 'TX', 'MI', 'OK', 'AR', 'TN', 'KY']. Should I just forward-fill 2009-2013 with either 2006, 2007, or 2008?

@zaneselvans

American Electric Power Company (2011-2013) [...]
Limit service territory to counties in OH, IN, VA, WV, TN, KY, MI

This doesn't seem quite right. In the earliest years (2006-2008) before the major expansion in 2009, the geometry spans the following states: ['OH', 'IN', 'VA', 'WV', 'TX', 'MI', 'OK', 'AR', 'TN', 'KY']. Should I just forward-fill 2009-2013 with either 2006, 2007, or 2008?

Just looking at my notes above, what I recall is that there wasn't an increase in demand corresponding to the expansion into the counties in TX/AR/LA that are disconnected from the main midwestern territory, which made me suspect that actually demand from those regions was not being integrated into the FERC 714 data, and so in this case I was trying to cobble together a territory that specifically matches the apparently reported demand, rather than reflecting what was reported in the EIA 861. So this is something that would only ever make sense to do in the context of working with these territories and the FERC 714. Does that seem reasonable? Was I wrong about the constant historical demand, even when the territory and population increased?

Just looking at my notes above, what I recall is that there wasn't an increase in demand corresponding to the expansion into the counties in TX/AR/LA that are disconnected from the main midwestern territory, which made me suspect that actually demand from those regions was not being integrated into the FERC 714 data, and so in this case I was trying to cobble together a territory that specifically matches the apparently reported demand, rather than reflecting what was reported in the EIA 861. So this is something that would only ever make sense to do in the context of working with these territories and the FERC 714. Does that seem reasonable? Was I wrong about the constant historical demand, even when the territory and population increased?

@zaneselvans I follow the logic, and you are right that there is an abrupt increase in service territory in 2009 without a corresponding increase in FERC 714 demand. All I'm saying is that the earliest years do include counties in TX, OK, and AR, states that were not on your list. It seems weird to exclude these utility-states combinations, since they are present in the years before the expansion.

@zaneselvans I follow the logic, and you are right that there is an abrupt increase in service territory in 2009 without a corresponding increase in FERC 714 demand. All I'm saying is that the earliest years do include counties in TX, OK, and AR, states that were not on your list. It seems weird to exclude these utility-states combinations, since they are present in the years before the expansion.

@zaneselvans Investigating the re-assigning of entities from balancing authorities to utilities... One thing to consider is that these "faux-BAs" have utilities associated with them. For Pacific Gas & Electric, San Diego Gas & Electric, and Dayton Power & Light, it makes sense that the utilities associated with them as BAs would be reassigned to their parent BA. For example, in 2002, PG&E is listed as both a utility of CISO, and a BA with several utilities, which in that year only are not listed as utilities of CISO. So it makes sense that the utilities assigned to PG&E be reassigned to its parent, CISO.
However, this gets weird for Consumers Energy Company, which as BA (2003-2006) only includes one utility (40211 in Indiana). It is not clear which BA to reassign this nested utility, if any. The BA parent to Consumers Energy Company (12427) is never listed as containing utility 40211, but several other BAs are associated with this utility.
More generally, should I check if there are BAs with utilities that themselves (as BAs) have utilities in balancing_authority_assn_eia861. I presume this nesting would indicate a problem?

@zaneselvans Investigating the re-assigning of entities from balancing authorities to utilities... One thing to consider is that these "faux-BAs" have utilities associated with them. For Pacific Gas & Electric, San Diego Gas & Electric, and Dayton Power & Light, it makes sense that the utilities associated with them as BAs would be reassigned to their parent BA. For example, in 2002, PG&E is listed as both a utility of CISO, and a BA with several utilities, which in that year only are not listed as utilities of CISO. So it makes sense that the utilities assigned to PG&E be reassigned to its parent, CISO.
However, this gets weird for Consumers Energy Company, which as BA (2003-2006) only includes one utility (40211 in Indiana). It is not clear which BA to reassign this nested utility, if any. The BA parent to Consumers Energy Company (12427) is never listed as containing utility 40211, but several other BAs are associated with this utility.
More generally, should I check if there are BAs with utilities that themselves (as BAs) have utilities in balancing_authority_assn_eia861. I presume this nesting would indicate a problem?

@zaneselvans So after the fixes you enumerated, there are still 111 EIA identifiers that show as both a utility and a balancing authority with utilities other than themselves in the same year in balancing_authority_assn_eia861.

@zaneselvans So after the fixes you enumerated, there are still 111 EIA identifiers that show as both a utility and a balancing authority with utilities other than themselves in the same year in balancing_authority_assn_eia861.

Hmm. I had not really looked into the potential for these multi-layered nesting relationships, and what to do about them, or really gone into detail on whether these relationships all made sense purely from the point of view of the EIA 861 data. I was chasing down big missing / bad territories in the FERC 714 data. I'm not sure what the right thing to do is in here.

Hmm. I had not really looked into the potential for these multi-layered nesting relationships, and what to do about them, or really gone into detail on whether these relationships all made sense purely from the point of view of the EIA 861 data. I was chasing down big missing / bad territories in the FERC 714 data. I'm not sure what the right thing to do is in here.


Add default proguard config for sample app

Update AGP to 3.2.0
Update Kotlin to 1.2.51
Include consumer proguard file in every variant
Add default proguard config for sample app
Run Proguard on release build type for sample app
Fixes: https://github.com/airbnb/MvRx/issues/126

A few more suggestions: you named proguard-project.pro instead of proguard-rules.pro. Also, I counted -dontwarn javax.annotation.** there 3 times.

@bernaferrari This is on purpose, I want to make clear that these are project specific rules. The name of the file is not really a problem.
-dontwarn javax.annotation.** is in there multiple times as it is in the different configs I had to copy for okhttp3, moshi and retrofit2. These configs are unchanged on purpose. It is ok to have duplicative config.

Fine. I tried the new configurations on my app that crashes with MvRx. I was able to make it stop crashing with the following configuration:
# Print out the full proguard config used for every build
-printconfiguration build/outputs/fullProguardConfig.pro

# These classes are used via kotlin reflection and the keep might not be required anymore once Progurad supports
# Kotlin reflection directlty.
-keep class kotlin.reflect.jvm.internal.impl.builtins.BuiltInsLoaderImpl
-keep class kotlin.reflect.jvm.internal.impl.load.java.FieldOverridabilityCondition
-keep class kotlin.reflect.jvm.internal.impl.load.java.ErasedOverridabilityCondition
-keep class kotlin.reflect.jvm.internal.impl.load.java.JavaIncompatibilityRulesOverridabilityCondition

# If Companion objects are instantiated via Kotlin reflection and they extend/implement a class that Proguard
# would have removed or inlined we run into trouble as the inheritance is still in the Metadata annoation
# read by Kotlin reflection.
# FIXME Remove if Kotlin reflection is supported by Pro/Dexguard
-if class **$Companion extends **
-keep class <2>
-if class **$Companion implements **
-keep class <2>

# https://medium.com/@AthorNZ/kotlin-metadata-jackson-and-proguard-f64f51e5ed32
-keep class kotlin.Metadata { *; }

# Oddly need to keep that even though Evernote state is not used in the app.
-keepnames class * { @com.evernote.android.state.State *;}

I suggest adding it to the library, since everyone using mvrx+epoxy+proguard will get a crash without it (probably because of reflection), which is not fun.

I think you should at least add on wiki that mvrx crashes without some proguard rules, else this will catch a lot of people on surprise.

Well the rules are now in the demo app. But I agree, let me update the README...

If I were you I would probably split in the demo what is necessary for the
library and what is necessary for the demo (which include retrofit and
okhttp that is independent of mvrx).
On Fri, Nov 16, 2018, 22:58 rossbacher<EMAIL_ADDRESS>wrote:

Well the rules are now in the demo app. But I agree, let me update the
README...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/airbnb/MvRx/pull/138#issuecomment-439572567, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAVblaS_epCzHugoRPj29OV6K70A_5zdks5uv18ggaJpZM4Ye4JX
.

I also updated the Wiki with a Proguard/Dexguard section here: https://github.com/airbnb/MvRx/wiki#proguarddexguard

I think you should at least add on wiki that mvrx crashes without some proguard rules, else this will catch a lot of people on surprise.

Done: https://github.com/airbnb/MvRx/wiki#proguarddexguard

I also updated the Wiki with a Proguard/Dexguard section here: https://github.com/airbnb/MvRx/wiki#proguarddexguard

Done.

Great, awesome, thanks!


OVG SN: skip links without PDF and fix PDF links

For SN OVG intermediate pages, skip links where the a element does not enclose text.
Fixes https://github.com/niklaswais/gesp/issues/11

I fixed more cases where it fails by skipping by URL pattern instead, and removing text that doesn't belong to the link.

I fixed more cases where it fails by skipping by URL pattern instead, and removing text that doesn't belong to the link.

The latest commit makes the fix even more robust by scanning for the filename pattern in both link text and href attribute (see issue for motivation).

In order to avoid missing files that were previously downloaded, I also collect links to DOCX files again. Some identifiers like ExportAsPdfPipeline or save_as_pdf might like a rename now. On the other hand, it might call for adapting the architecture to better cope with cases where one scraper can output different file formats.

Tahnk you! I'm in the process of re-writing the architecture. Will add it as a new branch for testing in the upcoming weeks


XMM data extraction

We need to extract the XMM-Newton data for IRAS 13224-3809 split into the different flux staets.
@DariusMichienzi - please feel free to post any questions here!

Darius and Tom have been working on an XMM data reduction script.


fix(Version): add version .rc file

:tada: This PR is included in version 4.0.5-rc.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


Fix DBConnection.OwnershipError when multiple tests are run together

Doesn't actually fail the tests themselves but the console output is really annoying.
Seems to be quite hard to debug.
Useful links:

https://elixirforum.com/t/issue-with-dbconnection-ownership-proxy-checkout-and-genserver-process/4334
https://elixirforum.com/t/exit-no-process-the-process-is-not-alive-or-theres-no-process-currently-associated-with-the-given-name-possibly-because-its-application-isnt-started/4368/6
https://elixirforum.com/t/issues-running-tests-with-a-phoenix-1-3-app-that-uses-genserver-processes/12696
https://elixirforum.com/t/ecto-test-multiple-process-transaction-in-sandbox-with-shared-connection/4901

Apparently the problem is caused by performing some DB actions upon the channel closing (which happens when each test ends), but I'm still not sure why error messages occurred as a result.

I've found the problem but I'm still not sure of the underlying mechanisms: In this example, the supervisor triggers a callback whenever a channel is closed. Apparently, whenever every test ends, the channel associated to that test is closed, so the callback always gets triggered for every test case during testing, as this led to the errors. I perform some DB actions in the callback. I'm not sure why error messages occur as a result though.
My current workaround:
  def handle_info({:EXIT, pid, reason}, state) do
    # Whenever a test ends the following path happens
    # Whenever the following path doesn't match, a genuine exit in the production environment happened, so we can use the `else` clause for our real code.
    with :test <- Application.get_env(:app, :environment),
         :shutdown <- reason do
      {:noreply, drop_participant(state, pid)}
    else
      _ -> # Real code
    end
end


How can we keep null rows on the bottom?

If I have 10 rows and 3 are empty, they will always appear on the top for alphabetical. What I would love is if the sorting could keep empty rows on the bottom when sorted. Rather than ask for this to be added, which might be seen as unnecessary bulk, how would you recommend I extend this to add that functionality myself?

I used data-sort-value="0" as a sufficient solution. They're not always on the bottom, but at least they're not on top for my numeric sorted columns.

FYI one other option is to set separate sorting functions for ascending and descending.
Column

Then in the blanksAsc sorting function, sort the blank value after the other (so it goes 1, 2, 3, blank), and in the blanksDesc function, sort blanks before the other (so it goes 3, 2, 1, blank).


Dropdown flicker

The buttons section  in the docs has a dropdown section. Clicking on the default trigger and then dismissing it by clicking somewhere else causes the dropdown shown to flicker and then dismiss itself.

Can you reproduce and post gif/video link?

Here is a video: dropdown-flicker.mov.zip

Related to #204


How do I use lottie animation files?

I am unsure how/where to place my lottie.json file. Please advise? Specifically, I used adobe after effects and generated the lottie file using the bodymovin plugin.

Follow Docs or this
You can get demo / example project here (Not json file is messing in iOS)


Added support for AUR4

Arch now uses Git for managing PKGBUILD files.
This uses the cgit web interface to download the plain text PKGBUILD file.
It's sort of a hack, and it might be better to actually checkout the PKGBUILD git repo but this requires only a single line change.

I appreciate the pull request. Can you submit this to the main repository?
github.com/GoogleCloudPlatform/compute-archlinux-image-builder
You will need to sign an agreement before I accept the PR there. Instructions in the README.md

Also just as a caveat. The original builder used Debian to build to bootstrap the install.
I need to update to the builder to just use a stable image that already exists now which will simplify the code a lot.

The reason I submitted it to this repository is that the main repository is horribly broken. It still uses makepkg --as-root and doesn't install the sed package which makes it fail to build.
As for the contribution agreement, do I need to if I've already signed the Go language one? I also just finished an internship at Google (not sure if it makes a difference).

Or this needs to be merged in as well.
https://github.com/tekacs/compute-archlinux-image-builder/commit/4dccb8ce9c3d0c7b3b52e29988f74c8c7f9028f8

I believe the Google cloud agreement is different than the Google Inc
agreement. And you need to sign even if you used to work there.
On Sun, Aug 23, 2015, 11:34 PM Tristan Rice<EMAIL_ADDRESS>wrote:

Or this needs to be merged in as well.
tekacs@4dccb8c
https://github.com/tekacs/compute-archlinux-image-builder/commit/4dccb8ce9c3d0c7b3b52e29988f74c8c7f9028f8
—
Reply to this email directly or view it on GitHub
https://github.com/jeremyje/compute-archlinux-image-builder/pull/1#issuecomment-134006508
.

Looks like it's the same since when I try and sign the agreement it says "It looks like you've already signed this CLA. If you'd like to edit your contact information, you may do so below.".

I'll verify when I get back to the office next week and review to accept
the PR.
Just curious do you know how I can rebase this repository since it's remote
I have a few commits that I want to remove before submitting upstream.
I can rebase interactive locally but pushing fails.
On Mon, Aug 24, 2015, 3:59 PM Tristan Rice<EMAIL_ADDRESS>wrote:

Looks like it's the same since when I try and sign the agreement it says
"It looks like you've already signed this CLA. If you'd like to edit your
contact information, you may do so below.".
—
Reply to this email directly or view it on GitHub
https://github.com/jeremyje/compute-archlinux-image-builder/pull/1#issuecomment-134359078
.

Not sure off the top of my head.

This PR is now obsolete. The project was pretty broken and I got around to fixing all the blocking issues. It's not perfect but the main repository will be updated tomorrow.


Disable DuckDB progress bars

Description
This PR disables DuckDB progress bars from appearing. I noticed these periodically could show up within Jupyter notebooks, which I believe was a result of DuckDB being run in "interactive mode" (which changes default behaviors).
Closes #226
What is the nature of your change?

[ ] Bug fix (fixes an issue).
[x] Enhancement (adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
[ ] This change requires a documentation update.

Checklist
Please ensure that all boxes are checked before indicating that a pull request is ready for review.

[x] I have read the CONTRIBUTING.md guidelines.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] New and existing unit tests pass locally with my changes.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] I have deleted all non-relevant text in this pull request template.

Thanks @gwaybio and @falquaddoomi ! Merging this in.


add dsp reports

URLs for dsp reports are:
https://advertising-api.amazon.com/dsp/reports
https://advertising-api.amazon.com/dsp/reports/{reportId}

obsolete


Cluster commands like FlushAll and Keys only contact one node.

cli := redis.NewClusterClient(&redis.ClusterOptions{
	Addrs: []string{"localhost:55400", "localhost:55401", "localhost:55402"},
})
// add data to a variety of keys
// ...
// now try flushing
cli.FlushAll().Result()
// only some keys will have been deleted because hashSlot just picks a random slot

I have a bit of code that fixes this (for FLUSHALL at least), but I wanted to make sure I'm not missing the right way to do this before I invest any more time in that.

Yes, I was wondering if it makes more sense to remove these from
ClusterClient in the next release and expose them on the single Client only.
On 8 Jan 2016 7:06 pm, "Matthew Jaffee"<EMAIL_ADDRESS>wrote:

cli := redis.NewClusterClient(&redis.ClusterOptions{
Addrs: []string{"localhost:55400", "localhost:55401", "localhost:55402"},
})
// add data to a variety of keys
// ...
// now try flushing
cli.FlushAll().Result()
// only some keys will have been deleted because hashSlot just picks a random slot
I have a bit of code that fixes this (for FLUSHALL at least), but I wanted
to make sure I'm not missing the right way to do this before I invest any
more time in that.
—
Reply to this email directly or view it on GitHub
https://github.com/go-redis/redis/issues/240.

Well, they're definitely useful commands to have IMO. Maybe a separate process method on ClusterClient for commands that need to talk to every node in the cluster? It looks like there are other clients (https://github.com/Grokzen/redis-py-cluster at least) that do this.
I'd be happy to take a stab at it if y'all are interested in having this functionality.

I think you are getting into really dangerous territory, far beyond what a
client library should be capable of.
What guarantees would a FlushAll provide? What if one node is unresponsive
or fails, how would you deal with such a scenario? What if a node has just
been added to the cluster and is unknown to the client?
Instead, I would rather implement something like an iterator that allows
you to run through individual client connections and execute custom
commands, handle individual errors, etc
On 8 Jan 2016 9:24 pm, "Matthew Jaffee"<EMAIL_ADDRESS>wrote:

Well, they're definitely useful commands to have IMO. Maybe a separate
process method on ClusterClient for commands that need to talk to every
node in the cluster? It looks like there are other clients (
https://github.com/Grokzen/redis-py-cluster at least) that do this.
I'd be happy to take a stab at it if y'all are interested in having this
functionality.
—
Reply to this email directly or view it on GitHub
https://github.com/go-redis/redis/issues/240#issuecomment-170128340.

I would rather implement something like an iterator

This sounds right, but I afraid that in practise you just pass the problem to users :) I.e. I doubt that users can better answer questions you raised. Or that those questions can have more than one right answer...

I'd be happy to take a stab at it if y'all are interested in having this functionality.

I am interested to take a look at such pull request - thanks in advance.

The iterator would solve the problem of what to return in the case that some nodes but not all encountered an error, but perhaps that could also be aggregated into a more sophisticated error from a single call.
The problem of ensuring that all nodes have been contacted/all slots have been covered is a bit trickier in the event that slots are being moved around - I think this problem remains in either case.
I'll see what I can come up with.

I'm interested in such feature. For the moment I'll do the cluster "keys" command manually (iterating over nodes)

Everyone who is interested in this please take a look at https://github.com/go-redis/redis/pull/331


fix for user story unmarshalling

fixes unmarshalling problems of user stories if:

origin_issue is set
origin_task is set

How did I miss this? Thanks for the fix!


ViewPropTypes will be removed from React Native, along with all other PropTypes. We recommend that you migrate away from PropTypes and switch to a type system like TypeScript. If you need to continue using ViewPropTypes, migrate to the 'deprecated-react-native-prop-types' package.

while do not  resolution this problem?
ViewPropTypes will be removed from React Native, along with all other PropTypes. We recommend that you migrate away from PropTypes and switch to a type system like TypeScript. If you need to continue using ViewPropTypes, migrate to the 'deprecated-react-native-prop-types' package.
platrom:
react-native:0.73

To resolve the deprecation warning for ViewPropTypes in React Native 0.73, you have two main options: migrating to TypeScript or using the deprecated-react-native-prop-types package. Here are the steps for both approaches:
Using deprecated-react-native-prop-types Package

Install the package:npm install deprecated-react-native-prop-types

Update your imports:
Replace any import of ViewPropTypes from react-native with deprecated-react-native-prop-types.import { ViewPropTypes } from 'deprecated-react-native-prop-types';

Migrating to TypeScript
If you decide to migrate to TypeScript, you can define the types directly without relying on ViewPropTypes.

Install TypeScript and necessary types:npm install typescript @types/react @types/react-native

Create a tsconfig.json file:{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "strict": true,
    "jsx": "react",
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true
  }
}

Update your component to use TypeScript types:
Replace ViewPropTypes with ViewStyle from react-native.import { StyleProp, ViewStyle } from 'react-native';

interface MyComponentProps {
  style?: StyleProp<ViewStyle>;
}

const MyComponent: React.FC<MyComponentProps> = ({ style }) => {
  return <View style={style} />;
};

By following either of these methods, you can resolve the deprecation warning for ViewPropTypes in React Native 0.73.
Details
Sources

src/types.ts
src/components/ScrollViewGesture.tsx
src/components/rnr-demo.test.tsx
example/app/tsconfig.json
example/expo/tsconfig.json
example/app/src/pages/complex/index.tsx
tsconfig.json

About Dosu This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.
Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.
To continue the conversation, mention @dosu.

is not work for me .  why  react-native-reanimated-carousel  do not instead ViewPropTypes  with new method?

not work

not work.

This is all fixed in version 4.0.0 -alphax


🍒 Cherry pick PR #6319 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/6319 to staging 🍒

This pull request has merge conflicts and can not be automatically merged. :disappointed:
Please manually resolve the conflicts, push your changes, and then request another reviewer to review and merge.
Important: There may be conflicts that GitHub is not able to detect, so please carefully review this pull request before approving.

@luacmartins @chiragsalian Will you please review this?

I had to resolve conflicts, so take a look at the commit I added and make sure it looks good!

🚀 Cherry-picked to staging by @roryabraham in version: 1.1.16-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by @roryabraham in version: 1.1.16-10 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Add a section about the Checker Framework to CONTRIBUTING.md (fixes #918).

Coverage remained the same at 81.377% when pulling 7860be92ed2d56667287f1bf3be47e10289e7443 on sebright:document-checker-framework into 1049f48ff933720506a70099bea8f9df23e2d993 on census-instrumentation:master.

Codecov Report

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

@@            Coverage Diff            @@
##             master     #922   +/-   ##
=========================================
  Coverage     79.16%   79.16%
  Complexity      974      974
=========================================
  Files           163      163
  Lines          4430     4430
  Branches        412      412
=========================================
  Hits           3507     3507
  Misses          827      827
  Partials         96       96

Continue to review full report at Codecov.

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

Thanks!


pen tool not working

I'm so happy to be able to run this program locally while I wait for your site to come back up!
I notice one issue that the pen tool is not working currently (tried Firefox and Chrome).  But perhaps you are aware of the issue already.
Thank you!

I figured out how to get the pen tool to work.  Sorry to bother you.  thank you


Update cats-effect, cats-effect-testkit to 3.4.9 in main

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-testkit

from 3.4.8 to 3.4.9.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.typelevel" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, version-scheme:early-semver, commit-count:1

Superseded by #20.


Tick format doesn't work

The directive: '<'chart-axis-x-tick tick-format="%Y-%m-%d %H" '/>', basically I want the time in following format other than default: '2015-06-10 04', but it doesn't work. I checked the source code and found it doesn't set 'config.data.xFormat', but only set 'config.axis.x.tick' (line 56), if I add the xFormat setting, it works well. Is it a bug or there is something I need to set?

Please verify using the example in the project. There is an example with this code:
<c3chart bindto-id="chart-timeseries" chart-data="datapoints" chart-columns="datacolumns" chart-x="datax">
    <chart-axis>
        <chart-axis-x axis-id="x" axis-type="timeseries">
            <chart-axis-x-tick tick-format="%Y-%m-%d"/>
        </chart-axis-x>
    </chart-axis>
</c3chart>

When I change the tick-format to what you want it works for me. Are you using the latest version of the library? (0.5.2)

The setting xFormat is format for input data parsing, but axis.x.tick.format is for displaying already parsed data. So, without setting xFormat it is not possible to parse date in custom format. Any possibilities to add that ?

Not sure I completely understand what you mean, can you give me a sample that actually does not work? Using the mentioned example works for me, what am I missing.

Let's assume he adds new datapoint with x value in format "2015-06-10 04". With x axis type timeseries and the default xFormat setting (which is, if not mistaken, "%Y-%m-%d") there will be a date parsing error. To fix this, xFormat needs to be set to "%Y-%m-%d %H", so the input data gets correctly parsed in a Date object. After that the date can be displayed on axis tick with specified format, which then can be the same or different, say, "%m-%d-%y".

Aha, now I get it, I'll reopen the issue.

Here https://github.com/jettro/c3-angular-directive/blob/master/src/axis-x-tick-directive.js#L151
is another issue: when type of x axis is timeseries, d3.time.format(...) should be used instead, but it seems, that with current design, it could be a little complicated to detect axis-type value from char-axis-x directive. One solution would be to move d3.format(...) and d3.time.format(...) to chart controller. This applies to y axis too, but more rarely.

There seems to be an inconsistency with x and y format attribute names:
https://github.com/jettro/c3-angular-directive/blob/master/src/axis-y-tick-directive.js#L70
versus
https://github.com/jettro/c3-angular-directive/blob/master/src/axis-x-tick-directive.js#L149
The second one judging by documentation at the top of the same file, is a bug, it should be tickFormat as for y axis.

I have serious problems in getting any formatting right for the x-axis timeseries.
Even the official example is not working for me on my machine. As you can see in the image that I am enclosing, the format says .140, .141 rather than use Y-m-d.
This specific timeseries example is very much publicized, but it is not present in the live demo pages on the c3-angular site. Can you please point me to a live working example page? I'd be most obliged, as I could then be able to check exactly which versions of the various libraries are needed to get all this straight.

It's the same for me (i get negative, 3 digit numbers) . I ended up using an extra function for formatting:
var time_format = function (timestamp) {
    return d3.time.format("%X")(new Date(timestamp));
};

<chart-axis-x-tick tick-rotate="50" tick-format-function="time_format" />

Which is of course only an intermediate solution…

Great workaround, @tamasgal. Thank you!
In the meantime I have found out that attribute tick-format is simply plainly ignored by the library code.

The tickFormat value is present in the object created by angular while parsing the HTML, but there are no lines of library code that care about it. Only tick-rotate and tick-format-function are managed.
This looks to me a plain old-fashioned bug, certainly it's no enhancement request: documentation talks about possibility to use tick-format but the code does not support it.

@tamasgal - after your kind clarifications offline, I have implemented inside the controller code my own series of formatting functions like:
$scope.dDOTmDOTYFormattingFunction = function(t) { return d3.time.format("%d.%m.%Y")(new Date(t)); }

...and so on.

Hi,
I'm having the same issue, where should I put that function @tamasgal? Inside the controller, in an apart js...
thanks.

This issue is becoming many issues in one. Going to extract multiple issues out of this one. Than I am closing this issue.

This issue is becoming many issues in one. Going to extract multiple issues out of this one. Than I am closing this issue.

Everything should be fine now. The example contains an example in the dynamic tab using time series. Going to close the issue, in case of problems feel free to let me know.

Everything should be fine now. The example contains an example in the dynamic tab using time series. Going to close the issue, in case of problems feel free to let me know.

This does not appear to be fixed in version 1.3.1 or there is a regression. The formatting is off as in the case for @marco-faustinelli e.g. requesting for a formatting of %Y-%m-%d for a valid date object returns the %H instead which is 05 PM in my case. I had to resort to the workaround formatting function in this thread to get it to work. See the attached screenshot.

I confirm that the issue is still in 1.3.1, I have used a format function, the same workaround @tamasgal proposed.

Hi there, i am having this issue too with last version. So i have a question because i started with hottowel angular project and i can't use 'd3' as you all did for the workaround of @tamasgal. So how do i inject d3 to use it in my controller ?

Is this still unresolved?  I'm unable to even use the tick-format-function workaround.


Add project logo

I provide this image for inspiration:

I mean, the actual inspiration for the name was more like https://i.colnect.net/f/1792/497/Brugse-Zot.jpg  :)   But I concede that may not be very inspiring.

I will take on this and engage some professionals. Any theme ideas apart from the above are welcome :)

Design contest started with 99 designs.  It's been fast-tracked to be done in 3 days.  When, I get the first set of candidate logos I'll hit you up for your opinion @rchamarthy

@rchamarthy @liljenstolpe Would love your feedback

By my favorite artist:

![](file:///tmp/zot-in-the-box.png)

Another, newer, logo is currently used.


[FLINK-26652][runtime] Makes Flink cluster not fail in case of the cleanup retries being exhausted

What is the purpose of the change
Flink 1.14- would just print warning in case of failures. The initial 1.15 retrable cleanup functionality failed the cluster fatally if the cleanup failed. This can happen if the user decides to limit the number of attempts (by default, Flink will try to cleanup infinitely). This would cause issues in session mode: Other jobs stop as well with the whole Flink cluster failing fatally. That's not what we want.
In contrast, for job and application mode: Failing fatally would be an option to notify the user about the failure. Flink is left in an inconsistent state. In HA mode, this would lead to a restart of the worker and the cleanup is picked up again. That would result in the cleanup logic being triggered again which might not be what the user intended when limiting the cleanup retries.
Therefore, logging a warning in case of the job and application mode is the more reasonable thing to do.
Brief change log

Added log message to Dispatcher after cleanup
Updated default value for fixed-delay to also try infinitely to force the user to explicitly change the configuration parameter if he/she really wants to leave jobs in an inconsistent state
Updated the documentation of the configuration parameters and the retryable cleanup accordingly

Verifying this change

Adapted DispatcherCleanupITCase - the test would now fail if the cluster fails fatally due to the TestingFatalErrorHandlerResource before verified after the test succeeded.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: yes
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? docs

I addressed your comments, updated the docs, fixed the test flakiness, squashed the commits and rebased the branch. PTAL

@flinkbot run azure

I fixed the docs issue in the force push. Don't know why ci didn't pick it up 🤔

Ok, looks like my browser cache wasn't freed properly. Now, the successful run shows up

I did another force-push after realizing that there were some minor doc issues (double period at the end of the sentence). Rebase performed as well

I force-pushed the minor docs change. The test failure of the previous ci run is documented in FLINK-26684

I override the values now. That required some changes in the CleanupRetryStrategyFactory and CleanupRetryStrategyFactoryTest. PTAL

Thanks for your review, @zentol . I addressed your comments and rebased the branch. I'm gonna go ahead and create a 1.15 backport


RuntimeError: super(): empty class cell

Trying to lint a file renders the following error:
I have two linters installed for JavaScript, jshint and eslint.
Any ideas?
SublimeLinter: --------------------
SublimeLinter: chdir not set or invalid, using /Users/michiel/Documents/storied/repos/discovery-server
SublimeLinter: eslint: server.js ['/usr/local/bin/eslint', '--format', 'compact', '--stdin', '--stdin-filename', '__RELATIVE_TO_FOLDER__']
SublimeLinter: error in SublimeLinter daemon:
SublimeLinter: --------------------
SublimeLinter: Traceback (most recent call last):
  File "/Users/michiel/Library/Application Support/Sublime Text 3/Packages/SublimeLinter/lint/queue.py", line 58, in loop
    except Empty:
  File "./queue.py", line 175, in get
queue.Empty

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/michiel/Library/Application Support/Sublime Text 3/Packages/SublimeLinter/lint/queue.py", line 66, in loop
  File "/Users/michiel/Library/Application Support/Sublime Text 3/Packages/SublimeLinter/lint/queue.py", line 112, in lint
  File "/Users/michiel/Library/Application Support/Sublime Text 3/Packages/SublimeLinter/sublimelinter.py", line 119, in lint
    Linter.lint_view(view, filename, code, hit_time, callback)
  File "/Users/michiel/Library/Application Support/Sublime Text 3/Packages/SublimeLinter/lint/linter.py", line 919, in lint_view
    continue
  File "/Users/michiel/Library/Application Support/Sublime Text 3/Packages/SublimeLinter/lint/node_linter.py", line 78, in lint
  File "/Users/michiel/Library/Application Support/Sublime Text 3/Packages/SublimeLinter/lint/linter.py", line 1379, in lint
  File "/Users/michiel/Library/Application Support/Sublime Text 3/Packages/SublimeLinter/lint/linter.py", line 1785, in run
    return self.tmpfile(cmd, code)
  File "/Users/michiel/Library/Application Support/Sublime Text 3/Packages/SublimeLinter-contrib-eslint/linter.py", line 96, in communicate
    return super().communicate(cmd, code)
RuntimeError: super(): empty __class__ cell

I know this sounds dumb, but does it work after a restart of SublimeText?
So the first error, is from SL and it causes a fatal error in the plugin, and from what I can tell, that causes the contrib-eslint plugin failure as well. Not sure, and I'm having trouble replicating the issue.
Maybe @roadhump has an idea?

Seems to work again after a Sublime restart.
Thanks for the suggestion!
Not sure how I got the error in the first place, I rarely restart Sublime Text.

While I'm confused on what caused the issue. I'm glad to hear it's working for you again!


Allow regex matching for string fields

Right now we allow q-types of begins/ends/matches/excludes/contains for strings. We could also allow something like "is like" and support simple regular expressions.

Agreed to implement BYBTW 2/6/2020


Postman tests running against localhost only and not Netlify preview deploy

Describe the bug
CI flow has a bug. It waits for netlify preview deployment, but does not use it for test run.
https://github.com/ambianic/ambianic-subscriptions/blob/3d9c15b39721ee426f8141ba0bc57992e27fa09c/.github/workflows/ci.yml#L34
      - name: Wait for successful preview deployment
        if: ${{ github.event_name == 'pull_request' }}
        uses: jakepartusch/wait-for-netlify-action@v1
        id: get-netlify-url
        with:
          site_name: "ambianic-serverless"
          max_timeout: 60

      - name: Run tests against deployed preview
        if: ${{ github.event_name == 'pull_request' }}
        run:  npm run test:postman
        env:
          FUNCTION_URL: http://<IP_ADDRESS>:4010

Expected behavior
Inspect closely the ambianc-ui flow to understand how netlify wait assigns an environment variable which is then passed on to the test step.
https://github.com/ambianic/ambianic-subscriptions/blob/3d9c15b39721ee426f8141ba0bc57992e27fa09c/.github/workflows/ci.yml#L46

@ivelin i would have to rename and adjust that CI job to run tests locally.
Like we discussed earlier, the tests are making use of the Mock HTTP server provided by Prism and the FUNCTION_URL variable is the endpoint for the test server.
Since the wait-for-netlify-action also ensures that a preview deployment was made successfully on Netlify, i thought it good to keep the action within the workflow. Asides that, the deployed preview is not being used by other steps within the workflow.

@vickywane testing locally is one step. Testing against preview deploy is a separate step. Both have value.
Currently wait-for-netlify is sitting on its own, but is not used in a follow up test step against the preview deployment.
See again the ambianic-ui lighthouse flow and add the necessary test step to verify the API against the netlify preview deployment using the URL variable provided by wait-for-netlify.


internal/tmpl: add postprocessing support

This enables callers to selectively opt out of the liveview
tree model by marking a section of a template for postprocessing
using matched postprocessing start/end functions.
When postprocessing starts, we disable all tree operations,
instead writing the output directly to the writer,
which (in the case of a tree) is a buffer.
We also provide a global postprocessing context variable.
When postprocessing ends, we provide the context variable and
buffer contents to the postprocessing end function to handle as it will;
whatever it returns/writes will be recorded as a dynamic
tree element, as if the entire postprocessed section was
generated in a single operation.
Because this is an unusual need, we add no API for it.
Instead, it is hidden behind magic named functions in the funcmap.
Note that all operations must be able to be executed in both
regular execution and tree mode. Writing postprocessing functions
is thus decidedly brain-bending.

sigh. hold on. just discovered one more thing we need here...

I've been wrong so many times so far, but I think this is finally ready for review.


browser.refresh() fails on IE11 without a timeout

Not sure if this one's known already.
Also not sure if this relates to the Webdriver update that led to browser.wait needing an explicit timeout.
But have found browser.refresh fails on IE (tested on IE11), whereas it worked fine on Chrome and Firefox.
- Failed: waiting for page to load for 10ms
Wait timed out after 107ms

Confirmed we no longer see this issue on IE11 with the latest Protractor.


[macos]] GUI version seems not complete

I get errors like 'can't find electrum server' and coin icons are missing. It start's up, but asicly all actions end in error. Last working GUI version for mac seems to be 1.0.7-rc.

Same with checkout latest dev branch

errors while installing
`/Users/bartvm/BarterDEX/node_modules/electron/install.js:47
throw err
^
Error: EACCES: permission denied, mkdir '/Users/bartvm/BarterDEX/node_modules/electron/electron-tmp-download-23078-1537174607632'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.`
errors while starting:
`start prices_loop

DEX stats <IP_ADDRESS>:7783 bind sock.24 DEX stats API enabled at unixtime.1537174776 <<<<<<<<<
sig failure.({"pubkey":"f20555287c8b9bb3889a69c69e457e8734a9e4cee45b84c30ee058ea6424c333","base":"KMD","rel":"BTC","price":0.0001
open
{ Error: ENOENT: no such file or directory, open '/Users/bartvm/Library/Application Support/BarterDEX/CoinsDB/explorers/KMD'
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/Users/bartvm/Library/Application Support/BarterDEX/CoinsDB/explorers/KMD' }
{ Error: ENOENT: no such file or directory, open '/Users/bartvm/Library/Application Support/BarterDEX/CoinsDB/electrums/KMD'
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/Users/bartvm/Library/Application Support/BarterDEX/CoinsDB/electrums/KMD' }
{ Error: ENOENT: no such file or directory, open '/Users/bartvm/Library/Application Support/BarterDEX/CoinsDB/explorers/KMD'`

you need to first enable all the coins in manage coins tab: https://www.youtube.com/watch?v=zVziQQvjb-I

Okay. Updated coins (local) and seems solved. Only 'my offers' (not updating) and 'trade status' (sluggish) remain to be problems


Use correct permission name

See: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions

We need to update the distributables in order to merge this, so I've incorporated your commit into PR #83 to get that resolved. 👍🏻


comment plugin: add comment syntax for Factor

Simply adds the comment symbol used by Factor, !, to the comment plugin.

Micro currently does not recognize "factor" file type so this change alone does not do much. It would be good to add a syntax file as well to detect the file type.

I'm using one locally but it's not polished enough to contribute:
filetype: factor

detect:
    filename: "\\.factor(-rc)?$"

rules:
    - comment: "!.*$"
    - comment: "/\\*.*\\*/"
    - symbol.operator: "\\[|\\]|\\(|\\)|\\{|\\}|;|--|:|>>"  # Added curly braces and colon
    - constant.string: "\".*\""
    - constant: "\\b(t|f)\\b"
    - type: "\\b[A-Z][A-Z0-9_-]*:\\b"  # All-caps words ending with colon
    - type: "\\b(USING:|IN:|FROM:|QUALIFIED:|ALIAS:|RENAME:)\\b"
    - statement: "\\b(2nip|2dup|2drop|2bi|2tri|2curry|2dip|2keep|2over|3bi|3curry|3dip|3drop|3dup|3keep|3tri|4dip|4drop|4dup|4keep|deep-clone|keep-under|bi-curry|clone|\\?execute|\\?if|and|assert|assert=|assert\\?|bi-curry|bi@|bi\\*|boolean|call|clear|compose|curry|die|dip|do|drop|dup|execute|if|keep|loop|new|nip|not|null|object|or|over|pick|rot|swap|throw|unless|until|when|while|with|wrapper)\\b"
    - identifier: "^:\\s+[\\w-]+\\b"
    - constant.number: "\\b[0-9]+\\b"

If anyone else wants to have a go, for reference here are some existing regex-based syntax highlighting definitions for Factor:

highlight
vim


Adding additional data to weekly export

The Crab and subsetted herbarium collections transcription data are not included in the weekly (tabular) exports. These are the relatively new collections that were added for the WeDigBio event in October. These need to get added.
I realize that it may require some discussion for how best to include the subsetted herbarium ones in the tabular exports.

Closed by #383


[Bug report] Internal server error on fresh project since vite is default: "Cannot read property '0' of undefined"

Bug report
(first erroneously reported in vuepress main repo)
Steps to reproduce
Follow Getting started guide

cd empty-project-dir/ && yarn init
yarn add --dev vuepress@next
mkdir docs && echo '# Hello VuePress' > docs/README.md
yarn vuepress dev docs
Visit http://localhost:8080

or clone this repo && yarn && yarn vuepress dev docs
What is expected?
normal page being rendered
What is actually happening?
Empty page & this error in console:
[vite] Internal server error: Cannot read property '0' of undefined
      at Context.load (/home/manu/dev/stuff/vuepress-root-repro/node_modules/vite/dist/node/chunks/dep-0351185a.js:21372:65)
      at Object.load (/home/manu/dev/stuff/vuepress-root-repro/node_modules/vite/dist/node/chunks/dep-0351185a.js:36961:50)
      at processTicksAndRejections (internal/process/task_queues.js:95:5)
      at async doTransform (/home/manu/dev/stuff/vuepress-root-repro/node_modules/vite/dist/node/chunks/dep-0351185a.js:51996:24)

debugging details

the stacktrace origin code is in vite: src/node/plugins/html.ts#L80

htmlProxyMap.get(config) = Map(1) { '/index.html' => [ "\nimport<EMAIL_ADDRESS>] }
file = 'http://localhost:8080/index.html'
config.root = '/home/.../vuepress-root-repro/docs/.vuepress/.temp/vite-root'
=> config.root is the directory but the code expects the HTTP root, so the root is not replaced with '', thus the error
=> it might be a vite issue? I'm not sure where the config.root is coming from or what it's supposed to be

Regression details
I have narrowed it down:

<EMAIL_ADDRESS>has the problem
<EMAIL_ADDRESS>does not - see working branch

Changelog says this version changes default bundler to vite so that might be it.
Other relevant information

Output of npx vuepress info in my VuePress project:

  System:
    OS: Linux 5.4 elementary OS 5.1.7 Hera
    CPU: (8) x64 Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz
    Memory: 294.29 MB / 11.60 GB
    Shell: 3.3.1 - /usr/bin/fish
  Binaries:
    Node: 14.18.2 - /tmp/yarn--1642540887358-0.748250110059048/node
    Yarn: 1.22.17 - /tmp/yarn--1642540887358-0.748250110059048/yarn
    npm: 6.14.15 - ~/n/bin/npm
  Utilities:
    Git: 2.34.1 - /usr/bin/git
  Browsers:
    Chrome: Not Found
    Firefox: 97.0b4
  npmPackages:
    @vuepress/bundler-vite:  2.0.0-beta.33
    @vuepress/bundler-webpack: Not Found
    @vuepress/cli:  2.0.0-beta.33
    @vuepress/client:  2.0.0-beta.33
    @vuepress/core:  2.0.0-beta.33
    @vuepress/markdown:  2.0.0-beta.33
    @vuepress/plugin-active-header-links:  2.0.0-beta.33
    @vuepress/plugin-back-to-top:  2.0.0-beta.33
    @vuepress/plugin-container:  2.0.0-beta.33
    @vuepress/plugin-debug: Not Found
    @vuepress/plugin-docsearch: Not Found
    @vuepress/plugin-external-link-icon:  2.0.0-beta.33
    @vuepress/plugin-git:  2.0.0-beta.33
    @vuepress/plugin-google-analytics: Not Found
    @vuepress/plugin-medium-zoom:  2.0.0-beta.33
    @vuepress/plugin-nprogress:  2.0.0-beta.33
    @vuepress/plugin-palette:  2.0.0-beta.33
    @vuepress/plugin-prismjs:  2.0.0-beta.33
    @vuepress/plugin-pwa: Not Found
    @vuepress/plugin-pwa-popup: Not Found
    @vuepress/plugin-register-components: Not Found
    @vuepress/plugin-search: Not Found
    @vuepress/plugin-shiki: Not Found
    @vuepress/plugin-theme-data:  2.0.0-beta.33
    @vuepress/plugin-toc: Not Found
    @vuepress/shared:  2.0.0-beta.33
    @vuepress/theme-default:  2.0.0-beta.33
    @vuepress/utils:  2.0.0-beta.33
    vue:  3.2.27
    vue-loader: Not Found
    vue-router:  4.0.12
    vuepress: ^2.0.0-beta.33 => 2.0.0-beta.33
    vuepress-vite:  2.0.0-beta.33
    vuepress-webpack: Not Found

Okay... just realised it's not reproducible on other machines:
https://gitpod.io/#https://github.com/tennox/vuepress-root-bug-repro
Urgh...
On gitpod, the id is /workspace/vuepress-root-bug-repro/docs/.vuepress/.temp/vite-root/index.html?html-proxy&index=0.js, as opposed to the http://localhost:8080/index.html?html-proxy&index=0.js on my machine

Okay, f*ck my life... it took me hours but here's what I found:
The IPFS companion extension was interfering with localhost:8080 traffic in some way :see_no_evil:  (no idea why that then causes this issue... :astonished: ).
Disabled it and now everything works fine :sweat:
Sorry to bother, hope you might laugh about it :laughing:


Fixed RenderTexture being upside down on Android in SFML 2.6 (backport of #2719)

This fixes https://github.com/SFML/SFML/issues/2419 on the 2.6.x branch
The fix was already merged in the master branch with https://github.com/SFML/SFML/pull/2719, this is a backport for the 2.6.x branch
How to test this PR?
The following code is supposed to render a green circle in the top left corner of the screen.
On Android, before the change from this PR is applied, the green circle will appear in the bottom left corner instead.
#include <SFML/Graphics.hpp>
int main()
{
    sf::RenderWindow window(sf::VideoMode::getDesktopMode(), "SFML works!", sf::Style::Fullscreen);

    sf::CircleShape circle(400.f);
    circle.setFillColor(sf::Color::Green);

    sf::RenderTexture texture;
    texture.create(window.getSize().x, window.getSize().y);

    texture.clear();
    texture.draw(circle);
    texture.display();

    sf::Texture copiedTexture = texture.getTexture();
    sf::Sprite sprite(copiedTexture);

    bool active = window.hasFocus();
    while (window.isOpen())
    {
        sf::Event event;
        while (window.pollEvent(event))
        {
            switch (event.type)
            {
            case sf::Event::Closed:
                window.close();
                break;
            case sf::Event::LostFocus:
                window.setActive(0);
                active = 0;
                break;
            case sf::Event::GainedFocus:
                window.setActive(1);
                active = 1;
                break;
            case sf::Event::KeyReleased:
                if (event.key.code == sf::Keyboard::Escape)
                    window.close();
                break;
            }
        }
        if (!active)
            continue;

        window.clear();
        window.draw(sprite);
        window.display();
    }
}

SFMLBuildMaster: Build this please.

I know you already tested #2719 but can you also please test this on your device? I'd like to be certain that the fix is still valid when applied to this separate branch.

To be clear, I did retest the issue and solution on the 2.6 branch before making the PR, I didn't just copy the code without checking.
Nevertheless it is always best if someone else can independently verify that it works as well.


Languages in discovery json v2

Discovery uses {} when profiles have no name instead of expected [].

@jornane Can you fix the json?

Fixed, the issue was entirely in the discovery generator, so no changes needed here.

Client side changes are needed and what this ticket was about.

Tested on: iPhone 11 Pro Max, iOS 16.7.2
Version: geteduroam v152
✅ test approved
I checked with the University of Ghent. This is a different name in NL than in ENG. Indeed, I can only see that one via searching on Ghent depending on the language that I am set in.


Add Telegram to social

The SVG icons comes from https://github.com/encharm/Font-Awesome-SVG-PNG. If you use some other unified source of SVG icons for the social icons, please let me know.
fix #295

Will this be released in the gem?


Don't download runc manually

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Runc now ships as part of the package, so there is no need to download it manually any more.
Which issue(s) this PR fixes:

None
Does this PR have test?
None

Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

Codecov Report

Merging #2114 (2af2979) into main (11d77f4) will decrease coverage by 0.09%.
Report is 24 commits behind head on main.
The diff coverage is 0.00%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2114      +/-   ##
==========================================
- Coverage   45.50%   45.41%   -0.09%
==========================================
  Files          79       79
  Lines        7782     6416    -1366
==========================================
- Hits         3541     2914     -627
+ Misses       4099     3360     -739
  Partials      142      142


chore: remove "Welcome" title from Home Tab

Description
Remove "Welcome" title from Home Tab
Test plan
Adjust existing TabHome tests
Related issues

Relates to RET-1189

Backwards compatibility
Yes
Network scalability
If a new NetworkId and/or Network are added in the future, the changes in this PR will:

[x] Continue to work without code changes, OR trigger a compilation error (guaranteeing we find it when a new network is added)

@kathaypacific I'll merge for now and might take a look into the warnings once I'm done with the current task!


Action Entity send_stream_msg don't send all the chunks

Describe the bug
When making a request via stream, the first payload sent in the stream is not sent to the user function.
Example:
/home/sleipnir/go/bin/grpcurl -d @ --plaintext localhost:9000 cloudstate.tck.model.action.ActionTckModel/ProcessStreamed <<EOF
{
   "groups":{
      "steps":[
         {
            "reply":{
               "message":"The north face was first climbed on July 24, 1938"
            }
         }
      ]
   }
}

{
   "groups":{
      "steps":[
         {
            "reply":{
               "message":"The north face was first climbed on July 24, 1939"
            }
         }
      ]
   }
}

{
   "groups":{
      "steps":[
         {
            "reply":{
               "message":"The north face was first climbed on July 24, 1940"
            }
         }
      ]
   }
}

{
   "groups":{
      "steps":[
         {
            "reply":{
               "message":"The north face was first climbed on July 24, 1941"
            }
         }
      ]
   }
}
EOF

The logs resulting from this request is:
2022-02-13 06:41:27.112 [massa-001@<IP_ADDRESS>]:[pid=<0.3878.0> ]:[debug]:Running client stream #Function<59.58486609/2 in Stream.transform/3>
2022-02-13 06:41:27.112 [massa-001@<IP_ADDRESS>]:[pid=<0.3878.0> ]:[debug]:send_stream_msg %Cloudstate.Action.ActionCommand{metadata: %Cloudstate.Metadata{entries: []}, name: "ProcessStreamed", payload: nil, service_name: "cloudstate.tck.model.action.ActionTckModel"}
2022-02-13 06:41:27.113 [massa-001@<IP_ADDRESS>]:[pid=<0.3878.0> ]:[debug]:send_stream_msg %Cloudstate.Action.ActionCommand{metadata: nil, name: "", payload: %Google.Protobuf.Any{type_url: "type.googleapis.com/cloudstate.tck.model.action.Request", value: "\n7\n5\n3\n1The north face was first climbed on July 24, 1939"}, service_name: ""}
2022-02-13 06:41:27.113 [massa-001@<IP_ADDRESS>]:[pid=<0.3878.0> ]:[debug]:send_stream_msg %Cloudstate.Action.ActionCommand{metadata: nil, name: "", payload: %Google.Protobuf.Any{type_url: "type.googleapis.com/cloudstate.tck.model.action.Request", value: "\n7\n5\n3\n1The north face was first climbed on July 24, 1940"}, service_name: ""}
2022-02-13 06:41:27.114 [massa-001@<IP_ADDRESS>]:[pid=<0.3878.0> ]:[debug]:send_stream_msg %Cloudstate.Action.ActionCommand{metadata: nil, name: "", payload: %Google.Protobuf.Any{type_url: "type.googleapis.com/cloudstate.tck.model.action.Request", value: "\n7\n5\n3\n1The north face was first climbed on July 24, 1941"}, service_name: ""}

As you can see from the payload: nil the first message goes with the payload attribute empty, and that's why in the reacquisition return only three messages are returned instead of four:
...
EOF
{
  "message": "The north face was first climbed on July 24, 1939"
}
{
  "message": "The north face was first climbed on July 24, 1940"
}
{
  "message": "The north face was first climbed on July 24, 1941"
}

To Reproduce
Steps to reproduce the behavior:

Execute docker user function docker run -it --rm -p 8090:8080 gcr.io/eigr-io/eigr-go-tck-action
Execute proxy MIX_ENV=prod USER_FUNCTION_PORT=8090 iex --name<EMAIL_ADDRESS>-S mix
Via grpcurl run the request from the example above
See error

Expected behavior
That the response of all messages return in the console.

@sleipnir this might be the reason for what is observed here in this issue https://github.com/eigr-labs/akkaserverless-protocol/blob/main/cloudstateio-protocol/cloudstate-protocols-0.6.0/protocol/cloudstate/action.proto
// For streamed in and duplex streamed calls, the first command sent will just contain the service
// name and command name, but no payload. This will indicate that the action has been invoked.
// Subsequent commands on the stream will only have the payload set, the service name and command
// name will not be set.

@sleipnir I think I misunderstood this issue, while the proxy does not sent the first message, I found that from the user functions perspective, in detail, in perspective of its runtime support, the proxy has to send first a command without any payload at all. I though you describe this issue as an issue of the SDK implementation, which seems not to be.

@sleipnir this might be the reason for what is observed here in this issue https://github.com/eigr-labs/akkaserverless-protocol/blob/main/cloudstateio-protocol/cloudstate-protocols-0.6.0/protocol/cloudstate/action.proto
// For streamed in and duplex streamed calls, the first command sent will just contain the service
// name and command name, but no payload. This will indicate that the action has been invoked.
// Subsequent commands on the stream will only have the payload set, the service name and command
// name will not be set.

Hi @marcellanz, I think we have two things here.
Firstly, an implementation misconception that causes a message sent by the user to not have a complete response and second, and what led to the first mistake, a serious protocol design flaw (in my opinion), I don't know why this separation of first and other messages is necessary, especially regarding stateless functions such as Actions.
The fact that you don't send valuable information in every payload generates all sorts of work arounds in SDK implementations just to maintain this kind of state that should be co-located with the payload. I find this literally bizarre and completely unnecessary, I even tested it by making the proxy send the service_name, and name in all requests and the user role implemented with the Go SDK kept returning me without problems, that is, there is no validation on this on the user side, and neither should there be.
I think here we can clearly diverge from the original protocol.

Yes, I had read that. Overall, it is unnecessary complexity and so far only justified by sending Metadata in the first message.

We can change that.

@sleipnir why does the current protocol and its description not make sense? Or why did it even made sense in the beginning?

My question is that first if the user sends ten messages the user function should probably respond with ten messages, this is a point where the Cloudstate description is confusing by not making it clear that this is its intention, that is, the protocol should say that an empty message body containing only the metadata should be added to the beginning of the stream, being the first message that the user role would have to deal with. Second information like service_name and command_name for me are crucial in all sends and not just in the first message, making this a must makes the design of messages and sdks considerably simpler (at least in the sdks I had to implement).
How it ever made sense I don't know, I've always gone against the grain but James seems to have convinced everyone at the time that this was good design.
It seems to me that certain things in Cloudstate and Akkaserveless are the way they are because they better match the Akka/Scala way of doing things and not because they make general architectural sense.

I fully agree with the point of made by @sleipnir. Cloudstate and Akkaserveless are making thing that fits theirs Akka/Scala and not because they make general architectural sense. We should be able to remove things if they do not make sense. But also we should strive for a general architectural which makes sense


Add Godeps directory or at least Godeps.json file

Hi,
would it be possible to add Godeps directory to skydns containing all imported packages? Or at least Godeps.json file listing commits of imported packages?
Thanks
Jan

If I am going to do something like this, it will likely be with gb.
On 3 Jun 2015 1:36 pm, "ingvagabund"<EMAIL_ADDRESS>wrote:

Hi,
would it be possible to add Godeps directory to skydns containing all
imported packages? Or at least Godeps.json file listing commits of imported
packages?
Thanks
Jan
—
Reply to this email directly or view it on GitHub
https://github.com/skynetservices/skydns/issues/184.


Make table full width when mouse hovered

Why?
The Type column in dev doc tables is invisible without scrolling the column, even on a very wide browser because of an artificially narrow center div.
What?
This PR makes the table in a page full width when mouse hovered. It also adds a background color to hide the table transparency when scrolled over another element/content.
How?

Checkout to this branch locally.
In  cloudflare-docs repo, cd into products/<IP_ADDRESS> or any other products.
Point the cloudflare-docs-engine package to it's local version. Usually, ../../../cloudflare-docs-engine if cloudflare-docs-engine and cloudflare-docs folders are in the same directory.
Install dependencies using yarn install.
Then run yarn bootstrap and yarn start to run the product in development environment.
Point your browser to http://localhost:8000/reference/log-fields/zone/spectrum_events and http://localhost:8000/logpull/requesting-logs

Once this PR gets merged, I will regenerate the lock files of the products in cloudflare-docs so they can have the latest changes

I will push a fix shortly


WebRequestPSCmdlet does not check existance of Location header when Authorization is present

The code introduced in https://github.com/PowerShell/PowerShell/pull/3885 seems to have introduced a regression bug which was quite hard to identify as the error message points to issues with the URI and not to anything related to redirection. The code introduced in the pull request initializes an URI using the Location Header, without first checking if the Location Header is present in the response of a redirect.. The HTTP RFC 7231 does not specify the Location Header to be mandatory and thus it's existance must be checked.
I discovered this while checking strange PowerShell errors when issuing a GET or HEAD request against a AWS S3 Bucket while connecting to the wrong region. AWS S3 does respond with HTTP 301 but without a Location header.
The issue only occurs if the Server responds with a redirect HTTP Status Code 3XX and without the Location header and if the client has specified the Authorization Header in the initial request.
The issue can probably be fixed by modifying line 1290 to if (stripAuthorization && IsRedirectCode(response.StatusCode) && response.Headers.Location).
I'd be glad to create a pull request to fix this issue if my analyzis is correct and the proposed change is the correct way to fix the issue.
Actual behavior
The following simple HEAD request demonstrates the unexpected error message:
Invoke-WebRequest -Uri https://s3.amazonaws.com/test-301-redirection/ -Method HEAD -Headers @{Authorization="test"}
Invoke-WebRequest : Value cannot be null.
Parameter name: uri
At line:1 char:1
+ Invoke-WebRequest -Uri https://s3.amazonaws.com/test-301-redirection/ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [Invoke-WebRequest], ArgumentNullException
+ FullyQualifiedErrorId : System.ArgumentNullException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Expected behavior
The response should be
Invoke-WebRequest -Uri https://s3.amazonaws.com/test-301-redirection/ -Method HEAD -Headers @{Authorization="test"}
Invoke-WebRequest : Response status code does not indicate success: 301 (Moved Permanently).
At line:1 char:1
+ Invoke-WebRequest -Uri https://s3.amazonaws.com/test-301-redirection/ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidOperation: (Method: HEAD, R...rShell/6.0.2
}:HttpRequestMessage) [Invoke-WebRequest], HttpResponseException
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

A workaround is, to specify the PreserveAuthorizationOnRedirect Parameter which will skip the section introduced in https://github.com/PowerShell/PowerShell/pull/3885 :
Invoke-WebRequest -Uri https://s3.amazonaws.com/test-301-redirection/ -Method HEAD -Headers @{Authorization="test"} -PreserveAuthorizationOnRedirect
Invoke-WebRequest : Response status code does not indicate success: 301 (Moved Permanently).
At line:1 char:1
+ Invoke-WebRequest -Uri https://s3.amazonaws.com/test-301-redirection/ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidOperation: (Method: HEAD, R...rShell/6.0.2
}:HttpRequestMessage) [Invoke-WebRequest], HttpResponseException
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Environment data
$PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.0.2
PSEdition                      Core
GitCommitId                    v6.0.2
OS                             Darwin 17.4.0 Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Can you see if the same thing happens in 6.1.0-preview.1? I think i fixed this in #6325

In 6.1.0-preview.1 I get a different error. I think even with your change, you are still expecting the Location header to be present.
PowerShell v6.1.0-preview.1
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/pscore6-docs
Type 'help' to get help.

PS /Users/florianfeldhaus> Invoke-WebRequest -Uri https://s3.amazonaws.com/test-301-redirection/ -Method HEAD -Headers @{Authorization="test"}
Invoke-WebRequest : Object reference not set to an instance of an object.
At line:1 char:1
+ Invoke-WebRequest -Uri https://s3.amazonaws.com/test-301-redirection/ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [Invoke-WebRequest], NullReferenceException
+ FullyQualifiedErrorId : System.NullReferenceException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Yup. Per the RFC "The server SHOULD generate a Location header field in the response containing a preferred URI reference for the new permanent URI." Oof.. so the Location header may not be present and we are currently not checking for that.
Your proposed fix LGTM. Go ahead with a PR.  might be a bit painful getting the test for that.. maybe not.


on small device words not displayed all at a time

freezes/general reliability. When generating the seed for the border wallet not all 12 words display on the screen at once for smaller screen phones.

iPhone SE
https://github.com/bithyve/bitcointribe/assets/61345820/588f200a-71ce-4f17-bdeb-ca85d595ce96

https://xd.adobe.com/view/e7fe32c6-047a-42b3-b3fe-fe92b4d9e11b-b2ad/screen/91a10138-860d-4a70-a05f-ae98d1d60d8f/

resolved


usm: Refactor nodejs monitor to use new uprobe attacher

What does this PR do?
This PR applies the new uprobe attacher introduced in https://github.com/DataDog/datadog-agent/pull/27663 to the NodeJS monitor.
Motivation
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes
Validated in system-probe load testing environment, using the soak_test and processes scenarios. Base version is agent release 7.57

soak_test
Summary: similar accuracy results, no significant difference in resource usage.
Dashboard
Resource usage:

Accuracy for base:

Accuracy for new  (this branch):

Accuracy comparison:

processes
Summary: negligible resource usage differences.
Dashboard
Resource usage:

/merge


Add vector compare to 0 optims

Signed-off-by: Freddie Liardet<EMAIL_ADDRESS>Optimization for simd comparisons to 0 vectors using dedicated instructions.

Thanks!


Navbar: Describe views in top navbar.

Adds description in views styled like stream descriptions along with adding a help center link to the appropriate page at the end of each description.
CZO thread
Fixes: #29769

Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Thanks! This does not work well when narrowing the window:

We can let the question mark disappear with the rest of the text when everything doesn't fit.

I also think the question mark is spaced a bit too far to the right.

I'm feeling good about the strings after seeing them in the UI.

@alya for me the help icon is disappearing when narrowing the windows.

https://github.com/zulip/zulip/assets/91622060/463b64bd-1b82-449d-9427-33935abbd05e

@alya I've also corrected the margin of help-icon.

OK, I dunno. I tested in Chrome on a Mac.

I've tested on both Firefox and Chrome on Mac, and I'm not able to reproduce the problem @alya is seeing with the help icon. Everything in testing looks good on my end, in other words.

Everything here LGTM. Probably worth some time on CZO, just because there is this head-scratcher with the help icon. I'll mark it as such, but @timabbott will make whatever seems to be the better call here.

The "combined feed" description seems to not be working on chat.zulip.org.

@timabbott I took a stab at fixing the Combined feed issue here after fixing the merge conflicts. @alya said this was part of the onboarding work, so I wanted to prioritize this

Thanks! I think overall the feature felt good on CZO, so marking it for integration review, since we might merge it without a test-deployment.

I think the problem with combined feed was probably that the check changed from filter === undefined to filter.is_in_home(), and this PR just hadn't been rebased. I did a few tweaks to readability, and added a bonus commit renaming a badly named variable... and some bonus TODO comments that I made after capturing the diff below.
diff --git a/web/src/message_view_header.ts b/web/src/message_view_header.ts
index efc4da43c5..06666bf347 100644
--- a/web/src/message_view_header.ts
+++ b/web/src/message_view_header.ts
@@ -46,6 +46,7 @@ function get_message_view_header_context(filter: Filter | undefined): MessageVie
             link: "/help/recent-conversations",
         };
     }
+
     if (inbox_util.is_visible()) {
         return {
             title: $t({defaultMessage: "Inbox"}),
@@ -56,16 +57,18 @@ function get_message_view_header_context(filter: Filter | undefined): MessageVie
             link: "/help/inbox",
         };
     }
-    if (filter === undefined || filter.is_in_home()) {
+
+    if (filter.is_in_home()) {
         return {
             title: $t({defaultMessage: "Combined feed"}),
             description: $t({
                 defaultMessage: "All your messages except those in muted channels and topics.",
             }),
             zulip_icon: "all-messages",
-            link: "/help/all-messages",
+            link: "/help/combined-feed",
         };
     }
+
     const title = filter.get_title();
     const description = filter.get_description()?.description;
     const link = filter.get_description()?.link;
@@ -76,6 +79,7 @@ function get_message_view_header_context(filter: Filter | undefined): MessageVie
         link,
         is_spectator: page_params.is_spectator,
     });
+
     if (filter.has_operator("channel") && !filter._sub) {
         return {
             ...icon_data,
@@ -86,6 +90,7 @@ function get_message_view_header_context(filter: Filter | undefined): MessageVie
             }),
         };
     }
+
     if (filter._sub) {
         // We can now be certain that the narrow
         // involves a stream which exists and
@@ -101,6 +106,7 @@ function get_message_view_header_context(filter: Filter | undefined): MessageVie
             stream_settings_link: hash_util.channels_settings_edit_url(current_stream, "general"),
         };
     }
+
     return icon_data;
 }

Here's all the TODOs noted:

// TODO: If we're not in the recent or inbox view, there should be
// a message feed with a declared filter in the center pane. But
// because of an initialization order bug, this function gets
// called with a filter of undefined when loading the web app
// with, say, inbox as the home view.
//
// TODO: Refactor this function to move the inbox/recent cases
// into the caller, and this function can always get a Filter object
//
// TODO: This ideally doesn't need a special case, we can just use
// filter.get_description for it.


[Bug] - Plots beeing pasted with Air, destroying other plots

Description
Unsure exactly when this happens, sometimes empty plots beeing pasted in city-inspiration-mode will destroy neighbouring plots
https://imgur.com/a/Je7rtRj
Steps to Reproduce

Create a Plot in C-I mode next to another plot
look and see

Possible Solution
Paste plots in C-I mode without air (-a)

Related Docs for the possible Solution:

Clipboard Pasting
ExistingBlockMask


Warning Indicator Broken In 1.20.2+

In 0.4.1+ versions of uku's Armor HUD, instead of the warning indicator going over the piece of armor that is on low durability, it goes above the piece of armor furthest on the right when the 'Show Widget: Not Empty' is selected. The animation is also broken where instead of bobbing slowly up and down it just cuts between up and down. I noticed the issue in the 1.20.2 version, but it seems like it also appears in the 1.20.3-1.20.4 version as well.

Can confirm on 1.20.4.

fixed in 0.4.4 https://modrinth.com/mod/ukus-armor-hud/version/inle1PJL
sorry for taking so long, github decided not to send me notifications for this repo...


Handle 404 not found for subcategory

Handle when the subcategory is not found (url is like /faq/someSubcategoryIdBlaBla)

@jaroslav-kubicek how can this be reproduced?
@mjancik what should this look like?

I also can't reproduce it.

Can't reproduce? Guys, have you ever tried? it's in the description, just specify invalid categoryId and that's it: https://kiwicom.github.io/smart-faq/?help=%2Ffaq%2FRkFRQ2F0ZWsdscnk6ODk%3D

Well use the same error design as for the bookings, but with different text.

closed by #616


Odd behavior with check-secrets

We just recreated our lab (new Vault, proto-bosh, CF foundation, jumpbox, CA certs). I upgraded just my user on the jumpbox to genesis 2.7.7.

Upgraded proto-bosh env file from 1.9.0 to 1.10.2==[]=[ 12:42:48 ]=[ cfoss-ops-jumpbox jumpbox/0 ]=[ ~/deployments/bosh-deployments ]=[]==
diff --git a/cfoss-ops.yml b/cfoss-ops.yml
index 0005218..8ef07bc 100644
--- a/cfoss-ops.yml
+++ b/cfoss-ops.yml
@@ -1,6 +1,6 @@
 kit:
   name:    bosh
-  version: 1.9.0
+  version: 1.10.2
   features:
     - aws
     - proto

Ran genesis check-secrets. No warnings or issues with certs. Warning about params.env becoming genesis.env==[]=[ 12:42:50 ]=[ cfoss-ops-jumpbox jumpbox/0 ]=[ ~/deployments/bosh-deployments ]=[]==
$ genesis check-secrets cfoss-ops.yml
[WARNING] Kit bosh/1.10.2 requires environment file to specify genesis.env
        but cfoss-ops is using params.env.  Please update your environment file as this
will be removed in a later version of Genesis
Verifying availability of selected vault...ok
Validating 37 secrets for cfoss-ops under path '/secret/cfoss/ops/bosh/':
Completed - Duration: 0 seconds [37 validated/0 skipped/0 errors]

Updated from params.env to genesis.env==[]=[ 12:43:12 ]=[ cfoss-ops-jumpbox jumpbox/0 ]=[ ~/deployments/bosh-deployments ]=[]==
$ git diff
diff --git a/cfoss-ops.yml b/cfoss-ops.yml
index 0005218..9eb58cc 100644
--- a/cfoss-ops.yml
+++ b/cfoss-ops.yml
@@ -1,11 +1,11 @@
 kit:
   name:    bosh
-  version: 1.9.0
+  version: 1.10.2
   features:
     - aws
     - proto
-params:
+genesis:
   env:   cfoss-ops
   # These properties definte the host-level networking for a proto-BOSH.

Ran genesis check-secrets. Now I get 9 warnings==[]=[ 12:43:20 ]=[ cfoss-ops-jumpbox jumpbox/0 ]=[ ~/deployments/bosh-deployments ]=[]==
$ genesis check-secrets cfoss-ops.yml
Verifying availability of selected vault...ok
Validating 37 secrets for cfoss-ops under path '/secret/cfoss/ops/bosh/':
  [ 2/37] blobstore/server X509 certificate ... warning!
          [⚠ ] Subject Name '(( param "What IP will BOSH be accessible on?" ))' (found 'xx.xx.xx.xx')
          [⚠ ] Subject Alt Names (missing: (( param "What IP will BOSH be accessible on?" )); extra: xx.xx.xx.xx)
  [ 4/37] credhub/server X509 certificate ... warning!
          [⚠ ] Subject Name '(( param "What IP will BOSH be accessible on?" ))' (found 'xx.xx.xx.xx')
          [⚠ ] Subject Alt Names (missing: (( param "What IP will BOSH be accessible on?" )); extra: xx.xx.xx.xx)
  [ 6/37] nats/director X509 certificate ... warning!
          [⚠ ] Subject Alt Names (missing: (( param "What IP will BOSH be accessible on?" )); extra: xx.xx.xx.xx)
  [ 7/37] nats/health/monitor X509 certificate ... warning!
          [⚠ ] Subject Alt Names (missing: (( param "What IP will BOSH be accessible on?" )); extra: xx.xx.xx.xx)
  [ 8/37] nats/server X509 certificate ... warning!
          [⚠ ] Subject Alt Names (missing: (( param "What IP will BOSH be accessible on?" )); extra: xx.xx.xx.xx)
  [10/37] ssl/mbus X509 certificate ... warning!
          [⚠ ] Subject Name '(( param "What IP will BOSH be accessible on?" ))' (found 'xx.xx.xx.xx')
          [⚠ ] Subject Alt Names (missing: (( param "What IP will BOSH be accessible on?" )); extra: xx.xx.xx.xx)
  [11/37] ssl/server X509 certificate ... warning!
          [⚠ ] Subject Name '(( param "What IP will BOSH be accessible on?" ))' (found 'xx.xx.xx.xx')
          [⚠ ] Subject Alt Names (missing: (( param "What IP will BOSH be accessible on?" )); extra: xx.xx.xx.xx)
  [12/37] ssl/uaa X509 certificate ... warning!
          [⚠ ] Subject Name '(( param "What IP will BOSH be accessible on?" ))' (found 'xx.xx.xx.xx')
          [⚠ ] Subject Alt Names (missing: (( param "What IP will BOSH be accessible on?" )); extra: xx.xx.xx.xx)
  [13/37] ssl/uaa-sp X509 certificate ... warning!
          [⚠ ] Subject Name '(( param "What IP will BOSH be accessible on?" ))' (found 'xx.xx.xx.xx')
          [⚠ ] Subject Alt Names (missing: (( param "What IP will BOSH be accessible on?" )); extra: xx.xx.xx.xx)
Completed - Duration: 0 seconds [28 validated/0 skipped/0 errors/9 warnings]

As discussed in person, this was because the entire params block was changed to genesis.  The required solution to the warning is to create a new genesis block in your environment file if it doesn't already exist, and move env from under params to be under genesis.
This was done to better delimit ownership of control.  genesis is meant for things that impact deployment and management of the environment file, whereas params block is specifically for things only the kit needs for building its manifest. In this vein, a couple of other items have also moved to be under genesis:

params.bosh becomes genesis.bosh_env
params.vault_prefix (and the legacy params.vault) become genesis.secrets_path

To rectify this issue, I will create a Genesis Migration Process to explain this detail.

GMP-GEN-0001 has been created to inform users of this change of behaviour, and how to remedy it.


Import ERROR ----> from .pmeshlab import *

Hi, thank you for your great work! I meet a error looking at Here. Can you help me?

@zhangquanwei962 This usually indicates the OS is too old, what's your OS?

@ashawkey Thank you for your reply. The os is CentOS Linux release 7.9.2009 (Core) or Linux mgt 3.10.0-1160.el7.x86_64 #1 SMP Mon Oct 19 16:18:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux. I am not sure which is we need.

@ashawkey Thank you for your reply. The os is CentOS Linux release 7.9.2009 (Core) or Linux mgt 3.10.0-1160.el7.x86_64 #1 SMP Mon Oct 19 16:18:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux. I am not sure which is we need.

Here is a discussion in the CentOS forum for a similar error: https://forums.centos.org/viewtopic.php?t=77763
"GLIBCXX_3.4.20+21 are in CentOS 8."
"CentOS 8 died a premature death at the end of 2021 - migrate to Rocky/Alma/OEL/Springdale ASAP."

I met this problem and create a new virtual environment and solved it... don't know why


Main script not executable when moved to another machine

I have written a python script, make it into script.app. Runs perfect on the machine it was created on (M1 Mac). Once I copy the application to another machine (Non-M1 mac) it doesn't work until I 'chmod +x' the script within the script.app on the new machine.

Weird... Must have been a one off thing. I remade it, one with/one without root, seems to have fixed itself.

I lied. More testing revealed its still not working.

What method are you using to copy it? UNIX file permissions might be lost if you're using a dodgy transfer method, e.g. sending via Apple's Mail without zipping first, etc.

Pretty much just copying into OneDrive. I also tried copying to my NAS and then to another machine locally, that worked fine. I’ll try zipping it first to see if that solves the issue with OneDrive.

I think you called it on the UNIX permissions changing. After zipping and then sharing through multiple different ways I have yet to run into the issue again. Thanks for then help!