Unpooling2D Function

Closes #597 #301
Demos

https://gist.github.com/wkentaro/bb8300867a5ed6d53200 (only unpooling)
https://gist.github.com/wkentaro/d778c48575d7a0e93042 (stacked pooling & unpooling layers)

Actually, currently I'm not so confident about the operation in backward_cpu and it's slow.

[x] forward_cpu & backward_cpu
[x] test code for cpu methods
[x] forward_gpu & backward_gpu
[x] test code for gpu methods

[ ] forward_gpu & backward_gpu

The test for backward_cpu does not pass.
I'm not sure what is wrong with the backward_cpu method.
Am I misunderstanding about the gradient for unpooling?
Anyone who knows well about this?

Now test passed. I'm going to implement repeat for cupy.ndarray.

done. Please review.

Updated.

I updated the commit with your comments, but I have a question.
Why we cannot add cover_all=False argument for conv.get_deconv_outsize?
It does not change the behavior of that function.

@wkentaro Sorry, I made a mistake. As this feature will be merged in minor release, we can add arguments to existing functions, as long as it does not force existing codes to change themselves.

@delta2323
I see. I updated the commits and fixed the broken test also. Please review.

Though there remains some points to be fixed, overall implementation is determined. So now we can add documents that specifies the behavior of this function. Could you add it?

Could you add test cases where:

We use different self.outsize is set
self.outsize is None

I have updated the commits as you commented (aside from one which I commented above).
Could you please review agian?

@wkentaro Thank you for quick response. The implementation is OK so far. So could you go on to the document?

@delta2323 Ok, I updated the commit.

Register the reference of unpooling_2d to chainer/docs/source/reference/functions.rst.

I have updated the doc string as you commented.

I have updated again.

@wkentaro  LGTM except the comments.

@delta2323 I have updated the commit.

LGTM :+1:

Thank you very much for your great work!

Thank you for your reviews!


cmd/go: cache conflict with compiler experiment flags

There seems to be cache conflict where the compiler experiment is not part of the hash.
Steps to reproduce (affects go1.10.3 and go1.11.beta3):
# Download the Go toolchain.
mkdir /tmp/cache-conflict
export GOCACHE=/tmp/cache-conflict/cache # clean cache for reproduction purposes
(cd /tmp/cache-conflict/ && curl -s -L https://dl.google.com/go/go1.10.3.src.tar.gz | tar -zxf -)

# Build the Go toolchain normally and use that to build some random target.
(cd /tmp/cache-conflict/go/src && ./make.bash)
/tmp/cache-conflict/go/bin/go build -race archive/tar

# Build the Go toolchain with fieldtracking support and use that to build the same target again.
(cd /tmp/cache-conflict/go/src && GOEXPERIMENT=fieldtrack ./make.bash)
/tmp/cache-conflict/go/bin/go build -race archive/tar

The last command fails with:
# runtime
/tmp/cache-conflict/go/src/runtime/atomic_pointer.go:8:2: import /tmp/cache-conflict/cache/f6/f6a70051462e64c976906382146c2b90e54e5565f3f4bdc9fcd551b422e152aa-d: object is [darwin amd64 go1.10.3 X:framepointer] expected [darwin amd64 go1.10.3 X:fieldtrack,framepointer]

Clearing the cache with /tmp/cache-conflict/go/bin/go clean -cache fixes the problem.
\cc @bcmills @rsc

@dsnet Can you see if CL 128735 fixes the problem?


How to update intermediate device with pre-encrypted firmware (IDFGH-11012)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Hello,
How to send pre-encrypted OTA BIN files to non-internet connected ESP32 and perform the pre-encrypted OTA update? The ESP32 will receive pre-encrypted OTA BIN file from UART communication. Previous issue
ESP-IDF: v5.0.1
Thank you.

@law-ko

Please have a look at the esp_encrypted_img component public interface here
Please have a look at the API usage for the custom data embedded in the application in this test file

Based on the above pointers you should be able to get the decrypted contents stream which can be fed to the OTA update APIs. Please note that the transport for pre encrypted contents could be anything, including UART for the use-case you specified here.
Hope this helps.

Closing, please feel to drop a comment if you need any further help.

@mahavirj In the pre-encrypted example, esp_https_ota_begin includes decryption progress. However, how should we seperate this? We want to have the host ESP32 (which has internet connection) to download the bin file and send to another ESP32.

@mahavirj Does the encrypted BIN need to be decrypted as an entire BIN file? We are sending small chunks (e.g. 110 bytes) and each chunk needs to be decrypted before feeding into esp_ota_write. However, we received esp_encrypted_img: Magic Verification failed error.
/* Decrypt data */
args->data_in = (char *)encrypted_ota_write_data;
args->data_in_len = data_read;

err = esp_encrypted_img_decrypt_data(ctx, args);

char *ota_write_data = args->data_out;

err = esp_ota_write( update_handle, (const void *)ota_write_data, data_read);

@law-ko
Please have a look at the API documentation for esp_encrypted_img_decrypt_data here:
https://github.com/espressif/idf-extra-components/blob/f115ea488e02e1af54e060fba1b1f06f0ff088ba/esp_encrypted_img/include/esp_encrypted_img.h#L92-L110

ESP_ERR_NOT_FINISHED indicates that the decryption is on-going, not yet finished (needs more input data). It should not be treated as an error.
If args->data_out_len is greater than 0 then there is decrypted contents in the args->data_out that you can use (of same length). The buffer must be freed after its usage.

API usage is also shown in the tests of the component here

@mahavirj
Thank you for your input. We continue to feed in the data and got the following error:
E (74545) esp_encrypted_img: failed
  ! mbedtls_pk_decrypt returned -0x4100

E (74565) esp_encrypted_img: Unable to decipher GCM key

For all the args->data_in, do we need to malloc and not erase before esp_encrypted_img_decrypt_data returns ESP_OK? Or once it is passed into esp_encrypted_img_decrypt_data then the args->data_in will be managed by itself?
In the default OTA examples, 1024 bytes is commonly used, if we use 110 bytes would it cause error?

E (74565) esp_encrypted_img: Unable to decipher GCM key

Please check if the binary is correctly pre-encrypted for this case. You may try decrypting it using esp_enc_img_gen.py for confirmation.

For all the args->data_in, do we need to malloc and not erase before esp_encrypted_img_decrypt_data returns ESP_OK? Or once it is passed into esp_encrypted_img_decrypt_data then the args->data_in will be managed by itself?

If you are allocating the buffer, then please free it up after the API returns.

In the default OTA examples, 1024 bytes is commonly used, if we use 110 bytes would it cause error or should we consolidate into 1024 bytes before passing into esp_encrypted_img_decrypt_data?

Any input size should work. In-fact the test file I pointed earlier has a test case for feeding 1 byte data at a time. Please have a look.


Bug: does not reconnect sensor?

It seems that reconnecting to the heart rate sensor is not working resulting in such diagrams.
Workaround: Stopping and starting a new track works.

On recording start, an initial connection is established (or at least tried for 30s).
However, if the connection fails no re-connection attempt is conducted.
This case needs to be handled in BluetoothRemoteSensorManager.


Add type check for input spec to parse

... and raise a helpful error message rather than treating it like an empty object.
Spurred by vega/vega#796

Added in fa6ca67.


adding support for whitelisting homes

Hey @0x5e — I've just created a quick PR which adds support for whitelisting a single home based on the home's ID number.  If the options.homeWhitelist key is unconfigured it includes all homes and devices as previously, but if configured it ignores all but the whitelisted home.
I've also added it to the config.schema.json so it's configurable through the settings dialog in homebridge-config-ui-x. Hopefully this is useful to you! If there are any changes you'd like me to make, please let me know. 🙂

Hey @0x5e — yeah, I had the same thought. I'd considered allowing the whitelist to be an array, but I'm not very familiar with the config.schema.json and it wasn't immediately obvious to me how to do that. I do think you're right that it would make the system more flexible, so it's probably worthwhile.
Let me take a look at how that could be implemented.

Here's some documents about homebridge config schema, and online form validation playground,
https://developers.homebridge.io/#/config-schema#arrays
https://hamidihamza.com/ajsf/?framework=bootstrap-4

Okay, I believe I've converted this over now to use an array of whitelisted homes IDs instead of a single whitelisted ID. Let me know how it looks.

It works on me, I've add the conditions when project type is 2. Thanks @JulianLepinski again!

Awesome, happy to help! 🙂

how would I get the value of my home id?

how would I get the value of my home id?

It can be found from the log.

found it thanks!


Error with useListItems and useSite Hooks in SPFx 1.20.0

I’m encountering an issue with the useListItems and useSite hooks after upgrading to SPFx version 1.20.0. These hooks were functioning correctly in the previous release, but I receive the following error message:
Module not found: Error: Invalid "exports" target "dist/index.js" defined for "." in the package config C:\Users\SandeepPS\Desktop\upgrade-samples\sp-dev-fx-webparts\samples\react-modern-carousel\node_modules\pnp-react-hooks\package.json, targets must start with "./"
Environment

SPFx Version: 1.20.0
Node Version: 18.18.2
@pnp/sp Version: 4.6.0

Steps to Reproduce

Upgrade the SPFx version to 1.20.0.
Attempt to use the useListItems and useSite hooks in the application.
Observe the error in the console.

Pull Request
@SuperioOne , I have created a pull request to fix this issue, which updates the exports target in the pnp-react-hooks/package.json. The changes have been tested in my environment, and everything is functioning as expected now.
Additional Context
Please review the PR linked below and merge it if everything looks good:
Link to PR

Thanks for the PR! It has been released as v2.0.1.


Add relative to GameObject to velocity estimator

The existing velocity estimator works in world space therefore if the controller is moved because the play area moves then it will report a controller velocity even if the controller hasn't moved irl.
The position of the tracked object needs to take into consideration a relative object, so in the case of the controller it would be relative to the play area

Also should take in to consideration the rotation of the relative to object in case of angular velocity


search and replace text

using (WordprocessingDocument xxDoc = WordprocessingDocument.Create(dstPath, WordprocessingDocumentType.Document))
{
MainDocumentPart objMainDocumentPart = xxDoc.AddMainDocumentPart();
objMainDocumentPart.Document = new Document(new Body());
       //add paragraphs here
       //Open-Xml-PowerTools
       TextReplacer.SearchAndReplace(xxDoc, tTarget, tKeyVP.Value, true);

}
SearchAndReplace will throw an exception. _exceptionMethod = {System.Xml.Linq.XDocument GetXDocument(DocumentFormat.OpenXml.Packaging.OpenXmlPart)}
It should be xxDoc cannot build the OpenXmlPart, what should I do? Please give me a method.
ps:
for example:
var inputDoc = WordprocessingDocument.Create("ttt.docx", WordprocessingDocumentType.Document);
    MainDocumentPart inputMainPart = inputDoc.AddMainDocumentPart();
    inputMainPart.Document = new Document(new Body(new
   DocumentFormat.OpenXml.Wordprocessing.Paragraph(new Run(new Text("Hello,world."))), new                       DocumentFormat.OpenXml.Wordprocessing.Paragraph(new Run(new Text("xxxx.")))));
    inputDoc.Save();

    TextReplacer.SearchAndReplace(inputDoc, "xxx", "ccc", false);

I got a null exception, whenever I save it then open the doc or I create it in memory like above.
Please tell me what should I do?
The word is here:
Hello,world.xxxx.

Your question or issue is not related to the Open XML SDK but rather the PowerTools for Open XML. The GetXDocument Extension method and the static TextReplacer class are not part of the SDK.
All of this is Open Source, so you can debug and see what the problem is. You should also have a look at the articles written by Eric White, e.g., on the TextReplacer. However, you might want to consider the OpenXmlRegex class as well.


[Suggestion] More Large Multiblocks

Feasible
• Compressor
(higher plate/curved plate/ring throughput when compared to a single block compressor)
• Cutting Machine
(could use two bronze fluid input hatches or a single steel hatch for the fluid inputs)
Kinda Complicated
• Mixer
(would need at least 1 input and output hatch, steel tier only)

At least for now, I don't think there's much precedent to add these multiblocks. Eventually I'll add KJS support for batch crafting machines.

an earlygame alternative to the processing array is just a machine chainer with copies of the machines you want to mass produce. Other than that, at mid or late game, just use the processing array.


Upgrade CamelSources to Camel K 1.1.0

Proposed Changes

Upgrade CamelSource to latest version of Camel K (1.1.0)

Release Note

Docs

There is this issue open: https://github.com/knative/eventing-contrib/issues/1414, so there are no tests for Camel running.

There is this issue open: #1414, so there are no tests for Camel running.

Thanks, I will look into that

Flaky https://github.com/knative/eventing-contrib/issues/1433
/retest


Fix v2 signature verification

Originally I was under the impression that our test suite ran using V2 signatures for all requests, but they're actually using V4 signatures (and S3rver makes no attempt to verify those). Turning on V2 signatures makes a whopping 101/184 tests fail!
This PR fixes all V2 verification errors within the testing suite and resolves #513 (closes #526).

@allan-simon v2 signature verification was actually quite broken and only functioned as expected for pre-signed URLs. I'm pretty confident #567 is fixed by this, but I haven't tested outside of the JavaScript AWS SDK.
If you have time to test against this branch, please let me know if it's still not working for you. Once v3.6.0 is published I'll assume it's fixed otherwise.

@kherock  thanks for the ping :)  looking to the code I think it will fix it yes ! don't wait for me :)


Build issue in proxy

Bug Description
There's a build failure in istio proxy with -Wall and -Werror
./extensions/common/istio_dimensions.h:60:39: error: unnecessary parentheses in declaration of 'connection_security_policy' [-Werror=parentheses]
60 | #define DEFINE_FIELD(name) std::string(name);
Changing this to #define DEFINE_FIELD(name) std::string name;
should fix this.
Version
not required

Additional Information
No response
Affected product area

[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Control Plane Revisions

Is this the right place to submit this?

[X] This is not a security vulnerability
[X] This is not a question about how to use Istio

cc @kyessenov

Feel free to fix the warning at istio/proxy!


Unit test fixes

Fixes #2006 by using UTC timezone when executing unit test
Resolves IDE warning about access to failedTestReportFiles.size exceeding access rights, by replacing this with a call to .size()

Closing, as this PR is rolled into #2010

Closing, as this PR is rolled into #2010


default to localhost http

The default web server ip to listen on should not be public.
https://github.com/dcrdata/dcrdata/blob/master/sample-dcrdata.conf#L13
Could also use a better name like 'serverhost'

That's a good point.  I should upload a sample nginx config to, since getting the websocket upgrade and RealIP parts correct can be tricky.

Sample nginx config added in PR https://github.com/dcrdata/dcrdata/pull/88


grailsw vs. gradlew

Just getting started going thru this document but I have seen some inconsistency between using ./grailsw and ./gradlew.   At first, when I tried this from Starbucks - it seemed like it hung.   I tried when I got home and I think the grailsw was using gradle version 3.2 and the gradlew package using gradle 3.0.   As a result, after just  couple steps into the doc, I had to download two different versions of Gradle.

gradlew is a wrapper that will download the version of gradlew specified in the gradle-wrapper.properties file. The intent if this is so that the script will download the appropriate version of gradle that is compatible with the grails application.


Superflous error message when sw list is larger than 16k

Describe the bug
There is a leftover error message published to topic tedge/errors in case that the software list is larger than 16k.
We probably can remove it, since we are publishing the list via http.

tedge/errors The input size 16601 is too big. The threshold is 16384.
To Reproduce
Install many packages :)
AC:

Don't check for the size

We send software list to Cumulocity via HTTP, so it should not have the size limitation of payload. However, the mqtt payload size check applies to sending software list. This is a bug.

Unable to reproduce this issue. PR #859 may have "accidentally" fixed this issue as wel.


[at-loader] cannot find name 'require'.

Followed the instructions in readme and executed npm start and I am getting below errors.
[at-loader] Checking finished with 6 errors
[at-loader] Cannot find type definition file for 'hammerjs'.
[at-loader] Cannot find type definition file for 'node'.
[at-loader] src\app\app.component.ts:19:5
Cannot find name 'require'.
[at-loader] src\app\home\home.component.ts:20:13
Cannot find name 'require'.
[at-loader] src\app\home\home.component.ts:22:13
Cannot find name 'require'.
[at-loader] src\polyfills.browser.ts:44:3
Cannot find name 'require'.

+1

me too.

I was able to solve the problem by changing line 106 of webpack.common.js from
'awesome-typescript-loader?{configFileName: "tsconfig.webpack.json"}',
to
'awesome-typescript-loader?{tsconfig: "tsconfig.webpack.json"}',

Awesome! Thank you All.

So something odd going on here that needs to be figured out.
'awesome-typescript-loader?{configFileName: "tsconfig.webpack.json"}', is as it should be per the awesome-typescript-loader api docs.
The three of you that were having issues with this.
Are these fresh clones of the repo?
What is your NodeJS Version?
What OS are you running on?
That "workaround" should be causing the loader to use it's default which means it's targeting tsconfig.json not tsconfig.webpack.json
//cc @colinskow

Fresh clones, node v7.4.0, windows 10;

I just had this happen to me as well. My package.json has
"awesome-typescript-loader": "~3.0.0-beta.17"
for my atl dependency. I'm building a project based off the AOT release download. I've modified quite a bit, but I haven't changed how atl is configured. Yesterday it built fine, no errors, today I got these. Changed the param name from configFileName to tsconfig and we're working good again.

@DBosley - I assume you are running on Windows as well?

#1372

Yes I am.
On Fri, Jan 13, 2017, 3:45 PM Stephane<EMAIL_ADDRESS>wrote:

#1372
https://github.com/AngularClass/angular2-webpack-starter/issues/1372
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/AngularClass/angular2-webpack-starter/issues/1371#issuecomment-272568663,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACo4WPlKHCx0HtOUBnlFxnfR1uq1THJHks5rR_6kgaJpZM4Lifyc
.

Could this be a breaking change in ATL?

No, everything works fine for me. We have two looming issues on Windows that need to be worked out.

configFileName is the correct option for awesome-typescript-loader. Changing this option will load tsconfig.json instead of tsconfig.webpack.json and disable tree shaking.

So what caused these errors to start today?
On Fri, Jan 13, 2017, 7:59 PM Colin Skow<EMAIL_ADDRESS>wrote:

configFileName is the correct option for awesome-typescript-loader.
Changing this option will load tsconfig.json instead of
tsconfig.webpack.json and disable tree shaking.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/AngularClass/angular2-webpack-starter/issues/1371#issuecomment-272596682,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACo4WMgF0opN8tdYADbHI6sUOu64bQM_ks5rSDobgaJpZM4Lifyc
.

This appears to be a bug affecting just Windows with TypeScript 2.1.5. It goes away when downgrading to TypeScript 2.0.10.
But I found a better solution:
Just above "types:" in both tsconfig.json files add the following:
"typeRoots": [
      "node_modules/@types"
    ],

TypeScript should automatically look there, but it appears this is failing on Windows.

Filed an issue with TypeScript
https://github.com/Microsoft/TypeScript/issues/13486

I've got some work to do so I won't be watching github issues. If anyone still has an issue with this after picking up the changes from @colinskow - Ping me directly in the AngularClass slack channel.

@colinskow I added "node_modules/@types" but I'm still getting the issue. It doesn't seem to be able to find any type files inside of node_modules. My tsconfig:
{     "compilerOptions": {         "target": "es5",         "module": "es2015",         "moduleResolution": "node",         "emitDecoratorMetadata": true,         "experimentalDecorators": true,         "allowSyntheticDefaultImports": true,         "sourceMap": true,         "noEmit": true,         "noEmitHelpers": true,         "strictNullChecks": false,         "baseUrl": ".",         "paths": {         },         "lib": [             "es2015",             "dom"         ],         "types": [             "node_modules/@types",             "hammerjs",             "node",             "source-map",             "uglify-js",             "webpack"         ]     },     "exclude": [         "node_modules",         "pkg",         "Client/angular/**/*.spec.ts",         "Client/angular/**/*.e2e.ts",     ],     "awesomeTypescriptLoaderOptions": {         "forkChecker": true,         "useWebpackText": true     },     "angularCompilerOptions": {         "genDir": "./pkg/compiled",         "skipMetadataEmit": true     },     "compileOnSave": false,     "buildOnSave": false,     "atom": { "rewriteTsconfig": false } }

Just to update, I've just downloaded the latest clone and getting the same error as mentioned here and in #1372
The change from @colinskow is already merged in and I've already tried the fix from @matb - but neither seem to make the difference.
I'm on OS X 10.12.2, running: Node Version 5.0.0 and NPM 3.3.6
@d3viant0ne - I'll ping you at Slack, as requested. Thanks for any help.

I upgraded my Node Version to 6.9.0 and that seems to have solved the problem.
Not sure what the minimum Node Version required is now, but on the README it still says 5.0.0.
Thanks all.

Solution:
If you have your separated tsconfig in NON-root folder (e.g. config folder), you have to set typeRoots prop of this config to be relative (e.g. "../node_modules/@types")


The h1, h2, h3, p1, p2 font sizes in table don’t work.

@riodeuno @Nikhil-Nandagopal could we introduce these font sizes+alignment options in the text widget too? They feel like related issues which should be tackled all together. It'll also mean that the text widget doesn't appear inconsistent compared to the table widget options.
Current list of properties:

We can but let's do it outside of this project. The controls are reusable but we need to write them to the widget separately

Sure, just don't do it too late or leave it out of the next projects. If we could do these together, we can announce new visual controls for text+button+table.

@areyabhishek Created a new issue #1810 to track your recommendation separately.


fix #683 RTCPeerConnection.getStats(mediaStreamTrack, callback) does not work correct

Description
The full desc
      // When spec-style getStats is supported, return those when called with
      // either no arguments or the selector argument is null.
      if (origGetStats.length === 0 && (arguments.length === 0 ||
          typeof arguments[0] !== 'function')) {
        return origGetStats.apply(this, []);
      }

As we can see the comment contradicts the code.
or the selector argument is null. and typeof arguments[0] !== 'function'
Purpose
When I call RTCPeerConnection.getStats(mediaStreamTrack, callback) I would like to be here:
return origGetStats.apply(this, [successCallbackWrapper_, arguments[0]]);

Thanks for contributing. Could you fix the errors as seen in the travis runs? Thanks!

Sorry did not read the original issue careful enough. Closing this.


Expo + trpc +_ reactQuery: Uncaught Error: No QueryClient set, use QueryClientProvider to set one

Describe the bug
I decided to use expo + trpc stack. But I have some issues with react-query used under the hood of trpc.
The courios thing is that iOS build is working fine but not web configuration.
During my investigations I spotted the place in QueryClientProvider -> getQueryClientContext
Although I placed the QueryClientProvider in code and default context is created, the method can't find it.
So is my app.tsx
export default function App() {
  return (
    <AuthenticationProvider>
      <TRPCProvider>
        <ThemeProvider theme={theme}>
          <NavigationContainer>
            <Stack.Navigator>
              <Stack.Screen name="Criteria" component={MovieSearchComponent}/>
              <Stack.Screen name="Results" component={ResultsComponent}/>
            </Stack.Navigator>
          </NavigationContainer>
        </ThemeProvider>
      </TRPCProvider>
    </AuthenticationProvider>
  );
}

my component
import { trpc } from "../../utils/trpc-client";

export function ResultsComponent({navigation, route}) {

  const {data} = trpc.moviesRecommendation.useQuery(
     {
      runtimeMinsMin: 100
    }
  )

trpc-client.ts
import { AppRouter } from "../server/trpc";
import { createTRPCReact, httpLink } from "@trpc/react-query";

export const trpc = createTRPCReact<AppRouter>()

export const trpcClient = trpc.createClient({
  links: [httpLink({url: 'http://localhost:3000/api/trpc'})],
})

and trpc-provider.ts
export function TRPCProvider({children}: PropsWithChildren) {
  const [queryClient] = useState(() => new QueryClient())

  return (
    <trpc.Provider client={trpcClient} queryClient={queryClient}>
      <QueryClientProvider client={queryClient} contextSharing={true}>
        {children}
      </QueryClientProvider>
    </trpc.Provider>
  )
}

So is the web error while using useQuery:

Uncaught Error: No QueryClient set, use QueryClientProvider to set one
    at Object.useQueryClient (QueryClientProvider.tsx:48:1)
    at Object.useBaseQuery (useBaseQuery.ts:33:1)
    at useQuery (useQuery.ts:139:1)
    at Object.useQuery$1 [as useQuery] (createHooksInternal-808efaa7.mjs:277:1)
    at createHooksInternal-808efaa7.mjs:52:1
    at Object.apply (index-972002da.mjs:18:1)
    at ResultsComponent (results-component.tsx:11:1)
    at renderWithHooks (react-dom.development.js:16175:1)
    at mountIndeterminateComponent (react-dom.development.js:20913:1)
    at beginWork (react-dom.development.js:22416:1)

babel.config.js
const createExpoWebpackConfigAsync = require('@expo/webpack-config');
const path = require('path')

module.exports = async function(env, argv) {
    const config = await createExpoWebpackConfigAsync(env, argv);
    config.module.rules.forEach(r => {
        if (r.oneOf) {
            r.oneOf.forEach(o => {
                if (o.use && o.use.loader && o.use.loader.includes('babel-loader')) {
                    o.include = [
                        path.resolve('.'),
                        path.resolve('node_modules/@trpc/*'),
                    ]
                }
            })
        }
    })
    config.module.rules.push({
        test: /\.mjs$/,
        include: /node_modules/,
        type: "javascript/auto"
    });

    return config;
};

webpack.config.js

// @generated<EMAIL_ADDRESS>// Learn more: https://github.com/expo/expo/blob/master/docs/pages/versions/unversioned/guides/using-nextjs.md#shared-steps

module.exports = {
    presets: [
        '@expo/next-adapter/babel',
    ],
    plugins: [
        '@babel/plugin-proposal-export-namespace-from',
        'react-native-reanimated/plugin',
        ["@babel/plugin-proposal-private-methods", { "loose": true }]
    ]
};

How often does this bug happen?
Every time
Screenshots or Videos

Platform
System:
OS: macOS 13.0
CPU: (10) arm64 Apple M1 Max
Memory: 4.32 GB / 64.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.18.1 - ~/.nvm/versions/node/v16.18.1/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v16.18.1/bin/yarn
npm: 8.19.2 - ~/.nvm/versions/node/v16.18.1/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Browsers:
Chrome: 108.0.5359.71
Firefox: 107.0
Safari: 16.1
npmPackages:
@tanstack/react-query: ^4.18.0 => 4.18.0
@trpc/client: ^10.4.1 => 10.4.1
@trpc/react-query: ^10.4.1 => 10.4.1
@trpc/server: ^10.4.1 => 10.4.1
next: ^13.0.4 => 13.0.5
react: 18.1.0 => 18.1.0
typescript: ^4.6.3 => 4.9.3
Tanstack Query version
^4.18.0
TypeScript version
No response
Additional context
No response

So far I found:
the method __useMutation inside createHooksInternal.tsx gets lost track about value inside defaultContext.
The supplied queryClient is lost and value gets undefined.

why is this an issue in react-query and not in trpc 😅 ?
almost always when this error occurs, it means there are two versions of react-query or react in your node_modules. The one that creates the Provider will then use a different react context than the one trying to consume it via useQuery. That's why, from the viewpoint of the consumer, there is no QueryClient in the context (because it technically isn't - it's in a "different one").

@TkDodo

I already asked a question on trpc board and I was forwarded here 😄
I will check this, my other suspicion is webpack configuration, expo doesn't use .mjs out of the box, so I'm not sure if I configured it appropriately / or .mjs file receive different scope of variables?

I can't help without more information, sorry. The error occurs because we are using react-context internally, so when we do useQueryClient(), we expect to find a QueryClient in the context. If we don't, this error is thrown. So it means there is no queryClient in the context.
This can happen for various reasons, like I tried to outline above. With two versions of react or two versions of react-query, the context created by the Provider might not be the same context used by useQueryClient. So even though you have setup a Provider, the consumers cannot "see it".
I'll move this to a discussion because it is very very likely not a bug in react-query but in your setup.

I checked the versions, there is only one in my repo.

It's not about the version numbers, it's about what gets installed. Have you looked at all node_modules directories on all packages and can be absolutely sure that react-query is only there once?


include,test,sunos: Oracle Developer Studio support.

Oracle Developer Studio requires public functions to be
defined as "__global" when "-fvisibility=hidden" used as
added by #3005.
For documentation on __global see Reducing Symbol Scope in
Oracle Developer Studio C/C++ guide
https://www.oracle.com/solaris/technologies/symbol-scope.html.
fs_utime_round test failed as timespec.tv_nsec conversion to
double resulted in negative number.  Skip this test for
__SPRO_C builds.
Note that it was necessary to have C99 language features
enabled with Studio compiler (-xc99=all) as version v1.41.0
has other commits that have used C99 features.
Tested with:

cc: Studio 12.6 Sun C 5.15 SunOS_sparc 152881-05 2019/10/30
gcc (GCC) 11.2.0

This addresses the incompatibility with Illumous, @jclulow please confirm.
I've added details of the __global option as requested on #3364

Thanks @alls0rts -- I confirm that this guard doesn't affect us:
$ cmake .. -DBUILD_TESTING=ON && gmake -j8
...
$ gmake test
Running tests...
Test project /ws/safari/libuv/build
    Start 1: uv_test
1/2 Test #1: uv_test ..........................   Passed   33.96 sec
    Start 2: uv_test_a
2/2 Test #2: uv_test_a ........................   Passed   33.75 sec

100% tests passed, 0 tests failed out of 2

Total Test time (real) =  67.72 sec

$ git log -n 1 | cat
commit 6620278a9d33cc63eb79ccae26667b3ee5724027
Author: Stacey Marshall<EMAIL_ADDRESS>Date:   Tue Nov 23 12:41:03 2021 +0000

    include,test,sunos: Oracle Developer Studio support.

    Oracle Developer Studio requires public functions to be
    defined as "__global" when "-fvisibility=hidden" used as
    added by [#3005](https://github.com/libuv/libuv/pull/3005).
    For documentation on `__global` see Reducing Symbol Scope in
    Oracle Developer Studio C/C++ guide
    https://www.oracle.com/solaris/technologies/symbol-scope.html.

    fs_utime_round test failed as timespec.tv_nsec conversion to
    double resulted in negative number.  Skip this test for
    __SPRO_C builds.

    Note that it was necessary to have C99 language features
    enabled with Studio compiler (-xc99=all) as version v1.41.0
    has other commits that have used C99 features.

    Tested with:
    - cc: Studio 12.6 Sun C 5.15 SunOS_sparc 152881-05 2019/10/30
    - gcc (GCC) 11.2.0


[Bug] kotlin value class as wrapper for uuid prodcues invalid uuid

Hey,
thank you very much for this great project.
Sometimes it is necessary for business logic to create a wrapper around some type. To solve such issues, Kotlin introduces a special kind of class called an inline class.  They don't have an identity and can only hold values.
Given this context I am using such a inline class to hold an UUID of an business object like Todo
data class Todo(
    val uuid: TodoID,
    val uuid2: UUID,
    val title: String,
    val description: String,
)

EasyRandom now generates a correct UUID uuid2 40d7d115-92fa-2632-9bda-574542460f3a,  if you are using the plain UUID object. However, if you are using the inline class TodoID EasyRandom generates not a correct UUID b921f1dd-3cbc-0495-fdab-8cd14d33f0aa
@JvmInline
value class TodoID(private val value: UUID) {

    companion object {
        fun fromString(id: String): TodoID = TodoID(UUID.fromString(id))

        fun create() = TodoID(UUID.randomUUID())
    }

    override fun toString(): String = value.toString()
}

You can checkout a minimal example at the following GitHub-Repository --> https://github.com/theexiile1305/easy-random-bug
Many thanks upfront!

Thank you for opening this issue. Do you mean ER is unable to generate a random instance of TodoID?

EasyRandom now generates a correct UUID uuid2 40d7d115-92fa-2632-9bda-574542460f3a, if you are using the plain UUID object. However, if you are using the inline class TodoID EasyRandom generates not a correct UUID b921f1dd-3cbc-0495-fdab-8cd14d33f0aa

I am not a Kotlin expert, but how did you conclude that? What is incorrect about that UUID? I see it similar to the first one you mention it.
If the type is not a regular Java bean or record, you can create a custom randomizer for it.

This ticket can be closed because it is no longer current. Thanks anyway!


Double quotes inconsistency in WITH clause

Working with Oracle databases can be tricky sometime, especially with double quotes and aliases. In the current state, there is a bug around the WITH clause that does not encapsulate the alias inside double quotes which is inconsistent with other clauses. It can lead to invalid identifier on Oracale as demonstrated with the query
sub_query = Query().from_(my_table).where(my_table.ID == "12345").select(my_table.ID)

QN = AliasedQuery("sub_query_with")

query = (
    Query()
    .with_(sub_query, "sub_query_with")
    .from_(QN)
    .select(
        QN.star
    )
)

df_temp = claim_conn.read_dataframe(query.get_sql())

A workaround has been proposed here working with UPPERCASE aliases, but with a proper management of double quotes inside WITH clause it would be better

I raised a PR here that may help resolve this PR #691
If you test this and it works for your use case (I use MySQL for this library, not Oracle), you can likely deploy the current repo with these files modified.


Is it possible to generate a colorscheme .vim file from this?

So, I understand that this plugin sets the syntax highlighting colors of vim based on the wallpaper, been using it for a long time and I love it. But is it possible to make a .vim file from it?

You can copy the ~/.cache/wal/colors.vim file generated by wal


Fixed getRowProps hook prop aggregation

Simple one liner fix.  I think you mistakenly used applyProps instead of applyPropHooks and it was causing the the next hook to overwrite the previous.
I created an issue for this here: https://github.com/tannerlinsley/react-table/issues/1366

Great PR. Thanks!


feat: gather stats on x-watcher-version header

References https://github.com/omgnetwork/elixir-omg/issues/1710.
Changes:

uses statsd (Datadog) to count occurrences of distinct values in x-watcher-version header for incoming requests

Thanks! I'll take a look on that.

The new metrics using telemetry have been merged to this repo here: https://github.com/omgnetwork/omg-childchain-v2/pull/181


Remove users with overall score of 0.0

Right now the leaderboard is filled with users that have a 0.0 score. Remove these users from the list.

PR: https://github.com/Lf-Network/oss-leaderboard/pull/50

@SpandanNepal Thank you for contributing. Your PR has been merged.


Stacyzeng/fix secret volume update

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

az containerapp update
fixes bug for using the update command to mount a secret volume, checks for if volume is null since volume is now a NoneType object and mounts volumeMount as an array
General Guidelines

[x] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally?

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Thank you for your contribution! We will review the pull request and get back to you soon.

@yonzhan this has been reviewed by the ACA team and ready for review from the CLI team

Recommend PR title:
az containerapp update: --secret-volume-mount fix appending to NoneType object bug

As we have the same command and feature in Azure-cli, please fix in https://github.com/Azure/azure-cli/tree/dev/src/azure-cli/azure/cli/command_modules/containerapp too.

Recommend PR title:
az containerapp update: --secret-volume-mount fix appending to NoneType object bug

I sadly don't have the ability to change the title and Stacy is OOF, next time though.

Hi @zhoxing-ms
Could you please help to review this PR? Thanks.


build: Update Vulkan-Headers and VUL to 1.3.293

CI CrashDiagnosticLayer build queued with queue ID 238643.

CI CrashDiagnosticLayer build # 227 running.

CI CrashDiagnosticLayer build # 227 passed.


Bree app can't be found in the AppStore

You find tons of apps related to BEER or BEARS...

Issue migrated to our-city-app/mobicage-ios-client#42


Allow running with Elixir 1.2 and fix warnings shown when compiling w…

…ith that version.
(1.2 is the default provided by Erlang Solutions .debs)

Yeah, so if you like this one, just go ahead and kill #1.


Returns nan when one of the entries in the batch is a digital silence triplet

Here is some code that reproduces the issue:
import torch
from torch_log_wmse import LogWMSE

loss_function = LogWMSE(audio_length=1, return_as_loss=True)
torch.manual_seed(0)
raw = torch.randn(2, 1, 44100, dtype=torch.float32)
raw[0] = 0.0
est = torch.randn(2, 1, 44100, dtype=torch.float32)
est[0] = 0.0
gt = torch.randn(2, 1, 44100, dtype=torch.float32)
gt[0] = 0.0
loss0 = loss_function(raw[0:1], est[0:1].unsqueeze(2), gt[0:1].unsqueeze(2))  # -73.6827
print(loss0)
assert not torch.isnan(loss0)
loss1 = loss_function(raw[1:2], est[1:2].unsqueeze(2), gt[1:2].unsqueeze(2))  # 2.7946
print(loss1)
assert not torch.isnan(loss1)
loss_combined = loss_function(raw, est.unsqueeze(2), gt.unsqueeze(2))  # nan
print(loss_combined)
assert not torch.isnan(loss_combined)

It looks like this part of the code does not add EPS to the batch entry that is all digital zero:
https://github.com/crlandsc/torch-log-wmse/blob/de47dbc18ff30416636cfbdca146da128ae9497b/torch_log_wmse/metric.py#L99
That leads to the problematic division by zero here:
https://github.com/crlandsc/torch-log-wmse/blob/de47dbc18ff30416636cfbdca146da128ae9497b/torch_log_wmse/metric.py#L103

Thanks for bringing this up!
Do you mean that if some of the values are 0, but not all of them, it will skip over this block and result in some inf entires in scaling_factor?
If so, I think it would make sense to just do an item by item compare and replace as such:
input_rms[input_rms < ERROR_TOLERANCE_THRESHOLD] = ERROR_TOLERANCE_THRESHOLD

Is this what you are saying?

Do you mean that if some of the values are 0, but not all of them, it will skip over this block and result in some inf entires in scaling_factor?

Yes.
The original implementation handles the digital silence case specifically and simply returns return np.log(EPS) * SCALER early. This is similar to the normal return value, return np.log((differences**2).mean() + EPS) * SCALER, assuming differences is zero.
https://github.com/nomonosound/log-wmse-audio-quality/blob/3ebe31703a8561b18306c7052a58846931eac306/log_wmse_audio_quality/metric.py#L28
But using an if and returning early is not possible when doing batched computations, like we want to do here.

If so, I think it would make sense to just do an item by item compare and replace as such:
input_rms[input_rms < ERROR_TOLERANCE_THRESHOLD] = ERROR_TOLERANCE_THRESHOLD

That's one viable solution, although in the original implementation of logWMSE, ERROR_TOLERANCE_THRESHOLD was for zeroing out small/tolerable differences between the processed audio and the target audio, not for bumping small input_rms values.
https://github.com/nomonosound/log-wmse-audio-quality/blob/3ebe31703a8561b18306c7052a58846931eac306/log_wmse_audio_quality/metric.py#L36
Using ERROR_TOLERANCE_THRESHOLD for two different things does not feel ideal. If we choose this approach, I would prefer to create a separate constant for that purpose.

Another way to avoid an "exploding" value is to add a small constant to the divisor, for example
scaling_factor = 1 / (input_rms + RMS_EPS)
instead of
scaling_factor = 1 / input_rms
If we choose this approach, where we add an RMS_EPS, we can remove the if that checks if the input is digital silence.

Yet another way to avoid the inf --> nan problem is to check for any inf values in scaling_factor and replace them with zero.
I'm not sure which solution is best yet, but I will give it some thought. Do we want to be "inventive", i.e. create a new/improved version of logWMSE, or do we want a "fix" that matches the calculations in the original implementation?

Do you want me to create a PR with a proposed patch?

Ok, let's do RMS_EPS then. I can create a PR


mempool.space API returns an incorrect/different value

https://mempool.space/testnet/api/address/tb1qvn7ge67z3lh5x0u5ue69c7etp8kavlacku2vae/txs
https://mempool.space/testnet/address/tb1qvn7ge67z3lh5x0u5ue69c7etp8kavlacku2vae

Also, the return of /testnet/api/v1/fees/recommended is inconsistent between different instances.
https://cell.mempool.space/testnet/api/v1/fees/recommended
https://mempool.space/testnet/api/v1/fees/recommended


Which branch should I submit to?

In contributing-guide, It mentioned to submit to the v2 branch.
But the v2 branch doesn't have GitHub Actions.
Like #145 , PR may fail in test.

In contributing-guide, It mentioned to submit to the v2 branch.
But the v2 branch doesn't have GitHub Actions.
Like #145 , PR may fail in test.

Yes, the current branch management is not standardized. To solve this problem, I suggest creating a release candidate (rc) branch to release the next version lib. All PRs should request be merged into the RC branch. At the same time, the RC branch uses GitHub Actions to run unit test tasks. After release, the rc branch will be merged into the main branch.

I think this is feasible, so when would be a good time to start?
Does anyone have any other suggestions?

I think this is feasible, so when would be a good time to start?
Does anyone have any other suggestions?

I created the rc branch for release candidate. All PRs should be merged into the rc branch. The main branch will be frozen.


List Store/Index List Store

When you're building these stores, do you create them from the ContentStore response, or are these created from separate API calls?

The same API response is consumed by all stores. Content stores consume entities, list stores consume ID lists.


Allow for negative array index for arrays of structs.

Version and Platform (required):
3.6.4667-dev
Bug Description:
If the variable is defined as a struct then ninja does not handle out-of-bounds access to the struct

In fact, this is supposed to be a new variable and the program is going to locate this new variable through this struct

Any chance you can share the binary in question?

Any chance you can share the binary/bndb in question?

demo.zip
demo.zip rename demo.so
demo1.zip
demo1.zip rename demo.bndb


Fix GitHub license autodetect

I've renamed LICENSE_HEADER to FILE_HEADER and add-license-headers.bat to add-file-headers.bat. Now Apache-2.0 shows on the top right of https://github.com/maoo/plexus-interop page.

:x: Build plexus-interop 596 failed (commit https://github.com/finos-plexus/plexus-interop/commit/4c82865a19 by @maoo)

I think deleted file references in .net build script, see build  failing with following:
File 'C:\projects\plexus-interop\LICENSE_HEADER' specified for property 'header' does not exist.

I think deleted file referenced in .net build script, see build  failing with following:
File 'C:\projects\plexus-interop\LICENSE_HEADER' specified for property 'header' does not exist.

TY @udalmik ! Is the LICENSE_HEADER mentioned somewhere, or it's a .NET naming convention?

@maoo, it is just referenced from few more Gradle scripts, "copy/paste effect" I suppose :)

@udalmik - PR updated, the build seems happier now.

:white_check_mark: Build plexus-interop 597 completed (commit https://github.com/finos-plexus/plexus-interop/commit/fc8f6fc7a5 by @maoo)


Remove the deprecated lcdd() from GeoSvc Interface

BEGINRELEASENOTES

Remove the deprecated lcdd() from GeoSvc Interface

ENDRELEASENOTES

I already merged https://github.com/HEP-FCC/k4SimGeant4/pull/58

The downstream-build workflow is failing because lcdd is still used by the dual-readout repo

Reverting https://github.com/HEP-FCC/k4SimGeant4/pull/58 for now.

Removing lcdd() from k4SimGeant4. Downstream test should pass now.
https://github.com/HEP-FCC/k4SimGeant4/pull/66

This looks fine now, some tests fail in fccsw but they are broken because of other reasons


drivers: counter: add Maxim DS3231 support

This PR provides support for the Maxim DS3231 TCXO RTC, a high-precision real-time clock peripheral with support for battery backup.
This is implemented as a counter, but the DS3231 has significant functionality enhancements beyond a general RTC API.    Also, as an I2C peripheral it has limitations that are incompatible with assumptions about how a counter can function.  Most users of its advanced functionality will interact with it through device specific API provided in a driver-specific header following the approach summarized in #17072.  Consequently the interface file is placed in the (existing) include/drivers/rtc directory, and the extension functions are named based on it being a specialization of a (no longer existing) rtc driver class.
There is a question of where to collect the documentation.  Because it's device specific, it really should be its own page at API Reference : Peripherals : RTC : DS3231.  For now I've just put it under (newly created) RTC.
As more infrastructure is added to support management of civil time tracking in Zephyr some of the functionality in this driver may need to be generalized. For example, the rtc_ds3231_syncpoint structure should probably be generalized and placed in the recently created <sys/timeutil.h> header long with functions that support generic conversion from a synchronization point and local time to RTC and back.

@anangl could you please take a look at the proposed API extension mechanism?

Added to dev-review in hopes of getting feedback on this specifically, and device-specific APIs in general.  TSC mention and posting on devel didn't produce much/anything.  Base question: can this make it into 2.0.0?

DEV-REVIEW: Marking #17072 as 'TSC' with regards to the approach for how to have driver specific api's.  This is just an implementation of those ideas.

Excerpted this comment on #17072 by @MaureenHelm:

Implementing the generic counter interface will make people think it's a counter. If you're worried about people thinking it's a counter, then why implement the generic counter interface at all?
Similarly, if you think applications will use the device-specific functions exclusively, then isn't implementing the generic counter interface a waste of code space? I think we either need to revisit the RTC driver API or you should have a driver-specific API.

The description in #17072 was based on early work.  I believe in the final version the usefulness as a counter is more clear: in particular that you can set alarms based on a time_t value without having to mess with the driver-specific API, and you can read the current time using the standard API.
More generally I think an RTC API (which may or may not extend Counter) may be useful, but we need more examples of capability before we can figure out what it should look like.

All current review comments addressed.  Because I expect subsequent work to require extensions to civic time support in Zephyr I'm not going to push this for 2.0.0, as that would complicate the API changes.
@dbkinder Please check new commit documenting generic approach to API extension.

A couple of typos, otherwise docs look good.

@dbkinder requested changes made.  Thanks.

Any update on this PR? Could the assigned reviewers (especially the codeowner ones) take a look please?

Is this PR waiting for something (other than more reviews) before it's ready for merging? @pabigot looks like you'll need to fix a CODEOWNERS conflict either way.

This is only waiting for more reviews, but it's been waiting so long it does need to be rebased and retested.  There's more interest now in supporting civil time in Zephyr, so I'll try to do that early in the 2.3 development cycle.

This has been updated again.  Please take a look; I'd like to get it into 2.3.

Nice work!
I see this PR has been waiting for 8 months.
Any chance it will be available for 2.3?

Any chance it will be available for 2.3?

Probably not, but we'll try.  The latest blocker is support for userspace, which I understand to be a requirement for all new API.  So this is going back into DNM mode until that's resolved; some background is in #24539.

This has been rebased and updated with proper locking and usermode support for the extended sync functions and the underlying counter API.  I would like to see something like the rtc_ds3231_{req,get}_syncpoint() API in whatever we use for RTC extensions.
Please provide feedback, particularly @jdascenzio @henrikbrixandersen  @sslupsky  who have expressed interest in RTC.  I would like to get this in to 2.3, rather than attempt to beat @nordic-krch 's record of 367 days from PR open to merge.

@henrikbrixandersen and @jdascenzio could you please review, especially in the context of the work for #23526

Rebased and all public symbols renamed from rtc_ds3231_ to maxim_ds3231_ in anticipation of possible dedicated RTC API.

@nordic-krch would you mind approving this if you have no objections?

@jfischer-phytec-iot @sslupsky @nordic-krch please approve if you are fine with this PR as-is.

Merging this since it's been open for far too long. If you have additional comments please voice them to @pabigot and they can go in as bug fixes during the 2.3 stabilization period.

This is a nice starting point thank you but also requires external chip. I have created a feature request here: https://github.com/zephyrproject-rtos/zephyr/issues/35333 :-)


Feature request: Personal stream notifications

I thought it would be a good idea to have the bot notify you whenever someone goes live.
Right now there's an option to do @everyone but it might get annoying for some people in your Discord server. How about a command like !streambot notifyme or !streambot subscribe and the bot would memorize and include a @username mention in their next stream notification, together with everyone else who chose to be notified?
This way you'd get notifications whenever there's a stream and it wouldn't notify everyone.

Thanks for the feedback, that's actually quite clever !
This shouldn't be too hard to implement, I'll see if I do it as a small update or part of the next big update I'm planning (mostly based on #11 that should make a lot of changes in the code once again)

Just implemented that. Commands are now !streambot notify me for everyone to add their name to the mentions list, and !streambot notify everyone for the managers to add the @everyone mention to the announces.


Different flavours/distributions for clients

Possible cosmetic differences in dashboard:

Logo (log-in, feed button, navigation menu)
Main colour
Links to resources in login

 Environment variable for deploying different client distributions


If statement not compiling correctly - being wrapped in parentheses and append with !

Description
My if statement is getting wrapped by parentheses and appended with a  !. I first thought to post this as an issue on Babel but I'm unable to reproduce it on their sampler and since they don't have a react-native-preset as one of the options, I can't completely verify it's them.
My ES6 code:
const [{ updated_at: newAuthorUpdatedAt }, { updated_at: newStoryUpdatedAt }] = await Promise.all([
    fetchAuthorLastUpdatedDate(authorId),
    fetchStoryLastUpdatedDate(id)
]);

if ((storyUpdatedAt !== newStoryUpdatedAt) || (authorUpdatedAt !== newAuthorUpdatedAt)) {
    await removeDownloadedStory(story);
    dispatch(removeStory(story.id));

    return download();
}

Here's the ES5 code that it compiles to:
newAuthorUpdatedAt = _ref2[0].updated_at;
newStoryUpdatedAt = _ref2[1].updated_at;
if (!(storyUpdatedAt !== newStoryUpdatedAt || authorUpdatedAt !== newAuthorUpdatedAt)) {
    _context12.next = 20;
    break;
}

It completely changes my logic by wrapping the entire statement in !(...). I can't figure out for the life of me why it's doing that. I tried changing the || to a && and the comparisons to ===:
if (!(storyUpdatedAt === newStoryUpdatedAt && authorUpdatedAt === newAuthorUpdatedAt)) {
    _context12.next = 20;
    break;
}

and it outputs:
if (!(!(storyUpdatedAt === newStoryUpdatedAt && authorUpdatedAt === newAuthorUpdatedAt))) {
    _context12.next = 20;
    break;
}

it just rewraps everything again in a !(...). My workaround is the following hack haha:
if ((storyUpdatedAt === newStoryUpdatedAt) && (authorUpdatedAt === newAuthorUpdatedAt)) {
    await removeDownloadedStory(story);
    dispatch(removeStory(story.id));

    return download();
}

because it wraps it and the logic is correct then.
Reproduction
I just tried to do a brand new project via react-native init using the latest react native and I can't reproduce it there. Not sure what to do about that.
Solution
The code doesn't wrap an extra parentheses and ! around the if expression
Additional Information

React Native version: 0.37.0
Platform: iOS (didn't test Android but assuming it's there too)
Operating System: MacOS

"babel-core": "6.4.5",
"babel-eslint": "7.1.1",
"babel-jest": "9.0.3",
"babel-preset-react-native": "1.5.6",

An update.. I tried putting a console log inside of the if and and it gets pushed outside of it. Could this have to do with the awaited Promise before it maybe?
ES6:
if ((storyUpdatedAt === newStoryUpdatedAt) && (authorUpdatedAt === newAuthorUpdatedAt)) {
    console.log('fetching!');
    await removeDownloadedStory(story);
    dispatch(removeStory(story.id));

    return download();
}

ES5 Output:
if (!(storyUpdatedAt === newStoryUpdatedAt && authorUpdatedAt === newAuthorUpdatedAt)) {
    _context12.next = 21;
    break;
}
console.log('fetching!');
_context12.next = 17;
return regeneratorRuntime.awrap(removeDownloadedStory(story));

How messed up is this?

Is this actually causing problems with your app? Reading through what you've posted, it looks like the program just bails out early when it passes the inverted if-clause.

It seemed to be doing that and it was causing a problem. I moved out a lot of the functions into their own (which they should've been anyway) and I'm not running into the issue anymore.


Allow Frame struct initialization with u16 data

When encoding at high bit depths, unless passing decoded frames right back to the encoder, we currently have to perform u16 to u8 conversions in order to initialize a Frame. The two options to do that that I am aware of are an unsafe from_raw_parts operation, or iterating over each input pixel to generate a new frame. It would be convenient to have a constructor for high bit depth data that could perform one of these options when fed u16 input. Alternatively, a frame could always maintain a u16 buffer and the encoder could write as u8 when outputting in 8-bit.

The simplest way is to add from_u16 method which would create Frame from u16 planes.
A bit better method is to implement #11 and accept either u8 or u16 depending on the colorspace. But it would be impossible to create high bitdepth frame from u8 planes then (unless introducing something like from_u8).
Also I'm not entirely sure y4m should deal with concept of pixels. Because u8 vs u16 is about the pixel values, not the data stream. Any frame can be represented as a stream of u8.
What do you think?

Handling pixel values instead of raw data does introduce some additional concerns. We can leave it as is and leave the user with the responsibility of providing the raw data in u8 format. On the other hand, converting from high bit depth u16 data to u8 in safe Rust seems to require a significant amount of boilerplate for a use case that should be fairly common.

for a use case that should be fairly common

Seems like it, accepting u16 planes might give better user experience in real world use-cases.
Would you like to implement from_u16 for Frame?

Sure, I will give it a try.

(Haven't seen github notifications for last post editings.)
I think we should unsafely represent u16 as u8 with from_raw_parts.

OK, I was trying to avoid unsafe code but that should work, I will try it soon.


Add unpack_chat

While this is something useful to have right now, it isn't what I was aiming format. My idea of "packed chat" was "an object you can format as hex string or bytes", but not "something you can load an user from".
In my opinion, everything should work over Chat and not PackedChat. My idea was that you could get a Chat from a PackedChat and then use something like chat.reload().await to re-fetch the current state of the particular chat instance. This would be useful beyond just getting the username from a packed chat.
But maybe we could do both. What do you think?

You want to do something like let chat = Chat::from_packed_chat(&packed_chat, handle.clone()) to have an instance of Chat with just only the ID and access hash, then do chat.reload().await to load all the information?

Yes, that's what I had envisioned. But then again it might be useful to provide this method as well. Telethon uses get_entity, in grammers I wanted to push away from the generic "entity" terminology and IMO "peer" is not as clear as "chat". Given we have chat.pack(), perhaps client.unpack_chat is the best name…

Do we implement Chat::from_packed_chat and chat.reload in this PR?

I'll merge this as-is. It's a good addition except for name bikeshedding which I can't be bothered to do at the moment.


Issue with content download for new app access on specific sp Sites Sites.Selected (Preview)

Category

[ ] Question
[ ] Documentation issue
[X] Bug

Expected or Desired Behavior
The expected behavior for Sites.Selected Graph Permissions is that calls to all objects work under the particular site assigned will be able to access all the resources. including downloading the content of the driveitems
eg. sites.read.all gives access to download content/downloadurl
Observed Behavior
With Sites.Selected permission on an app permissions, the app can sucessfully call the driveitems endpoint for sites
and list all the objects, and even get the pre-authed temp downloadurl.
However, when you try to use that url, you get access denied.
eg. /sites//Drive/root/children Correctly returns all the objects, including  @microsoft.graph.downloadUrl
but when you try to use the downloadURL in a browser, or try to hit the content endpoint it will error out or give access denied.
Headers for Successful DriveItem Call preceding the download:
"Date": ["Wed, 03 Mar 2021 18:09:32 GMT"],
"request-id": ["c8beadfe-2ef1-4084-b338-807a700dd3f5"]
Headers for Access Denied downloadurl attempt (behavior for /content is same, gives error)
Date →Wed, 03 Mar 2021 18:10:37 GMT
SPRequestGuid →5bb7b09f-b045-b000-db7e-a850c9c3cd10
request-id →5bb7b09f-b045-b000-db7e-a850c9c3cd10
If api permissions Files.Read.All added to app, or Sites.read.All .. the downloadurl works and /content works.
(this is what we don't want)
Steps to Reproduce

Create an App Registration
Give app api permissions to graph for sites.Selected
Use a http call to graph to any specific site /permissions endpoint to give newly created app id permissions.
make call to site/drive/root/children using a secret/appid of the app registration
use the downloadurl returned in step 4 to try to download a file.
observe Access Denied.

Thank you.
[ ]: http://aka.ms/onedrive-api-issues
[x]: http://aka.ms/onedrive-api-issues

@alphaz18 we are investigating this issue

thanks k-tsoi, I was wondering if there are any updates? thanks

Thanks for your patience. We're still looking into it.

We believe this should be working now.  Can you let us know if your app now works correctly with download (and upload) using the Sites.Selected permission?

Closing this issue, it should be working now


chore temporary change fetch_rpc_timeout_seconds to 150s to…

… solve rpc timeout
Rpc timeout is due to fetch phase acquire tablet lock, but the related PR(#26151) is now pending to merge to branch-2.0. So change fetch_rpc_timeout_seconds from 30 to 150 to solve the problem temporarily
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

https://github.com/apache/doris/pull/27482
https://github.com/apache/doris/pull/27478

这个PR不合入


Angular files does not work on VS code 1.23.0?

Hello Alexander,
I have installed the extension on VS code 1.23.0 version but I can't generate an Angular component.
Neither no error nor folder created. I wonder if this issue is related to the newer version of VS code?
Best regards,
AP

is work.thanks

I have the same problem using VS Code 1.39.2


captureScreenshots just opens html file

Question Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Question Subject
I just upgraded to using the Swift version of fastlane and now I'm having problems with getting snapshot to work properly. When I run captureScreenshots in my lane the html with all screenshots are opened immediately, but with no screenshots. It seems my UI test scheme is never executed at all.
This is the relevant code in my lane:
let screenshotDevices = [
        "iPhone SE",
        "iPhone 8",
        "iPhone 8 Plus",
        "iPhone X",
        "iPad Pro (9.7-inch)",
        "iPad Pro (12.9-inch)"
    ]

    let screenshotLanguages = [
        "sv", "en-US"
    ]

captureScreenshots(devices: screenshotDevices, languages: screenshotLanguages, launchArguments: [""], outputDirectory: "./fastlane/screenshots_rym", clearPreviousScreenshots: false, localizeSimulator: true, scheme: "MeetingsScreenshotsUITests", numberOfRetries: 3, concurrentSimulators: true)

Here's the output:
DEBUG [2018-08-15 16:03:29.45]: Checking if there are any plugins that should be loaded...
INFO [2018-08-15 16:03:29.68]: loading manifest: /Library/Ruby/Gems/2.3.0/gems/fastlane-2.101.1/fastlane/swift/upgrade_manifest.json
DEBUG [2018-08-15 16:03:29.85]: No missing groups found, so we don't need to worry about adding new groups
DEBUG [2018-08-15 16:03:29.85]: Fastlane.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.25/0.9.25
DEBUG [2018-08-15 16:03:29.85]: DeliverfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.3/0.9.3
DEBUG [2018-08-15 16:03:29.85]: GymfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2018-08-15 16:03:29.85]: MatchfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.1/0.9.1
DEBUG [2018-08-15 16:03:29.85]: PrecheckfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.1/0.9.1
DEBUG [2018-08-15 16:03:29.85]: ScanfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.3/0.9.3
DEBUG [2018-08-15 16:03:29.85]: ScreengrabfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.1/0.9.1
DEBUG [2018-08-15 16:03:29.85]: SnapshotfileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.4/0.9.4
DEBUG [2018-08-15 16:03:29.85]: LaneFileProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2018-08-15 16:03:29.85]: ControlCommand.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2018-08-15 16:03:29.85]: RubyCommand.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2018-08-15 16:03:29.85]: RubyCommandable.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2018-08-15 16:03:29.86]: Runner.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2018-08-15 16:03:29.86]: SocketClient.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2018-08-15 16:03:29.86]: SocketClientDelegateProtocol.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2018-08-15 16:03:29.86]: SocketResponse.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2018-08-15 16:03:29.86]: ArgumentProcessor.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2018-08-15 16:03:29.86]: main.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2018-08-15 16:03:29.86]: RunnerArgument.swift FastlaneRunnerAPIVersion (bundled/target): 0.9.2/0.9.2
DEBUG [2018-08-15 16:03:29.86]: Checking for new user-provided tool configuration files
INFO [2018-08-15 16:03:29.87]: FastlaneSwiftRunner project is up-to-date
DEBUG [2018-08-15 16:03:29.87]: Found changes to user's Fastfile.swift, setting re-build runner flag
DEBUG [2018-08-15 16:03:29.87]: Building FastlaneSwiftRunner
INFO [2018-08-15 16:03:29.90]: $ xcodebuild -showBuildSettings -scheme FastlaneRunner -project ./fastlane/swift/FastlaneSwiftRunner/FastlaneSwiftRunner.xcodeproj
DEBUG [2018-08-15 16:03:30.86]: Parsing project file '/Users/andlin/Documents/XCodeProjects/Stratsys/RunYourMeeting/fastlane/swift/FastlaneSwiftRunner/FastlaneSwiftRunner.xcodeproj' to find selected provisioning profiles
DEBUG [2018-08-15 16:03:30.86]: Finding provision profiles for 'Release'
DEBUG [2018-08-15 16:03:30.88]: Merging provisioning profile mappings
DEBUG [2018-08-15 16:03:30.88]: -------------------------------------
DEBUG [2018-08-15 16:03:30.88]: Primary provisioning profile mapping:
DEBUG [2018-08-15 16:03:30.88]: {}
DEBUG [2018-08-15 16:03:30.88]: Secondary provisioning profile mapping:
DEBUG [2018-08-15 16:03:30.88]: {}
DEBUG [2018-08-15 16:03:30.88]: Resulting in the following mapping:
DEBUG [2018-08-15 16:03:30.88]: {}
INFO [2018-08-15 16:03:31.03]: $ set -o pipefail && xcodebuild -scheme FastlaneRunner -project ./fastlane/swift/FastlaneSwiftRunner/FastlaneSwiftRunner.xcodeproj -destination 'generic/platform=macOS' | tee /Users/andlin/Library/Logs/gym/App-FastlaneRunner.log | xcpretty
INFO [2018-08-15 16:03:31.89]: ▸ Building FastlaneSwiftRunner/FastlaneRunner [Debug]
INFO [2018-08-15 16:03:31.89]: ▸ Check Dependencies
INFO [2018-08-15 16:03:32.01]: ▸ Compiling Fastfile.swift
INFO [2018-08-15 16:03:32.75]: ▸ Linking FastlaneRunner
INFO [2018-08-15 16:03:33.86]: ▸ Running script 'Run Script'
INFO [2018-08-15 16:03:33.90]: ▸ Signing /Users/andlin/Library/Developer/Xcode/DerivedData/FastlaneSwiftRunner-evoqsxleedmxywckzadzttkyhmml/Build/Products/Debug/FastlaneRunner
INFO [2018-08-15 16:03:34.05]: ▸ Build Succeeded
DEBUG [2018-08-15 16:03:34.12]: Waiting for 5 seconds for a connection from FastlaneRunner
INFO [2018-08-15 16:03:34.33]: $ ./fastlane/FastlaneRunner lane screenshotsMeetings logMode verbose swiftServerPort 2000 > /dev/null
DEBUG [2018-08-15 16:03:34.36]: Client connected
DEBUG [2018-08-15 16:03:34.37]: received command:#<Fastlane::ActionCommand:0x00007ffa70a096d8 @method_name="capture_screenshots", @class_name=nil, @command_id="", @args=[named argument: devices, value: iPhone SE,iPhone 8,iPhone 8 Plus,iPhone X,iPad Pro (9.7-inch),iPad Pro (12.9-inch), type: , named argument: languages, value: sv,en-US, type: , named argument: launch_arguments, value: , type: , named argument: output_directory, value: ./fastlane/screenshots_rym, type: , named argument: output_simulator_logs, value: false, type: , named argument: skip_open_summary, value: false, type: , named argument: skip_helper_version_check, value: false, type: , named argument: clear_previous_screenshots, value: false, type: , named argument: reinstall_app, value: false, type: , named argument: erase_simulator, value: false, type: , named argument: localize_simulator, value: true, type: , named argument: buildlog_path, value: ~/Library/Logs/snapshot, type: , named argument: clean, value: false, type: , named argument: scheme, value: MeetingsScreenshotsUITests, type: , named argument: number_of_retries, value: 3, type: , named argument: stop_after_first_error, value: false, type: , named argument: result_bundle, value: false, type: , named argument: concurrent_simulators, value: true, type: ]>
INFO [2018-08-15 16:03:34.39]: ---------------------------------
INFO [2018-08-15 16:03:34.39]: --- Step: capture_screenshots ---
INFO [2018-08-15 16:03:34.39]: ---------------------------------
DEBUG [2018-08-15 16:03:35.28]: Fetching available simulator devices
INFO [2018-08-15 16:03:35.56]: $ xcodebuild -showBuildSettings -workspace ./ToDoApp.xcworkspace -scheme MeetingsScreenshotsUITests
DEBUG [2018-08-15 16:03:37.65]: Fetching available simulator devices
DEBUG [2018-08-15 16:03:37.91]: Found 19 simulators.
DEBUG [2018-08-15 16:03:37.91]: Fetching available simulator devices
DEBUG [2018-08-15 16:03:38.17]: Checking that helper files contain SnapshotHelperVersion [1.12]

+----------------------------+---------------------------------------------------------------------------------+
|                                         Summary for snapshot 2.101.1                                         |
+----------------------------+---------------------------------------------------------------------------------+
| devices                    | ["iPhone SE", "iPhone 8", "iPhone 8 Plus", "iPhone X", "iPad Pro (9.7-inch)",   |
|                            | "iPad Pro (12.9-inch)"]                                                         |
| languages                  | ["sv", "en-US"]                                                                 |
| launch_arguments           | []                                                                              |
| output_directory           | /Users/andlin/Documents/XCodeProjects/Stratsys/RunYourMeeting/fastlane/screens  |
|                            | hots_rym                                                                        |
| output_simulator_logs      | false                                                                           |
| skip_open_summary          | false                                                                           |
| skip_helper_version_check  | false                                                                           |
| clear_previous_screenshots | false                                                                           |
| reinstall_app              | false                                                                           |
| erase_simulator            | false                                                                           |
| localize_simulator         | true                                                                            |
| buildlog_path              | ~/Library/Logs/snapshot                                                         |
| clean                      | false                                                                           |
| scheme                     | MeetingsScreenshotsUITests                                                      |
| number_of_retries          | 3                                                                               |
| stop_after_first_error     | false                                                                           |
| result_bundle              | false                                                                           |
| concurrent_simulators      | true                                                                            |
| workspace                  | ./ToDoApp.xcworkspace                                                           |
| xcode_path                 | /Applications/Xcode.app                                                         |
+----------------------------+---------------------------------------------------------------------------------+

INFO [2018-08-15 16:03:38.22]: Building and running project - this might take some time...

+----------------------+
|   snapshot results   |
+----------------------+
| Device               |
+----------------------+
| iPhone SE            |
| iPhone 8             |
| iPhone 8 Plus        |
| iPhone X             |
| iPad Pro (9.7-inch)  |
| iPad Pro (12.9-inch) |
+----------------------+

INFO [2018-08-15 16:03:38.22]: Generating HTML Report
INFO [2018-08-15 16:03:38.22]: Successfully created HTML file with an overview of all the screenshots: '/Users/andlin/Documents/XCodeProjects/Stratsys/RunYourMeeting/fastlane/screenshots_rym/screenshots.html'
DEBUG [2018-08-15 16:03:38.30]: return_value_type is nil value: true
DEBUG [2018-08-15 16:03:38.30]: sending {"payload":{"status":"ready_for_next","return_object":true,"closure_argument_value":""}}
DEBUG [2018-08-15 16:03:38.30]: received done signal shutting down

Also, it seems my snapshot.swift file with settings is completely ignored. I have to pass in all the settings I wish to use as arguments when calling captureScreenshots.

Anyone? Any suggestions?


Connecting with an existing Consul cluster

Hi,
I played around with socketplane for a while and noticed that it ships with its own embedded consul server.
I'm already running a consul cluster at version 0.5.0. Is it possible to use socketplane with this cluster as running two clusters seems to be redundant and socketplanes consul server is still at version 0.4?

Thanks for raising this issue @Marmelatze.
It's not yet possible to use an external consul cluster but we'd love to see a pull request to add it and/or to update the embedded Consul client


passlib 1.7.4 version bump address a couple bugs.

What this PR does / why we need it:
There are a couple corrections/improvement to the CrypContext class which is used in anchore-engine for password
hasher for database accounts.

CryptContext will now throw UnknownHashError when it can’t identify a hash provided to methods such as CryptContext.verify(). Previously it would throw a generic ValueError.

Which issue this PR fixes
closes: #855
Special notes:

@Toure, is this PR still active? Looks like the pyyaml commit may be included in https://github.com/anchore/anchore-engine/pull/864 already?

@Toure, is this PR still active? Looks like the pyyaml commit may be included in https://github.com/anchore/anchore-engine/pull/864 already?

We still need this update for passlib itself

We still need this update for passlib itself

We still need this update for passlib itself
Yes just waiting on a review.

We still need this update for passlib itself
Yes just waiting on a review.


Sign Up Page

Summary
The current Sign Up page is not connected to the platform. Are we going to keep this page? If so, is there something else we want to include in the sign-up process?

@KirstieJane @GeorgiaHCA @BrainonSilicon
Related Issues

https://github.com/alan-turing-institute/AutSPACEs/issues/265

Tasks

[ ] Redesign the sign up form
[x] Set a condition for navigation template for the registration page
[ ] Set up the backend

Thanks @soledadli ! I do think it is important to collect this information. We will need it to understand the experiences. I think we have two options, to collect the info when the user signs in or when they submit the story.

The former is much simpler for the user, the latter has some more flexibility especially if we are collecting other, optional demographic info which users might wish to share for some stories but not others.

I would recommend for the platform we deploy we should keep it simple and use a redesigned version of this page to test. Could it be supported in the backend trough adding an additional tag to the json file?

This also links to this issue: https://github.com/alan-turing-institute/AutisticaCitizenScience/issues/547. It will need furter consieration but maybe for a later version of the platform

alan-turing-institute/AutisticaCitizenScience#547

@GeorgiaHCA I will work on the re-design and include a simpler frontend form on the current platform for testing now.  For the backend set-up, I think it is definitely possible and we can bring it up to the meet-up tomorrow. 😄

Hiya @soledadli a few comments on this before we implement it

Apart from "Autism researcher"

"Medical professional, carer or social worker" instead of "Healthcare/medical worker for autistic person"

We should also allow people to say if they are autistic or not and whether they have a diagnosis or not separately as not all autistic people have a diagnosis (and not everyone diagnosed agrees with the diagnosis)

Final comment is there are a lot of potential additional pieces of information we may wish to collect, for instance to monitor gender and ethnic diversity, socio-economic etc., as well as co-occuring conditions. This is a next iteration probably though.

At this point a duplicate of #265


Rostopic hz show no messages.

Hi after I ran the launch file, I can see the rostopic list but the rostopic list shows no messages. I have checked all the ros_master and ros_ip. I am not sure what cause the problem.

Hi
the hostname cpr-a200-0630 can not be resolved on the machine you show the screenshot. The master_sync register the all the topics, but ROS can't establish a connection between publisher and subscriber because he can't resolve the hostname.
You have two options:

add cpr-a200-0630 to /etc/hosts
or
set ROS_IP on cpr-a200-0630 before launch ros stuff

I think it works now. Thank you for your help.


How to upload more pictures

The request is not clear. Could you please explain more about your problem?

How to upload multiple pictures at a time?


[Bug] Physic box not showing

The red box is mesh box, when I change physic box size it's not change


Scroll below end for sidebar

VSCode Version: 1.13.1
OS Version: Mac OS Sierra 10.12.5

Feature request. Scroll below end for sidebar. Similar to how we have "editor.scrollBeyondLastLine": true property; it would be cool to have one for the sidebar items.  Especially helpful if a project has a lot of folders.

This feature request will not be considered in the next 6-12 months roadmap and as such will be closed to keep the number of issues we have to maintain actionable. Thanks for understanding and happy coding!


Multi-task BERT for NER

Major changes
This pull request replaces the BERT model for NER with a model that supports multi-task learning on an arbitrary number of input datasets. Like the BiLSTMCRF model, you simply need to load more than one dataset to use multi-task learning
from saber import Saber

saber = Saber()
saber.load_dataset(['dataset_1', 'dataset_2'])

saber.build(model_name='bert-ner')
saber.train()

Unlike the BiLSTMCRF, this model implements smarter batching. During a training epoch, batches are randomly sampled from all the loaded datasets until each dataset is exhausted.
Minor changes
This pull request also introduces prune_output_layers(),
def prune_output_layers(self, output_layer_indices):
    """Removes output layers with indicies not in `output_layer_indices` in `self.model`.

    Args:
        output_layer_indices (list): A list of indicies into the output layers of `self.model`
            to retain.

    Returns:
        `self.model`, where any output layers with indicies not in `output_layer_indices` have
        been removed.
    """

a method that can be called from any Saber model. This method accepts a list of indices corresponding to output layers to retain in a Saber model. All other output layers are dropped. E.g.
saber.models[0].prune_output_layers([0, 2])

Would remove all output layers but the first and third from the saber model at saber.models[0]. This is useful when you train a model under the multi-task setting, but only want to retain one of the classifiers for inference/evaluation/deployment.
Closes
Closes #78. Closes #139.

Pull Request Test Coverage Report for Build 371

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

Totals

Change from base Build 369:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls


[5.8] Fix bug in scheduler

This resolves https://github.com/laravel/framework/issues/28943
Q: What was this caused by?
Carbon does some "under the hood" swaps when the end time is greater than the start time during a between() check. So when we pass in $start = 23:00 & $end = 03:00 - Carbon inverts those numbers since the date was always "today".
So we need to ensure that we've accounted for this before passing in the times and give Carbon a correct date range in addition to the time.
Q: Why did you change some of the original tests?
It turns out some of the original tests were incorrect, and were not actually "testing" what we thought they were.
In the original test suite, the Event class is mocked once per test function. But each subsequent test in the same function would "add" a new rule to the array stack, and therefore we were not testing them in isolation of each other.
This caused the later tests in the one function to be influenced by the earlier ones, and that caused some unexpected issues during the refactor. This is why @driesvints ran into some issues here https://github.com/laravel/framework/issues/28943#issuecomment-505453400
Q: Why do you do check on the startTime vs "now"
So we need to determine if we need to decrease the startTime date (when we've past that current time), or increase the endTime (when we've not gone past the start time). This helps handle the before/after midnight scenario.
I added some extra tests, with various scenarios to try to prove it works as expected.
Would be great if @aarondfrancis could test in his production to confirm this works before we merge this in.
It's been like this for literally years (maybe since 5.0) - so there's no rush here to merge - lets make sure we've all good...

@laurencei thanks for all your work on thus 👍
It may be beneficial to wait until the next major version to do these changes? Because maybe people would expect the old behavior and it could disrupt their scheduling flow. It might be better to inform people of the breaking change in the upgrade guide. Like you said, there's no real rush to fix this.

@driesvints - yeah I was thinking the same thing. It's been like this for so long, that I think of this xkcd comic and worry people are unintentionally relying on a bug: https://xkcd.com/1172/

Yeah I just want to reference this comment by @devcircus where he notes that he expects this behavior atm: https://github.com/laravel/framework/issues/28943#issuecomment-505209601

@driesvints maybe a stopgap until the next major release is to add a warning to the docs? I don't think it's intuitive that this is the actual behavior.

@laurencei let's just move this to the master branch to be sure?

Yes, can this be re-opened on master branch for discussion?

@driesvints @laurencei was this reopened against master? I can't seem to find it.

Issue is still open so I don't think so.

Resent: https://github.com/laravel/framework/pull/29467


Add Icelandic Ship Registry endpoint

This is an addition that creates a new endpoint for the Icelandic Ship Registry. It's based on the car endpoint, as the pages scraped are very similar.
The documentation is on the gh-pages branch so that'll be another pull request.
Checklist

[x] Write tests
[x] Write documentation

Great work @GunnarSturla 🎉 🎉 🎉!


DASHBUILDE-109: Tasks List shows incorrect time in CreatedOn (0.5.x)

Fix + test
@romartin Can you verify please?

Hi @dgutierr , merged: 7af795e58f4e273a0eab0dff7dde7019fa835a5a


PLATUI-2346: Add automatic accessibility assessment

Add accessibility assessment extension to Chrome and Edge browsers
Add file download trait for downloading accessibility assessment results files
Update project version to 0.2.0

Retest this please


Model stumbling on its words

Running the following code:
from parler_tts import ParlerTTSForConditionalGeneration
from transformers import AutoTokenizer
import soundfile as sf
import torch

device = "cuda:0" if torch.cuda.is_available() else "cpu"
model = ParlerTTSForConditionalGeneration.from_pretrained("parler-tts/parler_tts_mini_v0.1").to(device)
tokenizer = AutoTokenizer.from_pretrained("parler-tts/parler_tts_mini_v0.1")

description = "A male speaker with a low-pitched voice delivering his words at a slow pace in a small, confined space with a very clear audio and an animated tone."
prompt = "In the annals of history, the ink that drafted peace often dried under the shadow of future conflicts. Today, we dive deep into the bottom 10 worst peace treaties ever signed, the naive hopes and the grim repercussions they bore, unraveling a tapestry of unintended consequences that would haunt nations for generations. From agreements that sowed the seeds of resentments leading to catastrophic wars, to those that carved up continents disregarding the people who lived there, we explore how peace can sometimes lead to anything but."

input_ids = tokenizer(description, return_tensors="pt").input_ids.to(device)
prompt_input_ids = tokenizer(prompt, return_tensors="pt").input_ids.to(device)
generation = model.generate(input_ids=input_ids, prompt_input_ids=prompt_input_ids)
audio_arr = generation.cpu().numpy().squeeze()
sf.write(os.path.join('output.wav'), audio_arr, model.config.sampling_rate)

Outputs the .wav file posted at this link: http://sndup.net/vzyp
How can I get it to correctly output the prompt text? Is my prompt too large? Am I using the model incorrectly? Thank you!

This looks like a way too long prompt, I would do 1 prompt/sentence at most.

@bkutasi Hey Balázs, any idea how to pimp things to make longer prompts work? Got 256GB RAM and 2x 20GB VRAM RTX 4000.
Sorta waste. ;-) Thought I had a util now to read articles to me.
Greetings from Upper Austria!
G.

@ai-bits Hallo Günter and greetings from Tirol!
So I think we won't be able to ever generate minutes long audios ever, but maybe if we get chucks or some kind of sequential generation implemented (at the moment it was trained on 30 sec voice samples).
So this is kind of a software limitation and wish I had time to fork/contribute to this because I'm really interested in good TTS implementations. If you just want simply more output, you can build a pipeline to call it multiple times for every sentence or line, but the voices will be vastly different as this cant reproduce the same exact voice.
There were some talks about this here:
https://github.com/huggingface/parler-tts/issues/9
https://github.com/huggingface/parler-tts/issues/11

@bkutasi why not ever? What's the blocker to re-training with longer samples?

wish I had time to fork/contribute

Just too many fronts. @ current pace give Parler coupla weeks to mature & use alts 2 do tts.
stt Whisper pretty good v Dragon Naturally Speaking in 90ies. <grin>
Been talking to GPT since July & VS Code for weeks.
Cheers
G.
PS: 49" moni, 4 hd Chrome Windoze: this, Code, Bayern-Ars, MCI-RMA
FCB just won. MCI overtime w/ projector in bed.

@bkutasi Been following the whole AI craze, but lost track what's free & local (and really open needed?) in TTS.
Not yet decided what to think of LocalAI.io, but just got TTS debugged on the M3 Mac. (AMD64 via Docker) Still don't know what special chars sometimes throw it off w/ text from the clipboard.
curl http://localhost:8080/tts -H "Content-Type: application/json" -d "{ \"model\":\"tts-1\", \"input\": \"$(pbpaste)\" }" --output ~/local-ai.wav
Bark,.. available.
Hungarian (?) im Heiligen Landl? ;-)
Cheers
G.


My Tutorials - Completed tab won't load

When user taps on My Tutorials and then the Completed tab up top, they get a never ending "Loading..." message.
Steps to reproduce

Open app (log in if needed)
Tap My Tutorials
Tap Completed tab

Expected behavior
I'd expect to see a list of my completed tutorials, or a message that says I haven't completed any.
Actual behavior
I get a "Loading..." message.

The error in xcode:
EVENT:: ["object": "CategoryRepository", "action": "Last Updated: 2021-05-25 22:24:32 +0000. No refresh required."]
["object": "CompletedRepository", "action": "Failed_repositoryLoad", "reason": "Unable to receive content summary update: failure(Emitron.DataCacheError.cacheMiss)"]
["reason": "Unable to receive content summary update: failure(Emitron.DataCacheError.cacheMiss)", "action": "Failed_repositoryLoad", "object": "CompletedRepository"]
["action": "Failed_repositoryLoad", "reason": "Unable to receive content summary update: failure(Emitron.DataCacheError.cacheMiss)", "object": "CompletedRepository"]
Environment
1.0.7 on iPhone 12pro (from app store), ios 14.5
Can also reproduce in the simulator for ios 14.5 on iPhone 11 and 12

iOS Version: 14.5
raywenderlich.com App Version: 1.0.7
Device: iPhone 11, 12

Hello @heathermh Trying to replicate this issue, have you completed any video tutorials?

Yes @byaruhaf I have completed some. Here’s what this info looks like on the RW web site:

:

@byaruhaf The problem is coming from an old tutorial titled "iOS & Swift Learning Path Trailer 2019" with contentId = 775835. If I bypass that record, the completed list loads just fine.

@heathermh yes I am able to replicate the issue just by completing the iOS & Swift Learning Path Trailer 2019

Thanks for the bug report @heathermh, and thanks for confirming it @byaruhaf.
Any idea what it is about that particular item of content that is problematic? It might be a data issue that I can fix in the backend...

Hi @sammyd
From what I can see is JSON is missing both categories and domains data, see the JSON response below.
can you try adding them in the backend we see if that fixes the issue.
{
  "data": {
    "id": "775835",
    "type": "contents",
    "attributes": {
      "uri": "rw://betamax/videos/2425",
      "name": "iOS & Swift Learning Path Trailer 2019",
      "description": "
The trailer for the iOS & Swift Learning Path 2019.
\n",
      "released_at": "2019-01-17T00:00:00.000Z",
      "free": true,
      "difficulty": null,
      "content_type": "screencast",
      "duration": 60,
      "popularity": 100647,
      "technology_triple_string": "",
      "contributor_string": "",
      "ordinal": null,
      "professional": false,
      "description_plain_text": "The trailer for the iOS & Swift Learning Path 2019.\n",
      "video_identifier": 2425,
      "parent_name": null,
      "accessible": true,
      "card_artwork_url": null,
      "body": ""
    },
    "relationships": {
      "domains": {
        "data": [
        ]
      },
      "child_contents": {
        "meta": {
          "count": 0
        }
      },
      "progression": {
        "data": {
          "id": "253015195",
          "type": "progressions"
        }
      },
      "bookmark": {
        "data": null
      },
      "groups": {
        "data": [
        ]
      },
      "categories": {
        "data": [
        ]
      }
    },
    "links": {
      "self": "http://api.raywenderlich.com/api/contents/775835-ios-swift-learning-path-trailer-2019",
      "video_stream": "http://api.raywenderlich.com/api/videos/2425/stream",
      "video_download": "http://api.raywenderlich.com/api/videos/2425/download"
    }
  },
  "included": [
    {
      "id": "253015195",
      "type": "progressions",
      "attributes": {
        "target": 60,
        "progress": 60,
        "finished": true,
        "percent_complete": 100,
        "created_at": "2021-05-27T04:06:18.358Z",
        "updated_at": "2021-05-27T04:06:34.189Z"
      },
      "relationships": {
        "content": {
          "data": {
            "id": "775835",
            "type": "contents"
          },
          "links": {
            "self": "http://api.raywenderlich.com/api/contents/775835"
          }
        }
      },
      "links": {
        "self": "http://api.raywenderlich.com/api/progressions/253015195"
      }
    }
  ]
}

I have added those pieces, and some other bits that were notably lacking. Let me know if this solves the problem.
Thanks!

@byaruhaf I'm not quite sure what you mean?

@sammyd I was wondering should emitron be updated to ignore bad JSON data sent from the backend instead of throwing a DataCacheError.

@byaruhaf My view is that we shouldn't try and handle server edge cases. That's a large rabbit hole that doesn't provide huge benefits for a lot of work. We should just show an error message

I'm in agreement with @0xTim. Maybe there is some work to show errors rather than hanging? But let's not put any effort into trying to magically recover from them.

Closing this as this particular issue is handled. Please feel free to open up an additional issue with changes to error display if you'd like.