Path added via API, doesn't actually run runOnReady command

Which version are you using?
v0.20.0
v0.19.3
Which operating system are you using?

[x] Linux amd64 standard
[x] Linux amd64 Docker
[ ] Linux arm64 standard
[ ] Linux arm64 Docker
[ ] Linux arm7 standard
[ ] Linux arm7 Docker
[ ] Linux arm6 standard
[ ] Linux arm6 Docker
[ ] Windows amd64 standard
[ ] Windows amd64 Docker (WSL backend)
[ ] macOS amd64 standard
[ ] macOS amd64 Docker
[ ] Other (please describe)

Describe the issue
When adding a path via API, runOnReady command doesn't seem to be invoked.
I cannot see any logs about command errors, or the command being invoked
Describe how to replicate the issue

Start rtsp-simple-server (v 0.20.0) with API control
Add a path via API (let's use curl)

curl localhost:9997/v1/config/paths/add/path_name \
  -X POST \
  -H "Content-Type: application/json" \
  -d {
    "source": "publisher",
    "runOnReady":"echo hello",
    "runOnReadyRestar": false
  }

Path is added succesfully
Publisher publishes to path
runOnReady command starts
(BUG) Nothing happens a simple echo is not executed, command exits with code 0
Publisher stops publishing
runOnReady command stops SIGINT

I have tried changing runOnReady command to:
"echo", "echo hello", <-- This should show logs as shown in this issue: https://github.com/aler9/rtsp-simple-server/issues/828
"curl nginx_server" <-- This should show logs on my nginx server
"ffmpeg -i rtsp path_from_rtsp_server output.mp4" <-- A quick exit with code 0
"sh -c 'echo hello'" <-- A quick exit with code 0
"sh -c 'sleep 5'" <-- A quick exit with code 0
"sleep 20" <-- A quick exit with code 0
I have checked path configuration before doing replication steps:
path output from GET /v1/paths/list
"9cb696b6-6334-49cc-84f2-b72c534acda4": {
      "confName": "9cb696b6-6334-49cc-84f2-b72c534acda4",
      "conf": {
        "source": "publisher",
        "runOnReady": "echo please work",
        "runOnReadyRestart": false,
      },
      "source": {},
    },

Did you attach the server logs?
backend_1                 | INFO:     <IP_ADDRESS>:52722 - "POST /api/paths/check_permission/ HTTP/1.1" 200 OK
rtsp-simple-server_1  | 2022/10/11 10:28:47 INF [path 9cb696b6-6334-49cc-84f2-b72c534acda4] runOnReady command started
rtsp-simple-server_1  | 2022/10/11 10:28:47 INF [RTSP] [session 820221963] is publishing to path '9cb696b6-6334-49cc-84f2-b72c534acda4', with TCP, 1 track (Generic)
rtsp-simple-server_1  | 2022/10/11 10:28:47 INF [path 9cb696b6-6334-49cc-84f2-b72c534acda4] runOnReady command exited with code 0
rtsp-simple-server_1  | 2022/10/11 10:55:37 INF [RTSP] [conn <IP_ADDRESS>:55854] closed (terminated)
rtsp-simple-server_1  | 2022/10/11 10:55:37 INF [path 9cb696b6-6334-49cc-84f2-b72c534acda4] runOnReady command stopped

Did you attach a network dump?
no

@robertmielewczyk and @aler9 ,
I am having the same issue as robert even without using the API. I never see the echo print in the docker logs
All i see is "runOnReady command started" and "runOnReady command exited with code 0" for the path

It appears the echo command is missing from my rtsp-simple-server docker container while it exists in a janus docker container
What am I missing?
ubuntu@oakb1:~/rtsp-simple-server$ docker exec -it janus echo hello
hello
ubuntu@oakb1:~/rtsp-simple-server$ docker exec -it rtsp-simple-server echo hello
OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "echo": executable file not found in $PATH: unknown
ubuntu@oakb1:~/rtsp-simple-server$ docker exec -it rtsp-simple-server /bin/echo hello
OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "/bin/echo": stat /bin/echo: no such file or directory: unknown
ubuntu@oakb1:~/rtsp-simple-server$ docker exec -it rtsp-simple-server /usr/bin/echo hello
OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "/usr/bin/echo": stat /usr/bin/echo: no such file or directory: unknown

Aha!
The default docker image does not have ffmpeg
I need a more full featured Dockerfile such as the one below for echo and ffmpeg to work
ubuntu@oakb1:~/rtsp-simple-server$ cat Dockerfile
FROM aler9/rtsp-simple-server AS rtsp

FROM alpine:3.14
RUN apk add --no-cache ffmpeg

COPY --from=rtsp /rtsp-simple-server /
#COPY rtsp-simple-server.yml /

ENTRYPOINT [ "sh", "-c", "/rtsp-simple-server" ]

ubuntu@oakb1:~/rtsp-simple-server$ docker build -t asetlur13/rtsp-simple-server .

ubuntu@oakb1:~/rtsp-simple-server$ cat docker-compose.yml
version: '3.6'

services:
  rtsp-simple-server:
    container_name: rtsp-simple-server
    network_mode: host
    volumes:
      - ./rtsp-simple-server.yml:/rtsp-simple-server.yml
    environment:
      - TZ=America/Chicago
      - RTSP_RTMPENABLE=true
    #image: aler9/rtsp-simple-server
    image: asetlur13/rtsp-simple-server
    restart: always
ubuntu@oakb1:~/rtsp-simple-server$

Now echo and ffmpeg work
ubuntu@oakb1:~/rtsp-simple-server$ docker-compose up -d
Creating rtsp-simple-server ... done
ubuntu@oakb1:~/rtsp-simple-server$ docker exec -it rtsp-simple-server echo hello
hello
ubuntu@oakb1:~/rtsp-simple-server$

thank you @saket424
Changes applied in order to fix the problem:

Changed docker-compose.yml

rtsp-simple-server:
    build:
      context: config/dockerfiles/
      dockerfile: rtsp-simple-server.Dockerfile
    volumes:
      - type: bind
        source: ./config/rtsp-simple-server.yml
        target: /rtsp-simple-server.yml
    restart: always

Added rtsp-simple-server.Dockerfile

FROM aler9/rtsp-simple-server:v0.20.0 AS video-server

FROM alpine:3.17
RUN apk add --no-cache ffmpeg
RUN apk --no-cache add curl

COPY --from=video-server /rtsp-simple-server /

ENTRYPOINT [ "sh", "-c", "/rtsp-simple-server" ]

logs after aplying fix
rtsp-simple-server_1  | 2022/11/30 14:16:15 INF [RTSP] [session 158779442] is publishing to path 'test', with TCP, 1 track (Generic)
rtsp-simple-server_1  | hello message from run_on_ready
rtsp-simple-server_1  | 2022/11/30 14:16:15 INF [path test] runOnReady command exited with code 0
rtsp-simple-server_1  | 2022/11/30 14:16:15 INF [RTSP] [conn <IP_ADDRESS>:50524] closed (terminated)


Fix deprecation warning

This pull request fixes the following deprecation warning:
CLI options definitions were upgraded with "type" property (which could be one of "string", "boolean", "multiple"). Below listed plugins do not predefine type for introduced options:
 - Crypt for "name", "text", "save"

@marcy-terui can you please re-open this pull request? GitHub has started closing pull requests now when forks are deleted.


v3

BREAKING CHANGES: task.close() rename
closes #55

[ ] Add types for comment file objects
[ ] Extract projectColors to only "colors"


Support for Swift 4.2

Would like support for Swift 4.2, currently cannot use Qualaroo with Xcode 10 GM.

Hi @eneko!
Could you please try our latest release: https://github.com/qualaroo/QualarooSDKiOS/releases/tag/1.8.2
It's been recompiled in order to work with Xcode 10.
Sorry it took so long.

HI @scana,
Testing this now, it seems that 1.8.2 is not yet available via CocoaPods?
Eneko

Never mind, I see the update now.


[BUG] [RULES] False positive on "JBoss deprecated logging annotations" jboss-eap5and6to7-java-09000

Is there an existing issue for this?

[X] I have searched the existing issues

Konveyor version
0.5 beta 1
Priority
Undefined (Default)
Current Behavior
No response
Expected Behavior
No response
How Reproducible
Always (Default)
Steps To Reproduce
No response
Environment
No response
Anything else?
Tested with Kantra b0.5 beta1
Target: eap8 (and others)
Source: none
Source code used: https://github.com/sonatype/nexus-public
Rule triggered: jboss-eap5and6to7-java-09000 JBoss deprecated logging annotations
Report: https://drive.google.com/file/d/1TbdLS4_728DgxbB88F7YcXw84jK2elty/view?usp=drive_link
This rule reported 11 incidents for the application, all of them were related to annotations or other elements on unrelated packages.

Confirmed I can still reproduce this on 0.5.0. The results are not as many as the reporter but still seeing false positives on this rule.


Generic attribute bag shared by all filters

I was under the impression that the RequestInfo::FilterState (per request or per connection) is an object that can be modified by multiple (successive) filters. It turns out that its a write-once and read only object. @curiouserrandy any reason why you set the shared requestInfo::Filterstate to be a write-once thing instead of a model where multiple filters can write to same object?
I propose we move towards a generic attribute bag kind of system, such that the filters in a chain can append/update any attributes they want for that connection or request. This will allow all the reporting filters to consume info generated by all downstream filters, and emit access logs/reports with info gathered by everyone. Similarly, this will allow policy engines to act on data (about connection/request) gathered by multiple filters which have their own domain expertise.
For example, consider a stack that has
mongo+rbac+tcp_proxy+access_log
proprietary_decoder+rbac+tcp_proxy+access_log
hcm+oauth_filter+rbac+router+access_log
In all these cases, the RBAC filter does not have to know the semantics of the previous filters. If it simply exposes the ability to act on attributes generated by previous filters, we could do a lot many cool things. Similar idea applies to access logs, allowing any newly introduced protocol codec (or existing mongo/redis/thrift etc.) to emit the attributes to be logged and we can have the access log filter spit them out.
Along the same vein, it might help if we publish this so called object (one for HCM and one for Network stack) as protobuf representations for doc purposes.

Allowing multiple writers seems reasonable to me. It could also probably be expressed as part of the dependency/policy graph. @curiouserrandy thoughts?

[Just to clarify something that I think is understood: FilterState as a whole isn't write-once, but each object stored within FilterState is indeed write-once.]
Our experience at Google was that having a lot of filters all writing to the same objects made dependencies very hard to keep separate as the number of filters grew.  The goal of FilterState wasn't to create state that was shared between filters, it was to create a mechanism to allow information transfer between filters while keeping ownership and data flow of that data clear.  Data source is the (single) filter that sets the data originally, and the data sinks are the various filters that read that data.
Note that the current implementation doesn't make it impossible for different filters to write to the same filter, it just discourages it.  Object methods can implement arbitrary functionality by casting away const; indeed, this was how I imagined lazy evaluation being done for cases in which that was useful.  But the current design is specifically for the purpose of getting people to think carefully about their dataflow between filters, lest they end up in the state that we've experienced here.
In terms of a depencency graph, I suppose if we implemented the "Specifying Dependencies Between Filters" section of https://docs.google.com/document/d/1GNawM59Pp09WZ34zqJYiO_qmERjuGbOUeAqF1GG6v9Q/edit (and made it possible for multiple filters to call "providesData()" for a particular filter name, which the document doesn't forbid but hadn't been my vision) that could provide some level of constraint and documentation on the dependencies.  But I'd still worry that it was relaxing the structure too much for keeping inter-filter interfaces clean.  Maybe if you gave me some examples of the use cases you wanted to support?
@alyssawilk: You want to add to or modify anything in the above?

FWIW, in the PR that @rshriram just put in, I suggested doing a similar, but oppositely directed version: a key that anyone can write to, and that tcp_proxy would consume (if set). But that still maintains the property that it is easy to reason about, because it is (as currently written) a directed message from one filter to another. I'd be curious to hear your (@curiouserrandy) opinion on that use.

@curiouserrandy the use case I have is mentioned in the description above. I would like filters to add one or more attributes to a connection state (e.g., mongo adds some attributes, then tcp proxy adds some more, and finally access log uses it to create a log entry or the RBAC filter uses both to do some policy enforcement.). For example, lets say the RBAC filter looks for  "envoy.rbac.attributes" key in the shared connection state and does policies based on the attributes (a map of key value pairs). I would like all filters before RBAC to set the attributes that they glean from the connection into this shared object.

@ggreenway that was the original idea behind the post box style of the metadata namespace; the filter name was intended as the destination. It seems there are useful cases for both 1:N and N:1 communication.

@rshriram : Ah, sorry, somehow missed that section of your initial writeup.  I think I'm with @htuch / @ggreenway that 1:N and N:1 data flows would both have their use.  I'll note that one concern I have around N:1 is that I still don't think that it makes sense (at least based on what I understand of your use case) for multiple filters to overwrite the  same piece of data; what you want is for them to be able to add new pieces of data to a store/mailbox that the receiving filter will read.
WRT to protobufs, part of the reason for this implementation (using templates to allow arbitrary object storage) was to allow the cost for creation of complex data to be done once, and to allow filters to export logic/intelligence to be used by other filters.  So I'd rather not pull back from the current C++ template implementation to protobufs (though if I've misunderstood your point please correct me).
@htuch : Since I didn't end up replacing RequestInfo::dynamicMetadata(), it would be perfectly reasonable to keep that post office box style (and document it more clearly).  I'm not sure having both mechanisms in parallel for almost the same data transfer (the only difference being 1:N vs. N:1) makes sense as the mechanisms are fairly different (I think of dynamicMetadata() as being for config->filter communication, and FilterState as being filter->filter communication) but it's an option we could consider.

I am not looking for overwrite semantics. Append should do..

I would reasonably strongly prefer that we avoid that solution.  Let's craft a solution that's more targeted towards appending as opposed to allowing mutation.
One easy way to do that, either as another accessor or as a change to the existing situation, is to allow multiple setData<> of the same type on the same name, and have a getData<> that returns a vector of results.  Would that address this use case?
My personal preference would be another accessor so that it's clear when you're doing this different pattern of access.

neither of these would satisfy this use case though.. What I want is a bag of attributes.. Like a map within a map..
e.g.,
  mongoFilter:
     attributeBag = read_callbacks->connection().perConnectionState().getData("attribute_bag")
    attributeBag.addAttribute("foobar", someObject)
  rbacFilter:
    attributeBag = read_callbacks->connection().perConnectionState().getData("attribute_bag")
    iterate over the attributes in the attribute bag and do stuff..

Why wouldn't it satisfy the use case?  You just have objects with the same name (e.g. the destination filter that will consume the information) and those objects have an attributeName() accessor and the FilterState interface allows the ability to iterate through all of those objects.

sorry, i messed up the example.. here is the right one
mongoFilter:
     attributeBag = read_callbacks->connection().perConnectionState().getData("attribute_bag")
    attributeBag.addAttribute("foobar", someObject)
filterX:
    attributeBag = read_callbacks->connection().perConnectionState().getData("attribute_bag")
    attributeBag.addAttribute("filterX", someObject)
rbacFilter:
    attributeBag = read_callbacks->connection().perConnectionState().getData("attribute_bag")
    iterate over the attributes in the attribute bag and do stuff..

Ah I see what you are saying.. return vector of objects instead of a single object..
that could work.

should I change the getData to always return a vector instead of another variant?

We have been wanting a mixer-esque attribute bag for a while. I think it makes a lot of sense.
This proposal will have to decide on issues of attribute vocabulary that mixer had to before. Is it purely defined by the producer of the attribute, are attributes  namespaced ?

As this FitlerState is being implemented, what's the plan for the dynamic metadata? will the dynamic metadata be deprecated and removed sometime? If so when will this happen? Thanks.

@yangminzhu looks like it will be around for some time due to dependencies in JWT/RBAC filters IIRC.

We are planning to remove dynamic metadata from RBAC
and use the filter state instead.

Thanks for the comment, one more thing to confirm, currently the FilterState only has a generic Object interface.
To make it useful for sharing data between filters, should we define some well-known classes sub-classing the Object? For example, StringObject, NumberObject or even StructObject (for the protobuf struct).
Or otherwise should just we let each filter to create their own classes sub-classing the Object? (This seems creating a hard dependency if filter Y wants to receive data generated by filter X)
/cc @qiwzhang

Looking at RBAC filter, its simply a set of string matches isn't it? A string/NumberObject seems like a good start.

@rshriram I'm confused. How can the attributes be known well enough to be useful while the namespaces aren't known? At some point there is a contract over naming between producer and consumer, and that can include a namespace.
In your mixer example, why can't filter emit attributes under istio.mixer for example?

I think this is done. I will file a follow up issue to reconcile FilterState w/ dynamic metadata.


fix: Treat sites with 403 status codes as broken links

Treat sites with 403 status codes as broken links, reverting back default behavior implemented under #1157 (PR #1167).

Sorry for the delay. It's merged now. 😄


[pybind11] Py_DEBUG is defined, while interpreter does not support debug modules.

Describe the bug
When building a python module with pybind11 in Debug configuration, the wrong symbols are linked into the modules.
This bug occurs under the following conditions:

The python interpreter that is used for compilation/linkage does not have debug features (check via this method)
The module is compiled using a Debug configuration
Now, when building the module the wrong symbols are used, since vcpkg always sets Py_DEBUG to true (since this PR)

Environment

OS: Linux - Fedora 38
Compiler: gcc (GCC) 13.2.1 20230728 (Red Hat 13.2.1-1)
Python: Python 3.11.5 (Non Debug Build, important!)

To Reproduce
Steps to reproduce the behavior:
Build a python module using pybind11 in debug configuration. The system python interpreter does not support any
Expected behavior
A python module build in Debug-Configuration and with a non-Debug System interpreter should work.
Failure logs
When importing the module the following errors get thrown by the python interpreter
ImportError: undefined symbol: _Py_RefTotal
Additional context
By create a custom port of vcpkg without this patch everything worked as expected. Maybe it would be a solution to only apply this patch on windows?

cc @Osyotr

Maybe it would be a solution to only apply this patch on windows?

That would be reasonable

Here we have a similar issue. We use the pybind11::embed target (no module, just embedding the interpreter).
I checked the build output from my colleague. We build in CMAKE_BUILD_TYPE=Debug, but it links against "vcpkg_installed/x64-linux-dynamic/lib/libpython3.11.so" instead of "vcpkg_installed/x64-linux-dynamic/lib/debug/libpython3.11d.so" and fails with above linker error too. I recommended to my colleague to disable the pybind11 python handling, and instead explicitly link against the Python::Python target. And then re-check things.

Linux here, not Windows: We have a similar issue. We use the pybind11::embed target (no module, just embedding the interpreter).
I checked the build output from my colleague. We build in CMAKE_BUILD_TYPE=Debug, but it links against "vcpkg_installed/x64-linux-dynamic/lib/libpython3.11.so" instead of "vcpkg_installed/x64-linux-dynamic/lib/debug/libpython3.11d.so" and fails with above linker error too. I recommended to my colleague to disable the pybind11 python handling, and instead explicitly link against the Python::Python target. And then re-check things. Pybind11 does not appear to use "Python::" targets, but instead relies on find-module variables like PYHON_LIBRARIES. IMO this complicates the already complicated situation.
Maybe you have an idea, otherwise I will deep dive into the corresponding files to find the bug.
EDIT: What I said above about pybind11 using the variables instead of target based programming is incorrect. It has two modes, and in the modern mode, it actually uses the targets like Python::Python etc. So the bug maybe is in the find_python modules.. Will continue reporting here!

I now posted the narrowed-down reason in a separate issue report: https://github.com/microsoft/vcpkg/issues/34678


Catch invalid param exception

Description of changes:*

potential fix for https://github.com/aws-robotics/cloudwatchlogs-ros1/issues/54

Adding unit test for checking invalid parameter is caught.

I'm worried about other errors which we're not looking for. The root cause of the issue is us cherry-picking specific errors to check against instead of classifying all non-retryable errors as such, so adding one more error to the list is not solving the big picture problem. Let's spend a bit more time to get rid of this switch block and check the HTTP status instead. Retryable errors are 5XX (server side) or 429 (throttling). Example: https://github.com/aws/aws-sdk-js/blob/v2.543.0/lib/util.js#L896

I'm worried about other errors which we're not looking for. The root cause of the issue is us cherry-picking specific errors to check against instead of classifying all non-retryable errors as such, so adding one more error to the list is not solving the big picture problem. Let's spend a bit more time to get rid of the switch block and check the HTTP status instead. Retryable errors are 5XX (server side) or 429 (throttling). Example: https://github.com/aws/aws-sdk-js/blob/v2.543.0/lib/util.js#L896

Is there any bearing on how we handle the exception and the logic to determine if the logs should go to the offline cache? @dabonnie
I like @AAlon 's  recommendation, curious to know why we did not choose that option to begin with. I suspect that somehow the exception logic is intertwined with support for offline and I want to confirm that before we make further progress.

A few items:

How do we obtain the HTTP Status code from the C++ SDK? The only errors I see returnable by PutLogEvents are defined as enums as part of the API.

We should ensure all defined errors here (cloudwatch) and here (core) are handled appropriately; we may need to engage the SDK team to determine their scope.

I don't see a way to avoid cherry picking errors, e.g., data should be be discarded due to throttling but it should if improperly formatted or it exceeds the size / age limit.

I see all of the above as additional issues while not blocking this patch. However, one issue that this patch does not address is that the "old" data is still stored on disk and will be attempted to be uploaded later. I think we may need a mechanism to prune the offline logs.

A few items:

How do we obtain the HTTP Status code from the C++ SDK? The only errors I see returnable by PutLogEvents are defined as enums as part of the API.

The error returned is an Aws::Client::AWSError<CloudWatchLogsErrors> object which has methods like GetResponseCode, GetResponseHeaders (in addition to GetErrorType which we use).

We should ensure all defined errors here (cloudwatch) and here (core) are handled appropriately; we may need to engage the SDK team to determine their scope.
I don't see a way to avoid cherry picking errors, e.g., data should not be discarded due to throttling but it should if improperly formatted or it exceeds the size / age limit.

The HTTP standard already defined which codes constitute a retryable error, we don't need to think too much. 429 and 5xx should be retried, everything else should be discarded.

I see all of the above as additional issues while not blocking this patch. However, one issue that this patch does not address is that the "old" data is still stored on disk and will be attempted to be uploaded later. I think we may need a mechanism to prune the offline logs.

I agree that we can merge this with no downside and separately work on a follow up, but the follow up is a couple lines of code so might as well just do it...

everything else should be discarded.

Discarded as the data should never be uploaded?

I agree that we can merge this with no downside and separately work on a follow up, but the follow up for classifying errors correctly is a couple lines of code so might as well just do it...

If it's simple please feel free to open an issue + PR so we can merge independently while reducing the scope here :-).
It would definitely be a valuable add for both CW Logs and Metrics.


ARROW-7800 [Python] Create record batch reader interface on FileReader

This is a work in progress for the exposition of the record batch reader interface in Pyarrow.

@jorisvandenbossche hey thank you for the review.
The reason I put the get batches in the constructor was party out of laziness, so one wouldn't have to separately instantiate the row group readers. I will try and fix when I get the time, but I think it means a bit more of a refactor.
The reason I did the test with dictionaries was because batches actually break the dictionary array functionality, it was something that affected the project I'm working on, but the problem is outside the scope of this PR.

Seems like it would be useful to finish this. Perhaps the method could be called something like parquet_file.iter_batches()?

Thanks @rollokb for suggesting this and starting implementing it. I have a project where it could be very useful 😄
Looks like you haven't had a chance to make the suggested updates recently, so I made an attempt at it in #6979. I took Wes' suggestion and redesigned it as an iter_batches() method on both the ParquetFile and ParquetReader classes.
If you have time to spend on this soon, I hope what I wrote is helpful. If you don't, let me know and I'd be happy to bring this feature across the finish line in that other PR.

@wjones1 I'll close this in favor of your PR. You can always collaborate together there


Pagination of included resources?

In trying to debug some performance issues I discovered that whenever include is used to include child resources that ALL of the children are included in the response. Is there a way to paginate those, or just to include the first X children? (I suspect that my search-fu is weak this morning because I'm having trouble finding any issues that talk about this, but I'd be surprised if I'm the first person to have this problem.)

You are not the first person to notice this issue. It's probably the number one feature I feel the project is missing. I'm hoping to have some time to work on it soon.

Thanks for the info, @lgebhardt.

The easiest solution is to paginate the included relationship objects and add the pagination to relationship links. For example if a store has many products and default pagination is set to 20, show 20 products and show pagination in the relationship links like
http://example.com/api/v1/stores/:store_id/relationships/products?page=2


Change term - associatedSequences

Change term

Submitter: John Wieczorek
Justification (why is this change necessary?): Consistency and clarity
Proponents (who needs this change): Everyone

Current Term definition: https://dwc.tdwg.org/terms/#dwc:associatedSequences
Proposed new attributes of the term:

Term name (in lowerCamelCase): associatedSequences
Organized in Class (e.g. Location, Taxon): MaterialSample
Definition of the term: (unchanged): A list (concatenated and separated) of identifiers (publication, global unique identifier, URI) of genetic sequence information associated with the MaterialSample.
Usage comments (recommendations regarding content, etc.): Note that the ResourceRelationship class is an alternative means of representing associations, and with more detail. Recommended best practice is to separate the values in a list with space vertical bar space ( | ).
Examples: http://www.ncbi.nlm.nih.gov/nuccore/U34853.1, http://www.ncbi.nlm.nih.gov/nuccore/GU328060 | http://www.ncbi.nlm.nih.gov/nuccore/AF326093
Refines (identifier of the broader term this term refines, if applicable): None
Replaces (identifier of the existing term that would be deprecated and replaced by this term, if applicable): http://rs.tdwg.org/dwc/terms/version/associatedSequences-2017-10-06
ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG, if applicable): DataSets/DataSet/Units/Unit/Sequences/Sequence/ID-in-Database + constant

Discussions around changes to relationshipOfResource (#194), around a new term relationshipOfResourceID (#186, #283), and changes to associatedOccurrences (Issue #324) suggest that a clarification should also be made in the associatedSequences usage notes. Specifically, the convention on list item separation and the reference to ResourceRelationship as an alternative means of capturing these data are recommended.

dwc:associatedSeqences does not have dwciri: analog, so no revision necessary in that namespace.

Related issues are Issue #1, Issue #3, Issue #24 (reopened because of renewed interest), Issue #314, Issue #344, Issue #345, Issue #346, and Issue #347.

The Australasian Herbarium Information Systems Committee (HISCOM) considers moving attributes from Occurrence to MaterialSample premature given the Extended and Digital Specimen consultation that is occurring and the general conversation about the definition and scope of MaterialSample (#314).
Relates also to associatedSequences (#332), preparations (#346) and disposition (#347)
Regarding the usage note, associatedSequences differs from associatedOccurrences, associatedTaxa etc. In that it takes a list of URIs rather than a list of key–value pairs, so using the ResourceRelationship class instead does not add anything and in fact might make it harder for consumers to interpret and for aggregators to process the data. We suggest removing this usage note.

We endorse this proposal for the change in usage comments on behalf of @SiBColombia.
We think that the change in the class is also logic, but maybe is better to wait for the results of the consultation as @afuchs1 proposses, just to be sure.

The Australasian Herbarium Information Systems Committee (HISCOM) considers moving attributes from Occurrence to MaterialSample premature given the Extended and Digital Specimen consultation that is occurring and the general conversation about the definition and scope of MaterialSample (#314).

In the case of a sequence, it necessarily must derive from a MaterialSample, so I see no risk in making that organizational change regardless of the Extended and Digital Specimen consultation. Can anyone realistically see any risk in this non-normative change for this term?

Relates also to associatedSequences (#332), preparations (#346) and disposition (#347)
Regarding the usage note, associatedSequences differs from associatedOccurrences, associatedTaxa etc. In that it takes a list of URIs rather than a list of key–value pairs, so using the ResourceRelationship class instead does not add anything and in fact might make it harder for consumers to interpret and for aggregators to process the data. We suggest removing this usage note.

The usage note does not even make the recommendation to use ResourceRelationship instead, it only points out that it is an alternative, which is still true, including that more detail can be added (contrary to the position that "it does not add anything". Would a change in the usage note from "Note that the ResourceRelationship class is an alternative means of representing associations, and with more detail" to "Note that the ResourceRelationship class is an additional means of representing associations, and with more detail" alleviate the perception that the ResourceRelationship representation is somehow preferred?

This proposal has been labeled as 'Controversial' and in need of a task group to for resolution. It is no longer part of an active public review.

This issue has been superseded by https://github.com/tdwg/dwc/issues/454


Please update documentation in Android Integration section of local_auth plugin

Documentation is obsolete in Android Integration section of local_auth plugin
Update your MainActivity.java:
import android.os.Bundle;
import io.flutter.app.FlutterFragmentActivity;
import io.flutter.plugins.flutter_plugin_android_lifecycle.FlutterAndroidLifecyclePlugin;
import io.flutter.plugins.localauth.LocalAuthPlugin;

public class MainActivity extends FlutterFragmentActivity {
    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        FlutterAndroidLifecyclePlugin.registerWith(
                registrarFor(
                        "io.flutter.plugins.flutter_plugin_android_lifecycle.FlutterAndroidLifecyclePlugin"));
        LocalAuthPlugin.registerWith(registrarFor("io.flutter.plugins.localauth.LocalAuthPlugin"));
    }
}

Please see https://flutter.dev/go/android-project-migration for migration details. Kotlin MainActivity file seems to be OK.
Also,
  <uses-permission android:name="android.permission.USE_FINGERPRINT"/>
in AndroidManifest.xml file is deprecated.
[✓] Flutter (Channel stable, 2.0.4, on Mac OS X 10.15.7 19H524 darwin-x64, locale en-CA)
• Flutter version 2.0.4 at /Users/?????????????/Developer/SDKs/flutter
• Framework revision b1395592de (4 weeks ago), 2021-04-01 14:25:01 -0700
• Engine revision 2dce47073a
• Dart version 2.12.2
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
• Android SDK at /Users/?????????????/Library/Android/sdk
• Platform android-30, build-tools 30.0.2
• ANDROID_HOME = /Users/?????????????/Library/Android/sdk
• ANDROID_SDK_ROOT = /Users/?????????????/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 12.4, Build version 12D4e
• CocoaPods version 1.10.1
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 4.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

@misici234
There's similar open issue describing your case, https://github.com/flutter/flutter/issues/81127
Please follow-up there for updates.
Closing this as duplicate.


virt-launcher: disable isa-debugcon on Arm64

Device isa-debugcon does not support on Arm64,
and no good alternative device found, so just
disable it on Arm64.
Signed-off-by: Howard Zhang<EMAIL_ADDRESS>Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #7650
Release note:
NONE

/lgtm


Replaced map..flatten with flat_map

In these use cases, flat_map is more concise and performant

Oops what a rookie mistake! I just realised that flat_map is only does 1 level of flattening.


Fix write_enable commands and method.

-This only has effect if sector protection enabled.

@marcuschangarm @geky could you check this?

Ah good catch :+1:
@marcuschangarm, does this look correct to you?

@hesee thanks for the pr!


Angular v13

Needs additional configuration:

https://github.com/angular/angular/issues/44026

Big esm refactoring of webpack configs

First working version is @leanup stack v2.0.0-rc.19


Export as CSV

What problem does this feature solve?
The data should support simple exporting function, to allow further analytics on the data with ease.
What does the proposed API look like?
There should be a export button (of course = =). After clicking it will popup a confirmation dialog, double mentioning the license applied to our dataset, and should have an additional warning when using a mobile device (since those device typically offer poor or none file managing features, thus delivering the correct MIME with testing on multiple platforms is ESSENTIAL on this feature). After confirming the export dialog and they has chose a data format they want to use (currently, .xlsx and .csv are supported), the user will get a corresponding file named as [i18n Name] - [i18n Stage/Item] - penguin-stats.io.(ext).
For example:

when exporting the statistics of Orirock under zh locale: 固源岩 - 素材统计结果 - penguin-stats.io.(ext)
when exporting the statistics of Keton Colloid under ja locale: 高級アケトン - 素材統計結果 - penguin-stats.io.(ext)
when exporting the statistics of 1-7 under ko locale: 1-7 - 작전지역별 통계 의 통계 결과 - penguin-stats.io.(ext)

Should contain

Last updated at
Exported from client version
Original URL of the exported dataset
Dataset itself

Contents specifically should contain in a .csv file

A comment section at the top of the file containing the license information

Contents specifically should contain in a .xlsx file

A different sheet with license information

Due to abuse usage concerns this feature would not be implemented. The one interested to use our data programmatically may utilize our Public API.
Closing and the one may open a new issue if they found that this feature is particularly important.


GitLab, GitHub etc oAuth

Describe the bug
Short: Getting CORS error, if I want to set up GitLab OAuth. I'm not sure if I miss something in the README or examples, but even with the simplest one, I cannot overcome CORS error.
If someone brings me in the right direction, I can make it as a community-based example for such a use case
Stackblitz example
https://stackblitz.com/edit/oauth-gitlab?file=src/app/app.component.ts
To Reproduce
Steps to reproduce the behavior:

Load the given app (e.g. locally)
CORS error for discovery is shown:

Access to XMLHttpRequest at 'https://gitlab.com/.well-known/openid-configuration' from origin 'http://localhost:4200' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Expected behavior

No CORS problems exist, and configuration can be loaded

Desktop (please complete the following information):

Chrome 86

This is not an issue with this library.
The server that you configure as an OAuth2/OIDC provider (your Identity Provider Service) needs to send the correct CORS headers when it responds to any request your browser makes, no matter if you make the request from your own code or if a library requests that.
Github and Gitlab, as well as a lot of other OIDC providers, target their service for server-based web applications and not for SPAs, which is the reason that they do not add CORS headers for unknown hosts. This would also be a security risk for their services, which is also a reason that they do OIDC for server-based login and not SPAs.
If you want to use Github or Gitlab as an OIDC provider for your SPA, you need to "pipe" the external login through an OIDC provider that will allow setting CORS headers for your SPA origin (the server that serves your application).
Auth0 (https://auth0.com) would be such a service that you can use from your SPA, if you don't want to provide an OIDC provider yourself (which you probably don't want ;) ).


Unable to init new project

Describe the bug
I tried to configure credential for amplify but always showing my message No credentials found for appId
Also, I tried to reinstall amplify and delete~/.aws and recreate new IAM profiles
Amplify CLI Version
4.40.0
To Reproduce
> amplify init
? Enter a name for the project todo
? Enter a name for the environment dev
? Choose your default editor: Visual Studio Code
? Choose the type of app that you're building javascript
Please tell us about your project
? What javascript framework are you using vue
? Source Directory Path:  src
? Distribution Directory Path: dist
? Build Command:  npm run-script build
? Start Command: npm run-script serve

Using default provider  awscloudformation

For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html

Adding backend environment dev to AWS Amplify Console app: d1tpt3h0rdowiv
⠏ Initializing project in the cloud...

CREATE_IN_PROGRESS UnauthRole             AWS::IAM::Role             Sun Dec 20 2020 08:14:17 GMT+0200 (Eastern European Standard Time) Resource creation Initiated
CREATE_IN_PROGRESS DeploymentBucket       AWS::S3::Bucket            Sun Dec 20 2020 08:14:17 GMT+0200 (Eastern European Standard Time) Resource creation Initiated
CREATE_IN_PROGRESS AuthRole               AWS::IAM::Role             Sun Dec 20 2020 08:14:16 GMT+0200 (Eastern European Standard Time) Resource creation Initiated
CREATE_IN_PROGRESS UnauthRole             AWS::IAM::Role             Sun Dec 20 2020 08:14:16 GMT+0200 (Eastern European Standard Time)
CREATE_IN_PROGRESS DeploymentBucket       AWS::S3::Bucket            Sun Dec 20 2020 08:14:16 GMT+0200 (Eastern European Standard Time)
CREATE_IN_PROGRESS AuthRole               AWS::IAM::Role             Sun Dec 20 2020 08:14:16 GMT+0200 (Eastern European Standard Time)
CREATE_IN_PROGRESS amplify-todo-dev-XXXXX AWS::CloudFormation::Stack Sun Dec 20 2020 08:14:12 GMT+0200 (Eastern European Standard Time) User Initiated
⠇ Initializing project in the cloud...

CREATE_COMPLETE AuthRole AWS::IAM::Role Sun Dec 20 2020 08:14:28 GMT+0200 (Eastern European Standard Time)
⠋ Initializing project in the cloud...

CREATE_COMPLETE UnauthRole AWS::IAM::Role Sun Dec 20 2020 08:14:29 GMT+0200 (Eastern European Standard Time)
⠋ Initializing project in the cloud...

CREATE_COMPLETE DeploymentBucket AWS::S3::Bucket Sun Dec 20 2020 08:14:37 GMT+0200 (Eastern European Standard Time)
⠋ Initializing project in the cloud...

CREATE_COMPLETE amplify-todo-dev-XXXXX AWS::CloudFormation::Stack Sun Dec 20 2020 08:14:40 GMT+0200 (Eastern European Standard Time)
✔ Successfully created initial AWS cloud resources for deployments.

No credentials found for appId: XXXXXXXXXX
If the appId is correct, try running amplify configure --appId XXXXXXXXX

Expected behavior
Continue setup without asking for credentials
MacOS Big Sur
Node v12.16.1
NPM 6.13.4

@erashdan Could you please try using v 4.40.1? Tried reproducing it with v4.40.1 and wasn't able to. Please let us know if you're still seeing this.


Styling updates

 LOW URGENCY: Increase font size by 1 pt. in all header text

 LOW URGENCY: Increase line height on department headers below hero spot.

 LOW URGENCY: Fix font bolding issue on Media Gallery.

For clarity, can you provide before and after screen shots and update your first PR comment to show them (as opposed to adding new comments).

For clarity, can you provide before and after screen shots and update your first PR comment to show them (as opposed to adding new comments).

Comment updated


kconfig: Refactor kconfig.py to use main and argparse

Kconfig.py is not following the de-facto (real?) coding standards of
Zephyr. This commit refactors kconfig.py with two changes:
Use _main_ and def main().
Use argparse instead of sys.argv.
Signed-off-by: Sebastian Bøe<EMAIL_ADDRESS>

@ulfalizer, would this be the sort of patch you'd take upstream?

kconfiglib.py is the upstream kconfig library.
kconfig.py is a Zephyr-specific CLI program that uses kconfiglib.py.
It was originally based on an upstream example, but has since diverged significantly, as one would expect :)

It was originally based on an upstream example, but has since diverged significantly, as one would expect :)

Ah, so we're not maintaining a fork with small differences, the way we do with kconfiglib?

Codecov Report

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

@@           Coverage Diff           @@
##           master    #7351   +/-   ##
=======================================
  Coverage   55.09%   55.09%
=======================================
  Files         474      474
  Lines       51786    51786
  Branches     9937     9937
=======================================
  Hits        28530    28530
  Misses      19304    19304
  Partials     3952     3952

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 4954fe0...224dfe4. Read the comment docs.

Looks fine to me. Added some notes for unrelated stuff that could be cleaned up too.

@mbolivar
Here's the upstream example btw:
https://github.com/ulfalizer/Kconfiglib/blob/master/examples/merge_config.py
I think I prefer the manual version there, so that people can read the example easily even if they're not familiar with argparse.
argparse doesn't hurt for production stuff though. Get nicer error reports and help texts.


SMT: keep names of variables

It would be nice to keep the actual variable names, but also would be sufficient to emit the renamings to the log:
; MY_VARIABLE_ONE -> <0>
(dec-fun <0> Int 0)

Where ; ... is an SMTLIB comment.


Allow-list pragma_table_info(tablename) and similar

It would be great if pragma_table_info(tablename) was allowed to be used in queries. See also https://github.com/simonw/til/blob/master/sqlite/list-all-columns-in-a-database.md

select * from pragma_table_info(tablename); is currently disallowed for user-provided queries via a regex restriction - but could help here too.
https://github.com/simonw/datasette/blob/d349d57cdf3d577afb62bdf784af342a4d5be660/datasette/utils/__init__.py#L174

Originally posted by @simonw in https://github.com/simonw/datasette/issues/760#issuecomment-624729459

I could allow-list some other useful pragma_x tables too.

The rationale for blocking pragma entirely from statements is that it can be used to change the state of the SQLite database, e.g.
PRAGMA schema.application_id;
PRAGMA schema.application_id = integer ;

That second line is usafe. I don't think it's possible to use the pragma_table_x variants to make writes in this way.

Maybe use a negative lookahead assertion? https://docs.python.org/3/library/re.html#index-20

(?!...)
Matches if ... doesn’t match next. This is a negative lookahead assertion. For example, Isaac (?!Asimov) will match 'Isaac ' only if it’s not followed by 'Asimov'.

For the moment I'll allow-list the following:

pragma_database_list
pragma_foreign_key_list
pragma_function_list
pragma_index_info
pragma_index_list
pragma_index_xinfo
pragma_page_count
pragma_max_page_count
pragma_page_size
pragma_schema_version
pragma_table_info
pragma_table_xinfo

Some demos:

https://latest.datasette.io/fixtures?sql=select+*+from+pragma_database_list()
https://latest.datasette.io/fixtures?sql=select+*+from+pragma_foreign_key_list('complex_foreign_keys')
https://latest.datasette.io/fixtures?sql=select+*+from+pragma_function_list()
https://latest.datasette.io/fixtures?sql=select+*+from+pragma_index_info('idx_compound_three_primary_keys_content')
https://latest.datasette.io/fixtures?sql=select+*+from+pragma_index_list('compound_three_primary_keys')
https://latest.datasette.io/fixtures?sql=select+*+from+pragma_index_xinfo('idx_compound_three_primary_keys_content')
https://latest.datasette.io/fixtures?sql=select+*+from+pragma_page_count()
https://latest.datasette.io/fixtures?sql=select+*+from+pragma_max_page_count()
https://latest.datasette.io/fixtures?sql=select+*+from+pragma_page_size()
https://latest.datasette.io/fixtures?sql=select+*+from+pragma_schema_version()
https://latest.datasette.io/fixtures?sql=select+*+from+pragma_table_info('complex_foreign_keys')
https://latest.datasette.io/fixtures?sql=select+*+from+pragma_table_xinfo('complex_foreign_keys')

Interestingly https://latest.datasette.io/fixtures?sql=select+*+from+pragma_function_list() doesn't work, when it DOES work on my laptop.
latest.datasette.io currently runs SQLite 3.27.2 while my laptop runs 3.31.1
https://www.sqlite.org/changes.html#version_3_30_0 says that as-of 3.30.0:

The PRAGMA function_list, PRAGMA module_list, and PRAGMA pragma_list commands are now enabled in all builds by default. Disable them using -DSQLITE_OMIT_INTROSPECTION_PRAGMAS.

More demos here: https://github.com/simonw/til/blob/master/sqlite/list-all-columns-in-a-database.md

Here's another demo I built using this feature: https://observablehq.com/@simonw/datasette-table-diagram
Running on this query:
select
  sqlite_master.name as table_from,
  fk_info.[from] as column_from,
  fk_info.[table] as table_to,
  fk_info.[to] as column_to
from
  sqlite_master
  join pragma_foreign_key_list(sqlite_master.name) as fk_info
order by
  sqlite_master.name

See https://github-to-sqlite.dogsheep.net/github?sql=select
++sqlite_master.name+as+table_from%2C
++fk_info.[from]+as+column_from%2C
++fk_info.[table]+as+table_to%2C
++fk_info.[to]+as+column_to
from
++sqlite_master
++join+pragma_foreign_key_list(sqlite_master.name)+as+fk_info
order+by
++sqlite_master.name


Enhance transpose kernel generator to support additional sizes

The kernel transpose generator can only generate kernels whose sizes in the X and the Y dimensions that are mod-32. Given the fact that our FFT kernel generators support prime factors of 3 and 5, we have weak coverage of the vector sizes we support. The transpose kernel generator should be extended to handle all sizes that the FFT kernel generator supports, if not arbitrary dimension lengths.

This feature is supported now ..


expose a method to set font_global_scale

I noted that you hoped PRs would come with a cargo fmt included, but I saw there was a lot of reformatting done by this, so I thought I'd offer to do this as a follow-up rev if required.

Thanks!
It's ok, I should actually remove cargo fmt from the instructions because they keep changing the defaults and the formatting results change all the time :sleepy:


Feature/project structure

first content to fix #6
@lnnrtwttkhn, could you review it? It would help me, if you specifically emphasise the Citation of the examples. I am insecure about it, because I did not use pictures but copied the structures from the links.

@lnnrtwttkhn, this is also work I did a couple of weeks ago 🤓
If you have time you can also review it 😊

Awesome, very nice, thank you @justus-reihs! A few comments:

[ ] Use newline for every sentence in the abstract field in the YAML header, see 6b5cda771c85533711e70c6859059a12cd0382be
[ ] Start learning objectives with "You ..." and ideally focus on a concrete outcome, see my wak attempt in fe7610300ee38bc3430b40219e7004f1f032bd20
[ ] For the example project structures, use code comments for the explanations
[ ] Put the references for the project structure examples to the top, not the bottom
[ ] Assign an explicit language to the code chunk e.g., zsh and add filename=, see 30db016061c4e080656fbfe2593f4a328000d694
[ ] Replace code comments with code annotation, see example in a6db7d0eed6df50f8a85a856847b4c0bad94a96b. please do this for all code comments


How to make use of fingerprint id to correlate with log exception detail?

How to make use of fingerprint id to correlate with log exception detail?
Do you plan to support current timestamp in error message?

You can register a WebErrorHandlerPostProcessor.
Then it's possible to:

Save the fingerprint to some persistent storage or even log it for further investigation
Add timestamp

thanks


clarity-native-bin tag update: 2.0.0-rc1

:robot: This is an automated pull request created from a new release in stacks-blockchain.
Updates the clarity-native-bin tag.

@CharlieC3 is it intentional that we'd publish a new version with this tag? It seems like it, just want to make sure, as I haven't been following the version tags on stacks-blockchain.

@CharlieC3 is it intentional that we'd publish a new version with this tag? It seems like it, just want to make sure, as I haven't been following the version tags on stacks-blockchain.

@hstove Yup, this version is correct. We switched to a semver convention for this release going forward, and thought it made more sense than the previous versioning scheme.

@hstove Yup, this version is correct. We switched to a semver convention for this release going forward, and thought it made more sense than the previous versioning scheme.


Create factories in one go with different values?

Hello,
Is this the correct syntax to create several factories in one go?
Or is there some variant of create_listwhere I can pass different values to each factory?
cy
          .appFactories([
            ['create', 'user', { username: username1 }]
            ['create', 'user', { username: username2 }]
          ])

yes, basically correct but you are missing a comma after the first create
cy.appFactories([
  ['create', 'user', { username: username1 }],
  ['create', 'user', { username: username2 }]
])


Spring hateoas integration: ensure compatibility with 1.4

Hi,
When trying to upgrade to spring boot 2.6.2, I got this exception regarding the spring-hateoas integration:
Caused by: java.lang.NoSuchMethodError: 'void org.springframework.hateoas.EntityModel.<init>(java.lang.Object, org.springframework.hateoas.Link[])'
	at com.blazebit.persistence.spring.hateoas.webmvc.KeysetAwarePagedResourcesAssembler.lambda$toModel$0(KeysetAwarePagedResourcesAssembler.java:80)
	at com.blazebit.persistence.spring.hateoas.webmvc.KeysetAwarePagedResourcesAssembler.createModel(KeysetAwarePagedResourcesAssembler.java:133)
	at com.blazebit.persistence.spring.hateoas.webmvc.KeysetAwarePagedResourcesAssembler.toModel(KeysetAwarePagedResourcesAssembler.java:88)
	at com.blazebit.persistence.spring.hateoas.webmvc.KeysetAwarePagedResourcesAssembler.toModel(KeysetAwarePagedResourcesAssembler.java:80)

Could you please make the integration compatible with spring-hateoas 1.4 and the changes made by @odrotbohm ?
Thanks!

Switching to the factory methods should do the trick. They had been deprecated for quite a while already.

Thanks for the report! Too bad you ran into this today when I just released a new version 😞
If you had reported this earlier I would have been able to squeeze the fix in for that release. Is the update to the latest Spring HATEOAS very critical to you, or is it ok to wait e.g. 2 weeks? I'd like to wait a bit for feedback on this release before pushing out another one.

Yeah, I had the same feeling when I saw the release announcement. No rush needed,take your time 😉

Fixed via 4092ddc6afad23dd2afb46c7f87cd0c5eb17898f


Script only downloads files with extension JPG

By design, this script only downloads files with names like *.JPG.  Should a file be named *.JPEG it will not be processed.  PNG files will also not be processed.
I'm working on a way to fix that.

The solution is an update to the regex used in the Where-Object on line 12.  I have a version that should work, testing it now before submitting a pull request.
| ? { $_ -match "\.(jpe?)|pn)g$" }

Fixed in linked PR. Thanks @pandages!!


Methods and Errors

Began as cleanup to export error variables such that a receiver could distinguish errors it is receiving without using string literal comparisons as well as without importing the underlying PGX package. This ended up finding an error where some methods don't call SaveMethodCall.

Coverage increased (+30.5%) to 73.899% when pulling 364c51f9e4a78586444c0fabf88af7ff2901f494 on daMethodsErrors into<PHONE_NUMBER>a7b1ae12062e549f12a2524a1df3cd on master.


Which accuracy do I need to reach for a decent agent?

I ve trained my model by using 200gb of driving data and inception_v3 model on same street with same weather conditions and 8.000 epochs with 300kb batches per epoch and learning rate of 0.000000001.
Accuracy is somewhat about 0.2(smoothed).
But when I test it out it keeps pressing WD with a verage plus of 0.3 of probability.
My question, how much data and which acc. do I need for a decent agent?
Tensorboard:
http://honesthome.ddns.net/s.png
Example Output [W, WA, WD, S, SA, SD, A, D]:
[ 0.1167456   0.16700381  0.27807635  0.05266069  0.08322734  0.1091948
0.11513347  0.07795788]
0.278076350689
forward_right
[ 0.11684461  0.16718809  0.27833453  0.0525772   0.08328342  0.1088759
0.11493194  0.07796425]
0.278334528208
forward_right
[ 0.11666095  0.16800123  0.27791589  0.05253068  0.08310306  0.10876592
0.11503578  0.07798637]
0.277915894985
forward_right
[ 0.116884    0.16714898  0.2784971   0.05255117  0.08334375  0.10875834
0.11481125  0.0780055 ]
0.278497099876
forward_right
[ 0.11672532  0.16719386  0.27897081  0.05252673  0.08339871  0.10860606
0.11471127  0.07786718]
0.278970807791
forward_right
[ 0.11685108  0.16760175  0.27800107  0.05256343  0.08338011  0.10876746
0.11482292  0.07801216]

0.2 accuracy (20%) is quite low, and with 8 different predictions, even a random prediction is 0.125 (12.5%). If you trained your model at a learning rate of 1e-9, that is VERY low, you shouldn't start it any lower than 1e-5, I would use 1e-3 for one epoch, see how the accruacy/loss were progressing, and adjust down accordingly for later epochs.


Stdout from sensitive execute resource displays with chef-client -l debug

I have a sensitive execute block in one of my cookbooks. Normally, running chef-client suppresses the output from this block, as it should, however if I run it with -l debug, stdout goes straight to my terminal:
# chef-client -l debug
Starting Chef Client, version 12.4.1
resolving cookbooks for run list:

...
  * execute[my-execute-block] action run

(tons of stuff that we shouldn't be able to see)
    - execute sensitive resource
  * execute[next-thing] action run
This is undesirable ಠ_ಠ
I noted this issue, which is similar, but in this case the execution was successful, and debug mode was the variation.

I don't think this is actually the case in modern Chef Infra Clients. If someone is still having this issue with 17+ please file a new issue and we can track down what happens there.


dev: Separate countdown and stopwatch reducers

Separate reducers of countdown and stopwatch, and add functionality of stopwatch.

Closed.


Ensure public translations fall back to default locale

When a translation is missing in one of the contributed locales, we
want to make sure the corresponding translation from the default
locale is displayed.

For I18n.t calls from Ruby code, this already is the default
behavior if config.i18n.fallbacks is set to true. In standard
Rails apps, this is the case in production.

Inside the editor, translations of all locales are present via
i18n-js. Here we need to set the fallbacks option to true, to
ensure the default locale is used.

In publishe entries, i18n-js is initialized only with the
pageflow.public translations of the current locale. We need to
manually merge the corresponding translations from the default
locale since fallback does not work for namespace lookups.

Coverage increased (+0.002%) to 99.029% when pulling 2e70427bab96d1f4bb29e2de0997ed700e6e7786 on tf:i18n-fallback into 3a8fb995013025668c09d6ce8edd361e3abe1fdf on codevise:master.


Passing a proxy in recaptcha_params gets clobbered by base proxies, wouldn't work anyways.

I'm using a local proxy to route recaptcha solves through the localhost. As such, I am not passing a proxy to cloudscraper by default (as it'll access from the local machine anyways). However, I do need to pass a proxy through to the captcha solving service (so their requests will get forwarded to the local machine, which is running a proxy).
However, right now, if you have a proxies parameter in your recaptcha param, it gets clobbered in Challenge_Response().
It'd be nice if instead of
            self.recaptcha['proxies'] = self.proxies

this was something like:
            if self.proxies:
                self.recaptcha['proxies'] = self.proxies

Additionally, even if you set the proxy parameter, it doesn't seem to get passed through to at least the anticaptcha solver anyways, as it always uses a NoCaptchaTaskProxylessTask(). You need to use a NoCaptchaTask() to handle proxies. You're mutating client.session.proxies, but python-anticaptcha doesn't use client.session, so those changes are not effective.
Realistically, I think you're going to need to just pass user-provided args through to the NoCaptchaTask() creation, and perhaps have a different solver type for with-proxy/without proxy.

You can't do self.recaptcha['proxies'] = self.proxies or self.recaptcha['proxies'] ?

I mean, sure, but it's much less readable.

Proxy support has been added in to 2captcha and anti-captcha


Fix:fix memory crash

Problems found in performance testing.The test environment is as follows：5000 entities,BlinnPhongMaterial,PrimitiveMesh.createCuboid.

We have added a PR https://github.com/oasis-engine/engine/pull/226  and sorted out the relevant logic


add github star and  fork icons in home page

What is the purpose of the change
add github star and  fork icons in home page
https://github.com/apache/incubator-dubbo-website/issues/69
Brief changelog
modified:   src/pages/home/index.jsx
modified:   src/pages/home/index.scss

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Test your code locally by running docsite start, and make sure it works as expected.
[ ] Make sure no files under build directory is added.
[ ] If this contribution is large, please follow the Software Donation Guide.

Looking at the screenshot, the icons do not align with the above two buttons Get Started and GITHUB. Shall we align with it?

Updated

@lovepoem Button layout in the wrong.

@lovepoem Button layout in the wrong.

And I think there is no need to have a Star and Fork dead simple.For example:

I think it's because of the cache .
Please clean the cache of web browser and try again
Jlcao<EMAIL_ADDRESS>于2019年3月5日周二 下午12:08写道：

@lovepoem https://github.com/lovepoem Button layout in the wrong.
[image: image]
https://user-images.githubusercontent.com/29936718/53780328-dc6a7f80-3f3e-11e9-93d3-f1063bdba8b8.png
And I think there is no need to have a Star and Fork dead simple.For
example:
[image: image]
https://user-images.githubusercontent.com/29936718/53780419-5ac72180-3f3f-11e9-88b4-ecf6a592a04a.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-dubbo-website/pull/309#issuecomment-469529518,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAye6IPznIkquBcYlKiHrv-yEAoqNV_Qks5vTe22gaJpZM4bcBEB
.

Hi, the font looks different with others, are they built-in styles?


Gradle Build failing after adding image_picker plugin

Initializing gradle...                                       1.5s
Resolving dependencies...                                    5.0s
Gradle task 'assembleDebug'...
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
D8: Program type already present: android.support.v4.app.INotificationSideChannel

         *********************************************************
WARNING: This version of image_picker will break your Android build if it or its dependencies aren't compatible with AndroidX.
         See https://goo.gl/CP92wY for more information on the problem and how to fix it.
         This warning prints for all Android build failures. The real root cause of the error may be unrelated.
         *********************************************************
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.
> com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives: D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\142.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\118.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\94.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\124.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\88.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\136.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\157.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\103.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\163.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\151.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\127.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\100.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\166.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\139.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\97.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\115.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\160.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\169.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\106.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\154.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\148.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\112.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\172.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\133.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\109.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\91.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\121.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\130.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\145.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\27.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\52.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\18.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\43.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\19.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\51.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\60.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\36.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\34.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\42.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\28.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\50.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\33.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\37.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\2.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\9.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\25.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\45.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\32.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\38.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\39.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\44.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\57.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\26.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\8.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\31.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\30.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\56.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\13.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\14.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\21.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\49.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\7.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\12.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\15.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\55.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\58.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\6.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\20.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\46.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\11.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\59.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\24.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\29.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\54.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\16.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\41.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\5.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\10.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\3.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\17.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\23.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\47.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\40.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\53.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\35.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\4.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\48.jar, D:\fluuter_projects\motor_app_demo\build\app\intermediates\transforms\dexBuilder\debug\22.jar
  Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes.
  Program type already present: android.support.v4.app.INotificationSideChannel

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 22s
Gradle task 'assembleDebug'... Done                         23.7s
Gradle task assembleDebug failed with exit code 1

Same problem:

What went wrong:
Execution failed for task ':app:transformClassesWithMultidexlistForDebug'.

com.android.build.api.transform.TransformException: Error while generating the main dex list.

Didn't knew it was because of the image_picker

When i run the application without adding image picker as a dependency, it works fine.
So i think image_picker is causing the problem

Have you tried asking on StackOverflow?

For me its not the image_picker, i just tried to run my app without it and doesn't work

Did you enable multidex? See also #27682 #27702

yes

@joaowd did you migrate to AndroidX?

@zoechi yeah that was the problem, I thought I did but I didn't. It worked!

@DeepaVPanicker what is your current status with the problem?

@zoechi I've enabled multidex.
But still facing the same problem

I tried
flutter packages pub cache repair , but still the problem exists

Have you tried asking on StackOverflow?

Yes

The SO question has an accepted answer.

I fix it by upgrading the gradle to 5.6.2. And don't forget to remove old gradle files


⚠ Bofrost.lu has degraded performance

In 41c625a, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2353 ms

Resolved: Bofrost.lu performance has improved in c1d0ed8 after 6 minutes.


gsoler3 Acrolinx quality push: configure-ad-fs-extranet-soft0lockout-…

…protection.md

This PR makes only minor edits that don't affect meaning. I'll merge now.


Update Readme with info about the gradle plugin

This MR updates README:

info about gradle plugin
update link to maven plugin

Given that assertj-assertions-generator repo could be entry point for some-one looking for gradle plugin it make sense to have it mentioned together with maven plugin.

Integrated thanks @AlexTrotsenko!


Can I get my code to be called when the debugger stops/resumes?

See this.
I would like the debugger to call DateTimeDebug.Running = false when it stops, and DateTimeDebug.Running = true when it resumes.

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

ID: ed9dcc5d-ade9-c88a-76f6-538231671b0b
Version Independent ID: 6d86c444-dba6-8d0e-4b2c-a4cc57c11365
Content: First look at the debugger - Visual Studio
Content Source: docs/debugger/debugger-feature-tour.md
Product: visual-studio-windows
Technology: vs-ide-debug
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@daveyostcom  It looks like you have product feedback rather than documentation feedback. If you are looking for functionality that isn’t currently provided by the product, please use our new “Suggest a feature” option in the Visual Studio Developer Community. We’d be happy to have this on record, where others can view it and upvote it, too. For more information about this new functionality in the dev community, see our Suggest a feature page.

Posted feedback here


Pod install error

I am getting the error message when installing the pods:

[!] The 'Pods-...' target has transitive dependencies that include static binaries: (.../OpenSSL-Universal/lib-osx/libcrypto.a and .../OpenSSL-Universal/lib-osx/libssl.a)

My podfile is:
target 'Transfer' do
  pod 'MIHCrypto'
  use_frameworks!
end

added this to the beginning and it fixed the issue.


Example Pages Should Be All WCAG 2.0 AA and WAI ARIA Conform

All example pages should be WCAG 2.0 at least AA and WAI ARIA conform. At the moment they're not and have several accessibility issues. These pages should be built from scratch, so all the Heading and other elements are semantic correctly implemented and accessible. For example, quick accessibility check of "Homepage with global navigation", result:

Please analyse and estimate @topaxi


asking for edits re-renders the entire content

I notice when I ask for an edit to the generated content, its re-generating it through chat gpt, or whatever model.
I use Aider a lot as a personal code assistant. And their implementation and approach is to to generate a unified diff (by generating only the changes that are needed in udiff format) and apply that to the original work rather than regenerating the original work with the edits. I cannot overstate how exceptionally well this works. It does require some fine-tuning of the unified diff prompt and a error correction agent to fix when things go wrong. Which is in frequent, but it does happen.
In my opinion the experience would be greatly improved by generating a unified diff and applying that diff against the original source.

Nice, love this idea.  Right now I'm basically starting a new chat session each time.  If we include a diff it would definitely provide more context.  I'll experiment


[CostManagement] Release stable version

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.CostManagement


Post Control Tower Guardduty findings to slack

We need to have guard duty findings sent to sentinel from Control Tower first

Closed in https://github.com/cds-snc/sentinel/pull/164


Axios with promise.prototype.finally without shim()

Just following the cookbook here: https://github.com/mzabriskie/axios/blob/master/COOKBOOK.md
In the finally example, the code only works if I shim() promise.prototype.finally eg. require('promise.prototype.finally').shim()
Error message as seen here: http://stackoverflow.com/questions/39696007/axios-with-promise-prototype-finally-doesnt-work

@komirad I've updated the cookbook. Thank you!


Large range read blocks writes on 3.2.1?

I'm testing a very large 1.5 Kubernetes data set upgraded to 1.6 and etcd v3 mode (etcd 3.2.1).  Post v3 migration, I'm performing a kubernetes storage migration (GET -> PUT of all data) to force migration to protobuf.  However, as I was letting the migration run in the background (single threaded is taking about 30-40 minutes, since i'm migrating about ~500k kubernetes objects) I tried to do a range read of the /kubernetes.io keyspace to list all of the keys (etcdctl get /kubernetes.io --keys-only) and the migration halted until the range read completed or timed out.  I tried both serializable and linearizable, and both seemed to have the same behavior of "blocking" the migration process from continuing (specifically, the PUT of the object from Kubernetes to etcd timed out after 30s).
I didn't expect a range read to block writes, and have not noticed that behavior elsewhere.  It's somewhat reproducible on the data set I have, but was not sure where to start looking to debug.

dup with https://github.com/coreos/etcd/issues/7719
also: https://github.com/coreos/etcd/issues/8114
@smarterclayton can you move the comment to #7719. if we decide to solve this, we will solve it there. thanks.


Added documentation for debugging with core files

Added a small paragraph to document signal and exception disable switch of the build system. And more general, how to debug an hpx application with the help of a core file.
I'm pretty sure I didn't put that into a file where it really makes sense, I'm creating this pull request to get the process started.
(Also, Circle CI will likely complain, I couldn't get the documentation creation set up on my system.)

(Also, Circle CI will likely complain, I couldn't get the documentation creation set up on my system.)

@DavidPfander-UniStuttgart what didn't work? it should be relatively pain free to set up. Did you see this: http://stellar-group.github.io/hpx/docs/html/hpx/manual/build_system/building_hpx/doc_tools.html?

The build system told me that everything is fine, cmake ran successfully. But when I did the make docs, I got strange errors.
Beginning of the error log:
pfandedd@pcsgs09:~/git/hpx/build$ make docs
Generating BoostBook XML file hpx.xml from hpx.qbk.
Generating Output File: hpx.xml
/home/pfandedd/git/hpx/docs/hpx.qbk: warning: Quickbook 1.7 is still under development and is likely to change in the future.
/home/pfandedd/git/hpx/docs/manual/lcos.qbk:204: warning: line breaks generate invalid boostbook (will only note first occurrence).
Generating hpx.dbk
file://usr/share/xml/docbook/schema/dtd/4.2/dbcentx.mod:308: warning: failed to load external entity "file://usr/usr/share/xml/entities/xml-iso-entities-8879.1986/ISOamsa.ent"
%ISOamsa;
         ^
Entity: line 1:
 %ISOamsa;
          ^
file://usr/share/xml/docbook/schema/dtd/4.2/dbcentx.mod:312: warning: failed to load external entity "file://usr/usr/share/xml/entities/xml-iso-entities-8879.1986/ISOamsb.ent"
%ISOamsb;
         ^
Entity: line 1:

(a lot of similar errors)
Later on:
I/O error : No such file or directory
I/O error : No such file or directory
runtime error: file file://usr/share/xml/docbook/stylesheet/docbook-xsl/html/chunker.xsl line 239 element document
xsltDocumentElem: unable to save to file://home/pfandedd/git/hpx/build/share/hpx-1.0.0/docs/html/hpx/preface.html

(Again, lots of similar errors)
I had to built auto-index and quickbook myself and specified them as mentioned in the hpx documentation. I installed the other dependencies from the ubuntu repositories.

Well, if it says 'No such file or directory', it's probably missing a file or directory ;-)


feat: the normalized layer should contain gene-length normalized counts from SmartSeq data

The normalized layer is currently not usable for cells coming from SmartSeq assays. SmartSeq assays need to normalize raw counts by gene lengths prior to sum normalization.
When building the normalized layer, Census should be performing gene length normalization for applicable cells.

Solution:
For cells of assay "EFO:0008930", "EFO:0008931", "EFO:0700016". The normalized  cell vector should be:

Divide each value in the vector by  its corresponding var["gene_length"]
i.e a[i,:] = X["raw"][i,:] / obs["gene_length"] for cell i
Then, divide by the sum of these values
i.e.normalized[i:] = a[i,:] / sum(a[i,:])

Resolved by #884


Update to Maninc Miner Port xml and cover image

Trying to help out the project game data and practise my git skills(or lack of them!)

PS Seeing what happened in main with Love. The penny has finally dropped about branches :)

I did exclude from the conmit but it showed them as unchanged still?
Would it be better to close this pr and submit a new one from a branch?
On Wed, 6 Mar 2024, 08:01 Cebion, @.***> wrote:

When you do a git commit they'll list exactly what you changed. If you
don't want that in your PR you don't submit the commit.
—
Reply to this email directly, view it on GitHub
https://github.com/PortsMaster/PortMaster-New/pull/155#issuecomment-1980287645,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABONRNRULGUGZTLAIGUSKGLYW3EPBAVCNFSM6AAAAABEHNLMUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBQGI4DONRUGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

I did exclude from the conmit but it showed them as unchanged still? Would it be better to close this pr and submit a new one from a branch?
…
On Wed, 6 Mar 2024, 08:01 Cebion, @.> wrote: When you do a git commit they'll list exactly what you changed. If you don't want that in your PR you don't submit the commit. — Reply to this email directly, view it on GitHub <#155 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABONRNRULGUGZTLAIGUSKGLYW3EPBAVCNFSM6AAAAABEHNLMUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBQGI4DONRUGU . You are receiving this because you authored the thread.Message ID: @.>

as of now these are still getting renamed.


New fields

Introduction of the new fields priceRatePerMinute y priceCurrency to display the price rate per minute and the price currency

this PR should be collapsed with #124. Please use git cherry-pick to do so.


Use brew to install packages for darling.

Hi,
Is it possible to install packages for darling with brew?
Regards.

No idea. Please always fill in the issue template.


Stubbing request pane ui

This PR covers the scaffolding and styling of the core UI elements for gRPC feature implementation. Items include:

Client streaming | headers tab system
Body and supporting streams child tab system
Editors for child system, read-only for stream instances
"URL Bar" for gRPC, protocol | one-line editor | method DD | execute

UI provisioning visual:

Fixes INS-202

Closing this PR because it was merged with #2817


Question about NetVLAD in MODEL_ZOO.md

Hi, @yxgeee
Thanks a lot for sharing this valuable image-based localization tool.
I would like to re-rank the retrieval results based on your work.
In MODEL_ZOO.md,  I only find SFRS and SARE models but miss NetVLAD model.
Where could I download the pretrained NetVLAD model?
Thanks a  lot for your help.

Hi, here is the NetVLAD model reproduced by OpenIBL:
https://drive.google.com/drive/folders/1sjsxnlqyUCjrXOg2ahwrf7WufU1jvO_D?usp=sharing

Thanks a lot for your quick reply.
May I ask another question?
When I extract descriptor for a single image, How can I change
different pretrained models with  'torch.hub.load()'?
Thanks for your help.

I have only uploaded the best model (trained by SFRS) for torch.hub, I will upload both SARE's and NetVLAD's if required.

Fine,
Thanks a lot for your help and your work.


[feat][txn] implement the SnapshotSegmentAbortedTxnProcessor

Master Issue: https://github.com/apache/pulsar/issues/16913
Motivation
Implement an abortedTxnProcessor to handle the storage of the aborted transaction ID.
Modifications
The structure overview:

The main idea is to move the logic of the operation of checking and persistent aborted transaction IDs(take snapshots)  and the operation of updating maxReadPosition into the AbortedTxnProcessor.
And the AbortedTxnProcessor can be implemented in different designs.
Add persistentWorker to handle snapshot persistenting ：

The first four items below are the corresponding four tasks in the figure. The fifth item is not strictly a task, but a part of the first two tasks.

takeSnapshotSegmentAsync -> writeSnapshotSegmentAsync

These two method is used to persist the snapshot segment.

deleteSnapshotSegment

This method is used to delete the snapshot segment.

clearSnapshotSegmentAndIndexes

Delete all segments and then delete the index of this topic.

updateSnapshotIndex

Called by the deleteSnapshotSegment and writeSnapshotSegmentAsync. Do update the index after writing the snapshot segment.
Called to update index snapshot by takeSnapshotByChangeTimes and takeSnapshotByTimeout.
Called by recovery as a compensation mechanism for updating the index.

Documentation

[x] doc-not-needed
(Please explain why)

Matching PR in the forked repository
PR in forked repository: https://github.com/liangyepianzhou/pulsar/pull/9

Create a delete task for each segment, and update the index within each delete task. This method costs too much.

In factly, this logic in clearSnapshotSegmentAndIndexes  is executed in a single task.
There does not open new tasks for each segment deleting and index updating.

Codecov Report

Merging #18273 (b498a2d) into master (492a9c3) will decrease coverage by 23.56%.
The diff coverage is 5.23%.

@@              Coverage Diff              @@
##             master   #18273       +/-   ##
=============================================
- Coverage     47.46%   23.90%   -23.56%
+ Complexity    10727      294    -10433
=============================================
  Files           711     1654      +943
  Lines         69456   126369    +56913
  Branches       7452    13771     +6319
=============================================
- Hits          32964    30214     -2750
- Misses        32810    91699    +58889
- Partials       3682     4456      +774

Flag
Coverage Δ

inttests
23.90% <5.23%> (?)

unittests
?

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

Impacted Files
Coverage Δ

.../pulsar/broker/admin/impl/SchemasResourceBase.java
38.23% <0.00%> (-51.67%)
:arrow_down:

...r/impl/SnapshotSegmentAbortedTxnProcessorImpl.java
0.00% <0.00%> (ø)

...er/metadata/v2/TransactionBufferSnapshotIndex.java
0.00% <0.00%> (ø)

...a/v2/TransactionBufferSnapshotIndexesMetadata.java
0.00% <0.00%> (ø)

.../metadata/v2/TransactionBufferSnapshotSegment.java
0.00% <0.00%> (ø)

...er/impl/SingleSnapshotAbortedTxnProcessorImpl.java
40.42% <28.57%> (-30.23%)
:arrow_down:

...ransaction/buffer/impl/TopicTransactionBuffer.java
32.94% <28.57%> (-25.20%)
:arrow_down:

...va/org/apache/pulsar/client/impl/ConsumerImpl.java
34.46% <90.00%> (+19.36%)
:arrow_up:

...r/service/SystemTopicTxnBufferSnapshotService.java
60.86% <100.00%> (-17.40%)
:arrow_down:

...er/systopic/NamespaceEventsSystemTopicFactory.java
71.42% <100.00%> (-1.91%)
:arrow_down:

... and 1433 more

This PR introduced a new flaky test #19650, please fix

the implementation contains multiple thread-safety issues, I filed #22116


[BUG] Data adding without a property and limited rows

When the users add a property A, then delete it the user still can add properties.
Maybe implementing a vscroll to Properties and Data could solve the problem too

Good catch!
This should be fixed with commit e1016356985131c980aea4d1cdcfb635ec9c41cd into master branch.
If you have the time and will, please test again.
Thank you!

I'm closing this. If the issue persists, I'll reopen.


How can I model time series shorter than 512 timesteps?

Hi! Thanks to your excellent work!
I would like to ask can I make the initial time length of the pretrained model less than 512? Because the time length of my data is much less than 512, I worry that too much padding will prevent the model from extracting valid features.
Thank you in advance.

Hi Evelyn,
Can you tell us a bit more about the data?
There's a few ways you can upsample your time series. If the shape of your time series is important, and not its temporal resolution MOMENT research (https://github.com/moment-timeseries-foundation-model/moment-research) code has some up sampling functions such as cubic spline interpolation, which might be helpful.
Also note that MOMENT takes input_mask as input. You can "mask" the padded values so that the model does not pay attention to them. One thing to be careful here is that patches which are partially observed (i.e. some time stamps are observed while others are padded or masked) are completely masked, so there might be some loss of information. This may be important for extremely short time series where all time stamps are equally important.
Let us know if you have any more questions and thanks for your interest in MOMENT!
Don't hesitate to open another issue should you have one.
Best,
Mononito


primary artist name loops instead of retrieving secondary artist name

When i play a song by multiple artists, instead of foobar displaying all artists, the original artist name is displayed the amount of times there are artists. For instance, the image below should contain the artists 'Rob Scallon' & 'Pete Cottrell'

Ah, I see you're a man of culture as well =)


Webp thumbnails

Also refactors ThumbFile away from getter/setter pattern
Working on tests still

this block: https://github.com/Imgur/mandible/pull/79/files#diff-91bbeda7eb98a7adc57b9e47e2cf5c2bR475
requires a dimensions param to be passed in. We should remove this restriction so that we can convert full sized images to webps

our travis config doesn't use docker, so it doesn't contain the new webp library needed for the tests. will address this in the morning

travis now uses docker

actually.. this breaks max_width without specifying width. going to rework validation logic

:+1:


Templated Pdf Generation

Need the ability to create pdf templates and use them in the code generation.
I can think of a couple directions we could go and maybe we do all of them just for the fun of it

html / jsx / handlebars formatting

:+1: user friendly
:-1: people may not be able to do things they would expect
:-1: could get very complicated pretty quickly

latex

:-1: Very huge and complicated
:-1: may be difficult to integrate packages that people could expect to work
:+1: Would be really cool
:+1: Would really exercise the library quite a bit

custom markdown language

:+1: We control it completely
:+1: We can make it only have the features that we want it to have
:+1: We can add custom ide support for working with these files
:-1: New users would have a learning curve of a new format
:-1: Would take quite a bit of work

xml specification

:+1: We control it completely
:-1: Very ugly
:-1: Would be difficult to work in without a visual designer
:+1: Fastest

I am thinking I want to have a custom markdown language and maybe have something similar to stylesheets maybe

I would like to use code generators with this so we would generate all the C# code at compile time. The developer would then just need to supply a C# object containing the data that is needed to populate the template.
This would be nice because we wouldn't have to worry about compile times and we would have static type checking on the template in the code.

This has been started


Autocomplete panel doesn't close when an option click

Bug, feature request, or proposal:
Bug
What is the expected behavior?
After I click on an option (using mouse cursor) the autocomplete suggestion panel should be closed.
What is the current behavior?
When I click on an option (using mouse cursor) the autocomplete suggestion panel closing and immediately opening again. This bug occurs only in Internet Explorer (I tested on version 11).
What are the steps to reproduce?
Plunker:
https://plnkr.co/edit/7zAjuhQJdibmPCaLsulm
Use Internet Explorer 11.

Select option in 'State1' using the mouse cursor.
Input 'State2' is blocked by 'State1'

Also, this bug can be reproduced on official documentation
https://material.angular.io/components/component/autocomplete
What is the use-case or motivation for changing an existing behavior?
I have two autocomplete input. when user select option in one input, the application should do focus on the other input programmatically. With this bug, when user select option in first input, application do focus on the other input, but the suggestion panel of first input stays opened. In result, a user sees two suggestion panels for each input.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 4.2.2
Material 2.0.0-beta.6
OS Windows 10 (build 15063.0)
TypeScript 2.3.4
Internet Explorer 11
Is there anything else we should know?
In Chrome, Edge and Firefox this bug does not reproduce.

You don't need two autocompletes to see the problem. The panel just don't close after selecting a state in IE11 without throwing any error.
If you double click the desired item, with short interval between the clicks, it closes. Maybe something with the ripple effect is going wrong in IE11 preventing event bubling.


Update residues alphabet

Because our main model will be trained on MassIVE-KB, this adds the corresponding modifications to our residues alphabet. Note that the updated alphabet can't be used with our currently trained models.
To ensure that residues are always interpreted as strings by the YAML loader, they are now surrounded by quote marks. Otherwise N-terminal modifications are interpreted as floats.

nitpick/non-blocking: Maybe it would be helpful to mark which amino acids we needed to add because of the MSKB training job with a comment? Not sure if people would look at the paper and be confused as to why certain AA seem to have been added later. If this is not needed then this seems fine since it follows the old format for the residues section of the yaml.

Imo this is more a problem of the fact that we didn't do versioning with proper releases previously. At this point there are a few changes that are not fully backwards compatible with the code for the ICML paper, so just adding a comment for the residues won't be a complete solution anyway.
I'd just try to get the new model available asap and make a real release, so it's much easier and clearer for people what proper version to use.