Should we upgrade the Knative version for KFServing?

/kind feature
related https://github.com/kubeflow/kfserving/issues/1015
Describe the solution you'd like
Starting from KFServing 0.4 release, the logger API uses CloudEvents V1 which available on Knative Eventing 0.14.2+. Should we also consider updating the Knative serving version to something more recent?
Anything else you would like to add:
 I think Knative 0.16 is not working with KFServing, so we need to figure out a version that won't break our current implementation.

/cc @animeshsingh

@Tomcli Why Knative 0.16 is not working with KFS ?

Thanks @yuzisun, For Knative 0.16 I'm deploying with
Istio 1.6.8
Knative 0.16
KFServing 0.4
Kubernetes 0.16.14
Here are the events for one of the inferenceservice
  Warning  UpdateFailed   63s                kfserving-controller  Failed to update status for InferenceService "flowers-sample": Operation cannot be fulfilled on inferenceservices.serving.kubeflow.org "flowers-sample": the object has been modified; please apply your changes to the latest version and try again
  Warning  InternalError  63s                kfserving-controller  Operation cannot be fulfilled on inferenceservices.serving.kubeflow.org "flowers-sample": the object has been modified; please apply your changes to the latest version and try again
  Normal   Updated        16s (x3 over 63s)  kfserving-controller  Updated InferenceService "flowers-sample"

Thanks @yuzisun, so Knative 0.16 is working when we install istio with istioctl with operator. But we have to pay attention when we leverage the istio 1.1.6 and istio 1.3.1 with Dex when upgrading it for kubeflow.

I am new to KFserving so please excuse my most likely ignorant questions.
Following quote is from the KF serving docs themselves:
If you are looking to use PodSpec fields such as nodeSelector, affinity or tolerations which are now supported in the KFServing v1beta1 API spec, this requires Knative v0.17.0+, and you need to turn on the corresponding feature flags in your Knative configuration.
Q: Does serving without nodeSelectors force me to run my prediction service with KFserving on the same nodepool that KFServing and Kubeflow was installed on? And would that mean that for use cases with large memory intensive models and high throughput I would have to run Kubeflow 24/7 on a mega expensive nodepool strong enough for the occasional prediction jobs? I really liked the idea of scaling to zero.
I followed the KF/GKE installation guide which installs Knative v0.14.3 and KFServing v1alpha2.
Q: Is it possible to upgrade to v1beta1 and if so is it a matter of editing a few upstream manifests or Kustomization.yaml files and redeploying or is it more akin to open heart surgery for us mere mortals and wouldn't it also require upgrading Knative to v017? Any hints are appreciated!
Q: How about upgrading Knative to v0.17? It seems rather daunting. Just checking how many upstream files are referencing Knative v0.14 yields 28 files
$ find ./upstream -type f -exec grep -H 'release' {} \;  | grep v0.14  | cut -f 1 -d ':' | sort | uniq | wc -l       28
Sorry for the many questions. I have 200 more about setting up Ingress Gateway for a KFserving service, for which the docs made my head spin at 5000RPM.


Version for 1.20.2

Hey,
Is there any chance of a 1.20.2 version?
1.20.1 actually works but it messes up the version detection of the game somehow.
Unfortunately we can't upgrade to .4 just yet

Published a 1.20.2 version on Modrinth: https://modrinth.com/mod/fabricexporter/version/J6hcIgVH


[ui/ng] popover

This is v1 of the popover implementation which will prevent the clipping of elements that popover (tooltips, dropdowns, etc). Note that this solution uses javascript (TypeScript) to absolutely position the element using translate properties. This means that our css-only (non-angular) versions of those components will continue to be clipped off. Therefore, please note that this PR does not fix the clipping of the validation tooltip, which is not yet an angular component.
This PR introduces a new angular-component (tooltip) which behaves exactly as the existing static tooltip but will not clip the element when contained inside a scrolling container.
In a later iteration of this, we might want to consider adding smart functionalities, such as repositioning the popover if the position specified is outside of the browser's viewport.
fixes ##37.
Signed-off-by: Jeeyun Lim<EMAIL_ADDRESS>

@jeeyun So are there any updates related to the validation tooltip being clipped when a form is used in a modal? Any proposed workarounds if that is still a work in progress? I'm facing the issue now and I'm not sure how to best handle it. Thanks for any help you can provide.


✨ Better handling consecutive periods and reserved special symbols

Better handling Consecutive periods and these symbols - [。．.！!?？]
Update regression tests with respect to it.

🐛 Fix consecutive period bug reference in https://github.com/allenai/scholar-reader/issues/114

Codecov Report

Merging #78 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #78   +/-   ##
=======================================
  Coverage   98.42%   98.42%
=======================================
  Files          37       37
  Lines        1077     1077
=======================================
  Hits         1060     1060
  Misses         17       17

Flag
Coverage Δ

#unittests
98.42% <100.00%> (ø)

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

Impacted Files
Coverage Δ

pysbd/lang/common/common.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #78 into master will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #78      +/-   ##
==========================================
- Coverage   98.42%   98.41%   -0.01%
==========================================
  Files          37       37
  Lines        1077     1075       -2
==========================================
- Hits         1060     1058       -2
  Misses         17       17

Flag
Coverage Δ

#unittests
98.41% <100.00%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

pysbd/lang/common/common.py
100.00% <100.00%> (ø)

pysbd/languages.py
96.77% <0.00%> (-0.11%)
:arrow_down:

pysbd/exclamation_words.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


MySQL SSL connection error: unsupported protocol

Hi!
I wanted to upgrade from version 4.1.1-8 to 4.2.2.
During the upgrade I got this error message:
Migrating database. Please be patient, this could take a while...
SSL connection error: error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol
Couldn't create 'einfra_redmine' database. Please check your configuration.
rake aborted!
Mysql2::Error::ConnectionError: SSL connection error: error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/mysql2-0.5.3/lib/mysql2/client.rb:90:in `connect'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/mysql2-0.5.3/lib/mysql2/client.rb:90:in `initialize'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/mysql2_adapter.rb:22:in `new'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/mysql2_adapter.rb:22:in `mysql2_connection'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:830:in `new_connection'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:874:in `checkout_new_connection'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:853:in `try_to_checkout_new_connection'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:814:in `acquire_connection'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:538:in `checkout'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:382:in `connection'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/connection_pool.rb:1033:in `retrieve_connection'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_handling.rb:118:in `retrieve_connection'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_handling.rb:90:in `connection'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/tasks/mysql_database_tasks.rb:6:in `connection'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/tasks/mysql_database_tasks.rb:14:in `create'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/tasks/database_tasks.rb:119:in `create'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/tasks/database_tasks.rb:139:in `block in create_current'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/tasks/database_tasks.rb:316:in `block in each_current_configuration'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/tasks/database_tasks.rb:313:in `each'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/tasks/database_tasks.rb:313:in `each_current_configuration'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/tasks/database_tasks.rb:138:in `create_current'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/railties/databases.rake:29:in `block (2 levels) in <top (required)>'
/home/redmine/data/tmp/bundle/ruby/2.6.0/gems/rake-13.0.3/exe/rake:27:in `<top (required)>'
Tasks: TOP => db:create
(See full trace by running task with --trace)

The database is a MariaDB Galera cluster, with TLS support altough it's not enforced.
All database related settings are in place:
DB_ADAPTER: "mysql2"
DB_ENCODING: "utf8"
DB_HOST: "REMOTE HOST"
DB_NAME: "redmine"
DB_USER: "redmine"
DB_PASS: "SECRET"

Is there a way to explicitly disable the MySQL adapter's SSL connection?

Is it possible to enable TLSv1.2 in MariaDB?
ssl_cipher = TLSv1.2
It seems like the problem stems from debian and thus ubuntu increasing the minimal TLS version for SSL.
The docker could be updated to go back to supporting TLSv1 but there is apparently some big security issues with that.
https://github.com/microsoft/msphpsql/issues/1023#issuecomment-642340422
/etc/ssl/openssl.cnf section [system_default_sect] to
[system_default_sect]
MinProtocol = TLSv1.0
CipherString = DEFAULT@SECLEVEL=1

Its also made worse by MySQL client v5.7, changed its default to prefer using SSL.  And we are using v5.7.
root@fe4934890271:/home/redmine/redmine# mysql -V
mysql  Ver 14.14 Distrib 5.7.35, for Linux (x86_64) using  EditLine wrapper

This post implies it might be possible to explicitly disable ssl for MySQL. https://stackoverflow.com/a/60554755/780194
So options in order of best case:

Update server to support TLSv1.2
Drop min TLS to V1.0
Set ssl_mode to disabled

What would you like to try?

I think I would go the Set ssl_mode to disabled option for now.
How can I permanently add the ssl_mode: disabled option to database.yml, so that would be persistent across the versions?

Would you be willing to add DB_SSL_MODE as an option to the docker image and create a pull request?
This could be done by searching for anywhere DB_NAME is used and seeing if its appropriate to add DB_SSL_MODE

Alternatively a plugins/post-install.sh script could be created which changes the database.yml config file on each run, though would require a little bit of sed magic.

Would you be willing to add DB_SSL_MODE as an option to the docker image and create a pull request?
This could be done by searching for anywhere DB_NAME is used and seeing if its appropriate to add DB_SSL_MODE

That was my first idea. I'll take look at this.

Sounds good, the default should be preferred as I believe that's what its set to if its not supplied.
The options are as follows. sslmode: (disable|allow|prefer|require) though I have not been able to find an official documentation for rails which specifies this...

I was able create a working version based on what you have linked: https://stackoverflow.com/a/60554755/780194
The correct syntax were: ssl_mode: (disabled|allow|prefer|require)
Can you take a look at my commit? https://github.com/northway/docker-redmine/commit/fc8f05c766ac17b95eb0f4f02bb9a1cb43d95e13
If it's okay, I'll create a pull request.

Testing mysql and mariadb failed:
docker-compose -f docker-compose-mysql.yml up
...
redmine_1  | Migrating database. Please be patient, this could take a while...
redmine_1  | Unknown MySQL ssl_mode flag: prefer
redmine_1  | no implicit conversion from nil to integer
redmine_1  | Couldn't create 'redmine_production' database. Please check your configuration.
redmine_1  | rake aborted!
redmine_1  | TypeError: no implicit conversion from nil to integer

Testing postgres and sqlite3 started up fine though
$ docker-compose -f docker-compose-sqlite3.yml up
$ docker-compose -f docker-compose.yml up

Looks like mysql wants preferred instead of prefer...
I tried preferred with postgres and it didn't fail.  But I also tried setting a bad value and it didn't fail either so I'm not sure postgres pays any attention to the ssl-mode...

Looks like mysql wants preferred instead of prefer...

So should I change the default value to preferred?

I've changed to the default value to preferred, it looks good to me.
https://github.com/northway/docker-redmine/commit/37a1dd1414d7b2e01013c8efc983d53a96f5d7db

When can we except a new release, which contains this PR?

@northway you can always expect it to land with the next regular redmine version as our release system is at present broken. we are manualy releasing and we got only one member with release access.

I see, thanks for the update.

Hi was this patch rolled into 4.1.5?
I'm getting the very same issue.

was this pr rolled into 4.1.5?
It does not look like it.  It was included in 4.2.2-1

I just cherry-picked the changes to 4.1.5-1

Was there anything else I needed to do oother than the new ssl mode setting?
I couldn't get 4.2.2 to work either.

Did you try 4.2.2-1?

Did you try 4.2.2-1?

No, just 4.2.2


Update Storage Libraries to Use New AutoRest Features

Description
Updates the Azure Storage libraries to use the new AutoRest generation features generic-response-type and custom-strongly-typed-header-deserialization.
generic-response-type removes the use of named ResponseBase sub-types in favor of ResponseBase itself with the generic headers and body set. This helps reduce the need for reflection when handling network responses and also allows for implementation classes to be deleted reducing the footprint of the SDKs.
custom-strongly-typed-header-deserialization removes the use of Jackson Databind to convert the network response's HttpHeaders to the strongly-typed headers class. This greatly improves performance as it removes the need to convert the HttpHeaders to a JSON representation to deserialize them to the strongly-typed header and removes the need to use reflection when creating the strongly-type header.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check for com.azure:azure-storage-queue
API changes are not detected in this pull request for com.azure:azure-storage-queue

API change check for com.azure:azure-storage-file-share
API changes are not detected in this pull request for com.azure:azure-storage-file-share

/azp run java - stroage - tests

/azp run java - storage - tests

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-storage-blob

/azp run java - storage - tests

Let's run perf tests for this PR before merging (although the changes are not likely going to impact perf).

Let's run perf tests for this PR before merging (although the changes are not likely going to impact perf).

Perf test data has been added


[cli] Change zstd from fastest to default

Public-Facing Changes

[cli] Improved compression ratio when creating zstd-compressed mcap files

Description
In the future we should expose this as a CLI flag as well, but the zstd default compression level is a better default choice for an offline tool than "SpeedFastest".
Fixes #645

@jhurliman the CLI tool is an offline tool but the writer library is not necessarily. I think for that reason we are going to want to bundle this with a change that makes this a config option that can be passed into the writer so that nobody is forced to take a performance hit. At that point we may as well also pass it in as a flag in the CLI (potentially even retaining the old default in the writer).

As it currently stands, our real-time rosbag2 recorder that we publish benchmarks on produces smaller files than the mcap cli tool.

The bag2mcap.ts example now uses zstd compression and produces smaller files than our CLI tool as well.

This change seems good to me. @wkalt can you explain the reasoning why we would not want to use default in the CLI tool which is an offline tool?


[toranj] adding test-case for multi-hop traffic exchange

This commit adds a new toranj test script to test IPv6 traffic
exchange over multiple hops in a network with chain topology:
(r1 <--> r2 <--> r3 <--> r4)

Verifies Address Query process over multi-hop.
Verifies Mesh Header frame forwarding over multiple routers.
Verifies forwarding of large IPv6 messages (1000 bytes) requiring
lowpan fragmentation.

This is great.  What about also validating multihop traffic between FTD and MTD children across the same topology?

In the current test, every router has a SED child attached to it (need it to make sure routers are promoted quickly)
So this is the topology:
r1 --- r2 --- r3 --- r4
|      |      |      |
c1     c2     c3     c4

The first part of the test we send from first router (r1) in the chain to the last router in the chain (rN).
The second part we send from the child of last router (cN) to the child of first router (c1)

If you have ideas for more test let me know. It's easy to add it to the test.

Speaking here about how to interpret Thread specification: assuming that link quality is good between all devices (each link cost = 1), what should be routing cost of r1 -> r4 route and what should be the cost of c4-c1 route?
Does it count only router-router cost? I.e. both costs should be calculated as 3?

@Nopik, when routing a packet, the link cost between a given child and its parent are not factored in to the path/route cost.  To answer your question more directly, the answer is 3 for both.
The one minor exception is Router-Eligible End Devices (REEDs), which do compute their route cost to the leader and communicate that devices that are looking for a parent to attach to.

@abtink, I think it may be useful to have a test that includes communication with Full End Devices (FEDs).  This will test the FED's ability to respond directly to Address Query in addition to sending/receiving IPv6 messages even while it does not participate as a Router.

@jwhui , sounds great... Added it in the new pushed commit.


change: [UIE-8261] - Update doc links on db landing page empty state

Description 📝
Update doc links on Database landing page empty state
Changes  🔄

Updated doc links

Target release date 🗓
12/2024
How to test 🧪
Prerequisites

The showEmpty case needs to be true, which can be manually set in a local env, but which will also be true if there are no new or legacy databases

Reproduction steps

The documentation links are on the page that is presented when there are no databases present - i.e. if you see a table of databases, you won't see these links

Verification steps

Visit the links to see if they go to the new locations

As an Author, I have considered 🤔

👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿  Providing accessibility support

[ x] I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

[ x] All unit tests are passing
[ x] TypeScript compilation succeeded without errors
[ x] Code passes all linting rules

@rodonnel-akamai This PR is good to merge once change-set is added.

@rodonnel-akamai This PR is good to merge once change-set is added.
Forgot that step, just now got around to it and updated the PR.


FuncUnit able to use Jasmine (and JSTestDriver)

FuncUnit should be able to use Jasmine or other testing solutions.  And JSTestDriver should work as a steal.browser.
References:

https://github.com/jupiterjs/funcunit/issues/12
http://forum.javascriptmvc.com/#Topic/32525000000224009/32525000000667494

DoneJS repository migration.


go vet: vet should warn when time.Time type (or types embed it) is used as map keys.

What version of Go are you using (go version)?
go version go1.9.2 linux/amd64
Does this issue reproduce with the latest release?
yes
What did you do?
package main

import "time"

type T struct {
	time.Time
}

var a map[T]string

func main() {
}

$ go vet a.go
$ [nothing reported]

What did you expect to see?
$ go vet a.go
$ time.Time is not a good map key type.

Like time.Time, there may be some other types, which are not capable to be used as map key types.
What did you see instead?
nothing reported

I don't think this meets the bar for a vet check.
It's perfectly valid to use a time.Time as a map key, if you know what you're doing. I think it would be too noisy for valid code.
But somebody could do some analysis on GitHub to see what percentage of time.Time-keyed maps are valid.

I wrote a linter that detects this type of issue if you're interested: https://github.com/m3db/build-tools/blob/master/linters/badtime/README.md
I'm trying to get it integrated with gometalinter right now.

Now that vet is part of go test, the bar is even higher for new checks. Because it is valid sometimes to have a time.Time as a map key, rejecting it in vet is not OK.
You might talk to @dominikh about adding this to megacheck or one of the other linters.


Multiple calls to mx.sym.Variable with same name: Dangerous / unexpected behavior?

Description
Multiple calls to mx.sym.Variable with same name e.g. calling mx.sym.Variable('a') twice seems to result in unexpected and therefore possibly dangerous behavior in the forward and backward call.
Environment info (Required)
----------Python Info----------
Version      : 3.5.2
Compiler     : GCC 5.4.0 20160609
Build        : ('default', 'Nov 23 2017 16:37:01')
Arch         : ('64bit', 'ELF')
------------Pip Info-----------
Version      : 10.0.1
Directory    : /u/schamper/software/pyenvs/py3env_seye-1.18.1/lib/python3.5/site-packages/pip
----------MXNet Info-----------
Version      : 1.1.0
Directory    : /u/schamper/software/pyenvs/py3env_seye-1.18.1/lib/python3.5/site-packages/mxnet
Commit Hash   : 07a83a0325a3d782513a04f47d711710972cb144
----------System Info----------
Platform     : Linux-4.13.0-36-generic-x86_64-with-Ubuntu-16.04-xenial
system       : Linux
node         : valin
release      : 4.13.0-36-generic
version      : #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018
----------Hardware Info----------
machine      : x86_64
processor    : x86_64
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    1
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 58
Model name:            Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
Stepping:              9
CPU MHz:               3192.812
CPU max MHz:           3600.0000
CPU min MHz:           1600.0000
BogoMIPS:              6385.62
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              6144K
NUMA node0 CPU(s):     0-3
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti retpoline tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts
----------Network Test----------
Setting timeout: 10
Timing for PYPI: https://pypi.python.org/pypi/pip, DNS: 0.0093 sec, LOAD: 0.3110 sec.
Timing for MXNet: https://github.com/apache/incubator-mxnet, DNS: 0.0011 sec, LOAD: 0.8138 sec.
Timing for Gluon Tutorial(cn): https://zh.gluon.ai, DNS: 0.9853 sec, LOAD: 0.6936 sec.
Timing for FashionMNIST: https://apache-mxnet.s3-accelerate.dualstack.amazonaws.com/gluon/dataset/fashion-mnist/train-labels-idx1-ubyte.gz, DNS: 0.0264 sec, LOAD: 0.2201 sec.
Timing for Gluon Tutorial(en): http://gluon.mxnet.io, DNS: 0.1136 sec, LOAD: 0.0287 sec.
Minimum reproducible example
multiple_calls_to_sym_var.py.zip
Copied content of multiple_calls_to_sym_var.py
import mxnet as mx

var_f = mx.sym.Variable('a') * mx.sym.Variable('a')
gA = mx.nd.zeros(1)
ex_f = var_f.bind(ctx=mx.cpu(), args={'a':mx.nd.array([3])}, args_grad={"a": gA})
print(ex_f.forward())
# results in 9 as expected

ex_f.backward(out_grads=mx.nd.array([1]))
print(gA)
# results in 3 but expected gradient would be 6 (the two calls to sym.Variable
# seem to have created two versions of 'a').
# Up to now the program did not crash, so the wrong(?) usage of
# mx.sym.Variable(...) is not obvious to the programmer

print(ex_f.grad_dict)
# Only after e.g. reading the grad_dict the program crashes and the wrong usage
# becomes obvious: ValueError: Duplicate names detected, ['a', 'a']

Steps to reproduce
python3 multiple_calls_to_sym_var.py
Remarks
Is this behavior intentional and useful in any scenario? Do I miss something obvious? Maybe there is a guideline, I am not aware of, that mx.sym.Variable should not be called twice with the same name and then be used in the same computational graph, for most applications. But if so, mxnet should maybe warn the user a bit more.
I am aware of that constructing the graph e.g. via
var_a = mx.sym.Variable('a')
var_f = var_a * var_a

works and shows the expected behavior and that
mx.sym.Variable('a') is mx.sym.Variable('a') results in False, but found it still valiuable to report the behavior of the other construction.

Resolving the issue, because, with 2 issues referenced, this is an expected behavior. Please reopen for any other issues.


console error

getting this error on demo 28, maybe got something to do with a timer ?

thank you, should be fixed with https://github.com/abap2UI5/abap2UI5/pull/708


What is the radius of LocationID? Can you target just a city?

When specifying the locationId how specific is instafeed.js? In this Eiffel tower example (https://github.com/stevenschobert/instafeed.js/issues/10) you got a locationId from some lat + long cords and put it in your search. How wide is the radius of search?
The reason I ask is because what I really want to do is search for images from a specific city. So for example, I want all images from New York City. Is there a clever way to be able to roughly capture the whole city? Keeping in mind that every city has a different size.
I know it must be possible because sites like http://worldc.am/ can do it so I want to be able to do the same thing.
Thanks, and I really enjoy instafeed.js!

Location is no longer available in the current API.


Training Time? (Thanks so much)

Thanks so much for the project.
Curious about how much time it took for you to train and did you use the same cloud resources as in the inference one?
Thanks!

Current settings train for few hours (~2?) on 4XA100 40GB that I use from Lambda Cloud <3. But I think they look very short on GPUs these days.

Thanks so much!


implement StackStore and QueueStore

Ordered versions of the Store resource.

Codecov Report

Merging #98 (b466a37) into master (c8595c6) will decrease coverage by 9.48%.
The diff coverage is 21.21%.

@@            Coverage Diff             @@
##           master      #98      +/-   ##
==========================================
- Coverage   98.17%   88.70%   -9.48%
==========================================
  Files          10       10
  Lines         274      301      +27
==========================================
- Hits          269      267       -2
- Misses          5       34      +29

Files Changed
Coverage Δ

src/resources/ordered_stores.jl
0.00% <0.00%> (ø)

src/resources/stores.jl
90.90% <100.00%> (-4.33%)
:arrow_down:

... and 2 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

good catch! Thank you! Fixed this and will merge a bit later today.


Missing arm v6 and v7 docker images for v0.8 release

Currently the docker builds of amr v6 and v7 are missing for latest, version and unstable tag.
https://hub.docker.com/r/infinityofspace/certbot_dns_duckdns/tags

Ok the problem has fixed itself and the images are ready. The Docker Hub index was just a bit slow.


How to use it directly with cs file?

For some reasons, my monodevelop/VS Code doesn't work.
Could someone tell me, if there is still a chance to use this library and how?
Thx in advance :)

Can I close this issue?


Adding prisma to nestjs project should note/flag/modify start:prod script

Bug description
To build a production version of a nestjs project (without prisma), you run
yarn build
Which creates a dist directory, with a main.js file that can be run by:
yarn start:prod
which just executes:
node dist/main
When adding prisma to a nestjs project, something in prisma modifies the build such that instead of ./dist/ having the main.js file, it now has another level of indirection (as well as the new prisma directory in ` so it looks like:
prisma/
src/
src/main.js
tsconfig.build.tsbuildinfo

Now when running the production build, the package.json start:prod script, the script reports:
Error: Cannot find module '/tmp/rest-nestjs/dist/main'
As it still references dist/main(.js) instead of the new dist/src/main(.js)
Unfortunately, I haven't had the time yet to dig into how we get here, so maybe the first question is, what changes the build?

installation of @prisma/client?
some hook into nests build?
prisma generate?
something else?

I presume the correct fix would be to modify the prod:start if it is dist/main, or if it has changed (or doesn't exist) throw an error?
Also maybe add a note/flag saying it was modified?
And as I was tracking this down, I was (briefly) trying to figure out in the docs where and what exactly was happening here. Did I miss the explanations to what is happening here? I can be obtuse sometimes. ;-)
Thanks!
How to reproduce
Follow instructions from here:
 curl https://codeload.github.com/prisma/prisma-examples/tar.gz/latest | tar -xz --strip=2 prisma-examples-latest/typescript/rest-nestjs
cd rest-nestjs
yarn install
...
yarn build
ls -l dist/
yarn start:prod
Error: Cannot find module '/tmp/rest-nestjs/dist/main'

cat package.json| grep prod
    "start:prod": "node dist/main",

Instead run:
node dist/src/main

And all works fine
Expected behavior
The app runs fine
Prisma information
Uses prisma-examples-latest/typescript/rest-nestjs
Environment & setup

OS: WSL (Windows 10)
Database: PostgreSQL (but N/A)
Node.js version:  v16.15.0

Prisma Version
prisma                  : 3.13.0
@prisma/client          : 3.13.0
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine efdf9b1183dddfd4258cd181a72125755215ab7b (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli efdf9b1183dddfd4258cd181a72125755215ab7b (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core efdf9b1183dddfd4258cd181a72125755215ab7b (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt efdf9b1183dddfd4258cd181a72125755215ab7b (at<EMAIL_ADDRESS>Default Engines Hash    : efdf9b1183dddfd4258cd181a72125755215ab7b
Studio                  : 0.459.0

This happens because tsconfig.json in that project doesn't specify rootDir explicitly, so its implicit value is the longest common path of all non-declaration input *.ts files.
The start:prod command was written with the assumption that no TypeScript files would be present outside src, but that assumption was broken by adding the prisma/seed.ts file: TypeScript now needs to emit it as dist/prisma/seed.js and whatever used to be just dist/**/*.js as dist/src/**/*.js.
Prisma itself doesn't change anything in the build process, and has no way to know that some build commands need to be modified; this is a configuration issue in this specific project (/cc @ruheni).
I'll close this issue since it's not a bug on the Prisma side, feel free to reopen if I'm wrong or if I missed anything.

Thanks for the ping @aqrln. I'll re-open the issue and transfer it to the Prisma Examples repo


Feature: revoke token

This adds token revocation (#24)

LGTM! Happy to have targeted sign out on board soon :)


MAINT: Rollback python2.6 workaround

Reference issue

This was original commited in https://github.com/scipy/scipy/pull/11636 then rolledback in https://github.com/scipy/scipy/pull/12088
What does this implement/fix?

Additional information

Rollback was required because I had changed PyNumber_Check to PyLong_Check as part of testing and PyLong_Check was sufficient to build (but I failed to run the tests again before force pushing)

All green now, merging. Thanks @sethtroisi


Add Modal Nav Drawer

Description
Build the UI of the Modal Nav Drawer as shown in the image below
Screenshots

Hi, can you assign me this ?

@abhishek-900 Sure go ahead

@Roshaen
Assign me also, want to try this...

@Perumallpardhiv assigned you

@Debajyoti14
Pls add points to my Clueless profile for this #44 pr
Clueless profile link : https://www.clueless.tech/profile/admin/96647299


feat: refactor internal_collect_tests

Closes #553
Introduced changes

Deletes internal_collect_tests and performs the operations inline in collect_tests_from_directory

Breaking changes

Checklist

[x] Linked relevant issue
[ ] Updated relevant documentation
[ ] Added relevant tests
[x] Performed self-review of the code
[ ] Added changes to CHANGELOG.md

Thanks for your contribution!
The failing test is a bug on our side regarding foreign contributions.


io.netty security issues

Discussed in https://github.com/Azure/azure-sdk-for-net/discussions/25216

Originally posted by daesma November  9, 2021
Hi,
We are seeing that dependencies like  io.netty:netty-handler 4.1.52.Final, and a bunch of other io.netty packages, are flagged for security issues. We also know that it's coming from azure dotnet package as dependencies, such as com.azure:azure-storage-file-share:jar:12.11.1.
We'd really like to understand the roadmap for taking care of these issues and the recommendation for my team to remain secure in the meantime.

Transferring to the Java repository, as the dependencies and packages detailed are Java-related.   The link for the discussion thread comes up as a 404 so it's difficult to confirm context, but I believe the OP likely misspoke when they called out the "azure dotnet package"

I'm the OP. If I said that, yes - I misspone. This is definitely a Java related issue.

@daesma There's a newer version of azure-storage-file-share(12.11.2) that uses 4.1.68.Final version of io.netty libraries. Can you please try upgrading to this newer version?

Closing as much newer versions of Netty are being used in the latest versions of the SDKs


Can't install Triton

I booted up the server and figured I would try giving the code a whirl. I appear to be unable to successfully run pip install -r requirements.txt, with it throwing errors when it got to Triton. The first problem was that I didn't have llvm-9-dev installed, but apt-get install llvm-9-dev took care of that. The second problem was that I had to run pip install CMake. Now both packages are installed and yet pip is throwing it's most complicated error yet. Below is the full output
    Running setup.py install for triton ... error
    ERROR: Command errored out with exit status 1:
     command: /root/anaconda3/envs/ds/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-gwvnpboi/triton_22306e539ed64a7a9b6510483f530faa/setup.py'"'"'; __file__='"'"'/tmp/pip-install-gwvnpboi/triton_22306e539ed64a7a9b6510483f530faa/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-ukz_au5s/install-record.txt --single-version-externally-managed --compile --install-headers /root/anaconda3/envs/ds/include/python3.7m/triton
         cwd: /tmp/pip-install-gwvnpboi/triton_22306e539ed64a7a9b6510483f530faa/
    Complete output (193 lines):
    /root/anaconda3/envs/ds/lib/python3.7/distutils/dist.py:274: UserWarning: Unknown distribution option: 'keyword'
      warnings.warn(msg)
    running install
    running build
    running build_py
    creating build
    creating build/lib.linux-x86_64-3.7
    creating build/lib.linux-x86_64-3.7/triton
    copying triton/__init__.py -> build/lib.linux-x86_64-3.7/triton
    copying triton/kernel.py -> build/lib.linux-x86_64-3.7/triton
    package init file 'triton/_C/__init__.py' not found (or not a regular file)
    creating build/lib.linux-x86_64-3.7/triton/ops
    copying triton/ops/__init__.py -> build/lib.linux-x86_64-3.7/triton/ops
    copying triton/ops/batchnorm.py -> build/lib.linux-x86_64-3.7/triton/ops
    copying triton/ops/einsum.py -> build/lib.linux-x86_64-3.7/triton/ops
    creating build/lib.linux-x86_64-3.7/triton/_C
    creating build/lib.linux-x86_64-3.7/triton/_C/include
    creating build/lib.linux-x86_64-3.7/triton/_C/include/triton
    creating build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen
    copying triton/_C/include/triton/codegen/pass.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen
    copying triton/_C/include/triton/codegen/target.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen
    creating build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/analysis
    copying triton/_C/include/triton/codegen/analysis/align.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/analysis
    copying triton/_C/include/triton/codegen/analysis/allocation.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/analysis
    copying triton/_C/include/triton/codegen/analysis/axes.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/analysis
    copying triton/_C/include/triton/codegen/analysis/layout.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/analysis
    copying triton/_C/include/triton/codegen/analysis/liveness.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/analysis
    creating build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/selection
    copying triton/_C/include/triton/codegen/selection/generator.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/selection
    copying triton/_C/include/triton/codegen/selection/machine_layout.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/selection
    copying triton/_C/include/triton/codegen/selection/machine_value.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/selection
    creating build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/transform
    copying triton/_C/include/triton/codegen/transform/coalesce.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/transform
    copying triton/_C/include/triton/codegen/transform/cts.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/transform
    copying triton/_C/include/triton/codegen/transform/dce.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/transform
    copying triton/_C/include/triton/codegen/transform/disassociate.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/transform
    copying triton/_C/include/triton/codegen/transform/membar.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/transform
    copying triton/_C/include/triton/codegen/transform/peephole.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/transform
    copying triton/_C/include/triton/codegen/transform/reassociate.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/codegen/transform
    creating build/lib.linux-x86_64-3.7/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/backend.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/buffer.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/context.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/device.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/dispatch.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/error.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/handle.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/kernel.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/module.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/platform.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/driver
    copying triton/_C/include/triton/driver/stream.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/driver
    creating build/lib.linux-x86_64-3.7/triton/_C/include/triton/external
    copying triton/_C/include/triton/external/half.hpp -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external
    creating build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_d3d10.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_d3d11.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_dx9_media_sharing.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_dx9_media_sharing_intel.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_egl.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_ext.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_ext_intel.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_gl.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_gl_ext.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_platform.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl_va_api_media_sharing_intel.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/opencl.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl.hpp -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CL
    copying triton/_C/include/triton/external/CL/cl2.hpp -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CL
    creating build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CUDA
    copying triton/_C/include/triton/external/CUDA/cuda.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CUDA
    copying triton/_C/include/triton/external/CUDA/nvml.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/external/CUDA
    creating build/lib.linux-x86_64-3.7/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/basic_block.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/builder.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/constant.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/context.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/context_impl.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/enums.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/function.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/instructions.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/metadata.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/module.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/print.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/type.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/utils.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/value.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/ir
    copying triton/_C/include/triton/ir/visitor.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/ir
    creating build/lib.linux-x86_64-3.7/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/ast.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/code_gen.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/cpp.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/encoding.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/error.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/evaluator.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/mem_pool.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/parser.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/scanner.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/scope.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/token.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/type.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/lang
    copying triton/_C/include/triton/lang/visitor.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/lang
    creating build/lib.linux-x86_64-3.7/triton/_C/include/triton/runtime
    copying triton/_C/include/triton/runtime/arg.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/runtime
    copying triton/_C/include/triton/runtime/function.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/runtime
    creating build/lib.linux-x86_64-3.7/triton/_C/include/triton/tools
    copying triton/_C/include/triton/tools/graph.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/tools
    copying triton/_C/include/triton/tools/thread_pool.h -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/tools
    copying triton/_C/include/triton/tools/bench.hpp -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/tools
    copying triton/_C/include/triton/tools/sha1.hpp -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/tools
    creating build/lib.linux-x86_64-3.7/triton/_C/include/triton/tools/sys
    copying triton/_C/include/triton/tools/sys/getenv.hpp -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/tools/sys
    copying triton/_C/include/triton/tools/sys/mkdir.hpp -> build/lib.linux-x86_64-3.7/triton/_C/include/triton/tools/sys
    running build_ext
    -- The C compiler identification is GNU 7.5.0
    -- The CXX compiler identification is GNU 7.5.0
    -- Detecting C compiler ABI info
    -- Detecting C compiler ABI info - done
    -- Check for working C compiler: /usr/bin/cc - skipped
    -- Detecting C compile features
    -- Detecting C compile features - done
    -- Detecting CXX compiler ABI info
    -- Detecting CXX compiler ABI info - done
    -- Check for working CXX compiler: /usr/bin/c++ - skipped
    -- Detecting CXX compile features
    -- Detecting CXX compile features - done
    -- Found LLVM: /usr/lib/llvm-9 (found version "9.0.0")
    -- Adding Python module
    -- Configuring done
    CMake Warning (dev) at CMakeLists.txt:45 (add_library):
      Policy CMP0038 is not set: Targets may not link directly to themselves.
      Run "cmake --help-policy CMP0038" for policy details.  Use the cmake_policy
      command to set the policy and suppress this warning.

      Target "triton" links to itself.
    This warning is for project developers.  Use -Wno-dev to suppress it.

    -- Generating done
    -- Build files have been written to: /tmp/pip-install-gwvnpboi/triton_22306e539ed64a7a9b6510483f530faa/build/temp.linux-x86_64-3.7
    Scanning dependencies of target triton
    [  1%] Building CXX object CMakeFiles/triton.dir/lib/codegen/analysis/allocation.cc.o
    [  3%] Building CXX object CMakeFiles/triton.dir/lib/codegen/analysis/align.cc.o
    [  5%] Building CXX object CMakeFiles/triton.dir/lib/codegen/analysis/axes.cc.o
    [  7%] Building CXX object CMakeFiles/triton.dir/lib/codegen/analysis/layout.cc.o
    [  9%] Building CXX object CMakeFiles/triton.dir/lib/codegen/analysis/liveness.cc.o
    [ 10%] Building CXX object CMakeFiles/triton.dir/lib/codegen/selection/generator.cc.o
    [ 12%] Building CXX object CMakeFiles/triton.dir/lib/codegen/selection/machine_layout.cc.o
    [ 14%] Building CXX object CMakeFiles/triton.dir/lib/codegen/selection/machine_value.cc.o
    [ 16%] Building CXX object CMakeFiles/triton.dir/lib/codegen/target.cc.o
    /tmp/pip-install-gwvnpboi/triton_22306e539ed64a7a9b6510483f530faa/src/lib/codegen/target.cc:5:10: fatal error: llvm/IR/IntrinsicsNVPTX.h: No such file or directory
     #include "llvm/IR/IntrinsicsNVPTX.h"
              ^~~~~~~~~~~~~~~~~~~~~~~~~~~
    compilation terminated.
    CMakeFiles/triton.dir/build.make:185: recipe for target 'CMakeFiles/triton.dir/lib/codegen/target.cc.o' failed
    make[2]: *** [CMakeFiles/triton.dir/lib/codegen/target.cc.o] Error 1
    make[2]: *** Waiting for unfinished jobs....
    CMakeFiles/Makefile2:122: recipe for target 'CMakeFiles/triton.dir/all' failed
    make[1]: *** [CMakeFiles/triton.dir/all] Error 2
    Makefile:113: recipe for target 'all' failed
    make: *** [all] Error 2
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-install-gwvnpboi/triton_22306e539ed64a7a9b6510483f530faa/setup.py", line 129, in <module>
        'Programming Language :: Python :: 3.6',
      File "/root/anaconda3/envs/ds/lib/python3.7/site-packages/setuptools/__init__.py", line 153, in setup
        return distutils.core.setup(**attrs)
      File "/root/anaconda3/envs/ds/lib/python3.7/distutils/core.py", line 148, in setup
        dist.run_commands()
      File "/root/anaconda3/envs/ds/lib/python3.7/distutils/dist.py", line 966, in run_commands
        self.run_command(cmd)
      File "/root/anaconda3/envs/ds/lib/python3.7/distutils/dist.py", line 985, in run_command
        cmd_obj.run()
      File "/root/anaconda3/envs/ds/lib/python3.7/site-packages/setuptools/command/install.py", line 61, in run
        return orig.install.run(self)
      File "/root/anaconda3/envs/ds/lib/python3.7/distutils/command/install.py", line 545, in run
        self.run_command('build')
      File "/root/anaconda3/envs/ds/lib/python3.7/distutils/cmd.py", line 313, in run_command
        self.distribution.run_command(command)
      File "/root/anaconda3/envs/ds/lib/python3.7/distutils/dist.py", line 985, in run_command
        cmd_obj.run()
      File "/root/anaconda3/envs/ds/lib/python3.7/distutils/command/build.py", line 135, in run
        self.run_command(cmd_name)
      File "/root/anaconda3/envs/ds/lib/python3.7/distutils/cmd.py", line 313, in run_command
        self.distribution.run_command(command)
      File "/root/anaconda3/envs/ds/lib/python3.7/distutils/dist.py", line 985, in run_command
        cmd_obj.run()
      File "/tmp/pip-install-gwvnpboi/triton_22306e539ed64a7a9b6510483f530faa/setup.py", line 55, in run
        self.build_extension(ext)
      File "/tmp/pip-install-gwvnpboi/triton_22306e539ed64a7a9b6510483f530faa/setup.py", line 95, in build_extension
        subprocess.check_call(['cmake', '--build', '.'] + build_args, cwd=self.build_temp)
      File "/root/anaconda3/envs/ds/lib/python3.7/subprocess.py", line 363, in check_call
        raise CalledProcessError(retcode, cmd)
    subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--config', 'Release', '--', '-j4']' returned non-zero exit status 2.
    ----------------------------------------
ERROR: Command errored out with exit status 1: /root/anaconda3/envs/ds/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-gwvnpboi/triton_22306e539ed64a7a9b6510483f530faa/setup.py'"'"'; __file__='"'"'/tmp/pip-install-gwvnpboi/triton_22306e539ed64a7a9b6510483f530faa/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-ukz_au5s/install-record.txt --single-version-externally-managed --compile --install-headers /root/anaconda3/envs/ds/include/python3.7m/triton Check the logs for full command output.```

After conversing with @sdtblck, I’ve come to understand that this isn’t a problem with the base code and is instead a problem with @lucidrains’s sparse attention code.
In order to run the sparse attention code we appear to need triton on the server.

After conversing with @sdtblck, I’ve come to understand that this isn’t a problem with the base code and is instead a problem with @lucidrains’s sparse attention code.
In order to run the sparse attention code we appear to need triton on the server.

Removing Triton from requirements.txt and letting deepspeed install it solved this issue.

Removing Triton from requirements.txt and letting deepspeed install it solved this issue.


How update rboot.bin over the air

Hi.
I have some devices with rboot version v1.3.0.
I build a new firmware with rboot version v1.4.1 (SDK 1.5.4) and I updated the rom0 and rom1 over the air.
But the devices with old rboot.bin version does not change SSID/Password for Station Mode with command "wifi_station_set_config".
Someone can help me?
The device with rboot.bin version v1.4.1 works very well.
I changed the code with this suggestion (without success):
http://bbs.espressif.com/viewtopic.php?f=7&t=1085

Comparing versions of rboot.bin 1.3.0 and 1.4.1 - no important difference.

I do not understand what is wrong. Why the devices with new roms do not change the router target?

I'm in Cambodia at the moment on holiday so can't help you much, but rBoot
does not affect what you can do with WiFi, or anything else, once the
application rom is booted.
On 2 Jul 2016 1:17 a.m., "Fernando Vilmar Palha"<EMAIL_ADDRESS>wrote:

Hi.
I have some devices with rboot version v1.4.0.
I build a new firmware with rboot version v1.4.1 and I updated the rom0
and rom1 over the air.
But the devices with old rboot.bin version does not change SSID/Password
for Station Mode with command "wifi_station_set_config".
Someone can help me?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/raburton/rboot/issues/17, or mute the thread
https://github.com/notifications/unsubscribe/AAadh-Ke86dVqFBbVKr6IpvzuPIw38vEks5qRVmogaJpZM4JDXpd
.

Thank you @raburton
A happy holiday to you.
I will identify the problem and I will find a solution.

Hi @raburton
I found the problem and the solution:
Important SDK Patch Released

SDK versions earlier than V<IP_ADDRESS> have the limitation of flash map.  It is not clear that which sector of flash is available in users’ systems. Therefore the older SDK versions need to be upgraded.  In addition, “esp_init_data_default.bin” has been modified in this release.

Sorry about the delay in getting back to you. Is everything working ok now? Is there anything I need to do to accommodate this SDK change?

Hi @raburton ,
I found other case: ESP SDK and RBoot Woes

Hi @raburton .
At moment I am using SDK 1.5.3 and rBoot 1.3.0  without problems.
Thank you.

Tested sdk 1.5.4 this morning and rboot-sampleproject is building, running and OTAing just fine. Pete also has it working now too, he found some odd changes with the SDK he needed to account for, but nothing that needed changing in rBoot: http://tech.scargill.net/esp8266-home-control-update/

Hi @raburton .
Now my code works with SDK <IP_ADDRESS> and rboot v1.4.1
But, the devices with previous roms does not works after remote update.
I am thinking of not maintaining legacy support.


Add Menu icon on the left titled 'Uni'

Add a menu icon on the left titled 'Uni', in full it will be Focallocal University of Positive Action
url will be http://uni.focallocal.org
this is for a University Course i will be setting up to teach people how to do what i do, to work on and create some awesome projects together, and have their name and photo up on our website as a graduate, and in the projects they led, or worked on.
it won't be a real degree (for now), but it will look damn impressive on a CV/Resume, being able to point to what they made happen, and help our project build/maintain an active pro-active team

@alfiepoleon i've assigned you as i know you were working on the Menu anyway. No worries if you'd rather not, just seemed that this should be linked to the tasks you were working on

Nice!
W dniu niedziela, 7 sierpnia 2016 AndyatFocallocal<EMAIL_ADDRESS>napisał(a):

@alfiepoleon https://github.com/alfiepoleon i've assigned you as i know
you were working on the Menu anyway. No worries if you'd rather not, just
seemed that this should be linked to the tasks you were working on
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/focallocal/fl-events/issues/50#issuecomment-238113201,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APm6nmVn7xEvbfd4aOyN8cK1IYP63cwIks5qdl8WgaJpZM4Jemsj
.

My suggestion would be a Graduation Cap, like this one: http://fontawesome.io/icon/graduation-cap/
Although we aren't using font-awesome as yet

@erostatyka nice that you're still following the project. we've got a great team together and working on it now and you'd be welcome to join in again if you like, just let me know and ill invite you to our Slack group :)


UI for over receiving

What is the motivation for adding/enhancing this feature?
When the user is receiving more than was ordered in a PO, or was expected in a Shipment, the progress bar should turn red/danger so that the user knows they are doing something unexpected.

assign it to me


Add support for Content-Language metadata header

Fixes #922

perhaps content-language should be filtered from the object metadata and added as a separate field in ObjectInfo so that it doesn't show under user defined metadata.


Instructions on "Using custom DM build in Label Studio" not working

Describe the bug
After modifying dm2, and following the steps in the read me of dm2 for "Using custom DM build in Label Studio". I expect to see the changes reflected in the dm UI of label studio.
To Reproduce
Steps to reproduce the behavior:
You can follow the official steps here
What I did is

I make a small change on md2
run npm ci && npm run build:module
copy the files inside build to [my/path/to/ls]/label_studio/static/dm,
Run label_studio start project but the changes do not show up

Expected behavior
I expect to see the changes reflected in the dm UI of label studio.
Screenshots
N/A
Environment (please complete the following information):

OS: Mac
Label Studio Version 0.9.1

Additional context
N/A

@NotAnyMike alright, I got it. seems we missed one of the steps on the instruction
after copying files from build dir execute this command in label studio folder:
npm ci && npx webpack

we'll add it to the instruction, sorry for that

Nice thank you! we are having progress, but now there is a different issue. If I run npc ci && npx webpack before launching LS. The DM only shows loading.... If I copy the whole build folder instead of build/static it loads normally. But then I cannot see any change in the DM UI.

@NotAnyMike sorry for the long reply, was super busy with 1.0.0 launch
do you see any errors in your browser console when this "loading..." thing happens?
copying whole build instead of build/static won't take any effect as that's not an expected structure

I am running this with the new version. After running npm ci && npm run build:module in dm2 I get the following outputs
npm WARN prepare removing existing node_modules/ before installation

><EMAIL_ADDRESS>install /Users/mikem/Documents/git/dm2/node_modules/webpack-dev-server/node_modules/fsevents
> node install.js

No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.

No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.

gyp: No Xcode or CLT version detected!
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)
gyp ERR! System Darwin 20.3.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/mikem/Documents/git/dm2/node_modules/webpack-dev-server/node_modules/fsevents
gyp ERR! node -v v14.16.0
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok

><EMAIL_ADDRESS>install /Users/mikem/Documents/git/dm2/node_modules/husky
> node husky install

husky > Setting up git hooks
husky > Done

><EMAIL_ADDRESS>postinstall /Users/mikem/Documents/git/dm2/node_modules/husky
> opencollective-postinstall || exit 0

Thank you for using husky!
If you rely on this package, please consider supporting our open collective:
> https://opencollective.com/husky/donate

><EMAIL_ADDRESS>postinstall /Users/mikem/Documents/git/dm2/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

added 1642 packages in 26.138s

><EMAIL_ADDRESS>build:module /Users/mikem/Documents/git/dm2
> BUILD_NO_HASH=true BUILD_NO_CHUNKS=true BUILD_MODULE=true npm run build

><EMAIL_ADDRESS>build /Users/mikem/Documents/git/dm2
> webpack

Failed to load ./.env.
assets by status 6.82 MiB [emitted]
  asset main.js 6.82 MiB [emitted] [big] (name: main) 1 related asset
  asset src_dev_js.chunk.js 2.53 KiB [emitted] 1 related asset
assets by status 59.3 KiB [compared for emit]
  asset main.css 56.9 KiB [compared for emit] (name: main) 1 related asset
  asset index.html 2.49 KiB [compared for emit]
Entrypoint main 6.87 MiB (6.69 MiB) = main.css 56.9 KiB main.js 6.82 MiB 2 auxiliary assets
orphan modules 331 KiB [orphan] 194 modules
runtime modules 7.53 KiB 13 modules
cacheable modules 5.98 MiB
  modules by path ./node_modules/ 5.13 MiB 89 modules
  modules by path ./src/ 879 KiB 158 modules
css modules 56.8 KiB
  modules by path ./src/components/Common/ 25.4 KiB 7 modules
  modules by path ./src/components/Filters/ 2.85 KiB 3 modules
  modules by path ./src/components/Table/ 1.65 KiB 3 modules
  modules by path ./src/components/DataManager/ 332 bytes 2 modules
  modules by path ./src/components/Label/ 1.6 KiB
    css ./node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[3].oneOf[1].use[1]!./node_modules/stylus-loader/dist/cjs.js??ruleSet[1].rules[3].oneOf[1].use[2]!./src/components/Label/Label.styl 1.13 KiB [code generated]
    css ./node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[3].oneOf[1].use[1]!./node_modules/stylus-loader/dist/cjs.js??ruleSet[1].rules[3].oneOf[1].use[2]!./src/components/Label/Toolbar/Toolbar.styl 480 bytes [code generated]
  css ./node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[3].oneOf[1].use[1]!./node_modules/stylus-loader/dist/cjs.js??ruleSet[1].rules[3].oneOf[1].use[2]!./src/components/App/App.styl 1.49 KiB [code generated]
  css ./node_modules/css-loader/dist/cjs.js!./node_modules/react-datepicker/dist/react-datepicker.css 23.5 KiB [code generated]
webpack 5.23.0 compiled successfully in 10678 ms

After copying the static folder to label_studio/static/dm, I run npm ci && npx webpack inside label_studio I get the follwoing error (I didn't have this error in the older version).
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /Users/mikem/Documents/git/label-studio/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/Users/mikem/Documents/git/label-studio/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR!      /Users/mikem/.npm/_logs/2021-03-18T11_48_08_349Z-debug.log

thank you, appreciate your feedback!
if you're running LS 1.0.0, there are massive changes to the overall structure and architecture of the app. the instruction in DM repo is only applicable to LS <1.0.0
to run custom DM build in LS >1.0.0, please follow these steps:

as previously, you should first build the DM itself by running npm ci &&  npm run build:module in the DM repo
next copy everything from [your-dm-dir]/build/static to [your-ls-dir]/label_studio/frontend/lib/dm
make sure not to remove version.json from frontend/lib/dm, it's significant to have it there
in the label_studio/frontend execute the following: npm ci  && npx run build to build your LS frontend JS and CSS bundles

we have plans to improve and simplify those scenarios, where our users want to run LS with custom builds of LSF/DM, but it is  a work in progress and not yet available. we're planning to make it happen in LS 1.0.1

I am doing this in new clones of dm2 and label-studio to have everything new and shiny. On dm2 with the new version, after calling npm ci && npm run build:module the build folder does not have thecss nor the js folders anymore. Is this expected behaviour?
Anyway moving all the files (there is no js or css folder now) from dm2/build/ into [ls/path]/label-studio/frontend/lib/dm has no effect.

This is the output of running  npm ci && npm run build:module in dm2
npm WARN prepare removing existing node_modules/ before installation

><EMAIL_ADDRESS>install /Users/mikem/Documents/git/dm3/node_modules/webpack-dev-server/node_modules/fsevents
> node install.js

  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node

><EMAIL_ADDRESS>install /Users/mikem/Documents/git/dm3/node_modules/husky
> node husky install

husky > Setting up git hooks
husky > Done

><EMAIL_ADDRESS>postinstall /Users/mikem/Documents/git/dm3/node_modules/husky
> opencollective-postinstall || exit 0

Thank you for using husky!
If you rely on this package, please consider supporting our open collective:
> https://opencollective.com/husky/donate

><EMAIL_ADDRESS>postinstall /Users/mikem/Documents/git/dm3/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

added 1642 packages in 30.473s

><EMAIL_ADDRESS>build:module /Users/mikem/Documents/git/dm3
> BUILD_NO_HASH=true BUILD_NO_CHUNKS=true BUILD_MODULE=true npm run build

><EMAIL_ADDRESS>build /Users/mikem/Documents/git/dm3
> webpack

Failed to load ./.env.
assets by path *.js 6.82 MiB
  asset main.js 6.82 MiB [compared for emit] [big] (name: main) 1 related asset
  asset src_dev_js.chunk.js 2.53 KiB [compared for emit] 1 related asset
asset main.css 56.9 KiB [compared for emit] (name: main) 1 related asset
asset index.html 2.49 KiB [compared for emit]
Entrypoint main 6.87 MiB (6.69 MiB) = main.css 56.9 KiB main.js 6.82 MiB 2 auxiliary assets
orphan modules 331 KiB [orphan] 194 modules
runtime modules 7.53 KiB 13 modules
cacheable modules 5.98 MiB
  modules by path ./node_modules/ 5.13 MiB 89 modules
  modules by path ./src/ 879 KiB 158 modules
css modules 56.8 KiB
  modules by path ./src/components/Common/ 25.4 KiB 7 modules
  modules by path ./src/components/Filters/ 2.85 KiB 3 modules
  modules by path ./src/components/Table/ 1.65 KiB 3 modules
  modules by path ./src/components/DataManager/ 332 bytes 2 modules
  modules by path ./src/components/Label/ 1.6 KiB
    css ./node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[3].oneOf[1].use[1]!./node_modules/stylus-loader/dist/cjs.js??ruleSet[1].rules[3].oneOf[1].use[2]!./src/components/Label/Label.styl 1.13 KiB [code generated]
    css ./node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[3].oneOf[1].use[1]!./node_modules/stylus-loader/dist/cjs.js??ruleSet[1].rules[3].oneOf[1].use[2]!./src/components/Label/Toolbar/Toolbar.styl 480 bytes [code generated]
  css ./node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[3].oneOf[1].use[1]!./node_modules/stylus-loader/dist/cjs.js??ruleSet[1].rules[3].oneOf[1].use[2]!./src/components/App/App.styl 1.49 KiB [code generated]
  css ./node_modules/css-loader/dist/cjs.js!./node_modules/react-datepicker/dist/react-datepicker.css 23.5 KiB [code generated]
webpack 5.23.0 compiled successfully in 10467 ms

This is the output of npm ci && npm run build after running it inside label-studio/frontend
npm WARN prepare removing existing node_modules/ before installation
added 573 packages in 10.567s

><EMAIL_ADDRESS>build /Users/mikem/Documents/git/label-studio3/label_studio/frontend
> webpack

[BABEL] Note: The code generator has deoptimised the styling of /Users/mikem/Documents/git/label-studio3/label_studio/frontend/lib/dm/js/main.js as it exceeds the max of 500KB.
asset index.js 4.96 MiB [compared for emit] (name: main) 1 related asset
asset main.css 118 KiB [compared for emit] (name: main) 1 related asset
Entrypoint main 5.08 MiB (3.84 MiB) = main.css 118 KiB index.js 4.96 MiB 2 auxiliary assets
orphan modules 426 KiB [orphan] 201 modules
runtime modules 1.13 KiB 5 modules
cacheable modules 4.51 MiB
  modules by path ./src/ 316 KiB 144 modules
  modules by path ./node_modules/ 3 MiB 62 modules
  modules by path ./lib/dm/ 1.21 MiB
    ./lib/dm/css/main.css 50 bytes [built] [code generated]
    ./lib/dm/js/main.js 1.21 MiB [built] [code generated]
css modules 118 KiB
  modules by path ./src/components/ 35.5 KiB 11 modules
  modules by path ./src/pages/ 24.4 KiB 8 modules

@NotAnyMike it not an expected behavior. I pushed a fix to Webpack settings so it should properly build DM now. there was an issue with NODE_ENV not being properly set

hey @NotAnyMike, please check out #685. this PR brings easier integration with custom DM builds

If you run the instructions on a new dm and ls without any notifications, you cannot see the table with the labelled examples once you launch ls.
In the browser console this shows
Uncaught (in promise) TypeError: _lib_dm_js_main__WEBPACK_IMPORTED_MODULE_1___default(...).DataManager is not a constructor
    at initializeDataManager (DataManager.js:45)
    at DataManager.js:66
    at DataManager.js:99
    at invokePassiveEffectCreate (react-dom.development.js:23487)
    at HTMLUnknownElement.callCallback (react-dom.development.js:3945)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:3994)
    at invokeGuardedCallback (react-dom.development.js:4056)
    at flushPassiveEffectsImpl (react-dom.development.js:23574)
    at unstable_runWithPriority (scheduler.development.js:646)
    at runWithPriority$1 (react-dom.development.js:11276)

@NotAnyMike nevermind, the PR is merged into master already.
those changes remove the DM from main LS bundle. it mean that you only have to build DM itself and copy the files to LS. building LS bundle is only required if you're making changes to the LS frontend

Now it is working! There is no longer a [your-ls-dir]/label_studio/frontend/lib/dm but a [your-ls-dir]/label_studio/frontend/dist/dm. But there is one more thing that I haven't manage to make it work, how can I add an extra button on top right next to the Settings button or change the text on Setting?

@NotAnyMike such changes are made inside label_studio/frontend/src/pages/DataManager/DataManager.js. you can find DataManager.context section there, it describes what buttons will be in the top-right corner
after changing any of the files in frontend/src you need to build the bundle. to do that navigate to label_studio/frontend directory and execute the following command: npm ci && npm run build or, if you need optimized production build, run npm ci && npm run build:production

There is something else that I haven't been able to figure it out. There are two ways of launching LS, using label-studio start ... or python label-studio/manage.py run_server. The first is reachable from outside the instance through the url but the static folder is not found (so the interface looks bad), and with the second method, the static folder is found but you cannot reach it from outside the instance, do you know how to solve this (i.e. make it accessible from outside and have the static folder)?


Evilginx2 doesn't setup a Allow-Control-Allow-Origin header if not already in response

I am writing a phishlet for blockchain.com, the problem is that the website uses CSP-Policy to prevent cross origin requests and evilginx2 strips the CSP-Policy but it never sets the Access-Control-Allow-Origin header at all if not already sent by the server in the respone. And since the request is already cross origin, the browser is preventing the request.
My question is how could i set a new header Access-Control-Allow-Origin? I tried using sub_filters but no chance. I also tried setting up the same fake subdomain for both of the cross domains but it only messed up everything. Below is the code from second attempt:
- {phish_sub: 'login', orig_sub: 'login', domain: 'blockchain.com', session: true, is_landing: true}
- {phish_sub: 'login', orig_sub: '', domain: 'blockchain.info', session: true, is_landing: false}

I made a quick fix by altering the line 475 in http_proxy.go file:
if (allow_origin == "" || allow_origin != "") {
    ....
}

hi @hash3liZer
i try your fix but when i open the phishing url i got a looping login page
can you share your phishlet please

That's strange that you are getting a looping page. It is supposed not be like this and for the phishlet, It's almost done, just a little work and then i am gonna upload it.

@HsounaZinoubi Here you go, i've uploaded them on github: https://github.com/hash3liZer/phishlets

@hash3liZer thanks but i thin i am too late please send it by email
<EMAIL_ADDRESS>

Please help with your blockchain phishlets been trying getting errors
<EMAIL_ADDRESS>


Preflight checks improvements around udev/vsock code

Initially, the goal was to fix some corner cases when adding the udev rule for the vsock device.
I added a bit too many cleanups before/after it, so the PR is bigger than I would have liked :)

/lgtm

/lgtm


[CLOSED] Only single instance multi-models handled

 Issue by richardpayne
Tuesday Mar 29, 2016 at 10:04 GMT
Originally opened as https://github.com/into-cps/INTO-CPS_Application/issues/11

The COE does not handle multiple instances of a FMU properly:
e.g. .instance1 and .instance2 does not work correctly

 Comment by CThuleHansen
Monday Apr 04, 2016 at 10:10 GMT

Do you have any examples of this, so I can reproduce it?

 Comment by richardpayne
Monday Apr 04, 2016 at 10:18 GMT

This was the issue raised by Carl, regarding the COE not handling multi-process instantiation. Carl added an example here:
https://dl.dropboxusercontent.com/u/14852535/2sensorTestWithSDPs.zip

 Comment by CThuleHansen
Monday Apr 04, 2016 at 11:26 GMT

Ah okay. Then I understand.
For future reference:
This issue concerns using the same FMU for multiple instances.
Normally this is not an issue, but in this case the FMU in question contains the following flag: canBeInstantiatedOnlyOncePerProcess="true". It is preferable, that the FMUs themselves offer the ability to create separate instances. I guess the reason for not doing this is, that the implementation uses global variables.
However, looking at comment below from the generated source files it looks like it will be possible to export FMUs from 20-sim later on, where multiple instances can be spawned.
/* only one static instance for now */
Otherwise it might be possible to load multiple instances by copying and renaming the dll.

 Comment by CThuleHansen
Monday Apr 04, 2016 at 11:31 GMT

This seems to have been fixed in 20-sim 4-days ago: https://github.com/controllab/fmi-export-20sim/commit/65b8dfed9b413ac16c99fea1a9a354500063360d

 Comment by CThuleHansen
Tuesday Apr 05, 2016 at 08:02 GMT

Unfortunately the commit has been reverted.
https://github.com/controllab/fmi-export-20sim/commit/65b8dfed9b413ac16c99fea1a9a354500063360d

 Comment by CThuleHansen
Tuesday Apr 05, 2016 at 08:08 GMT

Todo:
Check if canBeInstantiatedOnlyOncePerProcess="true" and if so, then return an error detailing, that it is not supported currently.


How to switch from "development" to "production"

I asked this question from AWS support with no helpful answer:
The current deployment stage is:
sdk-generation-stage-name: Development
How are you supposed to switch to "Production"?
What is the workflow?
Now that I am in production, I'd like to use a production stage.  And, make updates to a development stage so I can test.
Again, I asked this exact question to AWS support and they gave the answer:
"The stage name corresponds to the APIGatway stage".

I understand this.  I get it.  But, I don't yet understand the workflow from "development -> staging -> production" with MobileHub.  And since APIGateway is a lambda proxy, I'd like to see lambda functions from development/staging/production or whatever stage I set the stage-name to.
Is there a blog somewhere?

@jbarwick: Checkout https://stackoverflow.com/questions/50736739/how-to-handle-development-to-production-process-with-multiple-aws-services/50751535?noredirect=1#comment88528527_50751535
The solution is to create two Mobile Hub projects.

Hi @jbarwick did you ever figure this out? Even with two mobile hub projects how do you change the default path to be 'production' instead of 'development'?

@matthewsommer I think it makes the most sense to create two projects.  So, managing this in git will be what's necessary.

@jbarwick okay. But how do you even change it in the first place? If I try to change "sdk-generation-stage-name: Development" to "sdk-generation-stage-name: Production" it reverts back when it syncs.

@jbarwick: Would love to chat with you if you have time. If you can share your email I can set something up.

Having similar issue, is there a fix for this ?


Fixing oops, templatelets for e-mail and online status

Please review before merging.

The e-mail stuff straddles the line between 'bug fix' and 'unwanted additional exposure'

I wasn't sure where I should put the template bits, so I stuck them in index for now. Had difficulty parsing what you were doing.

https://github.com/elkarte/Elkarte/pull/2516/files#diff-67f3afd2549112d5f8194b79dda5a762L130
if the one viewing the message is allowed to send emails, but the poster doesn't allow others to see his email, then an empty li will be rendered.
Considering template_msg_email is returning the link, I'd use something like:
$email = template_msg_email($message['id'], $message['member']);

if ($context['can_send_email'] && !empty($email))
{
    $poster_div .= '<li>' . $email . '</li>';
}

It won't render an empty li, it will render a non-linked e-mail icon. May want to make a separate icon for that, but that's just graphical gloss.
Can do your method too, it just calls it out as being explicitly hidden.


GET /accounts Add test for 401, "Session invalid" if user is not an admin

Write test and implement 'Not an admin' in tests/routes/accounts/get-accounts-test.js as required by issue #83
I will work on this if it looks good for the team...

Awesome! We’ve invited you to the Hoodie Contributors Team, you should see an invitation here: https://github.com/hoodiehq. When you join you can assign your self to issues like this in future :)

closed by https://github.com/hoodiehq/hoodie-account-server/issues/137. That was great work, merci bien!


Support different data serialisations

We used to read and write one single serialisation for each data
type, but XML Schema actually defines multiple serialisations for
several types of data. For example, the boolean true can be
represented as both "1" and "true". For more info, see
https://www.w3.org/TR/xmlschema-2/#built-in-datatypes
This commit introduces a couple of fixes to deal with the various
serialisations:

The get*() functions on Things now understand the different
serialisations. For example, this means that getBoolean() no
longer returns null for the a boolean literal "false", but the
expected value false.

The remove*() functions on Things now remove all equivalent
serialisations of a given value. For example, this means that
passing false to removeBoolean() now removes both boolean
literals with the value "0" (as before) as well as those with
the value "false".

The serialisations we use by default have changed. Booleans are
now "true" or "false" rather than "1" or "0",
respectively, and we now use JavaScript's native serialisations
of Dates to ISO 8601 strings, rather than manually converting it
and truncating milliseconds from it.

[x] I've added a unit test to test for potential regressions of this bug.

[x] The changelog has been updated, if applicable.

[x] Commits in this PR are minimal and have descriptive commit messages.

This fix seems to resolve reading true/false values.
I am however getting 409 Conflict with editing a value, e.g. The patch could not be applied. Could not find to delete: <https://andydavison.inrupt.net/profile/card#me> <http://xmlns.com/foaf/0.1/testboolean2> "false"^^<http://www.w3.org/2001/XMLSchema#boolean> .
this is with a request payload
DELETE DATA {<https://andydavison.inrupt.net/profile/card#me> <http://xmlns.com/foaf/0.1/testboolean2> "false"^^<http://www.w3.org/2001/XMLSchema#boolean>.}; INSERT DATA {<https://andydavison.inrupt.net/profile/card#me> <http://xmlns.com/foaf/0.1/testboolean2> "true"^^<http://www.w3.org/2001/XMLSchema#boolean>.};

Thanks for testing @andydavison, I'll take a look at that.

OK, with help of @andydavison kindly sending me a recording reproducing the bug, @megoth verifying that the request we sent looks correct to him, and trying it out against a different server, I'm quite sure that the 409 Conflict is a bug in Node Solid Server: https://github.com/solid/node-solid-server/issues/1468
Thus, I'm marking this for ready for review again. I did add some additional tests that should verify that parsing/serialising works as expected (b0661c5e4600654928470e61e2c93e3f5588b362).

I also added 279e7026a43e387fee6a4f36b17454baadd494a7 that demonstrates the bug - it is currently disabled for NSS (where it fails). If it gets resolved there, or we want to test it against another server, we can simply use that test to verify it.


Sign our Windows installer

This has been requested by a number of users to simplify and ease Spyder installation in corporate environments.
This is an initial resource on how we could sign our installer:
https://learn.microsoft.com/en-us/windows/apps/develop/smart-app-control/code-signing-for-smart-app-control

@mrclary, could you take a look at this one? At first glance, the process seems similar to the one we use to sign our Mac app.

Yep, I'll take a look. I think we can just use our Apple certificate and I think that constructor has the mechanism for it.

Thanks @mrclary for your help with this!

In the short term, we can use the Apple certificate, just like Napari does. I don't know anything about Windows security, but I think we will ultimately need another certificate to do it properly.

In the short term, we can use the Apple certificate, just like Napari does

Good idea, just to get the ball rolling. But I also think we're going to need a Windows approved certificate.


RFC: @prismicio/next alpha feedback

Overview
@prismic/next is a new package designed for making Prismic easier to use with a NextJS project. The original RFC from @angeloashmore and provides more background:
https://github.com/prismicio/prismic-next/issues/1
At the moment, the package is mostly focused around making it easier to to set up Prismic Previews with Next. As Next and/or Prismic itself release more updates, it's possible that this package could grow and adapt to whatever new features come out if necessary.
For this RFC, we'd like to gather feedback on the implementation from a developer experience perspective. Should we be doing more, should we be doing less? Could things be done in an easier, simpler way for the end user?
enableClientServerSupport
export const enableClientServerSupport = (
	config: EnableClientServerSupportConfig,
): void => {
	if ("context" in config && config.context) {
		const previewData = config.context.previewData;

		if (isPrismicNextPreviewData(previewData) && previewData.ref) {
			config.client.queryContentFromRef(previewData.ref);
		}
	} else if ("req" in config && config.req) {
		config.client.enableAutoPreviewsFromReq(config.req);
	}
};

enableClientServerSupport is a function that allows the end user to enable Previews with either PreviewData coming from NextJS context or a Prismic ref coming from the NextApiRequest. It's intended to be used in an end users createClient() function, like this:

import { enableClientServerSupport, CreateClientConfig } from 'prismic-next';

export const createClient = (config: CreateClientConfig) => {
  const client = Prismic.createClient(apiEndpoint);

  enableClientServerSupport({
    client,
    context: config.context,
    req: config.req,
  });

  return client;
};

One thing we've been wondering is whether or not @prismic/next should offer its own createClient function that would run enableClientServerSupport under the hood. On one hand, it'd be nice to not have to worry about creating your own client, however, the fear is that we might deal with feature creep as users might have more needs with creating client outside of what we provide.
Would love to get feedback on whether or not we might want to provide one on our own or leave it as is.
<PrismicPreview />
The PrismicPreview component is to be wrapped around the entire NextJS app. There are two reasons why we have this component:

It's job is to add the PrismicToolbar to a NextJS app, there's a required param called repoName where you just pass it the name of your Prismic Repo and the correct URL for the toolbar is added in the necessary <script /> tag.

There is a useEffect hook that adds event listeners that come from the Prismic Toolbar, so it can properly update when the Preview URL is triggered. It's listening for both prismicPreviewUpdate and prismicPreviewEnd.

By default, the updatePreviewURL is /api/preview and the exitPreviewURL is /api/exit-preview. The end user has an option to override both of those by passing their own URLs to the props. Here's what it looks like in usage:
import { PrismicPreview } from 'prismic-next';

function MyApp({ Component, pageProps }: AppProps) {
  return (
    <PrismicPreview repoName='smashing-mag-nick-1'>
      <Component {...pageProps} />;
    </PrismicPreview>
  );
}

export default MyApp;

setPreviewData & redirectToPreviewURL
These are actually really straight forward, to be used when the prismicUpdatePreview event gets triggered from the toolbar. Usage:
import { linkResolver, createClient } from '../../prismic-config';
import * as prismicNext from 'prismic-next';
import { NextApiRequest, NextApiResponse } from 'next';

export default async (req: NextApiRequest, res: NextApiResponse) => {
  const client = createClient({ req });

  prismicNext.setPreviewData({ req, res });

  await prismicNext.redirectToPreviewURL({ res, client, linkResolver });
};

Here is how they look under the hood:
redirectToPreviewURL
import { NextApiResponse } from "next";
import { Client } from "@prismicio/client";
import { LinkResolverFunction } from "@prismicio/helpers";

export type PreviewConfig = {
	res: NextApiResponse;
	client: Client;
	linkResolver: LinkResolverFunction;
};

export async function redirectToPreviewURL({
	res,
	client,
	linkResolver,
}: PreviewConfig): Promise<void> {
	const previewUrl = await client.resolvePreviewURL({
		linkResolver,
		defaultURL: "/",
	});

	res.redirect(previewUrl);
}

setPreviewData
import { NextApiResponse, NextApiRequest } from "next";

export type PreviewConfig = {
	req: NextApiRequest;
	res: NextApiResponse;
};

export async function setPreviewData({
	req,
	res,
}: PreviewConfig): Promise<void> {
	const { token: ref } = req.query;

	res.setPreviewData({ ref });
}

exitPreview
This one is also pretty straight forward. Usage:
import { NextApiResponse } from 'next';
import { exitPreview } from 'prismic-next';

export default async function exit(_: any, res: NextApiResponse) {
  exitPreview(_, res);
}

Under the hood:
export async function exitPreview(_: any, res: NextApiResponse): Promise<void> {
	// Exit the current user from "Preview Mode". This function accepts no args.
	res.clearPreviewData();

	// Redirect the user back to the index page.
	res.writeHead(307, { Location: "/" });
	res.end();
}

Note
There is still some feedback left on these implementations that have yet to be applied, the intent of this RFC is to really focus on the end user usage, not collect feedback on the Pull Request itself. If you do want to give feedback about code quality, feel free to leave that feedback on the PR:
#3

Hey Guys,
Have you discussed dynamic route generation? It's something that's tricky at the minute for Next users. We try to offer some help with it by having users add a queries file that gets all documents in Prismic to build the dynamic paths.
https://prismic.io/docs/technologies/nextjs#3.3.-queries-file
It's also what next-slicezone was doing with useGetStaticPaths but we don't want to recommend this package anymore:
https://github.com/prismicio/slice-machine/tree/master/packages/next-slicezone#usegetstaticpaths
This would also allow first-class support for the Route Resolver which is very difficult to use with Next.js at the minute.
Thanks.

I don't know Next very well, does the preview works on a special page ?
I was wondering why ending the preview has to redirect you
export async function exitPreview(_: any, res: NextApiResponse): Promise<void> {
	// Exit the current user from "Preview Mode". This function accepts no args.
	res.clearPreviewData();

	// Redirect the user back to the index page.
	res.writeHead(307, { Location: "/" });
	res.end();
}

I would say ending the preview should just close the toolbar and maybe reload the current page if you need to.
I think it is only be displaying the same content without preview that the user can instantly see the difference and be sure that the preview is off.

I have a question / comment. Some users have experienced issues with previews and Next when they add this security header in their project: X-Content-Type-Options. The preview stops working.
I'd like to know if this version of the kit addresses this issue or if this is not related to Prismic at all?

@phillysnow We did at the every beginning. It was kind of hard to figure out how to help here. I decided not to think about anything related to getStaticProps because we want to allow users to have the flexibility they might need within that function, and by making a helper we'd likely be taking away that flexibility.
I would definitely love to revisit the topic, though, support previews felt like the lowest hanging fruit. Much more obvious how we can help there vs other methods. Do you have any kind of proposal in mind or would you be interested in a sort of brainstorm session?
@Heyrows Oh I think I just got that from the NextJS documentation. I am experiencing some weird bugs right now so perhaps that would be a better way, I'll report back!
@pvpg We talked about this, just don't have a solid answer for you quite yet. I'll reach out to you on slack this week, though, to learn more.

@dayhaysoos I'd be really up for brainstorming on this, at least in terms of presenting the challenges and workarounds that currently exist for this. It would probably be beneficial to include @lihbr in that conversation as she worked on the nuxt plugin which gets all the routes to generate automatically for the user:
https://github.com/nuxt-community/prismic-module/blob/master/src/generator.js

@dayhaysoos I'd be really up for brainstorming on this, at least in terms of presenting the challenges and workarounds that currently exist for this. It would probably be beneficial to include @lihbr in that conversation as she worked on the nuxt plugin which gets all the routes to generate automatically for the user:
https://github.com/nuxt-community/prismic-module/blob/master/src/generator.js

Just a side note as this generator is deprecated and built-in into Nuxt now :)

@dayhaysoos , preview works great, but I tried using the shareable link to share a draft version and it does not work (I tested on my computer and another computer too)


Question 7

the method Array.isArray() is available in also in plain Jasvascript not just in JQuery
Array.isArray()
on MDN

hmmm, indeed! Is it since ES6 or earlier?


Add Vietnamese to the list

As I promoted a PR for Vietnamese right here, I would like to update it to this list too.
https://github.com/VDS13/telegram-captcha/pull/1

Hello, @anhtuank7c
Thanks for supporting the project.)

@VDS13 I'm happy to help.
Do you have any thoughts on reCaptcha?
Any idea to make it happen?

@anhtuank7c, At the moment there are no implementation ideas yet.


Unit Test:  associations_has_many_test

Support for Asssociation
--- FAIL: TestPolymorphicHasManyAssociation (7.61s)
associations_has_many_test.go:352: Toy's ID should be created
--- FAIL: TestSingleTableHasManyAssociation (5.52s)
associations_has_many_test.go:147: Team's ID should be created
--- FAIL: TestHasManyAssociation (7.36s)
associations_has_many_test.go:52: Pet's ID should be created

if user already has 2 pets, appending another one (DB.Association("Pets").Append(&pet)) would send and include everything in the MERGE statement. While snowflake can only return IDs of inserted rows, update would not return ID if the values don't actually changed.

The solution here is to only processed inserted rows at the end of MERGE statement to populate default values (by changing the CHANGES information to APPEND_ONLY.
The side effect is that any change will not be reflected back to the existing rows. This is probably OK, because the existing items already updated in the local vars, and the db value would  also get updated.