hpp-fcl: add missing dependency

Description of changes
I noticed that, when used alone, hpp-fcl python bindings lack zlib:
>>> import hppfcl
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/nix/store/dfnl1p604453r5rc29h3bnr4vjn811lj-hpp-fcl-3.0.0-pre/lib/python3.11/site-packages/hppfcl/__init__.py", line 35, in <module>
    from .hppfcl import *
ImportError: libz.so.1: cannot open shared object file: No such file or directory

Here is a fix, and also fix the import test to ensure this won't happen again.
While here, clean the package a bit.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 337549 run on x86_64-linux 1

12 packages failed to build:

python311Packages.crocoddyl
python311Packages.example-robot-data
python311Packages.hpp-fcl
python311Packages.hpp-fcl.dev
python311Packages.hpp-fcl.doc
python311Packages.pinocchio
python312Packages.crocoddyl
python312Packages.example-robot-data
python312Packages.hpp-fcl
python312Packages.hpp-fcl.dev
python312Packages.hpp-fcl.doc
python312Packages.pinocchio

5 packages built:

crocoddyl
hpp-fcl
hpp-fcl.dev
hpp-fcl.doc
pinocchio

Result of nixpkgs-review pr 337549 run on aarch64-darwin 1

12 packages failed to build:

python311Packages.crocoddyl
python311Packages.example-robot-data
python311Packages.hpp-fcl
python311Packages.hpp-fcl.dev
python311Packages.hpp-fcl.doc
python311Packages.pinocchio
python312Packages.crocoddyl
python312Packages.example-robot-data
python312Packages.hpp-fcl
python312Packages.hpp-fcl.dev
python312Packages.hpp-fcl.doc
python312Packages.pinocchio

5 packages built:

crocoddyl
hpp-fcl
hpp-fcl.dev
hpp-fcl.doc
pinocchio

Result of nixpkgs-review pr 337549 run on aarch64-darwin 1

12 packages failed to build:

python311Packages.crocoddyl
python311Packages.example-robot-data
python311Packages.hpp-fcl
python311Packages.hpp-fcl.dev
python311Packages.hpp-fcl.doc
python311Packages.pinocchio
python312Packages.crocoddyl
python312Packages.example-robot-data
python312Packages.hpp-fcl
python312Packages.hpp-fcl.dev
python312Packages.hpp-fcl.doc
python312Packages.pinocchio

5 packages built:

crocoddyl
hpp-fcl
hpp-fcl.dev
hpp-fcl.doc
pinocchio

Result of nixpkgs-review pr 337549 run on x86_64-linux 1

12 packages failed to build:

python311Packages.crocoddyl
python311Packages.example-robot-data
python311Packages.hpp-fcl
python311Packages.hpp-fcl.dev
python311Packages.hpp-fcl.doc
python311Packages.pinocchio
python312Packages.crocoddyl
python312Packages.example-robot-data
python312Packages.hpp-fcl
python312Packages.hpp-fcl.dev
python312Packages.hpp-fcl.doc
python312Packages.pinocchio

5 packages built:

crocoddyl
hpp-fcl
hpp-fcl.dev
hpp-fcl.doc
pinocchio

Result of nixpkgs-review pr 337549 run on aarch64-darwin 1

17 packages built:

crocoddyl
hpp-fcl
hpp-fcl.dev
hpp-fcl.doc
pinocchio
python311Packages.crocoddyl
python311Packages.example-robot-data
python311Packages.hpp-fcl
python311Packages.hpp-fcl.dev
python311Packages.hpp-fcl.doc
python311Packages.pinocchio
python312Packages.crocoddyl
python312Packages.example-robot-data
python312Packages.hpp-fcl
python312Packages.hpp-fcl.dev
python312Packages.hpp-fcl.doc
python312Packages.pinocchio

Result of nixpkgs-review pr 337549 run on x86_64-linux 1

17 packages built:

crocoddyl
hpp-fcl
hpp-fcl.dev
hpp-fcl.doc
pinocchio
python311Packages.crocoddyl
python311Packages.example-robot-data
python311Packages.hpp-fcl
python311Packages.hpp-fcl.dev
python311Packages.hpp-fcl.doc
python311Packages.pinocchio
python312Packages.crocoddyl
python312Packages.example-robot-data
python312Packages.hpp-fcl
python312Packages.hpp-fcl.dev
python312Packages.hpp-fcl.doc
python312Packages.pinocchio

@ofborg build pinocchio
@ofborg build crocoddyl


How to create a new user and login

user_dict = {
                'username': 'user1',
                'email'<EMAIL_ADDRESS>                'first_name': 'xxx',
                'last_name': 'xxx',
                'phone': '',
            }

# new_user.set_role(UserRole.ANNOTATOR)
created_user = ls.create_user(user_dict)
print(created_user)

how can I login with my created user, I don't see any doc for assigning password for the created user

I tried to create a first user and log in, but complaining about missing attribute cookies even though it is set by default to None here
from label_studio_sdk.client import ClientCredentials
ls = Client(url=LABEL_STUDIO_URL, credentials=credentials)

>>>
  File "/Users/.local/share/virtualenvs/ND9qtml7/lib/python3.12/site-packages/label_studio_sdk/client.py", line 91, in __init__
    else self.get_api_key(credentials)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/.local/share/virtualenvs/ND9qtml7/lib/python3.12/site-packages/label_studio_sdk/client.py", line 129, in get_api_key
    cookies=self.cookies,
            ^^^^^^^^^^^^
AttributeError: 'Client' object has no attribute 'cookies'

@fdejax90 please try it now with the latest LS SDK (0.0.34) or install it from the github repo.

BTW, In Label Studio Enterprise it's possible to create a user with password using the same API call.


No scope BOM dependency support

Candidate fix for #3088

I recall there were checks laso applying this PR to rewrite-spring and rewrite-migrate-java... don't see them now :-\

@BoykoAlex those checks weren't set up properly, so they would just run the latest snapshots, not necessarily with the changes in the pull request, on the downstream recipe jars. Gave a false sense of security

I ran rewrite-migrate-java and rewrite-spring builds with this change. Tests seem to pass now.


fix(Curriculum): Removed Step 59 from Learn Advanced Array Methods

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #56015

Removed step 59 from the  Learn Advanced Array Methods course.

Only deleting the file is not enough, there are various things to fix around


Bosch/Siemens HomeConnect appliances dont show up in latest release of Devices App

Hi,
first of all - thank you for filling the void of creating an open source eebus implementation!
I tried the latest release from releases on Mac and am unable to find any devices on the web ui:

This is the console output:
2024/08/04 12:16:26 Web Server running at port 7050
2024/08/04 12:16:26 EEBUS Service running at port 4815
2024-08-04 12:16:26 INFO  Local SKI:  4114b594bf4b30e35c6fdec6772bbb598d07b557
2024-08-04 12:16:26 DEBUG starting websocket server on :4815
2024-08-04 12:16:26 DEBUG mdns: announce
2024-08-04 12:16:26 DEBUG mdns: using zeroconf
2024-08-04 12:16:26 DEBUG mdns: start search
2024/08/04 12:16:48 Sent:  {"name":"allowremote","ski":"","services":null,"enable":true}
2024/08/04 12:16:48 Received {"name":"serviceslist"}
2024/08/04 12:16:48 Sent:  {"name":"serviceslist","ski":"","services":[{"ski":"4114b594bf4b30e35c6fdec6772bbb598d07b557","trusted":false,"state":0,"error":"","brand":"Enbility.net","model":"Devices App","itself":true,"discovery":"","usecase":""}],"enable":false}
2024/08/04 12:16:59 Sent:  {"name":"allowremote","ski":"","services":null,"enable":true}
2024/08/04 12:16:59 Received {"name":"serviceslist"}
2024/08/04 12:16:59 Sent:  {"name":"serviceslist","ski":"","services":[{"ski":"4114b594bf4b30e35c6fdec6772bbb598d07b557","trusted":false,"state":0,"error":"","brand":"Enbility.net","model":"Devices App","itself":true,"discovery":"","usecase":""}],"enable":false}
2024/08/04 12:18:42 Sent:  {"name":"allowremote","ski":"","services":null,"enable":true}
2024/08/04 12:18:42 Received {"name":"serviceslist"}
2024/08/04 12:18:42 Sent:  {"name":"serviceslist","ski":"","services":[{"ski":"4114b594bf4b30e35c6fdec6772bbb598d07b557","trusted":false,"state":0,"error":"","brand":"Enbility.net","model":"Devices App","itself":true,"discovery":"","usecase":""}],"enable":false}

I would expect a

dishwasher
washing machine
dryer
evcc device (https://docs.evcc.io/docs/reference/configuration/eebus)
to show up but nothing. Any hints what I might be doing wrong?

Hi, looks like the device doesn't show up in mDNS. Is EEBUS enabled? Is it on the same network? Does the disscovery mDNS app (free app on the app store) show the device?


Remove outdated architecture diagram

Summary
Removes outdated architecture diagram
Fixes #3700
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[x] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[ ] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[x] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 54.0% (+0.004%) from 53.996%
when pulling bf096e8330848cf28d73c2c2503e26f8cf69e72a on 3700-update-or-remove-architecture-diagram
into 6250f05b060a4d90b011b21493a0ccff2d8be91e on main.


Low uptake of TAF

TAF = Transparent assessment framework
Currently there is a low uptake of TAF within ICES

Likelihood: High as there is currently a low uptake
Impact: The potential in TAF is large and as long as it sits unused the impact of not using it is medium


DPK integration with LLamaIndex

The goal of this issue will be to explore how DPK can be integrated in llamaindex and then do the integration work.

#795 (related)


Structural changes in versioning

No longer gonna "test" stuff on this repository so gonna have a more sane tagging from now on.
Old v0.31.0 -> New v0.15.0
They're identically the same just less of a version jump.

So from now on it will be v0.15.0+1 for each change and yeah that should be it.


Flow app printing a lot of error messages

[03/30 21:34:50] [CRITICAL] [overte.scriptengine]     at Function.keys (<anonymous>)
[03/30 21:34:50] [CRITICAL] [overte.scriptengine]     at https://docs.overte.org/_static/resources/script/flow/flowAppCpp/flowAppCpp.js:434:37
[03/30 21:34:50] [CRITICAL] [overte.scriptengine] This provided: 0
[03/30 21:34:50] [DEBUG] [overte.scriptengine.v8] Emitting exception: Exception: "Uncaught TypeError: Cannot convert undefined or null to object" "[Error in signal proxy]"  at line  434 , column  36 Backtrace: ("TypeError: Cannot convert undefined or null to object", "    at Function.keys (<anonymous>)", "    at https://docs.overte.org/_static/resources/script/flow/flowAppCpp/flowAppCpp.js:434:37")
[03/30 21:34:50] [WARNING] [overte.scriptengine] run ---------- UNCAUGHT EXCEPTION --------
[03/30 21:34:50] [WARNING] [overte.scriptengine] runInThread Exception: "Uncaught TypeError: Cannot convert undefined or null to object" "[Error in signal proxy]"  at line  434 , column  36 Backtrace: ("TypeError: Cannot convert undefined or null to object", "    at Function.keys (<anonymous>)", "    at https://docs.overte.org/_static/resources/script/flow/flowAppCpp/flowAppCpp.js:434:37")

take the prints commands out, it'll be fine

take the prints commands out, it'll be fine

if an error prints but nothing breaks, does the error exist?


Bug

The color of the logo has blend with the background on daekmode

@codeboyfriend thank you for the feedback
I will be fixing this soon
If you have any new suggestions, please, I would love to hear it.
Soon new updates will come
I wish you a great day


Add Documentation for GeometryData Class and BaseParser class

Both the GeometryData class and BaseParser class currently lacks detailed documentation for its fields and methods. These two classes are important to understand how the parsing is done and what kind of data are being stored in GeometryData.

this is fixed in pull request #15


Fix multigpu set_model

This PR fixes what seems to be a bug in setting the model for multiple GPUs.

Please update the change log!

Updated - and fixed - the changelog!


I made .NET F# package for F*. Shall I merge?

Hello. Awesome work!
I wanted to compile it to F#, but it'd need git submodules and not very nice. So I decided to make a nuget package, see repo.
It's very easy to use (just adding the package as PackageReference). Here's example of a repo using this lib (see codegen.ps1).
I know there's some work making such a lib. But it included soucre files and some old targeting dlls. Instead, I suggest targeting netstandard2.0, have a new SDK-style proj file.
So, if you like the idea, I can try to add the package into this repo.

@WhiteBlackGoose hi! anything related to packaging F* for usage in .net & F# environment is really interesting.
I wanted to point at those issues, in case you haven't dug into it:

#2308
#2278

@smoothdeveloper yes I've seen them. This package looks packed wrong, that's why I'm suggesting mine. I mean... it doesn't matter if it's mine or not, but the key is, would you like it to be repacked the way I pack it? Just like a regular F# lib

I don't know how things are shifting with this repository tooling outside of OCaml toolchain, and latest F# versions deprecates stuff that implies there will be changes to occur here, eventually.
Despite things look headed like tearing appart overall, for now, I believe it would be worth to have a version of F*, up to date, released as nuget packages, and an ecosystem to build libraries with the bells & whistles F* provides that can be consumed in more general .NET projects.
It requires lots of effort around learning msbuild / .net sdk and of course, how this repository / compiler primarily works.
@7sharp9 have you played with this repository / compiler a bit?

Sorry no, I’ve used F* a little bit but not done anything than skim the compiler code.
Sent from my iPhone

On 12 Feb 2022, at 11:17, Gauthier Segay @.***> wrote:

I don't know how things are shifting with this repository tooling outside of OCaml toolchain, and latest F# versions deprecates stuff that implies there will be changes to occur here, eventually.
Despite things look headed like tearing appart overall, for now, I believe it would be worth to have a version of F*, up to date, released as nuget packages, and an ecosystem to build libraries with the bells & whistles F* provides that can be consumed in more general .NET projects.
It requires lots of effort around learning msbuild / .net sdk and of course, how this repository / compiler primarily works.
@7sharp9 have you played with this repository / compiler a bit?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.

@mateuszbujalski , any thoughts about this? You have done some similar work

@nikswamy I think that packaging F* as a nuget for easy consumption is important for the .net part of the community.
My work is still an open PR. I believe it was pretty close to getting merged and running on CI. It probably did rot a bit with time though.
I believe my solution was a bit more general and supported more use cases. It could also be consumed from both .net framework and .net standard projects. It probably could do a bit better job at filtering out not needed parts of F* binary package though, to make the package smaller.
I stopped pushing for it at some point as the project that was the main force driving my efforts died unfortunately and I've moved on since then. I also didn't have that much time to play around as quite a lot has been going on for me on the private side of things.
Nevertheless, if you're willing to get nuget packaging merged, I'm happy to revive my solution, improve it based on @WhiteBlackGoose feedback so his use case is supported (if it isn't already) and maintain it long term.


Error on integrating Vaadin Player 3.0.1 with java 8

We are getting the following exceptions on integrating Vaadin Player 3.0.1 with Java 8 ( during running it ).
Caused by: java.lang.NoSuchMethodError: java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer;
at org.vaadin.addon.audio.server.encoders.WaveEncoder.encode(WaveEncoder.java:45)
at org.vaadin.addon.audio.server.Stream.getChunkData(Stream.java:227)
at org.vaadin.addon.audio.server.AudioPlayer.lambda$registerChunkResource$46a38a13$1(AudioPlayer.java:210)
at com.vaadin.flow.server.communication.StreamResourceHandler.handleRequest(StreamResourceHandler.java:89)
at com.vaadin.flow.server.communication.StreamRequestHandler.handleRequest(StreamRequestHandler.java:106)
at com.vaadin.flow.server.VaadinService.handleRequest(VaadinService.java:1570)
It might be an issue with compiling vaadin player 3.0.1 code with > JDK8.
Plz look into https://github.com/eclipse/jetty.project/issues/3244

The 3.0.2 has been released and built with Java 8


docs: add en-us expansion-reduction.md

Please take a look @Tianqi-Dotes   chinese doc is here(https://dolphinscheduler.apache.org/zh-cn/docs/latest/user_doc/expansion-reduction.html)

Please take a look @Tianqi-Dotes chinese doc is here(https://dolphinscheduler.apache.org/zh-cn/docs/latest/user_doc/expansion-reduction.html)

what’s the problem?


[#12] [#13] [#15] [#16] [UI] [Backend] As a user, I can upload a CSV file of keywords, [UI] [Backend] As a user, I can see list of my uploaded keywords

Closes #12
Closes #13
Closes #15
Closes #16

What happened 👀

Create keywords schema and context:

Get a list of keywords by user_id.
Create a keyword.
Create a keyword list.

Show upload CSV file form.
Show uploaded keywords.

Insight 📝

Add fixture files for testing.
Create CSVParser for extracting the list of keywords and handling error states.

Proof Of Work 📹

@andyduong1920 All fixed in 413c25e


Handle legacy fork id Eth/64

PR description
The fork id computation has been updated to not include 0 fork blocks in the list of forks used to compute the fork id.
As a result, previous Besu versions are not capable anymore to talk to newest versions of Besu because their fork id are rejected with the new computation method.
We should allow previous Besu nodes to talk with new Besu nodes by adding a command line flag that enable the legacy fork id computation.
This PR adds a CLI flag to enable the legacy fork id computation method: --Xlegacy-eth-64-fork-id-enabled defaulted to false.
Fixed Issue(s)
Adresses #1541
Testing
Manual Test
Setup
Local testnet with 2 Besu nodes:

besu/v20.10.1-dev-9589ae08/osx-x86_64/adoptopenjdk-java-11

--Xlegacy-eth-64-fork-id-enabled=true

besu/v1.4.6/osx-x86_64/adoptopenjdk-java-11

Genesis
{
  "config": {
    "chainId": 1542,
    "homesteadBlock": 0,
    "eip150Block": 0,
    "eip155Block": 0,
    "eip158Block": 4,
    "byzantiumBlock": 5,
    "constantinopleBlock": 6,
    "petersburgBlock": 7,
    "istanbulBlock": 8,
    "muirGlacierBlock": 9,
    "ethash": {
    }
  },
  "difficulty": "0x20",
  "gasLimit": "0x200B20",
  "alloc": {
    "fe3b557e8fb62b89f4916b721be55ceb828dbd73": {
      "privateKey": "8f2a55949038a9610f50fb23b5883af3b4ecb3c3bb792cbcefbd1542c692be63",
      "balance": "90000000000000000000000"
    },
    "627306090abaB3A6e1400e9345bC60c78a8BEf57": {
      "privateKey": "c87509a1c067bbde78beb793e6fa76530b6382a4c0241e5e4a9ec0a0f44dc0d3",
      "balance": "90000000000000000000000"
    },
    "f17f52151EbEF6C7334FAD080c5704D77216b732": {
      "privateKey": "ae6ae8e5ccbfb04590405997ee2d52d2b330726137b875053c36d94e974d162f",
      "balance": "90000000000000000000000"
    }
  }
}

Result
Nodes are able to communicate correctly using Eth/64 subprotocol.
Admin peers of besu/v20.10.1
{
    "jsonrpc": "2.0",
    "id": 1,
    "result": [
        {
            "version": "0x5",
            "name": "besu/v1.4.6/osx-x86_64/adoptopenjdk-java-11",
            "caps": [
                "eth/62",
                "eth/63",
                "eth/64"
            ],
            "network": {
                "localAddress": "<IP_ADDRESS>:50958",
                "remoteAddress": "<IP_ADDRESS>:40303"
            },
            "port": "0x9d6f",
            "id": "0x3eca270e124b5e24e846bb39d0a911d152cfd2671be079478e72e768363c959852301b40b2afffddbe45a285fd752fa4541e8376f73dad688757e0a07a35e164"
        }
    ]
}

Admin peers of besu/v1.4.6
{
    "jsonrpc": "2.0",
    "id": 1,
    "result": [
        {
            "version": "0x5",
            "name": "besu/v20.10.1-dev-9589ae08/osx-x86_64/adoptopenjdk-java-11",
            "caps": [
                "eth/62",
                "eth/63",
                "eth/64"
            ],
            "network": {
                "localAddress": "<IP_ADDRESS>:40303",
                "remoteAddress": "<IP_ADDRESS>:50958"
            },
            "port": "0x765f",
            "id": "0x1c6d296749018e4e4a78baf9a8a3048aae2557c3f2f11a340570d57e71071e2e9816a5f5d9215a333d12b432a81ff5017520b09461c4a102e72c7a1a2d9d7d0f"
        }
    ]
}

Unit tests
Added ForkIdBackwardCompatibilityTest class to cover backward compatibility testing.
Copied legacy ForkIdManager from Besu 1.4.6 and added as a test resource to compute expected results for tests.
Changelog

[x] I thought about the changelog and included a changelog update if required.

Signed-off-by: Abdelhamid Bakhta<EMAIL_ADDRESS>

Which pairs of versions was this tested on?

20.10.1 <=> 1.4.6
20.10.1 <=> 1.5.0

And 1.4.6 and 1.5.0 is expected to continue to not work, correct? We're going to advise upgrading?

And 1.4.6 and 1.5.0 is expected to continue to not work, correct? We're going to advise upgrading?

Yes this is the plan for the moment.


Feature request: Support attribute((constructor)) for easy module loading

Related to #1717 would it be possible to implement support for constructors (__attribute__((constructor))) in jerry's C library? I think that's where it needs to be implemented, in the jerry-asm.S file.
Having support for constructors makes it easy to register modules independently of the main program, since all you have to do is compile in a module and it will be available at runtime without any additional code.

@gabrielschulhof What is your use case (hardware, OS, toolchain, program)? Jerry-libc is a very limited/restricted libc variant. Are you really using it instead of the compiler's default libc?  (I'm not saying you shouldn't, but you have to know/accept that jerry-libc is really just the bare minimum, at least for now.)

The use case is simply to make mixing and matching different modules easy. That is, adding a new module should be as simple as adding a few source files to your project, without having to have those source files exports some well known entry point, and without having to modify your main.c (or whatever) to call those entry points whenever the module mix changes for your project.
Consider the following example. You make one small change to your Makefile:
...
diff a/Makefile b/Makefile
+obj-$(MY_COOL_MODULE) = my_cool_module.c
...

and now, without any further code changes, your project supports
var my_cool_module = require( "my_cool_module" );

Without this feature, you would need
...
diff a/Makefile b/Makefile
+obj-$(MY_COOL_MODULE) = my_cool_module.c
...
diff a/main.c b/main.c
+#ifdef BUILD_WITH_MY_COOL_MODULE
+#include "my_cool_module.h"
+#endif /* def BUILD_WITH_MY_COOL_MODULE */
...
+#ifdef BUILD_WITH_MY_COOL_MODULE
+my_cool_module_init();
+#endif /* def BUILD_WITH_MY_COOL_MODULE */
...

which is a lot harder to maintain.
Also, Node.js uses constructors to start the process of loading modules, so this would increase interoperability with Node.js native addons - a project I'm currently working on 😀
I'm fairly certain that I'm using jerry-libc when the constructor doesn't work, because if I turn off -static and -nostdlib, the constructor works and it links to /lib64/libc.so.6.
I understand that jerry-libc is the bare minimum, which is why I would like to discuss the cost/benefit of adding this feature. The fact is that constructors are something that cannot be implemented by writing a few functions, because people (including me) would need to know assembly to implement that support, whereas features that can be expressed as a set of functions, even if they should go into a C library, need not go in if it is to be minimal, because they can be maintained outside - because they're just plain C code, and a lot more people know how to read/write/maintain that.
And yes, the above example is also C code, so yes, it could be maintained without constructors, but it's all boilerplate which could be avoided with constructors. Besides, constructors are supported by quite a few platforms - all the ones Node.js runs on, at any rate.

Question: could this be done in a way that the linker can cut the support when it is not used? At least the majority of it. If yes, I don't mind having this feature.

@zherczeg I don't think so. But it could be a compile time option for jerry-libc whether to support constructors or not. (BTW, it ctors are supported, it's nice to support destructors, too, as they walk hand-in-hand, quite often.)

@gabrielschulhof I get the usefulness of constructors. Where I'd like to pick your mind is why you'd like to use jerry-libc? Especially as you are mentioning Node.js native addons. Because of the minimalistic implementation of jerry-libc, the lack of constructors will be the least of your problems, I'd guess. You have been warned :)

Actually, after module registration, things are pretty straight forward, because I'm implementing the new Node.js N-API which maps ECMAScript pretty closely. The only challenges are scopes (which I have implemented as linked lists), and externals (a primitive type not part of ES, but which both N-API-supporting engines (V8 and ChakraCore) expose in order to make passing pointers into JS easier than having to wrap objects).

My ultimate goal is to use N-API to make it possible to build Node.js modules on JerryScript without any code changes. So, like, the same C-file will build against Node.js and against JerryScript. This could be good for both projects, because it would make Node.js addons more memory-consumption-conscious, and it would bring more addons to JerryScript. Of course it's all one big experiment 😃

@gabrielschulhof There are two major issues I see:

JerryScript is not the scaled-down version of Node.js, they are not at the same level of a software stack. Node.js is a whole ecosystem, something that is built on top of a JavaScript engine (V8 in that case). JerryScript is not that. It is a JS engine, say, the scaled-down version of V8 (actually, not, but the analogy works). I know that there is a related issue where discussion is already ongoing - even though a bit late, I'll join the club and speak my thoughts.
I envision a lot of problems trying to build Node.js native modules against jerry-libc. Constructors are not the only feature that are there in standard libc's (and projects rely upon) but are not there in jerry-libc.

That being said, constructors (and destructors) can be supported by jerry-libc, most probably. I'll try to come up with an implementation in the coming days.

@gabrielschulhof, have you tried to build with newlib or ulibc? IMHO those would be more suitable for your usecase.

@akosthekiss I understand that JerryScript is a JS engine and not a full runtime. The fact though is that by its very nature of being designed for constrained environments it provides some features of a runtime - such as a C library. Also, don't forget that I'm not talking about Node.js C++ modules linked directly against V8. I'm talking about the new N-API that has just landed in Node.js master, which is a C interface that seeks to be independent of the underlying JS engine and tracking ES itself.
We have already ported many of the most popular Node.js modules which were using the V8 API to N-API so that we can validate its function, performance, and completeness, and now I'm trying to see if it's possible to provide JerryScript's API as an implementation of N-API.
@LaszloLango I can certainly build with a different C library. In fact, until a few days ago I didn't even know that the system C library will run constructors even if they are linked into an executable :) I thought constructors only work with dlopen() :) So, I created two different entry points for my module - one for Node.js via the library constructor, and one via an exported function. This kept the central code providing the module functionality engine-agnostic, but it made the module registration code engine-specific. I figured that it may be worth implementing constructors in JerryScript to iron out this difference, and then we can use a single header for the API definition in both Node.js and JerryScript.

@gabrielschulhof have a look at #1725, see whether it works for you.
(BTW, one more potential issue came to my mind: I'm not sure how you'd like to register modules but note that a lot of jerry API functions cannot be called until jerry_init is called. Which means that jerry API is effectively blocked for constructor functions.)

@akosthekiss Aaaah, I'm glad you brought that up :) The module loading is broken into two steps. Indices into the pointer array are assigned at boot time in response to the constructor call. The module name is also added to a linked list for subsequent lookup by require(). This is context-independent and requires no cooperation from jerryscript. It's purely runtime initialization.
Only when require() gets called from JS is the resulting linked list consulted and, when a module is found, its initialization routine (which returns a jerry_value_t) called. Since the process starts from JS, an initialized context must be present.
This is contrast to Node.js, where bootup and initialization are one and the same. But then in Node.js every module gets dlopen()-ed in response to a require(), so obviously the environment is already there.

Closing as #1725 has landed


add option of 'none' for Container Network select in Basics tab of RKE2 provisioning

Summary
Fixes #10338

Occurred changes and/or fixed issues

add option of 'none' for Container Network select in Basics tab of RKE2 provisioning
add e2e test to check that option is available and can be selected

Technical notes summary

Areas or cases that should be tested

Under Cluster Management, create a RKE2 custom cluster
On the Basics tab, Container Network select, select the option none
Check that on the network request payload has been sent with none and check YAML after creation to confirm as well

spec.rkeConfig.machineGlobalConfig.cni
Areas which could experience regressions

Screenshot/Video

Confirmation of data after cluster creation

lgtm

The cluster I created never became available, but so did cluster with regular configurtion, so I don't think it's because of this change

@eva-vashkevich I've changed this PR with the correct logic to add the option none. Turns out the failing unit test exposed a problem that I didn't foresee.
The logic couldn't be applied to the Basics component directly because it's a prop that is passed from the rke2 component down to the Basics component.
Now everything is correct, I believe. Could you re-review this please? 🙏

Did creating an instance with 'none' setting work for you? It seems stuck in the updating state for me

It's not supposed to provision because it needs additional configuration. The aim of the none option is to allow for custom network config.


metricreader: fix that sometimes the metric history is not purged

What problem does this PR solve?

Issue Number: close #638
Problem Summary:

When multiple TiProxy read the metrics of the same TiDB, the history may grow longer and longer. This is because the history that is read from the other TiProxy overwrites the local history that is purged.
When the owner can connect to Prometheus but a member fails to connect to Prometheus, the member reads stale metrics.

What is changed and how it works:

Extract marshalHistory and history2QueryResult to the common path.
Call marshalHistory and history2QueryResult after purgeHistory
Call readFromBackends before readFromOwner

Check List
Tests

[x] Unit test
[ ] Integration test
[x] Manual test (add detailed scripts or steps below)
[ ] No code

Manual test:
Follow the steps described in the issue and check the data from /api/backend/metrics
Notable changes

[ ] Has configuration change
[ ] Has HTTP API interfaces change
[ ] Has tiproxyctl change
[ ] Other user behavior changes

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

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

Please upload report for BASE (main@3a49e3c). Learn more about missing BASE report.

Files
Patch %
Lines

pkg/balance/metricsreader/backend_reader.go
71.42%
8 Missing and 4 partials :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #639   +/-   ##
=======================================
  Coverage        ?   69.03%
=======================================
  Files           ?       86
  Lines           ?     8052
  Branches        ?        0
=======================================
  Hits            ?     5559
  Misses          ?     2095
  Partials        ?      398

Flag
Coverage Δ

unit
69.03% <71.42%> (?)

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

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


fix

That's right. Please, write your email.

<EMAIL_ADDRESS>

Does anyone know any active discussions on this bug and ways to fix it? I've found only https://bugs.swift.org/browse/SR-7048.


filenames become incorrectly formatted when using s3 direct upload

[I tried to post this in the Google Group but it didn't seem to work.]
Firstly, I wanted to say thanks for making a great tool for Ruby.
With direct S3 uploading, the filenames are incorrectly formatted when I try to redownload them from S3.
For example
“Fugiat Ab Est Consequatur Saepe” at Aut Nihil Culpa Quidem Ut Delectus, 2017.pdf
redownloads as
“Fugiat Ab+Est+Consequatur+Saepe”+at+Aut+Nihil+Culpa+Quidem+Ut+Delectus%2C+2017.pdf
Note that the filename has open/close quotes, not the normal quotes. Weirdly the first space is correct, but the rest turn into + . It seems like just a few random characters don't appear correctly, like ()^,'"
I also noticed that if I upload files to S3 via the web-based console I get almost the exact same problem.
Doesn't seem to be caused by the encode_content_disposition method in storage/s3.rb .
The filename is stored correctly in the database:
{
  "original": {
    "id": "doc\/591\/docshrine\/original-be415b340c9fef6c2ba4ad1d6583632e.pdf",
    "storage": "store",
    "metadata": {
      "size": 536018,
      "filename": "\u201cFugiat Ab Est Consequatur Saepe\u201d at Aut Nihil Culpa Quidem Ut Delectus, 2017.pdf",
      "mime_type": "application\/pdf"
    }
  }
}

But the metadata looks weird in S3:
attachment; filename="%E2%80%9CFugiat Ab+Est+Consequatur+Saepe%E2%80%9D+at+Aut+Nihil+Culpa+Quidem+Ut+Delectus%2C+2017.pdf"
My javascript:
Dropzone.autoDiscover = false;

$(document).ready(function(){
    var myDropzone = new Dropzone('div#docDrop', {
      url: '#',
      // Need to override the parameter so that it plays nicely
      paramName: 'file',
      maxFiles: 800,
      maxFilesize: 4900,
      timeout: 0,
      // We are manually triggering queue processing
      autoProcessQueue: true,
      autoQueue: false,
      createImageThumbnails: false,
      parallelUploads: 3,
      addRemoveLinks: true,
      dictRemoveFile: "✕",
      dictInvalidFileType: "Format not supported.",
      previewTemplate: docTemplate(),
      init: function() {
        myDropzone = this

        // Whenever a file is added, get the presigned S3 URL and attach it
        myDropzone.on('addedfile', function(file) {

          // Set the extension and add a date to avoid any strange caching
          // This options hash is sent to the presign URL to get S3 information
          options = {
            filename: file.name,
            _: Date.now()
          };

          $.ajax({
            url: '/presign',
            data: options,
            type: 'GET',
            success: function(response){
              file.additionalData = response['fields'];
              myDropzone.options.url = response['url'];
              myDropzone.enqueueFile(file);
            }
          });

        });

        // Before sending a file, set the formData to the S3 fields stored above
        myDropzone.on('sending', function(file, xhr, formData) {
          $.each(file.additionalData, function(k, v) {
            formData.append(k, v);
          });
        });

        myDropzone.on('success', function(data, asdf) {
          doc = {
            id: data.additionalData.key.match(/cache\/(.+)/)[1],
            storage: 'cache',
            metadata: {
              size: data.size,
              filename: data.name,
              mime_type: data.type
            }
          };

          var data = data;

        // After a file is successfully uploaded, we need to send it back
        // to Rails so that it can be attached to the Doc model
          $.ajax("/docs", {method: 'POST', data: {doc: {docshrine: JSON.stringify(doc)}}})
            .done(function(response) {
              vals = $('.doc_list').val();
              if (vals.length) {
                vals = vals.split(',');
              } else {
                vals = new Array();
              }
              vals.push(response.id);

              $(data.previewElement).addClass('dz-success').
                attr('data-docId', response.id).
                find('.dz-doc-filename').attr('href', response.original);

              updateDocFields(vals);
              myDropzone.processQueue();
            });

        });
      }
    });
  }
});

function updateDocFields(vals) {
  $('.record > form').change();
  $('.doc_list').val(vals.join(','));
}

function docTemplate(){
  return '
' +
  '  ' +    //
  '

' +
  '

' +
  '
';
}

config/initializers/shrine.rb
require "shrine"
require "shrine/storage/s3"

if !Rails.env.production?
  require "dotenv"
  Dotenv.load!
end

s3_options = {
  access_key_id:     ENV.fetch("AWS_ACCESS_KEY_ID"),
  secret_access_key: ENV.fetch("AWS_SECRET_ACCESS_KEY"),
  region:            ENV.fetch("AWS_REGION"),
  bucket:            ENV.fetch("S3_BUCKET_NAME"),
}

Shrine.storages = {
  cache: Shrine::Storage::S3.new(prefix: "cache", upload_options: {acl: "public-read"}, **s3_options),
  store: Shrine::Storage::S3.new(prefix: "store", upload_options: {acl: "public-read"}, **s3_options),
}
Shrine.storages[:cache].url(public:true)
Shrine.storages[:store].url(public:true)

Shrine.plugin :activerecord
Shrine.plugin :logging, logger: Rails.logger
Shrine.plugin :presign_endpoint, presign_options: -> (request) do
  filename     = request.params["filename"]

  {
    content_disposition: "attachment; filename=\"#{filename}\""
  }
end
Shrine.plugin :presign_endpoint, presign_location: -> (request) do
  "#{SecureRandom.hex}_#{request.params["filename"]}"
end

Shrine.plugin :backgrounding
Shrine.plugin :default_url_options, store: {public: true}

Shrine::Attacher.promote { |data| PromoteJob.perform_async(data) }
Shrine::Attacher.delete { |data| DeleteJob.perform_async(data) }

doc_uploader.rb
class DocUploader < Shrine
  plugin :determine_mime_type
  plugin :remove_attachment
  plugin :store_dimensions
  plugin :validation_helpers
  plugin :pretty_location
  plugin :processing
  plugin :versions, fallback_to_original: true

  Attacher.default_url do
    "/delayed_processing.png"
  end

  process(:store) do |io, context|
    {original: io}
  end

end

Any ideas of how to make all filenames appear correctly when redownloading?
Thanks!

@dauncing Thank you for such a detailed issue report.

With direct S3 uploading, the filenames are incorrectly formatted when I try to redownload them from S3.

This has actually been fixed in Shrine 2.9.0. It won't affect the existing uploads (because :content_disposition is a static object attribute), only new uploads.

But the metadata looks weird in S3

This is because Shrine URI-encodes the filename for :content_disposition (that's where the bug with + symbols came from). The reason for that is to avoid non-ASCII characters, as they break AWS SDK's signature generation. This should be fine, because browsers seem to automatically URI-decode the filename on download.

[I tried to post this in the Google Group but it didn't seem to work.]

Hmm, I'm not sure why is that 🤔. The asdf post you tested with was in fact posted, but the other one wasn't, I didn't even get any "pending approval" notification.

Thanks for the quick reply!
Updating Shrine to 2.9 fixed the problem with spaces. However I'm still finding that all other URI-encoded characters are not decoding on many browsers/OSes when I try to redownload.
I played with encode_content_disposition to only encode doublequotes ". Even if I don't escape filename at all it doesn't break the upload. All characters render perfectly except doublequotes, which turn into underscores. But I had weird behavior in some browsers when saving files that had the unescaped doublequote.
So for now, unless I find more bugs, I will patch line 425 with simply filename.gsub('"', '\'')
Judging from the issue you linked to and other related discussions, it seems like this issue is partly outside the scope of Shrine.
Thanks again.

However I'm still finding that all other URI-encoded characters are not decoding on many browsers/OSes when I try to redownload.

Oh, that's unfortunate. Yeah, I remember now that someone mentioned Firefox and perhaps even Chrome. I was hoping that other browsers do it as well.

Judging from the issue you linked to and other related discussions, it seems like this issue is partly outside the scope of Shrine.

Yeah, the issue is entirely in the aws-sdk-s3 gem, if I include non-ASCII characters, then aws-sdk-s3 gem will generate a different signature than the S3 service, and S3 will return an error response saying the signature was invalid.
Since this issue was effectively marked as "wontfix" on the aws-sdk-s3 repo, I decided that it was better to ensure that all uploads succeed, even if that means thae some characters might not display properly. But maybe it would be more correct to simply strip away all non-ASCII characters and only URI-encode the double quotes, I don't have a strong opinion about that.


EIP-7251: Fix off-by-one in churn computations

Resolves https://github.com/ethereum/consensus-specs/issues/3677
This PR refactors churn computations and resolves the above issue. Ideally, we would have one method handling computation for both churns if a number of parameters involved in the computation were lower, it is just ugly to pass four params to a method with four lines of code and would hinder readability IMO.

lgtm

and I do think we should refactor into one common compute_epoch_and_balance_to_process or something but we can do that later

I attempted to do that but the call to such method looks really cumbersome because of a number of params passed onto it


V1 tezos interop

Changes chain to commit on Tezos. As indicated in chain.ml, this is level-based and not time-based, which is not ideal. Also the consensus should watch for those updates. Also, better tests.
Manual tests: start the chain and see that the contract storage gets updated. This should not break deposits either.

Fixed according to @Pilou97's offline comments


Not Working in Azure DevOps Server 2019

Hi Team,
We are trying to use this extension in Azure DevOps Server 2019. When we run the pipeline we are facing below issue
issue 1: Plugin is not detecting target branch

Issue: Self Signed certificate issue
I tried to give Target branch through variables to check, then I am getting below error

Please let us know how we can make this work in On-prem Azure DevOps server 2019
Thanks
Balaji

@mlarhrouch Need help.

Exactly the same in Devops Server 2020:
fatal: ambiguous argument 'origin/undefined': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git  [...] -- [...]'

And I Use AzureOpenAI
Thanx in advance

@ezephillips seems like in Devops Server there is no System.PullRequest.TargetBranchName variable, a new PR will be created to fix this

@ezephillips seems like in Devops Server there is no System.PullRequest.TargetBranchName variable, a new PR will be created to fix this
Great! Thnx!!

@ezephillips a new version of the package is published (version 0.8.3), can you please check if the issue is fixed for you

@ezephillips notice that this repo is not supporting AzureOpenAI yet, a new issue is created to support it https://github.com/mlarhrouch/azure-pipeline-gpt-pr-review/issues/11


Keybase teams chat has #general and ##general

The groups have different memberships. I am unable to rename either one.

This may have happened because we joined the team at a VERY early stage and there was probably some errors on my part during the setup.
What can I do to delete one of these channels?

These types of issues are the best. Usually when developing apps, you don't think about these types of cases.
I think it would probably be a quick fix.

cc @mmaxim I'm not sure if that is tracked internally


Overlays are not deleted in native once destroyed in React Native

Bug report

Summary

Currently when you update the map with components such as overlay from the state and add and remove them many times, such as when moving the map, these elements are unmounted in react but persist on the map, which makes the application start to consume RAM until it fails.
Environment info

react-native info output:
      react-native: 0.63.3
      react: 16.13.1
      react-native-maps: 0.27.1

Steps to reproduce

Have a map and inside an array (what will come from the state) that will be filled with overlays
I create the overlay in a different component, for test if is unmounted.
Add many overlays to the array, for example 15 per second, and clean, add, clean, add, clean

Describe what you expected to happen:

React Native unmount components
Java/Ios remove the native component from the map

Describe what you actually happens:

React Native unmount components
Java/Ios does not remove the native component from the map and acumulate

Reproducible sample code

I found it.
There is a small bug in the Java code, probably the same bug will be in Objective C.
I will upload a PR to solve this bug.

Can you tell me if this problem has been fixed? I have a case here that is happening this same problem!


Rocket not able to find a destination

Version of Advanced Rocketry
1.4.0-77
Have you verified this is an issue in the latest unstable build
No
Version of LibVulpes
0.2.8-29
Version of Minecraft
1.12.2
Crash report
https://pastebin.com/N3F52mhr
Description of the problem
Create a space station, place a docking pad. Make a rocket in the overworld, launch it to the docking pad, send it back. Then break the docking pad and remove the blocks were the rocket landed the first time. When you launch the rocket next time (In this case it was unmanned) it crashes the server.

Is this still a issue? Please comment if it is and i will reopen if if you are unable? We are closing old issues to see what is still relevant and needs to be fixed.


Add support for end repair of small circular contigs. The flye_end_repair.sh script assumes the contig is at least 100 kb in length at the moment, and in a hard-coded way.

@jmtsuji Feel free to delete if addressed.

Addressed in the updated code -- the size range of circular contigs can now be specified in the config file. Closing this issue.


[Suggestion] Add Velocity Support

Hello,
I have a simple suggestion, make a version compatible with Velocity.
Since Waterfall was archived and discontinued, I've switched to Velocity, and I don't think I'm the only one. Since then, I've been unable to use BungeeGuardPlus, which is really annoying for me.
Thanks in advance.

Hello, I have a simple suggestion, make a version compatible with Velocity. Since Waterfall was archived and discontinued, I've switched to Velocity, and I don't think I'm the only one. Since then, I've been unable to use BungeeGuardPlus, which is really annoying for me.
Thanks in advance.

Hi, @SniperTVmc!
Follow the instructions to configure BungeeGuard on Velocity:
https://en.docs.nickuc.com/proxy/bungeeguard

Hello, I have a simple suggestion, make a version compatible with Velocity. Since Waterfall was archived and discontinued, I've switched to Velocity, and I don't think I'm the only one. Since then, I've been unable to use BungeeGuardPlus, which is really annoying for me.
Thanks in advance.

Hi, @SniperTVmc!
Follow the instructions to configure BungeeGuard on Velocity:
https://en.docs.nickuc.com/proxy/bungeeguard

Aw shit.. excuse me, I didn't think that's how this option was used like that! Thanks for the information!

No problem! If your server supports the modern forwarding type, I recommend using it, it is superior to BungeeGuard, but it only works for 1.14+ and some 1.13 versions.


DirecTV error/exception

Home Assistant release (hass --version):
0.26.2
Python release (python3 --version):
Python 3.4.5
Component/platform:
media_player/directv
Description of problem:
16-08-18 20:16:31 homeassistant.components.media_player: Error while setting up platform directv
Expected:
No error.
Problem-relevant configuration.yaml entries and steps to reproduce:
discovery:

media_player:
  - platform: plex
  - platform: directv

Enable discovery
Start HASS

Traceback (if applicable):
16-08-18 20:16:31 homeassistant.components.media_player: Error while setting up platform directv
Traceback (most recent call last):
  File "/usr/local/home-assistant/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 98, in _setup_platform
    discovery_info)
  File "/usr/local/home-assistant/lib/python3.4/site-packages/homeassistant/components/media_player/directv.py", line 44, in setup_platform
    dtvs.append(DirecTvDevice(*host))
  File "/usr/local/home-assistant/lib/python3.4/site-packages/homeassistant/components/media_player/directv.py", line 60, in __init__
    self.dtv = DIRECTV(host, port)
  File "/usr/local/home-assistant/lib/python3.4/site-packages/DirectPy.py", line 33, in __init__
    self.get_tuned()
  File "/usr/local/home-assistant/lib/python3.4/site-packages/DirectPy.py", line 73, in get_tuned
    self.channel = self._combine_channel(jResp['major'],jResp['minor'])
KeyError: 'major'

@hoopty, what DirecTv componets do you have?  Are you using a TV with an RVU?

HR44-200 - Genie Gen 2
C41-100 - Genie Mini
RVU TV - Samsung Smart TV (2013, I think)

Let me know if there is any more information or troubleshooting I can provide.

@cbulock - any ideas?

Same issue - HASS installed in virtual env, I also have an RVU.
Home Assistant release (hass --version):
0.27.1
Python release (python3 --version):
Python 3.4.2
Component/platform:
media_player/directv
Description of problem:
Unable to discover or manually configure DirecTV
Expected:
Successful discovery/setup of DirecTV
Problem-relevant configuration.yaml entries and steps to reproduce:
discovery:

media_player:
  platform: directv
  host: <IP_ADDRESS>
  name: DirecTV Living Room

Enable discovery
Start HASS
Issue also occurs with just discovery enabled.
Traceback (if applicable):
16-09-03 13:37:39 homeassistant.components.media_player: Error while setting up platform directv
Traceback (most recent call last):
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 98, in _setup_platform
    discovery_info)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/media_player/directv.py", line 44, in setup_platform
    dtvs.append(DirecTvDevice(*host))
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/media_player/directv.py", line 60, in __init__
    self.dtv = DIRECTV(host, port)
  File "/home/hass/.homeassistant/deps/DirectPy.py", line 33, in __init__
    self.get_tuned()
  File "/home/hass/.homeassistant/deps/DirectPy.py", line 73, in get_tuned
    self.channel = self._combine_channel(jResp['major'],jResp['minor'])
KeyError: 'major'

I still haven't had a chance to make any progress with this, sorry. Hopefully I can get some time this week.

Same problem here. HASS discovers the directv box but then throws an error..
16-09-10 14:49:52 INFO (Thread-2) [homeassistant.components.discovery] Found new service: directv ('<IP_ADDRESS>', 'RID-025222650084') 16-09-10 14:49:52 INFO (Thread-2) [homeassistant.components.discovery] Found new service: DLNA http://<IP_ADDRESS>:49152/2/description.xml 16-09-10 14:49:52 INFO (ThreadPool Worker 13) [homeassistant.core] Bus:Handling <Event platform_discovered[L]: discovered=('<IP_ADDRESS>', 'RID-025222650084'), platform=directv, service=load_platform.media_player> 16-09-10 14:49:52 INFO (ThreadPool Worker 13) [requests.packages.urllib3.connectionpool] Starting new HTTP connection (1): <IP_ADDRESS> 16-09-10 14:49:52 INFO (ThreadPool Worker 13) [requests.packages.urllib3.connectionpool] Starting new HTTP connection (1): <IP_ADDRESS> 16-09-10 14:49:53 ERROR (ThreadPool Worker 13) [homeassistant.components.media_player] Error while setting up platform directv Traceback (most recent call last):   File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/helpers/entity_component.py", line 98, in _setup_platform     discovery_info)   File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/components/media_player/directv.py", line 44, in setup_platform     dtvs.append(DirecTvDevice(*host))   File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/homeassistant/components/media_player/directv.py", line 60, in __init__     self.dtv = DIRECTV(host, port)   File "/Users/dustinmcgrew/.homeassistant/deps/DirectPy.py", line 33, in __init__     self.get_tuned()   File "/Users/dustinmcgrew/.homeassistant/deps/DirectPy.py", line 73, in get_tuned     self.channel = self._combine_channel(jResp['major'],jResp['minor']) KeyError: 'major'

I spent some time tracking this down. The server is sending an unexpected response that looks like this:

I just spent some time tracking this down. It is caused by an unexpected server response.
{'status': {'msg': 'Forbidden.Command not allowed.', 'query': '/tv/getTuned?clientAddr=0', 'code': 403, 'commandResult': 1}}

I did some digging around online and found the DirectTV SHEF API spec for version 1.3c
According to that document the API /getVersion provides metadata about the software running on your box. Here is the response from my box.
{'accessCardId': '****-****-****', 'stbSoftwareVersion': '0xc45', 'receiverId': '**** **** ****', 'status': {'msg': 'OK.', 'query': '/info/getVersion', 'code': 200, 'commandResult': 0}, 'version': '2.1', 'systemTime':<PHONE_NUMBER>}

It appears that the current version of this API is 2.1 but I could not find any later documentation then the one linked above. I can only suspect that DirectTV has disabled this functionality or has a new authentication scheme that is not documented there either.

After reviewing DirectPy.py, there is an issue in '_combine_channel' not handling the 'major' and 'minor' mappings.  I was able to get the module to load and work by making the following change to line 73:
self.channel = jResp['major']

After reviewing DirectPy.py, there is an issue in '_combine_channel' not handling the 'major' and 'minor' mappings.  I was able to get the module to load and work by making the following change to line 73:
self.channel = jResp['major']

It seems the latest update just disables some of the access by default. I was able to fix it by going to Menu -> Settings -> Whole-Home -> External Device and set everything to Allow. Cheers!

@jstarcher - that fix worked for me!

Works for me as well, closing issue!

I have a Genie box and a RVU. I can only get the Genie box to show up. Any ideas on how to get the RVU up? I can get the TV to show up but it does not seem to show directv stuff. They obviously use different ports to control and 8080 does show on a nmap of the tv's ip. Any help is appreciated.
Thanks in advance.

I was able to read information from the RVU by using @cbulock DirectPy fork that has the function get_locations. If you connect to the main one and then run get_locations you will see how many are connected and then see a clientAddr for each one. If you then initiate the second location DIRECTV(ip, port, clientAddr) you will then have access to the all the same functions as the original. Such as get_tuned(). I am new to python and still learning but is there a way to include cbulocks version on directpy and then update home assistant to control multiple locations.

Or would it make sense to just update home-assistant/homeassistant/components/media_player/directv.py with an optional clientAddr so that if set it can create a connection using a different clientAddr. I wouldn't mind doing it myself but I do not know python very well. Maybe some guidance would help as well.

I was going that route at one point. Was adding the clientaddr function to
directpy and was then going to add it in the Hass component. Python is also
not a language I'm all the versed in, and I've been distracted with some
other things lately so haven't gotten around to coming back to this.
On Feb 5, 2017 2:56 PM, "rmendoza3"<EMAIL_ADDRESS>wrote:

Or would it make sense to just update home-assistant/homeassistant/
components/media_player/directv.py with an optional clientAddr so that if
set it can create a connection using a different clientAddr. I wouldn't
mind doing it myself but I do not know python very well. Maybe some
guidance would help as well.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/2876#issuecomment-277544455,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKxhwVWvAAZq8ghmGphfFOdcTUbDi0Nks5rZilOgaJpZM4JoELw
.

I do not know when I will finish it, but I will be trying. I guess its time to get well versed in python and home assistant. Thanks for providing all the previous information. Much appreciated.

Where are we on a solution to getting access to the Genie remote boxes?

I apologize for the late reply. I have been very busy with work. As for the project, I created a test environment and updated the code that allows an updated yaml config for clientaddr. The clientaddr is the remote box mac address. My next step was to look into adding code for the auto discovery to configure but I just do not have the time at the moment.


WIP -- Add a storage backend that works for DSE-5.0

Add a storage backend that works for DSE-5.0
This would be helpful for those that can't upgrade to cassandra-3.9

Basic thoughts and a skeleton for using Zipkin with the new style of Cassandra datamodel, but replacing the SASI with Solr Cores. This allows the data model to run against Cassandra-3.0.8+ but does require a DSE installation.
A fair bit of work still has to happen here, wiring it together, etc.
But the basic idea is in place.

interested, as I'm interested in decommissioning the "cassandra" module, but I don't think this gets us there, as not everyone uses DSE. Basically, we end up with 3 codebases for cassandra that don't share code.
I know @schrepfler asked about DSE, but not sure if he uses zipkin at the moment or not. Do we have a good gauge of how many use DSE?
I'm concerned about the maintenance problem of bringing this into the core repo, particularly as it is getting bloated and it doesn't seem obvious how to test commercial variants like this. There's also bus factor.. we're lucky we have you, but there's few others working on cassandra, almost none. Can we afford to have a third codebase? Finally, we already blow up on memory often as it is and our builds are approaching 20minutes.. Feels like it should be a separate repo.
@openzipkin/cassandra @abesto What are your thoughts?

Personally I would rather not include the code into master, for the same reasons you describe @adriancole
But I did want to at least throw the code out here, so that others could take it (if only the idea) and run if they wanted to.

@michaelsembwever I noticed this has a dep on cassandra3. seems CassandraSpanConsumer is the same type, but it has a different front-end (SpanStore) and schema.
Am I right to think that this is "effectively" the same schema? Else, I'd assume you wouldn't be able to use cassandra3's CassandraSpanConsumer
While this PR is >2K lines, it seems some of it is benign (ex UDT related cruft) or some things that have to be copy/pasted. The heaviest class seems to be the SpanStore variant. Is that a fair assessment?

Yes it is the same schema as far as writes go. Just that the SASI are not used. DSE Solr Cores replace them.

Personally I would rather not include the code into master, for the same
reasons you describe @adriancole https://github.com/adriancole
But I did want to at least throw the code out here, so that others could
take it (if only the idea) and run if they wanted to.

Historically, most of the repos we spun out from concerns about interest
didn't turn into anything. Ex mongo and redis went to separate repos to
die. However, I think it is more reasonable that this could live. I'd offer
effort to carve out a repo for this.
We could attract attention to it, saying that once cassandra3 is done,
we'll deprecate "cassandra" for removal at some point. Those who can't
upgrade on account of DSE should look to the zipkin-storage-dse5 repo. If
no-one is interested enough even to comment there, then there's not much
else we can do... worst case, it dies.

Thanks for answering my questions, @michaelsembwever! I'll shut up and see what others think

I would go with external repo and some sort of contrib model and zipkin-storage-dse5 sounds fine (ideally Datastax themselves would be maintainers as they know their features best and it would advocate optimal use of their product.)
Is the DSE Solr interface so much different when starting Cassandra with the parameters to turn on string indexing using ES or Solr (I was under the impression Cassandra ships with such an example config but I can't find it in my instance, perhaps I've seen it in use on some modified Cassandra ex. Titan+Cassandra+ES)?

Is the DSE Solr interface so much different when starting Cassandra with the parameters to turn on string indexing using ES or Solr …

@schrepfler i'm only familiar with the rather basic approach of using dsetool create_core …  from the command line to create the Solr Core off a C* table.

I think that's the way to go too, haven't dealt with it directly though.

AFAIK there's the command line client, and a deprecrated? HTTP endpoint. Sadly can't create the indexes from CQL directly since you need the solr config.


listing layout choices

Great theme!
I am having an issue getting the list-grid feature to work. Quite simply, I place the 'list-grid' in place of 'list' as described here: https://hugo-apero-docs.netlify.app/start/section-config/?panelset1=list-sidebar-%25F0%259F%2593%25B7 but it doesn't switch the layout to grid.
Any suggestions?

What have you tried so far? Are you trying it for one blog or all blogs? What does your YAML look like (for the blog) and _index.md for blog?

I tried using the 'list-grid' format as the Apero documentation indicate but it doesn't change the layout to a grid. I am attempting to do it for one page only. Here are the contents of the _index.md for that page:

author:
description: Voici des projets de recherche actuellement en cours, ou récemment complété.
layout: list-grid
show_post_date: false
show_post_thumbnail: true
title: Projets de recherche
Any assistance is greatly appreciated. Thanks.

It is challenging to know by just looking at these lines. Also, I wonder if the order in YAML matters. Can you share the Github repo or the folder (/blog/)? To try anything new, we would need a reproducible example.


License Text Duplicated in ProxyCmdletDefinition.ps1

The License header emitted into ProxyCmdletDefinition.ps1 by [Export-ProxyCmdlet](https://github.com/Azure/autorest.powershell/blob/59e8eb2020d0f70fabd5ef0cc203996b4d818f63/powershell/resources/psruntime/BuildTime/Cmdlets/ExportProxyCmdlet.cs#L86-L99) is duplicated for each cmdlet. Generating unnecessary bloat in the resulting Nuget Package and ProxyCmdletDefinition.ps1 file.
It would be ideal if only one license instance was present at the head of the file.

Fixed in https://github.com/Azure/autorest.powershell/pull/824

Hi @dolauli .
Can this fix be applied to the msgraph branch as well? Otherwise we will remain with this issue.
Thanks!


[Bug]: Placing a block beside an existing block pushes the existing block downward

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When placing a block next to an existing block, the existing block is pushed downward. This issue does not occur with our legacy container widget.
Steps To Reproduce

D&d a block on the canvas.
Now drop another block next to the already placed block.

Expected: The new block should be placed next to the already existing block.
Actual: The already placed block gets displaced downwards
Public Sample App
No response
Environment
Release
Severity
High (Blocker to building or releasing)
Issue video log
https://jam.dev/c/7ca2fece-c9ca-41cc-a080-37a22f9cd3ff
Version
Cloud

Bumping this issue up to prod because it should have made it's way there by now if it was not fixed


[Bug]: tuple index out of range when calling LLM with prompt keyword arg

Bug Description
This succeeds:
output = llm.complete(prompt)

but see how it fails in Steps to Reproduce below. I could be wrong if providing prompt as a keyword arg is unsupported, but I didn't see any documentation or comments about that.
Version
0.10.30
Steps to Reproduce
output = llm.complete(prompt=prompt)

Relevant Logs/Tracbacks
File "…/main.py", line 411, in …
    output = llm.complete(prompt=prompt)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "…/.venv/lib/python3.12/site-packages/llama_index/core/llms/callbacks.py", line 305, in wrapped_llm_predict
    prompt = kwargs.get("prompt", default=args[0])
                                          ~~~~^^^
IndexError: tuple index out of range

Yea it's technically not supported/advised. It might not be mentioned in the docs, but also, I don't think there's any example that uses it as a kwarg either 😅


Get developement Setup in Gitpod

Description
Set up the project in gitpod.

@Harshil-Jani can I work on this ?

@bharatkashyap Can i work on this?

Sure
Sent from my iPhone
On 04-Jun-2022, at 9:50 AM, Ratika Swami @.***> wrote:

@bharatkashyaphttps://github.com/bharatkashyap Can i work on this?
—
Reply to this email directly, view it on GitHubhttps://github.com/Samagra-Development/x-admin/issues/52#issuecomment-1146561332, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEVFB6F54LN7VQDQGRLBZP3VNMDD5ANCNFSM5XZJYDUQ.
You are receiving this because you were mentioned.Message ID: @.***>

please assign me


Assembly version is <IP_ADDRESS> for release 8.0.2

Hi, I went to upgrade MediatR today in my application and got assembly version errors.  It appears the 8.0.2 release was published with assembly version(s) <IP_ADDRESS>, while the 8.0.1 release had assembly version(s) <IP_ADDRESS>.

Oof, I'll double-check

Ah, I switched to a different versioning library, which now follows the MS guidance around assembly versions:
https://docs.microsoft.com/dotnet/standard/library-guidance/versioning#version-numbers
What error are you getting now?

Does this mean MediatR will now be following this guidance, from that link?
CONSIDER only including a major version in the AssemblyVersion.
My error was due to a dependency graph: App (MediatR 8.0.2, assembly <IP_ADDRESS>) -> app class library (MediatR 8.0.1, assembly <IP_ADDRESS>).
Since the class library had MediatR 8.0.1 installed, upgrading the app to MediatR 8.0.2 resulted in the assembly version errors.
If <IP_ADDRESS> is going to be the go-forward assembly version for 8.x.x releases, that's fine.  I will simply update all my class libraries to 8.0.2.  Thanks!

@jbogard Afaik this guidance is no longer valid because binding redirects don`t exist in .NET Core. (Deps.json FTW :-)
Would be interested what made you think this change is still worth it? For the existing NetFX Consumers?

What change? I just added MinVer, the assembly version was unintentional.

What change? I just added MinVer, the assembly version was unintentional.

The assembly version change.  (keeping the major version number of the AssemblyVersion and the NuGet package version in sync.)

What change? I just added MinVer, the assembly version was unintentional.

The assembly version change.  (Including only including a major version in the AssemblyVersion.)

Right that was just an accident with moving to MinVer from manual versioning


Resource generated in postprocessor is not included in the manifest file

I am generating a webp image in my post processor in a following way:
app.assets.register_mime_type 'image/png', '.png'
app.assets.register_postprocessor 'image/png', :png_webp do |context, data|
     # ... generate webp file
end

Unfortunately this file is not being added to manifest, so next time I deploy my app with Capistrano, its being wiped out.
How can I then add this new file to the manifest?

If this is still an active issue can you close this one and re-open it at http://github.com/rails/sprockets. Active development has moved to that repo.
If you've got a bug with sprockets 3 please make sure you've tried the latest 3.3.3. If you can confirm this is still an active issue, the fastest way to get it fixed is to create a small example app that reproduces the failure and open an issue in the new repo http://github.com/rails/sprockets.

This issue was moved to rails/sprockets#175


Contributions welcome :)?

Would rigorous methods for diffraction grating simulation, or thin planar materials be welcomed? Or more optical material properties (permitivities, etc)? Would you all prefer 2-D optical simulation methods reside elsewhere? How about Jones calculus or Stokes matrices?

Hi Casey :)
We're still at early stages with this package so we're mostly focusing on tools which could help our in-house teams for now. But we would like to work towards a more generic product in the long run, so anything that takes us in this direction is of interest!
Regarding contributions, I'm pretty new here so I'll leave that to @BrianGun.

I have a few semi large, not completely refined chunks of code hanging around on my hard drive somewhere, been looking for places to give it a useful home. Would like to add this is very nice work, and after speaking with some people could become an integral part of the julia CEM ecosystem!

Casey,
Thank you for the kind words. All of the features you mention would be interesting and useful to add. That's why we open sourced the project, so it could grow into a broadly useful optical simulation/optimization package.
We're fairly new to Julia. This may be a dumb question but what is the CEM ecosystem?
Could the rigorous diffraction grating simulation be massaged to conform to our OpticalInterface abstract type (defined in OpticalInterface.jl)? If the answer is yes then integration should be easy, otherwise we'll have to work with you to figure out what changes might be required.
Jones calculus or Stokes matrices might take more work since this would require a change to the OpticalRay type (defined in OpticalRay.jl) to carry polarization information along with the ray, and to the interface that goes along with the abstract OpticalInterface type to add required or optional functions that define how surfaces affect light polarization.
If you take a stab at defining the necessary new types and functions needed for polarization that would help us understand how big a job it might be.
We've wanted to add thin film simulation for a long time so we could more accurately model anti-reflection coatings and the like. Ideally we'd extend OpticalInterface to allow stacking an arbitrary number of interfaces. Then, for example, you could easily create a partially reflective metallic coating on top of a fresnel interface (this is something we currently model in an ad hoc way), without having to define a new class for every possible combination of interfaces.
This would take some thought to get right. I don't pretend to be an expert in modeling stacks of interfaces so that might make the going a bit slow. But it's been on my list of things to learn.
As for 2D simulation methods it's not entirely clear what you are asking for. Some of the surface types (Bezier and NURBS are examples) are parameterized by dimension so you can easily create 2D instead of 3D surfaces. Is this what you mean or are you referring to something else? Could you give an example of the type of optical system this would be used for?

Really exciting to hear your interested in contributing @caseykneale!
Regarding 'diffraction grating simulation, or thin planar materials', I wrote some very basic and certainly not rigorous code for thin diffraction gratings, but from what I remember efficiency for each order had to be defined by the user. I also had some code implementing Kogelnik for planar HOEs where efficiency was assuming some thickness but the HOE was assumed to be geometrically thin because of our OpticalInterface abstraction that Brian mentioned above. There is certainly some complexity in introducing simulation of these types of components, but it isn't impossible. PS I'm pretty sure there were errors in the Kogelnik code, or at least it didn't handle any/many edge cases correctly... visual results looked plausible though
There is also added complexity because we (so far) don't support ray splitting or true per-ray energy, so energy accumulation on any detector converges on the correct solution through monte-carlo integration of individual rays with uniform energy. This can be a real pain when trying to deal with diffraction efficiency but again, not impossible!

Julia is pretty awesome for this kind of work as I'm sure you're all realizing :D. "Julia CEM" = "Julia Computational ElectroMagnetics" :).
Never heard of Kogelnik, I have the Chandezon method(an easy-impl. is here: https://www.osapublishing.org/ao/abstract.cfm?uri=ao-38-2-304) 1-D coded up and also accepting multilayer media in p/s polarization. Getting the conical mount and supporting 2D gratings would be nice, but the code I had for that took a long time to square away and is not owned by me anymore - so I'd have to do it again. The Chandezon method is quite nice for performance, especially on comparison to things like RCWA, FEM, for continuous surface geometries. The diffraction and transmission efficiencies, in my experience, tend to be <1% of experimental error for simple geometries.
Think I also have the Fresnel equations (forget the name of the author who made them computationally pliable - maybe Azzam - it's been years forgive me) for planar optically thin and thick materials. Pretty sure I have a sneaky way to handle very very thick, thin, and many material layers as well.
I used to do work on simulations of thin films for surface plasmon resonance sensor development/optimization. That's why I have piles of this code around.
Depending on if you want near/far field simulations I can likely recommend good test cases for gratings.
As for representing polarization - it's tricky. I don't know if anyone has a good way of doing that beyond field equations. The Jones/Mueller matrices are a little niche but they can be broadened out to handle other systems.  At one point I was eyeing up adding polarization to local plane interface approximation (LPIA) for a system somewhat similar in spirit to what you all are working on. Just ran out of time. Well - I can do a code dump at some point soon and you all can decide if any of it meshes with your interests or not.


One-Click Installation bad link in documentation

See https://nixos.org/nix/manual/#sec-one-click
If you click on http://hydra.nixos.org/jobset/nixpkgs/trunk/channel/latest it shows:

Does One-Click Installation still work? And what is the valid link for it?

One click installations are an all-but-dead feature of Nix.

@grahamc Should they be removed from the documentation then? I read about them from Nix Pills:
https://nixos.org/nixos/nix-pills/automatic-runtime-dependencies.html#idm140737316135584

Indeed! Let's leave this ticket open to help cover that.

I think this is still important. I just read about this in Nix Pills as well and wanted to learn more. It sounded like an interesting alternative to flatpak/appimage/snap. If this feature has been dead for over two years, it should be at least removed from Nix Pills.

@razvan-flavius-panda I think you can close this issue. The stable manual does not mention one-click installation anymore.

This was fixed in Nix manual by https://github.com/NixOS/nix/commit/15c035c13f3c452ffef3960e97bd0e9b38d98ec2 but we still need to remove it from nix-pills: https://github.com/NixOS/nix-pills/pull/184


Add a Gitter chat badge to README.md

abntex/limarka now has a Chat Room on Gitter
@edusantana has just created a chat room. You can visit it here: https://gitter.im/abntex/limarka.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Obrigado pela contribuição, pegue seu código e utilizei de outra forma.


Create all_operations_doublyLinkedList

Added code for
0. Creation

Insertion at beginning
Insertion at end
Deletion from beginning
Deletion from end
Insert anywhere
Delete anywhere
Searching an element
Printing the linked list

Please star this repository to show your support, in the meantime I am reviewing your code.

Excellent work @TaniaMalhotra Thanks a lot for making this PR.


Linkify punycode-encodes em-dash

Hi! Thanks for this library -- I use it in my new mailing list software to detect links in emails. Someone brought what appears to be a bug to my attention: https://lists.flounder.online/crabmail/threads/1beaffd2384b.html
Here's my code:
https://git.alexwennerberg.com/crabmail/file/src/utils.rs.html#l22
I think that this could unambiguously be parsed, but I'm not 100% sure. What do you think?

Someone brought what appears to be a bug to my attention: https://lists.flounder.online/crabmail/threads/1beaffd2384b.html

Hmm that link doesn't load for me, could you provide a copy here?

Ah, sorry -- I shuffled things around a bit on my site. Here's the fixed link:
<EMAIL_ADDRESS>

I see. That's an interesting case, because — can currently be part of an URL, e.g. like this:
https://www.example.com/—

In that case, the whole text including em-dash would get linked.
Also note that GitHub behaves the same way here:
https://www.example.com—
https://www.example.com/—
We could fix the case where it's part of the domain, see also #29 which has some discussion around that. But what would you expect with the case where it's part of the path?

I think that if it's part of the path it should be treated as such. I guess this is a broader question, whether this library should reject invalid TLDs? like:
<EMAIL_ADDRESS>I think that the tradeoffs that you've made with the library as written are reasonable though

I've reworked domain parsing in 0.9.0 (see https://github.com/robinst/linkify/blob/main/CHANGELOG.md#090---2022-07-11), but I haven't addressed this yet.
I think we could now do this by rejecting TLDs that contain non-alphanumeric Unicode characters. Note that there are TLDs that contain non-ASCII characters, see examples here (but they would be alphanumeric): https://en.wikipedia.org/wiki/Internationalized_country_code_top-level_domain


WIP: testing review pipeline

Testing review pipeline

Codecov Report

Merging #39 (b5e6901) into main (a336eed) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #39   +/-   ##
=======================================
  Coverage   96.20%   96.20%
=======================================
  Files          24       24
  Lines         474      474
=======================================
  Hits          456      456
  Misses         18       18

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 a336eed...b5e6901. Read the comment docs.

I guess so, the helm secret naming problem might re-appear, but let's follow the situation 👍


The React.cloneElement docs are incorrect or very misleading

The React.cloneElement docs state:

key and ref from the original element will be preserved.

This statement makes it seem like any key or ref passed in the new props will be ignored.
However this is clearly not the case, as can be seen in the source code:
export function cloneElement(element, config, children) {

  ...

  if (hasValidRef(config)) {
    // Silently steal the ref from the parent.
    ref = config.ref;
    owner = ReactCurrentOwner.current;
  }
  if (hasValidKey(config)) {
    key = '' + config.key;
  }

  ...

  return ReactElement(element.type, key, ref, self, source, owner, props);
}

Looks like there is an open PR that addresses exactly this issue: #1394


Fugu14

Dude, it'd be so sick if you could help me get this to work in Fugu14 to achieve a proper untether!
I have absolute no clue what I'm doing, this is what I've been able to botch together so far: https://github.com/SmartBoy84/Weazol
Trust cache injection works sometimes for some utilities but doesn't for others, daemon launching is unreliable and device will crash randomly

You can send me a dm at evln#0001, or talk on the r/Jailbreak discord. I'm saying that if you adapt the current Fugu15 basebinaries to work with the kernel read/write method of iOS 14, you can get a fully working jailbreak. The code should be reusable.


update indirect dependency github.com/hashicorp/vault to v1.13.7

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Steps to reproduce

Does this PR introduce a user-facing change?

Does this PR require documentation?

closes https://github.com/replicatedhq/kURL/pull/4824


Not enough stars

Can I trust this project? It has very few stars

Yes, it has few stars but many of these stargazers are from all around the world with different backgrounds: https://github.com/dannyyu92/barebones/stargazers
Remember @kingsleyliao, quality of stars of quantity!


Add Orally to ecosystem showcase

Add Orally to the ecosystem showcase with a description, links, logo, and picture.

Hi @verkhohliad can you please accept the CLA? Thanks a bunch!

This branch is out-of-date with the base branch
Can you please update the brach? thank you. @verkhohliad

This branch is out-of-date with the base branch

Can you please update the brach? thank you. @verkhohliad

Done


[Federation] Update the release location for kubefed

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
For 1.10 Features: set Milestone to 1.10 and Base Branch to release-1.10
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
NOTE: After opening the PR, please un-check and re-check the "Allow edits from maintainers" box so that maintainers can work on your patch and speed up the review process. This is a temporary workaround to address a known issue with GitHub.>
Please delete this note before submitting the pull request.

This change is

/assign @csbell @quinton-hoole
👋 could use a technical accuracy check on this please. If it's good, would you mind adding an /lgtm comment onto this PR?

/assign

/approve

@csbell, @quinton-hoole, can you please take a look at this.
@shashidharatd can also please comment on the technical accuracy of this PR.

@csbell thanks for the review. Have updated as per your comments. PTAL.


support for .flac files

Hi, I just encountered this error, and I'm not really sure what it means,
Sample rate of the given file is not supported Format: SampleRate $863379525, Channels $19777, BitsPerSample $50, Length $3384855. Supported sample rates 5512,8000,11025,16000,22050,44100,48000. Submit a github request if you need a different sample rate to be supported.
Initially, I'm using a flac file but later converted the flac file to mp3 format, then I got the error above.
I tried to convert the mp3 file to an mp3 file that has a sample rate of 48000 and also tried it with 44100 but I still get the same error,
Not sure what I'm doing wrong, just want to know your thoughts on the right approach to convert the files properly.
Thanks!
Jude Alquiza.

Default SoundFingerprintingAudioService supports only wave file at the input. If you would like to process other formats, consider using below extensions:

SoundFingerprinting.Audio.NAudio - replacement for default SoundFingerprintingAudioService audio service. Provides support for .mp3 audio processing. Runs only on Windows as it uses NAudio framework for underlying decoding and resampling.
SoundFingerprinting.Audio.Bass - Bass.Net audio library integration, comes as a replacement for default service. Works faster than the default or NAudio, more accurate resampling, supports multiple audio formats (.wav, .ogg, .mp3, .flac). Bass is free for non-comercial use. Recommended for enterprise users.

Hi Thanks :) I'm trying to look for documentation on what nuget packages to install, I know SoundFingerprinting.Audio.Bass is one which I can get from nuget but it seems that there's more, I'm also using .NET Core 3.x, not sure if there is a compatible version of SoundFingerprinting.Audio.Bass with .NET Core 3.x, thanks in advance :)


Unexpected jumps with clickToFocus and entering commands

Environment
Windows 7, Desktop, Chrome
Using a React Redux boilerplate
Expected Behavior
Clicking anywhere in the terminal will put focus into terminal, ready to type command.
Typing in commands will not cause the console to move.
Actual Behavior
It puts the focus into the terminal and scrolls down to it. The additional scroll behavior is not desirable.
Then, typing in commands causes the console to scroll down.

Load page.
Click console. (Observe scrolling down here)
Type in commands. After entering each command, it will keep scrolling down the whole browser.

When I played around with the code, I think I found a fix. If I have time, I'll look at it some more and make a pull request.
I'm thinking maybe a separate attribute for part of it. autoscroll?

Thanks for the update, I would love to see a PR for this issue.

Found this fix, there's two ways to implement...
One is to add false into scrollIntoView(), which causes it to scroll to the bottom of the terminal instead. This keeps the stuff above the terminal visible and the bottom of the terminal at the very bottom.
https://github.com/rohanchandra/react-terminal-component/blob/92eede895b218580d95637b15be082f07d995e42/src/input/CommandInput.js#L13
Alternatively, there can be a scrollToTop prop that goes to that function with default as false, though I am not sure if there is a situation where it is useful to keep it as scroll to top.
Completely removing the scroll does not exactly work because of the last line being partially obscured. There's probably a third way to fix it, but first way seems sufficient to me.
Do you want a pull request with adding false or a whole new prop? I can do either.

@alexxgathp Thanks for finding the cause of the bug. Let's just pass in false for now (if there's an actual use-case for the prop we can always add it later).

https://github.com/rohanchandra/react-terminal-component/pull/12

Separated out the other thing
https://github.com/rohanchandra/react-terminal-component/pull/15

Thanks for the updated PR, I've merged your changes from https://github.com/rohanchandra/react-terminal-component/pull/15 in.


Example to calculate address balance

Hello,
I am working on a project that has many private keys that have balances in them.  I do not want to have to go out to a public API to query for security concerns.
I see there is a way to get the unspent amounts for an address in the example. However, I am not seeing a way to connect the private key to it's address.  I believe this is what I would have to do to determine how much BTC the private key is linked to.
Is the data structure in indexd able to perform this type of query against the blockchain?
Thanks in advance!

@KryptoNova and others who might be interested: bitcoinjs/regtest-server implements most of this functionality and may serve as your example: https://github.com/bitcoinjs/regtest-server/blob/b699cfad29e21272c7c644d9d66c5ad089d56be8/routes/1.js#L107-L112
  router.get('/a/:address/unspents', addressWare, (req, res) => {
    let { scId } = req.params
    indexd().utxosByScriptRange({
      scId, heightRange: [0, 0xffffffff], mempool: true
    }, DBLIMIT, res.easy)
  })

The result is an array of UTXO objects; you may sum the value field of each to find the unspent balance of the address in satoshis.
Note the addressWare middleware function for converting the address to a script ID.


Tutorials won't embed in websites

Abhijith mentioned that only games have the option of being embedded right now, but we have a partner working with the Atlanta Hawks who are trying to embed their tutorial in the Hawks website so they can run a contest.
How soon can we get embeds working for tutorials?
(Their attempt at embedding Chase the Pizza)
https://atlhawksdigital.com/projects/__current/dunk2.html

Needs context. Why does the tutorial needs to be embedded? Can we have a workaround of launching in makecode?

Adding the information on existing embed scenarios we support.
Read Only scenario for shared game:

Simulator: Simulator of any shared game can be embedded in the html.
Code:  Blocks code of any shared game can be embeded in the html. This code can't be modified a.k.a there is no toolbox.
Simulator + Code:  Or known as editor model, lets you embed triple toggle mode for a shared game. This includes simulator, blocks & javacript. Blocks & simulator is ready only.

Widget scenario: In this scenario we allow embedding the entire editor as widget. See the API here: https://github.com/microsoft/pxt/blob/master/pxteditor/editorcontroller.ts#L32  However restriction is the parent frame owns all the data and MakeCode behaves as a widget which shows simulator, toolbox & blocks or javascript. No data is sent to backend as parent frame is responsible for handling all the code. Microbit classroom uses this model.

This particular partner has now decided to link off to our site due to the quick timeframe, but in general, people using tutorials as promotional tools want to bring people to their site, rather than ours.  They want to have the added time on their webpage and avoid passing customers off to domains where they need to give the warning "You are now leaving our site..." etc.
I'm surprised we haven't hit this requirement yet, but I know for sure that at least one of our future partners plans to require that the learning takes place within the "safety" of their domain.

Here's the recap of what we talked about today...
New Work/Capabilities to extend Widget scenario:
Potentially allow them to show their own tutorials
Button to bring them back to our main website - saving, sharing projects
"Powered by MakeCode" branding