text:
Initializing the model from state_dict

I would like to only modify certain layers of a nn model. Example way of doing so:
from transformers.models.mixtral.modeling_mixtral import *
from hqq.core.quantize import *

def hqq_init(self, config: MixtralConfig):
    nn.Module.__init__(self)
    self.ffn_dim = config.intermediate_size
    self.hidden_dim = config.hidden_size

    qcfg = BaseQuantizeConfig(nbits=2, group_size=64)
    self.w1 = HQQLinear(nn.Linear(self.hidden_dim, self.ffn_dim, bias=False), quant_config=qcfg)
    self.w2 = HQQLinear(nn.Linear(self.ffn_dim, self.hidden_dim, bias=False), quant_config=qcfg)
    self.w3 = HQQLinear(nn.Linear(self.hidden_dim, self.ffn_dim, bias=False), quant_config=qcfg)
    self.act_fn = ACT2FN[config.hidden_act]

MixtralBlockSparseTop2MLP.__init__ = hqq_init

^ Sparse layers of MoE have high level of redundancy unlike dense layers, so only quantizing them makes sense.
Which means that we need to convert the respective weight matrices to quantizised form and load them into the model:
from safetensors import safe_open
from hqq.core.quantize import Quantizer

tensors = {}
for i in range(1, 20):
    path = MODEL_DIR + f"/models--mistralai--Mixtral-8x7B-Instruct-v0.1/snapshots/1e637f2d7cb0a9d6fb1922f305cb784995190a83/model-{i:0>{5}}-of-00019.safetensors"

    with safe_open(path, framework="pt", device="cpu") as f:
        for k in f.keys():
            tensor = f.get_tensor(k)
            if "expert" in k:
                print("quantizising:", k)
                W_q, meta = Quantizer.quantize(tensor, nbits=2, group_size=64)
                tensors[str(k).replace(".weight", ".W_q")] = W_q
                # tensors[str(k).replace(".weight", ".meta")] = meta
                # meta is not marked as a parameter/tensor, so can't load it using nn.Module._load_from_state_dict
                # HQQLinear(nn.Module) doesn't overwrite the method either to a suitable one
            else:
                tensors[k] = tensor

config = MixtralConfig()
modified_model = MixtralForCausalLM(config=config)

modified_model.load_state_dict(tensors)

Which results in a model:
MixtralForCausalLM(
  (model): MixtralModel(
    (embed_tokens): Embedding(32000, 4096)
    (layers): ModuleList(
      (0-31): 32 x MixtralDecoderLayer(
        (self_attn): MixtralSdpaAttention(
          (q_proj): Linear(in_features=4096, out_features=4096, bias=False)
          (k_proj): Linear(in_features=4096, out_features=1024, bias=False)
          (v_proj): Linear(in_features=4096, out_features=1024, bias=False)
          (o_proj): Linear(in_features=4096, out_features=4096, bias=False)
          (rotary_emb): MixtralRotaryEmbedding()
        )
        (block_sparse_moe): MixtralSparseMoeBlock(
          (gate): Linear(in_features=4096, out_features=8, bias=False)
          (experts): ModuleList(
            (0-7): 8 x MixtralBlockSparseTop2MLP(
              (w1): HQQLinear()
              (w2): HQQLinear()
              (w3): HQQLinear()
              (act_fn): SiLU()
            )
          )
        )
        (input_layernorm): MixtralRMSNorm()
        (post_attention_layernorm): MixtralRMSNorm()
      )
    )
    (norm): MixtralRMSNorm()
  )
  (lm_head): Linear(in_features=4096, out_features=32000, bias=False)
)

But the resulting model doesn't have the correct meta parameters.
I see that the HQQLinear has a method load_state_dict, but it doesn't get called. By default _load_from_state_dict gets called instead. Additionally, I'm not entirely sure the weight matrices get loaded in properly either
Respective model serialization and deserialization could be done like this instead then:
path = EXPERIMENTS_DIR + f"/models/Mixtral-8x7B-Instruct-v0.1-HQQ-2bit"
modified_model.save_pretrained(path)

tokenizer = AutoTokenizer.from_pretrained("mistralai/Mixtral-8x7B-Instruct-v0.1", revision="1e637f2d7cb0a9d6fb1922f305cb784995190a83")
model = AutoModelForCausalLM.from_pretrained(path, torch_dtype=torch.float16).to("cuda")

 self.w1 = HQQLinear(nn.Linear(self.hidden_dim, self.ffn_dim, bias=False), quant_config=qcfg)

This is not gonna work because it's basically quantizing the randomly generated weights from nn.Linear.
You can simply give the experts layer ids the 2-bit config, and use None for the layers you don't want to quantize. You can follow the example here:
https://huggingface.co/mobiuslabsgmbh/Mixtral-8x7B-Instruct-v0.1-hf-attn-4bit-moe-2bitgs8-metaoffload-HQQ
If you want to use load_state_dict you need to feed it a state dict compatible with HQQLinear which means W_q and meta, they should come from the post-quantized corresponding nn.Linear. That's how quantized model loading works.
If you want to have your own custom logic of quantizing the weights. For example, you want to load the weights from disk for each layer, then quantize, you can simply inherit from BaseHQQModel and override the quantize_model call: https://github.com/mobiusml/hqq/blob/master/hqq/models/base.py#L199-L248
That would be the equivalent of initializing the model.
Hope this helps!

Closing since this has been merged, thank you!

authors: envomp mobicham

repo: mobiusml/hqq


text:
集成React 章节纠错

Hi, 在React集成章节中，中文文档有几处地方翻译有误或者欠佳，我这边做了几处修改。
例如  local observables 或 locally observable state 误翻译成 全局可观察对象/全局地可观察状态，应当为本地可观察对象或可观察状态
第一次给Mobx中文文档提交PR，水平有限，难免出现差错，敬请指正。感谢。

@iChenLei  Hi，给 《React集成》章节纠正了一些错误，烦请帮忙Review一下~

source: gharchive/pull-request

license: MIT

license_type: permissive

license_source: github-api


text:
Console logging gets extremely mixed up after a retry

I'm running a very long test suite that sends many requests to our API, so it's nice to be able to log what request I'm sending and what the response is for debugging purposes if a test fails. All goes well if I don't allow retries. Everything stays in order and everything gets printed. However, if I turn on any retrying using this.retries(1) the logging is fine until it hits a retry. Then it starts getting really weird. It continues logging most(some of the console.log statements appear to never be printed), but it puts some out of order and no longer splits into the separate suites. It begins printing everything into one suite until it randomly moves on to the next and is completely out of order. In addition, it doesn't actually print the error that caused the retry until ~3 tests after it happened.
My best guess as to what is causing this is that it has something to do with using promises and/or a setTimeout function in the area that gets retried.

@brubakbd Can you provide an example suite that will reproduce this?

require('mocha');
var variables = require('./../variables.js');
var rules = require('./../rules.js');
var async = require('async');

describe("overall suite", function(){
    this.retries(2);
    it("test one",function(){
        console.log("test one-1");
        console.log("test one-2");
        return new Promise(function(resolve, reject){
            setTimeout(function(){
                resolve("Test one promise response")
            },1000);
        })
            .then(function(resp){
                console.log(resp);
                console.log("Finished test one");
            });
    });
    it("test two",function(){
        console.log("test two-1");
        console.log("test two-2");
        return new Promise(function(resolve, reject){
            setTimeout(function(){
                resolve("Test two promise response")
            },1000);
        })
            .then(function(resp){
                console.log(resp);
                console.log("Finished test two");
            });
    });
    var i = 0;

    it("test three",function(){
        console.log("test three-1");
        console.log("test three-2");
        return new Promise(function(resolve, reject){
            setTimeout(function(){
                if(i===2)
                    resolve("Test three promise response")
                else{
                    reject("i = "+i);
                }
            },1000);
        })
            .then(function(resp){
                console.log(resp);
                console.log("Finished test three");
            });
    });

    it("test four",function(){
        console.log("test four-1");
        console.log("test four-2");
        return new Promise(function(resolve, reject){
            setTimeout(function(){
                resolve("Test four promise response")
            },1000);
        })
            .then(function(resp){
                console.log(resp);
                console.log("Finished test four");
            });
    });

    it("test five",function(){
        console.log("test five-1");
        console.log("test five-2");
        return new Promise(function(resolve, reject){
            setTimeout(function(){
                resolve("Test five promise response")
            },1000);
        })
            .then(function(resp){
                console.log(resp);
                console.log("Finished test five");
            });
    });
});

When looking at the console log for test one I see:
test one-1
test one-2
Test one promise response
Finished test one

Test two:
test two-1
test two-2
Test two promise response
Finished test two

First attempt of test three:
test three-1
test three-2test three-1
test three-2test three-1
test three-2test four-1
test four-2
Test four promise response
Finished test fourtest five-1
test five-2
Test five promise response
Finished test five
Process finished with exit code 1

Test four has nothing
Test five has nothing
Second iteration of test three has nothing
3rd iteration of test tree that fails:
Error: the string "i = 0" was thrown, throw an Error :)

Also, should the test three retries be running at the end? It appears that it fails once, then goes to four and five, then comes back to three for the retries. I couldn't find any documentation on what Mocha's retry is supposed to do.

someone should review this

Closing this as I am unable to reproduce with the latest mocha, feel free to re-open if this issue persists.

source: gharchive/issue

authors: Bamieh boneskull brubakbd

repo: mochajs/mocha


text:
Build gh pages with jekyll

This is an attempt to merge the pull requests by @boneskull and @rstacruz in #1729 and #1726. Discussed in #1640 and #1657.
I think this is the best of both worlds :smile: but please let me know what you guys think.

I've cherry-picked and rewrote all commits that occured on the gh-pages branch but were not included in the branch off point where @boneskull started work on this branch. A clean merge into gh-pages should now be possible, without loss of any work.

Also resolved issue #1743

And resolved #1738

See https://jbnicolai.github.io/mocha for a demo.

-1 on changing the license there. i think that says more about the project as a whole than that particular page.

-1 on changing the license there. i think that says more about the project as a whole than that particular page.

I'm not sure what you mean.  The license is for the site...

yeah updated my comment, just mention that the project is mit somewhere on it

@travisjeffery OK, fair enough.

yeah updated my comment, just mention that the project is mit somewhere on it

Agree with you there :)

@jbnicolai let me/us know if that doesn't make sense.  The CC says "mochajs.org is licensed CC..." but then thereafter we should mention Mocha is licensed MIT.

@boneskull yep, was in the middle of a too long response on copyright nuances, but I think we all agree. Let me update that line.

imo we could just get rid of that copyright for the page at the bottom, looking at other open source projects and they don't have something similar.

@travisjeffery I liked @boneskull's proposal to go with CC, which would mean people could use the source for other projects.

@travisjeffery If there's no license on the site, the site could be construed to not be released under any license, which means while it's "open source", you wouldn't be allowed to use it or copy it in any way.  IMO, it's better to be explicit.

afaik we can't really re-license something like this. since this page now has many different authors, we'd have to get each contributor to the page's consent to do so. here's a podcast with postsharp talking about when they did it: http://hanselminutes.com/286/startup-series-postsharp-from-open-source-to-commercial-business-with-gael-fraiteur

@travisjeffery we do the same relicensing for every pull-request we accept. The work someone presents is technically under their copyright, and we never ask them or make them sign anything when we accept it. Then we present the entire body of work under our original MIT licence.
Of course, I think this is a non-issue - although organisations like https://github.com/google do make you explicitly sign their contributers licence agreement for just this reason.

Actually, how about I revert the chances I made to the footer and we discuss this in an other issue?
That way we can move on merging this :)

We need to leave the "license" as-is; it's not actually licensed.

© 2011 TJ Holowaychuk. All rights reserved.

@jbnicolai after we revert the license change(s) let's merge this plz

@boneskull that line has already been reverted. Merge-time!

authors: boneskull jbnicolai travisjeffery


text:
build(ESLint/Git): Ignore JSDoc output directory

Description of the Change
Prettier-ESLint keeps busying itself with the JSDoc output directory, spewing hundreds of errors.
This tells both ESLint and Git to ignore the directory.
Benefits
Allows local use of JSDoc without it affecting any potential commit.
Possible Drawbacks
None
Applicable issues
semver-patch

Coverage increased (+0.09%) to 90.463% when pulling 723167b2decdaf43f6d7ebfa9717e8e6838ee5ba on plroebuck:lintstaged into b9b3ac0122347df9b9699413d2025541674c929f on mochajs:master.

authors: coveralls plroebuck


text:
Reduce object-bits for test to avoid OOM

Kani often runs out of memory on tests/expected/function-contract/history/stub.rs when running the regressions. In particular, quadruple_harness consumes over 9 GB of memory. This PR reduces the object bits for this test to 8 to avoid OOM issues. This brings down memory usage to ~125 MB.
Before:
$ /usr/bin/time -v kani -Zfunction-contracts stub.rs --harness quadruple_harness
        Maximum resident set size (kbytes): 9136036

After:
$ /usr/bin/time -v kani -Zfunction-contracts stub.rs --harness quadruple_harness --enable-unstable --cbmc-args --object-bits 8
...
        Maximum resident set size (kbytes): 125172

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

I wonder if we should tweak with the current default

I tried tweaking the test, but eventually gave up. For example, switching from 32-bit integers to 16 or 8-bits does not decrease the memory usage much.
I'm open to suggestions.

authors: celinval zhassan-aws

repo: model-checking/kani


text:
fix template bug2

add copyright
fix template bug

fix multi-node DDP bug

repo: modelscope/swift


text:
PERF: _propagate_index_objs can be implemented to compute caches

Place:
https://github.com/modin-project/modin/blob/aeff7ac70162b53f8c6178f048498c2ee9bd631b/modin/core/dataframe/pandas/dataframe/dataframe.py#L515
Most likely, we will have to change the interface of add_to_apply_calls function so that it passes caches to the partition constructor.

Same applicable to apply. Working on this in https://github.com/YarShev/modin/commit/adb38ca15eb70d396fed7bd45bde86e71a27fb63.

authors: YarShev anmyachev

repo: modin-project/modin


text:
Head tail performance

What do these changes do?
Fixes performance bugs from #37, no longer concatenating the full column into memory

Related issue number
#37

[x] passes git diff upstream/master -u -- "*.py" | flake8 --diff

Is this ready to be merged?

@simon-mo It is ready, yes. As long as there are no changes needed upon review.

Just to give a sense about the performance:
On a 500MB file, previously head took 7 seconds, every time.
Now head takes 2-300ms on the same file

authors: devin-petersohn simon-mo


text:
DOCS-#4027: Add GIF images and chart to Modin README demonstrating speedups

Signed-off-by: Naren Krishna naren@ponder.io

What do these changes do?
Add a GIF comparing Modin vs. Pandas execution on Taxi dataset to the Modin README. Related to #4027.

[ ] commit message follows format outlined here
[ ] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[ ] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[ ] signed commit with git commit -s
[ ] Resolves #?
[ ] tests added and passing
[ ] module layout described at docs/development/architecture.rst is up-to-date
[ ] added (Issue Number: PR title (PR Number)) and github username to release notes for next major release

Thanks @naren-ponder ! I agree with @mvashishtha the text on the GIF is a bit small. Increasing the resolution and fontsize would be better. Note that right now the parse_date and quoting on read_csv is what's making the cell really wide. If we can remove those, then you would be able to record the video at a much greater zoom level on the notebook. Also agree with @jeffreykennethli comments about the hard-to-read font sizes on the PNG.

authors: dorisjlee naren-ponder


text:
Running all DNN layers in REE

Hi,
for comparison and study purposes, is it possible to run all the DNN layers in REE ?
If so, how can I do it?
Thanks in advance.

Hi, sorry for the late reply. but yes, you should be able to run all layers in the REE, just by leaving the -pp_start and -pp_end argument away. They will be set as 999 by default, and no layer will be putting inside the TEE.

repo: mofanv/darknetz


text:
🛑 STATUS.MOFE.IO is down

In fc37f8a, STATUS.MOFE.IO (https://status.mofe.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: STATUS.MOFE.IO is back up in 8f5ecd7.

repo: mofelee/upptime


text:
🛑 STATUS.MOFE.IO is down

In 83e9865, STATUS.MOFE.IO (https://status.mofe.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: STATUS.MOFE.IO is back up in d2eab10.


text:
macOS build fails with error cannot find GeneratedPluginRegistrant.swift:12:3

Building macOS application...
/Users/xxx/Sites/insta_sensors/macos/Flutter/GeneratedPluginRegistrant.swift:12:3: error: cannot find 'FlutterSecureStorageMacosPlugin' in scope
  FlutterSecureStorageMacosPlugin.register(with: registry.registrar(forPlugin: "FlutterSecureStorageMacosPlugin"))
  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Am I doing something wrong or is it an issue with the latest XCode?

Same issue here

I know it's not correct, but just to help temporarily, but just change from FlutterSecureStorageMacosPlugin to SwiftFlutterSecureStoragePlugin in the generated file in Flutter/GeneratedPluginRegistrant

Same problem here. :(

Which version of flutter_secure_storage are you using?

Using the latest stable, version 7.0.0
These are the details in the .lock
  flutter_secure_storage:
    dependency: "direct main"
    description:
      name: flutter_secure_storage
      url: "https://pub.dartlang.org"
    source: hosted
    version: "7.0.0"
  flutter_secure_storage_linux:
    dependency: transitive
    description:
      name: flutter_secure_storage_linux
      url: "https://pub.dartlang.org"
    source: hosted
    version: "1.1.2"
  flutter_secure_storage_macos:
    dependency: transitive
    description:
      name: flutter_secure_storage_macos
      url: "https://pub.dartlang.org"
    source: hosted
    version: "2.0.0"
  flutter_secure_storage_platform_interface:
    dependency: transitive
    description:
      name: flutter_secure_storage_platform_interface
      url: "https://pub.dartlang.org"
    source: hosted
    version: "1.0.1"
  flutter_secure_storage_web:
    dependency: transitive
    description:
      name: flutter_secure_storage_web
      url: "https://pub.dartlang.org"
    source: hosted
    version: "1.1.1"
  flutter_secure_storage_windows:
    dependency: transitive
    description:
      name: flutter_secure_storage_windows
      url: "https://pub.dartlang.org"
    source: hosted
    version: "1.1.3"

I know it's not correct, but just to help temporarily, but just change from FlutterSecureStorageMacosPlugin to SwiftFlutterSecureStoragePlugin in the generated file in Flutter/GeneratedPluginRegistrant

It doesn't work for me. GeneratedPluginRegistrant.swift regenerate itself on build action and build fails.  :(
Launching lib/main.dart on macOS in debug mode...
lib/main.dart:1
/Users/gaston/Desktop/Proyecto_llaves/desktop/llavero/macos/Flutter/GeneratedPluginRegistrant.swift:11:3: error: cannot find 'FlutterSecureStorageMacosPlugin' in scope
FlutterSecureStorageMacosPlugin.register(with: registry.registrar(forPlugin: "FlutterSecureStorageMacosPlugin"))
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
** BUILD FAILED **
Exception: Build process failed
Exited

Building macOS application...
[project]/macos/Flutter/GeneratedPluginRegistrant.swift:14:3: error: cannot find 'FlutterSecureStorageMacosPlugin' in scope
FlutterSecureStorageMacosPlugin.register(with: registry.registrar(forPlugin: "FlutterSecureStorageMacosPlugin"))

please update pub.dev

please update pub.dev

@juliansteenbakker 🙏🏻

Is this fixed? Still facing the same issue.

I will update pub.dev after christmas, sorry for the delay

I have released a new version 2.0.1 of the macos implementation. I think running pub upgrade will upgrade the dependency automatically for you.

If someone stumbles upon this, you can try this.
dependency_overrides:
  flutter_secure_storage_macos: ^2.0.1

authors: Megamil Rohithgilla12 Shahriyar13 anaerobic felipecastrosales juliansteenbakker krsatz ptheofan valientegaston

license_source: bigquery


text:
Android: IllegalAcessError on flutter_secure_storage v7.0.*

Hi!
I use flutter_secure_storage in my flutter project like this:
late FlutterSecureStorage _storage;

 _storage = const FlutterSecureStorage(
      aOptions: AndroidOptions(
        encryptedSharedPreferences: true,
      ),
    );

and when I update package version to 7.0.0 or 7.0.1, Android app keeps crashing on startup with exception (release build):
Fatal Exception: java.lang.IllegalAccessError Illegal class access: 'd.h.c.a.F.e' attempting to access 'com.google.crypto.tink.internal.n' (declaration of 'd.h.c.a.F.e' appears in /data/app/***app package name + some key***/base.apk)
This happens only on release builds, on debug build app does not crash with v. 7.0.*
If I use flutter_secure_storage version 6.0.0, then app runs fine.

This will help https://www.youtube.com/watch?v=JogvnnaJ8TI

I'm also having this issue, but my app is using v6.0.0 of flutter_secure_storage

@mogol can you help here?

I also have the same issue in 9.0.0

I am closing all older issues. If this issue still exists in the latest version, please let me know.

authors: AbdulazizAlshami BraveEvidence dmytrohurskyi ericomine juliansteenbakker


text:
Add arrays support for deferred chips

This pull-request is similar to #36, but adds also arrays support for deferred chips.
When user enters text -- render function performs request to server and adds all returned results to chips.

Closed in favor of #40 (I've created new branch for PR to be able to change lib in master)

repo: mohbasheer/angular-chips

license: mit


text:
Add new locale  ?

How can I integrate another locale to plugin? So countries will be displayed with another language ?

How can I integrate another locale to plugin? So countries will be displayed with another language ?

Sadly this is only possible by building your own version:

Fork and clone the repository and npm install.
Change the imported langs in src/bootstrap-select-country.js#L4-L6
Test your new version with: npm start.
Build a new bundle with npm build.

authors: mojoaxel mvnaz

repo: mojoaxel/bootstrap-select-country


text:
nonProxyHosts settings are ignored

When nonProxyHosts are configured in maven's settings, this configuration is ignored by the jaxws-maven-plugin.
Given these settings:
<settings>
    <proxies>
        <proxy>
            <active>true</active>
            <protocol>http</protocol>
            <host>proxy.intern</host>
            <port>1234</port>
            <nonProxyHosts>*.intern</nonProxyHosts>
        </proxy>
    </proxies>
</settings>

and this pom.xml:
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>test</groupId>
    <artifactId>test</artifactId>
    <version>0.0.1-SNAPSHOT</version>
    <build>
        <plugins>
            <plugin>
                <groupId>org.codehaus.mojo</groupId>
                <artifactId>jaxws-maven-plugin</artifactId>
                <version>2.5</version>
                <executions>
                    <execution>
                        <id>jaxws-wsimport</id>
                        <goals>
                            <goal>wsimport</goal>
                        </goals>
                        <configuration>
                            <wsdlUrls>
                                <wsdlUrl>http://test.intern/service?wsdl</wsdlUrl>
                            </wsdlUrls>
                        </configuration>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </build>
</project>

When executing mvn clean generate-sources, the following line is shown in maven's log, even though the URL test.intern is covered by the nonProxyHosts settings.
[INFO] jaxws:wsimport args: [-keep, -s, 'C:\dev\issue\target\generated-sources\wsimport', -d, 'C:\dev\is
sue\target\classes', -Xnocompile, -httpproxy:proxy.intern:1234, "http://test.intern/service?wsdl"]

Expected behaviour is: the parameter -httpproxy:proxy.intern:1234 should not be generated.

For a workaround try to set the a wrong httpproxy in the plugin configuration.
For example:
localhost:8080

authors: MichaelWarnecke hwirnsberger

repo: mojohaus/jaxws-maven-plugin


text:
Fixing issues moving from x.x.x-SNAPSHOT to x.x.x when any usage of MajMiInc filtering is active

https://github.com/mojohaus/versions-maven-plugin/issues/274
If you have a dependency with the version X.X.X-SNAPSHOT in your POM, and the latest appropriate version you'd expect to move to is X.X.X (sans snapshot), your dependency will not be updated when using the UseLatest series of goals, while specifying a MajMiInc filter.

@olamy Could you please review this?

repo: mojohaus/versions-maven-plugin


text:
Axios timeout handling not respected instead molecular middleware response is sent

Getting similar issue on molecular web ^0.9.1 as https://github.com/moleculerjs/moleculer-web/issues/62 . My scenario :

Calling POST api using axios and sending response to my client with some customization, Sample code given below :

async function sentRequest(axiosConfig) {
	let result = {},
		finalResult = {
			httpStatus: 500,
			status : 'FAILURE',
			//error : {},
			data : {}
		};
	try {
		result = await axiosReq(axiosConfig);
		finalResult.httpStatus = result.status,
		finalResult.status = 'SUCCESS',
		finalResult.data = result.data;
	} catch (error) {
		finalResult.error = { errorCode: '', errorMessage: '' };
		if (error.response && error.response.status) {
			finalResult.error.errorCode = error.response.status,
			finalResult.error.errorMessage = error.error_description ? error.error_description : error.message,
			finalResult.httpStatus = error.response.status;
			finalResult.data = error.response.data;
		} else {
			finalResult.error.errorCode = error.errno,
			finalResult.error.errorMessage = "Unknown error occured" + ( error.code ? (" - " +  error.code) : "");
		}
	}
	return finalResult;
}

When a timeout occurs response gets sent as is which is something like below (my custom code written in catch block is triggered after some time after response is already sent to client ) :

{
    "name": "RequestTimeoutError",
    "message": "Request is timed out when call 'auth.initiateOTPFlow' action on '60015702438-17396' node.",
    "code": 504,
    "type": "REQUEST_TIMEOUT",
    "data": {
        "action": "auth.initiateOTPFlow",
        "nodeID": "60015702438-17396"
    }
}

This is causing uneven response to the my client.
Below is the error :
[2021-11-29T12:10:52.882Z] ERROR 60015702438-17396/API: Request error! RequestTimeoutError : Request is timed out when call 'auth.initiateOTPFlow' action on '60015702438-17396' node.
RequestTimeoutError: Request is timed out when call 'auth.initiateOTPFlow' action on '60015702438-17396' node. at D:\developement\ReactJs-Projects\selfservice-api\node_modules\moleculer\src\middlewares\timeout.js:42:14
at async Service.callAction (D:\developement\ReactJs-Projects\selfservice-api\node_modules\moleculer-web\src\index.js:616:16)
at async D:\developement\ReactJs-Projects\selfservice-api\node_modules\moleculer-web\src\index.js:443:22
Data: { action: 'auth.initiateOTPFlow', nodeID: '60015702438-17396' }

Please create a repro code.

repo: moleculerjs/moleculer-web


text:
Hyperchicken partially offline

Due to lalala. We are investigating...

Issue resolved.

repo: molgenis/status


text:
Addition of Named Isotopes

Would you consider adding element symbols of named isotopes, specifically Deuterium (D) and Tritium (T) to the atomic weight table?

Thank you for your suggestion regarding the addition of element symbols for named isotopes. Currently, the atomic weight data in ChemFormula is based on average atomic weights, reflecting the natural isotopic distribution of non-radioactive elements (of unknown origin). As such, the package does not differentiate between isotopes like protium (1H), deuterium (D, 2H), or tritium (T, 3H). From a calculation perspective, the package cannot distinguish whether H represents 1H (protium) or the natural isotopic distribution of hydrogen. This naturally applies to all elements - not just hydrogen.
However, you can extend the file /src/elements.py in your local installation by modifying the atomic_weight() function to include entries for deuterium and tritium as a quick workaround. I would also recommend defining a custom symbol for protium (e.g., Hp, since P, Pr, and Pm are already defined) to differentiate between the specific isotopes and natural hydrogen. This would look something like this:
def atomic_weight(element):
    atomic_weight_table = {
        "H":    1.008,   # average atomic weight for hydrogen in accordance with Pure Appl. Chem., 2016, 88, 265-291
        "D":    2.014,   # atomic weight for deuterium
        "T":    3.016,   # atomic weight for tritium
        "Hp":   1.00784, # atomic weight for protium, with a custom atomic symbol (not IUPAC compliant)
        # ... rest of the elements
    }
    # return the atomic weight of the element symbol passed to the function, False if the element symbol does not exist
    return float(atomic_weight_table[element]) if element in atomic_weight_table else False

This will allow you to specify deuterium and tritium in your formulas and calculations.
For a future release, I am planning to add support for user-defined abbreviations in chemical formulas, such as Ph for C6H5. In this context, I will also consider how to better support isotopes, as this deserves a more general approach. Thanks again for your feedback!

authors: lcnittl molshape

repo: molshape/ChemFormula


text:
Bug in format of floating point numbers on system with comma as decimal separator

On a German system, the floatingpoint number format changes the value of the number in pretty print.
Original Json file:
{"A":[4.76343,4.87822,4.98112312,3.9567656700000002]}
Pretty print:

Might be an issue with the standard  decimal separator on my system.  (,).
Expected Behaviour:
Values of numbers shouldn't be changed by pretty print.

Nevermind, old Version

repo: molsonkiko/JsonToolsNppPlugin


text:
Extra white-space in localized format for Serbian, Croatian, Bosnian, and Slovenian

For the locales listed below there should be no white-space in the localized date string ('L'), i.e. 25. 11. 2014 should be 25.11.2014.
Historically, all these inherit from the German locale.

Serbian sr at line 46 and sr-cyrl at line 46

Croatian hr at line 78

Bosnian bs at line 77

Slovenian sl at line 84

Macedonian locale has the correct date format.

Perhaps @milan-j is right for Serbian. But the DD.MM.YYYY. form is commonly used and correct in Croatian, and AFAIK Bosnian as well.

I'm going to close this due to age. If it is still an issue, feel free to re-open. If the locale files are wrong, we would definitely accept a pull request.

@milan-j and @cebence the correct way to write Serbian dates according to Serbian orthography is with spaces i.e. 1. 2. 2017. Alternatively, you can write like what @milan-j mentioned as primary way to write (with leading zero), which is used in accounting and business correspondency.
On top of that, there must be dot at the end except if there is another punctuation mark following the dot, in which case the dot is omitted.
https://ciklopea.com/sr/језичка-грешка/jezicka-greska-br-40-pisanje-datuma-u-srpskom-jeziku/
https://www.opismenise.com/nedoumice/kako-se-pise-datum-u-srpskom-jeziku/
https://www.pismenica.rs/kako-se-pise/pravilno-pisanje-datuma-nula-ispred-jednocifrenih-brojeva/
http://kakosepise.com/rec/12-12-2013-ili-12-12-2013/

I created #4741 and #4742 to fix this

authors: bmarkovic cebence maggiepint scrnjakovic

repo: moment/moment


text:
Issue with the setDefault timezone.

Upon switching form 2.09 to 2.10 I noticed that the setDefault timezone was no longer adjusting all of the moments like it was previously. Is there a known bug with the default timezone feature?

Could be related https://github.com/moment/moment/issues/2626

setDefault is part of the moment-timezone API.
There's one open issue on this in moment/moment-timezone#208.  If your scenario is different, then please log a new issue at https://github.com/moment/moment-timezone/issues

authors: michplunkett mj1856 paulfalgout


text:
Custom inspect() method for NodeJS?

Apologies if this is a dupe, I searched but couldn't find anything.
Would you be open to providing an inspect() method on moment objects which returns a human-readable representation of the moment? This would be useful for debugging and testing purposes.
As well as being used in Node core, a bunch of other inspect libraries out there will detect this method and use it.
I had a bit of a play around in the repl, this seems to be a decent first cut:
// Current
moment()
{ [Number: 1465642464921]
  _isAMomentObject: true,
  _isUTC: false,
  _pf:
   { empty: false,
     unusedTokens: [],
     unusedInput: [],
     overflow: -2,
     charsLeftOver: 0,
     nullInput: false,
     invalidMonth: null,
     invalidFormat: false,
     userInvalidated: false,
     iso: false,
     parsedDateParts: [],
     meridiem: null },
  _locale:
   Locale {
     _ordinalParse: /\d{1,2}(th|st|nd|rd)/,
     ordinal: [Function],
     _abbr: 'en',
     _config:
      { ordinalParse: /\d{1,2}(th|st|nd|rd)/,
        ordinal: [Function],
        abbr: 'en' },
     _ordinalParseLenient: /\d{1,2}(th|st|nd|rd)|\d{1,2}/ },
  _d: 2016-06-11T10:54:24.921Z }

// define an inspect() function
moment.prototype.inspect = function() {
  return this.format('[moment]("YYYY-MM-DD HH:mm:ss.SSSZ")')
}
[Function]

// Easier to read output
> moment()
moment("2016-06-11 11:55:05.192+01:00")

// And it seems to be reverisble
> moment("2016-06-11 11:55:05.192+01:00")
moment("2016-06-11 11:55:05.192+01:00")

I'm happy to submit a PR and tests if this is palatable.

I do all my JS development client side so I don't have a ton of node exposure, but I think this makes sense. Basically what I get from google is that if util.inspect() is called on a moment, node will find this inspect function on the prototype and return that string. Seems like this is largely used for logging purposes?
I will warn that if this affects the ability to read all the properties on the moment if you need to, then it's not a good thing. For debugging purposes, we frequently need to look at some of the internal properties. As long as it doesn't break that I'm cool with it.

It'll kick in whenever a moment get passed to node's util.inspect, which is used internally by console.log. All the properties are still there and accessible. In the browser this has no effect unless called explicitly.
If you wanted to log out a moment with all of it's properties in node after these changes, you'd need to do console.log("%j", m) or similar.

Closed in favor of pull #3231

authors: glenjamin maggiepint


text:
Leverage setHours to have a more efficient implementation of start-end-of

Description of the Issue and Steps to Reproduce:
let d = new Date()
d.setHours(0, 0, 0, 0)

is way more efficient than :
let d = new Date()
d.setHours(0)
d.setMinutes(0)
d.setSeconds(0)
d.setMilliseconds(0)

(about 400 times faster)
When calling startOf(unit), where unit is one of 'hour', 'day', 'week', 'month', 'year', moment should use the first method rather than the second one.
Environment:
I'm running a ReactNative app on an iOS Simulator, running iOS 10.1.
Other information that may be helpful:

The time zone setting of the machine the code is running on : UTC + 01:00 (Paris, France)
The time and date at which the code was run : 2016-11-23T10:56:19+01:00
Other libraries in use (TypeScript, Immutable.js, etc) : ReactNative

console.log( (new Date()).toString())
// [Log] Wed Nov 23 2016 10:58:47 GMT+0100 (CET) (index.ios.bundle, line 788)
console.log((new Date()).toLocaleString())
// [Log] 11/23/2016, 10:58:47 AM (index.ios.bundle, line 788)
console.log( (new Date()).getTimezoneOffset())
// [Log] -60 (index.ios.bundle, line 788)
console.log( navigator.userAgent)
// [Log] undefined (index.ios.bundle, line 788)
console.log(moment.version)
// [Log] 2.14.1 (index.ios.bundle, line 788)

#3620

closed in favor of #3620

authors: aymericbouzy maggiepint


text:
Talossan (tzl) translation

Hello, together with Iustì Canun I created a Talossan (tzl) translation of Moment.js.
It is almost finished, but there is one problem.
The relative time sentences don't fit in the variables, they differ per time (future/past).
Could somebody explain to me how I can implement the time sentences?
The missing future sentences:
in a few seconds => osprei viensas secunds
in a minute => osprei 'n míut
in % minutes => osprei % míuts
in an hour => osprei 'n þora
in % hours => osprei % þoras
in a day => osprei 'n ziua
in % days => osprei % ziuas
in a month => osprei 'n mes
in % months => osprei % mesen
in a year => osprei 'n ar
in % years => osprei % ars
The missing past sentences:
a few seconds ago => ja'iensas secunds
a minute ago => ja'iens míut
% minutes ago => ja % míuts
an hour ago => ja'iensa þora
% hours ago => ja % þoras
a day ago => ja'iensa ziua
% days ago => ja % ziuas
a month ago => ja'iens mes
% months ago => ja % mesen
a year ago => ja'iens ar
% years ago => ja % ars

Lets not argue about politics.
@robin0van0der0v what you want to achieve is relatively simple, using the advanced (function API). Check the russian language for reference. The arguments are value, withoutSuffix, unit, isFuture.

@ichernev I already checked the documentation and just checked the Russian locale, but I couldn't find my answer.
I will try to explain it more clearly.
If a year is shown, it should add the suffix "/"+(years since December 26 in Roman numerals).
Examples:
Thursday, Decemer 25, 2014 = Xhúadi, li 25. Zecemvar dallas 2014/XXXV
Friday, December 26, 2014 = Viénerçi, li 26. Zecemvar dallas 2014/XXXVI

Ah, well this is not supported at the moment, you can add a postformat that
detects the year and replaces it with this year plus roman thing.
On Jan 17, 2015 4:46 PM, "Robin van der Vliet" notifications@github.com
wrote:

@ichernev https://github.com/ichernev I already checked the
documentation and just checked the Russian locale, but I couldn't find my
answer.
I will try to explain it more clearly.
If a year is shown, it should add the suffix "/"+(years since December 26
in Roman numerals).
Examples:
Thursday, Decemer 25, 2014 = Xhúadi, li 25. Zecemvar dallas 2014/XXXV
Friday, December 26, 2014 = Viénerçi, li 26. Zecemvar dallas 2014/XXXVI
—
Reply to this email directly or view it on GitHub
https://github.com/moment/moment/pull/2124#issuecomment-70391495.

@robin0van0der0v we changed the directory / locale structure a bit, can you please rebase. I'll merge it afterwards. Also, you can really do the year correctly, as long as you "mark" it in a way, then detect it in postformat and replace it. Something like ##YYYY##, then search for ##\d+## and replace it with roman numerals.

Close in favor of #2508


text:
fix: cache dictionary get batch response returning hit errors

https://gomomento.slack.com/archives/C03HUJ5GPAB/p1669152191426729

@bruuuuuuuce thanks for digging in to this.  I believe it probably addresses https://github.com/momentohq/dev-eco-issue-tracker/issues/136 ?
lmk if this is blocking your progress on a canary.  The change looks reasonable but I would like for us to have an integration test that covers the bug before this gets merged, if possible.

repo: momentohq/client-sdk-dotnet-incubating


text:
chore: Add more descriptive error message for auth token parse

Is users paste an invalid auth token, the following error message will be displayed: Please make sure entered auth token matches your auth token
Closes #45

It looks like I'm not authorized to merge this pr...
@eaddingtonwhite - Do you have permission to do so?

repo: momentohq/client-sdk-rust


text:
Is there a way to get the input Id ? of the datetime input

Is there a way to get the input Id ? of the datetime input

If you have jquery loaded, you could do something like this:
$('sm-date-time-picker').find('input.sm-input-container').attr('id');

@oscar09 thanks

repo: mominsamir/smDateTimeRangePicker


text:
GNB1-Related Disorder

Mondo term
intellectual disability, autosomal dominant 42
Synonyms
No response
Synonym type
exact
Additional comments
This is related to 6600.  We have a NORD report about this condition with the requested synonym name.
Thank you! Gioconda

Hello @galyea123
According to OMIM:139380, a variation in the GNB1 gene can lead to multiple diseases, including, but not limited to 'intellectual disability, autosomal dominant 42'. Therefore "GNB1-Related Disorder" should be broad and not exact.
Do you have any other information that we could refer to and that would support this synonym as exact?
Thank you!

repo: monarch-initiative/mondo


text:
revise label for MONDO:0015023

closes #1446

this is fine but we need a consistent decision on naming diseases that are gene-specific members of a series

authors: cmungall nicolevasilevsky


text:
wallet.incoming(tx_id=tx_id) doesn't return any IncomingPayment(s) when the tx is unconfirmed

I'm not sure if this was intentional or not, if it is then feel free to close this issue.
The issue:
Scenario: A tx is currently unconfirmed / in the mem pool / not on the blockchain. The tx_id is 'abcdefg'
Code:
wallet = Wallet(JSONRPCWallet())

incoming_txs = w.incoming(tx_id='abcdefg')

Problem:
incoming_txs is an empty list : []
Work around:
Code:
incoming_txs = w.incoming(unconfirmed=True, confirmed=False)

    for tx in incoming_txs:

        if tx.transaction.hash == 'abcdefg':

            # do something

            # found tx

            break

It seems you missed unconfirmed=True kwarg in the first call. I've just run a test and cannot reproduce the error.

repo: monero-ecosystem/monero-python


text:
functional_daemon_test does not pass on first test run on local setup

functional_daemon_test, defined inside tests/rpc.rs does not pass when running cargo test the first time WHEN there are no blocks in the regtest network, but it works if there is.
Also, the test pass for the test workflow in the repository, probably because the tests run concurrently and the wallet test creates blocks before the daemon test runs.
As a solution, a block can first be created. Or, if the intention is to test a possible failure, then just test the Error returned.
This issue is related to #48

Error returned by cargo test --tests rpc:
'functional_daemon_test' panicked at 'called `Result::unwrap()` on an `Err` value: Server error: Requested block height: 1 greater than current top block height: 0

Line that causes the error is line 27 https://github.com/monero-ecosystem/monero-rpc-rs/blob/master/tests/rpc.rs#L27

I did more debugging and functional_daemon_test always pass on v0.17.3.2 but does not pass on master.

Cool, on v0.17.3, it returns:
{
  "id": "0",
  "jsonrpc": "2.0",
  "result": "0000000000000000000000000000000000000000000000000000000000000000"
}

On master:
{
    "error": {
        "code": -2,
        "message": "Requested block height: 1 greater than current top block height: 0"
    },
    "id": "0",
    "jsonrpc": "2.0"
}

Ok, I saw what is going on. The last commit on master (8f48f464957c875af3183cd9d35769592e1aef48) has the same of v0.17.32 for the function core_rpc_server::on_getblockhash, but my local branch was at 9750e1fa103539b3e533455500610aae76e253a5 which has a different implementation.
See: https://github.com/monero-project/monero/blob/8f48f464957c875af3183cd9d35769592e1aef48/src/rpc/core_rpc_server.cpp#L1701, https://github.com/monero-project/monero/blob/424e4de16b98506170db7b0d7d87a79ccf541744/src/rpc/core_rpc_server.cpp#L1663, and https://github.com/monero-project/monero/blob/9750e1fa103539b3e533455500610aae76e253a5/src/rpc/core_rpc_server.cpp#L1706
Those changes are related to https://github.com/monero-project/monero/pull/7936,  https://github.com/monero-project/monero/pull/7937, and https://github.com/monero-project/monero/pull/8384

Closing now that the debug is over :)

repo: monero-ecosystem/monero-rpc-rs


text:
🛑 Bitlending Monetix is down

In 74e2b65, Bitlending Monetix (https://api.bitlending.monetix.io/health) was down:

HTTP code: 502
Response time: 731 ms

Resolved: Bitlending Monetix is back up in ac3e2f3.

repo: monetixio/upptime


text:
No MongockChangeLog collection found

I am using mongock 4.3.8 with SpringBoot 2.5.7
I provided the configurations using mongock.change-logs-scan-package and used @EnableMongock annotation.
And then tested its working using @ChangeLog and @ChangeSet. Its working just fine.
But I cannot find any MongockChangeLog collection in db. Why is it so ?
Am I missing any configuration settings?

Sorry, this issue was raised due to a misunderstanding.
Apologies for any inconvenience.

repo: mongock/mongock


text:
Private Endpoint Service is not ready for AtlasProject

What did you do to encounter the bug?
Steps to reproduce the behavior:
After upgrading the Atlas operator from Alpha to GA version, we have started encountering following for the a specific AtlasProject:
helm history operator-release
20      	Wed Feb 23 09:27:23 2022	superseded	mongodb-atlas-operator-0.2.5	0.6.1      	Upgrade complete
21      	Thu Jun 30 13:37:32 2022	deployed  	mongodb-atlas-operator-1.0.0	1.0.0      	Upgrade complete

Status:
  Conditions:
    Last Transition Time:  2022-07-01T07:29:13Z
    Status:                True
    Type:                  Ready
    Last Transition Time:  2022-06-30T11:45:15Z
    Status:                True
    Type:                  ProjectReady
    Last Transition Time:  2022-07-01T07:29:11Z
    Status:                True
    Type:                  IPAccessListReady
    Last Transition Time:  2022-06-30T10:09:23Z
    Status:                True
    Type:                  ValidationSucceeded
    Last Transition Time:  2022-06-30T11:57:59Z
    Message:               Private Endpoint Service is not ready
    Reason:                ProjectPrivateEndpointServiceIsNotReadyInAtlas
    Status:                False
    Type:                  PrivateEndpointReady
    Last Transition Time:  2022-06-30T12:02:00Z
    Message:               Private Endpoint Service is not ready
    Reason:                ProjectPrivateEndpointServiceIsNotReadyInAtlas
    Status:                False
    Type:                  PrivateEndpointServiceReady
  Id:                      60ae9bf242cb863bc38a310a
  Observed Generation:     2
Events:                    <none>

There is no PE configured for this AtlasProject in Atlas and we don't encounter this issue for other AtlasProjects in this Env.
What did you expect?
Expectation was that there should not be any validation for Private Endpoint service for this Project.
What happened instead?
Wonder why its trying to create/validate Private Endpoint Service.
Screenshots
N/A
Operator Information

Operator Version (1.0.0)

Kubernetes Cluster Information

Distribution
Version
Image Registry location (quay, or an internal registry)

Additional context
If possible, please include:

kubectl describe output

k describe atlasproject projects-test -n platform
Name:         projects-test
Namespace:    platform
Labels:       app.kubernetes.io/instance=projects
             app.kubernetes.io/managed-by=Helm
             app.kubernetes.io/name=atlas-clusters
             app.kubernetes.io/version=0.5.0
             helm.sh/chart=atlas-clusters-0.0.1
Annotations:  meta.helm.sh/release-name: projects
             meta.helm.sh/release-namespace: platform
             mongodb.com/atlas-resource-policy: keep
API Version:  atlas.mongodb.com/v1
Kind:         AtlasProject
Metadata:
 Creation Timestamp:  2021-12-08T16:59:03Z
 Finalizers:
   mongodbatlas/finalizer
 Generation:  2
 Managed Fields:
   API Version:  atlas.mongodb.com/v1
   Fields Type:  FieldsV1
   fieldsV1:
     f:metadata:
       f:annotations:
         .:
         f:meta.helm.sh/release-name:
         f:meta.helm.sh/release-namespace:
         f:mongodb.com/atlas-resource-policy:
       f:labels:
         .:
         f:app.kubernetes.io/instance:
         f:app.kubernetes.io/managed-by:
         f:app.kubernetes.io/name:
         f:app.kubernetes.io/version:
         f:helm.sh/chart:
     f:spec:
       .:
       f:connectionSecretRef:
         .:
         f:name:
       f:name:
   Manager:      helm
   Operation:    Update
   Time:         2021-12-08T16:59:03Z
   API Version:  atlas.mongodb.com/v1
   Fields Type:  FieldsV1
   fieldsV1:
     f:spec:
       f:projectIpAccessList:
   Manager:      Go-http-client
   Operation:    Update
   Time:         2022-05-23T13:25:30Z
   API Version:  atlas.mongodb.com/v1
   Fields Type:  FieldsV1
   fieldsV1:
     f:metadata:
       f:finalizers:
         .:
         v:"mongodbatlas/finalizer":
     f:status:
       .:
       f:conditions:
       f:id:
       f:observedGeneration:
   Manager:         manager
   Operation:       Update
   Time:            2022-06-30T11:45:15Z
 Resource Version:  1616237116
 UID:               d424a085-95fa-4f5b-8a74-3eb7120e5b52
Spec:
 Connection Secret Ref:
   Name:  projects-test
 Name:    projects-test
 Project Ip Access List:
   Comment:                     test
   Ip Address:                  x.x.x.x./x
 With Default Alerts Settings:  true
Status:
 Conditions:
   Last Transition Time:  2022-07-01T07:29:13Z
   Status:                True
   Type:                  Ready
   Last Transition Time:  2022-06-30T11:45:15Z
   Status:                True
   Type:                  ProjectReady
   Last Transition Time:  2022-07-01T07:29:11Z
   Status:                True
   Type:                  IPAccessListReady
   Last Transition Time:  2022-06-30T10:09:23Z
   Status:                True
   Type:                  ValidationSucceeded
   Last Transition Time:  2022-06-30T11:57:59Z
   Message:               Private Endpoint Service is not ready
   Reason:                ProjectPrivateEndpointServiceIsNotReadyInAtlas
   Status:                False
   Type:                  PrivateEndpointReady
   Last Transition Time:  2022-06-30T12:02:00Z
   Message:               Private Endpoint Service is not ready
   Reason:                ProjectPrivateEndpointServiceIsNotReadyInAtlas
   Status:                False
   Type:                  PrivateEndpointServiceReady
 Id:                      60ae9bf242cb863bc38a310a
 Observed Generation:     2
Events:                    <none>

yaml definitions for your objects
log files for the operator and database pods

We've just released mongodb-atlas-operator-1.1.0 which might fix some of your problems.
Please try to upgrade and let us know if it helps. Thank you, @sunchill06  🙏

Thanks @fabritsius for your revert. Let me upgrade it and try it out.

This works fine now. Thanks a lot for fixing it up so quickly.

repo: mongodb/mongodb-atlas-kubernetes


text:
was built for HHVM 3.8, and cannot be loaded with HHVM 3.7

When doing 'service hhvm restart':
$ sudo service hhvm restart

Restarting HHVM FastCGI Daemon hhvm                                                                                Uncaught exception: /etc/hhvm/ext/mongo.so was built for HHVM 3.8, and cannot be loaded with HHVM 3.7\n
[fail]
$ hhvm --version
HipHop VM 3.7.0 (rel)
Compiler: tags/HHVM-3.7.0-0-gc8baf9cd3cb603e030969bfe24634d5e85549915
Repo schema: 1988ce75e6a571ce9c79c60fd7dc3ca8a5a5d403

same problem here, has someone solved or I should just come back to the 3.7?

same

can you check if still is not working with the latest version?

authors: bogomips joshuataylor mcuadros nlared

repo: mongofill/mongofill-hhvm


text:
Gemspec trouble

Hi,
I'm having trouble with my gemspec, it gives a infinite loop on this:
Invalid gemspec in [/var/www/staging/app/shared/bundle/ruby/1.9.1/specifications/mongoid-2.2.0.gemspec]: no such file to load -- mongoid/version
Invalid gemspec in [/var/www/staging/app/shared/bundle/ruby/1.9.1/specifications/mongoid-2.2.0.gemspec]: no such file to load -- mongoid/version
Invalid gemspec in [/var/www/staging/app/shared/bundle/ruby/1.9.1/specifications/mongoid-2.2.0.gemspec]: no such file to load -- mongoid/version
:(
It started to happen when i've fixed this bug:
Invalid gemspec in [/var/www/staging/app/shared/bundle/ruby/1.9.1/specifications/mongoid-2.2.0.gemspec]: invalid date format in specification: "2011-08-28 00:00:00.000000000Z"
replacing this invalid gemspec with the mongoid.gemspec on "/" of repository. It worked fine, but when i need to run 'bundle install' the loop starts :(

The simplest way to get around the gemspec issues is to reinstall ruby via rvm and make sure libyml is installed on your system beforehand. This way rvm installs ruby with Psych instead of Syck.

authors: durran guilherme

repo: mongoid/mongoid


text:
Add support for Ruby 2.4.0

Seems non-trivial. Even with this:
  gem 'mongo', github: 'mongodb/mongo-ruby-driver' if RUBY_VERSION >= '2.4.0'
  gem 'bson', github: 'mongodb/bson-ruby' if RUBY_VERSION >= '2.4.0'

      TypeError:
        wrong argument type Integer (expected Proc)
      # /Users/dblock/.rvm/gems/ruby-2.4.0/bundler/gems/mongo-ruby-driver-dd19e48bbb72/lib/mongo/server/connection.rb:193:in `block in write'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/bundler/gems/mongo-ruby-driver-dd19e48bbb72/lib/mongo/server/connection.rb:192:in `each'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/bundler/gems/mongo-ruby-driver-dd19e48bbb72/lib/mongo/server/connection.rb:192:in `write'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/bundler/gems/mongo-ruby-driver-dd19e48bbb72/lib/mongo/server/connection.rb:162:in `deliver'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/bundler/gems/mongo-ruby-driver-dd19e48bbb72/lib/mongo/server/connection.rb:108:in `block in dispatch'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/bundler/gems/mongo-ruby-driver-dd19e48bbb72/lib/mongo/monitoring/publishable.rb:47:in `publish_command'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/bundler/gems/mongo-ruby-driver-dd19e48bbb72/lib/mongo/server/connection.rb:107:in `dispatch'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/bundler/gems/mongo-ruby-driver-dd19e48bbb72/lib/mongo/operation/executable.rb:37:in `block in execute'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/bundler/gems/mongo-ruby-driver-dd19e48bbb72/lib/mongo/server/connection_pool.rb:107:in `with_connection'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/bundler/gems/mongo-ruby-driver-dd19e48bbb72/lib/mongo/server.rb:242:in `with_connection'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/bundler/gems/mongo-ruby-driver-dd19e48bbb72/lib/mongo/operation/executable.rb:35:in `execute'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/bundler/gems/mongo-ruby-driver-dd19e48bbb72/lib/mongo/operation/commands/collections_info.rb:51:in `execute'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/bundler/gems/mongo-ruby-driver-dd19e48bbb72/lib/mongo/database/view.rb:114:in `send_initial_query'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/bundler/gems/mongo-ruby-driver-dd19e48bbb72/lib/mongo/database/view.rb:95:in `collections_info'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/bundler/gems/mongo-ruby-driver-dd19e48bbb72/lib/mongo/database/view.rb:55:in `collection_names'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/bundler/gems/mongo-ruby-driver-dd19e48bbb72/lib/mongo/database.rb:116:in `collection_names'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/bundler/gems/mongo-ruby-driver-dd19e48bbb72/lib/mongo/database.rb:140:in `collections'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/gems/mongoid-6.0.3/lib/mongoid/config.rb:175:in `purge!'
      # /Users/dblock/.rvm/gems/ruby-2.4.0/gems/mongoid-6.0.3/lib/mongoid.rb:99:in `purge!'
      # ./spec/spec_helper.rb:20:in `block (2 levels) in <top (required)>'

https://github.com/mongodb/mongo-ruby-driver/pull/847, this is bug in MRI 2.4.0, fixed in ruby-head, same issue https://github.com/DatabaseCleaner/database_cleaner/issues/466, waiting for 2.4.1 with fix

This works now.

authors: Fudoshiki dblock


text:
publish for Scala 2.13.0-M5?

I think your dependencies are available for M4 now? (not 100% sure)
in the Scala 2.13 community build, at e.g. https://scala-ci.typesafe.com/job/scala-2.13.x-integrate-community-build/1228/consoleFull, I'm seeing that getting minitest onto the new collections would also help unlock a bunch of downstream projects. (most of which need cats too, but cats isn't too far from being able to publish, too.)
[info] Project ammonite--------------------: DID NOT RUN (stuck on broken dependencies: minitest, scala-async, spray-json, tut, utest)
[info] Project better-monadic-for----------: DID NOT RUN (stuck on broken dependencies: cats, minitest, pcplod)
[info] Project eff-------------------------: DID NOT RUN (stuck on broken dependencies: cats, minitest)
[info] Project fs2-reactive-streams--------: DID NOT RUN (stuck on broken dependencies: cats, minitest, scodec-bits, utest)
[info] Project giter8----------------------: DID NOT RUN (stuck on broken dependencies: cats, grizzled, minitest, scalamock, utest)
[info] Project http4s----------------------: DID NOT RUN (stuck on broken dependencies: cats, http4s-parboiled2, log4s, minitest, scodec-bits, spray-json, twirl, utest)
[info] Project kxbmap-configs--------------: DID NOT RUN (stuck on broken dependencies: cats, minitest, utest)
[info] Project minitest--------------------: FAILED (RuntimeException: )
[info] Project monix-----------------------: DID NOT RUN (stuck on broken dependencies: cats, minitest)
[info] Project sbinary---------------------: DID NOT RUN (stuck on broken dependencies: cats, minitest, utest)
[info] Project sbt-------------------------: DID NOT RUN (stuck on broken dependencies: cats, minitest, spray-json, utest)
[info] Project sbt-io----------------------: DID NOT RUN (stuck on broken dependencies: cats, minitest, utest)
[info] Project sbt-librarymanagement-------: DID NOT RUN (stuck on broken dependencies: cats, minitest, spray-json, utest)
[info] Project sbt-util--------------------: DID NOT RUN (stuck on broken dependencies: cats, minitest, spray-json, utest)
[info] Project scala-debugger--------------: DID NOT RUN (stuck on broken dependencies: minitest, scala-async, scalamock, scallop, spray-json, tut, utest)
[info] Project scala-ssh-------------------: DID NOT RUN (stuck on broken dependencies: cats, minitest, utest)
[info] Project scalafmt--------------------: DID NOT RUN (stuck on broken dependencies: cats, minitest, utest)
[info] Project scalaprops------------------: DID NOT RUN (stuck on broken dependencies: cats, minitest, utest)
[info] Project scopt-----------------------: DID NOT RUN (stuck on broken dependencies: minitest, utest)
[info] Project sttp------------------------: DID NOT RUN (stuck on broken dependencies: akka-actor, cats, minitest, scodec-bits, spray-json)
[info] Project zinc------------------------: DID NOT RUN (stuck on broken dependencies: cats, minitest, spray-json, utest)

https://github.com/monix/minitest/pull/19
[minitest] [error] 'by-name-right-associative' is not a valid choice for '-Xlint'
[minitest] [error] 'unsound-match' is not a valid choice for '-Xlint'

after #19 was merged, I tried the Scala 2.13 community build and got:
[minitest] [error] /Users/tisue/community.213/target-0.9.12/project-builds/minitest-140990deb8a820140508cf1c8a3f44a72fc477aa/shared/src/main/scala/minitest/runner/Framework.scala:30:5: trait Runner is abstract; cannot be instantiated
[minitest] [error]     new Runner(args, remoteArgs, testClassLoader)
[minitest] [error]     ^
[minitest] [info] No documentation generated with unsuccessful compiler run
[minitest] [error] one error found
[minitest] [error] /Users/tisue/community.213/target-0.9.12/project-builds/minitest-140990deb8a820140508cf1c8a3f44a72fc477aa/shared/src/main/scala/minitest/runner/Framework.scala:30:5: trait Runner is abstract; cannot be instantiated
[minitest] [error]     new Runner(args, remoteArgs, testClassLoader)
[minitest] [error]     ^

this looks a consequence of https://github.com/scala/scala/pull/6589; import sbt.testing.{Framework => BaseFramework, _} is importing Runner and then (after PR 6589) that shadows minitest.runner.Runner

if I run the community build with version=2.13.0-M4 I get:
[info] Project minitest--------------------: SUCCESS (project rebuilt ok)

so that's promising.

minitest remains green in the 2.13 community build. I've updated this ticket name now that Scala 2.13.0-M5 is out

scalacheck needs to publish first, I think. https://github.com/rickynils/scalacheck/issues/418

ScalaCheck 1.14.0 is now published for M5 (both JVM & JS), so this should be unblocked now, I think?

@SethTisue Can you review #30?

@ashawley done

ticket is closed, but I don't see artifacts at https://repo1.maven.org/maven2/io/monix/minitest_2.13.0-M5 ?

@SethTisue I don’t remember closing it, however I’ll publish it tomorrow.

@SethTisue I published it with version 2.2.2

Sorry for additional noise (spamming), I should have known better :worried:

authors: SethTisue alexandru ashawley dejan2609 xuwei-k

repo: monix/minitest


text:
Value types can still be constructed in an invalid state

Even following #1783, the following value type:
CS_VALUE_TYPE class DLL_API ValueType {
public:
    std::string string_member;
};

can be constructed in an invalid state, e.g. by using ValueType v = default;
Following v.string_member = "..."; resulting reads will result in garbage being read.
A remedy could be a variable to track whether the object was initialized and if not initializing it whenever any operation is called on it.

I'm fairly certain there is not. C# structs being zero-initialized in a number of cases seems deeply ingrained in the language. I also think this is a bad design choice.

repo: mono/CppSharp


text:
Updated submodule CppSharp / W.I.P fix #165

This is needed for completing #169  which is needed for fixing #165.
The current picked include paths for the windows 10 sdk are incomplete. The updated CppSharp version fixes the selection of those.
The commit will be adjusted further for fixing #165 too.

Hello! I'm the build bot for the Mono project.
I need approval from a Mono team member to build this pull request. A team member should reply with "approve" to approve a build of this pull request, "whitelist" to whitelist this and all future pull requests from this contributor, or "build" to explicitly request a build, even if one has already been done.
Contributors can ignore this message.

This PR is unfortunately a total mess. I'll make a new clean one.

authors: monojenkins realvictorprm


text:
Cannot deploy libSkiaSharp when copy libSkiaSharp from  runtimes\win10-x86\native location in SkiaSharp NuGet package into published folder.

Description
Cannot deploy libSkiaSharp when copy libSkiaSharp from the runtimes\win10-x86\native location in SkiaSharp NuGet package into the published folder.
Code

Create an asp.net core 2.0 web project (any template).
Reference a NuGet package that has a native library, in my particular case it was SkiaSharp 1.6.0.
Create publish profile
In publish, profile settings change deployment mode to self-contained, and target runtime to win-x86
Publish the project
Copy libSkiaSharp from the runtimes\win10-x86\native location in the SkiaSharp NuGet package into the published folder.

Expected Behavior
It should works
Actual Behavior
Cannot deploy

Is there an error or exception?
Also, you probably have to use 'runtimes\win-x86\native'

Did you manage to resolve this?

Closing this as the correct artifact is the on in runtimes\win-x86\native And, when you publish the web app, the files are not in the root, but rather in he runtimes folder that gets copied. The .NET Core runtime system will automatically load the correct architecture depending on the OS and CPU.

authors: ManishSync mattleibow

repo: mono/SkiaSharp


text:
[BUG] SkiaSharp Managed-Only Building does not work, because there is a mix of .NET 7 and .NET 6 assembly references

Description
I tried building SkiaSharp according to these instructions (Managed-Only Building): https://github.com/mono/SkiaSharp/wiki/Building-SkiaSharp
but I get 4 build errors using dotnet cake --target=everything --skipExternals=all and VS2022 17.7 Preview 4.0.
Example:
"C:\repos\mono\SkiaSharp\source\SkiaSharpSource.Windows-net.slnf" (Build target) (1:2) ->
       "C:\repos\mono\SkiaSharp\binding\SkiaSharp\SkiaSharp.csproj" (default target) (2:59) ->
       "C:\repos\mono\SkiaSharp\binding\SkiaSharp\SkiaSharp.csproj" (Build target) (2:66) ->
       (CoreCompile target) ->
         CSC : error CS1705: Assembly 'Microsoft.iOS' with identity 'Microsoft.iOS, Version=16.4.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065' uses 'System.Runtime, Version=7.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' which has a higher version than referenced assembly 'System.Runtime' with identity 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' [C:\repos\mono\SkiaSharp\binding\SkiaSharp\SkiaSharp.csproj::TargetFramework=net6.0-ios]

Based on dotnet cake output, CoreCompile is indeed using /reference:"C:\Program Files\dotnet\packs\Microsoft.NETCore.App.Ref\6.0.20\ref\net6.0\System.Runtime.dll"
Which is clearly net6.0.
And this is used for Microsoft.iOS: /reference:C:\repos\mono\SkiaSharp\externals\package_cache\microsoft.ios.ref\16.4.7090\ref\net7.0\Microsoft.iOS.dll
Which is clearly net7.0.
Expected Behavior
SkiaSharp will compile using dotnet cake.
Actual Behavior
SkiaSharp does not compile using dotnet cake.
Basic Information

Version with issue:  2.88.4-preview, latest code on 24th July 2023. Windows 11.
Last known good version:  ?
IDE:  Visual Studio 2022 17.7 Preview 4.0 (installed) but I'm using dotnet cake from the command line prompt.

Any way to fix this issue?
Also, it is strange that the target framework is xamarinios1.0. I cannot find it here: https://learn.microsoft.com/en-us/dotnet/standard/frameworks.

This should no longer be an issue as the main branch now is almost entirely net7.0+. There are a few netstandards and net472. But, now you can use dotnet build everywhere too.

authors: TommiGustafsson-HMP mattleibow


text:
BMDB: Operator/debug CLI

We want a CLI to talk to a BMDB, first to at least query per-machine state, and export that state to some somewhat machine-parsable format.
This is expected to be used when troubleshooting the BMDB in production, but also as a stopgap measure for integrating the BMDB in some deployments (eg. exporting machine information to spreadsheets, etc).

We now have webug as a read-only debug tool. We still should have a CLI for mutating the state, but that's probably gonna be written as we realize what kind of operations we need to perform. Until then, we'll probably mostly use webug and manual SQL surgery.

repo: monogon-dev/monogon


text:
fixbug: signed >= unsigned  type error.

./match ^1+  abc123 should not match

./match ^1+ abc123
type: BEGIN
type: CHAR '1'
type: PLUS
no match
This returns "no match". Am I missing something?

Old code works fine for months, untilI I change to a new platform  yesterday .

arch:  armv71
os: alpine + glibc
kernel: 4.19.97
gcc: 8.3.0

on this platform, tre_match() goes into endless loop.
by painful gdb, the problem is here:

while (text - start >= min)
condition is true : -2 >= 0

back to x86.debian/centos , the same code runs without error.
some mechanisms prevenct this error. either x86/linux/gcc may have done the job.
the gdb raw data, can be reproduced on this special platform only.
(gdb) n
488             while (text - start >= min)
(gdb) l
483         unsigned min, unsigned max)
484     {
485             const char *end, *start = text;
486             while (max && text < tend && matchone(nodes, *text)) { text++; max--; }
487
488             while (text - start >= min)
489             {
490                     end = matchpattern(nodes + 2, text--, tend);
491                     if (end)
492                             return end;
(gdb) p end
$22 = 0x0
(gdb) p text
$23 = 0x4eeb4f ""
(gdb) p start
$25 = 0x4eeb50 "(123"
(gdb) n
490                     end = matchpattern(nodes + 2, text--, tend);
(gdb) p text
$26 = 0x4eeb4f ""
(gdb) p start
$27 = 0x4eeb50 "(123"
(gdb) n
491                     if (end)
(gdb) n
488             while (text - start >= min)
(gdb) n
490                     end = matchpattern(nodes + 2, text--, tend);
(gdb) p text
$28 = 0x4eeb4e "f"
(gdb) p start
$29 = 0x4eeb50 "(123"
(gdb) p min
$30 = 0
(gdb) p text - start
$31 = -2
(gdb) p text - start >= min
$32 = 1
(gdb) p -2 >= 0
$33 = 0
(gdb) p (text-start) >= min
$34 = 1
(gdb) p text-start
$35 = -2
(gdb) p min
$36 = 0
(gdb) p -2>=0
$37 = 0
(gdb) p text-start >=0
$38 = 0
(gdb) p text-start >= min
$39 = 1
(gdb) p -2 >= min
$40 = 1
(gdb) p -2 >= 0
$41 = 0

I guess gcc is the reason.  need more dig later.

gcc versions
compile options
arch

anyway, -2  >= unsigned 0  should be avoid.
and this pr fix the bug.

arm platform, with gcc type warning, result: error-match
# uname -a
Linux 8947ca906ef9 4.19.97-v7l+ #1294 SMP Thu Jan 30 13:21:14 GMT 2020 armv7l GNU/Linux
# gcc --version
gcc (Debian 8.3.0-6) 8.3.0
# make
gcc -O2 -Wall -Wextra -pedantic -std=c99 -o match match.c
In file included from match.c:5:
tre.h:60:3: warning: ISO C99 doesn't support unnamed structs/unions [-Wpedantic]
  };
   ^
In file included from match.c:5:
tre.h: In function 'matchquant':
tre.h:486:22: warning: comparison of integer expressions of different signedness: 'int' and 'unsigned int' [-Wsign-compare]
  while (text - start >= min)
                      ^~
# ./match ^x?1+  abc123
type: BEGIN
type: CHAR 'x'
type: QMARK
type: CHAR '1'
type: PLUS
match start: 0 match end: 4294967294

x86 machine without gcc warning, result: no-match
$ uname -a
Linux Win-FX 4.4.0-18362-Microsoft #476-Microsoft Fri Nov 01 16:53:00 PST 2019 x86_64 x86_64 x86_64 GNU/Linux
$ gcc --version
gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
$ make
gcc -O2 -Wall -Wextra -pedantic -std=c99 -o match match.c
In file included from match.c:5:0:
tre.h:60:3: warning: ISO C99 doesn’t support unnamed structs/unions [-Wpedantic]
  };
   ^
$ ./match ^x?1+  abc123
type: BEGIN
type: CHAR 'x'
type: QMARK
type: CHAR '1'
type: PLUS
no match

the question is , why second machine success.
-1>0u  is always true by my test on both machine.
more dig will be done next week.

Thanks. You are right. It is a problem when min is 0.
I made some wrong assumptions and gcc didn't warn about it.

final reason: this is 32bit vs 64bit problem.
by c standard's type implicit convertion rule :
https://en.cppreference.com/w/c/language/conversion

Otherwise, both operands are integers. Both operands undergo integer promotions (see below); then, after integer promotion, one of the following cases applies:

If the types are the same, that type is the common type.
Otherwise (the types are not the same): If the types have the same signedness (both signed or both unsigned), the operand whose type has the lesser conversion rank (see below) is implicitly converted to the other type.
Otherwise (the signedness is different): If the unsigned type has conversion rank greater than or equal to the rank of the signed type, then the operand with the signed type is implicitly converted to the unsigned type.
Otherwise (the signedness is different, and the unsigned type has conversion rank less than the signed type): If the signed type can represent all values of the unsigned type, then the operand with the unsigned type is implicitly converted to the signed type.
Otherwise: Both operands undergo implicit conversion to the unsigned type counterpart of the signed operand's type.

case-4.5 is the problem, this may causes data lost or overflow error
test code
int main() {
        unsigned int u0 = 0;
        int i1 = -1;
        long L1 = -1;

        printf("-1L>0u = %d\n",  L1 > u0);
        printf("-1i>0u = %d\n",  i1 > u0);

        char *p1 = "abc";
        char *p2 = p1 + 1;
        printf("pointer>0u = %d\n",  p1-p2 > u0);

        return 0;
}

on 32bit machine, pointer type is int32,
hit case-4.5, -1i converted to unsigned int: 4294967295
causes data overflow error.
-1L>0u = 1
-1i>0u = 1
pointer>0u = 1

on 64bit machine, pointer type is long(int64),
hit case-4.4, 0u coverted to 0L, everything works fine.
-1L>0u = 0
-1i>0u = 1
pointer>0u = 0

that's why old buggy code works fine for 99% machines without error.
but explode me 1% 😆
gcc warnings
with gcc flag -Wall -Wextra there should be
 warning: comparison between signed and unsigned integer expressions
but,,, some gcc versions drop this warning.
maybe they think implicit convertions without data lost is fine.
when changed to 32bit, same convertion may causing problems, they show the warning.
I dont like tools too smart. 😞

Thanks again for the explanation. There doesn't seem to be an option to trigger the warning other than compiling for different targets. I tried -Wsign-conversion but it didn't seem to apply in that case.

authors: fanlix monolifed

repo: monolifed/tiny-regex-mod

license: Unlicense


text:
"For the best experience with crow, consider its outputs to be control-rate generators"

Is this still true, now that Crow has official(?) support for audio-rate oscillation?
(issue credit @postsolarpunk)

hey hey!
That sounds good to me! Just wanted to post this for him. Thanks :)

wondering if we can close this?
while crow can output audiorate signals, it can only collect them at control rate (albeit quite fast at 1.5kHz). more importantly though, crow's API is designed around events & declarative structures. ie the intention is to describe an audiorate action, rather than do per-sample manipulation like a live-dsp platform.
either way, if we want to include this note, where should it go?

authors: trentgill zjb-s

repo: monome/docs


text:
Does not work

F:\proxy>python main.py
https://api.proxyscrape.com/v2/?request=getproxies&protocol=http | No proxies found | Status code 403
https://api.proxyscrape.com/v2/?request=getproxies&protocol=socks4 | No proxies found | Status code 403
https://api.proxyscrape.com/v2/?request=getproxies&protocol=socks5 | No proxies found | Status code 403
https://raw.githubusercontent.com/hanwayTech/free-proxy-list/main/socks5.txt | No proxies found
https://raw.githubusercontent.com/hanwayTech/free-proxy-list/main/socks4.txt | No proxies found
https://proxysearcher.sourceforge.net/Proxy List.php?type=socks | No proxies found
https://raw.githubusercontent.com/hanwayTech/free-proxy-list/main/https.txt | No proxies found
https://raw.githubusercontent.com/hanwayTech/free-proxy-list/main/http.txt | No proxies found
https://proxysearcher.sourceforge.net/Proxy List.php?type=socks | No proxies found
Traceback (most recent call last):
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\asyncio\runners.py", line 44, in run
return loop.run_until_complete(main)
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\asyncio\base_events.py", line 628, in
run_until_complete
self.run_forever()
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\asyncio\base_events.py", line 595, in
run_forever
self._run_once()
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\asyncio\base_events.py", line 1845, in
_run_once
event_list = self._selector.select(timeout)
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\selectors.py", line 324, in select
r, w, _ = self._select(self._readers, self._writers, [], timeout)
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\selectors.py", line 315, in _select
r, w, x = select.select(r, w, w, timeout)
ValueError: too many file descriptors in select()
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "F:\proxy\main.py", line 403, in
asyncio.run(main())
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\asyncio\runners.py", line 47, in run
_cancel_all_tasks(loop)
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\asyncio\runners.py", line 63, in
_cancel_all_tasks
loop.run_until_complete(tasks.gather(*to_cancel, return_exceptions=True))
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\asyncio\base_events.py", line 628, in
run_until_complete
self.run_forever()
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\asyncio\base_events.py", line 595, in
run_forever
self._run_once()
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\asyncio\base_events.py", line 1845, in
_run_once
event_list = self._selector.select(timeout)
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\selectors.py", line 324, in select
r, w, _ = self._select(self._readers, self._writers, [], timeout)
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\selectors.py", line 315, in _select
r, w, x = select.select(r, w, w, timeout)
ValueError: too many file descriptors in select()
Scraper :: HTTP   ---------------------------------------- 100% 42/42
Scraper :: SOCKS4 ---------------------------------------- 100% 21/21
Scraper :: SOCKS5 ---------------------------------------- 100% 23/23
Checker :: HTTP   ----------------------------------------   0%     0/21368
Checker :: SOCKS4 ----------------------------------------   0%    0/7759
Checker :: SOCKS5 ----------------------------------------   0%    0/4395  Exception ignored in: <coroutine object main at 0x0000020784BB02E0>
Traceback (most recent call last):
File "F:\proxy\main.py", line 369, in main
File "F:\proxy\main.py", line 316, in main
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\site-packages\rich\progress.py", line 1178, in exit
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\site-packages\rich\progress.py", line 1164, in stop
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\site-packages\rich\live.py", line 147, in stop
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\site-packages\rich\console.py", line 869, in exit
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\site-packages\rich\console.py", line 827, in _exit_buffer
File "C:\Users\Users\AppData\Local\Programs\Python\Python310\lib\site-packages\rich\console.py", line 2017, in _check_buffer
ImportError: sys.meta_path is None, Python is likely shutting down
Exception ignored in: <coroutine object Proxy.check at 0x0000020784BB3BC0>
Traceback (most recent call last):
File "F:\proxy\main.py", line 242, in check_proxy
RuntimeError: coroutine ignored GeneratorExit
Exception ignored in: <coroutine object Proxy.check at 0x0000020784CE8350>
Traceback (most recent call last):

Reinstall the latest version of Python and dependencies. This should help.

authors: Roboxkin monosans

repo: monosans/proxy-scraper-checker


text:
Error on @update

I'm receiving the following error when using the @update binding:
Uncaught TypeError: Cannot read property 'apply' of undefined
I have the component registered:
import Multiselect from 'vue-multiselect';
Vue.component('multiselect', Multiselect);

HTML:
<multiselect :id="$index" @update="updateSelectOptions" :options="postcodes" :selected="area.postcodes" :multiple="true" :searchable="true" label="postcode" key="id" :max-height="150"></multiselect>

The multiselect works perfectly it just gives the error when updating. Not sure if it is something to do with my webpack setup? This is what I can see when looking further into the error (not sure how helpful it is!)
(function(scope
/**/) {
return  scope.updateSelectOptions.apply(this,scope.$arguments);
})

That’s weird. Would you mind trying to register it locally?
Also, where is your updateSelectOptions method located?

Hey @scrwdnet! I managed to reproduce this problem locally.
The global component registration doesn’t cause any problems. Uff... :)
However, the problem happens when the updateSelectOptions method isn’t defined on the component, where the multiselect is used. Is the method defined in the same component the postcodes data is?

Hey @shentao just been looking into this for the past couple of hours, you are right I didn't have the method on the right component it was in a sibling component and I must have had a bad case of code blindness!
Thanks for taking the time to have a look into it for me. Would it be worth adding in a check for the method and throwing an error message if it doesn't exist might help someone in the future who is having a moment of madness!
Thanks again, it's a great component!

Haha! It happens to the best of us! :D
You’re right, but this is more a Vue related issue. Maybe you could suggest adding such error message to Vue?

Ahhh ok, yeah I'll bring up an issue and see if they can add something helpful :D

authors: scrwdnet shentao

repo: monterail/vue-multiselect


text:
Usage without ngrok

Is this just a case of removing these lines and setting up a reverse proxy on the machine to point at port 8000 on the response container?
https://github.com/monzo/response/blob/97e35de75cd78eb3b6cd4db0a2b3f99a5ce582c8/docker-compose.yaml#L40-L47

Yes, that would be fine.
You shouldn't even need to remove that though. The response container is accessible on localhost:8000 so you can stick whatever you like in front of it.

repo: monzo/response


text:
🛑 kmj.wtf is down

In 4abfd9d, kmj.wtf (https://kmj.wtf) was down:

HTTP code: 0
Response time: 0 ms

Resolved: kmj.wtf is back up in 358e0dd after 22 minutes.

repo: mooseburgr/kmj-wtf-upptime


text:
Allow NOC Addenda Type entries for WEB

What were you trying to do?
Attempting to load an ACH file, containing NOC entries for SEC Code WEB
What did you expect to see?
I expected to see a valid ach.File with the correct contents.
What did you see?
 *ach.BatchError: BatchNumber 1 TypeCode 98 found in addenda and expecting 98 for batch type WEB

How can we reproduce the problem?
// TestBatchWEBAddendum98 validates Addenda98 returns an error
func TestBatchWEBAddendum98(t *testing.T) {
	mockBatch := NewBatchWEB(mockBatchWEBHeader())
	mockBatch.AddEntry(mockWEBEntryDetail())
	mockBatch.GetEntries()[0].AddAddenda(mockAddenda98())
	if err := mockBatch.Create(); err != nil {
		t.Errorf("%T: %s", err, err)
	}
}

Will be fixed with issue # 323

repo: moov-io/ach


text:
Can't compile go 1.5.x anymore after I terminate the installation

I have terminate the go1.5.x installation once cause I want to install another version at that time. But after I terminate the process once. I can't install any go1.5.x on this machine anymore even I remove gvm and reinstall gvm. This is the error message:
##### Building Go bootstrap tool.
cmd/dist

##### Building Go toolchain using /home/user/.gvm/gos/go1.4.3.
bootstrap/internal/obj
bootstrap/internal/obj/arm
bootstrap/internal/obj/arm64
bootstrap/internal/obj/ppc64
bootstrap/internal/obj/x86
bootstrap/asm/internal/arch
bootstrap/asm/internal/flags
bootstrap/asm/internal/lex
bootstrap/asm/internal/asm
bootstrap/asm
bootstrap/compile/internal/big
bootstrap/internal/gcprog
bootstrap/compile/internal/gc
go build bootstrap/compile/internal/gc: /home/user/.gvm/gos/go1.4.3/pkg/tool/linux_amd64/6g: signal: killed
bootstrap/link/internal/ld
bootstrap/link/internal/amd64
bootstrap/link/internal/arm
bootstrap/link/internal/arm64
bootstrap/link/internal/ppc64
bootstrap/link/internal/x86
bootstrap/link
go tool dist: FAILED: /home/user/.gvm/gos/go1.4.3/bin/go install -v bootstrap/...: exit status 1

Same problem here, except it worked fine under my initial user. I made a new user and tried to install through gvm there, and got the error for go 1.5 and go 1.5.2

authors: cmcdaniels wmh

repo: moovweb/gvm


text:
Bug

If i dont have YACL installed you get the screen with 4 buttons but "open mod folder" and "close" are switched with eachother

Which version are you using? This should have been fixed in 1.6.4+1.19.4

1.19.3

Yeah you should consider updating to the 1.19.4 version. If you really need to use 1.19.3 you can just stay with this version (as the bug isn't breaking anything really) or try to use the 1.19.4 version in 1.19.3 but I don't really recommend that

authors: SamLeGgamer mooziii

repo: mooziii/tpshud-fabric