aws-c-http: 0.6.15 -> 0.6.20

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/aws-c-http/versions.
meta.description for aws-c-http is: "C99 implementation of the HTTP/1.1 and HTTP/2 specifications"
meta.homepage for aws-c-http is: "https://github.com/awslabs/aws-c-http"
meta.changelog for aws-c-http is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.6.19 with grep in /nix/store/mk84y0k8fjmqd0i4lb4n1r5q2hmyba5m-aws-c-http-0.6.19
found 0.6.19 in filename of file in /nix/store/mk84y0k8fjmqd0i4lb4n1r5q2hmyba5m-aws-c-http-0.6.19

Rebuild report (if merged into master) (click to expand)

271 total rebuild path(s)

271 package rebuild(s)

First fifty rebuilds by attrpath
appvm
arrow-cpp
arrow-glib
aws-c-auth
aws-c-http
aws-c-mqtt
aws-c-s3
aws-crt-cpp
aws-sdk-cpp
bundix
cabal2nix
cached-nix-shell
cachix
colmena
comma
common-updater-scripts
crate2nix
crystal2nix
dep2nix
dydisnix
fusionInventory
gnome.gnome-packagekit
gnome.gnome-software
gnome.simple-scan
go2nix
haskellPackages.cabal2nix-unstable
haskellPackages.cachix
haskellPackages.hercules-ci-agent
haskellPackages.hercules-ci-cli
haskellPackages.hercules-ci-cnix-expr
haskellPackages.hercules-ci-cnix-store
haskellPackages.nix-paths
haskellPackages.nvfetcher
haskellPackages.update-nix-fetchgit
hci
hercules-ci-agent
home-assistant-component-tests.environment_canada
home-manager
hydra_unstable
intensity-normalization
libnixxml
libsForQt5.discover
libsForQt5.packagekit-qt
libsForQt512.discover
libsForQt512.packagekit-qt
libsForQt514.discover
libsForQt514.packagekit-qt
libsForQt515.discover
libsForQt515.packagekit-qt
lispPackages.quicklisp-to-nix

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mk84y0k8fjmqd0i4lb4n1r5q2hmyba5m-aws-c-http-0.6.19 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A aws-c-http https://github.com/r-ryantm/nixpkgs/archive/a41646ca1821e966ef4005cd92d93bb1442dc78d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mk84y0k8fjmqd0i4lb4n1r5q2hmyba5m-aws-c-http-0.6.19
ls -la /nix/store/mk84y0k8fjmqd0i4lb4n1r5q2hmyba5m-aws-c-http-0.6.19/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @r-burns for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/aws-c-http/versions.
meta.description for aws-c-http is: "C99 implementation of the HTTP/1.1 and HTTP/2 specifications"
meta.homepage for aws-c-http is: "https://github.com/awslabs/aws-c-http"
meta.changelog for aws-c-http is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.6.20 with grep in /nix/store/3db94zcpc9ry3qpwj3j4mb7jn3d7f3s0-aws-c-http-0.6.20
found 0.6.20 in filename of file in /nix/store/3db94zcpc9ry3qpwj3j4mb7jn3d7f3s0-aws-c-http-0.6.20

Rebuild report (if merged into master) (click to expand)

273 total rebuild path(s)

273 package rebuild(s)

First fifty rebuilds by attrpath
appvm
arrow-cpp
arrow-glib
aws-c-auth
aws-c-http
aws-c-mqtt
aws-c-s3
aws-crt-cpp
aws-sdk-cpp
bundix
cabal2nix
cached-nix-shell
cachix
colmena
comma
common-updater-scripts
crate2nix
crystal2nix
dep2nix
dydisnix
fusionInventory
gnome.gnome-packagekit
gnome.gnome-software
gnome.simple-scan
go2nix
haskellPackages.cabal2nix-unstable
haskellPackages.cachix
haskellPackages.hercules-ci-agent
haskellPackages.hercules-ci-cli
haskellPackages.hercules-ci-cnix-expr
haskellPackages.hercules-ci-cnix-store
haskellPackages.nix-paths
haskellPackages.nvfetcher
haskellPackages.update-nix-fetchgit
hci
hercules-ci-agent
home-assistant-component-tests.environment_canada
home-manager
hydra_unstable
intensity-normalization
libnixxml
libsForQt5.discover
libsForQt5.packagekit-qt
libsForQt512.discover
libsForQt512.packagekit-qt
libsForQt514.discover
libsForQt514.packagekit-qt
libsForQt515.discover
libsForQt515.packagekit-qt
lispPackages.quicklisp-to-nix

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3db94zcpc9ry3qpwj3j4mb7jn3d7f3s0-aws-c-http-0.6.20 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A aws-c-http https://github.com/r-ryantm/nixpkgs/archive/c9f960e5962a186d6a5de7c34892eda80dfad866.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3db94zcpc9ry3qpwj3j4mb7jn3d7f3s0-aws-c-http-0.6.20
ls -la /nix/store/3db94zcpc9ry3qpwj3j4mb7jn3d7f3s0-aws-c-http-0.6.20/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @r-burns for testing.


Update Composer dependencies (2021-10-15-00-16)

Visual regression test passed!
View the visual regression test report


Clicking a nav link reloads/jumps around the page

Re. Georgia's comment in a PR:

when you click on a menu option, there's a reload/jump that happens that is a bit jarring and the position on the menu doesn't persist to the page loading. Is there anything we can do about that? That seems like a bigger feature/need around maintaining state on load, but also I would think that was a standard feature from the theme?

And Saptak's reply

That is not part of the template. It can definitely be fixed, but needs a localStorage to store the scroll position persistently. I will play around with it in a separate PR.

Can I get assigned? let me know how to start

Can I get assigned? let me know how to start

If you have some ideas on how to do this then absolutely open up a PR and It'll get reviewed :)


createActionType should be using payload

It's somewhat confusing that data you pass in action dispatch are merged together with type of the action. I think that those data should go to payload property instead. This is especially important when my TcombType actually has it's own type property denoting something else. In that case it would fail with this:
TypeError: [tcomb] Invalid call to mixin(target, source, [overwrite]): cannot overwrite property "type" of target object

I think that those data should go to payload property instead

What if you define flux standard actions? You need more than a payload property. The shape of an action should be freely defined by the user, not imposed by this library

Well, the payload is part of FSA, it's optional, but definitely not something that would be against that standard. I kinda like this part of standard rather then mixed values and unable to use simple type property.
You certainly agree that error popping there is not good thing. Perhaps it could be optional behavior you can specify for createActionType call? Something like createActionType(actions, { usePayload: true }).
If I would have to specify payload for each of my action, it suddenly becomes very verbose to define those actions and createActionType kinda loses part of its magic brilliance.

I meant: the general shape of an FSA is
type FSA = {
  type: string,
  payload?: any,
  error?: boolean,
  meta?: any
};

so this library can't assume a single payload property.
Some users might not follow FSA and probably they want to define their actions without restrictions.
Also, it pretty easy to define a wrapper of creatwActions with your own logic

So you mean like iterating over those actions and wrap everything into t.interface({ payload: type })? I guess that could be a way, but feels rather dirty with too much wrapping for my taste.
I don't understand why it cannot be optional behavior to use payload, but I think I will just copy&paste the createActionType and modify for my needs. It's not that big to be a problem.


Scala Toolchains: Configure -target compiler flag

Partially addresses https://github.com/gradle/gradle/issues/18211
When using scala plugin and configuring toolchain to specify JDK to use, the Scala plugin does not configure the targetCompatibility under the hood. The -target compiler flag is missing.
There are cases where even using a newer JDK but compiling to the default in an older version of scala (for example 2.10.x), results in bytecode for JVM 1.6. This is ok until you try to use modern language features. Unfortunately, folks see this happening sometimes transitively when using an interface from a 3rd party module that was written in java and contains static and/or default methods (for example).
This change is to configure -target in scalaCompileOptions.additionalParameters automatically without user interaction when they leverage Toolchains. After some discussion with @ljacomet , we agreed that doing this change regardless if you use toolchains or not could be a breaking change and not suitable for 7.x releases.
Few important bits here:

This does not configure the targetCompatibility when using scala 3, it only detects scala-library version which includes 2.10.x, 2.11.x, 2.12.x and 2.13.x

When scala version is older than 2.13.1, it creates a flag like "-target:jvm-1.8". Otherwise, it will set something like -target:17. Went this route as I noticed the scalac command has the following for such versions Target platform for object files. All JVM 1.5 - 1.7 targets are deprecated. (jvm-1.5,jvm-1.6,jvm-1.7,[jvm-1.8]) . Starting on 2.13.1, it started supporting newer versions (-target:<target>             Target platform for object files. ([8],9,10,11,12))

Gradle tool is not responsible for understanding if the version of Scala selected is compatible with the toolchain. While this implementation makes the best guest to compile to JDK 8 when using modern JDKs and old versions of Scala, there are cases where patch releases added support to new JDKs, for example, Scala 2.13.4 supports Target platform for object files. ([8],9,10,11,12) while Scala 2.13.5 supports Target platform for object files. ([8],9,10,11,12,13,14,15,16,17).

Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[x] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[x] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[x] Ensure that tests pass sanity check: ./gradlew sanityCheck
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

OK, I've already triggered a build for you.


Internal Links are Broken and throw an error.

Unhandled Runtime Error when clicking an internal link.

To Reproduce
See video: https://www.loom.com/share/9eb8d52554df44fe8e70c73a814b259c
https://www.truework.com/docs-2/ZG9jOjE0OTA1NTk-introduction Live
https://stoplight.truework.com/docs/truework/ZG9jOjE0OTA1NTk-introduction Stoplight Hosted
Unhandled Runtime Error
TypeError: Cannot read properties of undefined (reading 'pathname')

Call Stack
createPath
node_modules/history/esm/history.js (47:0)
navigate
node_modules/react-router-dom/esm/react-router-dom.js (188:79)
onClick
node_modules/react-router-dom/esm/react-router-dom.js (145:0)
HTMLUnknownElement.callCallback
node_modules/react-dom/cjs/react-dom.development.js (188:0)
Object.invokeGuardedCallbackDev
node_modules/react-dom/cjs/react-dom.development.js (237:0)
invokeGuardedCallback
node_modules/react-dom/cjs/react-dom.development.js (292:0)
invokeGuardedCallbackAndCatchFirstError
node_modules/react-dom/cjs/react-dom.development.js (306:0)
executeDispatch
node_modules/react-dom/cjs/react-dom.development.js (389:0)
executeDispatchesInOrder
node_modules/react-dom/cjs/react-dom.development.js (414:0)
executeDispatchesAndRelease
node_modules/react-dom/cjs/react-dom.development.js (3278:0)
executeDispatchesAndReleaseTopLevel
node_modules/react-dom/cjs/react-dom.development.js (3287:0)
forEachAccumulated
node_modules/react-dom/cjs/react-dom.development.js (3259:0)
runEventsInBatch
node_modules/react-dom/cjs/react-dom.development.js (3304:0)
runExtractedPluginEventsInBatch
node_modules/react-dom/cjs/react-dom.development.js (3514:0)
handleTopLevel
node_modules/react-dom/cjs/react-dom.development.js (3558:0)
batchedEventUpdates$1
node_modules/react-dom/cjs/react-dom.development.js (21871:0)
batchedEventUpdates
node_modules/react-dom/cjs/react-dom.development.js (795:0)
dispatchEventForLegacyPluginEventSystem
node_modules/react-dom/cjs/react-dom.development.js (3568:0)
attemptToDispatchEvent
node_modules/react-dom/cjs/react-dom.development.js (4267:0)
dispatchEvent
node_modules/react-dom/cjs/react-dom.development.js (4189:0)
unstable_runWithPriority
node_modules/scheduler/cjs/scheduler.development.js (653:0)
runWithPriority$1
node_modules/react-dom/cjs/react-dom.development.js (11039:0)
discreteUpdates$1
node_modules/react-dom/cjs/react-dom.development.js (21887:0)
discreteUpdates
node_modules/react-dom/cjs/react-dom.development.js (806:0)
dispatchDiscreteEvent
node_modules/react-dom/cjs/react-dom.development.js (4168:0)

gz#7708(related to Zendesk ticket #7708)

@wmhilton

Issue occurs when using ngrok also.
Here's the code of the page that loads it.
import { StoplightProject } from '@stoplight/elements-dev-portal'
import<EMAIL_ADDRESS>import { Box } from '@hypobox/react'

import { hypostyle } from '@/hypostyle'
import * as routes from '@/utils/routes'

import { Footer } from '@/components/Footer'
import { Head } from '@/components/Head'
import { Logo } from '@/components/Logo'
import { Button } from '@/components/Button'

import og from<EMAIL_ADDRESS>
export const BASE_TITLE = `Docs @ Truework`

function formatTitle (pageTitle) {
  return pageTitle ? `${pageTitle} | ${BASE_TITLE}` : BASE_TITLE
}

hypostyle.injectGlobal(theme => ({
  '.sl-elements': {
    color: 'body',
    minHeight: '100vh',
    '*, ::after, ::before': {
      borderColor: 'outline',
      ff: 'sans'
    },
    '.sl-h-full': {
      minHeight: '100vh'
    },
    '.sl-bg-canvas-100': {
      backgroundColor: 'background'
    },
    '.sl-inverted': {
      '.sl-bg-canvas-100': {
        backgroundColor: 'rgba(26, 38, 73, 0.9)'
      },
      '.sl-bg-canvas-200': {
        backgroundColor: 'bodyDark'
      }
    },
    '.sl-bg-primary-tint': {
      backgroundColor: 'white',
      '> div': {
        color: `${theme.tokens.color.primary} !important`
      }
    },
    '.sl-prose': {
      p: {
        color: 'secondary'
      },
      'caption a, figcaption a, li a, p a, table a': {
        color: 'primary',
        textDecoration: 'none',
        '&:focus, &:hover': {
          textDecoration: 'underline'
        }
      }
    },
    // sidebar/content parent
    '.sl-elements-api': {
      flexWrap: { 0: 'wrap', 2: 'no-wrap' },
      // sidebar
      '> div:first-child': {
        width: { 0: '100% !important', 2: 'calc(50% - 600px) !important' },
        position: 'relative',
        pt: 4,
        boxShadow: 'medium',
        zIndex: 1
      },
      // content
      '> div:last-child': {
        px: { 0: '16px !important', 2: '48px !important', 3: '96px !important' }
      }
    }
  }
}))

export function Docs () {
  React.useLayoutEffect(() => {
    let prev = window.location.href

    setInterval(() => {
      const parent = document.querySelector('.sl-elements')
      const h1s = parent ? parent.getElementsByTagName('h1') : undefined
      const h1 = h1s ? [].slice.call(h1s)[0] : undefined
      const title = h1 ? h1.textContent : undefined

      if (window.location.href !== prev || !document.title.includes(title)) {
        prev = window.location.href
        document.title = formatTitle(title)
      }
    }, 100)
  }, [])

  return (
    <>
      <Box
        f
        aic
        jcb
        py={4}
        pl='calc(50% - 900px)'
        pr={4}
        bg='white'
        boxShadow='medium'
        rel
        zIndex={2}
      >
        <Box as='a' href='/docs' pl={4}>
          <Logo />
        </Box>

        <Button as='a' href='/' appearance='secondary' size='small'>
          Main Site
        </Button>
      </Box>

      <div key='root'>
        {typeof window !== 'undefined' ? (
          <StoplightProject
            platformUrl='https://stoplight.io'
            projectId='cHJqOjkxNTky'
            basePath='/docs-2'
            router={'history'}
          />
        ) : null}
      </div>

      <Box height='1px' bg='outline' />

      <Footer />
    </>
  )
}

export default function Page (props) {
  return (
    <>
      <Head
        canonical={routes.base + '/docs'}
        title={BASE_TITLE}
        description='Truework makes it easy to verify income and employment for any US employee.'
        image={og}
      />

      <Docs />
    </>
  )
}

I think I may have found the issue 🤔  unsure if fixing this would cause other issues downstream though
The ReactRouterMarkdownLink component accepts { href }, not { to }. It's passed to the NodeContent provider, which provides it to the LinkComponent which tries to pass in href instead of to.
Curious what the team's thoughts are on that 👍

I also noticed that markdown links populated as relative paths must not have been matching the edge.uri check here because it was rendering a raw <a> tag.
E.g. a link like docs/api/intro.md would fail that check and render a native anchor tag, whereas /docs/api/intro.md would match, and render the broken ReactRouterMarkdownLink. Some issue with stoplightio/path resolution maybe?

Maybe https://github.com/stoplightio/elements/pull/1984 will fix it?

Thanks @fsargent ! It appears internal links are only broken on some docs, not all (😬), but it is on our radar!

@wmhilton Any indication of what the common factor is? This is a critical issue for us and is stopping our migration to Stoplight.

@wmhilton I understand what you're trying to say but right now our docs site has a huge red error on it, and then the rest of the relative links don't work.
Is there more than we can do than having it on the radar?

@marbemac Wondering if you could put some eyes on this issue.

@fsargent can you try out this fix? From my testing its working, but I'm investigating why that line was changed in the first place: https://github.com/stoplightio/elements/pull/1989

@lottamus Thank you! This looks like it should work. How can I pull it before the release is out? Or I can just wait and will test when released.


AgmCircle dragStart event not working

Issue description
AgmCircle dragStart event not working
Steps to reproduce and a minimal demo of the problem
Create an amg-circle and start draging.
Current behavior
Not fires. Only dragEnd fires
Expected/desired behavior
Should fire
angular2 & angular-google-maps version
Other information

Nice, just close issues, dont solve them! ahahahah

Hey... @vguleaev , there was a minor issue with the events.set('dragStart', this.dragStart); where the event set needs to be all lowercase. I made a pull requested for it https://github.com/SebastianM/angular-google-maps/pull/1618
. If you want to change this in your current project before a new release you can edit it in your<EMAIL_ADDRESS>and change the
events.set('dragStart', this.dragStart);   line 140
to
events.set('dragstart', this.dragStart);

fixed


Fixes typo in README.md.

Replaces erroneous '.get' with '.search'.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Improvements

[x] test
[ ] document

This PR adds some QoL improvements for 3rd party contributors:

[x] We now trim the leading @ in the name+version output so as to not potentially ping an entire team (in the case of our own core monorepo repository the output is<EMAIL_ADDRESS>[x] The ability to change the icon_url (default is our metamask bot which lives in this repo)
[x] Bot name gives the ability to change the name displayed in Slack (again we default to our own such that we can keep our own config succinct)
[x] bot-at adds the ability to ping an user or subgroup of individuals

Moving this out of Draft now as I've completed my testing and this is good for review.
I'll be adding documentation for this stuff shortly and I may tweak the .png slightly. But all code changes should be final now.


fix: Cannot get twitter open graph tags

fix: https://github.com/yungzhu/flutter_link_preview/issues/12

ref:
Bypassing the User-Agent whitelist to receive server-side-rendered (SSR) HTML
https://stackoverflow.com/a/64332370/5588637

hi @WingCH , may i know if you can try on your side with this link https://twitter.com/LFC/status/1432980293904785413?s=20 ? i see "Javascript not found..." error with the link.
and this is how i use your PR, correct me if im wrong. thank you.

i create new PR include null safety, https://github.com/yungzhu/flutter_link_preview/pull/25


REST API implementation Bartek

https://code.tutsplus.com/how-to-build-a-simple-
rest-api-in-php--cms-37000t
Everybody should do this issue! I'm posting it three times and assigning it to everybody.

The changes are as shown on the branch!


Support exporting Rust functions as variadic JS functions

Support the following example
#[wasm_bindgen(apply_ending_slice_bikeshedded)]
pub fn add(first: u32, second: u32, rest: &[u32]) -> u32 {
    rest.iter().sum() + first + second
}

callable from javascript as
import { add } from './wasm';

console.log(add(1, 2, 3, 4, 5)); // prints 15

You could implement the transformation in javascript as
function add(first, second, ..rest) {
    return add_from_rust(first, second, rest);
}

This is a prerequisite for implementing #503 the reverse of #503.

Seems plausible to me! I think though that this is the opposite of #503, right? (this is about defining something in Rust whereas that's about importing something defined in JS)

Yeah I don't know why I said prerequisite :)

@alexcrichton maybe we can close this issue as #2954 has been merged.


Failed to build esp-sdk

Earlier it was working completely fine.
now whenever I build esp-sdk using
'docker build . -f esp-sdk-dockerfile -t esp-sdk'
It says
[INFO ]  Retrieving needed toolchain components' tarballs
[ERROR]
[ERROR]  >>
[ERROR]  >>  Build failed in step 'Retrieving needed toolchain components' tarballs'
[ERROR]  >>        called in step '(top-level)'
[ERROR]  >>
[ERROR]  >>  Error happened in: do_expat_get[scripts/build/companion_libs/210-expat.sh@12]
[ERROR]  >>        called from: do_companion_libs_get[scripts/build/companion_libs.sh@15]
[ERROR]  >>        called from: main[scripts/crosstool-NG.sh@591]
[ERROR]  >>
[ERROR]  >>  For more info on this error, look at the file: 'build.log'
[ERROR]  >>  There is a list of known issues, some with workarounds, in:
[ERROR]  >>      'share/doc/crosstool-ng/crosstool-ng-1.22.0-60-g37b07f6f/B - Known issues.txt'
[ERROR]
[ERROR]  (elapsed: 0:55.27)
[00:55] / make[2]: *** [build] Error 1
#9 75.34 ct-ng:152: recipe for target 'build' failed
#9 75.34 make[2]: Leaving directory '/build/esp-open-sdk/crosstool-NG'
#9 75.34 ../Makefile:135: recipe for target '_toolchain' failed
#9 75.34 make[1]: Leaving directory '/build/esp-open-sdk/crosstool-NG'
#9 75.34 make[1]: *** [_toolchain] Error 2
#9 75.34 Makefile:130: recipe for target 'crosstool-NG/.built' failed
#9 75.34 make: *** [crosstool-NG/.built] Error 2
executor failed running [/bin/sh -c su docker -c "     git clone --recursive https://github.com/pfalcon/esp-open-sdk.git /build/esp-open-sdk ;     cd /build/esp-open-sdk ;     make STANDALONE=n ; "]: exit code: 2
@maximkulkin

I recently had the same problem on Ubuntu.
Problem search resulted the build stopped because expat-2.2.10.tar.xz could not be downloaded. I downloaded it manually and the build was successful, but
Docker seems to be able to borrow a container that has already been created.
https://github.com/pfalcon/esp-open-sdk/issues/237

can you mention the steps to do the same !
@ds5apm

As detailed in the link above, I don't think there is a need to explain further.
As a beginner, the sequence I followed is as follows.
(Details can be found in /esp-open-sdk/crosstool-NG/build.log on your computer.)

Download the file from the address below.
https://master.dl.sourceforge.net/project/expat/expat/2.2.10/expat-2.2.10.tar.xz

Download "expat-2.1.0.tar.gz"
Go to ~/esp-open-sdk/crosstool-NG/.build/tarballs folder.

Then rebuild " ...STANDALONE=n"
I hope my experience will help you solve the problem.

btw the toolchain is looking for expat-2.1.0.tar.gzfile. The url above is targeting to version 2.2.10.

@maximkulkin
Any idea how to solve this while using docker?
get the same errors. but I can't manually edit or download because the image will not be created on error.
Thanks.

@camielverdult Yup, that works look here for more information.


What parameters should I use to change the background color and foreground color of the user name?

What parameters should I use to change the background color and foreground color of the user name?

Hi @Yakumo-Yukari! Check out this page of our wiki:
https://github.com/bhilburn/powerlevel9k/wiki/Stylizing-Your-Prompt#segment-color-customization
If that doesn't fix the issue for you, please re-open and let us know what's wrong!


Maven and travis configuration

@ipa-nhg I had overlooked the xtend files in the roscode generator project, https://github.com/ipa-nhg/ros-model/pull/2/commits/bc814fd24229e32d80b95cbb4cd072c634a3d8ec should fix the build

Maven build and eclipse installer tested and working.
Still missed:

predefine the .launch for "Run ROS tooling"
update documentation

@erogleva the PR is merged, I had to restructure the parent project, otherwise with the source code installation (using the eclipse installer) the projects were imported twice...
Pull from master version before you continue! Thanks!


Added check for hidden files in list comprehension

When invoking os.listdir() on OS X the hidden file ".DS_Store" will be included which breaks the check if there are as many folders as classes.

Can one of the admins verify this patch?

I signed it!

Thanks for catching this.
You've commented some things out in that cell that shouldn't be.
Also, your commit results in a huge diff that's hard to verify (I know that iPython Notebooks are a pain in that way). Can you try to make the diff minimal? I'm also happy to commit it on my end if the diff is only 'if not d.startswith(".")]'

This patch is made obsolete by:
https://github.com/tensorflow/tensorflow/pull/860
Thanks!


fix: check for \n in CodeMirror runmode

Asana Ticket
🧰 What's being changed?
For every language except node, putting in an empty line will cause two empty lines to show up in readOnly mode. This seems to be caused when the if and then else statements are hit on consecutive newline characters
🧪 Testing
change the code string in public/index.js to one of the following:
CURL *hnd = curl_easy_init();\n\ncurl_easy_setopt(hnd, CURLOPT_CUSTOMREQUEST, "GET");\n\ncurl_easy_setopt(hnd, CURLOPT_URL, "http://httpbin.orgpet/");\n\nCURLcode ret = curl_easy_perform(hnd);, 'c'
import requests\n\nurl = "http://httpbin.orgpet/"\n\nresponse = requests.request("HEAD", url)\n\nprint(response.text) , 'python'

@julshotal Can you add a test case for this if possible?

@julshotal Can you add a test case for this if possible?

Added!

@julshotal published to 10.1.1


Adding convolution analysis

Also, I added a visualization function and the stimuli.py.  Sorry the test file isn't the best, try running the plot to see that they're very similar.

Sorry if this is a dumb question, but where are your changes for stimuli.py?

I just threw it into the functions code folder (it wasn't there before)

actually, I guess it is there already?

hmmm... I guess it didn't come along...

yes, great idea though. please add it and make it part of the merge. from now on, whenever someone uses stimuli.py they can refer to that

They're now uploaded as well. I'm ok if this takes some time to look over :)


Try using double.p everywhere

I poked at this today.
Here are some observations:

I'm pretty sure we have a bug in our text layout algorithm (on the C++ side) that's actually the root cause of many of the unexpected line wrapping problems we've been seeing. Specifically, laying out a paragraph at its intrinsic width does not result in the same layout as led to that intrinsic width. https://github.com/flutter/flutter/issues/5852

We would need a .p equivalent of ceil, for those cases where you want to clamp the value to the right bit range but make sure that the new value is not smaller than the incoming value. This is critical in text layout, where we get back a very precise width, and if we ever lay out with a smaller width we'll have line wrapping.

We would definitely need analyzer support to know where we should be calling .p. It's simply impractical to do this by hand. I think at a minimum we would need a new type that the analyzer treats as separate from "double" (even if they're synonyms in the compiler), so that it can tell us when we are about to use a double for layout, or when we are multiplying or dividing values that use this type, and thus need to call .p. I'm not sure even that would necessarily be enough though.

Other than the text issue above which may be a red herring, we don't actually have any current known issues that are affected by this. (The other main issue we had recently got refactored out of existence, and I'm not aware of any other issues currently.)

cc @floitschG

Sounds like we did this. Thanks @Hixie !

@Hixie based on this feedback, I've communicated to @a-siva that we're OK with the VM removing double.p. Please scream if that's not the case.

SGTM, until we fix #5852 we can't really evaluate what we need. double.p was very useful in making me discover that bug, so, there's that at least. :-)


smali 2.1.2

Thanks for the pull request! 🎉 Homebrew depends on contributions from community members like you and we're grateful for your support.
For future reference, this repo has been deprecated. Please send formula related PR to https://github.com/homebrew/homebrew-core


docs: update liquidstaking spec docs

Description

This PR updates spec documents for liquidstaking module.

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Appropriate labels applied
[ ] Targeted PR against correct branch
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

suggestion
05_begin_block.md
Rebalancing (Auto-Redelegation)
Due to the events like slashing, tombstoning, become Inactive...
-> Due to the events like slashing, tombstoning, becoming inactive...

@CoinedLiberty I actually didn't update 05_begin_block.md much, but let me update that with other suggestions. Thanks!


Added support for NotAutomatic, ButAutomaticUpgrades and Origin fields

As a follow up on PR https://github.com/smira/aptly/pull/363 this PR fixes #184.
Description of the Change
The discussion in #363 resulted in that additional fields in Release file are fairly specific and are mainly handled by aptly itself exception being NotAutomatic, ButAutomaticUpgrades and Origin fields. What would be desirable though is to inherit those fields from mirror directly.
So what I implemented in this PR is:

automatically inheriting Origin, NotAutomatic and ButAutomaticUpgrades fields from mirror, in case all snapshots which are being published have the same value of this field.
if a publishes consist of several snapshots with different values of those fields, in case of NotAutomatic and ButAutomaticUpgrades those won't be added (same behaviour as today) and Origin will be generated with prefix and distribution (same behaviour as today)
those 3 flags can always be overwritten during publish with command line flags -origin, -notautomatic, -butautomaticupgrades

Checklist

[x] unit-test added (if change is algorithm)
[x] functional test added/updated (if change is functional)
[x] man page updated (if applicable)
[x] bash completion updated (if applicable)
[x] documentation updated
[x] author name in AUTHORS

Update for documentation: https://github.com/aptly-dev/aptly-dev.github.io/pull/44
dl.bintray.com seems to be a bit flaky today hence some tests failed. I guess best to rerun again at a later point.


Canary Deploment

Typo. "Deployment"
https://glossary.cncf.io/de/canary-deployment/

hello may i work on this issue?
Thank you


New command: "bash-it search  , ...."

Motivation
Given the ever-growing list of plugins, aliases, and completions, it seems that it would be difficult to ensure one uses bash-it to it's fullest.
For example, a Ruby programmer might want to install all plugins, aliases, and completions, related to several commands standard in Ruby development, such as ruby, rake, gem, bundle, etc. To find the list of relevant bash-it components by hand is rather tedious.
Solution
This PR introduces a new command search which is based on a very simple case-insensitive search (using grep) for a list of provided terms in the names and descriptions of all bash-it components, returning a result broken down by type of the component:
For example:

❯  bash-it search ruby rbenv rvm gem rake

    aliases: bundler
    plugins: chruby chruby-auto rbenv ruby rvm
completions: gem rake

Search + Action (Future Proposal)
It seems that a natural, logical step could be introducing the --enable and --disable flags, so that the search results can be instantly acted upon:
NOTE: Proposed functionality:
bash-it search ruby rbenv gem bundler rake --enable`

After this PR is discussed and accepted, it would make sense to continue down this route.
~Konstantin

Hrmm.. I added a very simple test, and it's working in my environment:
/usr/bin/env bash /Users/kig/.bash_it/test/run
1..10
ok 1 lib composure: composure_keywords()
ok 2 helpers search aliases
ok 3 plugins base: ips()
ok 4 # skip (myip is slow - run only with SLOW_TESTS=true) plugins base: myip()
ok 5 plugins base: pickfrom()
ok 6 plugins base: mkcd()
ok 7 plugins base: lsgrep()
ok 8 plugins base: buf()
ok 9 plugins ruby: remove_gem is defined
ok 10 plugins ruby: PATH includes ~/.gem/ruby/bin

Process finished with exit code 0

What could I be doing wrong in that test?

Hmm interesting.  Here is what I am getting on an Ubuntu box:
detached:origin/bash-it-search-command ~/.bash_it >                                                                                11:50:29 > kig
 130 ❯ test/run
 ✓ lib composure: composure_keywords()
 ✓ helpers search aliases
 ✓ plugins base: ips()
 - plugins base: myip() (skipped: myip is slow - run only with SLOW_TESTS=true)
 ✓ plugins base: pickfrom()
 ✗ plugins base: mkcd()
   (from function `teardown' in file test/plugins/../test_helper.bash, line 21,
    from function `bats_teardown_trap' in file bats/libexec/bats-exec-test, line 230,
    from function `main' in test file bats/libexec/bats-exec-test, line 1)
     `#!/usr/bin/env bash' failed
   rm: cannot remove ‘/tmp/.bash_it’: File exists
 ✓ plugins base: lsgrep()
 ✓ plugins base: buf()
 ✓ plugins ruby: remove_gem is defined
 ✓ plugins ruby: PATH includes ~/.gem/ruby/bin

10 tests, 1 failure, 1 skipped

On another Ubuntu node as root, I am getting:
bash-it-search-command  ~/.bash_it 11:53:53 root >
❯ test/run
Cloning into 'bats'...
remote: Counting objects: 61, done.
remote: Compressing objects: 100% (48/48), done.
remote: Total 61 (delta 0), reused 47 (delta 0), pack-reused 0
Unpacking objects: 100% (61/61), done.
Checking connectivity... done.
 ✓ lib composure: composure_keywords()
 ✓ helpers search aliases
 ✗ plugins base: ips()
   (from function `flunk' in file test/plugins/../test_helper.bash, line 35,
    from function `assert_line' in file test/plugins/../test_helper.bash, line 78,
    in test file test/plugins/base.plugin.bats, line 15)
     `assert_line $localhost' failed
   expected line `<IP_ADDRESS>'
 - plugins base: myip() (skipped: myip is slow - run only with SLOW_TESTS=true)
 ✓ plugins base: pickfrom()
 ✗ plugins base: mkcd()
   (from function `teardown' in file test/plugins/../test_helper.bash, line 21,
    from function `bats_teardown_trap' in file bats/libexec/bats-exec-test, line 230,
    from function `main' in test file bats/libexec/bats-exec-test, line 1)
     `#!/usr/bin/env bash' failed
   rm: cannot remove ‘/tmp/.bash_it’: File exists
 ✓ plugins base: lsgrep()
 ✗ plugins base: buf()
   (in test file test/plugins/base.plugin.bats, line 55)
     `[[ -e ${file}_$(date +%Y%m%d_%H%M%S) ]]' failed
 ✓ plugins ruby: remove_gem is defined
 ✓ plugins ruby: PATH includes ~/.gem/ruby/bin

10 tests, 3 failures, 1 skipped

Just for reference, in case you wanted to fix the IPs test, that machine returns three IPs:
 1 ❯ ips
addr:72.2.119.XXX
addr:192.168.YYY.XXX
addr:<IP_ADDRESS>

Anyway, I am going to wrap my test in a check for Darwin. Obviously the test suite is not particularly large, reliable and cross-platform.
Thanks!

Looks good now - one last request, though. Since this has gone through quite a few iterations, would you mind squashing this into a single commit, please?

@nwinkler curious about the reason for requesting these being squashed? I'm personally a fan of the full history so we have all of the variations that were tried.

Just went through and tried this out and checked out all the code -- looks really good! Thanks.

@tswicegood Just a matter of habit, I guess. Most of the other open source projects that I contribute to require people to squash their PRs, in order to keep the history clean.


[Gameplay] Toad's bullets and powerups are hard to see when he's taking damage

Is this intended as part of the difficulty (like the Toad's HP, I assume you tested and realize how high it is)?

Would you accept PRs for keeping it up to date?  I'd even implement some of the aforementioned "lots of things" that you'd do differently.
I'm nearly done with the 11.1 update.
I can tell this is a fun little project for you, and that's awesome.  I just would like to keep the fun going while staying true to the project (which is to say, what you intended, and not necessarily how the project ends up literally translated into newer versions)

I understand, thanks!  :)


catching exceptions in exception handling

When an Exception is thrown while logging that has a non numberic code another exception is thrown while formating the exception. This is for example the case when logging to a database and a PDOException is thrown.
[object] (ErrorException(code: 0): Undefined property: Illuminate\Database\QueryException::$code

$e->getCode is not supposed to throw an exception though. This should be reported to Laravel so that they fix their QueryException.

This is not a laravel problem. It is well known, that the PDOException which the QueryException extends causes this problem.
Look for example in many user comments of the official PHP documentation for the PDOException:
The PDOException class @ php.net
I already tried to handle it in laravels QueryException but it extends PDOException and PDOException::getCode() is final.
There seems to be no known way to handle it in an extended PDOException. All solutions seem to base on the idea of catching the PDOException and raise a custom exception.
This all in mind it seems much more elegant to fix it here instead of everywhere a PDOException might occur.

@Henning256 PDOException::getCode does not throw an exception (and especially not one saying Undefined property).

Thank you stof!
I can not reproduce outside of LineFormater. Very strange.
Closing for further investigation.


Deprecate luci > monitoring page

Most of the luci > monitoring docs have been already migrated to go/flutter-infra-metrics. We need to migrate "Flutter device pool healthiness" to be able to remove luci > monitoring page.

\cc @CaseyHillers @keyonghan

We need to add a link to the landing dashboards console and remove the page.

cl/376265072


Add support for automatically calling unsafe_load() in getproperty()

Copying the description from the code:

By default the getproperty!(x::Ptr, ::Symbol) methods created for wrapped
types will return pointers (Ptr{T}) to the struct fields. That behaviour is
useful for accessing nested struct fields but it does require explicitly
calling unsafe_load() every time. When enabled this option will automatically
call unsafe_load() for you except on nested struct fields and arrays, which
should make explicitly calling unsafe_load() unnecessary in most cases.

Here's the generated code for the struct-properties.h header in the tests:
using CEnum: CEnum, @cenum                                                                                [75/97867]

struct TypedefStruct
    i::Cint
end

struct Other
    i::Cint
end
function _getptr(x::Ptr{Other}, f::Symbol)
    f === :i && return Ptr{Cint}(x + 0)
    error("Unrecognized field of type `Other`" * ": $(f)")
end

function Base.getproperty(x::Ptr{Other}, f::Symbol)
    f === :i && return unsafe_load(_getptr(x, f))
    return getfield(x, f)
end

function Base.setproperty!(x::Ptr{Other}, f::Symbol, v)
    unsafe_store!(_getptr(x, f), v)
end

mutable struct WithFields
    int_value::Cint
    int_ptr::Ptr{Cint}
    struct_value::Other
    struct_ptr::Ptr{Other}
    typedef_struct_value::TypedefStruct
    array::NTuple{2, Cint}
end
function _getptr(x::Ptr{WithFields}, f::Symbol)
    f === :int_value && return Ptr{Cint}(x + 0)
    f === :int_ptr && return Ptr{Ptr{Cint}}(x + 8)
    f === :struct_value && return Ptr{Other}(x + 16)
    f === :struct_ptr && return Ptr{Ptr{Other}}(x + 24)
    f === :typedef_struct_value && return Ptr{TypedefStruct}(x + 32)
    f === :array && return Ptr{NTuple{2, Cint}}(x + 36)
    error("Unrecognized field of type `WithFields`" * ": $(f)")
end

function Base.getproperty(x::Ptr{WithFields}, f::Symbol)
    f === :int_value && return unsafe_load(_getptr(x, f))
    f === :int_ptr && return unsafe_load(_getptr(x, f))
    f === :struct_value && return _getptr(x, f)
    f === :struct_ptr && return unsafe_load(_getptr(x, f))
    f === :typedef_struct_value && return _getptr(x, f)
    f === :array && return _getptr(x, f)
    return getfield(x, f)
end

function Base.setproperty!(x::Ptr{WithFields}, f::Symbol, v)
    unsafe_store!(_getptr(x, f), v)
end

I've also tested it with CImGui.jl: https://github.com/Gnimuc/CImGui.jl/pull/131
I will admit the code is a bit hairy :octopus: Not sure if it's the cleanest implementation.
EDIT: marked as a draft because JET.jl found some issues with it.

The problem JET found was in how bitfields are handled, I believe that's fixed now. My approach was to:

Move the get/set code for bitfields into standalone functions in 129555d.
Have Base.getproperty(x::T, f) and Base.getproperty(x::Ptr{T}, f) both call those functions, so they should both behave the same.

One downside I noticed when playing around with the new wrappers in CImGui is that when we want to write to the struct we really do want to get a pointer instead of unsafe_load()'ing it automatically, e.g.:
# io.ConfigFlags is now a Cint, but we really want a Ptr{Cint}
CImGui.CheckboxFlags("io.ConfigFlags: NavEnableKeyboard", io.ConfigFlags, CImGui.ImGuiConfigFlags_NavEnableKeyboard)

The simple fix there would be to use _getptr(io, :ConfigFlags), but that's rather unsatisfying. So I had an evil thought :stuck_out_tongue: What if we add a third parameter to our Base.getproperty() methods, like Base.getproperty(x::Ptr{T}, f::Symbol, as_ptr::Bool=false), and implement a @ptr macro that turns @ptr foo.bar into Base.getproperty(foo, :bar, true)? Then folks could write e.g. @ptr io.ConfigFlags whenever they want a pointer.
On a side note, turns out that all of our wrappers are fantastically inferrable so JET is very good at finding problems with them :)

There's an example of that in the tests with @test obj_ptr.struct_value.i == obj.struct_value.i. The rule is that the dereferencing only occurs if the field type isn't a struct or array, so if there's a chain of nested structs Base.getproperty() will return a pointer to each of them just like the current behaviour. But if there's a non-struct/array type at the end of the chain, like an int, then that field will be dereferenced and Base.getproperty() on it will return a Cint.

The rule is that the dereferencing only occurs if the field type isn't a struct or array,

I'm pretty sure this gonna confuse newbies, probably LLMs too...

see https://giordano.github.io/blog/2019-05-03-julia-get-pointer-value/ for a hack of dereference operator in Julia.

I'm pretty sure this gonna confuse newbies, probably LLMs too...

I actually think it'll make it easier for newbies since they can blindly access nested properties and always get the right result. A good example of this is something like an ImVec2 field:
struct Foo
    vec::ImVec2
end

Currently to access .x and .y they would need to do:
vec = unsafe_load(obj.vec)
vec.x, vec.y

Whereas with this PR they can simply do obj.vec.x and obj.vec.y. In any case, the feature is off by default so folks will have to explicitly opt in to use it. And I confess I don't care very much about LLM's :stuck_out_tongue:

see https://giordano.github.io/blog/2019-05-03-julia-get-pointer-value/ for a hack of dereference operator in Julia.

That's interesting, but it still makes reading fields harder than writing to them. In my experience fields are read more often than written to, so I think it makes sense to sacrifice some write syntax for the sake of making reads simpler.

hmm... I kinda agree, but if some packages adopt one rule but not the other, there could be a Vim-vs-Emacs war in the future... 😄 however, I don't think that's something we can control. and it's not easy to implement this feature out of the source tree, so it's ok to merge I guess.

If it needs another macro anyway, I would rather integrate auto-dereference in it as well.
I implemented @c macro in https://github.com/Gnimuc/CSyntax.jl to mimic the & operator in C.
Maybe it can be extended to call some particular field access methods generated by Clang.jl. In this way, the field access behavior are kept as-is, and end users get a handy macro.

the main point here is that we can turn @ptr foo.bar into any custom function call, there is not necessary to pirates Base.getproperty.

Yeah @c would actually be perfect :thinking: Unless I'm mistaken, I think we do need to use Base.getproperty() though? The reason is that some code living outside of the bindings has no other way to know which getptr() function to call. For example:
module MyPackage

module lib
include("../bindings.jl")
end

using CSyntax
x() = @c lib.foo().bar

Presumably the field access methods are in lib, but @c has no idea about that so it can't know it has to put in a call to lib.getptr instead of getptr. An alternative would be to define methods of functions defined in either Clang.jl or CSyntax.jl or CEnum.jl, but that would make either package a hard dependency.

Presumably the field access methods are in lib, but @c has no idea about that so it can't know it has to put in a call to lib.getptr instead of getptr. An alternative would be to define methods of functions defined in either Clang.jl or CSyntax.jl or CEnum.jl, but that would make either package a hard dependency.

parentmodule(typeof(Foo())).getptr can do the trick.

julia> module Foo
         struct Bar
            x::Int
         end
         getx(x::Bar) = "x"
         export Bar
       end
Main.Foo

julia> using .Foo

julia> @generated function getxxx(x::T) where {T}
         mod = parentmodule(T)
         :($mod.getx(x))
       end
getxxx (generic function with 1 method)

julia> macro c(x, ex...)
        :(getxxx($(esc(x))))
       end
@c (macro with 1 method)

julia> @c Bar(1)
"x"

Ah, nice :+1: And with luck that'll constant fold away.

I ended up implementing @ptr in the module itself in 89be1a6 because then we can just use @__MODULE__.

Latest codegen
using CEnum: CEnum, @cenum

macro ptr(expr)
    if !isa(expr, Expr) || expr.head != :.
        error("Expression is not a property access")
    end

    quote
        local penultimate_obj = $(esc(expr.args[1]))
        (@__MODULE__).getptr(penultimate_obj, $(esc(expr.args[2])))
    end
end

struct TypedefStruct
    i::Cint
end

struct Other
    i::Cint
end
function getptr(x::Ptr{Other}, f::Symbol)
    f === :i && return Ptr{Cint}(x + 0)
    error("Unrecognized field of type `Other`" * ": $(f)")
end

function Base.getproperty(x::Ptr{Other}, f::Symbol)
    f === :i && return unsafe_load(getptr(x, f))
    return getfield(x, f)
end

function Base.setproperty!(x::Ptr{Other}, f::Symbol, v)
    unsafe_store!(getptr(x, f), v)
end

mutable struct WithFields
    int_value::Cint
    int_ptr::Ptr{Cint}
    struct_value::Other
    struct_ptr::Ptr{Other}
    typedef_struct_value::TypedefStruct
    array::NTuple{2, Cint}
end
function getptr(x::Ptr{WithFields}, f::Symbol)
    f === :int_value && return Ptr{Cint}(x + 0)
    f === :int_ptr && return Ptr{Ptr{Cint}}(x + 8)
    f === :struct_value && return Ptr{Other}(x + 16)
    f === :struct_ptr && return Ptr{Ptr{Other}}(x + 24)
    f === :typedef_struct_value && return Ptr{TypedefStruct}(x + 32)
    f === :array && return Ptr{NTuple{2, Cint}}(x + 36)
    error("Unrecognized field of type `WithFields`" * ": $(f)")
end

function Base.getproperty(x::Ptr{WithFields}, f::Symbol)
    f === :int_value && return unsafe_load(getptr(x, f))
    f === :int_ptr && return unsafe_load(getptr(x, f))
    f === :struct_value && return getptr(x, f)
    f === :struct_ptr && return unsafe_load(getptr(x, f))
    f === :typedef_struct_value && return getptr(x, f)
    f === :array && return getptr(x, f)
    return getfield(x, f)
end

function Base.setproperty!(x::Ptr{WithFields}, f::Symbol, v)
    unsafe_store!(getptr(x, f), v)
end

I want to play around with it a bit more in CImGui.jl before merging, but what do you think?

Hmm, looks like nightly is broken:

Because BinaryBuilderBase.jl is broken on nightly: https://github.com/JuliaPackaging/BinaryBuilderBase.jl/blob/406ec5c26348a7965cdc35aba15c03f84c02b525/src/BinaryBuilderBase.jl#L226

Because nightly just bumped Pkg: https://github.com/JuliaLang/julia/pull/55112

And Pkg just changed an internal variable: https://github.com/JuliaLang/Pkg.jl/pull/3911

IIUC, with the new flag off, we can get the same output as before, right?

Almost the same, the only difference is that with 129555d the logic for bitfields will be in standalone getbitfieldproperty()/setbitfieldproperty!() functions instead of being inline with Base.getproperty()/Base.setproperty!(). But the behaviour should be identical :crossed_fingers: I already added a test for that in the bitfield tests in 2e7e00d, but I'll add some more to make it doesn't regress.

I don't know how many people are using this package. But let’s take a poll and see if there are any unexpected problems.
This PR provides an alternative method for field access.
The default behavior is that accessing a field always returns a Ptr and one needs to call unsafe_load manually to load/copy the value.
The opt-in behavior provided by this PR is that:

Accessing a field will automatically call unsafe_load to load/copy the value if the field type isn't a struct or array.
When a pointer is needed, the macro @ptr needs to be called manually.
The rest of the behavior is the same as the default behavior.

Please leave a 👍🏻 or 👎🏻  reaction, and any feedback is appreciated.

Alrighty, now we're back in the green :green_circle:

Gentle bump, I rebased this and fixed a lingering bug in @ptr after some more testing with https://github.com/Gnimuc/CImGui.jl/pull/131.

CI should be fixed with 5f8a145 (reverts #504), unfortunately we're now hitting this: https://github.com/JuliaLang/julia/issues/54664

I noticed some warnings on nightly about the field access exception type changing to FieldError: https://github.com/JuliaLang/julia/pull/54504
Fixed in ff9c955, though the formatting isn't the best:

Latest codegen
using CEnum: CEnum, @cenum

macro ptr(expr)
    if !Meta.isexpr(expr, :.)
        error("Expression is not a property access, cannot use @ptr on it.")
    end

    quote
        local penultimate_obj = $(esc(expr.args[1]))
        getptr(penultimate_obj, $(esc(expr.args[2])))
    end
end

struct TypedefStruct
    i::Cint
end

struct Other
    i::Cint
end
function getptr(x::Ptr{Other}, f::Symbol)
    f === :i && return Ptr{Cint}(x + 0)
    @static if VERSION >= v"1.12.0-DEV"
            throw(FieldError(Other, f))
        else
            error("Unrecognized field of type `Other`" * ": $(f)")
        end
end

function Base.getproperty(x::Ptr{Other}, f::Symbol)
    f === :i && return unsafe_load(getptr(x, f))
    return getfield(x, f)
end

function Base.setproperty!(x::Ptr{Other}, f::Symbol, v)
    unsafe_store!(getptr(x, f), v)
end

mutable struct WithFields
    int_value::Cint
    int_ptr::Ptr{Cint}
    struct_value::Other
    struct_ptr::Ptr{Other}
    typedef_struct_value::TypedefStruct
    array::NTuple{2, Cint}
end
function getptr(x::Ptr{WithFields}, f::Symbol)
    f === :int_value && return Ptr{Cint}(x + 0)
    f === :int_ptr && return Ptr{Ptr{Cint}}(x + 8)
    f === :struct_value && return Ptr{Other}(x + 16)
    f === :struct_ptr && return Ptr{Ptr{Other}}(x + 24)
    f === :typedef_struct_value && return Ptr{TypedefStruct}(x + 32)
    f === :array && return Ptr{NTuple{2, Cint}}(x + 36)
    @static if VERSION >= v"1.12.0-DEV"
            throw(FieldError(WithFields, f))
        else
            error("Unrecognized field of type `WithFields`" * ": $(f)")
        end
end

function Base.getproperty(x::Ptr{WithFields}, f::Symbol)
    f === :int_value && return unsafe_load(getptr(x, f))
    f === :int_ptr && return unsafe_load(getptr(x, f))
    f === :struct_value && return getptr(x, f)
    f === :struct_ptr && return unsafe_load(getptr(x, f))
    f === :typedef_struct_value && return getptr(x, f)
    f === :array && return getptr(x, f)
    return getfield(x, f)
end

function Base.setproperty!(x::Ptr{WithFields}, f::Symbol, v)
    unsafe_store!(getptr(x, f), v)
end

@JamesWrigley
https://github.com/cjdoris/UnsafePointers.jl overloads getindex/[] to eliminate the use of unsafe_load, which is a good way to solve the problem that this PR is gonna solve.

maybe we should also adopt the way to overload setproperty! and setindex!

Just to clarify, are you saying that obj.foo.x should return the pointer and obj.foo.x[] should call unsafe_load()?

This is what I'm currently thinking about:
x::Ptr{T}
- `x[]` calls `unsafe_load(x)`
- `x[] = y` calls `unsafe_store!(x, y)`
-  `x.a` always returns a `Ptr`, so `x.a[]` and `x.a[] = b` are valid
- `x.a = b` should be removed

I see :thinking: But yeah that sounds reasonable, and it's kinda nice to share some syntax with Ref. I'll take a shot at it later in the week.

The following equality holds for all types T in Julia and passing Refs as input parameters to the C function is prevalent. It could be better if Ptr and Ref work similarly for all types of T.
julia> x = Ref{Cint}(0)
Base.RefValue{Int32}(0)

julia> x[] == unsafe_load(Base.unsafe_convert(Ptr{Cint}, x))
true


Update determine runner workflow to use large runners if the branch name matches a certain format

Context:
This PR is being opened under sc-66351. It introduces a new change to CI ahead of release where a local branch (not forked) that matches the regex pattern vX.Y.Z-rcN (The N after rc being optional) is auto ported over to the large runners.
Though this may provide a minor bump to the runtimes of the workflows themselves, the bigger objective (right now at least) is to not wait long times to get a runner.
Description of the Change:
The change is a minor one within the determine-runner workflow. It now checks for both a label present on a pr OR if the pr branch names matches the rc branching format above.
Benefits:
Faster queue times for rc branches.
Possible Drawbacks:
Though the large runners and standard runners should have parity in theory. We do not live in a perfect world. There is a none-zero chance that workflows might break. But we can test that out as part of this PR.
Related GitHub Issues:
None.

Hey @rashidnhm, how are we testing this change?

Hey @rashidnhm, how are we testing this change?

Hey @AmintorDusko, we can test the large runners themselves by adding the urgent label to this PR.
To test the auto on-board, I have tested the expression locally against the past rc branch names, we can also create an rc branch name and test it (but I didn't want to do that right now to cause confusion :sweat_smile: )

Thank you, @rashidnhm!

Thanks @rashidnhm . I'm trusting this works. Please don't forget to update the CHANGELOG with a description and your name, and then I'll approve.

Thank you for that @vincentmr. If a bug does arise in the logic, we can definitely fall forwards and fix the issue. We also still retain the ability to port any PR to using large runners with the urgent label (this includes rc branches).


Some casted column exprs cannot be referenced in GROUP BY clause

This works
(-airlines.cancelled.cast('boolean')).value_counts()

but this does not
expr = airlines.cancelled.cast('boolean').value_counts()

This is a bug in Impala that will need to be worked around
HiveServer2Error: AnalysisException: select list expression not produced by aggregation output (missing from GROUP BY clause?): CAST(cancelled AS BOOLEAN)

closing the loop, the fix was committed in impala trunk: https://github.com/cloudera/Impala/commit/ea637f4f3a05452b1d0a14f545990f99ee1d721b

I gave casted exprs default names again, so re-opened this for more testing to catch the issue in earlier Impala versions

I'm satisfied with the workaround I put in -- there will still be pathological failures in Impala < 2.3 but they will be easy to fix


ts file issues

Does this package support merging ts files?

No, it doesn't handle TS files at all. There are some small routines for handling AVC/HEVC in bytestream format as used in TS files, but that is all. As a general tool for manipulating TS files, I'd recommend tsduck.
A TS library in Go that I've been using myself is https://github.com/Comcast/gots but it also rather low-level library.

Ok,thanks.


Remove The Ability To React To Own Posts in #hiring-or-looking

What Functionality Are You Suggesting?
When a user adds a reaction to a message they created within the #hiring-or-looking channel it should remove the reaction.
Why Will This Benefit The Community?
People abuse the reactions feature to “upvote” or “like” their post, which is misleading. I want to remove the ability for people to do this, whilst keeping the ability for other people to react to people’s messages within the channel (i.e. so you can upvote a message of someone who's services you've used before).

Is this still relevant?

It's not mission critical but I'll approve it if it works


Black Image Output

The colab works perfectly fine but when I try to run the code locally, the final result is always a black image.
Everything seems to be working as intended. The face, contextual, noise and etc all show up correctly and begin to process. You can even visualize this data on tensorboard. However after a few steps -- it's random.. sometime 10 steps sometimes 20 steps .. all the data gets changed to "nan" and as a result the output goes black.
Not sure what is going wrong. Any help? Happens the same with any image and any model/checkpoint. Any help would be greatly appreciated. @roxanneluo

Any help? I noticed a pattern. The whole thing goes "nan" after the 10th iteration. There are loss values until then. And it's always the 10th iteration. I've changed and lowered all values to see if anything helps. Nothing does.
Any help understanding this issue would be greatly appreciated. @roxanneluo

Nans seem to happen a lot of times, but I tried running it again and it worked somehow.

It could be because of high color transfer loss weights. Could you try lowering it and testing again?

Can you share the input image for me to test on it to reproduce the problem?

@roxanneluo for my case the problem actually appears in the provided Lincon sample. Without changing anything or giving it any  new image or parameter. It feels like an nondeterministic behavior.
Further more, dependency on older CUDA/PyTorch is a headache to get it to compile the first time (StyleGAN fault).

Yep. I get the error even on the Lincoln image that ships with this repo. No changes made to the basic inference command provided on the repo page.

Skipping NaN causing losses (I suspect its the contextual loss) enables the optimization to progress (i.e. just adding a nan check in the joint_loss.py)

Hello! I have found that if I exclude the "relu1_2" option from the "--cx_layers" list, then the NaN error does not appear.


(doc) add Lean language

This is a followup to #1689. We've created a new repository at https://github.com/leanprover-community/highlightjs-lean and linked to it in SUPPORTED_LANGUAGES.md.
I'm not 100% sure we've made the new repo in the recommended way, so if a highlightjs maintainer would like to take a look and give some suggestions, I'd be very grateful!
cc: @PatrickMassot.

It'd be nice if you ran the build script and then committed the distributable to your repo.

Is it useful for people to see the minified version in the repo? I generally don't commit build outputs to version control, so I'm curious to know the reasons for doing so here.

I generally don't commit build outputs to version control, so I'm curious to know the reasons for doing so here.

Just so users just using it on the web have a one click download or easy copy/paste, etc... not everyone has a build environment or the ability to set one up.

Is it useful for people to see the minified version in the repo?

It's not JUST minified, it's compiled specifically for auto-loading CDN-style support.

Understood, thank you!

Thanks for the contribution!


Chore rebase cmt

PR Details
remove commit id: d927bc83b8a7996fa0c744f559bb52720427a19a

Description

Related Issue

Motivation and Context

How Has This Been Tested

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My code follows the code style of this project.
[ ] I have updated changeset
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.7 out of 9 committers have signed the CLA.:white_check_mark: xuchaobei:white_check_mark: chenjiahan:white_check_mark: zllkjc:white_check_mark: targeral:white_check_mark: lastIndexOf:white_check_mark: dev-itsheng:white_check_mark: caohuilin:x: KyrieLii:x: yimingjfeYou have signed the CLA already but the status is still pending? Let us recheck it.


Added new course

What does this PR do?
Add Resource
For resources
Web Development
Description
Added full playlist of Python flask tutorial by Corey Schafer
Why is this valuable (or not)
Its hands on learning and people could build a social media platform after learning this
How do we know it's really free?
It's a Youtube playlist
For book lists, is it a book?
No
Checklist:

Not a duplicate
Included author(s) if appropriate
Lists are in alphabetical order
Needed indications added (PDF, access notes, under construction)

we prefer playlist links and presenter name for youtube.

fix linter errors, please

I'm going to assume, we should be free to safely close issues if the resource already exist in the repo.


Sign Up User, Username and Password Can Be Empty

We use GitHub Issues for bugs.
If you have a non-bug question, ask on Stack Overflow or Server Fault:

https://stackoverflow.com/questions/tagged/parse.com
https://serverfault.com/tags/parse

You may also search through existing issues before opening a new one: https://github.com/ParsePlatform/Parse-Server/issues?utf8=✓&q=is%3Aissue
--- Please use this template. If you don't use this template, your issue may be closed without comment. ---
Issue Description
When attempting to signup a user with empty username and password, I think that can get error which is username and password are required. But it still created user and session.
Steps to reproduce
Post /parse/users
{ "username": "", "password": "" }
Expected Results
like this
{ "code": 201, "error": "username and password is required." }
or
{ "code": 201, "error": "username is required." }
or
{ "code": 201, "error": "password is required." }
Actual Outcome
{
"objectId": "xehXxh1MDt",
"createdAt": "2017-03-07T14:43:02.468Z",
"username": "QTt1bmB1ojpw7krJ7SaK8rBkP",
"sessionToken": "r:41e117452a9279cbddb70d434264aaac"
}
Environment Setup

Server

parse-server version (Be specific! Don't say 'latest'.) : 2.3.6
Operating System: OSX
Hardware: MacBook Pro (Retina, 13-inch, Early 2015)
Localhost or remote server? Localhost

Database

MongoDB version: v3.4.0
Storage engine:
Hardware: Same as above
Localhost or remote server? Localhost

Logs/Trace
Include all relevant logs. You can turn on additional logging by configuring VERBOSE=1 in your environment.

I think this is a valid point and that it should prevent us from creating users with empty passwords and / or usernames.
I can take a look at this and attempt a PR if the contributors agree. I'll wait for their confirmation before getting started.

Actually, after further investigation, I feel like this was the intended behaviour.
For starters, to avoid users passing an empty password, you should set the passwordPolicy in the config. This will make sure all passwords respect the rules you defined.
Secondly, I see in the code that the username is set to a random secure string if left blank. Based on that, I am assuming that this use case was accounted for and is working as-designed.
  if (!this.data.username) {
    if (!this.query) {
      this.data.username = cryptoUtils.randomString(25);
      this.responseShouldHaveUsername = true;
    }
    return Promise.resolve();
  }

I'll wait for confirmation on this from the maintainers before proceeding any further.

The randomly generated username is intended IIRC for non password based logins (i.e.: facebook, oauth...)
It seems that we don't make the distinction between a missing key and an invalid key.
Not sure we should let empty usernames/passwords in, if only this is passed along, however we still need the automatically generated username for the case discussed above.

Great, thanks for the update. I don't think we should let empty usernames/passwords either. This use case is handled when using the JS SDK, but not the REST API. I'll try to base myself off of what was done in the JS SDK. I'll keep you posted.
Merci @flovilmart

Just created a PR for this: https://github.com/ParsePlatform/parse-server/pull/3650

And just merged! Thanks for the PR!

Awesome! Thanks for the quick merge!

Thank A Lot


add DataTree.pipe to allow chaining DataTree consuming functions

This adds a pipe method to DataTree, very similar to Dataset.pipe and DataArray.pipe (in fact, it is a modified copy).

[x] Closes #151
[x] Tests added
[x] Passes pre-commit run --all-files
[x] New functions/methods are listed in api.rst
[x] Changes are summarized in docs/source/whats-new.rst

This looks great, thanks @keewis !


.vsc.cat is incompatible with testthat::expect_output and tinytest::expect_stdout

Describe the bug
.vsc.cat does not emit output in such a way that testthat::expect_output observes it.
Impact: when running tests in debug mode, some tests erroneously fail.
To Reproduce
Run these two lines:
testthat::expect_output(cat('hello world'), 'hello world')

testthat::expect_output(vscDebugger::.vsc.cat('hello world'), 'hello world')

Your Launch config
N/A
This can be reproduced with R alone.
Expected behavior
Above two lines to produce the same result (no failure, no output).
Actual behavior
First line with base::cat produces no output (expectation is met).
Second line with vscDebugger::.vsc.cat raises an error (expectation not met).
> testthat::expect_output(cat('hello world'), 'hello world')
> testthat::expect_output(vscDebugger::.vsc.cat('hello world'), 'hello world')
Error: `vscDebugger::.vsc.cat("hello world")` produced no output
7: stop(exp)
6: doWithOneRestart(return(expr), restart)
5: withOneRestart(expr, restarts[[1L]])
4: withRestarts(if (expectation_broken(exp)) {
       stop(exp)
   } else {
       signalCondition(exp)
   }, continue_test = function(e) NULL)
3: exp_signal(exp)
2: expect(!identical(act$cap, ""), sprintf("%s produced no output",
       act$lab), info = info)
1: testthat::expect_output(vscDebugger::.vsc.cat("hello world"),
       "hello world")

Desktop (please complete the following information):

OS: ...
R Version: ...
vscDebugger Version: ...
vscode-r-debugger Version: ...

Additional context
Add any other context about the problem here.

Same problem with tinytest:
> tinytest::expect_stdout(cat('hello world'), 'hello world')
----- PASSED      : <-->
 call| tinytest::expect_stdout(cat("hello world"), "hello world")
> tinytest::expect_stdout(vscDebugger::.vsc.cat('hello world'), 'hello world')
----- FAILED[xcpt]: <-->
 call| tinytest::expect_stdout(vscDebugger::.vsc.cat("hello world"),
 call| "hello world")
 diff| output ''
 diff| does not match pattern 'hello world'

Thanks for opening this issue. This is the expected behavior of .vsc.cat. The function does not write to the normal stdout channel, but instead sends a message to the debug-frontend, including information about the location of the print statement in the code. Doing both of this at the same time, would make every output appear twice, which is not desired, I guess.
You can stop the debugger from overwriting cat (and print, str) using the debug config entries described here. This will fix your issue, but remove the source info in normal usage, which you can resolve by using different debug configurations for each.
Hope this helps!

Update: I just realized the debug config entry "splitOverwrittenOutput": true does pretty much exactly what you need. Currently it will give a warning Property splitOverwrittenOutput is not allowed., but this can be ignored and the behavior will change anyways. I'll update the documentation accordingly.

@ManuelHentschel Thanks! Indeed, in my example repo this setting worked perfectly to eliminate erroneous test failures. I will try it out in my main project(s) and report back if I hit any other issues. Feel free to close this issue.
Other doc changes that may be helpful:

It may be nice to call out that this config is useful when working with testing frameworks or other tools that deal with stderr/stdout.
In the doc about the config, specify that the default is false.


Add datetime attribute to ProductAttributeValue as asked for in issue #2389

Add datetime attribute to ProductAttributeValue as asked for in issue #2389
Used widget DateTimePickerInput from oscar.forms.widgets

LGTM.


Avoid space around pow for None, True and False

Summary
Closes #8187
Test Plan
Added integration test.
The similarity index doesn't change

Current dependencies on/for this PR:

main

PR #8189   👈

This comment was auto-generated by Graphite.

I'm not really sure I prefer this formatting, but I am not opposed.

I'm not really sure I prefer this formatting, but I am not opposed.

The removal of the space in general or more specifically removing the space when either side is False, True, or None?


Hiding the Emailaddresses

To avoid spam the email adresses should not be shown directly on the webpage but instead only be used in contact forms.

To narrow this question down a bit, we must elaborate a way to produce some content in a delayed manner, such that it cannot be fetched automatically.
Note also that such content would have be displayed outside any content page, because anything else would result in a very complicated (or at least not beautiful) solution I would like to avoid.

@Janluak at least after logging in the mail adresses can be shown on the webpage.
The contact form is not visible to the public right now, you have to log in first. To make the form public accessible, we have to add a captcha.

I don't think this is necessary. The @wh2 addresses have been plain-text
public for ages, and all of us are on enough more-or-less public lists
to receive spam forever, no matter what we do with SIPA.
The only real effect of any address-hiding will be reduced usability,
e.g. for people relying on having a full history available in their
client, using voice-over and mailto-recognition, on mobile devices...
Also I don't think it's very representative for the AG DSN to only offer
a cheesy webform, in total disregard for the standard of communication
in the intertubes, especially in technical matters. What about signing,
encryption, attachments?

^- This.

mmarx: no spam plz :(

nearly no spam with @wh12 with hiding the address shows that it is quite affective. The usability might be lower, yet is still good enough to be working smoothly (again check with @wh12)

Am 11.09.2015 um 20:46 schrieb Lukas Juhrich<EMAIL_ADDRESS>mmarx: no spam plz :(
—
Reply to this email directly or view it on GitHub https://github.com/agdsn/sipa/issues/78#issuecomment-139624388.

Alright, no trolling now.
@Janluak Although this discussion surely has to be lead in an appropriate place other than this, I just want to mention the following:

The objective of this entire exercise is not to reduce the amount of spam you get in your email, but the amount of spam you manually have to remove from your inbox.
Email obfuscation is a constant battle to come up with ever sophisticated bot-proof, human-readable encoding, and is a drain on the productivity of both the creator, and the correspondent.
“Almost any email address that you use for any length of time eventually becomes widely enough known that you should assume all the spammers have it.”
“The convenience of stable, easily copy-pastable email addresses” wins over trying to hide from the spambots.

taken from here.
Note also that we don't have significant spam at @wh2 addresses either (at most once per month, varying slightly), since the metric is spam you have to remove manually.
With this in mind, I plead to not use anything costing the user more clicks / redirects than necessary and use some easy obfuscating method such as display:none (in the link given above, there is a graph undermining its effectiveness).

@Janluak told me to write this here.
We recently got a message from one of our partners. They stated that the contact over the website did not work. Since that issue was closed shouldn't that work?

@MarauderXtreme Alright, I have quite bad news, there has been a typo in the mail address (suppor@). I will be sending a test mail in the next few minutes.
Besides that, I will try to recover the messages from the log entries, and will add an apology in the news.
The problem here was that I thought I tested it – which I did, but by sending a support mail to the hss to verify the address, and not by using the contact form. This should not have happened.


Let taker chose leverage

Resolves #1739

I think the calculation of the margin according to the leverage is still missing. Merging this without the calculation does not make much sense to me.

There is a second ticket for this: https://github.com/itchysats/itchysats/issues/1983

I think the calculation of the margin according to the leverage is still missing. Merging this without the calculation does not make much sense to me.

There is a second ticket for this: #1983

Ok, but I still think that activating this in the UI without implementing https://github.com/itchysats/itchysats/issues/1983 does not make sense. If we merge this the user will be able to select it, but the calculation update is missing.

I think the calculation of the margin according to the leverage is still missing. Merging this without the calculation does not make much sense to me.

There is a second ticket for this: #1983

Ok, but I still think that activating this in the UI without implementing #1983 does not make sense. If we merge this the user will be able to select it, but the calculation update is missing.

Fair enough, I'll add the other ticket into this PR to avoid merge conflicts.

Great stuff!
I gave it a try locally also playing with allowing x5 in the maker orders which results in a somewhat funny "bug" where the slider on the taker side allows 4 but that's actually not available. That's probably the problem of using a slider.

If we only plan to use 1, 2, 3 for now then I think we can merge, otherwise we should probably somehow fix this. Not sure the slider allows choices with different step intervals.

damn you were too fast :D , I noticed this bug as well and wanted to remove the x5 again from the maker before anyone else notices it 😬
I don't think the slider allows steps with different intervals neither, so the alternative would just be to allow leverage 4 aswell
For now, we only want to support 1,2,3 anyway, so I'll remove the option from the maker.

I've removed leverage 5 from the maker's UI because we don't want to support it
bors r+


[fix] URL was going to 404 page before

Works fine for me. You’re only making it a Markdown link to itself, so even if it were going to a 404 before, this wouldn’t fix it.


Minor schematic errors in documentation

Describe the bug
Great project!
I found some issues in the schematics in the hardware section of the documentation:

Battery orientation is wrong. Could be misleading if anyone follows the schematic literally
Reset pins available on the iSpindel PCB are missing (RST <--> GND)
Now I feel a bit picky: Replace name of U1 ("WEMOS-D1-MINI") to "ESP32-x"

Software:

Platform (esp8266, esp32)
Version 1.2.0

Cheers
Lars

Thanks for spotting those issues, I will take care of them.

Fixed the battery schematics. The reset connections are specific to the PCB design, added links to the most common PCB options for more information.
Changes the text on the U1 chip on the ESP32 design (could not find a suitable component in the component library).


No Bot response DOTNET

No response from test in web chat as suggested in the documentation.
Server response of 502. Tested locally using Bot framework emulator and works fine.
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

See Bot Framework additional resources for the best places to submit product requests or ask troubleshooting questions.

@gavindavies,
502 errors are usually indicative of configuration errors or other issues that may make your bot inaccessible. Which document did you follow, and what code did you use? Did you just deploy a sample, or was it custom code? Have you double-checked the instructions to make sure no step was skipped?

Hi Anish, I followed the documentation exactly while deploying the echobot sample! Hence why I was confused at the immediate 502

Two more questions:

Which AppType did you use?
Which Azure CLI version did you use?

I've run through these instructions recently, and I haven't had any issues deploying a bot.


Update RPM build scripts for release

What kind of PR is this?

/kind enhancement
What does does this PR do / why we need it:
Fixes the release process for RPM building by adding a way to pass in
a new variable.
Which issue(s) this PR fixes:
N/A
How to test changes / Special notes to the reviewer:
N/A
Signed-off-by: Charlie Drage<EMAIL_ADDRESS>

Nevermind! Using an env variable instead.

we are not advertising RPMs anywhere anymore, do we even need to build them?

@kadel For now we need this for our internal script, but no, we don't need this here. We can transfer it over to our release script.


We shouldn't display town-level ballot questions

if we do, we'll need a description for each. where can we get them?

Done


Reasoning behind the trait-oriented design

Hi, I was wondering why this crate choose to go with a trait-oriented design and all the complication with it instead of going with the primitive/struct and macros route like core is doing for uX, iX and fX ?

Apologies, but it's best if conversation about this is contained in a single issue. Answered in https://github.com/rust-lang/portable-simd/issues/228#issuecomment-1019352921


Encoding errors when message body contains unicode

Is there a reason the utf-8 charset is overridden to remove the body encoding? (https://github.com/fengsp/sender/blob/928d289ed33f369a856cb108cf5511fc3091d933/sender.py#L26) This seems to cause encoding errors when the body contains non-ascii characters, at least on python3.
  File "python3.4/lib/python3.4/site-packages/sender.py", line 97, in send
    c.send(message)
  File "python3.4/lib/python3.4/site-packages/sender.py", line 147, in send
    message.mail_options, message.rcpt_options)
  File "/usr/lib/python3.4/smtplib.py", line 765, in sendmail
    msg = _fix_eols(msg).encode('ascii')
UnicodeEncodeError: 'ascii' codec can't encode character 'u2019' in position 491: ordinal not in range(128)

I've worked around this by restoring the defaults:
charset.add_charset('utf-8', charset.SHORTEST, charset.BASE64, 'utf-8')

Same happens to me, changing that line fixes the problem.

Python 3.x is not supported yet.


Upgrade?

Hey Erik!
I just found this very nice resource! Thank you for creating it!
I have a quick question: I moved over the 1k subs limit recently. It is ok if we put my channel into the "tutorials" section? 😃
I also do Live Streaming (planning to be more consistent)
Thank you!

OK I moved you to tutorials!


IMPROVEMENT: Cache Templates, only update the route component, not the entire layout

https://github.com/Rezact/Rezact/blob/3983220cf8280366599ee67ffc44389adae4b2eb/src/lib/rezact/router.ts#L115-L128

This issue is blocked by #30 .... using signals to swap the Route Components needs to be able to handle Fragments


Online Payment Compensation Support

For whatever reason, the online payment does not receive payment result notification.
A compensation operation should be performed to query if the payment is success.

Released in 0.1.2


changes in "include Text" text box effect "highlight lines..." textbox

Describe the bug
changing the content of the include text text box will also change the text in the highlight lines
To Reproduce
Steps to reproduce the behavior:

write a  word in the include text
see it updated in the highlight textbox
write a different word
highlight textbox will change as well

see
Expected behavior
highlight textbox stays the same unless directly altered
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

this is works as specified as the user most likely wants to highlight the current filter criteria

behavior changed: Highlight textbox is not connected to include texbox anymore


Change license to something more standard

I want to suggest something similar to what happened to the nerdcommander.
My points are pretty much identical to what is discussed in this issue https://github.com/preservim/nerdcommenter/issues/217.
Switching to another license can make it easier for people to use and/or contribute to the project.
I don't have any strong argument for/against any of the available licenses other than PUBLIC DOMAIN which doesn't really make that much of a difference with WTFPL; Since it is not considered a real license in many jurisdictions around the world(I've never consulted a lawyer about this but from what I've read on the internet I think it is true).
I'm going to ping a few of the people with most contributions to the project to chip in in this discussion.
@scrooloose @PhilRunninger @alerque @lifecrisis

This is also mentioned in #1280 which shows there is a real demand for it, And I'm not just suggesting this change for the sake of change alone.

My comments on the issue you linked as well as the previous re-license of nerdcommenter pretty much explains my position on this. The potential contributor with a legaly reason for not being able to contribute is a pretty solid nudge. Even if they don't turn back up I'm sure there are others is similar positions.
I'd fully support a re-license to CC0. Actually I'd be fine with MIT or several other options too but my previous research suggests CC0 is the closest match with the WTFPL while being palatable to FOSS orgs, individuals on the prudish side (myself included), and also having some legal standing in places where public domain is not a thing.
Given the lack of barriers to re-licensing in this situation I would probably just let this sit around a little while collecting upvotes and any comments, then if nobody objected with unaddressed concerns we'll just go for it.

Thank you for pinning this issue, I didn't want to be rude and pin this without permission from you.
I think CC0 is a solid choice for this project. I personally license everything under MIT or (L)GPL-3(mostly for tools since in my opinion, they benefit the most from the sticky license); But CC0 has a similar spirit to the original license(minus the coolness), and it will raise the least amount of objections(and hopefully none).


Linux Version pls

I would love to see a linux version of this tool it would be so awesome. I know there are other linux alternatives like Leetmouse and mouse driver, but none of them shows the graph and I couldn't get the Leetmouse-GUI to work. and since I'm so new to linux it's very confusing for me to go and edit the values in the files.

https://github.com/a1xd/rawaccel/issues/96


fix: Charges Dashboard -> Range added renamed to Ø Charge rate

fixes #4348 (should be merged on top of #4338, I can rebase after merge)

hm seams like you used your #4338 branch for this pr

yes 👍

@swiffer any idea why it still shows 27 changes after merging #4338 ?

Tested successfully.


FreshRSS Support

Is it possible for Vienna to support Fresh RSS? I chose Other from the Sync settings but it didn't work for me.
https://freshrss.org/

FreshRSS supports clients through two APIs:

Google Reader API (best set of features, most widely used, kind of de facto standard)
Fever API

I can see the Vienna-RSS supports the Open Reader API . As far as I can see, this API has never been written / completed (or I cannot find it - links welcome), and it is the first client I stumble upon that seems to support it.
I am happy to collaborate from FreshRSS side to make the compatibility happen.
Related: https://github.com/FreshRSS/FreshRSS/issues/2091

@Alkarex Thank you for responding and linking to the FreshRSS issue I submitted. I am quite new at self-hosted RSS world so unfortunaltely I cannot offer any contribution at this time. I am really hoping that someone from FreshRSS will respond. As far as I can tell both are great applications to solve the problem of news aggregation. It would be great to see if these two apps can work together.

There is no important differences between Google Reader API and Open Reader API.
I would appreciate temporary access to a FreshRSS account to debug this.

@Alkarex
Bonjour 😃
barijaona chez gmail point com

Thanks to the collaboration with @Alkarex, a new compatible version of FreshRSS should be available soon.
Meanwhile, I found some improvements / clarifications in Vienna's OpenReader code which have been submitted as #1200.
I just want to make clear here that these changes are not directly FreshRSS related.

Thank you both! Awesome work.

@Alkarex Can you tell me how to install the appropiate commit onto my server without screwing everything up? I'm not very good at advanced git commands. I don't want to install a separate instance of FreshRSS just for testing. If I can simple pull the correct commit temporarirly and revert to back after testing is completed that would be great!

@bisherbas Have you installed FreshRSS using git?
If yes, please see https://github.com/FreshRSS/FreshRSS#example-of-full-installation-on-linux-debianubuntu
cd /usr/share/FreshRSS/ # Or the path you use
sudo git checkout -b dev origin/dev

Should do it. If not, please report any error message you might get.
If you have not installed it by git, you can just deploy https://github.com/FreshRSS/FreshRSS/archive/dev.zip on top of your installation (after having done a back-up).

@Alkarex Yes I did install FreshRSS using git. After checking out the dev branch via the command you have provided and verifying that everything works properly, can I return to the latest stable release with sudo git pull? Or is there another command I should run?


Please identify the terminal emulator with TERM, do not pretend to be xterm.

Presently bash.exe/cmd.exe is not detectable by the usual method - $TERM - it misidentifies itself as xterm. Please, it behaves very differently from xterm, it emulates just an incredibly small amount of what sets xterm apart, has little in common with xterm (compare behavior in vttest). It should export something different to the environment for sanity to avoid the certain mess this can spell in the future.
TERM=linux is easier to justify. It should set TERM=interix, interix-nti, or some new suffix for now.

Fixing this is not that easy: the new setting would need to be added into the terminfo database.  It can be easily done on the local Linux subsystem -- but what if you ssh to a remote host?  Even if the new terminal's definition was added to the likes of Debian or Fedora unstable today, it'd take a long time to get to stable releases.  And that's assuming distro maintainers doing their job -- Solaris still doesn't understand TERM="linux" despite that being only 25 years old.
So there are two ways:

pragmatic: pick something defined in ncurses-term or ncurses-base
idealistic: use a new name and request its inclusion in terminfo databases

I guess it'd be best to go with a hybrid: masquerade as something for now but submit a new definition so in a year or two you'll be able to switch (no one cares about Solaris anymore...).
And identifying yourself as "xterm" is about the worst choice: xterm is an extremely feature-rich/bloated terminal, current Windows Console is not even adequate for the moment (which is a separate issue).  Let's pick a simpler definition for now...

Maybe some of this will be addressed when/if they bring some of the Windows 10 improvements to the CMD.exe console across to WSL + Ubuntu?

https://blogs.windows.com/buildingapps/2014/10/07/console-improvements-in-the-windows-10-technical-preview/

I also see there is TERM=interix and interix-nti! How about that! And it's just about everywhere! It's the champion at curses's box characters with raster fonts. It's otherwise a bit evident that it probably worked better on the old cons.

It seems to me that could be what this identifies as - and work on modernizing the termcaps.

As far as I've tried I prefer pcansi over interix.  Anyway, not xterm.

Thanks for the feedback and suggestions - we'll take this into consideration for our future planning.

any update here?

To be honest it should just define its own Termcap definition file. They're well defined, and they're there for this exact purpose. Plus, Microsoft would be able to define whatever escapes would suit their existing code bases, and terminfo-aware applications wouldn't have to change a thing.
Side note: If your application isn't terminfo aware, it should be. Assuming the xterm escapes will get you by is a hack and an unsafe assumption.

Thanks for the discussion.
Closing this issue since:

Console is now MUCH more XTERM compatible
This is the WSL issues repo, but this is an issue in Console which has its own Console GitHub Repo
GitHub doesn't allow issues to be moved between repos, preserving posters' identity :(

If you have further asks/issues, please file new issues on our Console GitHub Repo.