text:
Lights are not available in HA

I've done the setup for the Awox Mesh integration, and I could log in to the Awox account, my Lights are added. I have a mesh created by the Smart Plug, and 2 of my lights are in bluetooth range, but I can not control them.
HA is running on Raspberry Pi 4.
Log1:
Logger: custom_components.awox.awox_mesh
Source: custom_components/awox/awox_mesh.py:119
Integration: AwoX MESH control (documentation, issues)
First occurred: 10:22:59 (8 occurrences)
Last logged: 10:42:49
Fetching RSSI failed -
Log2:
Logger: custom_components.awox.bluetoothctl
Source: custom_components/awox/bluetoothctl.py:37
Integration: AwoX MESH control (documentation, issues)
First occurred: 10:21:33 (9 occurrences)
Last logged: 10:44:10
Failed to start scan: Timeout exceeded. <pexpect.pty_spawn.spawn object at 0x7f95aa3550> command: /usr/bin/bluetoothctl args: [b'/usr/bin/bluetoothctl'] buffer (last 100 chars): ' . \r\n[\x01\x1b[0;93m\x02CHG\x01\x1b[0m\x02] Device 26:17:72:CF:32:8B RSSI: -42\r\n' before (last 100 chars): ' . \r\n[\x01\x1b[0;93m\x02CHG\x01\x1b[0m\x02] Device 26:17:72:CF:32:8B RSSI: -42\r\n' after: <class 'pexpect.exceptions.TIMEOUT'> match: None match_index: None exitstatus: None flag_eof: False pid: 343 child_fd: 29 closed: False timeout: 30 delimiter: <class 'pexpect.exceptions.EOF'> logfile: None logfile_read: None logfile_send: None maxread: 2000 ignorecase: False searchwindowsize: None delaybeforesend: 0.05 delayafterclose: 0.1 delayafterterminate: 0.1 searcher: searcher_re: 0: re.compile('bluetooth') 1: EOF
Failed to start scan: Timeout exceeded. <pexpect.pty_spawn.spawn object at 0x7f9617ff40> command: /usr/bin/bluetoothctl args: [b'/usr/bin/bluetoothctl'] buffer (last 100 chars): '00 00 00 00 ................\r\n 00 . \r\n' before (last 100 chars): '00 00 00 00 ................\r\n 00 . \r\n' after: <class 'pexpect.exceptions.TIMEOUT'> match: None match_index: None exitstatus: None flag_eof: False pid: 372 child_fd: 27 closed: False timeout: 30 delimiter: <class 'pexpect.exceptions.EOF'> logfile: None logfile_read: None logfile_send: None maxread: 2000 ignorecase: False searchwindowsize: None delaybeforesend: 0.05 delayafterclose: 0.1 delayafterterminate: 0.1 searcher: searcher_re: 0: re.compile('bluetooth') 1: EOF
Failed to start scan: Timeout exceeded. <pexpect.pty_spawn.spawn object at 0x7f95a3aeb0> command: /usr/bin/bluetoothctl args: [b'/usr/bin/bluetoothctl'] buffer (last 100 chars): '08:B4 ManufacturerData Value:\r\n 53 4d 4f aa 58 SMO.X \r\n' before (last 100 chars): '08:B4 ManufacturerData Value:\r\n 53 4d 4f aa 58 SMO.X \r\n' after: <class 'pexpect.exceptions.TIMEOUT'> match: None match_index: None exitstatus: None flag_eof: False pid: 401 child_fd: 29 closed: False timeout: 30 delimiter: <class 'pexpect.exceptions.EOF'> logfile: None logfile_read: None logfile_send: None maxread: 2000 ignorecase: False searchwindowsize: None delaybeforesend: 0.05 delayafterclose: 0.1 delayafterterminate: 0.1 searcher: searcher_re: 0: re.compile('bluetooth') 1: EOF
Failed to start scan: Timeout exceeded. <pexpect.pty_spawn.spawn object at 0x7f95a00a00> command: /usr/bin/bluetoothctl args: [b'/usr/bin/bluetoothctl'] buffer (last 100 chars): ' . \r\n[\x01\x1b[0;93m\x02CHG\x01\x1b[0m\x02] Device 6D:80:75:E9:29:74 RSSI: -77\r\n' before (last 100 chars): ' . \r\n[\x01\x1b[0;93m\x02CHG\x01\x1b[0m\x02] Device 6D:80:75:E9:29:74 RSSI: -77\r\n' after: <class 'pexpect.exceptions.TIMEOUT'> match: None match_index: None exitstatus: None flag_eof: False pid: 430 child_fd: 48 closed: False timeout: 30 delimiter: <class 'pexpect.exceptions.EOF'> logfile: None logfile_read: None logfile_send: None maxread: 2000 ignorecase: False searchwindowsize: None delaybeforesend: 0.05 delayafterclose: 0.1 delayafterterminate: 0.1 searcher: searcher_re: 0: re.compile('bluetooth') 1: EOF
Failed to start scan: Timeout exceeded. <pexpect.pty_spawn.spawn object at 0x7f9afc2c70> command: /usr/bin/bluetoothctl args: [b'/usr/bin/bluetoothctl'] buffer (last 100 chars): 'HG\x01\x1b[0m\x02] Device 6D:80:75:E9:29:74 RSSI: -91\r\n[\x01\x1b[0;92m\x02NEW\x01\x1b[0m\x02] Device 02:ED:A9:02:08:B4 E3.5BT\r\n' before (last 100 chars): 'HG\x01\x1b[0m\x02] Device 6D:80:75:E9:29:74 RSSI: -91\r\n[\x01\x1b[0;92m\x02NEW\x01\x1b[0m\x02] Device 02:ED:A9:02:08:B4 E3.5BT\r\n' after: <class 'pexpect.exceptions.TIMEOUT'> match: None match_index: None exitstatus: None flag_eof: False pid: 459 child_fd: 29 closed: False timeout: 30 delimiter: <class 'pexpect.exceptions.EOF'> logfile: None logfile_read: None logfile_send: None maxread: 2000 ignorecase: False searchwindowsize: None delaybeforesend: 0.05 delayafterclose: 0.1 delayafterterminate: 0.1 searcher: searcher_re: 0: re.compile('bluetooth') 1: EOF

can you enable debug logging and post the logs here? https://github.com/fsaris/home-assistant-awox#troubleshooting

Hello i instaled the integration trew the Hacs extension but at every startup i get tihs masage from the Awox integration did any one of you now what i have to do i´m completly new to homeassistant :

Thank you

The warning is just a notice.
The error is fixed with latest version (just released it).

OK but I can Not control the lights

Can you enable debug logging and post the logs here?

Yes i can try but i don't now how to do this or where i can edit the yaml file

@mindbuilder18 see https://www.home-assistant.io/docs/configuration/#editing-configurationyaml
You can also go to Developer tools -> Services and send
service: logger.set_level
data:
  custom_components.awox: debug

That will temporary enable logging until next restart of HA

I get an alart if i try to actavate the logs "I hope you can read the report my mother language is german and because of this my Home Asisstant system is set to german

or what have I to do now ?

i can not see any directory witch is labeld debug ??

I get an alart if i try to actavate the logs "I hope you can read the report my mother language is german and because of this my Home Asisstant system is set to german

You could try to switch to UI mode. Select the log level service and paste custom_components.awox: debug as value

or what have I to do now ?

Open the configuration.yaml file. Add the lines from the readme regarding the debug config. Validate the configuration and restart HA

Like this right?

Logger: homeassistant.util.package
Source: util/package.py:98
First occurred: 20:21:49 (3 occurrences)
Last logged: 20:22:13
Unable to install package bluepy>=1.3.0: error: subprocess-exited-with-error × python setup.py bdist_wheel did not run successfully. │ exit code: 1 ╰─> [8 lines of output] /usr/local/lib/python3.10/site-packages/setuptools/dist.py:772: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead warnings.warn( running bdist_wheel running build running build_py Working dir is /tmp/pip-install-hsrc2jio/bluepy_5b51b2535b6a413dba5e030e122e1775 execute make -C ./bluepy clean error: [Errno 2] No such file or directory: 'make' [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for bluepy error: subprocess-exited-with-error × Running setup.py install for bluepy did not run successfully. │ exit code: 1 ╰─> [10 lines of output] /usr/local/lib/python3.10/site-packages/setuptools/dist.py:772: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead warnings.warn( running install /usr/local/lib/python3.10/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools. warnings.warn( running build running build_py Working dir is /tmp/pip-install-hsrc2jio/bluepy_5b51b2535b6a413dba5e030e122e1775 execute make -C ./bluepy clean error: [Errno 2] No such file or directory: 'make' [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: legacy-install-failure × Encountered error while trying to install package. ╰─> bluepy note: This is an issue with the package mentioned above, not pip. hint: See above for output from the failure.
Unable to install package bluepy>=1.3.0: error: subprocess-exited-with-error × python setup.py bdist_wheel did not run successfully. │ exit code: 1 ╰─> [8 lines of output] /usr/local/lib/python3.10/site-packages/setuptools/dist.py:772: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead warnings.warn( running bdist_wheel running build running build_py Working dir is /tmp/pip-install-f4bhg5sf/bluepy_dd6ea869a7cc4742be37a693da653817 execute make -C ./bluepy clean error: [Errno 2] No such file or directory: 'make' [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for bluepy error: subprocess-exited-with-error × Running setup.py install for bluepy did not run successfully. │ exit code: 1 ╰─> [10 lines of output] /usr/local/lib/python3.10/site-packages/setuptools/dist.py:772: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead warnings.warn( running install /usr/local/lib/python3.10/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools. warnings.warn( running build running build_py Working dir is /tmp/pip-install-f4bhg5sf/bluepy_dd6ea869a7cc4742be37a693da653817 execute make -C ./bluepy clean error: [Errno 2] No such file or directory: 'make' [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: legacy-install-failure × Encountered error while trying to install package. ╰─> bluepy note: This is an issue with the package mentioned above, not pip. hint: See above for output from the failure.
Unable to install package bluepy>=1.3.0: error: subprocess-exited-with-error × python setup.py bdist_wheel did not run successfully. │ exit code: 1 ╰─> [8 lines of output] /usr/local/lib/python3.10/site-packages/setuptools/dist.py:772: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead warnings.warn( running bdist_wheel running build running build_py Working dir is /tmp/pip-install-bq53c4ye/bluepy_a29faf503dce403dbda07cbdd654e5c1 execute make -C ./bluepy clean error: [Errno 2] No such file or directory: 'make' [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for bluepy error: subprocess-exited-with-error × Running setup.py install for bluepy did not run successfully. │ exit code: 1 ╰─> [10 lines of output] /usr/local/lib/python3.10/site-packages/setuptools/dist.py:772: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead warnings.warn( running install /usr/local/lib/python3.10/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools. warnings.warn( running build running build_py Working dir is /tmp/pip-install-bq53c4ye/bluepy_a29faf503dce403dbda07cbdd654e5c1 execute make -C ./bluepy clean error: [Errno 2] No such file or directory: 'make' [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: legacy-install-failure × Encountered error while trying to install package. ╰─> bluepy note: This is an issue with the package mentioned above, not pip. hint: See above for output from the failure.

Logger: homeassistant.setup
Source: setup.py:184
First occurred: 20:22:13 (1 occurrences)
Last logged: 20:22:13
Setup failed for custom integration awox: Requirements for awox not found: ['bluepy>=1.3.0'].

@mindbuilder18 you need to use the latest version of this integration https://github.com/fsaris/home-assistant-awox/releases/tag/0.1.3

OK i will try it out later thank you

It loks like its working now but i think my LEDs are not in range. Do you know a way to extend the Bluotooth signal

@mindbuilder18 use a Bluetooth USB dongle with some longer USB cable. The onboard devices have not great reach

I ouse a USB dongle but the Server ist in a difren rom

authors: fsaris gerendasp mindbuilder18

repo: fsaris/home-assistant-awox


text:
Add missing assemblies to ZIP package

Forge crashed on me because ICSharpCode.SharpZipLib.dll was missing. I also noticed that FParsecs assemblies aren't included, too.

Thanks

source: gharchive/pull-request

authors: Krzysztof-Cieslak inosik

repo: fsharp-editing/Forge

license: unlicense

license_type: permissive

license_source: bigquery


text:
IView vs IView<'a> is annoying

It's often useful to create functions that accept an IView as a child. This allows developers to use the same 'outer' view like a box or overlay, with different content inside. IView includes two definitions, a non-generic IView and a generic IView<'a>.
Because children (and similar properties) accept overloads, it's impossible to do this without some type annotations and casting:
// Reusable overlay function
let overlay child =
    Border.create [
        Border.classes [ "rw-modal" ]
        Border.child child // Error: A unique overload for method 'child could not be determined based on type information prior to this program point. A type annotation may be needed.
    ]

This causes multiple problems. First, it's inconvenient to provide an explicit type annotation for such a simple function. Second, annotating one casting of IView prevents using the function for the other type. The only way around this presently is to invoke Helpers.generalize for almost every view function in the application, or to write adapter functions. Either way, this adds a lot of boilerplate to the DSL.
In my usage of FuncUI, I have no reason to inspect the content of a view value. If I want to compose changes to a view, I do list operations on the IAttr list before passing the result to create.
After that, the framework uses the view's innards to diff and patch. Everything inside of the IView value is an implementation detail of FuncUI. The framework should expose a single, opaque View type to the developer.

What's the difference between IView and IView<unit>?

What's the difference between IView and IView<unit>?

The generic version is used to make the DSL type safe.
The non generic version is used internally.
This should be resolved by targeting .NET 6 I think.

source: gharchive/issue

authors: B-Reif JaggerJo uxsoft

license: MIT

license_source: github-api


text:
Recompile dependant files on watch compilation

See this comment.

Hi @ritcoder! Can you please give it a try to v0.3.17 and confirm if it works for you? This version should compile dependant files on watch compilation. Cheers!

Been using it for a while. only the updated files are recompiled for the most part. When compiling dependents, are they also listed in the console. If yes, then no dependent files were compiled. The only error I had was the one below. It worked after restarting.
Compiled NewCasePanel.fs at 8:39:16 PM
Compiled NewCasePanel.fs at 8:52:49 PM
Compiled Controllers.fs at 11:50:37 PM
path.js:7
    throw new TypeError('Path must be a string. Received ' + inspect(path));
    ^

TypeError: Path must be a string. Received null
    at assertPath (path.js:7:11)
    at Object.extname (path.js:887:5)
    at FSWatcher.<anonymous> (C:\Users\Richard\AppData\Roaming\npm\node_modules\fable-compiler\index.js:216:24)
    at emitTwo (events.js:106:13)
    at FSWatcher.emit (events.js:191:7)
    at FSEvent.FSWatcher._handle.onchange (fs.js:1406:12)

Yes, dependent files should be also listed in the console. So it's not working for you? Are you using fable-compiler@0.3.17? It's working for me when I'm compiling the React sample in the repo (for example, if I modify components.fs, both components.fs and client.fs are recompiled). If you can upload your project of part of it it'd be very helpful to try to reproduce your problem on my machine. Are you on Windows, by the way. Seems Node's file watcher may work differently on Windows.

Interesting. It was still 0.3.14. Did npm install instead of 'npm install -g'. Will do well to check versions on future reports. Updated to 0.3.17 and updating one file (SemanticUi.Extras.React.fs) causes some two dependents (NewCasePanel.fs and CaseContactsPanel.fs) to recompile so it is working fine.
One thing though is when it identifies changes and is about to compile, can it display something (like Start compilation...)? Reason is that compilation mostly takes its sweet time to start and you are not sure of what it is doing until you see the message compiled xyz at 0:00:00 PM.

I'm glad to hear it works 😄 About your suggestion, it's a good point and it's not difficult at all to implement. I was always testing the watch compilation with small projects so I didn't notice the issue because compilation was really fast. Thanks for the tip! 👍

After using it for a while, it mostly works well. It does give way after some pressure. When the following are combined, it appears to get confused.

error in the files (especially multiple files)
adding new files to the project
reordering files
Saving of multiple files (e.g. editing multiple files and using save all)

Can't really point how to reproduce it but when I notice strange errors from the app, running fable in another terminal should get thing back to normal. After that further edits are correctly taken care of by the one watching.

authors: alfonsogarciacaro ritcoder

repo: fsprojects/Fable


text:
Bug : Wildcarded source file path in Project file for 'paket pack' symbols flag

Hello again,
While applying the 'paket pack' 'symbol' flag in our projects, I noticed that there was a bug when paket tried to pack sources files that were wildcarded in the Microsoft project file. Paket crashes with "Illegal characters in path." or "Could not find source file [...]".
e.g.
<Compile Include="GENERATED_CS\*.cs" />

or
<Compile Include="GENERATED_CS_LINKED\*.cs">
  <Link>translated\%(FileName).cs</Link>
</Compile>

Here is a repro example : https://github.com/franknarf8/paket-issue-repro/tree/92a01bed12d54b953f518b34979763fa7b14cb01
Thank you

/cc @pms1969

I'll take a look.

@franknarf8, do you know if this was always the case, or was this always a problem?

Well, that was using the new 'symbol' flag for the 'paket pack' command, so it is fairly recent. I just started using this flag so I unfortunately can't tell you if it once was working with wildcards in the <compile [...]> elements.
Prior to this new flag, to get the source files in the nuget package, we had to manually add them in the paket.template file.
e.g.
files
    ../**/*.cs

The wildcards worked then, but with the new flag all the source files are added correctly in the .nupkg except for the ones with wildcards.

OK. I know what to do and where, just need to formulate a plan for how.  I'm not a native f# speaker, but I'll get it done soon.

@franknarf8  should be fixed in 2.45.0.  can you give it a shot and let me know how it goes?

@pms1969 @forki I just tested and everything seems to works perfectly.
Thanks again @pms1969

Awesome

repo: fsprojects/Paket

license: mit


text:
SetPaketCommand takes half a second

Description
An empty dotnet core 3.1 web app project takes ~1 sec to build 2nd time (no changes). Half of this 1 sec is taken by SetPaketCommand, even when --no-restore flag is set. Should this target be executed at all in this case?
Repro steps

With dotnet core SDk 3.1, cd test-proj && dotnet new web.
Configure paket as a local dotnet tool, add dependencies and references files.
paket install, restore etc.
dotnet build .
dotnet build . --no-restore /clp:PerformanceSummary

The output has this:
Target Performance Summary:
        ...
        0 ms  Compile                                    1 calls
        0 ms  AfterResolveReferences                     1 calls
        0 ms  CoreBuild                                  1 calls
        0 ms  BeforeResGen                               1 calls
        ...
        0 ms  Build                                      1 calls
        ...
        3 ms  CoreCompile                                1 calls
        ...
       19 ms  PaketRestore                               1 calls
       36 ms  ResolveProjectReferences                   1 calls
       37 ms  GenerateBuildDependencyFile                1 calls
       38 ms  ProcessFrameworkReferences                 1 calls
       52 ms  FindReferenceAssembliesForReferences       1 calls
       53 ms  GenerateBuildRuntimeConfigurationFiles     1 calls
       55 ms  ResolveAssemblyReferences                  1 calls
       67 ms  ResolvePackageAssets                       1 calls
      461 ms  SetPaketCommand                            1 calls
...
Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:01.18

Expected behavior
SetPaketCommand should not take half the build time, preferably it should not be executed at all if --no-restore flag is used
Actual behavior
SetPaketCommand takes ~0.5 sec, which is ~50% of build time.
Known workarounds
N/A

Every idea of how to improve it would be appreciated
Alexandr Sugak notifications@github.com schrieb am Sa., 25. Apr. 2020,
22:05:

Description
An empty dotnet core 3.1 web app project takes ~1 sec to build 2nd time
(no changes). Half of this 1 sec is taken by SetPaketCommand, even when
--no-restore flag is set. Should this target be executed at all in this
case?
Repro steps

With dotnet core SDk 3.1, cd test-proj && dotnet new web.
Configure paket as a local dotnet tool, add dependencies and
references files.
paket install, restore etc.
dotnet build
dotnet build . --no-restore /clp:PerformanceSummary

The output has this:
Target Performance Summary:
...
0 ms  Compile                                    1 calls
0 ms  AfterResolveReferences                     1 calls
0 ms  CoreBuild                                  1 calls
0 ms  BeforeResGen                               1 calls
...
0 ms  Build                                      1 calls
...
3 ms  CoreCompile                                1 calls
...
19 ms  PaketRestore                               1 calls
36 ms  ResolveProjectReferences                   1 calls
37 ms  GenerateBuildDependencyFile                1 calls
38 ms  ProcessFrameworkReferences                 1 calls
52 ms  FindReferenceAssembliesForReferences       1 calls
53 ms  GenerateBuildRuntimeConfigurationFiles     1 calls
55 ms  ResolveAssemblyReferences                  1 calls
67 ms  ResolvePackageAssets                       1 calls
461 ms  SetPaketCommand                            1 calls
...
Build succeeded.
0 Warning(s)
0 Error(s)
Time Elapsed 00:00:01.18
Expected behavior
SetPaketCommand should not take half the build time, preferably it should
not be executed at all if --no-restore flag is used
Actual behavior
SetPaketCommand takes ~0.5 sec, which is ~50% of build time.
Known workarounds
N/A
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/3836, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAOANBEYP4WIICWENV5URTROM7CHANCNFSM4MQ4OCCA
.

I ended up adding RunPaket variable (true by default) to Paket.Restore.targets and modifying  Condition of corresponding targets to skip running it if RunPaket is false.
So now I can do dotnet build . --no-restore --no-dependencies /p:RunPaket=false and have build time < 1 sec.
Will Paket override the targets file at some point though?
My use case is that I want to do fswatch on .cs files and run build+test every time something changes. To make it work, the feedback time (time between a file change and a test result) must be small. This is why I am trying to squish as much time out of the build+test pipeline as possible. I don't need to do any package restores here.

Yes Paket is adjusting the targets file with every update of itself. So
please send a PR to the one here in the embedded folder. That would ensure
that we don't break you
Alexandr Sugak notifications@github.com schrieb am So., 26. Apr. 2020,
13:53:

I ended up adding RunPaket variable (true by default) to
Paket.Restore.targets and modifying Condition of corresponding targets to
skip running it if RunPaket is false.
So now I can do dotnet build . --no-restore --no-dependencies
/p:RunPaket=false and have build time < 1 sec.
Will Paket override the targets file at some point though?
My use case is that I want to do fswatch on .cs files and run build+test
every time something changes. To make it work, the feedback time (time
between a file change and a test result) must be small. This is why I am
trying to squish as much time out of the build+test pipeline as possible. I
don't need to do any package restores here.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/3836#issuecomment-619537248,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAOANH2YNQTJZES2BWTVE3ROQOCDANCNFSM4MQ4OCCA
.

With your repro steps SetPaketCommand only takes 1-3 ms on my machine. Can you run the build with the -bl parameter and check if this block is executed or not:
https://github.com/fsprojects/Paket/blob/375923784ec2799f2573f0786cb7a2905d5f7067/src/Paket.Core/embedded/Paket.Restore.targets#L76-L78
You can look at the binary log with the MSBuild Binary and Structured Log Viewer.

authors: AlexSugak forki inosik


text:
Paket creates corrupt package (zip)

With a very specific file (that I am not allowed to put here) Paket.pack creates nupkg that give crc error when unpacked. Replacing that file after packing manually with somethign like 7 zip fixes the archive.
Simplest case I have been able to reproduce is file type template with single file content.
Are there any way I can get debug data to help figuring out this without publishing stuff I am not allowed to make public?

I assume the only thing is to trust me and use email or something.
That said: maybe it's time to upgrade paket to newer .NET framework and use
the framework stuff to zip files.
On Mar 27, 2015 4:25 PM, "Vidar Løvbrekke Sømme" notifications@github.com
wrote:

With a very specific file (that I am not allowed to put here) Paket.pack
creates nupkg that give crc error when unpacked. Replacing that file after
packing manually with somethign like 7 zip fixes the archive.
Simplest case I have been able to reproduce is file type template with
single file content.
Are there any way I can get debug data to help figuring out this without
publishing stuff I am not allowed to make public?
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/729.

Sent you an e-mail with the simplest possible repro. (and now everyone can create wonder what the super-secret file is..)

IT IS A MYSTERY INDEED!
I got no mail.

I can reproduce this bug with latest Paket, but #732 seems to fix it.
At least I don't get the CRC error any more. But #732 still has the issue that the package explorer can't find the metadata and I don't know why.

should be fixed in 0.39 alpha

I can confirm that my original problem is now fixed

authors: Vidarls forki


text:
Support fallback logics

Support the full fallback logics with fully covered local, memory, S3 UFS tests

Finished: S3 fallback logics testing
TODO: change to local filesystem fallback so that it can be a long term pytest
TODO: fallback with Alluxio end-to-end testing, testing alluxio logics and metrics

@ChunxuTang @jja725 Added the fallback logics and fully tested the fallback without Alluxio logics via local/memory/S3 fallback

repo: fsspec/alluxiofs


text:
publish the point cloud of the lidar in its own frame

Hi there, could it be possible to publish the point cloud of the lidar in its own frame (i.e. lidar_link) not the base_link frame? If yes, could you instruct the steps to set it up, please? Thank you.

Apologies, I'm not sure I'm following the question.  You can set the "Parent Transform Id" to whatever you wish in the ZOROSPointCloud2Publisher  component.

repo: fsstudio-team/ZeroSimROSUnity


text:
Initiazation of PGD attack for l1 and l2 perturbation

In the function 'init_delta' of pgd_attack.py, the perturbation is initialized uniformly at the hypersphere of l1 or l2 ball, instead of uniformly lying in the l1 or l2 ball.
Is it designed on purpose? Cause in this case, the initialized perturbation will always lie on the boundary of the adversarial budget.

Yes that's on purpose. The way we initialise for l‐inf also gives a perturbation that lies (nearly) on the boundary of the eps‐ball if the input is high-dimensional.
We could consider other ways of sampling too. I don't expect this to make a big difference though.

I see, thank you for your reply.

authors: ftramer yljblues

repo: ftramer/MultiRobustness


text:
NAS-BNN: バイナリニューラルネットワークのためのニューラルアーキテクチャサーチ

タイトル: NAS-BNN: バイナリニューラルネットワークのためのニューラルアーキテクチャサーチ
リンク: https://arxiv.org/abs/2408.15484
概要:
2値ニューラルネットワーク（BNN）は、従来の完全精度ネットワークと比較して、推論効率と圧縮率が高いため、大きな注目を集めています。しかし、BNNの独自の特性により、強力な2値アーキテクチャの設計は困難であり、多くの場合、多大な労力を必要とします。有望な解決策は、ニューラルアーキテクチャ検索（NAS）を利用してBNNの設計を支援することですが、BNNの現在のNAS手法は比較的単純であり、検索されたモデルと手動で設計されたモデルの間には性能の差があります。
この差を埋めるために、NAS-BNNと呼ばれる、2値ニューラルネットワークのための新しいニューラルアーキテクチャ検索スキームを提案します。まず、BNNの独自の特性に基づいて検索空間を慎重に設計します。次に、スーパーネットのトレーニングを大幅に強化し、すべてのサブネットのパフォーマンスを向上させる3つのトレーニング戦略を紹介します。私たちが発見した2値モデルファミリは、2,000万から2億の幅広い演算（OP）において、以前のBNNよりも優れたパフォーマンスを発揮します。たとえば、わずか5,700万OPでImageNetで68.20％のトップ1精度を達成しました。さらに、オブジェクト検出タスクに対するこれらの検索されたBNNの転送可能性を検証し、検索されたBNNを使用した2値検出器は、MS COCOデータセットで3億7,000万OPで31.6％のmAPなど、最先端の結果を達成します。ソースコードとモデルはhttps://github.com/VDIGPKU/NAS-BNNで公開されます。

@yukihiko-fuyuki が以下のラベルを提案し、適用しました：

model-compression
neural-network-pruning
image-classification

以下の新しいラベルが作成され、適用されました：

neural-network-pruning

repo: fulfulggg/Information-gathering


text:
Rewrite App.js to use ES6 syntax

Fixes #15
Improved readability and style of App.js using ES6 syntax:
Used React class component syntax instead of createClass
Extracted callbacks as class methods instead of inline in JSX
Used Class Properties syntax to define callback methods and initial state
Used Array.filter to remove item instead of "double-slice" approach

Thanks for your patience @markerikson, I've been heads down for the past few weeks.
This is really great! Super appreciative. I'm going to update the other components in this repo to match this style / the concerns you mentioned here.

authors: acco markerikson

repo: fullstackreact/food-lookup-demo


text:
There is not an option to disable subcomponents deletion on Update command.

When file teacking feature has subcomponents to delete, by default Update command always deletes them. There are cases where it is not necessary to delete them and it would be useful an option to disable this default operation.
E.G.
enforce{
    filetracking.delete.subcomponents = 'none'
}

enforce{
    filetracking.delete.subcomponents = 'fields, fieldsets, validationrules'
}

This feature meets the criterion defined, but I think that  customize the subcomponents selectors a name's level

authors: MarceloEof naverus

repo: fundacionjala/enforce-gradle-plugin


text:
Implement GETDEL

Get the value of key and delete the key. This command is similar to GET, except for the fact that it also deletes the key on success (if and only if the key's value type is a string).
See example: https://redis.io/commands/getdel/

what will the difference be towards the DEL command?

Only real difference is the return type after the executed command. DEL returns the number of keys removed and GETDEL returns the actual value of the KEY that is removed.
Example DEL:
SET key1 "Hello"
redis answer -> "OK"
DEL key1
redis answer -> 1
Example GETDEL:
SET key1 "Hello"
redis answer -> "OK"
GETDEL key1
redis answer -> "Hello"

Okay, I understand. Thanks for clarifying

authors: cmatlak robinalfengard

repo: fungover/haze


text:
Add Exception handling for D3D12 errors.

Create the exception classes, make them inherit from std::exception, create macros for ease of use. Include D3D12 graphics validated errors that show up on the vs output console in the error info. Use ID3D12InfoQueue for this.

implemented

repo: furkanveli/Cashew


text:
Can't bind to 'type' since it isn't a known property of 'fusioncharts'

I'm trying to add fusionchart to my application but I keep on hitting this issue and I'm not sure what is wrong with my code.
For reference I used the Angular template for dotnet core (dotnet new angular)
This created an almost empty application with just 3 pages.
It also contains 3 "modules" files being app.browser.module.ts app.server.module.ts and app.shared.module.ts.
I assumed I had to drop the import config in the browser one (though I tried adding it in shared one and it still failed...)
Here is the content of this file now:
import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { AppModuleShared } from './app.shared.module';

import * as FusionCharts from 'fusioncharts';
import * as Charts from 'fusioncharts/fusioncharts.charts';
import * as FintTheme from 'fusioncharts/themes/fusioncharts.theme.fint';
import { AppComponent } from './components/app/app.component';
import { FusionChartsModule } from 'angular4-fusioncharts';

FusionChartsModule.fcRoot(FusionCharts, Charts, FintTheme);

@NgModule({
    bootstrap: [ AppComponent ],
    imports: [
        BrowserModule,
        AppModuleShared,
        FusionChartsModule
    ],
    providers: [
        { provide: 'BASE_URL', useFactory: getBaseUrl }
    ]
})
export class AppModule {
}

export function getBaseUrl() {
    return document.getElementsByTagName('base')[0].href;
}

The only modification I made was to add thte fusionchart related things.
I also modified the home page to include a chart, both the html and the ts
Here is the full error message I have (I did not even add the end of it as it is so big...):
An unhandled exception occurred while processing the request.
NodeInvocationException: Template parse errors:
Can't bind to 'width' since it isn't a known property of 'fusioncharts'. ("
<fusioncharts
[id]="id"
[ERROR ->][width]="width"
[height]="height"
[type]="type"
"): ng:///AppModuleShared/HomeComponent.html@19:8
Can't bind to 'height' since it isn't a known property of 'fusioncharts'. ("
[id]="id"
[width]="width"
[ERROR ->][height]="height"
[type]="type"
[dataFormat]="dataFormat"
"): ng:///AppModuleShared/HomeComponent.html@20:8
Can't bind to 'type' since it isn't a known property of 'fusioncharts'. ("
[width]="width"
[height]="height"
[ERROR ->][type]="type"
[dataFormat]="dataFormat"
[dataSource]="dataSource"
"): ng:///AppModuleShared/HomeComponent.html@21:8
Can't bind to 'dataFormat' since it isn't a known property of 'fusioncharts'. ("
[height]="height"
[type]="type"
[ERROR ->][dataFormat]="dataFormat"
[dataSource]="dataSource"
></fusioncharts>
"): ng:///AppModuleShared/HomeComponent.html@22:8
Can't bind to 'dataSource' since it isn't a known property of 'fusioncharts'. ("
[type]="type"
[dataFormat]="dataFormat"
[ERROR ->][dataSource]="dataSource"
></fusioncharts>

"): ng:///AppModuleShared/HomeComponent.html@23:8
'fusioncharts' is not a known element:
1. If 'fusioncharts' is an Angular component, then verify that it is part of this module.
2. To allow any element add 'NO_ERRORS_SCHEMA' to the '@NgModule.schemas' of this component. ("

[ERROR ->]<fusioncharts
[id]="id"
[width]="width"
"): ng:///AppModuleShared/HomeComponent.html@17:4
Error: Template parse errors:
Can't bind to 'width' since it isn't a known property of 'fusioncharts'. ("
<fusioncharts
[id]="id"
[ERROR ->][width]="width"
[height]="height"
[type]="type"
"): ng:///AppModuleShared/HomeComponent.html@19:8
Can't bind to 'height' since it isn't a known property of 'fusioncharts'. ("
[id]="id"
[width]="width"
[ERROR ->][height]="height"
[type]="type"
[dataFormat]="dataFormat"
"): ng:///AppModuleShared/HomeComponent.html@20:8
Can't bind to 'type' since it isn't a known property of 'fusioncharts'. ("
[width]="width"
[height]="height"
[ERROR ->][type]="type"
[dataFormat]="dataFormat"
[dataSource]="dataSource"
"): ng:///AppModuleShared/HomeComponent.html@21:8
Can't bind to 'dataFormat' since it isn't a known property of 'fusioncharts'. ("
[height]="height"
[type]="type"
[ERROR ->][dataFormat]="dataFormat"
[dataSource]="dataSource"
></fusioncharts>
"): ng:///AppModuleShared/HomeComponent.html@22:8
Can't bind to 'dataSource' since it isn't a known property of 'fusioncharts'. ("
[type]="type"
[dataFormat]="dataFormat"
[ERROR ->][dataSource]="dataSource"
></fusioncharts>

"): ng:///AppModuleShared/HomeComponent.html@23:8
'fusioncharts' is not a known element:
1. If 'fusioncharts' is an Angular component, then verify that it is part of this module.
2. To allow any element add 'NO_ERRORS_SCHEMA' to the '@NgModule.schemas' of this component. ("

[ERROR ->]<fusioncharts
[id]="id"
[width]="width"
"): ng:///AppModuleShared/HomeComponent.html@17:4

Any clue?

I am also have same problem do you get the solution.

@georgeslegros, can you please raise the same issue with a demo?

authors: georgeslegros rousan sparshbhawsar


text:
Add ingress config to SDN report

This PR adds ingress config to SDN report.
I don't think we can migrate it, because the definition of CR for configuring cluster-ingress-operator in OCP4, is using domain:
apiVersion: config.openshift.io/v1
kind: Ingress
metadata:
  name: cluster
spec:
  domain: apps.openshiftdemos.com

In OCP3 we are working with ingressIPNetworkCIDR in network config
networkConfig:
  clusterNetworks:
  - cidr: 10.128.0.0/14
    hostSubnetLength: 9
  externalIPNetworkCIDRs: null
  hostSubnetLength: 9
  ingressIPNetworkCIDR: 172.29.0.0/16
  networkPluginName: redhat/openshift-ovs-multitenant
  serviceNetworkCIDR: 172.30.0.0/16

I am not sure if domain can represent a CIDR notation, because notation can include a range of IP addresses, but my knowledge is very limited in this area.
https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing
https://docs.openshift.com/container-platform/3.11/install_config/configuring_sdn.html
https://docs.openshift.com/container-platform/4.1/networking/ingress-operator.html#configuring-ingress
@jmontleon @gildub @arapov What do you think?
Closes https://github.com/fusor/cpma/issues/199

I wonder whether we deal with read-only configuration of OCP4 here.
@alexander-demichev, if we imagine we can do this translation, is it the pre- or post- installation part? Do you have an idea?

This is likely a read only https://docs.openshift.com/container-platform/4.1/networking/ingress-operator.html#nw-installation-ingress-config-asset_configuring-ingress

authors: alexander-demichev arapov

repo: fusor/cpma


text:
Adding this library in Eclipse

I want to use this library for my app. However, I am developing my app in Eclipse.
Can you please tell me how can I add this library in Eclipse and use it for my app?
Thanks

I think you should be able to import this project sources into Eclipse as library sub-project and reference it from your main project. I recommend switching to IntelliJ/Android Studio and using gradle though.

authors: chalup rahulchowdhury


text:
git管理章节代码

基本快做完了，提个小意见，其实可以通过git管理每个章节的代码。因为现在pdf每个章节里面没有把所有的代码变动都详细贴出来，确实可能因为篇幅不方便放，但是有时候测试跑不通但是不知道是哪里的代码发生变动了，所以很难找。用git可以很方便看出不同章节之间代码的变动，可能会好点

支持。

authors: Appinx chanpero

repo: fuzhengwei/small-spring


text:
Can't force webhook registration over http

Describe the bug
When adding a integration in home assistant logs are showing the following:

2021-01-29 22:29:40 INFO (MainThread) [custom_components.reolink_dev.base] Host 192.168.1.181 subscribed successfully to webhook https://homeassistant.home/api/webhook/f78eea31*****

My home assistant is accessible from both https://homeassistant.home (through nginx reverse proxy) and http://homeassistant.home:8312 but no matter what I try integration seems to always register webhook through https and thus does not provide motion detection events.
To Reproduce

Remove all cameras
Enable debug logging for reolink integration
Add a camera again
Watch the logs for webhook registration message

Expected behavior
I expect integration to default to http protocol for webhook registration
Screenshots
If applicable, add screenshots to help explain your problem.
Environment:
Please provide useful information about your environment, like:

Home Assistant version - latest (2021.1.5)
Reolink camera model - latest (0.13)
Camera firmware number - v2.0.0.647_20031413

Additional context
I've tried adding integration from both http and https. Results seems to be the same in both cases.

What's your 'internal URL' in HA's configuration?
Integration seems to use that.

What's your 'internal URL' in HA's configuration?
Integration seems to use that.

Yes, that did it. I had to change internal URL to http in order for the webhook to be registered correctly. Thanks!

Yes, that did it. I had to change internal URL to http in order for the webhook to be registered correctly. Thanks!

hey  @andriej
your comment saved my life, I couldn't find on the docs about these options, so I believe that it should be added to the README, and include all options that can be changed - what do you think @fwestenberg?
I will clone the repo and raise some PR.
Let me give some details about my use case - I have the main router, which connects to the internet and provide internet to all cameras, in addition, I have another router that connects the cameras network, so all my computers and the raspberry pi are behind the second router, so the webhook was pointing to the internal IP of the PI (behind the second router), which is not accessible from outside.

I think @fwestenberg mentioned that reolink may add https support in firmware upgrade

authors: andriej ilyavolodin matheuscanela


text:
Modified the Spec of FybrikStorageAccount CR

Fixes #963.  Modified the Spec of FybrikStorageAccount.

Added an ID field in the spec of FybrikStorageAccount CR.
Paired an endpoint with a region using map

Hi @YingchaoDu, please note that Fixes #963 should be in the PR message (not in the title). Otherwise GitHub won't link the PR to the issue.

Changed. Thanks!

@YingchaoDu please rebase.

repo: fybrik/fybrik


text:
There is a convolution layer with kernel_size=1 and stride=2.

There is a convolution layer with kernel_size=1 and stride=2. I think its a loss of 50% of the information during processing.

I got this by running this cell of code.
module = drn_d_24(pretrained=False)
module

The quoted code snippet doesn't show stride=2. For some part of the network, the downsampling layers are only for subsampled residual connection. The full information is used in the 3x3 layers, while some information might be lost in the residual connections. This design follows the original residual networks for direct comparison.

repo: fyu/drn


text:
Simplify and optimize randomElements()

Figures, on 100000 iterations:

For several random elements: before 590 ms, after 320 ms
For one random element: before 390 ms, after 120 ms

Tests failing. Investigating.

Fixed an issue with $count = 0, but remaining test failures seem unrelated…

Looks like it's because of the change from mt_rand() to array_rand(), which discards the seed(). So if you want Faker to be possibly deterministic using a seed, I guess this PR has to be dropped…

repo: fzaninotto/Faker


text:
Client timeouts

It happens sometimes that the client timeout even if the ping command respond immediatly.
Which make me think there is a problem in the core0 itself.
Here is the little script that I use to reproduce:
from g8core.client import Client
cl = Client('172.20.0.1')
for i in range(10):
    cl.bash('ls /')

# this call timeout
cl.disk.list()

Fixed

authors: muhamadazmy zaibon


text:
added answers for 5 question.  did not get to question 6 or a

chance to run many of the rails create and generation commands or
script files

4.25 of 6 (-0.25 on Q3, -0.5 on Q4, -1 on Q6)
Nice work, Bill.

authors: MattB-GA-Boston bbarbersox

repo: ga-wdi-boston/rails-crud-assessment


text:
pixart homework

Completeness - 2
comfort level - 1.5
Tyler - I would love for us to talk about this topic (callbacks and events) in our next 1-on-1.

Hey Matt, I fixed the bugs in your code. I want you to really focus on getting each line to work before even worrying about writing another line. You can do this by testing things out in the Chrome developer console and not putting them into your .js file until you know they work.
You can see all of the changes that were needed to make this work here
The first big road block you likely encountered was getting document.querySelector to work properly, you had it written as document.querySelection which although looks very similar, does not work at all. In computer programs every letter matters and a spelling mistake can be the difference between something that works and something that doesn't.
I'm also happy to move our 1on1 to earlier in the day if that would be helpful

authors: mvaden tylercrosse


text:
Feature/hosted cli fix

Some fixes for hosted tools and workflows on the CLI, also some small cleanup.

Coverage decreased (-43.07%) to 25.826% when pulling 3bff7f35357123f98259cf89de9197b5d8944f6c on feature/hosted-cli-fix into cada20eebd1ca96d96cd7dda1296f2dc9ca5393b on develop.


text:
Adds html info page served at /

Displays the following info:
GA4GH reference server 0.5.1

Operations available

Method	Path
POST	/callsets/search
POST	/readgroupsets/search
POST	/reads/search
GET	/references/<id>
GET	/references/<id>/bases
POST	/references/search
GET	/referencesets/<id>
POST	/referencesets/search
POST	/variants/search
POST	/variantsets/search

Uptime

Running since 18 minutes ago (03:04:56 03 Feb 2015)

Issue #111

Pushed new commit with exception handling improvements, tests

Looks good @dcolligan, thanks. I've a few small refactoring requests, but I'm +1 after that.

@jeromekelleher pushed a commit to address your concerns

+1

+1
I'm happy to merge this but right now github says it won't apply cleanly even though travis passes. Any ideas @dcolligan?

That just means there are merge conflicts with things that have been committed to master in the interim...  I'll rebase it and then you can merge it from there.

Ok, just pushed a new commit... this one should pass the tests and then you can merge it after that @pashields

authors: Naburimannu dcolligan jeromekelleher pashields


text:
TypeError

Hi,
TypeError: Can't instantiate abstract class MixDataset with abstract methods configure_train_test_splits, load_features, sanity_checks.
The TypeError show up when I run python -m train --config configs_pub/eccv20/MSRVTT_jsfusion_trainval.json, please help with the solution.

Hi,
I could not reproduce this error, could you please share the stacktrace?

authors: DreamCatcher-cai gabeur

repo: gabeur/mmt


text:
[Discussion] Changing the validation flow

TL;DR; We are considering changing the tools and flow we use for validation.  This won't have any effect on how to use the library, but will affect how to develop for and debug the library.

Current flow: 1) create interfaces in typescript, 2) convert to json schema, 3) use ajv for runtime validation.  Pros: (+) it's all setup and works, (+) it's fast.  Cons: (-) need to constantly regenerate the schema on changes, (-) ajv library is hard to debug, doesn't work in non-node environments.

Proposed: 1) create schema using relevant library, 2) infer to typescript, 3) use same lib.  Pros: (+) single source of truth, no need to constantly regenerate schema, (+) work in non-node envs.  Cons: (-) a lot of work!  Mixed: (+/-) Test speed could get better/worse based on library choice and implementation.

This discussion arose from a great exchange I had with @eddie-atkinson in https://github.com/gadicc/node-yahoo-finance2/issues/719.  Readers wanting more background on the issue may want to start there, however, I've summarized the most important points above and am quoting his most recent post below for us to continue the conversation from there.  Massive thanks again to Eddie both for raising the issue and for his contributions and research to the discussion.
I stress again that this change will have no visible impact on documented use of yahoo-finance2 but will impact developers and debuggers.  I expect after a full implementation the impact will be a more positive dev experience.  However, end-users who have written any custom flows (that were never documented or proposed) against the existing schema would need to rewrite their code -- I'm currently not aware of anyone who has done this.

Quoting @eddie-atkinson from https://github.com/gadicc/node-yahoo-finance2/issues/719#issuecomment-2076253522 (replying to me):

The flow is actually: a) typescript interfaces for all the APIs, b) typescript interfaces -> json schema, c) ajv to validate input using the json schema.

Given that this is the current workflow it feels like cutting out JSON Schema could make sense as a way of simplifying development as the source of truth is Typescript.

Lastly, AJV was actually selected (at the time?) due to being significantly faster (by a large margin) than all other solutions, which is handy considering that we have 1000's of tests

That's a fair call out that I didn't consider. Looking at the benchmarking done here it seems like zod has pretty poor performance characteristics compared to ajv. Interestingly the top 3 in the rankings all use Typescript types as their source of truth, though admittedly not "pure" Typescript (they have annotations you need to add). I did a little survey of the tools that ranked higher than ajv on that benchmark and I'm interested in your view. From the perspective of bundle size, maturity, and weekly downloads @sinclair/typebox seems like a promising option. Especially given that its perf in AOT and JIT mode exceed ajv. It also appears to support CF workers.

(source)

Name
Stars
Weekly Downloads
Date of first commit
Minified Bundle Size (as reported by bundlephobia)

ts-runtime-checks
228
146
2022-07-22
58 kB

@sinclair/typebox
4200
24,239,331
2017-04-07
50 kB

typia
4045
24,148
2022-04-19
65.4 kB

spectypes
91
31
2022-04-29
1.7 kB

suretype
490
17,553
2023-02-26
139 kB

ts-json-validator
341
29,848
2019-10-31
118.8 kB

ajv
13,378
81,611,055
2015-05-31
119.6 kB

But this would be a huuuge job, and I also think, probably worthy of a communal debate with enough time to elicit responses.

Is there a particular venue where you'd like to have that discussion? Here in this thread? GitHub discussions? I appreciate that this thread is, at the moment at least, a bit too hidden a way to have a discussion of this magnitude.

I would probably start off by looking for something that converts typescript interfaces to zod code, as a starting point... as there are a loooot of them

Yes and no, as shown by my highly scientific survey here:

The real questions for me would be less the leg work of converting all the interfaces and more so how we review the changes.

Keen to hear your thoughts and happy to put together a micro benchmark of some of the more gnarly interfaces to test feasibility and performance on any libraries of interest.

Firstly, @eddie-atkinson, thanks so much both for raising this issue but most especially for your preliminary research and helpful discussion.
Wow, I'd never heard of @sinclair/typebox before.  It looks super interesting.  I was actually a little excited thinking about zod since it's become so ubiquitous but I did suspect that performance would be an issue, since it's designed for much more complex cases than what we need (predominantly, just making sure runtime values match the expected typescript interfaces, which seems to be @sinclair/typebox's exact use-case).  Excited to see how well it could work for us.  If anyone else has other suggestions, let us know, otherwise I think this is a good place to start (and thanks again to Eddie for bringing it to our attention).
We will need coercion for some cases and we'll need to think at what level to best handle that.  More details in that file but in short:
YahooFinanceNumber: 123123 | { raw: 123123, formatted: "123,13" } | null?
YahooFinanceDate: Date | { raw: <unixEpoch>, /* other fields? */ } | StrDate | null?
DateInMs
TwoNumberRange: { low: 1, high: 10 }

The real questions for me would be less the leg work of converting all the interfaces and more so how we review the changes.

Very true.  It's a pity most of our tests are just "validation passes", but we do have a bunch that test for expected failures too.  Having said that, the main thing is just that types match... so probably enough to just check that the old typescript interface and the newly inferred one match (which should be pretty easy).
Thanks again for your efforts here and yeah sure, if you feel like playing around a bit and reporting back that would be absolutely amazing! :pray:   A first step might be making sure we'll be able to do the coersion, but I feel like we should be able to handle that fairly easily at the library level as long as we can expect the field type.

cc:

@nocodehummel (who's working at refactoring the testing architecture): FYI, and in case you have any input
@dtslvr (Ghostfolio author): FYI, but probably doesn't have much impact for you

if you feel like playing around a bit and reporting back that would be absolutely amazing!
I'll have a poke around this week and see if I can make coercion work 👍

Amazing!  You're the best :clap:   Thanks again :grin:

Hey @gadicc
I've had a bit of a play and put up a draft PR: https://github.com/gadicc/node-yahoo-finance2/pull/772
It seems like typebox can support the coercion logic that we currently have and is reasonably flexible. Nowhere in the league of Zod, but as the maintainer notes on several occasions this is why Zod's performance is not as good.
More details in the PR, but the TL;DR is I have created utility types in Typebox for YahooFinanceNumber, YahooFinanceDate, DateInMs and TwoNumberRange and added unit tests following the mold of the existing validateAndCoerceTypes.spec.ts.
Still need to add my own version of validateAndParse and test it for sensible error formatting. I'd also like to independently benchmark ajv vs typebox for a couple of choice interfaces to make sure there hasn't been a huge performance regression.

You, Sir, are a legend! :ok_hand:
My comments upcoming on the PR... but in short, I really believe this will be a massive improvement.  I've had something like this in the back of my mind for quite some time, but also no time to actually look at it seriously.  So thanks once again for raising this (ironically as an ancillary issue to getting this running outside of node), for taking it on, conducting research, and getting coding.  Open source projects can become quite draining, and then things like this happen, which is honestly just... wonderful.  So thank you :)

You, Sir, are a legend! 👌

Straight back at you, not sure I would have the stamina to run an open source project of this size for as long as you have, so kudos to you.

So thanks once again for raising this (ironically as an ancillary issue to getting this running outside of node)

You have no idea how much of a yak shave this will be for me. I started out just wanting to build a stock tracker for pricing the stock options I get for work properly 🙃. Great opportunity to give back to the community though so I'm more than happy to do it

Open source projects can become quite draining, and then things like this happen, which is honestly just... wonderful. So thank you :)

❤
zI've added some more commits to the PR whenever you get a spare minute to have a gander. I'll probably hack a bit more this week / weekend

not sure I would have the stamina to run an open source project of this size for as long as you have, so kudos to you.

thanks :pray: :heart:   the struggle is real.  i'd say I unfortunately don't manage to get to a large chunk of issues, but I've always tried to prioritise PRs, issues that could lead to PRs, schema fixes and anytime changes on Yahoo end broke functionality.  So while I haven't managed to maintain things at the level I'd hoped, the project continues to chug along :sweat_smile: :sweat_smile:

You have no idea how much of a yak shave this will be for me.

Haha, been down that rabbit hole way too many times.  But yeah, it's great when entire communities benefit from it.  So thanks so much again!  As for a stock tracker, not sure if you already saw Ghostfolio, probably the biggest single usage of this project - could save you some time if you're willing to go a servered (non-serverless, non-edge) approach.  I have my own small personal project - not open source - that's serverless NextJS though, so do understand stack preferences :blush:

authors: eddie-atkinson gadicc


text:
🛑 Trends is down

In 2cf6716, Trends (https://trends.gab.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Trends is back up in 8a0e8d4 after 58 minutes.

repo: gadmln/gabstatus


text:
🛑 Social is down

In 1c48d2e, Social (https://gab.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Social is back up in 0ca1327.

Resolved: Social is back up in 0ca1327.


text:
remove rimraf

because we can just rm -rf

We're actually probably just going to switch to shelljs: #94
Rimraf was there for Windows compatibility but I broke it later (hence #94)

authors: chicoxyzzy gaearon

repo: gaearon/redux


text:
feat(forge/debugger): Dynamic layout, stack & memory scrolling

Motivation
We were extremely sensitive to window size. Additionally, when stack and memory were too large, the user couldn't inspect tail elements. Also sometimes the user will store string in memory, where weren't decoded into string.
Solution
This adds dynamic sizing and a vertical view. Additionally, the user can now scroll memory and stack elements with ctrl + j/k and shift + j/k, respectively. Finally, we also add the ability to toggle memory decoding with  m.  Any non-null unicode characters are decoded. Null unicode  characters are replaced with  ..
Also fixes dimming issues by removing the color specifier in combination with DIM. This improves compatibility across terminals.

🔥🔥🔥

authors: brockelmore sambacha

repo: gakonst/foundry


text:
[Metagenomics] New tutorial "Taxonomic profiling and visualizazion"

@Sophia120199 and I created a new tutorial about taxonomic profiling, a bit more on the theory and tool comparison aspect, that also cover different visualizations

And thanks @Sophia120199! :tada:

authors: bebatut shiltemann

repo: galaxyproject/training-material


text:
Add the need for custom .gitignore extensions to the Getting Started guide.

Context
I just ran into an issue where I got a 'dirty branch'.
The trouble shooting page for dirty branch tells you to clone the project into an empty folder, create a build, and see if any changes were made to autogenerated files in your project.
This was not the case for me, however, I was still getting the issue.

I then added
# Ignore results from game-ci
/[Aa]rtifacts/
/[Cc]odeCoverage/

to my .gitignore, and now no longer encounter this error.
The only mention of .gitignore in the docs is here, which links to the proper Unity .gitignore file, but that does not include these two folders that were generated by running the workflow that follows the simple Example workflow listed here.
Suggested solution
Add a section to the Getting Started section that explains you have to expand the default .gitignore file to get things working.
Considered alternatives

Additional details

I forked the documentation repo and committed my suggested improvement:
https://github.com/game-ci/documentation/compare/main...kemmel-dev:documentation:main

Great suggestion and nice work on getting started on it as well!
Feel free to open a Pull Request to game-ci/documentation at its main branch.
Note that we try to keep our documentation as concise as possible (so that people actually read it). Two points of feedback:

My suggestion would be to reduce the amount of words needed for adding that suggestion.
We refer to our community as GameCI (functional), and only use game-ci when it's a namespace or implementation specific.

Okay, I will try to incorporate those points of feedback and submit a PR in a bit!

Fixed by https://github.com/game-ci/documentation/pull/366

I encountered the same error, but with a different file that I had excluded from the .gitignore:
...
Warning: Changes were made to the following files and folders:

Warning:  M Packages/manifest.json

Error: Branch is dirty. Refusing to base semantic version on uncommitted changes

Here is my .gitignore:
...
# The packages folder can be ignored because of Package Restore
**/[Pp]ackages/*
# Except for the manifest, which tells Unity which packages to install
!**/[Pp]ackages/manifest.json
...

Maybe I shouldn't have excluded the file, but this was the only way I found to ensure my team uses the same library versions. Do you know of a better way to handle this, or is there a way to avoid the error?

Sorry to bother you. I’ve solved the problem, it was related to the out-of-space issue.  I had to separate the jobs to run them in parallel, which triggered the "out of space" issue. So, I used the action you recommended in the docs to free up space, and all my builds started passing.
I already commented here: https://github.com/game-ci/unity-builder/issues/554#issuecomment-2525416383, but I believe it’s more relevant to this repository.
My project is currently very small (with an almost empty scene, a few scripts, and the usual Unity packages), and it seems strange to me that using the parallel workflow and the free-up-space action is considered optional in the docs. I can’t imagine a project that could run without this configuration (at least in Unity 6, which I’m using).

@stariluz You're right that a good number of Unity projects won't be able to test and build on the default GitHub runners without freeing up disk space. Especially when building to Android as the target platform, I suspect that even a blank Unity project would require freeing up disk space. For that reason, we do try to show the free-disk space action alongside all builds to Android in the docs.
But there also a lot of projects that won't need an action to free disk space. It is very possible to have a project small enough to run on the default GitHub runners without freeing disk space when building to non-Android target platforms. All my personal projects do fall into this small size.
More importantly, the free-disk-space action isn't necessarily the best solution for a project that needs more disk space than available on the default GitHub runners. Many projects may prefer to instead have self-hosted runners, or to use the cloud-runner (aka Coordinator), or to pay GitHub for larger runners. All these options are valid, and we want to bring visibility to these options.

authors: davidmfinol kemmel-dev stariluz webbertakken

repo: game-ci/documentation


text:
Ping

Create ping traffic (keep-alive) between mediator and client-websocket.
Builds atop  PR #74
Client-side can then do better connection management (timeout/pause-resume)

This change is

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

authors: BarDweller ebullient

repo: gameontext/gameon-mediator


text:
Fairy | Deps: Upgrade actions/cache.

Motivation

We're too behind on too many GHA deps.
This also means too many PRs from dependabot to live with.

TODO

Read and understand all relevant release notes.
If any change is required, please open a PR and do it.
End result will be merging #383.

@tomerle What is the status with this one?

@Ronensh110, tested myself. It's only the build process, and not the deploy, so we're cool. Declaring DONE.
FYI, Fairy releases are anyway meaningless to you guys, and you will test it anyway when TinkerBell upgrades to a newer Fairy version.

repo: gamitee-dev/html-fairy


text:
styled-components interpolation highlighting issue

Just saw this issue with the styled-components highlighting in some code:

Any idea what the issue here is?

Well, that was unbelievably fast! Thank you! 👏

repo: gandm/language-babel


text:
Flash during reload of slider on Chrome/Microsoft Edge

Issue description:
During the reload of the slider - when the last image changes in the first image - a flash appears. The flash corresponds to the fall back colour, which in our case is black. Can you please look into the issue and check if this can be solved?
Demo link/slider setting:
http://detron.acc-server.nl/
Tiny-slider version:
2.9.3
Browser name && version:
Chrome - Version 103.0.5060.114 (Official Build) (arm64) --> is irrelevant to this problem
OS name && version:   is irrelevant to this problem

I found a preview workaround solution for this bug in Chrome. In the file tiny-slider.js (on March 02, 2023) there is a doContainerTransformSilent function. In it, the command resetDuration(container, '0s'); You need to specify a very small duration value (I used 13ms). After this fix, the flashing bug disappears in Chrome.

authors: AChPCoder BasBlueDragon

repo: ganlanyuan/tiny-slider


text:
Nit: Switch notes to the new notes syntax in Github

How to categorize this PR?

/area documentation
/kind enhancement
What this PR does / why we need it:
See https://github.com/orgs/community/discussions/16925
Before:

After:

Which issue(s) this PR fixes:
N/A
Special notes for your reviewer:
N/A
Release note:

NONE

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Ismail Alidzhikov seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant ialidzhikov


text:
POC: Refactoring - moving seed determiner logic into dedicated strict

How to categorize this PR?
/area control-plane
What this PR does / why we need it:
We have a feature-request on Kyma side to offer customers an option to enforce that a seed and shoot are running in the same region. Our goal is to validate whether a seed would be available in a region before creating a shoot. This saves processing time on Gardener side and allows short roundtrip-times on our side in case of non-matching seed clusters.
This PR is a pure refactoring of reconciler which is moving logic related to determine the seed into a separate struct. No functional changes were applied, just code re-arrangements.
The change improves also a bit the separation of concerns within the logic. The reconciler is purely responsible for reconciliations, the seed-determiner does nothing beside determining the seed cluster.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Release note:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

After a call with @ScheererJ  we agreed on following options for the seed determining logic:

We change the visibility of the determineSeed function (from determineSeed to DetermineSeed) on the current Reconciler to make it public accessible and consumable for other applications (challenge could be to set the right strategy for detecting a suitable seed as it's depending on the Shoot purpose)
We consider the proposed PR and extract the determineSeed logic into a new struct (challenge could be to set the right strategy for detecting a suitable seed as it's depending on the Shoot purpose)
The other application implements their own determining logic by checking for the existence of a seed in this region

After a call with @ScheererJ we agreed on following options for the seed determining logic:

We change the visibility of the determineSeed function (from determineSeed to DetermineSeed) on the current Reconciler to make it public accessible and consumable for other applications (challenge could be to set the right strategy for detecting a suitable seed as it's depending on the Shoot purpose)
We consider the proposed PR and extract the determineSeed logic into a new struct (challenge could be to set the right strategy for detecting a suitable seed as it's depending on the Shoot purpose)
The other application implements their own determining logic by checking for the existence of a seed in this region

@ScheererJ is getting in contact with a team colleague to discuss these options and will reply in the coming 1-2 weeks with a suggestion how to proceed.

After offline discussion, option 1 seems to be a simple and acceptable solution. Please adapt the pull request accordingly.
Please note that a general option to enforce same region seed clusters in scheduling may be something for a future gardener hackathon. Let me know if you would like to join :-) .

/assign

authors: CLAassistant ScheererJ tobiscr

repo: gardener/gardener


text:
Rotation matrix output columns aligned.

Hello,
I love this library.  I changed the format of the output rotation matrix so that the columns align.  To do this I added a function to convert to fixed width strings of each matrix element.
Mark Brudnak

I made all requested changes.

Thanks again for your patch, merged it.

authors: gaschler malibrud

repo: gaschler/rotationconverter


text:
Title not displaying with "Save As"

Might be HTML-escaped

Fixed with 3fbfb695b563efced12669f55adae559c8dc531c


text:
hey quick question/ possible error

hey in misc functions
	if [ -n __BMT_START_WATCH ]
		then
			local stopWatchVar=0
			stopWatchVar=$(bmtMiscFunc now)
			bmtMiscFunc elapsed "$__BMT_START_WATCH" "$stopWatchVar"
			return 0
		else
			return 2
		fi
	;;

under stopwatch #6 shouldnt it be
if [[ -n "$__BMTSTART_WATCH" ]];
     then

i could be wrong I'm fairly new to programming.

HI
Yes that's correct. that's a typo, I should have spotted that as shellcheck flags it as an  issue(SC2154) and I always run shellcheck on scripts before i use/publish them.
The stopwatch function still works  , that "if statement" is only there to catch a user error: if they run "stopWatch" before they run "startWatch". and return error code 2.
thanks

hey no worries i just wasn't sure if there was some convention i didn't know about, i only noticed it because I'm building a bash snippet manager / command line IDE  and that and i happened to be doing it in vs code and it point it out to me. I've only been programming 6 months and exclusively in bash so far and its got some jacked up exceptions (like I've seen code that's set up to intentionally fail which still doesn't make sense to me).

authors: gavinlyonsrepo rayiik

repo: gavinlyonsrepo/bashmultitool


text:
Fix Camera info test

🦟 Bug fix
Summary
Fix incorrect camera info sdf tag used in test
Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

Needs https://github.com/gazebosim/sdformat/pull/1241 for green CI

repo: gazebosim/gz-sensors


text:
Error:   Could not find the 'robot' element in the xml file

When I transfer sdf model to usd model. I met the issue below.
Error:   Could not find the 'robot' element in the xml file          at line 109 in /build/urdfdom-VnCcob/urdfdom-1.0.4+ds/urdf_parser/src/model.cpp Errors encountered: Error Code 1: Msg: Unable to read file:model.sdf
Here is the sdf file:
https://github.com/bitcraze/crazyflie-simulation/blob/main/gazebo-ignition/crazyflie/model.sdf

Try changing the name of your file from model.sdf to something else. I dont know why but this made a difference for me. An issue for this has been raised.
refer to #8

authors: Zhehui-Huang joshuacv

repo: gazebosim/gz-usd


text:
Some errors in log

Thanks @gazoodle for the "alpha" integration.
Here some errors in HA logs :
`Logger: homeassistant.util.async_
Source: util/async_.py:105
First occurred: 9:54:09 (1 occurrences)
Last logged: 9:54:09
Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for gecko doing I/O at custom_components/gecko/init.py, line 47: facade = locator.get_spa_from_identifier(spa_identifier).get_facade(False)`
`Logger: geckolib.driver.udp_socket
Source: /usr/local/lib/python3.8/site-packages/geckolib/driver/udp_socket.py:316
First occurred: 9:54:17 (17 occurrences)
Last logged: 10:04:31
Couldn't find new handler for b"STATV\t\n'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00"
Couldn't find new handler for b"STATV\n\x0b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00"
Couldn't find new handler for b"STATV\x0b\x0c'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00"
Couldn't find new handler for b'STATV\x0c\x00\x0b\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'
Couldn't find new handler for b'PACKS'`
`Logger: geckolib.driver.spastruct
Source: /usr/local/lib/python3.8/site-packages/geckolib/driver/spastruct.py:49
First occurred: 9:54:19 (46 occurrences)
Last logged: 10:09:39
Out-of-sequence status block segment 8 - ignored
Out-of-sequence status block segment 9 - ignored
Out-of-sequence status block segment 10 - ignored
Out-of-sequence status block segment 11 - ignored
Out-of-sequence status block segment 12 - ignored`
`Logger: geckolib.driver.spastruct
Source: /usr/local/lib/python3.8/site-packages/geckolib/driver/spastruct.py:53
First occurred: 9:54:22 (5 occurrences)
Last logged: 10:09:39
Retry status block request`
The version of GeckoLib is 0.3.17 that was installed when I installed the integration via HACS
Also, the Pump is set as a switch, so unable to see/set the Speed of it (you know, I have a 2 speed pump). So maybe set Pump as a "Fan" instead of a "Switch"?

Thanks! I’ll look into the I/O during init.
Pumps: I’ve not implemented multi speed yet, but representing as a fan was the way I was planning on going!

Thank you Gazoodle, found your HA addons for gecko intouch2. Much welcomed! Installation worked fine (HA runs on Odroid N2+), also intergration shows up the relevant parameters from the spa.
Several entries in the HA logfile show up:
1.
Logger: homeassistant.util.async_
Source: util/async_.py:105
First occurred: 22. Dezember 2020, 18:59:43 (1 occurrences)
Last logged: 22. Dezember 2020, 18:59:43
Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for gecko doing I/O at custom_components/gecko/init.py, line 45: facade = locator.get_spa_from_identifier(spa_identifier).get_facade(False)

Logger: geckolib.driver.spastruct
Source: /usr/local/lib/python3.8/site-packages/geckolib/driver/spastruct.py:49
First occurred: 22. Dezember 2020, 19:00:01 (444 occurrences)
Last logged: 07:28:49
Out-of-sequence status block segment 8 - ignored
Out-of-sequence status block segment 9 - ignored
Out-of-sequence status block segment 10 - ignored
Out-of-sequence status block segment 11 - ignored
Out-of-sequence status block segment 12 - ignored

Logger: geckolib.driver.spastruct
Source: /usr/local/lib/python3.8/site-packages/geckolib/driver/spastruct.py:53
First occurred: 22. Dezember 2020, 19:00:03 (63 occurrences)
Last logged: 07:28:49
Retry status block request

All these issues should be resolved now

authors: Abtsbergblick gazoodle sicarriere

repo: gazoodle/gecko-home-assistant


text:
storybook: Ревью компонентов

Посмотреть тексты в компонентах, предложить корректировки (в едином стиле, на одном языке)

+Сделать гайд по ним

Место для пулреквестов коничилось, не могу больше прилинковать :)

authors: Lyubavskaya arhayka

repo: gazprom-neft/consta-uikit


text:
Identifiers validation failed for dataset Inventario florístico complementario de la Reserva de la Biosfera Sierra de Huautla (REBIOSH)

Identifier validation failed for the dataset Inventario florístico complementario de la Reserva de la Biosfera Sierra de Huautla (REBIOSH):

Crawler attempt: 233
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 2421
Cause: GBIF IDs hit maximum allowed - 50%, duplicates - 100%, total records count 2421, absent records count 2421
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3073576/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Inventario florístico complementario de la Reserva de la Biosfera Sierra de Huautla (REBIOSH) : https://doi.org/10.15468/ntpgmw.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Inventario florístico complementario de la Reserva de la Biosfera Sierra de Huautla (REBIOSH):

Crawler attempt: 236
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 2421
Cause: GBIF IDs hit maximum allowed - 50%, duplicates - 100%, total records count 2421, absent records count 2421
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3094390/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Inventario florístico complementario de la Reserva de la Biosfera Sierra de Huautla (REBIOSH) : https://doi.org/10.15468/ntpgmw.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

repo: gbif/ingestion-management


text:
Spanish list of languages

@MortenHofft @thomasstjerne if you can scrape it in a useable format, this could go a significant distance toward addressing that 5%-complete menu in CrowdIn:
https://es.wiktionary.org/wiki/Wikcionario:Lista_de_lenguas

en français: https://fr.wikipedia.org/wiki/Catégorie:Inventaire_de_langues

https://en.wikiversity.org/wiki/ISO_639-1_language_matrix will be easier.

I've just converted them only to realize they are 2 letter codes. we use 3 letter.
{
"language": {
"ab":	"abjazio",
"af":	"afrikaans",
"an":	"aragonés",
"ar":	"árabe",
"as":	"asamés",
"az":	"azerí",
"be":	"bielorruso",
"bg":	"búlgaro",
"bn":	"bengalí",
"bo":	"tibetano",
"br":	"bretón",
"bs":	"bosnio",
"ca":	"catalán / valenciano",
"ce":	"checheno",
"co":	"corso",
"cs":	"checo",
"cu":	"eslavo eclesiástico",
"cy":	"galés",
"da":	"danés",
"de":	"alemán",
"el":	"griego",
"en":	"inglés",
"eo":	"esperanto",
"es":	"español / castellano",
"et":	"estonio",
"eu":	"eusquera",
"fa":	"persa",
"fi":	"finés",
"fj":	"fidji",
"fo":	"feroés",
"fr":	"francés",
"fy":	"frisón occidental",
"ga":	"irlandés",
"gd":	"gaélico / gaélico escocés",
"gl":	"gallego",
"gv":	"manés",
"he":	"hebreo",
"hi":	"hindi",
"hr":	"croata",
"ht":	"haitiano, criollo haitiano",
"hu":	"húngaro",
"hy":	"armenio",
"id":	"indonesio",
"is":	"islandés",
"it":	"italiano",
"ja":	"japonés",
"jv":	"javanés",
"ka":	"georgiano",
"kg":	"kongo",
"ko":	"coreano",
"ku":	"kurdo",
"kw":	"córnico",
"ky":	"kirguís",
"la":	"latín",
"lb":	"luxemburgués",
"li":	"limburgués",
"ln":	"lingala",
"lt":	"lituano",
"lv":	"letón",
"mg":	"malgache",
"mk":	"macedonio",
"mn":	"mongol",
"mo":	"moldavo",
"ms":	"malayo",
"mt":	"maltés",
"my":	"birmano",
"nb":	"noruego (bokmal)",
"ne":	"nepalí",
"nl":	"neerlandés",
"nn":	"noruego (nynorsk)",
"no":	"noruego",
"oc":	"occitano (después de 1500); provenzal",
"pl":	"polaco",
"pt":	"portugués",
"rm":	"reto-románicas",
"ro":	"rumano",
"ru":	"ruso",
"sc":	"sardo",
"se":	"sami septentrional",
"sk":	"eslovaco",
"sl":	"esloveno",
"so":	"somalí",
"sq":	"albanés",
"sr":	"serbio",
"sv":	"Sueco",
"sw":	"swahili",
"tk":	"turcomano",
"tr":	"turco",
"ty":	"tahitiano",
"uk":	"ucraniano",
"ur":	"urdu",
"uz":	"uzbeko",
"vi":	"vietnamita",
"vo":	"volapuk",
"yi":	"yídish",
"zh":	"chino"
}
}

https://en.wikipedia.org/wiki/List_of_ISO_639-2_codes has both the two-letter and three-letter codes. There's probably a tabular format somewhere.
https://github.com/haliaeetus/iso-639/blob/master/data/iso_639-1.csv
https://gist.github.com/kaisyu/6103312

There was roughly a 100 names in those lists that you linked. They are now parsed from html, mapped to 3 letter iso codes and uploaded to crowdin. There is still 400 languages codes missing. But the most frequent ones was no doubt in the lists you linked to.
The uploaded languages appear as not approved in Crowdin. I have not proofread them in any manner.

authors: MattBlissett MortenHofft kcopas


text:
Loaders for all routes reload on any navigation

See router example. Contacts list should never reload, but reloads when any navigation happens.

The problem is actually that the router is re-running the root element over and over. See https://github.com/gbj/leptos/blob/3638f488c9df00ad2cc796fd33995504ecef7e39/router/src/components/routes.rs#L132-L140

Closed by b6cdf43622a1be87ac5a6573a07d0cd5fdc15ce4

repo: gbj/leptos


text:
Add missing multipolygon import

The function plot_buildings uses MultiPolygon but it is not imported:
elif isinstance(geometry, MultiPolygon):
    for subpolygon in geometry: #if geometry is multipolygon, go through each constituent subpolygon
        patches.append(PolygonPatch(subpolygon))

I only discovered this bug because i modified my buildings gdf so that it included multipolygons. create_buildings_gdf only generates a gdf consisting of polygons so alternatively the quoted lines could also be deleted and the additional import omitted.

Coverage decreased (-0.3%) to 94.289% when pulling 1dc9118f8ebc956113d75969c60e3af9ec28385a on Dosenpfand:fix_builings_plot into 47eb3890cbb36611f342486b9ea128e4cd18aa59 on gboeing:master.

@Dosenpfand thanks!

authors: Dosenpfand coveralls gboeing

repo: gboeing/osmnx


text:
Piping with sum types broken?

🐛 Bug report
Current Behavior
In fp-ts@1.x, I was able to chain sum typed values through methods that returned any one of the union's members (see the contrived example below). Starting with 2.x, using pipe and chain, I am getting type errors on the first argument
// contrived example
import { chain, either, fromPredicate } from 'fp-ts/lib/Either'
import { pipe } from 'fp-ts/lib/pipeable'

type InvalidPositive = ["InvalidPositive", number];
type InvalidInteger = ["InvalidInteger", number];

type InvalidPositiveInteger = InvalidPositive | InvalidInteger;

const positive = fromPredicate(
  (n: number) => n > 0,
  (a): InvalidPositive => ["InvalidPositive", a]
);

const integer = fromPredicate(
  (n: number) => Number.isInteger(n),
  (a): InvalidInteger => ["InvalidInteger", a]
);

pipe(
  either.of<InvalidPositiveInteger, number>(2), // <<< Type exception here
  chain(positive),
  chain(integer)
);

/**
Type exception I get is:

Argument of type 'Either<InvalidPositiveInteger, number>' is not assignable to parameter of type 'Either<["InvalidPositive", number], number>'.
  Type 'Left<InvalidPositiveInteger>' is not assignable to type 'Either<["InvalidPositive", number], number>'.
    Type 'Left<InvalidPositiveInteger>' is not assignable to type 'Left<["InvalidPositive", number]>'.
      Type 'InvalidPositiveInteger' is not assignable to type '["InvalidPositive", number]'.
        Type '["InvalidInteger", number]' is not assignable to type '["InvalidPositive", number]'.
          Type '"InvalidInteger"' is not assignable to type '"InvalidPositive"'.ts(2345)

**/

I can only solve this by specifying the sum type in each call to chain like so:
pipe(
  either.of<InvalidPositiveInteger, number>(2),
  chain<InvalidPositiveInteger, number, number>(positive),
  chain<InvalidPositiveInteger, number, number>(integer)
);

Expected behavior
I expect sum types to be able to pipe to methods that return union set members without causing type exceptions.

Reproducible example
Suggested solution(s)

Additional context

Your environment
Which versions of fp-ts are affected by this issue? Did this work in previous versions of fp-ts?

Software
Version(s)

fp-ts
2.1.x

TypeScript
3.6.x

Closing in favor of https://github.com/gcanti/fp-ts/issues/904

@gcanti - not sure this should be closed in favor of #904 . Though they are similar issues, they are not the same problem.
#904 is about automatically widening "Lefts" on Eithers, this one is about the interface of pipe and chain not accepting valid values. Notably, #904 would still be applicable in v1.x, while this issue was not present in the previous "class-based" version of Either/TaskEither/IOEither etc.
If I start with an Either<L | M, A> I should be able to chain it to a method that returns Either<L, A> or Either<M, A>. I should not need to "widen" type types down the pipeline.
Correct me if I'm wrong, but I believe this is an issue with either pipe or chain's interface definition(s).
Thoughts?

To my point, the following does not cause a type exception:
pipe(
  either.of<InvalidPositiveInteger, number>(2),
  ma => either.chain(ma, positive),
  mb => either.chain(mb, integer)
);

While this does:
e = pipeable(either)

pipe(
    either.of<InvalidPositiveInteger, number>(2),
    e.chain(positive),
    e.chain(integer)
)

@christianbradley the issue is the same: TypeScript type inference goes from left to right:
in
pipe(
  either.of<InvalidPositiveInteger, number>(2),
  ma => either.chain(ma, positive),
  mb => either.chain(mb, integer)
)

TypeScript infers
pipe(
  either.of<InvalidPositiveInteger, number>(2),
  // ma: Either<InvalidPositiveInteger, number>
  ma => either.chain<InvalidPositiveInteger, number, number>(ma, positive),
  // mb: Either<InvalidPositiveInteger, number>
  mb => either.chain<InvalidPositiveInteger, number, number>(mb, integer)
)

because, going from left to right, ma has type Either<InvalidPositiveInteger, number>, so chain is inferred as
chain<InvalidPositiveInteger, number, number>

however in
pipe(
  either.of<InvalidPositiveInteger, number>(2),
  e.chain(positive),
  e.chain(integer)
)

TypeScript infers
pipe(
  either.of<InvalidPositiveInteger, number>(2),
  e.chain<InvalidPositive, number, number>(positive),
  e.chain<InvalidInteger, number, number>(integer)
)

because e.chain has the following signature
chain: <E, A, B>(f: (a: A) => Either<E, B>) => (ma: Either<E, A>) => Either<E, B>

so in our case, going from left to right, the first e.chain has the following type
//      +-- E inferred as InvalidPositive
//      |
//      v                  this doesn't type check because E is already inferred as InvalidPositive  ------v
chain: <InvalidPositive, number, number>(f: (a: number) => Either<InvalidPositive, number>) => (ma: Either<InvalidPositiveInteger, number>) => Either<E, B>

authors: christianbradley gcanti

repo: gcanti/fp-ts


text:
Add unit tests for integration test suite

Currently the integration-test module is untested. It defines test classes which are used/extended by various Gaffer stores, but these tests are not tested themselves (unit or integration).
Usually tests don't have tests. But in this case integration-test is used as a utility class for other parts of Gaffer and is not simply a traditional test.
Adding some unit tests to integration-test will help to prevent problems caused by other changes from going undetected. Due to how the tests classes are written, there's a potential for tests to become broken without this being detected. This is because if the tests do not run or are skipped then it will appear from the CI that there's no problem.

@GCHQDeveloper314 How big a piece of work is this?

This is small piece of work. I would anticipate only a couple of new files containing some basic Unit tests.

Fixed by #2732

repo: gchq/Gaffer


text:
Add reduce option on accumulo-spark ImportRDDOfElements

Currently the importRDDOfElements operations just partition's the elements according to the accumulo table's split points and writes the result to HDFS to be imported,
We should add an option so that the RDD can be aggregated before partitioning.

@james010101101 is this still required? Have you done any work on it?

As noted above, this should be optional. The default option should be to perform the aggregation (as long as there are some groups with aggregation enabled).