Avoid KeyError: 'rev' for special repos

Description
pre-commit expects rev to be absent for special repo names:
An error has occurred: InvalidConfigError:
==> File .pre-commit-config.yaml
==> At Config()
==> At key: repos
==> At Repository(repo='local')
=====> Expected rev to be absent when repo is any of ('local', 'meta'), found rev: 'v0.0.0'

Avoid the following exception for these special repo names
Traceback (most recent call last):
  File "/home/christopher.covington/.cache/pre-commit/repoo_r80vol/py_env-python3/bin/piptools_sync", line 8, in <module>
    sys.exit(main())
  File "/home/christopher.covington/.cache/pre-commit/repoo_r80vol/py_env-python3/lib/python3.9/site-packages/piptools_sync/piptools_sync.py", line 468, in main
    yaml_dict = yaml_to_dict(config_file)
  File "/home/christopher.covington/.cache/pre-commit/repoo_r80vol/py_env-python3/lib/python3.9/site-packages/piptools_sync/piptools_sync.py", line 325, in yaml_to_dict
    version = repo["rev"]
KeyError: 'rev'

Checklist - did you ...

[ ] Add a CHANGELOG entry if necessary?
[ ] Add / update tests if necessary?
[ ] Add new / update outdated documentation?

Avoid KeyError: 'rev' for special repos


gollvm: GoStatepoints.cpp:1433:50: error: no member named 'getElementType' in 'llvm::PointerType'

2022-03-10T11:14:16.9117262Z FAILED: tools/gollvm/passes/CMakeFiles/LLVMCppGoPasses.dir/GoStatepoints.cpp.o
2022-03-10T11:14:16.9123244Z /usr/bin/clang++-10 -DGTEST_HAS_RTTI=0 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/build_min/tools/gollvm/passes -I/home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/passes -I/home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/build_min/include -I/home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/include -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -Wmisleading-indentation -fdiagnostics-color -ffunction-sections -fdata-sections -Os -DNDEBUG  -fno-exceptions -fno-rtti -std=c++14 -MD -MT tools/gollvm/passes/CMakeFiles/LLVMCppGoPasses.dir/GoStatepoints.cpp.o -MF tools/gollvm/passes/CMakeFiles/LLVMCppGoPasses.dir/GoStatepoints.cpp.o.d -o tools/gollvm/passes/CMakeFiles/LLVMCppGoPasses.dir/GoStatepoints.cpp.o -c /home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/passes/GoStatepoints.cpp
2022-03-10T11:14:16.9127681Z /home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/passes/GoStatepoints.cpp:1433:50: error: no member named 'getElementType' in 'llvm::PointerType'
2022-03-10T11:14:16.9128685Z       Type *T = cast(V->getType())->getElementType();
2022-03-10T11:14:16.9129281Z                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  ^
2022-03-10T11:14:16.9131080Z /home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/passes/GoStatepoints.cpp:2027:5: warning: misleading indentation; statement is not part of the previous 'if' [-Wmisleading-indentation]
2022-03-10T11:14:16.9132005Z     for (auto Attr : FnAttrsToStrip)
2022-03-10T11:14:16.9133782Z     ^
2022-03-10T11:14:16.9134762Z /home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/passes/GoStatepoints.cpp:2024:3: note: previous statement is here
2022-03-10T11:14:16.9136094Z   if (isa(F.getReturnType()))
2022-03-10T11:14:16.9136576Z   ^
2022-03-10T11:14:16.9137715Z /home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/passes/GoStatepoints.cpp:2182:11: warning: 'insertEdge' is deprecated: Use applyUpdates() instead. [-Wdeprecated-declarations]
2022-03-10T11:14:16.9138447Z       DTU.insertEdge(Old, PadBB);
2022-03-10T11:14:16.9138773Z           ^
2022-03-10T11:14:16.9140973Z /home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/include/llvm/Analysis/DomTreeUpdater.h:159:3: note: 'insertEdge' has been explicitly marked deprecated here
2022-03-10T11:14:16.9141749Z   LLVM_ATTRIBUTE_DEPRECATED(void insertEdge(BasicBlock *From, BasicBlock *To),
2022-03-10T11:14:16.9142128Z   ^
2022-03-10T11:14:16.9142916Z /home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/include/llvm/Support/Compiler.h:319:52: note: expanded from macro 'LLVM_ATTRIBUTE_DEPRECATED'
2022-03-10T11:14:16.9143557Z #define LLVM_ATTRIBUTE_DEPRECATED(decl, message) [[deprecated(message)]] decl
2022-03-10T11:14:16.9144375Z                                                    ^
2022-03-10T11:14:16.9144716Z 2 warnings and 1 error generated.

Thanks. I am working on a patch for this, but I have been bogged down with other tasks.


add nodeId to system-info

as a user I would like others to connect to my node to open channels to me.
insystem-info there is just the alias, not the nodeId
CC @rootzoll

Please name it identity_pubkey to keep the naming consistent with LnInfo.
Was discussed previously in #47

@fusion44 its not just the pubkey ... basically its the advertised node URI: pubkey@lndtor:port should it still be called identity_pubkey?

Hmm no, then not. I'd argue that it better fits into lightning/get-info as it isn't necessarily a system thing. Especially since RaspiBlitz can run without Lightning enabled.

OK https://github.com/fusion44/blitz_api/pull/89 waiting for merge

@cstenglein PR https://github.com/fusion44/blitz_api/pull/89 is merged


[BEAM-13019] Add containsInAnyOrder with matchers to the IterableAssert interface

This lets an existing assertion be usable in the PAssert class.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Thanks for bringing this up on the dev list.
Let us move forward with the change. Please address the test failures requiring the swap to empty().

Done.


:lady_beetle: Fix k8s API's statuses handing in StandardPage component for retrieving resources

When calling k8s hook APIs for retrieving resources, the API returns two statuses:
loaded and error.
See https://github.com/openshift/console/blob/7993fd9f652aac0c4c4f7f83e529a46e799b530c/frontend/packages/console-dynamic-plugin-sdk/src/utils/k8s/hooks/useK8sWatchResources.ts#L144-L163
Based on the code and on debugging, if an error status is returned setting to true, the loaded status is not necessarily set to true as well.
Therefore,  in case of an error when loaded is  false, fixing how we handle it in StandardPage  component is required to display an API failure's error message of "Unable to retrieve data" in the center of the page instead of keep rendering a Loading component.
An example + screenshots:
in the edge case scenario of a non admin user that trying to list the "all namespaces" resources, the API returns an error of "403 Forbidden" and loaded is returned set to false.
The providers page appears as follows before the fix:

And after the fix:

Note: there are other places in code that behaves the same (treats an API  error only if loading is set to true), for example:
https://github.com/kubev2v/forklift-console-plugin/blob/98773d6f51400133391ff3bb54d533e15aaaf0c6/packages/forklift-console-plugin/src/modules/Overview/hooks/useK8sWatchProviderNames.ts#L31
https://github.com/kubev2v/forklift-console-plugin/blob/98773d6f51400133391ff3bb54d533e15aaaf0c6/packages/forklift-console-plugin/src/modules/Providers/views/details/components/CredentialsSection/CredentialsSection.tsx#L40

@yaacov please see comment https://github.com/kubev2v/forklift-console-plugin/pull/1310#issuecomment-2304776148.


Configure a default host

A default host/page should be displayed if the host for a given domain was not found. We could also display a list of available hosts their or even link to available tools.

I using this vagrant because data bags and configuration my partner modified to our uses and remove some features and update this vagrant to ubuntu 14.04.
This data bags help us to configure vhosts independently and add via json file a vhost configurations today only path and domain name and aliases, but will be nice if we can set php version too.
This default host really help to start use your vagrant.

Sorry, I'm not sure I can follow you. What do you request/suggest?

I suggest maybe use data bags for vhosts configuration, because I think with data bags you can add more options to configurations, not only path and domains, but php version, mysql or postgree or mongodb, if use apache or nginx.

I see. Data-bags, how they're used in r8/vagrant-lamp are Chef data-bags, if I'm not wrong. As this Box does not Chef, I can't just implement data-bags easily.
But it's already possible to create custom vhost configurations.

Got it. +1


Allow verbosity to not be called verbosity

(How do I add a test for this)

(Restarted the build, CI should pass now.)
Re tests: I've been meaning to add a good testing story, aside from the doc tests. For now, I'd just add something like examples/verbosity_by_any_other_name_is_still_as_verbose.rs :)

Added an example with the first absurd field name to come to mind.

Added example can now be used to show off -vvv's behavior, and.... it doesn't seem to be doing anything.

Let's land this right now as its a valuable fix. (I'll also add a change log entry.)
bors r+


[examples/io_uring-udp] when  io_uring_register_files(&sockfd), sqe fd is fixed as 0 ?

When after  io_uring_register_files sockfd
https://github.com/axboe/liburing/blob/liburing-2.3/examples/io_uring-udp.c#L363
the sqe fd  would be fixed as 0  like the followings?
https://github.com/axboe/liburing/blob/liburing-2.3/examples/io_uring-udp.c#L369
https://github.com/axboe/liburing/blob/liburing-2.3/examples/io_uring-udp.c#L384

I'm not sure what you are asking, but if you are clarifying then yes that looks correct.
I would say the fd is not fixed as 0, but the fd is registered to index 0 when using IOSQE_FIXED_FILE


B 20915

INT PRs
##INT PR

Any reason why your file counts are so different?
I see two different INT PRs that changed ~1,500 lines of code, but this one is changing 4k+?

Any reason why your file counts are so different?
I see two different INT PRs that changed ~1,500 lines of code, but this one is changing 4k+?

confused on what you are saying?
since its db migration- each int pr would require a new migration file

Is there a int PR/branch that contains your<PHONE_NUMBER>0315_update_pws_violations_pt2.up.sql migration to confirm that made it? I'm seeing the part 1 and part 2 for the int PRs

https://github.com/transcom/mymove/commit/072980d98775d34336d7fe337297a73831bd9921
not sure what happened to the PR, but its in integration


PLAT-10466 - Handle Null Events gracefully

Ticket
PLAT-10466
Description
In certain cases a null event can be passed to the bot in the Datafeed v5 endpoint and we try to log all event ids where a null will not have one and crash the bot.

@anthony-symphony Could you update your branch against master please? It looks like it is outdated and does not include the circleci configuration.

Mmm that's weird I was able to push more commits to your branch but they don't appear in the PR
@anthony-symphony do you see a allow edits for maintainers checkbox in the PR?

This was built off master so whatever is in master should already be there. I originally made a PR against 1.3 branch but, it looks like that was behind.


Merge master into dev

IBM Cloud toolchain: Delivery Pipeline deployed LRP-web-app to dev, including commit dd2f59c5118fb00f4005cca50441dc292e74447c

IBM Cloud toolchain: Delivery Pipeline deployed LRP-web-app to dev, including commit 649d43ec6113ac9f113d3ad2582d25d4a94cb9b1

IBM Cloud toolchain: Delivery Pipeline deployed LRP-web-app to test, including commits 649d43ec6113ac9f113d3ad2582d25d4a94cb9b1, dd2f59c5118fb00f4005cca50441dc292e74447c

IBM Cloud toolchain: Delivery Pipeline deployed LRP-web-app to prod, including commits 649d43ec6113ac9f113d3ad2582d25d4a94cb9b1, dd2f59c5118fb00f4005cca50441dc292e74447c


Fix toggling JS Assistant

[Issue] https://github.com/Samsung/TAU-Design-Editor/issues/227
[Problem] JS Assistant toggle is not working properly when index.js is not included
[Reason] Toggling is invoking function to create index.js when it not exists in document.
When script is inserted it emits event to generate TAU component. Because inserted element
is not TAU component info structure is null
[Solution] Add null check for info structure
Signed-off-by: Lukasz Slachciak<EMAIL_ADDRESS>

Looks well and works well. :)


Buttons are not all displaying event though there is room, most are in the button overflow dialog

Jodit Version: 3.2.21
Code
  var jodit = new Jodit(element, {
      enter: 'DIV',
      removeButtons: 'fullsize',
      allowResizeX: true,
      width: 718,
      toolbarButtonSize: 'small'
    });

Expected behavior:
All buttons appear on the toolbar
Actual behavior:
Only some buttons appear on the toolbar

Disable adaptive https://xdsoft.net/jodit/play.html?toolbarAdaptive=false&currentTab=Buttons 12.11.2018, 19:05, "Netanel Livni" notifications@github.com:Jodit Version: 3.2.21Code  var jodit = new Jodit(element, {
     enter: 'DIV',
     removeButtons: 'fullsize',
     allowResizeX: true,
     width: 718,
     toolbarButtonSize: 'small'
   });Expected behavior:All buttons appear on the toolbarActual behavior:Only some buttons appear on the toolbar—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.  -- С Уважением,Чупурнов Валерий


Automatically output a "fix this FAIL" template message to be posted on upstream font repo issue trackers

@eliheuer said in an email:
I wish it were easier to create issues in upstream repos while using FontBakery. Here is an example "user story".
I run a font through Fontbakery and get a fail for "com.google.fonts/check/varfont_weight_instances" with the following message: This should instead be a multiple of 100. [code: bad-coordinate]
Now, I know I need to make an issue in the upstream repo to fix this. So I look for the rational in the source code and get this.
The named instances on the weight axis of a variable font must have coordinates that are multiples of 100 on the design space.
I can make an issue or PR to the upstream repo just saying that it fails the test, but it would be much more likely to be merged and not annoy the maintainer if I explained why the change should happen.
In this situation, I would need to research and compose an explanation for the issue, but it would be way easier if we had an already written description for why the change is needed, ready to paste into an issue.
This is somewhat related to removing dogma and improving the rationales.

This seems to be similar, but not identical, to the request at issue #2090


"Failed to load entity types" after upgrade to release-2021-06-24

After upgrading from release-2021-06-17.1 to release-2021-06-24 an error occurs on catalog page (/catalog) and the entity type picker is not shown.
Expected Behavior
Loading catalog page should work w/o errors.
Current Behavior
An error occurs on catalog page (/catalog) and the entity type picker is not shown, after import entity of type Location.
In the console following message is shown:
Cannot update a component (`AlertDisplay`) while rendering a different component (`EntityTypePicker`). To locate the bad setState() call inside `EntityTypePicker`, follow the stack trace as described in https://fb.me/setstate-in-render
    in EntityTypePicker (created by CatalogPage)
    in div (created by CatalogPage)
    in EntityListProvider (created by CatalogPage)
    in div (created by CatalogPage)
    in article (created by Content)
    in Content (created by CatalogPage)
    in div (created by Page)
    in ThemeProvider (created by Page)
    in Page (created by CatalogLayout)
    in CatalogLayout (created by CatalogPage)
    in CatalogPage (created by RoutableExtension(CatalogPage))
    in RoutableExtension(CatalogPage) (created by Extension(Component))
    in PluginErrorBoundary (created by Extension(Component))
    in Suspense (created by Extension(Component))
    in Extension(Component) (at App.tsx:80)
    in Route (at App.tsx:80)
    in FlatRoutes (at App.tsx:78)
    in div (created by SidebarPage)
    in SidebarPage (at Root.tsx:74)
    in Root (at App.tsx:107)
    in Route (created by AppRouter)
    in Routes (created by AppRouter)
    in SignInPageWrapper (created by AppRouter)
    in Router (created by BrowserRouter)
    in BrowserRouter (created by AppRouter)
    in AppRouter (at App.tsx:106)
    in RoutingProvider (created by Provider)
    in CssBaseline (created by WithStyles(CssBaseline))
    in WithStyles(CssBaseline) (created by AppThemeProvider)
    in ThemeProvider (created by AppThemeProvider)
    in AppThemeProvider (created by Provider)
    in AppContextProvider (created by Provider)
    in ApiProvider (created by Provider)
    in Provider (at App.tsx:103)
    in App (at src/index.tsx:6)

Possible Solution

Steps to Reproduce

Upgrade standalone app from release-2021-06-17.1 to release-2021-06-24
Import entity of type Location
Navigate to /catalog

Context

Your Environment

NodeJS Version (v12): 14.17.0
Operating System and Version (e.g. Ubuntu 14.04): PopOS 20.10
Browser Information: Opera v76.0.4017.123

Closed, because I missed the necessary changes for<EMAIL_ADDRESS>from release (release-2021-06-17)https://github.com/backstage/backstage/releases/tag/release-2021-06-17.
After made changes to catalog.ts everything works as expected.

I'm getting the same issue using the old catalog backend and I don't think it is actually fixed yet.
The problem is that the code that was added in https://github.com/backstage/backstage/pull/6093 (sort the entities in the catalog client) can break if field filters are involved, as done in the EntityTypeFilter:
https://github.com/backstage/backstage/blob/1d1b197a65660d7a4e7a9ffed9dfaac3152b62ff/plugins/catalog-react/src/hooks/useEntityTypeFilter.tsx#L53-L57
We then get the following exception:
TypeError: Cannot read property 'toLowerCase' of undefined
    at stringifyEntityRef (index.esm.js:908)
    at refCompare (index.esm.js:33)
    at Array.sort (<anonymous>)
    at CatalogClient.getEntities (index.esm.js:43)
    at async CatalogClientWrapper.getEntities (index-de361881.esm.js:1249)
    at async eval (index.esm.js:329) "\n    at EntityTypePicker (webpack-internal:///../../node_modules/@backstage/plugin-catalog-react/dist/index.esm.js:855:93)\n    at div\n    at EntityListProvider (webpack-internal:///../../node_modules/@backstage/plugin-catalog-react/dist/index.esm.js:200:3)\n    at div\n    at article\n    at Content (webpack-internal:///../../node_modules/@backstage/core-components/dist/index.esm.js:2918:3)\n    at div\n    at ThemeProvider (webpack-internal:///../../node_modules/@material-ui/styles/esm/ThemeProvider/ThemeProvider.js:42:24)\n    at Page (webpack-internal:///../../node_modules/@backstage/core-components/dist/index.esm.js:4474:16)\n    at CatalogLayout (webpack-internal:///../../node_modules/@backstage/plugin-catalog/dist/esm/index-de361881.esm.js:294:25)\n    at CatalogPage (webpack-internal:///../../node_modules/@backstage/plugin-catalog/dist/esm/index-de361881.esm.js:545:3)\n    at RoutableExtensionWrapper (webpack-internal:///../../node_modules/@backstage/core-plugin-api/dist/index.esm.js:422:13)\n    at PluginErrorBoundary (eval at ES6ProxyComponentFactory (webpack-internal:///../../node_modules/react-hot-loader/dist/react-hot-loader.development.js), <anonymous>:14:7)\n    at Suspense\n    at Result (webpack-internal:///../../node_modules/@backstage/core-plugin-api/dist/index.esm.js:470:21)\n    at D (webpack-internal:///../../node_modules/react-router/index.js:34:673)\n    at FlatRoutes (webpack-internal:///../../node_modules/@backstage/core-app-api/dist/index.esm.js:2623:88)\n    at div\n    at SidebarPage (webpack-internal:///../../node_modules/@backstage/core-components/dist/index.esm.js:4541:89)\n    at Root (webpack-internal:///./src/components/Root/Root.tsx:92:17)\n    at D (webpack-internal:///../../node_modules/react-router/index.js:34:673)\n    at E (webpack-internal:///../../node_modules/react-router/index.js:37:804)\n    at SignInPageWrapper (webpack-internal:///../../node_modules/@backstage/core-app-api/dist/index.esm.js:2240:18)\n    at x (webpack-internal:///../../node_modules/react-router/index.js:36:23)\n    at w (webpack-internal:///../../node_modules/react-router-dom/index.js:63:23)\n    at AppRouter (webpack-internal:///../../node_modules/@backstage/core-app-api/dist/index.esm.js:2252:25)\n    at RoutingProvider (webpack-internal:///../../node_modules/@backstage/core-app-api/dist/index.esm.js:1933:3)\n    at CssBaseline (webpack-internal:///../../node_modules/@material-ui/core/esm/CssBaseline/CssBaseline.js:65:31)\n    at WithStyles (webpack-internal:///../../node_modules/@material-ui/styles/esm/withStyles/withStyles.js:61:31)\n    at ThemeProvider (webpack-internal:///../../node_modules/@material-ui/styles/esm/ThemeProvider/ThemeProvider.js:42:24)\n    at AppThemeProvider (webpack-internal:///../../node_modules/@backstage/core-app-api/dist/index.esm.js:2070:28)\n    at AppContextProvider (webpack-internal:///../../node_modules/@backstage/core-app-api/dist/index.esm.js:1978:3)\n    at ApiProvider (webpack-internal:///../../node_modules/@backstage/core-app-api/dist/index.esm.js:145:3)\n    at Provider (webpack-internal:///../../node_modules/@backstage/core-app-api/dist/index.esm.js:2166:24)\n    at App"

The reason why it works with the new catalog backend is that the fields functionality is not implemented there and the new catalog backend always returns all fields. But I'm not sure if this is this a bug or a feature? @freben @Rugvip @benjdlambert


Union Type Not Inferred from Function that Returns a Boxed Type.

🔎 Search Terms
type parameter multiple return types boxed type union type inference
🕗 Version & Regression Information
This is the behavior in every version I tried, and I reviewed the FAQ for entries about Generics.
This is similar too, but slightly different than, Why doesn't type inference work on this interface: interface Foo<T> { }?.
⏯ Playground Link
https://www.typescriptlang.org/play?ts=5.2.2#code/C4TwDgpgBAQg9gDwDwBUB8UC8UDeVgAWAlgHYDmAXFClAL4DcAUKJFAGJxwDqRhqG2ABQBKLBnjJ0TRgDMAriQDGwInBJQZnEbkZQoRGVEEBZAIaEAdACdTJACZwAttsyuoABgsBmUVYjA5K3U8QlJKKC86Jj0DIzNLG3snFzdPAFZff0Dg-GJyKgAiYgKo3Sg-AKDcXLCqYCs5aAZGWkZZBWVVdQAjUyt+QU04Kg5uXgJ+YSoaHDKK7I0tYQtQ8iZWxkU1AGdgKF6ALyx9vsHOYSYgA
💻 Code
type Box<T> = { thing: T };
type FooWith<T> = () => Box<T>;

function foo() {
  if (Math.random() === 0.3) return { thing: 3 };
  if (Math.random() === 0.5) return { thing: "hi" };
  return { thing: true };
}

function bar<T>(foo: FooWith<T>): T {
  return foo().thing;
}

const baz = bar(foo);

🙁 Actual behavior
Typescript errors when the function foo is past to the function bar.
// Argument of type '() => { thing: number; } | { thing: string; } | { thing: boolean; }' is not assignable to parameter of type 'FooWith<number>'.
// $ExpectError Type 'string' is not assignable to type 'number'.
const baz = bar(foo);
//    ^? const baz: number

🙂 Expected behavior
There is no error and Typescript infers the type as 3 | "hi" | true.
const baz = bar(foo);
//    ^? const baz: 3 | "hi" | true

Additional information about the issue
Without the boxed type it works as expected.
type FooWith<T> = () => T;

function foo() {
  if (Math.random() === 0.3) return 3;
  if (Math.random() === 0.5) return "hi";
  return true;
}

function bar<T>(foo: FooWith<T>): T {
  return foo();
}

const baz = bar(foo);
//    ^? const baz: true | 3 | "hi"

I'm also able to get it to infer a union type with this alternative syntax.
type Box<T> = { thing: T };
type fooWith<T> = () => Box<T>;

function foo() {
  if (Math.random() === 0.3) return { thing: 3 };
  if (Math.random() === 0.5) return { thing: "hi" };
  return { thing: true };
}

function bar<F extends fooWith<unknown>>(foo: F) {
  return foo().thing as F extends fooWith<infer T> ? T : never;
}

const baz = bar(foo);
//    ^? const baz: string | number | boolean

However, this is a simplified example of what I'm trying to accomplish and the alternative syntax does not work for what I'm trying to accomplish. I need the union type to be inferred by the type parameter.
Thank you for taking the time to read this bug report and I appreciate any response.

@RyanCavanaugh Thanks for the reply. That video was informative but I'm not sure the algorithm is capturing my intent. Let me share with you what I am trying to accomplish. I have a flow function, inspired by Akka Streams, with the following signature:
/**
 *      +------+
 * In ~>|      |~> Out
 *      +------+
 */
export type Flow = <
  const In,
  const Out,
  const Error,
>(
  data: In
) =>
  | Continue<Out>
  | Fail<Error>;

A flow has an input and an output and may raise an error in a type-safe way (instead of just throwing). I'm trying to create an append function that can squash to flows together to create a composite flow.
/**
 * Takes 2 flows and squashes them together.
 *       +------+                 +------+                +------+
 * In1 ~>|      |~> Out1 ++ In2 ~>|      |~> Out2 = In1 ~>|      |~> Out2
 *       +------+                 +------+                +------+
 */
declare function append<
  const UpIn,
  const UpOut,
  const UpError,
  const DownOut,
  const DownError
>(
  upstream: FlowWith<UpIn, UpOut, UpError>,
  downstream: FlowWith<UpOut, DownOut, DownError>
): FlowWith<
  UpIn,
  DownOut,
  ExcludeUnknown<UpError> | ExcludeUnknown<DownError>
>;

This works great until you consider that a flow may have many conditional Continue or Fail branches.
const flow1 = (data: number) => {
  if (Math.random() === 0.1) return Fail(new MyError("💣"))
  if (Math.random() === 0.5) return Fail(new MyOtherError("💣"))
  return Continue("test");
};

const flow2 = <T,>(data: T) => {
  return Continue(data);
};

const flow3 = append(flow1, flow2);
//    ^? const flow3: FlowWith<number, "test", MyError | MyOtherError>

Is it not possible to type something like this with TypeScript? Should I be doing something different? Here is a playground link for the above example
Thanks!

I was able to get this to work by allowing Typescript to infer the return value and then writing some conditional types to pluck the types out of the box. For the example provided that looks like this.
type Box<T> = { thing: T };
type BoxType<T> = T extends Box<infer U> ? U : never;

function foo() {
  if (Math.random() === 0.3) return { thing: 3 };
  if (Math.random() === 0.5) return { thing: "hi" };
  return { thing: true };
}

function bar<B extends Box<unknown>>(foo: () => B): BoxType<B> {
  return foo().thing as BoxType<B>;
}

const baz = bar(foo);
//    ^? const baz: string | number | boolean

With this strategy I am able to type my append function as I hoped. Thanks again, That video was helpful!


Add config files for cluster wide setup

Add manifest files, Helm charts and other setup files for cluster wide services such as

[x] manifest files to persistent volumes
[x] manifest files for ingress and ingress controllers
[x] scripts to setup app namespaces and  kubectl config files (context definitions)
[x] cron script that updates Let's Encrypt certificate (replaced with cert-manager)

All tasks in this issue have been completed.


background color is not consistent in Web and other Platforms

Steps to Reproduce

Execute flutter run on the code sample

Expected results: To see same screen color in each platform.
Actual results: Windows (Desktop), Android and iOS show black screen, but (at least) Chrome and Edge show white screen.

Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(Container());
}

Logs
[√] Flutter (Channel stable, 3.3.10, on Microsoft Windows [Version 10.0.19045.2486], locale de-DE)
    • Flutter version 3.3.10 on channel stable at C:\src\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 135454af32 (5 weeks ago), 2022-12-15 07:36:55 -0800
    • Engine revision 3316dd8728
    • Dart version 2.18.6
    • DevTools version 2.15.0

[√] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at C:\Users\Julian\AppData\Local\Android\sdk
    • Platform android-33, build-tools 33.0.1
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Professional 2022 17.4.2)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Professional
[√] Connected device (4 available)
    • SM X200 (mobile)  • R9YT60RH43P • android-arm64  • Android 13 (API 33)
    • Windows (desktop) • windows     • windows-x64    • Microsoft Windows [Version 10.0.19045.2486]
    • Chrome (web)      • chrome      • web-javascript • Google Chrome 109.0.5414.74
    • Edge (web)        • edge        • web-javascript • Microsoft Edge 109.0.1518.55

[√] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Closing as duplicate of https://github.com/flutter/flutter/issues/107596. Please follow-up in it for further updates.


feat(stream): add Left + Right, Semi + Anti streaming hash join

What's changed and what's your intention?
Add Left + Right, Semi + Anti streaming hash join
Changes: some refactoring into a chunk builder to take into account differing behaviour across join type and update side.
Checklist

[x] I have written necessary docs and comments
[x] I have added necessary unit tests and integration tests

Refer to a related PR or issue link (optional)
Closes: https://github.com/singularity-data/risingwave/issues/1924

@skyzh could you recommend how to easily test this PR on tpch query 4 with test data?

In TPC-H e2e tests,
https://github.com/singularity-data/risingwave/blob/main/e2e_test/v2/streaming/tpch_snapshot.slt
Enable Q4, Q18, Q20 and you'll see if left semi join works.

Note that it is possible LeftSemiJoin is implemented correctly, but other parts have some small issues.

I noticed some bugs while reviewing. Perhaps those will not prevent you from passing the test, but if they did please try merging #2398.

e2e failed https://github.com/singularity-data/risingwave/runs/6359516396?check_suite_focus=true

Maybe we should ignore e2e in this PR, and fix in next PR?

Actually I managed to fix e2e tests. Thanks to merging main with https://github.com/singularity-data/risingwave/pull/2363 ;)

@yuhao-su seems it needs AWS credentials to run

CI runs in the branch https://github.com/singularity-data/risingwave/tree/forks/2387 (Don't click approve and run in the PR cc @yuhao-su)
Sorry for the inconvenience. We will migrate to new CI to avoid such problems soon.


Git clone fails due to trusted protection for netrc

Component
server, agent
Describe the bug
Seems like the normal clone step fails on next-101e684059 when the repo is not trusted due to the "Only inject netrc credentials into trusted containers" option that is now set by default
Is that a bug or am I doing something wrong ?
System Info
next-101e684059

Additional context
My CLone config:
clone:
  git:
    image: woodpeckerci/plugin-git
    settings:
      tags: true
    when:
      event: tag

Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
[X] Check that this is a concrete bug. For Q&A join our Discord Chat Server or the Matrix room.

well there is an edgecase: if you did set your gitea to always need login, you have to set WOODPECKER_AUTHENTICATE_PUBLIC_REPOS=true for the server

A faced this issue a long before 101e684059 with config below:
clone:
  git:
    image: woodpeckerci/plugin-git
    settings:
      partial: false
      depth: 2

Just disabled Only inject netrc credentials into trusted containers. And as I remember without custom settings it worked as expected.

can you point me to how I do setup trusted images ?

Me too.

If you have not set it yourself by default this one should be trusted

Didn't do anything special...
Woodpecker next-556607b525, Kubernetes backend, private repo in Gitea.
clone:
  git:
    image: woodpeckerci/plugin-git
    settings:
      partial: false
      depth: 2

Only inject netrc credentials into trusted containers = On
+ git init -b main
Initialized empty Git repository in /woodpecker/src/gitea.example.com/user/repo/.git/
+ git remote add origin https://gitea.example.com/user/repo.git
+ git fetch --no-tags --depth=2 origin +main:
fatal: could not read Username for 'https://gitea.example.com': No such device or address
exit status 128

My bad, without settings doesn't work too:
clone:
  git:
    image: woodpeckerci/plugin-git

Only inject netrc credentials into trusted containers = On
+ git init -b main
Initialized empty Git repository in /woodpecker/src/gitea.example.com/user/repo/.git/
+ git remote add origin https://gitea.example.com/user/repo.git
+ git fetch --no-tags --depth=2 origin +main:
fatal: could not read Username for 'https://gitea.example.com': No such device or address
exit status 128

Without special clone directives (using default clone step) works:
Only inject netrc credentials into trusted containers = On
+ git init -b main
Initialized empty Git repository in /woodpecker/src/gitea.example.com/user/repo/.git/
+ git remote add origin https://gitea.example.com/user/repo.git
+ git fetch --no-tags --depth=1 --filter=tree:0 origin +refs/heads/main:
From https://gitea.example.com/user/repo
 * branch            main       -> FETCH_HEAD
 * [new branch]      main       -> origin/main
+ git reset --hard -q 9cf746c3bf1af06f537ea80c920c700cd8d48dc1
+ git submodule update --init --recursive
+ git lfs fetch
fetch: Fetching reference refs/heads/main
+ git lfs checkout

With disabled flag:
clone:
  git:
    image: woodpeckerci/plugin-git
    settings:
      partial: false
      depth: 2

Only inject netrc credentials into trusted containers = Off
+ git init -b main
Initialized empty Git repository in /woodpecker/src/gitea.example.com/user/repo/.git/
+ git remote add origin https://gitea.example.com/user/repo.git
+ git fetch --no-tags --depth=2 origin +main:
From https://gitea.example.com/user/repo
 * branch            main       -> FETCH_HEAD
 * [new branch]      main       -> origin/main
+ git reset --hard -q b17d1a229b712f8ca0d9740eba730ed83e332d88
+ git submodule update --init --recursive
+ git lfs fetch
fetch: Fetching reference refs/heads/main
+ git lfs checkout

I am seeing a similar issue in one of our pipelines atm which could be related but could also be a different one:
When having a second .yaml file which has a depends_on on a previous one, the clone step fails with fatal: could not read Username for.
Yet when running the identical pipeline without the depends_on directly without changing anything else, the clone step succeeds.
Only inject netrc credentials into trusted containers is OFF for the repo.
next-7e708874

https://github.com/woodpecker-ci/woodpecker/blob/b616a822a068ef81aa47c6d1857524388ab23f6a/pipeline/frontend/yaml/compiler/compiler.go#L193-L198

I guess this part is a bit to strick. Currently you would need to use docker.io/woodpeckerci/plugin-git:2.0.3 as image name.
func (c *Container) IsTrustedCloneImage() bool {
+	return c.IsPlugin() && slices.Contains(constant.TrustedCloneImages, c.Image)
}

We could use some kind of normalize function for c.Image to be more flexible doing things like:

woodpeckerci/plugin-git:2.0.3 => docker.io/woodpeckerci/plugin-git:2.0.3
woodpeckerci/plugin-git => docker.io/woodpeckerci/plugin-git:latest


pull request for e2e test at 12/22/2016 17:45:17

:white_check_mark: Validation status: passed
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.


Add computed row or use a formula when using SHOW TOTAL

Hi,
I'm using Kibana 7.10 and I have a question regarding computed columns:
I've added the Show Total (SUM function) and I added a  computed column which computes the variance between 2 values.

Now, in the Total Sum row instead of  the Variance column being the total Sum of the variances above, is there any way that I can also use a formula to get the variance of the TOTAL SUM row by using a formula? Because what it's currently doing is adding all of the Variance which makes sense since the function is SUM.
Also, thank you for this wonderful plugin.
Best regards

Hi,
you can do that, by checking “compute column total using formula” in your computed column settings.

Hi Fabien,
Sorry to re-open this but I tried doing the same thing now with strings as the title column but it still doesn't show the total based on the formula.
This is my computed formula settings:

Below is the output:

Any idea or it might be a bug? Thank you in advance.

Well, I just tried to reproduce your issue.
And I get also a buggy result. My result seems to be a bit different, because I get 0% as total.
I will try to fix the bug in a next release.
Waiting this, here's a workaround that works for my test:
((col(2, 0)  * 2) - col(1, 0)) / col(1, 0.1)
That is to say: use column index to reference columns instead of column labels.

Great news: Enhanced Table v1.13.0 is out with this issue fixed!
Numerous other enhancements are also available.
Check it there:
https://github.com/fbaligand/kibana-enhanced-table/releases/tag/v1.13.0


Add ZEST: ZEroShot learning from Task descriptions

Adds the ZEST dataset on zero-shot learning from task descriptions from AI2.

Webpage: https://allenai.org/data/zest
Paper: https://arxiv.org/abs/2011.08115

The nature of this dataset made the supported task tags tricky if you wouldn't mind giving any feedback @yjernite. Also let me know if you think we should have a other-task-generalization or something like that...

Looks good to me, we can ping the authors for more info later. And yes apply other-task labels liberally, we can sort them out later :)
Looks ready to merge when you're ready @joeddav


".to is not supported for 4-bit or 8-bit bitsandbytes models" when i use load_best_model_at_end=True in QLoRa

I ran the qlora example by adding load_best_model_at_end=True and got ValueError: .to is not supported for 4-bit or 8-bit bitsandbytes models. Please use the model as it is, since the model has already been set to the correct devices and casted to the correct dtype.
Environment info

adapters version: 0.2.0
Platform: google colab / windows
Python version:  3.10.12 / 3.11
PyTorch version (GPU?): 2.2.1+cu121
Using GPU in script?: yes
Using distributed or parallel set-up in script?: no

Information
Model I am using (Bert, XLNet ...): llama 2
Language I am using the model on (English, Chinese ...): multi
Adapter setup I am using (if any): LORA
The problem arises when using:

[X] the official example scripts: (give details below) QLORA example
[ ] my own modified scripts: (give details below)

To reproduce
Steps to reproduce the behavior:

open QLoRA_Llama_Finetuning.ipynb
replace bf16 to fp16 in TrainingArguments because of google colab
add load_best_model_at_end=True, metric_for_best_model='eval_loss' in TrainingArguments
start notebook

Full error:

Full error:
   ValueError                                Traceback (most recent call last)
[<ipython-input-26-3c886d1bd8b7>](https://localhost:8080/#) in <cell line: 13>()
     11 )
     12
---> 13 trainer.train()

4 frames
[/usr/local/lib/python3.10/dist-packages/transformers/trainer.py](https://localhost:8080/#) in train(self, resume_from_checkpoint, trial, ignore_keys_for_eval, **kwargs)
   1778                 hf_hub_utils.enable_progress_bars()
   1779         else:
-> 1780             return inner_training_loop(
   1781                 args=args,
   1782                 resume_from_checkpoint=resume_from_checkpoint,

[/usr/local/lib/python3.10/dist-packages/transformers/trainer.py](https://localhost:8080/#) in _inner_training_loop(self, batch_size, args, resume_from_checkpoint, trial, ignore_keys_for_eval)
   2239                 smp.barrier()
   2240
-> 2241             self._load_best_model()
   2242
   2243         # add remaining tr_loss

[/usr/local/lib/python3.10/dist-packages/adapters/trainer.py](https://localhost:8080/#) in _load_best_model(self)
    223                 if os.path.exists(fusion_dir):
    224                     model.load_adapter_fusion(fusion_dir)
--> 225         model.to(self.args.device)
    226
    227

[/usr/local/lib/python3.10/dist-packages/accelerate/big_modeling.py](https://localhost:8080/#) in wrapper(*args, **kwargs)
    454                     if param.device == torch.device("meta"):
    455                         raise RuntimeError("You can't move a model that has some modules offloaded to cpu or disk.")
--> 456                 return fn(*args, **kwargs)
    457
    458             return wrapper

[/usr/local/lib/python3.10/dist-packages/transformers/modeling_utils.py](https://localhost:8080/#) in to(self, *args, **kwargs)
   2552         # Checks if the model has been loaded in 8-bit
   2553         if getattr(self, "quantization_method", None) == QuantizationMethod.BITS_AND_BYTES:
-> 2554             raise ValueError(
   2555                 "`.to` is not supported for `4-bit` or `8-bit` bitsandbytes models. Please use the model as it is, since the"
   2556                 " model has already been set to the correct devices and casted to the correct `dtype`."

ValueError: `.to` is not supported for `4-bit` or `8-bit` bitsandbytes models. Please use the model as it is, since the model has already been set to the correct devices and casted to the correct `dtype`.

Expected behavior
adapter trainer loads the best model at the end

Thanks for reporting this bug, should be fixed once #699 is merged.

I had this errorAttributeError: 'LlamaForCausalLM' object has no attribute 'adapter_to'

Are you using the latest library version from our main branch? These changes haven't been pushed to pypi yet.


Chart showing how many tokens unlock when

Show a chart on the Tranches page to show how overview of how many tokens unlock and when

This was tested and signed on Staging 2 - https://staging2.token.vega.xyz/tranches
Able to access the chart even without connected with a Eth or Vega Wallet.
The chart works well with resizing and different screen sizes


Question: What's the value of GlucoseRxMessage.timestamp?

GlucoseRxMessage.timestamp is a 32bit unsigned int. Is this the unix timestamp or some other representation of the datetime of the glucose value?

It's seconds since the transmitter was first activated. Once this value reaches 105 days or so, the transmitter shuts off.

On Jan 26, 2016, at 4:12 AM, Dennis Gove<EMAIL_ADDRESS>wrote:
GlucoseRxMessagetimestamp is a 32bit unsigned int Is this the unix timestamp or some other representation of the datetime of the glucose value?
—
Reply to this email directly or view it on GitHub.


Inplace operation error in gradient computation

I have come across this error when trying to train. After a bit of google searching, it seems that something is being updated during the gradient computation before it should be. I was hoping you could help me locate the error and let me know what I need to fix as I am not too familiar with pytorch. I have made no modifications to the utils/nn/tools.py script.

I have solved the issue by changing all the inplane operations (here)[https://github.com/hqucms/weaver/blob/master/utils/nn/model/ParticleNet.py#L183-L184] and (here)[https://github.com/hqucms/weaver/blob/master/utils/nn/model/ParticleNet.py#L265-L272] to non-inplace. Essentially the change is var1 = var2 was changed to var1 = var1var2.

Hi @cgsavard -- can you share the pytorch version? I don't seem to be able to reproduce this error in e.g., 1.12.1.

Yes, this occurred after I installed pytorch in this way "conda install pytorch torchvision torchaudio cudatoolkit=11.6 -c pytorch -c conda-forge" because I was working on a different GPU (K40) with a version of CUDA >11.6 (11.7). The pytorch version was the stable 1.12.1 and so I think it was actually the newer CUDA version that raised the issue.

I tested CUDA 11.6 + PyTorch 1.12.1 and still cannot reproduce this error. Did you change anything else when the problem got solved?


fix scrutinizer error handling

At the moment we're doing this:

I'm going to be quite busy in the next week or so, but I'm happy to pick this up after that and add some tests for this service. 😉


[Task]: Update/Create new scheduled task trigger (cronjob) in Appsmith server to also fetch EXTERNAL type plugins from Cloud services

SubTasks

Update/Create new scheduled task trigger (cronjob) already present to fetch REMOTE plugins from Cloud services to also include EXTERNAL type plugins.

Hey team! Please add your planning poker estimate with Zenhub @AmanAgarwal041 @sneha122


[REVIEW]

LinkFree link
https://linkfree.eddiehub.io/LinuxGamer

Lots of views, where do you use the link?
Looks great 👍

maybe use markdown in the bio


Add instructions for pnpm

Is your feature request related to a problem? Please describe.
Currently repository has instructions only for npm
Describe the solution you'd like
Improve Readme and add a section for pnpm
Additional context
See the popular repositories where describe npm and pnpm sections
See the contributing guide.

hey @dipiash please assign this issue to me i think i can help you with it🚀

Hey @Vidhanvyrs!
Done it

Hi, @Vidhanvyrs!
Do you want to continue this issue?

Hi, @Bhavya-Chawla!
Thank you for yours interest. Let's try to get answer from @Vidhanvyrs because @Vidhanvyrs was first 🙏

Sure. Just ping me if @Vidhanvyrs don't want to continue. Thanks :)

hey @dipiash i am working on this issue surely will generate a PR by today


Update README.md

Add your thoughts on Android OS in README.md on master using the following format:
- <your-thoughts-here> ~ [<your-full-name>](<your-github-profile-link)
For example:
- Simple, Fast, Customisable ~ [Sambhav Jain](https://github.com/sambhav2612)

Commit the changes as thoughts: <your-github-usrrname>
Please note that ANY SORT OF RANT FOR ANY FIRM OR COMPANY IS NOT ALLOWED. If anyone is found doing so s/he shall become banned from contributing to this repository.
Thanks for stopping by!

Hey @sambhav2612 ,
Request you to please check and approve this PR [https://github.com/sambhav2612/thoughts-on-android/pull/12]
Thanks Again!


[fixed] clear the delayed close timer when modal opens again.

Continuation of the fix #134. Look at this PR (#134) for more information.

added spec to validate the fix.
commits were not squashed to preserve the commit made by @CompuIves.

Thanks, @CompuIves.

Thanks a lot for writing a test for it! Hopefully we can merge this soon :shipit:.

@claydiffrient can you have a look in this PR?

Looks good merging now

Released in v1.4.0


Make header names case-insensitive

Motivation:
HTTP/2 header field names are compared in case-insensitive fashion.
Modification:

Make HTTP2_HEADER_NAME_HASHER case-insensitive
Lowercase header name when adding new header

Result:

Users do not worry case-sensitivity for header names

This looks like it breaks the HTTP2 spec which requires lowercase header names.
https://http2.github.io/http2-spec/#rfc.section.8.1.2

My understanding about the spec., is,
header names MUST be converted to lowercase for requests and responses, but those are comparable in case-insensitive way.

It says requests / responses with uppercase header names are malformed, and for malformed requests / responses the stream must be clsed.
A request or response containing uppercase header field names MUST be treated as malformed (Section <IP_ADDRESS>).

For malformed requests, a server MAY send an HTTP response prior to closing or resetting the stream. Clients MUST NOT accept a malformed response. Note that these requirements are intended to protect against several types of common attacks against HTTP; they are deliberately strict because being permissive can expose implementations to these vulnerabilities.

So to be honest, I'm not sure what they mean by comparing in a case-insensitive way given the names must be lowercase anyways - I guess it's just redundancy in the spec.

Ah I see now, it's ok for the client code to accept the lowercase strings, it just needs to be converted before encoding - got it :)

I see your point, there are some services, where process both HTTP/1 and HTTP/2 requests internally. If we support case insensitiveness, the result code for such services will be more maintainable.

Can you also add a ServerTest that verifies if the business logic returns headers with an uppercase name, the client sees a lowercase name? I think it will but the test will make sure.

Added.

LGTM


issue/1

https://github.com/dontforgetjared/marvel-characters-app/issues/1

Fixes border color on profile slide over image

Merging


Uncaught TypeError: Cannot set property '0' of undefined

Enter steps to reproduce:

Be using Termination as normal
Have files to commit in Git
Have a prebuilt COMMIT_EDITMSG
Type gc, which opens vi to edit commit message
Throw Exception

This is the current commit message that I believe started these issues, as we had been using this workflow for the previous hours/days.
This exception only gets thrown in Termination, using normal Mac Terminal will not cause issues on loading vi.

Co-Authored-By: Me<EMAIL_ADDRESS>Co-Authored-By: Teammate1<EMAIL_ADDRESS>Co-Authored-By: Teammate2<EMAIL_ADDRESS># Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
#
# On branch 7-email-activiation
# Changes to be committed:
#       modified:   app/views/verification_mailer/verification_email.html.erb
#       modified:   app/views/verification_mailer/verification_email.text.erb
#
# Changes not staged for commit:
#       modified:   app/controllers/users_controller.rb
#       modified:   config/routes.rb
#       modified:   spec/features/user/user_receives_activation_email_on_registration_spec.rb
#
# Untracked files:
#       app/controllers/email_verification_controller.rb

Atom: 1.38.2 x64
Electron: 2.0.18
OS: Mac OS X 10.14.5
Thrown From: termination package 0.7.1
Stack Trace
Uncaught TypeError: Cannot set property '0' of undefined
At /Users/brennan/.atom/packages/termination/node_modules/term.js/src/term.js:1939

TypeError: Cannot set property '0' of undefined
    at Terminal.write (/packages/termination/node_modules/term.js/src/term.js:1939:55)
    at /packages/termination/lib/view.coffee:141:17
    at /Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:38293
    at Function.simpleDispatch (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:1206583)
    at Emitter.emit (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:1208024)
    at ChildProcess.<anonymous> (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:37394)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at emit (internal/child_process.js:772:12)
    at _combinedTickCallback (internal/process/next_tick.js:141:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)

Commands
     -0:47.5.0 termination:toggle (atom-workspace.workspace.scrollbars-visible-when-scrolling.theme-one-dark-syntax.theme-one-dark-ui)

Non-Core Packages
atom-html-preview 0.2.6
busy-signal 2.0.1
erb-snippets 1.1.0
file-icons 2.1.32
intentions 1.1.5
language-slim 1.0.0
linter 2.3.0
linter-ruby 1.3.1
linter-slim 2.0.0
linter-ui-default 1.7.1
markdown-preview-plus 3.8.1
minimap 4.29.9
minimap-autohider 1.6.0
rainbow-csv 0.3.0
remove-whitespace 0.2.1
teletype 0.13.4
termination 0.7.1

This is something that popped up after I tried to reenable the package today. I think it's unrelated to the above issue, but it might not be. For context, I installed Python 3.7.4 just this previous week, after the above issue cropped up.
prebuild-install WARN install No prebuilt binaries found (target=3.1.10 runtime=electron arch=x64 libc= platform=darwin)
gyp ERR! configure error
gyp ERR! stack Error: Python executable "/Applications/Atom.app/Contents/Resources/app/apm/bin/python-interceptor.sh" is v3.7.4, which is not supported by gyp.
gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0.
gyp ERR! stack     at PythonFinder.failPythonVersion (/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/node_modules/node-gyp/lib/configure.js:501:19)
gyp ERR! stack     at PythonFinder.<anonymous> (/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/node_modules/node-gyp/lib/configure.js:483:14)
gyp ERR! stack     at ChildProcess.exithandler (child_process.js:267:7)
gyp ERR! stack     at emitTwo (events.js:126:13)
gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
gyp ERR! stack     at maybeClose (internal/child_process.js:925:16)
gyp ERR! stack     at Socket.stream.socket.on (internal/child_process.js:346:11)
gyp ERR! stack     at emitOne (events.js:116:13)
gyp ERR! stack     at Socket.emit (events.js:211:7)
gyp ERR! stack     at Pipe._handle.close [as _onclose] (net.js:554:12)
gyp ERR! System Darwin 18.6.0
gyp ERR! command "/Applications/Atom.app/Contents/Resources/app/apm/bin/node" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--build_v8_with_gn=false"
gyp ERR! cwd /Users/brennan/.atom/packages/termination/node_modules/node-pty-prebuilt
gyp ERR! node -v v8.9.3
gyp ERR! node-gyp -v v3.7.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: `prebuild-install || node scripts/install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/brennan/.atom/.apm/_logs/2019-07-27T00_04_54_842Z-debug.log

Refer to #96


Eager load  isFriendWith

Hi,
is it possible to eager load the isFriendWith method?
Else I would have an n+1 problem.
Best

Hi, is this request accepted?


Sound in webview pauses background music e.g. Spotify (only on iOS)

Bug description:
Sound in webview pauses background music e.g. Spotify (only on iOS).
On Android it's working correctly (it doesn't pause music).
To Reproduce:
Start music e.g. using Spotify.
Create a webview app which plays a sound.
Run on iOS.
Expected behavior:
Expecting it to work as it does on Android (not interrupting music), or some configuration to manage this.
Environment:

OS: iOS
OS version: 17
react-native version: 0.71.10
react-native-webview version: 11.26.0

any problems?


feat: non-blocking needs interop

Description
Continuation of the work started by

#6758
#7379

We allowed requests to flow through the pipeline in #6758 while pre-bundling, but we needed to block them when:

the optimized dep src code was loaded (this is unavoidable)
in the importAnalysis plugin when importing an optimized dep, we needed to wait until the dependencies are pre-bundled to know if they require interop

Ideally, we only would like to block on 1. Awaiting in 2 blocks requests for any user source code that imports a dep. So in a Vue app, we will be blocking most requests because they all import 'vue'.
Proposal
This PR proposes a way out potentially speeding up cold start even further, with the tradeoff that some legacy packages that advertise themselves as ESM but include mixed CJS may now need to be manually added in the user config. I believe that we could push this "breaking change" in Vite 3.0, and keep pushing for the ecosystem to fix packages as we already do in many other cases in Vite.
Edit: with the latest commits, there is no longer a breaking change. Mixed ESM and CJS would still work, and the only diff would be that cold start would be a bit slower because of an extra page reload if they aren't added to optimizeDeps.needsInterop.
Details
The old needsInterop checks:
a. KNOWN_INTEROP_IDS -> true (only 'moment' is included right now, that was the lib that originated the complex mixed ESM and CJS checks)
b. there aren't exports or imports -> true (assumes it is CJS or UMD)
c. mixed ESM and CJS by checking exports mismatch after esbuild bundled the dep
Because of c., this needs to be computed after pre-bundling
The new needsInterop after this PR checks only a. and b., and a new list in optimizedDeps.needsInterop. So we can compute it before pre-bundling.
We still check c. after pre-bundling, but now to be able to warn the user of the package issue and hint that this can be solved by adding the dep id to optimizedDeps.needsInterop
If we would like to proceed with this change, we would need to check how many dependencies have mixed ESM and CJS. And how problematic it is for users to manually add them to the config. I like the idea of having some friction so some of these packages get PRs to fix them.
As an alternative, we could avoid the optimizedDeps.needsInterop list and instead add a optimizedDeps.acceptMixedSyntax (better name?) that defaults to false. If the user sets it to true, then we revert to the current approach. I think that optimizedDeps.needsInterop is better because users don't need to revert to the slower scheme just because of one faulty package, and because the implementation (the one in this PR) is simpler than what we would need to support acceptMixedSyntax.

What is the purpose of this pull request?

[ ] Bug fix
[x] New Feature
[ ] Documentation update
[ ] Other

Adding this one to the 3.0 milestone, as it would be good to test it a bit during the beta window. I will add docs in the meantime and we would need to discuss the addition of the new optimizeDeps.needsInterop option. This PR could now be merged even without this option (but I think it is a good idea to add it)

After the latest changes in the repo, this PR makes this error happens more often: https://github.com/vitejs/vite/runs/6407272224?check_suite_focus=true#step:11:130, I think it may be a race condition that we are uncovering. I'm very confused by this test though, I tried to fix the package json of the dep it is importing but then the error is consistent:

https://github.com/vitejs/vite/pull/8147

@bluwy this dep is written in ESM + a .vue file, and it doesn't have "type": "module". I think adding it makes sense, but also it is strange that this works at all. @bluwy wouldn't this need your optimizeDeps extensions scheme? Maybe you better understand what the test is trying to do here.

@bluwy would you help me here? I think this test is not right and should be removed. It was added by:

https://github.com/vitejs/vite/pull/4986

The idea was to test an issue with the external detection heuristics, but added a Package with an uncompiled .vue file (that IIUC, it isn't what the Vue ecosystem does). We have been adding noExternal and other flags to try to make it pass but I think we should delete it. In that case, this PR would work. I'm having issues understanding why it works with this PR, maybe this shouldn't have worked before? Would this work if it was a .svelte file without your extensions feat?

Pushed a commit to update ssr-vue tests. It seems like when navigating to /store on the first test, vuex is detected and Vite dynamically optimize that, and somehow it keeps causing fails on the forth test ('/'). Adding a networkidle wait on the first test fixes it. So I don't think we need to remove the external test, and I think it's good that we keep it as it's a usecase in the wild.
I also found out that playgrounds with custom serve.js needs it's tests to call page.goto manually. This was not the case in the ssr-vue tests, which when the first test fails, it causes fails for the following ones. This is now fixed (along for ssr-react).
Hopefully the tests passes now.

Oh, awesome @bluwy! I still think this may not be the best test to have, but even better if we dont need to remove it because of this PR. Would you send these changes in a separate PR so we can merge them without waiting approval for this PR?

Oh are there more stuff to work on for this PR? Thought it was in a ready state except for the tests. If so yeah I can create a separate PR.

We didnt discuss it in a meeting, and there is a new option 👀


google-compute-image: fix Yama LSM option conflict

Having fixed the Google Compute Engine image build process's copying
of store paths in PR #24264, I ran nixos-rebuild --upgrade switch...
and the GCE image broke again, because it sets the NixOS configuration
option for the sysctl variable kernel.yama.ptrace_scope to
mkDefault "1", i.e., with override priority 1000, and now the
sysctl module sets the same option to mkDefault "0" (this was
changed in commit 86721a5f78718caf10c578e9501f8b4d19c0eb44).
This patch raises the override priority of the Google Compute Engine
image configuration's definition of the Yama sysctl option to 500
(still lower than the priority of an unmodified option definition).
I have tested that this patch allows the Google Compute Engine image
to again build successfully for me.

I expect this needs to be picked to release as well.


Prune and reorganize several areas of spell data

Should be fine since focus cantrips have the focus trait, and that leads to us not losing any data. Easy enough to back out on that one property (or handle it a different way).


is there any f7 v.2 layout samples downloads out there?

I have downloaded the v.2 of f7 and still not getting to work it out since i have been using f7 v.1.65 and here the things are different...
question:
is there any f7 v.2 layout samples downloads out there?
thanks

No, there is not

OK I will wait ...


Update search.md

Fix the description of the --command option.

@JohnMcPMS : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Don't update notebooks in git history upon automatic refresh

Change suggested by @artdgn in #332 where not including notebooks in git history, still refreshing images but that should be okay.


ng-add not installing itself

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior
Following dependencies added:
    "typescript": "~4.0.2",
    "svg-to-ts": "^5.0.0"

Expected behavior
@ngneat/svg-icon added to package.json

Minimal reproduction of the problem with instructions

ng new svg-test
ng add @ngneat/svg-icon
Check package.json

What is the motivation / use case for changing the behavior?

Probably happened when tested locally. Ignore it.

Probably happened when tested locally. Ignore it.


Mounting just one container

Is it possible to mount just one container. By default, cloudfuse mounts all available containers under the given account. Is it possible to specify the container name to mount as a command line parameter?

I would also welcome this feature.

Like. Like. I would also welcome this feature.

Waiting for this feature

Hi
I just implemented this in my fork
Feel free to use it!

I would really like this feature as well. I tried vfloz's fork and there is no documentation on how to mount an individual container.

nevermind, i looked through vfloz's source code and found it. line 426 in https://github.com/vfloz/cloudfuse/blob/master/cloudfuse.c
container=

Hi
I updated the README when I pushed the update
You can either specify container="your container" or pass the container="parameter" in the command line!

@vfloz just so you know, i tested your code and it doesn't work. it had really odd behavior. I did a 'ls' once mounted and it listed the same file multiple times.

I had no problem on my side. But I'll have a look at it.
[F v:lmart]
Le 2012-02-17 à 20:55, Jason<EMAIL_ADDRESS>a écrit :

@vfloz just so you know, i tested your code and it doesn't work. it had really odd behavior. I did a 'ls' once mounted and it listed the same file multiple times.

Reply to this email directly or view it on GitHub:
https://github.com/redbo/cloudfuse/issues/11#issuecomment-4031202

Just to give you more information, all of the folder structure was lost when I mounted using your version of cloudfuse. All 6100 of the items in the container where listed in the root folder.

not permanently obviously... just where mounted. I'm using CentOS 5.6.
uname -a
Linux myhostname 2.6.18-274.18.1.el5xen #1 SMP Thu Feb 9 13:27:02 EST 2012 x86_64 x86_64 x86_64 GNU/Linux

Thanks, i'll have a look, you never had a chance to list all the content in the container?
Le 2012-02-17 à 21:28, Jason Barnett a écrit :

not permanently obviously... just where mounted. I'm using CentOS 5.6.
uname -a
Linux myhostname 2.6.18-274.18.1.el5xen #1 SMP Thu Feb 9 13:27:02 EST 2012 x86_64 x86_64 x86_64 GNU/Linux

Reply to this email directly or view it on GitHub:
https://github.com/redbo/cloudfuse/issues/11#issuecomment-4031383

What do you mean?

once mounted, nothing was showing with a #ls ?
Le 2012-02-17 à 21:32, Jason Barnett a écrit :

What do you mean?

Reply to this email directly or view it on GitHub:
https://github.com/redbo/cloudfuse/issues/11#issuecomment-4031411

EVERYTHING showed up when i typed 'ls'
every single file at the root level showed up. there was no directory structure.

What command did you passed?
[F v:lmart]
Le 2012-02-17 à 22:36, Jason<EMAIL_ADDRESS>a écrit :

EVERYTHING showed up when i typed 'ls'
every single file at the root level showed up. there was no directory structure.

Reply to this email directly or view it on GitHub:
https://github.com/redbo/cloudfuse/issues/11#issuecomment-4031723

I passed the ls command
ls

I mean for mounting the container.
[F v:lmart]
Le 2012-02-27 à 10:14, Jason<EMAIL_ADDRESS>a écrit :

I passed the ls command
ls

Reply to this email directly or view it on GitHub:
https://github.com/redbo/cloudfuse/issues/11#issuecomment-4195186

entry in fstab:
cloudfusecontainer      /media/cloudfilescontainer fuse defaults,gid=156,umask=077,allow_other,use_snet=true,username=myusername,api_key=myapikey,container=main_site 0 0

I did not test fstab integration, do you have the same behavior mounting it from command line?
[F v:lmart]
Le 2012-02-27 à 13:56, Jason<EMAIL_ADDRESS>a écrit :

entry in fstab:
cloudfusecontainer      /media/cloudfilescontainer fuse defaults,gid=156,umask=077,allow_other,use_snet=true,username=myusername,api_key=myapikey,container=main_site 0 0

Reply to this email directly or view it on GitHub:
https://github.com/redbo/cloudfuse/issues/11#issuecomment-4200363

Hey, sorry to comment on such an old issue. I was just wondering if Cloud Fuse ever implemented single container mounting with cloud fuse?
I am thinking it might be possible to setup a complex ACL equivalent for read/write access for Cloud Files using something like S/FTP. Which would achieve complex ACL without the need for API or RBAC.
Best wishes,
Adam

Hello, I have the same request to mount only one container.
Regards
Guidtz

7 years later, still waiting for this simple feature....

@MrMoronIV if it’s so simple, why didn’t you get a crack at it? I’m genuinely curious.

Isn't this just using fuse subdir? Or am I misunderstanding? -o module=subdir -o subdir=/container


typo: faciliate -> facilitate

@nschonni : Thanks for your contribution! The author, @gopitk, has been notified to review your proposed change.


[WIP] vectorize llama methods

First attempt to migrate all possible loops to SIMD vectorization.. It shows 10% performance boost , but some parts seems buggy, since its printing wrong tokens

I think it's fixed now..


Jjgriff93/199 seperate out bootstrap

Resolves #ISSUE
What is being addressed
Describe the current behavior you are modifying. Please also remember to update any impacted documentation.
How is this addressed

Describe the changes made, and if appropriate, why they are addressed this way
Note any pending work (with links to the issues that will address them)
Update documentation

Has the CIS document been consulted / updated?

Are you adding new resources, or modifying existing ones?
Have settings been set in line with the CIS recommendations?

:robot: pr-bot :robot:
:runner: Running tests: https://github.com/Griff-Labs/FlowEHR/actions/runs/4669782084 (with refid acac35f2)
(in response to this comment from @jjgriff93)


Add TypeID Python implementation into README

Hello! I have written a Python implementation: https://github.com/akhundMurad/typeid-python
The package is published on PyPI: https://pypi.org/project/typeid-python/

@akhundMurad  Thanks for contributing!
Three quick things:

Due to a quirk of our internal setup, I need to accept the PR in our opensource monorepo and then it'll automatically get published here. Do you mind opening the PR there? The corresponding file is here: https://github.com/jetpack-io/opensource/blob/main/typeid/typeid/README.md
I'm trying to keep the list in alphabetical order, so add the Python link right before Rust.
If you want to mark your implementation as validated by the spec, I've added to files with test data: https://github.com/jetpack-io/typeid/blob/main/spec/valid.yml and https://github.com/jetpack-io/typeid/blob/main/spec/invalid.yml. If you can show your implementation has tests that pass using that data, I'll mark it as validated. This can happen later – we can go ahead and add your implementation to the list now and add the validation check mark once the tests are there.

@loreto Thanks for the quick response!
Here is the pull requests with the right order of https://github.com/jetpack-io/typeid/pull/16 https://github.com/jetpack-io/opensource/pull/56


v2 pass a value, starting with - as argument for a flag

Is there a way (with v2) to provide a value, starting with - as argument for a flag?
Currently I get the following error: error: expected argument for flag '--arg', try --help
Example:
package main

import (
	"fmt"

	"github.com/alecthomas/kingpin"
)

var (
	arg = kingpin.Flag("arg", "arg").String()
)

func main() {
	kingpin.Parse()
	fmt.Println("Arg: ", *arg)
}

Execution result:
$ ./kingpin-test --arg "-n"
kingpin-test: error: expected argument for flag '--arg', try --help

Might be related to #182.

--arg=-n

Thanks, works like a charm.

Apologies for the terse response, I was on my phone at the time. Glad it works.

No worries, I got what I needed and this very quickly, so I was glad I could continue with my work.


Add logging

It is overdue to implement a logging system. I want it to be simple but flexible. I want

Specify logging of arbitrary "modules" with e.g. LOG_REGISTER_MODULE("scheduler")
Set verbosity level for each module LOG_LEVEL("scheduler", LOG_INFO)
Set verbosity level for all modules in one go.
Do logging specific to each module LOG_ERR("scheduler", "Tried to schedule event into the past %ld", event_time);

Zephyr has a particularly nice logging system and I want our logging to match nicely to that: https://docs.zephyrproject.org/latest/services/logging/index.html
For other targets we can chose to either:

Implement the nice logging system with multiple modules or
Just check global verbosity level and dump everything out over printf.

@LasseRosenow is there a nice riot-os logging module the only thing I found is:
https://doc.riot-os.org/core_2lib_2include_2log_8h.html

I am looking at this currently :)

@LasseRosenow is there a nice riot-os logging module the only thing I found is: https://doc.riot-os.org/core_2lib_2include_2log_8h.html

From my knowledge in RIOT it is common to just use printf and then hide Debug prints behind the DEBUG define, which can be overwritten on a per-file basis.
This logging system that you are referencing there is the better alternative to that in my view, but usage of it is somewhat "random".

A first iteration of flexible logging system is now in main


No Module name pyrealsense2 on Jetson Nano

Required Info

Camera Model
{ D435}

Operating System & Version
{Ubuntu 18.04

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
Jetson Nano

SDK Version
{ realsense2 }

Language
{ python }

Segment
{Robot }

I know there are similar questions but none of the solutions I've found in the other threads has worked. So starting a thread to see if I can get assistance.
So I got it to build, but now it says 'no module named pyrealsense2'. If I use rs-enumerate devices the camera is found so it has something to do with the python installation after building. The installed samples also work through command line.
I set the executable to python3 and used sudo make install so I'm a bit confused what I'm doing wrong. I'm trying to run the script with python 3.6.7. Any ideas on how to get the python module in a position I can use it?
Build Output
chaserlewis@chaserlewis-desktop:~/librealsense/build$ sudo make
[  1%] Built target fw
[  7%] Built target tm
[ 15%] Built target realsense-file
Scanning dependencies of target realsense2
[ 16%] Linking CXX shared library librealsense2.so
[ 46%] Built target realsense2
[ 51%] Built target pybackend2
[ 51%] Linking CXX shared library pyrealsense2.cpython-36m-aarch64-linux-gnu.so
[ 52%] Built target pyrealsense2
[ 59%] Built target glfw
[ 59%] Linking CXX executable rs-hello-realsense
[ 59%] Built target rs-hello-realsense
[ 59%] Linking CXX executable rs-software-device
[ 59%] Built target rs-software-device
[ 59%] Linking CXX executable rs-capture
[ 60%] Built target rs-capture
[ 60%] Linking CXX executable rs-callback
[ 61%] Built target rs-callback
[ 62%] Linking CXX executable rs-save-to-disk
[ 62%] Built target rs-save-to-disk
[ 62%] Linking CXX executable rs-multicam
[ 63%] Built target rs-multicam
[ 63%] Linking CXX executable rs-pointcloud
[ 64%] Built target rs-pointcloud
[ 65%] Linking CXX executable rs-align
[ 66%] Built target rs-align
[ 67%] Linking CXX executable rs-align-advanced
[ 68%] Built target rs-align-advanced
[ 69%] Linking CXX executable rs-sensor-control
[ 69%] Built target rs-sensor-control
[ 69%] Linking CXX executable rs-measure
[ 70%] Built target rs-measure
[ 70%] Linking C executable rs-depth
[ 71%] Built target rs-depth
[ 72%] Linking C executable rs-color
[ 72%] Built target rs-color
[ 72%] Linking C executable rs-distance
[ 73%] Built target rs-distance
[ 73%] Linking CXX executable rs-post-processing
[ 75%] Built target rs-post-processing
[ 75%] Linking CXX executable rs-record-playback
[ 77%] Built target rs-record-playback
[ 77%] Linking CXX executable rs-motion
[ 78%] Built target rs-motion
[ 79%] Linking CXX executable rs-pose
[ 79%] Built target rs-pose
[ 79%] Linking CXX executable rs-pose-predict
[ 79%] Built target rs-pose-predict
[ 80%] Linking CXX executable rs-pose-and-image
[ 80%] Built target rs-pose-and-image
[ 81%] Linking CXX executable rs-trajectory
[ 81%] Built target rs-trajectory
[ 81%] Linking CXX executable rs-ar-basic
[ 81%] Built target rs-ar-basic
[ 82%] Linking CXX executable rs-terminal
[ 83%] Built target rs-terminal
[ 84%] Linking CXX executable rs-fw-logger
[ 86%] Built target rs-fw-logger
[ 86%] Linking CXX executable rs-enumerate-devices
[ 87%] Built target rs-enumerate-devices
[ 87%] Linking CXX executable realsense-viewer
[ 92%] Built target realsense-viewer
[ 92%] Linking CXX executable rs-data-collect
[ 92%] Built target rs-data-collect
[ 92%] Linking CXX executable rs-depth-quality
[ 97%] Built target rs-depth-quality
[ 97%] Linking CXX executable rs-rosbag-inspector
[ 99%] Built target rs-rosbag-inspector
[100%] Linking CXX executable rs-convert
[100%] Built target rs-convert

chaserlewis@chaserlewis-desktop:/usr/local/lib$ ls
cmake                    pybackend2.cpython-36m-aarch64-linux-gnu.so
libfw.a                  pybackend2.cpython-36m-aarch64-linux-gnu.so.2
librealsense2.so         pybackend2.cpython-36m-aarch64-linux-gnu.so.2.20.0
librealsense2.so.2.20    pybackend2.cpython-36m-aarch64-linux-gnu.so.2.21.0
librealsense2.so.2.20.0  pyrealsense2.cpython-36m-aarch64-linux-gnu.so
librealsense2.so.2.21    pyrealsense2.cpython-36m-aarch64-linux-gnu.so.2.21
librealsense2.so.2.21.0  pyrealsense2.cpython-36m-aarch64-linux-gnu.so.2.21.0
librealsense-file.a      python2.7
libtm.a                  python3.6
pkgconfig

PythonPath
chaserlewis@chaserlewis-desktop:/usr/local/lib$ echo $PYTHONPATH
:/usr/local/lib

How I called CMAKE
chaserlewis@chaserlewis-desktop:~/librealsense/build$ sudo cmake ../ -DBUILD_PYTHON_BINDINGS=TRUE -DPYTHON_EXECUTABLE=/usr/bin/python3
Python Script
import cv2
import numpy as np
import pyrealsense2 as rs
try:

    pipeline = rs.pipeline()
    pipeline.start()

    while True:
        frames = pipeline.wait_for_frames()
        depth = frames.get_depth_frame()

        if not depth:
            continue

        img = np.asanyarray(depth.as_frame().get_data())
        cv2.imshow('depth',img)
        cv2.waitKey(1)
except:
    print("Error!")

Could you try copying the .so files to Python's dist-packages folder? (Can
be found with import site; site.getsitepackages() from within the
interpreter)

@ChaseLewis Did you get through the issue? Looking forward to your update. Thanks!

No I have been using the C++ bindings because the python bindings do not work. I had already tried Iramti's suggestion. Those files are in the same place all my other python files. It does not work. It could be the script doesn't rename them or something as they have very odd names with cython in them. I am unsure. The instructions as provided do not work, so was hoping for feedback that could assist.

I'm having the exact same issue! Did you figure it out?
my issue is here: #4089

@ChaseLewis @kat-mcg-lin  I followed the steps in https://github.com/IntelRealSense/librealsense/tree/master/wrappers/python and couldn't reproduce the issue you reported on JetsonNano in my hand.  Could you please double check you followed the steps and if you're under python3 when execute?

@ChaseLewis @kat-mcg-lin  Any update for this issue? Did you get through now? Looking forward to your update. Thanks!

@RealSenseCustomerSupport I have gotten it to work!

@kat-mcg-lin  That's great! Thanks for the update!
@ChaseLewis  Any good news from your side? Thanks!

@ChaseLewis If no other questions, will close the ticket accordingly. Thanks!

@RealSenseCustomerSupport I have gotten it to work!

how did it worked? i am having same problem

@kat-mcg-lin I also would be interested in knowing how you fixed that. I followed the instruction here: https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md. The realsense-viewer is working, but I also receive the error ModuleNotFoundError: No module named 'pyrealsense2'

@RealSenseCustomerSupport Has anyone solved this ? I can't run some scripts because I get "ModuleNotFoundError: No module named 'pyrealsense2'" . I would like to get this to work so if anybody knows how please share the fix.

Also having this problem, Jetson Nano Ubuntu 18.04LTS installed following: https://dev.intelrealsense.com/docs/nvidia-jetson-tx2-installation
the realsense-viewer workes as does compiling for c++


Heap pairIsInCorrectOrder() missing

Awesome repo, thank you! QQ: Am I missing something or pairIsInCorrectOrder isn't fully implemented? It always returns an error. Can you clarify?
https://github.com/trekhleb/javascript-algorithms/blob/master/src/data-structures/heap/Heap.js#L280

Never mind, just noticed that this function gets overwritten and re-defined when the class is consumed. =/
Thanks!


Added entered Event

workflow.entered
Similar to workflow.enter, except the marking store is updated before this event (making it a good place to flush data in Doctrine).
The three events being dispatched are:
workflow.entered
workflow.[workflow name].entered
workflow.[workflow name].entered.[place name]

https://symfony.com/doc/current/workflow/usage.html#using-events

Hi @bigperson, thanks for this one. can you add a test to it?


Column Visibility

Summary of problem or feature request
Unable to hide columns when using Datatables as a service. When the page first loads, the columns marked visible => false, are indeed hidden, but once the ajax loads, they are once again visible.
Any suggestions? Thanks so much!
Code snippet of problem
Controller
use App\DataTables\ModelDataTable;

class ModelController extends Controller
{
    public function index(ModelDataTable $dataTable)
    {
        return $dataTable->render('model.index');
    }
}

View
{!! $dataTable->table() !!}
{!! $dataTable->scripts() !!}

ModelDataTable
class ModelDataTable extends DataTable
{
    public function ajax()
    {
        $result =  $this->datatables
            ->eloquent($this->query())
            ->make(true);
        return $result;
    }

    public function query()
    {
        //Relationships
		$model = Guarantee::all();
        return $this->applyScopes($guarantees);
    }

    public function html()
    {
        return $this->builder()
            ->columns($this->getColumns())
            ->parameters([
                'dom' => 'lBfrtip',
                'stateSave' => false,//true,
                'bScrollInfinite' => true,
                'responsive' => true,
                'lengthMenu' => [10, 15, 30, 50, 100],
                'buttons' => ['copy', 'csv', 'excel', 'print', 'reset'],
                'processing' => true,
                'serverSide' => true,

            ]);
    }

    protected function getColumns()
    {
        return  [
            [
                "orderable" => false,
                "searchable" => false,
                "title" => "ID",
                "data" => "id",
            ],
            [
                'name' => 'type_id',
                "searchable" => false,
                "title" => "Type",
                "data" => "type",
            ],
            [
                'name' => 'tag',
                "searchable" => false,
                "title" => "Tag",
                "data" => "tag",
		"visible" => false,
            ],
        ];
    }
}

System details

PHP Version - 7.1.1
Laravel Version - 5.4
Laravel-Datatables Version - 7

There is no visible in the whole datatables source code. I have the same issue because I want fulltext search on an invisible column behind the scenes. Please implement this feature.

Currently, I am doing it via CSS
style.css

th.dpass, td.dpass {
  display: none;
}

ModelDataTable.php
public function html()
    {
        return $this->builder()
            ->columns($this->getColumns())
            ->parameters([
                'dom' => 'lBfrtip',
                'stateSave' => false,
                'bScrollInfinite' => true,
                'responsive' => true,
                'lengthMenu' => [10, 15, 30, 50, 100],
                'buttons' => ['copy', 'csv', 'excel', 'print', 'reset'],
                "language" => [
                    "lengthMenu"    => "Show _MENU_ model",
                    "info"          => "Showing _START_ to _END_ of _TOTAL_ model",
                    "infoEmpty"     => "Showing 0 models",
                    "infoFiltered"  => "(filtered from _MAX_ models)",
                    "processing"    => "<i class=\"fa fa-cog fa-spin fa-2x\"></i> Searching Models"
                ],
                //HIDE COLUMNS
                "aoColumnDefs" => [
                    [ "sClass" => "dpass", "aTargets" => [ 4,5,6 ]],
                ],
                //END OF HIDE COLUMNS
                'processing' => true,
                'serverSide' => true,

            ]);
    }

Your suggestion worked fine @Skintillion. But a concrete behaviour for a column attribute visible would be perfect. Because the column visibility plugin does not work with that setting.

If you disable "responsive", it works.

But I need the responsive option :(
Thank you for your advice. It was a hassle examining the problems :)

responsive setting to false does not handle the column visibility visible = false. This does not work as you mentioned before.


Add a Gitter chat badge to README.md

schnaader/precomp-cpp now has a Chat Room on Gitter
@schnaader has just created a chat room. You can visit it here: https://gitter.im/schnaader/precomp-cpp.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Opened chat room on Gitter


Yez

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡

Examples 🌈

Motivation 🔦

I try


Simple 'make' then 'make install' fails

This is with Manjaro Linux, up to date.  If I run 'make' everything proceeds apace with a few warnings and then succeeds.  'make install' then fails.  (In the paste below, I ran the 'make' previously;  just demonstrating that it thinks it's succeeded at that.)
❯ make
make: Nothing to be done for 'all'.
❯ make install
INSTALL
install: cannot stat '.obj/unix/src+fluxengine/src+fluxengine': No such file or directory
make: *** [Makefile:102: install-bin] Error 1
❯ ls .obj/unix
+all  arch  dep  extras  lib  +protocol_hdr  __pycache__  scripts  src  tests  tools  build.mk  README.00  README.01

It  seems not to be making various directories in .obj/unix that the 'install' lines in the Makefile think should be there.  The binaries all seem to have been dropped in the top-level fluxengine directory, so I'm not sure what the 'install' lines in the Makefile are looking for.
I'm aware of #750 but this is not inside a chroot, and the directory it's trying to stat does contain the 'unix' chunk that's missing in that bug report.

Hello --- the install rule is broken, but the rest of it should work. I have added a Docker test for Manjaro, so I know it builds:
https://github.com/davidgiven/fluxengine/blob/master/tests/docker/Dockerfile.manjaro
So I'm guessing it's something about your local environment. I have been doing a lot of work on the build system, so it could be confused by old build artifacts. Try deleting the .obj directory?

Ah yeah, I was just reporting on the broken 'make install' rule -- it does drop the binaries at the top level of the project, and they seem to work, at least at first glance.  Do they need to have been installed as per the 'make install' clause in order to work fully, or does it work just fine to run them directly from the project directory?  But yeah, everything else seems fine apart from the broken install rule, so since that's a known thing, please feel free to close this if it suits you.  Thanks for the quick reply!

No, the binaries are all standalone. I can't even remember what that rule was for, now.

Broken rule removed. Thanks for the bug report!


fix: change verbose_name in changes_text migration

closes #570
my bad.
I don't know how this happened. The good thing is that verbose_name doesn't alter the db, so we don't need to create a migration for people already on v3.

I think the issue was because I created the migrations semi-manually (I was new to the project and didn't know how to set up a good local env)

V3 is in beta. So, people should not use it on prod. don't worry

We probably need to prepare the second beta for V3

Was this meant to be included in 3.0b2? The 3.0b2 tag on Github is for an earlier commit from September, but there's a commit on master after this was merged that mentions preparing for 3.0b2, so is the tag wrong?

@jgillard seems you are right.
Not sure what was the problem. But I will prepare a new beta release soon