[Merge] Merge develop into sdp-multitenant

Merge from develop to sdp-multitenant
Please review that your changes were ported correctly. We had to port some of the features, please review your feature and make sure it's ported correctly.

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr191.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr191.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr191.previews.kube001.services.stellar-ops.com


Overflow Account.ID in 32bit systems fix

I faced issues with immediately logout after login request. This is caused by casting int64 to int on adding authorization header (Ig-Intended-User-Id) while compiling it for arm32. Potentially fixes builds for other 32-bit systems.

When writing the lib I wondered if this was ever going to cause any issues hahah

If you find more casting issues please fix/let me know

Can you please add new release tag?

Changed all other int64 castings and tagged the release


DISABLE_GIT_HOOKS env variable is ignored

Gitea version (or commit ref): 1.14.0+dev-461-ga19447aed
Git version: 2.20.1
Operating system: Debian 10
Docker version 20.10.1, build 831ebea
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[X] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[X] No

Description
I start a fresh installation from gitea server with docker and provide a empty directory as volume to gitea. As decribed I set the enviroyment variable DISABLE_GIT_HOOKS to false. I am awaiting a "Git-Hooks" button in the project settings.
/usr/bin/docker run
.... more parameter like network, dns, ip etc ....
-v /emptydirectory/:/data/
-e DISABLE_GIT_HOOKS=false
gitea/gitea:latest
This creates a default ini file with no DISABLE_GIT_HOOKS entry under security

The parameter is a env variable inside the container but it seems that it is ignored. There is no Git-Hooks option in the web user interface

Then I edit the persistent ini file and add the missing DISABLE_GIT_HOOKS under security and restart the container. After setting the value in the ini file I am able to use Git-Hooks in the user interface.

DISABLE_GIT_HOOKS is not an env var that the docker image accepts. Please read the Gitea docker documentation for the list of env vars that are available for initial configuration.


Add https transport via luasec or ngx.socket

This is based off of #3. When that's merged, I'll rebase against master.

@mattrobenolt You can now rebase

Any updates on this guys? Would love to see this feature going in sooner rather than later. :)

If someone is passionate about it, they're happy to take over. I have close to 0 Lua experience and was poking around. Someone who knew more about Lua that this was a bad implementation, so I didn't attempt to continue. :)

A little googling on StackOverflow has pointed me to https://github.com/brunoos/luasec/wiki. So luasec might be the way to go ?

Yeah, this sounds familiar. Pretty sure this was the thing that we should use.


[FSSDK-8823] chore: release chart version 1.4.0

Summary

Release chart version 1.4.0 for Agent release 4.0.0

Ticket

FSSDK-8823

Side Note: Do you think we copy in the README content into this branch so https://optimizely.github.io/optimizely-agent-helm/ is a little more complete?
Plus, the links are on optimizely.github.io so we'll get a little extra SEO ❤ I'd 🤔 maybe 🤷


ffmpeg is not present in Ubuntu

Could there be alternatives to using ffmpeg offered in download_dataset.sh?

You should be able to get ffmpeg at this address:
https://johnvansickle.com/ffmpeg/releases/ffmpeg-release-64bit-static.tar.xz


Update camel quarkus micropofile metrics doc

Trying to fix issues in  Camel Quarkus 2.13 doc update PR

@oscerd  Ok let me do cherry-pick to those branches


Setup unit testing for websocket.js

Websocket.js has grown into quite a bit of code already, including some difficult (and error-prone) parsing code. At this point I don't think it is feasible to not have specific unit tests for all the methods in there. I should invest some time into setting something up like https://jestjs.io/

Add coverage (https://gotwarlost.github.io/istanbul/ ?)

Coverage added: https://github.com/medusa-ui/medusa/tree/main/medusa-ui/src/test/resources/coverage
Now to actually fill up the branches with tests


Add GitHub workflow for testing Vienna

Eventually we can replace Travis with GitHub workflows. Replaces #1275 and #1289 and #1310.

Well, we will wait and see, but some recent attitudes of GitHub (especially the taking down of youtube-dl) makes me wary of depending too much on GitHub proprietary tools.

@barijaona: Meanwhile, Travis is becoming paid-only for macOS. I am not sure if I understand the announcement correctly, but the allotted credit for FOSS projects do not apply to the surcharge for macOS.


[Question] Usage in Modpacks

Greetings,
I'm currently working on a VulkanMod based performance Modpack and would like to include this particular mod as well. However, I haven't found any information about the usage in Modpacks in the description.
What am I allowed to do?

Faster Random is licensed under Apache 2.0, so you're fine to put this mod in your modpack as long as you attribute the mod dev.
Furthermore, this means any mod with a permissive license like BSD, MIT, Apache, etc can be put in a modpack as long as you provide credit.


Test 2

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #
https://b1--my-franklin-website--achelsau.hlx.page/
Test URLs:

Before: https://main--{repo}--{owner}.hlx.live/
After: https://--{repo}--{owner}.hlx.live/

gen tests

gen tests

gen tests

gen tests

gen tests


Playground fails to start with error dependency failed to start: container playground-ranger is unhealthy

Expected Behavior:
Following the instructions in the documentation, Gravitino Playground containers should be healthy
Current Behavior:
Starting playground with ./playground.sh start shows that the playground-ranger container is unhealthy
Steps to Reproduce:

Build Apache Gravitino on Windows (Using WSL)
Clone or download Gravitino playground repository
cd gravitino-playground
Start playground with ./playground.sh start
After running, playground-ranger's status is unhealthy

Seem like playground.sh line 55 echo "Checking ports with sudo permission ...' unexpected EOF while looking for matching


Move Google.NearbyShare 1.0.993.0 to Google.QuickShare 1.0.993.0

Microsoft Reviewers: Open in CodeFlow

https://github.com/microsoft/winget-pkgs/issues/142854


DOCS: API docs ToC more levels

🚀 Pull Request
Description

Increases from 1 to 3 for the level of table of contents in the right hand sidebar. This makes a significant different when browsing the API Documentation.
Some examples:

Plotting a Cube: latest, this PR
The Mesh Data Model: latest, this PR
API index: latest, this PR
iris.analysis: latest, this PR
iris.exceptions: latest, this PR

Note that some ToCs (right side) are really useful, but some cab be long with a vertical and horizontal scroll (see iris.exceptions link above).
I believe the benefits in the navigation outweigh any scrollbars being present.  This PR may need some visibility to more than just a single reviewer.  Perhaps a short discussion in a @SciTools/peloton .

Consult Iris pull request check list

@tkknight are you still hoping to have team eyes on this before it gets merged?

@tkknight are you still hoping to have team eyes on this before it gets merged?

I think that will be useful.

@SciTools/peloton unanimously agrees!


F tensorflow/stream_executor/cuda/cuda_dnn.cc:88] Check failed: narrow == wide (-2128347136 vs.<PHONE_NUMBER>)checked narrowing failed; values not equal post-conversion

For some reason I get this error on the predict step. It doesn't happen for all tomograms, and I can't seem to track down the common issue. Was wondering if anyone has run into this?
My workflow is -> motioncor2 splitsum -> warp to make tilt stacks -> aretomo align/reconstruction (bin4). This current issue is coming from tomograms reconstructed from this data set: https://www.ebi.ac.uk/empiar/EMPIAR-10499/. I am currently using it to test that my new workstation was running smoothly, but have run into this error.
Any insight would be very appreciated.

Hi @rnwokonko,
I have encounter this issue in the past. Unfortunately I don't have a explanation to what is the root cause for this issue. But it seems to be connected to the tomogram size. I usually managed to get the network to work by increasing n_tiles slightly which reduced the size of the patches that were denoised.

I just encountered the same issue and increasing the number of tiles to [4, 4, 4] made it work.

Most likely this is clear, but I just want to mention it here again. Any number of tiles works, not only powers of two. So increasing from (4 ,4, 4) to (5, 4, 4) would also be fine.

Just wanted to circle back - it looks like increasing ntiles from [1,1,1] to [4,4,4] worked for my data set. I haven't tried other numbers.
Thanks for the input.


Support 'use strict'

When loading this file via babel/webpack which adds "use strict" by
default it throws an error because "i" is not defined.
I've added "i" to the var list at the beginning of the "ringArea"
function.

👍 Thanks David!


Add Fil9 dataset

Description
http://mattmahoney.net/dc/text.html

The test data for the Large Text Compression Benchmark is the first 109 bytes of the English Wikipedia dump on Mar. 3, 2006. http://download.wikipedia.org/enwiki/20060303/enwiki-20060303-pages-articles.xml.bz2 (1.1 GB or 4.8 GB after decompressing with bzip2 - link no longer works). Results are also given for the first 108 bytes, which is also used for the Hutter Prize.

We filter the 1 GB test file enwik9 to produce a 715 MB file fil9, and compress this with 17 compressors. Furthermore, we produce the file text8 by truncating fil9 to 100 MB, and test this on 25 compressors, including the 17 tested on fil9. The purpose of the smaller file is to allow quicker testing, and to establish the predictive value of this quick test on the larger data set.

Previously only Text8 was included in GluonNLP.
Checklist
Essentials

[X] Changes are complete (i.e. I finished coding on this PR)
[X] All changes have test coverage
[X] Code is well-documented

Changes

[X] Add Fil9 dataset from Large Text Compression Benchmark

Comments

Both datasets are now also hosted in our S3 bucket. Previously Text8 was downloaded from the authors homepage.

Job PR-363/3 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-363/3/index.html

I'm not sure why the coverage script reports changes in finetune_lm.py Actually coverage should be improved overall by this PR as it introduces tests for Text8 and Fil9.


Fluentbit loading unwanted index patterns

2 issues with kubernetes-logging-helm/chart/templates/fluent-bit/fluent-bit-config-sec.yaml.

I have created a PR for this change, https://github.com/dfishburn/kubernetes-logging-helm-1/pull/1

First issue:
    {{- if .Values.kafka.enabled }}

Only tests if the variable exists, not whether it is true or false.
This was showing up when I ran:
helm upgrade ofd -n os-logging --create-namespace -f ./single-node-setup.yaml ./../chart --install --wait-for-jobs --timeout=30m --debug --dry-run

You will see the @INCLUDE _output-kafka.conf, even though I had defined:
kafka:
  enabled: false

Updating the if to validate the variable is set to true resolves this.
    {{- if eq .Values.kafka.enabled true }}

2nd issue
The default indexPatterns is set to:
opensearch_dashboards:
  indexPatterns:
    - containers
    - systemd
    - nginx

In my case, the containers where chewing up all available space on my system.
I had already created a custom setup so that my logs were indexed under a separate pattern.
Therefore, I was not interested in the containers at all.
Removed - containers, unfortunately, the OUTPUT is still created and logged.
This change will prevent the creation of the [OUTPUT] if the deployment has not requested that index.
It was put into the file using this syntax:
  _output-opensearch-containers.conf: |-
  {{ if has "containers" .Values.opensearch_dashboards.indexPatterns }}
    [OUTPUT]
        Name                opensearch
        Match               kube.*
        Alias               containers
        Host                ${FLUENT_opensearch_HOST}
        Port                ${FLUENT_opensearch_PORT}
        HTTP_User           ${FLUENT_opensearch_USER}
        HTTP_Passwd         ${FLUENT_opensearch_PASSWORD}
        Logstash_Format     On
        {{- if .Values.fluentbit.indexPrefix }}
        Logstash_Prefix     {{ printf "%s-containers" .Values.fluentbit.indexPrefix }}
        {{- else }}
        Logstash_Prefix     containers
        {{- end }}
...
  {{ end }}

I had originally set it up as:
  {{ if has "containers" .Values.opensearch_dashboards.indexPatterns }}
  _output-opensearch-containers.conf: |-
    [OUTPUT]
        Name                opensearch
        Match               kube.*
        Alias               containers
        Host                ${FLUENT_opensearch_HOST}
        Port                ${FLUENT_opensearch_PORT}
        HTTP_User           ${FLUENT_opensearch_USER}
        HTTP_Passwd         ${FLUENT_opensearch_PASSWORD}
        Logstash_Format     On
        {{- if .Values.fluentbit.indexPrefix }}
        Logstash_Prefix     {{ printf "%s-containers" .Values.fluentbit.indexPrefix }}
        {{- else }}
        Logstash_Prefix     containers
        {{- end }}
...
  {{ end }}

But later on in this file we were issuing:
    @INCLUDE _output-opensearch-*.conf

And if we had so happened to turn off BOTH the systemd and containers then this line would fail as there would be no files which would meet the wildcard.
opensearch_dashboards:
  indexPatterns:
    - nginx

Leaving it as I have has worked for me.

Good catch @dfishburn  Can pls you create e PR against the main branch in this repo? I will merge it. Thanks

@nickytd the PR is at the top of the issue, did I do it correctly?

The correct handling of the enabled kafka field is fixed with https://github.com/nickytd/kubernetes-logging-helm/commit/0aa4bfd57accbf28b673d119c1e9d2c63e444e4c
The opensearch_dashboards.indexPattern is related to creating index patterns in the UI and shall not be used to control what indices shall be created in the opensearch data nodes. The containers index is default and shall not be removed. But that doesn't mean that all workloads  outputs shall be targeted there. If the requirement is to create a dedicated indices for particular workloads then nginx configs demonstrates an implementation strategy.
Here is a pattern that demonstrates how to redirect the logs from a specific workload to its own index in fluent-bit configuration

Create a filter catching the workload logs and set a new tag.  In this example we use kubernetes labels to identify nginx ingress controller logs and tag them with nginx
(Optional) Create a parser to transform the logs from lines to structured logs
Create a fluent-bit output containing the dedicated index prefix name.

Follow the naming convention for the files using the filter-, parser-, output- prefixes and place those in the fluent-bit-configs folder to be picked up by helm. The secret template for the fluent-bit configuration respects the location and pickups the files with the respective naming convention, adding them to the correct places in the fluent-bit configuration.

@nickytd the changes you checked in did not include these changes:
  _output-opensearch-containers.conf: |-
  {{ if has "containers" .Values.opensearch_dashboards.indexPatterns }}

And the same for systemd.
Did you do it a different way?
Without the change(s), all the data is still indexed and does not fix my original issue.


Ability to hide the scroller

Hi @krimin-killr21
Excellent library. There are couple of situations like Empty list, etc when the scroller is not needed can there be any method for this. I guess I tested setVisibility() which didn't work out.

Fixed. Use setScrollBarHidden(true) from now on.

Thank you so much.
Regards,
Akshay Chordiya
On Sep 13, 2015 1:04 PM, "Turing Technologies"<EMAIL_ADDRESS>wrote:

Fixed. Use setScrollBarHidden(true) from now on.
—
Reply to this email directly or view it on GitHub
https://github.com/krimin-killr21/MaterialScrollBar/issues/7#issuecomment-139849050
.


Detox build fails (minSDK version should be updated)

Fixed by #25, thank you! New release out now: 0.8.1


nacos-config.sh error

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description
$ sh ./nacos-config.sh
set nacosAddr=localhost:SEATA_GROUP
set group=
\033[31m Please check the cluster status. \033[0m
Ⅵ. Environment:

JDK version :
OS :windows 10
Others:

https://github.com/seata/seata/pull/2262


Error on integrating with sidekiq-scheduler

Hello folks,
Thank you for developing this gem. It provides such an elegant solution.
However, we've encountered an issue when integrating your gem with sidekiq-scheduler. Although we couldn't consistently reproduce the error, it seems to occur under certain conditions and results in the following stack trace:
TypeError: can't convert String into an exact number
-(/usr/local/bundle/ruby/3.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/time/calculations.rb:314)
minus_with_duration(/usr/local/bundle/ruby/3.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/time/calculations.rb:314)
minus_with_coercion(/usr/local/bundle/ruby/3.3.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/time/calculations.rb:325)
block in assign_queue(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-fair_tenant-0.1.0/lib/sidekiq/fair_tenant/client_middleware.rb:59)
filter(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-fair_tenant-0.1.0/lib/sidekiq/fair_tenant/client_middleware.rb:57)
assign_queue(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-fair_tenant-0.1.0/lib/sidekiq/fair_tenant/client_middleware.rb:57)
block in call(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-fair_tenant-0.1.0/lib/sidekiq/fair_tenant/client_middleware.rb:22)
block (2 levels) in with(/usr/local/bundle/ruby/3.3.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:110)
handle_interrupt(/usr/local/bundle/ruby/3.3.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:109
block in with(/usr/local/bundle/ruby/3.3.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:109)
handle_interrupt(/usr/local/bundle/ruby/3.3.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:106)
with(/usr/local/bundle/ruby/3.3.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:106)
call(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-fair_tenant-0.1.0/lib/sidekiq/fair_tenant/client_middleware.rb:20)
traverse(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-7.1.6/lib/sidekiq/middleware/chain.rb:182)
invoke(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-7.1.6/lib/sidekiq/middleware/chain.rb:173)
push(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-7.1.6/lib/sidekiq/client.rb:88)
block (2 levels) in enqueue_jobs(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-7.1.6/lib/sidekiq/scheduled.rb:39)
each(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-7.1.6/lib/sidekiq/scheduled.rb:33)
block in enqueue_jobs(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-7.1.6/lib/sidekiq/scheduled.rb:33)
block in redis(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-7.1.6/lib/sidekiq/config.rb:163)
block (2 levels) in with(/usr/local/bundle/ruby/3.3.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:110)
handle_interrupt(/usr/local/bundle/ruby/3.3.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:109)
block in with(/usr/local/bundle/ruby/3.3.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:109)
handle_interrupt(/usr/local/bundle/ruby/3.3.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:106)
with(/usr/local/bundle/ruby/3.3.0/gems/connection_pool-2.4.1/lib/connection_pool.rb:106)
redis(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-7.1.6/lib/sidekiq/config.rb:160)
redis(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-7.1.6/lib/sidekiq/component.rb:28)
enqueue_jobs(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-7.1.6/lib/sidekiq/scheduled.rb:32)
enqueue(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-7.1.6/lib/sidekiq/scheduled.rb:107)
block in start(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-7.1.6/lib/sidekiq/scheduled.rb:99)
watchdog(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-7.1.6/lib/sidekiq/component.rb:10)
block in safe_thread(/usr/local/bundle/ruby/3.3.0/gems/sidekiq-7.1.6/lib/sidekiq/component.rb:19)
block (2 levels) in thread_block_with_current_transaction(/usr/local/bundle/ruby/3.3.0/gems/newrelic_rpm-9.10.2/lib/new_relic/agent/tracer.rb:434)
capture_segment_error(/usr/local/bundle/ruby/3.3.0/gems/newrelic_rpm-9.10.2/lib/new_relic/agent/tracer.rb:357)
block in thread_block_with_current_transaction(/usr/local/bundle/ruby/3.3.0/gems/newrelic_rpm-9.10.2/lib/new_relic/agent/tracer.rb:433)

Our hypothesis is that some code is "stringifying" the sidekiq_options and converting the ActiveSupport::Duration objects in the per configuration into strings, causing the error.
We resolved the issue by using integer values instead of ActiveSupport::Duration objects. While this workaround is effective, it might be beneficial to include a warning in the README to enforce integer values usage, or implement a way of convert strings back to ActiveSupport::Duration objects if necessary.
Thank you for your attention to this matter. We appreciate your work on this gem.

Thanks for the report and kind words.
Sometimes, job configuration hash is being serialized and deserialized for whatever reason, and it is a bit of pain to understand why and when :face_with_head_bandage: (this gem already have some conversions to handle a bit different formats of it)

converting the ActiveSupport::Duration objects in the per configuration into strings

Do you have examples of such strings, what format they are in? Maybe it can be detected and parsed back to durations (e.g. if it is an ISO format)…


Factories for Eventstore with different configurations

Implemented in https://github.com/Enforcer/python-event-sourcery/pull/35


Support tensorflow

Support Tensorflow, already comment out the changes specific for Tensorflow.
Though I am still a N00b, I really like this repro, which is a super clear and easy learning materials :)

My pleasure if it helps in any way.  Please allow me some time to review the changes. Happy Chinese New Year!

I have just merged your commits to support tensorflow. There seems to be some problems, say the L2 penalty part and the train_step() method in the file policy_value_net_tensorflow.py. I have tried to fix all the problems, but not sure doing it right or not. So if you have time, maybe you can review my changes to your commits to double check. Thanks.


Crash on Ubuntu 12.04

From @isomorphisms on https://github.com/Microsoft/vscode/issues/50
I got this error in Ubuntu 12.04.
A JavaScript error occurred in the main process
Uncaught Exception:
Error: Failed to set path
    at Error (native)
    at Object.<anonymous> (/opt/VSCode-linux-ia32/resources/atom.asar/browser/lib/init.js:120:7)
    at Object.<anonymous> (/opt/VSCode-linux-ia32/resources/atom.asar/browser/lib/init.js:132:4)
    at Module._compile (module.js:434:26)
    at Object.Module._extensions..js (module.js:452:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:475:10)
    at startup (node.js:130:18)
    at node.js:982:3

Likely an electron issue...

@bpasero there were 2 reports in like 24 hours, electron wasn't touched recently was it?

@Tyriar no

Filed https://github.com/atom/electron/issues/4705 to get some more insights from Electron.

Another case https://github.com/Microsoft/vscode/issues/3737, they all seem to be on Ubuntu 12.04.

@isomorphisms @Tyriar  According to electron: Electron needs to write to $XDG_CONFIG_HOME/APP_NAME, this error happens when users don't have permission to create or write to that directory. please make sure you have the permissions.
We should probably add this to our FAQ. @gregvanl fyi

I just did:
sudo rm -r -f ~/.cache
I don't know if it was the best solution at all, but it does the trick...


Web socket deployment issue after new version creation

Description
Error encountered while deploying a newly created version of a WebSocket API.
Another error is encountered when attempting to update endpoints of the new version of the API.
Steps to Reproduce

Start APIM server
Login to the publisher portal
Create a websocket API, deploy and publish.
Create a new version of the websocket API
Press deploy
Go to endpoints in the menu and hit save button

Affected Component
APIM
Version
4.0.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response

This issue was only reproduced in the 4.0.0 pack, which was patched. Hence, closing this issue.


opencxr image standardization generates black image / png

Dataset: NIH CXR14
Input image (random selection: 00001714_000.png) :

Image after opencxr.utils.file_io.read_file:

Image directly after call to run() for algorithm "opencxr.algorithms.cxrstandardization":

Image as written out by opencxr.utils.file_io.write_file :

Sample code to reproduce :
import opencxr
import png

from pathlib import Path
from opencxr.utils.file_io import read_file as opencxr_read_file
from opencxr.utils.file_io import write_file as opencxr_write_file

pre_process_opencxr = opencxr.load("opencxr.algorithms.cxrstandardization")

dir_path = Path("my_input_dir")
target_root = Path("my_output_dir")

filename = Path("00001714_000.png")

full_cxr_file_path = dir_path / filename
img_np, spacing, dcm_tags = opencxr_read_file(str(full_cxr_file_path))
png.from_array(img_np.copy(), mode="L").save(target_root / f"DEBUG_PRE_{filename}")
# Do standardization of intensities, cropping to lung bounding box,
# and resizing to 1024 square
std_img, new_spacing, size_changes = pre_process_opencxr.run(
    image_np=img_np, spacing=spacing, do_crop_to_lung_box=False
)
output_cxr_loc = (
    f"{target_root}/OUT_{filename}"
)

png.from_array(std_img.copy(), mode="L").save(target_root / f"DEBUG_POST_{filename}")
print(f"Writing to: {output_cxr_loc}")
opencxr_write_file(output_cxr_loc, std_img, new_spacing)

Notes:

All 112120 images in the NIH CXR dataset are generated as black output images when applying opencxr standardization.
It doesn't look like the read_file / write_file functions are the cause since in parallel I directly wrote the images via pyng as well to compare - same image as read_file / write_file

Specifying astype('uint8') on the np array when writing generates something resembling an image:
So:
png.from_array(std_img.copy(), mode="L").save(target_root / f"DEBUG_POST_{filename}")

becomes:
png.from_array(std_img.copy().astype('uint8'), mode="L").save(target_root / f"DEBUG_POST_{filename}")

and generates:

which at least isn't entirely black.
So maybe look into opencxr.utils.file_io.write_file after all?

maybe sth like:
from math import ceil, log10
from numpy import amax
...
new_width = size_changes[0][1][0]
new_height = size_changes[0][1][1]
bitdepth = ceil(log10(amax(std_img)) / log10(2))
png_writer = png.Writer(width=new_width, height=new_height, bitdepth=bitdepth, greyscale=True)
...

... but I'm somewhat guessing on the list indexing of size_changes


Expanding Response Time tag to 3 decimals

What
Expanding to third decimal in Response Time Tag. Fixes #212
Why
Provides more insight to the response time in milliseconds rather than rounding the first decimal.
Before

After

Should add this to the PR template... Can you attach a screenshot since this touches the UI?

Screenshot added 😄

@sean3z thanks. Just added that to the PR template: https://github.com/getinsomnia/insomnia/pull/214


feat: noImplicitAny

What's the purpose of this pull request?
Strict mode in TypeScript is a way to opt into a more strict type-checking behavior to catch more potential issues at compile time. When enabled, it activates a set of stricter type-checking options that enforce more constraints on your code. Here's how it works and what it does:
No Implicit Any (noImplicitAny): This prevents variables and parameters from defaulting to the any type when TypeScript is unable to infer a more specific type. This helps catch cases where you might have forgotten to specify a type or TypeScript can't infer one for you.
To enable strict mode, you can set "strict": true in your tsconfig.json file. This is equivalent to enabling all of the above options individually.
The idea of this initiative is to enable rule by rule incrementally so that it is possible to open smaller PRs with low risk.
Task: https://vtex-dev.atlassian.net/browse/SFS-1124
How it works?
The first PR enables noImplicitAny rule. So codes like that will not work:
What's the type of address?
function printAddresss(address) {
    console.log(address)
}

How to test it?

The pipeline (build, tests, and lint) should work for @faststore packages and their dependencies (current branch).

Install the version of this PR in the starter.store and test if the build, tests and override feature works.

"@faststore/core": "https://pkg.csb.dev/vtex/faststore/commit/1b7aa312/@faststore/core"
"@faststore/cli": "https://pkg.csb.dev/vtex/faststore/commit/1b7aa312/@faststore/cli",
I welcome other suggestions and help with testing 🥇
Starters Deploy Preview

References

Team (small change). I changed from ts-expect-error to ts-ignore because ts-expect-error generates an error when the line has no error. In other words, it always expects the line to have an error. However, when I disable noImplictyAny, the lines stop having errors within the .faststore.


Linux 5.9.5 on arm32: Device did not provide ANY valid caps. Refusing playback.

Hi,
after updating my system to Linux 5.9.5, GLIBC_2.30 and tiscamera 0.12.0 tcamsrc is unable to get any caps from my camera and therefore fails:
root@host:~# GST_DEBUG=tcamsrc:9 gst-launch-1.0 tcamsrc serial="08810319" type="v4l2" ! fakesink
0:00:00.172613333  4585  0x1bc4c20 INFO                 tcamsrc gsttcamsrc.cpp:1769:gst_tcam_src_init: Versions:
        Tcam:   0.12.0_master/2ce3ee84_rev_2777
        Aravis: not_configured_version_not_configured
0:00:00.173013667  4585  0x1bc4c20 INFO                 tcamsrc gsttcamsrc.cpp:1824:gst_tcam_src_set_property: Set camera name to 08810319
0:00:00.173197000  4585  0x1bc4c20 DEBUG                tcamsrc gsttcamsrc.cpp:1250:gst_tcam_src_init_camera:<tcamsrc0> Initializing device.
0:00:00.173283333  4585  0x1bc4c20 DEBUG                tcamsrc gsttcamsrc.cpp:1266:gst_tcam_src_init_camera: Opening device. Serial: '08810319 Type: 'unknown'
0:00:00.213954333  4585  0x1bc4c20 DEBUG                tcamsrc gsttcamsrc.cpp:764:gst_tcam_src_get_all_camera_caps: Found 0 pixel formats
0:00:00.214065333  4585  0x1bc4c20 ERROR                tcamsrc gsttcamsrc.cpp:770:gst_tcam_src_get_all_camera_caps: Device did not provide ANY valid caps. Refusing playback.
0:00:00.214180667  4585  0x1bc4c20 INFO                 tcamsrc gsttcamsrc.cpp:774:gst_tcam_src_get_all_camera_caps: Device provides the following caps: EMPTY
0:00:00.214341333  4585  0x1bc4c20 DEBUG                tcamsrc gsttcamsrc.cpp:1859:gst_tcam_src_set_property: Setting device type to v4l2
0:00:00.221217333  4585  0x1bc4c20 INFO                 tcamsrc gsttcamsrc.cpp:1000:gst_tcam_src_get_caps: Available caps = EMPTY
0:00:00.221402667  4585  0x1bc4c20 INFO                 tcamsrc gsttcamsrc.cpp:1000:gst_tcam_src_get_caps: Available caps = EMPTY
0:00:00.221713000  4585  0x1bc4c20 INFO                 tcamsrc gsttcamsrc.cpp:1000:gst_tcam_src_get_caps: Available caps = EMPTY
0:00:00.222046667  4585  0x1bc4c20 INFO                 tcamsrc gsttcamsrc.cpp:1000:gst_tcam_src_get_caps: Available caps = EMPTY
WARNING: erroneous pipeline: could not link tcamsrc0 to fakesink0
root@host:~# uname -a
Linux host 5.9.5-1 #1 SMP PREEMPT Thu Nov 5 22:27:38 UTC 2020 armv7l armv7l armv7l GNU/Linux
root@host:~# dmesg | tail
[   97.940945] usb 1-1.4: new high-speed USB device number 4 using ci_hdrc
[   99.633323] usb 1-1.4: New USB device found, idVendor=199e, idProduct=8307, bcdDevice= 8.13
[   99.633349] usb 1-1.4: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[   99.633364] usb 1-1.4: Product: DFM 5U2-SKIDATA-2.9MM
[   99.633377] usb 1-1.4: Manufacturer: SKIDATA
[   99.633390] usb 1-1.4: SerialNumber: 08810319
[   99.634974] uvcvideo: Unknown video format 4c545250-0000-0010-8000-00aa00389b71
[   99.635021] uvcvideo: Found UVC 1.03 device DFM 5U2-SKIDATA-2.9MM (199e:8307)
[  100.144136] uvcvideo: Failed to query (GET_INFO) UVC control 4 on unit 1: -110 (exp. 1).
[  100.651919] input: DFM 5U2-SKIDATA-2.9MM as /devices/platform/soc/2100000.bus/2184200.usb/ci_hdrc.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input3

If more information is needed please come back to me!
Any help is greatly appreciated.
regards;rl

Hi,
do you have any information/news on this problem?
Or is there anything I should try?

Hallo
I missed your issue somehow, I am sorry. In between we updated tiscamera to 0.13.0 You may try that.  The save way of rebuilding is
cd tiscamera/build
gige-daemon stop
sudo make uninstall
git pull
rm * -rf
cmake -DBUILD_ARAVIS=OFF ..
make -j 32
sudo make install

Please come back to me, if the error stays.
Stefan

Hi @TIS-Stefan,
using tiscamera v0.13.0 on a Linux 5.9.10 works again!
Thank you!


Not working for me on raspberry pi

  ~  _magic_enter:10: exec format error: eza                                           adrian 
_list_files_here:8: exec format error: eza
_list_files_here:12: command not found: #

       _,met$$$$$gg.          adrian@caladan
    ,g$$$$$$$$$$$$$$$P.       --------------
  ,g$$P"     """Y$$.".        OS: Debian GNU/Linux 12 (bookworm) aarch64
 ,$$P'              `$$$.     Host: Raspberry Pi Zero 2 W Rev 1.0
',$$P       ,ggs.     `$$b:   Kernel: 6.6.31+rpt-rpi-v8
`d$$'     ,$P"'   .    $$$    Uptime: 2 hours, 3 mins
 $$P      d$'     ,    $$P    Packages: 762 (dpkg)
 $$:      $$.   -    ,d$$'    Shell: zsh 5.9
 $$;      Y$b._   _,d$P'      Resolution: 1024x768
 Y$$.    `.`"Y$$$$P"'         Terminal: /dev/pts/0
 `$$b      "-.__              CPU: (4) @ 1.000GHz
  `Y$$                        Memory: 71MiB / 417MiB
   `Y$$.                      Disk (/): 2.6G / 6.8G (41%)
     `$$b.
       `Y$$b.
          `"Y$b._
              `"""

do you have eza installed?

do you have eza installed?

I did but the version I installed is problematic (had no --git), I'm building from source, will report back when the raspberry pi zero 2 w finishes... 🐌

@chrisgrieser works on my mac, couldn't install eza with --git on the raspberry pi unfortunately, may run a custom version of you script on the pi, many thanks.


WebSockets support

Is your feature request related to a problem? Please describe.
WebSockets enable a whole set of real-time web applications, which look like great candidates for async web servers. It should be as easy to build a backend websocket server than it is to create a websocket client in the frontend world.
Describe the solution you'd like
Implement a friendly, async/await-based interface for building websocket views, which would allow to write something like:
import json
from bocadillo import API, WebSocket

api = API()

@api.websocket_route("/chat", value_type="json")
async def chat(ws: WebSocket):
    async with ws:
        # The connection has been accepted.
        async for message in ws:
            await ws.send({"type": "echo", "message": message})
        # Connection closes when leaving this block.
    # The client has disconnected normally. Perform extra cleanup if needed.

The async for syntax should just be a shortcut for a while True loop that repeatedly calls receive_<value_type>() on the WebSocket object.
The async with syntax allows to automatically accept() and close() the WebSocket.

It should catch Disconnect exceptions with normal close codes (1000 or 1001).
It should be possible to customize which close codes are silenced, e.g. with a caught_close_codes: Tuple[int] argument.
In case of an unknown exception, the connection should be closed with a 1011 (Unexpected Error) code.

value_type=X is a shortcut for receive_type=X, send_type=X. Possible values are ["text", "json", "bytes", "event"].

Note: with the syntax above, hooks do not have to be ported to WebSockets. The developer can perform any operation before/after the context enters/exits.
For the implementation, this feature should mostly be a wrapper around Starlette WebSockets.
Describe alternatives you've considered

Starlette's WebSocketEndpoint uses a callback style which is not consistent with the rest of the Bocadillo API.

Additional context
Came to this conclusion while thinking about example projects for a tutorial. :)

@cs01 Thanks for the heads up! I was interested in that thumbsup you left on the issue, my questions are now answered. ;-) Looking forward to seeing Bocadillo + WebSockets in action in pyxterm.js once we roll this feature out. :+1:

In the back of my mind I was thinking of using it on https://github.com/cs01/gdbgui, but that would be a much bigger undertaking. I realized today that a good first step would be pyxterm.js.

Yep, that's a smart move. Better to start with a proof of concept than putting the stability of a 6k+ star project at risk.

Great work, can’t wait to try it out.

Update: v0.9 has just been released :wink: https://pypi.org/project/bocadillo/0.9.0


Installation instruction

I tried to follow the instruction, but running 'ant' seems to do nothing.
I did :
clone the two required repositories,
checkout zeromq branch for both,
run ant in hyperledger-bftsmart,
then I ran launch4Replicas.sh with an error saying bft.BFTNode is not found.
What am I missing?

Did the ant command get to create a ./dist folder with the compiled jar inside? If so, try running these commands instead (one for each different replica):
java -cp dist/BFT-Proxy.jar:lib/* bft.BFTNode 0 10 /msp/sampleconfig/signcerts/peer.pem /msp/sampleconfig/keystore/key.pem 1000,2000
java -cp dist/BFT-Proxy.jar:lib/* bft.BFTNode 1 10 /msp/sampleconfig/signcerts/peer.pem /msp/sampleconfig/keystore/key.pem 1000,2000
java -cp dist/BFT-Proxy.jar:lib/* bft.BFTNode 2 10 /msp/sampleconfig/signcerts/peer.pem /msp/sampleconfig/keystore/key.pem 1000,2000
java -cp dist/BFT-Proxy.jar:lib/* bft.BFTNode 3 10 /msp/sampleconfig/signcerts/peer.pem /msp/sampleconfig/keystore/key.pem 1000,2000

Thanks, at least I was able to pass that stage


docker inspect -f uses floats instead of ints

It seems that the data type of all numbers in docker inspect data is floats, rather than ints.
For example, the following template fails:
$ docker inspect -f '{{eq .State.ExitCode 0}}' jenkins-data
FATA[0000] template: :1:2: executing "" at <eq .State.ExitCode 0>: error calling eq: incompatible types for comparison

But this one works:
$ docker inspect -f '{{eq .State.ExitCode 0.0}}' jenkins-data
true

The same seems to be true for all numbers. This is obviously quite confusing, as pretty much all the numbers would seem to be better represented as integers.
Could this be changed? I realise there is now an issue with backward compatibility, but it just seems ... wrong ...
Version data and stuff if needed:
adrian@bistromath:/tmp/dockerfile$ docker version
Client version: 1.5.0
Client API version: 1.17
Go version (client): go1.4.1
Git commit (client): a8a31ef
OS/Arch (client): linux/amd64
Server version: 1.5.0
Server API version: 1.17
Go version (server): go1.4.1
Git commit (server): a8a31ef
adrian@bistromath:/tmp/dockerfile$ docker info
Containers: 21
Images: 933
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 979
Execution Driver: native-0.2
Kernel Version: 3.13.0-32-generic
Operating System: Ubuntu 14.04.1 LTS
CPUs: 8
Total Memory: 5.82 GiB
Name: bistromath
ID: VFBH:SEDU:FTHB:6WGM:JMH5:EWPQ:SQ6X:WQEC:JFGP:S2RD:5VZN:7FJW
Username: amouat
Registry: [https://index.docker.io/v1/]
WARNING: No swap limit support
adrian@bistromath:/tmp/dockerfile$ uname -a
Linux bistromath 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

#dibs

@scalixte-mdsol I already worked on this. Please see the PR above.

@brahmaroutu when you do a PR, can you please add fixes or closes keyword to it? Thanks!

@rrarunan Does it not say Closes?

@brahmaroutu It was just a friendly reminder without looking at the PR themselves. You did good :+1:


Add binary Hamming distance to custom scoring

The Hamming distance measures the number of positions that are different between 2 equal length sequences of characters. This feature will look to support Hamming distance for binary sequences within the custom scoring logic.
A user should be able to ingest documents that have a term that can be interpreted as binary data and then apply the k-NN custom scoring script in order to get the k most similar results based on this distance metric. In order to implement this, we will need to determine which Elasticsearch types we will use to represent binary data. For instance, Elasticsearch has the binary field type, that uses Base64 encoded values. We will also look into supporting integral types (long, int, short, byte) and their related arrays. These may offer performance improvements over Base64.
Additional enhancements to this feature include supporting fixed radius nearest neighbor search, which will return all documents that fall within a certain radius of the query data.

i see there is space_bit_hamming in nmslib. is there any possible use this space in k-NN?

Hi @luyuncheng I think we could investigate adding that functionality. Because this issue is dedicated to adding Hamming distance in custom scoring, I am going to close it. Could you please open a separate issue for integrating nmslib's hamming bit space into the plugin?


Add cast to objective C convenience initializers to prevent naming co…

In generated Objective C code, convenience initializers can easily cause naming collisions with built in ios functions and other code that follows the same naming pattern.  As a trivial example, consider the following record:
MyColor = record {     red : f32;     green : f32;     blue : f32;     alpha : f32; } deriving( eq )
This produces a function that looks something like this:
 (nonnull instancetype)MyColorWithRed:(float)red { (nonnull instancetype)MyColor:(float)red                                    green:(float)green                                     blue:(float)blue                                    alpha:(float)alpha {     return [[self alloc] initWithRed:red                                                 green:green                                                  blue:blue                                                 alpha:alpha]; } }
If your project happens to include UIKit, this generated code will emit a compilation error because InitWithRed is defined in UIKit (see https://developer.apple.com/documentation/uikit/uicolor/1621925-initwithred?language=objc) and without qualification, the call is ambiguous.
Adding a cast to the generated code disambiguates the call to initWithRed (and other similar situations)

Hi, @wpurdy2:
I noticed you haven't signed the CLA yet, could you please sign it here: https://opensource.dropbox.com/cla/
Thanks a lot!


Privacy Policy and TOS to Render from Markdown from Existing URLs

The only time our MarkdownTemplateView gets triggered is when the URL matches ^markdown/(?P.+)/? - but for the privacy policy and TOS, we want them to have normal paths - and the StaticContentTemplateView is already a catch-all where no "markdown" folder would be needed.
Rather than try to either create some intermediary view which would make a determination, or modify the StaticContentTemplateView itself to somehow accommodate it, I'm creating a custom argument to the MarkdownTemplateView for 'markdown_local' which will look for the MD source in templates/markdown.
Possibly something to have someone take a look at in the future, and let me know what might be a better practice, but this seems to be working fine.
This was necessary since the new versions of the content for these pages was provided in markdown format - and I don't believe these are files we would want anyone to have the ability to contribute edits to.  (but- going to ask about that now, and if so, new issue shall come)

Also added frontmatter into the MD files for setting page title.  Left description and author blank.


Bug - Browse Job page - job card - duration info missing

Description
Duration info is missing on job cards on the browse job page. The info is showing on individual posters.
Images
Place image attachments here.

[ ] Regression test written.

hi @joshdrink, just want to flag this to you

Hey Rosita,
I'm having Chris look at this. I'll let you know when things have been
fixed.
Thanks!
Josh Beveridge
Digital Product Designer | Concepteur de produits numériques
@joshdrink https://twitter.com/joshdrink | https://joshbeveridge.ca/
On Wed, Nov 13, 2019 at 5:18 PM rositak<EMAIL_ADDRESS>wrote:

hi @joshdrink https://github.com/joshdrink, just want to flag this to
you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GCTC-NTGC/TalentCloud/issues/2041?email_source=notifications&email_token=ABVDKAW44VP2IDHCPJZGRFLQTR4JZA5CNFSM4JNCNRBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED73WCI#issuecomment-553630473,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVDKAXHG4VTJIHH6OGULCLQTR4JZANCNFSM4JNCNRBA
.

@Khristophor @joshdrink Any insights on this?

It's fixed, awaiting PR merge


fix #1536, support storm ack

this approach is like a state application, making using of CheckpointClock at ClockService.
Bolt tasks periodically report an acked timestamp to ClockService.
Spout tasks periodically poll the global CheckpointClock and ack the pending messages in a batch way.

I don' think this approach will ever work.
How about this, we keep one message with min-timestamp pending, and ack success all rest messages.
For example, for mesage sequence....
1, 2, 3 ,4, 5, 6, 7, 8, 9, 10, 11,
We keep message 1 pending, (neither success nor fail)
and ack message 2, 3,4, 5,6,7,8,9,10,11 as success.
when we confirm all subsequent mssages are all processed, we ack 1 as success, and choose a new pending message.
In this way, there is also 1 pending message for each spout, solving the memory issue.

When there is message loss, we will recover from the offset of the pending message, which is older than message 2,3 ,4,5,6,7,....
So, all subsequent messages are replayed.

This only works for persistent spout with two characteristics:

replayable.   which means we are able to replay messages if there is any loss.
sequential, which means we are able to replay all messages after the lost messages.

So, we should propoably warn user during the DAG submission stage for cases like:

if we are sure at-least-once cannot be supported.
If we are not sure at-least-once can be supported.

The ack and fail must be called with meanfully message id, even if we don't support exacly-once.
Otherwise, there is possble memory leak inside implementation of Spout.

which one do you mean ? The acked MessageId is passed from Spout.

How you handle failure? How you notify spout there are failures?
I don't know how at least once is working

The at-least-once works like this now,
With ack enabled by user, StormProducer keeps one pending message for Spout (sequentially replayable) along with its message time and start time and acks immediately for other messages (as you proposed).

On Bolt.ack, each StormProcessor periodically reports the acked timestamp (it's guaranteed there will be no more messages before this timestamp to be acked) to ClockService.
StormProducer periodically polls the global minimum checkpoint clock and acks Spout if the pendng message time is <= checkpoint clock.
if timeout is enabled, StormProducer will fail Spout if the pending message has expired
On Bolt.fail and other exceptions, Gearpump will restart applications and the Spout will replay from the last committed message.

The limitations are

if there is data skew (like in wordcount), a StormProcessor may not receive any messages and won't report its checkpoint clock. Then, the global checkpoint clock can't make progress.
we are not able to warn at topology submission stage whether at-least-once is supported since spout is in serialized form and its Class is not on the client class path.

+1
Make sure you  have done some perfomance test on this.

thanks, I can rest in piece now.

Can you check the build failure?

looks irrelevant to this pr
[info] HadoopCheckpointStoreIntegrationSpec:
[info] - HadoopCheckpointStore should persist and recover checkpoints *** FAILED ***
[info]   InvalidEscapeException was thrown during property evaluation.
[info]     Message: invalid escape character at index 12 in "checkpoints-\"
[info]     Occurred when passed generated values (
[info]       arg0 = 100 // 4 shrinks
[info]     )

opened #1582 for the spec failure

Merge this such that the integration test won't be blocked. I'll open follow up PRs if finding any bugs or performance issues.


fix: Collect usage statistic showing twice

Description
When running the very_good_cli for the first time it asks if it can collect usage statistics. If you say yes then it will output the exact message once more.
Steps To Reproduce

Install the very_good_cli from clean (tested it with v0.6.0)
Run a very_good create command
When asked if it can collect data say yes.
It outputs the same message again and continues.

Expected Behavior
That it will only show the message asking to collect data once, before answering and not again after answering the question.
Screenshots

Additional Context
I did run it on dart version 2.15.1 by accident but I was able to reproduce it after updating and clean installing the tool.

Terminal: bash v5.1.8
OS: pop-os 21.10

Hi @wolfenrain 👋
Thanks for opening an issue!
Are you able to provide more context regarding what OS you're running on? Also, can you confirm that other commands only execute once? The reason I ask is because there have been similar issues reported like https://github.com/leoafarias/fvm/issues/227 and https://github.com/VeryGoodOpenSource/very_good_cli/issues/121.

Hi @wolfenrain wave Thanks for opening an issue!
Are you able to provide more context regarding what OS you're running on? Also, can you confirm that other commands only execute once? The reason I ask is because there have been similar issues reported like leoafarias/fvm#227 and #121.

The commend itself ran only once, it also only happened after I gave an answer.
I am currently running it on Linux, pop-os 21.10

So I managed to reproduce this inside a Docker container, while that obviously does not fully reflect any working environment the problem itself is consistent on my Linux machine so I suspect this is a Linux + Bash problem?
Might still be a problem specific to the terminal emulator that is being used, can't test that right now.

Run docker run -ti dart:2.16.1 /bin/bash to start a container with Dart v2.16.1 and with bash as the shell. PS: I did test other versions of Dart as well and they all resulted in the same outcome.
Install the CLI: dart pub global activate very_good_cli
The container does not have proper PATH variables for Dart so just run it from the cache: .pub-cache/bin/very_good
The question pops up, press y and enter.
The question pops up again, so it now shown twice and the answer you gave is below that. Rest works as expected the help is visible.

Might still be a problem specific to the terminal emulator that is being used, can't test that right now.

This is no uncertain, I have followed these steps on my intel macbook and got exactly the same results. So either the stdout writing is going haywire (based on a quick assessment of the code for this I would assume that it is not the case) or the CLI and Bash/Linux aren't the greatest friends (yet).

Based on this method I wrote up a simple test file to see if the problem is reproducible in a simplere case.
The test I wrote up ran in a Docker VM on Dart 2.16.1, I initially just used the stdout and stdin from dart:io:
import 'dart:io';

void main() {
  const message = 'testing this';
  stdout.write(message);

  stdin.readLineSync()?.trim();

  stdout.writeln('\x1b[A\u001B[2K$message with result');
}

This does not result in the problem describe above. So I took a quick look at the universal_io, expected it to just reexport dart:io but it seems they have their own implementation of stdio, and it seems to be a full copy, based on the license at the top, from the dart stdio one.
So considering that it is working without universal_io as expected I suspect the problem might lie somewhere in their implementation.

Based on this method I wrote up a simple test file to see if the problem is reproducible in a simplere case.
The test I wrote up ran in a Docker VM on Dart 2.16.1, I initially just used the stdout and stdin from dart:io:
import 'dart:io';

void main() {
  const message = 'testing this';
  stdout.write(message);

  stdin.readLineSync()?.trim();

  stdout.writeln('\x1b[A\u001B[2K$message with result');
}

This does not result in the problem describe above. So I took a quick look at the universal_io, expected it to just reexport dart:io but it seems they have their own implementation of stdio, and it seems to be a full copy, based on the license at the top, from the dart stdio one.
So considering that it is working without universal_io as expected I suspect the problem might lie somewhere in their implementation.

Hmm that's interesting! Thanks for looking into it. Are you planning to try swapping out dart:io with universal_io in your example to see if you're able to reproduce?

Yes I already tried, but it was throwing some segmentation errors when I tried to run the file in Docker 😅 , but I can give it another go later today.

This should be resolved now. Developers should be able to just re-activate very_good_cli to get the latest release of package:mason_logger which includes the fix 🎉


Can we add a button to upload images directly into the editor?

same for video as well

Yes you can do that.
Please check this thread
https://github.com/modbender/nuxt-tiptap-editor/issues/6


[Bug]: class used instead of className and console.log messages still found

What happened?
I found a BUG 🐞
Add screenshots
Add screenshots

What browsers are you seeing the problem on?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@VenomFate-619 pls assign this issue to me

@VenomFate-619 I just made a PR ->  #corrected class error-messages


Wakeup timeouts in failing tests

Hi, not sure this is tied to the library or somehow to the client used for tests.
Our test suites fail quite regularly if we configure timeouts for our kafka consumer (which uses the akka-stream-kafka library) as follows:
  wakeup-timeout = 1s
  max-wakeups = 5

I have no stack-trace to provide, but the log errors are
[ERROR][2017-04-07 10:12:52,819][akka.kafka.KafkaConsumerActor]WakeupException limit exceeded, stopping.
[ERROR][2017-04-07 10:12:52,820][akka.kafka.KafkaConsumerActor]WakeupException limit exceeded, stopping.
[ERROR][2017-04-07 10:12:52,820][akka.kafka.KafkaConsumerActor]WakeupException limit exceeded, stopping.
[ERROR][2017-04-07 10:12:52,820][akka.kafka.KafkaConsumerActor]WakeupException limit exceeded, stopping.
[ERROR][2017-04-07 10:12:52,820][akka.kafka.KafkaConsumerActor]WakeupException limit exceeded, stopping.
[ERROR][2017-04-07 10:12:53,911][akka.kafka.KafkaConsumerActor]WakeupException limit exceeded, stopping.

If somehow it comes out that the error is not related to the library, I'll escalate to the kafka-stream project.

I had a similar problem with the wakeup-timeout. Honestly I don't think this is library related but I'll have a look anyway.


HHH-14921 + HHH-14922 Definition of the default catalog/schema on session factory creation

HHH-14922: Inconsistent precedence of orm.xml implicit catalog/schema over "default_catalog"/"default_schema"
HHH-14921: Definition of the default catalog/schema on session factory creation

This should allow us to change the catalog/schema in "runtime" settings in Quarkus: https://github.com/quarkusio/quarkus/issues/19660
I am currently working on porting this to the 6.0 branch. It's going to take some time, considering the size of this patch.

130 changed files and every build fails.  Mine had 5 files changed and all builds passed.  Why did you supersede mine?

I created a version of my PR targetting main - https://github.com/hibernate/hibernate-orm/pull/4354
IMO that should superseded this PR at least as far as HHH-14922 is concerned.  I think we should include your work for HHH-14921 and tests on top of https://github.com/hibernate/hibernate-orm/pull/4354

130 changed files

Yes, that's unfortunate, but this is to address HHH-14921: Definition of the default catalog/schema on session factory creation, which is unfortunately a much complex problem.

every build fails

Having a look right now. It passed locally... :/

Why did you supersede mine?

First, because your PR didn't pass the integration tests I'm adding in this PR (very first commit). I think I explained that on Zulip, shortly.
Second, because I need a fix in 5.x, not 6.0.
But more importantly, because my actual goal is to address HHH-14921, and THAT (much more complex) patch will require a completely different solution for HHH-14922, unfortunately.
Let's discuss this on Zulip.

Alright, we decided to go with this PR for now and apply Steve's improvements after this PR has been merged, if he has time.
@sebersole @beikov @dreab8 could someone please approve this PR?
I have a port ready for 6.0: https://github.com/hibernate/hibernate-orm/pull/4371. So in order to merge main into 6.0, we'll just need to create a local branch where we revert all commits from this PR, then merge; then we can apply my port.
Thanks.

For the record, I got the approval for merging on Zulip: https://hibernate.zulipchat.com/#narrow/stream/132094-hibernate-orm-dev/topic/Default.20and.20implicit.20schema/near/263869953
Will merge when CI jobs go green.


multiprocess and dill cannot transfer objects in main script, giving KeyError: 'main'

Problematic package: https://github.com/uqfoundation/multiprocess
Description: multiprocess is a fork of multiprocessing which uses dill instead of pickle for sharing objects between processes which causes significant improvements when it comes to sharing or passing objeccts to processes. In my case the application requires it becasue we share a lot of complex objects between our processes, and it simply is not workable with the regular multiprocessing implementation.
After compiling and starting the excecutable via CMD, we get:
Traceback (most recent call last):
  File "C:\Users\chwba\PYCHAR~1\NUITKA~3\APP~1.DIS\app.py", line 21, in <module __parents_main__>
  File "C:\Users\chwba\PYCHAR~1\NUITKA~3\APP~1.DIS\multiprocessing\spawn.py", line 74, in freeze_support
  File "C:\Users\chwba\PYCHAR~1\NUITKA~3\APP~1.DIS\multiprocessing\spawn.py", line 116, in spawn_main
  File "C:\Users\chwba\PYCHAR~1\NUITKA~3\APP~1.DIS\multiprocessing\spawn.py", line 126, in _main
  File "C:\Users\chwba\PYCHAR~1\NUITKA~3\APP~1.DIS\__init__.py-postLoad", line 29, in _create_compiled_function3
KeyError: '__main__'

Compiled executable: https://nextcloud.mnwd.in/s/t4xHomW8GBQKwY9
Compilation log: https://nextcloud.mnwd.in/s/rZKNoYPLTn8qb6E
Compiled with:
python -m nuitka --follow-imports^
                 --show-progress^
                 --show-scons^
                 --warn-unusual-code^
                 --assume-yes-for-downloads^
                 --warn-unusual-code^
                 --plugin-enable=pylint-warnings^
                 --plugin-enable=multiprocessing^
                 --plugin-enable=dill-compat^
                 --standalone^
                 --msvc=14.2^
                 app.py > compile.log

(Tested with clang and msvc=14.2, with and without multiprocessing plugin/dill-compat)
Code snippet to reproduce:
from time import sleep
from multiprocess import Process, freeze_support

def do_work():
	print("working..")
	sleep(3)

def main():
	p = Process(target=do_work)
	p.start()

if __name__ == "__main__":
	freeze_support()
	main()

Used requirements:
multiprocess

Nuitka
0.6.13
Python: 3.9.2 (tags/v3.9.2:1a79785, Feb 19 2021, 13:44:55) [MSC v.1928 64 bit (AMD64)]
Executable: C:\Users\chwba\PycharmProjects\nuitka_mp_pickling_error\venv\Scripts\python.exe
OS: Windows
Arch: x86_64

(Installed via python -m pip install nuitka)

The dill plugin of Nuitka might exist only because of this package you are using there. It may also have been another one, but they are all similar I guess. Can you try if it works moved outside of __main__ as that is a special case with multiprocessing, which would only have __parents_main__ (spelling). For normal modules it ought to work, does it?

Its not possible to call freeze_support outside of __main__, as described in the official documentation of multiprocessing (https://docs.python.org/3/library/multiprocessing.html#multiprocessing.freeze_support), which also applies for multiprocess multiprocess.

@chwba then you have that and only that on main and call somewhere_else.main() from another file.

Sorry, but im not sure I understand..... I have to create a separate file to call my main?

I am saying that dill might work everywhere but in the main script.
There is something fishy about __main__ as a module, it's not really one, so things have to take special action to work there, and the bug in Nuitka is only that. Still worth fixing, but you got a workaround clearly. Few people put their code in the main script, indeed it's often generated and only doing roughly what yours is doing now.
And the error would relate to the dill support only. I think it may be as easy as mapping __main__ to __parents_main__ or whatever it is in forks and vice versa. Very ugly, but true. I probably need to revisit this, it's also ugly in poluting every module code, even if not being active as a plugging. With a workaround like that though, it's not an immediate priority.

Should probably leave a note about this in the docs as the official documentation of multiprocessing will be misleading for anyone running into this one.

This works as expected nowadays


Exports is not defined in ES module scope

Hello 👋
thank you for this library, it's really helpful for our use case.
We recently updated monaco to 0.45 and received to following error afterwards

any idea what's wrong here?
It's a NextJS project using pretty much the default tsconfig. Here are some relevant dependencies:
"monaco-editor": "0.45.0",
"emmet-monaco-es": "5.3.0",
"@monaco-editor/react": "4.6.0",

kind regards

It seems you are using the cjs version for esm import, should related to package.json I think.    I'll figure it out later

@troy351 did you by any chance have time to look into this?

Could you provide a repro?
I'm not familiar with NextJS

@troy351 here's a reproduction https://stackblitz.com/edit/stackblitz-starters-5m53c2?file=pages%2Findex.tsx


questioN regarding faceted calssification

i know this does metrics, but under the hood does it essentially do faceted classification?

Hi
Sorry, I don't understand your question...

Faceted classification is a type on indexing, and allows thing like how Amazon search works with th facets on the left side.
These guys explain it better than me:
http://clojureelasticsearch.info/articles/facets.html

Facette is really only a time series front-end, it fetches datapoints from storage backends (RRDtool, Graphite etc.) and renders them on charts... It has nothing to do with search :)

Thanks.
Is this code base usable.
I have a data lake of data and am looking for a way to visualise it, but
also run computations on it to get metrics out.
On Fri, 19 Feb 2016, 17:11 Marc Falzon<EMAIL_ADDRESS>wrote:

Facette is really only a time series front-end, it fetches datapoints from
storage backends (RRDtool, Graphite etc.) and renders them on charts... It
has nothing to do with search :)
—
Reply to this email directly or view it on GitHub
https://github.com/facette/facette/issues/292#issuecomment-186280395.


Fix heading tag styling

Description

Fixes broken README styling, doesn't change any other code!
TESTING STAGE

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] I have read CONTRIBUTING.md
[x] I fully understand Github Flow.
[x] My code adheres to the code style of this project.
[x] I have updated the documentation in /docs if I have changed the config, arguments, logic in how the bot works, or anything that understandably needs a documentation change.
[x] I have updated the config file accordingly if my change requires a new configuration setting or changes an existing one.
[x] I have tested the bot with no issues for 24 continuous hours. If issues were experienced, they have been patched and tested again.

@ckcollab thanks.


Try to move tensorflow lite micro build inside of the microlite module

I'm getting linker errors when trying to combine the libtensorflow-microlite.a as built by ci: https://github.com/mocleiri/tensorflow-micropython-examples/actions/workflows/build_tensorflow_arm.yml
I think there is a difference between the toolchain used to build the static library and the firmware.
Lets try to use the create_tflm_tree.py script to generate the tensorflow lite micro files within the microlite module.
micropython needs the files to be called .cpp instead of .cc which is what tensorflow uses so we will have to transform the files into the .cpp naming.  If we can find a way to do it in the python generation script we should up stream it for others or maybe use a bit of shell scripting to do the transform.
arm-none-eabi-ld: /usr/bin/../lib/gcc/arm-none-eabi/10.2.1/../../../../arm-none-eabi/lib/thumb/v7e-m+dp/hard/libstdc++.a(new_op.o): in function `operator new(un
signed int)':
new_op.cc:(.text._Znwj+0xc): undefined reference to `malloc'
arm-none-eabi-ld: /usr/bin/../lib/gcc/arm-none-eabi/10.2.1/../../../../arm-none-eabi/lib/thumb/v7e-m+dp/hard/libstdc++.a(vterminate.o): in function `__gnu_cxx::
__verbose_terminate_handler()':
vterminate.cc:(.text._ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x42): undefined reference to `fwrite'
arm-none-eabi-ld: vterminate.cc:(.text._ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x50): undefined reference to `fputs'
arm-none-eabi-ld: vterminate.cc:(.text._ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x5e): undefined reference to `fwrite'
arm-none-eabi-ld: vterminate.cc:(.text._ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x68): undefined reference to `free'
arm-none-eabi-ld: vterminate.cc:(.text._ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x76): undefined reference to `fputs'
arm-none-eabi-ld: vterminate.cc:(.text._ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x88): undefined reference to `fwrite'
arm-none-eabi-ld: vterminate.cc:(.text._ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x9c): undefined reference to `fwrite'
arm-none-eabi-ld: vterminate.cc:(.text._ZN9__gnu_cxx27__verbose_terminate_handlerEv+0xc0): undefined reference to `fwrite'
arm-none-eabi-ld: vterminate.cc:(.text._ZN9__gnu_cxx27__verbose_terminate_handlerEv+0xca): undefined reference to `fputs'
arm-none-eabi-ld: vterminate.cc:(.text._ZN9__gnu_cxx27__verbose_terminate_handlerEv+0xd4): undefined reference to `fputc'
arm-none-eabi-ld: vterminate.cc:(.text._ZN9__gnu_cxx27__verbose_terminate_handlerEv+0xf4): undefined reference to `_impure_ptr'
arm-none-eabi-ld: /usr/bin/../lib/gcc/arm-none-eabi/10.2.1/../../../../arm-none-eabi/lib/thumb/v7e-m+dp/hard/libstdc++.a(cp-demangle.o): in function `d_growable
_string_callback_adapter':
cp-demangle.c:(.text+0x314): undefined reference to `realloc'
arm-none-eabi-ld: cp-demangle.c:(.text+0x32e): undefined reference to `free'
arm-none-eabi-ld: /usr/bin/../lib/gcc/arm-none-eabi/10.2.1/../../../../arm-none-eabi/lib/thumb/v7e-m+dp/hard/libstdc++.a(cp-demangle.o): in function `d_append_n
um':
cp-demangle.c:(.text+0x552): undefined reference to `sprintf'
arm-none-eabi-ld: /usr/bin/../lib/gcc/arm-none-eabi/10.2.1/../../../../arm-none-eabi/lib/thumb/v7e-m+dp/hard/libstdc++.a(cp-demangle.o): in function `d_print_co
mp_inner':
cp-demangle.c:(.text+0x2b20): undefined reference to `sprintf'
arm-none-eabi-ld: cp-demangle.c:(.text+0x3c5e): undefined reference to `sprintf'
arm-none-eabi-ld: cp-demangle.c:(.text+0x3d72): undefined reference to `sprintf'
arm-none-eabi-ld: cp-demangle.c:(.text+0x3e72): undefined reference to `sprintf'
arm-none-eabi-ld: /usr/bin/../lib/gcc/arm-none-eabi/10.2.1/../../../../arm-none-eabi/lib/thumb/v7e-m+dp/hard/libstdc++.a(cp-demangle.o):cp-demangle.c:(.text+0x4
088): more undefined references to `sprintf' follow
arm-none-eabi-ld: /usr/bin/../lib/gcc/arm-none-eabi/10.2.1/../../../../arm-none-eabi/lib/thumb/v7e-m+dp/hard/libstdc++.a(cp-demangle.o): in function `__cxa_dema
ngle':
cp-demangle.c:(.text+0x5e50): undefined reference to `free'
arm-none-eabi-ld: cp-demangle.c:(.text+0x5e7a): undefined reference to `free'
arm-none-eabi-ld: cp-demangle.c:(.text+0x5e9e): undefined reference to `free'
arm-none-eabi-ld: /usr/bin/../lib/gcc/arm-none-eabi/10.2.1/../../../../arm-none-eabi/lib/thumb/v7e-m+dp/hard/libstdc++.a(del_op.o): in function `operator delete
(void*)':
del_op.cc:(.text._ZdlPv+0x0): undefined reference to `free'
arm-none-eabi-ld: /usr/bin/../lib/gcc/arm-none-eabi/10.2.1/../../../../arm-none-eabi/lib/thumb/v7e-m+dp/hard/libstdc++.a(eh_alloc.o): in function `__cxa_allocat
e_exception':
eh_alloc.cc:(.text.__cxa_allocate_exception+0x8): undefined reference to `malloc'
arm-none-eabi-ld: /usr/bin/../lib/gcc/arm-none-eabi/10.2.1/../../../../arm-none-eabi/lib/thumb/v7e-m+dp/hard/libstdc++.a(eh_alloc.o): in function `__cxa_free_ex
ception':
eh_alloc.cc:(.text.__cxa_free_exception+0x16): undefined reference to `free'
make[1]: *** [Makefile:713: /opt/tflite-micro-micropython/boards/stm32/NUCLEO_H743ZI2_MICROLITE/build/firmware.elf] Error 1
make[1]: Leaving directory '/opt/tflite-micro-micropython/micropython/ports/

I verified that both the normal build and normal build with user_c_modules worked fine.

The linker errors were related to the stm32 micropython port being bare metal so not having a standard library and all memory allocation handled by the micropython garbage collector.
Circuitpython wants us to have the tflm files integrated and compiled as part of the microlite module build.
While #31 can build a firmware there are issues preventing inference from running so internalizing and standardizing the compile options may be a way to solve the issues experienced there.


chore: update tests to use Jest instead of Mocha/Chai

Coverage remained the same at 100.0% when pulling ff8d877b27b7d9e6ef5f2b0f6ac4c777fb6ce95d on tests into 3ea79c8010cb29919980da4c744ebad925a4e3ff on master.


[SPARK-19777] Scan runningTasksSet when check speculatable tasks in TaskSetManager.

What changes were proposed in this pull request?
When check speculatable tasks in TaskSetManager, only scan runningTasksSet instead of scanning all taskInfos.
How was this patch tested?
Existing tests.

cc @kayousterhout @squito

Test build #73649 has started for PR 17111 at commit 819a5e8.

lgtm
(btw, I just meant to update your old PR to mention the new jira in the title -- you didn't have to open a new pr.  but this works too)

@squito
Thanks a lot :)

Test build #73649 has finished for PR 17111 at commit 819a5e8.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #73667 has started for PR 17111 at commit 6840ce1.

Test build #73667 has finished for PR 17111 at commit 6840ce1.

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

Merged build finished. Test PASSed.

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

Thanks for fixing this! I've merged this.

@kayousterhout
Thanks for merging.
(btw, I made some measurements for https://github.com/apache/spark/pull/16867 SPARK-16929, please take a look when you have time :) )


[Feature]: Show in terminal, time spended on compilation task

I dont't think this is possible (at least trivial), since the compilation uses vscode's Task API and not just the regular terminal

As a future note, for clang there is this flag:
-ftime-report

Implemented in #105


Mismatch of versions

The setup.py file says 1.0.43 which matches the releaee on PyPI (1.0.43) but the tag on GitHub says 1.1.43.
It would be appreciated if you could align the release numbering as for distribution packages this is sub-optimal.
Thanks

Thank you @fabaff . Done!


Fix linspace implementation

This pull request attempts to fix a potential issue in linspace implementation.
steps should be strictly greater than 1 to make it consistent with the context (namely, to make it consistent with the error message and to avoid a potential divide-by-zero/NaN).
Although this implementation of linspace is still not completely conformant to the PyTorch equivalent, for example:
torch.linspace(0.0, 1.0, steps=1)    # tensor([0.])
torch.linspace(0.0, 1.0, steps=0)    # tensor([])
torch.linspace(0.0, 1.0, steps=-1)    # RuntimeError: number of steps must be non-negative

Thanks for pointing this out, I've tweaked this PR to handle the 0 and 1 cases properly instead of just failing.


Fix several issues using selenium from docker as well as an issue rendering revisions by of revision by revision label

Closing this in favor of #134 - I have fixed some merge conflicts and should be up to date with trunk.
@aboudreault - I merged this with some flame graph stuff, can you smoke test this?

Closing this in favor of #134 - I have fixed some merge conflicts and should be up to date with trunk.


Update moot.py

changed the thing so it imports from moot_user and not mute_user

why did it fail


GOV.UK COVID content guidance request - add entries to NHS A to Z?

We've had a request from GOV.UK to add some terms from their COVID guidance (which is being closed down) to the NHS content A to Z.

[x] Also amend link to GOV Covid entry
[x] Discuss with NHS/T&T content designers working on COVID content
[x] Bring to October Content Style Council
[x] Get approval for actions from October Style Council meeting: Actions after October Style Council meeting #1812
[x] Publish COVID updates
[x] Report back to Amy at GDS

Agreed at Style Council. Need to write up minutes and get clinical sign off.

Published. We've let GOV.UK know.


powerpoint

Create powerpoint outline, to include snippets of code, showing the models, how its connected, the database, the frontend and backend and a video of it working in the end

Presentation: each presents which part they contributed in. Thorsten: docker, explicit, ML Flow.

Question: to include the work flow and how things were prioritized etc? Or to make it more like a demo?

Include which person had each role, data scientist, etc.


feat: migrate to ESM

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Pull requests should be thought of as a conversation. There will be some back and forth when trying to get code merged into this or any other project. With all but the simplest changes you can and should expect that the maintainers of the project will request changes to your code. Please be aware of that and check in after you open your PR in order to get your code merged in cleanly.
Thanks!

that's current issue:
 node index.js ./out/test
file:///Users/vl.tansky/Projects/create-html5-boilerplate/lib/cli.js:19
inquirer.registerPrompt(
         ^

ReferenceError: require is not defined in ES module scope, you can use import instead
This file is being treated as an ES module because it has a '.js' file extension and '/Users/vl.tansky/Projects/create-html5-boilerplate/package.json' contains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.
    at file:///Users/vl.tansky/Projects/create-html5-boilerplate/lib/cli.js:19:10
    at ModuleJob.run (node:internal/modules/esm/module_job:195:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:337:24)
    at async loadESM (node:internal/process/esm_loader:88:5)
    at async handleMainPromise (node:internal/modules/run_main:61:12)

Very cool. This is great.


consistency_model=mean_teacher, when you do fully supervised learning

Hi,
I saw that you're using consistency model=mean_teacher even in cases where you are doing fully supervised learning. In fact, if we look at the yml files:
table-1-cifar10-4000-fullysup.yml and table-1-cifar10-4000-mean-teacher.yml
we see that the only difference between them is on:
--hparam_string="max_cons_multiplier=0" for fully_supervised and
--hparam_string="" for the mean teacher.
Am I right on this assumption, and can you please explain me how does the model needs where to do fully_supervised vs mean_teacher?

max_cons_multiplier=0 multiplies the consistency cost (i.e., the cost on unlabeled data) by 0. So, it doesn't matter which consistency model is being used; the cost is 0 and unlabeled data is ignored.


Add Array prepend and append

First commit:

added basic specs for Array#push
used alias_method for << instead of the real definition

Second commit:

aliased push to append and unshift to prepend

Two commits as I recognize that one might be wanted and not the other (and they don't have that much in common).
About the aliases, append and prepend just seem to be the easiest names for these methods to me. I think matz once also said that he'd had named them like this but it was his English/perl at the time. I might have imagined that though.
I know we don't want too many aliases. In that case I'd actually be pro on removing push (I sort of like push though) and unshift (I really don't like unshift, always confuses me with unshift, shift).

Let's get rid of aliases: https://github.com/manastech/crystal/issues/1179#issuecomment-131267190
But it's super cool that you add specs to existing functionality that doesn't have specs, so a separate pull request will be more than welcome :-)

@asterite you want to stick to the existing names then? Personally I think append/prepend are better names for this overall - others might disagree though :)
I'll PR the specs.


Unexpected token: ...

it can not check the spread operator "..." in case it is used in a method call.
function foo(...$arg){
 // implementation
}

foo(...[1,2,3]) // this place rise an "Unexpected token: ...,  line: 5, " error

Closing, duplicate of #279


Properly pass device ID to DALI pipelines in imagenet example

This PR fixes imagenet example to properly pass device ID, where #6397 was not enough.
This change is tested in https://github.com/chainer/chainer-test/pull/495.

@okuta Would you review this? The change in #6397 was not enough.

LGTM!


Not working on iPhone 12 Pro Max

I tried to logIn on the emulator with an iPhone 12 Pro Max and it shows that the app is not configured yet, but I tried the same on an iPhone 8, iPhone 11, iPhone 12 and even iPhone 12 Pro, and it shows the Facebook login form correctly.
Just not working on iPhone 12 Pro Max specifically.
Please help. does any body know what to do?

https://github.com/roughike/flutter_facebook_login/issues/310#issuecomment-790871331


[第二組]Fix/integration test

Purpose
fix the test problem.
Changes
fix the path in tests.

Please resolve your conflict, otherwise I can't merge!


MM-37299 - invite members ab testing

Summary
This PR adds the invite members button call to action. The button will be shown in different places and with different shapes depending on the value set in the feature flag InviteMembersButton.
The options are:
sticky_button: sticked to the bottom of the left hand side panel
lhs_button: Just below of the direct messages users list
user_icon: at the right side of the plus (more about channels) icon at the top of the left hand side panel
none: don't show any button
Ticket Link
https://mattermost.atlassian.net/browse/MM-37299
Related Pull Requests
https://github.com/mattermost/mattermost-server/pull/18016
Screenshots
User Icon:

Sticky:

Lhs_button:

Release Note
NONE

@pablovelezvidal how can I get the different tests to display so I can review?

@pablovelezvidal how can I get the different tests to display so I can review?

Im working on getting the splitio values read from the spinwick server, once I get this done, I will let you know. If I can not get this done quickly, I can simulate the splitio value responses so you can validate the UX for this PR. I will keep you posted. @matthewbirtch

@stevemudie @matthewbirtch This other PR https://github.com/mattermost/mattermost-webapp/pull/8506 contains this same code + a pipeline change so the spinwick server is updated correctly. You can do your tests there. Currently the default value for splitio is User Icon. Let me know via DM when you want me to change the values so you can see the different variations the button has.

/update-branch

Hey @pablovelezvidal a few things I've found:
User Icon Option

The new icon next to the + icon is misaligned. It's sitting 1px too low

Sticky Button Option

The button's border and text color should be full opacity of the sidebar text color.
The hover state will just be adding a background of 8% sidebar text color
The button size is too small. An update was made recently (sorry I don't think that got communicated back to you). It should be 32px in height.
The font-weight on the button label should be font-weight: 600
The font-size on the button label should be font-size: 12px
The font-size on the icon should be font-size: 14px
Can we add 4px of space between the icon and the label within the button?
Can we adjust the spacing around the button so that there is 16px of space all the way around it? And it looks like there is a min-width set on the button to 90%. If we make this padding adjustment, we should be able to make the button width 100% of its container

LHS button version

Can we mimic the style of a channel list item for this button?  The icon size, the spacing should align with the channel items above


chore(deps): update packages/contracts-core/lib/forge-std digest to ae570fe [ci skip]

This PR contains the following updates:

Package
Update
Change

packages/contracts-core/lib/forge-std
digest
1d9650e -> ae570fe

[!WARNING]
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for the packages/contracts-core/lib/forge-std ae570fe update again.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


SUGGESTION: SetTemp for Default Assignments/Rules

Can we please get an option for setting temporary groups to users upon joining from the config file?
Example of what it could look like:
default-assignments:
  my-defaults-rule:
    if:
      has-true: <group.default>
    take:
      - group.default
    give:
      - group.member 24d12h6m
    set-primary-group: member

The default assignment got removed in the upcoming V5 update (#1537).
However, will this update include a separate system for default groups on join that may or may not support what you're suggesting.


Starting V1.0.16

Fixed indentation throughout to be 2 spaces.

An old issue #54  was still mentioned in the code.
This problem fixed wasn't actually a rendering issue but a parsing issue.


error code - heating / climate zone

I changed the logs info so that it was clear which one it concerns

@mkz212 is it only a reformatting of the logs?


Fix transformation in plot_vgp()

Same as #622, but for plot_vgp().
I'm guessing that this issue exists elsewhere in the codebase as well, but I haven't investigated it yet.

I don't think that there ends up being a difference between the ccrs.Geodetic() and ccrs.PlateCarree() for scatter plots, but there does for line plots as ccrs.Geodetic() plots the great circle and ccrs.PlateCarree() plots a lat/lon straight line as in this example:
ff_lon = 8 + 41 / 60
ff_lat = 50 + 7 / 60

fig = plt.figure()
ax = fig.add_subplot(1, 1, 1,
                     projection=ccrs.PlateCarree(central_longitude=(to_lon + ff_lon) / 2))
ax.plot([to_lon, ff_lon], [to_lat, ff_lat], c='b', lw=2,
        transform=ccrs.PlateCarree())
ax.plot([to_lon, ff_lon], [to_lat, ff_lat], c='r', lw=2,
        transform=ccrs.Geodetic())
ax.set_global()
ax.stock_img()
ax.coastlines()
ax.gridlines()


Refresh coveralls badge when main is updated.

Fixes #37

Coverage: 97.33%. Remained the same when pulling aaaad078045e1477a2152b43040e09d3502d6665 on terjekv/issue37 into 8f6031dd70f52c2dffc9913607e7ef957e3dd6d4 on main.


Compatibility with smac 0.12.0

Fixes #116

@AndreBiedenkapp Ah, sorry, forgot to change the title. Will work with Drafts from now on.

Specifically are the type casts necessary?

Well, SMAC 0.12.0 returns lists for that function now (not np.array's). After I was halfway through PIMP, porting everything that uses types to support lists instead of arrays, I realized that PIMP heavily relies on it being arrays to perform array-operations in multiple places (the link is one example). So if we have to cast anyway, we might as well do it consistently I figured. Are you ok with that?


Add "refresh" functionality to existing indexes

I saw this mentioned in https://github.com/jerryjliu/gpt_index/issues/262 and thought it sounded useful (and fun!)
It's a little tricky, because once a document is inserted into an index, we lose most context for that document except for the doc_id.
I'm not sure if I like the UX for this, so I'll add this as a WIP. If it looks good or useful, I'll convert it to a real PR lol. (probably still need to fix linting and whatnot)
If a user has a flow where the need to periodically refresh their index from a directory of documents, they can follow a structure like this:
documents = SimpleDirectoryReader(documents_folder).load_data()
for i in range(len(documents)):
    documents[i].doc_id = str(i)  # or, you can give it whatever name is relevant
index = GPTListIndex(documents)

...

documents = SimpleDirectoryReader(documents_folder).load_data()
for i in range(len(documents)):
    documents[i].doc_id = str(i)
refreshed_docs = index.refresh(documents))

Each document is hashed based on it's text and extra info, so that's how I determined if it changed or not.
At the end, refresh() returns an array of bool, indicating which documents where updated and which weren't
In order for this to work, _delete needs to be implemented (and it isn't always)

wow! i had been thinking of getting to this but seems like you already have a draft PR out 🔥

Alright, made the hash lookup much more efficient using the docstore 💪🏻 looking much better now

I gotchu on that unit test 💪🏻


Testing changes and caching behaviour

Hello,
I'm not sure if I'm missing something obvious, but is there patterns for testing how my plugin interacts with mypy caching for both mypy and dmypy when code is changed?
So say I make a test case with code in a particular way and it passes mypy. I want a test that show it still passes mypy if I change that code in a particular way. Same with dmypy.

Right now this is not supported, but PR for this would be really welcomed!
Mypy test cases have a similar design, here: https://github.com/python/mypy/blob/master/test-data/unit/check-incremental.test

mmkay, I thought so. Thanks. I will add this to the list of things I want to look at (no guarantees on a timeline :p)

So on this, once you're happy with https://github.com/typeddjango/pytest-mypy-plugins/pull/152 and that's merged, I have one last prefactor lined up (https://github.com/delfick/pytest-mypy-plugins/compare/schema/split-from-execution...delfick:pytest-mypy-plugins:separation/use-fixtures, will have an explanation of what it's doing when I make it a PR) and then finally the changes to make it possible to specify followups - https://github.com/delfick/pytest-mypy-plugins/compare/separation/use-fixtures...delfick:pytest-mypy-plugins:scenarios/followups
Though I have a problem I haven't quite being able to figure out where I change a file and then mypy doesn't see the change to that file. But if I do the same thing outside of pytest it does see the change. It's very weird.

yay, after that current PR and the next two, I think I have all the changes in a state that is ready to use, was able to make this test on my extension on django-stubs https://github.com/delfick/extended-mypy-django-plugin/actions/runs/8980999731/job/24665659671 to show one of the things I need to fix that was slowing me down so much (an edge case where an app is removed from INSTALLED_APPS but is still present on the file system)

@sobolevn hello, I was wondering, I do want to eventually upstream these changes to this project, but my changes are quiet extensive and your time for reviewing appears to be limited. Do you mind if I make my fork into it's own package in the meantime?

@sobolevn Hello, just thought I'd let you know that I ended up creating a fork of this plugin with all of my changes
https://pytest-typing-runner.readthedocs.io/en/latest/
The documentation still needs quite a bit of improvement tbh, but I've ran out of time to devote to that for now.
It currently only supports mypy but it shouldn't be difficult to make it possible to make it support running pyright or any other type checker. And makes it possible and easy to create scenarios where we test what happens when the code changes against a warm cache. It also is built around making it possible to write these tests like any other pytest test rather than constraining to a yaml definition (ultimately it provides a typing_scenario_runner fixture, which can be configured by a number of pytest fixtures so it can be customized within any normal pytest scope).
I've also created an example of how it could be used in django-stubs without major surgery to those tests if you're interested in that - https://github.com/typeddjango/django-stubs/compare/master...delfick:django-stubs:using-pytest-typing-runner?expand=1
An example of using it to write tests with followup scenarios can be found in https://github.com/delfick/extended-mypy-django-plugin/tree/main/tests
Either way, I want to say thanks for pytest-mypy-plugins! It gave me a massive head start with that work, I really appreciate everything you do around mypy and django stubs!


tagged tasks with composite level/score tags (e.g. level1_scored)

PR addresses the level1/level2 scored/notscored tag issue mentioned in #93 Some tasks are not properly tagged
ansible-playbook playbook.yml --tags level1_scored

note that this will NOT apply to tasks tagged with level1 but NO scored/notscored tag...

I think the tagging needs a thorough review/clean up at this point!

...this (obviously) does not attempt to address the overall tagging and also raises the question of why some rules are named but not tagged as scored or unscored? happy to make further changes to enure consistency!

Hello,
I wanted to reach out and let you know that this PR is being closed. We have re-worked the role and want to start with a fresh PR's and issues list with this latest version. There was a post in the Ansible-Lockdown google group (https://groups.google.com/g/ansible-lockdown) with the details of the changes that are coming. Please checkout the thread titled RHEL 7 CIS and STIG Changes for all of the details, I also have the message pasted at below.
Please as you use the latest version and open issue tickets as you find them, it is the best way for us to improve the role for everyone. Thank you for being part of the community and providing awareness of problems or advice on improvement. Having community contribution is a huge part of this project.

Hello,
Thank you to everyone in the Ansible-Lockdown community who has contributed to RHEL7 STIG/CIS. Our team at MindPoint Group has been working with the entirety of the Ansible-Lockdown project, and we have some significant updates for both RHEL 7 STIG and CIS. With these updates, some larger changes have been made. I have these changes/updates outlined below.
Testing:

CI/CD - We have implemented some automated testing pipelines to test pull requests into the devel and main branches. With the current workflow, the community will PR into the devel branch (never the main branch) for review by the administrators. When your PR is created, the first check will remain the DCO check. The second check is a functional testing pipeline that will automatically perform a functional test of the branch the PR is initiated from. Once both tests pass, someone from the Administrator Team will review the changes and merge them into the devel branch. From there, an additional review is completed before the devel branch is merged into the main branch. Only the Admin Team will perform PRs/merges into the main branch. There is also an automated pipeline for PRs from devel to main. Please do not edit the .github/workflows files since those are used as part of the pipeline.
Compliance Checking – MindPoint Group has been working to create our own compliance audit scan tool. The tool uses a goss framework executable to run custom checks that we have created. The goal is to provide a more thorough check for control compliance and decrease the number of false positives/negatives. For example, it will check the configuration file related to the control and as well as checking if that configuration is active. With a smarter scan, we can hopefully identify attempts to trick scanners as well (for example stacking a parameter in a config file where the first instance is enabled and second disabled. Most audit tools search for the first instance but the application might look for the last instance of the parameter, thus making the scanning tool think it's enabled). In testing, we have found that our audit scan runs significantly faster than other audit tools, reducing audit times. Our audit tool and profiles will have their own repositories in the Ansible-Lockdown org, but within the remediation role there will be an integrated way to incorporate the audit. Keep an eye out for the audit tools as they are released. We plan on developing a goss audit profile for each current remediation role. Going forward, we plan to release a remediation role and goss audit tool profile simultaneously.
Role Updates:
RHEL 7 STIG/CIS – We have re-written much of the RHEL 7 STIG and CIS roles to increase clarity and readability and address some functionality items. We performed these updates while creating our goss testing framework for each of these roles. We plan on pushing our update to the devel and main branches. We will move the current devel and master branches to a devel_stable_ and master_stable_ branch in the respective repositories. Accordingly, community members who rely on the current version can still use that version going forward; this process will not remove what is currently there. The latest versions of the roles have also been updated to comply with the latest benchmarks.
Role Architecture – All roles will change with regard to the structure in the tasks folder. Taking CIS as an example, there will be a folder per section and yaml files for each sub-section. For example control 1.2.1 in CIS will be located in RHEL7-CIS/tasks/section_1/cis_1.2.x.yml. The cis_1.2.x.yml file will contain all controls related to section 1.2.x. This will hopefully make updates to roles a bit easier with less risk. This matches the architecture of our audit tool, creating consistency across remediation and audit platforms. The end goal is to repeat this architecture (the best we can) on STIG roles, but we are starting with CIS.
Existing PRs and Issues – With all of these changes comes the task of cleaning up existing PR’s and issues. Our plan is to close all of the existing PR’s and issues because of the re-work. Our team is growing and should be able to stay on top of the new issues and PRs as they come in.
Again, I would like to thank the community for your involvement in this project. The input and work from the community has contributed significantly to the success of this project. Please keep an eye out for these changes, which will be rolling out in the coming weeks.


File size check does not work for files brought in via iRODS browser when creating resources

While working with Ray on creating a Hydroshare resource using the large NFIE geo database file (~12GB) via iRODS browser from NFIE zone, I found files brought in via file browser has the size attribute as None, hence check_resource_files() routine cannot retrieve the file size to compare against the predefined file size limit (currently 10GB), and simply returns True for this case. Will need to retrieve file size from iRODS via icommands (probably via iquest) to pass it in so that the file size can be compared against the predefined file size limit.

@rayi113 has tested on dev using a 12GB file, and it properly tells that the file size is larger than the 10GB limit. So it works now. Closing.


feat: ⏯ Update landing page image components to be pausable

Overview

Allow LandingPage components with images to be pausable.

PR Checklist

[ ] Related to designs:
[x] Related to JIRA ticket: EN-1841
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change
[ ] The alpha package of this PR is passing end-to-end tests in all relevant Codecademy repositories

PR Links and Envs

Repository
PR Link
PR Env

Monolith
Monolith PR
Monolith Env

Portal
Portal Link
Portal Env

Another Repo
Another Link
Another Env

🚀 Styleguide deploy preview ready!https://62b1d929aa8c744e82b7c8ff--gamut-preview.netlify.appDeploy Logs