Unrecognized artifact type: orbit

Jetty is using some sketchy artifact type called 'orbit' in it's dependencies.
These orbit files can't be resolved by ivyIDEA unfortunately.

What steps will reproduce the problem?
Try to resolve an orbit dependency:
<dependency org="org.eclipse.jetty.orbit" name="org.apache.jasper.glassfish"
rev="2.2.0.v201112011158" />

What is the expected output? What do you see instead?
Orbit files should be treated just as jar files but instead i get this message:
org.eclipse.jetty.orbit#org.apache.jasper.glassfish;2.2.2.v201112011158:    Unrecog
nized artifact type: orbit, will not add this as a dependency in IntelliJ.

What version of the product are you using? On what operating system?
Version 1.0.11

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 14 Aug 2015 at 7:26

Thanks a ton. worked for me as well. Just added the "orbit" as an acceptable artifact in IVYIdea settings.


Automate nix dependency hash update

Summary
Dependabot automatically updates Go module dependencies, but does not update the hash values of Nix configurations it derives from. This causes Nix build to be broken, and then a developer who find this have to manually update the hash value each time.
To prevent this, either find a way to automatically update the Nix hash, or prevent CI or lint from updating only the Go module dependencies without updating the Nix hash.
There seems to be a way to automate it using Renovate (using flake.nix).
https://docs.renovatebot.com/modules/manager/nix/
Any better ideas, or plans, etc.? I want to hear from all contributors.
Cases

https://github.com/argoproj/argo-workflows/pull/11504 → We'll wait for the automation for this instead of updating manually every time

https://github.com/argoproj/argo-workflows/pull/11180 → Update to the nix hash following dependabot update. ...

https://github.com/argoproj/argo-workflows/pull/11188 → ...

https://github.com/argoproj/argo-workflows/pull/11635#pullrequestreview-1585963785 → LGTM, we really need to do something about the dependency hashes needing constant updating.

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

cc @isubasinghe

I was thinking of writing a program to do this, but I estimate it to take about 24 hours of work in the best case scenario.
As a result I think the best solution is to move to renovate, even without the support for Nix, it seems to be a better tool in general.
@tico24 could help us here, I think he's done a dependabot to renovate transition before.

@terrytangyuan what are your opinions on installing renovate?

Do we need org level app installation or can we use its GitHub Actions? https://github.com/renovatebot/github-action

Is there a way to only use renovate to update Nix and keep dependabot for everything else?

Yes. You control exactly what renovate does and doesn't monitor.

I've installed renovate app in this repo. Would anyone like to help setting this up for Nix update only?

Someone at Pipekit will take this on. You can put me down if you need to assign to someone.

This was not completed. See discussions in https://github.com/argoproj/argo-workflows/pull/11887#issuecomment-1741644512


Fix typos

@ironsmile , I guess you could squash && merge instead of using a normal merge because I made multiple commits and with the the squash && merge the history will look better.

Why disregard terminal punctuation?

#fullStopsMatter

#saveTheFullStops


@extract_* and @subdag should work together

Is your feature request related to a problem? Please describe.
When you use @extract_* on top of a subdag decorator it breaks. This is because they're both NodeExpanders, which don't support layering.
Describe the solution you'd like
NodeExpanders should be able to use the target decorator to enable layering. Furthermore, for subdags that only product one output (they currently all do), this should just work.

We are moving repositories! Please see the new version of this issue at https://github.com/DAGWorks-Inc/hamilton/issues/72. Also, please give us a star/update any of your internal links.
Note that everything else (slack community, pypi packages, etc...) will not change at all.


CSV output should be returning missing attributes

Describe the bug
I've downloaded a sample of SIDA's participating organisations from the Query Builder in CSV format.
It happens that all have a name and a role, but only some have an @ref and an @type
In the CSV output there's no way to tell which participating org the @refs or @types belong to
For example:

What would be helpful is to add commas for each non reported attribute. Allowing the user to know which attributes belongs to which participating organisation.
For example:

To Reproduce
Steps to reproduce the behaviour:

Go to 'https://iatidatastore.iatistandard.org/search/activity?q=(activity_date_start_actual_f:[2018-01-01T00:00:00Z TO ] OR (-activity_date_start_actual_f:[ TO ]            AND activity_date_start_planned_f:[2018-01-01T00:00:00Z TO ])) AND (activity_date_start_actual_f:[ TO 2019-12-31T00:00:00Z] OR (-activity_date_start_actual_f:[ TO ]            AND activity_date_start_planned_f:[ TO 2019-12-31T00:00:00Z]))&fl=participating_org_*&wt=csv&rows=2500'
Import data into Excel or other platform
Scroll down to example where participating org role doesn't match the number of types.
See error

Expected behaviour
Expect to see comma separated attributes in each column, displaying the number of 'expected' attributes. Rather than just those present

Additional context
I'd expect to see this functionality across all elements and attributes. Presume the same occurs for other elements and their expected attribtues.

Agree @amy-silcock nice find 👍

@siemvaessen as per @amy-silcock's OP, please can you ensure that all other elements are checked for containing the same error within their attributes.

cc @HeleneBourgoin

sure, I will check it

This work is not complete.
For example, look at participating-org refs in UNDP's activity: XM-DAC-41114-OUTPUT-00110174
Or download: https://test-datastore.iatistandard.org/search/activity-sector?q=reporting_org_ref:(XM-DAC-41114) AND recipient_country_code:(NG)&wt=xslt&tr=activity-sector-csv.xsl&rows=10
And see errors in the participating org columns

@amy-silcock  This will not include in this release. Full reparse/reindex is needed to reflect this fix.

@luminhan  do let me know once full reparse is done and I will check again :) Same for #2401 as they are related.

@petyaKangalova test url: https://test-datastore.iatistandard.org/search/activity/?q=iati_identifier:"SE-0-SE-6-10526A0101-KEN-15220"&wt=xslt&tr=activity-csv.xsl. In the screenshot you will see extra comma for misssing attributes.

Thanks @luminhan ! I tested the activity you shared and also did another test with a different activity from that the same file just to verify and all looks good! Issue can be closed!
https://test-datastore.iatistandard.org/search/activity/?q=iati_identifier:"SE-0-SE-6-10579A0101-KEN-31140"&wt=xslt&tr=activity-csv.xsl


Boilerplate: Update to 4e8e5f0dd9b4d95321872aaab701b21e59cee673

Conventions:

openshift/golang-osd-operator: Update
openshift/golang-osd-operator-osde2e: No change ---
https://github.com/openshift/boilerplate/compare/b5fef8ffb9b790d2d886bf522161a205f9ef043f...4e8e5f0dd9b4d95321872aaab701b21e59cee673

commit: f80d7d3b22e0055de63d550c1d32a16c25b20fdb
author: Michael Shen
Revert using containerized skopeo
We would need to mount the docker/podman sockets as a file mount for this to truly work and instead performed a workaround on the Jenkins VMs.
Signed-off-by: Michael Shen<EMAIL_ADDRESS>commit: 70f4f3e41146868b5ca0d52b917ccfea09fac5f8
author: Michael Shen
Limit controller-runtime to v0.17.2 for Go 1.21 support
Signed-off-by: Michael Shen<EMAIL_ADDRESS>commit: d11572e7fe85fd5c236d430c2d047ddf5b3869c3
author: Michael Shen
Update push steps to use containerized skopeo
Signed-off-by: Michael Shen<EMAIL_ADDRESS>commit: 5e86a99159abf0f428e9568e624cf1fc3bc9280e
author: Brady Pratt
golang-osd-operator: use new path to TEMPLATE_FILE
this file will not exist in most repositories yet, it will need to be added during the migration process
Signed-off-by: Brady Pratt<EMAIL_ADDRESS>commit: aad1f1f7fab42ece64fc88aa3ff61244c60bb09b
author: Michael Shen
Update docs link for location for openshift/release mirroring
Signed-off-by: Michael Shen<EMAIL_ADDRESS>commit: 802e445d71269d6222c876625cbfa62e60ace952
author: Ritu Mundhe
Update golangci lint version
commit: f67d44013d4bc051df8819624eb300d6cc16974b
author: Kirk Bater
Update OWNERS_ALIASES
Removes Team v1a.
commit: e5b6c598d3b71a2701ec663a8556f63f009187b0
author: Claudio Busse
Dockerfile.appsre: fix ci image name from build farm
commit: c0f1454be240aeadda950719868a17a95c756cf4
author: Claudio Busse
Use existing container engine instead of podman
commit: ce86987696a5bddc54dd9cbbb7720ed74927374a
author: typeid
Fix build push (#335)

Fix build-push script for boilerplate to build latest tag if it doesn't exist

Validate returned output of inspect and checkout tag

commit: 532a19ca42db4d73f6c51a8b9b779bbd7ec4ecb6
author: Chris Collins
Replaces egrep with grep -E due to deprecation
egrep is being deprecated in favor of grep
-e, and now throws warnings about the deprecation when being used.
This PR replaces egrep with grep -E, which should be a drop in replacement, handle the deprecation when it happens, and suppress the warnings that are printed every time we run the make command with boilerplate.
Signed-off-by: Chris Collins<EMAIL_ADDRESS>commit: 7752da0184b22a32162f29676f2fbe67f8b49d81
author: Claudio Busse
Empty commit to re-tag image-v5.0.0
commit: 70f2f2d539355d6ea52979d1a1cfaff58f8b2b71
author: Antony Natale
updates fl list, adds new fedramp team sre's
commit: 31a961f645f450eca0d738df2c2a701e1b356c02
author: Michael Shen
Leaver process - bdmiller3
Signed-off-by: Michael Shen<EMAIL_ADDRESS>commit: d80ca839f04fb651dfa070558ded1fa18c466577
author: Claudio Busse
Add Benson as TL and Nico as FL
commit: 26cc7d3aef3fc8ed1edd0fde32d61b78608557c6
author: Claudio Busse
Create boilerplate v5.0.0 to support Go 1.21
commit: d033aef49e14b4ddd74ecbe505e3399c9b4625bc
author: Brady Pratt
golang-osd-operator: bundle rvmo
Signed-off-by: Brady Pratt<EMAIL_ADDRESS>commit: 84ef94271c76e2b576fd612294746eace8a54865
author: Chris Collins
Subscribe compliance-audit-router (CAR) to boilerplate
Adds openshift/compliance-audit-router (CAR) to the boilerplate subscribers.yaml, with the osd-container-image convention.
Signed-off-by: Chris Collins<EMAIL_ADDRESS>commit: bd72354b8bbe2f9c67fc0b1f73fa1390fc5c3c67
author: Sam Nguyen
Update Team Security members
What type of PR is this?
(bug/feature/cleanup/documentation/test/refactor)
What this PR does / why we need it?
Which Jira/Github issue(s) this PR fixes?
Fixes #
Special notes for your reviewer:
Pre-checks (if applicable):

[ ] Tested latest changes against a cluster
[ ] Ran make generate command locally to validate code changes
[ ] Included documentation changes with PR

make container-generate

can likely fix the test issues.   I am having trouble running that in MacOS podman.


Apotheosis causes all items to have an effect

After checking, Apotheosis will cause all items to have render effects and particles and sound effects
latest.log

Seems to be fixed, so close


posix: sched: Implement sched_setparam() and sched_setscheduler()

From the pull request : https://github.com/zephyrproject-rtos/zephyr/pull/67028
Resolves : https://github.com/zephyrproject-rtos/zephyr/issues/66963
resolves : https://github.com/zephyrproject-rtos/zephyr/issues/66962

@moonlight83340 why you duplicate #67028 ?

@moonlight83340 why you duplicate #67028 ?

Sorry I wanted to continue with your work for base (That why it's a draft).

@moonlight83340 why you duplicate #67028 ?

Sorry I wanted to continue with your work for base (That why it's a draft).

then could you rename it and give some description ? just to avoid confusion

@moonlight83340 why you duplicate #67028 ?

Sorry I wanted to continue with your work for base (That why it's a draft).

then could you rename it and give some description ? just to avoid confusion

Okay, I will do that, thank you

@moonlight83340 why you duplicate #67028 ?

Sorry I wanted to continue with your work for base (That why it's a draft).

then could you rename it and give some description ? just to avoid confusion

Seems okay for you ?
The title was already different, I had description and that I take my start from your PR.


Option to use a tab instead of a pane?

This is looking very good.  As a heavy magit user (and then Sublime Git) I was thinking of writing this myself.
Is there any way to get an option to use a full tab instead of a pane?  Particularly after using emacs for so many years it seems really strange.
Great job.

Having this in it's own tab - or the option to open diffs in their own tabs, really, would be a big improvement. Viewing difs in the pane is very cramped - or you have to keep yo-yoing the width of the pane all the time.

Vote for tab https://github.com/diiq/atomatigit/issues/105 +1


Feature/Issue 687 Upgrade Expo including @types modules

@ian-lin-PG this'll need to be rebased to resolve conflicts. @tomy-pg I'm wondering if you can ensure that the build process for IPAs and APKs is still working as expected?

@bensinjin I can test this to ensure that it is working

@bensinjin currently the build process to generate the APK and IPA is not working.

Closing this as we're addressing it in another PR.


Optional SSL server session cache

Optionally enable server-only session caching with SSL_CTX_set_session_cache_mode if the binary is invoked with flag -z/--enable-ssl-session-cache. Useful for clients that support TLS session resumption (immediate use case is mcrouter).

nice, thanks! Will take a look soon. Have you tested TLS tickets at all?

Thanks! I've only tested session ID based resumption for now in an end-to-end environment with mcrouter as the client. Seems like supporting ticket based resumption is a bit more complicated, and in truth I'm probably not familiar enough with OpenSSL APIs to implement it here.

Based on https://www.openssl.org/docs/man1.0.2/man3/SSL_CTX_set_session_id_context.html,
If the session id context is not set on an SSL/TLS server and client certificates are used, stored sessions will not be reused  . So we also need to set SSL_CTX_set_session_id_context

I'm a bit busy to validate this right now, might be another week or two. Super bonus points to anyone who adds tests + fixes the context issue :) I'm pretty sure I've written TLS resumption tests ten years ago but my own mind's full of cobwebs.

I had some time to take a closer look at this, seems like this is actually a noop change in behavior since server-side session cache is already enabled by default. I confirmed this with a call to SSL_CTX_get_session_cache_mode, and documentation confirms this as well:

The default mode is SSL_SESS_CACHE_SERVER.

So there might not actually be too much value in merging this change. We could offer the ability to explicitly disable the session cache if desired, if you think there is value in providing such an option.
I've been able to verify session resumption behavior with the openssl binary itself and checking output for new and reused sessions, though I'm not sure how you feel about a unit test invoking a binary and screen-scraping the output for assertions.
$ openssl s_client -key t/client_key.pem -cert t/client_crt.pem -CAfile t/cacert.pem -connect localhost:11211 -no_ticket -sess_out /tmp/sess
$ openssl s_client -key t/client_key.pem -cert t/client_crt.pem -CAfile t/cacert.pem -connect localhost:11211 -no_ticket -sess_in /tmp/sess

@LINKIWI thanks for catching this. I checked my notes on the initial implementation, the goal was not to enable session resumption by default (I wasn't sure about vulnerabilities and how to invalidate sessions with automatic cert refresh without flushing them all), but looks like I missed it.
I propose to disable the session resumption by default and keep this changeset to enable if needed.

Thanks @tharanga. Sounds reasonable to me, I've updated this patch to explicitly set SSL_SESS_CACHE_OFF by default but otherwise set SSL_SESS_CACHE_SERVER (OpenSSL default) when the option is passed.

@LINKIWI LGTM. re: unit tests, looks like you can use IO::Socket::SSL->new(.. with SSL_session_cache created from IO::Socket::SSL::Session_Cache->new with SSL_session_key. More details are here : http://manpages.ubuntu.com/manpages/trusty/man3/IO::Socket::SSL.3pm.html

This looks better, but I still want some tests before merging it. Would one of you folks mind doing that soon? :) I'm about to do a lot of work in memcached.c which would cause a conflict.

Sure, I'll try to get something up for tests in the next few days. Thanks!

I've spent some time with this, but unfortunately I'm not familiar with Perl so I would appreciate some help on the necessary modifications to lib/MemcachedTest.pm. In particular, it seems like new_sock is decoupled from the initial $conn = ... so I'm not sure of the best way to set a global Session_Cache object that can be shared among all invocations.
My proposal for the actual unit test is something like this, which basically just makes sure total number of TCP connections goes up but new SSL sessions is unchanged (this takes advantage of a new gauge ssl_new_sessions introduced by this PR):
my $server;
my $sock;
my $stats;

$server = new_memcached();
$stats = mem_stats($server->sock);
is($stats->{ssl_new_sessions}, undef, "new SSL sessions not recorded when session cache is disabled");

$server = new_memcached("-o ssl_session_cache");
$stats = mem_stats($server->sock);
my $initial_ssl_sessions = $stats->{ssl_new_sessions};
my $initial_total_conns = $stats->{total_connections};
$stats = mem_stats($server->new_sock);
cmp_ok($stats->{total_connections}, '>', $initial_total_conns, "new connection is established");
is($stats->{ssl_new_sessions}, $initial_ssl_sessions, "SSL session is reused");

Added ssl_session_resumption.t. I have no experience with Perl so please let me know if needs additional work. Thanks @tharanga @dormando
$ SSL_TEST=1 perl t/ssl_session_resumption.t
ok 1 - new SSL sessions not recorded when session cache is disabled
ok 2 - client-side session cache is noop in establishing a new connection
ok 3 - client-side session cache is unused
Signal handled: Interrupt.
ok 4 - initial connection is established
ok 5 - successful new SSL session
ok 6 - new connection is established
ok 7 - no new SSL sessions are created on the server
ok 8 - client-persisted session is reused
1..8
Signal handled: Interrupt.

Thanks! will look as soon as I can. For an added bonus; please base branches off of 'next' (and target merge to 'next'). I tried to fix the defaults a few weeks ago but failed, sorry. I fixed a lot of flaky tests in the next branch.

Changed base pointer to next. Thanks
This change actually conflicts with #627 since both PRs add a new TLS stat; if we plan to merge both it might make more sense to merge #627 first and I can resolve the conflict + add a line to doc/protocol.txt in this PR after rebasing.

@LINKIWI test looks good to me as that counter is a direct function of whether session cache enabled or not. You have to install a newer version of libio-socket-ssl-perl or disable tests that are checking the client side session caching as get_session_reused is only available in newer versions of IO-Socket-SSL.

that makes sense. I think @tharanga's checking the counter PR shortly, then I'll finalize and merge if we all agree on it.

think we'll miss 1.6.1 on this (too much stuff queued, few things to fix/review here still) but it'll hit next soon.

Hm, I'm seeing different behavior between OpenSSL 1.1.0 (CI environment) and OpenSSL 1.1.1 (my local environment). I'll dig deeper this week.

Thanks for putting the work in! I'll check in on this too. what's the difference you're seeing?

Thanks! Seems like the combination of OpenSSL 1.1.0 + latest IO::Socket::SSL properly reports that the session is reused on the client side, but doesn't increment ssl_new_sessions on the server (i.e., the new session callback isn't called). However, when testing manually with openssl s_client, I can see the server-side stat incremented properly.
The combination of OpenSSL 1.1.1 + latest IO::Socket::SSL behaves as I expect, per the unit test (ssl_new_sessions is incremented on the server, and client-side reports that the session is reused). It also continues to behave correctly with openssl s_client.
There's a possibility that OpenSSL 1.1.1 introduces some bug fixes around this. Though seeing as session resumption seems to work fine in both versions, one option forward is to skip the assertion ssl_new_sessions > 0 in the unit test.

That's strange. Latest IO::Socket::SSL shouldn't impact the memcached, it should continue to use OpenSSL 1.1.0, where that callback is used.
Do you need those client side checks? I believe we can rely on the server session count for the correctness.

The client-side check is not strictly necessary, but the issue is that the server-side session count seems to only be incremented properly under OpenSSL 1.1.1. See for example the test failure here: https://travis-ci.com/github/memcached/memcached/builds/153608008

So it seems like the behavior is actually different between OpenSSL 1.1.0 and 1.1.1.
1.1.0: https://github.com/openssl/openssl/blob/b2758a2292aceda93e9f44c219b94fe21bb9a650/ssl/ssl_lib.c#L2977
1.1.1: https://github.com/openssl/openssl/blob/8658feddea6aef5cf5cbb1cfbf6b1817fa432051/ssl/ssl_lib.c#L3641
From what I gather, 1.1.1 always invokes the callback (see inlined comment in the source above) while 1.1.0 only invokes it if external session cache storage is enabled (SSL_SESS_CACHE_NO_INTERNAL_STORE) or internal caching failed.
Given this, I'd like to propose skip the server-side counter assertion in the unit test (assert ssl_new_sessions > 0 after handshake) and adding a note in the docs that the counter will only be incremented for new sessions in OpenSSL versions 1.1.1 and above. We can consider re-enabling the assertion if we upgrade the base CI image to Bionic or upgrade OpenSSL. Any thoughts on this?

sorry I've been so slow to poke at this :(

I bumped travis to bionic to simplify this a bit (and cut several minutes off the build/test run time...).
Think I'm out of complaints. Do you want to rebase/squash this down or should I do this for you?

Great! I believe Bionic ships with OpenSSL 1.1.1 already so I think I can remove the skipped tests now and the extra Perl installation in .travis.yml as well. I'll rebase against next and make those changes.

You should keep the skipped test unless you want to add version detection in there; as users may be on older versions, the test would become spurious.

Rebased against next. I reverted all my changes to .travis.yml from this branch. Let me know if you have any remaining concerns

released in 1.6.3 (I did a squash down for you)


fix: types for common functions

Description
see #7731
Checklist:

[x] Securely signed commits
[x] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

Rebased.


Fix link for haddock documentation in README

Description

Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[ ] When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
versioning process.
[ ] The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
[ ] All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
[x] Code is formatted with fourmolu (use scripts/fourmolize.sh)
[x] Cabal files are formatted (use scripts/cabal-format.sh)
[x] hie.yaml has been updated (use scripts/gen-hie.sh)
[ ] Self-reviewed the diff

Nope :)
Current approach is future proof and having a custom domain is nicer :wink:


Arcbox SQL Automation

Added automation to allow onboarding of SQL server for 2 different scenarios:

If the Service Principal only has "Contributor" on the target Resource Group, then an icon will be created on the desktop to allow the use to onboard the SQL server post ArcBox deployment. This method will use the login credentials of the actual user, so they themselves will need Microsoft.Authorization/write (Owner/User Access Administrator/Custom Role) on the target Resource Group so that permissions can be modified during the onboarding process.

If the Service Principal has Microsoft.Authorization/write on the target Resource Group, the SQL server will automatically be onboarded during the ArcBox deployment, and an assessment will be run.

NOTES: I likely need to include the SQL assessment code for scenario #1, but lets get this tested for now and that can easily be added (and I'll be actively working on this)

@DCMattyG Can you also please include updates to the READMEs (for full and ITPro) explaining how this works. Right now the READMEs still say that we need UAA on the SPN.

ArcSQL.ps1 should also be renamed to something more descriptive. ArcSQLAutomatedOnboarding.ps1 or something similar.

@dkirby-ms, I'll work on the suggested changes above including the corrected screenshots today.


oo

Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Please run down the following list and make sure you've tried the usual "quick fixes":

Search the issues already opened: https://github.com/googleapis/python-bigquery-dataframes/issues
Search StackOverflow: https://stackoverflow.com/questions/tagged/google-cloud-platform+python

If you are still having issues, please be sure to include as much information as possible:
Environment details

OS type and version:
Python version: python --version
pip version: pip --version
bigframes version: pip show bigframes

import sys
import bigframes
import google.cloud.bigquery
import ibis
import pandas
import pyarrow
import sqlglot

print(f"Python: {sys.version}")
print(f"bigframes=={bigframes.__version__}")
print(f"google-cloud-bigquery=={google.cloud.bigquery.__version__}")
print(f"ibis=={ibis.__version__}")
print(f"pandas=={pandas.__version__}")
print(f"pyarrow=={pyarrow.__version__}")
print(f"sqlglot=={sqlglot.__version__}")

Steps to reproduce

?
?

Code example
# example

Stack trace
# example

Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!

Hi @evanpenner1 , if you meant to report a real issue please update title and description and reopen


Thanks for rppal, showcase of our app using it, and question

Didn't know where to post this - so ended up using an issue. Sorry if no tthe best way.

Thanks for creating rppal. I've used in a couple of pi projects now and enjoying it.

New project of ours that uses it:

Two of us started a small project called “pigg” to learn more rust, Iced GUI and GPIO programming on the Pi with rppal.
The result is a first release (v0.1.0) that includes the “piggui” (“piggy” to friends) Iced GUI.

It runs on macOS/Linux/Windows hosts (mainly for dev for now, until we get remote GPIO implemented) and more importantly on a Raspberry Pi.
We hope this seems interesting, and potentially useful, especially when developed further. We’d love to hear your thoughts here, in GH issues or in GH discussions
Repo: https://github.com/andrewdavidmackenzie/pigg
Release Notes: https://github.com/andrewdavidmackenzie/pigg/releases/tag/0.1.0
crates.io entry: https://crates.io/crates/pigg
GH Issues: https://github.com/andrewdavidmackenzie/pigg/issues
GH Discussions: https://github.com/andrewdavidmackenzie/pigg/discussions
Release Discussion Thread: https://github.com/andrewdavidmackenzie/pigg/discussions/122

We have doubts about correct pin definitions, and what things are hardware and what sw. based on reading pi docs, rppal docs, pinout.xyz

I have listed the pins and doubts in this github issue:
https://github.com/andrewdavidmackenzie/pigg/issues/102
If there is any Pi expert here who can shed some light on the matter it would be much appreciated!

That's a nice UI and interesting project you have there! I'll have to play around with it.
As for the alternate function definitions, you'll probably want to use a different set for each set of Pis that shares the same SoC family. I'd go with the definitions as specified in the datasheets. So far I've avoided the issue by using generic Alt0-Alt8 names, but I should probably consider adding the actual function names at some point as well. Also remember the Pi 5 has 3 additional Alt functions compared to previous models, and a pin's function can technically be NULL on the Pi 5 as well.

Thanks!
And we hope "that's only the beginning"...
If you have suggestions please share them in issues or discussions.
I guess I'll have to slog through all the data sheets and compile per
device?
Your docs references to 3 I2C channels through us off...
Have you had any requests related to HATs?
On Mon, Jun 3, 2024, 5:19 PM Rene van der Meer @.***>
wrote:

That's a nice UI and interesting project you have there! I'll have to play
around with it.
As for the alternate function definitions, you'll probably want to use a
different set for each set of Pis that shares the same SoC family. I'd go
with the definitions as specified in the datasheets. So far I've avoided
the issue by using generic Alt0-Alt8 names, but I should probably
consider adding the actual function names at some point as well. Also
remember the Pi 5 has 3 additional Alt functions compared to previous
models, and a pin's function can technically be NULL on the Pi 5 as well.
—
Reply to this email directly, view it on GitHub
https://github.com/golemparts/rppal/issues/148#issuecomment-2145490634,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKF4LFJM7S7NRT43SVJVFTZFSCQNAVCNFSM6AAAAABIWVJAD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBVGQ4TANRTGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

I was thinking. There is the python pigpio library, that can be run as the pigpiod daemon on the Pi, to effectively export it's functionalities over the network.
I was wondering if you'd thought about doing something similar with rppal?
We want to make the functionality available over the network, to a remote GUI.
pigpiod seems to focus on making it available to python libraries running on a macos/linux/window machine.
We are very happy using rppal, and having it available as a system-service on a Pi, accessible from a remote UI would be perfect.
Others could focus on "remote rppal" library and remote rust, or remote scripts if they wanted.

I haven't had any HAT-related requests, but RPPAL is only meant to support the base peripherals, so adding support for HATs seems more appropriate as a separate project.
Similarly, providing remote access doesn't really fit the scope I have in mind for RPPAL. I've considered it, but I think a separate project that uses RPPAL internally would be a better fit. I don't have any current plans on developing one though, so if you're up for it you're more than welcome to!

Ok, that's clear. Thanks.
Pigpiod is a separate small project that creates a daemon out of the lib.
Something along those lines. "Piglet" may evolve into something along those
lines. If you want to, just follow the project and we'll see out it evolves.
Thanks again!
On Wed, Jun 5, 2024, 3:57 PM Rene van der Meer @.***>
wrote:

I haven't had any HAT-related requests, but RPPAL is only meant to support
the base peripherals, so adding support for HATs seems more appropriate as
a separate project.
Similarly, providing remote access doesn't really fit the scope I have in
mind for RPPAL. I've considered it, but I think a separate project that
uses RPPAL internally would be a better fit. I don't have any current plans
on developing one though, so if you're up for it you're more than welcome
to!
—
Reply to this email directly, view it on GitHub
https://github.com/golemparts/rppal/issues/148#issuecomment-2150046391,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKF4LERGMBAX6PB7WGN5GLZF4KLRAVCNFSM6AAAAABIWVJAD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJQGA2DMMZZGE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Use ContactsMixin for Assets

Currently, an asset can only be assigned to one contact. In practice, however, an asset may have more than one contact, i.e. someone who is responsible for an asset and multiple users who have access to it. Thus, a contact-asset relationship can also have multiple types.
Therefore I ask to switch to the use of ContactsMixin, which has a consistent contact assignment as for the NetBox core models. This mixin class is not part of the official NetBox plugin API, but is already used in this plugin anyway, so there seems to be no overhead for maintenance.
NOTE: This feature request will result in an API breaking change, as an existing field will be removed. Also, it can't be migrated automatically, as required fields for contact mapping are currently missing and can't be determined automatically.

I agree this  would make sense.
For migration I suppose we could create a ContactRole called something like InventoryAssetMigrated and use it for all existing asset contacts. Users can then go and rename this role or use bulk edit to assign a different one. Also role creation should only happen if any assets have contacts assigned at time of migration so we don't pollute ContactRoles if not needed...
Another breaking change is CSV import of assets. Currently import of assets can assign a contact as well (contact 	— 	name 	Contact using this asset. It must exist before import.). Also API will change.

Therefore I ask to switch to the use of ContactsMixin, which has a consistent contact assignment as for the NetBox core models.

I had the same thought during the development of #185 . Add a tab with contacts, and handle contacts via assignment, will be the same user experience as other NetBox core parts.


Numeric array and matrix spec

In an rspec, document minimum expectations for the following:

1D array
2D array
vector
matrix
data frame

Lean toward current GSL syntax.
John Prince began the spec: https://github.com/SciRuby/sciruby/blob/generic_numeric_array/spec/sciruby/nvector_spec.rb
However, we first need to decide on a unified interface for matrices and vectors. For example, should 2D arrays be matrices? Should all arrays and matrices be fundamentally the same type?
See the following threads:

Musings on matrices
Google+ posting

All dense vectors are 1D arrays, but not all 1D arrays are dense vectors. I think the same would apply to 2D arrays and matrices.

Current idea:
Have all matrix types be the same class (e.g., Matrix). Each has an internal data structure, storage, which can be changed using to_csc!, to_lil!, etc. These storage types may or may not inherit from one another, but can be swapped out and converted fairly easily. All should probably have a common base class that dictates interface, e.g., BasicStorage. Further, users can add new storage types (e.g., UpperTriangularWeirdStorage) without breaking calls to m.is_a?(Matrix) in other people's code.
DenseStorage will be what the current Ruby core Matrix would use in our implementation.
We'd also want, at a minimum, CSCStorage.
All SciRuby basic matrix storage types need to have working C extensions, and it'd be great if they worked with JRuby too. See clbustos' distribution gem for an idea of how to optionally use existing libraries, if you've never done this before.

Update: I've been talking with marcandre about modifying Ruby's stdlib Matrix to include sparse storage. He seems interested.

A lot of the expectations are listed here: https://github.com/princelab/narray/wiki

Maybe matrix should by default be created in dense storage and it should keep track of amount of non-zeroes. Whenever it is reasonable (for example it takes less memory), Matrix will change to some basic sparse storage (may it be CSR). Matrix in every storage should answer to the same methods, it will enable writing methods (for example linear equations) just once for every storage.
Another question i have. Why exactly we need 1d arrays AND vector? Whats the difference? Same thing with matrices and 2d arrays.

@KillaPL --
This inline optimization is something which might be set up as an option, e.g., pass :auto as the matrix storage type (stype). But it's sort of frowned upon by most programmers. One reason is the trade-offs in speed and storage between different stypes; and secondarily, that you want people using your library to be conscious of what trade-offs they are causing to be made.
Fundamentally, how would you initialize such a matrix? Let's say you're building it from a file, one cell at a time. Does it reach some threshold and then freeze your program while it transforms to a dense matrix from a CSR? What happens if your matrix is already taking up greater than half of available memory? Does it then crash as it tries to convert stypes?
The vector v. 1D array question is reasonable. I think of a vector as being like a slice of a matrix, and something that participates in matrix math (e.g., X=Mv), but an array as something that does not. But I need to think about it some more. Maybe @jtprince can weigh in.

I'm trying to decide out how to set up matrix constructors -- e.g., required versus optional arguments.
So far I have a dense matrix and a LIL matrix (list of lists). I plan on implementing a compressed sparse row (CSR) matrix as well. All use row-order currently (any need for column order that anyone can see?).
I want to be able to create a matrix with a call to NMatrix.new(type, ...), where type is :dense or :list or :hash or :compressed, etc. So at a minimum, that argument should be required (unless we initialize as NMatrix.dense, etc).
The next mandatory argument should probably be the shape of the matrix. If a list is given, ([3,2,3]), it produces a matrix of rank 3 with shape 3x2x3. If a number is given, say 4, it'll assume a square matrix of rank 2 (shape 4x4).
The third argument is where we start to have choices. At some point we need to know our dtype (int32, int64, complex64, etc). If we provide an initialization value or some array to reshape into the matrix contents, we can guess a dtype.
For example, init value of 0 suggests a dtype of int16, int32, int64; but 0.0 suggests a dtype of float32 or float64. It'll pick whichever is the default for the Ruby class in question -- e.g., for 0 the Fixnum, my MacBook Air uses 8 bytes, so int64.
Similarly, one could provide [1,0,0,0,1,0,0,0,1] to set a 3x3 matrix as the identity matrix. What happens, though, if the user only enters [0,1,2,3] for this argument? We could do it like R, where it just repeats the default until the matrix is full (e.g., [0,1,2,3] becomes [0,1,2; 3,0,1; 2,3,0]). But that could potentially lead to errors.
If the third argument is an initial value, the fourth argument would be an optional dtype -- so we don't have to guess from the third arg.
As an alternative, the third argument could simply be the dtype: NMatrix.new(:dense, 3, :int8). We would then assume a default value of 0, which is usually safe -- or 0.0 if it's float32, and so on.
What happens if the user doesn't want to provide a default value or a dtype?
Probably the best of all worlds here is to allow the following constructions:
NMatrix.new stype, shape, initial, dtype
NMatrix.new stype, shape, initial
NMatrix.new stype, shape, dtype

The vector v. 1D array question is reasonable. I think of a vector as
being like a slice of a matrix, and something that participates in matrix
math (e.g., X=Mv), but an array as something that does not. But I need to
think about it some more. Maybe @jtprince can weigh in.

Maybe this will be helpful as you think about it:
narray and numpy both treat the underlying data structures exactly the same
for numeric arrays and matrix/vectors.  This makes sense since the data is
the same, just a difference in the behavior of addition, multiplication,
and division signs (e.g., dot product vs. element-wise multiplication)
In numpy there is only a multidimensional array (that may be 1D).
Matrix/vector behavior is done through different method calls (although
they also have a distinct matrix class):
so, '*' gives elementwise multiplication ( resulting in another array ),
while 'dot' gives the dot product
In NArray, NVector and NMatrix are subclasses of an NArray.  The subclass
overrides the behavior of +,-,*,/
I like the numpy thinking on this.  Make vector or matrix math available
but under different names, like 'dot'.  That way, you can do matrix math if
you need to, but also elementwise arithmetic.  Then, if you really need it,
you can use the real matrix class which treats the operators like a matrix
would.
--John

I'm trying to decide out how to set up matrix constructors -- e.g.,
required versus optional arguments.

Here are my thoughts:
My feeling would be that the implementation detail should go last.  Here
are the two invocations that make sense to me:
NMatrix.new shape, initial, dtype=:float64, stype=:dense
NMatrix.new shape, dtype, stype
These are disambiguated because the initial value will always be a number
(or perhaps an Array) but the dtype will always be a symbol.
If you want to get a different stype without specifying the other things
(as you suggest):
NMatrix.dense( shape )  etc.
Default initial type should be a float64, IMHO.  The float part is easy: it
is the default type for GSL arrays, matlab, and R, I believe.  Just makes
sense as a default numeric value for scientific computation (integers are a
special case, really).  As for float64 or float32: it should be float64
because you can't easily implement anything else in pure ruby.
As for a default initial value:
The original NArray always defaulted to 0 (or 0.0 or whatever).  This is
predictable, but it is slow if you are going to immediately replace the
values with something else.
NArray redesign defaults to whatever random values happen to be at those
memory spots.  Numpy also follows this convention.
The point is, if you don't specify the value you must have a good reason
for not specifying it (i.e., you want to fill it in immediately with
something else).  So, the default value is some unpredictable random number.
Of course, if the implementation is in pure ruby you have to choose a
default value.  In this case, you default to 0, but the user should not
depend on this because it may not be 0 if it is implemented in C.
NMatrix[] is the operator for passing in an array that is immediately
converted (using the highest type found in the array).  This is slow
because the array has to be traversed to find the highest type, but it is
very convenient for just throwing in a bunch of rows:
NMatrix[ [1,2,3], [4,5,6], [7,8,9], [10,11,12] ]
->
[1,2,3]
[4,5,6]
[7,8,9]
[10,11,12]
Yes, should be row first for indexing:, so nmatrix[2,0] accesses the 7
above (follows numpy and NArray rewrite and matlab).

Just saw these, a bit too late, mostly.
NMatrix.new stype, shape, initial, dtype
NMatrix.new stype, shape, initial
NMatrix.new stype, shape, dtype

all work, but you can also leave out stype if you want :dense. It'll be dense by default.
Matrix creation from an array is not yet in there. I need to figure out a way to not specify an initial value for the dense matrix contents, wherein it's still consistent with the list matrix (which basically has to have a default type).
Anyway, it's really simple so far. If you want to play with it, it's github: mohawkjohn/nmatrix
You'll have to do:
cd src/
ruby extconf.rb
make
cd ..
rake # runs tests

Have a look in the spec to see what it does so far.
Goals were dtypes and stypes. Only list and dense are implemented, want to do at least CSR. Most dtypes are implemented, but I haven't tested complex or rational yet -- only float and fixnum.
Feel free to contribute to the spec, too. =)


Events: Create sample test data

See title.
Resolves #799.

oh what the heck did flyhe formatter get removed at some point?


[feat] Include @inherits in the content of Page auto-generation

Motivation
You can create one template element and then inherit and use it around to omit some of the canned declarations.
However, in this case, each page must include @inherits Template.
It would be useful to include this template in auto-generation.
Required Features

Function to specify the entire page at once BlazorPath(PageTemplate = typeof(Template)).
Function to Opt-out if necessary Page<Component>(Inherits = null)
Ability to override as needed Page<Component>(Inherits = typeof(AnotherTemplate))

I will post it here as well.
I noticed this when I was actually testing it.
If you don't add @inherit to the razor file, it seems that it inherits ComponentBase by default instead of losing the inheritance source.
So if you inherit another class in a different file, you will get an error.
I close this issue here because it is impossible to template without changing the mechanism on the razor side.
Translated with DeepL.com (free version)


Is this project still maintained?

I'd like to organise an event but I can see several PRs from many months ago that haven't been merged?

Same issue here, is there anybody alive @ tictail? :smile: I mean, I know you merged with Shopify, but since this has become a global event, colud anybody keep this repo alive?
Or just switch ownership to someone who will

Seems a shame doesn't it! A lot of people loved this concept... :(

Hi, we're sorry for leaving this repo unattended for a while. As @sickDevelopers mentioned, we've merged with Shopify so we have had our focus occupied by other things for a while. I'm happy however to say that we do plan to keep this project alive again now!
If you have any upcoming events, please submit a PR and we'll happily have them merged into the website.


update documentation for cosmos client

Packages impacted by this PR
@azure/cosmos
Issues associated with this PR
Describe the problem that is addressed by this PR
This PR updates the example in documentation for connection policy and cosmos client.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.

/azp run js - cosmosdb - ci

/azp run js-cosmosdb-ci

/azp run js - cosmosdb - ci


[BUG]: drizzle-zod Attempted import error: 'is' is not exported from 'drizzle-orm'

What version of drizzle-orm are you using?
0.26.5
What version of drizzle-kit are you using?
0.18.1
Describe the Bug
drizzle-zod (0.4.4) expects is to be exported from drizzle-orm but it is not. Temporary workaround is to downgrade drizzle-orm to 0.26.3 and drizzle-zod to 0.4.2.
Expected behavior
No response
Environment & setup
No response

Upgrading to drizzle-orm 0.27.0 fixed the issue.


NPCGUI

Just cant put Gui on NPC, done like in the wiki, and the console is not showing any issue dont kwon why its appening.
Server is runnig paper 1.14.4 can be that the reason??

Closing as OP did not follow issue template (missing Quests version, example quest).
Sent with GitHawk


pivot table relation

Laravel Version:  5.4.9
Voyager Version: latest
PHP Version: 7.1.8
Database Driver & Version: MySQL 5.7

Description:
I've read through the documentation and played with voyager for a few days and it seems at the moment the only way to get a pivot belongsToMany relation to show up on the edit page is to create an empty database column with the exact same name as the pivot relation?
Will this always be the case? as this is not very good practice and can cause issues with existing projects and seeders.
Steps To Reproduce:

👍  I'm wondering about this too. This pollutes the database schema :/

@michaelmano
does your multiselect dropdown function?  can you share your config.  I can't my option items to populate the option value attribute.

Here's mine:
I have an entity  named "Route" which has a relation to multiple "Location" entities via a pivot table.
This is the voyager BREAD json config:
{
    "relationship": {
        "key": "id",
        "label": "title",
        "page_slug": "admin/locations"
    }
}

Route.php:
public function locations() {
  return $this->belongsToMany(Location::class);
}

This works, but only because I added a column named "locations" in the route table, which is quite confusing. If I don't have the column, I could not figure out how to configure BREAD for this property.
Since it is stated explicitly in the docs, I assume that this is the current way to do it:

Simply enough, inside of the pages BREAD we would choose a Multiple Select as the input type for a categories row (this row can be any type) and include the following Optional Details as we did above:

See https://laravelvoyager.com/docs/0.11/#core-concepts-bread-relationships

And you have a pivot table route_locations?

@johnmain
Actually it's called location_route:

Name of the pivot table should consist of singular names of both tables, separated by undescore symbole and these names should be arranged in alphabetical order, so we have to have product_shop, not shop_product.

See: http://laraveldaily.com/pivot-tables-and-many-to-many-relationships/
Though I don't know if that's important ...
Here's the Schema for the pivot table:
<?php

use Illuminate\Support\Facades\Schema;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;

class LocationRoutePivotTable extends Migration
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
      Schema::create('location_route', function(Blueprint $table)
      {
          $table->integer('location_id')->unsigned()->index();
          $table->foreign('location_id')->references('id')->on('locations')->onDelete('cascade');
          $table->integer('route_id')->unsigned()->index();
          $table->foreign('route_id')->references('id')->on('routes')->onDelete('cascade');
      });
    }

    /**
     * Reverse the migrations.
     *
     * @return void
     */
    public function down()
    {
        Schema::dropIfExists('location_route');
    }
}

Ahh yeah.  that fixed my issue.  I think it was my Pivot table config.  I used your migration and I now have ids in my options.
Thanks

Ok, after some fiddling I found a workaround:

The table data_rows in the database holds the information about the BREAD config.
It is sufficient to add a row, the forms will work

For BREAD editing:
It seems like the author has intended to add fields beyond existing columns in the db:
DataType.php gathers information about the entitie's database table definition/schema in a method called fieldOptions(). The result is a multidimensional array which is iterated through in vendor/tcg/voyager/resources/views/tools/database/edit-add-bread.blade.php to setup the BREAD config table.
There is a method named extraFields() in DataType.php, which checks the model for the existance of a method called adminFields().
I implemented adminFields() in my model class to return a twodimensional array holding some fake values:
class Route extends Model
{

...

  public function adminFields() {
    $fieldOptions = array();
    $fieldOptions['agenda']['type'] = 'relation'; // <- I've choosen an arbitrary name
    $fieldOptions['agenda']['default'] = null;
    $fieldOptions['agenda']['notnull'] = 1;
    $fieldOptions['agenda']['columnDefinition'] = null;
    $fieldOptions['agenda']['comment'] = null;
    $fieldOptions['agenda']['name'] = 'location';
    $fieldOptions['agenda']['oldName'] = 'location';
    $fieldOptions['agenda']['null'] = 'NO';
    $fieldOptions['agenda']['extra'] = null;
    $fieldOptions['agenda']['composite'] = 0;
    $fieldOptions['agenda']['field'] = 'location';
    $fieldOptions['agenda']['key'] = null;

    // $fieldOptions['id']['length'] = null;
    // $fieldOptions['id']['precision'] = 0;
    // $fieldOptions['id']['scale'] = 0;
    // $fieldOptions['id']['fixed'] = 0;
    // $fieldOptions['id']['unsigned'] = 0;
    // $fieldOptions['id']['autoincrement'] = 0;

    return $fieldOptions;
  }

I don't know which are necessary, but the ones I did not comment out seemed reasonable to me.
This basically would work, but unfortunately there is a cast to object in Voyager's fieldOptions method in DataType.php, which renders my array useless in the blade rendering template, which is throwing an exception trying to acces an object like an array. If i remove the cast everything works as expected and the BREAD config is showing my extra field 👍
This would be a tiny patch, but I don't forsee the consequences removing the cast since I don't know the intentions of the adminFields() method. Any hints from the author?

Yeah I'm in love with this project and can't wait for it to mature a bit more. Going to take a look through it more and see if I can contribute in any way.

Labels: possible bug

This is no longer an issue now that 1.0 has been released with a complete rewrite of how relationships are handled


Json.fromValues rename to Json.fromIterable to Json.fromCollection

What do you think to make a rename of this method? I think it would be better to understand that this fromIterable wraps into json array instead of fromValues...

I don't understand the contrast you're suggesting with Json.fromValues? JsonObject.fromIterable is a semi-internal method (as the "provided for optimization" suggests) that's really just for cases where the more general fromFoldable (or just apply) have too much overhead.


[Accordion] Open/Close Event is chaining when option multi-expand is set

Hey guys,
i found a strage behaviour in the accordion component of foundation:
Open/Close Event is chaining when option multi-expand is set.
The problem is, that events are chained and beeing fired with a delay on heavily abusing the left click button on an accordion tab. This behaviour is in foundation a long long time, but i wanted to report it now. Multiple users of our websites have reportet this behaviour and i think its a pure improvment on stability and userbility of the component.
How to reproduce this bug:

Go to http://foundation.zurb.com/sites/docs/accordion.html#advanced-options
Click as fast as you can on Tab "Accordion 1"
Move cursor away and see the Accordion open/close several times without clicking.

What should happen:
Expected behaviour would be, that you click on a tab to open it, all other click events are disabled until the animation is finished. Then you can start the close event for that tab.
What happened instead:
All events are chaining and beeing fired late
Browser(s) and Device(s) tested on:
Firefox 54.0.x
Chrome 59.0.x
Foundation Version(s) you are using:
Foundation 6.4.1
Test case link:
http://foundation.zurb.com/sites/docs/accordion.html#advanced-options

This is because of missing debouncing and triggering multiple animations.

https://github.com/foundation/foundation-sites/blob/develop/js/foundation.accordion.js#L141
https://github.com/foundation/foundation-sites/blob/develop/js/foundation.accordion.js#L176
https://github.com/foundation/foundation-sites/blob/develop/js/foundation.accordion.js#L204
https://github.com/foundation/foundation-sites/blob/develop/js/foundation.accordion.js#L211
https://github.com/foundation/foundation-sites/blob/develop/js/foundation.accordion.js#L277


fix httpserver header all match

Codecov Report

Merging #699 (25d5244) into main (0132848) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #699   +/-   ##
=======================================
  Coverage   80.06%   80.07%
=======================================
  Files          93       93
  Lines       10100    10100
=======================================
+ Hits         8087     8088    +1
+ Misses       1538     1536    -2
- Partials      475      476    +1

Impacted Files
Coverage Δ

pkg/object/httpserver/mux.go
87.58% <100.00%> (+2.10%)
:arrow_up:

pkg/filters/headerlookup/headerlookup.go
84.61% <0.00%> (-1.40%)
:arrow_down:

pkg/filters/validator/basicauth.go
77.41% <0.00%> (-1.39%)
:arrow_down:

pkg/cluster/cluster.go
59.57% <0.00%> (-0.53%)
:arrow_down:

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 0132848...25d5244. Read the comment docs.


Orientation information

Thanks for the great dataset!
I am working on a project where I require the orientation of the ground vehicle in addition to the panorama image. Since the panoramas are north-aligned, have you considered additionally publishing the vehicle's bearing per frame?

Thank you for your interest in this dataset. I do have the original unaligned orientation which may be the street direction (not sure), but it may take some time for me to get the data extracted and organized. You can give me your email so that I can share a sample with you to see if this is what you want.


Advertised information is missing

[Enter feedback here]
The 'parent' page (https://learn.microsoft.com/en-us/visualstudio/ide/user-permissions-and-visual-studio?view=vs-2022) has a link that says you can find out how to run the debugger in VS2022 with elevated privileges. When I click the link and go to the 'child' page (https://learn.microsoft.com/en-us/visualstudio/debugger/debugger-settings-and-preparation?view=vs-2022), I can't see anything about that.
Also, this document is for VS2022 but I searched for VS2017 information. I know this is a Google failing but thought you ought to know. It might be useful to include a link to the VS2017 information, assuming it can be done in VS2017.

Patrick

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

ID: 0974e6c8-6131-25f5-5837-411ba0d4c1e0
Version Independent ID: d6c8c133-53b7-984a-cbc1-d5bf2baa1fcf
Content: Debugger Settings and Preparation - Visual Studio (Windows)
Content Source: docs/debugger/debugger-settings-and-preparation.md
Product: visual-studio-windows
Technology: vs-ide-debug
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@PatrickRyder -- Patrick, thank you for your feedback.  Please consider these resources, if you haven't already:

Ask a question or find an answer on the Microsoft Q&A page for Visual Studio.
Check the Visual Studio MSDN Forum.
Stack Overflow
Reddit

@Mikejo5000 -- Mike, please look into this issue.

@PatrickRyder Thanks for the feedback! I checked some old versions of this page back to 2008 and none of talk about running the debugger with elevated privileges. We do have a remote debugger topic that provides related guidance:
https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugging-errors-and-troubleshooting?view=vs-2022
BTW, the VS 2017 version of the page is here:
https://learn.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2017/debugger/debugger-settings-and-preparation?view=vs-2017
I'll update the link.

There are also a few other scenarios that require running VS as an administrator to debug, such as Debuggin on a local IIS server.
The parent page, https://learn.microsoft.com/en-us/visualstudio/ide/user-permissions-and-visual-studio?view=vs-2022, is really only saying that you need to run VS as administrator when debugging an app with elevated privileges. There isn't really a good link to use here, since the parent page has already said what needs to be said, as far as I can tell. I'm closing this for now, but let me know if there is some specific information you need that is missing.


Implement last value printing

We should implement the printing of the last value. The corresponding code is currently commented here, because unlike cling, clang-repl's process_code does not return the counterpart of a cling Value, which should be the case.

Let's cc @junaire who is actively working on this item to land in LLVM.


Cache busting

This is in relation to #222
adds something like &cachebuster=1633729203 onto the query parameters in order to defeat browser caching and force the document to be re-downloaded from the LRS server.
I used the same kind of pattern that the since parameter uses with the spread operator and ternary expression.
Only implemented on getActivityProfile(s) since that's the only place where I have run into a need for it, though it might arguably apply to something like the agent profiles as well, or really anything that requestResource is called for, but I'm reluctant to go changing the signature of every single function.  Maybe it could be something that you configure on the xapi obect rather than passing it in to the function calls.
Anyhow, this is just a first pass to illustrate the idea, and is sufficient for my use case.

The approach looks good, I agree that it could be configured elsewhere - not 100% sure yet. Any request that uses the GET method could benefit from this in theory.
Additional testing will need to be done against a few different LRS (e2e tests on this are currently configured for SCORM Cloud and Veracity) to ensure that an unexpected query string parameter will still result in a successful request as its not part of the xAPI specification. It's good to know that this approach works ok on Cornerstone. If you have any experiences of using this approach on other LRS that would be beneficial.
I will soon be releasing v2.0.0 of this library (https://github.com/xapijs/xapi/pull/215) which includes a full API change on the public methods. So instead of having several parameters, there will be a single object of parameters. I am thinking this object would be a good place to have a cache busting flag (default false), which all get requests could utilise.

Great to hear! After giving it some time to mull it over, by having it as an optional parameter on each of the request params its going to be a caveat per LRS whether the cache busting feature is supported or not.
I've done the majority of the structural refactors of the https://github.com/xapijs/xapi/pull/215 branch, and will be looking to publish a pre-release to test the new changes out via npm without doing a full release soon. Would it be a big ask for you to create a PR against that branch instead of the current master? I'm very keen to ensure your contributions are respected, but I am not sure if it would be very clean to add this into the v1.x format. If so, we could look to get this functionality included as part of the v2 release 😃
I'm thinking:

[ ] Create a generic interface for all get-based resource params e.g. GetParamsBase which only contains the useCacheBuster flag (this could live in the src/resources folder
[ ] Ensure all get-based resource param interfaces extend this base interface so they all have it as an option
[ ] Create a generic internal method for generating the cache buster string
[ ] Use the existing approach of the ternary expression and spread operator to optionally include the cache buster property on to each of the get-based resource methods (more of what you've already done in this PR)

Alternatively, if you don't have the time to get all/some of this done (I understand its not going to be a quick job!) I'm happy to pick this up and finish it off.

I don't have a lot of time to devote to it at the moment, since I have sort of been on a tangent of a tangent of a tangent already here, but I quickly whipped up a separate PR that I'll send you shortly with the same changes.  I haven't had a chance to really test it on that branch though.

Merged #224, closing this PR.


[<FIREBASE_PRODUCT>]

FCM is not showing in real device as well as simulator after updating flutter version to V1.12.13 hotfix 9 but it's coming to device and printing fcm message on android studio console

Hi @ziasultan2
Please upgrade to (Channel stable, v1.17.2 and firebase_messaging: ^6.0.16
After upgrade Can you please provide your flutter doctor -v, your flutter run --verbose and a minimal complete reproducible code sample.
Thank you


radosstriper

would it make sense to include the radosstriper api?
i'm a bit confused about the multiple incompatible ways ceph stores things, so i'm hoping at least rados_stripe is compatible with rgw?

Could you link to an example of this API please?  Either code or docs would be suitable.
Also, I'm not clear what you mean by "multiple incompatible ways". Do you mean like rbd vs. cephfs vs. rgw?

there's no docs, so i have no idea how it works either. I spotted it when trying to figure out how to access rgw objects without going through the AWS api, which requires a SeekReader.
https://github.com/ceph/ceph/blob/master/src/include/radosstriper/libradosstriper.h

Do you mean like rbd vs. cephfs vs. rgw?

yeah, it's confusing why they're all different implementations on top of rados objects. I'm not sure if radosstriper uses the same object format as rbd or rgw.

there's no docs, so i have no idea how it works either. I spotted it when trying to figure out how to access rgw objects without going through the AWS api, which requires a SeekReader.
https://github.com/ceph/ceph/blob/master/src/include/radosstriper/libradosstriper.h

Thanks. It certainly appears that this is designed to help build striped objects on top of rados, but I don't see much that uses it. There are very few PRs I see that refer to it by name. @tchaikov might know a bit more about it as one of the last people to make changes to those files.

Do you mean like rbd vs. cephfs vs. rgw?

yeah, it's confusing why they're all different implementations on top of rados objects. I'm not sure if radosstriper uses the same object format as rbd or rgw.

They're all trying to meet the needs of different use cases while using rados as a common layer. If they didn't use rados each one would need to (re)invent it's own back end storage [1]. The cephfs subsystem implements posix file system semantics where rgw is an http object store. I've not been involved with ceph a very long time so I'm probably not the best to explain this though. If you're interesting on delving deeper into this topic I suggest emailing the ceph list.
I'm skeptical that the rgw layer uses radosstriper because very few PRs in ceph seem to reference it. ceph is a very active repo so I'd assume I'd see more if it was a component of a hot topic like rgw. But I only looked for a couple of minutes so take what I say here with a grain of salt.
[1] - There are both upsides and downsides to this I'm sure, but that's how ceph does it. :-)

PR #1015 adds a rados/striper package. AFAIK the C radosstriper package is not used by either RGW, RBD, or CephFS but is similar to it. Either way you can now use (some) radosstriper  APIs via go-ceph and therefore I think it's safe to close this issue.


Uncaught (in promise) TypeError: this.pendingRequest.dispose is not a function

With 0.3.0-alpha.8 version this bug just appear. If I click on a Link while a query is running, I got this error:
Uncaught (in promise) TypeError: this.pendingRequest.dispose is not a function
    at QuerySubscription.dispose (http://localhost:3000/static/js/bundle.js:14996:27)
    at http://localhost:3000/static/js/bundle.js:15411:27
    at Array.forEach (<anonymous>)
    at Resolver.updateQuerySubscriptions (http://localhost:3000/static/js/bundle.js:15409:33)
    at Resolver._callee$ (http://localhost:3000/static/js/bundle.js:15291:41)
    at tryCatch (http://localhost:3000/static/js/bundle.js:5403:40)
...

oops

Fix released in v0.3.0-alpha.9.


Enable automatic updates to default blocklist

This is setup as a GHA workflow which is to run daily (schedule currently disabled) and invokes a shell script which runs the Elixir updater script itself, which automatically updates the dependency locks and the changelog upon there being any changes.
Upon that happening, a branch is pushed and a PR is opened.
All that's likely missing is setting up additional permissions in the repo settings.

I'm not sure there's a need for automatic sync, since this will probably require some major code changes (in addition to blocklist changes). Blocklist updates will cause ID changes, so we'll have to carefully introduce this. As of now, no blocklist changes are scheduled.

That makes sense, I got ahead of myself. But no problem, the automation bits were for the most part copied from another lib I maintain.


Add development history visualization post and cleanup GH-Pages code

This fixes a few odds and ends on the Github Pages site and adds a new post with a visualization I was playing with and thought others might want to see too. The video itself is stored in LFS so it shouldn't hurt the size of the repo and could potentially be updated from time to time.

Ug. It doesn't look like GH Pages supports the Jekyll plugin system. Let me look into that.

Humbug. I guess Github doesn't want people being able to run arbitrary Ruby code on their servers. Because sand-boxing is hard. Oh well.

Is it worth splitting this up into doable chunks?

Yes probably. I should make the temp dir stuff less specific to my dev machine too.

Wait, my last comment was on the wrong PR. What do you mean my "doable chunks"? I can rebase to factor out the attempt at using a Jekyll plugin if that's what you mean. It works on local Jekyll instances but not on GHP. If that's not what you mean then I'm confused.

I found another issue with the code (accidentally deleted line of markup) so I went ahead and rebased this and stripped the plugin attempt while I was in there.

Better hold off merging this for a sec, I setup GH-Pages to test build from my fork and it looks like LFS isn't serving up  the video  file as expected. Standby for tweaks.

There this link arrangement should work both for local Jekyll for testing, on anybody's fork (e.g. mine) on Github¹, and of course from the master GH Pages site.
¹ After you merge this—the video tag reference to the media file will not work from forks until the LFS stuff is in your repo.

Should I expect this:

The page build completed successfully, but returned the following warning:
You are attempting to use the 'pygments' highlighter, which is currently unsupported on GitHub Pages. Your site will use 'rouge' for highlighting instead. To suppress this warning, change the 'highlighter' value to 'rouge' in your '_config.yml'. For more information, see https://help.github.com/articles/page-build-failed-config-file-error/#fixing-highlighting-errors.

@simoncozens We aren't actually using the syntax highlighter at all yet, but we probably will so we might as well specify one Github allows.


rcS: move check for PWM input up

pwm_input was not working correctly (only after a pwm_input reset) on
Pixracer because fmu was started on all PWM output channels.
This moves the check if PWM input is needed up before the fmu start.
Tested on Pixracer and Pixhawk (for both it's FMU port 5).

Travis test this please.


Turn compact preset into an app theme

Starting from V15, "compact" no longer needs to be a "preset". Turn it into an application theme similarly to what "dark" is currently.

Compact should be a style sheet that can be included into any style scope.
I would not adopt the exact same solution which is currently used for the dark palette, where you need to import the whole lumo-color module and then use an additional theme="dark" attribute.
Instead, compact could be a simple style sheet (much like it is now), which sets the values of certain custom properties.
I suppose it could be achieved with something like this:
compact.css.js
export const props = `
  --lumo-size-xl: 3rem;
  --lumo-size-l: 2.5rem;
  --lumo-size-m: 2rem;
  ...
`;

Then you would use it like this:
import compactProps from 'compact.css.js';

...
      static get styles() {
        return css`
          .some-thing-that-should-be-compact {
            ${compactProps}
          }
        `;
      }

In addition to that we could still offer a convenience global style sheet which you can easily import in your app.

Related: #14


autosize bug?

The text cannot be automatically resized when it is set
TableCell Name="Cell6" Border.Lines="All" Border.Color="Silver" Text="深蓝色简约大气风格双肩包"

In another case, it's OK
TableCell Name="Cell6" Border.Lines="All" Border.Color="Silver" Text="这是内容啊啊啊啊啊啊啊啊啊啊啊"

I guess the width of the content word is set as a positive multiple of the width, so there is no problem？
How can I display all the words？

Have you tried this with full version (FastReport.Net Demo is enough)? It works well on my Win7 PC.


wish you hadn't changed the export setup and added this confusing subpackage thing

also, what happened to paramcase?
still though, thanks for your work.

What’s the confusing sub package thing? If you’re referring to the monorepo, I agree, it made more sense when it was a dozen separate packages.
You can read the release notes here: https://github.com/blakeembrey/change-case/releases/tag/change-case%405.0.0


Content-Type missing in responses triggered by interceptors returning Status

Bug Report
Services guarded by interceptors that return Err(Status::*) for any reason are missing Content-Type headers in the responses when queried with grpcurl.
Version
Tested on the main v0.6.1 release and the latest master branch
Platform
Linux plopear 5.14.16-arch1-1 x86_64 GNU/Linux
Crates
tonic
Description
TL;DR: Err(Status::*) responses are handled differently when they occur in Interceptors versus methods, leading grpcurl to complain that the content-type header is missing in Interceptor-generated responses.
Similar to #431, #700, and #759, but creating a new issue since this appears to be a broader case than a specific example not working (or represents a regression to the fix applied in #701).
I've created a repro of the issue here. This repro lets you configure different FAILURE_MODEs through environment variables: None means that there is no failure, Method means that the configured methods return a Status, and Interceptor means that the interceptor returns a Status. I'd expect Method and Interceptor failure modes to generate the exact same response, but they do not. Listed below are the tests I've run on each relevant failure mode.
Failure Mode: Method
Run command (in repro repo): RUST_LOG=info FAILURE_MODE=method cargo run
Query command: grpcurl -plaintext -import-path ./proto -proto health.proto [::]:50051 grpc.health.v1.Health/Check
Query response:
ERROR:
  Code: Internal
  Message: Failure within the Check method

Failure Mode: Interceptor
Run command (in repro repo): RUST_LOG=info FAILURE_MODE=interceptor cargo run
Query command: grpcurl -plaintext -import-path ./proto -proto health.proto [::]:50051 grpc.health.v1.Health/Check
Query response:
ERROR:
  Code: Unknown
  Message: OK: HTTP status code 200; transport: missing content-type field

The first is behaving as expected, the second is not.
Next Steps:
I'll do a bit more digging to see how these requests are different, and I suspect that a fix like #701 will be in order. But want to make sure that this is floated as a possible regression on all interceptors, rather than those used in a particular example.

Following up on this: it appears that by the time wrapped service responses are mapped at this line, Method failure modes include content-type headers of application/grpc and Interceptor failure modes include the message payload, but not the content-type. Going to do a bit more digging to determine where that content-type header might be getting dropped (assuming it's generated properly in the first place), but that difference is enough to qualify this as a bug within tonic, I think, rather than a bug with grpcurl's implementation.


Extension causes high cpu load

Issue Type: Performance
Extension Name: bracket-pair-colorizer-2
Extension Version: 0.0.28
OS Version: Darwin x64 18.5.0
VSCode version: 1.32.3

https://gist.githubusercontent.com/carloscarvallo/b35cbb76043e76de9a0d84895a1de18a/raw/587e5a994e637379e20984efe90ff71201910c37/CoenraadS.bracket-pair-colorizer-2-unresponsive.cpuprofile.txt
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Duplicate of #55. Please close this and post there instead.
@carloscarvallo


Visual mode fix and replace mode

Fixes cursor at the start of line when entering visual mode.
Adds replace mode detection with ModeChanged autocmd.

Sorry for the delay. It seems I haven't been getting notifications for this repo! And I haven't used it in quite some time.
Thanks for your contributions, I will get the new version uploaded to the package registry asap

Didn't think this would get merged, glad you like it.
For navigating the different modes this extension worked very well for me, thanks!
I don't notice any large delays - but I don't expect good performance from writing to the config and re-rendering UI Elements.
What worked best for me is only changing the color of the cursor with editorCursor.foreground.

I don't have that many public projects that other people collaborate on and I think the notifications must of got lost in a sea of dependabot messages.
Agreed, it's a very hacky way of getting something like this done, but I liked the feature in VSCode Vim and had no idea how to go about this.
I only noticed the lag on the status bar and it makes more sense for the cursor to be the default option as your eyes are already there.  I will give it a go and maybe update the README so it's the recommended config.
Thanks again for contributing!

Interestingly if I load the config in lua as is via
vim.api.nvim_exec([[
...config
]])

I don't get the delay at all 🎉
But I do get a vscode-neovim error 😥
2023-03-23T19:17:36.795Z BufferManager: nvim_win_set_cursor: Cursor position outside buffer

Will have a play around with this and if I make any ground I will make a new release.

I actually use the vimscript config and load it in my init.lua like this
prefix = os.getenv("HOME") .. '/.config/nvim' vim.cmd('source ' .. vim.fn.expand(prefix) .. '/theme.vim')
not sure if that changes anything.
But maybe it's useful for someone.


Default tweet string is wrong

Steps:

Create collective
Go to Admin > Connected Accounts
Connect Twitter
Click on "Settings"
See invalid tweet message:

Seems like we're not using internationalization properly there.

Also happens with all host tweets


AMD externals fail silently if libraryTarget is not 'amd'

Bug report
What is the current behavior?
External dependencies that are only available via AMD are only supported if the output libraryTarget is also 'amd'. This is rather surprising, and not at all documented.
If the current behavior is a bug, please provide the steps to reproduce.
Using this Webpack config:
module.exports = {
  mode: 'none',
  externals: {
    'amd-module': { amd: 'amd-module' }
  }
}

Transpiling the code require('amd-module') results in a dependency like this being included in the output:
/* 1 */
/***/ (function(module, exports) {

module.exports = undefined;

/***/ })

What is the expected behavior?
Given any AMD dependency and no libraryTarget, I would expect one of the following outcomes:

The output is surrounded by a require(...) or requirejs(...) wrapper, much as is done already with define(...) when libraryTarget: 'amd' is set.
A build-time error is shown about the unresolved dependency, as is already done if libraryTarget: 'umd' is set. Adding that to the above config results in a build error "Missing external configuration for type:commonjs2". In this case I would also expect a mention in the docs about this incompatibility.

The current behaviour of leaving the dependency as undefined is surprising and hard to debug.
Other relevant information:
webpack version:  4.19.1
Previously reported bugs #4609 and #6302 have touched on some aspects of this issue, but have not provided a workable solution for the case when the external dependency is only available via AMD and the target is not a library.

Send a PR

I would prefer the 2. behavior

@sokra Do you have a specific reason for the preference? It would be really useful to have some way of using AMD dependencies without requiring an additional manual require() call. As is, e.g. HtmlWebpackPlugin is rather difficult to use with code that has AMD dependencies. The required compilation would effectively be the same as that used by AmdMainTemplatePlugin, just replacing  define with require.

As a thought, how would you feel about solving this by a combination of two changes:

Add the errors for non-AMD targets as per my earlier 2nd proposal
Add a new libraryTarget "amd-require" that would configure the AmdMainTemplatePlugin to use a require() rather than define() wrapper.

I'm relatively confident that I could send in PRs for both of those.

That's sound good 👍

Bump


Promisify app API?

Do we want to transition the big complex data functions in app (e.g. app.computeLinks) to work with Promises instead of callbacks? We have some pretty deep callback nesting, so it'd be a readability/maintainability win, but we'd make it behave even more poorly for hapless IE users who attempt to load it. We could polyfill, but I want to do as little polyfilling as possible...

Took the plunge on 106601b


set default values to separatorVisible and headerVisible attributes

I've also created a .gitignore file

thanks for your help


Avoid overriding packages installed in the system environment.

Currently, even if packages are installed in the base environment, they can be superseded by the ones installed in the .local folder. I think that better practice would be to forbid installing the core packages (aiida-core, aiidalab, aiidalab-widgets-base).

I believe this issue can be resolved by utilizing a global constraints file.

I realized that this would actually be much better achieved by adding the constraint to the global or user-wide pip-configuration file. I am therefore going to revert this change and introduce the fix on https://github.com/aiidalab/aiidalab-docker-stack .


Cannot install using npm

Hi,
I cannot install this.It shows below error list.Can you tell me how to install this ?
My ---> Node ver = 7.3.0 and npm ver = 3.10.10

I got the same error, installing typings "fixed" it -- I'm guessing the README or dependencies needs to be updated to include this dependency.


Consistent api names

Most api names are operations that HaaS will perform on the switch and nodes on behalf of the user. Actions like
– Registering node, nic, switch, port and removing it
– Connecting and disconnecting networks
– Adding and deleting ports.
Having consistent opposite names makes it intuitive and therefore easy for a new user to get comfortable using the API. To that end, I wish to have a discussion where we can rename API calls to have a consistent naming scheme.
Affected API names:
– node_connect_network and node_attach_network. Either it should be "attach/detach" or "connect/disconnect". This also applies to
port_connect_nic,
headnode_connect_network,
project_connect_node
– node_register and node_delete. Either it should be "register/unregister" or "add/delete". Similarly for
switch_register,
node_register_nic,
port_register
– Also @kylehogan hogan suggested it should be switch_<action>_port rather than port_<action> since we have node_register_nic
-- Also adding to the list, we should remove all the plural mention of the resources. Keep it all consistent and singular. eg. rather than list_free_nodes I'd prefer node/list_all, node/list_free.

@henn, @knikolla @gsilvis @zenhack @okrieg @pjd-nu @apoorvemohan @kylehogan @xuhang57
Since the choices are largely binary, I can make a doodle poll and let moc-team-list participate.
This is important since I am working on a client library and can include this changes in my next PR.

Why do you think connect/detach is inconsistent?
In the case of *_register, delete is something of a misnomer; unregister better reflects the semantics. That said, #25 left an impression on me; I'm allergic to typographically similar names for things that do very different (or opposite) things. How about add/remove?

Another point on the naming: I would encourage everyone to bear in mind that the names were discussing here are not the API. There's no a priori reason your client library's interface should even line up 1:1 (or close to it) with the functions in haas.api, as that's implementation detail -- the HTTP details described in docs/rest_api.md are what you're interfacing with. We probably shouldn't have function names in that document at all.
There's nothing wrong with the procedural API wrapper per se, but we ought to stop thinking of the interface as intrinsically procedural. Indeed, a lot of the names are inspired by object oriented thinking; node_register_nic is named that way because when we wrote it we were thinking node.register_nic, i.e. a method on the Node class. A client library could very well choose to reflect that.
Re: port_*, the server already has switch_register_port which is analogous to node_register_nic Consistency would suggest making port_connect_nic into switch_connect_nic, to mirror node_connect_network and friends, or to change node_connect_network to nic_connect_network. The latter would closer reflect the OO mapping. If you're thinking of URLs as objects, /node/cisco-32/nic/eth0 ought to be the URL for a nic, and so /node/cisco-32/nic/eth0/connect_network better be something primarily about the nic -- the procedural api makes it sound like it's a method on Node.
...Looking at the HTTP mapping, everything is actually pretty awkward, and this is in no small part because nobody looks at it. URLs should map to objects, and /node/cisco-32/nic/eth0/connect_nic is not really what you would think of as an object. If we're not going to pay any attention to it, we should be using something like JSON-RPC and just give up on pretending we have a REST API. I guess I'm not super enthusiastic about putting time into making the python names prettier when the thing that's actually eventually going to be the stable we-can't-change-this thing is such an eyesore.

I'm not sure the names in the wrapper library aren't an API, they're just not the same as the REST API. Eventually, both may become difficult to change.
On the URL object mapping, I can certainly see how /node/cisco-32/nic/eth0/connect_nic maps to an object. Node and nic are the abstract classes, and cisco-32 and eth0 are the object instances. Maybe it's only obvious in hindsight, but I can't off-hand think of a clearer way to express the object mapping. Did you have some suggestions?
WRT consistency, I noticed that we have generally have _, except when the action is show. list is another action that always precedes the object. If it's supposed to be OO'ish, then node.show() would likely translate to node_show. list is difficult because it works on collections so there is no object per se (except the collection itself). One thing is that we are consistent in our show and list naming, which may be good enough.

So eth0 is the nic, what's connect_network (Before I typed connect_network; typo)? The method I suppose, but that's a bit un-RESTful
a more RESTful way of doing that call would to have the object eth0/networks be the list of connected networks, and (with our current paradigm), you could PUT to eth0/networks/${channel}.
@ron-unrau, you're right; obviously, if we actually make a client library, then this becomes an API, and there are similar stability questions. I'm not saying we shouldn't pay attention to that. But this team has a tendency to ignore the REST api, and just jump to the wrapper around it. As if there's only ever going to be one wrapper, and nobody is ever going to interact with HaaS from any language but python. If we keep it up they won't be able to. Ideally though, it shouldn't be a total pain to wrap the API from another language, or even just use it via curl in a pinch. I just think the proportions of focus has been off.
It's probably a bit off topic for this issue. I just worry it's something that we'll never get to.
I think the show/list vs. object_whatever thing is fine; the pattern is at least clear. I think ironing out the other minor inconsistencies is what we should focus on here.

from @zenhack
Why do you think connect/detach is inconsistent?
In the case of *_register, delete is something of a misnomer; unregister better reflects the semantics. That said, #25 left an impression on me; I'm allergic to typographically similar names for things that do very different (or opposite) things. How about add/remove?

I like add/remove better than register/unregister

Also adding to the list, we should remove all the plural mention of the resources. Keep it all consistent and singular. eg. rather than list_free_nodes I'd prefer node/list_all, node/list_free.

PR merged. Close this now. Please reopen if necessary

We didn't really reach a consensus here...

Going to re-open; let's settle on what to do with the issue before we just close it.
Making the API more consistent might be worthwhile, but I'd like to come up with an actionable list of inconsistencies. Anyone want to start brainstorming?
I'm also tempted to suggest per my thoughts above that we actually remove the function call names from docs/rest_api.md, and describe things the way we do in the obmd readme instead.

I'm also tempted to suggest per my thoughts above that we actually remove the function call names from docs/rest_api.md, and describe things the way we do in the obmd readme instead.

yeah, let's keep the API description about APIs only


update TXN spec

Update the TXN.md with retentionWindow and snapshot-backed read related info, and rename it to K2-3SI-TXN.md

Will update.


From private repo

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


docs(README): Adjust README documentation

Description
Renewed the README documentation to provide comprehensive information about the GitHub-AutoResponse application. Updated the content to offer clear insights into the features, configuration steps, usage guidelines, contributing procedures, and licensing information.

Ready to merge


Vechain block observer added

Task:
Implement BlockAPI interface in VeChain platform for push notifications support;
Changes:
api.go <-
Implemented CurrentBlockNumber and GetBlockByNumber interface functions
Added getTransactions function
Added parsers NormalizeTokenTransaction and NormalizeTransaction for VET and VTHO tokens
client.go <-
Added GetCurrentBlockInfo function for checking current blockchain height
Implemented GetBlockByNumber, GetTransactionById request functions
Added getHTTPError, getAPIError for error handling
model.go <-
Added models Error, NativeTransaction, TransactionReceipt, Output, Event, Transfer, CurrentBlockInfo, Block
api_test.go <-
Implemented normalize functions tests

like in ziliqa?
Viacheslav Kulish
Mobile Blockchain Developer, Titanium Labs
+380639958314 |<EMAIL_ADDRESS>Skype: the_lion13 <#>
Ukraine, Cherkasy
http://facebook.com/Mufasamc2010
http://linkedin.com/in/viacheslav-kulish-99560b15a/
Create your own email signature
https://www.wisestamp.com/signature-in-email?utm_source=promotion&utm_medium=signature&utm_campaign=create_your_own
пн, 12 авг. 2019 г. в 17:52, Leone Parise<EMAIL_ADDRESS>
@leoneparise commented on this pull request.
In platform/vechain/api.go
https://github.com/trustwallet/blockatlas/pull/254#discussion_r312966151
:

}

if len(t.Receipt.Outputs) == 0 ||

len(t.Receipt.Outputs[0].Events) == 0 ||

len(t.Receipt.Outputs[0].Events[0].Topics) != 3 {

return tx, false

}
valueBase10, err := util.HexToDecimal(t.Receipt.Outputs[0].Events[0].Data)
if err != nil {

return tx, false

}
fee := blockatlas.Amount(feeBase10)
value := blockatlas.Amount(valueBase10)
fromHex := t.Receipt.Outputs[0].Events[0].Topics[1]
toHex := t.Receipt.Outputs[0].Events[0].Topics[2]
from := "0x" + fromHex[26:]

Don't we have a utility function to format hex values and append 0x?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/trustwallet/blockatlas/pull/254?email_source=notifications&email_token=AH3DWP3DMHKPJ5K62F5JWGLQEF2JRA5CNFSM4IK2OH32YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCBIQVBI#pullrequestreview-273746565,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH3DWP5JO2S2XJNA3YVBJYLQEF2JRANCNFSM4IK2OH3Q
.

--
[image: photo]
Viacheslav Kulish
Developer, Titanium Labs
+380639958314 |<EMAIL_ADDRESS>Skype: the_lion13 <#SignatureSanitizer_SafeHtmlFilter_>
http://facebook.com/vcoolish
http://linkedin.com/in/viacheslav-kulish-99560b15a/
Create your own email signature
https://www.wisestamp.com/signature-in-email?utm_source=promotion&utm_medium=signature&utm_campaign=create_your_own

@vcoolish Could you look at https://app.codacy.com/app/TrustWallet/blockatlas/pullRequest?prid=3989508 and make appropriate changes ?. Thank you for the PR.

sure, I will do it asap. Thanks.
Viacheslav Kulish
Mobile Blockchain Developer, Titanium Labs
+380639958314 |<EMAIL_ADDRESS>Skype: the_lion13 <#>
Ukraine, Cherkasy
http://facebook.com/Mufasamc2010
http://linkedin.com/in/viacheslav-kulish-99560b15a/
Create your own email signature
https://www.wisestamp.com/signature-in-email?utm_source=promotion&utm_medium=signature&utm_campaign=create_your_own
вт, 13 авг. 2019 г. в 08:11, Mykola<EMAIL_ADDRESS>
@vcoolish https://github.com/vcoolish Could you look at
https://app.codacy.com/app/TrustWallet/blockatlas/pullRequest?prid=3989508
and make appropriate changes ?. Thank you for the PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/trustwallet/blockatlas/pull/254?email_source=notifications&email_token=AH3DWPZEQG35AX6GRQTRIMDQEI7BVA5CNFSM4IK2OH32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4ER3EI#issuecomment-520691089,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH3DWP3MVEVNSNZEXAD2VWTQEI7BVANCNFSM4IK2OH3Q
.

--
[image: photo]
Viacheslav Kulish
Developer, Titanium Labs
+380639958314 |<EMAIL_ADDRESS>Skype: the_lion13 <#SignatureSanitizer_SafeHtmlFilter_>
http://facebook.com/vcoolish
http://linkedin.com/in/viacheslav-kulish-99560b15a/
Create your own email signature
https://www.wisestamp.com/signature-in-email?utm_source=promotion&utm_medium=signature&utm_campaign=create_your_own


[WIP] Add support for reordering of Col component and alignment of Row component (#169)

This PR is WIP, to give you an idea on the discussion on how to implement the two features.
I implemented flexbox reordering for Col component, where each reordering class is passed via a single prop, where true and"all" is interpreted as adding the reordering for all sizes (xs, sm, md...).

[X] Reordering for Col component
[ ] Horizontal and vertical alignment for Row component
[ ] Update docs

Updated to alignment, now taking one prop for each value (xsFirst, smLast, etc.)

Closing this out, see https://github.com/reactstrap/reactstrap/issues/169#issuecomment-270574607 for more info


fix Julia 1.0 resolver issue

The target branch of this PR is #13 (not master)

Pkg version resolver is not smart enough to figure out a possible Manifest.toml in some cases. Here we manually set the versions for old Julia CI targets.
; metric as a syntax sugar only exists in new Julia versions, so for backward compatibility, I changed it to ; metric=metric.

Codecov Report

Merging #14 (8920ea2) into adrhill/color-diffusion (147b591) will decrease coverage by 5.00%.
The diff coverage is 100.00%.

@@                     Coverage Diff                     @@
##           adrhill/color-diffusion      #14      +/-   ##
===========================================================
- Coverage                    90.00%   85.00%   -5.00%
===========================================================
  Files                            7        7
  Lines                          120      120
===========================================================
- Hits                           108      102       -6
- Misses                          12       18       +6

Impacted Files
Coverage Δ

src/colorspaces.jl
77.77% <100.00%> (ø)

src/error_diffusion.jl
97.61% <100.00%> (ø)

src/show.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

src/eval.jl
33.33% <0.00%> (-33.34%)
:arrow_down:

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 147b591...8920ea2. Read the comment docs.

Thanks! 😊


Remove ruleset for printing AST

This issue originates from a discussion starting with this comment.
Ktlint CLI allows printing of the AST of a file or a piece of code via option --print-ast. Also it is possible to print the AST in unit tests by setting environment variable KTLINT_UNIT_TEST_DUMP_AST. The value of this functionality is very low compared to using the IntelliJ IDEA plugin PsiViewer.

@paul-dingemans could you also publish a new version of com.pinterest:ktlint which is used by org.jlleitschuh.gradle.ktlint for example.
ktlint-ruleset-test-tooling is still in the latest version 0.49.0-20230328.095730-189.
(https://oss.sonatype.org/content/repositories/snapshots/com/pinterest/ktlint/0.49.0-SNAPSHOT/ktlint-0.49.0-20230328.095730-189.pom)

As a result of an uninteded change, all snapshots starting from PR #1898 have been published to a different location. This will be fixed with #1929. In the 1.x release of ktlint we will switch to the new group coordinates.

Published, you can ref the integration in https://github.com/Goooler/DemoApp/pull/373.


Second image for firewall premium is blurry

The words on this image are hard to read

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

ID: 474ba3cb-afa1-4ec5-37df-6553a5523dbb
Version Independent ID: 56096558-1943-3f6b-9609-7722200272fb
Content: What is Azure Firewall?
Content Source: articles/firewall/overview.md
Service: firewall
GitHub Login: @vhorne
Microsoft Alias: victorh

Thanks for the feedback! I have assigned the issue to the content author to investigate this and update the document as appropriate.

fixed
#please-close