Spatial Subsetting, NHD Attribute Table functions, NLDI wrapper

From: https://github.com/dblodgett-usgs/nhdplusTools/pull/4
See that PR for some discussion.
@mikejohnson51 contributed:
Three big things are included in this PR so I am sure we have a lot to discuss before they are final :) Once we finalize what you like/don't like, I can write the needed tests.
The new features include:

Spatial subsetting for NHD, WBD08 and 12, as well as waterbodies (find_nhd.R)
-- Support for multi-realization requests (flowline, catchment and outlets)
-- Subsetting can be defined by location (POINT), areas, or IDs (either comid or nwis)
Add spatial wrapper around dataRetrieval NLDI (find_nldi.R)
-- straight use of dataRetrieval with a call to st_as_sf() at the end
Add tools around nhdplusVAA data - sans geometry (get_vaa.R)
-- include download/cache from HydroShare, column enabled read using fst
add discover_nwis() to find spatial NWIS locations via location and area

library(nhdplusTools)
#> Loading required namespace: sf
#> USGS Support Package: https://owi.usgs.gov/R/packages.html#support

# Search by Area
AOI   <-  AOI::aoi_get("Santa Barbara")
geoms <-  discover_nhd(AOI, realization = "all")
nwis  <-  discover_nwis(AOI)
plot(geoms$catch$geometry)
plot(geoms$flowline$geometry, col = "blue", add = TRUE)
plot(geoms$outlet$geometry, col = "red", add = TRUE, pch =16, cex = 1)
plot(nwis$geometry, col = "green", add = TRUE, pch =16, cex = 1)

# Search by Point
AOI <- AOI::geocode("University of Wisconsin-Madison", pt = TRUE)
catch <-  discover_nhd(AOI, realization = "catchment")
plot(catch$geometry)
plot(AOI$geometry, col = "red", add = TRUE, pch =16, cex = 1)

# Search by ID
c101 <-  discover_nhd(comid = 101)
plot(c101$geometry, col = "blue")

# Query Attrbitues, no geometries
vaa = get_vaa(atts = c("slope", "lengthkm"))
head(vaa)
#>     comid      slope lengthkm
#> 1 8318793 0.06083397    1.295
#> 2 8318787 0.09534391    1.323
#> 3 8318775 0.11273792    2.883
#> 4 8318785 0.15142342    2.370
#> 5 8318789 0.16246142    1.511
#> 6 8318801 0.10504926    0.406

# Basic NLDI
nldi = find_nldi(comid = 101, nav = "UT", find = c("basin", "nwis"), distance_km = 1000)
plot(nldi$basin)
plot(nldi$UT, col = "blue", add = TRUE)
plot(nldi$UT_nwissite$geometry, col = "red", add = TRUE, pch =16, cex = 1)

Created on 2020-11-14 by the reprex package (v0.3.0)

The last two commits from @mikejohnson51 on closed PR #174 are now all included here. Comments from #174 are below.

Documentation has been refined
Tests have been added with complete coverage (excluding error handling for internet failure)

Improvements to SRS handling

The new default behavior is that returned sf objects are returned in the SRS of the input AOI POINT, POLYGON. In the case of IDs, the default geoserver EPSG:4326 is used. The t_srs allows user to specify the return SRS.
A new parametert_srs and been added to all "get" functions.

> get_nhdplus(comid = 101) %>% st_geometry()
Geometry set for 1 feature
geometry type:  LINESTRING
dimension:      XY
bbox:           xmin: -94.6484 ymin: 31.0838 xmax: -94.63 ymax: 31.0992
geographic CRS: WGS 84
LINESTRING (-94.6484 31.0992, -94.648 31.0987, ...

> get_nhdplus(comid = 101, t_srs = 5070) %>% st_geometry()
Geometry set for 1 feature
geometry type:  LINESTRING
dimension:      XY
bbox:           xmin: 128529.7 ymin: 890725.7 xmax: 130304 ymax: 892413.3
projected CRS:  NAD83 / Conus Albers
LINESTRING (128529.7 892413.3, 128568.5 892358....

All distance and buffering calculations are handled internally in EPSG:5070

Intersections

We have had some weird issues with BBOX requests yielding extra objects due to the default geoserver behavior (intersection of feature BBOXs rather then the features themselves)
All intersections are now handled on the client side. This allows us to stick with faster geoserver BBOX calls

Buffer  Addition

All POINT AOI requests can now be supplemented with a buffer (in meters) that increases the search radius

Default get_nhdplus behavior

If a POINT AOI is given, and a flow line realization requested, the flow line returned is that of the intersecting catchment.
Only the requested realizations are returned (before if outlets were requested the flow lines used to find them were kept)


DOC: Documentation for sim_trait

Documentation for sim_trait function.

The comments in the code blocks will be removed once sim_trait is incorporated into tstrait.


Adds CreateClient to manager

This PR adds an optional option to the manager: CreateClient. This takes a function which returns a cert-manager client based on the passed Volume metadata. This is designed to be used to generate on the fly cert-manager clients that make use of CSI token requests. CertificateRequests created by this client will then have the UserInfo of the pod who owns that Volume. This allows a CSI driver to request identity documents on the pods behalf, whilst an approver can validate the contents of the certificate request matches that of the pod.
By default this is unset, which means the Client cert-manager client will be used to create CertificateRequests.
I have modified the filesystems RegisterMetadata func so that it will write to file also when the volume context has changed. This is important as the Kubelet will call NodePublishVolume again when the current token has expired, passing a new one. Without this change, the driver would continue to use a stale token which would result in certificate renewals being rejected.
Needs some manual testing but opening for visibility.
/cc @munnerz

/hold

Tested this and works how I want it to.
spec:
  extra:
    authentication.kubernetes.io/pod-name:
    - my-csi-app-5d5bf8b8cd-nw2np
    authentication.kubernetes.io/pod-uid:
    - 38ae3ebf-9c7e-4e0e-bbdc-8fa3a7945c8f
  groups:
  - system:serviceaccounts
  - system:serviceaccounts:sandbox
  - system:authenticated
  uid: 743b8be6-b9cc-48f7-bb0c-1a4abfa86fb4
  username: system:serviceaccount:sandbox:my-csi-app

/unhold

/lgtm


Clean up discogsauth.py wrapper and make project "current" again

This tool has sat idle for some time. OAuth is now handled within discogs_client official library. Swap this in and remove the cruft that is currently in place.

Addressed in commit https://github.com/jesseward/discogstagger/commit/7cd13695d818fbc2b9f4cd2bee9de8e5442acff0


New package: Chemistry v0.1.0

Registering package: Chemistry
Repository: https://github.com/baobabfruit88/Chemistry.jl
Created by: @baobabfruit88
Version: v0.1.0
Commit: 44249287e5fd1d2e795818773c486b171f69f1e4
Reviewed by: @baobabfruit88
Reference: https://github.com/baobabfruit88/Chemistry.jl/commit/44249287e5fd1d2e795818773c486b171f69f1e4#commitcomment-52414608

Closing in favor of https://github.com/JuliaRegistries/General/pull/39268

@DilumAluthge Thanks, had some issues getting it to work !


Removed reclaim & preempt actions in vk-scheduler (kube-batch)

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
Description:
Remove reclaim & preemption actions from volcano deployment:
https://github.com/kubernetes-sigs/volcano/blob/master/deployment/volcano/config/kube-batch.conf

/sig scheduling

/assign @thandayuthapani


How to realize the batch operation,update and delete

How to realize the batch update and batch delete data??Don't need to query and then update

Currently you would need to issue a raw SQL statement using context.Database.ExecuteSqlCommand() to run the command.
In the future, we plan to implement a set-based update/delete feature - https://github.com/aspnet/EntityFramework/issues/795.

But there are no ExecuteSqlCommand 1.0 and now this method


AXIS API integration Analysis

Title of ticket:
Description
Dependencies
Are there any dependencies?
DOD

[ ] API Integration POC
[ ]  Low level code integration with API endpoint to do REquest POST, GET etc.
[ ] Get request number from AXIS
[ ] Request opened in Flow is opened in AXIS

As per meeting with ATIP/Vendor, the APIs are not still not ready as promised. So for AXIS integration or Technically, to make a data sync. between AXIS and new FOI Flow, a Plan B development route is possible. Lets discuss that possibility , if we feel that AXIS Vendor dependency is not viable option. @lmullane @m-prodan @mpilchar @arielleandrews

@arielleandrews @mpilchar @m-prodan @lmullane
Plan B for AXIS Integration

Create/Develop an API inside firewall accessing AXIS Database

This API will fetch the Request Details from AXIS DB(SQL Server) and serve it for our FOI Flow Application

Benefits : there is no need for manually entering AXIS Updates to FOI Flow app. Anyhow, we need to create a reference on FOI Flow with AXIS Request Identifier . This "Sync-ing" process can be automatically as well as with a user interaction upon a proper review on the data. This can be decided.

Why API inside Firewall ? - Reason is because of the same reason we had with "File Conversion". Accessing an IP on Openshift need a full opening of entire IP Range - which will be an issue for IMB and OC folks - same as earlier

Bit to plan , design, architect around integrate area - including Data flow, data fields to be Sync'd etc.

IF NOT DONE, what is issue ? - Manual Data Entering is required, Source of truth confusions around Data even with Pilot ministries.


Scanner not working sometimes

I've faced with some strange scanner behavior on Android.
On some devices scanner not working (not scanning) at first page opening. I have to close page and open it again. After that scanner works correctly.
May be some "internal" things not ready on first try?
For example there https://github.com/JimmyPun610/BarcodeScanner.XF/blob/dd8c0d099b4c155a9aefd2accb92afe28affcf51/GoogleVisionBarCodeScanner/Android/Renderer/CameraViewRenderer.cs#L84

I have the same problem. In Debug mode, this is rare, but in Release it occurs every time

maybe related to #105

Hi,
In my case this is happening when proxy?.Close(); in SafeCloseImageProxy method in Android CameraViewRenderer.cs line 410 raise the ArgumentException.
private void SafeCloseImageProxy(IImageProxy proxy)
{
	try
	{
		proxy?.Close();
   	}
   	catch (ObjectDisposedException) { }
   	catch (ArgumentException)
   	{
      	//Ignore argument exception, it will be thrown if BarcodeAnalyzer get disposed during 		processing
    	}
}

System.ArgumentException: Handle must be valid.
Parameter name: instance
at Java.Interop.JniEnvironment+InstanceMethods.CallVoidMethod (Java.Interop.JniObjectReference instance, Java.Interop.JniMethodInfo method) [0x00009] in /Users/runner/work/1/s/xamarin-android/external/Java.Interop/src/Java.Interop/Java.Interop/JniEnvironment.g.cs:11853
at Android.Runtime.JNIEnv.CallVoidMethod (System.IntPtr jobject, System.IntPtr jmethod) [0x00000] in /Users/runner/work/1/s/xamarin-android/src/Mono.Android/Android.Runtime/JNIEnv.g.cs:258
at AndroidX.Camera.Core.IImageProxyInvoker.Close () [0x0002d] in D:\a\1\s\generated\androidx.camera.camera-core\obj\Release\monoandroid9.0\generated\src\AndroidX.Camera.Core.IImageProxy.cs:467
at BarcodeScanner.Mobile.XamarinForms.Renderer.CameraViewRenderer+BarcodeAnalyzer.SafeCloseImageProxy (AndroidX.Camera.Core.IImageProxy proxy, BarcodeScanner.Mobile.XamarinForms.Renderer.CameraViewRenderer _renderer) [0x00002]
After this exception scanning stops.
I've managed to add quick and dirty workaround with calling:
try
{
    proxy?.Close();
}
catch (ObjectDisposedException) { }
catch (ArgumentException)
{
    //Ignore argument exception, it will be thrown if BarcodeAnalyzer get disposed during processing
    Device.BeginInvokeOnMainThread(() =>
    {
        _renderer.CameraCallback();
    });
}

Hi, wanted to now if there is any progress made with this issue?

I am also facing same issue for Android Kyocera dual force pro device.
Sometimes it is working if we move application from background state to foreground state.

I have the same issue, using <IP_ADDRESS> in MAUI
In debug is works all the time, but when I switch to release there is like 1/5 chance that scanner won't send any OnDetected events when opened.


README.md: Broken link

Hello and many thanks for open sourcing the design of this sensor!
FYI: The link in "A complete Open Source logging solution employing a batch of 40 sensors in Crete for tree monitoring" returns Error 404

fixed, thanks


mgrpxy: expose port on IPv6 network (bsc#1227951)

What does this PR change?
followup of https://github.com/uyuni-project/uyuni-tools/pull/406. Same changes should be present in mgrpxy.
Test coverage

No tests
[x] DONE

Links
Issue(s): https://github.com/SUSE/spacewalk/issues/24848

[x] DONE

Changelogs
Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository
If you don't need a changelog check, please mark this checkbox:

[ ] No changelog needed

If you uncheck the checkbox after the PR is created, you will need to re-run changelog_test (see below)
Before you merge
Check How to branch and merge properly!

@aaannz @vzhestkov yes, this would work also if ipv6 is disabled. I followed what we implemented for server and trying to keep it simplest as possible, but enabling it just when ipv6 is enabled is not complicated. I'll go with this change

Hmm, it's really interesting. With salt-broker if it's set to listen to [::] it makes it responsive for both IPv6 and IPv4, but in case of conmon with podman it looks like we need to have it listening to both [::] and <IP_ADDRESS>.


Added scheduler integration tests

What type of PR is this?
/kind test
What this PR does / why we need it:
Adds integration test that covers end-to-end scheduling of jobs.
Which issue(s) this PR fixes:
Fixes  #30
Special notes for your reviewer:

LGTM.  Could you squash or wait Aldo review?

Squashed, lets move on and keep the momentum, this is just a test.

/lgtm
Thanks.


When recreating the VG-SGG file, the number of objects and relations is different

Hi All,
I'm trying to add some data to the VG-SGG file, and I thought the easiest way was to try and recreate the processed data. However, when I do this, the number of objects and relations that are remaining changes.
I have no clue why this is happening. Should I change some settings? Or is something else happening?
Thanks for the help and any insight you can give!

Hello, have you solved this problem？

Sorry for the late reply. Yes, I did.
I was trying with both versions available on the VisualGenome website. Apparently, the files linked in the data folder of this repo are a third version. All data versions create different results.
I don't know how these differences affect results in models, but at least something to consider.


[FR] typescript.suggest.paths show js files

Currently, the default typescript path completion doesn't show js files, could this be improved?

/needsMoreInfo
What is your tsconfig.json? Does it have  "allowJs": true?
If it allows JS then is it reproducible with all extensions disabled?
You can try this with F1 and >Developer: Reload Window With Extensions Disabled

After adding "allowJs": true, the suggestions did show up, thanks!


[Improvement] Better error message for self is not a module, it's a class

If you use a class (by mistake) instead of a module and extend it with self, you get an error like
Error self is not a module, it's a class

You don't get a file path and a line number
If you are new to Crystal the error message is not very helpful (you don't know what should be done)

Could this be improved?

Now in a code like this:
class Foo
  extend self
end

You get:
Error in ./foo.cr:2: Foo is not a module, it's a class

  extend self
         ^

Is that good enough?

Yes, that's better :+1:
Thx, asterite!


socket_import_stream() and TCP_NODELAY

Hi all !
I checked this code from PhpiredisStreamConnection.php (set $parameters->tcp_nodelay to 1):
$socket = $socket ?: socket_import_stream($resource);
socket_set_option($socket, SOL_TCP, TCP_NODELAY, (int) $parameters->tcp_nodelay);
...code executed OK, but it has no any effect for me (Linux cs20605 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u2 x86_64, PHP 5.4.41-0+deb7u1 (cli)), Nagle's algorithm works anyway (checked by tcpdump).
Any idea?

What kind of effect are you expecting that is not delivered by setting the TCP_NODELAY flag?

What kind of effect are you expecting that is not delivered by setting the TCP_NODELAY flag?

When I send small packets of data it will be sent not immediatelly (as expected after set TCP_NODELAY), but still will wait some time (because of Nagle's algorithm), so looks like TCP_NODELAY is not set really.

@alex-nevidomy I did an strace of the PHP CLI process and the TCP_NODELAY socket option is successfully set on the underlying socket resource (setsockopt() returns 0 thus no error) when specifying tcp_nodelay=1 in the connection parameters, as you can see in the last line here:
connect(3, {sa_family=AF_INET, sin_port=htons(6379), sin_addr=inet_addr("<IP_ADDRESS>")}, 16) = -1 EINPROGRESS (Operation now in progress)
poll([{fd=3, events=POLLIN|POLLOUT|POLLERR|POLLHUP}], 1, 5000) = 1 ([{fd=3, revents=POLLOUT}])
getsockopt(3, SOL_SOCKET, SO_ERROR, [0], [4]) = 0
fcntl64(3, F_SETFL, O_RDWR)             = 0
getsockopt(3, SOL_SOCKET, 0x27 /* SO_??? */, [2], [4]) = 0
fcntl64(3, F_GETFL)                     = 0x2 (flags O_RDWR)
setsockopt(3, SOL_TCP, TCP_NODELAY, [1], 4) = 0

The function socket_import_stream() makes it possible to access the underlying "raw" socket resource wrapped by a PHP stream so that you can set flags otherwise inaccessible when using the stream interface.

Did you check the data sending after you set TCP_NODELAY option? Data were sent immediately?
Could you please show tcpdump of your test?

Well the fact that the the low-level setsockopt() does not return an error code means that the operating system set the TCP_NODELAY on the resource but from that point whatever happens (e.g. the network stack is forced to act accordingly) is unfortunately beyond our reach. Anyway I tried a few times to reproduce latency by issuing commands that generate small packets but had no luck, even without setting the TCP_NODELAY (I'm developing locally on multiple virtual machines so it wouldn't surprise me if the network stack acted in a different matter), so all I can say for now is that it did indeed work last time I performed more extensive tests while implementing this feature.
You could try using Predis\Connection\PhpiredisSocketConnection which relies directly on socket resources (requires ext-socket and ext-phpiredis) instead of PHP streams and see if you notice any different behaviour.
I'm closing this issue for now because I'm pretty sure it's not directly attributable to Predis but feel free to add more details if needed.


Standardize Gaussian representation

Currently, gsplat's APIs largely revolve around Gaussians represented as some form of dict[str, Tensor].
https://github.com/nerfstudio-project/gsplat/blob/44544f7bdbbb9f0002e86025967e6e7dc877942d/gsplat/compression/png_compression.py#L75
https://github.com/nerfstudio-project/gsplat/blob/44544f7bdbbb9f0002e86025967e6e7dc877942d/gsplat/strategy/default.py#L109
As more features are added, I believe it'd be useful to have a more standard representation of Gaussians, rather than a loosely typed dict. Some ideas:
Mapping
Relaxing the dict requirement and using Mapping[str, Tensor] would allow for more flexibility.
TypedDict
In the opposite direction, a more strictly typed approach would allow for static type checking, and possibly alleviate the need for functions like check_sanity.
class Gaussians(TypedDict):
    means: Tensor
    scales: Tensor
    quats: Tensor
    opacities: Tensor
    # we could store SH coeffs, RGB colors, or features here

This would also allow arbitrary parameters (embeddings, features, etc.) to be supported.
TensorDict
TensorDicts are torch-native dictionary types that support tensor operations.
This could make implementation of more advanced features easier.
g = TensorDict(
    {
        "means": means,
        "scales": scales,
        "quats": quats,
        "opacities": opacities,
        "colors": colors,
    },
    batch_size=[len(means)],
)

assert means == g["means"]
g[0]  # this is possible

Hey sry for the late reply!
I was struggling to find a more general way to represent a Gaussian than dict. And all your options seem to be better than what we are having at the moment.
@brentyi What do you think about the above options?

Thanks @yklcs for raising this! Overall I'd also like to see this improved; @kerrj and I had also spent some time thinking about it a few months ago but didn't come to any solutions we were happy with.
If anyone has a specific solution they want to advocate for I'd be interested in discussing.
Some thoughts on what's been suggested in the meantime:

Mapping[str, Tensor]: I'm okay with switching to this but the practical impact seems relatively low, it feels rare to have non-dict mappings and there's very little static safety either way.

This type also isn't compatible with nn.ParameterDict so we'd still need a union if we want to retain compatibility. It seems to suppress type checking errors for TensorDict because TensorDict inherits from MutableMapping[Any, Any], but if this is the goal I'd prefer to just add TensorDict to the union.

TypedDict: despite my gripes with nn.ParameterDict it feels unlikely we'd switch away from it in Nerfstudio/splatfacto because it's a hassle to use standard dictionaries with PyTorch modules/optimizers. But I could see GaussianTypedDict | nn.ParameterDict or even GaussianTypedDict | dict[str, Tensor] | nn.ParameterDict being useful for type safety within gsplat, or for (the very few) outside users who care about types.

We could also move away from torch.nn (including nn.ParameterDict) for simple_trainer.py entirely and use a typed dict instead. It feels like we should be fine with just setting requires_grad=True on standard tensor objects.

TensorDict: I'm fine with supporting this as an input, tensordict seems like a great library. But I'm not sure about long-term maintenance given that the library is still in beta and if things like pytrees finally make it into the stable PyTorch API.

There's also @tensordict.tensorclass, but this gives me a slew of type checking errors when I try to use it so I'd prefer to avoid. (this also makes me hesitant about TensorDict)


[BACKEND] Fix hopper mma to linear layout constraints

n = 8 should be a valid option
https://docs.nvidia.com/cuda/parallel-thread-execution/index.html#asynchronous-warpgroup-level-matrix-shape

Thanks for the comment. Let me add it to our discussion topic list


[idea]:  Web API Response for Store?

Rather than returning Promise<Uint8Array> , we could unify the store interface around Web-standard Response to expose additional features to zarr.Array instances.

Use the Response.ok or response.status to determine if the item is in the store or not (rather than Uint8Array | undefined).
Exposes conveniences to read response directly via .json(), .text(), .arrayBuffer(), and .blob(), rather than copying array buffers etc.
Ability process Response.body as a stream. This is the most interesting/exciting to me, but it's not clear if it would be useful. Ideally there is a world were chunks could be partially decoded, etc.

Rather than handling Responses within zarr.Array, we could look into something like a StorageTransformer layer, which by default just reads the response in full.

https://github.com/zarr-developers/zarr-specs/pull/134

hmm doesn't seem like Response is provided as a global in Node.js... would likely need to allow the current interface as well with Uint8Array.


Fix rollup error

Not exactly sure if npm run rollup task was still expected to run, but noticed that it did not.  If this pull request is not needed for any reason then let me know.
$ npm install
$ npm run rollup
[BABEL] `emotion/src/styled.js`: Unknown option: `emotion/.babelrc.presets` (src/styled.js)

rollup.config.js

Changed dist from umd:main to main

.babelrc

Removed root level usage of env to fix rollup error:

(babel plugin) It looks like your Babel configuration specifies a module transformer. Please disable it. See https://github.com/rollup/rollup-plugin-babel#configuring-babel for more information (src/styled.js)

Updated a few minor versions:

babel-core from 6.24.1 to 6.25.0
babel-preset-env from 1.5.1 to 1.5.2

Added webpack as dev dependency to fix npm install message:
└── UNMET PEER DEPENDENCY webpack@2 || 3

Removed rollup-plugin-buble since it did not look like it was used any longer.
Updated .travis.yml

Test node version 8
Test npm run rollup
Add temporary fix to .travis.yml to ensure required test dependencies get installed.

Tests on node version 8 are failing, but it looks like it may only be because expectation results are returned in an order that is unlike the expectation:
-> % npm test

><EMAIL_ADDRESS>test /Users/afaur/Projects/Node/React/CSS/emotion
> standard src test && jest --coverage --no-cache

 FAIL  test/keyframes.test.js
  ● keyframes › renders

    - Snapshot
    + Received

    - .css-H1-o0kcx2-5hrnwy {
    + .css-H1-o0kcx2-1jnhxdn {
        font-size: 20px;
    -   -webkit-animation: animation-bounce-10a3qiv-c1ph90 2s linear infinite;
    -   animation: animation-bounce-10a3qiv-c1ph90 2s linear infinite;
    +   animation: animation-bounce-10a3qiv-1xeytvt 2s linear infinite;
    +   -webkit-animation: animation-bounce-10a3qiv-1xeytvt 2s linear infinite;
      }

      <h1
    -   className="css-H1-o0kcx2-5hrnwy"
    +   className="css-H1-o0kcx2-1jnhxdn"
      >
        hello world
      </h1>

      at Object.<anonymous> (test/keyframes.test.js:51:18)
          at Promise (<anonymous>)
      at Promise.resolve.then.el (node_modules/p-map/index.js:42:16)
          at <anonymous>
      at process._tickCallback (internal/process/next_tick.js:169:7)

 FAIL  test/styled.test.js
  ● styled › higher order component

    - Snapshot
    + Received

    - .css-onyx-wn422p-gyln3i {
    + .css-onyx-wn422p-ytvmc1 {
        name: onyx;
        background-color: '#343a40';
    +   flex-direction: column;
    +   -webkit-box-direction: normal;
    +   -webkit-box-orient: vertical;
    +   -ms-flex-direction: column;
        -webkit-flex-direction: column;
    -   -ms-flex-direction: column;
    -   -webkit-box-orient: vertical;
    -   -webkit-box-direction: normal;
    -   flex-direction: column;
        name: squirtle-blue-bg;
        background-color: #7FC8D6;
      }

      .css-Content-13wdnau-1z6hk6 {
        font-size: 20px;
      }

      <div
    -   className="css-Content-13wdnau-1z6hk6 css-onyx-wn422p-gyln3i"
    +   className="css-Content-13wdnau-1z6hk6 css-onyx-wn422p-ytvmc1"
      />

      at Object.<anonymous> (test/styled.test.js:198:18)
          at Promise (<anonymous>)
      at Promise.resolve.then.el (node_modules/p-map/index.js:42:16)
          at <anonymous>
      at process._tickCallback (internal/process/next_tick.js:169:7)

 FAIL  test/babel.test.js
  ● emotion/babel › babel styled component › css basic

    expect(value).toMatchSnapshot()

    Received value does not match stored snapshot 1.

    - Snapshot
    + Received

    @@ -5,11 +5,11 @@
             display: -webkit-box;
             display: -moz-box;
             display: -ms-flexbox;
             display: -webkit-flex;
             display: flex;
    +        flex: 1 0 auto;
    +        -ms-flex: 1 0 auto;
             -webkit-flex: 1 0 auto;
    -        -ms-flex: 1 0 auto;
    -        flex: 1 0 auto;
             color: blue;
             width: ${x0}; }`];
     });"

      at Object.<anonymous> (test/babel.test.js:75:20)
          at Promise (<anonymous>)
      at Promise.resolve.then.el (node_modules/p-map/index.js:42:16)
          at <anonymous>
      at process._tickCallback (internal/process/next_tick.js:169:7)

  ● emotion/babel › babel keyframes › keyframe basic

    expect(value).toMatchSnapshot()

    Received value does not match stored snapshot 1.

    - Snapshot
    + Received

     "
     const rotate360 = keyframes("animation-rotate360-f35ahc", [], function createEmotionKeyframe() {
    -  return ["from {\\n    -webkit-transform: rotate(0deg);\\n    -ms-transform: rotate(0deg);\\n    transform: rotate(0deg);\\n} to {\\n    -webkit-transform: rotate(360deg);\\n    -ms-transform: rotate(360deg);\\n    transform: rotate(360deg);\\n}"];
    +  return ["from {\\n    transform: rotate(0deg);\\n    -ms-transform: rotate(0deg);\\n    -webkit-transform: rotate(0deg);\\n} to {\\n    transform: rotate(360deg);\\n    -ms-transform: rotate(360deg);\\n    -webkit-transform: rotate(360deg);\\n}"];
     });"

      at Object.<anonymous> (test/babel.test.js:196:20)
          at Promise (<anonymous>)
      at Promise.resolve.then.el (node_modules/p-map/index.js:42:16)
          at <anonymous>
      at process._tickCallback (internal/process/next_tick.js:169:7)

Snapshot Summary
 › 4 snapshot tests failed in 3 test suites. Inspect your code changes or run with `npm test -- -u` to update them.

Test Suites: 3 failed, 1 skipped, 3 of 4 total
Tests:       4 failed, 1 skipped, 23 passed, 28 total
Snapshots:   4 failed, 23 passed, 27 total

Going to remove node version 8 from .travis.yml because of these issues.
Will keep commit history in PR (in case same issues are encountered in future).
I noticed that I had mutated package.json and package-lock.json when checking locally the node@8 testing issue.  I made an update to fix the files in my last commit for this PR. (https://github.com/tkh44/emotion/pull/25/commits/f62045346ce64731f059bfe5c91d0ab5ddf6fcdf)

Codecov Report

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

@@           Coverage Diff           @@
##           master      #25   +/-   ##
=======================================
  Coverage   79.49%   79.49%
=======================================
  Files          11       11
  Lines         395      395
  Branches       67       67
=======================================
  Hits          314      314
  Misses         67       67
  Partials       14       14

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 30107f9...41acb9d. Read the comment docs.

I removed the rollup build because a umd build is not necessary because of the babel requirement. I'm just keeping it around to keep an eye on bundle size.

Sounds good.  I will go ahead an close this out then.

Thank you though. Don't want to discourage you from helping in the future!


Fix first lint after

I was reading through the docs and previous issues, but couldn't find anything related to this.
I have set fix and lint to happen when I save the file. What happens some times is that linter will run says there are some bits that are wrong and I should use the fixer, then the fixer automatically kicks in and fixes the things and the errors eventually go way.
So I'm guessing what's happening is something like:

              |---- run linter > show errors
save file --- |                                            |---- run linter again
              |-----run fixer > fix and save file again  --|
                                                           |-----run fixer again?

Is there a way to only run the linter after running the fixer, so in this case do a chain?
save file --- > run fixer ---> fix and save file again  ---> run linter

What's happening is that some other event is checking the file before you save it. If you change your settings to only check files when you save them, it will behave as you describe already.
let g:ale_lint_on_text_changed = 0
let g:ale_lint_on_insert_leave = 0
let g:ale_lint_on_enter = 0
let g:ale_lint_on_save = 1
let g:ale_lint_on_filetype_changed = 0

That probably isn't what you want to do, though.


changes in UIETask to remove mutliple schema construction

PR types

Enhancement as discussed in issue 2165.
PR changes

remove import but unused os lib
use _schema_tree attribute to displace multiple times of schema tree construction
remove schema_tree arg in _multi_stage_predict
add early check & return in _multi_stage_predict
rename id var in _multi_stage_predict to idx to avoid mixing with python built-in funcs
change _build_tree func to python classmethod

Description

Use an attribute _schema_tree to avoid building schema tree on each call.
Local test passed.

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


fix ci and readme

Pull request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[x] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?
The CI fails because the auto format cannot commit to main. There is an open discussion about how this should be done (allowing the bot to push to a protected branch is not the right way, see https://github.com/orgs/community/discussions/25305).
This is a quick fix.
What is the new behavior?
Just applied make-format to fix the CI.
Other information
I've also fixed the build link in the CI and replaced the project owner in all-contributors

@all-contributors please add @matthieuauger for mentoring, code, tests

@all-contributors please add @matthieuauger for mentoring, code, test

https://github.com/all-contributors please add @matthieuauger for code

@all-contributors
please add @matthieuauger for mentoring code test
please add @seshanthS for code
please add @ftupas for code
please add @jobez for code


Experimental client: renaming

Fixes #1397
Description of the changes being introduced by the pull request:
~Note: this is done on top of changes introduced by #1396~
Proposes the following client naming and directory structure:
tuf/
    ngclient/
        __init__.py
        updater.py
        metadatabundle.py
        network/
            __init__.py
            requestsfetcher.py
            download.py

Most significant changes:

client_rework -> ngclient (next-gen-client): almost what @jku suggested but trying to avoid dashes (not accepted) and underscores (not recommended) in package names.
client public classes are exposed in ngclient/__init__.py
download related modules are moved under network. FetcherInterface is defined in network/__init__.py instead of fetcher.py
new client code is excluded from coverage until better tested

Please verify and check that the pull request fulfills the following
requirements:

[ ] The code follows the Code Style Guidelines
[ ] Tests have been added for the bug fix or new feature
[ ] Docs have been added for the bug fix or new feature

Note that the names here are not package names: they're just module names where underscores can be used if it improves readability.

The reason I suggested ngclient/_internal/ is that the name makes it obvious to an outsider that they should not rely on things inside this module. ngclient/network/ does not convey that and I don't think we can assume outsiders understand that ngclient/__init__.py defines what our API is (as much as I otherwise like it).

Note that the names here are not package names: they're just module names where underscores can be used if it improves readability... but I'm fine with ngclient, no better ideas at the moment

I'll just correct myself here: they do seem to call any directory with __init__.py a package.
I still maintain _internal is a fine name for a directory: this what a lot of big name python projects do (see pip for an example).

Agreed with @jku's review to move non-public modules to _internal.
The new structure is:
tuf/
    ngclient/
        __init__.py
        updater.py
        fetcher.py
        _internal/
            requests_fetcher.py
            download.py
            metadata_bundle.py

Also rebased on latest changes in experimental-client branch.

For some reason github claims there are conflicts here after merging 1403 -- manual rebase works without any issues though?

Yep, rebased.


[JavaScript] How to build a rich text editor with Vue.js and TipTap

Proposal Submission
Proposed title of article
How to build a rich text editor with Vue.js and TipTap
Proposed article introduction
A rich text editor is a necessary feature for all web applications that receive user input that require a degree of formatting:
profile bios, lengthy reviews, or even blog posts.
But that raises the question: how do we build one? It seems like a daunting task, and it would be if we had to do it from scratch.
Thankfully, TipTap solves this problem for us. TipTap is a free, open-source JavaScript library that allows us to create custom rich text editors for our needs.
This article will guide the reader through the process of using TipTap to quickly implement a rich text editor in their Vue.js application.
Key takeaways
At the end of the article, the reader will understand:

What TipTap is
Why they should use TipTap
How to construct a Vue.js TipTap editor
How to obtain the output of the editor in a format of their choice

Article quality
TipTap is not an obscure library, but it isn't extremely popular, so there aren't many articles about it yet. The official TipTap documentation is high quality but doesn't recommend a fixed path to implement it (by design).
This article will provide the reader with a much quicker and more straightforward path to get up and running with TipTap as soon as possible.
References
Official TipTap documentation

Great topic 🚀 , make sure it matches the following:

Adds value beyond what is in the official docs and covered in other blog sites.
To avoid potential article closure, it should not overlap with existing EngEd articles or incoming topic suggestions.

Please reference any relevant EngEd articles in yours and build a unique project - Approved.


Newest docker remote API now 1.24, whats the schedule of docker-api

Are we going to support new version of docker remote api

In fact this is now a blocker for me so I am having to "hack" this gem unfortunately.
In order to use Docker for Mac with IPAMConfig, you need version 1.24+ so that the gateway & ip address are setup correctly.  I would just bump the version number, but I have no idea what consequences could be so for now I'm hacking that single request to use the latest version of the API

relates to #423

Nothing new related to this issue ?

Here is pull request related to this issue #462

Seems the project was not actively maintained last time.
@tlunter Hey. Do you have time to review this and some related issues?
It would be great to add the ability (#462) to explicitly set docker remote api version you want to use.
If any help needed, let me know.
Thanks!

Encountering this as well. Using a really bad patch for now:
Docker.send(:remove_const, 'API_VERSION')
Docker.const_set('API_VERSION', '1.24')


updates to book_changes RPC command

High Level Overview of Change
Updates to the book_changes RPC command.
Pending clarification, I believe this PR also fixes #5033  and #5036 (improves the latency of the command)

Context of Change

accepts shortcut strings (current, closed, validated) as inputs to ledger_index parameter in the RPC command.
returns validated: true/false in the RPC output

Type of Change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactor (non-breaking change that only restructures code)
[ ] Performance (increase or change in throughput and/or latency)
[x] Tests (you added tests for code that already exists, or your new feature included in this PR)
[ ] Documentation update
[ ] Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
[ ] Release

API Impact

[ ] Public API: New feature (new methods and/or new fields)
[ ] Public API: Breaking change (in general, breaking changes should only impact the next api_version)
[ ] libxrpl change (any change that may affect libxrpl or dependents of libxrpl)
[ ] Peer protocol change (must be backward compatible or bump the peer protocol version)

@godexsoft you might want to test this branch with clio.

@Bronek  thanks for the quick review!
What do you mean by USER context? I feel the getLedgerByContext should only be used by the consensus mechanism (and Full History Nodes) to collect+store all ledgers. Its in-efficient for a tiny or medium resources validator to engage in acquisition of ledgers.
The getLedgerByContext method can also be removed in the ledger_request RPC call. I expect to see similar issues in that RPC call. Check my comment here: https://github.com/XRPLF/rippled/issues/5036#issuecomment-2279269503


Dotted keys are not supported

Status

[x] Parse dotted keys in tables
[x] Parse dotted keys in inline tables
[x] Preserve notion of dotted keys
[ ] https://github.com/ordian/toml_edit/issues/163
[x] Error when inserting dotted key into table
[x] Error when inserting table into dotted key

The following TOML file is not parsed successfully:
ssh.public-key-path = "C:/Users/andrew.hickman/.ssh/id_rsa.pub"

It fails with
TOML parse error at line 68, column 4
   |
68 | ssh.public-key-path = "C:/Users/andrew.hickman/.ssh/id_rsa.pub"
   |    ^
Unexpected `.`
Expected `=`

However the toml crate parses this correctly, and looking at the ABNF grammar I think it is a valid TOML file
toml = expression *( newline expression )

expression =/ ws keyval ws [ comment ]

dotted-key = simple-key 1*( dot-sep simple-key )

Just spotted #73 and tried using that branch instead, and I can confirm that it parses this successfully

Support for toml 0.5 is tracked in #58.

Some initial notes when researching this
Table-types summary
Tables

Empty super tables are optional
You cannot use a table to overwrite an item (value or table)
Tables can be out-of-order

Dotted Keys

Implicit tables can only merge with a previous implicit table from dotted key
Table can be used to create child-table

Inline Tables

Immutable

How toml_edit currently does it
Table

Order-preserving map of Key to Item
Create implicit tables for empty super tables

InlineTable

Order-preserving map of Key to Item

Proposed API in #73
Dotted keys are just an Item to serve as a pointer to the appropriate table

The table gets a has_dotted marker (unsure which implicit wasn't used)

Concerns

Directly exposing the dotted-key pointer creates undefined behavior for users directly manipulating it

How tomlkit does it
Root Container appears to directly represent the document as-is

A mapping is maintained between the direct representation and the users mental model
Proxy types are used when the direct representation needs adjusting for a smooth API

Table and InlineTable

independent Containers for their key-value pairs
Implicit super tables are created for each level of a dotted key

Not quite sure how the rest of this is handled.

The idea I'm playing with and trying to vet was briefly mentioned in #122, of having
pub struct Table {
    ...
    format: TableFormat,
}

pub enum TableFormat {
    ImplicitTable,
    DottedTable,
    InlineTable(...),
    Table(...),
}

TODO Finish filing this out

Some updates

I was looking at merging table types

A TableFormat enum was being added along with structs for its invariants, like StandardTable and InlineTable
A table type could be left as unknown until formatting
Problems:

Led to complications when doing different operations that require knowing what the table type is, like sorting.  Maybe that didn't have to be?  I could just sort any ways

I was looking into making the parser an iterator over Expression

Removes all the callbacks
Reduced the cosntant lookups because I kept the in-work table around
Problem: By not erroring inside of a parser, but outside, we lose automatically getting the position in the error message
Could still reduce the lookups by applying the same technique
Could still use expressions and have a shared callback

Overall, at this point, I am looking at keeping InlineTable and Table separate.  There will be a way to mark either table as Dotted.  I'll then add position information to TableKeyValuePari so we dotted positioning works like global table positioning.
I'm thinking of rolling out support gradually.  First, we'll just parse the dotted tables without preserving their style and maybe not handling all error cases correctly.  We'll then slowly add in those features.

Thanks for digging into this.
Something slightly related: you're probably familiar with #63 and table positioning. I think we should make to_string_in_original_order to_string, making the former the default Display behavior.

I was thinking of that! Glad we are on the same page.
I've  also wondered if we should switch away from formatting with Display.  I think its behavior can surprise people (e.g. value.display() including decor when they probably expect the underlying value) and the interface makes things a bit limited (can't pass around state without ...Display types)

(and yes, global table position was inspiring my table key positioning idea so we don't need markers)

I've also wondered if we should switch away from formatting with Display. I think its behavior can surprise people (e.g. value.display() including decor when they probably expect the underlying value) and the interface makes things a bit limited (can't pass around state without ...Display types)

Sure, we should only use Display when it makes sense. I think it does for the whole Document, but maybe not so for other types as you've mentioned.

Random implementation notes from order preserving

I initially tried storing the order in Key but it felt more natural in the parser to put it in the TableKeyValue
I switched to TableKeyValue but we lose that information after we pass through get_children.  So its back to being in the key

I'm splitting #163 out and closing this


fixes flexbox wrapper styles

this is a follow up of my previous pull request and moves the flexbox styles to the wrapper div to fix alignment of content and buttons.
as i'm not using sass in my project i converted my local changes to the sass styles in the component. please validate behaviour before merging.

Ok thanks - I'm going to merge this but I'm not going to push it just yet. I see something wrong that's now been introduced in the bar version. I'll post here when I'm done adjusting that.

Ok so actually everything was working fine - I just added align-items: center to the wrapper for the bar style. I pushed it, and the new npm version is v5.3.1.
I'm a little confused of your use-case here - I see that the wrapper really only is used for the bar version - is this the intent? In your previous comment you mentioned that you wanted to have more control over the width of the bar content - I might be missing something but couldn't you have just used the cookie__bar class that gets applied to the bar version? Maybe you can just shed a little light here. Thank you for your contributions.


CVE-2016-5118 - please upgrade to v0.15.x

http://www.openwall.com/lists/oss-security/2016/05/29/7
http://www.openwall.com/lists/oss-security/2016/05/30/1
This affects the pre-built binaries made available to v0.13.x and v0.14.x on both Linux and Windows. These previous versions will be deprecated and, within 7 days, the pre-built binaries removed.
The current v0.15.x release is unaffected (unless sharp is using an installation of libvips that was manually compiled with a *magick dependency).

npm deprecate<EMAIL_ADDRESS>"CVE-2016-5118 https://github.com/lovell/sharp/issues/449"
npm deprecate<EMAIL_ADDRESS>"CVE-2016-5118 https://github.com/lovell/sharp/issues/449"

I'm still seeing 400-500 downloads per day (~40% of total) of vulnerable versions of the pre-built binaries.
😿

The pre-compiled binaries for libvips v8.2.2 as used by sharp v0.13.0 have now been deleted.
ERROR: https://dl.bintray.com/lovell/sharp/libvips-8.2.2-lin.tar.gz status code 404

The pre-compiled binaries for libvips v8.2.3 as used by sharp v0.14.0 have now been deleted.
ERROR: https://dl.bintray.com/lovell/sharp/libvips-8.2.3-lin.tar.gz status code 404


Add deep has own property function to check whether an object contains a nested key path

Resolves #65.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines, including the relevant style guides.
[x] Read and understand the Code of Conduct.
[x] Read and understood the licensing terms.
[x] Searched for existing issues and pull requests before submitting this pull request.
[x] Filed an issue (or an issue already existed) prior to submitting this pull request.
[x] Rebased onto latest develop.
[x] Submitted against develop branch.

Description

What is the purpose of this pull request?

Provides the implementation of the deep has own property function, to check whether an object contains a nested key path.
Related Issues

Does this pull request have any related issues?

This pull request:

resolves #65

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

@stdlib-js/reviewers

@ognjenjevremovic Awesome!

@ognjenjevremovic Wow! Thanks for all the changes!

Awesome. Thanks for the updates! Will do review and let you know if there is anything else. :)

If I missed out on anything or you feel there's more room for improvement, please feel free to request changes.
Sorry I had to make 2 commits separately, I accidentally made a wrong assumption on where to add the @private JSDoc annotation and already pushed the changes to remote :).

@ognjenjevremovic Awesome! Thanks for making the changes!

Will wait for Circle CI to finish before squashing and merging. :)

Awesome! Thank you for your time and patience on this one @kgryte. :)
Hope it wasn't much of a hassle for you.

@ognjenjevremovic No worries! The first few PRs are always a bit of a slog, especially for projects like this, where a number of conventions have to be learned and implemented. Thanks again!


Multi-cloud, multi-tenant

Placeholder to not forget this needs working on

Handle multiple clouds, does az login do all we need?
Handle split of subscription for state and deployment (maybe already ok)
Tenancy issues?

Multi-cloud has been handled. #77


pixel perfect conversion using docx2pdf

Just wanted to link an alternative command line tool / python library just for the docx use case. It uses Microsoft Word's APIs to provide a perfect conversion to PDF and works on both MacOS and Windows: https://github.com/AlJohri/docx2pdf

Thanks @AlJohri but I don't think creating an issue here is an appropriate place to raise awareness of your project.


Bug: Fixed regression from the fix made in #146

The fix made in the isUpcoming function in issue #146 impacted the display of meetups in the section Next Meetup, Upcoming Meetups and Recent Meetups
Screenshots for better understanding :point_down:

This happened since the condition was inverted in other places using the isUpcoming function.
This PR fixes the issue. Please have a look whether the colors are correct. @MrSunshyne :pray:

thx for noticing and for sending the fix ! 🙏
colors look good. i'm thinking we should reorganize the layout a bit so that we show "events" above the fold when the page loads. for now this will do. i'll try to come up with another layout for the homepage soon.
merging !


[multistage] fix literal aggregate function not working issue

Codecov Report

Merging #9331 (8ee7571) into master (6047b06) will increase coverage by 32.92%.
The diff coverage is 100.00%.

:exclamation: Current head 8ee7571 differs from pull request most recent head 804f328. Consider uploading reports for the commit 804f328 to get more accurate results

@@              Coverage Diff              @@
##             master    #9331       +/-   ##
=============================================
+ Coverage     28.37%   61.29%   +32.92%
- Complexity       53     4907     +4854
=============================================
  Files          1867     1867
  Lines         99608    99618       +10
  Branches      15167    15170        +3
=============================================
+ Hits          28260    61064    +32804
+ Misses        68608    33946    -34662
- Partials       2740     4608     +1868

Flag
Coverage Δ

integration1
26.14% <0.00%> (+0.02%)
:arrow_up:

integration2
?

unittests1
67.11% <100.00%> (?)

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

Impacted Files
Coverage Δ

...inot/query/runtime/operator/AggregateOperator.java
84.37% <100.00%> (+84.37%)
:arrow_up:

...t/core/plan/StreamingInstanceResponsePlanNode.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ore/operator/streaming/StreamingResponseUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...server/starter/helix/SegmentReloadStatusValue.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../operator/blocks/results/MetadataResultsBlock.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ager/realtime/PeerSchemeSplitSegmentCommitter.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...urces/ServerReloadControllerJobStatusResponse.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...t/broker/broker/BasicAuthAccessControlFactory.java
0.00% <0.00%> (-90.91%)
:arrow_down:

...t/plugin/minion/tasks/purge/PurgeTaskExecutor.java
0.00% <0.00%> (-90.91%)
:arrow_down:

...ator/streaming/StreamingSelectionOnlyOperator.java
0.00% <0.00%> (-90.00%)
:arrow_down:

... and 1156 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Document Go SDK client usage

Add information on Go SDK installation
=> Also include information on generating go protobuf files
Add information on Go SDK usage for constructing a client
=> Used intkey as an example to demonstrate client application
development, this is in sync with document on other
languages
Add information on Go SDK for submitting a request to validator
[minor] Change from tab to space for Go TP doc section

Will upload working intkey Go client code soon to Sawtooth SDK Go repository.
Signed-off-by: S m, Aruna<EMAIL_ADDRESS>

@dcmiddle @chenette

Corrected lexer part, thanks.

I guess rebase is required here to make the build pass.

Commits are rebased and build passed.


Zipline bundle ingest too slow

Dear Zipline Maintainers,
Daily update for zipline ingest -b bundle_name takes too long, considering only one row is new for every symbol.
Currently ingest update every time all data.
There are 2 options which could improve the situation:

Zipline bundle update function
Ability to connect zipline to sql database directly and skip ingest

Please let us know what are advantages and disadvantages of each solution.
Kind Regards
S

+1

+1
It would be good to even get some tips on speeding up ingesting, or allow it to run in parallel (it runs per asset, this should be simple to run in parallel?). I am resorting to investigating manually creating the bcolz format files by bodging together my own ingest function so I can speed it up - I'm ingesting custom data and it takes around 24 hours just to ingest, so can't even run it daily for new daily data!

+1


Enable KDE integration in LibreOffice

Project description
LibreOffice has new KDE integration. This can be enabled with --enable-qt5 --enable-kde5.
Enabling these flags lets LibreOffice detect the appropriate integration. On Plasma, it will use Qt widgets. On GNOME it will use GTK widgets.
Here is the latest talk describing this improvement.
https://conf.linuxappsummit.org/en/LAS2019/public/events/60
Metadata

homepage URL: https://www.libreoffice.org/
source URL: https://donate.libreoffice.org/home/dl/src/6.3.3/all/libreoffice-<IP_ADDRESS>.tar.xz?idx=1
license: MPLv2.0 (secondary license GPL, LGPLv3+ or Apache License 2.0)[9]
platforms: all

@7c6f434c Pinging the LibreOffice maintainer on this issue.

I am really unlikely to test it (I haven't used KDE nor GNOME for ages), but willing to merge a PR if someone does test this.

I'm willing to test it, but unsure how to patch it. Should we keep kde4 integration?

Is kde4 still in Nixpkgs? If no, then I think it is OK to replace the integration.
I hope that passing some amount of Qt5 libraries as buildInputs and some Qt5 build tools as nativeBuildInputs and replacing the integration configure flags should be enough. It is OK to do this only in default.nix, still.nix gets overwritten by default version when Fresh/Still minor versions get incremented upstream (and we package this update)

IDK what versions of Libreoffice you people package, but kde4 has been deprecated from Libreoffice 6.3 on. In Libreoffice 6.2 both kde4 and kde5 can be built, but are mutually exclusive at runtime so you can't have both.
But kde5 in 6.2 is in pretty good shape and we keep backporting critical bugfixes (although we haven't had one in months :-)) For example we backported all of the threading bugfixes, so should you people deploy any extensions, they no longer deadlock

On master branch Still is 6.2, Fresh is 6.3. Thanks for the overview.

I've done some experimenting. So far I cannot get qmake to run properly:
Skipping configure process.QMAKEPATH=/nix/store/kv6mipfp13cl4m39c33a7kn0b3yzjs1v-qtbase-5.12.5-dev
qmake PREFIX=/nix/store/pfli681v3iskil5whl0r17q8zifrza46-libreoffice-<IP_ADDRESS> NIX_OUTPUT_OUT=/nix/store/pfli681v3iskil5whl0r17q8zifrza46-libreoffice-<IP_ADDRESS> NIX_OUTPUT_DEV=/nix/store/kxsnvnhqg644by2kyydjvhmqgzv49fyf-libreoffice-<IP_ADDRESS>-dev NIX_OUTPUT_BIN=/nix/store/pfli681v3iskil5whl0r17q8zifrza46-libreoffice-<IP_ADDRESS> NIX_OUTPUT_DOC=/nix/store/kxsnvnhqg644by2kyydjvhmqgzv49fyf-libreoffice-<IP_ADDRESS>-dev/share/doc/qt-5.12.5 NIX_OUTPUT_QML=/nix/store/pfli681v3iskil5whl0r17q8zifrza46-libreoffice-<IP_ADDRESS>/lib/qt-5.12.5/qml NIX_OUTPUT_PLUGIN=/nix/store/pfli681v3iskil5whl0r17q8zifrza46-libreoffice-<IP_ADDRESS>/lib/qt-5.12.5/plugins
Usage: qmake [mode] [options] [files]

It would be interesting to compare the build output with that of a passing build. Is there a log of a build for some other distro available somewhere?

Noticed this is a duplicate of #57846 and probably should be closed now or when #68414 lands.

You are right, it's a duplicate.


fix: custom redis configuration for the container

The current custom Redis configuration for the RSTUF Worker container doesn't work correctly.
The backend result custom port is not corrrectly parsed for the callbacks (signals) and in the default Celery Backend
Signed-off-by: Kairo de Araujo<EMAIL_ADDRESS>

Codecov Report
Base: 99.34% // Head: 99.34% // No change to project coverage :thumbsup:

Coverage data is based on head (8e76b20) compared to base (69d45c8).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #147   +/-   ##
=======================================
  Coverage   99.34%   99.34%
=======================================
  Files           7        7
  Lines         457      457
=======================================
  Hits          454      454
  Misses          3        3

Impacted Files
Coverage Δ

app.py
100.00% <100.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Improve the carousal on home-page .

I've contributed significantly to this repo. I want to do this one as well!

@gautam-bhagat  okk fine  i have assigned this to you attach screen shot once done


Feature request: add a "Show read notifications" setting

📝 Provide a description of the new feature
Thanks to the (coming 🤞) new Mark notification as done button (see #500 & #706), I think we could add a new "Show read notifications" setting, to better mimic the default Github's notifications experience.
The workflow would be the following:
With the setting ON:

You get a new notification, it appears in Gitify
You click on this notification, it opens and Github and automatically gets marked as "read"
It still appears inside Gitify, with a grey background, and you have the ability to click the new Mark as done button to make it disappear

With the setting OFF:

You get a new notification, it appears in Gitify
You click on this notification, it opens and Github and automatically gets marked as "read"
It doesn't appear inside Gitify anymore

➕ Additional Information
I'm willing to work on this if you think it could be a new feature!

I second this!
It's really annoying, because currently once you click the notification in Gitlify it disappears from there permanently and there's no way to go back to it. It would be incredibly useful to add a filtering option to show all the notifications.
It would also be convenient to add a Mark as read button that would turn to Mark as unread for the read notifications.

I second this! It's really annoying, because currently once you click the notification in Gitlify it disappears from there permanently and there's no way to go back to it. It would be incredibly useful to add a filtering option to show all the notifications.

Time to dust off #1052 - though I like the suggestion of moving it to be a "filter" type (I've done similar with atlassify.io actually)

It would also be convenient to add a Mark as read button that would turn to Mark as unread for the read notifications.

Unfortunately, as best as I could tell, there isn't any public API for mark as unread - https://github.com/gitify-app/gitify/issues/890


feat: ability to use ServerSideEncryption for S3 uploads

This PR allows users to enable Server-Side Encryption (SSE) for S3 uploads through the use of the  METAFLOW_S3_SERVER_SIDE_ENCRYPTION configuration setting.
See this PR for prior conversations regarding the topic.

@saikonen just wondering if anything else is needed from our side before we can get this merged, not sure if those failing checks are a blocker? Let us know if you need anything!


Sane minimum resource requests for Seed's metrics server

How to categorize this issue?

/area auto-scaling
/kind enhancement
/priority normal
What would you like to be added:
Provide sane minimum resource requests for Seed's metrics server to prevent it from being CPU throttled.
If it is throttled it cannot provide the necessary metrics for its own VPA and any Shoot cluster in the Seed.
This leads to horizontal scaling not working for Shoot kube-apiservers.
cc @mvladev
Why is this needed:
We have seen cases when the metrics server of a Shooted / ManagedSeed cluster got CPU throttled.
It could not serve the Metrics API any more.
k describe hpa kube-apiserver-fdjl
  Warning  FailedGetResourceMetric  99s (x744 over 6h16m)  horizontal-pod-autoscaler  missing request for cpu

In turn, the vpa recommendations for the deployment of the metrics server itself were also not adjusted.
So it never scaled up.
The CPU limits for the metrics server in the kube-system ns of the Seed were very low:
kubectl -n kube-system describe vpa metrics-server
RecommendationProvided
  Recommendation:
    Container Recommendations:
      Container Name:  metrics-server
      Lower Bound:
        Cpu:     22m
        Memory:  225354966
      Target:
        Cpu:     23m
        Memory:  225384266
      Uncapped Target:
        Cpu:     23m
        Memory:  225384266
      Upper Bound:
        Cpu:     24m
        Memory:  240035464

In comparison to another Seed of similar size:
  recommendation:
    containerRecommendations:
    - containerName: metrics-server
      lowerBound:
        cpu: 22m
        memory: "203680514"
      target:
        cpu: 35m
        memory: "203699302"
      uncappedTarget:
        cpu: 35m
        memory: "203699302"
      upperBound:
        cpu: 36m
        memory: "213093882"

Provide sane minimum resource requests for Seed's metrics server to prevent it from being CPU throttled.

I guess, this is not only related to Seed clusters but to Shoot clusters in general, right?
In the particular case you observed, was the VPA enabled for the Shoot?

In the particular case you observed, was the VPA enabled for the Shoot?

Not at first, but we enabled it.
I am just thinking that we need higher minimum resource requests for metric servers of Seed clusters because they'll have a higher load.

Actually, the minAllowed is not set for the metrics-server VPA https://github.com/gardener/gardener/blob/5a13e6b11a5452e51c0f010c3839319b8f8b67e6/pkg/operation/botanist/systemcomponents/metricsserver/metrics_server.go#L393-L408.

/assign


Clean up copy_url code

Copy_url is a bit of a mess -- see https://chat.openai.com/c/dc37083d-57c7-4e2f-95d8-93abdf7aa21b

This was fixed with this effort: https://github.com/oaustegard/bookmarklets/blob/main/copy_url_as_link_README.md


Prebuild trafficserver for Dev CDN-in-a-Box

This PR

Adds a workflow that builds and pushes the ghcr.io/apache/trafficcontrol/ci/trafficserver-alpine Docker image
Updates the t3c docker-compose service of the Dev CDN-in-a-Box to be based on the ghcr.io/apache/trafficcontrol/ci/trafficserver-alpine image, which decreases the build time of the t3c service's image from 7 minutes to about 30 seconds on my computer (and decreases the image build time in #6588 from 14 minutes to 1.25 minutes).

Which Traffic Control components are affected by this PR?

Dev CDN in a Box
Automation - GitHub Container Registry

What is the best way to verify this PR?

Push the zrhoffman:ghcr.io/apache/trafficcontrol/ci/trafficserver-alpine branch to the master branch of your Traffic Control fork
Go to your fork -> Actions -> Container ghcr.io/apache/trafficcontrol/ci/trafficserver-alpine workflow and manually trigger the worflow
Wait for the workflow to complete (~14 minutes)
Verify that https://github.com/<Your Fork>/trafficcontrol/pkgs/container/trafficcontrol/ci/trafficserver-alpine was created

PR submission checklist

[x] This PR has tests
[ ] This PR has documentation
[ ] This PR has a CHANGELOG.md entry
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Overwriting only the Go version in this file in https://github.com/apache/trafficcontrol/commit/9d1b0fe64b25a77f89d19780280d886b92d1a6e0

Do you have a place you already tested that that I could look at to see it working?

Overwriting only the Go version in this file in 9d1b0fe

Do you have a place you already tested that that I could look at to see it working?

Sure, it's passing on my fork here


udunits items

From Lars Bärring:

UDUNITS is mentioned as one theme for the housekeeping session. I have
done a bit of preliminary work in relation to this, just to identify
where UDUNITS is referenced in a more specific way than just linking to
the homepage over at UNIDATA. For many (maybe all) of those places I
have for myself some questions and thoughts.
As I am a git/asciidoc anti-guru I have just extracted those pieces
into a document and added my thoughts as comments into a pdf file
(attached), which maybe could serve as a starting point for some
further work, or just folded into an electronic paper plane and thrown
out the Windows.

CF Conventions text -- annotated UDUNITS refs.pdf

In https://github.com/cf-convention/cf-conventions/issues/298#issuecomment-866190249, Steve Emmerson says: Unidata documentation seems to favour "UDUNITS"

This is done, but still needs to be merged after the 3w deadline has passed - apologies for being too trigger happy, I was trying to clean things up so that we have as clean a slate as possible for finishing the week. See the corresponding PR - I will rebase those commits onto the Conventions in 3 weeks pending objections.

The associated PR will also take care of #260, which consequently can be closed together with this one.

These changes look fine to me, thanks.


Explorative analysis on best practices for saving clients api key

Useful resources:

https://romsbotframeworkarr.azurewebsites.net/2018/04/23/general-data-protection-regulation-gdpr/
https://stackoverflow.com/questions/48532285/store-and-access-user-secrets-credentials-on-bot-framework-best-practice
https://docs.microsoft.com/en-us/azure/key-vault/
https://stackoverflow.com/questions/52016229/how-to-store-the-api-keys-of-my-clients-in-a-secure-way
https://stackoverflow.com/questions/37951220/storing-api-keys-on-server

While the best solution is still OAuth2 clockify support, we can improve security by using a separate database for keys/sensitive information and encryption.
Evaluate if Azure Key Vault fits our use case.

Azure key vault seems a good fit to store API keys, in this way we have both separation and encryption.


Integration tests are failing

Currently the integration tests are failing, and I'm not sure why. Some investigation is needed here.

Worked fine for the. most recent pull request

Oh I think I fixed at the time? Closing now, thanks for checking @noenfugler :)

They are still failing actually, reopening this. It seems to fail at authentication, but I didn't look into why.

This got corrected with my work on authentication in the #28 PR.
Tests now pass (except on 3.7, for other reasons.)
Closing for now.


Token and bad code

This PR fix #389
Split the token_remover in two functions, one that checks that there is a token in the message (is_token_in_message), and the other takes the actions (deleting the message, etc.)
This new function is_token_in_message is reused in cogs/bot.py to know if the poorly formatted code contains a token. If it true, then the embed message is not displayed, since token_remover.py is already in charge.

@sco1 Hi, I am sorry but I am not sure about what you mean. Do you say the bot should also checks if a message contains a token every time a message is edited?

Yes

@kraktus any ETA on when you can add the requested changes from @sco1? We can't merge until that's done.

Pretty busy right now, will do it as soon as I can.

Not sure about using a classmethod or a static method.

In case it is not clear, I changed my code to respond to the requested changes.

A conflict was introduced here due to #681


Definition of Goal-Oriented Skills

Benefit Hypothesis
Having skill templates for common dataspace situations will help the use case and application developers to implement their business logic
Skills typically enwork data (assets) from the preconditions to the final output.
Assets need to be restricted/found on the meta-level in the reverse direction (from the goal type to the precondition type)
Having a template which can bring both directions together in a ping-pong style will allow very flexible data processing patterns.

Beneficiaries
any use case developer
any application developer

Acceptance Criteria
Necessary extensions to the CX-0084 and CX-0067 standards related to the description of input and output types of assets
Skill Template
Example Skill realising ping-pong behaviour
Invocation of remote skills
Aggregating individual results
Calling the Catalogue Graph as an Asset

Estimated Story Points:
16 SP

please also integrate the acceptance criteria of https://github.com/eclipse-tractusx/sig-release/discussions/203#discussioncomment-7324180

Story "Extend Catena-X Standards with SHACL-Descriptions of Graph Assets"
Repository https://github.com/eclipse-tractusx/eclipse-tractusx.github.io
Statement
As a Catena-X stakeholder, I want to have a standard for describing graph assets which allows me to describe the actual shape/content of a graph in a fashion that could be used to drive a meta-computation.
Acceptance Criteria

standard CX-0084 extended
optionally CX-0067 extended
descriptions of examples in both the standard and the kit

Estimation
5 SP

Story "Build a Blueprint and an Example Set of Assets and a Skill Demonstrating Goal-Oriented Computations"
Repository https://github.com/eclipse-tractusx/eclipse-tractusx.github.io
Statement
As a Graph or Skill Asset developer/deployer, I want to have a blueprint and realistic example which shows me how to encode a goal-oriented skill such that I can adopt this for my own use case.
Acceptance Criteria

blueprint with SPARQL snippets
set of asset descriptions
ready-made skill

Estimation
5 SP

Story "Document Some Important Features in the Agent Kit"
Repository https://github.com/eclipse-tractusx/eclipse-tractusx.github.io
Statement
As a KA developer, I want to have documented examples for important standard features, such as remote skill invocation, aggregation and dealing with the catalogue such that I can make use of them in my creation and invocation of skills.
Acceptance Criteria

Example for the invocation of remote skills in both distribution/run modes
Example for aggregating (in subselects)
Example for binding against the catalogue

Estimation
3 SP

Hi @drcgjung and @TomBuchertTSystems could we close this issue? seems that is already done?


Update Brakeman

Builds are failing with Brakeman 6.1.2 is not the latest version 6.2.1

Seems fine now


Insanely slow training (40 epochs in 8 hours)

I'm not sure what happened but it used to be 3 minutes per epoch on my GPU (GTX 1660 6Gb) now it takes about 40 epochs in 8 hours.  What happened?  Changing "fp16" to true doesn't help, nor does raising or lowering my CPU processes or the batch size.  I've tried all kinds of variations.  What might help?  Thanks.

are you now using the same size / length for dataset as previously?
you see, bigger the dataset, longer it takes.
As an example of the time on tesla t4:  15 min set, sub 20-30 secs for an epoch, sub 40-45 mins of set, 1-1.5 min for an epoch


epinio info can't determine versions when running on minikube

Epinio (v0.0.23) on minikube (minikube v1.22.0 on Opensuse-Tumbleweed; Preparing Kubernetes v1.21.2 on Docker 20.10.7) is unable to determine component versions:

> epinio info
✔  Epinio Environment
Platform: unknown
Kubernetes Version: unknown
Gitea Version: unavailable
Epinio Version: unavailable

Switching to k3d makes epinio info succeed:

> epinio info
✔  Epinio Environment
Platform: k3s
Kubernetes Version: v1.21.2+k3s1
Gitea Version: unavailable
Epinio Version: v0.0.23-4-ge431127

> TRACE_LEVEL=6 epinio info
2021/09/01 15:49:23 EpinioClient/Info "level"=1 "msg"="start"
2021/09/01 15:49:23 EpinioClient "level"=1 "msg"="GET https://epinio.<IP_ADDRESS>.omg.howdoi.website/api/v1/info"
2021/09/01 15:49:23 EpinioClient "level"=2 "msg"=""
✔  Epinio Environment
Platform: unknown
Kubernetes Version: unknown
Gitea Version: unavailable
Epinio Version: unavailable
2021/09/01 15:49:23 EpinioClient/Info "level"=1 "msg"="return"

Note the IP address is ending with .0 and ip r shows it as the network address. See #635.

> ip r
<IP_ADDRESS>/24 dev br-275de270ed6c proto kernel scope link src <IP_ADDRESS>

And epinio push shows that the underlying issue is #635 indeed:

> epinio push app1
🚢 About to push an application with given name and sources into the specified namespace
Name: app1
Sources: /abuild/projects/rancher/epinio/example-12factor
Namespace:
⚠  Hit Enter to continue or Ctrl+C to abort (deployment will continue automatically in 5 seconds)
Create the application resource ...
error pushing app to server: Post "https://epinio.<IP_ADDRESS>.omg.howdoi.website/api/v1/namespaces//applications": dial tcp <IP_ADDRESS>:443: connect: network is unreachable

Now I'd argue that the bug is also in epinio info, not showing the API access error.

Part of the problem is the Client.Info() implementation, not reporting errors.


Command Failed Error for Toggle Annotations

Hi there; the "Toggle Annotations" tab keeps appearing for this embedded ClearCase error - it keeps disappearing and reappearing making my code jump every few lines I write. Has anyone seen thie "use no checkouts option" error?

This is a known limitation, because clearcase doesn't allow to annotate a checked-out file.
If you pass the –nco parameter to the cleartool annotate command it just annotate the previous version which probably differ from the checked out one ( thus making the annotated scrambled ).

Just had the same problem. Would it be possible to detect this error condition and issue a more informative error message?


*:Fix MppInfo saving reference to temporary object.

What problem does this PR solve?
Issue Number: close #4476
Problem Summary:
pr #4610 revert the changes in #4477
What is changed and how it works?
Save a copy instead of an reference.
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-sanitizer-test asan tsan

/run-all-tests

/cc @JaySon-Huang @SeaRise @fuzhe1989

/merge


Futrell2018 SPRT benchmark using GAMs + control predictors

I'm starting a benchmark implementation for reading time evaluation that uses control predictors (word length and frequency; spillover effects from previous word(s)) as well as a more advanced statistical model (GAMs).
FWIW this PR is also a fun test case of a benchmark with Conda dependencies (needs R and an R package, which obviously can't be installed via pip).
Still to-do (& happy to accept help if anyone is interested):

[ ] Predict both RT mean and variance. Recent studies have argued that between-subject RT variance is meaningfully related to surprisal. Use the Gaussian location-scale implementation included in mgcv.
[ ] Held-out evaluation. Currently the benchmark evaluates on the training data, yikes
[ ] Test code

Hi @hans just checking in on this PR


Can't access the Dreamview web, please help

After executing the three commands sucessfully :"bash apollo.sh build; bash apollo.sh release;bash scripts/bootstrap.sh", I use the firefox to acess the http://localhost:8888, but the firefox display "Firefox can’t establish a connection to the server at localhost:8888." .  The snapshot is as below:

OS: ubuntu14.04
Browser: firefox 61.0.1
apollo: 3.0

How to fix the problem? Thanks！

@jt387 Could you try to pull the latest code, and check again?

Exit docker
Pull the latest code
Restart docker
Get into docker
Run apollo.sh build

Let me know if you get any errors along the way.

You can also refer to https://github.com/ApolloAuto/apollo/blob/master/docs/howto/how_to_debug_dreamview_start_problem.md for troubleshooting.

@natashadsouza @siyangy Thanks, they are very useful！ I find that the problem is the same with https://github.com/ApolloAuto/apollo/issues/4388, and I solve the problem following the advices.Thanks again!

changing the command "supervisorctl start dreamview  >  /dev/null" to "supervisorctl start dreamview" in the bootstrap.sh file, and run "bash scripts/bootstrap.sh",  the error "unix:///tmp/supervisor.sock refused connection"  is showed.


Unclear questions 1

changed:form_dark_latex_wolf_pup makes an error while eating any food
It is caused by a conflict with a certain module (definitely)
crash-2024-08-11_23.04.54-server.txt

It is highly likely that there is a conflict with the Not Enough Animations mod

It turns out that any form not supported by the model will cause the game to crash, and it is likely to be associated with mods related to player model animations.

Stack overflow exception, caused by unintentional recursion from ItemStack mixins.


Styles: Migration to Emotion v11

Looks like Emotion v11 came out!

🆙 Upgrades
I haven't tried the v11 yet. Based on the post, it looks like there are a couple of things we need to adjust in create-styles to make it compatible with v11.
Stylis

plugins written for the former Stylis v3 are not compatible with the new version. To learn more on how to write a plugin for Stylis v4 you can check out its README and the source code of core plugins.

I'm aware that Stylis v4 is substantially different than v3 (which was what powered Emotion and Styled Components). I haven't had any experience with Stylis v4 yet.
We'll had to rewrite the current plugins in create-styles to work with the new Stylis v4 middleware layer (previously referred to as "plugins").
Emotion Cache

The key option is now required when creating a custom instance of a cache. Please make sure it’s unique (and not equal to 'css') as it’s used for linking styles to your cache.

This one isn't a huge deal. We may have to change the prefix to something else, perhaps wp-css or something. If we do, we'll have to update all of our screenshots, and perhaps some of the create-styles code that may be looking for .css- specifically.
There's probably more to all of this. My sense is this won't be too bad. I expect all of the upgrades to happen within create-styles. A lot of the code there is modularized, which may make it easier to target and tweak things.

❓Should we upgrade?
There's also the question of whether we should or not. At the moment, Gutenberg is using Emotion v10.
Multiple emotion instances should not be a problem. For example, G2 Components can be used within Gutenberg without any conflicts (dedicated style system and all).
I'm not sure about Emotion V11 (if G2 Components upgrades) + Emotion V10 (Gutenberg).
I'm guessing it should be okay?
Would love some thoughts on this :)
cc'ing @saramarcondes

Chatted with @saramarcondes briefly on this. I think we'll hold on the upgrade for now, since Gutenberg is currently on Emotion v10.
Will keep this issue open, but removing from the "Prep" milestone

Bumping this! Emotion 11 was something @saramarcondes had mentioned recently during the G2 -> Gutenberg integration process.
I'll be looking into this to see how we can elegantly migrate to Emotion V11 in the create-styles package.

Bumping this! Emotion 11 was something @saramarcondes had mentioned recently during the G2 -> Gutenberg integration process.
I'll be looking into this to see how we can elegantly migrate to Emotion V11 in the create-styles package.

It looks like @emotion/create-instance would be a good place to start:
https://github.com/emotion-js/emotion/blob/master/packages/css/src/create-instance.js

It looks like @emotion/create-instance would be a good place to start:
https://github.com/emotion-js/emotion/blob/master/packages/css/src/create-instance.js

Update! Looks like swapping create-emotion with @emotion/css/create-instance works!
The only hiccup is Stylis. Stylis V4 is very different (mentioned in the original issue).
We'll need to make some adjustments there to ensure the plugins work correctly

Update! Looks like swapping create-emotion with @emotion/css/create-instance works!
The only hiccup is Stylis. Stylis V4 is very different (mentioned in the original issue).
We'll need to make some adjustments there to ensure the plugins work correctly


Confusion about the implementation of the weighted mask

Hi!

In the paper, the weighted mask is mutiplied on the product of Q and K. However, in the code, the refmask.masked_fill() is added to the sim_ref. In this case, weight on the mask is not multiplied to QK, but added. May I know the difference between these two strategies, which seem different ? Or my understanding is wrong ?
In addition, may I know what is the recommend weight value for single concept customization ? Is it still 3 ?

using addition or multiplication is both a good choice, we just need a method to emphasize the given concepts.

I understand that mask_fill() with -inf is for suppressing the unwanted part in K. But in the addition setting, the weight on the mask is just added to the original attention value. It is not that intuitive that how the added weight value can affect the original attention value to make the Q to attend more to the masked K. Could you elaborate more on this ?

I understand that mask_fill() with -inf is for suppressing the unwanted part in K. But in the addition setting, the weight on the mask is just added to the original attention value. It is not that intuitive that how the added weight value can affect the original attention value to make the Q to attend more to the masked K. Could you elaborate more on this ?

Actually, mask_fill() with -inf is used to suppress the unwanted part in the attention map, which is the sim_ref in the code. The weighted mask is not for the feature K, but for the attention map. It is used to emphasize the area of the attention map corresponding to the reference concepts.


Package PEG project components for publication

As discussed at UA team meeting.
Jessica:

[ ] Pull out growth rate modeling into separate repo
[ ] Document and test reproducibility
[ ] Add growth rates to latest version of MAC season 4 and 6 data?

Kristina:

[ ] summarize NEON data curation (should NEON datasets be separated? more clearly described?)
[ ] separate EFI forecasts into separate repo and update README (model details, automated submission details)
[ ] Archive code (ask Tyson)

Moved models folder, with all commits, from neon-datasets into a new repo neon-efi-challenge. Updated the two READMEs.
Need to replace the neon-datasets repo on the submission server with the neon-efi-challenge one, and test that it's still working correctly.

Archived curated NEON datasets on CyVerse in genophenoenvo NEON data folder.

Follow up issues created


CupertinoTextField: added ability to change placeholder color

Resolves #24175
https://github.com/flutter/flutter/projects/9#card-14775899

I signed it!

I signed it!

I signed it

I signed it

I signed it

Should I change anything to resolve this PR?

@Nizarius would you mind correcting the analysis issues?

@matthew-carroll yeah, of course.
By the way, it seems that it will be better to make not only placeholder color modifiable, but all the placeholder style at once. What do you think?
If you can make issue for that I can make pr to it. Because it's highly likely that developers want more that change only placeholder color (for example, I want to modify font weight too and so on).

@Nizarius yes, I think we should allow an arbitrary TextStyle in a property called placeholderStyle.  Let's do that here.  We wouldn't want to merge in color support and then immediately replace it.  Can you update this PR accordingly, and ensure that all checks pass?
Also, would you mind adding some tests for this new behavior?

@matthew-carroll I updated my PR to pass all the tests.
Frankly speaking, I'm new at Flutter and don't really understand what tests should I add for this new behavior.

Thanks @Nizarius.
@xster let's discuss on Tuesday if we should carry this PR across the finish line.

Sure.
@Nizarius, adding tests does sound a bit overwhelming initially though if you take a look at https://github.com/flutter/flutter/blob/master/packages/flutter/test/cupertino/text_field_test.dart, there are already tons of examples that you can base new tests off of. Some even creates and asserts the styles of the placeholder text. I'd create a new test based off of that one to make sure custom placeholder styles are respected.

@xster @matthew-carroll I fixed code according to your notes and also added test for placeholder's style.

@xster @matthew-carroll hi guys. Is there anything I need to do?

@Nizarius there's some trickiness with the whole TextStyle merge thing that isn't really easy to explain so we tweaked the doc in your branch a bit. Hope that's ok.
The rest of the PR looks good to us. We'll merge it in when our tree is green. Thanks for the contribution.

@xster @matthew-carroll thank you, guys.

Thanks for your contribution


Move from Grpc.Core to grpc-dotnet.

https://grpc.io/blog/grpc-csharp-future/

Yes, that would be very helpful.

#22


Add ibm-foundation operator using direct helm chart

added ibm-foundation operator

left destination as openshift-operators as I think we should be able to install the operator in all namespaces, and have cloud pak for business operator use it from there and not in cloudpak

minor fix for GIT_BRANCH
added cloudpak into infra to have it there for testing cp4a
Only added customize to inject the chart URL for repoURL at the services layer for now and not in infra or apps, until we add the first argocd in that layer to need it

Fixes #123


Overlay not Rotating with Camera

I am having a bug where the overlay is remaining fixed in the camera view despite the camera rotating.

Thanks for opening this issue!
Please make sure you are using Lighty v3.0.0-beta.1+1.20.5. For some reason, CurseForge wrongly suggests Lighty for 1.20.3/4 for versions 1.20.5/6, and I cannot change that. Very weird CurseForge bug.
Anyways, it has been fixed in v3.0.0-beta.1, so make sure you use that.
Thanks for using Lighty, and let me know if this fixes the Problem! Have fun!

Thank you!


Object not inserting into multiple QTNodes

When an object is lying on the edge between two nodes it will only be inserted into one. It prefers the nodes in the following order: top left --> top right --> bottom left --> bottom right with it mostly preffering the top left.

It was caused by wrong ordering in of two boolean values.
Before:
successfullyInserted = successfullyInserted || child!!.insert(obj)

After:
successfullyInserted = child!!.insert(obj) || successfullyInserted


Better introduction

The statement here is misleading: https://github.com/roots/sage#theme-installation

Clone the git repo - git clone https://github.com/roots/sage.git and then rename the directory to the name of your theme or website.

Wouldn't a better statement be?

git clone https://github.com/roots/sage.git my-theme

Or even better to just download the zip and not even worry about git? Considering a user will never be updating Sage?
Additionally its probably best to remove the .git folder.

Thanks.

I've recently inherited a project using Sage, and have been reading docs, and planned making suggestions, and comments towards improving Sage for others like myself with better documentation.
Thus far it seems to be summarized best in your own docs

The fact that Sage goes against “the WordPress way”


Feature request: Media commands

Commands to play/pause/next/previous and maybe even volume up and down.
Should be possible using this.

Of course, mute also ;)

This has been implemented and will be in the next release!


feat: Log chunking

Addresses https://github.com/electric-sql/electric/issues/1581
Will outline work done tomorrow, need to add some more tests as well - also I have deviated from the original design due to this thread.
I have externalised the chunk index from within the log itself but have kept it in storage - this might have a non-trivial impact on performance due to the additional IO involved in 1) storing the checkpoints and 2) reading the checkpoints on every request.
The benefits of externalising the index is that it makes it queriable, so we can still immediately know the end offset of a chunk before actually streaming it, which allows parallelisation of requests etc.

It could be neat to build https://github.com/electric-sql/electric/issues/1534 as part of this PR to check what the browser experience is like.


How to avoid TagManager.initialize() running many times

Hello.
In my React component, I have to get gtm-ID from another data which change many time. Each time this data changes, my component render. And each time component renders, function TagManager.initialize runs again, this create duplicate gtm scripts (as attached).
My code:
useEffect(() => {
   if (data.gtm_id){
     TagManager.initialize({
      gtmId: data.gtm_id,
     });
   }
}, [data.gtm_id])

Could you please advise me how to avoid function TagManager.initialize() to run if it already run?
Thank you.

@seandelaney have you found solution?
Currently I have to check if the above script tag already existed, will do nothing.
But I think this solution is not safe because actually I don't know what this library does in the background.

@vanminhquangtri No solution yet

We have the same issue. Any hacks on this?

I'd recommend to just keep track of gtm_id and check if it was previously used before initialising it again

@vanminhquangtri Based on what you wrote, the initialize function will be called again if data.gtm_id changes. As written, because you have passed data.gtm_id as a dependency on useEffect, it will be called any time it is modified. A potential solution here would be the following:
useEffect(() => {
   if (data.gtm_id){
     TagManager.initialize({
      gtmId: data.gtm_id,
     });
   }
}, []) // Remove data.gtm_id from the dependencies

I couldn't think of anything better than checking existing scripts on the page.
const gtmScriptUrl = 'https://www.googletagmanager.com/gtm.js';

function useGTM(gtmContainerId?: string) {
  React.useEffect(() => {
    // check for existing GTM script for preventing double initialization
    const scriptExists = Array.from(document.scripts).some((script) => {
      if (!script.src) return false;
      const url = new URL(script.src, window.location.origin);
      return url.href.includes(gtmScriptUrl) && url.searchParams.get('id') === gtmContainerId;
    });

    if (scriptExists) return;
    if (!gtmContainerId) return;

    const tagManagerArgs = { gtmId: gtmContainerId };
    TagManager.initialize(tagManagerArgs);
  }, [gtmContainerId]);
}


neovim or vim??

ISSUE Template
Fill the answers for all of the questions below
Do you miss the requirements?
[NO]
Which distribution are you using ?
[Darwin - macOS 10.12.6]
Are you a noob ?
[NO] - vim
[YES] neovim
Hi, are these dotfiles intended for regular vim use or neovim or both?
Cause that works fine with vim-plug! However I just started using neovim (which I had a previous install) but now when I try to  use it I get the following issues when I use nvim:
nvim Gemfile
Error detected while processing /Users/me/.config/nvim/init.vim:
line  537:
E117: Unknown function: airline#section#create
E15: Invalid expression: airline#section#create(['windowswap', '%3p%% ', 'linenr', ':%3v'])
Press ENTER or type command to continue

---

"Gemfile" 30L, 694C
Error detected while processing BufEnter Auto commands for "*":
E492: Not an editor command: EnableStripWhitespaceOnSave
Error detected while processing function OpenNerdTree:
line    3:
E492: Not an editor command:         NERDTreeFind
Press ENTER or type command to continue

:healthcheck (neovim):
  29 health#provider#check
  28 ========================================================================
  27 ## Clipboard (optional)
  26   - OK: Clipboard tool found: pbcopy
  25
  24 ## Python 2 provider (optional)
  23   - WARNING: pyenv was found, but $PYENV_ROOT is not set.
  22     - ADVICE:
  21       - Did you follow the final install instructions?
  20       - If you use a shell "framework" like Prezto or Oh My Zsh, try without.
  19       - Try a different shell (bash).
  18   - INFO: `g:python_host_prog` is not set.  Searching for python2 in the environment.
  17   - INFO: Executable: /usr/local/bin/python2
  16   - INFO: Python2 version: 2.7.14
  15   - INFO: python2-neovim version: 0.2.0 (outdated; from /usr/local/lib/python2.7/site-packages/neovim)
  14   - WARNING: Latest python2-neovim is NOT installed: 0.2.1
  13
  12 ## Python 3 provider (optional)
  11   - WARNING: pyenv was found, but $PYENV_ROOT is not set.
  10     - ADVICE:
   9       - Did you follow the final install instructions?
   8       - If you use a shell "framework" like Prezto or Oh My Zsh, try without.
   7       - Try a different shell (bash).
   6   - INFO: Using: g:python3_host_prog = "/Users/me/.pyenv/versions/3.4.3/bin/python"
   5   - INFO: Executable: /Users/me/.pyenv/versions/3.4.3/bin/python
   4   - ERROR: Command error (job=8): '/Users/me/.pyenv/versions/3.4.3/bin/python' '-c' 'import neovim; print(neovim.file)'
   3     Output: Traceback (most recent call last):  File "<string>", line 1, in <module>ImportError: No module named 'neovim'
   2   - INFO: Python3 version: 3.4.3
   1   - INFO: python-neovim version: unable to load neovim Python module
 50    - ERROR: Neovim Python client is not installed.
   1     Error: unable to load neovim Python module
   2     - ADVICE:
   3       - Run in shell: pip3 install neovim

Also, once I enter thru those warnings and errors, I don't have nerdtree once the file opens. nor do I have it once I hotkey < ctl-n >
WHAT HAPPENED TO MY NEOVIM INSTALL?
please contact me on telegram to debug thru this if you can?? @salsys84 on Telegram

oh! also followed these instructions...
https://vi.stackexchange.com/a/10110
Still nothing! 👎

Well you have to install the python modules.
sudo pip2 install neovim
sudo pip3 install neovim

Closing no respond.