text:
chore(deps): update dependency mocha to v8

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

mocha (source)
7.2.0 -> 8.3.0

@types/mocha
7.0.2 -> 8.2.1

Release Notes

mochajs/mocha
v8.3.0
Compare Source
:tada: Enhancements

#4506: Add error code for test timeout errors (@boneskull)
#4112: Add BigInt support to stringify util function (@JosejeSinohui)

:bug: Fixes

#4557: Add file location when SyntaxError happens in ESM (@giltayar)
#4521: Fix require error when bundling Mocha with Webpack (@devhazem)

:book: Documentation

#4507: Add support for typescript-style docstrings (@boneskull)
#4503: Add GH Actions workflow status badge (@outsideris)
#4494: Add example of generating tests dynamically with a closure (@maxwellgerber)

:nut_and_bolt: Other

#4556: Upgrade all dependencies to latest stable (@AviVahl)
#4543: Update dependencies yargs and yargs-parser (@juergba)

Also thanks to @outsideris and @HyunSangHan for various fixes to our website and documentation.
v8.2.1
Compare Source
Fixed stuff.
:bug: Fixes

#4489: Fix problematic handling of otherwise-unhandled Promise rejections and erroneous "done() called twice" errors (@boneskull)
#4496: Avoid MaxListenersExceededWarning in watch mode (@boneskull)

Also thanks to @akeating for a documentation fix!
v8.2.0
Compare Source
The major feature added in v8.2.0 is addition of support for global fixtures.
While Mocha has always had the ability to run setup and teardown via a hook (e.g., a before() at the top level of a test file) when running tests in serial, Mocha v8.0.0 added support for parallel runs. Parallel runs are incompatible with this strategy; e.g., a top-level before() would only run for the file in which it was defined.
With global fixtures, Mocha can now perform user-defined setup and teardown regardless of mode, and these fixtures are guaranteed to run once and only once. This holds for parallel mode, serial mode, and even "watch" mode (the teardown will run once you hit Ctrl-C, just before Mocha finally exits). Tasks such as starting and stopping servers are well-suited to global fixtures, but not sharing resources--global fixtures do not share context with your test files (but they do share context with each other).
Here's a short example of usage:
// fixtures.js

// can be async or not
exports.mochaGlobalSetup = async function() {
  this.server = await startSomeServer({port: process.env.TEST_PORT});
  console.log(`server running on port ${this.server.port}`);
};

exports.mochaGlobalTeardown = async function() {
  // the context (`this`) is shared, but not with the test files
  await this.server.stop();
  console.log(`server on port ${this.server.port} stopped`);
};

// this file can contain root hook plugins as well!
// exports.mochaHooks = { ... }

Fixtures are loaded with --require, e.g., mocha --require fixtures.js.
For detailed information, please see the documentation and this handy-dandy flowchart to help understand the differences between hooks, root hook plugins, and global fixtures (and when you should use each).
:tada: Enhancements

#4308: Support run-once global setup & teardown fixtures (@boneskull)
#4442: Multi-part extensions (e.g., test.js) now usable with --extension option (@jordanstephens)
#4472: Leading dots (e.g., .js, .test.js) now usable with --extension option (@boneskull)
#4434: Output of json reporter now contains speed ("fast"/"medium"/"slow") property (@wwhurin)
#4464: Errors thrown by serializer in parallel mode now have error codes (@evaline-ju)

For implementors of custom reporters:

#4409: Parallel mode and custom reporter improvements (@boneskull):

Support custom worker-process-only reporters (Runner.prototype.workerReporter()); reporters should subclass ParallelBufferedReporter in mocha/lib/nodejs/reporters/parallel-buffered
Allow opt-in of object reference matching for "sufficiently advanced" custom reporters (Runner.prototype.linkPartialObjects()); use if strict object equality is needed when consuming Runner event data
Enable detection of parallel mode (Runner.prototype.isParallelMode())

:bug: Fixes

#4476: Workaround for profoundly bizarre issue affecting npm v6.x causing some of Mocha's deps to be installed when mocha is present in a package's devDependencies and npm install --production is run the package's working copy (@boneskull)
#4465: Worker processes guaranteed (as opposed to "very likely") to exit before Mocha does; fixes a problem when using nyc with Mocha in parallel mode (@boneskull)
#4419: Restore lookupFiles() in mocha/lib/utils, which was broken/missing in Mocha v8.1.0; it now prints a deprecation warning (use const {lookupFiles} = require('mocha/lib/cli') instead) (@boneskull)

Thanks to @AviVahl, @donghoon-song, @ValeriaVG, @znarf, @sujin-park, and @majecty for other helpful contributions!
v8.1.3
Compare Source
:bug: Fixes

#4425: Restore Mocha.utils.lookupFiles() and Webpack compatibility (both broken since v8.1.0); Mocha.utils.lookupFiles() is now deprecated and will be removed in the next major revision of Mocha; use require('mocha/lib/cli').lookupFiles instead (@boneskull)

v8.1.2
Compare Source
:bug: Fixes

#4418: Fix command-line flag incompatibility in forthcoming Node.js v14.9.0 (@boneskull)
#4401: Fix missing global variable in browser (@irrationnelle)

:lock: Security Fixes

#4396: Update many dependencies (@GChuf)

:book: Documentation

Various fixes by @sujin-park, @wwhurin & @Donghoon759

v8.1.1
Compare Source
:bug: Fixes

#4394: Fix regression wherein certain reporters did not correctly detect terminal width (@boneskull)

v8.1.0
Compare Source
In this release, Mocha now builds its browser bundle with Rollup and Babel, which will provide the project's codebase more flexibility and consistency.
While we've been diligent about backwards compatibility, it's possible consumers of the browser bundle will encounter differences (other than an increase in the bundle size). If you do encounter an issue with the build, please report it here.
This release does not drop support for IE11.
Other community contributions came from @Devjeel, @Harsha509 and @sharath2106. Thank you to everyone who contributed to this release!

Do you read Korean? See this guide to running parallel tests in Mocha, translated by our maintainer, @outsideris.
:tada: Enhancements

#4287: Use background colors with inline diffs for better visual distinction (@michael-brade)

:bug: Fixes

#4328: Fix "watch" mode when Mocha run in parallel (@boneskull)
#4382: Fix root hook execution in "watch" mode (@indieisaconcept)
#4383: Consistent auto-generated hook titles (@cspotcode)
#4359: Better errors when running mocha init (@boneskull)
#4341: Fix weirdness when using delay option in browser (@craigtaub)

:lock: Security Fixes

#4378, #4333: Update javascript-serialize (@martinoppitz, @wnghdcjfe)
#4354: Update yargs-unparser (@martinoppitz)

:book: Documentation & Website

#4173: Document how to use --enable-source-maps with Mocha (@bcoe)
#4343: Clean up some API docs (@craigtaub)
#4318: Sponsor images are now self-hosted (@Munter)

:nut_and_bolt: Other

#4293: Use Rollup and Babel in build pipeline; add source map to published files (@Munter)

v8.0.1
Compare Source
The obligatory patch after a major.
:bug: Fixes

#4328: Fix --parallel when combined with --watch (@boneskull)

v8.0.0
Compare Source
In this major release, Mocha adds the ability to run tests in parallel. Better late than never! Please note the breaking changes detailed below.
Let's welcome @giltayar and @nicojs to the maintenance team!
:boom: Breaking Changes

#4164: Mocha v8.0.0 now requires Node.js v10.12.0 or newer. Mocha no longer supports the Node.js v8.x line ("Carbon"), which entered End-of-Life at the end of 2019 (@UlisesGascon)

#4175: Having been deprecated with a warning since v7.0.0, mocha.opts is no longer supported (@juergba)
:sparkles: WORKAROUND: Replace mocha.opts with a configuration file.

#4260: Remove enableTimeout() (this.enableTimeout()) from the context object (@craigtaub)
:sparkles: WORKAROUND: Replace usage of this.enableTimeout(false) in your tests with this.timeout(0).

#4315: The spec option no longer supports a comma-delimited list of files (@juergba)
:sparkles: WORKAROUND: Use an array instead (e.g., "spec": "foo.js,bar.js" becomes "spec": ["foo.js", "bar.js"]).

#4309: Drop support for Node.js v13.x line, which is now End-of-Life (@juergba)

#4282: --forbid-only will throw an error even if exclusive tests are avoided via --grep or other means (@arvidOtt)

#4223: The context object's skip() (this.skip()) in a "before all" (before()) hook will no longer execute subsequent sibling hooks, in addition to hooks in child suites (@juergba)

#4178: Remove previously soft-deprecated APIs (@wnghdcjfe):

Mocha.prototype.ignoreLeaks()
Mocha.prototype.useColors()
Mocha.prototype.useInlineDiffs()
Mocha.prototype.hideDiff()

:tada: Enhancements

#4245: Add ability to run tests in parallel for Node.js (see docs) (@boneskull)
:exclamation: See also #4244; Root Hook Plugins (docs) -- root hooks must be defined via Root Hook Plugins to work in parallel mode

#4304: --require now works with ES modules (@JacobLey)

#4299: In some circumstances, Mocha can run ES modules under Node.js v10 -- use at your own risk! (@giltayar)

:book: Documentation

#4246: Add documentation for parallel mode and Root Hook plugins (@boneskull)

:nut_and_bolt: Other

#4200: Drop mkdirp and replace it with fs.mkdirSync (@HyunSangHan)

:bug: Fixes
(All bug fixes in Mocha v8.0.0 are also breaking changes, and are listed above)

Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you check the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: packages/opentelemetry-cloud-trace-propagator/package-lock.json
bash: line 0: hash: npx: not found


text:
Add semantic release

@destroyerofbuilds would you consider this repo stable enough to start releasing?

@rarkins we have been using github-app-cli since it's availability without any issues (Related to this package. We did encounter a few issues with GHE)
We have a deployment of this project that renovates a dozen repositories on a schedule of every 10 minutes. Performance and stability have been solid the entire time.

source: gharchive/issue

authors: destroyerofbuilds rarkins

repo: renovateapp/github-app-cli

license: MIT

license_type: permissive

license_source: github-api


text:
copying and pasting disk image file doesn't trigger renaming

Describe the bug
Copying an existing image file (PNG, to be specific) in Finder, and pasting it to markdown, no renaming window shows up.
Environments (please complete the following information):

OS: MacOS
Use [[Wikilinks]]: true
Debug info:
SYSTEM INFO:
Obsidian version: v0.14.6
Installer version: v0.14.6
Operating system: Darwin Kernel Version 21.4.0: Fri Mar 18 00:45:05 PDT 2022; root:xnu-8020.101.4~15/RELEASE_X86_64 21.4.0
Login status: not logged in
Insider build toggle: off
Live preview: off
Legacy editor: off
Base theme: light
Community theme: none
Snippets enabled: 1    <----- disable this doesn't solve my problem
Safe mode: off
Plugins installed: 1
Plugins enabled: 1
1: Paste image rename

To Reproduce
Steps to reproduce the behavior:

copy an existing disk image file
paste it to markdown
file copied to my default directory and default wikilink inserted, no renaming process triggered

Expected behavior
the plugin let me rename the image file
Screenshots
not available

I have the same trouble on Windows 10. When I drag and drop an image from the Windows File Explorer onto Obsidian, the file gets inserted correctly, but the rename is not triggered. I have "Auto Rename" and "Handle all Attachments" active.
It works fine with images I copy i.e. from the browser, but not for the ones I drag onto Obsidian from my file system. Also don't work when I right-click -> Copy and paste into Obsidian.

I have the same trouble on Windows 10. When I drag and drop an image from the Windows File Explorer onto Obsidian, the file gets inserted correctly, but the rename is not triggered. I have "Auto Rename" and "Handle all Attachments" active.
It works fine with images I copy i.e. from the browser, but not for the ones I drag onto Obsidian from my file system. Also don't work when I right-click -> Copy and paste into Obsidian.
EDIT: Oh dear, I just fixed it for me 😆 When I put something in the "Exclude Patterns" for the handle all attachments input, i.e. zip, it renames the files I drag and drop from the explorer correctly. I guess the plugin cannot handle an empty exclude pattern field.

Thx! This works for me too! I'm using MacOS right now.

This should be fixed in release 1.5.2, try enabling "handle all attachments" and then drag'n drop an image, or paste an image directly from a file copy to see if it works.

repo: reorx/obsidian-paste-image-rename


text:
add {{hex}} and {{uuid}}

resolves #22

we would obviously need to add more documentation, but it does the job for now.

Thanks for the PR, I see how this works. Surely UUID is a great idea, but I doubt whether using 4 random generated hex string conform the RFC standard.
As to the hex and hexNs, I suggest changing them to hash and shortHash, because random hex string is not guaranted to be unique, which may cause collision with other files. hash and shortHash are borrowed from Git, which use SHA-1 hex digest to represent a commit. For this plugin, we can generate the SHA1 hex for image file based on its content.

Ah, OK. I see your suggestion.
For {{hex}}, This is the convention I use for my vault. I use it so that each entity can be mapped in an sRGB colorspace, which I use for determining meta colors. I also figured that the chances of collision are improbable, considering that even if I have 1K images, the case of collision is 0.00625%.
But I know — this is purely my opinion, and I agree that the chance of collision is comparably way higher than UUIDs.
What if we add hash and shortHash and keep the {{hex}} options as well? We can

add a warning that the chance of collision will be high
or make a loop that retries when the entity already exists

I am already using a variant of your extension that supports {{hex}}, and it satisfies my needs, so if you do not like it, I don't mind removing the option.

Hi @anaclumos , it's been a long time, but I finally got myself back to this project.
My suggestions are:

rename hex to randomHex to clarify it.
indicating the size of the hex string by appending the number with a colon, e.g. {{randomHex:8}}. A similar format is seen in {{DATE:YYYYMMDD}}, which gives more flexibility and avoids redundancy.
hash and shortHash are omitted until anyone wants them.

After these simple changes are made, we'll be good to go!

Apologies for the late reply! I was having trouble with my Obsidian - Cloudflare setup and cannot confirm it immediately. If this PR works for you, please feel free to merge it!
Thank you so much for your consideration and attention to detail.
It was a brilliant experience collaborating with you! ❤🔥

@reorx How have you been? 😅 I'm going to close this unless it gets merged within the next few days.

source: gharchive/pull-request

authors: anaclumos reorx


text:
Password generator

Add a function to generate a new password when creating a user, and append a flag to set the password too, but don't declare it. This can be sent via secure method (ie - SMS later in the web interface)

Password generator added -> Core/Utilities/Security/PasswordGenerator.cs

Password generator added -> Core/Utilities/Security/PasswordGenerator.cs

On a new user account being created, if the flag password:true is provided, it will generate a random password of 20 characters and assign it to the user account. At the moment it will not be able to send the SMS, this has to be added via the front-end GUI later, and work with an SMS provider to send the SMS to the end-user. Clients will be charged for this service.

repo: repasscloud/ActivusXPro-CLI


text:
Add smoke testing for Cog

We should create a GitHub Actions workflow that runs on a schedule and automatically builds and uploads a test model to Replicate on supported platforms. This would help us catch any regressions or other problems.

Hey, can I work on this one?

repo: replicate/cog


text:
collect and analyze data from goldpinger

This endpoint of goldpinger produces json like:
{"hosts":[{"hostIP":"10.138.0.127","podIP":"10.32.0.7","podName":"goldpinger-qbpdg"},{"hostIP":"10.138.15.194","podIP":"10.32.12.11","podName":"goldpinger-zsg6q"}],"responses":{"goldpinger-qbpdg":{"HostIP":"10.138.0.127","OK":true,"PodIP":"10.32.0.7","response":{"podResults":{"goldpinger-qbpdg":{"HostIP":"10.138.0.127","OK":true,"PingTime":"2021-06-23T23:46:09.709Z","PodIP":"10.32.0.7","response":{"boot_time":"2021-06-23T19:43:58.525Z"},"status-code":200},"goldpinger-zsg6q":{"HostIP":"10.138.15.194","OK":true,"PingTime":"2021-06-23T23:45:58.463Z","PodIP":"10.32.12.11","response":{"boot_time":"2021-06-23T23:10:18.578Z"},"response-time-ms":1,"status-code":200}}}},"goldpinger-zsg6q":{"HostIP":"10.138.15.194","OK":true,"PodIP":"10.32.12.11","response":{"podResults":{"goldpinger-qbpdg":{"HostIP":"10.138.0.127","OK":true,"PingTime":"2021-06-23T23:46:12.262Z","PodIP":"10.32.0.7","response":{"boot_time":"2021-06-23T19:43:58.525Z"},"response-time-ms":1,"status-code":200},"goldpinger-zsg6q":{"HostIP":"10.138.15.194","OK":true,"PingTime":"2021-06-23T23:45:55.667Z","PodIP":"10.32.12.11","response":{"boot_time":"2021-06-23T23:10:18.578Z"},"status-code":200}}}}}}

Properly formatted:
{
    "hosts": [
        {
            "hostIP": "10.138.15.194",
            "podIP": "10.32.12.11",
            "podName": "goldpinger-zsg6q"
        },
        {
            "hostIP": "10.138.0.127",
            "podIP": "10.32.0.7",
            "podName": "goldpinger-qbpdg"
        }
    ],
    "responses": {
        "goldpinger-qbpdg": {
            "HostIP": "10.138.0.127",
            "OK": true,
            "PodIP": "10.32.0.7",
            "response": {
                "podResults": {
                    "goldpinger-qbpdg": {
                        "HostIP": "10.138.0.127",
                        "OK": true,
                        "PingTime": "2021-06-23T23:47:10.331Z",
                        "PodIP": "10.32.0.7",
                        "response": {
                            "boot_time": "2021-06-23T19:43:58.525Z"
                        },
                        "status-code": 200
                    },
                    "goldpinger-zsg6q": {
                        "HostIP": "10.138.15.194",
                        "OK": true,
                        "PingTime": "2021-06-23T23:47:00.611Z",
                        "PodIP": "10.32.12.11",
                        "response": {
                            "boot_time": "2021-06-23T23:10:18.578Z"
                        },
                        "response-time-ms": 8,
                        "status-code": 200
                    }
                }
            }
        },
        "goldpinger-zsg6q": {
            "HostIP": "10.138.15.194",
            "OK": true,
            "PodIP": "10.32.12.11",
            "response": {
                "podResults": {
                    "goldpinger-qbpdg": {
                        "HostIP": "10.138.0.127",
                        "OK": true,
                        "PingTime": "2021-06-23T23:47:13.357Z",
                        "PodIP": "10.32.0.7",
                        "response": {
                            "boot_time": "2021-06-23T19:43:58.525Z"
                        },
                        "response-time-ms": 2,
                        "status-code": 200
                    },
                    "goldpinger-zsg6q": {
                        "HostIP": "10.138.15.194",
                        "OK": true,
                        "PingTime": "2021-06-23T23:46:57.857Z",
                        "PodIP": "10.32.12.11",
                        "response": {
                            "boot_time": "2021-06-23T23:10:18.578Z"
                        },
                        "response-time-ms": 10,
                        "status-code": 200
                    }
                }
            }
        }
    }
}

The analyzer looks for "OK": false and fails if it's present.

And this does NOT display if there isn't a goldpinger service - exactly what we want!

repo: replicatedhq/kots


text:
Exposing global "REPLIT_LD_LOADER" property to be picked up by replenv builder

Why
For better or worse, uv mandates the virtualenv being a "real" virtualenv, including bin/python symlinks. This subverts our attempts to manipulate the environment via shell-script wrappers, causing runtime library issues.
By moving the environment shuffling into the replenv builder itself, curating the environment itself instead of the wrapper scripts, we can have both uv as well as tools like rtld-loder.
What changed

Expose REPLIT_LD_AUDIT

Test plan
I should be able to echo $REPLIT_LD_AUDIT and get the value defined even on an empty Repl.
Rollout

[x] This is fully backward and forward compatible

I've confirmed that this puts the entry I need in the right place -- the intent is that this will replace not only the python wrappers but also the node/bun wrappers as well.

Question, does this mean we are not setting this var at all for our current python setup?

@airportyh Currently the value is interpolated into the Python wrapper directly, but I'm trying to move it to "globally available" if the flag is turned on.
Is it OK to be globally enabled for all binaries within a Repl? I would presume yes, at a possible slight impact to startup speed, but effectively a no-op after that, but we'd get the benefit of broken applications and libraries working out of the box without further patching.

authors: airportyh blast-hardcheese

repo: replit/nixmodules


text:
Add orcid icon

Need to make orcid icon available https://fontawesome.com/v5.15/icons/orcid

orcid icons available in updated fontawesome library, see #121

authors: annakrystalli twinkarma


text:
GIS-related error when trying to run Django migrations: 'DatabaseOperations' object has no attribute 'geo_db_type'

Think we need to change the database URL type in compose/production/django/entrypoint b/compose/production/django/entrypoint from
DATABASE_URL="postgres://..."

to
DATABASE_URL="postgis://..."

Fixed via #48.


text:
Clarify license

Could you please clarify the license this software is distributed under?
package.json says BSD, but there is no license file in the repo. Since BSD family licenses typically require distributing an exact copy of the license alongside the software, and there isn't one canonical version of the BSD license, I can't get the legal department OK to use this software.
I know it's pedantic, but you know how lawyers are =(
Thanks!

Thank you!

repo: request/caseless

license_source: bigquery


text:
fixing issues and add test

Closes #85 and #84
There is no proper way to fix #84, but returning an empty interval makes more sense than returning (nan, nan).

@dsaxton wrote:

I think raising a helpful warning explaining why a meaningful result wasn't computed makes sense, whatever we decide the return value should be

I am not sure whether we should raise a warning or not.
Case against:
With my patch, the "bca" method now gives the same result as the "percentile" method in the pathological case, which is good. If all the replicas end up being the same value x, then the correct confidence interval according to the bootstrap algorithm is [x, x]. So it is not really an error, it is just a natural limitation of the bootstrap. We also don't raise a warning when the data sample is small, e.g. 1 element, which also makes the bootstrap meaningless.
Case in favor:
When bias and acceleration cannot be computed, the bca method becomes first-order accurate instead of second-order accurate. So issuing a warning about that makes sense.

Thanks @HDembinski

authors: HDembinski dsaxton

repo: resample-project/resample


text:
opam file: Add missing dependency

Detected in https://github.com/ocaml/opam-repository/pull/18590

Thanks

authors: cristianoc kit-ty-kate

repo: rescript-association/reanalyze


text:
Prototype

This is as much a review of the README as anything else, so I'll see if that speaks for itself!

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b83aa07). Click here to learn what that means.
The diff coverage is 86.75%.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   86.75%
=========================================
  Files             ?        1
  Lines             ?      151
  Branches          ?       36
=========================================
  Hits              ?      131
  Misses            ?       20
  Partials          ?        0

Impacted Files
Coverage Δ

treeTable.js
86.75% <86.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 b83aa07...68d2978. Read the comment docs.

These comments have been extremely helpful, thank you!

LGTM - just need a blog post now :)

for sure!

authors: codecov-io hillalex

repo: reside-ic/tree-table


text:
Implement bmap file checksum verification

Connects to #7, #6
This implements verification of a block map's file checksum when parsing a .bmap file, and adds an option to BlockMap.parse() to disable it by passing { verify: false } as options.
Example:
// This will throw, if the file's checksum doesn't check out
var bmap = BlockMap.parse( xml )
// This will happily ignore verifying it
var bmap = BlockMap.parse( xml, { verify: false })

Oh, very nice addition :+1: I'd love to see this tested with more bmap versions though.

Ah, you're testing various versions already, I missed that. Ignore me :)

Wait, I see the files were indeed added, but the test suite only tests 2.0. Am I missing something?

but the test suite only tests 2.0. Am I missing something?

Yeah, I thought it'd be enough by exclusion criteria (if the parsing tests pass for all versions, then pretty much the only thing being able to fail is the checksum comparison) – but better be safe than sorry – so I added tests for all versions which support checksums now.

authors: jhermsmeier jviotti

repo: resin-io-modules/blockmap


text:
Fix for extraction of the NMState result for manager.get_state

The manager.get_state() method currently fails with error "Wrong response type".
Looking at the DBUS API, the type for the "state" method return is "u" (uint32):
https://developer.gnome.org/NetworkManager/stable/gdbus-org.freedesktop.NetworkManager.html
I modified the From<> and manager invocation, and it seems to have fixed the error in my application.

Thanks for the PR! I am able to reproduce locally as well.

@spiderkeys I created a new PR for this so that I can easily merge it due to our VersionBot requirements: #114

Closing this one in favor of the other.

authors: majorz spiderkeys

repo: resin-io-modules/network-manager


text:
Resin-Supervisor: test config.txt changes

To be tested only on the Raspberry Pi family.
Test steps:

Set a RESIN_HOST_CONFIG_foo variable
Expected result: Logs show the variable is being applied. The device reboots and has a foo variable in config.txt correctly set.
Change the variable to a different value.
Expected result: same as before, now after the reboot config.txt will show the updated value.
Delete the variable
Expected result: after reboot, the device no longer shows the foo variable in config.txt

Useful documentation: https://docs.resin.io/configuration/advanced/

authors: horia-delicoti pcarranzav

repo: resin-io/autohat


text:
Details on SD card and reminder to share connection

In Getting Started with RPI2.
The Internet connection sharing thing could be expanded a bit more, but so far I couldn't find a single webpage  / wikiHow with a tutorial for all OS's.

Yeah, its difficult...There are also a number of issues with connection sharing with OSX especially with the new retina macbooks when you need a thunderbolt ethernet adaptor, I have had trouble making it work reliably :cry:

authors: pcarranzav shaunmulligan

repo: resin-io/docs


text:
sftp: persist "ssh command exited" error

What is the purpose of this change? What does it change?
If our ssh process has died, not only the next, but all subsequent
calls to clientError() should indicate the error.
restic output when the ssh process is killed with "kill -9":
  Save(<data/afb68adbf9>) returned error, retrying after 253.661803ms: Write: failed to send packet header: write |1: file already closed
  Save(<data/afb68adbf9>) returned error, retrying after 580.752212ms: ssh command exited: signal: killed
  Save(<data/afb68adbf9>) returned error, retrying after 790.150468ms: ssh command exited: signal: killed
  Save(<data/afb68adbf9>) returned error, retrying after 1.769595051s: ssh command exited: signal: killed
  [...]
  error in cleanup handler: ssh command exited: signal: killed

Before this patch:
  Save(<data/de698d934f>) returned error, retrying after 252.84163ms: Write: failed to send packet header: write |1: file already closed
  Save(<data/de698d934f>) returned error, retrying after 660.236963ms: OpenFile: failed to send packet header: write |1: file already closed
  Save(<data/de698d934f>) returned error, retrying after 568.049909ms: OpenFile: failed to send packet header: write |1: file already closed
  Save(<data/de698d934f>) returned error, retrying after 2.428813824s: OpenFile: failed to send packet header: write |1: file already closed
  [...]
  error in cleanup handler: failed to send packet header: write |1: file already closed

Was the change discussed in an issue or in the forum before?
No
Checklist

[X] I have read the Contribution Guidelines
[ ] I have added tests for all changes in this PR
No - not yet sure if possible. If you think it is, I will try to get something done.
[ ] I have added documentation for the changes (in the manual)
No - nothing changes for the user besides better error output
[ ] There's a new file in changelog/unreleased/ that describes the changes for our users (template here)
No - change seems too small for a changelog entry. I can add an entry if you thing the change is worth an entry.
[X] I have run gofmt on the code in all commits
[X] All commit messages are formatted in the same style as the other commits in the repo
[X] I'm done, this Pull Request is ready for review

Codecov Report

Merging #1824 into master will decrease coverage by 4.56%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1824      +/-   ##
==========================================
- Coverage   51.14%   46.57%   -4.57%
==========================================
  Files         167      167
  Lines       12876    12876
==========================================
- Hits         6585     5997     -588
- Misses       5298     5941     +643
+ Partials      993      938      -55

Impacted Files
Coverage Δ

internal/backend/sftp/sftp.go
61.59% <100%> (ø)
:arrow_up:

internal/backend/azure/azure.go
0% <0%> (-82.15%)
:arrow_down:

internal/backend/b2/b2.go
0% <0%> (-78.54%)
:arrow_down:

internal/backend/swift/swift.go
0% <0%> (-78.45%)
:arrow_down:

internal/backend/gs/gs.go
0% <0%> (-73.61%)
:arrow_down:

internal/backend/swift/config.go
36.95% <0%> (-54.35%)
:arrow_down:

internal/archiver/blob_saver.go
95.06% <0%> (-2.47%)
:arrow_down:

internal/archiver/file_saver.go
88.59% <0%> (+2.63%)
:arrow_up:

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 185b60c...dd3b991. Read the comment docs.

authors: codecov-io rfjakob

repo: restic/restic


text:
add nspwn command

Adds nspwn command officially. Currently doesn't allow choosing a TID, though that can be changed (I'm just a JS noob). Should also take care of #125 as well

Fixed!

repo: reswitched/pegaswitch

license: ISC


text:
什么是康奈尔笔记法？

什么是康奈尔笔记法？
概要：
其实康奈尔笔记没有传说中的那么神秘，它最大的总用在于鼓励你养成课后咀嚼的习惯，站在宏观的角度总结知识点，多次复习。比起传统的阅读笔记来，它也更接近于考试时对于知识点的回忆方式。
推荐语：
康奈尔笔记法，又叫做5R笔记法，高赞答案有康奈尔大学的留学生现身说法，表示从未听说过，哈哈哈哈哈哈（当然，不代表不存在，因为确实存在）。可是在网上、在国内却享有盛名；不管了，总之，这个方法还挺好用的，可以用于听课笔记、阅读笔记等等。

四色笔记法

repo: retech-fe/weekly


text:
Tutorial links in the footer link to a wrong page

Describe the bug
A clear and concise description of what the bug is.
The tutorial links in the footer directs to a wrong for all languages displayed
To Reproduce
Steps to reproduce the behavior:

Go to any page on https://rethinkdb.com2.
Scroll down to the footer, under getting started click on tutorials
You will be redacted to a list of languages page here https://rethinkdb.com/docs/guide
Click any of the languages displayed
Notice you will be redirected to a 404 page e.g: https://rethinkdb.com/docs/java/

Expected behavior
A clear and concise description of what you expected to happen.
It should redirect to a page with links that work like this one https://rethinkdb.com/docs/guide/javascript
Screenshots
If applicable, add screenshots to help explain your problem.

System info

OS: [e.g. macOS Mojave 10.14.3]
RethinkDB Version: [e.g. 2.4.0]

Additional context
Add any other context about the problem here.

While trying to fix this issue, I went through the docs and www, I wasn't able to locate the footer.

Thank you for trying to fix it and reporting it.  I have fixed it in #1346.
It's probably bad that the tutorial link points to /docs/guides instead of /docs/guides/, and I suppose it's bad that we don't have a redirect from /docs/guides to /docs/guides/ and likewise for other index pages, so that we have a single canonical URL.
The footer is in _layouts/default.html in the www repo, and it was easier to find using ack than it would have been with grep because ack filters out the _site folder (as I found out).

Thanks for the explanation, I will go ahead and close this issue.

authors: OlivierJM srh

repo: rethinkdb/docs


text:
🛑 Lindas Kingdoms is down

In 5b4bf91, Lindas Kingdoms (https://lindas.admin.ch/query?query=PREFIX rdf%3A <http%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23>
SELECT DISTINCT %3Fk (SAMPLE(%3Fs1) as %3Fs)%0AWHERE%20%7B%0A%20%20%3Fs1%20a%20%3Chttp%3A%2F%2Ffilteredpush.org%2Fontologies%2Foa%2FdwcFP%23TaxonName%3E%3B%0A%20%20%3Chttp%3A%2F%2Frs.tdwg.org%2Fdwc%2Fterms%2Fkingdom%3E%20%3Fk.%0A%7D%0AGROUP%20BY%20%3Fk) was down:

HTTP code: 503
Response time: 1323 ms

Resolved: Lindas Kingdoms is back up in fc84f4e after 26 minutes.

repo: retog/my-upptime


text:
ASM6 Output is Broken

The bug is that if the asm6 assembler config is chosen, the output asm file is not assemble-able with asm6.
To reproduce the behavior: Get an unmodified Super Mario Bros (NTSC) ROM and write nesgodisasm -a asm6 -o smb.asm smb.nes. Then, write asm6 smb.asm. It should show the output above.
I expected the output of the diasssembler to assemble back into a ROM, but instead, tons of errors popped up as seen in the error.txt file.

OS: Windows
Version / Commit: v0.2.1

error.txt

@htmlcoder2023 thanks for the bug report. Only asm6f is supported (linked in the readme) as the standard asm6 does not support some unofficial opcodes that you can find in some ROMs

I was not able to replicate the bug using asm6f 1.6 (+ f003):
nesgodisasm -a asm6 -o smb1.asm Super\ Mario\ Bros.\ \(World\).nes

asm6f smb1.asm
pass 1..
pass 2..
smb1.bin written (40976 bytes).

I was using asm6f version 1.6, which can be found here: https://github.com/freem/asm6f/releases/tag/v1.6_freem02. It doesn't work with either the 32-bit or 64-bit asm6f versions. I'm not sure what (+ f003) means.

@cartdb I potentially use a different version compiled for Linux that is more uptodate, please ask at https://github.com/freem/asm6f/ to create a new release, there are code changes of nearly 7 years now that are not part of any official release

@cornelk But this disassembler cannot be producing code that references non-existent labels. I disassembled the smb3 pal rom again, but the disassembler used jsr _func_cd83 twice and jsr _func_cb61 once even though these labels do not exist.

@cartdb I understand, however this issue is about the "Illegal instruction" error of asm6. Referencing labels that do not exist is a known and unrelated bug probably the same as #75

I added a readme note that an asm6f version needs to be used that needs to be compiled from source until a new release is made.

authors: cartdb cornelk htmlcoder2023

repo: retroenv/nesgodisasm


text:
Add release action

Here you find a basic implementation of a release action. When a Github Release is triggered, it will run after the successful completion of the of the lint and test steps. In my testing, it is successfully uploading an empty package to my personal npmjs.com account.
However, it may need to be customized to support the yarn build rollup step in this repository. Rather than try to guess how you'd like that part to work, I thought I'd put this up here as a starting point for discussion. Let me know what more I can do to improve the proposal.

Cool. Just outlining the release job to make sure I get it: We add a git tag for new patch/minor/major on master. That then bootstraps and builds (missing rn, as you said) the library. Finally, npm versions and publishes to the registry with the tag we pushed (so need to consistently tag as 1.0.1 not v1.0.0, I think??).
Other Qs: Do we need to restrict this job to just master branch and just our repo (e.g.)?
Do we need to commit back to the repo, since npm-version is updating package.json with the new version number? Would it make sense to throw release in its own yaml restricted to push on master?

Cool. Just outlining the release job to make sure I get it: We add a git tag for new patch/minor/major on master. That then bootstraps and builds (missing rn, as you said) the library. Finally, npm versions and publishes to the registry with the tag we pushed (so need to consistently tag as 1.0.1 not v1.0.0, I think??).

Yes, that's basically it. Though it should stamp the version with whatever you pass into the release name in GitHub's web interface.

Other Qs: Do we need to restrict this job to just master branch and just our repo (e.g.)?

The release event that qualifies to run new final step of the action should only get triggered for the default branch, I think. We want the tests that precede it to run for every push to every branch, so I wouldn't want to add a workflow-level branch restriction. I could imagine adding another statement to the if clause if you can imagine a circumstance where a tagged release would run for another branch.
The alternative method for handling the event, which is recommended by the GitHub docs, is to craft a separate release action that runs on the published hook that fires after a GitHub Release is created. I tend not to use that approach because I like having the linter and test jobs act as hurdles to prevent broken code from shipping, and I prefer not to replicate those jobs in two different actions. That said, this alternative structure totally works and I'd be happy to switch to using it here.

Do we need to commit back to the repo, since npm-version is updating package.json with the new version number? Would it make sense to throw release in its own yaml restricted to push on master?

You've put your finger on a potential problem in the code here, I think. Currently it is not automatically updating the version attribute in package.json to match the version number that's been shipped to the registry. There must be a way to make this work but I haven't put the time to sort it out. Right now that would have to be updated manually prior to sending the release out with the same version number. We could make that extra feature a requirement before we merge, if you like.

Yes, that's basically it. Though it should stamp the version with whatever you pass into the release name in GitHub's web interface.

Ah, that's right. I forgot about the web release interface. Was thinking of this triggering on, e.g., git tag 1.0.0 (which I think it will??).

The release event that qualifies to run the new, final step of the action should only get triggered for the default branch, I think. We want the tests that precede it to run for every push to every branch, so I wouldn't want to add a workflow-level branch restriction. {{ Yep, agree. }} I could imagine adding another statement to the if clause if you can imagine a circumstance where a tagged release would run for another branch.

So I see the startsWith(github.ref, 'refs/tags') in the new release job stops it from running on anything other than a tag. But if somebody created a PR with a tag on a branch, would that get through here?

I tend not to use that approach because I like having the linter and test jobs act as hurdles to prevent broken code from shipping, and I prefer not to replicate those jobs in two different actions.

👍

There must be a way to make this work but I haven't put the time in to sort it out. Right now that would have to be updated manually prior to sending the release out with the same version number. We could make that extra feature a requirement before we merge, if you like.

Hmm.. I think this might be easy enough to just commit back to the repo. npm version is gonna bump package.json automatically, so we just push that 1-line change back, and because action pushes don't trigger subsequent actions, I think we're in the clear??
Happy to help write this up. My only blocker is the first Q there about manual tags added on branches.

I don't know what will happen if you do a manual tag with git. My habit has been to limit my usage to the Releases interface here on the web. I can test it on my demo repo and see what happens.
Committing back to the repo should be doable, in the same manner as a scraper. Though I think that the tagged action checks out a detached head and it might require some kind of slick git repository maneuver to commit back to the default branch.

I can put these two items on my homework list and get back to you.

Your suspicion was correct. Manually creating a tag and pushing it a branch did slip past the if clause and trigger the release job. That's bad. I've pushed a patch. Here's are the receipts on the bug, which should not be resolved.
I'm still working on the second bit of homework.
Before
# palewire @ archbook in ~/Code/npm-ci-test on git:main o [4:27:58]
$ git status
On branch main
Your branch is up to date with 'origin/main'.

nothing to commit, working tree clean

# palewire @ archbook in ~/Code/npm-ci-test on git:main o [4:27:59]
$ git checkout -b test-tag
Switched to a new branch 'test-tag'

# palewire @ archbook in ~/Code/npm-ci-test on git:test-tag o [4:28:08]
$ git tag 1.0.0

# palewire @ archbook in ~/Code/npm-ci-test on git:test-tag o [4:28:19]
$ git push origin test-tag --tags
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
To https://github.com/palewire/npm-ci-test.git
 * [new branch]      test-tag -> test-tag
 * [new tag]         1.0.0 -> 1.0.0

After
# palewire @ archbook in ~/Code/npm-ci-test on git:vet-tags o [5:04:01] C:128
$ git checkout -b vet-the-branch
Switched to a new branch 'vet-the-branch'

# palewire @ archbook in ~/Code/npm-ci-test on git:vet-the-branch o [5:04:14]
$ git tag 0.0.999

# palewire @ archbook in ~/Code/npm-ci-test on git:vet-the-branch o [5:04:22]
$ git push origin vet-the-branch --tags
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
To https://github.com/palewire/npm-ci-test.git
 * [new branch]      vet-the-branch -> vet-the-branch
 * [new tag]         0.0.999 -> 0.0.999

I believe I've handled the commit issue. The key trick was adding the contents permission to the job. This pull request is again ready for your review.

I've added documentation explaining the release process this enables.

Hey, if it works it's better. My only nit pick would be that a doctoring or two might be nice in something that long.

K. Tried out a trim of your OG that simplifies a few bits and I think will apply well across most of our other node libs, too.
Here's the idea: https://github.com/reuters-graphics/npm-ci-test/blob/main/.github/workflows/ci.yaml
Checks I've done:

[x] Runs tests on all pushes/PRs
[x] Runs release only on tags
[x] Does not run release on branch tags
[x] Does not run release on tags on forks

Open question from me, I'm not sure when we'd run this on a workflow_dispatch. I'm guessing for integrating with other CI tools, but there's no real harm in't, I suppose.

Okay. I've tried to reconcile my patch to use your new if statement. I'm agnostic on the workflow_dispatch, though I do like it to run an ad hoc test run every once in a while. Happy to lose it that's what you'd prefer.
Small bugs asides, my only major question left is whether the packaging commands I've include will work with this package. Are you doing any rollup work or other building locally before you upload a distribution with npm publish? If so, that will likely need to be added yet.

I shoulda said, normally we run build in a prepublishOnly lifecycle script, so it's covered when we run npm publish.
In this repo, that's also tied into running tests, so yeah, probably a bit of cleanup to dedup for this new pattern.

Okay. Am I right to take it that would mean reduce prePublishOnly to npm run build? Are you include any additional flags to publish that instruct it to upload the dist folder created by build?

Am I right to take it that would mean reduce prePublishOnly to npm run build?

yep!

any additional flags to npm publish that instruct it to upload the dist folder created by build?

The main prop in package.json handles that one.

Thank you. I believe I've made that edit to the package.json's prePublishOnly command.

repo: reuters-graphics/bluprint


text:
Add format for haml-lint

Hello
I would like to add the haml-lint format
https://github.com/sds/haml-lint

@ZeroPointEnergy 👋Thank you for your contribution! 🚀

authors: ZeroPointEnergy mgrachev

repo: reviewdog/errorformat


text:
Add api credentials to fujitsu_const

In the PR for the Fujitsu HVAC code in home assistant (https://github.com/home-assistant/core/pull/109335) it was suggested that I put the API credentials in this repo instead of the homeassistant repo.
Feel free to reject if you are not comfortable with this.

This is interesting. Taking a step back and thinking about what's happening now.
If this library is intended to only handle connections to Ayla and create device objects, all of the individual integration specific code should probably be in a separate library. e.g. see Culligan. It handles the logic for calling ayla_iot_unofficial to establish the connection with Ayla and returning softener devices. Then the library has the logic for what to do with those devices.
I bring this up because Culligan has const  for the Ayla tokens.
If this needs to be here in an interim capacity, it should be renamed appropriately to its specific app (e.g. FGLair_APP_ID and FGLair_APP_SECRET). Even though it is currently in its own fujitsu_const file, it will help avoid naming collisions with core Ayla variable names (search or otherwise).

I updated the names as suggested (which makes sense). As for the broader discussion, I do agree that it would make sense for this library to only include the code to access the Ayla API and not device code. I'd like to get this into home assistant first though before reworking it into a separate repository it that's ok with you.

I'll look forward to the future refactor :)
That will also give you more direct maintainability for dependency versioning, code changes, etc.

authors: crevetor rewardone

repo: rewardone/ayla-iot-unofficial


text:
Update s3, sdk-core, sqs to 2.16.73

Updates

software.amazon.awssdk:s3
software.amazon.awssdk:sdk-core
software.amazon.awssdk:sqs

from 2.16.67 to 2.16.73.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, semver-patch

Superseded by #203.

repo: rewards-network/pure-aws


text:
Is it possible to test partial html?

My interest in this plugin is to validate HTML partials from a textarea in a CMS.  Is there a parser option to allow for partial HTML testing?  If I validate only the partial HTML I get the following errors.
"Element “head” is missing a required instance of child element “title”."
"Start tag seen without seeing a doctype first. Expected “<!DOCTYPE html>”."

This is understandable as this is testing a full HTML page.  I found a workaround by wrapping the HTML with html/title/body tags, but it would more convenient to allow for partial HTML checking.
Thanks!

I agree, but the API does not support this. I also solved it by wrapping it in a well-formed document, for what it's worth.

repo: rexxars/html-validator

license: mit


text:
[Legacy DB] Drop plan_credits_use table

not being used anymore

Approved

authors: Tooseriuz rassokhina-e

repo: rfcx/arbimon-db


text:
Update README.md

We should add our names with a link to our github to the authors section

Good thinking, can you make a trello card.

authors: TimEngleSF girithodu


text:
Support moving shows to an intermediate storage

A user has suggested a new feature where media files are moved to a different storage location after they reach a certain age. The media server re-indexes these files, so they are still accessible. A second time configuration then governs when these files are actually deleted. Additionally, there should be an interface that provides an overview of what media is currently live, in intermediate storage, or recently deleted.
Requirements:

Implement Move Action Type

Create a new action type in Deleterr to "move" files to a designated intermediate storage location.

Two-Stage Deletion Process

Set up two time-based conditions: one for moving to intermediate storage and one for deletion.

Re-Index Media After Move

Ensure the media server can re-index moved media so it remains accessible to users.

Overview Interface

Develop an interface that lists media by its current stage: live, intermediate, or recently deleted.

Update User Guide

Include instructions for setting up and using the intermediate storage feature.

Optional Turn On/Off Feature

Allow users to enable or disable this feature from Deleterr settings.

Currently only Radarr supports moving files across rootFolders.
Support for sonnar is being tracked here: https://github.com/totaldebug/pyarr/pull/164

repo: rfsbraz/deleterr


text:
[FEATURE REQUEST] - Add an option for playlist groups

Add an option for shelves (that is playlists groups) like %(shelf)s or %(playlists_group)s or %(group)s so when downloading playlists grouped in a shelf they are downloaded in a subfolder named as the shelf

This does not solve the problem in general. There can be an arbitrary nesting of playlists.

@dstftw what solves it?

license: Unlicense


text:
instagram: --sleep-interval doesn't work when dowloading playlists

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.03.03. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.03.03

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

Description of your issue, suggested solution and other information
The --sleep-interval option doesn't work when downloading a playlist using the instagram:user extractor.
I often get the http 429 error (too many requests) from instagram in this phase.
Maybe related to #4924?

If you could explain what makes this report "incomplete" I'll be glad to add more details.

Issue template explains what makes it incomplete.

Sorry but I still can't understand. I've checked all the relevant boxes and I didn't include any verbose output because it's of no use for this issue: simply the --sleep-interval machinery is only used while downloading video files, not while downloading JSON data (as in the instagram:user extractor), so quick repeated requests made while downloading JSON data for the instagram user can trigger the server 429 http error (too many requests). I've actually tested that hard-wiring a time.sleep(1) into the extractor seems to fix the issue.
So I had a better look at the code: I think the code that implements min_sleep_interval in the download() method of the FileDownloader() class in downloader/common.py
should be ported to _download_webpage() in extractor/common.py, so that it will also apply to http requests made to download JSON/webpage data.
If you agree this is the way to go, I can try to come up with a PR for this.

For the records, changes made in 27b1c73 to reflect the new instagram API also fix this issue, since now the instagram:user extractor downloads all the relevant JSON data in only one request. Well done!

authors: Vrihub dstftw


text:
hello, why this link isn't working : http://www.francetvinfo.fr/politique/notre-dame-des-landes/video-sur-france-inter-cecile-duflot-denonce-le-regard-meprisant-de-patrick-cohen_1520091.html ? bug or myself mistake ? regards  db

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.06.27. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[ ] I've verified and I assure that I'm running youtube-dl 2016.06.27

Before submitting an issue make sure you have:

[ ] At least skimmed through README and most notably FAQ and BUGS sections
[ ] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
$ youtube-dl -v <your command line>
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2016.06.27
[debug] Python version 2.7.11 - Windows-2003Server-5.2.3790-SP2
[debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
[debug] Proxy map: {}
...
<end of log>

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: https://www.youtube.com/watch?v=BaW_jenozKc
Single video: https://youtu.be/BaW_jenozKc
Playlist: https://www.youtube.com/playlist?list=PL4lCao7KL_QFVb7Iudeipvc2BCavECqzc

Description of your issue, suggested solution and other information
Explanation of your issue in arbitrary form goes here. Please make sure the description is worded well enough to be understood. Provide as much context and examples as possible.
If work on your issue required an account credentials please provide them or explain how one can obtain them.

Please download from source, as embedded videos doesn't work as a rule of thumb. In this case Daily Motion is the source.

Le 30/06/2016 11:53, SamuSoft a écrit :

Please download from source, as embedded videos doesn't work as a rule
of thumb. In this case Daily Motion is the source.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rg3/youtube-dl/issues/9955#issuecomment-229614317, or
mute the thread
https://github.com/notifications/unsubscribe/AHzYpbMsg3ipcQkrjJRJwD4bCufos-hFks5qQ5INgaJpZM4JB5y9.

Ok it's good !
thanks   db

Dailymotion videos on francetvinfo.fr will be recognized in the next version. Thanks for the report!

authors: SamuSoft dufoin yan12125


text:
support align.ustream.tv domain

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[ ] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[x] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Ustream has an enterprise version that's basically the same site but at the domain align.ustream.tv.
I didn't check the flake8 box because I don't have a Python dev env installed.

Add only matching tests.

authors: dstftw pushcx


text:
NO-ISSUE: Use a dedicated build dir per pipeline/task

Description
It is currently not possible to run multiple deployments in parallel because ZTPFW re-uses the same build dir for all pipelines. This PR creates a dedicated OUTPUTDIR using the pipeline-name/task-name of the specific run.
all is used in case of a no pipeline (task ran in isolation)
Signed-off-by: Flavio Percoco flavio@redhat.com
Type of change
Please select the appropriate options:

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] This change is a documentation update

Testing

Example of the build dir:

Test Configuration:

Versions:
Hardware:

Checklist

[ ] I have performed a self-review of my own code
[ ] If a change is adding a feature, it should require a change to the README.md and the review should catch this.
[ ] If the change is a fix, it should have an issue. The review should make sure the comments state the issue (not just the number) and it should use the keywords that will close the issue on merge.
[ ] A change should not be merged unless it passes CI or there is a comment/update saying what testing was passed.
[ ] PRs should not be merged unless positively reviewed.

I wonder if we also need different WORKDIR
If you deploy two different branches or some files are rendered on the folder and not the output
@alknopfler WDYT?

The only doubt after your comment @eifrach is the different deployment using branches different. Did you try it with several branches @flaper87 ???

authors: alknopfler eifrach flaper87


text:
Switch to using buildah in the example

https://github.com/rhd-gitops-example/services/blob/master/tekton-example/resources/build-task.yaml mounts the docker socket. Replace this with buildah as per https://github.com/tektoncd/catalog/tree/master/buildah

I'll work on this

authors: a-roberts mnuttall

repo: rhd-gitops-example/services


text:
Rethink "connected" attribute

When we originally designed the ev3dev-lang libraries, we based them all on a concept where devices would expose a connected property to indicate whether they had successfully found a device matching the parameters from the constructor. This has led to a lot of code that looks like this:
m = ev3.Motor(ev3.OUTPUT_A)
assert m.connected

...and lots of confused users as a result (especially when they don't know to include that assertion).
Do we want to change this behavior? I think it would make sense at this point to throw an exception from the constructor. This would be just for this library and wouldn't necessarily require a change to others.

I guess there is no point in creating a Motor class instance that is not actually linked to a physical motor, so :+1:

Seems worth raising an Exception in this scenario

+1, right now you get exception when you try to use it anyway (e.g. when you set m.polarity right after constructing it).

See PR #402

Throwing the exception is ok. But, should we get rid of the connected attribute too? Isn't there a valid use case for it?

Yep, one of the changes in #402 is to remove the attribute entirely. In fact, that's the title of the PR.

Yep, one of the changes in #402 is to remove the attribute entirely. In fact, that's the title of the PR.

I noticed the title :). My question is, if it would make sense to just throw the exception but not get rid of the attribute, because it might come in handy at some point (for things that could actually go on/offline after instantiation) and because it was exposed, so it's removal would break things (for example this or this from the projects gallery).

Yes, it will be a breaking change. I can't imagine a case where a device would come on/offline in a way that we'd notice proactively (i.e., every read of connected would need to perform I/O to check if things are still connected). If there are devices that have such a need, those classes can implement this attribute as needed.
Existing scripts will work as-is. I'm working on an "upgrading guide" (#399) which walks you through the details, but the short version is that we plan to rename the module to be ev3dev2. So, if you continue to import ev3dev, you'll get the existing version of the library, but you can choose to update your import statements and only then will you be forced to adapt to breaking changes. So, those examples will work, however we'll need to make sure we have clear documentation that explains this behavior.

Existing scripts will work as-is. I'm working on an "upgrading guide" (#399) which walks you through the details, but the short version is that we plan to rename the module to be ev3dev2. So, if you continue to import ev3dev, you'll get the existing version of the library

Well done. No concerns then. Thanks for clearing that up.

authors: WasabiFan bidaian ddemidov dwalton76 ensonic


text:
[devops:bot] update deps in nix/sources.json (from: rhino-core@cdae9e0

update nix refernces for rhino-core and|or nixpkgs to match https://github.com/rhinofi/rhino-core/blob/cdae9e0341927d3fcc07cedf9343f59a45410848/nix/sources.json (branch: dev)

superseded by #86

repo: rhinofi/logger


text:
🛑 BOS2 is down

In a95c652, BOS2 ($URL_BOS2) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BOS2 is back up in 7bda3a9 after 7 minutes.

repo: rholak/upptime


text:
🛑 BOS2 is down

In b5c396d, BOS2 ($URL_BOS2) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BOS2 is back up in 52246d2 after 14 minutes.


text:
🛑 BOS2 is down

In 51da640, BOS2 ($URL_BOS2) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BOS2 is back up in e947722 after 10 minutes.


text:
🛑 BOS2 is down

In 135d028, BOS2 ($URL_BOS2) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BOS2 is back up in 73221c3 after 33 minutes.


text:
Reverting publisher back to printing once when all systems are done

The current approach is a problem for JSON output. The easiest way to do it is to generate a dictionary with the whole answer out of an environment and then dump that into JSON format. That is not possible if the output is generated in steps as systems are queried, I need to have the data all at once.
In order to get that, this PR reverts the publisher to how it was before. Now all systems are polled and a single output is printed with the whole solution.

Mixed the branches out, I will recreate this pull request with the correct one.

repo: rhos-infra/cibyl


text:
Diffusers out of date. Cannot import name 'cached_download' from 'huggingface_hub'

OS: Debian 12
Install steps:
git clone https://github.com/rhymes-ai/Allegro
cd Allegro
python3 -m venv pyevn
source ./pyenv/bin/activate
pip install -r requirements.txt

Download via:
from huggingface_hub import snapshot_download

# Download the model files
model_path = snapshot_download(
    repo_id="rhymes-ai/Allegro",
    local_dir="./Allegro",  # Local directory to save the model
    revision="main"         # Specify the model version/branch
)

But when I run:
python single_inference.py \
--user_prompt "Your text description here" \
--save_path ./output_videos/output.mp4 \
--vae path/to/vae \
--dit path/to/transformer \
--text_encoder path/to/text_encoder \
--tokenizer path/to/tokenizer \
--guidance_scale 7.5 \
--num_sampling_steps 100 \
--seed 42

I get:
Traceback (most recent call last):
  File "/matrix/david/main_home_folder/myProjects/AI/BIN/Allegro/single_inference.py", line 5, in <module>
    from diffusers.schedulers import EulerAncestralDiscreteScheduler
  File "/matrix/david/main_home_folder/myProjects/AI/BIN/Allegro/pyevn/lib/python3.11/site-packages/diffusers/init.py", line 5, in <module>
    from .utils import (
  File "/matrix/david/main_home_folder/myProjects/AI/BIN/Allegro/pyevn/lib/python3.11/site-packages/diffusers/utils/init.py", line 38, in <module>
    from .dynamic_modules_utils import get_class_from_dynamic_module
  File "/matrix/david/main_home_folder/myProjects/AI/BIN/Allegro/pyevn/lib/python3.11/site-packages/diffusers/utils/dynamic_modules_utils.py", line 28, in <module>
    from huggingface_hub import cached_download, hf_hub_download, model_info
ImportError: cannot import name 'cached_download' from 'huggingface_hub' (/matrix/david/main_home_folder/myProjects/AI/BIN/Allegro/pyevn/lib/python3.11/site-packages/huggingface_hub/init.py)

The solution is:
git clone https://github.com/huggingface/diffusers.git
cd diffusers
pip install -e .

This likely needs added to the readme.

repo: rhymes-ai/Allegro


text:
add subPath to config mount

Hi @bueti
This PR fixes the issue with collector config mount. As you may know, SQL exporter need an extra collector config to work properly. It could be defined in ConfigMap and then mounted to /config directory aside of main config file. For example:
extraVolumeMounts:
  - name: collector
    mountPath: /config/sql.collector.yml
    subPath: sql.collector.yml

The problem is that current deployment config takes whole /config directory for mount a single file, so no other file could be mounted. Use of subPath solves this issue.

@bueti ready for merge!

@bueti anybody there?

added with https://github.com/ricardo-ch/helm-charts/pull/78

authors: axelaris bueti

repo: ricardo-ch/helm-charts


text:
v0.5.0リリースノート作成

ついでにリリースノート作成時にPyPIへの登録とかもGitHub Actionsでできると、バージョンや内容の差異が踏まれなくて良いかも

@ShotaroKataoka
#121 にてワークフローでリリース作成することになったので、リリースノートに書く内容をこのissueで議論しようかなと思ってるんですが、どうですか？（こういうのってissueで議論すべきなんですかね？）

@ShotaroKataoka
確かにバージョン決めて開発しますね…
リリースノート作成をissueやる目的は、「このバージョンのリリースノートこれで良いんだっけ？これ抜けてない？この表現分かりにくくない？」みたいなのをやるためですね

@ShotaroKataoka

v0.x.xリリースノート作成

ひとまず↑でやってみます！

@ShotaroKataoka
リリースノート、こんな感じでどうですか？

✨ New Feature

Support .ipynb format files

🐛 Bug Fix

Bug fixed to cause an error if the -w option was not specified when pipe input.

Others

richcat documentation is available: https://richcat-dev.github.io/richcat/

@yamamoto-yuta
良いと思います！

反映したのでcloseします
https://github.com/richcat-dev/richcat/releases/tag/v0.5.0

authors: ShotaroKataoka yamamoto-yuta

repo: richcat-dev/richcat


text:
Stuck on container build

Running docker-compose up left me here:

I'm installing on a 5.5 project.

@neutt22 I have no idea why I never got notified of this issue. How long was it stuck for? First time builds can take a little longer as it needs to build everything and there is no cache. I use this daily on everything from Laravel 5.2 to Laravel 5.6

repo: richdynamix/arc


text:
[Feature Request]Print WiFi MAC address at boot

Could the device print a MAC address on boot to the serial debug console. My office network incorporates MAC address filtering (actually, its about ownership), so it would be good to be able to find this easily.
Thanks!

Hi,
do you have access to the router rules and current clients ?
this is just to know but why also MAC address of the board? what is filtered?
like giving permission to boards with only certain MAC addresses as defining static internal net IP is not posible?

Hi. No. I do not. It is a corporate guest network. I can connect to the WiFi, but unless the device accepts the T&C or is sponsored by an employee (see below) then the device cannot access the internet.
In the end I used the ESPTool's read_mac instruction to get the MAC address, but I'm not sure of the WiFi stack you're using follows this MAC or if it generates a random one.
To sponsor a device, I just need to match the devices MAC address with my LDAP account - easily done, but I need to find the MAC address for the device. It would be cool if this was printed on the LCD for a second while connecting to WiFi or sent via the serial log.

As a workaround, you can connect the iGate to your local accesspoint of your mobile phone, then you see the used MAC.

Thanks @Mane76 - that's a good idea. I just don't want to do that at the office, as I'll confuse all the guest devices when they decide to jump to my phone as the RSSI is better! ;) The easiest option is to just print the MAC at boot. Hence the feature request. Most people will just ignore it, but it's useful for those who want it.
I did use the ESP32Tool to get the MAC but I am not sure that they use the same MAC.
C:\tmp\esptool-win64>esptool --chip esp32-s3 --port COM7 read_mac
esptool.py v4.7.0
Serial port COM7
Connecting....
Chip is ESP32-S3 (QFN56) (revision v0.2)
Features: WiFi, BLE, Embedded Flash 8MB (GD)
Crystal is 40MHz
MAC: 64:e8:33:69:00:04              <---  here
Uploading stub...
Running stub...
Stub running...
MAC: 64:e8:33:69:00:04              <---  here
Hard resetting via RTS pin...
C:\tmp\esptool-win64>

s I'll confuse all the guest devices when they decide to jump to my phone as the RSSI is better!

Normally this should not happen when you give your phone a unique ssid and password and connect the iGate with this credentials.
I checked the esptool code with my iGate, here I have also two MACs shown and they are also equal. And with this MAC the iGate is connecting.
BR
Manfred

this should not happen when you give your phone a unique ssid and password

Agreed; but since it does connect to the WiFi, the AutoAP doesn't start. I cannot change the SSID/PWD easily, so my easiest option is to spoof work's guest network - which is a bad idea for keeping my job ;)
The easiest option would be to print the MAC in future versions of the code during boot. Anyone who did need it would have it. Simple. And only requires half a line of C ;)

Mac address printing over serial output in this new release (today)


text:
Add --quiet command line argument

Quiet makes output quiet unless errors occurs.
Mainly used by automation tools when parsing huge amount of files.
In those cases actual error might get lost in the pile of other stats
prints.
This argument is also handy for build system integration, so it's
possible to add automated lint target to a project and invoke it
via build system and have no pollution of terminals or IDE.
For example when hooking cmakelint to a Ninja project without this
argument oen will have screen filled with "Total Errors: 0" messages,
which defeats all the idea of clean Ninja output.

Thanks, finally got round to merging this!

authors: Nazg-Gul richq

repo: richq/cmake-lint


text:
Publishing changes from background threads is not allowed; make sure to publish values from the main thread (via operators like receive(on:)) on model updates.

Hi. Could you possibly share the relevant code or a reproduction sample?

yeah sure,
The problem i am facing right now is that state is not being observed contiously in IOS  its fluctuating sometimes it works as expected and sometimes.Example code of login/logout senario when login is pressed sometimes i dont see loading, or sometimes the loginstate is not updating something like that. Please help !
Android:
BaseViewModel
open class BaseKMMViewModel : KMMViewModel() {
private val _snackBarVisibleState = MutableStateFlow(viewModelScope, false)
val snackBarVisibleState = _snackBarVisibleState.asStateFlow()
private val _showLoading = MutableStateFlow(viewModelScope, false)
val showLoading = _showLoading.asStateFlow()

private val _showLoadingDialog = MutableStateFlow(viewModelScope, false)
val showLoadingDialog = _showLoadingDialog.asStateFlow()

private val _showMessage = MutableStateFlow(viewModelScope, "")
val showMessage = _showMessage.asStateFlow()

private val _showMessageDialog = MutableStateFlow(viewModelScope, "")
val showMessageDialog = _showMessageDialog.asStateFlow()

private val _logout = MutableStateFlow(viewModelScope, false)
val logout = _logout.asStateFlow()

fun hideSnackBar() {
    _snackBarVisibleState.value = false
}

fun showSnackBar() {
    _snackBarVisibleState.value = true
}

fun showMessage(msg: String) {
    showSnackBar()
    _showMessage.value = msg
}

private fun showMessageDialog(msg: String?) {
    _showMessageDialog.value = msg ?: ApiConstants.defaultErrorMsg
}

fun hideMessageDialog() {
    _showMessageDialog.value = ""
}

fun showLoading() {
    _showLoading.value = true
}

fun hideLoading() {
    _showLoading.value = false
}

fun showLoadingDialog() {
    _showLoadingDialog.value = true
}

fun hideLoadingDialog() {
    _showLoadingDialog.value = false
}

fun showError(error: Exception?) {
    when (error) {

        is UnAuthorizedError -> {
            _logout.value=true
        }

        is IOException -> {
            showMessageDialog("No internet")
        }

        else ->
            showMessageDialog(error?.message ?: ApiConstants.defaultErrorMsg)
    }

}

suspend fun getToken(): String? {
    return if (isTokenValid())
        loginInfo?.accessToken
    else {
       getNewToken()
    }
}

private suspend fun getNewToken(): String? {
    return coroutineScope {
        when (val result =
            LoginRepository.doLogin(
                Login(
                    grantType = ApiConstants.refreshToken,
                    type= ApiConstants.Driver,
                    refreshToken = loginInfo?.refreshToken
                )
            )) {
            is Response.Success<*> -> {
                val loginResponse = result.data as? LoginResponse
                loginResponse?.loginTime = Clock.System.now().toEpochMilliseconds()
                loginInfo = loginResponse
                loginInfo?.accessToken
            }

            is Response.Error<*> -> {
                hideLoading()
                _logout.value=true
                null
            }
        }
    }
}

private fun isTokenValid() =
    (((loginInfo?.expiresIn?.times(1000))?.plus(loginInfo?.loginTime?: 0L))
        ?: 0L) > Clock.System.now()
        .toEpochMilliseconds()

}
=================
LoginViewModel
class LoginViewModel : BaseKMMViewModel() {
private val _loginState = MutableStateFlow(viewModelScope, false)
var loginState = _loginState.asStateFlow()
private fun validateLoginData(login: Login?): Boolean {
if (login?.account.isNullOrEmpty() && login?.password.isNullOrEmpty()) {
showSnackBar()
showMessage("Phone Number and Email shouldn't be empty.")
hideLoading()
return false
}
    if (login?.account.isNullOrEmpty()) {
        showSnackBar()
        showMessage("Phone Number shouldn't be empty.")
        hideLoading()
        return false
    }

    if (login?.password.isNullOrEmpty()) {
        showSnackBar()
        showMessage("Password shouldn't be empty.")
        hideLoading()
        return false
    }

    if ((login?.account?.length ?: 0) < 10) {
        showSnackBar()
        showMessage("Phone Number shouldn't be less than 10 digit.")
        hideLoading()
        return false
    }

    if (login?.account?.startsWith("9") == false) {
        showSnackBar()
        showMessage("The Phone Number format is invalid.")
        hideLoading()
        return false
    }

    return true
}

fun doLogin(login: Login?) {
    if (validateLoginData(login)) {
        viewModelScope.coroutineScope.launch(Dispatchers.IO) {
            showLoading()
            when (val result = LoginRepository.doLogin(login)) {
                is Response.Success<*> -> {
                    hideLoading()
                    val loginResponse=result.data as? LoginResponse
                    loginResponse?.loginTime=Clock.System.now().toEpochMilliseconds()
                    KeyValueStorageImp.loginRequest = login
                    KeyValueStorageImp.loginInfo = loginResponse
                    _loginState.value = true
                }

                is Response.Error<*> -> {
                    hideLoading()
                    showError(result.error as Exception?)
                }
            }
        }
    }
}

}
========== Swift UI = =========
I am observing like this
import SwiftUI
import shared
import KMMViewModelSwiftUI
import SwiftUISnackbar
import FirebaseDatabaseInternal
struct LoginView: View {
@EnvironmentObject var appStateVM:AppStateViewModel
@StateViewModel var viewModel = LoginViewModel()
@StateViewModel var profileVM = ProfileViewModel()
private var isLoggedIn: Binding<Bool> {
    Binding { viewModel.loginState.value as! Bool } set: { _ in        }
}

private var isLoading:Binding<Bool> {
    Binding { viewModel.showLoading.value as! Bool } set: { _ in }
}

private var isProfileLoading:Binding<Bool>{
    Binding {
        profileVM.showLoading.value as! Bool
    } set: { _ in }
}

private var profileStateData:Binding<Profile>{
    Binding {
        profileVM.profileDetailState.value as? Profile ?? Profile(id: nil, firstName: nil, lastName: nil, email: nil, username: nil, phoneNumber: nil, imageName: nil, totalDelivery: nil, licenseNumber: nil, address: nil)
    } set: { _ in }
}

// only with error
private var showMessage:Binding<String> {
    Binding { viewModel.showMessage.value as! String } set: { _ in }
}

private var showMessageDialog:Binding<String> {
    Binding { viewModel.showMessageDialog.value as! String } set: { _ in  }
}

private var snackBarVisible :Binding<Bool> {
    Binding { viewModel.snackBarVisibleState.value as! Bool } set: { _ in  }
}

private func handleValidation() {
    viewModel.doLogin(login: Login(account: phone, password: password, grantType: "password", type: "driver", refreshToken: nil))
}

var body: some View {
   ZStack{
   // other view here
   CustomButton(title: "login", handleAction: {
                    handleValidation()
                })
                .padding([.horizontal],24)
   }

.onChange(of: showMessageDialog.wrappedValue) { newValue in
print("Error (newValue)")
if !newValue.isEmpty {
isAlertShown = true
        }
    }
    .onChange(of:profileStateData.wrappedValue){ newValue in
        print("is logged In \(newValue)")
        // store it to fireabse
        let userId = newValue.id ?? 0
        saveDataToFirebase(userId: Int(truncating: userId))
    }
    .onChange(of:viewModel.loginState.value as! Bool){ newValue in
        print("is logged In \(newValue)")
        if newValue {
            profileVM.getProfile()
        }

    }
}

Thanks that helps a lot!
In the doLogin function you are launching a job on the IO dispatcher:
viewModelScope.coroutineScope.launch(Dispatchers.IO)

All the state updates inside that job won't be performed on the main thread.
Please try and move the dispatcher to the LoginRepository instead.

Thank you so much...It fixed the issue !

authors: rickclephas sangampokharel

repo: rickclephas/KMM-ViewModel


text:
Upgrade "rsvp" version contraint

Allows "rsvp" minor releases too now, which enables NPM to deduplicate more efficiently.

Current coverage is 96.07% (diff: 100%)

Merging #102 into master will not change coverage

@@             master       #102   diff @@
==========================================
  Files             3          3
  Lines           153        153
  Methods          15         15
  Messages          0          0
  Branches         36         36
==========================================
  Hits            147        147
  Misses            6          6
  Partials          0          0

Powered by Codecov. Last update 51d2779...133f8d4

Thanks!

authors: Turbo87 codecov-io rickharrison

repo: rickharrison/broccoli-asset-rev


text:
Feat/add commands

Add following commands for Android/iOS native

getMySetting
setMySetting
deleteMySetting
listPlugin
setPlugin
startPlugin
stopPlugin
getPlugin
setPlugin
setBluetoothDevice(include ReactNative support)
getPluginLicense

Update/Add test code

Update kotlin-multiplatform/src/commonTest/kotlin/com/ricoh360/thetaclient/CheckRequest.kt
Update kotlin-multiplatform/src/commonTest/kotlin/com/ricoh360/thetaclient/repository/options/OptionsTest.kt
Add new test code for added commands to  kotlin-multiplatform/src/commonTest/kotlin/com/ricoh360/thetaclient/repository/

MySetting用に追加したDO_NOT_UPDATE_MY_SETTING_CONDITIONの変換テストを追加した方がよいと思いました。

ExposureDelayEnum
https://github.com/ricohapi/theta-client/blob/0b385e40051ec930cf3e373c823039b3bd381bdb/kotlin-multiplatform/src/commonTest/kotlin/com/ricoh360/thetaclient/repository/options/ExposureDelayTest.kt#L79
FileFormatEnum
https://github.com/ricohapi/theta-client/blob/0b385e40051ec930cf3e373c823039b3bd381bdb/kotlin-multiplatform/src/commonTest/kotlin/com/ricoh360/thetaclient/repository/options/FileFormatTest.kt#L84
IsoAutoHighLimitEnum
https://github.com/ricohapi/theta-client/blob/0b385e40051ec930cf3e373c823039b3bd381bdb/kotlin-multiplatform/src/commonTest/kotlin/com/ricoh360/thetaclient/repository/options/IsoAutoHighLimitTest.kt#L79
MaxRecordableTimeEnum
https://github.com/ricohapi/theta-client/blob/0b385e40051ec930cf3e373c823039b3bd381bdb/kotlin-multiplatform/src/commonTest/kotlin/com/ricoh360/thetaclient/repository/options/MaxRecordableTimeTest.kt#L79

@osakila typoの修正と、DO_NOT_UPDATE_MY_SETTING_CONDITION enumのテストを追加しました。

authors: osakila simago ywatanabe-dev

repo: ricohapi/theta-client


text:
Does matmulfreellm support Windows 10?

I have installed matmulfreellm with Triton for Windows via triton-2.0.0-cp310-cp310-win_amd64.whl which makes matmulfreellm work on the 'configuration' file but fail on the 'generate' file. The 'generate' file with 'ridger/MMfreeLM-370M' gets some problems at model.generate. A brief of error messages are
File "C:\Users\hp\Anaconda3\envs\mat_env\lib\subprocess.py", line 1457, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError:

printout executable and args are
None whereis libcuda.so
Does matmulfreellm supports Windows 10?
Some libraries are listed as follows.
torch              2.3.1+cu118
torchaudio         2.3.1+cu118
torchvision        0.18.1+cu118
transformers       4.41.2
triton             2.0.0

Hi, we have not tested Windows 10 yet since the server we used are all Linux... You can try to upgrade triton to 2.2.0 and cuda to 12.2 or above

@ridgerchu Thanks for your comments. I have upgraded to Triton 2.1.0 for Windows (triton-2.1.0-cp310-cp310-win_amd64.whl). However, the system still doesn't work. I haven't found Trion 2.2.0 for Windows yet. I will suspend my test for now. Do you have any plans to support Windows officially?

It depends when the triton 2.2.0 for windows release I think, without 2.2.0 this repo cannot work well

@ridgerchu Got it. Thanks!

I successfully ran the project on Windows, and I am documenting my process here in hopes of helping others who need it:
Steps to Run the Project on Windows

Clone the Project and Install Dependencies
First, you need to clone the project and install the required dependencies as per the README:
git clone https://github.com/ridgerchu/matmulfreellm.git
pip install einops transformers ninja cmake wheel

Install PyTorch with GPU Support
To use the GPU, I recommend manually selecting the appropriate version of PyTorch from the PyTorch website. You will also need to have CUDA and Visual Studio installed.

Install Triton
Installing Triton is a bit tricky because it officially supports only Linux. However, you can find Windows-compatible builds on GitHub. For example, you can use builds from this GitHub action or Triton Windows Builds.
For my setup, I installed Triton using the following command:
pip install triton-2.1.0-cp310-cp310-win_amd64.whl

My Environment

Python: 3.10
Torch: 2.4.0+cu118

Verifying NVIDIA and CUDA Installation
Run nvidia-smi to check the GPU and driver information:
nvidia-smi
Wed Jul 24 22:17:02 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 551.86                 Driver Version: 551.86         CUDA Version: 12.4     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                     TCC/WDDM  | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 3050 ...  WDDM  |   00000000:01:00.0 Off |                  N/A |
| N/A   44C    P8              6W /   74W |     630MiB /   4096MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------------------------------------------------------+

Run nvcc --version to check the CUDA compiler version:
nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Mon_Apr__3_17:36:15_Pacific_Daylight_Time_2023
Cuda compilation tools, release 12.1, V12.1.105
Build cuda_12.1.r12.1/compiler.32688072_0

Setting Up Environment Variables
You need to set the appropriate environment variables, or use the corresponding Visual Studio command prompt. Ensure you use the correct Visual Studio command prompt (x64 Native Tools Command Prompt for VS XXXX), which automatically configures environment variables.
Alternatively, you can manually add the environment variables before starting your script:
import os

# CUDA Compiler Path
os.environ['CC'] = r"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.1\bin\nvcc.exe"

# Add Visual Studio Compiler Path to PATH
os.environ['PATH'] = r"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\bin\Hostx64\x64;" + os.environ['PATH']

# Add CUDA and Other Include Paths to INCLUDE
os.environ['INCLUDE'] = r"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.1\include;" + \
                        r"C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\ucrt;" + \
                        r"C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\um;" + \
                        r"C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\shared;" + \
                        r"D:\yy\Python\Python310\include"  // Your Python path

# Add CUDA and Other Library Paths to LIB
os.environ['LIB'] = r"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.1\lib\x64;" + \
                    r"C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\um\x64;" + \
                    r"C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\ucrt\x64;" + \
                    r"D:\yy\Python\Python310\libs"  // Your Python path

Running the Script
Finally, to run the script:
python generate.py

You should see output similar to the following:
The attention mask and the pad token id were not set. As a consequence, you may observe unexpected behavior. Please pass your input's `attention_mask` to obtain reliable results.
Setting `pad_token_id` to `eos_token_id`:2 for open-end generation.
The attention mask is not set and cannot be inferred from input because pad token is same as eos token.As a consequence, you may observe unexpected behavior. Please pass your input's `attention_mask` to obtain reliable results.
ptxas info    : 0 bytes gmem
ptxas info    : Compiling entry function 'fused_recurrent_hgrn_fwd_kernel_0d1d2d3d4d' for 'sm_86'
ptxas info    : Function properties for fused_recurrent_hgrn_fwd_kernel_0d1d2d3d4d
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Used 18 registers, 392 bytes cmem[0]
In a shocking finding, scientists discovered a herd of unicorns living in a remote, 200-year-old forest.

I successfully ran the project on Windows, and I am documenting my process here in hopes of helping others who need it:
Steps to Run the Project on Windows

Clone the Project and Install Dependencies
First, you need to clone the project and install the required dependencies as per the README:git clone https://github.com/ridgerchu/matmulfreellm.git
pip install einops transformers ninja cmake wheel

Install PyTorch with GPU Support
To use the GPU, I recommend manually selecting the appropriate version of PyTorch from the PyTorch website. You will also need to have CUDA and Visual Studio installed.
Install Triton
Installing Triton is a bit tricky because it officially supports only Linux. However, you can find Windows-compatible builds on GitHub. For example, you can use builds from this GitHub action or Triton Windows Builds.
For my setup, I installed Triton using the following command:pip install triton-2.1.0-cp310-cp310-win_amd64.whl

My Environment

Python: 3.10
Torch: 2.4.0+cu118

Verifying NVIDIA and CUDA Installation
Run nvidia-smi to check the GPU and driver information:
nvidia-smi
Wed Jul 24 22:17:02 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 551.86                 Driver Version: 551.86         CUDA Version: 12.4     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                     TCC/WDDM  | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 3050 ...  WDDM  |   00000000:01:00.0 Off |                  N/A |
| N/A   44C    P8              6W /   74W |     630MiB /   4096MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------------------------------------------------------+

Run nvcc --version to check the CUDA compiler version:
nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Mon_Apr__3_17:36:15_Pacific_Daylight_Time_2023
Cuda compilation tools, release 12.1, V12.1.105
Build cuda_12.1.r12.1/compiler.32688072_0

Setting Up Environment Variables
You need to set the appropriate environment variables, or use the corresponding Visual Studio command prompt. Ensure you use the correct Visual Studio command prompt (x64 Native Tools Command Prompt for VS XXXX), which automatically configures environment variables.
Alternatively, you can manually add the environment variables before starting your script:
import os

# CUDA Compiler Path
os.environ['CC'] = r"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.1\bin\nvcc.exe"

# Add Visual Studio Compiler Path to PATH
os.environ['PATH'] = r"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\bin\Hostx64\x64;" + os.environ['PATH']

# Add CUDA and Other Include Paths to INCLUDE
os.environ['INCLUDE'] = r"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.1\include;" + \
                        r"C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\ucrt;" + \
                        r"C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\um;" + \
                        r"C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\shared;" + \
                        r"D:\yy\Python\Python310\include"  // Your Python path

# Add CUDA and Other Library Paths to LIB
os.environ['LIB'] = r"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.1\lib\x64;" + \
                    r"C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\um\x64;" + \
                    r"C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\ucrt\x64;" + \
                    r"D:\yy\Python\Python310\libs"  // Your Python path

Running the Script
Finally, to run the script:
python generate.py

You should see output similar to the following:
The attention mask and the pad token id were not set. As a consequence, you may observe unexpected behavior. Please pass your input's `attention_mask` to obtain reliable results.
Setting `pad_token_id` to `eos_token_id`:2 for open-end generation.
The attention mask is not set and cannot be inferred from input because pad token is same as eos token.As a consequence, you may observe unexpected behavior. Please pass your input's `attention_mask` to obtain reliable results.
ptxas info    : 0 bytes gmem
ptxas info    : Compiling entry function 'fused_recurrent_hgrn_fwd_kernel_0d1d2d3d4d' for 'sm_86'
ptxas info    : Function properties for fused_recurrent_hgrn_fwd_kernel_0d1d2d3d4d
    0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Used 18 registers, 392 bytes cmem[0]
In a shocking finding, scientists discovered a herd of unicorns living in a remote, 200-year-old forest.

it is so effective

authors: aoguai fangkuoyu ridgerchu vv-get-ti

repo: ridgerchu/matmulfreellm


text:
Title: Typing Speed Calculator

Is your feature request related to a problem? Please describe.
It is frustrating to visit different websites to measure typing speed.  A chrome extension for the measurement of typing speed will make it convenient to measure typing speed and accuracy.
Describe the solution you'd like.
This extension will allow users to measure their typing speed and accuracy. It will make it handy to check typing speed anytime. It is easy to use and will provide a wonderful experience with a beautiful UI.
Describe alternatives you've considered.
This extension will fetch different quotes each time which makes it engaging and will display the accuracy and speed of typing.
Add any other context or screenshots about the feature request here.

Kindly assign me this issue.

Sorry @Joiyad  but #298 also does the similar thing.

@narayan954  I have seen that extension #298 which is a game for user engagement, it doesn't tell a user about typing speed and accuracy but shows a score which is calculated on the basis of the typed word, it doesn't take into account the accuracy and speed and focus only on completion of the word.

Ok you can work on this or just as a suggestion, would you like to enhance that game and provide these functionalities as well?

According to me, the purpose both extensions serve is different and that's why I would like to make it a new extension. Further, I will try to complete it as soon as possible.

yes you're right, go ahead !

Could you assign it an SSoC label

repo: ridsuteri/Awesome-Chrome-Extensions


text:
🛑 Seoul Server is down

In c48698e, Seoul Server (119.110.71.221) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Seoul Server is back up in 0bd4d04 after 10 minutes.

repo: rifzkiadiyaksa/upptime


text:
Correct graying of attribute names in deep nesting

Properly gray the prefix of attribute names in a table when there are more than 2 nested hashes/structs.
Signed-off-by: Josep M. Blanquer blanquer@rightscale.com

Coverage remained the same at 91.486% when pulling 7f8d362d1c5d3f02e3b7da038d1346add6de2bcd on fix_graying_of_nested_attributes_when_deep into 5e56e5b0c146d8bb72fc7153f1b09dd953579b77 on master.

Build is failing.
I wonder if we should only show one parent property, since if the attribute names are fairly long and deeply nested, the table will soon run out of space.

Coverage remained the same at 91.486% when pulling c11544201b0e83256dabcb1a0a5e30b04c7f6db4 on fix_graying_of_nested_attributes_when_deep into 5e56e5b0c146d8bb72fc7153f1b09dd953579b77 on master.

authors: blanquer coveralls gampleman

repo: rightscale/praxis