text:
Possible issue with codegen/vm

What Git revision are you using?
aiken v1.0.24-alpha+b6b57c7
What operating system are you using, and which version?
nixos
Describe what the problem is?
Possible problem between the vm and codegen ?

 aiken output

× test_and2_bool failed
  help: ┍━ left ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┑
        │ Unable to unlift value because it is not a constant:        │
        │                                                             │
        │ Lambda {                                                    │
        │     parameter_name: NamedDeBruijn {                         │
        │         text: "_capture__1",                                │
        │         index: DeBruijn(                                    │
        │             0,                                              │
        │         ),                                                  │
        │     },                                                      │
        │     body: Force(                                            │
        │         Apply {                                             │
        │             function: Apply {                               │
        │                 function: Apply {                           │
        │                     function: Var(                          │
        │                         NamedDeBruijn {                     │
        │                             text: "__if_then_else_wrapped", │
        │                             index: DeBruijn(                │
        │                                 4,                          │
        │                             ),                              │
        │                         },                                  │
        │                     ),                                      │
        │                     argument: Var(                          │
        │                         NamedDeBruijn {                     │
        │                             text: "x",                      │
        │                             index: DeBruijn(                │
        │                                 2,                          │
        │                             ),                              │
        │                         },                                  │
        │                     ),                                      │
        │                 },                                          │
        │                 argument: Delay(                            │
        │                     Var(                                    │
        │                         NamedDeBruijn {                     │
        │                             text: "_capture__1",            │
        │                             index: DeBruijn(                │
        │                                 1,                          │
        │                             ),                              │
        │                         },                                  │
        │                     ),                                      │
        │                 ),                                          │
        │             },                                              │
        │             argument: Delay(                                │
        │                 Constant(                                   │
        │                     Bool(                                   │
        │                         false,                              │
        │                     ),                                      │
        │                 ),                                          │
        │             ),                                              │
        │         },                                                  │
        │     ),                                                      │
        │     env: [                                                  │
        │         Builtin {                                           │
        │             fun: TailList,                                  │
        │             runtime: BuiltinRuntime {                       │
        │                 args: [],                                   │
        │                 fun: TailList,                              │
        │                 forces: 1,                                  │
        │             },                                              │
        │         },                                                  │
        │         Builtin {                                           │
        │             fun: HeadList,                                  │
        │             runtime: BuiltinRuntime {                       │
        │                 args: [],                                   │
        │                 fun: HeadList,                              │
        │                 forces: 1,                                  │
        │             },                                              │
        │         },                                                  │
        │         Builtin {                                           │
        │             fun: MkCons,                                    │
        │             runtime: BuiltinRuntime {                       │
        │                 args: [],                                   │
        │                 fun: MkCons,                                │
        │                 forces: 1,                                  │
        │             },                                              │
        │         },                                                  │
        │         Builtin {                                           │
        │             fun: ChooseList,                                │
        │             runtime: BuiltinRuntime {                       │
        │                 args: [],                                   │
        │                 fun: ChooseList,                            │
        │                 forces: 2,                                  │
        │             },                                              │
        │         },                                                  │
        │         Builtin {                                           │
        │             fun: SndPair,                                   │
        │             runtime: BuiltinRuntime {                       │
        │                 args: [],                                   │
        │                 fun: SndPair,                               │
        │                 forces: 2,                                  │
        │             },                                              │
        │         },                                                  │
        │         Builtin {                                           │
        │             fun: FstPair,                                   │
        │             runtime: BuiltinRuntime {                       │
        │                 args: [],                                   │
        │                 fun: FstPair,                               │
        │                 forces: 2,                                  │
        │             },                                              │
        │         },                                                  │
        │         Builtin {                                           │
        │             fun: Trace,                                     │
        │             runtime: BuiltinRuntime {                       │
        │                 args: [],                                   │
        │                 fun: Trace,                                 │
        │                 forces: 1,                                  │
        │             },                                              │
        │         },                                                  │
        │         Builtin {                                           │
        │             fun: IfThenElse,                                │
        │             runtime: BuiltinRuntime {                       │
        │                 args: [],                                   │
        │                 fun: IfThenElse,                            │
        │                 forces: 1,                                  │
        │             },                                              │
        │         },                                                  │
        │         Con(                                                │
        │             ProtoPair(                                      │
        │                 Data,                                       │
        │                 Data,                                       │
        │                 Data(                                       │
        │                     Constr(                                 │
        │                         Constr {                            │
        │                             tag: 121,                       │
        │                             any_constructor: None,          │
        │                             fields: [                       │
        │                                 BigInt(                     │
        │                                     BigUInt(                │
        │                                         BoundedBytes(       │
        │                                             [               │
        │                                                 181,        │
        │                                                 242,        │
        │                                                 62,         │
        │                                                 231,        │
        │                                                 152,        │
        │                                                 36,         │
        │                                                 225,        │
        │                                                 158,        │
        │                                                 43,         │
        │                                                 11,         │
        │                                                 160,        │
        │                                                 23,         │
        │                                                 144,        │
        │                                                 85,         │
        │                                                 204,        │
        │                                                 154,        │
        │                                                 207,        │
        │                                                 100,        │
        │                                                 71,         │
        │                                                 164,        │
        │                                                 63,         │
        │                                                 110,        │
        │                                                 216,        │
        │                                                 86,         │
        │                                                 242,        │
        │                                                 43,         │
        │                                                 64,         │
        │                                                 177,        │
        │                                                 46,         │
        │                                                 18,         │
        │                                                 90,         │
        │                                                 57,         │
        │                                             ],              │
        │                                         ),                  │
        │                                     ),                      │
        │                                 ),                          │
        │                                 BigInt(                     │
        │                                     Int(                    │
        │                                         Int(                │
        │                                             Int {           │
        │                                                 neg: false, │
        │                                                 val: 1,     │
        │                                             },              │
        │                                         ),                  │
        │                                     ),                      │
        │                                 ),                          │
        │                             ],                              │
        │                         },                                  │
        │                     ),                                      │
        │                 ),                                          │
        │                 Data(                                       │
        │                     Constr(                                 │
        │                         Constr {                            │
        │                             tag: 122,                       │
        │                             any_constructor: None,          │
        │                             fields: [],                     │
        │                         },                                  │
        │                     ),                                      │
        │                 ),                                          │
        │             ),                                              │
        │         ),                                                  │
        │         Con(                                                │
        │             Bool(                                           │
        │                 true,                                       │
        │             ),                                              │
        │         ),                                                  │
        │     ],                                                      │
        │ }                                                           │
        ┕━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┙

        should be equal to

        ┍━ right ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┑
        │ Unable to unlift value because it is not a constant:        │
        │                                                             │
        │ Lambda {                                                    │
        │     parameter_name: NamedDeBruijn {                         │
        │         text: "_capture__1",                                │
        │         index: DeBruijn(                                    │
        │             0,                                              │
        │         ),                                                  │
        │     },                                                      │
        │     body: Force(                                            │
        │         Apply {                                             │
        │             function: Apply {                               │
        │                 function: Apply {                           │
        │                     function: Var(                          │
        │                         NamedDeBruijn {                     │
        │                             text: "__if_then_else_wrapped", │
        │                             index: DeBruijn(                │
        │                                 4,                          │
        │                             ),                              │
        │                         },                                  │
        │                     ),                                      │
        │                     argument: Var(                          │
        │                         NamedDeBruijn {                     │
        │                             text: "x",                      │
        │                             index: DeBruijn(                │
        │                                 2,                          │
        │                             ),                              │
        │                         },                                  │
        │                     ),                                      │
        │                 },                                          │
        │                 argument: Delay(                            │
        │                     Var(                                    │
        │                         NamedDeBruijn {                     │
        │                             text: "_capture__1",            │
        │                             index: DeBruijn(                │
        │                                 1,                          │
        │                             ),                              │
        │                         },                                  │
        │                     ),                                      │
        │                 ),                                          │
        │             },                                              │
        │             argument: Delay(                                │
        │                 Constant(                                   │
        │                     Bool(                                   │
        │                         false,                              │
        │                     ),                                      │
        │                 ),                                          │
        │             ),                                              │
        │         },                                                  │
        │     ),                                                      │
        │     env: [                                                  │
        │         Builtin {                                           │
        │             fun: TailList,                                  │
        │             runtime: BuiltinRuntime {                       │
        │                 args: [],                                   │
        │                 fun: TailList,                              │
        │                 forces: 1,                                  │
        │             },                                              │
        │         },                                                  │
        │         Builtin {                                           │
        │             fun: HeadList,                                  │
        │             runtime: BuiltinRuntime {                       │
        │                 args: [],                                   │
        │                 fun: HeadList,                              │
        │                 forces: 1,                                  │
        │             },                                              │
        │         },                                                  │
        │         Builtin {                                           │
        │             fun: MkCons,                                    │
        │             runtime: BuiltinRuntime {                       │
        │                 args: [],                                   │
        │                 fun: MkCons,                                │
        │                 forces: 1,                                  │
        │             },                                              │
        │         },                                                  │
        │         Builtin {                                           │
        │             fun: ChooseList,                                │
        │             runtime: BuiltinRuntime {                       │
        │                 args: [],                                   │
        │                 fun: ChooseList,                            │
        │                 forces: 2,                                  │
        │             },                                              │
        │         },                                                  │
        │         Builtin {                                           │
        │             fun: SndPair,                                   │
        │             runtime: BuiltinRuntime {                       │
        │                 args: [],                                   │
        │                 fun: SndPair,                               │
        │                 forces: 2,                                  │
        │             },                                              │
        │         },                                                  │
        │         Builtin {                                           │
        │             fun: FstPair,                                   │
        │             runtime: BuiltinRuntime {                       │
        │                 args: [],                                   │
        │                 fun: FstPair,                               │
        │                 forces: 2,                                  │
        │             },                                              │
        │         },                                                  │
        │         Builtin {                                           │
        │             fun: Trace,                                     │
        │             runtime: BuiltinRuntime {                       │
        │                 args: [],                                   │
        │                 fun: Trace,                                 │
        │                 forces: 1,                                  │
        │             },                                              │
        │         },                                                  │
        │         Builtin {                                           │
        │             fun: IfThenElse,                                │
        │             runtime: BuiltinRuntime {                       │
        │                 args: [],                                   │
        │                 fun: IfThenElse,                            │
        │                 forces: 1,                                  │
        │             },                                              │
        │         },                                                  │
        │         Con(                                                │
        │             ProtoPair(                                      │
        │                 Data,                                       │
        │                 Data,                                       │
        │                 Data(                                       │
        │                     Constr(                                 │
        │                         Constr {                            │
        │                             tag: 121,                       │
        │                             any_constructor: None,          │
        │                             fields: [                       │
        │                                 BigInt(                     │
        │                                     BigUInt(                │
        │                                         BoundedBytes(       │
        │                                             [               │
        │                                                 181,        │
        │                                                 242,        │
        │                                                 62,         │
        │                                                 231,        │
        │                                                 152,        │
        │                                                 36,         │
        │                                                 225,        │
        │                                                 158,        │
        │                                                 43,         │
        │                                                 11,         │
        │                                                 160,        │
        │                                                 23,         │
        │                                                 144,        │
        │                                                 85,         │
        │                                                 204,        │
        │                                                 154,        │
        │                                                 207,        │
        │                                                 100,        │
        │                                                 71,         │
        │                                                 164,        │
        │                                                 63,         │
        │                                                 110,        │
        │                                                 216,        │
        │                                                 86,         │
        │                                                 242,        │
        │                                                 43,         │
        │                                                 64,         │
        │                                                 177,        │
        │                                                 46,         │
        │                                                 18,         │
        │                                                 90,         │
        │                                                 57,         │
        │                                             ],              │
        │                                         ),                  │
        │                                     ),                      │
        │                                 ),                          │
        │                                 BigInt(                     │
        │                                     Int(                    │
        │                                         Int(                │
        │                                             Int {           │
        │                                                 neg: false, │
        │                                                 val: 1,     │
        │                                             },              │
        │                                         ),                  │
        │                                     ),                      │
        │                                 ),                          │
        │                             ],                              │
        │                         },                                  │
        │                     ),                                      │
        │                 ),                                          │
        │                 Data(                                       │
        │                     Constr(                                 │
        │                         Constr {                            │
        │                             tag: 122,                       │
        │                             any_constructor: None,          │
        │                             fields: [],                     │
        │                         },                                  │
        │                     ),                                      │
        │                 ),                                          │
        │             ),                                              │
        │         ),                                                  │
        │         Con(                                                │
        │             Bool(                                           │
        │                 true,                                       │
        │             ),                                              │
        │         ),                                                  │
        │     ],                                                      │
        │ }                                                           │
        ┕━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┙

      Summary 1 error, 32 warnings

To reproduce: run aiken check on https://github.com/waalge/aiken-fuzz/commit/338c9c6a9749110e2acf27befc3755494eda0d51
See also commented out tests that also use map2 but have larger error message output
What should be the expected behavior?
running tests

thanks for reporting, we'll take a look

I looked further and found this
pub fn map2(f: fn(a, b) -> c, fuzz_a: Fuzzer<a>, fuzz_b: Fuzzer<b>) -> Fuzzer<c> {
  fn(x) { f(x, _) }
    |> map(fuzz_a)
    |> and_map(fuzz_b)
}

The underscore in f(x, _) should cause a type checking error and should not even reach codegen.

Nvm still seeing the issue after changing the code will look into a bit more

Ok found the actual issue missing from the type checker
pub fn map(f: fn(a) -> b, fuzz_a: Fuzzer<a>) -> Fuzzer<b> {
  fn(s0) {
    let (s1, a) = fuzz_a(s0)
    (s1, f(a))
  }
}

pub fn and_map(fuzz_f: Fuzzer<fn(a) -> b>, fuzz_a: Fuzzer<a>) -> Fuzzer<b> {
  fn(s0) {
    let (s1, f) = fuzz_f(s0)
    let (s2, a) = fuzz_a(s1)
    (s2, f(a))
  }
}

pub fn and_then(f: fn(a) -> Fuzzer<b>, fuzz_a: Fuzzer<a>) -> Fuzzer<b> {
  fn(s0) {
    let (s1, a) = fuzz_a(s0)
    f(a)(s1)
  }
}

/// A convenient composition of map and and_map
pub fn map2(f: fn(a, b) -> c, fuzz_a: Fuzzer<a>, fuzz_b: Fuzzer<b>) -> Fuzzer<c> {
  fn(y) { fn(x) { f(y, x) } }
    |> map(fuzz_a)
    |> and_map(fuzz_b)
}

The type check is missing out on preventing tuples that hold functions from being allowed.

When you hover over
|> map(fuzz_a) the type checker can see that a tuple containing a function is being returned. This should be banned via type checker.

Essentially and_map is not able to be represented in Aiken using tuples.

Indeed, so that goes in the bucket of "things we have to disable with the type-checkers", in the same way that we can't have List<x> where x is anything else than something that unifies with Data.
Note, it works with this very idiomatic Aiken code 😬:
type Tuple<a, b> =
  fn(fn(a, b) -> _) -> _

pub fn tuple(a: a, b: b) -> Tuple<a, b> {
  fn(f) { f(a, b) }
}

pub fn fst(t: Tuple<a, b>) -> a {
  t(fn(a, _) { a })
}

pub fn snd(t: Tuple<a, b>) -> b {
  t(fn(_, b) { b })
}

type Fuzzer<a> =
  fn(Int) -> Tuple<Int, a>

fn int() -> Fuzzer<Int> {
  fn(seed) { tuple(seed, seed) }
}

fn bool() -> Fuzzer<Bool> {
  fn(seed) { tuple(seed, seed % 2 == 0) }
}

fn map(f: fn(a) -> b, fuzz_a: Fuzzer<a>) -> Fuzzer<b> {
  fn(s) {
    let t = fuzz_a(s)
    tuple(fst(t), f(snd(t)))
  }
}

fn and_map(fuzz_f: Fuzzer<fn(a) -> b>, fuzz_a: Fuzzer<a>) -> Fuzzer<b> {
  fn(s0) {
    let t0 = fuzz_f(s0)
    let t1 = fuzz_a(fst(t0))
    tuple(fst(t1), snd(t0)(snd(t1)))
  }
}

type Foo {
  a0: Bool,
  a1: Int,
}

fn mk_foo(a0: Bool) -> fn(Int) -> Foo {
  fn(a1) { Foo { a0, a1 } }
}

test foo() {
  let fuzzer =
    mk_foo
      |> map(bool())
      |> and_map(int())

  snd(fuzzer(42)) == Foo { a0: True, a1: 42 }
}

Closed in #869

authors: KtorZ MicroProofs rvcas waalge

repo: aiken-lang/aiken


text:
mdp value iteration calculation seems wrong

I am using the mdp.GridMDP as documented.
   seq_dec_environ = GridMDP([[-3, -3, -3, +100],
                              [-3, None, -3,-100],
                              [-3,  -3, -3, -3]],
                              terminals=[(0, 3), (1, 3)], gamma=0.8)

   print_table(seq_dec_environ.to_grid(mdp.value_iteration(seq_dec_environ)))

And he result was
182.49732656930627    250.0934953917249   332.93553924746084     452.266550537396
 135.4739047797976                 None   248.12890941320666   227.50075663876515
 102.6064691402491   133.68576924105906    180.1503986747119    170.6655512537616

Thing to observe. It is updating the reward state values. That should not happen. This is a bug in the code too.

The values, since it updates the reward state values (+100, -100), and goes about calculating rest, the numbers are weird.

The expected matrix should be as discussed in the value iteration video

85 89 93 100
81 None 68 -100
77 73 70 47

The terminals takes indices in a different format. The origin is the bottom left cell. Right is (1, 0) and Up is (0, 1). The terminals which you have given in python list format would become [(3, 2), (3, 1)] in the expected format
Also if you wish to get the output similar to the video you need to set the value of gamma to 1(no loss). Since then implementation doesn't allow such a value, set it it 0.9999 or a similar high value

Thanks, @Chipe1 for clarification. Closing this, ticket.

source: gharchive/issue

repo: aimacode/aima-python

license: mit

license_type: permissive

license_source: bigquery


text:
Mask shape error in xder code implementation

Hello. Thank you for your recent work and for sharing xder code.
While I tried to reproduce your work on my one, I encountered a troublesome as follows.

File ".../models/xder.py", line 143, in update_logits
gt_values = old[torch.arange(len(gt)), gt]
IndexError: The shape of the mask [32] at index 0 does not match the shape of the indexed tensor [32, 10] at index 1
Have you ever met such problem? I'd like to ask you how to fix it. Thank you.

Hello there,
I'm gonna need some more details to assess what's happening. (i) What dataset are you using? (is it one of ours?) (ii) what shape is the input tensor of the observe function?

Thank you for your quick response. For detail, (i) I using custom dataset, (2)

Thank you for your quick replying. First of all, I tried to run this code for a custom dataset with some modifications. After I examined the code with the cifar-100 dataset, the existing code works well with no troubleshooting. I will update the comment later if I meet the same problem after I look into the code. Thank you :D

Ok, great!
Let me know if you have any trouble.

repo: aimagelab/mammoth

license: MIT

license_source: github-api


text:
Possible standards violation: 8BITMIME (decode_data=True) implies Strict ASCII (if SMTPUTF8 not enabled)

Currently, the only way to make SMTP return the 8BITMIME capability is by setting decode_data=True
However, this activated the piece of code in smtp_DATA which enforces "Strict ASCII".
Indicating 8BITMIME but rejecting "arbitrary octet-aligned data" is a violation of RFC 6152, notably Section 3.
I propose:

We separate decode_data with "Strict ASCII", and
For decode_data without "Strict ASCII", the encoding used for .decode() should be "Latin-1"

Point No. 1 above means that this change have the potential of breaking things; so I propose we bump up the version to 1.3 while we're at it.

This might impact #216

Changing the behavior of decode_data will likely break things.
I'll defer this to the "2.0" Milestone.

repo: aio-libs/aiosmtpd


text:
Lodash dependency overwrites Window._

Enzyme uses Lodash version 4.13.1 as a dependency.
This version of Lodash overwrites Window._ which I use for underscore.
As a result, any webapp that expects Window._ to be something else will break if Enzyme is imported.
Lodash versions 4.14.0 and onward have solved this issue, but Enzyme uses the older version:
https://github.com/lodash/lodash/issues/1798
Can you please upgrade to a newer version of Lodash to resolve this issue?

Enzyme uses Lodash version 4.13.1 as a dependency.

Enzyme depends on version ^4.15.0. Are you using an older version of enzyme?

Yeah, it turns out that the version of Enzyme I got when I npm installed it yesterday was an old version. I installed it using the github:airbnb/enzyme and it seems up to date.

Thanks for verifying! The latest version is available on npm too, so it should install from there just fine. But since this doesn't seem to be an issue with enzyme, I'm going to close this out 👍

I just reinstalled with npm and these are dependencies i got from the package.json file:
"dependencies": {     "cheerio": "^0.20.0",     "is-subset": "^0.1.1",     "lodash": "^4.13.1",     "object-is": "^1.0.1",     "object.assign": "^4.0.3",     "object.values": "^1.0.3"   },
some of these are older versions compared to the package.json on github.
Although, the version number still says "version": "2.4.1" maybe the version of enzyme on npm isn't exactly up to date.

@kushalk25 I just tested myself and you are totally right, looks like that dep update was made after we published 2.4.1. I'll keep this closed since it's resolved on master, but this should be fixed in the next release then.

Great! thanks for clearing that up.

It turns out this issue is due to a Webpack transform that's catered to end users and not libraries, like Lodash, that have AMD support. For the time being, Webpack recommends opting-out of their AMD parsing if you're running into issues.

authors: Aweary jdalton kushalk25

repo: airbnb/enzyme


text:
.children() are empty when a component doesn't wrap its children

I have a Localize component that is used with the app as its single child and provides context to it. The relevant part is:
class Localize extends React.Component {
  render() {
    return React.Children.only(this.props.children);
  }
}

When I mount this component and try to get .children(), I get nothing.
const children = mount(React.createElement(Localize, {}, childElement)).children();
// children.length === 0

I can get the wrapper for the child component if I do this:
const child = mount(React.createElement(Localize, {}, childElement))
  .find(childElement.type)
  .at(0);

When you say someComponent - children need to be Elements, not Components - can you share the code that initializes someComponent?

@ljharb Sorry, I see how that is misleading. I updated the description to clearly describe it as Element. It can be any Element, e.g.
 or <MyComponent ... /> where MyComponent extends React.Component.

Does this same thing happen with shallow, or only with mount?

I've just tested it with
    class Wrapper extends React.Component {
      render() {
        return React.Children.only(this.props.children);
      }
    }

    const wrapper = shallow(
      React.createElement(Wrapper, {}, React.createElement('div'))
    );

    expect(wrapper.children().length).toBe(1);

and it fails too (expects 1, gets 0). Just like when I use mount in place of shallow.

Does anyone have an update on this or any idea how we can fix it?

Related to #977?

@ljharb Yeah, looks #977 is a duplicate of this, though with a tad more extensive description.

I have very similar issue, also related to if component doesn't have a wrapping element.
const StepsComponent = function StepsComponent({ steps }) {
  return steps.map(function stepsMap(step) {
    if (step.src) {
      return ;
    }

    return step;
  });
};

const steps = [
  '123',
  'another simple string',
  { src: './src/to/img', alt: 'img alt' },
];
const wrapper = mount(<StepsComponent steps={steps} />);

// The following only returns the img elements, it doesn't return simple nodes, such as strings.
const elements = wrapper.children().getElements();

// Now if I try this for shallow rendering, it won't even proceed
const wrapper2 = shallow(<StepsComponent steps={steps} />);
// This throws the following error:
// ShallowWrapper::getNode() can only be called when wrapping one node
const elements2 = wrapper.children().getElements();

If I wrap my component into a div, such as:
const StepsComponent = function StepsComponent({ steps }) {
  return (

      { steps.map(function stepsMap(step) {
           if (step.src) {
             return ;
           }

           return step;
      }); }

  );
};

Using shallow rendering on such component and then calling wrapper.children().getElements() will output all children, however simple nodes are presented as null (but at least it indicates there are such nodes).

@c-emil you're using react 16? I think your issue is different, since StepsComponent renders an array. I believe you want #1213.

@ljharb Thanks for quick reply. Yes, I'm using react 16, I updated my comment to reflect that information. That's exactly the issue I'm referring to :) I missed that one, thanks! Even though I think it's related to both the issue you mentioned and this one since this one is also about not wrapped fragments, but author doesn't mention it explicitly. Should I rather add this comment to the issue you mentioned? It seems like it's not resolved either.

This issue long predates React 16, so I don't think it's related.

@ljharb Alright, it may not be after all. So do you think I should repost this comment to the issue you mentioned?

Yes, that'd be great, thanks. If you want to delete your comments here too that'd also be good :-)

I don't think this is still an issue in v3; please file a new issue if that's not the case.

authors: c-emil hon2a jantorestolsvik ljharb


text:
Make .exists take optional selector

This PR makes .exists optionally take a selector, in which case it will delegate to .find(selector).exists().

Thanks for the PR - I'm not sure if this complexity is worth adding to the API, since .exists(x) is simple sugar for .find(x).exists(). Can you elaborate on how this is helpful?

I'm not sure either, and I very much appreciate the lean API and the effort that went into keeping it lean, so I'm rather happy you're hesitating.
Here are some arguments, ordered from crappy to somewhat good, why I'd still like to see this change included in Enzyme;

Throwing .exists onto a  .find is a very common use case for it, so making that use case less clunky has some extra value.

The added complexity is rebated by the fact that we're just referring existing concepts  - "selectors" and .find - so the cognitive cost of the change is rather small.

It is easy to intuitively expect .exists to take an argument. It just reads so well, and that kind of .has functionality is very common in libraries in similar problem space, but Enzyme lacks this.

Making that misunderstanding is dangerous. In a recent project (with crappy tooling lacking static type checking) I added a test in the line of wrapper.exists(selector).should.be.true(). The test passed, but without protecting against what it was supposed to, and that ended up blowing up in my client's face. My bad, but to some extent I did feel let down by the API.

And that last sob story is of course what prompted this PR. Now the question is just whether the story is sad enough! :)

If exists threw an exception when it received an argument, would you still want this API?

Oh, very good question! Hmm. Not sure.
Preventing the misunderstanding was definitely my main intent, so if an error had saved me from blowing my client's face off I probably wouldn't have made this PR.
The crappy parts of the arguments still stand however, and I think my immediate reaction to an error saying "Exists doesn't take an argument" would be "well, why the hell not".
As a very unscientific and solitaire data point; in our current fledgling project we have 18 uses of .exists, and every single one of them is preceeded by a .find. This also matches my previous experiences. The current lack of a .has/.contains method is a bit of an eyebrow-raiser.
My answer to your question: Yes, I'd still want this proposed API, but not as badly, and would be happy to rework the PR to make .exists throw an error, if you feel the crappy arguments are too crappy. But shortening 100% of the tests using .exists does still have quite the appeal to me.

Ah, good catch adding the default arg!

source: gharchive/pull-request

authors: krawaller ljharb


text:
Can not manage dates in a newly added month

Hi, everyone!
That happens when you change a number of months via numberOfMonths props right in storybook, no matter how (via wrapper element with state or knobs).

You can't hover or click on those dates at all. Seems it only happens when you change a number of months in real time.
I managed to reproduce this error in your examples. Version: 12.5.1. The code I'm using:
/* eslint-disable react/no-unused-prop-types */
import React from 'react';
import PropTypes from 'prop-types';
import momentPropTypes from 'react-moment-proptypes';
import { forbidExtraProps } from 'airbnb-prop-types';
import moment from 'moment';
import omit from 'lodash/omit';

import DayPickerRangeController from '../src/components/DayPickerRangeController';

import ScrollableOrientationShape from '../src/shapes/ScrollableOrientationShape';

import { START_DATE, END_DATE, HORIZONTAL_ORIENTATION } from '../constants';
import isInclusivelyAfterDay from '../src/utils/isInclusivelyAfterDay';

const propTypes = forbidExtraProps({
  // example props for the demo
  autoFocusEndDate: PropTypes.bool,
  initialStartDate: momentPropTypes.momentObj,
  initialEndDate: momentPropTypes.momentObj,

  keepOpenOnDateSelect: PropTypes.bool,
  minimumNights: PropTypes.number,
  isOutsideRange: PropTypes.func,
  isDayBlocked: PropTypes.func,
  isDayHighlighted: PropTypes.func,

  // DayPicker props
  enableOutsideDays: PropTypes.bool,
  numberOfMonths: PropTypes.number,
  orientation: ScrollableOrientationShape,
  withPortal: PropTypes.bool,
  initialVisibleMonth: PropTypes.func,
  renderCalendarInfo: PropTypes.func,

  navPrev: PropTypes.node,
  navNext: PropTypes.node,

  onPrevMonthClick: PropTypes.func,
  onNextMonthClick: PropTypes.func,
  onOutsideClick: PropTypes.func,
  renderDay: PropTypes.func,

  // i18n
  monthFormat: PropTypes.string,

  isRTL: PropTypes.bool,
});

const defaultProps = {
  // example props for the demo
  autoFocusEndDate: false,
  initialStartDate: null,
  initialEndDate: null,

  // day presentation and interaction related props
  renderDay: null,
  minimumNights: 1,
  isDayBlocked: () => false,
  isOutsideRange: day => !isInclusivelyAfterDay(day, moment()),
  isDayHighlighted: () => false,
  enableOutsideDays: false,

  // calendar presentation and interaction related props
  orientation: HORIZONTAL_ORIENTATION,
  withPortal: false,
  initialVisibleMonth: null,
  numberOfMonths: 2,
  onOutsideClick() {},
  keepOpenOnDateSelect: false,
  renderCalendarInfo: null,
  isRTL: false,

  // navigation related props
  navPrev: null,
  navNext: null,
  onPrevMonthClick() {},
  onNextMonthClick() {},

  // internationalization
  monthFormat: 'MMMM YYYY',
};

class DayPickerRangeControllerWrapper extends React.Component {
  constructor(props) {
    super(props);

    this.state = {
      focusedInput: props.autoFocusEndDate ? END_DATE : START_DATE,
      startDate: props.initialStartDate,
      endDate: props.initialEndDate,
      numberOfMonths: 2,
    };

    this.onDatesChange = this.onDatesChange.bind(this);
    this.onFocusChange = this.onFocusChange.bind(this);
    this.handleChange = this.handleChange.bind(this);
  }

  onDatesChange({ startDate, endDate }) {
    this.setState({ startDate, endDate });
  }

  onFocusChange(focusedInput) {
    this.setState({
      // Force the focusedInput to always be truthy so that dates are always selectable
      focusedInput: !focusedInput ? START_DATE : focusedInput,
    });
  }

  handleChange(event) {
    this.setState({
      numberOfMonths: Number(event.target.value),
    });
  }

  render() {
    const { showInputs } = this.props;
    const { focusedInput, startDate, endDate } = this.state;

    const props = omit(this.props, [
      'autoFocus',
      'autoFocusEndDate',
      'initialStartDate',
      'initialEndDate',
    ]);

    const startDateString = startDate && startDate.format('YYYY-MM-DD');
    const endDateString = endDate && endDate.format('YYYY-MM-DD');

    return (

        {showInputs &&

            <input type="text" name="start date" value={startDateString} readOnly />
            <input type="text" name="end date" value={endDateString} readOnly />

        }
        <input type="number" value={this.state.numberOfMonths} onChange={this.handleChange} />

        <DayPickerRangeController
          {...props}
          numberOfMonths={this.state.numberOfMonths}
          onDatesChange={this.onDatesChange}
          onFocusChange={this.onFocusChange}
          focusedInput={focusedInput}
          startDate={startDate}
          endDate={endDate}
        />

    );
  }
}

DayPickerRangeControllerWrapper.propTypes = propTypes;
DayPickerRangeControllerWrapper.defaultProps = defaultProps;

export default DayPickerRangeControllerWrapper;

error text: Uncaught TypeError: Cannot read property '2017-12-01' of undefined
I found a closed issue with same error, but different problem, that looks like has been solved, but I will share it with you anyway in case it can help you: https://github.com/airbnb/react-dates/issues/569

Thank you for including your code! I believe the issue is that the componentWillReceiveProps method of the DayPickerRangeController does not expand the state based on a change in numberOfMonths.
If you look at the code here - https://github.com/airbnb/react-dates/blob/master/src/components/DayPickerRangeController.jsx#L217-L234, it looks like it would require a change in focus (from hidden to visible) to rerun the state generation code.
I think this makes sense for initialVisibleMonth but not for the other two props. I will put up a PR with the fix.

Note that in your gif the height also doesn't expand for this case so we'll need to cover that case as well.

This should be addressed in v12.6.0

Thank you! :D

authors: ArtyomResh majapw

repo: airbnb/react-dates


text:
Update to babel 7

Updates react-dates to babel 7.
Closes #1389. Closes #1346. Closes #1416. Closes #1390. Closes #1377. Closes #1378.

Coverage decreased (-0.2%) to 84.792% when pulling 4ec3ddacad9cd7662c11b2e5a45f1e07b0d80bce on babel-7 into b1dd928a4be1976246a2d867cdaa616017aa19b6 on master.

This update seems to break storybook locally, as it can't find babel-core (replaced with @babel/core)
Opened issue here https://github.com/airbnb/react-dates/issues/1429

authors: coveralls ljharb pedroabreu


text:
[launcher] Allow classic link to associate VPC security groups by name

Add a new security_groups field to classic_link, which should contain an array of VPC security groups to associate with a classic instance. If specified, the security group names are resolved to their ids in the given VPC.

LGTM

authors: darnaut noggi

repo: airbnb/stemcell


text:
Make requestID optional for issue #447

to: @airbnb/streamalert-maintainers
cc:
size: small
resolves #447

Coverage remained the same at 95.687% when pulling d357eec5e95e6a1d29f06a0ccf482a19d7011606 on 0xdabbad00:spiper-make_requestID_optional into 71a51cf322e83954d0b72a761147c7b4dab4eb28 on airbnb:master.

repo: airbnb/streamalert


text:
Changes 3.0.0+ behavior to by default include SQS prefix

to: @ryandeivert @chunyong-lin @blakemotl
cc: @airbnb/streamalert-maintainers
related to: #885
Background
In #960 I added the classifier SQS resource prefix as an optional variable. The default behavior was "you must specify this or I will error".
As promised, in 3.0.0+, the default behavior now uses SQS resource prefix by default.

Coverage remained the same at 96.616% when pulling 8ab098ea43e8009623ac9e20c4b086736096105f on dw--sqsprefix into a078b4a5d5cc0d473bb1644eed91b4ab89f4d3b9 on release-3-0-0.

authors: Ryxias coveralls


text:
go get error

I run the go get github.com/airbusgeo/godal, and got the follow error.
....
/usr/local/Cellar/gdal/3.2.0_1/include/ogr_geometry.h:1802:34: warning: 'override' keyword is a C++11 extension [-Wc++11-extensions]
/usr/local/Cellar/gdal/3.2.0_1/include/ogr_geometry.h:1711:34: error: use of undeclared identifier 'oCC'
/usr/local/Cellar/gdal/3.2.0_1/include/ogr_geometry.h:1713:32: error: use of undeclared identifier 'oCC'
/usr/local/Cellar/gdal/3.2.0_1/include/ogr_geometry.h:1717:53: error: use of undeclared identifier 'oCC'
/usr/local/Cellar/gdal/3.2.0_1/include/ogr_geometry.h:1719:51: error: use of undeclared identifier 'oCC'
/usr/local/Cellar/gdal/3.2.0_1/include/ogr_geometry.h:1880:24: error: function definition does not declare parameters
/usr/local/Cellar/gdal/3.2.0_1/include/ogr_geometry.h:1883:15: warning: 'override' keyword is a C++11 extension [-Wc++11-extensions]
/usr/local/Cellar/gdal/3.2.0_1/include/ogr_geometry.h:1885:15: warning: 'override' keyword is a C++11 extension [-Wc++11-extensions]
/usr/local/Cellar/gdal/3.2.0_1/include/ogr_geometry.h:1893:24: warning: 'override' keyword is a C++11 extension [-Wc++11-extensions]
/usr/local/Cellar/gdal/3.2.0_1/include/ogr_geometry.h:1914:49: warning: 'override' keyword is a C++11 extension [-Wc++11-extensions]
....
fatal error: too many errors emitted, stopping now [-ferror-limit=]

fixed by:
go env -w CGO_CXXFLAGS=-std=c++11
```

What compiler version are you using? I consider this an issue, correct compiler flags should be set by the godal build

authors: sshuair tbonfort

repo: airbusgeo/godal


text:
Is it safe to remove asterisks from keywords in NCBI BioSample templates?

The mandatory keywords/column headings in the NCBI BioSample template are usually prefixed with an asterisk. Those were removed in 5d75d77af9aa33ed8d83e9dc568507809ae69c67. @ahmadchan is it save to do this or could this break the submission process?

No, it will not disturb the regular submission process. Here are the example that I have tested and these are without *   https://github.com/airr-community/airr-standards/tree/master/NCBI_implementation/Filled_NCBI_Templates. Moreover, I have added new examples in the NCBI filled templates in the development branch.

authors: BusseChristian ahmadchan

repo: airr-community/airr-standards


text:
Question: Tokenizer used for RoBERTa model?

I'm trying to integrate Vokenization with BERTScore and I'd like to get clarification on which tokenizer is being used for the pretrained RoBERTa + VLM model. Is it roberta-base or bert-base-uncased?

Thanks. I am using bert-base-uncased for  BERT + VLM (on Wiki) here, and use roberta-base for RoBERTa + VLM (on Wiki).

Perfect, thanks for the quick reply!

authors: FelixLabelle airsplay

repo: airsplay/vokenization


text:
如何在tabbar-item 使用svg图标

<tabbar style="position: fixed;z-index:400;">
  <tabbar-item selected link="/">

    总览
  </tabbar-item >
  <tabbar-item link="/store">

    店铺360
  </tabbar-item>
  <tabbar-item  link="/dataAnalyze">

    数据分析
  </tabbar-item>
  <tabbar-item link="/personal">

    我的
  </tabbar-item>
</tabbar>

authors: liguChen zhoutengshen

repo: airyland/vux


text:
swiper组件在左右拖动时，可以不可以禁止页面的上下拖动

swiper组件在左右拖动时，可以不可以禁止页面的上下拖动

好像没有这么设计的吧，使用场景是什么呢

好像没有这么设计的吧，使用场景是什么呢

有呀，当你拖动广告左右切换时，同时上下滚动的话，体验好差，你试一试淘宝app的广告

拖动广告左右切换时，同时上下滚动

我想知道这个怎么做到。。。

页面强制 overflow: hidden;

js控制左右切换时，禁止默认的操作

这个应该是自己控制比较好

问题是自己改需要改源码

@LiangFuzhi 你可以提个pr来瞅瞅

我这里 swiper 左右拖动拖动时 就是不能上下拖动

@ph2-cst 如何实现的？

@lichunqiang 我的意思我这里的swiper就是这样的 vux原本的

咦... @LiangFuzhi  where are u

@lichunqiang @LiangFuzhi 我确认了一遍 android微信内置浏览器, uc, android chrome 是这样
"vuex": "^0.6.3"
"vux": "0.0.111"

<template>

      <vux-swiper v-ref:swiper :list="sliderList" :height="180" v-show="sliderList&&sliderList.length"></vux-swiper>

      <vux-tab :line-width="1" v-show="tabList&&tabList.length">
        <vux-tab-item :selected="$index === selectedTabIndex" v-for="tab in tabList"
                      @click="selectedTabIndex = $index">
          {{tab}}
        </vux-tab-item>
      </vux-tab>

        <vux-panel :list="list" :type="type" v-on:on-click-item="handleListItemClick"></vux-panel>

</template>

呃，vux@0.0.111应该有问题，  或者你该试试0.1.2的，0.1.2的修正了

@unclay 这样啊 不过算了 跑得好好的

authors: LiangFuzhi fundon lichunqiang ph2-cst unclay


text:
Add incompatible_no_build_defs_pkg

Test with
bazel build scripts/packages/fedora:bazel
--experimental_build_setting_api
--//tools/build_defs/pkg:incompatible_no_build_defs_pkg=True
bazel build scripts/packages/fedora:bazel
--experimental_build_setting_api \

wrong pr

repo: aiuto/bazel


text:
Make "Profile" field in QED S3 config panel an optional field

Change "Profile" field in QED S3 config panel from a required field to an optional field. Omitting a profile might allow usage of user's running EC2 instance permission or user's "default" AWS profile.

Fixed in f4c71e822580214845bb973d16108062510c8fe9

Closing as complete

authors: aivazis jeffreypon

repo: aivazis/qed


text:
Replacing outdated 'Create Service` screenshot

What changed, and why it matters
Per, replaced the outdated 'Create Service' screenshot with a recent one that shows the new summary section as well as opensearch.
Testing
Original URL: https://developer.aiven.io/docs/platform/howto/create_new_service.html
Screenshot of the page when locally run:

Thanks for the PR, @dewan-ahmed! I will leave this comment for you so next time you know it. If you write Fix <Issue link> then GitHub automatically links the issue to your PR and closes it. So you can always link it like this :)

authors: dewan-ahmed laysauchoa

repo: aiven/devportal


text:
chore(release): v4.30.0

Release v4.30.0

Running tests on main (triggered it before I thought of a release).

repo: aiven/terraform-provider-aiven


text:
bind: address already in use

Problem: Starting dotdocker-dnsmasq step fails with:  (HTTP code 500) server error - driver failed progarmming extenral connectivity on endpoint dotdocker-dnsmasq" ... "Error starting userland proxy: listen tcp 0.0.0.0:53: bind: address already in use
Reproduced by running dotdocker start
Expected behavior is that dotdocker will start.
See attached screenshot.

Docker and dotdocker have both been stopped and restarted.
dotdocker -V returns 1.4.2.
dnscrypt is bound to port 53.

Now it's working after the latest restarting of docker, dotdocker restart, and sudo dotdocker start

Resolve this problem by:

installing a new version (1.4.2) that doesn't bind to port 53;
running dotdocker stop after the new version is installed (because this will remove the old container that was left dangling);
run dotdocker start

repo: aj-may/dotdocker


text:
Make Featured-article and article page working

About Featured-article Page.
as data is emitted already about all articles, let's make Featured-article Page working. Data will be passed to featured-article component and then Open it via URL, Considering Mobile First Approach.

I'm working on that next Thursday I've already done the CSS Can you pick something else

Try to pick something completely different from what I'm working on. Like details page

repo: ajitsinghkaler/devto-clone


text:
🛑 NV Energy is down

In 066b004, NV Energy (https://www.nvenergy.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NV Energy is back up in 696103d after 5 minutes.

repo: ajshastri/musical-waffle


text:
skip super.stop when loop

このpull requestが解決する内容
offset+duration の値が音声の長さを上回るオーディオアセットをループ再生した場合、
2週目以降はオーディオを停止できなくなる現象を修正します。
破壊的な変更を含んでいるか?

なし

PR 引き継ぎ。動作確認用コンテンツを作成し、ループ再生2週目以降に任意のタイミングで停止できる事を確認。version と CHANGELOG を変更。

repo: akashic-games/pdi-browser


text:
AKShare 接口问题报告

从上交所拿数据的接口，http://query.sse.com.cn/sseQuery/commonQuery.do，实测应该最大只支持返回2000行。
目前 akshare 的处理方法应是 pageHelp.pageSize 设置到10000行，暂时我使用还没遇到问题，但是这个处理是有风险的。

从上交所拿数据的接口，http://query.sse.com.cn/sseQuery/commonQuery.do，实测应该最大只支持返回2000行。 目前 akshare 的处理方法应是 pageHelp.pageSize 设置到10000行，暂时我使用还没遇到问题，但是这个处理是有风险的。

get it

repo: akfamily/akshare


text:
Install/audit gives some warnings

yarn install gives some info and warning messages, would be nice to know we're starting with no warnings
info fsevents@2.3.2: The platform "win32" is incompatible with this module.
info "fsevents@2.3.2" is an optional dependency and failed compatibility check. Excluding it from installation.
info fsevents@1.2.13: The platform "win32" is incompatible with this module.
info "fsevents@1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "@vue/cli-plugin-unit-jest > vue-jest@3.0.7" has incorrect peer dependency "vue@^2.x".
warning "@vue/cli-plugin-unit-jest > vue-jest@3.0.7" has unmet peer dependency "vue-template-compiler@^2.x".
warning " > vue-jest@5.0.0-alpha.10" has unmet peer dependency "@babel/core@7.x".
warning " > vue-jest@5.0.0-alpha.10" has unmet peer dependency "babel-jest@>= 24 < 27".
warning " > vue-jest@5.0.0-alpha.10" has unmet peer dependency "jest@>= 24 < 27 ".
Also yarn audit reports
60 vulnerabilities found - Packages audited: 1762
Severity: 57 Moderate | 3 High

@kerrpeter  the 3 high  vulnerabilities  are from vue-cli ,
https://snyk.io/test/npm/@vue/cli
https://github.com/vuejs/vue-cli/issues/6375 , i have used latest stable version of the package , since its under devDependencies , we can ignore , it will not affect production . I will update the package when ever the stable version is ready

authors: akhi-ninja kerrpeter


text:
clean up argv options

many options are either missing, named something else or not assigned to anything. And the fugliness of the code!!
perhaps using a cache object to hold/store/transpose said items would help.

forgot about these changes.
From npinit readme:
Changes [WIP]
project name is now required else usage() is generated. see next entry for cavet
can enter npinit -d [options] for a dry run without entering a project name.
flag -n/--new gone. use "test" as project name to replicate initing a new test project.
test name generated is now "test-###" instead of "testproj###"
flag --addRemote replaced with --remote
flag --noRemote replaced with --no-remote
flag --noPush removed. determined automatically
flag --dry can also use single flag -d
flag --D changed to --dep (install Dependencies)
flag --d changed to --dev (install devDependencies)
verbose option added (--verbose). displays standard output from git init and npm install
using both options -rg or --repo --github generates a private repo only. private overrides public
if project name is "test" with option of --github then a private repo will only be generated. I am making the assumption that you will not call a public repo "test". You can over this by naming the project "test1" if you like.

directly related to #8

directly related to #7 as well

start working on this... d151f9875b139af7f1b306dc40b7f878d735d6c4

repo: akileez/test-npinit

license: ISC


text:
Implement Tune message

What this PR does
Add new message TunableConfig for grpc communication with server (TunableConfigReq & TunableConfigRep)
Add tune_config rpc call to Service Raft
Add TuneConfigInfo to core_message:req and core_message:rep to be able to query TunableConfig from RaftCore
Add tunable-config to lol-admin to query TuneConfigInfo
Rel
Fixes #57: Implement Tune message

We did these modifications livestreaming with @PierreZ it may be missing some stuff.
Please us know if anything is missing :slightly_smiling_face:

@fteychene Thank you for the PR.
The PR consists of reader side (TuneConfigInfo) and writer side (TunableConfig).
For the reader side, I think everything is perfect. But the writer side, I have two comments:

TunableConfigReq needs full set of fields to make a request but this isn't good for people who wants to change the config partially. (They typically wants to use builder-pattern) My thought on this is to change the fields to optional. I want you to fix this.

My initial thought on where to put TunableConfigReq was core_mesasge. My criteria on which to choose between gRPC proto or core_message is those which is of Raft in general is in gRPC and of lol specific is in core_message. Based on my criteria, TunableConfigReq should be placed in core_message. However, I think putting this message in proto isn't bad in this case because backward-compatibility offered by protobuf is more important here.

Btw, you name the reader side message "TuneConfig" instead of "TunableConfig", is this because you feel the word tunable is strange here? If this is just a mistake, please use the same word so to avoid confusion.
    TuneConfigInfo {
        compaction_delay_sec: u64,
        compaction_interval_sec: u64,
    }

Thanks @akiradeveloper
I updated the PR from your comments. I kept the TunableConfig proto message and service since it seems that the backward compatibility could be usefull. We could change it to be in core_message if needed, just let us know if we need to.
I updated the name of from TuneConfif to TunableConfig everywhere in the PR to be more consistent :+1:
The fields in TunableConfigReq are now optional and I added the flag in priotoc compilation to allow it.

authors: akiradeveloper fteychene

repo: akiradeveloper/lol


text:
Syntax highlighting in signature help

I don't know if signature help is the correct word, but I'm talking about this

if (sortedarray != null) {

}

So syntax highlighting like GitHub would be nice there

Hi :)
I've wanted to do this before, but I didn't know a good way to do it.
Ummm, how does Coc make this.
The UI doesn't get any valid information from Neovim about this additional information, so if we want to do it simply, we'll have to parse it out on the UI side and give it a color.
If there is a better way to do this, I'd like to implement it.

I mean, any markdown parser would work

repo: akiyosi/goneovim


text:
为什么总是报接口请求错误

如图

更新,然后用备用1号线路
https://github.com/akl7777777/bob-plugin-akl-chatgpt-free-translate/releases/tag/v1.2.4

我刚更新过最新版，确实用的也是备用一号线路但还是不行

我知道问题所在了，我试了试翻译模式没问题，是对话模式会报接口错误

对话模式我也试了没问题啊

那就不知道为什么了，我挂不挂梯子都不可以

那就不知道为什么了，我挂不挂梯子都不可以

等会我再加个新的

已加上,请更新

还是不行，大概是我这里的问题，我再检查一下吧

1.2.5版本，相同的报错。

这里的接口是对应的 URL 是什么呢？我应该如何设置代理？

我的也是这个问题诶，我翻译都不行都是弹那个，题主问题解决了么

免费线路偶尔拥堵,请更新最新版,切换其他线路尝试


text:
Bump castore to 1.0.3

Appreciate the package!
Bumping castore to 1.0.3, since the latest phoenix version is blocked:
Resolving Hex dependencies...
Resolution completed in 0.078s
Because "the lock" specifies castore 1.0.3 and every version of litestream depends on castore ~> 0.1.15, the lock is incompatible with litestream.
And because your app depends on the lock, no version of litestream is allowed.
So, because your app depends on litestream ~> 0.3.0, version solving failed.
** (Mix) Hex dependency resolution failed

Thanks for the contribution!

authors: akoutmos sourdoughdev

repo: akoutmos/litestream


text:
css: change signup button background color

change the bgcolor of the SignUp button thats defined in index.html

change the bg color to match with the application theme
theme colors are defined in css variables  (--primary)
✨ Feel free to add your own changes !
💬 drop a comment if you like to take up this issue, so i can assign it to you.

Can I work on this issue?

I would like to give it a try since I would like to Figur out how this works with issues on GitHub.

I would like to give it a try since I would like to Figur out how this works with issues on GitHub.

@Simon-H01 go on :+1:

repo: akshayitzme/cinlist


text:
PULL REQUESTS WILL BE MERGED

PULL REQUESTS WILL BE MERGED
Thankyou so much everyone for contributing in the repository.
As i am the only one to manage the repo so after some simple checks I will surely merge your pull request.
Happy Coding! and contributing to open source.
These contributions are really valuable.

issue#156  ,can you plz explain it ?

This is just to tell the contributors that all pr will be merged

repo: akshitagit/Python


text:
Override card on footer section

Description
Override card on footer section

When triggering the Iskcons Events, the page changes its route and directs me to this particular page. The problem lies with the card components overriding the footer section of that page.

Expected behavior:

The desired behavior is clear: the card component must remain within its assigned section without changing its size. This prevents a negative user experience and ensures the website appears attractive and enhances its beauty..

Actual behavior:

The issue is with the card components that are overriding the footer section of the page, creating a poor user experience.

Screenshots:

Additional Information:

[x] OS: [Windows]
[x] Browser [Chrome, Safari, Firefox, Microsoft Edge, Brave]

Additional:

[x] I am an Open Source Contributor in GSSOC'24

Allow me to work on this issue under GSSOC' 2024 @akshitagupta15june.


text:
Bug Alert: Site isn't responsive in mobile phone

hey can i work on this?

Yes you can

What breakpoint should i use?

Hey it seems like i would need to rework Almost the whole desktop code since tailwind only supports min width media queries. Would that be a problem?

Yes please work on it

so i will be using basic css if you dont mind

Is this good for the pet cards?

Is this Good?

Yes it is


text:
Various features

Major changes:

Added missing capacity check (resolves https://github.com/akuker/RASCSI/issues/192)
Unification of device types (resolves https://github.com/akuker/RASCSI/issues/181)
Removable media support with new SCRM type/.hdr extension (resolves https://github.com/akuker/RASCSI/issues/6)
Enriched PbOperation with PbDevice
Added PbImageFile, containing the image file name, size and read-only status. This information is useful for clients. In particular a UI client can prevent the user from starting useless operations by not giving the user a choice.
An operation can be executed not just for a single device but for a list of devices. An error status is returned with the first failing operation.
To a certain extent ProcessCmd() validates whether all commands there were passed are valid (dry run) before executing anything.
Added Device, PrimaryDevice (for SCSI primary commands), BlockDevice (for SCSI block device commands) classes (resolves https://github.com/akuker/RASCSI/issues/186)
The default image folder is ~/images, which is backwards compatible for the user pi, but more convenient for other users, which may not be able to access the /home/pi folder. (It might not even exist.)
Controllers and disks are not stored in arrays anymore but in vectors. This is a preparation for using maps, which will resolve issues with static controller/disk count limits.
Improved abstraction: ProcessCmd uses Device class instead of Disk class
The device name can be set (resolves https://github.com/akuker/RASCSI/issues/182)
The rascsi interface supports setting the default image folder (resolves https://github.com/akuker/RASCSI/issues/178)
Added PbDeviceDefinition in order to make more transparent which device data are sent from the server to the client and from the client to the server
DETACH supports optional "all" parameter in order to detach all devices with a single command
Use more standard C++ integer data types in os.h and format using C++ streams where printf format specifiers do not work. The sources now compile without warnings on arm64 and x64 platforms. (Partially resolves https://github.com/akuker/RASCSI/issues/126)
Logging should not depend on compiler flags, causing different behavior for debug and non-debug builds. For RaSCSI logging is not performance-critical and should always be available when a user needs it.
INFO is default log level
Manpage updates
Added support for .hdr images (type SCRM) to the web interface

@akuker Can you please review the list of major changes (only the list, not the actual code) above? I would like to ensure that you are fine with these changes now, in order to avoid major issues later in case something has to be reverted. The further I progress that harder it gets to revert changes made in the beginning.

@akuker It's time for my consolidated PR. I've been running tests (hard disk and CD-ROM devices) against my retro hardware, and so far have not found any issues.

@akuker It's time for my consolidated PR. I've been running tests (hard disk and CD-ROM devices) against my retro hardware, and so far have not found any issues.
Before reviewing please read my comments on the top of this PR.

Holy cow, @uweseimet !! You've been busy!! I looked through the list of changes you proposed and they look good. The only one I have a little concern with is the default images directory being ~/images. Since RaSCSI always runs as root, I don't think it will resolve to /home/pi/images. But, as long as the directory can be specified in the startup command, that shouldn't be a big problem.
Its going to take me a little while to review all of the changes, but I'll try to get on it as soon as I can.
Thank you for all of the awesome updates!

@akuker Regarding the image directory for the root user we can simply add a special rule that sets the image to the home folder of the PI user. I can do this later, it's not a big deal.

@akuker I changed the default image folder handling, so that for the root user the default folder is /home/pi/images.

@akuker Any news on the review of this PR? @rdmark and I tested hard disks, CD-ROMs and Daynaport on various Macs and my Atari. After fixing a number of 64 bit issues rascsi now also works on 64 bit Ubuntu and 64 bit Raspberry Pi OS beta.

authors: akuker uweseimet

repo: akuker/RASCSI


text:
No proper documentation to add custom svg icons

I want to add my customs SVG icons. But, I cannot find any proper guide or documentation to do so.
For example Whatsapp, Instagram etc icons missing

This repo is not maintained anymore

repo: akveo/eva-icons


text:
Expo

💬 Question
Any updates for expo or how can i build this on windows ?
UI Kitten and Eva version
LATEST

@samuhay https://github.com/akveo/kittenTricks/blob/master/DEV_DOCS.md#running

authors: artyorsh samuhay

repo: akveo/kittenTricks


text:
No value accessor for form control with unspecified name attribute

TemperatureComponent.html:11
ERROR Error: No value accessor for form control with unspecified name attribute
at _throwError (forms.js:2094)
at setUpControl (forms.js:2004)
at NgModel.push../node_modules/@angular/forms/fesm5/forms.js.NgModel._setUpStandalone (forms.js:4732)
at NgModel.push../node_modules/@angular/forms/fesm5/forms.js.NgModel._setUpControl (forms.js:4719)
at NgModel.push../node_modules/@angular/forms/fesm5/forms.js.NgModel.ngOnChanges (forms.js:4649)
at checkAndUpdateDirectiveInline (core.js:20661)
at checkAndUpdateNodeInline (core.js:21929)
at checkAndUpdateNode (core.js:21891)
at debugCheckAndUpdateNode (core.js:22525)
at debugCheckDirectivesFn (core.js:22485)

Hi @xuanhungptithcm. Thanks for reporting. Please provide more details.
I don't see any errors on the latest master.

authors: xuanhungptithcm yggg

repo: akveo/ngx-admin


text:
Improve user interface

Fixes #159.

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

Project coverage is 88.15%. Comparing base (69932f1) to head (b488761).

Files
Patch %
Lines

autoemulate/compare.py
94.73%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #195      +/-   ##
==========================================
+ Coverage   88.09%   88.15%   +0.06%
==========================================
  Files          44       44
  Lines        2083     2102      +19
==========================================
+ Hits         1835     1853      +18
- Misses        248      249       +1

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

Two high level things:

Could we put this into a separate module to keep compare clean?
What would be great eventually (though no need for this now if you're tight on time) is to check whether autoemulate is run in a notebook and if so display the table with display(HTML(df.to_html())) from from IPython.display, which looks a bit nicer.

Do you mean to move it to, say, utils.py? I was thinking, as it pertains to the class specifically, it makes sense to have it as a method of the compare.AutoEmulate class?

This sounds like a great idea. I haven't found a super way of checking whether the script is run in a notebook or not..
I have seen two different versions of trying to resolve it (see this source for instance) -- any idea which ones is preferrable?

try:
    __IPYTHON__
    _in_ipython_session = True
except NameError:
    _in_ipython_session = False

try:
    from IPython import get_ipython
    ip = get_ipython()
    if ip is None:
            # we have IPython installed but not running from IPython
            return False
        else:
            from IPython.core.interactiveshell import InteractiveShell
            format = InteractiveShell.instance().display_formatter.format
            if len(format(_checkhtml, include="text/html")[0]):
                # TODO: need to check for qtconsole here!
                return True
            else:
                return False
    except:
        # We do not even have IPython installed
        return False

Two high level things:

Could we put this into a separate module to keep compare clean?
What would be great eventually (though no need for this now if you're tight on time) is to check whether autoemulate is run in a notebook and if so display the table with display(HTML(df.to_html())) from from IPython.display, which looks a bit nicer.

Do you mean to move it to, say, utils.py? I was thinking, as it pertains to the class specifically, it makes sense to have it as a method of the compare.AutoEmulate class?

This sounds like a great idea. I haven't found a super way of checking whether the script is run in a notebook or not..
I have seen two different versions of trying to resolve it (see this source for instance) -- any idea which ones is preferrable?
try:
    __IPYTHON__
    _in_ipython_session = True
except NameError:
    _in_ipython_session = False

try:
    from IPython import get_ipython
    ip = get_ipython()
    if ip is None:
            # we have IPython installed but not running from IPython
            return False
        else:
            from IPython.core.interactiveshell import InteractiveShell
            format = InteractiveShell.instance().display_formatter.format
            if len(format(_checkhtml, include="text/html")[0]):
                # TODO: need to check for qtconsole here!
                return True
            else:
                return False
    except:
        # We do not even have IPython installed
        return False

Ah sorry, I wasn't very clear. I think it's good to have it as a autoemulate.compare method, but I'd still put the majority of code in a separate module (say pretty_printing.py or so), and then import _print_setup for the autoemulate.compare print_setup method. This is just so that autoemulate.compare doesn't become too big with all it's methods.
Good question with the checking for whether it's run in a notebook. I couldn't find a super clear answer either. I'll have a closer look tomorrow, but both versions seem to work.

Fixed the high-level (1) above in https://github.com/alan-turing-institute/autoemulate/pull/195/commits/6dab835c6bf949bfbe151adc305cdb10271be535

Fixed (2) in https://github.com/alan-turing-institute/autoemulate/pull/195/commits/daec70f5b742868c240c24424f3860c575101188

OK @mastoffel I think that's all the stuff addressed! Check out the branch now :)

repo: alan-turing-institute/autoemulate


text:
[DOC] update core developers

The core developer list docs/source/about/team should be updated:

Ryan Kuhns @RNKuhns has left and is inactive
Patrick Schäfer @patrickzib has joined core developers

Core developers should also be ordered alphabetically by first name, then last name.

Can I work on this?

Sure :) And thank you!

authors: fkiraly patrickzib sumit-158

repo: alan-turing-institute/sktime


text:
CI exchange purge failing with connection reset by peer error

Some recent CI purge runs have failed with connection reset by peer errors when trying to remove test data. The failures have been intermittent and subsequent attempts have succeeded
Right now mostly just monitoring the situation, we can find and push a fix later on if this becomes a consistent issue

closing since this seems to have mostly gone away

repo: alcionai/corso


text:
Wrong events offset

The height of the event gets a higher offset the lower it is.

I'm using  @aldabil/react-scheduler@2.9.2

I am facing the Same issues, Please Help me in this,
Thanks in advance

@kelf47 @kapilsahitya can you reproduce the bug on https://codesandbox.io/ ?

Hey
This seems to be like #208
feel free to reopen if you think its still an issue

license: Unlicense


text:
Removing array items in the form does not remove hidden input from the dom

Hi Aldeed,
Didn't find this reported as an issue yet, maybe I did not look properly enough...
Maybe this is not a bug but a feature, if so, I don't understand:
When array items are removed from the form (tested with QuickForm only), the hidden input elements are not removed from the DOM. That means, that adding and deleting array items increases the number of hidden input items in the DOM. I know, there's no need to do so, but (sometimes) users are silly.
After some adds/removes it looks like the following:
<form id="insertContactPersonForm" class="grey lighten-5 niyu-panel-narrow" novalidate="novalidate">
  ...

Titel ?

      <input type="hidden" name="contactPerson.titles.0" data-schema-key="contactPerson.titles.0" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.1" data-schema-key="contactPerson.titles.1" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.2" data-schema-key="contactPerson.titles.2" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.3" data-schema-key="contactPerson.titles.3" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.4" data-schema-key="contactPerson.titles.4" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.5" data-schema-key="contactPerson.titles.5" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.6" data-schema-key="contactPerson.titles.6" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.7" data-schema-key="contactPerson.titles.7" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.8" data-schema-key="contactPerson.titles.8" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.9" data-schema-key="contactPerson.titles.9" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.10" data-schema-key="contactPerson.titles.10" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.11" data-schema-key="contactPerson.titles.11" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.12" data-schema-key="contactPerson.titles.12" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.13" data-schema-key="contactPerson.titles.13" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.14" data-schema-key="contactPerson.titles.14" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.15" data-schema-key="contactPerson.titles.15" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.16" data-schema-key="contactPerson.titles.16" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.17" data-schema-key="contactPerson.titles.17" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.18" data-schema-key="contactPerson.titles.18" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.19" data-schema-key="contactPerson.titles.19" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.20" data-schema-key="contactPerson.titles.20" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.21" data-schema-key="contactPerson.titles.21" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.22" data-schema-key="contactPerson.titles.22" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.23" data-schema-key="contactPerson.titles.23" data-null-value="true">
      <input type="hidden" name="contactPerson.titles.24" data-schema-key="contactPerson.titles.24" data-null-value="true">

        <button type="button" class="btn btn-primary autoform-add-item" data-autoform-field="contactPerson.titles"></button>

  ...

Does this make sense?
Have Fun!

This is similar to an issue I have been seeing, where an array of objects includes nulll values, when in fact it should just remove them

Thanks, I'll try what you proposed.

Experiencing the same behaviour. Gives problems when using css selectors with sibling selector.
.form-group + .form-group {
    //using this kind of selectors is impossible
}

<fieldset>
    <input type="hidden" name="answers.0" data-schema-key="answers.0" data-null-value="true">
    <input type="hidden" name="answers.1" data-schema-key="answers.1" data-null-value="true">
    <input type="hidden" name="answers.2" data-schema-key="answers.2" data-null-value="true">

        <input type="text" placeholder="Answer text" name="answers.3" label="false" data-schema-key="answers.3">

    <input type="hidden" name="answers.4" data-schema-key="answers.4" data-null-value="true">
    <input type="hidden" name="answers.5" data-schema-key="answers.5" data-null-value="true">

        <input type="text" placeholder="Answer text" name="answers.6" label="false" data-schema-key="answers.6">

    <button type="button" class="button autoform-add-item" data-autoform-field="answers">Add answer</button>
</fieldset>

Unless you use your own custom templates probably which is easy enough once you figure it out.  Will have to ferret an example if it helps.

Creating a custom template is not a problem indeed. I'll probably work around this problem. However the hidden input fields should probably not be there and are polluting the dom. Maybe @aldeed can help out here?

This behavior is needed in some cases for update forms to ensure that we remove the correct array items. It's possible we can ensure that we only ever update entire arrays and then keep things simpler, but I need to look back at the various use cases this was attempting to handle.

authors: aldeed harryhurry st3phan vincro

repo: aldeed/meteor-autoform


text:
[5.1.2] AutoForm.getValidationContext().isValid() not reactive.

After upgrading to AutoForm 5.1.2, the isValid() method of a form's validation context doesn't seem to be reactive anymore. If I use simple schema to get the context however, it works as expected.
Template.myTemplate.helpers({
  isValid: function() {
    // var context = AutoForm.getValidationContext().isValid(); // only returns on render, isn't re-run reactively.
    return Collection.simpleSchema().namedContext('form-id').isValid(); // works as expected.
  }
});

Note that AutoForm.getValidationContext() does return the correct validation context.
Also, this throws an error AutoForm.getValidationContext('form-id'); if run from a template helper. The documentation still states the form id parameter is mandatory.
Exception in template helper: Error: No form with ID form-id is currently rendered. If this call originated from within a template event or helper, you should call without passing a formId to avoid seeing this error

This is basically the same as the issue I just opened: #877

Just stumbled upon the same issue. +1 to get it solved.

It should work as long as you do AutoForm.getValidationContext('form-id').isValid()

Fixed to work without passing the formId argument in 5.8.1

authors: Pagebakers aadamsx aldeed thebarty


text:
Publish is being ignored

Hi,
I published my Collection this:
Meteor.publish("userBooks", function () {    return Links.find( {field: "value"); });
But Tabular Table is ignoring this filter from publish. Is it correct? Thanks.

I am understanding which Tabular create a publish for collection with all data. Is it? Then I cant use a publish mine with filters, right? I have to use selector. My mind is right ?

repo: aldeed/meteor-tabular


text:
🛑 Nitter is down

In 5e8df6d, Nitter (https://nitter.alefvanoon.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nitter is back up in e816bb7.

repo: alefvanoon/Status


text:
Resolve Namespace provision with helm

Through further use of helm, it was found that the recommended way to provide a helm chart is without the namespace predefined so that the user has an easier time specifying their own namespace to deploy resources to.
For this, all resources have had their namespace changed to the .Release.Namespace version which is provided on install.
The release process will now create the template with a provided .Release.Namespace and also include the creation of the namespace.
Unfortunately, helm doesn't like having you create a namespace and wants to do it itself, so the release of the package will first delete the namespace.yaml then package. And the README has been updated to show full command usage with specifying a namespace and creating it on install.

I will be releasing a new v1.1.0 after merging this pull request.

repo: alehechka/kube-secret-sync


text:
Add tooltip when hovering title

Adds a little tooltip when hovering grid card (as the grid title is blocked by absolute inset-0 z-20 rounded-xl span) or list title

Good catch! Seems I forgot something in the client tests to make pnpm to work so the build failing can be ignored.

authors: alessandrojean ghostbear

repo: alessandrojean/tankobon


text:
Lighthouse

https://www.npmjs.com/package/lighthouse
https://github.com/GoogleChrome/lighthouse

npm install -g lighthouse
# NOTE: specifying an output path with multiple formats ignores your specified extension for *ALL* formats
lighthouse --output json --output html --output-path ./myfile.json
# saves `./myfile.report.json` and `./myfile.report.html`

https://www.npmjs.com/package/lighthouse-ci

https://github.com/andreasonny83/lighthouse-ci

https://www.npmjs.com/package/@cypress-audit/lighthouse

https://github.com/mfrachet/cypress-audit

https://github.com/GoogleChrome/lighthouse-ci

https://github.com/treosh/lighthouse-ci-action

https://github.com/manrueda/lighthouse-report-action

Example: https://github.com/wyze/wyze.github.io/blob/d15f368b665daaef736a8e9877dda9eb8073ce1d/.github/workflows/lighthouse.yml

authors: AlexHedley alex-hedley

repo: alex-hedley/react-ts-vite-example


text:
How to use relative paths for filename

Hi, I have a rst file:
.. argparse::
   :filename: ../config/system/run_utils/parse_args.py
   :func: parser
   :prog: run

which works properly on my Windows computer, but breaks on read the docs:
Traceback (most recent call last):
  File "/home/docs/checkouts/readthedocs.org/user_builds/ascent-docs/envs/latest/lib/python3.7/site-packages/sphinxarg/ext.py", line 469, in run
    f = open(self.options['filename'])
FileNotFoundError: [Errno 2] No such file or directory: '../config/system/run_utils/parse_args.py'

How can I add a relative path outside of the docs directory?
Thanks!

This repo is abandoned, but there is an actively mantained fork you should use: https://github.com/ashb/sphinx-argparse
@ashb Your fork does not have issuesgithubfeature enabled.You might wanna consider that. It's a default on forks I think.

@JOJ0 oh thanks! Issues turned on there now

I put it on that repo, thanks!

authors: JOJ0 ashb dmarshall-bing

repo: alex-rudakov/sphinx-argparse


text:
Use require() in electron main / preload

Describe the bug
I have refactored my app to use electron-vite, using svelte on the frontend. I like the streamlined configuration available through electron.vite.config.js.
My electron main and preload scripts currently use commonjs syntax, files have module.exports = {} and the main uses require() to load them.
It seems to me that electron-vite supports ESM style imports only.
I have set the outDir to dist/* and in dist/main/index.js only the main entry file can be found, without it's required files. I tried to add the vite-plugin-commonjs to main, but no success.
When in package.json the main is set to the built outDir index.js, the project fails to start as it can't find modules.
If possible, I would avoid refactoring to ESM now, as we have couple dependencies having cjs exports only.
Electron-Vite Version
1.0.14
Electron Version
18.3.15
Vite Version
3.1.8
Validations

[X] Follow the Code of Conduct.
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

@kkerti electron-vite supports pure CJS dependencies, the externalizePlugins will externalize all CJS dependencies that do not need to be bundled. For pure esm  dependencies, they will be bundled into CJS to support Electron. So you can write code in ESM syntax. But it also works if you use CJS syntax. In fact, there is no need to build for CJS.
For outDir,  check out https://evite.netlify.app/guide/build.html#output-dir

@kkerti This issue will be closed as there is nothing to do. If you have any other questions, please feel free to submit an issue.


text:
[metabug] OS platforms

[x] don't require root when not needed
[x] install into /opt
[x] universal paths generally (no /home/pi or /root/, ...)
[x] universal init files for all platforms
[x] rewrite the setup script

Last part of this fixed by #82.

repo: alexa-pi/AlexaPi


text:
Extend the repository to support new API's

Is your feature request related to a problem? Please describe.
Add new available API's to the package
Describe the solution you'd like
All API's are available in the package
Additional context
New API's are periodically added and should be added to the package

All publicAPI's supported as of today

repo: alexander-hagen/node-api-hitbtc


text:
Weird 500 Error

I have installed the integration via HACS and then via the Integrations page.  Tried to configure it the way I want, but then deleted and installed again with bare-minimum default configuration.  When it loads, it shows on the Integrations page as the following:
"Retrying setup: 500, message='Internal Server Error', url=URL('https://api.pirateweather.net/forecast/I'd be lying if I said I didn't do that religously. Its been a long week for sure! That info is definitley interesting to see though. Thanks!/XX.XXXXXXXXX,-XXX.XXXXXXXXX?units=si')"
All I entered was my API key, long/lat was entered automatically.  The only thing I changed was Round values to the nearest integer, but I even tried that without changing.

Have you tried again at all after the initial setup? If it's still not working then can you try querying the API in your browser to see if it has the same issue?
It could have been that there was an error with the API when you were trying to setup your HA integration and it has since resolved itself. I tested the API on my end and it worked without any issues.

I just tried it again after leaving it for a few hours.  Still the same weird 500 error.  If I go to https://dev.pirateweather.net/forecast/API_KEY/LAT,LONG?units=us, it works.
Just as a test, I removed the "-" from the LONG, and it worked.  It also put my location as China.  So maybe there's a bug with certain locations?

Hmmm, I just tried with a different lat/long to a different section of the city and it worked.  If I change it back to mine, I get the 500 error again.  I'll just use the working lat/long, as there isn't a huge difference in the weather between the two locations.  Just a weird bug.

@Spankythemusical I wonder if there's an issue with your current location that's causing an issue. I know you found a fix but I'd still recommend reaching out to @alexander0042 to see if he can figure anything out. His email address is api@alexanderrey.ca

Yes, exactly that! I use a regex parser to extract the locations and return the results, so from time to time something weird happens. If you're ok replying with the location in question, feel free to re-open here, otherwise shoot me an e-mail and I'll take a look!


text:
d3 not defined via npm/browserify use?

angular.js:12477 ReferenceError: d3 is not defined
at Object.51 (scale.coffee:2)
at s (_prelude.js:1)
at _prelude.js:1
at Object.50../scale.coffee (random.coffee:1)
at s (_prelude.js:1)
at _prelude.js:1
at Object.66.../../color/random.coffee (color.coffee:2)
at s (_prelude.js:1)
at _prelude.js:1
at Object.68../color.coffee (sort.coffee:2)(anonymous function) @ angular.js:12477(anonymous function) @ angular.js:9246Scope.$apply @ angular.js:16094bootstrapApply @ angular.js:1660invoke @ angular.js:4478doBootstrap @ angular.js:1658bootstrap @ angular.js:1678angularInit @ angular.js:1572(anonymous function) @ angular.js:28899trigger @ angular.js:3024eventHandler @ angular.js:3298

I'm going to move this over to #315, unless you feel this is separate

authors: danieldram davelandry


text:
[Not an issue] Commendation

I looked on your profile for a public e-mail or means of contacting you, but I could find none. I just wanted to let you know that this is the first Shapeless-based project that I've been able to understand just by reading its source. You have done a very good job in designing your codebase. I hope you continue to develop this project. 😄

Wow, thanks 😄 Glad it's been useful to you! (and that you took the time to say it :)

authors: Idyllei alexarchambault

repo: alexarchambault/scalacheck-shapeless