bo-selector 0.0.10

Type: Missing
Summary:
bo-selector 0.0.10
Details:
ClearlyDefined license is BSD-2-Clause
NPM is BSD
GitHub is BSD-3-Clause: https://github.com/featurist/bo-selector/blob/master/LICENSE
Resolution:
BSD-3-Clause
Affected definitions:

bo-selector 0.0.10

License is BSD-2-Clause. Updated.


overlord assignment changes

Please review changes for overlord.

Bomb looks good however I would like to see more tests. For cucumber tests please provide tests that attempt to input invalid data as well as addressing the other comments Hound and I made. I would also like to see some rspec tests for the bomb class.

This is looking good.  Definitely needs some more tests, especially RSpec tests.  Take a look at the above comments, refactor and add tests, and resubmit for another review.


fix: Added context menu to delete a container

Fixes #974
The Canvas looks like this with the Context menu:

Merging this PR now, to move forward with the repository rename. The upcoming tests will be added in a new PR.


Cannot locate configuration files after installation

For the version v0.2 and below, the main program (cli.py) is not able to locate all configuration files after is has been installed by
python3 ./setup.py develop

since its lookup path is relative to the sys.path[0] and all the content under the "license" as well as "config" folders are not able to be located.
Changes to 'setup.py' or source code is needed.

Fixed by version v0.3.


refactor(backend): refactor config

🍰 Pullrequest

refactor config.
This is a suggestion, please have a look @Mogge
The functions in the config are not tested yet - a test strategy might be needed?
Issues

fixes #112

Todo

[X] None

@Mogge Please review
Dev mode:

Production:

Test - no warning or anything:

Furthermore we have reusable checks for specific parts of the software which need configuration values to be present:

We remain typesafe without casts (except on the checks which are a bit more difficult to understand)
CONFIG_CHECK_BREVO_SEND_CONTACT: (
    config: typeof CONFIG,
  ): config is typeof CONFIG & {
    BREVO_KEY: string
    BREVO_TEMPLATE_CONTACT_BASE: number
    BREVO_TEMPLATE_CONTACT_USER: number
    BREVO_CONTACT_REQUEST_TO_NAME: string
    BREVO_CONTACT_REQUEST_TO_EMAIL: string
  } =>
    typeof config.BREVO_KEY === 'string' &&
    typeof config.BREVO_TEMPLATE_CONTACT_BASE === 'number' &&
    typeof config.BREVO_TEMPLATE_CONTACT_USER === 'number' &&
    typeof config.BREVO_CONTACT_REQUEST_TO_NAME === 'string' &&
    typeof config.BREVO_CONTACT_REQUEST_TO_EMAIL === 'string',


Many interfaces seem to be broken when exactOptionalPropertyTypes is enabled.

⚙ Compilation target
ES2018
⚙ Library
lib.es.2018.regexp.d.ts
Missing / Incorrect Definition

interface RegExpExecArray {
    groups?: {
        [key: string]: string;
    };
}

Sample Code
With "exactOptionalPropertyTypes": true, then this interface implies that for all properties of groups there will always be a string, which is wrong. I suspect that this pattern is largely endemic when using exactOptionalPropertyTypes.
const matrixToRegexp =
  /^https:\/\/matrix\.to\/#\/(?<entity>[^/?]+)\/?(?<eventId>[^?]+)?(?<query>\?[^]*)?$/;

const url = matrixToRegexp.exec(matrixTo)?.groups;
if (!url) {
  return ActionError.Result(`Not a valid matrix.to URL: ${matrixTo}`);
}
const eventID = url.eventId // eventID is typed as `string` when it should be `string | undefined`

Why is this a recommended setting when it actually quite dangerous^1? Especially when combined with typescript-eslint's  no-unnecessary-condition rule, which will use typescript's incorrect information to recommend removal of "redundant" checks. This is quite serious.

### Documentation Link

_No response_

Seems like you want to turn on noUncheckedIndexedAccess

Hey, that's right, thank you!

Maybe https://www.typescriptlang.org/tsconfig/#noUncheckedIndexedAccess should be recommended though


date_from and date_to should be required=False

These fields:
https://github.com/django-oscar/django-oscar/blob/1.0.1/oscar/apps/dashboard/reports/forms.py#L22
should be set to required=False
Because the base ReportGenerator class is capable of handling form submissions without a date range by checking if self.date_range_field_name is set to None.
https://github.com/django-oscar/django-oscar/blob/1.0.1/oscar/apps/dashboard/reports/reports.py#L56

Sorry. I would send a pull request. But to be honest, I have to look up how to do that--and it's 1:00am in my timezone. :(


Keep aspect ratio for BGA

Nowadays BGA files are shipped in many aspect ratios, and while 1:1 and 4:3 wouldn't look too different when resized, 16:9 BGAs will look weird.
There should be an option to add letterboxing to BGAs which aspect ratio does not match the aspect ratio of #DST_BGA

Could you send some examples of such charts? Also, how does LR2 handle this?

Also, how does LR2 handle this?
It will stretch the BGA to match the size of skin's #DST_BGA class.
Could you send some examples of such charts?
Not really, as nowadays charts ship with two variants of the BGA: one .mp4 file for modern players (like beatoraja) and one .mpg or .wmv file specifically for LR2 which is letterboxed to fit 1:1 or 4:3 aspect ratio.
SPACE RENDA 5 is an example of such a chart.


Drawer should use correct default values from Material Spec

Proposal
Align with Material spec by:

Update Drawer backgroundColor to use ColorScheme.surface
Update drawer scrim color to use ColorScheme.onSurface with 0.32 opacity

To be done after https://github.com/flutter/flutter/pull/89237 is merged

Is there any further development in that matter?


[comment] extended geotiffHandler with Validator

Hi @giohappy
this is not an issue but only a comment.  The concept of handlers is great. It can solve a problem I'm facing since a long time.
Badly prepared geotiffs.
With the handler concept it looks it is easy to implement an extended handler that does basic checks like

does the tiff use compression
does the tiff use overviews
...

Cheers,
Toni

Yes @t-book and it's one of the goals of having handlers ;)


first upcomming date is incorrect near the end of the year.

Support guidelines

[X] I've read the support guidelines

Description
my sensor show the next garbage pickup on january 4th, while actually it is tomorrow

next date is tomorrow

while plastic and gft show 04-01-2024(dd-MM-yyyy)
probably some order by misses the year
Expected behaviour
date 21-12-2023 are shown for (plastic,gft) and
28-12-2023 for rest
Actual behaviour
date 04-01-2024 are shown for (plastic,gft) and
25-01-2024 for rest
Version
Core 2023.12.3
Supervisor 2023.12.0
Operating System 11.2
Frontend 20231208.2
component2023.09.01
HASS logs

logger -> logs -> custom_components.afvalwijzer: debug in you configuration.yaml

created a fix for you,
https://github.com/xirixiz/homeassistant-afvalwijzer/pull/258
please check it out,

Drafted release: 2023.12.01
Sorry for the delay. Forgot about it due to the holidays :)


Player messed up

If you are not using the latest developer version 497 then download it from here and let us know if the problem is gone:
https://github.com/YePpHa/YouTubeCenter/wiki/Developer-Version

That seems to help. Is there anyway for you to add a dark mode? I'd rather not have to use more scripts than I have to

Also volume adjust with scroll is just about the only thing keeping me from using this exclusively

Scroll volume has already been requested in #90, #990 and #1210. The same goes for the the dark mode, it's a matter of the addon author having some free time and willing to add them.


[Ionic v4] First card behind toolbar if ion-content has no padding

Ionic Info
@ionic/angular: "4.0.0-beta.1"
Describe the Bug
If no padding is specified for the ion-content then the first ion-card will be partially rendered behind the ion-toolbar
Expected Behavior
The first ion-card should not be behind the toolbar regardless if the content has or not padding
Code
git clone https://github.com/peterpeterparker/first-ion-card

Screenshot

Confirmed this is already fixed thanks to the .scroll-inner refactor!!

All good with v4.0.0-beta2, thx a lot 👍


Update phpunit/phpunit and illuminate/database

@alexweb One of the tests is failing. Can you please fix that test? Also would appreciate it if you could add a test for Laravel 11 and PHP 8.2 and 8.3.

@alexweb One of the tests is failing. Can you please fix that test? Also would appreciate it if you could add a test for Laravel 11 and PHP 8.2 and 8.3.

Hmm... Not sure I know how to do that in Github. I just run composer test locally and tests pass.
Do you know how to add/change the tests you mentioned?

@alexweb you need to do a couple of things in .github/workflows/tests.yml file

Add new PHP and laravel versions on line 14 and 15 (matrix)
Remove --verbose from the vendor/bin/phpunit --verbose --testdox command on line 36.

Can you please update the PR with these changes?


refactor: encryption envelope APIs, tests

Builds on top of https://github.com/hyperledger/aries-vcx/pull/1081 - please merge that first
Restores (and simplifies) tests of EncryptionEnvelope
Refactors EncryptionEnvelope by decoupling its APIs from concept of Aries messages. Even inherently didcomm !== aries, so this decoupling makes broader sense and also makes testing a lot easier.

The changes also represent one step towards dropping usage of legacy AriesDidDoc structure in encryption envelope

Deleted unused error mappings

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

Comparison is base (3a2da3d) 0.05% compared to head (b33c40e) 0.05%.

Files
Patch %
Lines

aries/aries_vcx/src/utils/encryption_envelope.rs
0.00%
149 Missing :warning:

aries/aries_vcx_core/src/wallet/indy/signing.rs
0.00%
11 Missing :warning:

...ries/aries_vcx_core/src/wallet/indy/indy_wallet.rs
0.00%
8 Missing :warning:

aries/aries_vcx/tests/test_connection.rs
0.00%
1 Missing :warning:

Additional details and impacted files
@@                    Coverage Diff                     @@
##           fix/encryption-envelope   #1082      +/-   ##
==========================================================
- Coverage                     0.05%   0.05%   -0.01%
==========================================================
  Files                          471     471
  Lines                        24019   24093      +74
  Branches                      4295    4332      +37
==========================================================
  Hits                            13      13
- Misses                       24005   24079      +74
  Partials                         1       1

Flag
Coverage Δ

unittests-aries-vcx
0.05% <0.00%> (-0.01%)
:arrow_down:

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

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

@xprazak2 rebased


can i get some help?thanks!

I write an attention(based on lstm) for nmt using own data by studying your code.but the attention weights doesn't seem normal. here is the code. Can i get some help from you?thanks very much.
code

I'm exactly with the same problem. I wrote my own model based on the provided code of the 3rd/4th tutorial (i.e. add attention) and I'm using my own data (specifically, I'm using Tatoeba es-en from Opus). The results when checking the attention are the same that you provided. It looks like if the attention is "looking" at the last tokens. I've checked out the code ~30 times, but I don't see any problem after have solved a few mistakes...
@bufuchangfeng did you solve this problem?

I already know what my problem was. The problem was related to the quantity of data that I was providing. It seems that if you provide too small data, the attention will not generalize well, and it seems to focus on the last tokens for some reason I don't understand. Now, with 100.000 sentences, 60/20/20 for train/dev/test, the attention seems to focus on the expected tokens.
I just leave this comment here in the case that might help someone :)

I already know what my problem was. The problem was related to the quantity of data that I was providing. It seems that if you provide too small data, the attention will not generalize well, and it seems to focus on the last tokens for some reason I don't understand. Now, with 100.000 sentences, 60/20/20 for train/dev/test, the attention seems to focus on the expected tokens.
I just leave this comment here in the case that might help someone :)


Improve the documentation

The current documentation has grown too much and is hard to navigate. We should break it into smaller pieces and organize it better.

There are plenty of alternatives if the current documentation generator is not flexible enough.
Putting some here just so I remember.

https://www.mkdocs.org
https://www.docsy.dev/docs/examples/
https://dokz.site/docs

Also https://www.docz.site/ is a good bet

I need to think about it.
But definitely something more organized and documented than the current "Examples" which is a bit messy and not very easy to navigate.

Hi maybe I can jump in and try to design what we already have in a new format

@Haugf what did you have in mind?

@knownasilya I was thinking we could implement a table of content section to mark out the different examples a little bit clearer

@Haugf go for it, a focused pr would be great.

Can you explain what a focused PR is? sorry 😅

Just changing the table of contents in the markdown without any doc site updates. So structural navigation changes only.

A TOC would be of great help no doubt. but I still think that we need to rethink a bit the current documentation to make it more browsable and easier to use.

Agreed. I think any small improvements we can make in the mean time is good, until we have a plan.

Sounds good, I can go ahead and add that in

Am I allowed to make branches in this repo or do I have to do something else?

Just read the documentation, we're good :-)

Hey I made a pull request, builds are passing 🎃

Silly question, is there a way you can add a hacktoberfest tag to this issue  before pulling it in?  :)

Hi, something like a "Quick Start" Guide would be very nice.
csvtojson  has this for example.

I started working on this in https://github.com/zemirco/json2csv/tree/site and a quick start is part of it. Still very wip.


python310Packages.sphinxcontrib-details-directive: init at 0.1.0

Description of changes
https://github.com/sphinx-contrib/sphinxcontrib-details-directive/

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

I’m no longer trying to use this.


Rename credentials name to username

https://github.com/gdg-garage/space-tycoon/blob/master/api/swagger.yaml#L294

done


StatiCrypt 3.x

Hi @a-nau, just letting you know StatiCrypt 3.x is out. With it come a number of improvements, the most important one being using WebCrypto as a default engine, which is more secure that CryptoJS that we used before. There are also some breaking changes, hopefully easy to resolve (I'd be happy to hear if they're not).
This project is still listed in the "Community" section of StatiCrypt README, I'll mark it as compatible with 2.x only and useful for inspiration purpose for now. Let me know if you ever make it compatible with 3.x, and I'll update accordingly!

Hi @robinmoisson
thanks a lot for pinging me!
Actually, I have some issues which started with version 2.5 (2.4 is fine). Is it possible that we need to update the installation instructions? I get the following error (when just running staticrypt or staticrypt --help):
internal/modules/cjs/loader.js:818
  throw err;
  ^

Error: Cannot find module 'node:crypto'
Require stack:
- /usr/local/lib/node_modules/staticrypt/lib/cryptoEngine/webcryptoEngine.js
- /usr/local/lib/node_modules/staticrypt/cli/index.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
    at Function.Module._load (internal/modules/cjs/loader.js:667:27)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/staticrypt/lib/cryptoEngine/webcryptoEngine.js:1:48)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/usr/local/lib/node_modules/staticrypt/lib/cryptoEngine/webcryptoEngine.js',
    '/usr/local/lib/node_modules/staticrypt/cli/index.js'
  ]
}

I still only use
npm install -g staticrypt

inside the container. I added a new branch with a devcontainer so you can easily reproduce the issue.

Ah yes thanks for sharing, someone opened an issue on staticrypt to post that error as well. I am not super familiar with Docker, do you know which node version is used in the image?
It turned out Staticrypt 2.5.x to 2.6.1 became incompatible with node versions <= 14, this has been fixed in 2.6.2. Is 2.6.2 throwing you the same error?

Thanks @robinmoisson, that was the issue. I fixed it now and the project uses version 3.x 😃

Awesome, thanks for updating! I've updated the references to this project in staticrypt README :slightly_smiling_face:

Perfect, thanks a lot!


[bug] picker icon click noting when isRange is false

Version
1.4.0
Environment
windows chrome63 v1.4.0
Reproduction link
https://ng.ant.design/components/date-picker/zh
Steps to reproduce
click the datapicker's icon
What is expected?
show calander
What is actually happening?
nothing
Other?

@0maxxam0 funded this issue with $5. See it on IssueHunt

I think the current code is all working fine ??

fixed in current version


Space issue

Hey there,
When I installed stableswarmui in my D drive it took a lot of space in my C drive, and when I generate an image it takes about 10 gigs of space in C drive but it goes back to normal when I turn it off.
With that being said, if I try to make any adjustment ( like making the image larger or try to make a video ) it gives me an error and I’ll have to rest all backends.
Is there any solution to this problem?

Swarm itself doesn't use anything outside its own folder, though it does depend on Microsoft DotNET 7 and Git, either of which may end up installing core files wherever it puts those, you might be able to install them manually instead to force a different path.
Any usage that appears while generating and disappears after is some form of temporary storage, not in Swarm itself but probably in the Comfy backend's underlying python libs?
re  it gives me an error and I’ll have to rest all backends. i'd have to know the specifics of what error exactly to be able to respond to that


When I clone and run this project: Uncaught Invariant Violation: block is not a BlockNode

pageage.json
"resolutions": {
"draft-js": "0.11.7"
}

@hanwenbo   您好,更新后没有解决这个报错


Allow changes to banners on dashboard and landing page

[ ] There is a banner for when intake is open - to landing page and dashboard
[ ] There is a banner for when intake is closed - to landing page and dashboard
[ ] can use Growthbooks to turn on and off the above 2 banners
[ ] can use growthbooks to modify text in the above 2 banners

Gherkin acceptance criteria:

Dupe of #689

Hey team! Please add your planning poker estimate with Zenhub @marcellmueller @matthieu-foucault @AntBush @VB-at-Bis

@VB-at-Bis, is this still in progress? We need a PR for the documentation


AnnotationProperty -- exact alternate label

From<EMAIL_ADDRESS>on February 01, 2011 11:57:30
Please indicate the label for the new term exact alternate label Please provide a textual definition an alternate label for a class C that precisely denotes C in the context of the domain of the ontology in which it is used Please add an example of usage for that term Please provide any additional information below. (e.g., proposed position in the IAO hierarchy) subannotationpropertyof: alternate label
xref: obo-format:EXACT
Original issue: http://code.google.com/p/information-artifact-ontology/issues/detail?id=96

From<EMAIL_ADDRESS>on February 12, 2011 09:02:25
"context of the domain of the ontology in which it is used" is too broad and impossible to predict. Terms will be adopted by other ontologies and other communities without intervention of initial authors.
Should something like this be desired, I suggest making explicit the community in which the term is an acceptable exact alternative term and annotating this axiom to indicate that.

From<EMAIL_ADDRESS>on May 25, 2011 14:19:57
see https://code.google.com/p/information-artifact-ontology/issues/detail?id=106
Status: WontFix

This issue was moved to information-artifact-ontology/ontology-metadata#10


Code for the interactive annotation procedure.

Hi,
Thanks for such a great work, can you please provide with code for the interactive annotation procedure.

As far as I remember, the code for this is in a rather messy state. Please contact @pvoigtlaender for details.


build: compile docker-cli statically

Compile docker-cli statically to avoid problems described on #132.
Currently, the docker-snap is shipped with the docker-cli dynamically linked:
lincoln@fenrir:~/docker/multiarch/dynamic/amd64$ ldd bin/docker
        linux-vdso.so.1 (0x00007ffc5850a000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x0000719048400000)
        /lib64/ld-linux-x86-64.so.2 (0x000071904a179000)

When shipping a companion snap based on core 20 or an older version, we encounter GLIBC problems due to incompatible versions:
lincoln@fenrir:~/docker/rocker$ sudo rocker hello-world
docker: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by docker)
docker: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by docker)

Note: "Companion snap" refers to the snap that is compiled to wrap docker and use it in systems like Ubuntu Core.
The static compilation of docker-cli aims to avoid GLIBC problems with compatibility between docker-snap and other snaps based on legacy core versions.

@lucaskanashiro, could you please enable the workflow to run? Thank you!

@locnnil thanks for this PR, the proposed change looks good. I am pretty sure you tested this version before submitting the PR but could you please give me some reproduction steps so I can try it myself locally?

@lucaskanashiro Sure here is a quick guide to do so:
Preparation
First, we're going to test using an installation from the store, then we would build the docker-snap with the modifications of this PR.
Firstly, you need a companion snap, that is basically a snap that will wrapper docker functionality, let's call it rocker:
Creating the directory for the companion snap
mkdir -p rocker/src/usr/bin && cd rocker

Then create the script that will trigger the docker snap:
cat << 'EOF' > src/usr/bin/rocker_run.sh
#!/bin/sh -e

export PATH=$SNAP/docker-bin/bin:$PATH
docker run "$@"
EOF

chmod +x src/usr/bin/rocker_run.sh

Then we create the snapcraft.yaml file:
mkdir snap

cat << 'EOF' > snap/snapcraft.yaml
name: rocker
base: core20
version: '0.1'
summary: A test of interacting with the Docker snap through another snap.
description: |
  Here I am
  Rock you like a hurricane
  Here I am
  Rock you like a hurricane

grade: stable
confinement: strict

# Add an app section to the snapcraft.yaml for our script:
apps:
  rocker:
    command: usr/bin/rocker_run.sh
    plugs: [docker, docker-executables]
    environment:
      PATH: $SNAP/docker-bin/bin:$PATH

parts:
  copy-src:
    plugin: dump
    source: src/

plugs:
  docker-executables:
    interface: content
    content: executables
    target: $SNAP/docker-bin

EOF

OBS: It's important to use the core20 as base, because then, we're going to demonstrate the problem on #132 and how we get rid of it.
Now, it's time to build and install the snap:
snapcraft --use-lxd

sudo snap install --dangerous ./rocker_0.1_amd64.snap

Then, we connect the needed interfaces on rocker snap:
sudo snap connect rocker:docker             docker:docker-daemon
sudo snap connect rocker:docker-executables docker:docker-executables

The Results
Now, it's the final demonstration
Current behavior
By using the current docker snap, when trying to run the command we got:
$ sudo rocker hello-world
docker: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by docker)
docker: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by docker)

Ideal behavior
But using the docker snap with the docker-cli compiled statically, it executes the command perfectly.
First, it's necessary to build the docker snap with the modification of this PR.
Then prepare it:
# Remove the stable installation of docker snap
sudo snap remove docker --purge

# Install the compiled docker with the patch of this PR
sudo snap install --dangerous ./docker_24.0.5_amd64.snap

# Connect the interfaces
sudo snap connect docker:docker-cli            docker:docker-daemon
sudo snap connect docker:privileged           :docker-support
sudo snap connect docker:support               :docker-support
sudo snap connect docker:firewall-control  :firewall-control
sudo snap connect docker:network-control   :network-control

# Initialize the docker snap service
sudo snap start --enable docker.daemon

# Then test the rocker snap
sudo rocker hello-world

Then the rocker snap works as expected:
$ sudo rocker hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
c1ec31eb5944: Pull complete
Digest: sha256:6352af1ab4ba4b138648f8ee88e63331aae519946d3b67dae50c313c6fc8200f
Status: Downloaded newer image for hello-world:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
    (amd64)
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
 https://hub.docker.com/

For more examples and ideas, visit:
 https://docs.docker.com/get-started/

@locnnil thanks for the very detailed reproduction steps, appreciated!
I was able to reproduce the issue and also verify the fix. LGTM, +1.


Disk stats for mounted EBS drives are missing on EC2 instances

Output of the info page (if this is a bug)
====================
Collector (v 5.27.0)
====================

  Status date: 2018-09-19 13:18:27 (12s ago)
  Pid: 884
  Platform: Linux-4.14.67-66.56.amzn1.x86_64-x86_64-with-glibc2.3
  Python Version: 2.7.15, 64bit
  Logs: <stderr>, /var/log/datadog/collector.log, syslog:/dev/log

  Clocks
  ======

    NTP offset: 0.0027 s
    System UTC time: 2018-09-19 13:18:40.032566

  Paths
  =====

    conf.d: /etc/dd-agent/conf.d
    checks.d: Not found

  Checks
  ======

    ntp (1.2.1)
    -----------
      - Collected 0 metrics, 0 events & 0 service checks

    disk (1.3.0)
    ------------
      - instance #0 [OK]
      - Collected 30 metrics, 0 events & 0 service checks

    network (1.6.1)
    ---------------
      - instance #0 [OK]
      - Collected 20 metrics, 0 events & 0 service checks

    mysql (1.4.0)
    -------------
      - instance #0 [OK]
      - Collected 172 metrics, 0 events & 2 service checks
      - Dependencies:
          - pymysql: 0.8.0

  Emitters
  ========

    - http_emitter [OK]

====================
Dogstatsd (v 5.27.0)
====================

  Status date: 2018-09-19 13:18:38 (1s ago)
  Pid: 877
  Platform: Linux-4.14.67-66.56.amzn1.x86_64-x86_64-with-glibc2.3
  Python Version: 2.7.15, 64bit
  Logs: <stderr>, /var/log/datadog/dogstatsd.log, syslog:/dev/log

  Flush count: 13
  Packet Count: 52
  Packets per second: 0.1
  Metric count: 22
  Event count: 0
  Service check count: 0

====================
Forwarder (v 5.27.0)
====================

  Status date: 2018-09-19 13:18:38 (2s ago)
  Pid: 876
  Platform: Linux-4.14.67-66.56.amzn1.x86_64-x86_64-with-glibc2.3
  Python Version: 2.7.15, 64bit
  Logs: <stderr>, /var/log/datadog/forwarder.log, syslog:/dev/log

  Queue Size: 456 bytes
  Queue Length: 1
  Flush Count: 32
  Transactions received: 33
  Transactions flushed: 32
  Transactions rejected: 0
  API Key Status: API Key is valid

======================
Trace Agent (v 5.27.0)
======================

  Pid: 875
  Uptime: 133 seconds
  Mem alloc: 1768184 bytes

  Hostname: xxxxx
  Receiver: localhost:8126
  API Endpoint: https://trace.agent.datadoghq.com

  --- Receiver stats (1 min) ---

  --- Writer stats (1 min) ---

  Traces: 0 payloads, 0 traces, 0 bytes
  Stats: 0 payloads, 0 stats buckets, 0 bytes
  Services: 0 payloads, 0 services, 0 bytes

Describe what happened:
The system.disk metrics only get collected for the root device on ec2 instances.
Mounted EBS storages won't show up. Even if they are mounted as completely normal block devices with an ext4 filesystem on them.
Describe what you expected:
system.disk metrics for all mounted blockdevices.
Steps to reproduce the issue:
Install the datadog agent on an EC2 instance that has an external EBS storage mounted with an ext4 filesystem on it.
Look at the system.disk metric.
Additional environment details (Operating System, Cloud provider, etc):
Amazon EC2 with latest Amazon Linux.
Two EBS storages mounted.

Hi, can you send the output of (mask the host values and the Instance ID
datadog-agent check disk | sed -r 's/"host": "[^"]+"/"host": "some.thing.com"/' | sed -r 's/Instance ID: disk:[^ ]+/Instance ID: disk:xxxxxx/'
and also, what is the mount point of your volume ?
I also noticed I'm seeing the same behaviour on my side, I'm looking into this, must be a simple configuration issue I suppose, I'll let you know what I find.
Btw, here's the partial output of the device that doesn't get collected on my side. The mount point of this partition is under /home/developers/backup and it's a XFS filesystem.
{
      "metric": "system.disk.free",
      "points": [
        [
<PHONE_NUMBER>,
          8.3811152e+07
        ]
      ],
      "tags": null,
      "host": "some.thing.com",
      "device": "/dev/nvme1n1p1",
      "type": "gauge",
      "interval": 0,
      "source_type_name": "System"
    }
  ]
}
=========
Collector
=========

  Running Checks
  ==============

    disk (1.3.0)
    ------------
        Instance ID: disk:xxxxxx [OK]
        Total Runs: 1
        Metric Samples: 72, Total: 72
        Events: 0, Total: 0
        Service Checks: 0, Total: 0
        Average Execution Time : 48ms

Output of df (without tmpfs) showing devices, mount points and filesystems
df -hPT | grep -v tmpfs
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/nvme0n1p1 xfs       150G   78G   73G  52% /
/dev/nvme1n1p1 xfs        80G   33M   80G   1% /home/developers/backup

After a few checks, it's most likely just a linux file permission problem (At least for me).
The dd-agent user cannot see the mounted volume because the directory where it is mounted belongs to another user (developers in my case) without read permissions to others.
Here's my output
sudo -u dd-agent df -hPT | grep -v tmpfs
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/nvme0n1p1 xfs       150G   78G   73G  52% /

sudo -u dd-agent ls -al /home/developers/backup
ls: cannot access /home/developers/backup: Permission denied

I'll adjust my permissions on my side to fix this or mount the volume somewhere else and that should fix it for me. Can you check if this explains your problem as well ?

It indeed was a permission problem.
Giving the dd-agent access to the directorys the storages are mounted on fixed the problem.
Thanks for the help.

It indeed was a permission problem.
Giving the dd-agent access to the directorys the storages are mounted on fixed the problem.
Thanks for the help.


Spectrum Options not working

Trying to use the following options:
Type: Flat;
Palette: none;
Picker: Show/Cancel Button
But spectrum always show me everything.
https://jsfiddle.net/JoshuaGiacobo/9epu05ho/1/
In the working demo I don't know whats the difference.
https://seballot.github.io/spectrum/
It should be like this:

Same problem


example for multi-turn position

I'm trying to use the ATM22 14bit multi-turn  version.
Would it be posible to give an example to get the absolute position including the number of turns ?
Thanks

hi, the same question

Was this question ever answered?

based on the examples here and documentation I wrote a some code ...
AMT Sample.zip


MF-1365 - Add ADOPTERS.md file

What does this do?
It adds the ADOPTERS.md file, a public ledger that tracks Mainflux technology adopters. Maintained by users themselves.
Which issue(s) does this PR fix/relate to?
Resolve #1365
List any changes that modify/break current functionality
NA
Have you included tests for your changes?
NA
Did you document any new/modified functionality?
NA
Notes
NA

@drasko IMHO Adopters is more appropriate for a project such as Mainflux. Both users and adopters are used, some of the popular projects using adopters.md
OpenFaaS
Containerd
CoreDNS
OpenBS
Etc...

@drasko @nmarcetic I prefer ADOPTERS since Users terminology  is already used  in the platform.

@drasko @nmarcetic I prefer ADOPTERS since Users terminology is already used in the platform.

Agree.


resolves #190, fixed pagination for reviews list

Summary

Fixes #190
List of changes proposed in this PR (pull-request)

Added Review.get_reviews_viewable_by_user()  to get a query set that lists all reviews that a user is allowed to view, added test for this function
Used the above in ReviewList.get_queryset() to supply the Paginator with the correctly filtered list of reviews

What should a reviewer concentrate their feedback on?

[x] Please check that reviews are appearing as expected and properly paginated
[x] Is the ordering of reviews ok, it's currently sorted by newest -> oldest

This all works and looks correct to m. happy with the ordering. Thanks Twin!

Feel free to merge when ready

Actually @twinkarma I just noticed a problem that I missed locally as I don't have too many examples of a review with multiple authors in my test dB. It looks like the reviews are repeated for each reviewer so for example if there's 3 reviewers, the review appears 3 times.

Fixed it for you in #192


Sort by profit/prices

Any plans to add sorting functionality?
Would be very handy to have the highest profits on top of the list! Great program either way.

Yeah, sorting was the next thing I was to implement, but I'm not sure if this repo will be maintained anymore since the albion-data-client servers are going to be deactivated soon (or has already been). :face_with_head_bandage:


Port to .NET Core

WIP

Have you tested all the changes in this PR and confirmed that all the old .NET Framework 2, 3.5, 4 and 4.52 library still build correctly in addition to the new .NET Core library?

No, not yet. This is currently just a rough spike to see if it was happening. I did accidentally open a PR against your Repo (which I then closed) instead of against my Repo (this one).
There is still a bit to go, particularly around how the solution is built.

Ok. I'm not sure which one I was commenting on, but I did a review of this code base and made a few comments. Please let me know when you have yours building and I'll do another review and then merge. Thanks for your work.

What process did you use to convert the project file?

@dahall I did it by hand, not sure if there is an automatic way. I've had to put this on hold a bit, some personal things have come up, but planning to pick it back up at some stage.


Add automatic schema docs generation to website workflow

Current state
In current state of repository we are able create md file which can be later deployed on the website.
The procedure current looks like:

call make docs-generate this will result with creating the md file in following path ./docs/md_files/schema-reference.md
copy generated md file from ./docs/md_files/schema-reference.md to ./website/src/pages/docs/schema-reference.md
git commit and push new content from ./website/src/pages/docs/schema-reference.md

See scheme below:

Proposal
To automate this more what I propose is:

change the destination md path in make docs-generate from ./docs/md_files/schema-reference.md to ./website/src/pages/docs/schema-reference.md. Therefore we avoid unnecessary copy operation
Important note: I would avoid automatic commit&push done by the Github Action. I would stay with approach that we as maintainers are responsible for git operations on repository. This will results with extend the current Github Actions with following check:

call make docs-generate
check if we see any difference between present and generated schema-reference.md file - git diff will handle this operation
if there are no difference we are good so deploy the website
it there are differences failed with job and we as maintainers should generate md files and perform git commit& push operation

See scheme below for changes in make docs-generate:

See scheme below for current state of Deploy Website GitHub Action:

See scheme below for proposed state of Deploy Website GitHub Action:

@michalbiesek @iapaddler @jrcheli
Should this be for 1.0.4 or 1.1.0?
Or, should we wait until after 1.1.0?

IMHO 1.1.0

Current approach:

I have added logic that  schema-reference.md will be created directly in website/src/pages/docs/
I have added new workflow in GitHub Actions schema.yml:

check if the Pull Request is designated to master branch
check if the changes applies to schema-reference.md related files: docs/schema or docker/docs/layout.js
if yes then run make docs-generate & generate a commit with changes to ./website/src/pages/docs/schema-reference.md`

See last commit https://github.com/criblio/appscope/pull/950

Closing, work was done in #950.


Including original-sin (panic) in report

Choose one: This a 🐛 bug fix
Including original panic-cause in report
Okay so this PR is a bit of a dilemma.
The API we need to get the original panic message isn't stable
and requires a feature flag.
We can conditionally enable the feature flag for nightly users
but that doesn't quite deal with the problem of what to do
when someone is using human-panic on stable.
As far as I can see there's no other API to get that information?
We could always just gate it all away behind the nightly feature
and just ommit a static "not supported" or something when running
on stable.
The tests pass (provided you pass --features nightly for now).
Wanted to open this PR to discuss how to proceed :)

[x] tests pass
[x] tests and/or benchmarks are included
[ ] documentation is changed or added

This fixes #40
This should be a minor bump I believe?
The Report struct isn't exported so adding a field there isn't gonna make a difference 🤷

Sounds good! Thanks for the review!
The doc comment things is really weird, I'll have a look at what might have happened there...

Ping @yoshuawuyts sorry for the delay, I fixed the issues in the code. No idea what caused the issue in the changelog, or how to fix it? What's the tool that is invoked there?

I think I'll just rebase this against master once #49 lands :tada:


feat: add support for GENERATE_UUID

Fix: #173
Checklist

[x] CHANGELOG

Reference

Thanks for the review!


rename RouteTech to NaturalRules

Describe your changes
rename for sake of consistency and good variable names (also this naming was Connor's suggestion)
extent of testing: compiles 😎 (npm test)
Issue ticket number and link
#183

jest still not working (bc i updated the github action .yaml file on xplat/main)
gonna close & reopen this PR


Fix Anope 2.1 not using the right protocol modules.

Something is not right with this. I'll look into it tomorrow.


Cardiovascular Risk Prediction Model

Is your feature request related to a problem? Please describe.
Improve platform's health assessment with a Cardiovascular Risk Prediction Model due to lacking specific tools for assessing users' cardiovascular disease risk, a major global mortality factor.
Describe the solution you'd like
Integrate a Cardiovascular Risk Prediction Model considering age, gender, medical history (hypertension, diabetes), lifestyle (smoking, physical activity), and Biometrics (Body Mass Index, blood pressure) to estimate risk over time. This model will help determine more disease than only heart disease, like strokes and several other.
Describe alternatives you've considered
Integrating a custom Cardiovascular Risk Prediction Model tailored to our platform's user base and data would provide more accurate and personalized risk assessments.
Additional context
Adding this model can help us as it aligns with our goal. This will enhance the overall value of our model.

Please assign this issue to me.

can you please assign me to this issue?
Proposed Solution:
Integrate a comprehensive model that considers:
Demographics: Age, Gender
Medical History: Hypertension, Diabetes
Lifestyle: Smoking, Physical Activity
Biometrics: BMI, Blood Pressure
Steps:
Collect and validate user data.
Customize and implement an existing risk model.
Develop the algorithm using machine learning.
Design a user-friendly interface for data input and risk feedback.
Test and iterate based on user feedback.


AmountInput doesn't work

Looks like I broke it
When putting in a value, it doesn't recognize it in the form.

Only if the comma was added => The wrong value is used for validation

Morrrr tests :)

Not enough time, as sad as it is. Just pushing out features and hoping I have more later on. :/


Refactor endpoints to get rid of kwargs

As @Kami pointed in https://github.com/StackStorm/st2/pull/2727#discussion_r103643612, using **kwargs in controllers require user to constantly keep in mind the list of parameters available for the particular controller or get back and forth between code and spec.
Luckily, as it turns out, we no longer need to use **kwargs in most cases and it's just a matter of refactoring.
The point of this PR is to replace the use of kwargs in every controller it is possible to do and justify it's use in the rest of them.

We can not completely get rid of **raw_filters in .get_all due to how filters are currently implemented in v1 API. We can however be mindful of it and save this issue for v2.

Nice, better :+1:

LGTM :+1:


🐛[BUG]: Pytest getting killed on SFNO package test with wheel install

Version
main
On which installation method(s) does this occur?
Pip
Describe the issue
Getting the classic uninformative:
test/models/px/test_sfno.py::test_sfno_package[cpu] make: *** [Makefile:40: pytest] Killed
Likely a memory issue. Some research suggests pytest can cause memory usage to compound between tests...
One potential solution is to change the models loaded to a fixture to load the models scoped to something, seems tricky problem with these large models.

Fixed by adding explicit memory request in helm chart of test container:
resources:
  requests:
      nvidia.com/gpu: 1
      memory: "64Gi"
  limits:
      nvidia.com/gpu: 1
      memory: "64Gi"


[BUG] rename_keys processor: json pointers with escaped syntax fail to validate

Describe the bug
The escaped syntax for json pointers define how to build json pointers for fields that include special characters.
However, the isValidKey() method in JacksonEventKey only checks the basic character set and keys defined with the escaped syntax are rejected.
To Reproduce
Steps to reproduce the behavior:

Create a pipeline with a rename_keys processor using an escaped syntax:

my-file-pipeline:
  source:
    file:
      path: run/data/events.jsonl
      record_type: event
      format: json
  sink:
    - file:
        path: "run/data/result.jsonl"
  processor:
    - rename_keys:
        entries:
          - from_key: host
            to_key: '"cs(host)"'

Run data-prepper
data-prepper cannot start with the error:

2024-10-28T16:35:39,367 [main] ERROR org.opensearch.dataprepper.core.validation.LoggingPluginErrorsHandler - 1. rp-pipeline-file.processor.rename_keys: caused by: Parameter "entries.null.to_key" for plugin "rename_keys" is invalid: key "cs(host)" must contain only alphanumeric chars with .-_@/ and must follow JsonPointer (ie. 'field/to/key')

Expected behavior
The to_key argument "cs(host)" should be accepted as it conforms to the documented syntax.
Screenshots
N/A
Environment (please complete the following information):

OS: macOs
Version 14.5

Additional context
N/A

@joelmarty , Do you want to produce key names with parenthesis in them?

Perhaps we can make use of escape sequences to allow parenthesis. Right now, our validation just looks for the characters themselves. But, we do not allow them to be escaped.
We have some related work in #5111.

@dlvenable yes, I am trying to produce field names compatible with w3c's extended log file format, that uses the format prefix(header) to designate headers sent in the request or the response. For instance, cs(user-agent) is the field for the user-agent header sent in the request.


Forward the subscribeToMore option to enable usage from useQuery

I did not see subscribeToMore in the observer. Did you test it ? Is it working ?

Hi @seeden , indeed it is part of the prototype of ObservableQuery from apollo-client/core link and is available in the returned observableQuery.
The relevant excerpt of calls is useQuery -> getCachedObservableQuery -> watchQuery -> instance of ObservableQuery -> public method subscribeToMore

Great sounds good. I can not wait :)

@dimitar-nikovski Thanks for your PR, but I'm not sure if it's a good idea to use subscribeToMore with hooks. You'll have to use it with the useEffect or useLayoutEffect hook and ensure that the array with correct variables is passed as the second argument of that hook and a proper unsubscribe function returned. Otherwise, you'll risk that the subscription will be subscribed/unsubscribed after each update (even if arguments won't be changed) or not resubscribed at all if they changed. In my opinion, a much better solution is the useSubscription hook which is WIP in #37. Are you aware of any use cases of subscribeToMore which wouldn't be possible to solve with useSubscription (or ApolloClient.subscribe which it will use under the hood)?

I am using it like this
export default (query, options: Options = {}): Object => {
  const { onReady, ...rest } = options;
  const [subscribed, setSubscribed] = useState(false);
  const response = useQuery(query, {
    suspend: false,
    ...rest,
  });

  const { loading, error } = response;
  if (error) {
    throw error;
  }

  if (!loading && !subscribed && onReady) {
    setSubscribed(true);
    onReady(response);
  }

  return response;
};

useQuery(query, {
onReady({ subscribeToMore } => {
...
}),
})

@seeden What do you think about that API:
const response = useQuery(query, {
  // query options
});

const subscriptionResult = useSubscription(subscription, {
  // subscription options
});

We could add a skip option for both useQuery and useSubscription to start them conditionally (#21).

@trojanowski  I am fine with useSubscription. I think that many users will not use subscriptionResult. They will use just updateQuery from subscription options

Actually updateQuery is related to useQuery. I need to combine useQuery and useSubscription.

@trojanowski I was thinking about it and I recommended to use both

forward subscribeToMore for queries because it is related to current query.
add useSubscription as well. If user want to use just response from subscribe without updating query

Hi @seeden, now it should be much better, as @trojanowski pointed out, there are necessary conditions to set it up properly. I don't expect it to be merged, unless there is genuine desire from more people for it to be part of the project, for me, it mainly helps with the convenience of merging the subscription updates back into the store with updateQuery.

[x] - unsubscribe from the subscription in useEffect if it has been set up
[x] - only resubscribe if the variables or document (gql) have changed, also the recommended way, source

Conveniently, when merging the results in updateQuery, Apollo's ObservableQuery will schedule an update which will broadcast right into the subscription made in useQuery, therefore then setting a new result as if it was a change in query result, so that would then become query + subscription merged.

Hi @dimitar-nikovski thank you for your update 👍. Actually I am using subscribeToMore only with updateQuery. But it is related to useQuery because I am using old query result in the updateQuery (it is standard in the react-apollo and Query component I guess). I am merging edges most of the time.

I ought to add some tests, just in case it will be going further.

What do you think about the API suggested in https://github.com/trojanowski/react-apollo-hooks/pull/37#issuecomment-450200481? It would allow to update any previous query.

Do you think it would solve all your use cases for subscribeToMore or you still need it?

@trojanowski it's cleaner indeed, we can use the subscription result from useSusbscription and the updateQuery prop form ObservableQuery returned by useQuery and achieve the exact same result. Feel free to close this down.


Skip running fork choice if there is already a previous update still in progress

PR Description
Currently we run fork choice and then may fail to actually apply the new chain head because a new change comes in while we were regenerating the state.  Instead if we're still waiting for a previous result to apply, skip running fork choice entirely.
Documentation

[x] I thought about documentation and added the documentation label to this PR if updates are required.

This has not proven effective. Need to try a different approach.


Make a request from python code to free web service

Henna working on this

Installed git on windows
Installed python on windows
Created a script in python requesting weather details from Json API
Created branch on git
Pushed the script onto the branch(Heena_KRAR).

Displayed the python script's output(JSON object) in a html format(to browser)

2 python scripts added to one single python script using function definitions

Cannot push the script to git


Error told me to create an issue

I work with a few repos at work that us TS.  When I add //ts-worksheet at the top of any file and save I get this error:
ts-worksheet: An Error happend during the running of the worksheet. If you think there is something wrong with the plugin, please file an issue: : Error: Manipulation error: A syntax error was inserted. Users/adam.hinckley/projects/exit-offer-customizer-ui/src/util/.toedit.ts:123:13 - error TS1005: '>' expected. 123 status="error"    ~~~~~~ Users/adam.hinckley/projects/exit-offer-customizer-ui/src/util/.toedit.ts:123:19 - error TS1005: ',' expected. 123 status="error"    ~ Users/adam.hinckley/projects/exit-offer-customizer-ui/src/util/.toedit.ts:124:13 - error TS1005: ',' expected. 124 message={    ~~~~~~~ Users/adam.hinckley/projects/exit-offer-customizer-ui/src/util/.toedit.ts:[93...

It looks like it's saying there is a file called .toedit.ts in my util folder, but that file does not exist in my repo anywhere.

Hi thanks for opening this issue. Could you show me the file you added //ts-worksheet to it? This .toedit.ts is a temporary file which gets created by ts-morph.

It looks like wrapping code which i create from your file is not valid

I'm getting the same thing. It seems to break on my stitches components.

@smol-honk do you have a code example?

@smol-honk do you have a code example?

Unfortunately it's my work code. I'll try to put together something with the same stack to share.

Would be great. A minimal reproducible example would be nice.

I've done a basic example with styled and createStitches but did not receive any errors. Would be great to see where it fails for you. Which function for example.

Currently it's not possible to support stuff beside ts files. So I sadly have to close the issue


v1.0 plan detail

Fix bugs
UI re-designed
Some graph
Windows support

focus on gui

will not support Windows.