Update nanosplus to FW 1.0.3 support

I copied the latest files from upstream at this commit, and added DEFINES    += HAVE_CHACHA
Fixes #36
commit cb599834c7b527e264711ef71189229789018ec1
Author: Clement Bouvet<EMAIL_ADDRESS>Date:   Wed Aug 10 17:46:31 2022 +0200

    fix pending review screen not displaying

I noticed that this unfortunately breaks the compatibility with speculos

Thanks !


does not start at boot on CentOS 6

On CentOS 6, this cookbook registers consul as an upstart job. The consul process is started when Chef runs. I can also manually start and stop consul using something like sudo start consul. But after rebooting, consul is not automatically started. I can start it manually again, and everything is fine, but that's probably not the idea.
The configuration in /etc/init/consul.conf seems to indicate that it should automatically start at system start.  But the upstart version CentOS 6 is so old, it's hard to debug anything.
Here is a small Vagrantfile to test this:
Vagrant.configure('2') do |config|
  config.vm.box = 'chef/centos-6.6'
  config.vm.provision 'chef_solo' do |chef|
    chef.add_recipe 'consul-cluster'
    chef.json = {
      'consul' => {
        'config' => {
          'enable_syslog' => true
        }
      },
      'consul-cluster' => {
        'config' => {
          'bootstrap_expect' => 1
        }
      },
    }
  end
end

After vagrant up, check that consul is running, then run vagrant reload, and it won't come back up.

What's the minor version of CentOS 6 that you're using?

6.6, as in the Vagrantfile shown above.

I was able to confirm that Consul isn't starting on reboot.

@petere FYI: it could be worked around by switching service provider to sysvinit (instead of upstart):
node.set['poise-service']['consul']['provider'] = 'sysvinit'

Or the same with poise_service_options resource:
poise_service_options node['consul']['service_name'] do
  _options['provider'] = 'sysvinit'
end

That was what I was going to suggest as well. I'm not comfortable using the version of upstart on CentOS 6 because it is ancient. I'll try and take some time to mess around with this, but this is probably the best route.

I had tried that as well, but it doesn't work. The first problem is that the generated init script does not pass the path (/usr/local/bin) for consul, so it doesn't start. And if you fix that (manually), consul starts, but the init script fails because it checks for the PID of /usr/bin/env. And you don't get any error messages about either of these. It become clear very quickly that that scenario is not tested very well in poise-service. You can easily reproduce this by adding the appropriate attributes to the default test in .kitchen.yml.

Alright, we can fix this by putting a custom sysvinit template into the project.

I saw this too, and managed to figure out what's going on. It's failing because with the upstart config on EL6, Consul is being started before the network is up, and then Consul itself bails out because, again, the network is not up. I would be nice if Consul was a little more patient in this scenario, but there's probably a way to build some patience in to the upstart config, or give it an explicit dependency on networking. Note that networking on EL6 is managed by a sysvinit script.

@griffint61 That's interesting. I have a new sysvinit template that I wrote for the project, but if I configure the service to start on run levels 3 and 5 it should be fine?


Fix MySql _fromTables()

When there are JOINs and more than one table exists, the FROM clause must be enclosed in parentheses, otherwise an error occurs if a JOIN does not refer to the last table.
Checklist:

[X] Securely signed commits
[X] Component(s) with PHPdocs
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[X] Conforms to style guide

I checked the codebase and this was indeed merged this time :)


Made AbsrtactIterator package-private

Fixes #1729

Codecov Report

Merging #1985 into master will decrease coverage by 0.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #1985      +/-   ##
============================================
- Coverage     97.78%   97.77%   -0.02%
+ Complexity     5167     5166       -1
============================================
  Files            91       91
  Lines         11797    11797
  Branches       1565     1565
============================================
- Hits          11536    11534       -2
- Misses          115      116       +1
- Partials        146      147       +1

Impacted Files
Coverage Δ
Complexity Δ

...main/java/io/vavr/collection/AbstractIterator.java
80% <100%> (ø)
4 <1> (ø)
:arrow_down:

...r/src/main/java/io/vavr/concurrent/FutureImpl.java
82.5% <0%> (-2.5%)
21% <0%> (-1%)

Continue to review full report at Codecov.

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


Add GitHub Gist extension

Description
Getting Started
This extension brings GitHub Gist support to Raycast through the personal access tokens. To get started, first:

Login to your  GitHub instance (Eg. https://github.com/)
Click on your avatar image in the right upper corner
From the dropdown menu, click on Settings
On the left-hand side, click on Developer settings.
On the left-hand side, click on Personal access tokens.
On this page, we'll create a new access token. Click on Generate new token in the upper-right.
Leave a note for your token (Eg. Raycast). This will help you identify it in the future.
You'll need to check the following boxes to ensure this extension can perform properly:

repo
gist
user

Click Generate token and save this value somewhere. You'll only be able to see this once.

Future updates to this extension will offer more functionality that may require additional scopes be defined in this token.

Create Gist
Automatically get the selected text or clipboard and generate a gistfile, you can also add additional gistfiles and finally create a gist.
Once created successfully, you can choose to copy the link or open it in your browser.
Search Gist
Search and display gists from GitHub.

Gist Tag

My Gists

My Starred

All Public Gists

Action

Copy to Clipboard

Paste to Active App

Copy Gist Link

Open in Browser

Star Gist (Only in MyGists)

Delete Gist (Only in MyGists)

Unstar Gist (Only in My Starred)

Star Gist (Only in All Public Gists)

Clone Gist

Screencast
https://user-images.githubusercontent.com/36128970/159161962-70adae29-29c5-4026-82d0-19f23b8dcc22.mp4
https://user-images.githubusercontent.com/36128970/159211152-65b06683-56a3-4db4-842f-3acb05c6ce62.mp4
Checklist

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

Great work! I feel like it would be nice to have a loading state when switching between My/Starred/All Gists.
As a feature suggestion, would it be worth adding the ability to create a Gist from whatever is copied from your clipboard? This would create a Gist from whatever is in your clipboard, and return the URL to said Gist to your clipboard.

hi @andreaselia, Thank you for the review.
Changes in this commit :

Add Loading state for time-consuming network operations to improve user experience,
Add the command to create gist,
Please continue to review.

@koinzhang Cheers, just fixed some typos...


Allow tasks to be clickable behind legend

Apologies if this is contributed incorrectly and/or contentious at all!
Our concourse installation has tasks to be laid out such that the legend sits over the tasks. Since this is a block element at the top, the tasks underneath it cannot be clicked on even if they are in progress.

Since the legend does not contain any links or clickable 'calls to action' we can use pointer-events as a quick fix to propagate the click events to the elements below (this works on all browsers except IE10 and below, which will act as before so there's no regression there.)

@SwamWithTurtles Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@SwamWithTurtles Thank you for signing the Contributor License Agreement!

@jama-pivotal Seems simple - should we just merge this in?

@SwamWithTurtles we made a manual commit (https://github.com/concourse/web/commit/698b46a2794e7a602d287c5c304fdcd793ef7521) because the web is now in a separate repo.
Thanks for the PR!


Remove cache requirement.

This has been included in pytest since 2.8.0.

Thanks!
Since you already wrote when it was added, could you please update the pytest requirement accordingly.
A changelog entry would also be nice.

A changelog entry would also be nice.

This is the changes in README? If so what should the version be?  A new release may contain other commits?


Touch support WIP

Hello, as I need touch support in an application I'm developing with druid, I'm opening this draft with the changes I made to hack a very early  touch support.
The code is not ready for review or inclusion, but it can be a first base for discussion or experimentation. Please feel free to chime in if you are interested in this.
Current code limitations:

Only linux (gtk) support. I may try to write to windows backend in the future, but I don't own a mac.
Touch events (TouchBegin/TouchUpdate/TouchEnd) are propagated by WidgetPod's. Inside WidgetPod, an instance of TouchProcessor is created that tries to convert touch events to standard mouse events. A mechanism to permit widgets to by-pass the processor is needed, I'm trying to think of something.
Limitation: touch events conversion is only done inside WidgetPod's, so some lightweight widgets won't have it. This is why I slightly modified the scroll example.
Current logic for converting events is hacky to say the least. Mouse click and on finger scroll (pan) are supported.
I still don't know what the best way is to push synthesized events back into the event loop.

Every platform has gesture recognition utilities (e.g. gtk's GtkGesture), but I think having druid implement its own platform-independent logic would be a plus?

I'll postpone working on this due to uni for a couple of weeks, but after some discussion on zulip we figured that a better strategy could be to  put the processor at the top of the event chain and mark synthetic events as such, so that widgets can discard them. Doing the processing at every WidgetPod node is not going to work.


Further Spawner Tweaks

A number of tweaks relating to mob spawners have been added already. This includes a recipe that allows you to craft spawners that drop themselves when broken and the ability to disable spawners by powering them with Redstone.
A future change to be introduced is the ability to improve spawners by increasing the amount of mobs spawned at a time and reducing the maximum time between spawn attempts. An elegant in-game mechanic for this needs to be developed, as well as a way to visualize the current spawner's stats - but only if it's one placed by the Player.

This is resolved using the spawner mod that has been added to the modpack.


[Release] Version 0.5.1

Description
Missing documentation from optional support changes
Review checklist

[x] PR is split into meaningful commits for the ease of reviewing
[x] Description contains clear instructions on how to test the feature (where applicable)
[x] Tests have been written
[x] Appropriate labels have been applied

Codecov Report

Merging #76 (6ab129a) into main (06ed619) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 6ab129a differs from pull request most recent head 335df8c. Consider uploading reports for the commit 335df8c to get more accurate results

@@           Coverage Diff           @@
##              main     #76   +/-   ##
=======================================
  Coverage     92.4%   92.4%
  Complexity      52      52
=======================================
  Files           15      15
  Lines          106     106
  Branches        18      18
=======================================
  Hits            98      98
  Misses           4       4
  Partials         4       4


Release 0.10.0

@matprec It looks like this wasn't actually published?

It's published it now. Sorry for the inconvenience, i haven't been paying attention the last time, so there might have been an error i didn't catch.


Fix JAX export support of TFDataLayer.

During export, the tf.function wrapping the jax2tf function is traced. In this scenario, we're in a JAX tracing scope within a Tensorflow graph. TFDataLayer now detects this correctly.
Also improved jax_utils.is_in_jax_tracing_scope(): there are multiple tracer array classes that all extend jax._src.core.Tracer.

Codecov Report
Attention: Patch coverage is 50.00000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 57.20%. Comparing base (4f3fa0e) to head (27491f9).

Files
Patch %
Lines

keras/src/utils/jax_utils.py
0.00%
3 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (4f3fa0e) and HEAD (27491f9). Click for more details.
HEAD has 3 uploads less than BASE
| Flag | BASE (4f3fa0e) | HEAD (27491f9) |
|------|------|------|
|keras|4|1|

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #19902       +/-   ##
===========================================
- Coverage   78.99%   57.20%   -21.79%
===========================================
  Files         499      499
  Lines       46396    46399        +3
  Branches     8548     8549        +1
===========================================
- Hits        36650    26543    -10107
- Misses       8019    18207    +10188
+ Partials     1727     1649       -78

Flag
Coverage Δ

keras
57.20% <50.00%> (-21.65%)
:arrow_down:

keras-jax
?

keras-numpy
57.20% <50.00%> (+<0.01%)
:arrow_up:

keras-tensorflow
?

keras-torch
?

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

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


Make using RLMException a little less awkward to use

Remove the error-specific userInfo from all exceptions (there were only a few left) and move the relevant information to the exception message, since it's quite clear that no one actually looks at the userInfo.
Make RLMException take varargs and perform string formatting since nearly every usage of it was of the form RLMException([NSString stringWithFormat:...]) (or something equivalent split over more lines), which was needlessly verbose.

:+1:

Nice :+1:


Use the correct .write proxies while swapping audio effect buffers.

edit: before anyone gets their hopes up too much, this breaks effects completely. 1am me didn't realize that at first so I jumped the gun on making the PR. But I think this might be close to where the actual problem is. Will continue working at a more reasonable time.
Fixes #38372
This was a fun one to track down. It seems like it was introduced in https://github.com/godotengine/godot/commit/0e29f7974b59e4440cf02e1388fb9d8ab2b5c5fd and wasn't caught by the compiler presumably because of the semantics of the SWAP operation? I don't fully understand what's going on here so hopefully somebody with a bit of knowledge on the COW stuff and the audio server can review. What I do know is that buffers seem to get shuffled around in ways that are extremely difficult to predict without this patch.
Testing can be done with the minimal repro project in #38372
Since I'm in the audio server making this change, let me know if there's something that would make more sense than SWAP here, or if everything should be fine now that it's just using the write proxies.

Sorry for the false alarm. Second time today I've had to close a PR because it wasn't the right approach. :(


i2c_driver_delete(i2c_port_t i2c_num) crashes IDF 5.0.1 but works on IDF 5.0 (IDFGH-10066)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
IDF version: v5.0.1
Operating System used.
Windows
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
CMD
Development Kit.
Custom Board
Power Supply used.
USB
What is the expected behavior?
I expected i2c_driver_delete(i2c_port_t i2c_num) to free the used resources (GPIO, buffers etc).
What is the actual behavior?
Instead it just crashed my application.
Steps to reproduce.
Start a blank project or modify an existing one.

Use i2c_param_config(i2c_port_t i2c_num, const i2c_config_t *i2c_conf) to configure i2c port...
Use i2c_driver_install(i2c_port_t i2c_num, i2c_mode_t mode, size_t slv_rx_buf_len, size_t slv_tx_buf_len, int intr_alloc_flags) to install the i2c port...
Lastly, use  i2c_driver_delete(i2c_port_t i2c_num) uninstall the current i2c port and free the resources used...

It will crash on step 3...
Debug Logs.
Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.

Core  0 register dump:
PC      : 0x40376c14  PS      : 0x00060033  A0      : 0x82005614  A1      : 0x3fcf0e30
0x40376c14: esp_intr_disable at C:/Users/pgdur/esp/esp-idf/components/esp_hw_support/intr_alloc.c:824

A2      : 0x3fcec4bc  A3      : 0x3fca1d1c  A4      : 0x00060020  A5      : 0x00060023
A6      : 0x00060023  A7      : 0x0000cdcd  A8      : 0x00060620  A9      : 0x3fcf0e00
A10     : 0x00000001  A11     : 0x3fca1d24  A12     : 0x00000000  A13     : 0x00060023
A14     : 0x000000fd  A15     : 0x0000cdcd  SAR     : 0x00000004  EXCCAUSE: 0x0000001c
EXCVADDR: 0x00060620  LBEG    : 0x00000000  LEND    : 0x00000000  LCOUNT  : 0x00000000

Backtrace: 0x40376c11:0x3fcf0e30 0x42005611:0x3fcf0e50 0x420056f1:0x3fcf0e70 0x4037eaac:0x3fcf0e90 0x40386f79:0x3fcf0eb0
0x40376c11: esp_intr_disable at C:/Users/pgdur/esp/esp-idf/components/esp_hw_support/intr_alloc.c:823

0x42005611: esp_intr_free at C:/Users/pgdur/esp/esp-idf/components/esp_hw_support/intr_alloc.c:710

0x420056f1: esp_intr_free_cb at C:/Users/pgdur/esp/esp-idf/components/esp_hw_support/intr_alloc.c:690

0x4037eaac: ipc_task at C:/Users/pgdur/esp/esp-idf/components/esp_system/esp_ipc.c:87

0x40386f79: vPortTaskWrapper at C:/Users/pgdur/esp/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:154

More Information.
This was not a problem in IDF 5.0 official release. If I revert back to 5.0, the problem is gone.

Can you share your code of this part directly?

 I can't reproduce the same issue locally.
in i2c_sample example, my code is like
void app_main(void)
{
    uint8_t data[2];
    ESP_ERROR_CHECK(i2c_master_init());
    ESP_LOGI(TAG, "I2C initialized successfully");

    // /* Read the MPU9250 WHO_AM_I register, on power up the register should have the value 0x71 */
    // ESP_ERROR_CHECK(mpu9250_register_read(MPU9250_WHO_AM_I_REG_ADDR, data, 1));
    // ESP_LOGI(TAG, "WHO_AM_I = %X", data[0]);

    // /* Demonstrate writing by reseting the MPU9250 */
    // ESP_ERROR_CHECK(mpu9250_register_write_byte(MPU9250_PWR_MGMT_1_REG_ADDR, 1 << MPU9250_RESET_BIT));

    ESP_ERROR_CHECK(i2c_driver_delete(I2C_MASTER_NUM));
    ESP_LOGI(TAG, "I2C de-initialized successfully");
}

@d18-builder Do you still hit the issue with latest v5.0.4?

I am currently using ESP-IDF v5.1.2
https://esp32.com/viewtopic.php?f=10&p=123464#p123464and this issue is no
longer present in this version.
B.R.
On Thu, Dec 7, 2023 at 9:59 AM Axel Lin @.***> wrote:

@d18-builder https://github.com/d18-builder Do you still hit the issue
with latest v5.0.4?
—
Reply to this email directly, view it on GitHub
https://github.com/espressif/esp-idf/issues/11341#issuecomment-1844052994,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOQQQKKDSC4QKGCLRLWGKYDYIEPGPAVCNFSM6AAAAAAXXKE5QWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBUGA2TEOJZGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@d18-builder
Could you verify if it works with v5.0.5? (If yes, you can close this issue)


Please describe differences to MichaelTJones/walk

MichaelTJones/walk seems to be an older implemention with the same purpose as cwalk. It would be nice to know what differentiates both libraries.
I have tried both and found actually no differences in my use case:

both take the same amount of time (and are much faster than the builtin filepath.Walk()).
both do not prepend the path of the found files with the search path (as opposed to the behaviour of the builtin filepath.Walk()) (see also #3)
both to not sort the output (as opposed to the behaviour of the builtin filepath.Walk()).

For the records: I also tried godirwalk. But even though the README of godirwalk indicates it would be faster than its competitors and other comparisons  come to the same conclusion, I found that it is way slower than both, cwalk and MichaelTJones/walk, in my use case (even though still faster than the builtin filepath.Walk()).
Interestingly it didn't even make a difference whether the output is sorted or not.

Idk, MichaelTJones/walk seems to have a lot of code borrowed from stdlib, so it's hard to compare. Not sure why this was needed.
CWalk also returns all encountered errors (see #1) while the other library returns the first error encountered (according to their readme). Overall, I'd say you need to try both and see what works best for you.

I'll close this as resolved, but let me know if you have further questions.


VSCode doesn't Run/Debug python with pyenv's virtualenv

Type: Bug

Behaviour
Expected vs. Actual
Expected: Run
Actual: Doesn't Run
Steps to reproduce:

install pyenv
install python with pyenv (I tried 3.6.15 version)
choose ~/.pyenv/versions/3.6.15/bin/python as interpreter
make a simple python script, for example:

# main.py
print('hello')

make launch.json with this code (actually, it's standard template):

{
    "configurations": [
        {
            "name": "Python",
            "type": "python",
            "request": "launch",
            "program": "main.py",
            "console": "integratedTerminal",
            "justMyCode": true
        }
    ]
}

Press F5 and make sure it does nothing

I tried last version of vscode and python extension on last Fedora 36 and last Debian 11.5.0. Also tried vscode which was downloaded from official website and snap-version. Alos tried 1.71 version of vscode and August  version of python extension
P.S. If I choose standard /usr/bin/python3 then all works fine.

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.6.15
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Pyenv
Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

Experiment 'pythonaacf' is active
LSP Notebooks experiment is enabled
LSP Notebooks interactive window support is enabled
Python interpreter path: ~/.pyenv/versions/3.6.15/bin/python
DAP Server launched with command: /home/alex/.pyenv/versions/3.6.15/bin/python /home/alex/.vscode/extensions/ms-python.python-2022.16.1/pythonFiles/lib/python/debugpy/adapter
Starting Pylance language server.
DAP Server launched with command: /home/alex/.pyenv/versions/3.6.15/bin/python /home/alex/.vscode/extensions/ms-python.python-2022.16.1/pythonFiles/lib/python/debugpy/adapter

User Settings

languageServer: "Pylance"

Extension version: 2022.16.1
VS Code version: Code 1.72.2 (d045a5eda657f4d7b676dedbfa7aab8207f8a075, 2022-10-12T22:16:26.920Z)
OS version: Linux x64 6.0.5-200.fc36.x86_64 snap
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i5-11500 @ 2.70GHz (12 x 4200)

GPU Status
2d_canvas: unavailable_softwarecanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onopengl: disabled_offrasterization: disabled_softwareraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: unavailable_softwarewebgl2: unavailable_softwarewebgpu: disabled_off

Load (avg)
1, 1, 1

Memory (System)
31.12GB (23.63GB free)

Process Argv
--no-sandbox . --crash-reporter-id 01cd247f-40b4-4331-a522-34261ef2f886

Screen Reader
no

VM
0%

DESKTOP_SESSION
gnome

XDG_CURRENT_DESKTOP
GNOME

XDG_SESSION_DESKTOP
gnome

XDG_SESSION_TYPE
wayland

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
vscccc:30566498
pyindex848cf:30577861
nodejswelcome1:30587005
fc301958:30595537
2e4cg342:30596373

Oh... Python extension doesn't support debugging < 3.7? :sob:
I found same bug report https://github.com/microsoft/vscode-python/issues/19799
I try all other versions (3.7 ... 3.12) with/without pyenv - and it works fine.

Yes, sorry we gotta do a better job of highlighting it to the user: https://github.com/microsoft/vscode-python/issues/19988. https://github.com/microsoft/vscode-python/issues/19559 might be of interest to you.


Permission denied (publickey): npm i dashmate tries to pull dash-spv via ssh://git

installing dashmate via npm throws:
sudo npm i -g dashmate
npm ERR! code 128
npm ERR! An unknown git error occurred
npm ERR! command git --no-replace-objects ls-remote<EMAIL_ADDRESS>npm ERR<EMAIL_ADDRESS>Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.

proposed solution: use dash-spv package from NPM registry instead of git.

Issue fixed a while ago, we pulled dash-spv into platform monorepo


Add Run Code Server configuration

For SuperDevMode.

You are probably looking for the Super Development Mode configuration that is used to run the code server. https://github.com/johndevs/gradle-vaadin-plugin/wiki/Tasks-and-configuration-DSL#vaadinsuperdevmode

This configuration is automatically terminated and you can not access http://localhost:9876

Executing task 'vaadinSuperDevMode'...
Using Gradle Vaadin Plugin 1.1.6
:compileJava
:vaadinUpdateWidgetset
:processResources UP-TO-DATE
:classes
:vaadinClassPathJar UP-TO-DATE
:vaadinCompile UP-TO-DATE
:vaadinSuperDevMode
BUILD SUCCESSFUL
Total time: 2 mins 16.686 secs
17:09:36: Task execution finished 'vaadinSuperDevMode'.

Could you run the task with --info and post the output?


Update the Arithmetic and Boolean section of the reference documentation

Following up on #29, update the documentation to reflect current parenscript behaviour. Also, to ease the publishing of the documentation, in the settings tab of the repository under github-pages, selecting sources master branch/docs folder will publish the html files in docs in the link pointed to by the updated readme. A couple of questions.

Couldn't find find how to generate >>>, haven't dug into special-operators.lisp. Is there another way? The >>> doesn't appear to have a counter part in CL.
Should the bit-wise symbols be removed from the reserved keywords?

I can merge the pull requeest, but cannot change the repository settings. @vsedach will have to do so before this is merged if he likes the gh-pages idea.

@PuercoPop mind undoing the change to the README?  I've put the updated reference.html on the project page: https://common-lisp.net/project/parenscript/reference.html but cannot make the change to github pages as I lack admin rights on the github project.

@jasom Done


Get rid of 'other' section

Not sure if required for proper operation without gutting the code a bit; but at least can remove from HTML since it always seems to be empty

done


chore(storybook): re-enable for pull requests

This PR adds support for building stories on pull requests to kaoto-ui from any fork or branch, excluding Dependabot PRs.
Resolves #1100
Storybook no longer provides its own Babel configuration, so we have had to introduce it. This should not cause build issues as we are using Webpack and ts-loader for transpilation for the project.
Follow-up PR will include Storybook MSW add-on for mocking network requests.

E2E tests are being flaky again, particularly for Chrome and Edge :(


Launcher UI scale on steam deck

When I open the launcher on steam deck (KDE, 1280×800 resolution), it is far too large to use. Is there a way to change the UI scaling of the launcher?

There is a setting for this, but you may not be able to get to it with this scale. Try editing the settings file catapult_settings.json in the launcher directory, for example:
    "ui_scale_override": 0.75,
    "ui_scale_override_enabled": true,

However, chances are the game will not run on Steam Deck anyway, see #96.

mearly enabling ui scale override solves the issue, though it still seems odd that its default behavior is too render at ~1000% scale or more on archlinux with kde plasma.


Implement mkdocs key from v2 config

This is on top of https://github.com/rtfd/readthedocs.org/pull/4482, it should be merged after.
New changes are from 3f311ef
Ref https://github.com/rtfd/readthedocs.org/issues/4219

I will wait until the base PR gets merged to review this.

Base PR is merged, care to rebase this?

I'm rebasing this now

I had to use an empty commit, travis wasn't being executed, even forcing the push :/

I'll be testing this with a couple of mkdocs projects and see how it goes

Search tests are failing, but before fixing them, I'd like to resolve https://github.com/rtfd/readthedocs.org/pull/4486#pullrequestreview-154052230

We can use https://docs.djangoproject.com/en/1.9/ref/contrib/postgres/fields/#jsonfield to store metadata on the build/version object.

We can't use the readthedocs-env.json file, because it is saved on the builders (those are deleted frequently)

So, what I think:

use a json type on the build object (we can get this from version object, querying the latest build of that version).
Or we can just add a new field (documentation_type) to the Version model.

I prefer 1), as we can save all the metadata used to build the docs, and query that data (like show the exact configuration used to build the docs). One downside is that we need to figure out how to make it work on development with sqlite.

@agjohnson done!

@agjohnson done

Thanks for repeatedly taking my nitpick abuse! :slightly_smiling_face:
Looks good!

I miss something here. I understood that you said that we were returning documentation_type in the API response. What are we returning now? If I'm reading correctly, we didn't remove that field from our DB and we are returning it as usual, but just added a validation on the config file that fails when the doctype from the YAML object differs from the one set in the admin. Am I right?

@humitos yes, we keep the documentation_type here, we opened https://github.com/rtfd/readthedocs.org/issues/4638 to track the complete remove


add, sub, truediv ... for Node need to be fixed

The behaviour of these methods is very unintuitive and unsatisfactory:
node = tn.Node(np.array([1,2,3], dtype=np.float64),backend='tensorflow')
node + 10 #raises an error

while this works fine in tensorflow:
tensor = tf.convert_to_tensor(np.array([1,2,3], dtype=np.float64))
tensor + 10 #fine
tensor = tf.convert_to_tensor(np.array([1,2,3], dtype=np.float32))
tensor + 10 #fine

This is also related to the broken build (#753)

Is this issue solved? While using the terminal, I am getting an error as mentioned but when I run it using a separate python file in the same directory as network_components.py, it runs without issues.
Terminal
>>> import tensornetwork as tn
>>> import numpy as np
>>> node = tn.Node(np.array([1,2,3], dtype=np.float32),backend='tensorflow')
>>> node + 10  # Fails
>>> node + 10. # Passes

File
import numpy as np
from network_components import Node

node = Node(np.array([1,2,3], dtype=np.float64),backend='tensorflow')

new_node = node + 10
print(new_node.tensor) # Passes

new_node = node + 10.
print(new_node.tensor) # Passes

I didn't see any difference in the __add__ method of the the package I installed using pip and master.

Hi @manav28 thanks for submitting an issue!
This bug should be fixed, but it has not been released yet. I tried both codes above and they work.
I'm not sure as to why you don't see any differences in the latest release and the current master though.
Have you tried to fetch and pull the repo?

@mganahl False alarm. Something probably went wrong on my local and I got a fresh copy. Now I do see differences. Thanks for the response!

no problem, thanks again for submitting an issue!

If you use it I can push and new version soon.

@Thenerdstation No worries. I wanted to contribute on this one. I wanted to verify if it was solved and clarify my question. Thank you for the support.


add Vite-howto to documentation

Added example for how to get Vite and Quinoa to work together.

Just to give som context, I have had some issues with the changes in Quinoa version 1.6, where the headers are now forwarded in QuinoaDevProxyHandler. When vite attempts to create a websocket-connection to localhost:8080 it generates the error: Invalid object PooledUnsafeDirectByteBuf(freed), it may still work, but som time Quinoa crashes. The changes in vite.config make Vite use the vite-dev-server so thats why HMR works.
The error is reproduced here: https://github.com/fasuke85/quinoa-vite/tree/error
I did som debugging in the Quinoa-plugin first, and adding headers.remove("Connection"); in QuinoaDevProxyHandler make the problem co away in this case.

Thanks @fasuke85 :)
It would be nice to have you as a code contributor on Quinoa, here are a few options:

https://github.com/quarkiverse/quarkus-quinoa/issues/198
https://github.com/quarkiverse/quarkus-quinoa/issues/174
https://github.com/quarkiverse/quarkus-quinoa/issues/175

@fasuke85 I am trying to get NextJS working and seeing some of the same issues you were with Vite including the Invalid object PooledUnsafeDirectByteBuf(freed)  .  also the HMR websocket connect is being denied for CORS headers.

@melloware as I told you, you should configure NextJS to not send websocket to the Quarkus port but directly to the nextjs server (like @fasuke85 did with Vite). Your problem is just in devmode right?

Next by default sends everything to port 3000 so that is not the issue. The websocket is getting rejected with CORS.  Let me try PRD mode.

Next by default sends everything to port 3000 so that is not the issue. The websocket is getting rejected with CORS. Let me try PRD mode.

The websocket is rejected because it is not handled at all by the Quarkus backend. This is what should be sent to 3000, NextJS should be configured to use 3000 for websocket.


Calixo888

What is the Purpose?
This addresses the failed date validation on program workflow level 2
Are there any concerns to addressed further before or after merging this PR?
None I believe
Issue(s) affected?
This affects #457

So sorry @andrewtpham !!  I will re-fix this and push my changes again, and ping you on Slack when I would like it reviewed.

@andrewtpham  Tried this locally and the issue in #457 looks fixed and working as expected.
@calixo888 Was this an issue of the date format? Also could you please address this similar bug (https://github.com/hikaya-io/activity/issues/457#issuecomment-613352138) while this is fresh in your mind?
The bug seems to originate from the format of the date, but now the input field assists the user in using the right format: DD/MM/YYYY

@TAnas0 Yeah, so this is for the edit program page here with extension: /workflow/level1
I just realized the date formats are off though. The edit page date format is different from the create program modal format, so I will take a look into that.

Hi @calixo888 is this PR still in draft? Do you need more time to address the comments in the PR?


Refresh JS build system

The changes here:

Upgrade to the latest major version of gulp.

Using gulp.task is no longer the preferred way of defining a task. Instead you simply define functions with various asynchronous completion mechanisms (returning streams, promises, etc) and export them from the module to register them with gulp.
Task dependencies as string arrays have been removed in favor of composing tasks with series and parallel.

Update gulp plugins

gulp-shell is discouraged by gulp because it encourages bad practices. It's fairly easy to replace it with calls to functions in Node's child_process module. I've wrapped those calls into a new shell function that tasks can use.
I removed several gulp plugins that were not being used anywhere.

Add Babel to JS compile pipeline. This uses @babel/preset-env  to enable a baseline set of the latest JS features, including ES modules. Additional Babel plugins and configuration can be done here as needed in the future.
Some light reformatting of the gulpfile to be more inline with standard JS styling.

Fixes #676

@pkalita-lbl Okay, testing locally with sjcarbon@moiraine:~/local/src/git/amigo[issue-676]$:) ./node_modules/.bin/gulp build
The sub-command cd ./javascript/npm/amigo2-instance-data && npm install gives me the error:
ERROR:
Pinged: https://s3-us-west-1.amazonaws.com/go-amigo-usage-master/ping.json
/home/sjcarbon/local/src/git/amigo/javascript/npm/amigo2-instance-data/node_modules/npm/lib/utils/exit-handler.js:22
  const hasLoadedNpm = npm?.config.loaded
                           ^

SyntaxError: Unexpected token .

I suspect that you need to do to that sub-package what you did for in the mail package. If you'd like, and you have tylenol/whiskey available, I can walk you through why this aberration exists in the first place.
It could also be that I'm messing something else up at my end. Let me know if there is something else I should be doing.

Hmm I don't see the same error while working in the amig-standalone container. It smells like some kind of version mismatch issue though. It's complaining about an optional chaining operator (?.). That was implemented in Node.js 14.0.0, and we're using Node.js 8.x (at least in the container). So for some reason your version of the npm package in amigo2-instance-data must be way ahead of where it should be. We should probably just meet to work through it instead of going back and forth in GItHub comments.

@pkalita-lbl After some cleaning locally, this worked for me in a non-docker environment, so I think this is good.
What do you think about updating the amigo-standalone image with newer code? I think we can punt on that until there is something "production-worth" to add, but it might help in your development?
Later on, we'll want to coordinate with @abessiari about getting this out to the production devops images.

What do you think about updating the amigo-standalone image with newer code? I think we can punt on that until there is something "production-worth" to add, but it might help in your development?

I don't think it matters too much one way or the other for the development workflow I'm using, but I'd be happy to nonetheless. Maybe that's something to take on once more of the actual AmiGO UI work is done?

Later on, we'll want to coordinate with @abessiari about getting this out to the production devops images.

Yeah, please loop me in. I'm curious how all that works.


Support http protocol versions besides 0.9, 1.0, 1.1, 2.0

This pull request was prompted by https://github.com/SpiderLabs/ModSecurity/issues/2380.
Until this change, any HTTP protocol version other than 0.9, 1.0, 1.1, and 2.0 would actually result in the ModSecurity-nginx connector passing a value of "1.0" to ModSecurity's msc_process_uri function.
With this change, any characters following the five-character 'HTTP/' protocol prefix will get passed to ModSecurity, as long as nginx has successfully populated ngx_http_request_t->http_protocol.

Are there any updates on this? What is blocking this pull request?
Would like to see this merged to get http3 working. There is already a dedicated nginx branch for quic support but it can not be used as long as http3 is not supported by the ModScurity-nginx module.
See https://hg.nginx.org/nginx-quic


Need a way to load a trained model (without retraining it).

In cases where training is slow. However, we can't use the pre-trained model if our pipeline is different (in some significant way) than the pipeline the model was trained inside of. We could just load the model without retraining and leave it up to the user whether or not to retrain -- maybe with a warning if it seems like the pipelines are different. This would require saving the whole pipeline and, on load, comparing it to the pipeline specified by the current example.

This probably depends on #150, as we'd want to load the calibration data, the tunable parameter values, the training data, and the pipeline / model together.

This was fixed as part of #150, etc.


Level 2 warning instead of kludge/STOP1 for negative ncore

          I probably need @jonmaddock to comment on this, as he is the one that wrote the kludge. For now, since this is a level 2 error, I will approve it but will make a follow-up issue to check that this fix is ok with the UQ tools (which is why the kludge was added)

Originally posted by @timothy-nunn in https://github.com/ukaea/PROCESS/pull/3060#discussion_r1495573238

We actually decided to go a different route so this can be solved in #3059


Migrate OpenAI & Anthropic plugins

This PR migrates the more up-to-date OpenAI & Anthropic plugins from my repo so that from now on we can maintain them in this repo instead.
Note: due to the regeneration of the lockfile, the PR also bumps the Cohere AI package to version 7.10.0, which includes some breaking changes to the types. For this reason, a fix on the types of the Cohere plugin is also included in this PR.

@all-contributors please add @Dabolus as a code contributor

Thanks for the great contribution @Dabolus! @all-contributors please add him as a docs and test contributor as well.


Adding support for vCloud Air OnDemand.

The API path is different between Subscription and OnDemand.  Specifically,
in Subscription it's '/api' while in OnDemand it's '/api/compute/api'.
The Fog gem supports a path override, but knife-vcair did not support
collecting and passing the path override.  This commit addresses that issue.
Addresses the issue reported in #28.

@adamleff - Thanks for getting this out so quick!  I pulled down your branch, built and installed knife-vcair, and it appears to be creating a VM in my ondemand org.  However, just after the creation task is initiated the Fog API errors and returns immediately.
stewartc-mbpro:knife-vcair stewartc$ knife vcair server create --ssh-password ChangeMe --image "CentOS64-64BIT" --node-name centos64 --vcair-net default-routed-network --vcair-show-progress true -VV
INFO: Using configuration from /Users/stewartc/.chef/knife.rb
DEBUG: vcair_username USERNAME
DEBUG: vcair_org MYORG
DEBUG: vcair_api_host MYAPIHOST
DEBUG: vcair_api_path /api/compute/api
DEBUG: vcair_api_version 5.7
DEBUG: vcair_show_progress
DEBUG: Using fog version: 1.31.0
/opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/fog-1.31.0/lib/fog/vcloud_director/compute.rb:436:in `wait_and_raise_unless_success': status: queued, error:  (Fog::Compute::VcloudDirector::TaskError)
	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/fog-1.31.0/lib/fog/vcloud_director/compute.rb:425:in `process_task'
	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/fog-1.31.0/lib/fog/vcloud_director/models/compute/catalog_item.rb:17:in `instantiate'
	from /Users/stewartc/.chefdk/gem/ruby/2.1.0/gems/knife-vcair-0.6.1/lib/chef/knife/vcair_server_create.rb:145:in `instantiate'
	from /Users/stewartc/.chefdk/gem/ruby/2.1.0/gems/knife-vcair-0.6.1/lib/chef/knife/vcair_server_create.rb:36:in `execute_command'
	from /Users/stewartc/.chefdk/gem/ruby/2.1.0/gems/knife-cloud-1.2.0/lib/chef/knife/cloud/command.rb:51:in `run'
	from /opt/chefdk/embedded/apps/chef/lib/chef/knife.rb:422:in `block in run_with_pretty_exceptions'
	from /opt/chefdk/embedded/apps/chef/lib/chef/local_mode.rb:39:in `with_server_connectivity'
	from /opt/chefdk/embedded/apps/chef/lib/chef/knife.rb:421:in `run_with_pretty_exceptions'
	from /opt/chefdk/embedded/apps/chef/lib/chef/knife.rb:214:in `run'
	from /opt/chefdk/embedded/apps/chef/lib/chef/application/knife.rb:142:in `run'
	from /opt/chefdk/embedded/apps/chef/bin/knife:25:in `<top (required)>'
	from /usr/bin/knife:51:in `load'
	from /usr/bin/knife:51:in `<main>'

I'm currently looking through the stacktrace to see if I can provide additional information or provide any contributions

Well, darn. I will take a deeper look at this tomorrow morning. I didn't encounter this in my testing but I may have missed something. If you find anything more specific, please let me know!

@cstewart87 - I've been able to determine the cause of the issue.  In vCloud Air OnDemand, all tasks appear to get created with an initial status of "queued."  In Fog, while waiting for a task to complete, it considers any task that is not in a state of "running" to be no longer running:
https://github.com/fog/fog/blob/master/lib/fog/vcloud_director/models/compute/task.rb#L46
Fog should really wait for tasks that are not in a state of "running" OR "queued." I submitted a PR up to the fog repo to address this:
https://github.com/fog/fog/pull/3653
You can feel free to pull down my fog branch and run with it and it should work for you now.  I've been able to create multiple vApps/VMs in OnDemand this morning with my patched fog.  I'll still get this knife-vcair change cut into a gem hopefully today after a code review as it's still necessary. :)

:+1: :cocktail: :coffee: :rocket: :guardsman: :guitar: :gun: :+1: :100:

:shaved_ice: :100:


SAK-45837: Not able to click on close dropdown in link tool url in some languages

I happened to test this before it was merged into 20.x branch and it wasn't an issue pre-merge. After merge it's also not an issue. Should it be retained in branch though?
Was in French so perhaps length of words didn't trigger issue?

I happened to test this before it was merged into 20.x branch and it wasn't an issue pre-merge. After merge it's also not an issue. Should it be retained in branch though?
Was in French so perhaps length of words didn't trigger issue?

That's correct, but in spanish text is longer, so you are able to see the problem there. In 21 and trunk close button is bigger, so in french some character is over the button.


Issue : Generate PDF Fail because some special char

Open https://github.com/asciidocfx/AsciidocFX/README.asc
PDF , Save As , not generated PDF File , it generate a temp docbook xml ,
then get error message: ERROR => Please fix Docbook validation error. LineNumber: 648, Column: 85
org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'emphasis'. One of '{"http://docbook.org/ns/docbook":inlinemediaobject, "http://docbook.org/ns/docbook":remark, "http://docbook.org/ns/docbook":superscript, "http://docbook.org/ns/docbook":subscript, "http://docbook.org/ns/docbook":xref, "http://docbook.org/ns/docbook":link, "http://docbook.org/ns/docbook":olink, "http://docbook.org/ns/docbook":anchor, "http://docbook.org/ns/docbook":biblioref, "http://docbook.org/ns/docbook":alt, "http://docbook.org/ns/docbook":annotation, "http://docbook.org/ns/docbook":indexterm, "http://docbook.org/ns/docbook":phrase, "http://docbook.org/ns/docbook":replaceable}' is expected.
the temp docbook xml at line 648 is: =>
    <entry align="left" valign="top"><simpara><keycombo><keycap><emphasis role="strong">tblx,y</emphasis></keycap><keycap>Tab</keycap></keycombo></simpara></entry>
I found the README.asc is
    |kbd:[*tblx,y* + Tab] |Generates asciidoc table (x=row,y=column)
It looks  special char is ,   make AsciidocFX  translate to docbook xml not validattion

Problems caused from **, please try updated readme in master.

@simplelife201008 Did you try that?


Update GitHub API example [question/documentation]

I have been trying to use the package for the GitHub API based on the example, but it haven't been able to. I will post the code I currently use to access the API in hope of understanding how it should be transformed to use the package.
HTTP way
using HTTP: post
using JSON3: JSON3
const github_endpoint = "https://api.github.com/graphql"
const github_user = # Your GitHub login
const github_token = "" # Your GitHub Personal Token
const github_header = ("User-Agent" => github_user,
                       "Authorization" => "bearer $github_token")
owner = "JuliaLang"
name = "Julia"
body = """
{
  rateLimit {
    cost
    remaining
    resetAt
  }
  repository(owner: \\"$owner\\", name: \\"$name\\") {
    id
  }
}
""" |>
    (x -> replace(x, "\n" => " ")) |>
    (x -> replace(x, r"\s+" => " ")) |>
    (query -> """{\"query\": \"query $query\" }""")
response = post(github_endpoint,
                github_header,
                body)
output = response.body |>
         String |>
         JSON3.read

Hi, thank you for your question. The answer to your request is this:
using Diana

client = GraphQLClient("https://api.github.com/graphql",auth="Bearer github_token",headers=Dict("User-Agent"=>"github_user"))

query = """
       query A{
         rateLimit {
             cost
             remaining
             resetAt
           }
          repository(owner:"JuliaLang", name: "Julia" ){
                id
             }
          }"""

r = client.Query(query,operationName="A")

if (r.Info.status == 200)
println(r.Data)
end
#"{\"data\":{\"rateLimit\":{\"cost\":1,\"remaining\":4998,\"resetAt\":\"2019-07-28T15:50:45Z\"},\"repository\":{\"id\":\"MDEwOlJlcG9zaXRvcnkxNjQ0MTk2\"}}}"

Thanks! Could I have a follow up in using Diana.jl by passing query variables in this case?
using Diana
const github_endpoint = "https://api.github.com/graphql"
const github_user = # Your GitHub login
const github_token = # Your GitHub Personal Token
const github_header = Dict("User-Agent" => github_user)
client = GraphQLClient(github_endpoint,
                       auth = "bearer $github_token",
                       headers = github_header)

query = """
        query(\$owner: String!, \$name: String!) {
          rateLimit {
            cost
            remaining
            resetAt
          }
          repository(owner: \$owner, name: \$name) {
            id
          }
        }"""

r = client.Query(query,
                 vars = Dict("owner" => "JuliaLang",
                             "name" => "Julia"))

I am not sure how using the operationName works when passing variables.

in that case you use
query = """
       query A (\$owner:String!, \$name:String!){
         rateLimit {
             cost
                 remaining
                     resetAt
                       }
                         repository(owner:\$owner , name: \$name ){
                             id
                               }
                               }"""

r = client.Query(query, vars = Dict("owner" => "JuliaLang","name" => "Julia"),operationName="A")

I put the operationname because github requires it, in my tests of not placing it I get
"{\"errors\":[{\"message\":\"No operation named \\\"\\\"\"}]}"

to the query he placed the names of A and then indicated that this is the query that I want to execute

Thanks!


Update guidance to include ValidateDataAnnotations

[Enter feedback here]
One of the sections in recommend not using the AddOptions method.  We use AddOptions to automatically validate settings with data annotations i.e.
                   .AddOptions<LibraryOptions>()
                        .BindConfiguration("LibraryOptions")
                        .Configure(c =>
                        {
                           //override some values here if desired
                        })
                        .ValidateDataAnnotations()
                        .ValidateOnStart();

This causes startup errors for misconfigured settings which is exactly what we want.  Appreciate this is one-time snapshot of that instance.  Going with the recomendation bypasses validation at the earliest moment and we'd have to validate within every consuming DI of those settings - potentially leading to delayed recognition of those issues.
Can the guidance be updated to account for library writers that want to use ValidateDataAnnotations?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 03494bb6-433a-5385-b664-7b830c37f9ce
Version Independent ID: d0e9398d-50c6-01b8-a242-4edc8b27df31
Content: Options pattern guidance for .NET library authors - .NET
Content Source: docs/core/extensions/options-library-authors.md
Product: dotnet-fundamentals
GitHub Login: @IEvangelist
Microsoft Alias: dapine

Associated WorkItem - 59283

Hi @MarkAtAgilliance,
Thank you for posting this issue, I'm adding some clarifying content and examples to this guide based on your feedback. One thing to note, is that this guidance doesn't say not to use AddOptions, but rather advises of potential concerns when using it with Bind. Specifically, that it would be read-once. I'll make that more clear and add the validation example, with a string parameter suggestion.


UI: pass the untransformed node size to the shader

Objective

#12500 broke rotating ui nodes, see examples pbr (missing "metallic" label) or overflow_debug (bottom right box is empty)

Solution

Pass the untransformed node size to the shader

Do we have an example/test for this? If not, do you mind adding one? This is the second time we've seen a UI rotation bug like this :(


WebGUI works but API not working

What happened?
system: Ubuntu 22.04  i7-13700KF/64gb-ram/4080ti
Web gui and Fast Track works as expected.
Running gradio_client against the run_htr_pipeline endpoint does not work.
Steps To Reproduce

Install requirements.txt
Start server with python3 app.py
Start webserver python3 -m http.server 8080
run client

Relevant log output
Client
python app.py
Loaded as API: http://<IP_ADDRESS>:7860/ ✔
StatusUpdate(code=<Status.FINISHED: 'FINISHED'>, rank=0, queue_size=None, eta=None, success=False, time=datetime.datetime(2023, 11, 12, 17, 54, 50, 432654), progress_data=None)
Traceback (most recent call last):
  File "/home/patrik/projects/htrflow_client/.venv/lib/python3.10/site-packages/gradio_client/client.py", line 836, in _predict
    output = result["data"]
KeyError: 'data'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/patrik/projects/htrflow_client/app.py", line 14, in <module>
    print(job.result())
  File "/home/patrik/projects/htrflow_client/.venv/lib/python3.10/site-packages/gradio_client/client.py", line 1131, in result
    return super().result(timeout=timeout)
  File "/usr/lib/python3.10/concurrent/futures/_base.py", line 451, in result
    return self.__get_result()
  File "/usr/lib/python3.10/concurrent/futures/_base.py", line 403, in __get_result
    raise self._exception
  File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/patrik/projects/htrflow_client/.venv/lib/python3.10/site-packages/gradio_client/client.py", line 798, in _inner
    predictions = _predict(*data)
  File "/home/patrik/projects/htrflow_client/.venv/lib/python3.10/site-packages/gradio_client/client.py", line 842, in _predict
    if "error" in result and "429" in result["error"] and is_public_space:
TypeError: argument of type 'NoneType' is not iterable

Server
Traceback (most recent call last):
  File "/home/patrik/projects/htrflow_app/venv/lib/python3.10/site-packages/gradio/routes.py", line 488, in run_predict
    output = await app.get_blocks().process_api(
  File "/home/patrik/projects/htrflow_app/venv/lib/python3.10/site-packages/gradio/blocks.py", line 1435, in process_api
    result = await self.call_function(
  File "/home/patrik/projects/htrflow_app/venv/lib/python3.10/site-packages/gradio/blocks.py", line 1107, in call_function
    prediction = await anyio.to_thread.run_sync(
  File "/home/patrik/projects/htrflow_app/venv/lib/python3.10/site-packages/anyio/to_thread.py", line 33, in run_sync
    return await get_asynclib().run_sync_in_worker_thread(
  File "/home/patrik/projects/htrflow_app/venv/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 877, in run_sync_in_worker_thread
    return await future
  File "/home/patrik/projects/htrflow_app/venv/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 807, in run
    result = context.run(func, *args)
  File "/home/patrik/projects/htrflow_app/venv/lib/python3.10/site-packages/gradio/utils.py", line 707, in wrapper
    response = f(*args, **kwargs)
  File "/home/patrik/projects/htrflow_app/src/htr_pipeline/gradio_backend.py", line 92, in segment_to_xml_api
    rendered_xml = self.pipeline.running_htr_pipeline(image)
  File "/home/patrik/projects/htrflow_app/src/htr_pipeline/utils/helper.py", line 15, in wrap_func
    result = func(*args, **kwargs)
TypeError: Pipeline.running_htr_pipeline() missing 1 required positional argument: 'htr_tool_transcriber_model_dropdown'

ba4de4ab538a654c932d4cd876d54850967d925e was the last commit when i got the API to work. but there was other issues with that commit. like the models were not downloaded properly.

Hi, I accepted your pull request 👍  and this some quick changes to make the api working now!
See this demo notebook here:
https://github.com/Swedish-National-Archives-AI-lab/htrflow_app/blob/main/notebooks/demo_api.ipynb
Currently their are only 3 models that are supported.

Swedish from 16th-18th =  "Riksarkivet/satrn_htr"
English text = "microsoft/trocr-base-handwritten"
Latin and High German = "pstroe/bullinger-general-model"

In the future we will also add PyLaila model support and also a new model Swedish model for historical texts (It will be much better).


Feature Request : Option to not replace selected text

Thank you so much for making this!  Working great right out of the box.
Like most people I know, I never want to fully hand over the reigns to ChatGPT, and would love the ability to to have it engage with selected text somehow and then produce results after the text, rather than replacing it. Best of all might be to wrap the generated text in a span that allows me accept/reject the results.  With this small change I think you could go a long way towards getting some of the best parts of https://www.notion.so/product/ai .

Hey @laffan, thank you for your comment.
The option not to replace selected text when using the prompt command is available in the settings: under Prompt behaviour, you can deactivate replace selection. The answer will be pasted directly in your note after the selection.


Reference to unsupported version of the Java SDK

This tutorial refers to an unsupported version of the SDK. This section https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-java-application#InstallSDK mentions azure-documentdb which is "The implementation in this project is intended for reference purpose only." (as per https://github.com/Azure/azure-documentdb-java#disclaimer)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2948cf4b-b078-cf73-611a-63cc09a5484a
Version Independent ID: 0a7c4de9-3e99-daa7-6580-d08b6499e78a
Content: Tutorial: Java application development tutorial using Azure Cosmos DB
Content Source: articles/cosmos-db/sql-api-java-application.md
Service: cosmos-db
Sub-service: cosmosdb-sql
GitHub Login: @tknandu
Microsoft Alias: ramkris

@abhirockzz We are checking this and will get back to you.

This issue is being assigned to the content author to evaluate and update the tutorial & documentation as appropriate.

@abhirockzz I recently refreshed this doc to use the Java V4 SDK (azure-cosmos). The above-referenced PR has all the updates. We will now close this issue.
#please-close


PrivateMessages.UnreadUpdated event is not being fired under certain conditions

I created a new project today with the first goal being to just monitor unread messages, but wasn't able to get it to work until I compared it directly to the RedditTests.ControllerTests.WorkflowTests.PrivateMessagesTests.Conversation test. The difference that I ended up finding is as below:
using Reddit;
using Reddit.Controllers;
using Reddit.Controllers.EventArgs;
using System;

namespace ConsoleApp1
{
    class Program
    {
        static void Main(string[] args)
        {
            var reddit = new RedditClient(/*credentials*/);

            FailingMonitorMessages(reddit);
            //SucceedingMonitorMessages(reddit.Account.Messages);
        }

        private static void FailingMonitorMessages(RedditClient reddit)
        {
            reddit.Account.Messages.MonitorUnread();
            reddit.Account.Messages.UnreadUpdated += C_UnreadMessagesUpdated;

            DateTime start = DateTime.Now;
            while (start.AddMilliseconds(60000) > DateTime.Now) { }

            reddit.Account.Messages.UnreadUpdated -= C_UnreadMessagesUpdated;
            reddit.Account.Messages.MonitorUnread();
        }

        private static void SucceedingMonitorMessages(PrivateMessages messages)
        {
            messages.MonitorUnread();
            messages.UnreadUpdated += C_UnreadMessagesUpdated;

            DateTime start = DateTime.Now;
            while (start.AddMilliseconds(60000) > DateTime.Now) { }

            messages.UnreadUpdated -= C_UnreadMessagesUpdated;
            messages.MonitorUnread();
        }

        private static void C_UnreadMessagesUpdated(object sender, MessagesUpdateEventArgs e)
        {
            Console.WriteLine("Message!");
        }
    }
}

There are two methods for monitoring messages. If you use an account with an unread message, and then run this application, the first method, which is uncommented, fails to fire the event handler when new unread messages are present. If you comment out the first method and use the second method instead, it works fine.
Notice that the difference between the two is only that with the successful method, we're passing in the reference to reddit.Account.Messages instead of just the reference to reddit. This was the difference between the test and my project (as well as the ELIZA sample code, which I couldn't get to work either).
I don't actually know why it works one way and not the other, maybe I'm overlooking or lacking some fundamental C# behaviour, or maybe it's a bug.

It also counts already read pms as unread on startup and modmails just permanently fires.

@GamingWolf If you happen to be still searching for a solution on this, see #117

@GamingWolf If you happen to be still searching for a solution on this, see #117

I just pushed a fix to #117.  Could you let me know if it also fixes your issue?  You can find it on the devleop branch.

Scratch that, it doesn't fix the issue.  The problem was a bug in the Account Controller.  The Messages property's get accessor wasn't actually storing the value when initialized, which apparently caused the event not to fire properly.  It's fixed now.  Nice catch!
Merged into 1.5.


Enable DMA driven PWM for all GIO pins except PWM1 pins.

@maruel
I am not sure if we should enable DMA depending on pins or introduce a flag to select DMA/hardware PWM/50%duty clock. What do you think?

Also, a test is broken. How can I fix it?
gpio_test.go:164: bcm283x-gpio (C1): videocore: failed to open the mailbox to the GPU: file I/O is inhibited

You need to mock the code in the tests to make sure that the test would pass even on Windows.

Codecov Report

Merging #195 into master will increase coverage by 0.73%.
The diff coverage is 27.41%.

@@            Coverage Diff             @@
##           master     #195      +/-   ##
==========================================
+ Coverage   84.11%   84.85%   +0.73%
==========================================
  Files          66       66
  Lines        5509     5500       -9
==========================================
+ Hits         4634     4667      +33
+ Misses        763      711      -52
- Partials      112      122      +10

Impacted Files
Coverage Δ

host/bcm283x/gpio.go
56.17% <27.11%> (+3.03%)
:arrow_up:

host/bcm283x/dma.go
66.04% <33.33%> (+10.4%)
:arrow_up:

devices/lepton/lepton.go
88.34% <0%> (-1.23%)
:arrow_down:

host/bcm283x/pwm.go
64% <0%> (+8%)
:arrow_up:

Continue to review full report at Codecov.

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


CTS TestSupportedEntitySharingPropertySearch assertion seems incomplete

Assertion 4 of this CTS test case looks for whether the results are null or not (and if they are null fails the assertion).  However, above this there is a calculation of the results that are expected (and are used as part of assertion 5); if the number of expected results is 0 then I believe it is perfectly valid for the results in assertion 4 to be null (?)
I'd suggest that the assertion for 4 is revised to something more like:
( (expectedEntityCount > 0 && result != null) || (expectedEntityCount == 0 && (result == null || result.isEmpty()) )

Yep - good spot - and I'm already on the case - been working on a refactored unified test case and that is one of the changes I've made.

The PR mentioned above is a fix to just the entity and relationship sharing testcases.
I aim to switch over to the refactored search tests soon but the PR should help until then.


pyosmium-up-to-date; NameError: name 'extra_headers' is not defined

(Also gave me a similar error using Python 2)
:~/osm_history_planet/pyosmium/tools$ python3 pyosmium-up-to-date -v ../../history-180806.osm.pbf
2018-10-16 20:44:50,870 INFO: Using replication service at https://planet.osm.org/replication/hour/
2018-10-16 20:44:50,870 INFO: Using timestamp 2018-08-06 00:59:56+00:00 as starting point.
2018-10-16 20:44:52,769 INFO: Starting download at ID 51689 (max 1024 MB)
Traceback (most recent call last):
  File "pyosmium-up-to-date", line 226, in <module>
    ret = update_from_osm_server(ts, options)
  File "pyosmium-up-to-date", line 64, in update_from_osm_server
    None, ts, options)
  File "pyosmium-up-to-date", line 121, in update_from_custom_server
    extra_headers=extra_headers)
TypeError: apply_diffs_to_file() got an unexpected keyword argument 'extra_headers'

Looks like your version of pyosmium-up-to-date and the pyosmium library don't match. Do you have an older version somewhere in your PYTHONPATH potentially installed with pip?

I'm not sure, when used pip install osmium it gave me the following:
~/osm_history_planet/pyosmium/tools$ pip install osmium
Collecting osmium
Installing collected packages: osmium
Successfully installed osmium-2.14.3

when tried to find the version number of osmium, I got the following:
osmium --version
osmium version 1.7.1
libosmium version 2.13.1
Copyright (C) 2013-2017  Jochen Topf<EMAIL_ADDRESS>License: GNU GENERAL PUBLIC LICENSE Version 3 <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

I don't understand if these are the same osmiums or if different ones exist on my system.

What does which pyosmium-up-to-date say? If you install pyosmium via pip, you need to use the binaries that come with it, which are usually installed in /home/ubuntu/.local/bin. You likely have also installed an older version of pyosmium via apt-get and are accidentally using that one.


chore: remove unused dependencies

found using cargo-udeps

CI failure doesn't look related to change


PWA asset caching for offline

A more recent trial run seems to suggest the component having problems may be maps.


Parsing error

Hi,
I tried to process metabolomics data and met followig error:
Error: There was a problem finding spectrum IDs within header file for this data. Error occured after function 'dissectScans'.
By debugging the function dissectScans,
function (mzDb, observedPeak, header)
{
  scansOfPeak <- which(observedPeak$start < header$retentionTime &
    header$retentionTime < observedPeak$end)
  peakHead <- header[scansOfPeak, ]
  ms1 <- peakHead$msLevel == 1L
  scanID <- as.numeric(sub("(.* )?scan=|(.* )?scanId=", "",
    peakHead$spectrumId[ms1]))
 ...
}

I found that scanID returns NA due to the invalid value of peakHead$spectrumId:
sample=1 period=1 cycle=233 experiment=1 which contained no scan or scanId information.
Other columns such as spIdx, acquisitionNum, and spectrum are fine
          scanWindowUpperLimit spectrum
F1.S01459                 1500     1459
F1.S01464                 1500     1464
F1.S01473                 1500     1473
F1.S01484                 1500     1484
F1.S01495                 1500     1495
F1.S01506                 1500     1506
F1.S01517                 1500     1517
F1.S01528                 1500     1528
F1.S01539                 1500     1539
F1.S01550                 1500     1550
F1.S01561                 1500     1561
F1.S01572                 1500     1572
F1.S01583                 1500     1583
F1.S01594                 1500     1594
F1.S01605                 1500     1605
F1.S01616                 1500     1616
F1.S01627                 1500     1627
F1.S01638                 1500     1638
F1.S01649                 1500     1649
F1.S01660                 1500     1660
F1.S01671                 1500     1671
F1.S01682                 1500     1682
F1.S01693                 1500     1693
F1.S01704                 1500     1704
F1.S01715                 1500     1715

This looks like a bug.  Just wonder if the scanID information can be extracted from other columns if scanId can not be found.
The test data is from https://drive.google.com/drive/folders/1PRDIvihGFgkmErp2fWe41UR2Qs2VY_5G
AB TripleTOF 6600 datasets
Thanks,
-Han

Dear Han,
Sorry for not responding sooner. I've been quite busy the past few days. I'll try and take a look at this today.
All the best,
Craig

Dear Han,
Thank you for your detailed review of my code. This is the first time I have worked with wiff type files. I think the bug can be attributed to that. I added some if statements to acquire scan number information from the column "spectrum" as you pointed out above. Please run the updated version of the code and let me know if you were able to run it. I was not able to reproduce your error, as I could not load the files into xcms. Could you please send me a script on how you are loading data into AutoTuner? I'd like to include the functionality to handle wiff files into other parts of the software. Hopefully, the changes let you run you Autotuner despite this.
All the best,
Craig

Hi Craig,
I converted the wiff files into mzML format through msconvert or
Proteowizard.  In order to do the conversion on Linux server,  I use docker
to do that:
https://hub.docker.com/r/chambm/pwiz-skyline-i-agree-to-the-vendor-licenses
-Han
On Mon, Jul 6, 2020 at 11:10 PM crmclean<EMAIL_ADDRESS>wrote:

Dear Han,
Thank you for your detailed review of my code. This is the first time I
have worked with wiff type files. I think the bug can be attributed to
that. I added some if statements to acquire scan number information from
the column "spectrum" as you pointed out above. Please run the updated
version of the code and let me know if you were able to run it. I was not
able to reproduce your error, as I could not load the files into xcms.
Could you please send me a script on how you are loading data into
AutoTuner? I'd like to include the functionality to handle wiff files into
other parts of the software. Hopefully, the changes let you run you
Autotuner despite this.
All the best,
Craig
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/crmclean/Autotuner/issues/29#issuecomment-654296860,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVZ7ZHLDBBBPWBKT4ZKGZLR2HSNBANCNFSM4ONCHYKQ
.

Ah, gotcha. One of the docs for xcms said it would accept wiff files if you loaded both the original and the scan file, but I wasn't able to figure it out in a short amount of time. If the solution does not work, would you mind sending me a few of the mzML files you generated?

@crmclean Absolutely not.

@crmclean The updated commit didn't work.  I added a few lines in EICParams.R and this works for me:
        header <- suppressWarnings( MSnbase::header(msnObj))

        # -- Begin: fix the header scanId problem
        scanID <- as.numeric(sub("(.* )?scan=|(.* )?scanId=", "", header$spectrumId))
        if (any(is.na(scanID))) {
          header$spectrumId <- stringr::str_c(header$spectrumId, " scanId=", header$spectrum)
        }
        # -- End

        allMzs <- MSnbase::mz(msnObj)

BTW, I am trying to benchmarking the tuning algorithms (MetaboAnalystR 3, IPO, Autotuner) using dataset from
Li et al. 2018 Comprehensive evaluation of untargeted metabolomics data processing software in feature detection, quantification and discriminating marker selection
The results are interesting: Autotuner gives more identified peaks, but quantification is not as good as others.  I will dig more into it.

Thanks for the fix! I'll update the code. Super curious, what do you mean by "quantification"?

@crmclean The actual log ratio vs. the expected log ratio (ground truth).

Gotcha. Thanks for clarifying.


Multiple features on sframesky from 20240406

There were several features observed on some of the sframesky from 20240406. There were no apparent effects on the redshifts (aside from some fibers being flagged with FIBERSTATUS!=0), I marked all tiles as good during QA.
On that night, there were visitors on the mountain. They left at 10pm, on exposure 234749. It seems unlikely that these features were caused by car lights. I couldn't find any other unusual features in the data.
Here are the features I found on the sframesky data:
Unmasked bright fibers across cameras b and r on petal 7 and across all cameras on petal 3.

Unmasked bright fibers across camera b and r on petal 7, along some vertical features on the r camera.

These are probably just some contaminated sky fibers that clearly didn't end up messing with the sky too much.  Closing.


ReScript Demo & New user interface

Hey!
I'm starting a new real-world app implementation using ReScript and React... and I want to know if I can use a redesign version of this real-world app. It will have the same features and a very similar UI but with a new branding, logo, colors but the same name. Will be considered a valid implementation for the official list? I can send a preview of the UI before implementing :)

Hello,
By providing specs, our goal is to make sure rules are available for everyone without having to argue on each submission.
As previous contributors respected these specs, it wouldn't fair to start accepting personal interpretations.
From the specs :

We created a custom Bootstrap 4 style & templates to ensure all frontends had consistent UI functionality.

However if the goal is to provide a better or more modern user experience, we'll soon start working on a v2 of the current specs. Challenging the user interface is part of this new version and we'll welcome any contribution.
Meanwhile for the current version of the spec, we encourage people to follow them to add them to the implementation list.

Thanks for answering!
I understand that all projects here are following the current spec. But if the project has the same features and a similar UI (navigation, sign-in page, list of items, etc) is not acceptable to be a real-world app that follows the technical requirements of the spec? I don't understand how a color or the logo of the UI can impact the comparison between two projects that delivers the same feature. I respect and understand your decision, I just want to help and contribute to this project :)
@mvila I'm working on the UI, but I have a preview of the wireframe and a draft of the branding/colors 😀
Wireframe of the sign-in page:

@vmarcosp Your UI looks very nice, and it'd be a shame not to accept it.
@geromegrignon Could we make an exception?

Thanks @mvila! 😄
If you like and agree we can work together on a new UI to the v2 or we can use this UI that I'm creating for my real-world app implementation :)

Since the v2 is not for tomorrow, I think you should start implementing a v1 with the UI you have in mind, and we'll see later if this UI can be used in the reference implementation of the v2.

I totally agree @mvila, thanks for answering 😄

As an exception which will showcase the future of the ui for next version we can integrate it.
However @vmarcosp, you must consider the ui is part of the specs, not an option.
The goal of these specs is to be able to provide rules for everyone, rather than having to argue with each implementation.
Such situation would lead to the end of the project as it doesn't scale. The former maintainer team tried to manually test and review each implementation and while they did a great work, having to spend time on individual contributions over the community did lead to having issues still opened after few years.
Your changes aren't just about colors :

having additional images means your implementation is less performant on a benchmark (as there are defined specs, consumers shouldn't be expected to dive into source code to see if there are any difference between 2 implementations)
as you are using different stylesheets, consumers can't compare how you integrate the specs. If it sounds obvious for you, we had some use cases where integrating the stylesheet has a cost or need some changes. Such differences are valuables when you need to compare implementations.

Besides the submission of this implementation, we would be happy to work with you on the next version o the ui.

@geromegrignon You're right, my changes aren't just about colors. Having additional images means that implementation is less performant, I agree. I would be happy if you accept my implementation with a new UI, maybe adding a disclaimer about an exception that you made for my case, I appreciate 🙏🏻

Besides the submission of this implementation, we would be happy to work with you on the next version o the UI.
Sure, I can help you with the design of a new spec / v2.

About the exception, i would encourage you to add a disclaimer into the readme.md of your repository.

@geromegrignon I can do this. So, for my case,  following the spec (features, sign-in page, feed page, etc) but with a new UI, might be accepted as an official implementation? Just to make it clear 😄

Accepted! :+1:


Custom Id for md2-datepicker

Hi, As far as I can see, there isn't a way to add a Custom ID to the  component!
I tried doing it like
<md2-datepicker id="customID"></md2-datepicker>

You can find a working example of the datepicker here with fixed id.
However, the id remains the one you assign in your file here..
  /** The id for the datepicker calendar. */
  id = `md2-datepicker-${datepickerUid++}`;

Is there a way we can input() id attribute of the md2-datepicker object?
Please guide.
Thanks for these nice components!

@shubham-k7 will provide it in next build


https proxy support

https://github.com/jwilder/nginx-proxy already has HTTPS support, it's just not seamless enough for a development environment. I'd like to make it unnecessary to manually generate a self-signed cert for each app. Maybe just a default cert for all apps, the domain mismatch isn't a huge deal if the cert will have to be manually accepted anyway.

To address this would you consider supporting a different domain structure?
I assume that the issue is that you can't get a browser to trust a wildcard on a TLD, like *.docker.
You can issue a wildcard certificate to *.dock.er that browsers will trust. (Not saying I like app.dock.er, just that you can use a wildcard at that point.)
Thanks for the great project, by the way. :)

That's a great point, I actually hadn't considered it that far yet. Thanks, I agree that it's worth switching to a 2nd level domain to implement this in a seamless way.

Just want to add a :+1: here, since I'm eagerly awaiting this feature.
In the interim, is there a manual approach I can use to mount my SSL certs/keys into Dinghy's running nginx-proxy container?

Thought I might add, I believe a wildcard cert like *.docker is perfectly valid, it's just highly unusual to see.

The cert would be "valid", but most browsers are hard-coded to reject it anyway. See for instance http://security.stackexchange.com/questions/6873/can-a-wildcard-ssl-certificate-be-issued-for-a-second-level-domain

Oh wow, the comments in the Chromium source seem to suggest that not only are second-level wildcard certs rejected, but any cert from a non-standard TLD is also rejected.
https://chromium.googlesource.com/chromium/src/net/+/HEAD/cert/x509_certificate.cc#574

Thanks again for this great project. Until Docker will support natively Docker on Mac OS X, it's the only way to go when using large file sharing...
I understand that https support of jwilder/nginx-proxy  is not as straightforward as it should be especially for a development environment. However, complex support would be better that no support at all.
How would you recommended the use of https with dinghy ? By-pass the dinghy nginx-proxy and use it directly in our containers ?
I look at the codekitchen/dinghy-http-proxy, it seems that the support of https has been removed in the nginx templates files, and the http_proxy.rb file mention certificates but do not mount the port 443. Would it be much more difficult than reuse the original Nginx templates files regarding SSL support to reactivate it ?
To go further, and regarding the previous posts, the use of a wildcard *.docker seems to be difficult. Why about the generation of self-signed wildcard domain by changing the dinghy_domain variable ? Or what about auto-generating trusted certificates from let's encrypt like the project https portal does ?

Just added two pull requests to implement a basic https support in the way jwilder/nginx-proxy did. I think I backported only what was needed for single host certificate files (no wildcard or SNI).

Patch for dinghy
Patch for dinghy_http_proxy

Thanks again for the work there. I'm going to close this, and open a separate issue for auto-generating certs, if we ever want to tackle that.


[BUG] server list is not working

Describe the bug
just cant load server list
[HTML] asset://garrysmod/html/js/menu/control.Servers.js:414: Uncaught TypeError: Cannot read property 'toLowerCase' of undefined
To Reproduce
Steps to reproduce the behavior:
1, go to multiplayer
2. check console
3. PROFIT
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: windows 10
Branch of the game: x86-64 - Chromuim + 64-bit binaries

Additional context
and yes add a text for sort gamemode

After Update 21/11/20 project maintaining has been stopped. Thanks

After Update 21/11/20 project maintaining has been stopped. Thanks

@Blueberryy Thank you very much for the response :)
@joinmod Yes, the project is no longer maintained because I don't have enough time to redo the whole menu !
And with the arrival of S&Box I don't think it's useful to spend more time doing it again on Gmod ;)


gui: Markdown renderer/chat content display

Due to the various issues currently open that are due to roughly the same overall issue, I figured I'd open up an issue that would describe the current problems and requirements for a new (or forked) widget.
(Issues that would be fixed: #160, #135)
Currently, we are using the 'official' markdown renderer package flutter_markdown.  While this does do a pretty good job at displaying a wide range of content, we're currently experiencing issues with a few different element types within the markdown, namely embeded images, code blocks and quotes.  And currently we can't have nice text selection due to an issue with the widget (and roughly described in the opened issue here: https://github.com/flutter/flutter/issues/99819).
My first proposal is to create a parent widget that would still use Markdown below, but would first parse various portions of the text to render and then create a series of widgets to display the content as expected.  So for instance if the message/md sent was the following:

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc id ipsum tellus. Sed accumsan lectus diam, ac eleifend metus hendrerit scelerisque. Vivamus eleifend neque vitae cursus gravida. Sed dictum diam quis diam cursus, ut pharetra nunc aliquam. In sed velit a tortor tincidunt scelerisque. Phasellus dignissim at felis id fringilla. Vestibulum efficitur nulla et ex viverra, in tincidunt dolor finibus. Donec vitae dui vel turpis vehicula condimentum sit amet nec mi. Vestibulum et est lorem. Praesent auctor fringilla leo a eleifend. Maecenas rhoncus lacus ut leo vehicula bibendum. Quisque dictum eros vitae est accumsan eleifend. Sed at lorem augue. Morbi cursus massa nisi. Phasellus non nisl eros.

Vestibulum condimentum dolor a libero blandit, tempor venenatis tortor euismod. Donec vitae suscipit sapien. Phasellus quis rhoncus turpis. Nunc laoreet nulla sed facilisis cursus. Ut eu egestas odio, ut vehicula lacus. Mauris tellus velit, tempus vitae euismod id, pharetra sit amet massa. Etiam velit leo, tincidunt nec convallis quis, lacinia at quam. Nulla aliquam volutpat purus id malesuada. In hendrerit sit amet velit at dictum.

Quisque dolor quam, fringilla eu leo sed, molestie lacinia nisl. Quisque porta luctus laoreet. Fusce a ultricies turpis. In placerat augue at tempus vulputate. Donec felis eros, ullamcorper nec fermentum ut, convallis eu lectus. Sed vel ipsum nec odio volutpat aliquam. Praesent sodales urna id mi posuere, quis viverra tellus rutrum. Cras quis condimentum nibh. Praesent et orci sed nisi iaculis accumsan. Quisque congue elementum elit sed sagittis. Morbi semper auctor rhoncus.

This message would then be split up into 4 "different" widgets below that would offer more granularity for things like scroll-downs and correct sizing for images.   The parser could find the image, the codeblock and the quote area and handle them individually and then present them all together as a single message for the end user.
This is just a brainstorming activity now to hopefully capture all the limitations of our currently markdown situation.

We can customize flutter_markdown's MarkdownBody with MarkdownElementBuilders. It doesn't work so nice for nested tags, like
some text
 because we can't pass a MarkdownElementBuilder to both tags without changing the package code.  Also, we don't have much control about inline text elements styles, like strikethrough, bold, italic, code, etc. because they are basically TextSpans in a huge Text.rich Widget. That means we can only pass TextStyle styles to them and we can't control some stuff like borders, etc.
That said, I think flutter_markdown with MarkdownElementBuilders and some tweaks to my forked repo is enough for our needs.


Add removePackage function to Environment Package cache

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues.

Fixes #31669
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

This will be revisited for beta4 after new package resolution changes

This has been fixed with https://github.com/ballerina-platform/ballerina-lang/pull/33639


Suggestions regarding the new heat exchanger design

Seen that the heat exchanger is not done for overhaul yet, as a chemical engineer myself I have some suggestions regarding the design.
Here is a simplified schema for a shell-and-tube heat exchanger which is mostly used IRL

Normally the heat exchange happens between 2 fluids only in a single HX, it is divided into shell side and tube side where 2 fluids are separated. Usually the pressure on both sides are quiet different .
The material selection depends mostly on the operating conditions (temperature, pressure) and how corrosive the fluid is. Normally it is carbon steel or stainless steel, and sometimes copper or other alloys. The heat exchange efficiency is not always a concern, since one can just build a bigger one (or make a series of them) instead of upgrading to expensive and less mechanically-performant materials.
As for application for nuclearcraft, I’d recommend:

Divide the HX into shell and tube, where shell side is the chassis, and tube side same as before. There can be only one fluid in the shell side, but possibility to have more than one fluid in different “tubes”. Shell side can be rendered as fluid tanks.
Each fluid input must be filtered, so that when forming the structure all the processing capacity is fixed, thus improving the performance.
Use baffles blocks in the shell side to regulate the flow, refer to pic above for placement. Too many baffles will result in a lower flowrate, too less will lead to a lower heat exchange efficiency. Applying this to Minecraft means either will lead to a lower processing efficiency.
Fluid viscosity is something interesting to consider yet might be difficult to implement, with it one can define the maximum flowrate of fluids for different types of tubes, where one must also balance between heat exchange efficiency and max flowrate as above. Also longer tube + viscous fluid = less flowrate.
But of course one can always add more tubes, making the exchanger bigger. The optimum inter-baffle distances can be also affected by viscosity.
To be more sadistic, add penalty for oversized exchangers.

I understand it’s rather different with current implementation, but with this in mind, it’s very easy to make an exchanger that works, but more difficult to make it just right: Player need to optimize the tube type/count and baffle placement based on the fluids on both sides. Please let me know if you are interested in some of these ideas.
Also a question, with current forge fluid system I wonder if it’s possible to have one fluid at 2 different temperatures instead of having two fluids?

I've left this unanswered for a while, but should say that when I actually get to implementing the new multiblock, I'll be happy to chat about incorporating these concepts into the 'NuclearCraft-style' framework :)


[CSYS-345] Migrate PasswordInput.js to function component

Link to task:
CSYS-345
Staging app:
https://CSYS-345-migrate-password-input-to-fn-component--confetti-storybook.netlify.app/
How to test:
Just run all tests with npm run tests to check if the component has problems.
Description of your solution:

Moved proptypes to outside the class component.
Changed the class to function.
Removed this statements.

Screenshots (when applicable):
N/A

LGTM! @tiidadavena can you create a PR on confetti-storybook, pointing to this branch, before we merge this? I'll approve this PR once everything is ok on storybook

Yes, of course, Lélis. Tks for the reminder :D


iptables,option,node: Consistent condition for ipset usage

This pull request fixes a bug where we would create ipsets and fill them with IP addresses even though they would never be used by our iptables rules.
To fix this, we introduce a new NodeIpsetNeeded helper function, such that there is a single place where we define whether node ipsets should be used. This helper function is then used both to create ipset iptables rules and add IP addresses to ipsets.
Fixes: https://github.com/cilium/cilium/pull/16603.
Related: https://github.com/cilium/cilium/issues/18787.
Fix bug where unnecessary ipset was created and populated in tunneling mode with iptables masquerading.

/test

/test-runtime

/test


fix connect session logic and wait for gae ready

Codecov Report

Merging #2326 (59121c1) into main (f9c8698) will decrease coverage by 1.31%.
The diff coverage is 15.78%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2326      +/-   ##
==========================================
- Coverage   72.97%   71.66%   -1.32%
==========================================
  Files          89       89
  Lines        9937     9956      +19
==========================================
- Hits         7252     7135     -117
- Misses       2685     2821     +136

Impacted Files
Coverage Δ

...on/graphscope/tests/kubernetes/test_demo_script.py
81.75% <15.78%> (-10.63%)
:arrow_down:

python/graphscope/tests/unittest/test_java_app.py
53.01% <0.00%> (-46.99%)
:arrow_down:

python/graphscope/analytical/app/java_app.py
24.36% <0.00%> (-27.92%)
:arrow_down:

python/graphscope/client/rpc.py
81.67% <0.00%> (-3.06%)
:arrow_down:

python/graphscope/framework/graph_utils.py
80.15% <0.00%> (-2.39%)
:arrow_down:

python/graphscope/client/session.py
75.18% <0.00%> (-1.52%)
:arrow_down:

python/graphscope/framework/app.py
90.32% <0.00%> (-1.39%)
:arrow_down:

python/graphscope/framework/utils.py
67.25% <0.00%> (-1.00%)
:arrow_down:

python/graphscope/framework/graph_schema.py
64.61% <0.00%> (-0.23%)
:arrow_down:

Continue to review full report at Codecov.

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


⚠ ClamAV has degraded performance

In a9dfb8d, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 473 ms

Resolved: ClamAV performance has improved in 8f99560.


DOCS-1357: Restores SysReq prerequisite to RKE install procedure

Product Version(s):

Issue:
https://tigera.atlassian.net/browse/DOCS-1357
Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

@lwr20 Can you take a look?

@lwr20 Can you take a look?


hdfs: Implement overwrite flag on client.Create method

We are using this library to send siva files to HDFS: github.com/colinmarc/hdfs. We will need to be able to set a flag to overwrite=true in some cases into the client.Create method. We can do a PR to these library with the improvement.

fixed here: https://github.com/src-d/core-retrieval/pull/33


Virtual IP failover - Cluster ARP probing in overlay

Issue Type

Role enhancement

Is your feature request related to a problem? Please describe.
There will be services that rely on ARP probing mechanism in Overlay and Arista has workaround for this
https://eos.arista.com/eos-4-21-3f/virtual-ip-failover-support/
The main idea is the nodes in cluster use ARP for keepalive mechanism, so by default if the VLAN has IRB we trigger ARP suppression, which is not desirable for certain hosts.
Describe the solution you'd like
Option to configure a prefix-list with hosts that we should not perform ARP suppression
Describe alternatives you've considered
Use pure L2 VLAN with no IRB, or configure this statically.
Additional context
router_l2_vpn:
  arp_proxy:
    prefix_list: < prefix_list_name >

We will need to be able to extend this in a way that with a knob (true/false) under SVI we should be able to factor the IPv4 Subnet and Mask to the prefix-list, otherwise large setups with suffer.

This needs to be abstracted at some point into eos_designs.

Can we abstract this in a way to be able to use this under tenants structure.
router_l2_vpn:
arp_proxy:
prefix_list: < CLUSTER_NODES >
So we will use a knob under each VRF/SVI and specify a /32 prefix that will be appended to the prefix-list which is a global prefix-list per router that is valid for all VRFs. This way customer can easily remove / add items from prefix-list.
svis:
  "820":
     disable_proxy_arp: < prefix/mask >

prefix_lists:
  < CLUSTER_NODES >:
    sequence_numbers:
      10:
        action: "deny < NODE_1 >/32"
      20:
        action: "deny < NODE_2 >/32"
      30:
        action: "deny < NODE_3 >/32"