TypeError: dataloaderSequelize is not a function

This is the code that I used:
const dataloaderSequelize = require('dataloader-sequelize');

dataloaderSequelize(sequelize)

The library is combiled with babel, you'll likely need to use require('dataloader-sequelize').default

require('dataloader-sequelize').default works!!
Thanks!!


Zapproxy integration with Testcafe

What is your Test Scenario?
I would like the ability to run Zap proxy along with my Testcafe tests
What are you suggesting?
Integrate Zap proxy and Chrome capabilities required.
What alternatives have you considered?
Can't find any
Additional context

Thank you for sharing your idea with us. We will check out this tool and see how its integration might be useful for testcafe users.

Hi, was there an investigation into ZAP proxy integration with Testcafe?

Hi, No there hasn't been any update.


fix: example docker run parameters

In README.md example docker run parameters were in the wrong order.
Correct order copied from aws-lambda-runtime-interface-emulator:
https://github.com/aws/aws-lambda-runtime-interface-emulator#test-an-image-without-adding-rie-to-the-image

I've gotten this wrong.  Apologies.


Hide already added mods in build

Hide all added mods from "Add a Mod" section in build management. Makes
adding new mods a lot easier.

This will be Amazing.

+1, This would be very useful.

Please resubmit this request on the dev branch


Fix default target in driver

Recent changes removed migraphx_all_target lib from driver and that led to missing compile time definitions.
Missing compile definitions led to change of default target in driver.
This PR fixes that.

can't use lazy loading in driver. it requires GPU header files for perf measurements.

https://github.com/ROCmSoftwarePlatform/AMDMIGraphX/pull/1608
Not sure how performance tests passed on this one, it would have used CPU backend.


[Feature]: Circular progress widget

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
Create a new circular progress widget
Why should this be worked on?
Community contributed

@dilippitchika please check the related and give us an approval from the product POV


Remove .process listeners

This is more like a question than an issue, but i'd like to know what happens with the listeners (.process in particular) when no more messages get in the queue for a given message type. For example, lets say I set a listener like:
var kue = require('kue')
 , queue = kue.createQueue();

queue.process('foo', function(job, done){
  // Do something with the job
});

Is there a way to tell kue to stop (not temporarily pause) processing a given message type, so any memory allocated to that would be freed?
Something like:
var kue = require('kue')
 , queue = kue.createQueue();

queue.stopProcessing('foo');

Thanks a lot!

*bump


Update the product review resource based on developer documentation

Fixes #106
Update ProductReview resource to use information from: https://developer.bigcommerce.com/api/stores/v2/products/reviews
Todo:

[ ] Testing
[ ] Update changelog

closing this in favor of getting #107 merged down.


chore: Use get-tested for GH actions

Modified

Updated directory and optparse-applicative boundaries
Include tested-with
Modify GH Actions

solves #51

Hey @DavidMazarro I think this is ready for a second review!


[Bug]: CUDA out of memory when setting prompt_logprobs with larger batch_size

Your current environment
Collecting environment information...
PyTorch version: 2.3.0+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.6 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Clang version: Could not collect
CMake version: version 3.29.3
Libc version: glibc-2.31

Python version: 3.11.5 (main, Sep 11 2023, 13:54:46) [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.4.0-182-generic-x86_64-with-glibc2.31
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA A100 80GB PCIe
Nvidia driver version: 535.171.04
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                       x86_64
CPU op-mode(s):                     32-bit, 64-bit
Byte Order:                         Little Endian
Address sizes:                      48 bits physical, 48 bits virtual
CPU(s):                             256
On-line CPU(s) list:                0-255
Thread(s) per core:                 2
Core(s) per socket:                 64
Socket(s):                          2
NUMA node(s):                       2
Vendor ID:                          AuthenticAMD
CPU family:                         25
Model:                              1
Model name:                         AMD EPYC 7713 64-Core Processor
Stepping:                           1
Frequency boost:                    enabled
CPU MHz:                            1499.385
CPU max MHz:                        2000.0000
CPU min MHz:                        1500.0000
BogoMIPS:                           4000.18
Virtualization:                     AMD-V
L1d cache:                          4 MiB
L1i cache:                          4 MiB
L2 cache:                           64 MiB
L3 cache:                           512 MiB
NUMA node0 CPU(s):                  0-63,128-191
NUMA node1 CPU(s):                  64-127,192-255
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit:        Not affected
Vulnerability L1tf:                 Not affected
Vulnerability Mds:                  Not affected
Vulnerability Meltdown:             Not affected
Vulnerability Mmio stale data:      Not affected
Vulnerability Retbleed:             Not affected
Vulnerability Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:           Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:           Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIBP always-on, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Not affected
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 nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 pcid 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 invpcid_single hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 invpcid cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr wbnoinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold v_vmsave_vmload vgif umip pku ospke vaes vpclmulqdq rdpid overflow_recov succor smca

Versions of relevant libraries:
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.26.4
[pip3] nvidia-nccl-cu12==2.20.5
[pip3] torch==2.3.0
[pip3] transformers==4.41.2
[pip3] triton==2.3.0
[conda] numpy                     1.26.4                   pypi_0    pypi
[conda] nvidia-nccl-cu12          2.20.5                   pypi_0    pypi
[conda] torch                     2.3.0                    pypi_0    pypi
[conda] transformers              4.41.2                   pypi_0    pypi
[conda] triton                    2.3.0                    pypi_0    pypi
ROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.4.3
vLLM Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:
GPU0    CPU Affinity    NUMA Affinity   GPU NUMA ID
GPU0     X      73,201  1               N/A

Legend:

  X    = Self
  SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
  NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
  PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
  PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
  PIX  = Connection traversing at most a single PCIe bridge
  NV#  = Connection traversing a bonded set of # NVLinks

🐛 Describe the bug
torch.cuda.OutOfMemoryError: CUDA out of memory when setting prompt_logprobs=1 for a large batch
from transformers import AutoTokenizer
from vllm import LLM, SamplingParams

model_name = "meta-llama/Meta-Llama-3-8B-Instruct"
llm = LLM(model=model_name)
tokenizer = AutoTokenizer.from_pretrained(model_name)

messages = [
    {"role": "user", "content": "What is the capital of France? Repeat 50 times."},
    {"role": "assistant", "content": "The capital of France is Paris." * 50},
]
batch_size = 10
prompt_token_ids = [tokenizer.apply_chat_template(messages)] * batch_size
print("Prompt token ids:", len(prompt_token_ids[0]))

sampling_params = SamplingParams(temperature=0, max_tokens=1, prompt_logprobs=1)
outs = llm.generate(prompt_token_ids=prompt_token_ids, sampling_params=sampling_params)

Hi, same problem here, any idea how to fix it?

It is known that requesting prompt_logprobs can cause a spike in memory usage and lead to an crash. OOMs due to logprobs are being tracked on:
https://github.com/vllm-project/vllm/issues/5907
There is no fix yet, but the current workaround is to use --enable-chunked-prefill. This reduces the meomry spike due to the limit on the number of tokens processed in a batch, but is not supported yet supported for all other parameter configurations.


Parsing of contract input for fixed uint8 array (uint8[8]) fails

Version
ethers v0.17.0
Platform
Mac
Description
I tried this code:
use ethers::prelude::*;
use ethers::abi::AbiDecode;

abigen!(
    WyvernExchangeV1,
    r#"[
        function atomicMatch_(address[14] addrs, uint[18] uints, uint8[8] feeMethodsSidesKindsHowToCalls, bytes calldataBuy, bytes calldataSell, bytes replacementPatternBuy, bytes replacementPatternSell, bytes staticExtradataBuy, bytes staticExtradataSell, uint8[2] vs, bytes32[5] rssMetadata) public payable
    ]"#,
);

fn main() {
    let tx_input = "[encoded data, 5834 characters]";
    let call_data: Bytes = tx_input.parse().unwrap();
    let decoded = AtomicMatchCall::decode(&call_data).unwrap();
}

Results in:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: DetokenizationError(InvalidOutputType("Expected `FixedBytes(8)`, got FixedArray([Uint(1), Uint(0), Uint(0), Uint(1), Uint(1), Uint(1), Uint(0), Uint(1)])"))',

It seems that the field uint8[8] feeMethodsSidesKindsHowToCalls can not be parsed correctly. I would expect no error.
I guess the error is based in ethers-core/src/abi/tokens.rs. The impl<const N: usize> Tokenizable for [u8; N] { should parse maybe as well FixedArray?
I copy/pasted very quick a test case that should pass I guess in tokens.rs. Hope I am not leading in a wrong direction:
    #[test]
    fn should_decode_array_of_fixed_uint8() {
        // uint8[8]
        let tokens = vec![Token::FixedArray(vec![
            Token::Uint(1.into()),
            Token::Uint(2.into()),
            Token::Uint(3.into()),
            Token::Uint(4.into()),
            Token::Uint(5.into()),
            Token::Uint(6.into()),
            Token::Uint(7.into()),
            Token::Uint(8.into()),
        ])];
        let data: [u8; 8] = Detokenize::from_tokens(tokens).unwrap();
        assert_eq!(data[0], 1);
        assert_eq!(data[1], 2);
        assert_eq!(data[2], 3);
        assert_eq!(data[7], 8);
    }

rn we have byte arrays as FixedBytes:
impl<const N: usize> AbiType for [u8; N] {
    fn param_type() -> ParamType {
        ParamType::FixedBytes(N)
    }
}

which would match bytes8,
so there's some ambiguity with uint8[..] arrays.
so uint8[8] should probably be generated as [U256; u8]?

I see that the lexer.rs does parse it correct:
    #[test]
    fn test_parse_fixed_array_uint8() {
        assert_eq!(
            HumanReadableParser::parse_type("uint8[8]").unwrap(),
            ParamType::FixedArray(Box::new(ParamType::Uint(8)), 8)
        );
    }

The codec.rs code is hard to read because of the special treatment for arrays. I would not like to overcomplicated things but could a custom type be helpful to get the mapping between lexer and codec correct? I would guess it could be preferable to avoid U256 here.
If for the sake of backward compatibility reasons it is simpler I would agree for parsing it as [U256; 8] instead of [u8; 8].

I see that the lexer.rs does parse it correct:
    #[test]
    fn test_parse_fixed_array_uint8() {
        assert_eq!(
            HumanReadableParser::parse_type("uint8[8]").unwrap(),
            ParamType::FixedArray(Box::new(ParamType::Uint(8)), 8)
        );
    }

The codec.rs code is hard to read because of the special treatment for arrays. I would not like to overcomplicated things but could a custom type be helpful to get the mapping between lexer and codec correct? I would guess it could be preferable to avoid U256 here.
If for the sake of backward compatibility reasons it is simpler I would agree for parsing it as [U256; 8] instead of [u8; 8].

I would also be ok with [U256; 8] instead of [u8; 8].

you would need u256 anyways when tokenizing the array.
so the only distinct solution here would be either uint8 -> U256 or introducing additional wrapper types, wdyt @gakonst ?

I'd try to make u8 work w/o converting to u256 , but understand that this can be a pain, so if it is let's go with the simple solution

another solution would be to roll a custom U8 type used for fixedbytes uint8[size] edge case

That also works, as long as it doesn't leak to the user, i.e. I should still be able to pass a u8 and not need to convert to U8 myself

does decoing via the generated call struct work?

Hi @mattsse,
my bad. After seeing the expanded macro I noticed that my input data is not correct. I missed to skip the "0x". Everything is working now fine. Thanks you very much.
Fixed:
let tx_input = "...";
let call_data: Bytes = tx_input.parse().unwrap();
...
let log_data_token: Vec<Token> = ethers::abi::decode(&param_types_atomic, &call_data[4..]).unwrap();


Reset state after logout & changing a job

Motivation and context
Resolved #2524
How has this been tested?
Manual testing
Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[x] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[x] I have updated the license header for each file (see an example below)

# Copyright (C) 2020 Intel Corporation
#
# SPDX-License-Identifier: MIT

Coverage increased (+0.008%) to 61.227% when pulling cc3e977f359bb70d83b813aabd237a33c921793e on bs/clear_storage into 5735efe72f4c5a50cd6a417cdc01ef88928e9a93 on develop.


Framework missing if build configuration changed

Framework can't be found when I changed the build configuration from 'Build' to 'Release'. Thus, import XCGLogger gives error.
Using Xcode 9.1, swift.

Fixed by building project.
I was using separate space for DerivedData, it was probably due insufficient space.


0.5.17 drops support for node 10 and webpack

The latest version 0.5.17 has a breaking change for consumers who use webpack and are on node v10.x.
I've solved this by locking my version to 0.5.16.
Error: ./node_modules/source-map-support/source-map-support.js
--
  | Module not found: Error: Can't resolve 'worker_threads' in '.../node_modules/source-map-support'
  | resolve 'worker_threads' in '.../node_modules/source-map-support'
  | Parsed request is a module

Hmm, this is interesting, the require is made dynamically and is inside a try/catch 🤔
Any ideas if there is anything we can do to tell WebPack that it doesn't need to be able to resolve it?

Hmm, this is probably the best solution:
https://github.com/getsentry/sentry-javascript/blob/bd35d7364191ebed994fb132ff31031117c1823f/packages/utils/src/misc.ts#L9-L11
https://github.com/getsentry/sentry-javascript/blob/89bca28994a0eaab9bc784841872b12a1f4a875c/packages/hub/src/hub.ts#L340
ref: https://github.com/webpack/webpack/issues/8826

@vsumner hmm, are you using WebPack to produce a bundle for Node.js or for the browser? 🤔

@vsumner could you test if #271 fixes this for you?

Sorry I missed this. @LinusU thanks for fixing this!


Getting red deprecation error when running my app that uses firebase packages

Hey Everybody,
I'm new to flutter and firebase, and recently I had a lot of problems and hardnesses for implementing firebase to a flutter app, but anyway, after creating my app and adding the google services file to my project and editing gradle files, when I added 3 packages from pub.dev(firebase_auth, firebase_core and cloud_firestore) and running the flutter packages get, and finally running my app, I got this red error in my console :
Note: C:\Users\Parsa\AppData\Roaming\Pub\Cache\hosted\pub.dartlang.org\cloud_firestore-0.12.9+4\android\src\main\java\io\flutter\plugins\firebase\cloudfirestore\CloudFirestorePlugin.java uses or overrides a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: C:\Users\Parsa\AppData\Roaming\Pub\Cache\hosted\pub.dartlang.org\cloud_firestore-0.12.9+4\android\src\main\java\io\flutter\plugins\firebase\cloudfirestore\CloudFirestorePlugin.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details.
My app was built successfully but I am wondering if there is a problem with my configuration or it's just a simple deprecation error?
Any help and comment are welcome.
Thanks a lot.
I want to put my gradle files and my pubspec.yaml file here in case you want to take a look at it:
My project level gradle file
buildscript {
    repositories {
        google()
        jcenter()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:3.2.1'
        classpath 'com.google.gms:google-services:4.0.1'
    }
}

allprojects {
    repositories {
        google()
        jcenter()
    }
}

rootProject.buildDir = '../build'
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
    project.evaluationDependsOn(':app')
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

My app level gradle file
def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
    localPropertiesFile.withReader('UTF-8') { reader ->
        localProperties.load(reader)
    }
}

def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
    throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}

def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
    flutterVersionCode = '1'
}

def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
    flutterVersionName = '1.0'
}

apply plugin: 'com.android.application'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"

android {
    compileSdkVersion 28

    lintOptions {
        disable 'InvalidPackage'
    }

    defaultConfig {
        // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
        applicationId "My application id :D"
        minSdkVersion 16
        targetSdkVersion 28
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
        multiDexEnabled true
    }

    buildTypes {
        release {
            // TODO: Add your own signing config for the release build.
            // Signing with the debug keys for now, so `flutter run --release` works.
            signingConfig signingConfigs.debug
        }
    }
}

flutter {
    source '../..'
}

dependencies {
    testImplementation 'junit:junit:4.12'
    androidTestImplementation 'androidx.test:runner:1.1.0-alpha4'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.1.0-alpha4'
    implementation 'androidx.multidex:multidex:2.0.0'
}
apply plugin: 'com.google.gms.google-services'

My pubspec.yaml file
name: flash_chat
description: A new Flutter application.

version: 1.0.0+1

environment:
  sdk: ">=2.0.0-dev.68.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter

  cupertino_icons: ^0.1.2
  animated_text_kit: ^1.3.1
  firebase_core: ^0.4.0+9
  cloud_firestore: ^0.12.9+4
  firebase_auth: ^0.14.0+5

dev_dependencies:
  flutter_test:
    sdk: flutter

flutter:
  uses-material-design: true

  assets:
  - images/

why all the modules converted into androidx :(

Hi @officer47p
I see there's an open issue addressing the case you described.
Please follow up on that issue,
I'm closing the current one as duplicate.
If you disagree please write in the comments
and I will reopen it.
Thank you


Code block support

Now code blocks are highlighting with prettify

This is awesome, I think this syntax works with both liquid and razor.
But there is a few things:

there is one test failing on AppVeyor. I have improved the build, now if a test fail the all build will fail.
I think it's too linked to pretiffy, I think it can be the default choice but we can add the possibility to override the highlighter, like in Jekyll?

For the last one, if you haven't the time I will look into it.
I want to make a very flexible highlighting:

Support different highlighter
Be able to parse different syntax:

{% highlight c# %}
{{c#}}

@shiftkey, @JakeGinnivan, what do you think?

For reference, this is how Jekyll does it:
{% highlight ruby %}
def foo
  puts 'foo'
end
{% endhighlight %}

A couple of quick thoughts on the proposed syntax (contrasting against the above sample):

I've stopped doing "four spaces to indicate code" in Markdown for a while now - it feels fiddly unless you've set your editor up right. I feel the code fencing is so much nicer for managing this pain (shift-TAB to remove the whitespace, live a happy life) but that's specific to GitHub-Flavoured Markdown (which I don't believe is supported in MarkdownDeep
One of the other benefits of the previous point is that you can specify the language inline

```ruby

That feels so much friendlier than needing to wrapp the language name in {{ foo }}

I do like dropping the "close tag" syntax

@laedit, @shiftkey, thank you for feedback. I will try to add suport of differenet syntax for declare code blocks. About highlighters: I suggest to use some predefine set of highlighters and choose it in the config like in the following line:
highlighter: prettyify

What kind of additional highlighters is needed?

There is a problem with the MarkdownDeep library. The issue about support for backtick fenced code blocks have been fixed only at 24 Feb 2014. But the current NuGet version of the library (0.5) is obsolete (last updated at August 20, 2012). So, it is impossible to implement nice support of markdown codeblocks with this version.
I suggest switching the project to CommonMark.NET for markdown processing. Advantages:

Great compatibility
Great performance
Full CommonMark specification support
Active developing

What do you think?

Also I suggest using of CommonMark Spec 0.17 without specific highlighter. For example, lines
```ruby
def foo(x)
  return 3
end
```

will transform in

def foo(x)
  return 3
end

Next, a pretzel user can add any highlighter yourself. What do you think?

I'd totally be down for switching over to a more modern Markdown library

That is a great idea!
I'm good with that.

It seems that prettify always need the class="prettyprint".
But there is highlightjs and prism which support the HTML5 convention.

It seems that prettify always need the class="prettyprint".

Yes, but you can add this class with one jQuery line. So, it is not a problem.

Good point.
Another way to do it: using an IContentTransform specific for each highlighter, if needed.

Done.

In that case we can use highlightjs which does not require JQuery.
Or just indicates to the user how to choose and use an highlighter?
For the plugins it is a bit more complicated :)
We have the PR #157 waiting, but in the meantime you can add a class in the plugin folder which will implement IContentTransform.
We will transform it to an external plugin (dll) after the acceptation of PR #157.

Ok, then I just will change prettyify+jQuery to highlightjs.

Done.

Any updates?

Sorry, I haven't got the time to merge it.
I intend to do it this week end, and to accept the PR #157 to be able to create the PrettifyContentTransformer plugin.


README badge to promote subscription plans

Like we do for Issues looking for funding, we should propose an SVG badge to integrate in README and such so the maintainer can showcase their subscription plans.
Basically, it could take the form of a pricing table.

Cleaning up GitHub issues. This one will resurface as a new one given conversation past Thursday.


IE,Firefox : Scroll Horizontal Problem

When I use this library for datatable in IE, Firefox (work fine only on Chrome), I found problem about Scroll Horizontal.
When I drag scroll horizontal and release mouse, position of scroll horizontal is not correct. You can see in my demo image ( .gif animation).
Please help me to resolve this problem.

It's been a long time since I worked with this plugin but i don't think it expects scrollbars to be visible and your gifs suggest that it's picking up mouse movement from clicking on the bars when it shouldn't. You might be able to fix this within a filterTarget check based on how close the mouse is to the bottom of the kinetic div.
I'm going to close this as it's very old though.


explore automating the pool pump

See https://neon.subspace.de/2017/10/smarter-swimming-pool-1-pool-pump/ for inspiration

Too expensive, juice is not worth the squeeze.  Won't pursue.


I want to contribute but I have few questions, please reply.

can we add custom filters or is it a strict policy to add the instagram filters only ?
Thanks. #question

@ahsan-alef No, currently it only allows Instagram's filters.


Simplifies the CustomObjectiveCBrideable protocol by removing unnecessary conformances

There's no need for implicitly bridged types to conform to the protocol, so we can remove their conformances and use traditional bridging for non-conforming types.

I'm not entirely sure this is an improvement given we lose exhaustivity checks, so I'm going to close this.

(For context, this change seemed to be the groundwork to fixing a bug, but I late realized that this would not be sufficient.)


feat: add methods to support ERC-4337 accounts

Description
Depends on:

[x] https://github.com/MetaMask/keyring-api/pull/213
[x] https://github.com/MetaMask/KeyringController/pull/315
[x] https://github.com/MetaMask/core/pull/3617

This PR adds the following new methods available in the EthKeyring interface:

prepareUserOperation
patchUserOperation
signUserOperation

See the PR in the keyring-api for more details.
Checklist

[ ] I've updated the test suite for new or updated code as appropriate
[ ] I've updated documentation for new or updated code as appropriate (note: this will usually be JSDoc)
[ ] I've highlighted breaking changes using the "BREAKING" category above as appropriate

@metamaskbot publish-preview

@SocketSecurity ignore npm/<EMAIL_ADDRESS>


Use declared settings

Hi,
Just give your project a try, and I see that panels (at least) declared in settings are not used when instanciating the bar.
I guess this line is wrong:
https://github.com/runcmf/runtracy/blob/master/src/RunTracy/Middlewares/TracyMiddleware.php#L67
It should be $cfg = $this->defcfg;
Regards.

Also, setting any panel to 0 in config does not have effect (panel is always enabled). As example, if you declare in the setting showTwigPanel => 0, it would suppose twig panel is enabled, but not shown per default.
Something like that shoudl do the trick:
-        if (isset($cfg['showTwigPanel'])) {
+        if (isset($cfg['showTwigPanel']) && $cfg['showTwigPanel']) {

I made changes locally to test; but as I'm not sure the way you had in mind to handle the whole config; I'm not sure about them. Lemme know if you want me to open a PR.

ping?


I think should always use $_SERVER['HTTP_HOST']

https://github.com/apereo/phpCAS/blob/6846e000570bb4a82e72ea00ff1e5a2b0ac78c6f/source/CAS/Client.php#L3588-L3592
my nginx conf

server {
listen      80 default_server;
server_name .mydomain.com;
....
}

then when I open https://first.second.mydomain.com/, $_SERVER['SERVER_NAME'] will be mydomain.com, and $_SERVER['HTTP_HOST'] will be first.second.mydomain.com.

Please have a look at #234. We already had some discussion in this topic.
Happy to hear your arguments aside from "make it work for my case" :-)

Closing this as duplicate


Using Kontena volumes fails with Docker v2 volume plugins

When using Docker volume plugins, Docker uses version/tag in volume driver information
$ docker volume inspect s3fs-test
[
    {
        "Driver": "rexray/s3fs:latest",
        "Labels": {},
        "Mountpoint": "/var/lib/docker/plugins/165a4e198e4ff02d1a3f1167cdfe132e046efa45db6a2384e03fdfd4f6e9a381/rootfs",
        "Name": "s3fs-test",
        "Options": {},
        "Scope": "global",
        "Status": {
            "availabilityZone": "",
            "fields": null,
            "iops": 0,
            "name": "s3fs-test",
            "server": "s3fs",
            "service": "s3fs",
            "size": 0,
            "type": ""
        }
    }
]

When deploying a stack, Kontena::Workers::Volumes::VolumeManager checks exisiting volumes without the version information and the comparison will fail causing:
GridServiceInstanceDeployer::ServiceError: Kontena::Workers::Volumes::VolumeManager::DriverMismatchError: Volume driver not as expected. Expected rexray/s3fs, existing volume has rexray/s3fs:latest

If you try to create volume with version information kontena volume create --driver rexray/s3fs:latest ... Kontena scheduler cannot find a proper node because version/tag information is not used in the comparison.

This is a bad interaction between #2061 and #2135. In #2061 we decided to explicitly split out the version and only use the driver name, and then in #2135 we only tested it with the un-versioned local driver.

@nevalla did you install driver as a docker plugin? If yes, workaround might be to set --alias at install.

No fix for 1.3 yet, bumping to 1.4. Might also be to a 1.3.2 if we want to.

Impossible to get v2 volume plugins to work because agent throws DriverMismatchError (even with --alias).
Tested with CoreOS Alpha & rexray/s3fs.
$ docker version
Client:
 Version:      17.05.0-ce
 API version:  1.29
 Go version:   go1.7.6
 Git commit:   89658be
 Built:        Wed Jun  7 23:07:34 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.05.0-ce
 API version:  1.29 (minimum version 1.12)
 Go version:   go1.7.6
 Git commit:   89658be
 Built:        Wed Jun  7 23:07:34 2017
 OS/Arch:      linux/amd64
 Experimental: false

Also spent few hours to get this to work, my notes:

target nodes pre-installed with driver as kontena still does not distribute plugins across grid (#2320)
installed using --alias, version of rexray/s3fs 0.9.1 has permissions issue as also noted on https://hub.docker.com/r/rexray/s3fs/, therefore 0.9.0 version is used

$ docker plugin ls
ID                  NAME                 DESCRIPTION               ENABLED
06dd4c96420f        rexray/s3fs:latest   REX-Ray for Amazon S3FS   true

a) creating kontena volume with :latest tag
$ kontena volume create  --scope grid --driver rexray/s3fs:latest adptw-test2-vol
$ kontena volume ls
NAME              SCOPE   DRIVER               CREATED_AT
adptw-test2-vol   grid    rexray/s3fs:latest   12 minutes ago

Deploy fails as plugin does not match node's plugins:
$ kontena stack ls
NAME  STACK  SERVICES_COUNT  STATE  PORTS
kraken@thingol:~/sandbox/stack-multiple-nodes                                                                                [09:24:21]$ kontena stack install
 [done] Creating stack test1
 [done] Triggering deployment of stack test1
 [fail] Waiting for deployment to start
        Cannot find applicable node for service instance production/test1/web1-1: Did not find any nodes with required volume drivers: ["rexray/s3fs:latest"]
 [error] RuntimeError : deploy failed
         See /home/kraken/.kontena/kontena.log or run the command again with environment DEBUG=true set to see the full exception

Target node info:
$ kontena node show smaug
smaug:
  id: VJDW:5QRW:BU45:ZMMB:4AZI:4RIT:LC2T:6DY6:QCE4:2EA7:6CQU:4GNE
  agent version: 1.3.0
  docker version: 17.05.0-ce
  connected: yes
  last connect: 2017-06-15T21:16:10.465+00:00
  last seen: 2017-06-23T07:26:40.177Z
  public ip: ***
  private ip: ***
  overlay ip: <IP_ADDRESS>
  os: Arch Linux
  kernel: 4.11.5-1-ARCH
  drivers:
    storage: overlay2
    volume: rexray/s3fs,local
  initial node: yes
  labels:
  stats:
    cpus: 2
    load: 1.32 0.51 0.26
    memory: 0.52 of 1.96 GB
    filesystem:
      - /var/lib/docker: 26.91 of 39.34 GB

b) creating kontena volume without :latest tag
$ kontena volume create  --scope grid --driver rexray/s3fs adptw-test2-vol
$ kontena volume ls
NAME              SCOPE   DRIVER        CREATED_AT
adptw-test2-vol   grid    rexray/s3fs   3 seconds ago

DriverMismatchError:
$ kontena stack install
 [done] Creating stack test1
 [done] Triggering deployment of stack test1
 [done] Waiting for deployment to start
 [fail] Deploying service web1
Deployment of service production/test1/web1 failed:
  - halting deploy of production/test1/web1, one or more instances failed
  - GridServiceInstanceDeployer::ServiceError: Kontena::Workers::Volumes::VolumeManager::DriverMismatchError: Volume driver not as expected. Expected rexray/s3fs, existing volume has rexray/s3fs:latest (on node smaug)

Alright, doing some local testing with CoreOS alpha, Docker 17.05 to try and understand how these plugin / volume driver names and versions work re  #2518 and #2526

The "unqualified" driver only works for either alias or latest version.

Right, it seems like the volume driver versions behave as the Docker image versions:  vieux/sshfs without a suffix just means vieux/sshfs:latest, both for docker volume create --driver and docker plugin *.
However, the Docker plugins have the added confusion of having a local suffix for the plugin name which is independent of the actual plugin version suffix, as per docker plugin install --alias (custom local name suffix that is different from the plugin version suffix) and docker plugin upgrade (keep the local name suffix, but upgrade the plugin version). This can be seen in the docker plugin inspect Name (taken from install --alias, stays the same on upgrade) vs PluginReference (taken from the actual install remote, changes on upgrade).
Additional it seems like Docker Hub plugins have similar updatable tags as images... the remote vieux:lastest plugin reference can be updated with a new plugin version? I assume this based on the default docker plugin upgrade vieux/sshfs behavior: Upgrading plugin vieux/sshfs:latest from vieux/sshfs:latest to vieux/sshfs:latest

OFC I also saw the Docker API doing some crazy stuff when testing...
Some commands run earlier to install plugins / create volumes:
$ docker volume create --driver vieux/sshfs --name sshfs-test -o sshcmd=core@localhost:/tmp^C
$ docker volume ls
DRIVER               VOLUME NAME
vieux/sshfs:latest   ssh-test1
vieux/sshfs:latest   ssh-test2
vieux/sshfs:latest   sshfs-test
$ docker plugin install vieux/sshfs:1.0
$ docker plugin install --alias vieux/sshfs:test vieux/sshfs:1.0

And then:
$ docker plugin ls
ID                  NAME                 DESCRIPTION               ENABLED
79b9052f8801        vieux/sshfs:latest   sshFS plugin for Docker   true
95ba6f52efb5        vieux/sshfs:1.0      sshFS plugin for Docker   true
a74005c94ffc        vieux/sshfs:test     sshFS plugin for Docker   true
$ docker plugin disable vieux/sshfs:latest
Error response from daemon: plugin vieux/sshfs:latest is in use
$ docker volume ls
vieux/sshfs:latest   ssh-test1
vieux/sshfs:latest   ssh-test2
vieux/sshfs:latest   sshfs-test
$ docker volume rm sshfs-test
sshfs-test
$ docker volume rm ssh-test1
ssh-test1
$ docker volume rm ssh-test2
ssh-test2
$ docker plugin disable vieux/sshfs:latest
Error response from daemon: plugin vieux/sshfs:latest is in use
$ docker volume ls
DRIVER              VOLUME NAME
vieux/sshfs:1.0     ssh-test1
vieux/sshfs:test    ssh-test1
vieux/sshfs:1.0     ssh-test2
vieux/sshfs:test    ssh-test2
vieux/sshfs:1.0     sshfs-test
vieux/sshfs:test    sshfs-test

No idea how it picked up multiple identically named copies of the same volume, one for each of the other installed plugin versions... I imagine this would confuse the agent.

I imagine this would confuse the agent.
Quite possibly. It also seems to confuse docker itself:

$ docker run --rm -ti -v wordpress.wp-s3fs:/data alpine sh
docker: Error response from daemon: error while mounting volume '/var/lib/docker/plugins/f0d5c0da35f2ce3beb2f692eb37c6ecef56fef9bbb040bbea645e795ff046275/rootfs': VolumeDriver.Mount: {"Error":"error executing xcli"}.

That's from a case where I had multiple versions of rexray/s3fs installed and had multiple identically named volumes.

VolumeDriver.Mount: {"Error":"error executing xcli"}.

That looks like the rexray/s3fs:0.9.1 permissions problem that @Edke also mentioned: https://github.com/codedellemc/rexray/issues/891

Documenting the design discussion on fixing this issue of dealing with the Docker plugin / volume driver versions for configuring the --driver to use for Kontena volumes.

I think we need to remove volume driver version specify. It's too confusing to users and also freezes plugin version (hard to install newer versions to fresh nodes without removing old installation first).

My understanding of the issue with driver versions here is something like the following:

node-1 docker plugin install rexray/s3fs:0.8.2
node-1 docker plugin upgrade rexray/s3fs:0.8.2 rexray/s3fs:0.9.1
node-2 docker plugin install rexray/s3fs:0.9.1

This results in the both nodes running the same 0.9.1 version, but the Docker volume driver on node-1 is still rexray/s3fs:0.8.2, whereas on node-2 it is rexray/s3fs:0.9.1. There would be no way to create/deploy the same Kontena volume to both nodes in this case.
The two approaches to avoiding this kind of foot-gun situation:

#2526 assuming that nodes only have a single plugin version installed, and all versions of the same plugin are compatible with eachother across nodes, have Kontena automatically use the installed Docker plugin version for each node
This will work in the above nightmare scenario of using docker plugin install rexray/s3fs:x.y.z and ending up with different volume driver versions on different nodes.

#2518 allow specifying an explicit kontena volume create --driver rexray/s3fs:stable version, or falling back to the implicit Docker rexray/s3fs:latest default for kontena volume create --driver rexray/s3fs
For the typical case of docker plugin install vieux/sshfs, which results in the same vieux/sshfs:latest plugin being installed on all nodes, this would work fine with kontena volume create --driver vieux/sshfs. You can use docker plugin upgrade vieux/sshfs on each node in turn to upgrade the plugin version without affecting the volume drivers used.
If you need to install specific versions of plugins, then it is a requirement to use custom local plugin versions using something like docker plugin install --alias rexray/s3fs:stable rexray/s3fs:0.8.2, to ensure that the plugin name is the same across nodes and versioned installs/upgrades. The local alias can then be used per kontena volume create --driver rexray/s3fs:stable.
You could also use upstream labels like docker plugin install rexray/s3fs:edge, or use multiple different local plugin aliases to install different (possibly incompatible?) versions of the same plugin across nodes.

The two approaches behave identically in the typical usecase of docker plugin install vieux/sshfs, and both approaches will have kontena volume create --driver vieux/sshfs use the installed vieux/sshfs:latest plugin.

fixed in #2526


Don't print the request to the console

Line 122 and 197 in GooglePlaces.swift print the request to the console and it includes the API key, which exposes the API key to anyone who can read the console.
This may happen in other files, but I only saw it in GooglePlaces.swift.

Yeah, this is definitely an issue. I will remove the debugPrint and update it


DOC: stats.mstats.sen_seasonal_slopes: add docstring

Reference issue
Closes gh-9119
What does this implement/fix?
There was no docstring for stats.mstats.sen_seasonal_slopes. This PR adds a docstring.
Additional information
Someday we'll probably want to move this over to stats, but in the meantime, even mstats functions should have a docstring.

We have been giving stats functions the ability to work with masked arrays. When that is done, there will be little need to maintain a separate mstats. So yes, then I'd suggest moving this one (and maybe others that don't currently exist in stats) to stats.

Thanks @tupui. Any other comments or does this look ok otherwise?

Thanks for the explanation, I understand better where we're going now. Aside from the CI it looked good.

Ugh I copy-pasted the example and ran it, but i must not have started a fresh session first.
What do you think of the names inter_slope and intra_slope? Should they be theil_sen_slope and kendall_slope or something based on those names? Should slope come first like slope_inter?

Ugh I copy-pasted the example and ran it, but i must not have started a fresh session first.
What do you think of the names inter_slope and intra_slope? Should they be theil_sen_slope and kendall_slope or something based on those names? Should slope come first like slope_inter?

I think inter and intra are better names that are easier to understand/parse than theil/Kendall. For someone not familiar with these, they would need to come back to the doc all the time to know what is what.
For the naming, I don't have a strong preference. Personally I tend to name things as you did. I don't think we have a convention for SciPy (maybe we should??).

thanks, @mdhaber !


[BUG] Vagrant Share with SSL is broken

Problem
e.g.: vagrant share --https 443 --name 'foobaru'
After opening https://foobaru.vagrantshare.com
Bad Request

Your browser sent a request that this server could not understand.
Apache/2.4.7 (Ubuntu) Server at foobaru.vagrantshare.com Port 443

Upstream issue mitchellh/vagrant#5493


Migrate to react-use-gesture

Summary

[ ] switch over from react-with-gesture to react-use-gesture

Motivation
react-with-gesture is depreciated, and we should make sure our dependencies are up-to-date so we stay current and also, more importantly, secure

The only place I can find react-with-gesture is in the yarn.lock file, should this issue be closed?

I’m pretty sure it’s being used for the WeeklyTracker / DailyTracker sliding components no? It was last I checked (not at computer now). If not, all that needs to be done would be to remove it entirely using ‘yarn remove’

I found react-use-gesture in the sliding parts for those components so i think were good, ill try it out and submit a pull request

Ah, nice - hadn’t noticed someone must’ve changed it when updating them at some point!


error: connection_data["phone"]

dear @p4kl0nc4t please help me
my code is:
`    # create the Client instance using create class method
whatsapp = await kyros.Client.create()
# do a QR login
qr_data, scanned = await whatsapp.qr_login()

# generate qr code image
qr_code = pyqrcode.create(qr_data)
print(qr_code.png('code.png', scale=1, module_color=[0, 0, 0, 128], background=[0xff, 0xff, 0xff]))
# print(qr_code.terminal(quiet_zone=0))`

after scan qr code, occur this error:
Traceback (most recent call last):   File "init.py", line 41, in <module>     asyncio.run(main())   File "/usr/local/lib/python3.8/asyncio/runners.py", line 43, in run     return loop.run_until_complete(main)   File "/usr/local/lib/python3.8/asyncio/base_events.py", line 612, in run_until_complete     return future.result()   File "init.py", line 26, in main     await scanned   File "/tmp/w/lib/python3.8/site-packages/kyros/client.py", line 103, in wait_qr_scan     self.phone_info = connection_data["phone"] KeyError: 'phone'

Well, that's bad. It seems like the WhatsApp Web API has quite changed. I am busy now, I will take a look on that later.

thnaks
On Tue, Jan 11, 2022 at 6:18 PM Faiz Jazadi @.***>
wrote:

Well, that's bad. It seems like the WhatsApp Web API has quite changed. I
am busy now, I will take a look on that later.
—
Reply to this email directly, view it on GitHub
https://github.com/p4kl0nc4t/kyros/issues/19#issuecomment-1010036231,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADL6RELGKNRHM2CKZ43HCRLUVQ7MJANCNFSM5LWK7CSA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

--
i digit web design ;)

If it helps, the value of connection_data on ln 102 of /path/to/venv/lib/python3.9/site-packages/kyros/client.py is:
{'type': 'upgrade_md_prod', 'version': '2.2126.11'}

At least for me.
The dictionary does not contain the phone key, hence the error. I am facing the same error.

I don't seem to be able to reproduce this issue.

@rijumone Your connection_data value looks bad. I think this issue is much more seriuous than I initially thought. The connection_data object should contain many important details as specified in here. The values especially the tokens are mandatory for kyros to be working properly.
Below is my connection_data value.

Checking this.

I can't reproduce the error. Is it related to this?

I can't reproduce the error. Is it related to this?

I think, yes! The message received (lacking the phone key) is identical and even my WA a/c is multi-device enabled as mentioned in the linked issue. Is your WA a/c multi-device enabled?
I am trying to check if I have access to a WA a/c with multi-device disabled.

I procured a device with a W/A a/c which has never been logged into W/A (at least I believe so, definitely never been logged in as a multi-device). Now, while the library itself does not throw any errors, the script just exits.
I am checking the code for the same as to why this is happening.
Attaching a screenshot of the same.

I have similar results when I scanned it using a multi-device enabled WhatsApp (produces no output, just exits). Try setting the logger mode to DEBUG.
logging.getLogger("kyros").setLevel(logging.DEBUG)

I found out that the WhatsApp websocket server closed the connection right after the QR scan. It seems that many things have to be adjusted. Baileys and whatsmeow both supports multi-device. I think they can be used as a reference.

I have similar results when I scanned it using a multi-device enabled WhatsApp (produces no output, just exits). Try setting the logger mode to DEBUG.
logging.getLogger("kyros").setLevel(logging.DEBUG)

I found out that the WhatsApp websocket server closed the connection right after the QR scan. It seems that many things have to be adjusted. Baileys and whatsmeow both supports multi-device. I think they can be used as a reference.

@p4kl0nc4t Apologies for the late response, last week has been incredibly busy.
I am still getting the same traceback.
Traceback (most recent call last):
  File "/home/rijumone/Kitchen/kyros/main.py", line 43, in <module>
    asyncio.run(main())
  File "/usr/lib/python3.9/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete
    return future.result()
  File "/home/rijumone/Kitchen/kyros/main.py", line 28, in main
    await scanned
  File "/home/rijumone/Kitchen/kyros/.venv/lib/python3.9/site-packages/kyros/client.py", line 102, in wait_qr_scan
    self.phone_info = connection_data["phone"]
KeyError: 'phone'

Printing connection_data on ln 101 in file: .venv/lib/python3.9/site-packages/kyros/client.py still outputs:
{'type': 'upgrade_md_prod', 'version': '2.2126.11'}

There is no phone key which is being accessed on ln 102.
I am checking the issue you linked previously. Do you have any suggestion?

@p4kl0nc4t I was able to have a successful login using this particular branch of this repo.
Though what a successful login means, I am still investigating. I was able to scan the QR code on my phone and it didn't error out. Terminal spewed out some debug text showing my contacts data.
This is in TS which I am not familiar with. Suggestions welcome.

@p4kl0nc4t I was able to have a successful login using this particular branch of this repo.
Though what a successful login means, I am still investigating. I was able to scan the QR code on my phone and it didn't error out. Terminal spewed out some debug text showing my contacts data.
This is in TS which I am not familiar with. Suggestions welcome.

I can help reviewing it, i have worked with TS. I'm using WA Business and it's working fine on my Android phone (I have testes develop branch). I don't have tested on WA multidevice, maybe with the support of multiple devices maybe there are some changes, but i don't think so because phone contains only the information of the real device (battery, os, wa version, model, manufactures) and the support of multiple device allow up to 4 instances of Web WA, but only 1 phone.
Maybe the field was removed in new versions of WA because phone can be offline or off. In any case i think that it can be ignored.


riscv64: Optimize bitselect+{i,f}cmp codegen

👋 Hey,
This is a followup to #6874 where f{min,max}_pseudo was removed and replaced it with bitselect+fcmp. Here we optimize that pattern into a mask generation instruction and vmerge.vvm that merges both inputs.
This allows us to avoid the quite long sequence for bitselect (4 instructions) and also vector mask expansion (1 instruction) in these patterns.
For tests here I'm relying mostly on wasmtimes wast testsuite.

This might be good for a rule like on x64 where much of the logic of bitselect can be skipped if the mask is known to have a particular pattern? (e.g. generated by icmp or fcmp)

Yeah, that's a neat way of de-duplicating these rules. I also think it might be worth copying that vconst_all_ones_or_zeros pattern into an egraphs rule, since it looks like we should be able to const propagate that

Oh this may not be applicable for riscv64, but on x64 at least there's no bitselect instruction so it uses the and/or/not/etc combo by default, but x64 does have lane-based select so if a bitselect's input mask is a comparison then the and/or/not/etc combo can be skipped in favor of a single lane-based instruction. I figured the same might be possible for riscv64 where bitselect could skip the combo of instructions and generate a single vmerge* (which I interpreted, perhaps mistakenly, as a lane-based instruction) after the normal instruction generated for the comparison. That way the rules for bitselect wouldn't generate icmp/fcmp instructions at all, instead the output of those instructions will be fed directly into vmerge.

since we have different ways of generating a icmp mask and fcmp mask.

On x64 I believe this is handled by bitselect not actually generating the icmp/fcmp, instead basically calling put_in_reg for the output of the icmp/fcmp which then will later use other lowering rules to generate the icmp/fcmp.

We can't skip generating the icmp/fcmp mask since in RISC-V the masks are 1 bit per lane, so we always need to make the conversion from 1 bit per bit, into 1 bit per lane. Is that what you meant?

Right yeah, my thinking was that like on x64 the lowering for bitselect wouldn't generate the cmp, only the vmerge, but because the mask of the bitselect is only pattern-matched on but we don't use the sub-operands that it would still generate the cmp naturally via other lowering rules.

Oh, okay so it's pretty much the same on RISC-V. We don't have a direct bitselect equivalent, we lower to and/or/not combo as well by default. vmerge is a lanewise select as you mentioned.

That way the rules for bitselect wouldn't generate icmp/fcmp instructions at all, instead the output of those instructions will be fed directly into vmerge.

Here's where this diverges. vmerge does not support the regular masks that are fed into bitselect. For a i8x16 we need a 16bit mask instead of a 128bit mask. (Or a 8 bit mask for i16x8, etc...)
In the regular icmp and fcmp instruction lowerings we do two things, first we generate the small mask (1 bit per lane), and then we do a second step of expanding that into a big mask.
In this PR gen_icmp_mask and gen_fcmp_mask only generate the small mask, that is compatible with vmerge. But we never expand it, which is what would happen if we let the regular icmp and fcmp instructions get lowered.
Does that make sense? I think I might be missing something, sorry if I am.

A different way to deduplicate these rules would be along the lines of maybe_uextend; riscv could use a maybe_bitcast extractor to have just one bitselect rule for each of icmp and fcmp, instead of two for each.
But I'm not sure that would be more broadly useful so I'm not sure it's worth doing. Just a thought in case it helps with something later.


Unresolved import when trying to use impl_header!

I am trying to implement a custom HTTP header using impl_header macro from hyper crate but it seems it cannot resolve the hyper::header module.
Here is my code:
#[macro_use] extern crate hyper;

use hyper::header;

struct CustomHeader(String);
impl_header!(CustomHeader, "name", String);

And here is the compiler error:
<hyper macros>:11:14: 11:20 error: unresolved import `header::HeaderFormat`. Maybe a missing `extern crate header`?
<hyper macros>:11 Result { use header:: HeaderFormat ; self . fmt_header ( f ) } } }
                           ^~~~~~
<hyper macros>:1:1: 11:67 note: in expansion of impl_header!
lib.rs:4:1: 4:45 note: expansion site
error: aborting due to previous error
Could not compile `macro_issue`.

Tried against master? I think a fix for this was merged in this morning (so
hasn't been published via cargo yet).
On Tue, Feb 17, 2015, 12:34 PM maximih<EMAIL_ADDRESS>wrote:

I am trying to implement a custom HTTP header using impl_header macro from
hyper crate but it seems it cannot resolve the hyper::header module.
Here is my code:
#[macro_use] extern crate hyper;
use hyper::header;
struct CustomHeader(String);
impl_header!(CustomHeader, "name", String);
And here is the compiler error:
:11:14: 11:20 error: unresolved import header::HeaderFormat. Maybe a missing extern crate header?
:11 Result { use header:: HeaderFormat ; self . fmt_header ( f ) } } }
^~~~~~
:1:1: 11:67 note: in expansion of impl_header!
lib.rs:4:1: 4:45 note: expansion site
error: aborting due to previous error
Could not compile macro_issue.
—
Reply to this email directly or view it on GitHub
https://github.com/hyperium/hyper/issues/323.

Seems parts of it was fixed on master but there is one issue left (check  use header::HeaderFormat; below) causing the whole macro to fail:
    impl ::std::fmt::Display for $from {
        fn fmt(&self, f: &mut ::std::fmt::Formatter) -> ::std::fmt::Result {
            use header::HeaderFormat;
            self.fmt_header(f)
        }
    }

<hyper macros>:11:14: 11:20 error: unresolved import `header::HeaderFormat`. Maybe a missing `extern crate header`?
<hyper macros>:11 Result { use header:: HeaderFormat ; self . fmt_header ( f ) } } }

I'm getting the exact same issue. Also tried against master, resulting in the same partial fix


Add completions for purge command

antidote purge should provide completions. antidote list --short along with --all flag should be the contents.

Closing as dupe of #97. Lots of completions work should get rolled into that one.


Remove test and other unnecessary files, from dist folder before publishing packages to npm

This was fixed on: #238


[fix](schema change) reduce memory usage in schema change process

pick
https://github.com/apache/doris/pull/30231
https://github.com/apache/doris/pull/36285
https://github.com/apache/doris/pull/33073

run buildall


update action page

https://app.zeplin.io/project/5c81bede826def625074c12c/screen/5cd79d99188bff348afc51d8

@nmhung1210  could you add what should be shown when click show more and its the only information we need to show?

@nmhung1210 could you add what should be shown when click show more and its the only information we need to show?

I think it should be the receipt details of the action. Like https://iotexscan.io/action/f2ac620ac37b4c3b6690ddd29f0d5b0c007411c72f6b230723cfee7eb6d4022b


Comments between doc comments and an enum variant are removed

Example:
#[derive(Debug, Clone, PartialEq, Eq)]
pub enum Bencoding<'i> {
    Str(&'i [u8]),
    Int(i64),
    List(Vec<Bencoding<'i>>),
    /// A bencoded dict value. The first element the slice of bytes in the source that the dict is
    /// composed of. The second is the dict, decoded into an ordered map.
    // TODO make Dict "structlike" AKA name the two values.
    Dict(&'i [u8], BTreeMap<&'i [u8], Bencoding<'i>>),
}

becomes
#[derive(Debug, Clone, PartialEq, Eq)]
pub enum Bencoding<'i> {
    Str(&'i [u8]),
    Int(i64),
    List(Vec<Bencoding<'i>>),
    /// A bencoded dict value. The first element the slice of bytes in the source that the dict is
    /// composed of. The second is the dict, decoded into an ordered map.
    Dict(&'i [u8], BTreeMap<&'i [u8], Bencoding<'i>>),
}

I realize that's probably not the best place for a TODO comment, but it really shouldn't be deleted completely.

The same thing happens with struct fields.


REPL crashes on Windows newlines

When I execute cargo run and type 1<ENTER> on the REPL, the parser crashes:
Welcome to the magnificent Rust Python 0.0.1 interpreter
>>>>> 1
thread 'main' panicked at 'Not impl Some('\r')', parser\src\lexer.rs:582:21

This is somehow related to Windows newlines (\r\n), so I'll try to come up with a PR which fixes this issue on Windows.

@wulmer Can this issue be closed since you implemented this functionality?

Sure. Was fixed in #15 .


DashMap locking

The DashMap seem to be somewhat lock-contended, see:
src/store.rs
1925-
1926-    // Get hash for expr, but only if it already exists. This should never cause create_scalar_ptr to be called. Use
1927:    // this after the cache has been hydrated. NOTE: because dashmap::entry can deadlock, it is important not to call
1928-    // hash_expr in nested call graphs which might trigger that behavior. This discovery is what led to get_expr_hash
1929-    // and the 'get' versions of hash_cons, hash_sym, etc.
1930-    pub fn get_expr_hash(&self, ptr: &Ptr<F>) -> Option<ScalarPtr<F>> {
1931-        self.hash_expr_aux(ptr, HashScalar::Get)

Originally posted by @huitseeker in https://github.com/lurk-lab/lurk-rs/pull/359#discussion_r1175448762
We currently have some caveats and infrastructure like the HashScalar enum to try to avoid DashMap locking.
I think we can use some of the fancier Dashmap methods like
https://docs.rs/dashmap/latest/dashmap/struct.DashMap.html#method.try_entry
    /// Advanced entry API that tries to mimic `std::collections::HashMap`.
    /// See the documentation on `dashmap::mapref::entry` for more details.
    ///
    /// Returns None if the shard is currently locked.
    pub fn try_entry(&'a self, key: K) -> Option<Entry<'a, K, V, S>> {
        self._try_entry(key)
    }

To dynamically check for locks and safely recover, instead of the places we use possibly locking DashMap::entry now:
    /// ensure that they are cached properly
    fn create_scalar_ptr(&self, ptr: Ptr<F>, hash: F) -> ScalarPtr<F> {
        let scalar_ptr = ScalarPtr::from_parts(ptr.tag, hash);
        let entry = self.scalar_ptr_map.entry(scalar_ptr);
        entry.or_insert(ptr);

        let entry2 = self.pointer_scalar_ptr_cache.entry(ptr);
        entry2.or_insert(scalar_ptr);
        scalar_ptr
    }

Closed in #351


Allow user to pass profile sample at the workflow level in UI

depends on #6183
Context
When users set up a profiler workflow in the UI they should be able to specify a sample percentage to apply for the profiler.

Fixed with #6292


feat: shell script to install prebuilt releases

Please confirm that your PR fulfills these requirements

[x] Multiple commits are squashed into one commit.
[x] The commit message follows Conventional Commits, which allows us to autogenerate release notes; e.g. fix(plugins/plugin-k8s): fixed annoying bugs
[x] All npm dependencies are pinned.

could we perhaps place this perhaps in bin/?

The bin folder means something in the npm world, nothing related to an installation script. In fact, the content of the bin folder needs to be pushed to npm, which is not the case here.
https://docs.npmjs.com/files/folders

tools sounds good!

I must have missed some context, but could you help me understand what problem you are trying to address? Maybe put in the PR description box would be helpful. Thank you!


chore: Update openedx brand dependency.

We've moved the dependency to the openedx scope so update the
dependency and re-build package-lock.json where applicable.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Configuration Persistence

Figure out a nice way to allow updates to the config that works across the different possible hosting providers

https://github.com/barnjamin/rareaf/pull/11 working on this


single & multi-select drop down list

Refer to https://github.com/solidify/jira-azuredevops-migrator/issues/40#issuecomment-482722481 and previous comment. I haven't seen any further actions on this topic. What I'd like to see is single & multi-select drop down lists, similar to https://marketplace.visualstudio.com/items?itemName=ms-devlabs.vsts-extensions-multivalue-control. Thanks for the good work up to now.
AB#5937

Hi, Would like this feature, any progress? Cheers

Any update on the multi-select drop down list

No, and we will probably not prioritize functionality outside of the Core ADO features for now :)

If it's not planning now, is there any option of  customizing it by own.
Pls share thought of how we can customize by self to own project, as in my project migration the multi select field is must to migrate it.

Migrate the raw data to a text field and then bulk copy (+transform) the contents of that field to your custom field? You may need a custom script solution if you cannot use ADO Queries


[Docs] add botcommand documentation

The documentation for the botcommand object should be rendered using docstrings

This issue needs to be closed.

It was resolved under issue #142


python_library: Use https url

Otherwise, it gets a redirect and fails to work

We are actually moving away from adding scripts to repository in favor of separate npm packages per scripts. See #1113 for details, and let us know if you have any questions about getting going with that!


vertx Pressure fault

version:3.41
pressure tool:wrk(https://github.com/wg/wrk)
java code:
public class Micro extends AbstractVerticle {
public static void main(String[] args) {
Runner.runExample(Micro.class);
}
@Override
public void start() throws Exception {
vertx.createHttpServer().requestHandler(req -> {
req.response().putHeader("content-type", "text/plain").end("Hello world!");
}).listen(8081);
}
}
script:
wrk -t1 -c5 -d10s http://localhost:8081/
error log:
io.vertx.core.net.impl.ConnectionBase
java.io.IOException: Connection reset by peer

You see that message whenwrk finishes and abruptly kills the connection. It is a notification that your peer (the client) just closed the connection before the server sent any data.

@pmlopes
5 connections into the 1, then no error
wrk -t1 -c1 -d10s http://localhost:8081/


build error - SEVERE: Cargokit BuildTool failed

Im getting this build error in my new project, and there is no error if i run Flutter run in  your example app from github( yet same error popsup if i run Flutter build apk ).
Running Gradle task 'assembleRelease'...
INFO: Precompiled binaries are disabled
INFO: Installing Rust target: armv7-linux-androideabi
INFO: Building android_adb_tool for armv7-linux-androideabi
SEVERE: ================================================================================
SEVERE: Cargokit BuildTool failed with error:
SEVERE: --------------------------------------------------------------------------------
SEVERE: External Command: rustup "run" "stable" "cargo" "build" "--manifest-path" "C:\Users\hfmmb\AppData\Local\Pub\Cache\hosted\pub.dev\android_adb_tool-0.0.2\rust\Cargo.toml" "-p" "android_adb_tool" "--release" "--target" "armv7-linux-androideabi" "--target-dir" "C:\Users\hfmmb\StudioProjects\adb_test2\build\android_adb_tool/build"
SEVERE: Returned Exit Code: 101
SEVERE: --------------------------------------------------------------------------------
SEVERE: STDOUT:
SEVERE: --------------------------------------------------------------------------------
SEVERE: STDERR:
SEVERE: Compiling proc-macro2 v1.0.82
SEVERE:    Compiling libc v0.2.154
SEVERE:    Compiling unicode-ident v1.0.12
SEVERE:    Compiling memchr v2.7.2
SEVERE:    Compiling autocfg v1.3.0
SEVERE: error: linker `link.exe` not found
SEVERE:   |
SEVERE:   = note: program not found
SEVERE:
SEVERE: note: the msvc targets depend on the msvc linker but `link.exe` was not found
SEVERE:
SEVERE: note: please ensure that Visual Studio 2017 or later, or Build Tools for Visual Studio were installed with the Visual C++ option.
SEVERE:
SEVERE: note: VS Code is a different product, and is not sufficient.
SEVERE:
SEVERE: error: could not compile `proc-macro2` (build script) due to 1 previous error
SEVERE: warning: build failed, waiting for other jobs to finish...
SEVERE: error: could not compile `libc` (build script) due to 1 previous error
SEVERE: --------------------------------------------------------------------------------
SEVERE: #0      runCommand (package:build_tool/src/util.dart:118:5)
SEVERE: #1      RustBuilder.build (package:build_tool/src/builder.dart:139:5)
SEVERE: <asynchronous suspension>
SEVERE: #2      ArtifactProvider.getArtifacts (package:build_tool/src/artifacts_provider.dart:68:25)
SEVERE: <asynchronous suspension>
SEVERE: #3      BuildGradle.build (package:build_tool/src/build_gradle.dart:32:23)
SEVERE: <asynchronous suspension>
SEVERE: #4      BuildGradleCommand.runBuildCommand (package:build_tool/src/build_tool.dart:62:5)
SEVERE: <asynchronous suspension>
SEVERE: #5      BuildCommand.run (package:build_tool/src/build_tool.dart:34:5)
SEVERE: <asynchronous suspension>
SEVERE: #6      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
SEVERE: <asynchronous suspension>
SEVERE: #7      runMain (package:build_tool/src/build_tool.dart:248:5)
SEVERE: <asynchronous suspension>
SEVERE: --------------------------------------------------------------------------------
SEVERE: BuildTool arguments: [build-gradle]
SEVERE: ================================================================================

Fixed in version 1.0.0


Matt Mastin DS Unit 1 Sprint 2

I'd like you to solve the stretch (one where you using matplotlib) and use seaborn, pandas, or another tool of your choice for practice.


chore: optimize gulp watchers

Reduce amount of watchers for gulp serve-and-sync-devguide by roughly 50% (~4900-ish to ~2500).
This should help with the 100% CPU usage #1082, on my machine it went from ~90% to ~50%.
At the end of the day we're still watching an insane amount of files, so it is a demanding process. Maybe using better watcher libs would also help.
/cc @wardbell @Foxandxss

merged and live


Title: Page View Time Series Visualizer

Is your feature request related to a problem? Please describe.
Machine Learning Basic Project to visualize time series data using a line chart, bar chart, and box plots.
Describe the solution you'd like.
You will use Pandas, Matplotlib, and Seaborn to visualize a dataset containing the number of page views each day on the given forum from 2016-05-09 to 2019-12-03. The data visualizations will help you understand the patterns in visits and identify yearly and monthly growth.
Describe alternatives you've considered.
GGplot, Altair, Geoplotlib, etc can be used as libraries.
Add any other context or screenshots about the feature request here.
No response

Will assign after you have successfully send PR .


Gain wrong when transforming Transfer Function to zeros, poles, gain

I believe gain of a continuous transfer function is wrong, when it is transformed to zpk representation.
In the documentation it is stated several times that numerator and denominator polynomials are defined in descending order. That means gain is given by the last entries.
Reproducing code example:

from scipy.signal.filter_design import tf2zpk

# Simple First Oder model with gain 1 and time constant 10
zeros, poles, gain = tf2zpk([1], [10, 1])

# Should be 1, but is 0.1
print(gain)

Scipy/Numpy/Python version information:

1.5.2 1.16.5 sys.version_info(major=3, minor=7, micro=4, releaselevel='final', serial=0)

1/10s+1 becomes 0.1/s+0.1 if you make the denominator a monic polynomial. So that's why you 0.1 as gain.

Here is an additional code block to see the issue visualized:
from scipy import signal
import matplotlib.pyplot as plt
lti = signal.lti([1.0], [10.0, 1.0])
t, y = signal.step(lti)
plt.plot(t, y)
plt.xlabel('Time [s]')
plt.ylabel('Amplitude')
plt.title('Step response for 1. Order Lowpass')
plt.grid()

The result clearly shows that gain is 1.0.
And transfer function 0.1/(s + 0.1) still has gain 1.0.

If the gain is 1 and you only have a single pole then you would get 1/s+0.1. K is the model gain not the DC gain.

Ah, ok. That makes sense. I didn't know there are two different gains and always thought about DC gain.
Thanks, for the help.


delete this repo

we package vault in mantl-packaging

congrats on that packaging, I still like plain rpm more, so I'd prefer to keep this.


Odata V4 reference service produces incorrect Metadata without alias/namespace

The http://services.odata.org/TripPinRESTierService/ service returns the following annotation:
...
				<EntitySet Name="Airlines" 					EntityType="Microsoft.OData.Service.Sample.TrippinInMemory.Models.Airline"> 					<Annotation Term="Org.OData.Core.V1.OptimisticConcurrency"> 						<Collection> 							<PropertyPath>Name</PropertyPath> 						</Collection> 					</Annotation> 				</EntitySet> ...
unfortunately, the used Org.OData.Core.V1 namespace is not referencing anywhere an alias or namespace in the schema.
This results, when retrieving the code with the latest available OData V4 Lib for Java, in the EdmAnnotationClass Code
  public EdmTerm getTerm() {     if (term == null) {       if (annotation.getTerm() == null) {         throw new EdmException("Term must not be null for an annotation.");       }       term = edm.getTerm(new FullQualifiedName(annotation.getTerm()));     }     return term;   }
that in debugging the annotation.getTerm()=="Org.OData.Core.V1.OptimisticConcurrency" but the term is then set to null from edm.getTerm() as it seems to check for available namespace/aliases in the schema and cannot find one.
So practically, this annotation does not exist for the currently latest Olingo-OData-Client-for-Java-4.3.0

I have cross created this issue in https://issues.apache.org/jira/browse/OLINGO-1062 as i am not sure, wether the service is not correct or the client should be more forgiving


Minor improvement on template and update dulwich requirement

All in title, reacted to one of Francesc's comments

Better late than never! Thanks.


Vite can not resolve path pre-bundling Swiper dependencies

Check that this is really a bug

[X] I confirm

Reproduction link
https://codesandbox.io/s/github/forchel/swiper-test
Bug description
We use Vue 3 with Typescript support, script setup and Swiper 7.3.2 in a project.
In our App, we include Swiper Types. If we want to run Vite the following error occurs:
`Pre-bundling dependencies:
vue
bootstrap
vue3-form-validation
@fortawesome/fontawesome-svg-core
vue-router
(...and 15 more)
(this will be run only when your dependencies or config have changed)

node_modules/swiper/types/index.d.ts:1:14: error: Could not resolve "./shared"
1 │ export * from './shared';
╵               ~~~~~~~~~~

node_modules/swiper/types/index.d.ts:2:34: error: Could not resolve "./swiper-class"
2 │ export { default as Swiper } from './swiper-class';
╵                                   ~~~~~~~~~~~~~~~~

node_modules/swiper/types/index.d.ts:3:14: error: Could not resolve "./swiper-events"
3 │ export * from './swiper-events';
╵               ~~~~~~~~~~~~~~~~~

node_modules/swiper/types/index.d.ts:4:14: error: Could not resolve "./swiper-options"
4 │ export * from './swiper-options';
╵               ~~~~~~~~~~~~~~~~~~

node_modules/swiper/types/index.d.ts:5:14: error: Could not resolve "./modules/public-api"
5 │ export * from './modules/public-api';
╵               ~~~~~~~~~~~~~~~~~~~~~~

error when starting dev server:
Error: Build failed with 5 errors:
node_modules/swiper/types/index.d.ts:1:14: error: Could not resolve "./shared"
node_modules/swiper/types/index.d.ts:2:34: error: Could not resolve "./swiper-class"
node_modules/swiper/types/index.d.ts:3:14: error: Could not resolve "./swiper-events"
node_modules/swiper/types/index.d.ts:4:14: error: Could not resolve "./swiper-options"
node_modules/swiper/types/index.d.ts:5:14: error: Could not resolve "./modules/public-api"
at failureErrorWithLog (C:\projects\tschingo\vue\node_modules\vite\node_modules\esbuild\lib\main.js:1493:15)
at C:\projects\tschingo\vue\node_modules\vite\node_modules\esbuild\lib\main.js:1151:28
at runOnEndCallbacks (C:\projects\tschingo\vue\node_modules\vite\node_modules\esbuild\lib\main.js:941:63)
at buildResponseToResult (C:\projects\tschingo\vue\node_modules\vite\node_modules\esbuild\lib\main.js:1149:7)
at C:\projects\tschingo\vue\node_modules\vite\node_modules\esbuild\lib\main.js:1258:14
at C:\projects\tschingo\vue\node_modules\vite\node_modules\esbuild\lib\main.js:629:9
at handleIncomingPacket (C:\projects\tschingo\vue\node_modules\vite\node_modules\esbuild\lib\main.js:726:9)
at Socket.readFromStdout (C:\projects\tschingo\vue\node_modules\vite\node_modules\esbuild\lib\main.js:596:7)
at Socket.emit (events.js:315:20)
at addChunk (internal/streams/readable.js:309:12)`
Expected Behavior
No problems resolving path.
Actual Behavior
No response
Swiper version
7.3.2
Platform/Target and Browser Versions
Windows, Chrome
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

reproduction link you provided doesn't replicate the issue

Please use this https://codesandbox.io/s/github/forchel/swiper-test or this repo https://github.com/forchel/swiper-test.git

for me it looks like issue on the vite(vite-ts) side, in Swiper package files everything is correct and in place, not sure why it can't resolve those types definitions

Add to vite.config
  optimizeDeps: {     exclude: ["swiper/vue", "swiper/types"],    },

Thank you for your solution. Works for me now.

I got this error when I added "importsNotUsedAsValues": "error" to my tsconfig.json and resolved it by importing the swiper types as type.
import type { Swiper as SwiperClass } from 'swiper/types';
There's no need to exclude swiper in vite.config

I got this error when I added "importsNotUsedAsValues": "error" to my tsconfig.json and resolved it by importing the swiper types as type. import type { Swiper as SwiperClass } from 'swiper/types'; There's no need to exclude swiper in vite.config

Thanks to your post I could resolve the same type of error (path resolve issue) in my no-typescript-js :)
Using vite-js and regular modules I had the same issue. Choosing a different name as Swiper when importing fixed the path-issue for me. I guess the export default in swiper.ems.js makes this possible.
import FadeSwiper, { Autoplay, EffectFade } from 'swiper';

const SwiperInstance = new FadeSwiper(selectorSwiper, {
    // ...options here
});

I got this error when I added "importsNotUsedAsValues": "error" to my tsconfig.json and resolved it by importing the swiper types as type. import type { Swiper as SwiperClass } from 'swiper/types'; There's no need to exclude swiper in vite.config

I spent some hours now figuring out why this kept failing. Apparently my auto-fix .eslintrc was configured to use inline-type-imports.
"@typescript-eslint/consistent-type-imports": [                     "error",                     {                         "fixStyle": "inline-type-imports"                     }                 ]
It appears it is required to convert the whole import to type as you just did.
Failing:
import { type Swiper } from 'swiper/types';
Working:
import type { Swiper } from 'swiper/types';


Krishna profile update

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

@eddiejaoude  Here I have followed all the steps see the screenshot.


:bug: Fix: Bug in unplugin

Description
Concise description of proposed changes
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

#1184  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @roninjin10 and the rest of your teammates on  Graphite


⚠ Bofrost.at has degraded performance

In dbf6bdf, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1174 ms

Resolved: Bofrost.at performance has improved in eafe26e after 8 minutes.


Electron-React ;npm run package' throws a Token error, unable to package.

Is there an existing issue for this?

[X] I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
[X] I have reviewed the documentation https://docs.sentry.io/
[X] I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?
Sentry Saas (sentry.io)
Electron SDK Version
4.15.1
Electron Version
25.0.1
What platform are you using?
Windows
Link to Sentry event
No response
Steps to Reproduce

Setup sentry as per the electron wizard
On your main.ts file initialize sentry
In CLI run 'npm run package'
We are using electron-react-boilerplate. Have only setup sentry for main.ts to replicate this.

Expected Result
Application to package.
For reference, the setup sentry.init works in development environment, but cannot seem to package into a production environment .
Actual Result
npm run package

package
ts-node ./.erb/scripts/clean.js dist && npm run build && electron-builder build --publish never

build
concurrently "npm run build:main" "npm run build:renderer"

[0]
[0] > build:main
[0] > cross-env NODE_ENV=production TS_NODE_TRANSPILE_ONLY=true webpack --config ./.erb/configs/webpack.config.main.prod.ts
[0]
[1]
[1] > build:renderer
[1] > cross-env NODE_ENV=production TS_NODE_TRANSPILE_ONLY=true webpack --config ./.erb/configs/webpack.config.renderer.prod.ts
[1]
[0] ERROR in ./src/main/main.ts + 219 modules
[0] Unexpected token (400:99)
[0] |     // parse node.js major version
[0] |     // Next.js will complain if we directly use `proces.versions` here because of edge runtime.
[0] |     const [major] = __WEBPACK_MODULE_REFERENCE__145_5b22474c4f42414c5f4f424a225d_call_asiSafe1__._ ).process.versions.node.split('.').map(Number);
[0] |
[0] |     // allow call extractOriginalRoute only if node version support Regex d flag, node 16+
[0] while analyzing module<EMAIL_ADDRESS>for concatenation
[0]
[0] webpack compiled with 1 error
[0] npm run build:main exited with code 1
[1] npm run build:renderer exited with code 0

Hi, this looks like a bug in your webpack configuration. There is indeed a syntax error in the output in the terminal but this is not code that is in our npm package. Please check that you don't have webpack plugins that do anything funky.

@lforst thanks for swift reply. I will have a look. This only happens after I've installed sentry, for reference.

We have an electron-react-boilerplate example that is built and tested for our integration tests although this does not test a packaged build:
https://github.com/getsentry/sentry-electron/tree/master/examples/electron-react-boilerplate

@timfish yep used as reference, works fine in dev. It's on package it fails

As far as I can see, the package script just runs the build and then runs Electron builder to package the app.
It looks like the following error comes from this code:
https://github.com/getsentry/sentry-javascript/blob/679e149495190b682131aa1575cb96c5f4efcd2a/packages/tracing-internal/src/node/integrations/express.ts#L491
[0] |     // Next.js will complain if we directly use `proces.versions` here because of edge runtime.
[0] |     const [major] = __WEBPACK_MODULE_REFERENCE__145_5b22474c4f42414c5f4f424a225d_call_asiSafe1__._ ).process.versions.node.split('.').map(Number);

Our ERB example does not use Next.js. Do you have an example repository showing exactly the code you are trying to compile?
If you're using Next.js, how are you using the server side stuff with Electron?

Hi @timfish
We aren't using next.
If I change the const[major] variable to directly reference the major node version number, being 18, it packages fine.
if (!lrp) {
// parse node.js major version
// Next.js will complain if we directly use proces.versions here because of edge runtime.
// const [major] = (GLOBAL_OBJ ).process.versions.node.split('.').map(Number); // Changing this
cont[major] = 18; // ** // To this**
// allow call extractOriginalRoute only if node version support Regex d flag, node 16+
if (major >= 16) {

This is definitely a bandaid solution I assume as we would like to be exposed to all new versions of sentry.

Hi I'm working with @finnlaymfarmor. Your build seems to work with npm run build. We are attempting npm run package per the ERB boilerplate. Sentry installed with the wizard using webpack config as prompted. I can't see anything related to sentry in your webpack config files, which method of installation have you used? Thanks.

@ofarnill What exact wizard did you use to set up Sentry? The examples were last touched 2 years ago and the wizard most certainly is newer than that.

npx @sentry/wizard@latest -i sourcemaps

Then following the prompts for webpack config. Thanks.

The wizard will not set up the entire SDK for you, just how to upload sourcemaps for a given setup. I honestly 100% think this  not an issue within the SDK, our Wizard, or the example, but rather a webpack bug. https://github.com/getsentry/sentry-javascript/issues/10048 reports a similar issue. Would you mind raising this over at https://github.com/webpack/webpack? Thank you!

Have opened an issue over at webpack. Will let you know if resolved. Thanks for your help.

Closing for clean-up. Please open a new issue if this still applies. Thanks!


qa: Remove MixedTypeRector exception in rector.php

This no longer triggers and thus is not required to be skipped.

Thanks for the contribution!

Is it too annoying needing to wait for me?

It is mostly to ease your task. 😛
I get the company-time thing, no worries!

It is mostly to ease your task. 😛

All good from my side, doing this kind of stuff is easy enough to do for me and this amount of PRs I currently send is a little unusual :innocent:


Sorry I have a question on how to export videos

Windows 10, just started using the app
I am trying to figure out how to export videos. I can only export to images. I watch a video on YouTube and the users installers had a config file and .yaml files that I don't have. I am missing something here and I am not sure what. I downloaded ffmpeg because some of the posts mentioned that and I have no idea what to do with it.
Sorry and thanks for your help.

I would also like to know how to use

Install ffmpeg and open up PowerShell in the directory with the images that are named exportsequence_XXX with XXX being the numbers.
> ffmpeg -framerate 30 -i exportsequence_%10d.jpg  -c:v libx264 -pix_fmt yuv420p analysis.mp4


[Bug]: UI neverending startup

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Describe the bug and reproduction steps
I install the actual prepared container. Everything works fine. Then I access the docker container (ubuntu).
The UI Page of OpenHands appears. On the bottom I see the red 'sign' that it is starting up. This never ends.
In case I write sth in the chat field it is not sent. Not log output.
Then I tried downloading an building from source. Also does not work. There are access issues within the docker container.
OpenHands Installation
Docker command in README
OpenHands Version
latest
Operating System
Linux
Logs, Errors, Screenshots, and Additional Context
no log output

Assuming you are running the docker command from the README, in your terminal you should be getting some output. Are you able to attach the output you get in your terminal when the UI is stuck in "Starting Up..." please?

I think there may be an issue with Linux. Seeing quite a few issues with running OpenHands from users using Linux.
Hoping someone with Linux can take a look.


Import Error: No module named request

Hi there
When running this I get the error:
Traceback (most recent call last):
File "/usr/local/bin/wayback-machine-scraper", line 5, in
from wayback_machine_scraper.main import main
File "/usr/local/lib/python2.7/site-packages/wayback_machine_scraper/main.py", line 7, in
from .mirror_spider import MirrorSpider
File "/usr/local/lib/python2.7/site-packages/wayback_machine_scraper/mirror_spider.py", line 7, in
from scrapy_wayback_machine import WaybackMachineMiddleware
File "/usr/local/lib/python2.7/site-packages/scrapy_wayback_machine/init.py", line 3, in
from urllib.request import pathname2url
ImportError: No module named request
It looks like it's pointing to Python 2.7...but when I type "python --version" I get Python 3.7. Shouldn't this run with either though? Thanks.

If you have both Python2 and Python3 installed, you may need to use pip3 instead of pip to install. What is your output for ls -l /usr/bin | grep python?

It looks like Python 2 support was broken in sangaline/scrapy-wayback-machine#2. I just published a fix in sangaline/scrapy-wayback-machine#6.


Unmodel issue....

while i was extracting PUBG mobile made on unreal engine 4 Mostly all files gets unmodeled but when i started to unmodel static mesh of buildings the application crashed and said bad memory allocation i tried every version of UE1/UE2/UE3 and UE4. I litraly extracted whole game file except the Buildings... help me out with the same!

Ask on the forum (in PUBG Mobile thread) please. May be the issue is already there, and may be someone already solved it.
The Issue board on github is for something else, not about compatibility with games.

I didn't found related one.. actually it is mostly  related  unmodel software.. that why it is saying bad memory allocation even if more than half of the files are unmoled by UE 4.18 version?

Crash usually means that settings are wrong or game is not supported.


Rewrite ecosystem checks and add ruff format reports

Still in progress. I've commented out massive parts of CI and pinned to specific versions for testing! Will revert before review.
Closes #7239

Refactors scripts/check_ecosystem.py into a new Python project at python/ruff-ecosystem

Includes documentation now
Provides a ruff-ecosystem CLI

Fixes bug where ruff check report included "fixable" summary line
Adds truncation to ruff check reports

Otherwise we often won't see the ruff format reports
The truncation uses some very simple heuristics and could be improved in the future

Identifies diagnostic changes that occur just because a violation's fix available changes

We still show the diff for the line because it's could matter where this changes, but we could improve this

Adds support for JSON ecosystem check output

I added this primarily for development purposes

When caching repositories, we now checkout the requested ref
Adds ruff format reports, which format with the baseline then the use format --diff to generate a report

Known problems

Since we must format the project to get a baseline, the permalink line numbers do not exactly correspond to the correct range

This looks... hard. I tried using git diff and some wonky hunk matching to recover the original line numbers but it doesn't seem worth it. I think we should probably commit the formatted changes to a fork or something if we want great results here. Consequently, I've just used the start line instead of a range for now.

I don't love the comment structure — it'd be nice, perhaps, to have separate headings for the linter and formatter.

However, the pr-comment workflow is an absolute pain to change because it runs separately from this pull request so I if I want to make edits to it I can only test it via manual workflow dispatch.

Lines are not printed "as we go" which means they're all held in memory, presumably this would be a problem for large-scale ecosystem checks
We are encountering a hard limit with the maximum comment length supported by GitHub. We will need to move the bulk of the report elsewhere.

Future work

Update ruff-ecosystem to support non-default projects and check_ecosystem_all.py behavior
Remove existing ecosystem check scripts
Add preview mode toggle (#8076)
Add a toggle for truncation
Consider parsing JSON output of Ruff instead of using regex to parse the text output
Links to project repositories should use the commit hash we checked against
When caching repositories, we should pull the latest changes for the ref

very clean code!

That means a lot if comes from @konstin !


Add Forgot Password Functionality

Can I work on this task?

Can I work on this task?

Sure! Go ahead. I've assigned you this issue


Extensions are randomly uninstalling

VSCode Version: 1.19.3 (and the previous two versions, I think)
OS Version: Ubuntu 16.04

My extensions are occasionally uninstalling randomly. The most recent being Bracket Pair Colorizer. I noticed the brackets weren't colorizing, and I knew immediately the extension must have uninstalled, as it's happened before with Live Server, and Prettier. So, I checked the extensions, and indeed, it was uninstalled.
I just looked at my extensions, and once again, Prettier and Live Server are uninstalled. :/
Thanks!
EDIT: After I reinstalled Prettier, Bracket Pair Colorizer uninstalled, again. It happened after clicking "reload" after reinstalling Prettier.

my Prettier extension was automatically uninstalled too
VSCode Version: 1.20.1
OS Version: win10

Fixed in 1.21
Duplicate of https://github.com/Microsoft/vscode/issues/44471


PubSub subscription stops delivering messages to CloudFunction

Using CloudFunctions with client library "google-cloud/pubsub" version 0.14.5
I have CloudFunctions which when triggered connect to a subscription and pull messages. Sometimes when a CloudFunction is triggered it connects to a subscription but sees no messages. The CloudFunction stays in this "blocked" state until it is redeployed after which it sees all the past messages and processes them. During the time the CloudFunction is in the "blocked" state I can run local debug code in node.js v6.11.3 and it connects to the same subscription and sees messages. I have been using this same code for > 2 months and this issue started two weeks ago. The issue is intermittent.
Attached are the logs
cloud-function.log
-> A triggered CloudFunction seeing no messages when pulling from a subscription
local-function.log
-> Almost the same code run locally and seeing messages when pulling from a subscription
cloud-function-after-deploy.log
-> Re-deploy the CloudFunction
cloud-function-deploy.log
-> CloudFunction sees messages when pulling from a subscription
Thanks in advance for any help
cloud-function-after-deploy.log
cloud-function-deploy.log
cloud-function.log
local-function.log

There is also a problem sending messages to PubSub from a CloudFunction, sending the messages by running the same code locally through node.js works fine. I have tried deleting all functions, subscriptions and topics and re-creating them but the problem remains the same. I have another project with the same code that where sending messages is ok but pulling is intermittent. I guess this is some routing issue that surfaces from time to time...

BTW the last time this happened was the same day of the week, I remember because we had a demo that failed :)

This is obviously nothing to do with the google client library so closing this issue


Replace Ignored<T> with CommandNotReplicateExt::not_replicate

Now Ignored<T> is private and renamed into NotReplicate<T>. Now CommandNotReplicateExt::not_replicate should be used instead.

Suggestions are welcome, especially about docs and naming.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (ba23e90) 90.50% compared to head (345a17d) 90.61%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #147      +/-   ##
==========================================
+ Coverage   90.50%   90.61%   +0.10%
==========================================
  Files          19       20       +1
  Lines        1148     1161      +13
==========================================
+ Hits         1039     1052      +13
  Misses        109      109

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


WIP: ARROW-11608: [CI] Fix turbodbc nightly

@github-actions crossbow submit test-conda-python-3.7-turbodbc-master

@github-actions crossbow submit test-conda-python-3.7-turbodbc-master

@github-actions crossbow submit test-conda-python-3.7-turbodbc-master

@github-actions crossbow submit test-conda-python-3.7-turbodbc-master

@github-actions crossbow submit test-conda-python-3.7-turbodbc-master

@github-actions crossbow submit test-conda-python-3.7-turbodbc-*

The failure in Integration / AMD64 Conda Integration Test should be unrelated. Thus this is ready for a merge.