Handle build-files promise error & exit properly

Motivation
Fix #805
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Try with https://github.com/facebook/react-native-website, delete versioned_docs/version-0.5/removing-default-permissions.md from master.
Run docusaurus build
Before

After

Try with Docusaurus, delete first doc from versioned_docs version-1.0.11 and yarn build
Before

After

@endiliey @yangshun Should we release 1.3.1 given this and other fixes?

Yes we should! Would you like me to do it since you're on PTO? I can do it tonight.

I am on PTO starting Tuesday -- but you can still do it tonight, if you would like 👍 Just let me know.

Sweet! I love it when I come back to check on an issue, but a PR has already been sent, reviewed, and merged. <3

Ok I'll do it


More approximations enabled

Namely,

--mi_approximation_factor, a term that enables sub sampled estimation of relational space (this is mostly the bottleneck)

--min_support parametrization of min support for entropy estimators. This enables skipping computation where support for a value is too small. Default is at least 2, but higher values seems to yield similar results (this has to be further evaluated).

Added also printout of arguments for easier orientation.

@miha-jenko I'm thinking of closing this PR given the unexpected speed boost that renders it kind of obsolete. Wdyt


Replying/Forwarding a message and saving as draft does not show message immediately in messageGrid

fixed with #54


Added support rtl languages in HStackView + activation constrains by scope

Hello Sergey 👋

For Right-to-Left languages (Arabic and Hebrew) you need to change the direction of views in HStackView.
For example, UIStackView do it by default.

Activation constrains by scope is more efficient. Apple documentation says:

 /* Convenience method that activates each constraint
 in the contained array, in the same manner as setting active=YES.
 This is often more efficient than activating each constraint individually. */
@available(iOS 8.0, *)
open class func activate(_ constraints: [NSLayoutConstraint])

Hey! All looks reasonable. Thanks Alex 🙌


TS 3.7: unlike x is T, asserts x is T cannot close over generics defined in outer scopes

TypeScript Version:  3.7.0-dev.20191016

Search Terms:
asserts, asserts return, asserts higher order, asserts type, 2775
Code
function literal<T extends keyof any>(lit: T): {
    is(value: any): value is T
    assert(value: any): asserts value is T
} {
    return null as any; // implementation doesn't matter
}

const isHi = literal("hi")
const x: unknown = "test"

if (isHi.is(x)) {
    console.log(x) // x is correctly inferred to be 'hi' :)
}

isHi.assert(x); // error: Assertions require every name in the call target to be declared with an explicit type annotation.(2775)
console.log(x); // x should be inferred to be 'hi' here :(

Expected behavior:
No compile error, x is inferred to be "hi" on the last line.
Actual behavior:
Compile error on isHi.assert. Assertions require every name in the call target to be declared with an explicit type annotation.(2775)
Construction higher order type guards is possible without problem (as shown in the snippet). This mechanism used heavily in libraries like io-ts and mobx-state-tree.
However, when trying to extend the latter library with assertion functionality for more convenient control flow, we run into this issue.
We can build type.is properly, but not type.assert, although they seem to be needing the exact same type / depth of type analysis; if type guards can close over T, so should type assertions?
Playground Link: link
Related Issues:
#34523

This is, unfortunately, working as intended as per #33622, see #33580.  The issue is not about closing over generics, but about the fact that your isHi variable is not typed via explicit type annotation.  The error message says as much, I guess, but it is bewildering, and I expect you won't be the last person bewildered by it.  The fix is something like:
interface Lit<T extends keyof any> {
    is(value: any): value is T;
    assert(value: any): asserts value is T;
}

function literal<T extends keyof any>(lit: T): Lit<T> {
    return null as any;
}

const isHi: Lit<"hi"> = literal("hi")

Playground Link
in which you are forced to write out a type like Lit<"hi">.

This is clearly going to be a pain point with user-defined assertion functions once 3.7 is out of beta.  Is the current error message really the best we can do?  Anyone have any great ideas?  I was hoping the error would come with a "quick fix" that suggests some suitable annotation somewhere, but I guess that would be too hard to get right (if the compiler could always figure out what the annotation should be I guess the annotation wouldn't be necessary in the first place).

That last type annotation is exactly what I want to avoid.

Literal is the simplest example, for complex ones it would be really
hard for consumers of the API to know what to put there
That last type annotation will make it impossible for this system to
work OOTB in ts-checked Javascript files.

Op zo 20 okt. 2019 01:29 schreef Joe Calzaretta<EMAIL_ADDRESS>
This is, unfortunately, working as intended as per #33622
https://github.com/microsoft/TypeScript/pull/33622, see #33580
https://github.com/microsoft/TypeScript/issues/33580. The issue is not
about closing over generics, but about the fact that your isHi variable
is not typed via explicit type annotation. The error message says as much,
I guess, but it is bewildering, and I expect you won't be the last person
bewildered by it. The fix is something like:
interface Lit {
is(value: any): value is T;
assert(value: any): asserts value is T;
}
function literal(lit: T): Lit {
return null as any;
}
const isHi: Lit<"hi"> = literal("hi")
Playground Link
http://www.typescriptlang.org/play/?ts=3.7-Beta#code/JYOwLgpgTgZghgYwgAgDLDAHgCrIgD0hABMBnZAawgE8B7GZOEagPmQG8AoZH5YUgBQA3OABsArhABcjZgEoZIiSn7JsAbm684pUtDDCxkmU2oLGu-eSWS+5DZwC+nTjHEgEYYLRDJRGaDEcPEIIEnIqOgZTFgF-MBlsc3QsbDYuXmQoCDBxKF8QcVFRC1lqTWdOBB9SMDsACWAZFMwAIgALYFa2AF4-AKgxAQ6uuRdqkFrkfBl3ChBaAHdfPtbIWtaXYAYBfkaAOn4BfDk5Di0eCdJaUQh90VoAc2OzgHpX6btkaqhsz1FqHwQDBoNliMgwLRkAByTrQpxbUgHHR6KAGE6aKo1G53B7PDHId6fUjtWhFcEAIxUwNBEHBOhhcOQtCE0GQ7WgECAA
in which you are forced to write out a type like Lit<"hi">.
This is clearly going to be a pain point with user-defined assertion
functions once 3.7 is out of beta. Is the current error message really the
best we can do? Anyone have any great ideas? I was hoping the error would
come with a "quick fix" that suggests some suitable annotation somewhere,
but I guess that would be too hard to get right (if the compiler could
always figure out what the annotation should be I guess the annotation
wouldn't be necessary in the first place).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/TypeScript/issues/34596?email_source=notifications&email_token=AAN4NBDWWDKH4YGX36X4N63QPOQ6HA5CNFSM4JCQ6252YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBX7NSY#issuecomment-544208587,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN4NBDZJW7LRCUNMJFTEDTQPOQ6HANCNFSM4JCQ625Q
.

To elaborate a bit more, how this functionality in general is used, is like:
import { types } from "mylib"

const User = types.Object({
  name: types.string,
  tags: types.array(types.union(types.literal("happy", "sad")))
})

// Later
if (User.is(someData)) {
  // someData is correctly inferred to be of type { name: string, tags: ("happy" | "sad")[] }
}

This all works splendidly well for typeguards, however, forcing the user to type User explicitly to be able to make asserts as well, partially defeats the purpose of library, as these types get really large in practice (the demo above is still really small).
What is more, to add to the consistency (see snippet below), if assertion is extracted as utility function that receives the type as generic argument, it works fine. So it seems that in principle the TypeChecker in principle doesn't have any trouble checking this, but that there is just a hard limit (magic number) put in place somewhere?
type Guard<T> = { is(value: any): value is T }

function assert<T>(t: Guard<T>, value: any): asserts value is T {
    // something
}

assert(isHi, x)

console.log(x); // x is correctly as 'hi' over here

playground

What is more, to add to the inconsistency (see snippet below), if assertion is extracted as utility function that receives the type as generic argument, it works fine.

This is consistent in that assert has an explicit type signature. As @jcalz's says, polymorphism is orthogonal to the cause of the issue - though it does exacerbate to pain because instantiated generic types are usually harder to write explicit types for.

The issue here is that we need the information about the assertness of a function early enough in the compilation process to correctly construct the control flow graph. Later in the process, we can detect if this didn't happen, but can't really fix it without performing an unbounded number of passes. We warned that this would be confusing but everyone said to add the feature anyway 🙃
I think it would be tractable to produce a quick fix in many places, since we (should?) know the originating declaration, know how to write the type down (if possible) in the context of that declaration.

I don't really understand much of this but I tried this today and couldn't make it work. is the takeaway that assertions won't work with polymorphism?

Ran into this exact thing while trying to see how Superstruct could be made super useful for TypeScript and automatically infer the return types whenever people constructed validations.

@RyanCavanaugh I wanted to add a weird behavior that I encountered about this... It seems like there's a difference in this behavior across package boundaries.
For example, given package 'a' which creates an "asserter":
export interface Asserter<T> {
  assert(x: unknown): asserts x is T;
}

export const create = <T>(): Asserter<T> => null as any;
export const number = () => create<number>();
export const Number = number();

If you import it in package 'b' the assertion works only if you use the pre-defined asserter, and don't create a new one from the factory:
import { Number, number } from "a";

{
  const x: unknown = 42;
  Number.assert(x);
  x;
  // This one works fine, and `x` is known to be of type `number`.
}

{
  const x: unknown = 42;
  const N = number();
  N.assert(x);
  // (method) Asserter<number>.assert(x: unknown): asserts x is number
  // Assertions require every name in the call target to be declared with an
  // explicit type annotation.ts(2775)
  // index.ts(12, 9): 'N' is declared here.
  x;
}

Here's the reproduction as a repo to clone.
Even further, if you actually inline the logic from package 'a' as a file inside package 'b' and import it with './a', both of the examples will error.

I kind of assume this is "expected" given the internal limitations of how this feature is written, but externally it feels weird and adds confusion.
For an example of confusion in the wild, there's a library called runtypes which has added an .assert method to its validators, and currently it has this halfway-working behavior. For example:
import { Number, Array } from 'runtypes'

const ArrayOfNumbers = Array(Number)

Number.assert(x) // works!
ArrayOfNumbers.assert(x) // fails!

TWe can't really fix it without performing an unbounded number of passes. We warned that this would be confusing but everyone said to add the feature anyway 🙃

@RyanCavanaugh I won't pretend I fully understand what a "pass" is, but was it considered to "count" the number of "passes" and throw an error similar to the Type instantiation is excessively deep and possibly infinite if there are more than some reasonably limit? I'm not sure whether that would help, I don't know how many passes the examples in this issue would require, for example.

It's possible to workaround this in a strange way, by assigning the assertion function to itself, with a redundant type annotation. Example with io-ts:
import * as t from 'io-ts'
import {inspect} from 'util'

export const getAsserter = <A>(input: t.Type<A>) => (val: unknown): asserts val is A => {
  const decoded = input.decode(val)
  if (decoded._tag === 'Left') {
    throw Error(inspect(decoded))
  }
}

const _assert = getAsserter(t.type({foo: t.string}))
const assert: typeof _assert = _assert

export const printFoo = (x: unknown) => {
  console.log(x.foo) // error: Object is of type 'unknown'
  assert(x)
  console.log(x.foo) // ok: x now has type {foo: string}
}

👆 the above breaks if you remove the pointless-looking type annotation in const assert: typeof _assert = _assert.
Playground link


[Question] Is it possible to mock arbitrary imports?

I understand that I can mock vue plugins, such as vue-router or vuex; but how would I mock a module that is imported and called within a component? For example, many of my components call to a custom logger via a JS module (just called Log). How would I mock this, and include it in the mounted component definition, to see if the functions had been called (and prevent them actually logging)?
I had hoped I could do something like:
const Log = {
  error: jest.fn()
}

const component = mount(Component, {
  Log
})

in the same way you might mock $router 😄

That's not within the scope of vue-test-utils, because it depends on the test runner and build setup you are running your tests with.
For Jest, you can look here: https://facebook.github.io/jest/docs/en/manual-mocks.html
For karma/mocha+webpack, you would use inject-loader, which vue-loader can do for you: https://vue-loader.vuejs.org/en/workflow/testing-with-mocks.html

If Log is imported from another file you can use Jest manual mocks, if you're using Jest.
If not you could use babel-plugin-rewire, or inject-loader. I wrote a blog post on how to use those libraries—https://eddyerburgh.me/stub-file-dependencies-vue-unit-tests

@LinusBorg @eddyerburgh Thanks for the links and references, much appreciated


prims algorithm in c++[gsssoc21]

💥 Proposal
want to add this in neoalgo cplusplus ds
prims algorithm is a greedy algorithm that finds a minimum spanning tree for a weighted undirected graph
input: {
{5, 7, 85, 2, 1, 58, 45,1,7},
{54 , 0, 75, 9, 2, 46 ,17,4,5},
{63, 16, 0, 41, 66 , 48,36,48,84},
{7, 9, 5, 0,65, 1,3,87,59 },
{6, 72, 76, 75,48,95,49,46,47},
{19, 25,65,39,17,24,28,12,14},
{76,89,94,15,14,28,27,78,74},
{1,75,48,75,48,63,15,4,8},
{3,37,36,18,25,2,9,29,43}
};
output :Weight of ele, Edge of graph
1  0 - 4
1  0 - 7
2  0 - 3
1  3 - 5
3  3 - 6
5  3 - 2
7  0 - 1
5  1 - 8
time_complexity_O(ElogV) where v no of vertices and e no of edges
Have you read the Contributing Guidelines on Pull Requests?
yes

/assign


uint256_t: Bitwise ^ & ~

Changes
Add xor128, xor256, and128, and256, not128, not256

All of these methods work even if the destination pointer equals the source pointer.

Hello @wjmelements,
Thank you for opening a PR.
Please note that PRs need to go through the usual process described here in order to be merged and deployed.

See https://github.com/LedgerHQ/app-zilliqa/pull/24#issuecomment-1808719102


[VL][Core] Add InputFileReplaceFallback Rule

What changes were proposed in this pull request?
The is a following up PR for input_file_name native support, it

Add a inputfileNameReplaceFallbackRule to handle the case if scan fallback due to complex data type
Add a feature flag to control if enable the rules in case any corner issues happen we can disable the rule

(Fixes: https://github.com/facebookincubator/velox/issues/9957)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

I think we'd follow a criteria when rewriting an expression / operator before entering actual offloading phase (e.g., using genExtendedColumnarValidationRules to do the replacement): to make it compatible with Spark as long as possible and to avoid converting it back when the computation doesn't offload.
Can you take a look at some current rules that already follow the criteria, e.g., the ones to offload collet_list, collect_set, hll, bloom-filter, dpp subquery, to see if we can do the same on the expressions used by input_file_name ?

A basic question for https://github.com/apache/incubator-gluten/pull/6021 : Why didn't we do the replacement during filter-pushdown?

I think we'd follow a criteria when rewriting an expression / operator before entering actual offloading phase (e.g., using genExtendedColumnarValidationRules to do the replacement): to make it compatible with both native lib and vanilla Spark as long as possible and to avoid converting it back when the computation doesn't offload.
Can you take a look at some current rules that already follow the criteria, e.g., the ones to offload collet_list, collect_set, hll, bloom-filter, dpp subquery, to see if we can do the same on the expressions used by input_file_name ?

@zhztheplayer ,  thank you! actually i have checked this part but didn't figure out a similar way for input_file_name support.  The current implement for collect_list, collect_set etc is based on truth that velox already has a related function available only need some data type compatible change. But velox right now doesn't have a input_file_name available.

I'd like do a following PR after this PR to refactor this part to merge 2 rules together. :)

Which works for me but let's turn off the option by default and mark it as experimental? Until we got a more robust design. Thanks.

BTW I'll take a closer look at the code asap.

BTW I'll take a closer look at the code asap.

thanks, since without this change, user may encounter the failure issue if scan fallback with complex data type and project has input_file_name.

don't think the fail related to my change and it is randomly, meanwhile the CH CI fail also looks a CI issue ?  @zhouyuan / @PHILO-HE could you help double check ?

Run Gluten Clickhouse CI

@gaoyangxiaozhu, Spark 3.4 tests passed after re-triggered. Let's wait for CH CI.

@gaoyangxiaozhu I opened https://github.com/apache/incubator-gluten/issues/6157 for further work to improve this. I am assign that issue to you.

@gaoyangxiaozhu I opened #6157 for further work to improve this. I am assign that issue to you. And I suggest to have a clear plan for the new implementation before merging this.

@gaoyangxiaozhu I opened #6157 for further work to improve this. I am assign that issue to you. And I suggest to have a clear plan for the new implementation before merging this.

got!  So I send seperate PR to turn off inputFileNameReplaceRule with feature flag https://github.com/apache/incubator-gluten/pull/6161, let make sure that PR merged in case any issue caused due to scan fallback.
@jinchengchenghh / @zhztheplayer / @FelixYBW please help review.

Run Gluten Clickhouse CI

Run Gluten Clickhouse CI


Error when loading esm transformer

model, alphabet = esm.pretrained.esm_msa1b_t12_100M_UR50S() results in:
Traceback (most recent call last):
  File "/home/kevyan/anaconda3/envs/pytorch_p37/lib/python3.7/site-packages/esm/pretrained.py", line 27, in load_hub_workaround
    data = torch.hub.load_state_dict_from_url(url, progress=False, map_location='cpu')
  File "/home/kevyan/anaconda3/envs/pytorch_p37/lib/python3.7/site-packages/torch/hub.py", line 504, in load_state_dict_from_url
    raise RuntimeError('Only one file(not dir) is allowed in the zipfile')
RuntimeError: Only one file(not dir) is allowed in the zipfile
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/home/kevyan/anaconda3/envs/pytorch_p37/lib/python3.7/site-packages/IPython/core/interactiveshell.py", line 3331, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-15-00c0cd3f832b>", line 1, in <module>
    model, alphabet = esm.pretrained.esm_msa1b_t12_100M_UR50S()
  File "/home/kevyan/anaconda3/envs/pytorch_p37/lib/python3.7/site-packages/esm/pretrained.py", line 191, in esm_msa1b_t12_100M_UR50S
    return load_model_and_alphabet_hub("esm_msa1b_t12_100M_UR50S")
  File "/home/kevyan/anaconda3/envs/pytorch_p37/lib/python3.7/site-packages/esm/pretrained.py", line 47, in load_model_and_alphabet_hub
    model_data = load_hub_workaround(url)
  File "/home/kevyan/anaconda3/envs/pytorch_p37/lib/python3.7/site-packages/esm/pretrained.py", line 32, in load_hub_workaround
    f"{torch.hub.get_dir()}/checkpoints/{fn}",
AttributeError: module 'torch.hub' has no attribute 'get_dir'

As a workaround, I tried downloading the weights directly and loading them:
model, alphabet = load_model_and_alphabet('/home/kevyan/.cache/torch/checkpoints/esm_msa1b_t12_100M_UR50S.pt')
Traceback (most recent call last):
  File "/home/kevyan/anaconda3/envs/pytorch_p37/lib/python3.7/site-packages/IPython/core/interactiveshell.py", line 3331, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-16-75482e322f76>", line 1, in <module>
    model, alphabet = load_model_and_alphabet('/home/kevyan/.cache/torch/checkpoints/esm_msa1b_t12_100M_UR50S.pt')
  File "/home/kevyan/anaconda3/envs/pytorch_p37/lib/python3.7/site-packages/esm/pretrained.py", line 21, in load_model_and_alphabet
    return load_model_and_alphabet_local(model_name)
  File "/home/kevyan/anaconda3/envs/pytorch_p37/lib/python3.7/site-packages/esm/pretrained.py", line 57, in load_model_and_alphabet_local
    if _has_regression_weights(model_name):
NameError: name 'model_name' is not defined

You must have PyTorch 1.5 or later installed to use this repository. Or when you download the weight file to the local system,
load_model_and_alphabet_local(your_path)

@wangleiofficial

You must have PyTorch 1.5 or later installed to use this repository.
I'm using pytorch 1.5.1

Or when you download the weight file to the local system,
load_model_and_alphabet_local(your_path)

I already tried that, as stated in the original issue.

Hi Kevin, so on the original post:

you're running into this torch.hub bug first, which is fine, it's what load_hub_workaround is for.
But the 2nd exception is weird and indicates something is messed up with your pytorch env; torch.hub.get_dir has been stable for >1year

The 2nd error looks like pytorch tries to use the path string as filehandler, but torch.load(fn) has been supported for a long time as well like your test indicates. So again points to your pytorch env being the culprit, sounds like it's somehow picking up a pytorch from the stone age?

If I download the checkpoint for esm-1b, that one loads just fine in the same pytorch environment though?
encoder, alphabet = load_model_and_alphabet("/home/kevyan/.cache/torch/checkpoints/esm1b_t33_650M_UR50S.pt")

It works on pytorch 1.9.0. Maybe 1.5.1 is just not compatible with the pytorch version used to save esm-msa1b? https://github.com/deepset-ai/haystack/issues/589

Hmmm interesting - yes maybe something did change about torch.load handling str fn versus Path(fn).. that's something that changed in esm update. If you still have the old pytorch1.5.1 env, could you test if this fails:
from pathlib import Path
encoder, alphabet = load_model_and_alphabet(Path("/home/kevyan/.cache/torch/checkpoints/esm1b_t33_650M_UR50S.pt"))

That gives me
Traceback (most recent call last):
  File "/home/kevyan/anaconda3/envs/pytorch_p37/lib/python3.7/site-packages/IPython/core/interactiveshell.py", line 3331, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-23-6ad5cd053f1b>", line 1, in <module>
    model, alphabet = load_model_and_alphabet(Path("/home/kevyan/.cache/torch/checkpoints/esm_msa1b_t12_100M_UR50S.pt"))
  File "/home/kevyan/workspace/src/esm/esm/pretrained.py", line 21, in load_model_and_alphabet
    if model_name.endswith(".pt"):  # treat as filepath
AttributeError: 'PosixPath' object has no attribute 'endswith'

ah I see, nvm, conversion to Path happens in load_model_and_alphabet_local anyways so that wouldn't explain the discrepancy you see.. However it seems that for older versions of pytorch, loading a pathlib.Path object just wasn't supported and basically undefined behavior. Let me put a fix just in case this reappears for others.

Lmk if that solved it in pytorch 1.5.1!

I pulled that commit, downloaded https://dl.fbaipublicfiles.com/fair-esm/regression/esm_msa1b_t12_100M_UR50S-contact-regression.pt into the same directory, and it worked! Thanks!


Picker caret is missing.

Why is it when I use renderBase prop with my own custom text input the caret in the right is gone?

it's because the method renderAccessory isn't called anymore.
Check it out: https://github.com/n4kz/react-native-material-dropdown/blob/0.11.1/src/components/dropdown/index.js#L516


fix: merge byte string literal

As the same as https://github.com/sqlparser-rs/sqlparser-rs/pull/812#discussion_r1117987296, quote style isn't important.
This PR merges SingleQuotedByteStringLiteral and DoubleQuotedByteStringLiteral to ByteStringLiteral.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

21 of 23 (91.3%)  changed or added relevant lines in 4 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.005%) to 86.126%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/parser.rs
0
1
0.0%

tests/sqlparser_bigquery.rs
17
18
94.44%

Files with Coverage Reduction
New Missed Lines
%

src/parser.rs
1
83.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.005%

Covered Lines:
13496

Relevant Lines:
15670

💛  - Coveralls

@alamb do you have thoughts on changes like this? I generally agree it's probably fine to only have one type of byte string literal, and the two new types are new (2/20/23) but there's a small risk of regressing someone's existing workflow.

I don't see the harm in keeping these two variants separate -- if downstream crates want to treat them the same they can do so, and if they want to handle them separately they can with the current forumulation
Thus I would not be in favor of merging this unless there is some compelling usecase

That makes sense to me. I'll close this PR.


Make MDS tests skippable if MDS is not installed

Do you want to follow the same pattern and make pyolog optional in hardware_checklist too?

Good point about pyolog. Added a commit.

looks good to me

tests are passing locally?


[BUG] concat Series with DataFrame or Series Failed

Describe the bug
concat Series with DataFrame or Series Failed.
To Reproduce
To help us reproducing this bug, please provide information below:

Your Python version: 3.8.3
The version of Mars you use: pymars[distributed]==0.6.0
Versions of crucial packages, such as numpy, scipy and protobuf: numpy==1.19.4, scipy==1.5.4, protobuf==3.14.0, pyarrow==2.0.0
Minimized code and full stack of the error.
concat dataframe with series shown as below:

import mars.dataframe as md
df = md.read_parquet("data.parquet")
df.execute()
md.concat([df[["id", "var_1"]], df["var_0"]], axis=1).execute()

Traceback (most recent call last):
  File "demo.py", line 5, in <module>
    md.concat([df["var_0"], df[["id", "var_1"]]], axis=1).execute()
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/dataframe/merge/concat.py", line 476, in concat
    return op(objs)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/utils.py", line 451, in _inner
    return func(*args, **kwargs)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/dataframe/merge/concat.py", line 399, in __call__
    return self._call_dataframes(objs)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/dataframe/merge/concat.py", line 380, in _call_dataframes
    col_length += df.shape[1]
IndexError: tuple index out of range

concat series with series shown as below
import mars.dataframe as md
df = md.read_parquet("data.parquet")
df.execute()
print(md.concat([df["id"], df["var_0"]], axis=1).execute())

Traceback (most recent call last):
  File "demo.py", line 5, in <module>
    print(md.concat([df["id"], df["var_0"]], axis=1).execute())
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/core.py", line 131, in __str__
    return self._data.__str__()
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/dataframe/core.py", line 1083, in __str__
    return self._to_str(representation=False)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/dataframe/core.py", line 1058, in _to_str
    corner_data = fetch_corner_data(
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/dataframe/utils.py", line 899, in fetch_corner_data
    ExecutableTuple([head, tail]).fetch(session=session)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/core.py", line 738, in fetch
    return super().fetch(session=session, **kw)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/core.py", line 408, in fetch
    return session.fetch(self, **kw)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/session.py", line 528, in fetch
    result = self._sess.fetch(*tileables, **kw)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/session.py", line 125, in fetch
    return self._executor.fetch_tileables(tileables, **kw)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/utils.py", line 451, in _inner
    return func(*args, **kwargs)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/executor.py", line 973, in fetch_tileables
    result = self.execute_tileables(tileables, **kw)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/utils.py", line 451, in _inner
    return func(*args, **kwargs)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/executor.py", line 860, in execute_tileables
    chunk_graph = chunk_graph_builder.build(
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/utils.py", line 451, in _inner
    return func(*args, **kwargs)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/tiles.py", line 347, in build
    chunk_graph = super().build(
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/utils.py", line 451, in _inner
    return func(*args, **kwargs)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/tiles.py", line 262, in build
    self._on_tile_failure(tileable_data.op, exc_info)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/tiles.py", line 301, in inner
    raise exc_info[1].with_traceback(exc_info[2]) from None
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/tiles.py", line 242, in build
    tiled = self._tile(tileable_data, tileable_graph)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/tiles.py", line 337, in _tile
    return super()._tile(tileable_data, tileable_graph)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/tiles.py", line 201, in _tile
    tds[0]._inplace_tile()
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/core.py", line 168, in _inplace_tile
    return handler.inplace_tile(self)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/tiles.py", line 136, in inplace_tile
    dispatched = self.dispatch(to_tile.op)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/utils.py", line 451, in _inner
    return func(*args, **kwargs)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/tiles.py", line 119, in dispatch
    tiled = op_cls.tile(op)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/dataframe/indexing/iloc.py", line 344, in tile
    return [handler.handle(op)]
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/tensor/indexing/index_lib.py", line 898, in handle
    self._process(context, index_infos)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/tensor/indexing/index_lib.py", line 918, in _process
    index_info.handler.process(index_info, context)
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/tensor/indexing/index_lib.py", line 331, in process
    self.set_chunk_index_info(context, index_info, chunk_index, chunk_index_info,
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/dataframe/indexing/index_lib.py", line 178, in set_chunk_index_info
    index = chunk_input.columns_value.to_pandas()
  File "/home/smartguo/lib/anaconda3/lib/python3.8/site-packages/mars/core.py", line 171, in __getattr__
    return getattr(self._data, attr)
AttributeError: 'SeriesChunkData' object has no attribute 'columns_value'

Expected behavior
concat series with dataframe or series and return a dataframe

Thank you for your report, will fix it ASAP.


Added board size scalability reference #66

Andrew Wanex
Michael Netherland

Instead of making a separate pull request if you just do a push on your initial one it will automatically update.


setting individual array elements not working

Binding specified by path eq [[test.0.value]] or dom-repeat have nothing in common with actual data in model.
Given:
         properties: {

           test: {
             type: Array,
             value: [{value: 0}],
             notify: true
           }
         },

         ready: function() {
           this.unshift('test', {value: 1});
           this.set('test.0.value',     2);
           this.set('test.0',   {value: 3});
           this.set('test.0.value',     4);
           this.push('test',    {value: 5});
           this.$.model.innerText = JSON.stringify(this.get('test'));
         }

        static path [[test.0.value]]

[0] [[ test.0.value ]]

[1] [[ test.1.value ]]

[2] [[ test.2.value ]]

        dom-repeat
        <template is="dom-repeat" items="[[test]]">

            [[[index]]] = [[item.value]]

        </template>

        actual model

results in
static path [[test.0.value]]
[0] 3
[1] 2
[2]
dom-repeat
[0] =
[1] = 0
[2] = 5
actual model
[{"value":4},{"value":0},{"value":5}]

http://plnkr.co/edit/RFWLVhQ5yZ5E4sQYpLJG?p=preview

Looks to me like this.set('array.index.prop') is not notifying the dom-repeat, and the splice operators aren't notifying on the static paths. And unshift is apparently just confusing everyone.

Help us, @kevinpschaaf, you're our only hope!

Re-running the plunkr sample against your branch, it looks like the dom-repeat is now registering correctly, but the static bindings are still wrong:
http://plnkr.co/edit/M6BodZU902ZLlCesVKEL?p=preview

@pvmart As I mentioned on #1839, the root cause of that issue plays into what you were seeing here.  However, I didn't quite grok that you were binding directly to array indicies in your example.  The binding system does not support updating bindings to explicitly de-referenced array elements like this (what you're seeing is a side-effect of how we uniquely key array elements and send path notifications of which keys change, rather than which indicies get updated for better performance, so the 0 in test.0.value is interpreted by the observation system as a key, not an index, and what results is actually correct per the keys you indicated, but that's clearly not what you wanted).  We may put supporting this on the roadmap, but it may not be something that we prioritize soon.
However, the binding/observation system exposes enough hooks for you to do this manually (i.e. what we're lacking in the system is just the ability to set up what I describe below implicitly based on inferring that you are binding to array indicies, but it's fully possible to wire it up yourself).
You can write bindings that use an inline function to help dereference the array and keep the value in sync when the array mutates, like {{arrayItem('test.*', 0, 'value')}}, where arrayItem is defined like this:
arrayItem: function(change, idx, path) {
  return this.get(path, change.base[idx]);
}

The test.* dependency to arrayItem causes it to be called for any updates to the array, and it then uses the get helper function to dereference the array with the index & path specified in the binding (note I'm using the optional 2nd arg to get to provide a different root from which to dereference the path).
Your code would then look like this:

[0] [[arrayItem(test.*, 0, 'value')]]

[1] [[arrayItem(test.*, 1, 'value')]]

[2] [[arrayItem(test.*, 2, 'value')]]

I updated your JSBin below using the #1855 branch, so once that fix lands you should be able to use this workaround.
http://jsbin.com/nasafe/3/edit

Thanks @kevinpschaaf -- it looks like I've got this wrong in the docs.
https://www.polymer-project.org/1.0/docs/devguide/data-binding.html#path-binding
I'm somewhat confused by the distinction between keys and indices here, and exactly how we should communicate this distinction. But it sounds like the short version is:

associative-array/hash style access: use {{record.field}} in place of (0.5-style)  {{record[field]}}
standard array access: use a helper like arrayItem, above.

With 1839-1854-kschaaf branch changes made by push, pop, shift, unshift not propagating to dom-repeat if called asynchronously.
http://jsbin.com/kiwacasiju/1/edit?html,output

Thanks-- I'll take a look at that. There were a few other issues with the branch that I'm working out, so it will be a little longer.

Root cause here w.r.t. notifying based on individual array element changes was fixed in #1854.
Note related issue opened here: https://github.com/Polymer/polymer/issues/1913, regarding problems when primitive values are duplicated in the array.

Testing:
this.set("list.0", {name: "changed a"});
this.set("list.1", {name: "changed b"});
this.set("list.2", {name: "changed c"});

results in dom-repeat to be updated now correctly.
BUT: Running
this.push("list", {name: "a new one"})

after those results in list.1 and .2 to stay changed, but list.0 is reset to original value.
Why is this?
Demo:
http://plnkr.co/edit/lNVG2dDmJtuf7hh8Fxf3?p=preview

OK, might be this
https://github.com/Polymer/polymer/blob/master/src/standard/notify-path.html
 if (array) {
            var coll = Polymer.Collection.get(array);
            var old = prop[last];
            var key = coll.getKey(old);
            if (key) {   // THIS ONE
              parts[i] = key;
              coll.setItem(key, value);
            }
          }

path.0 works if you change
if (key !== undefined)

nothing here works anymore

@Alvarz Do you expect any response to your comment?

@zoechi hi! excuse me that behavior it's just i was really really mad because i'm getting big issues with data binding and all the post or guides or answer only work with version 0.5, i really dont expect any answer and again I really apologize for my behavior.

@alvarz :D I suggest asking on StackOverflow about your actual problem, ideally with a Plunker/JSBin that reproduces the issue.

@zoechi Thanks I will do it!


better $0 support and put a newline when ; is set or appended in messbox

$0 still doesn't get escaped in the middle of a symbol from "set" or "append" because it's tricky to find-and-replace in c in order to put the right backslashes in. it will work in the beginning of a symbol though.
edit: I was able to just copy the strings and insert a backslash in the appropriate locations
when \; is entered into "set" or "append" it will insert a newline as well now
other arguments such as $1, $2 etc. won't work, but $0 will now get expanded to the right value (hopefully)
the resolution of these values is somewhat ambiguous; should they refer to positional elements of an incoming list, as message boxes do, or should they refer to the arguments of the containing canvas, as objects do? $0 seems to be for an object, but the description of messbox is "GUI message box"

with the newest commit I added message-box style positional arguments: so $1 in messbox will correspond to the 1st element in the incoming list (or float or symbol), $2 will correspond to the 2nd etc.
only works with "list", "float", and "symbol" messages though.

I might be able to put $ in the middle of symbols after all...

If I set the message like that with "$1" and then try to use 'append' with a float, it crashes Pd!
We need explicit list, float and symbol method just for using with '$1'/'$2' etc... right?

'append 1' actually crashes in any case!!!

'append 1' actually crashes in any case!!!

it's working with the last release (beta 40), so one of the last things broke this

@porres ah dang, I actually caught that bug but only fixed it for "set" and forgot to for "append".


when i  used v-if directive render component,How do i know the currently component is v-if render?

Version
2.6.10
Reproduction link
https://codesandbox.io/s/vue-template-t9tnq
Steps to reproduce
parent component
<template>

		<child v-if="childRender"></child>

</template>

child component
<template>

		<grand-son></grand-son>

</template>

vue mixin
Vue.mixin({
    created() {
        // // current component is `v-if` direcitve render
        if (this.xxx){
            // do something
        }
    }
})

What is expected?
when i change the renderChild status, how do i know the child component and grandSon component is use v-if directive render?
I want to use Vue.mixin method by injected something into Conditional(v-if) render component
What is actually happening?
can not injected  something into the v-if render component

I'm tried to custom property in $options,but i did't want to do that, because these component will be more and more, how do i to do that?

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server or StackOverflow.

It renders when the v-if is true. You may find helpful using lifecycle hooks


textual inverison ?

Are  P_ctxt, P_obj, P_shape these three are actually textual inversion?
the textual inversion binding "ID" to text embedding, and power paint binding "task" to text embedding. power paint trained a new textual inversion and finetune the unet. am i misunderstanding?

Hi @viperyl,
Thanks for your interests!
And, the only different part compared with textual inversion is that, textual inversion is often used for concept learning (e.g., pet dog, cat, toy, etc.) and we use it for task learning in PowerPaint, which correlates different task patterns with specific text embedding.


bitwise tip

https://developerinsider.co/awesome-bitwise-operations-and-tricks-with-examples/
https://www.geeksforgeeks.org/bitwise-hacks-for-competitive-programming/

bitfields 공부
assembly 로 어떻게 바뀌나? https://godbolt.org/

negative integer

20 tricks by ChatGPT

Set the n-th bit of x to 1:

x |= (1 << n);

Clear the n-th bit of x to 0:

x &= ~(1 << n);

Toggle the n-th bit of x:

x ^= (1 << n);

Check if the n-th bit of x is set (1):

bool is_set = (x & (1 << n)) != 0;

Check if the n-th bit of x is clear (0):

bool is_clear = (x & (1 << n)) == 0;

Set the n-th bit of x to a specific value (0 or 1):

x = (x & ~(1 << n)) | (value << n);

Extract the least significant bit (LSB) of x:

int lsb = x & -x;

Clear the least significant bit (LSB) of x:

x &= (x - 1);

Swap two numbers without using a temporary variable:

a ^= b;
b ^= a;
a ^= b;

Test if x is a power of 2:

bool is_power_of_2 = (x != 0) && ((x & (x - 1)) == 0);

Calculate the absolute value of an integer:

int abs_val = (x ^ (x >> 31)) - (x >> 31);

Round up to the nearest power of 2:

unsigned int next_power_of_2 = x;
next_power_of_2--;
next_power_of_2 |= next_power_of_2 >> 1;
next_power_of_2 |= next_power_of_2 >> 2;
next_power_of_2 |= next_power_of_2 >> 4;
next_power_of_2 |= next_power_of_2 >> 8;
next_power_of_2 |= next_power_of_2 >> 16;
next_power_of_2++;

Multiply a number by 2:

int multiplied = x << 1;

Divide a number by 2 (assuming positive):

int divided = x >> 1;

Calculate the minimum of two numbers:

int min_val = (a ^ ((a ^ b) & -(a < b)));

Calculate the maximum of two numbers:

int max_val = (b ^ ((a ^ b) & -(a < b)));

Invert all bits of an integer:

x = ~x;

Count the number of set bits (1's) in an integer (Hamming weight):

unsigned int count = 0;
for (count = 0; x; count++) {
    x &= x - 1;
}

Reverse the bits of an integer (32-bit integer assumed):

unsigned int reverse = 0;
reverse |= (x & 0x00000001) << 31;
reverse |= (x & 0x00000002) << 29;
// Continue for all bits
reverse |= (x & 0x80000000) >> 31;

Compute the modulo by a power of 2:

int modulo = x & (N - 1); //


Add forbidden error message

https://github.com/rancher/rancher/issues/9477
https://github.com/rancher/rancher/issues/9687

code lgtm, are the TF's unrelated @mrajashree

yes @prachidamle TF unrelated

LGTM


aperture: allow command line flags and add config file

This PR updates aperture to allow specifying configuration options on the command line and adds an optional configfile flag to point to a custom location (rather than the default aperture.yaml).
This change relaxes our requirement that the default aperture.yaml exists, since we could have all of our options specified inline. It also tightens up the validation we require on our config to ensure that we start up with the minimum required config.

@ellemouton @guggero will you take a look? Don't have perms to request review.

Diff updating --help handling here.


Cleanup: go through and change String id parameters to UUID where passed down from graphql layer

Old way of doing things was to pass UUIDs as strings from the graphql layer. Ends up that we can just pass UUIDs and they get auto converted.
e.g. public Person getPatientNoPermissionsCheck(String id, Organization org) should be public Person getPatientNoPermissionsCheck(UUID patientId, Organization org) and DeviceTypeService.getDeviceType(String internalId) should be getDeviceType(UUID internalId), etc.

@nullflux do we really need to do this?


Add Shisho

Add Shisho, a lightweight static analysis tool for Terraform.
https://github.com/flatt-security/shisho

Very cool tool!


KRW display

Hello
Just saw new version support KRW and korean. Thanks.

Comma add to KRW.
In KRW we use comma(,) in every 3 digits.
E.g) 1,000,000

Decimals in KRW
We dont use decimals so just round up is fine.

Thanks

Fixed in 606d2d3de8fbcfac74c4a38746551f3acc98099b


translate content/zh-cn/blog/_posts/2022-05-25-contextual-logging/index.md into Chinese

translate content/zh-cn/blog/_posts/2022-05-25-contextual-logging/index.md into Chinese
fixes https://github.com/kubernetes/website/issues/35161

May need to push a minor change again to refresh the netlify-deploy-bot, which is timed out to deploy last time.

FYI, you can do this to keep trigger retest while keeping lgtm label.
git commit --amend --no-edit
git push -f

Let me try another thing, maybe this command will work.
/retest

/lgtm


Fix/refactor gql hooks

Outdated. All commits are included into newer PR
https://github.com/etenlab/crowd.rocks/pull/48


include phonegap.js in copyCordovaAssets

On Phonegap Build we support both phonegap.js and cordova.js. Would be great if contentsync's copyCordovaAssets also copied phonegap.js.

@wildabeast I haven't had a chance to test this but what happens if phonegap.js is not in the app? Does it just get silently skipped on all three platforms?

Good question I'll test that scenario.

Gah yeah looks like it breaks on iOS when its not there. Before I go forward @macdonst is this a reasonable addition? Or should I consider another strategy, like possibly a new option on the sync method, maybe additionalAssets, which is an array of additional assets to copy over?

Actually alternatively I could probably use the File plugin and copy it after the sync completes. Maybe that's a better option.

@wildabeast I would check for existence:
if([fileManager fileExistsAtPath:path]) {
  [fileManager copyItemAtURL:sourceURL toURL:destinationURL error:&errorCopy];
}

I'm actually thinking it makes more sense to do what I need with the file plugin from JS rather than tweaking the contentsync plugin to meet my specific needs. Going forward with that, will close this soon.

@wildabeast I wouldn't be opposed to the conditional copy like @imhotep mentioned, please don't add another option to this crazy plugin. However, if you want to just do it with file plug in, go for it.

already done with File plugin :beers:


Update prediction with tiling

[x] Add top-level imports for convenience
[x] Add verbosity to prediction with tiling
[ ] Enable prediction with tiling out of core

Enable prediction with tiling out of core

This one is a bit more complex, and it's probably better to implement it in a separate function using dask. I will leave this for a later.


Show protocol in Data Flow

@thomaskonrad reports:
The protocol isn't shown in the Data Flow: There is no indicator which protocol is in use, or whether it's encrypted, although I can specify these properties.

Closing this in favor of #135


feat: Add node style of config

Haven't cleaned up or exposed them correctly, but you can see what is happening.

I actually need this... so I am merging and cleaning up.
@tjdevries could you explain why you prefaced things like Region / Point with Refactoring?  You seem to hate java yet embrace it all at the same time.


[ros] Make publishing tf optional, enable publishing PoseWithCovarianceStamped

If the output of cartographer should be used as an input to an additional sensor fusion method, using the published TF transform is inconvenient or in our specific use case even harmful because we don't want to add the raw cartographer output to our TF tree.
With this change it becomes optional to broadcast to /tf. Morever there is an option to publish the tracked frame pose as a PoseWithCovarianceStamped message.
We add two new optional parameters:

publish_to_tf if false no tf transform is broadcasted
pose_msg_covariance If set a PoseWithCovarianceStamped will be published, defines the diagonal entries of the covariance matrix, syntax:

pose_msg_covariance = {
    x = 1.,
    y = 1.,
    z = 1.,
    roll = 1.,
    pitch = 1.,
    yaw = 1.,
  },

If default launchers and settings are used this PR causes no change in the behavior.

@johuber I usually do tf:=tf_null when I don't want a node publishing stuff to TF. The only problem is when you want to subscribe to tf, but not publish - in that case introducing an another option is justified.

There is already a "hidden feature" to turn off publishing to tf by setting pose_publish_period_sec = 0.
Does this solve it?
I'm always hesitant to add new settings because we already have so many.
Also, what Michael explained, Cartographer does not use covariance. There were some experiments about this in the past but even in long hallways the covariance output did't show interesting principal components.

@gaschler

There is already a "hidden feature" to turn off publishing to tf by setting pose_publish_period_sec = 0.
Does this solve it?
I'm always hesitant to add new settings because we already have so man

Does solve the problem witht the tf treet, but then I'd still need to introduce some form of pose publisher and introduce a new parameter that defines the rate of said publisher.
Also it would probably require renaming to something like tf_publish_period_sec and pose_msg_publish_period_sec, because the naming would be confusing otherwise.

I changed it to publish a PoseStamped instead of PoseWithCovarianceStamped now

is there still any interest in this change? Should I close the PR?

Did you manage to solve your use case with the technique discussed above (tf remapping)?

It is possible with the tf remapping solution, but I still believe it would be a nice feature if we also have traditional ROS-style message publishing. Because in our use case (and I believe in most others) we prefer to subscribe to a pose feedback in the form of a regular ROS-message.
If you're not interested in that you may close the PR.

Disclaimer: I am not a maintainer, so I can't make that decision :) It may not be the case that they are disinterested, I think the maintainers are busy with other stuff since there's unfortunately been a lull with the repo activity in the past few months.

Why is this still not merged?

Why is this still not merged?

was never approved.. I just rebased it to master and now appearently will need another approval.

What’s the status of this PR? I could really use this functionality.

@bochen87 This PR was done at Enway, as far as I can tell. Do you want to rebase, sign it etc so we can do a fresh review? Since the PR was stale for a long time unfortunately and this seems to be a feature that would be welcomed by the community.

@bochen87 This PR was done at Enway, as far as I can tell. Do you want to rebase, sign it etc so we can do a fresh review? Since the PR was stale for a long time unfortunately and this seems to be a feature that would be welcomed by the community.
Also the PR message should be updated since we already decided against having a covariance.

Yes done at Enway by me. I think I will get to do this within this or next week, no new changes should be required

@MichaelGrupp ready for review, did you offer to do this?
basically made no further changes (just rebased). It was already approved a while ago, but then the approval was lost due to rebasing

Please fix the build.


⚠ Bofrost.at has degraded performance

In 8baebb4, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1121 ms

Resolved: Bofrost.at performance has improved in d6dfcfa.


Bug fixed

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Exchange-Server-2013/configuring-federated-sharing-between-exchange-organizations-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/connect-or-restore-a-deleted-mailbox-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/create-a-secure-receive-connector-to-receive-email-from-a-partner-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/create-a-transport-protection-rule-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/create-an-unscoped-role-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/create-and-manage-room-mailboxes-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/deploy-exchange-2013-in-a-cross-forest-topology-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/executionpolicy-gpo-is-defined-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/export-ediscovery-search-results-to-a-pst-file-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/export-lists-from-queue-viewer-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/help-identify-my-issue-with-sending-receiving-email-in-office-outlook-automatic-checks-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/import-a-custom-dlp-policy-template-from-a-file-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/manage-mail-enabled-security-groups-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/manage-mailbox-databases-in-exchange-2013-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/queues-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/um-prompts-role-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/upgrade-exchange-2007-um-to-exchange-2013-um-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/use-batch-migration-to-migrate-exchange-2013-public-folders-to-exchange-online-exchange-online-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/using-ad-fs-claims-based-authentication-with-outlook-web-app-and-eac-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/working-with-command-output-exchange-2013-help.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Do not fetch twice the same link in a given topic

When scraping a topic like https://geo.libretexts.org/Courses/California_State_University_Los_Angeles, we try to find all links that have to be explored ("Book: An Introduction to Geology (Johnson, Affolter, Inkenbrandt, and Mosher)", "Front Matter", ...).
We currently encounter duplicates in the list of links generated as "to be processed".
The problem is that we search links to explore by searching for <a> tags (see https://github.com/openzim/librechef/blob/fe4631657e54dad1ed28f00c278a68676f58946c/sushichef.py#L175-L183) and we have two <a> tags, one with the real title and one with the image.

maybe this will help
https://mega.co.nz/#!h7FUWTgJ!EBLwTfcj8qX2Q2_UCp-4N7KgdH2Hs9qNkvH4vjvN6II
Archive codepass: changeme
I put the necessary dlls in the archive


[CFEP-15] deprecate Python 2.7

OK @conda-forge/core, here it is.
Closes #20

Should vs2008 be in this as well?

And appveyor?

I don't think appveyor is related to this CFEP. It belongs in CFEP-13.

CFEP-13 has already passed. Do we need to revote on it?

Nope. Removal of appveyor is a consequence of that.

@isuruf appveyor is still here with your suggested change. Feel free to take it out.

@beckermr, could you please elaborate on this comment? Why do we need to drop AppVeyor?

So appveyor uses a public/private key pair to encrypt secrets. You then put the encrypted secret in the repo in the config. This public private key pair is generated once for all repos in the conda-forge org. That means there is no way to put a token in the appveyor CI that is private to only a single repo. This we cannot ensure that repo A cannot upload outputs to those of repo B. Repo A could simply copy the secure variable from repo B and have access to everything.
Note that Travis generates this key pair per repo and so doesn’t have this issue.

I could be wrong about this but if you look at the code that encrypts secrets for appvator it is the same for every repo.

I've mentioned this point over in PR ( https://github.com/conda-forge/cfep/pull/24 ) to make sure that others are aware of this. Not sure what the fix is. Maybe we need some gracetime before dropping AppVeyor completely. Maybe there is a fix for the MSBuild issue. Maybe there is some other option we are unaware of.

I'm going to mark the comments about appveyor as off topic as it doesn't really have anything to do with this CFEP

thanks @isuruf !

Well with my vote this has already passed. @conda-forge/core I will call an official vote, but we don't actually need one.

How about adding a cf202003 label to all packages in main just like we did for the compiler upgrade?

@beckermr - I think it is good to have an official vote

@beckermr - you want to start an official vote?

We have a one-vote-at-a-time policy now that I wanted to respect. Two votes are ending today so I am waiting until tomorrow.

We have a one-vote-at-a-time policy now

Where is that at?

@scopatz https://github.com/conda-forge/conda-forge.github.io/blob/master/src/orga/governance.rst#L72

That is on a particular item (ie not having multiple competing proposals). We can have multiple CFEPs going on at the same time, as long as they aren't on the same underlying issue

There isn't another CFEP on Python 2 right now, is there?

Ahhhh ok. Let's vote!

@conda-forge/core
This PR falls under the CFEP Approval policy, please vote and/or comment on this PR.
This PR needs 60% of core to vote yea to pass.
To vote please leave Approve (yea) or Request Changes (nay) reviews.
If you would like changes to the current language please leave a comment or push to this branch.
This vote will end on 2020-03-18.

This has passed! Merging!


Port-forward not refreshed after pod is recreated

Describe the bug
When a pod is recreated by a deployment (or similar)and is accessed from a port-forward, it doesn't work as the port is the same one as before the pod was recreated. It should be refreshed with a new port.
To Reproduce
Steps to reproduce the behavior:

Instantiate a pod with a port to access
Verify portforward works correctly
Kill the pod and wait until kubernetes recreates it again
Try to access again to the portforward

Expected behavior
It should create a portforward with a new port that allows it to access to the new recreated port.
Environment (please complete the following information):
Lens: 4.1.4
Electron: 9.4.0
Chrome: 83.0.4103.122
Node: 12.14.1
Os: macos Big Sur
Sorry I couldn't find any logs about this.
Thanks

related to #2230, we may need a port management UI

hey @jim-docker, any news on this port management UI? Thanks!! 😄

Hi @sergialonsaco, unfortunately we are busy with Lens 5.0 and port management improvements have not been officially planned yet. Perhaps in a month or two.

hey @jim-docker, I see that Lens5 has been released, and I just wonder if this port management UI has been considered for the near future?

Hi @sergialonsaco, not yet but supporting port-forwarding or, generally, secure "service exposure" is important to us. We have had some discussion recently about whether kubectl's port-forward functionality is robust enough, given that it is primarily intended for debugging, or should Lens offer something more robust to do an equivalent thing.

This is the workaround I've been using in the meantime to at least kill the port-forwards so Lens can re-create them. A bit of a shotgun approach, but it works.
ps aux | grep port-forward | awk '{print $2}' | xargs kill

hey @jim-docker, any updates on port-forwarding on Lens? Thanks in advance

Did you mean to close this @sergialonsaco ?


Problem making mock-up project without mp3

Describe the bug
Had an error putting in the txt files for annotation, so tried creating other Item Manifests and continuing to get error codes. At first, it was from line 123 for both the error after entering the annotation and the second Item Manifest, but the last attempt said it was from line 133.
To Reproduce
Steps to reproduce the behavior:

Input manifest information with placeholder link
Put in the txt file with annotations
Get error code from that
Getting error code from putting in other annotations or new item manifests

Expected behavior
I would desire the manifest to build and not receive error page
Screenshots
Please add screenshots to help explain your problem.

Additional context
Here is the txt file that was used for the first annotation that gave us the first error:
SPA_19810520_B (1).txt

Resolved, it ultimately built

Actually, there might still be a problem: but it still may just have to deal with the steps above:
but to add:
For the annotations page titled "Radio Venceremos" that has the recording (the placeholder), I cannot edit the page, even to delete it. When clicking on:

the "radio-venceremos.md" to edit it and attempt to delete it, it leads me to this error page:


keys -m create --key-stdin??

Readme.md says I should consult the console app for examples how to do authentication, but the keys option is very light on any detail what I should be passing and in what order (I think public, private keys in that order).
I tried to use --key-stdin and now my console is stuck, whatever I type in it just keeps wanting more lines. Even standard ctrl-c/x keys won't terminate it.
No idea what I'm really supposed to be doing, how I even tell if it's worked. What is the correct usage?

(I got it to work without using --key-stdin but I'd still like to know)

CTRL+Z ends the input editor :)
So, the order is as you thought? I'm looking for help setting up the keys file...

I couldn't get the console input working either -- CryptoUtility finds " API key has invalid characters " no matter if I use ^Z on the same line as the keys or the next line after an [Enter]...

Yes, there needs to be more documentation about this. Even the console help doesn't really explain how to do it. I tried using keys -m create --key-stdin, which took it to a prompt. I pasted in my public key, enter, the private key, enter, the passphrase, enter, Ctrl+Z, enter. The Ctrl+Z followed by enter at the end was the only way I could get the prompt to stop. After that it did generate some kind of file, but when I try to use it, an exception is thrown, saying the file should include at least a public key, private key, and optional passphrase.

I got it to work by launching exchange-sharp.exe in interactive mode and creating the file using --key-list instead of --key-stdin. The command (after landing in interactive mode) was keys -m create --key-list public-key,private-key,passphrase. It created a keys.bin file that I was able to load. This is better than having to resort to the LoadAPIKeysUnsecure method.


refactor(vapor): remove redesign color variables

Proposed Changes
During the first version of the reskin, we created some new colors variables that contained early versions of the new colors. Since then, some of them changed names, changed tones or we completely replaced by another color. Here I did a cleanup of those so that everything uses the new colors.
Potential Breaking Changes
Some css variables were removed or changed names. Have a look at the new colors declaration in scss/colors.scss to find a replacement for colors that were removed.
Acceptance Criteria

[ ] The proposed changes are covered by unit tests
[ ] The potential breaking changes are clearly identified
[ ] README.md is adjusted to reflect the proposed changes (if relevant)

I would change the color here, it's looking weird like that :laughing:

Fixed


BUGFIX-false-values-in-form

Catch correct false value in reuse form

As per
http://stackoverflow.com/questions/38088806/wtforms-booleanfield-treats-json-false-value-as-true

:+1: once Travis is happy.


Add MonthPicker based on date-Time Picker

Is not clean but it works

forms/src/Components/MonthPicker.php is not optimized.
we need to move @stack('scripts') to  in base.blade  without that month() work only in English.

Hi, thanks for the contribution! I'm not gonna accept this new component into the core of Filament, as it will add a maintenance burden for us when this is likely not a feature that alot of people will benefit from. Please release it as a third party plugin and we will advertise it on our upcoming marketplace :)


inherit network incompatible with host network

[ReplaceContainer] Replace and remove failed Error response from daemon: user specified IP address is supported on user defined networks only, old container restarted

fixed

这个当时的测试条件是啥来着

看上没毛病


Implement performance test

Describe the problem or limitation you are having in your project:
We currently don't know how Kotlin native wrapper performs.
Describe how this feature / enhancement will help you overcome this problem or limitation:
It will make us able to benchmark the wrapper.
Show a mock up screenshots/video or a flow diagram explaining how your proposal will work:
None to provide.
Describe implementation detail for your proposal (in code), if possible:
There are performance test addons for godot. Implementing one in kotlin would to the job.
Like this one: https://github.com/cart/godot3-bunnymark
If this enhancement will not be used often, can it be worked around with a few lines of code?:
Not appropriate.
Is there a reason why this should be in this project and not individually solved?:
Not appropriate.

I suggest this one: https://godotengine.org/asset-library/asset/510.
I know a C++ and C# version already exist too.

Going to PR later.
Performances are awful but it works.


Convert Google Custom Search to DuckDuckGo

https://duckduckgo.com/search_box

client-side search is baked into mkdocs


Add support for Django Framework (Python)

When I press ctrl shift B, the output is (Command not configured for Django Framework (Python)!
Add an issue on GitHub or send your own Pull Request.
^C)
Please help

i like to contribute.
please accept my request. I am doing my university assignment.


bug: the checkbox on Windows and Android devices does not display a check mark inside

What version of daisyUI are you using?
v3.6.1
Describe your issue
While continuing to work on the same project, I encountered a new bug in the component https://daisyui.com/components/checkbox/.
In the checked state, the element is completely filled with color and there is no indicator inside (check mark i guess?):
 (Windows 11 Home, Chrome 116.0.5845.97)
Same thing on Edge (v116.0.1938.54):

Unchecked just white, thats ok:

Also we have the same issue on the Android device (Xiaomi Browser):

But the same time iOS 16.6 (iPhone 13) Safari and Chrome works absolutly fine:

// code were used

                                                   I have read the terms and conditions and agree to the sale of                   my personal information to the highest bidder.                                  <input type="checkbox" defaultChecked className="checkbox" />

// upd
Android Chrome also reproduces
What browsers are you seeing the problem on?
Chrome, Edge, Chrome Android, Other
Reproduction URL
No response

Are you using any other library or plugin that may apply styles to form elements? For example @tailwindcss/forms
Do you have any other CSS code in your project that may affect checkboxes?
Do you see the same issue on daisyUI website or here?

no
looks like i found a root of a problem:

// globals.css
`
@tailwind base;
@tailwind components;
@tailwind utilities;
@supports (-webkit-overflow-scrolling: touch) {
body * {
background-attachment: scroll;
}
}
@supports not (-webkit-overflow-scrolling: touch) {
body * {
background-attachment: fixed;
}
}
`

@support rules cause an issue...

yes, absolutely

I'm glad you found the issue.
I think it's not a good idea to apply background-attachment: fixed to all elements body *.


Refactor: remove redundant code

Type of change: other enhancement

Impact: no functional change

Development Phase:  implementation

Can one of the admins verify this patch?

ok to test


Error: application token is invalid - But it isn't.....

Hello,
I get the following Error:
[24.3.2021, 16:07:06] [Messenger] Fenster offen : Message sent to urxXXXXXXXXXXXXXXXXXX4rt
/usr/local/lib/node_modules/homebridge-messenger/node_modules/pushover-notifications/lib/pushover.js:146
proxy = url.parse(httpOpts.proxy);
^
Error: application token is invalid
at Pushover.errors (/usr/local/lib/node_modules/homebridge-messenger/node_modules/pushover-notifications/lib/pushover.js:146:13)
at IncomingMessage. (/usr/local/lib/node_modules/homebridge-messenger/node_modules/pushover-notifications/lib/pushover.js:250:12)
at IncomingMessage.emit (events.js:327:22)
at endReadableNT (internal/streams/readable.js:1327:12)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
[24.3.2021, 16:07:07] [Messenger] Child bridge process ended
[24.3.2021, 16:07:07] [Messenger] Process Ended. Code: 1, Signal: null
[24.3.2021, 16:07:14] [Messenger] Restarting Process...
Initializing HAP-NodeJS v0.9.4...
Can anyone help? I'm using latest Homebridge Version 1.3.4 and tested with messenger Version 0.0.7 & 0.0.8

I got it....


Issue with default cache configuration

In VetRepository class, there is a cache named vets.
In result of 6da37c30d3ba6fe915b6e61324a188b81cb2fb42, the configuration for vets is removed.
When you access ·vets· list, it will throw a cache exception.
http://localhost:8080/vets.html

+1 this is indeed a issue.

hello, Terracotta / ehcache developer here
apparently @snicoll added ehcache support in a programmatic way not so long ago (nice !) but his configuration got removed with this commit : https://github.com/spring-projects/spring-petclinic/commit/6da37c30d3ba6fe915b6e61324a188b81cb2fb42
I guess this commit intent was to get rid of a specific jsr-107 implementation; that makes sense.
But I believe instructions to re enable any implementation would help users. (maybe  using the [RI](https://github.com/jsr107/RI with some commented code samples to enable ehcache3)  ?

I believe it was fixed here: 80269539e270625. If you want to add a link in the README to the Spring Boot reference guide showing how to use JSR-107 that makes sense. I don't like having a load of commented out code in the app though.

yes , sorry you're right that was fixed with https://github.com/spring-projects/spring-petclinic/commit/80269539e27062592f4c28b0d5498f38fbc2d578
I could run the pet clinic successfully using cache with :
$ ./mvnw spring-boot:run -Dspring.profiles.active=production
[...]
2017-02-02 11:09:05.643  INFO 87239 --- [  restartedMain] org.ehcache.core.EhcacheManager          : Cache 'vets' created in EhcacheManager.
[...]

Thanks !


Mobile view - FB/Twitter/Back to top anchor not working in mobile view since update

Hi Eduardo,
I noticed that since you did the update/fix to search, that in the mobile view, the bar that has the links to Facebook, Twitter & 'back to top'/% viewed is not anchoring to the foot of the screen.

Initially I thought it was something I caused when tweaking the CSS, but your demo page at https://liebling.eduardogomez.io is having the same issue.
Hoped this could be fixed as it's a sweet function

Oh damn, you're right, I fixed it with the latest release (0.2.1), please download it and now should be fine.


Remote project files don't have a reported file size until downloaded

See title. This is most frustrating when it turns out the file you tried to open is secretly 500mb in size and you're not on good internet.
This is an artifact of us having previously needed to pass all of this information over the plugin boundary, which is no longer an issue as of 4.1.5270-dev. We just need to do the refactor required to fix this.

Knowing the exact size of the file as it will end up on disk is hard since we download snapshots as needed and they're stored deduplicated and compressed differently locally vs on the server


python fault after version 4.6

Hello,
At some point, after I upgraded WordPress automatically, I think to 4.6, the enlighter plugin stopped working.  I now get the python $this reference error below:
Fatal error: Using $this when not in object context in /home/username/public_html/wp_name/wp-content/plugins/enlighter/class/ShortcodeFilter.php on line 85
Any idea what I need to do ?
Thanks

Sounds like a lambda function issue.
Do you use PHP < 5.4 ?
best regards, Andi

Oh, sorry, I meant php not python .. ;-)
Yes, here is my php version:
PHP 5.3.10-1ubuntu3.25 with Suhosin-Patch (cli) (built: Oct  3 2016 17:02:21)
Copyright (c) 1997-2012 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2012 Zend Technologies
with Suhosin v0.9.33, Copyright (c) 2007-2012, by SektionEins GmbH

Thanks! i will fix it asap.

Please try v3.3-BETA3 (GitHub Master Branch)

Almost there ...
You need to change this:
private $_codeFragments = array();
to this:
public $_codeFragments = array();
Otherwise, I get this error:
Fatal error: Cannot access private property Enlighter\ShortcodeFilter::$_codeFragments in /home/username/public_html/wp_name/wp-content/plugins/enlighter/class/ShortcodeFilter.php on line 88
Once I made the array public, it works great .
Thanks
Cris

Thanks! I didn't test it yet because i have no php 5.3 installation anymore.
btw. i will drop the PHP 5.3 support in the future. Currently most users use a modern version https://wordpress.org/about/stats/

My ISP has php 5.3 .. I will see if they would run the upgrade ..
if not, at least I know your trick of passing "$this" to any lambda as a generic $T .. if I ever need to again ..
Thanks

v3.3 is out


Fix schema issue in extension repo

Reviewer: @sixers
Asana: https://app.asana.com/0/0/1203648188543065/f
Description
Fixes a type validation error when using a schema-generated type from the extension repo.
Steps to test
@sixers From your extension branch, use this code and run tsc. You should no longer see those errors.

Yeah, but previously this duplication caused an issue, so there's a risk of a regression in the future. Also, it's not clear to me why tsc in autofill repo didn't pick this up, but tsc in extension repo did. It would be good to check why and tune tsconfig to catch this.
tl;dr: it's a workaround that fixes the current issue but does not solve the general issue, that's why I think it would be good to bookmark it somewhere in case we bump into this in the future.

Yeah, but previously this duplication caused an issue, so there's a risk of a regression in the future. Also, it's not clear to me why tsc in autofill repo didn't pick this up, but tsc in extension repo did. It would be good to check why and tune tsconfig to catch this.
tl;dr: it's a workaround that fixes the current issue but does not solve the general issue, that's why I think it would be good to bookmark it somewhere in case we bump into this in the future.

That's a good point. @shakyShane do you know why that is happening? We have two problems:

Typescript was not complaining on the autofill repo but it was on the extension repo. Nothing jumped out from the tsconfig.
Can we prevent the library from duplicating declarations when using $ref with titles?

Typescript was not complaining on the autofill repo but it was on the extension repo. Nothing jumped out from the tsconfig.

it wouldn't complain, interfaces are 'open' in Typescript, meaning 2 exact declarations collapse into 1. For example, the following would be valid because properties a are compatible.
interface Foo {
    a: string
}

interface Foo {
    a: string
    b: number
}

Can we prevent the library from duplicating declarations when using $ref with titles?

yes, I've been working on improve this process and we should address as a bug.

For now, it was correct to merge as this change just inlined some types. The risk of regression would only be in situations where you directly reference a generated type name, but in that instance TSC would help.

@GioSensation where you say,

but it was on the extension repo

Could you point me to where this was occuring? (eg: a branch I can check out locally and see the error?)

You can check the branch in @sixers' fork https://github.com/duckduckgo/duckduckgo-privacy-extension/pull/1608. IIRC, the double declaration created a problem for [key: string]: something where we were basically re-declaring [key: string] twice.

Thanks @GioSensation  I will take a look later on :)


Clicking a Toggle component selects nearby text

If you click quickly on a Toggle component, this will cause the browser to select text on the page. This happens when clicking on the graphical part of the toggle, not the label beside it.
Here's a demonstration of the behaviour on the documentation page, showing how text gets selected alternately above and below the toggle:

This is a question best suited for the upstream library.
https://github.com/carbon-design-system/carbon/issues

I added the issue at the main library here: https://github.com/carbon-design-system/carbon/issues/10881

It looks like the "user-select: none" approach is endorsed by the upstream implementation, so we can apply it here.

Fixed in v0.67.3


Add on not working or me

Hello
I tried using this add on (looks amazing)- however I keep getting an error message. I have no knowledge of source code (noob here) but I'm desperate to have this add on.
Basically this is what I get:
When loading 'Ankimote - remote to control Anki from your phone':
Traceback (most recent call last):
File "aqt/addons.py", line 205, in loadAddons
File "/Users/dbehbehani/Library/Application Support/Anki2/addons21/149004221/init.py", line 351, in
gui_hooks.top_toolbar_did_init_links.append(addlink)
AttributeError: module 'aqt.gui_hooks' has no attribute 'top_toolbar_did_init_links'
Thank you very much

Hi,
What version of anki are you using? Can you try updating?

Hi,
What version of anki are you using? Can you try updating?

Hi
thanks for answering
I wish I could but the latest I can update is Version 2.1.20 (which is the Anki version I have now)
I can't update any further cause my laptop software is version  10.10.5 (yosemite)

Hi
thanks for answering
I wish I could but the latest I can update is Version 2.1.20 (which is the Anki version I have now)
I can't update any further cause my laptop software is version  10.10.5 (yosemite)

That's the problem. Thanks for letting me know, I'll update the listing on ankiweb so it's no longer compatible with 2.1.20

That's the problem. Thanks for letting me know, I'll update the listing on ankiweb so it's no longer compatible with 2.1.20


Top of the line laptop

Like most programmers, you leap before you think.  I have a Dell Alienware m17.... 3 USB 3.1 ports and your hardware check says I have none!

I'm not developing anything, just trying to use the software, I'm having
trouble with the drivers which do not install properly.
On Tue, May 11, 2021 at 11:23 AM Harrison Ferrone @.***>
wrote:

Hi @HillTAP https://github.com/HillTAP - can you give me some more info
on what you're developing?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/mixed-reality/issues/301#issuecomment-839183370,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACMZI7T5MRZY3CT45Y4U573TNGN4TANCNFSM44N2BC5Q
.

--
KWHill

Gotcha, this is a support issue then, as we only deal with the docs side of things.


deps: Upgrade to Expo SDK 44

Following the "bare workflow" instructions for upgrading:
https://blog.expo.dev/expo-sdk-44-4c4b8306584a#8ff0
Marking as a draft because I'd like to use tsflower for some of the dependencies I'm bumping here. 🙂 I've started a discussion.
I've kicked the tires with this revision on iOS and Android, with and without "Debug JS Remotely" activated, and things seem fine.

From the commit message for the upgrade:
When I ran `expo upgrade`, it went through a phase it described as
"Updating packages to compatible versions (where known)." This
changed a lot of version ranges, even of non-Expo things like
react-native-reanimated. I kept some of these and ignored others,
and I plan to elaborate on these choices in the GitHub PR thread. I
didn't find more info in the CLI's docs about how it chooses these
upgrades. I believe the code is
  https://github.com/expo/expo-cli/blob/expo-cli%405.4.12/packages/expo-cli/src/commands/info/upgradeAsync.ts#L541-L597
and that
  https://github.com/expo/expo/blob/sdk-44/packages/expo/bundledNativeModules.json
gets consulted as part of that.

So, here is that elaboration. (Formatted for a commit message because that's where I thought I'd put it, before I decided it's just too long.)
Several proposed upgrades seemed fine to take without much
inspection. Here are some explanations for more interesting ones:

  expo-application: Major-version bump, but the only breaking change
    announced is dropping iOS 11 support, and we've done that:
      https://github.com/expo/expo/blob/main/packages/expo-application/CHANGELOG.md

  expo-screen-orientation:
    - We had upper-bounded this because<EMAIL_ADDRESS>was
      needed to avoid an error we saw with 4.1.0. We ran into
      problems trying to bump expo-modules-core to 0.6.0, with the
      hypothesis that some RN upgrade would fix that issue; see
        https://github.com/zulip/zulip-mobile/pull/5203#issuecomment-1020722398 .
      When we got to RN 0.67 and still saw the error, we found that
      Expo actually has a workaround (it papers over a RN problem),
      and we just have to take the Expo code with that:
        https://github.com/expo/expo/commit/c91d5a3e4#diff-53a846ea04b571c7981cbbab9b69d839993ff6f2982ad4a1a3fd02be5b042652R1-R36 .
      It's available in expo-modules-autolinking 0.4.0, and we get
      it with `expo` 44. I've updated
        https://github.com/zulip/zulip-mobile/pull/5203#issuecomment-1020722398
      with this information.
    - As mentioned in the changelog
        ( https://github.com/expo/expo/blob/main/packages/expo-screen-orientation/CHANGELOG.md#410--2021-12-03 )
      , the setup instructions have been simplified, so we make
      corresponding changes in ios/ZulipMobile/AppDelegate.m and
      ios/ZulipMobile/Info.plist. (Some of the changes in
      AppDelegate.m are unrelated. They're from a diff that we're
      asked to apply, in Expo's upgrade guide.)

  expo-web-browser: Major-version bump, but the only breaking change
    announced is dropping iOS 11 support, and we've done that:
      https://github.com/expo/expo/blob/main/packages/expo-web-browser/CHANGELOG.md

  react-native-gesture-handler:
    - v2 comes with a few announced breaking changes, but none
      should apply to us because we don't use the package directly
      ourselves:
        https://github.com/software-mansion/react-native-gesture-handler/releases/tag/2.0.0 .
      (We added it to satisfy peer-dep requirements for React
      Navigation. We don't get any peer-dep complaints from React
      Navigation when we do this upgrade.)
    - The Expo upgrade guide is apparently wrong in saying
        ( https://blog.expo.dev/expo-sdk-44-4c4b8306584a#d532 )
      that a requirement to use `<GestureHandlerRootView>` is new in
      v2; the v1 doc also mentions the requirement. For why we don't
      use `<GestureHandlerRootView>`, see the code comment we added
      in our 9c6009964.

  jest-expo: A major version bump, but things still seem to work
    fine, and the changelog doesn't start until 46.0.0? :shrug:
      https://github.com/expo/expo/blob/main/packages/jest-expo/CHANGELOG.md

Here are other updates it proposed, and why we aren't taking them:

  @react-native-async-storage/async-storage
    from ^1.13.0 to ~1.15.0,
    so we'd get 1.15.7 instead of 1.17.6
    (a downgrade; good to avoid if possible)

  @react-native-community/netinfo
    from 6.0.0 to 7.1.3,
    so we'd get 7.1.3 instead of 6.0.0
    (see e6d1231f7 for why we've pinned to 6.0.0 for now)

  expo-apple-authentication
    from ^4.0.0 to ~4.1.0,
    so we'd get 4.1.0 instead of 4.2.1
    (a downgrade; good to avoid if possible)

  expo-sqlite
    from ^10.0.0 to ~10.1.0,
    so we'd get 10.1.1 instead of 10.2.0
    (a downgrade; good to avoid if possible)

  react, react-native, and @types/react-native
    downward, so we'd get react-native 0.64.3 instead of 0.67.4
    (we definitely don't want that)

  react-native-reanimated
    from "^2.2.0 <2.3.0" to ~2.3.1
    so we'd get 2.3.3 instead of 2.2.4
    (We'd upper-bounded this because of an error we observed in
      2.3.0, which was reportedly caused by an incompatibility with
      Expo 43. There was hope at the time that it was fixed with
      Expo 44 --
        https://github.com/software-mansion/react-native-reanimated/issues/2702#issuecomment-988743559
      -- and that seems to be true; I don't see an error like that
      if I take this upgrade. However, "Debug JS Remotely" breaks
      with an insta-crash on startup, at least on Android. So if we
      need this upgrade, we should either debug that, or see if we
      agree with a finding that we should…abandon "Debug JS
      Remotely":
        https://github.com/software-mansion/react-native-reanimated/issues/1990#issuecomment-850564351 )

  react-native-safe-area-context
    from ^3.1.7 to 3.3.2,
    so we'd get 3.3.2 instead of 3.4.1
    (a downgrade; good to avoid if possible)

  react-native-screens
    from ^2.10.1 to ~3.10.1,
    so we'd get 3.10.2 instead of 2.18.1
    (we're managing this upgrade as part of upgrading React
      Navigation 6; good to not conflict with that if possible)

  react-native-webview
    from ^11.6.4 to 11.15.0,
    so we'd get 11.15.0 instead of 11.22.2
    (a downgrade; good to avoid if possible)

I assume, all else being equal, it's better to put this in
devDependencies than install it globally, since we want commands to
have consistent results across environments. (The guide we're about
to follow, to upgrade to Expo 44, would have us install it
globally.)

Yeah, agreed.
It comes with a ton of new dependencies, though, and that
might be a reason to not have it in the project.

Hmm. It sure does make the yarn.lock a lot longer, which sounds like it's pulling in a lot of dependencies:
 yarn.lock    | Bin 560322 -> 768341 bytes

But it doesn't increase the total size of node_modules by nearly as much. Before:
$ git checkout main~~ && yarn
$ du -s -BMB node_modules/
1109MB	node_modules/

After:
$ git checkout main~ && yarn
$ du -s -BMB node_modules/
1220MB	node_modules/

So it's adding 111MB of new dependencies, which sounds big… except that we have 1109MB already, so it's only 10%. I think it makes sense to not try to optimize that when the cost would be version skew.

All that reasoning for upgrades to take or not take makes sense. Thanks for the details!
However, "Debug JS Remotely" breaks
      with an insta-crash on startup, at least on Android. So if we
      need this upgrade, we should either debug that, or see if we
      agree with a finding that we should…abandon "Debug JS
      Remotely":
        https://github.com/software-mansion/react-native-reanimated/issues/1990#issuecomment-850564351 )

Hmm, yikes. Ultimately I do expect we'll be on Hermes, and so I guess Hermes Inspector as a result. But until then, we definitely need a way to get a JS debug console. Holding react-native-reanimated back seems like a good plan.

Marking as a draft because I'd like to use tsflower for some of the dependencies I'm bumping here. 🙂

Just sent #5447 for this.

Revision pushed, and this one includes my current revision for #5449. It may be easier to settle that one first.

Just rebased, so this is ready for review. 🙂

Just rebased again, so this is ready for review. 🙂

All looks good -- merging. Thanks for taking care of this upgrade!


Cleanup main routing page and ngrid lists

Sets the main container to absolute,
makes it easier to detect the pages height
ngrid lists can dynamically detect the page height using flexbox,
remove external class injection from list-views,
add "spacer-bottom-60" class for the jitsi-container,
add it everywhere where the jitsi container could hide the content.

ok. Changes some more stuff

Also, contrary to other list views, the scroll bar goes all the way to the top of the screen.

this is actually intended, there is no inline scrolling in this view.


Command 'Beautify file' resulted in an error (command 'HookyQR.beautifyFile' not found)

Hi,
I noticed some closed issues around this but not clear answer as to what's going on.
I had a working VSCode installation but had to reinstall everything from backup. Since then, everytime I run beautify I get the error listed in the title when I try to run Beautify on any file.
I've tried disabling all extensions except for Beautify with no difference.
When I open the console, I see this error message
Activating extension 'HookyQR.beautify' failed: Cannot find module '../core/templatablepattern'
Require stack:
- /Users/joec/.vscode/extensions/hookyqr.beautify-1.5.0/node_modules/js-beautify/js/src/javascript/tokenizer.js
- /Users/joec/.vscode/extensions/hookyqr.beautify-1.5.0/node_modules/js-beautify/js/src/javascript/beautifier.js
- /Users/joec/.vscode/extensions/hookyqr.beautify-1.5.0/node_modules/js-beautify/js/src/javascript/index.js
- /Users/joec/.vscode/extensions/hookyqr.beautify-1.5.0/node_modules/js-beautify/js/src/index.js
- /Users/joec/.vscode/extensions/hookyqr.beautify-1.5.0/node_modules/js-beautify/js/index.js
- /Users/joec/.vscode/extensions/hookyqr.beautify-1.5.0/extension.js
- /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js
- /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-amd.js
- /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-fork.js.

/causedByExtension


fix: mew-input number input bug

https://user-images.githubusercontent.com/9893774/176253432-736ab6f8-0f13-4240-8699-77ae2d8f776c.mp4

This doesn't seem like a component issue as the input should be validated in web's end.


Support readonly view of a multi-select input

Support a 'readonly' version of select inputs with enableMulti: true to render values as readonly tags within a disabled control.
Would be nice to use as a readonlyRenderer for form fields that support multiple values as well.

Closing this -- will continue to see what apps do here in app code.


nh scraper is blocking "Juriscraper" user agent

We are getting a JSONDecodeError in Sentry, but below that there is a 403 Forbidden response
Text:
Access Denied
You don't have permission to access "http://www.courts.nh.gov/content/api/documents?" on this server.
Reference #18.264ede17.1724262770.3c5420e3

https://errors.edgesuite.net/18.264ede17.1724262770.3c5420e3

Headers:
{'Mime-Version': '1.0', 'Content-Type': 'text/html', 'Content-Length': '409', 'Cache-Control': 'max-age=0', 'Date': 'Wed, 21 Aug 2024 17:53:34 GMT', 'Connection': 'close', 'Strict-Transport-Security': 'max-age=86400'}

Sentry Issue: COURTLISTENER-80A
JSONDecodeError: Expecting value: line 1 column 1 (char 0)
  File "requests/models.py", line 974, in json
    return complexjson.loads(self.text, **kwargs)
  File "__init__.py", line 514, in loads
    return _default_decoder.decode(s)
  File "simplejson/decoder.py", line 386, in decode
    obj, end = self.raw_decode(s)
  File "simplejson/decoder.py", line 416, in raw_decode
    return self.scan_once(s, idx=_w(s, idx).end())

JSONDecodeError: Expecting value: line 1 column 1 (char 0)
  File "cl/scrapers/management/commands/cl_scrape_opinions.py", line 413, in handle
    self.parse_and_scrape_site(mod, options)
  File "cl/scrapers/management/commands/cl_scrape_opinions.py", line 376, in parse_and_scrape_site
    site = mod.Site().parse()

While inspecting this problem, I also noticed that the source now has neutral citations
reporters-db seems to support it
In [1]: from eyecite import get_citations
In [2]: get_citations("2024 N.H. 42")
Out[2]: [FullCaseCitation('2024 N.H. 42', groups={'volume': '2024', 'reporter': 'N.H.', 'page': '42'}, metadata=FullCaseCitation.Metadata(parenthetical=None, pin_cite=None, year=None, court=None, plaintiff=None, defendant=None, extra=None))]

To cite an opinion issued after January 1, 2024, review this notice .pdf Icon concerning neutral citation

Notice — Adoption of Neutral Citation Form
Beginning on January 1, 2024, the Supreme Court of New Hampshire
will add a neutral citation form (also referred to as public domain citation) to its
published opinions. Neutral citation is a form of case citation that is
independent of a local or regional reporter. The citation begins with the year
issued, followed by the jurisdiction, and concludes with the opinion number.
For example, the first opinion of the court issued after January 1, 2024, will
receive a citation of 2024 N.H. 1.
Opinions with neutral citation will include individually-numbered
paragraphs. To cite an opinion using neutral citation, the writer will refer to
the paragraph that contains the proposition cited, rather than to the page.
Therefore, a full case citation will include the following: (1) the case name; (2)
the year; (3) the jurisdiction (N.H.); (4) the opinion number for that year; and (5)
the paragraph number(s). For instance, if the information cited is contained in
the fifth and sixth paragraphs of the opinion, the full citation would appear as
follows: Kennedy v. Acme, Inc., 2024 N.H. 1, ¶¶ 5-6. A short cite to the same
material would be Kennedy, 2024 N.H. 1, ¶¶5-6.
Opinions issued after January 1, 2024, will continue to be published in
the New Hampshire Reports until further notice. They will also continue to be
posted to the Supreme Court of New Hampshire website. During this period,
the writer may continue to cite the New Hampshire Reports or may use neutral
citation. Adding the neutral citation form at this time not only enables
opinions of the Supreme Court to be assigned a permanent citation
immediately upon online issuance without waiting for the publication of an
official paginated report, but also prepares for online issuance as the exclusive
method of opinion publication. See RSA 505:8, I.

That's wonderful about the neutral citations. I'd love to figure out who made this happen there, and to chat with them. It looks like we might be able to work the grapevine a bit, according to the contact here: https://github.com/freelawproject/crm/issues/477.
On the substance, let's add this to @flooie's list to ① become friends and applaud their neutral citation usage, and ② get access restored.

About access, I have been testing, and the scraper works by changing the User-Agent and a few other headers, so we can use that provisionally

Great!
On Wed, Aug 21, 2024 at 2:51 PM Rossi @.***> wrote:

About access, I have been testing, and the scraper works by changing the
User-Agent and a few other headers, so we can use that provisionally
—
Reply to this email directly, view it on GitHub
https://github.com/freelawproject/juriscraper/issues/1128#issuecomment-2303070725,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABZ3KV5GTL4MLRTLYUBVZDZSUDUTAVCNFSM6AAAAABM4Q3EHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBTGA3TANZSGU
.
You are receiving this because you commented.Message ID:
@.***>

About the neutral citations, giving it another look, the reporter "N.H." on reporters-db maps to a "STATE" type reporter on Courtlistener, not a "NEUTRAL" type, so, it would not be proper to use that one. We should probably solve that issue before collecting these citations
On the reporter's page, we jump from volume 172 to "volume" 2009, which actually stands for a year:
https://www.courtlistener.com/c/nh/

You're absolutely right, we should fix these before we gather the citations. Very nice catch.


UI Design Guidelines

Hi, I would like to make a mock-up of this with an updated design and also improve the User Experience.
I'd like you to assign this task to me.

Okay sure. Kindly create a new branch for this task.

Hello, I'd like to give a try and make the design for this website, please assign me the task