WGLMakie + Pluto

Hi thanks for all the work you are putting into this!
I just tried out the new WGLMakie, it so far is not yet perfect...
Thus is what I am seeing in pluto:

Here is the notebook with the MWE
https://gist.github.com/j-fu/6213665e0c0043e8e97bb2e3b4292e5a
... the single scatter plot is messed up, and it is not clear what to show for a scene...
EDIT: @fonsp

Sorry, 0.3 is a breaking release, since it now works a bit different.
I added a Page mode to JSServe  for Pluto, which still needs full documentation etc.
The very first cell in your notebook now needs to be:
begin
	using JSServe
        port = 8449 # the port you want
	JSServe.JSSERVE_CONFIGURATION.listen_port[] = port
	JSServe.JSSERVE_CONFIGURATION.external_url[] = "http://localhost:$(port)"
	JSServe.JSSERVE_CONFIGURATION.content_delivery_url[] = "http://localhost:$(port)"
	JSServe.Page() # needs to get displayed by Pluto
end

The docs + UI still needs to be cleaned up and then I'll prepare docs + blogpost.

Sorry, 0.3 is a breaking release, since it now works a bit different.
I added a Page mode to JSServe  for Pluto, which still needs full documentation etc.
The very first cell in your notebook now needs to be:
begin
	using JSServe
        port = 8449 # the port you want
	JSServe.JSSERVE_CONFIGURATION.listen_port[] = port
	JSServe.JSSERVE_CONFIGURATION.external_url[] = "http://localhost:$(port)"
	JSServe.JSSERVE_CONFIGURATION.content_delivery_url[] = "http://localhost:$(port)"
	JSServe.Page() # needs to get displayed by Pluto
end

The docs + UI still needs to be cleaned up and then I'll prepare docs + blogpost.

Ah now this works. Great!
Also mixing 2D and 3D + updating Nodes works:
https://gist.github.com/j-fu/efe75cc057d4d8643464b196bbce0eb7
Seems I am running into #805 when I run the rendering cell a second time.
I wonder about the CPU usage: I see 300% during interaction which is not the case with GLMakie.

Ah now this works. Great!
Also mixing 2D and 3D + updating Nodes works:
https://gist.github.com/j-fu/efe75cc057d4d8643464b196bbce0eb7
Seems I am running into #805 when I run the rendering cell a second time.
I wonder about the CPU usage: I see 300% during interaction which is not the case with GLMakie.

You should try to use this for sliders:
 n = JSServe.Slider(3:100)

data = map(x-> ..., n) # the slider works just like an observable

You should try to use this for sliders:
 n = JSServe.Slider(3:100)

data = map(x-> ..., n) # the slider works just like an observable

Is see, thank you - need to carve out some time for following these recent developments...

Is see, thank you - need to carve out some time for following these recent developments...

Is port 8449 fixed?  I tried putting a different number in arbitrarily and it didn't seem to work, but I am not sure if I did the experiment correctly.  Seems like it might limit having multiple notebooks open at once if so.

Is port 8449 fixed?  I tried putting a different number in arbitrarily and it didn't seem to work, but I am not sure if I did the experiment correctly.  Seems like it might limit having multiple notebooks open at once if so.

Each notebook needs its own port!

Each notebook needs its own port!

I repeated the experiment, and it is working with other port numbers.  So operator error on my part before.  However I am getting this warning on the console as I go along:
┌ Warning: session closed and not ready
└ @ JSServe ~/.julia/packages/JSServe/a4Ibj/src/session.jl:112

I repeated the experiment, and it is working with other port numbers.  So operator error on my part before.  However I am getting this warning on the console as I go along:
┌ Warning: session closed and not ready
└ @ JSServe ~/.julia/packages/JSServe/a4Ibj/src/session.jl:112

Ah forgot to remove that one...you can ignore that!

Ah forgot to remove that one...you can ignore that!

It looks like with WLGMakie 0.3.2 and Julia 1.5.3, the work-around no longer works around the problem.  I am back to nothing being displayed again.

It looks like with WLGMakie 0.3.2 and Julia 1.5.3, the work-around no longer works around the problem.  I am back to nothing being displayed again.

http://juliaplots.org/WGLMakie.jl/dev/

http://juliaplots.org/WGLMakie.jl/dev/

@SimonDanisch
Any idea what I can do for the low DPI?


FancyZones shown when hovering over maximize button

Microsoft PowerToys version
0.65.0
Installation method
WinGet
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce
I do not use FancyZones, so I disabled it.
But although disabled, the FancyZones are still shown when hovering with the mouse over the maximize button of an application.
✔ Expected Behavior
FancyZones not shown when disabled.
❌ Actual Behavior
When hovering over the maximize button, you could select a fancy zone layout, although it is disabled.
Other Software
No response

It's the Windows 11 feature you're talking about, not FancyZones. You can find it in the system settings to turn off.


CEXIO balance incorrect

Just enabled live trading on cexio - the balance calculation is wrong as cexio reports 'available balance' and 'balance in orders' - you don't need to subtract the orders from the reported 'available' figure...

at this moment cex.io is not supported!


[ ! ] Nuitka Couldnot Compile a Large Python File

Nutika --version
2.0
Commercial: None
Python: 3.11.6 (tags/v3.11.6:8b6ee5b, Oct  2 2023, 14:57:12) [MSC v.1935 64 bit (AMD64)]
Flavor: CPython Official
Executable: E:\fbvenv\build\Scripts\python.exe
OS: Windows
Arch: x86_64
WindowsRelease: 10
(gcc 13.2.0).

(Inside venv)

COMMAND
./Scripts/nuitka --disable-console --standalone --lto=no --enable-plugin=pyqt5 main.py

so i have a python file that is Qt compiled ui of 12K lines (582K characters) when nuitka gets stuck when it tries to compile its (C|Headers) generated code so in first it got stuck at 99,9% and when i terminated c1.exe from task manger it said that it failed to compile it and also its object file was empty (0KB) so i tried again but to only compile it with the following command
nuitka --mingw FacebookGui.py --lto=no --enable-plugin=pyqt5

And after running it, it also again worked to generate C code but when compiling it got stuck at 5/6
Output
Nuitka-Options: Used command line options: --mingw FacebookGui.py --lto=no --enable-plugin=pyqt5
Nuitka-Options:WARNING: You did not specify to follow or include anything but main program. Check options and make sure
Nuitka-Options:WARNING: that is intended.
Nuitka-Plugins:WARNING: pyqt5: Not relevant with this OS, or Nuitka arguments given, not activated.
Nuitka: Starting Python compilation with Nuitka '2.0' on Python '3.11' commercial grade 'not installed'.
Nuitka: Completed Python level compilation and optimization.
Nuitka: Generating source code for C backend compiler.
Nuitka: Running data composer tool for optimal constant value handling.
Nuitka: Running C compilation via Scons.
Nuitka-Scons: Backend C compiler: gcc (gcc 13.2.0).
Backend C: 83.3%|████████████████████▊    | 5/6

Any idea how can i fix this?
Scons output

Also there is a solution to my case is using the loadUi function from Qt instead and if u care about not sharing the ui file u can encrypt it with a hardcoded key lets say
from cryptography.fernet import Fernet
key = b'zyX8lG9R_t74kPsRqH6OKfI8YbyKRFGiLt94Kpj5pPA='
cipherSuite = Fernet(key)
inputFilePath = "Gui.ui"
outputFilePath = "_AnStrangeName.dll"
with open(inputFilePath, 'rb') as inputFile:
    data = inputFile.read()
encryptedData = cipherSuite.encrypt(data)
with open(outputFilePath, 'wb') as outputFile:
    outputFile.write(encryptedData)

then you can decrypt it on startup
        cSuite = Fernet(b'zyX8lG9R_t74kPsRqH6OKfI8YbyKRFGiLt94Kpj5pPA=')
        with open(appMainDir/"_AnStrangeName.dll", 'rb') as encFile:
            encData = encFile.read()
        decryptedData = cSuite.decrypt(encData)
        decryptedDataStr = decryptedData.decode('utf-8')
        uiFile = StringIO(decryptedDataStr)
        loadUi(uiFile,self)

Here comes an issue if u were doing something like self.ui = Ui_MainWindow() as that will result into a not found attributes so u can proxify the getattr dunder method to repalce self.ui with self as the following
class Window(ResizeableWindow, QModernFramelessWindow):
    """_summary_

    Args:
        QMainWindow (_type_): _description_
    """
    def __getattr__(self, name):
        if name == "ui":
            return self
        else:
            return super().__getattr__(name)
    def __hasattr__(self, name):
        if name == 'ui':
            return True
        return super().__hasattr__(name)

NOTE This doesnot solve nuitka problem obviously

there is one possible solution
use --clang --msvc=latest not --mingw64
is this case, it may just need a "bit" longer wait (like about 10~20 min?), so switch your compiler to msvc+clang(clang-cl) will make it faster
this is just a suggestion, and you need to install both msvc and clang to try it

Without a reproducer there is nothing I can do. Yes, you can find a better C compiler. Probably random scalability work of Nuitka may eventually make it work. Since this is a commercial project of a non-subscriber to Nuitka commercial I invite you to become one, then you can report the problematic Python file privately to me.

Closing for lack of feedback

Closing for lack of feedback

I already have my answer thank you so much


ci: support source coverage and report to codecov

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Better scenario outlines

Super tiny change that came out of #516

:ship:
Don't forget to tag people in the future

Will do. Thanks!


Is this an official npm package by Flockler?

Hello!
The current documentation for flockler embeds here doesn't mention this package at all. This seems to be an official helper package but it would really help this package to be more trustworthy if the official docs would refer to it.

Moi @akselikap! Sorry for the really late response! 😅
Yes, this is an official package and we’ve added a mention of this to our documentation on March 28, 2022.


[gardening] Improve readability of pstdev in swift-bench.py

What's in this pull request?
This doesn't change how the function works, just makes it easier to follow:

Add a docstring that explains how standard deviation is computed
Use sample instead of l for the input variable
Use math.sqrt for readability
Break it down into a couple of intermediate steps for ease of comprehension

Plus a nicer error message in the case where you try to get the standard deviation of an empty list (previously you got a not-completely obvious ZeroDivisionError).
Resolved bug number: (SR-)
This isn't resolving any Swift bugs (that I know of).

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci Please Python lint

Looking at the lint issues

Lint issues should be fixed

@alexwlchan Excellent stuff! Thanks for some great contributions, please continue cleaning up the Python code in the repo if time permits :-)


Example.py: allow CoAP port customization and debug logging level

2 new parameters for example.py:

"--socket_port" : allows CoAP port customization.
"--debugger": set debug logging level.

I find it very odd that we know have two places for setting the port, one in the constructor and one in the initialize function.
The problem was that from the first we should have port the port in the constructor.
Consider this code:
coap = COAP(1234)
coap.initialize(1111)

We have now speficied two different ports and the port from the constructor will override the port  set by initialize
I think we should consider one of the following:

Move the port to the constructor and remove it from initialize, clean solution,  breaking change
Modify the example to pass the port via initialize (without using asynchronous context manager) - simple change

I find it very odd that we know have two places for setting the port, one in the constructor and one in the initialize function.

Agree

I think we should consider one of the following:

Move the port to the constructor and remove it from initialize, clean solution,  breaking change
Modify the example to pass the port via initialize (without using asynchronous context manager) - simple change

I prefer the second option, so I implemented it ;-)
Simone


icons show me sometimes chinese letters

hi,
i download fontello vector icon font,
sometimes show me all my icons like some chinese letters,
how i can fix that ?
thank you,

Please, create new issues with more details how to reproduce. Problem can be at your side, for example server does not serve font files.


Negative values unsupported in range slider

Do you want to request a feature or report a bug?
Bug. Example: https://jsfiddle.net/8zzvL5y1/
Bug: What is the current behavior?
Attributes with negative values do not show those negative values in the range slider. Additionally, explicitly setting a negative minimum doesn't seem to fix anything.
Bug: What is the expected behavior?
I'd expect any positive or negative numbers to be supported.
Bug: What browsers are impacted? Which versions?
Chrome (Mac) 61.0.3163.100
Bug: What is the proposed solution?

support negative values in facets
set range selection minimum appropriately

What is the version you are using? Always use the latest one before opening a bug issue.
<EMAIL_ADDRESS>

That's for the maintenance version. AFAIK, this is a limitation of the previous implementation of the slider, and we changed it in v2. I'm not sure we're gonna be able to make something for this v1. Can you update?

We will not add new features to maintenance releases, as said :)


Disable git comments

Hi there,
How do I disable this? I tried toggling the annotation setting but I don't think that is. Check the package settings but not sure what settings to switch. This happen when I click on a line.

@iamarmanjon that's actually a GitGutter feature. had the same issue and managed to disable it by setting "show_line_annotation": false in the GitGutter configuration file.

:D sorry, I should have debug more. Closing this.


[Serializer] Deal with recursive objects

Records can be recursive -
Ensure that doesn't cause an infinite loop in the serializer.

Example for future reference: https://github.com/microsoft/Power-Fx/blob/2e9130f2352b3a04a910a4ca86c8e8cb44c4e2c3/src/tests/Microsoft.PowerFx.Interpreter.Tests/MarshalTests.cs#L150

It's ok if we fail to serialize a recursive object.
But we can't hang / stack overflow.

Punting to 1.1 - cards can't actually hit this.


Medical Treatment

Required

[ ] Non surgery medical treatments like applying bandages, injections, consuming pills (instant effect healing) to recover entity health.
[ ] CPR/defibulator to try and resuscitate an entity in critical status.
[ ] Healing machines like the cryosleep casket (not cloning).

Optional

[ ] Metabolizing drugs for effects (delayed effect healing).

Requires #1472.

Assign me to this.

#1918 resolved the first point.

Currently bruise packs recover blunt damage and ointment recovers burn damage (welders don't currently give burn damage however when attacked with). Gauze is also in but has it's blunt recover effect commented out.

I wouldn't mind trying some of these. Handheld medical scanners would also be nice - it can just show whatever details the big body scanner shows for now, and maybe in a popup window.
Is the original ticket fairly up to date, or have any of those 4 points been solved? If there's a roadmap or other design document for medical gameplay, please let me know. Otherwise I'll probably make another HackMD and get organized.

@mirrorcult I was recommended to ping you on this for body system. No rush 🙂

I wouldn't mind trying some of these. Handheld health analyzers would also be nice - it can just show whatever details the big body scanner shows for now, and maybe in a popup window.
Is the original ticket fairly up to date, or have any of those 4 points been solved? If there's a roadmap or other design document for medical gameplay, please let me know. Otherwise I'll probably make another HackMD and get organized.
(edit: "medical scanners" -> "health analyzers")

First point is more or less okay. Drugs are now metabolised (or will be more body system dependent)
Body scanner will probably rely on body system to get individual body part damages.
I have the assets ported for defib but it's not in and will rely on body system. Similarly no cryo tubes or caskets etc.
Imo health analyser should be a nerfed scanner so can simply read out the values from the damage component for values of overall burn, brute etc. When body is in maybe it can scan individual limbs. Advanced version for CMO / research down the line that is a portable body scanner.

I'll try for some of these but will wait until #6147 is complete/merged first.

on each point this is either done or superseded by other issues


Chrome crash in PlatformSharedMemoryRegion with Ozone Wayland backend

This commit https://github.com/swaywm/wlroots/commit/d290b13871fa18dcad6cd90d9ee93e7205742124 is causing google chrome running natively in wayland to crash:
[71027:71027:0906/002722.685673:ERROR:cursor_loader.cc(115)] Failed to load a platform cursor of type kNull
[71027:71027:0906/002722.705785:ERROR:platform_shared_memory_region_posix.cc(47)] Descriptor access mode (0) differs from expected (2)
[71074:71074:0100/000000.311777:ERROR:gpu_init.cc(441)] Passthrough is not supported, GL is egl
google_chrome_stable: line 7: 71027 Trace/breakpoint trap   (core dumped) google-chrome-stable --enable-features=UseOzonePlatform --ozone-platform=wayland
[71074:71074:0100/000000.529227:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.

https://bugs.chromium.org/p/chromium/issues/detail?id=1246834

All chromium-based browsers currently throw an unrecoverable error when launching:
$ vivaldi-stable --enable-features=UseOzonePlatform --ozone-platform=wayland
[884998:884998:0923/150713.280127:ERROR:platform_shared_memory_region_posix.cc(47)] Descriptor access mode (0) differs from expected (2)
[1]    884998 trace trap (core dumped)  vivaldi-stable --enable-features=UseOzonePlatform --ozone-platform=wayland

$ opera-developer --enable-features=UseOzonePlatform --ozone-platform=wayland
[885107:885107:0923/151113.928380:ERROR:platform_shared_memory_region_posix.cc(47)] Descriptor access mode (0) differs from expected (2)
[1]    885107 illegal hardware instruction (core dumped)  opera-developer --enable-features=UseOzonePlatform --ozone-platform=wayland

@MarkusVolk can you please add this to the chromium bug?

I wanted to do this until this:
You need a Google Account associated with your email address in order to use the bug system.
I'm out here.
But didn't the google guy write that he tried it like this and ran into issues with gnome-shell?


Simplify access to enum values

This a proposal to fix #424.  I think this issue should be addressed in Julia itself.  There is some discussion of it online.  Other languages make this easier, IMHO.
Here are the ways to fix/mitigate this in order of simplicity.

Export all enum types.  Functions could accept parameters of type LoadModel (not PowerSystems.LoadModel).  However, you would have to type PowerSystems.ConstantPower::LoadModel in a notebook or REPL.

Export all enum types and values (manually or with some macro).  You could just type ConstantPower.  This would give Jose and Rodrigo what they want.  However, it would pollute the namespace.  All enum values would essentially be global variables and you could have collisions.  I think it is better to always to type the enum type with the value (ConstantPower::LoadModel).

Implement the workaround proposed here:  https://discourse.julialang.org/t/encapsulating-enum-access-via-dot-syntax/11785/2.  I think that this is the best solution.  In this PR I implemented it for one enum type.

Let me know what you guys think.

I like option 3. We can also decrease developer effort and avoid visual noise in code by using a macro to imitate default syntax.
"""
Macro to wrap Enum in a baremodule for keeping top level scope clean
"""
macro scoped_enum(T, args...)
    blk = esc(:(
            baremodule $(Symbol("$(T)s"))
               using Base: @enum
               @enum $T $(args...)
            end
        ))
    top = Expr(:toplevel, blk)
    return top
end

Usage:
julia> @scoped_enum Fruit Apple=1 Banana=2
Main.Fruits

julia> Fruits.Apple::Fruits.Fruit
Apple::Fruit = 1

I like the enum Dheepak proposed. We should put it in InfrastructureSystems.

Implemented the third option with support in IS.


Sync with 2017.06.23-1

Better env dir support

Codecov Report

Merging #19 into master will increase coverage by 0.16%.
The diff coverage is 94.36%.

@@            Coverage Diff             @@
##           master      #19      +/-   ##
==========================================
+ Coverage   86.08%   86.25%   +0.16%
==========================================
  Files          40       40
  Lines        2321     2364      +43
==========================================
+ Hits         1998     2039      +41
- Misses        323      325       +2

Impacted Files
Coverage Δ

lib/winss/environment.hpp
100% <ø> (ø)
:arrow_up:

lib/winss/filesystem_interface.cpp
11.67% <0%> (ø)
:arrow_up:

lib/winss/utils.cpp
98.27% <100%> (+0.97%)
:arrow_up:

lib/winss/svscan/svscan.hpp
98.18% <100%> (+0.22%)
:arrow_up:

lib/winss/process.cpp
98.13% <100%> (ø)
:arrow_up:

lib/winss/environment.cpp
95% <94.11%> (-5%)
:arrow_down:

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 8c792db...b0f667c. Read the comment docs.


Yet another environment pass-through PR

Compared to #39: I did not hard-code anything, so there won't be an ever-growing list of environment variables we need to manually pass through.
Compared to #40: I did not switch to systemd-run, therefore systemd still starts user sessions. Avoids reintroducing issues like #18 and #29.
Compared to #41: My patch is simpler and doesn't combine machinectl and systemd-run in confusing ways.

I also added the Windows %PATH% to the Linux $PATH, so running Windows exe's doesn't require specifying the full absolute file path.

Did you shutdown the WSL distro after building from my branch (i.e. run wsl -t NixOS)? It needs a fresh start to take effect.

I've been running this for a while now and it works perfectly.

Just rebuilt the tarball and it's working just fine. I probably got something wrong somewhere 😅


PATH order should take priority even if coqidetop.opt is before coqidetop

It looks like launch in xmlInterface.py the  above already tries both coqidetop and coqidetop.opt. However, prefer coqidetop over coqidetop.opt even if coqidetop is earlier in PATH. This means that adding a coqidetop.opt to PATH does not change coqtail to use it if coqidetop is already on the system path. This currently occurs when building coq master with dune.

I think #114 fixes this, but I'm having trouble getting coq to compile with dune locally, so it would be great if you could confirm if it works for you.


Can't find kernel

When I use qemu, virtualbox, or my own pc (literally), it can't find the kernel even if the filename is right.

I'm having an issue finding the kernel too. I thought it was my code but I used this code and I'm getting the same weird error. It seems to be reading from near the beginning of the main.img file. Instead of seeing the 'OS Booted' message, it shows 'Vx JAZZ OS FAT12'.
Booting from Floppy...
Loading...
Vx JAZZ OS FAT12     ╕

I found that i needed to update the kernel code, it is working with this, either i missed the change in the videos or it wasn't in them
ORG 0x0
BITS 16
main:
MOV si,os_boot_msg
call print
HLT
halt:
JMP halt
print:
PUSH si
PUSH ax
PUSH bx
print_loop:
LODSB
OR al,al
JZ done_print
MOV ah, 0x0E
MOV bh, 0
INT 0x10

JMP print_loop

done_print:
POP bx
POP ax
POP si
ret

os_boot_msg: DB 'OS has booted!', 0x0D, 0x0A, 0


[11.x] Fix PHP and Artisan binary

This PR fixes usages of PHP and Artisan binary on different places of the framework.

@hafezdivandari Are you going ahead with this? This fixes issues caused by the binary path via Herd: /Users/<user>/Library/Application Support/Herd/bin//php. The whitespace in Application Support causes an exception. I'm just wondering if Application can be used here since Concurrency doesn't depend on it in composer.json?

@devajmeireles yeah I'm gonna fix this if I can control my OCD!

I'm just wondering if Application can be used here since Concurrency doesn't depend on it in composer.json

It's Console\Application and I think we already require illuminate/console, because Cocurrency works by calling this command that depends on illuminate/console?

I'm just wondering if Application can be used here since Concurrency doesn't depend on it in composer.json

It uses Console\Application and I think we already require illuminate/console, because Cocurrency works by calling this command that depends on illuminate/console?

This is outdated. Previously you had entered Illuminate\Foundation\Application, but now it looks correct using Illuminate\Console\Application.

https://github.com/symfony/symfony/pull/52409
There are some internal differences between passing a string and an array to Symfony Process where using an array can be twice to 4x faster.


fix: move Natalia to Core Team

Yes! This is the best and most deserved PR :)

Superseded by https://github.com/vuejs/vuejs.org/commit/627f03b76d5d53d061192b92c4f78dcb042c7876


improve initial loading / updating times

see here: https://continuedev.slack.com/archives/C057XNXUUNT/p1688840812798559

Majority of the time comes from downloading the python requirements. These are often shared across updates, so if we installed the server instead in the ~/.continue directory it could reuse. We mostly just need to replace the .whl


expect('').toEqual([]) passes

expect('').toEqual([])

I would expect this to fail. This is probably more of an issue in the underlying lib that governs toEqual, but I thought it was worth reporting as an issue here.

toEqual is like == - and an empty array stringifies to the empty string. You should only be using toEqual when you know the possible types of the things you're comparing, and when you expect the associated implicit coercions. toBe is more like === if you want strict comparison.

Yeah, you might want deepEqual instead.
On Sat, Jul 9, 2016, 2:27 PM Jordan Harband<EMAIL_ADDRESS>wrote:

toEqual is like == - and an empty array stringifies to the empty string.
You should only be using toEqual when you know the possible types of the
things you're comparing, and when you expect the associated implicit
coercions. toBe is more like === if you want strict comparison.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mjackson/expect/issues/127#issuecomment-231518596,
or mute the thread
https://github.com/notifications/unsubscribe/AAEikSl7IpjY9VNs8Q1KQtMbig5Idl08ks5qTz9ngaJpZM4JIW1_
.

=== doesn't apply in this case, either. I understand how == and === work, but it seems like a bad thing that we literally cannot craft a test for this particular case.
Perhaps the correct thing is to check both typeof and ==?

@flushentitypacket Of course you can. expect(Array.isArray(foo)).toEqual(true); expect(foo).toEqual([]);

If you always make assertions on the types of things you're working with up front, you can avoid a lot of confusion later on - in tests as well as implementations.

Yeah, that seems like how I'll have to structure such a test going forward. Thanks!


HotReloading pure function components.

This is not an issue report but a question I couldn't find an answer for on my own.
As we were evaluating a number of bootstrap projects, what we've noticed about this one is that it hot reloads pure function components using react-transform + react-transform-hmr - something that should not be possible according to many sources (especially the author of above tool).
Would you mind shedding some light on how was this achieved?

Hello, @michael-donat. Yee, pure function hot reload is working, but i had problems with him past.
If you will use this boilerplate please tell me when meet this problem again.
I don't know why it's working now :) I remember that wanted to wait react-hot-reload 3


Stay consistent with variable names among modules (if possible)

What is the issue?
Variables of one context among modules named differently.
https://github.com/fredrikhgrelland/terraform-nomad-minio/blob/master/variables.tf#L95-L96
vault_kv_access_key    = string,
vault_kv_secret_key    = string

while in the Postgres module, has different suffix _name
https://github.com/fredrikhgrelland/terraform-nomad-postgres/blob/master/variables.tf#L85-L86
    vault_kv_username_name = string,
    vault_kv_password_name = string

Suggestion(s)/solution(s) [Optional]
Use one naming convention, smth like vault_kv_<entity>_name
Checklist (after created issue)

[X] Added label(s)
[ ] Added to project
[ ] Added to milestone

I believe the vault_kv_<entity>_name and vault_kv_<entity>_value for the key and value, respectively, for a KV-pair is a good way to go.

I imagine that credentials stored in a vault kv path, might be way more complex. I would suggest, smth like
vault_kv_<entrity>_fieldname or vault_kv_<entrity>_fieldkey
Take a look at JSON representation here, where the access_key and secret_key are fields.

I imagine that credentials stored in a vault kv path, might be way more complex. I would suggest, smth like
vault_kv_<entrity>_fieldname or vault_kv_<entrity>_fieldkey
Take a look at JSON representation here, where the access_key and secret_key are fields.

Not quite sure I got that, but I'm down to call it fieldname and fieldkey!

We can use naming from Vault cli, where you can specify -field
Example:
vault kv get -field=access_key secret/data/random-string/minio

We can use naming from Vault cli, where you can specify -field
Example:
vault kv get -field=access_key secret/data/random-string/minio

vault_kv_<entrity>_field <- like this

Good idea, I like that

Options

[ ] vault_kv_field_<entity>
[ ] vault_kv_<entity>_field
[ ] vault_kv_<entity>_name
[ ] vault_kv_<entity>_fieldname

Options

[ ]  vault_kv_field_<entity>
[ ]  vault_kv_<entity>_field
[ ]  vault_kv_<entity>_name
[ ]  vault_kv_<entity>_fieldname

Voting for vault_kv_field_<entity> 🙋


Bump version to v0.15.dev1

Contains dependencies for the UI repo.

Codecov Report

Merging #1665 (71e1737) into main (6dc3153) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #1665   +/-   ##
=======================================
  Coverage   68.12%   68.12%
=======================================
  Files          58       58
  Lines        6701     6701
=======================================
  Hits         4565     4565
  Misses       2136     2136


Error creating server: The attribute title has an invalid value. (STORAGE_TITLE_INVALID)

The error message is very cryptic.
What packer template attribute is it complaining about?
What is the value it is complaining, what part of the value is illegal?
This
source "upcloud" "cicd_upcloud" {
  template_prefix = "${local.template}"
  password        = "${var.upcloud_api_password}"
  storage_name = "ubuntu server 20.04"
  username     = "${var.upcloud_api_username}"
  zone         = "nl-ams1"
}

Appears to produce this:
2021/05/16 21:50:29 [INFO] Packer version: 1.7.2 [go1.16.3 linux amd64]
2021/05/16 21:50:29 [TRACE] discovering plugins in /usr/local/bin
2021/05/16 21:50:29 [TRACE] discovering plugins in /home/user/.packer.d/plugins
2021/05/16 21:50:29 [TRACE] discovering plugins in .
2021/05/16 21:50:29 [INFO] PACKER_CONFIG env var not set; checking the default config file path
2021/05/16 21:50:29 [INFO] PACKER_CONFIG env var set; attempting to open config file: /home/user/.packerconfig
2021/05/16 21:50:29 [WARN] Config file doesn't exist: /home/user/.packerconfig
2021/05/16 21:50:29 [INFO] Setting cache directory: /home/user/chef/packer/packer_cache
2021/05/16 21:50:29 [TRACE] listing potential installations for "github.com/vultr/vultr" that match "~>2.3.1". plugingetter.ListInstallationsOptions{FromFolders:[]string{"/usr/local/bin/packer", ".", "/home/user/.packer.d/plugins"}, BinaryInstallationOptions:plugingetter.BinaryInstallationOptions{APIVersionMajor:"5", APIVersionMinor:"0", OS:"linux", ARCH:"amd64", Ext:"", Checksummers:[]plugingetter.Checksummer{plugingetter.Checksummer{Type:"sha256", Hash:(*sha256.digest)(0xc000142180)}}}}
2021/05/16 21:50:29 [TRACE] Found the following "github.com/vultr/vultr" installations: [{/home/user/.packer.d/plugins/github.com/vultr/vultr/packer-plugin-vultr_v2.3.1_x5.0_linux_amd64 v2.3.1}]
2021/05/16 21:50:29 [INFO] found external [-packer-default-plugin-name-] builders from vultr plugin
2021/05/16 21:50:29 [TRACE] listing potential installations for "github.com/upcloudltd/upcloud" that match "~>v1.0.0". plugingetter.ListInstallationsOptions{FromFolders:[]string{"/usr/local/bin/packer", ".", "/home/user/.packer.d/plugins"}, BinaryInstallationOptions:plugingetter.BinaryInstallationOptions{APIVersionMajor:"5", APIVersionMinor:"0", OS:"linux", ARCH:"amd64", Ext:"", Checksummers:[]plugingetter.Checksummer{plugingetter.Checksummer{Type:"sha256", Hash:(*sha256.digest)(0xc000142180)}}}}
2021/05/16 21:50:30 [TRACE] Found the following "github.com/upcloudltd/upcloud" installations: [{/home/user/.packer.d/plugins/github.com/upcloudltd/upcloud/packer-plugin-upcloud_v1.0.0_x5.0_linux_amd64 v1.0.0}]
2021/05/16 21:50:30 [INFO] found external [-packer-default-plugin-name-] builders from upcloud plugin
2021/05/16 21:50:30 [TRACE] validateValue: not active for headless, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for linode_token, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for preseed_path, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for ruby_path_version, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for chef_config_path, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for guest_additions_url, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for mirror, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for release_version, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for chefdk_sha256, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for name, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for no_proxy, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for git_revision, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for http_proxy, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for memory, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for os_arch, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for policy_name, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for box_basename, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for digitalocean_spaces_secret, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for disk_size, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for vault_token, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for serial, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for upcloud_api_username, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for vault_addr, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for os, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for os_version, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for vultr_api_key, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for cpus, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for iso_checksum, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for iso_name, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for chefdk_commands, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for digitalocean_spaces_key, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for disk_interface, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for iso_checksum_type, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for mirror_directory, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for packer_run_uuid, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for upcloud_api_password, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for chefdk_version, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for digitalocean_token, so skipping
2021/05/16 21:50:30 [TRACE] validateValue: not active for https_proxy, so skipping
2021/05/16 21:50:30 [TRACE] Starting external plugin /home/user/.packer.d/plugins/github.com/upcloudltd/upcloud/packer-plugin-upcloud_v1.0.0_x5.0_linux_amd64 start builder -packer-default-plugin-name-
2021/05/16 21:50:30 Starting plugin: /home/user/.packer.d/plugins/github.com/upcloudltd/upcloud/packer-plugin-upcloud_v1.0.0_x5.0_linux_amd64 []string{"/home/user/.packer.d/plugins/github.com/upcloudltd/upcloud/packer-plugin-upcloud_v1.0.0_x5.0_linux_amd64", "start", "builder", "-packer-default-plugin-name-"}
2021/05/16 21:50:30 Waiting for RPC address for: /home/user/.packer.d/plugins/github.com/upcloudltd/upcloud/packer-plugin-upcloud_v1.0.0_x5.0_linux_amd64
2021/05/16 21:50:30 packer-plugin-upcloud_v1.0.0_x5.0_linux_amd64 plugin: 2021/05/16 21:50:30 Plugin address: unix /tmp/packer-plugin842328682
2021/05/16 21:50:30 Received unix RPC address for /home/user/.packer.d/plugins/github.com/upcloudltd/upcloud/packer-plugin-upcloud_v1.0.0_x5.0_linux_amd64: addr is /tmp/packer-plugin842328682
2021/05/16 21:50:30 packer-plugin-upcloud_v1.0.0_x5.0_linux_amd64 plugin: 2021/05/16 21:50:30 Waiting for connection...
2021/05/16 21:50:30 packer-plugin-upcloud_v1.0.0_x5.0_linux_amd64 plugin: 2021/05/16 21:50:30 Serving a plugin connection...
2021/05/16 21:50:30 packer-plugin-upcloud_v1.0.0_x5.0_linux_amd64 plugin: 2021/05/16 21:50:30 [TRACE] starting builder -packer-default-plugin-name-
2021/05/16 21:50:30 [TRACE] Starting internal plugin packer-provisioner-shell
2021/05/16 21:50:30 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-provisioner-shell"}
2021/05/16 21:50:30 Waiting for RPC address for: /usr/local/bin/packer
2021/05/16 21:50:30 Received unix RPC address for /usr/local/bin/packer: addr is /tmp/packer-plugin223373671
2021/05/16 21:50:30 packer-provisioner-shell plugin: [INFO] Packer version: 1.7.2 [go1.16.3 linux amd64]
2021/05/16 21:50:30 packer-provisioner-shell plugin: [INFO] PACKER_CONFIG env var not set; checking the default config file path
2021/05/16 21:50:30 packer-provisioner-shell plugin: [INFO] PACKER_CONFIG env var set; attempting to open config file: /home/user/.packerconfig
2021/05/16 21:50:30 packer-provisioner-shell plugin: [WARN] Config file doesn't exist: /home/user/.packerconfig
2021/05/16 21:50:30 packer-provisioner-shell plugin: [INFO] Setting cache directory: /home/user/chef/packer/packer_cache
2021/05/16 21:50:30 packer-provisioner-shell plugin: args: []string{"packer-provisioner-shell"}
2021/05/16 21:50:30 packer-provisioner-shell plugin: Plugin address: unix /tmp/packer-plugin223373671
2021/05/16 21:50:30 packer-provisioner-shell plugin: Waiting for connection...
2021/05/16 21:50:30 packer-provisioner-shell plugin: Serving a plugin connection...
2021/05/16 21:50:30 [TRACE] Starting internal plugin packer-provisioner-shell-local
2021/05/16 21:50:30 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-provisioner-shell-local"}
2021/05/16 21:50:30 Waiting for RPC address for: /usr/local/bin/packer
2021/05/16 21:50:30 Received unix RPC address for /usr/local/bin/packer: addr is /tmp/packer-plugin945441734
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: [INFO] Packer version: 1.7.2 [go1.16.3 linux amd64]
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: [INFO] PACKER_CONFIG env var not set; checking the default config file path
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: [INFO] PACKER_CONFIG env var set; attempting to open config file: /home/user/.packerconfig
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: [WARN] Config file doesn't exist: /home/user/.packerconfig
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: [INFO] Setting cache directory: /home/user/chef/packer/packer_cache
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: args: []string{"packer-provisioner-shell-local"}
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: Plugin address: unix /tmp/packer-plugin945441734
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: Waiting for connection...
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: Serving a plugin connection...
2021/05/16 21:50:30 [TRACE] Starting internal plugin packer-provisioner-shell-local
2021/05/16 21:50:30 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-provisioner-shell-local"}
2021/05/16 21:50:30 Waiting for RPC address for: /usr/local/bin/packer
2021/05/16 21:50:30 Received unix RPC address for /usr/local/bin/packer: addr is /tmp/packer-plugin235459429
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: [INFO] Packer version: 1.7.2 [go1.16.3 linux amd64]
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: [INFO] PACKER_CONFIG env var not set; checking the default config file path
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: [INFO] PACKER_CONFIG env var set; attempting to open config file: /home/user/.packerconfig
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: [WARN] Config file doesn't exist: /home/user/.packerconfig
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: [INFO] Setting cache directory: /home/user/chef/packer/packer_cache
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: args: []string{"packer-provisioner-shell-local"}
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: Plugin address: unix /tmp/packer-plugin235459429
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: Waiting for connection...
2021/05/16 21:50:30 packer-provisioner-shell-local plugin: Serving a plugin connection...
2021/05/16 21:50:30 [TRACE] Starting internal plugin packer-provisioner-file
2021/05/16 21:50:30 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-provisioner-file"}
2021/05/16 21:50:30 Waiting for RPC address for: /usr/local/bin/packer
2021/05/16 21:50:30 packer-provisioner-file plugin: [INFO] Packer version: 1.7.2 [go1.16.3 linux amd64]
2021/05/16 21:50:30 packer-provisioner-file plugin: [INFO] PACKER_CONFIG env var not set; checking the default config file path
2021/05/16 21:50:30 packer-provisioner-file plugin: [INFO] PACKER_CONFIG env var set; attempting to open config file: /home/user/.packerconfig
2021/05/16 21:50:30 packer-provisioner-file plugin: [WARN] Config file doesn't exist: /home/user/.packerconfig
2021/05/16 21:50:30 packer-provisioner-file plugin: [INFO] Setting cache directory: /home/user/chef/packer/packer_cache
2021/05/16 21:50:30 packer-provisioner-file plugin: args: []string{"packer-provisioner-file"}
2021/05/16 21:50:30 packer-provisioner-file plugin: Plugin address: unix /tmp/packer-plugin057781786
2021/05/16 21:50:30 packer-provisioner-file plugin: Waiting for connection...
2021/05/16 21:50:30 Received unix RPC address for /usr/local/bin/packer: addr is /tmp/packer-plugin057781786
2021/05/16 21:50:30 packer-provisioner-file plugin: Serving a plugin connection...
2021/05/16 21:50:30 [TRACE] Starting internal plugin packer-provisioner-file
2021/05/16 21:50:30 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-provisioner-file"}
2021/05/16 21:50:30 Waiting for RPC address for: /usr/local/bin/packer
2021/05/16 21:50:30 packer-provisioner-file plugin: [INFO] Packer version: 1.7.2 [go1.16.3 linux amd64]
2021/05/16 21:50:30 packer-provisioner-file plugin: [INFO] PACKER_CONFIG env var not set; checking the default config file path
2021/05/16 21:50:30 packer-provisioner-file plugin: [INFO] PACKER_CONFIG env var set; attempting to open config file: /home/user/.packerconfig
2021/05/16 21:50:30 packer-provisioner-file plugin: [WARN] Config file doesn't exist: /home/user/.packerconfig
2021/05/16 21:50:30 packer-provisioner-file plugin: [INFO] Setting cache directory: /home/user/chef/packer/packer_cache
2021/05/16 21:50:30 packer-provisioner-file plugin: args: []string{"packer-provisioner-file"}
2021/05/16 21:50:30 packer-provisioner-file plugin: Plugin address: unix /tmp/packer-plugin190166079
2021/05/16 21:50:30 Received unix RPC address for /usr/local/bin/packer: addr is /tmp/packer-plugin190166079
2021/05/16 21:50:30 packer-provisioner-file plugin: Waiting for connection...
2021/05/16 21:50:30 packer-provisioner-file plugin: Serving a plugin connection...
2021/05/16 21:50:30 [TRACE] Starting internal plugin packer-provisioner-shell
2021/05/16 21:50:30 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-provisioner-shell"}
2021/05/16 21:50:30 Waiting for RPC address for: /usr/local/bin/packer
2021/05/16 21:50:30 packer-provisioner-shell plugin: [INFO] Packer version: 1.7.2 [go1.16.3 linux amd64]
2021/05/16 21:50:30 packer-provisioner-shell plugin: [INFO] PACKER_CONFIG env var not set; checking the default config file path
2021/05/16 21:50:30 packer-provisioner-shell plugin: [INFO] PACKER_CONFIG env var set; attempting to open config file: /home/user/.packerconfig
2021/05/16 21:50:30 packer-provisioner-shell plugin: [WARN] Config file doesn't exist: /home/user/.packerconfig
2021/05/16 21:50:30 packer-provisioner-shell plugin: [INFO] Setting cache directory: /home/user/chef/packer/packer_cache
2021/05/16 21:50:30 packer-provisioner-shell plugin: args: []string{"packer-provisioner-shell"}
2021/05/16 21:50:30 Received unix RPC address for /usr/local/bin/packer: addr is /tmp/packer-plugin963194899
2021/05/16 21:50:30 packer-provisioner-shell plugin: Plugin address: unix /tmp/packer-plugin963194899
2021/05/16 21:50:30 packer-provisioner-shell plugin: Waiting for connection...
2021/05/16 21:50:30 packer-provisioner-shell plugin: Serving a plugin connection...
2021/05/16 21:50:30 [TRACE] Starting internal plugin packer-provisioner-shell
2021/05/16 21:50:30 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-provisioner-shell"}
2021/05/16 21:50:30 Waiting for RPC address for: /usr/local/bin/packer
2021/05/16 21:50:30 packer-provisioner-shell plugin: [INFO] Packer version: 1.7.2 [go1.16.3 linux amd64]
2021/05/16 21:50:30 packer-provisioner-shell plugin: [INFO] PACKER_CONFIG env var not set; checking the default config file path
2021/05/16 21:50:30 Received unix RPC address for /usr/local/bin/packer: addr is /tmp/packer-plugin489660315
2021/05/16 21:50:30 packer-provisioner-shell plugin: [INFO] PACKER_CONFIG env var set; attempting to open config file: /home/user/.packerconfig
2021/05/16 21:50:30 packer-provisioner-shell plugin: [WARN] Config file doesn't exist: /home/user/.packerconfig
2021/05/16 21:50:30 packer-provisioner-shell plugin: [INFO] Setting cache directory: /home/user/chef/packer/packer_cache
2021/05/16 21:50:30 packer-provisioner-shell plugin: args: []string{"packer-provisioner-shell"}
2021/05/16 21:50:30 packer-provisioner-shell plugin: Plugin address: unix /tmp/packer-plugin489660315
2021/05/16 21:50:30 packer-provisioner-shell plugin: Waiting for connection...
2021/05/16 21:50:31 packer-provisioner-shell plugin: Serving a plugin connection...
2021/05/16 21:50:31 [TRACE] Starting internal plugin packer-provisioner-shell-local
2021/05/16 21:50:31 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-provisioner-shell-local"}
2021/05/16 21:50:31 Waiting for RPC address for: /usr/local/bin/packer
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: [INFO] Packer version: 1.7.2 [go1.16.3 linux amd64]
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: [INFO] PACKER_CONFIG env var not set; checking the default config file path
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: [INFO] PACKER_CONFIG env var set; attempting to open config file: /home/user/.packerconfig
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: [WARN] Config file doesn't exist: /home/user/.packerconfig
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: [INFO] Setting cache directory: /home/user/chef/packer/packer_cache
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: args: []string{"packer-provisioner-shell-local"}
2021/05/16 21:50:31 Received unix RPC address for /usr/local/bin/packer: addr is /tmp/packer-plugin475519405
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: Plugin address: unix /tmp/packer-plugin475519405
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: Waiting for connection...
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: Serving a plugin connection...
2021/05/16 21:50:31 [TRACE] Starting internal plugin packer-provisioner-shell-local
2021/05/16 21:50:31 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-provisioner-shell-local"}
2021/05/16 21:50:31 Waiting for RPC address for: /usr/local/bin/packer
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: [INFO] Packer version: 1.7.2 [go1.16.3 linux amd64]
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: [INFO] PACKER_CONFIG env var not set; checking the default config file path
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: [INFO] PACKER_CONFIG env var set; attempting to open config file: /home/user/.packerconfig
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: [WARN] Config file doesn't exist: /home/user/.packerconfig
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: [INFO] Setting cache directory: /home/user/chef/packer/packer_cache
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: args: []string{"packer-provisioner-shell-local"}
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: Plugin address: unix /tmp/packer-plugin491885865
2021/05/16 21:50:31 Received unix RPC address for /usr/local/bin/packer: addr is /tmp/packer-plugin491885865
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: Waiting for connection...
2021/05/16 21:50:31 packer-provisioner-shell-local plugin: Serving a plugin connection...
upcloud.cicd_upcloud: output will be in this color.

2021/05/16 21:50:31 Build debug mode: false
2021/05/16 21:50:31 Force build: false
2021/05/16 21:50:31 On error:
2021/05/16 21:50:31 Waiting on builds to complete...
2021/05/16 21:50:31 Starting build run: upcloud.cicd_upcloud
2021/05/16 21:50:31 Running builder:
2021/05/16 21:50:31 [INFO] (telemetry) Starting builder
==> upcloud.cicd_upcloud: Creating temporary ssh key...
==> upcloud.cicd_upcloud: Getting storage...
==> upcloud.cicd_upcloud: Creating server based on storage "Ubuntu Server 20.04 LTS (Focal Fossa)"...
==> upcloud.cicd_upcloud: Error creating server: The attribute title has an invalid value. (STORAGE_TITLE_INVALID)
2021/05/16 21:50:34 [INFO] (telemetry) ending
==> Wait completed after 2 seconds 974 milliseconds
2021/05/16 21:50:34 machine readable: error-count []string{"1"}
==> Some builds didn't complete successfully and had errors:
Build 'upcloud.cicd_upcloud' errored after 2 seconds 974 milliseconds: Error creating server: The attribute title has an invalid value. (STORAGE_TITLE_INVALID)

2021/05/16 21:50:34 machine readable: upcloud.cicd_upcloud,error []string{"Error creating server: The attribute title has an invalid value. (STORAGE_TITLE_INVALID)"}
==> Builds finished but no artifacts were created.
2021/05/16 21:50:34 [INFO] (telemetry) Finalizing.
==> Wait completed after 2 seconds 974 milliseconds

==> Some builds didn't complete successfully and had errors:
--> upcloud.cicd_upcloud: Error creating server: The attribute title has an invalid value. (STORAGE_TITLE_INVALID)

==> Builds finished but no artifacts were created.
2021/05/16 21:50:35 waiting for all plugin processes to complete...
2021/05/16 21:50:35 /usr/local/bin/packer: plugin process exited
2021/05/16 21:50:35 /usr/local/bin/packer: plugin process exited
2021/05/16 21:50:35 /usr/local/bin/packer: plugin process exited
2021/05/16 21:50:35 /usr/local/bin/packer: plugin process exited
2021/05/16 21:50:35 /usr/local/bin/packer: plugin process exited
2021/05/16 21:50:35 /usr/local/bin/packer: plugin process exited
2021/05/16 21:50:35 /usr/local/bin/packer: plugin process exited
2021/05/16 21:50:35 /usr/local/bin/packer: plugin process exited
2021/05/16 21:50:35 /usr/local/bin/packer: plugin process exited
2021/05/16 21:50:35 /home/user/.packer.d/plugins/github.com/upcloudltd/upcloud/packer-plugin-upcloud_v1.0.0_x5.0_linux_amd64: plugin process exited

Fixed in https://github.com/UpCloudLtd/packer-plugin-upcloud/pull/10


Show autocomplete suggestions on click

In order to make autocomplete behave like a button, I added loadOnClick:

event handler and template:
https://github.com/emiguevara/ngTagsInput/commit/3ca413ec0ae6ec4987cf4bcc297af60448710302
implementation:
https://github.com/emiguevara/ngTagsInput/commit/b2227f3b2d9817a802c5c0d80c1838d61e10edeb

I'm not sure if it is the best way to accomplish this, first time I get dirty with angular modules.

+1 for this, will be really useful.

Sorry for not replying sooner.
That behavior can sort of be accomplished by setting the loadOnFocus option as true. And if you want the user to be able to reload the autocomplete list while the input is focused, you can turn the loadOnDownArrow option on.

Can this issue be closed?

yes, thanks for the reply


VTOL: Back transition Ramp Up problem.

Hi guys,
I think we found a bug in the Position / Mission modes for vtol.
Trying to fix the #8655 we made the VT_B_TRANS_DUR from 3 sec to 5 sec. And with the VT_B_TRANS_RAMP set to 3 sec. the ramp up of the quad motors to the "commanded thrust" happens in the middle of the transition and the throttle stays at that level up to the end of the transition, then it pasees the throttle to the MC.
In our case In Position mode the hover throttle is at 0.6 for the MC. So it is logical that the ramp up of the quad in the back transition go from 0 to hover throttle in order to hold the MC at current altitude (the idea behind Position mode) and continue like this up to the end of transition then pass the throttle to the MC to continue in Position mode until it stops.
The problem is that for the back transition ramp up commanded throttle PX4 uses VT_TRANS_THR which is the throttle for the front transition pusher motor.
You can see it clearly in:
Mission

LOG: https://logs.px4.io/plot_app?log=e6381c08-4b42-41f2-a01b-bd9f7f0bbb58
Position

LOG: https://logs.px4.io/plot_app?log=66fa60a2-e7b4-487e-b916-3c45f024daf3
We could not see this up to now because we had a 3 sec back transition with 3 sec ramp up and with pretty low VT_TRANS_THR = 0.7 .
Now because we fight the fron transition ramp up problem #8664 we made the VT_TRANS_THR = 0.9 and found out that during the back transition in Mission and Position modes the quad trhottle during the transition is so high that the VTOL just gains some 10-15 meters og height during the transition. It holds horizontal level but climbs drastically during the transition and then drops suddenly to hover throttle once in MC.
In Mission and Position modes neither the front transition ramp up neither the back transition ramp up are such to allow a smooth transition. at given altitude.

There should be no link in back transition and VT_TRANS_THR.
What i think is happening here is that the quad motor thrust somehow effects the pressure in the fuse whereby the vehicle thinks it's below requested altitude and starts commanding max thrust.

ps: 0.9 is from MPC_THR_MAX
@tubeme can you send a picture of your vtol?

@tubeme @sanderux I agree with @bresch that the problem is due to the effect of the transition on the barometer. I've seen this a lot in the past, some vehicles would not transition because they were climbing during the front transition because the baro said it was loosing altitude. This the vehicle never reaches the transition airspeed...
I've seen setups where this was hardly a problem (although I think some of them had custom hardware with proper static ports installed).
I think the next autopilots should have the option to install static ports, e.g. the board could come with a nipple so that you can attach a tube and put the static port where ever you want it.
@kd0aij Used to to some interesting tests https://gitter.im/PX4/Hardware/archives/2016/03/09

Isn't it coupled though? In forward transition that means changing the ramp up. In back transition it can be even worse. If the MC motors come on too quickly the barometric pressure issues are worse and feed back into the altitude controller commanding even more thrust.
In both cases I suspect we'd get better results by letting the appropriate controllers handle each throttle and stop forcing things.

@RomanBapst he is flying airspeedsensorless
@tubeme you are flying a deltaquad type system. A good staring point is:
VT_B_TRANS_DUR: 8.0
VT_F_TRANS_DUR: 1
VT_TRANS_MIN_TM: 12
VT_TRANS_THR: 100%
the maximum thrust you see in back transition is because the deltaquad returns to level from the quad perspective while doing the backtransition. This will likely cause altitude loss because your fixed wing is then pointing down. Try tuning TRIM_PITCH so your elevons are slightly up in neutral state to combat this behavior. (or mechanically offset them). Try with a value of 0.05 and see what happens on the bench in FW mode. start tuning from there.

@sanderux I'm  referring  to  a  static  port  for  the  baro which  of  course  could  also  be  used  for  the  airspeed  sensor.

@tubeme your setup is identical to ours and we do not have such issues. I would therefor conclude it is a matter of tuning. Closing for now. Let me know if you keep having problems.

@sanderux @RomanBapst @dagar
So we made a lot of flights since this problem occured. And I think we have a pattern. SO
The baro sensor is kind of laggy. So If we make the transition at leve flight, the normal way, there is no problems what so ever.
But if the pane is at height and we pitch down  to lower the pane height without  a throttle ie with a gliding and then during this descend we make the transition, the baro is always laggy and iPX4 always does this max throttle during the back transition. So in this very moment the GPS altitude is adequate, the acceleromater data is adequate, but the baro sensor continues to lower its reading for some 2,3,4 seconds so the PX4 kicks on the throttle. We try to give more weight on tha accelerometer data in the fusion but then this is not very good for the regular flying.
We tried this on 4 different boards and it is always the same.
BTW I cannot understand when we are in airpeedless mode where the TECS get their speed information?? We did not set the ground speed to be taken instead of the airspeed.

Does transition need to function during a descent? Would we lose anything if we enforced stabilized altitude before beginning the transition procedure? The way the current code is designed already effectively assumes normal level flight in good conditions.

Yes transition need to be fluent in all conditions. Because the novice pilots are expected to do a lot of irrational things. If there is a way to get in to account the GPS altitude as well for the fusion could be good idea. And BTW the plane is leveled during our transition innitiation. It is just that this happens after long descend . After long descent the baro is lagging behind.  I spoke with a friend in the airplane industry and he told me Baros are always made with this lag otherwise the baro reading will be much frantic all the time.

Did you try the params i suggested?

@sanderux Yes we tried it. But we have concerns in several points during the transition some are:

We want to make the transition as short as possible (for strong weather that is the way). We know it works perfect because we use a KK2.0 setup with no FW controller bench mark setup. So this in reality is manual setup airplane and a attitude stabilized quad. With it we make a perfect transition to full speed in 5 seconds, and during the whole transition the KK2.0 is at 50% throttle (the hover throttle) it makes the attitude corrections and at the end of transition just go to 0% throttle. This is pre-programmed in a Taranis. So it is a flip of a switch thing.

During the transition only the Attitude controller of both MC and FW works. This means that for Position or Mission transitions there will be no position control during the transition. Which in its term makes prolonged transition in strong weather to be tough for the VTOL's path. So again we want a shorter transition forth and back. in order to spend less time without Position control. Mainly because intend to allow only Altitude and Position modes for flying.

You keep comparing a manual control system to a position controlled system.
 You will see bad behavior from that.
I have implemented smart transition duration so it will transition back faster when you make it transition in a nose wind (it considers it complete when quadcopter cruise speed has been reached, or when the timeout occurs). If you give it a try you will notice your problems go away.

Alternatively you can do active breaking as i explained in this doc: https://docs.px4.io/en/config_vtol/vtol_back_transition_tuning.html

@sanderux Thanks a lot. I understand that we are engaging the MC while still in 10-12 m/s speed.
We are flying without airspeed so probably the smart transition will end when the MC cruise (ground) speed achieved. Is this in 1.7+? Or is it some other PR?
Do you know if we fly without airspeed where are the TECS getting their speed info from if it is not preset to take it from the ground speed?

@sanderux I saw the smart transition is in 1.7 thanks.

Without airspeed tecs doesnt know airspeed and just uses proportional scaling based on altitude


[Feature Request] fillet image component

Existing Component
否
Component Name
圆角图片组件
Description
圆角图片组件，用在Avatar等地方

Sorry, we have no plan to support this.


Invalid Shipping Address

Description
Shipping address is always invalid if country code is PH.
Steps to reproduce
Here is my button
paypal.Button.render({
env: 'sandbox', // sandbox | production
commit: true,
style: {
size:   'medium',    // medium | large | responsive
shape: 'pill',
color:  'gold'       // gold | blue | silver | black
},
client: {
sandbox:    'HadfgIeiFiz6s-0V6E4aLvRIPY2JhUg8gnqJzgJCCabgijn0sQo9yv-t3-BsdfgfdZPMvDcbx5H',
production: 'GasdfgU690oI-7jzf_LlwZIGMy4qu-mEpYva8xdfhdfhfasdfgmYYuj56nCmIxpfgphasdfas'
},
payment: function(data, actions) {
console.log('payment callback...');
    return actions.payment.create({
        payment: {
            transactions: [
                {
                    amount: { total: 123.00, currency: 'PHP' },
                    item_list: {
                        items: {
                            name: 'a',
                            description: 'abc',
                            quantity: 1,
                            price: 123.00,
                            tax: 0,
                            sku: 'a',
                            currency: 'PHP'
                        },
                        shipping_address: {
                            recipient_name: 'Brian Robinson',
                            line1: '4th Floor',
                            line2: 'Unit #34',
                            city: 'San Jose',
                            country_code: 'PH',
                            postal_code: '1600',
                            phone: '09567888987',
                            state: 'Metro Manila'
                        }
                    }
                }
            ],
            redirect_urls: {
                return_url: window.location.origin + "/success",
                cancel_url: window.location.origin + "/failure"
            }
        },
        experience: {
            input_fields: {
                no_shipping: 1
            }
        }
    });
},

// Wait for the payment to be authorized by the customer

onAuthorize: function(data, actions) {
    // Execute the payment
    console.log('authorization completed...');
    actions.redirect();
},
onCancel: function(data, actions) {
    console.log('authorization completed...');
    actions.redirect();
},
onError: function (err) {
    // Show an error page here, when an error occurs
    console.log(err);
}

}, '#paypal-button-container')
.then(function() {
console.log('button rendered...');
})

Can you check this one out @trainerbill ?

First off you client id didn't work so I grabbed the one from the demo app.  Secondly your JSON was not correct.  The items: is an array.  This worked for me in the payment callback.
payment: function(data, actions) {
            return actions.payment.create({
                payment: {
                    transactions: [
                        {
                            amount: { total: 123.00, currency: 'PHP' },
                            item_list: {
                                items: [{
                                    name: 'a',
                                    description: 'abc',
                                    quantity: 1,
                                    price: 123.00,
                                    tax: 0,
                                    sku: 'a',
                                    currency: 'PHP'
                                }],
                                shipping_address: {
                                    recipient_name: 'Brian Robinson',
                                    line1: '4th Floor',
                                    line2: 'Unit #34',
                                    city: 'San Jose',
                                    country_code: 'PH',
                                    postal_code: '1600',
                                    phone: '09567888987',
                                    state: 'Metro Manila'
                                }
                            }
                        }
                    ],
                    redirect_urls: {
                        return_url: window.location.origin + "/success",
                        cancel_url: window.location.origin + "/failure"
                    }
                },
                experience: {
                    input_fields: {
                        no_shipping: 1
                    }
                }
            });
        },

First off you client id didn't work so... - I apologize as I intentionally changed some part of the client id.
Secondly your JSON was not correct. The items: is an array... -  I apologize again. I don't know what happened but I guess I was a bit of in hurry when I created this issue. I actually have a dynamic array items:. I used the exact JSON above but still not working. Funny, because in my Paypal Guest Checkout, my country is still United States and my State is empty. Everything else is fine. When I try to login, I am getting this error. SHIPPING_ADDRESS_INVALID
{ 	"ack": "success", 	"data": { 		"memberSegment": { 			"ack": "success", 			"data": { 				"memberSegment": "" 			}, 			"meta": { 				"calc": "67bc1d9dc17d8", 				"rlog": "eabmw6eM025ODHFzdx07Yoo2WAXwZaCjXTHV9EO%2FQbLZ7aU%2F55sxLgPni%2B0ZMUTEgRKmrSaBBF7CMMQcO8GC%2FQ_16632fa274d" 			}, 			"server": "0g2uzX1wwa2_-MrXpEHyPUo_1Rs75Vk_vjed--Xf7W2PbjMSgDnSW01MBqAsGEj9qie0Za5pxRdlMNMUkIwf7-Q5XMgjPUnEH52WjFYDDtjmc8Lv-DOdv4sDHcqR85ppVgINsx7xl1ahkw2Hw-t8uuX1H6zn4NEkszRPPmE2xAPIVzxkrfs3gQTli_CtZWbQCFQdD6s5-W8FqvwvTe3MHyvvxgEE60569-JkmQvElq6ma0BXm4doj6bEv91NjryuYvRaypM9sBi" 		}, 		"eConsent": { 			"ack": "success", 			"data": { 				"required": false 			}, 			"meta": { 				"calc": "67bc1d9dc17d8", 				"rlog": "eabmw6eM025ODHFzdx07Yoo2WAXwZaCjXTHV9EO%2FQbLZ7aU%2F55sxLgPni%2B0ZMUTEgRKmrSaBBF7CMMQcO8GC%2FQ_16632fa274d" 			}, 			"server": "VnR8njViKdmmVBwgLhaNct4vxz1qRFHn9A7s7iclIn-1i0e0Ri1_wk506oU-LXg_3hVopD5P6Y2C0YqIM5LEAfkgoUqBonU6ehFud44rwmcKfd7Kl5JVE4er9lgO35yY35hieXk8MIPxES_G7sOiTu_mwN6VWRyBB6LGnqWinzUYqi3QoKcmmV0AXVNf9asZoKAm4De5qdFbeGgTzvKZ_GDM_e_HmUsDFdEpUlnZSOW9zvPfQoZwWuO_88-RRm1T" 		}, 		"createCheckoutSession": { 			"ack": "contingency", 			"contingency": "SHIPPING_ADDRESS_INVALID", 			"errorData": { 				"step_up_context": {} 			}, 			"meta": { 				"calc": "67bc1d9dc17d8", 				"rlog": "eabmw6eM025ODHFzdx07Yoo2WAXwZaCjXTHV9EO%2FQbLZ7aU%2F55sxLgPni%2B0ZMUTEgRKmrSaBBF7CMMQcO8GC%2FQ_16632fa274d" 			}, 			"server": "Yn0VjrLObqVaOIa-6aAD_43_Ebn8o9bJynM2wCld9IgPQ08AIA0QaergBksjhdPMoh-BcbHz0VcPwQz0ccX0ezekz9R8JUgMyk09zDITXVCbdiVyIEY12_7Vc10Bp5KAukfPY2npP2-7JCxI0KnBN1hsFWLptVrdQhxG0j9yqQN19hKHfjLAAgQFPPsIegPNf4QUU5PaLowJE6GXzmC8dK6eEFtDVkrt1zeRRxkDNdXcMoUts1e8b7NXrSP24X2gF_O2acvrGxAnpA0oBjYwiW" 		} 	}, 	"meta": { 		"calc": "67bc1d9dc17d8", 		"rlog": "eabmw6eM025ODHFzdx07Yoo2WAXwZaCjXTHV9EO%2FQbLZ7aU%2F55sxLgPni%2B0ZMUTEgRKmrSaBBF7CMMQcO8GC%2FQ_16632fa274d" 	}, 	"server": "I2BI5CpYLDBraOBtAkWZjnf1xYxkxd8Iq1yAE5yH4J8W2HAQLKEo3h8WvG649XpxEQSUYQSMHneisY2EawcAKFKfwqJD-Y9HKjwjhjtB0bH3B4WdyZuNd9ugIJgIk9VfEeQai_XDccYkQGxxw0Y6LVzRiB6ckTyGP1YJcxsiVLwUF6NS5hiSIvWCWgfH0GDhiTdbw083YWuF9tYwd_heXc5sZ3v-fcJk90Yq-sygD_W145QLZjMy-iMPQYS2zEPu" }
Thank you.

@rafaelcentric ok that is in our guest checkout product.  It is actually a known issue.  I will try and get some additional visibility to it.  The cause is the way we choose the default country in the list.  Right now it defaults to the merchants locale and not what is passed into the rest api call.

@trainerbill thank you for the support. Actually, the merchant's locale is also Philippines, not United States.  Anyway, we turned off the shipping address for now. Thanks.

I used the same way paypal.Button.render ....
The error message for invalid address is kinda unclear. I use braintree-web with paypal. The error message is like
**PAYPAL_INVALID_PAYMENT_OPTION **
it doesn't really indicate it is an address error.
Braintree does return full error however, paypal-checkout seems like removing some error details.
Could you guys improve the error handling?
Full error is like
code: "PAYPAL_INVALID_PAYMENT_OPTION"
message: "Error: PayPal payment options are invalid.↵    at Object._RECEIVE_MESSAGE_TYPE.(anonymous function) [as postrobot_message_response] (https://www.paypalobjects.com/api/checkout.4.0.233.js:2569:31)↵    at receiveMessage (https://www.paypalobjects.com/api/checkout.4.0.233.js:2611:60)↵    at messageListener (https://www.paypalobjects.com/api/checkout.4.0.233.js:2632:13)"
stack: "Error: Error: PayPal payment options are invalid.↵    at Object._RECEIVE_MESSAGE_TYPE.(anonymous function) [as postrobot_message_response] (https://www.paypalobjects.com/api/checkout.4.0.233.js:2569:31)↵    at receiveMessage (https://www.paypalobjects.com/api/checkout.4.0.233.js:2611:60)↵    at messageListener (https://www.paypalobjects.com/api/checkout.4.0.233.js:2632:13)↵    at deserializeError (http://localhost:8888/Content/build/dist/Checkout/vendor.js?hash=a1e52b3a82:153042:27)↵    at http://localhost:8888/Content/build/dist/Checkout/vendor.js?hash=a1e52b3a82:153063:274↵    at http://localhost:8888/Content/build/dist/Checkout/vendor.js?hash=a1e52b3a82:152877:34↵    at eachArray (http://localhost:8888/Content/build/dist/Checkout/vendor.js?hash=a1e52b3a82:152860:55)↵    at each (http://localhost:8888/Content/build/dist/Checkout/vendor.js?hash=a1e52b3a82:152866:39)↵    at replaceObject (http://localhost:8888/Content/build/dist/Checkout/vendor.js?hash=a1e52b3a82:152876:17)↵    at http://localhost:8888/Content/build/dist/Checkout/vendor.js?hash=a1e52b3a82:152878:173↵    at eachObject (http://localhost:8888/Content/build/dist/Checkout/vendor.js?hash=a1e52b3a82:152863:69)↵    at each (http://localhost:8888/Content/build/dist/Checkout/vendor.js?hash=a1e52b3a82:152866:148)↵    at replaceObject (http://localhost:8888/Content/build/dist/Checkout/vendor.js?hash=a1e52b3a82:152876:17)"

@maxisam are you using the client side integration pattern, calling actions.payment.create in the payment callback?  If so then you can see the exact error in the network tab when the XHR is called.

Well, braintree throw an error that is clear, but when it bubbles up to PayPal, PayPal doesn't preserve the detail of the error. You guys should work together to handle errors better.


Cleanup

Thanks @ThyMYthOS :+1:

@ThyMYthOS a new 0.3.1 release is available in alire

@Fabien-Chouteau thanks! Although I think it's not a good idea to update dependencies for a bugfix release.
Dependency to hal 0.4 should be done in usb_embedded 0.4.x.


Dragons Dogma 2 temporary free trial broke prices

Browser name and version: Any
Device (mobile or desktop): any
Page where the issue happens:
https://steamdb.info/app/2054970/

Describe the bug
Recent free trial for DD2 broke prices for the game on SteamDB main page, now everything is N/A.

Right. SteamDB showing Trial price which N/A. But you can still access to prices via sub: https://steamdb.info/sub/734193/


window.is_visible()

Would be great to be able to check if a window is visible. Useful for toggling a window's visibility

Tracked in https://github.com/tauri-apps/tao/issues/43

Closed by #1925


Timeline pattern

Implement the timeline pattern as specified on the patternfly.org site:
http://www.patternfly.org/pattern-library/data-visualization/timeline/

Closing due to inactivity.


Provide a mode where the operator can provision a service but will not delete the service with the CR is deleted

Currently, when a Service CR is created the operator will provision the service in the account and when that Service CR is deleted the operator will delete the service. In many environments, this is not desired as deleting a namespace or an application deployment will cause the resource (e.g. a database) to be deleted.
It would be helpful if there were a way (perhaps through an annotation) to tell the operator not to delete the resource when the CR is deleted.

Would be very good to see this capability. Any time horizon for this to be considered?

Would be very good to see this capability. Any time horizon for this to be considered?


fix: configure the default assetPrefix for MF apps correctly

Summary
The default asset prefix has been changed when using moduleFederation.options. These changes ensure that the assets of remote modules can be requested by consumer apps with the correct URL, and that the SPA URL fallback works as expected.

Only change the default asset prefix for MF provider apps.
Only change the default asset prefix in development mode (via dev.assetPrefix).
The default asset prefix has been changed from auto to true (equivalent to localhost:<port>)
Always prefer to use the dev.assetPrefix value set by user.

@nyqykk please take a look, I suppose these changes should be ported to @module-federation/rsbuild-plugin
Related Links
resolve: https://github.com/web-infra-dev/rsbuild/issues/3751
Checklist

[ ] Tests updated (or not required).
[x] Documentation updated (or not required).

ok i will port this to universe repo


Add spinners duration

Hello!
I wanted to help you with your project.
Here I added the ability to set the duration of the animation.
Please accept this help

Hey @DasneiN, thanks a lot for this contribution! 😃
I'll review and merge it today.

@DasneiN, I see that the ellipsis-loader is buggy, can you fix it?

I see that the ellipsis-loader duration is not working well, so I removed the duration from this component.
can you fix it?

Yes, I'll see what I can do.


Creating app.config.ts forces to define nuxtIcon

Environment

Operating System: Darwin
Node Version:     v18.15.0
Nuxt Version:     3.8.2
CLI Version:      3.10.0
Nitro Version:    2.8.0
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, typescript, modules
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Version
v2.11.0
Reproduction
Create an app.config.ts without nuxtIcon and run build task
export default defineAppConfig({   ui: {     primary: 'teal',     gray: 'neutral'   } })
Description
We should be able to create app.config.ts without nuxtIcon (following is ok)
export default defineAppConfig({   nuxtIcon: {},   ui: {     primary: 'teal',     gray: 'neutral'   } })
Additional context
v2.11.0 brings following dependency
"nuxt-icon": "^0.6.6",
Logs
No response

This is weird I haven't encountered this myself, also it should have been fixed already in https://github.com/nuxt-modules/icon/pull/113.

I tried to reproduce with a new project and indeed to have the issue, you also need to run pnpm i -D typescript vue-tsc and in nuxt.config.ts add
typescript: {
    typeCheck: true
  }

Shouldn't we have nuxtIcon?: {...} instead in following in Icon.vue ?
const appConfig = useAppConfig() as {
  nuxtIcon: {
    size?: string
    class?: string
    aliases?: Record<string, string>
    iconifyApiOptions?: {
      url?: string
      publicApiFallback?: boolean
    }
  }
}

I'm running into this issue as well with typeCheck: true using the latest 0.6.1 release. The only want to fix it is defined nuxtIcon in the app config otherwise builds fail. Here is my config:
export default defineAppConfig({
  /**
   * Nuxt UI
   * https://ui.nuxt.com/getting-started/theming
   */
  ui: {
    primary: 'yellow',
    gray: 'stone',
  },
  /**
   * TODO: Remove this when the issue listed below is fixed.
   * https://github.com/nuxt/ui/issues/1043
   */
  nuxtIcon: {},
})

For good measure I did a fresh install of node_modules but the issue is still occurring.

Related to https://github.com/nuxt-modules/icon/issues/117


cilium-operator does not use IAM Role for ServiceAccounts to access AWS API

Bug report
We deploy our clusters with eksctl 0.30. Since ekstl 0.28 the nodes do not get the Policy arn:aws:iam::aws:policy/AmazonEKS_CNI_Policy  attached. Therefore we want to use an IAM Role for ServiceAccounts. However, the cilium-operator seem to ignore this instance role since our logs of the cilium-operator says:
level=info msg="Retrieving own metadata from EC2 metadata server..." subsys=ipam-allocator-aws
level=info msg="Connected to EC2 metadata server" instance=i-08cb4b6758811177c region=eu-central-1 subsys=ipam-allocator-aws
level=info msg="Connected to EC2 service API" subsys=ipam-allocator-aws
level=warning msg="Unable to synchronize EC2 interface list" error="UnauthorizedOperation: You are not authorized to perform this operation.\n\tstatus code: 403, request id: 23cb8daa-90bc-49e0-94eb-358a2e609770" subsys=eni
level=fatal msg="Unable to start eni allocator" error="Initial synchronization with instances API failed" subsys=cilium-operator-aws

General Information

Cilium version: 1.8.4
Kernel version: 4.14.198-152.320.amzn2.x86_64
Orchestration system version in use: managed elastic kubernetes v1.18.8-eks-7c9bda

How to reproduce the issue
Deploy cluster with eksctl >= 0.28.0 . Enable withOIDC.

Controlled By:  ReplicaSet/cilium-operator-55cf8d97bb
Containers:
  cilium-operator:
    Container ID:  docker://0dc151f58d699026bff79c2d3b3358f8bc7d979c58e5fef70af15dbaa6b7d4ca
    Image:         docker.io/cilium/operator-aws:v1.8.4
    Image ID:      docker-pullable://cilium/operator-aws@sha256:68d4a24fc5388063d8f4f679c276f838f069851a039e8e5678d4b7db0667d48f
    Port:          <none>
    Host Port:     <none>
    Command:
      cilium-operator-aws
    Args:
      --config-dir=/tmp/cilium/config-map
      --debug=$(CILIUM_DEBUG)
[...]
    Environment:
      K8S_NODE_NAME:                 (v1:spec.nodeName)
      CILIUM_K8S_NAMESPACE:         kube-system (v1:metadata.namespace)
      CILIUM_DEBUG:                 <set to the key 'debug' of config map 'cilium-config'>           Optional: true
      AWS_ACCESS_KEY_ID:            <set to the key 'AWS_ACCESS_KEY_ID' in secret 'cilium-aws'>      Optional: true
      AWS_SECRET_ACCESS_KEY:        <set to the key 'AWS_SECRET_ACCESS_KEY' in secret 'cilium-aws'>  Optional: true
      AWS_DEFAULT_REGION:           <set to the key 'AWS_DEFAULT_REGION' in secret 'cilium-aws'>     Optional: true
      AWS_ROLE_ARN:                 arn:aws:iam::xxxxxxxx:role/eksctl-cluster-name-addon-iamserviceaccou-Role1-1PFQQDTWNTIFT
      AWS_WEB_IDENTITY_TOKEN_FILE:  /var/run/secrets/eks.amazonaws.com/serviceaccount/token
    Mounts:
      /tmp/cilium/config-map from cilium-config-path (ro)
      /var/run/secrets/eks.amazonaws.com/serviceaccount from aws-iam-token (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from cilium-operator-token-jzwbq (ro)

hi @hikhvar, thanks for reporting this!
I think that using arn:aws:iam::aws:policy/AmazonEKS_CNI_Policy maybe insufficient for Cilium as the implementation differs from AWS VPC CNI significantly.
Since Cilium relies on EKS instance role, I'd recommend adding arn:aws:iam::aws:policy/AmazonEKSWorkerNodePolicy. If you could test it, it would be very helpful.

I can cross check this.
However, my current workaround is to manually add the policies arn:aws:iam::aws:policy/AmazonEKS_CNI_Policy and arn:aws:iam::aws:policy/AmazonEKSWorkerNodePolicy  to my worker nodes instance profile. This works so far. Furthermore I could not see any access to the cilium service account instance role in the IAM console. Thus I thought, cilium is not using the instance role at all. I tried to debug this in the go code myself but I did not see any odd settings. But I'm not that familar with the aws-go-sdk-v2.

@hikhvar did you have a chance to try using both policies with the service account?

Ok, I removed the arn:aws:iam::aws:policy/AmazonEKS_CNI_Policy policy from the worker nodes instance roles. Than I added arn:aws:iam::aws:policy/AmazonEKSWorkerNodePolicy to the service account role of the cilium operator.
Now I'm back to the start of this issue. The pods are unable to list the interfaces.
My next step was to upgrade to cilium 1.9.0 since the used aws-sdk was bumped to v0.23 from v0.18
https://github.com/cilium/cilium/pull/12393
But now I still get:
level=info msg="Initializing IPAM" mode=eni subsys=cilium-operator-aws
level=info msg="Starting ENI allocator..." subsys=ipam-allocator-aws
level=info msg="Retrieving own metadata from EC2 metadata server..." subsys=ipam-allocator-aws
level=info msg="Connected to EC2 metadata server" instance=i-0e06c11adbbd82f9f region=eu-central-1 subsys=ipam-allocator-aws
level=info msg="Connected to EC2 service API" subsys=ipam-allocator-aws
level=warning msg="Unable to synchronize EC2 interface list" error="UnauthorizedOperation: You are not authorized to perform this operation.\n\tstatus code: 403, request id: 2d16e8e1-394c-40c6-8225-91024e173cfe" subsys=eni
level=fatal msg="Unable to start eni allocator" error="Initial synchronization with instances API failed" subsys=cilium-operator-aws

So, fixed the service acoount mapping. Upgrading to cilium 1.9.0 fixed the issue for me :tada:

@joestringer @aanm I am not sure if we should consider this as a 1.8 bug that needs addressing, I think this is just a missing feature - wdyt?

If it is fixed in 1.9.0 we can close this issue since it is fixed.

@aanm I am just looking back at this, and looks like we are using AWS SDK v2, which is still beta. This feature was supposed to work automatically with classic SDK supported since 1.23.13. I have looked at v2's changelog, but couldn't see any reference to this... I am slightly concerned that v2 could be still too  experimental. I'll keep looking, it would be good to link to an upstream issue.

Ok, looks like SDK v2 was just lagging behind v1 on this feature (see https://github.com/aws/aws-sdk-go-v2/issues/338 and https://github.com/aws/aws-sdk-go-v2/pull/507.

Getting the same error in newer version as well(1.9.6)
level=info msg="Connected to EC2 service API" subsys=ipam-allocator-aws level=warning msg="Unable to synchronize EC2 interface list" error="UnauthorizedOperation: You are not authorized to perform this operation.\n\tstatus code: 403, request id: xxxxx" subsys=eni
Have verified Imdsv2 and Imdsv1 is working fine in my worker nodes.(Given this because of aws-sdk-v2 depedency)
Followed this for Cilium deployment: https://docs.cilium.io/en/v1.9/gettingstarted/k8s-install-eks/#deploy-cilium, Actually didn't spend much on troubleshooting this issue, Do I need to configure any additional thing to use the worker role. From the error it says that it was not able to authenticate.

Having this same issue on all latest images and tools.

Cilium helm chart is designed in the way that you have to set  .Values.eni.iamRole: <iam-role-arn> parameter. The chart will create cilium-operator service account annotations for you. Otherwise, cilium-operator will fail because the AWS default region environment variable is not set (link).


Implement new layout/design

We will do some basic redesign based on the mockup below:

This is how it looks right now:

Performance over time:

Diagram Generator:

Waterfall diagram:

Boomerang JS Builder:

So far so good!
Closing because the current results are satisfying.


add to list at jhuangtw-dev/xg2xg

https://github.com/jhuangtw-dev/xg2xg/commit/7a8c90ca82ab31ad19cc86c62c64f392fb002b11#diff-04c6e90faac2675aa89e2176d2eec7d8


[Refactor] Evaluate If Preact Pre-Render Workaround Is Still Necessary.

Code Snippet:
https://github.com/TaiwanVtuberData/TaiwanVTuberData.github.io/blob/ea2ea9f765327a329a79e11fa1ca234c623a8a76/src/utils/CookieUtils.ts#L17-L22

Resolved.


Neptune Logger assumes unix-style filepath for model checkpoint

The Neptune Logger can automatically upload model checkpoints if the callback is used. It generates an "expected_model_path" for that. This path has hard-coded a '/' at the end (see here), which can cause problems on Windows systems because the actual path has (or can have) a backslash at this position. A simple fix would be to use os.path.sep insteat of '/'.
cc @justusschock @awaelchli @akihironitta

never mind, there is already a pull request (#10500) for this problem

Let's use this issue then to link with the PR (which had no bug report attached).
I interpret that you are reporting a bug.


ValidateSamFile detects errors in BAM files after soft-clipping primers with BamClipper

Dear Tommy,
I've used the following command to soft-clip primers:
ls *.bam | parallel '/usr/local/bin/bamclipper.sh -b {} -p ./TruSeq.bedpe -n 4'
I've run Picard's ValidateSamFile before and after primer clipping. BAM files were free of errors before running BamClipper but ValidateSamFile revealed a bunch of errors and warnings in the clipped files. Example of ValidateSamFile's output:

HISTOGRAM	java.lang.String
Error Type	Count
ERROR:INVALID_FLAG_SUPPLEMENTARY_ALIGNMENT	138
ERROR:INVALID_MAPPING_QUALITY	315
ERROR:MISMATCH_FLAG_MATE_UNMAPPED	217
ERROR:MISMATCH_MATE_ALIGNMENT_START	8775
ERROR:MISMATCH_MATE_CIGAR_STRING	2385125
WARNING:MISSING_TAG_NM	2387464

Is it the expected outcome of soft-clipping primer sequences? How to handle it?

Thanks for your report. I have not tested the BAMClipper output to pass ValidateSamFile test. However, various mainstream variant callers were tested to properly work on BAMClipper output without warning or errors.

I am facing the same error and this seems to cause problems for jbrowse which complains that it cannot uncompress the bam file:

Is there any update on this?


[Lightbox video player] Caption override enhancements

originally discussed here https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/7025#pullrequestreview-743172648
related:
#5642
#5753
#6195
The React and web component versions of the lightbox video player should be able to take custom captions, similar to the standalone video player (see related issues)

should be covered in #6878 and unblocked by #7007 and #7025


Add support for Python 3.13

Python 3.13 will be released on October 1st. After testing has been performed, the package metadata should be updated to support 3.13.
Also consider bumping the Docker image to use python-3.13.

Python 3.13 release is now October 7th. Will cut a new release next week with support, pending sufficient time to perform regression testing (CA/Browser Forum F2F might throw a wrench in that plan).