Fix directory for formal.

Sby formal would fail before because directory was improperly formed.

Hm we check that on CI, do you have an unusual environment? No problem merging this, I'm just curious whether this hides a deeper issue.

Hello WQ, Yehowshua from LibreSOC.
I have a Mac, and four other LS devs have Linux machines
from Ubuntu, Debian, to Arch.
I think we all had the same issue and had manually been applying
the patch for a few months now.

I can give you a gist test case where it failed for me if that helps.

Are you just unable to run nMigen tests? Or were you using nmigen.test.utils in your own code?

OK so here's a toy file test.py
python3 test.py
FileNotFoundError: [Errno 2] No such file or directory: '': ''

----------------------------------------------------------------------
Ran 1 test in 0.012s

FAILED (errors=1)

"""
formal verification of adder.
A.K.A, we mathematically prove the adder
works.

We do this for 16 bits.
"""
from nmigen import (Module, Signal, Elaboratable, Mux, Cat, Repl,
                    signed)
from nmigen.asserts import Assert, AnyConst, Assume, Cover
from nmigen.test.utils import FHDLTestCase
from primitives.adder3 import Adder3
import unittest

class Adder3(Elaboratable):
    def __init__(self, WIDTH):
        self.PARAMS = {"WIDTH":WIDTH}

        # inputs
        self.A_in = Signal(signed(WIDTH))
        self.B_in = Signal(signed(WIDTH))
        self.C_in = Signal(signed(WIDTH))

        # outputs
        self.C_out = Signal(signed(WIDTH))

    def elaborate(self, platform):
        m = Module()
        m.d.comb += self.C_out.eq(
            self.A_in + self.B_in + self.C_in
        )
        return m

    def ports(self):
        return [self.A_in,
                self.B_in,
                self.C_in,
                self.C_out]

class Driver(Elaboratable):
    def __init__(self):
        # no additional signals needed
        pass

    def elaborate(self, platform):
        m = Module()
        m.submodules.adder3 = adder = Adder3(WIDTH=16)

        m.d.comb += [
            adder.A_in.eq(AnyConst(16)),
            adder.B_in.eq(AnyConst(16)),
            adder.C_in.eq(AnyConst(16))
            ]

        m.d.comb += Assert(adder.C_out == adder.A_in +
            adder.B_in + adder.C_in
            )

        return m

class TestAdder3(FHDLTestCase):

    def test_formal(self):
        module = Driver()
        self.assertFormal(module, mode="bmc", depth=2)
        self.assertFormal(module, mode="cover", depth=2)

if __name__ == "__main__":
    unittest.main()

Are you just unable to run nMigen tests? Or were you using nmigen.test.utils in your own code?

Only formal tests derived from the FHDLTestCase class fail.
Regular pysim is fine - if that's what you're referring to.

Its quite possible this isn't the way formal was meant to be done in nMigen(referring to the example toy code from above)?

Right so everything under nmigen.test was never intended as a public API, and in particular FHDLTestCase is an internal class that I didn't realize anyone uses. I've removed tests from the PyPI packages in commit 9c80c32c306c4cd9483821e3503141111ed7ffde to make it harder to accidentally depend on them.

If you find FHDLTestCase useful please copy it into your code because it was just a quick hack I threw together in a hour as a proof of concept and it's really not intended to have any sort of stability or anything.

Oh! ok - so how are we supposed to do formal with nMigen haha.
I didn't see an official example

There isn't an official example. nMigen has basic support for formal verification but (unlike for synthesis) it does not yet provide an out-of-box way to run sby and friends, so you're supposed to do it yourself. This will improve of course.

This makes sense. Well, we do have several hundred lines of proof written using FHDLTestCase. I think that provides some weight to its utility.
Given that only one line needs to be fixed, do you think a merge is still possible?

Given that only one line needs to be fixed, do you think a merge is still possible?

Please copy the implementation of FHDLTestCase into your own code. It is not a public API, I will change it in the future without warning, and it will not be present in the next release. Having your own implementation also lets you fix any bugs you encounter, or, for example, use different solver engines.

Ok then. Will do.

We've actually discussed this with lkcl a few days ago. There is a certain hazard in learning something by reading its source code, namely that you might not be able to guess the intent correctly, and then you'll be unpleasantly surprised by upstream changes. This is the number one reason why documentation is top priority.

Right. That's why we need first party documentation. nMigen is a good and useful tool none the less.

Yep. I'm working on documentation--take a look at the doc branch. It's pretty unfinished though at the moment and not very usable yet.

Just now seeing this. Good deal.

I do wonder if we copy the FHDLTestcase class, would that copy break as nmigen progresses. That is, does it depend on non-public components of nMigen?

require_tool("sby") is also a part of the private API but you can just replace that with "sby". The rest only uses public APIs. Oh and please ditch assertRaises, assertRaisesRegex and assertWarns, the reason those methods exist is because I didn't read the unittest docs...

I assume you won't need assertRepr either but that one is fine.

Will do.
Thanks!


Use Bazel to build/test/release

Apart from goodness that Bazel provides, the motivation is to be able to use code generation via special rules (this is a Bazel term) from Kubernetes so that we don't have to check in generated code. Namely client and deep copy code. This is the direction Kubernetes is going and we should follow. I'm talking both about not checking in generated code and using Bazel.
I think we will be able to use generators once we are on 1.8 machinery.

All BUILD.bazel files are autogenerated, however some of them have been modified - mostly added things. See comments.


New tag or release?

I'd like to use a newer version of FreeRDP in NixOS, but I don't feel comfortable pinning the package to a random git revision of FreeRDP. Is there any chance that FreeRDP would tag a new beta soon? It looks like the most recent relevant tag is from Sept 2014.
Apologies if I've missed a discussion about how releases/tags are handled, I did look around.

@colemickens please have a look to #2678 or #2839. As described we are working on getting everything ready for 2.0 but as resources are rare there is no fixed schedule.


feat: New Functionalities

closes #12
I wanted to bypass geo types by making it String on the rust side to store the geom from SQL as a string. I've also added new features to integrate my project more.
Added:

Rust Enum creation based on SQL Enum types
Optional --serde flag if you wanna derive structs/enums with serde
Optional --datetime-lib to select time or chrono crate to use. defaults to chrono

Fixed:

If the column name is type, it's a reserved keyword in Rust. So, I created a helper function rust_type_fix. (naming could be better)

Notes:

I haven't try the migrate command yet, I only needed generate command

Appreciate the work so far!
Thanks for doing this, I know @yellowHatpro will appreciate the enum generation!

With this library, we could create many more generators for other things as well. For example, I'm working on creating redis json schemas in here: https://github.com/R3-Lab/sql-gen/commit/bdba71589372e33dda8ef478f9667cf96de9fa75. But Since we only focus only on the rust types and helpers for SQL, Redis may not have life in here :) lmk what you think

Appreciate the work so far! Thanks for doing this, I know @yellowHatpro will appreciate the enum generation!

Thanks a lot for this. I even had a column name type in one of the tables, and I had to make it work by renaming it to #type.
The new features will definitely be helpful 🤩🤩

With this library, we could create many more generators for other things as well. For example, I'm working on creating redis json schemas in here: https://github.com/R3-Lab/sql-gen/commit/bdba71589372e33dda8ef478f9667cf96de9fa75. But Since we only focus only on the rust types and helpers for SQL, Redis may not have life in here :) lmk what you think

Yeah I think my intention is to maybe expand to support other DBs in future but it probably still would be SQL.
If you split out the Redis part v. happy to mention and link to it in README :)


Switching from Difference between dates to Add or subtract dates ignores the first date field

Describe the bug
The date fields for the two date manipulation systems are treated independently (both apparently seeded w/ "today")
Steps To Reproduce
Step 1: (3/10/2019 5:53:03 PM) User left click on "Calculator (window)" in "Cal"
Step 2: (3/10/2019 5:53:04 PM) User left click on "Open Navigation (button)" in "Cal"
Step 3: (3/10/2019 5:53:05 PM) User left click on "Date Calculation Calculator (list item)" in "Cal"
Step 4: (3/10/2019 5:53:07 PM) User left click on "From (calendar date picker)" in "Cal"
Step 5: (3/10/2019 5:53:09 PM) User left click on "14 (data item)" in "Cal"
Step 6: (3/10/2019 5:53:11 PM) User left click on "To (calendar date picker)" in "Cal"
Step 7: (3/10/2019 5:53:12 PM) User left click on "20 (data item)" in "Cal"
Step 8: (3/10/2019 5:53:15 PM) User left click on "Difference 6 days (text)" in "Cal"
Step 9: (3/10/2019 5:53:17 PM) User left click on "Calculation mode (combo box)" in "Cal"
Step 10: (3/10/2019 5:53:19 PM) User left click on "Add or subtract days (text)" in "Cal"
Step 11: (3/10/2019 5:53:21 PM) User left click on "March 10, 2019 (text)" in "Cal"
Expected behavior
The date in the first field of Difference between dates / Add or subtract dates should be carried over when switching between the two.
Screenshots

Step 8:

Step 11:

Device and Application Information (please complete the following information):

OS Build: 10.0.18351.0
Architecture: X64
Application Version: 10.1812.10048.0

Additional context

I understand that this is just the way it is, but when using Converter and changing the first drop down, it doesn't forget the user's selected value.

It's a great idea!

Thanks for the report! I agree that this value should not reset when switching between the two date calculation modes.

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.


webpack doesn't recompile changes if you make a style change

i'm not sure if this is an issue with the loader or my whole setup. when watching, if you do a code change that is only a style change, it does not recompile.
http://cl.ly/3K2j3C0j0D15
using<EMAIL_ADDRESS>loader setup is:
[
      // babel + jsx loader
      {
        test: /\.jsx?$/,
        exclude: /node_modules/,
        loaders: [
          'babel'
        ]
      },
      // eslint loader - needs to be below babel
      {
        test: /\.jsx?$/,
        exclude: /node_modules/,
        loader: 'eslint-loader'
      },
      // json loader
      {
        test: /\.json$/,
        loaders: [
          'json'
        ]
      },
      // sass loader
      {
        test: /\.scss$/,
        loader: ExtractTextPlugin.extract('style-loader', 'css-loader!sass-loader')
      },
      // css loader
      {
        test: /\.css$/,
        loader: ExtractTextPlugin.extract('style-loader', 'css-loader!postcss-loader')
      },
      // added specifically for svg images in css, this will inline them as base64 strings
      {
        test: /\.(svg)$/,
        loader: 'url-loader?limit=100000'
      }
    ],

has anyone else experienced this problem?

Nope. That's might be related to webpack caching system...
Why do you defined 2 sections for eslint and babel?

yeah i'm thinking the same. webpack might be caching too inteligently
i copied your readme https://github.com/MoOx/eslint-loader#usage lol does having two sections matter?

Might affect webpack caching (no idea lol). Can you try with one section?
{
        test: /\.jsx?$/,
        exclude: /node_modules/,
        loaders: [
          'babel-loader',
          'eslint-loader',
        ]
      },

Maybe because of the ExtractTextPlugin?

@jonathanong did you still have the issue?

i don't know because i just removed this library

hum ok...

FWIW, my guess is Babel is caching based on AST, which doesn't change when you make a stylistic change.


Update package number

Pull Request Test Coverage Report for Build 5414

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 5403:
0.0%

Covered Lines:
993

Relevant Lines:
993

💛  - Coveralls


Scrollbar for easier scrolling

I would love to have an scrollbar to easily scroll longer distances in the view. Currently it's only possible to use the scroll of the mouse.

Yeah, I am using GNOME and in GNOME there is a scrollbar, so I didn't know that is missing O:-)
Scrollbar will be added in next version.


Restore p2pk address type in rpc

This PR enables old behaviour of displaying p2pk address format in rpc, i.e. before bitcoin v19.0.1 release.
Related to https://github.com/3xplcom/Core/pull/65

Closing this PR as I've checked out from the v26.0 but the master branch is far away. Only latest 2 commits are related to my PR.
It would be better to make a flag like -deprecatedp2pk=1 to enable the behaviour described in the PR.


Wonderful Chartreuse Tortoise

Hotspot Name
Wonderful Chartreuse Tortoise
Hotspot b58 Address
11dYbwaSPpYPjpLbE6fwMcR7YceWMpFy9MVXmdbziVko85PVj4z
Discord Handle
没有反应
Hotspot Manufacturer
山猫
Removal Reason
我把热点设置在住处高层建筑的窗边，希望能从黑名单中删除
Modifications
No
Extra forwarders
No
Extra antennas
No
Additional Information

We have taken into account this removal request in the next iteration of the denylist. It may take some time before it's processed. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.

非常感谢


Is there a way to remove headers once created or even update them?

I would like to update my header but there are a lot of source files.

After running sbt clean, the headers were regenerated.


Add option to show config diffs in a simple format

This patch adds an option --oneline to mujin_controllerclientpy_applyconfig.py which changes the diff formatting to simple one. This option makes it easier to work with many controllers or many changes in a conf template.
Example with --oneline:
[MOD] parameters.parameterA.[2]=-100 (old: -120)
[MOD] parameters.parameterB.[2]=250.0 (old: 100.0)

Same diff without --oneline:
--- /tmp/old-config-m5Y2FE.json 2020-04-22 22:40:10.416135387 +0900
+++ /tmp/new-config-lnOvdS.json 2020-04-22 22:40:10.424135377 +0900
@@ -87,11 +87,11 @@
       "use": true
     },
     "parameterA": [
       0,
       0,
-      -120
+      -100
     ],
     "blah": false,
     "blahblah": "blah",
     "blahblahblah": [
       0,
@@ -146,11 +146,11 @@
     "blah": 2000,
     "blahblah": 2000,
     "parameterB": [
       0.0,
       0.0,
-      100.0
+      250.0
     ],
     "blahblahblah": 2500,
     "a": -1,
     "b": 5,
     "c": "all",

This patch also adds an option --dryrun which just shows diffs without applying the changes.

sure, thanks~


Simplified Shrink in ArbitraryTuple

This is just another step in simplifying the shrink logic of ArbitraryTuple after 5467ce8.
By the way, is anyone brave enough to put some sanity in the types of this class? Typescript supports variadic tuple types ever since v4.0, but we are clearly not using them correctly, and so we have a lot of unsafe casting going around.

We should have an issue for fixing the types in this class. Otherwise, LGTM.


CVSSv3 Temporal score

Hello,
Are you interested in the Temporal Score parsing and calculation? I'm asking because I have an internal fork of your repo and I needed that so i thought it would be nice to propose the patch upstream.
Regards,

Hi, luxifer.
Thank you for your advice.  If you give me a patch code or PR, merge it.

I'll take time to subimt a PR this week.

many many thanks @luxifer and merged your code.


Unable to use both aws iot sdk and aws sdk together

Describe the bug
I'm having difficulties using the mentioned sdks together.

I'm unable to build the aws sdk using MinGW (As far as I know, MinGW is not supported yet). This is causing us difficulties since we're working on a big database that is all compiled using MinGW. These are some of the errors when building with CMake:

/aws-sdk-cpp/crt/aws-crt-cpp/crt/aws-c-common/include/aws/common/array_list.inl:99:48: error: unknown conversion type character 'z' in format [-Werror=format=]
aws-sdk/aws-sdk-cpp/crt/aws-crt-cpp/crt/aws-c-common/include/aws/common/array_list.inl:99:85: error: format '%p' expects argument of type 'void*', but argument 4 has type 'long long unsigned int' [-Werror=format=]
/aws-sdk-cpp/crt/aws-crt-cpp/crt/aws-c-common/include/aws/common/array_list.inl:99:9: error: too many arguments for format [-Werror=format-extra-args]
I got my MinGW version from https://winlibs.com/. Not sure if using another version might help.

As a workaround, I tried to build both skds using Visual Studio toolset. This worked, however there were linking errors. With a bit of research, I found out that I had to build the skds as shared libraries. This didn't work out in the aws iot sdk, causing the following error: \aws-iot-sdk\aws-iot-device-sdk-cpp-v2\jobs\include\aws/iotjobs/JobStatus.h(61,25): err or C2059: Syntaxfehler: "__declspec(dllexport)" [C:\Users\KONVOI04\CMAKE_PACKAGES\aws-iot-sdk\build\jobs\IotJobs-cpp.vc xproj]

The optimal solution would be to build the aws sdk using MinGW tools. I appreciate the work you are putting into this project, but not being able to use MinGW tools to compile the sdk is causing us a lot of trouble and headache. I know from going through the issues that this feature is demanded by many developers.
I'd appreciate any help from you.
Expected Behavior
Both SDKs can be used together
Current Behavior
see above
Reproduction Steps
Command for building with Visual Studio:
git clone --recursive https://github.com/aws/aws-iot-device-sdk-cpp-v2.git
mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=%installDir% -DBUILD_SHARED_LIBS=ON -DBUILD_DEPS=ON ../aws-iot-device-sdk-cpp-v2
cmake --build . --target install

Commands for building with MinGW:
    git clone --recursive https://github.com/aws/aws-iot-device-sdk-cpp-v2.git
    mkdir build
    cd build
    cmake -DCMAKE_INSTALL_PREFIX=%installDir% -DCMAKE_CXX_FLAGS="-w -Wa,-mbig-obj" -G "MinGW Makefiles" ..
    cmake --build . --target install

Possible Solution
No response
Additional Information/Context
No response
AWS CPP SDK version used
latest
Compiler and Version used
gcc (MinGW-W64 x86_64-ucrt-posix-seh) 11.3.0 / clang version 14.0.1
Operating System and version
Windows 11

Thanks for bringing this up. Currently the aws-cpp_sdk and aws-iot-device-sdk-cpp-v2 use different versions of the common runtime (crt) and might be causing some of your issues. This prevents you from using shared libraries when building them, but this is something that we are looking at resolving.
Also are most of your problems from installing the aws-sdk-cpp or aws-iot-device-sdk-cpp-v2? As it looks like the IoT sdk is causing you more problems and this issue was opened on the non-IoT sdk


Update alleycats-core, cats-core, cats-free to 2.7.0

Updates

org.typelevel:alleycats-core
org.typelevel:cats-core
org.typelevel:cats-free

from 2.6.1 to 2.7.0.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: library-update, early-semver-minor, semver-spec-minor

[info] - LogTree and tethys builder results are consistent *** FAILED ***
[info]   "{"aaaa":[[{"field1":"lol","field2":2},{"field1":"kek","field2":-1}]]}" did not equal "{"aaaa":[[null,null]]}" (LogTreeSuite.scala:23)
[info]   Analysis:
[info]   "{"aaaa":[[{"field1":"lol","field2":2},{"field1":"kek","field2":-1}]]}" -> "{"aaaa":[[null,null]]}"

This test fails with the new cats.

This line causes regression with cats 2.7.0:
https://github.com/tofu-tf/tofu/blob/ed141b87420801ab63eb29d27c94ef3e54c10189/modules/logging/structured/src/main/scala/tofu/logging/LogTree.scala#L66
Change to traverse fixes the test. Revert to cats 2.6.1 fixes the test.
Probably the test fails due to changes in https://github.com/typelevel/cats/pull/3960

The root cause of the failure is that Eval is misused for side-effects, while it must not.
The new stacksafe impl of traverse_ uses this function internally:
https://github.com/typelevel/cats/blob/358a06712aa8811d8c0bf6b5d107cd125789e94c/core/src/main/scala/cats/Eval.scala#L377
It discards the whole computation along with its side effects.


👨💻☎ WinUI Community Call: March 16, 2022

This live event has now ended, but you can view the recording on YouTube at the link below. If you didn't get your question answered, feel free to open it up as a question on this repo. Thanks all for joining!
https://youtu.be/fRpXbB8WUko
Details
Date: March 16, 2022
Time: 16:00-17:00 UTC (9:00-10:00am Pacific)
Anyone and everyone is welcome - no pre-registration is required.
This will be an informal interactive live stream directly with members of our engineering team.
Format
The community call is a call among the WinUI team that is live-streamed onto YouTube. We present on new updates, share information, welcome guests, and answer your questions. In this month's call, we'll be sharing the latest info around the WinUI & Windows App SDK roadmap and releases and give an overview of the Windows App SDK Samples repository.
Call Summary

Updated Windows App SDK 1.0 release cadence expectations, docs to be updated shortly.
Windows App SDK 1.0.1 coming very soon with critical bug fixes & multi-window support!
Windows App SDK 0.8.7 coming soon with several C#/.NET Performance improvements following up from 0.8.7-preview1 released in February.
Overview of Windows App SDK Samples repo & demo of the Windowing sample in WinUI. Video available.
Published Windows App SDK roadmap with more confident information about the features coming for WinUI 3 in Windows App SDK 1.1.
Invitation to send us your comments about the community call, I'd love to hear what we should continue/stop doing in the calls. E.g. do you like this call summary? 😊
Q&A

Q&A Code of Conduct

To help ensure Q&A remains beneficial for the majority of the call's developer audience, please consider whether your question could be framed so that it might be more broadly relevant to our larger developer audience by ensuring it is reasonably concise, broadly beneficial, well-suited for the fast-paced live Q&A format, or able to spark open ended discussion.
Please understand some questions are not well-suited for the fast-paced live Q&A format and should be filed as standalone Discussion or Question issues where they can be most appropriately handled. Excluding presentation topic requests, this generally includes requests for dedicated follow-ups or technically complex questions that require investigative time or expertise not included in this month's guest list.

Leave us your questions in the comments on this issue or live in the YouTube chat during the stream!

Can you update us on the windowing API's that are being developed, is there an issue we can follow?

Could you please address the issue with the touch keyboard not displaying when text input controls get focus? (https://github.com/microsoft/microsoft-ui-xaml/issues/6291)

This might be WAY out of the scope of what can be answered in the community call, but this has been worrying me. New inbox apps on Windows 11 and many other cruical areas of the shell have been undergoing large overhauls from Win32/GDI to UWP Xaml. If these core components of the operating system are only now being migrated, and UWP is already on life support, how is support expected to be maintained for these areas?

Not sure if this is the right place to ask this but will comctl32/uxtheme GDI controls from classic windows desktop applications ever have a dark mode to match the themes that WinUI/XAML apps have?

We need to hear what the actual commitment of Microsoft on Windows App SDK and WinUI 3.0 is.

Are there Microsoft Windows applications (like, Notepad) developed in WinUI 3?
What is Microsoft's actual commitment, when news has it that a project like One Outlook (Project Monarch) is reportedly built on web technologies and not native? If Microsoft are not basing their core products on WinUI, why should developers do so?
Looking at the number of commits and active contributors, it looks like WinUI 3 is being developed by a handful of people only, which makes it hard to believe that WinUI 3 is really the next UI platform. Looks like more of a hobbyist project.

This year I will need to make a decision on how to modernize a WPF app in our core product. How can I be sure WinUI 3 is the way to go?

Please weake up Microsoft and add .NET 7/8 support to UWP!
https://developercommunity.visualstudio.com/t/Add-NET-678-support-to-UWP/1596483?space=61

I think it's worth adding the main docs page for WinUI to the list of places that need to get updated for each community call:

😉Long time no see. Would you release a 1.1preview build or 1.0servicing at this time point? After silence for several months, I think most of developers are thirst for new releases. At least, please disclose more information about your recent progress! As promised WinUI3 is going to be open-source, currently it's too mysterious for us however.

As others write, please in this community call, focus on what Microsoft wants with WinUI 3.
I think it is safe to say that the community is in doubt whether Microsoft is committed to delivering WinUI 3 for professional use.
Example of an issue regarding whether WinUI can be used/is used.
Real projects with WinUI
Since there is 2500 open issues in here there is plenty of examples to pick from, but one example is: Modern WinUI Datagrid This has been open for 2,5 years and yet such a control is still not a direct part of WinUI 3.
It all comes down to resources and what resources are Microsoft putting into WinUI 3? Or are those resources already being scaled back?
To be honest, WinUI was/is very exciting, and looked to be something that could finally replace WPF. But it starts feeling like Silverlight or UWP all over again. So please bring us some hope :-)

Hope alone doesn't cut it any longer:

Rewrite Win32 into Windows 8 WinRT model, using three API models across mobile, tablet and desktop
Rewrite Windows 8 WinRT into Windows 8.1 UAP model, using two API models across mobile/tablet and desktop
Rewrite Windows 8.1 UAP into Windows 10 UWP model, using one Core model across mobile, table, desktop, HoloLens and XBox
Merge classical Win32 with Windows 10 UWP model via XAML Islands
Rewrite Windows 10 UWP back into Win32 with WinUI 3.0 model, only for desktop, leaving behind HoloLens/XBox on their own
Rewrite Windows 10 UWP back into Win32/DirectX in what concers games targeting HoloLens/XBox as respecitve teams decide to refocus on Win32

Bugs accumulate, less capabable tooling (C++/WinRT vs C++/CX, no designer), lots of missing APIs, many basic stuff requires additional work on our side to write boilerplate on our side for what is platform code on UWP side, CsWinRT versus plain Forms/WPF, and we get asked to rewrite code yet again.
So if you want people like myself that decided 6 years of this is enough, actually provide facts how this is going to happen, without rewrites of any sort.
I really wanted .NET Native and C++/CX alongside UWP to be the future, pity it ended up not being so and now everyone is shipping Electron apps instead.

Can you address how WinUI 2 is playing out against WinUI 3? When does WinUI 2 go into maintenance mode?

Recently, the team has mentioned that they would like to concentrate on improving the quality and address fundamental infrastructure pieces. I am wondering if it would mean addressing an issue about loading Xaml controls using reflection from assemblies not part of the main app? This would enable many of us to start writing applications with plug-in architecture. Please see #6299 for more details. Can the team say if this issue comes under core infrastructure? Any hope of getting it fixed this year?

Can we make the Xaml compiler a standalone executable, or even as a standalone/redistributeable DLL.
This is one missing feature if  we want to use easily cmake integration.
Also it should be able work in interpreter mode so we can integrate it with script languages and script plug-in architecture as mentioned by @harvinders  above.

I mentioned that in Reunion roadmap updated today, you say you will increase usage of WinUI 3 in the Windows OS.
Please hurry up. The first release of Windows 11 looks very incomplete, as the same of WindowsAppSDK 1.0.
I can understand you are getting rid of design debt of Windows 8, which coupled too much things. But the transition period is too long. It's 10 years from Windows 8 release now.

When 1.0 or 1.1 gives us more freedom to deploy non MSIX packages, are you going to provide WiX (Windows Installer XML Toolkit) with samples and tutorials?

@tinmac

Can you update us on the windowing API's that are being developed, is there an issue we can follow?

Hi, @tinmac! These can be found on the 1.1 WinAppSDK Roadmap. 🙂

Thank you for addressing a rough timeframe for media controls on WinUI3. Sounds like Ryan Demopoulos says he's confident it should arrive with SDK 1.2 (2H'22?). This gives developers like me a clear direction for the coming year on how I want to approach projects related to those features, and which frameworks to use.
For anyone else interested in what was said, fast forward the stream to approx "-38:25" timeframe.

I literally can't watch these community calls anymore, it just makes me sad :((
I was hoping that open sourcing WinUI can solve some of the 2.5k issues we have but to me it's starting to look like a lost cause as it's probably only going to increase the issues we have.  Sad that we still have to wait more years for open sourced WinUI.
The whole time I'm thinking MS does not have the resources to fix this mess. Too much work and not enough resources. Goes beyond my comprehension why an executive can't fix the overall state of affairs and I mean no disrespect to MS employees here.


Workaround for static libraries breaks go get -u

After<PHONE_NUMBER>a1fc8d043e301522c565a0b8b56480 it's no longer possible to update all dependencies in a project that use go-sdl2.
Normally this would be done by running go get -u ./..., but after the dummy package was added the go command fails:
go: malformed module path "github.com/veandco/go-sdl2/.go-sdl2-libs": leading dot in path element
go: malformed module path "github.com/veandco/go-sdl2/.go-sdl2-libs/include/SDL2": leading dot in path element

Go version: 1.20.2
Go-SDL2 version: 0.4.33
OS: macos
Architecture: arm64

Hi @ptxmac, thanks for reporting this issue! Sorry for taking so long to reply as I'm out of town. I will try to implement a solution around end of next week once I'm back, perhaps by renaming the directories. Will post an update here then!

Any update? I think it would be fine if we just replace the . with _

Hi @ptxmac, sorry I was actually just starting to work on this! Could you let me know how I can reproduce the issue? I might just end up following your suggestion in order to fix it.

Sure, create a new project that use go modules. E.g.
main.go:
package main

import "github.com/veandco/go-sdl2/sdl"

func main() {
	sdl.GetRevision()
}

and go.mod:
module github.com/ptxmac/go-sdl2-get-bug

go 1.20

require github.com/veandco/go-sdl2 v0.4.33

Then run go get -u

That's strange.. go get -u succeeded for me using the same configuration as yours. Is there something else that I should do?

Perhaps you're using a different version of go?
This bug appears on go1.20
I've created a quick sample project here: https://github.com/ptxmac/go-sdl2-get-bug

My Go version is go version go1.20.2 darwin/arm64. I cloned the sample project and ran go get -u there as well but it didn't produce any error.

Very strange, I'm using go version go1.20.3 darwin/arm64 But I also saw it on v1.20.2
Maybe if you use go get -u ./... instead?

I tried with go get -u ./... but the error doesn't show up. I will keep trying to see if I can reproduce it.

Very strange... perhaps try removing go-sdl from the mod cache in go env GOMODCACHE

It still runs fine...I also tried with a new macOS user with an empty home directory.

So apparently it's something with my setup - I just tried an empty user, and there it works fine... 🙃

Oh... if you happen to find the cause, please let me know! I would be interested to know why that error happened and perhaps add that information to the README.

I figured it out!
I had to step through go get in a debugger, but finally discovered the difference. I have GONOPROXY configured!
From my understanding the go get command will look up modules on a proxy server to avoid putting too much load on the repository. If GONOPROXY is set it will go directly to the repository instead.
I guess the proxy server ignores files starting with a dot when it indexes a repository.
You can test it out with GONOPROXY=test go get -u

It also happens if GONOSUMDB is set. BAsically if you have a project that depends on private packages, then it will break

Hi @ptxmac, thank you very much for finding the way to reproduce it! I renamed the .go-sdl2-libs directory to _libs and pushed that change to the test branch. It seems to work for me so let me know if it works for you too. I will tag a new version once it's confirmed to fix it 🙂

Works perfect for me too!

Okay, I have pushed the tag v0.4.34!


VSCode Extensions are not getting installed in the Dev Container

Describe the bug
In the .devcontainers/devcontainer.json file, there are multiple extensions specified but no extension is getting installed in the Dev container VSCode. This issue occurred because of VSCode changed the way extensions get loaded in the .devcontainers/devcontainer.json file. Currently, extensions are specified in the configuration as follows:
"customizations": {
     "extensions": [
               . . . list of extensions here . . .
	]
},

However, the template should be as follows:
"customizations": {
	"vscode": {
		"extensions": [
                            . . . list of extensions here . . .
		]
	},
},

To Reproduce
Steps to reproduce the behavior:

Clone the repository.
Open the folder in Vscode.
Click "Reopen in Container" popup appeared in Vscode.
After the dev container is setup, click extensions icon in VSCode.

Expected behavior
The specified extensions should show up in dev container installed extensions.
Observed behavior
No extension is showing up in the installed extensions.

Verified! The extensions are now showing up in the installed section of dev container.


Create different framework files for iOS Extension

There is basically a problem where building the frameworks means that the iOS Extension framework get's over-written by the iOS (app) framework.

I thought I could fix this by just changing the product name. But that doesn't work because then the module name also gets changed.
If I explicitly set the module name, then I get a build error (although it says warning)

warning: PRODUCT_MODULE_NAME may not be overridden for framework target 'Operations-iOS-Extension'

I've also tried overriding the WRAPPER_EXTENSION to be extension.framework but this doesn't work either.
Next ideas:

Rename the files via a script as the last build phase? This is the most pragmatic idea so I'll try it next, the possible problem I see is that the unit tests won't be able to find the bundle? Could also just delete the test target for the extension scheme - all of the code is tested in the main app framework target.

Probably the "correct" way to handle this is to use a module map with an umbrella module called Operations and then internal modules for the app level stuff. So that
import Operations // imports the extension api compatible stuff
import Operations.Features // ? imports the non-extension api compatible stuff, not available in extensions.

Anyone got any bright ideas?

Current coverage is 0.00%

Merging #114 into development will decrease coverage by -63.88% as of 498b5e2

No diff could be generated. No reports for #114 found.
Review entire Coverage Diff as of 498b5e2

Powered by Codecov. Updated on successful CI builds.

Okay, at the moment, on this branch there are two Xcode projects, one for normal frameworks, and the other for extension API only frameworks. However, waiting for this PR to merge before Carthage will handle it: https://github.com/Carthage/Carthage/pull/892
I'm gonna hold off merging this until that change makes it through.

Okay, I'm actually going to merge this - as it's got significant changes which are also in CI (just the script names).I'll just make sure that it doesn't break normal Carthage usage...


[enchancement] Use importlib for getting staticfiles

Coverage increased (+0.004%) to 99.399% when pulling 376a95a7713471c115584e48edb538cba3bd418d on atb00ker:master into 946b21d17300b25e5e286b3d5a062f849da4c913 on openwisp:master.

Coverage increased (+0.004%) to 99.399% when pulling 376a95a7713471c115584e48edb538cba3bd418d on atb00ker:master into 946b21d17300b25e5e286b3d5a062f849da4c913 on openwisp:master.


[LIBCLOUD-783] API 2.1 support for dimension data driver

Move image functions to the 2.1 API namespace
Update existing calls to 2.1
Update test fixtures with response changes where appropriate
Image listing and customer image listing
Allow user to configure CPU and RAM specifications up front

Completed.

famous last words. I've CR'ed this but I'm sure it could do with a second pair of eyes. @Kami @runseb or @erjohnso would be appreciated.

finished final tests against prod instances and AU and NA APIs which were both updated yesterday. merging


FRL_INSTANCE_MESH is no longer used in the simulator and should be deprecated.

Problem
FRL_INSTANCE_MESH is for the initial scan of the apartments, and it is replaced by mesh_semantic.ply in the public released replica dataset. Such model can be loaded using our generic instance mesh loader.
Thus, it should be deprecated.
More details: #190
Search
FRL_INSTANCE_MESH

Fixed by #191


django-material-admin having trouble with Django==3.2 release

It seems that django-material-admin is having trouble with Django==3.2 release
Error that I am receiving is as following:
/var/www/html/gesi/backend/src/gesi/settings.py changed, reloading.
Watching for file changes with StatReloader
Exception in thread django-main-thread:
Traceback (most recent call last):
  File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.6/threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "/var/www/html/gesi/backend/src/env/lib/python3.6/site-packages/django/utils/autoreload.py", line 64, in wrapper
    fn(*args, **kwargs)
  File "/var/www/html/gesi/backend/src/env/lib/python3.6/site-packages/django/core/management/commands/runserver.py", line 110, in inner_run
    autoreload.raise_last_exception()
  File "/var/www/html/gesi/backend/src/env/lib/python3.6/site-packages/django/utils/autoreload.py", line 87, in raise_last_exception
    raise _exception[1]
  File "/var/www/html/gesi/backend/src/env/lib/python3.6/site-packages/django/core/management/__init__.py", line 375, in execute
    autoreload.check_errors(django.setup)()
  File "/var/www/html/gesi/backend/src/env/lib/python3.6/site-packages/django/utils/autoreload.py", line 64, in wrapper
    fn(*args, **kwargs)
  File "/var/www/html/gesi/backend/src/env/lib/python3.6/site-packages/django/__init__.py", line 24, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/var/www/html/gesi/backend/src/env/lib/python3.6/site-packages/django/apps/registry.py", line 91, in populate
    app_config = AppConfig.create(entry)
  File "/var/www/html/gesi/backend/src/env/lib/python3.6/site-packages/django/apps/config.py", line 255, in create
    return app_config_class(app_name, app_module)
  File "/var/www/html/gesi/backend/src/env/lib/python3.6/site-packages/django/apps/config.py", line 39, in __init__
    "The app label '%s' is not a valid Python identifier." % self.label
django.core.exceptions.ImproperlyConfigured: The app label 'material.admin' is not a valid Python identifier.

Any reason why that is happening? Thank you in advance........

It's seems to be because of https://docs.djangoproject.com/en/3.2/releases/3.2/#automatic-appconfig-discovery .
The AppConfig.label shoudn't be materia.admin but some string which is a valid python identifier. When I tried to change it to admin, or simply comment it, another exception occured:
django.core.exceptions.ImproperlyConfigured: Application labels aren't unique, duplicates: admin

Which should to be material.admin.default

Hi @oberix, thanks for responding, you implying removing 'material.admin' from the settings?

Hi @Vulum, that of course would make your project run... but that's just "killing the patient to cure the disease"!
No, the issue here is in the AppConfig class of django-material-admin. I did just a few quick attempt to fix it but could only stumble in another (related?) problem. Sorry but I don't have the time and the urgency now to go deeper into this. Just thought that it would be a good pointer to someone more into the development of this app.

Appreciate your response @oberix

in progress, will be ready this week
https://github.com/MaistrenkoAnton/django-material-admin/pull/138

Hi @MaistrenkoAnton , truly appreciate your work and effort

I'm here for the same bug. It's a great work. Waiting forward to be fixed.

fixed since v1.8.3


feat: when the user's bot code crashes, we should display the crash log on the UI to let the user debug it

Currently, if the user's bot code crashes, the user won't see why or where on the UI.
We should:

capture the crash log
send it back to the UI with the bot state

Dupe of #66


Specified code cause crash.

I had reproduced this problem at both macOS and windows(without any plugin).

Create a new HTML file
Type or copy code into workspace

<!DOCTYPE html>
<html content="text/html; charset=UTF-8">
<style>
.
</style>
</head>
</html>
<script>
        d.addData([
                true, // false则自定删除原有数据，队头插入删队尾，队尾插入删队头
        ]);
</script>

It seems that vscode consider javascript comments as code hints?
idkw. Using English instead of Chinese it will lag as well when type in

How is it going on?

@lsvih In the issue title, you say it causes a 'crash'. I can't see that. I see that the syntax highlighting is confused because of the . in the style tag.
Is that the issue?

crash at VSCode June release, it works fine now.

@aeschli It has been fixed，I can't reproduce it now. Thank you for your attention ; )


Update cats-effect-laws, cats-effect-std to 3.5.2

About this PR
📦 Updates

org.typelevel:cats-effect-laws
org.typelevel:cats-effect-std

from 3.3.14 to 3.5.2
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.typelevel" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #701.


Make file names consistent

How do you feel about this convention:

If the file exports a class, the file's name should be Capitalized and camelCased like the class. Example: class App is in App.js
If the file exports a function, it should not be capitalized but should be camelCased like that function. Example: module.exports = function wowMan() { is in wowMan.js

???

This suits me. 👍


Added lecture 41. Teaching the learner to have a radio button checked for guarantee of account type.

Checklist:

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

This does not have an associated issue. Can you explain why you think these changes are needed?

The issue I have tried to solve is the following
https://github.com/freeCodeCamp/freeCodeCamp/issues/47456

The issue I have tried to solve is the following
#47456

You should add the issue to the PR description. Also, reading the contribution guidelines (the box you checked) will tell you how to title the PR.

I am extremely sorry. I will re-do the entire process.


Brian/add javadoc to interfaces

Pull Request Test Coverage Report for Build 2484

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 2476:
0.0%

Covered Lines:
581

Relevant Lines:
581

💛  - Coveralls


Update dotnet 8

PR Details
Updated Stride projects to .NET 8.
Description

changed any references from .NET 6 to .NET 8 in all csproj files.
Added unsafe keyword to OpenVR due to changes in C# 11 regarding ref.
Added #pragma warning disable SYSLIB0011 to Binary formatter due to security error found from dotnet 7 (may need to be looked into further)
worked off of https://github.com/stride3d/stride/pull/1593

Marked draft as the CPP projects cant seem to be found by the dotnet build command.
Related Issue

Motivation and Context

Types of changes

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

Checklist

[x] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

 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.

Just wondering for the future updates, would it make sense to have this net6.0-windows7.0 as a parameter so it can be updated just in one place?

The reason these were done manually was because I was modifying threw a find and replace all in VSCode. all of these are outside the scope of the Stride.sln file where the references are managed by a couple of variables inside StrideEditorTargetFramework and StrideFrameworkWindows for net8.0-windows7.0.
Just noting this for myself in case I dont update this today. I will try to take a look later to see if those can be referenced outside of the base Stride solution.

Why stride use windows7.0 TFM?

I guess Stride.Core.AssemblyProcessor also should be updated and recompiled to net8.0 in deps\AssemblyProcessor.

I guess Stride.Core.AssemblyProcessor also should be updated and recompiled to net8.0 in deps\AssemblyProcessor.

Good catch, should be fixed.

I guess Stride.Core.AssemblyProcessor also should be updated and recompiled to net8.0 in deps\AssemblyProcessor.

Good catch, should be fixed.

But not so simple
https://github.com/stride3d/stride/pull/1840
AssemblyProcessor used in build pipeline with netstandard2.0 TF and as binary dependency.
I'm not sure why exists net6.0 version, and for what it should be updated to net8.0.
Maybe we should leave only the netstandard2.0 version.
But for now you should recompile AssemblyProcessor and commit produced files. I guess.

AssemblyProcessor used in build pipeline with netstandard2.0 TF and as binary dependency. I'm not sure why exists net6.0 version, and for what it should be updated to net8.0. Maybe we should leave only the netstandard2.0 version.

The reason there's 2 variants is because dotnet build loads the newer version (which can use modern CLR features), while Visual Studio in some cases uses a legacy .NET Framework based MSBuild that can only load up to netstandard2.0 libraries. And we use the AssemblyProcessor for some MSBuild Task definition so it has to be loadable in its process - maybe a look needs to be have if that task could be removed.

Suggestion
As this PR already touches all .csproj files, wouldn't it make sense to also introduce Central Package Management with its Directory.Packages.props to manage all package versions in 1 file?
This way misaligned PackageReference Version attributes will be impossible within Stride's solution.
It's very well supported since .NET 7 (including tooling) and eases upgrading NuGet dependencies tremendously.

As this PR already touches all .csproj files, wouldn't it make sense to also introduce Central Package Management

I am a big fan of this, It simplifies version management a lot! We can define one property for the Silk.NET version and have it consistent everywhere.

I think the last suggestion left is the property centralization for version from Vaso, Warappa and Tebjan. Would it be possible to just use the existing properties or should there be a new one?
I also left the Compiler service alone as it was since there needs to be some extra work to move it away from standard2.0 as well.

I think the last suggestion left is the property centralization for version from Vaso, Warappa and Tebjan. Would it be possible to just use the existing properties or should there be a new one?
I also left the Compiler service alone as it was since there needs to be some extra work to move it away from standard2.0 as well.

you cant write roslyn in non netstandard2.0

Nice job, thanks again! I tried to run it and it worked fine. I have just commented on a few small details. One last thing to do is to update the prerequisite installer. I can do that part if you want.

No problem! I think I got everything you suggested done. I don't know what the prereq installer is or where it is? The only thing I see is a VS2019 and a DriectX installer.
If you want to do it then we could the the peas in a pod achievemnt in GitHub... wink wink. But I dont mind looking into it lol

@Doprez Currently we are using propertary installer : Advanced Installer 19.4 and prereq file is prerequisites.aip

Ah I see it now, thank you. should this not be downloading the SDK instead of the Runtime? or is this not for the GameStudio prereqs
    <ROW PrereqKey="FAC9C433D3044829E6669A2C6FF54E6" DisplayName=".NET Desktop Runtime 6.0.2 x64" VersionMin="6.0" SetupFileUrl="https://download.visualstudio.microsoft.com/download/pr/efa32b7a-6eec-4d97-9cdc-c7336a29a749/3df4296170397cf60884dae1be3d103b/windowsdesktop-runtime-6.0.2-win-x64.exe" Location="1" ExactSize="57296456" WinNTVersions="Windows 9x/ME/NT/2000/XP/Vista/Windows 7/Windows 8 x86/Windows 8.1 x86/Windows 10 x86" WinNT64Versions="Windows Vista x64, Windows Server 2008 x64, Windows 7 RTM x64, Windows Server 2008 R2 x64, Windows 8 x64, Windows Server 2012 x64, Windows 10 version 1507 x64, Windows 10 version 1511 x64" Operator="1" NoUiComLine="/q /norestart" Options="xy" MD5="ce032ed3b098ceb4054eaf9c9158e2f5" TargetName=".NET 6.0"/>

I have triggered some teamcity builds.
I think the OpenGL errors will be fixed once latest master is merged.
Not sure about the Android build issues though. Something might have changed in dotnet build system.

I have triggered some teamcity builds. I think the OpenGL errors will be fixed once latest master is merged. Not sure about the Android build issues though. Something might have changed in dotnet build system.

Updated with master so the opengl should hopefully work now. I can try later to build an android project when I have time to see if something changed.

Consider updating the README.md with the correct dependencies for building with .NET 8.

 And then force-push your branch.
master currently contains binary files where it shouldn't (they should have been added through git LFS).

I took the liberty to do the merge again properly.
Howvever I didn't have the permissions to push it to your repo.
You can reset on this branch: https://github.com/stride3d/stride/tree/update-dotnet-8
or this commit: https://github.com/stride3d/stride/commit/e1d97deaf5fb16658d5b4418f21bb80ddc763dc6

I have also added another commit which should hopefully fix android build


pypy-2.5.0

Please, add support of pypy 2.5.0

This one can be closed.  https://github.com/heroku/heroku-buildpack-python/blob/master/builds/runtimes/pypy-2.5.1


Show usage with API

Hi @pydanny,
I've been working on enhancing the documentation for this project and this issue seems to require examples that demonstrate how to use the refry decorator with API calls (i.e. REST requests). Specifically, I am thinking about scenarios where the retry logic is crucial for API interactions, such as handling rate limits or temporary server errors. Is this so? Any guidance or examples for this context are welcome.
Thank you for your assistance!

Apologies, I just saw this, it's been a busy couple of weeks.
Some scenarios I've encountered:

Need for both sequential, logarithmic, and exponential backoffs. We only have sequential now, but as I've seen that's not always the best way to handle issues. But neither are the other options
Documentation for jitter, which is a random amount of time added to each sequential increase, which aids in dealing with the thundering herds problem. We don't have that - yet.
Capturing and raising different types of server errors

Need for both sequential, logarithmic, and exponential backoffs. We only have sequential now, but as I've seen that's not always the best way to handle issues. But neither are the other options
Documentation for jitter, which is a random amount of time added to each sequential increase, which aids in dealing with the thundering herds problem. We don't have that - yet.

Done and done on pull request #38  🎉

Capturing and raising different types of server errors

☝ Not done yet, but here's a draft idea I'd like to discuss with you and get some feedback:
Proposed Strategy for Handling Multiple Server Errors
To handle multiple types of server errors in the @retry decorator, we can allow the user to specify a list or tuple of exception types that should trigger a retry.
Key Changes:

Parameter Update:

Change rate_limit_exception to rate_limit_exceptions, which accepts a tuple of exception types.

Exception Handling:

Modify the except block to catch any of the specified exceptions and retry accordingly.

Updated retry Decorator Code:
import functools
import math
import random
import time

from typing import Any
from typing import Callable
from typing import Type
from typing import Tuple

def retry(
    backoff_increment: int = 5,
    backoff_type: str = "sequential",
    jitter: bool = False
    rate_limit_exceptions: Tuple[Type[Exception], ...] = (Exception,),
    retries: int = 5,
) -> Callable:
    """
    Decorator to retry a function if it raises one of the specified exceptions with support for sequential, logarithmic, and exponential backoffs.
    """

    def calculate_backoff(attempt: int) -> float:
        backoff_strategies = {
            "sequential": backoff_increment * (attempt + 1),
            "logarithmic": math.log(attempt + 2) * backoff_increment,
            "exponential": (2 ** attempt) * backoff_increment
        }
        backoff = backoff_strategies.get(backoff_type, backoff_strategies["sequential"])
        return backoff + random.uniform(0, backoff_increment) if jitter else backoff

    def _outer_wrapper(func: Callable) -> Callable:
        @functools.wraps(func)
        def _wrapper(*args: Any, **kwargs: Any) -> Any:
            for attempt in range(retries):
                try:
                    return func(*args, **kwargs)
                except rate_limit_exceptions as e:
                    current_backoff = calculate_backoff(attempt)
                    print(
                        f"Attempt {attempt + 1} failed with {type(e).__name__}. Retrying in {current_backoff:.2f} seconds."
                    )
                    time.sleep(current_backoff)
        return _wrapper

    return _outer_wrapper

Example usage:
class RateLimitException(Exception):
    pass

class ServerErrorException(Exception):
    pass

@retry(rate_limit_exceptions=(RateLimitException, ServerErrorException), backoff_increment=2, retries=5, backoff_type="sequential", jitter=True)
def function_with_problem():
    raise RateLimitException('Rate limit exceeded')

# Call the function to see the retry mechanism in action
function_with_problem()

Key Benefits:

Flexibility: Users can specify multiple exception types to handle different error scenarios.
Robustness: The decorator becomes more robust in dealing with various server errors.
Customization: Maintains support for existing backoff strategies and jitter for enhanced retry logic.

Would love to hear your thoughts, @pydanny, on this approach before proceeding with the implementation.
Thanks!

This issue can be closed!

Need for both sequential, logarithmic, and exponential backoffs. We only have sequential now, but as I've seen that's not always the best way to handle issues. But neither are the other options
Documentation for jitter, which is a random amount of time added to each sequential increase, which aids in dealing with the thundering herds problem. We don't have that - yet.

Done and done on pull request #38 🎉

Capturing and raising different types of server errors

☝ Not done yet, but here's a draft idea I'd like to discuss with you and get some feedback:
Proposed Strategy for Handling Multiple Server Errors
To handle multiple types of server errors in the @retry decorator, we can allow the user to specify a list or tuple of exception types that should trigger a retry.
Key Changes:

Parameter Update:

Change rate_limit_exception to rate_limit_exceptions, which accepts a tuple of exception types.

Exception Handling:

Modify the except block to catch any of the specified exceptions and retry accordingly.

Updated retry Decorator Code:
import functools
import math
import random
import time

from typing import Any
from typing import Callable
from typing import Type
from typing import Tuple

def retry(
    backoff_increment: int = 5,
    backoff_type: str = "sequential",
    jitter: bool = False
    rate_limit_exceptions: Tuple[Type[Exception], ...] = (Exception,),
    retries: int = 5,
) -> Callable:
    """
    Decorator to retry a function if it raises one of the specified exceptions with support for sequential, logarithmic, and exponential backoffs.
    """

    def calculate_backoff(attempt: int) -> float:
        backoff_strategies = {
            "sequential": backoff_increment * (attempt + 1),
            "logarithmic": math.log(attempt + 2) * backoff_increment,
            "exponential": (2 ** attempt) * backoff_increment
        }
        backoff = backoff_strategies.get(backoff_type, backoff_strategies["sequential"])
        return backoff + random.uniform(0, backoff_increment) if jitter else backoff

    def _outer_wrapper(func: Callable) -> Callable:
        @functools.wraps(func)
        def _wrapper(*args: Any, **kwargs: Any) -> Any:
            for attempt in range(retries):
                try:
                    return func(*args, **kwargs)
                except rate_limit_exceptions as e:
                    current_backoff = calculate_backoff(attempt)
                    print(
                        f"Attempt {attempt + 1} failed with {type(e).__name__}. Retrying in {current_backoff:.2f} seconds."
                    )
                    time.sleep(current_backoff)
        return _wrapper

    return _outer_wrapper

Example usage:
class RateLimitException(Exception):
    pass

class ServerErrorException(Exception):
    pass

@retry(rate_limit_exceptions=(RateLimitException, ServerErrorException), backoff_increment=2, retries=5, backoff_type="sequential", jitter=True)
def function_with_problem():
    raise RateLimitException('Rate limit exceeded')

# Call the function to see the retry mechanism in action
function_with_problem()

Key Benefits:

Flexibility: Users can specify multiple exception types to handle different error scenarios.
Robustness: The decorator becomes more robust in dealing with various server errors.
Customization: Maintains support for existing backoff strategies and jitter for enhanced retry logic.

Would love to hear your thoughts, @pydanny, on this approach before proceeding with the implementation.
Thanks!

@pydanny what do you think of this approach? Do you want me to implement it or should we find an alternative?


Slight jittering issue, more pronounced with a negative speed

At slower speeds, I've seen a small jitter that on a mouse wheel or when moving fast can be very noticeable.
I tried to trace down the issue in my fork /maxwerr/ember-parallax. It just logs the situation that I think is causing the event, which is when one pair of scrollTops are significantly(?) further apart than the next pair (sharing one middle scrollTop).
I haven't been able to figure out a solution, or even write a failing test, but if I revisit/make any headway, I'll come back with my findings :)

i found a solution. you can fork this repo, find scroll-speed-adjust.js, and replace all top with transform: translateY(...)


This only updates MAPL to version 1.1.9. Needed for fixing issue #82 …

…in GEOSgcm_GridComp repo

@lltakacs and @sdrabenh - this is zero diff change. It only updates Develop.cfg to use new version of MAPL (1.1.9) which is needed to compile the fix for issue #82 in GEOSgcm_GridComp r epo


Debugger:variable of local window won't be change while changing variable in watch window

Environment data
dotnet --info output:
VS Code version:1.2.1
C# Extension version:1.1.7
Steps to reproduce
1.Download and launch the sample project from https://github.com/OmniSharp/omnisharp-vscode/files/336372/musicstore.zip
2.Select ".NET Core Launch Web" and configure the location of musicstore.dll for "program which contains the space at the end as following: "program": "${workspaceRoot}/bin/Debug/netcoreapp1.0/musicstore.dll ",
3.Add some simple code in HomeController.cs, then set bp as bellow:
HomeController(IOptions options){
int a=1;
int  b=20;//set Breakpoint here
int c=a+1;
}
4.F5, add variable "a" in watch window , then wait VS hit BP
5.Change variable a=10 in watch window, and click "Enter".
Expected  behavior
variable "a" value should be 10 in local window
Actual behavior
variable "a" value is 1 in local window

This is an issue with VS Code, as it currently doesn't ask for updated values after expression evaluation. Please see VS Code issue #8118. Once this functionality is fixed in VS Code, it should work here.


dynamoose.local() not being recognized

I'm not sure what I did, but at one point in my functional tests I had this working properly. Then I moved on to working on a script to connect to the db and generate some records for me and I noticed that even though it said there were records I couldn't even find a table. So I checked my AWS and sure enough everything from my functional tests and the new script are being pushed there instead of locally.
I'll work off of my script as they're similar enough. Here's my debug output for top-level stuff.
./scripts-dist/scripts/CreateInternalApiToken.js  create -m auth -s 'auth,user'
  dynamoose Looking up model Application +0ms
  dynamoose Getting default DynamoDB +2ms
  dynamoose Looking up model AppToken +41ms
using local database
  dynamoose Setting DynamoDB to local (http://localhost:8000)

So it is actually setting up my dynamoose to point at local, but from what I've read this should be happening before the models are loaded? And I'm not even sure how that's happening. Here's my import section.
#!/usr/bin/env DEBUG=dynamoose node

const program = require('commander');
const dynamoose = require('dynamoose');

import config from '../config/settings';
dynamoose.setDefaults(config.get('dynamoose.defaultTableSettings'));
const awsConfig = config.get('dynamoose.awsConfig');
if(awsConfig !== null) {
    dynamoose.AWS.config.update(awsConfig);
}

const dynamooseLocal = config.get('dynamoose.local');
if (dynamooseLocal === true) {
    console.log('using local database');
    dynamoose.local();
}
import * as Application from '../services/Application';

The Application service is the only one that imports any model definitions and that should be happening after the dynamo config?
Any help resolving this is greatly appreciated. It would also be good to figure out how to enforce a db connection properly across the board whenever someone sets this because it seems to have bitten more than one person.

@warnero What happens if you run a console.log inside of that Application service (where you input models)?  Or add a console.log inside each of your model files?
My question is, is for some reason the models being loaded before the using local database console.log? I haven't used the ES6 import syntax very much, so I'm not sure if there are behaviors that cause it to act differently than a require.

Output
loading Application model
  dynamoose Looking up model Application +0ms
  dynamoose Getting default DynamoDB +1ms
loading AppToken model
  dynamoose Looking up model AppToken +36ms
using local database
  dynamoose Setting DynamoDB to local (http://localhost:8000) +31ms

So the model class is getting pulled before my dynamoose.local is getting called.
const uuidv4 = require('uuid/v4');

import dynamoose from 'dynamoose'

console.log('loading Application model');
let options = {
    useDocumentTypes: true,
    useNativeBooleans: true,
    timestamps: true
};

export const jsonSchema = {
    applicationId: {
        type: String,
        hashKey: true,
        default: function() {
            return uuidv4();
        }
    },
    name: String,
    description: String,
    scopes: [String]
};

export const Schema = new dynamoose.Schema(jsonSchema, options);
export const Model = dynamoose.model("Application", Schema);

@warnero That is the problem then. Either you are including/requiring that model somewhere else, or for some reason the include ES6 syntax gets hoisted to the top of the file.

And now I think I see why. I'm using babel to transpile and it is setting Application before my db local call happens.
var _settings = require('../config/settings');

var _settings2 = _interopRequireDefault(_settings);

var _Application = require('../services/Application');

var Application = _interopRequireWildcard(_Application);

function _interopRequireWildcard(obj) { if (obj && obj.__esModule) { return obj; } else { var newObj = {}; if (obj != null) { for (var key in obj) { if (Object.prototype.hasOwnProperty.call(obj, key)) newObj[key] = obj[key]; } } newObj.default = obj; return newObj; } }

function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { default: obj }; }
const program = require('commander');
const dynamoose = require('dynamoose');

setupDb();

@warnero The problem with that is Dynamoose has certain functions that get called on model load and throughout the lifecycle of the application that require it to be setup correctly. For example Dynamoose can create the table automatically. It also polls for when the table is actually active and ready to go before running any commands on it.
I think it would require a complete restructuring of how those systems operate, and setting it to .local() would require a lot of double check work to ensure the tables are setup correctly and all of that. It's not as easy as just changing the connection due to how much setup work goes into those tables.

OK, will dig into the babel side of things to see how I can get it to force load other stuff beforehand. Just noticed none of my default config is being loaded before either so that's messing with my prefix stuff.


Orient images correctly based on metadata

If a photo is taken with the camera upside down, re-orient the image the right way up based on the metadata rather than showing image upside down in posts.

This is definitely still an issue with the way Beta displays images. See, for example, https://beta.pnut.io/@jeremycherfas/posts/372113

Hopefully this will be implemented: https://github.com/pnut-api/api-spec/issues/63

Tested with firefox, issue appears to be fixed. Thank you!


Clarify email

I added language to flash messages and email so that vendors who follow specific opportunities are prompted to sign up for the newsletter. This was in reference to #1

@alizauf: I added some comments to this PR for changes that should be made before it gets merged. You can checkout this branch (clarify-email), and any commits you push will be appended to this PR. Once you're done, write a comment to let me know, and I'll review it again.
Also, it looks like there's a test (test_signup_for_opportunity) that's failing.

Cool I'll make these changes. Thanks.

I think that test is failing due to the new added link--I'll work on that.

Okay, I believe I fixed all of these. I added Markup to the tests since it is used in the flashes, but I'm not sure if that will cause issues with the tests. Is there a way for me to run the tests locally?

https://github.com/dobtco/beacon#testing

Ah, yep, that was right there.

Looks great. Merged!


Update GUI

Minor bugs

Codecov Report

Merging #97 into master will decrease coverage by 0.48%.
The diff coverage is 0.00%.

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


Expose set_environment to GDScript

set_environment is nicely implemented in our OS class but not exposed to GDScript while get_environment and has_environment are.
Especially when building editor plugins being able to change environment settings can be extremely handy.
(3.2 version, master PR will come in a minute, I just needed this in 3.2 badly :) )

Thanks!


As a user, I want to filter the list of references so that I can narrow the results based on my interests.

Notes for testing

Year filters will be handled separately via #122
We may revise the layout some to clarify book attributes vs reference attributes, but the filter functionality is working.

Filter by:

book is extant
book contains annotation
book contains corresponding annotation
book author
book subject
book language of publication
book original language
book place of publication
~book original publication year~
~book edition year~
~book printing year~
citation type
derrida work

@rlskoeser the filters seem to be working properly


Implement single comment/note field/string for an Objective

After discussing with Wendy, this strays from our initial goal of parity with a presentation view. Adding this increases the amount of information that would not fit into a meeting.


update xmind to 3.6.0.R-201511090408, update download link

http://dl3.xmind.net/xmind-macosx-3.6.0.R-201511090408.dmg return 403.
update link to http://www.xmind.net/xmind/downloads/xmind7-macosx-3.6.0.R-201511090408.dmg

Thank you for the contribution. It was merged directly as 6d175c1daa24ee290eabfa5bf9d722af8757e671 to keep commit history cleaner. Your contribution is still credited to you.


Update README.md

Updated Table of Content + Added License section.

Thank you @imrtls00 🙏

Close #20


Issue updateing RcppParallel

This morning while updating packages I got the following message in regards to RcppParallel.
Error: Transaction test error:
  file /usr/local/lib/R/library/RcppParallel/lib from install of R-CRAN-RcppParallel-5.0.3-1.fc33.copr2016906.x86_64 conflicts with file from package R-CRAN-RcppParallel-5.0.2-1.fc33.copr1802054.x86_64

I uninstalled R-CRAN-RcppParallel and reinstalled which solved the issue but thought I'd flag in case it was an issue you need to look at.

Thanks for the report. I saw that too, and I don't quite understand the issue yet. Will look into it.

Something has changed in the RcppParallel building process + there's some limitations with symlinks in RPM packaging = this conflict. Note to self: https://docs.fedoraproject.org/en-US/packaging-guidelines/Directory_Replacement/#_working_around_it_with_scriptlets

Fixed now.

Similar issues again.

RcppParallel copies the tbb shared libraries, and thus RPM generates identical IDs. :-\

Fix coming in the next release of RcppParallel, see https://github.com/RcppCore/RcppParallel/issues/161.

:+1: Great - ran in to this today.


Implement a Linter Framework

As the project grows, code quality and standards enforcement will become important. This is a stub issue for discussion of linter frameworks that might handle immediate needs and facilitate long-term possibilities.

What are the compelling options currently in the space?
What are current/future needs?
Are there more esoteric requirements that should guide a decision?

jshint is currently run during npm test (as part of the pretest script in package.json). Are there issues that it misses that other linters would detect?

The notion with linters is work smarter not harder. JSHint may satisfactorily lint JS (I'd yield to anyone who knows more about JS than I on that), but there are lot's of other aspects of a project worth linting. For instance, the repo is filled with YAML files, wouldn't it be nice to have commit or merge time validation checks? A full linting framework permits validation across the project so that you don't have think about "does this maintain our standard" or "is this valid?" It's good hygiene.

General requirement

Make sure all code published in markdown-lint-check is clean and follows coding/formatting best practices

Mega-Linter
Demo PR in this repo (without fixes): https://github.com/nvuillam/markdown-link-check/pull/2
Demo PR in this repo (with fixes): https://github.com/tcort/markdown-link-check/pull/137
Pros:

100% free and open-source
Based on heavily used Github Super Linter (6k stars), but with much more features (https://nvuillam.github.io/mega-linter/#mega-linter-vs-super-linter)
Everything happening on Github Actions servers, not on a remote black box cloning the repo
Easy logs browsing
Can automatically (or manually) apply formatting and fixes
Always using the latest version of all linters
Easy configuration to activate/deactivate linters, or define them as non-blocking
Same config files used by locally installed linters
Also checks abusive copy-pastes and spelling mistakes (those checks can be disabled if wished)

Cons:

No very known yet (but seriously maintained)
No "easy" local run yet (but linters used can be individually added thanks to centralized documentation)
No UI except inside GitHub and in (organized) artifact logs

Other cloud code quality tools:
Sonar , Codacy, CodeClimate ...
Pros

Online UI
Maturity
Free for open source use

Cons

Need to go outside of github to check links
No auto-formatting and auto-fixing
No local run

Individual linters
Install and configure one by one the linters then call them locally and thru CI
Pros

Same linter commands runned locally and on CI

Cons

More setup time and more maintenance
Need to manually upgrade linters versions (PR can be generated via dependabot)

Summary
So, not surprisingly , I will propose Mega-Linter , for all the pros :)
Note: All available propositions provide a better developer experience in case of use of related linters extensions in the developer IDEs (ex: eslint for VsCode), so that errors can be directly detected while writing, instead of when running tests, committing and pushing
I obviously may not be objective, do not hesitate to add more pros & cons to the available choices :)

I like Pre-commit. I use it extensively both personally and professionally. It has a number of things going for it:

Mature. It has been around for ages and is stable with new features released routinely. I’ve seen very few if any critical, breaking bugs in the time I’ve used it.
Active and experienced development team. Not only active but experienced, the core team are the same folks who maintain pytest & tox-- major python projects
Language agnostic and batteries included. Write lints in virtually any language that suits, there’s a full internal framework for installing tools.
Large, community-driven directory of existing hooks. Even if what you’re looking for isn’t available in the directory, most linters are GitHub search away.
Git-first. It was designed around git hooks and can trigger on virtually every available hook. For instance, I trigger a test run pre-push on most repos to ensure that I’m not pushing breaking code.
Easy to install. A struggle with many tools of this sort is getting them installed, pre-commit is available for install from most package managers.
Adding additional checks is dead simple. It uses a single config file per repository.
GitHub Workflow support already exists. There’s little work adding it existing CI.

I’ve surely missed something glaring, and will update the comment if it comes to mind.

@nvuillam Probably my biggest concern with Mega-Linter is that you describe it as a hard fork, but the documented plans for the project suggest a full port to python. Ports can be difficult, and stabilizing them even more so. I'm not sure I understand the reason for a port of super-linter other than language preference/learning.

@cadeef > bash vs python... it's not just about languages, more about capabilities, that are dramatically increased thanks to python modules :)
It is already fully ported to python (the remaining sh files are used only in internal CI, and to check differencies when periodically refreshing from base repo
I hear you about the "no easy local run = deal breaker",  i think i'll implement some wrapper in a npm package that would run on a .mega-linter.yml using config file at the root of the repo (no matter if mega-linter is selected for markdown-link-check or not ! )

@nvuillam I'm sure there's interesting conversation to be had about your justification for porting, but probably not in this thread, feel free to email me if you'd like to continue (I might have some battle-hardened perspective for you).

FYI, now Mega-Linter is locally runnable locally :)
https://nvuillam.github.io/mega-linter/mega-linter-runner/
May I wake upgrade https://github.com/tcort/markdown-link-check/pull/137 ? :)


CLI: timeout to master is 60 seconds, makes all commands (including kontena version) hang if no master is available

~/.kontena_client.json:
{
  "current_server": "default",
  "servers": [
    {
    },
    {
      "name": "default",
      "url": "http://kontena-master.example.com",

all commands like kontena service ls will just hang. CLI should fail faster.

The default connect_timeout used in the underlying HTTP library (Excon) is 60 seconds. IMO we could lower that a bit. Maybe even to 20secs, if we don't get HTTP connection to master within 20 secs things are anyway going pretty south. :)

Closing this as the timeouts are now configurable and the default connect timeout is now 5 secs. https://github.com/kontena/kontena/blob/master/cli/lib/kontena/client.rb#L59


Safeguard of H3Event body stream locking in edge runtime workaround

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] infrastructure changes
[ ] Other... Please describe:

What is the current behavior?
https://github.com/solidjs/solid-start/blob/main/packages/start/src/runtime/server-handler.ts#L136
There's currently a workaround for edge runtimes to create a new Request object instead of using the current one.
What is the new behavior?
Add a safeguard for the edge runtime workaround when a stream is already locked to not create the new Request object.
Other information
My goal is to make Solid Start work 100% on the Azure Functions runtime. I currently have a PR open at Nitro to support the latest Azure Function runtime.
However there's currently an issue that the H3 event body stream is already locked when it gets to the part of the edge runtime workaround when running on Azure Functions, which causes issues with server actions.
Im happy to say that all Solid Start functionality seems to work on Azure Functions once we get around this locking issue.

Yeah I see hacks on hacks in there. I'm glad you figured something out. That being said. I'm going to probably need to test this fix against Vercel/Netlify edge as I thought the creation of the new Request was to get around stream locking so this fix may impact them.


reserved identifier violation

I would like to point out that identifiers like "_HW_HIGHWAY_H_" and "_HW_LINE_LIST_H_" do not fit to the expected naming convention of the C language standard.
Would you like to adjust your selection for unique names?

Thanks. I will adjust.

Thanks for your improvement of affected include guards.


Feature: Support React Query in React Router

Or optionally:

let the user configure the route and its context
let the user configure the template

@gunta AFAIK there's nothing special needed for supporting React Query with React Router through generouted.
Here's an article about React Query + React Router covering prefetch and invalidation through action and loader functions which you can use at generouted by exporting route-based Action/Loader function.
Also you could add a custom routes.tsx to modify and/or configure more exports, see #103.
Hope that helps.


Buffer gets overwritten while decoding

Is it possible that a buffer can get overwritten while still parsed?
Sending following messages (quite fast behind each other).
The number indicates the length in bytes:
/iad/led/color iii 36
/iad/imu/rpy i 24

On the arduino, when falling into this error-check (regarding too few arguments), I print out the current buffer (storage.end() - storage.begin()), first the byte value and then the corresponding charachter:
Size: 36
47|/ 105|i 97|a 100|d 47|/ 105|i 109|m 117|u 47|/ 114|r 112|p 121|y 0|� 0|� 0|� 0|� 44|, 105|i 0|� 0|� 0|� 0|� 1| 101|e 0|� 0|� 0|� 49|1 0|� 0|� 0|� 0|� 0|� 0|� 0|� -1|⸮

Well, that looks like the 36 byte buffer of the /iad/led/color packet, but filled with the values of the /iad/imu/rpy packet.
I am super confused now...either I am not reading the right data for debug or there is some concurrent work going on. Sending the same package behind each other of course makes no difference, because we are overwriting the same buffer.
After one of these messages, the stream.parsePacket() returns always 65524.
Here an example sketch, which let me recreate this problem:
#include <SPI.h>
#include <WiFiNINA.h>
#include <WiFiUdp.h>
#include <utility/wifi_drv.h>

#include <ArduinoOSC.h>

#include "secrets.h"

#define OscWiFi ArduinoOSC::Manager<WiFiUDP>::getInstance()

#define IN_PORT 8000

int keyIndex = 0;
int status = WL_IDLE_STATUS;

void setup() {
  Serial.begin(9600);

  // connect wifi
  while (status != WL_CONNECTED) {
    Serial.print("Connecting to SSID: ");
    Serial.println(ssid);
    status = WiFi.begin(ssid, keyIndex, pass);
  }

  // setup inputs
  OscWiFi.subscribe(IN_PORT, "/test/rgb", [&](int& r, int& g, int& b) {
    // do nothing
  });

  OscWiFi.subscribe(IN_PORT, "/test/w", [&](int& w) {
    // do nothing
  });

  Serial.println("everything setup to test!");
}

void loop() {
  OscWiFi.update();
}

Just send (with any OSC client) /test/rgb and /test/w alternately in a high framerate.

Ok, the same seems to happen in CNMAT/OSC as well, so it is really a WiFiNINA problem. But would be great if you could test it on another board which if you have on available.

Ok, on my ESP32, it works fine on 60fps for each.
It's not completely relate to this issue, the packet storage is based on the ring buffer with fixed size if you use WiFiNINA boards (because they cannot use STL). Currently it is set to 64 bytes by default, so if you want to use bigger message than it, please use change this macro.
However, all osc message has 64 bytes buffer storage in each, it's not related to this issue... just FYI. Please let me know if you have the progress!

Has been fixed in https://github.com/arduino/nina-fw/pull/49! 🎉

Great! Thanks for the report!


Buttons are slow to update themselves at page load

Hello,
I am very happy about oauth-ng except for one thing: when the page is loaded for the first time, I see all three buttons (sign-in, logout, access denied) before two of them disappear and only the sign-in one remains. I guess that Angular is slow to find out that two of them are to be hidden (the ng-show="show=='logged-out'" properties in the 3 spans). I am using the default.html template.
Visually it's very annoying and surprising for the user.
I tried all sorts of CSS tricks to hide the buttons until the show context variable is set, but I was not able to make anything work.
I am using Angular 1.4.6. I'm a beginner at Angular.
Does anyone else has this problem? Am I doing something wrong?

I saw the same behaviour. I would suggest to try out and experiment with
ng-cloak
https://docs.angularjs.org/api/ng/directive/ngCloak

Thanks for the quick answer, I learned something new about Angular today :)
Unfortunately, it did not solve the problem. I tried putting it at various places, even simultaneously, and the flicker effect is still there. I tried to put it in the  tag of the default.html template, in the <oauth> tag itself, in the
 enclosing it, nothing helps. Pretty distressing.
Ideas are welcome.

I see. In this link they make a hack that seems to work.
http://stackoverflow.com/questions/19599144/in-angular-is-there-a-way-to-prevent-flicker-in-expressions-that-contain-concat
I don't like it at all and I think that ng-cloak with in page CSS (on the
header, not CSS file) should work out.

I found the solution! And it's a clean one.
I simply added the ng-hide class to the 3 UI elements. So they are hidden by default, and only the right one becomes displayed when the oauth-ng code ultimately takes over and sets the display classes correctly. So here is how my template/default.html file looks like:

  {{text}}
  Logout
  Access denied.

Maybe you'll want to adjust your code this way.
In any case, thanks for your help on this! My app now looks much better.

A pull request would be really appreciated @YannDoW.
Thanks for your work

I created a Pull Request. I'm still a beginner at GitHub, so I hope I did things properly. I hope it helps.
Thanks!


How to concat  two wav files?

I wanna merge multiple Wav files to one,  can I use this library to handle this?

The current version of wavefile does not support this. I will add this to the roadmap for a future release. Thanks!

I got this working with the following code (i'm using Bun but works with node too):
import { WaveFile } from "wavefile";

const audio1 = await Bun.file("hello.wav").arrayBuffer();
const audio2 = await Bun.file("world.wav").arrayBuffer();

const mergedAudio = mergeAudio(audio1, audio2);

await Bun.write("merged.wav", mergedAudio);

function mergeAudio(audio1: ArrayBuffer, audio2: ArrayBuffer) {
  const a = new WaveFile(new Uint8Array(audio1));
  const b = new WaveFile(new Uint8Array(audio2));

  const aSamples = a.getSamples();
  const bSamples = b.getSamples();

  const mergedSamples = new Float64Array(aSamples.length + bSamples.length);

  mergedSamples.set(aSamples);
  mergedSamples.set(bSamples, aSamples.length);

  const newWaveFile = new WaveFile();

  newWaveFile.fromScratch(1, 24000, "16", mergedSamples);

  return newWaveFile.toBuffer();
}


fix(servers): Changeing to post-fork servers

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fixes for downloads

Three fixes related to downloads:

Ensure query parameters are decoded properly before being re-encoded by RequestBuilder
Handle query params without values correctly (fix index out of range error)
Check the response code before streaming the download and report any non-success codes as failed downloaded.

Thanks for doing this change. I think that I've just nits :+1:

Cleaned things up, should be better now.

Awesome work!
Before merging this pull request, can you verify that your initial sample (the one that didn't work before) is working now with the new code? Ping me if you need help to set it up.
I know that your test covers it, but it just to double check...

Yep, was able to pull the client lib projects in to my solution and build against that. Seems OK now.


Change fmin optimizer to more general minimize for _fit method

Also thinking about add warning where there is no convergence.

👍 nice I like this alot

scipy's minimizers should display a warning if convergence fails, so I would leave that to them.


extension node_modules not packaged properly

VSCode Version: 1.7.2
OS Version: Windows 10 / 1607

in short: After publishing and installing my extension 'Markdown+Math' I get
command 'extension.mdmath' not found
when trying to run it. Having a look at the extensions node_modules folder, I see only the three dependency folders

katex  ... which is needed.
markdown-it-katex... which is also required.
match-at ... which I don't know where it comes from, but this is irrelevant.

After doing a npm install from the command line in that extensions main directory the  node_modules folder is populated with a lot more modules. The extension is working properly after that.
My package.json file has an
    "dependencies": {
        "markdown-it-katex": "^2.0.3"
    },

entry.
My question is: What am I doing wrong or what can I do, if I don't want to force my users doing an extra  npm install from the command line.
I should mention, that I use the newest npm version 3.10.6 which generates a flat dependency folder structure now.
Steps to Reproduce: publishing and running extension ...  Markdown+Math

npm install ... installing all required node modules in dev subfolder ./node_modules
vsce publish 0.8.8   ...  publish extension to market place
install extension 'Markdown+Math' from within VS Code ...
Error when invoking extension

> cd  %USERPROFILE%\.vscode\extensions\goessner.mdmath-0.8.8
> npm install
Ctrl+Shift+. invokes extension properly with any  *.md file.

Thanks ....

I finally managed to resolve the problem. In the node_modules folder there were still a lot dependencies originating from vscode itself. After filtering those out, only a handful relevant were remaining, which I put into the dependencies list of package.json.
Everything is fine now ... please close this issue.


Spyder fails to open a new IPython console

Description
What steps will reproduce the problem?

Open a new IPython console.

What is the expected output? What do you see instead?
Spyder doesn't manage to open the console. Error dialog.
Afterwards, Spyder at startup is not able to open the first IPython console either. The error dialog opens at startup.
Please provide any additional information below
File "/usr/lib/python3.6/site-packages/spyder/plugins/ipythonconsole.py", line 974, in create_new_client
self.connect_client_to_kernel(client)
File "/usr/lib/python3.6/site-packages/spyder/plugins/ipythonconsole.py", line 995, in connect_client_to_kernel
stderr_file)
File "/usr/lib/python3.6/site-packages/spyder/plugins/ipythonconsole.py", line 1383, in create_kernel_manager_and_kernel_client
stderr = codecs.open(stderr_file, 'w', encoding='utf-8')
File "/usr/lib/python3.6/codecs.py", line 895, in open
file = builtins.open(filename, mode, buffering)
FileNotFoundError: [Errno 2] Aucun fichier ou dossier de ce type: '/tmp/spyder-nchouika/kernel-8f3ba0aad080.stderr'
Version and main components

Spyder Version: 3.2.0
Python Version: 3.6.2
Qt Versions: 5.9.1, PyQt5 5.9 on Linux

Dependencies
pyflakes >=0.6.0 :  1.6.0 (OK)
pycodestyle >=2.3:  2.3.1 (OK)
pygments >=2.0   :  2.2.0 (OK)
pandas >=0.13.1  :  0.20.3 (OK)
numpy >=1.7      :  1.13.1 (OK)
sphinx >=0.6.6   :  1.6.3 (OK)
rope >=0.9.4     :  0.10.7 (OK)
jedi >=0.9.0     :  0.10.2 (OK)
psutil >=0.3     :  5.3.1 (OK)
nbconvert >=4.0  :  5.1.1 (OK)
sympy >=0.7.3    :  1.1.1 (OK)
cython >=0.21    :  0.26.1 (OK)
qtconsole >=4.2.0:  4.3.0 (OK)
IPython >=4.0    :  5.3.0 (OK)
pylint >=0.25    :  1.7.2 (OK)

This was fixed in Spyder 3.2.3. Please update to that version.


Display dates using the local system timezone

Please implement the same for this processlogs.php as for the LoRa logs one
(keep the raw log entries in UTC, display datetimes in local tz)
Excellent stuff by the way! thanx a lot for these scripts :)

Done! Thanks for the suggestion and for the compliments! I'm glad you like these tools  :)


logging and flags support

abseil-py supports logging and flags, but why not support in cpp? Does it already supported? I can not found where to using it.

Flags and logging are not supported yet, but both are actively being worked on.

@derekmauro Thanks for your reply, I am happy hoping for that. So that we can integrate all useful tools into one single lib.

Flags are now released: https://abseil.io/blog/20190509-flags

@cblichmann  What about logging? Any schedual?

I'm not on the Abseil team, I just linked the blog post :)
@derekmauro, do you have some schedule you can share wrt logging?

Schedules are really hard in this space, because we're not just
developing a logging API, we're taking the thing that's used internally
everywhere, cleaning it up (any changes are going to be a lot harder once
its externalized), moving it into our internal copy of Abseil, fixing all
internal references to point to that ... and doing that without breaking
the internal Google developers. Seems like still probably 6 months off, but
could be a lot longer than that.
*From: *Christian Blichmann<EMAIL_ADDRESS>*Date: *Thu, May 9, 2019 at 10:51 AM
*To: *abseil/abseil-cpp
*Cc: *Subscribed
I'm not on the Abseil team, I just linked the blog post :)

@derekmauro https://github.com/derekmauro, do you have some schedule
you can share wrt logging?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/abseil/abseil-cpp/issues/297#issuecomment-490937339,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC7CRX5D427IC32CIGDNUV3PUQ27XANCNFSM4HGQGSVQ
.

Now that this issue is closed, is there somewhere else where we can track the progress of logging support in abseil-cpp? I’m also curious about what the plans are for the CHECK macros that are currently part of glog. Would those macros still be part of the logging library going forward, or would they become something like an //absl/check:check Bazel target?

I plan to ship CHECK in the same header and Bazel target as LOG, which I expect to be absl/logging/logging.h and //absl/logging:logging.

Awesome thanks for the update! Is there any timeline for when we can expect the //absl/logging:logging target to be available?

Why closing this issue since logging is still not available in abseil-cpp and AFAIK we may expect it ?
note: you should rename this double issues too...

They likely closed it because there exists an internal tracking bug for this and there will probably be some blog post announcing it when it becomes available.
(Note the use of "likely" and "probably", I can only guess how the Abseil team will actually release logging when it's finally ready)

Mother issue of:

https://github.com/abseil/abseil-cpp/issues/658
https://github.com/abseil/abseil-cpp/issues/882
https://github.com/abseil/abseil-cpp/issues/980
https://github.com/google/glog/issues/564

I hacked glog library to use absl instead of gflags. Here is how I import it: https://github.com/romange/helio/blob/master/cmake/third_party.cmake#L186
and here is the modified branch of glog: https://github.com/romange/glog/tree/Absl


Update Volto core customizations

Ref #264530

@avoinea I still have to rewrite the unit tests for this addon


PropertyPaneMultiSelect is not retaining preselected values

The problem is the once i set the values and then save the changes, the next time when i open the webpart configuration the multiselect values are not retained.

                PropertyFieldMultiSelect('selectedColumns', {
                  key: 'selectedColumns',
                  label: "Multi select field",
                  options: this.ddlColumnOptions,
                  selectedKeys: this.properties.selectedColumns
                })

Here is the screen shot , the value for normal dropdown are retained.But it is not working for multiselect

Code on start :

  protected async onPropertyPaneConfigurationStart(): Promise<any> {
    debugger;
    let lists:IPropertyPaneDropdownOption[]=await this.getAllList();
    this.ddlListOptions=lists;
    this.render();
    this.context.propertyPane.refresh();
    let views:IPropertyPaneDropdownOption[]=await this.getAllViews()
    this.ddlViewOptions=views;
    this.render();
    this.context.propertyPane.refresh();
    let columns:IPropertyPaneDropdownOption[]=await this.loadColumns();
    this.ddlColumnOptions=columns;
    this.render();
    this.context.propertyPane.refresh();
  }

This is an issue in the Office UI Fabric control used behind the scenes which seems to have issues when async options are provided. I did an update to the control so that it is supported.
Here you can see the result:


Refactor section version content to markdown

@Aharon-Porath after doing some research, we now know that there are some issues when saving markdown (some styling is lost, multiple syntax options). Closing this for now, Let's get back to this if and when a need comes up (i.e. demand from community, performance etc)


Reuse some buffers and apply clippy fixes

This reuses some buffers that have previously been deallocated in each loop iteration. Additionally clippy has been showing me a bunch of warnings that I haved fixed as well.

I rebased the PR and reverted the changes to the imports.