Make 'Select items' compatible with 'Scan In Items' and 'Return Items' screens

The cloud app currently supports a 'Select items' option to choose items to print that are visible in a search results screen.
For our acquisitions and maintenance workflows, it would be a desirable enhancement to be able to print labels using the 'Select items' view directly from the 'Scan In Items' and 'Return Items' screens.
For acquisitions, we currently:

Receive the item
End process the item
Perform cataloguing / copy cataloguing as necessary
3a. This often involves a librarian reviewing the classification
Scanning the item into SpineOMatic desktop to print a label
Scanning in the item through 'Scan In Items' to complete the work order.

To embed the cloud app into our acquisitions workflow, it would make a lot of sense to be able to scan in the item/s, click the cloud app, and have the scanned in item/s currently listed on the 'Scan In Items' page available under 'Select items'.
For streamlining high-volume physical acquisitions workflows, this would help reduce duplication and multiple scans of barcodes in different screens, and would aid individual or bulk printing for items in-hand that the operator has already scanned in.
Hopefully the 'Return Items' screen would be similar to implement - for maintenance, our circulation desks each have a spine label printer for easy reprinting of labels as needed, and they primarily use 'Return Items'. If an item is returned, and the CSO notices it needs a new label, they could avoid having to double handle the item by opening it up to scan again, and could print directly from the cloud app using 'Select items'.

@jonahhighmanUWA, this is coming to "Scan In Items" in the June 2024 Alma release. It has not been added for "Return Items".


Cannot run ftdetect in Vundle

I am using Vim 7.4 on Linux with Vundle and Git. I am writing my own plugin called potion (following an example in the book LEARN VIMSCRIPT THE HARD WAY by Steve Losh) that is stored in my GitHub repository.
The potion folder structure looks like the following:
potion
+ README
+ LICENSE
- colors/
   + potion.vim
- doc/
   + potion.txt
- ftdetect/
   + potion.vim

Using a brand new environment, I copy the Vundle repo:
git clone https://github.com/VundleVim/Vundle.vim.git ~/.vim/bundle/Vundle.vim
I have the following as my minimalist .vimrc file:
set nocompatible

filetype off                   " required
filetype plugin on

set rtp+=~/.vim/bundle/Vundle.vim/

call vundle#begin()

" let Vundle manage Vundle, required
Plugin 'VundleVim/Vundle.vim'

" Load my plugin.
Plugin 'MisterSnrub/potion'

call vundle#end() " required!

filetype plugin indent on     " required

After loading my potion plugin, I create a new file ~/factorial.vim. The ftdetect/potion.vim file should be run and a "Hello world" message should be output. And if we type "set ft?" in factorial.pn, it still does not recognize the potion filetype.
However, if I copy-and-paste the file ~/.vim/bundle/potion/ftdetect/potion.vim file to ~/.vim/ftdetect/potion.vim (so that it is run outside of the Vundle process), I do get the "Hello world" output, and "set ft?" returns "filetype=potion", as expected.
Tested in Vim 7.4

Also tested in gVim version 9.1 using "~/vimfiles/bundle" as my Vundle folder.


Only format a url if it is present

Currently is the homepage is present on a project the create action fails.
This is the error I received:
NoMethodError (undefined method `[]' for nil:NilClass):
  app/models/project.rb:77:in `format_url'
  app/models/project.rb:70:in `update_from_github'
  app/models/project.rb:42:in `update_info'
  app/models/project.rb:15:in `create_from_github_url'
  app/controllers/projects_controller.rb:26:in `create'

nvm fixed with d2357c41f35a39352d83f5632ba1879f78beaa36

Ah, sorry my bad on that one!

No problem :smile:


[Feature]: Ability to freeze columns in table widget

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
A way to lock/freeze columns so that when you scroll horizontally through the rest of the table the locked columns stay put on the screen.
Why should this be worked on?
It'd be very useful when there are many columns in the table and you need some columns to be always visible on the screen. Like pinning columns on ag-grid - https://www.ag-grid.com/javascript-data-grid/column-pinning/
Asked by discord user - https://discord.com/channels/725602949748752515/760761686549463060/950217151627808799

Duplicate of https://github.com/appsmithorg/appsmith/issues/3265


Scoreboard api guide please

How to use scoreboard api (AdvencedCore), guide please <333

Still need help?


Tale of immortal System.Net.WebException: Error: ConnectFailur

Installed MelonLoader for the game Tale of Immortal. The translator starts up successfully, but communication with the server is not established, and after 5 attempts it stops working. Log copied directly from the window.
Log.txt

Installed MelonLoader for the game Tale of Immortal. The translator starts up successfully, but communication with the server is not established, and after 5 attempts it stops working. Log copied directly from the window. Log.txt

did you ever manage to make it work?

Installed MelonLoader for the game Tale of Immortal. The translator starts up successfully, but communication with the server is not established, and after 5 attempts it stops working. Log copied directly from the window. Log.txt

Installed MelonLoader for the game Tale of Immortal. The translator starts up successfully, but communication with the server is not established, and after 5 attempts it stops working. Log copied directly from the window. Log.txt

did you ever manage to make it work?

im play its my config
this game us MelonLoader
put this in game folder
https://mega.nz/file/DVZSzIbJ#uczjLYTwaiJRaIV_daJcefFl3o5eb94gju05SMn2oh8
open this AutoTranslator\Config.ini
modify this
[General]
Language=ru   <- you lang

Installed MelonLoader for the game Tale of Immortal. The translator starts up successfully, but communication with the server is not established, and after 5 attempts it stops working. Log copied directly from the window. Log.txt

https://mega.nz/file/GRYDgC7K#55dCVEHWcclKquwk225JJPdL8YK9gtCFyUZR-D0VI80


In CSV reader, add a loading icon while the csv file is loading

cc @serverfire

No longer needed.


Subreddits in new Fullscreen modal presentation become unresponsive?

Found out it was when trying to hide the fab that may not have been present. Fixed by checking for a fab in hideUI before continuing


How to use it from top side for alerts?

Description
Describe your issue here.
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[ X] question
[ ] documentation related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Hey, How can I use pan present from top side not bottom on alerting something.

Hey @wixvii , unfortunately this library only supports presentation from the bottom of the screen. We don't have any current plans to support presentation from the top.

I just wanna add +1 on this

Still no plans?


Added local and localhost to skipped TLDs

localhost and local are tlds blocked in the Handshake code as they are used by the local computer or network. As such fingertip should not direct these through the proxy.

Thanks for the PR! I wouldn't add those to the tld.go list as it's (was?) intended to be auto generated see comment.
You can add those to config.go#235 instead. Fingertip already skips .localhost, .test, .example and .invalid per rfc2606 see here but a PR to also include .local is welcome!


Google Cloud Storage Support

I was hoping to user yas3fs with Google Cloud Storage. I've had luck with other s3 mounter tools I have tested due to the s3 compatibility mode on GCS.
But I was disappointed to find that yas3fs enforces syntax that makes it impossible to get it to mount buckets from https://storage.googleapis.com/ (rather than s3://)
Would it be possible to add an argument for explicitly setting the url prefix rather than assuming everything is mounted from s3://   ?    Based on my experience with other s3 mounters, I'm fairly certain  yas3fs will work on GCS with no other changes if only the URL could be fed to it correctly.
thank you
Here is the error message when using https://storage.googleapis.com/ :
ERROR The S3 path to mount must be in URL format: s3://BUCKET/PATH, use -h for help.

So, I did a quick proof of concept and I was able to mount GCS. But my updates are not perfect. I can't list directories properly. Here is a link to my hack. Any pointers to getting directory listing working would be appreciated.
https://github.com/lordtangent/yas3fs/commit/ea264449d05c8c06263db8d9613e3293297ea6a2
Here is the debug info that dumped out when I tried to list directories:
2016-03-10 09:16:54,525 DEBUG readdir '/test_dir' '0' S3 list 'test_dir/'
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/fuse.py", line 414, in _wrapper
    return func(*args, **kwargs) or 0
  File "/usr/lib/python2.7/site-packages/fuse.py", line 602, in readdir
    fip.contents.fh):
  File "/usr/lib/python2.7/site-packages/fuse.py", line 881, in __call__
    ret = getattr(self, op)(path, *args)
  File "/usr/lib/python2.7/site-packages/yas3fs/__init__.py", line 1699, in readdir
    for k in key_list:
  File "/usr/lib/python2.7/site-packages/boto/s3/bucketlistresultset.py", line 34, in bucket_lister
    encoding_type=encoding_type)
  File "/usr/lib/python2.7/site-packages/boto/s3/bucket.py", line 473, in get_all_keys
    '', headers, **params)
  File "/usr/lib/python2.7/site-packages/boto/s3/bucket.py", line 411, in _get_all
    response.status, response.reason, body)
S3ResponseError: S3ResponseError: 400 Bad Request


pull request for e2e test at 12/10/2016 09:45:05

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Distribution of messages among offline clients

VerneMQ Version: 1.12.3
OS: Ubuntu 18
Cluster size/standalone: 1

I was testing shared subscriptions and I found one issue that can be problematic for unaware users and I think this could be fixed.
Consider a case where horizontally scaled microservice subscribes to a topic using a shared subscription (for load balancing).
Steps:

5 Instances of a service are subscribed to a shared topic using QOS=1 & clean=false wanting not to lose messages
Services get messages distributed among 5 instances OK
Autoscaler or admin scales microservice to 1
Only one online microservice is receiving all the messages now OK
Microservice dies because of any reason
Messages are distributed among 5 offline clients NOK & VerneMQ is waiting for those clients to connect
Died microservice is stared again and gets 1/5 of messages (published during offline period) NOK
4/5 of messages will be published to other subscribers when they connect (if it ever happens) NOK

Expected:
In my opinion when all subscribers are offline, qos 1 messages should be treated equally an no client assignment should be done. Client assignment should be done just before sending messages to online clients, not before saving msgs to DB.
With such implementation first client becoming online would receive all messages from the offline period and no msgs would be lost or processed later than expected.

@mwilniewiec Thank you for your input. It's an often raised point.
While I do not dismiss it as invalid, your picture of the feature is incomplete. Let me, therefore, add a couple of points.
You expect Shared subscriptions to behave as a single queue. This is not the case in VerneMQ. Each subscriber has an exclusive queue it consumes from. This enables the following features:

Shared consumers can still control their session settings (like a regular MQTT client). Namely, they should not request message persistence if they do not intend to come back to collect them.
Mixed scenarios (some subscribers are persistent, some not)
Optimisation in a cluster: we can deliver messages incoming at a specific node to a shared subscriber on that same node. This is called local delivery.
Above allows for more flexible load balancing policies (called Shared Subscription Policies). Currently, the following policies are implemented:  prefer_local, local_only, random, and prefer_online_to_local. The last one is new and available in the main branch but not yet part of a release.

So there are multiple criteria in a Shared Subscription Policy. Some of those are implicit and admittedly non-intuitive. (prefer_local will prefer an offline consumer on the local node to an online consumer at a different node, as an example).
To make things simpler, I have added the prefer_online_to_local strategy, which always routes messages to an (any) online consumer in the cluster. It's a more expensive strategy because we need to determine whether consumers are online or offline. But it might be an acceptable trade-off for your use case, as it should allow you to avoid "cold" offline queues.
On a general note: you can use Shared subscribers to do consumer side load-balancing. So you'd use five subscribers when the capacity of your consuming application allows for 1/5 of the message throughput. If one consumer can handle it all, why use Shared Subscribers at all? (rhetorical point only... I get what you want to do)

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
:point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

I came here with quite good knowledge on how RabbitMQ or Kafka works. Maybe I'm a bit shortsighted when it comes to MQTT but lets take the problem under consideration starting from the very beginning.
What was the real motivation of introducing shared subscriptions in MQTT?
I would say this is load balancing of messages between multiple customers.
Why would you ever want to load balance your messages?

Thoughtput is so big that vertical scaling of a customer is not enough, you want to scale horizontaly.
You want to have high availability of your consumer and when one dies you want others to do his job immediately.
Your thoughtput is not that big right now but you are building a horizotally scallable system which is able to handle lots of users/iot devices and get ready for the future.
Additionally new trends like microservices, kubernetes/docker swarm, autoscaling makes it very simple to scale up your services to have multiple consumers.
I would say that vast majority of shared subscription clients are horizontally scaled services (where every each of it is the same, in rare cases twin-similar). Its designed for a many publishers, one subscriber problem.

What was the real motivation of doing clustering in VerneMQ?
I would say 3 points from above are also valid.
I also think that broker cluster should give you those benefits but should be totally transparent when it comes to functionality and how clients use the broker. When you a are a publisher or a subscriber you don't care if broker is a single instance or its a cluster of 10.
I can understand that current implementation works the way you described but its a bit hard for me to find a business case where multiple consumers sharing one subscription are set in a mixed mode where some are persistent, some are not.
A consumer using a shared subscription will get only a random part of the whole stream. When he is really unlucky, he might get almost no messages.
I can't also find a business case where online client is doing nothing and messages are sent to a local offline client queue and waiting for him to connect (if it ever happens).
Of course in case clients configure such a monster - broker must behave somehow but I would say its a minor problem how it's solved.
My thoughts:
The tool/feature/program should mainly solve the problem it is created for. Implementation under the hood is just a detail.
If only motivation of Shared Subscription Policies was performance optimization I would say its unnecessary complexity and it breaks the rule of standalone broker working the same as cluster of brokers.
From my perspective the basic rule for Shared subscriptions should be Distribute between online clients.
With optional settings like: random_local_first, random, round_robin, idle_first.


Add functional record update

See discussion in #113.
I'm leaning towards {rv, x = 42, c= true} as the best one, but with an extension: instead of a field-value pair, one can put an arbitrary expression evaluating to a record, and the fields of that record will be included.
The big question: should leftmost or rightmost records take precedence?  This affects whether setting the field x to 42 in rv should be written {rv, x=42} or {x=42, rv}.

Summary for @melsman to comment.
The expression grammar is extended with the following construct (in EBNF):
exp: "{" (exp | fieldid "=" exp) ("," [exp | fieldid "=" exp])* "}"

This means that a record expression is now a comma-separated sequence of either "field=value" pairs, or an arbitrary expression.  In the former case, the given field of the record being constructed will have the indicated value.  In the latter case, the expression must evaluate to a record, and the fields of that record are added to the record being constructed.  In case a field is mentioned several times, the right-most takes priority.
For example, we can do record concatenation: {fv1, fv2} contains the union of the fields in fv1 and fv2.
Functional record update is just a special case: {fv1, x = 2}.
I like the simplicity and generality of this approach.

The biggest problem I see with the record update syntax
let r1 = {...} in let r2 = {...} in {r1, r2}

is that typing will succeed for all possible records r1 and r2, as I
understand the previous discussion. Only an external type constraint will
force the resulting record to be well-typed and it may even be that fields
in r1 are overwritten (also wrt types) by the r2-binding. If instead
there were two different syntactic constructs for catenation and
record-update, the programmer would better be able to express the
intensions, which would lead to a type error popping up closer to where the
mistake is...
On Fri, Mar 3, 2017 at 1:46 PM, Troels Henriksen<EMAIL_ADDRESS>wrote:

Summary for @melsman https://github.com/melsman to comment.
The expression grammar is extended with the following construct (in EBNF):
exp: "{" (exp | fieldid "=" exp) ("," [exp | fieldid "=" exp])* "}"
This means that a record expression is now a comma-separated sequence of
either "field=value" pairs, or an arbitrary expression. In the former case,
the given field of the record being constructed will have the indicated
value. In the latter case, the expression must evaluate to a record, and
the fields of that record are added to the record being constructed. In
case a field is mentioned several times, the right-most takes priority.
For example, we can do record concatenation: {fv1, fv2} contains the
union of the fields in fv1 and fv2.
Functional record update is just a special case: {fv1, x = 2}.
I like the simplicity and generality of this approach.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/HIPERFIT/futhark/issues/313#issuecomment-283944513,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHRu2RdScS4kKKtH02l5IazSl_dwGdwks5riAu3gaJpZM4MPwle
.

I've also considered that problem.  I don't think it's a large enough problem to avoid this solution.  For two main reasons:

Right now, we can't have partial record types the way we have in SML.  Also, all function parameters must have an explicitly assigned type.  This prevents the error from propagating too wildly, as I've noticed can easily happen in un-annotated SML programs.

When we do finally get proper type inference and/or partial record patterns, any confusion can be cleared up with improved compiler error messages.  GHC has a very nice feature where the inferred types of relevant bindings are printed along with the type error - this is very useful for seeing where the inference went off the rails.

There is another problem I thought of, which is that a programmer may forget that record construction is right-biased, and end up writing {x = 2, rv}.  Fortunately, this is easy to detect and warn about in the type checker.  A more tricky case is if the programmer writes {rv2, rv1} but really intended {rv1, rv2}.  We can't read minds.  But this case only occurs when the programmer does not use explicit record assignment, and would occur no matter which convention we pick.


Added new examples. Modified an API.

Added two dll proxy examples.
Modified an API.

Thank you for your reply which gave me some tips


Autoroute migrations: Consolidate UpdateFrom4 changes into Create

UpdateFrom4 was added in #7449, but its changes were not added to Create, which makes further changes/contributions harder.

Fixed in #8217


CustomHttpClientHandler vs ModernHttpClient

I'm wondering if it's possible to use ModernHttpClient in conjunction with the technique described in the README regarding setting authorization headers via a custom handler:
https://github.com/paulcbetts/refit#authorization-dynamic-headers-redux

Duplicate of #42

Thanks @Cheesebaron!


Button: Small buttons are not sized correctly

See screenshot (from https://modus-web-components.trimble.com/?path=/docs/components-content-tree--multi-selection) showing active state here:

We should specify height and width of the button, or set consistent vertical/horizontal padding to fix this issue.

@ElishaSamPeterPrabhu Maybe the modus-button should have icon-only on it e.g. icon-only="add" ?

@ElishaSamPeterPrabhu Maybe the modus-button should have icon-only on it e.g. icon-only="add" ?

Yes we can do that but the icon map doesn't contain for the other icons
So where should we update them?

...or instead use some custom CSS like:
height: 28px; width: 28px; padding: 8px; margin-left: 8px

height: 28px; width: 28px; padding: 8px; margin-left: 8px

after applying the css

Is this the expected look?

not exactly, I just included that CSS as a starting point which improves things somewhat.

Is this the expected look?

not exactly, I just included that CSS as a starting point which improves things somewhat.

@coliff
There are two points to address

#1466 has a similar need to decide between modus button with icon-only property or the custom css with svg.
Is there a reference on how the custom bar should look as its not available in figma?


fix documentation in README for radios

Got a little bit confused about radios when reading documentation. Did I understand everything right?

Good catch, thanks.


Add Blazor support for SortByFieldName on anchor and text columns

Pull Request
🤨 Rationale
Adds support in Blazor for the SortByFieldName property on the anchor and text columns.
👩💻 Implementation
Followed existing patterns to add the SortByFieldName property to the anchor and text column components.
🧪 Testing
New tests for the property
✅ Checklist

[ ] I have updated the project documentation to reflect my changes or determined no changes are needed.

@atmgrifter00, will you buddy this PR for me?

Seems like a straightforward change, assuming that @atmgrifter00 would agree that we can bypass @msmithNI. Marking the PR automerge.


Test python 3.10 in CI

Python 3.10 is now bundled in most distributions, and we should make sure that it works properly. Maybe it doesn't make sense to test four versions, so I suggest these:

python 3.7 (for compatibility)
python 3.9 (many will still use this)
python 3.10 (all new users will use this)

Many will of course also be on 3.8, but if it works on 3.7 and 3.9, it probably works for 3.8 too.
A heads-up in case I'm not the one implementing this:

rasterio 1.2 does not work with 3.10! rio 1.3 will work, and their latest master works, but the 1.3a2 does not. https://github.com/rasterio/rasterio/commit/329c481bfdad4fa3272d07a548001f5ec1e8bda4 fixed this on 26 November 2021, so any release after that should work.
I've also had issues with fiona. This was also fixed (https://github.com/Toblerity/Fiona/commit/3b1e80bfba017651151942b46fa1744e7fee6842; 22 November 2021), but has not yet been found in a release.

In addition, it would be great to somehow stay ahead of the curve and test python 3.11 as well! (It's in alpha 3 at the time of writing)

Decided to add 3.10 but to include 3.11 only when it is stable.


feat(oracle): oracle gas needs to be low/negligible

Problem
Currently, votes for x/oracle are expensive for node operators even with lowered fixed gas. Currently, it costs 500 unibi and is dictated by the OracleMessageGas constant from ante/fixed_gas.go. Although this gas cost is low compared to something like MsgMarketOrder (200k unibi), it adds up to be a lot due to the frequency of transactions that have to be sent for the oracle voting rounds.
Prohibitive costs on x/oracle make it unlikely for us to have full participation from every active validator, so we need to make it more cost-efficient without increasing the potential for spam.
MVP Solution
Add a module-specific ante handler similar to the one in x/devgas/ante that has access to the OracleKeeper. When a tx comes in:

Check if it has an oracle pre-vote or vote msg. Otherwise, don't change its gas (exit).
Check if the sender is an eligible oracle voter (active validator or delegated feeder). Otherwise, exit.
Ensure that the tx only has one message. Otherwise, exit.
If the oracle has not already voted or prevoted at the current ctx.BlockHeight and voteHash, lower the gas cost significantly.

Open Problems
Spam prevention: We need to make sure that a single active validator can't troll by filling up blocks with low-gas oracle transactions. This becomes more challenging as we lower the gas for the oracle voting messages.
What ways can step 4 of the MVP solution be exploited to spam the network?

Log:

2023-09-18: Description follows a recent discussion with @jgimeno

The actual reason why node operators are paying so much gas to run a pricefeeder is because our pricefeeder implementation sets the gas fees too high, which was addressed in https://github.com/NibiruChain/pricefeeder/commit/df1f3b3f1f8f6a2954a17b2aedc0d643c7045747.
As for the spam issue, I like the idea of having an AnteHandler that has access to OracleKeeper, which can check if the validator has already prevoted/voted in that vote period and only reduce the gas if they haven't voted yet (thereby penalizing the validator for voting multiple times by inducing higher fees).


fix bug: KeyError, can't find some parameter key

fix paddle model2tvm, can't find key:
int  relay/frontend/paddlepaddle.py
self.params[name] = _nd.array(scope[name])
KeyError: 'generated_tensor_0'
@siju-samuel
cc @jiangjiajun @heliqi

One suggestion: The title could be changed to "[Frontend] [Paddle] fix bug ..".
LGTM!

@junrushao1994 Could you help to merge this pr?

Of course! Thanks for the contribution!

OK, thank your suggestion


Update doctest code for more consistent runs

Description
Doctest seems to be failing locally because of updates with needClean or pitId fields being included in _explain requests, but when trying to update the test cases to account for this, they start failing again as the field list changes more. This PR adds a normalization step to get these tests to behave more consistently.
Related Issues
N/A
Check List

[X] New functionality includes testing.
[ ] New functionality has been documented.
[X] New functionality has javadoc added.
[ ] New functionality has a user manual doc added.
[ ] API changes companion pull request created.
[X] Commits are signed per the DCO using --signoff.
[ ] Public documentation issue/PR created.

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

@Swiddis Thanks for the change! Could you verify if this is related https://github.com/opensearch-project/sql/issues/3048?

I copied the changes to 2.x and looked at the failures: those failures actually seem related to this PR: updating a specific dependency of sql-cli caused the padding on formatted tables to change.

I copied the changes to 2.x and looked at the failures: those failures actually seem related to https://github.com/opensearch-project/sql-cli/pull/30: updating a specific dependency of sql-cli caused the padding on formatted tables to change. I'll add the updates to this PR.

So, it turns out that this formatting change affects a lot of tables. I automated refactoring all of them and verified it passes locally, the diff jumped up to ~2k lines. To refresh the doctests locally you need to purge the venv and repo with outdated dependencies, rm -rf ./doctest/.venv ./doctest/sql-cli.

Test failures related to #3056, waiting to merge that

Gradle build is passing as advertised, BWC seems to have unrelated issues


Color problem

TCameraComponent of Android and iOS (without GlobalUseMetal) is wrong.

Fixed in v3.0.1


Error in Testcase - Day 21 - Test Of Accuracy

In the testcase, the first point given as
30 40 10

but in the diagram, line is plotted for
30 10 10

So if the first point is 30 40 10 , then 4 targets can be hit.
3 targets can be the maximum, only if the first point is 30 10 10

There is an error in the Sample Input provided in the question.
The first point should be 30 10 10 only.
It will be rectified at the earliest.

Thank you for spotting the error.


wizzy diff commands

wizzy diff dashboards stage prod
wizzy diff panels dashboard-1 dashboard-2

:+1:


monitoring: migrate from OpenCensus to OpenTelemetry

~Blocked by https://github.com/open-telemetry/opentelemetry-go/pull/4306. I have a hold until that is ready; should be fairly quick~
For https://github.com/istio/istio/issues/44743
Fixes https://github.com/istio/istio/issues/44513
This PR migrates from OpenCensus to OpenTelemetry for Go metrics. This
doesn't impact proxy metrics, or non-metrics observability.
These changes are intended to be 100% transparent to end users.
The changes are mostly transparent from pkg/monitoring public
interface, with a few changes:

Register is no longer needed. Creating the metric registers it. This
makes no real difference in any of our usage
MustCreateLabel -> CreateLabel; it is infallable
No need to define the set of keys upfront with the metric.
RegisterIf -> WithEnabled
monitortest behaves slightly different; only metrics recorded after
its creation are counted. A few tests are updated to handle this
change.
Only one exporter can be defined; this only impacts tests, which are
updated to handle this.

There are a number of changes, of course, to the internals. Most of this
is a fairly mechanical translation. A few quirks:

There is no real Gauge like in OC. Instead, we can only do a callback.
So we need to handle a bit of this on our end; not a huge deal, and
looks like it will be added eventually.
Setting histogram buckets is a bit awkward currently. This will be
addressed eventually upstream.
monitortest previously was based on OC internals. This has been re-written to prometheus instead of OTEL. This is because prometheus is our primary usage, so its a bit more realistic.

~This results in a 1% increase in the binary size, which is due to importing both OC and Otel. This is addressed in https://github.com/istio/istio/pull/46010, which introduces a 1% decrease in binary size when combined with this PR.~

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

FYI: I test with opentelemetry-go offline, it's will add _total suffix fro counter, which maybe a regression
https://github.com/open-telemetry/opentelemetry-go/blob/4d473d105a5f59a58d153e7c492a4ea0ee027871/exporters/prometheus/exporter.go#L216

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
a2e551c3eb25f7b0e38fe988c5e17cac8952a570
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
a2e551c3eb25f7b0e38fe988c5e17cac8952a570
link
true
/test lint

unit-tests_istio
a2e551c3eb25f7b0e38fe988c5e17cac8952a570
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
a2e551c3eb25f7b0e38fe988c5e17cac8952a570
link
true
/test unit-tests

lint_istio
6ecac3bb4de7d4f88dffe72c534b3fce4f3d66af
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
31fc60b32d87f0fcf8b5e324ba010ff9a1f713cd
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
31fc60b32d87f0fcf8b5e324ba010ff9a1f713cd
link
true
/test lint

unit-tests_istio
31fc60b32d87f0fcf8b5e324ba010ff9a1f713cd
link
true
/test unit-tests

integ-ambient_istio
31fc60b32d87f0fcf8b5e324ba010ff9a1f713cd
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Looks very good.
One concern - not blocking this PR - is that I would prefer if labels are declared at metric creation, even if otel doesn't require it.


Download only selected bands/files on cop_dataspace

Hello,
I would like to ask if there is a chance at some point to extend some functionality for specific providers. Here, that would be Copernicus Dataspace.
Some datasets like e.g., Sentinel-1 or -2 can be pretty heavy, while a user may only need just a few bands (#910).
When querying thru oData e.g. "https://catalogue.dataspace.copernicus.eu/odata/v1" instead of downloading a whole zipped *.SAFE file, a user can download manifest XML only:
url = f"{catalogue_odata_url}/Products({product_identifier})/Nodes({product_name})/Nodes(MTD_MSIL1C.xml)/$value"
After taking band names from XML, a user can download files (bands) of interest. The whole approach is in https://github.com/eu-cdse/notebook-samples/blob/main/geo/odata_basics.ipynb (although there is a typo in the search (https://github.com/eu-cdse/notebook-samples/issues/49).
Would that be something to consider?
Thanks!

Hello @Rapsodia86 and thanks for this feature request and the associated inputs!
Single assets download is already implemented on the develop branch and will be shipped in the incoming v2.12.0.
You will be able to download individual assets from the new creodias_s3 provider or also STAC providers like astraea_eod, earth_search, planetary_computer`, ....
Not yet with cop_dataspace, but we will plan to make it available using your inputs!

For this feature, OData should be used for creodias and cop_dataspace instead of OpenSearch

Walking through the node tree of the products to discover the assets requires a high number of HTTP request (~10 request per product), leading to a high execution time. As alternative solution, the manifest file can be used to get all the assets at once.
The file name of the manifest is different among different Sentinel products:

for Sentinel-1 and Sentinel-2 the file is manifest.safe
for Sentinel-3 the file is xfdumanifest.xml
no manifest file for Sentinel-5

The Copernicus Data Space support team has been contacted to have a clarification on the different behavior.


UiAutocomplete

I'm not sure where you define the value prop? But it's returning the text value. I can't see how to return the value property which contains my id?
Ideally I would like to:

:text.sync=""

to sync the text

:value.sync=""

to sync the value

:object.sync=""

to sync the whole object

The behavior you are describing (where the text and value are synced separately) was removed when I rewrote the autocomplete in v0.8.6.
Now it only only auto-completes the user's input, therefore there is only one prop to watch, the value.
What you want is more like a select component, which I plan on adding soon.

I want a select too yes. But I use the auto complete to search for collections in the database like users. I want the users name to be displayed, but I want to submit the users ID.

In that case you could use the text (value) to find the ID if you have it in a suggestions array. This is how it was done in v0.8.5:
function findValue(text) {
    // Just return the text if suggestions is an array of strings
    if (this.suggestions[0] && typeof this.suggestions[0] === 'string') {
        return text;
    }
    text = text.toLowerCase();
    for (let i = 0; i < this.suggestions.length; i++) {
        if (this.suggestions[i].text.toLowerCase() === text) {
            return this.suggestions[i].value;
        }
    }
    return null;
}

You can then run this function on submit to find the user ID. The new select component will have this functionality by default.

I'm not sure if we differentiate a select and an auto complete the same way?
For me a select has a preset range of values and don't have a search option
The auto complete has a dynamic set of values and they are found by searching

A select can also be dynamic and have search. Like, for example, Select2.
But a select doesn't allow the user to select a value that's not in the options, while an autocomplete allows for entering any text, even if it's not in the suggestions.

That's true.
Do you have an idea when you have it finished?

Not sure, but I've already started work on it and it might be done by Friday.

Perfect :-)

Not to rush but i could really use a select component in the coming week. going to use keen-ui on a product.

A Select and Slider component just landed in v0.8.8. Check it out.


Refactor mailer views

The existing mail templates have their CSS inline which is difficult to read/amend. Premailer gem used to extract the css to a separate file.

thanks @axemonkey  - the premailer gem converts the separate CSS to be inline by preprocessing the template. Its a nice way of making the css/html easier to read for devs but still producing the inline CSS


Something different between my practice and README

I tried to register and unregister EventBus in a subscriber Activity's onStart and onStop as README shows, then posted my event from a publisher Activity (codes are as follows). However, the subscriber didn't receive any event from the publisher, until I set sticky = true in the annotation @Subscribe and called EventBus.getDefault().postSticky() in publisher.
Moreover, I tried registering and unregistering EventBus in subsciber's onCreate and onDestroy, and ran the code without setting sticky = true or calling EventBus.getDefault().postSticky(), then it worked! The subscriber received an event from the publisher. So I wonder if there is something wrong with my practice, or README made a mistake?
//Subsciber Activity
class MainActivity : AppCompatActivity() {
    private val text: TextView by lazy {
        findViewById(R.id.text)
    }
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContentView(R.layout.activity_main)
        text.setOnClickListener {
            startActivity(Intent(this,MyActivity::class.java))
        }
    }

    override fun onStart() {
        super.onStart()
        EventBus.getDefault().register(this)
    }

    @Subscribe(threadMode = ThreadMode.MAIN)
    fun onMessageEvent(message: Message) {
        text.text = message.myMessage
    }

    override fun onStop() {
        super.onStop()
        EventBus.getDefault().unregister(this)
    }
}

//Publisher Activity
class MyActivity : AppCompatActivity() {
    private val button: Button by lazy {
        findViewById(R.id.button)
    }
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContentView(R.layout.activity_my)
        button.setOnClickListener {
            EventBus.getDefault().post(Message("Hello World!"))
            finish()
        }
    }
}

//My event class
data class Message(
        val myMessage: String
)

The activity lifecycle does not work as you expect it does, have a look at https://developer.android.com/guide/components/activities/activity-lifecycle#coordinating-activities


Entry::insert

I'm currently in a position of wanting an Entry::insert (or other bikesheddable name) for when you want to conditionally update a value - inserting a value if there is none and updating it if it exists but is "worse" by some metric. This would be nicely captured with code similar to the following:
let was_updated = match map.entry(key) {
    Entry::Occupied(ref entry) if !new_val.better_than(entry.get()) => false,
    otherwise => { otherwise.upsert(new_val); true },
};

Instead, you have to do:
let was_updated = match map.entry(key) {
    Entry::Occupied(ref entry) if !new_val.better_than(entry.get()) => false,
    Entry::Occupied(entry) => { entry.insert(new_val); true },
    Entry::Vacant(entry) => { entry.insert(new_val); true },
};

Which is redundant. The two insert methods have different signatures but I would imagine that Entry::insert would return an Result<&mut Value, Value> to pass ownership in the case that the entry is occupied (or maybe a CowMut if that was to exist).

can this not be done with something like the following?
let was_updated = match map.entry(key) {
    Entry::Occupied(ref entry) if !new_val.better_than(entry.get()) => false,
    (entry) _ => { entry.insert(new_val); true }
};

If it cannot be done, then this could be a good solution

The insert calls have different type signatures, so although I don't know what the (entry) _ syntax is it wouldn't work either way.

Sounds reasonable. User can fix it locally in the mean time:
use std::collections::hash_map::Entry;

pub trait InsertExt {
    type Item;
    fn insert(self, item: Self::Item);
}

impl<'a, K, V> InsertExt for Entry<'a, K, V> {
    type Item = V;
    fn insert(self, item: Self::Item) {
        match self {
            Entry::Occupied(mut e) => { e.insert(item); }
            Entry::Vacant(e) => { e.insert(item); }
        }
    }
}

https://crates.io/crates/mucow


Commercial use

Hello console.re team,
I want to use this part of your software in a commercial product.
Since your license states that it is only for non commercial use i ask for some kind of agreement so that it is possible to use the console.re server component without re-implementing it.
Best regards,
Timo****

Yeah, you can use it anyway you want. Just add a link to https://github.com/kurdin/console-remote-server
I'll change to MIT. Good luck.


mac-node-3 not able to compile protobuf

missing autosomething?
CC @jtattermusch @nicolasnoble
https://grpc-testing.appspot.com/job/gRPC_master/15577/config=dbg,language=c++,platform=macos/console

Hm, yeah I'm on it.
It looks like it might be the new https://wiki.jenkins-ci.org/display/JENKINS/pre-scm-buildstep plugin.
autoconf and xbuild are /usr/local/bin   so perhaps the PATH is set incorrectly.

And i've verified that the tools are actually installed properly (by sshing to the workers).

From a job run on jenkins:
PATH=/Users/jenkinsnode2/.nvm/versions/node/v4.2.6/bin:/usr/bin:/bin:/usr/sbin:/sbin
when SSH'd
PATH=Users/jenkinsnode2/.nvm/versions/node/v4.2.6/bin:/usr/local/rvm/gems/ruby-2.1.5/bin:/usr/local/rvm/gems/ruby-2.1.5 @global/bin:/usr/local/rvm/rubies/ruby-2.1.5/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/rvm/bin

This could also be the https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin   that I installed in the morning (but we are not using it, it was a dead end, uninstallation pending)

Ah stupid EnvInject:
[EnvInject] - Loading node environment variables. - despite the plugin not being used anywhere in the project!

Scheduled restart of jenkins master. After the EnvInject plugin is uninstalled, thing shoud be fine.

Jenkins restarted, mac builds seem to be fine again.


Not found 404 while install CNI with scripts/install_cni_plugin.sh

Is this a request for help?:
Yes
Is this an ISSUE or FEATURE REQUEST? (choose one):
Issue
Which release version?:
Latest
Which component (CNI/IPAM/CNM/CNS):
CNI
Which Operating System (Linux/Windows):
LINUX
For Linux: Include Distro and kernel version using "uname -a"
44-Ubuntu SMP Thu Feb 21 14:24:01 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Which Orchestrator and version (e.g. Kubernetes, Docker)
Kubernetes
What happened:
Got 404 while installing loopback cni plugin.
What you expected to happen:

How to reproduce it (as minimally and precisely as possible):
Run bash scripts/install_cni_plugin.sh
Anything else we need to know:
Getting 404 release itself not present this need to be fixed. Not able to use the CNI.
--2019-08-28 17:29:35--  https://github.com/containernetworking/cni/releases/download/0.4.0/cni-amd64-0.4.0.tgz
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found```

Download address is changed to https://github.com/containernetworking/cni/archive/v0.7.1.tar.gz

#418 fixes this.


Documentation update for interface level counters

Based on https://docs.docker.com/articles/runmetrics/#interface-level-counters but scripted/refined and working on Ubuntu 14.04. The main thing needed in the documentation a comment for 14.04 showing the path to the cgroup device is /sys/fs/cgroup/devices/docker/$CID*/tasks instead of /sys/fs/cgroup/devices/$CID*/tasks, but here's a script to show the interface stats in one command.
#!/bin/bash
if [ $# -ne 1 ]; then
  echo "usage: $0 {container_id}"
  exit 1
fi

SHORT_CID=$1
CID=$(docker inspect --format="{{.Id}}" ${SHORT_CID} 2>/dev/null)
if [ $? -ne 0 ]; then
  echo "No container: ${SHORT_CID}"
  echo "Are you running with sudo?"
  exit 2
fi

TASKS=/sys/fs/cgroup/devices/docker/$CID/tasks
PID=$(head -n 1 ${TASKS})
NETNS_PATH=/var/run/netns/${CID}

mkdir -p /var/run/netns
ln -sf /proc/$PID/ns/net ${NETNS_PATH}
ip netns exec ${CID} netstat -i

unlink ${NETNS_PATH}

I think this can be closed, because https://github.com/docker/docker/pull/15885 was merged


4.x: Upgrade Jersey to 3.1.1

Upgrade Jersey:

Upgrade to a version that supports Jakarta 10 (requires #5815)
Add JAX-RS TCK to our set of TCK tests to make sure Helidon is compliant (if feasible)

TCKs are passing when I exclude the tests that deploy war files, and the signature test.
The problem is that these tcks are not published in maven. Jersey is taking them from this URL:
wget -q https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl/jakarta-restful-ws-tck-3.1.1.zip -O jakarta-restful-ws-tck-3.1.1.zip
@tomas-langer  question: Do we make TCKs to be published in maven repo, or do I make similar approach than Jersey with a maven plugin?.

Let's wait for the TCK to be available in Maven central (unless they already are).
For certification purposes, we will add a separate job to use the proper TCK zip file.

@jbescos could you please upgrade Jersey to 3.1.1?

Let's wait for the TCK to be available in Maven central (unless they already are). For certification purposes, we will add a separate job to use the proper TCK zip file.

I have more information about this topic.
The jars cannot be published in Maven central because of a license issue, and this is not going to be fixed in EE10.
The bundle (the zip file containing the jars) can be published. I guess this is the only option we have right now, unless we want to wait for EE11.


✨ add device info

In this PR

[x] add get device info, closes #11

Get device  details from Wappsto using device id.
This is based on #14 and must be merged and this branch must be rebased, so that commit history will match.
TODO

[ ] add login
[ ] add get device entities
[ ] add get entity states
[ ] add update entity state if allowed

This will be moved to new branch


Write Script that calculates focus from focus-sequence images

Last night I added an rts2 python script that initiates the focus shifting. You can find it here. Eventually we will put the focus calculator in here as well.
you can test this script by associating it with a target in rts2 like:
rts2-target -c C0 -s "exe /home/rts2obs/ARTN/scripts/shiftfocusing.py" <targetid>

or by running it with rts2-scriptexec:
rts2-scriptexec -d C0 -s "exe /home/rts2obs/ARTN/scripts/shiftfocusing.py"

and the shiftfocus will be done wherever the telescope is in the sky currently.
Right now the file is written to shiftfoc__.fits, which isn't great because it will overwrite each time. I will try to fix this.

Tonight rts2 changed the focus away from the value of 2300 we had determined by hand, winding up around 2480. I think it may be trying to run an autofocusing routine, and I don't know how to enable/disable that. I didn't catch this for a long time and suspect a lot of the data is out of focus.

To turn off focus run set the shiftfocus value in rts2-mon C0 to false. Though you should never have to do this, it should be done automatically.
It may have become confused because we changed it with the xephem gui.
Another possibility is that I am confused about the focuser settings on RTS2. There are 5, they are written below with their RTS2 descriptions:

FOC_POS  -> focuser postion
FOC_TAR  -> focus target position
FOC_DEF -> default target value
FOC_FOFF -> offset from focusing routine
FOC_TOFF -> Temprorary offset for focusing

I think I move the FOCUS_TAR when I do the focusing script. Maybe this is wrong.

Quick update.  I think we want a 1) a good starting value and 2) a good map for seeing how the focus changes with telescope position and temperature.
I think we have this information now.

Based on Betsy's email here: Betsy email
We can set the initial focus to 2400, or something close, before our initial focus run?

Go to:CSS_info
This shou.d have the CSS-derived focus map on the sky, and info on how the focus changes with temp.

We are now using T.E. Pickerings focus analysis script which works if there are enough stars on the CCD (5-10). We should come up with some focus fields that will assure we get enough stars at whatever exposure time we deem necessary.


Add coverage reporting. Fixes #114. r=jsantell

@jsantell it's for real this time

Changes Unknown when pulling 071563a3682916aec54a3b0f7af0b68d8bacf3e5 on linclark:coveralls into ** on mozilla:master**.

Looks good! Only change I'd say is using explicit versions for the dependencies (we don't yet have a good dependency upgrade story, so this will make those deps atleast consistent with the others)

We should land this, yes?

Changes Unknown when pulling 411e3c7baef5aa43677e120b06a0313c889ed493 on linclark:coveralls into ** on mozilla:master**.

Changes Unknown when pulling 411e3c7baef5aa43677e120b06a0313c889ed493 on linclark:coveralls into ** on mozilla:master**.

I updated the PR to pin the dependencies. We may want to consider greenkeeper for dependency updates. I created #149 to discuss this.
Do we like the comments that coveralls is posting here? If not, I can disable them.

I like 'em.

Same! I guess we can merge this and deal with the account setup/hooks? Right now they're just on your branch, Lin, yeah? Should add a badge to README.md once we have that wired up!

I'm pretty sure that it will work on all Travis CI builds once it's merged. If it doesn't I'll look into it after the merge.

Merging.

@linclark oh nice! I thought it would've needed some account or something to set up, but this looks pretty great really, especially with the codecoverage diffing: https://github.com/mozilla/tofino/pull/150#issuecomment-211108380


Rename repository

The name biz-model_pm feels a little awkward to me. I vote for BMWG instead.
What does everyone else think?

Changed the name to try it on for size!

Closing since this change was finalized, no further action necessary. If you have an idea for a new name, please propose a new issue!


Fix Menu bar UI

PR Fixes:
-fix Menu bar UI
Resolves #1219
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I assure there is no similar/duplicate pull request regarding same issue

Thank you


Module Route with middleware auth not works

Hello, first of all thank you for your works!
I'm using your module, but i think to have find a problem. Default routes of module (web.php) is:
Route::group(array('module' => 'Test', 'middleware' => ['web'], 'namespace' => 'App\Modules\Test\Controllers'), function() {
 //list of my routes, for example
 Route::get('/test', 'TestController@testIndex');
});

If i would like to protect my routes by middleware, i should change Route::group like that:
Route::group(array('module' => 'Test', 'middleware' => ['**auth**'], 'namespace' => 'App\Modules\Test\Controllers'), function() {
 //list of my routes, for example
 Route::get('/test', 'TestController@testIndex');
});

If i change Route::group like example above when i try to go to "/test", i will be redirect to "/". My suspicion is that auth middleware are not loaded in right way inside module, maybe for different namespace?
The only way i finded to workaround, is to edit routes.php of project (not of module!) adding inside Route::group(['middleware' => ['auth']], function() {
[...]
Route::get('/test', '\App\Modules\Test\Controllers\TestController@testIndex'); [...]
This is no a really useful way to solve the problem. What i can do to solve that problem in web.php of module, istead of edit main Route file?
Best Regards,
Simone

After about 2 hours of test and debug i think i found solution. This code inside web.php of module works like a charms:
Route::group(['middleware' => ['auth'], 'namespace' => 'App\Modules\Test\Controllers'], function() {     /* Test Module */     Route::get('/test', 'TestController@testIndex'); });
The only difference seems to be the use of [ ] instead of array()... Anyhow, now seem to be solved.

I have no idea if the **auth** is what you really typed into your code or just the mark down. If so, this could be the problem.
I'll check this issue with the following code in a few hours.
Route::group(array('module' => 'Test', 'middleware' => ['web', 'auth'], 'namespace' => 'App\Modules\Test\Controllers'), function() {
 //list of my routes, for example
 Route::get('/test', 'TestController@testIndex');
});

please make sure, you have not defined this route somewhere else without the middleware.
F.A. the route Route::resource('screen_colors', 'ScreenColorsController');
I think i should remove the resourceful api route from the generator.

I have not define route any where, my route in module/screencolors/route/web.php
Route::resource('screen_colors', 'ScreenColorsController');

could you post the api route of your screen_colors module?

closing due to inactivity


PointNet implementation

Hi, a PointNet-based network that processes each point in the masked 3D point cloud to a geometric feature embedding, said in the paper. But in the code implementation only convolution and ReLU of point cloud x in network.py. No spacial transform networks(STN) and maxpooling operation on point cloud. These are the two most important features of PointNet.
` Class PoseNetFeat (nn. Module):
def init(self, num_points):
super(PoseNetFeat, self).init()
self.conv1 = torch.nn.Conv1d(3, 64, 1)
self.conv2 = torch.nn.Conv1d(64, 128, 1)
    self.e_conv1 = torch.nn.Conv1d(32, 64, 1)
    self.e_conv2 = torch.nn.Conv1d(64, 128, 1)

    self.conv5 = torch.nn.Conv1d(256, 512, 1)
    self.conv6 = torch.nn.Conv1d(512, 1024, 1)

    self.ap1 = torch.nn.AvgPool1d(num_points)
    self.num_points = num_points
def forward(self, x, emb):
    x = F.relu(self.conv1(x))
    emb = F.relu(self.e_conv1(emb))
    pointfeat_1 = torch.cat((x, emb), dim=1)

    x = F.relu(self.conv2(x))
    emb = F.relu(self.e_conv2(emb))
    pointfeat_2 = torch.cat((x, emb), dim=1)

    x = F.relu(self.conv5(pointfeat_2))
    x = F.relu(self.conv6(x))

    ap_x = self.ap1(x)

    ap_x = ap_x.view(-1, 1024, 1).repeat(1, 1, self.num_points)
    return torch.cat([pointfeat_1, pointfeat_2, ap_x], 1) #128 + 256 + 1024`

I am confused. Would you explain this to me?
Thanks in advance.

Hi,
(1) Since we are already uncovering the 6DoF pose (rotation and translation) of the target object, we don't need the STN to rotate the input pointcloud which might disturb the pose estimation process.
(2) Maxpooling will lead to poor training efficiency of the CNN-based encoder-decoder network since it's skipping too many pixel embeddings during the Max-pool step.

Thank you for your reply. And what about scale-awareness like PointSIFT or sampling&grouping like PoseNet++? Do you think it will be helpful for pointcloud processing? Looking forward to your suggestions.

Ya, PointNet++ might worth a try.

Thanks.

Hi, a PointNet-based network that processes each point in the masked 3D point cloud to a geometric feature embedding, said in the paper. But in the code implementation only convolution and ReLU of point cloud x in network.py. No spacial transform networks(STN) and maxpooling operation on point cloud. These are the two most important features of PointNet.
` Class PoseNetFeat (nn. Module):
def init(self, num_points):
super(PoseNetFeat, self).init()
self.conv1 = torch.nn.Conv1d(3, 64, 1)
self.conv2 = torch.nn.Conv1d(64, 128, 1)
    self.e_conv1 = torch.nn.Conv1d(32, 64, 1)
    self.e_conv2 = torch.nn.Conv1d(64, 128, 1)

    self.conv5 = torch.nn.Conv1d(256, 512, 1)
    self.conv6 = torch.nn.Conv1d(512, 1024, 1)

    self.ap1 = torch.nn.AvgPool1d(num_points)
    self.num_points = num_points
def forward(self, x, emb):
    x = F.relu(self.conv1(x))
    emb = F.relu(self.e_conv1(emb))
    pointfeat_1 = torch.cat((x, emb), dim=1)

    x = F.relu(self.conv2(x))
    emb = F.relu(self.e_conv2(emb))
    pointfeat_2 = torch.cat((x, emb), dim=1)

    x = F.relu(self.conv5(pointfeat_2))
    x = F.relu(self.conv6(x))

    ap_x = self.ap1(x)

    ap_x = ap_x.view(-1, 1024, 1).repeat(1, 1, self.num_points)
    return torch.cat([pointfeat_1, pointfeat_2, ap_x], 1) #128 + 256 + 1024`

I am confused. Would you explain this to me?
Thanks in advance.

I have some related question about this part.

I'm confused in this code which variable represents color embeddings and geometry embeddings??
I understood pointfeat_1(pixel), pointfeat_2(color and geometry embeding_space), ap_x(global_feature). Is is right?

Would you explain about this part??
Thanks.

though STN and symmetry function like max pooling are the key idea of PointNet, cause they are the operation to deal with the  problem of pointcloud data , otherwise the whole architecture is actually not so "PointNet" ...


slice: IndexError: stop index must be greater than startindex for slice

>>> len(models.SpeechAct.objects)
259

>>> models.SpeechAct.objects[0]
<SpeechAct: # onedirectionatheat You will  ...>

>>> models.SpeechAct.objects[10:11]
[<SpeechAct: 2 . ...>]

>>> models.SpeechAct.objects[100:101]
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/mongoengine/queryset.py", line 1615, in __repr__
    data = list(self[self._skip:limit])
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/mongoengine/queryset.py", line 1028, in __getitem__
    raise err
IndexError: stop index must be greater than startindex for slice slice(100, 21, None)

Thanks for the code - now fixed in dev


Fix/swift evolution keys

Description
The following is a list of the changes applied to the Swift Evolution extension by @BProg:

Migrated to the new Raycast API version.
Fix a typo in the package.json.
Fix React warnings about list items without keys in map loop.
Fix issue when the Swift version is not specified.
Used cached state to remember if you use simple or detail list last time a user opened the command.
Add standard keyboard shortcuts to open in browser and copy proposal URL.

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi @dehesa 👋
It works as expected and it's some nice enhancements, @BProg do you want to check it before merging?

Let me take a look

Works great 🚀
however I found another place where there are duplicate items:
13:52:08.885 Warning: Encountered two children with the same key, `https://github.com/apple/swift/pull/62652`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version.

I could fix this separately

You can use make a suggestion in the code @BProg 🙂

I am not sure whether you can directly push to this branch, but if you can feel free to do it. If not, you can do as @pernielsentikaer suggests and leave me some comments. I will then write them right away.

@dehesa following method needs an update
New implementation for getImplementations from the domain.ts file
function getImplementations(proposal: ProposalJson): { title: string; url: string }[] {
  const implementations = proposal.implementation ?? [];
  const initialValue: { title: string; url: string }[] = [];
  return implementations
    .reduce((accumulator, x) => {
      const mapped = {
        title: `${x.repository}#${x.id}`,
        url: `https://github.com/${x.account}/${x.repository}/${x.type}/${x.id}`,
      }
      // Ignore duplications
      if (accumulator.find(impl => impl.url == mapped.url)) {
        return accumulator
      }
      return accumulator.concat(mapped);
    }, initialValue)
}

Done! We are done @pernielsentikaer !
By the way, @BProg, it would be amazing to add ⌘+P filter for the status of the proposals (i.e. accepted, returned, implemented, etc.) if you have some time. Bonus points if we can filter for Swift version implementations. Sadly, my TypeScript/React knowledge is not that great.

@dehesa The existing search is looking at status and swift version as well. It may not be very intuitive, I do like your suggestion, would look at it 👍🏽
Existing search functionality:


[BEAM-2530] Upgrade maven plugins to the latest versions

This is part of the ongoing work to support java 9
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

This upgrade was done in particular to include the recent support for Java 9 added to the enforcer and javadoc plugins.

R: @jbonofre

Upgrade is just for better Java 9 support ?

Changes Unknown when pulling eeb9fcf861afe5ada312ad47d0659c88f5bea6f7 on iemejia:BEAM-2530-java9 into ** on apache:master**.

Retest this please

Changes Unknown when pulling eeb9fcf861afe5ada312ad47d0659c88f5bea6f7 on iemejia:BEAM-2530-java9 into ** on apache:master**.

@jbonofre yes, this solves some issues with Java 9 (not all of them, this probably will take months since other plugins are broken + also we need to fix more issues before this). This PR also fixes another issue I found with the starter archetype that was not inheriting the versions of the plugins correctly..


Enforce absolute url for SS_BASE_URL

At the moment bad things happen near-silently if you don't specify a FQN for SS_BASE_URL.
E.g. SS_BASE_URL=www.mysite.com is not incorrectly determined to be the FQN, and the baseurl becomes http://www.mysite.com/www.mysite.com. Minimal validation of the URL in constants.php would prevent this.
Valid urls:
SS_BASE_URL=http://www.mysite.com

SS_BASE_URL=//www.mysite.com

SS_BASE_URL=//www.mysite.com/sub.directory

Invalid urls:
SS_BASE_URL=ambiguously.could.be.domain.or.subdirectory

I think the sensible thing to do here is throw a Notice and assume // - that will at least not-break things and developers should pick up on the Notice. Also documentation (of course)

The confusion here is that BASE_URL used to be for a base directory and could optionally be used for a full URL, but now we're doing it "properly" and expecting full URLs.
Throwing some kind of notice, warning, or error for malformed URLs would be good

How is this critical? Hasn't this existed since the dawn of time in SS3? :D

SS_BASE_URL replaces _FILE_TO_URL_MAPPING, so yes if you used a non-absolute-url in _FILE_TO_URL_MAPPING it would be the same issue.

OK, removing from milestone then.

I never said it wasn't critical; People may have known the original url was absolute, but not know this new variable should be. It's also not a 1-for-1 replacement; We use SS_BASE_URL for non-CLI where the old variable was CLI-only. We are running the risk (and have demonstrated with several examples) that people are deploying sites in broken states that break and have no obvious remedy.

OK, you didn't explain the criticality very well then ;) I assume this is a trivial fix: Make usage clearer in upgrade guide and dev docs, add a one-liner to check domain format somewhere. Please let me know if it's any more work than this.

Sorry, I should have referred back to my previous statement.

SS_BASE_URL=www.mysite.com is not incorrectly determined to be the FQN, and the baseurl becomes http://www.mysite.com/www.mysite.com.

The fact that this happens silently is what makes this critical.


Adds 'spo site add' owners option for CommunicationSite creation. Partically solves #1734

The --owners option is mandatory for site creation of type CommunicationSite
when using Azure AD application permissions and this PR enables that.
The creation of the team site spo site add using Azure AD application permissions currently throws error 'Insufficient privileges to complete the operation.'. As a workaround, the aad o365group add command can be used instead, followed by spo site set to further set the properties on the Team site.
This PR adds Remarks to address the Teams site creation issue. I will later reply into #1734 with more details how the workaround can be applied.

Coverage remained the same at 100.0% when pulling 57ff70fa20a5da86ac661e93d81e3068f3e59e7d on VelinGeorgiev:appperm-siteadd-fix into 0d730dbdd2ddff7d90e039a9d8ab56a87de7a794 on pnp:master.


SQL queries omitting the keyword AS for aliases result in error

Whereas MySQL and MariaDB do not require using the keyword AS for aliases, ontop returns an error, when an alias is not introduced by AS
Description
Ontop returns the error:
java.lang.RuntimeException: it.unibz.inf.ontop.exception.InvalidMappingSourceQueriesException: The placeholder(s) xxx in the target do(es) not occur in source query of the mapping assertion

Steps to Reproduce
make a simple R2RML mapping like
<#topbib_map> a rr:TriplesMap;
rr:logicalTable [rr:sqlQuery """
SELECT objects_id, table_id id
FROM objects
""";];
rr:subjectMap [
rr:template "https://example.com/#id" ;
rr:class http://www.w3.org/2004/02/skos/core#Concept;
].
Expected behavior: Ontop understands that id is an alias for object_id
Actual behavior: error: The placeholder(s) id in the target do(es) not occur in source query of the mapping assertion
Reproduces how often: always
Versions
Ontop 5.1.0, MariaDB 10.4.28

Hi,
You need to enclose the column in {} in the template:
rr:template "https://example.com/#{id}" ;

I am really sorry; I have complex mappings that fail in ontop unless I add " AS " before aliases. But I cannot yet reproduce this error using simpler mappings as an example.

Any update how to resolve the Alias AS invalid mapping issue, the parsing is not able to suffice to create mapping / RDF. In case of mapping creation used force to create file but when operating to create RDF it's getting failed.

Could you please give us an example of a failing mapping entry?

Falling mapping entry is below (database is postgres):-
Problem location: source query of triplesMap [id: MAPPING-ID28 target atoms: triple(s, p, o) with s/RDF(http://www.w3.org/ns/r2rml/dcim_interface/id={}(TmpToTEXT(dcim_interface_id)),IRI), p/<http://www.w3.org/ns/r2rml/dcim_interface#ref-bridge_id>, o/RDF(http://www.w3.org/ns/r2rml/dcim_interface/id={}(TmpToTEXT(dcim_interface_id)),IRI) source query: SELECT "dcim_interface"."id" AS "dcim_interface_id", "dcim_interface"."id" AS "dcim_interface_id" FROM "dcim_interface", "dcim_interface" WHERE "dcim_interface"."bridge_id" = "dcim_interface"."id"]
Attaching log file as well for detail stacking.
log.log

Why is "dcim_interface" repeated twice in the following?
SELECT "dcim_interface"."id" AS "dcim_interface_id", "dcim_interface"."id" AS "dcim_interface_id" FROM "dcim_interface", "dcim_interface" WHERE "dcim_interface"."bridge_id" = "dcim_interface"."id"
Is it a self-join? Then one should use something along the lines of
SELECT "parent"."id" AS "bridge_dcim_interface_id", "child"."id" AS "dcim_interface_id" FROM "dcim_interface" "parent", "dcim_interface" "child" WHERE "child."bridge_id" = "parent"."id"

Okay i see, wired but this is getting generated while creating the operation bootstrap within the .obda file. Attaching the file. Renaming not able to upload.
obda_file.txt
ontology_file.txt

Should be fixed by now. Thanks for reporting!


Run cypress tests in github actions, running up front-end and back-end http servers.

Run cypress tests in github actions, running up front-end and back-end http servers.
Hi, i would like to run cypress tests on my Vue project linked to cypress dashboard in Github actions, triggered on push or pull events.
To test my application, wich is written on NodeJS at the backend and Vue in the frontend, i have to run both https server in the github workflow.
I am using cypress-io/github-action and it worked fine without running the backend server. This was my configuration:
name: End-to-end tests
on: [push]
jobs:
  cypress-run:
    runs-on: windows-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v1

      - name: Cypress run
        uses: cypress-io/github-action@v1
        with:
          record: true
          start: npm run serve --prefix frontend/app
          wait-on: http://localhost:8080
        env:
          CYPRESS_RECORD_KEY: <key>

Now the goal is to have also a running server using:
npm run start # --> node index.js
So that i can get backend api listening on localhost:8000 (and vue in dev mode is refering to).
But i can not get that to work. I have tried various configuration like this:
name: End-to-end tests
on: [push]
jobs:
 cypress-run:
   runs-on: windows-latest
   steps:
     - name: Checkout
       uses: actions/checkout@v1

     - name: Run backend
       uses: actions/setup-node@v1
       with:
         node-version: ${{ matrix.node-version }}
         run: npm run start

     - name: Cypress run
       uses: cypress-io/github-action@v1
       with:
         record: true
         start: npm run serve --prefix frontend/nix-app
         wait-on: http://localhost:8080
       env:
         # pass the Dashboard record key as an environment variable
         CYPRESS_RECORD_KEY: <key>

The backend server runs correctly on port 8000, but then the workflow is stuck there! It doesn't continue on Cypress run because, i guess, it's waiting the end of the process.
How can i force to go at the next step after the first server is set up?
Another solution that i have tried is to use two different jobs in parallel, but also this is not working because the two servers will not stop running. Then what if cypress tests run before the two servers are up?
Can you suggest something else? Thank you!

@alessandroAmedei I was going to open an issue asking for multiple https://github.com/cypress-io/github-action#wait-on keys, is this what you are also asking for?

@alessandroAmedei dunno if its just a typo but you said your backend is running correctly on port 8000 but your ci setup is waiting on port 8080

@alessandroAmedei dunno if its just a typo but you said your backend is running correctly on port 8000 but your ci setup is waiting on port 8080

No, 'npm run start' runs the application on port 8000 because my Express app is running there. I found another solution. I think Github actions is really confusing and there is not clear documentation.

@alessandroAmedei would you please share what solution you used? I would also like to run both the node.js backend and the frontend in GitHub actions, thanks.

@davidpodhola also trying to figure this out right now.
This may be of help but doesn't use the Cypress action:
https://medium.com/tomorrowapp/running-end-to-end-tests-with-github-actions-d45b70c032e6

Similar to #152


FV - Exercise finished

New pages
/subscribe.html => form
/subscribers => mailing list of people registered on form


Update cats-effect-testing-specs2 to 0.5.1

Updates com.codecommit:cats-effect-testing-specs2 from 0.4.2 to 0.5.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.codecommit", artifactId = "cats-effect-testing-specs2" } ]

labels: test-library-update, semver-minor

Superseded by #405.

Superseded by #405.


Connect React's Review Component to Express API

Goal
Integrate the Reviews API into React. Don't start until the pull request #19 is approved. Ask Mars for a FAUNA_SECRET, then add an additional entry to api/.env (FAUNA_SECRET=). I recommend you play around with the endpoints in Postman. Make some dummy data first and get familiar with the endpoints.
Fauna extension: https://docs.fauna.com/fauna/current/integrations/vs_code.html
Get Review

Endpoint URL: /reviews
Method: GET
Query: to filter reviews, use one of the below query parameters. To get all reviews, do not provide any query parameters.

courseID: String
professorID: String
userID: String

[ ] Replace dummy data with data from our database using the get review endpoint.

Post Review

Endpoint URL: /reviews
Method: POST
Body: key names must be the same
{
professorID: String
courseID: String
userID: String
reviewContent: String
rating: Float
difficulty: Float
timestamp: String
gradeReceived: String
forCredit: Boolean
score: Int
}
[ ] When user submits review form in client, send fetch request to update database using the post review endpoint.

Vote Review

Enpoint URL: /reviews/vote
Method: PATCH
Body:
{
id: String // a review's id is included in the get review endpoint
upvote: Boolean // true if is an upvote request, false if is a downvote request
}
[ ] When user upvotes or downvotes a review, update the database using the vote review endpoint.

The CSS/color scheme only accounts for integers 1-5 right now, so I'm going to change it to apply to decimals and number greater than 5 by doing:
- flooring decimal numbers
- having the same colors for intervals of 2 (1 and 2 will have the same color, 3 and 4, ... all the way to 9 and 10)
Let me know if the design team has any specific way they want it done!

I used professorID for the "Taken With" and right now "Quarter Taken" is blank

Also for the POST request, do you want me to make the review form component first and then call the request from that component?

The CSS/color scheme only accounts for integers 1-5 right now, so I'm going to change it to apply to decimals and number greater than 5 by doing:

flooring decimal numbers
having the same colors for intervals of 2 (1 and 2 will have the same color, 3 and 4, ... all the way to 9 and 10)

Let me know if the design team has any specific way they want it done!

These design decisions sound good to me! We can go through with this for now.

I used professorID for the "Taken With" and right now "Quarter Taken" is blank

That's my bad. I'll try to add a quarter taken field soon.

Also for the POST request, do you want me to make the review form component first and then call the request from that component?

Yes, make a form component first, and then make the request when the user submits the data.

I used professorID for the "Taken With" and right now "Quarter Taken" is blank

That's my bad. I'll try to add a quarter taken field soon.
Edit: just updated the schema to include a 'quarter' field. The code is updated in the master branch.

Ok just saw the edit, thank you!


promtool check rules no longer identifies invalid fields as of 2.16.0

What did you do?
We use promtool check rules with Prometheus 2.16.0 in our CI to validate our Prometheus alerts. We recently had a misconfiguration where an annotation had incorrect indentation, making it an illegal field of the rule rather than an annotation.
What did you expect to see?
Promtool should through an error field foo not found in type rulefmt.Rule as it does in Prometheus 2.15.2
What did you see instead? Under which circumstances?
Promtool succeeded.
Repro steps
➜  cat << EOF | docker run --entrypoint promtool -i prom/prometheus:v2.15.2 check rules /dev/stdin
groups:
- name: group
  rules:
  - alert: alert
    expr: expr
    labels:
      key: value
    foo: bar
EOF
  FAILED:
/dev/stdin: yaml: unmarshal errors:
  line 8: field foo not found in type rulefmt.Rule
Checking /dev/stdin

➜  cat << EOF | docker run --entrypoint promtool -i prom/prometheus:v2.16.0 check rules /dev/stdin
groups:
- name: group
  rules:
  - alert: alert
    expr: expr
    labels:
      key: value
    foo: bar
EOF
Checking /dev/stdin
  SUCCESS: 1 rules found

Thanks. Probably related to #6533

cc @Harkishen-Singh FYI

Will take this up. Thank for reporting @jutley. @roidelapluie


Add model to TH sample

Without model it looks like the TH isn't doing anything other than changing asp-for into for.
This is not meant to be a clean up, just need to fix this problem.
review url

@Rick-Anderson Please review my PR for proposed changes.