How to handle labels found in corpus but not in supplied label parameter?

Since implementing #169 which deals with #167 I have the following situation I'd like some help designing the API for:
How do we handle the case where the Corpus contains a set of labels say for example {"a", "b", "c"} and then someone decides to construct a Corpus with a labels parameter containing only {"a", "b"}?
Do we want to supply some sort of message to the user that there are labels found in the corpus that were not in the the supplied label parameter? (for example: label "c" found in corpus but not in provided labels). Should the labels parameter act as some sort of a filter on the corpus or not?  Or do we want to do something else entirely?
I'd appreciate some advice on how this case should be handled

Quoting from a paper reporting on early tests with Yongning Na (section 4.1):

Data preparation offered a chance to check that all the data conformed to the phonological description. At data conversion from XML to plain text, a list of segments was produced, and compared with the list of sounds provided for the language (by the second author). This comparison brought out a handful of inconsistencies in the notation, such as the use of /ẽ/ for an interjection appearing in some of the texts. This prompted a return to the data, which revealed that these were in fact instances of ‘yes’ (canonical transcription: /ĩ/) that had been transcribed before the second author identified the nature of this morpheme. Systematic examination of the passages at issue revealed that this /ẽ/ was in most cases a response to a comment or yes/no question on the part of someone in the audience, confirming the interpretation of this morpheme as a sign of approval.

@alexis-michaud  thanks for this, it shows that clear and immediate feedback on data discrepancies is important, so we will make sure to address this.

Yes, clear and immediate feedback on data discrepancies will be great. This relates to preprocessing: the feedback could be used as an early-stage 'diagnosis' of how much preprocessing remains to be done on the corpus before Persephone can be applied with best results.
In addition to the issue of transcriptional inconsistencies, there is the issue of code-switching. In principle, preprocessing needs to be done before using a corpus as input to Persephone, so that the input contains only data from one language. But I guess that in many (most?) corpora there will remain some words (or even entire sentences) in other languages, due to code-switching: in fieldwork, the investigator & the consultant often share a contact language that is native to neither of them (typically the national language: for instance, English or Chinese or Arabic or Portuguese) and they may talk in that language during part of the recordings. If this has not been properly encoded in the transcription files (as language information inside the XML tag for a given chunk of transcription: lang="cmn" or the like) and taken into account at preprocessing, it will make trouble for training an acoustic model.
This is a situation where interdisciplinary collaboration matters, because these cases, once spotted, are easy for the corpus author to explain (for her, it goes without saying, that's why she may not realize that it needs to be encoded as logical text) whereas they are hard for people who don't know the languages at issue. Each data set has its own context, and if sufficient information is not provided and neatly encoded, it can be excruciatingly hard for users to 'reconstruct' later.
For instance, in the Japhug corpus (transcribed in International Phonetic Alphabet), some Chinese loanwords are transcribed with Chinese characters, thus:

tɕe ɯ-me nɯnɯ andi xiaoshuigou 小水沟 kɯre tha-zmɤrʑaβ-nɯ tɕe, nɯre thɯ-ɣe

There is an implicit convention that is clear to someone who knows Chinese: the author, Guillaume Jacques @rgyalrong, provided a transcription of the loan in Standard Mandarin romanization, xiaoshuigou, followed by the transcription in Chinese characters, 小水沟. Something needs to be done about this so that the data can serve as input to Persephone: simply excluding sentences containing such loans from the training corpus, or maybe converting the transcription of loanwords to IPA.
(The latter solution would be the most interesting thing to do linguistically, as it would add value to the transcription: speakers of Japhug don't pronounce this word in the usual Southwestern Mandarin way. It would also enrich the acoustic model, which might ultimately succeed in identifying the phonetic form of loanwords with high accuracy, too. And it would be good to choose the way to go as early as possible, because such adjustments are time-consuming: in this case it requires making up one's mind about the best way to transcribe the consultant's Chinese pronunciation, and this is a non-trivial linguistic issue.)

For now, if a user supplies labels and they are inconsistent with what is automatically raised, an exception is thrown. This is specifically for Corpus.init() constructor, which assumes user supplied data is already preprocessed. Therefore the only function the labels argument to this constructor serves is to ensure that what is automatically found is consistent with user's expectations.
For filtering, that is handled via LabelSegmenter's to other corpus constructors. For example, from_elan() will not expect pre-segemented units, so the behavious there is going to be more sophisticated.


🎁: Enhance the workflow design to be more aesthetically pleasing

Expected outcome

the improvements we want for readability in the workflow.

REMOVED - hide previous steps
REMOVED - Two steps before current step are shown.
NOTE: You can keep the description all on one line, as we currently have, we have shortened the workflow texts
text for functional roles should be smaller / can be a different font to break up the workflow
There is some space between each workflow step
enable the text from the sidesheet to be a bit wider, then there are fewer lines of text

looks good :) - go for push - i think you stull cant drag the workflow steps, but i guess thats being handled somewhere else?

PR: https://github.com/equinor/lighthouse-client/pull/1788


How to get destination address for https://api.ng.bluemix.net

Actually i am giving destination address like as below can you help how to get destination address
abacus.json
[
{"protocol":"all","destination":"<IP_ADDRESS>"}
]
command:
cf create-security-group abacus abacus_group.json
error:
Server error, status code: 403, error code: 10003, message: You are not authorized to perform the requested action

Run the following command to find application instances IP addresses
CF_TRACE=true cf app <APP_NAME>

BTW, I see that you are getting 403 - Forbidden when trying to create a security group. If you are working on bluemix environment, you should be able to skip creating security groups and use public routes to get the applications talk to each other.

@naveensf are you still having issues with this? Did @sasrin's answer help?

Will close this issue sometime tomorrow unless there's an update. We can always reopen it later if needed.

No update so assuming there is no issue at this point. Please reopen if this is still a valid issue.


helm: support configurable service port

this allows users to use customized port.
Fixes #1613

Sorry for the inconvenience, but the prometheus-operator and kube-prometheus helm charts are currently being migrated to the upstream stable helm charts. Because of this we are currently not accepting any pull requests. We apologize for the inconvenience, but this is necessary for the migration to actually happen. We announced this here: https://github.com/coreos/prometheus-operator/tree/master/helm#warning
You can view the progress and help here and here.
Thank you for your understanding! :slightly_smiling_face:


[WIP] chore(logspout): upgrade logspout

Fixes #4292 #4293
This WIP PR uses upstream logspout v3 (without forking it!) along with a deis adapter module.
When merged, this addresses many recent, notable log issues related to discovery, deadlock, Kubernetes, and more.  Some (not all) of these issues have also been fixed in our ancient fork of logspout, but the point is I have attempted to keep this PR in feature / fix parity with what currently exists.
Why is this WIP?

Release of logspout v3 is pending
The plugin still requires unit and functional tests

Ideally, also, it would be good to find a way to keep the adapter code right here in the deis/deis project.  That, however, would require that we deviate from upstream logspout's own documentation on how to produce custom builds that include our own adapter.  This may be worthwhile to figure out since it will mean one less repository to manage, but my early attempts at doing this have resulted in built images that are (somehow) much, much larger than what their documented custom build process produces.  I do intend to solve that.

I've discovered how to produce adequately compact images from a Dockerfile that combines stock logspout with the custom code from this repo.  This eliminates the need to maintain the separate (and very short-lived) deis/logspout-v3-deis repo.  The downside to this build, however, is that it's slow, so I also provide a second, development-optimized build that produces a less compact image, but does so much more quickly.  This seems reasonable to me.
A few unit and functional test are all that stand between this and a review.

Although unit and functional tests are still required, I'm encouraged that this passed integration tests.  :)

This needs a rebase now. See also #2158. :pray:

Accidentally closed the PR.

Unless other maintainers disagree, I don't see this getting done.  Logspout v3 is a blocker for this and has been a long time coming.  Meanwhile, Deis v2 won't use logspout at all.  I can't see this as being something that makes it into a v1.x LTS, not can I see it as being something that makes the leap to V2.


Limitation of Snapshot backup

Case Reference -<PHONE_NUMBER>000055
If DB count is more than 64 , Snapshot backup failed with below error:
Error message:
Msg 925, Level 19, State 1, Line 4
Maximum number of databases used for each query has been exceeded. The maximum allowed is 64.

@perrysk-msft
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

This change has been incorporated into internal PR https://github.com/MicrosoftDocs/sql-docs-pr/pull/26344.
#please-close


WELZ: Watch bubblyhub.in

WELZ requests the watch of the watch_keyword bubblyhub\.in. See the Metasmoke search here and the Stack Exchange search here.

bubblyhub.in has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Coverage remained the same at 65.093% when pulling a5384919ba56b5d7c2c3bcd35a30d0462bcbd300 on auto-blacklist-1519772280.224983 into 21009bbf902698d4e78b1efc90b94d28827aa4cc on master.

!!/approve


Show the source of conflicting dependencies

When dependencies directly conflict, we should show which file we loaded them from.
e.g.
× No solution found when resolving dependencies:
╰─▶ Because you require filelock==1.0.0 and you require filelock==3.8.0, we
    can conclude that the requirements are unsatisfiable.

from compile_constraints_incompatible_version could say
× No solution found when resolving dependencies:
╰─▶ Because you require filelock==1.0.0 (from requirements.txt) and you require filelock==3.8.0 (from constraints.txt), we
    can conclude that the requirements are unsatisfiable.

Originally mentioned at https://github.com/astral-sh/uv/pull/1796/files#r1498258800

@zanieb I need this functionality for for an app installer tool that I'm writing. If you're willing to point out the files and rough line numbers that need to change, I would be happy to contribute a fix for this.


Continuous improvement of nodule classification models (see #2)

Overview
We want to continuously improve the accuracy and reliability of models developed for nodule classification. This is a continuation of #2 and will remain open indefinitely.
Note: Substantive contributions are currently eligible for increased point awards.
Design doc reference:
Jobs to be done > Detect and select > Prediction service
Acceptance criteria

[ ] trained model for classification
[ ] documentation for the trained model (e.g., cross validation performance, data used) and how to re-train it

NOTE: All PRs must follow the standard PR checklist.

Maybe we should proceed in small steps by e.g. first adding evaluation methods that cover most of the metrics introduced in #221 so we can have a more standardized way to determine those metrics? This way we would also be able to quickly determine the quality of the current implementations of the identification, classification and segmentation algorithms. This would in turn make it easier to focus first on the algorithm that is performing the worst so far. Any thoughts @isms @reubano @lamby ?

For folks who are interested, see the latest announcement here:
https://concepttoclinic.drivendata.org/newsfeed
There are a limited number of AWS credits available for folks to continue to make progress on these algorithms.

Thanks @pjbull !
I contacted the DrivenData team and asked for credits. If they can provide me with some, I'd like to work on this issue. Once I get their answer, I'll update this comment with the current state for transparency reasons.

@WGierke, I have create a virtual machine, the support should increase the instances limit anytime soon, and then the machine will be ready for use. Also, I have plenty of time for upcoming week. So, if you have some ideas, we can work together on the issue and share the points and the fun :)
If this sounds good to you, please, contact me on Gitter.


Add ability to configure number of colors in palette

@nanaian I forgot - did you say we already support detecting the number of colors automatically?

@nanaian I forgot - did you say we already support detecting the number of colors automatically?

I'm pretty sure its derived from the size of the segment, yes

Closing unless we deem it necessary


Starting two view animations causes stutter

Describe the bug
When calling animate on the view two times before the first animation finishes, at the start of the second animation the view jumps back a little.
To Reproduce
Steps to reproduce the behavior:

Go to https://codesandbox.io/s/view-animation-stutter-bywqs?file=/main.js
Click on the button multiple times
Notice that the animation is not smooth at the end.

Expected behavior
The second animation should be a noop, instead it jumps back a little and animates to the target again.

I don't think I'm seeing the effect.  I wonder if it doesn't occur in all browsers/os.  I'm using Chrome 94 on macOS 11.5.

I tried in latest Chrome and Firefox, the problem occurs in both.
Click the button multiple time to make it worse.

I see it now.  I missed the "multiple times" part (before waiting for the animation to finish).


Doesn't support intersected Promise types

When trying to integrate with tRPC fromThrowable breaks if the infered return value is not purely a Promise. The query method returns a Promise<T> & { cancel: () => void } as a CancellablePromise, which breaks with:
Argument of type 'CancellablePromise<{ id: string; }>' is not assignable to parameter of type '(...args: any[]) => any'.
  Type 'Promise<{ id: string; }> & { cancel: CancelFn; }' provides no match for the signature '(...args: any[]): any'.

fromThrowable should support insected Promise types when inferring the ReturnType of a given function.

Ah man, I got my own code wrong.
Closing because indeed, intersected Promise types ARE supported.


need example for backward in time integration

In examples/worldwide/OCCA_FlowFields.jl you will find that you can just set backward_in_time=false in the setup function.
https://github.com/JuliaClimate/IndividualDisplacements.jl/blob/7f2ae7b8a07001e41b5e44bc91ffddf0f70a0e82/examples/worldwide/OCCA_FlowFields.jl#L11
Does this work?

Yes, it work well! Here's the plot integrating backward 365 days.

And  the plot integrating forward 365 days.

Great! Thank you


add focusable=false added by iD startup process

Building iD (https://github.com/openstreetmap/iD#building-id) on my computer resulted in changes to svg files.
I have no idea whatever it is result of bug (in that case treat it as a bug report), misconfiguration on my computer (in that case sorry) or desirable change (in that case merging it would help to reduce noise in command line, building program should not cause code to change).

@matkoniecz The font awesome icons are added by a dependency. Make sure you run npm install first to make sure you have the latest version. These files as checked into iD aren't critical since they're autogenerated and will be replaced with the latest versions when releasing.

I followed https://github.com/openstreetmap/iD#building-id and run npm install


How do you display total number of records in a template?

I'm having trouble getting any answers on underscore.js on stackoverflow, so I'm just going to ask here. How do you display the total number of records in a template? In this example, how would I display totalNum?

shouldn't it be
_.each(items,function(item,key,items) { %>
<%- items.length %> of addresses in this search
<% });

For future reference, if your items looks like this:
[{id: 100}, {id: 101}]

Then you can render something for each item and then display the total number of them at the end like this:
<% _.each(items, function(item, index, list) { %>
    <!-- print whatever you want about each `item` here -->
<% }); %>
Total number of items: <%= items.length %>

If you want to tally during iteration to show something like “item 5 of 10”, this will work:
<% _.each(items, function(item, index, list) { %>
    This is item <%= index %> of <%= list.length %>.
<% }); %>

@lschneiderman @spattanaik75


Update f1.py - race_notification_check func added

Original code didn't have a function to check whether or not it was a race day. This was something quickly generated by GPT-4 LLM. Please note: await asyncio.sleep(60) on line 482 has this action performing every minute. Adjust as needed.
Feel free to edit as needed, just figured folks would appreciate this working!

There's already code to support sending a notif for race day, I dont see the point in spamming a reminder every hour.
Also, I will not blindly accept any AI generated code. Specifically when it doesn't know Red and it's inner workings.

Yea async def raceday_loop(self):. I'll close. But an interesting point, your function was never being called. Adjusted as shown and the raceday posts are occuring as intended.

its called every day at midnight UTC

https://github.com/flaree/flare-cogs/blob/master/f1/f1.py#L34
https://github.com/flaree/flare-cogs/blob/master/f1/f1.py#L47

I was on the master branch, I'll switch over to dpy2 and use the original code to test. Thank-you!


Schema generation fails for tuple with ellipsis

Bug
Good day,
Thanks again for this awesome lib!
The issue: pydantic can't generate JSON schema for fields defined as Tuple with ellipsis. Consider the following:
from typing import Tuple
from pydantic import BaseModel

class Foo(BaseModel):
    names: Tuple[str, ...]

print(Foo.schema())

which breaks with:
Traceback (most recent call last):
  File "/tmp/model.py", line 10, in <module>
    print(Foo.schema())
  File "pydantic/main.py", line 431, in pydantic.main.BaseModel.schema
  File "pydantic/schema.py", line 225, in pydantic.schema.model_schema
  File "pydantic/schema.py", line 536, in pydantic.schema.model_process_schema
  File "pydantic/schema.py", line 563, in pydantic.schema.model_type_schema
  File "pydantic/schema.py", line 279, in pydantic.schema.field_schema
  File "pydantic/schema.py", line 502, in pydantic.schema.field_type_schema
AssertionError: Shape.TUPLE_ELLIPS

For bugs/questions:

OS: Ubuntu 16.04, amd64
Python version 3.7.3
Pydantic version 0.28

/cc @tiangolo

Thanks, I'll check it as soon as I get a chance.

This was fixed some time ago, I don't remember in which exact version.
But in the latest (currently v1.5.1) it works as expected, the output is:
{'title': 'Foo', 'type': 'object', 'properties': {'names': {'title': 'Names', 'type': 'array', 'items': {'type': 'string'}}}, 'required': ['names']}


Re-assess nonce encoding in VRF signatures

Description
With https://github.com/spacemeshos/go-spacemesh/pull/3877 nonces were added to VRF signatures. These are currently just added as an 8 byte little endian prefix to the message that is signed before signing (and validation).
We should re-assess how we want to encode this nonce (see also https://github.com/spacemeshos/go-spacemesh/pull/3877#discussion_r1056026113) :

Add it to the message as a field before serializing it with go-scale
using a separate VRFMessage type that has 2 fields: the message to be signed and the nonce before encoding that with go-scale
possibly a different encoding

Both have advantages and disadvantages; using it as a field in the actual message means we can have messages with and without the nonce, and the messages can be validated without first needing to fetch and validate the initial ATX of a node. The second requires less code change and keeps the message objects themselves clean to contain only the data that is relevant for the message itself.
Affected code
signing package and possibly common/types for the objects that are signed with the VRFSigner

cc @countvonzero

Add it to the message as a field before serializing it with go-scale

yes. my preference would be to add nonce to all the VRF messages the node would sign/prove with the vrf signer.
rationale:

having customized encoding for the nonce is not porting friendly when the node is implemented in a different language
it's declarative, so the logic of nonce is not hidden in the signing package.
only one vrf verifier instance is needed per node, not per vrf msg

note that msg size is not an argument for the current impl.
the sender construct a vrf msg, sign with vrf signer (as some eligibility proof of some protocol), and send it as part of a separate message (hare round msg, block proposal, beacon proposal...)
the receiver, when verifying eligibility, reconstructs the expected vrf msg, and verify it with the sender's vrf signature/output and public key.
as such, vrf msg are never sent over the wire. so the size of the vrf msg struct is not a concern. all output of vrf signing has fixed size.

using a separate VRFMessage type that has 2 fields: the message to be signed and the nonce before encoding that with go-scale

note that there was a misunderstanding here. i didn't mean to have the nonce separate from the vrf message, but embedded in.
for example
type beaconVRF struct {
  beacon_eligibility
  nonce
  epoch
}

only one vrf verifier instance is needed per node, not per vrf msg

This is already the case, there is only one instance of the VRF Verifier that is used to verify all signatures against their messages independent of who signed the message.


Got internal server error on web UI

I got internal server error on nipap web UI after upgrade. This the log
[Wed Oct 25 17:20:30.716799 2023] [wsgi:error]  Traceback (most recent call last):
[Wed Oct 25 17:20:30.716823 2023] [wsgi:error]    File "/etc/nipap/www/nipap-www.wsgi", line 7, in
[Wed Oct 25 17:20:30.716827 2023] [wsgi:error]      from nipapwww import create_app
[Wed Oct 25 17:20:30.716837 2023] [wsgi:error]  ImportError: No module named 'nipapwww'
[Wed Oct 25 17:20:30.859976 2023] [wsgi:error]  mod_wsgi (pid=30011): Target WSGI script '/etc/nipap/www/nipap-www.wsgi' cannot be loaded as Python module., referer: https://ipam.te.net.id/
[Wed Oct 25 17:20:30.860010 2023] [wsgi:error]  mod_wsgi (pid=30011): Exception occurred processing WSGI script '/etc/nipap/www/nipap-www.wsgi'., referer: https://ipam.te.net.id/
[Wed Oct 25 17:20:30.860062 2023] [wsgi:error]  Traceback (most recent call last):, referer: https://ipam.te.net.id/
[Wed Oct 25 17:20:30.860079 2023] [wsgi:error]    File "/etc/nipap/www/nipap-www.wsgi", line 7, in , referer: https://ipam.te.net.id/
[Wed Oct 25 17:20:30.860082 2023] [wsgi:error]      from nipapwww import create_app, referer: https://ipam.te.net.id/
[Wed Oct 25 17:20:30.860092 2023] [wsgi:error]  ImportError: No module named 'nipapwww', referer: https://ipam.te.net.id/
is it something wrong with nipapwww?

nipapd and nipap-www is the newest version (0.31.2-1) and i already install libapache2-mod-wsgi-py3.
What a notification?the only notification i got when i ran apt upgrade was the option of generate secret key (automatic or manually)

Okay, that's odd.. I presume you have restarted Apache? If you just start an interactive Python 3 interpreter, can you import nipapwww?
What distribution are you running NIPAP on?

Yes i have restarted apache and nipapd. How to import nipapwww?
I'm running on ubuntu 16.04

Just run python3 in a shell and then import nipapwww.
Ubuntu 16.04 ships with Python 3.5, I haven't tested NIPAP with versions < 3.6. Automated tests are run on Ubuntu 20.04, I've tested manually on 18.04. Would you consider a dist upgrade?

This what i got when tried to import nipapwww on version 3.5 and 3.6
Python 3.5.2 (default, Jan 26 2021, 13:30:48)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.

import nipapwww
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named 'nipapwww'
quit()

Python 3.8.6 (default, Dec  6 2020, 14:28:49)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.

import nipapwww
Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'nipapwww'
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook
from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/init.py", line 5, in
from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in
import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 25, in
from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 23, in
import apt
File "/usr/lib/python3/dist-packages/apt/init.py", line 23, in
import apt_pkg
ModuleNotFoundError: No module named 'apt_pkg'

Original exception was:
Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'nipapwww'
What minimal ubuntu version to run nipap?i have tried install on ubuntu 22.04 got this error
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
nipapd : Depends: nipap-common but it is not going to be installed
Depends: python (>= 2.7) but it is not installable
Depends: python-psycopg2 but it is not installable
Depends: python-flask but it is not installable
Depends: python-flask-xml-rpc but it is not going to be installed
Depends: python-flask-restful but it is not installable
Depends: python-flask-compress but it is not going to be installed
Depends: python-tornado but it is not installable
Depends: python-parsedatetime but it is not installable
Depends: python-tz but it is not installable
Depends: python-dateutil but it is not installable
Depends: python-psutil but it is not installable
Depends: python-pyparsing but it is not installable
Depends: python-jwt but it is not installable
Depends: python-requests but it is not installable
E: Unable to correct problems, you have held broken packages.

same over here...

import nipapwww
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named nipapwww

running ubuntu 20.04.6

Getting the same type of error. Anyone got a fix for this on Ubuntu 20.04?

Hello, my nipap installation on Ubuntu 20.04 gave the same errors, then I've found that it needed libapache2-mod-wsgi-py3 instead of libapache2-mod-wsgi installed.


Add a page highlighting OpenCost in the news

Signed-off-by: Matt Ray<EMAIL_ADDRESS>

@alexkubecost ^^

https://capture.dropbox.com/Jdn6camgjNpD0M0t

Just going off screenshot, but is there any chance we can add simple styling to the page? For example, maybe convert links to be bullet point list?

@dwbrown2 updated to use bullets. It's Markdown rather than React, so the formatting is pretty limited, but I can try to convert it to React + Tailwind if you think it's worthwhile

This works for me, unless @Annalillie has other input!

This is fantastic! I have no additional input here.


Node/RequireJS conflict?

The following snippet results in a "Uncaught AssertionError: path must be a string" (shown in the dev console)
returned from an app running locally on url: http://<IP_ADDRESS>:3000
<!DOCTYPE html>
<html>
<head>
  <meta charset="utf-8">
  <title>Application</title>
  <script src="/static/js/bower_components/requirejs/require.js"></script>
  <script>
  // Configure the AMD module loader
  requirejs.config({
    // The path where your JavaScripts are located
    baseUrl: '/static/js/',
    // Specify the paths of vendor libraries
    paths: {
      jquery: 'bower_components/jquery/dist/jquery',
      underscore: 'bower_components/underscore/underscore',
      backbone: 'bower_components/backbone/backbone'
    },

  require(['jquery', 'backbone'], function($, Backbone) {
    $("body").append("hello body world")
  });

  </script>
</head>
<body></body>
</html>

will look into to it..

Have raised the issue...let us see if there is a possible solution...https://github.com/atom/electron/issues/2396

Look like node integeration is big deal..So moving away from node-integeration on. Please check and close the issue.

Works now, thanks


Sync worker kickoff

Upstream PR

The merge of this PR has been reverted on master, and a new PR has been opened targetting integration-sync-worker: https://github.com/Automattic/hydrogen-web/pull/11


5xx responses from API should raise a TransientError

I would love to see 5xx responses raise a TrackerApi::TransientError to let client code handle transient errors (timeouts, etc) differently than permanent errors (auth problems, bad requests, etc). For example, I would like to retry if there is a transient error, but not if there is a permanent error.
TrackerApi::TransientError could be a child of TrackerApi::Error to preserve compatibility with existing client code.
Here are a few examples of errors our app has reported. I'm assuming that these responses were accompanied by an appropriate 5xx HTTP status code.
A TrackerApi::Error occurred in background at 2016-01-20 08:29 :

  757: unexpected token at '
This website is under heavy load

We're sorry, too many people are accessing this website at the same time. We're working on this problem. Please try again later.
'
  /app/vendor/bundle/ruby/2.2.0/gems/tracker_api-0.2.11/lib/tracker_api/client.rb:207:in `rescue in request'

  A TrackerApi::Error occurred in background at 2016-02-04 07:11 :

  757: unexpected token at '
504 Gateway Time-out

The server didn't respond in time.

'
  /app/vendor/bundle/ruby/2.2.0/gems/tracker_api-0.2.11/lib/tracker_api/client.rb:207:in `rescue in request'

I think adding this behavior is the right direction. Are you interested in making the updates?

Thanks for the positive feedback, @forest. I’m interested, but I don’t know
if I’m going to have time anytime soon.
On Fri, Feb 5, 2016 at 12:20 PM, Forest<EMAIL_ADDRESS>wrote:

I think adding this behavior is the right direction. Are you interested in
making the updates?
—
Reply to this email directly or view it on GitHub
https://github.com/dashofcode/tracker_api/issues/61#issuecomment-180449818
.

Relatedly (hi @sbleon), is there interest in fleshing out ::TrackerApi::Error to handle specific Error Responses from the Tracker API? I could work on this over the next few weeks.

@patientdev what were you thinking of? Subclasses of ::TrackerApi::Error
could correspond either to HTTP statuses or to Tracker's code field
values. Or we could just have two subclasses (for 4xx "client is wrong" and
5xx "server is broken" error codes), which is the only distinction that I
really care about at the moment. If we started with a
::TrackerApi::InputError for 4xx and a ::TrackerApi::ServerError for
5xx, we could always subclass those further in the future.
On Fri, Apr 21, 2017 at 11:34 AM, Shane Cavanaugh<EMAIL_ADDRESS>wrote:

Relatedly (hi @sbleon https://github.com/sbleon), is there interest in
fleshing out ::TrackerApi::Error to handle specific Error Responses
https://www.pivotaltracker.com/help/api#Error_Responses from the
Tracker API? I could work on this over the next few weeks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dashofcode/tracker_api/issues/61#issuecomment-296224545,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMINz4_wcmZQsgWlc1t287NaP46qjPaks5ryMyhgaJpZM4HTern
.

@sbleon That proposal seems good. I'd vote for starting simple and getting more detailed as needed.

👌 Sounds good to me. I'll subclass generic 4xx and 5xx responses to start.


Add Dev Container configuration

This PR adds support for Dev Containers in order to have a quick and easy development environment using Dev Containers.

Thanks @ludelafo !


docs: document g:test#runner_commands

Make sure these boxes are checked before submitting your pull request:

[x] Update the Vim documentation in doc/test.txt

Resolves #768

@kyoh86 have I missed anything?

@codeinabox no, you have not.
Thank you!


[Fix] Don't update mutually exclusive on update calls

Describe your changes:

Don't allow updation of mutually Exclusive
Only during creation update we can set mutually exclusive

Type of change:

[x] Bug fix
[ ] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My PR title is Fixes <issue-number>: <short explanation>
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

closing taken care of here #16068


Error when trying to use matlab wrapper

I am at the point where I am supposed to build librealsense.mex, but I keep getting several errors. First, I kept getting errors saying visual studios was missing libraries and headers. I just copied those into the same directory and that fixed the problem. Now, im getting an error that says: "cannot open file realsense2.lib". Did I configure cmake wrong or is there another problem. I am extremely desperate at this point and have been trying to get this matlab wrapper to work for 11 hours now. Please help!

Hi @sharfin99
Sorry for the frustration, I'd like to make sure you have tried / considered the Windows installer route?

@dorodnic I am very new at all of this, so I did not know that was a different option than the "buid from source" option. I did select that option when downloading the sdk, but matlab still does not recognize objects and functions from the realsense camera. Do I have to move files or is it something else that I am missing?

From my personal experience setting-up the Installer version is just simpler.
You need the +realsense folder to be near your Matlab project, so it detect the declarations.
Inside you will also find couple of examples, such as depth_example.m
@lramati please comment if anything extra is required

Nope. As step 3 of the Installer options states, you just need to make sure Matlab can find the files. Your options are either to add it to Matlab's path (this can be done from within the matlab's settings, and there should be plenty of tutorials on the internet showing how), Or simply copying +realsense (The Whole folder, not just it's contents) into your project's root folder

@sharfin99 Did you get through the issue now with Dorodnic and Iramati's suggestion? Looking forward to your update. Thanks!

@sharfin9 Could you please update? Thanks!

Fixed! I did not realize the wrapper and download are the same thing. I just needed to add the path to the folder in MATLAB.

@sharfin99 Glad to hear that it fixed. Close the issue accordingly. Thanks!


fix: export non-Procedures TypeScript types

Should close #320.
Typemaps should now be correctly merged and exported. Let me know of any issues or things I've overlooked.

This PR fixes the issue. But it couldn't handle the generic type. For example, the following code:
#[derive(Debug, Serialize, Type)]
pub(crate) struct Success<T: Serialize + Type = ()> {
  data: T,
}

...will produce:
export type Success = { data: T };

But previously with the older versions crates:
specta = "=2.0.0-rc.1"
specta-macros = "=2.0.0-rc.1"
rspc = { version = "1.0.0-rc.5", features = ["tauri"] }

It can produce the correct types.
export type Success<T> = { data: T }


Introducing: Colmena CMS

🍯 Colmena CMS
I have been working on a new version of this project and as of today it will be available in a branch in this project.
Once most of the functionality of the v0.x project is in place I will archive the current master and rename the github project to colmena-cms and move it to the colmena organization.
To concentrate the development effort on the new version I have closed all outstanding issues, most of theme where inactive anyway due to the small movement in the project due to a lack of time.
Versions
The admin interface of Colmena CMS will be using the latest stable version of Angular (2.4.x at this moment) and aims to be updated. The backend will be LoopBack v2 as a lot of the components and mixins are not yet available for v3.
Timeline
While it's hard to give an exact timeline I will aim to get most the functionality working within 2 weeks from now (February 1st 2017), the progress can be followed here.
Contributions
Contributions are obviously welcome. As there are currently a lot of moving parts, it probably makes sense to first discuss what you'd like to contribute in order to don't waste time working on things that are not needed/are already being worked on. To get in touch please create an issue or join me on the Colmena CMS slack.
Tracking progress

[ ] Build out User Authentication
[ ] Build out basic Content Management
[ ] Add multi-language support
[ ] Create documentation
[ ] Rename project and move to colmena org

:+1:
Am excited about this new project.

Closing this story as it's no longer relevant.


Upgrade Traefik to v1.1.1

Traefik released v1.1.1 this morning, which includes some fixes that are especially relevant to its use as a k8s ingress controller.
This should not be merged yet because the v1.1.1 build hasn't made it up to Dockerhub yet. This PR is just a placeholder until then.

This image is finally up in Dockerhub, so this should be testable now.

Worked for me. Thanks @krancour!

CI is currently busted due to https://github.com/kubernetes/test-infra/pull/1204.

I would hold off on any consideration of merging this for now. I am having trouble getting ACME to work with this.

Nevermind about the difficulties I mentioned above. I got bitten by a little bit of a chicken and egg problem. ACME challenge was failing because the traefik pod came up before DNS was updated to point *.mydomain to Traefik's load balancer.
I suspect a lot of people will get bitten by this. It's probably worth documenting this better. (It's mentioned now, but should be emphasized.) That should be in a separate PR though because it's not a difficulty that this PR (the Traefik v1.1.1 upgrade) introduced.

See #266

Thanks @krancour. I've been bitten by this. This PR looks good.

@k8s-bot e2e test this

@k8s-bot ok to test


Allow usage of service from ngInit lifecycle event

Allow the usage of NgxSmartLoaderService.(start|stop)('i'); from Angular's OnInit lifecycle event.
The method getLoader return now null instead of throwing an error when the loader isn't created yet.
Calling loaderService.start('i') in OnInit, i is not created, so I store the need to open it.
When the loader component is created it calls the function addLoader to register itself inside the service. In this function I call executeWaitingAction('i', 'onStart') to execute the callback that was registered previously
PROS

Simplify the usage of the library
Avoid implementing AfterViewInit when you want to control loader by the service

CONS

Add complexity to the code

IMHO the right way is to inject the component before the OnInit lifecycle event, because this component is a loader so it must be present in the page earlier.
Unfortunately I don't know a way to achieve this.
Your reviews will be much appreciated @maximelafarie @khylias @marco10024 @melicerte 😘

Thank you @mcsky, I'll take the time to review it!

Thanks again, you rock! 🤘

Yes TestComponent is just here to proove that calling service in OnInit is working now :)

Any updates on this guys?

@Et3rnal I was on holidays, so this PR was on standby. I'll do my best to fix the current problem this week. Unfortunately, the maintainer is currently on holidays too so this won't be released very soon.

Hi all,
I tried your PR, and it seems to work perfectly! That's very good work, well done!
Why not make a real demo component? Other than test.component :)

The last commit fix a bug (@khylias yes there was one ^^)
Moreover, I did some refacto in the service's methods

@Nek- It seems that you request changes

@khylias Yes, but it seems all points are resolved. I need to make a big check on this PR to verify all's working as expected given that this PR is more than 2 months old. 😉

Actually reviewing it, potential feedback incoming... 😉

thank for the review @maximelafarie I'll take a look soon, be ready to release ;)

@maximelafarie After one hour switching from master and my branch and try differents strategies :

multi loaders with same identifier, start them by string identifier
multi loader with differents identifiers, start by array

I can't figure out a difference between master and my branch.
Please provide a sample to reproduce the bug that you are speaking, and then I'll provide a fix

@maximelafarie could you commit a sample to reproduce the bug on this branch, please?

@mcsky As I tell you previously, you can reproduce using any new methods you made on loaders getter with array instead of a simple string parameter. Example :
this.loaderService.{stop|start|...}(['my-loader', 'my-other-loader', '...']);


Disable auto line breaking

Thanks for providing this good configuration. I noticed that it automatically breaks a long line into multiple short lines (true multiple lines, not line-wrapping). May I know how I can turn this feature off?

Please check out:
http://vimcasts.org/episodes/hard-wrapping-text/


DeviceBondStateChangedEventArgs should inherit from DeviceEventArgs rather than just EventArgs

DeviceBondStateChangedEventArgs should inherit from DeviceEventArgs rather than just EventArgs and the property Device should be removed falling back to that of DeviceEventArgs
It's obvious from the description of DeviceEventArgs  that this was the intention anyway since they are both events in IAdapter
/// Event arguments for device events in IAdapter

Hi @axa88,
I'm the friendly issue checker.
It seems like (100.00 %) you haven't used our issue template :cry: I think it is very frustrating for the repository owners, if you ignore them.
If you think it's fine to make an exception, just ignore this message.
But if you think it was a mistake to delete the template, please close the issue and create a new one.
Thanks!

Also shouldn't members of derived EventArgs all be properties rather than what it is now, a mix of properties and fields?
better for consistent serialization handling i would think, no?

Inheriting would make some testing and generic handlers more convenient, and i dont see it is a breaking change but could be wrong...
@janusw if this isnt under consideration please feel free to close, maybe im the only one to see things this way.


Use exec-jar instead of docker image

Compared to using docker pull to get an image, using the build jar can save a lot of time and may also have requirements for modifying V2 API in the Java engine.
Using docker pull takes 9 mins, build jar only 1 min.

We have observed that sometimes pulling a Docker image is very fast. We should continue to monitor this CI process for another week.


Bytes leak when ]11 OSC is used to get background color.

When "\x1b]11;?\x1b\\" is used to query the background color, the loop reading stdin breaks after receiving the 0x1b byte. But there is still one byte left in stdin to be read (In my case 0x5c) which causes problems if I try to read stdin after this.
I'm not sure if this also happens in the other two cases as well.
https://github.com/dalance/termbg/blob/6a1bdcb86cf103648bcad4f0b6c8c3dc48d057b3/src/lib.rs#L175-L181
I'm running bash in alacritty.

Thanks!
I fixed it, and released v0.2.2.

Wow! That was quick. Thanks!


[Do Not Merge] test not triggering bundle build on konflux

DO NOT MERGE
test purpose only.

bundle build has not been triggered

/close
test ok


UI waits for sound to render making tuning a slow process

Acknowledgement

[x] I have read Getting-Started and FAQ

🐛 Describe the bug
While working on projects there is a consistent issue of OpenUtau hanging every time a tuning parameter is changed, so that the UI can wait for the sample to render. This makes it impossible to tune efficiently, especially on hardware that isn't extremely new or powerful.
Explains how to reproduce the bug

Tune or modify a USTx in any context on any mid-to-low-end hardware

OS & Version
Linux 5.15 (Arch Linux, EndeavourOS)
Logs
log20220915.txt

you can turn off pre-render in preferences

Even with pre-render switched off, I end up with performance issues though they only appear upon hitting play.
It can be a tad irritating when I hit play and the playhead does not follow the sound output. I know for many people this can be negligible but I find it hard to follow what the sound equates to on the piano roll.
These two aspects should, in the long run, ideally become asynchronous from one another. Obviously it's not a high priority but i feel that it may be a good QoL improvement for future updates.

Which renderer or engine are you using? I recommend wordline-r for note and pitch editing, which doesn't call external process and is efficient.


Contacts not available with RainLoop owncloud-app from direct URL

While it is indeed possible to open the RainLoop-app for owncloud directly (from URL: https://myowncloud.domain.com/index.php/apps/rainloop/app/), RainLoop can't access the contacts of owncloud. Is this issue inevitable or can it be solved?
Of course the contacts addressbook does work when first logging into owncloud, then on the email app for RainLoop.

To get contacts from owncloud, it is neccessary to be logged in in owncloud.
If you log out in owncloud and start rainloop with your direct link you don't use owncloud authentifiation:
Use https://myowncloud.domain.com/index.php/apps/rainloop/ instead and you get the login screen of owncloud. Then you log in with your owncloud credentials and are directly in rainloop mail.
If you use permanent authentification (remember login) via cookies in owncloud, you don't need to give credentials at all.
I use it like this since I integrated rainloop in owncloud and have this link as favorite to check mails fast without first starting owncloud and then switching to rainloop.

Right, I understand, thanks.
Then it's not possible to serve only mail to some users without ownCloud while having RainLoop integrated in ownCloud. Seems logical when we speak about it, but I didn't realize this when installing. I guess I have to give everyone an ownCloud account if they want to be able to use/store their contacts.

Just to add a note: ...then the original implementation of RainLoop (with syncing the addressbooks while staying seperate) wasn't that bad at all. People could use the addressbook without ownCloud account but also with one...

Rainloop has it's own standalone contacts database but it is deactivated, if you integrate rainloop via owncloud app.
This is a good decision, if you have a onwcloud account but makes it impossible to use it like you want.
Maybe there is a solution for your task:
If rainloop developer sees a way to activate rainloop sql database if you log in directly (via your link in first post) without using owncloud credentials and so only users without owncloud account use the rainloop adress database.
But it could be a problem, if someone with owncloud account also logs in directly.
This shouldn't be done because this could lead in two contact lists depending on the way you logged in.
The contacts sync wasn't very reliable in my opinion. It worked but integrating owncloud contacts is really the best way. Only adding contacts from rainloop in owncloud contacts is a still missing request.
Let's see what "Mister rainloop" says to it ... :wink:

Yes, that's well put. I agree. Because of the problem you're describing I don't think activating the RainLoop sql DB should be done while integrated in ownCloud. If I really want a seperate mail-only solution, I will install a seperate instance of RainLoop. (altough I'll have to buy it twice then...)
Indeed storing addresses from rainloop to ownCloud would be great to have!

I don't think, you need to buy it twice if you want to use it like that and want to brand your rainloop install.
But to circumvent the problem with an owncloud user logging in the "wrong way", a separate installation for non oC users would be the best way.
So you separate this two groups of users and it will  be more easy to maintain.

Since 1.9.0+ version local contacts are allowed in the ownCloud package.


Fix licenses

Motivation for this change
Continuation on the way to resolve https://github.com/NixOS/nixpkgs/issues/43716
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg eval

@doronbehar OK, magic. works again.thanks!


Make DDP/FSDP a regular transform

🚀 Feature
Make DDP/FSDP a regular transform (to a large part including making transforms flexible enough to support this).
Motivation
Currently DDP/FSDP is not a regular transform, leading to things like #94 and limiting composability / sequencing.
One of the key bits is that DDP/FSDP would need to do the adjustments we currently do to the prologue during tracing with DDP/FSDP in the transform, so we need to allow mutation of prologues through transforms. This is also in line with similar needs for other transforms (lora, quantization, but also value-and-grad-things) that change prologue signatures, so this generalization should happen.
cc @carmocca @awaelchli @crcrpar

What is meant by making DDP/FSDP a regular transform? What are you planning to do?
Today it's not a transform at all, as I commented here https://github.com/Lightning-AI/lightning-thunder/issues/94#issuecomment-2048269542. thunder.distributed.ddp/fsdp only annotate parameters for tracing. It's also described in the tutorial https://github.com/Lightning-AI/lightning-thunder/blob/main/notebooks/dev_tutorials/fsdp_tutorial.ipynb
I don't see any other way for sharding happen somewhen after the thunder.jit(model) call. What ideas do you have?
The current workflow is

Shard the model
Done with thunder.distributed.fsdp(model) or with torch.distributed.FullyShardedDataParallel in PyTorch
Set up the optimizer using the sharded model so that the optimizer state is a shard
Call thunder.jit(sharded_model) or torch.compile(sharded_model) in PyTorch.

I would like to move 3 up (for thunder.jit).

Is the preferred order then 3 -> 1 -> 2?

So per discussions with @crcrpar and @IvanYashchuk (thank you!)

This needs to modify model & prologue and compute trace (and invalidate / modify old cached entries).
Needs to come before autograd and stay compatible.
We need a good way to represent the changes to model state, the current goal is to put this on the ThunderModule and leave the user modules intact. This is why #228 simplifies parameter access and also we want to access the thunder module in the prologue (which has also come up before).

triage review — let's start design review with draft PR to discuss

This is done.


Merge pact files before upload + split pacts config to be consumerPact and providerPacts

Hi,
I as trying to use your maven plugin to download and upload pacts from the pactbroker.
I was facing with issues I tried to address:

I am using ITV scala pact library which is unfortunately not merging pact files after the tests generated pacts like pact_jvm_consumer. They do the merge in their sbt pact upload plugin. But I am forced to use maven and your plugin satisfies my needs apart the fact that it is not merging. I added this piece of functionality into the PactFile. It checks the provider and the consumer for the loaded pact files and if two files has the same it merges them, writes the new file to the file system and finally the new file is used for uploading. If you use the plugin with pact_jvm it should have any negative effect but you could use with other pact generators like ITV's scalatest based.

The other thing is that I tried to use it in a multi module maven project where I have modules with consumers and producers. I would like to download pacts for producer tests and upload from consumer tests. With the current way of working the only way I could have this if I use profiles what I would like to avoid as much as possible. I believe it is an unnecessary complexity here.
All I need is a mvn clean install on the parent project and every submodule should know if it needs to download or upload. That is why I introduced consumerPacts and producerPacts config items. If both of them is missing nothing happens. If any of them or both is provide it behaves accordingly.
You can find an example here:
https://github.com/lachatak/consumer-driven-contract
The example is under development but the main thing is that on top level project a mvn clean install is enough and works nicely.
The third thing is that I had to set @Execute(phase = LifecyclePhase.NONE) as in a multi module project every tests were running 2 times.
Feel free to use it in your project or just reject if you don't like.
I am open for further discussion :)
Obviously my change set has breaking changes as it doesn't support pacts config element any more.
Krisztian

Hi
Thanks for your work, it looks useful. It would have been nice to door these new features into different PRs though.
I will have a closer look at it in the next few days, but I would like to avoid breaking changes...

Hi
Have a look at it. If you like I could slice the features to separate PRs also keeping backward compatibility some how.
thx
k

hi
i had a look and i would like to integrate that, i just have some questions:

regarding the renaming of the pact-element: could this work for you?
this is still a bit redundant in the sense of the phase though
can you explain why @Execute(phase = LifecyclePhase.GENERATE_TEST_RESOURCES) leads to 2 test-executions?
i think, putting the merging-functionality behind a property with default= false is safer, what do you think?
are you really sure that you merge pacts with same producer/consumer? BrokerRepositoryProvider::43 groups only by provider, no?

(i wont have any time in the next few weeks otherwise i would invest  some time to make those changes myself)

Hi,

I suppose the first 2 points some how connected to each other. I saw that the configuration meant to be pushed under the execution which is fine. Probably I made a mistake that is why it didn't work for me. But! If you have a multi-module maven project you probably want to define everything at the top level and just add project specific configuration in the sub-modules. If you configure just the executions on the top level and try to run 'mvn clean install' at top level then the plugin fails as you didn't provided the pact directory on the parent. Obviously I don't want to do this at the parent as it belongs to the child. So I suppose still something is missing here.
The other thing what I can do is just define the plugin at every child project without pre-configuring at the parent. This is something I have to investigate. But in this case some configuration will be duplicated across all the sub-mudules.
I will spend some time to look into it and I will get back to you with my findings.
property is fine. I like it.
Good point. I will fix this and adding test as well.

Thx the feedback
k

I have just tried your suggestions with executions:
http://stackoverflow.com/questions/16540808/can-i-configure-multiple-plugin-executions-in-pluginmanagement-and-choose-from
I followed the description in the post. I am using your latest plugin (0.0.8) There are 2 major issues:

Upload-artifact runs in verify phase in sub-modules and somehow every tests is executed twice. -> Two pact files are generated with the same content and eventually uploaded to the broker. Obviously duplicated pacts are the same so it won't effect anything in the broker but still not nice that it runs twice.  If I change the LifecyclePhase in the @Exceution to be NONE then it is alright. Runs just once with the previous configuration in every sub-module.
Well known issue. Merging pact not happens.

So theoretically it works but something is not correct with the upload phasing.
I have created a branch so you could look into it:
https://github.com/lachatak/consumer-driven-contract/tree/execution_test
So the only thing we have left is to fix the phasing and the merge.
I will look into it tomorrow.
k

Everything has been removed apart from the merging functionality and UploadPactsMojo phase.NONE. With the original phase.TEST every test runs twice in a multi-module project.
producer consumer merging issue is fixed as well.
minor cleaning of not used imports


How to generate the ground truth depth map in the NuScene dataset?

Hi, you can generate sparse depth gound truth by projecting LiDAR into images.
The function can be found in nuscenes-devkit (render).

OK, thanks!


Theme: smooth dark

Which bug report or feature request do these changes address?
#75
a dark theme with customisable options - see screenshot - options and their defaults

What does your code do and why?
app.css: an option to add rounding to highlights - selectors are the same as the ones in theming/colors.css
theme.mjs: sets many colours based on selected options
the function rgbLinearShade lightens or darkens a specified colour, the same as overlaying black/white on top of the colour with the specified opacity.
ui_corner_action, ui_corner_action-hover, ui_corner_action-active, code, bg_secondary and bg_card are lighter/darker tints of the background.
primary and secondary colours are also configurable, similar to the ones in the dark+ theme.
colours for highlight-text, text, highlight, callout, tag and boards are set depending on which colour profile is selected.
pastel has lighter and less saturated colours - highlight-text is made black(ish) as there is little contrast if it stays white
regular has darker and more saturated colours, highlight-text stays white
the colours for these are all from LCh colours with the same chrominance and lightness (specific values in comments). most blues are altered to be less saturated (LCh is not very accurate in the blues).
theme colours are not set directly to work with other themes.
variables.css: some colours have opacity to change based on the existing background. colours that are lighter/darker tints of the background but need to have 100% opacity are set in theme.mjs.
theming/theme.css: I found that transparent iframes use the default Notion background. Easily fixed by setting iframe to the custom background.
smooth-dark.png: file is created but empty so no changes need to be made in mod.json. Replace with your theme screenshot with the default options pls :)
screenshots:
default settings

grey: background #1F1F1F, color profile regular

a more saturated colour: background #40121A

thanks, this will be part of v0.12.0

theming/theme.css: I found that transparent iframes use the default Notion background. Easily fixed by setting iframe to the custom background.

it might be worth opening a separate PR to add that to the global styles

Hey @blorbb, sorry for such a long wait. I'm getting the ball rolling for release now and the notion-enhancer has returned to a monorepo architecture for simplification of development & contributions, so I'm archiving this repository. If you're still keen on building this theme for the notion-enhancer, feel free to open a PR over at https://github.com/notion-enhancer/notion-enhancer - if you'd like, feel free to update it to be compatible with the latest changes, otherwise if you open a PR of this code as-is then I can port the code across for you. Thanks!


W10 App: Javascript error main process

Just downloaded the desktop app, and when I clicked about

This was the error I received:

This bug already solved https://github.com/RocketChat/Rocket.Chat.Electron/issues/427

This bug already solved #427


boards/sama5d4-ek: Move -fno-common to CELFFLAGS/CXXELFFLAGS

Summary
like other's Make.defs
Impact
No
Testing
Pass CI

abandon see here: https://github.com/apache/incubator-nuttx/pull/5485


liblept1742.so missing?

Hi!
I set up a solution, installed Tesseract 3.2.0alpha4 und copied the tessdata folder to my project.
I can find some information about a missing liblept1742 .dll but the error I am encountering is, that i am missing a file liblept1742 .so. Where can I find that, and where do I have to put it?
My debug information:
Tesseract Information: 0 : Current OS: Unix
Tesseract Information: 0 : Current platform: x86
Tesseract Information: 0 : Checking custom search location './x86' for 'liblept1742.so' on platform x86.
Tesseract Information: 0 : Checking executing application domain location '/Users/***/RiderProjects/OcrMvp/OcrMvp/bin/Debug' for 'liblept1742.so' on platform x86.
Tesseract Information: 0 : Checking current application domain location '/Users/***/RiderProjects/OcrMvp/OcrMvp/bin/Debug/' for 'liblept1742.so' on platform x86.
Tesseract Information: 0 : No bin directory exists under the current application domain's location, skipping.
Tesseract Information: 0 : Checking working directory '/Users/***/RiderProjects/OcrMvp/OcrMvp/bin/Debug' for 'liblept1742.so' on platform x86.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.DllNotFoundException: Failed to find library "liblept1742.so" for platform x86.

This project doesn't supply Unix .so libs.  You would need to build that from scratch.


Test naoki branch on CI

Summary
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

17 of 111 (15.32%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.09%) to 50.18%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_ibm_provider/ibm_backend.py
1
6
16.67%

qiskit_ibm_provider/utils/json_decoder.py
16
105
15.24%

Files with Coverage Reduction
New Missed Lines
%

qiskit_ibm_provider/ibm_backend.py
1
61.86%

Totals

Change from base Build<PHONE_NUMBER>:
0.09%

Covered Lines:
2923

Relevant Lines:
5825

💛  - Coveralls