SignalR input binding fails to parse standard Authorization header

When using the idToken property on SignalR input binding as specified in the documentation it should be possible to use binding expession to specify the header from which the JWT token should be extracted. Then using claimTypeList  you can specify which extracted claims should be propagated to resulting access token for SignalR. However if standard Authorization header is specified in idToken, the JWT token parsing fails.
Sample Azure function (nodejs runtime, programing model v4):
const inputSignalR = input.generic({
  type: "signalRConnectionInfo",
  name: "connectionInfo",
  hubName: "my-hub",
  idToken: "{headers.authorization}", // extract JWT from standard Authorization header with Bearer JWT token in it
  claimTypeList: ["name", "email"], // propagate name and email claims to SignalR Service access token
});

async function negotiate(
  request: HttpRequest,
  context: InvocationContext
): Promise<HttpResponseInit> {
    return { body: JSON.stringify(context.extraInputs.get(inputSignalR)) };
}

app.post("negotiate", {
  authLevel: "anonymous",
  handler: negotiate,
  route: "negotiate",
  extraInputs: [inputSignalR],
});

when such negotiate endpoint is invoked, it however fails with error:
Executed 'Functions.negotiate' (Failed, Id=8c21bcd7-d061-4184-bac7-3f1046b00f99, Duration=71ms)
[2024-09-29T20:21:11.648Z] System.Private.CoreLib: Exception while executing function: Functions.negotiate. System.IdentityModel.Tokens.Jwt: IDX12709: CanReadToken() returned false. JWT is not well formed.
The token needs to be in JWS or JWE Compact Serialization Format. (JWS): 'EncodedHeader.EndcodedPayload.EncodedSignature'. (JWE): 'EncodedProtectedHeader.EncodedEncryptedKey.EncodedInitializationVector.EncodedCiphertext.EncodedAuthenticationTag'.

this can be resolved by removing the Bearer  string from the begginning of the incoming Authorizzation header. If this is done, the JWT header is parsed successfully and the specified claims are propagated to accessToken returned by negotiate endpoint.
It would be helpful if parsing of JWT token could handle common Bearer  prefix in the Authorization header without failure.
Further technical details
Nodejs 20.15..1
@azure/functions 4.5.1

Are you using a specific identity provider, the provider tokens are injected into the request headers. See https://learn.microsoft.com/azure/app-service/configure-authentication-oauth-tokens#retrieve-tokens-in-app-code for more information. Does it satisfy your need?

We use a third party Identity Provider and in JWT token issued by it the user identifier claim is named account_id, but there are of course also other more standard claims present there like email and name . Which claims will be propagated into those automatically populated headers (X-MS-CLIENT-PRINCIPAL-ID, X-MS-CLIENT-PRINCIPAL-NAME etc.) or is it somehow configurable?
Because if its name or enail, that does not help. We need the claim account_id to be used as the user identifier for SignalR.


Updates to AriesOpenAPIDemo.md

Added explanatory notes to "Issuing a Credential" section

Codecov Report

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

@@          Coverage Diff           @@
##           master    #370   +/-   ##
======================================
  Coverage    89.2%   89.2%
======================================
  Files         236     236
  Lines       11205   11205
======================================
  Hits         9995    9995
  Misses       1210    1210

On clicking the details button next to the DCO error I was asked to do “git rebase HEAD~6 —signoff” then “git push —force-with-lease origin master” I had made the original changes online and committed them in GitHub itself so I cloned the repo to my local machine and did as instructed above.
I am not familiar with git so I don’t know what to do next.
I think the best thing for me to do is to close this pull request and submit a new one with things done right.

That is the other way to do it!  :-).  It's what I tend to do...


deactivate groups

requires https://github.com/mitre/caldera/pull/235

this does not seem to work

@privateducky please use in coordination with https://github.com/mitre/caldera/pull/244


Allow MarkupContent[] to be used as Hover contents

Fixes #518 and Microsoft/vscode-languageserver-node#374.
Supported by Microsoft/vscode-languageserver-node#417

Closing after discussion with @dbaeumer in Microsoft/vscode-languageserver-node#417. Note that atom-languageclient does not use this same approach (at least when I last checked.
Sourcegraph uses css rules to make the markdown content with horizontal seperators look the same as multiple array items: https://github.com/sourcegraph/codeintellify/commit/2ab2bf62289fc0266b3772fe07aee9d82c1786e7


Pre-translation Cleanup

Sort of a running to-do list of things to do prior to next round of translations:

[ ]  /files directory: Refresh TeachOSM files, jettison obsolete LearnOSM files

[ ]  /vendor directory: need to update jquery?

I've been trying to simplify the setting up of new languages on LearnOSM and have created
https://github.com/Nick-Tallguy/LearnOSM-language-helper
which automates much of the process of setting up.
In case you are interested in something similar, I have started to setup a similar 'helper' for TeachOSM at https://github.com/Nick-Tallguy/TeachOSM-language-helper
I've paused while waiting to see if this would be of any use and for any discussion on amendments if needed.

Nick,
First, thanks so much for taking this on. I think it could be quite useful in simplifying the setup for new languages. Look forward to the discussion on this.

Deferred.


[Windows] Check if the uplink is virtual before creating HNSNetwork

Otherwise it would fail with "The parameter is incorrect" which is not
useful for end users.
Signed-off-by: Quan Tian<EMAIL_ADDRESS>Fixes #2213
Without the PR, the log was
F0329 23:35:27.090421    3936 main.go:58] Error running agent: error initializing agent: failed during hnsCallRawResponse: hnsCall failed in Win32: The parameter is incorrect. (0x57)

With the PR, the log became:
E0607 09:57:45.645715    1808 agent_windows.go:65] Transparent HNSNetwork requires a physical adapter while the uplink interface "vEthernet (Ethernet0 2)" is virtual, please detach it from other HNSNetwork and try again
F0607 09:57:45.647765    1808 main.go:58] Error running agent: error initializing agent: uplink "vEthernet (Ethernet0 2)" is not a physical adapter

/test-all

Codecov Report

Merging #2246 (4aa2826) into main (18da642) will decrease coverage by 21.60%.
The diff coverage is n/a.

:exclamation: Current head 4aa2826 differs from pull request most recent head f1a5f8c. Consider uploading reports for the commit f1a5f8c to get more accurate results

@@             Coverage Diff             @@
##             main    #2246       +/-   ##
===========================================
- Coverage   61.79%   40.18%   -21.61%
===========================================
  Files         279      273        -6
  Lines       21327    20504      -823
===========================================
- Hits        13179     8240     -4939
- Misses       6780    11112     +4332
+ Partials     1368     1152      -216

Flag
Coverage Δ

kind-e2e-tests
40.18% <ø> (-12.81%)
:arrow_down:

unit-tests
?

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

Impacted Files
Coverage Δ

pkg/agent/controller/egress/id_allocator.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/controller/networkpolicy/crd_utils.go
0.00% <0.00%> (-91.57%)
:arrow_down:

pkg/controller/networkpolicy/endpoint_querier.go
2.85% <0.00%> (-88.58%)
:arrow_down:

pkg/controller/networkpolicy/status_controller.go
0.00% <0.00%> (-87.10%)
:arrow_down:

...agent/flowexporter/connections/deny_connections.go
7.14% <0.00%> (-85.72%)
:arrow_down:

...kg/controller/networkpolicy/antreanetworkpolicy.go
0.00% <0.00%> (-85.00%)
:arrow_down:

pkg/controller/egress/controller.go
0.00% <0.00%> (-83.88%)
:arrow_down:

pkg/agent/util/iptables/lock.go
0.00% <0.00%> (-81.82%)
:arrow_down:

pkg/agent/controller/networkpolicy/priority.go
8.49% <0.00%> (-81.70%)
:arrow_down:

pkg/controller/networkpolicy/clustergroup.go
1.40% <0.00%> (-81.31%)
:arrow_down:

... and 129 more

/test-all


Better RNG

It's now more modular and self-commenting.
Avoid panic by returning 0
More random, because nanoseconds are faster than micros

I think ultimate_rng should be placed in a separate module file (for potential-future use by other modules), but because it's so small I've leave it in _bool

Holup, test is failing in playground. I'll convert to draft

I found a possible solution, but that looks like bad practice, and I'm too lazy, and inlining may improve performance, so I'll revert some changes

Why not =)


cephfs mount

Details
Describe the solution you'd like:
Hi! It would be very handy to not only mount pvc, emptyDir, hostPath and nfs within the persistence section but also ceph.
As of the docs it does not need a lot of configuration expect the monitors on which the ceph-storage is running.
At the end, it would be nice to configure it in the values.yaml as the following:
persistence:
   cephfs-config:
     enabled: true
     type: cephfs
     monitors:
      - mon.rook.svc.cluster.local:6790
      - mon.rook.svc.cluster.local:6789
     path: /registryFS
     secretRef:
       name: rook-rbd-user

Anything else you would like to add:
If there is no intention to add this, I can create a PR and try to implement it. I am relatively new to k8s, helm and everything but would put in the effort to create the PR properly.
Thanks in advance!

I'm curious what problem does this solve, why do you want to mount ceph?

When assuming to have a running ceph cluster and you want to share data across different pods over different namespaces, you can mount the ceph storage via cephfs such as NFS.
As soon as the ceph storage has been mounted, all containers and pods can access the data. Eventually it must be pointed out that a readOnly flag would also be handy.
Hopefully, this was clear enough!

What's the difference in just using an PVC that uses the cephfs storage class and attaching it via existingClaim?
e.g.
https://github.com/onedr0p/home-ops/blob/457ef2f4b85947b3caf1fddd3775013784880a9f/cluster/apps/monitoring/vector/geoipupdate/config-pvc.yaml

Thanks for your answer!
Unfortunately, my understanding of rook/ceph is very limited.
Are you saying that:

I can create 1 PersistentVolumeClaim in pod A that accesses the ceph storage and mount it under /my-pvc
I store one file via pod A in this pvc such as /my-pvc/mytestdata.bin
I use this pvc in another pod B via existingClaim and mount it as well under /my-pvc
I see the file /my-pvc/mytestdata.bin in the pod B

I was already trying to achieve this using a pvc to no avail. If this is working, there is obviously no need to create an explicit cephfs mount section.
Thank you!

As in the EDIT described, I am going to describe the use-case here more in detail:

Before the pod starts there must be a binary file stored in the shared file system in order to run the application
I want to be able to store this binary file from outside (eg. my computer or the Node)

Hi! Sorry it took me a bit to get to this issue. This is not a feature that I am looking to add since it is very specific to folks using Ceph(FS). But you can already mount these types of storage by using the custom persistence type:
https://bjw-s.github.io/helm-charts/docs/common-library/common-library-storage/#custom.


No DNS request received with systemd-resolved

Hello,
I've observed that when systemd-resolved is used, DNS requests are not received on the Interactsh server.

We've also tested with a friend on two different private Interactsh installations, without really understanding the source problem, we think that it comes directly from interactsh-server because it's a problem that I don't encounter with my private burp collaborator or my custom dns server.
To reproduce it is enough to use a server ubuntu 20.04 / Debian 11 with systemd-resolved (I did not test other OS)
Regards

I have observed the same problem with some servers. At first I thought it was the TTL but even when recompiling with a lower TTL I still have the problem. I could observe that it came from interactsh because on the same server it works with a program I made (burp collborator like) and not with interact sh.


*: fix query statement detail error cause by round

Signed-off-by: crazycs520<EMAIL_ADDRESS>When query statement detail, dashboard uses to use ROUND function to query, but it may cause the flowing error:

This is caused by the ROUND function result is float64, not int, here is an example.
test> create table t (a int, b double);
Query OK, 0 rows affected
Time: 0.044s
test> insert into t values (62695, 2240325.4838709678),(6, 0.0);
Query OK, 2 rows affected
Time: 0.042s
test> select round(sum(a*b)/sum(a)) as avg from t;
+-----------+
| avg       |
+-----------+
| 2240111.0 |
+-----------+

This PR use CAST( ... AS SIGNED) function instead of ROUND when query statement detail.

@breeswish @baurine PTAL


install Hwameistor by Operator can not set the component Resource

installing Hwamestor by Operator cannot enable/disable the component and set the resource

disabling component is ready now.setting resources of component will be ready this month.

supported


Requesting support for Logitech G213 Keyboard

Logitech G213 has been since a long time now and has great RGB feature set !  Will be great to have its support ty !

You should be able to just copy the device file from the G915, adjust the USB ID and get it to work.
https://github.com/libratbag/libratbag/blob/master/data/devices/logitech-g915.device

Didn't work

Did you restart the daemon?
killall ratbagd

and then reopen piper.

Still didn't work in infact restarting the system..

I can provide some more info, not sure if it will help.
ratbag version in my system is 0.16.
I tried to create a device file file, based on the G915, as suggested by @FFY00.
After that, all my tests were done with /usr/sbin/ratbagd --verbose=raw.
The content of my device file is:
[Device]
Name=Logitech G213
DeviceMatch=usb:046d:c336
LedTypes=logo;switches
Driver=hidpp20

Looks like the keyboard is detected, but there's some kind of problem reading the LEDs, an ' Undocumented error codehappens, andratbagd` crashes:
noindex.log
Removing logo from LedTypes does not fix the crash
If I switch the driver to hidpp10, and configure Leds=5, nothing really happens:
hidpp10.log
Reviewing https://github.com/libratbag/libratbag/blob/master/data/devices/device.example I am not sure if there's something else I can try.
I will be happy to receive any hint (and if I am able to create a .device file, I will contribute it with a PR), provide any other debug information, or test patches if needed.

Any update? @FFY00 G213 is a popular model and I think libratbag should support it. If you can give u some guidance we can solve this problem and contribute to the community. :)

Unfortunately, I don't have this device, so I can't do it myself, but if anyone with some basic-ish C experience wants to help, it should be doable. The first step would be figuring out the value of led->type in the failed assertion in the log above. Then I can try to check my notes to figure out what that value is meant to represent, or ping the Logitech engineers about it, and go from there.

@FFY00 thanks for the hint. I am not a C developer, but I think I can handle myself.
I will paste the data as soon as I have it.

I was trying to compile the library and debug it manually, the compilation was successful but since I am not very experienced with C debuggers I could not debug it. I read 'Building from source' and 'Debugging' articles which are in the contributing page but i was not successful. If you can give me more info about how I can debug the project I will be debugging and giving more info about the situation.

Hey, I got successful with debugging and took some info. As far as I can see there is 3 leds, one is SWITCHES, one is LOGO and the third one is (0) unknown type. I got all properties of the led variable printed, I'm pasting the detailed output here. If you need any further info I can see what I can do.
`
Breakpoint 1, ratbag_sanity_check_device (device=0x5555555c7aa0)
at ../src/libratbag.c:316
316				assert(led->type != RATBAG_LED_TYPE_UNKNOWN);
(gdb) print led
$1 = (struct ratbag_led *) 0x5555555d0b40
(gdb) print led->type
$2 = RATBAG_LED_TYPE_LOGO
(gdb) c
Continuing.
Breakpoint 1, ratbag_sanity_check_device (device=0x5555555c7aa0)
at ../src/libratbag.c:316
316				assert(led->type != RATBAG_LED_TYPE_UNKNOWN);
(gdb) print led->type
$3 = RATBAG_LED_TYPE_SWITCHES
(gdb) c
Continuing.
Breakpoint 1, ratbag_sanity_check_device (device=0x5555555c7aa0)
at ../src/libratbag.c:316
316				assert(led->type != RATBAG_LED_TYPE_UNKNOWN);
(gdb) print led->type
$4 = 0
(gdb) print led==null
$5 = 0
(gdb) print led->index
$6 = 2
(gdb) print led->mode
$7 = RATBAG_LED_OFF
(gdb) print led->color
$8 = {red = 85, green = 85, blue = 0}
(gdb) print led->refcount
$9 = 1
(gdb) print led->profile
$10 = (struct ratbag_profile *) 0x5555555c8170
(gdb) print led->link
$11 = {prev = 0x5555555d0e70, next = 0x5555555c8500}
(gdb) print led->colordepth
$12 = RATBAG_LED_COLORDEPTH_RGB_888
(gdb) print led->ms
$13 = 21852
(gdb) print led->brightness
$14 = 216
(gdb) print led->dirty
$15 = false
(gdb) print led->modes
$16 = 3
`

@huseyinsaatci @shuriken1812
Just use openrgb if you need Logitech g213 keyboard support


FYI: Works on Linux

Sorry for opening an issue for this but just wanted to give you a heads up, this companion app has been working well for me on Linux (Ubuntu 21.04). I use the method of running npm install and node script.js in the folder of my Slippi files and they upload successfully; maybe just update the README with this info, as it says it only works with Windows.

thanks for letting me know! README updated


PostgreSQLModel should use Int64 (instead of int)

When utilizing PostgreSQLModel in Vapor 3 the int declared as the id is actually stored as a bigint in postgres according to pgadmin. However you cannot declare id as an Int64/bigint
final class myClass: Codable {
  var id: Int?
  var name: String
  var createdAt: Date?
  var updatedAt: Date?

  // MARK: Init
  init(name: String) {
    self.name = name
  }

  init(id: Int, name: String) {
    self.id = id
    self.name = name
  }
}

if already being stored as a bigint in pg, I purpose just changing the int? to an Int64? to prevent breaking any bigint keys that already exist.

If I recall, I also had problems using Int64 IDs, but can’t remember the error message.
I also remember changing those primary keys to BIGINT automatically for 8-byte wide integers (which Int is on 64-bit systems). So I’d say at least the BIGINT part is working as expected; use Int32 if you don’t want BIGINTs.

@tanner0101
if you do this "var id: Int64?" when using a postgreSQL model, it tells you it does not conform and attempts to re-add an id stub. even though they are being stored in pg as int64/bigint

@brntphish does it work if you manually conform to Model though?

This should work if you use Model directly (not PostgreSQLModel). Closing this since the default should not be a problem on any platform that Vapor supports (they are all 64-bit).


Should GlobalSimpleAgg output one row immediately after created?

Current behavior:
=> create table t (a int, b int);
CREATE_TABLE

=> create materialized view mv as select count(*), sum(a) from t; select * from mv;
CREATE_MATERIALIZED_VIEW
 count | sum
-------+-----
(0 rows)

=> flush; select * from mv;
FLUSH
 count | sum
-------+-----
     0 |
(1 row)

I'm not really sure if it's necessary to have an output row immediately after create materialized view. Any ideas? I remember there was a discussion on this, but can't find any link about it. And I remember someone said it's hard to implement and maybe not worth doing so, not quite sure.

https://github.com/risingwavelabs/risingwave/issues/4954#issuecomment-1231276799 this one?

#4954 (comment) this one?

Oh yes it is! In fact the current behavior is no longer the same as the one described in #4954, while the comment seems still true for our system. Let me quote the comment here and we may discuss in this issue later if needed.

@TennyZhuang: know the bug long long ago, but to fix this, we have to send a message to downstream when the first time we set up an actor. The SimpleAgg is the only operator who has the behavior but the fix may introduce too many efforts. I'd prefer keep the bug until we find a elegant way.

I think the current behavior is good enough and no users will notice this latency.

Any conclusion?


gitlab.gnome.org: Max retries exceeded: connect timeout=15

pypillowfight:
requests.exceptions.ConnectTimeout: HTTPSConnectionPool(host='gitlab.gnome.org', port=443): Max retries exceeded with url: /World/OpenPaperwork/libpillowfight (Caused by ConnectTimeoutError(<urllib3.connection.VerifiedHTTPSConnection object at 0x7f97179c4640>, 'Connection to gitlab.gnome.org timed out. (connect timeout=15)'))

The timeouts for known SCM should be much higher.

pyxdg can occasionally raise IncompletePackageMetadata: pyxdg has no license in PyPI metadata, because timeout on freedesktop.org, when http://freedesktop.org/wiki/Software/pyxdg is slow, meaning it cant reach SCM gitlab.freedesktop.org, so base domains need to also have a higher timeout, or add a rule for freedesktop.org if it can be used to reach gitlab:
ERROR    https_everywhere.adapter:adapter.py:124 handle_error requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='freedesktop.org', port=443): Read timed out. (read timeout=15)
ERROR    https_everywhere.adapter:adapter.py:124 handle_error requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='freedesktop.org', port=443): Read timed out. (read timeout=15)
ERROR    https_everywhere.adapter:adapter.py:124 handle_error requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='freedesktop.org', port=443): Read timed out. (read timeout=15)
ERROR    https_everywhere.adapter:adapter.py:124 handle_error requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='freedesktop.org', port=443): Read timed out. (read timeout=15)
ERROR    https_everywhere.adapter:adapter.py:124 handle_error requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='freedesktop.org', port=443): Read timed out. (read timeout=15)
ERROR    https_everywhere.adapter:adapter.py:124 handle_error requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='freedesktop.org', port=443): Read timed out. (read timeout=15)

upt-pypi
E               requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='framagit.org', port=443): Read timed out. (read timeout=11)


Day Night Toggle

A day night toggle made using html and css @1dharode please assign this to me under hacktoberfest

Can i work on it??

Can you please assign me this issue @1dharode ?

I wish to contribute. Kindly assign this to me.


MOTR-269 Release Sample Count Visualization

Key Changes

Replaced mocked upload/download stat UIs with UIs representing actual release sample counts in Dashboard component.
Updated Sidebar component with functionality to expand/collapse sidebar.
Added the rendering of tooltips for active sidebar items when the sidebar is collapsed.
Updated all pages that required authentication to support the collapsible sidebar.
Updated unit test assertions due to changes of various UI components.
Upgraded some npm dependencies.

Steps to test sidebar

Sign into local instance of this branch.
Expect to see sidebar to be collapsed by default.
Click on the hamburger menu icon at the top of the sidebar. Expect to see the sidebar being expanded.
Then click on the close icon at the top of the sidebar. Expect to see the sidebar being collapsed.
You may wish to repeat the steps above on other pages.

Steps to test dashboard

Sign into local instance of this branch and go to the ^/dashboard page.
Expect to see the Internal Release and PASS1A 6-Month button being active by default at the upper-right corner.
Click on the PASS1B 6-Month button and expect to see the UIs (e.g. various metrics, sample count plot/table) being updated on the dashboard.
Click on the Samples dropdown menu above the plot and select Tissue by count. Expect to see the plot being re-rendered.
Click on the Sort dropdown menu above the table and select Tissue name ascending. Expect to see the table being sorted by tissue name in alphabetical order.

@ysyskim4 Thanks for reviewing the PR. The default sort for the table is by tissue code (e.g. T30). Any suggestion on making it more intuitive will be greatly appreciated!

@jimmyzhen thanks for the answer! then just want to suggest one thing for the next version - would it be too much work to add tissue code by adding one more column or by adding tissue code to the tissue name like T40 Adrenal Powder instead of Adrenal Powder ?

@ysyskim4 Thanks for the suggestion. I can prepend the tissue codes to the tissue names in this version.

@ysyskim4 @cteng585 @kilodalton I have merged the latest version of the dev branch into this PR and resolved all the conflicts, along with couple of addition changes:

Prepending tissue codes to tissue names in the sample count table as Young recommended.
Making the Dashboard the entry page upon authentication.
Added messages to clarify that PASS1A-06 and PASS1B-06 phenotypic data consists of 18-month data.

Please review/test again if possible. Thanks!

@cteng585, thank you for taking the time out to review the PR. Your comments and suggestion are greatly appreciated.
My thoughts on your comment

Selecting a sorting type in the dashboard (e.g. Assay by Name) will stay preserved even if the user navigates to another part of the data hub.

Persisting the states of sorting on the dashboard (as well as the release and phase filters) is intentional in the attempt to provide convenience to users who return to the dashboard upon looking up other relevant data/analysis on the portal.

Trying to enter a gene name in the "Meta analysis of Public Data" part of the data hub using the "Enter" key clears the entry field. You have to click on the magnifying glass with your mouse right now to have it function correctly.

Although this behavior is somewhat outside of this PR's scope, I agree that the UX can be improved, especially when the human meta analysis feature has not been fully implemented. My goal is to revisit the analyses with David Amar and make them available on the data hub portal going forward.

Maybe clicking the tissue number or assay number at the top of the dash board applies that sorting method (by name) in the bar graph? I just get this feeling that they should be clickable, but I'm not sure about this.

This is actually an interesting user observation, since the highlighted metrics are non-interactive. Is it the borders that make them look like buttons, or their placement on the page?

For me, I think it's the borders that make me feel like they should be clickable.

It is possible that the drop shadow makes it looking like a button. I will fiddle with it and see whether something different can be attempted.
Nonetheless, this doesn't sound like a showstopper for the PR to be moved forward.


WaitForIdle only sleep within select

Before everytime within the loop we would sleep for 10 microseconds, now
we're only sleeping if output has drained but there are still input
samples.

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

Leaving this one as draft since we want to properly test and get this merged first https://github.com/prometheus/prometheus/pull/10878

seems like this is probably not needed, so I guess let's close it :)

We can use a similar technique to https://github.com/prometheus/prometheus/pull/10973 to avoid that sleep


fix OpenSearch Dashboards install dir

Signed-off-by: Tianle Huang<EMAIL_ADDRESS>Description
The install dir has been changed to remove architecture and platform.
Issues Resolved
Resolves https://github.com/opensearch-project/opensearch-build/issues/1310
Test
Before
File "/usr/share/opensearch/workspace/opensearch-build/src/test_workflow/integ_test/service_opensearch_dashboards.py", line 50, in start
    self.__add_plugin_specific_config(self.additional_config)
  File "/usr/share/opensearch/workspace/opensearch-build/src/test_workflow/integ_test/service_opensearch_dashboards.py", line 86, in __add_plugin_specific_config
    with open(self.opensearch_dashboards_yml_dir, "a") as yamlfile:
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpgp4hhhgu/local-test-cluster/opensearch-dashboards-1.2.0-linux-x64/config/opensearch_dashboards.yml'

Now, the integ test can run successfully.
2021-12-11 19:14:17 INFO     Keeping /tmp/tmp24ydsfzp
2021-12-11 19:14:17 INFO     | functionalTestDashboards | with-security        | PASS  |    0 |
2021-12-11 19:14:17 INFO     | functionalTestDashboards | without-security     | PASS  |    0 |

Check List

[x] Commits are signed per the DCO using --signoff

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

Codecov Report

Merging #1313 (7f96d9a) into main (de29f28) will decrease coverage by 19.80%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##               main    #1313       +/-   ##
=============================================
- Coverage     93.87%   74.07%   -19.81%
  Complexity       11       11
=============================================
  Files           134       17      -117
  Lines          2956       81     -2875
  Branches          8        8
=============================================
- Hits           2775       60     -2715
+ Misses          173       13      -160
  Partials          8        8

Impacted Files
Coverage Δ

...rkflow/integ_test/service_opensearch_dashboards.py

src/system/working_directory.py

src/build_workflow/builder.py

src/test_workflow/test_cluster.py

src/test_workflow/test_recorder/log_recorder.py

src/test_workflow/test_component.py

...workflow/opensearch/build_artifact_check_plugin.py

src/run_bwc_test.py

...eg_test/integ_test_runner_opensearch_dashboards.py

src/system/config_file.py

... and 107 more

Continue to review full report at Codecov.

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


CM-777: Parsing HTML With AngleSharp in C#

This PR includes the source code with examples for the article Parsing HTML With AngleSharp in C#.

@elfico I've made the necessary changes that you have outlined, can you confirm that everything is alright now?


Add inline sourcemaps option to TS compilation

Is it possible to debug ts playcanvas game with breakpoints?

By default, inlineSourceMap and inlineSources are true in the tsconfig.json so the sourcemap is inlined to the built JS file
So yes, you can add breakpoints to TS source in devtools

I'm going to make a change to the project so there's debug and production config files to use so that a final build without source maps can be created

Fixed as of #5


Fix incorrect cast in NioDomainSocketChannel.parent()

Motivation:
NioDomainSocketChannel.parent() returned a ServerSocketChannel, which is not implemented by NioServerDomainSocketChannel. This makes the parent method unusable.
Modification:
Change the return type and cast to ServerChannel. Unfortunately this is a binary incompatible change, but there is no way to make this change in a binary compatible way, and the method never worked in the first place.
Result:
parent() becomes usable.

oops, test case still needs some work

Needs a revapi exception:
{
  "ignore": true,
  "code": "java.method.returnTypeChanged",
  "old": "method io.netty.channel.socket.ServerSocketChannel io.netty.channel.socket.nio.NioDomainSocketChannel::parent()",
  "new": "method io.netty.channel.ServerChannel io.netty.channel.socket.nio.NioDomainSocketChannel::parent()",
  "justification": "ADD YOUR EXPLANATION FOR THE NECESSITY OF THIS CHANGE"
  /*  "oldType": "io.netty.channel.socket.ServerSocketChannel",
  "newType": "io.netty.channel.ServerChannel",
  "package": "io.netty.channel.socket.nio",
  "classQualifiedName": "io.netty.channel.socket.nio.NioDomainSocketChannel",
  "classSimpleName": "NioDomainSocketChannel",
  "methodName": "parent",
  "elementKind": "method",
  "oldArchive": "io.netty:netty-transport:jar:4.1.114.Final",
  "oldArchiveRole": "primary",
  "newArchive": "io.netty:netty-transport:jar:4.1.115.Final-SNAPSHOT",
  "newArchiveRole": "primary",
  */

},

It might also need a japicmp exception.

Thanks!


Recipes link goes nowhere

When viewing the recipes readme the link to the only recipe goes to the wrong location.  It's set to https://github.com/bloomberg/brisket/blob/master/docs/recipes/README.md#fetching-multiple-models.md which doesn't work.

Hello Donavan! I put in a PR to fix the link, for now you can find it here: Fetching Multiple Models


Create a player which moves around the worlds

One basic piece in all our voxels creations is the player or the viewer who travells around the world. Let's explore the best approaches to implement it.
We can have several cameras:

First Person
Over the player
In front of the player
In the back of the player
...

Let's reuse this ticket to:

Create a simple model
Move it around the world

The plan is to use a KinematicBody and move it over a plain. The first step could be a sphere. The idea later is to start adding animations (ideally some done with bones).


Add Last Action Taken Column to generate sequence nodes

Be able to regenerate sequences of actions

commiting to incorrect issue, this still needs to special case in behavior tree builder

commiting to incorrect issue, this still needs to special case in behavior tree builder

Adam has idea around all conditions being same and then check for last action in order

Implement up tree behavior generation for LAT

Add collapsible indicator

[ ] last action taken into binary

last action taken also needs to be configurable

I'm dumb and tested on wrong thing, reopening

possibly add conditions from original action on tree?


Guidance: pattern and samples for authoring templates that can be shared between official and unofficial

This issue tracks this bullet-point from https://github.com/dotnet/dnceng/issues/2148

There is guidance, a pattern and samples for authoring templates that can be shared between official and unofficial, and don't run excessive SDL scans.

We can conditionalize Microbuild / 1ES template usage via variables.  ie, we can propose one of the following patterns.
azure-pipelines.yml
variables:
- ${{ if and(ne(variables['System.TeamProject'], 'public'), in(variables['Build.Reason'], 'Schedule')) }}:
  - name: oneespttemplate
    value: azure-pipelines/MicroBuild.1ES.Official.yml@MicroBuildTemplate
- ${{ if and(ne(variables['System.TeamProject'], 'public'), notIn(variables['Build.Reason'], 'Schedule')) }}:
  - name: oneespttemplate
    value: azure-pipelines/MicroBuild.1ES.Unofficial.yml@MicroBuildTemplate
resources:
  repositories:
  - repository: MicroBuildTemplate
    type: git
    name: 1ESPipelineTemplates/MicroBuildTemplate
    ref: refs/tags/release
extends:
  template: ${{ variables['oneespttemplate'] }}

or
variables.yml
variables:
- ${{ if and(ne(variables['System.TeamProject'], 'public'), in(variables['Build.Reason'], 'Schedule')) }}:
  - name: oneespttemplate
    value: azure-pipelines/MicroBuild.1ES.Official.yml@MicroBuildTemplate
- ${{ if and(ne(variables['System.TeamProject'], 'public'), notIn(variables['Build.Reason'], 'Schedule')) }}:
  - name: oneespttemplate
    value: azure-pipelines/MicroBuild.1ES.Unofficial.yml@MicroBuildTemplate

azure-pipelines.yml
variables:
- template: variables.yml
resources:
  repositories:
  - repository: MicroBuildTemplate
    type: git
    name: 1ESPipelineTemplates/MicroBuildTemplate
    ref: refs/tags/release
extends:
  template: ${{ variables['oneespttemplate'] }}

I don't know that we should provide a "variables.yml" template via Arcade unless we find there to be a consistent pattern for the conditions.  It feels like teams will have slightly different needs and need to control the conditions themselves.
FYI @riarenas

Is there a scenario in which a repo needs to import a different flavor of template depending on a condition?
What would be the guidance for say, how we are going to refactor job.yml, or the source-build templates so that we can share them between the official and unofficial without so much duplication of the YAML?

Is there a scenario in which a repo needs to import a different flavor of 1ES template depending on a condition?

My understanding is that "official" applies to builds which produce shipping output, "unofficial" would apply more to an internal CI scenario which doesn't produce shipping assets but validates the build.

What would be the guidance for say, how we are going to refactor job.yml, or the source-build templates so that we can share them between the official and unofficial without so much duplication of the YAML?

what is your definition of "official" and "unofficial" for this question?  ie, are you referring to the 1es.official and 1es.unofficial templates or "official" meaning internal builds and "unofficial" meaning public?

I'm referring to eng/common/templatesand eng/common/templates-official

yeah, that's a different issue that we need to consider  I actually think there are 3 separate issues (in my mind) for the bullet point which spawned this particular issue.

There is guidance, a pattern and samples for authoring templates that can be shared between official and unofficial, and don't run excessive SDL scans.

we have a plan for 1es official / unofficial template adoption (that's this issue)
we have a sane approach to manage our templates (that's the issue you are referring to).
we have a reasonable pattern for reducing SDL noise which 1es templates incur.

I'll update the name of this issue to be more specific.

Is 1. future proofing for when we get asked to move non-production to the 1es templates as well?

Back on topic though! I think this is a good approach for this scenario, and I agree that we don't need to provide the variables via Arcade.

Is 1. future proofing for when we get asked to move non-production to the 1es templates as well?

yes, it's having an answer for that scenario, and also i wanted to understand it better because it could potentially impact how we approach 2.


Why is long_name not in the attributes - Macehead and Cabauw

When processing GCWERKS data for Macehead and some data for Cabauw the long_name attribute isn't being added to the Dataset. Need to look into why this isn't happening.

@gareth-j - was this something that needed fixing then? Or could this be closed?

This can be closed.


Ensure that the conda environment is portable

The included conda environment at https://github.com/PrefectHQ/prefect-intel/blob/main/conda-environment.yaml is usable across Prefect internal machines which are all running macOS. We must confirm that this install is usable across Intel development environments as well.
The requirements generated by exporting the environment may be overly constrained.

Hi Michael,
The CS team at Prefect has been investigating this and other Windows compatibility issues for this repo. A modification of the conda-environment.yaml to:
name: prefect-intel
channels:
  - defaults
dependencies:
  - ca-certificates=2022.3
  - certifi=2021.10.8
  - openssl=1.1
  - pip=21.2.4
  - python=3.9
  - setuptools=61.2
  - sqlite=3.38
  - tk=8.6
  - tzdata=2022a
  - wheel=0.37
  - xz=5.2
  - zlib=1.2
  - pip:
    - -e ./prefect

has shown to be portable from macOS to Windows. As you can see above, the patches and builds are unspecified, so that the exported environment is not overly constrained, as you mentioned. Platform-specific dependencies for macOS have also been removed from this (libffi, libcxx, ncurses, readline) as they are installed when Python is.

Corresponding (Windows/macOS) requirements.txt:
aiofiles==0.8.0
aiohttp==3.8.1
aiohttp-cors==0.7.0
aiosignal==1.2.0
aiosqlite==0.17.0
alembic==1.8.0
anyio==3.6.1
asgi-lifespan==1.0.1
asgiref==3.5.2
async-timeout==4.0.2
asyncpg==0.25.0
attrs==21.4.0
azure-core==1.24.1
azure-storage-blob==12.12.0
blessed==1.19.1
boto3==1.24.2
botocore==1.27.2
cachetools==5.2.0
certifi==2021.10.8
cffi==1.15.0
charset-normalizer==2.0.12
click==8.1.3
cloudpickle==2.1.0
colorful==0.5.4
commonmark==0.9.1
coolname==1.1.0
croniter==1.3.5
cryptography==37.0.2
dask==2022.5.2
distlib==0.3.4
distributed==2022.5.2
docker==5.0.3
fastapi==0.78.0
filelock==3.7.1
frozenlist==1.3.0
fsspec==2022.5.0
google-api-core==2.8.1
google-auth==2.6.6
google-cloud-core==2.3.0
google-cloud-storage==2.3.0
google-crc32c==1.3.0
google-resumable-media==2.3.3
googleapis-common-protos==1.56.2
gpustat==1.0.0b1
greenlet==1.1.2
grpcio==1.43.0
h11==0.12.0
HeapDict==1.0.1
httpcore==0.15.0
httpx==0.23.0
idna==3.3
isodate==0.6.1
Jinja2==3.1.2
jmespath==1.0.0
jsonschema==4.6.0
kubernetes==23.6.0
locket==1.0.0
Mako==1.2.0
MarkupSafe==2.1.1
msgpack==1.0.4
msrest==0.6.21
multidict==6.0.2
numpy==1.22.4
nvidia-ml-py3==7.352.0
oauthlib==3.2.0
opencensus==0.9.0
opencensus-context==0.1.2
packaging==21.3
partd==1.2.0
pendulum==2.1.2
platformdirs==2.5.2
-e ./prefect
prometheus-client==0.13.1
protobuf==3.20.1
psutil==5.9.1
py-spy==0.3.12
pyasn1==0.4.8
pyasn1-modules==0.2.8
pycparser==2.21
pydantic==1.9.1
Pygments==2.12.0
pyparsing==3.0.9
pyrsistent==0.18.1
python-dateutil==2.8.2
python-slugify==6.1.2
pytz==2022.1
pytzdata==2020.1
PyYAML==6.0
ray==1.12.1
readchar==3.0.5
requests==2.27.1
requests-oauthlib==1.3.1
rfc3986==1.5.0
rich==12.4.4
rsa==4.8
s3transfer==0.6.0
six==1.16.0
smart-open==6.0.0
sniffio==1.2.0
sortedcontainers==2.4.0
SQLAlchemy==1.4.37
starlette==0.19.1
tblib==1.7.0
text-unidecode==1.3
toml==0.10.2
toolz==0.11.2
tornado==6.1
typer==0.4.1
typing_extensions==4.2.0
urllib3==1.26.9
uvicorn==0.17.6
virtualenv==20.14.1
wcwidth==0.2.5
websocket-client==1.3.2
yarl==1.7.2
zict==2.2.0

👍 Can you open a PR to update the conda specification?


Issue with icu4c on<EMAIL_ADDRESS>& php7.4 (on M1)

Describe the bug
During a brew upgrade. Seems like it's trying to link with the old version of icu4c, that was just upgraded.
==> Upgrading icu4c 68.2 -> 69.1
==> Downloading https://ghcr.io/v2/homebrew/core/icu4c/manifests/69.1
######################################################################## 100.0%
==> Downloading https://ghcr.io/v2/homebrew/core/icu4c/blobs/sha256:25a1ec460d422ba5abff15dc5cb60ad36003ad021585fa7be278d1dca6fcd2c4
==> Downloading from https://pkg-containers-az.githubusercontent.com/ghcr1/blobs/sha256:25a1ec460d422ba5abff15dc5cb60ad36003ad021585fa7be278d1dca6fcd2c4?se=2021-04-25T18%3A30%3A0
######################################################################## 100.0%
==> Pouring icu4c--69.1.arm64_big_sur.bottle.tar.gz
==> Caveats
icu4c is keg-only, which means it was not symlinked into /opt/homebrew,
because macOS provides libicucore.dylib (but nothing else).

If you need to have icu4c first in your PATH, run:
  echo 'export PATH="/opt/homebrew/opt/icu4c/bin:$PATH"' >> ~/.zshrc
  echo 'export PATH="/opt/homebrew/opt/icu4c/sbin:$PATH"' >> ~/.zshrc

For compilers to find icu4c you may need to set:
  export LDFLAGS="-L/opt/homebrew/opt/icu4c/lib"
  export CPPFLAGS="-I/opt/homebrew/opt/icu4c/include"

For pkg-config to find icu4c you may need to set:
  export PKG_CONFIG_PATH="/opt/homebrew/opt/icu4c/lib/pkgconfig"

==> Summary
🍺  /opt/homebrew/Cellar/icu4c/69.1: 259 files, 73.3MB
Removing: /opt/homebrew/Cellar/icu4c/68.2... (259 files, 73MB)
Removing: /Users/henk/Library/Caches/Homebrew/icu4c--68.2.arm64_big_sur.bottle.tar.gz... (27.2MB)

[..]

==> Reinstalling 2 broken dependents from source:
<EMAIL_ADDRESS><EMAIL_ADDRESS>==> Downloading https://ghcr.io/v2/shivammathur/php/php/7.3/manifests/7.3.27-1
######################################################################## 100.0%
==> Downloading https://ghcr.io/v2/shivammathur/php/php/7.3/blobs/sha256:82e1747e76551dba8c8cc2941c73d28eb78456a293c86b48b995b689756d699b
==> Downloading from https://pkg-containers-az.githubusercontent.com/ghcr1/blobs/sha256:82e1747e76551dba8c8cc2941c73d28eb78456a293c86b48b995b689756d699b?se=2021-04-25T18%3A35%3A0
######################################################################## 100.0%
==> Reinstalling<EMAIL_ADDRESS>==> Pouring<EMAIL_ADDRESS>==><EMAIL_ADDRESS>config-set php_ini /opt/homebrew/etc/php/7.3/php.ini system
Last 15 lines from<EMAIL_ADDRESS>2021-04-25 20:28:52 +0200

<EMAIL_ADDRESS>config-set
php_ini
/opt/homebrew/etc/php/7.3/php.ini
system

dyld: Library not loaded: /opt/homebrew/opt/icu4c/lib/libicui18n.68.dylib
  Referenced from<EMAIL_ADDRESS>  Reason: image not found

Warning: The post-install step did not complete successfully
You can try again using:
  brew postinstall<EMAIL_ADDRESS>==> Caveats
To enable PHP in Apache add the following to httpd.conf and restart Apache:
    LoadModule php7_module<EMAIL_ADDRESS>
    <FilesMatch \.php$>
        SetHandler application/x-httpd-php
    </FilesMatch>

Finally, check DirectoryIndex includes index.php
    DirectoryIndex index.php index.html

The php.ini and php-fpm.ini file can be found in:
    /opt/homebrew/etc/php/7.3/

<EMAIL_ADDRESS>is keg-only, which means it was not symlinked into /opt/homebrew,
because this is an alternate version of another formula.

If you need to have<EMAIL_ADDRESS>first in your PATH, run:
  echo 'export PATH="/opt/homebrew/opt/php@7.3/bin:$PATH"' >> ~/.zshrc
  echo 'export PATH="/opt/homebrew/opt/php@7.3/sbin:$PATH"' >> ~/.zshrc

For compilers to find<EMAIL_ADDRESS>you may need to set:
  export<EMAIL_ADDRESS>  export<EMAIL_ADDRESS>

To have launchd start<EMAIL_ADDRESS>now and restart at login:
  brew services start<EMAIL_ADDRESS>Or, if you don't want/need a background service you can just run:
  php-fpm
==> Summary
🍺<EMAIL_ADDRESS>516 files, 75.4MB
==> Downloading https://ghcr.io/v2/shivammathur/php/php/7.4/manifests/7.4.16
######################################################################## 100.0%
==> Downloading https://ghcr.io/v2/shivammathur/php/php/7.4/blobs/sha256:e2ff216d661c207e186501356b9d7205f8eedf41d1d4a0b67a9e36ea885c6c98
==> Downloading from https://pkg-containers-az.githubusercontent.com/ghcr1/blobs/sha256:e2ff216d661c207e186501356b9d7205f8eedf41d1d4a0b67a9e36ea885c6c98?se=2021-04-25T18%3A40%3A0
######################################################################## 100.0%
==> Reinstalling<EMAIL_ADDRESS>==> Pouring<EMAIL_ADDRESS>==><EMAIL_ADDRESS>config-set php_ini /opt/homebrew/etc/php/7.4/php.ini system
Last 15 lines from<EMAIL_ADDRESS>2021-04-25 20:34:11 +0200

<EMAIL_ADDRESS>config-set
php_ini
/opt/homebrew/etc/php/7.4/php.ini
system

dyld: Library not loaded: /opt/homebrew/opt/icu4c/lib/libicuio.68.dylib
  Referenced from<EMAIL_ADDRESS>  Reason: image not found

PHP versions

PHP 7.3<EMAIL_ADDRESS>PHP 7.4<EMAIL_ADDRESS>
To Reproduce
🤷♂
Expected behavior
brew upgrade should just work.
Screenshots/Logs

Additional context

Are you willing to submit a PR?

@HenkPoley
Thanks for reporting. icu4c was updated to 69.1 on homebrew/core. Working on a fix.

Looks like a simple rebuild with the new icu fixes it: brew reinstall<EMAIL_ADDRESS>--build-from-source

Yes, the rebuilds are in progress in CI, should be done in an hour

All formulae have been updated.

Run brew update and then install php
For example to install PHP 7.4

brew update
brew install<EMAIL_ADDRESS>

If you got Library not found error for icu4c before, run brew update then reinstall PHP.
For example to reinstall PHP 7.4

brew update
brew reinstall<EMAIL_ADDRESS>


Minor fixes

I just set this up on my computer. It's very nice, thanks!
I had some minor issues following the update to 2.3.0:

The compactor config seems to be required. It would crash with Must specify compactor config otherwise (I'm not sure about the config I put here, though)
https://github.com/grafana/loki/issues/4170 prevents version checks in binaries

Sorry I can't figure out how to make github notifications work at all in a useful way :( this got lost in a sea of other notifications I can't make stop...


HandlerThread use wrong thread priority

Reading the code it looks like the HandlerThreads use Thread.MIN_PRIORITY (IE priority 1) for the priority.
HandlerThread itself uses

Process.setThreadPriority(mPriority);

So I believe the correct priority to pass would be Process.THREAD_PRIORITY_LOWEST (19) or maybe something higher, but overall I think Thread.MIN_PRIORITY is a deceptive value to pass in creating the HandlerThread
I could be missing something here, but reading the code that stood out as strange to me.

@ryanzor thanks a lot for pointing it out. You are absolutely correct and we should be using android.os.Process instead of java.lang.Thread. I've created a PR that will be merged soon. Thanks!


Error in PPO implementation?

Hi there! I believe there may be an error in your PPO implementation.
In 3.ppo.ipynb, at the function ppo_update(), you compute the policy ratio using the expression
ratio = (new_log_probs - old_log_probs).exp()

however tracing the source of the variable old_log_probs shows it is actually lob probabilities computed with the exact same policy as new_log_probs. Thus, any variation in r(\theta) is due to random sampling from the action distributions. This might explain poor performance seen by some others in the issues. It seems at least one other GitHub implementation of PPO have the same issue.
If you inspect the OpenAI baseline PPO1 implementation, or stable-baselines source code, you'll see they construct two copies of the policy and copy parameters across after each update, which would be the correct way of computing the policy odds ratio.

Oooh I understand now - the policies will be the same only during the first epoch - after that they will be different. Please disregard :)


linux version?

it seems an amazing result, but I want to know is there any Linux version?

Already tested in ubuntu16.04.

Thanks for your attention.
but how you run the .bat file on Ubuntu?
Could you please guide me.

I focus on how to generate vmd files, so I just run IV step in OpenMMD/VMD 3D Pose Baseline Multi-Objects/applications/. and data in examples. If you focus on project, you need to run whole project step by step~ so there maybe a lot dependcy~

Yep, thank you @bailiqun for answering :D. @erjanmx That will be a good choice if you can focus on the python file component that is most helpful to you. Or you may have to run all the .bat files step by step on Windows. I will program an interface in the later version if possible.

@bailiqun @peterljq Thanks for your attention.
Finally, I was successful to run the code and get a good result.
my issue was I couldn't run the OpenPose code cause for my weak hardware, so finally I used AWS for that.
but there is another question?
is there any way to convert VMD to another motion files like BVH format?

For myself, I am not quite familiar with other formats like BVH. It will be great if you are willing to develop a relevant toolkit for conversion from vmd to other formats. :D By the way, here is a tool for relevant conversions and read/write in VMD. You may refer to this tool.

@HHIR You can see my project video2bvh. It was developed on Linux, and the output format is BVH.


float64 support?

Not sure if this is useful, since f32 is probably enough for most vector database usecases. But if you'd benefit from float64 vector, leave a comment below and give this issue a 👍

There's a couple of Go libraries I've seen that return an []float64. I'm not sure whether or not they actually use all that precision, but I think this would be great just for completeness.


ECS + AWS Route 53?

¡Hola!
I am trying to deploy a replica set on ECS (+route 53?); I am thinking about making a derivate of your image for that propouse. Would you kindly point me to some document about the node.js configuration app your'e using on it?
¡Gracias!

Hi @mautematico,
sorry, there is no documentation of the app itself. It uses the Marathon API to trigger the task starts etc., but I guess that's not available on ECS. To be honest, I doubt that you can port the app to interface with ECS.

Never used the Marathon API before, but I think some of my team leads may give me a hint.
¡Gracias!

You cannot use Marathon of you're not using Mesos or DC/OS. I guess you can't use this project on ECS, as I said before.
Therefore closing the issue.


Made editor section of luis inspector scrollable & made scrollbars th…

…inner.
Fixes #1514
===
Before:

After:

Eww.. scrollbars for tiny divs :)

Coverage remained the same at 57.201% when pulling 2aa96dc3f3167208b9fe07e117b3b4d5a21027c1 on toanzian/luis-inspector into dd26d76cceb8a26beb4e8ebd07b1b955286843b5 on master.

Coverage remained the same at 57.201% when pulling 2aa96dc3f3167208b9fe07e117b3b4d5a21027c1 on toanzian/luis-inspector into dd26d76cceb8a26beb4e8ebd07b1b955286843b5 on master.


Error - no bucket for users

When I try to authenticate a user I have this error:
ERRO[0014] no bucket for users
ERRO[0014] key required
2018/09/05 23:20:59 http: panic serving <IP_ADDRESS>:57072: interface conversion: interface is nil, not string
goroutine 11 [running]:
net/http.(*conn).serve.func1(0xc420055600)
/usr/lib/go/src/net/http/server.go:1491 +0x12a
panic(0x8a1c00, 0xc420012e40)
/usr/lib/go/src/runtime/panic.go:458 +0x243
github.com/LassoProject/lasso/handlers.CallbackHandler(0xb3af00, 0xc42010fad0, 0xc4200b2b40)
/root/go/src/github.com/LassoProject/lasso/handlers/handlers.go:414 +0x894
net/http.HandlerFunc.ServeHTTP(0x960320, 0xb3af00, 0xc42010fad0, 0xc4200b2b40)
/usr/lib/go/src/net/http/server.go:1726 +0x44
github.com/LassoProject/lasso/pkg/timelog.TimeLog.func1(0xb3af00, 0xc42010fad0, 0xc4200b2a50)
/root/go/src/github.com/LassoProject/lasso/pkg/timelog/timelog.go:33 +0x14b
net/http.HandlerFunc.ServeHTTP(0xc42012b660, 0xb3af00, 0xc42010fad0, 0xc4200b2a50)
/usr/lib/go/src/net/http/server.go:1726 +0x44
net/http.(*ServeMux).ServeHTTP(0xc420136780, 0xb3af00, 0xc42010fad0, 0xc4200b2a50)
/usr/lib/go/src/net/http/server.go:2022 +0x7f
net/http.serverHandler.ServeHTTP(0xc420054b80, 0xb3af00, 0xc42010fad0, 0xc4200b2a50)
/usr/lib/go/src/net/http/server.go:2202 +0x7d
net/http.(*conn).serve(0xc420055600, 0xb3b780, 0xc420139400)
/usr/lib/go/src/net/http/server.go:1579 +0x4b7
created by net/http.(*Server).Serve
/usr/lib/go/src/net/http/server.go:2293 +0x44d

@aaronpk is this similar to the error you saw a few weeks ago?
@gzzglc89 my fuzzy recollection of @aaronpk's issue was that this occurred once the first time lasso was authenticated against and then it went away.  Is this the case with your error?

FYI we're often in the IRC channel #lasso on freenode and can offer some support there

@bnfinet I have this error every time I try to authenticate the user, not only the first time.

I had this problem too at one point. IIRC I did something like delete the SQLite database and start over and it started working. I wasn't able to figure out the actual underlying issue.

@gzzglc89 did that resolve the issue for you?

@bnfinet it did not resolve but I'm using another way to authenticate so this is not needed


Executing other queries inside user-defined functions

Essentially #203, but inside user-defined functions. I didn't wanted to hijack that thread as it is moving in a different direction (mutating stuff).
Assuming SQLite allows that, would it be possible to enable SELECT inside user-defined functions? Currently I'm getting "TypeError: This database connection is busy executing a query".
My current use-case is a custom caching mechanism. Passing large BLOB or TEXT to a user-defined function is slow (not necessarily the passing, but reading them from disk) and makes the difference between 5000ms and 30ms. If I could SELECT inside the user-defined function I could only process the data I need and cache the results of the function for later. The user-defined function would then only accept the id as parameter instead of the data itself.

For the time being I'm using a second readonly connection to query the data inside the user-defined function. Works as expected and is only a little awkward. So if there is a way to flick a switch and allow the same connection to do that, that would be neato.

For the same reason as in #203, it's currently disabled. But in a future version there might be an "expert mode" that can be turned on, for people with these needs.

For future reference: I don't think SQLite itself has any issues with doing what is asked here

An application-defined function is permitted to call other SQLite interfaces. However, such calls must not close the database connection nor finalize or reset the prepared statement in which the function is running.

https://www.sqlite.org/c3ref/create_function.html
I'm not familiar with SQLite internals, but that sounds like the list of things you can not do is pretty short?


IO/get_time not working

Reproducing the behavior
Run the following program using bend run-c:
def rnd(n):
  with IO:
    timestamp <- IO/get_time()
    bend n, state=timestamp:
      when n != 0:
        state = state ^ (state << 13)
        state = state ^ (state >> 17)
        state = state ^ (state << 5)
        res = List/Cons(state % 100, fork(n - 1, state))
      else:
        res = List/Nil
    return wrap(res)

Expected output is a random list of numbers
Actual output is λa (a IO/Done/tag IO/MAGIC [λc (c 0 (39, 81))])
System Settings
Example:

HVM: 2.0.22
Bend: 0.2.36
OS: Linux Mint 21.3 Cinnamon
CPU: Intel Core i5-8250U
GPU: Intel UHD Graphics 620
Cuda Version N/A

Additional context
No response

It works when used like this:
def rnd(n):
  with IO:
    timestamp <- IO/get_time()
    bend n, state=timestamp:
      when n != 0:
        state = state ^ (state << 13)
        state = state ^ (state >> 17)
        state = state ^ (state << 5)
        res = List/Cons(state % 100, fork(n - 1, state))
      else:
        res = List/Nil
    return wrap(res)

def main:
  with IO:
    x <- rnd(5)
    return x

@developedby is this how it's supposed to be used?
I remember main should wrap x, but it doesn't work that way.

when I run the revised code I get [λb (b 0 (29, 75)), λd (d 0 (66, 87)), λf (f 0 (84, 3)), λh (h 0 (83, 74)), λj (j 0 (32, 88))], what does this mean?

@NoamDev Yes, I just tested here and it works. If you don't wrap the return of main usually nothing breaks, you just can't type check it.
I still need to add some code to unwrap the final IO value coming from main so that it looks nicer.
@GitCat3 you're probably not running the latest version of Bend. Please try installing the developement version (clone/download the git repo and then cargo install --path .).
It's returning a list of Result/Ok(timestamp). In the latest version of Bend we already unwrap the result for you since get_time should never fail.

You can also install it using cargo install --git https://github.com/HigherOrderCO/bend


Vista previa icono miniatura error

Microsoft PowerToys version
v0.66.0
Installation method
PowerToys auto-update
Running as admin
None
Area(s) with issue?
File Explorer: Thumbnail preview
Steps to reproduce
Con la última actualización, al intentar enviar a la papelera pdfs retocados, ha aparecido el siguiente error:

No deja eliminar los pdfs si no cierras los procesos del COM surrogate.
Creo que también interviene en el problema el Acrotray.exe.
Antes de la última actualización no me había pasado y, no sé si el error és de la actualización o de alguna otra aplicación instalada el mismo día.
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software

I had that as well right now on a PDF file. I was using an older version because I was on an older Windows 10 build. Recently I was able to update Windows and PowerToys and now this is happening. I wasn't sure which one caused that, because the new Windows version did make a lot of stuff run slower like taking screenshots sometimes takes a couple of seconds to actually trigger and so on (it became unusable if I need a quick screenshot before stuff change on screen... but anyway, this is not the place for this report)
I've clicked on Report a bug. Where does it save it, so I can send it to you?
BTW, I've just tried deleting the file again now and it worked. The place where it didn't work was when I tried to overwrite it with a new file form the internet with same name

Are you still experiencing this issue? /needinfo

@cinnamon-msft, I'm not.


ERROR:app.pipeline.Pipeline:Unable to create Encoder

First of all, thanks for the work, I'm trying to work with your code with ds 6.1.1. that I run from docker container created from nvcr.io/nvidia/deepstream:6.1.1-triton
When  the output is rtsp it works properly, when I try to write mp4 files it does not work:
INFO:app.pipeline.Pipeline:Creating Encoder
ERROR:app.pipeline.Pipeline:Unable to create Encoder
ERROR:app.pipeline.Pipeline:If the following error is encountered:
/usr/lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block
Preload the offending library:
export LD_PRELOAD=/usr/lib/aarch64-linux-gnu/libgomp.so.1

Traceback (most recent call last):
  File "run.py", line 10, in <module>
    run_pipeline(args.source_uri)
  File "/root/deepstream-python/deepstream/app/core.py", line 11, in run_pipeline
    pipeline = Pipeline(
  File "/root/deepstream-python/deepstream/app/pipeline.py", line 106, in __init__
    self._create_elements()
  File "/root/deepstream-python/deepstream/app/pipeline.py", line 357, in _create_elements
    self.sink_bin = self._create_mp4_sink_bin()
  File "/root/deepstream-python/deepstream/app/pipeline.py", line 266, in _create_mp4_sink_bin
    encoder.set_property("bitrate", 33000000)
AttributeError: 'NoneType' object has no attribute 'set_property'

The error is not explicit, I think that I miss some codec or smth like that in my container, may be you can point thai I miss

Have you tried the suggested action in the error message?

Preload the offending library:
export LD_PRELOAD=/usr/lib/aarch64-linux-gnu/libgomp.so.1

This env var should be set in the container before starting the pipeline.

This is for jetson devices, as you can see from path aarch64-linux-gnu/ but I'm working at x_86 machine

I started with your container and modified it for my proposes and it works


Investigate Compatability with Node 6.X

During WDD 2016 one user reported errors in what appeared to be core Node code. The only difference between his rig and mine that I could tell was the Node version, me being on 5.5.X and him being on 6.X.X

Confirmed grunt patternlab:serve works on Node 5.0.0 and throws the following error on Node 6.2.2:

Is this going to be solved any time soon?

Sorry, this is not a current priority of mine. I'd welcome help understanding why this is breaking for grunt users on newer versions of Node and or PL.  PL core has changed quite a bit since first reported

using node version 6.10.2 the patternlab:serve task works as intented for us.


SortBy: should not be part of the query parameter q

There is Rest API standards written here https://consoledot.pages.redhat.com/docs/dev/developer-references/rest/sorting.html we should try to follow as possible.

At the moment the "sorting field" is part of the query parameter q. E.g. q=sort:severity. This is not intuitive since q (query) should be used for only filtering data. The sorting data, just like pagination, represent "how we want to see the filtered data" but is not used to filter data itself.
Following the best practices of the link above, ideally we should have something like q=my_query&sort_by=field_name:desc.

Here a more complete example of how ideally the GET query might look like:
q=my_query&sort_by=field_name:desc&offset=10&limit=0

This way each query parameter has its own role and the whole request is easier to read and create (from the human perspective)

Sikula is following the concepts as GitHub in this case: https://docs.github.com/en/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#sorting-issues-and-pull-requests
In case of the Trustification SPoG UI/API we expect people to be more familiar with GitHub's search syntax than with the definition of "console dot". In order to support the "simple" search approach (where the user does not formulate the query string, but the code is doing that) it doesn't really matter IMHO.
The expectation is, that either the human is interested and capable in writing a custom query, then sorting should be part of the request the user writes. Or the user isn't, then it doesn't matter.
It would only matter in cases where the focus is on the actual HTTP request. But as this is a topic of SPoG UI, I think we might want to transfer the issue. Or create a new one there.


Bump Tor Browser to 5.5.3

Thank you for the contribution. It was merged directly as 2e6eff152ef70c2a0a959b20babb35f4dfa3568c to keep commit history cleaner. Your contribution is still credited to you.


Support for YAML, TOML?

@hkellaway Hi, have you thought about extending this framework to work with YAML and/or TOML formats as well, or are you just sticking with JSON? Thanks.

the idea has just been to stick with JSON
if you like the implementation Gloss uses, I'd encourage you to take inspiration and write those libraries yourself!


Moving to selenium 4 and adding layout tests

Was looking to add some test around relative location of elements and this is easily done in Selenium 4, so have upgraded references to Selenium 4. Have included a basic relative location test for now but scope to increase coverage, need to consider how best to sample different configurations, @istride can discuss in our catch up

@istride investigated the multiple browser testing a bit further with selenium but couldn't find a way to automate tests across multiple browsers. Have set up firefox and edge nodes in the docker-compose, but they are currently not being used in the tests. There must be a way to loop through all the tests running in each browser but I couldn't get anything to work. Think the thread below is on the right lines but couldn't figure it out.
https://stackoverflow.com/questions/11869431/selenium-parallel-browser-testing-in-python
Also as we discussed, some tests had to be modified for different browsers and I couldn't find a workaround for this so have just left everything running in chrome. Think this is probably the best solution for now. This PR upgrades to selenium 4 and includes some basic tests around layout and varying the window size, so probably still worth merging. Let me know any comments, thanks


Filters

Filtering server side
Is there any news / plans for filter integration,
like search only for a specific content type: audio / video / files,
or channel and tags...
(if the daemon ever support it) :upside_down_face:
https://github.com/lbryio/lbry-app/issues/664#issuecomment-335684392

Yes, we have this metadata in the search database, when chainquery is added this will be possible to do!

We can extend the search api so it resembles a more common example. Right now we only accept 1 parameter which is the search string.
We should have a set of arguments that are defined for advanced search capabilities. For example:

Channel or Claim or Playlist, etc
ClaimID ( there are some less known ways defined for the protocol  )
Active in claim trie
language
content type
By Publisher
controlling claims

Probably a lot more ways to search but we should be able to have a better api for this. Would love some feedback on an advanced search capability. Knowing what we need or expect will help in designing the best format for the api.

@tiger5226 I'm for providing this functionality, but the vast majority of users are going to be used to a single box where they type things and get what they want. I think it's important we prioritize this use-case over advanced searching which is more likely to be for power users.

agreed, not a priority right now

Ok all clear!
So then keeping the same search field for lighthouse we could enhance the field to allow for tags. This also allows the feature to be there before it is released in the app.
so if a user types contentType: followed by a word (or phrase in quotes ) it will create a tag in the app. that appears like contentType: files. This lets the user know they are searching only files with that tag. Below is an example of  tag system is OSX search.

Our tags based on current information in the elastic document are as follows:
controllingClaims: <boolean>
channels: <boolean>
Author: "<phrase>"
Language: <isocode>
ActiveClaim: <boolean>
contentType: <type>
Below is and example elastic document stored in elastic search:
{
  "name": "pok-mon-from-other-games-gabby-games",
  "claimId": "da73dabbc78e429254fec760d1dc97cc179b7878",
  "value": {
    "claimType": "streamType",
    "stream": {
      "metadata": {
        "preview": "",
        "license": "Copyrighted (contact author)",
        "licenseUrl": "",
        "thumbnail": "http:\/\/berk.ninja\/thumbnails\/nz7uDRZBKCo",
        "nsfw": false,
        "author": "Rerez",
        "description": "Nintendo needs new Pok\u00e9mon! Gabby is here to help!\nSubscribe to Rerez: https:\/\/goo.gl\/0qauGx\nBecome a Patron!: https:\/\/www.patreon.com\/rerez\nFollow Rerez on Twitter: https:\/\/twitter.com\/RerezTV\n\nCheck out Adam's work at: https:\/\/www.youtube.com\/user\/ItsaDogandGame\n\nRerez is a YouTube channel presented by Shane Luis all about video games. Presenting you the newest, strangest and most unique gaming topics. Featuring high quality reviews of new video games, consoles, previews, oddities, rare titles, unknown hardware, classic and retro games, and much more!\n\nCredits:\n...\nhttps:\/\/www.youtube.com\/watch?v=nz7uDRZBKCo",
        "language": "en",
        "title": "Pok\u00e9mon From Other Games! - Gabby Games - Rerez",
        "version": "_0_1_0"
      },
      "source": {
        "sourceType": "lbry_sd_hash",
        "source": "e427b1add5f93adcc21a6623c8664319cd9f2353bcf5499b32ca2d204c623d9f7014cf8c679bdb573c988e8e7a4bd983",
        "version": "_0_0_1",
        "contentType": "video\/mp4"
      },
      "version": "_0_0_1"
    },
    "publisherSignature": {
      "signature": "07c1825acf0a764a38ec92dc1c348d36eb9efc3126c821d452a80e0c75a13200923c7d8d91485e750e55577c826b8c22a5ef83ed136296ad2bcd039fd2b7af34",
      "certificateId": "6f36dfa66117b39500d6a74da38ddcb5a37301d8",
      "signatureType": "SECP256k1",
      "version": "_0_0_1"
    },
    "version": "_0_0_1"
  }
}

So what we do here is check if the first term in a search query is a keyword for a tag. If so we process it as such. If the next two characters is  " then we split the string to get phrases associated with the tag. The rest is the search query.
We can start off allowing 1 tag, then can extend to allow for n tags.
This should keep it independent of the apps features and allows it to be used straight away.

Would be possible to add read / add tags inside description?
My proposal would be to add the tags in the last line of the claim description:
This is a video a about cats!
Please support my chanel: <http://click.bait.com>
Tags: cat, funny, awesome  // <- HERE

Then we just need to read the last line:
ParseTags(description) -> [cat, funny, awesome]

We can also add a simple form to attach this last line for better (UX) inside the publish page:

@tiger5226 or @filipnyquist is this viable to pursue now that chainquery is integrated?

The most immediately useful filter would be filtering by file type.

A lot of @jamesbiller proposed maker community initiatives could really use the ability to filter by file types.
I split out this aspect of filtering into a separate ticket: #111

@tiger5226 or @filipnyquist is this viable to pursue now that chainquery is integrated?

I believe I missed this comment, but I don't think Chainquery is required here. This has been ready for a while, but it was put on the backburner a while ago because it was not urgent and seen as a power user feature. I like the idea to split out the file type stuff.

done


Error: Not Found

https://github.com/OpenRA/GeoIP-Database/runs/3653667430?check_suite_focus=true
Run cb80/pubrel@latest
Parsing the ref
Tag is: monthly
Setting up Octokit
Searching release by tag: monthly
Deleting release
Error: Not Found

It doesn't delete the existing release assets, but also doesn't really tell why.

Interesting. Step debugging may give you more information: https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging#enabling-step-debug-logging

##[debug]{"status":200,"url":"https://api.github.com/repos/OpenRA/GeoIP-Database/releases/tags/monthly","headers":{"access-control-allow-origin":"*","access-control-expose-headers":"ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, Deprecation, Sunset","cache-control":"private, max-age=60, s-maxage=60","connection":"close","content-encoding":"gzip","content-security-policy":"default-src 'none'","content-type":"application/json; charset=utf-8","date":"Mon, 20 Sep 2021 18:16:05 GMT","etag":"W/\"90efdf1e7fab8f3f45a4ca4f253d924924f924938f88666c2948ea948bafadc3\"","last-modified":"Mon, 20 Sep 2021 13:43:47 GMT","referrer-policy":"origin-when-cross-origin, strict-origin-when-cross-origin","server":"GitHub.com","strict-transport-security":"max-age=31536000; includeSubdomains; preload","transfer-encoding":"chunked","vary":"Accept, Authorization, Cookie, X-GitHub-OTP, Accept-Encoding, Accept, X-Requested-With","x-accepted-oauth-scopes":"repo","x-content-type-options":"nosniff","x-frame-options":"deny","x-github-media-type":"github.v3; format=json","x-github-request-id":"0402:616A:121735:132B25:6148CFE5","x-oauth-scopes":"repo, workflow","x-ratelimit-limit":"5000","x-ratelimit-remaining":"4999","x-ratelimit-reset":"1632165365","x-ratelimit-resource":"core","x-ratelimit-used":"1","x-xss-protection":"0"},"data":{"url":"https://api.github.com/repos/OpenRA/GeoIP-Database/releases/49852973","assets_url":"https://api.github.com/repos/OpenRA/GeoIP-Database/releases/49852973/assets","upload_url":"https://uploads.github.com/repos/OpenRA/GeoIP-Database/releases/49852973/assets{?name,label}","html_url":"https://github.com/OpenRA/GeoIP-Database/releases/tag/monthly","id":49852973,"author":{"login":"Mailaender","id":756669,"node_id":"MDQ6VXNlcjc1NjY2OQ==","avatar_url":"https://avatars.githubusercontent.com/u/756669?v=4","gravatar_id":"","url":"https://api.github.com/users/Mailaender","html_url":"https://github.com/Mailaender","followers_url":"https://api.github.com/users/Mailaender/followers","following_url":"https://api.github.com/users/Mailaender/following{/other_user}","gists_url":"https://api.github.com/users/Mailaender/gists{/gist_id}","starred_url":"https://api.github.com/users/Mailaender/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Mailaender/subscriptions","organizations_url":"https://api.github.com/users/Mailaender/orgs","repos_url":"https://api.github.com/users/Mailaender/repos","events_url":"https://api.github.com/users/Mailaender/events{/privacy}","received_events_url":"https://api.github.com/users/Mailaender/received_events","type":"User","site_admin":false},"node_id":"RE_kwDOEIr2d84C-LIt","tag_name":"monthly","target_commitish":"master","name":"IP2Location™ LITE IP-COUNTRY Database","draft":false,"prerelease":false,"created_at":"2021-09-20T13:16:15Z","published_at":"2021-09-20T13:18:52Z","assets":[{"url":"https://api.github.com/repos/OpenRA/GeoIP-Database/releases/assets/45201674","id":45201674,"node_id":"RA_kwDOEIr2d84CsbkK","name":"IP2LOCATION-LITE-DB1.IPV6.BIN.1.ZIP","label":null,"uploader":{"login":"Mailaender","id":756669,"node_id":"MDQ6VXNlcjc1NjY2OQ==","avatar_url":"https://avatars.githubusercontent.com/u/756669?v=4","gravatar_id":"","url":"https://api.github.com/users/Mailaender","html_url":"https://github.com/Mailaender","followers_url":"https://api.github.com/users/Mailaender/followers","following_url":"https://api.github.com/users/Mailaender/following{/other_user}","gists_url":"https://api.github.com/users/Mailaender/gists{/gist_id}","starred_url":"https://api.github.com/users/Mailaender/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Mailaender/subscriptions","organizations_url":"https://api.github.com/users/Mailaender/orgs","repos_url":"https://api.github.com/users/Mailaender/repos","events_url":"https://api.github.com/users/Mailaender/events{/privacy}","received_events_url":"https://api.github.com/users/Mailaender/received_events","type":"User","site_admin":false},"content_type":"application/zip","state":"uploaded","size":1744103,"download_count":0,"created_at":"2021-09-20T13:33:10Z","updated_at":"2021-09-20T13:33:12Z","browser_download_url":"https://github.com/OpenRA/GeoIP-Database/releases/download/monthly/IP2LOCATION-LITE-DB1.IPV6.BIN.1.ZIP"}],"tarball_url":"https://api.github.com/repos/OpenRA/GeoIP-Database/tarball/monthly","zipball_url":"https://api.github.com/repos/OpenRA/GeoIP-Database/zipball/monthly","body":"Mirrored from download.ip2location.com due to rate limits. This file is licensed under the Creative Commons Attribution-ShareAlike 4.0 International terms.\r\n\r\n\r\n"}}

This looks good. There is a valid id in that response which is used in https://github.com/cb80/pubrel/blob/main/src/main.ts#L48. Does your token have the repo scope?

With the latest release the log now also contains the release ID to be deleted (example at https://github.com/cb80/pubrel/runs/3679045489?check_suite_focus=true). Can you please trigger a new workflow with the default GitHub token?

https://github.com/OpenRA/GeoIP-Database/runs/3679699735?check_suite_focus=true

That workflow was still based on your GEOIP_TOKEN token right? Please remove line https://github.com/OpenRA/GeoIP-Database/blob/master/.github/workflows/geoip.yml#L24 that the workflow runs with the default token.

Now it works. Was this a configuration error on my end?

Looks like your token does not have the required permissions. That could mean that the owner/user of the token either does not have them, or the scope of the token restricts them, or both.

It was on the service user @orabot which used to work. I guess someone accidentally revoked access. I thought this was an API change and this action had to adapt to it. Sorry, if the error message were more conclusive, I wouldn't have bothered you. Thanks for the help!

Please star pubrel if you are happy with it.


[Enhancement] route_handler concept should include response return type

This is mostly for tracking
Currently the route_handler concept (which is used by router::add to constrain the callback type) only checks for invocable with the request and optionally the capture results. This is an incomplete definition as the type must also return a response<...> when invocked with said arguments.
The current lack of this additional requirement in the concept means that the user is presented with a rather obscure template error about void if their function does not have a return type (e.g. a default lambda) and which I spent a few minutes staring at before I realised the issue (bearing in mind I wrote that code in the first place :p).

Yeah... I ran into that problem too 🙈
I'm all pro extending the concept.

You wanna get this done for v0.1?

It shouldn't be too hard. I'll have a look tomorrow


Compare OFAC "Extended" and "Advanced" data formats

It looks like the US Treasury has birthed yet another SDN data format, this time called "Extended". So far, we're importing "Advanced". We should check if there is a) more data, or b) easier parsing to be had with the new format. The structure of the old one can only get simpler....

https://sanctionslist.ofac.treas.gov/Home/SdnList

Looks like "Advanced" is more advanced than "Extended", so we're doing ok.


Code available?

Hello. Thank you for your great work accepted on CVPR 2023.
When will you publicize the official code?
Thank you.

Thank you for your reminder. I have organized the code and uploaded it. Please feel free to review it. If you have any questions, don't hesitate to discuss them with me at any time.

Thank you for your code and kind reply.
I'll perform experiments based on your research and further discuss with you!
Thank you very much for your inspiring works.


finished the subaccounts endpoint

Done with tyhe subaccounts.

should be BodyParams instead of bodyParams
bodyParams: { required: ["business_name", "settlement_bank"], optional: [

check on this also @chepkok3

Checked and changed sir.
On Sun, Nov 20, 2022 at 9:45 AM Ezrqn Kemboi @.***>
wrote:

should be BodyParams instead of bodyParams
bodyParams: { required: ["business_name", "settlement_bank"], optional: [
check on this also @chepkok3 https://github.com/chepkok3
—
Reply to this email directly, view it on GitHub
https://github.com/momi-foundation-coding/paystack-gateway/pull/174#issuecomment-1321052991,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASWLWCHXHX62SQQXRO7P22LWJHCG5ANCNFSM6AAAAAASFVOWWU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Sure
On Sun, Nov 20, 2022 at 9:47 AM Nicholas Kipkoech Ngetich <
@.***> wrote:

@.**** requested changes on this pull request.
change from const root = "/subAccounts"; to const route = "/subAccounts";
—
Reply to this email directly, view it on GitHub
https://github.com/momi-foundation-coding/paystack-gateway/pull/174#pullrequestreview-1187215271,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASWLWCFNCGOWCISVS233AOTWJHCR5ANCNFSM6AAAAAASFVOWWU
.
You are receiving this because you were mentioned.Message ID:
@.***
.com>

I did but it seems it did not update. let me push again with some changes
made.
On Sun, Nov 20, 2022 at 9:52 AM Ezrqn Kemboi @.***>
wrote:

@.**** commented on this pull request.
In src/endpoints/subaccounts.js
https://github.com/momi-foundation-coding/paystack-gateway/pull/174#discussion_r1027235385
:

     "account_number",

     "active",

     "percentage_change",

     "description",

     "primary_contact_name",

     "primary_contact_email",

     "primary_contact_phone",

     "settlement_schedule",

     "metadata",

   ],

 },

},
},
+};

+export default subAccounts;
Also, rename this file to sub_accounts
—
Reply to this email directly, view it on GitHub
https://github.com/momi-foundation-coding/paystack-gateway/pull/174#discussion_r1027235385,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASWLWCCM3CYEGEPURB5VV5TWJHDDVANCNFSM6AAAAAASFVOWWU
.
You are receiving this because you were mentioned.Message ID:
@.***
.com>

also check the methods

Like which one specifically?
On Sun, Nov 20, 2022 at 10:04 AM Emmanuel Kipsang @.***>
wrote:

also check the methods
—
Reply to this email directly, view it on GitHub
https://github.com/momi-foundation-coding/paystack-gateway/pull/174#issuecomment-1321056133,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASWLWCGHG726HGIAHAU6TELWJHEQDANCNFSM6AAAAAASFVOWWU
.
You are receiving this because you were mentioned.Message ID:
@.***>

should be BodyParams instead of bodyParams
bodyParams: { required: ["business_name", "settlement_bank"], optional: [

No it should be in camel case

Okay
On Sun, Nov 20, 2022 at 10:14 AM Ezrqn Kemboi @.***>
wrote:

@.**** commented on this pull request.
In src/endpoints/sub_accounts.js
https://github.com/momi-foundation-coding/paystack-gateway/pull/174#discussion_r1027237629
:

   "metadata",

 ],

},
listSubAccounts: {

 route: route,

 method: "put",

 QueryParams: {

   required: ["perPage", "page"],

   optional: ["from", "to"],

 },

},
fetchSubAccount: {

 route: route + "/id",

 method: "get",

 PathParams: {

   required: ["id"],

this one should be id_or_code and not id
—
Reply to this email directly, view it on GitHub
https://github.com/momi-foundation-coding/paystack-gateway/pull/174#pullrequestreview-1187217738,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASWLWCEJZJKZ7QJC5SR6QE3WJHFT5ANCNFSM6AAAAAASFVOWWU
.
You are receiving this because you were mentioned.Message ID:
@.***
.com>

Awah si Nico amenishow ni change hivo
On Sun, Nov 20, 2022 at 10:15 AM Ezrqn Kemboi @.***>
wrote:

@.**** commented on this pull request.
In src/endpoints/sub_accounts.js
https://github.com/momi-foundation-coding/paystack-gateway/pull/174#discussion_r1027237684
:

@@ -0,0 +1,59 @@
+const roote = "/subAccounts";

+const subAccounts = {

createSubaccount: {
route: route,
method: "post",
BodyParams: {

bodyParams instead of BodyParams
—
Reply to this email directly, view it on GitHub
https://github.com/momi-foundation-coding/paystack-gateway/pull/174#pullrequestreview-1187217918,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASWLWCGVQOZ7CEHMBTUFZO3WJHFXLANCNFSM6AAAAAASFVOWWU
.
You are receiving this because you were mentioned.Message ID:
@.***
.com>


Bad Changeset - incorrect partition value but doesn't make sense

Goals

I'm trying to write to a realm and as part of my test am hard coding the partition value (a required field in my schema)
Expected Results

I expected to get a new record in Atlas.  Instead I get a new entry on the device but it is not syncing to Atlas
Actual Results

Error:
failed to validate upload changesets: SET instruction had incorrect partition value for key "partition" { expectedPartition: {team=BC21BE45-E402-4DC7-A85E-142DEAABDC19}, foundPartition: {team=BC21BE45-E402-4DC7-A85E-142DEAABDC19} } (ProtocolErrorCode=212)
Steps for others to Reproduce

Code Sample

func writeActivityData(locationName: String) {
        let teampartitionValue = "team=BC21BE45-E402-4DC7-A85E-142DEAABDC19"
        let user = app.currentUser!

        let activity = ActivityMessage()

        activity.text = locationName
        activity.partition = "{team=BC21BE45-E402-4DC7-A85E-142DEAABDC19}"
        activity.timestamp = Date()
        activity.points = 50

        Realm.asyncOpen(configuration: (user.configuration(partitionValue: teampartitionValue))) { [self] result in
        switch result {
                    case .failure(let error):
                        print("Failed to open realm: \(error.localizedDescription)")
                        // handle error
                    case .success(let realm):
                        print("writeActivivityData routine:  Successfully opened realm for useractivity: \(realm)")
                        // Use realm

                        try! realm.write {
                            realm.add(activity)

                        }

                        }
                    }
             }

Version of Realm and Tooling

Realm framework version: ?
Xcode version: ?
iOS/OSX version: ?
Dependency manager + version: ?

Looks like teampartitionValue is set to team=BC21BE45-E402-4DC7-A85E-142DEAABDC19 while activity.partition is {team=BC21BE45-E402-4DC7-A85E-142DEAABDC19} - i.e. the same, but with curly braces around it. You should either make them identical or just remove activity.partition from your model altogether and have the server populate it (if you don't set it, the server will automatically set to the partition of the Realm instance).

Regarding the log message - I agree it's confusing and we filed a ticket for the cloud team to fix the formatting. Closing this now, but feel free to reopen if you need more help.

Thanks @nirinchev I tried with and without the brackets based on the log message but this didn't make any difference.  I've now removed activity.partition but it now states
Error:
Ending session with error: failed to validate upload changesets: SET instruction had incorrect partition value for key "partition" { expectedPartition: {team=BC21BE45-E402-4DC7-A85E-142DEAABDC19}, foundPartition: } (ProtocolErrorCode=212)

Given I'm using partition for sync, the schema is forcing me to make partition a required field?

Regarding the brackets - can you confirm that if you modify your code to set activity.partition = teampartitionValue (i.e. ensure that they're identical), you get the same error? Also, remember to wipe your local state as it's possible that your simulator is still trying to upload the original changeset that contained the bracket mismatch.
Regarding removing activity.partition - you should be able to delete the field from your model - I'm guessing when you got the empty string error, you only removed the line which sets activity.partition = ... rather than the field altogether.

thanks @nirinchev setting activity.partition = teampartitionValue works.  Interesting given I had previously defined them by copy pasting the id into each!

Great - I'm glad to hear you've got it working now and we will most definitely address the confusing log messages!


Add algorithms for mathematical operations

As the title suggests, I propose to add a new folder named Mathematical_Algorithms(??). Is the '_' required? We should replace it with spaces instead. Also is appending Algorithms to the folder required?
We could name it simply 'Math' for readability. It can hold algorithms for finding/verifying primes, gcd, totient functions, zeta functions, partitions, multiplying matrices, finding eigenvalues/eigenvectors etc.

@GnikDroy Break this issue into multiple issues and raise PR for each algo/function


Refactor CSS to more look like the "Hub"

Hi there!
I did a complete CSS redesign (and a bit of HTML too) to match the Galaxy Hub look and feel. It is deployed here: http://williamdurand.fr/training-material/, so you can test it. Emoji (like :stuff:) are not rendered as I used gh-pages to build the website (neither Travis) but it is working.
I tried to come up with the smallest CSS possible (well, SASS actually but it is built-in in Jekyll). Therefore, all the credits go to Bootstrap. It is now fully responsive and should be slightly more readable. I changed the color scheme for the tutorial boxes with @bebatut and the help of http://paletton.com.
The PR gets pretty big, next chunk will be about replacing the Emoji icons in the "tutorial boxes" to FontAwesome icons, and then maybe redesign other parts. Let me know what you would like to do next!
🔥 Test it at: http://williamdurand.fr/training-material/

The logo (top left corner) will be updated, cf. #461.

Thanks @willdurand!
@galaxyproject/training can you please vote here if you think this is good to go and an improvement to the old style.

💯

For maintainibility, could we share a single set of base stylesheets between hub and here (and may end even Galaxy itself)?

For maintainibility, could we share a single set of base stylesheets between hub and here (and may end even Galaxy itself)?

The base stylesheet is Bootstrap I guess. See the main.scss file, it is very specific to the tutorials.

@jxtx That would probably mean bringing LESS to the build process to hub and here?

There is definitely stuff that is custom, but if we based it off the existing Galaxy styles then the bar sizes would match, fonts, base colors, etc.

(Also, I don't t care about less vs sass, we should just use one thing everywhere).

Yup, this can be done later anyway, especially if it involves Galaxy and Hub. The idea was to get rid of the old CSS and making the website a bit more appealing/responsive.

Fine with merging this now, but let's keep going!

Looks sleek! I noticed a couple of issues:

I found a few "500 Internal Server Error", e.g. http://williamdurand.fr/training-material/topics/assembly/
the "hat" logo is now used for "Hands-on", while previously a similar "hat" logo was used for "Slides", maybe that can be confusing?

@nsoranzo GitHub is having troubles again (for the 500)

the "hat" logo is now used for "Hands-on", while previously a similar "hat" logo was used for "Slides", maybe that can be confusing?

Yes. New logo for slides is the one from Slideshare, which seems to make more sense that the hat. Do you think we should switch back to the previous logos?

Yes. New logo for slides is the one from Slideshare, which seems to make more sense that the hat. Do you think we should switch back to the previous logos?

Don't know, mainly raising the point for discussion. Maybe a mouse logo for the tutorial?

This is a good point! Here are all the available icons: http://fontawesome.io/icons/ 😸

What about http://emojipedia.org/female-teacher/

I had that in mind too but read in #304 that FontAwesome should be preferred.

For training site we can afford to expand to other icon libraries I believe.

In the navbar, the emoji will look weird. I thought it would be better not having 2 different icons for same things and having icons in the navbar adds a visual hint

@willdurand What about http://fontawesome.io/icon/laptop/ for tutorials?

For getting the styles more uniform, all sites could start with this as a base: https://github.com/jxtx/galaxy-bootstrap
That's where the styles in Galaxy proper came from. It needs to be updated and packaged with all the modern stuff, but there it can produce a bootstrap.min.css with Galaxy styles ready to use.

Just replaced the navbar logo with a better one :)

ping @galaxyproject/training: we would like to have more feedbacks 😄

I like it! thanks a lot @willdurand :)

(rebased)

I think this was open long enough and I haven't heard any negative things - also counting the :+1: here is a clear merge this - and here we go!
Thanks @willdurand and all others for feedback. Keep the PRs coming!