text not visible in dark mode

Current Behavior
The text 01 & 02 are not clearly visible

here too:

Expected Behavior
The 01 & 02 should be green /black  in color or any other color
Please assign me this issue

Thank you for raising this up, @ranjanmangla1.

@ranjanmangla1 would you like to give an update?

Can I work on this ? @vishalvivekm @leecalcote

Sure @Ardent10,  go ahead and fix it :rocket:

its visible in mine however

//@thisiskaransgit

Thanks @Ghat0tkach, yeah the adopter container looks fine, the step numbers can use another shade though, since we haven't heard back from @ranjanmangla1. Assigning the issue to @Ardent10 🚀 , for only updating the step-number color.

@thisiskaransgit Sorry, I had been inactive for a week, i have solved this issue already, and i just have to make a pull request. Sorry, had been busy ,somehere. @Ardent10 , if you don't mind, can this issue be reassigned to me?

@ranjanmangla1 you can ask @thisiskaransgit.

@ranjanmangla1, push the update please

@thisiskaransgit can i work on this issue

Guys updates? @Ardent10 @ranjanmangla1

Solved, sending a pr @Savio629

hi @thisiskaransgit and @Ghat0tkach , i have fixed this, i have found another issue here in meshery.io:
there is no hierarchy in headings of catalog, calendar, and programs, these headings convey an important info and should be highlighted.
Catalog:

Community Calendar

Programs:

Should i modify this changes in pr of this issue itself as these are just minor changes or i should open a new issue?


Change semver from tilde to caret for dependencies

Currently the blueprint has many occurrences of ~(tilde). This prevents seamless upgrades of minor versions.
As far as I know, it's quite safe to use ^ (caret). Is there any history for this semver usage, or it's just too old and not updated?
Since upgrading blueprints is a annoying work, let's minimize the effort to change them.

It is safe if the package follows semver and doesn't introduce breaking changes in patch or minor versions.  The versioning strategy was chosen to emphasize safety and minimize breakage.
If someone is comfortable with the increased risk potential, they can always adjust the versioning for their individual project.  In general, as a project grows and ages, the packages and their required versions will become more specific to the project regardless.

To be honest even ~ has proved problematic in many occasions. This isn't something that we're looking to relax.


upstream: fixes comment to remove references to LogicalHostDescriptionImpl

Commit Message: A prior PR to fix a race in LogicalHost left a stale comment; this fixes it.
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:

LGTM


Razor Pages are missing RedirectToLocal helper method

The RedirectToLocal method should be on the Microsoft.AspNetCore.Mvc.RazorPages.PageModel and Microsoft.AspNetCore.Mvc.RazorPages.Page base classes.

Superseded by #5846 - which has the comprehensive list of action result helpers.


Segfault

After updating the library I started getting SIGSEGV.
The commit cec178dcef3ce809c6d567dca9f8122464d5a53d still works just fine.
It stopped working when REVM was bumped to 12.1.
I decided to debug it via GDB, attaching logs:
P.S. libdexy is the bytecode I statically linked via:
revmc_context::extern_revmc! {
    fn libdexy;
}

(gdb) backtrace
#0  0x0000555555ad0bf9 in libdexy ()

#1  0x0000555555a82222 in revmc_context::EvmCompilerFn::call (self=..., stack=..., stack_len=..., ecx=0x7bfee2ff6da8)
    at /root/.cargo/git/checkouts/revmc-cb5494447e430bb4/4ad65bd/crates/revmc-context/src/lib.rs:320

#2  0x0000555555a81d4a in revmc_context::EvmCompilerFn::call_with_interpreter (self=..., interpreter=0x7bfee1c7c400, host=...)
    at /root/.cargo/git/checkouts/revmc-cb5494447e430bb4/4ad65bd/crates/revmc-context/src/lib.rs:271

#3  0x0000555555a8202a in revmc_context::EvmCompilerFn::call_with_interpreter_and_memory (self=..., interpreter=0x7bfee1c7c400, memory=0x7bfee2ff73c0, host=...)
    at /root/.cargo/git/checkouts/revmc-cb5494447e430bb4/4ad65bd/crates/revmc-context/src/lib.rs:247

#4  0x0000555555ad7e9a in strategy::simulator::register_handler::{closure#0}<revm::db::in_memory_db::CacheDB<ethmatrix::duality::Duality>> (frame=0x7bfee1c80000, memory=0x7bfee2ff73c0,
    tables=0x7bfee2ff9e78, context=0x7bfee2ff9af0) at crates/strategy/src/simulator/mod.rs:107

#5  0x0000555555bfb732 in revm::handler::handle_types::execution::ExecutionHandler<strategy::simulator::ExternalContext, revm::db::in_memory_db::CacheDB<ethmatrix::duality::Duality>>::execute_frame<strategy::simulator::ExternalContext, revm::db::in_memory_db::CacheDB<ethmatrix::duality::Duality>> (self=0x7bfee2ff9dc8, frame=0x7bfee1c80000, shared_memory=0x7bfee2ff73c0,
    instruction_tables=0x7bfee2ff9e78, context=0x7bfee2ff9af0) at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/revm-12.1.0/src/handler/handle_types/execution.rs:175

#6  0x0000555555c1b6bc in revm::handler::Handler<revm::context::Context<strategy::simulator::ExternalContext, revm::db::in_memory_db::CacheDB<ethmatrix::duality::Duality>>, strategy::simulator::ExternalContext, revm::db::in_memory_db::CacheDB<ethmatrix::duality::Duality>>::execute_frame<strategy::simulator::ExternalContext, revm::db::in_memory_db::CacheDB<ethmatrix::duality::Duality>> (
    self=0x7bfee2ff9d00, frame=0x7bfee1c80000, shared_memory=0x7bfee2ff73c0, context=0x7bfee2ff9af0) at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/revm-12.1.0/src/handler.rs:118

#7  0x0000555555aea394 in revm::evm::Evm<strategy::simulator::ExternalContext, revm::db::in_memory_db::CacheDB<ethmatrix::duality::Duality>>::run_the_loop<strategy::simulator::ExternalContext, revm::db::in_memory_db::CacheDB<ethmatrix::duality::Duality>> (self=0x7bfee2ff9af0, first_frame=...) at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/revm-12.1.0/src/evm.rs:95

#8  0x0000555555aebec8 in revm::evm::Evm<strategy::simulator::ExternalContext, revm::db::in_memory_db::CacheDB<ethmatrix::duality::Duality>>::transact_preverified_inner<strategy::simulator::ExternalContext, revm::db::in_memory_db::CacheDB<ethmatrix::duality::Duality>> (self=0x7bfee2ff9af0, initial_gas_spend=23192)
    at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/revm-12.1.0/src/evm.rs:371

#9  0x0000555555aec71d in revm::evm::Evm<strategy::simulator::ExternalContext, revm::db::in_memory_db::CacheDB<ethmatrix::duality::Duality>>::transact<strategy::simulator::ExternalContext, revm::db::in_memory_db::CacheDB<ethmatrix::duality::Duality>> (self=0x7bfee2ff9af0) at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/revm-12.1.0/src/evm.rs:236

#10 0x0000555555aeb584 in revm::evm::Evm<strategy::simulator::ExternalContext, revm::db::in_memory_db::CacheDB<ethmatrix::duality::Duality>>::transact_commit<strategy::simulator::ExternalContext, revm::db::in_memory_db::CacheDB<ethmatrix::duality::Duality>> (self=0x7bfee2ff9af0) at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/revm-12.1.0/src/evm.rs:46

#11 0x0000555555c19678 in strategy::simulator::dexy::evaluate_arb_revenue (arb_amount=..., next_block=0x7fffffffc0d0, duality=..., cycle=0x7bfeb5e12040, victim_txs=...)
    at crates/strategy/src/simulator/lil_dexy.rs:216

#12 0x0000555555adbef5 in strategy::simulator::dexy::find_optimal_inputs::{closure#2} () at crates/strategy/src/simulator/lil_dexy.rs:105

What we can understand from the backtrace (imho):

Frame 0: The segmentation fault occurred in the libdexy macro-generated function.
Frame 1: The libdexy function was called by revmc_context::EvmCompilerFn::call.
Frame 2: This function call occurred within revmc_context::EvmCompilerFn::call_with_interpreter.
Frame 3: Which was called by revmc_context::EvmCompilerFn::call_with_interpreter_and_memory.
Frame 4-11: The subsequent frames show the nested function calls within the revmc_context, strategy::simulator, and revm crates leading up to the segmentation fault.
Frame 12: The last frame shows a closure in strategy::simulator::lil_dexy::find_optimal_inputs.

Locals info:
(gdb) frame 1

#1  0x0000555555a82222 in revmc_context::EvmCompilerFn::call (self=..., stack=..., stack_len=..., ecx=0x7bfee2ff6da8) at /root/.cargo/git/checkouts/revmc-cb5494447e430bb4/4ad65bd/crates/revmc-context/src/lib.rs:320
320             (self.0)(

(gdb) info locals
No locals.

(gdb) info args
self = revmc_context::EvmCompilerFn (0x555555ac33b0 <libdexy>)
stack = core::option::Option<&mut revmc_context::EvmStack>::Some(0x7bfee1c72600)
stack_len = core::option::Option<&mut usize>::Some(0x7bfee1c7c520)
ecx = 0x7bfee2ff6da8

(gdb) print self
$1 = revmc_context::EvmCompilerFn (0x555555ac33b0 <libdexy>)

(gdb) print self.0
$2 = (*mut fn (*mut revm_interpreter::gas::Gas, *mut revmc_context::EvmStack, *mut usize, *mut revm_primitives::env::Env, *mut revm_interpreter::interpreter::contract::Contract, *mut revmc_context::EvmContext) -> revm_interpreter::instruction_result::InstructionResult) 0x555555ac33b0 <libdexy>

Mem dump for Frame 1:
Arg `stack`:

(gdb) x/16x 0x7bfee1c72600
0x7bfee1c72600: 0x00000024      0x00000000      0x00000000      0x00000000
0x7bfee1c72610: 0x00000000      0x00000000      0x00000000      0x00000000
0x7bfee1c72620: 0x00000064      0x00000000      0x00000000      0x00000000
0x7bfee1c72630: 0x00000000      0x00000000      0x00000000      0x00000000

Arg `stack_len`:

(gdb) x/16x 0x7bfee1c7c520
0x7bfee1c7c520: 0x0000000000000000      0x0000000000000000
0x7bfee1c7c530: 0x0000000000000008      0x0000000000000000
0x7bfee1c7c540: 0x0000000000000000      0x00007bfee2ffea58
0x7bfee1c7c550: 0x00007bfee2ffea58      0x00000000000cbfe8
0x7bfee1c7c560: 0x00007bfee2ffea58      0x00007bfee1c7c400
0x7bfee1c7c570: 0x00007bfee2ffef50      0x00000000000cbfe8
0x7bfee1c7c580: 0x00007bfee2ffea70      0x000055555745cc08
0x7bfee1c7c590: 0x00007bfee1c87000      0x0000000000000f76

Arg `ecx`:

(gdb) x/16x 0x7bfee2ff6da8
0x7bfee2ff6da8: 0x00007bfee2ff9af0      0x00005555573a3338
0x7bfee2ff6db8: 0x0000000000000001      0x0000000000000000
0x7bfee2ff6dc8: 0x0000000000000000      0x00007bfee1c7c4d8
0x7bfee2ff6dd8: 0x00007bfee1c7c400      0x00007bfee1c7c5d0
0x7bfee2ff6de8: 0x00007bfee1c7c548      0x00007bfee1c7c528
0x7bfee2ff6df8: 0x00007fff6df10000      0x00007bfee2ff9af0
0x7bfee2ff6e08: 0x00005555573a3338      0x0000000000000001
0x7bfee2ff6e18: 0x0000000000000000      0x0000000000000000

Attempted to examine the stack reference but encountered issues with direct dereferencing, hence did mem inspection via x/16a command and concluded the following:

Inspected memory contents at addresses provided by stack, stack_len, and ecx using the x/16a command.
Found that stack contains valid-looking memory data with significant values at specific offsets.
stack_len showed a length value, and other pointers appeared valid.
ecx also contained a mix of valid pointers and data.

Place in code where it panics:
https://github.com/paradigmxyz/revmc/blob/main/crates/revmc-context/src/lib.rs#L271

Thanks for the detailed issue! Would like to confirm that this happens on a clean build and with updated and equal versions for all packages, since the code is very sensitive about all of this.
I'd appreciate if you could either provide the bytecode and relevant inputs and environment to reproduce this, or, if not possible, see if you can bisect the commit where this segfault occurs, the range you gave is https://github.com/paradigmxyz/revmc/compare/cec178dcef3ce809c6d567dca9f8122464d5a53d...main.

Thanks for the detailed issue! Would like to confirm that this happens on a clean build (cargo clean) and with updated and equal versions for all packages, since the code is very sensitive about all of this.
I'd appreciate if you could either provide the bytecode and relevant inputs and environment to reproduce this, or, if not possible, see if you can bisect the commit where this segfault occurs, the range you gave is cec178d...main.

Can confirm that I did cargo clean as well as tested with debug and release profiles. About deps my alloy-primitives is 7.7 while revmc's is at 7.1.
Im gonna make a repro example repo ser, sounds good. Bisecting commit is also possible yh

@DaniPopes Heres a good repro that produces Segfault (well at least for me hehe).
https://github.com/0xDmtri/segfault-revmc-repro

Ok, wild fact.  But it doesnt on my AMD box... Metnal.
Probably this is caused by the same issue I have with Reth:
https://github.com/paradigmxyz/reth/issues/9611
But Reth works and doesn't crash without native cpu optimizations flag, but the repro crash with segfault even without any optimizations at all. Even in debug.
I think im going insane already, spent 2 weeks debugging all these thing.
Probably related to Revm optimizations? As its the common crate between Reth and Revmc. But then why would it work without opts for Reth but not for Revmc? I am even more confused now...

lscpu:
Architecture:             x86_64
  CPU op-mode(s):         32-bit, 64-bit
  Address sizes:          48 bits physical, 48 bits virtual
  Byte Order:             Little Endian
CPU(s):                   32
  On-line CPU(s) list:    0-31
Vendor ID:                AuthenticAMD
  BIOS Vendor ID:         Advanced Micro Devices, Inc.
  Model name:             AMD Ryzen 9 7950X3D 16-Core Processor
    BIOS Model name:      AMD Ryzen 9 7950X3D 16-Core Processor           Unknown CPU @ 4.2GHz
    BIOS CPU family:      107
    CPU family:           25
    Model:                97
    Thread(s) per core:   2
    Core(s) per socket:   16
    Socket(s):            1
    Stepping:             2
    Frequency boost:      enabled
    CPU(s) scaling MHz:   58%
    CPU max MHz:          5758.5928
    CPU min MHz:          3000.0000
    BogoMIPS:             8384.18
    Flags:                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good
                           amd_lbr_v2 nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm
                           cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_
                          l3 hw_pstate ssbd mba perfmon_v2 ibrs ibpb stibp ibrs_enhanced vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma
                          clflushopt clwb avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local avx512_bf16 clzero irperf xsaveerptr
                           rdpru wbnoinvd cppc arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif x2avic v_spec_ct
                          rl avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq rdpid overflow_recov succor smca fsrm flush_l1d amd_lbr_pmc_f
                          reeze
Virtualization features:
  Virtualization:         AMD-V
Caches (sum of all):
  L1d:                    512 KiB (16 instances)
  L1i:                    512 KiB (16 instances)
  L2:                     16 MiB (16 instances)
  L3:                     128 MiB (2 instances)
NUMA:
  NUMA node(s):           1
  NUMA node0 CPU(s):      0-31
Vulnerabilities:
  Gather data sampling:   Not affected
  Itlb multihit:          Not affected
  L1tf:                   Not affected
  Mds:                    Not affected
  Meltdown:               Not affected
  Mmio stale data:        Not affected
  Reg file data sampling: Not affected
  Retbleed:               Not affected
  Spec rstack overflow:   Mitigation; safe RET, no microcode
  Spec store bypass:      Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:             Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:             Mitigation; Enhanced / Automatic IBRS; IBPB conditional; STIBP always-on; RSB filling; PBRSB-eIBRS Not affected; BHI Not affected
  Srbds:                  Not affected
  Tsx async abort:        Not affected

I can reproduce, but only when optimizing the bytecode, and if I don't add printf at every instruction. Not sure what's going on, will investigate further

I can reproduce, but only when optimizing the bytecode, and if I don't add printf at every instruction. Not sure what's going on, will investigate further

Thats wicked mate haha, if you need any help def lmk, im here to assist!

Maybe an LLVM miscompilation, or some undefined behavior related to MSTORE builtin, because adding noinline fixes the segfault.

Maybe an LLVM miscompilation, or some undefined behavior related to MSTORE builtin, because adding noinline fixes the segfault.

Interesting. I wonder whats causing it in Reth

Don't know, it's unrelated, and a known issue.


vue-slide-bar not working inside a bootstrap modal

I have used vue-slide-bar 2 places in my project.  The one inside the bootstrap modal does not initialise unless i resize my screen. Here is my code for the vue-slide-bar.
`components: {
VueSlideBar
},
data() {
return {
sliderCustomzie: {
lineHeight: 1,
processStyle: {
backgroundColor: '#1FA0FB'
},
tooltipStyles: {
backgroundColor: '#1FA0FB',
borderColor: '#1FA0FB'
}
},
sliderWithLabel: {
data: [
1,
2,
8
],
range: [
{
label: 'Poor'
},
{
label: 'Fair',
isHide: true
},
{
label: 'Mint'
}
],
rangeValue: {}
},`
and the html in .vue file
<vue-slide-bar ref="slider" v-model="sliderWithLabel.value"                             :processStyle="sliderCustomzie.processStyle"                             :lineHeight="sliderCustomzie.lineHeight"                             :tooltipStyles="sliderCustomzie.tooltipStyles"                             :data="sliderWithLabel.data"                             :range="sliderWithLabel.range"                             @callbackRange="callbackRange">                     </vue-slide-bar>

@rajnvkr Please see solution in this issue #15 .

Thanks mate that helped me to fix my problem. Although I had to do a lot of modifications to my code but you helped me to go in the right direction. Cheers (y)


feat: support swiping to switch pages

Use hammer library to add support for swiping to switch to next/previous
page.
When menu is on the left, changing pages is done using swipe up/down
motion and when on the bottom, using swipe left/right motion.
With menu on the bottom, for page toggle animation to match swipe
direction, it was necessary to change how pages are layouted (needed to
be horizontally instead of vertically).
angular-long-press library was replaced with hammer as it supports the
same and was needed for swiping anyway.
Fixes #242

Thank you! Could you please also include .less with changes made to CSS?

Perfect!
P.S. I have also added you as a maintainer :)


[viu] New extractor for viu.com

Viu.com is a video streaming platform from Hong Kong listed PCCW offering content from Korea, Japan, Mainland China and Taiwan.
The service is currently geo-restricted to Hong Kong and Singapore.

Since #8497 landed, please move changes in youtube_dl/extractors/__init__.py to youtube_dl/extractors/extractors.py. Check step 5 of the new developer instructions for more information.

Replaced with #10607


Auto-sync CI status for each package

Currently, the failed packages are managed by hard-coded:
https://github.com/stylelint/stylelint-ecosystem-tester/blob/a64c4f9e0c5c09014c798d9a775dcbf5cc319ecd/scripts/update-readme.js#L10-L25
This way is not smart. We would like to automate updating the README file from CI results.

Could we use re-usable workflows and have 1 workflow per repo we want to test?
Then each would have its own status and status badge.

We can have helper scripts to (re)generate the workflow files and the badges in the readme.
So that it isn't that much effort when we want to add or remove projects.

That sounds great! 👍🏼
If someone is interested, feel free to open a pull request!


Switch implementation for core, cocoa and iOS(label not working on iOS)

@freakboy3742 I know we talked about not including the switch widget as a normal widget but only through the settings api. But on my settings-api-journey I found out that for macOS and iOS you have to (if you don't manage all the settings in the settings app what basically every normal app does) provide your own settings and therefor you need to be able to create your own switch widget.

macOS work
iOS switch has no label by default this is because it should only appear in a UITableViewCell with a label. I found some apps that use a switch with a label in a single UITableViewCell without a UITabelView wrapped around it and they say it is no problem. If I get your ok I would try to implement this into the iOS switch integration. The iOS switch functionality works already.

Here a little demo program if you would like to take it for a spin.
import time
import toga
from colosseum import CSS

def build(app):
    def callback(widget):
        label.text = 'Switch State: {}'.format(widget.state)

    def btn_callback(widget):
        switch.label = str('Update Label: {}'.format(time.time()))
        if switch.state:
            switch.state = False
        else:
            switch.state = True
        label.text = 'Switch State: {}'.format(switch.state)

    switch = toga.Switch('My Switch', on_press=callback)
    button = toga.Button('My Button', on_press=btn_callback, style=CSS(width=200))
    label = toga.Label('Switch State: {}'.format(switch.state))

    style = CSS(flex=1, padding=10)
    box = toga.Box(style=style)
    box.add(switch)
    box.add(button)
    box.add(label)
    return box

if __name__ == '__main__':
    app = toga.App('Test Switch', 'org.pybee.helloworld', startup=build)
    app.main_loop()

Signed-off-by: Jonas Schell<EMAIL_ADDRESS>

@freakboy3742 I did the changes and also added a label to the iOS implementation. It works quite nicely. Let me know what you think about is_on as the switch on/off state. Other than that it should be ready. Thank you for your feedback, I learn a lot from your input :)


New extension: Detect system type

Description
This extension allows you to detect the user's system type.
It features only 1 condition - Check the user's system.
You can use this extension if you want to add features only for certain system types.
How to use the extension
No response
Checklist

[X] I've followed all of the best practices.
[X] I confirm that this extension can be integrated to this GitHub repository, distributed and MIT licensed.
[X] I am aware that the extension may be updated by anyone, and do not need my explicit consent to do so.

What tier of review do you aim for your extension?
Community (Unreviewed)
Example file
https://gd.games/instant-builds/83ea88c4-9af1-4d9b-b8d0-7e17f8f11486
Extension file
SystemType.zip

Hello, @CommiePoland
If you want this extension to be seen, you should:

Add period in the end of extension's short description.
Follow X.Y.Z versioning, for example 1.0.1.
The example file should be a valid GDevelop project file, not a compiled preview link.
Hope you update your extension.

I am not a moderator.


ModuleNotFoundError: No module named 'finnews'

Trying to utilise the package but can't get it running. I'm using poetry as my package manager and have added to my pyproject.toml file:
[tool.poetry.dependencies]
python = "^3.8"
Flask = "^2.0.1"
fin-news = "^0.1.1"

However when I then try and import finnews:
from finnews.client import News
It throws error.
Any ideas why this could be?

same problem


Load mtl file manually from firebase

OS: Windows
Version: ViroCore version
Device(s): samsung a5

Description
I have uploaded the mtl file and obj file separately to firebase database. When I loaded the 3d obj model, it cannot read mtl file. May i know is there any way to load mtl file to 3d obj model programmatically?

Hi @HLneoh ,
Thanks for reaching out. From our Object3D,

To load an OBJ with an associated MTL file, the MTL file and all of its associated textures must placed in the same directory as the OBJ file. They will then be automatically retrieved and applied.
Currently there is no way to manually load the mtl file to the 3d obj model. But you can manually set the material textures, colors, etc. Example here -> https://virocore.viromedia.com/v1.11.0/docs/3d-scene-lighting#materials .
If manually constructing the materials object is too cumbersome, I'd recommend trying to pre-download the mtl & obj files from firebase to local media in the same directory, before trying to render the 3d object on to the scene.


App immediately crashes when joining call (targeting android API version 31)

Expected behavior
No crash / exception.
Describe the bug (unexpected behavior)
Unable to start service com.daily.reactlibrary.DailyOngoingMeetingForegroundService@c6d9368 with Intent { cmp=_____/com.daily.reactlibrary.DailyOngoingMeetingForegroundService (has extras) }: java.lang.IllegalArgumentException: ______: Targeting S+ (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE be specified when creating a PendingIntent.
Strongly consider using FLAG_IMMUTABLE, only use FLAG_MUTABLE if some functionality depends on the PendingIntent being mutable, e.g. if it needs to be used with inline replies or bubbles.

Steps to reproduce

Set react native project to target android API version 31
Run on a physical device running android 12
Try to join a daily call
Immediately crashes

System information

Device: Samsung S10, Pixel 5a
OS, version: Android 12

Hi @raymondpebble
This issue has been fixed on our latest version of react-native-daiy-js, 0.24.0.
We have added support for Android 12. You can see the release notes here: https://github.com/daily-co/react-native-daily-js/releases

Hi @filipi87
I am still having the same issue on Android 12. The app crashes once call join method is invoked in Android. I have attached the snippet of the terminal as the error message keeps repeating after join method.

Hi @vineetk242000 ,
This looks like a completely different issue. Could you open a ticket so we can investigate that, would be nice to also add more information about your environment, like which version of react-native-daily-js you are using.
At first glance, looking at the error about, I found It curious about the error, because we have two possible listeners:

joining-meeting
joined-meeting

And the error says just join-meeting.
If you are trying to use some listeners, please also add on the ticket so I can try to reproduce it here.
Thanks a lot for your report.


docs: init custom plugin docs

This PR is about custom plugin docs. It contains a couple of simply written example plugins as well as some docs.
included:

a section on custom plugins
filesize plugin
lighthouse plugin
dummy config to execute the plugins
include the plugins in the repo code-pushup.config.ts

I started to implement 2 simple plugins and try to get a standard for the plugin file.
ATM a plugin file maintains:

create - function that returns the PluginConfig
pluginSlug - slug of the plugin
recommendedRefs - to configure CategoryConfig


[Docs]: .tocontainequalitem() explanation is ambiguous

Page(s)
https://github.com/jestjs/jest/blob/main/docs/ExpectAPI.md#tocontainequalitem
Description
I find this explanation is very ambiguous.

Use .toContainEqual when you want to check that an item with a specific structure and values is contained in an array. For testing the items in the array, this matcher recursively checks the equality of all fields, rather than checking for object identity.

describe('my beverage', () => {
  test('is delicious and not sour', () => {
    const myBeverage = {delicious: true, sour: false};
    expect(myBeverages()).toContainEqual(myBeverage);
  });
});

I have the following questions:
What does the myBeverages() return? An array, I think.
So does the expect argument HAVE TO BE an array? I think so.
Does myBeverage have to be an object literal? Could it be an array inside an array? Not sure.
Does myBeverage match to things which have more fields than the specified fields? Not sure.
function myBeverages() {
  return [
    {
        delicious: true,
        sour: false,
        salty: false
    },
    {
        delicious: true,
        sour: true,
        salty: true
    }
  ]
}

const const myBeverage = {
  delicious: true,
  sour: false
}

expect(myBeverages()).toContainEqual(myBeverage) // True? Possibly?

What does the myBeverages() return? An array, I think.
So does the expect argument HAVE TO BE an array? I think so.
Does myBeverage have to be an object literal? Could it be an array inside an array? Not sure.

Does myBeverage match to things which have more fields than the specified fields? Not sure
No it does not. It has to be exactly the same key: value pairs.


[BugFix] ensure a valid cast clause for MySQL/JDBC table

What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes:

Fixes #23434
Problem Summary(Required):

The root casue is when translate scalarOperator to expr, the implicit flag is not being set correctly.  Only when the scanNode is JDBC/MySQL scanNode, the formatterContext.implicitCast is true.
public Expr visitCastOperator(CastOperator operator, FormatterContext context) {
            CastExpr expr =
                    new CastExpr(operator.getType(), buildExpr.build(operator.getChild(0), context));
            expr.setImplicit(context.implicitCast);
            hackTypeNull(expr);
            return expr;
        }

To ensure these unnecessary implicit cast not being pushed to MySQL/JDBC scanNode, we remove these implicit cast in PushDownPredicateToExternalTableScanRule. Only valid cast caluse in both in SR and MySQL can be pushed then only implicit cast will be removed for MySQL table.
# col_1 is a varchar, col_2 is a varchar, col_3 is a int
select * from table where col_1 and cast(col_2 as date) and cast(col_3 as string);

# in SR
select * from table where cast(col_1 as boolean) and cast(col_2 as date) and cast(col_3 as string);

# in MySQL the scan will be
select * from table where col_1 and cast(col_2 as date) -- the cast(col_3 as string) will do in the SR because MySQL don't support cast as string.

Changes in Load.java
When use VectorizedLoad, we need analyzeMappingExprs which will replace the origin slotRef to a new slotRef without description and it may lead NPE inslotRef.getColumn() . So use slotRef.getColumnName() instead of slotRef.getColumn().getName();
public static Expr analyzeAndCastFold(Expr expr) {
        ExpressionAnalyzer.analyzeExpressionIgnoreSlot(expr, ConnectContext.get());
        // Translating expr to scalar in order to do some rewrites
        try {
            ScalarOperator scalarOperator = SqlToScalarOperatorTranslator.translate(expr);
            ScalarOperatorRewriter scalarRewriter = new ScalarOperatorRewriter();
            // Add cast and constant fold
            scalarOperator = scalarRewriter.rewrite(scalarOperator, ScalarOperatorRewriter.DEFAULT_REWRITE_RULES);
            return ScalarOperatorToExpr.buildExprIgnoreSlot(scalarOperator,
                    new ScalarOperatorToExpr.FormatterContext(Maps.newHashMap()));
        } catch (UnsupportedException e) {
            return expr;
        }
    }

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

[FE PR Coverage Check]
:heart_eyes: pass : 28 / 34 (82.35%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/analysis/SlotRef.java
6
11
54.55%
[292, 312, 319, 320, 322]

:large_blue_circle:
com/starrocks/sql/optimizer/rewrite/ExternalTablePredicateExtractor.java
16
17
94.12%
[91]

:large_blue_circle:
com/starrocks/sql/optimizer/rule/transformation/PushDownPredicateToExternalTableScanRule.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/load/Load.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/plan/ScalarOperatorToExpr.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/CastExpr.java
2
2
100.00%
[]

LGTM

@Mergifyio backport branch-3.0


Add missing solution to problem 8

Problem 8 requests to find the digits as well as the product. I added the 13 digits

Hi! For consistency, we only collect the final answer (that you submit into the box).


Review and set guidelines for use of contact component

The contact component can be positioned at any arbitrary spot on a content page, but this can lead to inconsistency. By including multiple contacts on a page, it further muddles the page purpose, and is likely to cause confusion by too much choice.
We need to:

establish whether contact is fit for purpose in its current configuration
write up guidelines that describe when and when not to use the component.

https://cardigan.wellcomecollection.org/?path=/story/components--contact

26 January 2021

contact block should always be at the bottom of the page (as it's secondary information)

26 January 2021

contact block should always be at the bottom of the page (as it's secondary information)

Agreed guidelines https://www.notion.so/wellcometrust/Content-design-guidelines-in-progress-de0681bbd1804d2c89d128ab2f3a64b2#3bc1ef8f9abd4a57821af29ded01653b
Contact slice
Cardigan component Contact https://cardigan.wellcomecollection.org/?path=/story/components--contact
When to use the contact slice:

Use only once per page when there is a primary contact (team, individual) that supports the service you're describing on the page.
The contact shouldn't need to be repeated throughout the text. As long as it's apparent who is the main contact
Place at bottom of text for consistency across site (NB this is currently editor's control; not baked into page template)

When not to use the contact slice:

When it would be better for readability to mention an email or contact in line with text
When there's already one on the page.

Agreed guidelines https://www.notion.so/wellcometrust/Content-design-guidelines-in-progress-de0681bbd1804d2c89d128ab2f3a64b2#3bc1ef8f9abd4a57821af29ded01653b
Contact slice
Cardigan component Contact https://cardigan.wellcomecollection.org/?path=/story/components--contact
When to use the contact slice:

Use only once per page when there is a primary contact (team, individual) that supports the service you're describing on the page.
The contact shouldn't need to be repeated throughout the text. As long as it's apparent who is the main contact
Place at bottom of text for consistency across site (NB this is currently editor's control; not baked into page template)

When not to use the contact slice:

When it would be better for readability to mention an email or contact in line with text
When there's already one on the page.


Error parsing attribute "@default": The function auto is not a known function.

Hi there, trying to follow along with the quickstart guide. When trying to generate, I get the following error using auto() for attribute @default. I switched over to uuid() and it works now, but thought this error was weird and worth looking into.
I'm using next.js v12 with Typescript on node v16
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Error: Schema parsing
error: Error parsing attribute "@default": The function `auto` is not a known function. You can read about the available functions here: https://pris.ly/d/attribute-functions.
  -->  schema.prisma:12
   |
11 | model Project {
12 |   id       String    @id @default(auto()) @map("_id") @db.ObjectId
   |
error: Error parsing attribute "@default": The function `auto` is not a known function. You can read about the available functions here: https://pris.ly/d/attribute-functions.
  -->  schema.prisma:24
   |
23 | model Bug {
24 |   id          String    @id @default(auto()) @map("_id") @db.ObjectId
   |
error: Error parsing attribute "@default": The function `auto` is not a known function. You can read about the available functions here: https://pris.ly/d/attribute-functions.
  -->  schema.prisma:32
   |
31 | model User {
32 |   id       String    @id @default(auto()) @map("_id") @db.ObjectId
   |

Validation Error Count: 3

schema.prisma
datasource db {
  provider = "mongodb"
  url      = env("DATABASE_URL")
}

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["mongoDb"]
}

model Project {
  id       String    @id @default(auto()) @map("_id") @db.ObjectId
  slug     String    @unique
  title    String
  body     String
  bugs     Bug[]
  user     User      @relation(fields: [userId], references: [id])
  userId   String    @db.ObjectId
}

// Comments contain a comment string and connect back to the post.
// postId must have @db.ObjectId to match up with Post's id type
model Bug {
  id          String    @id @default(auto()) @map("_id") @db.ObjectId
  project     Project   @relation(fields: [projectId], references: [id])
  projectId   String    @db.ObjectId
  description String
  priority    String
}

model User {
  id       String    @id @default(auto()) @map("_id") @db.ObjectId
  email    String    @unique
  name     String?
  projects Project[]
}

Try dbgenerated() in place of auto() - this seems to be a future change that has not actually been released yet that somehow made it into the docs.

This is now fixed in our docs again. Thanks for reporting.
Please let me know if using the suggested syntax fixes the problem for you.

It did. Thank you!

Sorry for replying to this but, I'm starting to have this issue.

After using auto() I get the same error this thread is titled as.

Moved your issue to https://github.com/prisma/prisma/issues/11985 @ThatBlueDevil

I'm getting this error now, I thought it was solved. But literally whenever I change it to uuid() works. here is error:
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db"
Error: P1012

error: Error parsing attribute "@default": The function `auto` is not a known function. You can read about the available functions here: https://pris.ly/d/attribute-functions.
  -->  schema.prisma:14
   |
13 | model Url {
14 |   id          String   @id @default(auto()) @map("_id") @db.ObjectId
   |

What version are you using @iamshabell? That looks like an older one.

it worked, I was using an older version. Thank You


Add method to connect using existing channel

Add a connect method that allows using an existing Channel for the connection.
This makes it possible to for example create an SSH tunnel and establish a Postgres connection on the SSH Channel.

Codecov Report

Merging #314 (ca932a0) into main (f636f59) will decrease coverage by 0.11%.
The diff coverage is 0.00%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #314      +/-   ##
==========================================
- Coverage   43.52%   43.41%   -0.12%
==========================================
  Files         115      115
  Lines        9763     9788      +25
==========================================
  Hits         4249     4249
- Misses       5514     5539      +25

Flag
Coverage Δ

unittests
43.41% <0.00%> (-0.12%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...es/PostgresNIO/Connection/PostgresConnection.swift
16.25% <0.00%> (-0.90%)
:arrow_down:

Superseeded by https://github.com/vapor/postgres-nio/pull/335.


Rigorous testing for appointment editor funtions.

Is your feature request related to a problem? Please describe.
The appointment editor is both the most important part of the app and the most likely to have bugs, due to its complexity and heavy reliance on firebase. As such, it needs rigorous testing.
Describe the solution you'd like
Write rigorous testing to test as many intended features and possible edge cases as possible to ensure the appointment editor works as intended.

Appointment editor is tested


Should TemporalRelation be a modeling pattern rather than a class?

@DanCarey404 raised the question of whether gist:TemporalRelation should be a modeling pattern instead of a class. We came to this conclusion in discussing a possible superclass ComplexRelation; see #424.

@DanCarey404 @rjyounes
After a careful read of #424, I don't see there is anything more to consider.
I recommend we close this issue.

Agreed - closing.


re-enable perf

I get a test suite failure:
> /tmp/stackage-build14/perf-0.2.0$ ghc -clear-package-db -global-package-db -package-db=/var/stackage/work/builds/nightly/pkgdb Setup
> /tmp/stackage-build14/perf-0.2.0$ ./Setup configure --enable-tests --package-db=clear --package-db=global --package-db=/var/stackage/work/builds/nightly/pkgdb --libdir=/var/stackage/work/builds/nightly/lib --bindir=/var/stackage/work/builds/nightly/bin --datadir=/var/stackage/work/builds/nightly/share --libexecdir=/var/stackage/work/builds/nightly/libexec --sysconfdir=/var/stackage/work/builds/nightly/etc --docdir=/var/stackage/work/builds/nightly/doc/perf-0.2.0 --htmldir=/var/stackage/work/builds/nightly/doc/perf-0.2.0 --haddockdir=/var/stackage/work/builds/nightly/doc/perf-0.2.0 --flags=
Configuring perf-0.2.0...
> /tmp/stackage-build14/perf-0.2.0$ ghc -clear-package-db -global-package-db -package-db=/var/stackage/work/builds/nightly/pkgdb Setup
> /tmp/stackage-build14/perf-0.2.0$ ./Setup build
Preprocessing library for perf-0.2.0..
Building library for perf-0.2.0..
[1 of 3] Compiling Perf.Cycle       ( src/Perf/Cycle.hs, dist/build/Perf/Cycle.o )
[2 of 3] Compiling Perf.Measure     ( src/Perf/Measure.hs, dist/build/Perf/Measure.o )
[3 of 3] Compiling Perf             ( src/Perf.hs, dist/build/Perf.o )
Preprocessing test suite 'test' for perf-0.2.0..
Building test suite 'test' for perf-0.2.0..
[1 of 1] Compiling Main             ( test/test.hs, dist/build/test/test-tmp/Main.o )
Linking dist/build/test/test ...
Preprocessing executable 'perf-examples' for perf-0.2.0..
Building executable 'perf-examples' for perf-0.2.0..
[1 of 1] Compiling Main             ( examples/examples.hs, dist/build/perf-examples/perf-examples-tmp/Main.o )
[1 of 1] Compiling Main             ( examples/examples.hs, dist/build/perf-examples/perf-examples-tmp/Main.o )
Linking dist/build/perf-examples/perf-examples ...
> /tmp/stackage-build14/perf-0.2.0$ dist/build/test/test

src/Perf/Cycle.hs:38:1: error:
    Could not find module ‘Protolude’
    Use -v to see a list of the files searched for.
   |
38 | import qualified Protolude
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^
Perf.Cycle DocTest


fixing new 454 issue

This solves an issue when you have 3 sff files, where 2 are from the same run (prefix aaa) and the 3rd one has a different prefix (prefix bbb). This is aaa1.sff, aaa2.sff, bbb.sff. In this case we need to split at the same time aaa1-2 and then bbb.
Note that this is blocking some analysis so quick reviews are greatly appreciated. @biocore/qiita-dev

Mostly minor comments, but I think there is a potential bug with the branching logic that needs to be resolved

Also, odd build failure?
numpy.distutils.system_info.NotFoundError: no lapack/blas resources found

#1011 should take care of this failure.
On (Mar-20-15|14:47), Daniel McDonald wrote:

Also, odd build failure?
numpy.distutils.system_info.NotFoundError: no lapack/blas resources found

Reply to this email directly or view it on GitHub:
https://github.com/biocore/qiita/pull/1008#issuecomment-84161846

Can you remove the travis-cleanup branch from this PR? I think we can merge travis-cleanup much faster than we can merge this and others.

Code looks fine but I need to test this in my system.

I set up the following case three sequence files five1.sff, five2.sff and four.sff. The run prefix column has two different values four and five. When I tried to process the data I got the following error:
ValueError('Your run prefixes in your prep template "/tmp/MMF_120GKWhmU/five_MMF.txt, /tmp/MMF_120GKWhmU/four_MMF.txt" do not match your file names "/Users/yoshikivazquezbaeza/git_sw/qiita/qiita_db/support_files/test_data/raw_data/116_five1.sff, /Users/yoshikivazquezbaeza/git_sw/qiita/qiita_db/support_files/test_data/raw_data/116_five2.sff, /Users/yoshikivazquezbaeza/git_sw/qiita/qiita_db/support_files/test_data/raw_data/116_four.sff"',), <traceback object at 0x10b13d170>)

If I'm correct, this is exactly the case you were targeting with this PR, otherwise am I missing something completely obvious?

Agree that merging your branch first is a good idea but I wanted to
have the tests passing on this one ...

Thank you for catching this!!! This is one of those situations where
the test data doesn't follow the patterns on the real one. Fixing now.

Thanks this is working now! :+1:

Coverage increased (+0.07%) to 78.93% when pulling a7d3f8b06ac331889011bb39ad0db4690492941e on antgonza:454-issue into e937609cb72f65e59fc488091f2efe09fe9ed412 on biocore:master.

Changes Unknown when pulling 954cf15a16aa62e044d06cef619577017cbb9049 on antgonza:454-issue into ** on biocore:master**.


Add Open Graph Data To Events

At the same time, rich result information may as well be considered: https://developers.google.com/search/docs/appearance/structured-data/event

At the same time, rich result information may as well be considered:
* Google: https://developers.google.com/search/docs/appearance/structured-data/event

* Bing: https://www.bing.com/webmasters/help/?topicid=0f23328d

Brilliant suggestion, would go in a separate issue though. Can still be part of the same pr though.


[tests-only][full-ci]Bump latest ocis commit id

Part of https://github.com/owncloud/QA/issues/867

I'm sorry. I pressed the wrong button.

@nirajacharya2 @PrajwolAmatya note that there is also PR #4938 - I guess that can be closed.

Upload steps are flaky in posixfs pipelines
Failed step: And user "Alice" has uploaded file with content "file to delete" to "/textfile0.txt"
        HTTP status code was not 201 or 204 while trying to upload file '/textfile0.txt' for user 'Alice'
        Failed asserting that an array contains 404.

CC @aduffeck

Waiting for PR https://github.com/owncloud/ocis/pull/10622

Ready to be merged


Creating a production tool for scaling crop-mask predictions

In order for users to move efficiently from testing crop mask models within a notebook environment, into scaling classifications to entire Agro-Ecological Zones (AEZ), we need to build a suite of relatively easy-to-use scaling tools.
The final product should have a number of features:

Be relatively straight-forward to use:
-  Require no interaction with source code
-  A small number of user inputs (feature layer function, model path, tile-geojson, file export name)
-  Interaction with the tool should occur within a familiar environment e.g. command line, or a jupyter notebook
The code should export Cloud-Optimized Geotiffs in a manner that allows for indexing into the Open Data Cube. i.e. it should follow the correct file path and naming conventions, and contain the correct STAC metadata (I assume this part will not generalize beyond the crop-mask, but that's okay).
Excellent documentation, with examples, is an important feature
While the first iteration of this tool will likely serially loop through a set of polygon tile boundaries in the input geojson, the code should be written in a way that ensures easy translation into an AWS SQS system that can run tiles in parallel across multiple instances (this will be necessary for classifying large AEZs in a reasonable amount of time).
While this tool is mostly specific to the crop-mask, if we can build them as modular and as generic as possible then they could prove useful for other product development projects.

@fivejjs Something I didn't consider above.  Post-process masking (like we do with WOfS and elevation in the Eastern crop-mask) could be difficult to incorporate....Perhaps an optional post-process function as a user input could be one option?

working on that after the current branch?

resolved for current stage. I will open new one wit the new semiannual data access approach.


Accessory state not updated after restart

@oznu
After restart Homebridge Config UI X (all Versions) dummy accessory are not updated but if U go to logs and again to accessory then updated all.
Look on rollershutter and thermostats.
Here the video:
https://vimeo.com/383703844

While the states of the accessories are not being shown, can you use the UI to control an accessory and let me know if this triggered all the other accessories to correctly reflect their states?

Yes I can control all accessory normal, the correct state is show after going to logs window and again to accessory or if the accessory change its state itself. This happened only on dummy rollershutter or thermostat. T think restart Config UI X clear the state and not refresh again.

Try the latest @test v4.7.0-test.31. I've done a small change that I think might fix this.

Thanks, now working as excepted.


Allow date pickers to not have selected date

This enables our various date picker classes to have a null initialDate.
It also fixes the logic of some of the widgets which used to do something when you changed the initial* parameters, which is wrong for initial* properties (they by definition should only impact the initial state) and wrong for properties in general (behaviour should not change based on whether the widget was built with a new value or not, that violates the reactive design principles).
Fixes https://github.com/flutter/flutter/issues/638.

Doesn't DatePicker.initialEntryMode also need to be updated?

As far as I can tell it's already doing the right thing. If you mean the documentation, then I did try to update it but I wasn't really sure what it should say. I don't want to recommend resetting the key just to change the mode because that'll reset everything else as well which seems rather disruptive (compared to when changing the selected date, where you kind of want to be resetting everything? I think?).

I updated the branch and will mark it to land on green but feel free to remove the autosubmit label if you have a particular thing you'd like me to change for initialEntryMode.

The initialEntryMode parameter seemed like it needed a /// Subsequently changing this has no effect ... comment just for the sake of symmetry.  I agree that resetting this parameter with a new key is likely to lead to more confusion; I'm fine with leaving things as they are here.


MM-22818 - Removing status icon from channel

Summary
MM-22818 - Removing status icon from channel
Ticket Link
https://mattermost.atlassian.net/browse/MM-22818
Screenshots

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-5030.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

Hi @asaadmahmood @adamjclarkson
I've tested on the spinwick and the status icon is removed in the center channel.
However, the status icon still remains on reply posts in the right-hand-side which looks weird to me.
I also noticed your comment on the ticket Adam:

It also pushes the firstname initial letter off to the left when user has a default avatar.

Even although the status icon is removed, this doesn't fix the first-name initial letter being off to the left when a user has a default avatar. In my opinion, the default avatar looks very strange now.

@lindy65 I can update the ticket, but the letter in the avatar is not positioned to the left because of the status icon, that is a separate thing.
I have removed it from the RHS thread view now as well.

New commit detected. SpinWick will upgrade if the updated docker image is available.

Mattermost test server updated with git commit 2f103115dd7c3a786ca7bc94ac2717c618dff035.
Access here: https://mattermost-webapp-pr-5030.test.mattermost.cloud

I've assigned @esethna to the PR. @esethna the letters on the left are a bit separate from the emojis, and maybe coming from elsewhere. We can tackle that in another PR.

Thanks @asaadmahmood - I've re-tested and see the status is removed from the user avatar in the right-hand-side now too.
I realise that the letter on a default user avatar is over to the left whether or not the status icon is present. The reason I drew attention to this in my comment above is because Adam had mentioned on the Jira ticket that it was because of the status icon on the avatar that the letter was over to the left - which isn't the case.

Discussed with UX team, propose we only do this only for DMs as a test (already have the online status in the channel header), and allow it to soak for feedback on daily for a release cycle

@sudheerDev @saturninoabril Eric requested we remove the status icon from the DMs only, so please rereview the PR.

New commit detected. SpinWick will upgrade if the updated docker image is available.

New commit detected. SpinWick will upgrade if the updated docker image is available.

New commit detected. SpinWick will upgrade if the updated docker image is available.

Test server creation failed. See the logs for more information.

Test server creation failed. See the logs for more information.

Mattermost test server updated with git commit 3356b3d6607090fbb9648fb58d9395b445edce61.
Access here: https://mattermost-webapp-pr-5030.test.mattermost.cloud

New commit detected. SpinWick will upgrade if the updated docker image is available.

New commit detected. SpinWick will upgrade if the updated docker image is available.

Test server creation failed. See the logs for more information.

Mattermost test server updated with git commit c8aa48f4b0a4b0dcf64a65afbe864e5e9667651c.
Access here: https://mattermost-webapp-pr-5030.test.mattermost.cloud

@asaadmahmood, thinking about this more, doing it only in DMs creates an inconsistency that people may find frustrating. I think something like this should probably require a setting as SA suggests - that would apply to all channels. Propose we close this ticket for now

@esethna Cool.

Test server destroyed


ERROR: _warn() takes 2 positional arguments but 5 were given

What is the purpose of your issue?

[x] Bug
[ ] Feature Request
[ ] Question
[ ] Other

Description
Hi, I'm back! Well, I was trying to download my Spotify playlist (https://open.spotify.com/user/1qlzuykudenvmxvdggdwf1rcm/playlist/2My0t4jTZI0LefLq8hJeqx?si=t3sJHKGxTzeQ97Px3Dzlnw) by using the command "spotdl -l lollol.txt (before I did spotdl -p "playlist link") --overwrite skip" and first of all it doesn't skip the already downloaded songs but it downloads them again and after around the 160th song it gets the error in the Log section and it continues over... and over... and it will never stop again until I press CTRL+C.
Please answer this issue and bye.
I'm happy to be here again!
TheLifeGamingYT
Log
ERROR: _warn() takes 2 positional arguments but 5 were given
Traceback (most recent call last):
File "d:\programmi\python 3\lib\site-packages\spotdl\spotdl.py", line 95, in download_list
download_single(raw_song, number=number)
File "d:\programmi\python 3\lib\site-packages\spotdl\spotdl.py", line 130, in download_single
content, meta_tags = youtube_tools.match_video_and_metadata(raw_song)
File "d:\programmi\python 3\lib\site-packages\spotdl\youtube_tools.py", line 55, in match_video_and_metadata
meta_tags = spotify_tools.generate_metadata(track)
File "d:\programmi\python 3\lib\site-packages\spotdl\spotify_tools.py", line 41, in generate_metadata
meta_tags = spotify.track(raw_song)
File "d:\programmi\python 3\lib\site-packages\spotipy\client.py", line 222, in track
trid = self._get_id('track', track_id)
File "d:\programmi\python 3\lib\site-packages\spotipy\client.py", line 850, in _get_id
type, fields[-2], id)
TypeError: _warn() takes 2 positional arguments but 5 were given
WARNING: Failed to download song. Will retry after other songs

first of all it doesn't skip the already downloaded songs but it downloads them again

Do you mean it overwrites the already download song or does it download a different version of the same song?


Remove unnecessary information dialog, throw error when we cannot find swift

@swift-server-bot test this please


How can we insert tuples into a relational database?

I found most of the topics are about reading from some sources. But how to write the results to DB?

Writing tuples to databases in storm would be a side-effect of a bolt in your topology.
You'd have your spout reading data, sending it some number of bolt, and one of those bolts would do the correct INSERT or UPDATE statements, depending on your database schema. Storm provides "at least once" guarantee of tuples, which means that your database writes should be prepared for sometimes attempting to re-save a tuple that had already been processed.
The idea is similar to the RedisWordCountBolt in the examples https://github.com/Parsely/streamparse/blob/master/examples/redis/src/bolts.py
Does that answer your question?


Merge down from main to dev

Merge down from main to dev
Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Not able to merge down for some conflicts at this moment.  Close the PR.


Add option to download articles

As member you can download articles as epub, mobi, mp3 ...

See #4 which it this is depened on.


Segmentation Fault

Running on Debian 8.6 64-bit. MySQL user/db/privs all correct. Turns out the issue is you provide no empty 'data' dir in your skeleton, while your main.cpp sets the download_dir to ./data/. Might want to create an empty data dir in the repo or at least mention it in the README.
# Database credentials
DB_HOST     = tcp://<IP_ADDRESS>
DB_PORT     = 3306
DB_USER     = redacted
DB_PASS     = redacted
DB_NAME     = POE
DB_DATA_DIR = /var/lib/mysql

Segfaults in /var/log/messages:
Jan  5 13:24:10 REDACTED kernel: [  950.516414] indexer[13408]: segfault at 0 ip 00007f2e107ad9e0 sp 00007f2e067fb230 error 4 in libc-2.19.so[7f2e10743000+1a1000]
Jan  5 13:26:27 REDACTED kernel: [ 1088.254572] indexer[13813]: segfault at 0 ip 00007faec44209e0 sp 00007faeba5ef230 error 4 in libc-2.19.so[7faec43b6000+1a1000]
Jan  5 13:30:48 REDACTED kernel: [ 1348.780972] indexer[13903]: segfault at 0 ip 00007fca2f19a9e0 sp 00007fca293ef230 error 4 in libc-2.19.so[7fca2f130000+1a1000]

Backtrace from gdb, this is how I found out it had to do with a problem writing a file:
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./indexer...done.
(gdb) run
Starting program: /root/POE-Stash-indexer-NG/indexer
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff2f44700 (LWP 13823)]
[Thread 0x7ffff2f44700 (LWP 13823) exited]
2017-01-05 13:26:38 > [main] Connected to DB in 0.036458 sec
2017-01-05 13:26:38 > [main] Checking last downloaded chunk
2017-01-05 13:26:38 > [main] New indexation:
[New Thread 0x7ffff2f44700 (LWP 13824)]
2017-01-05 13:26:38 > [mod_loop] Waiting for mods to insert
[New Thread 0x7ffff2537700 (LWP 13825)]
2017-01-05 13:26:38 > [requirement_loop] Waiting for requirements to insert
[New Thread 0x7ffff1d36700 (LWP 13826)]
2017-01-05 13:26:38 > [property_loop] Waiting for property to insert
[New Thread 0x7ffff1535700 (LWP 13827)]
2017-01-05 13:26:38 > [socket_loop] Waiting for socket to insert
[New Thread 0x7ffff0d34700 (LWP 13828)]
[New Thread 0x7fffe3fff700 (LWP 13829)]
[New Thread 0x7fffe37fe700 (LWP 13830)]
2017-01-05 13:26:38 > [processing_loop] Waiting for files to process
[Thread 0x7fffe37fe700 (LWP 13830) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff0d34700 (LWP 13828)]
__GI__IO_fwrite (buf=0x7fffd8015a40, size=1, count=1694, fp=0x0) at iofwrite.c:41
41      iofwrite.c: No such file or directory.
(gdb) bt
#0  __GI__IO_fwrite (buf=0x7fffd8015a40, size=1, count=1694, fp=0x0) at iofwrite.c:41
#1  0x00007ffff79673c8 in ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
#2  0x00007ffff79876cc in ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
#3  0x00007ffff7987a02 in ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
#4  0x00007ffff7981ad3 in ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
#5  0x00007ffff797c3df in ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
#6  0x00007ffff7986749 in ?? () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
#7  0x00007ffff7986f91 in curl_multi_perform () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
#8  0x00007ffff797ddeb in curl_easy_perform () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4
#9  0x000000000041b5de in download_JSON(std::string) ()
#10 0x0000000000423c98 in download_loop() ()
#11 0x00007ffff73ec970 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00007ffff7bc70a4 in start_thread (arg=0x7ffff0d34700) at pthread_create.c:309
#13 0x00007ffff6b5c62d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
(gdb) quit
A debugging session is active.

        Inferior 1 [process 13819] will be killed.

Quit anyway? (y or n) Y```

Thanks for the heads-up. It should be fixed in the last patch ;)


arch-arm: Fix KVM Failed to set register (0x603000000013808c)

Some debug registers were incorrectly tagged
(e.g. as being writeable). This was causing a bug in some gem5-KVM runs where gem5 was trying to initialize the state of those registers (OSLSR_EL1) [1] but KVM was returning an error (as the registers were RO).
[1]: https://github.com/gem5/gem5/blob/stable/
src/arch/arm/kvm/armv8_cpu.cc#L408
Change-Id: Iaa8d94e0e4b6fa34c39b30f0f12fcd7fe8a8da4d

Mmmm.. It seems like there is some checkpoint restore riscv test failing

We updated that checkpoint this morning. You need to rebase to include this change so the tests pass: https://github.com/gem5/gem5/commit/73c48a482831ac87b176751dd713d02d378ea7be


two-step verification

app doesn't seem to work if 2-step verification is active since there is no prompt to insert code

confirm, the app doesnot access the 2-step verification request.

There is already an issue about
here is the link: https://github.com/ifedapoolarewaju/igdm/issues/30

closing this as duplicate


npm run test fails when run from both win10 and wsl

Environment data

VS Code version: 1.43.2
Extension version (available under the Extensions sidebar): 2020.4.0-dev
OS and version: Windows 10 - 1903
Python version (& distribution if applicable, e.g. Anaconda): 3.8 but not relevant
Type of virtual environment used (N/A | venv | virtualenv | conda | ...):
Relevant/affected Python packages and their versions:
Relevant/affected Python-related VS Code extensions and their versions:
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977):
Value of the python.languageServer setting:

Expected behaviour
npm run test
successfully runs when the command is issued in win10.
When the command is rerun in WSL, the script only checks for the presence of ./.vscode-test/vscode-[ver].
However, the installer places the downloaded copy for windows and the copy needed for WSL in different locations. So it skips installing the extra version it needs, and subsequently crashes.
This is also happens in reverse (I.E. wsl successfully runs and then the command is run from win10)
Actual behaviour
root @ win10 .../projects/all_msft/vscode-python 19:22 0
@In [2] $ npm run test

><EMAIL_ADDRESS>test /mnt/c/Users/fac/projects/all_msft/vscode-python
> node ./out/test/standardTest.js && node ./out/test/multiRootTest.js

****************************************************************************************************
Start Standard tests
Found .vscode-test/vscode-1.43.2. Skipping download.
Test error: Error: spawn /mnt/c/Users/fac/projects/all_msft/vscode-python/.vscode-test/vscode-1.43.2/VSCode-linux-x64/code ENOENT
Exit code:   -2
Done

End Standard tests (with errors) Failed
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test: `node ./out/test/standardTest.js && node ./out/test/multiRootTest.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-03-26T23_22_08_810Z-debug.log

Sorry if anything here is unclear at all. I'd be happy to elaborate if so.

@farisachugthai, thanks for getting in touch with us.  If I understand correctly, you are trying to use the same clone of the repo from Windows and WSL.  Is that right?
If so, I would expect that to not work in exactly the way you have described.  FWIW, no effort has ever been made to set up the repo for that sort of cross-platform development.  I don't think anyone has ever even considered it. :smile:  However, that isn't to say it's a bad idea.  Furthermore, there are probably very few blockers to making it work.
Regardless, what is the advantage to sharing the same clone on the two platforms?  Having a separate clone on each will work fine.  If there's an advantage to sharing the clone in some situations then we would definitely be interested in at least understanding what it would take to make it work.

Hahaha yes that is absolutely correct. To be frank with you I hadn't actually considered simply cloning the repo again.
Insofar I've successfully built the repo by simply deleting the installation of VSCode in vscode-test, so I think you guys are most of the way there.
Admittedly I wouldn't be able to give you a definitive advantage as to why to use the same clone on the 2 platforms though. I simply hadn't realized that this behavior moved things into "Hadn't considered before." hahaha.
I definitely agree that there are few blockers to making it work however.

@farisachugthai, thanks for the update.  I'm going to mark this issue as an enhancement request and we'll make a decision in the near future on whether to proceed with it.  Thanks again.

This wouldn't work, during development done native dependencies are installed via npm install, and the native dependencies are platform specific. I.e. Windows <> wsl (Linux)
In the case of tests we download a Windows version of VSCode and on wsl we download a Linux version of VSCode, i.e. it's impossible to get this working unless the user runs npm install again.

Would it be possible if the user runs npm install under the new platform?
As in:
C:\Users\user\projects: npm install
npm installs platform specific modules to .vscode-test\win64 as expected
C:\Users\user\projects: wsl.exe
/mnt/c/Users/projects: npm install
And then npm installs platform specific modules to ./.vscode-test/linux-64 as expected.
Because seemingly the only problem I've noticed insofar is not checking for the existence of the right dirs and handling the case appropriately, which more than likely wouldn't be more than 1 or 2 lines of code changed though admittedly I haven't checked this myself.

Thanks for the suggestion! We talked about it with the team and we have unfortunately decided we will not be moving forward with this idea. We think there isn't an enough widespread need for this to warrant the maintenance cost for the feature.


Fix and improve README

Turn it more "elegant" by:

[ ] writing a better descripion of the package's purposes
[ ] placing the project logo as the top element
[ ] Initializing the Getting Started section
[ ] EO Principles badge
[ ] Rultor badge
[ ] pub badge
[ ] license badge
[ ] lint badge
[ ] PDD badge
[ ] CI status badge
[ ] codecov badge
[ ] Hits-of-Code badge

@rafamizes the puzzle #8 is still not solved.


docs(v2): recommend Docusaurus 2 usage

Motivation
It has been reported that some parts of the doc let people think versioning is not supported yet.
Versioning is working fine now, and i18n is coming soon.
We should now drive more users to start on v2 than v1, despite v2 still being in alpha (not for long), even if they need i18n support.
Note: most users are already using v2 anyway:

@slorber thanks!


read_matrix_market_file() bug (relating to reading in karate club digraph)

There seems to be an issue relating to the way way read_matrix_market_file() reads in the karate.mtx file ( in /arachne/data/)  and instantiates an ar.Digraph. The edges added in don't appear to be correct.

This was caused due to an issue with the edge aggregators in the Chapel method readMatrixMarketFileMsg. The aggregators were removed in favor of:
src[ind] = temp[0]:int;
dst[ind] = temp[1]:int;
wgt[ind] = temp[2]:real;


Unable to use two fields with @default(now()) directive

Right now query engine will throw a parsing error when we try to execute a create query against a model with two DateTime fields marked with @default(now()) directive.

Reproduction: https://github.com/harshit-test-org/prisma-p2-457
Steps:

Clone this repo and install node dependencies
Run prisma2 dev
Run ts-node src/script.ts
See the error

Note: This relates to the query engine expression work.

internal note: dropping as part of a larger refactor that we'll get to later.

Closing as duplicate of https://github.com/prisma/photonjs/issues/183


Onedeploy API swapper spec

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month - October
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[x] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

BTW, do we have deployment status API?
subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/deploymentStatus/{deploymentId}

deploymentStatus

Yes there is  a deployment status API

BTW, do we have deployment status API?
subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/deploymentStatus/{deploymentId}

@weidongxu-microsoft - can you please approve and merge the PR if it looks good.


Add support for this. Issue: https://github.com/charliermarsh/ruff/issues/970

How does it relate to PGH001?

Good point, its the same rule. Thanks!

It should be added to the many-to-many mapping.


[FLOC-2907] Human-readable volume names

When possible we want UIs displaying information about volumes we've created to include something a human can easily use to correlate with our logs. I.e. we want a user to be able to say "oh that's dataset XYZ and I see that detached earlier that's what's going on". Right now there's a whole bunch of extra work trying to correlate volumes with Flocker datasets.

Review status: 0 of 5 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

flocker/node/agents/functional/test_ebs.py, line 116 [r1] (raw file):
I'm sure this is covered somewhere, but I'm just curious: Presumably this is run against real AWS since we don't have a full fake aws implementation (AFAIK). How do we keep this from just adding volumes and not deleting them? Presumably that could eventually be expensive if we just keep creating volumes and never remove them. Same with the Cinder implementation.

Comments from the review on Reviewable.io

If you follow the code there's a flocker.node.agents.test.blockdevicefactory.get_blockdeviceapi_with_cleanup that is used to construct IBlockDeviceAPI used by tests.

Thanks.
Build failures look like known issues (but a JIRA search doesn't turn up an issue for the DatasetExists failures ...  File one, please).
I don't think the issue this PR fixes is defined very well.  A user story giving some sense of how this change actually helps users would probably be nice.  It's not clear how presenting the information in this way makes the user's life easier - or how the user will learn about this feature in order to benefit from it.
In the future I'd like to see more thought (reflected somewhere in our trail of artifacts) put into the user experience for changes that are primarily user-experience-oriented.
Last thought - there's no upgrade code here.  Anyone who already has volumes won't benefit from this and once they upgrade Flocker, they'll have a mix of annotated and un-annotated volumes.  That seems undesirable to me.  If the feature is useful, we should provide it to everyone?  At the very minimum, warning existing users of the inconsistency that will result seems necessary.
Address those points and then merge.

Sorry, user story was somewhat implicit, yeah. Goal is "I can easily identify volumes as belonging to Flocker and to which dataset they correspond, by glancing at EC2 web console, Cinder command line, etc." So user doesn't have to do anything special, they just use thier normal tools and life is easier.
Upgrading... yeah, maybe. On the one hand maybe not worth the time since user base is so small and this is not a semantic change, on the other hand would help current user who is main motivation (for easier debugging).

I'm going to say that upgrade isn't worth it; better to have functionality for new users *the vast majority) and not spend time on upgrading something that is merely a nice to have.  I will document the new feature and its impact on existing volumes, though.

OK, mergeable as soon as buildbot is green.


Skype calling bot CollectDigits no longer works and Recognize seldom works

Trying to collect digits from a Skype calling bot forever returns "InternalServerError". It used to work a few weeks ago and now never works.
Also the recognize speech often fails with "InitialSilenceTimeout" or "InternalServerError" for no apparent reason.

Can you share your bot Id please?

Here you go: c0b9c83d-a571-4e4c-9301-9fbc9102d751

Thanks. I placed a call and it worked well. Can you give me the scenario that does not work and I can look.

@camer314 do you still have this issue?

I will go ahead and close the issue for now. Please re-activate if you are hitting the issue and let us know the exact scenario that you are trying out.


(iOS) RTL issues

Here are some issues and improvements to the app when the language is RTL (such as Arabic):

Fees explanation popup is misaligned

Hi again, thanks for the fixed, I checked it and everything looks great!
I found another small issues:

the gray amount in sats is misaligned

channel information should be LTR

if possible add more room for this text, there are 3 words missing.

the gray amount in sats is misaligned

Can you give me more clarity on this. It currently reads "sat .015153-". I'm guessing this is wrong. What should it be?

Can you give me more clarity on this. It currently reads "sat .015153-". I'm guessing this is wrong. What should it be?

it should be "sat -153.015"
numbers in RTL are just like LTR languages, you read them from left to right (look at the fees on the same screen, it is rendered without issues), maybe the only difference is the "sat" is on the other side of the number so if "sat" is translated it should be like this

Thanks for the fixes and support for RTL languages.
I will close the issue


Watch gets dropped quite frequently for v1/services

Hey,
Noticing some really odd behaviour when watching services.
As you can see in this log, i'm watching three apis, nodes, ingresses and services.  Services gets dropped really frequently and requires reconnection.  When i say dropped, i mean the watcher.each do |notice| block returns and i have to reconnect the watch.
No errors or anything as far as I can see?
I, [2018-10-01T14:41:32.866122 #1]  INFO -- : [Queues::QueueFactory#queue_for] Using redis for queue
I, [2018-10-01T14:41:32.869182 #1]  INFO -- : [App#watch] Watching for 'nodes' on api '' version 'v1'
I, [2018-10-01T14:41:32.870100 #1]  INFO -- : [App#watch] /v1/nodes will start from offset: 41408258
I, [2018-10-01T14:41:32.870514 #1]  INFO -- : [App#watch] Watching for 'ingresses' on api '/apis/extensions' version 'v1beta1'
I, [2018-10-01T14:41:32.871624 #1]  INFO -- : [App#watch] /apis/extensions/v1beta1/ingresses will start from offset: 41407491
I, [2018-10-01T14:41:32.873113 #1]  INFO -- : [App#watch] Watching for 'services' on api '/apis/atcloud.io' version 'v1'
I, [2018-10-01T14:41:32.874617 #1]  INFO -- : [App#watch] /apis/atcloud.io/v1/services will start from offset: 41393730
W, [2018-10-01T14:43:10.771390 #1]  WARN -- : [App#watch] /apis/atcloud.io/v1/services stopped, will restart from 41393730
I, [2018-10-01T14:43:11.771714 #1]  INFO -- : [App#watch] /apis/atcloud.io/v1/services will start from offset: 41393730
I, [2018-10-01T14:44:04.085678 #1]  INFO -- : [Handlers::Slack#create_apis_atcloud_io_v1_services] shippr-simple
W, [2018-10-01T14:44:35.922408 #1]  WARN -- : [App#watch] /apis/atcloud.io/v1/services stopped, will restart from 41408969
I, [2018-10-01T14:44:36.922661 #1]  INFO -- : [App#watch] /apis/atcloud.io/v1/services will start from offset: 41408969
W, [2018-10-01T14:45:54.584440 #1]  WARN -- : [App#watch] /apis/atcloud.io/v1/services stopped, will restart from 41408969
I, [2018-10-01T14:45:55.584756 #1]  INFO -- : [App#watch] /apis/atcloud.io/v1/services will start from offset: 41408969
W, [2018-10-01T14:47:13.200599 #1]  WARN -- : [App#watch] /apis/atcloud.io/v1/services stopped, will restart from 41408969
I, [2018-10-01T14:47:14.200865 #1]  INFO -- : [App#watch] /apis/atcloud.io/v1/services will start from offset: 41408969
W, [2018-10-01T14:48:58.754999 #1]  WARN -- : [App#watch] /apis/atcloud.io/v1/services stopped, will restart from 41408969
I, [2018-10-01T14:48:59.755265 #1]  INFO -- : [App#watch] /apis/atcloud.io/v1/services will start from offset: 41408969
W, [2018-10-01T14:50:15.733208 #1]  WARN -- : [App#watch] /apis/atcloud.io/v1/services stopped, will restart from 41408969
I, [2018-10-01T14:50:16.733523 #1]  INFO -- : [App#watch] /apis/atcloud.io/v1/services will start from offset: 41408969

Any ideas?

Poke... We see this with some resources but not others.  It's bizzare.  Seems to be consistent with CRDs and v1/services

I've noticed on https://github.com/Stono/kubeclient/blob/master/lib/kubeclient/watch_stream.rb#L25 when this happens, the chunk is empty, so it's like we're receiving a nil body (perhaps some sort of keep alive?)

sounds like duplicate of #273.  (see there and #275 for some discussion how to re-connect from last seen resourceVersion.  not yet implemented in kubeclient itself.  your "stopped, will restart from offset NNNN" log suggests you already implemented that?)
The empty chunk finding is extremely interesting!
But looking at the code, empty chunk should just be a no-op, should not terminate the watch.  So I'm afraid it's not a bug where we choke on "" but server really closes the socket (and the block may get one last empty chunk when that happens)?
From what I understood kubernetes disconnects watch sockets after some period of inactivity.

Hey, thanks for this.
That's right, I have already implemented a loop and restart from the last successful resourceVersion, it just feels like there should be some sort of keep alive that we are missing as it feels a bit rough!

try adding logging for each received chunk, at least timestamp & the size of the chunk.  it will let you confirm or refute:

is there roughly constant time between last non-empty chunk to disconnection?
is there exactly one empty chunk just before .each loop exits?

There is exactly one chunk of length 0 before the body.read.each exits

cool, then I think we can close this in favor of #273?
if you feel like working on improving this, see my comments on #275.
perhaps a smaller step that'd already be useful is enriching watch objects with an attribute storing the last seen resource_version.

I'm not sure, it feels so odd.... check these logs which output all events:
You can see I set up watchers for:

/v1/nodes
/apis/extensions/v1beta1/ingresses
/apis/atcloud.io/v1/services
/apis/kubitzer.io/v1/secrets
/apis/kubitzer.io/v1/shared_secrets

You can see the CRDs are the ones that drop more frequently, it doesn't seem to be anything to do with a rate of activity (because /apis/extensions/v1beta1/ingresses also doesn't have any activity, but doesn't drop)
W, [2018-10-09T22:07:03.545247 #37311]  WARN -- : [App#block in setup_watch_thread] /apis/kubitzer.io/v1/shared_secrets has no offset stored, will start at the latest offset43258964 instead
W, [2018-10-09T22:07:03.545317 #37311]  WARN -- : [App#block in setup_watch_thread] Some events may have been missed!
I, [2018-10-09T22:07:03.545356 #37311]  INFO -- : [App#watch] /apis/kubitzer.io/v1/shared_secrets watch will start from offset: 43258964
W, [2018-10-09T22:07:03.547095 #37311]  WARN -- : [App#block in setup_watch_thread] /apis/kubitzer.io/v1/secrets has no offset stored, will start at the latest offset 43265612 instead
W, [2018-10-09T22:07:03.547139 #37311]  WARN -- : [App#block in setup_watch_thread] Some events may have been missed!
I, [2018-10-09T22:07:03.547164 #37311]  INFO -- : [App#watch] /apis/kubitzer.io/v1/secrets watch will start from offset: 43265612
W, [2018-10-09T22:07:03.642914 #37311]  WARN -- : [App#block in setup_watch_thread] /v1/nodes has no offset stored, will start at the latest offset 43331571 instead
W, [2018-10-09T22:07:03.642966 #37311]  WARN -- : [App#block in setup_watch_thread] Some events may have been missed!
I, [2018-10-09T22:07:03.642992 #37311]  INFO -- : [App#watch] /v1/nodes watch will start from offset: 43331571
W, [2018-10-09T22:07:03.812132 #37311]  WARN -- : [App#block in setup_watch_thread] /apis/atcloud.io/v1/services has no offset stored, will start at the latest offset 43312473 instead
W, [2018-10-09T22:07:03.812202 #37311]  WARN -- : [App#block in setup_watch_thread] Some events may have been missed!
I, [2018-10-09T22:07:03.812237 #37311]  INFO -- : [App#watch] /apis/atcloud.io/v1/services watch will start from offset: 43312473
W, [2018-10-09T22:07:03.899857 #37311]  WARN -- : [App#block in setup_watch_thread] /apis/extensions/v1beta1/ingresses has no offset stored, will start at the latest offset 43312598 instead
W, [2018-10-09T22:07:03.899924 #37311]  WARN -- : [App#block in setup_watch_thread] Some events may have been missed!
I, [2018-10-09T22:07:03.899952 #37311]  INFO -- : [App#watch] /apis/extensions/v1beta1/ingresses watch will start from offset: 43312598
D, [2018-10-09T22:07:06.474703 #37311] DEBUG -- : [App#add_to_queue] update (43331590) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-70fv
D, [2018-10-09T22:07:06.711010 #37311] DEBUG -- : [App#add_to_queue] update (43331591) /v1/nodes/gke-delivery-platform-cpu1ram2-330d7c37-cggp
D, [2018-10-09T22:07:08.301875 #37311] DEBUG -- : [App#add_to_queue] update (43331595) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-htrz
D, [2018-10-09T22:07:15.961709 #37311] DEBUG -- : [App#add_to_queue] update (43331614) /v1/nodes/gke-delivery-platform-cpu1ram2-330d7c37-cggp
D, [2018-10-09T22:07:16.672584 #37311] DEBUG -- : [App#add_to_queue] update (43331618) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-70fv
D, [2018-10-09T22:07:16.771613 #37311] DEBUG -- : [App#add_to_queue] update (43331619) /v1/nodes/gke-delivery-platform-cpu1ram2-330d7c37-cggp
D, [2018-10-09T22:07:17.128188 #37311] DEBUG -- : [App#add_to_queue] update (43331620) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-htrz
D, [2018-10-09T22:07:18.431425 #37311] DEBUG -- : [App#add_to_queue] update (43331623) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-htrz
D, [2018-10-09T22:07:26.823987 #37311] DEBUG -- : [App#add_to_queue] update (43331646) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-70fv
D, [2018-10-09T22:07:26.937033 #37311] DEBUG -- : [App#add_to_queue] update (43331647) /v1/nodes/gke-delivery-platform-cpu1ram2-330d7c37-cggp
D, [2018-10-09T22:07:28.408847 #37311] DEBUG -- : [App#add_to_queue] update (43331648) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-htrz
D, [2018-10-09T22:07:36.797184 #37311] DEBUG -- : [App#add_to_queue] update (43331672) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-70fv
D, [2018-10-09T22:07:36.894620 #37311] DEBUG -- : [App#add_to_queue] update (43331673) /v1/nodes/gke-delivery-platform-cpu1ram2-330d7c37-cggp
D, [2018-10-09T22:07:38.493136 #37311] DEBUG -- : [App#add_to_queue] update (43331674) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-htrz
D, [2018-10-09T22:07:46.865428 #37311] DEBUG -- : [App#add_to_queue] update (43331697) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-70fv
D, [2018-10-09T22:07:46.934801 #37311] DEBUG -- : [App#add_to_queue] update (43331698) /v1/nodes/gke-delivery-platform-cpu1ram2-330d7c37-cggp
D, [2018-10-09T22:07:48.473646 #37311] DEBUG -- : [App#add_to_queue] update (43331702) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-htrz
D, [2018-10-09T22:07:56.914548 #37311] DEBUG -- : [App#add_to_queue] update (43331724) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-70fv
D, [2018-10-09T22:07:56.963743 #37311] DEBUG -- : [App#add_to_queue] update (43331725) /v1/nodes/gke-delivery-platform-cpu1ram2-330d7c37-cggp
D, [2018-10-09T22:07:58.531128 #37311] DEBUG -- : [App#add_to_queue] update (43331726) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-htrz
D, [2018-10-09T22:08:00.568104 #37311] DEBUG -- : [App#add_to_queue] update (43331734) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-70fv
D, [2018-10-09T22:08:07.011952 #37311] DEBUG -- : [App#add_to_queue] update (43331750) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-70fv
D, [2018-10-09T22:08:07.112442 #37311] DEBUG -- : [App#add_to_queue] update (43331752) /v1/nodes/gke-delivery-platform-cpu1ram2-330d7c37-cggp
D, [2018-10-09T22:08:08.621882 #37311] DEBUG -- : [App#add_to_queue] update (43331753) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-htrz
W, [2018-10-09T22:08:09.039144 #37311]  WARN -- : [App#watch] /apis/kubitzer.io/v1/shared_secrets stopped, will restart from 43258964
I, [2018-10-09T22:08:10.042149 #37311]  INFO -- : [App#watch] /apis/kubitzer.io/v1/shared_secrets watch will start from offset: 43258964
D, [2018-10-09T22:08:16.945298 #37311] DEBUG -- : [App#add_to_queue] update (43331777) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-70fv
D, [2018-10-09T22:08:17.000401 #37311] DEBUG -- : [App#add_to_queue] update (43331778) /v1/nodes/gke-delivery-platform-cpu1ram2-330d7c37-cggp
D, [2018-10-09T22:08:17.105476 #37311] DEBUG -- : [App#add_to_queue] update (43331780) /v1/nodes/gke-delivery-platform-cpu1ram2-330d7c37-cggp
D, [2018-10-09T22:08:17.177432 #37311] DEBUG -- : [App#add_to_queue] update (43331781) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-htrz
D, [2018-10-09T22:08:18.712541 #37311] DEBUG -- : [App#add_to_queue] update (43331784) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-htrz
W, [2018-10-09T22:08:22.359254 #37311]  WARN -- : [App#watch] /apis/kubitzer.io/v1/secrets stopped, will restart from 43265612
I, [2018-10-09T22:08:23.360279 #37311]  INFO -- : [App#watch] /apis/kubitzer.io/v1/secrets watch will start from offset: 43265612
W, [2018-10-09T22:08:23.389326 #37311]  WARN -- : [App#watch] /apis/atcloud.io/v1/services stopped, will restart from 43312473
I, [2018-10-09T22:08:24.390742 #37311]  INFO -- : [App#watch] /apis/atcloud.io/v1/services watch will start from offset: 43312473
D, [2018-10-09T22:08:26.850834 #37311] DEBUG -- : [App#add_to_queue] update (43331806) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-70fv
D, [2018-10-09T22:08:26.952799 #37311] DEBUG -- : [App#add_to_queue] update (43331807) /v1/nodes/gke-delivery-platform-cpu1ram2-330d7c37-cggp
D, [2018-10-09T22:08:28.591471 #37311] DEBUG -- : [App#add_to_queue] update (43331809) /v1/nodes/gke-delivery-platform-core-pool-a5aa4684-htrz

Yeah, somewhat strange.
Found this:
https://github.com/kubernetes/apiserver/blob/2603dd2bc0e2/pkg/server/config.go#L157-L159

// If specified, long running requests such as watch will be allocated a random timeout between this value, and
// twice this value.  Note that it is up to the request handlers to ignore or honor this timeout. In seconds.
MinRequestTimeout int

controlled by --min-request-timeout command line flag, not sure what's the default.
Anyway, it's a thing and clients need to deal with it.
closing, let's continue on #273.


Fix CI for Windows

[x] Closes #240

Summary

Uses action to install poetry
For the test of the distribution, avoids poetry because Windows CI isn't installing it in the right place
Adds a couple of missing PYI files that pyright said were missing

One downside (at least for me).  The setting
[tool.poe.executor]
type = "virtualenv"

makes a local test with poetry not work inside of a conda environment.
But at least the CI is working.

I was going to merge this since green.  Fix looks fine, although the source'ing is annoying. but maybe necessary. Could you instead call poetry shell before the poe commands.
I didn't merge because looks like you accidentally got some pyi changes in that aren't needed.

So the issue is that we have at least two python executables and for some reason, poetry/windows CI uses both of them in an inconsistent manner?
Is it possible to remove one of them from the PATH (or delete it) so that poetry/CI is not confused by it?

I didn't merge because looks like you accidentally got some pyi changes in that aren't needed.

That was intentional, as pyright was reporting that some imports were missing.

So the issue is that we have at least two python executables and for some reason, poetry/windows CI uses both of them in an inconsistent manner?
Is it possible to remove one of them from the PATH (or delete it) so that poetry/CI is not confused by it?

I don't know.  Prior to a few days ago, we always had 2 environments on Windows and things worked.  With the setup-python action, it creates a "system" python, and then poetry creates a virtual one.  I created an issue in the poetry repo thinking that the upgrade from poetry 1.1.15 to 1.2 was the issue, but the poetry people found a failed CI run on Windows using 1.1.15.
I'm now thinking that it is the setup-python action that messed things up.

I was going to merge this since green. Fix looks fine, although the source'ing is annoying. but maybe necessary. Could you instead call poetry shell before the poe commands.

See https://github.com/snok/install-poetry#running-on-windows as to why we have to do the sourcing.

closing in favor of #249


contextual logging: beta in Kubernetes 1.30

Related-to: https://github.com/kubernetes/enhancements/issues/3077
/hold
https://github.com/kubernetes/kubernetes/pull/122589 needs to be merged first.

Hello @pohly :wave: please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before Tuesday March 12th 2024 18:00 PST. Thank you!

/milestone 1.30

Hello @pohly 👋, it looks like you've already engaged feedback in review of this PR. Great job! Keep this up. 🚀
@alculquicondor @liggitt @serathius @ehashman @thockin
When one of y'all have a moment, please give a review for technical accuracy. A friendly reminder that this PR needs doc review complete by Doc Freeze on March 26th 18:00 PT to get this into the release.
It also looks like there is a hold here and a PR that has been merged. Can this hold be removed?
Thanks!

There's not much technical content that needs to be reviewed here. I think it's fine if the docs team does a LGTM + approve for the wording and formatting.
/hold cancel
Implementation was merged, PR can be merged, too.

/milestone 1.30


fix(Provider): staticStyles should be executed with the merged siteVariables

This PR aims to fix https://github.com/stardust-ui/react/issues/526
Note
Important thing to note is that, per one Provider we will execute the staticStyles only once, when they are the first time applied.

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS


Fix #41 - get cake scripts running on Mac

Also added compile-time support for OSX.10.12-x64. The acceptance tests still fail on this version of OS X, however, because of the funky stuff going on in TestConfiguration.cs. Fixing this is outside the scope of this issue.

The build now works on my mac and windows. Note that the release notes cannot be generated on osx because that uses an exe that is not cross platform.
I had to add runtimes for osx.10.12-x64 to do the work on my mac. This exposes problems in the acceptance tests - they fail for me because the config file switcheroo that is going on in TestConfiguration.cs assumes osx.10.11-x64 if you're on a mac and I didn't know how to fix. However, I guess you're using osx.10.11-x64 so should be fine for you for now. I remember that this config stuff also caused issues when I set up the original cake scripts, so would be good to fix.

@binarymash thanks! All looks fine. I'm going to sort that testconfig thing now.