esbuild plugin resolves paths incorrectly on Windows

The esbuild plugin does
import { posix as path } from "path";

and uses that to resolve paths. This does not work on Windows. The error I get is
X [ERROR] [plugin vite-plugin-wasm] ENOENT: no such file or directory, open '(project root directory)\client_bg.wasm'

    out/bindgen/client.js:1:22:
      1 │ import * as wasm from "./client_bg.wasm";
        ╵                       ~~~~~~~~~~~~~~~~~~

I would expect the plugin to try to load '(project root directory)\out\bindgen\client_bg.wasm', but path.dirname(args.importer) returns ".".
As a workaround, I've disabled optimizeDeps in vite.config.ts:
import { defineConfig } from "vite";
import solid from "vite-plugin-solid";
import wasm from "vite-plugin-wasm";

export default defineConfig({
    plugins: [
        solid(),
        wasm(),
    ],
    build: {
        target: "esnext",
        outDir: "./out/web",
    },
    optimizeDeps: {
        disabled: true,
    }
});

This works, but isn't ideal.

What's your args.importer value?

@anak1st What's your args.importer value?

@Menci we encountered the same issue:
[0]
[0]   VITE v4.1.1  ready in 962 ms
[0]
[0]   ➜  Local:   http://localhost:8080/
[0]   ➜  Network: use --host to expose
[0] {
[0]   path: './graphite_wasm_bg.wasm',
[0]   importer: 'F:\\Graphite\\Graphite\\frontend\\wasm\\pkg\\graphite_wasm.js',
[0]   namespace: 'file',
[0]   resolveDir: 'F:\\Graphite\\Graphite\\frontend\\wasm\\pkg',
[0]   kind: 'import-statement',
[0]   pluginData: undefined
[0] }
[0] args.path ./graphite_wasm_bg.wasm
[0] args.path F:\Graphite\Graphite\frontend\wasm\pkg\graphite_wasm_bg.wasm
[0] {
[0]   path: './graphite_wasm_bg.wasm',
[0]   importer: 'F:\\Graphite\\Graphite\\frontend\\wasm\\pkg\\graphite_wasm_bg.js',
[0]   namespace: 'file',
[0]   resolveDir: 'F:\\Graphite\\Graphite\\frontend\\wasm\\pkg',
[0]   kind: 'import-statement',
[0]   pluginData: undefined
[0] }
[0] args.path ./graphite_wasm_bg.wasm

Changing the plugin code to not use the posix methods for path resolution works fine for compilation but produces errors down the line:

I don't have a windows machine for local debugging these logs were generated on a friends computer
(pinging @Keavon to keep him up do date)

@TrueDoctor Thanks! I'll get it fixed soon.

Try v3.2.2

Thanks for the quick change @Menci. But it looks like that failed CI so it didn't publish to npm. I tried using that commit hash as the source rather than npm and I get
[0] failed to load config from C:\Users\Keavon\Projects\Graphite\frontend\vite.config.ts
[0] error when starting dev server:
[0] Error: Cannot find module '../dist/index'
[0] Require stack:
[0] - C:\Users\Keavon\Projects\Graphite\frontend\node_modules\vite-plugin-wasm\exports\require.cjs
[0] - C:\Users\Keavon\Projects\Graphite\frontend\vite.config.ts
[0] - C:\Users\Keavon\Projects\Graphite\frontend\node_modules\vite\dist\node\chunks\dep-ca21228b.js
[0]     at Module._resolveFilename (node:internal/modules/cjs/loader:995:15)
[0]     at Module._load (node:internal/modules/cjs/loader:841:27)
[0]     at Module.require (node:internal/modules/cjs/loader:1061:19)
[0]     at require (node:internal/modules/cjs/helpers:103:18)
[0]     at Object.<anonymous> (C:\Users\Keavon\Projects\Graphite\frontend\node_modules\vite-plugin-wasm\exports\require.cjs:1:18)
[0]     at Module._compile (node:internal/modules/cjs/loader:1159:14)
[0]     at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
[0]     at _require.extensions.<computed> [as .js] (file:///C:/Users/Keavon/Projects/Graphite/frontend/node_modules/vite/dist/node/chunks/dep-ca21228b.js:62359:17)
[0]     at Module.load (node:internal/modules/cjs/loader:1037:32)
[0]     at Module._load (node:internal/modules/cjs/loader:878:12)
[0] vite exited with code 1

I'm not sure if that's an issue with our end (I'm working with @TrueDoctor) or if it's caused by the same thing that made 3.2.2 fail CI.

Fixed CI. Now you could try 3.2.2


allow users to just specify any service name within stack for affinity

This is to address lately issue in https://github.com/rancher/rancher/issues/1531

Adding more context:
before, i was being too restrictive and only pre-pending the stack name if the service mentioned is the same service as itself.  This solves the use case like anti-affinity to itself.  But if we try to do anti-affinity to another service within the same stack, it won’t prepend.
but I also don’t want to just blindly prepend the stack name to whatever string is there.  that’s why there’s the check to make sure that at least it’s still a service within the same stack

LGTM

@cjellick @ibuildthecloud Can you please review?

LGTM

Darn.  This drone build passed just a couple minutes ago with only a flake8 failure which I fixed


please consider setting up travis build

it's worth having some kind of automated build process. travis-ci.org has decent support for D. The following .travis.yml will be enough to build with dmd, ldc, and gdc on both Linux and OSX:
language: d

sudo: required
dist: trusty

d:
  - dmd
  - dmd-2.069.2
  - dmd-2.068.2
  - dmd-2.068.0
  - ldc-1.0.0-beta2
  - gdc

os:
 - linux
 - osx

matrix:
  allow_failures:
    - d: gdc

On May 25, 2016 8:14:26 PM EDT, Samael<EMAIL_ADDRESS>wrote:

it's worth having some kind of automated build process. travis-ci.org
has decent support for D. The following .travis.yml will be enough to
build with dmd, ldc, and gdc on both Linux and OSX:
language: d

sudo: required
dist: trusty

d:
 - dmd
 - dmd-2.069.2
 - dmd-2.068.2
 - dmd-2.068.0
 - ldc-1.0.0-beta2
 - gdc

os:
- linux
- osx

matrix:
 allow_failures:
   - d: gdc

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/mysql-d/mysql-native/issues/73

Yea, i agree, that's the #1 next thing I've been meaning to do on mysqln, but haven't quite gotten back to the project yet.
I'm out at the moment and cant really double check right now, but iirc I dont think i've yet set up the tests to run correctly with "dub test", but there's a script included that does run the tests. I know it's trivial to set .travis.yml to run that instead of the default dub test.
Also, there's some stuff I'd need to take care of wrt setting up the db and/or correct mysql connection settings. Nothing difficult of course, just need to get to it, hopefully asap.


Update AbstractNacos.php

删除多余代码

[This message is created by hyperf-bot]
Hi @pmw1014, this is a READ-ONLY repository, please submit your Pull Request to hyperf/hyperf repository, this Pull Request will close automatically.


Clarification around expected timeouts/backpressure when honeycomb API slows down?

The other day in the pollinators slack several folks noticed that their refinery clusters all had buffer overruns at the same time. After a bit of discussion it came to light that the honeycomb API had been having a bit of a slowdown around that time, which caused requests to the honeycomb API to stall and put backpressure on refinery's cache.
It seems like the metrics that honeycomb emits don't include statistics about how long upstream API requests are taking - would it be possible to add support for these metrics so that operators can understand if performance/capacity issues are related to the honeycomb API?
On a related note, it appears that libhoney configures a 60s timeout on all upstream requests. Given the decision to change the timeout from 10 seconds to 60 seconds was made 2 years ago I was wondering if that's still an appropriate timeout, or if a lower value would be more suitable?
For reference, here're some charts of what our refinery cluster looked like during the incident. You can see how our refinery instance started dropping incoming spans almost as soon as the API slowdown occurred (the upstream_response_errors_peer is actually for the honeycomb API, not refinery peers - see #244). The point where memory usage drops is where the instance OOMs and restarts:

As an aside, it's not really clear to me why the collect_cache_entries_max metric just disappears as soon as the system starts experiencing backpressure - is that something you would expect to happen?

We'll likely close this out. So much has changed with Refinery, including improving its resiliency. Additionally, we have been exploring what to do when honeycomb is down or experiencing significantly degraded services.


BCC not supported?

Using your connector - nice work!
But I am having trouble getting bcc to send.
Snippet:
      const message = {
        to: EMAIL_CONFIG.to,
        bcc: post.emailSendCopyTo,
        from: EMAIL_CONFIG.from,
        subject: EMAIL_CONFIG.subject,
        html: letter.getLetterAsHtml()
      };

      EMAIL.send(message)
      .then((response) => console.log('response',response))
      .catch((err) => console.log('error',err))

Is the bcc property not supported?

I've added bcc and cc options. It should work

Thanks for quick response/action.
But the changes might have broken the api:
I'm getting {"message":"'cc' parameter is not a valid address. please check documentation"} as response from mailgun - meaning, Mailgun consume the parameter even if its set to null?
Change line 100-101 to:
        if(options.cc) {
                mailgunMessage.cc = options.cc;
        }
        if(options.bcc) {
                mailgunMessage.bcc = options.bcc;
        }

?

that. or it could be that the version of mailgun-js we're using did not support cc and bcc. I changed it to the if statement but can't test it now. If you get it working, submit a PR and i'll merge right away

I actually switched to mailgun-js directly and they had the same problem when I specified bcc as null. Easy to adjust on my part though.
I'm a bit in a hurry so I'll just leave you with the conclusion that we need the if():s :)
Thanks for your time and work!


Add support for supplying generic method type parameters

PR Summary
Adds support for specifying type arguments for generic methods.
For example:
[Array]::Empty[int]()

$dictionary = [System.Collections.Concurrent.ConcurrentDictionary[string, int]]::new()
$dictionary.AddOrUpdate[float]($Key, $addEntryScript, $updateEntryScript, $FloatValue)

Many thanks to @dlwyatt for the initial parsing implementation! 😊 💖
PR Context
Resolves #5146
/cc @lzybkr @daxian-dbw
/cc @TylerLeonhardt would this necessitate an update to language spec like the dispose{} one did?
This may affect tools not using an actual PS parser, but in general I think the impact will be minor overall, likely requiring some updates to any regex recognition patterns for some syntax highlighting rules.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[ ] Not Applicable
OR
[x] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[x] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

This may affect tools not using an actual PS parser, but in general I think the impact will be minor overall, likely requiring some updates to any regex recognition patterns for some syntax highlighting rules.

Yeah this will possibly need a change to EditorSyntax.

@vexx32 There are many formatting and style issue. Please fix issues for changed code and move unrelated ones to another PR (I mean specially build.psm1 and some in other code). It will very help reviewers!

@iSazonov ah, you're right. I'll have to do a bit of a rebase to clear that up, give me a few moments. I think a lot of those came from Dave's original code here, so I'll pare out what's needed and drop the unrelated style changes. Thanks! 💖

@iSazonov that should do it. Time for bed. 😁

@rjmholt Can you review?

@rjmholt Could you review this please?

@rjmholt please update your review when you can. Thanks! 😊 💖
@daxian-dbw did you want to review this as well? ^^

@rjmholt @daxian-dbw - Do we need a RFC for this?

@vexx32 Please resolve merge conflicts

@adityapatwardhan all sorted

@PoshChan please remind me in 2 days

Linux elevated test on last commit failed with a seemingly unrelated error. Restarting it to see if it's sporadic, this is the 2nd time I've come across it (across different PRs, too, I think).

not sure what's up with codeQL here... the log shows nothing, and I get no errors building locally.

@rjmholt, this is the reminder you requested 2 days ago

@vexx32 Also can you have a look at the CodeFactor issues?

@adityapatwardhan that should sort it out. Some of the codefactor things were more or less tangential, but I figured they were small enough to fix anyway, save someone else the hassle later.

I will have a look at separating out purely style changes when I can, although I'm not sure I made that many in this PR.

This mostly looks good to me, just want a few more tests

@rjmholt I've removed the default values for the public API constructors and added extra overloads instead, thanks for pointing that out! 💖

@adityapatwardhan please refresh your review, @daxian-dbw please take a look when you get time

I added Breaking-Change label to notice EditorSyntax.

Just a note: since 7.2 is going to RC soon, we're intending to merge this after that so it gets some time in the 7.3 preview

@daxian-dbw @adityapatwardhan Any chance this PR can make it into the next preview? 🤞

We need @andschwa review too (for possible PSES breaking).

I realize this question is probably beyond the scope of this PR, but I feel it's still relevant:
Does it make sense to attempt coercion of enumerables passed as arguments to method parameters constrained by generic type parameters when overload resolution is not otherwise ambiguous?
Take the following example:
$linq = [System.Linq.IEnumerable]

# this fails because [object[]] doesn't implement [IEnumerable[int]] (not because of ambiguous overload resolution)
$linq::Distinct[int](@(1,2,3,1,2,3))

# this succeeds
$linq::Distinct[int]([int[]]@(1,2,3,1,2,3))

@IISResetMe I agree we should have that, and agree it's out of this scope... but I would really love to have that. Because yeah, in some method calls it does feel like casts should not be necessary. Maybe would be good to file a follow up issue with that? I think it'll be easier to manage with the changes from this PR actually defining some of the types needed for the method call, so PS has less to infer from just the arguments.

We need @andschwa review too (for possible PSES breaking).

What are the concerns around breaking PSES?

We need @andschwa review too (for possible PSES breaking).

What are the concerns around breaking PSES?

Changes in Parser.

Thanks @vexx32 for your contribution!

can we have better coercion semantics for downcasting to interfaces with covariant generic type parameters?

@IISResetMe Feel free to open an issue for discussion about this 😄
@andschwa I guess EditorSyntax would need update? If so, can you please open an issue tracking that?
@JamesWTruher Not sure how much this would affect PSSA. It would be great if you can help evaluate and open tracking issue as needed.

Just noticed no documentation issue was filed. @vexx32 can you please open a documentation issue for this feature?

Aye, will do!

w00000000.
Congrats @vexx32

@vexx32 Finally! This is awesome!


Fix pytest 5.x version errors

Fixes #2466
Tests that require an exception to be thrown failed because newer pytest versions changed the str representation of the returned exception object.

Jenkins, test this please

Jenkins CI test (for commit 6e9898770f634fb4b76f2cec778e4b093258d290, target branch master) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit 6e9898770f634fb4b76f2cec778e4b093258d290, target branch master) succeeded!

LGTM

@niboshi This pull-request is marked as to-be-backported, but the corresponding backport PR could not be found. Could you check?

@gwtnb These tests were introduced in #2389 and it has not been backported. Why did you put the to-be-backported label?

@niboshi This pull-request is marked as to-be-backported, but the corresponding backport PR could not be found. Could you check?

Sorry, due to my misunderstanding.


Renovating FadeInImage

MIgrates FadeInImage from ImplicitlyAnimatedWidget to StatefulWidget.
ImplicitlyAnimatedWidget is supposed to be used when the widget needs to animate to its changes. In the case of FadeInImage, the animation is supposed to occur only in one direction, placeholder fades out -> loaded image fades in. If the image changes, the animation shouldn't be occurring in the opposite direction (viz. old image fades out -> placeholder fades in) which makes the use of ImplicitlyAnimatedWidget an overkill.
Fixes #94540
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

Bugs needed to be fixed:

[ ] When using two images, as in the issue's code sample, one of them is not cached (the first one to be specific), while the other is.

I looked at https://github.com/flutter/flutter/issues/94540 and I agree that FadeInImage is behaving strangely today when switching out the image. We actually documented what should happen if you do this in https://master-api.flutter.dev/flutter/widgets/FadeInImage-class.html:

When either placeholder or image changes, this widget continues showing the previously loaded image (if any) until the new image provider provides a different image. This is known as "gapless playback" (see also Image.gaplessPlayback).

That used to be the behavior and something broke it. We should restore that behavior. However, as far as I can tell, this PR is not quite doing that. Instead, it is showing the placeholder again.

My suspicion is actually that the bug is on this line: https://github.com/flutter/flutter/blob/d063961dda02ee1488daf3e5b336bc64060f4691/packages/flutter/lib/src/widgets/fade_in_image.dart#L432
After we have loaded the target image for the first time, isTargetLoaded  is correctly switched to true. But when you replace it with a new image, it switches back to false to show the placeholder again. That's incorrect it should continue to show the target image.

These lines also look problematic for that:
https://github.com/flutter/flutter/blob/d063961dda02ee1488daf3e5b336bc64060f4691/packages/flutter/lib/src/widgets/fade_in_image.dart#L418-L421
Once we have loaded the target once, we shouldn't be resetting the animation, I think.

I actually suspect we broke this all the way back in https://github.com/flutter/flutter/pull/33370.

We actually documented what should happen if you do this in https://master-api.flutter.dev/flutter/widgets/FadeInImage-class.html:

When either placeholder or image changes, this widget continues showing the previously loaded image (if any) until the new image provider provides a different image. This is known as "gapless playback" (see also Image.gaplessPlayback).

I totally missed that. I understand now why ImplicitAnimatedWidget is the correct candidate. I'll try to go over the previous PR and fix this instead.

After we have loaded the target image for the first time, isTargetLoaded is correctly switched to true. But when you replace it with a new image, it switches back to false to show the placeholder again. That's incorrect it should continue to show the target image.

Does the new image fade in (fading out the old one)? Or does it replace it as soon as the new one is loaded?

After we have loaded the target image for the first time, isTargetLoaded is correctly switched to true. But when you replace it with a new image, it switches back to false to show the placeholder again. That's incorrect it should continue to show the target image.

Should the new image animate in (fading out the old one) or not?

What does Image.gaplessPlayback do by default? That's what we should do here as well.

What does Image.gaplessPlayback do by default? That's what we should do here as well.

It updates the image as soon as the new one loads. Will do the same here.

I have fixed the playback bug, but can't seem to understand how to fix the other bug (stated in the issue and this PR's description).

@chunhtai @goderbauer I have made some improvements to the code. Now, the _AnimatedFadeInFadeOut widget will never leave the tree (never dispose) and sync logic is passed on for it to handle internally.


chore: update fastlane for google api instability workaround

This PR resolves []
Description

Fastlane added a workaround for some of the google API failures we are seeing!
We can pass this env var to retry if we continue to see issues:
https://github.com/fastlane/fastlane/pull/21518
PR Checklist

[ ] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

update fastlane for google api fix - Brian

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (update fastlane for google api fix - Brian)

  Generated by :no_entry_sign: dangerJS against 04af7cfa8984106aef4a802888bf3c55a059c8b0

hmm I think I am messing up our gem file with my bundler version, WIP til I fix.


No developer drop visible on Binance Web3 wallet

Hi, I'm not really familiar with this. After going through the process I claimed the drop.
I don't see the value in my web3 wallet on binance. When I click on transaction history, then I see I received 2500 FTL-DROP but I can't see the assets somewhere. Does it take 2 months before I can see this (lock up period)?

Yeah, in two months you have to click "I already have FLT-DROP" here: https://claim.fluence.network


Unable to query Influxdb

Specifications

Client Version: Influx CLI dev (git: none) build_date: 2023-04-28T14:24:14Z
InfluxDB Version: v2.7.1
Platform: Linux

Code sample to reproduce problem
from influxdb_client_3 import InfluxDBClient3

# Create a client instance
with open('influxdb_certificate.pem', 'rb') as fp:
    root_cert = fp.read()

token = "my_token"
influxdb_org = "my_org_id"
influxdb_database = "database"
influxdb_host = "{address}"
client = InfluxDBClient3(
    host=influxdb_host, token=token, org=influxdb_org, database=influxdb_database,
    flight_client_options={'tls_root_certs': root_cert})

query = "select * from measurement"
reader = client.query(query=query, language="sql")
table = reader.read_all()
print(table.to_pandas().to_markdown())

Expected behavior
Returned values from the query above
Actual behavior
E0426 19:56:38.171490399   59368 hpack_parser.cc:1218]                 Error parsing metadata: error=invalid value key=content-type value=text/html; charset=utf-8
Traceback (most recent call last):
  File "/home/raphael/stuff/eskalator-sample/api/.venv/lib/python3.11/site-packages/influxdb_client_3/__init__.py", line 257, in query
    raise e
  File "/home/raphael/stuff/eskalator-sample/api/.venv/lib/python3.11/site-packages/influxdb_client_3/__init__.py", line 243, in query
    flight_reader = self._flight_client.do_get(ticket, _options)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "pyarrow/_flight.pyx", line 1633, in pyarrow._flight.FlightClient.do_get
  File "pyarrow/_flight.pyx", line 58, in pyarrow._flight.check_flight_status
pyarrow._flight.FlightServerError: Flight RPC failed with message: Stream removed. gRPC client debug context: UNKNOWN:Error received from peer ipv4:<IP_ADDRESS>:8086 {grpc_message:"Stream removed", grpc_status:2, created_time:"2024-04-26T19:56:38.171564399-03:00"}. Client context: IOError: Server never sent a data message. Detail: Internal```

### Additional info

_No response_

Hi @raphapassini,
Thank you for using our client. This client is designed for use with InfluxDB 3. If you need to query InfluxDB 2, please use the InfluxDB 2 client.
Best regards


converted credentials to secrets, fixed spout to not close /pfs/out

Overall everything looks pretty good. I wonder if we should look at using .env files to manage the config locally and create secrets from there? Just a thought. Here's a quick reference on doing it that way.


keep connecting to kernel

Environment data

VS Code version: <IP_ADDRESS>
Jupyter Extension version (available under the Extensions sidebar): v2022.8.1002431955
Python Extension version (available under the Extensions sidebar): v2022.14.0
OS (Windows | Mac | Linux distro) and version: Windows 10
Python and/or Anaconda version: Python: 3.9
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
Jupyter server running: Local

Actual behaviour
Neverending: Connecting to kernel
Steps to reproduce:
Run Jupyter notebook
Logs
There is no log to share from Output.

This issue is resolved. I am not sure the cause of this issue and what fixed this issue.
I will repost another issue when it happens, again.
Sorry for the inconvenience.


Z_BUF_ERROR makes app crash

When trying to unfurl certain URLs, zlib sometimes throw a Z_BUF_ERROR, and this part of the app makes it crash.
res.body.once('error', (err) => {
      log('error', err.message)

      process.nextTick(function () {
        throw err
      })
    })

I was using this URL https://www.reddit.com/r/holdmybeer/comments/9644ap/work_is_hard/
The result of the unfurling is fine but the app crashes. Should an error really be thrown in the case of that non fatal error?

1.1.7

I can replicate very occasionally but seems like i did have some metadata when the error is thrown, so it shouldn't be a fatal error, i'll make a prerelease on npm if you wouldn't mind seeing if it solves the issue in version1.1.8-beta.3

Thank you very much for your quick reaction. Giving it a try today!

Looking great, I can't seem to be able to reproduce so far.

@romainbraun No problem, glad it works for you now 😃


how to use copypixels to get a pixel value in WIC ?

how to use copypixels to get a pixel value in WIC ?
https://learn.microsoft.com/en-us/windows/win32/api/wincodec/nf-wincodec-iwicbitmapsource-copypixels
Can you provide a sample code?

Getting a pixel depends on the pixel format of the WIC bitmap source.
There are various examples here for example https://github.com/smourier/WicNet/blob/main/WicNet.Tests/Program.cs#L59

Getting a pixel depends on the pixel format of the WIC bitmap source.
There are various examples here for example https://github.com/smourier/WicNet/blob/main/WicNet.Tests/Program.cs#L59

var bytes = bmp.CopyPixels();  --- it is slowly
HRESULT CopyPixels(
[in]  const WICRect *prc,
[in]  UINT          cbStride,
[in]  UINT          cbBufferSize,
[out] BYTE          *pbBuffer
);
how to set WICRect ?
i use it in mousemove event , so I need a quick method to read the pixel values of the specified coordinates
thanks for your help.

WIC is not a screen technology, it's a software bitmap (in-memory) technology, so reading pixel from WIC while you're moving the mouse is somewhat already a problem in itself. You could look a Direct2D, DirectComposition, etc instead I guess.
That being said, WicNet's CopyPixels has multiple overloads, for example
public void CopyPixels(int left, int top, int width, int height, uint bufferSize, IntPtr buffer, int? stride = null)

here
https://github.com/smourier/WicNet/blob/main/WicNet/WicBitmapSource.cs#L268
which maps to the native method with a rectangle

thanks a lot


Fixed Hidden Previous Button in Review Mode

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #2516
Description
Issue was constraints applied to the buttons.
Initial Constraints :
[Prev] -> [Next] -> [Submit] [Review]
So if submit and next button becomes invisible, prev was hiding below review
Current Constraints :
[Prev] -> [Next] -> [Review] -> [Submit]
Type
Choose one: Bug fix
Screenshots (if applicable)
Checklist

[x] I have read and acknowledged the Code of conduct.
[x] I have read the Contributing page.
[x] I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA.
[ ] I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach.
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project.
[x] I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally.
[x] I have built and run the demo app(s) to verify my change fixes the issue and/or does not break the demo app(s).

https://github.com/google/android-fhir/assets/82660329/58dfb089-0521-44b5-834f-6c703c73e0e7
https://github.com/google/android-fhir/assets/82660329/86e20294-dd2f-4ca1-ae7d-782a7d3ef246


some question in table2 on your paper

what's the means feature only and weight only in table 2?

As is their name, normalize the feature only or normalize the weight only.

I have visualized face normalized features with tsne, it's not 'radial', it's some separated blocks. Your visualization is different from tsne? @happynear

t-sne actually changes the distribution.
My visualization is created by modifying the last inner-product layer's output to 2 directly. There is no need to run other dimension reduction algorithms.
BTW...When you are asking a question that has no relationship with the current issue, could you open a new one?

OK, this question has a relationship with table 2. I will try to do dimension reduction with an added layer on my pretrained face model. Thx.

This question is actually related with Figure 2, not table 2.....

oh my god ...


[Event Request] Codeunit 5816 Undo Return Receipt Line - procedure Code - OnBeforeCode

Please add the following Event OnBeforeCode to procedure Code in Codeunit 5816 Undo Return Receipt Line
[Event Request] Codeunit 5816 Undo Return Receipt Line - procedure Code
var
    PostedWhseRcptLine: Record "Posted Whse. Receipt Line";
    SalesLine: Record "Sales Line";
    Window: Dialog;
    ItemShptEntryNo: Integer;
    DocLineNo: Integer;
    PostedWhseRcptLineFound: Boolean;
    IsHandled: Boolean;
begin
    IsHandled := false; // <-- ADDED
    OnBeforeCode(ReturnRcptLine, HideDialog, IsHandled); // <-- NEW EVENT
    if IsHandled then
        exit; // <-- ADDED

    with ReturnRcptLine do begin
        Clear(ItemJnlPostLine);
        ...

[IntegrationEvent(false, false)]
local procedure OnBeforeCode(ReturnReceiptLine: Record "Return Receipt Line"; HideDialog: Boolean; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 10881.


fix: Revert "feat: Add a field for the post message api exposure"

Reverts appsmithorg/appsmith#12551

/ok-to-test sha=1d51627


SUS005- Change LMS case status

Motivation and Context

Survey Enquiry Line (SEL) users are able to change the response status for a respondent's case in response-operations-ui. These tests cover the scenarios from the story requirements.
What has changed

Added new feature social_change_case_status
Added tests to cover the above feature.

How to test?

Checkout and run the following branches:

response-operations-ui
rm-casesvc-api
rm-case-service

make acceptance_tests

Links

Trello

 SUS005: Change the status of an LMS case (13)

 SUS005: Change the status of an LMS case (13)


[Security] Bump rack from 2.0.5 to 2.0.6

Bumps rack from 2.0.5 to 2.0.6. This update includes security fixes.

Vulnerabilities fixed
Sourced from The Ruby Advisory Database.

Possible XSS vulnerability in Rack
There is a possible XSS vulnerability in Rack.  Carefully crafted requests can impact the data returned by the scheme method on Rack::Request. Applications that expect the scheme to be limited to "http" or "https" and do not escape the return value could be vulnerable to an XSS attack.
Vulnerable code looks something like this:
<%= request.scheme.html_safe %>

Note that applications using the normal escaping mechanisms provided by Rails may not impacted, but applications that bypass the escaping mechanisms, or do not use them may be vulnerable.
All users running an affected release should either upgrade or use one of the workarounds immediately.
Patched versions: ~> 1.6.11; >= 2.0.6
Unaffected versions: none

Sourced from The Ruby Advisory Database.

Possible DoS vulnerability in Rack
There is a possible DoS vulnerability in the multipart parser in Rack. Carefully crafted requests can cause the multipart parser to enter a pathological state, causing the parser to use CPU resources disproportionate to the request size. Impacted code can look something like this:
Rack::Request.new(env).params

But any code that uses the multi-part parser may be vulnerable. Rack users that have manually adjusted the buffer size in the multipart parser may be vulnerable as well. All users running an affected release should either upgrade or use one of the workarounds immediately.
Patched versions: >= 2.0.6
Unaffected versions: <= 2.0.3

Commits

8376dd1 Bumping version for release
313dd6a Whitelist http/https schemes
37c1160 Reduce buffer size to avoid pathological parsing
99fea65 Merge tag '2.0.5' into 2-0-stable
216b7ca Merge pull request #1296 from tomelm/fix-prefers-plaintext
See full diff in compare view

I won't port across any more Dependabot PRs, as I don't want you to feel like I'm spamming you with them, but I'd still love you to use it. This one looks kinda nasty so it didn't feel right just leaving it on my fork. :octocat:

/domain @jmileham
/platform @jmileham
<< domain lgtm platform lgtm

Thanks!


MSL: Accessing shader input blocks uses the incorrect variable name

Shaders which access the shader input blocks appear to use the name of the block's variable in the main function, instead of the name of the parameter which references the block. Tested on master @ c029b0a. See the GLSL below:
#version 450 core

layout(location = 0) out vec4 col;
layout(location = 0) in VertexData {
  vec4 foo;
};

vec4 bar() { return foo; }

void main() { col = bar(); }

Current output:
#pragma clang diagnostic ignored "-Wmissing-prototypes"

#include <metal_stdlib>
#include <simd/simd.h>

using namespace metal;

struct main0_out
{
    float4 col [[color(0)]];
};

struct main0_in
{
    float4 VertexData_foo [[user(locn0)]];
};

float4 bar(thread VertexData& v_13)
{
    return in.VertexData_foo;
}

fragment main0_out main0(main0_in in [[stage_in]])
{
    main0_out out = {};
    out.col = bar(v_13);
    return out;
}

I'm assuming "in" in the bar function should be v_13.

Ok, the problem is dealing with passing down global-aliased and flattened types like I/O blocks and structs.
I think we'll need to refactor how this works, adding support for this directly will get very messy.

Hmmm...this should be working already.

This kind of code should work now in MSL.

Fantastic! Thank you. Can confirm the issue is fixed.


Can't setup DVR

First of all, thank you for this promising software.
I tried to setup Telly but I can't manage to get past the DVR setup. It tries to get the channel list but then shows an error.
My Plex Media Server version is <IP_ADDRESS>60.

This is what I get from the terminal
# ./telly -file playlist.m3u
[telly] [parser] Reading m3u file playlist.m3u ...
[telly] [warning] telly is not attempting to strip out unneeded channels, please use the flag -useregex if telly returns too many channels
[telly] [info] telly is currently not filtering for only uk television. if you would like it to, please use the flag -uktv
[telly] [info] found 131 channels

[telly] [info] creating discovery data
[telly] [info] creating lineup status
[telly] [info] creating device xml
[telly] [info] creating webserver routes
[telly] [info] listening on localhost:6077
2018/02/08 18:53:45 http: panic serving <IP_ADDRESS>:43795: runtime error: index out of range
goroutine 19 [running]:
net/http.(*conn).serve.func1(0xc420093040)
	/usr/local/Cellar/go/1.9/libexec/src/net/http/server.go:1697 +0xd0
panic(0x684ea0, 0x849410)
	/usr/local/Cellar/go/1.9/libexec/src/runtime/panic.go:491 +0x283
main.main.func6(0x81ff40, 0xc42013c000, 0xc420138000)
	/Users/tom/go/src/github.com/tombowditch/telly/main.go:204 +0x4a9
net/http.HandlerFunc.ServeHTTP(0xc42008cd80, 0x81ff40, 0xc42013c000, 0xc420138000)
	/usr/local/Cellar/go/1.9/libexec/src/net/http/server.go:1918 +0x44
net/http.(*ServeMux).ServeHTTP(0x853b60, 0x81ff40, 0xc42013c000, 0xc420138000)
	/usr/local/Cellar/go/1.9/libexec/src/net/http/server.go:2254 +0x130
net/http.serverHandler.ServeHTTP(0xc4200a2c30, 0x81ff40, 0xc42013c000, 0xc420138000)
	/usr/local/Cellar/go/1.9/libexec/src/net/http/server.go:2619 +0xb4
net/http.(*conn).serve(0xc420093040, 0x820480, 0xc4200a8440)
	/usr/local/Cellar/go/1.9/libexec/src/net/http/server.go:1801 +0x71d
created by net/http.(*Server).Serve
	/usr/local/Cellar/go/1.9/libexec/src/net/http/server.go:2720 +0x288

Do you know what I've done wrong ? I've tried to pass m3u file with only one (working) channel, but that doesn't fix it.
Thank you

Do you mind sharing your m3u file? I'm unable to get it to read my own

@gignonje what version of telly are you running? This should be fixed in v0.2 - if you're using that version, let me know and I'll take a look.

@Nezreka what issue are you having? Please open a new one if it's not the same error ;-)
T

I am seeing something very similar, running v0.2 tried both in Windows and Linux and it looks like everything is running with the script shows 188 channels available litening on port 6077, but Plex never finds it when I try to add manually.  Ran nmap on both windows and linux and I don't show port 6077 as open.

@tombowditch I was in v0.1 and v0.2 fixed it, thanks !
@Nezreka I had an issue about Invalid m3u file format. Expected #EXTM3U file header, if this the issue you have, I just had to convert from UTF-8 encoding to ISO-8859-1 to get it to work. I don't know why.


Copy and paste doesn't work properly in Debug Console

VSCode Version: 1.2.1
OS Version: Windows 10 Pro 1511, Node 5.10

Steps to Reproduce:

Create an app with a large output to the console, e.g. crash report, console.dump etc.
Try to copy and paste 10 + lines of output on a small screen

The Issue
I am using an M'soft surface, so the small screen makes the debug window is small.

Using shift + up to select multiple lines rolls over into the code screen rather than scrolling the console.

If I select a line and then manually scroll up through many lines while holding shift and then click the new line (10 or so lines higher - they don;t all fit on the screen) however, scrolling up and down shows them highlighted, copy and paste only shows the last 4 lines (presumably the only ones that were visible at one go).

Dup of #2163


[Entry] Add Pitch Accent Info

https://greasyfork.org/en/scripts/31070-wanikani-pitch-info
We have strokes, why not!
Instead of just [0], [1], [2] -> would be nicer to have a little drawn svg that indicates the rise and fall ~

Probably easier to scrape for our current data.
When adding custom vocab can xhr for the pitch accent during creation.

may as well add alc, goo, web etc links
https://community.wanikani.com/t/userscript-Additional-resource-links-Stroke-Order/10623
also forvo pronunciations

Done


docs(AppState.js): update example to ES6

If this is the way to go, I'll update the rest of the document :)

Explain the motivation for making this change. What existing problem does the pull request solve?

Update basic usage to latest ES6-7 syntax
Provide a working simple example of using AppState

Thank you, just one small nit, no space between the method name and parens: render()

@hramos
the cirecleci is failing:
Unable to download: mvn:org.easytesting:fest-util:jar:1.2.5
Is that related to my changes?
(I assume not since I only touched documentations)

@goldylucks unlikely to be related.


Include greeting SWF

Greeting SWF is part of the https://github.com/parodos-dev/orchestrator-helm-chart and the image needs to be generated using the defined CI pipeline

I added greeting with this
https://github.com/rgolangh/serverless-workflows-helm/pull/11
The 2nd thing is to merge serverless-workflows-helm to parodos-dev/orchestrator-helm-chart. They are not the same although very close. (more developer/kubernetes functionality in the the former)

now we got https://github.com/rgolangh/serverless-workflows-helm/pull/12
merging soon after the image is pushed to quay

Closed by https://github.com/parodos-dev/serverless-workflows/actions/runs/7518017920/job/20465098576
✅ Successfully pushed "serverless-workflow-greeting:latest" to "quay.io/orchestrator/serverless-workflow-greeting:latest"
sha256:33b2a46374b51e7cc90b70b731d80ce94b19d6fa095b192619800ab384883720
/usr/bin/podman push --quiet --digestfile serverless-workflow-greeting-latest_digest.txt serverless-workflow-greeting:8dc7224f47325e380e72ac4555f4b2aa1d129e8a quay.io/orchestrator/serverless-workflow-greeting:8dc7224f47325e380e72ac4555f4b2aa1d129e8a --tls-verify=true --creds=***:***
✅ Successfully pushed "serverless-workflow-greeting:8dc7224f47325e380e72ac[45](https://github.com/parodos-dev/serverless-workflows/actions/runs/7518017920/job/20465098576#step:4:51)55f4b2aa1d129e8a" to "quay.io/orchestrator/serverless-workflow-greeting:8dc7224f47325e380e72ac4555f4b2aa1d129e8a"
sha256:33b2a[46](https://github.com/parodos-dev/serverless-workflows/actions/runs/7518017920/job/20465098576#step:4:52)374b51e7cc90b70b731d80ce94b19d6fa095b192619800ab384883720


Enhance boot3-actuator-autoconfigure

Motivation:
https://github.com/line/armeria/issues/4874
Modifications:
It should behave the same as spring boot's WebEndpointAutoConfiguration.

Support management.endpoints.web.exposure.*
Support management.endpoints.web.path-mapping.*
Support management.endpoints.web.discovery.*
Support management.endpoint.health.status.http-mapping.*
Support application/vnd.spring-boot.actuator.v3+json, application/vnd.spring-boot.actuator.v2+json and application/json

Result:

Closes #4874

It would be also useful to comment about management.endpoints.web.path-mapping.* on the method or Javadoc.

fixed: https://github.com/line/armeria/pull/4880/commits/f477edd35902108daddccbf299f6314abaa5955d

Thanks for the review :) > armeria team


Paper Discussion: 2b. Fog Computing for the Internet of Things: Security and Privacy Issues

Reviewer: Lily Shpak
Review Type: Comprehension
Problem Being Solved
The problem that the authors in this paper are trying to solve is how to make the Internet of Things more secure by using fog computing. The authors acknowledge that there are many obstacles that would have to be crossed in order to make this a secure and effective solution.
Main Contributions
The main contributions this paper makes to solving this issue is providing solutions to the biggest issue that fog computing introduces, security. The authors give different facets of security that would need help, and then they provide solutions for these issues but they also recognize that there are extreme strides that need to be made in order for fog computing to be an effective solution.
Three Questions

The authors acknowledge that there is a communication overhead to send the certificate packets back and forth, is this a significant enough overhead that would cause delays in the system?
In order for this to work for all IoT devices, the devices need to be significantly updated, how would administrators of this system ensure that all devices are updated so no vulnerabilities can occur?
How hard would it be to implement a fog computing system in a system that already exists?

Reviewer: Pat Cody
Review Type: Comprehension
Problem Being Solved
IoT devices by themselves generate massive amounts of data and have intrinsic problems due to being small physical devices, on top of the security challenges from being connected to the Internet. As a result, these shortcomings place a higher burden on cloud computing servers. Fog computing has been introduced as a means to bridge IoT devices with the cloud, but they also suffer from security issues.
Main Contributions
This paper highlights a wide variety of security issues present in IoT. It proposes a novel means of performing certificate revocation using fog computing. It also describes how fog computing can be used more generally to solve the security issues they previously highlighted.
Questions

How has fog computing evolved into edge computing?
Regarding their certificate revocation proposal, how would the case of the fog node not being able to reach the cloud be handled?
How would an IoT device communicate with the fog node regarding authentication?

Reviewer: Greg Kahl
Review Type: Comprehensive
Problem Being Solved
In this survey paper, the authors discuss the advantages of using Fog Computing, or Edge Computing, in IoT. They also discuss the security risks that may be brought about by utilizing Fog Computing and address these risks with solutions to mitigate the risks that may arise.
Main Contributions
In the first portion of the survey discusses the issues that the use of Fog Computing may bring with it. They then move on to discuss their solution which helps to mitigate these issues and hopefully provide a better experience than the systems currently in place. And finally, they discuss Fog Computing could be utilized to help solve some of the problems discussed earlier.
Questions

Doesn't the use of CRL on the Fog Computing device run into the same issue as when it is on the actual IoT device, wherein if the table isn't updated revoked keys may still be authorized?
Continuing off that, would it be more secure to use OSCP to request the certificate status if the certificate does not show up in the bloom filter?
Although the table isn't being stored on the IoT device, is this proposed method scalable? Would the addition of many more devices on the system increase latency as more requests are being made to the single Fog Node?

Reviewer: Sam Hanna
Review Type: Comprehension
Problem Being Solved:
This paper talks about fog computing and the security and privacy implications of using fog computing with IoT devices. The paper covers common security problems and gives an example of a solution for one of the problems, Certificate Revocation.
Important Areas:
The paper focused on how fog computing can help improve the security of IoT devices. The areas of security that were focused on in particular were authentication, privacy, and access control. It also gave a solution for Certificate Revocation, which uses Bloom Filters on the device and checks any false positives on the edge.
Questions about the Survey:

In the section about using bloom filters as a solution for certificate revocation, it talks about reliability and authentication, but one important aspect of security is Integrity. I’m curious if it would be possible for a man-in-the-middle type attack that would be able to change the bloom filter and thus circumvent the security that was put in place?
In the section called “Certificate Revocation Schemes,” it briefly mentions public-key cryptosystems but does not really explain how it is used in relation to the certificate revocation, so I am confused about the relevance of the inclusion?
It mentioned the location of the fog devices helping with security updates, and I don’t think I understand how that would help with updating?

Reviewer: Sean McBride
Review type: Comprehension
Problem Being Solved
"Fog Computing for the IOT: Security and Privacy Issues" seeks to provide a high-level and non-exhaustive list of security and privacy issues around the IOT, demonstrate a focused example of fog computing to one of the many problems in this domain, and then outlines numerous open research issues at the intersection of fog computing and IOT security and privacy."
Main Contributions

Outlines a number of ways that the characteristics of IOT devices are hamstrung in executing the sorts of security and privacy measures common in data centers. I.e. cryptographic hashing
Provides a quick primer in Certificate Revocation Schemes, why these are problematic for IOT, and then presents a novel reference architecture for a "fog-native" certificate revocation scheme that provides on-IOT verification via Bloom Filters with fallback to client-server interaction with a fog device.
Provides a number of possible areas for follow on research.

Questions about the Research Paper:

Is the certificate revocation architecture the main topic of the paper or is it more of an example and call-to-arms to encourage more researchers to perform creative architectural thinking at the intersection of these domains?
The paper discusses using the fog to obfuscate or anonymize data before sending it to the cloud, but assuming a customer rents edge computing services from a service provider, how does locality change the trust relationship with the edge computing provider? Alternatively, does this suggest that edge devices should be personally-owned and run within some sort of trusted enclave?
What sort of security problems are exposed by trusted an external device to do crypto on your behalf? What sort of controls can be put in place to defend this, and do these security controls scale down to IOT?

Reviewer: Cuidi Wei
Review Type: Comprehension
Problem being solved
Employing fog to improve the distribution of certificate revocation information among IoT devices security enhancement. Also. The fog computing paradigm aims to reduce the data volume and traffic to cloud servers, decrease latency, and improve quality of service.
Main contributions
Proposing a new scheme using fog to solve security issues in distributing certificate revocation information IoT environments.
Questions about the survey
1.Is there a possibility that a client A disguises as another client B to communicate with fog and access a certain source?
2.How to measure the communicate overhead? Is the comparison between the latency and communicate overhead fair enough? I mean, if there is a fog between cloud and client, there may be more latency because there is one more step to communicate with.

Reviewer: Rachell Kim
Review Type: Comprehension
Problem Being Solved
Ensuring security and privacy in IoT devices can be a unique challenge due to architectural constraints and the mobile nature of the devices involved. This paper discusses areas that may pose as security and privacy threats to IoT as well as the insufficiency of existing mechanisms to cover for these identified problems. The authors also propose a new method which utilizes fog computing to enhance security in IoT environments that do interact with fog devices.
Main Contributions
The authors survey various vulnerabilities in IoT devices and propose a new system to improve certificate revocation schemes through fog computing. They also survey different facets of security in IoT that may benefit from incorporating the usage of fog computing as a part of potential solutions.
Questions

The authors mention providing a short list of the CRL in the form of a bloom filter as one of the key steps in their certificate revocation scheme, but how is this short list made? What decides which serial numbers make it into the filter and how does this guarantee that a certificate is not revoked if it isn’t found inside the bloom filter that was passed onto the IoT device?
I understand that fog computing adopts some of the similar challenges faced with cloud computing with respect to IoT devices, as discussed in this paper, but what exactly are the unique challenges that can be introduced that are specific to fog in IoT that is not faced with the cloud?

Reviewer: Michael Hegarty
Review Type: Comprehension
Problem being solved
This paper discusses the challenges related to IoT devices fitting into the current internet system. They discuss how different aspects of security and privacy are facing issues due to the unique nature of IoT. The authors go into detail about the challenges of certificate revocation, particularly in IoT devices.
Main Contributions
The authors sum up different problems facing the world of IoT while explaining how the nature of IoT lead to these problems. They give a case study to show how the specific issue of certificate revocation in IoT would be fairly difficult to solve in a conventional way without making trade offs involving data size, round trip time, or security, and provide a solution using a fog based framework. They then discuss the potential issues that fog computing will need to address.
Questions

The authors discuss in the later sections how location verification can be an issue with IoT devices moving in a fast and dynamic way. Wouldn't this issue have already been addressed and solved by the numerous maps programs on cell phones?

The authors mention the idea that a user's usage pattern of IoT devices can be revealed from the data generated from the devices. Assuming the attacker gets this information from intercepting the wireless transmission from node to node is this something that can be dealt with without simply encrypting every transmission?

How would the trust model based on reputation be implemented in the IoT domain? Wouldn't it get computationally expensive to keep track of reputations for every single device on the network and update them based on their behavior?

Reviewer: Huachuan Wang
Review Type: Comprehension
Overview
This paper analyzed the security and privacy issues of fog computing in IoT environments. It proposed a new methodology using fog to solve security issues in distributing certificate revocation information in IoT environments.
Contribution
This paper investigated and discussed security and privacy challenges of introducing fog computing in IoT environments. It emphasized great attention should be paid to solve the authentication in the context of fog computing in IoT applications and other security problems. This paper also did research on the location and other new privacy issues.
Questions*

Figure 2 gives an example of a bloom filter with k independent hash functions. Why did this paper argue although a false positive matching is possible in the bloom filter, a false negative is not?
In the overhead part. This paper comparison of the communication overhead in different certificate revocation schemes and showed the proposed scheme is more efficient, however, as mentioned in the storage overhead part, OCSP protocol doesn’t incur any storage overhead, because it’s an online approach, referring to figure 4, which compared the speed vs package size,  why the OCSP's zero storage overhead has cannot benefit the speed?

Reviewer: Ratnadeep Bhattachara
Review type: Critical
Problem Solved
The paper analyzes the overall security situation of IoT devices. It then goes on to describe the role fog nodes can play. Finally, it discusses the use of a scheme to provide certificate revocation better than current schemes.
Main Contribution
It discusses a scheme that combines hashing and a bloom filter data structure (a bit map) that provides certificate revocation information better than current schemes like CRL (Certificate Revocation List) and OCSP (Online Certificate Status Protocol).
Figure 1 and 2 in the paper provide a very concise description of the scheme. It improves on two aspects of current schemes

Communication overhead required by OCSP
Storage overhead required by CRL

The method is rather simple where each fog node maintains CRL files for a CA. The node then passes the certificates through k hashing functions and store a single bit for each certificate in a bloom filter. The data structures are stored in the IoT devices. If a source device talks to a destination device then the bits corresponding to the destination are checked. If they are unset then the destination has a valid certificate; otherwise the fog is checked with because there is a small probability for false positives.
According to my calculations, for a fog having 1000 devices in a hostile environment (500 devices could be malicious), the size of the CRL file would be around 1 KB. Also, in case of revoked certificates, the devices make much lesser requests to the fog.
Critique

The underlying assumption is that fogs would be inherently secure (maybe as a subset of the cloud)
The paper mentions that the probability of false positive (p) depends on the number of hash functions (k). However, this relationship is not explained. According to their formula for the size of the bloom filter (m), m has a substantial relationship with p.
If we hold p constant at 0.01, then in a large-ish environment (n = 1000) which is also hostile (b = 500), the ~1661 bits required to store the bloom filter.


proof jwt is empty string

Hi,
I have recently try out the authorization code flow in the mobile app. I found that, if there are now issuer, the iss field in proof jwt will be empty string.  from the specification, seems like only in pre-authorisation code flow can omit iss, even if iss is omitted, I not pretty sure if it should be empty string.
example
{   "iss": "",   "aud": " [https://e9b4-119-73-236-216.ngrok-free.app/oid4vci/test/test-issuer"](https://e9b4-119-73-236-216.ngrok-free.app/oid4vci/test/test-issuer%22) ,   "iat":<PHONE_NUMBER>,   "nonce": "u76wqIVIFXwudmPYZwtE0N1xIRMKyVRX" }
Thank you, sorry for bothering so much

Thank you @cindy-chin , we will look into this, no bother at all btw!


Adding resource_manager_tags to the NodePool module

Adding resource_manager_tags to the NodePool module at modules/gke-nodepool

I applicable, I acknowledge that I have:

[ X] Read the contributing guide
[ X ] Ran terraform fmt on all modified files
[ X ] Regenerated the relevant README.md files using tools/tfdoc.py
[ X ] Made sure all relevant tests pass

I'll reopen after some more testing


Create AtmelStudio.gitignore

Added a new .gitignore for Atmel Studio 6.
Atmel Studio is for embedded development, so the build result files are mostly C.
It's built on top of an old version of Visual Studio, so they prefixed VS file extensions with at.
Keeping user settings out of the repo applies to everyone in my opinion.
It also used a similar build output directory structure as Visual Studio, hence the exclusion of Debug and Release directories.

I'm going to close this out because I'm not sure how much value this would add, given it's roots in Visual Studio.
@rubberduck203 if you feel like this should still be a template listed here, please read the section about specialized templates and open a new pull request with more context.

@shiftkey I still thinks this adds value.
I'm happy to open a new PR with the file in the "community" location, but I don't know what more context you're looking for.


Tekton pipeline to build and host collections in nginx

Adding a Tekton pipeline to:

build the collections (without images for now)
packaged them in a Docker container based on nginx
publish them to OpenShift cluster

The initial step to build the collections is a bit hairy (in the pipeline) and should be cleaned up.
Checklist:

[X] Read the Code of Conduct and Contributing Guidelines.

[X] Followed the commit message guidelines.

[ ] Stack adheres to Appsody stack structure.

Modifying an existing stack:

[ ] Updated the stack version in stack.yaml

Contributing a new stack:

Describe how application dependencies are managed:

Explain how Appsody file watcher is utilized:

Describe other Appsody environment variables defined by the stack image:

Describe any limitations and known issues:

Related Issues:

https://github.com/kabanero-io/kabanero-collection/issues/60

@jgawor The latest changes that Erin has put into Appsody and we have pulled into this repo have broken the changes you made. The nginx image is being built as part of the ./ci/package.sh which doesn't seem to work when running as part of the tekton pipeline.
I have been making some changes to skip this step if an environment variable "USING_TEKTON"  is set.  The build step then passes, however the pipeline still fails at the "build-and-push" step.
The log shows this error:
error checking push permissions -- make sure you entered the correct tag name, and that you are authenticated correctly, and try again: checking push permission for "docker-registry.default.svc.cluster.local:5000/kabanero/collections-repository:tekton-build": creating push check transport for docker-registry.default.svc.cluster.local:5000 failed: Get http://docker-registry.default.svc.cluster.local:5000/v2/: dial tcp: lookup docker-registry.default.svc.cluster.local on <IP_ADDRESS>:53: no such host

Not sure whether I am missing something related to my config etc. I don't have an OpenShift / OKD (or whatever environment is used to use the oc command) and am just using plain Kubernetes (with the kubectl command).      This means I haven't run the
oc adm policy add-scc-to-user anyuid -z kabanero-collections -n kabanero or oc secrets link kabanero-collections basic-user-pass commands.

Try docker-registry.default.svc:5000 instead.

Replaced by https://github.com/kabanero-io/collections/pull/49.


weechat: enable pie

Motivation for this change
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Added a release notes entry if the change is major or breaking
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 124191 at 63705502 run on x86_64-linux 1

2 packages built successfully:

weechat
weechat-unwrapped

1 suggestion:

warning: unclear-gpl
gpl3 is a deprecated license, please check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/applications/networking/irc/weechat/default.nix:81:9:
   |
81 |         license = lib.licenses.gpl3;
   |         ^

Can someone tests if weechat is still usable on macOS after this? If it would break macOS it should be immediately after start.

Added a simple test to see if it starts on macOS.


Can not import in react project

I copy the dist file into react project(create-react-app), then import like this:
import { mxClient } from "./mxGraph/jjgraph.umd.js";

got a bunch of errors like:
Line 3:      'define' is not defined                   no-undef
Line 3:      'define' is not defined                   no-undef

is there some examples of the usage?

@navono, try to import like this:
import mxgraph from "./mxGraph/jjgraph.umd.js";

const editor = new mxgraph.mxEditor();

Or if the library is installed via npm:
import mxgraph from "jjgraph";

const editor = new mxgraph.mxEditor();

Thanks.


Some PortFolio Plans will not Load

Some off the Portfolio Plans will not load, and I have no ability to remove them.
What can i do to remove those Portfolio Plans

Browser
Choose a browser
[ ] IE11
[X] Chrome
[ ] FireFox
[ ] Safari
Version
[X] Azure DevOps/VSTS
[ ] TFS 2017 Update 2/3
[ ] TFS 2018
Screenshots
If applicable, add screenshots to help explain your problem.

I am also experiencing the same issue as WimKok01. I have the same browser and version as well. Some of my Portfolio plans will load while I have a few that won't.

Same also the same browser and version.

I was able to delete a plan that wouldn't load by using postman and Chrome dev tools. Here's how I did it:

Open dev tools, click on the network tab and try to load the portfolio plan
Make note of the document id; it'll be in guid format
Now, open postman and create a new DELETE request. The URL will look like this:  https://extmgmt.dev.azure.com//_apis/ExtensionManagement/InstalledExtensions/ms-devlabs/workitem-feature-timeline-extension/Data/Scopes/Default/Current/Collections/PortfolioPlans/Documents/
Add this header: /;api-version=3.1-preview.1;excludeUrls=true
Now run the request in postman. Be sure to replace DevOps Org and Doc Id with values relevant to you.
Go back to portfolio plans. You'll still see the offending plan, but this time you'll be able to open it and click the delete button.

After you've gone through this process you might need to refresh your browser cache.

Hello Steve, Thanks for jour comment. I have tried to do also, but a collague of mine ( Postman User) made a suggestion to do a clean browser approach ( or incognito), with this clean browser approach i was able to delete the Portfolio plans, so i didnot follow your steps, but i get my result trough another way .
For me: This issue can be closed.

Hello Steve,
Thanks for your feedback.
I recently went through your step-by-step plan in consultation with a Postman user.
The postman user indicated that it can also be easier if you use a clean browser or an Incognito session
We tried that and because of that we were able to remove the Portfolio plans
Kind regards
Wim
Van: Steve Landsaw @.>
Verzonden: woensdag 23 juni 2021 16:26
Aan: microsoft/featuretimeline @.>
CC: Kok, Wim @.>; Author @.>
Onderwerp: Re: [microsoft/featuretimeline] Some PortFolio Plans will not Load (#320)
I was able to delete a plan that wouldn't load by using postman and Chrome dev tools. Here's how I did it:

Open dev tools, click on the network tab and try to load the portfolio plan
Make note of the document id; it'll be in guid format
Now, open postman and create a new DELETE request. The URL will look like this: https://extmgmt.dev.azure.com/https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fextmgmt.dev.azure.com%2F&data=04|01|wim.kok%40waternet.nl|134626bcffe841c65bb008d93652c3e9|dc176db0cbcb4c4984e9efe31a545c55|1|0|637600551381348481|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=n8OEchaA8xufXTsiCF8%2FZrsvGox5us1UW2mqw8LKbYc%3D&reserved=0/_apis/ExtensionManagement/InstalledExtensions/ms-devlabs/workitem-feature-timeline-extension/Data/Scopes/Default/Current/Collections/PortfolioPlans/Documents/
Add this header: /;api-version=3.1-preview.1;excludeUrls=true
Now run the request in postman. Be sure to replace DevOps Org and Doc Id with values relevant to you.
Go back to portfolio plans. You'll still see the offending plan, but this time you'll be able to open it and click the delete button.

After you've gone through this process you might need to refresh your browser cache.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Ffeaturetimeline%2Fissues%2F320%23issuecomment-866885065&data=04|01|wim.kok%40waternet.nl|134626bcffe841c65bb008d93652c3e9|dc176db0cbcb4c4984e9efe31a545c55|1|0|637600551381348481|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=dITOEDU8kt3I0Lg5T9zWb2%2BK9zNb47of9a%2FSHE6fxcI%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALH7AVOLX6JNRJUIBJSXWGLTUHVFZANCNFSM44QRC72A&data=04|01|wim.kok%40waternet.nl|134626bcffe841c65bb008d93652c3e9|dc176db0cbcb4c4984e9efe31a545c55|1|0|637600551381358436|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=qNhfXuEQ3L5eQuPyxbk1fL1NFxT2Y87vYG2Gk8zQdtQ%3D&reserved=0.


New library to support Range requests

R: @addyosmani @gauntface @philipwalton
CC: @jakearchibald @beaufortfrancois @paullewis as an FYI.
Fixes #372
This adds a new library that exposes a static method which takes in a Request with a Range: header and a Response, and returns a new Response with the partial content specified via the Range: header (or an error Response if the Range: was invalid).
It also adds in a new plugin class, meant to be used statically, that implements RequestWrapper's cacheWillMatch lifecycle method, meaning it could be used easily from within workbox-sw.
This relies on reading and manipulating the entire source response body as a Blob, which is not as efficient as it would be if there were full Streams API support across all service worker implementation. It also forgoes a method that @paullewis seemed to have pioneered, in which a larger source Response is broken up into smaller individual Response chunks before it's cached, meaning that each individual body is smaller. I did not want this library to require that the original Response be cached in that specific chunked format, and the Streams API approach seems like the long-term solution anyway.

Reading it as a blob is actually really efficient in Chrome https://github.com/whatwg/fetch/issues/569

Sorry, I forgot that this is blocked on https://github.com/GoogleChrome/workbox/issues/709, i.e. we need the cacheWillMatch interface to change to return a promise. Adding the chilling label while I wait for that.

I've changed this PR to go against the v2 branch, now that #709 is merged there.

PTAL. Specifically, it should be cleaner now that @philipwalton's test bundling stuff means that I can avoid exporting things that are meant to be private.

@jeffposnick Please ping me when workbox-range-requests library is publicly available so that we can promote it in https://github.com/google/WebFundamentals/pull/4744

@beaufortfrancois It'll be included in the v2.0.0 release, planned for August 23.


Add testing framework, Makefile

I am not certain that this doesn't break something, but this appears to install on ubuntu with python setup.py install

fixing merge conflicts in new pull request


Item tooltips rendered behind "Comfigure IO" in GUIs

 Not displayed?
I think that should not be the case? The tooltip should probably go over the box?
Using EnderIO version 1.7.10-<IP_ADDRESS>1 #311
Issue still exists in #331 (Which is the latest as of now)
Modlist

I'm not sure this is fixable, the tooltip rendering is almost completely out of my control.

Fixed in a605736710202a17d1ec240e09374a675adefe45, I was wrong :P


[Draft] Add a snapshot store.

A draft diff of snanpshot store.
This diff will be broken in multiple diffs going forward.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Suman Karumuri seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Computing isochrone for public transport

Hi! I am trying to display an isochrone of 80 minutes, based on public transport.
For public transport, it looks like we need to specify if those 80 minutes are done exclusively by public transport or with some walking.
The parameters I am playing with are travel_time and transportation.walking_time.
For a total of 80 minutes, I tried:
travel_time=50 and transportation.walking_time=15
travel_time=60 and transportation.walking_time=10
travel_time=70 and transportation.walking_time=5
Here are the results:
50 + 2*15:

60 + 2*10:

70 + 2*5:

As you can see, they are very different, and I would like a combination of all of them, to include every possibility.
Is there a way to indicate only 80 as a parameter, and the API consider "every" possibility?

Hi Noel, thanks for reaching out!
It's probably worth me explaining how the walking_time and travel_time parameters work together, as this may answer your question.
The travel_time is just the total allowed time for the entire journey, including any walking parts.
The walking_time parameter is the maximum time allowed for walking at the start and end of the journey. In other words, from the origin to the first stop/station and then from the final stop/station to the destination. The value is applied independently at both ends, so 5 minutes would allow 5 minutes walking at the start and the end.
Any walking legs in the middle of the route (i.e between changes of public transport) are capped at 10 minutes regardless of the walking_time parameter.
So in your example of wanting an 80 minute journey with different amounts of walking_time, you should still set the travel_time as 80, rather than taking away 2x the walking time.
If you do this, the isochrones will get larger as you increase the walking_time, because more options will become available, but others won't become unavailable. So if you wanted a 'combined' area of all possibilities, you should simply set the walking_time value to as large as possible (although it can't be greater than the travel_time itself).
Hope this helps!


Add a wrapper for requests

Motivation
Consistent HTTP(S) behavior based on configuration, especially important for proxies
Implementation (Agent 6.13+)
Every check that sets a class attribute HTTP_USE_WRAPPER to true like so:
class MyCheck(AgentCheck):
    HTTP_USE_WRAPPER = True
    ...

will get a member named http that is set to an instance of RequestsWrapper.
The wrapper automatically parses configuration from the instance, init_config, and agent config. Also, this is only done once during initialization and cached to reduce the overhead of every call (for legacy reasons we usually had to re-parse configs at every check run or network call).
The standard settings are:

username - For basic authentication
password - For basic authentication
timeout - The number of seconds to wait on a connect or read (default 10)
headers - Map of headers to send on every request
proxy - Map of proxy settings e.g. HTTP: example.com. May be defined in the agent config, init_config, or instance (with increasing priority)
skip_proxy - Whether or not to ignore proxy settings entirely. May be defined in the init_config or instance (with increasing priority)
ssl_verify - Whether or not to verify SSL certificates (default true)
ssl_ca_cert - The path to a CA_BUNDLE file or directory with certificates of trusted CAs. Implicitly sets ssl_verify to true
ssl_cert - The client side certificate to use
ssl_private_key - The private key to use if it's not included in the ssl_cert file
ssl_ignore_warning - Whether or not to ignore urllib3's InsecureRequestWarning when ssl_verify is false
persist_connections - Whether or not to persist cookies and use connection pooling

The wrapper exposes the exact same interface as requests, so all you have to do is e.g.:
response = self.http.[get|post|head|put|patch|delete](url)

and the wrapper will pass the right things to requests based on configuration. All methods accept optional keyword arguments like stream, etc.
Any method-level option will override configuration. So for example if ssl_verify was set to false and you do self.http.get(url, verify=True), then SSL certificates will be verified on that particular request. You can use the keyword argument persist to override persist_connections.
There is also support for non-standard or legacy configurations with the HTTP_CONFIG_REMAPPER class attribute. For example:
class MyCheck(AgentCheck):
    HTTP_USE_WRAPPER = True
    HTTP_CONFIG_REMAPPER = {
        'disable_ssl_validation': {
            'name': 'ssl_verify',
            'default': False,
            'invert': True,
        },
        ...
    }
    ...

Notes
For now you must actively decide to use ssl_ignore_warning by doing:
with self.http.handle_ssl_warning():
    self.http.get(url)

The reason is twofold:

The mechanism the warnings module provides to filter warnings is not thread-safe. This affects us because even though the Agent uses only one thread, multiple checks may be running concurrently as the GIL is ignored.
We can't use threading.RLock because it does nothing for the same thread, and as far as I can tell the Agent may simply bypass a real threading.Lock (or crash).

When we have a proper lock we will make warning handling happen by default without the manual use of a context manager.
Future

We'll switch all checks that use requests to this, including OpenMetrics base class.
I chose to add our other forms of authentication (Kerberos, NTLM, etc.) in a separate PR to ease the review.
Cookies. They can be set globally, per-domain, and even per-path! Therefore, the configuration may be complex if not thought out adequately. We'll discuss options for what that might look like. Only our cisco_aci check currently sets cookies, and that is based on code logic, not configuration.
I disagree with our supposed default headers (except User-Agent) and the function has a legacy signature. We'll reassess whether or not these are still desired, and add any that are as defaults.

Additional Notes
This will have 100% coverage when https://github.com/DataDog/integrations-core/pull/3308 is merged 😄

What's the reasoning behind using a class variable like HTTP_USE_WRAPPER? We could cache a http property, no? In the same vein, we could replace HTTP_CONFIG_REMAPPER with an explicit method call. For example something like:
@property
def http(self):
    if not self._http:
        XXX
    return self._http

def build_http_with_config(self, config):
    self._http = XXX

@therve Ah good idea 🥇
I'll keep the config how it is though so no need for manual calls, just the definition


nftStorageUploader on Next.js App throws polyfill error

Hi, I want to make a section on my dapp to mint an nft. To do that, I need to upload images to ipfs but that code throws me error on frontend. Does anyone have that issue before?
import { mplCore } from "@metaplex-foundation/mpl-core";
import { GenericFile } from "@metaplex-foundation/umi";
import { createUmi } from "@metaplex-foundation/umi-bundle-defaults";
import { nftStorageUploader } from "@metaplex-foundation/umi-uploader-nft-storage";
import { clusterApiUrl } from<EMAIL_ADDRESS>
const MintNFTSection = () => {
  const umi = createUmi(clusterApiUrl("devnet")).use(mplCore());
  umi.use(
    nftStorageUploader({
      token: "60b43e86.cec3fd1101fe4cb38d32e4048c72eb41",
    }),
  );

  const mintNFT = async (imageFile: GenericFile) => {
    const [imageUri] = await umi.uploader.upload([imageFile]);
  };
  return
MintNFTSection
;
};

export default MintNFTSection;

ERROR

we have same issue here, did you manage to resolve this?

I have solved it without using nftStorageUploader :), I have uploaded it using default uploader of umi
import { createBundlrUploader } from '@metaplex-foundation/umi-uploader-bundlr';

const uploader = createBundlrUploader(umi);
const jsonURI = await uploader.uploadJson(metadata);

Still an issue - with
"@metaplex-foundation/umi-uploader-nft-storage": "0.9.2",


Support non-day index intervals

resolves #25
Now you can read and write from weekly, monthly, yearly,
or singular indices by specifying -index_interval in
read commands or configuration.
@demmer @VladVega @go-oleg @rlgomes @dmehra

See comment on #25 with an alternative suggestion for how we could get the same functionality in a way that (IMO) would be easier to reason about and more flexible.

Updated the code for yesterday's suggestions. README changes still in the works.

README updates complete.

Did I correctly interpret that with indexInterval defaulting to 'none', the Logstash schema is no longer the default one? So if I use logstash for ingest, I will be required to pass indexInterval='day' to able to read the data? Since logstash is common, maybe this deserves a subsection.

You correctly interpreted! Check the new README as I do describe how to read from Logstash in the new world.

Technically you don't need to specify -indexInterval day to read from Logstash as long as you do -index logstash-*. It's more robust against big data with -indexInterval day though.

And since the default read index is * you don't even have to do -index logstash-* as long as Logstash is the only data in your Elasticsearch.

My observation is that we are changing the default. Previously read elastic "just worked" for logstash schema, with no options. Now one must specify read elastic -index 'logstash-*' at a minimum, or (as documented) read elastic -index 'logstash-*' -indexInterval 'none'. I'll update the very-much-in-flux demo to account for this. The README is sufficient, but examples would be handy here. Maybe we can just link to the demos once they are in.

@dmehra As @davidvgalbraith pointed out in his last comment, while it is true that we're changing the default, it's also true that read elastic will still "just work" assuming you only have logstash data in your ES instance.

Now that I see that comment (caching...) it seems handy, but not documented and therefore magical. Can we have a README section specifically for the handling of Logstash schema, since it is common?

I made a section.

+1 on the README, nice

Looks good to me!


Support shared durable consumers

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


Error callback is only triggered once progam exits

Hello!
I'm playing around with basic C++ native WebGPU apps using Dawn (and Vulkan backend) following your guide, and I've set the error callbacks like this:
wgpuDeviceSetUncapturedErrorCallback(Globals::device, Impl::on_device_error, nullptr);

With a callback that looks like this:
void on_device_error(WGPUErrorType type, char const* message, void* pUserData)
{
    std::cout << "Uncaptured device error: type " << magic_enum::enum_name<WGPUErrorType>(type);
    if (message)
    {
    	std::cout << " (" << message << ")";
    }
    std::cout << std::endl;
}

So basically exactly like it says here: https://eliemichel.github.io/LearnWebGPU/getting-started/the-device.html
From the text, I get the impression that these callbacks should fire as soon as there's any form of error, and I should be able to see them on the console while my app runs.
Unfortunately only when I close the app that it seems that these error messages are flushed and on_device_error called, which makes it very annoying. I'd like to see the errors streaming on the console while they happen and my app continues to run.
This happens even if I launch with a debugger and put a breakpoint within on_device_error, so it is likely something related to Dawn itself because other regular std::cout calls work fine and output as my app runs.
I've tried setting the DAWN_DEBUG_BREAK_ON_ERROR environment variable, but it doesn't seem to have any effect (and I can't even find that env var mentioned on Dawn source?)
I've had a look at the callstack when on_device_error is called (after my app exits) and it looks like this:
app.exe!Impl::on_device_error(WGPUErrorType type, const char * message, void * pUserData) Line 324 (e:\Projects\test\src\renderer\renderer.cpp:324)
app.exe!dawn::native::DeviceBase::HandleError::__l23::<lambda>() Line 571 (e:\Projects\test\third_party\dawn\build\Win64\Debug\_deps\dawn-src\src\dawn\native\Device.cpp:571)
app.exe!std::invoke<void <lambda>(void) &>(dawn::native::DeviceBase::HandleError::__l23::void <lambda>(void) & _Obj) Line 1565 (c:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.35.32215\include\type_traits:1565)
app.exe!std::_Invoker_ret<void>::_Call<void <lambda>(void) &>(dawn::native::DeviceBase::HandleError::__l23::void <lambda>(void) & _Func) Line 674 (c:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.35.32215\include\functional:674)
app.exe!std::_Func_impl_no_alloc<void <lambda>(void),void>::_Do_call() Line 834 (c:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.35.32215\include\functional:834)
app.exe!std::_Func_class<void>::operator()() Line 875 (c:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.35.32215\include\functional:875)
app.exe!dawn::native::`anonymous namespace'::GenericFunctionTask::HandleShutDownImpl() Line 30 (e:\Projects\test\third_party\dawn\build\Win64\Debug\_deps\dawn-src\src\dawn\native\CallbackTaskManager.cpp:30)
app.exe!dawn::native::CallbackTask::Execute() Line 44 (e:\Projects\test\third_party\dawn\build\Win64\Debug\_deps\dawn-src\src\dawn\native\CallbackTaskManager.cpp:44)
app.exe!dawn::native::CallbackTaskManager::Flush() Line 114 (e:\Projects\test\third_party\dawn\build\Win64\Debug\_deps\dawn-src\src\dawn\native\CallbackTaskManager.cpp:114)
app.exe!dawn::native::DeviceBase::FlushCallbackTaskQueue() Line 1854 (e:\Projects\test\third_party\dawn\build\Win64\Debug\_deps\dawn-src\src\dawn\native\Device.cpp:1854)
app.exe!dawn::native::DeviceBase::WillDropLastExternalRef() Line 325 (e:\Projects\test\third_party\dawn\build\Win64\Debug\_deps\dawn-src\src\dawn\native\Device.cpp:325)
app.exe!dawn::native::RefCountedWithExternalCount::APIRelease() Line 28 (e:\Projects\test\third_party\dawn\build\Win64\Debug\_deps\dawn-src\src\dawn\native\RefCountedWithExternalCount.cpp:28)
app.exe!dawn::native::NativeDeviceRelease(WGPUDeviceImpl * cSelf) Line 1069 (e:\Projects\test\third_party\dawn\build\Win64\Debug\_deps\dawn-build\gen\src\dawn\native\ProcTable.cpp:1069)
app.exe!wgpuDeviceRelease(WGPUDeviceImpl * device) Line 342 (e:\Projects\test\third_party\dawn\build\Win64\Debug\_deps\dawn-build\gen\src\dawn\dawn_proc.c:342)
app.exe!Renderer::release_renderer() Line 1221 (e:\Projects\test\src\renderer\renderer.cpp:1221)
app.exe!main(int __formal, char * * __formal) Line 294 (e:\Projects\test\src\main.cpp:294)
app.exe!invoke_main() Line 79 (d:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:79)
app.exe!__scrt_common_main_seh() Line 288 (d:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288)
app.exe!__scrt_common_main() Line 331 (d:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:331)
app.exe!mainCRTStartup(void * __formal) Line 17 (d:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_main.cpp:17)

But I'm not sure if this is meant to be right or not.
Any ideas? It is supposed to be calling on_device_error in real time, right?
Another thing that could be related: On the following step the guide has us setup the wgpuQueueOnSubmittedWorkDone callback. I get an analogous issue there: I got the feeling I was supposed to be seeing the WorkDone callback called every frame or something like that, but I also only get its callback called exactly once, when the app finishes. And it's always called with the "DeviceLost" WGPUQueueWorkDoneStatus (because I closed the app, I imagine). That is pretty useless overall, so I wonder if I'm doing something wrong?
Thanks!

Ah, I've been looking into this and apparently we need to call wgpuDeviceTick: https://github.com/webgpu-native/webgpu-headers/issues/117
I've tested on my own code and it does work: I get the error callback as soon as Tick is called. It doesn't seem to block any GPU work on either webgpu-native or Dawn, so I guess it should be safe to use, at least for development/debug modes?

Yes wgpuDeviceTick is needed to flush callbacks in Dawn. Problem is that this is not standard, and wgpu-native has its own wgpuPoll to do something similar.
This issue is being discussed here because it would be better to have callbacks be called immediately when debugging. This is how we got the DAWN_DEBUG_BREAK_ON_ERROR although imperfect. Did you make sure you set it to =1 and that you run your program with a debugger (IDE or gdb, in a Debug build)?

Hello. I'm sorry to reply on a closed issue, please tell me if I need to open a new one or this is okay.
I'm following this part of tutorial: command-queue.
I'm currently using Dawn's C++ binding header, #include <webgpu/webgpu_cpp.h>.
They support passing capturing lambda as callback for most operations, with a change that we need to specify wgpu::CallbackMode, which is one of the following:

wgpu::CallbackMode::WaitAnyOnly
wgpu::CallbackMode::AllowProcessEvents
wgpu::CallbackMode::AllowSpontaneous

And it seems in the end section of main(), I do not need to call wgpu::Device::Tick() if I already call wgpu::Instance::ProcessEvents or wgpu::Instace::Wait.
Can anyone help me confirming that in these cases Tick is indeed not needed?
Relevant issues: #117


UI to show that test is stopping

Fixes ooni/probe#1032
Shows an animated progress bar at 99% when the close button is clicked on a running test screen.

LGTM!


Update docker-compose.yml

Updated to start initial Dockerfile with deviavir image.

The latest deviavir dockerfile image is outdated by 3 months. The last posted fculpo image (via the website) is 8 months but after inspecting it was updated 4 days ago. The dockerfile website is not maintaining the latest version. Recommend rolling back the changes.


Reconnect on hangup or timeut

@DTVD if you're okay with the PR suggested in https://github.com/DTVD/rainbowstream/issues/199#issuecomment-255689910 ... here you go. :smiley:
rainbowstreamをありがとうございました.

@stephenwithav Do your changes help with the Hangup errors?

@manasb the changes will automatically reconnect after receiving a Hangup message if AUTO_RECONNECT is true.

Hi @stephenwithav, thanks for contribution.
Does this prevent hangup happens after reconnect ?

@DTVD
I think it will attempt to reconnect upon a Hangup or Timeout (if the setting is enabled)
@stephenwithav should clarify this though
With regards to preventing a Hangup/Timeout, if it isn't an error/disconnect on the client's side then there's not much to prevent? I'm familiarizing myself with rainbowstream's code. Thank you for developing this program!
I think having a 'Reconnect on Hangup/Timeout' is useful, though you may run into Twitter's connection rate limit. Now that I think of it, I guess that my errors were related to hitting Twitter's rate limit.

Yes reaching rate limit was my concern. Automatically reconnecting can lead to rate limit easily and in theory you will be blocked for a while before you can try again. So best practice maybe limit (for example, 3 times) of reconnecting.

Can you provide a link to Twitter's rate limit documentation?
This code simply reconnects when a Hangup message is received--or there's a heartbeat timeout.

https://dev.twitter.com/streaming/overview/connecting
Yes this wraps calling TwitterStream inside a while loop without limit. I guess we will need some backoff strategies.

Thank you, @DTVD.  The docs suggest delaying reconnect attempts in increments of 250ms up to 16s, which shouldn't be difficult.


Main thread access requirements

MS.VS.Threading has a an analyzer that know about certain VS APIs and the requirement that they need to be run on the main thread to work properly. They then check that any code calling them is properly flagged with ThrowIfNotOnUIThread and such.

This would mean adding additional files to the compilation which contain the semantics:
https://github.com/Microsoft/vs-threading/blob/34c6eae89e0514ca6c6e72d411629cdb4cd88d2e/src/Microsoft.VisualStudio.Threading.Analyzers/VSTHRD109AvoidAssertInAsyncMethodsAnalyzer.cs#L51
https://github.com/Microsoft/vs-threading/blob/34c6eae89e0514ca6c6e72d411629cdb4cd88d2e/src/Microsoft.VisualStudio.Threading.Analyzers/CommonInterest.cs#L168


google cloud launcher integration

What does this PR do?
A brief description of the change being made with this pull request.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?

@hkaj Plop, really good! I just left some wording comments.
The only nit to tackle across your doc is to always capitalise the word Agent when writing about the Datadog Agent.


Filter schema service

This PR adds the API of a service in the frontend that enables to request information about the data schema. Implements and closes #102.

This is feature complete, but unit tests are missing.

Changed base branch to main as this is also needed for #50.


Add toolpad runtime sync from GitHub

Allow setting up a branch on github to watch for changes and read a Toolpad application artifact* from. Deploy said artifact as a toolpad application whenever on every push to this branch. Perhaps a github target can be thought of as another application environment?
Complementary to https://github.com/mui/mui-toolpad/issues/395 and https://github.com/mui/mui-toolpad/issues/398. It would allow setting up a local development workflow in which Toolpad applications are authored inside of the toolpad editor, toolpad artifacts are stored in the local file system and synced (outside of toolpad, by the developer) to a branch on github. Applications are deployed automatically from that branch

when I talk about "Toolpad application artifact" I mean the json file that describes a whole Toolpad application same way as we store snapshots in the database

are stored in the local file system and synced (outside of toolpad, by the developer)

Presumably this could also be native to Toolpad rather than via file system/git push, similar to how Netlify CMS works?

This issue is equivalent to Vercel which deploys Next.js apps (from GitHub to Live). It's different from #389 which focus on the other direction of the sync (low-code edits -> GitHub).

To be clear I was commenting on a specific clause, which I quoted; but perhaps there's a good reason to save to FS and before manually pushing to GitHub?
https://github.com/mui/mui-toolpad/issues/389 does seem to describe what I was suggesting:

changes done in the Toolpad UI would lead to opening a PR on GitHub

perhaps there's a good reason to save to FS and before manually pushing to GitHub?

The main reasons we had in mind were

The abiity for Toolpad to run in offline mode, perhaps even as a desktop application
The ability to generate, edit, lint,... toolpad comfiguration files with other tools. a power user feature


Fake O5 Issue

Hi,
I have a Zyxel PMG5617-R20B on Airtel (India). I'm having fake O5 issue and have tried many combinations on Realtek but none seem to work.
PON Status
Temperature | 59.820313 C
Voltage | 3.372800 V
Tx Power | 2.255692  dBm
Rx Power | -30.000000  dBm
Bias Current | 13.110000 mA
GPON Status
ONU State | O5
ONU ID | 0
LOID Status | Initial Status
This is the mib info from Zyxel:
https://pastebin.com/mdUFaJpX
And this is the mib info I have on Realtek:
https://pastebin.com/6m9aEdd5

Ok so I finally got it working after a lot of trial and error with the config.
Here is the mib info now:
https://pastebin.com/raw/YT11giWj
But there is a problem my speed is stuck at 16-20Mbps
https://beta.speedtest.net/result/14499126843.png

Ok so I finally got it working after a lot of trial and error with the config.
Here is the mib info now:
https://pastebin.com/raw/YT11giWj
But there is a problem my speed is stuck at 16-20Mbps
https://beta.speedtest.net/result/14499126843.png
This is my ONU, it is Realtek but not in the sfp stick form
http://www.hsgq.com.cn/products_34/67.html

Can you please share your config........

i have the same issue with alcl olt but its some strange because the voip lan stablishes link and work but internet isnt working


Potential memory leak on Timer.scheduledTimer

Since there's no invalidation operation on Timer.scheduledTimer, I'm wondering whether there could be a memory leak problem.
Timer.scheduledTimer(withTimeInterval: animationTime, repeats: true) { (mainTimer) in
                self.animateSpinner()
            }

Hi @skywalkerlw!
thanks for reporting this. It's likely that this produces a memory leak, will dig into it :)


Migrate to Python 3.5

I am getting an import error in io.py
from urlparse import urlparse

Module has been renamed to urllib.parse and the old version has been removed.

Seems to be solved by.

Thanks. Yes, that module has moved. I still need to determine if further changes are required for 3.x compatibility.


Fix: import of private symbols affects the type inference

As described in #309, imports of private symbols destroys the type inference. This pull request propose a simple check of symbols access specificators to filter out the private symbols.
TODO:

[x] Support for other frontends
[x] Unit test

Many thanks for finding this and providing the fix, this looks fantastic!
I've just a few stylistic pointers but otherwise very happy to merge this as soon as possible.

Thank you for great suggestions! I have applied them.
No problem, the pleasure is on our side (IPSL), as we are actively using your tool in our work.

ecwam regression fails due to missing permissions from an external contribution. Verified compatibility offline.


Investigate chainlink sequencer health oracle

See https://docs.chain.link/docs/l2-sequencer-flag/
This might be helpful when deciding of we take new requests.

@fredo do you know what this is about?

this could have something to do with downtimes of the sequencer but I really don't know

As it stands, there is not much sense to keep this open anymore so I'm going to close it.


Not able to DM by username

I am not able to send a direct message to user by username.
want to know is this feature is not there
can anyone help me
thank you .

Could you share your code?

Should be ig.entity.directThread(threadId | userIds)

I got it ,
it is like
await ig.user.searchExact(toUser);
Thanks