text:
Namespacing

Ticket: #869
Reviewer: @jarednova
Issue

Modernising Timber to use namespaces
Solution

A lot of code changes...
Impact

Is fully backwards compatible, I was thinking of using a trait, but as the list of classes that needed backwards compatibility is atomic, it was easier just to create a function.
Usage

Yes, too much to list here. See considerations.
Considerations

We need to update all the docs to represent this new change.
Testing

Tests need updating with this.
For now to test you can do the following composer require timber/timber:dev-dev-namespacing

Awesome! I'll start my review tonight

Good progress so far!

@connorjburton: Woohoo! everything finally passes! Before merging I want to test this in a local build which I should be able to do tomorrow

Changes Unknown when pulling 9414cdc3e27af2ce9a2bbfcbdd81e27f88316b0f on dev-namespacing into ** on master**.

Changes Unknown when pulling 9414cdc3e27af2ce9a2bbfcbdd81e27f88316b0f on dev-namespacing into ** on master**.

Oh my days! Made my week. Looks like you got the hard end of the stick though, sorry about that :) I'll have a test tonight aswell and will upgrade on a few sites I've done recently to make sure backwards compatibility works perfectly.

Changes Unknown when pulling b665a90241f894f6239ede775cc4574e7d7dd6fc on dev-namespacing into ** on master**.

Changes Unknown when pulling 11dc2b434464147729c0ff73e3554b1bb771a4f1 on dev-namespacing into ** on master**.

Changes Unknown when pulling 11dc2b434464147729c0ff73e3554b1bb771a4f1 on dev-namespacing into ** on master**.

Changes Unknown when pulling 11dc2b434464147729c0ff73e3554b1bb771a4f1 on dev-namespacing into ** on master**.

Changes Unknown when pulling 11dc2b434464147729c0ff73e3554b1bb771a4f1 on dev-namespacing into ** on master**.

Changes Unknown when pulling 41bad42ab63ee54de8d608832862c1c34a1b1d88 on dev-namespacing into ** on master**.

Changes Unknown when pulling f6661ac7244fe499de7612d8b448d4342ba672fb on dev-namespacing into ** on master**.

Changes Unknown when pulling f6661ac7244fe499de7612d8b448d4342ba672fb on dev-namespacing into ** on master**.

@connorjburton. I feel very confident about where this stands. I've put a few themes through the ringer and have yet to find any other issues. Once #955 is merged into this (I've assigned to you), I'm ready to merge this unless you've found any other issues on your end

Changes Unknown when pulling 99e1bf83e5fa451d5bd801d80b1a6e491820c0f6 on dev-namespacing into ** on master**.

Changes Unknown when pulling 482c99aa648eaa49d1f698a4484b89a3719dfcb4 on dev-namespacing into ** on master**.

Changes Unknown when pulling bbc95ad0d4f9e5a4cae00c25fb56c284870e9d01 on dev-namespacing into ** on master**.

Brilliant, I will review #955 tonight. I probably won't be available after tonight until early next week but i'll make sure #955 gets merged tonight.
Thank you for all the work!

I have also moved all other tasks on the 1.0.0 milestone to > 1.0.1 - as we are a bit behind it'd be good to get 1.0.0 released on packagist and wp.org once we merge.

@connorjburton — that plan works for me!

Changes Unknown when pulling 0e8a4bb74171eeae65e42a255ae90e301c46d6a2 on dev-namespacing into ** on master**.

Awesome, been merged! What is schedule for release on packagist and wp.org?

@connorjburton — I just pushed to Packagist. My plan was to wait a few days for any bugs to surface and then release on Tuesday May 3 to WordPress.org!

Aha, good idea. Thanks for the info

authors: connorjburton coveralls jarednova

repo: timber/timber


text:
0.2.7 includes a semver breaking change

0.2.7 includes commit https://github.com/time-rs/time/commit/a93d32efffba2f96512fe3758d56cb3ac037fe82, which is a (silent) semver breaking change. This is causing cookie-rs to fail to test. I also don't see this panicking behavior documented anywhere.
This is at least the third semver breaking change without a semver version bump this library has experienced since moving to 0.2, not to mention the failure to build in 0.2.8. This makes using the library a hazard. My advice is to consider asking for external review before releasing a new version. At present, I am considering a migration away from the library.

Without seeing the backtrace I can't be positive, but given the error I believe this actually has nothing to do with the overflow checks in Duration. Rather, it is a result of the clearly-stated validity guarantee that has been present since the initial 0.2.0 release:

Years between -100_000 and +100_000 inclusive are guaranteed to be representable. Any values outside this range may have incidental support that can change at any time without notice. If you need support outside this range, please file an issue with your use case.

With regard to 0.2.8 possibly not building, I presume you've seen #233. As is standard practice, I allowed the usage of any semver version back to the most recent major (0.1). I naïvely assumed this would work; this was obviously not the case. I have since verified all other direct dependencies work at both the minimum and current version in the semver range.

Are there any tools that would allow me to perform something along the lines of a crater run? If I could manually give something a list of libraries (starting with all reverse dependencies) and ensure that there are no regressions, that would be ideal.
External review is far from perfect — we don't need to look any further than the standard library where breaking changes have been introduced (without an FCP) on the unverified assumption that it wouldn't break anything. This is precisely what occurred with overflow checks on Duration arithmetic. I could not conceive of a single use case where one would actively want a Duration to overflow, given it is capable of storing lengths of time vastly longer than the age of the universe, and it does not appear that this is the cause of the CI failure in the cookie crate.

Without seeing the backtrace I can't be positive, but given the error I believe this actually has nothing to do with the overflow checks in Duration. Rather, it is a result of the clearly-stated validity guarantee that has been present since the initial 0.2.0 release:

The error is:

thread 'tests::format' panicked at 'year must be in the range -100000..=100000 (was 219250468)', <::std::macros::panic macros>:5:6

Looking at the test, it's obvious this comes from Duration. But, here are the relevant lines in the backtrace:

14: time:: date::Date::from_julian_day
at ./<::std::macros::panic macros>:5
15: <time:: date::Date as core::ops::arith::Addtime::duration::Duration>::add
at .cargo/registry/src/github.com-1ecc6299db9ec823/time-0.2.9/src/date.rs:1027
16: <time::primitive_date_time::PrimitiveDateTime as core::ops::arith::Addtime::duration::Duration>::add
at .cargo/registry/src/github.com-1ecc6299db9ec823/time-0.2.9/src/primitive_date_time.rs:549
17: <time::offset_date_time::OffsetDateTime as core::ops::arith::Addtime::duration::Duration>::add
at .cargo/registry/src/github.com-1ecc6299db9ec823/time-0.2.9/src/offset_date_time.rs:768

Are there any tools that would allow me to perform something along the lines of a crater run? If I could manually give something a list of libraries (starting with all reverse dependencies) and ensure that there are no regressions, that would be ideal.

Besides crater itself, not that I know of, but writing such a script yourself wouldn't be too difficult, for instance using cargo-edit-locally.

External review is far from perfect — we don't need to look any further than the standard library where breaking changes have been introduced (without an FCP) on the unverified assumption that it wouldn't break anything. This is precisely what occurred with overflow checks on Duration arithmetic.

Changes to the standard library don't make it to stable for ~12 weeks after they're introduced, allowing time for catching bugs. What's more, one can easily roll back to an older version. Changes to this library affect all of its dependencies immediately, and rolling back a transitive dependency can be difficult.

I could not conceive of a single use case where one would actively want a Duration to overflow, given it is capable of storing lengths of time vastly longer than the age of the universe, and it does not appear that this is the cause of the CI failure in the cookie crate.

Unfortunately it doesn't matter if it's reasonable behavior or not. What matters is what's specified. In this case, even now, it's not specified that year needs to be within a given range, neither in Duration nor OffsetDateTime nor PrimitiveDateTime. As it stands, it is impossible to know, aside from reading the code or running into this issue inadvertently, that a panic can happen under any Add operation. What's more, I'd argue that this is incredibly odd behavior for a time library: nothing should ever panic; something reasonable should always happen. For instance, if you must cap the year (why do you need to?), then simply bound the year or wrap around. But panicking is incredibly odd.

The error is:

thread 'tests::format' panicked at 'year must be in the range -100000..=100000 (was 219250468)', <::std::macros::panic macros>:5:6

Looking at the test, it's obvious this comes from Duration. But, here are the relevant lines in the backtrace:

14: time:: date::Date::from_julian_day
at ./<::std::macros::panic macros>:5
15: <time:: date::Date as core::ops::arith::Addtime::duration::Duration>::add
at .cargo/registry/src/github.com-1ecc6299db9ec823/time-0.2.9/src/date.rs:1027
16: <time::primitive_date_time::PrimitiveDateTime as core::ops::arith::Addtime::duration::Duration>::add
at .cargo/registry/src/github.com-1ecc6299db9ec823/time-0.2.9/src/primitive_date_time.rs:549
17: <time::offset_date_time::OffsetDateTime as core::ops::arith::Addtime::duration::Duration>::add
at .cargo/registry/src/github.com-1ecc6299db9ec823/time-0.2.9/src/offset_date_time.rs:768

As I suspected, it does originate from Date (see line 14). A Duration has no concept of a "year", let alone with a fixed epoch. What is happening is you're adding a Duration to a PrimitiveDateTime (and therefore Date), causing the year to go out of the valid range.

Besides crater itself, not that I know of, but writing such a script yourself wouldn't be too difficult, for instance using cargo-edit-locally.

Thanks, I wasn't aware of that crate. I'm definitely going to take a look into this, along with possible integration into CI. If I can get it to work with GitHub Actions, I should be able to trigger it via a variety of methods.

Changes to the standard library don't make it to stable for ~12 weeks after they're introduced, allowing time for catching bugs. What's more, one can easily roll back to an older version. Changes to this library affect all of its dependencies immediately, and rolling back a transitive dependency can be difficult.

Ironically, this still isn't perfect. There have been plenty of stable-to-stable regressions. But that's not the point here, so there's no purpose in continuing. If I can get an automated crater-like system for time, it should catch a variety of real-world use cases.

What's more, I'd argue that this is incredibly odd behavior for a time library: nothing should ever panic; something reasonable should always happen. For instance, if you must cap the year (why do you need to?), then simply bound the year or wrap around. But panicking is incredibly odd.

It is my intent to saturate Dates in 0.3. Times already wrap. UtcOffset methods will return a Result, as macros now provide the capability for values known at compile-time.
The reasoning for capping the year was to allow for the possibility of restructuring internally, namely bitpacked fields. I still haven't ruled it out, but I'd want to do some performance checks first.

source: gharchive/issue

authors: SergioBenitez jhpratt

repo: time-rs/time

license_type: permissive

license_source: bigquery


text:
Promscale integartion with timescaleDB ext with Apache 2.0 liecense

Integration of PostgreSQL deployed via zalando operator  with timescaleDB extension ( Apache 2.0 ) does not support with Promscale .Can you fix it ?

This has been in our backlog. We did a bit of discussion and thought to do some work on this on upcoming quarter due to tight plans right now.
However, would be awesome if you want to fix this and submit a PR for this. This will be an awesome help to the project as well. Let me know if you are interested, and I can try to help you with it.

Currently i have some time constraints  but will wait for your team to fix this .

#659 is a WIP PR for this issue.

@raviranjanelastisys this issue was fixed a few weeks ago and released with Promscale 0.5.1. Please reopen the ticket if you are still seeing it after upgrading Promscale.

repo: timescale/promscale

license_source: github-api


text:
xchange's poloniex example failure.

hello,I use vpn to run xchange's poloniex example:"PoloniexMarketDataDemo", then I receive a string,it is html layout,I put the string to a text,and open it with chrome browser,then I know the string's mean is:
"One More Step,Please complete the security check to proceed."
I use vpn is Shadowsocks,is xchange can not use under vpn?

It looks like you got cloudflare captcha page in response.
I think you should ask this question to poloniex. Normally, you should expect that if you use authentication on exchange, your requests should not be filtered.

repo: timmolter/XChange

license: mit


text:
Add visual effect for scene covers based on opacity value in user settings

Enhanced initial functionality for scene cover brightness for matching and/or missing scenes. It works for every website which uses img tag close to our check/cross mark symbol. Performance isn't an issue anymore and also works with observe: true quite well.
This technically covers and solves #34
Following features will come soon:

Replace opacity input fields with more user-friendly select menu (already implemented and used at #47)
CheckOptions.sceneCardSelector to define whole scene cards for each website
Remove scene cards on 0% capacity (only for realizable websites)
Injected switch for "Only missing scenes" at StashDB (configurable in settings) comparable to 'capacity at 0%'

Scenes page
Performer/Scenes
Studio page
Studio page/Performers
Tag/Scenes

I don't like actually removing content from the site. Visual effects on the scene covers seem fine, but I don't want to remove entries.

PR reworked and initial functionality tackled by #50.
Enhanced feature like removing scene card moved to #51.

source: gharchive/pull-request

license: MIT


text:
Badge variables

Our badges are broken. We use variables inside our badges, and gitlab-monitor shows a broken image. The generated url/image looks like this: https:///%%7Bproject_path%7D/pipelines
Seems like %{project_path} is not translated. Don't know wether this is a bug in gitlab or in gitlab-monitor.

Hi there!
The badges do work inside GitLab though, right?

Yes, like a charm ;-)

Should be fixed now. Docker image and hosted version should be up in a few minutes... :wink:

authors: temp timoschwarzer

repo: timoschwarzer/gitlab-monitor


text:
--wrap-length prepends the line with a bad string

isort version: 4.3.21
issue: using --wrap-length config adds the string import \ at the end of the line
Note: 4.3.21 has an issue with --wrap-length via CLI parameter, as reported in #1060, for this issue to work, i've hotfixed my local isort to fix #1060 by wrapping the statement causing error with int()
Test files:
# test.py
def a_very_long_function_name_that_exceeds_the_normal_pep8_line_length():
    pass

# test2.py
from .test import a_very_long_function_name_that_exceeds_the_normal_pep8_line_length

after running the following command isort -y test2.py --wrap-length=99 the output of test2.py will no be
# test2.py updated after isort
from .test import a_very_long_function_name_that_exceeds_the_normal_pep8_line_lengthimport \

notice that the string import \ has been added to the end of the line, whereas running isort normally isort -y test2.py will yield
from .test import \
    a_very_long_function_name_that_exceeds_the_normal_pep8_line_length_of_79

Thanks for reporting! I believe, this is an issue of validation and documentation, which has been improved in develop in preparation for isort 5.0.0 release. isort is an import only formatter. It is agnostic to any other line, such as the one presented in test.py above. Therefore, in general the line length should be specified with -l. If you want to set isort to wrap at a shorter length when seeing a longer line (say if it's going to wrap at all, wrap to 80 characters, but only wrap if it reaches a line over 100) that's where wrap_length comes in. See the original ticket that led to it's creation: https://github.com/timothycrosley/isort/issues/225. Therefore, I believe it only ever makes sense for wrap_length to be lower than line_length, and I've added validation and documentation toward that effect.
Thanks!
~Timothy

authors: ibaguio timothycrosley

repo: timothycrosley/isort


text:
Fix api.project_configuration overriding output_dir

This function in the api module was unwittingly overwriting output_dir args passed along from pyproject.toml.
Added a regression test.
Fixes #63

Codecov Report

Merging #68 (20c155c) into master (c00235a) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #68   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         8
  Lines          301       301
=========================================
  Hits           301       301

Impacted Files
Coverage Δ

portray/api.py
100.00% <ø> (ø)

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 c00235a...20c155c. Read the comment docs.

authors: codecov-io leblancfg

repo: timothycrosley/portray


text:
Uploaded images are uploaded to 'tmp' directory, not the directory specified by uploadDir

Description
When uploading images via an image component, uploaded images are uploaded to a 'tmp' (/content/tmp) directory instead of the directory specified by uploadDir (/content/images).
Steps to reproduce
I defined uploadDir in the page below:
import { useLocalMarkdownForm } from 'next-tinacms-markdown';
import matter from 'gray-matter';
import ReactMarkdown from 'react-markdown';
import { get } from 'lodash';
import { Layout, ProductTiles } from '../components';

export default function WholesalePage(props) {
  const formOptions = {
    label: 'Wholesale Page',
    fields: [
      {
        name: 'frontmatter.title',
        label: 'Title',
        component: 'text'
      },
      {
        name: 'markdownBody',
        label: 'Body',
        component: 'markdown'
      },
      {
        name: 'frontmatter.products',
        label: 'Products',
        component: 'group-list',
        itemProps: item => ({
          key: item.id,
          label: item.name
        }),
        defaultItem: () => ({
          name: 'New Product',
          price: 0,
          description: 'Description',
          images: []
        }),
        fields: [
          {
            name: 'name',
            label: 'Name',
            component: 'text'
          },
          {
            name: 'price',
            label: 'Price',
            component: 'number'
          },
          {
            name: 'description',
            label: 'Description',
            component: 'text'
          },
          {
            name: 'images',
            label: 'Images',
            component: 'group-list',
            fields: [
              {
                name: 'url',
                label: 'Image',
                component: 'image',
                parse: filename => `/content/images/${filename}`,
                previewSrc: (formValues, { input }) => get(formValues, input.name),
                uploadDir: () => '/content/images/' // DEFINED HERE
              }
            ]
          }
        ]
      }
    ]
  };

  const [data] = useLocalMarkdownForm(props.markdownFile, formOptions);

  return (
    <Layout title={data.frontmatter.title}>
      <ReactMarkdown>{data.markdownBody}</ReactMarkdown>
      <ProductTiles products={data.frontmatter.products} />
    </Layout>
  );
}

WholesalePage.getInitialProps = async () => {
  const markdownData = await import('../../content/pages/wholesale.md');
  const data = matter(markdownData.default);

  return {
    markdownFile: {
      fileRelativePath: 'pages/wholesale.md',
      frontmatter: data.data,
      markdownBody: data.content
    }
  };
};

Please note the use of get(formValues, input.name) which evaluates to the path of an image in the /content/images directory (e.g., /content/images/0wg4pd5roap31.jpg). I am relying on this value for the previewSrc value, and since the image was uploaded to /content/tmp, the path /content/images/0wg4pd5roap31.jpg is invalid.
Expected result
Images should be uploaded to the directory specified by uploadDir, not a 'tmp' directory.
Actual result
Images are uploaded to /content/tmp instead of /content/images.
Maybe this is by design? If so, the docs should mention this and walk us through why this is and how to work with it.
Environment
Tinacms Package Versions

├─┬ @tinacms/api-git@0.5.6
├── @tinacms/git-client@0.4.2
├─┬ next-tinacms-markdown@0.2.3
├─┬ tinacms@0.14.0
│ ├── @tinacms/core@0.7.1
│ ├─┬ @tinacms/fields@0.5.1
│ ├─┬ @tinacms/form-builder@0.2.15
│ ├─┬ @tinacms/forms@0.2.0
│ ├── @tinacms/icons@0.5.2
│ ├─┬ @tinacms/react-core@0.2.7
│ ├── @tinacms/styles@0.1.2

Tools

Tool
Version

browser
79.0.3945.130 (Official Build) (64-bit)

os
macOS Version 10.15.1 (Build 19B88)

node
12.14.1

npm
6.13.4

yarn
1.21.1

Nevermind, I figured it out.
I changed the "images" group-list field to this:
{
  name: 'images',
  label: 'Images',
  component: 'group-list',
  itemProps: () => ({ label: 'Image' }),
  fields: [
    {
      name: 'url',
      label: 'Image',
      component: 'image',
      parse: filename => `/images/${filename}`,
      previewSrc: (formValues, { input }) => get(formValues, input.name),
      uploadDir: () => 'images/'
    }
  ]
}

Then I set pathToContent in my server to "public" to use the Next.js "public" directory. Now images upload to public/static, and they are referenced there on the site as well.

repo: tinacms/tinacms


text:
Added vendor data endpoint. Changed formatting

Signed-off-by: Srikar Ganti srikarsganti@gmail.com
Description
Added vendor data endpoint to API. Added newlines after all HTTP GET requests.
Why is this needed
Adding to the v0 Hegel changes.
Fixes: #
How Has This Been Tested?
Not well tested. TODO.
How are existing users impacted? What migration steps/scripts do we need?
Feature + Formatting fixes.
Checklist:
I have:

[ ] updated the documentation and/or roadmap (if required)
[ ] added unit or e2e tests
[ ] provided instructions on how to upgrade

We'll write tests separately for this.

repo: tinkerbell/hegel


text:
fp16 conv2d numerical inaccuracy

This is a blocker for true fp16 usage in onnx.
This inaccuracy is also exacerbated when the output is used as input for other ops
for instance this conv->elu->conv->... at the start of openpilot (output of elu is used as input for the next conv)
# 0: op "Conv" input shapes [(1, 12, 128, 256), (32, 12, 3, 3), (32,)] opt {'dilations': (1, 1), 'group': 1, 'kernel_shape': (3, 3), 'pads': (1, 1, 1, 1), 'strides': (2, 2)}
# 1: op "Elu" input shapes [(1, 32, 64, 128)] opt {'alpha': 1.0}
# 2: op "Conv" input shapes [(1, 32, 64, 128), (32, 1, 3, 3), (32,)] opt {'dilations': (1, 1), 'group': 32, 'kernel_shape': (3, 3), 'pads': (1, 1, 1, 1), 'strides': (1, 1)}
# 3: op "Elu" input shapes [(1, 32, 64, 128)] opt {'alpha': 1.0}
# 4: op "Conv" input shapes [(1, 32, 64, 128), (16, 32, 1, 1), (16,)] opt {'dilations': (1, 1), 'group': 1, 'kernel_shape': (1, 1), 'pads': (0, 0, 0, 0), 'strides': (1, 1)}
# 5: op "Conv" input shapes [(1, 16, 64, 128), (16, 1, 3, 3), (16,)] opt {'dilations': (1, 1), 'group': 16, 'kernel_shape': (3, 3), 'pads': (1, 1, 1, 1), 'strides': (1, 1)}
# 6: op "Elu" input shapes [(1, 16, 64, 128)] opt {'alpha': 1.0}
# 7: op "Conv" input shapes [(1, 16, 64, 128), (16, 16, 1, 1), (16,)] opt {'dilations': (1, 1), 'group': 1, 'kernel_shape': (1, 1), 'pads': (0, 0, 0, 0), 'strides': (1, 1)}
...

caught this using a little verifier I wrote where I compare outputs to torch onnx for each op
for openpilot in particular, after the 7th conv op, rtol=2e-3, atol=2e-3 (rtol atol for external_model_benchmark.py) is already violated.
not too sure whats the right thing to do here.

it might also be affected by hand_coded_optimization, i think these are better put into their own test file with more focus on numerical issues

is torch on gpu different from torch on cpu

Yeah it's about a rtol=1e-3 atol=1e-3 difference (tested on colab)

i think it's less of an issue if tinygrad in float matches tinygrad in half with small tol

it's rtol=2e-2, atol=2e-2 big :(

it might also be affected by hand_coded_optimization

Yeah there's also a smaller rtol=2e-3 atol=2e-3 difference

inaccuracies will probably accumulate as sizes get bigger also.

authors: chenyuxyz geohotstan

repo: tinygrad/tinygrad


text:
Add module dependency resolver

Adding all modules (with the dependencies) in the modules list might be an issue, because the list might be unnecessarily big. Adding a resolver would be nicer.

Fixed in 0.0.8

repo: tinythings/microhop


text:
Support SHA256 and SHA512 for manifest checksums

Currently this is supported by solutions implemented using other languages: https://github.com/LibraryOfCongress/bagit-python#configuring-bagit

@jrgriffiniii I added support for this in version 0.4.2:
Allow for setting the hashing algorithm:
You can choose from md5, sha1, sha256, sha512.
From the command line you can supply the hashing algo as well:
bagit add -f LICENSE.txt -a 'sha256' test

repo: tipr/bagit


text:
Test on Ruby 2.5 and 2.6 as well

Currently the .travis.yml only tests on Ruby 2.4 and JRuby 9.2, it'd probably be good to run the test suite on Ruby 2.5 and 2.6 as well :)
https://github.com/titusfortner/webdrivers/blob/024b60a73ad7b1a004e8e2b8c35c31a2753757dc/.travis.yml#L1-L14

Hi @connorshea, I plan to adding them in my next PR including the performance improvements.

authors: connorshea kapoorlakshya

repo: titusfortner/webdrivers


text:
Pip-compatible packaging?

Really awesome work, not seen much else of this quality for visualizing hyperbolic spaces in Python!
Would be great to get this into a more pip-friendly installation (and maybe even get it on PyPI if you're open to that), had a hard time with the existing setuptools based approach but was able to repackage it to a pip-friendly format pretty easily, more than happy to help with a fork as well!

thanks, glad people are checking this out! I have been procrastinating putting this up on PyPI solely because I think the project might need a more descriptive name and I don't have one yet...
do you mind letting me know what you needed to change to get this to work with pip? I've only tested installation in pretty limited circumstances, but when I tried, pip worked as-is.


text:
Download sample data using python script

Summary
We can download sample data using python script instead of shell script.
From now, you can download sample data more simply in python code.

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@6a09028). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop      #47   +/-   ##
==========================================
  Coverage           ?   90.78%
==========================================
  Files              ?       16
  Lines              ?     1172
  Branches           ?        0
==========================================
  Hits               ?     1064
  Misses             ?      108
  Partials           ?        0

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 6a09028...71685ce. Read the comment docs.


text:
about use goalteryx to develop plugin tool 'GoDetour'

Dear Tom, hello!
I am glad to see your goalteryx on github. This is an unofficial innovation SDK. I only know a little about Python before, but as you said, .Net SDK is no longer supported. Python still has some difficult problems in efficiency and scene limitations. So I am very interested in your goalteryx. Learning the Go language from scratch is a major challenge for me. I wonder if I can see more complete codes of plug-ins developed based on goalteryx, so that I can learn from them for research. I have an idea about switching output anchor points like 'GoDetour'. If you can use this as an example and write a code case when you are free, I will be very grateful!

I have roughly described the solutions for plugins earlier. What is your idea?
Undoubtedly, this approach can also be implemented using Macro and Python SDK, but both methods have bugs. The former is unfriendly to tools like Summarize and may result in data loss, possibly involving the underlying Alteryx software, so it cannot be improved at present. The latter does not have caching and has certain issues in dealing with large amounts of data and efficiency, and relies on AMP mode.
So if it can be used goalteryx to implement this automatic Detour feature will effectively leverage its advantages. Unfortunately, as newbie, I am unable to do it myself. Therefore, if you are interested, implementing it will surpass Alteryx's existing capabilities.
Looking forward to your good news! thank you!

Hi Ayxer008,
The Go SDK can certainly be used to make tools like this. But tools with multiple input anchors will usually require caching, which is not something provided by the SDK. You would need to create your own caching solution. Caching is difficult to do correctly (with high performance), so I generally don't make custom tools that require it.
I think the tool you describe can be easily created as a macro. I have attached a macro to this post for you to try out.
In general, my preferred approach is to create custom tools as macros. You get all of the benefit and speed of Alteryx's native tools. I only reach for SDKs where there is a clear benefit to using them.
Tom
DetourMacro.zip

Dear Tom, hello!
Thank you very much for your quick reply!
1- I carefully checked the macro you made, but it did not achieve my expected effect. This may be related to my unclear expression, so please allow me to explain it again.
2- My idea is to implement a tool similar to intelligent Detour to achieve the effect of automatically switching workflow paths. The Detour tool that comes with Alteryx software can switch workflow paths in normal Workflow when it is not referenced by Macro, but it cannot be automated, so I came up with this idea.
3- If you use v2023.1+ version and turn on AMP mode by default, you can use the Control Container tool to achieve the above effect, but unfortunately, my usage scenario is based on the premise that there is no Control Container tool (such as low version) and AMP mode is disabled.
4- The native Detour tool has two Anchors, L and R. The default value is that L Anchor outputs data, and R Anchor does not output anything (your Macro uses the Filter tool, so although the field value is filtered, the field column header will still be output, which is different from the output effect of Detour, which makes the subsequent Detour End tool loses the basis for identification).
5- Although the Macro created by the native tool has the advantages of speed and compatibility, it is not as flexible as the SDK in controlling some interfaces, so I thought of using plug-ins to implement this idea.
6- As you said, the SDK does not provide a cache function, so can GoAlteryx be used to implement the control process of 1 Input Anchor according to the following process?
7- Thank you again for your help!

Dear Tom, hello !
If it is difficult for goalteryx to achieve the above effect, please take a look at this python code when you have time. It would be great if you can correct the errors and give the correct code. Thank you!
https://community.alteryx.com/t5/Alteryx-IO-Discussions/use-python-Engine-SDK-to-implements-2-inputs-and-2-outputs-for/td-p/1349322

repo: tlarsendataguy/goalteryx


text:
Fix typo in tensor_ir_opt_flow

Fix typo of loop order in fig
cc @junrushao1994

CC: @juda

Thanks @Hzfengsy @juda! It's merged!

repo: tlc-pack/web-data


text:
v2.0.0

Z! v1 focused on describing and validating schemas with an emphasis on validation. The public API for v1 was heavily influenced by packages such as Joi, Yup, and Zod from the JavaScript community.
Based on feedback from @yordis, v2 will focus on providing an API that first gives the community an efficient way of describing structs and allows type casting, validation, and other functionality to be layered on.
Minimum Example
defmodule Book do
  use Z.Struct

  schema do
    field :title
    field :author
    field :description
    field :price
    field :read_at
  end
end

The example above is the most basic form of defining a struct and is equivalent to
defmodule Book do
  defstruct [:title, :author, :description, :price, :read_at]
end

The base API will be able to describe structs with all of the built-in functionality provided by vanilla Elixir. This includes defining keys, default values, @enforce_keys, and typespec
Base API Example
defmodule Book do
  use Z.Struct

  schema do
    field :title, enforce: true, typespec: String.t
    field :author, default: "Unknown", enforce: true, typespec: String.t
    field :description, typespec: String.t
    field :price, default: 0.0
    field :read_at
  end
end

The above example is equivalent to
defmodule Book do
  @enforce_keys [:title, :author]
  defstruct [:title, :description, :read_at, author: "Unknown", price: 0.0]

  @type t :: %Book{
          title: String.t(),
          author: String.t(),
          description: String.t()
        }
end

In v1 field accepted a name, type, and rules. One thing that became obvious is that you may want to validate a struct using different rules depending on the use case. For this reason, we want to provide convenient helper functions for defining and composing your own validation functions.
Also, all rules can be categorized as a cast, mutation, or validation. Where cast is a rule that converts from one type to another, mutation is a rule that changes the value but doesn't change the type, and validation is a rule that makes an assertion about the value.
By bucketing each rule into one of these three categories, we can more granularly layer on our validation.

Please, keep this up, I think is awesome and filling a hole in the Elixir ecosystem. Currently I find it a bit of a pain to work with schemas, I find it quite more straightforward to use than Ecto embedded schemas.

authors: ivcosla tleef

repo: tleef/zbang


text:
Update index.html

fixed a small typo at line 235
don't know what happened at line 246 though..
Great work by the way 👍

Thanks @abrabah, could you make a PR against the master branch instead?
The website is getting automatically generated based on the things in /docs ;)
Here's the file you probably want to edit: https://github.com/tleunen/react-mdl/blob/master/docs/pages/components/textfield.md

authors: abrabah tleunen

repo: tleunen/react-mdl


text:
Custom types

subSchemas argument becomes options which may contain subSchemas and types.
types are custom types that accept Joi schemas / custom schemas.

That is so not bad.

authors: aredridel tlivings

repo: tlivings/enjoi


text:
MethodError: no method matching interpretation(::Val{TiffImages.PHOTOMETRIC_MINISWHITE}), Float32 support

xref: https://discourse.julialang.org/t/problem-in-reading-tiff-floats-file/106610/4
The primary problem is that interpretation(::Val{TiffImages.PHOTOMETRIC_MINISWHITE}) is not implemented.
ERROR: MethodError: no method matching interpretation(::Val{TiffImages.PHOTOMETRIC_MINISWHITE})

Closest candidates are:
  interpretation(::TiffImages.PhotometricInterpretations, ::Val{TiffImages.EXTRASAMPLE_UNSPECIFIED}, ::Val{4})
   @ TiffImages ~/.julia/packages/TiffImages/yETMK/src/layout.jl:63
  interpretation(::TiffImages.PhotometricInterpretations, ::TiffImages.ExtraSamples, ::Int64)
   @ TiffImages ~/.julia/packages/TiffImages/yETMK/src/layout.jl:45
  interpretation(::TiffImages.PhotometricInterpretations)
   @ TiffImages ~/.julia/packages/TiffImages/yETMK/src/layout.jl:38
  ...

Stacktrace:
  [1] interpretation(p::TiffImages.PhotometricInterpretations)
    @ TiffImages ~/.julia/packages/TiffImages/yETMK/src/layout.jl:38
  [2] interpretation(p::TiffImages.PhotometricInterpretations, extrasamples::TiffImages.ExtraSamples, samplesperpixel::Int64)
    @ TiffImages ~/.julia/packages/TiffImages/yETMK/src/layout.jl:46
  [3] interpretation(ifd::TiffImages.IFD{UInt32})
    @ TiffImages ~/.julia/packages/TiffImages/yETMK/src/layout.jl:29
  [4] getcache(ifd::TiffImages.IFD{UInt32})
    @ TiffImages ~/.julia/packages/TiffImages/yETMK/src/layout.jl:91
  [5] load(tf::TiffImages.TiffFile{UInt32, Stream{DataFormat{:TIFF}, IOStream, String}}, ifds::Vector{TiffImages.IFD{UInt32}}, ::Nothing; verbose::Bool)
    @ TiffImages ~/.julia/packages/TiffImages/yETMK/src/load.jl:71
  [6] load
    @ TiffImages ~/.julia/packages/TiffImages/yETMK/src/load.jl:69 [inlined]
  [7] load(tf::TiffImages.TiffFile{UInt32, Stream{DataFormat{:TIFF}, IOStream, String}}; verbose::Bool, mmap::Bool, lazyio::Bool)
    @ TiffImages ~/.julia/packages/TiffImages/yETMK/src/load.jl:36
  [8] load(tf::TiffImages.TiffFile{UInt32, Stream{DataFormat{:TIFF}, IOStream, String}})
    @ TiffImages ~/.julia/packages/TiffImages/yETMK/src/load.jl:18
  [9] load(io::IOStream; kwargs::@Kwargs{})
    @ TiffImages ~/.julia/packages/TiffImages/yETMK/src/load.jl:17
 [10] load
    @ TiffImages ~/.julia/packages/TiffImages/yETMK/src/load.jl:17 [inlined]
 [11] #13
    @ TiffImages ~/.julia/packages/TiffImages/yETMK/src/load.jl:13 [inlined]
 [12] open(::TiffImages.var"#13#14"{@Kwargs{}}, ::String, ::Vararg{String}; kwargs::@Kwargs{})
    @ Base ./io.jl:396
 [13] open
    @ Base ./io.jl:393 [inlined]
 [14] #load#12
    @ TiffImages ~/.julia/packages/TiffImages/yETMK/src/load.jl:12 [inlined]
 [15] load(filepath::String)
    @ TiffImages ~/.julia/packages/TiffImages/yETMK/src/load.jl:11
 [16] #invokelatest#2
    @ Base ./essentials.jl:950 [inlined]
 [17] invokelatest
    @ Base ./essentials.jl:947 [inlined]
 [18] #_#1
    @ LazyModules ~/.julia/packages/LazyModules/d9Be6/src/LazyModules.jl:29 [inlined]
 [19] (::LazyModules.LazyFunction)(args::String)
    @ LazyModules ~/.julia/packages/LazyModules/d9Be6/src/LazyModules.jl:27
 [20] load(f::File{DataFormat{:TIFF}, String}; canonicalize::Nothing, kwargs::@Kwargs{})
    @ ImageIO ~/.julia/packages/ImageIO/XthUV/src/ImageIO.jl:111
 [21] load(f::File{DataFormat{:TIFF}, String})
    @ ImageIO ~/.julia/packages/ImageIO/XthUV/src/ImageIO.jl:109
 [22] #invokelatest#2
    @ Base ./essentials.jl:950 [inlined]
 [23] invokelatest
    @ Base ./essentials.jl:947 [inlined]
 [24] action(::Symbol, ::Vector{Union{Base.PkgId, Module}}, ::Formatted; options::@Kwargs{})
    @ FileIO ~/.julia/packages/FileIO/BE7iZ/src/loadsave.jl:219
 [25] action
    @ FileIO ~/.julia/packages/FileIO/BE7iZ/src/loadsave.jl:196 [inlined]
 [26] action
    @ FileIO ~/.julia/packages/FileIO/BE7iZ/src/loadsave.jl:185 [inlined]
 [27] load(::String; options::@Kwargs{})
    @ FileIO ~/.julia/packages/FileIO/BE7iZ/src/loadsave.jl:113
 [28] load(::String)
    @ FileIO ~/.julia/packages/FileIO/BE7iZ/src/loadsave.jl:109
 [29] top-level scope
    @ REPL[13]:1
Stacktrace:
 [1] handle_error(e::MethodError, q::Base.PkgId, bt::Vector{Union{Ptr{Nothing}, Base.InterpreterIP}})
   @ FileIO ~/.julia/packages/FileIO/BE7iZ/src/error_handling.jl:61
 [2] handle_exceptions(exceptions::Vector{Tuple{Any, Union{Base.PkgId, Module}, Vector}}, action::String)
   @ FileIO ~/.julia/packages/FileIO/BE7iZ/src/error_handling.jl:56
 [3] action(::Symbol, ::Vector{Union{Base.PkgId, Module}}, ::Formatted; options::@Kwargs{})
   @ FileIO ~/.julia/packages/FileIO/BE7iZ/src/loadsave.jl:228
 [4] action
   @ FileIO ~/.julia/packages/FileIO/BE7iZ/src/loadsave.jl:196 [inlined]
 [5] action
   @ FileIO ~/.julia/packages/FileIO/BE7iZ/src/loadsave.jl:185 [inlined]
 [6] load(::String; options::@Kwargs{})
   @ FileIO ~/.julia/packages/FileIO/BE7iZ/src/loadsave.jl:113
 [7] load(::String)
   @ FileIO ~/.julia/packages/FileIO/BE7iZ/src/loadsave.jl:109
 [8] top-level scope
   @ REPL[13]:1

TIFFTAG_SAMPLEFORMAT value 3 corresponds to SAMPLEFORMAT_IEEEFP. That is IEEE floating point.
https://gitlab.com/libtiff/libtiff/-/blob/master/libtiff/tiff.h#L335
If TIFFTAG_BITSPERSAMPLE is 32, then the image should be interpreted as consisting of Float32 samples.
See the xref on Discourse for a TIF sample.

https://github.com/tlnagy/TiffImages.jl/blob/46131077adba3a7461288f1ebc67ceb89ea94ff4/src/utils.jl#L161 the encoding does exist in this package, so what went wrong?

I guess the actual problem here was
ERROR: MethodError: no method matching interpretation(::Val{TiffImages.PHOTOMETRIC_MINISWHITE})

I had never implemented PHOTOMETRIC_MINISWHITE as the Colors.jl ecosystem doesn't have a nice way to represent inverted grayscales and I decided that ignoring the inversion (which is what most libraries do) is in violation of Colors.jl's promise to represent the meaning of colors faithfully despite what the raw data might look like.

Presumably mappedarrays(complement, A) would solve that problem?

I think we might also need setindex! support as well.

authors: mkitti timholy tlnagy


text:
deprecation of genericLSTM

I have seen that in the last version genericLSTM has been "softly" deprecated. Could you please explain me the reason why this choice has been made?

I've run a lot of benchmarks that have shown that (1) peephole optimizations don't help (and usually hurt), and (2) any other choice of non-linearity other than the default one performs considerably worse.
I'll publish that as an Arxiv tech report soon.

Is the arxiv link of your tech report available now?

I got publication clearance, but it's not quite out yet. I'll try to push it in the next few days.

Thank you!  Have you ever try to push a GPU version of LSTM since the community seems to have more interests in the RNN field?

I'm planning on GPU support via Eigen;  however, that will still be a few months before the necessary dependencies are out.

@BestSonny, here it is:
Benchmarking of LSTM Networks
Thomas M. Breuel
http://arxiv.org/abs/1508.02774

Thank you！

@tmbdev , mshadow may be a strong alternative to Eigen. Both cxxnet and mxnet are built upon it.

Thanks. Looks like Eigen and mshadow have similar goals. Is there any performance data comparing the two?

@tmbdev , mshadow has very detailed tutorials and other documentations including multi-GPU support while Eigen documents almost nothing related to GPU on its official website.
More importantly, mshadow exploits the powerful NVIDIA cuDNN library. It's impossible for Eigen to catch up mshadow in performance on GPUs.

authors: BestSonny amitdo apbard futurely tmbdev

repo: tmbdev/clstm


text:
Suite name missing

I filed an issue in karma-tap-reporter because the suite name never appear in the output of the tool (https://github.com/fumiakiy/karma-tap-reporter/issues/11). However, it seems that the problem is in karma-tap, as the suite array is always empty. I'll have a look if I can find some time, but if someone know how to fix that, your comments/PR are welcome ;)

This repository is 'up for adoption': I no longer use or maintain this module, and will transfer it to any prospective maintainer.

Ok, I am not willing to maintain this library, sorry. I'm just trying to get my project done and it's harder than I thought.

@tmcw I'm considering adapting this repo because I want to use it for my company (unless karma-ava comes out in time, but unlikely).
I want to learn a bit more about it so that I know I can actually handle it afterwards.
Here is a question regarding suite:
https://github.com/tmcw-up-for-adoption/karma-tap/blob/master/src/adapter.js#L19
Where does this result object interface defined? I can't find it on TAP. I saw that you specify it (although it is empty) and karma-tap-reporter is using it (hence this issue).

this is solved now with pending PR´s:

https://github.com/fumiakiy/karma-tap-reporter/pull/12
https://github.com/tmcw-up-for-adoption/karma-tap/pull/15

Solved on current release 2.1.3

authors: bySabi sprat tmcw unional

repo: tmcw-up-for-adoption/karma-tap

license: ISC


text:
Init project failure

Started like this:
➜  rootDir  npm install -g create-graphql-server
/Users/me/.nvm/versions/node/v6.9.1/bin/create-graphql-server -> /Users/me/.nvm/versions/node/v6.9.1/lib/node_modules/create-graphql-server/dist/bin/create-graphql-server.js
/Users/me/.nvm/versions/node/v6.9.1/lib
└── create-graphql-server@0.5.1

Error:
➜  rootDir create-graphql-server init generator
env: babel-node: No such file or directory

i have the same problem...

Have you tried installing babel-cli globally?
npm install -g babel-cli

npm install -g babel-cli fixed this for me.
thanks @xavcz

@xavcz That resolves the issue...
I was trying sth similar : npm install babel-cli - forgot to add -g

This sounds like a bug though, I don't think you should have to do that.

Fixed in 0.5.3

authors: ChrisLusted jfabraxas parhelium tmeasday xavcz

repo: tmeasday/create-graphql-server


text:
🛑 Portal 1 is down

In eb77c01, Portal 1 (https://portal1.hcmus.edu.vn/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Portal 1 is back up in e493777 after 39 minutes.

repo: tmkhiem/hcmus-web-uptime


text:
Install instructions for jsdom 3 branch

For anyone else that needs it.

npm i jsdom@3 would probably be better since it's published. GitHub might be unstable.

Good point.

Merged as f62ba5ed4235c425709e84e4ccbd1f6fc2f93e0d, thanks!

authors: Sebmaster domenic mikemaccana

repo: tmpvar/jsdom


text:
No notifications if there is no auth data

The phone won't create a notification if it receives a message but there is no auth data.

:+1:

authors: Revenaunt bradmontgomery

repo: tndatacommons/android-app


text:
logging failure: check-ex-spec

(From Thomas from Slack) I found a sample program that causes the logging to get out of sync:
#lang forge/check-ex-spec "forge2/spanning_tree" "thomas_del_vecchio@brown.edu"
test expect {
    alwaysSat : {} is sat
}

Output:
#<void>
download-file link: https://raw.githubusercontent.com/tdelv/lfs-2021-check-ex-spec/master/forge2/spanning_tree/summary-forge2-spanning_tree.json
download-file link: https://raw.githubusercontent.com/tdelv/lfs-2021-check-ex-spec/master/forge2/spanning_tree/wheats-0_rkt.zo
download-file link: https://raw.githubusercontent.com/tdelv/lfs-2021-check-ex-spec/master/forge2/spanning_tree/wheats-0_rkt.dep
download-file link: https://raw.githubusercontent.com/tdelv/lfs-2021-check-ex-spec/master/forge2/spanning_tree/chaffs-0_rkt.zo
download-file link: https://raw.githubusercontent.com/tdelv/lfs-2021-check-ex-spec/master/forge2/spanning_tree/chaffs-0_rkt.dep
download-file link: https://raw.githubusercontent.com/tdelv/lfs-2021-check-ex-spec/master/forge2/spanning_tree/chaffs-1_rkt.zo
download-file link: https://raw.githubusercontent.com/tdelv/lfs-2021-check-ex-spec/master/forge2/spanning_tree/chaffs-1_rkt.dep
download-file link: https://raw.githubusercontent.com/tdelv/lfs-2021-check-ex-spec/master/forge2/spanning_tree/chaffs-2_rkt.zo
download-file link: https://raw.githubusercontent.com/tdelv/lfs-2021-check-ex-spec/master/forge2/spanning_tree/chaffs-2_rkt.dep
download-file link: https://raw.githubusercontent.com/tdelv/lfs-2021-check-ex-spec/master/forge2/spanning_tree/chaffs-3_rkt.zo
download-file link: https://raw.githubusercontent.com/tdelv/lfs-2021-check-ex-spec/master/forge2/spanning_tree/chaffs-3_rkt.dep
download-file link: https://raw.githubusercontent.com/tdelv/lfs-2021-check-ex-spec/master/forge2/spanning_tree/chaffs-4_rkt.zo
download-file link: https://raw.githubusercontent.com/tdelv/lfs-2021-check-ex-spec/master/forge2/spanning_tree/chaffs-4_rkt.dep
LOGGING: Found 1 logs; 1 valid.
(http-response 201 '#hash(("Content-Length" . "25") ("Server" . "Google Frontend") ("X-Cloud-Trace-Context" . "6e215a93deef0b1249fac77bed6a0a4f") ("Alt-Svc" . "h3-29=\":443\"; ma=2592000,h3-T051=\":443\"; ma=2592000,h3-Q050=\":443\"; ma=2592000,h3-Q046=\":443\"; ma=2592000,h3-Q043=\":443\"; ma=2592000,quic=\":443\"; ma=2592000; v=\"46,43\"") ("Function-Execution-Id" . "0lar4ewdzs3a") ("Date" . "Sat, 06 Feb 2021 01:32:19 GMT")) "Successfully logged data.")
#t
#vars: (size-variables 337); #primary: (size-primary 52); #clauses: (size-clauses 497)
Transl (ms): (time-translation 59); Solving (ms): (time-solving 3)
#<void>
#vars: (size-variables 337); #primary: (size-primary 52); #clauses: (size-clauses 497)
Transl (ms): (time-translation 46); Solving (ms): (time-solving 4)
#<void>
#vars: (size-variables 337); #primary: (size-primary 52); #clauses: (size-clauses 497)
Transl (ms): (time-translation 47); Solving (ms): (time-solving 3)
#<void>
#vars: (size-variables 337); #primary: (size-primary 52); #clauses: (size-clauses 497)
Transl (ms): (time-translation 47); Solving (ms): (time-solving 3)
#<void>
#vars: (size-variables 337); #primary: (size-primary 52); #clauses: (size-clauses 497)
Transl (ms): (time-translation 47); Solving (ms): (time-solving 3)
#<void>
#vars: (size-variables 337); #primary: (size-primary 52); #clauses: (size-clauses 497)
Transl (ms): (time-translation 46); Solving (ms): (time-solving 3)
Missed chaff 0.
Missed chaff 1.
Missed chaff 2.
Missed chaff 3.
Missed chaff 4.
LOGGING: Found 1 logs; 1 valid.
(http-response 201 '#hash(("Content-Length" . "52") ("Server" . "Google Frontend") ("X-Cloud-Trace-Context" . "d0b5d4b80619a4a1aef063971ab24553") ("Alt-Svc" . "h3-29=\":443\"; ma=2592000,h3-T051=\":443\"; ma=2592000,h3-Q050=\":443\"; ma=2592000,h3-Q046=\":443\"; ma=2592000,h3-Q043=\":443\"; ma=2592000,quic=\":443\"; ma=2592000; v=\"46,43\"") ("Function-Execution-Id" . "fbl29ltni103") ("Date" . "Sat, 06 Feb 2021 01:32:22 GMT")) "There was an error, but logs were saved to database.")
#t

The output suggests that Racket is not waiting for a response from the server, and is instead continuing with it's execution (I say this because the 1 logged file in the first log print is an execution log, which came from the current execution, and all of the download process plus execution logging happens after the flush log.)

So far it looks like forge/logging/logging.rkt waits in the right places
I wonder if the not-waiting only happens in DrRacket, and if the interactions have anything to do with it.

we're not using check-ex-spec anymore

repo: tnelson/Forge


text:
Appstudio update test-component-pac-hbxu

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-hbxu-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
17 seconds
clone-repository

✅ Succeeded
37 seconds
build-container

✅ Succeeded
24 seconds
inspect-image

✅ Succeeded
20 seconds
deprecated-base-image-check

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
14 seconds
clair-scan

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
13 seconds
label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
6 seconds
show-summary


text:
Question: Support for SSRS 2017

Hi
Does this support SSRS 2017? My understanding is that SSRS 2017 deprecates the WSDL service in favour of a REST API.
Will this extension still deploy ok?
Thanks

Is there still a WSDL endpoint available on your 2017 installation? If so, you could give it a try.

Yes, it looks like there is one. I thought it was being deprecated in favour of the REST API but it is still there. Thanks!

authors: Swellenator ygeelen-tb


text:
Change integer literals to floats for OpenGL ES compatibility

Change integer literals into floats so it's compatible with OpenGL ES which doesn't support implicit type conversions.

Nice, thanks!

authors: not-surt tobspr

repo: tobspr/GLSL-Color-Spaces


text:
🛑 Nube Luxis is down

In 757f224, Nube Luxis (https://ls.luxis.com.ar/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nube Luxis is back up in c2c9c30 after 11 minutes.

repo: tochimoreno/upptime


text:
Move libtock2 to the root package and rename it to libtock.

Now that the Tock 1.0 crates have been removed (#372), we can give libtock2 its intended name: libtock. This also moves the crate to the root of the repository, which will make it easier to navigate for newcomers.
I alphabetized libtock's dependencies in Cargo.toml during the move.

bors r+

repo: tock/libtock-rs


text:
Loss of remaining ETH

Describe the bug
If more Ether is sent than the '_amounts' set in the sendETH function, the transaction is executed, and the remaining Ether is locked in the contract.
Configuration

Severity: HIGH
Severity Classification

Impact
Loss of transferred funds.
If the amount of Ether sent to the contract is more than the amount you intended to send, the remaining Ether will be locked in the contract and cannot be retrieved.
Recommendation
A transaction can be only executed when the amount of Ether sent to the contract is equal to the sum of the amount to be transferred.
https://github.com/tokamak-network/multisend_bayram/blob/b9ff5f93fa2de61a80e87908e899d3ab356c3212/contracts/MultiSender.sol#L35C7-L36C61
require(msg.value >= totalAmount, "Not enough ETH");

change
require(msg.value == totalAmount, "Unequal transfer amount");

**Exploit Scenario **
Demo

@Zena-park Thanks for the clear explanation. I will create a new PR to fix this issue.


text:
Example i18n refactor

Please do code review; Ask questions if there is something weird / doesn't make sense to you.
Squash commits as you want.

I use macros where:

There is missing abstraction - e.g. this macro in drop_zone example.
It helps with readability a lot - e.g. macro t in this example.
It's hard/impossible to encode everything by proper Rust types - e.g. Seed element macros like div!
It can hide boilerplate and variable number or parameters are required - e.g. Seed's log! - it formats input parameters and calls console.log under the hood through web_sys

I've written first macros in the Seed core and I was pretty happy about it once I had idea how they work :D

repo: tokcum/seed


text:
[整理改修]モニタリング項目

「モニタリング項目」を改修します。
近日リリース予定です。
改修内容

お知らせを削除
入院患者数の「確保病床」を削除
重症患者数の「確保病床」を削除
注釈「(5)の確保病床数には、(6)の確保病床数を含む」を削除

使用データ
現在、数値を data/monitoring_items.json から取得しているところ、それを切り離し、各モニタリング項目のjsonから取得するようにします。
実装イメージ

こちらもやります

@kaizumaki
更新日時はどのjsonからとればよいでしょうか？

@Murayu0225 あ、たしかに！それ確認しておきますね！
とりあえず、 data/monitoring_items.json のままで実装してもらえると助かります 🙏

わかりました！


text:
Dev-V2 and Demo Strategicobjective API Error

ValueError at /api/strategicobjective/
Cannot query "TolaData": Must be "Country" instance.

Related to TolaDataV2/#47

authors: crajapax jefmoura

repo: toladata/TolaActivity


text:
建议使用$withBase()处理一下绝对路径

当config.js文件中的base设置为非/值时，且themeConfig.cover和markdown文件中的$frontmatter.image的值是绝对路径，则编译后会图片路径会出错。
建议使用$withBase()处理一下。
参考文档

关于这个 欢迎 pr

这个我在想会不会通过 img-lazy 处理会更好一些，同时处理主题与mark down的图片。我周末测试一下

done

authors: mishengqiang tolking

repo: tolking/vuepress-theme-ououe


text:
package/wikipedia

v0.1.0-1 of remarkable-wikipedia for toltec

I suggest someone test on rM2 since https://github.com/ddvk/remarkable2-framebuffer/issues/17 has been a long-standing issue. my understanding is dps fixed that in https://github.com/dps/remarkable-wikipedia/commit/ad039ff801bd2d20919ec6131f934cc2464432e8 a few days ago, but it should still be verified by someone with an rM2.

I can probably give it a shot tonight.

@dps did mention he was testing on a rM2, but having a second test would be fine. I was waiting to merge based on if @dps wanted to add an icon or not.

Edit: Even if links turn out to be broken, that's no reason to keep the package out of testing.

https://github.com/dps/remarkable-wikipedia/issues/12 Known issue

Closing in favor of #311

authors: Eeems danshick dps raisjn

repo: toltec-dev/toltec


text:
Update: Model rendering on client but not on server

Update:
Model won't load on server but when I take the original model it works. Also, it won't load under all conditions. I tried everything and I don't really want to redo it from the beginning. The update didn't do anything.
My model on my view :

Me on my friend view :

Original model :

Originally posted by @xArkailzx in https://github.com/tom5454/CustomPlayerModels/issues/170#issuecomment-1030827401

Check your gist, I checked your skin model and it gives a missing gist error.
Also ask your friend to open the Gesture gui [G]/Social Settings and click on your name, it may give an error message.


text:
Problem with TwitchWebSocket while trying to run MarkovChainBot.py

Hello! I'm a long time user of your program and so far it has been working flawlessly! But recently i formatted my SSD and while trying to set up the bot again i installed Python, Git and ran the requirement.txt command with no problems, but as soon as i tried to run the file MarkovChainBot.py it gave me this error:
Could not find platform independent libraries <prefix>
Traceback (most recent call last):
  File "C:\Users\Administrator\Downloads\TwitchMarkovChain-2.4\TwitchMarkovChain-2.4\MarkovChainBot.py", line 4, in <module>
    from TwitchWebsocket import Message, TwitchWebsocket
  File "C:\Users\Administrator\Downloads\TwitchMarkovChain-2.4\TwitchMarkovChain-2.4\TwitchWebsocket.py", line 8, in <module>
    from TwitchWebsocket.Message import Message
ModuleNotFoundError: No module named 'TwitchWebsocket.Message'; 'TwitchWebsocket' is not a package

I tried to download the TwitchWebSocket myself and copy the message and twitchwebsocket files into the folder but to no avail, rerunning the requirements command just gave back that the requirement was already satisfied, so i'm not sure what's going on or how to fix, any help is highly appreciated!

Hello!
According to your logs, you have a file called TwitchWebsocket.py. This is probably from copying the files locally. When it then tries to do
from TwitchWebsocket.Message import Message

then it'll see TwitchWebsocket as the current file, and there's no Message defined in the current file. Perhaps you could get around this by copying the TwitchWebsocket folder, i.e. this full folder.
However, normally it should work with just pip install TwitchWebsocket, but then make sure there's no local file called TwitchWebsocket.py, or that one will have priority. I think you probably tried that already based on your message. If you run pip show TwitchWebsocket, does it then show a package?
A relatively common error with that is that the pip is from a different python than the python that you're running the program with. You can get around this by doing python -m pip show TwitchWebsocket and python -m pip install TwitchWebsocket. Then you know for sure that the pip and python "match".
Hopefully this helps you in the right direction already, but please let me know if you still can't get it to work, and I'll try to help with some more details.

Tom Aarsen

I'm glad that you got it working, despite all that you had to go through to get it to work again!
As for the anomaly, I'm aware of it. Twitch removed most (or all?) of the "slash commands" like /mods. However, it shouldn't affect you - I think it was only used to allow moderators to update the cooldown and disable/enable the bot on the fly from the chat.

I'll close this now :)

authors: Ursometamorfo tomaarsen

repo: tomaarsen/TwitchMarkovChain


text:
Mapbox not working with json

I made my own map at mapbox studio and download it. But when I follow  example 40, there's an error saying wrong formation. When I opened mapbox.geography-class.json, I could check that the file is very different from the json that I downloaded from mapbox website. So, how can I convert my json for the one that is working or there's another way to make it work?

I found the answer:

In the mapbox studio go to Styles;
On your map menu go to Share, develope & use;
Go to Develop with this style and choose Leaflet;
Copy the text and paste it:

                        name: 'MapBox Night',
                        active: false,
                        source: {
                            type: 'XYZ',
                            url: 'https://api.mapbox.com/styles/v1/tatianass/cj28xs19900002rpatmcj4i7g/tiles/256/{z}/{x}/{y}?access_token=<your key>'
                        }
                    }


text:
SearchBox dropdown not showing up.

I just follow all the instruction stated in the SearchBox example, yeah it works fine but the dropdown didn't show up.
And I can't figure out where did I go wrong.

I have also noticed the autocomplete is not working all of the sudden. Has Google API changed?

authors: dlape lipenco

repo: tomchentw/react-google-maps


text:
Feature/add ajax showtime and banned word list

Kleine toevoeging naar aanleiding van dit weekend.
Misschien is het het overwegen waard om momenteel de like requirement even uit te schakelen? Zo krijg je hopelijk wat meer content tijdens de wedstrijden van users, en kunnen we elkaar ook wat makkelijker vinden? Misschien even deze week aankijken en dan kun je het altijd weer opschalen.
Ik had ook een idee voor de hitWords, denk dat het opzich makkelijker bijhouden is als er wat meer orde wordt aangebracht? Specifieke lijsten voor bijvoorbeeld spelers / staff / media, zo is het makkelijker bij te houden en hoef je niet door een array van 300 woorden te gaan zoeken naar een specieke speler bijvoorbeeld? Kunnen we in de toekomst ook eventueel nog bepaalde waardes aan verschillende lijsten hangen (Spelers 1.0, jeugd 0.8 bijvoorbeeld).

Nogmaals thanks voor je meedenken! In reactie op je punten:

Ik heb de like requirement eerder al uitgezet, maar dan krijg je echt veel troep. Ik kan hem wel even op 2 likes zetten om dat aan te kijken, maar ik zet hem niet uit. Kwaliteit over kwantiteit ;)
Het opsplitsen van de hitWords kan zeker, maar met de huidige lijst misschien een beetje een premature optimization. Problemen tackelen als ze er zijn is meestal mijn aanpak.


text:
Supporting other editors besides vscode ?

This is really not a bug report nor a question or possible feature request.
Many other editors besides vscode also support language server protocols (köhvimköh) so i was wondering if  this project (without the client) is cabable of also interacting with any other editors?  Has it been tried ? If it not possible, any estimates about how much work it would be?

Yes, this project uses the Language Server Protocol and is implemented with VSCode Language Server. It consists of a client and server, and the server is completely standalone Node.js server. Is is possible to take just the server and with your own client integrate that to another editor. I have not tried it tho, and it I guess it depends how much work that is. For example does the other editor support the language server protocol out of the box, is there a ready made client for you editor you can use to integrate it with the server, how hard is it to make plugins for the other editor etc.

Client side things are not really concern for me as there is generic plugin for vim that implements the protocol.
I guess my real question is: how “stand-alone” this implementation is in regards to dependency towards vscode ?

The server has no dependency to vscode. The only thing you need to run it is Nodejs.

@tomi
Can you give a hint how to start the Server as "stand Alone" with nodeJS?
i want to give it a try.
We in the board of Robot Framework Foundation want to develop a Language Server for "all" Editors in the future. And you did already quite a good job!
Can you help me a bit with this issue?
Tanks.

Hi @Snooz82
I made couple small changes and now with these steps you should be able to start the language server:
cd server
npm install
npm run build
node out/server.js

This starts the server using stdin and stdout for the transport. Other transports can be used by giving params --node-ipc or --socker={number}. Hopefully this helps you.
My original plan has always been to publish the parser as an NPM package, but I haven't done it yet. It would be possible to publish also the language server as an NPM package, so it could be easily installed with NPM.

i know this is not issue really about vscode-rf-language-server but id like to make comment.. Imho, if the langserv requires different runtime as rf itself, there will be issue about adopting it for general use.

Hi Jani,
I know that using a NodeJS Language Server is not a solution. We need a Python Solution.
But i want to give it a try to see if this could be a workaround for the meantime.
The VSCode integration of Tomi is imho (except the RED for Eclipse) one of the best plugins for editors.
An i like Pycharm but the Robot integration is odd and outdated.
I want to see how it feels and if this is the way to go for the future.
As i remembered you volunteered as a Developer for the Python Language Server, right? 😉

Thanks Tomi!

@tomi are you on rf slack ? If yes, could you join to #lsp channel?

authors: Snooz82 rasjani tomi

repo: tomi/vscode-rf-language-server


text:
Alarmas con 1 hora de retraso

Hola, tengo un Blackshark 3 con S.O. joyui 11(basado en miui 11).
Cuando pongo una alarma en la aplicación nativa de reloj, en el widget siempre me sale con 1 hora de retraso. Es decir si está puesta a las 9:00am, en el widget sale alarma a las 8:00.  Ya me he acostumbrado, pero me gustaría que saliese la hora correcta. He probado de todo. El móvil está con la región correcta y la hora el móvil la muestra correctamente. Adjunto capturas. Gracias.

#246

authors: aritzvinagre tommasoberlose

repo: tommasoberlose/another-widget


text:
Use new

Why are you doing this?
https://github.com/tomo1026j/SampleWeb3/blob/5bd9a32c7ca1d915c80417f7841bcde468626f40/src/index.ts#L14-L15
I would say it should rather be
const web3 = new Web3('http://localhost:8485')

Oh! Thanks, it's working!
Appreciate it!

Did this fix your initial issue? Glad to be able to help.

Your code does not work at all. Here you copied the wrong code from my code above
https://github.com/tomo1026j/SampleWeb3/blob/c750d70798b67f164683e8854a187932b64d674c/src/index.ts#L19
It needs to be 8545.
And here you are basically throwing a function into the res.send function
https://github.com/tomo1026j/SampleWeb3/blob/c750d70798b67f164683e8854a187932b64d674c/src/index.ts#L22
Again: You are sending a function back, not the result of a call to that function. Even if you would call that function you would have to wait for the result before you could give it to res.send because it is an async function that returns a promise.


text:
Swagger document for Epochs APIs

Should update swagger docs, then third-party can be easy to read the data

https://github.com/tomochain/tomoscan/commit/fd54f97f7ba2a268a51a88ca2aafafc6c589ea5e

repo: tomochain/tomoscan


text:
Add firewall support

I added firewall support as noted in #38, but mostly ignored tests

It would be cool if you can add your change  in CHANGELOG.md. You can either do it manually or use the proper tool https://github.com/MarkusFreitag/changelogger (I'll add some documentation about the CHANGELOG.md file in a separate MR).

👍

repo: tomsiewert/hetznercloud-java


text:
Available communication methods

I would like to make language server for Pascal but I'm not sure which methods LSP uses for communication with the server. I think the options are named pipes and sockets, is that correct? If sockets are used is there a default port to listen on and if named pipes a specific name to be used?
I looked over the spec at https://microsoft.github.io/language-server-protocol/ but they just say the data format is JSON-RPC but nothing as to how the tools communicate (I guess that application specific details).

Named pipes (stdout and stderr) are the most common.
Some servers (also) support TCP, this package currently only allows users to hardcode the port as an argument to the server (there is no default)
In the future this package will select the port automatically and pass it to the server as an argument - this is what the LSP spec suggests

Thanks, I see in the preference there is a "tcp_port" setting.  If I use sockets can I run the server from the terminal so I debug input from LSP? I think LSP is meant to spawn the process itself but using sockets means this isn't strictly necessary.
I've never used named pipes before but I think you mean that if I simply write to stdout then LSP will parse the output? That sounds easiest for sure.

Correct, tcp mode makes it easy to run from a debugger.
Some challenge with named pipes exists - for example in PHP on Windows stdio communication blocks the process/threads - only TCP mode works there. But most other languages have no such issues.

Then do we even need the "command" setting? I'm trying my first tests by running the server on 127.0.0.1 and listening on port 6050 but I don't get any data back from LSP when I enable it in the project.
Does that setting look correct? I'm thinking I can omit "command" because the server is already running and so LSP shouldn't need to spawn the process itself. Looking at the ST console I don't get any feedback either (I was expected LSP errors to appear at least)
"clients": {
"fpc-language-server":
{
"command": ["/Users/ryanjoseph/Desktop/symbols/fpcls"],
"scopes": ["source.pascal"],
"syntaxes": ["Packages/FPC/FPC.sublime-syntax"],
"languageId": "pascal",
"tcp_port": 6050,
}
},

Correct, command can be omitted in this  case (did you try it?)
I'd like to invite you to the gitter chat (gitter.im/SublimeLSP/Lobby) as this is turning more into a support discussion.

I asked my question again on gitter. Thanks.


text:
Add ButtonGroup

Set the size and variant of all buttons within it.
Add spacing between the buttons.
Flush the buttons together by removing the border radius of their children as needed

Add spacing between the buttons.

Container are fine for it.
The idea is good but it is still very complicated to implement and we may encounter some bugs, I lower the priority and put it on "low".

The goal of this group container is to assign the same props to every buttons within it like this, i think it could be great to have that feature, not only for tonightpass, but as a complete ui-kit.
<ButtonGroup variant='outline'>
  <Button color='blue'>Save</Button>
  <Button>Cancel</Button>
</ButtonGroup>

https://chakra-ui.com/docs/components/button

authors: AntoineKM jerembdn

repo: tonightpass/kitchen


text:
[BUG] Reconciled & Scheduled Buttons Stacked & Spaced Incorrectly

Describe the bug
The clickable icons to enable/disable showing reconciled and scheduled transactions now appear to be stacked on top of each other and not in the proper location on the accounts screen.
To Reproduce

Navigate to the accounts screen.

Expected behavior
The buttons should be next to each other with appropriate spacing.
Screenshots
https://i.imgur.com/yoagUr7.png
Desktop (please complete the following information):

OS: Windows 10
Browser: Chrome 81.0.4044.138
Toolkit Version: 2.23.1

Setting Export
[{"key":"AccountsDisplayDensity","value":"0"},{"key":"AccountsEmphasizedOutflows","value":false},{"key":"AccountsStripedRows","value":true},{"key":"AutoDistributeSplits","value":false},{"key":"AutoEnableRunningBalance","value":false},{"key":"AutomaticallyMarkAsCleared","value":false},{"key":"BetterScrollbars","value":"2"},{"key":"BottomNotificationBar","value":false},{"key":"BudgetCategoryFeatures","value":true},{"key":"BudgetProgressBars","value":"0"},{"key":"BudgetQuickSwitch","value":false},{"key":"BudgetSpendingGoal","value":true},{"key":"BulkManagePayees","value":false},{"key":"CalendarFirstDay","value":"0"},{"key":"CategoryActivityCopy","value":true},{"key":"CategoryActivityPopupWidth","value":"2"},{"key":"CategorySoloMode","value":"cat-toggle-all"},{"key":"ChangeEnterBehavior","value":true},{"key":"ChangeMemoEnterBehavior","value":false},{"key":"CheckCreditBalances","value":false},{"key":"CheckNumbers","value":false},{"key":"ClearSelection","value":true},{"key":"CollapseSideMenu","value":false},{"key":"ColourBlindMode","value":false},{"key":"CompactIncomeVsExpense","value":true},{"key":"ConfirmKeyboardCancelationOfTransactionChanges","value":false},{"key":"CreditCardEmoji","value":false},{"key":"CurrentMonthIndicator","value":false},{"key":"CustomFlagNames","value":false},{"key":"DateOfMoney","value":false},{"key":"DaysOfBuffering","value":true},{"key":"DaysOfBufferingDate","value":false},{"key":"DaysOfBufferingHistoryLookup","value":"12"},{"key":"DeselectTransactionsOnSave","value":true},{"key":"DisableToolkit","value":false},{"key":"DisplayTargetGoalAmount","value":"0"},{"key":"DisplayTotalMonthlyGoals","value":true},{"key":"DisplayUpcomingAmount","value":false},{"key":"EasyTransactionApproval","value":false},{"key":"EditAccountButton","value":"0"},{"key":"EnlargeCategoriesDropdown","value":true},{"key":"EnterToMove","value":true},{"key":"FilterCategories","value":true},{"key":"GoalIndicator","value":false},{"key":"GoalWarningColor","value":true},{"key":"GoogleFontsSelector","value":"0"},{"key":"HideAccountBalancesType","value":"0"},{"key":"HideAgeOfMoney","value":false},{"key":"HideClosedAccounts","value":false},{"key":"HideHelp","value":true},{"key":"HideReferralBanner","value":true},{"key":"HideTotalAvailable","value":false},{"key":"HighlightNegatives","value":true},{"key":"ImportNotification","value":"0"},{"key":"IncomeFromLastMonth","value":"0"},{"key":"IncomeVsExpenseHoverHighlight","value":true},{"key":"LargerClickableIcons","value":false},{"key":"LinkToInflows","value":true},{"key":"MonthlyNotesPopupWidth","value":"1"},{"key":"NavDisplayDensity","value":"1"},{"key":"NotesAsMarkdown","value":false},{"key":"POSStyleCurrencyEntryMode","value":false},{"key":"Pacing","value":"0"},{"key":"PrintingImprovements","value":true},{"key":"PrivacyMode","value":"2"},{"key":"QuickBudgetWarning","value":false},{"key":"ReconciledTextColor","value":"1"},{"key":"RemovePositiveHighlight","value":false},{"key":"RemoveZeroCategories","value":true},{"key":"ResizeInspector","value":true},{"key":"ResizeSidebar","value":true},{"key":"RightClickToEdit","value":true},{"key":"RowHeight","value":"0"},{"key":"RowsHeight","value":"0"},{"key":"RunningBalance","value":"0"},{"key":"SeamlessBudgetHeader","value":true},{"key":"SetMultipleFlags","value":true},{"key":"ShowCategoryBalance","value":true},{"key":"SpareChange","value":false},{"key":"SplitTransactionAutoAdjust","value":true},{"key":"SquareNegativeMode","value":false},{"key":"StealingFromFuture","value":false},{"key":"StripedBudgetRows","value":true},{"key":"SwapClearedFlagged","value":false},{"key":"TargetBalanceWarning","value":false},{"key":"ToBeBudgetedWarning","value":true},{"key":"ToggleMasterCategories","value":true},{"key":"ToggleSplits","value":false},{"key":"ToggleTransactionFilters","value":"1"},{"key":"ToolkitReports","value":true},{"key":"TransactionGridFeatures","value":true},{"key":"ViewZeroAsEmpty","value":true},{"key":"l10n","value":"0"},{"key":"options.dark-mode","value":true}]

I have the same issue using Chrome on macOS.

This appears to be fixed to me? Please reopen if not.

authors: gouldjames joshmadewell undaunt

repo: toolkit-for-ynab/toolkit-for-ynab


text:
update README to suggest using Node v10 or lower

I spent a few hours trying to get the extension to build and it would always fail with various errors. Turns out if you try to build with a Node version that's greater than 10 it will fail (yeah, should have tried that first). I tried v16, 14, and 12 with no success.

I had the same issue until I checked the package.json: https://github.com/toolkit-for-ynab/toolkit-for-ynab/blob/master/package.json#L151
This would help a lot, and I hope that the project can update to node 14+ at some point...

Ah, yep, there it is.
"engines": {
    "node": "^8.16.0 || ^10.13.0 || >=11.10.1",

It seems like >=11.10.1 might be a mistake? It should be ^11.10.1 instead. i.e.
"engines": {
    "node": "^8.16.0 || ^10.13.0 || ^11.10.1",

That way yarn correctly throws an error if you try to yarn install with a version of node that's not one of those 3 major versions (or not greater than or equal to the minor version for each).
$ yarn install
error toolkit-for-ynab@2.32.0: The engine "node" is incompatible with this module. Expected version "^8.16.0 || ^10.13.0 || ^11.10.1". Got "12.22.1"

That's odd, I'm running node 16.1.0 and the extension has been building successfully for me.
I'm on Windows, with node and yarn installed via chocolatey. I had to install Python and Visual Studio Build Tools for node-gyp but after that I don't think I had any issues.

I'm on MacOS 10.14.6 Mojave, and had the same issues as OP, yarn and nvm installed via brew, and node installed via nvm.

I've been running node 12 without any issues (x64 Win10).  Haven't tried v14 or v16.

Blegh, we should always support the LTS version of node. I'll try to spend the time this weekend getting this to work!

hmmm so I just tried this on osx and windows and it's working fine :(
node: 14.16.0
yarn: 1.16.0

Well, I'm not sure what changed but I'm able to build it no problem now with the latest LTS version (building on linux). I can also build without issue on v8, v10, v11, v12, and v13. I still think it's probably a good idea to update the package.json engines and the readme.


text:
PRs that only have the repository as a source are shown in changelogs

Our changelog shows PRs from our repo into a fork. This is especially annoying since https://github.com/apps/pull is used to keep the forks up to date which creates a lot of those PRs. The link to those PRs is also wrong, since it uses the right id but the wrong repo.
So in bakdata/conquery you can see

while these PRs are actually in a fork, e.g.

This should be solved by #251 I think

Oh yeah, awesome.

repo: toolmantim/release-drafter


text:
Allow multiple queues per worker configuration

Take a look at this enhancement.  This change allows for you to run multiple queues for a given worker application.
In my use case, I run multiple SAQ workers as a component of an "Agent" daemon that runs on groups of servers.  Each API process can service multiple groups of the agent workers.  This allows me to send tasks to particular groups of workers or create a "high priority" worker queue in addition to the default.

Nice, I just started thinking about this yesterday as I worked through exposing the job configs. An easy way to scope the keys beneath the application slug makes a lot of sense!

Closing in favor of #227 (changing base branch - using semantic releases makes me want to group commits into a release branch if I have a few things to work on. I still have work to do on a good default workflow for this).

authors: cofin peterschutt

repo: topsport-com-au/starlite-saqlalchemy


text:
Refactoring of THCNumerics

Here, this refactoring was initially driven by idea of supporting both pseudo and native fp16 for a single arch. That support proved to be unfeasible, but the refactoring made the code much cleaner and shorter, take a look.
Also, CUDA_HALF_INSTRUCTIONS compile-time switch is turned on for 6.0 and 6.2+ architectures in this version - if you encounter any new issues with accuracy on Pascal, try turning it off.

Replaced by https://github.com/torch/cutorch/pull/679

repo: torch/cutorch


text:
Make String.startsWith return ${P}${string}

See: https://github.com/microsoft/TypeScript/issues/46958

also https://github.com/microsoft/TypeScript/issues/58152

Closing for reasons described here

authors: alexgleason btoo mattpocock

repo: total-typescript/ts-reset


text:
[Bug]: Code is wrong reporting "operator towhee/select not found!" in face-landmark-detection for mobilefacenet

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
>>> towhee.glob('/Users/binbin/Towhee_projects/image.png') \
...   .image_decode.cv2() \
...   .face_landmark_detection.mobilefacenet() \
...   .select('img','landmark') \
...   .to_list()
2022-07-20 12:08:07,482 - 4628667904 - git_utils.py-git_utils:96 - ERROR: towhee/select repo does not exist.
Traceback (most recent call last):
  File "/Users/binbin/towhee-test-env-3.8-0.7.3/lib/python3.8/site-packages/towhee/engine/operator_loader.py", line 134, in load_operator_from_cache
    path = fm.get_operator(operator=function, tag=tag)
  File "/Users/binbin/towhee-test-env-3.8-0.7.3/lib/python3.8/site-packages/towhee/hub/file_manager.py", line 451, in get_operator
    git.clone(tag=tag, install_reqs=install_reqs, local_repo_path=repo_path)
  File "/Users/binbin/towhee-test-env-3.8-0.7.3/lib/python3.8/site-packages/towhee/utils/git_utils.py", line 97, in clone
    raise ValueError(f'{self._author}/{self._repo} repo does not exist.')
ValueError: towhee/select repo does not exist.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/binbin/towhee-test-env-3.8-0.7.3/lib/python3.8/site-packages/towhee/hparam/hyperparameter.py", line 198, in __call__
    return self._func(*args, **kws)
  File "/Users/binbin/towhee-test-env-3.8-0.7.3/lib/python3.8/site-packages/towhee/functional/data_collection.py", line 156, in wrapper
    return self.map(op)
  File "/Users/binbin/towhee-test-env-3.8-0.7.3/lib/python3.8/site-packages/towhee/functional/mixins/dag.py", line 11, in wrapper
    children = f(self, *arg, **kws)
  File "/Users/binbin/towhee-test-env-3.8-0.7.3/lib/python3.8/site-packages/towhee/functional/data_collection.py", line 315, in map
    if hasattr(unary_op, 'is_stateful') and unary_op.is_stateful:
  File "/Users/binbin/towhee-test-env-3.8-0.7.3/lib/python3.8/site-packages/towhee/engine/execution/stateful_execution.py", line 30, in is_stateful
    self.__check_init__()
  File "/Users/binbin/towhee-test-env-3.8-0.7.3/lib/python3.8/site-packages/towhee/engine/factory.py", line 93, in __check_init__
    self._op = op(self._name,
  File "/Users/binbin/towhee-test-env-3.8-0.7.3/lib/python3.8/site-packages/towhee/engine/factory.py", line 61, in op
    return loader.load_operator(operator_src, arg, kwargs, tag)
  File "/Users/binbin/towhee-test-env-3.8-0.7.3/lib/python3.8/site-packages/towhee/engine/operator_loader.py", line 162, in load_operator
    op = factory(function, arg, kws, tag)
  File "/Users/binbin/towhee-test-env-3.8-0.7.3/lib/python3.8/site-packages/towhee/engine/operator_loader.py", line 136, in load_operator_from_cache
    raise ValueError('operator {} not found!'.format(function)) from e
ValueError: operator towhee/select not found!

Expected Behavior
I think here ".select('img','landmark') " is wrong?
The following is correct with ".select'img','landmark' "
>>> towhee.glob['path']('/Users/binbin/Towhee_projects/image.png') \
...   .image_decode.cv2['path', 'img']() \
...   .face_landmark_detection.mobilefacenet['img', 'landmark']() \
...   .select['img','landmark']() \
...   .show()
<IPython.core.display.HTML object>

Steps To Reproduce
https://towhee.io/face-landmark-detection/mobilefacenet

Environment
- Towhee version(e.g. v0.1.3 or 8b23a93):towhee 0.7.3.dev32 (models latest)
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:

Anything else?
No response

It has been fixed，please check the latest doc.

authors: binbinlv wxywb

repo: towhee-io/towhee


text:
Extra module

Feel free to add AtCoder.Extra.* modules! These modules would be available on AtCoder after next language update. The big point is that they can be used with qualified imports!

My recommendations:

[ ] Heavy-light decomposition
[ ] IntervalMap
[ ] IntHashMap
[ ] IntMap (dense, 64-trie)
[ ] Max cost flow function to MinCostFlow
[ ] MultiSet
[ ] Rolling Hash (monoid-based)

Difficult (for me):

[ ] Aho-corasick
[ ] Convex hull trick
[ ] Li-chao tree


text:
Duration ...  HowTo set ?

Hi,
Congratz with the development of this library. Really great work !
If I can ask ...
How would you suggest to set the duration for repeating events ?
E.g. I have weekly meetings on Monday, Wednesday and Friday starting at 08:AM and a duration of 2 hrs...
Startday is June 1st, and Endday is June 29th...
I'm getting a bit confused with all the options I can set ...
Thanks in advance for your reply,
Johnny

Sorry about my question...
Realising now it's rather irrelevant ...

repo: tplaner/When


text:
Please document how to work around vim bug using  the vim package format (Not directly related to pathogen)

I use pathogen for many years now. Recently, I migrated, motivated by the notice in your readme, to the native package format in vim.
Unfortunately that made at least one plugin, fugitive, not working correct anymore. The bindings in blame window are broken now.
So could you please document one or both of the following?

Add a warning to users that vim packages might not work correctly.
Add a hint how to mitigate that bug(s) in vim with pathogen. (Maybe one can use execute pathogen#infect('bundle/{}', 'pack/{}/start/{}') to mitigare that. I did not chek until now if that work)

I personally use Fugitive in this exact setup without issue. Without knowing what's going wrong on your machine, I don't think there's anything to be done here.

authors: mowgli tpope

repo: tpope/vim-pathogen

license: Vim


text:
provide a mechanism to allocate funds

after the chain is created - only the bootstrap account is funded and so only the bootstrap account can bake
provide a mechanism for chain participants to request and receive funds to allow baking privileges.

There are a couple of scenarios, we may want to allow users to choose between one or more of them:
The testnet faucet:

the deployment allows anyone to go to https://faucet.tzalpha.net/ and get a (fake) ICO account
for that, we only need to include the same commitments as carthagenet/delphinet in the parameters.json (I have one example of such JSON here:
https://gitlab.com/smondet/tezos/-/blob/4b51e6046e47e2b888a637f0120b3364ae41149b/activate-labnet.sh)

The DAO-consortium:

the funds are in a multisig (or on-chain-voting) contract that acts as a DAO and a quorum of existing share-holders can transfer funds to the new-comer (and potentially add their pubkey to the DAO-voters)
we can use the multisig.tz or some exisiting DAO contract, likely, we'll want to add a CLI-wrapper, or a webapp

The specialized “baking rights” bank:

the funds are also in a DAO-ish contract but the contract (or the way it's called) has some logic to treat baking rights separately: the new-comer gets a few ꜩ to run operations and pay for gas, but most of its baking rights come from a KT1 originated-by and under-control-of the central bank which uses SET_DELEGATE to give rights to the new-comer.
multisig.tz and manager.tz are so generic that I think we can use those 2 and just make a nice command line wrapper that crafts lambdas — may be interesting to encode more of the logic in the contract though (it's a “constitutional” central bank after all, we may want to forbid some usages)

The completely custom setup:

the users may know better what they want, and can provide their own contract and associated tooling

https://gitlab.com/nomadic-labs/tezos-faucet

authors: agtilden harryttd smondet


text:
maximumFileSizeToCacheInBytes to 5Mb

The main javascript file is not being cached by the service worker be cause it passes the 4Mb limit.
The problem here is the server updates. If you update the server with a new build, the page won't open because the service worker will try to fetch and old javascript file which doesn't exist anymore.
It can be stuck forever. For it to update you have to shutdown the browser (not just refresh the page or close the tab/window) so that all clients release the active service worker.
If we cache the main javascript we won't have this problem, the page will open and the popup for the update will appear.

I say we pick a higher number, like 10MB. Also let's make it proper 10MB (10 * 1024 * 1024).

authors: jcardus tananaev

repo: traccar/traccar-web


text:
Update scala3-library to 3.3.1

About this PR
📦 Updates org.scala-lang:scala3-library from 3.1.3 to 3.3.1
📜 GitHub Release Notes - Version Diff - Version Diff
Usage
✅ Please merge!
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!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala3-library" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-lang", artifactId = "scala3-library" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:semver-spec, commit-count:n:2

Superseded by #349.


text:
FPO-87: Attempting to improve the startup time somewhat

Jira link
https://transformuk.atlassian.net/browse/FPO-87
What?
I have added/removed/altered:

[x] Altered the caching of the sentence transformer model to use pytorch load/save as it's much quicker
[x] Altered ruff to use a max line length of 120 columns

Why?
I am doing this because:

The startup time is a bit slow
It's 2024. Who's still using an 80 column display??!!

AC

The lambda startup time is a bit faster than it was

We can revisit this.

authors: ashward willfish


text:
Invalid candlestick rendering/scaling with addCandlestickSeries

Lightweight Charts Version: 3.2.0
Steps/code to reproduce:
useEffect(() => {
  const c = createChart(chartRef.current, {
    // styling options: colors, fonts, etc.
  });

  const candlestickSeries = c.addCandlestickSeries({
    // styling options
  });

  return () => c.remove();
}, []);

// later
candlesticks.forEach(candlestick => candlestickSeries.update(candlestick));

Actual behavior:

Sometimes initial scaling is incorrect, part of candlesticks is not visible, rendered outside of the visible area.
Sometimes growth candlestick (close > open) is rendered as if it was close < open.
Sometimes both at the same time.

Expected behavior:
Expecting correct initial scaling and correct candlestick color.
Screenshots:
Invalid scaling and candlestick color:

Invalid candlestick color, scaled manually to fit the visible area:

CodeSandbox/JSFiddle/etc link:
I can not figure out the pattern that causes this behavior, so no special code sample. Data set for the chart from the screenshots is:
[{
  open: "92.49",
  high: "131.65",
  low: "92.49",
  close: "128.00",
  created_at: "2020-12-10T00:00:02.001Z"
}, {
  open: "42",
  high: "99.00",
  low: "42",
  close: "92.49",
  created_at: "2020-12-09T18:41:00.034Z"
}]

created_at is mapped to timestamp like Math.floor((new Date(created_at)).getTime() / 1000).
I suspect there is some if (open < close) comparison which works fine for numbers, but obviously is not correct when comparing stringified numbers ('100' < '90' === true but should be otherwise in this case). If my assumprion is correct, and if the series does not expect stringified numbers, I believe there should be an error or at least warning. Or, if it is allowed, comparison should be done correctly.

and if the series does not expect stringified numbers

Yes, it definitely doesn't expect strings for numbers.

I believe there should be an error or at least warning.

We already should have warnings for such cases, but only in development mode. We drop that checks in production build on purpose to avoid 1) increasing bundle size 2) unnecessary checks in the production.
Probably at the moment it might be tricky to enable debug build though, but I thought that it should works fine at least for webpack by default. We're going to provide some docs for that soon, but so far you can see https://github.com/tradingview/lightweight-charts/blob/cjs-and-ssr/docs/debug-mode.md#webpack.

Debug checks in runtime were added in https://github.com/tradingview/lightweight-charts/pull/578.

authors: ololoepepe timocov

repo: tradingview/lightweight-charts


text:
Plugin: Parsing string array in nested config structs doesn't work

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
I'am working on a traefik plugin where i want to configure the plugin using a yaml-array.
This works fine on top-level, but not on a nested one.
I found the following depending PRs:

https://github.com/traefik/traefik/pull/8886
https://github.com/traefik/paerser/pull/15

They all talk about traefik 2.x but i'am using 3.1.
Is there something missing in v3?
Here is my code:
Config:
middlewares:
    oidc-auth:
      plugin:
        traefik-oidc-auth:
          Authorization:
            AssertClaims:
              - Name: "preferred_username"
                Values: ["value1", "value2", "value3"]

Structs:
type Config struct {
	Authorization *AuthorizationConfig `json:"authorization"`
}
type AuthorizationConfig struct {
	AssertClaims []ClaimAssertion `json:"assert_claims"`
}
type ClaimAssertion struct {
	Name   string   `json:"name"`
	Value  string   `json:"value"`
	Values []string `json:"values"`
}

What did you see instead?
When i loop over the Values-array, i get: [║24║value1║value2║value3]
Instead, i'am expecting to get a real array.
The only workaround is to use:
Values: "value1,value2,value3"

What version of Traefik are you using?
Version:      3.1.2
Codename:     comte
Go version:   go1.22.5
Built:        2024-08-06T13:37:51Z
OS/Arch:      linux/amd64
What is your environment & configuration?
global:
  checkNewVersion: true
  sendAnonymousUsage: true

entryPoints:
  web:
    address: :80

# Enable API and dashboard
api:
  insecure: true
  dashboard: true
  debug: true

experimental:
  localPlugins:
    traefik-oidc-auth:
      moduleName: github.com/sevensolutions/traefik-oidc-auth

providers:
  file:
    filename: /etc/traefik/configs/http.yml
    watch: true

If applicable, please paste the log output in DEBUG level
No response

Hello @sevensolutions,
Thanks for the bug report, we were able to reproduce it. We would love community support to address it.
If you or another community member would like to build it, let us know, and we will work with you to make sure you have all the information needed so that it can be merged.
We prefer to work with our community members at the beginning of the design process so that we can make sure that we are aligned and can move quickly with the review and merge process.  Let us know here or create a PR before you start, and we will work with you there.
Don’t forget to check out the (contributor docs)[https://doc.traefik.io/traefik/contributing/submitting-pull-requests/] and to link the PR to this issue.

Hi @nmengin,
i've cloned the repo and started analyzing this a bit but i don't really understand it.
It looks like this exact problem has already been fixed in the paerser-library in this commit
I've then checked which version of paerser is used by traefik, which is 0.2.0. This already includes the fix.
It looks like traefik 3 has the same problem which has been fixed in #8886 so i think we just need to apply the same changes to version 3. Maybe this should have been merged but haven't?
I can try to implement these changes and make some tests...

Hello @sevensolutions,
Thank you for your feedback, and your analysis.
I share the issue with the other maintainers.
We'll keep you updated after that.

Thx. I will re-do my changes on the correct base branch (v3.1) in the meantime.

authors: nmengin sevensolutions

repo: traefik/traefik