Check / Change Units in p2_FORESCE_LC_per_catchment_reclass_cat$total_PRMS_area

Change to SQKM as NLCD is in that area at the moment
drb-network-prep PR#2 comment

@msleckman : did you address this issue in #97? Can it be closed?

Not addressed in #97. Should be done when combining NLCD and FORESCE.

PRMS area from edited shapefile are different from the PRMS area given in the NLCD tables. This might be due to rounding process that occurs when aggregating from comid to PRMS in the original NLCD proportions datasets
p1_catchments_edited_sf_areakm2 <- p1_catchments_edited_sf %>%
  sf::st_drop_geometry() %>% group_by(PRMS_segid) %>%
  summarise(PRMS_area_km2 = sum(hru_area_m2)/10^6)

summary(p1_catchments_edited_sf_areakm2$PRMS_area_km2)
    Min.  1st Qu.   Median     Mean  3rd Qu.     Max.
  0.0222  20.5840  55.5049  78.3554 112.0621 541.9462

vs:
> summary(p2_PRMS_NLCD_lc_proportions_reclass_cat[[1]]$AREASQKM_PRMS)
    Min.  1st Qu.   Median     Mean  3rd Qu.     Max.
  0.0009  13.0510  44.2323  70.9794 104.5773 538.9892

[ ] Check proportion_lc_by_prms_tot$AREASQKM_PRMS. Think it is the area of catchment only, not Total upstream.
Need to change proportion_lc_by_prms.R and add a parameter that accepts the TOTDASQKM colname as well as AREASQKM

This blocks #102 because the PRMS areas in final FORESCE (p2_FORESCE_lc_proportions_reclass_cat) != NLCD areas (p2_PRMS_NLCD_lc_proportions_reclass_cat)

Produced gist to review and plot the area difference between area in FORESCE dataset (derived from edited catchments shapefile) and area given in processed NLCD data tables and scaled from comid/nhd to PRMS. Review and comparison done on the back of similar issue #45.

We find about ~28 PRMS segments have catchment polygon area in NLCD != catchment polygon area in FORESCE by over 50 km2. About 17 PRMS segments have a difference over 10 km2.
sample:

TBC:

[ ] complete unchecked bullet above.
[ ] Examine source of difference

Branch 108-... addressing this in my forked repo.
Added function area_diff_fix.R with work in progress on extracting the PRMS_segid with area discrepancy and fixing by pulling it's attributed nhd catchments.

I addressed Change FORE-SCE to SQKM as NLCD is in that area at the moment in https://github.com/USGS-R/drb-inland-salinity-ml/issues/126 by adding hru_area_km2 to p1_catchments_edited_sf. It sounds like you're also using this issue to make the FORE-SCE and NLCD catchment areas match, so maybe https://github.com/USGS-R/drb-inland-salinity-ml/issues/126 shouldn't close this issue

Ah, did not see this. Hopefully this doesnt complicate the pipeline too much (it shouldnt) as I also addressed this in #134 PR that I just submit. I think this PR makes the task transfer smoother.


Ultra L1b dependency update

Change Summary
Overview
Adding dependencies for L1b
Updated Files

dependency_config_ultra.py

Adding new dependencies for L1b

I couldn't find your comment. But to answer your question

Wouldn't this make it to where if only packets from Ultra 45 arrive then it would kick off Ultra 45 and Ultra 90 l1a processing?

Even if your l0 data file only exists Ultra 45 data, in your processing code, you group your data by apid and then process each apid at a time. That should take care of not kicking Ultra 90 since it should have different apid, right?


Whitespace

The project mixes tabs and spaces throughout the source code. I suggest eliminating all tabs from the project. Also, please remove all trailing whitespace.

Submit a pull request.

Done. See #36

Accepted and closed.


[FX-4114] Remove integration builder open beta warnings

Changelog
Updated

Page
Deploy Preview
Comment

Name
Link
Comment

integration builder
https://deploy-preview-547--cobalt-docs.netlify.app/integrations/integrationbuilder/

dast integrations
https://deploy-preview-547--cobalt-docs.netlify.app/platform-deep-dive/scans/integrations/

Preview This Change
To see how this change looks in production, scroll down to Deploy Preview. Select the link that looks like https://deploy-preview-<num>--cobalt-docs.netlify.app/
Variables
Help us support a “Write once, publish everywhere” single source of truth. If you see a line that looks like:
{{% asset-categories %}}
You’ve found a shortcode that we include in multiple documents.
You’ll find the content of the shortcode in the following directory:
https://github.com/cobalthq/cobalt-product-public-docs/tree/main/layouts/shortcodes
That shortcode has the same base name as what you see in the PR, such as asset-categories.html.
Checklist for PR Author
[ ] Did you check for broken links and alt text?
Be sure to check for broken links and Alt Text issues. We have a partially automated process,
as described in this section of our repository README:
Test Links and Alt Attributes.

Do not merge yet


Actions tests are sometimes failing

I sometimes get the following error while running the actions tests:
PASS  tests/reducers/pagination.test.js
FAIL  tests/actions/index.test.js
● Test suite failed to run
TypeError: path must be a string or Buffer

  4 |
  5 | console.log("Using configuration file " + process.argv[2])
> 6 | const anetConfig = jsyaml.safeLoad(fs.readFileSync(process.argv[2], "utf8"))
    |                                       ^
  7 | const Settings = anetConfig.dictionary
  8 | const API = BaseAPI
  9 |

  at Object.readFileSync (platform/node/api.js:6:39)
  at Object.<anonymous> (src/actions/index.js:1:1)

If I run the tests again, they succeed.

Do you have this issue when running yarn test-jest or with yarn jest? With the latter I also get the same issues, however this is not the preferred route to run jest tests. At the moment jest should only be used to test the actions and reducers. yarn test-jest configures the runner with the correct settings.

I have it when doing yarn run test-all.

From @gjvoosten
The error goes away after:
yarn install v1.15.2
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[4/4] Building fresh packages...
Done in 180.88s.

% yarn run test-jest
yarn run v1.15.2
$ jest ../anet.yml --testPathPattern='tests/(actions|reducers)'
 PASS  tests/reducers/pagination.test.js
 PASS  tests/actions/index.test.js
  ● Console

    console.log platform/node/api.js:5
      Using configuration file ../anet.yml

Test Suites: 2 passed, 2 total
Tests:       6 passed, 6 total
Snapshots:   0 total
Time:        1.185s
Ran all test suites matching /..\/anet.yml|tests\/(actions|reducers)/i.

Done in 2.34s.```

This leads me to believe it is some kind of caching problem (perhaps something from a previous branch before switching to this one), although which particular cached item is the culprit is a mystery to me. (edited)


[HOLD for payment 2023-11-07] [HOLD for payment 2023-11-06] [$500] Contact methods - Fix the errors CTA in Add new contact method page crashes the app

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR https://github.com/Expensify/App/pull/29869
Note: Crash is reproducible on Android and iOS app.
On web and desktop, console error shows up.
Action Performed:

Launch New Expensify app.
Go to Settings > Profile > Contact methods.
Click New contact method.
Enter an invalid email.
Click Save.
Click Fix the errors.

Expected Result:
App does not crash.
Actual Result:
App crashes.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[x] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/93399543/a775b4a2-27df-4337-8d9d-0ee527d0aebd

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0131fa74ee0414e807
Upwork Job ID:<PHONE_NUMBER>459390976
Last Price Increase: 2023-10-27

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

cc @luacmartins
I think we should accept both object or function (alternative solution).

Agreed that it should accept both.

@ishpaul777 are you available to work on the alternate solution fix in the next few minutes?

It's yours! Please tag me for review

Fix is being CPed. Keeping this issue open to process payment.

I didn't review the PR actually. It was reviewed internally.

Just pending payment

Payments

[ ] Reporter: N/A
[ ] Contributor: @ishpaul777 ($500 paid via Upwork)
[ ] C+: @abdulrahuman5196 ($500 paid via Upwork)

Contributor hired on / PR merged on Oct 27

offers sent ($500 via Upwork)

paid


[Feature] Encrypt unicode properly for EncryptedTextFields [#OSF-7200]

Purpose
#6766, but for Django
h/t @alexschiller
Changes

Add helper function to ensure incoming strings to be encoded are in the proper utf-8 format
Add tests for helper function and encryption in general since it was untested.

Side effects
None expected
Ticket
#OSF-7200

TCI passed for my build, merging.


Support for SWADE system

It would be great if you could support the SWADE system. I looked into creating a PR, but it seems you have hardcoded basically every assumption that comes with DND, which is unfortunate, as other systems just don't always work this way. One is for example the 6ft grid size.
To fully support another system (and also SWADE) the following would need to be done:

Use the canvas grid size instead of hardcoding 6ft grids. SWADE default distance is 2 yards per Pace (which is the speed of a character). The grid itself is also defined as 2 yards per grid, which means you could simplify the system to just count grids. 1 grid per Pace. Handling it by using the canvas measurements means this should work automatically (set one map grid to be 2 yards and have each Pace count for 2 yards - done). At best allow people to specify the amount of grid units per speed value, this way you would be open for other systems. For DND etc it can be defaulted to 6ft for example.
 It would be great to support it, but I think a simple start is fine)
Weapon ranges are tricky: Basically any value is allowed and there are three "bands" each doubling the distance of the one before. So a value of "12/24/48" is typical for a pistol, meaning you can hit easily up to 12 grid units, get a slight malus up to 24 units and then a bigger malus up to 48 and anything above is nearly impossible to hit. This counts for ranged weapons. Close-combat weapons usually just hit the grid right next to the character, but rarely weapons have a "reach" value, which I don't think is actually implemented into the system itself. The range is found under system.range of the weapon item. This is a string in the above format, so a simple "split" should suffice to give the separate values.
You can find currently equipped weapons by scanning through all items a character has and check for the equipment status. If the system.equipStatus is >= 3 the weapon is equipped.

There is the concept of multi-actions in SWADE, but it's complex and I wouldn't try to implement it from the start. I would instead assume that every character can do one action per turn for now. This can already be set up with the slider in the settings.
I think the most important change should be the first one. Actually using the canvas grid units and letting the user decide in the settings how the speed value is supposed to be interpreted will help a lot in making this module work with non-dnd systems.
As a fellow developer I would recommend to try to refactor the system to have less hardcoded values. Instead using an OOP system might work well here. This way new values for a system could be as simple as inheriting a class and implementing the differences. THis makes it easier for other people to provide PRs as well.
This is a long text and I hope I didn't disencourage you with it :D it's a really great module and I just want more people to be able to enjoy it :)

Sorry I haven't noticed this issue before as issues do not transfer to forks. This module was taken over by me June 16 2023 and is now at this repository. I hope this issue has been resolved since, but if it still persists, please open it again at this page.


Select only month and year

Hi,
In my app, I want my user to be only able to select the year and the month at a certain place. Is there a possibility of parameter to set to disable the day selection?
Thanks

There is no such parameter.
The design of the dialog is meant to select days. It doesn't make a lot of sense when selecting just a month and a year.
You can easily use dropdowns for this.

I get your point, the thing is, I can select months for a big range of years and having dropdown for that with my UI doesn't work well.. I'll find something else, thanks.


Allow flexible formatting from URI: JSON | XML

Some enterprise orchestrations would be easier to manage with XML payloads

Thanks for the PR it has been merged. Do you mind closing this?


Added openshift-logforwarding-splunk to top README

What is this PR About?
Adding openshift-logforwarding-splunk to the list of links in the top-level README
How do we test this?
check link
cc: @redhat-cop/day-in-the-life

thanks @nilsotto 🤸♀


Get url only

How i can get direct url only

machine translation
To get a direct video url you can use for example:
System.out.println(new Youtube("https://www.youtube.com/watch?v=lTRiuFIWV54").streams().getHighestResolution().url);
If you wish to obtain another type of link, please specify it.


Fix warning in FourierTransform

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Before submitting (must do checklist)

[ ] Did you read the contribution guide?
[ ] Did you update the docs? We use Numpy format for all the methods and classes.
[ ] Did you write any new necessary tests?
[ ] Did you update the CHANGELOG?

Type of Change

[ ] Examples / docs / tutorials / contributors update
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Improvement (non-breaking change which improves an existing feature)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Proposed Changes
Fix warning:
/usr/local/lib/python3.8/dist-packages/etna/core/mixins.py:25: UserWarning: You haven't set all parameters inside class __init__ method: 'order'

Related Issue

Closing issues

Codecov Report

Merging #661 (9d404ce) into master (290cb3c) will decrease coverage by 31.53%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           master     #661       +/-   ##
===========================================
- Coverage   83.80%   52.27%   -31.54%
===========================================
  Files         119      119
  Lines        6398     6399        +1
===========================================
- Hits         5362     3345     -2017
- Misses       1036     3054     +2018

Impacted Files
Coverage Δ

etna/transforms/timestamp/fourier.py
28.00% <0.00%> (-72.00%)
:arrow_down:

etna/commands/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

etna/commands/backtest_command.py
0.00% <0.00%> (-96.43%)
:arrow_down:

etna/commands/forecast_command.py
0.00% <0.00%> (-93.94%)
:arrow_down:

etna/commands/__main__.py
0.00% <0.00%> (-87.50%)
:arrow_down:

etna/commands/resolvers.py
0.00% <0.00%> (-80.00%)
:arrow_down:

etna/analysis/outliers/density_outliers.py
22.44% <0.00%> (-75.52%)
:arrow_down:

etna/datasets/datasets_generation.py
27.02% <0.00%> (-72.98%)
:arrow_down:

etna/transforms/timestamp/time_flags.py
27.02% <0.00%> (-72.98%)
:arrow_down:

... and 69 more

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


feat(ol-geom-circle): new geometry function

Description

This new geometry function incorporates one of the features in OpenLayers, building upon existing geometry functions.
Some indentation was changed cause the use of eslint making the code easier to read, in case it does not bothers you
Motivation and Context

As I was working to create a complex geometry based on coordinates from the map, I searched through the documentation and realized that OpenLayers had a function that was missing in Vue3 OpenLayers.
How Has This Been Tested?

Based on the other geometry functions, I displayed the feature just running the code.
Screenshots (if appropriate):
Types of Changes

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

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

@Filipe-Goulart we recently integrated the docs in this repository. Would you mind to rebase your changes and add the new circle geom to the docs?

@Filipe-Goulart can you also please add the documentation where missing:

[ ] Create a src/demos/CircleDemo.vue
[ ] Create a docs/componentsguide/geometries/geomcircle/index.md containing the Demo and documentation
[ ] Add the docs page to docs/.vitepress/config.ts
[ ] Update the sitemap docs/public/sitemap.xml

@Filipe-Goulart I cherry-picked your commit and added my requested changes (https://github.com/MelihAltintas/vue3-openlayers/pull/183). I will close this PR as it is obsolete now.
Thanks for your effort.


CXXFLAGS in Makefile is not used

CXXFLAGS and LDFLAGS are defined twice in the makefile, and CXXFLAGS should be used for the .o targets, but it's missing.
https://github.com/SegmentLinking/TrackLooper/blob/ad8ed39d7a701ce505363352f2b406c82d3744a6/Makefile#L13-L17

Apart from that, it seems to me like there are outdated things like the bin/doAnalysis target.


Add cachebusting fingerprints to asset files.

docs.css had to be moved out of /static because the static datasource
treats all files as binary, and thus no textual filters can be applied
(necessary for rewriting the jumbotron background image URL).
Fixes https://github.com/prometheus/docs/issues/369

@grobie

:+1: if it works.

Well, it works locally - let's give this a try ;)


Consider restoring the focus on "string means string" and @Nullable __ as a union type in docs

Preface: a user's first model of JSpecify nullness can be as simple as "extra information about nullness gets to ride along wherever types go, and checkers can enforce various rules using that data". But by the time they are trying to annotate complex APIs themselves, they will need a deeper model that helps them think more like a checker does.
To that end, the current javadocs talk about "augmented types" forming an overlay type system, and how String becomes a subtype of @Nullable String, etc.
But there is a more fundamental underlying model, which we were feeling good about as a design center, yet which I wound up making no mention of in the current javadocs or even FAQ. (The user guide gets at it a bit.)

A reasonable model of what the Java language does re: null is that it automatically grafts the null type onto every potentially-nullable type usage. (That "graft" is a lenient union type, which leniently allows null to be assigned, yet leniently allows expressions of the type to be dereferenced too; result: rampant NPEs.)
A reasonable model for what null-marked code does is that it simulates making Java not do that anymore. The type of null is simply "the null type" and nothing else, not "it's a magic value that target-types to whatever reference type you want".
Ergo, "String means a real actual string" (abbreviated "string means string").
@Nullable __ is a union type between __ and the null type. (Java has never had union types before, but they are not complex; something has type A|B if it either has type A or type B; it has only the operations found on their common supertypes.)
That works the same whatever the __ is, including type variables. "Nullable projection" isn't a special concept, just a way to describe the natural implications on type variables.
@Nullable __ is still a supertype of __, which we do state in current docs, but now it's just the direct consequence of being a union type.
A slight complication is @NonNull T, which should probably be seen as a way to "undo" any union-null-type that might have happened in T. (Technically it's a difference type, but it's much less complex than a generalized difference type would be.)

So the questions of this issue:

Do we think that is the right model to expose users to?
Where should it be taught?
How should the Javadoc incorporate it, without taking on the burden of actually "teaching" it?

I think there are several good consequences for how we talk about type variables. One was already mentioned: @Nullable T isn't really special compared to @Nullable String. Here's another.
In base Java, why can we assign null to a type-variable type T? There are two reasonable explanations:

Because Java "grafts" the null type onto every reference type, and that includes T.
Because the values that should be assignable to T (that don't already have type T) are logically the intersection of the value sets of every type T can range over; since all those types automatically include null, the intersection does too.

But the model proposed blows both of those away. In null-marked code, T does not include null, and the intersection of those value sets is empty. It wasn't empty before only because you weren't allowed to have non-nullable reference types.
That leaves us with the expectation that we can't assign null to T in null-marked code, which is correct!
The model also explains why we can assign null to @Nullable T: because that is no longer a type-variable type, but a union type between that type-variable type and the null type.
And we can understand all this without needing to appeal to "parametric nullness, a very special kind of nullness".

Don't union types already exist in the form of multi-catch clauses?

@Nullable __ is still a supertype of __, which we do state in current docs, but now it's just the direct consequence of being a union type.

Hmm. I am slightly surprised by this statement. Does "X is a supertype of Y" mean anything more specific than "all values of Y are also X"? Is X | Z also a supertype of X? What about X | Y | Z? Does every type therefore have an infinite number of supertypes?
Is there an alternative where we keep "supertype" to mean what the JLS defines it as, as a relation among what we're calling base types (or the reference-type subset of those), and to treat the nullness augmentation as union or subtraction types? So that in nullness-augmented world, String means string, @Nullable String means string + null, and @NonNull T means T - null—but there is no "supertype" relation among those, just a containment relation.
Or am I making a distinction without a difference? Do we use the word "supertype" to just mean assignment-compatible?

What I believe: for Sub to be a subtype of Super, it is enough to know that every value having type Sub must always also have type Super; i.e. valueset(Sub) ⊆ valueset(Super). That's enough that we get to call conversion from A to B "widening", and I think that's kinda what it's all about. I think this is the simplest concept of subtyping and that simplest is best.
(The "soft" requirement for subtyping is that Sub ought to have some additional interesting operation or characteristic that Super doesn't; that's beside the point but I didn't want to leave it out.)
FYI, Comparator<? super Foo> is an existing example of a base type with infinite supertypes.

Don't union types already exist in the form of multi-catch clauses?

You just get the least upper bound of those types. We could attempt that here, but we'd have to declare that the type of null is @Nullable Object, and then it's a circular definition. No help, I think.

FYI, Comparator<? super Foo> is an existing example of a base type with infinite supertypes.

As I read JLS 4.5.1, Comparator<? super Foo> is contained by an infinite number of types (is it? only Comparator<? super X> where X <: T and ? and ? extends Object); it does not have that number of supertypes.
Again, I may be pursuing a distinction without a difference.

(The "soft" requirement for subtyping is that Sub ought to have some additional interesting operation or characteristic that Super doesn't; that's beside the point here but I didn't want to not mention it.)

I feel like most definitions of subtyping (including Java's) treat it as reflexive (cf. "proper" subtype), so you're right.

Tangent:

I feel like most definitions of subtyping (including Java's) treat it as reflexive (cf. "proper" subtype), so you're right.

I think all that argues is that I just accidentally left out the word "proper".

Tangent:

As I read JLS 4.5.1, Comparator<? super Foo> is contained by an infinite number of types (is it? only Comparator<? super X> where X <: T and ? and ? extends Object); it does not have that number of supertypes.

As I read it, containment is a relation among type arguments per se. The type argument Foo is contained by ? super Foo is contained by ? super SubFoo is contained by ?.

I'm still hoping for engagement with the main topic.

I'm happy with the main idea, but I'm not sure how that would manifest in changes to the Javadoc or other docs. Maybe prepare a PR?

That will be enough work that I'll wait for more consent, which I can get at the next meeting if not before.

I might be a good guinea pig representative of how a user without existing depth knowledge of the Java type system as described by the JLS might respond (I know a bit about it, but I have not ingrained it into my psyche by any means).
I'm going to respond to (1.) first, since I do have some thoughts on it, then I'll tackle (2.) and (3.) later in separate comments.

Do we think that is the right model to expose users to?

Here's how I understand the model as described in the issue (lmk if it's a poor understanding):

In vanilla Java, null is a special type, of one value, that's "grafted" onto all other reference types in Java. We can dereference values of proper reference types Foo but we can also dereference values of the special null type. The dereference of the special null type is always an NPE.
The null-aware model has one diff from the vanilla Java model: it denudes the null type of its special status. Now, Foo has no graft. It is just Foo. This lets us say a string is a string instead of a string is a string (or possibly null).
@Nullable Foo essentially has the effect of forming a union type of Foo and null. Roughly speaking, it gets us back into vanilla Java land, but now this is a distinct type, instead of being silently a synonym for just Foo.  It only supports the operations on their common supertypes.

Overall, it seems fairly clear. But it does raise some questions/thoughts for me, which are mostly intended to spark potential further refinement/thinking and not strong arguments for adopting a different model, per se.
Re: (1.) -- the grafting metaphor is not how I (naively) think about reference types in general (across languages). I see null as in the value set of one sumtype type called Reference<T> which is a higher-kinded type, taking a T.  The sumtype Reference<> has two constructors: null and it(t) -- in other words it is a tagged union (sum type), one constructor of the type has an inhabitant of the parameterized type T, the other has no inhabitant. Thus, the operation dereference is defined not on two types Foo and the special null, but on one type Reference<T> and its result is dependent upon the value of the reference at run time which is dependent on which branch of the sum type we used (either constructed a valid reference or gave a null). In pseudo ML you'd have something like:
data Reference T
  = Null
  | Reference T

dereference :: Reference T -> T
dereference Null = throw NPE
dereference (Reference x) = x

In other words, the magic, in my view, is not the grafting of null into the value set of References, but rather the grafting of the exception type into the value set of T. In other terms, dereferencing is a partial function, not a total function, and that's why it's problematic.
This perspective is I think a little closer to the working model a programmer might have, as the JLS calls out:

In practice, the programmer can ignore the null type and just pretend that null is merely a special literal that can be of any reference type.

That said, I don't think this means we shouldn't "pull back the curtain" a bit and explain the null type. It might be necessary to give tool owners a better understanding. What we might want to do though, is be very particular about when/where we delve into this detail, I feel in most cases we might be better off avoiding talk of the "null type" as it pertains to vanilla Java altogether, and avoiding metaphors like grafting. The simplification and smaller ontology of: "all references have null as a possible value" is simpler imo and reduces to the same semantics since the null type admits of no operations that aren't already admitted by the reference type. In fact, because the null type is cannot be represented directly in the syntax of the language itself, it effectively has no ontological status at the level of a Java program.
Given what I just said about (1.) I would couch (2.) in slightly different terms. I think we could state the same thing as (2.) as: "a null-aware model removes null from the value set of Reference types". I think "a string is a string" is a wonderful way of expressing this, but I also worry that it would confuse some users. It has the appearance of a tautology even outside of this context, and you won't understand what it's trying to say unless you grok the whole problematic (i.e. if you know that the tautology is not actually a tautology under normal type system conditions (you have a robust mental model of type systems and Java's type system in particular). Contrarily, I find "A String is never null" or the more general An instance of any class is never null to be quite explicit and quite clear.
We could present a null-values table:

Reference Type
Null Values Allowed?

Class (e.g. Foo)
No

Array[]
No

Type Variable
No

@Nullable __
Yes

@NonNull __
No

Re: (3.) I think there is one minor issue with talking about union types, namely that the null type, even in the null aware model is still not expressible in the language. We can only ever introduce it in a union (just like vanilla Java implicitly does); it's a huge benefit that that introduction is now explicit @Nullable, but we still cannot express the null type in isolation nor can we construct a value of the null type on its lonesome (e.g. Null foo = null). So, while it is a type union, it's still a special kind of type union where one element in the union is a non-denotable type. Since this type is non-denotable, it may not make sense to talk about things in terms of a more general type union mechanism, which we don't have.
At the same time, talking about things in terms of union types might be the simplest explanation, even when one of the types is non-denotable.
An alternative picture would use a type-universe perspective, which is how Kotlin describes their nullable system. Instead of describing @Nullable __ as denoting the union type of __ and the non-denotable Null in the same type universe, we could describe @Nullable __ as moving __ into the nullable universe and @NonNull __ as moving __ out of the nullable universe. This also simplifies the explanation of supertypes between the nullable and nonnull universes. Subtypes in either universe may be passed for a nullable supertype. Only nonull subtypes may be passed for a nonnull supertype.
The benefit to the universe approach, imo is that @Nullable and @NonNull seem to be more like special operations than unions since they are a special union with a non-denotable type. I think the description in terms of universes better reflects the non-denotability aspect of the null type. I think it better suggests a difference in kind, rather than a difference in degree (we are moving between systems, not forming a new construct in the same system). Additionally, should Java ever get proper union types, we don't need to go back and hedge all our explanations with "this is a special sort of union type over the non-denotable Null" or explain why the syntax for a normal union is Foo|Bar but for a union with Null it's @Nullable Foo|Bar--the concepts instead remain distinct (though this seems highly unlikely/irrelevant).
I don't feel particularly strongly about this. I do think the union-types explanation is also quite straightforward and workable, just food for thought in case it sparks something.

I might be a good guinea pig representative of how a user without existing depth knowledge of the Java type system as described by the JLS might respond (I know a bit about it, but I have not ingrained it into my psyche by any means).

On the other hand, you also have far more understanding of type theory, and that might even be a distinct audience.

Shallow but serviceable for the general public: types work exactly as always, but an extra bit gets to ride along in a sidecar: "btw, can this be null?". Tools use that information to make smart decisions about where bugs could creep in.
For the more deeply interested, but still accessible to most: refresher on how types work, now imagine Java "grafting" on null to everything, we're simulating making it not do that, letting you ask for it.
For the type theorist,  :-)

This issue is about the middle one.

Here's how I understand the model as described in the issue (lmk if it's a poor understanding):

Perfecto

In other words, the magic, in my view, is not the grafting of null into the value set of References, but rather the grafting of the exception type into the value set of T. In other terms, dereferencing is a partial function, not a total function, and that's why it's problematic.

I'm not picking up on the distinction. It seems to amount to the same thing. To get compile-time safety we turn partial functions into total functions on the more specific types that actually support them, right? But of course to do that we have to actually differentiate the types, and I think that's all I'm attempting to do here?

This perspective is I think a little closer to the working model a programmer might have, as the JLS calls out:

In practice, the programmer can ignore the null type and just pretend that null is merely a special literal that can be of any reference type.

That's a bit odd: beyond the literal being special, null is a value that gets to belong to every reference type, period. Not sure why it doesn't say it that way, but that is the view you get from the JLS, and my proposed model is saying "imagine we throw that out". It does mean we have to talk about the null type per se. That doesn't worry me.

I feel in most cases we might be better off avoiding talk of the "null type" as it pertains to vanilla Java altogether, and avoiding metaphors like grafting. The simplification and smaller ontology of: "all references have null as a possible value" is simpler imo and reduces to the same semantics since the null type admits of no operations that aren't already admitted by the reference type.

I'm lost here. I would have said that, no matter what explanatory model, we certainly want @NonNull Object o; to be seen as a reference that does not have null as a possible value (equivalently, @NonNull Object to be seen as a reference type that does not include null in its value set) ... no?
Perhaps what you're getting at is the idea that first Object includes null, then @NonNull takes it back out. But that seems quite circuitous to me. First we need the notion of a difference type or refinement type (restriction type?). Then we need to think of null as actually supporting dereferencing, as you say (it supports it just fine by throwing NPE!) It seems way cleaner to view the null type as not having dereferenceability in the first place (and null as not being a reference!). Dereferenceability belongs to Object.

We could present a null-values table:
Reference Type	Null Values Allowed?
Class (e.g. Foo)	No
Array[]	No
Type Variable	No
@Nullable __	Yes
@NonNull __	No

We would say "includes null" and avoid "allows". Note that following #275 the answer for Type Variable would be "Yes iff nullable-bounded".

Re: (3.) I think there is one minor issue with talking about union types, namely that the null type, even in the null aware model is still not expressible in the language...

I just haven't thought of this as a problem. Anonymous class types are also non-denotable, but they feel just as real. I think the null type would be denotable if we had any use for denoting it.

At the same time, talking about things in terms of union types might be the simplest explanation, even when one of the types is non-denotable.
An alternative picture would use a type-universe perspective, which is how Kotlin describes their nullable system. Instead of describing @Nullable __ as denoting the union type of __ and the non-denotable Null in the same type universe, we could describe @Nullable __ as moving __ into the nullable universe and @NonNull __ as moving __ out of the nullable universe. This also simplifies the explanation of supertypes between the nullable and nonnull universes. Subtypes in either universe may be passed for a nullable supertype. Only nonull subtypes may be passed for a nonnull supertype.

This isn't far from how I expect people to think at the first of the three rungs (way up there). But to me this has very little explanatory power. A little more like it's just defined to be that way arbitrarily because that happens to "work out".
I think that for the price of having to face up to "null type" and "union type", we get a lot -- a lot of things become natural consequences -- but, that is indeed what this issue is here to question.

Additionally, should Java ever get proper union types,

It seems farfetched that it would do this, or that if it did it wouldn't make sure nullness is handled that way (Foo|Null etc., like I think scala and typescript do).

From another issue:

I think #274 does lead to that conclusion [can't assign null to a type variable], but it doesn't contain a pithy explanation.

Well, my first self-reply offered two for consideration. One follows the interpretation of type variables you favored in #275 just now, but it's not pithy so I'm restating the other one:
You can only assign to T something that has the type T. In plain Java, null does have the type T, because T is a reference type and every reference type gets null added to its value set. But that is what we are undoing. There is no longer any value that can belongs to all the types a type variable might range over.
Is it pithy?

You state there that "String means actual string", and then talk about @Nullable ___ and @NonNull ___ working the same whether ___ is a type variable or not.

Sadly, @Nullable only. @NonNull is a strange animal, which is part of why we resisted including it.

And in the second comment, you state "T does not include null" but later suggest that that only refers to the fact that you cannot assign literal null to them.

Well, "T does not include null" was just a slip-up. If T is nullable-bounded then it includes null, because you could read null from it. I meant that it is not getting null added on automatically, the way Java likes to do.
The reason this starts to seem like it is specifically about the null literal is that any other expression has a usable type, which we need to check for assignability to T anyway, and then that seems to take care of everything. That wasn't clear in my head at first.

@scolsen said:

Overall, it seems fairly clear. But it does raise some questions/thoughts for me, which are mostly intended to spark potential further refinement/thinking and not strong arguments for adopting a different model, per se.

Sparking achieved! I do still feel good about writing up the original basic idea; your comments will help me explain it better.

In a rare move I'm going to stop considering this issue as just a "make-a-decision" issue, and make it about actually doing the doc changes. :-)

@kevinb9n sgtm! Thanks for your thorough responses, we can work out the perspectives a bit more through documentation work, I think. It seems to me that the biggest hurdles here are hitting the right balance of ease of understanding, accuracy/correctness, and explanatory power. I like your idea of carving out a few distinct audiences; we'll want to optimize different parameters for different audience sets (and different delivery mechanisms (e.g. site v. javadoc)).


Support BigDecimal raw value forward index; Support BigDecimal in many transforms and operators

Support BigDecimal raw value forward index

No dictionary group by
No dictionary distinct only, distinct w/ order by
etc.

Support BIG_DECIMAL in:

CASE statement.
CAST transform.
Groovy transform.
Addition, Subtraction, Multiplication, and Division.
abs(), ceil(), and floor() math functions.
Greatest transform.
Least transform.
EQUAL, NOT_EQUAL, IN, NOT_IN, RANGE predicates.
NoDictionary based EQUAL, NOT_EQUAL and IN predicates.
Binary operators (=, !=, >=, >, <=, <).

~18 unit tests
Document the reason for choosing specific data structures for BigDecimal (TreeSet vs. HashSet)

feature, release-notes

Codecov Report

Merging #8622 (413de90) into master (b5690a7) will decrease coverage by 3.88%.
The diff coverage is 72.72%.

@@             Coverage Diff              @@
##             master    #8622      +/-   ##
============================================
- Coverage     70.47%   66.58%   -3.89%
+ Complexity     4313     4298      -15
============================================
  Files          1703     1294     -409
  Lines         89569    65774   -23795
  Branches      13564    10312    -3252
============================================
- Hits          63123    43798   -19325
+ Misses        21990    18799    -3191
+ Partials       4456     3177    -1279

Flag
Coverage Δ

integration1
?

integration2
?

unittests1
66.58% <72.72%> (+0.13%)
:arrow_up:

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...edicate/BaseDictionaryBasedPredicateEvaluator.java
48.14% <0.00%> (-1.86%)
:arrow_down:

...predicate/BaseRawValueBasedPredicateEvaluator.java
85.29% <0.00%> (-1.28%)
:arrow_down:

.../core/query/reduce/filter/PredicateRowMatcher.java
76.47% <0.00%> (-4.78%)
:arrow_down:

...riter/impl/FixedByteChunkSVForwardIndexWriter.java
84.84% <0.00%> (-11.71%)
:arrow_down:

...riter/impl/VarByteChunkSVForwardIndexWriterV4.java
95.12% <0.00%> (-1.58%)
:arrow_down:

...e/impl/forward/FixedByteSVMutableForwardIndex.java
93.87% <0.00%> (-2.97%)
:arrow_down:

...ime/impl/forward/VarByteSVMutableForwardIndex.java
72.72% <0.00%> (-3.47%)
:arrow_down:

...ment/creator/impl/DefaultIndexCreatorProvider.java
68.83% <ø> (ø)

.../impl/fwd/SingleValueFixedByteRawIndexCreator.java
82.60% <0.00%> (-7.87%)
:arrow_down:

...rs/forward/VarByteChunkSVForwardIndexReaderV4.java
91.07% <0.00%> (-0.83%)
:arrow_down:

... and 693 more

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 b5690a7...413de90. Read the comment docs.


feat: compile noir contracts with noir_wasm

This PR adds support for compiling contracts with noir_wasm instead of nargo.
Fix #2644
Requires:

[x] #2728
[x] noir-lang/noir#3036
[x] noir-lang/noir#3049
[x] noir-lang/noir#3091
[x] noir-lang/noir#3213
[x] updates to noir-contracts to add pub modifiers to return types (TBD)
e.g. getThisAddress() -> pub Field here https://github.com/AztecProtocol/aztec-packages/blob/4881414ceb30590674c244ef9bc4c8416eacd6bc/yarn-project/noir-contracts/src/contracts/test_contract/src/main.nr#L45
[x] build noir_wasm with aztec feature enabled (based on noir-lang/noir#3049)
[x] output compilation errors (based on noir-lang/noir#3091)

Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[x] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[x] Every change is related to the PR description.
[x] I have linked this pull request to relevant issues (if any exist).

Running the compiler on this branch is not going to work until a newer version of noir_wasm is published on npm

I'm investigating why 4 end to end tests are currently failing with Failed to solve brillig function, reason: explicit trap hit in brillig.

Benchmark results
Metrics with a significant change:

note_history_successful_decrypting_time_in_ms (5): 1,447 (-24%)
note_history_successful_decrypting_time_in_ms (10): 2,787 (-25%)
l2_block_building_time_in_ms (8): 17,668 (+21%)
l2_block_building_time_in_ms (32): 69,354 (+20%)
l2_block_building_time_in_ms (128): 274,358 (+19%)
l2_block_rollup_simulation_time_in_ms (8): 16,104 (+21%)
l2_block_rollup_simulation_time_in_ms (32): 63,047 (+20%)
l2_block_rollup_simulation_time_in_ms (128): 249,433 (+19%)
l2_block_public_tx_process_time_in_ms (8): 1,513 (+18%)
l2_block_public_tx_process_time_in_ms (32): 6,153 (+21%)
l2_block_public_tx_process_time_in_ms (128): 24,078 (+18%)
l2_block_processing_time_in_ms (8): 2,780 (+21%)
l2_block_processing_time_in_ms (128): 40,037 (+17%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit df389b5f and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
222,984
868,280
3,449,564

l1_rollup_execution_gas
842,071
3,595,388
22,204,933

l2_block_processing_time_in_ms
:warning: 2,780 (+21%)
9,974 (+14%)
:warning: 40,037 (+17%)

note_successful_decrypting_time_in_ms
263 (-9%)
729 (-10%)
2,616 (-11%)

note_trial_decrypting_time_in_ms
65.0 (-28%)
38.0
145 (+6%)

l2_block_building_time_in_ms
:warning: 17,668 (+21%)
:warning: 69,354 (+20%)
:warning: 274,358 (+19%)

l2_block_rollup_simulation_time_in_ms
:warning: 16,104 (+21%)
:warning: 63,047 (+20%)
:warning: 249,433 (+19%)

l2_block_public_tx_process_time_in_ms
:warning: 1,513 (+18%)
:warning: 6,153 (+21%)
:warning: 24,078 (+18%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
25,065 (+1%)
49,152 (+1%)

note_history_successful_decrypting_time_in_ms
:warning: 1,447 (-24%)
:warning: 2,787 (-25%)

note_history_trial_decrypting_time_in_ms
123 (+1%)
145 (-1%)

node_database_size_in_bytes
1,631,004
1,098,453

pxe_database_size_in_bytes
27,188
54,187

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
89.1 (+8%)
61,697
18,841

private-kernel-ordering
54.5 (+8%)
24,233
8,089

base-rollup
2,246 (+8%)
656,309
811

root-rollup
97.9 (+9%)
4,072
1,097

private-kernel-inner
64.0 (+9%)
81,504
18,841

public-kernel-private-input
50.5 (+9%)
41,455
18,841

public-kernel-non-first-iteration
31.5 (+10%)
41,497
18,841

merge-rollup
1.01 (+27%)
2,592
873

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

 It is not the default
Nargo compilation of noir-contracts was restored
noir-version.json was restored (for the above compilation step)
e2e error message expectation restored as before

I've done this because noir_wasm doesn't output debug information yet so it would make fixing issues in contracts difficult. The wasm compiler can still be used if needed (will be used in dockerized aztec-cli, see #3031).
Plan going forward:

[ ] get noir_wasm to output debug information
[ ] build noir-contracts with noir_wasm instead of nargo
[ ] make --compiler wasm the default option
[ ] keep --compiler nargo around for users that want/need it
[ ] use consistent nargo/noir_wasm version number so that we might switch between them easily (one uses build numbers e.g. aztec.1, aztec.2 and the other hashes e.g. aztec.abcdef)


Ref($close,0)取出的数据不对

🐛 Bug Description
Ref参数取0的时候每个日期都取的第一个数据

如下（我的日历从2004-12-31开始）
In [10]: D.features(['SH600000'], ['$close'])
Out[10]:
$close
instrument datetime
SH600000   2004-12-31   10.904439
2005-01-04   10.717505
2005-01-05   10.546150
2005-01-06   10.405951
2005-01-07   10.437106
...                           ...
2020-12-25  128.427292
2020-12-28  128.293243
2020-12-29  127.757004
2020-12-30  127.354836
2020-12-31  129.767868
In [11]: D.features(['SH600000'], ['Ref($close,0)'])
Out[11]:
Ref($close,0)
instrument datetime
SH600000   2004-12-31      10.904439
2005-01-04      10.904439
2005-01-05      10.904439
2005-01-06      10.904439
2005-01-07      10.904439
...                              ...
2020-12-25      10.904439
2020-12-28      10.904439
2020-12-29      10.904439
2020-12-30      10.904439
2020-12-31      10.904439
To Reproduce
Steps to reproduce the behavior:

Expected Behavior

Screenshot

Environment
Note: User could run cd scripts && python collect_info.py all under project directory to get system information
and paste them here directly.

Qlib version:
Python version:
OS (Windows, Linux, MacOS):
Commit number (optional, please provide it if you are using the dev version):

Additional Notes

I think you can find the answer here: https://qlib.readthedocs.io/en/latest/reference/api.html#qlib.data.ops.Ref

I think you can find the answer here: https://qlib.readthedocs.io/en/latest/reference/api.html#qlib.data.ops.Ref

thx

thx


Fix typo

/csharp/i -> C#

@changeworld : Thanks for your contribution! The author(s) have been notified to review your proposed change.


debugging to log

Also try and log some metrics
date/time
source ip
browser used
graph direction
File size


On macOS 15, tmux can't run nord.tmux even it has a shebang (e.g. #!/usr/bin/env bash or #!/opt/homebrew/bin/bash). Why?


Property's xml documentation not used when the property references a custom C# type

Version of Swashbuckle.AspNetCore: 6.1.5
Issue: Following StackOverlfow (not filed by me) issue describes the same issue that I am seeing in my scenario too.
https://stackoverflow.com/questions/65238148/asp-net-core-generated-swagger-descriptions-missing-on-object-attributes
Expected: The documentation for ExampleValue2 property should be present in the generated swagger document. i.e "description": "ExampleValue description." should be present.
Actual: This information is currently missing.

See https://github.com/OAI/OpenAPI-Specification/issues/1514 - the OpenApi spec does not allow sibling elements for $ref.
A workaround is to use the allOf operator.
var schemaGenerator = new SchemaGenerator(
    new SchemaGeneratorOptions
    {
         UseAllOfToExtendReferenceSchemas = true,
    }, ...);


Why ! sign is used in for loop ? while printing the message numTimes.

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 788d46c9-a91a-2788-8db7-b53c37b512f2
Version Independent ID: 00c2c01d-d235-2d2d-5c96-1f33a9314382
Content: Part 3, add a view to an ASP.NET Core MVC app
Content Source: aspnetcore/tutorials/first-mvc-app/adding-view.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Hi @iamzm. The ! in this context is the ! (null-forgiving) operator. The compiler thinks that ViewData["NumTimes"] could return a null value, so we use the ! to assert that it won't be null. We ensure a value gets set in the Welcome action.

If we get more questions on !, we should document it. It's not easy to search on  !


Your wallet is ready shows duplicated on 1.0.3b Mac

Same for HTC 10 5.2 inch 2560x1440
Android 7.0

fixed


Update zh translation in basic-stateful-set.md

Update zh translation in basic-stateful-set.md

/lgtm
/approve


licenseKey is required for fullPage.js

Fullpage.js version 3 has changed its license to GPLv3 and it requires a licenseKey option. Read about it here:
https://github.com/alvarotrigo/fullPage.js#options

Will not be fixed as old portfolio is in the process of being deprecated.
Please see https://kendlbat.dev/beta for a preview of the replacement.


Orion Miniconda module permission issue

@climbfuji I can't access your Miniconda on Orion, could you fix the permission?
Orion-login-4[82] gkyle$ ls /work/noaa/da/jedipara/spack-stack/
ls: cannot open directory /work/noaa/da/jedipara/spack-stack/: Permission denied

Sorry about that. Can you please try again?

On Jun 7, 2022, at 9:41 PM, Kyle Gerheiser @.***> wrote:
@climbfuji https://github.com/climbfuji I can't access your Miniconda on Orion, could you fix the permission?
Orion-login-4[82] gkyle$ ls ls /work/noaa/da/jedipara/spack-stack/
ls: cannot access ls: No such file or directory
ls: cannot open directory /work/noaa/da/jedipara/spack-stack/: Permission denied
—
Reply to this email directly, view it on GitHub https://github.com/NOAA-EMC/spack-stack/issues/187, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB5C2RM77FOIGKYBAI4GK7TVOAI55ANCNFSM5YFAZKTA.
You are receiving this because you were mentioned.

@kgerheiser Can you confirm that the permissions are now correct?


New spec design: table rows are hard to distinguish

Affects the redesign table rows and columns are pretty hard to distinguish imo, for several reasons:
On my monitor, the row colors are barely distinguishable:

On my monitor in daylight, I can't really distinguish those 2 rows well. This probably is also an accessibility issue for people with bad eyesight, that need high contrast.
The table header is not visually part of the table:

Visually the table header is part of the headings, not part of the table, since it shares the bold font, background color and size.
Tables are too "large"
The new spec wastes a lot of vertical space with padding on the left and right as well as horizontally, which makes most tables too big to fit on my screen. Which is why the comparison screenshot is cut off (in the table table section), I simply can't fit that on my screen anymore to compare it, which I think is pretty bad for a spec, that is 90% tables (not actually, but it feels like that sometimes, when you look for specific stuff). Not fitting full tables and maybe even multiple on the screen makes it much easier to miss stuff.
Suggestions to improve legibility

Give table headers a background color to make them part of the table
Maybe add borders around the cells in the table and maybe even the table itself. That way the color is not the primary orientation method. The border should have a very distinguishable color.
Maybe to align the table values? The you could have at least one visual line to orient yourself
Reduce the row distance and font size in tables, as well as make them grow past the padding on the right. The latter is a separate issue though (#3042).

table table

old spec
new spec
MDN, which looks similar to the new spec, but does it better (imo)

(Screenshots taken at same screen size without any zoom)

I can confirm that on one of my monitors the blue background for table separators is lost as well.

On my monitor, the colors are okay, but the table has unnecessary horizontal whitespace, making it harder to read. This also leaves less room for the description text, so that breaks more often:

Funnily enough, on different spec pages tables look like this and are readable imo:


IPAM: add support for ippool

[x] Make sure you have followed Kube-OVN Code Style.

What type of this PR

Feature

Which issue(s) this PR fixes:
Fixes #(issue-number)
WHAT

🤖 Generated by Copilot at 0fa880d
This pull request adds a new IPPool resource type to the kube-ovn API, which represents a pool of IP addresses that can be allocated to pods or other resources. It also refactors the condition types for various resources to use a common Condition type. It updates the controller, the clientset, the informers, the listers, the charts, and the workflow to support the new resource and the refactored types.

🤖 Generated by Copilot at 0fa880d

Oh we are the kube-ovn crew, and we have a job to do
We'll add a new IPPool type, and make the code more tight
Heave away, me hearties, heave away
On the count of three, we'll push the PR and sail the IPAM sea

HOW

🤖 Generated by Copilot at 0fa880d

Increase the timeout-minutes for the build-x86-image workflow to avoid premature cancellation (link)
Add a new IPPool resource type for managing a pool of IP addresses (link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link)
Refactor the condition types for various resources to use a generic Condition type (link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link)
Add a new key mutex field to the Controller type for synchronizing access to the IPPool resources (link)
Initialize the informer, lister, and work queues for the IPPool resources in the Run function of the Controller type (link, link, link)
Use the numKeyLocks constant for the npKeyMutex field of the Controller type (link)
Shut down the work queues for the IPPool resources in the shutdown function of the Controller type (link)
Add worker functions to process the IPPool resources from the work queues in the startWorkers function of the Controller type (link, link)
Initialize the IPAM module with the existing IPPool resources in the InitIPAM function of the Controller type (link)
Use the podNet.Subnet.Name field instead of the pod annotation for the subnet variable in the InitIPAM function of the Controller type (link)

@oilbeater  Please review. Test cases will be added later.


Sensor LYWSD03MMC  multiple Configuration

Updated from v2.0-alpha.4 to v2.0.1  and the following error is repeated 4 times for EACH ble LYWSD03MMC by Xiaomi on EVERY reboot.
2022-02-09 15:22:07 ERROR (MainThread) [homeassistant.components.sensor] Error adding entities for domain sensor with platform xiaomi_gateway3
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 382, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 422, in _async_add_entity
    entity.add_to_platform_start(
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 752, in add_to_platform_start
    raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: Entity sensor.a4c138f30641_temperature cannot be added a second time to an entity platform
2022-02-09 15:22:07 ERROR (MainThread) [homeassistant.components.sensor] Error adding entities for domain sensor with platform xiaomi_gateway3
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 382, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 422, in _async_add_entity
    entity.add_to_platform_start(
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 752, in add_to_platform_start
    raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: Entity sensor.a4c138f30641_humidity cannot be added a second time to an entity platform
2022-02-09 15:22:07 ERROR (MainThread) [homeassistant.components.sensor] Error adding entities for domain sensor with platform xiaomi_gateway3
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 382, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 422, in _async_add_entity
    entity.add_to_platform_start(
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 752, in add_to_platform_start
    raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: Entity sensor.a4c138f30641_battery cannot be added a second time to an entity platform

Check if v2.0.3 helps

Line 761 on v2.0.3.
2022-02-12 21:15:15 ERROR (MainThread) [homeassistant.components.sensor] Error adding entities for domain sensor with platform xiaomi_gateway3 Traceback (most recent call last):   File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 382, in async_add_entities     await asyncio.gather(*tasks)   File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 422, in _async_add_entity     entity.add_to_platform_start(   File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 761, in add_to_platform_start     raise HomeAssistantError( homeassistant.exceptions.HomeAssistantError: Entity sensor.temperature_work_room_e_temperature cannot be added a second time to an entity platform 2022-02-12 21:15:15 ERROR (MainThread) [homeassistant.components.sensor] Error adding entities for domain sensor with platform xiaomi_gateway3 (...)

How many gateway do you have?

I have two gateways (ZNDMWG03LM) on v1.5.0_0102 firmware.

I have 3 gateways (ZNDMWG03LM) 2 are on 1.4.7_0115 and 1 is on 1.5.0_0102 firmware.

LYWSD03MMC sensor is unavailable with integration version v2.0.3 and gateway ZNDMWG03LM firmware v1.5.0_0102. I have one gateway and one LYWSD03MMC sensor only

I have 10 LYWSD03MMC sensors all visible and working on 3 ZNDMWG03LM gateways (2 firmware v1.4.7_0115 and 1 v1.5.0_0102) with integration  v2.0.3.

Fixed on 2.0.4. :) Thx!

All good.


Can we get the relative distance of all cells?

Hi,
Thank you for this great package!
I wonder if we could get the relative distance of all cells. If I understand correctly, novoSpaRc returns the expression data on spatial locations, and it may calculate the "physical distance" between cells.
How can we get this information?
Sorry if my question is too naive or due to my ignorance.
Many thanks!
Yiwei Niu

Hi, can you please explain in more detail what you mean by "relative distance of all cells"? novoSpaRc will map the cells spatially and provide the spatial DGE matrix. The "physical distances" between the mapped locations are given, as you provide the target space for the reconstruction.

Thank you for your reply!
Sorry I did not make myself clear. I mean, for example, for cell A and cell B, can we get the spatial distance between them?
By viewing the final spatial expression of specific marker genes, I could see cells of group A and cells of group B are close. But it is a visual check, what I want to do is to qualify the distances  between groups of cells, i.e. to compare if the distance between group A and group B is smaller than that of group A and group C.
Hope that I did not misunderstand the purpose of novosparc.

Hi, we currently don't have a function that does this, but you can compute it on your own by using the geometrical locations and the final sdge produced with novosparc.


Add healthcheck Agent Lifecycle Hook that runs between jobs

buildkite-agent has a disconnect-after-idle-timeout setting which causes it to shut down after an idle period.
It would be nice if there was an option to disconnect / shut down the agent if a healthcheck fails. We run an elastic autoscaled pool of agents, and shutting down in the case of a problem would allow the autoscaling group to replace unhealthy agents.
Currently when an agent has its disk fill up for example then all jobs allocated to it will fail, but it will still keep accepting jobs regardless. These often require manual intervention to kill the instance and let the pool recover. Having the agent stop accepting jobs and shut down when available disk space is low would allow them to be replaced with clean agents without manual intervention.

If sent a SIGTERM the agent will stop accepting new work but finish it's current job. I'd be tempted to solve this with a cronjob that checked health of the instance and gracefully terminated the instance and shutdown the instance 🤔

That is a good point. However, one concern I'd have with that is that cronjobs can only run once per minute. An agent could accept and fail a number of jobs before the cronjob gets run. If the agent could run the healthcheck between jobs that wouldn't be a problem.
The cronjob idea might be a reasonable workaround though, if you don't think it's appropriate to add it to the agent.

To clarify a bit, the cronjob solution would work well for a preventative shutdown under normal/predictable use. That's useful but I'm also concerned about builds that create problems very quickly (we have some big builds that do this on a semi-regular basis).
A more general solution might be to add a post-exit hook that runs outside of a job. The hook could then SIGTERM the parent to achieve the result I'm looking for, while being flexible enough to have other uses.

Yeah, post-exit is one I've wanted for quite a while. The other option that we've been pondering is a pre-accept hook that runs before the agent accepts and provides an opportunity to decline accepting the job.

There is now a pre-bootstrap hook introduced by https://github.com/buildkite/agent/pull/1456 . I think it's intended to validate the environment variables, but it could also be used to quickly clean the filesystem before accepting the next job.

Similar scope here, but I see #1363 was closed as a duplicate so I'll mention here.
On completion of an arbitrary job it is possible agent resources (e.g. databases, background services) to be left in a bad state, either through implementation mistakes, timeouts, or errors. These problems are currently dealt with in pipelines as a safeguard against build flakes but this solution is not without problems.

It complicates job logic.
It increases the time required to complete jobs.
In rare cases issues can't be resolved, leading to job failures (and eventually retry logic, complicating things further).
Increases risk of timeouts.

A better way to deal with this would be in a "recovery" phase where the agent can prepare for the next job (if there is one) without increasing agent wait times (since agents in the pool should all be clean and healthy).


Is there a Dockerfile for CPU installation only?

I just need a Docker environment for inferencing on CPU. I've tried using the existing Dockerfile but gotten numerous errors which can be seen in multiple issues reported in this repository such as No module found 'mmcv.ops' etc.

Hi, you might re-install mmcv if you have error message 'No module found 'mmcv.ops' '.


Add python version requirements to setup.py

This is need in the future so we can gracefully remove python 2.7 support.
See #1075.
https://packaging.python.org/guides/dropping-older-python-versions/

The python3 versions that were dropped are because sphinx has already dropped support for them when sphinx 1.6 is removed. We require sphinx 1.6 because it is the first version with experimental HTML5 and needed for some other bug fixes in the theme.


[DNM] Core: remove Python compatibility

Remove the Python module compatibility.  When building on macOS, it
continues to conflict with the Python framework from CPython.

@dan-zheng yeah, I think we want to wait a little while before we merge this.


Make clear that a new job creates a snapshot of the project

As of now it's not really clear in the UI that a snapshot of the project is made when a new job is created.
We should find a way to refer to these snapshots such that it becomes more visible to the user that jobs of a single project are based on different versions of the project directory.
For example, we could list a revision number or hash in the job list. As the current implementation of Orchest doesn't require a separate git commit/branch for job snapshots.

Added in: 9db1ad07771998b217e6c57340b092bc00806b8f


How to enable fxaa in the view component or elsewhere

How to enable fxaa in the view component or elsewhere, please help me.

You can use Fxaa component:
import { Viewer, Fxaa } from "resium";

<Viewer>
  <Fxaa />
</Viewer>

Thank you for your reply.
Just using the above example will also cause this error:
DeveloperError: czm_FXAA has already been added to the collection or does not have a unique name.

I don't know so much about how to use Fxaa. Resium just wraps Cesium, so that error may be due to usage of Cesium.

I found a way to turn it on for cesium:
viewer.scene.postProcessStages.fxaa.enabled = true
viewer.scene.fxaa = true

I tried to use it on resium:
<Viewer>
  <Scene fxaa={true} postProcessStages.fxaa.enabled = {true}>
  </Scene>
</Viewer>

but,postProcessStages.fxaa.enabled = {true} is not allowed.
I have a brief look at the source code. I'm not sure. It seems that scene does not support the "postprocessstages" props.

It seems a bug. I consider fixing fxaa.
Workaround:
const ref = useRef(null);
useEffect(() => {
  const scene = ref.current?.cesiumElement?.viewer.scene;
  if (!scene) return;
  scene.postProcessStages.fxaa.enabled = true;
}, []);

// ...

<Viewer ref={ref}></Viewer>

It seems a bug. I consider fixing fxaa.
Workaround:
const ref = useRef(null);
useEffect(() => {
  const scene = ref.current?.cesiumElement?.viewer.scene;
  if (!scene) return;
  scene.postProcessStages.fxaa.enabled = true;
}, []);

// ...

<Viewer ref={ref}></Viewer>

thanks.
A method I have experimented with is also shared:
const App = () => {   let viewer: any; // This will be raw Cesium's Viewer object.   useEffect(() => {     viewer.scene.postProcessStages.fxaa.enabled = true;   }, []);   return (     <Fragment>       <Viewer           ref={(e) => {             entity = e && e.cesiumElement;           }}      />       </Viewer>     </Fragment> }

thanks.
A method I have experimented with is also shared:
const App = () => {   let viewer: any; // This will be raw Cesium's Viewer object.   useEffect(() => {     viewer.scene.postProcessStages.fxaa.enabled = true;   }, []);   return (     <Fragment>       <Viewer           ref={(e) => {             entity = e && e.cesiumElement;           }}      />       </Viewer>     </Fragment> }

I could not reproduce the bug. It works even when any props are specified to Fxaa component (FXAA was automatically enabled).
If the problem occurs again, reopen the PR.

https://github.com/reearth/resium/blob/main/src/PostProcessStage/PostProcessStage.stories.tsx#L80
https://resium.reearth.io/examples/?path=/story/postprocessstage--fxaa


Improve Contributors.md

Write proper steps to run the app in your local machine.

@Abhijit2505 Please look for this issue and if you find it legitimate award me points for nwoc.

@Vrindagupta6828 I believe the steps are written in the README section already. And we don't regard this as an issue.
Hence closing it.


Rename variables readme.me instructions to fix bug

@mxstbr Here's the requested pull request to change the readme.md

Coverage remained the same at 99.301% when pulling 64d740e37bc24be6b76b992145a50f7c3a3fe738 on heretoinfinity:instructions-edit into<PHONE_NUMBER>2ab2e34162b842fd9b48760d50eba9 on SamyPesse:master.


Helper functions get_text() between 2 anchors and del_chars() from TagUI - to add

This is very useful when extracting text from a chunk of text content, by providing the left anchor and right anchor.
https://github.com/kelaberetiv/TagUI/issues/972#issuecomment-849316512
// retrieve text between 2 provided anchors in given text content
function get_text(source_text, left_marker, right_marker, optional_count) {
    if (!source_text || !left_marker || !right_marker) return '';
    var left_position = source_text.indexOf(left_marker); if (left_position == -1) return '';
    var right_position = source_text.indexOf(right_marker, left_position+1); if (right_position == -1) return '';
    if (optional_count > 1) {var occurrence_count = 2; while(occurrence_count <= optional_count) {occurrence_count++;
            left_position = source_text.indexOf(left_marker, right_position+1); if (left_position == -1) return '';
            right_position = source_text.indexOf(right_marker, left_position+1); if (right_position == -1) return '';}}
    return source_text.slice(left_position + left_marker.length, right_position).trim();}

Consider also adding remove_char() from upstream

After thinking through, better to create the functions within the package instead of routing to TagUI's functions

del_chars() is something as trivial as below, and if multiple characters needed, then loop
text_content.replace('\r', '')

get_text() is something as trivial as below in Python -

text_content.split(start)[1].split(end)[0]

skip adding these 2 functions because trivially easy in Python

This is added in v1.43, available with pip install rpa --upgrade
Usage - https://github.com/tebelorg/RPA-Python#helper-functions


Refine document for new user to submit job

New guidance to submit job.
Refine homepage to connect with new guidance.
Reorganize content of troubleshooting for next refactoring.
Fix some links.

Coverage increased (+4.7%) to 57.337% when pulling c990d56f9717d27b521dde413c86ca83fea9af6f on squirrelsc:first_job into 83b911465ae86e95998678eff5d3f92b193c896c on Microsoft:master.

Coverage increased (+4.7%) to 57.337% when pulling c990d56f9717d27b521dde413c86ca83fea9af6f on squirrelsc:first_job into 83b911465ae86e95998678eff5d3f92b193c896c on Microsoft:master.


Don't scroll on long message. Emulate ChatGPT.

Is your feature request related to a problem? Please describe.
I'm frustrated when a long message is streamed to the UI and screen scrolls down automatically to keep pace with the text but before I have had time to read what's above the fold. I need to scroll back the top again.
Describe the solution you'd like
Don't scroll automatically. Show the user an element to indicate there is more text below the fold and let the user scroll at their own pace. This is how ChatGPT works.
Describe alternatives you've considered
None
Additional context
None. Thanks for listening!

The current implementation is a scroll "dock". If you manually scrolled to the bottom then streamed content will auto scroll. if you "undock" by scrolling up it should not autoscroll anymore.


spotifyd: 0.2.24 -> 0.3.0

Motivation for this change
https://github.com/Spotifyd/spotifyd/releases/tag/v0.3.0
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Seems like removing the changes in #106050 (using an older version of Rust to build) causes the same panics until https://github.com/Spotifyd/spotifyd/issues/719 is resolved.

@bnjmnt4n that panic is now fixed in https://github.com/NixOS/nixpkgs/pull/114309

I just saw this and I am a bit stunned. The comment was removed while the issue wasn't fixed. Has either of you (@marsam, @SuperSandro2000) actually tested this on their setup? Checked the upstream issue if it was fixed in this version?

@andir I'm so sorry. This was a half-automatized update, I forgot to test it thoroughly. I'll be more careful in the future.


Refactor: [WIP] Improve email template design #31150

As asked, bigger font and zulip's font in order to looks cool.
Fixes:  https://github.com/zulip/zulip/issues/31150
I had problems to send emails from the development environment, so its hard to get the screenshots to show to you, but the changes look like this - it's how i tested the result: https://imgur.com/a/how-looks-qv79gl7
It's what i've done 4 now and if needed i can upload the "/docs" - i just dont know where.

Communicate decisions, questions, and potential concerns.

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

There was something about "UPDATE UI" on check boxes but i deleted for accident. Ye, it updates it.

Now it works on Ubuntu 22.xx I had trouble trying to send email templates to myself in order to test it, but i feel will work fine.


Waitress threads 16 -> 64

I wasn't sure whether this is the right branch, but I followed the flow in https://softwiretech.atlassian.net/wiki/spaces/Support/pages/20519190529/GBIS+Help+to+Heat+Development+process
My only change is waitress threads 16 -> 64
The reason behind it is waitress queuing during load testing.
This increase may lead to general slow down, as there are more threads than thread vcores on our compute insteance, but we will find out how much impact this has during load testing

Will do

Oh, for load testing we'll also want to cherry-pick these changes onto prod (main branch). That will probably need a new PR (I believe it's protected).


Natural Language Processing course

"Thanks so much for your interest in Natural Language Processing! Alas, we're writing to tell you that the Natural Language Processing class was listed by mistake, and we weren't even aware it was listed; we are not offering NLP this year. We apologize for the mistake, and we do hope to get back to this course someday, but we have no plans to do so anytime soon. We regret that we won't be able to work with you, but we warmly wish you all the best in your future in Natural Language Processing."
This was the message I received today on my e-mail from Coursera. Since the course will not be offered anytime soon, should probably change it.

Hi andrecsq, I created a pull request addressing your issue.

@andrecsq yes, I'll change it now :smile:


Rework UI

Currently the UI is designed around having the torrents' details in columns. Intention is to rework this such that each torrent will have it's own little table of information that will be laid out in multiple lines.
Torrent title
Size X MB of Y MB (% complete) / Speed / ETA
[++++++++++++-------I am a progress bar-----------]
Buttons will be overlaid on top of the progress bar at the right-hand side.
Progress bar will be coloured according to the status of the torrent (active, paused, seeding, waiting).
Status colours of the progress bar will closely match the colours of the icons in the Deluge WebUI.
Once this work is complete, I'll pretty much consider this extension ready for release on the Chrome Web Store.

I'm happy that commit e5c28c482066cbe8e8b90fd038cdedcb587dd499 fixes this. There are other nitpicky adjustments to be made, but I'll track them in separate issues from here.


Embed PDFs

It would be great if there was a command to embed other PDF files similar to images.
That might even happen without rasterizing the PDF first, so that the PDF commands of the embedded pdf are directly imported into the typst output pdf.
In LaTeX this is possible using the pdfpages package.

Duplicate of #145.


RuntimeError Exception: can't modify frozen String

Hi @robforman - thanks for this great gem!
However, we encountered an issue with mocking an IMAP connection. TCR tries to force the UTF-8 encoding on frozen string which results in a RuntimeError Exception: can't modify frozen String.
Pull request is on the way 👍

very cool- thanks for the addition.

Thanks for your blazing fast response and the new release 💪 Works as expected. Closing now.


Whitelist array() built-in in smarty security

1. Why is this change necessary?
Smarty erroneously treats the PHP array() built-in as a function and applies its PHP function security policy to it (https://github.com/shopware/shopware/blob/9a116f29f78c0005e031e34ffcce919b6a50e3a9/engine/Library/Smarty/sysplugins/smarty_internal_templateparser.php#L2871). This causes template security to prevent array() from being used from templates.
Right now, we work around this for Shopware 5.3 by using array_fill(0, 0, null) within our templates instead of array().
2. What does this change do, exactly?
It adds the array() built-in to Shopware's whitelist of functions that are allowed within smarty templates.
3. Describe each step to reproduce the issue or behaviour.
Call array() from a template (e.g. by doing {assign var=a value=array()}) and try to compile that on Shopware 5.3. Smarty security will throw an Exception.
After applying the patch, remember to clear the cache before testing the fix.
4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
None.
6. Checklist

[ ] I have written tests and verified that they fail without my change
[X] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[X] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-19525.
Please use this issue to track the state of your pull request.

Thank you @fixpunkt for the hint.
We have scheduled this for the next 5.3.1 release. But you can simply use the shorthand syntax to get around this.
{assign var=test value=[]}

Thanks for scheduling and for the suggestion.
Unfortunately, we cannot use the shorthand syntax since this is code that still needs to work on Shopware 4.3. Or is that a smarty built-in?

The syntax depends on the required PHP Version 5.4

Ok, thanks for clarifying. In this case we'll have to stick with array_fill().

thanks again @fixpunkt :+1:


blindness overlay shouldn't be a harsh circle

Description

we have brand new overlays for crit. It should look like that. The current one looks absolutely awful and has no transition either.

is this still a thing i never use blindness

no bhijn made it epicpilled


Panel Not Displaying Any Data

This just started in the past month or so but the panel is no longer displaying any data.  When I click edit or view it does nothing as well.
I tried to delete the panel plugin folder but it still didnt seem to fix it.  Restarted grafana multiple times.  This is the only panel plugin that doesnt seem to be working.
The log indicates it was downloaded and isntalled successfully so I am not really sure what else I can look for to try.
installing grafana-piechart-panel @ 1.3.4
from url: https://grafana.com/api/plugins/grafana-piechart-panel/versions/1.3.4/download
into: /var/lib/grafana/plugins

✔ Installed grafana-piechart-panel successfully

Restart grafana after installing plugins . <service grafana-server restart>

installing natel-influx-admin-panel @ 0.0.5
from url: https://grafana.com/api/plugins/natel-influx-admin-panel/versions/0.0.5/download
into: /var/lib/grafana/plugins

✔ Installed natel-influx-admin-panel successfully

Restart grafana after installing plugins . <service grafana-server restart>

installing ryantxu-ajax-panel @ 0.0.5
from url: https://grafana.com/api/plugins/ryantxu-ajax-panel/versions/0.0.5/download
into: /var/lib/grafana/plugins

✔ Installed ryantxu-ajax-panel successfully

Restart grafana after installing plugins . <service grafana-server restart>

installing natel-discrete-panel @ 0.0.9
from url: https://grafana.com/api/plugins/natel-discrete-panel/versions/0.0.9/download
into: /var/lib/grafana/plugins

✔ Installed natel-discrete-panel successfully

Restart grafana after installing plugins . <service grafana-server restart>

installing natel-plotly-panel @ 0.0.5
from url: https://grafana.com/api/plugins/natel-plotly-panel/versions/0.0.5/download
into: /var/lib/grafana/plugins

✔ Installed natel-plotly-panel successfully

Restart grafana after installing plugins . <service grafana-server restart>

t=2019-01-09T10:02:26-0500 lvl=info msg="Starting Grafana" logger=server version=4.5.2 commit=ec2b0fe compiled=2017-09-22T04:34:03-0400

t=2019-01-09T10:02:26-0500 lvl=info msg="Config loaded from" logger=settings file=/usr/share/grafana/conf/defaults.ini
t=2019-01-09T10:02:26-0500 lvl=info msg="Config loaded from" logger=settings file=/etc/grafana/grafana.ini
t=2019-01-09T10:02:26-0500 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.data=/var/lib/grafana"
t=2019-01-09T10:02:26-0500 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.logs=/var/log/grafana"
t=2019-01-09T10:02:26-0500 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.plugins=/var/lib/grafana/plugins"
t=2019-01-09T10:02:26-0500 lvl=info msg="Config overridden from command line" logger=settings arg="default.log.mode=console"
t=2019-01-09T10:02:26-0500 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SERVER_DOMAIN=<REMOVED>"
t=2019-01-09T10:02:26-0500 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SERVER_ROOT_URL=https://<REMOVED>"
t=2019-01-09T10:02:26-0500 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SESSION_PROVIDER=file"
t=2019-01-09T10:02:26-0500 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_ANALYTICS_REPORTING_ENABLED=false"
t=2019-01-09T10:02:26-0500 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_ANALYTICS_CHECK_FOR_UPDATES=false"
t=2019-01-09T10:02:26-0500 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SECURITY_ADMIN_PASSWORD=*********"
t=2019-01-09T10:02:26-0500 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_USERS_ALLOW_SIGN_UP=false"
t=2019-01-09T10:02:26-0500 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_AUTH_ANONYMOUS_ENABLED=false"
t=2019-01-09T10:02:26-0500 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_AUTH_BASIC_ENABLED=false"
t=2019-01-09T10:02:26-0500 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_AUTH_PROXY_ENABLED=true"
t=2019-01-09T10:02:26-0500 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_AUTH_PROXY_HEADER_NAME=X-WEBAUTH-USERNAME"
t=2019-01-09T10:02:26-0500 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_LOG_LEVEL=debug"
t=2019-01-09T10:02:26-0500 lvl=info msg="Path Home" logger=settings path=/usr/share/grafana
t=2019-01-09T10:02:26-0500 lvl=info msg="Path Data" logger=settings path=/var/lib/grafana
t=2019-01-09T10:02:26-0500 lvl=info msg="Path Logs" logger=settings path=/var/log/grafana
t=2019-01-09T10:02:26-0500 lvl=info msg="Path Plugins" logger=settings path=/var/lib/grafana/plugins
t=2019-01-09T10:02:26-0500 lvl=info msg="Initializing DB" logger=sqlstore dbtype=sqlite3
t=2019-01-09T10:02:26-0500 lvl=info msg="Starting DB migration" logger=migrator

Tried in both ie and Chrome with the same result.

Grafana v4.5.2


Game ends as soon as you start it.

So I wanted to try this out. I have a few tabs open, and then I open up this tab-invaders game. After doing so, it tells me to press space to start the game. And so I do. The game starts for a split second, and then is instantly over, telling me that 0 tabs were destroyed.

Are your tabs pinned?

No.


Specify a message in the git tests

The ancient git version in CentOS 7 (<IP_ADDRESS>) has a but where despite --allow-empty-message it will not accept -m '' so to fix this we set a (boring) message to commit.

Given we don't test on CentOS 7 and it ships an ancient git I am not entirely convinced myself supporting it is worth it, because who knows what else is broken.


feat: add Button with to indicator

The goal is to be able to use it in TAs Configuration tab instead of helpLink
That was requested by @artemrys
Closes #307

Hello @hsekowski-splunk @artemrys
I was investigating the existing code. We can achieve the same result without adding any additional code to the UI.
We already have a wrapper component for the button called StyledButton that we are exporting and (for example) using in the ConfigurationFormView component. If we add openInNewContext and to props, it will behave exactly as we want.
For Example:
<StyledButton
    className="saveBtn"
    appearance="primary"
    label={isSubmitting ? <WaitSpinner /> : _('Save')}
    openInNewContext
    to="https://www.google.com/"
/>

Output:


Fix integration workflows in Github action

Since there are several workflow failures which report as below:

Error: .github#L1
<EMAIL_ADDRESS>is not allowed to be used in apache/shardingsphere-on-cloud. Actions in this workflow must be: within a repository owned by apache, created by GitHub, verified in the GitHub Marketplace, or matching the following: /@[a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9]+, AdoptOpenJDK/install-jdk@, JamesIves/github-pages-deploy-action@5dc1d5a192aeb5ab5b7d5a77b7d36aea4a7f5c92, TobKed/label-when-approved-action@, actions-cool/issues-helper@, actions-rs/, al-cheb/configure-pagefile-action@, amannn/action-semantic-pull-request@, apache/, burrunan/gradle-cache-action@, bytedeco/javacpp-presets/.github/actions/, chromaui/action@, codecov/codecov-action@, conda-incubator/setup-miniconda@, container-tools/kind-action@, container-tools/microshift-action@, dawidd6/action-download-artifact@, delaguardo/setup-graalvm@, docker://jekyll/jekyll:, docker://pandoc/core:2.9, eps1lon/actions-label-merge-conflict@, gaurav-nelson/github-action-markdown-link-...

The action provided by helm/kind-action is now allowed to be used in Apache projects. This should be fixed in another way.

Because kind action is not available in this repo. Plan to try ginko and envtest and refactor all unit and integration tests.

Ginkgo and envtest have been introduced to this project.

Fixed


Subshell notation during globals' initialization

Dear maintainers,
just has excellent support for backticks when defining global variables.
I would like to just -pun intendend- use simple subshell syntax like $(foo) during globals' initialization.
Backticks are akin to subshell commands anyway, why not the explicit subshell notation support?
This would:

allow nesting
clearly delimit subshells

I'm fine with allowing $(…) as a synonym for backticks. Although I'd like to wait for a bit to get some more positive feedback, since it would be a bit confusing to have two ways of doing the same thing.

Ah yeah, right, if you want nested backticks, you can of course use $(…) which is also the recommended syntax for bash. In that case, I don't think this is worth it.


Missing idle_time_before_shutdown_minutes option from the schema

The option for idle_time_before_shutdown_minutes is missing here in this documentation.
It is mentioned in another article, but should also be here for reference - thanks
https://learn.microsoft.com/en-us/azure/machine-learning/how-to-create-manage-compute-instance?tabs=azure-cli&view=azureml-api-2#enable-idle-shutdown
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: c28b80c4-5aee-5465-654a-082d340fed70
Version Independent ID: b7b02f43-32c2-1239-1da1-cf7f666d281a
Content: CLI (v2) compute instance YAML schema - Azure Machine Learning
Content Source: articles/machine-learning/reference-yaml-compute-instance.md
Service: machine-learning
Sub-service: core
GitHub Login: @jesscioffi
Microsoft Alias: jcioffi

@jesscioffi
could you please review this, add your comments and update as appropriate.

@neilmca-inc
I've delegated this to @jesscioffi, a content author, to review and share their valuable insights.


can't change output column width in a notebook resultset grid

Azure Data Studio Version: 1.5.2

Steps to Reproduce:

Run a cell that has a table in the results
Try to resize any column width
I cant seem to make them wider or smaller like I used to

Not able to repro this one in the insider build. @amthomas46 are you on Mac or Windows? I can test both just to be sure.
We fixed an output area notebook issue last week in the insiders build, which may be related. I'll confirm, though.

This was on Windows

@YurongHe made improvements here for our April release with #4790. Just tried on both Windows and Mac, and we now resize correctly on double clicking.


steps to creating datastore missing in data_store_checker notebook

data_store_checker.ipynb does not show the steps to create the data store. This might make the notebook difficult to learn from for those new to the topic.
Solution: we should add the steps to creating the datastore.

This wasn't added to the Data Store Checker notebook because creation wasn't supported through the API at the time.
The creation steps have now been added to https://github.com/GoogleCloudPlatform/generative-ai/blob/main/search/create_datastore_and_search.ipynb


Upgrading to<EMAIL_ADDRESS>breaks the app

I think it's a react-hot-loader issue, but it can be good to know about in the project since it took some time to find out.
Read more about it here: https://github.com/gaearon/react-hot-loader/issues/986

Thanks @joacim-boive for reporting this. But the error seems caused by DLL bundle not loaded. Can you check if the global variable devVendors_xxxx exists? The variable should not be related with RHL since it's loaded in a separate <script> tag. And could you please check <prj-root>/.tmp/dev-vendors.js if the variable is the same as which in error message? If not, remove .tmp folder and restart dev server.


Can't open the login page normally, it shows error page 500

I have tried many times and still can't solve it.
Please tell me where the problem is and how to solve it?
System check identified no issues (0 silenced).
April 19, 2020 - 22:58:55
Django version 2.2.10, using settings 'crm.settings'
Starting development server at http://<IP_ADDRESS>:8000/
Quit the server with CTRL-BREAK.
[19/Apr/2020 22:59:09] "GET / HTTP/1.1" 302 0
[19/Apr/2020 22:59:09] "GET /login/?next=/ HTTP/1.1" 500 1553
[19/Apr/2020 22:59:09] "GET /favicon.ico HTTP/1.1" 404 1286

Having the same problem.  Tried the complete installation procedure two times.
Please help.

in crm/settings.py
DEBUG = os.getenv('DEBUG_STATUS', False)
APPLICATION_NAME='My App Name'
SETTINGS_EXPORT = [
'DEBUG',
'APPLICATION_NAME',
]

Same issue, Can anyone help?

Having the same problem.  Can anyone help?

Download released 0.6.0 source code

Thanks @yanhaocn2000 , Now it works....

Need this MR to go in: https://github.com/MicroPyramid/Django-CRM/pull/377

@Cheradenine can you fix conflicts in the PR?


Added weight compression for Dolly 2.0

Added weight compression for Dolly 2.0:

Performance boost is about 2x
No prediction quality degradation based on the samples provided in gradio

Enabled the compression by default, however there is still a widget for enabling/disabling it

@eaidova @MaximProshin please review


is the llama 3.1 405b you serving using fp8 or bf16?

sorry i dont know where to ask it.
is the llama 3.1 405b you serving using fp8 or bf16?

Ah it is FP8 for our public API. We do support different precisions in dedicated deployments.


[Chart]Line Chart Time Series markers not correct after zoom

For details see superset-ui issue: https://github.com/apache-superset/superset-ui/issues/881

Thanks for reporting!  im able to reproduce on master. will get it fixed soon. 🙏

This will actually be fixed by https://github.com/apache/superset/pull/12349

This will actually be fixed by https://github.com/apache/superset/pull/12349


Registration Agency: ES-MDJ

Hi AidStream,
Please can the Registration Agency ES-MDJ be added to Aidstream?
This is for the Ministry of Justice, Spain - http://org-id.guide/list/ES-MDJ
Thank you,
Jahnvi

Hi Jahnvi,
The registration Agency ES-MDJ has been added to Aidstream.
Thank you

Thank you!