Add possibility to launch specific script

When you are updating, for example, a Dockerfile.mo file, in the current scripts you need to redo cd . in order to rebuild the final Dockerfile.
It would be great to have an optional parameter in ddb enter which will execute a part of the script such as :
ddb enter --script=templates

It should handle glob patterns and multiple occurences.

ddb now has a watch mode that supports automatic refresh of generated files when template changes. I also plan to make generated files read-only so that use won't be able to modify a generated file.


Expected parent IDs to be set when ordering by parent ID.

Hi Prisma Team! My Prisma Client just crashed. This is the report:
Versions

Name
Version

Node
v16.16.0

OS
rhel-openssl-1.0.x

Prisma Client
4.8.1

Query Engine
d6e67a83f971b175a593ccc12e15c4a757f93ffe

Database
mysql

Logs
prisma:tryLoadEnv No Environment variables loaded
prisma:tryLoadEnv Environment variables not found at null
prisma:tryLoadEnv Environment variables not found at undefined
prisma:tryLoadEnv No Environment variables loaded
prisma:client dirname /var/task/node_modules/.prisma/client
prisma:client relativePath ../../../prisma
prisma:client cwd /var/task/node_modules/.prisma/client
prisma:client clientVersion 4.8.1
prisma:client clientEngineType library
prisma:client:libraryEngine internalSetup
prisma:client:libraryEngine:loader Searching for Query Engine Library in /var/task/node_modules/.prisma/client
prisma:client:libraryEngine:loader loadEngine using /var/task/node_modules/.prisma/client/libquery_engine-rhel-openssl-1.0.x.so.node
prisma:client:libraryEngine library starting
prisma:client:libraryEngine library started
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true

Client Snippet
const looks = await prisma.looksOnMaterials.findMany({
    where: {
      materialId: {
        in: assortments.map((a) => a.material.id),
      },
    },
    select: {
      materialId: true,
      look: {
        select: {
          name: true,
          lookBook: {
            select: {
              category: true,
            },
          },
        },
      },
    },
  });

Schema
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["fieldReference"]
}

datasource db {
  provider     = "mysql"
  url          = env("DATABASE_URL")
  relationMode = "prisma"
}

model Material {
  id             String                 @id
  description    String                 @db.VarChar(255)
  colour         String                 @db.VarChar(255)
  level2         String                 @db.VarChar(255)
  level25        String                 @db.VarChar(255)
  level3         String                 @db.VarChar(255)
  level4         String                 @db.VarChar(255)
  level5         String                 @db.VarChar(255)
  origin         String?                @db.VarChar(255)
  composition    String?                @db.VarChar(255)
  createdAt      DateTime               @default(now())
  updatedAt      DateTime               @updatedAt
  materialPrices MaterialPrice[]
  articles       Article[]
  linkedLines    LinkedLine[]
  assortments    Assortment[]
  buys           Buy[]
  ranges         SubLocationRange[]
  looks          LooksOnMaterials[]     @relation("lookMaterial")
  posts          MaterialsOnPosts[]
  campaigns      CampaignsOnMaterials[]
}

model LookBook {
  id           String     @id
  collection   Collection @relation(fields: [collectionId], references: [id], onDelete: Cascade)
  collectionId String
  category     String
  createdAt    DateTime   @default(now())
  updatedAt    DateTime   @updatedAt
  looks        Look[]

  @@index([collectionId])
}

model Look {
  id           String     @id
  collection   Collection @relation(fields: [collectionId], references: [id], onDelete: Cascade)
  collectionId String
  lookBook     LookBook   @relation(fields: [lookBookId], references: [id], onDelete: Cascade)
  lookBookId   String
  name         String
  createdAt    DateTime   @default(now())
  updatedAt    DateTime   @updatedAt

  materials LooksOnMaterials[]

  @@index([collectionId, lookBookId])
  @@index([lookBookId])
}

model LooksOnMaterials {
  id         String   @id
  look       Look     @relation(fields: [lookId], references: [id], onDelete: Cascade)
  lookId     String
  material   Material @relation("lookMaterial", fields: [materialId], references: [id], onDelete: Cascade)
  materialId String
  runwayLink Boolean  @default(false)
  createdAt  DateTime @default(now())
  updatedAt  DateTime @updatedAt

  @@index([lookId, materialId])
  @@index([materialId])
}

Prisma Engine Query
{"X":{}}

Having a similar issue

Hey @sbkl @ashemag, could you provide the data sample from your DB that causes the issue? Unfortunately, code snippet and schema are not enough to reproduce the issue in this case.

Hey @sbkl @ashemag  ,
Did you get a chance to have a look at my previous comment? It'd be helpful for us to move your issue forward.
Without further information, we'll have to close this issue. Thank you 🙏


Tweak feed card styles

Small tweaks to #3998
No real changes to desktop, so just mobile screenshots.
This PR adjusts FeedSourceCard to truncate the display name and Feed by text to 1 line. This would affect rendering in other locations in the app.
However, displayName for a feed gen is limited to 24 graphemes, so this is really only an issue on small screens.
For the Feed by text, this could be much longer, but as you can see with a long handle, the wrapping is pretty bad. When clicking into a feed detail screen, this text is shown in full.
After:

Before:

Just adding a test: top feed is at max length


Remove 'extra-lib-dirs'.

Created by: nc6
This should be picked up from .pc file, and also breaks with
stack 1.2

Closing as an obsolete


Code blocks not syntax highlighting

Is there any way to make code blocks have syntax highlighting?

Sure you can use something like React Syntax Highlighter or React Prism. Check out the example from react-syntax-highlighter below and feel free to open a PR if you implement it!
import SyntaxHighlighter from 'react-syntax-highlighter';
import { docco } from 'react-syntax-highlighter/dist/esm/styles/hljs';
const CodeBlock = () => {
  const codeString = '(num) => num + 1';
  return (
    <SyntaxHighlighter language="javascript" style={docco}>
      {codeString}
    </SyntaxHighlighter>
  );
};


No webhoook response on connection

still not working even installed 2.2.4, please contact me at whatsapp, i send u server to debug if needed

it's working yes, we just tested it please check your code


Option to change default blur for

Summary
The default blur for small <g-image> is 40. This is often too much. There should be an option in config to change this globally.
We should probably also change the default so something like 15-20.

@tomtev @hjvedvik should we close this issue? I can open a PR with the default blur changes if that's what's keeping you from closing the issue.

Yes, I think so, @hacknug. We have probably just forgotten to close this. The default blur can already be configured with a images.defaultBlur option in gridsome.config.js. But it's not documented yet because the plan is to move the image processing out to a separate plugin with proper documentation.


Minor cleanups

replace all .../CasperLabs/casper-node URLs with .../casper-network/casper-node
remove

build_wasm_package.sh
docker_make.sh
joiner-dev-tmux.sh
run-dev-tmux.sh
stop-dev.sh
update-rev.sh
upload.sh

avoid using #[serde(with = "HexForm")] in ExecutableDeployItem::ModuleBytes::module_bytes (we can remove the dependency entirely)
feature-gate CorrelationId::is_empty() via #[cfg(test)]

Triaged;

replace all .../CasperLabs/casper-node URLs with .../casper-network/casper-node - Still some references are there. Needs cleaning up.
remove - Done

build_wasm_package.sh
docker_make.sh
joiner-dev-tmux.sh
run-dev-tmux.sh
stop-dev.sh
update-rev.sh
upload.sh

avoid using #[serde(with = "HexForm")] in ExecutableDeployItem::ModuleBytes::module_bytes (we can remove the dependency entirely) - Done
feature-gate CorrelationId::is_empty() via #[cfg(test)] - Removed

Triage update - Create new ticket for "replace all .../CasperLabs/casper-node URLs with .../casper-network/casper-node" and close this ticket.

New ticket created to replace incorrect URLs - https://github.com/casper-network/casper-node/issues/4902


Domain registration expired

http://openperipheral.info/ points to a stub page with
NOTICE: This domain name expired on 6/23/2016 and is pending renewal or deletion.

Thanks for info. I'm trying to contact @mikeemoo, since he holds registration.
For now, use openmods.info.

I'm using it, but it has about zero documentation. On any of the openmods. And ingame help is also all botched, and I barely can make heads to tails.

@AnrDaemon I wrote a program to provide browsable documentation for attached OpenPeripheral peripherals, which you can download like so:
pastebin get 3NPXAasm opdoc
It requires an advanced computer and it will show tabs with documentation for each attached peripheral.

Ugh, really, this again?
There are multiple ways to get documentation, including command to generate offline HTML document.

I'm talking about OpenBlocks documentation. I.e. console commands, like ob_inventory.

You mean this or  ?
I don't bother with recipes, since NEI/JEI/TMI/Wikis are enough. About sensor: just place it in creative and play.

just place it in creative and play.

That's what ducumentation is for - to save time "playing" and, possible, missing an important feature, and do actual work instead.

It's not software engineering project, it's game that in vanilla version does not tell you how to make pickaxe.
Also, I don't see your point. Every function on sensor is documented.


chore(NODE-5986): parallelize SRV/TXT resolution

Just a small thing I noticed while looking at the driver code, this is a quick win to improve connection establishment performance.
Description
What is changing?
Is there new documentation needed for these changes?
What is the motivation for this change?

Release Highlight

Fill in title or leave empty for no highlight

Double check the following

[x] Ran npm run check:lint script
[x] Self-review completed using the steps outlined here
[x] PR title follows the correct format: type(NODE-xxxx)[!]: description

Example: feat(NODE-1234)!: rewriting everything in coffeescript

[ ] Changes are covered by tests
[ ] New TODOs have a related JIRA ticket

Just verifying from spec: "TXT records MAY be queried either before, in parallel, or after SRV records."


Modified mkdir flags register.c

This flags are able to create a new file with read/write/search permissions for owner and group, and with read/search permissions for others.

Can you update the other demo as well, please?


appimage-run: will not run OpenRA mods, due to it failing to detect Mono, even when installed

Issue description
OpenRA provides AppImages for its official mods and via their SDK they make it easier for developers of unofficial mods to distribute their mods as AppImages.
The AppImages they provide are unusual in that they do have a host dependency, beyond FUSE and modern standard system libraries, Mono. Presently a compatible version of Mono is installed on my system, namely version <IP_ADDRESS> (which is the version mono --version gave me), but still I see this error dialog box appear:

When I try to launch the official Red Alert mod using appimage-run.
Steps to reproduce

Install NixOS 18.09, using my configs: https://github.com/fusion809/NixOS-configs/tree/dc4954f15812bbb319fdcf7644646c9ed9fb968d).
Install Mono <IP_ADDRESS> and appimage-run with:

nix-env -f '<nixos-unstable>' -iA mono-<IP_ADDRESS> appimage-run

(refer to note 1 for further details)

Obtain the official release-20180923 Red Alert AppImage from (and yes I have tested this on other AppImages belonging to OpenRA mods): https://github.com/OpenRA/OpenRA/releases/download/release-20180923/OpenRA-Red-Alert-x86_64.AppImage, e.g. by downloading it with wget:

wget -c https://github.com/OpenRA/OpenRA/releases/download/release-20180923/OpenRA-Red-Alert-x86_64.AppImage

Set its permissions to executable with:

chmod +x OpenRA-Red-Alert-x86_64.AppImage

Run appimage-run on it, with:

appimage-run OpenRA-Red-Alert-x86_64.AppImage

and Voila, you should see this error.
Technical details
$ nix-shell -p nix-info --run "nix-info -m"
these paths will be fetched (0.35 MiB download, 1.59 MiB unpacked):
  /nix/store/63j8mi5vjyxfc89rhjknwxaxqg3a2sx2-paxctl-0.9
  /nix/store/bqp3d4yhpx6h60fv8jww5id0nkm44034-patchelf-0.9
  /nix/store/i6vl5lwlz5jbkg4r6p340dwmj6fha3xq-stdenv-linux
  /nix/store/kic17fw8wil74k04kzh3dha43izrr9j3-bash-interactive-4.4-p23-dev
  /nix/store/ql3azyviwyc6w73h6prk1j2945skfapf-gnumake-4.2.1
copying path '/nix/store/kic17fw8wil74k04kzh3dha43izrr9j3-bash-interactive-4.4-p23-dev' from 'https://cache.nixos.org'...
copying path '/nix/store/bqp3d4yhpx6h60fv8jww5id0nkm44034-patchelf-0.9' from 'https://cache.nixos.org'...
copying path '/nix/store/ql3azyviwyc6w73h6prk1j2945skfapf-gnumake-4.2.1' from 'https://cache.nixos.org'...
copying path '/nix/store/63j8mi5vjyxfc89rhjknwxaxqg3a2sx2-paxctl-0.9' from 'https://cache.nixos.org'...
copying path '/nix/store/i6vl5lwlz5jbkg4r6p340dwmj6fha3xq-stdenv-linux' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 4.14.85, NixOS, 18.09.1534.d45a0d7a4f5 (Jellyfish)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.1.3`
 - channels(fusion809): `""`
 - channels(root): `"nixos-18.09.1534.d45a0d7a4f5, nixos-unstable-19.03pre161545.7c73f53d836"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Notes:

nixos-unstable is the repo mentioned as it is what I was using when I noticed this error. By-the-way, I have also tried adding mono to my systemPackages array in /etc/nixos/configuration.nix and rebuilding. Even after this, and following steps 3-5, I receive this same error. I also tried adding both mono and appimage-run to this array and rebuilding, and after this I still received this error when trying to run the subsequent steps. In case you're wondering, I made sure to start new shells after rebuilding, so my environment variables should have been properly set up. I verified I was using system appimage-run and monoby runningwhich mono appimage-run` which returned:

/run/current-system/sw/bin/mono
/run/current-system/sw/bin/appimage-run

.

Should probably cc @tilpner, as he seems like the lead dev of appimage-run.

appimage-run doesn't use your system environment, you need to add mono to appimage-runs environment:
# Something like this
appimage-run.override { extraPkgs = p: with p; [ mono ]; }

I'm fairly new to NixOS, so I'm not sure what I'm meant to do with this. Guessing that's something I add to my /etc/nixos/configuration.nix file?

That's a Nix expression describing a modified appimage-run that will include mono.
You can use that anywhere you can use Nix expressions, like nix-build, nix-instantiate, overlays, and of course your configuration.nix too.
# Here's a module that will install this modified appimage-run for the user "fusion"
{ pkgs, ... }: {
  users.users.fusion.packages = [
    (pkgs.appimage-run.override {
      extraPkgs = p: with p; [ mono ];
    })
  ];
}

Aha it works now, thanks! I'm pleased I cc'ed ya. So this issue essentially now becomes an instruction manual for those experiencing the same issue.


[Bug] Inconsistent behaviour for allowAutoTopicCreationType

Search before asking

[X] I searched in the issues and found nothing similar.

Version
Run a standalone cluster in Docker
Pulsar: 3.1.0
Minimal reproduce step
docker script environment
-e PULSAR_PREFIX_allowAutoTopicCreationType=partitioned

and none such env(thus default non-partitioned)
What did you expect to see?
Both CreationType should auto create same RETRY/DLQ rule topic. <topicname>-<subscriptionname>-RETRY
ref:
https://github.com/apache/pulsar-site/pull/651
https://pulsar.apache.org/docs/3.1.x/concepts-messaging/#retry-letter-topic
What did you see instead?
Write some code to consume topic, for example：
consumeFunc(topicname, subscriptionname, xxxHandler)

When using non-partitioned configuration server, it auto create topic as respected.
But when using partitioned config server, it auto create topic subName-RETRY/DLQ which may conflict when multi topics has same subName.
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

I may have found the cause of this bug.
When allowAutoTopicCreationType=non-partitioned, and the topic does not exist, when getPartitionedTopicMetadata is executed, the broker automatically creates a topic with a partiton number of 1. This results in the use of the old name rule ({tenant}/{namespaces}/{sub}-RETRY).
See the following code, especially lines 144 to 149
https://github.com/apache/pulsar/blob/2bf13547bf4b4ec9babd6513a87dffbd53d678bb/pulsar-client/src/main/java/org/apache/pulsar/client/impl/ConsumerBuilderImpl.java#L126-L149


ATS FRIENDLY RESUME

Is there an existing issue for this?

[X] Yes, I have searched the existing issues and it doesn't exist

Feature Description
Please make resumes which are ats-compatible

The Onyx resume is indeed ATS compatible, as it doesn't contain columns or unnecessary background graphics. Is there another kind of resume template you were looking for?


Refresh credentials on node removal

Problem:
The same credential used to create a node is used to delete it so if a
cloud cred is updated or keys rotated nodes will leak
Solution:
Before doing an update or delete of a node rebuild the credentials using
the latest cloud cred referenced in the template

https://github.com/rancher/rancher/issues/24234


[New Port Request]

Library name: MITK
Library description: The Medical Imaging Interaction Toolkit (MITK) is a free open-source software system for development of interactive medical image processing software. MITK combines the Insight Toolkit (ITK) and the Visualization Toolkit (VTK) with an application framework.
Source repository URL: https://github.com/MITK/MITK
Project homepage: http://mitk.org

Block by boost-python build failure:
wrap_python.hpp(57): fatal error C1083: Cannot open include file: 'pyconfig.h': No such file or directory

I'll try putting a pull request for this.

I attempted to throw together a portfile, but it looks like there's an issue with qt5-base. QT5 is a dependency for this library, so i added it as a build-depends. But QT5 is having errors building (Seems independent from anything involving my portfile. I tried installing QT5 alone and it still resulted in an error)
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
    Command failed: C:/Users/vpaladino/Desktop/vcpkg/downloads/tools/jom/jom-1.1.3/jom.exe /J 8
    Working Directory: C:/Users/vpaladino/Desktop/vcpkg/buildtrees/qt5-base/x86-windows-rel
    Error code: 2
    See logs for more information:
      C:\Users\vpaladino\Desktop\vcpkg\buildtrees\qt5-base\build-x86-windows-rel-out.log
      C:\Users\vpaladino\Desktop\vcpkg\buildtrees\qt5-base\build-x86-windows-rel-err.log

Here's the QT5 error logs
config-x86-windows-dbg-out.log
config-x86-windows-rel-err.log
config-x86-windows-rel-out.log
build-x86-windows-dbg-err.log
build-x86-windows-dbg-out.log
build-x86-windows-rel-err.log
build-x86-windows-rel-out.log
config-x86-windows-dbg-err.log

boost-python failure will be fixed in #8882.

Error:
C:\Users\vpaladino\Desktop\vcpkg\buildtrees\qt5-base\src\5.12.5-0f870116d4\src\3rdparty\angle\src\libANGLE\renderer\d3d\d3d11\texture_format_table_autogen.cpp : fatal error C1083: Cannot open compiler generated file: '': Invalid argument
C:\Users\vpaladino\Desktop\vcpkg\buildtrees\qt5-base\src\5.12.5-0f870116d4\src\3rdparty\angle\src\libANGLE\renderer\d3d\d3d11\texture_format_table_autogen.cpp
is already 237 characters long..... should we make the path length warning fatal if the root path is much longer than the warning level? So that people actually try to build with shorter paths before posting an issue?
If that is not the root problem I would assume insufficient disk space.

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.

Since the DCMTK library on which MITK is depending is now integrated in vcpkg why doesn't MITK part of this?
I've looked into the CMakeLists.txt and BlueBerry, CppMicroservices should be used directly from vcpkg and not integrated inside of that big mess.
Currently supported by vcpkg:

CppMicroservices

DCMTK

Missing port:

BlueBerry Framework
MITK

Please let us know when this is doable.
Best Regards

Since the DCMTK library on which MITK is depending is now integrated in vcpkg why doesn't MITK take part of this?
I've looked into the CMakeLists.txt and BlueBerry, CppMicroservices should be used directly from vcpkg and not integrated inside of that big mess.
Currently supported by vcpkg:

CppMicroservices
DCMTK

Missing port:

BlueBerry Framework
MITK

Please let us know when this is doable.
Best Regards

Well, according to Stefan, the CppMicroservices of vcpkg is probably not the same one that MITK is using.

CppMicroServices started like BlueBerry as MITK subproject (Modules/CppMicroservices) and it is still a subproject in its initial version (which we are using). There’s also subsequent versions of CppMicroServices that are completely decoupled and are hosted on http://cppmicroservices.org/ and have nothing to do with MITK anymore (and won’t work out of the box with MITK).

<EMAIL_ADDRESS>


\s+ mode shouldn't be on by default

Squashing spaces makes compiler output harder to read, sometimes much harder.  It's not helpful at all for most screen sizes unless an advanced user creates multiple output panes.
Some StackOverflow questions/answers that include compiler asm output get posted with this de-indented output, making it harder for other people to read the code (so the bad default has negatively affected me directly), but it would help people for their own use, too.
e.g. this ICC18 output: https://godbolt.org/g/G3KKGh
strlen_1(char const*):
  xor eax, eax #6.8
  cmp BYTE PTR [rdi], 0 #6.28
  je ..B1.6 # Prob 10% #6.28
  mov rdx, rax #6.4
..B1.3: # Preds ..B1.4 ..B1.2
  inc rdx #6.4
  lea rcx, QWORD PTR [rdx+rdx] #6.41
  cmp BYTE PTR [-1+rdi+rcx], 0 #6.28
  lea rax, QWORD PTR [-1+rdx*2] #6.41
  je ..B1.6 # Prob 18% #6.28
  mov rax, rcx #6.41
  cmp BYTE PTR [rdi+rcx], 0 #6.28
  jne ..B1.3 # Prob 82% #6.28
..B1.6: # Preds ..B1.3 ..B1.4 ..B1.1
  ret #7.11

(ICC puts comments on every line.  With color highlighting it's merely bad, not unintelligible.)
It's bad for other compilers with long mnemonics (e.g. x86 SIMD instructions like vpunpcklqdq) mixed with short instructions like dec rdi.

Thanks for the feedback. I don't have any opinions for nor against this, and it's a 1 line change. So I'll default to whatever @mattgodbolt decides. But that can take a while, as he is currently with limited internet access

Great example of why \s+ isn't a good default, @pcordes ! Thanks for the feedback. I personally like the squashed output for GCC etc, but you're right, it makes a right mess of icc's lovely indented output.
Let's change the default to being off. It will still be on by default for embedded views, and of course it can be toggled on and off if individuals like the look of it.


Improve Sandcastle load time

By using the built Cesium.js for the deployed version.
See https://github.com/AnalyticalGraphicsInc/cesium/pull/4889#discussion_r96953182

In the interest of avoiding thrashing, it's worth noting that we went the other direction (from pre-built to separate requires) back in #2164.  We did this so users didn't need to run combine before running Sandcastle.  Maybe we could look for the built version for speed, and fall back on the requires for convenience?  That seems like a lot of dependency logic to inject just to get a version number and autocomplete working.

+1 for improving load times though!

@emackey I'm suggesting that we basically just have this optimization for the released version.  I'm open to other variations, but do not want to require building often.

Ah, release Sandcastle should use a built copy of Cesium, yes.


Cannot import name SocketIO

I was trying to use socketIO_client but always getting this error:
"from socketIO_client import SocketIO
ImportError: cannot import name SocketIO"

hello
please I almost have the same problem and I try this solution but nothing.
perable program or batch file.
Traceback (most recent call last):
File "train.py", line 14, in
from config import config
File "C:\Users\lenovo\Desktop\RGBD_Semantic_Segmentation_PyTorch-master\model\SA-Gate.nyu.432\config.py", line 58, in
from furnace.utils.pyt_utils import model_urls
File "C:\Users\lenovo\miniconda3\lib\site-packages\furnace_init_.py", line 20, in
from .context import ContainerContext  # NOQA: F401 '.context.ContainerContext' imported but unused
File "C:\Users\lenovo\miniconda3\lib\site-packages\furnace\context.py", line 28, in
from . import pid1
File "C:\Users\lenovo\miniconda3\lib\site-packages\furnace\pid1.py", line 27, in
from socket import sethostname
ImportError: cannot import name 'sethostname' from 'socket' (C:\Users\lenovo\miniconda3\lib\socket.py)
please help me


hip runtime compilation bug in simple cupy code

Hello, I'm trying to use cupy with AMD MI50 GPUs and I find that there is a bug in the hip runtime compilation code.  Running this simple code piece will get these error messages:
import numpy as np
import cupy as cp

squared_diff = cp.ElementwiseKernel(
    'float32 x, float32 y',
    'float32 z',
    'z = (x - y) * (x - y)',
    'squared_diff')

x = cp.arange(10, dtype=np.float32).reshape(2, 5)
y = cp.arange(5, dtype=np.float32)
squared_diff(x, y)

Traceback (most recent call last):
  File "/home/.conda/envs/cupy/lib/python3.8/site-packages/cupy/cuda/compiler.py", line 512, in compile
    nvrtc.compileProgram(self.ptr, options)
  File "cupy_backends/cuda/libs/nvrtc.pyx", line 108, in cupy_backends.cuda.libs.nvrtc.compileProgram
  File "cupy_backends/cuda/libs/nvrtc.pyx", line 122, in cupy_backends.cuda.libs.nvrtc.compileProgram
  File "cupy_backends/cuda/libs/nvrtc.pyx", line 58, in cupy_backends.cuda.libs.nvrtc.check_status
cupy_backends.cuda.libs.nvrtc.NVRTCError: HIPRTC_ERROR_COMPILATION (6)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "111.py", line 10, in <module>
    x = cp.arange(10, dtype=np.float32).reshape(2, 5)
  File "/home/.conda/envs/cupy/lib/python3.8/site-packages/cupy/_creation/ranges.py", line 57, in arange
    _arange_ufunc(typ(start), typ(step), ret, dtype=dtype)
  File "cupy/core/_kernel.pyx", line 1084, in cupy.core._kernel.ufunc.__call__
  File "cupy/core/_kernel.pyx", line 1107, in cupy.core._kernel.ufunc._get_ufunc_kernel
  File "cupy/core/_kernel.pyx", line 881, in cupy.core._kernel._get_ufunc_kernel
  File "cupy/core/_kernel.pyx", line 60, in cupy.core._kernel._get_simple_elementwise_kernel
  File "cupy/core/core.pyx", line 1921, in cupy.core.core.compile_with_cache
  File "/home/.conda/envs/cupy/lib/python3.8/site-packages/cupy/cuda/compiler.py", line 324, in compile_with_cache
    return _compile_with_cache_hip(
  File "/home/.conda/envs/cupy/lib/python3.8/site-packages/cupy/cuda/compiler.py", line 662, in _compile_with_cache_hip
    binary = compile_using_nvrtc(source, options, arch, name + '.cu')
  File "/home/.conda/envs/cupy/lib/python3.8/site-packages/cupy/cuda/compiler.py", line 163, in compile_using_nvrtc
    return _compile(source, options, cu_path,
  File "/home/.conda/envs/cupy/lib/python3.8/site-packages/cupy/cuda/compiler.py", line 144, in _compile
    prog = _NVRTCProgram(source, cu_path,
  File "/home/.conda/envs/cupy/lib/python3.8/site-packages/cupy/cuda/compiler.py", line 523, in compile
    raise CompileException(log, self.src, self.name, options, 'nvrtc')
cupy.cuda.compiler.CompileException: /tmp/comgr-2f0b69/input/CompileSource:2:10: fatal error: 'cupy/complex.cuh' file not found
#include <cupy/complex.cuh>
         ^~~~~~~~~~~~~~~~~~
1 error generated when compiling for gfx906.
Error: Failed to compile opencl source (from CL or HIP source to LLVM IR).

I've already found that it's the hiprtcCompileProgram API in cupy/cupy_backends/cuda/libs/cupy_hiprtc.h that cause this problem and I have submitted an issue to the HIP project https://github.com/ROCm-Developer-Tools/HIP/issues/2182#issue-731199084.
I'm curious if anyone else encountered this problem.

Thanks for reporting. This is a known issue in ROCm that hipRTC does not recognize the -I option. However, a workaround has been made on our side to avoid this. May I ask how did you install your CuPy, which version/branch did you use, etc?

Notes:

The workaround to which I referred was added in #3823: https://github.com/cupy/cupy/blob/50361e0d42ca8e41e7200382c3031cfc4e201764/cupy/cuda/compiler.py#L613-L627
I just checked that this hipRTC bug is still present in ROCm 3.8.0
I can run @ipe-zhangyz's sample code locally on two different machines without problem. (One with Radeon VII (gfx906) + ROCm 3.5.0, the other with the same GPU + ROCm 3.8.0.)

Thank you @leofang ! The version I installed before is v8.0.0rc1.  I installed it on a server with CentOS 7.6 and ROCM 3.5 from source in this steps:
$ cd cupy
$ export HCC_AMDGPU_TARGET=gfx906
$ export __HIP_PLATFORM_HCC__
$ export CUPY_INSTALL_USE_HIP=1
$ export ROCM_HOME=/opt/rocm/rocm-3.5.0
$ pip install .

I've switched to v8.0.0 and reinstalled  it in the same steps. My test code can run now.

Thanks for confirming, @ipe-zhangyz. Yes, this was fixed between v8.0rc1 and v8.0, so you had the buggy version installed 😅

Hi @leofang , I find that you have done many tests of cupy on rocm platform. I also want to do a systematical test on my CentOS 7.6 + rocm 3.5 server, as the official supported OS of hip is usually ubuntu. Could you please tell me how do you do your tests? Did you use the code in the source code of cupy, or you write your own test codes? If it is the first case, is there any simple command to run all the test cases at once? Thank you！

The current CuPy test suite has a great coverage, some much more extensive than NVIDIA's internal ones that we were able to catch a dozen of CUDA bugs in the past. I'd say if you're super interested, running CuPy's tests locally (given that you already built from source) is the best. You can do it as simple as pytest tests/ to run them all!
However, I don't recommend you to do this for the moment. If you search my ID, you can see I've already found a bunch of ROCm bugs, and between I and PFN (the company behind CuPy) we have a much longer bug list not tracked on this issue tracker. Some bugs are serious enough that you would just get segfaults. The more severe issue is hipRTC is >5x slower than NVRTC, so unlike on NVIDIA GPUs we couldn't run the full tests within a reasonable amount of time on AMD GPUs. I'll be slowly working on this when I have time & hear more from AMD, but in the meanwhile I suggest the way to go is to first run your own applications written in CuPy, and see whether they like AMD GPUs or not. This is more reasonable than trying to make sure everything work at once...

Thanks for your advice! I just tried the cases on the cupy tutorial web page. Most of them work on my machine, however, I find that if the kernel in my source file includes some headers, like this:
import numpy as np
import cupy as cp

complex_kernel = cp.RawKernel(r'''
    #include <cupy/complex.cuh>
    extern "C" __global__
    void my_func(const complex<float>* x1, const complex<float>* x2,
                 complex<float>* y, float a) {
        int tid = blockDim.x * blockIdx.x + threadIdx.x;
        y[tid] = x1[tid] + a * x2[tid];
    }
    ''', 'my_func')

x1 = cp.arange(25, dtype=cp.complex64).reshape(5, 5)
x2 = 1j*cp.arange(25, dtype=cp.complex64).reshape(5, 5)
y = cp.zeros((5, 5), dtype=cp.complex64)
complex_kernel((5,), (5,), (x1, x2, y, cp.float32(2.0)))  # grid, block and arguments
print(y)

I will still encounter the hiprtc error for not found the header file. I can include the absolute path to the header, but if the header itself includes some other header files, the error still occurs. Is there any workaround for this problem?

For RawKernel and RawModule, you can set backend='nvcc' to make it use hipcc. It's probably a confusing name for ROCm users that we should change.

Thank you! @leofang Now all of my test cases are passed.


feat(kno-7174): add Expo SDK docs

Description
This PR updates the docs to include the Expo SDK added by knocklabs/javascript#243. I also updated the React Native push notifications guide to describe integrating push notifications using Firebase Cloud Messaging and React Native Firebase.
Tasks
KNO-7174
Screenshots

Thank you for adding the "💡 Using Expo?" callouts throughout the React Native pages! 🙌


Figure out "Release History" behavior of top ribbon routing based on current page

There is some weird routing issues on the top ribbon for the "Release History" link. When clicked on from the home page it works properly and routes to https://hivelab.tst.biochemistry.gwu.edu/biomarker-partnership/data/history_list.
If you click on it from the FAQ or About page the static/ gets left in the url and the /data/history_list just gets appended.

Fixed in the init.json.


Add jq example

Howdy, I came across your blog post when searching for "weird fzf tricks".
I occasionally find myself wanting to dive interactively into some json document using jq, and noticed you'd filed an issue for yourself to build something. Here's what I think will be useful for me:

Closing - old


Enabling BLAS for faster computation

The core routines (recursions) should use BLAS for faster execution. A good overview of how to improve processing speed is already given here:
https://www.benjaminjohnston.com.au/matmul

Enhancement ist quite low compared to nativ python. JIT is already faster
import numpy as np
import time
from scipy.linalg.blas import sgemm, sgemv
K = 100000
N = 5
A = np.random.random((N, N))*1e-6
AT = A.T
C = np.random.random((N,))
gamma = 0.9999
W = np.zeros((K, N, N))
CC = np.outer(C, C)

t0 = time.perf_counter()
for k in range(K-1):
    W[k+1] = gamma * AT @ W[k] @ A + CC
print(time.perf_counter()-t0)

A = np.copy(A, order='F')
AT = np.copy(AT, order='F')
C = np.copy(C, order='F')

gamma = 0.9999
W = np.zeros((K, N, N))
W_f = np.copy(np.zeros((K, N, N)), order='F')
CC = np.outer(C, C)
t0 = time.perf_counter()
for k in range(K-1):
    W_f[k+1] = sgemm(gamma, sgemm(1, AT,W_f[k]),A) + CC
print(time.perf_counter()-t0)

>>> 0.31028587500000004
>>> 0.20534937499999995


The view tries to draw before the dataview indices are loaded

Specifically, getFileFrontmatter tries to access app.plugins.plugins.dataview.api before it is done indexing

Issue from #10: Dataview indices aren't loaded by the time the BreadcrumbsView tries to populate

Obsidian version: 0.12.4
Breadcrumbs plugin: 0.2.1
Dataview: 0.3.13
My breadcrumb view is empty now. Tried clean reinstall of the plugin and also disabling and re-enabling the plugin.
Ther are some error logs (also, I noticed that the plugin says "loading plugin" instead of "loading Breadcrumbs plugin". This is what I get when I start Obsidian. I think it might be due to dataview not having populated its index yet. Don't think there's much that can be done until Dataview provides an API to check if indexing is done.

Current solution is just to setTimeout the first call of draw by about 4 seconds. This is hacky, but works to fix the bug. I'll close this once the dataview api-ready event is exposed


Impossible to resize maximized terminal panel

VSCode Version: 1.43.2
OS Version: Linux Mint

Steps to Reproduce:

Open terminal window
Maximize terminal window manually by dragging the resize helper to the top of the window.
Unable to resize terminal window back to a normal size because it's impossible to find the resize helper icon once the terminal window has been maximized.

This is made especially frustrating because the last size of your terminal is saved in your workspace. Meaning I can't simply restart the app to fix the problem. Meaning I'm stuck with a maximum-height terminal window in this project until I can find a workaround, making VSCode almost unusable.
I tried deleting everything in ~/.config/code/Local Storage but that didn't work. I tried window.localStorage.clear() in developer console but that didn't work. I tried >Clear editor history in the editor command prompt and that didn't work either. Short of creating an entirely new project and copying all my code over to that, I'm unsure what to do to work around this issue.
I'm updating to say I went ahead and copied the folder. It was a pretty large project but my OS is pretty quick so it didn't take too long. But that's the only workaround I know of if someone accidentally does this!
Although I've learned my lesson, this is a very bad UX, especially if you have a slower machine, so I'm writing this in hopes that the team can improve the resizing functionality of the terminal window in a future release. Thanks all.

Does this issue occur when all extensions are disabled?: Yes

Works for me:

There's the drag near the title bar and also the button. Maybe the dragger doesn't work when you're using native title bar?

Maybe the dragger doesn't work when you're using native title bar?

Yea that seems to be it. Bringing in @joaomoreno since this is similar to the sidebar in full screen situation.

@sbatten I can't seem to find the duplicate... Can you find it and add the grid-view tag to it?

found it https://github.com/microsoft/vscode/issues/92709


CGLib proxy of spring-boot 2 is not supported

Hi!
Great library, I've been using 2.5.0 with spring-boot 2.1.7 and the jdbc lock provider and the following setup:
@EnableScheduling
@EnableSchedulerLock(defaultLockAtMostFor = "PT12H", defaultLockAtLeastFor = "PT10S", mode = InterceptMode.PROXY_METHOD)

I'm encountering the following error:
[...]
Caused by: org.springframework.beans.factory.BeanNotOfRequiredTypeException: Bean named 'publishIntakeCheckJob' is expected to be of type 'com.bol.amnesia.jobs.PublishIntakeCheckJob' but was actually of type 'com.sun.proxy.$Proxy207'
[...]

The offending line is:
    @Autowired PublishIntakeCheckJob publishIntakeCheckJob;

which goes like this:
public class PublishIntakeCheckJob implements ScheduledJob {
[...]
    @Scheduled(cron = "${intake.cron}")
    @SchedulerLock(name = JOB_NAME)
    public void execute() {}
[...]
}

If I change the wiring of the publishIntakeCheckJob:
    @Autowired ScheduledJob publishIntakeCheckJob;

it works.
Looking at the source code, it seems that only supports jdk proxies. Since spring-boot 2, the default proxy method is cglib, for the exact reason that jdk proxies would implement the interface of the bean only, even if said interface is only used as a trait, not an old-OO-style interface.
See AopAutoConfiguration in spring-boot 2 for more details.
Is it possible to add some cglib support? As it stands, I'll have to add an aspect myself that would call the locks manually, which makes this nice lean library more painful to use.

Yes, I have been thinking about it. Will try to implement it in next few weeks. In the meantime, you can try this https://github.com/lukas-krecan/ShedLock#scheduled-method-proxy

Will add new config option PROXY_SCHEDULER_CGLIB. Will make it default option after it's tested in the field for a while.

Hey, thanks for picking it up so fast!

Released as 3.0.0, should take settings from Spring Boot, so no manual configuration is necessary


sirepo: update oauth and beaker_session config

Need to make compatible with latest code.

Tested backward compatibility on alpha.


Line with Focus Chart is not working in IE9 with version 1.0.9.

I have open https://krispo.github.io/angular-nvd3/#/lineWithFocusChart in IE9 and chart does not work. (i choose version 1.0.9). If I choose version 0.1.1 everything works.
Could you please provide a hot fix or tell me the latest version which I can choose.

Finally, I have found solution:
versions need to be changed:
d3 - 3.5.17
nvd3 - 1.8.4
On your website you use version
d3 - "3.5.5"
nvd3 - 1.8.3


Update Makefile to build kopia image b9be9632a27751860c870732a74b076c2cd9d42a

Change Overview
This PR updates kopia commit in Makefile to https://github.com/kopia/kopia/commit/b9be9632a27751860c870732a74b076c2cd9d42a. This will push the image and can be used in kanister-tools image.
Pull request type
Please check the type of change your PR introduces:

[ ] :construction: Work in Progress
[ ] :rainbow: Refactoring (no functional changes, no api changes)
[ ] :hamster: Trivial/Minor
[ ] :bug: Bugfix
[ ] :sunflower: Feature
[ ] :world_map: Documentation
[ ] :robot: Test

Issues

fixes #issue-number

Test Plan

[ ] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

@pavannd1 We need to update kopia dependency to a version which supports repository upgrade. This commit contains minimum changes, but we can upgrade to v0.12.1 since it's the new released version.


Adds migrations to create user-group and add section to admin group

This implements a solution for issue #16.
I've added 2 migrations, one for adding the SEO section to the "admin" user-group, and the second to create a separate user-group (for granular SEO user access).
@patrickdemooij9 If you don't want the "admin" group to have the SEO section, I can either update the PR, or feel free to change the code as you want it.

Looks great! Did find one issue when the user already has a user group with the exact name alias (which probably doesn't happen too often, but good to catch) it'll throw an error on startup.
I made the changes in this commit: https://github.com/patrickdemooij9/uSeoToolkit.Umbraco/commit/843e2e06de27f18dd8a9674046ab3c97b40904e5, but I have no idea how to actually update this PR 😅

Good point! 👍
I've rebased this PR on your pr/23 branch - so it has your latest changes now.

Perfect! Then all is good to go! Thanks

Awesome, thanks @patrickdemooij9!


UDP sends incorrect time

During the IOTA contest, I connected N1MM do WavelogGate via UDP. The logs posted on WaveLog side is incorrect time (few hours in the past)

Hello @spREGR
Sorry for the delay. I have some more questions

If you try to reproduce the issue now, does it still persist?
Which timezone is set on your computer?
Which timezone is set on N1MM?
Which timezone is set on Wavelog?

I never saw this issue before and it's probably just a settings issue between these three endpoints.

Sorry, I was travelling and couldn't conduct the tests
If you try to reproduce the issue now, does it still persist? ==> Yes, current time is 22:30 UTC and Wavelog recorded 17:00 UTC via UDP
Which timezone is set on your computer? UTC +5:30
Which timezone is set on N1MM? UTC
Which timezone is set on Wavelog? UTC

Okay I was able to reproduce this issue.
N1MM does export a QSO not as ADIF but as XML
Therefore it does not have the ADIF specific tags date_on or time_on but a timestamp tag which does not correctly get parsed in WLgate

I will take a look with @int2001 about this. In the meantime you can workaround this by setting the timezone of your computer to UTC aswell.


Add pagination_mode to tweepy.models.User.followers and friends

Right now we are able to cursor using
tweepy.Cursor(api.friends)
tweepy.Cursor(api.followers)

But if we have a user instance
u = api.get_user('rogeliorv')
tweepy.Cursor(u.friends)  # Does not work
tweepy.Cursor(u.followers) # Does not work

We get:
TweepError: This method does not perform pagination

We should be to benefit from the already implemented Cursor class.
This is fixed easily by adding
friends.pagination_mode = 'cursor'
followers.pagination_mode = 'cursor'

in tweepy.models.User after the method declarations.

you do not need to use
tweepy.Cursor(u.friends)  # Does not work
tweepy.Cursor(u.followers) # Does not work
insteed use only:
print(u.friends)
print(u.followers_count)


Add repository generation via cookiecutter

Fix use of optional dependencies
Improve documentation
Don't raise if there are no dependencies
Revert "Use sets for config paths and sessions"
Deduplicate config paths
Add cookiecutter template to generate repositories

Demo:

Ready for the final review. Enabling auto-merge.


Add documentation and limit number of expressions in unsafe block for RawMutex

Try to move not unsafe stuff out of large unsafe blocks. And keep only the unsafe call at the end in that block. Documenting the safety contract to think about in said call.
Document what the bits in RawMutex::state, and what all combinations of that state, means. Please verify the descriptions are correct, since you know all edge cases much better than me :)
Clippy complained about #[inline] on function with no body. The corresponding actual implementations still have #[inline]
Clippy complained about two unsafe functions with docs, but without a # Safety section. So I took what looked like the safety notes of those functions and formatted them according to the standard.

Travis issue on OSX, so I'm just going to merge manually.


distinguishing the key words in batch scheduler

from normal text used

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

/lgtm


popup alert

is there any way to add an alert function to the extension?
so if a key is found it should display the data in popup alert on the browser
Thank You

You could use this branch with Chrome,
https://github.com/nilaoda/widevine-l3-guesser/tree/modified

please dont use this

You could use this branch with Chrome.
https://codeload.github.com/nilaoda/widevine-l3-guesser/zip/refs/heads/modified
https://github.com/nilaoda/widevine-l3-guesser/tree/modified

NOTE - DONT USE THIS FORK, IT HAVE VIRUS

@amitalokbera Which virus? Could you explain more please?
https://www.virustotal.com/gui/file/9cbffe806c26bdb57392cd474cf1f559c44837e2663f98390aa757ef03995b39/detection

then why does that fork library size is 200mb whereas the original one is only 11mb

@amitalokbera This PR will help you to modify the extension for getting the popup alert.
https://github.com/Satsuoni/widevine-l3-guesser/pull/3/commits/56ad38500d23210ae51fc577b3852824b1dda095

No it doesn't or it's just a false flag ...

Just replace console.log with alert? Or use one of the forks that use alerts, prompts, etc? Or read Issue #1 for my stance on various matters?


Adds missing test for dropdown in navbar

see https://github.com/twbs/bootstrap/pull/33643#issuecomment-820412591

I see it is not specific to the dropdown inside the navbar only. :thinking:

It's actually not working as intended because the event doesn't reach the clearMenus method for some reason.


Fixed lint targets

When we moved from vanilla JS to React, it looks like we never updated our lint rules to cover other files. In this PR:

Corrected lint rules to lint every JS file in app/

/cc @wlaurance

I almost forgot. @justinnichols could you take a look at this PR?

I applied it manually at your suggestion to help fix my lint errors for #136 and it worked perfectly for me.

Going to take that as a ":+1:/Looks good to me" =P. Landing this PR.


Why not using angle project?

I was thinking about using Angle project for my personal project, why bgfx does not use angle?
I saw that shader language is more GLSL like than HLSL, terms are more like OpenGL, uniform etc.
There is also a WinRT port and probably same code can be taken on Xbox One.
What do you think about?
Thanks

In this test https://github.com/bkaradzic/bgfx/blob/master/README.md#60hz, you can see how it performs with just adding ANGLE DLL to bgfx (with ANGLE bgfx can issue draw ~5 times less draw calls and maintain 60Hz):

CPU
Renderer
GPU
Arch/Compiler/OS
Dim
Calls

i7-920 2.66
GL2.1
GTX650Ti
x64/VS2008/Win 7
38
54872

i7-920 2.66
NV 331.113
GTX650Ti
x64/GCC/Linux
34
39304

i7-920 2.66
DX9
GTX650Ti
x64/GCC/Win 7
32
32768

i7-920 2.66
DX9
GTX650Ti
x86/VS2008/Win 7
30
27000

i7-920 2.66
DX9-Wine
GTX650Ti
x64/GCC/Linux
24
13824

i7-920 2.66
ES2-ANGLE
GTX650Ti
x86/VS2008/Win 7
21
9261

i7-920 2.66
ES2-PowerVR
GTX650Ti
x86/VS2008/Win 7
18
5832

i7-920 2.66
FF27-GL
GTX650Ti
JIT/Clang/W7-asm.js
17
4913

i7-920 2.66
ES2-Qualcomm
GTX650Ti
x86/VS2008/Win 7
15
3375

i7-920 2.66
ES2
GTX650Ti
x64/GCC/NaCl 31
15
3375

i7-920 2.66
ES2
GTX650Ti
JIT/Clang/PNaCl 31
15
3375

i7-920 2.66
FF27-ANGLE
GTX650Ti
JIT/Clang/W7-asm.js
12
2744

i7-920 2.66
ES2-Mali
GTX650Ti
x86/VS2008/Windows7
6
216


Request for metadata on the event_time column

Hi there!
Thank you for the amazing library and for sharing it openly!
I gave it a try on running cell-by-cell code from the dichotomic_pattern_mining.ipynb file using the same dataset from Requena (2020). By referring to the sample_data.csv used in the mentioned .ipynb file, do you mind elaborate more on the metadata of the column event_time, for example, the unit (is it in seconds, milliseconds, or in other form?).
You also mentioned that the event_time column (as well as the other columns) is extracted from the original dataset. I am assuming that the event_time column is constructed from the column server_timestamp_epoch_ms which we can also get from the original dataset. If so, do you mind sharing how the process of constructing the event_time was done?
Looking forward to hear from you. Thanks!

Thanks @dinaamir for your interests to the library!
The event_time is in milliseconds. So it shows the time that a user spent on each visit in event_sequence, mostly a few tens of seconds.
We extracted event_time by calculating the time elapsed in the consecutive timestamps, e.g. event_time_1 = timestamp_2 - timestamp_1. The last event time in a sequence can't be estimated in this way, so we used median of the preceding event times in that sequence.


stabilization release - fix issues that were causing forks and crashes

Multiple fixes to try to stop my nodes from crashing, see #119

@sashimi-houdini this is ready for production... I recommend releasing ASAP along with #113 & #123 to stabilize the network and allow new nodes to join in.

@sashimi-houdini This is really final now... I've started work on a new PR.

This PR has become obsolete due to other changes I've started working on. I'm flipping this back to Draft to minimize change history churn and avoid double-review in some areas.

this has now been broken up into smaller PRs


Skip gas estimation in tests [wip]

By default web3 uses binary searching to determine the gas usage of a transaction.  This slows down the CI tests a lot.  This PR tries to remove that.  The approach follows #794.  Currently I'm trying to fix the tests.
Moreover, when I expect .transact() to success, I should start using call_and_transact() function,.  .transact() no longer raises TransactionFailed when the transaction fails.

I'm seeing an interesting error.
__________________________________________________________________ test_channel_settle_old_balance_proof_values[one_old-channel_test_values0] ___________________________________________________________________
[gw1] linux -- Python 3.6.7 /home/yoichi/src/raiden-contracts/venv/bin/python3.6

web3 = <web3.main.Web3 object at 0x7f40bbb2fd30>, get_accounts = <function get_accounts.<locals>.get at 0x7f40bbaa8ea0>, assign_tokens = <function assign_tokens.<locals>.get at 0x7f40bb79c2f0>
channel_test_values = {'last_old': [ChannelValues deposit:40 withdrawn:10 transferred:20020 claimable_locked:4 unclaimable_locked:2 locked:6...ed:6 locksroot:b'\xfd\x83J\xc46\x7f\xc2\xba\x17\x9eY\xc6b\xa2\x11\xd6 \xdb.\x8eZa~7\x15\xd1\x97\xb5\x83\x1b\xc4\x87' )}
create_channel_and_deposit = <function create_channel_and_deposit.<locals>.get at 0x7f40bb79c7b8>, test_settlement_outcome = <function test_settlement_outcome.<locals>.f at 0x7f40bb79cbf8>
tested_range = 'one_old'

    @pytest.mark.slow
    @pytest.mark.parametrize('channel_test_values', channel_settle_test_values)
    @pytest.mark.parametrize('tested_range', ('one_old', 'both_old_1', 'both_old_2'))
    # This test is split in three so it does not time out on travis
    def test_channel_settle_old_balance_proof_values(
            web3,
            get_accounts,
            assign_tokens,
            channel_test_values,
            create_channel_and_deposit,
            test_settlement_outcome,
            tested_range,
    ):
        """ Test the settlement implementation when both/one of the balance proofs are outdated """
        (A, B, C, D) = get_accounts(4)
        (vals_A0, vals_B0) = channel_test_values['valid_last']
        assert are_balance_proofs_valid(vals_A0, vals_B0)
        assert not is_balance_proof_old(vals_A0, vals_B0)

        # Mint additional tokens for participants
        assign_tokens(A, 400)
        assign_tokens(B, 200)
        # We make sure the contract has more tokens than A, B will deposit
        create_channel_and_deposit(C, D, 40, 60)

        # Calculate how much A and B should receive while not knowing who will receive the
        # locked amounts
        expected_settlement0 = get_settlement_amounts(vals_A0, vals_B0)
        # Calculate how much A and B receive according to onchain computation
        expected_settlement_onchain0 = get_onchain_settlement_amounts(vals_A0, vals_B0)

        # Calculate the final expected balances after the channel lifecycle, (after settlement and
        # unlocks), when we know how the locked amounts will be distributed.
        # This is a very important check. This must be true for the last known balance proofs,
        # but also for a last known balance proof + an old balance proof provided on purpose or not.

The CI finishes in 14 minutes.  Much faster.


Microsoft Answers?

Will this also replace Microsoft Answers too or just MSDN/TechNet?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5be114f3-6668-8b9d-b698-a088050edd1e
Version Independent ID: 360c7943-63c3-72b8-ddbe-b275f86793ba
Content: Introducing Microsoft Q&A (Preview)
Content Source: teamblog/introducing-microsoft-qanda.md
Product: team-blog
GitHub Login: @saldana
Microsoft Alias: saldana

@bgiesing The current scope is to move customers from MSDN and TechNet forums to Microsoft Q&A. the scope for Answers remains as-is today. We will look at ways to consolidate and share content between the different sites.


Vulkan: Occlusion culling incorrectly culls objects which are not completely occluded

Godot version
v4.0.beta9.official
System information
Windows 10, Vulkan, GeForce GTX 1070 driver ver. 512.15
Issue description
A large object being occluded by another large object will be incorrectly culled with occlusion culling when viewed almost off screen. I would expect that the object be fully occluded before being culled.
This seems to not happen so long as the face of the occluder that is perpendicular to the object being occluded is not visible. The face colored red below is what I am referring to.
The issue also seems to only happen when the objects cover the whole screen, though this is not entirely the case for the second video I've provided.

Here is a video from a test project:
https://user-images.githubusercontent.com/94566175/209424410-57278a7d-6d34-4346-b6c3-fb0bc4de7313.mp4
Here is a video from a personal project where I first noticed the issue:
https://user-images.githubusercontent.com/94566175/209424430-34b225e1-7007-4f0e-af46-86df5bdd32a2.mp4
Steps to reproduce
Create two large cube meshes slightly offset from one another
Create Occluder Instance 3D and bake
Approach one of objects closely such that it partially covers the other object
Slowly move or rotate camera to occlude the other object
The object being occluded will (sometimes) be culled before it should be
Minimal reproduction project
Test.zip

Can you reproduce it on 3.x?

I tried this on 3.5.1 stable using an occluder shape and a similar setup; however I could not reproduce it. Forgive me if I am missing something here, I never used occlusion culling in 3.x and I'm not entirely sure if I've set it up here to work as needed.
https://user-images.githubusercontent.com/94566175/209425509-359e5c94-05fa-4e7f-8080-9b297e5419ea.mp4

I can also confirm this is still an issue in 4.0 beta 10.

Related to https://github.com/godotengine/godot/issues/63771.

Duplicate of https://github.com/godotengine/godot/issues/53288. Closing in favour of https://github.com/godotengine/godot/issues/53288 so we can track this issue in only one place


Vagabond in Tie Striker ability not working

Fly Casual Release Version
Version 2.5 - 2.5.20240906.01
Online Game Mode
No
Describe the bug
Vagabond in the Tie Striker's ability is to drop a device after using the adaptive ailerons. However, after the aileron maneuver, there is no choice to drop a device, instead, the dial maneuver is immediately performed
To Reproduce
Load out Vagabond with a device/bomb.
Perform the aileron maneuver
Expected behavior
After perforrning the aileron maneuver, expect to see a prompt to drop a device or skip.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform/Device (please complete the following information):

OS: Android
Version [e.g. Windows 10, iOS22] - not sure, tablet is at home

Additional context
Add any other context about the problem here.

The pilot ability was there and "worked" but never linked correctly to Vagabond. Commit 81caa25.


Clarify why to use this image

What is this image good for in comparison with other images like official python?
Official image is well maintained (with autobuild) and offers great selection of tags (versions).
What offers this image?

@iBobik The official python docker images are for Intel/AMD CPU's only. This rpi-python image is for ARM CPU's like the one on a Raspberry Pi and similar boards.
Where do you have missed this information as it is both in the README here in this repo as well as in the description at Docker Hub. So we could improve this.

There is just:

Raspberry Pi compatible Docker base image with Python preinstalled.

It don't mention official Python image will not work on RPi (and other ARM machines), so I did not saw reason why not use it.
Jan Pobořil
http://honza.poboril.cz/

2016 v 21:03, Stefan Scherer<EMAIL_ADDRESS>

@iBobik The official python docker images are for Intel/AMD CPU's only. This rpi-python image is for ARM CPU's like the one on a Raspberry Pi and similar boards.
Where do you have missed this information as it is both in the README here in this repo as well as in the description at Docker Hub. So we could improve this.
—
Reply to this email directly or view it on GitHub.


Exception has occcurred: IndexError

Exception has occurred: IndexError
list index out of range
pypreprocessor.parse()
What does this exception mean?
I created several lists (this one has  about 300 entries) and used #defines to shorten them a bit if necessary.
Some lists contain more than 600 elements and there is no complication at all.

The error seems to occur at an #else directive
self._ifblocks[-1] = not self._if(blocks[-1] ( ~line 170) in the pypreprocessor source file
What could be the error?

that would mean you have more #else than active #if blocks?


[BUG] setuptools fails on 'pytz (>dev)' with 'Expected closing RIGHT_PARENTHESIS'

setuptools version
setuptools==67.0
Python version
Python 3.11 and others
OS
Fedora Linux
Additional environment information
No response
Description
Installing Kallithea as described on https://kallithea.readthedocs.io/en/default/contributing.html#getting-started works fine when only upgrading setuptools to < 67 .
With 67 or later, it fails as
$ gearbox serve -c my.ini --reload
15:56:54,111 ERROR [gearbox] Expected closing RIGHT_PARENTHESIS
    pytz (>dev)
         ~^

The error seems to come from the vendered packaging, when stumbling upon venv/lib/python3.11/site-packages/celery-5.0.5.dist-info/METADATA with Requires-Dist: pytz (>dev). It might be an issue in celery, and it might already be fixed in later celery versions, but it is still a regression in setuptools.
Expected behavior
I expect it to work with setuptools 67 as it does with setuptools 66.
How to Reproduce
hg clone https://kallithea-scm.org/repos/kallithea
cd kallithea
python3 -m venv venv
. venv/bin/activate
pip install --upgrade pip setuptools
pip install --upgrade -e . -r dev_requirements.txt python-ldap python-pam
kallithea-cli config-create my.ini

Output
...
  File "/tmp/kallithea/venv/lib64/python3.11/site-packages/celery/bin/celery.py", line 11, in <module>
    from pkg_resources import iter_entry_points
  File "/tmp/kallithea/venv/lib64/python3.11/site-packages/pkg_resources/__init__.py", line 3323, in <module>
    @_call_aside
     ^^^^^^^^^^^
  File "/tmp/kallithea/venv/lib64/python3.11/site-packages/pkg_resources/__init__.py", line 3298, in _call_aside
    f(*args, **kwargs)
  File "/tmp/kallithea/venv/lib64/python3.11/site-packages/pkg_resources/__init__.py", line 3336, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/tmp/kallithea/venv/lib64/python3.11/site-packages/pkg_resources/__init__.py", line 629, in _build_master
    ws.require(__requires__)
  File "/tmp/kallithea/venv/lib64/python3.11/site-packages/pkg_resources/__init__.py", line 966, in require
    needed = self.resolve(parse_requirements(requirements))
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/tmp/kallithea/venv/lib64/python3.11/site-packages/pkg_resources/__init__.py", line 832, in resolve
    new_requirements = dist.requires(req.extras)[::-1]
                       ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/tmp/kallithea/venv/lib64/python3.11/site-packages/pkg_resources/__init__.py", line 2821, in requires
    dm = self._dep_map
         ^^^^^^^^^^^^^
  File "/tmp/kallithea/venv/lib64/python3.11/site-packages/pkg_resources/__init__.py", line 3107, in _dep_map
    self.__dep_map = self._compute_dependencies()
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/tmp/kallithea/venv/lib64/python3.11/site-packages/pkg_resources/__init__.py", line 3117, in _compute_dependencies
    reqs.extend(parse_requirements(req))
  File "/tmp/kallithea/venv/lib64/python3.11/site-packages/pkg_resources/__init__.py", line 3170, in __init__
    super(Requirement, self).__init__(requirement_string)
  File "/tmp/kallithea/venv/lib64/python3.11/site-packages/pkg_resources/_vendor/packaging/requirements.py", line 37, in __init__
    raise InvalidRequirement(str(e)) from e
pkg_resources.extern.packaging.requirements.InvalidRequirement: Expected closing RIGHT_PARENTHESIS
    pytz (>dev)
         ~^

Hi @kiilerix, pytz (>dev) is not a valid dependency specifier according to PEP 508/PEP 440. The error seems to come specifically from the version dev (which is not a valid version for a Python package). A valid version would look something like 0.dev1.
Previous versions of setuptools used to emit a deprecation warning about this.
After some years of announcing this deprecation, setuptools removed support for malformed dependency specifiers[^1].
I don't think there is an action point to be followed here.
[^1]: Setuptools relies on pypa/packaging for parsing dependencies and recent versions of pypa/packaging no longer support this kind of specifiers.

It is however a regression for my use case. But ok, fair if enough if it is a deliberate or acceptable regression in a "garbage in" undefined behaviour. I can't update the celery dependency on my stable branch, so I guess I will have to add a constraint on setuptools<67.

Thanks @kiilerix. I will close this issue for now.

If it helps, Celery fixed its dependency metadata as of Celery 5.2.1, in:
https://github.com/celery/celery/pull/7074


Github actions not working

Hello,
the Github actions for "Preview on PR" and "Publish on Merge" do not work for me. I have forked this repository and changed an alias on one of the dashboards to test the Github actions. Neither of them worked. I got the following error messages.
Preview on PR:

Publish on Merge:

For full logs see: https://github.com/Sarabor/grafana-dashboards/actions
I have only changed the grafana-url in the files in \grafana-dashboards.github\workflows.
Are there any more changes I need to make to use the Github actions?

have the same problem 😷


Add type validation and null checking to all model object init methods to prevent crashes

Hey @shyambhat, thanks for creating this library. Our production app recently experienced a spike in crashes (as noted in issue #90) due to improper null-checking. After investigating, I noticed two serious issues:

Inconsistent checking for NSNull when creating model objects
No type checking when dealing with objects pulled from NSDictionary

As a result, if Instagram changes their API or is experiencing any technical issues (eg: sending back null for a property that isn't expecting null), any applications using InstagramKit will crash. This pull request does the following:
1. Removes dependence on the IKNotNull macro during model object creation.
2. Implements a new NSDictionary+IKValidation category that null-checks every value returned from the Instagram API and also checks that the type of each object is of the expected type
Now, if the InstagramAPI changes and/or experiences bugs, applications using InstagramKit won't crash.
Let me know if you have questions. Thanks!

This is good,builds on #90 and makes it much more resilient to mistakes that Instagram Devs might make to return nil values in their API responses.  @shyambhat Please accept PR :)

@scalessec thanks a ton for your PR and sorry I took this long to act on it.
I've worked on a separate branch to address these issues. To me, adding a category to NSDictionary made the code look more complex and sightly unreadable.
I experimented with adding additional checks in the macros and made sure every key was null checked and type checked and also returns default empty values to avoid crashes.
I'm not too sure I'm in the right direction, though.
@scalessec @joelbyler @dezinezync could you spare a few minutes to review my pull request #111

@scalessec thanks a ton for your PR and sorry I took this long to act on it.
I've worked on a separate branch to address these issues. To me, adding a category to NSDictionary made the code look more complex and sightly unreadable.
I experimented with adding additional checks in the macros and made sure every key was null checked and type checked and also returns default empty values to avoid crashes.
I'm not too sure I'm in the right direction, though.
@scalessec @joelbyler @dezinezync could you spare a few minutes to review my pull request #111


Standard value set LeadStatus in conflict with SObject.

If any Apex code contains LeadStatus SObject than it's not possible to deploy LeadStatus apex constants for its standard value set. Currently, this value set is ignored automatically.

The LeadStatus will now generate class with the name 'LeadStatus2'.


implement flutter format

fixes https://github.com/flutter/flutter/issues/5338
@devoncarew

lgtm

FYI @Hixie


Is there tutorial about texture?

I install the texture,it's clean,and light.
I wonder that if there is a tutorial about texture?like,how to add math formula?

Support for adding math formulas will be added soon. However there is no tutorial yet. We will work on better documentation in the coming months.


v2: column "row_id" does not exist

I think this is a bug, but I might be doing something wrong,
I've got a server running withclassIds: true
When I try and query for a record by id ( the postgresql table id  )
query Q {
  allProjects(condition: {rowId: 135}) {
    nodes {
     name
    }
  }
}

I get
{
  "data": {
    "allProjects": null
  },
  "errors": [
    {
      "message": "column \"row_id\" does not exist",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ]
    }
  ]
}

( Using id doesn't work either, which isn't surprising as I can see its not available in the ProjectCondition object )

Thanks for reporting 👍

Fixed in<EMAIL_ADDRESS>This is a consequence of how conditions are currently implemented, to fix it I used a quick hack because I intend to improve conditions soonish. There are tests though so we should never regress back to this faulty functionality :+1:


Create joss.md

Adding this org to map

Hey @RichardLitt
I'm starting this pull request from scratch again.


Generated Backend

This pr does the following

updates the old backend to a new generated backend

this will make maintance much easier

adds a tool (scripts/amd/gen_hip_backend.py) used to generate the backend

the tool is based on the parsing lib tree-sitter
it parses the c++, python, cmake and tablgen files in this fork and modifies them to be used for the backend
the modifications involve altering Macros (defines, includes), imports, types, functions, namespaces, strings.

adds a github actions tests for both upstream testing and fork testing

in the future this will allows us to move away from jenkins
fork test

is the same as the jenkins ci

upstream test

clones the upstream
checkouts it out to the last shared commit with upstream
applies a patch
checks out this branch as a backend
builds
runs unit tests

when reviewing you can ignore python/third_party/hip/gen. It is the generated files from the rest of the fork. If the upstream test works It should be fine.

https://github.com/ROCmSoftwarePlatform/triton/blob/3538df7d4cddbc0770c52bffef17e25ad68792e4/python/triton/third_party/hip/hip_backend.py#L580
It cannot hard coded to 64 since Navi31 has wave size 32. The PR for dynamic warp size is at:
https://github.com/ROCmSoftwarePlatform/triton/pull/244

moveing the work on the ci to #455. Generating the backend might not be needed.


how can i download files inside a webview flutter

I want to add download support to my webview in flutter. and for that i just want a webview.setdownloadlistner alternative for flutter dart.

Duplicate of https://github.com/flutter/flutter/issues/39321


View transition support

Thanks for amazing project. I also hate file based routing and I really like elegua router. Is there any plan to add support for view transitions?

Glad you like it. What do you mean by "view transitions"? Could you be more specific? Do you mean the new, experimental  View Transitions API ?

Yes I mean the new experimental view transitions API.  Sveltekit has an open PR and Astro also has a support for view transitions.

Except if I'm missing something, that API was made to fix the animation's problem in non-SPA applications where app state is lost between navigation. In svelte/SPAs, including Elegua, you can just use plain svelte animations and it should work out of the box. So I don't see the need in implementing support for non-SPA animations in a SPA router.
Let me know if that makes sense.

Closing as per lack of reply. Feel free to reopen.


Emit errors when kube-aws sees unexpected keys in cluster.yaml

Resolves #404

Codecov Report

Merging #425 into master will increase coverage by 0.15%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #425      +/-   ##
==========================================
+ Coverage   40.03%   40.19%   +0.15%
==========================================
  Files          33       34       +1
  Lines        2515     2525      +10
==========================================
+ Hits         1007     1015       +8
- Misses       1372     1373       +1
- Partials      136      137       +1

Impacted Files
Coverage Δ

model/spot_fleet.go
0% <ø> (ø)
:arrow_up:

model/controller.go
0% <ø> (ø)
:arrow_up:

model/etcd.go
0% <ø> (ø)
:arrow_up:

model/asg.go
0% <ø> (ø)
:arrow_up:

model/node_pool_config.go
19.44% <ø> (ø)
:arrow_up:

model/unknown_keys.go
100% <100%> (ø)

core/controlplane/config/config.go
64.86% <100%> (-0.32%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 04ea55b...86380e0. Read the comment docs.

This doesn't cover e.g. subnets, worker.nodePools[].subnets, worker.nodePools[].spotFleet.launchConfiguration[].
However, believing it is much better than nothing, I'd like to set this as the starting point 😃


Stream FTX : Checksum is not correct!

Hi,
I try the stream with FTX (code is like the example) and this part cause an issue : Checksum is not correct!
class FtxStreamingAdapters
            if (!calculatedChecksum.equals(message.getChecksum())) {
              throw new RuntimeException("Checksum is not correct!");
            }

If i comment this lines (88/89/90), it's worked. I receive the orderbook.

what is the issue? Can you please send the stacktrace. Thanks

What is the issue? Can you please send the stacktrace? Thanks

This happens after an unsubscribe message send and then trying to reconnect. I am investigating right now. If anyone knows about  the internal mechanism of NettyStreamingService please add any comment on this issue . Thanks

Hi @makarid,
I comment the checksum part to work, and i don't understand if the current code (xchange) match with the FTX Documentation.
Did you worked with this stream orderbook and FTX?
Because, the stream always add values on my orderbook. And the init doesn't work for me.
https://docs.ftx.com/#orderbooks
Initial snapshot
Upon subscribing, you will receive one snapshot of the orderbook (partial) with a data field containing:

looks like empty for me. But after i receive updates.

Updates
After receiving your snapshot, you will be streamed updates (message type is update) that have data fields with:

with the update i try to update my local orderbook, but the size is growing

Part of my code for example.
`
	Exchange exchangeFTX = ExchangeFactory.INSTANCE.createExchange(FtxExchange.class);
	FtxMarketDataService marketDataService = (FtxMarketDataService) exchangeFTX.getMarketDataService();
	try {
		orderBook = marketDataService.getOrderBook(CurrencyPair.BTC_USD);

	} catch (IOException e) {
		e.printStackTrace();
	}

	FtxStreamingExchange exchange = (FtxStreamingExchange) StreamingExchangeFactory.INSTANCE.createExchange(FtxStreamingExchange.class); // FtxStreamingExchange.class
	 exchange
        .connect(
            ProductSubscription.create()
                .addOrderbook(CurrencyPair.BTC_USD)
                .build())
        .blockingAwait();

	Disposable subscription2 = exchange.getStreamingMarketDataService()
	    .getOrderBook(CurrencyPair.BTC_USD)
	    .subscribe(
	    		orderBookUpdate -> {
	    			if (orderBookUpdate.getBids().size() > 0 && orderBookUpdate.getAsks().size() > 0) {

	    				for (LimitOrder limitOrder : orderBookUpdate.getAsks()) {
		    				 OrderBookUpdate update = new OrderBookUpdate(OrderType.ASK, limitOrder.getOriginalAmount(), limitOrder.getInstrument(), limitOrder.getLimitPrice(), orderBookUpdate.getTimeStamp(), limitOrder.getOriginalAmount());
		    				 orderBook.update(update);
	    				}

	    				for (LimitOrder limitOrder : orderBookUpdate.getBids()) {
		    				 OrderBookUpdate update = new OrderBookUpdate(OrderType.BID, limitOrder.getOriginalAmount(), limitOrder.getInstrument(), limitOrder.getLimitPrice(), orderBookUpdate.getTimeStamp(), limitOrder.getOriginalAmount());
		    				 orderBook.update(update);
	    				}

	    			}
	    		},
				throwable -> LOGGER.error("Error in trade subscription", throwable)
	);

`

I think you are doing it wrong. No need to update your local orderbook like this. You just need to tell that:
youLocalOrderbook = streamingOrderbook;

Indeed, the most basic example fails with a checksum error:
      var x = StreamingExchangeFactory.INSTANCE.createExchange(FtxStreamingExchange.class);
      x.connect().blockingAwait();
      x.getStreamingMarketDataService().getOrderBook(CurrencyPair.BTC_USD)
              .subscribe(book -> System.out.println(book.getTimeStamp()));

Thank you for your message! I am looking forward to make it much better,
please feel free to give any advice how to implement it. Thanks
On Sun, Apr 25, 2021, 1:02 PM Viktor Szathmáry @.***>
wrote:

Indeed, the most basic example fails with a checksum error:
  var x = StreamingExchangeFactory.INSTANCE.createExchange(FtxStreamingExchange.class);
  x.connect().blockingAwait();
  x.getStreamingMarketDataService().getOrderBook(CurrencyPair.BTC_USD)
          .subscribe(book -> System.out.println(book.getTimeStamp()));

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/knowm/XChange/issues/4014#issuecomment-826295876, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AHIWQ735DW4Y63XRKPE2QWTTKPSFBANCNFSM426BSM5Q
.

https://github.com/knowm/XChange/pull/4151/commits/20154ce6504cd077d219888deb1f8e5e7737f254

Fixed by @mdvx


feat!: add Basilisk ss58

fixes #21

waiting for https://github.com/paritytech/substrate/pull/8955

dependent on #54


[Bug Report] ttnn.concat - Tile padding along concatenated dim is not supported

Describe the bug
The ttnn.concat op throws Tile padding along concatenated dim (3) not supported for concat yet (tensor: 0) error when the tuple of two input tensor of same shape (1, 32, 12, 50) are passed with concat dim = -1. The above error is thrown while validating the input tensor of the concat op in the ttnn::operations::data_movement::ConcatDeviceOperation::validate function.
For more context, here is the exact error message:
E       RuntimeError: TT_FATAL @ ../ttnn/cpp/ttnn/operations/data_movement/concat/device/concat_device_operation.cpp:43: !in_ref.get_shape().has_tile_padding(this->dim)
E       info:
E       Tile padding along concatenated dim (3) not supported for concat yet (tensor: 0).

To Reproduce
Run the following test:
import torch
import ttnn
from tests.ttnn.utils_for_testing import assert_with_pcc

def test_concat_rotary_embedding(device):
    concat_dim = 3
    torch_input_tensor_a = torch.rand((1, 32, 12, 50), dtype=torch.float32)
    torch_input_tensor_b = torch.rand((1, 32, 12, 50), dtype=torch.float32)
    torch_output_tensor = torch.concat([torch_input_tensor_a, torch_input_tensor_b], dim=concat_dim)

    input_tensor_a = ttnn.from_torch(torch_input_tensor_a, layout=ttnn.TILE_LAYOUT, device=device)
    input_tensor_b = ttnn.from_torch(torch_input_tensor_b, layout=ttnn.TILE_LAYOUT, device=device)

    output = ttnn.concat([input_tensor_a, input_tensor_b], dim=concat_dim)
    output = ttnn.to_torch(output)

    assert_with_pcc(torch_output_tensor, output, 0.9999)

@jaykru-tt can you see if this has been covered by the concat merge you did ?

Did not hear back reason for P0 label. Setting to P1.

@ntarafdar let's update the Forge team on the status on this issue. :)

This can be cherry-picked right now in Jay's branch. He is currently trying to push this in through CI and running into perf issues (allocater).  https://github.com/tenstorrent/tt-metal/pull/14306
Need to investigate if this is infra issue or issue in concat.
Let us know if cherry-picking will work in meantime, Jay will be back next Wednesday to push it in.
If not we can assign someone this in the mean time

Hi Naif, thanks for the update. At the moment we are consuming only metal main so we can't consume custom branch that you shared and we will wait for fix to land on main. I understand that it takes some time to get this in and it is fine, important part if that this is being worked on with priority.
Assigning someone else at this point seems inefficient. Wednesday sounds fine.

Any updates on this one? We are still blocked on Llama bringup due to this.

@jaykru-tt is back to work on this. He has seen unexpected bugs related to perf tests of models due to concat allocating large tensors. His eta to get this fixed and in is tomorrow.

just wanted to give context on this bug on the turn around time.
Concat allocates really big tensors and this shows up an unrelated bug due to allocation that @jaykru-tt should have a fix for.
Unfortunately it only shows up in a large e2e test that shows up in the SD tests that takes 1.5 hrs to run, even a smaller unit test doesn't recreate this with the same inputs to concat as  its dependent on previous op allocations.
@jaykru-tt is working hard at this and we want to thank you for your patience.

Should be resolved by #14306. Let me know if you're still seeing problems! @dgolubovicTT @tt-mpantic

After this fix we have problems with the same concat. Namely ttnn.concat gives output that is padded
input1 shape: (1,1,12,50)
input2 shape: (1,1,12,50)
concat dim = -1
pytorch output: (1,1,12,100)
ttnn output: (1,1,32,128)
you can repro it with your ttnn test ust putting these shapes:
@pytest.mark.parametrize("height", [12])
@pytest.mark.parametrize("width", [50])
@pytest.mark.parametrize("dim", [-1])
@pytest.mark.parametrize("async_mode", [True, False], ids=["async_on", "async_off"])
def test_concat(device, height, width, dim, async_mode):
    device.enable_async(async_mode)
    torch_input_tensor_a = torch.rand((1, height, width), dtype=torch.bfloat16)
    torch_input_tensor_b = torch.rand((1, height, width), dtype=torch.bfloat16)
    torch_output_tensor = torch.concat([torch_input_tensor_a, torch_input_tensor_b], dim=dim)

    input_tensor_a = ttnn.from_torch(torch_input_tensor_a, layout=ttnn.TILE_LAYOUT, device=device)
    print(" shape of input: ", input_tensor_a.shape)
    input_tensor_b = ttnn.from_torch(torch_input_tensor_b, layout=ttnn.TILE_LAYOUT, device=device)
    print(" shape of input: ", input_tensor_b.shape)

    # if ttnn.has_tile_padding(input_tensor_a, dim=dim) or ttnn.has_tile_padding(input_tensor_b, dim=dim):
    #     pytest.skip("Cannot concat tensors with tile padding")

    output = ttnn.concat([input_tensor_a, input_tensor_b], dim=dim)
    print(" shape of output: ", output.shape)
    print(" shape of torch_output_tensor: ", torch_output_tensor.shape)
    output = ttnn.to_torch(output)

    assert_with_pcc(torch_output_tensor, output, 0.9999)

So this is still a blocker for Llama bringup, therefore it is again P0.
Can you please add some tests when you fix it just to know it works at least for these shapes.

@jaykru-tt could you look at this.

@dgolubovicTT spoke to @jaykru-tt , he is on it, I think early next week is when he can have it done since Thu/Fri is off

Should be resolved by https://github.com/tenstorrent/tt-metal/pull/15513 once merged. I've added the requested shapes to make sure we don't regress on this.

I've cherry-picked your fix and it works. Closing this one for now


dracut: reduce closure and suffix DRACUT_PATH

Description of changes
Implement a few usability changes for dracut framework by suffixing rather than prefixing DRACUT_PATH (so that downstream consumers can more easily override it) and reduce closure size by bundling fewer default utilities in DRACUT_PATH
Done per comments at https://github.com/NixOS/nixpkgs/pull/210075#discussion_r1088822274
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg eval
Not sure why ofborg-eval-lib-tests failed but it seems unrelated to this PR?

I just pushed again to substitute the glibc dependency with stdenv.cc.libc since that should always have ldd but should deal better with cross


Adsk Contrib - Add exchange role for display-referred color space

Now that reference type has been added to color spaces, we can enhance the feature to create processor between configs.
When first color space is scene-referred, the role for the exchange color space is aces_interchange.
When going from one config to another, if the first color space is display-referred, the default role of the exchange color space is cie_xyz_d65_interchange.
Signed-off-by: Bernard Lefebvre<EMAIL_ADDRESS>

This completes the implementation of issue #927.


Enable alternative repository location for Terragrunt releases

Installer tools commonly support the ability to specify the location to get the list of releases and download them, like...

tfenv (Terraform) has TFENV_REMOTE
n (Node.js) has N_NODE_MIRROR

The benefit is that, for organizations concerned with secure supply chains, a mirror can be established in an internal location that has pre-approved versions of tools that can be used.
What I'm hoping for is a similar solution for tgenv to allow an internal mirror to handle listing versions and pulling binaries.
Given the repo and command structure for tfenv appears largely similar to tgenv it may be possible to "borrow" some of the strategies and code there to update things here.

Hi @tillig. Thanks for your suggestion. I agree it could be a good feature to have an we can compare notes with the tfenv project.
I can't give you a timeline for when this will be implimented. Would you consider raising a PR yourself?

If I get a chance, I'd be happy to contribute. I'll have to dig in a bit to see how it works.

TFENV_REMOTE works because you can supply a single URL that will serve both the list of available versions and the downloads. In the case of tfenv, this is https://releases.hashicorp.com. This is used in two places:

In tfenv-install it's used to build the URL for downloads
In tfenv-list-remote it's used to build the URL to get the HTML list of releases

Terragrunt doesn't have a similar "single location" for things. Right now tgenv uses the Git repository to get the list of tags for Terragrunt, which isn't terribly easy to reproduce or proxy; and there's no way to swap in the location for the binary download.
My current thought is there may need to be two variables.

TGENV_REMOTE_RELEASES - this is an endpoint that can respond with a list of releases, ostensibly in the same format as the GitHub API like https://api.github.com/repos/gruntwork-io/terragrunt/releases. I'm not sure how else to get a list of releases with a straight HTTPS call that can be proxied by a standard HTTPS server. The key here is it needs to be accessible via curl rather than git.
TGENV_REMOTE_DOWNLOAD_FORMAT - this is a format string where we can replace certain placeholders (os, version) to "build" the URL for downloads. For example, the default might be https://github.com/gruntwork-io/terragrunt/releases/download/v{version}/terragrunt_{os} and we can do a replacement of the two placeholders to build the right download location.

Why two variables? Why not just get the download location from releases?
At least in my case, I can proxy GitHub API calls pretty easily because they don't download an executable. However, I'd need to build the URL for download differently to pull through our Sonatype Nexus Repository. Conversely, Sonatype Nexus Repository doesn't have a simple release list available. So I would be able to split the two things apart - leave the default for the release list, change the format for download to something that works.
The alternative, of course, is to use a single TGENV_REMOTE like https://api.github.com/repos/gruntwork-io/terragrunt/releases and assume someone swapping the remote will do so with data that mimics the GitHub API. In that case, we could parse the JSON and find the appropriate download URL from that instead of building it with string manipulation.
This leaves me with a couple of questions before I head down this road.

Does the two-variable approach sound acceptable? It's maybe less straightforward to configure, but it's pretty flexible. Or is there some other proposal?
Can we use jq? If we use the GitHub API for downloading the list of releases, it'll be far easier to parse and find data out of the JSON if we can use jq. I'm sure we can probably figure out how to get it with grep/sed/awk but it might be harder code to maintain and read longer-term. That said, perhaps there's no appetite for taking the additional dependency, so I figured I'd ask.,


Don't try and show Vidcrunch ad outside US

Vidcrunch ads are not being filled outside the US but are significantly impacting the UX of the app

This stops the sticky ad from impacting the UX outside of the US as a first step

Maybe exclude EU instead? Most of it is in the US,but does work in some other areas too.

Poked the new ad provider again this morning btw..

Is that bad floater in old code, or in today's prod? (seeing that the screenshot is localhost)
Pretty sure I tested the fix on iOS.

Sorry that branch had master from the beginning of last week pulled in but not since then, it seems the floating is fixed now. @infinite-persistence


Files for the twitter demos and RSS feed demo

These files were verified over the summer.  They are being committed now to be added to the Malhar repository.  These include the RSS reader demo and further demos for twitter.

The pull request should target the devel-3 branch. Please see: http://apex.incubator.apache.org/contributing.html

The Pull Request is opened against master. Please open a pull request on devel-3 branch after taking care of review comments.  check http://apex.incubator.apache.org/contributing.html for contributing.
Also there needs to be a JIRA associated with a checkin. Please open JIRA and specify its id in commit message.

@NithinPerumal , Couple of things in general:

When you convert a certain type of exception to RuntimeException, please ensure that the originally caught exception is passed to RuntimeException. I could see a lot of such places where the caught exception is thrown as RuntimeException with just a message and call trace of real exception is lost there. In debuging scenario it's really useful to see the cause of exception.

There are 2 operators which are just taking the tuple from input and sending it to output port. In such case a better option would be to just connect the input stream to downstream operator in DAG.

Lastly, as @tweise  said, please taking care of the comments and create a pull request on devel-3 branch.

Travis build says Twitter demo compilation has failed.
Please check why compilation failure is happening.

@NithinPerumal there are un-addressed comments on this pull request. Can you please address them or close this pull request.


Request fix if request binding does not exist in the app

When running in testing environment, $app['request'] does not exist, so we initialize a new Request instance if needed.

Hello @briedis, thanks for your PR.
This shouldn't be handled by Sentry, that is dependent on your environment.