Fela shorthand expand with merge SSR

Type: Bug

Packages
Version

fela
11.2.0

react-fela
11.2.0

fela-monolithic
11.2.0

fela-plugin-extend
11.2.0

fela-plugin-expand-shorthand
11.2.0

fela-plugin-fallback-value
11.2.0

fela-plugin-named-keys
11.2.0

fela-plugin-unit
11.2.0

fela-plugin-validator
11.2.0

Description
When using fela-plugin-expand-shorthand with merge, an order of atomic classes is different when rendered on a server than on a client. It works properly if merge is turned off.
Honestly I don't know if it is a bug or my own misuse of fela.
Steps to reproduce
A rule producing the problem:
export const input = ({ theme, disabled = false, error = null, prefix = null, suffix = null }) => {
    const errorStyle = {
        backgroundColor: [theme.colors.error, tinyColor(theme.colors.error).setAlpha(0.08).toRgbString()],
        borderColor: 'transparent',
    };

    const padding = 2 * theme.widths.spacing;
    const paddingWithAddition = additionSize + 2 * theme.widths.spacing;

    const baseStyle = {
        display: 'inline-block',
        boxSizing: 'border-box',

        width: '100%',

        paddingTop: padding,
        paddingBottom: padding,
        paddingLeft: prefix ? paddingWithAddition : padding,
        paddingRight: suffix ? paddingWithAddition : padding,
        marginTop: 0,
        marginBottom: theme.widths.spacing,

        fontFamily: theme.fontFamily.primary,
        fontSize: 0.875,
        lineHeight: 1.14,

        color: theme.colors.text,
        backgroundColor: theme.colors.white,

        border: `1px solid ${theme.colors.midGrey}`,
        borderRadius: '8px',

        isMobile: {
            fontSize: 1,
        },
    };
    const inputStyle = {
        ...baseStyle,
        ':hover': {
            borderColor: theme.colors.grey,
            boxShadow: theme.boxShadows.input,
        },

        ':focus': {
            outline: 'none',
            borderColor: theme.colors.text,
        },

        '::placeholder': {
            color: theme.colors.grey,
        },
    };
    const disabledStyle = {
        ':disabled': {
            color: theme.colors.grey,
            borderColor: 'transparent',
            backgroundColor: theme.colors.midGrey,
            boxShadow: 'none',
        },
    };
    if (disabled) {
        return {
            ...baseStyle,
            ...disabledStyle,
        };
    }
    if (error) {
        return {
            ...inputStyle,
            ...errorStyle,
        };
    }
    return inputStyle;
};

Expected Behavior
The order of atomic classes remains the same. I can't see a reason for it to be rendered in a different order since the rendered output is the same.
Actual Behavior
The error produced by react:
index.js:1 Warning: Prop `className` did not match. Server: "bj a c at av fs ft o q t cy fu w cc y fv fw fx fy fz ga gb gc gd ge gf gg gh gi gj gk gl gm gn go gp gq du gr gs gt gu gv gw gx" Client: "bj a c at av fs ft o q t cy fu w cc y fv fw gb gc gd ge fx fy fz ga gf gg gl gm gn go gh gi gj gk gp gq du gr gs gt gu gv gw gx"
    in input (at Input.jsx:32)

The misordered classes are classes produced by :hover and :focus parts of the afore mentioned rule.

Could I ask you to try with<EMAIL_ADDRESS>It should list<EMAIL_ADDRESS>as a dependency in your lock file — this is very important, since there was a potential regression (which we failed to really reproduce) in<EMAIL_ADDRESS>Let us know if it yields the same result please, as this would help narrowing the problem down. :)

I'll close this for now, as it is an issue in inline-style-expand-shorthand rather than Fela itself.


soc: silabs: Include series-specific Kconfig

The series-specific Kconfig files were not included, leading to RTT not being considered available.
Make the inclusion of series and SoC family Kconfig files explicit.
Fixes #75511.

@nordicjm  please re-review


Adding files required to build instructions

The changes are based on course 20486.

Moin Moin.
Do You know, how to download the pandoc.ps1 and template.docx files.
I am new to git and used to TFS.
_Tschüß,
__Michael.


practice 6 - simple_local_planner - code comments

Please fix the following:

No need to assign parameter values that are not about to change to local variables. You can use them directly in the callback using the class (global) variable name
https://github.com/AnishShr/autoware_mini_practice/blob/21d92c582d289c5f9fc24b477ca34f7889b10b66/practice_6/nodes/planning/local/simple_local_planner.py#L102-L116

I would bring these out of the self.lock group. Important is that all the things coming from path callback stay consistent, so they are in the lock group. But current pose and velocity come from separate topics and with different frequency, so no point having them in that group.
https://github.com/AnishShr/autoware_mini_practice/blob/21d92c582d289c5f9fc24b477ca34f7889b10b66/practice_6/nodes/planning/local/simple_local_planner.py#L95-L100

This is wrong and it is not used in this callback later. Not necessary!
https://github.com/AnishShr/autoware_mini_practice/blob/21d92c582d289c5f9fc24b477ca34f7889b10b66/practice_6/nodes/planning/local/simple_local_planner.py#L134

Important is to publish empty local path! Then follower will get it empty and will stop the go vehicle if it is not stopped already!
https://github.com/AnishShr/autoware_mini_practice/blob/21d92c582d289c5f9fc24b477ca34f7889b10b66/practice_6/nodes/planning/local/simple_local_planner.py#L141-L143

You should not return from here! If we don't get the transform, then we set it to None and we still need to detect the obstacles publish the local path and calculate the target velocity. Now we will just assume that objects have 0 velocity since we don't have a reliable transform.
https://github.com/AnishShr/autoware_mini_practice/blob/21d92c582d289c5f9fc24b477ca34f7889b10b66/practice_6/nodes/planning/local/simple_local_planner.py#L154-L163

1&2. Put only relevant variables inside the self.lock block
https://github.com/AnishShr/autoware_mini_practice/blob/db7de2e51eb2ac93c232ab33cd755905c6f50521/practice_6/nodes/planning/local/simple_local_planner.py#L93-L98
3. Removed this variable
4. published empty local path when local_path is None before returning
5. Removed the return line an later assigned zero velocity if transform is not there
https://github.com/AnishShr/autoware_mini_practice/blob/db7de2e51eb2ac93c232ab33cd755905c6f50521/practice_6/nodes/planning/local/simple_local_planner.py#L153-L161
https://github.com/AnishShr/autoware_mini_practice/blob/db7de2e51eb2ac93c232ab33cd755905c6f50521/practice_6/nodes/planning/local/simple_local_planner.py#L181-L185

latest commit: https://github.com/AnishShr/autoware_mini_practice/commit/7d19ddadcd79e106cadf593cf4e87f63427ab2fd

OK


Defer Composition of Priority and Eviction Policies

Breaks out the prioritization policy into its own data type Priority. CachingPolicy then becomes a simple product type that contains a Priority and an Evict. Composing CachingPolicy values composes the individual Priority and Evict values, maintaining the separation of the binary Evict and the rank ordered Priority until a comparison is actually done in CachingPolicy#compare.
This now has the following properties:

Priority values compose using ++, which prioritizes using the first instance and breaks ties by the second, similar to alphabetizing by last name and then first name. ++ is associative and Priority.any is an identity element with respect to this which represents the policy of giving all cache entries the same priority.
Evict composes using && and || which has all the usual boolean structure.
CachingPolicy values compose using ++ which compose the priority values using ++ and the evict values using || (definitely evict if either policy says definitively evict). This operation is associative and it is also now independent of the ordering in which eviction policies are composes, so the following always holds: cachingPolicy ++ CachingPolicy.fromEvict(evict) == CachingPolicy.fromEvict(evict) ++ cachingPolicy.

Beautiful work and massive cleanup!


Routing

Please review @rynowak
Not sure about last sentence, which was taken from our initial discussion - help me clarify it please.

just FYI - buried under a pile of important work now. No ETA on when I'll get to this.

@Rick-Anderson Can we have a UE review?

Really complete and comprehensive doc BUT
@Eilon  don't we need a warning to not get too cleaver with routes? Do we want to mention that complicated routes can be difficult to test and debug?
Can we say, many apps won't need more the default route?

We could certainly add a recommendations section, as we have done in other docs like http://docs.asp.net/en/latest/fundamentals/dependency-injection.html#recommendations

Do we really need to include all these other random files besides the code that we're explaining?

@rynowak Which files are you thinking can be left out and still leave the sample as a project the end user can open and run?

a project the end user can open and run

I don't think that should be a goal. We do that kind of thing elsewhere and we have repos where we can build and test the samples to verify they work. It's a maintenance nightmare to have runnable code that we can't verify programmatically. It will rot and break.
My suggestion would be to just check in the files/snippets that are directly explained in the docs.
/cc @danroth27

I'll let @danroth27 chime in; the general practice thus far has been to include projects, not just files, for exactly the reason you stated (so we can run and verify the code). That part's not automated (yet), but it will certainly be easier with the projects than it would be with just files (and at that point, you could forego the files and just put in code blocks).

@rynowak We want samples that we can build and run so that the code snippets in our docs don't rot and break. I don't want docs with inlined code that doesn't compile. I do agree that our samples shouldn't have unnecessary files, but this sample looks pretty focused to me. Are the VS files the concern?

Nice article, @ardalis! :watch:

Hopefully we're close to :shipit: ?  Should I create a new, clean PR to avoid merge issues with the MVC move that occurred while this was in PR? /cc @danroth27

@ardalis This topic isn't in the MVC project, so I don't think merge conflicts should be much of an issue.

@danroth27 Yes, but the CI build is failing because of broken MVC links. I figured it would be easier to fix that (once) in the post-MVC move version of things.

@ardalis looks like you have a travis failure.

@danroth27 Travis is failing due to an intersphinx link to /mvc which will be fixed when this is merged into the new structure (with MVC in same docs project). Do you want me to get latest master and PR against that to fix this, or just fix it after the PR is accepted (if necessary)?

:watch: - I'm just waiting on resolution of two things now

data tokens info
https://github.com/aspnet/Docs/pull/1037#discussion_r55450307

@ardalis I would rebase on master and force push your branch to fix the travis failure

Build fixed - shipit? @rynowak @danroth27

:shipit: from me, but please get signoff from DANTHOR as well.

:shipit: Looks great.


Master branch build crashes on startup on macOS

Godot version:
master (8dd58a6)
OS/device including version:
macOS Mojave 10.14.6
Issue description:
Master branch crashes on startup on macOS
Steps to reproduce:
$ scons platform=osx --jobs=$(sysctl -n hw.logicalcpu)
$ ./bin/godot.osx.tools.64
arguments
0: ./bin/godot.osx.tools.64
Current path: .../godot-master
Godot Engine v4.0.dev.custom_build - https://godotengine.org
ERROR: No surface extension found, is a driver installed?
     at: _initialize_extensions (drivers/vulkan/vulkan_context.cpp:264)
ERROR: Could not initialize Vulkan
    at: DisplayServerOSX (platform/osx/display_server_osx.mm:3522)
handle_crash: Program crashed with signal 11
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] 1   libsystem_platform.dylib            0x00007fff5cef4b5d _sigtramp + 29
[2] 2   ???                                 0x0000000000000000 0x0 + 0
[3] RenderingServerRaster::RenderingServerRaster() (in godot.osx.tools.64) (rendering_server_raster.cpp:252)
[4] RenderingServerRaster::RenderingServerRaster() (in godot.osx.tools.64) (rendering_server_raster.cpp:263)
[5] Main::setup2(unsigned long long) (in godot.osx.tools.64) (main.cpp:1276)
[6] Main::setup(char const*, int, char**, bool) (in godot.osx.tools.64) (main.cpp:1177)
[7] main (in godot.osx.tools.64) (godot_main_osx.mm:70)
[8] 8   libdyld.dylib                       0x00007fff5cd093d5 start + 1
[9] 9   ???                                 0x0000000000000001 0x0 + 1
-- END OF BACKTRACE --
Abort trap: 6

You need to install MoltenVK to have Vulkan drivers in macOS.

You need to install MoltenVK to have Vulkan drivers in macOS.

This is how I got it to run. First, go to the Vulkan SDK Website at LunarXchange to download the Vulkan SDK. After unzipping the archive, use ./install_vulkan.py to have the SDK installed in /usr/local. Then, there will be new demo applications in Launchpad. After restarting the computer, run one of the demo applications to confirm that Vulkan is installed.

You need to install MoltenVK to have Vulkan drivers in macOS.

This is how I got it to run. First, go to the Vulkan SDK Website at LunarXchange to download the Vulkan SDK. After unzipping the archive, use ./install_vulkan.py to have the SDK installed in /usr/local. Then, there will be new demo applications in Launchpad. After restarting the computer, run one of the demo applications to confirm that Vulkan is installed.

I install MoltenVK, it work, but I can't run Godot:
Godot Engine v4.0.dev.calinou.8793a464d - https://godotengine.org
Vulkan API 1.2.162
Using Vulkan Device #0: INTEL - Intel HD Graphics 5000
handle_crash: Program crashed with signal 11
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] 1   libsystem_platform.dylib            0x00007fff2036ed7d _sigtramp + 29
[2] 2   ???                                 0x0000000000000000 0x0 + 0
[3] vkGetPhysicalDeviceProperties2 (in Godot) + 142
[4] VulkanContext::_check_capabilities() (in Godot) + 155
[5] VulkanContext::_create_physical_device() (in Godot) + 6926
[6] VulkanContext::initialize() (in Godot) + 28
[7] DisplayServerOSX::DisplayServerOSX(String const&, DisplayServer::WindowMode, unsigned int, Vector2i const&, Error&) (in Godot) + 4272
[8] DisplayServerOSX::DisplayServerOSX(String const&, DisplayServer::WindowMode, unsigned int, Vector2i const&, Error&) (in Godot) + 57
[9] DisplayServerOSX::create_func(String const&, DisplayServer::WindowMode, unsigned int, Vector2i const&, Error&) (in Godot) + 73
[10] DisplayServer::create(int, String const&, DisplayServer::WindowMode, unsigned int, Vector2i const&, Error&) (in Godot) + 220
[11] Main::setup2(unsigned long long) (in Godot) + 2229
[12] Main::setup(char const*, int, char**, bool) (in Godot) + 39428
[13] main (in Godot) + 982
[14] 14  libdyld.dylib                       0x00007fff20345631 start + 1
[15] 15  ???                                 0x0000000000000001 0x0 + 1
-- END OF BACKTRACE --
Abort trap: 6

@HonestHacker See #47877. This was fixed today.
Closing as the original issue was due to lack of MoltenVK.


Add block exchange protocol

Block Exchange
Allows peers to store, and exchange data blocks between them.
Features

[x] Store and allow the transfer of data blocks #67
[x] A block's key is the hash of it's payload #67
[ ] A block's payload can be split up into multiple ordered chunks
[ ] A block can have additional metadata of key (string) value ([]byte) pairs
[ ] The length of the chunk will be fixes for all chunks, but can be different for each block
[x] A peer can request a block from another peer using its key #67
[ ] A peer can optionally request only the blocks's metadata, or even only specific chunks
[ ] A peer can refuse returning chunks
[ ] Blocks can optionally have white and blacklists of peers who can retrieve them
[ ] Blocks can be optionally signed

Notes

Does the block's hash use only the payload or the metadata as well?
How do we store the blocks so that retrieving specific chunks is cheap?
Can/should we use a Patricia Merkle Tree instead of a list of chunks?
Does it make sense to have acl at the block level?

Literature
Wire protocols

https://github.com/ipfs/specs/tree/master/bitswap
https://zeronet.readthedocs.io/en/latest/help_zeronet/network_protocol
https://github.com/ethereum/wiki/wiki/Ethereum-Wire-Protocol
https://github.com/ethereum/wiki/wiki/Parallel-Block-Downloads
http://www.bittorrent.org/beps/bep_0003.html
https://github.com/hyperledger-archives/fabric/blob/master/docs/protocol-spec.md#3.1-Message
https://docs.syncthing.net/specs/bep-v1.html
https://docs.mongodb.com/manual/reference/mongodb-wire-protocol/

Data structures

https://en.bitcoin.it/wiki/Protocol_documentation#Common_structures
https://github.com/hyperledger-archives/fabric/blob/master/protos/fabric.proto#L89
https://wiki.theory.org/index.php/BitTorrentSpecification#Metainfo_File_Structure
https://github.com/ipfs/specs/tree/master/merkledag
https://docs.syncthing.net/specs/bep-v1.html#protocol-buffer-schema

Block exchange replaced messenger and api is now merged #105


Networkd doesn't restart anymore on unit changes in 20.03

Describe the bug
When you change a networkd option, networkd doesn't pick them up anymore
To Reproduce
Change a networkd option and see it not getting applied
Bisected to https://github.com/NixOS/nixpkgs/commit/1d61efb7f177
Bug was introduced here: https://github.com/NixOS/nixpkgs/pull/63103/files?file-filters[]=.nix#diff-7d08c03fc593d925ed022e395579c866R941
It seems to replace x.source with attrName in restartTriggers however this is a semantic change. restartTriggers should point to derivations, not strings. This breaks  things
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

That PR seems to not only have broken networkd but many other services as well. We should have a closer look

The only other affected service seems to be datadog https://github.com/NixOS/nixpkgs/pull/63103/files?file-filters[]=.nix#diff-05b73b65b3562a8474e78df934f044c2R228
I'll prepare a PR and a backport PR

The fix has been merged to master and 20.09.


[Fix #11762] Fix an incorrect autocorrect for Style/ClassEqualityComparison

Fixes #11762.
This PR fixes an incorrect autocorrect for Style/ClassEqualityComparison when comparing a variable or return value for equality.
when a variable or return value of a method is used, it cannot be suggested and safe autocorrected because the type is not known. So this PR tweaks the cop that doesn't suggest instance_of argument at those times and doesn't autocorrect. Anyway, detection is possible.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[ ] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Thanks!


Creating test set name dynamically

This is a question on how I can name the testSet dynamically - and maybe more of a groovy question. I am new to groovy and gradle so any help is much appreciated.
What I am trying to is create multiple test sets (in a loop). I have a set of names so I am trying to do as follows in my own plugin:
names.each { name ->
            def testSetName = "testName"+name
            project.configure(project) {
                apply plugin: 'org.unbroken-dome.test-sets'
                testSets {
                    testSetName {
                        ...
                    }
                }
...

The testSetName is what I want dynamically added to my project. The above does not work and it fails saying a String cannot be applied to a method expecting a closure. What would be the way to do this?
Thanks

Hi,
The testSets container is just another NamedDomainObjectSet, you'll find a lot of them in Gradle, for example tasks and configurations. There's several ways how you can achieve what you want. Pick the one that you like most :-)
First, you can use the container's create method directly (actually the "dynamic" method is just Gradle's syntactic sugar for calling create):
testSets.create(testSetName) {
    // ...
}

You can also enclose the variable name in a GString, which will trigger the behavior of invoking a dynamic method:
testSets {
    "$testSetName" {
        // ...
    }
}

By the way, I think that project.configure(project) in your example is redundant; configuring the project object is exactly what you are doing already in your build script.
Hope this helps!

Thank you @tkrullmann, exactly what I needed.


Resolving some small typos/grammar errors found in the docs

Fixing some small typos/grammar errors found in the docs.

I have read the Code of Conduct and I hereby accept the Terms

recheck

:tada: This PR is included in version 2.29.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


add support for proxying websockets

When proxying a websocket with --rewrite '/ws/(.*) --> https://someserver.com/ws/$1' local-web-server somehow mangles the response.

lws-rewrite does not currently support rewriting Websocket requests (which can only be proxied via HTTP Connect tunnelling) but i've starting looking for a solution which also honours corporate HTTP proxies.

Hi! Still needing some help with this?
If so, do you have any contributing guidelines or something like this?
We are adopting Open Source Friday here at Banco do Brasil and I can take this one on my Open Source Fridays.

Yes, help welcome thanks.. I should write some contributing guidelines - will add it to my list, thanks.

Any update on this issue? I recently ran into it as well

I solved the issue of forwarding a Next.JS HRM websocket connection by writing some middleware in file proxy/mw-websocket.mjs:
import { WebSocket, WebSocketServer } from 'ws';

const HMR_PATH = '_next/webpack-hmr';

class Websocket {
  middleware(config, lws) {
    const wss = new WebSocketServer({ server: lws.server, path: `/${HMR_PATH}` });

    wss.on('connection', (serverSocket) => {
      const target = `${config.wsRewrite}/${HMR_PATH}`;
      console.log(`WebSocket connection opened; forwarding to ${target}`);

      const clientSocket = new WebSocket(target);
      clientSocket.on('message', (message) => {
        // console.log(`Received from upstream: ${message}`);
        serverSocket.send(message.toString());
      });

      serverSocket.on('message', (message) => {
        // console.log(`Received from browser: ${message}`);
        clientSocket.send(message.toString());
      });
    });
  }
}

export default Websocket;

Configure it as follows. Target address in in property wsRewrite and don't forget to include the middleware in the stack. The stack following the middleware is the default stack, feel free to adjust to your needs:
module.exports = {
  [... your other configuration],
  wsRewrite: 'ws://localhost:4200',
  stack: [
    'proxy/mw-websocket.mjs',
    'lws-body-parser',
    'lws-request-monitor',
    'lws-log',
    'lws-cors',
    'lws-json',
    'lws-rewrite',
    'lws-blacklist',
    'lws-conditional-get',
    'lws-mime',
    'lws-compress',
    'lws-spa',
    'lws-static',
    'lws-index',
  ],
};

Note that this only forwards connections to one specific path and performs absolutely zero error checks, which is fine for my application. Ideally this use case would at some point be supported but for now this is a functioning workaround.


rootNamespace property is never used

The rootNamespace property is never used and has no effect. Responses in format:
{"status":"ok","data":{"contacts":[{"id":"1","firstname":"jack","lastname":"white","prefi ...
Can therefore not be handled by specifying config.rootNamespace = "data"

Thanks for reporting this! It has been fixed now as of:
https://github.com/erkie/ApiModel/commit/2fa29a1a0af4430653c5a7b462877e48ed092a37
I'll make a release soon.

Thanks for reporting this! It has been fixed now as of:
https://github.com/erkie/ApiModel/commit/2fa29a1a0af4430653c5a7b462877e48ed092a37
I'll make a release soon.


Build failure in MacOS with llvm6

Hello experts,
I was trying to build the Hobbes in my laptop with different versions of llvms, I found there seems some interfaces gaps in llvm8 and llvm10 with current Hobbes, so I tried to use the llvm6 to do build, but still always got failure when the make tries to link the hobbies test or hi/hog, could you please help to show some lights on this ?
Here is my env status:
llvm : 6.0.1
cmake: 3.18.0
clang: 11.0.3
Here is the build log failures:
[ 40%] Linking CXX static library libhobbes.a
[ 40%] Built target hobbes
Scanning dependencies of target hobbes-test
[ 41%] Building CXX object CMakeFiles/hobbes-test.dir/test/Arrays.C.o
[ 41%] Building CXX object CMakeFiles/hobbes-test.dir/test/Compiler.C.o
[ 42%] Building CXX object CMakeFiles/hobbes-test.dir/test/Convert.C.o
[ 42%] Building CXX object CMakeFiles/hobbes-test.dir/test/Definitions.C.o
[ 43%] Building CXX object CMakeFiles/hobbes-test.dir/test/Existentials.C.o
^[[B[ 44%] Building CXX object CMakeFiles/hobbes-test.dir/test/Hog.C.o
[ 44%] Building CXX object CMakeFiles/hobbes-test.dir/test/MC.C.o
[ 45%] Building CXX object CMakeFiles/hobbes-test.dir/test/Main.C.o
[ 45%] Building CXX object CMakeFiles/hobbes-test.dir/test/Matching.C.o
[ 46%] Building CXX object CMakeFiles/hobbes-test.dir/test/Net.C.o
[ 46%] Building CXX object CMakeFiles/hobbes-test.dir/test/Objects.C.o
[ 47%] Building CXX object CMakeFiles/hobbes-test.dir/test/PREPL.C.o
[ 47%] Building CXX object CMakeFiles/hobbes-test.dir/test/Prelude.C.o
[ 48%] Building CXX object CMakeFiles/hobbes-test.dir/test/Python.C.o
[ 48%] Building CXX object CMakeFiles/hobbes-test.dir/test/Recursives.C.o
[ 49%] Building CXX object CMakeFiles/hobbes-test.dir/test/Storage.C.o
[ 49%] Building CXX object CMakeFiles/hobbes-test.dir/test/Structs.C.o
[ 50%] Building CXX object CMakeFiles/hobbes-test.dir/test/TypeInf.C.o
[ 50%] Building CXX object CMakeFiles/hobbes-test.dir/test/Variants.C.o
[ 51%] Linking CXX executable hobbes-test
Undefined symbols for architecture x86_64:
"typeinfo for llvm::CallbackVH", referenced from:
typeinfo for llvm::ValueMapCallbackVH<llvm::Value const*, llvm::WeakTrackingVH, llvm::ValueMapConfig<llvm::Value const*, llvm::sys::SmartMutex > > in libhobbes.a(bindings.C.o)
typeinfo for llvm::ValueMapCallbackVH<llvm::Value const*, llvm::WeakTrackingVH, llvm::ValueMapConfig<llvm::Value const*, llvm::sys::SmartMutex > > in libhobbes.a(jitcc.C.o)
typeinfo for llvm::ValueMapCallbackVH<llvm::Value const*, llvm::WeakTrackingVH, llvm::ValueMapConfig<llvm::Value const*, llvm::sys::SmartMutex > > in libhobbes.a(cexpr.C.o)
typeinfo for llvm::ValueMapCallbackVH<llvm::Value const*, llvm::WeakTrackingVH, llvm::ValueMapConfig<llvm::Value const*, llvm::sys::SmartMutex > > in libhobbes.a(signals.C.o)
typeinfo for llvm::ValueMapCallbackVH<llvm::Value const*, llvm::WeakTrackingVH, llvm::ValueMapConfig<llvm::Value const*, llvm::sys::SmartMutex > > in libhobbes.a(dfa.C.o)
"typeinfo for llvm::JITEventListener", referenced from:
typeinfo for hobbes::LenWatch in libhobbes.a(jitcc.C.o)
"typeinfo for llvm::SectionMemoryManager", referenced from:
typeinfo for hobbes::jitmm in libhobbes.a(jitcc.C.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

It looks like travis is able to build on OSX using llvm@6 (using clang-9). Not a macos expert here unfortunately, but can you run the following and compare your output against travis output?
$ export DEPS="${DEPS} readline llvm@6"
$ export LLVM_DIR=/usr/local/opt/llvm@6/lib/cmake/llvm/
$ export CXX=${CXX:-clang++}
$ export CXX_FOR_BUILD=${CXX_FOR_BUILD:-clang++}
$ export CC=${CC:-clang}
$ export CC_FOR_BUILD=${CC_FOR_BUILD:-clang}

$ brew update && brew install -v ${DEPS} && find /usr/local/opt/llvm@6/ | grep cmake;

$ mkdir build && cd build/ && cmake .. && make && make test

Thanks for your quick feedback, I tried the commands as you suggest. Unfortunetely I got error when run home-brew install, I assume this should not be as expected, any ideas, please?
hobbes-master % brew install -v ${DEPS}
hobbes-master % brew install -v ${DEPS}
Error: No available formula with the name " readline llvm@6"
==> Searching for a previously deleted formula (in the last month)...
readline llvm@6 was deleted from homebrew/core in commit 4a992dc515:
wpscan: delete (https://github.com/Homebrew/homebrew-core/issues/59328)==> Searching for a previously deleted formula (in the last month)...
readline llvm@6 was deleted from homebrew/core in commit 4a992dc515:
wpscan: delete (https://github.com/Homebrew/homebrew-core/issues/59328)

Hi jimmy!
That’s a strange formula name, “ readline llvm@6”, maybe two dependencies are getting joined there?
It looks like homebrew still supports 6:
https://formulae.brew.sh/formula/llvm@6#default
Providence also has a nice way to install through nix if you’re interested in trying that path (I think it’s a little more reliable than brew).
Those errors about undefined typeinfo values at link time look like an issue with LLVM not being built with RTTI enabled.  Since hobbes uses RTTI (to make some cases of C++ type binding work), it makes that assumption about LLVM as well.

Hi Kthielen,
Thanks for your suggestions on the RTTI for LLVM building, I tired to remove the brew llvm and download the official llvm6 and do build myself, turn on the option for LLVM_ENABLE_RTTI, then do the Hobbes build again, it works!
Thanks for your help, appreciate it.


edge_list version of diff_pool

🚀 Feature

currently the dense_diff_pool accepts graph adjacency matrix as input.Is there a version such that it can accept edge_index, as in GraphConv?
Motivation

Additional context

Hi, no currently it only accepts dense matrices. A sparse version would also produce dense adjacencies, so this is a bit inconsistent. There is also no memory saving by using a sparse version, because we would need to convert the adjacency to a dense one by ourselves. We could offer a to_dense_adj batch-wise functionality though. I see what I can do.

Added in master.


feat: String decryption transformer

This was one of the main blockers to getting up to 667 deobfuscated. While there's some other changes to get the output compilable (that I think may be better suited as separate commits), this transformer seems to be at a good place to open a PR.
I also included some fixes around handling class scrambling inside packages -- I decided to go with the assumption that classes are not static-scrambled so they get skipped now.
The change in TypedRemapper is just to reduce the console warnings for packaged classes.

I found a couple cases for the inlining to account for still -- some  methods do z[0][index] or z[0].length directly

Thanks, addressed all those points. Let me know how the latest version looks to you and what else may be improved.


[Bug]: Indoor chime not working

Version
0.7.0
Node version
N/A
Operating System type
Linux
Operating system version
Home assistant core-2021.12.9
Describe the bug
Issue #https://github.com/fuatakgun/eufy_security/issues/164 reported on Eufy integration for Home assistant eufy_secutiry, however developer has suggested to report the issue here.
Newest versions have introduced an Indoor Chime switch which I assume is to turn on/off the chime ring after the doorbell button is pressed, however it does nothing. It's always off, regardless and switching on or off, doesn't really change the indoor chime on/off option on the app.
As far as I can tell, this Indoor Switch is related to the Ringtone Settings switch on the app that controls the "Wi-Fi Doorbell Chime Alert" and has described above, it does nothing nor synchronizes with the status of the switch on the app. There is also a Snooze option to snooze Motion or Chime for x amount of time, which may be a good plan B to make this option more reliable as it's useful for periods where it's useful not to have the Chime ringing.
To reproduce

Install eufy_repository on Home assistant and set up
Try switching Indoor Chime switch on / off
Try switching on Eufy app as well

Screenshots & Logfiles
Image of the switch on Home assistant:

Additional context
No response

thanks for sharing a temporary solution, let's wait response on other side, I will just update the library version here.

Afraid that Chime Volume has not stopped working so the temporary solution no longer works.

Changing on the app eventually syncs with Home assistant but not the other way around...

I need the debug logs to find the exact cause.

I need the debug logs to find the exact cause.

Chime Volume is working again, forgot to mention.
I will check if I can extract something from the logs re Chime switch.

Here you go, this is what happens when I switch the Indoor Chime On and Off. Please note that regardless of the status of the switch on the Eufy app, Home Assistant switch always reports Off and if I try to switch it On it always goes back to Off after a few seconds. And as mentioned switching the Indoor Chime switch On and Off has not effect on the Eufy app switch.
- 2022-02-03 10:47:58 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - WebSocket message sent. {"messageId": "device_set_property", "command": "device.set_property", "serialNumber": "T8222P6021280739", "name": "chimeIndoor", "value": "True"}
- 2022-02-03 10:47:58 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - on_message - {'type': 'result', 'success': True, 'messageId': 'device_set_property', 'result': {}}
- 2022-02-03 10:47:59 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - WebSocket message sent. {"messageId": "device_set_property", "command": "device.set_property", "serialNumber": "T8222P6021280739", "name": "chimeIndoor", "value": "False"}
- 2022-02-03 10:47:59 DEBUG (MainThread) [custom_components.eufy_security] eufy_security - on_message - {'type': 'result', 'success': True, 'messageId': 'device_set_property', 'result': {}}

@Zeunas
I need the debug logs from eufy-security-ws and not from another integration...

Ah yes, that makes sense sorry...However not sure how to do it if not via Home Assistant logger, @fuatakgun are you able to shed some light?

Sadly, we can not generate debug logs to share with @bropat inside home assistant. So, you have to run a docker instance manually and redirect your home assistant to the docker instance (not supervisor addon)

@fuatakgun
Since version 0.8.0 there are new commands to control log level and get log messages.
Look here and here.

thanks @bropat for the ping, home assistant UI is only showing last 100 lines of docker logs, users should SSH to machine and read the system logs to get the full logs and it would be hard to extract them from there. That is because, I advised to run a separate / temporary docker container to fetch these logs.

I'd like to report the same issue.
The switching works, the chime does turn on and off, but the switch in Home Assistant always shows off.
When switching, the Home Assistant switch turns on for a few seconds and then turns off itself, but the setting in the Eufy app doesnt change again.
Which specific debug log do you need?

I need the complete debug logs of eufy-security-ws.

Alternatively, I need access to the device with admin rights.

stale


[FEATURE] Animation while loading images.

Description
I want to use framer Motion to make animation while image card are in view

What type of animation you refer to? we already have an ease effect while hovering
please add a video/gif on what animation you're refering to in Framer Motion

Want to Implement this animation
https://github.com/Vijaykv5/Image-Searcher/assets/106283743/193f7448-056e-4ddb-9772-c65444ad1376

It's actually not needed ..I think current one works fine


v1.10 backports 2021-06-04

#16360 -- .github: Fix error triggered by large comments (@pchaigno)
#16190 -- pkg/k8s: add pod IP event change (@aanm)
#16381 -- endpoint: trigger k8s sync controller on identity update (@jibi)
#16374 -- operator: remove deprecated options (@twpayne)
#16373 -- helm: Fix patch failure when updating hubble-generate-certs (@gandro)
#16342 -- docs: Clarify LRP loop related note (@aditighag)
#16323 -- install: Allow setting enable-health-check-nodeport to 'false' (@dctrwatson)
#16273 -- install: fix ordering of operator resource block (@rkage)
#16231 -- test: Use new test-verifier image in K8sVerifier (@pchaigno)

Minor conflicts.

#16118 -- daemon: Improve logging of device auto-detection (@brb)
#16016 -- Clarify one-time setup for backporting (@christarazi)
#16380 -- helm: Disable the bandwidth manager by default (@pchaigno)
#16307 -- k8s, node: Restore router IPs (cilium_host) from K8s resource  (@christarazi)
#16423 -- Update test/packet instructions for running CI tests on dedicated instances (@christarazi)

Once this PR is merged, you can update the PR labels via:
$ for pr in 16360 16190 16381 16374 16373 16342 16323 16273 16231 16118 16016 16380 16307 16423; do contrib/backporting/set-labels.py $pr done 1.10; done

test-backport-1.10

test-1.18-4.9

All tests are passing and the missing reviews are only for backports without conflicts, so I think we can merge. Marking.


fix: disable minify in ssr build

Summary
Related Issue

Checklist

[ ] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

Related issue: https://github.com/web-infra-dev/rspack/issues/4906


Any way to control value directly

Instead of using initialValue...
Something like:
<ReactSimpleMDE
    value: this.props.value
/>

So that it can be controlled by some higher level component?

Can you explain the use case in more detail?
Does setting the initial value using props not get what you wish to achieve? -
<ReactSimpleMDE
    initialValue: this.props.value
/>

it only sets the initial value - so if somewhere higher up the component hierarchy the value changes then currently ReactSimpleMDE doesn't reflect that

Sure, I see what your saying, thanks for pointing out. My simple use case never exposed this issue. I'll be pushing an update shortly.


Backport security fixes already merged on master

Questions
Answers

Description?
backport 2 security fixes that are already merged on master

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?
no

Sponsor company
PrestaShop SA

How to test?
already QAed by @florine2623

@matks Do we need Release 5.1.5 after this PR :stuck_out_tongue_winking_eye: ?


Compare page logo fix || ISSUE #1032

I have added the logo to the compare page.

@sanjay-kv @HimangshuSharma01 Sir, Please merge my PR under hacktoberfest, gssoc-ext labels.
This PR closes the issue #1032

there is conflcits.

@sanjay-kv @HimangshuSharma01  sir, then what I need to do?

Hi @sanjay-kv @HimangshuSharma01 sir, I have resolved the changes. Please accept and approve my PR

# # Resolved Conflicts
I have resolved the issues in the branch. Please accept my PR under gssoc-ext and hacktoberfest labels

@sanjay-kv @HimangshuSharma01


Remove dependency on locally installed docker-compose

docker-compose has an official suggestion on using it from a container instead of installing the binary or python packages.

https://docs.docker.com/compose/install/#install-as-a-container  (go to "Alternative Install Options").
This would bring us a great benefit of not requiring users to install docker-compose (usually an extra step on setting up Docker locally).
Other than that, we would also pin down the version we use and remove unexpected behaviours.

In order to do that I guess we should mimic most of the official shell script into a docker run builder.Command internally.The affected areas would be:
cmd/start.go:42:                builder.NewCommand("docker-compose", "up", "-d", "--force-recreate"),
cmd/checker/checker.go:24:              builder.NewCommand("docker-compose", "ps"),
cmd/shell/shell.go:108: if exe == "docker-compose" {
cmd/shell/shell.go:139: if exe == "docker-compose" {
cmd/stop.go:40:         builder.NewCommand("docker-compose", "down"),
cmd/exec.go:41:         builder.NewCommand("docker-compose", "exec"),
cmd/logs.go:40:         builder.NewCommand("docker-compose", "ps", "-aq"),
cmd/logs.go:41:         builder.NewCommand("docker-compose", "logs"),
cmd/status.go:53:               builder.NewCommand("docker-compose", "ps", "--services"),
cmd/status.go:54:               builder.NewCommand("docker-compose", "ps", "-q"),

The script: https://github.com/docker/compose/releases/download/1.28.0/run.sh

The script: https://github.com/docker/compose/releases/download/1.28.0/run.sh

Implemented, going in the next release.

Implemented, going in the next release.


General Q&A Thread: Quick Questions

How could I lock the weather widget on always show details?
I have tried hideDetails: true and even showFullInfo: true and hideDetails: false with no joy. The default setting is false but setting it won't work.
Also the icon shows night for day and day for night even if  the data is displayed correctly on the site:
hideDetails: false
Config:
widgets:
  - type: weather
    options:
      city: Bucharest, RO
      apiKey: xxxx
      units: metric
  - type: weather-forecast
    options:
      city: Bucharest, RO
      apiKey: xxxxx
      numDays: 6
      units: metric

I indeed confirm that using hideDetails: false as per doc doesn't work...


Per Dave G., find a way to analyses are the most useful

After chatting with Dave G on slack and getting his advice, I drafted up a quick TypeForm here:
https://cfa.typeform.com/to/ODoSQi

[X] Make the survey
[x] Integrate feedback from Jazmyn
[ ] Write out copy for e-mail
[ ] Send the survey out to Inson, Christa, Donna, Jim Byers, Juliana

I should probably send this in the morning fore maximum impact.

Hi _____,

This is Ernie from the Miami-Dade Code for America Fellowship team; I hope you're doing well!

We would appreciate it if you spent less than five minutes answering the questions to this survey - the answers would help shape the tools we build for RER in the upcoming months.

You can find the survey here:
https://cfa.typeform.com/to/ODoSQi

Let me know if you have questions. Thanks!
- Ernie


Maintenance Help

Do you need help maintaining this project?

@mgwidmann we can also help

@mgwidmann, just seeing if you have any plans to add some other contributors to maintain the project?

Anyone want to volunteer to organize a fork?
I didn't see any forks for any of you, the previous commenters, in the network graph for this project:

Network Graph · mgwidmann/scrivener_html

Should I reach out to one of those projects about committing to maintaining a fork?

If @mgwidmann doesn't transfer ownership of the package on Hex, we'd have to pick a new package name too:

FAQ | Hex

I have called for help on how to reach Matt here on the Elixir Forum:
https://elixirforum.com/t/call-for-help-on-scrivener-html-maintenance-can-anyone-reach-matt-widmann/42526

I'm willing to try to maintain a 'community' version in my own fork (that I just created a few minutes ago):

kenny-evitt/scrivener_html: HTML view helpers for Scrivener

@thbar I want to review some of the pending 'community changes' and merge them into my own fork – I'm personally interested in resolving the dependency issues with the newest versions of Phoenix and related packages, but I'm willing to review some other changes if they're sensible and of plausible use to others (and not too much trouble to integrate).

Merged the commits approved by community in https://github.com/goravbhootra/scrivener_html
Happy to add more maintainers and maintain the repo till this one becomes active again

There are a good number of forks with commits:

https://github.com/mgwidmann/scrivener_html/network

And also a good bunch of warnings in the official version:

==> scrivener_html
Compiling 2 files (.ex)
warning: Phoenix.Naming.resource_name/1 defined in application :phoenix is used by the current application but the current application does not depend on :phoenix. To fix this, you must do one of:

  1. If :phoenix is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :phoenix is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :phoenix, you may optionally skip this warning by adding [xref: [exclude: [Phoenix.Naming]]] to your "def project" in mix.exs

  lib/scrivener/html.ex:178: Scrivener.HTML.name_for/2

warning: Phoenix.HTML.__using__/1 defined in application :phoenix_html is used by the current application but the current application does not depend on :phoenix_html. To fix this, you must do one of:

  1. If :phoenix_html is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :phoenix_html is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :phoenix_html, you may optionally skip this warning by adding [xref: [exclude: [Phoenix.HTML]]] to your "def project" in mix.exs

Invalid call found at 2 locations:
  lib/scrivener/html.ex:2: Scrivener.HTML
  lib/scrivener/html/seo.ex:15: Scrivener.HTML.SEO

warning: Phoenix.HTML.raw/1 defined in application :phoenix_html is used by the current application but the current application does not depend on :phoenix_html. To fix this, you must do one of:

  1. If :phoenix_html is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :phoenix_html is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :phoenix_html, you may optionally skip this warning by adding [xref: [exclude: [Phoenix.HTML]]] to your "def project" in mix.exs

Invalid call found at 3 locations:
  lib/scrivener/html.ex:11: Scrivener.HTML
  lib/scrivener/html.ex:123: Scrivener.HTML.pagination_links/4
  lib/scrivener/html.ex:639: Scrivener.HTML.safe/1

warning: Phoenix.HTML.Link.link/2 defined in application :phoenix_html is used by the current application but the current application does not depend on :phoenix_html. To fix this, you must do one of:

  1. If :phoenix_html is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :phoenix_html is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :phoenix_html, you may optionally skip this warning by adding [xref: [exclude: [Phoenix.HTML.Link]]] to your "def project" in mix.exs

Invalid call found at 2 locations:
  lib/scrivener/html.ex:344: Scrivener.HTML.page/7
  lib/scrivener/html.ex:374: Scrivener.HTML.page/7

warning: Phoenix.HTML.Tag.content_tag/2 defined in application :phoenix_html is used by the current application but the current application does not depend on :phoenix_html. To fix this, you must do one of:

  1. If :phoenix_html is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :phoenix_html is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :phoenix_html, you may optionally skip this warning by adding [xref: [exclude: [Phoenix.HTML.Tag]]] to your "def project" in mix.exs

  lib/scrivener/html.ex:204: Scrivener.HTML._pagination_links/2

warning: Phoenix.HTML.Tag.content_tag/3 defined in application :phoenix_html is used by the current application but the current application does not depend on :phoenix_html. To fix this, you must do one of:

  1. If :phoenix_html is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :phoenix_html is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :phoenix_html, you may optionally skip this warning by adding [xref: [exclude: [Phoenix.HTML.Tag]]] to your "def project" in mix.exs

Invalid call found at 18 locations:
  lib/scrivener/html.ex:205: Scrivener.HTML._pagination_links/2
  lib/scrivener/html.ex:222: Scrivener.HTML._pagination_links/2
  lib/scrivener/html.ex:223: Scrivener.HTML._pagination_links/2
  lib/scrivener/html.ex:240: Scrivener.HTML._pagination_links/2
  lib/scrivener/html.ex:256: Scrivener.HTML._pagination_links/2
  lib/scrivener/html.ex:272: Scrivener.HTML._pagination_links/2
  lib/scrivener/html.ex:288: Scrivener.HTML._pagination_links/2
  lib/scrivener/html.ex:289: Scrivener.HTML._pagination_links/2
  lib/scrivener/html.ex:313: Scrivener.HTML.page/7
  lib/scrivener/html.ex:319: Scrivener.HTML.page/7
  lib/scrivener/html.ex:322: Scrivener.HTML.page/7
  lib/scrivener/html.ex:340: Scrivener.HTML.page/7
  lib/scrivener/html.ex:351: Scrivener.HTML.page/7
  lib/scrivener/html.ex:365: Scrivener.HTML.page/7
  lib/scrivener/html.ex:370: Scrivener.HTML.page/7
  lib/scrivener/html.ex:383: Scrivener.HTML.page/7
  lib/scrivener/html/seo.ex:84: Scrivener.HTML.SEO.prev_header_link/4
  lib/scrivener/html/seo.ex:89: Scrivener.HTML.SEO.next_header_link/4

warning: Plug.Conn.Query.encode/1 defined in application :plug is used by the current application but the current application does not depend on :plug. To fix this, you must do one of:

  1. If :plug is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :plug is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :plug, you may optionally skip this warning by adding [xref: [exclude: [Plug.Conn.Query]]] to your "def project" in mix.exs

  lib/scrivener/html.ex:60: Scrivener.HTML.Default.path/3

Generated scrivener_html app

It would be cool to find a way to consolidate something here or elsewhere & consolidate it as the official version as a package (https://hex.pm/packages/scrivener_html).

@thbar Did this ever get resolved or did anyone hear back from @mgwidmann?
It does not appear so
Seems like this could be an alternate option: https://github.com/julp/scrivener_phoenix

I've made an alternative based on Phoenix.Component, so it doesn't require phoenix_html_helpers and is more Phoenix 1.7 and LiveView friendly: https://github.com/Tricote/scrivener_components/. There is only the BootstrapV5 pagination component for now, but if anyone is interested in contributing, it should be quite straightforward to add...


Inconsistent background color

version 1.71 window control button have different background color

/duplicate https://github.com/microsoft/vscode/issues/159671


[enhancement] Currently, Openetelemetry does not support Jedis4.0 Instrumentation

When the user uses the version of Jedis4.0 or above, the span of Redis will not be generated, can this be supported?

I will do it.


feat: supports rename for 'kcl mod add'

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[x] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[x] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

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 15.591%

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
99

Relevant Lines:
635

💛  - Coveralls


Tiered SMT delete soundness issue

In #1046 we implemented basic delete functionality (i.e., without support for the last tier deletions) for TSMT implementation in stdlib. While this implementation works, on case of the delete procedures has a soundness issue because it relies on the advice provider supplying correct data.
The specific case is when we need to remove a leaf node from TSMT. Currently, this is done non-deterministically. Specifically:

The advice providers performs the deletion and provides the root of a new TSMT to the VM.
The VM performs insertion into the TSMT defined by this root, and checks this against the original root.
If the root post insertion is the same as the original root, then we can say that the root provided by the advice provider is the root resulting from deleting the specified key from the original TSMT.

The issue with the above approach is that our insert procedure assumes that the TSMT it works with is valid. However, in this case, the advice provider could provide an invalid TSMT. For example:
Let's say we have a TSMT with root R and two leaves: A and B. Keys for these leaves share the same 16-bit prefix, and thus, both of them are located at depth 32. Now, let's say we want to delete A. The proper deletion would remove A and move B up to depth 16. The root of the new tree would be R_new. Then the VM can insert A into R_new and if all was supplied correctly, it'll get R.
However, if a malicious user provides R_bad instead of R_new to the VM, and in this R_bad, A is removed, but B is not moved up to tier 16, inserting A into R_bad would also output R. So, the VM would accept R_bad as the new root of the TSMT.
I think it would be too difficult to ensure that insert procedure checks the validity of the entire tree. But it seems to me that implementing deletions without use of this kind of non-determinism should not be too compliated.

Yes, although I think it can be patched, it is an issue. A patch could be to provide data to justify the depth at which the insertion into R_new is done. This can be two non-empty nodes that are checked for inclusion as part of the deletion procedure.
Another solution, as you suggested, is to implement the deletion procedure in a direct manner. My worry is that this might be very complicated but there might be some opportunities to use non-determinism to speed-up some parts of it.

Giving this some thought.

Closed by #1215 because we no longer will use TSMT.


next.js withGluestack fails in nx monorepo

Description
service next fails due to withGluestack looking for node_modules in the wrong location
CodeSandbox/Snack link
No response
Steps to reproduce

generate a new nx repo with next.js:
npx create-nx-workspace@latest &&
nx g @nx/next:app frontend

follow instructons to add gluestack manually

follow the code in template repo to make sure everything is correct https://github.com/gluestack/gluestack-ui-nextjs-app-router-template

start serving the app nx serve frontend

nx serve frontend

> nx run frontend:serve:development

- ready started server on <IP_ADDRESS>:4200, url: http://localhost:4200
Error: ENOENT: no such file or directory, scandir '/Users/evanion/Projects/Personal/courses/courses/apps/frontend/node_modules'
    at Object.readdirSync (node:fs:1446:3)
    at traverseFolder (/Users/evanion/Projects/Personal/courses/courses/node_modules/@gluestack/ui-next-adapter/dist/ui-next-adapter.cjs.development.js:63:18)
    at getExactDependenciesFromNodeModules (/Users/evanion/Projects/Personal/courses/courses/node_modules/@gluestack/ui-next-adapter/dist/ui-next-adapter.cjs.development.js:82:25)
    at withGluestackUI (/Users/evanion/Projects/Personal/courses/courses/node_modules/@gluestack/ui-next-adapter/dist/ui-next-adapter.cjs.development.js:159:33)
    at /Users/evanion/Projects/Personal/courses/courses/node_modules/@nx/next/src/utils/compose-plugins.js:12:40
    at Generator.next (<anonymous>)
    at fulfilled (/Users/evanion/Projects/Personal/courses/courses/node_modules/tslib/tslib.js:164:62) {
  type: 'Error',
  errno: -2,
  syscall: 'scandir',
  code: 'ENOENT',
  path: '/Users/evanion/Projects/Personal/courses/courses/apps/frontend/node_modules'
}
 >  NX   Next.js app exited with code 1
   Pass --verbose to see the stacktrace.

 ——————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 >  NX   Running target serve for project frontend failed

   Failed tasks:

   - frontend:serve:development

   Hint: run the command with --verbose for more details.

   View structured, searchable error logs at https://cloud.nx.app/runs/7PgIjSlgnd

gluestack-ui Version
2.1.5
Platform

[ ] Android
[ ] Expo
[ ] iOS
[X] Next

Other Platform
nx
Additional Information
It seems like withGluestack is looking in the project root, but it's located two directories up, but I can't find any config that I can pass to tell gluestack where to look, and it seems like the yarn workspace package doesn't support nx.

Hi @Evanion , I was able to run next project with gluestack with nx monorepo.  Although, I don't have much idea about nx-monorepo. Can you please share the next config file and the project structure?

@makkarMeenu here is a reproduction repo with nx, next and gluestack
https://github.com/Evanion/reprod-gluestack
When the withGluestackUI is commented out, it fails to load the react-native parts, and with the withGluestackUI plugin enabled,  it fails with Error: ENOENT: no such file or directory, scandir '<path to repo root>/apps/frontend/node_modules'

Had to reorder and place the withGluestackUI plugin before withNx plugin. And now it works, thank!


💡 [FEATURE] - Design a Website for the resources

Idea Contribution

[X] I have read all the feature request issues.
[X] I'm interested in working on this issue
[X] I'm part of GSSOC organization

Explain feature request
So in order to make the resources easily availableto everyone i would like to make a website with basic html css concepts and would like to attach the resource links attached there .
Thank You :)
Regards
Explain your solution
No response
Any alternative approaches/features
No response
Additional Context
No response

The wbesite is currently in development


The tag ID

I have a quick question about the tag ID.
1.) Is it unique?
2.) Can a user override it(So if someone clone a card?)?
I just want to know if i can rely on it being secure. Or if i would build a unique set of ID myself then lock the card up??

It depends on the tag type. Mifare Classic 4 byte ids are reused. I think most 7 byte ids on other tags should be unique, but you'd need to check with the tag manufacturer to be sure.
You're not supposed to be able to change the tag id. I've heard of non-conformant tags that let you change the id, but I've never used one.

Even you cannot prevent users from cloning your tag you can store the Id
and make sure you store the tag id associated with the content.
To encrypt I use an sha256 library.
Allan
On Oct 8, 2015 10:25 AM, "Don Coleman"<EMAIL_ADDRESS>wrote:

It depends on the tag type. Mifare Classic 4 byte ids are reused. I think
most 7 byte ids on other tags should be unique, but you'd need to check
with the tag manufacturer to be sure.
You're not supposed to be able to change the tag id. I've heard of
non-conformant tags that let you change the id, but I've never used one.
—
Reply to this email directly or view it on GitHub
https://github.com/chariotsolutions/phonegap-nfc/issues/206#issuecomment-146578459
.

@allannaranjo  but if someone use a card emulator and clone the whole thing, and when the server reads it and decrypt it, the replica card would be able to cause action to the db tho. but thanks for the advice anyway.
On NXP documentation they said they have the "anti-cloning" mechanism but i am not sure if it is as tough as it says....


Remove the const_generics feature flag

Currently, the "unstable" feature no longer compiles on recent nightly
Rust toolchains, because it enables the const_generics feature flag.
Since const generics have stabilized, this feature flag is no longer
necessary, and results in a compilation error on recent toolchains.
This commit removes #[feature(const_generics)] from the crate. Now,
the "unstable" feature builds on recent nightly compilers. Additionally,
we can remove the "unstable" feature flag from the impls for converting
volatile arrays to slices, as that impl no longer requires an unstable
feature.
In order to make the tests pass on stable Rust after removing the
unstable feature flag from the impls for arrays, I had to modify the
examples so that they no longer use other unstable methods, such as
copy_from_slice. I think the new examples still get the point across,
although they're maybe not quite as nice...
Fixes #24

Published as version 0.4.5

Thanks a lot! Sorry for the late review.

No worries, thanks for the new release!


Database / App Setup

Boiler Plate Stuff

Updated boilerplate schema to handle our dataset. Will create new ticket to handle test cases for schema setup


Update benchmark and control tags for compatibility with dashboard page Closes #10

On hold for conversation - breaking change? controls/vcn.sp


Will the next version be 3.3.+ or 3.4?

What problem does this feature solve?
thanks
What does the proposed API look like?
thanks

Hi, thanks for your interest but GitHub issues are for bug reports and feature requests only. You can ask questions in Discussions or our Discord server.


failure hooks

Need to be able to call a hook on task failure so that users can be notified of failures. For example, something using IFTTT could look like this:
def failure_callback(task, exception, pk):
    import requests
    data = {
        'Value1': task,
        'Value2': exception,
        'Value3': pk,
    }
    requests.post('https://maker.ifttt.com/trigger/my_ifttt_trigger/with/key/my-ifttt-key',  data)

This is now implemented. Here is a working example, where a failure callback is used to attempt a task 5 times before failing:
my_project/my_app/consumer.py
from carrot.utilities import publish_message

def failure_callback(log, exception):
    if log.task == 'myapp.tasks.retry_test':
        logger.critical(log.__dict__)
        attempt = log.positionals[0] + 1
        if attempt <= 5:
            log.delete()
            publish_message('myapp.tasks.retry_test', attempt)

class CustomConsumer(Consumer):
    def __init__(self, host, queue, logger, name, durable=True, queue_arguments=None, exchange_arguments=None):
        super(CustomConsumer, self).__init__(host, queue, logger, name, durable, queue_arguments, exchange_arguments)
        self.add_failure_callback(failure_callback)

my_project/my_app/tasks.py
def retry_test(attempt):
    logger.info('ATTEMPT NUMBER: %i' % attempt)
    do_stuff()

my_project/my_project/settings.py
...
CARROT = {
    'default_broker': vhost,
    'queues': [
        {
            'name': 'default',
            'host': vhost,
            'consumer_class': 'my_project.consumer.CustomConsumer',
        }
    ]
}

Presuming do_stuff() fails on all of the 5 attempts (it isn't defined here so it will), this gives you a single failed task which looks like this in the monitor:


MP abnormal cytokinesis

elongated multinucleate multiseptate vegetative cell, single septa between nuclei (FYPO:0001253) [single allele genotypes]
is a cytokinesis failure so should have abnormal cytokinesis parent\

They do show up on the term page for abnormal cytokinesis. If the search doesn't find the same genes, that seems like a question for Kim about search behavior.

just to check
I don't see
elongated multinucleate multiseptate vegetative cell, single septa between nuclei
on the abnormal cytokinesis page, but I do see
elongated multinucleate multiseptate vegetative cell, irregular septum position
inviable elongated multiseptate vegetative cell with fragmented DNA
which seem very similar?

Hmm. I looked specifically for FYPO:0000118 'multiseptate vegetative cell' when I last commented. It's odd, though, and definitely one for Kim to look at, because FYPO:0000133 'elongated multinucleate vegetative cell' appears on that page, and FYPO:0001253 is_a FYPO:0000133. I therefore don't understand why FYPO:0001253 wouldn't be on the FYPO:0000032 page if FYPO:0000133 is.
Closing here, because the ontology is OK.


check whether self-hosted action runner is still necessary when utilising multiple cores

https://github.com/robertsLando/pkg-binaries/pull/9 introduced using all the cores available for compiling. It might be possible that that is sufficient for compiling below 6 hours which would make it runnable n GitHub action runners.
Specs:
https://docs.github.com/en/actions/reference/virtual-environments-for-github-hosted-runners#supported-runners-and-hardware-resources
Limitations:
https://docs.github.com/en/actions/getting-started-with-github-actions/about-github-actions#:~:text=Usage limits,-There are some&text=Job execution time - Each job,apply to self-hosted runners.

@n1ru4l Let me know about the PR, the build in my self hosted machine tooks 6h 0' 10'', I think that with latest fixes and with github runners it will for sure stay under the 6h limits

Yes, I will hopefully have some to do it this evening! I was busy yesterday.


Submit for inclusion in F-Droid

Ideally with an open source app, this can be made available on F-Droid for people who prefer not to use Google Play.
F-Droid's docs for getting included in their app is here:
https://f-droid.org/en/docs/Inclusion_How-To/

While we're not using Google Play services now, we plan on doing so when we add location tracking and push notifications.
Also F-Droid already has an Home Assistant app that uses our logo and name while not being allowed: https://f-droid.org/en/packages/io.homeassistant.android/ . The listing has been made without the knowledge of the author of that app.  I complained to F-Droid over 2 years ago, including follow up, and they never took any action.
So nah, even if we could, I wouldn't be interested in publishing our app there.

Officially share on Github release apks then. Thanks !

@balloob It's common for apps to have compile-time options to build sans Google libs. Would you be open to adding such a feature?

You're better off forking the project and creating your own app.
Since Home Assistant will provide the UI via a webview, all parts that this app will provide are going to be things that tie into the operating system: push notifications, location tracking, etc. Those things generally tie into Google Play Services.

add location tracking and push notifications

Both of these things can be easily implemented without bundling Google spyware and breaking compatibility with AOSP/degoogled ROMs.  For example, when it detects the absence of the aforementioned spyware, the Signal android app implements push notifications with an autostarted background service and a websocket connection.  This is also the approach used by the Android client for Gotify, a self-hosted push notification server.  The Gotify source code license (MIT) is compatible with this repository's license (Apache 2.0), so code could be copypasted from Gotify without legal issues.
Location tracking could be implemented in the same background service as the push notifications.
The only difference noticeable to the app user is that Android requires a persistent notification when an app is running a background service.  However, it is trivial for the user to block/mute this persistent notification. The background service will continue to run, but will not show a notification while doing so. This block/mute does not prevent the app from displaying push notifications.
Currently on my phone running LineageOS, there are several open source apps running persistent background services for receiving push notifications, checking location, and other features. These apps include KDE Connect (which can receive files from my computer), AsteroidOS Sync (communicates over Bluetooth to my Linux smartwatch and periodically updates the watch with the weather for my location), Signal (receives push notifications for incoming encrypted messages), and Gotify (receives notifications from my self-hosted push notification server).
To summarize, there is no excuse for a popular open source application, especially one that lists "reclaim your privacy" as a feature, to rely on closed-source, proprietary, anti-freedom, anti-privacy, and anti-user code supplied by a corporation more powerful than many nation-states which makes billions of dollars by selling private user data.

Also F-Droid already has an Home Assistant app that uses our logo and name while not being allowed: https://f-droid.org/en/packages/io.homeassistant.android/ . The listing has been made without the knowledge of the author of that app. I complained to F-Droid over 2 years ago, including follow up, and they never took any action.
So nah, even if we could, I wouldn't be interested in publishing our app there.

Hi @balloob,
this just got to my attention while searching through old issues. I for some reason didn't get any notification back then, seems you'd have had to mention me for that.
First of all, sorry for the trouble the F-Droid listing of my app caused for you. The thing is, after you contacted me, I rebranded most of the app, changed the name, made it obvious in the repo that the app is unofficial, and even did some work on a new icon, which I unfortunately didn't implement anymore.
And there's also a part of the problem, lack of time, changes to Home Assistant which made my app more and more pointless (especially Lovelace, which just doesn't make any sense and isn't possible to reimplement natively) and a general attention shift to (to me) more important things caused me to completely forgot about the app (and this problem), so that I now can't even remember anymore that I once published it to F-Droid. Also, the latest F-Droid version still carries the old name as a result..
In retrospective, I realize what a shitty move this all has been, especially because I took the obvious package name as well (seems I really wanted to make an official app back then, not thinking that also you & the core dev team have to accept it).
Again, I'm really sorry about that. Since the app is mostly abandoned anyway, I'll have a look if I can get it removed from F-Droid, to make place for the official app, if you one time decide to publish it there. Even if not, I don't want to be the blocker for that anymore.

Hi. The PR to remove the app made this catch my attention.
First of all: Our apologies! We never meant to tread on anyone's trademark, or give the wrong impression about the homeassistant.io project by packaging an app.
Since the app was originally packaged we have changed our policies to require the original author of the app to be informed and approve the packaging of the app. (See the request for packaging issues where author consent is on the checklist).
Should there be interest in publishing this, or another homeassistant app on the f-droid repository please feel free to reach out. We could, for instance, package a branch that doesn't depend on any proprietary services, a number of other apps use this approach.

Thanks for the reply both of you.
We have no interest in maintaining a branch of the app that doesn't depend on any proprietary services.

We have no interest in maintaining a branch of the app that doesn't depend on any proprietary services.

Shame. I thought this was a mature open source project.  Guess I was wrong.
I wonder, what percentage of Home Assistant users are using it because they value privacy and want to own their devices?  How many of those are willing to throw both of those principles away for a single Android app?

I guess we're not a serious or mature open source project 🤣
👋

See https://github.com/home-assistant/home-assistant-android/issues/124#issuecomment-604561816


Docker Installation

Where can I find how to install, configure and use TensorTrade (docker version) for Windows?
Which version is the latest and official?
https://hub.docker.com/search?q=tensortrade&type=image

The dockerfile is provided within the master source repository. Please use this one not a hosted model from dockerhub.


OSM File Loader and multiprocessing trigger multiple Authorization Expiration messages

Hi @ThomasEmge,
Again a rare corner case that is actually probably an ArcGIS core issue, and not a Loader issue, but I thought I would report it anyway.
Since my subscription for ArcGIS was near to its end, I now noticed the OSM File Loader's multiprocessing steps trigger multiple Authorization Expiration messages, one for each process spawned. So, as you can see in the screenshot below, when I set 4 cores in the geoprocessing environment settings, 4 warning boxes pop-up.
This is not really a big deal, because fortunately, the pop-ups / expiration messages are being closed automatically during the loading process once the python.exe processes are shut down upon finishing a multiprocessing step.
Still, this is mildly annoying behaviour. In case someone runs a hefty XEON workstation with potentially something like 24 cores, it is not unthinkable they will set the multiprocessing factor to 24 as well and get 24 pop-ups.
I guess this - likely ArcGIS core - issue is already known with ESRI and registered, so there is probably nothing to do for you here, but it is good to be aware of it.

Yes, this is core behavior. You can disable the warning by using the AdvancedArcMapSettings.exe application in the Desktop10.4\Utilities installation folder. Choose the Miscellaneous tab and uncheck the license warning on the bottom of the dialog.


Can not update a kotest-extension to its latest release

[x] I have read the guidelines for submitting issues

🐛 Describe the bug

All kotest-extensions are grouped under the same alias, thereby using the same version, although all extensions are independently maintained.
✅ Expected behavior

All kotest-extensions should be independently versioned. Or in some way be able to override the default aliases provided by this library.
💣 Steps to reproduce

The following build.gradle.kts:
dependencies {
    testImplementation("io.kotest.extensions:kotest-extensions-spring:_")
    testImplementation("io.kotest.extensions:kotest-extensions-pitest:_")
}

Generates the following versions.properties when running ./gradlew refreshVersions:
version.kotest-extensions=1.0.1
##            # available=1.0.2
##            # available=1.0.3
##            # available=1.0.4
##            # available=1.0.5
##            # available=1.0.6

But the latest version of kotest-extensions-spring (as of writing) is 1.1.0, and the latest of kotest-extensions-pitest is 1.0.1.
Setting version.kotest-extensions=1.1.0 fails the download of kotest-extensions-pitest (as expected).
Attempt to adding the artifacts explicitly tags them as "unused", making it not possible to override this behavior:
## unused
version.io.kotest.extensions..kotest-extensions-spring=1.1.0

## unused
version.io.kotest.extensions..kotest-extensions-pitest=1.0.1

version.kotest-extensions=1.0.1
##            # available=1.0.2
##            # available=1.0.3
##            # available=1.0.4
##            # available=1.0.5
##            # available=1.0.6

Hello again, this should be fixed in 0.30.1


Typesafe marking and general refactoring

NOTE: This is based on mw-uninterpret: that should be merged first?
This mainly refactoring PRQ:

Removes Unmarked: every instance where a variable could be unmarked now has this reflected in the variable type (Var vs MarkedVar);
Makes all of the backends use the same MarkedVar to string converter: this is the one previously used only for HSF.  This means Z3 output will use VfooA instead of foo!after;
Accidentally put the heap-explicit version of the lclist in with the above… oops.

Okay. Looks good to me.  Just two small things
I am having a slight issue running NUnit I get exceptions for

Starling.Core.GuardedView+Tests+NUnit
Starling.Tests.Instantiate+InstantiateTests
Starling.Tests.Optimiser+OptimiserTests

One full exception follows:
SetUp failed for test fixture Starling.Tests.Optimiser+OptimiserTests
An exception was thrown while loading the test.
System.NullReferenceException: Object reference not set to an instance of an object.
   at NUnit.Framework.Internal.AsyncInvocationRegion.IsAsyncOperation(MethodInfo method)
   at NUnit.Framework.Internal.Builders.NUnitTestCaseBuilder.CheckTestMethodSignature(TestMethod testMethod, TestCaseParameters parms)
   at NUnit.Framework.Internal.Builders.NUnitTestCaseBuilder.BuildTestMethod(IMethodInfo method, Test parentSuite, TestCaseParameters parms)
   at NUnit.Framework.TestCaseSourceAttribute.<BuildFrom>d__16.MoveNext()
   at NUnit.Framework.Internal.Builders.DefaultTestCaseBuilder.BuildFrom(IMethodInfo method, Test parentSuite)
   at NUnit.Framework.Internal.Builders.NUnitTestFixtureBuilder.AddTestCasesToFixture(TestFixture fixture)
   at NUnit.Framework.Internal.Builders.NUnitTestFixtureBuilder.BuildFrom(ITypeInfo typeInfo)
   at NUnit.Framework.Internal.Builders.DefaultSuiteBuilder.BuildFrom(ITypeInfo typeInfo)
NUnit Adapter <IP_ADDRESS> executing tests is finished

Minor nit, it would be good if stuff didn't disappear in one commit, and then appear in a later one.  Makes it harder review.

@mjp41 I have an awful feeling I've accidentally pushed a version with an infinite loop in it.  If it's the same one I had earlier this week I've already fixed it.  I keep forgetting I'm not in a lazy pure language anymore…
  Was hoping I wouldn't have messy PRQs again, but the problem is I keep trying to make minor changes, then realising they snowball into bigger changes, then keep changing my mind several times about the implementation mid-flight, then before I know it I've spent 3 days on one commit and can't easily break it up.

Can you add that fix to this pull request?  So I can put it into master.

@CaptainHayashi  Can you add the fix? Will this affect the test cases that are failing for me?

Hmm, on second look mw-typesafe-mark is passing 100% for me…  Odd

NUnit is passing 100% for me too. What's the best way to narrow this down?

So can you confirm it is actually running the test "GFunc with no guard and no parameters has no variables".  On mine it is failing to even find this test with a NPE, and then happily reports success.

So there is also an issue with this PRQ and the hsf output.  It generates the following at the top for -s hsf for the Ticket Lock example (before the query_naming secion):
emp(serving, ticket) :-
    serving = 0,
    ticket = 0.
v_holdLock_holdLock(serving, ticket) :-
    false.
false :-
    v_holdLock_holdLock(serving, ticket).

But should generate
emp(Vserving, Vticket) :-
    Vserving = 0,
    Vticket = 0.
v_holdLock_holdLock(Vserving, Vticket) :-
    false.
false :-
    v_holdLock_holdLock(Vserving, Vticket).

I think it is using the same map as the query_naming for the View Definitions.
https://github.com/septract/starling-tool/blob/mw-typesafe-mark/Horn.fs#L305-L313

@mjp41 Ah, good catch… maybe we need some HSF regression tests at some point.
Am trying to find out how to kick NUnit into telling me whether it's run the offending test.  I've had this issue with it before when it gives me failures on Windows and passes on Mono.

@mjp41 Ok, I can't work out whether my tests are running it.  All I can say is that I'm getting 157 passes.
On the test you mentioned, I've noticed the type of some of the incoming test data is ambiguous, so I've tightened it up and will be pushing soon.  I'll look at the other failing tests to see what sticks out.  I don't know if this fixes it, but if nothing else I can check on my desktop tonight.

So I have a 123 tests run.  So it is some difference between Mono and Windows.
That didn't help either.

Hmm… It is definitely running the tests on my end, because commenting out the GFunc test dropped it to 156.

@CaptainHayashi do you think it could related to
https://github.com/nunit/nunit/issues/1346

So changing
 member this.``testVarsInGFunc`` gf =

with
 member this.``testVarsInGFunc`` (gf : MGFunc) =

Fixes the first one.  It had inferred a generic type for the gf, the internals were not pinned down.

This commit fixes the tests on Windows.  I think we can merge now.


do not clone gltf binary data

change parseBinaryGltf to not clone the typedarray. Typedarray operations are really slow in internet explorer 11.
Advantages:

much better gltf loading characteristics in ie11

Disadvantages

the underlying buffer has to stay in main memory until the b3dm gets unloaded

After updating to Cesium 1.36 we saw much worse performance in ie11 with 3d-tilesets during tile loading, this change helps a lot.

Welcome to the Cesium community @jbo023!
Can you please send in a Contributor License Agreement (CLA) so that we can review and merge this pull request?
I noticed that CHANGES.md has not been updated. If this change updates the public API in any way, fixes a bug, or makes any non-trivial update, please add a bullet point to CHANGES.md and comment on this pull request so we know it was updated. For more info, see the Pull Request Guidelines.
I noticed that a file in one of our ThirdParty folders (ThirdParty/, Source/ThirdParty/) has been added or modified. Please verify that it has a section in LICENSE.md and that its license information is up to date with this new version. Once you do, please confirm by commenting on this pull request.
I am a bot who helps you make Cesium awesome! Thanks again.

@jbo023 you are covered under an existing CLA so you can just ignore the above CLA message.  I'll add your GitHub username to the list so that the concierge knows this in the future.
Thanks again for the PR.

@jbo023 thanks for looking at this, I'm not 100% sure that we will want this change given the code comment just about the line.
@lilleyse can you please evaluate?

The change should be fine since Batched3DModel3DTileContent will release the glTF json, which includes this buffer.
The clone served a dual purpose originally, to also ensure the glb buffer started on the correct byte alignment. But as the code is written now none of the gltf parsing requires byte alignment.
So basically I am fine with this change.

Since https://github.com/AnalyticalGraphicsInc/cesium/pull/5783 will go into gltf-pipeline ultimately, can you add yourself to the contributors section in this PR?
Thanks for all the recent bug fixes and improvements!

@lilleyse Thanks for the review,
i found one problem with this code change. Animated Models didn't work anymore because of a problem in the following line: https://github.com/AnalyticalGraphicsInc/cesium/blob/master/Source/Scene/ModelAnimationCache.js#L83
Here the code access directly access the underlying ArrayBuffer without taking into account the byteoffset of the TypedArray.
Can you think of more occurences where the code directly access the underlying array buffer?

Good find on the animations.
GltfPipeline/parseBinaryGltf should probably be changed to use a DataView instead of ComponentDatatype.createArrayBufferView in case the glb is not aligned correctly within the b3dm (assuming these changes take effect: https://github.com/AnalyticalGraphicsInc/cesium/pull/5784#discussion_r135825102).
I can't find any other cases right now.

Maybe best to leave https://github.com/AnalyticalGraphicsInc/cesium/pull/5784#issuecomment-325733894 and https://github.com/AnalyticalGraphicsInc/cesium/pull/5784#discussion_r135825102 for another PR.

@jbo023 can you add yourself to CONTRIBUTORS.md here, since #5783 went into gltf-pipeline?

Thanks @jbo023!


[Production] Allow parallel Dropzone uploads

Steps

Go to staging.osf.io and log in.
Create a new project.
Select multiple files to upload a once. e.g. a.txt, b.txt, c.txt.

Expected
Multiple files should upload at the same time to provide the user an optimal experience.
Actual
When uploading many small files, files are uploaded one at a time with significant delays.
A Bit of History
The parallelUploads option was reduced to 1 as interacting with GitHub (git in general) requires all operations be synchronous for structured commit history.
It would be optimal if we could dynamically adjust DropZone when files are being uploaded to a GitHub repo to be synchronous while allowing for up to 10 asynchronous uploads to other providers.
https://github.com/CenterForOpenScience/osf.io/blob/3b5d9f36525432e9c29f1d846dff649bf00d422c/website/static/js/onboarder.js#L522
https://github.com/CenterForOpenScience/osf.io/blob/ec02891986a23a1a1c70c31669ff95b59d785013/website/static/js/fangorn.js#L2094

Chris' PR addresses this issue: https://github.com/CenterForOpenScience/osf.io/pull/3356


Checking included files not working

Hi,
Good tool!
From #17, it's indicated that your tool can check multi-file projects (where a main.typ uses include statement to include other files). For me, this doesn't seem to work at the moment (using an --extern-jar, not LSP, and for any combination of specifying root and main as CLI arguments):
> cat main.typ
= Hello

this is an mistake

#include "sub.typ"
> cat sub.typ

also an mistake

> typst-languagetool check --jar-location=languagetool.jar --main=main.typ --root=.

Checking Document

info[EN_A_VS_AN]: Use of 'a' vs. 'an'
 --> main.typ:3:9
  |
3 | this is an mistake
  |         -- info: Use <suggestion>a</suggestion> instead of 'an' if the following word doesn't start with a vowel sound, e.g. 'a sentence', 'a university'.
  |           - help: a
  |

It seems to only be checking the main.typ, not sub.typ. Any idea what I'm doing wrong?
Cheers,
Henk

I designed the API for Editor first and CLI second.
At the moment you need to add --path=sub.typ to check sup.typ (and only sub.typ).
I am going to change the default behaviour to display all mistakes for CLI + Check + No Path.

Ok great! If multi-file projects with include statements are not supported for CLI, I'll try to set it up then for my editor, as I can't compile separate files in my larger project without breaking compilation.


TypeError: Cannot read property 'NextShardIterator' of undefined

Got the following stack trace/error:
/home/jason/Repos/webin8-bot/node_modules/kinesis/index.js:161
    if (res.NextShardIterator == null) {
           ^
TypeError: Cannot read property 'NextShardIterator' of undefined
    at /home/jason/Repos/webin8-bot/node_modules/kinesis/index.js:161:12
    at f (/home/jason/Repos/webin8-bot/node_modules/kinesis/node_modules/once/once.js:17:25)
    at /home/jason/Repos/webin8-bot/node_modules/kinesis/index.js:395:16
    at IncomingMessage.<anonymous> (/home/jason/Repos/webin8-bot/node_modules/kinesis/index.js:344:20)
    at IncomingMessage.emit (events.js:129:20)
    at _stream_readable.js:908:16
    at process._tickCallback (node.js:355:11)

This is on a stream where I am only reading events.

Woah, that's weird – that means the response is undefined.
Ah, I guess it's probably this: https://github.com/mhart/kinesis/blob/master/index.js#L395
I should construct an error there if we've reached the max number of retries

Although... that doesn't really make sense either because err wouldn't be null in that case.
So it's come from here: https://github.com/mhart/kinesis/blob/master/index.js#L344
So somehow the JSON is parsing as null? That doesn't make sense either.
Can you reproduce easily?

Or it could be that Kinesis has returned an empty response somehow, so this line is false: https://github.com/mhart/kinesis/blob/master/index.js#L340
But it would be weird to return an empty response with a 200.
Any more info you can give (a reproducible case, Node.js version, etc) would help track it down hopefully.

This was just a one off error, can't really reproduce. I have been running this script for weeks and this is the first I've seen it.

Tricky. Ok, thanks. I'll have a bit more of a think about it.

node v0.12.7 and the latest kinesis 1.2.2

Going to close this – if there's an easy way to reproduce, happy to reopen


No executable found matching command "dotnet-ef"

I have changed my ASP.NET Core app to target .Net 4.5.2 (before it was a Net Core app) in order to support WCF Relay.
I have the Migrations and DB Context in a different project (With the Program.cs and everything) and was working fine before changing the target and updating.
Now, after upgrading EF Core and changing the target of the solution I get the message in the title.
Here is my project.json
{
  "version": "1.0.0-*",
  "buildOptions": {
    "emitEntryPoint": true
  },

  "dependencies": {
    "Microsoft.EntityFrameworkCore.SqlServer": "1.1.0",
    "Microsoft.EntityFrameworkCore.SqlServer.Design": {
      "version": "1.1.0",
      "type": "build"
    },
    "Microsoft.EntityFrameworkCore.Tools": {
      "version": "1.1.0-preview4-final",
      "type": "build"
    },
    "Newtonsoft.Json": "9.0.1"
  },

  "frameworks": {
    "net452": {}
  },
  "tools": {
    "Microsoft.EntityFrameworkCore.Tools": "1.1.0-preview4-final"
  }
}

I have checked some other issue reports, and a lot of them say move to Tools.DotNet but I can't  because the app is targeting .net 4.5.2
Further technical details
EF Core version: 1.1.0
Database Provider: SQL Express 2016
Operating system: Win 10
IDE: VS 2015 update 3

I can't update Tools to Tools.DotNet because the app is targeting .net 4.5.2

Update your tools section to include .DotNet. You'll also need to use preview3 because of #7071
{
  "tools": {
    "Microsoft.EntityFrameworkCore.Tools.DotNet": "1.0.0-preview3-final"
  }
}

@bricelam I did and the following appeared

Cannot execute this command because 'Microsoft.EntityFrameworkCore.Tools' is not installed in project 'src\CAP.ShipsLogisticsManager.Data'. Add 'Microsoft.EntityFrameworkCore.Tools' to the 'tools' section in project.json. See http://go.microsoft.com/fwlink/?LinkId=798221 for more details.

Ensure you also have the LTS .NET Core Runtime installed.

Ok, after doing that on my pal's machine worked

Thank you mate!

No problem. Sorry for all the trouble! We know it's painful, and we're working hard to make it great.


[IE11]  'wrap-reverse' renders without implicit 'align-items:flex-end'

All tested browsers render wrap-reverse with implicit align-items: flex-end. IE 10/11 renders wrap-reversewith an implicit align-items: flex-start
Testcase
Workaround
  @media screen and (-ms-high-contrast: active), (-ms-high-contrast: none) {
    align-items: flex-end;
}

Bug Report | Flexbugs

@renatocarvalho Should the fix be in hagrid?

@felics I would keep the fix in hashgrid for now. Would be nice to add a comment about the workaround to hagrid code and as soon as they fix this (if they fix) we can cleanup the code.

The fix is not yet in master, have it working in a branch though and will send a PR asap. 0.9.x got rid of all vendor-specific conditionals (FF 26-, Opera 12-), it is sad having to merge in conditionals once again :crying_cat_face: Admittedly though, it is an edge case


Phpunit overhaul

Did I say this were an ongoing effort? Certainly is. Still far from complete, but there are now 196 assertions in 87 tests and counting. Coverage is somewhere in the 90% range. Not that this means anything: Some tests are still close to being pointless. But overall, the test suite is in quite okay shape.

I worked a bit on integrating the coveralls.io service during the weekend, whcih should've went into its own branch in retrospect … anyways, currently it would allow for this shiny new badge:

I also took the opportunity to have the code checked though codeclimate:

@DaSourcerer Isn't it better to rebase instead of creating merge commits?

@Kubo2: Probably yes. The process of rebasing always scares me a bit as it's not entirely unproblematic.

Ok, I'm pretty much done: There are now 250 assertions in 111 tests. The tests for HTMLSafeVisitor and NestLimitVisitor could still need some work but to be frank, I'm out of motivation right now.
@jbowens: Are you ok with that coveralls.io thing? If not, I can still remove it. TBH, it wasn't that trivial to get it working either.

@jbowens: Would it help if I condense everything into a single commit? Or are you uncomfortable with coveralls.io?

@DaSourcerer yeah, please squash your commits

k, will do as soon as I get home. You're still cool with the coveralls-thing? You would need to sign up and set two environmental variables in Travis to get it to run.

Heh, looks like the latest version of my IDE came with an important new feature: Havoc-free interactive rebases \o/

@DaSourcerer That's interesting (and getting even better with history :-). Any news on this?

@Kubo2 What are you missing? Most of what isn't covered by test cases atm is deprecated, only leaving room for improvements within the tests for HTMLSafeValidator and NetLimitValidator. The coveralls-thing could need some spit and polish, though as it's going to fail spectacularly in pull requests (this is due to a security restriction within Travis CI). Oh, and it seems hhvm-nightly is no longer available on Travis.
Just to have the setup for coveralls.io documented:

Sign up with coveralls.io (can be done with GitHub auth)
add the jBBCode repository
Copy the repo token (atm that's at the right hand side of the repository view)
Go to the repository settings in Travis CI and add two new environmental variables:

COVERALLS_REPO_TOKEN set to the repo token from step 3
COVERALLS_RUN_LOCALLY set to 1

Double check COVERALLS_REPO_TOKEN is hidden during builds. That's actually the default, but since this is a shared secret, it can't hurt to be a bit paranoid.
5. All done :smile:

@Kubo2 @jbowens Just removed hhvm-nightly. Everything else should be good to go. As is, coveralls will fail but it won't taint the build itself (see the last build)

Hey @DaSourcerer, when #61 is merged, you would probably like to add some more tests for CodeDefinitionBuilder and CallableValidatorAdapter on top of it directly in this PR.

@Kubo2: I'd rather see it PR-authors were implementing their own tests suiting their changes. This PR is really an overhaul of the test suite to get it into better shape; it's not an effort by me to spare others from writing meaningful tests. Besides, with no feedback from @jbowens since about two months, I'm reluctant to invest any more time in this for the time being.

Oh, okay. I will add the tests.

@jbowens @Kubo2 Are you guys still planning on merging this?

I'd be pleased to see it merged, however I am getting worried about the bus
factor of the project. I haven't heard about @jbowens for quite a long
time. Moreover, my #61 kinda depends on this too.
Regards,
Kubis
On 06-Apr-2016 9:41 pm, "Max Loeb"<EMAIL_ADDRESS>wrote:

@jbowens https://github.com/jbowens @Kubo2 https://github.com/Kubo2
Are you guys still planning on merging this?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/jbowens/jBBCode/pull/53#issuecomment-206445160

@Kubo2, @shmax: I actually were to post something quite in that spirit. It's been now over a year since this PR opened and we are closing in on an entire year since the last commit to master which is leaving me equally worried.
I still believe in the technical merits of this project and would love to continue working on it. In fact, I am very much looking forward to replace my own regexp-based parser with jBBCode in one of my projects. However, in order to do so, I need text nodes with way more powerful capabilities. I see the need for some code reorg to do this cleanly, so I always considered this PR to be a blocker as the increased test coverage would allow for more confidence when implementing the needed changes.
Having said this, I am increasingly concerned over the lack of participation by @jbowens, leaving me (and not only me) with the impression of an abandoned project. This is a situation that would usually suggest forking jBBCode; yet I cannot state adequately just how much I would hate doing so: I'd much rather contribute to an existing project than create and maintain my own.

@jbowens come back to us!

@jbowens if you're no longer interested in maintaining this project, may I suggest giving @DaSourcerer write permissions?

@jbowens I am very sad to see this project abandoned, especially because there are some active supporter. If you don't have much time I would recommend to give someone write permission, like @shmax mentioned.

Please squash all your commits. I'll try to give this another look tonight or tomorrow.

[x] done. Sorry for the holdup.