click.prompt fails with UnicodeEncodeError on Windows

I get this failure:
Traceback (most recent call last):
  File "c:\program files\python 3.5\lib\runpy.py", line 170, in _run_module_as_main
    "__main__", mod_spec)
  File "c:\program files\python 3.5\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Program Files\Python 3.5\Scripts\cookiepatcher.exe\__main__.py", line 9, in <module>
  File "c:\program files\python 3.5\lib\site-packages\click\core.py", line 700, in __call__
    return self.main(*args, **kwargs)
  File "c:\program files\python 3.5\lib\site-packages\click\core.py", line 680, in main
    rv = self.invoke(ctx)
  File "c:\program files\python 3.5\lib\site-packages\click\core.py", line 873, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "c:\program files\python 3.5\lib\site-packages\click\core.py", line 508, in invoke
    return callback(*args, **kwargs)
  File "c:\program files\python 3.5\lib\site-packages\cookiepatcher\cli.py", line 95, in main
    extra_context=extra_context,
  File "c:\program files\python 3.5\lib\site-packages\cookiecutter\main.py", line 129, in cookiecutter
    context['cookiecutter'] = prompt_for_config(context, no_input)
  File "c:\program files\python 3.5\lib\site-packages\cookiecutter\prompt.py", line 129, in prompt_for_config
    val = read_user_variable(key, val)
  File "c:\program files\python 3.5\lib\site-packages\cookiecutter\prompt.py", line 28, in read_user_variable
    return click.prompt(var_name, default=default_value)
  File "c:\program files\python 3.5\lib\site-packages\click\termui.py", line 86, in prompt
    value = prompt_func(prompt)
  File "c:\program files\python 3.5\lib\site-packages\click\termui.py", line 69, in prompt_func
    echo(text, nl=False, err=err)
  File "c:\program files\python 3.5\lib\site-packages\click\utils.py", line 314, in echo
    file.write(message)
  File "c:\program files\python 3.5\lib\encodings\cp437.py", line 19, in encode
    return codecs.charmap_encode(input,self.errors,encoding_map)[0]
UnicodeEncodeError: 'charmap' codec can't encode character '\u0103' in position 27: character maps to <undefined>

Is unicode text not supported in prompts?

Can you provide a testcase?

Actually, no testcase needed.  You are writing a character to the console that the windows console does not support in the codepage you provided.  Python does not support unicode for the windows console.

Should at least it show some garbled output? Why does the app need to care about this - isn't click supposed to handle these sort of situations?

Ok, seems to work if I chcp 65001 but I still wonder if click could just handle this.

There was some discussion about this.  We could do that but then our stdout behaves differently than the built-in Python one which especially on Python 3 has some bizarre consequences where some surrogate escape based apis will no longer behave as you expect on 3.4 and higher.
It's not entirely sure what to do there.  The absolutely correct thing to do would be to use the unicode APIs for cmd.exe but I cannot see a way to actually do that from within Python because that would require bypassing stdout entirely.
Feel free however to open a feature request separately for making this configurable at the very least or to get more opinions on how to deal with this.

@ionelmc unfortunately cp65001 is ludicrously broken on windows otherwise we would already do this :(


Fix invalid ignore pattern for underscore files

Was discussed here: https://github.com/cloud-annotations/docusaurus-openapi/pull/107#discussion_r772093391
Closes #232

Is GlobExcludeDefault used anywhere else? Can we just add **/category.{json,yaml,yml} to it so we don’t need to do the filtering or pushing of the spec files?

True! That should work just fine 👌

Hmm it looks like the demo isn’t picking up the _spec_ 🤔
I didn’t realize the default glob is coming directly from Docusaurus, so maybe they changed their glob in a newer version?

That's a mystery for me, I checked the file history that contains the GlobIgnore pattern, it has never changed 🤔 I'll investigate and let you know

It's this pattern "**/_*/**" that excludes _spec_.* files.
Let's just not rely on GlobExcludeDefault for this source fetching. It's useless.


bytebuffer.js - this.view is never null

related issue: https://github.com/dcodeIO/bytebuffer.js/issues/79

Iirc this behavior is intended for consistency because the DataView-version must do this, as there are no empty data views.


8 to 9 20210104

This merges transport8 to transport9, which is just topic statistics.

We should require ign-msgs 6.2 on CMakeLists.
Done in edccca4df40dbaed94da6db26f367bb1898e9e1f

We should require ign-msgs 6.2 on CMakeLists.
Done in edccca4df40dbaed94da6db26f367bb1898e9e1f

I'm not sure why the Windows CI is not finding the statistics message.

It looks like CI is using an old branch:
Installing branch master of ign-msgs

I'm not sure why the Windows CI is not finding the statistics message.

It looks like CI is using an old branch:
Installing branch master of ign-msgs


Refactor UserProgressController

fixed #633

Codecov Report

Merging #640 into master will not change coverage.
The diff coverage is 0%.

@@          Coverage Diff           @@
##           master    #640   +/-   ##
======================================
  Coverage    35.3%   35.3%
======================================
  Files          40      40
  Lines         946     946
  Branches       18      18
======================================
  Hits          334     334
  Misses        612     612

Impacted Files
Coverage Δ

...scalaexercises/exercises/controllers/package.scala
0% <ø> (ø)
:arrow_up:

...exercises/services/interpreters/interpreters.scala
0% <0%> (ø)
:arrow_up:

...exercises/controllers/UserProgressController.scala
0% <0%> (ø)
:arrow_up:

...ercises/exercises/controllers/UserController.scala
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Works fine 2

[Enter feedback here]
The numeric calculations in .NET editor works fine there are no issues that I have encountered
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 37ce5a16-aa17-7f0b-3a6f-aa00cb17949c
Version Independent ID: d714c86e-bb00-a07d-eb7e-e3235acb1fb8
Content: Numbers in C# - Introduction to C# interactive tutorial
Content Source: docs/csharp/tour-of-csharp/tutorials/numbers-in-csharp.yml
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Everything works well no issue


Added WaultPoly MATIC-USDC, MATIC-ETH

Moo WexPoly MATIC-ETH
Vault: 0x5c0174Db34B7eb0F46bC895340113f4427AC9e02
Strat: 0x9Cc44B40E652a4Ede4E19c7cBdDADe78866DdCaa
Want: 0x679B8Ab80F298bF802fB294137765C6386D43dcA
Moo WexPoly MATIC-USDC
Vault: 0xD4E0D1EfEd5cDbD1c4205748a325253Eb596A7bF
Strat: 0x71A348BCd9920Cc472958f8222Cb12DFCdc8EF7d
Want: 0x8312A29A91D9Fac706F4d2ADEB1FA4540faD1673

lpToken0 and outputToLp0 don't match, it works because they are reversed but wouldn't for "WEX-xxx" LPs.
should we redeploy with correct values?

lpToken0 and outputToLp0 don't match, it works because they are reversed but wouldn't for "WEX-xxx" LPs.
should we redeploy with correct values?

Done 👍


libxshmfence: 1.2 -> 1.3 fixes memfd_create usage w/musl

I think needed for newer glibc versions as well, FWIW.

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

Errr @GrahamcOfBorg that can't be right, many things use libxshmfence ! :(

Simple explanation: We're already at 1.3:
https://github.com/NixOS/nixpkgs/blob/868f2561b54979a11f62f7451489f94335855530/pkgs/servers/x11/xorg/overrides.nix#L269
You edited the wrong file :smile:
https://github.com/NixOS/nixpkgs/blob/868f2561b54979a11f62f7451489f94335855530/pkgs/servers/x11/xorg/default.nix#L1


feat: add support for "autorotate"

How do you guys handle rotated images with this amazing module? We currently see issues displaying those and would be interested in  either supporting this as a  properly here (like Ti.UI.ImageView) or via pre-processing. Thank you!

according to https://github.com/bumptech/glide/pull/3444#issuecomment-447421962 it will already autorotate based on the exif information.
Check the image if it actually has EXIF infos. Some manufacturer store data in strange ways which makes it hard to find the proper orientation on different devices

The version linked (merged December 5) is not used in AV.ImageView so far I think, but maybe latest master does! I have to try.

the lnked issues add a custom rotation to glide. They just mention in the ticket that it is already using exif Glide will already parse exif and rotate images according to the exif.. I didn't test the images from  https://github.com/recurser/exif-orientation-examples yet

I close this issue, the latest versione as you know uses glide 4.9.0 and exif should be correctly handled. Reopen this if this is not working as expected.


advice

http://ionicframework.com/docs/v2
It seems that  i can't find descriptions of update.
Recently,it changes.

Hello, thanks for using Ionic! All our changes are always listed on our changelog here. For major releases we also usually do a post on our blog.


Update data_io.py

update @st.cache to @st.cache_data

also the third option (uploading csv) is not working because the "_tree.py" and "_tabular.py" files in shap package have "np.bool" and "np.int" that need to be changed to "bool" and "int"


Add semantic convention for AWS ECS Service

What are you trying to achieve?
Add aws.ecs.service.name to AWS ECS resource attributes.
What did you expect to see?
ECS Service name is set to aws.ecs.service.name.
Additional context.
AWS ECS Service name is available in ECS Task Metadata API V4. https://github.com/aws/amazon-ecs-agent/pull/3362
Currently, it is only detected in awsercscontainermetricsreceiver in https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/19744. The same detection can also be achieved in OTEL SDKs, but since it's not included in semantic conventions, the agent cannot proactively report the attribute to OTEL collector.

Related: https://github.com/open-telemetry/semantic-conventions/pull/576#issuecomment-2115510275

Also #600


Why is a Shockwave Flash SWF file included

We noticed that<EMAIL_ADDRESS>has a dependency on node-forge<EMAIL_ADDRESS>is includes swf/SocketPool.swf, apparently for some special networking features that can be optionally use a Flash component. As you know most browsers have disabled flash support for security reason. But customers are not allowing flash components (.swf files etc.) to be deployed.
Can this be cleaned up from google-p12-pem?

Hi @mehboob-at-ibm,
Are you aware of any replacement for node-forge that can be used instead of it?
I will keep this PR open as a feature request for now; if the existence of this swf file bothers anyone else, please +1 and we'll see what we can do. Probably one easy thing we could technically do without rewriting the code is forking node-forge and shipping the fork without an swf file. If any of the folks who experience this problem has a support contract, please mention this issue there.
Thank you!

@alexander-fenster I am not aware. But I am not sure if " swf/SocketPool.swf" is really useful/needed anymore either.
There is an open an issue on the node-forege side as well - https://github.com/digitalbazaar/forge/issues/843

I think we should work on internalizing the key functionality for node-forge - we use a very limited subset of it's API capabilities.
Related: It's also the largest dependency for downstream modules, such as @google-cloud/storage, which include node-forge from this package:

https://github.com/googleapis/nodejs-storage/issues/1888

visual representation: https://bundlephobia.com/package/<EMAIL_ADDRESS>


[Bug] Semver rules & current branch

Hey! I noticed two bugs while setting up this action and testing it.

[ ] 1. The action fails while pushing due to fatal: couldn't find remote ref master
[ ] 2. Pre-Release generates invalid/wrong semver version

I've the following step

      - name: Create bump and changelog
        uses: commitizen-tools/commitizen-action@master
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          changelog_increment_filename: body.md
          prerelease: ${{ steps.is_main.outputs.prerelease_type }}

and everything works expect the pushing. This is because the action tries to push to master, but I'm using main. Sadly I can't hard-code it, because I'm listening to multiple branches (for pre-release branches)

While testing I've noticed it generates for a (beta) pre-release the following version 1.1.0b0 but it should be 1.1.0-beta(.0) instead (see semver rules)
In their example for which version is lower and higher, they have the following Example: 1.0.0-alpha < 1.0.0-alpha.1 < 1.0.0-alpha.beta < 1.0.0-beta < 1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1 < 1.0.0.

I hope it's okay, that I've not split this issue in two, that's why I've created checkboxes.

This action uses the CURRENT_BRANCH variable now. Or you can specify it in the action.
The problem with semver is part of commitizen, as you pointed out.


v1.3 scan: CAMD Services: Med 1

CampDv1.3APIupdate.xlsx
Application Information Leakage is an application weakness
where an application reveals sensitive data, such as
technical details of the web application or environment.
Application data may be used by an attacker to exploit the
target web application, its hosting network, or its users.
Therefore, leakage of sensitive data should be limited or
prevented whenever possible. Information Leakage, in its most
common form, is the result of one or more of the following
conditions: A failure to scrub out HTML/Script comments
containing sensitive information or improper application or
server configurations.
Failure to scrub HTML/Script comments prior to a push to the
production environment can result in the leak of sensitive,
contextual, information such as server directory structure, SQL
query structure, and internal network information. Often a
developer will leave comments within the HTML and/or script
code to help facilitate the debugging or integration process
during the pre-production phase. Although there is no harm in
allowing developers to include inline comments within the
content they develop, these comments should all be removed prior
to the content's public release.
Software version numbers and verbose error messages (such as
ASP.NET version numbers) are examples of improper server
configurations. This information is useful to an attacker by
providing detailed insight as to the framework, languages, or
pre-built functions being utilized by a web application. Most
default server configurations provide software version numbers
and verbose error messages for debugging and troubleshooting
purposes. Configuration changes can be made to disable these
features, preventing the display of this information.
Error Message Exposed via 'GET api.epa.gov/easey/staging/camd-services/*'

I think there is no application leakages.
%0a%2fusr%2fbin%2fenv%0a = usr/bin/env
When scanning this application, they try to pull the usr/bin/env file by using https://api.epa.gov/easey/staging/camd-services/
%2Fusr%2Fbin%2Fenv
/100 then the Nginx throw the error 500 internal server error instead of 403: Access Denied/Forbidden . I believe it is good throw error rather than leaking the urs/bin/env data.

False Positive. Approved reclassification on 3/4/2040


integrate social media links to footer

namely:

facebook
wechat
youtube
instagram
linkedin

this was implemented by PR #14


Fibaro Co2 Sensor FGCD-001 show up as unknown

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.55.2 (hassio)
Python release (python3 --version):
Python 3.6.1
Component/platform:
zwave
Description of problem:
Fibaro Co2 Sensor FGCD-001 show up as unknown sensor.fibaro_system_unknown_type1201_id1000 even though it has an entry in the /open-zwave/blob/master/config/manufacturer_specific.xml

Expected:
The sensor should show up as "FGSD001 CO Sensor" as defined in the zwave manufacturer config.
Additional info:
Tried adding and removing the sensor 3 times before i gave up.

Home Assistant has most recently updated to <IP_ADDRESS> of python-openzwave. That was created on the 6th of June 2017. Support for FGCD-001 was added to OpenZWave on 25 July 2017.
You'll need the python-openzwave maintainers to release an updated version so that Home Assistant can include it.

Ah. I was looking at the openzwave and though that was it. I'll take contact to the python-openzwave team.
Thanks!


Support for .Net 5.0

Describe the solution you'd like
I am using AppCenter for Xamairn and I have updated my code to support C# 9. It's not compiling on AppCenter anymore.
Is there any roadmap to support .Net 5.0?
Describe alternatives you've considered
For now, I have created a post clone script following this - https://codetraveler.io/2019/08/23/using-preview-versions-of-net-core-with-app-center-build/

Duplicate of https://github.com/microsoft/appcenter/issues/86. We are working on .NET 5.0 support. Should be available by the end of the year.

@sawankumarbundelkhandi did you manage to get it to work with a post-clone script? Can you provide an example? Thanks in advance.


Provider Request

Yomovies: https://github.com/miru-project/repo/blob/main/repo/yomovies.js
Kisshk: https://github.com/miru-project/repo/blob/main/repo/kisskh.co.js

sorry but I can't take more provider requests for now I am already at limit

sorry but I can't take more provider requests for now I am already received many requests that's it practically not possible

Kisshk is api based so I think it's more practical and easier to add for you?

oh that would be easy, I will try that

Can u add olamovies.baby also

Can u add olamovies.baby also

Its not possible to add olamovies.
Join discord if you want more info on that.


[modify] send_file headers : forcibly set Content-Disposition attachment when ie11

Coverage decreased (-13.7%) to 70.533% when pulling aa64f0ad1914b6f92443542e94cd30aa45697090 on itowtips:content-disposition into a7d03e008d23b059626649fcd62f6e6a922f1953 on shirasagi:master.


Refactor docs generator to find .dll from csproj file

[x] The documentation generator should not need the hardcoded path to the DLL file. The values are available from the csproj file.
[ ] Extend logging
[ ] Add table to Table of Contents: Friendly Name | Ignorable | Message

Also add more logging please. :)

Wrote a new ps to extract the info from the project file. I have a need for it as well to auto create a release if I can figure it out.


Null Safety

Please migrate this package to Null-Safety.

This migration will happen on 0.6.1 version.

Do you have any predictions for the release date?

Today!


ISSUE: Schlage FE599 Door check

Describe the bug
For some locks such as Schlage FE599nx Lever lock the door status is always open since the lock can't detect open or close. However with this issue the auto lock feature stops working. It will just keep resetting to 30 secs
Environment (please complete the following information):

OS: HassOS
Type of system that HA is running on:  RPi4
Home Assistant version: core-2021.10.0
Hassio
Component version: [e.g. 0.1.2]
Z-Wave integration name: zwave_js
Lock make and model: Schalge fe599nx

Logs
Screenshots
Additional context
Can we add a way to turn off the door status check?
right now what i did was delete the check from the packages
 - alias: keymaster_front_door_timer_finished
    trigger:
      platform: event
      event_type: timer.finished
      event_data:
        entity_id: timer.keymaster_front_door_autolock
    action:
      - service: lock.lock
        entity_id: lock.front_door

Sorry I am not sure why I didn't get notified of a reply.
Yes, I can disable the auto lock however then my lock will not auto lock if I use the manually unlock the door.
Side note: deleting the condition: seems to work even after many updates so feel free to close this issue if there are no plans to add a switch to disable the door status condition.


OAuth2 client credentials, access token support, pingfederate_oauth_client resource bug fix

OAuth2 Client Credentials Flow Support
Access Token Support
pingfederate_oauth_client resource grant_types bug fix

It might be nice to have a test that confirms that the provider gracefully fails when no auth is configured at all, with the expected error message.


Upgrade NBitcoin to .NET Standard 2.0

Integration tests pass and same NBitcoin tests pass as prior to update.

Hi @mikedennis any special reason to do this?
We still have some components  that relay on NBitcoin being 1.6 if I am not mistaken.

I don't think so unless they are external to the full node, everything I checked there seems to be at 2.0. I was mainly removing the 4.61 framework build because that errors when you try to build on linux/osx but I can revert back to 1.6 if you think we need it for something.

The BlockExplorer is using NBitcoin but from the NBitcoin repo, so what we do here doesn't affect it.
And when BlockExplorer is using the full node, it's using the nuget package.
I think this can be changed to .NETStandard without problem.

I think this can be changed to .NETStandard without problem.

It is already .NETStandard you mean to 2.0 I guess.
yeah  4.61 and 1.6 where there for a reason block explorer and indexer (and also older versions of those use it, how much they use it is not clear)
@quantumagi  @YakupIpek can perhaps provide some info

@YakupIpek what do you think?
NStratis has now moved to be inside the full node solution.
From what I see, you're using the StratisBitcoinFullNode projects in Stratis.Bitcoin.Features.AzureIndexer.csproj which targets netstandard2.0, in Stratis.Bitcoin.Features.AzureIndexer which targets netstandard2.0 and net471.
Does Stratis.Bitcoin.Features.AzureIndexer really need to target net471?
What do you think, can we move NStratis in the StratisBitcoinFullNode to be netstandard2.0? Do yo plan to get a new version of the Stratis.Bitcoin anytime soon?

@andrasfuchs I'm not sure what exactly NETSTANDARD1_6 is being used for but in latest version of NBitcoin I notice Nicolas is no longer using that conditional compile. Probably another future PR to get rid of NETSTANDARD1_6 define and replace it with whatever NBitcoin is currently using as he doesn't seem to be using version specific ones anymore.


Update RSC journals

See https://github.com/citation-style-language/journals/pull/34#issuecomment-283976387

Closed per https://github.com/citation-style-language/journals/commit/54a7fcd47cbb2938e4243c7aa2a1160a8dd49a51


aws-c-common: 0.6.17 -> 0.6.18

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/aws-c-common/versions.
meta.description for aws-c-common is: "AWS SDK for C common core"
meta.homepage for aws-c-common is: "https://github.com/awslabs/aws-c-common"
meta.changelog for aws-c-common is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.6.18 with grep in /nix/store/744znvvcjlffw62b3y22rr9jkn4zz3mc-aws-c-common-0.6.18

found 0.6.18 in filename of file in /nix/store/744znvvcjlffw62b3y22rr9jkn4zz3mc-aws-c-common-0.6.18

Rebuild report (if merged into master) (click to expand)

194 total rebuild path(s)

115 package rebuild(s)

114 x86_64-linux rebuild(s)
80 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
arrow-cpp
aws-c-auth
aws-c-cal
aws-c-common
aws-c-compression
aws-c-event-stream
aws-c-http
aws-c-io
aws-c-mqtt
aws-c-s3
aws-c-sdkutils
aws-checksums
aws-crt-cpp
aws-sdk-cpp
bundix
cabal2nix
cached-nix-shell
cachix
common-updater-scripts
crate2nix
crystal2nix
dep2nix
docbookrx
dydisnix
fusionInventory
go2nix
haskellPackages.cabal2nix-unstable
haskellPackages.cachix
haskellPackages.hercules-ci-agent
haskellPackages.hercules-ci-cli
haskellPackages.hercules-ci-cnix-expr
haskellPackages.hercules-ci-cnix-store
haskellPackages.nix-paths
haskellPackages.nvfetcher
haskellPackages.update-nix-fetchgit
hci
hercules-ci-agent
hubstaff
hydra-unstable
libnixxml
lispPackages.quicklisp-to-nix
lispPackages.quicklisp-to-nix-system-info
nix
nix-bundle
nix-direnv
nix-doc
nix-du
nix-eval-jobs
nix-index
nix-pin

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/744znvvcjlffw62b3y22rr9jkn4zz3mc-aws-c-common-0.6.18 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A aws-c-common https://github.com/r-ryantm/nixpkgs/archive/117e4df1bb94acbf11ddd5c34aa3e5fb9270e429.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/744znvvcjlffw62b3y22rr9jkn4zz3mc-aws-c-common-0.6.18
ls -la /nix/store/744znvvcjlffw62b3y22rr9jkn4zz3mc-aws-c-common-0.6.18/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @orivej @edolstra @r-burns for testing.

@GrahamcOfBorg eval

@ofborg build nix

I think the ofborg timeouts are due to mass rebuilds on staging. Cherry-picked back to master and built nix on x86_64-darwin, and the upstream changes are pretty minor, so I think this is good to go.


Fix concourse should use renamed git-master resource in files

What
I renamed a resource and missed a couple of references

https://github.com/alphagov/govuk-coronavirus-find-support/pull/111


[$250] Migrate MoneyRequestParticipantsSplitSelector.js to function component

Class Component Migration
Filenames

[ ] [src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsSplitSelector.js](https://github.com/Expensify/App/blob/main/src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsSplitSelector.js)

type: React.Component
has state values: true
has refs: false
has context: false
lifecycle methods: none

Task

We currently have some class components in our codebase that we would like to refactor to a function component.
Here's a link with some general advice on how to refactor a class component to a function component: https://react.dev/reference/react/Component#alternatives
If you need additional guidance, please ask in #expensify-open-source
Test for any regressions and verify that there are no breaking changes

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01a5adde5530f45b97
Upwork Job ID:<PHONE_NUMBER>805845504
Last Price Increase: 2023-06-05

⚠ Could not update price automatically because there is no linked Upwork Job ID. The BZ team member will need to update the price manually in Upwork.

Heads up, I'm taking this issue off HOLD and making it a Daily. If you are unable to work on it please remove your assignment and add the External + Help Wanted labels as per this update.

The page is now named: MoneyRequestParticipantsSplitSelector. I see state being used, so will investigate further.

Phew. This one has it all:

Class component
State
componentDidUpdate

I'm struggling to break this down into smaller changes. I'm tempted to open this one up and pick up a simpler migration.

I want to work on it

I tried but this was a tricky refactor for my first attempt, specifically the large getSections function was where I started to fail.
@multijump I'd be happy to assign this to you while I pick up a simpler one for my first migration.

Great, I look forward to learning from you here 😄

Sorry my mistake. I'm going to assign @multijump for this task.

Thanks for your considering me, @Julesssss
I will put my PR tomorrow.

Can I work on it ?

so do i have to apply now on upwork? or you will reach out to me.

@rahmanasad222 you need to apply on upwork

Thanks @Vishrut19, @s-alves10 and @rahmanasad222.
I have already assigned Multijump for this task and another member of our team will be soon assign them in UpWork. Please review our process here.

@Julesssss
I created the PR https://github.com/Expensify/App/pull/20271
Please give me your feedback.

Monitoring PR - https://github.com/Expensify/App/pull/20271

Monitoring PR - https://github.com/Expensify/App/pull/20271

⚠ Looks like this issue was linked to a Deploy Blocker here
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

Hello @allroundexperts @Christinadobrzyn
So everything is fine now?
Or there is something which I should change?

Yeah, just to clarify we closed the linked issue as expected behavior.

Hi @Julesssss @Christinadobrzyn
This issue was fully completed?

Hi @Christinadobrzyn, this issue is ready to be paid when you're back from OOO.

okay hiring @allroundexperts as C+ and @multijump as contributor.
Upwork Internal posting - https://www.upwork.com/ab/applicants/1681244482343641088/job-details
Upwork External posting - https://www.upwork.com/jobs/~01ced557c4c463eb04
@multijump can you provide your Upwork profile link so I can invite you?

okay hiring @allroundexperts as C+ and @multijump as contributor.
Upwork Internal posting - https://www.upwork.com/ab/applicants/1681244482343641088/job-details Upwork External posting - https://www.upwork.com/jobs/~01ced557c4c463eb04
@multijump can you provide your Upwork profile link so I can invite you?

Hi, @Christinadobrzyn
https://www.upwork.com/freelancers/~0168534bdf28bd4cf8
Here is my upwork profile.
Thanks.

@allroundexperts is paid

Thanks @multijump - sent an offer to you, if you can accept it, I'll pay this out!

Hi, @Christinadobrzyn
I accepted your offer.
Thanks.

Thanks @multijump! I've paid you $250 through Upwork. Going to close this GH and the Upwork job posting but please reopen if I've missed something!


feat: add pull_request_target to main.yml

#185  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tremarkley and the rest of your teammates on  Graphite


Fix dev mode

:tada: This PR is included in version 1.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Failed to activate the script package

[Enter steps to reproduce below:]

Install the script package,
Profit? :(

Atom Version: 0.187.0
System: Unknown Windows Version
Thrown From: script package, v2.18.0
Stack Trace
Failed to activate the script package
At undefined is not a function

TypeError: undefined is not a function
  at ScriptOptionsView.module.exports.ScriptOptionsView.initialize (C:\Users\Christian\.atom\packages\script\lib\script-options-view.coffee:51:37)
  at ScriptOptionsView.View (C:\Users\Christian\AppData\Local\atom\app-0.187.0\resources\app\node_modules\atom-space-pen-views\node_modules\space-pen\lib\space-pen.js:184:25)
  at new ScriptOptionsView (C:\Users\Christian\.atom\packages\script\lib\script-options-view.coffee:6:3)
  at Object.module.exports.activate (C:\Users\Christian\.atom\packages\script\lib\script.coffee:28:30)
  at Package.module.exports.Package.activateNow (C:\Users\Christian\AppData\Local\atom\app-0.187.0\resources\app\src\package.js:240:19)
  at C:\Users\Christian\AppData\Local\atom\app-0.187.0\resources\app\src\package.js:221:30
  at Package.module.exports.Package.measure (C:\Users\Christian\AppData\Local\atom\app-0.187.0\resources\app\src\package.js:167:15)
  at Package.module.exports.Package.activate (C:\Users\Christian\AppData\Local\atom\app-0.187.0\resources\app\src\package.js:214:14)
  at PackageManager.module.exports.PackageManager.activatePackage (C:\Users\Christian\AppData\Local\atom\app-0.187.0\resources\app\src\package-manager.js:465:21)
  at C:\Users\Christian\AppData\Local\atom\app-0.187.0\resources\app\node_modules\settings-view\lib\package-manager.js:268:29
  at exit (C:\Users\Christian\AppData\Local\atom\app-0.187.0\resources\app\node_modules\settings-view\lib\package-manager.js:43:16)
  at BufferedProcess.triggerExitCallback (C:\Users\Christian\AppData\Local\atom\app-0.187.0\resources\app\src\buffered-process.js:63:47)
  at ChildProcess.<anonymous> (C:\Users\Christian\AppData\Local\atom\app-0.187.0\resources\app\src\buffered-process.js:85:18)
  at ChildProcess.emit (events.js:119:17)
  at Process.ChildProcess._handle.onexit (child_process.js:1072:12)

Commands
     -2:19.2 core:move-left (atom-text-editor.editor.is-focused)
  3x -2:18.8 core:select-left (atom-text-editor.editor.is-focused)
     -2:08.4 core:move-up (atom-text-editor.editor.is-focused)
  3x -2:07.8 core:select-left (atom-text-editor.editor.is-focused)
  3x -2:05.7 core:move-down (atom-text-editor.editor.is-focused)
     -2:05.0 core:move-up (atom-text-editor.editor.is-focused)
     -2:04.5 core:move-down (atom-text-editor.editor.is-focused)
     -2:04.2 core:move-left (atom-text-editor.editor.is-focused)
  2x -2:03.9 core:move-right (atom-text-editor.editor.is-focused)
  4x -2:03.5 core:select-left (atom-text-editor.editor.is-focused)
  8x -2:02.1 core:move-up (atom-text-editor.editor.is-focused)
  8x -2:00.5 core:move-down (atom-text-editor.editor.is-focused)
     -1:59.3 core:move-up (atom-text-editor.editor.is-focused)
     -1:58.7 core:save (atom-text-editor.editor.is-focused)
  2x -1:57.2 core:close (atom-text-editor.editor.is-focused)
     -1:54.5 settings-view:open (atom-text-editor.editor)

Config
{
  "core": {
    "themes": [
      "atom-dark-ui",
      "atom-dark-syntax"
    ],
    "autoHideMenuBar": true
  }
}

Installed Packages
# User
script, v2.18.0

# Dev
No dev packages

Having the same issue after updating to 0.192.0

oh interesting - I just had this happen when going from Atom 0.196 to 0.198.

I just updated everything (including Atom), and it's working perfectly for me. Script version is 2.21.0.


cp.nonzero, and cp.where Synchronizes Device, can not Run Concurrently

CuPy Version : 7.8.0
CUDA Root : C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1
CUDA Build Version : 10010
CUDA Driver Version : 11000
CUDA Runtime Version : 10010
cuBLAS Version : 10100
cuFFT Version : 10010
cuRAND Version : 10010
cuSOLVER Version : (10, 1, 0)
cuSPARSE Version : 10010
NVRTC Version : (10, 1)
cuDNN Build Version : 7605
cuDNN Version : 7605
NCCL Build Version : None
NCCL Runtime Version : None
CUB Version : None
cuTENSOR Version : None
When I use cp.nonzero, and as a result, cp.where, synchronizes the device, and breaks concurrency.
Under the implementation code, I found this line, return nonzero(condition) # may synchronize, indicating that there may be further synchronization in the source code. In the map_reduce.py, under the streams example folder, if I generate a random array x = rand.normal(size=(1024**2)) and replace matmul with cp.nonzero(x>0.5) or cp.where(x>0.5), and profile the application with the visual profiler, I get this result: https://drive.google.com/file/d/1OsVM_Lhcz2L3NIQb8MLgULzTADWc5AnG/view?usp=sharing, showing the serial code. Does anyone have an alternative method to replace cp.where or cp.nonzero that will work synchronizes, or am I using the functions incorrectly?

Please see this comment: https://github.com/cupy/cupy/issues/4026#issuecomment-702025770


Python Tooltip when hovering long string overlap mouse

(Reported at https://developercommunity.visualstudio.com/content/problem/109893/python-tooltip-when-hovering-long-string-overlap-m.html)
When editing a Python script, if we put the mouse over a string value waiting  for a second, a tooltip appears near the mouse displaying the string.
Generally the tooltip is display on bottom right of the mouse, which is OK.
However, if we have a long multiline string, let's say taking most of the screen height, then the tooltip appears behind the mouse (see attached screen) making almost impossible to select the text itself. We have to continuously fighting against this damned tooltip to select the text.
I didn't found any option to turn off this tooltip.
I don't know if it's related to python only or if it's the case for other languages too.

We should really just trim the string contents in tooltips. It's easy enough to F12 or Ctrl+Click to see the full string, and the most valuable uses of this are when the string length is short anyway.

It's also pretty annoying when you are trying to CTRL click. You have to race against the tooltip.

Actually, we only show them on the literal itself... let's just stop doing that.

For me it was a problem hovering on json.dumps (which I was trying to CTRL click on).

That's probably too much docstring in the tooltip, I'm guessing? That's different from a string literal, which is what this specific complaint is about (pretty sure we have another one for docstrings)

You're right, it's docstring in my case.
FYI https://github.com/Microsoft/PTVS/issues/2474 proposed removing string literal tooltips as well.

And https://github.com/Microsoft/PTVS/issues/622 too :)

Let's deal with it in #622


Error parsing timezones other than "Z" or "+00:00"

I am not able to parse timezones other an Z/+00:00 with dtparse 1.3.2.
>>> dtparse.parse("2021-05-04 13:37:00+00:00", "%Y-%m-%d %H:%M:%S%:z")
datetime.datetime(2021, 5, 4, 13, 37)
>>> dtparse.parse("2021-05-04 13:37:00+10:00", "%Y-%m-%d %H:%M:%S%:z")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ValueError: no possible date and time matching input

>>> dtparse.parse("2021-05-04T13:37:00Z", "%+")
datetime.datetime(2021, 5, 4, 13, 37)
>>> dtparse.parse("2021-05-04T13:37:00+00:00", "%+")
datetime.datetime(2021, 5, 4, 13, 37)
>>> dtparse.parse("2021-05-04T13:37:00+01:00", "%+")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ValueError: no possible date and time matching input

I'd also expect that tzinfo is attached to the datetime for Z/+00:00:
>>> dtparse.parse("2021-05-04 13:37:00+00:00", "%Y-%m-%d %H:%M:%S%:z")
datetime.datetime(2021, 5, 4, 13, 37, tzinfo=datetime.timezone.utc)
>>> dtparse.parse("2021-05-04T13:37:00Z", "%+")
datetime.datetime(2021, 5, 4, 13, 37, tzinfo=datetime.timezone.utc)
>>> dtparse.parse("2021-05-04T13:37:00+00:00", "%+")
datetime.datetime(2021, 5, 4, 13, 37, tzinfo=datetime.timezone.utc)

Did I miss something or is this a bug or even expected behavior?

Hi! You're right, it only parses UTC. See the call to the Rust library: https://github.com/gukoff/dtparse/blob/master/src/lib.rs#L20
We could make parsing timezone-aware. I think fixed offsets should be easy to support.
It's harder to support real-world timezones (PST, EST, Europe/Berlin, etc), as their definitions change over the time, and one must think how to bring chrono-tz and pytz together.
Is your usecase strictly fixed offsets?

Fixed offsets would be a huge benefit and cover most use cases. :)


Add Dangerfile

It would be nice to have Danger.rb run proselint on new posts. Check out ashfurrow/blog for an example repo that runs danger-prose on PRs. This will also get me more familiar with Danger.rb, which will be nice to compare with where Danger.js is now / see what it needs.

I made a bot to use with this (and for other projects) - @macklinu-bot.


[godot 4.0 beta.10~13]A bug about text editor parsing.

Godot version
4.0 Beta 10~13
System information
Window10
Issue description
This is an unexpected malignant bug, which will crash directly when you export the release version on your PC.

If you don't add "return ‘expected variable type’" at the end of the function, it will crash in the release version.

But if you add "return expected variable type" at the end of the function, it will notify Unreachable code.

Steps to reproduce
略
Minimal reproduction project
略

Duplicate of #71577


Add automated component testing

We recently (#136) added end-to-end browser tests to the docs using Playwright. We should also add tests for individual components, ideally without having to visit individual pages in content/<ver> since these change frequently.
One approach to this is to use Storybook alongside the Storybook Test runner, which allows us to turn Storybook stories into Playwright tests.
Let's consider this issue complete when:

We have written at least one automated component test (e.g., for fixing a bug)
We have included a command to run the automated component test in package.json and our CI config

@hatched @avatus @sandylcruz Is there any other context we should add here? Any other approaches that would work better?

Having tests for the individual components is a good idea however I try to only reach for something like Playwright when I need to write an end to end test. Something in the context of the "bigger picture" like the whole app running connected to a real backend.
I feel using a headless browser test runner like playwright for individual component tests is quite heavy weight compared to using something like jsom with Jest and React Testing Library while simulating interactions.

@hatched That makes sense to me!  Those files don't exist in gravitational/docs, though, so it's a good opportunity to start afresh with lightweight component testing.

It would be great to implement automated component testing, I also want to suggest a solution with not only interaction tests for docs components:
Mostly, the components in the docs repo are really simple and don't contain hard logic connected with interactions. It will be handy to add such tests for the complex components (which are few), but I anticipate that even more useful for docs would be to have visual tests. They give the ability to catch regressions in UI, for example, if we change something in the code and unintentionally worse UI in unexpected places, visual tests will warn us about this. It will be especially helpful also because it's hard to every time check the visual regressions for all pages when there are a lot of them.
So, I propose the flow of implementing interaction tests and visual tests. It can be done by a single Storybook, which has Test Runner (which is powered by Jest by the way) for automating test executions and Chromatic for visual tests. Both UI and interaction tests can be easily run automatically.
I can create a PR by implementing these two tools and creating a few stories for the most complex stories, and then we can decide if it covers all needs. WDYT?

@avatus Thanks, Michael, I will take a look at this PR.
Regarding Chromatic, I think it depends on your decision if this tool will be valuable for you for permanent use, did you have problems with visual regression before or not, and if there is a high probability of frequent changes in common files which can invoke such regressions. Seems to me, it can be valuable in this case with a lot of pages, and simple components. By heaviness, do you mean its bundle size?

By heavy i mean, cloud hosted with project tokens and all that related configuration. I think storybook alone would get us mostly what we need.

@ninaTorgunakova @avatus Thanks for looking into this! I'd rather not tie us to another third-party SaaS vendor unnecessarily. We tend not to have issues with visual regression (as far as I know)—what I'm worried about with regard to our components are the more complex ones like Tabs, where it's easier to trigger a regression in one code path by fixing a bug in another.
I think Storybook sounds good!
Is there a more dependency-free alternative to Chromatic for snapshot testing if we just want a quick way to prevent unintended regressions in simple components? E.g., something like a golden file test where we render each React component, serialize it, and compare it to an on-disk serialization?

@ptgott @avatus Thanks for describing your opinion, I understood it.
If you don't have issues with visual regressions and are open to Storybook, then we can go with simple Snapshot tests which are provided by Storybook. It's a very quick way to ensure that the DOM structure doesn’t change and that there are no errors appeared. They are easy to use, with no additional configurations/environments. Will this option be more suitable?
And sure, besides that, let's add interaction tests for complex components.

@ninaTorgunakova Storybook snapshot tests sound good to me! This will be a quick way to ensure we have solid test coverage without needing to define test expectations retroactively for all of our components. Do you have any thoughts on this, @avatus?

Yup, sounds good to me!

@avatus @ptgott Sorry for stepping in, but I wanted to share some considerations about snapshots and screenshots testing there.
We tried to use snapshots on four different projects, and on each of them, we removed them in the end. Reasons were:

They are very noisy - every small change can potentially cause multiple snapshots to break.
Their body is big chunks of automatically generated code. Comparing them visually takes a lot of time, and it is easy to miss something.
They only show HTML code, but not the applied CSS and visual render. As a result, they can't catch visual regressions of problems with JS logic.

As a result, after some time, everybody just starts to automatically update them without reading.
On projects where we removed snapshots, we were usually switching to screenshots testing and it was a lot more effective. Comparing images are faster and easier than comparing snapshots and this comparison often helped in finding bugs.
Speaking of visual regressions on the docs site, I remember multiple times then I changed some base component like buttons, dropdown, or menu item styles and missed manually checking it on one of the pages, with some combination of content or in the mobile and broken version came to prod. I usually catch and fix these bugs myself, then retest in on prod, but having screenshot testing would help to catch these bugs before publishing or at least to add new tests to prevent this situation in the future.
Saying that, setting up screenshot testing manually takes a lot of time, resources, and infrastructure - to store old versions of screenshots, to compare them, to generate diffs, to update changed screenshots, etc. So usually, instead of doing it ourselves, we use third-party services like Chromatic.
We proposed Chromatic in this case because it is a service from the creators of Storybook, and it works with storybook pages out of the box - it can automatically create screenshots for each storybook page on deployment and automatically compare them on new branch creation.
I do understand that having additional SaaS services is not optimal, especially if docs styles are not changed very often, but having screenshot testing, in my opinion, is a lot more helpful than snapshots.
And even if we decide not to use Chromatic, I'd say let's still not do snapshot testing and only do unit tests. In my memory, I do not remember any cases then snapshots helped to catch a bug, but they always make tests more fragile and create a lot of noise.

@iAdramelk I love your input, thank you!!
I appreciate the feedback on storybook snapshot tests. Honestly, when it comes down to it, I don't mind how we do our testing and is mostly up to the docs team. Anything that can be automated by our writers/engineers to help keep our components in line is what I care about. I 👍 anything that achieves that goal. My preference is as little added complexity as possible but, you tell me.

That's a really helpful writeup, @iAdramelk, thanks! @avatus @ninaTorgunakova Why don't we start with unit tests for complex components? I think setting up the SaaS dependency will require some non-dev work that we'll have to talk about within Teleport (procurement, etc.).

@ptgott Yes, I'm already in the process of adding unit tests and stories (started with Tabs). Ping me please when there is any news regarding the discussion of visual tests 👍

@ptgott PR with automated component testing was merged, but there is left our recommendation to add visual tests. If it's more convenient to track a new issue, it can be created as you proceed with agreements regarding Chromatic within Teleport (or just continue in this issue).

Hi @ninaTorgunakova, I would say that the automated component testing PR fulfills most/all of the requirements for this issue, since we can now test complex behavior in our components.
Preventing regressions is also important, but I think we can decouple that work from this task. Would you be okay creating an issue for visual tests? Then I can run the issue by some people at Teleport.
Does that make sense to you, @avatus ?

@ptgott Yes, sure, I added a separate issue for it with a description https://github.com/gravitational/docs/issues/328.

Closing as completed in #312


KAFKA-8381; Disable hostname validation when verifying inter-broker SSL

Make endpoint validation configurable on SslEngineBuilder when creating an engine
Disable endpoint validation for engines created for inter-broker SSL validation since it is unsafe to use localhost
Use empty hostname in validation engine to ensure tests fail if validation is re-enabled by mistake
Add tests to verify inter-broker SSL validation

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

retest this please.

JDK 8 build passed, JDK 11 failed during git checkout due to environmental issues.

retest this please

@omkreddy Thanks for the review, merging to trunk.

Thanks, @rajinisivaram .  Good catch


Cocde Review Commentsa from #1971

There were a coupole of minor comments in #1971 which I address here:

teardown eventingester in tests-e2e
remove e2e/setup/event-ingester-config.yaml as it should no longer be needed

Codecov Report
Base: 46.83% // Head: 46.84% // Increases project coverage by +0.01% :tada:

Coverage data is based on head (82403ed) compared to base (27ebaca).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2015      +/-   ##
==========================================
+ Coverage   46.83%   46.84%   +0.01%
==========================================
  Files         206      206
  Lines       27625    27625
==========================================
+ Hits        12939    12942       +3
  Misses      13791    13791
+ Partials      895      892       -3

Flag
Coverage Δ

airflow-operator
89.13% <ø> (ø)

armada-server
45.73% <ø> (+0.01%)
:arrow_up:

python-client
93.83% <ø> (ø)

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

Impacted Files
Coverage Δ

internal/scheduler/scheduler.go
78.22% <0.00%> (-0.64%)
:arrow_down:

internal/common/pgkeyvalue/pgkeyvalue.go
78.65% <0.00%> (+3.37%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Trigger metadata retrieval when attaching PDFs

General
Platform:  Windows/MacOS
Python version:  2.7.15
Pyzotero version: 1.3.5
Problem description
I'm writing a script to replicate a forrest of PDFs as a mirror network of links in Zotero. So far the system working well with a few test files. However, Zotero doesn't initiate an automatic metadata download when Pyzotero creates the link. Any idea how I might trigger metadata retrieval?
Thanks.
Gareth.
And thanks for pyzotero - it's a fantastic tool

Do you mean creating a new item (i.e. a journal article) from a PDF that has been uploaded using the API? I don't think the API supports that functionality…

Thanks @urschrei, I had forgotten that the API works with the web based database and not the app directly. I'll work out another way of triggering this.
Thanks.
Gareth.


Add message in joining

When joining an HA cluster we print a  Contacting cluster at <node> right at the beginning so we do not leave the user wondering if the command works or not.
$ sudo microk8s join <IP_ADDRESS>:25000/c30b882c33b126b388af31c61573d4f6
Contacting cluster at <IP_ADDRESS>
Waiting for node to join the cluster. .. ..

@knkski this came from a feedback you provided some time ago.

Done @knkski. Thank you for the review.


object-c  project

support object-c

Please check this.
https://github.com/tilltue/TLPhotoPicker/issues/55

@dogfenglee  Check this PR, hope it helps.
https://github.com/tilltue/TLPhotoPicker/pull/166


ValueError: list.remove(x): x not in list

Traceback (most recent call last):
  File "/root/main.py", line 549, in my_function
    async for i in bot.ask_stream(
  File "/usr/local/lib/python3.10/dist-packages/re_edge_gpt/chat/re_edge_gpt.py", line 202, in ask_stream
    async for response in self.chat_hub.ask_stream(
  File "/usr/local/lib/python3.10/dist-packages/re_edge_gpt/chat/chathub.py", line 125, in ask_stream
    conversation_style.value.remove(option)
ValueError: list.remove(x): x not in list

Look like you remove some option not in conversation_style list.

I delete "autosave", although it is not a problem the first time I delete it, I think it creates a problem in the following times because it has already been deleted before

Because the new version of ReEdgeGPT’s conversation_style default setting does not include autosave
new version :
    creative = [
        "nlu_direct_response_filter",
        "deepleo",
        "disable_emoji_spoken_text",
        "responsible_ai_policy_235",
        "enablemm",
        "dv3sugg",
        "autosave",
        "iyxapbing",
        "iycapbing",
        "h3imaginative",
        "clgalileo",
        "gencontentv3",
        "uquopt",
        "sunoupsell",
        "gndlogcf",
        "flxvsearch",
        "noknowimg",
        "eredirecturl"
    ]
    creative_classic = [
        "nlu_direct_response_filter",
        "deepleo",
        "disable_emoji_spoken_text",
        "responsible_ai_policy_235",
        "enablemm",
        "dv3sugg",
        "autosave",
        "iyxapbing",
        "iycapbing",
        "h3imaginative",
        "clgalileo",
        "gencontentv3",
        "uquopt",
        "sunoupsell",
        "gndlogcf",
        "flxvsearch",
        "noknowimg",
        "eredirecturl"
    ]
    balanced = [
        "nlu_direct_response_filter",
        "deepleo",
        "disable_emoji_spoken_text",
        "responsible_ai_policy_235",
        "enablemm",
        "dv3sugg",
        "autosave",
        "iyxapbing",
        "iycapbing",
        "enable_user_consent",
        "fluxmemcst",
        "galileo",
        "saharagenconv5",
        "dc1mncp",
        "uquopt",
        "sunoupsell",
        "crkt2t",
        "immslots",
        "cpproname",
        "vidtoppb",
        "gptv1desc2",
        "eredirecturl"
    ]
    precise = [
        "nlu_direct_response_filter",
        "deepleo",
        "disable_emoji_spoken_text",
        "responsible_ai_policy_235",
        "enablemm",
        "dv3sugg",
        "autosave",
        "iyxapbing",
        "iycapbing",
        "enable_user_consent",
        "fluxmemcst",
        "h3precise",
        "clgalileo",
        "uquopt",
        "sunoupsell",
        "crkt2t",
        "flxvsearchans",
        "noknowimg",
        "eredirecturl"
    ]

So, I think this is not actually an issue.
But I will add precheck to remove options.
Like:
if option in style_options:
    list.remove(option)
else:
    print(f"Warning {option} not in style options list", file=sys.stderr)

#133


NewInstance of Object from v8go.NewObjectTemplate is not correctly initialized in v8

Hi
I've been playing with v8go for some time and I've been encountering some strange behavior
Small precision I use "go.kuoruan.net/v8go-polyfills/console" and "go.kuoruan.net/v8go-polyfills/timers"
This is my JS function executed from GO
async function reaction(event) {
    console.log(event)
    console.log(Object.keys(event))
    console.log(Object.values(event))
    console.log(event.b)
    await sleep(5000)
    console.log('Fart button clicked !'); // Just to display a message in the console when clicking
    const volume = 0.2; // value between 0 and 1
}
const sleep = (ms) => new Promise((resolve) => setTimeout(resolve, ms));

The go code
                        reactionFunctionJS, _ := ctx.RunScript("reaction", "")
			fn, _ := reactionFunctionJS.AsFunction()

			object, _ := v8go.NewObjectTemplate(iso)
			object.Set("a", true)
			object.Set("b", 1)
			object.Set("c", 1.258)
			object.Set("d", 42)
			object.Set("e", 666666)
			object.Set("f", "test")

			var valueObj, _ = object.NewInstance(ctx)

			resultReactionFn, _ := fn.Call(valueObj)

			if resultReactionFn.IsPromise() {
				prom1, _ := resultReactionFn.AsPromise()

				for prom1.State() == v8go.Pending {
					continue
				}
			}

Result
console.log(event) => [object Object]
console.log(Object.keys(event)) => a,c,f
console.log(Object.values(event)) => true,1.258,test
console.log(event.b) => undefined

First of all I can't make a console.log of the object, how can i do that ?
    console.log(event)

Secondly, the console.log
    console.log(Object.keys(event))
    console.log(Object.values(event))

Doesn't return all the values, which is pretty weird, did I miss something somewhere?
Only number values are not in the object
Thx

First of all I can't make a console.log of the object, how can i do that ?

Sounds like that is a v8go-polyfills bug/feature request, since I believe it defines the console.log function.

Secondly, the console.log
Doesn't return all the values, which is pretty weird, did I miss something somewhere?

You didn't check for object.Set errors.  It looks like it fails for int, since (oddly) that isn't one of the types it supports.  https://pkg.go.dev/rogchap.com/v8go#Object.Set lists the supported Go primitives as: string, int32, uint32, int64, uint64, float64, big.Int
So you could explicitly cast to one of those fixed size integers as a workaround.  E.g. object.Set("b", int32(1))
It does seem like v8go could easily support other integer types, especially int, to avoid this problem.  Perhaps it could also have a MustSet method that panics on errors, which would be convenient for initializing, where no errors are expected.


Use better exception messages

Find all instances of throw std:: in

apyfixed.cc
apyfixed.h
apyfixedarray.cc
apyfixedarray.h,

make sure that the exception messages give proper information when raised. It should be simple now that Fmt has been added to the project.

One should also consider throwing more targeted error. TypeError and ValueError in particular.

For APyFixedArray:

Proper exception messages added in 3d12f908e02b0c9ae6ba733cdb90556b7aad4eab
Proper (NumPy equivalent) exception types added in f74ba35a13d6da9f2dcc1b7863f77298cbc90fbd

With the addition of fmt::format() it is now very easy to throw good error messages, and this should be done for all raised exceptions.
However, it does not make sense to have such a broad issue as this one open. For more targeted 'better exception message' issues, please open a new issue.
Closed.


Modernizing setup

Modernizing setup to use pyproject.toml with setuptools as backend.
Replacing python setup.py sdist bdist_wheel command with python -m build

I suppose the only way to test this for me is to just make a release and hope for the best. Locally building worked fine for me


TCP-only connection

Forgot to say that this was tested on friday on my laptop and it seemed to correctly receive updates from the mocap server

Also since this is a simple change, there's a possibility that we'd add an ENV variable based toggle to change between TCP/UDP modes in case that's something we could benefit from later, but I'm not sure if it's worth the added complexity. Currently we could toggle between those by changing the version of mocap pose that we use. Though later when this software gets more changes, the old and new versions will start diverging more and more in which case this ability dies off gradually..


blank pages

The document located at the URL below has numerous blank pages.
chrome://pdf.js/content/web/viewer.html?file=http://www.safework.sa.gov.au/uploaded_files/wah_booklet.pdf
Firefox Portable 8 on Windows 7 32 bit.

Thanks for reporting the issue.  There seem to be a few issues. 1) JPEG 2000 images which we do not currently support.  2) Inverted CMYK images, which will be fixed soon.

The issue is resolved


Fix inconsequential stack sh errors

Current coverage is 38.57%

Merging #93 into devel will decrease coverage by -0.07% as of 5491f66

@@            devel     #93   diff @@
=====================================
  Files           2       2
  Stmts         885     884     -1
  Branches        0       0
  Methods         0
=====================================
- Hit           342     341     -1
  Partial         0       0
  Missed        543     543

Review entire Coverage Diff as of 5491f66

Uncovered Suggestions

+1.92% via src/mpi/mpi_caf.c#1892...1908
+1.58% via src/mpi/mpi_caf.c#1990...2003
+1.58% via src/mpi/mpi_caf.c#1557...1570
See 7 more...

Powered by Codecov. Updated on successful CI builds.

:ballot_box_with_check: :ok_hand:

:ok_hand:

Was this ever merged into master as well? (I'm on a plane, on my phone, using an iPhone app so it's hard for me to tell at the moment)

From the network graph, it appears it was not.  I'll try to do that today. I think there were merge conflicts that needed to be resolved at the command line.

Ok I can take a look too. It can be harder/more complicated to merge into master after merging into devel rather than before. I'm waiting to take off now so I may not be able to take a look until tomorrow.

I'm trying to do the merge.  If I don't succeeds, let's talk tomorrow while you look at it so I can see what you do.


Error on Jetson Nano

ETA: Love your work, looking forward to resolving my issues and getting to play with this.
Kind of stumped.
Receive this error on Front End
Traceback (most recent call last):   File "/usr/local/lib/python3.8/site-packages/tornado/web.py", line 1681, in _execute     result = self.prepare()   File "/src/viseron/webserver/__init__.py", line 81, in prepare     raise tornado.web.HTTPError(404) tornado.web.HTTPError: HTTP 404: Not Found
back-end boot with debug turned on looks like:
'[services.d] done.
[2021-10-06 11:38:19] [INFO    ] [viseron                 ] - -------------------------------------------
[2021-10-06 11:38:19] [INFO    ] [viseron                 ] - Initializing...
[2021-10-06 11:38:19] [DEBUG   ] [viseron.watchdog        ] - Starting scheduler
[2021-10-06 11:38:19] [DEBUG   ] [viseron                 ] - Starting cleanup scheduler
[2021-10-06 11:38:19] [DEBUG   ] [viseron                 ] - Running initial cleanup
[2021-10-06 11:38:19] [DEBUG   ] [viseron.cleanup         ] - Running cleanup
[2021-10-06 11:38:19] [DEBUG   ] [viseron.cleanup         ] - Items in /recordings/2021-10-06/Lorex_IR_2: 2
[2021-10-06 11:38:19] [INFO    ] [viseron.mqtt            ] - Initializing MQTT connection
[2021-10-06 11:38:19] [DEBUG   ] [viseron.mqtt            ] - MQTT connected with returncode 0
[2021-10-06 11:38:19] [DEBUG   ] [viseron.detector        ] - Initializing object detector darknet
[2021-10-06 11:38:19] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic */frame/scan/object, <queue.Queue object at 0x7f69b6e880>
[2021-10-06 11:38:19] [DEBUG   ] [viseron.detector        ] - Object detector initialized
[2021-10-06 11:38:19] [INFO    ] [viseron                 ] - Initializing NVR threads
[2021-10-06 11:38:19] [DEBUG   ] [viseron.nvr.lorex_ir_2  ] - Initializing NVR thread
[2021-10-06 11:38:19] [DEBUG   ] [viseron.camera.lorex_ir_2] - Initializing camera Lorex_IR_2
[2021-10-06 11:38:19] [DEBUG   ] [viseron.nvr.lorex_ir_3  ] - Initializing NVR thread
[2021-10-06 11:38:19] [DEBUG   ] [viseron.camera.lorex_ir_3] - Initializing camera Lorex_IR_3
[2021-10-06 11:38:19] [DEBUG   ] [viseron.camera.stream.lorex_ir_2] - Getting stream information for rtsp://:@<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif
[2021-10-06 11:38:19] [DEBUG   ] [viseron.camera.stream.lorex_ir_3] - Getting stream information for rtsp://:@<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0
[2021-10-06 11:38:21] [DEBUG   ] [viseron.camera.stream.lorex_ir_3] - Stream information from FFprobe: Width: 3840 Height: 2160 FPS: 15.0 Video Codec: h264 Audio Codec: None
[2021-10-06 11:38:21] [DEBUG   ] [viseron.camera.lorex_ir_3] - Resolution: 3840x2160 @ 15 FPS
[2021-10-06 11:38:21] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic lorex_ir_3/frame/decode/object, <queue.Queue object at 0x7f68302970>
[2021-10-06 11:38:21] [DEBUG   ] [viseron.camera.lorex_ir_3] - Starting decoder thread
[2021-10-06 11:38:21] [DEBUG   ] [viseron.camera.lorex_ir_3] - Running decoder lorex_ir_3.object_detection at 1.0s interval, every 15.0 frame(s)
[2021-10-06 11:38:21] [DEBUG   ] [viseron.camera.lorex_ir_3] - Camera Lorex_IR_3 initialized
[2021-10-06 11:38:21] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic lorex_ir_3/frame/processed/object, <queue.Queue object at 0x7f682fd520>
[2021-10-06 11:38:21] [DEBUG   ] [viseron.motion.lorex_ir_3] - Initializing motion detector
[2021-10-06 11:38:21] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic lorex_ir_3/frame/decode/motion, <queue.Queue object at 0x7f683161f0>
[2021-10-06 11:38:21] [DEBUG   ] [viseron.motion.lorex_ir_3] - Starting decoder thread
[2021-10-06 11:38:21] [DEBUG   ] [viseron.motion.lorex_ir_3] - Running decoder lorex_ir_3.motion_detection at 1s interval, every 15 frame(s)
[2021-10-06 11:38:21] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic lorex_ir_3/frame/scan/motion, <queue.Queue object at 0x7f69b67790>
[2021-10-06 11:38:21] [DEBUG   ] [viseron.motion.lorex_ir_3] - Motion detector initialized
[2021-10-06 11:38:21] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic lorex_ir_3/frame/processed/motion, <queue.Queue object at 0x7f682f54c0>
[2021-10-06 11:38:21] [DEBUG   ] [viseron.nvr.lorex_ir_3  ] - Starting camera
[2021-10-06 11:38:21] [DEBUG   ] [viseron.camera.lorex_ir_3] - Starting capture thread
[2021-10-06 11:38:21] [DEBUG   ] [viseron.recorder.lorex_ir_3] - Initializing ffmpeg recorder
[2021-10-06 11:38:21] [DEBUG   ] [viseron.camera.stream.lorex_ir_3] - FFMPEG decoder command: lorex_ir_3 -hide_banner -loglevel error -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts -use_wallclock_as_timestamps 1 -vsync 0 -stimeout 5000000 -c:v h264_nvv4l2dec -rtsp_transport tcp -i rtsp://:@<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0 -f segment -segment_time 5 -reset_timestamps 1 -strftime 1 -c:v copy -c:a none /segments/Lorex_IR_3/%Y%m%d%H%M%S.mp4 -filter:v fps=1 -f rawvideo -pix_fmt nv12 pipe:1
[2021-10-06 11:38:21] [DEBUG   ] [viseron.nvr.lorex_ir_3  ] - Waiting for first frame
[2021-10-06 11:38:21] [DEBUG   ] [viseron.nvr.lorex_ir_3  ] - NVR thread initialized
[2021-10-06 11:38:22] [DEBUG   ] [viseron.camera.stream.lorex_ir_2] - Stream information from FFprobe: Width: 352 Height: 240 FPS: 10.0 Video Codec: h264 Audio Codec: None
[2021-10-06 11:38:22] [DEBUG   ] [viseron.camera.stream_segments.lorex_ir_2] - Getting stream information for rtsp://:@<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=onvif
[2021-10-06 11:38:23] [ERROR   ] [viseron.camera.stream.lorex_ir_3] - NvMMLiteOpen : Block : BlockType = 261
[2021-10-06 11:38:23] [ERROR   ] [viseron.camera.stream.lorex_ir_3] - NVMEDIA: Reading vendor.tegra.display-size : status: 6
[2021-10-06 11:38:23] [ERROR   ] [viseron.camera.stream.lorex_ir_3] - NvMMLiteBlockCreate : Block : BlockType = 261
[2021-10-06 11:38:25] [DEBUG   ] [viseron.camera.stream_segments.lorex_ir_2] - Stream information from FFprobe: Width: 3840 Height: 2160 FPS: 15.0 Video Codec: h264 Audio Codec: None
[2021-10-06 11:38:25] [DEBUG   ] [viseron.camera.lorex_ir_2] - Resolution: 704x480 @ 15 FPS
[2021-10-06 11:38:25] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic lorex_ir_2/frame/decode/object, <queue.Queue object at 0x7f6831fcd0>
[2021-10-06 11:38:25] [DEBUG   ] [viseron.camera.lorex_ir_2] - Starting decoder thread
[2021-10-06 11:38:25] [DEBUG   ] [viseron.camera.lorex_ir_2] - Running decoder lorex_ir_2.object_detection at 1.0s interval, every 15.0 frame(s)
[2021-10-06 11:38:25] [DEBUG   ] [viseron.camera.lorex_ir_2] - Camera Lorex_IR_2 initialized
[2021-10-06 11:38:25] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic lorex_ir_2/frame/processed/object, <queue.Queue object at 0x7f682f5af0>
[2021-10-06 11:38:25] [DEBUG   ] [viseron.motion.lorex_ir_2] - Initializing motion detector
[2021-10-06 11:38:25] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic lorex_ir_2/frame/decode/motion, <queue.Queue object at 0x7f683287f0>
[2021-10-06 11:38:25] [DEBUG   ] [viseron.nvr.lorex_ir_3  ] - First frame received
[2021-10-06 11:38:25] [DEBUG   ] [viseron.motion.lorex_ir_2] - Starting decoder thread
[2021-10-06 11:38:25] [DEBUG   ] [viseron.motion.lorex_ir_2] - Running decoder lorex_ir_2.motion_detection at 1s interval, every 15 frame(s)
[2021-10-06 11:38:25] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic lorex_ir_2/frame/scan/motion, <queue.Queue object at 0x7f683283a0>
[2021-10-06 11:38:25] [DEBUG   ] [viseron.motion.lorex_ir_2] - Motion detector initialized
[2021-10-06 11:38:25] [DEBUG   ] [viseron.data_stream     ] - Subscribing to data topic lorex_ir_2/frame/processed/motion, <queue.Queue object at 0x7f68328220>
[2021-10-06 11:38:25] [DEBUG   ] [viseron.nvr.lorex_ir_2  ] - Starting camera
[2021-10-06 11:38:25] [DEBUG   ] [viseron.camera.lorex_ir_2] - Starting capture thread
[2021-10-06 11:38:25] [DEBUG   ] [viseron.recorder.lorex_ir_2] - Initializing ffmpeg recorder
[2021-10-06 11:38:25] [DEBUG   ] [viseron.camera.stream.lorex_ir_2] - FFMPEG decoder command: lorex_ir_2 -hide_banner -loglevel error -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts -use_wallclock_as_timestamps 1 -vsync 0 -stimeout 5000000 -c:v h264_nvv4l2dec -rtsp_transport tcp -i rtsp://:@<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif -filter:v fps=1 -f rawvideo -pix_fmt nv12 pipe:1
[2021-10-06 11:38:25] [DEBUG   ] [viseron.nvr.lorex_ir_2  ] - Waiting for first frame
[2021-10-06 11:38:25] [DEBUG   ] [viseron.nvr.lorex_ir_2  ] - NVR thread initialized
[2021-10-06 11:38:25] [INFO    ] [viseron                 ] - Initialization complete
[2021-10-06 11:38:25] [DEBUG   ] [viseron.camera.stream_segments.lorex_ir_2] - FFMPEG decoder command: lorex_ir_2_segments -hide_banner -loglevel error -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts -use_wallclock_as_timestamps 1 -vsync 0 -stimeout 5000000 -c:v h264_nvv4l2dec -rtsp_transport tcp -i rtsp://:@<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=onvif -f segment -segment_time 5 -reset_timestamps 1 -strftime 1 -c:v copy -c:a none /segments/Lorex_IR_2/%Y%m%d%H%M%S.mp4
[2021-10-06 11:38:28] [ERROR   ] [viseron.camera.stream.lorex_ir_2] - NvMMLiteOpen : Block : BlockType = 261
[2021-10-06 11:38:28] [ERROR   ] [viseron.camera.stream.lorex_ir_2] - NVMEDIA: Reading vendor.tegra.display-size : status: 6
[2021-10-06 11:38:28] [ERROR   ] [viseron.camera.stream.lorex_ir_2] - NvMMLiteBlockCreate : Block : BlockType = 261
[2021-10-06 11:38:33] [DEBUG   ] [viseron.nvr.lorex_ir_3.object] - Objects: [], message repeated 3 times
[2021-10-06 11:38:34] [DEBUG   ] [viseron.nvr.lorex_ir_2  ] - First frame received
[2021-10-06 11:39:08] [DEBUG   ] [viseron.nvr.lorex_ir_3.object] - Objects: [], message repeated 35 times'
any ideas where to look?

yeah, i can't see anywhere to change that on the Lorex camera's themselves, but taking a dig :-) thanks for the help :-)

let me try that
if its any help, Shinobi's jetson build has this nailed. worked first go.

just to update, not luck on this path unfortunately.

Sorry you are having so many issues!
Im busy with a rewrite of Viseron right now which makes it more extensible and easier for me to maintain.
As soon as i am done with that i will look into improving the Jetson Nano integration.
Another user kindly set up a VPN to his Nano so i can remote into it and develop directly on it.
That was my biggest issue before and is the reason why there are so many problems with it, i could not do any debugging at all.

Sorry you are having so many issues!
no need to be sorry my man, its a cool project and i was keen to screw with it and see if i could move away from Shinobi to something a bit lighter in weight. all is good though and will keep plodding away seeing what i can figure out :-)

makes it more extensible and easier for me to maintain.
look forward to seeing it, how much abstraction are you doing out of curiosity? enough to abstract ffmpeg out so we could drop in gstreamer as an example? n.b. i have no idea about the complexity of gstreamer or if it even supports whats needed :-)

Another user kindly set up a VPN to his Nano so i can remote into it and develop directly on it.
great, yell if you need a B01 (4GB) as well, i can get one online for you when the time comes as well :-)

look forward to seeing it, how much abstraction are you doing out of curiosity? enough to abstract ffmpeg out so we could drop in gstreamer as an example? n.b. i have no idea about the complexity of gstreamer or if it even supports whats needed :-)

Yes exactly that.
Im splitting it into components and domains, so the component would be gstreamer and the domain would be camera.
I will post my progress soon in a WIP Pull Request so people can follow along

great, yell if you need a B01 (4GB) as well, i can get one online for you when the time comes as well :-)

Thats very kind of you!

I will post my progress soon in a WIP Pull Request so people can follow along

how do i get notified about the pull request, me n00b?
with this issue here?
liek to see the gstreamer options as i am also struggling getting this (or frigate) onto the jetson nano.
may shinobi (??) is my third option.. but like to give this here the first shot on the nano

#306 is where it happens! Still a bit to go before its ready.
Also need to implement gstreamer and i dont really know how hard that will be.

i subscribed also to https://github.com/roflcoopter/viseron/pull/306 to see it happen.
hope to see ffmpeg coming stable on the nano.
seems hard work...

Awesome!! Look forward to having a play :)
also sub’ed on #306, yell if you need anything tested 👍


Set a default sqlitePath

Set the config param sqlitePath in the default config.  Without this, an error will be thrown by db.js:10 setupDb when run without a config specified by --configPath while when attempting to export GTFS before exiting the program.
Current Behavior:
Program exits with error:
Error: TypeError: Expected a string, got undefined
[  TypeError: Expected a string, got undefined

  - index.js:7 untildify
    [gtfs-tts]/[untildify]/index.js:7:9

  - db.js:10 setupDb
    [gtfs-tts]/[gtfs]/lib/db.js:10:27

  - db.js:31 openDb
    [gtfs-tts]/[gtfs]/lib/db.js:31:12

  - export.js:37 exportGtfs
    [gtfs-tts]/[gtfs]/lib/export.js:37:14

  - gtfs-tts.js:215 gtfsTTS
    file:///.../gtfs-tts/dist/bin/gtfs-tts.js:215:9

  - gtfs-tts.js:254 async setupImport
    file:///.../gtfs-tts/dist/bin/gtfs-tts.js:254:3

]

New Behavior:
Program exits with success:
Starting GTFS export for 1 agency using SQLite database at /tmp/gtfs
Exporting - agency.txt
...

Thanks for identifying this issue and making a pull request!
Let me know if you have any other feedback.

I published this change in https://github.com/BlinkTagInc/gtfs-tts/releases/tag/0.3.0 - I actually updated the default to use :memory: - an in memory database to avoid needing to write the database to disk.


GH-44428: [CI][C#] Use setup-python to use "pip install"

Rationale for this change
We can't use pip install with Ubuntu 24.04's Python.
What changes are included in this PR?
Use actions/setup-python instead of Ubuntu 24.04's Python.
Are these changes tested?
Yes.
Are there any user-facing changes?
No.

GitHub Issue: #44428

+1


I don't see a problem

Lydia,
Your github repository looks OK to me. What was the problem?

Okay I was just having trouble reaccessing the first assignment edited.
Maybe I will just ask you in class.
Thanks!!


Enhancement: Add link to download json report

I didn't see a link in the UI to download a submission result (json) as I might get if I used the API.  Would be nice to add that as an option.

Also, if there is a JSONSectionBody for a service, it would be nice to provide a link in the section to download that as a file.


Cheatcodes should work in test state

If we target address 0, cheatcode should target test state

This is urgent task, effectively blocking #611 .
We should implement it ForgeHintProcessor tries to execute hint, otherwise falls back to CheatnetSyscallHandler otherwise falls back to BlockifierSyscallHandler

Is it blocked by #670? @cptartur

I don't think it is blocked but there may be merge conflicts

Please make sure if event related cheatcodes work as well


Added gunship and some notifictions to players

I modified these in 1.4.0, so there might missed something in 1.4.1

looks good :D
when I will get home I will test it and merge it

I love it ❤
expect the high health


Sigh. another RTD fix.

I definitely tested it this time fully.... Evidence:
https://ats.readthedocs.io/en/task-white238-another_rtd_fix/

This fixed the build but the theme is all messed up

I think i figured it out... Sphinx did a lot of default stuff before and they removed a lot of this logic. I took the section from Axom that should fix it.


Avoid erroneous import cycle loop detection in ToReachMap() arising from tests

From @sdboyer on March 6, 2017 20:48
When tests are included as part of a ToReachMap() call, all import statements are collapsed together, regardless of whether they originate from the actual package or from tests in that package. As @adg and I observed on one larger project, this can create a situation where those test imports create the appearance of an import cycle. For example, if:
A -> B -> C

Then everything's fine. But, say that C has tests that import A; that's fine for a real build, because C's tests are a "sidecar" and not actually scoped-in to anything that imports C. If, however, we can't tell that the C -> A import link arises from a test in ToReachMap(), then we'll mistakenly identify it as an import cycle.
Right now, we've addressed this by not addressing it - cycle detection is simply skipped in ToReachMap().
An analogous delineation of "importable package" could also be made with build tag parameterization...but honestly, that situation seems pretty far out from where we are right now. It'd be hard to do, too. And, because it would be strictly additive if we were to support it later, we can cross that bridge when someone actually runs into the problem.
Copied from original issue: sdboyer/gps#179

this is likely going to involve changing exported APIs, so we have to finish it before 1.0/whatever


feat:  Sha256 utils tests + chore improvements

Also created folder and files for cairo 1 runner
I named the Package Cairo with the cairo zero runner being in the Zero package.  Dont know if Cairo is the best naming, maybe Cairo1 (but now its Cairo 2 actually, I think Cairo vs Cairo Zero is a good terminology, @zmalatrax  uses this naming)

I like this idea of naming cairo0 runner zero and cairo for the future cairo versions. Gave approve 😉

ok for now its Cairo and Zero right?


Sort iteration according to human logic

Iteration names are now sorted according to machine logic.
E.g :
 pred-1, pred-100, pred-2, pred-3
For a human it is desirable with logic:
pred-1, pred-2, pred-3, pred-100

There is no standard on iteration (ensemble) names. It is a mix of conventions and free text. (E.g. does the pattern described above (pred-1, pred-2, etc) exist outside Troll?)
It is difficult to find a universal rule that will work.
Example: iter-0, iter-2, iter-10, pred.
Example: iter-0, iter-2, pred-1, pred-2, pred-10.
Example: myiter, myotheriter, final, first, test
Trying to sort on name I think could quickly explode into quite a lot of code. Perhaps better to sort on datetime? First created, first listed?


Do you actually need a user-generated GitHub PAT?

I notice from the readme:

Unfortunately, ${{ github.token }} does not have access to updating wiki repositories, so it is necessary to create a new PAT.

I don't think this is true? I was under the impression from my own attempt at a sub-par wiki action https://github.com/jcbhmr/publish-to-github-wiki that you can just use the ${{ github.token }} as long as you have the content: write permission.
name: Test publish to own wiki
on:
  push:
    paths:
      - index.sh
      - action.yml
      - .github/workflows/test-publish-to-own-wiki.yml
      - wiki/**
concurrency: test-publish-to-own-wiki
jobs:
  test-publish-to-own-wiki:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      # This just uses the secrets.GITHUB_TOKEN (or github.token, both are equivalent)
      - uses: ./

Recently GitHub did change up their permissions defaults to make them no longer write-permissive by default which may have thrown things off? I have already been bitten by this: https://github.com/jcbhmr/devcontainer-features/issues/2
Am I completely wrong? Is there something I'm missing? 🤷♂

First: I'd be happy to be proven wrong about this, since manually creating a PAT is a bit annoying 🙂
As far as I know, the default GitHub token available in actions (secrets.GITHUB_TOKEN/github.token) is limited to only being able to access the repo that triggered the action. In my experience, that limitation means it has read access to the wiki repository, since it's a public repository, but does not have write access, since it's a different remote URL.
If you could find a way to get this action to work without creating a PAT, and documented it, I'd be very grateful :pray:

There's some more discussion about this that I had with @Andrew-Chen-Wang over in https://github.com/Andrew-Chen-Wang/github-wiki-action/issues/17 that is at least tangentially related to this

Although it's not mentioned in any GitHub issues in my repo, I made the repo from inspo that you couldn't delete files from decathalon's action. Someone who beta tested said a GitHub pat is needed, so that's why I've got it in my repo as well.

👍 @Andrew-Chen-Wang good to know! I'd love to contribute some wiki documentation about:

how the heck the GITHUB_TOKEN value is used when pushing to git (could also be applicable to PAT when pushing from your own PC using the git push cli)
what/how a user can/needs to use the permissions: ... github actions yml value to set the proper permissions (this seems to be a recurring issue https://github.com/Andrew-Chen-Wang/github-wiki-action/discussions/14#discussioncomment-2769855)

After some investigative journalism (i.e. googling), I've come to the conclusion that you don't need a PAT to push to the wiki of a repo. You just need the content: write permission. This lets you push, force push, pull, etc. with the git endpoint.
This can be reflected in the readme refactor #9

If it's alright, would you be able to link to a successful workflow run that uses github.token so that I can be sure about this?

Sure! Here's some of my tests:

https://github.com/jcbhmr/publish-wiki-action-OLD/actions/runs/4370272621/workflow (uses the OLD "default write" permissions
https://github.com/devcontainers-contrib/features/actions/runs/4405809069/workflow (used an older version of my action, but still no GITHUB TOKEN passed)

Here's what I mean by "old default write"

https://github.blog/changelog/2023-02-02-github-actions-updating-the-default-github_token-permissions-to-read-only/
Now the default is the second "readonly" option, not the read/write one


KafkaInputOperator fixes.

I also noticed that the tests don't pass:
contrib$ mvn test -Dtest=KafkaInputOperatorTest -DskipTests=false
Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 73.123 sec <<< FAILURE!
testRecoveryAndIdempotency(com.datatorrent.contrib.kafka.KafkaInputOperatorTest)  Time elapsed: 12.975 sec  <<< FAILURE!
java.lang.AssertionError: largest recovery window expected:<2> but was:<3>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at com.datatorrent.contrib.kafka.KafkaInputOperatorTest.testRecoveryAndIdempotency(KafkaInputOperatorTest.java:257)
Results :
Failed tests:
KafkaInputOperatorTest.testRecoveryAndIdempotency:257 largest recovery window expected:<2> but was:<3>

Please remove the oldest recovery path(i.e, target) directory under Malhar and then run the test case.

This test still does not pass (after changing increment and clean):
Results :
Failed tests:
KafkaInputOperatorTest.testRecoveryAndIdempotency:271 Total messages collected  expected:1500 but was:1000
Tests run: 4, Failures: 1, Errors: 0, Skipped: 0
Further the test should not require a manual clean step. It should clean any leftover state in setup.


change std::unexpected() to std::terminate()

Signed-off-by: Mark Sisson<EMAIL_ADDRESS>Dynamic exception specification was deprecated in C++11, and removed in C++17.  This fixes compiler error when using C++17 compile feature by changing std::unexpected() to std::terminate().

I don't mind this change, but I wonder why we don't just set EXIT_FAILURE and fall through? std::terminate doesn't define return value...
Mind you, I don't like EXIT_SUCCESS and EXIT_FAILURE either for a similar reason. I'd want the tools to be have the same on all platforms, and 0 to always be success.

It seems we're a bit inconsistent in this regard. vdb_print and vdb_render handle this case, but don't set the return code, vdb_view doesn't even handle it. I'll clean up the others too - from reading up on this, std::terminate seems to be more correct, but I wouldn't mind if we settled on using EXIT_FAILURE instead here.


Fixed #31524 -- Removed minified static assets from the admin.

https://code.djangoproject.com/ticket/31524

Thanks Carlton. I added a blurb to the release notes please let me know if it aligns with what you have in mind or if you have any wording suggestions.

buildbot, test on selenium.

I can reproduce the test failures locally. I will investigate them.

buildbot, test on selenium.

Test failures fixed.

buildbot, test on selenium.


HttpServer has no public initializer

Xcode 7.2

Swifter 1.0.5

Image from sample project:

oops :+1: I forgot about "public override init() { }" for HttpServer class :)

one again, thanks for the report. It's fixed by https://github.com/glock45/swifter/commit/3eecb3204170b7583ff2076ff995b556dbdaf4f0
I am going to release the next version.

@crayment could you please check the latest release (1.0.6) ?

Confirmed working on 1.0.6 :+1: Thanks!!


Perform EDA on heart.csv dataset

Perform EDA on heart.csv dataset, after which we would finalise this dataset and move to train It for stress level prediction

Hi @TAHIR0110, please assign this to me. I have previously done EDA for ML models. Also, if you have any specifications do let me know!

@sivadurga0208 done, after the EDA just write a brief about the features which directly impact the stress level(column). dependent features to be more precise.

@TAHIR0110 Will do! Thank you

hi @TAHIR0110 i wanna contribute. plz assign the issue to me

Hi @TAHIR0110
I would like to take on the task of performing Exploratory Data Analysis (EDA) on the heart.csv dataset. Conducting EDA will provide valuable insights into the dataset's characteristics, helping us understand its structure and relationships between variables.
I believe this task aligns well as i have previously Worked on EDA for Training ML Models, and I am eager to contribute to the project's success

i can do EDA  on the heart.csv dataset as i have   worked on  analaysis and getting insight  from data from past 2 years and  i am  currently doing  b.tech in data science .I believe this task aligns well as i have previously Worked on EDA for analysing datasets  and for Training ML Models, and I am eager to contribute to the project's success

Hello, @TAHIR0110 .
I want to contribute to work on solving issues as part of GSSoc'24. I eagerly want to work on performing EDA on the heart.csv dataset. I'm passionate about Data science. Please assign me the issue.

@TAHIR0110  I want to contribute to work on performing EDA. please assign this to me

@TAHIR0110 . I AM PARTICIPATING THIS YEAR GSSOC 2024 AND I AM INTERESTED TO PERFORM EDA ON HEART.CSV . PLS ASSIGN ME THIS ISSUE

@TAHIR0110 i want to to contribute to this assign me this issue. I will perform EDA and also Identify corelations among the features.

Hi @TAHIR0110 Sir, I am participating in GSOC 2024 and would like to contribute to performing EDA. Please do assign me


Switch registry library image to debian:jessie

Fixes #8
cc @dmp42 @docker/distribution-maintainers

LGTM

woo! :+1:


Adding "html" to standard plugins breaks validation

I'm trying to enable standardjs validation for javascript and vue files. Following the instructions here, I added the following reference in my VSCode settings file:
"standard.options": {
  "plugins": ["html"]
}

However, this not only doesn't make validation work in *.vue files, but also stops validation from working in *.js files.

StandardJS version? 11.0.1
VSCode version? 1.24.0
StandardJS configuration?

    "standard.validate": [
        "javascript",
        "html"
    ],
    "standard.options": {
        "plugins": ["html"],
        "ignore": [
            "node_modules/**"
        ]
    },
    "files.associations": {
        "*.vue": "html"
    }

What do you have in the OUTPUT panel? Nothing

You should got something like this under OUTPUT panel:

You can find if module 'standard' and 'eslint-plugin-html' are under the same folder, if not, standardjs won't work


Event scheduler setting tweaks

About the PR

A couple tweaks for the event scheduler balance that should make ramping slightly slower, and meteors more likely to be dust.
If ramping seems too quick, the next step is probably changing the used distribution to be less flat and more gaussian.
Why / Balance

The default reoccurrenceDelay was 30 minutes, meaning that once meteor dust was spawned it would not send dust again, effectively forcing large meteors by 30 minutes. This was unintended.
The ramping event scheduler tweaks are just to make the values match wizden's actual round timing.
Technical details

Media

Requirements

[x] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

tweak: Meteor dust should more consistently happen instead of meteors.

whenever someone refactors this id like for the chaos metrics to be tied to a prototype and not the component itself

Hmmm. Interesting idea. I'll have to think on the best way to do that. It might be best to allow for completely setting the distribution and evolution in yaml.
I don't know that the flexibility that gives is necessary but it would be pretty cool. Maybe that's enough of a reason.