Cannot read property 'div' of undefined

System:

OS: macOS High Sierra 10.13.6
CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
Memory: 428.57 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash

Binaries:

Node: 8.11.4 - /usr/local/bin/node
Yarn: 1.12.3 - /usr/local/bin/yarn
npm: 6.5.0 - ~/.npm-global/bin/npm

npmPackages:

styled-components: ^4.1.3 => 4.1.3

Reproduction
This issue occurred once I have updated project dependencies:
-    "babel-eslint": "^8.2.6",
-    "babel-loader": "^7.1.5",
+    "babel-eslint": "^10.0.1",
+    "babel-loader": "^8.0.4",
-    "flow-bin": "^0.86.0",
+    "flow-bin": "^0.89.0",
-    "lint-staged": "^7.3.0",
+    "lint-staged": "^8.1.0",
-    "styled-components": "^4.1.1",
+    "styled-components": "^4.1.3",

Steps to reproduce
git clone https://github.com/kettanaito/atomic-layout
cd atomic-layout
git checkout dependencies
npm install
npm run storybook

You can see all the config files (babel, webpack, etc.) on the mentioned branch.

See the following exception thrown by Storybook.
Cannot read property 'div' of undefined
    TypeError: Cannot read property 'div' of undefined
    at Module.srcComponentsBoxJsx (http://localhost:6020/main.4a3566b995dd1c2ae279.bundle.js:2172:76)
    at __webpack_require__ (http://localhost:6020/main.4a3566b995dd1c2ae279.bundle.js:199:27)
    at Module.srcIndexJs (http://localhost:6020/main.4a3566b995dd1c2ae279.bundle.js:2815:60)
    at __webpack_require__ (http://localhost:6020/main.4a3566b995dd1c2ae279.bundle.js:199:27)
    at http://localhost:6020/main.4a3566b995dd1c2ae279.bundle.js:393:14
    at http://localhost:6020/main.4a3566b995dd1c2ae279.bundle.js:395:6
    at webpackUniversalModuleDefinition (http://localhost:6020/main.4a3566b995dd1c2ae279.bundle.js:143:898)
    at Module.<anonymous> (http://localhost:6020/main.4a3566b995dd1c2ae279.bundle.js:144:3)
    at Module../index.js (http://localhost:6020/main.4a3566b995dd1c2ae279.bundle.js:5381:30)
    at __webpack_require__ (http://localhost:6020/runtime~main.4a3566b995dd1c2ae279.bundle.js:782:30)

The following outputs undefined in the console:
import styled from 'styled-components'

console.log(styled)

I do acknowledge that this is most likely not an issue with the styled-components package. However, I would be very thankful for help, as I couldn't find any relevant issues anywhere else.
Expected Behavior

styled can be imported as a default export of styled-components package

Actual Behavior

import styled from 'styled-components' resolves styled to undefined

If I had to guess, it's some sort of module re-exporting bug from having multiple versions of s-c in the tree. Have you tried the yarn "resolutions" field to dedupe? https://yarnpkg.com/lang/en/docs/selective-version-resolutions/

Update
I have found the problematic package. Consider the next code:
import styled from 'styled-component'

Using<EMAIL_ADDRESS>results into styled being undefined.
Using<EMAIL_ADDRESS>imports styled namespace properly.
The very same configs and settings are used, only the babel-loader version changes.

I am facing the same issue as @kettanaito.
If I do const Element = styled.View  I get this error:

It seems I need to change all my  declarations to
import { View } from 'react-native
const Element = styled(View)

to make it work but I really don't want to do that, or downgrade my babel-loader.
Any ideas on how to fix this?

@altany curious if you ended up finding a solution to this issue. Started experiencing this today, and have found that it renders local development pretty much impossible.

@altany curious if you ended up finding a solution to this issue. Started experiencing it today, and have found that it renders local development pretty much impossible.

I have given up on it for now unfortunately.

I was having  the same error... i get rid of the selected code (in webpack.config.js):

and it worked for me =)

Oh by the way... i'm using this .babelrc:

Did anyone figure out a fix for this? I'm getting the same error when trying to use styled.div. The above solution did not work for me.

Hi, I'm getting this error when trying to override a style too
// ErrorAlert.js

import { Modal, Icon, Typography, Button } from 'frozen/components'

// trying to override the PrimaryButton style
const ActionButton = styled(Button.PrimaryButton)`
  width: 100%;
`

Is there anything that I should remove? I don't have any mention of styled components in my webpack.
Here's my .babelrc
{
  "presets": [
    [
      "@babel/preset-env",
      {
        "targets": {
          "node": "current"
        },
        "useBuiltIns": "usage",
        "corejs": {
          "version": 3,
          "proposals": true
        }
      }
    ],
    "@babel/preset-react"
  ],
  "plugins": [
    "babel-plugin-styled-components",
    "@babel/plugin-syntax-dynamic-import",
    "@babel/plugin-proposal-object-rest-spread",
    "@babel/plugin-proposal-export-default-from",
    "@babel/plugin-proposal-export-namespace-from",
    [
      "@babel/plugin-proposal-class-properties",
      {
        "spec": true
      }
    ],
    "react-hot-loader/babel"
  ]
}

@vinamelody as you're saying you're using Webpack to bundle and I'm seeing a reference to Node in your configuration. I don't know if you're accidentally transpiling all modules with Babel and are converting them to CommonJS but try setting modules: false in your @babel/preset-env config

Hi @kitten tried that but for some reason it's still getting error.
Created this codesanbox but it works there https://codesandbox.io/s/sharp-shaw-nsfmf?file=/src/components/ErrorAlert.js
For now, i'd do a little hack by declaring the button that I want in my Button.js file and use it in the other component.
// Button.js
import styled from 'styled-components'
import { Base } from './components'

const PrimaryButton = styled.button`
  min-width: 10em;
  height: 2.75em;
  color: ${props => props.theme.colors.salt};
  background: ${props => props.theme.colors.mint};
  border-radius: 0.3125em;
  border: 1px solid transparent;
  padding: 0.625em 1em;

  &:hover {
    color: ${props => props.theme.colors.salt};
    background: ${props => props.theme.colors.darkmint};
  }
  &[disabled] {
    color: ${props => props.theme.colors.grey400};
    background: ${props => props.theme.colors.grey200};
  }

  ${Base.MediaQuery[0]} {
    min-width: 7em;
  }
`
const SecondaryButton = styled.button`
  min-width: 10em;
  height: 2.75em;
  color: ${props => props.theme.colors.mint};
  background: ${props => props.theme.colors.salt};
  border: 1px solid;
  border-color: ${props => props.theme.colors.mint};
  border-radius: 0.3125em;

  ${Base.MediaQuery[0]} {
    min-width: 7em;
  }
`

const FullWidthButton = styled(PrimaryButton)` ---> this styled() works if I put it here
  width: 100%;
`

export default {
  PrimaryButton,
  SecondaryButton,
  FullWidthButton
}

then in my component:
import React from 'react'
import styled from 'styled-components'
import iconFail from './assets/icon-fail.svg'
import { Modal, Icon, Typography, Button } from './components'

const ModalButtonWrapper = styled.div`
  width: 100%;
`

const IconImage = styled.img`
  max-height: 16em;
`
const CustomButton = styled(Button.PrimaryButton)` ----> this will throw Uncaught TypeError: Cannot read property 'PrimaryButton' of undefined
  width: 100%;
`

function ErrorAlert (props) {
  const { show, title, buttonText, handleClose } = props
  return (
    <Modal show={show}>
      <IconImage src={iconFail} />
      <Typography.PageTitle>{title}</Typography.PageTitle>
      <ModalButtonWrapper>
        <Button.FullWidthButton onClick={handleClose}>
          {buttonText}
        </Button.FullWidthButton>
      </ModalButtonWrapper>
    </Modal>
  )
}

export default ErrorAlert

@vinamelody You have a circular import in that file where Base is imported in Button's file but both of them are imported and exported in that components/index file. If you reference Base'a file directly in Buttondo file it'll work.
I'll also have to ask you to please ask usage questions (particularly since this is Webpack related) on other platforms like StackOverflow or Spectrum :)


no background scrolling when menu is opened in mobile devices

Description of PR
In mobile devices, when menu is expanded, the background main content should not be scrollable.
Type of PR

[x] Bugfix
[ ] New feature

Relevant Issues
Fixes #1311
Checklist

[x] Compiles and passes lint tests
[x] Properly formatted
[x] Tested on desktop
[x] Tested on phone

Screenshots

Hey, @nayakrahul i have already worked on it at this PR #1184

Oh. Closing it.

@Binu42 Your PR #1184 makes the main content unscrollable in desktop view also.

@nayakrahul i think it should work like that only because contents are getting overlapped with sidenav and it's distracting to allow users to scroll.

Patched by #1364


Implement CocoaPods podspec

CocoaPods podspec implementation would allow to put together iOS & macOS SDK.

Initial implementation done with e61e809.


env._.run

similar to #1447, it should be possible to execute arbitrary scripts which "export" env vars like this:
[env]
_.run = "./myscript"

Where unlike in #1447, this would be run like any other binary. Somehow it needs to pull env vars out of it, I know that direnv has a trick where they launch direnv inside of this script and that is able to pull the env vars out. We'll need something like that to make this possible.

Would also solve my use case for direnv, loading environment modules, eg:
module load CUDA/12.1

Would be lovely for scripts execution, but for single commands as well, to have atomic commands too :pray:

You're welcome to take it on

@jdx If you are open to it, we'd be willing to sponsor some improvements around this issue as well as these other two:

https://github.com/jdx/mise/issues/1982
https://github.com/jdx/mise/issues/1777

Of course, this assumes you are onboard with the proposed changes.
In short, we are trying to replace direnv with Mise and there are some differences in how they work, which are currently blocking a switch. Happy to elaborate on the details if you want to know more about what's keeping us from switching.
I'd guess you are probably busy, but just wanted to ask 😄

@jdx Awesome 😄
If you enable donations we'll still send something over (we're not a huge company though, just a dozen of engineers).
In either case, this is great and I think (a colleague is double-checking) that this will unblock us from moving off direnv to Mise! 🎉

I really appreciate that! let me know how it works, it was quite a bit of code and it's a bit tricky to test but I had it working well enough on my machine

@jdx Great!
I'm not directly involved but my colleague will likely write back here or in the other issue that was also closed yesterday (those were related) in case there are questions.
You should see some fresh sponsorship. I know it's not much, but at least it's something (we're not a big company).


Promote latest SPI changes to production

https://github.com/redhat-appstudio/service-provider-integration-operator/pull/563
https://github.com/redhat-appstudio/service-provider-integration-operator/pull/582
https://github.com/redhat-appstudio/service-provider-integration-operator/pull/583
https://github.com/redhat-appstudio/service-provider-integration-operator/pull/581
https://github.com/redhat-appstudio/service-provider-integration-operator/pull/575
https://github.com/redhat-appstudio/service-provider-integration-operator/pull/587
https://github.com/redhat-appstudio/service-provider-integration-operator/pull/577
https://github.com/redhat-appstudio/service-provider-integration-operator/pull/586
https://github.com/redhat-appstudio/service-provider-integration-operator/pull/578
https://github.com/redhat-appstudio/service-provider-integration-operator/pull/585
https://github.com/redhat-appstudio/service-provider-integration-operator/pull/579
https://github.com/redhat-appstudio/service-provider-integration-operator/pull/588

/lgtm


Unredeable header css

.mat-datetimepicker-calendar-header has #fff color, identical to it's default background.
With default theme it's impossible to chosen datetime because it's white on white background.
It would be nice to make it customizable or to delete this css and let it inherit.

Example to issue.

I'm seeing this same issue. Any progress on this?

Hi guys. The project is currently "kind of maintained". I'm happy to accept PR's all the time. However I cannot find to implement features or fix bugs. In fact, I still didn't even found the time to fix the build (it's angular/v8) or to upgrade the angular version (angular/v9 beta).

@bbortt I can help contributing and maitaining if you need an extra pair of hands :)

That'd be great! I mean I can accept PRs and push releases at any time, that's a matter of minutes. But my company does no longer use this project, so there's no time investment possible from this side. And I'm (sadly) pretty busy otherwise.

Without taking a deep dive into this, I found this line of code:
https://github.com/kuhnroyal/mat-datetimepicker/blob/release/projects/core/src/datetimepicker/calendar.scss#L26
I think that should go away. When I remove this exact color property in the dev console in the browser the colors go back to normal. The elements even have different colors. So I think this just incorrectly overwrites them.
I would test this out but I have no experience in testing/developing JS libraries. Maybe someone else can test this?

@moritzluedtke I will take a look at it by the end of the week.. thanks for the hint.


Plastic Free July - 14th July Post

This Plastic Free July, we challenge you to reduce your plastic use. Single-use plastics are a major environmental concern, contributing to pollution and harming wildlife. By opting for reusable alternatives, we can make a significant impact.
Share your tips for living a plastic-free life and inspire others to join the movement. Together, we can create a cleaner, healthier planet.
#ClentAfrica #PlasticFreeJuly #ReduceWaste #EcoFriendly #SustainableLiving

I like this illustration
On Sat, Jul 13, 2024 at 11:24 AM Yigakpoa Samuel @.***>
wrote:

Green.Illustration.Say.No.To.Plastic.Campaign.Instagram.Post.png (view on
web)
https://github.com/user-attachments/assets/8c77c2f0-f5b2-4094-9b42-9648dca9b564
—
Reply to this email directly, view it on GitHub
https://github.com/clentafrica/marketing-and-comms/issues/7#issuecomment-2226956176,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJQTEFO2AEMDLVCD6ZRFPKTZMFBBJAVCNFSM6AAAAABKWSZ6PCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRWHE2TMMJXGY
.
You are receiving this because you were assigned.Message ID:
@.***>

Nice design

@Okpeelizabeth1989 please post this on FB & Instagram while @SDauphin15 posts on LinkedIn. I will post on twitter for now.
——
This Plastic Free July, we challenge you to reduce your plastic use. Single-use plastics are a major environmental concern, contributing to pollution and harming wildlife. By opting for reusable alternatives, we can make a significant impact.
Share your tips for living a plastic-free life and inspire others to join the movement. Together, we can create a cleaner, healthier planet.
#ClentAfrica #PlasticFreeJuly #ReduceWaste #EcoFriendly #SustainableLiving

Done for twitter 💃

Noted. I will post now
On Mon, Jul 15, 2024 at 11:54 AM Yigakpoa Samuel @.***>
wrote:

@Okpeelizabeth1989 https://github.com/Okpeelizabeth1989 please post
this on FB & Instagram while @SDauphin15 https://github.com/SDauphin15
posts on LinkedIn. I will post on twitter for now.
——
This Plastic Free July, we challenge you to reduce your plastic use.
Single-use plastics are a major environmental concern, contributing to
pollution and harming wildlife. By opting for reusable alternatives, we can
make a significant impact.
Share your tips for living a plastic-free life and inspire others to join
the movement. Together, we can create a cleaner, healthier planet.
#ClentAfrica #PlasticFreeJuly #ReduceWaste #EcoFriendly #SustainableLiving
Green.Illustration.Say.No.To.Plastic.Campaign.Instagram.Post.png (view on
web)
https://github.com/user-attachments/assets/3dd68dd9-baa0-4cd3-b1b5-62ef08c1811f
—
Reply to this email directly, view it on GitHub
https://github.com/clentafrica/marketing-and-comms/issues/7#issuecomment-2228841671,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJQTEFPZDPSNOJHYUSELO43ZMPWEFAVCNFSM6AAAAABKWSZ6PCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRYHA2DCNRXGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Posted this since on the 14th on Facebook and Instagram


Release: 2018.04.03

There are several bugs in the latest release. I think we should make a new minor release fixing these issues. The goal are the following:
Bug fixes:

[x] Rework run-stats:

[x] Sharing intel_mp RX/TX counters does not seem to work properly on latest release #1137
[x] Snabb top interface view does not report RX/TX of non-master queue #1134
[x] The semantics of run_stats is changed in the latest lwAFTR release #1139

[x] path_data.setter_for_grammar mangles path query containing #1116
[x] Minor snabb top UI improvements #1153
[x] Binding-table generation always skip psid 0 #1155

Features:
None
There's a new Snabb release since our last lwAFTR release. I think we should not merge lastest Snabb release and focus only on fixing the bugs on the latest release.

Superseded by https://github.com/Igalia/snabb/issues/1174


[main] Fix "Expand recursively" and "Collapse recursively" menu actions

The comparisons of action->text() with kActionExpandRecursively and
kActionCollapseRecursively were wrong because the text that is not used
sometimes contains "ALT+Click" after https://github.com/google/orbit/pull/3513.
Bug: http://b/232211219
Test: Try the actions in the top-down and bottom-up views (I only tried on
Linux, it should be enough).

Reviewed in https://github.com/google/orbit/pull/3697


Getting error CRYPTO_STATIC_MUTEX_lock_write when using aws-sdk-cpp-v2 with http lib cpr (using curl + openssl)

Hi All,

I dont know if its the right place to post the que here but its due to a lib conflict thats why m posting it here / or can help someone in future and to find some help from community.

I want to integrate one cpr with my aws-sdk based pub-sub mqtt example
How I did it (example code)

I used our basic-pub-sub mqtt example (https://github.com/aws/aws-iot-device-sdk-cpp-v2/tree/main/samples/mqtt/basic_pub_sub) to start.
added this small code to test it.

#include <cpr/cpr.h>
****
****
int test_http {
   cpr::Response r = cpr::Get(cpr::Url{"https://api.github.com/repos/whoshuu/cpr/contributors"},
                     cpr::Authentication{"user", "pass"},
                     cpr::Parameters{{"anon", "true"}, {"key", "value"}});
   r.status_code;                  // 200
   r.header["content-type"];       // application/json; charset=utf-8
   r.text;                         // JSON text string
}

compiled it and linked the lib as described on their website README and it all went smoothly.

Problem

when i run the code without any AWS-SDK code just only CPR lib demo then the code runs fine and work as expected.
When I run this our above described code (with aws pub-sub example), then it throws a CRYPTO_STATIC_MUTEX_lock_write and then it crashes.
screenshot of gdb trace:

Hints(why this can happen)
I am not an expert in libcrypto but still m putting my assumptions here

can be due to multi threaded/mutex problems with curl (because curl does not support it and some threads can be already in use by AWS-SDK)
conflicts between aws-lc (libcrypto) and libcrypto from cpr lib

If anyone has hints about solving this problem then please let me know.
Thank you in advance and wish you all a great working day.

I think this one has been solved https://github.com/aws/aws-iot-device-sdk-cpp-v2/issues/301#issuecomment-884493921?
As you suggested I also think this is a clash between different versions of OpenSSL / libcrypto.
Therefore I don't think this is a cpr related issue.


gnutls/gnutls.h: No such file or directory while installing latest cups 2.3.3

I am trying to install the latest version of cups 2.3.3, I was following https://fossies.org/linux/cups/INSTALL.md
After the make command, I got the foll error.
In file included from cups-private.h:21:0,
                 from auth.c:17:
http-private.h:70:14: fatal error: gnutls/gnutls.h: No such file or directory
 #    include <gnutls/gnutls.h>
              ^~~~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [../Makedefs:271: auth.o] Error 1

Note that I followed the step
sudo apt-get install autoconf build-essential libavahi-client-dev \
     libgnutls28-dev libkrb5-dev libnss-mdns libpam-dev \
     libsystemd-dev libusb-1.0-0-dev zlib1g-dev

before going to make.

Hi,
thank you for reporting the issue!
However, CUPS is a separate project - see OpenPrinting/cups.
Regarding the error - either libgnutls28-dev doesn't provide gnutls/gnutls or you have your includes set up incorrectly.
Would you mind reporting the issue to CUPS project and attaching there as files (you can add .txt suffix to a file and github can upload it) your compilation log and config.log after running configure?


Compilation with mingw does not work

Steps to reproduce

Obtained vim from github
cd vim\src
Run "mingw32-make -f Make_ming.mak ARCH=x86_64 gvim.exe"
At the end following error is displayed:
g++ -I. -Iproto -DWIN32 -DWINVER=0x0601 -D_WIN32_WINNT=0x0601 -DHAVE_PATHDEF -DFEAT_HUGE -DHAVE_STDINT_H -DHAVE_GETTEXT -DHAVE_LOCALE_H -DDYNAMIC_GETTEXT -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DFEAT_JOB_CHANNEL -DFEAT_IPV6 -DFEAT_TERMINAL -DFEAT_SOUND -DFEAT_DIRECTX -DDYNAMIC_DIRECTX -DFEAT_DIRECTX_COLOR_EMOJI -DFEAT_GUI_MSWIN -DFEAT_CLIPBOARD -DFEAT_MBYTE_IME -DDYNAMIC_IME -DDYNAMIC_ICONV -pipe -march=x86-64 -Wall -DFEAT_XPM_W32 -I xpm/x64/include -I xpm/x64/../include -O3 -fomit-frame-pointer -freg-struct-return -ffunction-sections -fno-asynchronous-unwind-tables -s -municode -mwindows -Wl,--gc-sections -o gvim.exe gobjx86-64/alloc.o gobjx86-64/arabic.o gobjx86-64/arglist.o gobjx86-64/autocmd.o gobjx86-64/beval.o gobjx86-64/blob.o gobjx86-64/blowfish.o gobjx86-64/buffer.o gobjx86-64/bufwrite.o gobjx86-64/change.o gobjx86-64/charset.o gobjx86-64/cindent.o gobjx86-64/clientserver.o gobjx86-64/clipboard.o gobjx86-64/cmdexpand.o gobjx86-64/cmdhist.o gobjx86-64/crypt.o gobjx86-64/crypt_zip.o gobjx86-64/debugger.o gobjx86-64/dict.o gobjx86-64/diff.o gobjx86-64/digraph.o gobjx86-64/drawline.o gobjx86-64/drawscreen.o gobjx86-64/edit.o gobjx86-64/eval.o gobjx86-64/evalbuffer.o gobjx86-64/evalfunc.o gobjx86-64/evalvars.o gobjx86-64/evalwindow.o gobjx86-64/ex_cmds.o gobjx86-64/ex_cmds2.o gobjx86-64/ex_docmd.o gobjx86-64/ex_eval.o gobjx86-64/ex_getln.o gobjx86-64/fileio.o gobjx86-64/filepath.o gobjx86-64/findfile.o gobjx86-64/float.o gobjx86-64/fold.o gobjx86-64/getchar.o gobjx86-64/gc.o gobjx86-64/gui_xim.o gobjx86-64/hardcopy.o gobjx86-64/hashtab.o gobjx86-64/help.o gobjx86-64/highlight.o gobjx86-64/if_cscope.o gobjx86-64/indent.o gobjx86-64/insexpand.o gobjx86-64/json.o gobjx86-64/list.o gobjx86-64/locale.o gobjx86-64/logfile.o gobjx86-64/main.o gobjx86-64/map.o gobjx86-64/mark.o gobjx86-64/match.o gobjx86-64/memfile.o gobjx86-64/memline.o gobjx86-64/menu.o gobjx86-64/message.o gobjx86-64/misc1.o gobjx86-64/misc2.o gobjx86-64/mouse.o gobjx86-64/move.o gobjx86-64/mbyte.o gobjx86-64/normal.o gobjx86-64/ops.o gobjx86-64/option.o gobjx86-64/optionstr.o gobjx86-64/os_mswin.o gobjx86-64/os_win32.o gobjx86-64/pathdef.o gobjx86-64/popupmenu.o gobjx86-64/popupwin.o gobjx86-64/profiler.o gobjx86-64/quickfix.o gobjx86-64/regexp.o gobjx86-64/register.o gobjx86-64/scriptfile.o gobjx86-64/screen.o gobjx86-64/search.o gobjx86-64/session.o gobjx86-64/sha256.o gobjx86-64/sign.o gobjx86-64/spell.o gobjx86-64/spellfile.o gobjx86-64/spellsuggest.o gobjx86-64/strings.o gobjx86-64/syntax.o gobjx86-64/tag.o gobjx86-64/term.o gobjx86-64/testing.o gobjx86-64/textformat.o gobjx86-64/textobject.o gobjx86-64/textprop.o gobjx86-64/time.o gobjx86-64/typval.o gobjx86-64/ui.o gobjx86-64/undo.o gobjx86-64/usercmd.o gobjx86-64/userfunc.o gobjx86-64/version.o gobjx86-64/vim9class.o gobjx86-64/vim9cmds.o gobjx86-64/vim9compile.o gobjx86-64/vim9execute.o gobjx86-64/vim9expr.o gobjx86-64/vim9instr.o gobjx86-64/vim9script.o gobjx86-64/vim9type.o gobjx86-64/viminfo.o gobjx86-64/winclip.o gobjx86-64/window.o gobjx86-64/os_w32exe.o gobjx86-64/vimres.o gobjx86-64/netbeans.o gobjx86-64/job.o gobjx86-64/channel.o gobjx86-64/gui_dwrite.o gobjx86-64/xpm_w32.o gobjx86-64/terminal.o gobjx86-64/vterm_encoding.o gobjx86-64/vterm_keyboard.o gobjx86-64/vterm_mouse.o gobjx86-64/vterm_parser.o gobjx86-64/vterm_pen.o gobjx86-64/vterm_screen.o gobjx86-64/vterm_state.o gobjx86-64/vterm_unicode.o gobjx86-64/vterm_vterm.o gobjx86-64/sound.o gobjx86-64/xdiffi.o gobjx86-64/xemit.o gobjx86-64/xprepare.o gobjx86-64/xutils.o gobjx86-64/xhistogram.o gobjx86-64/xpatience.o gobjx86-64/gui.o gobjx86-64/gui_w32.o gobjx86-64/gui_beval.o -lkernel32 -luser32 -lgdi32 -ladvapi32 -lcomdlg32 -lcomctl32 -lnetapi32 -lversion -lws2_32 -ld2d1 -ldwrite -Lxpm/x64/lib -lXpm -lwinmm -lole32 -luuid
C:/Users/voropaev.andrey/StrawberryPerl/c/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: xpm/x64/lib/libXpm.a(RdFToI.o):RdFToI.c:(.text+0xf2): undefined reference to __imp___iob_func' C:/Users/voropaev.andrey/StrawberryPerl/c/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: xpm/x64/lib/libXpm.a(RdFToI.o):RdFToI.c:(.text+0x12f): undefined reference to __imp___iob_func'
collect2.exe: error: ld returned 1 exit status
gmake: *** [Make_cyg_ming.mak:1169: gvim.exe] Error 1

Expected behaviour
I hoped to get gvim.exe as described in INSTALLpc.txt
Version of Vim
Latest sources
Environment
Windows 11 (cmd.exe)
gcc --version
gcc (MinGW-W64 x86_64-ucrt-posix-seh, built by Brecht Sanders, r8) 13.2.0
This MinGW is part of StrawberryPerl-5.40. But I've tried it also with latest MinGW (14.2) obtained from winlibs.com, the outcome was the same.
Logs and stack traces
No response

Did this work before? What patch broke it? Try to disable xpm support

Well, some years ago I compiled version 9.0 with mingw in
StrawberryPerl-5.32. Possibly, this is connected to the change of C-library
under Windows. I'll try to get  mingw with support for old library
On Wed, Dec 25, 2024, 17:00 Christian Brabandt @.***>
wrote:

Did this work before? What patch broke it? Try to disable xpm support
—
Reply to this email directly, view it on GitHub
https://github.com/vim/vim/issues/16301#issuecomment-2561937348, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AHVTP3IKTUDP3HFUUVEAPRT2HLJBFAVCNFSM6AAAAABUGBSYL6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRRHEZTOMZUHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Exactly, I should have thought about it earlier. Now I've used
gcc --version
gcc (MinGW-W64 x86_64-msvcrt-posix-seh, built by Brecht Sanders, r2) 14.2.0
This version uses old msvcrt library instead of new ucrt. Now compilation was successful. And I've looked at documentation for libXpm.a at http://gnuwin32.sf.net. They mention it explicitly there, that the version is compiled against msvcrt.
Now, to compile gvim with perl I'll have to use version of gcc that comes with perl. Let's see if it works without support for Xpm.

There seems to be an issue with the distributed libXpm.a file. It seems like __imp___iob_func is no longer defined. I don't know how to fix this, but you should be able to build using mingw32-make -f Make_ming.mak ARCH=x86_64 XPM=no gvim.exe
Ah, I just see your newer message. Can you please suggest a change for INSTALLpc.txt to clarify this please?

You mean, I should push a patch for INSTALLpc.txt? Or some text in this thread would be enough?

Yes some doc patch for INSTALLpc.txt mentioning that msvcrt runtime is required for XPM support

Ok, I've created pull-request. Hopefully I did it correctly, github always gives me headache :)
I close this issue, since I could compile gvim with support for Perl and I don't need support for XPM. Maybe in the future it would be possible to get libXpm.a for both C-Libraries, since UCRT is considered to be better than MSVCRT.


github-util: Update FROM version

Update underlying docker images.
Issue number: #1

no-op PR from automation


Adding nth fibonacci code in python

Solving #27

The old function had to be updated. A new file was not required for this issue

The CI checks are failing. Please review your code.

Please sync your fork with upstream. The test case was incorrect (#75 ) which has been fixed #76


ENH: Return full dataset for subsequent analysis

As per discussion with @nehargupta via email, it'd be helpful if dame returned an analysis dataset. results is a start, but it drops treatment assignment and outcome, and the insertion of "*" values means it can't actually be used for analysis.
Basically, most people I know who do matching in the social sciences expect the matching package to return a data set with all the matched pairs. In 1 to 1 matching, that data set is just a subset of the original data set for which matches were found. In many to one matching, observations that are matched more than once end up being repeated in the data set but with weights that reflect that fact. you can see this in the matchit docs here:
https://kosukeimai.github.io/MatchIt/articles/MatchIt.html#estimating-the-treatment-effect (you may have to scroll up a little for context).
Here's a super-crude implementation of what I'm looking for, where result_of_fit is the output of the match (the "result"), and model is my fitted model.
def get_dataframe(model, result_of_fit):

    # Get original data
    better = model.input_data.loc[result_of_fit.index]

   # Get match groups for clustering
   matched_data["match_group"] = np.nan
   for idx, group in enumerate(model.units_per_group):
       matched_data.loc[group, "match_group"] = idx

    # Weights
    better["weights"] = 1 / model.groups_per_unit

    if not model.repeats:
        assert (better["weights"] == 1).all()

    # Make sure right N!
    assert len(result_of_fit) == len(better)

    return better

EDIT: Oops. @nehargupta points out the result that the index in result_of_fit IS preserved, so edited with much much simpler solution.

@nehargupta you were right about index. Fixed solution.

Realizing the "weights" solution there is wrong -- repeats=False does not imply 1:1 matching. Gotta remember how weights are calculated when not doing 1:1 matching... It's the inverst for 1:1 matching with replacement, but here we can get odd sized groups of matches (e.g. 3 observations all matching).

This might implement weights correctly?

def get_dataframe(model, result_of_fit):

    # Get original data
    better = model.input_data.loc[result_of_fit.index]

    # Get match groups for clustering
    better["match_group"] = np.nan
    better["match_group_size"] = np.nan
    for idx, group in enumerate(model.units_per_group):
        better.loc[group, "match_group"] = idx
        better.loc[group, "match_group_size"] = len(group)

    # Get weights. I THINK this is right?! At least for with repeat=False?
    t = model.treatment_column_name
    better["t_in_group"] = better.groupby("match_group")[t].transform(np.sum)
    better["share_t_in_group"] = better["t_in_group"] / better["match_group_size"]
    better.loc[better[t] == 0, "prelim_weight"] = 1
    better.loc[better[t] == 1, "prelim_weight"] = 1 / better["share_t_in_group"]
    better["group_prelim_weight"] = better.groupby("match_group")[
        ["prelim_weight"]
    ].transform(sum)

    better["weights"] = better["prelim_weight"] * (
        better["match_group_size"] / better["group_prelim_weight"]
    )

    better = better.drop(
        ["prelim_weight", "group_prelim_weight", "t_in_group", "share_t_in_group"],
        axis="columns",
    )

    # Make sure right N!
    assert len(result_of_fit) == len(better)

    return better

But I'll admit my grasp of the stats of matching is limited -- I've never used it in research, so I've forgotten much of what I learned in class long ago. :)

Hi @nickeubank,
I’m not sure I am familiar with the goal...is it the definition of weights here?
https://www.rdocumentation.org/packages/MatchIt/versions/3.0.2/topics/matchit
I initially thought it would be just the groups_per_unit parameter as it is, but that parameter is just the number of times a unit appears in a group (which is 1 for each unit if repeats=False, but that doesn't mean it's only matched to one unit, since groups can be any size 2->n where n is the number of units).
Sorry for the vocabulary confusion, I'm not that familiar with the other packages, but we welcome any suggestions that would help us to have more typical naming convention.
Glad you got the reindex issue figured out (we force a reindex if non-unique indexes because that would break it, we might want to add a user-warning in that case I guess, or possibly also non-integer if I remember correctly). Let me know if there's anything else!

Hahaha -- don't worry -- this is not a domain in which I'm expert, so any errors are probably the same as mine.
When the weights are right, then running a weighted least squares should give us our treatment effect estimate. e.g.:
smf.wls(
    "annual_earnings ~ has_college", matched_data, weights=matched_data["weights"]
).fit().summary()

But now you get statistical significance, can add coefficients for non-exact match corrections, cluster standard errors, etc.
OK, the more current docs for matchit have a longer definition (https://www.rdocumentation.org/packages/MatchIt/versions/4.1.0/topics/matchit), but also one I think is incomplete...

How Matching Weights Are Computed
Matching weights are computed in one of two ways depending on whether matching was done with replacement or not.
For matching without replacement, each unit is assigned to a subclass, which represents the pair they are a part of (in the case of k:1 matching) or the stratum they belong to (in the case of exact matching, coarsened exact matching, full matching, or subclassification). The formula for computing the weights depends on the argument supplied to estimand. A new stratum "propensity score" (p) is computed as the proportion of units in each stratum that are in the treated group, and all units in that stratum are assigned that propensity score. Weights are then computed using the standard formulas for inverse probability weights: for the ATT, weights are 1 for the treated units and p/(1-p) for the control units; for the ATC, weights are (1-p)/p for the treated units and 1 for the control units; for the ATE, weights are 1/p for the treated units and 1/(1-p) for the control units.
For matching with replacement, units are not assigned to unique strata. For the ATT, each treated unit gets a weight of 1. Each control unit is weighted as the sum of the inverse of the number of control units matched to the same treated unit across its matches. For example, if a control unit was matched to a treated unit that had two other control units matched to it, and that same control was matched to a treated unit that had one other control unit matched to it, the control unit in question would get a weight of 1/3 + 1/2 = 5/6. For the ATC, the same is true with the treated and control labels switched. The weights are computed using the match.matrix component of the matchit output object.
In each treatment group, weights are divided by the mean of the nonzero weights in that treatment group to make the weights sum to the number of units in that treatment group. If sampling weights are included through the s.weights argument, they will be included in the matchit output object but not incorporated into the matching weights. match.data, which extracts the matched set from a matchit object, combines the matching weights and sampling weights.

If weights are just 1 for treated units, and then 1/(num controls matched to a treatment) for treatments in a match group, then this would do it I think?
def get_dataframe(model, result_of_fit):

    # Get original data
    better = model.input_data.loc[result_of_fit.index]

    # Get match groups for clustering
    better["match_group"] = np.nan
    better["match_group_size"] = np.nan
    for idx, group in enumerate(model.units_per_group):
        better.loc[group, "match_group"] = idx
        better.loc[group, "match_group_size"] = len(group)

    # Get weights. I THINK this is right?! At least for with repeat=False?
    t = model.treatment_column_name
    better["t_in_group"] = better.groupby("match_group")[t].transform(np.sum)
    better["weights"] = np.nan
    better.loc[better[t] == 1, "weight"] = 1
    better.loc[better[t] == 0, "weights"] = (
        better["match_group_size"] - better["t_in_group"]
    ) / better["t_in_group"]
    print(better.weights.value_counts(dropna=False))
    assert better.weights.notnull().all()

    better = better.drop(["t_in_group"], axis="columns")

    # Make sure right N!
    assert len(result_of_fit) == len(better)

    return better

Oh! I didn't realize you wanted the weights to put the dataset in a WLS regression, now I see! Ok, thank you. I will need to think about this more before proceeding...

(nudge)

Dropping another nudge here.


emacsPackages: remove outdated helm

Things done:

[x] Tested using sandboxing (nix-build --option build-use-chroot true -A emacsPackagesNg.helm)
Built on platform(s)

[ ] NixOS
[ ] OS X
[x] Linux

[x] Tested compilation of some pkgs that depend on this change using emacsWithPackages (epkgs: [ epkgs.helm epkgs.helm-projectile ])
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

More
helm-20150105 was added in https://github.com/NixOS/nixpkgs/pull/6250, which looks like an abandoned path since we now have automatically generated melpa packages.
Meanwhile, helm-projectile (probably among other packages) requires a newer helm (one that has helm-types.el i.e. 1.7.7 onwards). helm-1.9.2 is already in melpa-stable-generated.nix. This removal makes that work (and hopefully others).
Question: is there any plan for emacs-packages.nix? IIUC it's just there for overrides (e.g. when some auto generated melpa packages are broken). If there are melpa generated packages that aren't broken, they should be removed from emacs-packages.nix, is that correct?

Please note, that points are not mandatory, but rather desired.

Can you rebase on top of master ? It looks like there is a merge conflict

cc @oxij

@zimbatm not sure how the conflict happened (I rebased and didn't see anything), but updated anyway


0.41.3 shows error on boot and cannot be started

Microsoft PowerToys version
0.41.3
Running as admin

[X] Yes

Area(s) with issue?
General
Steps to reproduce
Windows 10 x64 Pro 21H1
Just boot the OS - the error message appears.
Powertoys cannot be started at all.
The message in Windows log:
Application: PowerLauncher.exe
CoreCLR Version: 4.700.21.26205
.NET Core Version: 3.1.16
Description: The process was terminated due to an unhandled exception.
Exception Info: System.TypeInitializationException: The type initializer for 'System.Windows.Threading.Dispatcher' threw an exception.
---> System.ComponentModel.Win32Exception (5): Отказано в доступе.
at System.Diagnostics.ProcessManager.OpenProcess(Int32 processId, Int32 access, Boolean throwIfExited)
at System.Diagnostics.NtProcessManager.GetModules(Int32 processId, Boolean firstModuleOnly)
at System.Diagnostics.Process.get_Modules()
at System.Windows.WpfDllVerifier.VerifyWpfDllSet(String[] additionalDlls)
at System.Windows.Threading.Dispatcher..cctor()
--- End of inner exception stack trace ---
at System.Windows.Threading.Dispatcher.get_CurrentDispatcher()
at System.Windows.Threading.DispatcherObject..ctor()
at System.Windows.Application..ctor()
at PowerLauncher.App..ctor()
at PowerLauncher.App.Main()
✔ Expected Behavior
Normal start during boot
❌ Actual Behavior
Message error on Welcome screen
Other Software
No response

Looks for me like #11955

@gjf
Right-click on the PowerToys icon in the tray menu and select Report Bug

Drag and drop report into a GitHub comment.

@gjf
Right-click on the PowerToys icon in the tray menu and select Report Bug

Drag and drop report into a GitHub comment.

Impossible because Powertoys cannot be started - please read my first post attentively.

@gjf
Can you start PowerToys manually?
If not

Go to C:\Program Files\PowerToys\Tools
Run BugReportTool.exe
Drag and drop the bug report from the desktop into the github comment

Here we go:
PowerToysReport_2021-06-30-21-17-32.zip

After reverting back to 0.37.2 and installing 0.41.3 again I was able to start Powertools manually.
After reboot I cannot observe the error any more. So possibly the issue resolved - no idea what it was.
Anyway - maybe logs will show something.

@mykhailopylyp is this a dup against #11955?

Today the error on boot starts appearing again.
However I can see the icon of Powertoys and it seems working.
PowerToysReport_2021-07-01-13-30-27.zip

@mykhailopylyp is this a dup against #11955?

From the bug report it looks as a duplicate.

@gjf
We will release a hotfix shortly. Feel free to reopen if will still reproduce.


Rating events misbehaving in OS X Safari 9

Simple enough to reproduce; visit the demo page for ratings in Safari 9 and try clicking on a rating. The mouseover events work fine, but the click doesn't seem to register, and so the rating value doesn't persist.

I could reproduce the issue in Safari. Will look into this probably tomorrow. Thanks for letting us know :smile:

Sorry, took me a bit longer to get to it fixed here https://github.com/nikgraf/belle/issues/277 und cutting a new release now

Awesome! Thank you so much. :beers:


Activity io.flutter.embedding.android.FlutterActivity has leaked IntentReceiver com.pauldemarco.flutter_blue.FlutterBluePlugin$1$1@c0fd054 that was originally registered here. Are you missing a call to unregisterReceiver()?

E/ActivityThread(10556): Activity io.flutter.embedding.android.FlutterActivity has leaked IntentReceiver com.pauldemarco.flutter_blue.FlutterBluePlugin$1$1@c0fd054 that was originally registered here. Are you missing a call to unregisterReceiver()?
E/ActivityThread(10556): android.app.IntentReceiverLeaked: Activity io.flutter.embedding.android.FlutterActivity has leaked IntentReceiver com.pauldemarco.flutter_blue.FlutterBluePlugin$1$1@c0fd054 that was originally registered here. Are you missing a call to unregisterReceiver()?
E/ActivityThread(10556):        at android.app.LoadedApk$ReceiverDispatcher.<init>(LoadedApk.java:1437)
E/ActivityThread(10556):        at android.app.LoadedApk.getReceiverDispatcher(LoadedApk.java:1214)
E/ActivityThread(10556):        at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1486)
E/ActivityThread(10556):        at android.app.ContextImpl.registerReceiver(ContextImpl.java:1459)
E/ActivityThread(10556):        at android.app.ContextImpl.registerReceiver(ContextImpl.java:1447)
E/ActivityThread(10556):        at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:633)
E/ActivityThread(10556):        at com.pauldemarco.flutter_blue.FlutterBluePlugin$1.onListen(FlutterBluePlugin.java:731)
E/ActivityThread(10556):        at io.flutter.plugin.common.EventChannel$IncomingStreamRequestHandler.onListen(EventChannel.java:193)
E/ActivityThread(10556):        at io.flutter.plugin.common.EventChannel$IncomingStreamRequestHandler.onMessage(EventChannel.java:172)
E/ActivityThread(10556):        at io.flutter.embedding.engine.dart.DartMessenger.handleMessageFromDart(DartMessenger.java:93)
E/ActivityThread(10556):        at io.flutter.embedding.engine.FlutterJNI.handlePlatformMessage(FlutterJNI.java:642)
E/ActivityThread(10556):        at android.os.MessageQueue.nativePollOnce(Native Method)
E/ActivityThread(10556):        at android.os.MessageQueue.next(MessageQueue.java:326)
E/ActivityThread(10556):        at android.os.Looper.loop(Looper.java:165)
E/ActivityThread(10556):        at android.app.ActivityThread.main(ActivityThread.java:6806)
E/ActivityThread(10556):        at java.lang.reflect.Method.invoke(Native Method)
E/ActivityThread(10556):        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
E/ActivityThread(10556):        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)
W/ActivityThread(10556): handleWindowVisibility: no activity for token android.os.BinderProxy@5c39dc0

When you click the return key of the mobile phone, this error will appear. The official example is the same. Why? How to solve it?

Same here.

I think it's a duplicate of https://github.com/pauldemarco/flutter_blue/issues/228 ?


Refactor(findDOMNode, string ref): replace deprecated findDOMNode and string ref

Addresses issue: #430
Replacing findDOMNode and string ref usage with callback refs so code run in StrictMode doesn't give warnings.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


withCredentials() on Cross-Origin-Calls

Hello,
we are working on a learning platform based upon TinCan. Most course suppliers are using the Rustici-Tincan-Library and we like it. The course storage is on a different domain than the LRS-Endpoint. However we would like our users to be authenticated at the LRS in order to check if users are allowed to send this specific Tincan-Statement.
In our case Authentication is done via Cookies. Now we have the problem, that the TinCan-Calls do not contain any cookies at all. As they are Cross-Origin-Calls (CORS-Headers are all set) they need to have 'withCredentials' set inside the XMLHttpRequest object, otherwise cookies won't be send. Interestingly TinCanJS looks for this specific attribute and sets env.hasCORS to true but this gets not evaluated...
Is it planned to call withCredentials() in the future?

There isn't a specific plan in place to include it in the future, though pull requests tend to have the effect of speeding up any plan :-). I can honestly say I'd not looked into withCredentials enough to know what it did beyond indicating CORS capability in a client. I'm not opposed to adding the capability to set it so that cookies are sent though it would be a fairly unorthodox usage of Tin Can at the moment. I wouldn't want to just set it by default to on as that would be a pretty big change in the request dynamic.
Presumably in this case there is no "Authorization" header sent, and in general I think this becomes a new "Auth Type" for the library so would need to have a config setting for the LRS object to activate it. It would also be an issue in the Node environment because we don't have a cookie jar working automatically for us, though that could be set aside and just prevent constructing an LRS object in that environment, or hook into whatever the request module provides for cookie handling.

Thanks for your response. I am also not sure if it would be making sense in activating this flag by default inside the TinCan-Library because it may imply other problems or raise security concerns.
Anyway, we circumvented the problem now with putting the LRS and the Course Storage behind the same reverse proxy thus making them visible by being served from the same domain and disabling CORS entirely.
I just wanted to make sure if there isn't not another "hidden" configuration option we could use ;)


Deleted versions of episodes are not removed and still show on Web UI

I deleted one version of all episodes in a TV show from the filesystem.
However, I cannot seem to get them removed from the DB and Web UI. The show's episodes still come up with the version selector, and the '2' icon on the top left.
I tried splitting all episodes, then rescanning the library, then re-merging all episodes, but no results, the episodes still show as if they have two versions. I have confirmed the alternate version has indeed been deleted from the filesystem.
Is this a known bug? Is there a way to get the web UI to not show this non-existent version any more?

After a while my UI stopped showing the deleted version (even though the library scan had finished ages ago), and only the version counter badge remains, which suggests this is the same bug as this:
https://github.com/jellyfin/jellyfin/issues/9281
So, happy to report this is not related to the plugin.


Project dead?

What's the status of this repo? No release in 2 years, 400+ issues unresolved. Is this project still - somehow - maintained?

You’re right there isn’t a lot going on.
I think I’m the only person listed in the MAINTAINERS file who’s still interested, though sadly I didn’t spend any time on Scope lately.
Maybe someone from Weaveworks will comment.

The only options are a community fork or Weaveworks transferring ownership.

Perhaps worth posting this link:
https://www.linkedin.com/posts/richardsonalexis_hi-everyone-i-am-very-sad-to-announce-activity-7160295096825860096-ZS67

happy to help with any forks / moves

I would like to help

I was able to build the code from the default branch and it still works with Docker using the provided Dockerfile.
My understanding is that it needs a few small changes to work with recent k8s, since the API's have changed.


Troubleshoot Ansible Conjur installation on 2.9

##Bug description
Please see [ONYX-14300|https://ca-il-jira.il.cyber-ark.com:8443/browse/ONYX-14300] for details. This was originally raised as a documentation issue but may indicate a bug. Try reproducing with Ansible 2.9 to determine if there's a bug here.
If there is a problem, spend a little time figuring out what's wrong and then either fix it if it's something simple or file a new issue w/ details describing a proper fix.
If this does end up being a docs change, please let Shuli know by commenting on [ONYX-14300|https://ca-il-jira.il.cyber-ark.com:8443/browse/ONYX-14300].
##Found in version
12.0
##Workaround Complexity
NA
##Workaround Description
##Affects Version/s
##Link to JIRA bug
https://ca-il-jira.il.cyber-ark.com:8443/browse/ONYX-14387

https://ca-il-jira.il.cyber-ark.com:8443/browse/ONYX-14387


tfsec: 0.58.12 -> 0.58.14

Motivation for this change
Update to latest upstream release 0.58.14
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 140866 run on x86_64-linux 1

1 package built:

tfsec


Add JavaFX Application

🚀 Feature
JavaFX Applications
Hello, I would like to add some JavaFX Applications

@debajitdeb11 you can create a pull request for the same.


[Runtime] Enable option to use OpenMP thread pool

I found that when TVM uses MKL library, two different threadpool implementation competes for CPUs and leads to pool performance. This PR adds an option in the compiler flag to use OpenMP threadpool. It also helps TVM integration with MxNet as it uses OpenMP threadpool.
cc @yidawang @yzhliu @tqchen

ping @icemelon9

@tqchen Could you take a look again?

Thanks @icemelon9 @soiferj @yidawang @junrushao1994 @tmoreau89 !


The following silly piece of code lives (probably) forever in mono, but crashes in dotnet after 217 iterations on my machine:
public static void Main() {
            for (int i = 0; i < int.MaxValue; i++) {
                Process.Start(new ProcessStartInfo {
                    FileName = "ls",
                    UseShellExecute = false,
                    RedirectStandardOutput = true
                });
                Console.WriteLine(i);
            }
}

Adding a .StandardOutput.Close() extends lifetime 5 fold, indicating other things are not being collected.

Product Information:
 Version:            2.0.2
 Commit SHA-1 hash:  a04b4bf512

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.13
 OS Platform: Darwin
 RID:         osx.10.12-x64
 Base Path:   /usr/local/share/dotnet/sdk/2.0.2/

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0
  Build    : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d```

Issue moved to dotnet/corefx #25962 via ZenHub


Add an option to skip the create view and action

--no-create should skip generation of:

"create a new Model" link
new and create controller actions and views

I'll create a separate issue for --read_only.


Build fails with HPX_WITH_HWLOC=OFF

> make hello_world_exe
[  0%] Building CXX object src/CMakeFiles/hpx.dir/runtime.cpp.o
In file included from /home/simbergm/src/hpx/hpx/runtime/serialization/detail/polymorphic_nonintrusive_factory.hpp:23:0,
                 from /home/simbergm/src/hpx/hpx/lcos/future.hpp:15,
                 from /home/simbergm/src/hpx/hpx/performance_counters/counters.hpp:10,
                 from /home/simbergm/src/hpx/hpx/performance_counters/counter_creators.hpp:11,
                 from /home/simbergm/src/hpx/src/runtime.cpp:10:
/home/simbergm/src/hpx/hpx/util/static.hpp: In instantiation of ‘static T& hpx::util::static_<T, Tag>::get_reference() [with T = hpx::threads::noop_topology; Tag = hpx::threads::noop_topology::noop_topology_tag; hpx::util::static_<T, Tag>::reference = hpx::threads::noop_topology&]’:
/home/simbergm/src/hpx/hpx/util/static.hpp:50:26:   required from ‘hpx::util::static_<T, Tag>::static_() [with T = hpx::threads::noop_topology; Tag = hpx::threads::noop_topology::noop_topology_tag]’
/home/simbergm/src/hpx/hpx/runtime/threads/policies/noop_topology.hpp:243:68:   required from here
/home/simbergm/src/hpx/hpx/util/static.hpp:76:22: error: cannot declare variable ‘t’ to be of abstract type ‘hpx::threads::noop_topology’
             static T t;
                      ^
In file included from /home/simbergm/src/hpx/hpx/runtime/threads/policies/topology.hpp:12:0,
                 from /home/simbergm/src/hpx/src/runtime.cpp:25:
/home/simbergm/src/hpx/hpx/runtime/threads/policies/noop_topology.hpp:32:8: note:   because the following virtual functions are pure within ‘hpx::threads::noop_topology’:
 struct noop_topology : topology
        ^
In file included from /home/simbergm/src/hpx/hpx/runtime/threads/thread_executor.hpp:14:0,
                 from /home/simbergm/src/hpx/hpx/lcos/detail/future_data.hpp:16,
                 from /home/simbergm/src/hpx/hpx/lcos/future.hpp:12,
                 from /home/simbergm/src/hpx/hpx/performance_counters/counters.hpp:10,
                 from /home/simbergm/src/hpx/hpx/performance_counters/counter_creators.hpp:11,
                 from /home/simbergm/src/hpx/src/runtime.cpp:10:
/home/simbergm/src/hpx/hpx/runtime/threads/topology.hpp:195:34: note:   virtual hpx::threads::hwloc_bitmap_ptr hpx::threads::topology::cpuset_to_nodeset(hpx::threads::mask_cref_type) const
         virtual hwloc_bitmap_ptr cpuset_to_nodeset(
                                  ^
/home/simbergm/src/hpx/hpx/runtime/threads/topology.hpp:206:23: note:   virtual void* hpx::threads::topology::allocate_membind(std::size_t, hpx::threads::hwloc_bitmap_ptr, hpx::threads::hpx_hwloc_membind_policy, int) const
         virtual void* allocate_membind(std::size_t len,
                       ^
/home/simbergm/src/hpx/hpx/runtime/threads/topology.hpp:210:36: note:   virtual hpx::threads::mask_type hpx::threads::topology::get_area_membind_nodeset(const void*, std::size_t, void*) const
         virtual threads::mask_type get_area_membind_nodeset(
                                    ^
/home/simbergm/src/hpx/hpx/runtime/threads/topology.hpp:213:22: note:   virtual bool hpx::threads::topology::set_area_membind_nodeset(const void*, std::size_t, void*) const
         virtual bool set_area_membind_nodeset(
                      ^
/home/simbergm/src/hpx/hpx/runtime/threads/topology.hpp:216:21: note:   virtual int hpx::threads::topology::get_numa_domain(const void*, void*) const
         virtual int get_numa_domain(const void *addr, void *nodeset) const = 0;
                     ^
src/CMakeFiles/hpx.dir/build.make:206: recipe for target 'src/CMakeFiles/hpx.dir/runtime.cpp.o' failed
make[3]: *** [src/CMakeFiles/hpx.dir/runtime.cpp.o] Error 1
CMakeFiles/Makefile2:1353: recipe for target 'src/CMakeFiles/hpx.dir/all' failed
make[2]: *** [src/CMakeFiles/hpx.dir/all] Error 2
CMakeFiles/Makefile2:6713: recipe for target 'examples/quickstart/CMakeFiles/hello_world_exe.dir/rule' failed
make[1]: *** [examples/quickstart/CMakeFiles/hello_world_exe.dir/rule] Error 2
Makefile:2279: recipe for target 'hello_world_exe' failed
make: *** [hello_world_exe] Error 2

Relevant issue: #2977
@biddisco

I think this can be easily fixed by adding dummy implementations for the missing virtual functions to hpx::threads::noop_topology.
@msimberg would you mind having a look? I don't think we should wait for #2977 just for this.

@hkaiser, @biddisco will have a look.

Didn't we agree to require hwloc now?

Shrug whatever. Adding the missing virtual functions is a matter of 5 minutes, making hwloc mandatory takes more time.

Closing because of #3133.


star-rating cannot work with float values

When ratings are in the form of 3.2 3.8 4.1 then the star-rating widget cannot work because it's adding refinements like "rating = 2" or "rating = 3".
I wonder if we could use numeric filters? Maybe not because we want the counts for each rating, is that it?

Indeed, it's "designed" to run on integers and having the counts on floating point numbers won't be possible. I would rather insist on the "must be integers from 0 to 5" in the documentation.

Ok will add that, also its totally ok to still duplicate the rating attribute in precise form and have it configured as a custom ranking attribute so that the ranking is still very precise.


Remove Composer self-updating from .travis.yml

It is done automatically by Travis.

Glad they do this now! They might have been doing it for ages, but at some point they were not. :)

Crap, moments too late... Travis currently does composer self-update 1.0.0 which was released 2016-04-05. The current stable version is 1.3.0.
I recommend reverting this.

The biggest reason we need version 1.3.0 is because it fixes the "running composer with xdebug" problem.

Done!

Travis updates Composer to 1.0.0 first and to 1.3.1 then, it's correct behaviour, isn't it?

There's a Sylius build running self-update on before_script as well, saying that the newest version is already installed: https://travis-ci.org/Sylius/Sylius/jobs/195153143#L195-L196

@pamil @philsturgeon ah crap, I messed up here. I thought the self-update to stable was being run because of my own self-update call, but looking closer I see that is not the case. I don't know why Travis runs self-update 1.0.0 first, but @pamil is correct.
I recommend removing the revert command and doing a force push.
Apologies for the confusion.

https://github.com/thephpleague/skeleton/pull/108


update default consulUrl to http instead of https

The default consul.yml in the consul module is connecting to localhost consul agent for testing. Most cases, users will start the consul with the docker and only http is available. To make it suitable for this use case, let's change the consulUrl to http instead.
To start the consul locally.
docker run -d -p 8400:8400 -p 8500:8500/tcp -p 8600:53/udp -e 'CONSUL_LOCAL_CONFIG={"acl_datacenter":"dc1","acl_default_policy":"allow","acl_down_policy":"extend-cache","acl_master_token":"the_one_ring","bootstrap_expect":1,"datacenter":"dc1","data_dir":"/usr/local/bin/consul.d/data","server":true}' consul agent -server -ui -bind=<IP_ADDRESS> -client=<IP_ADDRESS>

 update default consulUrl to http instead of https


NIFI-2553 Fixing handling of Paths in HDFS processors

@bbende I can pick this up

@bbende  ran several tests on 3 node HDFS cluster doing file movement from and to HDFS. Forced EL syntax errors on all changed processors and they reported as expected. Please let me let me know about comments provided above, otherwise all looks good.

@YolandaMDavis Thanks for reviewing and testing! After looking at the existing EL validator in StandardValidators, it wasn't used by any processor and I believe the logic didn't fully make sense. It was saying "if a property supports EL and EL is present, return true" but this doesn't mean the EL was valid.
So I replaced it with the logic from the validator in the abstract hadoop processor which I believe is correct... "if EL is supported and EL is present, check if all expressions are valid and return true if they are, otherwise return the message about what wasn't valid. If EL is not supported, or if EL is not present, return true"

@bbende thanks for the updates and comments on working directory. All looks good!
+1
Will merge as soon as possible.


Test failures while running test-integration test suite on ppc64le

Some of odo test-integration fail with the below error on ppc64le:-
[odo]   Could not find a version that satisfies the requirement pip==19.3.1 (from versions: )
[odo] No matching distribution found for pip==19.3.1
[odo]  ✗  command terminated with exit code 1

Trying to investigate this further, any leads would be helpful.
Attaching is detailed spec failure -
odo_17-FAILURE_Z_PR_3716_3744-Integration_with_P_3m5w.txt

/area system-pz

Was able to resolve this using --env HTTP_PROXY=http://<IP_ADDRESS>:3128 --env HTTPS_PROXY=http://<IP_ADDRESS>:3128 while executing odo create


parse return wrong date

Hi, I'm using the following code:
       `var originImage = await s3.getObject(params).promise();

        var buffer = await sharp(originImage.Body).withMetadata().toBuffer();

        var parser = require('exif-parser').create(buffer);

        var exifData = await  metaDataService.Convert(parser.parse());`

All the data is fine, expect for the dates. I'm getting the following:
ModifyDate:<PHONE_NUMBER>,
DateTimeOriginal:<PHONE_NUMBER>,
CreateDate:<PHONE_NUMBER>,
All these and translated to dates from 1970 (!).
But the image creation date is 19/07/2020 14:22.
What might be the problem?
Thanks

They seem to be without the millisecond part, so you need to multiply it by 1000 to get the correct date:
> new Date(1595168559)
> Mon Jan 19 1970 11:06:08

> new Date(1595168559 * 1000)
> Sun Jul 19 2020 14:22:39

They seem to be without the millisecond part, so you need to multiply it by 1000 to get the correct date:
> new Date(1595168559)
> Mon Jan 19 1970 11:06:08

> new Date(1595168559 * 1000)
> Sun Jul 19 2020 14:22:39


Rename EmergencyExit to EmergencyExitAnnotation

Changes
Change the naming rule of the annotation class name to the same as that of the test-helper.monkey.
see: https://github.com/nowsprinting/test-helper.monkey/tree/master/Annotations
Priority
It's a low priority for me.

Contribution License Agreement

[x] By placing an "x" in the box, I hereby understand, accept and agree to be bound by the terms and conditions of the Contribution License Agreement.

@nowsprinting
Thank you for your contribution!


add an align function

should fast-forward the assembler pointer to the nearest place divisible by n
eg
(align 256)
:table (data 1 2 3)

done 7dfa964db50ae2bf623e44295071f5c1c4aee7ae


Ignore rmtree Errors

https://github.com/lean-dojo/LeanDojo/issues/168

I'll also re-build the docs and pypi wheels after merging into main

LGTM, thank you! Merging into main.


New App Submission

App Logo (Required)
(Attach image here)

App Details (Required)
Type: Wallet
Name:PayTube
Homepage Url:https://www.paytube.io/
Chains supported: Ethereum
App Url (Required - at least one)
Browser Url:
iOS Url:https://apps.apple.com/us/app/paytube/id1574456998
Android Url:https://play.google.com/store/apps/details?id=com.paytube.wallet.zkwallet
Mac Url:
Windows Url:
Linux Url:
Mobile Linking (Optional)
Deep Link:
Universal Link:
Desktop Linking (Optional)
Deep Link:
Universal Link:
Metadata (Optional)
Short Name:PayTube
Primary Color:
Secondary Color:

Added on commit 809468cab00bdb5bd7200c326d3294ddbeac9db3


remove deprecated bqx and bqext

This change is

Pull Request Test Coverage Report for Build 858

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+2.0%) to 84.739%

Totals

Change from base Build 843:
2.0%

Covered Lines:
1266

Relevant Lines:
1494

💛  - Coveralls


Program freezes when hitting Esc when the list of container actions is shown

dry is awesome and works great in most cases. But I encountered a case where the program freezes and can reproduce this every time. It's only in a very specific case though (at least it seems so).
To reproduce:

Start via CLI with dry
Show the command list with Enter on the first container
Close the command list with Esc
=> Program goes back to the list of all filtered containers, but is then completely frozen (Esc, q and any other shortcut doesn't work, only Ctrl+C works)

Note: This does not happen when you move the selection in the command list before. So when the command list is shown and you hit Down and then Esc, everything works fine. Also, when having done this a single time, and then opening more command lists and closing them without hitting Down, everything works fine as well. So for some reason, only the first opening/closing of the command list matters here.

P.S.:

Installed via go get, with Go 1.11.5
Installed dry commit a1a56132d75fba85443cf4811fa6bee257d24c0e

(dry --version is: dry version , build, so it doesn't contain any info, probably because installing with go get doesn't lead to the required code generation or setting of constant values in the code)

Thanks for reporting it and the clear instructions!!

hi @philippgille
I have not been able to reproduce the problem following your instructions, could you please try again? Thanks


[question] Multimodal input

Hello,
What's the proper way to handle multi modal input? i.e. an image and a vector input? My current approach is to pretrain some other model (e.g. VAE) and wrap it around the environment, then concat the two. The downside of this is that the gradients aren't propagated.

Hello,
This may be a duplicate of #133 .
Short answer: you should use a custom policy, dict spaces are not supported yet.
Better support is planned for v3.1.
Using an autoencoder is a good solution, and I recommend that (see an example)

Hi,
I closed it as I found #133. I was mainly looking for ways to circumvent TF as my AE models are in PyTorch but I will figure it out. Thanks.

I was mainly looking for ways to circumvent TF as my AE models are in PyTorch but I will figure it out.

Tensorflow will be soon not a pb anymore with v3 ;) (finally !)
but you can take a look at #372 .


Using with Universal Render Pipeline

Hi,
I've used this on the build-in render pipeline and it works exactly as expected, but when trying to use it on a project with the universal render pipeline the video recorded is stored in the correspondent folder, but when I try to open it the video player shows an error.
Does the package support URP or HDRP?
Kind regards.

I also have the same issue


Aren't actions tied to a specific Store?

It's sort of weird...
I have 2 stores and 2 different actions module.
Both actions contain
    switch(payload.actionType) {
      case 'SET':
        //do something

It now looks like when I trigger one action, the other also gets called.

Actions are unique per the constant that defines them.  They are not
necessarily specific to a store.
Dave
On Oct 21, 2015 5:41 AM, "Marco F."<EMAIL_ADDRESS>wrote:

It's sort of weird...
I have 2 stores and 2 different actions module.
Both actions contain
switch(payload.actionType) {
  case 'SET':
    //do something

It now looks like when I trigger one action, the other also gets called.
—
Reply to this email directly or view it on GitHub
https://github.com/kenwheeler/mcfly/issues/53.

@mfirry that is the expected behaviour.  That is why you subscribe both stores to an specific action.  If you want to force store1 to do something with the payload before store2 you can always use in store2 the waitFor() promise.  If you want 2 different actions, then you should name them differently.

Good to know.


PROPOSAL: Allow class name to be specified by a variable dynamically

Like so:
var className = 'MySuperClass';
var MyClass = class [className] {};
console.log(MyClass.name); // MySuperClass

This is similar to how property names in object assignment can be variables:
var propName = 'MySuperProperty';
var obj = {
    [propName]: true,
};
console.log(obj); // {MySuperProperty: true}

Otherwise now all classes get class_1 name or something like that:
var MyClass = class {};
console.log(MyClass.name); // class_1

Class expressions are an ES6 feature and there's not anything motivating TypeScript to add this kind of syntax (i.e. it doesn't improve static typing at all), so this suggestion should go to ES Discuss / the TC39 committee.


ReR50-ReFPN   The model and loaded state dict do not match exactly

ReResNet Orientation: 8	Fix Params: False
loading annotations into memory...
Done (t=1.74s)
creating index...
index created!
The model and loaded state dict do not match exactly
missing keys in source state_dict: neck.fpn_convs.3.conv.expanded_bias, backbone.layer3.2.conv1.filter, neck.fpn_convs.0.conv.filter, backbone.layer3.1.conv3.filter, neck.fpn_convs.1.conv.filter, backbone.layer3.4.conv2.filter, backbone.layer3.5.conv1.filter, neck.lateral_convs.1.conv.expanded_bias, backbone.layer2.1.conv1.filter, neck.fpn_convs.2.conv.expanded_bias, backbone.layer2.3.conv2.filter, backbone.layer4.0.downsample.0.filter, backbone.layer4.1.conv1.filter, backbone.layer3.5.conv2.filter, backbone.layer4.1.conv3.filter, backbone.layer4.0.conv2.filter, backbone.layer3.1.conv2.filter, backbone.layer3.4.conv1.filter, neck.lateral_convs.3.conv.filter, backbone.layer3.3.conv2.filter, neck.fpn_convs.2.conv.filter, backbone.layer3.2.conv2.filter, neck.fpn_convs.1.conv.expanded_bias, backbone.layer2.2.conv1.filter, backbone.layer2.3.conv1.filter, backbone.layer3.2.conv3.filter, backbone.layer2.2.conv2.filter, backbone.layer4.2.conv3.filter, backbone.layer3.0.downsample.0.filter, backbone.layer4.2.conv2.filter, backbone.layer2.0.conv3.filter, backbone.layer2.1.conv3.filter, backbone.layer2.0.conv2.filter, backbone.conv1.filter, neck.fpn_convs.3.conv.filter, backbone.layer2.0.downsample.0.filter, neck.lateral_convs.0.conv.filter, backbone.layer2.2.conv3.filter, backbone.layer2.0.conv1.filter, backbone.layer4.1.conv2.filter, backbone.layer4.0.conv1.filter, backbone.layer3.0.conv3.filter, backbone.layer3.3.conv3.filter, backbone.layer4.0.conv3.filter, neck.lateral_convs.1.conv.filter, backbone.layer3.4.conv3.filter, neck.fpn_convs.0.conv.expanded_bias, backbone.layer3.0.conv1.filter, backbone.layer2.1.conv2.filter, neck.lateral_convs.0.conv.expanded_bias, neck.lateral_convs.2.conv.expanded_bias, backbone.layer2.3.conv3.filter, backbone.layer3.5.conv3.filter, neck.lateral_convs.3.conv.expanded_bias, backbone.layer3.0.conv2.filter, backbone.layer3.1.conv1.filter, backbone.layer3.3.conv1.filter, neck.lateral_convs.2.conv.filter, backbone.layer4.2.conv1.filter
why???what should i do???

https://github.com/csuhan/ReDet/issues/22

#22

tnx 👍
so its ok
but i test it an i got very low AP result for dota v1 :
This is your result for task 1:
mAP: 0.3796692927779224
ap of each class: plane:0.5393134760132164, baseball-diamond:0.2727272727272727, bridge:0.4428214528237172, ground-track-field:0.14898989898989898, small-vehicle:0.2509144865918008, large-vehicle:0.25942160410103354, ship:0.7073533101735577, tennis-court:0.5454545454545455, basketball-court:0.32725572697522204, storage-tank:0.09090909090909091, soccer-ball-field:0.21752528974341798, roundabout:0.14793388429752066, harbor:0.6952776159604523, swimming-pool:0.6333621700100804, helicopter:0.41577956689800866
why??


Setting test infrastructure

The intention of this PR is to show a working example for a posible test infrastructure for Chart.js.
The idea is to use a combination of mocha, chai and sinon and run them from gulp with gulp-mocha-phantomjs.
Please let me know what you think.
In order to run this:
gulp test

Install dependencies before:
npm install

We've recently announced a feature complete status for v1.x and will only be accepting bug fixes for v1.x. Be sure to take a look at v2.0-dev and it's new features that are either finished or currently under development.  If you see your feature is still not implemented, feel free to submit another PR to the v2.0-dev (or later) branch for your feature.


Error Deploying. Node Version?

Hi,
I forked and published in heroku and I got this error:

-----> Node.js app detected
-----> Creating runtime environment
NPM_CONFIG_LOGLEVEL=error
NPM_CONFIG_PRODUCTION=true
NODE_ENV=production
NODE_MODULES_CACHE=true
-----> Installing binaries
engines.node (package.json):  unspecified
engines.npm (package.json):   unspecified (use default)
Resolving node version (latest stable) via semver.io...
Downloading and installing node 5.8.0...
Using default npm version: 3.7.3
-----> Restoring cache
Skipping cache restore (new runtime signature)
-----> Building dependencies
Pruning any extraneous modules
Installing node modules (package.json)
><EMAIL_ADDRESS>postinstall /tmp/build_6619cd61696aad452aff1308273a9b6f/deckard86-angular2-express-slim-0c728da
> typings install && tsc
sh: 1: typings: not found
npm ERR! Linux 3.13.0-79-generic
npm ERR! argv "/tmp/build_6619cd61696aad452aff1308273a9b6f/deckard86-angular2-express-slim-0c728da/.heroku/node/bin/node" "/tmp/build_6619cd61696aad452aff1308273a9b6f/deckard86-angular2-express-slim-0c728da/.heroku/node/bin/npm" "install" "--unsafe-perm" "--userconfig" "/tmp/build_6619cd61696aad452aff1308273a9b6f/deckard86-angular2-express-slim-0c728da/.npmrc"
npm ERR! node v5.8.0
npm ERR! npm  v3.7.3
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>postinstall: typings install && tsc
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'typings install && tsc'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the angular2-express-slim package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     typings install && tsc
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs angular2-express-slim
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls angular2-express-slim
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /tmp/build_6619cd61696aad452aff1308273a9b6f/deckard86-angular2-express-slim-0c728da/npm-debug.log
-----> Build failed
We're sorry this build is failing! You can troubleshoot common issues here:
https://devcenter.heroku.com/articles/troubleshooting-node-deploys
Some possible problems:
- Node version not specified in package.json
https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version
Love,
Heroku
!     Push rejected, failed to compile Node.js app

How can I solve this? Thanks

No, it is not problem in Node version.
dev-dependencies are problem.
I fixed it on master branch, can you update your repository with latest changes?

Great! Thanks very much! :)

I am having the same problem, what was the solution?

@michaelb-01 When you cloned this repo?

@michaelb-01 I had the same issue and resolved it by adding typings to the dependencies itself, not just devDependencies.

@zzbennett  Thank you a lot

NPM_CONFIG_PRODUCTION needs to be set to false for Heroku to install devDependencies

I just ran into this recently.
I added a new gulp task

gulp.task('installTypings', function() {
  let gulpTypings = require('gulp-typings');
  return gulp.src('./typings.json')
    .pipe(gulpTypings());
});

and changed my postinstall in package.json to
"postinstall": "gulp installTypings"


Erroneous Polygon Object collision with Edges

My student is creating a game in which a shape falls along a path dictated by a line the player creates by clicking. It works really well with circles but with triangles he encountered this glitch. This is a low priority error since he'll just have the player directed object stay a circle but I thought you guys should be aware of it. Here is a video for reference:
https://user-images.githubusercontent.com/20031683/179632484-743d5423-2ed7-4c68-bc69-29acb6ec8493.mov

@quinton-ashley Could you please provide some code to reproduce this issue?
Here is an example that works for me: https://piqnt.com/space/dRNv2YJWf

That was a video the student sent so I don't have the code, and now it's been a while so I don't remember who it was. I just wanted to pass along the error report. I can try making a demo of the problem though.

I see, makes sense. I will close it for now, please feel free to reopen if you are able to reproduce the issue. Thanks!


Missing word in documentation

2.5. Select the type of collector you're using and enter the relevant details. If you're using the Cloudfront collector you will need to enter the Cloudfront subdomain. If you're using the Clojure collector (or any other collector) you will need to enter the or the endpoint collector URL.
"enter the ???"

For the sake of clarity, the page being referenced is this. @fblundun could you suggest what was meant here?

I think it should just read "enter the endpoint collector URL" (i.e. that's the only thing you can enter).

Updated locally

Done by @ihortom !


ovftool: init at 4.4.1

Motivation for this change
Adding VMWare's proprietary ovftool (c.f. https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=vmware-ovftool), which has a weird self-extracting installer on i686-linux and x86_64-linux that requires a FHS env to run.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 107599 run on x86_64-linux 1

@SuperSandro2000 It currently uses requireFile since ovftool is from VMWare's website and requires a (free) account to download... if I can find a mirror that we can actually use I'll replace it

It also currently requires the (insecure) openssl_1_0_2, because ovftool depends on pre-1.1 OpenSSL

So, I at least tried forcing ovftool to use openssl 1.1 and trying to get it to sign a .ova file. It seems to specifically want to use 1.0.2 rather than 1.1. strace shows it looking for 1.0.2 - since our OpenSSL 1.0.2 is named 1.0.0, symlinking that into lib seemed to satisfy it. But lying it to it and symlinking 1.1 as 1.0.2 makes it look elsewhere and eventually give up/abort.
This gives us a couple options if we don't want to add new dependencies on insecure libraries:

Use VMWare's OpenSSL. VMWare bundles an OpenSSL 1.0.2 .so with ovftool, but I deliberately didn't copy it into $out because we can provide one ourselves. It seemed better to warn users of using an old OpenSSL version by forcing them to use NIXPKGS_ALLOW_INSECURE or similar.
Maybe try openssl-compat? Do we have any other packages that need to do this?

Result of nixpkgs-review pr 107599 run on x86_64-linux 1

1 package marked as broken and skipped:

ovftool

@numinit still not able to test it as it is marked as broken

This is because openssl_1_0_2 is insecure. If you allow insecure packages it will build.

@numinit still not able to test it as it is marked as broken

This is because openssl_1_0_2 is insecure. If you allow insecure packages it will build.

Comments addressed.

Comments addressed.

Added ovftoolBundles param to facilitate use of the package with callPackage + VMWare .bundle file.

Added ovftoolBundles param to facilitate use of the package with callPackage + VMWare .bundle file.

Any chance of seeing this merged for 21.05?

@ofborg eval

@GrahamcOfBorg eval

Changes addressed.


[IMPROVEMENT] Improving Longhorn-Manager's Metric Collection: Alternatives to Metrics Server

Is your improvement request related to a feature? Please describe (👍 if you like this request)
Hello
I would like to ask about the implementation of the metric_collector in longhorn-manager (https://github.com/longhorn/longhorn-manager/tree/master/metrics_collector).
The metric_collector currently fetches kubelet metrics collected by the metrics server via the kube-api. While this is convenient, it seems to have two main drawbacks:

Increased load on the kube-api when the number of nodes scales up.
The requirement to always deploy the metrics server.

Describe the solution you'd like
I am wondering if there are any plans to change the structure of longhorn-manager to collect metrics directly from kubelets. However, this approach may have the issue of needing to obtain the kubelet token.
Lastly, if neither method is ideal, I think it would be beneficial to add a feature to disable metric collection. I would appreciate any feedback on this.
Thank you.

add a feature to disable metric collection.

The request sounds fair. WDYT? @longhorn/dev @innobead

I'll reopen this issue when I find a good solution.
Thanks for looking into this


How to use as scaled decimal number (1.x)

When I try to use this code below, the complier error occurred when std::cout.
using DecX = cnl::scaled_integer<cnl::rounding_integer<long long>, cnl::power<-1, 100>>;
DecX num1 = 10.554;
DecX num2 = 10.545;
std::cout<<num1<<" "<<num2<<std::endl;

Clang 12 with libstdc++ and  c++ 17
In file included from ../third/cnl-1.1.7/include/cnl/_impl/scaled_integer/extras.h:22:
../third/cnl-1.1.7/include/cnl/_impl/scaled_integer/to_chars.h:52:24: error: no matching function for call to 'scale'
                return scale<Exponent, Radix>(to_rep(scalar));
                       ^~~~~~~~~~~~~~~~~~~~~~
../third/cnl-1.1.7/include/cnl/_impl/scaled_integer/to_chars.h:66:48: note: in instantiation of member function 'cnl::_impl::split<cnl::_impl::number<long long, cnl::native_rounding_tag>, -1, 100, false>::integral' requested here
                return from_integral_and_value(integral(value), value);
                                               ^
../third/cnl-1.1.7/include/cnl/_impl/scaled_integer/to_chars.h:207:32: note: in instantiation of member function 'cnl::_impl::split<cnl::_impl::number<long long, cnl::native_rounding_tag>, -1, 100, false>::operator()' requested here
            auto const split = _impl::split<Rep, Exponent, Radix>{}(value);
                               ^
../third/cnl-1.1.7/include/cnl/_impl/scaled_integer/../to_chars.h:88:28: note: in instantiation of function template specialization 'cnl::_impl::to_chars_positive<cnl::_impl::number<long long, cnl::native_rounding_tag>, -1, 100>' requested here
                    return to_chars_positive(first, last, value);
                           ^
../third/cnl-1.1.7/include/cnl/_impl/scaled_integer/to_chars.h:242:16: note: in instantiation of member function 'cnl::_impl::to_chars_non_zero<cnl::scaled_integer<cnl::_impl::number<long long, cnl::native_rounding_tag>, cnl::power<-1, 100>>, true>::operator()' requested here
        return _impl::to_chars_non_zero<native_rounding_type>{}(
               ^
../third/cnl-1.1.7/include/cnl/_impl/scaled_integer/../to_chars.h:120:23: note: in instantiation of function template specialization 'cnl::to_chars<cnl::_impl::number<long long, cnl::nearest_rounding_tag>, -1, 100>' requested here
        auto result = to_chars(chars.data(), chars.data()+max_num_chars, value);
                      ^
../third/cnl-1.1.7/include/cnl/_impl/scaled_integer/extras.h:210:23: note: in instantiation of function template specialization 'cnl::to_chars<cnl::scaled_integer<cnl::_impl::number<long long, cnl::nearest_rounding_tag>, cnl::power<-1, 100>>>' requested here
        return out << to_chars(fp).data();
                      ^
../study/try_cnl.cpp:43:9: note: in instantiation of function template specialization 'cnl::operator<<<cnl::_impl::number<long long, cnl::nearest_rounding_tag>, -1, 100>' requested here
    cout<<num1<<" "<<num2<<endl;
        ^
../third/cnl-1.1.7/include/cnl/_impl/number/../num_traits/scale.h:52:38: note: candidate template ignored: substitution failure [with Digits = -1, Radix = 100, S = cnl::_impl::number<long long, cnl::native_rounding_tag>]: implicit instantiation of undefined template 'cnl::scale<-1, 100, cnl::_impl::number<long long, cnl::native_rounding_tag>>'
        [[nodiscard]] constexpr auto scale(S const& s)
                                     ^
1 warning and 2 errors generated.

Then I check the source code at: cnl/rounding_integer.h:63
I am confusing that why can't be default_scale<(Digits < 0), (Radix != 2)>?
(tag v1.7, also v1.x branch currently)
https://github.com/johnmcfarlane/cnl/blob/2dde6e62e608a4adc3c5504f067575efa4910568/include/cnl/rounding_integer.h#L57-L73

Hi. Thanks for filing this issue. It has since been addressed in the latest version:
1.x: https://godbolt.org/z/1Y53M5Knj
2.x: https://godbolt.org/z/exxafsKjx
Is it possible for you to upgrade?

I am confusing that why can't be default_scale<(Digits < 0), (Radix != 2)>?

The specialisation that was provided in v1 is likely to be using a bit shift operation and so only works for the binary base.

Hi. Thanks for filing this issue. It has since been addressed in the latest version:
1.x: https://godbolt.org/z/1Y53M5Knj
2.x: https://godbolt.org/z/exxafsKjx
Is it possible for you to upgrade?

I am confusing that why can't be default_scale<(Digits < 0), (Radix != 2)>?

The specialisation that was provided in v1 is likely to be using a bit shift operation and so only works for the binary base.

Still in v1 since the C++17 we used.
I try to add these code in cnl/_impl/num_traits/scale.h
( https://github.com/johnmcfarlane/cnl/blob/v1.x/include/cnl/_impl/num_traits/scale.h#L48 )
And then the problem solved.
namespace cnl {
    template<int Digits, int Radix, template<typename, typename> class TNUM, typename S, typename Tag>
    struct scale<Digits, Radix, TNUM<S, Tag>, _impl::enable_if_t<(
        Digits<0 && cnl::_impl::is_integral<S>::value)>>
    {
        CNL_NODISCARD constexpr auto operator()(TNUM<S, Tag> const& s) const
        -> decltype(s/_impl::power_value<S, -Digits, Radix>())
        {
            return s/_impl::power_value<S, -Digits, Radix>();
        }
    };
}

Could you please help me to review these code?

Is that a right change?
Any other improvement suggestion?

Hi. Thanks for the feedback and suggestion. I should be able to take a look at it later today.
The great thing about DVCS and CI is that you can safely break things without causing harm or disruption to others. So while I'm happy to help, you don't have to wait.

fork the project under your own user account,
See whether GitHub Actions runs and builds the project for you (it may not or there may have been degradations in the build system over the past few months; I'm not sure),
make a branch off of v1.x,
add a test which fails - it doesn't have to be perfect or ready for merging but shows the problem,
apply the change,
push the branch to GitHub,
see whether the fix prevents the test from failing.

CI for v1.x is not currently working, likely due to updates to the docker images used to build the project. I'll need to fix the v1.x branch first.

Test case pushed and confirmed.
Fix pushed but breaking.
@vrqq did you add the specialisation of cnl::scale or did you replace an existing specialisation?

After one years I retry to fix this issue, and there still some bug I cannot fixed. (I made a pull request into 991 branch it into branch)
The code previous I posted, was break the coding style of template partial specialization. For the third argument, I should keep it fixed on the special type, instead of using template<typename, typename> to match any _impl::number type.
After reading the code in project, I found out the design-rule of struct scale. The third argument class Rep should be specialized in different files, such as rouding_integer.h
So It may more suitable to move into https://github.com/johnmcfarlane/cnl/blob/991/include/cnl/rounding_integer.h#L74
There's some problem on test like std::hash<path> in cppcon2017.cpp. In the code below, there still have problem on GCC and Clang compiler.
https://github.com/johnmcfarlane/cnl/blob/main/test/unit/presentations/cppcon2017.cpp#L23
And conan in pip has been updated into 2.0, but a lot of package hasn't upgraded in there repo.


base64/hex utils

We implemented helpers that are similar to libsodium.js helpers. Eventually, those should be probably used instead of platform-specific base64 tools for input/output.

Thank you for your PR.
Can you please explain in more detail, some concrete use cases of these utility functions as they are not related to sodium library.


Groovy DSL test hard to make work on Quarkus Platform

The test can currently be characterized as follows:

The execution is moved to integration test phase
It relies on the existence of the runner artifact under target directory
The path to the runner is passed from pom.xml to the test via property

All of these are quite against how the tests in Quarkus Platform are set up:

Native tests are not executed and thus their CI is only reaching Maven test phase. This was discussed several times and the general agreement was that this should change, but it has not changed yet. Hence point 1. may get solved at some point by the Platform team.
Running mvn package in the generated test module directory generated-platform-project/quarkus-camel/integration-tests/camel-quarkus-integration-test-groovy-dsl does not produce any jars under target. Maybe quarkus-maven-plugin is not set up. It needs to be investigated.
Setting the quarkus.runner property (and moving surefire to integration-test) can be done by this piece of XSL added to src/main/resources/xslt/camel/test-pom.xsl in the Platform source tree:

    <!-- camel-quarkus-integration-test-groovy-dsl requires to move surefire:test to integration-test phase -->
    <!-- to be able to run java -jar target/*runner.jar from a test -->
    <xsl:template match="/pom:project/pom:build/pom:plugins/pom:plugin[(pom:artifactId/text() = 'maven-surefire-plugin') and (/pom:project/pom:artifactId/text() = 'camel-quarkus-integration-test-groovy-dsl')]">
        <xsl:copy>
            <xsl:apply-templates select="@* | node()" />
            <executions>
                <execution>
                    <id>default-test</id>
                    <goals>
                        <goal>test</goal>
                    </goals>
                    <phase>integration-test</phase>
                    <configuration>
                        <systemProperties>
                            <quarkus.runner>${project.build.directory}/quarkus-app/quarkus-run.jar</quarkus.runner>
                        </systemProperties>
                    </configuration>
                </execution>
            </executions>
        </xsl:copy>
    </xsl:template>

Instead on pushing on any of the above, I'll remove camel-quarkus-integration-test-groovy-dsl from the test list we publish for the platform for now.
@essobedo I wonder whether the classloading issue because of which we have this special setup cannot be fixed in Quarkus or elsewhere? If it can be fixed, we would not need to bother with any special measures to make the test work in the Platform.

could you please also share the link to the failing build

I am doing it locally so far. IIRC, there is no CQ release with the new Groovy DSL tests, so I cannot prepare a PR for the Plaform where it would be visible.
This would be the steps to do it locally:
cd camel-quarkus
mvnd clean install -DskipTests -Dquarkus.build.skip # -Dquickly is not enough to build test-jars

cd ..
git clone git@github.com:quarkusio/quarkus-platform.git
cd quarkus-platform

# in the top pom.xml change <camel-quarkus.version> to your local snapshot
# then regenerate the boms and test modules
./mvnw install -DskipTests # this dowloads the internet

# review the generate groovy DSL module
cd generated-platform-project/quarkus-camel/integration-tests/camel-quarkus-integration-test-groovy-dsl
mvn verify # will fail for the reasons sketched above


Passing Parameters via M.me Links supported

2 separate patches which introduce support for Existing User Scenario and First-Time Use Scenario correspondingly.
The patches also include relevant tests.

Coverage increased (+0.1%) to 90.632% when pulling 739c2efb1aa83357115e175ef2b1718a0b532ca6 on anton-nayshtut:master into dced88dddf8f5bdc7b7cdfa8af500a62b4a92440 on conbus:master.

thanks merged.


can't duplicate

VSCode Version: 1.7.1 (1.7.1)
OS Version: macOS Sierra 10.12.2

well i can't duplicate so it's not for me, i'll be back in case you add this function...

What you don't can duplicate? What are you talking about?

Are you saying split window?

nova-tmtheme

I do not understand what you mean by not duplicate nova-tmtheme. Please provide what exactly the  issue / feature you are looking for. Thanks.


How to get RunMetadata for tf.data.Dataset ops?

Tensorflow version: 1.5 (pip)
I am interested in the runtime of ops when using the tf.data.Dataset api.
Information like how long shuffle, repeat or batch took.
When running the code below and visualizing it in tensoboard the intersting ops are marked as "unused substructure".
Is my approach the right one?
I find it a little confusing that they show up, but are not traceable.
Example code
import numpy as np
import tensorflow as tf

tf.set_random_seed(0)

data = np.array([[10] * 10] * 3 + [[4] * 10]).astype(np.float32)

with tf.Graph().as_default():
  dataset = tf.data.Dataset.from_tensor_slices(data)
  sess = tf.Session()

  dataset = dataset.cache()
  dataset = dataset.shuffle(10, seed=0)
  dataset = dataset.repeat(5)
  dataset = dataset.batch(2)

  iterator = tf.data.Iterator.from_structure(
      output_types=tf.float32)
  batch = iterator.get_next()

  init1 = iterator.make_initializer(dataset)

  sess.run(init1)

  writer = tf.summary.FileWriter('tmp/datasettest/', sess.graph)
  run_options = tf.RunOptions(trace_level=tf.RunOptions.FULL_TRACE)

  i = 0
  while True:
    try:
      run_metadata = tf.RunMetadata()
      sess.run(batch, options=run_options, run_metadata=run_metadata)
      writer.add_run_metadata(run_metadata, 'step{}'.format(i))
      i += 1
    except tf.errors.OutOfRangeError as ex:
      break
    except Exception as ex:
      raise ex

This will result in the following visualization in Tensorboard.

There's no way to do that right now. The tf.RunMetadata interface isn't ideal for capturing this kind of information, because a Dataset transformation might contribute to 0, 1, or multiple different runs, and it may happen asynchronously with any of them. The transformations produce events for a tracing interface that captures fine-grained execution information, but this interface is currently unimplemented.

Assigning to @mrry for implementing the tracing_impl.h interface.

I doubt I will work on this in the near future.

You seem to be using older version(1.x) of Tensorflow which is not supported anymore. Please try the latest Tensorflow version and let us know if the problem still persists.
Also, refer the tf.data API in Tensorflow 2.x version. Thanks!