Failed to run demo: Cannot read property 'ImageWrapper' of undefined

I'm trying to run this demo in React, but always got error:

import React, { useState, FC, useRef, useEffect, isValidElement } from "react";

import { QuaggaJSStatic } from "@ericblade/quagga2";
import QuaggaLib from "@ericblade/quagga2/lib/quagga";

let Quagga: QuaggaJSStatic = QuaggaLib;

let BarcodeArea: FC<{}> = (props) => {
  let videoElementRef = useRef<HTMLDivElement>(null);

  useEffect(() => {
    Quagga.init(
      {
        inputStream: {
          type: "LiveStream",
          target: videoElementRef.current,
          constraints: {
            width: 400,
            height: 400,
          },
        },
        locate: false,
        numOfWorkers: 2,
        frequency: 10,
        decoder: {
          readers: ["code_128_reader"],
        },
      },
      (err) => {
        if (err) {
          console.error(err);
          return;
        }

        console.log("started");
        Quagga.start();
      }
    );

    Quagga.onDetected((result) => {
      console.log("detect", result);
    });

    Quagga.onProcessed((result) => {
      console.log("process", result);
    });

    return () => {
      Quagga.stop();
    };
  }, []);

  return

;
};

Also I tried to run the demo at http://localhost:8080/example/live_w_locator.html by fixing the paths and adding Quagga = quagga.default. Turned out the problem remains.
Is there a fix for that?

It looks like there is actually no Quagga defined in this function alone: https://github.com/ericblade/quagga2/blob/master/src/quagga.js#L377-L421

Facing the same issue here!

Interesting question, I haven't looked at live_w_locator at all since i've started maintaining this fork ..
I also haven't really looked at the worker interface much at all, at least in part due to the automated tests that I inherited not exercising it at all.  However, I do have a project that uses Quagga2 and uses the worker threads, and it hasn't stopped working (although i think it's still using 0.0.4 or something like that)
It looks like generateWorkerBlob() should be responsible for sending the worker some code to run, but it's not immediately obvious to me exactly what that does, and i'm not certain exactly when I'll get to being able to have a look at that, end of year craziness right now.
I'm not sure how React relates to live_w_locator -- live_w_locator doesn't use React, as far as I remember, and there's a separate example of React using Quagga2 here https://github.com/ericblade/quagga2-react-example/blob/master/package.json
that demo is currently using 0.0.7, but did work when i built it.
Other thing that I can think of, is that there was a build problem with 0.0.11, might try updating to the 0.0.12, which i've tested all the way through the normal pipeline using the qr reader plugin tests.
I might get to having a look at live_w_locator in the next couple of days, might be a while, i'm not entirely certain.  If either of you come up with any further information, let me know :-)
oh, if you could provide exactly how you're running that demo, that'd be helpful too thanks :)

...looked at live_w_locator...

I tried with the working demo on https://serratus.github.io/quaggaJS/examples/live_w_locator.html and looked into the code of workers. the worker code turned out to be much longer than the one I got. looks like it got a Quagga object there.

I'm not sure how React relates to live_w_locator -- live_w_locator doesn't use React

my mistake, I tried the demo live_w_locator. also I tried with @ericblade/quagga2 wrapped in my own React component(code paste above). Both of them run into the same problem read property 'ImageWrapper' of undefined. My current installed version is<EMAIL_ADDRESS>guessing it should be the latest one.
Probably I can get my code bundled and put on web later today...
I'm feeling lucky Quagga still got a maintainer. Thanks for the work.

BTW is there any other demo on your side which runs Quagga2 correctly?

@chenyong the test suite in https://github.com/ericblade/quagga2-reader-qr builds and runs, i'm going to take a second and update the one here: https://github.com/ericblade/quagga2-react-example/blob/master/package.json
and see if that works.  i'll check back in a few minutes
If you're around, I'm on gitter, link in the README here.

It's looking to me like it works.. at least in my browser, when served from localhost

this is using @ericblade/quagga2^0.0.12

I tried downloaded that react example as well, and upgraded to 0.0.12,

the camera(of macbook pro) worked. but when I open the Console, I see errors from worker threads again, on both Chrome Canary 80, and Chrome 79:

hmm. what's the value of navigator.hardwareConcurrency in Safari?
It does sound like the option to use workers is just straight up broken.  I know I was having issues with it trying to use it with custom readers, but I didn't even test it without a custom reader, i don't think..
I do see a bunch of the error on console on Chrome on Windows.  SO, I guess I've got a repro case..
I wonder if you might have time to go back through some previous revisions and see where it works correctly? if we can nail down a specific revision, we should be able to at least get a hint of what broke it.
My thinking is first try 0.0.2 then 0.0.3, as 0.0.3 was the version that introduced the external readers support, and is where i discovered external readers presently don't work with numOfWorkers set.  I hadn't even considered that i might've accidentally broken the worker feature completely, while i was trying to thread through the worker support for the external readers.
I'm going to be absolutely buried in work today / tomorrow (and then i have a lot of free time, that i'll be spending finding new work..) so if you have some time to try, lmk what you find out

undefined in Safari.

Also tried Chrome:

Tried several versions, works with 0.0.10, breaks in 0.0.11.

i wouldn't expect 0.0.11 to actually install, there's a build error there, npm tries to ... oh, i bet if you already had a different version there, it'd install the new one, before it failed out...
I find that to be really interesting, that means that one of the typescript changes seems to be responsible, and I don't recall touching anything near the worker stuff.   ... i .. wonder if it's trying to ship straight up typescript code to the workers.  i need to learn how workers work.
use 0.0.10 in the meantime, i guess, or set numOfWorkers to 0

use 0.0.10 in the meantime, i guess, or set numOfWorkers to 0

yep. should be enough for our current need if it runs and return the code.

wonder if it's trying to ship straight up typescript code to the workers. i need to learn how workers work. . . . and if it's shipping typescript code to the workers... how is it doing that?

not familiar with workers as well. which commit? I may have some time to see where it broke.

I think I need to understand how it was that you examined the code in the workers, if you can point me to how to do that, it might help me understand.  i doubt that it's shipping typescript to the workers, but it might be shipping the contents of something that no longer exists.. that seems more likely.
anyway, my first idea would be to try doing a git bisect between 0.0.10 and 0.0.12, and that should point to the commit. there were a lot of commits in the typescript branch

figured it out, it's the removal of the webpack-plugins\umd.js file that was removed as part of the upgrade to webpack from v2 to v5.  i.. don't think that can be directly put back in, but i think we'll need to study it.  it would put the entire source of the quagga.js module into the factorySource variable .. and that no longer exists...
maybe it can just be put back in.. not sure...

it would put the entire source of the quagga.js module into the factorySource variable .. and that no longer exists...

I prettified code copied from Workers and noticed that code for QuaggaJS was missing. While there is quite some code(although minified so I was not sure) in the Workers of https://serratus.github.io/quaggaJS/examples/live_w_locator.html .

ok, so.. i think we have a few possible options.. we could try to go back to doing it the way it was done before, or attempt to follow a guide like this: https://stackoverflow.com/questions/38715001/how-to-make-web-workers-with-typescript-and-webpack
or one of the links on that page points to this https://github.com/Qwaz/webworker-with-typescript

Got some problem running 0.0.10,

But it does work with numOfWorkers: 0.
I'll be out for a while. It's like already mid-night on your side.. Thanks for the help!

fwiw, following the relatively simple instructions on the webpack worker-loader page at https://webpack.js.org/loaders/worker-loader/ I found it to be very easy to get a proper Worker setup.  Unfortunately, attempting to load Quagga into the Worker resulted in webpack infinite looping.
SO, I think ultimately we need to restructure the worker handling code, which ultimately ties directly into restructuring the entire base of the library, to fix the well known problem where you can't decode multiple images simultaneously with decodeSingle().
I think for the time being, I'm going to disable workers entirely

sounds ok to us. not heavy use of barcode scanner at current.

i'm not convinced that with the current structure of the worker, that there's even any benefit to it -- it just ran multiple copies of itself configured the same way, across multiple threads.  A restructuring of it might perhaps run different decoders on different worker threads.
I've published 0.0.13, if you want to try that and see if it fixes the issue.  I'm going to close this one anyway, in favor of the all-encompassing "restructuring things is really needed", but if this persists, lmk.. i didn't see it in my quick test (i did look at the console output this time :-D )


Add sudo to make install

/usr/local/bin is a root-owned directory, so sudo is necessary to avoid make install failing due to lack of permission.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 60.598%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2573

Relevant Lines:
4246

💛  - Coveralls


Is this repo active?

I would like to contribute and maintain this repo! There's any improvement roadmap or issues guides?

The repo is active, just stable recently. We use it every day in Batteries Included
Roadmap that I know of:

Better documentation for the LiveView pipeline assert
Update to the newest snappy version
Better errors around node types when trying to click on things in live view tests

Cool to know! I would like to tackle errors improvement firstly and then the full documentation

Welcome and thank you for taking a look at the code!


WIP: added select_most_precise<T1, T2>::type

Description
This is a first draft to implement a compile-time selection of a most precise type as suggested in #363.
It follows closely the solution offered by Boost.Geometry, with the following changes:

arity of just 2 (but variable arity can be added later)
modernized to C++11
improved error handling in cases where one cannot select one of both types

Some pending questions:

std::is_floating_point does not support floating point types other than float, double and long double. Do we expect other floating point types?

Any thoughts on this?
Tasklist

[x] Add test case(s)
[ ] Ensure all CI builds pass
[ ] Review and approve

Shall we use std::common_type that has the advantage of following the usual promotion rules and might be specialized by users to support more exotic types (fixed point, multi precision...)?
I found this MP11 example inspiring.

@marco-langer
Boost.Geometry's version allows pairs of integers
using B = boost::geometry::select_most_precise<short, short>::type;

while your variant requires one of the two must be float-point. Is that intentional?
@sdebionne

Shall we use std::common_type that has the advantage of following the usual promotion rules ... ?

Good question. It depends as perhaps we expect:
static_assert(std::is_same<decltype(short{} * short{}), int>::value);

instead of this:
using T = std::common_type<short, short>::type;
static_assert(std::is_same<T, short>::value);

or, BTW,  instead of this:
using T = boost::geometry::select_most_precise<short, short>::type;
static_assert(std::is_same<UT, short>::value);

Yes, disallowing two integral types was intentional (and I forgot to mention it in my above enumeration). While implementing my solution I too came to the same conclusion as @sdebionne, that the Boost.Geometry solution is problematic with respect to missing promotion rules.
While your example seems to be quite reasonable
using T = boost::geometry::select_most_precise<short, short>::type;
static_assert(std::is_same<UT, short>::value);

consider an example in which both types have the same size but different signedness
  using T1 = boost::geometry::select_most_precise<short, unsigned short>::type;
  using T2 = boost::geometry::select_most_precise<unsigned short, short>::type;

  static_assert(std::is_same<T1, short>::value);
  static_assert(std::is_same<T2, unsigned short>::value);

This non-communtativity is either a.) just unintuitive or b.) a potential source of bugs. One can easily contrive examples in which there is a chance of signed integer overflow if calling this trait with the wrong order of template arguements.

This non-commutativity is either a.) just unintuitive or b.) a potential source of bugs.

A very good point.

While implementing my solution I too came to the same conclusion as @sdebionne, that the Boost.Geometry solution is problematic with respect to missing promotion rules.

So, we are leaning towards the std::common_type and given the C++ rule
static_assert(std::is_same<decltype(short{} * short{}), int>::value);

we are agreeing on the following type selection:
static_assert
(
    std::is_same
    <
        std::common_type
        <
            decltype(short{} * short{}),
            short
        >::type,
        int
    >::value
);

Am I getting it right?

Am I getting it right?

Maybe we should have a look at some concrete use cases of this trait before answering this question?

@marco-langer  How about @sdebionne 's #204 ? n.b. it's also a follow-up to #363 discussion, so could be fixed/closed by this PR too.


feat: footer, premium, terms

Fixes Issue
FOOTER

PREMIUM PAGE

Changes proposed

Check List (Check all the applicable boxes)

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

Screenshots

Note to reviewers

There is a premium page coming!!😮

I think you are still working on the issue but still wanted to make observations incase they slip by :

Dark mode style aren't added in the premiums page

The padding seems missing in larger devices

To me the forms seems miss aligned due to its padding

I was playing around with the ui.

I added flex-1 to the button component
These changes to footer.js

I found some of the reasons the tests are failing

The "100% Open Source on GitHub" in the footer has no link.
There is no longer a "Powered by EddieHub" button in the footer but there are still tests that look for that

@ChinmayMhatre wow thank you so much for solving all those issues 😍 !! So you can get green squares do you want to make a PR to my PR? (but note the form is generated from another platform, so there is not much we can do with it)

There is a premium page coming!!😮

There are no Premium features coming for a while, we learnt from the GitHub Accelerator to try and see how many people would be interested in a Premium version - so this is just to get an idea

@ChinmayMhatre wow thank you so much for solving all those issues 😍 !! So you can get green squares do you want to make a PR to my PR?
Some thoughts:

the form is generated from another platform, so there is not much we can do with it
we should add Powered by EddieHub back in, may be a link on 100% Open Source on GitHub, Powered by EddieHub with a link on Powered by EddieHub

There is a premium page coming!!😮

There are no Premium features coming for a while, we learnt from the GitHub Accelerator to try and see how many people would be interested in a Premium version - so this is just to get an idea

I am travelling today, I can create one tomorrow if that works.

I am travelling today, I can create one tomorrow if that works.

Sure @ChinmayMhatre that would be great 👍 . Safe journey!

Hey @eddiejaoude do I branch off from the 'new-footer' branch and then create a new pr into this branch again?

Hey @eddiejaoude do I branch off from the 'new-footer' branch and then create a new pr into this branch again?

@ChinmayMhatre yes that is correct 👍

The footer looks fantastic 🎉

Thank you Pradumna!


UFix64 <-> UInt256 conversion fix and init test coverage

Closes: #56
Description
Fixes UFix64 <-> UInt256 conversion bug that simply truncated decimal values and adds test coverage for the util functionality.

For contributor use:

[x] Targeted PR against main branch
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Code follows the standards mentioned here.
[x] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[x] Added appropriate labels

Codecov Report
Attention: Patch coverage is 96.42857% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 85.89%. Comparing base (428634e) to head (0bf337c).
Report is 69 commits behind head on main.

Files
Patch %
Lines

cadence/contracts/bridge/FlowEVMBridgeUtils.cdc
96.15%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #57      +/-   ##
==========================================
+ Coverage   82.88%   85.89%   +3.00%
==========================================
  Files          18       19       +1
  Lines         818      886      +68
==========================================
+ Hits          678      761      +83
+ Misses        140      125      -15

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


All Node and CommonJS rules deprecated

Hey all,
First of all thanks a lot for maintaining ESLint. It is really helpful and useful. 💯
Just wanted to ask that since all the Node and CommonJS issues show deprecated : true in their rules source, so are they going to be replaced by any set of new issues or is there any other workaround to use them?
Thanks 🙂

hi, these rules have been included in eslint-plugin-node, please give it a try!

Oh, will try it out for sure. Thanks :)


[Enhancement] Optimize the generation of random numbers

Search before asking

[X] I had searched in the issues and found no similar issues.

Feature Request
ThreadLocalRandom performs better than Random in a multi-threaded environment, so I can't use ThreadLocalRandom instead of Random

Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Thanks for the suggestion @weihubeats . BTW, it should be an [Enhancement] instead of [Feature], right?

It should be, thank you for helping me to modify


Adding a test workflow name to the slack bot whitelist

Description
Adding a test workflow name to the slack bot whitelist

Risk

Deploy Plan

FYI @spolu this will allow us to test before communicating with Clay.


Softdelete on shopping cart table

Thanks for this package. It is helping me a lot.
My intention is to extend the functionality of the shoppingcart table by keeping the information on the table after checking out the cart.
To achieve that, I need to soft delete the current instance using the identifier. Is it possible to do that?
I saw deleteStoredCart method on the Cart.php file but I am not sure how to called as it is protected.

its public
https://github.com/hardevine/LaravelShoppingcart/blob/8dea942f3c61ed450fe7dfee968dc9943fa649f8/src/Cart.php#L414


Fix Ray::create() bug

This PR fixes a bug in Ray::create() where a call to a non-existent method (Settings::load()?) prevented the method from returning a new Ray instance.
The call was replaced with SettingsFactory::createFromConfigFile(), allowing the create() method to successfully return a new Ray instance.
Unit test included.

Could you rebase this PR against the current master? Thanks!

Could you rebase this PR against the current master? Thanks!

Thank you!

Thank you!


Small fix to prepare_dataloader

Change the behaviour of prepare_dataloader to make sure it does not throw away data if it does not need to.
Many thanks to @ebeyabraham for finding this issue!

@microsoft-github-policy-service agree company="Microsoft"


Drop old get_query_set syntax, replaced by get_queryset now

Remove some artefacts left on #212:

[x] get_query_set usages

@carljm do you think we should also update the doc to only reflect current code? (like removing PassThroughManager mentions/examples, etc.). Versioning the doc would be ideal, but maybe not that easy...

@romgar Yes, we should update the docs to remove outdated references. The docs in the repo should always match the code in the repo.
ReadTheDocs makes doc versioning very easy; I just went into the RTD admin and enabled building the docs for the latest bugfix release in each minor release series back to 1.5.0. I also added you as RTD admin for the project so you can manage this in future if you want.

I didn't think it was that easy... I will manage it then, and clean the doc for the latest version at least.


fix: updated model types

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


add precommit config

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
:loudspeaker: Thoughts on this report? Let us know!.


[kcp] Add new port

https://github.com/skywind3000/kcp/blob/master/README.en.md
https://repology.org/projects/?search=kcp&maintainer=&category=&inrepo=&notinrepo=&repos=&families=&repos_newest=&families_newest=

Hi @myd7349
Is there any work left to be done in this port?

Hi! @vicroms I think I have finished this port.


Changed name of container_replication_controller to container_replicator

@abonas @simon3z Please review
I kept the name replication controller wherever k8s objects(like pod) are referenced such as here

I kept the name replication controller wherever k8s objects(like pod) are referenced such as here

yes, this is OK :)

:+1: I like this much better.  Otherwise, minor comments and it needs a rebase.

I like this much better. Otherwise, minor comments and it needs a rebase.

@Fryguy  Fixed and rebased.

:+1:  but I think there's one line that doesn't belong to this PR (commented inline).

:+1: but I think there's one line that doesn't belong to this PR (commented inline).

Fixed.

:+1: thanks @zeari, @Fryguy can you review/merge? Thanks!


Create Chrome Extension to Generate and Commit Devcontainer Files from GitHub Repositories

Is your feature request related to a problem? Please describe.
Users often need a quick way to generate and commit a devcontainer.json file directly from a GitHub repository's interface. Manually generating and committing the file involves multiple steps and can be cumbersome.
Describe the solution you'd like

Develop a Chrome extension that integrates with the GitHub interface.
When the user is on a GitHub repository page, the extension should display a button.
Upon clicking the button, the extension will:

Check if the user is authenticated with GitHub through the extension.
If authenticated, generate a devcontainer.json file and create a pull request (PR) committing it to the repository.
If not authenticated, allow the user to download the generated devcontainer.json as a raw file.

Describe alternatives you've considered

Providing a CLI tool for similar functionality, but this would not be as seamless or integrated as a browser extension.
Using a web-based service where users can enter repository URLs manually, but this adds steps and reduces convenience.

Additional context

Chrome Extension Development:

Use the Chrome Extensions API to create the extension.
Implement content scripts to detect when the user is on a GitHub repository page.

Authentication:

Use GitHub OAuth to handle authentication within the extension.
Store the authentication token securely and use it for API calls.

GitHub API Integration:

Make API calls to generate the devcontainer.json and create a PR using the authenticated user's credentials.
If the user is not authenticated, fetch the devcontainer.json and allow them to download it.

UI/UX:

Design a user-friendly button that appears on GitHub repository pages.
Provide clear feedback and instructions based on the user's authentication status.

Dependencies:

Ensure the feature depends on the backend capability to fetch the generated devcontainer.json via URL hash.

Example Flow:

User visits a GitHub repository page.
Extension displays a "Generate Devcontainer" button.
On click, extension checks if the user is authenticated.

If yes, generate and commit the devcontainer.json via PR.
If no, provide the devcontainer.json file for download.

/bounty $50

@nkkko Do we need a new repo for this chrome extension?

@nkkko If the extension potentially grows with additional features or integrations, we can create a new repository. However, i think for now it remains a simple utility tightly coupled with the main project, it could reside in the same repository under a dedicated folder (e.g., /chrome-extension)...thoughts?


Prepare release v0.5.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.452%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
153

Relevant Lines:
157

💛  - Coveralls


made an e2e.go file and created a function for making base command

What this PR does / why we need it:
Focus of this PR is on making a e2e dry run helper. See more details here
Which issue(s) this PR fixes

Fixes #1524

Special notes for your reviewer:
Release note:
release-note

@johnSchnake just made the base command.
Is it alright ?
If it is, then what should be the logic inside the functions for adding subcommands.

I wont have much availability to look at this this week; I'll try but it may be next week before I get a chance. Just FYI

@johnSchnake Just reminding about the PR.
Could you read the above comments and give your feedback.

@johnSchnake Just reminding about the PR.
Could you read the above comments and give your feedback.

So you dont have much here yet to review. Here are a few milestones you can iterate towards:

add the flags to the command (ensure they are parsed correctly)
Add the subcommands and their flags as needed
add increasing bits of the core logic (see below)

Flush out the logic the best you can. As the originating issue said, we'll put the tests into github so you know you'll need to just do an HTTP GET to pull the tests down. So you can set up the code to do that and apply the focus/skip to it. The URL can be specified later.

First, just hardcode a few strings ("a\nb\nc" for instance) and apply the regexps so you can be done with the focus/skip logic
add in code to get that string from a URL
add the logic to have the URL depend on the k8s version

@johnSchnake could you please share some resources from where I can learn about making these (for listing the tests and filtering them through regexp package) kind commands, I looked in some commands in kubernetes repo where we take input and list resources (pod, deployment etc.), but even after hours of brainstorming I am still not able to find a reasonable solution.
Apologies for asking questions more than doing.

I'm not exactly sure which part you're asking about. I'll try and answer what I think is your question though.
For now assume that you have an io.Reader that has a bunch of test names in it. Just hardcode it for now; it can just be a hardcoded string that you put into a strings.Reader.
Then read line by line and check if it matches the focus regexp and/or the skip regexp and decide whether the test should be chosen or not. The regexp package has examples of how to do regexp checks: https://pkg.go.dev/regexp#example-MatchString
Then if it matches it, add it to an io.ReadWriter (probably just a *bytes.Buffer) and return it.
Does this answer your question?

@NikhilSharmaWe Do you mind if I run with this a bit? I'm putting up a poc list of tests (tiny list) and will just tinker to get it in a usable state. I know you were struggling with the direction on this and it is larger than some of the initial PRs you've taken on.

@johnSchnake Yes of course, I will be observe and learn from how you will move forward with adding this feature.


add: Vishal Isharani

Description
I have added my profile.
Related Issues
Changes Proposed
Checklist

[x] I have read and followed the Contribution Guidelines.
[x] All new and existing tests passed.
[x] I have updated the documentation to reflect the changes I've made.
[x] My code follows the code style of this project.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
Note to reviewers

@Vishal-Isharani Thank you so much for your contribution! Your efforts are greatly appreciated and will go a long way in improving our project. Please feel free to share it with others and help us grow even further!
Try to create a new branch and make changes to that branch before raising an PR.


Base map last updated dates

basemap last cached dates and possibly link to data update doc

Yes, it's a spreadsheet at the moment. But I could have honeycomb write to whatever.


2.1.0rc0 doesn't find GPU libraries

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10 1909
TensorFlow installed from (source or binary): source
TensorFlow version: 2.1.0rc0
Python version: 3.7.5
Installed using virtualenv? pip? conda?: pip/virtualenv
CUDA/cuDNN version: Cuda 10.0, cudnn v7.6.4
GPU model and memory: rtx 2060 6gb

Describe the problem
2.1.0rc0 and nightly builds doesn't see any of the libraries below, and it defaults to use CPU.
Any other info / logs
2019-12-01 20:12:55.597639: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'cudart64_101.dll'; dlerror: cudart64_101.dll not found
2019-12-01 20:12:55.601941: I tensorflow/stream_executor/cuda/cudart_stub.cc:29] Ignore above cudart dlerror if you do not have a GPU set up on your machine.
timestamp divided..
timestamp divided..
(1112,)
2019-12-01 20:12:59.141649: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library nvcuda.dll
2019-12-01 20:12:59.168743: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1555] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce RTX 2060 computeCapability: 7.5
coreClock: 1.695GHz coreCount: 30 deviceMemorySize: 6.00GiB deviceMemoryBandwidth: 312.97GiB/s
2019-12-01 20:12:59.176962: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'cudart64_101.dll'; dlerror: cudart64_101.dll not found
2019-12-01 20:12:59.181864: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'cublas64_10.dll'; dlerror: cublas64_10.dll not found
2019-12-01 20:12:59.186511: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'cufft64_10.dll'; dlerror: cufft64_10.dll not found
2019-12-01 20:12:59.191583: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'curand64_10.dll'; dlerror: curand64_10.dll not found
2019-12-01 20:12:59.197264: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'cusolver64_10.dll'; dlerror: cusolver64_10.dll not found
2019-12-01 20:12:59.202050: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'cusparse64_10.dll'; dlerror: cusparse64_10.dll not found
2019-12-01 20:12:59.216645: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cudnn64_7.dll
2019-12-01 20:12:59.219553: W tensorflow/core/common_runtime/gpu/gpu_device.cc:1592] Cannot dlopen some GPU libraries. Please make sure the missing
libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...
2019-12-01 20:12:59.232902: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not
compiled to use: AVX2
2019-12-01 20:12:59.236973: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1096] Device interconnect StreamExecutor with strength 1 edge matrix:
2019-12-01 20:12:59.246142: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1102]
<RepeatDataset shapes: ((None, 720, 1), (None,)), types: (tf.float64, tf.float64)>
(720, 1)
Train for 200 steps, validate for 50 steps

2019-12-01 20:12:55.597639: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'cudart64_101.dll'; dlerror: cudart64_101.dll not found
2019-12-01 20:12:55.601941: I tensorflow/stream_executor/cuda/cudart_stub.cc:29] Ignore above cudart dlerror if you do not have a GPU set up on your machine.
timestamp divided..
timestamp divided..
(1112,)
2019-12-01 20:12:59.141649: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library nvcuda.dll
2019-12-01 20:12:59.168743: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1555] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce RTX 2060 computeCapability: 7.5
coreClock: 1.695GHz coreCount: 30 deviceMemorySize: 6.00GiB deviceMemoryBandwidth: 312.97GiB/s
2019-12-01 20:12:59.176962: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'cudart64_101.dll'; dlerror: cudart64_101.dll not found
2019-12-01 20:12:59.181864: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'cublas64_10.dll'; dlerror: cublas64_10.dll not found
2019-12-01 20:12:59.186511: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'cufft64_10.dll'; dlerror: cufft64_10.dll not found
2019-12-01 20:12:59.191583: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'curand64_10.dll'; dlerror: curand64_10.dll not found
2019-12-01 20:12:59.197264: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'cusolver64_10.dll'; dlerror: cusolver64_10.dll not found
2019-12-01 20:12:59.202050: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'cusparse64_10.dll'; dlerror: cusparse64_10.dll not found
2019-12-01 20:12:59.216645: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cudnn64_7.dll
2019-12-01 20:12:59.219553: W tensorflow/core/common_runtime/gpu/gpu_device.cc:1592] Cannot dlopen some GPU libraries. Please make sure the missing
libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...
2019-12-01 20:12:59.232902: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not
compiled to use: AVX2
2019-12-01 20:12:59.236973: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1096] Device interconnect StreamExecutor with strength 1 edge matrix:
2019-12-01 20:12:59.246142: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1102]
<RepeatDataset shapes: ((None, 720, 1), (None,)), types: (tf.float64, tf.float64)>
(720, 1)
Train for 200 steps, validate for 50 steps

Closed by mistake

Try using a video driver >= 418.96 and Cuda 10.1

Try using a video driver >= 418.96 and Cuda 10.1

I thought it doesn't support Cuda 10.1, it doesn't mention on release notes.

Please see https://github.com/tensorflow/tensorflow/pull/34494

Please see #34494

Oh thank you a lot that's great, I'm upgrading now. Closing it.


[REVIEW] linuxdotexe

GitHub Profile Link
https://github.com/linuxdotexe

Looks great, some suggestions

try to contribute more to open source
also try to do more pull requests, reviews, and issues


Create Project Portfolio Page

Sample at:
https://github.com/nusCS2113-AY1819S1/addressbook-level4/blob/master/docs/team/johndoe.adoc

Resolved through #175


Tag Hooks not working for Gogs

Tag hook support for Gogs was introduced in #1498 but is not working (anymore).
I tested using the latest Drone 0.5 image from Docker Hub and the latest version of Gogs on Docker Hub.
The Gogs webhook payload is:
{
  "secret": "mysecret",
  "ref": "0.0.5",
  "ref_type": "tag",
  "repository": {
    "id": 84,
    "owner": {
      "id": 3,
      "username": "org",
      "full_name": "Organization",
      "email": "",
      "avatar_url": "https://gogs.somewhere.com/avatars/3"
    },
    "name": "project",
    "full_name": "org/project",
    "description": "Some description",
    "private": true,
    "fork": false,
    "html_url": "https://gogs.somewhere.com/org/project",
    "ssh_url": "ssh://git@gogs.somewhere.com:10022/org/project.git",
    "clone_url": "https://gogs.somewhere.com/org/project.git",
    "website": "",
    "stars_count": 0,
    "forks_count": 0,
    "watchers_count": 7,
    "open_issues_count": 0,
    "default_branch": "master",
    "created_at": "2016-11-24T08:42:01Z",
    "updated_at": "2016-11-24T12:21:33Z"
  },
  "sender": {
    "id": 1,
    "username": "michael",
    "full_name": "Michael de Wit",
    "email"<EMAIL_ADDRESS>    "avatar_url": "https://gogs.somewhere.com/avatars/1"
  }
}

It also sends the following headers:
X-Gogs-Delivery: asdf-asdf-asdf-asdf
X-Gogs-Event: create

The Drone response is successful (200 OK), but the body is empty and no build is triggered (the project has steps for "tag" events).
Tag Hooks are enabled in the Drone repository settings, and Create hooks are enabled in the Gogs repository settings.

I have a patch to improve the tag implementation that I will submit shortly, however, Gogs does not return the sha in the tag hook. This is a problem for Drone because we need a sha in order to fetch the .drone.yml using the Gogs API.
I think we've done as much as we can from the Drone side of things, and now require improvements to the Gogs hook payload to include sha:
{
+ "sha": "940bd336248efae0f9ee5bc7b2d5c985887b16ac",
  "ref": "v1.0.0",
  "ref_type": "tag",
  "repository": {
    "id": 1,
    "owner": {
      "id": 1,
      "username": "gordon",
      "full_name": "Gordon the Gopher",
      "email"<EMAIL_ADDRESS>      "avatar_url": "https://secure.gravatar.com/avatar/8c58a0be77ee441bb8f8595b7f1b4e87"
    },
    "name": "hello-world",
    "full_name": "gordon/hello-world",
    "description": "",
    "private": true,
    "fork": false,
    "html_url": "http://gogs.golang.org/gordon/hello-world",
    "ssh_url": "git@gogs.golang.org:gordon/hello-world.git",
    "clone_url": "http://gogs.golang.org/gordon/hello-world.git",
    "default_branch": "master",
    "created_at": "2015-10-22T19:32:44Z",
    "updated_at": "2016-11-24T13:37:16Z"
  },
  "sender": {
    "id": 1,
    "username": "gordon",
    "full_name": "Gordon the Gopher",
    "email"<EMAIL_ADDRESS>    "avatar_url": "https://secure.gravatar.com/avatar/8c58a0be77ee441bb8f8595b7f1b4e87"
  }
}

For gitea we already merged a fix for that, but we can't influence Gogs as unknwon is not available.

Before this can be closed, a change is required in Drone.
Drone uses the raw file API of Gogs/Gitea to retrieve the .drone.yml config file, it accesses this API using the following endpoint: GET /repos/:username/:reponame/raw/:ref/:path, but it uses the full git ref as :ref (refs/tags/v1.0.0). Gogs and Gitea only support a short ref (v1.0.0).

I'm not sure why it uses the API for this at all? just regular /:user/:proj/raw/:sha/.drone.yml should work just fine. TBH I'm not sure why gogs/gitea even has this endpoint 😕

It may have been part of @bradrydzewski's fix, because the SHA was not included in the webhook payload at first. It's just that it was never going to work because of an incorrect implementation.
As far as I can see, there are two possible solutions now:

Fix the current raw API implementation, correctly using the short ref. The upside of this fix will be that it will also be compatible with Gogs.
Remove usage of the raw API and use the SHA to directly access the file, as suggested by @bkcsoft. The upside is that this is probably very similar to other Git services, the downside is that Gogs will not work with this, since it's missing a SHA in the payload.

I think that we need something like GitHub because gogs try to implement
API like GitHub.
20 Дек 2016 г. 16:20 пользователь "Michael de Wit"<EMAIL_ADDRESS>написал:

It may have been part of @bradrydzewski https://github.com/bradrydzewski's
fix, because the SHA was not included in the webhook payload at first. It's
just that it was never going to work because of an incorrect implementation.
As far as I can see, there are two possible solutions now:

Fix the current raw API implementation, correctly using the short
ref. The upside of this fix will be that it will also be compatible with
Gogs.
Remove usage of the raw API and use the SHA to directly access the
file, as suggested by @bkcsoft https://github.com/bkcsoft. The
upside is that this is probably very similar to other Git services, the
downside is that Gogs will not work with this, since it's missing a SHA in
the payload.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/drone/drone/issues/1870#issuecomment-268241107, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAdYGwlrcrbS4sPd9fCQsbhHcC8J3lwyks5rJ9YFgaJpZM4K7t8q
.

Fix the current raw API implementation, correctly using the short ref. The upside of this fix will be that it will also be compatible with Gogs.

I prefer this option.

Remove usage of the raw API and use the SHA to directly access the file

The potential problem with this option is Gogs and Gitea will eventually implement application oauth, granting access to API endpoints. For this reason I would prefer the Drone codebase to rely on the API endpoints as much as possible.

Hi, any work on progress in this issue?

@lunny I'm working on a PR

👍

tested in my local， fantastic

same issue here with latest gogs 0.9.113 (released yesterday).
not only tag event, but PR and branch create does not work as well.

Drone does not support PR or branch create events. It supports push events. Lack of PR support is documented

OK thank you! may be because gogs has delivery on these events, caused me to expect drone to support them!!! sorry!
is that planed to implement? specially on PR that could be very helpful (checking tests before merging, for example)

There is an open issue for PR support if you want to subscribe to https://github.com/drone/drone/issues/1605
It is certainly a feature I'd like to see, but unfortunately I have other items I need to focus on right now. Certainly open to contributions, though.

merged fix, thanks!


Increase the API definition of Extend Volume

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
design spec #2
Special notes for your reviewer:
Release note:

Coverage remained the same at 42.232% when pulling d6868de06198c9690daa703c9f41f6d546a5da31 on BaiHuoYu:volume_action_API_definition into 2aa4451590f5cd4a826f65427146f1ac175d8ee9 on opensds:development.


Locking for stdin

Implement

Stdin::lock
Stdout::lock
Stderr::lock

ref: https://github.com/async-rs/async-std/issues/229

Thanks for the PR! I think we should make async versions of StdinLock, StdoutLock, and StderrLock. If we lock an async I/O handle, we should also get back an async I/O handle.
Also, methods like std::io::StdinLock::lock() are blocking operations, so we should perhaps spawn a blocking task that acquires the lock.

Yh!
However, I am a little worried about what to implement.
please wait a moment.

Oh. I accidentally erased the branch...

It is probably CI upset that CI will fail.
I believe this PR will be solved.
https://github.com/async-rs/async-std/pull/414

@k-nasa merged the branch you linked!


Support rbenv-gem-rehash

Support rbenv-gem-rehash. This plugin automatically runs rbenv rehash.

Thank you :+1:

Released as v0.3.2 :gem:

:heart_eyes:


runtime failure using derived types and multidimensional cobounds

Avg response time

Defect/Bug Report

OpenCoarrays Version: 4cc41bf4f301190c (1.9.3+)
Fortran Compiler: GNU Fortran (GCC) 7.3.0 (release)
C compiler used for building lib: gcc (GCC) 7.3.0 (release)
Installation method: cmake ..; make -j; make install
Output of uname -a: Linux <...> 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
MPI library being used: mpich 3.2.1 (release)
Also tested with OpenMPI 3.0.0  (release)
Machine architecture and number of physical cores: x86_64 12 cores
Version of CMake: cmake version 3.10.2 (release)

Observed Behavior
On the following example, running on 8 images, the scattering from rank 1 fails when using a coarray in a derived type, whereas we observe no issue with pure coarrays.
log
# cafrun -np 8 ./scatter false
global size           8           6
local size           2           3
 all close ? T

# cafrun -np 8 ./scatter true
 global size           8           6
local size           2           3
Fortran runtime error on image 1: libcaf_mpi::caf_send_by_ref(): unable to allocate memory on remote image.

Expected Behavior
The following sequence should not fail.
Steps to Reproduce
script
#!/usr/bin/env bash
caf -o scatter scatter.f90

cafrun -np 8 ./scatter false
cafrun -np 8 ./scatter true

scatter.f90
program main
   implicit none

   type co_arr
      real, allocatable :: a(:, :)[:, :]
   end type

   type(co_arr) :: co1 ! derived type with coarray
   real, allocatable :: co2(:, :)[:, :] ! pure coarray
   real, allocatable :: glob(:, :), buf2d(:, :)
   integer, parameter :: nx = 2, ny = 3 ! local chunk, same over all images
   integer :: me, nimg, mx, my, i, j, k
   character(len = *), parameter :: tab = char(9), nl = char(10)
   character(len = 10) :: arg
   logical :: switch

   call getarg(1, arg)
   read (arg, '(L)') switch

   me = this_image()
   nimg = num_images()
   mx = nimg / 2 ! 2d grid distribution
   my = nimg / mx

   if (nimg /= 8) then
      stop 'example for 8 images'
   end if

   allocate(co1 % a(nx, ny)[mx, *])
   allocate(co2(nx, ny)[mx, *])
   allocate(buf2d(nx, ny), glob(mx * nx, my * ny))

   if (me == 1) print *, 'global size', [(mx * nx), (my * ny)], nl, 'local size', [nx, ny]

   ! call random_number(glob)
   glob = reshape([(i, i = 1, (mx * nx) * (my * ny))], shape(glob))

   sync all ! separate segments
   if (me == 1) then
      ! scatter glob from root (1st image)

      ! local to local
      co1 % a = glob(:nx, :ny)
      co2 = glob(:nx, :ny)

      ! loop over all other images
      do i = 1, mx
         do j = 1, my
            k = image_index(co2, [i, j])
            if (k /= 1) then
               buf2d = glob((i - 1) * nx + 1:i * nx, (j - 1) * ny + 1:j * ny) ! send buffer
               ! print *, 'filling up image #', k, '[', [i, j], ']', nl, tab, '==>', buf2d, nl
               if (switch) then
                  co1 % a(:nx, :ny)[i, j] = buf2d ! <= failure
               else
                  co2(:nx, :ny)[i, j] = buf2d ! ok
               end if
            end if
         end do
      end do
   end if
   sync all

   ! output local arrays after scattering
   ! print *, me, 'co1', co1 % a, nl, me, 'co2', co2

   ! collect results on rank 1
   call co_sum(co1 % a, result_image = 1)
   call co_sum(co2, result_image = 1)

   sync all
   if (me == 1) print *, 'all close ?', abs(sum(glob) - sum(merge(co1 % a, co2, switch))) < epsilon(0.)

   deallocate(co1 % a, co2, glob)
end program

@neok-m4700:
First of all, please let me say THANK YOU for the amazing bug report and sleuthing! We REALLY appreciate thorough and detailed bug reports like this! 💯 🙇 🥇
Second, may we adapt the code you posted above as a regression test for OpenCoarrays?
Third, I will look into applying your patch to the library, if you consent to it, and if I can verify its correctness.
Thanks once again, and sorry I was slow to get to this, work has been nuts recently!

Thanks, @zbeekman !
Yes sure, please use and modify the test case for non-regression.
OC seems mature enough for a research code, so I'm trying to port my own CFD code from a shared mem approach in C to Fortran for HPC runs under MPI, and coarrays seems to provide smooth transition for PGAS like programs, while covering the ugly bits of comms (cleaner code = better code).
 Warning ! sendget_by_ref() is mostly unfunctional due to a design error

which has to be split into something like
allocate(buf(...))
buf = co % rhs
co % lhs = buf
deallocate(buf)

It's ok for now, as long as the program runs ...
Feel free to close the issue if you think it's resolved in master.

We are thrilled that using CAF in production research code appeals to you
and will do everything in our power to try to make its adoption as painless
as possible. I certainly agree it is much more pleasant to use than MPI.
Just a word of caution: some issues (compiler side mostly) persist with
indirect addressing (vector subscripts) so structured grids should be
fairly doable, but some issues that are relevant to unstructured grids may
be a source of frustration. We’re addressing it as quickly as possible.
Also coarray objects with pointer or allocatable components are a WIP and
you may find some rough edges there.
Also, please keep in mind that much OC development is done by volunteers or
thanks to monetary donations, by Sourcery Institute and a few others.
Currently, however, development is unfunded. We welcome suggestions for
funding opportunities and contributions in terms of pull requests. I think
I can speak for @rouson and others when I say that we would be happy to
jointly author grant proposals etc to better support your research through
funding additional OC development.
Lack of resources aside, we will be as responsive as possible but certain
issues could take some time to resolve without additional funding or source
code contributions.
Cheers,
Izaak “Zaak” Beekman
On Sat, Feb 3, 2018 at 12:08 PM neok-m4700<EMAIL_ADDRESS>wrote:

Thanks, @zbeekman https://github.com/zbeekman !
Yes sure, please use and modify the test case for non-regression.
OC seems mature enough for a research code, so I'm trying to port my own
CFD code from a shared mem approach in C to Fortran for HPC runs under MPI,
and coarrays seems to provide smooth transition for PGAS like programs,
while covering the ugly bits of comms (cleaner code = better code).
 Warning ! sendget_by_ref() is mostly unfunctional due to a design error
which has to be split into something like
allocate(buf(...))
buf = co % rhs
co % lhs = bufdeallocate(buf)
It's ok for now, as long as the program runs ...
Feel free to close the issue if you think it's resolved in master.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sourceryinstitute/OpenCoarrays/issues/488#issuecomment-362835047,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAREPDsM1zh-2UiPyJ6becNsbUz4Mu8Eks5tRJKOgaJpZM4RyTmE
.

Yes.


Provide a simulation mode that guarantees no out of memory errors

This will require keeping track of memory currently allocated in GPU, and ask cuTensorNet how much memory the next primitive (contract or tensor decompose) will require.

Proper support for this will be possible after the next release of CuTensorNet (see https://github.com/NVIDIA/cuQuantum/issues/156). A hack is possible at the moment, but perhaps it is not high priority.


Small Code Updates to support Python3.11

When using cimpyorm with python 3.11 there is an Import Error for from collections import ..., Iterable, ...
see also:
The Iterable abstract class was removed from collections in Python 3.10. See the deprecation note in the 3.9 [collections docs](https://docs.python.org/3.9/library/collections.html). In the section [Removed](https://docs.python.org/3/whatsnew/3.10.html#removed) of the 3.10 docs, the item

Remove deprecated aliases to [Collections Abstract Base Classes](https://docs.python.org/3/library/collections.abc.html#collections-abstract-base-classes) from the collections module. (Contributed by Victor Stinner in bpo-37324.)

This PR fixes the Code Issue.
Additionally i adjusted the pylintrc config (got some warnings) and GitlabCI + GithubAction config to support for a broader range of Python Versions being tested

Jo @TOffergeld,
Thanks for the quick review, I guess once you are Maintainer of a project and didn't turn off notifications you'll get notified :D
Do you know of the person responsible for this repo or was there any agreement on whoever is the maintainer?
Otherwise we can also try to get into contact with the IAEW


Update to ghc 8.10.7 and latest haskell.nix, nixpkgs-unstable and iohk-nix

We are trying out an aarch64-darwin build of daedalus on https://ci.zw3rk.com/project/daedalus.  It needs these updates.
See https://github.com/input-output-hk/daedalus/pull/2684 and https://github.com/input-output-hk/daedalus/pull/2683

@rvl, I am not sure how useful this is to you.  I see you already have PRs for these updates.  I did run into an issue with cardano-config needing git that required addition of the build-tools override (that might have only been when I was using the master branch of cardano-node).  haskell-language-server also seemed to need a bump to work with ghc 8.10.7.


fix: Fixed crash issue for video enabled in android devices

What
The plugin-used apps are crashing on Android devices while the video is enabled due to beta version usage of native android camera package.
Changes
changed the package versions of camera from beta to stable.
Tested on
Oppo Reno 7 5G, android 13
Related issues
Fixes #1425
Closes #1425
Resolve #1425

Thanks for your PR!! Looks good to me

@mrousavy I have checked it by reinstalling the package but still getting old code can you please publish it on npm or provide me some steps to upload it on npm

As of August 11, 2023, it appears that the resolution for this issue has not yet been deployed to the npm repository. The problem remains unaddressed, which could potentially impact users relying on this fix.

Is it possible to deploy this fix. I am having issues on android devices that this would solve. Any movement here would be greatly appreciated 🙏🏼

Hey - done, I just released this in 2.15.6! :)

Thank you so much!

On the Oppo Reno 8 5G, when I try to use VisionCamera, it shows a blank screen. On other Oppo devices, it works fine.

Have you encountered such a problem?

On the Oppo Reno 8 5G, when I try to use VisionCamera, it shows a blank screen. On other Oppo devices, it works fine.   Have you encountered such a problem? both "react-native-vision-camera": "2.16.2", and "react-native-vision-camera": "2.16.5",

I haven't faced that kind of issue in my oppo device maybe you can try version 3 of the package. But it contains some breaking changes so, clear your requirements and look around for the solution in the package and integrate.

On the Oppo Reno 8 5G, when I try to use VisionCamera, it shows a blank screen. On other Oppo devices, it works fine.   Have you encountered such a problem? both "react-native-vision-camera": "2.16.2", and "react-native-vision-camera": "2.16.5",

I haven't faced that kind of issue in my oppo device maybe you can try version 3 of the package. But it contains some breaking changes so, clear your requirements and look around for the solution in the package and integrate.

Thanks for your reply. I found that Vision 3 does not support orientation about 2 months ago. So I do not want to upgrade until the orientation of V3 is fixed.


Graph View from pjarnfelt was perfected by me

Now all manipulations with reanimator can be maked in graph view.

I just noticed this pull request.
(lol, wish I would have seen this earlier).
In case anything can help you with your implementation, here is how I implemented GraphView: https://github.com/JoshMayberry/ReanimatorHelper/tree/1f1b511ed3eb64b8ae72f56fcff345d552e1737b

I'm sure your implementation is much better than the one I cobbled together- but if my code can be of any help to you at all- use what you need from it. :D

@JoshMayberry Oh, just see your comment. Thx for providing another implementation. My one has only switch and basic animation nodes as i remember, so if you fully realized all functionality thats cool. I'd recommend mentioning that in Issues tab Visual editor enchancment so other can find your work.

Not all functionality was implemented so cant use properly


[iOS] NS_ASSUME_NONNULL_BEGIN

@phvannor previously I had made a PR adding nullability attributes, but there are macros for NS_ASSUME_NONNULL_BEGIN and NS_ASSUME_NONNULL_END.
All the nonnull annotations could be removed with these and would make it slightly cleaner and less to do for new code. Downside being if the author doesn't think about nullability, it will assume non-null which may be in error.
Thoughts on converting to the macros? Or continue to use explicit nonnull and nullable annotations?

I believe Apple's doc officially recommends using them, so I see no reason not to.  Probably just something to do as files are touched.  Not worth changing on its own most likely.

Agreed, will keep in mind with any future changes


Unicode icons are not portable

Several of the default icons used are in the private use area of Unicode, which means they can vary wildly from font to font and will most likely look like gibberish to anyone who is not using the exact same font as you. I propose replacing the defaults with something standardized; it will not look the same to everyone, but at least it will look like more or less similar.
The signs in question are:

g:ultest_pass_sign
g:ultest_fail_sign
g:ultest_running_sign
g:ultest_not_run_sign

I propose:

g:ultest_pass_sign: ✓ Check Mark U+2713
g:ultest_fail_sign: 🗲 Lightning Mood U+1F5F2
g:ultest_running_sign: 🗘 Clockwise Right and Left Semicircle Arrows U+1F5D8
g:ultest_not_run_sign: ? Question Mark U+003F

Oh TIL, thank you for flagging. I've gone with the multiplication sign instead of lightning as it feels more consistent. Also chose the heavy versions of the check and multiplication.


Github Recovery_CERTIFICATE_PASSWORD

Hello Rexiox80,
GitHub is a truly awesome service but to put any sensitive data like SSL certificate path, password with CN number make visible on GitHub create vulnerability for end to end communication, which might create man in the middle attack.
Please find the below link;
https://github.com/Rexios80/Health-Data-Server-Overlay.git
POC:
certificate_path: windows\fluttercertificate.pfx
110 | certificate_password: f>G@wtohG7]Y
111 | publisher: CN=3DC3FAF1-ABA5-4AAC-856A-275AF0D1C0B4
Regards,
Tushar Sawant
<EMAIL_ADDRESS>+91-9561345722

If you can figure out how to use environment variables to get that done in the pubspec and GitHub Actions be my guest

Also it’s not used for communication just signing. And the Microsoft store signs with a different certificate anyways I’m pretty sure.

Actually there's a way to run the msix generation command with parameters. I'll just get it done.

Generated a new certificate with a different password and used GitHub secrets to store them

That sounds great.
On Sun, 2 May, 2021, 11:01 pm Rexios80, @.***> wrote:

Generated a new certificate with a different password and used GitHub
secrets to store them
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Rexios80/Health-Data-Server-Overlay/issues/56#issuecomment-830843182,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARSR2UCKSJ24YPRJDKW2LXLTLWD5TANCNFSM437IQZCQ
.


feat(book): RollupConfig Type

Description
Outlines the RollupConfig type in op-alloy-genesis.

📚 $\text{Stack Overview}$
Pulls submitted in this stack:

#209 👈
#208
main

This comment was automatically generated by st.


register FormDataCollector with container to make it singleton

The issue is the form section of webprofiler is always empty. This is because one instance of FormDataCollector collects form information via form events, but when webprofiler is rendered, it gets a another newly instantiated FormDataCollector which is obviously empty.
My solution registers FormDataCollector as a service to $app and returns it. This way single instance of FormDataCollector collects form data then webprofiler gets that same instance, so it can show form information.

Tested and works. @fabpot can you please merge and tag new version?

Thank you @sarim.


feat: add device trigger and conditions to Steam integration

Proposed change

This PR implements device conditions and triggers for the Steam Integration. This allows you to setup automations when your friends changes their game. Additionally with the trigger you can filter the events down to only trigger when they change the game to be the same as the game you're playing.
Screenshot:

Test execution:

Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[x] New feature (which adds functionality to an existing integration)
[ ] Deprecation (breaking change to happen in the future)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:

Checklist

[x] The code change is tested and works locally.
[x] Local tests pass. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist
[x] I have followed the perfect PR recommendations
[x] The code has been formatted using Ruff (ruff format homeassistant tests)
[x] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly.
Updated and included derived files by running: python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt.
Updated by running python3 -m script.gen_requirements_all.
[ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

[ ] I have reviewed two other open pull requests in this repository.

Seems like a lot of the failing CI steps are from files we haven't touched.

Based on the quality gate, the issues came from: homeassistant/components/steam_online/device_condition.py
And, from the changed files history, you did touch the file.

Yea sorry, I meant the remaining CI checks
The quality gate complains about unused function parameters but as we explained on the presentation these functions have a fixed signature decided by home assistant so we can't remove that parameter. 1st positional argument has to be the hass object


How to retraining for 10ms audio

How to retraining this model for 10ms audio frame : ）

Hi,
you have to change self.blockLen and self.block_shift inside the DTLN_model constructor to your desired values or call the properties inside your training script before building the model. For 10ms block length set blockLen to 160 (samples). As block shift 5ms should work, so set it to 80 (samples). The quality is probably similar to the 32 ms model.

hello there,
I modified the block Len to 160, block shift to 80 and running the training, but the loss is nan...


Add Tracker backend

Codecov Report
Attention: Patch coverage is 0% with 18 lines in your changes are missing coverage. Please review.

Project coverage is 90.86%. Comparing base (22825cc) to head (625b0f3).

Files
Patch %
Lines

...ceTrackerExt/DifferentiationInterfaceTrackerExt.jl
0.00%
17 Missing :warning:

src/DifferentiationTest/pretty.jl
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #67      +/-   ##
==========================================
- Coverage   91.93%   90.86%   -1.08%
==========================================
  Files          43       44       +1
  Lines        1526     1544      +18
==========================================
  Hits         1403     1403
- Misses        123      141      +18

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


True Romance by Parov Stelar unsupported.

Check if issue with swaglyrics or whether song lyrics unavailable on Genius.

stripper -> Parov-Stelar-True-Romance
version -> 0.2.6

should be supported now


Extend range async/await benchmarks to cover various scenarios

We should expand benchmarking of async/async*/await code to cover more scenarios

running inside root zone vs custom error zone vs custom zone
running with many different return types of async functions (e.g. due to sdk/issues/48235)
running with few / many live variables across awaits

/cc @mraleph @alexmarkov

@mraleph Also suggested to add benchmark for awaiting a custom Future implementation such as SynchronousFuture from Flutter.


ComfyUI Manager can't update this repo

Hi, I just pulled an update from ComfyUI Manager and this is the only repo it can't upgrade.
I also used the "try update" button, but it gave me this error:

(I'm also worried about that error because there's my full name twice under those red lines... How did it get that!? 😟)

Hi Matteo, I don't know why but it keeps throwing me an error when updating with the manager:

I had an error yesterday with the commit, you got caught in the cross-fire while I was fixing it :smile:  . If you delete the node now and reinstall it, it won't give you more issues in the future

Ok, now seems fixed! Thanks again! 😄


Fix: Stop notification check on root certs

⚠⚠⚠ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma
Tick the checkbox if you understand [x]:

[x] I have read and understand the pull request rules.

Description
Fixes #3323
Store the fingerprints of the known root certificates that are bundled with node.js. When checking certificates for expiry notification, stop when a known root certificate is encountered.
Note that this does not account for extra certificates imported by using NODE_EXTRA_CA_CERTS.
Type of change

Bug fix (non-breaking change which fixes an issue)

Checklist

[x] My code follows the style guidelines of this project
[x] I ran ESLint and other linters for modified files
[x] I have performed a self-review of my own code and tested it
[x] I have commented my code, particularly in hard-to-understand areas
(including JSDoc for methods)
[x] My changes generate no new warnings
[ ] My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)

thank you very much sir !


"Dependency is not satisfiable: libgcrypt11" when installing deb package on ubuntu 15.10

I get this error trying to install N1:

On fresh install of ubuntu 15.10

I solved this by first installing libgcrypt11 from an older ubuntu version first:
32bit: https://launchpad.net/ubuntu/+archive/primary/+files/libgcrypt11_1.5.3-2ubuntu4.2_i386.deb
64bit: https://launchpad.net/ubuntu/+archive/primary/+files/libgcrypt11_1.5.3-2ubuntu4.2_amd64.deb
Ubuntu is transitioning from libgcrypt11 to libgcrypt20 and have set up a linked package during the transition. The nylas package doesn't seem to understand the link though (my understanding of deb packages is minimal). I don't know if this is an Ubuntu bug or a bug in the N1 deb package.

This fixed it for me too..

This seems to be a electron issue rather then N1.. Closing

This affects also Ubuntu 15.04.
May I ask you why you close this ticket? In my opinion N1 should not depend on obsolete version of libgcrypt. A real solution should be to compile N1 against libgcrypt newer version.

clobrano is right from my point of view
Ubuntu suggest to contact software maintainer rather then messing with security packages, but this is not only happening to N1, Spotify and others are having same issue...

Ill reopen this issue.. from my understanding this was something related to electron so it was affecting all electron applications.. But I can't remember where i saw it, neither can I find it.. I must have been dreaming!

Duplicate of #55

Closing this as a duplicate of https://github.com/nylas/N1/issues/55—we're working on a fix for this and should have it resolved soon, but you can track the conversation there.

I installed "libgcrypt11" and able to install brackets software... But is there a way to change the dependency of brackets to libgcrypt20....

I installed "libgcrypt11" and now able to install staruml software. Thanks

bharadwaj509 I installed "libgcrypt11" and was unable to install brackets. Did you ever find out if it is possible to change the dependency to libgcrypt20?

thanks so much


fix: fast scroll in back to top

What

fast scroll in the slide up screen when clicking back to top #1461

Screen recording
for small length
https://user-images.githubusercontent.com/75238158/202836597-0ecd2730-11d1-4586-9512-bc19a4621994.mp4
for big length
https://user-images.githubusercontent.com/75238158/202836722-44df2d79-86b4-40dd-a000-c655db3db972.mp4
Fixes bug(s)

Part of

#1461

As you wish. For the record this is not an important issue at all and we have many P0 P1 P2 issues that deserve more attention.

As you wish. For the record this is not an important issue at all and we have many P0 P1 P2 issues that deserve more attention.

For important issues I will work on 😁😄

Codecov Report

Merging #3344 (e15f5ae) into develop (a67a2c5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #3344   +/-   ##
========================================
  Coverage    10.49%   10.49%
========================================
  Files          254      254
  Lines        12362    12362
========================================
  Hits          1297     1297
  Misses       11065    11065

Impacted Files
Coverage Δ

...p/lib/pages/product/common/product_query_page.dart
0.45% <ø> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Thanks for this PR @prathamsoni11 🥳

Thanks for this PR @prathamsoni11 🥳

Your welcome @M123-dev 😁


Xcode 12.5: Using ‘class’ keyword for protocol inheritance is deprecated; use ‘AnyObject’ instead

Hi @daltoniam, Thanks for considering this fix.
Issue Link 🔗
https://docs.swift.org/swift-book/LanguageGuide/Protocols.html#ID281
Goals ⚽
Avoid having warning when you are building on Xcode 12.5.
Implementation Details 🚧
Replace all the class with AnyObject due to the deprecation.

https://github.com/apple/swift-evolution/blob/master/proposals/0156-subclass-existentials.md

@acmacalister any eta on this?

Bump. Builds with Carthage not possible until this is fixed.

@daltoniam do you have any update on this?

hey, @acmacalister Could you also help out on this?

I believe this issue also causes the following (fatal) dyld error which I am experiencing when trying to link Starscream with a binary framework on Xcode <12.5:
dyld: Symbol not found: __ZN5swift34swift50override_conformsToProtocolEPKNS_14TargetMetadataINS_9InProcessEEEPKNS_24TargetProtocolDescriptorIS1_EEPFPKNS_18TargetWitnessTableIS1_EES4_S8_E

It would be highly desirable to merge this ASAP...

Hi @fassko,
Could you take a look at this pull request? It seems that many people need this fix 🙏
Mentioning you because you handled the recent releases. Thank you.

Sorry for my absence, I'm not using Websockets that much myself.
@ikarishinjigao or @ken0nek maybe you want to take this project over?


Exclude unclaimed giftcards

Good hotfix. Would be great to have some SQL filtering on that in the future.


modify_script uses a variable declared outside of the function

This seems to work since the univmss_script variable is declared in the function containing this function, but we should really use the script parameter to be correct:
https://github.com/irods/irods_testing_environment/blob/a61cd7a6afc776c9fe82ecfce177ca85d5b6f631/irods_testing_environment/irods_config.py#L279-L283

that's weird.   it's always been this way?

It probably became this way when adding parallel-ism to the test suite. Like I said, it seems to work, but that's just coincidental here. Also, the run_tests.py script also seems to do this work, so it really doesn't matter that much in the end.


build: add wx and observer as extra applications

          Beam is a VM. Probably will have problems debugging this with system tools, think you will need beam tools.

One such tool is the erlang observer. https://blog.sequinstream.com/how-we-used-elixirs-observer-to-hunt-down-bottlenecks/
Having said that, it may be fiddly to get this working in a Docker container. Either the observer needs to have X access somehow (e.g. https://github.com/c0b/docker-elixir/issues/19#issuecomment-257637757), or you need to run a local beam that connects to the remote beam somehow (https://stackoverflow.com/questions/42164298/using-the-erlang-observer-app-with-a-remote-elixir-phoenix-server-inside-docker). Either way likely to be fiddly.
Also: It seems that our nix flake doesn't compile in the observer. I tried some things, but so far have been failures. Later: Oh, wait, this fixes it:
diff --git a/mix.exs b/mix.exs
index d159eefd..afa1c98a 100644
--- a/mix.exs
+++ b/mix.exs
@@ -27,7 +27,7 @@ defmodule TeslaMate.MixProject do
   def application do
     [
       mod: {TeslaMate.Application, []},
-      extra_applications: [:logger, :runtime_tools]
+      extra_applications: [:logger, :runtime_tools, :wx, :observer]
     ]
   end

(solution copied from https://stackoverflow.com/a/76760603)
Originally posted by @brianmay in https://github.com/teslamate-org/teslamate/issues/4307#issuecomment-2440184233

According to the report here: https://github.com/teslamate-org/teslamate/issues/4307#issuecomment-2440874346:
It is looking for libglu1-mesa which we haven't provided in the docker container.
How very odd. But probably due to the X UI stuff required by observer. I thought this wouldn't be required though unless you actually started the observer.
Need to test this, I imagine other libraries might be required also. Maybe we only want to add this if there is some debugging flag set, if it becomes too much overhead.

#4307 solved via #4319
If we wanna go debug route in the future this ca be taken as a first step with above mentioned additions.


Add verbose flag to build

The verbose flag hides all the extra output printed by the docker build
command, and also the contents of the dockerfile.
I tried to write unit tests for this but really build isn't easy to write tests for (the part that I modified, where we call out to docker). Not sure it's worth it, or if we do want to get tests for this, may require some more refactoring than I want to put into this PR.

💃 🔥

Should we also add this to the publish command?

Should we also add this to the publish command?

Yeah I want to, just started small with build for this PR. I ran into a snag with install/upgrade/uninstall because the duffle docker driver writes directory stdout and filed an issue.
Also I'm working on writing better integration tests right now for rebuild, that don't use bash but Go instead.


Unpin port_for

Thanks for this great package. I couldn't write docs without it.
The hard pin of port_for is problematic for downstreams, and it doesn't look like the API used has changed for 7 years. Let's have new port_for!

Coverage remained the same at 76.068% when pulling 849ce295cbe7dab9c6355ba0369254dfc43bb3c3 on bollwyvl:patch-1 into e0f40b6359ca00a48ca5ba903de1e25da27de453 on GaretJax:develop.

Will this be merged and a new release done please?

Coming from #81 -- I'm probably gonna drop this dependency.


Avoid importing self audits when pulling from an aggregated source

I now have aggregate running for Mozilla here: https://github.com/mozilla/supply-chain
However, when I add that as an import for Firefox, I get an enormous dump of all the audits we already have in Firefox. Ideally we would not have that duplication.
@mystor Is this problem just going to go away with the other work we have planned to be more minimal about what we import?

I just tried this on top of the changes in #399 and the problem does indeed go away. \o/

Yes, as you noted this will be going away with the changes in #399 as we will be only importing the audits which are used.


Removed isRequired from product description

Product description is not required via the PortfolioItem model https://github.com/ManageIQ/catalog-api/blob/master/app/models/portfolio_item.rb#L11 so removing the isRequired in the schema.
This depends on https://github.com/ManageIQ/catalog-api/pull/441
There is still more work to be done for the edits to fully work.
For any patch operation all readOnly params need to be stripped from the payload:
found unpermitted parameters: :id, :service_offering_source_ref, :service_offering_type, :portfolio_id

Product edits will work once https://github.com/ManageIQ/catalog-api/pull/441 is merged and the readOnly attributes are removed from the patch payload.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #281   +/-   ##
=======================================
  Coverage   83.48%   83.48%
=======================================
  Files         105      105
  Lines        1223     1223
  Branches      106      106
=======================================
  Hits         1021     1021
  Misses        184      184
  Partials       18       18

Impacted Files
Coverage Δ

src/forms/edit-portfolio-item-form.schema.js
100% <ø> (ø)
: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 6151947...8867469. Read the comment docs.

@syncrou isRequired is attribute that changes the component visuals. (that * in label). You also have to remove the validate attribute validate: [{ type: validatorTypes.REQUIRED }] from schema.

@Hyperkid123 please re review. I forgot about this one last week.


Fixes for latest Zig master

This PR updates the project for the latest changes in Zig master. The project is now buildable and runnable under Zig 0.14.0-dev.1573+4d81e8ee9. The extension code has also been updated.
I am able to run zig build codegen -Dgir-profile=gnome46 inside the Flatpak environment successfully with these changes.

Thanks for the PR! Sorry I haven't been keeping this project as up to date as it should be; I got sidetracked rewriting my XML parser, and now that that's mostly done, I'm hoping to come back to make more progress here.
Currently, I'm trying to primarily target Zig 0.13.0 until a new release is tagged, to make things a bit easier/more stable for users who might want to take advantage of other dependencies also following the latest tagged release (e.g. https://github.com/allyourcodebase as one recent example) and ecosystem tools such as the Zig SDK extension for Flatpaks. However, I would definitely like the generated bindings to support Zig master as well, which I think should be possible on top of your current changes by replacing direct usage of @typeInfo with a wrapper function that adapts the older naming conventions to match the new ones (and which could be removed when Zig 0.14.0 is out).
The Zig version targeted by the bindings generator itself is a little more flexible, since it's not going to be used by other projects. I'm inclined to go with using Zig master for it, given there are no other constraints.
In order to effectively support both 0.13.0 and master for the bindings, the test sub-project will need to be updated as well to support running under both versions; there's a bunch of "ABI tests" being generated as part of the translation process which were helpful earlier in development for spotting issues (though more ad-hoc than something like https://github.com/ziglang/zig/issues/20654) which can probably be made to work on both versions in a similar way to the bindings.
I'd also like to double-check the field names being changed and make sure none of them break any of the translated virtual method helpers (which reference fields in their implementations).
I know that's a lot; when I get a chance later this week I'm planning to come back to this and take another look, and build on top of this PR to address the points mentioned above (though you're certainly welcome to try making any of those changes yourself, if you'd like). Thanks again for getting this started!

Thanks for the detailed explanation! My changes were "just enough" to make a basic GTK application work with Zig master (as part of the Browser Jam), and I definitely didn't check things exhaustively. Please feel free to base your changes off of mine. Best of luck!


fmt: drop Scanf %X support for bytes and strings?

CL https://go-review.googlesource.com/#/c/15689/ made a trivial change to fmt.Scanf to make %X an alias for %x when applied to []byte and string values.
%x has always (even before Go 1) accepted either upper or lower case; now %X does too.
The only real effect here is that now people can write code using %X, which will only work with Go 1.6 or later, when they could instead use %x and work with Go 1 or later.
Should we keep the new %X support?
Leaving for @robpike to decide.
The original issue was #12940.

It seems like a regularization to accept %X, but there is always a cost to any addition of a feature. Taking that worry too far, we can't change anything ever.
The problem of versioning is being addressed by the community, and in that light I think it's fine for this minor cleanup to persist.


New Assembler API

Deprecated CalculateCraftingRecipe, GetCraftCooldown, and
GetInventory
Add Craft and GetRecipe

There is a mistake in the deprecation note of Assembler:CalculateCraftingRecipe

oop


how to resend a confirmation email ?

I was wondering, what if the user didn't receive the confirmation email, is there any way I can resend it ?
Something like "if you didn't receive the confirmation email please click here"
I guess there is a route for this ?
Thanks.

Would be nice if this was automatically (but only once) sent if a user gets the error message above.

@ACPK  Yes that would be nice, most website have something similar. Any update ?

any news on that one ? :)

will probably need to write this part myself :|

+1

+1 -- anybody have code for this? Seems like you have to override ConfirmationsController#new and call send_confirmation_instructions from the model concern.
Shouldn't be too hard but why reinvent the wheel?

Thanks to mkhatib providing a solution on the related ng-token-auth issue:
https://github.com/lynndylanhurley/ng-token-auth/issues/79#issuecomment-73386934

+1

+1

I just ran into the same issue, but where should I put the class extension?

@zachfeldman Would a PR containing the solution mentioned above (or similar) be considered? It seems like this is a pretty common use case.

@ethagnawl I would certainly be open to it!

@ethagnawl please submit a PR for this if you have time.


style(readme): fix typo

(Docs): Readme
orthographe ==> contin(u)o(u)s
ras

Thanks. I'll merge it if you just update the commit message to follow the contribution guideline.
https://github.com/ghpabs/angular2-seed-project/blob/master/.github/CONTRIBUTING.md#commit-message-format

I thought it would change the commit message. Reverted.

Lovely thanks @pas2al

The Git history got a bit mangled but oh well... :-)

Ya, i don't like that too. Next time i know better ;-)


[BUG] Theme is lost when using "Move to new window" option

Describe the Bug
When attempting to use the "Move to new window" option on a note, the note opens in a new window but loses the Everforest Enchanted theme. (Same as what is described HERE.)
Relevant Screenshots
https://github.com/FireIsGood/obsidian-everforest-enchanted/assets/42494843/f253ddc1-27d2-4127-9c64-811adf8bc4e5
Which editor are you using?

[ ] Legacy Editor
[X] New Editor

Which version of Obsidian are you using?

[X] Public Release (Desktop)
[ ] Public Release (Mobile)
[ ] Insider Release (Desktop)
[ ] Insider Release (Mobile)

Checklist

[X] I have updated to the latest version of the theme (Obsidian Settings → Appearance → Themes - Manage → Update).
[X] I made sure that the issue is related to this theme, by checking that the issue does not occur with other themes or the default theme.

This happens to be a very weird Obsidian bug!
For some reason, having any occurrence of the text ͼ1 will cause Obsidian to not load it specifically when moving tabs to new windows. Don't ask me why, I have no idea either...
This will be fixed in the next update along with some other things I've been cooking. Thanks for pointing it out!

Fixed in 3.6.2

Awesome! Thanks so much, and for all your work on this theme. Absolutely love it.


password() sometimes gives 1 more character than specified

This should be easy to track down and fix.

Fixed! The problem was in the randomNumberAsString() function on line 81:
// Broken code
randomNumberAsString = function() {
    // Uses Math.ceil() which means it'll never equal 0
    return String(Math.ceil(Math.random() * 10)); // Can return the number 10 which can cause the length to be higher than specified since it's a double digit number
  }

// Fixed code
randomNumberAsString = function() {
    // Uses Math.ceil() which means it'll never equal 0
    return String(Math.ceil(Math.random() * 9)); // Can't return double digit number
  }


Update README to include information on adding Background Functions to a site

It's not entirely clear how to set up Background Functions to a Gatsby site.
We should add a section to this project's README telling users how to do so
Related issue: https://github.com/netlify/netlify-plugin-gatsby/issues/436
Related documentation:

https://docs.netlify.com/functions/background-functions/
https://docs.netlify.com/functions/build-with-javascript/#background-function-format

Might as well add info for scheduled functions at the same time, as the process is the same


No route to host

After doin every steps perfectly, i come up with this error "No route to host". What is the solution for this??

Hey there. Usually that means that your system cannot fully reach or connect to the target system's services or IP address. This could be for a wide range of reasons. I'd start by trying to ping your target or running and nmap scan on port 445 to see if the host and the target service can even be reached.
Ultimately without more information I cannot determine if this is a tool issue or not. More importantly if you do have issues in the future please include screenshots of the errors your seeing and and the exact commands you're running. This could very well be a valid issue somehow but it is impossible to know based on your description.
Even running a "ping" or another tool could give you the exact an error and it is unhelpful in diagnosing the issue. I'll close this issue for now, and suggest you open a new one with more details if you still encounter a problem in the future.


Modelling Friend / Contact requests

Currently, we send contact request using Offer > Add > Profile.
In the activitystreams spec, it uses Offer > Relationship which I find a bit more intuitive. https://www.w3.org/TR/activitystreams-vocabulary/#connections
What are your thoughts about this?

Yes that would be more conformant with the specs.
But what predicate would we use ? I don't think the VCard ontology has a predicate to describe a simple "contact" relationship.