Max values for maxBatchSize and prefetchCount

What is the maximum value for maxBatchSize? I wasn't able to find the constraints in the docs.

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

ID: 47f65d3b-7b17-223e-2ffa-caff402d0e57
Version Independent ID: 3a7e1ff6-06f6-672f-b9bc-05c642d94593
Content: EventProcessorOptions.MaxBatchSize Property (Microsoft.Azure.EventHubs.Processor) - Azure for .NET Developers
Content Source: xml/Microsoft.Azure.EventHubs.Processor/EventProcessorOptions.xml
Service: event-hubs
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

Hi @ajsaclayan.  The maximum for the batch size and prefetch counts are not bounded by the client; they are constrained only be the limits of its type declaration.   In this case,  int which has a maximum of 2,147,483,647.
An important call-out, however, is that the maxBatchSize is the maximum size that you'll receive in a single call, intended to limit the amount not.   It does not guarantee the number of events that you will receive in a batch and the client does not attempt to build a batch of that size.  Each receive call will return the number of events that are available in the prefetch queue.  If the prefetch queue is empty, the client will attempt to wait until the queue has at least one event available and then populate the batch with those.

As @jsquire pointed there is no boundary for those settings other than the INT type. I would also like to add that most clients won't see any meaningful improvements after around 5000 on both settings.


\n is a valid preprocessing token

Expected behavior

\n should be a valid preprocessor token so that it can be used in token pasting.
Found in /usr/include/sys/sysmacros.h. glibc is cursed.
Code

#define __SYSMACROS_DM(symbol) __SYSMACROS_DM1 (a b \n c)
#define __SYSMACROS_DM1(...) __glibc_macro_warning (#__VA_ARGS__)
__SYSMACROS_DM(a)
<stdin>:1:53 error: invalid token: unknown token: '\'
#define __SYSMACROS_DM(symbol) __SYSMACROS_DM1 (a b \n c)
                                                    ^

Output from clang -E:
__glibc_macro_warning ("a b \n c")

http://port70.net/~nsz/c/c11/n1570.html#6.4p3:

The categories of preprocessing tokens are: header names, identifiers, preprocessing numbers, character constants, string literals, punctuators, and single non-white-space characters that do not lexically match the other preprocessing token categories.

"If it's not whitespace, it's valid!" :facepalm:

Fixing this long-term will be difficult, since \n is not a valid lexer token. I came up with an idea to split apart the lexer and preprocessor: preprocessor tokens are a superset of lexer tokens, but should be turned into lexer tokens by the time preprocessing finishes. Then there would be two options for a lexer: either the preprocessor or the lexer, but not both.

So is '


Can't find prisma binary on vercel serverless function

Bug description
When I deploy my project on vercel, It always throws this error.
It seems generating prisma client not work.
Tested on pnpm 8.6.8, yarn 1.22.18
Unhandled rejection: PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-1.0.x".

This is likely caused by a bundler that has not copied "libquery_engine-rhel-openssl-1.0.x.so.node" next to the resulting bundle.
Ensure that "libquery_engine-rhel-openssl-1.0.x.so.node" has been copied next to the bundle or in "node_modules/.pnpm/@prisma+client<EMAIL_ADDRESS>
We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/engine-not-found-bundler-investigation

The following locations have been searched:
  /var/task/node_modules/.pnpm/@prisma+client<EMAIL_ADDRESS>  /var
  /vercel/path0/node_modules/.pnpm/@prisma+client@5.6.0_prisma@5.6.0/node_modules/@prisma/client
  /.prisma/client
  /tmp/prisma-engines
    at il (/var/task/index.js:67:805)
    at async Object.loadLibrary (/var/task/index.js:114:9808)
    at async Wt.loadEngine (/var/task/index.js:115:448)
    at async Wt.instantiateLibrary (/var/task/index.js:114:19566) {
  clientVersion: '5.6.0',
  errorCode: undefined
}
Error: Runtime exited with error: exit status 1
Runtime.ExitError

How to reproduce

Clone this repo nabi-chan/vercel-test
deploy it to vercel
after build, enter the deployment
It reproduced!

Expected behavior
Find prisma binary and correctly works
Prisma information

generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model User {
  id    Int    @id @default(autoincrement())
  email String @unique

  name     String?
  password String

  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
}

const prisma = new PrismaClient();

Environment & setup

OS: macOS
Database: PostgreSQL
Node.js version: v20.10.0
Package Manager : pnpm

Prisma Version
prisma                  : 5.6.0
@prisma/client          : 5.6.0
Computed binaryTarget   : darwin-arm64
Operating System        : darwin
Architecture            : arm64
Node.js                 : v16.15.0
Query Engine (Node-API) : libquery-engine e95e739751f42d8ca026f6b910f5a2dc5adeaeee (at node_modules/.pnpm/@prisma+engines<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli e95e739751f42d8ca026f6b910f5a2dc5adeaeee (at node_modules/.pnpm/@prisma+engines@5.6.0/node_modules/@prisma/engines/schema-engine-darwin-arm64)
Schema Wasm             : @prisma/prisma-schema-wasm 5.6.0-32.e95e739751f42d8ca026f6b910f5a2dc5adeaeee
Default Engines Hash    : e95e739751f42d8ca026f6b910f5a2dc5adeaeee
Studio                  : 0.495.0

I actually get a different error message:
PrismaClientInitializationError: Prisma Client could not find its `schema.prisma`. This is likely caused by a bundling step, which leads to `schema.prisma` not being copied near the resulting bundle. We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/bundler-investigation-error
    at new ir (/var/task/index.js:107:118)
    at t.getEngine (/var/task/index.js:177:6126)
    at new t (/var/task/index.js:177:5710)
    at Object.<anonymous> (/var/task/index.js:187:2735)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at r.<computed>.e._load (/var/task/___vc/__launcher/__launcher.js:14:2516)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:169:29) {
  clientVersion: '4.16.2',
  errorCode: undefined
}

Did you already do anything with your setup to overcome this, and then land on the error above?

Faced the same issue. @janpio , can you provide any workaround or the info about fixing ability?

No, but you could help by looking at the reproduction above and shared what is similar to your situation. Is this related to one of these dependencies?
Optimally provide your own reproduction for us so we can take a look at that one as well.

Are there any updates on this? I'm using tsup with turborepo and I cannot build my docker image because of the same reason
PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "darwin-arm64".

This is likely caused by a bundler that has not copied "libquery_engine-darwin-arm64.dylib.node" next to the resulting bundle.
Ensure that "libquery_engine-darwin-arm64.dylib.node" has been copied next to the bundle or in "packages/api/dist".

We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/engine-not-found-bundler-investigation

Are there any updates on this? I'm having the same error, I cannot run my container based on my image
PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "darwin-arm64".

This is likely caused by a bundler that has not copied "libquery_engine-darwin-arm64.dylib.node" next to the resulting bundle.
Ensure that "libquery_engine-darwin-arm64.dylib.node" has been copied next to the bundle or in "packages/api/dist".

We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/engine-not-found-bundler-investigation

Same issue - have tried a number of suggestions online, but nothing is working.
During the vercel build phase, the libquery_engine-rhel-openssl-3.0.x.so.node is present in the ./node_modules/@prisma/client/fast-pos directory, but not bundled into the vercel functions.
I tried the @prisma nextjs-monorepo-workaround, but that broke the local next build.
I am on pnpm monorepo<EMAIL_ADDRESS>and<EMAIL_ADDRESS>prisma:error
Invalid prisma.application.findMany() invocation:
Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".
We detected that you are using Next.js, learn how to fix this: https://pris.ly/d/engine-not-found-nextjs.
This is likely caused by a bundler that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" next to the resulting bundle.
Ensure that "libquery_engine-rhel-openssl-3.0.x.so.node" has been copied next to the bundle or in "node_modules/@prisma/client/fast-pos".
We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/engine-not-found-bundler-investigation
The following locations have been searched:
/var/task/packages/frontend/products/fast-pos/node_modules/@prisma/client/fast-pos
/var/task/packages/frontend/products/fast-pos/.next/server
/vercel/path0/packages/frontend/products/fast-pos/node_modules/@prisma/client/fast-pos
/var/task/packages/frontend/products/fast-pos/.prisma/client
/tmp/prisma-engines
Error [PrismaClientInitializationError]:

Facing the same issue, is there any workaround ? I'm using turborepo.


Multiple instances not supported

I have 2 printers configured as 2 module instances in magic mirror. The information only displays in the first module. The information of both printers cycles through. So for a second it shows printer 1, then it updates and shows printer 2. It basically cycles between the 2 printers. I would like to be able to configure more than one printer to have a kind of dashboard where I can see everything at one glance.

I was about to ask the same, also it would be nice to only show active printers.


I think this could be made a little more clear (maybe have an example as a tool tip)

(note: the "??" in the file path is "🎮", but the program does not know how to display emojis)

Ah that it will, in this case the appdata directory needs to be the games app data directory, ill add some tool tips in the next hotfix

may I still ask for a bit more clarification on "the game's app data"? do you mean the "Larion Studios" folder?

Ah apologies the bg3 folder in that folder
On Sat, 16 Sept 2023, 22:37 StuffOfSonny, @.***> wrote:

may I still ask for a bit more clarification on "the game's app data"? do
you mean the "Larion Studios" folder?
—
Reply to this email directly, view it on GitHub
https://github.com/CHollingworth/Lamp/issues/18#issuecomment-1722321288,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARGLQVOUSS6M3CIPTSHAN7LX2YLYTANCNFSM6AAAAAA43AJOZ4
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Remove IInvokedMethod references from SuiteRunner

Instead of saving all invoked methods, now we are
resorting to computing it on a need basis.
Fixes #2096

@juherr - I have fixed all the review comments. Please help take another look


[all] Remove custom psa_crypto.c for mbedtls v3.6.1

psa-driver.c updated to zephyr latest version in https://github.com/aosedge/aos_core_lib_cpp/pull/152
PR is not valid


Non-yarn Installation Instructions

Is your feature request related to a problem? Please describe.
I'd like to implement OUI on our statically generated jekyll  site. So far the only 'installation' instructions are to use yarn.
Describe the solution you'd like
I see two solutions.

Someone creates a yarn file for us that we can place at the root of our website-project github repo so that yarn can be used to install it in an appropriate location or
A non-yarn tutorial / build process for grabbing all of the assets and styles so that we can include them from our site layouts 'the old fashioned way'

Describe alternatives you've considered
Rebuilding project-website with Gatsby or some other kind of react ready static site generator.
Additional context
I hope this doesn't indicate too much ignorance on my part. These fancy-schmancy react component libraries are new to me. I'm slowly getting up to speed.
Thanks!

One thing that we could do is upload oui.min.js as well as any oui_theme[...].min.css as artifacts when we create Github releases. It's not ideal, as updating to newer OUI versions would be manual, but it would be an option for cases like this

This might have been my own doing in regards to yarn not working - apparently Ubuntu selects 'cmdtest' when you tell it to install yarn. After getting the actual yarn installed, I was able to yarn build
I'll leave this open, as it might be good fodder for adding a document on describing the build process.

Alternatively, other libraries like Bootstrap usually provide a CDN link using services like jsDelivr. That one can grab files directly from the published NPM package, so it would be minimal setup on our end.
One thing that should be up for discussion, though, is if this should be within the scope of the project, being a React library and targeted at being used in a Webpack-style bundling system.

One thing that should be up for discussion, though, is if this should be within the scope of the project, being a React library and targeted at being used in a Webpack-style bundling system.

Now that I've learned a thing or two about a thing or two, I couldn't imagine going through the compilation process any other way other than using yarn. I'd still like to be able to use something like jsDelivr so that when things are updated and changed that they reflect on our website too.


Cannot escape simulator full screen in tutorial mode

In tutorial, click on simulator to go full screen, cannot go back.

Dup of #717?

Yup, fixed in https://github.com/Microsoft/pxt/pull/5471

Dupe


Issues integrating

Hi,
I'm having issues with integrating. Here is my code:
QUICK_RATIO_CHART_SQL = "SELECT [Quick Ratio] FROM [RATIO ANALYSIS] WHERE [ASX Code] like '" & ASXCODE & "'
Set QR_Chart = BAC.Chart(Me.wbChartQR)
QR_Chart.CreateChart
QR_Chart.DataSource.SQLStatement = QUICK_RATIO_CHART_SQL
QR_Chart.DataSource.DataFieldNames = Array("Quick Ratio")
QR_Chart.ChartType = chChartType.Line

When the chart displays is shows only the Demo Data as a bar graph.
Are there any obvious issues?
Thank you

Hi there!
I see some reasons here for the trouble you have:

In row 3 you create the chart without further specifications. This will always lead to the demo chart. Put this row at the end
In the SQL-Statement you have only one field (for the data I think). You also have query the label field.
At the end you must tell the chart the name of the label field.

I've adapted your code to the data in the sample database. In the end my code looks like this:
    Dim QR_Chart As BAC_Chart
    Dim QUICK_RATIO_CHART_SQL As String

    QUICK_RATIO_CHART_SQL = "SELECT DataLabel, [Dataset1] FROM [tbl_DemoData] WHERE 1=1"
    Set QR_Chart = BAC.Chart(Me.wbChartQR)
    QR_Chart.DataSource.SQLStatement = QUICK_RATIO_CHART_SQL
    QR_Chart.DataSource.DataFieldNames = Array("Dataset1")
    QR_Chart.DataSource.LabelFieldName = "DataLabel"
    QR_Chart.ChartType = chChartType.Line
    QR_Chart.CreateChart

I will close this issue.


MDNavigationRailItem icon not loading from local image

Description of the Bug
First off, is this possible to load an image into the icon? The documentation doesn't specify this, and all examples seem to point to an internal cache of icons.  When using any of the md_icons it works fine, when using a local image it doesn't.
I found MDChip also uses icon so I tried with that element, and it successfully loads the image.
Code and Logs
There are no errors that I can tell.

from kivy.app import App, Builder
from kivymd.app import MDApp

kv = """
#:kivy 1.0.9
#:import get_color_from_hex kivy.utils.get_color_from_hex

<MyTile@SmartTileWithStar>
    size_hint_y: None
    height: "240dp"

MDBoxLayout:
    orientation: "vertical"
    MDToolbar:
        title: "MDNavigationRail"
        md_bg_color: rail.md_bg_color
    MDBoxLayout:
        orientation: "horizontal"
        MDNavigationRail:
            id: rail
            color_normal: get_color_from_hex("#718089")
            color_active: get_color_from_hex("#f3ab44")

            MDNavigationRailItem:
                icon: "coffee-cup.png"
                text: "Python"
            MDChip:
                icon: "coffee-cup.png"
                text: "Python"
"""

class MainApp(MDApp):
    def build(self):
        self.root = Builder.load_string(kv)

if __name__ == '__main__':
    MainApp().run()

Screenshots
Application:

Image File:

Versions

OS: Windows 10
Python: 3.9.0b3
Kivy: 2.0.0
KivyMD: 0.104.2.dev0

@jpan127

possible to load an image into the icon?

What do you have in mind?

Hi, the library has a bunch of predefined icons, but I wanted to supply my own.  Is that possible with this element? I looks like it is with MDChip.

@jpan127 https://kivymd.readthedocs.io/en/latest/components/chip/#use-custom-icon

@HeaTTheatR Sorry, what? I said MDChip works, but the post is about MDNavigationRailItem.

@jpan127 You cannot use custom icons for the MDNavigationRailItem class.

I see, that is unfortunate.
Are there plans to support this? And if not, do you have suggestions on how I can add this feature?

Deprecated - https://github.com/kivymd/KivyMD/commit/c683f53e8eb565dc6510814c5e4382b78ce1e216


Unable to edit the convo files in the "Shared Folder" in UI

I have shared a folder in botium consisting of more than 500 convo files. But if I want to edit the convo files in UI, I haven't seen such a provision there. Is there some other way to edit the convo files in UI?

currently there is no way to edit the files within the botium box.


Blogspot

This doesn't seem to work for any blogspot subdomain..
test.blogspot.com gives as registrable domain: test.blogspot.com
test.github.com gives as registrable domain: github.com
I don't understand how it would work that way?

Hi @atypicalprogrammer
TLDExtract uses TLDDatabase which uses PublicSuffix List as single source of truth. PSL has two sections: ICANN and private domains. So, when you set TLDExtract's parsing mode it operates with determined sections.
blogspot.com is defined in private section, so it's private domain. If don't need private domains in your result, you need to set parsing mode:
$extract = new Extract(null, null, Extract::MODE_ALLOW_ICCAN);
$result = $extract->parse('test.github.com');
// of in fuction
tld_extract('test.github.com', Extract::MODE_ALLOW_ICCAN);

Howerer, I agree that getRegistrableDomain() returns an incorrect result without parsing options, it's a priority issue for next major version.

hi,
there are also some other domains falsley valid.
ex.: #test.com or test.com#test_test
->isValidDomain() gives me true for both, and also in the ->getRegistrableDomain() i get the false domain
regards

@dgram Thanks, I opened #15 for this.


Adding quarantined and isolated to AR scraper

@dominikgehl thank you for this! I'll run some tests with this, but looks good so far.


Backup

Some of the deployed services have data that could be useful to backup. I have been playing around with restic/autorestic using backblaze and dropbox as backend and it works really good.
TODO:

[ ] Create a list in this issue with all services and then go through each service and figure out what needs backup.
[ ] Automatic deployment on changes

[ ]
[ ] autorestic
[ ] dashdot
[ ] diun
[ ] dozzle
[ ] duckdns
[ ] gatus
[ ] glances
[ ] healthchecks
[ ] homeassistant
[ ] homepage
[ ] mosquitto
[ ] nixos
[ ] pihole
[ ] piper
[ ] speedtest
[ ] tailscale
[ ] traefik
[ ] uptimekuma
[ ] whisper
[ ] zigbee2mqtt

Automatic deployment in place, might need some tweaking on when to run it but that will be handled in #23 and #26.


fix(lang-lexer/inject): better support injection of pp. dirs. from multiple files

As of now, injecting preprocessor directives found in included files back into the AST when using the v2-full lexer is not supported. Attempting to do so will trap the Directives::inject method in the following loop forever, as a different source file ID will cause neither directive_idx to be incremented or break to be reached:
https://github.com/vtavernier/glsl-lang/blob/881c0e472bfa990150c7a3fcd8b3efc787b66ccc/lang-lexer/src/v2_full/directives.rs#L134-L158
After giving the situation some thought, I think it's more appropriate to inject the preprocessor directives that we are currently capable of injecting, regardless of whether they come from a different file:

#pragma: most of these directives are to be defined by the GLSL compiler implementation, and those documented in the GLSL specification change the compiler state in a way where only their location in the source is relevant, not the file they were expanded from.
#extension: similar to #pragma. Furthermore, the specification explicitly states that "directives that occur later override those seen earlier".
#version: the GLSL specification states that "the #version directive must occur in a shader before anything else". This suggests (but does not unequivocally assert) that there should only be one #version directive per shader.

By now, I think it is clear that #pragma and #extension can be injected as they are without further ado. However, handling #version in combination with #include requires further work, in my view.
Let's consider a shader A that is valid on its own, but does not contain a void main() function (this is allowed by the GLSL specification, as long as the shader is linked together with another shader that defines this function). Now, consider a shader B that #includes shader A and defines void main(). Let's assume that the GLSL application compiles shader B. In this scenario, I'd argue that it makes sense for both A and B to have a #version directive in the beginning of their respective sources, because both are shaders, according to the specification. A could define a void main() function only if a preprocessor directive set by B before the #include is unset, allowing it to be linked as a completely standalone shader, where the #version directive can't be placed anywhere else. Remarkably, the specifications for #include extensions like ARB_shading_language_include do not mention how to handle multiple #version directives at all.
Given the above scenario, I think that a good solution is to make sure that Directives::inject only emits at most one #version directive, with its version and profile set to the highest version and most featureful profile among those specified in all #version directives. As far as I know, GLSL versions are backwards compatible, and even if they weren't, several #version directives are likely to violate the GLSL specification, so there would be no way to reconcile GLSL sources targeting incompatible GLSL versions anyway.
These changes let #pragma and #extension directives coming from included files be injected anyway. #version directives are injected too, but only one #version directive is ever injected, according to the technique stated in the previous paragraph.
(By the way, I appreciate your prompt PR reviews. As you can see, I'm taking these crates for a good spin, trying to improve what I find in the process. I think that Rust deserves a rock-solid GLSL parser library :heart:)

While I think I do understand the issue, this seems like a rather complex case and I'm worried it could show up again later if refactor was to come.

Indeed, I had to scratch my head quite a bit to understand what was going on 😄

Do you think you could add a regression test for this issue so we make sure this is fixed and stays this way?

Sure, I could give it a shot! I didn't add a regression test because I wasn't sure how to go about it, given that the modified files don't contain any tests. What's the rough outline of how you'd like such test to look and where would you put it?

Sure, I could give it a shot! I didn't add a regression test because I wasn't sure how to go about it, given that the modified files don't contain any tests. What's the rough outline of how you'd like such test to look and where would you put it?

They do not contain any tests because unfortunately those components are currently hard to unit test, since they use the SyntaxNode structures from rowan. I think the best course of action is to have the test in the global parser tests folder (https://github.com/vtavernier/glsl-lang/tree/master/lang/tests), and since it relies on multiple files these could be residing in https://github.com/vtavernier/glsl-lang/tree/master/lang/data/tests. It's not in the same crate as the changes but right now it's easier to get a full parsing context ready from the glsl-lang crate to target this bug.

Alright, I can try to cobble up together an integration test. I'll let you know when I get to it :smile:
(As a completely unrelated side note, I recently came across the proptest crate. I think it can be very useful for testing components like the transpiler, but that's out of the scope for this PR anyway.)

(As a completely unrelated side note, I recently came across the proptest crate. I think it can be very useful for testing components like the transpiler, but that's out of the scope for this PR anyway.)

This looks interesting, another thing that works well for compilers is fuzzing, and it's already setup (using afl) in this repository (here). It helped find a bunch of bugs in the v2 parser in early development, and from experience it's also pretty good at finding infinite loops (as well as panics). The hard part is getting an interesting corpus to run fuzzing on, which I haven't got around to yet.

I went busy after these last comments, and then totally forgot about this PR until I opened another now :sweat_smile:
I will see if I can get some tests done soon; if not, and if anyone is interested in seeing this PR through to completion, please feel free to pick up this branch where I left it.

Finally got some time to spend on this, I've added a regression test for the issue that this PR fixes.
If you rebase your PR on the latest master and cherry-pick e137fef72b4cbd302e6da276131b0afc666b2956 and df5f33cdae636b29490f16283f2aa042444fe005 we can get this merged and released!

Sorry for the delay - I finally had time to get around the rebase and cherry-picking. Thank you a bunch for adding the tests. Let me know if you there is anything else left :heart:


How to do query on button click?

I want to say thanks first for this great Apollo integration!
I ran into some problem recently and got no answer after googling around. The scenario is pretty simple: I don't want the query to be called automatically when the page/components is loaded, I just want to call the query on button click.
So in React with react-apollo I can do something like this:
import { withApollo } from 'react-apollo';
import{ Component } from 'react';

class MyComponent extends Component {
  doQuery() {
  	this.props.client.query({
  	  query: myCustomQuery,
  	  variables: {
  	  	variable1,
  	  	variable2,
  	  }
  	})
  }
  render() {
  	<button onClick={() => this.doQuery}></button>
  }
}

export default withApollo(MyComponent);

The 'client' prop comes from withApollo HOC
I wonder if there is a way to do this in vue-apollo?
Looked into this issue #36 , but I believe the answer provided does not meet my need, because "refetch" will simply do the query again with same query/variables. I am searching for a way in which every time I click the button I can get different queries according to my variables.

You can either use this.$apollo.query(...) or use skip in the smart query definition:
export default {
  data () {
    return {
      myVariables: null,
    },
  },

  apollo: {
    items: {
      query: GQL_QUERY,
      variables () {
        return this.myVariables
      },
      skip () {
        return !this.myVariables
      },
    },
  },

  methods: {
    onButtonClick () {
      this.myVariables = {
        // ...
      },
    },
  },
}

Thanks for you reply. So with the skip, will it help me avoid auto query on component load? (Because I only want the query on button click). If not, is there any other ways to do this?

I showed you two different ways already. :smile:

Oh I see what you are saying. It works perfectly, thanks!

@Akryum thanks for the answer. I have another question:

How do we specify custom client when we do query/mutation on a click event.
   this.$apollo.mutate({
         mutation: UserAuth,
        variables: {
            email<EMAIL_ADDRESS>            password: "admin123",
         },
   }).then((data) => {
     return data;
   }).catch((error) => {
     // Error
     console.error(error)
     // We restore the initial user input
   });

@Akryum i got the answer. Just in case if someone wants to know the solution.
async authMutation() {
    this.$apollo.client = "auth";
    return this.$apollo.mutate({
        // Query
        mutation: UserAuth,
        clientId: 'auth',
        // Parameters
        variables: {
          email<EMAIL_ADDRESS>// change this to actual data
          password: "admin123", // change this to actual data
        },
      }).then((data) => {
       return data;
      }).catch((error) => {
        // Error
        console.error(error)
        // We restore the initial user input
      });
}


Still maintained?

Last commit is from 2019
Travis CI is outdated "Since June 15th, 2021, the building on travis-ci.org is ceased. Please use travis-ci.com from now on."

@cameronmaske

Recommend switching to celery-singleton.


fix(controllers): Remove controller global init

What this PR does / why we need it:
Add your description
Which issue(s) this PR is related to (optional, link to 3rd issue(s)):
Fixes https://github.com/kleveross/klever-model-registry/issues/79
Reference to #

Special notes for your reviewer:
/cc @gaocegege @FogDong

Release note:

NONE

Please fix the CI


This removes the sudo: false line enabling container builds, but this allows branches to build again on travis without issue.

This will slow down the Travis builds a lot :/

This will slow down the Travis builds a lot :/

Yes, but at least our branches will build again. Nothing can build with the Docker containers at the moment, and Travis developers are out for the weekend (understandably).

http://docs.travis-ci.com/user/common-build-problems/#My-build-script-is-killed-without-any-error

http://docs.travis-ci.com/user/common-build-problems/#My-build-script-is-killed-without-any-error

Our builds don't consume more than 3GB of memory, we've checked, and the builds don't have more than two "tasks". Please be considerate when suggesting a thread that doesn't exactly apply to our situation (that link specifically speaks about tools with parallelism with other languages/setups that aren't applicable to our builds).

Okay, sorry I even spoke.

We had the same problem already a while ago in Sponge, but for some reason only with OpenJDK6, that's why it is also running on the old infrastructure already: https://github.com/SpongePowered/Sponge/blob/master/.travis.yml#L4

We had the same problem already a while ago in Sponge, but for some reason only with OpenJDK6, that's why it is also running on the old infrastructure already: https://github.com/SpongePowered/Sponge/blob/master/.travis.yml#L4

Ok, but in this case, javadocs too is failing not only on jdk6, but open7 and oracle jdk7. The only JDK that doesn't fail always is Oracle's JDK8, which occasionally fails for the same odd reason that the other three fail.
Personally, I prefer faster builds, but if it's at the cost of randomly failing without rhyme or reason, I'd rather have stability with automated build hooks.

Okay, sorry I even spoke.

It's not that you spoke, it's just the demeanor of simply posting a link without further looking into the reasoning of the PR. Personally, I find it rude to simply drop a link to an article to a PR that has to have taken some more time to consider making than it took for you to find that link. I wouldn't have replied tearing you down if you provided some simple context as to why you posted the link.
You could've said something along the lines of:

I don't know if it's relevant to the issue, but I found this article after a minute googling about Travis builds suddenly getting killed. Link to the article: http://foo.bar.baz/

We had the same problem already a while ago in Sponge

Which btw is now affecting Sponge as well.

I just remembered it, that's all.

It seems like it is simply allocating not enough memory for the Javadoc tool, and after fixing that the same for checkstyle. It seems to work fine on the new container infrastructure when allocating some more memory like this: https://github.com/SpongePowered/SpongeAPI/compare/master...Minecrell:Tmp
Travis build:


React Native can't login on Android and doesn't render images

login doesn’t work in React Native web or Android
photos don’t render in React Native iOS

What I see when I try to login via web to React Native app.

Missing images:

@ruddell I created my React Native app using these steps. If you have any ideas, please let me know!

Will check this week
Web login fails currently, started after Expo major version upgrade.  Related open issue https://github.com/ruddell/generator-jhipster-react-native/issues/395

Android/Web clients can now log in with OAuth2, added a route that redirects to the authUrl instead of NotFound.
The missing image styling was also added back (lost in a refactor at some point), so they should be visible now.
Thanks for the report 👍

Hey Jon,
I'm still unable to log in with Android. It works fine with web and iOS, so I suspect my Keycloak settings are fine. I can also see the request being made to the JHipster backend to get the auth info. I've run the following command too:
adb reverse tcp:8080 tcp:8080 && adb reverse tcp:9080 tcp:9080

It just says login failed. I'm not sure why. I'm using Pixel_5_API_30 for my AVD.

I couldn't reproduce the login issue on Android with the latest release or the one out at the time of this issue.  I updated the error messaging to reflect the reason for the failure which should help debugging.

I was able to reproduce this again today. Here's the error in my console:
Account - FAIL

No matching activity!
at node_modules/react-native/Libraries/BatchedBridge/NativeModules.js:103:50 in promiseMethodWrapper
at node_modules/@unimodules/react-native-adapter/build/NativeModulesProxy.native.js:15:23 in moduleName.methodInfo.name
at node_modules/expo-web-browser/build/WebBrowser.js:72:23 in openBrowserAsync
at node_modules/core-js/modules/es.promise.js:245:8 in Promise
at node_modules/expo-web-browser/build/WebBrowser.js:57:7 in openBrowserAsync
at node_modules/expo-web-browser/build/WebBrowser.js:164:43 in _openBrowserAndWaitAndroidAsync
at node_modules/core-js/modules/es.promise.js:245:8 in Promise
at node_modules/expo-web-browser/build/WebBrowser.js:158:0 in _openBrowserAndWaitAndroidAsync
at node_modules/expo-web-browser/build/WebBrowser.js:183:47 in _openAuthSessionPolyfillAsync
at node_modules/core-js/modules/es.promise.js:245:8 in Promise
at node_modules/expo-web-browser/build/WebBrowser.js:173:0 in _openAuthSessionPolyfillAsync
at node_modules/expo-web-browser/build/WebBrowser.js:97:44 in openAuthSessionAsync
at node_modules/core-js/modules/es.promise.js:245:8 in Promise
at node_modules/expo-web-browser/build/WebBrowser.js:86:7 in openAuthSessionAsync
at node_modules/expo-auth-session/build/AuthSession.js:153:25 in _openWebBrowserAsync
at node_modules/core-js/modules/es.promise.js:245:8 in Promise
at node_modules/expo-auth-session/build/AuthSession.js:151:0 in _openWebBrowserAsync
at node_modules/expo-auth-session/build/AuthSession.js:33:43 in startAsync
at node_modules/core-js/modules/es.promise.js:245:8 in Promise
at node_modules/expo-auth-session/build/AuthSession.js:12:7 in startAsync
at app/modules/login/login.utils.ts:77:27 in doOauthPkceFlow
at node_modules/core-js/modules/es.promise.js:115:20 in callReaction
at node_modules/core-js/modules/es.promise.js:140:11 in microtask$argument_0
at node_modules/core-js/internals/microtask.js:28:10 in flush

I followed these instructions.

I published my apps to https://github.com/oktadev/okta-react-native-jhipster-example.

I published my apps to https://github.com/oktadev/okta-react-native-jhipster-example.

I published my apps to https://github.com/oktadev/okta-react-native-jhipster-example.


Automate deployment

Currently, the deployment is done manually. Implement a continuous delivery solution.
Considerations:

Portability, open standards preferred
Balance doing the deployment on the target server vs offloading the work to GitHub
Avoid overriding .env file OR use a different method for env variables

Options:

scp
rsync
platform-specific API
self-hosted runner

For the implementation I will go with rsync:
🟢 it's an open standard
🟢 balances the traffic by sending the diff only
🟢 built-in ignore
The build process will be mostly offloaded to GitHub Actions: including resolving node_modules


signer: Extract the bip32 key correctly

Turns out we did not parse the init message correctly, rather we used the trailer of the message which included the bip32 key, but also the fields after it.
@roeierez does this change impact any existing data or can this be switched in-place? If not we will add another method to retrieve the data formerly returned by bip32_ext_key() to maintain forward compatibility.
Reported-by: @roeierez

Thanks @cdecker
Indeed we need the old format as we already have encrypted data (such as backup) that uses the previous key.

Thanks for the feedback, I will add a new method to retrieve the old bytestring. Any preference as what to call it? It will be in the API until anything that made use of the old behavior has been migrated. Is there a way for you to decrypt and re-encrypt the existing blobs to migrate away from the old behavior or are some of these on write-only media that can't be replaced with newer versions? In that case we'd keep it in there indefinitely until we're reasonably sure we'd not be breaking anything.
Apologies for the oversight, we were open-coding the parsing and made a wrong assumption (that the message would not be extended under our feet).

No worries, Christian, thanks for the support.
Currently only the sync.db that is stored in gl data store needs migration. My intention is to do that right on start of the sdk where we anyway check for new data. We will re-encrypt with the new key and that will be the only use of the old key.
We don't have a way to know that all nodes upgraded their backup but maybe after some time it would be reasonable to remove it considering the early stage we are now.

Any preference as what to call it?

Should be something ugly the ring the bells. Not sure but maybe legacy_bip32_ext_key ? and mark as deprecated with some warning.


Set v10.0.0

What does this PR do?

Sets the version to 10.0.0.
Updates projext to its latest version.

How should it be tested manually?
yarn test
# or
npm test

Pull Request Test Coverage Report for Build 330

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 328:
0.0%

Covered Lines:
646

Relevant Lines:
646

💛  - Coveralls


overflow-wrap is in Edge 18

Source?

Edge is closed source

From Wiktionary:

The person, place, or thing from which something (information, goods, etc.) comes or is acquired.


Upgrade to @vscode/test-electron

Signed-off-by: David Thompson<EMAIL_ADDRESS>

I think that something is wrong with the VS Code CDN (or maybe my internet connection) because downloading VS Code 1.86.1 as a part of the tests either takes a really long time for me, or the checksum doesn't match.
As well, I have VS Code 1.86.0 installed and no updates are yet available from the yum repo.


Question: Passing headers in context as opts to fetcher

Hi guys!
Is it currently possible to customise each query's header on the fly?
For example:
const [{ data, fetching: loading }] = useQuery({
    query: HomeQuery,
    context: {
       headers: {
           'custom': 1
       },
    },
});

Looking at apollo, looks like they are passinng the context as the second arguments to the fetch function (opts).
Thanks!

Hey,
Yes you can pass in fetchOptions which can be an object or function containing headers, ... https://formidable.com/open-source/urql/docs/api/core/#operationcontext I saw an error in our docs I'll correct it asap.

Passing in fetchOptions means it's during initialization of the Urql client right?
Some of use cases, you might need to pass specific header in specific query call.

My explanation relates to the query call where you can do
useQuery({ context: { fetchOptions } })

We should likely expand on this in additional sections in “Queries” and “Mutations” along the lines of requestPolicy being a shortcut for the context object, but the entire object being modifiable

I recently tried to append fetchOptions to context to each individual query, it's resulting into something weird:

It always says the cache outcome is miss, even though the fetchPolicy is cache-first.
Both using v1.8.2 or v1.9.4 are the same.
Do you guys have any idea or maybe I'm missing something basic?

Could you paste in your code or reproduce it in codesandbox please?

@JoviDeCroock here's some minimal reproduction of it, call the useInfiniteLoop as a function instead.
https://codesandbox.io/s/hopeful-euler-e2gmq

Yes so that's what I'm saying in that comment @josteph
const useInfiniteLoop = () => {
  const [result] = useQuery({
    query: gql`
      {
        books {
          id
          name
          genre
          author {
            name
          }
        }
      }
    `,
    context: useMemo(() => ({
      fetchOptions: {
        headers: {
          "some-headers": "hello world"
        }
      }
    }, []),
  });

  return result;
};

Alright now I understood about it more now.
Honestly wasn't quite expecting it to be like that 😅
Thanks for the explanation!


Duty cycle tracking causes downlink to be rejected for antenna gains < 2dBi

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

What happened?
Thanks for adding duty-cycle tracking to chirpstack-concentratord v4.4.0. While the time part works fine, the power part does not work with the default power level in the EU868 region and an antenna gain below 2. Downlinks get rejected, even if duty cycle enforcement is not enabled.
What did you expect?
From the regulation a 16 dBm EIRP should be allowed for the M band and a 29 dBm EIRP should allowed for the P band.
Steps to reproduce this issue
Steps:

Set the antenna gain to 0 or 1 dBi
Schedule a downlink
See it getting rejected

Could you share your log output?
MQTT logs:
chirpstack/eu868/gateway/xxxxxxxxxxxxxxxx/command/down {"downlinkId":691944082,"items":[{"phyPayload":"YMaLLQKgQwABLts0PT8=","txInfo":{"frequency":868100000,"power":16,"modulation":{"lora":{"bandwidth":125000,"spreadingFactor":7,"codeRate":"CR_4_5","polarizationInversion":true}},"timing":{"delay":{"delay":"1s"}},"context":"BIMWzQ=="}},{"phyPayload":"YMaLLQKgQwABLts0PT8=","txInfo":{"frequency":869525000,"power":29,"modulation":{"lora":{"bandwidth":125000,"spreadingFactor":12,"codeRate":"CR_4_5","polarizationInversion":true}},"timing":{"delay":{"delay":"2s"}},"context":"BIMWzQ=="}}],"gatewayId":"xxxxxxxxxxxxxxxx"}
chirpstack/eu868/gateway/xxxxxxxxxxxxxxxx/event/ack {"gatewayId":"xxxxxxxxxxxxxxxx","downlinkId":691944082,"items":[{"status":"DUTY_CYCLE_OVERFLOW"},{"status":"DUTY_CYCLE_OVERFLOW"}]}

Console logs (with an antenna gain of 1 dBi):
WARN  [libconcentratord::jitqueue] No duty-cycle band found for packet, downlink_id: 691944082, freq: 868100000, tx_power: 15
WARN  [libconcentratord::jitqueue] No duty-cycle band found for packet, downlink_id: 691944082, freq: 869525000, tx_power: 28

(Notice how the antenna gain has been subtracted at that level)
Your Environment

Component
Version

Network Server
v4.7.0

MQTT Forwarder
v4.3.0

Concentratord
v4.4.0

Analysis
The transmitted TX power is configured the following way:

Chirpstack sends the downlink command to chirpstack-concentratord with EIRP TX power
The antenna gain (in dBi) is subtracted from this TX power
The transmitter is configured with the resulting TX power
Up to there that looks all fine, with a high gain antenna (relative to isotropic) the transmitter is configured to use less power, with a bad antenna (or a very long and bad cable) having a negative gain, the transmitter is configured to use more power. At the end the radiated power is the same.

Now comes the ETSI EN 300 220 regulation. The etsi_en_300_220.rs lists for each band maximum allowed duty cycle and the maximum TX power. In that file, the TX powers are actually ERP TX powers, so 2.15 dB lower (rounded to 2 dB) than the EIRP TX powers. In practice chirpstack-concentratord:

Gets the EIRP TX power from the downlink packet
Subtracts the antenna gain
Tries to match it to the ERP power from ETSI EN 300 220

In short it tries to match the transmitter power to the regulation, while the regulation applies to the radiated power by the antenna. Therefore I think the regulation matching should be done by converting the EIRP to ERP (or vice versa) and before subtracting the antenna gain.

Lets break this issue in two:
1. Downlinks get rejected, even if duty cycle enforcement is not enabled.

2. Currently there is no option do compensate for cable loss.

Sounds good splitting the issue in two, but I am not sure we want an option to compensate for cable loss.

The minimum antenna gain should always be 2 dBi if I'm not mistaken, but what you try to achieve is to compensate for the potential cable loss (e.g. very long cable). Wouldn't it be better to add a separate option for this?

There are antennas with a gain smaller than 2 dBi, even if those are small antennas you usually do not want to have on a gateway (see for example https://www.mouser.fr/datasheet/2/418/9/ENG_DS_L9000149_01_A-3238949.pdf). I don't think there is a need to compensate for a cable loss, this is traditionally included in the antenna gain, and represents the difference between the power at the transmitter level and the radiated power. It is how chirpstack-concentratord interprets that to compute the transmit power to be send to the SX12xx chip and that part is correct and works fine.
I still believe that what is done for the power at the duty cycle tracking level is not correct. The inherent problem is that the SX12xx transmit power is matched with the radiated power of the regulation, and in addition EIRP vs ERP.
In my opinion, this is what should be done:

the TX power should be matched to the regulation without the antenna gain, basically the TX power that is in the MQTT packet is the one to consider
either the ERP power from the regulation has to be converted to EIRP by adding 2 (rounded from 2.15) or the EIRP power from the MQTT packet has to be converted into an ERP by subtracting 2. Alternatively the regulation can be update to use EIRP values instead of ERP.

Thanks, I'm not an expert in antennas, so this is very helpful information. Maybe updating the regulation config to EIRP might be even better, because then we are dealing with one unit, not two (there is no guarantee that future regulations will be in ERP only). Maybe we could define the values as tx_power_max: 14 + 2, just to make it explicit that we have added 2 on purpose (and a comment for the first entry). If we change it to 16 and when the context is forgotten, it might look as a mistake.
I will try to look into this later today / tomorrow. If you would like to create a PR for this, that would be great as well :)

@aurel32 could you review these changes, I believe this is what you proposed:
https://github.com/chirpstack/chirpstack-concentratord/compare/fix_issue_157

@aurel32 could you review these changes, I believe this is what you proposed:
https://github.com/chirpstack/chirpstack-concentratord/compare/fix_issue_157

Thanks a lot for the quick fix. This definitely corresponds to what I described. I also tested the resulting chirpstack-concentratord-sx1302 binary and I confirm it works as expected.

Thanks @aurel32 for testing. This has been released as v4.4.1.


Onboard opensearch-java to new release process

Is your feature request related to a problem? Please describe
Opensearch-java is still using old release process. Need to onboard it to new one using one-click release.
Describe the solution you'd like
Adapt to #1234
Describe alternatives you've considered
Continue using what we have
Additional context
No response

cc: @wbeckler @bbarani


error upgrading connection: unable to upgrade connection

=======Following is my error logs=========
$ kubevpn connect
get cidr from cluster info...
get cidr from cluster info ok
get cidr from cni...
get cidr from svc...
get cidr from svc ok
traffic manager not exist, try to create it...
pod kubevpn-traffic-manager-f89667975-d4qwg is Pending
Type Reason Message
pod kubevpn-traffic-manager-f89667975-d4qwg is Running
Container     Reason           Message
control-plane ContainerRunning
vpn           ContainerRunning
webhook       ContainerRunning
update ref count successfully
error upgrading connection: unable to upgrade connection:
Resource not found

error upgrading connection: unable to upgrade connection:
Resource not found

prepare to exit, cleaning up
update ref count successfully
clean up successful
======= Env Info =========

K3s
Mac Apple M2

It looks like a k8s client-go error，can you try it again? by the way, apple m1 is not support to install k3s, are you using docker?

Referring to official document, arm is supported.
https://docs.k3s.io/?_highlight=arm
And telepresence is worked for me.

➜  ~ curl -sfL https://get.k3s.io | sh -
[ERROR]  Can not find systemd or openrc to use as a process supervisor for k3s
➜  ~ uname
Darwin
➜  ~ uname -m
arm64
Looks like can not install by this way?

did you try kubevpn connect again ?

can you provide your kubeconfig and pod cidr and service cidr, let me to locate problem ?

@wencaiwulue yes, i tried kubevpn connect many times, following link may help you to install k3s.
https://docs.k3s.io/installation/configuration.
By the way, I installed k3s cluster on top of Parallels Desktop，using openEuler as the VM Guest OS.
And your latest question:

kubeconfig

apiVersion: v1
clusters:
  - cluster:
      certificate-authority-data: ***
      #   insecure-skip-tls-verify: true
      server: https://<IP_ADDRESS>:6443
    name: default
contexts:
  - context:
      cluster: default
      user: default
    name: default
current-context: default
kind: Config
preferences: { }
users:
  - name: default
    user:
      client-certificate-data: xxx
      client-key-data:  xxx

pod cidr:   <IP_ADDRESS>/24
service cidr:   <IP_ADDRESS>/24

Thanks.

Ok, got it, i will try to test it on k3s, i tested it on TKE, VKE，ACK, Minikube and it works well. that's very weird

Ok, got it, i will try to test it on k3s, i tested it on TKE, VKE，ACK, Minikube and it works well. that's very weird

That's sounds great, kubevpn seems to be a lightweight and powerful solutions.

i use a linux to install k3s, and use copy kubeconfig to my local pc, use kubevpn to connect, it works well. maybe i needs to install a Parallels Desktop and openEuler to setup k3s ?

If you have interest, can you add my wecat:fcw895703375 and maybe we can use Tencent Meetting to diagnose the problem online ?

If you have interest, can you add my wecat:fcw895703375 and maybe we can use Tencent Meetting to diagnose the problem online ?

I am trying to upgrade my k3s version (1.24 currently) and test again.
I will get in touch with you  if suffering from same fails.

we found that k3s master node can't port-forward

I reinstall k3s cluster, and then test passed.


[Darwin] Need new API to suspend operations

For Darwin framework clients that wishes to go away for any reason (e.g. about to disconnect from network) and that wants devices to stop sending subscription reports, there should be an API.
This API should be on MTRDeviceController and be named something similar to "suspend / resume" but more applicable to the Matter API.

https://github.com/project-chip/connectedhomeip/issues/29273


Creating a new site with Browser leads to 404 error

Previous error #1119 has been fixed but the browser still does not allow the creation of a site.
Steps:
Download SAFE Browser v0.15.4.beta.2 Appimage
Start safe-authd
Start CLI and login
Start SAFE Browser
(EDIT: logging in and lanching brower from SNAPP  makes no difference)
Enter nonsese URL safe://frwer3r3ssdd
"Nobody owns this address yet"
Click on Register safe://frwer3r3ssdd
Click on Create site
"404 Not found"
Windows 10 and Ubuntu 19.10
Shared vault
v0.15.4.beta.2

Aha, @JPL1 I think you're missing the auth request in whatever form of authd you have running. This would lead to the browser auth timing out, and then an attempt to load an emtpy page.
ATM SNAPP does not jump into focus with auth requests, so you'll need to manually focus the app to auth the request.
Equally, with the command line authd, you have to manually trigger 'accept', which is best done via watching the authd logs (for me: tail -f $TMPDIR/safe-authd.out, and getting the request ID, and then running safe auth allow <request-id>.


Publish https://tron.network/ source code

Please publish the https://tron.network/ website on GitHub in the tronprotocol account.
I saw an error on the page and wanted to fix it. But I couldn't find the source code on GitHub.

The error can be written here, thanks.

I already forgot it. It was probably a typo I could have sent a PR for.


Getting started should not use images/screenshots

I feel we need consistent size/sharp schematic UX if we want to show them:

//cc @misolori

@bpasero are you suggesting to use illustrations instead? And if we do use images to have the size be consistent?

Consistent sharpness seems to be the main issue, especially with the latest batch I added. I can fix that in the figma export step.
We have some illustrations we want to test but its hard to get them for every entry.

Yes, illustrations and not actual screen shots. ideally SVGs that scale with any resolution.

We can support SVGs for ourselves, but there are some security concerns with rendering extension-provided SVGs, even in an iframe as far as I understand. @mjbvz may be able to fill in more info.

Continued in #125877


TS-4920: Consolidate accept socket options.

We have an object AcceptOptions that contains the options to apply
to listening sockets, but in many places, the individual options
are passed around. Consolidate this so that we pass a AcceptOptions
to provide better guarantees that all listening sockets are created
equal.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/912/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/807/ for details.

Ping @bryancall @amc?

@jpeach Good job!
And I have my own thoughts on AcceptOptions optimization, but it is quite basic and rough.

class NetVCOptions as base class and defined in iocore/net/I_NetVConnection.h
class AcceptOptions : public NetVCOptions and defined in iocore/net/I_NetAccept.h (moved it from P_NetAccept.h)
class HttpSessionAcceptOptions : public AcceptOptions and defined in proxy/http/HttpSessionAccept.h


Record videos for notebook 04

Done, finished recording 36 videos for 04 today. Woohoo!!!! Onto section 05!


Segmentation fault when running examples on Ubuntu 14.04

When running the example non_blocking, I get:
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused

ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused

bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
PortAudio:
version: 1899
version text: Ok("PortAudio V19-devel (built Feb 25 2014 21:08:14)")
host count: 2
default host: Some(
    HostApiInfo {
        struct_version: 1,
        host_type: ALSA,
        name: "ALSA",
        device_count: 8,
        default_input_device: Some(
            DeviceIndex(
                6
            )
        ),
        default_output_device: Some(
            DeviceIndex(
                6
            )
        )
    }
)
Default input device info: DeviceInfo {
    struct_version: 2,
    name: "default",
    host_api: 0,
    max_input_channels: 128,
    max_output_channels: 128,
    default_low_input_latency: 0.021333333333333333,
    default_low_output_latency: 0.021333333333333333,
    default_high_input_latency: 0.021333333333333333,
    default_high_output_latency: 0.021333333333333333,
    default_sample_rate: 48000
}
Default output device info: DeviceInfo {
    struct_version: 2,
    name: "default",
    host_api: 0,
    max_input_channels: 128,
    max_output_channels: 128,
    default_low_input_latency: 0.021333333333333333,
    default_low_output_latency: 0.021333333333333333,
    default_high_input_latency: 0.021333333333333333,
    default_high_output_latency: 0.021333333333333333,
    default_sample_rate: 48000
}
Segmentation fault (core dumped)

When doing a stacktrace with gdb:
(gdb) backtrace
#0  0xb7f977d4 in ?? () from /usr/lib/i386-linux-gnu/libportaudio.so.2
#1  0xb7f97d4c in Pa_IsFormatSupported ()
   from /usr/lib/i386-linux-gnu/libportaudio.so.2
#2  0x8001bd9a in portaudio::is_format_supported (maybe_input_parameters=...,
    maybe_output_parameters=..., sample_rate=44100) at src/lib.rs:661
#3  0x80005f5b in non_blocking::PortAudio::is_duplex_format_supported<f32,f32>
    (self=0xbfffeed0, in_params=..., out_params=..., sample_rate=44100)
    at src/lib.rs:404
#4  0x80004a51 in non_blocking::run () at examples/non_blocking.rs:50
#5  0x80003653 in non_blocking::main () at examples/non_blocking.rs:18
#6  0x8002797b in sys_common::unwind::try::try_fn::h10144795978809605109 ()
#7  0x80025268 in __rust_try ()
#8  0x8002743a in rt::lang_start::he74f855a6a899d05rKz ()
#9  0x8000552e in main () at ../src/libcore/result.rs:29

A similar thing happens to blocking.rs, saw.rs, sine.rs, but not on devices.rs or hosts.rs.
I suspect that some struct passed to the C functions isn't correct.

Hmm this might have something to do with not having the linux ALSA extension header bindings set up yet. We only have bindings to the general portaudio.h so far. #22 is the related issue.
Would you mind running the devices.rs and hosts.rs examples and posting their output to here?
I only have OS X available to me at the moment, but I'm hoping to use rust-portaudio w/ ALSA for some embedded audio stuff mid-next month which is when I was planning on having a go at this. It shouldn't be too tricky to run rust-bindgen on the necessary header and set it up (I'm happy for someone else to beat me to it).

I can't get into the computer on which I've initially done that, but on another computer, also running Ubuntu 14.04, but running Pulseaudio, I get the same error and I get:
When running non_blocking using cargo:
     Running `target/debug/examples/non_blocking`
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
jack_client_new: deprecated
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
jack_client_new: deprecated
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
PortAudio:
version: 1899
version text: Ok("PortAudio V19-devel (built Feb 25 2014 21:08:14)")
host count: 2
default host: Some(
    HostApiInfo {
        struct_version: 1,
        host_type: ALSA,
        name: "ALSA",
        device_count: 8,
        default_input_device: Some(
            DeviceIndex(
                7
            )
        ),
        default_output_device: Some(
            DeviceIndex(
                7
            )
        )
    }
)
Default input device info: DeviceInfo {
    struct_version: 2,
    name: "default",
    host_api: 0,
    max_input_channels: 32,
    max_output_channels: 32,
    default_low_input_latency: 0.008707482993197279,
    default_low_output_latency: 0.008707482993197279,
    default_high_input_latency: 0.034829931972789115,
    default_high_output_latency: 0.034829931972789115,
    default_sample_rate: 44100
}
Default output device info: DeviceInfo {
    struct_version: 2,
    name: "default",
    host_api: 0,
    max_input_channels: 32,
    max_output_channels: 32,
    default_low_input_latency: 0.008707482993197279,
    default_low_output_latency: 0.008707482993197279,
    default_high_input_latency: 0.034829931972789115,
    default_high_output_latency: 0.034829931972789115,
    default_sample_rate: 44100
}
An unknown error occurred

When running devices.rs:
Running `target/debug/examples/devices`
ALSA lib pcm_dsnoop.c:618:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
jack_client_new: deprecated
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
jack_client_new: deprecated
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Number of devices = 6
Defualt input device: Ok(DeviceIndex(5))
Defualt output device: Ok(DeviceIndex(5))
All devices:
--------------------------------------- DeviceIndex(0)
DeviceInfo {
    struct_version: 2,
    name: "HDA Intel: ALC1200 Digital (hw:0,1)",
    host_api: 0,
    max_input_channels: 2,
    max_output_channels: 2,
    default_low_input_latency: 0.005804988662131519,
    default_low_output_latency: 0.008707482993197279,
    default_high_input_latency: 0.034829931972789115,
    default_high_output_latency: 0.034829931972789115,
    default_sample_rate: 44100
}
Supported standard sample rates for half-duplex 16-bit 2 channel input:
	44100hz
	48000hz
	96000hz
Supported standard sample rates for half-duplex 16-bit 2 channel output:
	44100hz
	48000hz
	88200hz
	96000hz
	192000hz
Supported standard sample rates for full-duplex 16-bit 2 channel input, 2 channel output:
	44100hz
	48000hz
	96000hz
--------------------------------------- DeviceIndex(1)
DeviceInfo {
    struct_version: 2,
    name: "HDA Intel: ALC1200 Alt Analog (hw:0,2)",
    host_api: 0,
    max_input_channels: 2,
    max_output_channels: 0,
    default_low_input_latency: 0.005804988662131519,
    default_low_output_latency: -1,
    default_high_input_latency: 0.034829931972789115,
    default_high_output_latency: -1,
    default_sample_rate: 44100
}
Supported standard sample rates for half-duplex 16-bit 2 channel input:
	44100hz
	48000hz
	96000hz
Supported standard sample rates for half-duplex 16-bit 0 channel output:
Supported standard sample rates for full-duplex 16-bit 2 channel input, 0 channel output:
--------------------------------------- DeviceIndex(2)
DeviceInfo {
    struct_version: 2,
    name: "iec958",
    host_api: 0,
    max_input_channels: 0,
    max_output_channels: 2,
    default_low_input_latency: -1,
    default_low_output_latency: 0.005804988662131519,
    default_high_input_latency: -1,
    default_high_output_latency: 0.034829931972789115,
    default_sample_rate: 44100
}
Supported standard sample rates for half-duplex 16-bit 0 channel input:
Supported standard sample rates for half-duplex 16-bit 2 channel output:
	44100hz
	48000hz
	88200hz
	96000hz
	192000hz
Supported standard sample rates for full-duplex 16-bit 0 channel input, 2 channel output:
--------------------------------------- DeviceIndex(3)
DeviceInfo {
    struct_version: 2,
    name: "spdif",
    host_api: 0,
    max_input_channels: 2,
    max_output_channels: 2,
    default_low_input_latency: 0.005804988662131519,
    default_low_output_latency: 0.008707482993197279,
    default_high_input_latency: 0.034829931972789115,
    default_high_output_latency: 0.034829931972789115,
    default_sample_rate: 44100
}
Supported standard sample rates for half-duplex 16-bit 2 channel input:
	44100hz
	48000hz
	96000hz
Supported standard sample rates for half-duplex 16-bit 2 channel output:
	44100hz
	48000hz
	88200hz
	96000hz
	192000hz
Supported standard sample rates for full-duplex 16-bit 2 channel input, 2 channel output:
	44100hz
	48000hz
	96000hz
--------------------------------------- DeviceIndex(4)
DeviceInfo {
    struct_version: 2,
    name: "pulse",
    host_api: 0,
    max_input_channels: 32,
    max_output_channels: 32,
    default_low_input_latency: 0.008707482993197279,
    default_low_output_latency: 0.008707482993197279,
    default_high_input_latency: 0.034829931972789115,
    default_high_output_latency: 0.034829931972789115,
    default_sample_rate: 44100
}
Supported standard sample rates for half-duplex 16-bit 32 channel input:
	8000hz
	9600hz
	11025hz
	12000hz
	16000hz
	22050hz
	24000hz
	32000hz
	44100hz
	48000hz
	88200hz
	96000hz
	192000hz
Supported standard sample rates for half-duplex 16-bit 32 channel output:
	8000hz
	9600hz
	11025hz
	12000hz
	16000hz
	22050hz
	24000hz
	32000hz
	44100hz
	48000hz
	88200hz
	96000hz
	192000hz
Supported standard sample rates for full-duplex 16-bit 32 channel input, 32 channel output:
	8000hz
	9600hz
	11025hz
	12000hz
	16000hz
	22050hz
	24000hz
	32000hz
	44100hz
	48000hz
	88200hz
	96000hz
	192000hz
--------------------------------------- DeviceIndex(5)
DeviceInfo {
    struct_version: 2,
    name: "default",
    host_api: 0,
    max_input_channels: 32,
    max_output_channels: 32,
    default_low_input_latency: 0.008707482993197279,
    default_low_output_latency: 0.008707482993197279,
    default_high_input_latency: 0.034829931972789115,
    default_high_output_latency: 0.034829931972789115,
    default_sample_rate: 44100
}
Supported standard sample rates for half-duplex 16-bit 32 channel input:
	8000hz
	9600hz
	11025hz
	12000hz
	16000hz
	22050hz
	24000hz
	32000hz
	44100hz
	48000hz
	88200hz
	96000hz
	192000hz
Supported standard sample rates for half-duplex 16-bit 32 channel output:
	8000hz
	9600hz
	11025hz
	12000hz
	16000hz
	22050hz
	24000hz
	32000hz
	44100hz
	48000hz
	88200hz
	96000hz
	192000hz
Supported standard sample rates for full-duplex 16-bit 32 channel input, 32 channel output:
	8000hz
	9600hz
	11025hz
	12000hz
	16000hz
	22050hz
	24000hz
	32000hz
	44100hz
	48000hz
	88200hz
	96000hz
	192000hz

When running hosts.rs:
     Running `target/debug/examples/hosts`
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
jack_client_new: deprecated
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
jack_client_new: deprecated
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Default Host API: Ok(0)
All Host APIs:
(
    0,
    HostApiInfo {
        struct_version: 1,
        host_type: ALSA,
        name: "ALSA",
        device_count: 8,
        default_input_device: Some(
            DeviceIndex(
                7
            )
        ),
        default_output_device: Some(
            DeviceIndex(
                7
            )
        )
    }
)
(
    1,
    HostApiInfo {
        struct_version: 1,
        host_type: OSS,
        name: "OSS",
        device_count: 0,
        default_input_device: None,
        default_output_device: None
    }
)

fyi, i was seeing this with debian bullseye as well, however, it seems to be resolved with portaudio 19.6.0-1.1


change dataset order and log_prob call in snle.

This change has no direct consequences, it is just about naming.
Our variable names for the batches were just wrong, because in SNLE the data set is built as (x, theta) not as (theta, x).
Now, it is (theta, x) again, as one would expect, and the call to log_prob is changed accordingly.

Codecov Report

Merging #364 into main will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #364      +/-   ##
==========================================
- Coverage   74.09%   74.08%   -0.01%
==========================================
  Files          49       49
  Lines        2841     2840       -1
==========================================
- Hits         2105     2104       -1
  Misses        736      736

Flag
Coverage Δ

#unittests
74.08% <100.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

sbi/inference/snle/snle_base.py
95.12% <100.00%> (-0.06%)
: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 d0fe846...400141b. Read the comment docs.


Cow: Watch conversionfree.com

Cow requests the watch of the watch_keyword conversionfree\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

conversionfree\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.


[WIP] Goodbye Grit!

This PR so far:

Refactors the revert method (see here)
Reactivates revert tests

Todo:

[x] Wait until new rugged adapter release
[ ] Require the new version of rugged adapter / cleanup Gemfile
[ ] Reactive revert tests
[ ] Make sure the RJGit adapter also supports the new revert method
[x] Set rugged as default adapter
[ ] Remove all references to grit

The tests currently fail because they are being run with the grit adapter.
@bartkamphorst I won't have time to work on this for a bit. If you have any time and want to get started on a Git#revert method for the RJGit adapter, that would be great! (See here. It should return a String sha of the newly modified tree (after reverting) and an array of affected filepaths.)

Rugged v0.99 has been released, which includes the required Repo#apply method! 🎈 🎆 🎉 🚀 🕺

Major step towards a 5.x release!

Only Jruby revert tests are failing, as expected until we release a new version of the rjgit adapter with revert support.

This PR should be ready to go once we merge https://github.com/gollum/rjgit_adapter/pull/14


Unhandled command:  PROXY IPV4 TCP <IP_ADDRESS> 53

If I open the wasm client locally and try to connect to a self hosted minetest server, the proxy connection doesn't work:
Proxy listening on port 8888
[CLIENT 1] New client from  [ '', '::ffff:<IP_ADDRESS>' ]
[CLIENT 1] Unhandled command:  PROXY IPV4 TCP <IP_ADDRESS> 53

Here the wasm client output of the browser console of https://localhost/index.html (serves the www build folder):
Uncaught 50077280 [minetest.js:6:5](https://localhost/fca7c8c9d007/minetest.js)
    quit_ https://localhost/minetest/fca7c8c9d007/minetest.js:6
    handleException https://localhost/fca7c8c9d007/minetest.js:1255
    callUserCallback https://localhost/fca7c8c9d007/minetest.js:2240
    ...

this.proxyUrl in launcher.js is set to ws://localhost:8888. The original url wss://minetest.dustlabs.io/proxy works.
https://github.com/paradust7/minetest-wasm/blob/e8f754e1c59517be978935935849be61352cfc40/static/launcher.js#L576
this.vpn is null - could that be the reason?
https://github.com/paradust7/minetest-wasm/blob/e8f754e1c59517be978935935849be61352cfc40/static/launcher.js#L573
Are some additional settings necessary?

Just to make sure I understand, you're running a minetest server outside of the browser? On localhost?

Just to make sure I understand, you're running a minetest server outside of the browser? On localhost?

Correct, I run a minetest server outside of the browser, accessible via a public domain (not on local host). The client for the browser and the proxy run local.
As I mentioned, with one of your public proxy servers everything works fine, without any other changes.


Compatibility to cf workers

without node compatibility, trying to access process will result in build issues. Checking if process is available will make builds work fine.

@bkniffler  thanks

published 11.0.2

Cheers!


Fixing an issue where CreateInstances could be called before Awake

Overview
Fixing an issue where CreateInstances could be called before Awake. Which would in turn try and set the shared materials to null.
This would only occur in scenes with very specific hierarchy setups where a clipping primitive was placed in the hierarchy after a renderer it reference which is also initially disabled.
Issue found by @radicalad.
Verification
Please test scenes and scripts which heavily use ClippingPrimitives.

/azp run

/azp run


RS3 Music Plugin

Would it be possible for the Music plugin to have an option to replace the original soundtrack with their RS3 counterparts where applicable?
As good as the soundtrack is, RS3's orchestral melodies are phenomenal & I think a lot of people would play without the game muted if implemented.

Duplicate of #3390 (see final comment btw)


Bump Go version to 1.7.0

Signed-off-by: Dieter Reuter<EMAIL_ADDRESS>

LGTM!
Might even consider switching this to golang:1.7.0-alpine since we're not doing anything Debian-specific

I already tested it with golang:1.7.0-alpine, but this causes some errors. 😇

just need to apk add --update --no-cache git in the Dockerfile.  I'm surprised the Golang alpine distributions don't include it actually.


Progressive Load on Local Cached Video

I use react-native-fs to preload videos and put them on user's mobile.
I'm expecting that when the video is loaded on the local device, it can be progressively loaded.
However when i try to put the URI source to the path all i get is
2020-03-04 07:51:37.401 'video props source ', { uri: '/Users/soqqlepteltd/Library/Developer/CoreSimulator/Devices/60177C63-6FC9-47EE-89F7-73AA3D940FD2/data/Containers/Data/Application/04E48EAF-7C63-40F7-A797-6E45B5A32077/Documents/1583278564271.mp4' }
2020-03-04 07:51:37.414 starting onloadstart
2020-03-04 07:51:37.426 'onerror ', { error: { code: -1100, domain: 'NSURLErrorDomain' },
  target: 299 }

-1100 code i believe is file not found.  I set the URI when react-native-fs 's progress method is called. But now i just double checked, that the file is not saved until the whole download is completed.
Any ideas if anyone has done this before?
Platform
Need on both ios / android
Environment info
React native info output:
System:
    OS: macOS 10.14.6
    CPU: (8) x64 Intel(R) Core(TM) i5-8279U CPU @ 2.40GHz
    Memory: 21.14 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 10.17.0 - /usr/local/bin/node
    Yarn: 1.21.1 - /usr/local/bin/yarn
    npm: 6.11.3 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
  IDEs:
    Android Studio: 3.5 AI-191.8<IP_ADDRESS>77832
    Xcode: 11.3/11C29 - /usr/bin/xcodebuild
  npmPackages:
    @react-native-community/cli: ^3.0.4 => 3.0.4
    react: ^16.12.0 => 16.12.0
    react-native: 0.61.2 => 0.61.2
  npmGlobalPackages:
    react-native-cli: 2.0.1

"react-native-video": "^5.0.2",
Steps To Reproduce

Download a file with react-native-fs
Hook up the local file to react-native-video

Did you figure this out, was trying to do something similar in order to get it working like a local proxy server for videos to load and play faster?

Has the problem been solved? Why is it closed?

I ended up making my videos m3u8 (hls)
And even if the files were mp4, the files were already progressively loading from my s3 bucket (as long as i set the mime correctly in the bucket)

Hi @enigmablue , After you converted m3u8, what you did do next? How you downloaded the video and played it as a local file?

The m3u8 is just saved in my aws s3 bucket. And i just load the link into my video player and it iwll play progressively.


Add simple performance testing

I want to start some basic performance testing, this is a naive version of the implementation. I think we can build from here.
What do you think? @glennsl @bordoley

If we're really serious about perf testing for micro optimization of these small O(1) functions, it probably makes sense to adopt a framework like corebench. In native, the main cause of perf issues is gc cleanup. JS makes this worst introducing a penalty for allocating as well. There are some other techniques that can be used to improve pure cpu bound code, such as preferring if/else chains over pattern matching when possible, but these are hacks that ideally the compiler would render unnecessary. In native, we have flambda now which helps. In Bucklescript, I imagine this introduces a tradeoff between readability and perf.
For context, Imm.re's test do use the technique your using, but my goal is to use them to identify outlier functions that don't seem to have the right characteristics and then hunt for whatever code is unnecessarily allocating memory.

I think my goal is to benchmark and find out the best practices to use this library, for example with the data gathered we can convince users to use more 'a option rather than using OrRaise version of the functions. Also with a bit statistics gathered we can build confidence in how well this library will perform. Although it is not a goal for us to be the most performant library, we still want to be reasonably fast, which aligns what you are doing with Imm.re


The line # is not correct in log file

The line # is not correct in log file, almost all of line # in log entries is located to entry.go:314.

It's fixed, and close the issue.


openhmd: init at 0.3.0-rc1-20181218

What? Why?
New package: a KISS library for doing VR stuff. I felt like writing an expression for it simply because it is the only one that does something VR and adheres to the KISS principle (i.e. I don't even have an HMD, made an expression purely for religious reasons :]).
git log

openhmd: init at 0.3.0-rc1-20181218

nix-instantiate environment

Host OS: Linux 4.9, SLNOS 19.03
Nix: nix-env (Nix) 2.1.3
Multi-user: yes
Sandbox: yes
NIXPKGS_CONFIG:

{
  checkMeta = true;
  doCheckByDefault = true;
}

nix-env -qaP diffs

On x86_64-linux:

New (1):

openhmd

On aarch64-linux: ditto

On x86_64-darwin: ditto

Things done

[X] Built before rebasing on master.
[X] Examples from the package run fine with the dummy driver.

ping @7c6f434c @Ericson2314 (I want a "ping a random person with commit access" button)

Thanks!

Re: button: To be honest, simple package additions do usually get into some broad-swiping «let's review simple stuff» pass that some committers (not me) do nowadays.
(You can always use me as a random person with commit access — it is always something technically sound, and either something I merge soon, something I merge if noone cares to object, or something where I do want to follow the comments because it's a high-quality controversy and knowing the current layout of opinions on tradeoffs might be useful information even if I can predict the net outcome)

I see, noted, thanks.

a high-quality controversy

:)


Investigate and try and fix memory spike issue with running scheduling

Closing based on discussion with @parkerabercrombie at last week's performance working group


local tunnel is down?

Localtunnel send me an error 503. why? please help me, thanks.

Sorry about that, the server will be back up shortly.

Is it still down ?
I tried this lt -p 8084 -h "https://myapp.localtunnel.me"
It gives me nothing, please help

Hey @jagadeeshkoka, the service should be up.
your command seems to be off though, it should be:
lt -p 8084 -s myapp and that'll try to give you the subdomain myapp.loca.lt

Hey @jagadeeshkoka, the service should be up. your command seems to be off though, it should be: lt -p 8084 -s myapp and that'll try to give you the subdomain myapp.loca.lt

I tried that its not returning anything

Hey @jagadeeshkoka can you try again. Seems like the ssl cert was expired for localtunnel.me


[Tree Details - Design] No Image Tree Filler + Photo Upload

For trees with no image at, we can add a default filler no tree image similar to this ticket https://github.com/waterthetrees/wtt_front/issues/691
we want a way so users know this tree has no data. Will have a message stating no image for tree available, take a picture if you can.
Will work on a prototype for both desktop and mobile.

Some trees don't have any tree photo and can be confusing for people as it only shows the data with no context of the tree looks like. To alert users that a photo is needed for the tree we can signal it by having a box with no photo available. This will then tell the user that this tree needs more info.
When the user hovers over the nonexistent image there will be a message of "please upload a picture" which will then give the user a hint of what needs to occur if they have the information.


Unable to change branch rules

@neilslinger i'm unable to change branch rules in this repo, as well as several others.

Looks like I'm also missing some perms on jupyterlab_templates

Thanks @neilslinger!


Content changes for Stocks

What is the context of this PR?
This PR is for some more content changes to stocks. Rewording, removing bullet points etc
How to review
Survey launches and looks ok

 2. Stocks Change Required from CAT Testing

 3. Stocks Change Required from CAT Testing

 4. Stocks Change Required from CAT Testing

 5. Stocks Change Required from CAT Testing

 1. Stocks Change Required from CAT Testing


Dont work camera on Android

Last plugin version. iOS works fine, when try to open camera/gallery on Android - nothing happens both in devices and emulator (no matter what version).
 $scope.takePhoto = function () {
        var options = {
            quality: 75,
            destinationType: Camera.DestinationType.DATA_URL,
            sourceType: Camera.PictureSourceType.CAMERA,
            allowEdit: false,
            encodingType: Camera.EncodingType.JPEG,
            targetWidth: 217,
            targetHeight: 217,
            popoverOptions: CameraPopoverOptions,
            saveToPhotoAlbum: false
        };

Tried to remove and add plugin and thats doesnt help... What shout I do?

Cordova CI Build has completed successfully.
Commit     - Link
Dashboard - Link

Builder Name
Console Output
Test Report
Device Logs

Windows 8.1 Store
Link
Link
Link

Windows 10  Store
Link
Link
Link

Windows 8.1 Phone
Link
Link
Link

iOS
Link
Link
Link

Android
Link
Link
Link

Thank you @thedoorbell

Cordova CI Build has one or more failures.
Commit     - Link
Dashboard - Link

Builder Name
Console Output
Test Report
Device Logs

Windows 8.1 Store
Link
Link
Link

Windows 10  Store
Link
Link
Link

Windows 8.1 Phone
Link
Link
Link

iOS
Link
Link
Link

Android
Link
Link
Link

Cordova CI Build has one or more failures.
Commit     - Link
Dashboard - Link

Builder Name
Console Output
Test Report
Device Logs

Windows 8.1 Store
Link
Link
Link

Windows 10  Store
Link
Link
Link

Windows 8.1 Phone
Link
Link
Link

iOS
Link
Link
Link

Android
Link
Link
Link

Cordova CI Build has one or more failures.
Commit     - Link
Dashboard - Link

Builder Name
Console Output
Test Report
Device Logs

Windows 8.1 Store
Link
Link
Link

Windows 10  Store
Link
Link
Link

Windows 8.1 Phone
Link
Link
Link

iOS
Link
Link
Link

Android
Link
Link
Link

Cordova CI Build has one or more failures.
Commit     - Link
Dashboard - Link

Builder Name
Console Output
Test Report
Device Logs

Windows 8.1 Store
Link
Link
Link

Windows 10  Store
Link
Link
Link

Windows 8.1 Phone
Link
Link
Link

iOS
Link
Link
Link

Android
Link
Link
Link

Cordova CI Build has completed successfully.
Commit     - Link
Dashboard - Link

Builder Name
Console Output
Test Report
Device Logs

Windows 8.1 Store
Link
Link
Link

Windows 10  Store
Link
Link
Link

Windows 8.1 Phone
Link
Link
Link

iOS
Link
Link
Link

Android
Link
Link
Link

Cordova CI Build has completed successfully.
Commit     - Link
Dashboard - Link

Builder Name
Console Output
Test Report
Device Logs

Windows 8.1 Store
Link
Link
Link

Windows 10  Store
Link
Link
Link

Windows 8.1 Phone
Link
Link
Link

iOS
Link
Link
Link

Android
Link
Link
Link

Cordova CI Build has completed successfully.
Commit     - Link
Dashboard - Link

Builder Name
Console Output
Test Report
Device Logs

Windows 8.1 Store
Link
Link
Link

Windows 10  Store
Link
Link
Link

Windows 8.1 Phone
Link
Link
Link

iOS
Link
Link
Link

Android
Link
Link
Link

Cordova CI Build has one or more failures.
Commit     - Link
Dashboard - Link

Builder Name
Console Output
Test Report
Device Logs

Windows 8.1 Store
Link
Link
Link

Windows 10  Store
Link
Link
Link

Windows 8.1 Phone
Link
Link
Link

iOS
Link
Link
Link

Android
Link
Link
Link

Cordova CI Build has one or more failures.
Commit     - Link
Dashboard - Link

Builder Name
Console Output
Test Report
Device Logs

Windows 8.1 Store
Link
Link
Link

Windows 10  Store
Link
Link
Link

Windows 8.1 Phone
Link
Link
Link

iOS
Link
Link
Link

Android
Link
Link
Link

Cordova CI Build has one or more failures.
Commit     - Link
Dashboard - Link

Builder Name
Console Output
Test Report
Device Logs

Windows 8.1 Store
Link
Link
Link

Windows 10  Store
Link
Link
Link

Windows 8.1 Phone
Link
Link
Link

iOS
Link
Link
Link

Android
Link
Link
Link

Cordova CI Build has one or more failures.
Commit     - Link
Dashboard - Link

Builder Name
Console Output
Test Report
Device Logs

Windows 8.1 Store
Link
Link
Link

Windows 10  Store
Link
Link
Link

Windows 8.1 Phone
Link
Link
Link

iOS
Link
Link
Link

Android
Link
Link
Link

This is not the best place to report issues. Try to search for an existing issue in project's JIRA or file a new one as described here. Also you can ask your questions on Slack

Cordova CI Build has one or more failures.
Commit     - Link
Dashboard - Link

Builder Name
Console Output
Test Report
Device Logs

Windows 8.1 Store
Link
Link
Link

Windows 10  Store
Link
Link
Link

Windows 8.1 Phone
Link
Link
Link

iOS
Link
Link
Link

Android
Link
Link
Link


CI broken due to conda-forge openmpi update

conda-forge seems to have updated the package for openmpi in a way that is now breaking the CI. We'll need to figure out why this is happening and if there's a workaround. See here for details.

It appears that this will be resolved with this PR to mpi-feedstock.


Invoice sequence number  mentioned in the invoice attached to the email is not as per format

Describe the bug
The invoice number format for the invoice is IN-Client code-Project code - sequence number .  The invoice number available in the invoice sent though ,email has format IN-Client code-Project code - sequence number-monthyear.

The issue has been fixed


Buggy RLS filter implementation

This line looks wrong:
https://github.com/ar1st0crat/NWaves/blob/c1a6a4a8fdb70ce7cfd6b31ad59595e8461ff2e5/NWaves/Filters/Adaptive/RlsFilter.cs#L112
Are there any tests to make sure that this implementation behave correctly?

Looks like an ordinary matrix multiplication (straightforward implementation, not the most efficient, though). I didn't write tests for adaptive filters, but there are demo forms that allow us checking the results. In particular, this form:

Even if implementation idea is correct, the matrix multiplication I linked above is flawed. One needs +=. Otherwise older values are overwritten.

You're right - it's a bug; it should be +=. Thanks for noticing. I'll double-check this and fix it when I have the time


A filtered settings view resets to unfiltered view after a couple of seconds

Environment data

VS Code version: 1.47.3
Extension version (available under the Extensions sidebar): 2020.7.96456
OS and version: Windows 10
Python version (& distribution if applicable, e.g. Anaconda): 3.8.5
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
Value of the python.languageServer setting: Pylance (of course!)

Expected behaviour
Go to Settings UI
Type the setting to look for in the top text box
Choose one the extensions in the left nav of the settings page
Observe that the search result are reduced to a filtered view
Actual behaviour
The view stays filtered for a couple of seconds and then reverts back to results for all extensions
Steps to reproduce:
Go to Settings UI
Type the setting to look for in the top text box
Choose one the extensions in the left nav of the settings page

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

This should be filed on VS Code. We don't control that UI.


Add getting recent docker events

Allow to pull recent recent containers events

:+1: LGTM

Is the ContainerManager really the right place for this? If I understand correctly, this has nothing to do specifically with containers, so maybe it should be in Docker?
Coding standards: we usually put a white line before and after structure blocks like fors and ifs, except before a block that begins another block. For example, the splitEvents method would look like this:
        // ...
        $currentString = '';

        for ($i = 0; $i < strlen($contents); $i++) {
            if ($contents{$i} == '{') {
                $numOfBrackets++;
            }

            if ($contents{$i} == '}') {
                $numOfBrackets--;
            }

            $currentString .= $contents{$i};

            if ($numOfBrackets == 0 ) {
                if (!empty($currentString)) {
                    $retVal[] = new Event(json_decode($currentString, true));
                }

                $currentString = '';
            }
        }
        // ...

Also, +1 for the documentation, and this will also needs tests :)

I moved it into ContainerManager because those are container events. Maybe some new EventMenager? Tell me where you want it and I'll correct it and add docs.

We are talking about http://docs.docker.com/reference/api/docker_remote_api_v1.18/#monitor-dockers-events, right?

Yes.

Well that page says /events can report containers events AND images events

Then it can also report image events:
and Docker images will report:

    untag, delete

So yeah, maybe an EventManager would make sense, maybe something based on https://github.com/symfony/EventDispatcher so that we can easily register listeners to these events, what do you think?

At the moment it uses polling. If you want to dispatch events it should use streaming. It should open /events and asynchronously react to received data converting it to events.
I might be wrong (don't know guzzle so good) but it seems to require guzzle5 with its asynchronous capabilities.

Right, I guess both polling and streaming can have their place in docker-php.
In the end, because /events can report image events, it shouldn't be in ContainerManager, but there might not be a need for an EventManager right now (you're right about the streaming, and we're already talking about switching to egeloen/ivory-http-adapter which would bring in async + psr-7 compliance, so this part should wait) so maybe you can move it to Docker\Docker and that would be fine for now, what do you think?

Hey, I put it into new place. It's not a lot of code but when async is added it will more. I don't want to change api then.
And there is a unit test now.

Ok that's great, ready to merge once the coding style issues are fixed!

poke @ggodlewski, are you going to fix the CS issues? :)

Why was this closed without merge? Are these changes in the code or in another PR?

As you see there were some empty lines missing and instead of just putting them he spent more time on writing comments.
I have a life. I prefer to use and contribute to another project.

@ggodlewski Thank you for the info, sad to hear the PR failed just because of code-formatting.

@ggodlewski sorry that you feel this way, but code formatting is important. If you do not wish to spend the time to respect the work of others by complying to simple rules, that is your right and I hope you find another project to use and contribute to that will suit your needs and philosophy.
In the meantime, I would just like to point that being sarcastic and/or ironic is not necessary, and implying that your time is more valuable than that of other people here is, simply put, rude.


[FEAT]: change proposal into 5 Question

Description
not the paper-type format, but 5Q format
Additional Information
No response

solved in #605 and #588


Use fixtures from DataSpaces-Auth

Utilize the exposed fixtures in the upcoming DataSpaces-Auth release.
This is a draft until a new release of DataSpaces-Auth has happened, which includes SemanticMatter/ds-auth#18.
Edit: This has now happened. v0.2.0 has been released.
~This should be rebased after #59 is merged~ Done.
Another PR should be opened once SemanticMatter/ds-auth#19 has been merged and released in a new DataSpaces-Auth version. This is now expressed via issue #63.
Edit: This has now happened, the newest version is v0.2.1.
Edit: Updated to the newest version: v0.3.0.
Cleaned up ignored warnings for the test suite.

Summary from Copilot

This pull request includes several updates to the `entities_service` to improve logging, dependency management, and testing configurations. The most important changes include updating the logger configuration, modifying environment variable handling for testing, updating dependencies, and refining test fixtures.
Logger Configuration:

Changed the logger initialization to use __name__ instead of a hardcoded string in entities_service/main.py.

Environment Variable Handling:

Removed the manual setup and cleanup of environment variables for testing in entities_service/main.py. [1] [2]

Dependency Updates:

Updated dependencies in pyproject.toml to newer versions, including DataSpaces-Auth and fastapi.
Updated test dependencies and removed deprecated warnings.

Test Fixtures:

Refined test fixtures to use dataspaces_auth.fastapi._pytest_fixtures and updated role handling in tests/conftest.py. [1] [2] [3] [4] [5]
Added a new fixture to avoid raising a user warning for missing realm-export.json.

Test Configuration:

Updated test configuration to use new fixtures and removed unnecessary setup in tests/service/routers/conftest.py. [1] [2]
Modified test files to use the new _mock_openid_url_request fixture. [1] [2]

@quaat @Treesarj I will merge this as is. All CI checks are successful, and it will be good to get this in a new release for further development of the dataspaces.
If any issues should arise due to these changes, or there are comments, please open issues to follow up on this.