Signal method inserted after the end of C# class implementation in the Godot editor

Signal method inserted after the end of C# class implementation when connecting a signal
in the Godot editor to a node with a C# script attached.
Presents with error: "A namespace cannot directly contain members such as fields or methods"
Godot version:
3.1.dev.mono.custom_build.b49ca94
OS/device including version:
Windows 8.1 64bit, 8GB AMD FX 6350 6 core
Graphics Chipset
AMD Radeon HD 7700 Series
Memory Size 1024 MB
Radeon Software Version 17.4.4
Issue description:
Signal method inserted after end of the C# class implementation when connecting a signal
in the Godot editor to a node with a C# script attached.
Error: "A namespace cannot directly contain members such as fields or methods"
Just have to drag the signal handler back inside the class brackets.

Steps to reproduce:
Connect a signal from a node in the editor to a node with a C# script attached.
Signal method inserted after end of class implementation.
Minimal reproduction project:

Basic 3D scene such as
https://www.youtube.com/watch?v=-D-IcbsdT04

Related to #12908 (perhaps should be considered a duplicate)

Oh, didn't see that, should probably be marked as duplicate then.
duplicate of #12908

Sorry about the dup, didn't see!

Closing as duplicate.
@karroffel that feature worked for me only once, and it doesn't auto-close the issue.


Update devops

Pull Request Test Coverage Report for Build 674

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

Totals

Change from base Build 655:
0.0%

Covered Lines:
398

Relevant Lines:
417

💛  - Coveralls


[iOS ]Unable to add  tag functionality on MarkDowbTextView().  as it is display on UI.

Please provide your solution. Is it supported or need to find another way ?
Marky-Mark information

Marky-Mark version: _____
MarkDownConfiguration: _____ (View, AttributedString)

Describe the bug
A clear and concise description of what the bug is.
Used markdown text
What markdown text did you use that caused this issue?
Try to isolate the part causing the issue.
Screenshots
If applicable, add screenshots to help explain your problem.

 is HTML, not Markdown. Just use regular new lines if you want to add newlines in Markdown.
Hope this helps.
Kind regards,
Jim

thank you


Websocketconnection timeout

:white_check_mark: Build Fleck 1.0.13 completed (commit https://github.com/statianzo/Fleck/commit/662c1ebc4f by @notgiven688)


Move String into std-lib

Description
The String type is more of a primitive type than a library that provides special functionality. It should live in the std-lib.
Checklist

[x] I have linked to any relevant issues.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] I have updated the documentation where relevant (API docs, the reference, and the Sway book).
[x] I have added tests that prove my fix is effective or that my feature works.
[x] I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
[x] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
[x] I have requested a review from the relevant team or maintainers.

This isn't a String, it's just Bytes with convenience methods. I don't see the point of standardizing it if we're not standardizing the actual behavior of characters and unicode handling in Sway, which this doesn't do.
All it does is add overhead and breakage to our later attempts at doing that. So unless there is a good reason I don't see to do it, I don't think we should do it.

This is pulled from the Sway-Libs String which addresses this specific problem. Until we have char there is no way to 1. convert a str to a String or 2. guarantee a valid UTF-8 string.
The intent to move it into the std-lib was based on the fact that String is a type used in many of the Sway-Standards

Convenience types should indeed belong in user packages, I think Rust's approach of doing it with things like regex is sound. As they say, standard libraries are where things go to die.
But this isn't really the reason not to add this. Rather, this convenience string type will not be what we settle on when proper strings actually get standardized. Because it does not actually solve the Unicode problem, it just sidesteps it by pretending a collection of bytes is a Unicode string without checking, and doesn't actually let you manipulate code points in any meaningful way. As you say, this isn't actually possible to implement without char.
I don't think it's proper to standardize an interface we know we will break in the near future.
I may be compelled to do it if there was a strong reason, but people (including us) using a convenience interface isn't a strong reason.

The standard library should consist of components that can be used directly or libraries can stitch together.
The string is a convenience type, a wrapper, which is a library rather than some atomic component. I do not believe that this type should be in the standard library for that reason.

By this logic, the Rust String type shouldn't be in the standard library either as it is just a wrapper of Vec<u8>s. This was also once a Vec<u8>, but the Bytes type is more efficient for the fact that the FuelVM pads to the size of a word.
The main problem is that any str is treated as it's own type and the length must be defined. A str[8] cannot be compared with a str[7] as within the VM they are different types.
Hence, the use of the String type in the standard, I cannot define a standard using the str type. Unfortunately, a side effect of this is any use of a String in a standard is reading from storage and not something like a constant.
It is also impossible to create any conversions to the String type, unless I unrealistically define a separate From implementation for every possible length of str. Any uses of something like EIP-191 cannot be implemented either.
Fundamentally, yes, in it's current state the String type is just a convenience type. I personally don't see a type sitting in the same repo as something like a merkle proof library, but we can leave it there for now with the expectation that every use must add an additional dependency to the project.


adds VTG logo

[ ✅ ] Filename in the lowercase format
[ ✅ ] Image format: png
[ ✅ ] Image size: 256 by 256 px

Also, you can use these graphics to say that your ERC20 token fully compatible with Trust Wallet (https://trustwallet.com/logo-assets). Tokens will show up automatically once the user receives them.
Feel free to share this on social media and tag Trust Wallet:

Twitter: @trustwalletapp

Facebook: @trustwalletapp


  Nowhere near as nice:

The basic rail would look a lot more aesthetically pleasing if the rail block was covered in water rather than air:

Other than that, only need a powered rail which I know you have planned, and this will be an excellent modpack addition !   I love underwater rail networks !

All of these have been or will be fixed with the soon to be releases 1.16.5/1.18 releases.
Unfortunatley i do not think i will have the time to get these fixes into the 1.12 version.

All of these have been or will be fixed with the soon to be releases 1.16.5/1.18 releases.
Unfortunatley i do not think i will have the time to get these fixes into the 1.12 version.

All of these are fixed for both the 1.16.5 version and the 1.18.1 version.


Fix README links

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

@luizbills thank you for your contribution.
If you'd like, please send your first+last name and website so we can add it to our official contributors page: https://www.wondercms.com/contributors

If you'd like, please send your first+last name and website so we can add it to our official contributors page: wondercms.com/contributors

it's not necessary, don't worry.


Fix detection of latest stable release (fix #443)

If the first fetched package is not stable, but has a greater version than any of the stable packages, wrong behaviors such as that reported in #443 may occur.

Can I help with this to get it over the line?

sorted in #617 feel free to reopen if I make false assumptions :wink:


Maximum call stack size exceeded in jsrender.js

I am facing the error while creating 900 columns in the table by using jsrender. I have used the below code.
var i = 0, htmlStr =  "
" , colgrp = document.createElement("colgroup"), templates ={obj:""};
        while (i < 900) {
            colWth = 20;
            colHdr = "A" + 1;
            col = document.createElement("col");
            col.style["width"] = colWth + "px";
            htmlStr += "{{:" + colHdr + "_value}}	";
            colgrp.append(col);
            i++;
        }
        templates["obj"] = htmlStr + "
";
        $.templates(templates);

While running the sample getting the error.

JsViewsError {name: "JsRender Error", message: "Syntax error↵Compiled template code:↵↵// obj↵var v…↵return ret;↵: "Maximum call stack size exceeded""}

The error occurring in > jsrender-1.0.0-beta.js < . Which is working fine in exact jsrender-1.0.0-beta.js version. Is this an issue?.
JSFiddle link: https://jsfiddle.net/z8fqs1yb/2/

This seems to be an issue with Chrome. In other browsers it renders without error. In Chrome it errors if you put while (i<900), but if you put while (i<400) (or less) it works without error.
Your way of creating the template has 900 * 4 = 3600 {{: ...}} tags in a single template. Chrome throws an error while compiling that template - because of some kind of limit they have on JavaScript expressions of the form ret="..." +((v=...)!=null?v:"") + "..." +((v=...)!=null?v:"") + "..." +((v=...)!=null?v:"")... (where you have >7200 such terms added together to produce a single string variable).
I'd suggest you instead use a template along the lines of

  {{for cols}}
    {{:_value}}
  {{/for}}

Then you can render the template with data which has a cols array of 900 items for the columns:
var data = {
  height: 220,
  rowidx: "a",
  ...
  cols: [
    {_value: "AVal", _className: "AClass",  ...},
    {_value: "BVal", _className: "BClass", ...}
    ...
  ]
};

Closing - since this is not a JsRender bug (really a Chrome bug), and there is a workaround proposed...


Update talon swerve odom publishers to use periodic interval timer

Would prevent issues with publishin odom info if clock is changes while code is running, similar to other fixes for various state controllers using the same PeriodicInteralTimer code

Ported over into https://github.com/FRC900/2023RobotCode/pull/84, closing this one


LivePaper Error

Regardless of the file type chosen, be it MP4, GIF, or WEBP, none seem to function properly. Are there any potential solutions?

Same by me. Did you find the solution?

No, I think it's because of the new version of windows 11 24H2. I hope it gets fixed asap 😕.

How it's resource usage by the way? I never used it but i want to because of it's lightweight being (it doesn't work properly tho). As you used it for a while could you share some info about resource usage?

Hey, thanks for reporting!
I've attempted to fix the issue. If you want to try it out, download the latest builds https://github.com/zuranthus/LivePaper/releases/tag/latest

The app is just running in the background, and nothing is happening (´･ω･`)?

The app is just running in the background, and nothing is happening (´･ω･`)?

The app is just running in the background, and nothing is happening (´･ω･`)?
P.S. Sorry about the closing and reopening the issue, I didn't mean to ಥ_ಥ

How it's resource usage by the way? I never used it but i want to because of it's lightweight being (it doesn't work properly tho). As you used it for a while could you share some info about resource usage?

I've played different types of games, some take low resources while some take a lot and in all those times, I've never felt any drop in frames or slower system performance. Even doing your casual work or leaving the screen just like that doesn't affect much. Also, sorry because I can't provide you any resource usage statistics as I've resettled my laptop a lot, but I can assure you that It's the best one I've used so far.


website/doc: documentation for pkg builtin is broken

Looks like the docs for the builtin package are broken in https://golang.org/pkg/builtin/.
I'm not sure this is the right place for filing this issue, please point me in the right direction if that's the case. I've also skipped most of the questions in the issue template because it isn't related to running go itself.
What did you do?
Tried to browse the documentation for the builtin package in https://golang.org/pkg/builtin/.
What did you expect to see?
The documentation for the builtin package.
What did you see instead?
/src/builtin/builtin.go:88:11: expected type, found '=' (and 1 more errors)

Screenshot including the URL:

Duplicate of #21601.

Thanks for checking, @martisch, and sorry for the noise!


Expose AbstractScheduledEventExecutor.getCurrentTimeNanos

It would be useful to expose the getCurrentTimeNanos method to channel handlers, so that they can use it instead of calling System.nanoTime directly. The main purpose would be to make handlers work predictably with the EmbeddedEventLoop time manipulation methods (advance, freeze).
A good example is IdleStateHandler. It uses both event loop scheduling, and then nanoTime to confirm the timeout. If the event loop was advanced with advanceBy, the scheduled task will run, but the nanoTime will not show a timeout. For the unit test of IdleStateHandler, this nanoTime call is already overridden (it's in a package-private method), but when writing an external test that involves IdleStateHandler, this is not available. By exposing getCurrentTimeNanos, we would have a "single source of truth" when it comes to time, circumventing this issue.
Another minor advantage would be that handlers can take advantage of the nanoTime offset that the event loops implement, but this is not worth a change on its own.
The right place for this api would probably be EventExecutor (maybe EventExecutorGroup? does it make sense to have different times for each event loop in a group?). What do you think, is this worth adding?

Project reactor has a similar idea in its Scheduler class: https://projectreactor.io/docs/core/release/api/reactor/core/scheduler/Scheduler.html#now-java.util.concurrent.TimeUnit-

I need to think a bit more about it

How about introducing something similiar to Ticker in Guava? - https://guava.dev/releases/21.0/api/docs/com/google/common/base/Ticker.html Much simpler than Reactor's Scheduler yet does its job. We may want to add a few more methods though, e.g. advance() and sleep().

It's actually something I wanted to implement in our codebase to reduce the overall test run time. Let me try to come up with one soon.

@trustin i think exposing getCurrentTimeNanos would be basically the same as what you describe. Since #12459, advance already exists for the embedded event loop. So I'm not sure what you're proposing. Do you want to make it independent of EmbeddedEventLoop?

i think exposing getCurrentTimeNanos would be basically the same as what you describe. Since https://github.com/netty/netty/pull/12459, advance already exists for the embedded event loop. So I'm not sure what you're proposing. Do you want to make it independent of EmbeddedEventLoop?

Correct. I want to make it generic enough so it can be used in more places than just EmbeddedEventLoop.

@yawkat I've just sent out a PR for my idea. Would you mind taking a look? #13169


Integrate with other HSMs

notary implements the PKCS11 interface so it should be possible to integrate to other HSMs such as CloudHSM and Nitrokey

So in theory this works but hasn't been tested?  Will this work for targets / delegated targets keys, or only root keys?  It would be nice for a CI/CD pipeline in AWS to be able to store delegated targets keys in cloud HSM and use that to have the pipeline sign image metadata.

Currently, hardware support for root keys in Notary has not been tested across different HSMs but should work "in theory" due to the standard pkcs11 interface.
@endophage can definitely speak more to what changes might need to be made to our pkcs11 code since he's been looking into this more actively.
Storing and signing with targets / delegated keys in yubikes isn't currently supported in Notary but is on the 1.0 roadmap https://github.com/docker/notary/issues/306

Riyaz is spot on. I've been told by other sources that it has been reasonably easy to modify notary to work with other HSMs in PoC situations. We're just starting to get this kind of real world interest in actually making it work so while I don't consider this issue as a blocker on releasing a 1.0, we may want to prioritise it for other reasons.
CloudHSM is of particular interest as we would likely also use it for some (not incl. root) of our official image signing keys. We'd happily accept community help on tweaking and testing the existing PKCS11 implementation that does have a couple of very Yubikey specific instructions (i.e. to enable touch to sign).

There is even a PR that add support for other HSM's
#1369
But this PR seem to be blocked...


[ISSUE #442] update checkStyle file

Since the sChat2.jks has been removed, we can remove the filter.

Codecov Report

Merging #450 (0b7a55c) into develop (7850620) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             develop    #450   +/-   ##
=========================================
  Coverage       9.84%   9.84%
  Complexity       283     283
=========================================
  Files            228     228
  Lines          10829   10829
  Branches         923     923
=========================================
  Hits            1066    1066
  Misses          9666    9666
  Partials          97      97

Continue to review full report at Codecov.

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

@SteveYurongSu Hi, sChat2.jks has been added again, do you think we still need to remove this filter?

@SteveYurongSu Hi, sChat2.jks has been added again, do you think we still need to remove this filter?

I have noticed that. @qqeasonchen What is the file used for? 😂

@SteveYurongSu This file is used for ssl configure, it can be changed by user.
https://github.com/apache/incubator-eventmesh/blob/4eaebde2506a582f8c211143b8d22dedf21e4f5c/eventmesh-runtime/src/main/java/org/apache/eventmesh/runtime/boot/SSLContextFactory.java#L44-L55

@SteveYurongSu This file is used for ssl configure, it can be changed by user.
https://github.com/apache/incubator-eventmesh/blob/4eaebde2506a582f8c211143b8d22dedf21e4f5c/eventmesh-runtime/src/main/java/org/apache/eventmesh/runtime/boot/SSLContextFactory.java#L44-L55

Thanks!
I don't know if we should keep the binary file in our repo, especially when we don't know what content is in.
Maybe documentation is needed for this file?

What content is in?
Or how to generate it.

@SteveYurongSu Yes, there already has a doc about enable ssl, https://github.com/apache/incubator-eventmesh/blob/develop/docs/cn/features/https.zh-CN.md.
Maybe we can enhance this doc. So do you agree to keep this file, if this file is needed, we may need to filter this file in checkStyle file.

Maybe we can enhance this doc. So do you agree to keep this file, if this file is needed, we may need to filter this file in checkStyle file.

@ruanwenjun Yes, I agree. Let's keep this file in repo and add a filter in our checkStyle file. 😊


RE: [LOOKING FOR MAINTAINERS]: From Potential Maintainer

[LOOKING FOR MAINTAINERS]

Hello, I am Nathan G and I was considering helping with this project. I am curious about what your expectations would be of a maintainer? Is there a user base that has certain expectations?

@NGenetzky My original goal was to keep the layer up to date with the latest home assistant and current yocto releases.
The main reason I'm looking for a new maintainer is that I don't use home assistant anymore via yocto. So it's hard for me to verify that things still work. Somebody who is using it would be suited way better. Other than that I don't know what the expectation of other users are.

Hello guys,
I have some yocto experience in the professional projects. And also I've recoreded a training series on yocto in youtube.com/doctorpi. Just tell me the starting point, such as you can open an issue, and assign to me

Hi @mboyar The main issue is keeping the recipe up to date with the releases of home-assistant. I tried to do it for several releases but it was a lot of work, which I currently can't invest.
It might be worth to invest into automating the update process similar to what's done in nixpkgs.


Incorporating own code into manimlib

I would like to add functions to the manimlib that are callable in any new scene class.
Therefore, I created some new classes (e.g. class_name) with respective functions, in function.py and added a map to the manimlib folder, say functions. The I added a line to the imports.py file found in the manimlib folder:
from manimlib.functions.function import *
Now when I start a new Scene, I can indeed reach those new functions, when I type
class_name.function_name(parameters)
but Visual Code does not seem to recognize those. That is, they run and they work just as they should, but Visual Studio does not auto-complete or suggest the functions or parameters. Is this solvable? Because this now takes a lot of going back and forth and the whole idea to automatize this is lost.

I don't think this is a Manim issue. It seems to be more related to VSCode.
I use VSCode myself, and can't get any Manim objects to show up in IntelliSense, which I find pretty funny.

Try enablig Jedi  in settings --> python. This somethings helps.

Yea this seems like a VSCode issue if you could let us know if you find a solution in the future that would be great but as of now we should probably close this issue

But can you confirm this does not occur when using other IDE?

Yea this seems like a VSCode issue if you could let us know if you find a solution in the future that would be great but as of now we should probably close this issue

But can you confirm this does not occur when using other IDE?

I know for a fact that users of Vim have it autocomplete even custom manim stuff for them.

Yea this seems like a VSCode issue if you could let us know if you find a solution in the future that would be great but as of now we should probably close this issue

But can you confirm this does not occur when using other IDE?

I know for a fact that users of Vim have it autocomplete even custom manim stuff for them.

and does the jedi function not help you got auto complete the standard manim functions for you?

Unfortunately, it doesn't seem to pick it up for me. I found that I've had
jedi enabled this whole time!
On Sun, 3 May 2020, 21:15 stevenschn<EMAIL_ADDRESS>wrote:

Yea this seems like a VSCode issue if you could let us know if you find a
solution in the future that would be great but as of now we should probably
close this issue
But can you confirm this does not occur when using other IDE?
I know for a fact that users of Vim have it autocomplete even custom manim
stuff for them.
and does the jedi function not help you got auto complete the standard
manim functions for you?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/3b1b/manim/issues/1019#issuecomment-623129665, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AH5H6JHUDMIZMJYD25SRLXDRPWGR7ANCNFSM4MW46SXQ
.

Yea this seems like a VSCode issue if you could let us know if you find a solution in the future that would be great but as of now we should probably close this issue

But can you confirm this does not occur when using other IDE?

I know for a fact that users of Vim have it autocomplete even custom manim stuff for them.

Is this using the jedi-vim library or something else?

, both with and without jedi, but
 regardless of the setting.

Yea this seems like a VSCode issue if you could let us know if you find a solution in the future that would be great but as of now we should probably close this issue

But can you confirm this does not occur when using other IDE?

I know for a fact that users of Vim have it autocomplete even custom manim stuff for them.

Is this using the jedi-vim library or something else?

I'm not actually sure. It was mentioned in passing by one of the members of the Manim Discord community.


Link existing 'DialogHelper.IDialogWindow' logic with the 'DialogHost.Avalonia'

What is the best way to proceed if you want to link your existing IDialogWindow logic with the DialogHost (https://github.com/AvaloniaUtils/DialogHost.Avalonia)?
Currently I have implemented all popups or dialogs in my application with the DialogHelper class.
Since my application is designed as a desktop application and also as a "Kiosk app" on the Raspberry pi, I would like to find a solution how I can link my existing calls with the DialogHost.

@appleneko2001 can you take a look?

Well I break the support because I moved templates to window styles
It should be marked as bug not enhancement
It was worked before

Apparently this is resolved now. Closing


Remove duplicate $global-margin in _settings.scss

Noticed a duplicate $global-margin in settings on one of my recent projects.

Merged in #7107 which resolves this.


[Name lookup] Look through parentheses when finding type references.

When resolving type declarations in, e.g., the inherited type declarations
request, look through parenthesized types. Fixes rdar://problem/45527696.

@swift-ci please test and merge

@shahmishal it looks like the Linux CI for this branch might be misconfigured?
20:49:04 CMake Error at CMakeLists.txt:58 (find_package):
20:49:04   Could not find a package configuration file provided by "Swift" with any of
20:49:04   the following names:
20:49:04
20:49:04     SwiftConfig.cmake
20:49:04     swift-config.cmake
20:49:04
20:49:04   Add the installation prefix of "Swift" to CMAKE_PREFIX_PATH or set
20:49:04   "Swift_DIR" to a directory containing one of the above files.  If "Swift"
20:49:04   provides a separate development package or SDK, be sure it has been
20:49:04   installed.


possible small improvement to the readme.md about sample inputs for new datasets

Section "Generating a Random Sample Input" provides the following line as an example:
np.save(os.path.join('tests', 'sample_mnist'), a, allow_pickle=False, fix_imports=False)
where a is a random tensor initialized explicitly as dtype=np.int64 in the previous line. The input being of an integer type seems to be important for the synthesis tool because it fails at the "bitwise and" operator inside the parameter load function in izer/load.py at this line when the type is e.g., float64. The example already uses an input cast to int64, which gives a hint, but the error message when you don't use an int type is pretty cryptic:

ufunc 'bitwise_and' not supported for the input types, and the inputs could not be safely coerced to any supported types according to the casting rule ''safe''

and it was a bit cumbersome to trace the izer/... files to understand that my input wasn't saved with the correct type (I just copied the line I pasted above to save my sample data for a new dataset, which therefore skipped the typecasting, and numpy defaulted to float64 even though I had 256 unique values in the -128...+127 range). So my suggestion:

maybe a very small note under Section "Generating a Random Sample Input" in the readme.md, reiterating that the data should be dtype=np.int64

or, even though it's redundant, adding an explicit typecast to the "saving line" in the example (which everybody will probably copy without reading the randgen line, like me):

np.save(os.path.join('tests', 'sample_mnist'), a.astype('int64'), allow_pickle=False, fix_imports=False)
the second suggestion might induce even worse "hidden" errors like casting float input data in small ranges to int64 without notice, flooring them all to 0, -1 etc. though (depending on rounding settings), so I personally vote for the first one

Thanks for your suggestion. #151 should address this.


Visual Modifications and Project Additions.

In this Milestone, I made the following additions ➕ ➕ 🟢

Modified social image sources

Changed the paths of social images to make them appear on

Modified the appearance of Project images in Project Modals.

Resized project modal images to improve visuals of the page.

Add new projects to works section

Add picture background

Fix works cards swap position

Fixed Linter errors 🧰

Hello @jonas-45, @chepkok3
Can you take a look at this PR with some changes?
I have an error with Webhint, can you suggest a solution to this problem too?
I would appreciate if any of you approves this PR.


fix(popup)!: remove remaining balance from WalletInformation

Context

https://github.com/interledger/web-monetization-extension/pull/388#discussion_r1665539532
Slack discussion
Changes proposed in this pull request

Remove remaining balance from "settings" screen as balance is shown on "home" screen under slider (due to https://github.com/interledger/web-monetization-extension/pull/388).

Extension builds preview

Name
Link

Latest commit
2befef624229d9fe34a032b2a3934e6e0d17538b

Latest job logs
Run #9794257905

DownloadDownload


Support new streaming model

Add back support for streaming, according to https://github.com/projectriff/invoker-specification

I have started working on this, using RxPy as the reactive stack. Currently blocked by https://github.com/ReactiveX/RxPY/issues/467


Create a "How to setup Elixir" guide or point to a good one

Then we can link to it from our meeting pages, for people that want to come to meetings prepared. There's a sort of start of one on the Institute Readme: https://github.com/hui-ad/institute#prerequisites (perhaps once we have something here, we can point that over here, since this is the main "help" site for the group).

asdf-vm/asdf was a good suggestion. Their Getting Started guide was extremely easy to follow. The brew installation made it even simpler.
Just setting up Phoenix requires:

Erlang
Elixir
Nodejs

It definitely streamlines the installation process and is something someone could easily set up in half an hour (depending on download speeds) at one of the meetups.
Doesn't look like there's window support yet though 🤔

That's good to hear. Thanks for suggesting that link. Do you think we should put it on the GETTING_STARTED.md file in this repo?


Opacity goes to zero when moving mouse cursor over two windows quickly

Hyprland Version
 System/Version info
Hyprland, built from branch main at commit df990c80e211553fc63136072b0e518860172f2f dirty (hyprpm: log verbose return of cmake and meson in update).
Date: Sun Jan 28 04:00:05 2024
Tag: v0.34.0-74-gdf990c80

flags: (if any)

System Information:
System name: Linux
Node name: arch
Release: 6.7.1-arch1-1
Version: #1 SMP PREEMPT_DYNAMIC Sun, 21 Jan 2024 22:14:10 +0000

GPU information:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller])

os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

plugins:
  hycov by DreamMaoMao ver 0.1

Bug or Regression?
Bug
Description
https://github.com/hyprwm/Hyprland/assets/96977790/da18d4a5-74df-4204-b27d-8ae2302521a0
When hovering over two windows and moving the cursor between them quickly, the opacity of the windows fades to zero as shown in the video.
How to reproduce
Have these config files:
decoration {
    rounding = 5

    blur {
        enabled = true
        size = 100
        passes = 1
    }

    drop_shadow = true
    shadow_range = 35
    shadow_scale = 1.0
    shadow_render_power = 4
    shadow_offset = [500, 500]
    col.shadow = rgb(171a1f)

    active_opacity = 0.95
    inactive_opacity = 0.9
    fullscreen_opacity = 1.0
}

animations {
    enabled = true

    bezier = myBezier, 0.68, -0.55, 0.47, 0.84

    animation = windows, 1, 7, myBezier
    animation = windowsOut, 1, 7, myBezier, popin 80%
    animation = border, 1, 10, myBezier
    animation = borderangle, 1, 8, myBezier
    animation = fade, 1, 7, myBezier
    animation = workspaces, 1, 6, myBezier
}

Crash reports, logs, images, videos
No response

dont make a bezier with negative values then


Allow ID allocation to resume after continuous failures exceeding ids.renew-timeout

This is assigned somewhat arbitrarily to 0.5.5.  It may also apply to 0.9 (not sure yet).
Looking at StandardIDPool.java in 0.5.4, I think I see the following:

Successive IO failures when attempting to claim a new ID block in the storage backend which take (collectively) longer than ids.renew-timeout will set StandardIDPool.nextBlock = null.
If StandardIDPool.nextBlock is null, calls to StandardIDPool.nextID will not start a new allocation attempt.  nextID will call nextBlock, which then throws an IllegalArgumentException without talking to the storage backend.  I don't see how we can get out of this state once we enter it, even if the storage backend later becomes responsive enough to satisfy new ID block allocation attempts.

The first next step is to add a test that proves the behavior describes above actually exists in controlled conditions.  Then we can change StandardIDPool.

I can confirm this behaviour in Titan 0.5.3.
Once I'm getting this exception, it re-occurres continuously and I cannot get out of this state:
java.lang.IllegalArgumentException: null
	at com.google.common.base.Preconditions.checkArgument(Preconditions.java:111)
	at com.thinkaurelius.titan.graphdb.database.idassigner.StandardIDPool.nextBlock(StandardIDPool.java:152)
	at com.thinkaurelius.titan.graphdb.database.idassigner.StandardIDPool.nextID(StandardIDPool.java:193)
	at com.thinkaurelius.titan.graphdb.database.idassigner.VertexIDAssigner.assignID(VertexIDAssigner.java:330)
	at com.thinkaurelius.titan.graphdb.database.idassigner.VertexIDAssigner.assignID(VertexIDAssigner.java:185)
	at com.thinkaurelius.titan.graphdb.database.idassigner.VertexIDAssigner.assignID(VertexIDAssigner.java:151)
	at com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.assignID(StandardTitanGraph.java:385)
	at com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.addEdge(StandardTitanTx.java:675)
	at com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsTransaction.addEdge(TitanBlueprintsTransaction.java:132)
	at com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsTransaction.addEdge(TitanBlueprintsTransaction.java:124)
	at com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsTransaction.addEdge(TitanBlueprintsTransaction.java:28)
	at com.iqser.gin.server.persistence.titan.StatementPersistenceServiceImpl.add(StatementPersistenceServiceImpl.java:78)

The exception occurres when Cassandra is under heavy load.

I just pushed a new test method for this scenario and associated fix.

@dalaro @skiefer any advice for overcoming this issue in Titan 0.5.4? Or, equivalently, any quick tunings we can do to Cassandra so that it behaves more nicely?

This particular bug requires ID allocation to repeatedly fail / take longer than ids.renew-timeout.  Are you seeing repeated "Lock write succeeded but took too long: duration foo exceeded bar"?  A succession of these can accumulate to ids.renew-timeout.  It's one way this can happen, though maybe not the only way.  ids.authority.wait-time should control bar.


fix(asset_migration): fixes multiple assets migration and optimizations

Fix: iterate over each asset instead of calling mCreate, mDelete that can lead to odd behaviour in case of large number of assets
Fix: Remove the recovery process that can also lead to unwanted things
Fix: Check if new asset already exists in new tenant instead of throwing an error
Fix: Check and allow to migrate an asset even if no linked device
Optim: optimized calls (avoid update groups)
Optim: call sync/refresh at the end of the whole process

2 points

If you still want to remove the queue to rollback actions, you need to remove the associated file that came with it in the first place
Also removing this queue rather to fixing it can lead to incoherent data inside ES in the long run

Sorry but what is "the associated file that came with it" ?

In a first iteration, I prefer removing it rather than use something that can by itself add some more  inconsistencies. If the normal process has failed, why the recovery queue operation can't also fail, and add more inconsistencies ?
It is also a choice to iterate one asset by one asset, to avoid a large amount of inconsitencies (vs mCreate / mDelete).

Sorry but what is "the associated file that came with it" ?

The associated file is RecoveryQueue in lib/modules/shared/utils/recoveryQueue.ts

In a first iteration, I prefer removing it rather than use something that can by itself add some more  inconsistencies. If the normal process has failed, why the recovery queue operation can't also fail, and add more inconsistencies ?

That what I was saying, by taking the time to fix this behaviour of the recoveryQueue. But it's true that there is no such process in the whole plugin so we might wait another iteration to implement it correctly

It is also a choice to iterate one asset by one asset, to avoid a large amount of inconsitencies (vs mCreate / mDelete).

The process will be much longer but less errors prone, if we want KDM to be more performant we should still use mCreate and mDelete requests and running migration in batch. We should raise an issue about this performance cost choice

Switching from 1 mGet call to Iterating over N assets using exists (which under the hood is a get) is a huge deoptimization and will probably sink the performance. Same goes for 1 mCreate to N create. I think this will require a full test and benchmark suite before we consider merging it.

Ye, I'll do some benchmarks and give results to see if acceptable.
But, I prefer a slower solution 100% successfully.
Currently, when we have a fail, we lead into a lots of inconsistencies.
And the first point is to fix this.

I don't understand a TF (export csv) is not passing anymore ...

Switching from 1 mGet call to Iterating over N assets using exists (which under the hood is a get) is a huge deoptimization and will probably sink the performance. Same goes for 1 mCreate to N create. I think this will require a full test and benchmark suite before we consider merging it.

This is a new feature, and I prefer a slower solution 100% successfully.
Currently, when we have a fail, we lead into a lots of inconsistencies, and this is the first point to fix.
@fmauNeko Also, I have removed the iteration with exists, and preffered mGet calls.

While this implementation should be reworked to be faster in the futur, we could implement it as is for now

I think I have rewritten everything to use mGet, mCreate and mDelete, but taking care to avoid several inconsistencies

IMHO, this looks like a huge deoptimisation instead of an optimisation like it's stated in the title.
replacing the mCreate with N calls to create is going to cause a huge degredation of performances. this is likely to impact every users of KDM, even more so if the document are relatively large. The same idea is applied for every operation done in the loops.
I understand that you're trying to have something that produces more consistent results but maybe fixing the RecoveryQueue might have been a been a better idea before introducing such regressions.
At least what could have been done to reduce the number of incosistent result and keep a decent speed by using mCreate, mDelete etc on smaller batches, for example if you had 100 documents you could have splitted them in batches of 10 documents, so you would have 10 calls to mCreate that each contains 10 documents, and you would stop if one of the document in the batch had an error, this way you would have kept a somewhat decent speed (the 10 document size is an example) while avoiding having a huge load of document in an inconsistent state.
It important to be able to measure the impact of such changes and so having benchmarks in those cases are mandatory since this will pretty much affect any production using KDM.

I have rewriten keeping back the use of all mGet, mCreate and mDelete to improve performances, butbut while minimizing the risk of inconsistencies.


Blurry Show race menu when first creating character

This is probably noted already but when you create a new game the character show race menu is blurry

Indeed this one is known already :) Unsure exactly what is causing it at the moment. It's some type of light blast effect that occasionally happens before the initial racemenu is opened. Sometimes it takes long enough to occur that it does show in the race menu. Tis being looked into I'll close this one to just have one issue on the subject https://github.com/zediious/tpfz-sprinkles/issues/8


Restore null behavior

I'm going to merge this PR as-is since it's about restoring null behavior, and the comments are about deficiencies in existing tests, or in restoring the NaN behavior for the array functions. We can follow up on those separately.

Can you please create issue(s) for the outstanding work?


Add instructions to build linux and windows

> ls -ah dist/ | grep 0.0.1
Mosaic-0.0.1-ia32-win.zip
Mosaic-0.0.1-win.zip
mosaic-browser_0.0.1_amd64.deb
mosaic-browser_0.0.1_i386.deb
mosaic-browser-0.0.1.i686.rpm
mosaic-browser-0.0.1-ia32.tar.gz
mosaic-browser-0.0.1.tar.gz
mosaic-browser-0.0.1.x86_64.rpm
Mosaic Setup 0.0.1.exe
Mosaic Setup 0.0.1.exe.blockmap

Added pacman and

https://github.com/marketplace/actions/electron-builder-action
https://github.com/samuelmeuli/action-electron-builder

examples

https://github.com/samuelmeuli/mini-diary/blob/master/.github/workflows/release.yml
https://github.com/samuelmeuli/mini-diary/blob/master/package.json


feat(snackbar): add initial mdl-snackbar implementation.

Same 'showSnackbar' API in component/foundation.
Basic adapter API for various interactions.
Adds VueJS example as well.
Some test coverage.
Closes #4490.

Doc file is just the checkbox copy. Should be updated to be the snackbar information.
I'd call the method just show instead of showSnackbar for v2.

Those are the immediate issues. One thing to remember is we need to discuss Snackbars with the MD team still. They are painful on desktops and we should have alternative's on desktop to show notifications in a way that users will notice them better. So, merging this shouldn't mean it is set in any way, as we should ideally work out a way to have relative positioned snackbar alerts for desktop.
Great work here though so far. Looks like a good upgrade of the V1 code into V2.

Fantastic work, this looks great, @petejohanson! Can't believe how quickly you put this together!
As for setting things in stone, don't worry about it. We're still pre-alpha, so as "definitive" as we like to get every component, there's still plenty of room for massive refactorings and changes :D This is an excellent start, whether or not any changes are needed.
@Garbee: We've mostly been following a methodology where we try to get everything right the first time, and raise any issues with the MD team ahead of time. That doesn't necessarily have to be the case, though; it's just easier to plan around that way if we're building everything ;) We have to adjust accordingly for outside contributions.
Thanks again for digging in deep even at this early stage, @petejohanson! 👍

@petejohanson echoing what @sgomes said, this is off to a really great start! Thanks for your work so far!
I left my first round of comments to address. It also looks like there are some lint errors, which is causing TravisCI to fail.
Once you address the changes above, you can use the PTAL label to notify us that the PR is ready for another round, or just feel free to comment directly!

They''ll have to comment. Only contributors on the repo can modify labels. :wink:

This is looking really excellent so far! The code looks great and the toast UI looks great as well.
I did notice a couple of UX issues when viewing the demo page:

On page load, I am able to see an artifact of the toast being translated off the screen. We could probably afford to have the snackbar by styled by default with display: none;. Then we could have a class e.g. mdl-snackbar--upgraded that removes the display: none; styling. This way, there's no "flash of untranslated content" on page load.
I think by default the color of the action text should be the theme's accent color, rather than it's primary color. This appears to be what's shown in the mocks, and from looking at the demo the contrast ratio does seem pretty low when styled w/ primary color.
We should probably show an example of a multi-line snackbar with a short action message, such that it's not aligned to the bottom. I'm perfectly fine with adding more configuration options to show to specify whether or not the action is long, e.g. placeActionBelowText: true // | default false. It's a bit clunky but IMO it's way better than trying to magically do this based on the text, which has lead to suboptimal results when we've tried to do similar things.

Some other things to consider:
Accessibility
So I believe the correct ARIA attrs for snackbars are aria-live="assertive" and aria-atomic="true". Also, aria-hidden="true" must be set initially, and must be updated when toasts are displayed / hidden.
Furthermore, we're going to have to figure out what to do regarding keyboard focus around the action button. For example - should the snackbar trap focus when it's displayed? If it does trap keyboard focus, should the toast remain visible until it's blurred? What does the focus state look like? etc. etc.
I'm personally okay with punting on the keyboard input story until we get some input from our A11y folks, because it's not exactly straightforward and has the potential to blow up the scope of this PR. @sgomes WDYT? We can create a follow-up item on #4490
Moving other elements when snackbars are shown.
The canonical "FAB moves when the snackbar is shown" is a good example of this. My suggestion here would be to add/remove a document-level class/data attr specifying that the snackbar is open. While the snackbar itself doesn't have to use it, other elements on the page can key off it to rearrange themselves.
The other option would be to create some sort of controller-style or helper component that could have something to do with orchestrating this.
The final option would be to say that this is out of scope of the toast component. For example, it may fall into the realm of material motion. They're still in the pre-alpha / planning phases of their work as well, but choreography is a big part of material motion and this specific issue may be more in that wheelhouse.
Besides the above looks really great. I'll be pushing a temporary workaround which falls back to Xvfb + Firefox until TravisCI sorts out their issues with Sauce Labs + JWT. Let me know if you run into any snags with the tests.

If we treat these as an alertdialog then the action should be focused when it appears. I think that is a required need since tabbing into the snackbar from the application could take some time and be gone by the time a user gets to it. It would also trap focus in this regard. The only difference is these snackbars may get used for non-error/alert data (such as simply "Email sent Undo") which would not strictly require that level of attention.
I think a good middle-ground is...

Auto-focus into snackbar
Provide an option to say "This is a serious alert" (like critical: true). This would cause focus trap and keep it open indefinitely until the first point beyond the timeout where it is not focused.

@Garbee
The issue with alertdialog is that snackbars are meant to be temporary. Even though some consumers (mistakenly) use snackbars as an error indicator, this is an anti-pattern since snackbars are transient by design. Compare that to alerts, which need to be manually dismissed by the user.


Output interval control

I'm having trouble getting IPC to output and .obj file every timestep.  I looked over the documentation and there is an input called playBackSpeed.  I've tried setting this value to 1 and to a speed that that equals  number of time steps/simulation end time.  Neither of these setting has produced a 1.obj or a 2.obj file after Timestep 1 and 2 are completed.
Any help would be appreciated.
Thanks,
Nick

Hi Nick,
Forgive me that the playBackSpeed setting is too complicated, it has to be set to a value such that playing back in that speed at about 30 frame/s requires all objs from each time step, it will output every obj. So to ensure every time step has the output, simply setting it to a tiny value like 1e-20 should definitely work.
Minchen

Thanks Minchen, that works perfectly.  Sorry to ask such a trivial question, but I got confused.
Nick


[FR] Adding support for Yeelight LED bulbs

Came across this library after seeing your post on https://github.com/aholstenson/miio/issues/291.  How can I help add support for this device? And do you have a Docker Container of this perhaps?

Sr about the late, I'm still finding the way to support devices which I don't have. You can post some information about your device, such as the model, photo, link to buy, ...?

I'm on the way to integrate my Yeelights Tunable/color/strip. Its near finish, its working but not all. I'll make a pr when finished.

I'm on the way to integrate my Yeelights Tunable/color/strip. Its near finish, its working but not all. I'll make a pr when finished.


Cannot pull or switch between environments containing notifications

Describe the bug
I opened an issue yesterday on this but I was looking in the wrong place  #6469 and I also have experienced this before in #5056.  Both times I thought it was old issue or a config issue but there is definitely a recurring problem that breaks my CI pipeline on a regular basis.
I think the reason this is occurring due to one particular value in amplify-meta.json not being updated correctly.  I think it pulls from the first environment in team-provider-info.json instead of the environment you are trying to initialise.  This means if you destroy the other environment the new environment is broken because it cannot update the APNS/FCM resources for wrong and old environment and thus prevents you switching or pulling environment.
This is the amplify-meta.json of a newly created environment from my machine.  I had one environment called "core" before running init again.  After creating the environment and then downloading the amplify-meta.json from the deploy bucket you can see the value below still points the pinpoint appid of the "core" environment and not the new appid.
If I now teardown "core" then this new environment is now completely broken (cannot pull or checkout).  To correct I have to edit the amplify-meta.json in the #current-cloud-backend.zip and reupload it just to fix it
"notifications": {
    "myNotifications": {
      "service": "Pinpoint",
      "output": {
        "Arn": "arn:aws:mobiletargeting:eu-west-1:<account>:apps/acdb82ba838543e6b4ccf86ccef3a4e2",
        "Id": "acdb82ba838543e6b4ccf86ccef3a4e2",
        "Name": "myNotifications-newenv",
        "tags": {},
        "Region": "eu-west-1",
        "APNS": {
          "ApplicationId": "acdb82ba838543e6b4ccf86ccef3a4e2",
          "CreationDate": "2021-01-24T20:38:49.442Z",
          "DefaultAuthenticationMethod": "Certificate",
          "Enabled": true,
          "HasCredential": true,
          "HasTokenKey": false,
          "Id": "apns",
          "IsArchived": false,
          "LastModifiedDate": "2021-01-24T20:38:49.442Z",
          "Platform": "APNS",
          "Version": 1
        },
        "FCM": {
          "ApplicationId": "acdb82ba838543e6b4ccf86ccef3a4e2",
          "CreationDate": "2021-01-24T20:38:50.749Z",
          "Enabled": true,
          "HasCredential": true,
          "Id": "gcm",
          "IsArchived": false,
          "LastModifiedDate": "2021-01-24T20:38:50.749Z",
          "Platform": "GCM",
          "Version": 1
        },
        "Email": {
          "ApplicationId": "acdb82ba838543e6b4ccf86ccef3a4e2",
          "CreationDate": "2021-01-24T20:38:51.162Z",
          "Enabled": true,
          "FromAddress"<EMAIL_ADDRESS>          "Id": "email",
          "Identity": "arn:aws:ses:eu-west-1:<account>:identity/email.co.uk",
          "IsArchived": false,
          "LastModifiedDate": "2021-01-24T20:38:51.162Z",
          "MessagesPerSecond": 1,
          "Platform": "EMAIL",
          "RoleArn": "arn:aws:iam::<account>:role/service-role/pinpoint-events",
          "Version": 1
        },
        "SMS": {
          "ApplicationId": "acdb82ba838543e6b4ccf86ccef3a4e2",
          "CreationDate": "2021-01-24T20:38:51.795Z",
          "Enabled": true,
          "Id": "sms",
          "IsArchived": false,
          "LastModifiedDate": "2021-01-24T20:38:51.795Z",
          "Platform": "SMS",
          "PromotionalMessagesPerSecond": 20,
          "TransactionalMessagesPerSecond": 20,
          "Version": 1
        }
      },
      "lastPushTimeStamp": "2021-01-24T20:38:47.919Z"
    }
  },
  "analytics": {
    "myNotifications": {
      "service": "Pinpoint",
      "providerPlugin": "awscloudformation",
      "dependsOn": [
        {
          "category": "auth",
          "resourceName": "myvipapp",
          "attributes": [
            "UserPoolId"
          ]
        },
        {
          "category": "auth",
          "resourceName": "userPoolGroups",
          "attributes": [
            "adminGroupRole"
          ]
        },
        {
          "category": "auth",
          "resourceName": "userPoolGroups",
          "attributes": [
            "publicGroupRole"
          ]
        }
      ],
      "providerMetadata": {
        "s3TemplateURL": "https://s3.amazonaws.com/amplify-myapp-newenv-134601-deployment/amplify-cfn-templates/analytics/pinpoint-cloudformation-template.json",
        "logicalId": "analyticsmyNotifications"
      },
      "lastPushTimeStamp": "2021-01-24T21:04:04.080Z",
      "output": {
        "appName": "myNotifications", <----- NOT CHANGED FROM CORE SETTINGS
        "Region": "eu-west-1",
        "Id": "c40b2b7d9baa475b811fd07d74240084" <--- NOT CHANGED FROM CORE SETTINGS
      },
      "lastPushDirHash": "19mkE0kFkhhdMb2VC5pxjiHSuKA="
    }
  },

Amplify CLI Version
4.41.2
To Reproduce
See above
Expected behavior
This value should be updated to the current environment settings from team-provider-info.json
Desktop (please complete the following information):

OS: Mac or Linux
Node Version. v14.4.0

Log output
None really
2021-01-25T09:00:15.257Z|info : amplify env core checkout eventgroup
2021-01-25T09:03:51.334Z|info : amplify pull core  [***]{"amplify":"{\"projectName\":\"[***]App\",\"defaultEditor\":\"code\",\"envName\":\"[***]roup\",\"appId\":\"[***]tln025\"}","frontend":"{\"frontend\":\"javascript\",\"framework\":\"react\",\"config\":{\"SourceDir\":\"packages/core\",\"DistributionDir\":\"packages/core/lib\",\"BuildCommand\":\"yarn build\",\"StartCommand\":\"yarn start\"}}","providers":"{\"awscloudformation\":{\"configLevel\":\"project\",\"useProfile\":true,\"profileName\":\"[***]ar-[***]ify\"\n}}","categories":"{\"notifications\":{\"Pinpoint\":{\n\"SMS\":{\n\"Enabled\":true},\"Email\":{\n\"Enabled\":true,\"FromAddress\":\"[***]elopment.co.uk\",\"Identity\":\"[***]ses:eu-[***]st-[***]5:identity/[***]nt.co.uk\",\"RoleArn\":\"[***]6357915:role/[***]ice-[***]le/[***]oint-[***]nts\"},\"APNS\":{\n\"Enabled\":true,\"DefaultAuthenticationMethod\":\"Certificate\",\"P12FilePath\":\"/Users/jimbo/Projects/roar/certs/push-notifications.p12\",\"P12FilePassword\":\"\"},\"FCM\":{\n\"Enabled\":true,\"ApiKey\":\"[***]Mh3xZwmxZVKZFWyBh2OJaZY0cYe-[***]9Pw4FSEn9vneq-[***]BJ90wA4RHBPWWoN7YlCiW\"}}},\"auth\":{\"facebookAppId\":\"[***]130007\",\"googleClientId\":\"[***]55857-[***]ps.googleusercontent.com\",\"facebookAppIdUserPool\":\"[***]130007\",\"facebookAppSecretUserPool\":\"[***]99fde78abbfbb\",\"googleAppIdUserPool\":\"[***]55857-[***]ps.googleusercontent.com\",\"googleAppSecretUserPool\":\"[***]QgWP2XF8IH\"}}","yes":true,"restore":true}
2021-01-25T09:03:57.567Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/Users/jimbo/.aws/config"])
2021-01-25T09:03:57.567Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/Users/jimbo/.aws/config"])
2021-01-25T09:03:57.569Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["roar-amplify"])
2021-01-25T09:03:57.569Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/Users/jimbo/.aws/config"])
2021-01-25T09:03:57.570Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"eu-west-1"}])
2021-01-25T09:03:57.570Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["roar-amplify"])
2021-01-25T09:03:57.570Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/Users/jimbo/.aws/credentials"])
2021-01-25T09:03:57.576Z|info : amplify-provider-awscloudformation.amplify-service-permission-check.checkAmplifyServiceIAMPermission.amplifyClient.listApps([])
2021-01-25T09:03:58.051Z|info : amplify-provider-awscloudformation.attach-backend.getAmplifyApp.amplifyClient.getApp([{"appId":"[***]tln025"}])
2021-01-25T09:03:58.452Z|info : amplify-provider-awscloudformation.attach-backend.getBackendEnv.amplifyClient.getBackendEnvironment([{"appId":"[***]tln025","environmentName":"[***]roup"}])
2021-01-25T09:03:58.654Z|info : amplify-provider-awscloudformation.attach-backend.downloadBackend.s3.getObject([{"Key":"[***]rent-[***]ud-[***]d.zip","Bucket":"[***]ify-[***]app-[***]roup-[***]601-[***]ment"}])
2021-01-25T09:04:02.855Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["roar-amplify"])
2021-01-25T09:04:02.855Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/Users/jimbo/.aws/config"])
2021-01-25T09:04:02.856Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"eu-west-1"}])
2021-01-25T09:04:02.856Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["roar-amplify"])
2021-01-25T09:04:02.856Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/Users/jimbo/.aws/credentials"])
2021-01-25T09:04:02.856Z|info : amplify-provider-awscloudformation.zip-util.downloadZip.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip"},null])
2021-01-25T09:04:02.858Z|info : amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip","Bucket":"[***]ify-[***]app-[***]roup-[***]601-[***]ment"}])
2021-01-25T09:04:03.876Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["roar-amplify"])
2021-01-25T09:04:03.876Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/Users/jimbo/.aws/config"])
2021-01-25T09:04:03.876Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"eu-west-1"}])
2021-01-25T09:04:03.876Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["roar-amplify"])
2021-01-25T09:04:03.877Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/Users/jimbo/.aws/credentials"])
2021-01-25T09:04:03.881Z|info : amplify-provider-awscloudformation.initialize-env.run.cfn.updateamplifyMetaFileWithStackOutputs([{"StackName":"[***]ify-[***]app-[***]roup-[***]601"}])
2021-01-25T09:04:04.686Z|info : amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]ify-[***]json","Bucket":"[***]ify-[***]app-[***]roup-[***]601-[***]ment"}])
2021-01-25T09:04:04.854Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["roar-amplify"])
2021-01-25T09:04:04.854Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/Users/jimbo/.aws/config"])
2021-01-25T09:04:04.854Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"eu-west-1"}])
2021-01-25T09:04:04.854Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["roar-amplify"])
2021-01-25T09:04:04.855Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/Users/jimbo/.aws/credentials"])
2021-01-25T09:04:06.393Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["roar-amplify"])
2021-01-25T09:04:06.393Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/Users/jimbo/.aws/config"])
2021-01-25T09:04:06.394Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"eu-west-1"}])
2021-01-25T09:04:06.394Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["roar-amplify"])
2021-01-25T09:04:06.394Z|info : amplify-provider-awscloudformation.system-config-manager.makeFileOwnerReadWrite(["/Users/jimbo/.aws/credentials"])
2021-01-25T09:04:06.534Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["roar-amplify"])
2021-01-25T09:20:48.071Z|info : amplify version core  {"version":true,"yes":false}

It might be that this value never gets update (instead of getting pulled from team-provider-info.json).  So if you create an environment from another environment then the value propagates to each environment without being updated.

It might be that this value never gets update (instead of getting pulled from team-provider-info.json).  So if you create an environment from another environment then the value propagates to each environment without being updated.

I have tracked down the "source" of the old app id on new environments.  It is pulled from the appId in the parameters.json in the folder alongside the cloudformation file
for example in file amplify/backend/analytics/myNotifications/parameters.json
This appId at the bottom never gets updated and thus the value in the amplify-meta.json is always pointing to the wrong pinpoint.
{
  "appName": "myNotifications",
  "roleName": "pinpointLambdaRole5b86667f",
  "cloudformationPolicyName": "cloudformationPolicy5b86667f",
  "cloudWatchPolicyName": "cloudWatchPolicy5b86667f",
  "pinpointPolicyName": "pinpointPolicy5b86667f",
  "authPolicyName": "pinpoint_amplify_5b86667f",
  "unauthPolicyName": "pinpoint_amplify_5b86667f",
  "authRoleName": {
    "Ref": "AuthRoleName"
  },
  "unauthRoleName": {
    "Ref": "UnauthRoleName"
  },
  "authRoleArn": {
    "Fn::GetAtt": ["AuthRole", "Arn"]
  },
  "appId": "c40b2b7d9baa475b811fd07d74240084"
}

Not only does the appId not change but none of these resources exist anymore as the environment is long torn down.

I have tracked down the "source" of the old app id on new environments.  It is pulled from the appId in the parameters.json in the folder alongside the cloudformation file
for example in file amplify/backend/analytics/myNotifications/parameters.json
This appId at the bottom never gets updated and thus the value in the amplify-meta.json is always pointing to the wrong pinpoint.
{
  "appName": "myNotifications",
  "roleName": "pinpointLambdaRole5b86667f",
  "cloudformationPolicyName": "cloudformationPolicy5b86667f",
  "cloudWatchPolicyName": "cloudWatchPolicy5b86667f",
  "pinpointPolicyName": "pinpointPolicy5b86667f",
  "authPolicyName": "pinpoint_amplify_5b86667f",
  "unauthPolicyName": "pinpoint_amplify_5b86667f",
  "authRoleName": {
    "Ref": "AuthRoleName"
  },
  "unauthRoleName": {
    "Ref": "UnauthRoleName"
  },
  "authRoleArn": {
    "Fn::GetAtt": ["AuthRole", "Arn"]
  },
  "appId": "c40b2b7d9baa475b811fd07d74240084"
}

Not only does the appId not change but none of these resources exist anymore as the environment is long torn down.

@attilah @renebrandel
I am looking at the PR for this change and could you explain something to me?
Does this change mean you can only have one pinpoint app?  Because multiple pinpoint apps was working before if you manually updated those two values in my first.  Is there a reason you have only forced the one environment?
Also, I have sandboxes for feature branches and I think looking at it that if I teardown one environment it will still remove the pinpoint application and thus destroy all other environments.
This actually makes the situation worse over the original?

This still isnt working correctly on the latest version
When I created a new environment it created a new pinpoint app but left the amplify-meta.json pointing to the original environment.  So I was in environment "master" and run a headless script to create environment "test".  There was now two apps called "myNotifications-master" and "myNotification-test" but the meta still points to "myNotifications-master".  When I then called amplify env remove test it tore down the test environment except it left "myNotifications-test" and deleted "myNotifications-master" app.  Thus breaking the master environment!

@attilah @renebrandel @kaustavghosh06 This is NOT fixed and is much worse!
To workaround this I have had to put this script in for post init of a new environment (and then re-push).  Otherwise the values are still wrong and the original (master env for me) pinpoint gets torn down when the new environment is torn down and the new pinpoint gets left instead
// fix for pinpoint multienv bug - https://github.com/aws-amplify/amplify-cli/issues/6475
const notifcationsParams = JSON.parse(
  fs.readFileSync(path.resolve('../amplify/backend/analytics/myNotifications/parameters.json')).toString(),
);
const meta = JSON.parse(fs.readFileSync(path.resolve('../amplify/backend/amplify-meta.json')).toString());

const pinpoint = new AWS.Pinpoint({
  region: global.env.ANALYTICS_myNOTIFICATIONS_REGION,
});

const appIds: PromiseResult<AWS.Pinpoint.GetAppsResponse, AWS.AWSError> = await pinpoint.getApps({}).promise();

const pinpointAppName = `myNotifications-master-${global.env.ENV}`;
const pinpointAppId = (appIds.$response.data as AWS.Pinpoint.GetAppsResponse).ApplicationsResponse.Item.filter(
  a => a.Name == pinpointAppName,
);
notifcationsParams.appName = pinpointAppName;
notifcationsParams.appId = pinpointAppId[0].Id;
console.log('Updating parameter.json for analytics/myNotifications');
fs.writeFileSync(
  path.resolve('../amplify/backend/analytics/myNotifications/parameters.json'),
  JSON.stringify(notifcationsParams, null, 2),
);

console.log('Updating team-provider-info.json for missing pinpoint info');
let teamProvider = JSON.parse(fs.readFileSync(path.resolve('../amplify/team-provider-info.json')).toString());
teamProvider[global.env.ENV].categories.notifications.Pinpoint.Name = pinpointAppName;
teamProvider[global.env.ENV].categories.notifications.Pinpoint.Id = pinpointAppId[0].Id;
fs.writeFileSync(path.resolve('../amplify/team-provider-info.json'), JSON.stringify(teamProvider, null, 2));

console.log('Patching amplify meta data');
meta.notifications['myNotifications-master'].output.Name = pinpointAppName;
meta.notifications['myNotifications-master'].output.Id = pinpointAppId[0].Id;
meta.notifications['myNotifications-master'].output.APNS.Id = pinpointAppId[0].Id;
meta.notifications['myNotifications-master'].output.FCM.Id = pinpointAppId[0].Id;
meta.notifications['myNotifications-master'].output.Email.Id = pinpointAppId[0].Id;
meta.analytics.myNotifications.output.Name = pinpointAppName;
meta.analytics.myNotifications.output.Id = pinpointAppId[0].Id;
fs.writeFileSync(path.resolve('../amplify/backend/analytics/myNotifications/parameters.json'), JSON.stringify(teamProvider, null, 2));


Macro-expanded usages of Box should use the fully-qualified path

It turns out that some crate decided to create a type called Box... ooof.
struct Box;

#[async_trait::async_trait]
trait Demo {
    async fn oops(&self);
}

#[async_trait::async_trait]
impl Demo for () {
    async fn oops(&self) {}
}

error[E0107]: struct takes 0 generic arguments but 1 generic argument was supplied
 --> src/lib.rs:3:1
  |
3 | #[async_trait::async_trait]
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^- help: remove these generics
  | |
  | expected 0 generic arguments
  |
note: struct defined here, with 0 generic parameters
 --> src/lib.rs:1:8
  |
1 | struct Box;
  |        ^^^
  = note: this error originates in the attribute macro `async_trait::async_trait` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0107]: struct takes 0 generic arguments but 1 generic argument was supplied
 --> src/lib.rs:8:1
  |
8 | #[async_trait::async_trait]
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^- help: remove these generics
  | |
  | expected 0 generic arguments
  |
note: struct defined here, with 0 generic parameters
 --> src/lib.rs:1:8
  |
1 | struct Box;
  |        ^^^
  = note: this error originates in the attribute macro `async_trait::async_trait` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no function or associated item named `pin` found for struct `Box` in the current scope
  --> src/lib.rs:10:26
   |
1  | struct Box;
   | ---------- function or associated item `pin` not found for this struct
...
10 |     async fn oops(&self) {}
   |                          ^^ function or associated item not found in `Box`

Duplicate of https://github.com/dtolnay/async-trait/issues/132, https://github.com/dtolnay/async-trait/issues/163, https://github.com/dtolnay/async-trait/issues/214.

Fair enough. I searched for the error messages before opening this issue, but didn't think to search for related terms.


Adds Float class

We need to upload Float class for easy comparison with floating points numbers.

The class 'efloat' was removed from this repo, because it can cause ambiguity. There are many ways of doing comparisons. I think it is best having comparison functions like almost_equal.

Ok, then just i will just add almost_equal function

Ok, that's fine.

Wait, now I think, the almost_equal function is not so necessary. First, it is intuitive to implement. Second, it could be very dependent of the case. I propose not to integrate this function and close this issue (at least until we have a good reason).


Run-time dependency wayland-client found: NO (tried pkgconfig and cmake)

Tried the instructions on Ubuntu 20.04 I get:
...
Build type: native build
Project name: wf-recorder
Project version: 0.2
C compiler for the host machine: cc (gcc 9.2.1 "cc (Ubuntu 9.2.1-31ubuntu1) 9.2.1 20200304")
C linker for the host machine: cc ld.bfd 2.34
C++ compiler for the host machine: c++ (gcc 9.2.1 "c++ (Ubuntu 9.2.1-31ubuntu1) 9.2.1 20200304")
C++ linker for the host machine: c++ ld.bfd 2.34
Host machine cpu family: x86_64
Host machine cpu: x86_64
Found pkg-config: /usr/bin/pkg-config (0.29.1)
Found CMake: /usr/bin/cmake (3.16.3)
Run-time dependency wayland-client found: NO (tried pkgconfig and cmake)

meson.build:26:0: ERROR: Dependency "wayland-client" not found, tried pkgconfig and cmake

Seems like we have missed to add libwayland-client0 dependency (I do not use ubuntu so I am not sure whether there is a -dev package for it). Can you try to install that and tell me which packages you needed so that others can find it too?

wayland-client.pc is provided by libwayland-dev.

Yes I had also to install libgtk-dev


Testing on NuScenes Validation

Hi authors,
Great work!
I have a question about the testing results on NuScenes. In the paper "V2B", they also evaluate the trackers using the keyframes of the validation set, but you have a different number of the final testing frames. For example, you have 64159 cars, V2B has only 15578 cars. Could you give some tips if you know the reason behind it?
Thanks!

For V2B, it converts the NuScenes data to KITTI format. Since NuScenes and KITTI have different categories, there may exist some mismatchs between the classes.  Furthermore, we found that V2B needs extra meta data from "nuScenes-lidarseg" to do the data conversion. It probably filters out more frames that were not covered by nuScenes-lidarseg.
The splits generated by V2B may be just sub-splits of ours.
As the conversion is not recommended by the NuScenes official, we filter training/testing tracklets directly using official NuScenes APIs without extra meta data from nuScenes-lidarseg.


How can I convert canvas to image and save it to device gallery?

Here is my code.
Any advice would be appreciated.
var PluginPage = require("./PluginPage");

var page = new PluginPage("Camera", "org.apache.cordova.camera", function(parent) {
  var button = tabris.create("Button", {
    layoutData: {left: 10, top: 10, right: 10},
    text: "Select a picture"
  }).appendTo(parent).on("select", function() {
    navigator.camera.getPicture(onSuccess, onFail, {
      quality: 50,
      destinationType: Camera.DestinationType.FILE_URI,
      sourceType: navigator.camera.PictureSourceType.SAVEDPHOTOALBUM
    });
    function onSuccess (imageUrl) {
      canvas.set("backgroundImage", imageUrl);
      // draw something to Canvas
    }
    function onFail (message) {
        alert('エラーが発生しました: ' + message);
    }
  });

  var canvas = tabris.create("Canvas", {
    layoutData: {top: [button, 20], left: 20, right: 20, bottom: 20}
  }).appendTo(parent);

  var saveButton = tabris.create("Button", {
    layoutData: {left: 10, bottom: 10, right: 10},
    text: "save the picture"
  }).appendTo(parent).on("click", function() {
    // convert canvas to image and save to device gallery
  });
});

Usually you would use
getimageData to get the pixels drawn on a canvas. Tabris.js currently does not support this.
I opened  separate issue for you feature request in#559. Please follow that issue.
Also not that instead of setting the backgroundImage as in your example, you would usually use drawImage() or putImageData() to draw an image on the Canvas. That feature was requested in #413 but is not yet available, either.
Please leave further comments on the referenced issues.


show bar only on fullscreen

I am using i3wm.
Is there anyway to show bar only on fullscreen and hide when it when not in fullscreen?

no. you need to hide and show it yourself whenever you go to fullscreen. You may be able to automate this via keybindings.


RmqMessageConsumer.Requeue should send a message to a specific queue rather than a topic

By sending a message to a topic, it results in sending a message to every queue that is bound to that topic via a routing key.

Thanks @yiannistri


DuckDB ClickBench Q28 and Q29 fail for missing scalar character_length

Describe the bug
DuckDB ClickBench Q28 and Q29 fail for missing scalar character_length
Query Error Execution error: Unable to query arrow: Unable to get schema: Catalog Error: Scalar Function with name character_length does not exist!

To Reproduce
Steps to reproduce the behavior:

Configure ClickBench in DuckDB
Run ClickBench Q28 or Q29
See error

Expected behavior
The query should succeed, or a workaround should be documented.
Runtime Details
Spicepod
Add the relevant spicepod.yml section.
Output of the describe table
Add any relevant describe table output here.
Output of explain query
Add any relevant explain query output here.
E.g. explain select 1
+---------------+--------------------------------------+
| plan_type     | plan                                 |
+---------------+--------------------------------------+
| logical_plan  | Projection: Int64(1)                 |
|               |   EmptyRelation                      |
| physical_plan | ProjectionExec: expr=[1 as Int64(1)] |
|               |   PlaceholderRowExec                 |
|               |                                      |
+---------------+--------------------------------------+

spice, spiced, OS info

spice version: spice version
spiced version: spiced --version
OS info: uname -a

Have you tried this on the latest trunk branch?

[ ] Yes
[ ] No

If possible, run spiced with DEBUG log level
By setting the environment variable SPICED_LOG="task_history=DEBUG,spiced=DEBUG,runtime=DEBUG,secrets=DEBUG,data_components=DEBUG,cache=DEBUG,extensions=DEBUG,spice_cloud=DEBUG"
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Closed by: https://github.com/spiceai/datafusion/pull/59


[key commit! the code is very important]: continue to complete channel.hpp.

Improved the code framework of channel.hpp
Completed the definition of protocol.proto: all request and response message protocol definitions
Added map_helper to helper.hpp to handle type conflicts between google::protobuf::Map and std::unordered_map. Test Done.
Completed the implementation of some network interface calls in channel.hpp
basic_publish, basic_ack, basic_consume, basic_cancel. The implementation of these four interfaces is relatively complex, and only the first one is implemented. The logic of this basic_publish interface is very important and is the core. A thread pool is also introduced to complete asynchronous operations.

see title and description.

Note a key commit, [key commit! the code is very important]

see title and description.


Refactor imports

remove unnecessary imports
make headers consistent

Finishes #142860715

          1 Message

:book:
Nice, more deletions than insertions :red_circle:

  Generated by :no_entry_sign: danger


Drop C++14 Support

Related to:

https://github.com/drogonframework/drogon/issues/1589

This PR is the first step among the tasks:

Update CMakeLists.txt to use only C++17 or later

@ken-matsui thanks.
The string_view.h, any.h and option.h should be removed from Drogon.

@ken-matsui thanks.
The string_view.h, any.h and option.h should be removed from Drogon.

@ken-matsui thanks.
The string_view.h, any.h and option.h should be removed from Drogon.

@an-tao Yes, but including that makes this PR massive. I think having separate PRs would be better.

@an-tao ^ any thoughts on this?

@an-tao ^ any thoughts on this?

Yes, I'll merge this patch after releasing the 1.8.5 version.

@an-tao Great. Thank you for your review!

This PR is a subset of https://github.com/drogonframework/drogon/pull/1734


Cannot find module './uws_linux_x64_108.node'

Hi,
I have this issue since trying to deploy on my linux server.
`Error: This version of µWS is not compatible with your Node.js build:
Error: Cannot find module './uws_linux_x64_108.node'
Require stack:

/home/debian/anymagik/server/node_modules/uWebSockets.js/uws.js
<EMAIL_ADDRESS><EMAIL_ADDRESS>/home/debian/anymagik/server/src/server.ts
/home/debian/anymagik/server/src/index.ts
at /home/debian/anymagik/server/node_modules/uWebSockets.js/uws.js:22:9
at Object. (/home/debian/anymagik/server/node_modules/uWebSockets.js/uws.js:24:3)
at Module._compile (node:internal/modules/cjs/loader:1119:14)
at Module._compile (/home/debian/anymagik/server/node_modules/source-map-support/source-map-support.js:568:25)
at Module._extensions..js (node:internal/modules/cjs/loader:1173:10)
at require.extensions..jsx.require.extensions..js (/tmp/ts-node-dev-hook-4798241668083143.js:114:20)
at Object.nodeDevHook [as .js] (/home/debian/anymagik/server/node_modules/ts-node-dev/lib/hook.js:63:13)
at Module.load (node:internal/modules/cjs/loader:997:32)
at Function.Module._load (node:internal/modules/cjs/loader:838:12)
at Module.require (node:internal/modules/cjs/loader:1021:19)
at require (node:internal/modules/cjs/helpers:103:18)
at Object. (/home/debian/anymagik/server/node_modules/@colyseus/uwebsockets-transport/build/uWebSocketsTransport.js:6:19)
at Module._compile (node:internal/modules/cjs/loader:1119:14)
at Module._compile (/home/debian/anymagik/server/node_modules/source-map-support/source-map-support.js:568:25)
at Module._extensions..js (node:internal/modules/cjs/loader:1173:10)
at require.extensions..jsx.require.extensions..js (/tmp/ts-node-dev-hook-4798241668083143.js:114:20)
[ERROR] 16:29:36 Error: This version of µWS is not compatible with your Node.js build:

Error: Cannot find module './uws_linux_x64_108.node'
Require stack:

/home/debian/anymagik/server/node_modules/uWebSockets.js/uws.js
<EMAIL_ADDRESS><EMAIL_ADDRESS>/home/debian/anymagik/server/src/server.ts
/home/debian/anymagik/server/src/index.ts
`
I don't know why.
I used yarn (last version) and cleared all my node_modules before doing "yarn install"
I went to node_modules/uwebsockets.js there's the "uws_linux_x64_108.node"
Any idea ?

Open issue with library you are using https://github.com/colyseus/colyseus tell them update uws.js version https://github.com/colyseus/colyseus/blob/master/packages/transport/uwebsockets-transport/package.json#L11

You don't need that colyseus library get rid of that and code your app without it


Pass context to machine webhook

Description:
Resolves #

Codecov Report

Merging #48 (5e7f997) into master (70183c9) will increase coverage by 0.53%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##           master      #48      +/-   ##
==========================================
+ Coverage   82.22%   82.76%   +0.53%
==========================================
  Files          12       12
  Lines        1148     1149       +1
==========================================
+ Hits          944      951       +7
+ Misses        152      147       -5
+ Partials       52       51       -1

Impacted Files
Coverage Δ

pkg/api/v1alpha1/machine_webhook.go
87.50% <75.00%> (+0.09%)
:arrow_up:

pkg/controllers/machine_controller.go
76.16% <0.00%> (-0.88%)
:arrow_down:

pkg/controllers/machinenodepool_controller.go
80.66% <0.00%> (+3.00%)
:arrow_up:

Continue to review full report at Codecov.

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

Codecov Report

Merging #48 (5e7f997) into master (70183c9) will increase coverage by 0.53%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##           master      #48      +/-   ##
==========================================
+ Coverage   82.22%   82.76%   +0.53%
==========================================
  Files          12       12
  Lines        1148     1149       +1
==========================================
+ Hits          944      951       +7
+ Misses        152      147       -5
+ Partials       52       51       -1

Impacted Files
Coverage Δ

pkg/api/v1alpha1/machine_webhook.go
87.50% <75.00%> (+0.09%)
:arrow_up:

pkg/controllers/machine_controller.go
76.16% <0.00%> (-0.88%)
:arrow_down:

pkg/controllers/machinenodepool_controller.go
80.66% <0.00%> (+3.00%)
:arrow_up:

Continue to review full report at Codecov.

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


List of presentations after inserting it

List of presentations after inserting it.

feat: List of presentations after inserting it
commit 8f0bf78835f6acae22b49881b0484749078f0dee


Example for options

Can you please provide example in the documentation how to use hitCacheCallback?

ok, I'll provide an example later~

https://github.com/chenyahui/gin-cache/blob/main/examples/options/main.go
I add an example for WithOnHitCache option, a common use case for WithOnHitCache is to record the number of hit caches.

Thanks!


High-contrast mode: SVG icons within links should match link text colour

This is a bug specific to Windows high-contrast mode. cc @kbayliss who did the testing for this.

Current: fill: currentColor
Proposed: fill: LinkText
Places to fix:

[ ] Main navigation icons
[ ] Pagination left/right arrows
[ ] Breadcrumb globe icon
[ ] <a class='button'> icons

Current:

Proposed:

Marking as a good first issue – I think the proposed fix could work well with the forced-colors media query, or even applied directly whenever the icon and text color match already. Note testing this does require having access to Windows high-contrast mode.

Additionally adding the case of icons in text:

Fixed via fb66c1fd1732f462a1983edb5410192a9b8963da / #7460


NL, PL probing task

Regarding NL and PL probing task used to evaluate CodeBERT, there are a few unclear issues that I hope you can clarify

Number of datapoints for probing: In the CodeBERT paper, it is described that only test and valid data from codesearchnet is used to evaluate probing. Take PL probing for example where only codes containing max or min is chosen, however I can't get the same number of datapoints reported in Table 3 (for example: python-paper: 1264, me: 1246, java-paper: 482, me: 556). I grab the dataset following the codesearchnet repo and only exclude data that tokenize to longer than 512 tokens. Do you guys do additional processing to adjust the dataset size for probing?
Probing NL tokens: In this task, the paper describes 6 keywords that are used max, maximizer, min, minimize, less, and greater and group into 4 categorizes. However using the tokenizer, different keywords can tokenize to different length of tokens. For example greater tokenizes to 2 different tokens (great and er). In this case does the NL probing evaluation only tokenizer the first token (i.e  er) ? If so, is it really a fair evaluation? since its unlikely the model will ever predict maxer since its not a word in the english language.

We don't do additional processing. We have released the max/min ClozeTest in CodeXGLUE. You can find this dataset in this repo.
We replace the max, maximizer, min, minimize, less and greater with [MASK] before tokenization. So there will be no such situation as you said. We specify that the masked position corresponds to one of max, min, less, and great.


Gauge multiprocess_mode "latest"

Usecase:

Exposing static info that is the same across all processes. For example the commit id or project version.

Just noticed that I can achieve the same thing for static info with max.


Optimize inspired by SQLite

SQLite hvae release details about how it optimizes the execution plan.
we might want to look into it and get inspired to improve AlaSQL
https://www.sqlite.org/optoverview.html

@derekelkins thank you for inputs!


2nd attempt to correct image urls  both in Campaign.md and UserDocTem…

...plate.mdt.  To use the template, copy it to the docs/user_documentation directory in the local file explorrer and rename it to the module desired, but with the md extension.  You can then edit it with your favorite markdown editor.

I'm not sure why this build failed.  There were no conflicts and everything is synced and builds locally.

@DanKline Can you rebase to master (again!)? I think it should be pretty straightforward, and then your commit/push should push AppVeyor into submission.  Thanks!

I’ve never done it … but let me try.  Thanks.  I’m looking forward to continuing with the documentation.
From: James Chambers<EMAIL_ADDRESS>Sent: Tuesday, August 22, 2017 7:14 AM
To: HTBox/allReady<EMAIL_ADDRESS>Cc: Daniel C. Kline<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [HTBox/allReady] 2nd attempt to correct image urls both in Campaign.md and UserDocTem… (#2078)
@DanKline https://github.com/dankline  Can you rebase to master (again!)? I think it should be pretty straightforward, and then your commit/push should push AppVeyor into submission. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/HTBox/allReady/pull/2078#issuecomment-324007631 , or mute the thread https://github.com/notifications/unsubscribe-auth/AC8ECg-pfiAcSnmDUOhY5cYBtQoRPEH9ks5sasX7gaJpZM4O8cev .  https://github.com/notifications/beacon/AC8ECp6xMA0wqvlyNqT_4DeR3GZCiLBsks5sasX7gaJpZM4O8cev.gif

I'm stuck on this rebase.  Between the post-surgical fog and my lack of experience, I just don't  "git" Git.  My rebases never pull the 60 commits into my forked repo on Github.  I'm about to give up and delete my fork and refork from HTBOX, then just make my few changes.  Are there any caveats to this approach?

@DanKline  it sounds like you are not rebasing your fork against the HTBox master.  To do that you will need to setup a remote for HTBox master and then sync your fork with HTBox upstream.  (Note: you should be able to use git rebase instead of git merge when syncing to do an actual rebase instead of merge)

PR# 2078 is finally ready for merge.  I've corrected the conflicts.  I'm not sure how to resubmit the pull request.


migrate-az-1.0.0.md: spelling fix

Docs Build status updates of commit bf69875:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-1.7.0/migrate-az-1.0.0.md
:bulb:Suggestion
View (azps-1.7.0)
Details

docs-conceptual/azps-1.7.0/migrate-az-1.0.0.md

Line 23: [Suggestion] Illegal link: Default Device Code login instead of Web Browser prompt -- missing bookmark. The file docs-conceptual/azps-1.7.0/migrate-az-1.0.0.md doesn't contain a bookmark named temporary-default-device-code-login-instead-of-web-browser-prompt.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@fowl2 Please resolve the conflict and I can merge.


Source -> Show/Edit -> dropzone or quicker access to document dropping

  When I find a source
     and it has no documents (pdf, etc.)
        then I want quick(er) access to adding a document on the show and edit pages

I believe it is done already


Feat: Add doc and change source of message system

We can push, the compilation problem is solved in another branche


dask.dataframe.DataFrame.reduction fails onsplit_every=False if query planning is in effect

Describe the issue:
This is a follow-up to #11000 - thanks again for the fix! It appears that the now present dask.dataframe.DataFrame.reduction changes its behavior if query planning is activated or not.
Minimal Complete Verifiable Example:
The following snippet fails:
import dask
import pandas as pd
dask.config.set({'dataframe.query-planning': True})

import dask.dataframe as dd

dd.from_pandas(pd.DataFrame({"a": [1]}), npartitions=1).reduction(chunk=lambda x: x, split_every=False)

The error raised reads:
ValueError: split_every must be at least 2

If query planning is disabled the following snippet executes without raising an exception:
import dask
import pandas as pd
dask.config.set({'dataframe.query-planning': False})

import dask.dataframe as dd

dd.from_pandas(pd.DataFrame({"a": [1]}), npartitions=1).reduction(chunk=lambda x: x, split_every=False)

Anything else we need to know?:
The docstring describing split_every states that this argument is in fact of type int | None but it does not make clear how to set it to "false".
Environment:

Dask version: 2024.3.0
dask-expr version: 1.0.2
Python version: 3.12.2
Operating System: MacOS 14.2.1
Install method (conda, pip, source): conda

Sorry about that, put up a pr


Fix MM-61710

Summary
Fix MM-61710
Ticket Link
Fix https://mattermost.atlassian.net/browse/MM-61710
Release Note
NONE

/cherry-pick release-2.23

Cherry pick is scheduled.


fix: when log_root set, traces will failed.

when use traces, and set log_root as following, the traces will be failed, because the Name of log_filebackend not match :
app.config
{lager, [
	  {log_root, "logs"},
	  {handlers, [
		      {lager_file_backend, [{file, "router_error.log"}, {level, error}]},
		      {lager_file_backend, [{file, "router_info.log"}, {level, info}]}
		     ]},
	  {traces, [
		    {{lager_file_backend, "user_online.log"}, [{module, rcp_client}, {function, help}], info}
		   ]}
]}.

see pull request #258 - test und bugfix.

@ChinaXing Is there something in your PR that isn't covered in #258?

Going to close this as #258 has been staged on both 2.x and 3.0 integration branches.


Vaulting tables is buggy when objects are slightly in the way

After failing a vault (when it says you succeed), you cant try again until you move a tile away
https://user-images.githubusercontent.com/19853115/103474160-51d35100-4d5e-11eb-83d2-263ac01ac4c8.mp4

oops dupe of #2302 didnt check thoroughly

oops dupe of #2302 didnt check thoroughly


Open Source : 4.7 Everything about Outreachy Program

Description 📜
Explained Everything about Outreachy program in the form of documentation.
Fixes #299

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Open Source

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Hey @Aryamanz29 , you are requested to review and  let me know if any changes needed.

@Aryamanz29 please review. I have done the changes


Move required asterisk to before label/placeholder

In Collect and Enketo, the asterisk for a required form field appears before the text, but in Central, it's after. This PR makes things more consistent by changing it to before the text in Central as well. Here's an example from the login page:

What has been done to verify that this works as intended?
I searched src/components for *, and I'm pretty sure the only places to change are FormGroup and DateRangePicker. I've viewed the change locally as well.
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
The risk of regression should be low.
Does this change require updates to user documentation? If so, please file an issue here and include the link below.
Probably some screenshots will be out-of-date, but I wouldn't think we need to update those just for this.
Before submitting this PR, please make sure you have:

[x] run npm run test and npm run lint and confirmed all checks still pass OR confirm CircleCI build passes
[x] verified that any code or assets from external sources are properly credited in comments or that everything is internally sourced

@lognaturel, would you mind taking a look at the screenshot just to confirm that this is a change we want to make?

After discussion, we prefer the current placement of the asterisk.


Add genre analysis of control schemes to design book

The control scheme is a very important factor for the user experience and should be taken into consideration when designing features.
It's often challenging for complex games like factory builders and RTS games, as they have many actions to execute which should have shortcuts available.
I think it makes sense to look at both factory builders and RTS games to take inspiration.
The schemes could be divided into "character-based control schemes", where the player is controlling a main character (usually with an inventory system), e.g. Factorio, Satisfactory, Dyson Sphere Program and "god-mode-based control schemes" where there is no player character, e.g. Age of Empires 4, Settlers 3, etc.
We should look at both mouse & keyboard based controls as well as controller controls.
Stellar controller support could be a nice selling feature for our game, as it is usually an afterthought for this genre and not a great experience.
With the Steam Deck, controller support for PC games has become even more important.

Agreed, I think this is a great lens to look at a critical problem.

How mouse interaction works in Civ 6:
Less detail: https://discord.com/channels/1027393534627692645/1028004706435485766/1059197231393157171
More detail: https://discord.com/channels/1027393534627692645/1028004706435485766/1059203882569449482

traditional RTS: https://discord.com/channels/1027393534627692645/1028004706435485766/1059195353875894313

Factorio: https://discord.com/channels/1027393534627692645/1028004706435485766/1058949910889779243

From @bzm3r

Some discussion around reasons to prefer drag-to-pan instead of pan-when-cursor-is-at-edge: https://discord.com/channels/1027393534627692645/1027394523585839165/1059331741694824449

Closing, as I don't think that this analysis is a useful enough use of time at this stage :)