Include Sweden Central to the statistics?

Could the table also include Sweden Central region?
It seems that the following table linked in the documentation page
:::image type="content" source="media/azure-network-latency/azure-network-latency-thmb-july-2022.png" alt-text="Chart of the inter-region latency statistics as of June 30, 2022." lightbox="media/azure-network-latency/azure-network-latency-july-2022.png":::
Does not include Sweden Central, even though the region was opened 2021, so June 2022 should include the results.
Thanks for the update.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 311b6efb-2d93-6130-96a9-867fad56bd52
Version Independent ID: a17faabf-04c6-c3da-9a37-a86b0d00cbfd
Content: Azure network round-trip latency statistics
Content Source: articles/networking/azure-network-latency.md
Service: virtual-network
GitHub Login: @mbender-ms
Microsoft Alias: mbender

@marion-msft , Thanks for the feedback.
I shall assign this thread to the author @mbender-ms to review this and update the docs as required.

Thanks for the feedback @marion-msft.
I'll take this to the product group and work on getting an update to the chart.

@marion-msft A quick update on Sweden Central - The reporting mechanism for this article was not capturing the latency information for Sweden Central, even though it came online over a year ago. I spoke with engineering and they are working to get it added. As soon as it is, we'll get the table updated. If you have a customer-critical need for specific DC to DC latency numbers, I can connect you with a teammate who can help you out.

Hi @mbender-ms,
Thanks for the update. Could you please share with me the official latency between Sweden Central and Norway East?
There is no emergency anymore with customer as we've found other ways to measure latency (eg do individual tests with Azure resources), but an official statement would be great. Thanks.

Hi @marion-msft - I'll run down that data for you and report back. Thanks for your patience!

@marion-msft Contact me via teams or email @mbender, and I'll put you in touch with my contact in engineering who manages the data on this.

This issue is being worked internally.
#please-close

Issue of Sweden Central and Sweden South is still an open issue


Some but not all Criteo fixes

WIP Criteo fixes. Criteo PyTorch still does not hit the target, but these are some known issues that need to be resolved.

Thanks for debugging the code! I will also play around with it this week.

I have briefly looked at the code and didn't spot anything yet which could cause the OOM error. If the bug isn't fixed until after NeurIPS I can also help with debugging. Two other minor comments:

For the eval_train split we currently don't shuffle, which should be changed (see here and here).
This comment is not up-to-date, since we do not use itertools.cycle anywhere in this workload.

Ignore the pylint changes, those will be fixed once https://github.com/mlcommons/algorithmic-efficiency/pull/310 goes in


pin xesmf < 8.4

Description
Just a couple of hours ago, as @malmans2 and I were hoping to get a new oceanspy release, there was a new release of ESMpy, which affected how to import xESMF. The new version (8.4) leads to the following error in oceanspy.subsample which I reproduce by simply just trying to import xesfm on the command line:

The issue and temporal solution can be seen here on (xESMF GH repo):
https://github.com/pangeo-data/xESMF/issues/212
Pinning down esmf < 8.4 (hence installing version 8.3.+) allows all tests to pass. This is a temporal solution to a problem outside of oceanspy.
Espect a PR soon enough...

I think you can unpin now: https://github.com/pangeo-data/xESMF/issues/217

will do so. I was also making some other little changes. PR coming soon!

closed by #300


Add filters in settings which shows only the newly-added settings since the last update

I propose a button to be added to the settings. It's action may be implemented as a filter. Upon click of that button it would show all the new settings and settings with new possible values to select since the last updates.
For example:

You update VS Code three times but you don't check what new settings there are.
 This filters the settings and shows you all the new settings from the last 3 versions.
Then an update to VS Code happens. Now you can again click this button once updated to see the new settings from the last 1 version.
Now say 4 updates to VS Code happen but you haven't checked what new settings there are for the last 3 updates. But after the 4th update you remember to check. When you check, the new settings from the last 4 updates are shown.

Bonus: This button shows up in some visible place (say like the same way the "Add configuration" button shows up in "launch.json") when you haven't checked and there are new settings from updates.

Thanks for the suggestion. We have actually discussed this before, and decided against it. We think that the release notes is the right place for this where we can show new settings in context of the feature area, with extra explanation, etc.
Here are some other issues https://github.com/microsoft/vscode/issues/107831 https://github.com/microsoft/vscode/issues/45093


2019 copyright update

Requirements

Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion;
Review the contributing guidelines for this repository; remember in particular:

do not modify code without testing for regression
provide simple unit tests to test the changes
if you change the schema you must patch the test databases as well, see Updating the schema
the PR must not fail unit testing

Description
2019 yearly copyright update
Use case
Describe the problem. Please provide an example representing the motivation behind the need for having these changes in place.
Benefits
copyright up to date
Possible Drawbacks
If applicable, describe any possible undesirable consequence of the changes.
Testing
NA
If so, do the tests pass/fail?
NA

Coverage remained the same at 81.365% when pulling a8c451eb88daedd46386db9a43931ee686ad321f on copyright_update into ffedb151d144d1e8ea75e3d195ccba5b6009d9d5 on master.


BUG: Bottom top button - alignment correction

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Hello PA,
I have observed that the alignment of bottom top scroll button is not at the right place, that should be in the same alignment as message button
screensort

this is my first contributation to this project and i really wanted to do this, so it's my humble request to you to please add all the required labels and assigne me this task
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Assigned!
Make sure to attach before & after screenshots in your PR and include the issue number.
Also, please star the repo before working on it.
I am the project mentor so you can always reach out to me for any help!
Happy open-source contributing!


Detailed Setup and Usage Docs

Lots of work do here.

Hey just found this from here: https://github.com/reactjs/react-rails/issues/301
There's nothing in the README about how to use this. I'm happy to contribute in writing docs, but it looks  like there's nothing at this point?
Was hoping this post would provide some context -- looks like it's broken.
Lemme know how I can help!

@taylorbrooks super!: http://www.railsonmaui.com/blog/2014/10/03/integrating-webpack-and-the-es6-transpiler-into-an-existing-rails-project/
I'll add you to our slack chat. You'll become an expert very quickly!
For anybody else that wants any mentoring in this, the best way to master it is to reach out to me<EMAIL_ADDRESS>or any members of the Shaka Code team.

@taylorbrooks where did you get the broken link. I'll fix it.

https://github.com/reactjs/react-rails/issues/301#issuecomment-113597288

Documentation was improved in #20. @taylorbrooks I'd be grateful for any feedback.


Label hidden when draw line at top of chart

I want to add a line with label at top of chart.
But the label is hidden.

You can set anchor to start or center
https://chartjs-plugin-datalabels.netlify.app/guide/positioning.html

You can set anchor to start or center
https://chartjs-plugin-datalabels.netlify.app/guide/positioning.html

This is other plugin. How I can apply this to current plugin?

Use yPadding.

set the axes 'offset' property to true and it provides a little space above the chart that helps this issue
https://www.chartjs.org/docs/latest/axes/cartesian/#common-configuration

I've got the same problem, but with a vertical line and the y-axis on the left. Activating offset on the y axis didn't help. and moving the label with xAdjust looks ugly

You could probably set the value to 100.1 and the scale would expand to next "nice" number.


COLLATION 'utf8_bin' is not valid for CHARACTER SET 'latin1'

Setup used

https://github.com/SUSE/Portus/issues/1507#issuecomment-356281128

Infos
[Mailer config] Host:     redacted
[Mailer config] Protocol: https://
Evaluated configuration:
---
email:
  from<EMAIL_ADDRESS>  name: Portus
  reply_to<EMAIL_ADDRESS>  smtp:
    enabled: false
    address: smtp.example.com
    port: 587
    user_name<EMAIL_ADDRESS>    password: "****"
    domain: example.com
gravatar:
  enabled: true
delete:
  enabled: false
ldap:
  enabled: false
  hostname: ldap_hostname
  port: 389
  method: plain
  base: ''
  filter: ''
  uid: uid
  authentication:
    enabled: false
    bind_dn: ''
    password: "****"
  guess_email:
    enabled: false
    attr: ''
oauth:
  google_oauth2:
    enabled: false
    id: ''
    secret: ''
    domain: ''
    options:
      hd: ''
  open_id:
    enabled: false
    identifier: ''
    domain: ''
  github:
    enabled: false
    client_id: ''
    client_secret: ''
    organization: ''
    team: ''
    domain: ''
  gitlab:
    enabled: false
    application_id: ''
    secret: ''
    group: ''
    domain: ''
    server: ''
  bitbucket:
    enabled: false
    key: ''
    secret: ''
    domain: ''
    options:
      team: ''
first_user_admin:
  enabled: true
signup:
  enabled: true
check_ssl_usage:
  enabled: false
registry:
  jwt_expiration_time:
    value: 5
  catalog_page:
    value: 100
  timeout:
    value: 2
  read_timeout:
    value: 120
machine_fqdn:
  value: redacted
display_name:
  enabled: false
user_permission:
  change_visibility:
    enabled: true
  create_team:
    enabled: true
  manage_team:
    enabled: true
  create_namespace:
    enabled: true
  manage_namespace:
    enabled: true
security:
  clair:
    server: ''
    health_port: 6061
  zypper:
    server: ''
  dummy:
    server: ''
anonymous_browsing:
  enabled: true
background:
  registry:
    enabled: true
  sync:
    enabled: true
    sync-strategy: initial

Portus version: 2.3.0@dd4b1644c8f275a5c851f7329c547f6317a0648f

Impact
Not sure what are the consequences
Logs
After a success push (Handling "push" event), I see this logs in background image
crono_1     | /srv/Portus/vendor/bundle/ruby/2.5.0/gems/mysql2-0.4.10/lib/mysql2/client.rb:120:in `_query': Mysql2::Error: COLLATION 'utf8_bin' is not valid for CHARACTER SET 'latin1': SELECT COUNT(*) FROM `tags` WHERE (name COLLATE utf8_bin = 'latest' AND repository_id = 1) (ActiveRecord::StatementInvalid)
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/mysql2-0.4.10/lib/mysql2/client.rb:120:in `block in query'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/mysql2-0.4.10/lib/mysql2/client.rb:119:in `handle_interrupt'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/mysql2-0.4.10/lib/mysql2/client.rb:119:in `query'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:317:in `block in execute'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/abstract_adapter.rb:484:in `block in log'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activesupport-4.2.10/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/abstract_adapter.rb:478:in `log'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:317:in `execute'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/mysql2_adapter.rb:217:in `execute'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/mysql2_adapter.rb:221:in `exec_query'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/abstract/database_statements.rb:356:in `select'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/abstract/database_statements.rb:32:in `select_all'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/abstract/query_cache.rb:70:in `select_all'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/relation/calculations.rb:270:in `execute_simple_calculation'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/relation/calculations.rb:227:in `perform_calculation'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/relation/calculations.rb:133:in `calculate'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/relation/calculations.rb:48:in `count'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/relation.rb:268:in `empty?'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/relation.rb:278:in `any?'
crono_1     | 	from /srv/Portus/app/validators/unique_tag_validator.rb:19:in `validate_each'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activemodel-4.2.10/lib/active_model/validator.rb:151:in `block in validate'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activemodel-4.2.10/lib/active_model/validator.rb:148:in `each'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activemodel-4.2.10/lib/active_model/validator.rb:148:in `validate'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activesupport-4.2.10/lib/active_support/callbacks.rb:455:in `public_send'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activesupport-4.2.10/lib/active_support/callbacks.rb:455:in `block in make_lambda'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activesupport-4.2.10/lib/active_support/callbacks.rb:192:in `block in simple'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activesupport-4.2.10/lib/active_support/callbacks.rb:504:in `block in call'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activesupport-4.2.10/lib/active_support/callbacks.rb:504:in `each'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activesupport-4.2.10/lib/active_support/callbacks.rb:504:in `call'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activesupport-4.2.10/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activesupport-4.2.10/lib/active_support/callbacks.rb:778:in `_run_validate_callbacks'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activemodel-4.2.10/lib/active_model/validations.rb:399:in `run_validations!'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activemodel-4.2.10/lib/active_model/validations/callbacks.rb:113:in `block in run_validations!'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activesupport-4.2.10/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activesupport-4.2.10/lib/active_support/callbacks.rb:778:in `_run_validation_callbacks'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activemodel-4.2.10/lib/active_model/validations/callbacks.rb:113:in `run_validations!'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activemodel-4.2.10/lib/active_model/validations.rb:338:in `valid?'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/validations.rb:58:in `valid?'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/validations.rb:83:in `perform_validations'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/validations.rb:37:in `save'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/attribute_methods/dirty.rb:21:in `save'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/transactions.rb:286:in `block (2 levels) in save'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/transactions.rb:351:in `block in with_transaction_returning_status'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/abstract/database_statements.rb:211:in `transaction'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/transactions.rb:220:in `transaction'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/transactions.rb:348:in `with_transaction_returning_status'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/transactions.rb:286:in `block in save'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/transactions.rb:301:in `rollback_active_record_state!'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/transactions.rb:285:in `save'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/associations/has_many_association.rb:41:in `insert_record'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/associations/collection_association.rb:506:in `block (2 levels) in _create_record'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/associations/collection_association.rb:419:in `replace_on_target'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/associations/collection_association.rb:414:in `add_to_target'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/associations/collection_association.rb:504:in `block in _create_record'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/associations/collection_association.rb:194:in `block in transaction'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/transactions.rb:220:in `transaction'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/associations/collection_association.rb:193:in `transaction'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/associations/collection_association.rb:503:in `_create_record'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/associations/has_many_association.rb:187:in `_create_record'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/associations/collection_association.rb:164:in `create'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/associations/collection_proxy.rb:290:in `create'
crono_1     | 	from /srv/Portus/app/models/repository.rb:152:in `add_repo'
crono_1     | 	from /srv/Portus/app/models/repository.rb:101:in `handle_push_event'
crono_1     | 	from /srv/Portus/app/models/registry_event.rb:35:in `block in handle!'
crono_1     | 	from /srv/Portus/app/models/registry_event.rb:35:in `each'
crono_1     | 	from /srv/Portus/app/models/registry_event.rb:35:in `handle!'
crono_1     | 	from /srv/Portus/lib/portus/background/registry.rb:30:in `block in execute!'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/relation/batches.rb:51:in `block (2 levels) in find_each'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/relation/batches.rb:51:in `each'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/relation/batches.rb:51:in `block in find_each'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/relation/batches.rb:124:in `find_in_batches'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/activerecord-4.2.10/lib/active_record/relation/batches.rb:50:in `find_each'
crono_1     | 	from /srv/Portus/lib/portus/background/registry.rb:28:in `execute!'
crono_1     | 	from /srv/Portus/bin/background.rb:56:in `block (2 levels) in <top (required)>'
crono_1     | 	from /srv/Portus/bin/background.rb:54:in `each'
crono_1     | 	from /srv/Portus/bin/background.rb:54:in `each_with_index'
crono_1     | 	from /srv/Portus/bin/background.rb:54:in `block in <top (required)>'
crono_1     | 	from /srv/Portus/bin/background.rb:53:in `loop'
crono_1     | 	from /srv/Portus/bin/background.rb:53:in `<top (required)>'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/railties-4.2.10/lib/rails/commands/runner.rb:60:in `load'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/railties-4.2.10/lib/rails/commands/runner.rb:60:in `<top (required)>'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/railties-4.2.10/lib/rails/commands/commands_tasks.rb:123:in `require'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/railties-4.2.10/lib/rails/commands/commands_tasks.rb:123:in `require_command!'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/railties-4.2.10/lib/rails/commands/commands_tasks.rb:90:in `runner'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/railties-4.2.10/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
crono_1     | 	from /srv/Portus/vendor/bundle/ruby/2.5.0/gems/railties-4.2.10/lib/rails/commands.rb:17:in `<top (required)>'
crono_1     | 	from bin/rails:12:in `require'
crono_1     | 	from bin/rails:12:in `<main>'
crono_1     | RuntimeError: Something went wrong while invoking: /srv/Portus/vendor/bundle/ruby/2.5.0/bin/bundler.ruby2.5 exec rails r /srv/Portus/bin/background.rb
crono_1     |   /srv/Portus/packaging/suse/portusctl/lib/runner.rb:12:in `exec'
crono_1     |   /srv/Portus/packaging/suse/portusctl/lib/runner.rb:34:in `block in bundler_exec'
crono_1     |   /srv/Portus/packaging/suse/portusctl/lib/runner.rb:30:in `chdir'
crono_1     |   /srv/Portus/packaging/suse/portusctl/lib/runner.rb:30:in `bundler_exec'
crono_1     |   /srv/Portus/packaging/suse/portusctl/lib/cli.rb:272:in `exec'
crono_1     |   /srv/Portus/vendor/bundle/ruby/2.5.0/gems/thor-0.19.4/lib/thor/command.rb:27:in `run'
crono_1     |   /srv/Portus/vendor/bundle/ruby/2.5.0/gems/thor-0.19.4/lib/thor/invocation.rb:126:in `invoke_command'
crono_1     |   /srv/Portus/vendor/bundle/ruby/2.5.0/gems/thor-0.19.4/lib/thor.rb:369:in `dispatch'
crono_1     |   /srv/Portus/vendor/bundle/ruby/2.5.0/gems/thor-0.19.4/lib/thor/base.rb:444:in `start'
crono_1     |   packaging/suse/portusctl/bin/portusctl:6:in `<top (required)>'
crono_1     | bundler: failed to load command: packaging/suse/portusctl/bin/portusctl (packaging/suse/portusctl/bin/portusctl)

This is something that we had to workaround from the official mariadb docker image. That is, we have to make sure that it uses utf. In our examples (see this one) we use the following command:
command: mysqld --character-set-server=utf8 --collation-server=utf8_unicode_ci --init-connect='SET NAMES UTF8;' --innodb-flush-log-at-trx-commit=0

This is the easiest way to fix this (after checking the issues and comments for this image). Maybe there are better/easier ways to fix this? Anyways, this is a good thing to document before the final release.

IMHO
command: mysqld --character-set-server=utf8 --collation-server=utf8_unicode_ci --init-connect='SET NAMES UTF8;' --innodb-flush-log-at-trx-commit=0
is not the right Approach as its a global setting for all databases. If someone happens to have a shared DB, which not such an uncommon case. Portus will dictate the further setup.
However I think the right way is to extend rake db:create to create a DB in the right character set and collation.  In this case we don't have to bother with that on the global level. Also the db:status could check if the db is in the right format and complain otherwise.
default: &default
  adapter: mysql2
  pool: 5
  encoding: utf8mb4
  charset: utf8mb4
  collation: utf8mb4_unicode_ci
  socket: /tmp/mysql.sock

It's bad, yeah, but I already tried your example configuration when we first encountered this and it doesn't work for me. It looks like mariadb has to be called with that command (or to provide an alternative my.cnf), or otherwise the encoding, the charset and the collation will be messed up :disappointed:
PostgreSQL doesn't have this, so using PostgreSQL instead of MariaDB might be a good option when starting as well :sweat_smile:

Hey, I've tried to start the mariaDB container with the command you pointed out above, but my portus background continues on restarting and displaying:

/srv/Portus/vendor/bundle/ruby/2.5.0/gems/mysql2-0.4.10/lib/mysql2/client.rb:120:in _query': Mysql2::Error: COLLATION 'utf8_bin' is not valid for CHARACTER SET 'latin1': SELECT COUNT(*) FROM tags` WHERE (name COLLATE utf8_bin = 'latest' AND repository_id = 4) (ActiveRecord::StatementInvalid)
11/04/2018 12:28:21bundler: failed to load command: packaging/suse/portusctl/bin/portusctl (packaging/suse/portusctl/bin/portusctl)

:'(

@Vad1mo oh ok. Thanks!

In the main portus application, I wanted to use both command, but I received this error message:

rake aborted!
LoadError: cannot load such file -- bundler/setup
/srv/Portus/config/boot.rb:5:in <top (required)>' /srv/Portus/config/application.rb:3:in <top (required)>'
/srv/Portus/Rakefile:6:in `<top (required)>'
(See full trace by running task with --trace)

With --trace:

rake aborted!
No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb)
/usr/lib64/ruby/gems/2.5.0/gems/rake-12.3.0/lib/rake/application.rb:698:in raw_load_rakefile' /usr/lib64/ruby/gems/2.5.0/gems/rake-12.3.0/lib/rake/application.rb:104:in block in load_rakefile'
/usr/lib64/ruby/gems/2.5.0/gems/rake-12.3.0/lib/rake/application.rb:186:in standard_exception_handling' /usr/lib64/ruby/gems/2.5.0/gems/rake-12.3.0/lib/rake/application.rb:103:in load_rakefile'
/usr/lib64/ruby/gems/2.5.0/gems/rake-12.3.0/lib/rake/application.rb:82:in block in run' /usr/lib64/ruby/gems/2.5.0/gems/rake-12.3.0/lib/rake/application.rb:186:in standard_exception_handling'
/usr/lib64/ruby/gems/2.5.0/gems/rake-12.3.0/lib/rake/application.rb:80:in run' /usr/lib64/ruby/gems/2.5.0/gems/rake-12.3.0/exe/rake:27:in <top (required)>'
/usr/bin/rake:23:in load
/usr/bin/rake:23:in main

Do I need to stop Portus first?

Actually, it seems you can change the charset as per https://www.a2hosting.com/kb/developer-corner/mysql/convert-mysql-database-utf-8.
Also, you've got to be joking with rake db:drop.

What is the impact of this issue? In my setup, I can't use such a global configuration.

Documentation already contains information about this (see this). As for a less hackish solution, I'm open to ideas. For now, I haven't found a solution that works and that is more elegant than the one describe above... Thank you everybody for the feedback.

What is the impact of this issue? In my setup, I can't use such a global configuration.

The recommended setup is with docker containers, and in that case you can use the following command to start the MariaDB container:
command: mysqld --character-set-server=utf8 --collation-server=utf8_unicode_ci --init-connect='SET NAMES UTF8;' --innodb-flush-log-at-trx-commit=0

This has already been written in our examples. Hope it helps.

@mssola utf8 encoding should never be used with MySQL/MariaDB, because it's broken. utf8mb4 should be used instead.
https://medium.com/@adamhooper/in-mysql-never-use-utf8-use-utf8mb4-11761243e434
https://www.eversql.com/mysql-utf8-vs-utf8mb4-whats-the-difference-between-utf8-and-utf8mb4/
I was able to fix this bug by changing the COLLATION of portus tables to utf8_bin.


Pairing should not fail due to lack of judges

[Sat Sep 20 13:09:55 2014] [error] Copied /var/www/tab/mittab/pairing_db.sqlite3 to /var/www/tab/mittab/backups/round_4_before_pairing.db
[Sat Sep 20 13:09:55 2014] [error] Traceback (most recent call last):
[Sat Sep 20 13:09:55 2014] [error]   File "/var/www/tab/mittab/apps/tab/pairing_views.py", line 100, in pair_round
[Sat Sep 20 13:09:55 2014] [error]     tab_logic.pair_round()
[Sat Sep 20 13:09:55 2014] [error]   File "/var/www/tab/mittab/libs/tab_logic.py", line 40, in pair_round
[Sat Sep 20 13:09:55 2014] [error]     validate_round_data(current_round)
[Sat Sep 20 13:09:55 2014] [error]   File "/var/www/tab/mittab/libs/tab_logic.py", line 283, in validate_round_data
[Sat Sep 20 13:09:55 2014] [error]     raise errors.NotEnoughJudgesError()
This is no good, we should not be checking that we have enough judges during pairing but rather during judge assignment.

Would this not be solved simply by removing the line here? It's the only thing in the codebase which throws that error.


Protocols - extend T model

As seen in #1924, some concern also root, i.e. global settings for the whole deploy (ACL: only owner can do this global settings).

My idea is that the global settings would be stored in the root T as its not changing and the same interface could be used within all T models consistently.

@jancimertel could you please integrate the T extension (see packages/shared/types/territory.ts)on the Backend? No special logic is needed here.

@adammertel : I agree, storing the global settings in the root T is an ideal solution. The only difference would be access rights, i.e. that for root T, only owner can edit the Validation rules.


Re-exclude /dist/traefik from .dockerignore.

The master build is currently broken. Turns out we can't remove the .dockerfile exclusion for /dist/traefik since it's needed to build the Docker image.
This PR reverts that decision taken in #1470.

Once again, the latest commit changing .travis.yml is only to show that the build should be fixed now. (We need this since make image is only called by before_deploy which seemingly isn't executed in PRs.) It will be removed once CI goes green and the review is done.

CI is green, so fix is working.


Markdown doesn't rendered correctly even set long_description_content_type

My project at PyPI: https://pypi.org/project/gff3tool/1.4.2
Libraries used:
wheel==0.31.1
setuptools==39.1.0
twine==1.11.0

Same files can be correctly used under following tools and versions (linux).
wheel (0.31.1)
setuptools (40.0.0)
twine (1.11.0)

@di You are right. I use Windows build that. I will report to setuptools and report the update back.

@hsiaoyi0504 Great, I'm going to close this issue in the meantime since there's not much Warehouse can do here, but feel free to comment if there's any other way we can help.


Adding German to MTEB

Hi everybody,
I think it would be great to add German to the Benchmark as well, in a broader manner.
I would like to support, if someone would tell me where to help I would be happy! Are the present /proposed datasets enough, should I machine-translate some?
These dataset are already here:
Classification:
AmazonCounterfactualClassification
AmazonPolarityClassification - missing (3.4 million train, 400k test)
AmazonReviewsClassification
Banking77Classification - missing (10k rows train)
EmotionClassification - missing (16k rows train)
ImdbClassification - missing (25k rows train test each)
MassiveIntentClassification
MassiveScenarioClassification
MTOPDomainClassification
MTOPIntentClassification
ToxicConversationsClassification - missing (50k train / test each)
TweetSentimentExtractionClassification - missing this could be a replacement
Clustering:
one could use XNLI German Split
TwitterURLCorpus - could be translated
MMarcoReranking
Reranking:
tba
STS:
STS22
STS-B - (MT)
STS17 - could also be MT for the 250ish rows.
Would love to have feedback!

Yeah that'd be great. I'd be happy to add an Overall German tab once we have ~30 datasets (https://huggingface.co/spaces/mteb/leaderboard)
Note that for Clustering there are some German datasets already thanks to @slvnwhrl who may also be interested in helping out with this effort.
We should aim to minimize MT and use as many human-written datasets as possible I think.
Some datasets from here https://github.com/embeddings-benchmark/mteb/pull/174 may also be available in German

Hi,
@Muennighoff thanks for including me. I'd be happy to help. And I agree, there should be enough German open source datasets out there, at least for some of the tasks. To give som suggestions:
Classification:

SCARE - The Sentiment Corpus of App Reviews with Fine-grained Annotations in German
Germeval Task 2017: Shared Task on Aspect-based Sentiment in Social Media Customer Feedback
GermEval2021 - Toxic, Engaging, & Fact-Claiming Comments
GermEval 2019 Task 1 -- Shared task on hierarchical classification of blurbs (note that the current German clustering benchmark uses the same data)
Ten Thousand German News Articles Dataset (note that the current German clustering benchmark uses the same data)

Reranking:

GermanQuAD and GermanDPR

These are some German datasets that come to my mind at the moment. I am sure there are more, although, for some tasks it might be harder to find good datasets. I also haven't checked all of the licenses of the listed datasets. This repository could also be of help: German-NLP

Hey there :)... currently working on implementing a retrieval benchmark based on GermanQuAD. Will publish a PR soon and keep you updated here. If you want to chat about it/join the discussion, here's a link to the DiscoResearch discord: https://discord.gg/FBvnqsDS

Working on it here:
https://github.com/DiscoResearch/mteb/tree/germanquad-retrieval
Here are first results for intfloat/multilingual-e5-large on the test split of deepset/germanquad.
INFO:root:MRR@1: 0.8720
INFO:root:MRR@3: 0.9091
INFO:root:MRR@5: 0.9130
INFO:root:MRR@10: 0.9139
INFO:root:MRR@100: 0.9149
INFO:root:MRR@1000: 0.9149

Are the scores on the actual HF leaderboard multiplied by 100 or why are they in the range 0-100? 🤔
And I couldn't find the code for the actual HF space. Is it not open source?

Great! Yes they are multiplied by 100 to be from 0-100 in order to make it more readable :)
Everything is open-source - Do you mean this code https://huggingface.co/spaces/mteb/leaderboard/blob/main/app.py ?

Ah yes thank you! :) I knew about the "Files" tab in spaces but somehow overlooked it this time 😅
I'm currently testing with intfloat/multilingual-e5-small.
As you might know these need to be prompted in a specific way for full capability:
https://huggingface.co/intfloat/multilingual-e5-large#usage
I can't find a corresponding model class in mtebscripts although the e5 embeddings are on the leaderboard.
And how do I contribute a benchmarks specifically?
Everything runs fine with my run_mteb_german.py.
As I understand the README and the other scripts, that's enough and you take care of running it for different embeddings?
If so the only things I see left to do are:

clean/finish up my fork a bit
host the GermanQuAD dataset in BEIR format on HF instead of generating it locally

I will create and link a draft PR in a minute, so you can compare the changes more easily ;)

Draft PR: #197

Great work! For running the evaluation, they have a section on their HF hub page: https://huggingface.co/intfloat/multilingual-e5-large#mteb-benchmark-evaluation

Therefore only one matching context can be retrieved from the corpus and MRR would be the best metric to score this, correct?

I think you can still use nDCG but MRR is fine too

FYI there is this German fork already https://github.com/jina-ai/mteb-de?ref=jina-ai-gmbh.ghost.io

FYI there is this German fork already https://github.com/jina-ai/mteb-de?ref=jina-ai-gmbh.ghost.io

Nice, do you plan on opening a PR? Would be to help 🙌

Given the merged PR it seems like this issue is resolved? Though we might still be missing a german tab on the leaderboard. If that is the case we can create a separate issue on this.

Yes will close this issue then as lots of good development. Thanks all!
Will open a new one here for the German tab and see if / how I can support !


Loss of bound values for variables assigned in a SERVICE graphPattern

(Migrated from https://openrdf.atlassian.net/browse/SES-2209 )
Federated queries like the following won't return bound values for variables assignments defined in the SERVICE graph pattern.
{code}
SELECT ?s ?bindingS ?now
WHERE {
SERVICE http://dbpedia.org/sparql {
?s a ?someType .
BIND (?s as ?bindingS)
BIND (now() as ?now)
}
} LIMIT 1
{code}

This works as expected with the #812 fix


Error in camper.js when null or undefined is passed to 'setup'

#36 Introduced a bug that can crash the app under certain circumstances.
If a user submits a post with a null or undefined 'setup' value, the react app can't render the page or allow new posts to be added.
@jenovs' codepen api request is the thing currently triggering the problem (don't click this unless you know how to use Postman to clean up after yourself :) ) http://codepen.io/jenovs/pen/pNWLmy?editors=0010
This should probably be fixed on the backend, but the frontend should handle these empty values to

I just tested with not checking a checkbox and not filling in other against the code I submitted to solve #43 and if I'm understanding this issue correctly, #48 resolves this as well.

BTW, I didn't mean to imply that there was not still an issue with a lack of validation. Rather, I see no error when submitting empty values.

Submitting empty values is ok, but the problem comes when using something like Postman or an Ajax request to post null values.
It's not standard behaviour, and we'll lock down the access origin stuff soon so it won't be an issue, but backend validation would still be a nice safety net.


Some buttons doesn't work on issues screen

Description
After update from 1.15.9 to 1.16.1 the close issue button stop working, when you hit the button nothing happens.
Checking screen I detect some buttons stop working too:

Add time
Start timer
Edit issue title

Other buttons still works:

New Issue
Comment
Tags
Milestone

I update gitea to 1.17.0+dev-351-g54961f3ac but get the same result.
Gitea Version
1.16.1 and up
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.25.1
Operating System
linux
How are you running Gitea?
Gitea server is downloaded from gitea repo.
Gitea is running as systemd service.
server is ubuntu 20.20.4
Database
SQLite

More info: Tested on Firefox and Chrome do the same result.

Any JS errors visible in the browser console/devtools?

Browsers show this message when reload page:
jQuery.Deferred exception: Cannot read properties of undefined (reading 'adminUserListSearchForm') TypeError: Cannot read properties of undefined (reading 'adminUserListSearchForm')
but no reactions when click on buttons

Remove your customized templates.

Solved. Now I'll try to restore mermaid and katex render to pages.
Thanks for the solution.

@silverwind how about show JS errors to end users, like this one https://github.com/go-gitea/gitea/pull/18971
There should be no JS error during normal usage. If there is an error, it must be reported and fixed.

Yeah, sounds like a good idea.


Update state of BottomNavigationBar if background updates

This tracks the backgroundColor of the selected item  and updates the widget accordingly.
Note that I do not fully understand why we need to keep track of the _backgroundColor (and use widget.items[widget.currentIndex].backgroundColor directly...
Fixes #19653

I am not sure if I am supposed to add a test.
I looked in the current tests, but nothing is testing the color of the widget (neither should I know how to do it). So I think we need to accept this is untestable?
Please correct me if I am wrong

@HansMuller is there anything I can do to expedite the review of this pull request?
I mention you because on https://github.com/flutter/flutter/wiki/Triage it mentions you as the Material widget specialist :)

@nathansamson
Sorry about the inexplicable delay in reviewing this. I'm looking now.

Since this fix had been idling for so long, I created a new PR, updated it, and added a regression  test: #20890.


Use polling for login and room joining

Closes https://github.com/TypeFox/open-collaboration-tools/issues/35
Attempts to fix https://github.com/TypeFox/open-collaboration-tools/issues/34
Uses a different networking solution when logging in and joining rooms. Instead of waiting until either action is completed until returning a result, both now are using a polling approach. This has two benefits:

We can use the polling of the client to send updates about the process to the user (e.g. whether the join request is currently awaiting input from the host).
It is less affected by a few bad requests. Since we regularly resend the polling requests, we can always ask again whether the login or join request has succeeded.

This is a breaking change in the server communication protocol. After merging this, we should update the protocol version to 0.2.0.

@spoenemann I cannot reproduce. How did you test the feature? Did you use vsce package --no-dependencies to build the extension and install that in a second vscode instance?


Use securekey-textarea widget for SA json fields

Changes the widget type for SA json fields from textbox to secure-textarea
Please notice the shield icon in the SA json field. Clicking the shield lets the user select one of the secure keys defined in the namespace.
A corresponding PR in cdap-ui adds the securekeys tab in Namespace Admin and also makes the securekey-textarea widget non-editable (so that the user will only be able to add the value as a secure macro).

Can you please add the screenshot in the PR description on how the change was tested?

Added a screenshot.

Can you please add the screenshot in the PR description on how the change was tested?

Added a screenshot.

What will be the case for existing pipelines? How will the UI look like? Have we tested it? Also since it has been using textarea from sometime now, do we have a PM approval?


⚠ Bofrost.lu has degraded performance

In 218bc30, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1257 ms

Resolved: Bofrost.lu performance has improved in 3414537 after 11 minutes.


syncHistoryWithStore is removing (or ignoring) parseQueryString from history object

i've got some code that does this:
const memoryHistory = useRouterHistory(createMemoryHistory)({ parseQueryString, stringifyQuery})
memoryHistory.push(req.originalUrl)
const reduxStore = configureStore(memoryHistory)
const history = syncHistoryWithStore(memoryHistory, reduxStore)

when this code is called on a server render with params that aren't handled correctly out of the box (ie, /foo?a[]=1) my location object ends up with incorrect query params:
query: { 'a[]': 1 }

and these values are also stored in my routing store.
if i skip the syncHistoryWithStore call and set const history = memoryHistory my code works as expected and the location object's query object is set correctly (but not in my routing store)
query: {a: [1] }

i've looked over the syncHistoryWithStore code and i can't see anything off the top of my head that could be contributing to this but i've definitely narrowed it down. have you seen anything like this before?

actually i think the issue is here:
https://github.com/reactjs/react-router-redux/blob/master/src/sync.js#L103
this is overriding any previously set listen method and that's how useQueries works:
https://github.com/ReactTraining/history/blob/v2.x/modules/useQueries.js#L97

nevermind, this looks like user error. sorry for the noise.


works with electron 3.0.9 but not with 5.0.0

The repo download worked great, but when I tried to copy this process into my electron 5.0.0 project this line fails:
this.ipc = (<any>window).require("electron").ipcRenderer;
Is there some updated way to get a reference to the ipcRenderer from inside Angular?

Thanks for your issue!
I was able to reproduce the problem. Seems like the additional node features (like require) need to be enabled before they can be used using the nodeIntegration flag.
  win = new BrowserWindow({
    width: 800,
    height: 600,
    webPreferences: { nodeIntegration: true }
  });

The flag was always there but its default value was changed to false in a recent release.
Fixed in 47d6002f8f13935ff62d71adc21828f371b1eb67.

Confirmed fixed!  Thanks for the excellent tutorial and the super fast
reply.
If you have any insight into making this combo of Electron/Ang7/TypeScript
run in the VSCode debugger that's my only remaining struggle.  The debugger
isn't able to find the corresponding Javascript files even when I set the
OutFiles param to the absolute location under electron/dist/*.js.
thanks again,
Deanna
On Fri, Apr 26, 2019 at 1:30 AM Lukas Marx<EMAIL_ADDRESS>wrote:

Thanks for your issue!
I was able to reproduce the problem. Seems like the additional node
features (like require) need to be enabled before they can be used using
the nodeIntegration flag.
win = new BrowserWindow({
width: 800,
height: 600,
webPreferences: { nodeIntegration: true }
});
The flag was always there but its default value was changed to false in a
recent release.
Fixed in 47d6002
https://github.com/LukasMarx/angular-electron/commit/47d6002f8f13935ff62d71adc21828f371b1eb67
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/LukasMarx/angular-electron/issues/2#issuecomment-486942352,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEL4OV4AMAGGJYNVT6C2JBLPSKORJANCNFSM4HIQUZSQ
.


Wallet sync problem ?

Hey, i just downloaded latest version of wallet. But block number at 57. Is there anything to do or bootstrap ?

Just be extraordinarily patient.  :)

I'm syncing my newly created wallet using Linux desktop client (wallet) for more than 24 hours as of now...
Synchronizing, Block: 313600 (4263043)
Is this normal?
log_2017-12-28_05-07-55.4.log

Now it states:
Running, Block: 313603 (4266505)
but it's apprently not synced up to latest block.. and considering another 5 hours of syncing from my last post there is very little progress. It doesn't not seem like this is going to be finished any time soon.

Follow this tutorial. Only difference for linux is location of ldb file: /home//RaiBlocks/
https://steemit.com/utopian-io/@ankarlie/tutorial-how-to-install-the-raiblock-desktop-wallet-with-synchronization-short-cut

What about macOS ? is it suitable ?

The best latest guide for quick syncing by downloading the ledger is on the Raiblocks official reddit daily discussion page, at the bottom of the main post: https://www.reddit.com/r/RaiBlocks/comments/7ml95j/faq_daily_general_discussion_december_28_2017/

Yes. Only difference is location of ldb file. It’s in Library/RaiBlocks
On Dec 28, 2017, 08:57 -0500, coinheo<EMAIL_ADDRESS>wrote:

What about macOS ? is it suitable ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks, i just handled!


Error with units

Station Pairs = ("WV053", "WVO54", )  # Units issue
Start and end times were full duration of the stations
The same behavior was observed for  Station Pairs = ("WV053", "WVO55", )

(VAQ55, VAQ56),

I had success processing "WV053" using "WVO54" as the reference when I specified identical start and end times for both stations. These are the values I used.
WVO53 = ["4P", "WVO53",  '2016-04-25T22:13:06', '2016-05-14T05:25:17']
WVO54 = ["4P", "WVO54", '2016-04-25T22:13:06', '2016-05-14T05:25:17']

Here is the associated request_df that contains data from WVO53, WVO54, and WVO55.
MMitchell_df.csv
channels = ["LFE", "LFN", "LFZ", "LQE", "LQN"]

# WVO53 2016-04-23T22:43:07 (114) - 2016-05-16T14:59:31 (137)
# WVO54 2016-04-22T19:12:22 (113) - 2016-05-16T18:53:36 (137)
# WVO55 2016-04-25T22:13:06 (116) - 2016-05-14T05:25:17 (135)

WVO53 = ["4P", "WVO53",  '2016-04-25T22:13:06', '2016-05-14T05:25:17']
WVO54 = ["4P", "WVO54", '2016-04-25T22:13:06', '2016-05-14T05:25:17']
WVO55 = ["4P", "WVO55", '2016-04-25T22:13:06', '2016-05-14T05:25:17']
# REV06 = ["8P", "REV06", '2020-06-02T19:00:00', '2020-07-13T19:00:00']

stations = [WVO53, WVO54, WVO55,]
# stations.append(REV06)

request_list = []
for entry in stations:
    for channel in channels:
        request_list.append(
            [entry[0], entry[1], "", channel, entry[2], entry[3]]
        )

# Turn list into dataframe
request_df =  pd.DataFrame(request_list, columns=fdsn_object.request_columns)
request_df


pentablet: Unify packages?

I began packaging the user space driver for the XPPen Artist 12 (2nd Generation) drawing tablet and noticed that it’s already been packaged as xp-pen-deco-01-v2-driver named after a different device.
It appears that many devices are covered by the same software:
list.mjs
#!/usr/bin/env node

import { JSDOM } from "jsdom";

const prefix = "/download/file/id/1936/";
const devicesByDownload = {};

const index = await JSDOM.fromURL("https://www.xp-pen.com/download");
for (const itemLink of index.window.document.querySelectorAll("#productList > li > a")) {
  const item = await JSDOM.fromURL(itemLink.href);
  const downloadLink = item.window.document.querySelector(`a[href^="${prefix}"]`);

  if (downloadLink) {
    const response = await fetch(downloadLink.href, { method: "head" });
    const disposition = response.headers.get("content-disposition");

    (devicesByDownload[disposition] ||= []).push(itemLink.textContent.trim());
  }
}

console.log(devicesByDownload);

$ ./list.mjs
{
  'attachment; filename="XPPen-pentablet-<IP_ADDRESS>323-1.x86_64.tar.gz"': [
    'Artist Pro 16',
    'Artist 24 Pro',
    'Artist 22R Pro',
    'Artist 22E Pro',
    'Artist 22 Pro',
    'Artist 16 Pro',
    'Artist 15.6 Pro',
    'Artist 13.3 Pro',
    'Artist 12 Pro',
    'Artist 24',
    'Artist 22 (2nd Generation)',
    'Artist 15.6',
    'Artist 16 (2nd Generation)',
    'Artist 13 (2nd Generation)',
    'Artist 12 (2nd Generation)',
    'Artist 10 (2nd Generation)',
    'Artist 12',
    'Innovator 16',
    'Deco Pro SW/MW',
    'Deco Pro S/M',
    'Deco LW',
    'Deco L',
    'Deco MW',
    'Deco M',
    'Deco mini7W',
    'Deco mini7',
    'Deco mini4',
    'Deco 03',
    'Deco 02',
    'Deco 01 V2',
    'Deco 01',
    'Deco Fun',
    'Star G960S Plus',
    'Star G960S',
    'Star G960',
    'Star G640S',
    'Star G640',
    'Star G430S',
    'Star G430',
    'Star 06',
    'Star 05',
    'Star 03',
    'AC 19'
  ]
}

Notably this includes the Star G430 for which xp-pen-g430-driver also exists using an older source.
Would a unification to pentablet be appropriate?
@virchau13, @IvarWithoutBones

A quick script reveals that all of the downloads have the same sha256 hash, so it seems perfectly fine to do this.
A couple of questions:

Although this is the driver for quite a lot of the tablets, it is not the driver for all of them. Should we

a) rename xp-pen-deco-01-v2-driver to xp-pen-pentablet-driver and hope people pick up on which tablets it does and does not work for, or
b) make a package collection xpPenDrivers.deco-01-v2, xpPenDrivers.artist-pro-16, etc., where some names are aliases to the same package?

What should I do about the datadir? Currently it's set to /var/lib/xppend1v2. Should it be renamed to something more common (I dunno, /var/lib/xp-pentablet)?

Taking option (1b) above would allow us to use different data directories between different drivers if necessary, but I believe having shared settings across different tablets might be useful, so we should probably keep the data directory the same.

Although this is the driver for quite a lot of the tablets, it is not the driver for all of them.

Looks like it is now. I don’t see any downloads for other software:
list.mjs
#!/usr/bin/env node

import { JSDOM } from "jsdom";

dispositionByDownload = {};

const index = await JSDOM.fromURL("https://www.xp-pen.com/download");
for (const itemLink of index.window.document.querySelectorAll("#productList > li > a")) {
  const item = await JSDOM.fromURL(itemLink.href);
  const downloads = [...item.window.document.querySelectorAll(".info_right_main")]
    .filter((section) => /Debian|Red Hat/.test(section.querySelector(".system").textContent))
    .flatMap((section) => [...section.querySelectorAll("a")].map((a) => a.href));

  for (const download of downloads) {
    const response = await fetch(download, { method: "head" });
    const disposition = response.headers.get("content-disposition");

    (devicesByDownload[disposition] ||= []).push(itemLink.textContent.trim());
  }
}

console.log(dispositionByDownload);

$ ./list.mjs
{
  'attachment; filename="XPPen-pentablet-<IP_ADDRESS>323-1.x86_64.tar.gz"': [
    'Artist Pro 16',
    'Artist 24 Pro',
    'Artist 22R Pro',
    'Artist 22E Pro',
    'Artist 22 Pro',
    'Artist 16 Pro',
    'Artist 15.6 Pro',
    'Artist 13.3 Pro',
    'Artist 12 Pro',
    'Artist 24',
    'Artist 22 (2nd Generation)',
    'Artist 15.6',
    'Artist 16 (2nd Generation)',
    'Artist 13 (2nd Generation)',
    'Artist 12 (2nd Generation)',
    'Artist 10 (2nd Generation)',
    'Artist 12',
    'Innovator 16',
    'Deco Pro SW/MW',
    'Deco Pro S/M',
    'Deco LW',
    'Deco L',
    'Deco MW',
    'Deco M',
    'Deco mini7W',
    'Deco mini7',
    'Deco mini4',
    'Deco 03',
    'Deco 02',
    'Deco 01 V2',
    'Deco 01',
    'Deco Fun',
    'Star G960S Plus',
    'Star G960S',
    'Star G960',
    'Star G640S',
    'Star G640',
    'Star G430S',
    'Star G430',
    'Star 06',
    'Star 05',
    'Star 03',
    'AC 19'
  ],
  'attachment; filename="XPPen-pentablet-<IP_ADDRESS>323-1.x86_64.deb"': [
    'Artist Pro 16',
    'Artist 24 Pro',
    'Artist 22R Pro',
    'Artist 22E Pro',
    'Artist 22 Pro',
    'Artist 16 Pro',
    'Artist 15.6 Pro',
    'Artist 13.3 Pro',
    'Artist 12 Pro',
    'Artist 24',
    'Artist 22 (2nd Generation)',
    'Artist 15.6',
    'Artist 16 (2nd Generation)',
    'Artist 13 (2nd Generation)',
    'Artist 12 (2nd Generation)',
    'Artist 10 (2nd Generation)',
    'Artist 12',
    'Innovator 16',
    'Deco Pro SW/MW',
    'Deco Pro S/M',
    'Deco LW',
    'Deco L',
    'Deco MW',
    'Deco M',
    'Deco mini7W',
    'Deco mini7',
    'Deco mini4',
    'Deco 03',
    'Deco 02',
    'Deco 01 V2',
    'Deco 01',
    'Deco Fun',
    'Star G960S',
    'Star G960',
    'Star G640S',
    'Star G640',
    'Star G430S',
    'Star G430',
    'Star 06',
    'Star 05',
    'Star 03',
    'AC 19'
  ],
  'attachment; filename="XPPen-pentablet-<IP_ADDRESS>323-1.x86_64.rpm"': [
    'Artist 24',
    'Artist 22 (2nd Generation)',
    'Artist 15.6',
    'Artist 16 (2nd Generation)',
    'Artist 13 (2nd Generation)',
    'Artist 12 (2nd Generation)',
    'Artist 10 (2nd Generation)',
    'Artist 12',
    'Innovator 16',
    'Deco Pro SW/MW',
    'Deco Pro S/M',
    'Deco LW',
    'Deco L',
    'Deco MW',
    'Deco M',
    'Deco mini7W',
    'Deco mini7',
    'Deco mini4',
    'Deco 03',
    'Deco 02',
    'Deco 01 V2',
    'Deco 01',
    'Deco Fun',
    'Star G960S Plus',
    'Star G960S',
    'Star G960',
    'Star G640S',
    'Star G640',
    'Star G430S',
    'Star G430',
    'Star 06',
    'Star 05',
    'Star 03',
    'AC 19'
  ]
}

What should I do about the datadir?

I’d suggest whatever the normal behavior of the application is. If following the download instructions for multiple tablets just repeatedly installs the same application and reuses the same datadir, that’s what the Nix package should do.

Checking in on the status of this?

I almost packaged up a new version of the driver same as @AndrewKvalheim before I realized there's duplication.
Few notes for unification however:

It should not be necessary to require running as root. I managed to get this working using proper udev rules that grant permissions to the device to currently logged in user
/var/lib files are only read as far as I can tell. They belong in /usr/share.
Desktop file should be packaged so that it can be run without going into console

I think this issue has been open for too long :P
@sochotnicky If you can make a PR with your new version (optionally with package unification), I'll test it and approve it.
Just a question:

/var/lib files are only read as far as I can tell. They belong in /usr/share.

Are they? When I tested  the older version a year ago, modifying settings in the GUI would result in changes to the files. If that's no longer the case then it should definitely be moved under /usr/share.

I've started cleaning up the package, noticed some additional oddities (i.e. we call sed on the binary to replace a string where it looks for configs which is very brittle). I'm trying to replace it with buildFHSEnv but hitting some issues (I am probably "holding it wrong").
All that just to say - I might not get to finalize this rework anytime soon.

OK, put together a draft PR in https://github.com/NixOS/nixpkgs/pull/277176. It's not yet finished/fully tested since I don't have the tablet with me at this moment. Should get to it in the next few days hopefully. In the meantime perhaps people can look it over/try it out.

I've tested this under Wayland and X11 with a XP-Pen Artist 12 (2nd Gen).
The application loads on both with the same general functionality. However, on Wayland the Work area tab doesn't mirror what is on the screens.
That said, while the Diagnostic tool sees the pen, it does not seem to be picked up by the system as a mouse, table, or other input.
It isn't clear whether this relates to the underlying system or this package, and I am unsure when I'll be able to test on a different distro.
Some searching did bring up the suggestion of adding a file such as /usr/share/libwacom/xp-pen-artist-12-2.tablet which I've done manually, but the device still fails to be detected by libwacom-list-local-devices.
$ xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Elan Touchpad                           	id=10	[slave  pointer  (2)]
⎜   ↳ Elan TrackPoint                         	id=11	[slave  pointer  (2)]
⎜   ↳ HANVON UGEE Artist 12 (2nd Gen) Mouse   	id=15	[slave  pointer  (2)]
⎜   ↳ HANVON UGEE Artist 12 (2nd Gen)         	id=16	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=8	[slave  keyboard (3)]
    ↳ Integrated Camera: Integrated C         	id=9	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=12	[slave  keyboard (3)]
    ↳ ThinkPad Extra Buttons                  	id=13	[slave  keyboard (3)]
    ↳ HANVON UGEE Artist 12 (2nd Gen) Keyboard	id=14	[slave  keyboard (3)]

@altsalt I can confirm that the work area problem on wayland is in the driver and has nothing to do with the packaging, because it has done the same to me on both arch and fedora. That's probably because the driver application runs on xwayland, but the thing I know for sure is that it has to be fixed by xp-pen directly.
I'd like to test the PR too with my Deco 02, but I'm new to nixos, so I'll have to figure out how to add it to my flake.
I'll let you know if I'm able to

@sochotnicky I'm testing your PR right now, and it appears that /usr/lib/pentablet is still modified when the user changes the settings in the driver GUI. Seems that we need to bind-mount /usr in the FHS env to a writable directory. Perhaps /var/lib/xp-pentablet?
We'll also need to make this into a NixOS module to support the udev rules.

I saw this suggestion and made some modifications.
We also created nixosModule.
nixosModules now creates a path under /var/lib and copies the config.
We have confirmed that it works without using buildFHSEnv, but please consider continuing to use it if it is a good solution for your config path.

nixosModule

{ config, pkgs, lib, ... }:
with lib;
let
  cfg = config.services.xserver.xp-pentablet;
  dataDir = "/var/lib/xppenconf";
in
{
  options = {
    services.xserver.xp-pentablet = {
      enable = mkOption {
        type = types.bool;
        default = false;
        description = lib.mdDoc ''
          Whether to enable the xp-pen-tablet.
        '';
      };
    };
  };
  config = mkIf cfg.enable {
    hardware.uinput.enable = true;

    environment.systemPackages = [ pkgs.xp-pentablet ]; # provides xsetwacom

    services.udev.packages = [ pkgs.xp-pentablet ];

    system.activationScripts.xp-pentablet-config.text = ''
      install -m 755 -d "${dataDir}/conf/xppen"
      find ${pkgs.xp-pentablet}/usr/lib/pentablet/conf -type f | while read -r file; do
        if [ ! -f ${dataDir}/conf/$(basename ''${file}) ]; then
          install -m 666 "''${file}" "${dataDir}/conf/xppen/$(basename ''${file})"
        fi
      done
    '';
  };
}


App Workspace debug keystore, update documentation

Would be cool to add to App Workspace's documentation the need of generating a debug keystore to run the boilerplate. This answer helped me with it.

Feel free to improve it


[Spark-37715][SQL][BUILD]Docker integration tests: Tweak docs and remove unneeded dependency

What changes were proposed in this pull request?
These are a couple of changes I found worthwhile while running docker integration tests for https://github.com/apache/spark/pull/34745.
JIRA: https://issues.apache.org/jira/browse/SPARK-37715
The doc changes are minor fixes to add the missing repository to the suggested command to run the docker integration tests.
The library change relates to this comment: https://github.com/apache/spark/pull/34745#discussion_r773084417; I don't know if my testing was thorough enough, but I found that the referenced dependency was not needed and could be removed.
Why are the changes needed?
The doc changes are needed because the current suggested command is missing the docker repository so will not work in its current state.
The library removal is needed because the build fails when the ojdbc6 package is included because the referenced library is no longer available in jfrog: https://camunda.jfrog.io/ui/native/public/com/oracle/ojdbc6
Does this PR introduce any user-facing change?
No
How was this patch tested?
Attempted to run all the docker integration tests locally by running
ENABLE_DOCKER_INTEGRATION_TESTS=1 ./build/sbt -Pdocker-integration-tests "testOnly *IntegrationSuite"

Assuming this didn't miss any tests, all the tests passed.

Can one of the admins verify this patch?

@sarutak , I pulled these changes (with modifications based on your feedback) out of https://github.com/apache/spark/pull/34745. Let me know if I've missed anything.

ok to test.

@tdg5 This PR changes not only comments but also the build definition (SparkBuild.scala). So, could you file a JIRA just in case, and modify the title of this PR like [SPARK-XXXX][SQL][BUILD]... ?

Test build #146456 has started for PR 34979 at commit c7b279b.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50931/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50931/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/50931/

Test build #146456 has finished for PR 34979 at commit c7b279b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/146456/

Can one of the admins verify this patch?

@sarutak , JIRA created and title updated

ok to test

Test build #146497 has started for PR 34979 at commit c7b279b.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50973/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50973/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/50973/

Test build #146497 has finished for PR 34979 at commit c7b279b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/146497/

@tdg5
The library removal is needed because the build fails when the ojdbc6 package is included because the referenced library is no longer available in jfrog: https://camunda.jfrog.io/ui/native/public/com/oracle/ojdbc6

I think that the more justified reason to remove odbc6 is it no longer used by Spark right?
Spark uses ojdbc8 for docker-integration-tests whose setting is in pom.xml.

Can one of the admins verify this patch?

ok to test

Test build #146546 has started for PR 34979 at commit c7b279b.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/51021/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/51021/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/51021/

Test build #146546 has finished for PR 34979 at commit c7b279b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/146546/


Fix typo

/rest/i -> REST

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

@dougseven,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge. Thanks.

@jborsecnik
Hi Jeff.  Doug is a senior leader on my team.  I don't believe he receives these messages from GitHub. I reviewed the change made in the MD file and approve it.

#sign-off

@SteveWohl: I'm sorry - only the author of this article, @dougseven, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


How to move scene in from left?

<EMAIL_ADDRESS>Removed support for pushing things from left side?

Could you clarify?

@FrankSalad Do you mean having the new scene slide in form the left side to the right, instead from the right to the left?
@aksonov If so I have the same question(s):

For scene transitions ex. SlideDown, SlideUp, SlideFromRight, SlideFromLeft, how can those 4 be applied on the next/prev scene? I think by default there is only 2 that work that I've seen in the demo.
For other transitions, like FlipRight/FlipLeft, how can those be applied on the next/prev scene? Is it possible?

@aksonov like Tinder - there's a center card (swiper), right card (messages) and left card (settings). When the left nav button is pressed the whole interface slides right to place the left card in the center.

Maybe we should wait for RN0.25 to allow custom animations. Closing it for now.

@aksonov Is there any news regarding this ?

Some work was started in #868 which has been published, looking for help with additional animations.


Breadcrumb

Fixes #1398
By breaking the TOC into sub-TOCs, we really need to enhance the breadcrumb to improve navigation. I tried to add here the sub-sections needed. Please review.
Also, because of the new universal header, I've removed the first link to Docs. Is that still a requirement? @dend @bradygaster
Azure doesn't have that as the first link.

LGTM.  I'd say :shipit: when ready.


health and disk I/O error

The acme-dns has a unexpected behavior. When I call https://github.com/joohoi/acme-dns#health-check-endpoint we see a report it works correct, but it doesn't correct, we can't do any operations with sqlite.
➜  curl -v http://acme.exapmle.com/health
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to acme.exapmle.com (<IP_ADDRESS>) port 80 (#0)
> GET /health HTTP/1.1
> Host: acme.exapmle.com
> User-Agent: curl/7.58.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx/1.15.10
< Date: Tue, 21 May 2019 22:40:57 GMT
< Content-Length: 0
< Connection: keep-alive
< Vary: Origin
<
* Connection #0 to host acme.exapmle.com left intact

➜  curl -X POST http://acme.exapmle.com/register
{"error": "disk I/O error"}

acme-dns version: 0.7.2

The health check endpoint can be used to ensure the server is reachable. But it does not validate the server is functioning properly.

@Kugelschieber
So why do we need health check if it doesn't check anything?

It's just an endpoint to check wether the service is reachable or not. It does not make sure it's working correctly. My first guess is that you have misconfigured the server somehow.

Acme-dns is working in kubernetes. SQLite located in cephfs. SQLite is becoming unreachable when cephfs doesn't availiable or restarted. Your health check doesn't check it, so kubernetes can't restart acme-dns. I receive I/O error after this situation.

Running acme-dns inside Kubernetes isn't a good idea. Kubernetes uses port 51 (DNS) for service discovery that collides with acme-dns.

@socketpair


Enable Haskell CI GHA trigger for main branch

Changelog
- description: |
    Enable Haskell CI GHA trigger for `main` branch
# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  # - breaking       # the API has changed in a breaking way
  # - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  # - improvement    # QoL changes e.g. refactoring
  # - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
   - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
  # - documentation  # change in code docs, haddocks...

Context
Currently merge groups' CI run takes more than 1 hr.

This PR adds trigger for main branch which should populate cache and make it available to all child branches.
https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#restrictions-for-accessing-a-cache
Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated. See Running tests for more details
[ ] Self-reviewed the diff

Nice, I didn't about those cache restrictions :+1:


[Feature Request] gif to webp

Is your feature request related to a problem? Please describe.
15MB to big.
Describe the solution you'd like
Single function, gif converted to webp

单一功能,gif转为为webp

Describe alternatives you've considered
No response
Additional context
Simple format conversion, canvas can be easily implemented, but animations can only be converted to single frames

单纯的格式转换,canvas可以轻易实现.但是动画只能转换单帧.

Can we combine the advantages of both?
mk33mk333/wasm-im

that one have 14-18S, original size 33% encode. wasm file have 4MB.
demo https://renzhezhilu.github.io/webp2jpg-online-demo/src/gifToWebp-Stable/gifToWebp-Stable.html

xiaozhuai/webp_encoder

that one have 1.5-5S, original size 80%-120% encode., wasmfile 500KB.
demo https://xiaozhuai.github.io/webp_encoder/

I really don't understand what you are asking me? You are saying multiple things and I don't know what you think you are missing?

Thank you, I have found a solution
.
https://github.com/xiaozhuai/webp_encoder/tree/master/dist


Update make_spec.sh

We would like to add some improvents to make_spec.sh

tarball file can be sourced based on name and version
tarball file name can be simplified

lgtm

After discussion with Max, I've decided to close it


Native translation support (or markup in s)

See https://notifications.spec.whatwg.org/ for an example. I think it would be good for the clarifying text to be inside a <small>.

Done. Use Translations: 简体中文 https://w3c-html-ig-zh.github.io/notifications/whatwg/. Comma-separated if you have more than one.

I don't think that does quite what I want. It would no longer say "Simplified Chinese" in a title and it would no longer have an accurate lang attribute.

Ah, I didn't look at all the markup. Be specific about what you want. ^_^
Hmm, I can either expand the syntax to take a title and a lang, or just let it be raw HTML. Do you anticipate ever needing anything more than text/title/lang/url?

I don't know. Maybe hreflang too? I'm not really experienced with linking to translations. This is a new thing for me.

Okay, thinking of this format:
Translation: <lang-code> <url> [ [ , name <name-in-spec-lang> ] || [ , native-name <name-in-the-lang> ] ]?

native-name is displayed in text content. If it's missing, name is displayed. If that's missing, use lang code.
name is displayed in the title. if it's missing, use lang-code.
So for your line you'd do:
Translation: zh https://w3c-html-ig-zh.github.io/notifications/whatwg/, name Simplified Chinese, native-name 简体中文

What does "use lang code" mean?

Also, we could let bikeshed keep the database of name/native-name so all you need is the URL and language, if we're automating. Might get a little ahead of ourselves with that, given the number of translations, but who knows.

The reason I don't want to do that is (a) there's a lot of languages, and (b) "name" is written in the spec's language.  While all W3C specs are written in American English, I don't see a reason to bake in that assumption to all Bikeshed-using documents. (I do in fact currently make that assumption in a few parts, like auto-generated headings, but it's fixable.)
Then again, maybe I could go ahead and do so, and just allow for the possibility of specifying a name in the spec's language later.
I did look into using existing dbs for this information, but it seems hard to do?  In particular, there's multiple types of language codes.
...okay, so here's the plan.  I'll go ahead and do what I said in https://github.com/tabatkins/bikeshed/issues/600#issuecomment-185431658.  I'll also maintain a manually-updated list of lang-code => english/native name mappings; if the lang code is on the list, you can omit that information from your Translation line.  So all you'll have to do is write Translation: zh <url> and be done with it.  But if someone is providing a translation in a new language, they can still supply all the info, if they don't want to bother with adding it to Bikeshed.

And done.  It's as I described above: just put a Translation: zh https://w3c-html-ig-zh.github.io/notifications/whatwg/ line in your metadata, and Bikeshed will fill in the rest (better than you have currently, per Google recommendations!).

Nevermind, use zh_CN - the zh lang code is for the "Chinese" macrolanguage, not Simplified Chinese specifically.

Hmm, should that not be zh-CN (or maybe zh-cn as Wikipedia seems to do) with a hyphen? Also, is there a way to have this appear as the last <dl> item?

I can go ahead and accept all those variations (I'll canonicalize it to lowercase with dashes, and just convert whatever you entered into that).
I can definitely move it to below all the non-custom values.  I can't easily adjust the order relative to custom values without weird tweaking that I haven't thought thru yet.

Okay, I canonicalize the code you use.  Translations are already the very last built-in bit of header stuff.


Support CUDA on Julia 1.9+ via a package extension.

This PR adds a package extension for CUDA on Julia 1.9+, with support for CUDA.jl versions 4 and 5. ~It does not change anything for older Julia, where CUDA support remains implemented through the Requires package.~ It drops support for Julia < 1.9 and CUDA.jl < 4.
The file test/test_cuda_extension.jl, not included from runtests.jl, tries to verify that the CUDA extension works for a variety of Julia/CUDA.jl/CUDA runtime versions. Possibly it should use a more demanding ONNX file, in case that affects the amount of needed libraries.
Fixes #27.

Codecov Report
Attention: 12 lines in your changes are missing coverage. Please review.

Comparison is base (dfb67d6) 89.60% compared to head (5f07cf3) 84.16%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #32      +/-   ##
==========================================
- Coverage   89.60%   84.16%   -5.44%
==========================================
  Files           3        4       +1
  Lines         375      360      -15
==========================================
- Hits          336      303      -33
- Misses         39       57      +18

Files
Coverage Δ

src/ONNXRunTime.jl
100.00% <100.00%> (ø)

ext/CUDAExt.jl
0.00% <0.00%> (ø)

src/highlevel.jl
81.25% <0.00%> (-9.78%)
:arrow_down:

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

The tests fail on Julia 1.9 and later because the test  environment specifies CUDA 3 and the package extension has a CUDA 4, 5 compat. There are some different ways forward but it depends on the support ambition for Julia and CUDA versions.

Most radical is to make a breaking release and drop support for CUDA < 4 and Julia < 1.9. This allows all the Requires stuff to be removed.
Adding support for CUDA 3 in the package extension seems difficult since the cuDNN package isn't compatible with  any CUDA version < 4. Possibly a second extension that only depends on CUDA could be implemented and there sort out the logic for handling different CUDA versions.
Adding support for CUDA 4+ in the Requires approach doesn't seem impossible but on the other hand nothing much has happened in #27 over time. It should be easier if CUDA 3 support is dropped at the same time.
Keeping support for Requires in Julia 1.9+ is not advisable since it doesn't play nicely at all with PrecompileTools.

I think we should just drop pre 1.9 julia support.

Done in second commit. I need to do some tests on my real use case and it needs README updates and a breaking version bump, either to 0.4 or 1.0. I would recommend taking the opportunity to jump to 1.0, regardless of package maturity, but that's your call.

Done in second commit. I need to do some tests on my real use case and it needs README updates and a breaking version bump, either to 0.4 or 1.0. I would recommend taking the opportunity to jump to 1.0, regardless of package maturity, but that's your call.

Thanks, 1.0 is a good idea!

From my point of view this is good to go. The CI failure on nightly is a CUDA.jl issue; it doesn't load in isolation either.
Oh, there's a docs directory as well. Clearly index.md needs some of the updates from README.md. Should some of the new material only go into one of the files?

In theory that should be automatic https://github.com/jw3126/ONNXRunTime.jl/blob/dfb67d6facae4a9b66054a68c63f0589ef171a05/docs/make.jl#L6
Of course feel free to do any other additions to the docs, but it is not required from my side.

Ok, then I'm happy with it as it is.

I tried to play with your brach locally. I setup an environment, with
]dev ONNXRunTime
]add CUDA cuDNN
import CUDA; CUDA.set_runtime_version("v11.8")
exit()

However when I do import CUDA I get
 Downloading artifact: CUDA_Runtime
    Downloading [==================================>      ]  82.6 %

And after that hits 99.1% it just starts again at 0% in an infinite loop. Any ideas?

And after that hits 99.1% it just starts again at 0% in an infinite loop. Any ideas?

It's nothing I've run into but I'm trying it out in a clean depot. If it's reproducible I'm sure the Pkg developers would love a bug report.

With CUDA runtime version v12.2 I don't get stuck in an infinte loop, but I get the following:

This is expected since you don't get v11 .so files with CUDA runtime v12, and ONNXRunTime tries to load v11.

And after that hits 99.1% it just starts again at 0% in an infinite loop. Any ideas?

Could it be a network or package server issue? Kind of sounds like the artifact transmission gets interrupted and something decides to start over. Might be worth trying to switch to another package server or disable it, to see if something changes. Or just try again and hope it was a transient problem.

With CUDA runtime version v12.2 I don't get stuck in an infinte loop, but I get the following:

This is expected since you don't get v11 .so files with CUDA runtime v12, and ONNXRunTime tries to load v11.

Ok, let's make this stricter. The latest commit gives an error outside the officially supported range of CUDA runtime versions. It also centralizes the version data and adds consistency checks within the package.

What’s the rush with 1.0?
What would be reasonable, achievable goals for a first not-supposed-to-need-breaking changes version?

Will restricting CUDA support to v11+ (via restrictions on CUDA.jl) rule out support for ONNXRuntime on Jetson Nano devices (that only support CUDA 10.2)?
It might be that Nvidia has released a newer version with Jetson Orin Nano (at 5x the price), but I think dropping support for a quite popular runtime platform from a quite popular runtime package sounds like a bad idea.

The main point of going to 1.0 is to get all three digits of semantic versioning and being able to distinguish between new features and bugfixes.
Does the current version work with Jetson Nano?

And after that hits 99.1% it just starts again at 0% in an infinite loop. Any ideas?

Could it be a network or package server issue? Kind of sounds like the artifact transmission gets interrupted and something decides to start over. Might be worth trying to switch to another package server or disable it, to see if something changes. Or just try again and hope it was a transient problem.

The issue disappeared, but now I get with CUDA_Runtime_jll v11.8:
  Got exception outside of a @test
  /onnxruntime_src/onnxruntime/core/session/provider_bridge_ort.cc:1131 onnxruntime::Provider& onnxr
untime::ProviderLibrary::Get() [ONNXRuntimeError] : 1 : FAIL : Failed to load library libonnxruntime
_providers_cuda.so with error: libcudnn.so.8: cannot open shared object file: No such file or direct
ory

If I try to import it directly, I get:
julia> import cuDNN
┌ Error: cuDNN is not available for your platform (x86_64-linux-gnu-libgfortran5-cxx11-libstdcxx30-c
uda+none-julia_version+1.9.3)

My best guess is that your artifacts are messed up. I've seen similar things at work occasionally and then it has turned out that there is some empty artifact directory, possibly a result of some Pkg operation being interrupted at a bad time. Just removing the empty directory has solved the problem since Pkg in that case automatically downloads the missing artifact. A more brutal approach is to just delete all of .julia/artifacts and reinstantiate everything.
A more sophisticated approach is to try to find the exact artifact where libcudnn.so.8 should be located. With Julia 1.9.3 on Linux, doing
pkg> activate --temp
pkg> add cuDNN
pkg> status
julia> using cuDNN
julia> cuDNN.libcudnn

I get
(jl_GNl34o) pkg> status
Status `/tmp/jl_GNl34o/Project.toml`
  [02a925ec] cuDNN v1.2.0

julia> using cuDNN

julia> cuDNN.libcudnn
"/home/gunnar/.julia/artifacts/46618accf53d4306ae450d749de3cb080111ac3b/lib/libcudnn.so"

@GunnarFarneback Thanks a lot, my artifacts are not fixed and this works for me locally.
@stemann I have no idea if the current version runs on Jetson Nano, I would guess you are the only person, who even dared to run it in that setup? Would this PR make life for you more harder? Are you opposed to parts of this PR, or only to the 1.0 tag? It would be super cool if someday we can use proper artifacts and don't depend on CUDA.jl anymore.
In my view tagging 1.0 does not mean we are opposed to supporting Jetson Nano or any other platform.
This package did not have breaking changes for a long time and I don't foresee any breaking changes after this PR (except bumping CUDA.jl version from time to time), so in my view 1.0 is appropriate.

The current version of ONNXRunTime.jl does not (I believe) run on the Jetson Nano, but ONNXRuntime does and the ONNXRuntime JLL should - that was a primary goal of JuliaPackaging/Yggdrasil#4386 (#12) and #19.
All that has been left (for ages, I agree!) is to implement, I believe, a similar approach as the CUDARuntime JLL - using e.g. Preferences.jl to select among the execution providers (and hence the artifacts) at Pkg.add-time. Please feel free to comment e.g. in #19 or #12.
I agree that compatibility with recent CUDA.jl versions should be an important goal for this package (I believe that is what this PR achieves…?).
But it would be nice if there was still room to get the Jetson Nano etc. support completed. Preferable without having to go for a 2.x version of this package, I would say.
So yes, I guess my main concern with this is bumping the version to 1.0.
P.S. Inspired by this PR, I raced to the office to get the old Jetson Nano fired up and ready for testing - hoping to find some time soon for pitching in…

The main point of this PR is to make the package play well with Julia 1.9+ precompilation and PrecompileTools, which is accomplished by replacing Requires with a package extension. Making it compatible with recent CUDA.jl is more of a bonus since it was easier to do that than to stay with the old version.
There's no harm done in going to major version 2, or more, if it turns out that further breaking changes are needed.

So yes, I guess my main concern with this is bumping the version to 1.0.
P.S. Inspired by this PR, I raced to the office to get the old Jetson Nano fired up and ready for testing - hoping to find some time soon for pitching in…

Cool! How about this? We merge this PR with v0.4 and release v1 December first. If you find the time to add artifacts support until then @stemann, that is awesome.
If not, also no big deal IMO to release a  v2 a later.

The no-later-than-December plan sounds great.

Have you considered using https://github.com/cjdoris/PackageExtensionCompat.jl ?

Have you considered using https://github.com/cjdoris/PackageExtensionCompat.jl to keep 1.6 compatibility?

CUDA v4 would be compatible with 1.6, CUDA v5 needs julia 1.8. Personally I would keep it simple and just drop 1.6 compat, but if anyone wants to add it using PackageExtensionCompat I am also fine with that.

I did some git commit rewriting to change the version bump to 0.4.

Have you considered using https://github.com/cjdoris/PackageExtensionCompat.jl to keep 1.6 compatibility?

It's not entirely that simple since it doesn't help with the Base.get_extension-based diagnostics.

Remember to register as well. I'd love to get back to a registered version instead of depending on this branch.


Feature: add Expo + React Native example repo

Hello Guys,
I've been using Nhost with NextJS for a while and a new upcoming project will be with React Native + Expo and I am currently doing my research how to set it up. Would I follow the basic React + Apollo example at this point? I think a dedicated example would be great for onboarding RN users.
Cheers & keep up the great work

We would be thankful if anyone from our community could help us with this.
cc @Svarto? :)

We would be thankful if anyone from our community could help us with this.
cc @Svarto? :)

Really swamped right now, will try over Christmas. If anyone has any questions, feel free to DM me on Discord. Username is same as here


Add mount for missing template path in docker container creation

This could be all of rtd.org checkout as well. Without this mount, sphinx will
not inject the context data into the output docs, and will pass without failure.

Addressed the prefix and rebased


Add test for PutWithTimestamp in tx.go

Adds TestTx_PutWithTimestamp in tx_test.go, refer to issues https://github.com/nutsdb/nutsdb/issues/238

@rayz tks your pr!


Changes required for ORDER_PAYMENT network message

This is wrt ob-go PR1654.

Reopened as #94 in local branch


Prevent useTranslations being triggered on prefetch

Is your feature request related to a problem? Please describe.
When hovering over a link on production that prefetches, useTranslation is triggered causing a rerender of the client component that it is in.
Describe the solution you'd like
Prevent useTranslation causing a rerender on prefetching of future link
Describe alternatives you've considered
Temporarily disabled prefetching

useTranslations doesn't have anything to do with prefetching, there might be a bug in your app code. If you think you've found a bug, then you're welcome to submit a bug report, but I'd assume the bug to be in the app code.


support cert-manager acme dns challenges

https://cert-manager.io/docs/configuration/acme/dns01/
https://cert-manager.io/docs/configuration/acme/dns01/route53/
This requires us to create CNames from the base Domain pointing to any subdomains. Cert managers can not directly target sub domains.


Add details of all the CoverageJSON bblocks

@avillar I neglected this over the last couple of months, so may need to resolve difference with all the changes you have added.

@chris-little @avillar I have merged the PR into the legacy branch


Use setPlainText when finishing a completion

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable

Description
Without it, you could "execute html" for yourself in the input box, which had no use
https://i.nuuls.com/sxpyU.png

Looks good to me!


automatically folds after deleting newlines between folds

Neovim version (nvim -v | head -n1)
NVIM v0.9.0-dev
Operating system/version
linux mint 21
How to reproduce the issue
create text file with multiple levels of folds:
test
    row
        sub
        sub
    row
        sub
        sub

fold to hide sub, but show row  (set foldlevel=1, I think)
insert or delete a blank newline between the two row folds.  Both inserting and deleting cause it.
editor will now automatically (and undesirably) fold all the way, and hide rows
Expected behavior
fold level should not change because of modification of text
Actual behavior
The text you're editing gets folded because you edited the text.  Especially troublesome if it folds, then you end up deleting N folded lines instead of the single unfolded line you meant to.

Using a provider of ufo, must set a large value for foldlevel, this is the limitation of foldmethod=manual. A small value may close fold automatically if the fold ranges updated.

https://github.com/kevinhwang91/nvim-ufo/issues/7
https://github.com/kevinhwang91/nvim-ufo/issues/57
https://github.com/kevinhwang91/nvim-ufo/issues/89

I do have a large foldlevel in my config, as the instructions say.
vim.o.foldcolumn = '0' -- '0' is not bad
vim.o.foldlevel = 99 -- Using ufo provider need a large value, feel free to decrease the value
vim.o.foldlevelstart = 99
vim.o.foldenable = true

However, I change the foldlevel when editing text with zM, zr, etc.
Do you mean, this kind of use is not compatible with nvim-ufo?

Ah, I see.  Sorry about that.
Is the config here supposed to restore normal functionality to zm, zM, zr, and zR?  https://github.com/kevinhwang91/nvim-ufo#customize-configuration
I copied it directly, and zm and zr seem to have the same behavior as zM and zR.

number + zm.
zr is the same as zM if the kind is excluded in close_fold_kinds.

Is there a way to just increment/deincrement mock-indent-level, to simulate standard behavior?

No, foldlevel should keep a large value. Must maintain your_foldlevel by yourself. Need to write a script.
vim.api.nvim_create_autocmd({'WinNew', 'VimEnter'}, {
    pattern = '*',
    callback = function()
        vim.w.my_foldlevel = 20
    end
})

vim.keymap.set('n', 'zr', function()
    vim.w.my_foldlevel = vim.w.my_foldlevel - 1
    require('ufo').closeFoldsWith(vim.w.my_foldlevel)
end)

vim.keymap.set('n', 'zm', function()
    vim.w.my_foldlevel = vim.w.my_foldlevel + 1
    require('ufo').closeFoldsWith(vim.w.my_foldlevel)
end)

This seems to be working well.  Need to figure out how to hold it to min of zero (never programmed Lua).  Might also like it to use current cursor position's indent level, if it's not too hard (ie: vim.w.my_foldlevel = max(vim.w.my_foldlevel, cursor_foldlevel).
Thanks for the help!
vim.api.nvim_create_autocmd({'WinNew', 'VimEnter'}, {
    pattern = '*',
    callback = function()
        vim.w.my_foldlevel = 1
    end
})

vim.keymap.set('n', 'zM', function()
    vim.w.my_foldlevel = 0
    require('ufo').closeFoldsWith(vim.w.my_foldlevel)
end)

vim.keymap.set('n', 'zR', function()
    vim.w.my_foldlevel = 5
    require('ufo').closeFoldsWith(vim.w.my_foldlevel)
end)

vim.keymap.set('n', 'zr', function()
    vim.w.my_foldlevel = vim.w.my_foldlevel + 1
    require('ufo').closeFoldsWith(vim.w.my_foldlevel)
end)

vim.keymap.set('n', 'zm', function()
    vim.w.my_foldlevel = vim.w.my_foldlevel - 1

    require('ufo').closeFoldsWith(vim.w.my_foldlevel)
end)


404 Not Found for the french user group

Description
Current link to change (404 not found) : http://osgeo.asso.fr/content/project/qgis-user-fr/
Good link (@DelazJ for validation) : https://www.osgeo.asso.fr/
(I tested all the others, they works (sometimes with security issues but works)
Page URL : https://qgis.org/en/site/forusers/usergroups.html
Impacted file : https://github.com/qgis/QGIS-Website/blob/master/source/site/forusers/usergroups.rst

Thanks @jef-n


Conditionally IMemRecv pushed back too far after Stage merging

The following generates the wrong code at the moment:
split {
    case(a): {
       wdata <- mem[addr];
    ...
    default: {
     wdata <- 3;
     }
---
    x = (a) ? wdata : wdata + 1;

The computation for x uses the default wdata value instead of the one from the memory read, becuase the IMemRecv() command is ordered after the computation of x in the stage command list. This should not be generated in this order.
This is likely a result of stage merging as well -> when the IMemRecv is merged into the stage assigning to x, it should be at the beginning of the command list.

Attached is an example PDL circuit that will cause this exact issue:
lateRecv.txt
In the following snippet from the output of the PDL compiler (generated BSV code):
    Int#(32) _Stage__4_wdata = fifo_Start_TO_Stage__4.first.wdata;
    ...
    Int#(32) _Stage__4_x = ?;
    _Stage__4_x = ( ( _Stage__4_cond == 2'd0 ) ? _Stage__4_wdata : ( _Stage__4_wdata + 32'd1 ) );
    if ( ( _Stage__4___condStage__3 == 1'd0 ))
    begin
        _Stage__4_wdata = mem.peekResp(_Stage__4__request_0);
    end

x ignores the result coming back from memory (i.e., mem.peekResp(...)).
The compiler should generate all code that writes to a variable, before it is used in that stage.
The fixed version would simply have the conditional assignment to wdata be moved earlier:

    Int#(32) _Stage__4_wdata = fifo_Start_TO_Stage__4.first.wdata;
    if ( ( _Stage__4___condStage__3 == 1'd0 ))
    begin
        _Stage__4_wdata = mem.peekResp(_Stage__4__request_0);
    end
    ...
    Int#(32) _Stage__4_x = ?;
    _Stage__4_x = ( ( _Stage__4_cond == 2'd0 ) ? _Stage__4_wdata : ( _Stage__4_wdata + 32'd1 ) );

Resolved by #50


CLI mode HOW TO documentation

In the file dps-model.h you mention:
you can see real ADC value in CLI mode's stat:
Is the documentation on how to use it available anywhere specifically for this firmware?

@kanflo I am happy to tune the parameters for the DPS8005 and send in a PR once I know how to do the above...

I assume this is referring to the dpsctrl -cr command

The line I'm referring to is this one: https://github.com/kanflo/opendps/blob/c1a8ab69d97ee3a329a2283ec88c49150537978c/opendps/dps-model.h#L18
Does the command you shared show the raw ADC values?

Yes, the calibration screen does. I'm away at the moment but I believe you press both the up and down arrow at the same time to get there (it's intentionally awkward)

Oh that was easier than I thought! Is there any documentation for this?

Weeeell, the documentation has somewhat fallen behind. Some of the information from my old blog posts are stil valid and some is obsolete. Recompiling them into a GitHub.io page has been on the todo list for quite some time. As always, contributions are welcome ;)

Can you share how you execute the following?
over openocd console:  mww 0x40007408 77
Do we need the FTDI connected for this?
Or just open an openocd console in one window and in another terminal type the above command?
Does the DPS need to be in any particular state for this to work?

It seems you found the correct way to execute the openpcd commands. It is strange you don't see any difference when changing 0x40007408. Can you try changing output value in the UI and see what happens to that, and other registers?