Error: No template specified for component SelectComponent

Hi @basvandenberg, for some reason i cannot use your select module.
Error is because of: https://github.com/basvandenberg/angular2-select/blame/master/src/select.component.ts#L29
Reference: https://github.com/angular/angular/issues/14010
Commit introduced it: https://github.com/basvandenberg/angular2-select/commit/a2a8970816787403e278631c64dac06ac885b2b5
Version i use: "angular2-select": "1.0.0-beta.2",

You cannot import the source code, as it is, into your own project. You can see in the build file (tasks templates and styles, at the bottom of the file) that the HTML and CSS files are transformed to typescript files. These generated typescript files (containing the HTML and CSS as string variable) are imported into select.component.ts and select-dropdown.component.ts.
With little adjustments you could import incorporate the source code into your project when using angular-cli. In select.component.ts you should remove:
import {STYLE} from './select.component.css';
import {TEMPLATE} from './select.component.html';

and replace:
@Component({
    selector: 'ng-select',
    template: TEMPLATE,
    styles: [STYLE],
    providers: [SELECT_VALUE_ACCESSOR],
    encapsulation: ViewEncapsulation.None
})

with
@Component({
    selector: 'ng-select',
    templateUrl: 'select.component.html',
    styleUrls: ['select.component.scss'],
    providers: [SELECT_VALUE_ACCESSOR],
    encapsulation: ViewEncapsulation.None
})

The same should be done for select-dropdown.component.ts

I hope my comment helped. I'll close the issue for now. Please let me know if you need more help.

@basvandenberg hi, sorry for the late ansver
i do not try to import the source code to my own project. i installed it via npm i --save angular2-select and did import { SelectModule } from 'angular2-select' then imported it in the app module

Copying the source is indeed not ideal, but based on your initial issue I thought that you tried to do that.
When installing with npm and importing it as you mentioned there should be no issue with the templates. What does your app.module.ts look like? And what build tool are you using?


Error:  Failed to create wallet from private key: signature error

Component
Forge, Anvil
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (bf8a612 2022-08-26T19:22:03.6751305Z)
What command(s) is the bug in?
forge script script/Counter.s.sol:CounterScript --fork-url http://localhost:8545 --private-key $PRIV_KEY --broadcast
Operating System
Windows
Describe the bug
"anvil" is running in the backend and the environment variable "PRIV_KEY" is right with no "^M", "0x" or not.
It's showing "Connection header did not include 'upgrade'" in the page  when I open http://<IP_ADDRESS>:8545/.
It returns "Error:  Failed to create wallet from private key: signature error" when I type the command "forge script script/Counter.s.sol:CounterScript --fork-url http://localhost:8545 --private-key $PRIV_KEY --broadcast".

What was the resolution here? I'm having the same issue with the latest version of forge (0.2.0)

@grp06 does this still happen on latest foundryup?

Yes I confirm having the same problem. I got the PK from anvil

In my case I was missing the $ to refer the PRIVATE_KEY environment variable from the .env file

I see, perhaps we should check this for the error message?

Closed in #3270


Figure out if we can use the sidebar, if yes allow stackoverflow question selection on there

I think this has been mostly done, so closing the issue for now. We can make more specific ones later if we need some fixes.


User can click a link to go to a Locality/Species/Time Unit/Time Bound in all tables of those entities

Tables of these entitites where there is currently no link to go to the details of that entity:

Species-tab in a Locality
Localities-tab in a Species
Localities-tab in a Time Unit
Time Units-tab in a Time Bound
(Cross-search rows only link to localities, link to species could be useful)

Last point tracked in #211, keeping both stories as I'm not sure if we want/need that functionality, and if it's in scope for this story or not.

[ ] All table rows have a link to the  listed entities
[ ] Tests are implemented
[ ] Documentation is written

Tasks:

[ ] #602

docs for this:
https://github.com/nowcommunity/nowdatabase/blob/main/documentation/components/EditableTable.md
https://github.com/nowcommunity/nowdatabase/blob/main/documentation/components/SimpleTable.md

Test results:

[x] OK: All table rows have a link to the  listed entities
[x] Possibly OK: Tests are implemented
[x] OK: Documentation is written

Comment: Go to: Localities -> Locality -> Projects -> Project -> Project Members -> Person -> Return to table --> Goes to Localities instead of Project Members as one would expect

Good catch, now tracked in #640


Model for parent-child content page relationship

What is it and who's it for?
For website users who need access to a group of related content pages so they can pick and choose what they look at, and can follow onward journeys to related content
Background
We currently don't have a way to connect a group of content pages together under a single 'parent' page. It's like a series model, but for informational content, not domain objects.
This is problematic in situations where we have multiple pages that relate to each other under a single 'service' area, for example, this set of content pages held together under the main topic of 'Library services and facilities'
Library services and facilities
- Library membership
- Copying and imaging services
- Computers and wifi in the library
- Study rooms

We have multiple instances of this problem across the website.
Aims

Establish 'Part of' relationship for informational content
Allow nested, parent-child content pages
Build this so that sibling pages can be included on each other as onward journeys

TODO

[ ]

Acceptance criteria TBC
Other considerations
<---Delete as appropriate--->

Impact on URL design
Cardigan documentation

Initial sketch of how the parent > child content page relationship could work. It's similar to the seasons model, but for informational content only.
Parent page includes:

Hero image?
Standfirst
Content about the section
Cards for child content

Child page includes:

Anchor links
Page content
Related child content as cards (onward journeys)

Need to figure out how to describe a group of content pieces in Prismic, and how the 'Part Of' section of the headings could be used to help build the connection between the pages in another way.

Initial sketch of how the parent > child content page relationship could work. It's similar to the seasons model, but for informational content only.
Parent page includes:

Hero image?
Standfirst
Content about the section
Cards for child content

Child page includes:

Anchor links
Page content
Related child content as cards (onward journeys)

Need to figure out how to describe a group of content pieces in Prismic, and how the 'Part Of' section of the headings could be used to help build the connection between the pages in another way.

26 January 2021:

Parent page: cards are of equal size
Parent page could be an extension of the landing page

26 January 2021:

Parent page: cards are of equal size
Parent page could be an extension of the landing page


Refactor RefElemData

Currently dispatch on approximation_type is messy and makes it hard to add structure based on quadrature structure (e.g., Stroud tensor product quadrature).
This PR reorganizes RefElemData so that quadrature information goes into the Polynomial approximation type. This is consistent with the current approach taken by SBP approximation type, which also encodes specific information about the quadrature used to construct operators.

To clean up the Polynomial approximation type, we'll take the following steps:

we now default to TensorProductQuadrature on Quad and Hex elements
we introduced MultidimensionalQuadrature instead of DefaultPolynomialType to distinguish from TensorProductQuadrature.
DefaultPolynomialType is now only be used for dispatch.


Feat: non compliant strings parsing

Sometimes PHP objects can contain strings that are not UTF8 compliant. This can cause problems when unserializing. An example of such a string:
"searchTerm";s:28:"�f���V�����b��r�[�t�n���~�q";`
This is actually a Shift JIS encoded string. If we parse this currently the unserializer dies as the string length is not correct. PHP handles this correctly, at least it doesn't die, and gives a string with many question marks as a result.

Merged as 6aedd57


arXiv Filterting

Update Notebooks to also include arXiv category tags like stat.ML, cs.ML, cs.CV, etc.
On UI, user should be able to filter the arXiv linked papers by tags

Closing as considering in Roadmap for 2021


remove clean in .travis.yml

Is there a duplicate in the other #633 ? maybe we need to close that and instead just merge this?
Anyway..its trivial and you can handle it

Is there a duplicate in the other #633 ? maybe we need to close that and instead just merge this?

Sorry for the confusion. This PR this removes the clean, in its 2nd commit, but it builds on top of #633 which is the first commit... I raise 2 separate PRs for separate review - but it's probably just confusing... :smile: GitHub, contrary to Gerrit, doesn't support this kind of workflow very well - if you want to make 2 changes which touch the same lines of code. (If you raise two separate PRs from master, then one will nessarily conflict with the other, which is just overhead.)
What I don't understand is why Travis CI doesn't run for these 2 PRs... or is it just overloaded? Let's wait a bit.

@vorburger  with #633 merged, this seems to have conflicts, want to pull from develop and fix this?

@vorburger with #633 merged, this seems to have conflicts, want to pull from develop and fix this?

@awasum done

Thank @vorburger


Update NS1 _REGION_FILTER to include remove_no_georegion in config

NS1 api appears to be returning remove_no_georegion in the config for geofence_regional now which breaks the filter expectations (but does match what it does for geofence_country.
The box is checked in the UI so this probably makes sense. Not sure if the remove_no_georegion stuff is a new addition or just newly added to the API, but this change will be required to prevent octoDNS from rejecting the filter chains of NS1 dynamic records.
Return value now is:
            'config': {
                'remove_no_georegion': True
            },
            'filter': u'geofence_regional'

This was an expected change in a recent API update so should be gtg.


Enable sign editing if user has nabsuite.editsigns permission

Added new permission nabsuite.editsigns
Allow players with permission to edit signs
Don't allow the sign editor to open if the player lacks build permission in area

Looks good, thank you - I'll give the permission to loyalists and up


add deletion file handling to scanner

NOTE: Only supports Scan right now. Still need to add support for index scans.
TODOs:

[ ] pull in #931 and test
[x] write some unit tests
[ ] test e2e from scanner

addressed all comments except one. Working on moving deletion vector read further up


pnpm build fails after commit bb855a2f8f1be70d1b1f739ed229bcd09b73f931

i'm unable to do pnpm build after pnpm install on current master, i've bisected the problem to commit bb855a2f8f1be70d1b1f739ed229bcd09b73f931.
Lockfile is up to date, resolution step is skipped
Packages: -2
--

dependencies:
- applesauce-core 0.6.0
+ applesauce-core 0.0.0 <- ../applesauce/packages/core
- applesauce-react 0.6.0
+ applesauce-react 0.0.0 <- ../applesauce/packages/react
- applesauce-signer 0.6.0
+ applesauce-signer 0.0.0 <- ../applesauce/packages/signer

Done in 1.6s

><EMAIL_ADDRESS>build /home/.../nostrudel
> tsc --project tsconfig.json && vite build "--outDir" "/home/www/..." "--emptyOutDir"
...
src/classes/accounts/account.ts:2:32 - error TS2307: Cannot find module 'applesauce-signer' or its corresponding type declarations.

2 import { Nip07Interface } from "applesauce-signer";
                                 ~~~~~~~~~~~~~~~~~~~

src/classes/accounts/amber-account.ts:1:38 - error TS2307: Cannot find module 'applesauce-signer' or its corresponding type declarations.

1 import { AmberClipboardSigner } from "applesauce-signer";
                                       ~~~~~~~~~~~~~~~~~~~

src/classes/accounts/extension-account.ts:1:32 - error TS2307: Cannot find module 'applesauce-signer' or its corresponding type declarations.

1 import { Nip07Interface } from "applesauce-signer";
                                 ~~~~~~~~~~~~~~~~~~~

src/classes/accounts/nsec-account.ts:2:30 - error TS2307: Cannot find module 'applesauce-signer' or its corresponding type declarations.

2 import { SimpleSigner } from "applesauce-signer";
                               ~~~~~~~~~~~~~~~~~~~

src/classes/accounts/serial-port-account.ts:1:34 - error TS2307: Cannot find module 'applesauce-signer' or its corresponding type declarations.
...
 ELIFECYCLE  Command failed with exit code 2

i have already tried to clean the tree, to no avail. Looks like it's dropping applesauce from the dependencies which isn't intentional.
Version:
$ pnpm -v
9.12.1

Let me know if you need any more info, i don't really know much about typescript build systems.

thank you!
yes, the master version is unstable, i realize, but kind of important when trying to do development on top :smile:

If you want to build it locally you can clone https://github.com/hzrd149/applesauce and link the packages locally. Ill try to write up some instructions in the readme at some point

OK that makes sense. Instructions would be very helpful, but i think i can figure it out with this.

Can confirm the recent dependency change fixed the build flow.


Keras appears to generate non-deterministic tensorflow graph

System information

Have I written custom code (as opposed to using example directory):  Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  Ubuntu 18.04
TensorFlow backend (yes / no):   yes
TensorFlow version:  1.13.1
Keras version:  2.4.4 (bug exists on latest master as well)
Python version:  3.6.8
CUDA/cuDNN version:  not using cuda for this
GPU model and memory:  not using cuda for this

Describe the current behavior
If I set all the random seeds, use only the CPU, disable CPU multiprocessing, and I run the same experiment 10 times, the loss of the second train_for_step() call comes out as one of two different values each time.
Describe the expected behavior
The loss should be bit-perfect reproducible in this situation.
Code to reproduce the issue
import random
random.seed(999)
import numpy as np
np.random.seed(999)
import tensorflow as tf
tf.set_random_seed(999)

import keras
from keras.layers import (Activation, Conv2D, Dense, Dropout, Flatten,
                          MaxPooling2D, Layer)
from keras.losses import categorical_crossentropy
from keras.models import Sequential
from keras.optimizers import RMSprop, Adam
from keras.utils.data_utils import get_file

session = tf.Session(
        graph=tf.get_default_graph(),
        config=tf.ConfigProto(intra_op_parallelism_threads=1,
                              inter_op_parallelism_threads=1)
        )
keras.backend.set_session(session)

# Model taken from the keras cifar10 example
model = Sequential()
# specifying input shape upfront does not matter
#model.add(Conv2D(32, (3, 3), padding="same", input_shape=[ 32, 32, 3 ]))
model.add(Conv2D(32, (3, 3), padding="same"))
model.add(Activation("relu"))
model.add(Conv2D(32, (3, 3)))
model.add(Activation("relu"))
model.add(MaxPooling2D(pool_size=(2, 2)))
model.add(Dropout(0.25))

model.add(Conv2D(64, (3, 3), padding="same"))
model.add(Activation("relu"))
model.add(Conv2D(64, (3, 3)))
model.add(Activation("relu"))
model.add(MaxPooling2D(pool_size=(2, 2)))
model.add(Dropout(0.25))

model.add(Flatten())
model.add(Dense(512))
model.add(Activation("relu"))
# eliminating this dropout layer restores reproducibility:
model.add(Dropout(0.5))
model.add(Dense(10))
model.add(Activation("softmax"))

# setting decay to 0.0 or using Adam restores reproducibility
optimizer = RMSprop(lr=1e-4, decay=1e-6)
#optimizer = RMSprop(lr=1e-4, decay=0.0)
#optimizer = Adam(lr=1e-4, decay=1e-6)
model.compile(loss=categorical_crossentropy,
              optimizer=optimizer,
              metrics=[keras.metrics.categorical_accuracy,
                       keras.metrics.categorical_accuracy])

# metrics which break reproducibility:
#   losses.categorical_hinge x1
#   metrics.categorical_accuracy x2
#   losses.hinge x2
#   losses.mean_absolute_percentage_error x2

# metrics which seem fine:
#   losses.mean_squared_error
#   losses.mean_absolute_error

# build some phony data
xtrain = np.ones([64,32,32,3])
xtest = np.ones([64,32,32,3])
ytrain = np.array([[1,0,0,0,0,0,0,0,0,0] for _ in range(64)])
ytest = np.array([[1,0,0,0,0,0,0,0,0,0] for _ in range(64)])

xtrain = xtrain.astype('float32')
xtest = xtest.astype('float32')
xtrain /= 255
xtest /= 255

# train two batches

start = 0
xbatch = xtrain[start:start+32]
ybatch = ytrain[start:start+32]
print( model.train_on_batch(xbatch, ybatch) )

start = 32
xbatch = xtrain[start:start+32]
ybatch = ytrain[start:start+32]
print( model.train_on_batch(xbatch, ybatch) )

Check the reproducibility with the following command:
for i in `seq 10` ; do python3 code_example.py 2>/dev/null | tail -n 1 ; done

Result:
[2.2911897, 1.0, 1.0]
[2.2910979, 1.0, 1.0]
[2.2910979, 1.0, 1.0]
[2.2910979, 1.0, 1.0]
[2.2911897, 1.0, 1.0]
[2.2911897, 1.0, 1.0]
[2.2910979, 1.0, 1.0]
[2.2910979, 1.0, 1.0]
[2.2911897, 1.0, 1.0]
[2.2910979, 1.0, 1.0]

Other info / logs
There are a variety of things which affect whether or not the training is bit-perfect reproducible:

The loss is always consistent after the first train_for_batch().  Training for three steps exhibits identical behavior to training for two steps (all losses come out to one of two values)
Commenting out various layers restores reproducibility (see comments in code example)
Eliminating the decay from RMSprop optimizer (or using Adam optimizer with decay) restores reproducibility
Metric selection affects reproducibility.  Some metrics break reproducibility when included twice, one metric, losses.categorical_hinge breaks reproducibility when included at all.
I noticed no change in behavior when I used the git master branch.
Inserting a tf.print() into the graph, while using the RMSprop with decay, will restore reproducibility.  Patch:

*** optimizers.py	2019-04-23 11:10:15.269380564 -0700
--- new	2019-04-23 09:57:50.773179254 -0700
***************
*** 255,274 ****
--- 255,275 ----
      def get_updates(self, loss, params):
          grads = self.get_gradients(loss, params)
          accumulators = [K.zeros(K.int_shape(p), dtype=K.dtype(p)) for p in params]
          self.weights = accumulators
          self.updates = [K.update_add(self.iterations, 1)]

          lr = self.lr
          if self.initial_decay > 0:
              lr = lr * (1. / (1. + self.decay * K.cast(self.iterations,
                                                        K.dtype(self.decay))))
+         self.updates.append(tf.print(lr))

          for p, g, a in zip(params, grads, accumulators):
              # update accumulator
              new_a = self.rho * a + (1. - self.rho) * K.square(g)
              self.updates.append(K.update(a, new_a))
              new_p = p - lr * g / (K.sqrt(new_a) + self.epsilon)

              # Apply constraints.
              if getattr(p, 'constraint', None) is not None:
                  new_p = p.constraint(new_p)

@rb-determined-ai I checked with Keras==2.2.4 and tensorflow==1.14.0, the results are consistent. Please check the gist here. Thanks!

Automatically closing this out since I understand it to be resolved, but please let me know if I'm mistaken.Thanks!


lib/pthread: Fix create/join race in thread lifecycle

The pthread_join() implementation was done using a condition variable and not k_thread_join(), and that's actually fatal.  It's not possible in Zephyr to guarantee a thread has exited in a race-free way without calling either k_thread_abort() or k_thread_join().
This opened a hole where an app could call pthread_join(), which would go to sleep waiting on the condition variable, which would be signaled from the exit path of the thread, and then return to call pthread_create() (and thus k_thread_create()) on the same pthread_t object (and thus the same struct k_thread) BEFORE THE EARLIER THREAD HAD ACTUALLY EXITED.
This makes the scheduler blow up, at least on SMP (I wasn't personally able to make it happen on uniprocessor configs, though the race is present always).
Rework to call k_thread_join().  There's no other correct way to do this.
Fixes #56163

Note that this may not be completely conformant to POSIX semantics.  There's a pthread_detach() implementation using that same condition variable, and I suspect these two need to be unified.  Hopefully someone with more POSIX-fu than I can explain the requirements.
But the race needs to be addressed by using k_thread_join().

Oh, and to be clear: I tested this with @cfriedt 's rig in #57637 which reverts some recent workarounds to make the bug more visible.
Also: the checkpatch failure is a false positive.  POSIX does indeed use positive errno values.

I had a chance to look up pthread_detach(), btw.  And indeed, the treatment here is insufficient.  The documented behavior of pthread_detach() is that it wakes up any threads blocked in a pthread_join() call[1].  And now that that's a k_thread_join() we need some way to do that out of the scheduler (which is probably just as simple as a z_thread_wake_joiners() or something -- just a little lock around an unpend_all() call).
Let me stick a DNM on this for now, pending a little bit of thought.
[1] For the life of me, I can't understand why!  The "meaning" of the call is that the OS can clean the thread up instead of holding on to things like its result code and process ID until something retrieves them (analogous to the way unix processes live as zombies until something calls wait()).  But... that doesn't mean that you can't join it!  This is just inventing a special edge case when none was needed.  POSIX, I swear...

New version, updated as described.  This one seems to be working for me both through a full twister and on the test rig.  Please re-review.

New version, updated as described.  This one seems to be working for me both through a full twister and on the test rig.  Please re-review.

I unfortunately force-pushed on my branch, but I should be able to test it out without the additional commit.
Will give it a shot shortly.

Close this.  Patches got folded into #57637 and discussion continues there


[FLINK-36817] Introduce KafkaConsumerFactory

In certain scenarios users of the KafkaSource in the flink-connector-kafka might want to provide their own KafkaConsumer. Right now this is not possible as consumer is created in the KafkaPartitionSplitReader which makes customisation impossible.
Proposal is to let users pass KafkaConsumerFactory when building the KafkaSource.
public interface KafkaConsumerFactory {
  KafkaConsumer<byte[], byte[]> get(Properties properties);
}

Builder will have a default implementation which creates the KafkaConsumer the same as it is done now.

Will add the javadocs. But first wanted to get the initial feedback if this makes sense.


Roll Flutter Engine from 1b132e44194d to d3edcc98582f (5 revisions)

https://github.com/flutter/engine/compare/1b132e44194d...d3edcc98582f
2023-02-04<EMAIL_ADDRESS>Roll Dart SDK from de912d108ebb to a507a9057730 (2 revisions) (flutter/engine#39385)
2023-02-04<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from _6bmpi47oMZC-msOI... to hcZFTTKMN0k4lXjfs... (flutter/engine#39384)
2023-02-04<EMAIL_ADDRESS>[fuchsia] Add output_path property to customize output path of .so files (flutter/engine#39007)
2023-02-04<EMAIL_ADDRESS>Roll Skia from 5d8a7ed8acfe to 8de8c6287254 (1 revision) (flutter/engine#39382)
2023-02-04<EMAIL_ADDRESS>Roll Skia from f083b79aa388 to 5d8a7ed8acfe (3 revisions) (flutter/engine#39381)
Also rolling transitive DEPS:
fuchsia/sdk/core/mac-amd64 from _6bmpi47oMZC to hcZFTTKMN0k4
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC bdero@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Add support for 1.19.3

Can you please update the plugin to 1.19.3?
This is the error I get when launching it:
[20:58:02 INFO]: [SmartSignEditor] Enabling SmartSignEditor v2.7.5
[20:58:02 ERROR]: [SmartSignEditor] The current server version is not supported!
[20:58:02 ERROR]: [SmartSignEditor] Your current version is v1_19_R2. This is a newer version that is still not supported. Ask the author to provide support for it!
[20:58:02 INFO]: [SmartSignEditor] Disabling SmartSignEditor v2.7.5

Support added for 1.19.3!


refactor(all): improve theming and CSS consistency

Please find here the WIP, targeting the ux-button component at the moment to improve theming and CSS consistency.
If you want to see it in practice, you can run the local app (detailed instruction in the main README)
cd app
npm ci
npm run dev

If you want to have quick look, here is a published dev version: https://ux.mintello.com
It should look like the GIF below and allow you to play with Aurelia UX core variables and ux-button theme properties and see the result live.

@ben-girardet Just wanted to say thanks for putting this together and that I haven't forgotten about it. I'm planning to review it this week.

@ben-girardet it'd be so nice, if we are able to use the test app, as some sort of e2e for the CI for ux. Would you be interested in writing some tests for this? So we have some thing that can guarantee things still work properly on the surface. Though I'm not sure which style of test we should be doing, e2e or just some integration

@bigopon I agree that would be very useful to have tests for Aurelia UX. However I don't have any experience whatsoever in E2E testing. If someone could put together a few tests as exemples I'm sure I could contribute and add more.
At the moment I use the test app to manually test things out. As I'm using the library in several projects I already have some ideas of issues that need to be addressed (hence this topic and PR).

@ben-girardet yes thats the plan, once this in, I will start a PR to set up test infra for the test app, then write some sample tests and we can start ramping up in this area. Should help greatly. For now, i think we have the luxury of doing manual testing

@bigopon I've merged your latest build-fix into this branch and PR.
It builds correctly for the components, but when I try to run the dev app, I get an error with npm ci

I've cleaned node_modules and app/node_modules before to try
I've followed the npm ci, npm run bootstrap, npm run build steps on project root
And then: cd app and npm ci which result in:

npm ci
npm ERR! aurelia-binding not accessible from @aurelia-ux/core

Any idea how to fix this ?

@ben-girardet can you try adding aurelia-framework to here https://github.com/aurelia/ux/blob/64ec9bb6566f3f05785881faf2f76a4e59bf3ee7/app/package.json#L30
Basically npm i aurelia-framework inside app folder`

That was it! Thanks @bigopon

@ben-girardet This is looking good. I'm quite happy with the approach. @serifine Do you have time to make a review? Any reason not to continue in this direction?

Sorry for the delay, it's been a very busy week for me. I just took a look at the changes so far and everything looks great to me! I think we can keep going this direction no problem.

Thank you @serifine. No need to apologize.
@ben-girardet Thanks again for this contribution. Just ping us when you are ready for final review before merge and we'll jump back in and move this forward.

@EisenbergEffect @serifine @bigopon
I ping you all to keep you up to date with how I move forward with this PR. I have to take some decisions along the way and I try to summarize theme here. Feel free to comment and help me navigate this issue with the best respect of web standards and Aurelia values.
Core

Add an alphaGrey swatch (https://github.com/aurelia/ux/pull/232/commits/60a69862b921cebc9b7e3836339e7b8805753c30)
Add a controlLabel style property (https://github.com/aurelia/ux/pull/232/commits/576d051a660e54b505aed91bf9dd1236d20d4f0d). This new property is used to set the default label color for controls and is also used in default border colors (depending on state)

Input (https://github.com/aurelia/ux/pull/232/commits/f64f1891dc084d569dc7e2ea86aba0010e714465)

Simplify the theme properties, especially:
Add an activeColor theme property (defaults to primary) to set the color of the input when active. This will be used for floating label, border, etc... I find that most of the time (if not all the time) there is only one active color needed and it would be painful to set labelActiveColor, borderBottomActive color and so on...
Add the option to have both filled and outline input (following material design guidelines)
For filled input, I do display a light bottom border by default (material guideline). This border will grow with scaling effect when input becomes active
When the input is not active, I default the bottom border to the controlLabel property
For outline input, the hover effect do not impact background but the border (so that the floating label can correctly hide the border at the top when going over the border). Therefore I default this border hover color to the controlForeground property

In essence, I try to follow material design as closely as possible and group styling properties when it makes the most sense. Let me know if you agree with the above decisions, need more informations or prefer to change things.
Demo Update

Next

So far I have added 3 new core properties: disabledBackground, disabledForeground and controlLabel. I think that they can really help designers to fine tune their global themes without needing to set specific values for each components. I would like to go further by adding an error property (most controls need an error color).
When ux-input looks good I plan to continue with the other control components

@ben-girardet This all looks great to me. Please continue 😄

Quick update:
ux-input
Small improvements, including:

error color default with core property (https://github.com/aurelia/ux/pull/232/commits/e93136d220b04ddf8e105743c9ace61ddd9bc5c5)
fix the observation of type change (https://github.com/aurelia/ux/pull/232/commits/fe43aac3f83a8635409d0397edd354290c17415e)

ux-input-info
Small improvements, including:

error color default with core property (https://github.com/aurelia/ux/pull/232/commits/e93136d220b04ddf8e105743c9ace61ddd9bc5c5)
fix ux-input-info counter (https://github.com/aurelia/ux/pull/232/commits/d31f0781b4e57628e917fa704f488276cb00338d)
use label color for counter instead of accent color (https://github.com/aurelia/ux/pull/232/commits/54718eb5a1feefceb09b862452ac76505242ce85)

ux-card
Small improvements and small new features, including:

use app background/foreground instead of control background/foreground default color (https://github.com/aurelia/ux/pull/232/commits/ad7ac6b122e5a1a131bcf524c0a6c2e11475a334)
add a class for header thumbnail ux-card__thumbnail(https://github.com/aurelia/ux/pull/232/commits/a1f96d1004c6fd6ad4bf3bc107d4b4b8cd174590)
add a class for card separator ux-card__separator (https://github.com/aurelia/ux/pull/232/commits/5e16f271d69a0977bc1b60acb66709aabb86e5b0)
no font definition in card css file (https://github.com/aurelia/ux/pull/232/commits/5e16f271d69a0977bc1b60acb66709aabb86e5b0)

Test App
Big refactoring, leading this app to become a useful design tool. Not only to test components, but for demo, showcase and theme design (https://github.com/aurelia/ux/pull/232/commits/584d9f4e431ca19e7f902c211e87a38d787b1b23)
See more here (WIP): https://ux.mintello.com

@EisenbergEffect  @serifine @bigopon
PR Status
I've made good progress with this PR. I've focused on 4 main components that I believe are ready for review.

button
input
textarea
select

In order to test and improve consistency, I've improved the dev app inside this project. Basically the idea is to have

a simple tool to create and customize themes
demo each component (good to test components on their own)
showcase scenarios where components are used together (good to test consistency accross components)

Using this tool one can easily test styles and states of each components. While developing all this, I've already started to improve other components such as

slider
card
chip
form

Even thought I don't consider these components ready for review.
Question
Is it possible to start reviewing the four main components mentioned above ?
And how can I help with the process ?
Preview
As earlier, I've published the dev app here: https://ux.mintello.com
And here are GIF previews:
1. Select and Create Themes

2. Core variables

3. Components settings

4. Components demo

5. Showcases

@ben-girardet thanks for the notification & the great work put into this. I will review soon

@ben-girardet We are so thrilled to have you working on this. The progress is fanatastic. Thank you!
As @bigopon we can definitely review the four components above right away. To help with the process, let us know if there are any specific details you want us to look at more closely or if there is any specific feedback you want. In other words, let us know how we can help you as well :)

My pleasure, looking forward to continue.
First of all I would like to make sure that I follow guidelines and standards.
As for specific details, I think I can spot a few areas that I feel more critical than others:
Core
Choice of new core variables. Do they all make sense and do you agree with my choices ?

https://github.com/aurelia/ux/pull/232/files#diff-b43a812f2f01bc3bed730585c13207b6

Fixes to how CSS are generated. I added tests so that when a property has "no value", the CSS rule is not generated (or removed)

https://github.com/aurelia/ux/pull/232/files?file-filters[]=.ts#diff-bec23c32ec6c0eb7a30a3d12c60a5f88
https://github.com/aurelia/ux/pull/232/files?file-filters[]=.ts#diff-fcf4a2a20243c0dd0324e7cdbf170a96

Input, Textarea, Select
Outlined / Filled. In material design, text fields have two types, filled and outlined. In the components I have used the bindable variant instead of type as type is already used for the ux-input types (text, number, ...). What do you think about this naming ?
@bindable public variant: 'filled' | 'outline' = 'filled';

https://github.com/aurelia/ux/pull/232/files?file-filters[]=.ts#diff-72b6aa053ed3248c275eba9feac250d9

As I write this, I already realize that the possible values should be filled and outlined
Detect background for outlined fields. For outlined fields (input, textarea, select), the floating label of outlined fields must go over the outline border and mask it with the same color than the surrounding. The background of the field must be transparent, and therefore in order to properly mask the border behind the floating label, we must find a way to detect the background of the surrounding elements. I think it would be good to have a close look to this solution and let me know if you have better ideas to solve this issue.

https://github.com/aurelia/ux/pull/232/files?file-filters[]=.ts#diff-72b6aa053ed3248c275eba9feac250d9

Select
@bigopon I think you know this component very well. Would be great if you have a close look to my changes.

@ben-girardet looks pretty awesome. Nice work! I left a few comments, few small nitpits to have better demo mainly, and a few Q for some components tidying up

@ben-girardet looks pretty awesome. Nice work! I left a few comments, few small nitpits to have better demo mainly, and a few Q for some components tidying up

Thanks for your review @bigopon . I've tried to reply to your comments. I'll publish fixes in a few hours I hope.

Looks good to me, one last Q related to the div for the border bottom effect. @ben-girardet nice work! Thanks for this

Looks good to me, one last Q related to the div for the border bottom effect. @ben-girardet nice work! Thanks for this

Thanks!
I'm planning to work on the remaining components soon. It souldn't take too long before I can call for final review. Thanks for your help in the process.

@ben-girardet no worries, glad that we got you working on this. Looking towards that call

@bigopon @EisenbergEffect
I've been working on ux-chip component and I'm calling for a review to help me ensure I'm going in the right direction. It's still WIP. Would you mind taking a look and let me know your thoughts
For reference
Chips Material Doc
To sum up my ideas

ux-chip: my goal is that this component can be used independently to display any kind of chip. I've added a thumbnail slot (as suggested in material doc) which is fully compatible with ux-icon and applying a default resize of the icons to make them fit perfectly the chip. All of this is customizable via the UxChipTheme.
filled and outline variants: As for the other input components, Material design offers two ways to display the component. I've added this option with the same naming than for input, select and so on...
ux-chip-choice: this is a new component that can handle the usage of chips for choices scenarios. The Material doc describe a few of these situations. It can handle single/multiple choices. My idea here is that the component behave like a smart slot for ux-chip component. The choice list is therefore defined by HTML markup (see below) with value bindable on the ux-chip component. It is quite similar to the select component.
The display of the choices can be inline, scroll or stack as suggested by the Material doc. The ux-chip-choice handles the three options via its type bindable.
ux-chip-input: this will stay the input component for values such as tags or any imputable chips. I haven't work on it yet so the styles are currently not quite nice.

ux-chip with icon markup
<ux-chip><ux-icon slot="markup" icon="person">User</ux-chip>
<!-- because the thumbnail is a slot, it can host other things than ux-icon, such as image or any kind of content -->

ux-chip-choice markup
<ux-chip-choice value.bind="stringProperty" type="inline">
  <ux-chip value="choice1">Choice 1</ux-chip>
  <ux-chip value="choice2">Choice 2</ux-chip>
  <ux-chip value="choice3">Choice 3</ux-chip>
</ux-chip-choice>

<ux-chip-choice value.bind="arrayProperty" multiple type="scroll">
  <ux-chip value="choice1">Choice 1</ux-chip>
  <ux-chip value="choice2">Choice 2</ux-chip>
  <ux-chip value="choice3">Choice 3</ux-chip>
</ux-chip-choice>

Link Preview
https://ux.mintello.com/#/showcase
Scroll the page to see the chips towards the bottom of the form example
Visual Preview

Related commits

https://github.com/aurelia/ux/pull/232/commits/b6b938e96a0421ee900eacf9a57a466b7ceef0fe
https://github.com/aurelia/ux/pull/232/commits/b8ecd8bc956a955e7669e084149d3b1a5b736927

Note regarding icons
All exemples use ux-icon from the component. However due to size we know that this component is not included by default. At the moment I do have a strong dependency with the icon component when the ux-chip-choice component is used in multiple mode (for the check icon). This can be fixed in the future by including the SVG for this icon in the ux-chip-choice component itself.
However, and this is not related to my current review request, I'm suggesting that we should implement a registering mechanism for icons (allowing users to register any icons they need in their projets) and ship the Aurelia UX library with an empty ux-icon component. Therefore we could have a strong dependency with our own ux-icon component and registering the few only necessary icons that we use in our components (such as calendar, check or cross). Naturally, these icons could be overwritten when user register their own icons. Hope that I make sense. We can tackle this question later, but wanted to side-note it here because I use the check icon.

@ben-girardet This is looking great. I agree on the icon proposal. Let's definitely move that to a registration mechanism so we can decouple things a bit and not take the hit when not needed. Regarding chip choice, I was wondering if we should have a generic list-box type of component. In that way people could use whatever markup they want for the list items, including chips. Thoughts?

Thanks for your feedback @EisenbergEffect
For the generic list-box type my concern is that the markup used inside the component needs to have some requirements:

a way to define the value (currently through a value bindable on ux-chip
a way to define the selected status (currently through a public property selected on ux-chip

If we accept other things than ux-chip (any markup) then we need to find a way to get the value of the element and define the selected status.
Ideas for the value:

get the inside text of the component (cons: we often want a different value than the label, especially with translated content)
use the .value property of the component (requiring this to be present in the element prototype)
other ideas ???

Ideas for the selected status:

applying a class to the element (cons: component might have specific things happened when being selected and the class might not be enough)
again, using a .selected property on the component which then must be present in the element prototype

Yet another solution would be to create a UxChoiceItem class with the value and selected properties and UxChip or other component that could be hosted by UxChoice must extends.
Your thoughts ?

I think we can have a generic UxChoice element, but let's also have an IUxChoice interface. Let the list box be able to work with anything that implements IUxChoice. Then have UxChoice implement that as well as UxChip. In this way you can put chips directly in the listbox but also anything else as long as it is wrapped in the choice element.

@EisenbergEffect
I’ll try to go this way. In summary:

A ux-choice-list component (list box) than can handle any elements implementing a IUxChoice interface
The IUxChoice interface define the value and selected
A ux-choice component implement IUxChoice interface
The ux-chip implements also the IUxChoice interface to make it work naturally with ux-choice-list

Now I need some guidance for the ux-choice component as I don’t see how it would look like visually.

For the visual, let's start with the lists design from Material: https://material.io/components/lists/# The example at the top basically just darkens the background of the selected item. We could also use the accent color to affect the border. There isn't an exact match. What do you think?

So what you mean then is that the ux-list-item should implement the IUxChoice interface and could be used for choices as well ?

Yes.

I figured that if our purpose is to have a generic way to manage choices across components the best way might well be with CustomAttributes. Here is a new proposal with this approach:

ux-choice-container attribute, with binding to the final choice value property
ux-choice attribute, with binding to each choice option property

Usage is very simple and can be applied to any HTML elements, see below. I've made some exemples:

Very minimalistic HTML markup
Using our ux-list component (as it is, just applying the attributes)
Using the chips and a new ux-chip-list component

Files:

ux-choice-container attribute file
ux-choice attribute file

Markup Exemples:
<!--  Chip Markup -->
<ux-chip-list type="inline" ux-choice-container.bind="priority">
  <ux-chip ux-choice="low">Low</ux-chip>
  <ux-chip ux-choice="medium">Medium</ux-chip>
  <ux-chip ux-choice="high">High</ux-chip>
</ux-chip-list>

Preview exemple:

What are your thoughts ?

@EisenbergEffect Forgot to mention you in my previous post

That's a pretty cool idea. Will it work if there's a repeater on the choice items?
@serifine @bigopon What do you all think?

That's a pretty cool idea. Will it work if there's a repeater on the choice items?

Yes it works with repeater @EisenbergEffect because each choice is responsible for registering itself to its choice-container when attached and dispose itself when detached.

@EisenbergEffect @bigopon @serifine Can I ask you guys for an important review ?
After working many hours improving consistency between components I realize that I keep repeating the same kind of styles between input components such as

input
select
datepicker
chip-input
and textarea

Moreover they all share some issues that still need to be fixed, for exemple the positioning of the floating labels and content when some variables changes. At the moment, it all work well with default values, but when font-size changes, or border width changes, then it doesn't look right anymore.
Therefore I'm coming now with a new proposal. Basically it would be very helpful to have a generic markup for these element, composed of a basic markup and according CSS styles.
Here is a list of requirements that I see from my recent experience:

Outer component with filled and outline style.
Inner zone for input area
Follow Material design
Floating labels if provided
Floating labels and content must adapt according to font-size and label font-size
Floating labels and content must adapt to component height (textarea or chip-input have variable height)
Floating labels and content must adapt to border width
Work well with any font family
Leading and trailing icons

I've put together a test page in the dev app of the project. You can find the link below. A few things I would like to mention first:

The goal of the generic CSS is to get the geometry right for each elements and set the default styles. Of course it will still be themable from each component like it is now
The plan is to keep the markup of the current components very similar to the actual one. In fact it should be exactly the same, but we would just add some classes. For exemple the ux-input component would still have its ux-input class but also receive the ux-input-component class to get the styles from the generic CSS
I'm expecting to be able to significantly reduce the CSS footprint of the components as we will avoid quite a few repetitions
In order to apply the theme styles of a component it would now look like:

/* ux-input.css */
.ux-input {
  --background: var(--aurelia-ux--input-background);
  --foreground: var(--aurelia-ux--input-foreground);
  /* ... */
}

/* with the generic variables sets it will affect each parts using the generic styles */

Links:

Demo page: https://ux.mintello.com/#/ux-generic-component
Related commit

What do you guys think ?

Do you think that having a generic set of CSS is the right way to go ?
Do you see other requirements ?
Would really appreciate your comments on the code as it would become a central piece in the library

I like the idea. One requirement that I would add is to not let the element change size when selected. Currently in your demo, if you click on the component the content shifts ever so slightly, about a pixel or two. This is even more apparent in the outlined version.

@ben-girardet arr love your innovation here, thanks for the work.
For ux-choice, I think we should inject the parent instead of relying on tree walking, as it may yields incorrect result (imagine slot scenarios, where the <ux-choice/> will be moved elsewhere.
And we have a resolver for this purpose: optional, so it will be like this:
import { Optional } from 'aurelia-dependency-injection';

@customAttribute('ux-choice')
@inject(Element, Optional.of(UxChoiceContainer)
export class UxChoiceAttribute {

If it's put in a path without any UxChoiceContainer then we get null as 2nd parameter in the constructor, which is good for our early setup.
For the floating label, I think it's pretty good, maybe we can recognize some pattern and will be able to provide some doc for folks how to do the positioning properly as a result as well. Amazing work!

For ux-choice, I think we should inject the parent instead of relying on tree walking, as it may yields incorrect result (imagine slot scenarios, where the <ux-choice/> will be moved elsewhere.
And we have a resolver for this purpose: optional, so it will be like this:

This is brilliant @bigopon  !! I didn't know about the Optional resolver, such a useful thing. Fixed here: https://github.com/aurelia/ux/pull/232/commits/39b61356a937e62eb5a667be7ee3a26f169c1ee1

One requirement that I would add is to not let the element change size when selected. Currently in your demo, if you click on the component the content shifts ever so slightly, about a pixel or two. This is even more apparent in the outlined version.

Absolutely @serifine It's even more visible with bigger font-size.

@EisenbergEffect @bigopon @serifine
I've updated the generic component and the demo page. In my opinion now it fits the requirement and provide a solid base to build input components upon.
Would you mind having a look and give me a thumb up if you think I can go ahead and use these styles in the input components.
As for the .css file that will need to be required I'm planning to place it in the core component as it could be needed by several other components I think it makes sense.
Bonus: I've added a dense option as suggested by material design. Now that everything is calculated using CSS vars it makes it easy to do.

@ben-girardet for ux choice, its registering too late, if theres no particular reason for this, can we register the choice during constructor or bind? For better timing & control, the earlier something is guaranteed to happen, the better I feel. Especially when its the list based UI like this

@ben-girardet I agree with @serifine I think this is a great way to do; just need to address the shifting issue. Keep up the great work!

@ben-girardet for ux choice, its registering too late, if theres no particular reason for this, can we register the choice during constructor or bind? For better timing & control, the earlier something is guaranteed to happen, the better I feel. Especially when its the list based UI like this

@bigopon good feedback
I think on bind we have the right balance as then we know that the choice as its value bound and then the choice-container can attribute the correct selected value
Fix: https://github.com/aurelia/ux/pull/232/commits/35a0232d6ff1b8d93fdc318f13931d6b03b878d7

@bigopon @EisenbergEffect @serifine
Regarding the ux-choice custom attributes I have two questions.
1. Where should we place these attributes ?
I feel like they belong to the core package as they can be used in several other packages. Except if we prefer to create a separate choice package in the mono-repo ?
2. Naming ?
Currently I have called the two attributes:

ux-choice-container
ux-choice

The naming fits the visual appearance but I feel like it doesn't suit well the function. I have two other suggestions and would appreciate your feedbacks:

ux-choice
ux-choice-item

Pros: similar to ux-list concept
Cons: ux-choice can be confusing

ux-choice-value
ux-choice-option

Pros: with the word value in the container attribute we better understand that this attribute will hold the final choice. When binded it would look like ux-choice-value.bind="..." which is pretty easy to understand
Cons: feel like it's a bit wordy

@bigopon @serifine @EisenbergEffect
I've now migrated all the input components under a unified interface and css (filled, outline). I'm very happy with the result and the great consistency between components.
I'm reaching the end of what I wanted to achieve through this PR (hence not WIP anymore)
Looking forward to your feedbacks and review.
Demo:
Still  available here: https://ux.mintello.com/#/showcase.
Enjoy the new Label position demo
Questions left opened
See here: https://github.com/aurelia/ux/pull/232#issuecomment-582893024

Tested the app on mobile, looks really good to me. Beside the flickering of border when focused vs when not, it's amazing. is it possible to use outline to simulate the effect of bolder border?

Tested the app on mobile, looks really good to me. Beside the flickering of border when focused vs when not, it's amazing. is it possible to use outline to simulate the effect of bolder border?

What if I use the same DIV than for the bottom border in filled variant? Then I would not hide it with if.show but use it to create an inset absolute full width/height border in pure CSS. As an absolute inset it would not alter the DIV size/position

@bigopon here is my new proposal to remove border flickering in outline mode:
https://github.com/aurelia/ux/pull/232/commits/8f751ac1bec675688695886de204380b40754982
I also fixed your other change requests

@ben-girardet awesome, thanks.
@EisenbergEffect I think i have no further comments to add. We will to address any issues that come up later.
Looking at the demo again, I think, after this PR, it's reasonable that we include customized scrollbar in our themes too. It needs to cater for both chrome (webkit pseudo selector based solution) and firefox (css rules based). thoughts?

Ok, @ben-girardet ready for merge?

The packages part is ready.
The app part has a small issue at the moment if someone want to build and run the app. It lacks ‘aurelia-framework’ and ‘aurelia-validation’ dependencies. I tried to include the change by running npm install for these packages and push the package.json and package-lock.json but then it broke the install process somewhere and someone pulling the repo would not be able to install properly. I wonder if @bigopon could give me a hand fixing this? Could be before or after merging...

@EisenbergEffect
Found the fix. Basically just needed to update the package.json and package-lock.json files.
It is now ready for merge.
I suggest that we first merge this PR and then:

I will rebase my branch for the ux-icon PR before merging this one
I should probably also write a few comments regarding the breaking changes and updates of this PR ?

@ben-girardet Sounds great. Yes, if you can add a little section to this PR description with the breaking changes, I can directly translate that to the release notes. Just ping me after that addition and I'll get this merged. Then let me know when ux-icon is ready and I can merge that too. After that, we can do a new release with all the great new work together. Awesome job!

This PR improves theming and consistency accross components. Find below a list of the major changes:
Core
New properties available in ux.design :

surfaceBackground : set here main surface background/foreground, esp. for cards
surfaceForeground
controlLabelColor : set here the default label color for all controls
disabledBackground : set here the default background/foreground for all disabled states
disabledForeground
error : set here the default error color
onError : this one is available for when you need to write text on top of a surface using the error color. It is currently not used in Aurelia UX components

Input Controls
Components that act as an input control are now more consistent and can be themed like Material Design components. Here are some cool stuff available:
Themable properties (same for all input-like components)

foreground
foregroundLabel
background
backgroundHover
activeColor
fontSize
letterSpacing
labelFontSize
labelLetterSpacing
lineHeight
labelLineHeight
borderColor
borderRadius
borderWidth
borderActiveWidth
disabledForeground
disabledBackground
error

Filled, Outline, Dense

change the style of the input with filled or outline variants (exemple <ux-input variant="outline"></ux-input>
Reduce the visual impact of the input with dense: (exemple <ux-input dense></ux-input>

Floating Labels or Placeholder

Floating labels are the default way, but you can choose:
Use the label bindable for floating labels
Use the placeholder bindable for labels that disappear when field has a value
Use the <ux-field><label>...</label><ux-input>...</ux-input></ux-field> markup for labels that stay on top of the field all the time

Leading and Trailing Icons

All input controls host leading and trailing icons slots. The trailing icon is deactivated for ux-select and ux-datepicker due to the arrow and calendar icons present in the control by default
Exemple: <ux-input><ux-icon icon="person" slot="leading-icon"></ux-input>

Affected components:

ux-input
ux-textarea
ux-select
ux-datepicker
ux-chip-input

Button

Removed some theme properties: flatBackground, flatForeground, textBackground, textForeground, outlineBackground and outlineBorder. Each of this colors now derived from background and foreground or accentBackground and accentForeground
Renamed backgroundDisabled and foregroundDisabled in disabledBackground and disabledForeground

Card
New ux-card-separator component.

This component makes it easy to add separator in cards (see Material Design guidelines)
By default it adds a vertical margin (up and down) of the separator. You can disable this margin with no-margin attribute.
You can include the separator between cards parts (header and content for exemple) or inside the content. It will adjust its width accordingly

Defaults to surface colors

Cards default color properties are now defaulted with the new surfaceBackground and surfaceForeground design properties.

New .ux-card__thumnail class
Checkbox and Radio

Removed disableBorder theme property
Replaces checkedBackground and checkmarkColor by activeColor
Add the indeterminate state

Chip-Input

New ux-chip-list component
ux-chip-input theme supports now all the new control theme properties
ux-chip now have a selected state (bindable)
ux-chip also supports variants such as filled or outline
ux-chip now have a thumbnail slot for icon or avatar purposes

Slider

Add new trackHeight theme property
Mobile-friendly: now works with touch gestures

New Custom Attributes
The new ux-choice-container and ux-choice-item can be used to make any markup act as a selector component. It works works particularly well with ux-list or ux-chip-list but you can use them anywhere. Here are two exemples:
<!-- bind a property to the ux-choice-container attribute to get the value of the choice -->
<!-- bind a property to the ux-choice attribute to give it its choice value -->
<ux-chip-list ux-choice-container.bind="labelPosition">
  <ux-chip variant="outline" ux-choice="floating">Floating</ux-chip>
  <ux-chip variant="outline" ux-choice="placeholder">Placeholder</ux-chip>
  <ux-chip variant="outline" ux-choice="top">On Top</ux-chip>
</ux-chip-list>

<!-- If the binded property in ux-choice-container is an array, then the selector will allow multiple choices -->
<ux-chip-list type="inline" ux-choice-container.bind="region">
  <ux-chip variant.bind="variant" ux-choice="basel">Basel</ux-chip>
  <ux-chip variant.bind="variant" ux-choice="bern">Bern</ux-chip>
  <ux-chip variant.bind="variant" ux-choice="geneva">Geneva</ux-chip>
  <ux-chip variant.bind="variant" ux-choice="lausanne">Lausanne</ux-chip>
  <ux-chip variant.bind="variant" ux-choice="zurich">Zürich</ux-chip>
</ux-chip-list>

@EisenbergEffect please find above my comment regarding this PR.

@ben-girardet All merged. Congratulations! I've got the notes recorded. Let me know when the other PR is ready and we'll get that merged and release the packages.


Keybindings don't play nice on Win10 1809 + PSReadline 2.0

Looks like one of the keybindings scripts on 2.0.0 of PSUtil sets expand alias to spacebar. I can look into it more later, but figured I'd file the issue now. at first sight it appears like line 2 of expandAlias.ps1 at
(Get-PSFConfigValue -FullName psutil.keybinding.expandalias -Fallback 'Shift+Spacebar')
See below for an example of the behavior
PS C:\repos> 'look at spaces'
look at spaces
PS C:\repos> ipmo psutil
PS C:\repos> 'nospaces'
nospaces
PS C:\repos> Get-PSReadLineKeyHandler

#trimmed for brevity
User defined functions
======================

Key    Function      Description
---    --------      -----------
F1     CommandHelp   Open the help window for the current command
Ctrl+C CopyAllLines  Copies the all lines of the current command into the
                     clipboard
Space  ExpandAlias   Converts aliases into the resolved command / parameter
F7     History       Show command history
Alt+w  SaveInHistory Save current line in history but do not execute

Looks like this is related to this Issue in PSRL: https://github.com/lzybkr/PSReadLine/issues/719
To remove it without a reload: Remove-PSReadLineKeyHandler When prompted for chord to remove, hit the space bar. Hit <enter> twice and bam you can not hit space again 😃


GUI breaks dramatically when window is resized

The issue looks to much of the gui having a wrong set of UVs, text seems to continually work as expected.
No know way to reproduce as off now.

@stevensona I totally goofed and created an issue on the wrong project. Can you do me the favour and delete this one?

@Malacath92 Github doesn't support deleting issues, but I'm not worried about it.


"mangle.exclude" doesn't seem to exclude the namespaces

Hi. I'm using the latest version of this package - 0.2.0.
Issue
Providing mangle.exclude doesn't exclude the given class/method names from being mangled.
Minify options
new BabelMinifyPlugin({
      removeConsole: true,
      mangle: {
        topLevel: true,
        exclude: {
          /* I need to preserve the names of the classes listed below */
          'FormProvider': true,
          'Form': true,
          'connectField': true,
          'Condition': true,
          'Field': true
        }
      }
    })

Environment

Node: v6.9.5
OS: MacOS Sierra (10.12.6 (16G29))

Reproduce

Clone/fork my repository.
Checkout to dev/bundle-size branch if not there already.
Run npm run build to build the project in production mode
Examine the output bundle - excluded namespaces are still mangled.

Please help me resolve this issue. Thanks.

@kettanaito Thanks for issue, you just use invalid configuration - use minifyOptions: { ... } for mangle option, see https://github.com/webpack-contrib/babel-minify-webpack-plugin#pluginopts

@evilebottnawi thanks for the reply!
To be honest, I would like to see at least one working example. Even what you've posted right now doesn't make much sense to me:
Here's how to use the plugin from its README:
new MinifyPlugin(minifyOpts, pluginOpts)

How I'm using it:
new MinifyPlugin({
  removeConsole: true,
  mangle: { ... }
})

You suggest I should use minifyOptions, which I do - that's the Object which the plugin accepts as the first argument, isn't it?
removeConsole and removeDebugger, which are minifyOptions, if I get it correctly, work properly when passed as I am passing them. That makes it valid to assume the first Object is a minifyOptions.
Please, could you clarify this? It feels like there's no clear explanation how to pass those options.
Thanks.

@kettanaito sorry, you are right, you have valid config, i reopen issue, but seems it is not related to plugin, we just pass option to babel using babel-preset-minify

@evilebottnawi thanks!
Regardless, what do you think about adding at least one real-world example to this repo? That would help a lot, from my experience.

@kettanaito agree, PR welcome, many work right now


Antrea running as a service on windows

Describe the problem/challenge you have
While we wait for HostNetworking on Windows, Antrea for Containerd (like other CNIs) must run as a host process, making it critical that this stays up and is tolerate to restarts.  I would like to make sure that the antrea agent and kube-proxy are able to be installed as services rather than running the start.ps1 script manually.  Nssm seems to be the most adopted way of doing this with other host services such as the Kubelet so we would like this to happen with the cni components.  Please can we get a "supported" way for this documented/automated?  Also is there a way that we can allow the node kubelet.conf to get access to the resource required to make kube-proxy and antrea agent setup, or is this opening too many security vulnerabilities?
Describe the solution you'd like
An example of this would be
mkdir c:/var/log/antrea
mkdir c:/var/log/kube-proxy
& nssm install kube-proxy "c:/k/kube-proxy.exe" "--proxy-mode=userspace --kubeconfig=C:/etc/kubernetes/kubelet.conf --log-dir=c:/var/log/kube-proxy --logtostderr=false --alsologtostderr"
& nssm install antrea-agent "c:/k/antrea/bin/antrea-agent.exe" "--config=c:/k/antrea/etc/antrea-agent.conf --logtostderr=false --log_dir=c:/var/log/antrea --alsologtostderr --log_file_max_size=100 --log_file_max_num=4"
& nssm set antrea-agent DependOnService kube-proxy ovs-vswitchd
& nssm set antrea-agent Start SERVICE_DELAYED_START
start-service kube-proxy
start-service antrea-agent

Anything else you would like to add?
The need for this may go away once we have a windows equivalent privileged container as that will force the pod onto the host network but until that happens this remains an issue for people on containerd or those who would like to avoid using wins.

/sig windows

At minimum, & nssm set kube-proxy DependOnService tcpip afd
although we might discover other minimal service dependencies.
Is this also worthwhile? & nssm set kube-proxy Start SERVICE_AUTO_START
One advantage to nssm is that stderr (stdout, even stdin) can be piped, e.g.
& nssm set antrea-agent AppStderr C:/var/log/antrea/stderr.log
& nssm set kube-proxy AppStderr C:/var/log/kube-proxy/stderr.log
Although I see the combination of --logtostderr=false and --alsologtostderr, this covers the executable startup edge cases where an error occurs before or during command line parsing, any time prior to the log initialization phase.
[cc @jayunit100 (this solves an issue we recently discussed)]


migration: cortex.cpp as a mono repository

Should we submodule cortex.onnx, cortex.llamacpp, cortex.tensorrt-llm?

Let's keep the engines as separate repos for now, we can revisit this in the future.

cortex.llamacpp
cortex.onnx
cortex.tensorrt-llm


Fixing Errors when building documentation via tox commands without Notebooks

Hello,
This PR aims to Fix #1186
This PR implements hardcoded nbsphinx thumbnails which successfully fixes the non-generation of the thumbnails for the notebooks.
Thanks :)

Hey @astrojuanlu, I have made some changes to the way the notebook thumbnails are generated. Would love to have a review on the same :)

Thumbnail for Revisiting Lambert's problem is not working ... Investigating on the same 🔍

Hey @DhruvSondhi All Tests Were Occurred Correctly :),Although py_38 test is failing which I think occurred by Reopening this PR.

I wonder if we want to hardcode the thumbnails like this though, we lose some of the dynamism.

Probably the dynamism can be kept by ignoring the warnings?
See https://github.com/poliastro/poliastro/issues/1186#issuecomment-866167372.

Correct! I very much prefer that approach. Closing this in favor of https://github.com/poliastro/poliastro/issues/1186#issuecomment-866342753, thanks again @mgeier


⚠ Bofrost.com has degraded performance

In 74398ac, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 614 ms

Resolved: Bofrost.com performance has improved in 13b4f89 after 9 minutes.


Re-Drawing charts on resize, avoids charts going beyond viewport.

Hello Keen,
Feature : issue #61
Redrawing charts on resize to avoid the charts to span beyond the viewport.
Has only been done in one example so far, but the resize function can be moved to a global js file, so that all charts are redrawn.
When the drawCharts() function is moved up a level of scope and invoked by the Keen.ready() function it fires an error
Uncaught TypeError: Cannot read property 'apply' of undefined  (keen.min.js)
This is something I haven't been able to figure out and would like to know what it's expecting.
It's my first fork, I'll be more than happy to fix any errors if they arise : ]
Cheers!

@UiCandy thanks for putting this in. Keen.ready requires a function as an argument, so perhaps this would work:
Keen.ready(drawCharts);

https://github.com/UiCandy/dashboards/blob/bfda1e0491a56af3848824a1c72bdecba959b9e3/examples/military-surplus-flow/military-surplus-flow.js#L68-L70

How is this going? Any chance to merge it?

Hello Alexander, you can use it locally as it is barely 2-3 lines of code. : )

@UiCandy Yeah, but having it merged in upstream is always better.

+1. Can’t disagree with that one. : P
Sent from Windows Mail
From: Alexander Nestorov
Sent: Sunday, February 22, 2015 8:56 PM
To: keen/dashboards
Cc: Rishav Sharma
@UiCandy Yeah, but having it merged in upstream is always better.
—
Reply to this email directly or view it on GitHub.


colors for metrics

Let's add colors to all metrics, to indicate their quality (red, green, yellow).

Manual assignment of issues is discouraged, see par.19: -5 points just awarded to @yegor256, total is +4110.

Job gh:yegor256/jpeek#12 assigned to @yegor256, please go ahead (policy).

Oops! Job gh:yegor256/jpeek#12 is already assigned to @yegor256, sorry.

Bug was reported: +15 points just awarded to @yegor256, total is +4125.

Job gh:yegor256/jpeek#12 is now out of scope.

Order was successfully finished: +30 points just awarded to @yegor256, total is +4245.


Prism only highlights first code segment on web page in Chrome on Android when including copy to clipboard plugin

I found this out through trial and error.  If I download PrismJS with the copy to clipboard plugin enabled, it only highlights the first section of code on a page with multiple different sections of code on it.  But it only fails in Chrome for Android.
It works on Firefox for Android and if I remember correctly even the Android native browser, and it works on Firefox, Edge and Chrome on a Windows desktop machine.
This failed on three different android devices - 2 identical tablets and a phone.
I did lots of troubleshooting via trial and error, and finally found that when I did not use that plugin, it worked fine.

I'm not sure I follow. It should only copy the current snippet, not all snippets on a page.

@aeoril Do you have an example page online reproducing the issue?

@Golmote Yes:
https://aeoril.github.io/2017-08-19-center-animated-css-3D-cube-in-page-test.html
Github:
https://github.com/aeoril/aeoril.github.io/blob/master/2017-08-19-center-animated-css-3D-cube-in-page-test.html
I am using the Coy theme with it.

@mAAdhaTTah It is not the copy to clipboard functionality that is in question.  The syntax highlighting on the web page itself is the problem.  When I include that plugin, on Chrome on Android and only on Chrome on Android (of the ones I can try), the first code snippet is highlighted on my web page but the others are not.

@mAAdhaTTah @Golmote here is a screenshot:

I'm able to reproduce this on my phone now. And you're saying this highlights both correctly when not using copy-to-clipboard?

Also, what version of Chrome Mobile are you using (Settings -> About Chrome)?

Just to eliminate any relationship to #1181, can you add this script tag right before the prism.js:
<script src="https://cdnjs.cloudflare.com/ajax/libs/clipboard.js/1.5.8/clipboard.min.js"></script>

Chrome version 61.0.3163.98 on my phone.
Yes, it works fine when I do not download the copy-to-clipboard plugin from the download page, but that also downloads the toolbar plugin automatically, and I deselected both in my testing to make it work.
Just to be sure, you are able to reproduce this problem on your phone?
I will try to get to further testing as you suggest above when I have time, but if you want to alter the code and test it yourself, everything is on my github repo:
https://github.com/aeoril/aeoril.github.io

@aeoril The example page you provided does not work properly in Chrome desktop either.
@mAAdhaTTah I'm pretty sure it's the same error as #1181

@mAAdhaTTah thx, That helped
<script src="https://cdnjs.cloudflare.com/ajax/libs/clipboard.js/1.5.8/clipboard.min.js"></script>

@Golmote @mAAdhaTTah It works fine for me on Chrome for Desktop.  What OS are you using for Chrome for Desktop?  What version of Chrome for Desktop?
I can use the copy buttons fine, without any console errors in the dev tools.  Here is a screenshot of Chrome Desktop (Version 60.0.3112.113 (Official Build) (64-bit)) with that page up after a hard refresh (Ctrl-Shift-R):

@Golmote @mAAdhaTTah Adding the line you suggested above fixed the problem:
https://aeoril.github.io/prism-troubleshooting.html

@aeoril Yes the problem occurs only on Chrome 61+. Refer to #1181 from now on. I'm closing this issue as a duplicate.


Instead of throwing "Path too long" error, Expand-Archive throws errors about removing non-existing items

When expanding an archive that contains long file paths to a location that also has a long path, the files to be expanded may have a resulting path that causes an error because it is too long.
When using "Expand All" from within Windows, this results in

Error 0x80010135: Path too long

The same should occur when running Expand-Archive in PowerShell, but what happens instead is that errors are thrown from Remove-Item on this line:
https://github.com/PowerShell/Microsoft.PowerShell.Archive/blob/c9fc2b3a303ae6471bf751e6451182fd8835ef40/Microsoft.PowerShell.Archive/Microsoft.PowerShell.Archive.psm1#L408

Remove-Item : Cannot find path {...} because it does not exist.

It appears that this line of code is meant to clean up after a failed expansion, but it is trying to remove items that it hasn't expanded yet, so this would indicate another issue.

I am experiencing the same problem exactly; it is amazing that these windows 95 era path limitation problems are still around 20+ years later.

FYI: There is a workaround for this issue: instead of using Expand-Archive, use 7-zip.
Following this suggestion worked in our environment: https://stackoverflow.com/a/58289112/1009693
Name                           Value
----                           -----
PSVersion                      5.1.14393.3866
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.3866
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

We will reopen this issue if it is still persistent.

This issue still occurs

Jep Chap can confirm. Still exists. Whats the reason behind .zip?

@ayousuf23 please reopen

@SydneyhSmith please reopen

Ongoing issue for me please resolve


Enable importing SVG

closes #118
What's Changing and Why
Adding a means to import SVG files and render them.
This is just an initial proof of concept at the moment, because the workflow for allowing pre-render manipulation of SVG is a lot more complicated than any other plugins or type support currently implemented, and needs some more thought put into it.
In it's current state it also node-only since its imports of node polyfills for canvas, xml, and fetch are not dynamically applied by platform. And a few method calls would have to change depending on the platform as well.
What else might be affected
Nothing I can think of.
Tasks

[ ] Add tests
[ ] Update Documentation
[ ] Update jimp.d.ts
[ ] Add SemVer Label

I'm not sure that jimp support svg makes all the much sense. I can see that case for decode it into a bitmap. But encoding seems like it's impossible. jimp lets you convert from one format to another. converting a raster image to vector seems like a much bigger thing than jimp sets out to solve


Regression from closed source: Many 0-length frames in decoding

The open source media for mobile library appears to regress from the old JAR we had. On transcoding using my Nexus 6, we're finding many video frames are now decoded as 0-length. The final, transcoded video then has many dropped frames and the audio presentation timestamps go backwards at each dropped frame. Reverting to the JARs of version 1.2.2675 fixes this regression for us.
We cannot easily pinpoint the source of this regression because the open source library was committed without history.

Thank you for reporting this issue, we will take a look at it.
Could you clarify the origin of the input video stream? Was it recorded using phone's camera or copied from other source? If you could share the stream, it would help.

Yes, we simply imported the video from an mp4 movie file. I'll attach it.
VidkuHQsnowstorm.mp4.zip

For parameters, we were changing the video from 1080x1920 to 720x1280. Rotation 0.


How do I set the client?

I'm getting a response, that the client is invalid, when using the oauth2 gem, as opposed to using cURL. Here is my cURL command, which works:
curl -i http://movis.dev/oauth/token \
-F grant_type=client_credentials \
-F client_id=92645627ec318278c2d7f94271e858f5c02d313226a0764ffbf7ade196e86b84 \
-F client_secret=d21c63732ee2a2ea7bada0192a2387d571dc713de587f3094b2b890067b9bafc \
-F username=emil \
-F password=hej

And here is my implementation of the oauth2 client:
client_id = params[:client][:id]
client_secret = params[:client][:secret]
client = OAuth2::Client.new(client_id, client_secret,
  site: "http://movis.dev")

username = params[:user][:username]
password = params[:user][:password]

access_token = client.password.get_token(username, password)

The last of those lines raises this error:
#<OAuth2::Error: invalid_client: Client authentication failed due to unknown client, no client authentication included, or unsupported authentication method.
{
  "error":"invalid_client",
  "error_description":"Client authentication failed due to unknown client, no client authentication included, or unsupported authentication method."
}

So my question is: How do I set the client on the oauth object.

This was not an issue with Oauth2


have chatbox open without clicking the launcher button

Hello,
I'm not sure if this is the place to post this since it's not an "issue", but is there a way that I can have the chat window open when the page loads, rather than having to click the launcher button for it to open?

Greetings! That's actually a "feature" I've been thinking about, so surely it will be added in the next version. For now, I can offer you a more jQuery-ish solution:
document.getElementsByClassName('launcher')[0].click()

Thanks for the heads up! :smile:

This feature request has been addressed in v2.1.0


MacOS Installation Issues

Greetings,
We are running into issues installing biomage-utils on a M2 Mac running Ventura (macOS 13.6 - 22G120 with kernel version 22.6.0) and Python-3.11.6 managed by Homebrew.
Here is the output from a failed attempt.  Please advise if there is any additional data we can provide.

❯ make install
==> Cleaning up...
    [✓]

==> Creating virtual environment...
    [✓]

==> Installing utility and dependencies...
Requirement already satisfied: pip in ./venv/lib/python3.11/site-packages (23.2.1)
Collecting pip
  Obtaining dependency information for pip from https://files.pythonhosted.org/packages/47/6a/453160888fab7c6a432a6e25f8afe6256d0d9f2cbd25971021da6491d899/pip-23.3.1-py3-none-any.whl.metadata
  Using cached pip-23.3.1-py3-none-any.whl.metadata (3.5 kB)
Using cached pip-23.3.1-py3-none-any.whl (2.1 MB)
Installing collected packages: pip
  Attempting uninstall: pip
    Found existing installation: pip 23.2.1
    Uninstalling pip-23.2.1:
      Successfully uninstalled pip-23.2.1
Successfully installed pip-23.3.1
Obtaining file:///Users/rmarable/src/scicomp/biomage/biomage-utils
  Installing build dependencies ... done
  Checking if build backend supports build_editable ... done
  Getting requirements to build editable ... done
  Preparing editable metadata (pyproject.toml) ... done
Collecting anybase32==1.1.0 (from biomage-utils==0.0.1)
  Using cached anybase32-1.1.0.zip (3.4 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting blessed==1.19.1 (from biomage-utils==0.0.1)
  Using cached blessed-1.19.1-py2.py3-none-any.whl (58 kB)
Collecting boto3==1.17.93 (from biomage-utils==0.0.1)
  Using cached boto3-1.17.93-py2.py3-none-any.whl (131 kB)
Collecting botocore==1.20.93 (from biomage-utils==0.0.1)
  Using cached botocore-1.20.93-py2.py3-none-any.whl (7.6 MB)
Collecting biomage-programmatic-interface==0.0.39 (from biomage-utils==0.0.1)
  Using cached biomage_programmatic_interface-0.0.39-py3-none-any.whl (9.3 kB)
Collecting backoff==2.2.1 (from biomage-utils==0.0.1)
  Using cached backoff-2.2.1-py3-none-any.whl (15 kB)
Collecting certifi==2021.10.8 (from biomage-utils==0.0.1)
  Using cached certifi-2021.10.8-py2.py3-none-any.whl (149 kB)
Collecting cffi==1.15.0 (from biomage-utils==0.0.1)
  Using cached cffi-1.15.0.tar.gz (484 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting cfn-flip==1.2.3 (from biomage-utils==0.0.1)
  Using cached cfn_flip-1.2.3.tar.gz (10 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting chardet==4.0.0 (from biomage-utils==0.0.1)
  Using cached chardet-4.0.0-py2.py3-none-any.whl (178 kB)
Collecting click==8.0.1 (from biomage-utils==0.0.1)
  Using cached click-8.0.1-py3-none-any.whl (97 kB)
Collecting deepdiff==5.5.0 (from biomage-utils==0.0.1)
  Using cached deepdiff-5.5.0-py3-none-any.whl (66 kB)
Collecting Deprecated==1.2.13 (from biomage-utils==0.0.1)
  Using cached Deprecated-1.2.13-py2.py3-none-any.whl (9.6 kB)
Collecting idna==2.10 (from biomage-utils==0.0.1)
  Using cached idna-2.10-py2.py3-none-any.whl (58 kB)
Collecting inquirer==2.10.1 (from biomage-utils==0.0.1)
  Using cached inquirer-2.10.1-py3-none-any.whl (17 kB)
Collecting jmespath==0.10.0 (from biomage-utils==0.0.1)
  Using cached jmespath-0.10.0-py2.py3-none-any.whl (24 kB)
Collecting numpy==1.22.0 (from biomage-utils==0.0.1)
  Using cached numpy-1.22.0.zip (11.3 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting ordered-set==4.0.2 (from biomage-utils==0.0.1)
  Using cached ordered-set-4.0.2.tar.gz (10 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting pandas==1.3.4 (from biomage-utils==0.0.1)
  Using cached pandas-1.3.4.tar.gz (4.7 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting prompt-tool-kit==1.0.14 (from biomage-utils==0.0.1)
  Using cached prompt_tool_kit-1.0.14-py3-none-any.whl (242 kB)
Collecting prompt-toolkit==1.0.14 (from biomage-utils==0.0.1)
  Using cached prompt_toolkit-1.0.14-py3-none-any.whl (248 kB)
Collecting pycparser==2.21 (from biomage-utils==0.0.1)
  Using cached pycparser-2.21-py2.py3-none-any.whl (118 kB)
Collecting PyGithub==1.55 (from biomage-utils==0.0.1)
  Using cached PyGithub-1.55-py3-none-any.whl (291 kB)
Collecting Pygments==2.11.1 (from biomage-utils==0.0.1)
  Using cached Pygments-2.11.1-py3-none-any.whl (1.1 MB)
Collecting PyJWT==2.3.0 (from biomage-utils==0.0.1)
  Using cached PyJWT-2.3.0-py3-none-any.whl (16 kB)
Collecting PyNaCl==1.4.0 (from biomage-utils==0.0.1)
  Using cached PyNaCl-1.4.0.tar.gz (3.4 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting python-dateutil==2.8.2 (from biomage-utils==0.0.1)
  Using cached python_dateutil-2.8.2-py2.py3-none-any.whl (247 kB)
Collecting python-editor==1.0.4 (from biomage-utils==0.0.1)
  Using cached python_editor-1.0.4-py3-none-any.whl (4.9 kB)
Collecting pytz==2021.3 (from biomage-utils==0.0.1)
  Using cached pytz-2021.3-py2.py3-none-any.whl (503 kB)
Collecting random-name==0.1.1 (from biomage-utils==0.0.1)
  Using cached random_name-0.1.1.tar.gz (4.7 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting readchar==4.0.3 (from biomage-utils==0.0.1)
  Using cached readchar-4.0.3-py3-none-any.whl (8.4 kB)
Collecting regex==2021.11.10 (from biomage-utils==0.0.1)
  Using cached regex-2021.11.10.tar.gz (702 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting requests==2.25.1 (from biomage-utils==0.0.1)
  Using cached requests-2.25.1-py2.py3-none-any.whl (61 kB)
Collecting ruamel.yaml==0.17.21 (from biomage-utils==0.0.1)
  Using cached ruamel.yaml-0.17.21-py3-none-any.whl (109 kB)
Collecting ruamel.yaml.clib==0.2.7 (from biomage-utils==0.0.1)
  Using cached ruamel.yaml.clib-0.2.7-cp311-cp311-macosx_13_0_arm64.whl.metadata (2.2 kB)
Collecting s3transfer==0.4.2 (from biomage-utils==0.0.1)
  Using cached s3transfer-0.4.2-py2.py3-none-any.whl (79 kB)
Collecting six==1.16.0 (from biomage-utils==0.0.1)
  Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting tabulate==0.9.0 (from biomage-utils==0.0.1)
  Using cached tabulate-0.9.0-py3-none-any.whl (35 kB)
Collecting urllib3==1.26.7 (from biomage-utils==0.0.1)
  Using cached urllib3-1.26.7-py2.py3-none-any.whl (138 kB)
Collecting wcwidth==0.2.5 (from biomage-utils==0.0.1)
  Using cached wcwidth-0.2.5-py2.py3-none-any.whl (30 kB)
Collecting wrapt==1.13.3 (from biomage-utils==0.0.1)
  Using cached wrapt-1.13.3.tar.gz (48 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [85 lines of output]
      Traceback (most recent call last):
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/config/expand.py", line 81, in __getattr__
          return next(
                 ^^^^^
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/config/expand.py", line 82, in <genexpr>
          ast.literal_eval(value)
        File<EMAIL_ADDRESS>line 110, in literal_eval
          return _convert(node_or_string)
                 ^^^^^^^^^^^^^^^^^^^^^^^^
        File<EMAIL_ADDRESS>line 109, in _convert
          return _convert_signed_num(node)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^
        File<EMAIL_ADDRESS>line 83, in _convert_signed_num
          return _convert_num(node)
                 ^^^^^^^^^^^^^^^^^^
        File<EMAIL_ADDRESS>line 74, in _convert_num
          _raise_malformed_node(node)
        File<EMAIL_ADDRESS>line 71, in _raise_malformed_node
          raise ValueError(msg + f': {node!r}')
      ValueError: malformed node or string on line 2: <ast.Call object at 0x1010de620>

      The above exception was the direct cause of the following exception:

      Traceback (most recent call last):
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/config/expand.py", line 193, in read_attr
          return getattr(StaticModule(module_name, spec), attr_name)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/config/expand.py", line 87, in __getattr__
          raise AttributeError(f"{self.name} has no attribute {attr}") from e
      AttributeError: wrapt has no attribute __version__

      During handling of the above exception, another exception occurred:

      Traceback (most recent call last):
        File "/Users/rmarable/src/scicomp/biomage/biomage-utils/venv/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/Users/rmarable/src/scicomp/biomage/biomage-utils/venv/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/Users/rmarable/src/scicomp/biomage/biomage-utils/venv/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 149, in prepare_metadata_for_build_wheel
          return hook(metadata_directory, config_settings)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 396, in prepare_metadata_for_build_wheel
          self.run_setup()
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 507, in run_setup
          super(_BuildMetaLegacyBackend, self).run_setup(setup_script=setup_script)
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 341, in run_setup
          exec(code, locals())
        File "<string>", line 41, in <module>
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/__init__.py", line 103, in setup
          return distutils.core.setup(**attrs)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/_distutils/core.py", line 159, in setup
          dist.parse_config_files()
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/dist.py", line 649, in parse_config_files
          setupcfg.parse_configuration(
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/config/setupcfg.py", line 189, in parse_configuration
          meta.parse()
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/config/setupcfg.py", line 500, in parse
          section_parser_method(section_options)
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/config/setupcfg.py", line 475, in parse_section
          self[name] = value
          ~~~~^^^^^^
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/config/setupcfg.py", line 293, in __setitem__
          parsed = self.parsers.get(option_name, lambda x: x)(value)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/config/setupcfg.py", line 606, in _parse_version
          return expand.version(self._parse_attr(value, self.package_dir, self.root_dir))
                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/config/setupcfg.py", line 417, in _parse_attr
          return expand.read_attr(attr_desc, package_dir, root_dir)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/config/expand.py", line 196, in read_attr
          module = _load_spec(spec, module_name)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-build-env-ynuh3zzh/overlay/lib/python3.11/site-packages/setuptools/config/expand.py", line 216, in _load_spec
          spec.loader.exec_module(module)  # type: ignore
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "<frozen importlib._bootstrap_external>", line 940, in exec_module
        File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-install-rxli4ixa/wrapt_1e7c9461e64f4d57816b0b1eb20a71d9/src/wrapt/__init__.py", line 10, in <module>
          from .decorators import (adapter_factory, AdapterFactory, decorator,
        File "/private/var/folders/qg/kdkb1cv92k9dyx577psp88bw0000gn/T/pip-install-rxli4ixa/wrapt_1e7c9461e64f4d57816b0b1eb20a71d9/src/wrapt/decorators.py", line 34, in <module>
          from inspect import ismethod, isclass, formatargspec
      ImportError: cannot import name 'formatargspec' from 'inspect'<EMAIL_ADDRESS>      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
make: *** [install] Error 1

The issue might be the python version. If I remember correctly, python 3.9.xx should work. I do not have access to an Apple Silicon mac to test though.

The issue is the wrapt package. The version we have locked can't be installed in python 3.11. Using a venv with 3.9 should solve it.

Hi German,
Using a venv with 3.9 worked as expected.
❯ python3 --version
Python 3.11.6

❯ biomage --help
Usage: biomage [OPTIONS] COMMAND [ARGS]...

  🧬 Your one-stop shop for managing Biomage infrastructure.

Options:
  --help  Show this message and exit.

Commands:
  account         Manage Cellenics account information.
  configure-repo  Configures a repository to conform to standards.
  experiment      Manage Cellenics experiment data and settings.
  rds             Manage Cellenics RDS databases.
  rotate-ci       Rotates and updates repository access credentials.
  stage           Deploys a custom staging environment.
  unstage         Removes a custom staging environment.


add deprecation notice for AzMon connector in ConfigMgr 2010

Per ConfigMgr engineering team user story https://msazure.visualstudio.com/Configmgr/_workitems/edit/8269855, the Azure Monitor connector is deprecated as of version 2010. As of right now, we plan to remove it entirely in the 2107 release (July 2021). ConfigMgr support lifecycle is 18 months, so we'll need to keep the article until the last supported version (2103) is out of support (~October 2022).

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

D'oh! I probably should have put this in private repo. @bwren let me know if this is ok, or if I need to move this commit. Sorry...

Proof that it happens to the best of them. :)

Happy new year! 😄 Following up on this @bwren
Do you need me to move it over to private repo?

Happy new year! 😄 Following up on this @bwren
Do you need me to move it over to private repo?

@bwren Thanks for the review.
@aczechowski I don't find the new linked file in the azure-docs-pr repo, but I find it here: https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/changes/deprecated/removed-and-deprecated-cmfeatures. I've updated the (relative) link to go to this article. OK?

@bwren Thanks for the review.
@aczechowski I don't find the new linked file in the azure-docs-pr repo, but I find it here: https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/changes/deprecated/removed-and-deprecated-cmfeatures. I've updated the (relative) link to go to this article. OK?

@ktoliver, yes THANK YOU! I copied the markdown from memdocs without thinking. Thanks for catching it, that's the correct target. 😄

@ktoliver, yes THANK YOU! I copied the markdown from memdocs without thinking. Thanks for catching it, that's the correct target. 😄


What are the differences between 3 types of IoB tagging levels?

There are 3 levels of IoB tagging: box_level, document_level and box_and_within_box_level. But I couldn`t see what is the most appropriate for my dataset.
I have the entities in contiguous rows in the .tsv with the form B-tag , I-tag, I-tag ...
thanks

@jorgerodriguezsj : Did you find anything? I have the same question.

@jorgerodriguezsj : Did you find anything? I have the same question.

@ninjakx Sorry for taking time to answer, I suppose you have already discovered the meaning of each one. The only one that is clear to me is the document_level that what it does is that the IOB tagging is performed on the entire document. The other two do it within the same box if there is only one category and the other if there is more than one category within the box. But of these last two I am not sure which one does what.

@ninjakx Sorry for taking time to answer, I suppose you have already discovered the meaning of each one. The only one that is clear to me is the document_level that what it does is that the IOB tagging is performed on the entire document. The other two do it within the same box if there is only one category and the other if there is more than one category within the box. But of these last two I am not sure which one does what.


Avian On the Mod Page isnt Bold

UNPLAYABLEEEEE!!!!!!!!!

Thanks for spotting this, will fix later today.