Added Spyder IDE Terminal as a xterm case-use application

At Spyder IDE organization we've implemented a embed version of xterm.js inside a Qt Widget, this project, named Spyder Terminal allows users to interact with a terminal inside the IDE

Coverage remained the same at 67.904% when pulling 365f9b4c1bb0a6175d005b1adc8853d4cf513d57 on andfoy:patch-1 into 2cf90d90f75f12164600836ef14d59a34b1de7f1 on sourcelair:master.

Awesome, thanks a lot @andfoy!


[commonjs--resolver] [plugin vite:resolve] Cannot bundle Node.js built-in "tty" imported from "node_modules/consola/dist/chunks/prompt.mjs". Consider disabling environments.ssr.noExternal or remove the built-in dependency

Describe the bug
I am trying to deploy a Astro v.5 project to Cloudflare. It uses Vite v.6 under the hood and I keep getting a build error (it worked on Astro 4 which uses Vite 5). Any ideas?
Astro Info
Astro                    v5.0.3
Node                     v20.15.0
System                   macOS (arm64)
Package Manager          npm
Output                   server
Adapter                  @astrojs/cloudflare
Integrations             @astrojs/tailwind
                         @astrojs/react

Describe the Bug
Trying to upgrade from v4 to v5 and build on it Cloudflare integration. Here is the build error:
17:15:48.511	16:15:48 [ERROR] [vite] x Build failed in 4.93s
17:15:48.741	[commonjs--resolver] [plugin vite:resolve] Cannot bundle Node.js built-in "tty" imported from "node_modules/consola/dist/chunks/prompt.mjs". Consider disabling environments.ssr.noExternal or remove the built-in dependency.
17:15:48.742	  Stack trace:
17:15:48.742	    at getRollupError (file:///opt/buildhome/repo/node_modules/rollup/dist/es/shared/parseAst.js:396:41)
17:15:48.742	    at Object.error (file:///opt/buildhome/repo/node_modules/rollup/dist/es/shared/node-entry.js:20622:20)
17:15:48.742	    at Object.handler (file:///opt/buildhome/repo/node_modules/vite/dist/node/chunks/dep-yUJfKD1i.js:50806:15)
17:15:48.742	    at async PluginDriver.hookFirstAndGetPlugin (file:///opt/buildhome/repo/node_modules/rollup/dist/es/shared/node-entry.js:20707:28)
17:15:48.742	    at async ModuleLoader.resolveId (file:///opt/buildhome/repo/node_modules/rollup/dist/es/shared/node-entry.js:19740:15)
17:15:48.792	Failed: Error while executing user command. Exited with error code: 1
17:15:48.838	Failed: build command exited with code: 1
17:15:50.145	Failed: error occurred while running build command

Here is the astro.config.mjs:
import cloudflare from '@astrojs/cloudflare';
import react from '@astrojs/react';
import tailwind from '@astrojs/tailwind';
import { defineConfig } from 'astro/config';

export default defineConfig({
  prefetch: true,
  output: 'server',
  server: { port: 3000 },
  adapter: cloudflare({ imageService: 'passthrough', platformProxy: { enabled: true } }),
  integrations: [tailwind({ applyBaseStyles: false }), react()],
  vite: {
    ssr: {
      external: ['node:process', 'node:tty', 'node:util', 'node:path', 'node:stream', 'node:buffer', 'node:readline'],
    },
  },
});

It threw errors for each of the added external node:* packages too (like need to update the docs). Web app deploys to Cloudflare using v4 without issues (https://www.websitefeedback.ai).
What's the expected result?
I expect the app to build without issues and/or the needed configuration be described in https://docs.astro.build/en/guides/integrations-guide/cloudflare.
Original issue: https://github.com/withastro/astro/issues/12670
Reproduction
https://stackblitz.com/edit/github-rewgio
Steps to reproduce
No response
System Info
System:
    OS: macOS 14.6.1
    CPU: (8) arm64 Apple M1
    Memory: 1.52 GB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.15.0 - /usr/local/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 10.9.0 - /usr/local/bin/npm
    pnpm: 9.14.2 - ~/Library/pnpm/pnpm
    bun: 1.0.2 - ~/.bun/bin/bun
  Browsers:
    Safari: 17.6

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

It looks like latest release added defaultServerConditions https://github.com/withastro/adapters/pull/465, but this includes node, so Vite picks up consola' s node entry, which perhaps uses tty<EMAIL_ADDRESS>I think we can close this in favor of Astro issue. cc @bluwy


Add Answers and Communities sections in Dashboard page

You have to make Answers and Community section in the Dashboard page of the Forum website.
Design is provided HERE
Guidelines

The code should be clean and reusable.
Make sure that you make components for code reusability.

Note

Make sure you follow the given template before making the pull request.

claim

Go ahead @TheDivineAurora 👍🏼

@TheDivineAurora update

Evening Tak time dedo sir 😓

@TheDivineAurora okay..

@TheDivineAurora updates?


Add python-dateutil==2.8.0 to unblock release

Notice

[x] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.

I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorised to submit this contribution on behalf of the original creator(s) or their licensees.

I certify that the use of this contribution as authorised by the Apache 2.0 license does not violate the intellectual property rights of anyone else.

Motivation and Context
Why was this PR created?
Pip dependency resolution installs python-dateutil==2.8.1 in CI, which is blocking the release.
As a temporary hack, we hardpin it in requirements.txt to unblock the release.
How has this been tested?
What testing strategies have you used?
CI
Checklist

[ ] Read the contributing guidelines
[ ] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Updated the documentation to reflect the code changes
[ ] Added new entries to the RELEASE.md file
[ ] Added tests to cover my changes
[ ] Assigned myself to the PR
[ ] Added Type label to the PR

interesting, I'm making the same change on pai, it would be good if your comment said which pacakge(s) were causing the issue, I'm guessing the main culprit is botocore

It's botocore requiring <2.8.1, pandas requiring >=2.6.0, and the latest version available being 2.8.1
So depending on the resolution order, pip either installs 2.8.0 and it's all cool, or 2.8.1 and it fails on the second package.
pip is shit :(


Dev - add forum post and comments feature

Luis, coloca lá as tuas rotas, controladores e model no server.js.


Gives an error when calling from the notes in the Ukrainian language.

Gives an error when calling any template to process one of the paragraphs, if the note is in Ukrainian (in the yaml alias is in English)
The same template, with the same content, in another temporary note, works successfully

not sure why is that


fix: Quote CL cmd in iCmd5250 for shell escaping

iCmd5250 is just a fancy wrapper around iSh, using the PASE system
command. It did not do any shell escaping/quoting, so it basically only
allowed calling CL commands without parameters or with only positional
parameters because the parentheses would cause the shell to gack.
eg.
iCmd5250('wrkactjob', 'WRKACTJOB SBS(QBATCH)')
basically became
iSh('wrkactjob', '/QOpenSys/usr/bin/system WRKACTJOB SBS(QBATCH)')
When executed, an error would be given from the shell:
sh: syntax error at line 1 : `(' unexpected
The proper fix is to quote the string, but that can be tricky to get
right. Luckily, Python has shlex.quote to do the hard work for us.
https://docs.python.org/3/library/shlex.html#shlex.quote
Fixes #49

@ranga543 Can you please test this? I was able to verify with this script:
from itoolkit import *
from itoolkit.transport import DirectTransport

itransport = DirectTransport()
itool = iToolKit()
itool.add(iCmd('aspgroup_cmd', 'SETASPGRP ASPGRP(TEST)'))
itool.add(iCmd5250('dspjob', 'DSPJOB'))

itool.call(itransport)

print(itool.dict_out('aspgroup_cmd'))

for line in itool.dict_out('dspjob')['dspjob'].split('\n'):
    if 'ASP' not in line:
        continue

    print(line)

@kadler I copied your code and tried it and that seems to be working.

@kadler Is there a way to capture error from iCmd5250 right now it's just throwing CPF ?
CPF9801: Object X in library X not found.
{u'aspgroup_cmd': {u'success': u'+++ success SETASPGRP ASPGRP(ARKONA99)'}, u'dspjob': {}}

@kadler any ideas ?


New version: OceanTurb v0.2.1

Registering package: OceanTurb
Repository: https://github.com/glwagner/OceanTurb.jl
Created by: @glwagner
Version: v0.2.1
Commit: 71bdb6d73fa12b21f0f5c1cff9e7206385eff555
Reviewed by: @glwagner
Reference: https://github.com/glwagner/OceanTurb.jl/commit/71bdb6d73fa12b21f0f5c1cff9e7206385eff555#commitcomment-37189022

@glwagner did you intend to skip a version?


Wrongly rendered code for nextflow schema

https://github.com/openpipelines-bio/openpipeline/blob/c4b39e32f9da10efb54ac3c85985b47f83f873f8/workflows/multiomics/multisample/nextflow_schema.json#L72-L76
This code block is rendered into the nextflow GUI, however it is represented as a string, i.e. "top_n_vars":"[50, 100, 200, 500]". The quotes mean that the this is represented as a string leading to the pipeline being unable to parse this as it expects a list of integers.

This should have been fixed by b741077dbb308e1c83a3b404e4d49b6f3cbff942


Slow performance using @azure/storage-queue compared to azure-storage

Package Name: @azure/storage-queue
Package Version: 10.1.0
Operating system: macOS 10.14.4
[x] nodejs

version: v8.12.0

[ ] browser

name/version:

[x] typescript

version: 3.4.5

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
Performance of @azure/storage-queue is significantly slower than azure-storage for sending individual messages.
Our use case is to use Azure Storage Queues for messaging between services, however, a simple test is showing that @azure/storage-queue is about 3x slower than azure-storage for inserting individual messages into a queue.
To Reproduce
Steps to reproduce the behavior:

Clone https://github.com/csuich2/azure_queue_perf
export SA_NAME=<sa_name>
exportexport SA_KEY=<sa_key>
npm i
npm run oldqueue
npm run newqueue

Expected behavior
Performance with the new queue library should be closer if not better than that of the old queue library.
Screenshots
Example output when run on an Ubuntu VM in the same Azure region as the SA
Old queue library:
Create queue queuetest1556323061402 successfully
publish: dur: 20ms avg: 20ms
publish: dur: 8ms avg: 14ms
publish: dur: 12ms avg: 13.333333333333334ms
publish: dur: 8ms avg: 12ms
publish: dur: 8ms avg: 11.2ms
publish: dur: 9ms avg: 10.833333333333334ms
publish: dur: 18ms avg: 11.857142857142858ms
publish: dur: 8ms avg: 11.375ms
publish: dur: 9ms avg: 11.11111111111111ms
publish: dur: 14ms avg: 11.4ms
publish: dur: 10ms avg: 11.272727272727273ms
publish: dur: 7ms avg: 10.916666666666666ms
publish: dur: 8ms avg: 10.692307692307692ms
publish: dur: 9ms avg: 10.571428571428571ms
publish: dur: 8ms avg: 10.4ms
publish: dur: 8ms avg: 10.25ms
publish: dur: 6ms avg: 10ms
publish: dur: 6ms avg: 9.777777777777779ms
publish: dur: 9ms avg: 9.736842105263158ms
publish: dur: 7ms avg: 9.6ms
Delete queue successfully

New queue library:
Create queue queuetest1556323151712 successfully, service assigned request Id: 63a10b99-8003-0020-6c8c-fca483000000
publish: dur: 45ms avg: 45ms
publish: dur: 25ms avg: 35ms
publish: dur: 30ms avg: 33.333333333333336ms
publish: dur: 33ms avg: 33.25ms
publish: dur: 27ms avg: 32ms
publish: dur: 49ms avg: 34.833333333333336ms
publish: dur: 23ms avg: 33.142857142857146ms
publish: dur: 28ms avg: 32.5ms
publish: dur: 34ms avg: 32.666666666666664ms
publish: dur: 30ms avg: 32.4ms
publish: dur: 24ms avg: 31.636363636363637ms
publish: dur: 25ms avg: 31.083333333333332ms
publish: dur: 31ms avg: 31.076923076923077ms
publish: dur: 38ms avg: 31.571428571428573ms
publish: dur: 26ms avg: 31.2ms
publish: dur: 29ms avg: 31.0625ms
publish: dur: 52ms avg: 32.294117647058826ms
publish: dur: 27ms avg: 32ms
publish: dur: 21ms avg: 31.42105263157895ms
publish: dur: 33ms avg: 31.5ms
Delete queue successfully, service assigned request Id: 8eb5ee15-e003-0019-808c-fce427000000
Successfully executed sample.

Thank you for opening this issue! We are routing it to the appropriate team for follow up.
CC: @vinjiang, @AlexGhiondea

Ignore this comment

@vinjiang can you take a look.

/cc @XiaoningLiu

This is expected because new JS SDK cannot enable HTTP connection keep-alive, while old SDK enables by default.
@kpajdzik is planning to add keep-alive support for SDK HTTP client, but not ready yet.

Close this issue as answer provided. Please reopen if there is still question.


Use testcase-scoped variables

...because unnecessary package-level variables are a no-no.

/hold
in case the tests are flaky and you're still working on something, but this looks like nice cleanup work.  Thanks!
/lgtm

/hold in case the tests are flaky and you're still working on something, but this looks like nice cleanup work. Thanks! /lgtm

Thanks! It is a flake, but doesn't seem to be one I caused. Re-running...

/unhold

@gparvin The merge is waiting for a GitHub review also.


hysteria: 2.2.2 -> 2.2.3

Diff: https://github.com/apernet/hysteria/compare/app/v2.2.2...app/v2.2.3
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.


Add GitHub link in footer

Is your feature request related to a problem? Please describe.
I want to add a GitHub link in the footer section.

Describe the solution you'd like
I will add a link to Github account in the footer section.
Describe alternatives you've considered
No response
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Github link is already there on the navbar


Implement no discard error for return values

Search Terms
nodiscard , check return , must use, must inspect result , warn unused result , check return value
Suggestion
Allow marking functions who's return value should not be discarded, like c++ [[nodiscard]] attribute https://en.cppreference.com/w/cpp/language/attributes/nodiscard
Nodiscard function/method
Annotate function/method with nodiscard then its return value should never be discarded
Nodiscard type
Annotate class , interface ,enum ,and/or type can be annotated with nodiscard then  , if any function returns value of that type  ,then returned value  should never be discarded
what if user wants to discard the value any way
user can use same ts-ignore override compiler error
Use Cases

If a function returns error_code programmer always need to check for errors before proceeding to next step
If a function returns Observable programmer always need to subscribe that or need call that function as Observables are evaluated only on subscribe.

Examples
This is purely conceptual (I have no idea which syntax will suit this)
Function/Method
function someCalulation():ErrorCode [[nodiscard]]{}
const error = someCalculation(); // good builds
someCalculation(); // compiler error return value discarded

Type
class VeryImportant [[nodiscard]]{}
function someCalulation():VeryImportant {}
const error = someCalculation(); // good builds
someCalculation(); // compiler error return value discarded

Checklist
My suggestion meets these guidelines:

[ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code (it depends on syntax which need to be decided)
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

Duplicate of #8240

@ajafff  #8240 is closed may be #8584 is more appropriate issue
also I have edited description with more search terms which i failed to add before


installing an R package gives error

install.packages("corrgram")
results in
Installing package into '/usr/local/lib/R/site-library'
(as 'lib' is unspecified)
Warning in install.packages("corrgram") :
'lib = "/usr/local/lib/R/site-library"' is not writable
with the container

Are you able to install packages from base R and load them in Beaker? I know this issue is old, but I am trying to do so now with the new docker container, and am still receiving this error above.

The instructions for installing packages in the docker container are in the docker wiki: https://github.com/twosigma/beaker-notebook/wiki/Running-the-Docker-Container

I see. I tried installing dplyr from CRAN into my container, and when I try to load it via the library command, I get the following error:

Error in library.dynam(lib, package, package.lib) :
shared object 'dplyr.so' not found
In addition: Warning message:
S3 methods '[.fun_list', '[.grouped_df', 'all.equal.tbl_df', 'anti_join.data.frame', 'anti_join.tbl_df',
-Error : package or namespace load failed for 'dplyr'

Am I supposed to load the package in my bash script as well? I noticed in some notebooks you can load the package in Beaker, so I'm just trying to make sure I understand this.


Issue with failing TokenUpdateNftsTransaction

Hey team.
We're seeing an issue with failing transactions in the Hedera WalletConnect repo as described here: https://github.com/hashgraph/hedera-wallet-connect/issues/265
It looks as if the error is stemming from this line:
https://github.com/hashgraph/hedera-sdk-js/blob/ba47014e129cca1125e1a143b677ed9bba43439c/src/token/TokenUpdateNftsTransaction.js#L104
Before we continue further investigations, could someone please verify that this line is correct. It appears as if it's not accessing the correct data key. I'm not familiar enough with this code, but it feels like the data key should be this instead:
body.tokenUpdateNfts

as defined here:
https://github.com/hashgraph/hedera-sdk-js/blob/ba47014e129cca1125e1a143b677ed9bba43439c/src/token/TokenUpdateNftsTransaction.js#L195-L197
Any input would be appreciated as it's hard to see what else is wrong from the Hedera WalletConnect side. Many thanks!

Hi Justyn,
I hope you're doing well! I took some time to investigate the issue and cloned Nadine's repo to see if I could reproduce the problem. I was able to replicate the same behavior. However, I also tested the functionality in the SDK environment (please see the examples below) and it appeared to work without any issues at first glance.
It’s worth noting that this feature is currently being utilized successfully by other users and wallets, and it seems to be functioning correctly in those contexts.  If you haven’t been able to find the issue elsewhere, we will investigate deeper into it. Just let me know how you’d like to proceed :))
SDK environment example:
import {
    Client,
    PrivateKey,
    AccountId,
    TransactionId,
    TokenType,
    TokenCreateTransaction,
    TokenMintTransaction,
    LocalProvider,
    TokenUpdateNftsTransaction,
    Wallet,
} from "@hashgraph/sdk";

import dotenv from "dotenv";
dotenv.config();

async function main() {
    if (process.env.OPERATOR_ID == null || process.env.OPERATOR_KEY == null) {
        throw new Error(
            "Environment variables OPERATOR_ID, and OPERATOR_KEY are required.",
        );
    }
    const operatorId = AccountId.fromString(process.env.OPERATOR_ID);
    const operatorKey = PrivateKey.fromStringED25519(process.env.OPERATOR_KEY);

    const client = Client.forTestnet().setOperator(operatorId, operatorKey);

    const provider = new LocalProvider();

    const wallet = new Wallet(
        process.env.OPERATOR_ID,
        process.env.OPERATOR_KEY,
        provider,
    );

    const createNft = async () => {
        const supplyKey = PrivateKey.generateED25519();
        const metadataKey = PrivateKey.generateED25519();

        const tokenCreateTx = await new TokenCreateTransaction()
            .setTokenName("TestToken")
            .setTokenSymbol("TEST")
            .setTokenType(TokenType.NonFungibleUnique)
            .setTreasuryAccountId(wallet.accountId.toString())
            .setAutoRenewAccountId(wallet.accountId.toString())
            .setAutoRenewPeriod(7776000)
            .setSupplyKey(supplyKey.publicKey)
            .setMetadataKey(metadataKey.publicKey)
            .setTransactionId(
                TransactionId.generate(wallet.accountId.toString()),
            )
            .freezeWithSigner(wallet);

        const txResult1 = await tokenCreateTx.executeWithSigner(wallet);
        const nftCreateRx = await txResult1.getReceipt(client);
        const tokenId = nftCreateRx.tokenId;

        console.log("NFT created! Token Id" + tokenId);
        console.log("MetadataKey:" + metadataKey);
        return { tokenId, metadataKey, supplyKey };
    };

    const mintNft = async (tokenId, supplyKey) => {
        const metadataBytes = new TextEncoder().encode(
            "QmbokN1onYuUHCUagbUApmd3zsw2xgN1yoJ8ouHnb1qApu",
        );
        const tokenMintTx = new TokenMintTransaction()
            .setTokenId(tokenId)
            .addMetadata(metadataBytes);

        await tokenMintTx.freezeWithSigner(wallet);
        console.log("Signing NFT with MetadataKey....");
        const signedTokenMintTx = await tokenMintTx.sign(supplyKey);
        console.log("NFT signed!");

        const txResult = await signedTokenMintTx.executeWithSigner(wallet);
        const nftMintRx = await txResult.getReceipt(client);
        const supply = nftMintRx.totalSupply;
        console.log(
            `NFT minted with TokenId: ${tokenId}. New total supply is ${supply}`,
        );

        return txResult ? txResult.transactionId : null;
    };

    const metadataUpdate = async (
        tokenId,
        serialNumber,
        newMetadata,
        metadataKey,
    ) => {
        const newMetadataUri = new TextEncoder().encode(newMetadata);

        const updateTransaction = new TokenUpdateNftsTransaction()
            .setTokenId(tokenId)
            .setSerialNumbers([serialNumber])
            // @ts-ignore
            .setMetadata(new TextEncoder().encode(newMetadataUri));

        await updateTransaction.freezeWithSigner(wallet);
        const signedUpdateTx = await updateTransaction.sign(metadataKey);

        const txResult = await signedUpdateTx.executeWithSigner(wallet);
    };

    try {
        const newMetadata = "The input text field ";
        // Create the NFT and get tokenId and metadataKey
        console.log("Creating NFT...");
        const { tokenId, metadataKey, supplyKey } = await createNft();

        // Mint the NFT using the tokenId from the create step
        console.log("Minting NFT...");
        const serialNumber = await mintNft(tokenId, supplyKey);

        // Update the metadata after minting the NFT
        console.log("Updating metadata...");
        await metadataUpdate(tokenId, serialNumber, newMetadata, metadataKey);

        console.log(
            "NFT creation, minting, and metadata update completed successfully.",
        );
    } catch (error) {
        console.error(error);
    }

    client.close();
}

void main();


Obsolete / not maintained by the author

From: mobilPay<EMAIL_ADDRESS>Subject: Compatibilitate OpenCart 2.3.x
Pe GitHub nu au mai fost actualizate modulele. Va rugam sa accesati https://admin.mobilpay.ro/ sectiunea Implementare→Exemple de implementare si sa descarcati de acolo modulul pentru plata card - OpenCart, in arhiva comuna exista si o varianta pentru v.2.3.x .
Va multumim.
https://suport.mobilpay.ro/index.php?/Knowledgebase/List/

@andreipanait - instead of silently marking the issue as invalid and closing it, afterwards uploading an updated version after 2 years of the project being unmaintained you could instead mention in a comment that you have uploaded an updated version and maybe comment on how you are planning to keep the project on GitHup up-to-date so that users are not being confused.
Add files via upload
andreipanait committed on GitHub 11 minutes ago
https://github.com/mobilpay/opencart/commit/7d57de3b7a6f41fa1b211013e2d2c842f15f07a2

You must have missed the update on July 1st 2016...

@andreipanait the update you refer to a fix for the certificate loading routine to allow sandbox testing https://github.com/mobilpay/opencart/commit/a146be83efa66d4a1e36d0aa0f11a0d9e4495bb9
There are no other commits since Dec 3, 2014.
The module downloaded from the MobilPay admin section contains mods for OC versions:

v.1.5.x - 1.9.x
v.2.0.x - 2.2.x
v.2.3.x

Compare the commits history of the MobilPay OC mod on GitHub https://github.com/mobilpay/opencart/commits/master with the OpenCart releases schedule https://github.com/opencart/opencart/releases
There is a clear conclusion that the module was maintained out of GitHub and was offered only internally to the customers from the MobilPay Admin section. While at the same time the project on GitHub was not maintained for years, exactly what the issue refers to.
Since the MobilPay Admin section is very difficult to use, and does not allow to see a versions history, compatibility notes, etc. a developer/implementor would naturally prefer to use GitHub for this, will find the official repository and will stumble upon the unmaintained project - this is why the issue was submitted, to prevent users from downloading an outdated/unmaintained module code.

Additionally, the folder structure you have created with the most recent upload introduces even more confusion and does not reflect the folder structure of the official module download from the MobilPay Admin section:

v.1.5.x - 1.9.x
v.2.0.x - 2.2.x
v.2.3.x

Thus it is difficult/ambiguous for a developer to chose a correct compatible version from this repository.

@andreipanait https://pbs.twimg.com/media/CwahMkiXcAEJXte.jpg:large

Good, I get it, you have a lot of time, we don't.


config: enable the format checker for tidb repos

The format checker will make sure the PR body contains the issue number, the the rules will be enable for the following repos:

pingcap/tidb
pingcap/tidb-tools
pingcap/tidb-binlog
pingcap/ticdc
pingcap/ng-monitoring

Regex test on: https://regex101.com/r/3DGhNN/1/

/hold

cc: @zhangyangyu

/merge

/unhold

@amyangfei @kennytm @tiancaiamao @lance6716 PTAL~
Please also make sure that the PR modified PR template in each repository to be merged, avoiding the rules of the bot reminder and the PR template does not match.

https://github.com/pingcap/tidb/pull/30817
https://github.com/pingcap/tidb-tools/pull/568
https://github.com/pingcap/tidb-binlog/pull/1099
https://github.com/pingcap/tiflow/pull/3968
https://github.com/pingcap/ng-monitoring/pull/65

/LGTM

config: ignore the PR on release branches or created before 2021/12/27

cc @amyangfei @glorv

/merge

/unhold


Dynamic Namespace Cfg using Mins (not Nanos)

Usability tweak for kv configuration ~ using mins rather than nanos in the config parameters.
Adding tests (unit/prop)

Coverage decreased (-0.2%) to 78.148% when pulling fd4519419c951eb7068cab03236f7d3d0a718fb4 on prateek/ns-isolation-cfg-mins into 2ae02904d75c7a05342787e8a6d0b1be452af4e4 on prateek/ns-isolation.

Coverage increased (+0.05%) to 78.38% when pulling c6c152d72565960748e5f9c4fad822001434648d on prateek/ns-isolation-cfg-mins into 2ae02904d75c7a05342787e8a6d0b1be452af4e4 on prateek/ns-isolation.

Coverage increased (+0.03%) to 78.356% when pulling 52ff5cdb1199bd3b3c691f887fc3935cf3db8169 on prateek/ns-isolation-cfg-mins into fa5ee9e50605d345af6dc283b3778eea50a2912e on prateek/ns-isolation.

I'm not opposed to the tests, but the change from nanos to minutes change seems to remove the ability to use sub-minute block sizes, etc.  Which might be useful in embedded cases, etc.
It'd be better to simply make the tooling better rather than the underlying datastructures more friendly (i.e. make the tooling have an hours, minutes, seconds, etc flag or take a time.Duration using time.ParseDuration to be able to specify "1m10s" etc).

@robskillington that's fair, there's no need to loose generality here. addressed in the new patch

Coverage decreased (-0.07%) to 78.255% when pulling af134d76e5c1eb77cafee17fe7cbb20f01cbcf38 on prateek/ns-isolation-cfg-mins into fa5ee9e50605d345af6dc283b3778eea50a2912e on prateek/ns-isolation.


[Bug]:

Issue description
I have the app connected to my Ledger wallet and after the latest update 1.3.3 I can't log in. The screen stays on the butterfly fluttering and after a while the screen goes blank, but it does not enter the application.
Expected behaviour
Help to access my funds
Actual behaviour
I went into the application to get the shipping address for a transaction, I had to connect the Ledger to validate the address and I sent the coins. Before receiving the funds and without disconnecting the Ledger I started the update process because I saw the notice of the new update available. The application restarted and I could not log in anymore.
Can the issue reliably be reproduced?
No
Steps to reproduce the issue
I don't know how it could be reproduced
Diagnostics
No response
Errors
No response
Duplicate declaration

[X] I have searched the issues tracker this issue and there is none

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Do you use windows?

Same here .. i created a Profil .. set up my ledger and transfer some MIOTAs to the seed .. now it wont open .. it stays on the butterfly and my Pin is correct .. i hope that my IOTAs arent trash .. :(

Don't worry your tokens are stored on nodes in the network. Firefly is just the GUI to connect to a node.
Can you try to restore your profile? Create a new profile -> recover wallet -> Ledger backup -> Firefly ledger backup.

Wow!!! thank you very much. it was very simple and everything works correctly. How can I delete the profiles that have stopped working?

Don't worry your tokens are stored on nodes in the network. Firefly is just the GUI to connect to a node.
Can you try to restore your profile? Create a new profile -> recover wallet -> Ledger backup -> Firefly ledger backup.

I`ll try it later .. Hope that it works for me .. like @Bewater2140 down below ..

Wow!!! thank you very much. it was very simple and everything works correctly. How can I delete the profiles that have stopped working?

That works for me too .. i have restored my Wallet with a new Profil ..

Seems related to #2343 which I converted from a discussion, but they were able to begin staking before Firefly froze on them. I am able to reproduce this bug with a new Firefly Ledger profile.

Create a profile with Ledger
Generate address with Ledger
Send to address
Firefly freezes and funds aren't updated
Opening Firefly again and accessing Ledger profile never passes loading screen (but accessing non-ledger profiles still works)

@Bewater2140
In the next release of Firefly you will also be able to delete profiles with balances. In the meantime you can go to C:\Users\[username]\AppData\Roaming\Firefly\__storage__. There you can delete the profile you want to delete.

@Bewater2140 In the next release of Firefly you will also be able to delete profiles with balances. In the meantime you can go to C:\Users\[username]\AppData\Roaming\Firefly\__storage__. There you can delete the profile you want to delete.

Perfect. Just deleted it and the restored Profil works as it should. Thx!

@Bewater2140 In the next release of Firefly you will also be able to delete profiles with balances. In the meantime you can go to C:\Users\[username]\AppData\Roaming\Firefly\__storage__. There you can delete the profile you want to delete.

Everything solved and working correctly.
Thank you very much for the quick and efficient response. I congratulate you for the work you do, keep up the good work!
And by the way, I find the staking system a bit strange, when you delegate new coins, first you get back all the staked and then send all the coins again, wouldn't it be easier to simply add the coins to the staking, as the other protocols do?

Closing this because I created issue #2345 that encompasses this bug and similar ones.


is this project still maintained? [Answer: Yes]

is this project still maintained? are there alternatives or forks available?

I believe no. Which is a shame.

@LunaticMuch it is shame. This voyager api tool is really one of the best web tools I've seen or used.

@iambumblehead @LunaticMuch Thanks for the kind words about our project 😊
We have big plans for moving this project forward but it requires a lot of work hours together with day-to-day maintenance.
So we are in the process of finalizing a solution that will give us the necessary financing.
I will keep this issue open and will update you here.

Feel free to get to get in touch for any help.
On 19 Mar 2021, 14:28 +0000, Ivan Goncharov @.***>, wrote:

@iambumblehead @LunaticMuch Thanks for the kind words about our project 😊
We have big plans for moving this project forward but it requires a lot of work hours together with day-to-day maintenance.
So we are in the process of finalizing a solution that will give us the necessary financing.
I will keep this issue open and will update you here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@IvanGoncharov that is great news! thank you for your response :)

@IvanGoncharov I've been using this on a project over the last year and love it. Any chance you could create a new release with what is in the master branch? I see a lot of improvements on the live demo from what I see in 1.0.0-rc.31. Thanks!

@IvanGoncharov it's been a while and I'm wondering if you can give another update

Update: APIs.guru (as a consulting company) died years ago. My attempts to find financing by merging APIs.guru projects into another company failed. I discussed this situation with Roman (co-author) and he gave me full rights to this project.
Currently, I work at Apollo full-time but I have some spare time on weekends. So I will try to contribute and accept external contributions regularly. I moved all projects related to GraphQL to my personal account as a first step. Next weekend I plan to do basic cleanup on projects and update dependencies.

hi,
wouldn't this be a nice addition to apollo studio anyway? As far as I am aware, there is no visual representation of the graph in apollo studio:

despite the fact that the icon indicates a graphical representation 😉:

maybe you could pitch that on the team...?

@macrozone correct, there's not but this should be asked to Apollo directly. Not sure they might want.

@macrozone correct, there's not but this should be asked to Apollo directly. Not sure they might want.

(i mentioned it because @IvanGoncharov works at apollo 🤓 )

(i mentioned it because @IvanGoncharov works at apollo 🤓 )

I know, that's why it should be better asked from outside 😉

(i mentioned it because @IvanGoncharov works at apollo 🤓 )

I know, that's why it should be better asked from outside 😉

true, i opened a FR: https://github.com/apollographql/apollo-feature-requests/issues/337

Recently, Voyager saw quite a big push with the 1.0.0 release 🎉
So I want to use this opportunity and Voyager users to help my country to fight this war 🇺🇦
I set up OpenCollective: https://opencollective.com/graphql-voyager
All collected money after expenses goes to Ukrainian paramedics deployed alongside troops.
cc: @iambumblehead @LunaticMuch @ifnull @alfaproject @dp28 @macrozone


LZ self-played games for AQ training

<!--
Thank you for reporting issues.
Since the developer is so busy, please understand that unimportant questions or requests may not be responded.

[Before adding an issue]
Please search and check if there are similar issues and questions, including those already closed.

[How to add a new issue]
**Title**
Make it possible to grasp the content of the issue by title only.

  Good: 'Resigns immediately on handicap games'
  Bad: 'some questions', 'a bug'

**Comments**
Please write the contents concisely.
Do not include multiple topics in one issue.

In the case of a bug, please describe the following contents.
+ Execution environment (AQ ver. / OS / CPU / GPU)
+ Reproduction procedure (in detail as much as possible)
+ How to fix it (if you have an idea)

**Labels** (able to attach from the right setting list)
'question': just a question
'enhancement': request for additional functions and improvement
'bug': a bug

Other labels will be judged by the developer, so the reporter should not use it.
--!>
I raised the issue before when LZ was very weak compared to AQ. Now LZ is becoming stronger and stronger.  Its latest 1 million games are on par with high level pros.  I think training with those may help to improve AQ's strength further.

This issue mentions an older version, or hasn't been discussed in a long time, so we close it.


chore(ci) add unreleased image tests

Add test jobs for the latest unreleased images.

Codecov Report
Base: 53.39% // Head: 40.13% // Decreases project coverage by -13.25% :warning:

Coverage data is based on head (b4ab8c0) compared to base (da154a4).
 Consider uploading reports for the commit 4bc7a21 to get more accurate results

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #242       +/-   ##
===========================================
- Coverage   53.39%   40.13%   -13.26%
===========================================
  Files          46       46
  Lines        4178     4178
===========================================
- Hits         2231     1677      -554
- Misses       1470     2196      +726
+ Partials      477      305      -172

Flag
Coverage Δ

2.0.5
40.13% <ø> (ø)

2.1.4
39.99% <ø> (ø)

<IP_ADDRESS>
?

<IP_ADDRESS>
?

2.2.2
39.99% <ø> (ø)

2.3.3
39.99% <ø> (ø)

<IP_ADDRESS>
?

2.4.0
39.99% <ø> (ø)

<IP_ADDRESS>
?

2.5.1
39.99% <ø> (ø)

<IP_ADDRESS>
?

2.6.0
39.99% <ø> (ø)

<IP_ADDRESS>
?

2.7.0
39.99% <ø> (ø)

<IP_ADDRESS>
?

2.8.0
39.99% <ø> (ø)

<IP_ADDRESS>
?

3.0.0
39.32% <ø> (ø)

<IP_ADDRESS>
?

community
40.13% <ø> (ø)

enterprise
?

integration
40.13% <ø> (-13.26%)
:arrow_down:

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

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


perf(fetcher): backoff retry in get transactions

PR Description
This PR updates the transaction fetching mechanism to use an exponential backoff strategy when retries are necessary. Previously, the system would attempt a maximum of five retries with no delay between them. With the new changes, the delay between retries increases exponentially.

@raphjaph this is my first attempt contributing to the repo. It would be great if you have a look at this PR. Thank you

oh my mistake. Lets me just close this PR for now


Incorrect default value placeholders on host edit form

Defect description

Create ~/.ssh/config file with the following contents:

Host localhost
    HostName <IP_ADDRESS>
    User override-user

Open goto and create a host with similar parameter, but leave Login field untouched.
Notice that the placeholder of Login field contains your actual login instead of override-user as it is defined in ~/.ssh/config.

Also blocks IMPROVEMENT-47 as goto will not display proper ssh key name in the status line.


requests must be installed to use this module

Hi,
I use python3 for ansible with var ansible_python_interpreter=/usr/bin/python3 on my mac.
I got msg when ansible was trying to create A-record in DNS server:
requests must be installed to use this module.
Requests of course is installed.
❯ python3 -m pip list  | grep requests
requests     2.25.1

what is wrong?

lol. it appeared because I had two python3 (/usr/bin/python3 and /usr/local/bin/python3) and for /usr/bin/python3 requests had not been installed

you may close ;)

problem still exist ;)

You need to install the python requests module in the environment where the ansible playbook is being run. For example, if I am running this as part of a role from localhost against desthost then the python requests module should be installed in the python environment on localhost.


Open-vocabulary LVIS performance when using all ImageNet-21k classes?

Hi,
Thanks for publishing Detic, very interesting work!
As far as I can tell, the LVIS numbers in the paper were all obtained using image-level data that only contains classes overlapping with LVIS (i.e. "IN-L", or CC captions containing LVIS classes).
What is the LVIS performance when image-level data covering all 22000 ImageNet-21k-classes is used for training? Sorry if this is in the paper and I missed it!
Thanks,
Matthias

Hi,
Thank you for your interest! The results are not in the paper. I attached them below:

LVIS box mAP
LVIS box mAP rare
Objects365 box mAP
OpenImages box mAP50

Box-Supervised
45.0
39.2
19.1
46.2

Detic w. IN-L
46.7
45.1
21.2
53.0

Detic w. IN-21K
45.0
41.2
21.4
55.2

Detic w. IN-21K is worse than Detic w. IN-L on LVIS as expected, due to less-focused vocabulary in training. It still outperforms the Box-supervised baseline on rare classes.
Best,
Xingyi

Thanks for sharing these results!


Update actions/runner by Renovate

This will add a config to continuously update actions/runner by Renovate.

https://github.com/actions-runner-controller/actions-runner-controller/issues/416

Test
I tested this config in my forked repository as https://github.com/int128/actions-runner-controller/pull/21.
Note that Renovate will send pull requests besides actions/runner.
See also the pull requests https://github.com/int128/actions-runner-controller/pulls.
For maintainers
You can install Renovate GitHub App into the organization from https://github.com/apps/renovate.
Thanks.

Could we also get the automerge property included, I think we are safe to have this just merge immediately and I think it will help with stability for people. Consumers of our runners can then auto patch their custom runners when a new version of our runner is published automatically.
https://docs.renovatebot.com/configuration-options/#automerge

It is possible to enable automerge only for actions/runner. I will add a commit.
This config will raise pull requests for all dependencies.


Site doesnt work in Google chrome

The site not opening in google chrome
What to do?>>

Closing because there's not enough information. Maybe duplicate of #1157.

same stuff over there

are you kiddin me?? you answered after several month!!!
and it STILL dont work!
https://pastenow.ru/f047a6a80d0d32d89945579103609ff5
[image: image.png]
ср, 12 сент. 2018 г. в 9:50, mouchin777<EMAIL_ADDRESS>
same stuff over there
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Codewars/codewars.com/issues/1181#issuecomment-420532497,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJCKiKDEMSKwdefMCmX_oLaHgQRSov-Iks5uaK6lgaJpZM4P7EMu
.


New version: LilithGames.Dislyte version 0.04

Pull request has been created with komac v2.6.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Hi @solomoncyj,
The package didnt't result in any application files reaching the VM. Are installer switches needed?


May I ask if there is a way to know which menu item was clicked on

I want to know if I clicked on the user menu, or library.
I want to match with the region of Prism

Not right now, could be done later

Not right now, could be done later

Do you have a plan? please

Not right now, could be done later

I am looking forward to this feature

I don't write code on my spare time to have deadlines so I have no 'plan'
But I added the idea in my todo list in my notes app at the deepest point of my phone, that's the best I can offer :)

I don't write code on my spare time to have deadlines so I have no 'plan'
But I added the idea in my todo list in my notes app at the deepest point of my phone, that's the best I can offer :)

Cool, thank you
I am looking forward to it

In new nuget package 4.7.1, there is a "MenuItemChanged" event in the SIdeMenu that is triggered everytime the MenuItem change, the event has the header string has argument


Crash when passing a dataframe containing NaT back to Excel

Passing a dataframe containing a pandas NaT causes Excel to crash.

Fixed in 9f2d236902b586214717f54a7733b73d941095ea


Version up KUMA_VERSION from 0.7.1 to 0.7.2

Signed-off-by: Yuiko Mori<EMAIL_ADDRESS>PR Details
This PR fixes kuma version  to 0.7.2 in:

vagrant/Vagrantfile
vagrant/README.md
kubernetes/README.md

@YuikoTakada sorry for the late merge! Thanks for contributing and helping us bump versions.


Add additional agent info

Request info: https://github.com/actions/virtual-environments-internal/issues/208
Provide more virtual environment details in the runner.

The OS version
The image version
A link to the markdown file with image details

Default file path for imagedata.json:

Name
Path
Packer Variable
Packer script

Ubuntu 16.04
/imagegeneration/imagedata.json
imagedata_file
installers/preimagedata.sh

Ubuntu 18.04
/imagegeneration/imagedata.json
imagedata_file
installers/preimagedata.sh

Windows Server 2016
C:\imagedata.json
imagedata_file
Installers/Update-ImageData.ps1

Windows Server 2019
C:\imagedata.json
imagedata_file
Installers/Update-ImageData.ps1

macOS 10.15
/Users/runner/imagedata.json
-
preimagedata.sh

Example imagedata.json output:
Ubuntu 16.04
[
  {
    "group": "Operating System",
    "detail": "Ubuntu\n16.04.6\nLTS"
  },
  {
    "group": "Virtual Environment",
    "detail": "Environment: ubuntu-16.04\nVersion: 20200301.1\nIncluded Software: https://github.com/actions/virtual-environments/blob/ubuntu16/20200301.1/images/linux/Ubuntu1604-README.md"
  }
]

Ubuntu 18.04
[
  {
    "group": "Operating System",
    "detail": "Ubuntu\n18.04.4\nLTS"
  },
  {
    "group": "Virtual Environment",
    "detail": "Environment: ubuntu-18.04\nVersion: 20200301.1\nIncluded Software: https://github.com/actions/virtual-environments/blob/ubuntu18/20200301.1/images/linux/Ubuntu1804-README.md"
  }
]

Windows 2016
[
  {
    "group": "Operating System",
    "detail": "Microsoft Windows Server 2016\n10.0.14393\nDatacenter"
  },
  {
    "group": "Virtual Environment",
    "detail": "Environment: windows-2016\nVersion: 20200301.1\nIncluded Software: https://github.com/actions/virtual-environments/blob/win16/20200301.1/images/win/Windows2019-Readme.md"
  }
]

Windows 2019
[
  {
    "group": "Operating System",
    "detail": "Microsoft Windows Server 2019\n10.0.17763\nDatacenter"
  },
  {
    "group": "Virtual Environment",
    "detail": "Environment: windows-2019\nVersion: 20200301.1\nIncluded Software: https://github.com/actions/virtual-environments/blob/win19/20200301.1/images/win/Windows2019-Readme.md"
  }
]

macOS 10.15
[
  {
    "group": "Operating System",
    "detail": "macOS\n10.15.3\n19D76"
  },
  {
    "group": "Virtual Environment",
    "detail": "Environment: macos-10.15\nVersion: 20200301.1\nIncluded Software: https://github.com/actions/virtual-environments/tree/master/images/macos"
  }
]

May be, we should use $HOME folder everywhere for consistency,

/Users/runner/ on macOS
/home/runner on Ubuntu
C:\ on Windows

/azp run

@al-cheb I use this to apply some extra info to our own agents, but that info is not displayed in Azure DevOps. (groups missing in "initializing job") , I however do see this info displayed when choosing the MS hosts. Missing something?

@frankzo As far as I know there is an additional logic on the hosted-agents side to display this data. That explains why it's not shown using self-hosted ones.

@miketimofeev Thanks. I was able to set the image version with the setx from initialize-vm.ps1 so was hoping this would work too.

@frankzo , yep. As Mikhail mentioned, currently, it works only for Hosted agents.
Additional context:
We have an additional logic that copies this imagedata.json file to the agent folder:
Copy /imagegeneration/imagedata.json file to the /home/vsts/agents/2.182.1/.setup_info target

(Example for Ubuntu but general logic should be pretty clear - copy file to the root of agent folder)
On Hosted machines, we have to do it after azure-pipelines-agent installation since agent installation is not covered by image-generation.
On Self-Hosted machine, I guess you can just copy this file once after agent installation and it should work.

That worked like a charm.  I use scale sets agents in Azure DevOps which are installed by an extension that set the agent directory (Windows) to c:\agent by default.
I added this section to my Packer json just before sysprep:
        {                 "type": "file",                 "source": "C:\\imagedata.json",                 "destination": "C:\\Agent/.setup_info"         }


Use precomputed twiddles in avx

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#443  👈
#401
#399
#398
#397
#396
#395
#394
#390
#389
#383
#382
#381
#380
#379
#378
#377
#368
#367
#366
#365
dev

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

Join @spapinistarkware and the rest of your teammates on  Graphite

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

Project coverage is 96.07%. Comparing base (10ea17f) to head (2da0555).

Additional details and impacted files
@@                        Coverage Diff                         @@
##           spapini/02-25-Precompute_twiddles     #443   +/-   ##
==================================================================
  Coverage                              96.07%   96.07%
==================================================================
  Files                                     55       55
  Lines                                   8681     8698   +17
  Branches                                8681     8698   +17
==================================================================
+ Hits                                    8340     8357   +17
  Misses                                   293      293
  Partials                                  48       48

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


The RCS works fine, but when the enemy enters the aimbot FOV, the RCS doesn't work.

Same happening here

Should be fixed now, I've embedded recoil control into aimbot.


Framework 2 or 5

Dear rianjs,
I found Your iCal in Github, thank you for sharing it with others!
You wrote it for Frameworks 2.0 and 5.0 and now I have the problem,
that I don't want to switch my project to 2.0 because of Lib-Functions
wanting 3.5 and not to 5.0 because of "too new for some".
Up to now I always had Libraries, working with "we need FW x.y as a
minimum" -including DevXpress- so that I don't know how to include
your Lib.
I included a net20;net40 to my
Project File, but it did not work. I also tried netstandard2.0 there,
same result.
It would be fine, if you had a tip, how to run your library
in a project targetting Framework 3.5 or 4.0.
Thanks and best regards

It's actually not Framework 2.0. It's .NET Standard 2.0. See the supported Frameworks here [https://www.nuget.org/packages/Ical.Net#supportedframeworks-tab].
I target .NET Framweork 4.8 and it works fine.


Add missing license headers

@manstis adding a lot of missing license headers in various UF classes.
/cc @ederign

jenkins retest this.


code-65536 models cannot decode

Hi,
I was just trying out the code tokenizers, seems like all the code-65636-* models are all unable to decode:
import tokenmonster

tokenizer = tokenmonster.load("code-65536-balanced-nocapcode-v1")
tokens = tokenizer.tokenize("hello world") # [  127 51042]
decoded_string = tokenizer.decode(tokens)
print(decoded_string)
> ''

The 100k and 32k models work.

Thanks for the bug report.
It was caused by the maximum token ID overflowing from uint16 65536 to 0 when checking for valid token IDs, thereby rendering all token IDs invalid.
I've fixed this and pushed the change. It requires updating to the latest version (1.1.11) pip install --upgrade --no-cache-dir tokenmonster. Please let me know if you encounter any issues.


[Code Addition Request]: Bubble Shoot Game

Have you completed your first issue?

[X] I have completed my first issue

Guidelines

[X] I have read the guidelines
[X] I have the link to my latest merged PR

Latest Merged PR Link
N/A
Project Description
It's like a shooting game , you can shoot by using space and collect points.
Full Name
Souvik Kumar Pramanik
Participant Role
GSSOC

@souvikpramanikgit what tech stack you are planning to use?

only python


Fix undefined route when switching to grid/tile view

Fix undefined route when switching to grid/tile view, ems_cloud
is using restful routes, so there is no /show
Exception when clicking on tile view e.g. on ems_cloud page, clicking on relation cloud_tenants
No route matches [GET] "/ems_cloud/show/23"
Rails.root: /home/Ladas/Projects/cfme/manageiq
Application Trace | Framework Trace | Full Trace
/home/Ladas/.rvm/gems/ruby-2.2.3/bundler/gems/rails-597fa0b42f90/actionpack/lib/action_dispatch/middleware/debug_exceptions.rb:53:in call' /home/Ladas/.rvm/gems/ruby-2.2.3/bundler/gems/rails-597fa0b42f90/actionpack/lib/action_dispatch/middleware/show_exceptions.rb:31:in call'
/home/Ladas/.rvm/gems/ruby-2.2.3/bundler/gems/rails-597fa0b42f90/railties/lib/rails/rack/logger.rb:36:in call_app' /home/Ladas/.rvm/gems/ruby-2.2.3/bundler/gems/rails-597fa0b42f90/railties/lib/rails/rack/logger.rb:26:in call'
request_store (1.3.1) lib/request_store/middleware.rb:9:in call' /home/Ladas/.rvm/gems/ruby-2.2.3/bundler/gems/rails-597fa0b42f90/actionpack/lib/action_dispatch/middleware/request_id.rb:24:in call'
rack (2.0.0.alpha) lib/rack/method_override.rb:22:in call' rack (2.0.0.alpha) lib/rack/runtime.rb:22:in call'
/home/Ladas/.rvm/gems/ruby-2.2.3/bundler/gems/rails-597fa0b42f90/activesupport/lib/active_support/cache/strategy/local_cache_middleware.rb:28:in call' /home/Ladas/.rvm/gems/ruby-2.2.3/bundler/gems/rails-597fa0b42f90/actionpack/lib/action_dispatch/middleware/executor.rb:12:in call'
/home/Ladas/.rvm/gems/ruby-2.2.3/bundler/gems/rails-597fa0b42f90/actionpack/lib/action_dispatch/middleware/static.rb:136:in call' rack (2.0.0.alpha) lib/rack/sendfile.rb:111:in call'
/home/Ladas/.rvm/gems/ruby-2.2.3/bundler/gems/rails-597fa0b42f90/railties/lib/rails/engine.rb:522:in call' puma (3.3.0) lib/puma/configuration.rb:224:in call'
puma (3.3.0) lib/puma/server.rb:561:in handle_request' puma (3.3.0) lib/puma/server.rb:406:in process_client'
puma (3.3.0) lib/puma/server.rb:271:in block in run' puma (3.3.0) lib/puma/thread_pool.rb:111:in call'
puma (3.3.0) lib/puma/thread_pool.rb:111:in `block in spawn_thread'

@himdel @mzazrivec could you please review?

I think so, but ems_common is not the only controller that's restful now.. maybe it'd make sense to have gtl_url return restful? ? '/' : '/show'?

@himdel I think that make sense :-)

@himdel done

Note that @AparnaKarve had an open PR (https://github.com/ManageIQ/manageiq/pull/8222) which might fight for a solution to #8201


feat(ui): Warehouse creation form

Fixes #1538

Would it be an idea to provide a visual indicator to show the button is actually a dropdown? Classic bootstrap example: https://getbootstrap.com/docs/4.0/components/dropdowns/#single-button-dropdowns

@rpelczar the modal itself works great!
Thing I am noticing now is some trouble with a bug I've noticed before and keep forgetting to report...
A warehouse are never displayed in the DAG unless there is a Stage subscribed to it.
So creating a new Warehouse works, but with nothing initially subscribed to it, it doesn't show up in the view, which I think is likely to lead people to believe the modal didn't do its job.

@krancour I see why this bug happens, IMO we should merge this PR and I'll open a fast-follow fix for that bug

@rbreeze that sgtm.

@rpelczar hope you don't mind that I merged this on your behalf. I wanted to make sure this was included in a v0.5.0-rc.1.

@krancour Here's the fix: https://github.com/akuity/kargo/pull/1689


On creating a new entry, slug ignores changes in field "date"

- Do you want to request a feature or report a bug?
Bug.
- What is the current behavior?
New entry slug ignores "date" field of the post, puts current date instead.
- If the current behavior is a bug, please provide the steps to reproduce.
Take your Hugo-generated site on Github, connect NetlifyCMS as in docs, by adding index.html and config.yml exactly as in https://www.netlifycms.org/docs/quick-start/ to the folder ./static/admin/
In particular, there is a collection named "blog" with a slug field "{{year}}-{{month}}-{{day}}-{{slug}}"
Then create a new blog post at yoursite.com/admin, change field labeled "Publish date" (which has name "date") to any other date, put random data to other fields, and save a new entry.
Then the new file name starts with a current date.
- What is the expected behavior?
The new file name should start with the provided date.
- Please mention your node.js, and operating system version.
Hugo v0.22.1 on Ubuntu 16.04 in WSL of Windows 10. node.js not installed.

This isn't actually a bug - the slug template is referring to the current date. The "Publish Date" field isn't related to the slug at all.
That said, the ability to control slugs is definitely a priority, https://github.com/netlify/netlify-cms/issues/445 is the issue to watch.


Mention bin target in the readme file

Closes #171.

Codecov Report

Merging #177 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #177   +/-   ##
=======================================
  Coverage   82.91%   82.91%
=======================================
  Files          12       12
  Lines         439      439
=======================================
  Hits          364      364
  Misses         75       75

Continue to review full report at Codecov.

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


[Distributed] Try redirecting AST dump to file for test

It seems that this test likes to fail on some platforms by the output being truncated.
Let's try redirecting to a file like some other ast dumping tests do -- perhaps this will be more stable.
rdar://107631491

@swift-ci please smoke test and merge


Deprecation warnings for builtins don't handle the explicit builtin:... case

I was looking at the coverage report and noticed that approximately half the deprecated commands in https://github.com/elves/elvish/blob/3545cb5020eff5b7a5c544ab044b1abebe4bf4ae/pkg/eval/compiler.go#L124-L158 are exercised by unit tests. Which caused me to notice that you don't get a deprecation warning if you use the explicit builtin: namespace when executing a deprecated command:
> builtin:ord a
▶ 0x61
> ord a
deprecation: the "ord" command is deprecated; use "str:to-codepoints" instead
[tty 1], line 1: ord a
▶ 0x61

As a practical matter this probably doesn't matter since it is unusual to explicitly use the builtin: namespace prefix for builtins. Nonetheless, it should probably be handled.
TBD is why any of the cases in checkDeprecatedBuiltin() are being exercised. Other than ord~ which has an explicit test that it is deprecated.

TBD is why any of the cases in checkDeprecatedBuiltin() are being exercised.

Unsurprisingly that is because some of the commands (e.g., chr and -is-dir) have unit tests that predate their deprecation. While others (e.g., esleep) never had a unit test and thus don't exercise that portion of checkDeprecatedBuiltin(). TBD is how to handle deprecated commands in unit tests. It seems silly to retain unit tests of deprecated commands since there are, presumably, appropriate unit tests of the replacement command. Also, a lengthy switch statement like that in checkDeprecatedBuiltin() is implemented as if it were a sequence of if ... else if ... else if statements. Which, in this case, is not efficient since the comparison to a literal string results in a bunch of pointer comparisons that fall back to a byte-by-byte comparison of the var name to those in the list of deprecated vars. Switching to a map lookup will make the function much smaller and probably make the process faster.

Ugh! The cost of checking for deprecated builtins is doubled because it is called, indirectly, from two places in pkg/eval/compile_effect.go for each builtin:
https://github.com/elves/elvish/blob/3545cb5020eff5b7a5c544ab044b1abebe4bf4ae/pkg/eval/compile_effect.go#L190
and
https://github.com/elves/elvish/blob/3545cb5020eff5b7a5c544ab044b1abebe4bf4ae/pkg/eval/compile_effect.go#L223
Both of those function calls will typically be made for a particular builtin literal in the Elvish program. In a situation like this a "negative cache" would typically be employed to short-circuit a potentially expensive operation. But in this case it looks like simply changing the existing deprecation check to do a map lookup will be sufficient.

The current command deprecation mechanism only supports bare builtin commands; e.g., ord and not builtin:ord. More importantly, it doesn't extend to other embedded modules like path or str. Regardless, I still think the implicit builtin deprecation check should use a map rather than a switch. I'm also inclined to change the related unit tests to simply verify the deprecation warning rather than the functionality of the deprecated command.

Another oddity with the current implementation is that ord x results in a deprecation warning while resolve ord does not. I noticed this while exploring how to generalize the deprecation mechanism. However, I don't think fixing this is useful or worth the cost. However, it caused me to notice another surprising behavior. From my interactive Elvish shell which imports all the internal modules:
> resolve ord
▶ '$ord~'
> resolve x:ord
▶ '(external x:ord)'
> resolve math:ord
▶ '$math:ord~'

The first two commands produced the expected result. The third should have output the same result as the second command since the math module does not have an ord command. TBD is what, if anything, to do about this behavior.

See also the comments by @xiaq on my PR that addressed some, but not all, of the problems with the current implementation. The main issue with my attempted fix is that it doesn't correctly handle import aliasing, such as use builtin b or use path builtin, but then neither does the current implementation.


Add TDVT test report for the Tableau connector

Signed-off-by: Yury Fridlyand<EMAIL_ADDRESS>Description
Issues Resolved
AOS-260
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Closed without merge - PR #25 would merge the same changes into main.


test_random.py fail in conda env after rolling release driver update

there are multiple failures which can be reproduced by enabling the test in the workflow
Mismatched elements: 1 / 1 (100%)
Max absolute difference: 0.0625
Max relative difference: 0.01686
 x: array(3.77, dtype=float16)
 y: array([[3.707]], dtype=float16)
ERROR language/test_random.py

@leshikus could please provide more information:

Are those tests fail in non-conda env?
Which exact tests are failing?

Are those tests fail in non-conda env?

These tests fail only in conda environment.

Not reproducible today


Reposilite 3.5 unable to start

What happened?
Hey
after upgrading to 3.5, the docker container is unable to find java? That is what at least the logs tell me.
Using dzikoysk/reposilite:latest as the image.
Reposilite version
3.x
Relevant log output
Adding group `reposilite' (GID 999) ...
Done.
Adding system user `reposilite' (UID 999) ...
Adding new user `reposilite' (UID 999) with group `reposilite' ...
Creating home directory `/home/reposilite' ...
runuser: failed to execute java: No such file or directory
reposilite:x:999:999::/home/reposilite:/bin/sh
runuser: failed to execute java: No such file or directory
reposilite:x:999:999::/home/reposilite:/bin/sh
runuser: failed to execute java: No such file or directory
reposilite:x:999:999::/home/reposilite:/bin/sh
runuser: failed to execute java: No such file or directory
...

Hmm... this is strange. I've only bumped JDK from 19 -> 20, CI works:

https://github.com/dzikoysk/reposilite/actions/runs/6842989228/job/18605089885

I'll try to rebuild & run it on localhost. Thanks for reporting this.

@SirEndii do you use some kind of a custom software to run your Docker image? It looks fine for me:

Yeah, I use portainer
It seems that in the ENV vars it uses JDK 19

Yeah, I think we had similar issue in the past with Portainer. It seems to put JDK version in env variables when container is initialized, but later on it's not detecting changes, so it keeps referring the old value. I wonder if there's something we could do to notify it about this change.

Removed them, they got automatically replaced
Still, didn't fix the problem 🤔

The PATH still refers 19, so it could be the issue 🤔

Woops, I just noticed

Yeah, that fixed it
Thank you for the help

Nice :)


refactor resource const

What does this PR do and why?
Remove external link and spread props with linkStyle. No functionality or style changes.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] I have tested this PR in all supported browsers.
[ ] I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #2047

PR #2048

PR #2049

PR #2094

PR #2089

PR #2090

PR #2091

PR #2092

comment

Graphite Merge Job
Current status: 🔄 Waiting for checks to pass
This pull request is currently waiting for CI and mergeability checks to pass before being merged.
This comment was auto-generated by Graphite.

Job Reference: OhSplG4sLw5ccXyOTEUT


[Suggestion] List Mod Categories & Search by Category

Would be much easier to find binds if they were grouped by mod such as how the vanilla keybinds GUI works, would also be nice if users could search for keybinds that belong to a mod by entering say "@roughlyenoughitems" or whatever the mod is as can be found in Controlling for Fabric.

I don't know how I missed that this is already a thing, sorry about that


Event listener on OverlayView and its children

I'd like to register event listeners with elements contained within OverlayView. However, when I tried something similar to:
<OverlayView>

</OverlayView>

the event handlers don't actually receive the events. Is there a nice way to resolve this?

@pieterv Any tips? Been banging my head against this. Thanks!

Are you still having trouble with this? I had this issue open today as I coded up an OverlayView. I was worried about it. I didn't have any issue. My code looks something like:
<OverlayView>
  // ...
  This Particular
</OverlayView>

In the React component:
_handleThisParticularClick(e) {
  console.log('Works!');
},

And 'Works!' logs.


Timeout error?

Hi!
I just started using Ouroboros, and it already updated a bunch of my containers. However, after updating a handful, it gave me a timeout error. I cannot read any code, so I am afraid I have no idea what is going on.
I am sorry that the log is upside down in my Synology, hope you can start from the bottom :)
2019-02-28 22:41:04 | stderr | 2019-02-28 23:41:04 : ERROR : base : Job "Initial run interval container update for unix://var/run/docker.sock (trigger: date[2019-02-28 23:29:58 CET], next run at: 2019-02-28 23:29:58 CET)" raised an exception
2019-02-28 22:41:04 | stderr | Traceback (most recent call last):
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 384, in _make_request
2019-02-28 22:41:04 | stderr | six.raise_from(e, None)
2019-02-28 22:41:04 | stderr | File "<string>", line 2, in raise_from
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 380, in _make_request
2019-02-28 22:41:04 | stderr | httplib_response = conn.getresponse()
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/http/client.py", line 1321, in getresponse
2019-02-28 22:41:04 | stderr | response.begin()
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/http/client.py", line 296, in begin
2019-02-28 22:41:04 | stderr | version, status, reason = self._read_status()
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/http/client.py", line 257, in _read_status
2019-02-28 22:41:04 | stderr | line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/socket.py", line 589, in readinto
2019-02-28 22:41:04 | stderr | return self._sock.recv_into(b)
2019-02-28 22:41:04 | stderr | socket.timeout: timed out
2019-02-28 22:41:04 | stderr |
2019-02-28 22:41:04 | stderr | During handling of the above exception, another exception occurred:
2019-02-28 22:41:04 | stderr |
2019-02-28 22:41:04 | stderr | Traceback (most recent call last):
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 449, in send
2019-02-28 22:41:04 | stderr | timeout=timeout
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 638, in urlopen
2019-02-28 22:41:04 | stderr | _stacktrace=sys.exc_info()[2])
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/urllib3/util/retry.py", line 367, in increment
2019-02-28 22:41:04 | stderr | raise six.reraise(type(error), error, _stacktrace)
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/urllib3/packages/six.py", line 686, in reraise
2019-02-28 22:41:04 | stderr | raise value
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 600, in urlopen
2019-02-28 22:41:04 | stderr | chunked=chunked)
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 386, in _make_request
2019-02-28 22:41:04 | stderr | self._raise_timeout(err=e, url=url, timeout_value=read_timeout)
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 306, in _raise_timeout
2019-02-28 22:41:04 | stderr | raise ReadTimeoutError(self, url, "Read timed out. (read timeout=%s)" % timeout_value)
2019-02-28 22:41:04 | stderr | urllib3.exceptions.ReadTimeoutError: UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
2019-02-28 22:41:04 | stderr |
2019-02-28 22:41:04 | stderr | During handling of the above exception, another exception occurred:
2019-02-28 22:41:04 | stderr |
2019-02-28 22:41:04 | stderr | Traceback (most recent call last):
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/apscheduler/executors/base.py", line 125, in run_job
2019-02-28 22:41:04 | stderr | retval = job.func(*job.args, **job.kwargs)
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/pyouroboros/dockerclient.py", line 321, in update
2019-02-28 22:41:04 | stderr | self.recreate(container, latest_image)
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/pyouroboros/dockerclient.py", line 137, in recreate
2019-02-28 22:41:04 | stderr | self.remove(container)
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/pyouroboros/dockerclient.py", line 128, in remove
2019-02-28 22:41:04 | stderr | container.remove()
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/docker/models/containers.py", line 339, in remove
2019-02-28 22:41:04 | stderr | return self.client.api.remove_container(self.id, **kwargs)
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/docker/utils/decorators.py", line 19, in wrapped
2019-02-28 22:41:04 | stderr | return f(self, resource_id, *args, **kwargs)
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/docker/api/container.py", line 990, in remove_container
2019-02-28 22:41:04 | stderr | self._url("/containers/{0}", container), params=params
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/docker/utils/decorators.py", line 46, in inner
2019-02-28 22:41:04 | stderr | return f(self, *args, **kwargs)
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/docker/api/client.py", line 233, in _delete
2019-02-28 22:41:04 | stderr | return self.delete(url, **self._set_request_timeout(kwargs))
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 615, in delete
2019-02-28 22:41:04 | stderr | return self.request('DELETE', url, **kwargs)
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 533, in request
2019-02-28 22:41:04 | stderr | resp = self.send(prep, **send_kwargs)
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 646, in send
2019-02-28 22:41:04 | stderr | r = adapter.send(request, **kwargs)
2019-02-28 22:41:04 | stderr | File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 529, in send
2019-02-28 22:41:04 | stderr | raise ReadTimeout(e, request=request)
-- | -- | --
2019-02-28 22:41:04 | stderr | requests.exceptions.ReadTimeout: UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

(Flipped the line order - DirtyCajunRice)
Is this expected behaviour? And can I assume it is still doing it's job at this point?
 Ouroboros lost connection to the docker socket as it was unavailable for some extended period of time. I flipped the line order for you too

This has nothing to do with us. Ouroboros lost connection to the docker socket as it was unavailable for some extended period of time. I flipped the line order for you too

Ok, sorry I did not mean to imply that it was anything to do with you. It seems something is causing incompatibility. I have no idea how docker socket works or anything like that. But at the same time I get these exceptions, my KODI Driver for my remote(running Node v6) also crashes:
Kodi Driver by Niels de Klerk.
Updater registered.
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE <IP_ADDRESS>:1337
    at Object.exports._errnoException (util.js:1020:11)
    at exports._exceptionWithHostPort (util.js:1043:20)
    at Server._listen2 (net.js:1262:14)
    at listen (net.js:1298:10)
    at net.js:1408:9
    at _combinedTickCallback (internal/process/next_tick.js:83:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)

If you by chance could help point me in any sort of the right direction, I would highly appreciate it.

the issues section isnt the place for this. hop in discord if you can


Adapter: apply_order_by

Hi,
I saw your post on Elixir Forum and implemented  the changes for selected_as here: https://github.com/elixir-ecto/ecto/pull/4232
If you're still interested you= could give it a try and let u know how it goes.

Hi @greg-rychlewski, thanks for implementing that so quickly!
It works as expected, and it makes the code quite a bit simpler here: https://github.com/woylie/flop/pull/392


parabuzzle/craneoperator:latest image V2, schema 1

Hello,
the crane operator docker image is in V2 schema 1 format wich is deprecated, last push on docker hub is 6 years ago.
I got this error on docker compose build :
[DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of docker.io/parabuzzle/craneoperator:latest to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/
i also created an issue here  https://github.com/digital-ai/release-integration-template-python/issues/9
Thank you
Rachid.

resolved here
https://github.com/digital-ai/release-integration-template-python/issues/9


Add French translation

Hey! Thanks for the PR! I released the french translations in version 6.1.1. :)


2.x.x - How to disallow HBResponseBodyWriter from being used outside HBResponseBody.write.

Can we add a swift 6 conditional conformance to ~Escapable

It appears the consensus around the SwiftNIO team is to use a with...() { } type method for these stuff.
See: https://github.com/swift-server/async-http-client/issues/752
(I'm taking a guess at what you mean by this issue, so disregard this comment if what I mentioned is unrelated)

@MahdiBM I'm guessing something like this
var writerCopy: ResponseBodyWriter
let response = Response(
    status: .ok,
    body: .init { writer in
        writerCopy = writer
    }
)
try await writerCopy.write(anotherByteBuffer)


suppressLogging can be culled?

Unless I'm missing something, the LogHost.suppressLogging field is never set to true. Seems the whole concept could be culled.

Afaik at some point we needed suppressLogging in order to set up logging itself (i.e. you'd end up stack overflow'ing). It could be that this code is dead though


Response streaming in 3.0.0 beta version

Issue description
Response Streaming not working in 3.0.0 beta, Error : decode not found
Expected Behavior
Response Streaming doesnt work as expected as its features cannot be found in the lib in beta and i cannot find a guide on how to stream response in 13.0.0 beta as the same from stable version doesnt work as expected.
Actual Behavior
Response Streaming should work as before in 2.8.10
Steps to reproduce
use the same Response streaming code in 2.8.10 then upgrade to beta and the same code doesnt work
import {fileURLToPath} from "url";
import path from "path";
import {
    LlamaModel, LlamaContext, LlamaChatSession, Token
} from "node-llama-cpp";

const __dirname = path.dirname(fileURLToPath(import.meta.url));

const model = new LlamaModel({
    modelPath: path.join(__dirname, "models", "codellama-13b.Q3_K_M.gguf")
});
const context = new LlamaContext({model});
const session = new LlamaChatSession({context});

const q1 = "Hi there, how are you?";
console.log("User: " + q1);

process.stdout.write("AI: ");
const a1 = await session.prompt(q1, {
    onToken(chunk: Token[]) {
        process.stdout.write(context.decode(chunk));
    }
});

My Environment

Dependency
Version

Operating System
Windows 10

CPU
ryzen 5 7600

Node.js version
v20.9.0

Typescript version
latest

node-llama-cpp version
3.0.0

Additional Context
No response
Relevant Features Used

[ ] Metal support
[ ] CUDA support
[ ] Grammar

Are you willing to resolve this issue by submitting a Pull Request?
No, I don’t have the time and I’m okay to wait for the community / maintainers to resolve this issue.

Should probably be model.detokenize(tokens) now.

I've updated the version 3 beta PR to include an example of how to stream a response


Fix link to non-existent file

Fix incorrect reference to swarm_rm.md which should be node_rm.md. This was introduced by #26125. @thaJeztah @SvenDowideit PTAL, this is blocking us from publishing. Needs cherry-pick as well.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix_broken_build" git@github.com:mstanleyjones/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix_broken_build" git@github.com:mstanleyjones/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

The commit is signed. Not sure why the tests won't detect it ...

LGTM


internet time restrictions

I intended to apply time restriction for a family member with this guide https://openwrt.org/docs/guide-user/firewall/fw3_configurations/fw3_parent_controls but it seems not works along Open clash

How do limit access 22.00 until 07.00?

transform timezone on your own

 transform timezone on your own

Thank you very much. I will test it

not working? my timezone for UTC +7
script:
  shortcuts:
    limit-child: in_cidr(src_ip,'<IP_ADDRESS>/32') and (time.now().hour > 14 and time.now().hour < 1)
    limit-brother: in_cidr(src_ip,'<IP_ADDRESS>/32') and (time.now().hour > 17 and time.now().hour < 21)
    limit-sister: in_cidr(src_ip,'<IP_ADDRESS>/32') and (time.now().hour > 15 and time.now().hour < 20)

rules:
- SCRIPT,limit-child,REJECT
- SCRIPT,limit-sister,REJECT
- SCRIPT,limit-brother,REJECT

not working? my timezone for UTC +7
script:
  shortcuts:
    limit-child: in_cidr(src_ip,'<IP_ADDRESS>/32') and (time.now().hour > 14 and time.now().hour < 1)
    limit-brother: in_cidr(src_ip,'<IP_ADDRESS>/32') and (time.now().hour > 17 and time.now().hour < 21)
    limit-sister: in_cidr(src_ip,'<IP_ADDRESS>/32') and (time.now().hour > 15 and time.now().hour < 20)

rules:
- SCRIPT,limit-child,REJECT
- SCRIPT,limit-sister,REJECT
- SCRIPT,limit-brother,REJECT

maybe try it without time conversion... it works for me

use rule mode

typo in limit-child
script:
  shortcuts:
    limit-child: in_cidr(src_ip,'<IP_ADDRESS>/32') and (time.now().hour > 14 or time.now().hour < 1)
    limit-brother: in_cidr(src_ip,'<IP_ADDRESS>/32') and (time.now().hour > 17 and time.now().hour < 21)
    limit-sister: in_cidr(src_ip,'<IP_ADDRESS>/32') and (time.now().hour > 15 and time.now().hour < 20)

rules:
- SCRIPT,limit-child,REJECT
- SCRIPT,limit-sister,REJECT
- SCRIPT,limit-brother,REJECT

@djoeni said:

maybe try it without time conversion... it works for me

yes tested and works pretty well
@vernesong said:

typo in limit-child

thanks you sir.


Feature: Open archives from the home page in the same tab

What feature or improvement do you think would benefit Files?
Files usually opens supported archives (Zip, 7z, ...) in the same tab even if they are associated with Windows Explorer.
However, opening them from Recents in the home page launches a new Files instance or Windows Explorer.
Requirements

This proposal will make open supported archives listed in Home in the same tab

Files Version
Version: 2.4.40
Windows Version
Windows 11 22H2 22621.1344
Comments
No response

Hi, just to let everybody know and help prevent duplicate efforts, I am working on this issue.


[TrapFocus] Make isEnabled and getDoc optional

[x] I have followed (at least) the PR section of the contributing guide.

Closes #25528
Preview: https://deploy-preview-25784--material-ui.netlify.app/components/trap-focus/

@m4theushw It's a good one 🙏


Add build config files for Ray example pipelines

This is a follow-up to #844 that adds build configuration files to the example pipelines which require Ray as a dependency.
This is enabled by adding a sematic[ray] dependency to the pipelines' requirements, and including the pipelines' code and data as dependencies to the sematic.ee module, so the example pipelines will be installed together with the ee wheel.
Some bazel dependencies are moved around in order to avoid dependency cycles.
Testing
Because these pipelines now depend on the version of sematic[ray] that is built using these changes, which are not released to PyPi, they were tested using a local build of the Sematic wheel. This commit contains the version that was tested.
Example Testing Pipeline run command:
$ sematic run --build sematic/examples/testing_pipeline/__main__.py -- --images --cloud --detach

Resulting Dashboard entry: link.
Example Lightning ResNet run command:
$ sematic run --build sematic/examples/lightning_resnet/main.py -- --cloud

Resulting Dashboard entry: link (did not complete due to this error)
Example CIFAR10 Classifier run command:
$ sematic run --build sematic/examples/cifar_classifier/main.py -- --cloud

Resulting Dashboard entry: link (did not complete due to this error)

Hitting an issue where the Ray Agent dies on the Ray Workers with no real debugging information. The Ray pods continue in zombie mode forever.
Ray Worker info:
root@rc0547849f186b8d5ea42ecb94f-worker-worker-group-0-6rnwx:/# cat /tmp/ray/session_2023-06-01_13-42-32_415121_1/logs/raylet.err
[2023-06-01 13:43:05,421 E 26 94] (raylet) agent_manager.cc:135: The raylet exited immediately because the Ray agent failed. The raylet fate shares with the agent. This can happen because the Ray agent was unexpectedly killed or failed. Agent can fail when
- The version of `grpcio` doesn't follow Ray's requirement. Agent can segfault with the incorrect `grpcio` version. Check the grpcio version `pip freeze | grep grpcio`.
- The agent failed to start because of unexpected error or port conflict. Read the log `cat /tmp/ray/session_latest/logs/dashboard_agent.log`. You can find the log file structure here https://docs.ray.io/en/master/ray-observability/ray-logging.html#logging-directory-structure.
- The agent is killed by the OS (e.g., out of memory).
root@rc0547849f186b8d5ea42ecb94f-worker-worker-group-0-6rnwx:/#
root@rc0547849f186b8d5ea42ecb94f-worker-worker-group-0-6rnwx:/# cat /tmp/ray/session_latest/logs/dashboard_agent.log
cat: /tmp/ray/session_latest/logs/dashboard_agent.log: No such file or directory

Ray Head info:
2023-06-01 13:43:24,205 INFO (monitor) autoscaler.py:466 -- The autoscaler took 0.001 seconds to complete the update iteration.
[2023-06-01 13:43:24,647 W 116 116] (raylet) agent_manager.cc:115: Agent process expected id 424238335 timed out before registering. ip , id 0
[2023-06-01 13:43:24,650 I 116 195] (raylet) agent_manager.cc:131: Agent process with id 424238335 exited, exit code 0. ip . id 0
[2023-06-01 13:43:24,650 E 116 195] (raylet) agent_manager.cc:135: The raylet exited immediately because the Ray agent failed. The raylet fate shares with the agent. This can happen because the Ray agent was unexpectedly killed or failed. Agent can fail when
- The version of `grpcio` doesn't follow Ray's requirement. Agent can segfault with the incorrect `grpcio` version. Check the grpcio version `pip freeze | grep grpcio`.
- The agent failed to start because of unexpected error or port conflict. Read the log `cat /tmp/ray/session_latest/logs/dashboard_agent.log`. You can find the log file structure here https://docs.ray.io/en/master/ray-observability/ray-logging.html#logging-directory-structure.
- The agent is killed by the OS (e.g., out of memory).
[2023-06-01 13:43:24,650 I 116 116] (raylet) main.cc:301: Raylet received SIGTERM, shutting down...
[2023-06-01 13:43:24,650 I 116 116] (raylet) accessor.cc:435: Unregistering node info, node id = 3dc2eef92b42a949fc9ae3319dc63f3aada2094b400313dbe6178f4a
[2023-06-01 13:43:24,650 E 116 195] (raylet) agent_manager.cc:135: The raylet exited immediately because the Ray agent failed. The raylet fate shares with the agent. This can happen because the Ray agent was unexpectedly killed or failed. Agent can fail when
- The version of `grpcio` doesn't follow Ray's requirement. Agent can segfault with the incorrect `grpcio` version. Check the grpcio version `pip freeze | grep grpcio`.
- The agent failed to start because of unexpected error or port conflict. Read the log `cat /tmp/ray/session_latest/logs/dashboard_agent.log`. You can find the log file structure here https://docs.ray.io/en/master/ray-observability/ray-logging.html#logging-directory-structure.
- The agent is killed by the OS (e.g., out of memory).
[2023-06-01 13:43:24,650 I 13 13] (gcs_server) gcs_node_manager.cc:88: Draining node info, node id = 3dc2eef92b42a949fc9ae3319dc63f3aada2094b400313dbe6178f4a
[2023-06-01 13:43:24,650 I 13 13] (gcs_server) gcs_node_manager.cc:212: Removing node, node id = 3dc2eef92b42a949fc9ae3319dc63f3aada2094b400313dbe6178f4a, node name = <IP_ADDRESS>
[2023-06-01 13:43:24,650 I 13 13] (gcs_server) gcs_placement_group_manager.cc:739: Node 3dc2eef92b42a949fc9ae3319dc63f3aada2094b400313dbe6178f4a failed, rescheduling the placement groups on the dead node.
[2023-06-01 13:43:24,650 I 13 13] (gcs_server) gcs_actor_manager.cc:991: Node 3dc2eef92b42a949fc9ae3319dc63f3aada2094b400313dbe6178f4a failed, reconstructing actors.
[2023-06-01 13:43:24,650 I 116 116] (raylet) io_service_pool.cc:47: IOServicePool is stopped.
[2023-06-01 13:43:24,661 I 13 13] (gcs_server) gcs_node_manager.cc:134: Raylet 3dc2eef92b42a949fc9ae3319dc63f3aada2094b400313dbe6178f4a is drained. Status GrpcUnavailable: RPC Error message: Cancelling all calls; RPC Error details: . The information will be published to the cluster.
2023-06-01 13:43:29,208 INFO (monitor) autoscaler.py:147 -- The autoscaler took 0.0 seconds to fetch the list of non-terminated nodes.
2023-06-01 13:43:29,208 INFO (monitor) load_metrics.py:161 -- LoadMetrics: Removed ip: 3dc2eef92b42a949fc9ae3319dc63f3aada2094b400313dbe6178f4a.
2023-06-01 13:43:29,208 INFO (monitor) load_metrics.py:164 -- LoadMetrics: Removed 1 stale ip mappings: {'3dc2eef92b42a949fc9ae3319dc63f3aada2094b400313dbe6178f4a'} not in set()
2023-06-01 13:43:29,208 INFO (monitor) autoscaler.py:423 --

The only difference I can find between the Bazel and Docker versions of the pods is the size of the image, with the Docker version being ~5.6GB compared to Bazel's 1.3GB. Will pause this effort and continue again after optimizing the image size.


Add missing enum fields for the set_presence parameter

ok to test

@mujx: are you sure? What makes you believe that other values are valid here?
The description only documents offline, so if other values are valid, they need documenting too.

I thought that the presence parameter would support all the values from the presence endpoints.. If I'm wrong and only one value is allowed why not convert it into a boolean?

I believe all the values should be allowed. At least, that was my intention when I designed it :)

@richvdh Any update on this?

The description only documents offline, so if other values are valid, they need documenting too.

@mujx are you able to update this to include descriptions? Given the age, it'd be nice to have this be merged :)

@mujx Thank you for this PR! I hope you don't mind that I've added the requested descriptions to the PR. Stuff like this is very much part of the "end of August" goal for the spec, which happens to be in just a few short days.
It's worth noting that synapse currently does not support unavailable as an option, however as per leo's comment above, it seems reasonable to expect it in the spec and have the implementation follow.
I've also merged the latest master into the branch so that the PR can benefit from the new changelog format and build process.

Thanks @turt2live for finishing the PR. I've forgotten about the PR because I wasn't sure what unavailable really means in that context.


Check if cx is None

We need to check if cx is None because GRU and RNN do not use cx and they set None.
related to #1659

Thanks for the fix, I verified it locally!

jenkins, test this please.


Allow Grafana Config to use variables

Creating a few variables that will be used to alter a few SMTP settings.
All of the defaults have been maintained through the main.yml file, but they can be changed to specific values that are mapped to the grafana.ini.j2 template.

@rstjohn I think you use this role, can you take a look at this PR?


Fix deluge sparse files/movedone functionality

Fixed http://flexget.com/ticket/2881
Makes sure there is only one top level directory, enabling correct movedone functionality in deluge.
This is accomplished by ensuring the content_filename option doesn't pop the main file / sub file out of folder and also by changing the location of the sparse files (top_torrent_folder/.sparse_files)

Cool, I think this is the right fix.
Would it be good to make it so that if content_filename contains a directory, it renames the top level torrent folder?

Good idea! I was actually in the middle of writing something to that effect anyway, using another config option. Keeping it all in content_filename is more elegant I feel.
A a side effect this supports multiple directories theoretically - don't know if there is a depth limit on the deluge side of things.

Thanks!

This fix broke my configuration.
This is my configuration:
    deluge:
      host: localhost
      port: 58846
      username: **
      password: **
      main_file_only: true
      hide_sparse_files: true
      content_filename: "{{trakt_series_name|default(series_name)|replace(':',' -')}} - {{series_id}} - {{tvdb_ep_name|default('Unknown')}}"
      movedone: "/home/osmc/Public/TV Shows/{{trakt_series_name|default(series_name)|replace(':',' -')}}/Season {{series_season|pad(2)}}/"

Before it was correctly moving only the main file to the correct place:
home/osmc/Public/TV Shows/CSI - Cyber/Season 01/CSI - Cyber - S01E12 - Bit by Bit.mkv
But now, it's moving the main file but with its parent folder and this is definitely not the behaviour that I was expecting:
home/osmc/Public/TV Shows/CSI - Cyber/Season 01/CSI.Cyber.S01E12.720p.HDTV.X264-**/CSI - Cyber - S01E12 - Bit by Bit.mkv

Although the previous behaviour (of using multiple top level files) is probably preferential in the long run, it isn't currently supported in deluge (ticket) and seems to provide inconsistent functionality when used in combination with movedone.
This fix changes FlexGet functionality to work in line with the documentation This covers two points:

making sure main_file_only doesn't touch the file structure of the torrent, only setting the do_not_download status of individual files
sparse files are moved to a subdirectory instead of a top level one

Having said this, it does seem surprising the you had the previous code working consistently - perhaps it wasn't as broken as previously thought? What happened to the sparse files from your torrents before?
The fix also extends functonality by accepting paths in content_filename. This means you can rename the top folder in the torrent (see docs).
I currently use a combination of this and a script triggered by the deluge execute plugin to move the main file up one level once complete.

I understand your point but you need to agree it must have a way to simply configure flexget to move the main file to the correct place with the correct name, no matter the torrent folder structure.
I have been using a deluge plugin to delete the sparse files (they're no problem for me)

@gazpachoking Sorry for dragging this one up, but I would appreciate it if you could share that deluge execute script.

@jpts Sorry for dragging this one up, but I would appreciate it if you could share that execute script.

I have this set up to execute on torrent removed https://gist.github.com/jpts/e99347902976f81c1570723af6ffac2e