Allow aborting pending requests

Motivation
When working with MSW, users experience an issue that requests may continue pending even after the tests are done. The issue itself is often caused by the user's mistake, but it's still wrong for us to keep requests alive after server.close()/interceptor.dispose() was called.
I'd be careful not to introduce "abort on close" behavior in the Interceptors, because it's not unexpected to dispose of the interceptor while still expecting the request to finish. I'm not sure at the moment what would be the default behavior here, if any.
Proposal
Some sort of unified abort API would be nice to expose from the Interceptors. I can imagine something like this:
// consumer.js
const interceptor = new BatchInterceptor({ interceptors: [...] })

interceptor.on('request', ({ request, controller }) => {
  // Unified means to abort any intercepted request.
  controller.abort()
})

Technical details
All currently supported request modules provide native means to achieve the abort functionality:

http.ClientRequest via request.destroy().
XMLHttpRequest via request.abort().
fetch via AbortController.abort().

Technically speaking, this task is about propagating those methods up the interceptor chain, wrapping them in a nice API, and exposing that API in the argument of request listeners.
Here's a draft of the controller interface:
interface RequestController {
  abort(reason?: unknown): void
}

XMLHttpRequest.abort() doesn't support the reason parameter but that's okay.

I'm also considering whether we should move .respondWith() to the newly introduced controller. That way, the controller is what allows the consumer to control what to to with the intercepted request.

The issue itself is often caused by the user's mistake

What are the mistakes that users often make?
...asking for a friend

Will keep this in mind and close in favor of #520. There are a few corner cases that make the experience around aborting requests unpredictable. I'd love to discuss those before moving forward with this feature.


fix: fix wrong api calling

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


⚠ SceneTime has degraded performance

In 26903c4, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 2078 ms

Resolved: SceneTime performance has improved in 5965798 after 6 minutes.


[Issue]: Opening a .sra file with help of file association (double click) does not open the file correctly

Issue Description
On windows, when double clicking on a .sra file, the sratool is creating a new empty risk assessment instead of displaying the .sra content.
Duplicate Steps
Use sratool 1.1.0 installer to get file association.
Get a valid and non empty risk assessment file, named with .sra extension.
Double click on the .sra file, sratool is launched but with an empty risk assessment.
Expected Results
sratool should open and display .sra file content.
Version Detected
1.1.0 (Default)
Attachments
No response

Tested ok.


Discuss Google Play possible support

As a Pillarbox developer I need to understand how Pillarbox could support Google Cast and at which level. As a developer integrating Pillarbox I want to have a better understanding of what Pillarbox could provide in this area.
Acceptance criteria

Google Cast support has been discussed and our current common understanding documented.

Tasks

[ ] Discuss and document.

We have discussed current capabilities provided by Google Cast sender SDKs on web, Apple and Android devices.
Current landscape

(Source)
On the web and Android casting is more tightly integrated than on iOS:

On the web a tech can be defined for Google Cast sender behavior. video.js tech can be switched between local and Google Cast techs when needed.
On Android a Player common interface is provided to offer transparent interactions with either local or distant playback.
On iOS no such tool exists.

For the receiver we should likely deliver an implementation that works with Pillarbox default sources (URN, URL). Products that need to support more sources will implement a dedicated receiver from scratch, using Pillarbox web as player.
Next steps

Web: A dedicated tech can be implemented.
Receiver: A default receiver can be implemented.
Android: Should be straightforward.
iOS: We should start with a demo integration without actual integration witin the player. Maybe we could provide helpers to build a custom UI (e.g. a GoogleCastPlayer ObservableObject like our Player). Maybe we should stop there, maybe this could reveal a common internal API upon which we could build a common abstraction, like on Android, so that Player could then transparently be used with a Google Cast backed player or an AVPlayer backed one, similar to how techs work for the web. If possible this should likely not be part of PillarboxPlayer but injected externally using this common abstraction.


Improve APIM analytics related queries to reduce DB errors.

Description:
Improve the rdbms-config.xml queries to reduce DB level exceptions.
Fix the DROP INDEX QUERY in PostgreSQL section.
        <recordTableDeleteQueries>
            <query>DROP INDEX {{TABLE_NAME}}_PARTITION_KEY ON {{TABLE_NAME}}
             </query>
            <query>DROP INDEX {{TABLE_NAME}}_TIMESTAMP ON {{TABLE_NAME}}</query>
            <query>DROP TABLE IF EXISTS {{TABLE_NAME}}</query>
        </recordTableDeleteQueries>

Improve the CREATE INDEX query in PostgreSQL section.
       <recordTableInitQueries>
            <query>CREATE TABLE {{TABLE_NAME}} (record_id VARCHAR(128), timestamp BIGINT, data BYTEA, partition_key
                INTEGER, PRIMARY KEY(record_id))</query>
            <query>CREATE INDEX {{TABLE_NAME}}_TIMESTAMP ON {{TABLE_NAME}} (timestamp)</query>
            <query>CREATE INDEX {{TABLE_NAME}}_PARTITION_KEY ON {{TABLE_NAME}} (partition_key)</query>
        </recordTableInitQueries>

By @gnudeep from https://wso2.org/jira/browse/ANLYAPIM-159

Since analytics are refactored, DAS based analytics not using. SP based analytics didn't report this kind of issue and hence closing.


Add option to stop polling in Settings Page.

Add a checkbox in Settings Page to stop moVirt from polling the datacentre to update Events.

@jelkosz given that accounting is already merged and user can disable SYNC I believe we can close this issue?

yes, closing


Update to new panic_implementation attribute

This updates the old lang item to the new #[panic_implementation] attribute, fixing the bootloader on new nightlies

Thanks!

Published as v0.2.0-alpha-005


The edit control in the treeview needs a prompt for entering a container name (NVDA)

Storage Explorer Version: 1.7.0
Platform/OS: All
Architecture: All
Regression From: No
Bug description
There is no feedback when creating a new blob container or folder.  It says 'tree view'. It doesn't say that the user is naming it. (NDVA)
The edit control in the treeview needs a prompt for entering a container name.

The aria label of the input now says what it is for.


[DebugAdapter] Return Object instead of plain string in evaluateRequest

VSCode Version: 0.10.11
OS Version: Mac OS

When we implement our own debug adapter, we need to override evaluateRequest functionality. For now the return result is simply a string per definition
/** Response to "evaluate" request. */
    interface EvaluateResponse extends Response {
        body: {
            /** The result of the evaluate. */
            result: string;
            /** If variablesReference is > 0, the evaluate result is structured and its children can be retrieved by passing variablesReference to the VariablesRequest */
            variablesReference: number;
        };
    }

However if we inspect objects when we debug TypeScript project, we can get a TRUE object

Maybe I miss something, is this possible for custom debug adapters?
Moreover, as it's plain string and it can't produce multiline output as OutputEvent does, we fail to do the right evaluation for ruby inspect override (see https://github.com/rebornix/vscode-ruby/issues/14). Let's say we have such a Class called Person and its inspect is override as "hello \n #{@name}", you will get following results in irb
> person = Person.new("Peng")
 => hello
 Peng
> person
 => hello
 Peng
> person.inspect
 => "hello \n Peng"

In current EvaluateResponse, the result is always "hello \n Peng". I don't see any workaround for this.

Yes this functionality is avialble to all debug adapters. Go, powershell and others use it.
The variablesReference from the response is the key here, if that is greater than zero vscode will treat it as a complex object. Once the user tries to expand the object VSCode will try to get all the children of that variable using the reference.
https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/debug/common/debugProtocol.d.ts#L429

@isidorn thanks for pointing out the usage of variableReference.
Just one more question, is multiline output possible? We've raised the same question in https://github.com/Microsoft/vscode/issues/255 .

@rebornix multiline output should be possible using the output event. If each line ends with a \n we will nicely split them on the vscode side.
If it does not work as expected feel free to create a new issue


Babel creates no working code, because babel using 'use strict' mode.

$ node ./build/server.js
/home/rodzewich/Projects/obcomm/build/server.js:549
                 */HAS_JSCRIPT:'ScriptEngine'in this},/**
                                                ^

TypeError: Cannot use 'in' operator to search for 'ScriptEngine' in undefined
    at /home/rodzewich/Projects/obcomm/build/server.js:549:42
    at Object.<anonymous> (/home/rodzewich/Projects/obcomm/build/server.js:555:62)
    at __webpack_require__ (/home/rodzewich/Projects/obcomm/build/server.js:20:30)
    at Object._typeof (/home/rodzewich/Projects/obcomm/build/server.js:472:13)
    at __webpack_require__ (/home/rodzewich/Projects/obcomm/build/server.js:20:30)
    at Object.<anonymous> (/home/rodzewich/Projects/obcomm/build/server.js:49:16)
    at __webpack_require__ (/home/rodzewich/Projects/obcomm/build/server.js:20:30)
    at /home/rodzewich/Projects/obcomm/build/server.js:40:18
    at Object.<anonymous> (/home/rodzewich/Projects/obcomm/build/server.js:43:10)
    at Module._compile (module.js:541:32)

@rodzewich are you still having this issue?

Off course, but I am fixed problem in the forked branch https://github.com/rodzewich/soy-loader.git . I want you to fix problem in your npm package like I am, please.

We are using babel in our project, and haven't encountered this issue. From what I can tell from the diff, your branch simply adopts rodzewich-closure-templates over closure-templates. Surely the fix then belongs in closure-templates?

In new versions babel used "use strict" as default behavior and your provided module not working. I use<EMAIL_ADDRESS>

Could you fix closure-templates module in code places where code incompatible with use strict mode. You can resolve this issue in forked branch like I am. And you can use forked branch in your module. In my opinion there is no other solution to support new versions of babel.

If it's closure-templates that needs to be fixed, then you should create an issue over at https://github.com/google/closure-templates


how to compare eq classes between multiple runs

Hi authors
I wanted to compare the TCCs between two kallisto-bus runs, which shared the same set of barcodes. I want to do the gene level testing, and I want to avoid dealing with multiple tx-to-ec maps. Is there a way to subset the outputs such that I can use ONE tx-to-ec map for all batches?
Best,
Vivek

Update: I tried to merge the two matrices by Kallisto merge (after tweaking the barcodes to make them unique), but it doesn't seem to merge the ECs containing the same transcripts into one ID, but rather just appends them in one file with different IDs. I suppose there's no existing solution to my problem?

I implemented a custom solution. closing for now.


What are the specific benefits of ER for O365?

Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[ ] The relevant Azure service or technology.
[ ] A link to the published documentation article that you have feedback about.
[ ] Clear, specific feedback that the author can act on.

Pull requests and article contributions
If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

[ ] Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
[ ] Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.
Tech support and product feedback
If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/forums/34192--general-feedback.

Hello @lmurthy-git, Can you share the Azure document link / URL that you are referring to ?
This azure-docs repository deals about feedback related to particular Azure document page (like correcting doc bugs, doc enhancements, product issues related to wrong doc instructions if any, etc.) so that's the reason for asking related Azure document link / URL to get more context of this issue if it's intended to update / correct / enhance anything in the referred Azure document.

Hello,
https://docs.microsoft.com/en-us/office365/enterprise/azure-expressroute
Azure ExpressRoute for Office 365

06/05/2019
5 minutes to read
This article applies to both Office 365 Enterprise and Microsoft 365 Enterprise.
Learn how Azure ExpressRoute is used with Office 365 and how to plan the network implementation project that will be required if you are deploying Azure ExpressRoute for use with Office 365. Infrastructure and platform services running in Azure will often benefit by addressing network architecture and performance considerations. We recommend ExpressRoute for Azure in these cases. Software as a Service offerings like Office 365 and Dynamics 365 have been built to be accessed securely and reliably via the Internet. You can read about Internet performance and security and when you might consider Azure ExpressRoute for Office 365 in the article Assessing Office 365 network connectivityhttps://docs.microsoft.com/en-us/office365/enterprise/assessing-network-connectivity.
But the link Assessing Office 365 network connectivityhttps://docs.microsoft.com/en-us/office365/enterprise/assessing-network-connectivity does not talk about what the security benefits are of using ER for O365.
The two links provide  -  General MS recommendation is don’t use ER for O365, use if required for regulation.  Performance recommendations are provided for Internet, but the details of the security benefits of ER are NOT mentioned. Would be great if they are clarified.

Thanks
-Lavanya
From: KrishnaG-MSFT<EMAIL_ADDRESS>Sent: Thursday, February 20, 2020 12:02 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Lavanya Murthy<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] What are the specific benefits of ER for O365? (#48572)
Hello @lmurthy-githttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flmurthy-git&data=02|01|lmurthy%40newsignature.com|eef7867109b04793e5ff08d7b62ef8cc|a1a2578a8fd34595bb187d17df8944b0|1|1|637178185171145101&sdata=RUyk%2BjG2Ned2Du4LepZN6fLsDXsgiLvEBwpOC%2Fq5KWQ%3D&reserved=0, Can you share the Azure document link / URL that you are referring to ?
Thishttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues&data=02|01|lmurthy%40newsignature.com|eef7867109b04793e5ff08d7b62ef8cc|a1a2578a8fd34595bb187d17df8944b0|1|1|637178185171155099&sdata=stjy9fNpsFwOJesZVQRiLWaAmKSHwRLpe8S1zDbNuZ0%3D&reserved=0 azure-docs repository deals about feedback related to particular Azure document page (like correcting doc bugs, doc enhancements, product issues related to wrong doc instructions if any, etc.) so that's the reason for asking related Azure document link / URL to get more context of this issue if it's intended to update / correct / enhance anything in the referred Azure document.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F48572%3Femail_source%3Dnotifications%26email_token%3DAOTSJHMOVSBLZZQTB3YWOZTRD3ARFA5CNFSM4KYRTUEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMPOOPY%23issuecomment-589227839&data=02|01|lmurthy%40newsignature.com|eef7867109b04793e5ff08d7b62ef8cc|a1a2578a8fd34595bb187d17df8944b0|1|1|637178185171155099&sdata=ym5AKg6NybqCcDK1kKu6WzOazBjJ%2FPbORwz%2FLFFbNN8%3D&reserved=0, or unsubscribehttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOTSJHNHN6E2G3SKNIGPU3LRD3ARFANCNFSM4KYRTUEA&data=02|01|lmurthy%40newsignature.com|eef7867109b04793e5ff08d7b62ef8cc|a1a2578a8fd34595bb187d17df8944b0|1|1|637178185171165134&sdata=4czyJKE2X5r1c%2BLKq2AJgv7eInRuQMp0UA3e1lmDu8I%3D&reserved=0.

@lmurthy-git , Appreciate your patience. We have assigned this issue to the respective content author for updating the document accordingly.


Clang error in gRPC-Core and xcodebuild failed with return code: 65

Question, Bug, or Feature?
Type: Question
Enter Task Name: Xcode@5
Environment

Server - Azure Pipelines

Account name<EMAIL_ADDRESS>Organization: hacksnextdoor
Project name: Lyrist
Build: #20210425.10 Update pipeline-ios.yml for Azure Pipelines

Agent - Hosted

Not sure where to find agent queue name. Pipeline name is Lyrist CI-ios.

Issue Description
Build succeeds in Xcode but fails in the pipeline whether or not the legacy build system is used. I have also tried Debug / Release configurations, manual signing by following the instructions for iOS apps, and auto signing. Nothing seems to work and I'm not sure what's missing.
Relevant pipeline steps
  - task: InstallAppleCertificate@2
    displayName: Install Apple Certificate
    inputs:
      certSecureFile: 'dev-cert.p12'
      keychain: 'temp'

  - task: InstallAppleProvisioningProfile@1
    displayName: "Install Apple provisioning profile"
    inputs:
      provisioningProfileLocation: 'secureFiles'
      provProfileSecureFile: 'dev.mobileprovision'

  - task: CocoaPods@0
    displayName: 'Install iOS dependencies'
    inputs:
      workingDirectory: 'ios'

  - task: Xcode@5
    displayName: 'Build iOS'
    inputs:
      actions: 'build'
      configuration: 'Debug'
      sdk: 'iphoneos'
      xcWorkspacePath: 'ios/Lyrist.xcworkspace'
      scheme: 'Lyrist'

Task logs
Raw logs: https://dev.azure.com/hacksnextdoor/f0e18470-e914-4b62-a081-888527664ce6/_apis/build/builds/217/logs/14
Zipped logs: logs_217.zip
Error logs
    ...
    The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 7.0, but the range of supported deployment target versions is 9.0 to 14.4.99. (in target 'gRPC-Core' from project 'Pods')
** BUILD FAILED **

The following build commands failed:
	CompileC /Users/runner/Library/Developer/Xcode/DerivedData/Lyrist-czsdykdfnicfwodqkmhliduillpf/Build/Intermediates.noindex/Pods.build/Debug-iphoneos/gRPC-Core.build/Objects-normal/armv7/xds_load_balancer_api.o /Users/runner/work/1/s/ios/Pods/gRPC-Core/src/core/ext/filters/client_channel/lb_policy/xds/xds_load_balancer_api.cc normal armv7 c++ com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
##[error]Error: /usr/bin/xcodebuild failed with return code: 65

@DaniilShmelev, any thoughts on this? I updated some dependencies and the build succeeded locally using the following command for Xcode 12.5 (Build version 12E262):
xcodebuild -sdk iphoneos -configuration Debug -workspace ios/Lyrist.xcworkspace -scheme Lyrist clean build CODE_SIGNING_ALLOWED=NO
I don't get the same luck in CI. Is it possible the hosted agent is using stale DerivedData? I tried to cd into the folder and it didn't exist but the error keeps happening in DerivedData/Lyrist-czsdykdfnicfwodqkmhliduillpf.

Hi @psdewar2 there is a header file 'src/core/lib/gprpp/inlined_vector.h' which was not found during compilation according to logs, and there is also warning meaning that 'IPHONEOS_DEPLOYMENT_TARGET' is set to 7.0, but the supported range is 9.0 to 14.4.99. Did you try to set it to some value between 9.0 - 14.4.99?
This error doesn't seem to be related to issue on devops side - there could be a difference between xcode versions on hosted agent machines and your environment causing this issue. You can set up specific xcode version you need using 'xcodeVersion' Xcode task input.
For more details about this specific error I would suggest to open an issue in gRPC repo.

I updated IPHONEOS_DEPLOYMENT_TARGET and still got the same error. As you mentioned, it's probably as simple as Xcode versions. MacOS-latest supports Xcode 12.4. According to https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml#software, macOS 11 which would support Xcode 12.5 is not yet available on Microsoft-hosted agents. Is there an ETA for supporting the new macOS SDK / Xcode version?

@psdewar2 there was a related changes on macOS 11 image - https://github.com/actions/virtual-environments/issues/3226, so it should be available soon.

@anatolybolshakov thanks. Do you know if it's as soon as this month or later in the summer?

@psdewar2 yes, as far as I know it should be no later than the end of current month.

Hi @psdewar2 I'm closing this at the moment since it's not related to pipeline tasks - feel free to track progress about this in https://github.com/actions/virtual-environments/issues/2486


Support for OAuth2

Hi, thank you so much for this!  Do you have any plans to update for OAuth2?

Hi, I have not maintained this in a very long time. Unfortunately I do not have the time to invest in it. If you are willing and able to make the code changes, I will gladly accept the pull request.

Thanks @scottksmith95 - unfortunately we are spread a bit thin right now and do not have the time to invest in it either.  Hopefully someone will be able to at some point.  It would definitely be nice for use in another open source project we are hoping to launch for the DNN community.

Created a pull request.


update ru

Thanks!!

By the way, I noticed you've updated your name in your profile, do you want me to update your name in the contributions to
Russian localization by Ioan (vanja-san)? like with other contributors.
Let me know if you want me to do that (no need to do anything if you are happy with/prefer just vanja-san, but just in case you'd like to update it I thought I should mention it, it's no problem at all. And you can update it in the Russian localization file' authors if you want, so it is used in the localization.txt credits file).

@binarynonsense Let everything be as it is! 😁

OK, no changes needed then :)


Tracking output state

How precise do we want to be in tracking output state?
Currently output can be:
- "pending": the default state when creating an output
- "confirmed": the output is confirmed on the rootchain
- "exiting": the output is being exited
- "piggybacked": the output is a part of an IFE and has been piggybacked

If we want to be really precise why not mark output as challenged or exited?
I don't see benefits for tracking state in greater detail than, pending, confirmed or spent (general name for exited or used as an input for other transaction). What are those benefits?

To sum up:

Marking as challenged or exited introduces additional complexity and is not necessary, we spent output when standard exit is started or ife is piggybacked. We'll still get this info from watcher, which has to track state more precisely than childchain.
When it comes to having outputs "exiting" and "piggybacked" I think that was a product requirement but I don't remember why/ @Pongch @mederic-p do you guys remember why?


Swapping account leads to mass unfriend

Swapping account shows me unfriending all the friends from the preivous account, I run 2 vrcx's and I even created 2 seprate vrcx installs and the issue still occures, Is there a way i can manually change the DB location and manually config that?

It is known and will be fixed next release.


assign existing pull request

What is the proper way to assign someone after a PR has been created?
$ hub pull-request -a 212556808
Waiting for Emacs...
Error creating pull request: Unprocessable Entity (HTTP 422)
A pull request already exists for hubs:fix/show-nonjson-error.

Sorry! That feature isn't available yet. It might be possible in the future.


add ibero university

please add ibero university

Please add my university

@camiloandres2a Pull request merged. Thank you!


Inclusive terminology update

Update master reference to main in onnx-mlir doc
Update rapidcheck to newer commit with inclusive terminology changes
Update benchmark to 1.6.2 with inclusive terminology changes
Update pybind11 to 2.10 with inclusive terminology changes

Jenkins Linux amd64 Build #7934 [push] Inclusive terminology up... started at 10:23

Jenkins Linux ppc64le Build #6998 [push] Inclusive terminology up... started at 11:26

Jenkins Linux amd64 Build #7934 [push] Inclusive terminology up... passed after 1 hr 10 min

Jenkins Linux ppc64le Build #6998 [push] Inclusive terminology up... passed after 1 hr 41 min

Jenkins Linux s390x Build #7950 [push] Inclusive terminology up... passed after 1 hr 43 min


rebar3 plugin

As promised in #19 I've had a go at a rebar3 compiler plugin
So far this is standalone and very basic, relying on an existing caramel installation and very new rebar3 features
I'm not sure about rebar3 support for git submodules, but I'm happy for you to host this as another repo under AbstractMachinesLab if and when you think it's ready.

Also just realised it doesn't handle process.erl. That one I had copied manually into my rebar3 project. I'll iterate a bit more..

Added an example project to the plugin repo.
It's not at all clear to me how to handle the caramel runtime modules. Maybe in the direction of lfe and have the plugin install its own local caramel and take care of everything.
Or this plugin is a short term effort and crane will become the one true way for all caramel projects.
Thoughts? Preferences?

Hej @seanhinde sorry for the delay 🙏🏼  been pretty swamped at work. This looks phenomenal 🚀 and thanks so much for putting time into it.
I'd very much like to have this plugin available since crane may take some time to get to a releasable state, and rebar3 is already here.
I think the plugin will have to detect the arch you're running on and download the right release file from Github for it to work nicely -- then you have control over the entire thing. And since right now it means just compiling an extra process.erl, it doesn't seem like that big of a thing. But let me know :) I haven't written rebar plugins yet.
We'll have to figure out how to compile transitive dependencies, and whether rebar3 supports batch compilation of files (we'll need this since we need to support compiling a.ml, b.ml, c.ml in order or as a unit).
But otherwise I'll try to spend some time with it tonight and give you more feedback. Thanks again 🙌🏼

Hej @seanhinde I tried to use the plugin and while I got a clean rebar3 compile without errors it didn't seem to pick up the .ml file I had around. This was on the example project included.
I essentially:

git cloned
ran rebar3 compile on the example project, saw that caramelc wasn't on path
made sure caramelc was on path
ran rebar3 clean, compile on the example project
run tree -9, and I see this:

.
├── apps
│   ├── beam
│   │   └── src
│   │       ├── beam.app.src
│   │       └── process.erl
│   └── caramel_readme
│       └── src
│           ├── caramel_readme_app.erl
│           ├── caramel_readme.app.src
│           ├── caramel_readme_srv.ml
│           └── caramel_readme_sup.erl
├── _build
│   └── default
│       ├── lib
│       │   ├── beam
│       │   │   ├── ebin
│       │   │   │   ├── beam.app
│       │   │   │   └── process.beam
│       │   │   ├── include -> ../../../../apps/beam/include
│       │   │   ├── priv -> ../../../../apps/beam/priv
│       │   │   └── src -> ../../../../apps/beam/src
│       │   └── caramel_readme
│       │       ├── ebin
│       │       │   ├── caramel_readme.app
│       │       │   ├── caramel_readme_app.beam
│       │       │   └── caramel_readme_sup.beam
│       │       ├── include -> ../../../../apps/caramel_readme/include
│       │       ├── priv -> ../../../../apps/caramel_readme/priv
│       │       └── src -> ../../../../apps/caramel_readme/src
│       └── plugins
│           └── rebar3_caramel
│               ├── ebin
│               │   ├── rebar3_caramel.app
│               │   ├── rebar3_caramel.beam
│               │   └── rebar3_caramel_compiler.beam
│               ├── examples
│               │   └── caramel_readme
│               │       ├── apps
│               │       │   ├── beam
│               │       │   │   └── src
│               │       │   └── caramel_readme
│               │       │       └── src
│               │       ├── config
│               │       │   ├── sys.config
│               │       │   └── vm.args
│               │       ├── LICENSE
│               │       ├── README.md
│               │       └── rebar.config
│               ├── LICENSE
│               ├── README.md
│               ├── rebar.config
│               └── src
│                   ├── rebar3_caramel.app.src
│                   ├── rebar3_caramel_compiler.erl
│                   └── rebar3_caramel.erl
├── config
│   ├── sys.config
│   └── vm.args
├── LICENSE
├── README.md
├── rebar.config
├── rebar.lock
└── tree_stuff

Let me know if I'm doing something wrong here or if I missed any other steps

Ah, nevermind, I had modified the .ml file and forgot about it. It fails silently when there's a type-checking error at the moment but otherwise it does seem to work 🙌🏼  🚀

Nice. I should find some more time to work on it soon. I also have a job, but have half an eye on this being useful there

A couple of immediate challenges:
Erlang's os:cmd/1 ignores the exit code of the command it is running. Solutions to this are a bit painful (there is a project erlexec, or we implement our own using the underlying primitives). If the output of caramelc is pretty regular another option is just to parse its output. I didn't look too closely.
As far as I can tell rebar3 doesn't provide a way to download architecture specific files as a simple dependency.
Both workaroundable.
For module dependencies the rebar plugin has a mechanism. My first idea was to grab the output of caramelc sort-deps and declare that every file earlier in the list than the current file is a dependency. Not sure if that's exactly right though..?

I think we could use os:type/0 to pick the OS for now and see how far that takes us.
For running caramelc we can probably use a port that we open/close. That should give us all the info we need.
Regarding the dependencies, I'd expect the rebar3 dependency tree to automatically build things in the right order, but I may be wrong.
What do you say we move the repo to this org, I'll give you full access, and we can start shaping it up there?

Sounds good to me. If you invite me as a user I can probably just import what I have

Or you can probably clone my repo and import it as a new project here. I'm not that familiar with how GitHub roles work

Hi! I think I sent you an invite as an outside collaborator but it don't really know what's what in that world. I'll look into it, but it seems that you should be able to go to settings and use the "Transfer ownership" button to get the process started from your end as well.
In the meantime I'm looking into making a mix plugin as well.

Nice on the mix front. I fixed the os:cmd issue - rebar3_utils:sh/1 does the right thing.
to trigger a compile failure message it would be good if caramelc will do exit 1 if it finds errors

Good find! That should be the case at the moment, did you find any errors for which it doesn't exit with != 0 ?
Btw, if you're on discord, I started a small server where we can keep the communication more fluid: https://discord.gg/SRpjUE99

I have raised an issue on rebar3 GitHub asking about their built in dependency handling. In theory it should be perfect for us, but I can't get it to work

Closing this since we have the separate repository now: https://github.com/AbstractMachinesLab/rebar3_caramel


Calculate etags on-the-fly for shares directory and home folder

:thinking:

@ishank011 nice! This is the last piece to make shares discoverable for the sync client. This sets the baseline, from now on, optimisations can be made, like caching this virtual etags for 30 seconds (sync discovery), etc ..


[tests-only][full-ci]Check for issue not mentioned to a test

Description
This PR check the expected to failure file and make sure there is not any tests that is not mentioned to an issue.
Also cleans up some description and lines to make maintain format consistency.
Related to
https://github.com/owncloud/QA/issues/716

https://drone.owncloud.com/owncloud/ocis/15638/74/14
runsh: Total unexpected passed scenarios throughout the test run:
webUIWebdavLockProtection/move.feature:146
webUIWebdavLockProtection/move.feature:147

but this PR is 15 commits behind master - I will rebase it.


Fix for inconsistent-missing-destructor-override warning

Disables the no-inconsistent-missing-destructor-override, which fail the clang builds atm.
This follows the C++ Core Guidelines (C.128) which recommend not to add override to dtors.

Coverage remained the same at 99.88% when pulling 4231f4762ab389d597176d1a11feba2aabb0a5ea on offa:clang_override_fixes into e60a539fd1287a6fab95ac88b2905f4ae6f5f2e8 on cpputest:master.


Sound does not work well on some browsers on iOS

Trying to play any clip on the following test page will result in no audible output while on iOS: https://pixijs.io/sound/examples/
Tested on the following iOS versions:
16.6
16.6.1
Tested on the following browsers:
Chrome
Safari
DuckDuckGo
It works just fine when connected to headphones. After its disconnected, trying to play a sound will result in a brief sound and it goes completely silent again.

Duplicate of #175?

@bigtimebuddy not sure, here the issue has nothing to do with the headphones. The sound was already not working before connecting the headphones. I've only mentioned the headphones example for more information. But yes, issue might be related.

Can you try the fix mentioned in that thread and see if that works?

@bigtimebuddy tried the fix mentioned on the other thread but it didn't work. The problem on our end doesn't start when the player switches tabs or connects/disconnects the headphones (I'm guessing this is what the workaround tried to fix). There is no sound from the get go.


Recipe for Schema Stitching

Upfront: Mesh looks like a great tool. Perhaps, non-trivial examples will be configurable with time. As for now, I've tried to do a simple stitching, correlating on the Id passed down from the parent resolver (see repo):
{
  widgets {
    id
    gadgets {
      name
    }
  }
}

where the extra resolver uses the Id from the parent object:
const resolvers = {
    Widget: {
        async gadgets( /*parent*/ { id }, /*args*/ _, { Service2 }) {
            return await Service2.api.gadgets({
                parentId: id,
            });
        }
    }
};

module.exports = { resolvers };

However, this is problematic, as the Mesh cannot know it has to fetch the Id field in the widgets resolver. If one comments out the id, the query fails (with or without federation transform):
{
  widgets {
    # id # will not be queried in `widgets`
    gadgets {
      name
    }
  }
}

with federation  on:
{
  "errors": [
    {
      "message": "Variable `parentId` of type `Int!` must not be null.",
      "locations": [],
      "path": [
        "gadgets"
      ],
      "extensions": {
        "variableName": "parentId",
        "code": "EXEC_NON_NULL_VIOLATION"
      }
    },
...

without federation on:
{
  "error": {
    "errors": [
      {
        "message": "Cannot return null for non-nullable field Query.widgets.",
        "locations": [
          {
            "line": 2,
            "column": 3
          }
        ],
        "path": [
          "widgets"
        ]
      }
    ],
    "data": null
  }
}

expected behaviour would be successful resolver execution like when querying with the Id of the parent (without "id": 1):
{
  "data": {
    "widgets": [
      {
        "gadgets": [
          {
            "name": "Gadget 1/1"
          },
          {
            "name": "Gadget 1/2"
          },
          {
            "name": "Gadget 1/3"
          }
        ]
      },
      ...
    ]
  }
}

This looks similar to the openapi-location-weather example, which failed to run due to certificate issues, but I presume it suffers from the same problem, as data is taken from the parent objects, and I couldn't find any special configuration to say that the fields must be fetched, even if not present in the query

separating out the stitching discussion from #296

Thanks @d-led for opening this issue!
Could you try to use selectionSet to provide required fields like below?
const resolvers = {
    Widget: {
        gadgets: {
        selectionSet: `{ id }`
        async resolve( /*parent*/ { id }, /*args*/ _, { Service2 }) {
            return await Service2.api.gadgets({
                parentId: id,
            });
        }
          }
    }
};

query:
{
  widgets {
    # id # will not be queried in `widgets`
    gadgets {
      name
    }
  }
}

with or without selectionSet:
{
  "errors": [
    {
      "message": "Variable \"$_v0_parentId\" of required type \"Int!\" was not provided.",
      "locations": [],
      "path": [
        "widgets",
        0,
        "gadgets"
      ]
    },
    {
      "message": "Variable \"$_v0_parentId\" of required type \"Int!\" was not provided.",
      "locations": [],
      "path": [
        "widgets",
        1,
        "gadgets"
      ]
    },
    {
      "message": "Variable \"$_v0_parentId\" of required type \"Int!\" was not provided.",
      "locations": [],
      "path": [
        "widgets",
        2,
        "gadgets"
      ]
    },
    {
      "message": "Variable \"$_v0_parentId\" of required type \"Int!\" was not provided.",
      "locations": [],
      "path": [
        "widgets",
        3,
        "gadgets"
      ]
    },
    {
      "message": "Variable \"$_v0_parentId\" of required type \"Int!\" was not provided.",
      "locations": [],
      "path": [
        "widgets",
        4,
        "gadgets"
      ]
    }
  ],
  "data": {
    "widgets": [
      {
        "gadgets": null
      },
      {
        "gadgets": null
      },
      {
        "gadgets": null
      },
      {
        "gadgets": null
      },
      {
        "gadgets": null
      }
    ]
  }
}

Thank you! @d-led We'll keep you posted!

@ardatan thanks!

@d-led https://github.com/Urigo/graphql-mesh/pull/510#issuecomment-636527537
You can check new canary version but you should use additionalTypeDefs near additionalResolvers instead of extend transform.
Could you try and let me know if it works?

@ardatan which alpha do I use as dependency? tried one from #510, but yarn couldn't find it

installed something, and it works!

pushed the commit with the yarn.lock. My initial goal was to achieve the same with federation, but the current example only adds federation to one of the services. Still couldn't get the mesh config right. Do you think, the same scenario could work with federation as well?

I think so. First you need to convert your sources to federated services using Federation transform then add federation merger on top.
You can see how nonfederated graphql service transformed in that example
https://github.com/Urigo/graphql-mesh/tree/master/examples/federation-example
Thank you for your feedback and opening this issue :)

Available in 0.2.0. So, for federation let's move this discussion into different issue. Thank you for your collaboration so far! It helped us to improve Mesh a lot!

@ardatan thanks a lot likewise! Will watch out for progress :)


How can I apply downstream filtering steps to the cleaned VCF to further control the false discovery rate?

How can I apply downstream filtering steps (minGQ filtering, FilterOutlierSamples, BatchEffect, and FilterCleanupQualRecalibration) to the cleaned VCF to further control the false discovery rate?

MinGQ filtering is being deprecated in favor of the FilterGenotypes workflow. We are still working on documentation but here is an outline:
Main steps:

JoinRawCalls
FormatVCFForGatk (if needed)
SVConcordance
FilterGenotypes

Instructions:
Generate inputs and run JoinRawCalls from the main branch to produce a clustered VCF of raw calls for the entire cohort.
Note: the input VCFs here use svtk-style END fields, which need to be modified no matter what version of the pipeline was used, so make sure FormatVcfForGatk.formatter_args is “--fix-end”
If your “cleaned” VCF was generated prior to v0.22-beta, you must run  FormatVcfForGatk to produce a GATK-formatted cleaned VCF. If you used a later version of the pipeline, you can skip this step.
IMPORTANT: The "formatter_args" parameter may need to be modified depending on exactly what version of the pipeline was used.
If your cleaned VCF has invalid END tags, you must include the "--fix-end" flag. You can check to see if there are any END fields less than the POS of the record (e.g. for BND records).
If your cleaned VCF has GQ values are scaled to 0-999, you must use the "--scale-down-gq" flag to rescale to 0-99. If you’re unsure, you should be able to tell by looking at the VCF.
Run SVConcordance with the GATK-formatted cleaned VCF as "eval_vcf" and JoinRawCalls VCF as "truth_vcf".
Run FilterGenotypes with the SVConcordance VCF
The “ploidy_table” is generated during JoinRawCalls but wasn’t included as an output for the v0.28.4-beta release. If you kept intermediate files from JoinRawCalls, you can use the output from the CreatePloidyTableFromPed task. Otherwise, you will need to generate the ploidy table manually using this script: https://github.com/broadinstitute/gatk-sv/blob/main/src/sv-pipeline/scripts/ploidy_table_from_ped.py
Recommended default "no_call_rate_cutoff" is 0.05 but can be adjusted
Modify "sl_filter_args":
High specificity (5% DNR): "--small-del-threshold 93 --medium-del-threshold 85 --small-dup-threshold -51 --medium-dup-threshold -4 --ins-threshold -13"
High sensitivity (15% DNR): "--small-del-threshold -53 --medium-del-threshold -12 --small-dup-threshold -105 --medium-dup-threshold -81 --ins-threshold -97"
Note these thresholds were generated for the first AoU-SV release, which had relatively little technical noise. You may want to iterate on these thresholds for your dataset until results are satisfactory.
Review the MainVcfQc plots generated with this workflow and compare them to the “Structural Variants QC Results” section of the AoU-SV quality report: https://support.researchallofus.org/hc/en-us/articles/4617899955092-All-of-Us-Genomic-Quality-Report.
We recommend using de novo rates as a proxy for your FDR. Plots of this are generated in MainVcfQc if you have at least one trio.
7,000-11,000 are typical counts for total (non-BND) SVs per genome.
Higher thresholds will increase precision.
For larger call sets, you can increase the amount of sharding with RecalibrateGq.recalibrate_records_per_shard and filter_vcf_records_per_shard depending on which parts are slow. Defaults for both are 20,000. It is recommended to try to keep the total number of shards under 1000.


emacs: Add custom elpa fetcher

Motivation for this change
Elpa (and by extension nongnu) only serves the latest version of a given package uncompressed.
Once that release is no longer the latest & greatest it gets archived and compressed meaning that both the URL and the hash changes.
To work around this issue we fall back to the URL with the .lz suffix and if that's the one we downloaded we uncompress the file to ensure the hash matches regardless of compression.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Hi, I'm not sure how the release process works, but is there any chance that this could be backported to 21.05?

Actually, I read the contributing doc and created this one: #135549


Implementing a "hide all children except one" [Navigation]

Hello,
I'm trying to implement a sort of navigation.
I want to set an index and hide all children except one that is the one provided from the index.
With this method:
	set index(index) {
		this.children = this.children.map((e,i)=>({
			...e,
			alpha: Number(i == index)
		}));
	}

I receive this errors:
Patch of private property '__id' is not allowed
...

How I can accomplish that?
Regards
Mattia
UPDATE:
I've fixed like this:
set index(index) {
		this.children.forEach((e,i) => {
			this.childList.getAt(i).setSmooth('alpha', Number(i == index));
		});
	}

But I want to ask if someone knows some minimal pattern more that this one. I do not like to reuse the getAt inside the loop.

Actually i've solved managing alpha in the focus handlers of childeren an leave to the parent the responsability of the index.
If nothing else It can be closed.


example - internal columns leak

I tried to simulate this https://keboola.zendesk.com/agent/tickets/9356
But it looks like it was caused by copied state.

zavírám, celé to byla blbost.


HTTP error 403 Forbidden

I've recently been facing the problem that the bot disconnects and keeps giving HTTP error 403 Forbidden, does anyone know how to solve it?
distube client:
client.distube = new DisTube(client, {
  emitNewSongOnly: true,
  emitAddSongWhenCreatingQueue: false,
  emitAddListWhenCreatingQueue: false,
  nsfw: true,
  plugins: [
    new SpotifyPlugin(),
    new YouTubePlugin({ cookies: cookiesJson }),
    new SoundCloudPlugin(),
    new YtDlpPlugin(),
  ],
});

Player.js
const { EmbedPlayer } = require("../util/embed/embedPlayer");
const embed = new EmbedPlayer();
const { EmbedClass } = require("../util/embed/embedBase");
const embedClass = new EmbedClass();
const { ValidationServer } = require("../util/serverValidation");
const vali = new ValidationServer();

module.exports = {
  name: "play",
  aliases: ["p"],
  description: "Enter your song link or song name to play",
  usage: "play <URL/song name>",
  voiceChannel: true,
  options: [
    {
      name: "search",
      description: "The song link or song name",
      type: 3,
      required: true,
    },
  ],

  async execute(client, message, args) {
    if (vali.vali(client, message) === true) {
      const { member } = message;
      const voiceChannel = member.voice.channel;
      const string = args.join(" ");

      try {
        if (!args[0]) {
          return embed.noSong(message);
        }

        await client.distube.play(voiceChannel, string, {
          textChannel: message.channel,
          member: member,
        });
      } catch (err) {
        console.error(err);
        return embed.genericError(message);
      }
    } else {
      return embedClass.noPermission(message);
    }
  },
};

DisTube version: ^5.0.2
discord.js version: ^14.15.3
Node.js version: v20.11.1
Operating system: Win 11

Log ffmpeg
error.txt

Not distube issue.
Please report at https://github.com/distubejs/extractor-plugins/issues


[Android] user id not filled in for native crashes if you set user id after bugsnag.init

Description
I am setting the user id and I want to see that same user id on bugsnag issues for native crashes.
I think the problem is because I am calling Bugsnag.Init before I set the user id, so it sends the previous native crash before the user id is set. But that is going to be a typical workflow and there should be a mechanism to handle it.
Issue
When I look at the bugsnag issue, the user id is the bugsnag generated user id and not my custom user id.
Environment
Android

bugsnag-unity version: 4.2.0
Unity version: 2017.4.14f1
Operating system name and version: building with OSX
Target platform names and versions: Android 8.0 on HUAWEI ANE-LX2 (P20 Lite)
Initializing bugsnag via the Unity UI or in code? UI

Example code snippet
// after your app starts up, run this code somewhere to set the user id
// this will run after bugsnag initializes, because we want to capture errors and exceptions from the first moment possible, but we dont know their user id until later
		BugsnagUnity.Bugsnag.SetUser(guid, email, name);
		BugsnagUnity.Bugsnag.BeforeNotify(report => {
			report.Metadata.Add("user", new Dictionary<string, object> {{ "admin", isAdmin }, { "guid", guid }});
		});

// run this method and it will crash your android device. start it up again and you should get a SIGSEGV error in Bugsnag.
// Then look at your report in bugsnag, the user id will not be set properly.
public void MemoryCrash() {
	StartCoroutine(MemoryCrashCor());
}

IEnumerator MemoryCrashCor() {
	Debug.Log("MemoryCrashCor");
	System.Text.StringBuilder sb = new System.Text.StringBuilder();
	List<string> list = new List<string>();
	for (int i = 0; i < int.MaxValue; ++i) {
		if (i % 100 == 0) {
			yield return 1;
		}
		try {
			sb.AppendFormat("!! {0},{1},{2},{3} !!\n", i, i * 2, Mathf.Pow((float)i, 2f), int.MaxValue - i);
			list.Add(sb.ToString());
		} catch {
			Debug.Log("MemoryCrashCor .... BOOOM!!");
		}
	}
}

Note: In the Android docs it says there is a setting called persistUserBetweenSessions  (https://docs.bugsnag.com/platforms/android-kotlin/configuration-options/#setpersistuserbetweensessions) but that doesn't seem to exist for Unity. Mabye this would solve the problem?

Thanks for the report, @tayl0r. This seems like a bug as calling SetUser should include the same ID in native reports.


Model name suffix

Is there any chance of adding functionality to add a suffix to the generated models as the generated names tend to clash with our POCO domain model names?

#213

Yes, and directly related to #213 which is about prefix. Adding to backlog too.

Closing as duplicate of #213 which is in-progress.


Fix timestamp format to match the SDK docs.

The SDK docs say the timestamp should not have a timezone, and the example timestamp doesn't include microseconds: https://docs.sentry.io/clientdev/attributes/
This pull fixes the format to match what the docs describe.  Addresses https://github.com/getsentry/sentry-elixir/issues/99.

Thanks for opening this issue.  It looks like the time is correct in some way, as it shows when it was sent:

I tested the changes made here, and was still unable to get "first seen" to show up.
This may be an issue with the Sentry server?

Well that's disappointing... I was hoping this would fix it.  Does it at least cause the timestamp field to be accepted by the server?  See #99 to see my screenshot of the server UI indicating that the timestamp field was ignored.  If it at least fixes that then this pull should still be valuable.

I haven't seen that error myself yet, and wasn't able to get it using the old format or the new format.  Does it happen every time for you?
The changes are still valuable, as I'd rather we follow what the docs say is the correct format.  Since it persists, it may be an upstream issue within Sentry itself.

I'm not consistently getting the error, no.  Funny enough, I just enabled release tracking in my app, and now the "first seen" and "last seen" are working...  but I still get the error at the top warning me that timestamp was disregarded.


Support for HEAD verb

For a project I'm busy with, I need support for HEAD, and noticed that it is not implemented as far as I can see.
Is there a reason for this? Would be happy to add it and submit a PR unless there is a good reason why it doesn't exist.

The good reason is … none at all.
I’d welcome a pull request! Some design questions:

What kind of entity should it return? Entity<Data> with zero-length data? Or Entity<Void> to help code not accidentally parse an empty response?

How does this interact with the transformer pipeline? Should Siesta take special measures to prevent transformers from operating on HEAD responses?

Request currently guarantees that any request that calls onSuccess will also call exactly one of onNewData or onNotModified. I’d like to preserve that guarantee. Since a HEAD doesn’t actually return any data, onNewData seems like a bit of a misnomer — but I tend to think that we should interpret it as meaning “there would be new data if you made a GET request,” and thus interpret HTTP response codes exactly as we do for the other methods. Thoughts on that?


Fix react-native-smooch.podspec

Fix issue where source files would not be included when installing this pod.

This is also fixed in https://github.com/smooch/react-native-smooch/pull/47 and I will be using that


STAR-1217 Add CompactionProgressListener

Allows to register listeners to observe table operations called in
compaction manager.
This is port of CNDB-3258

No test is added yet for the code coverage.

@jasonstack Thank you for review. I added tests for the functionality of the patch. Do you mind to review?


ExecutorBeanPostProcessor creates proxies with null fields values

Hi,
I found a problem during creation of async executors proxies in ExecutorBeanPostProcessor.
Namely when creating proxies for the executors they are created with null fields inside, which is a bit problematic if you use any delegating executor, e.g. DelegatingSecurityContextSchedulingTaskExecutor.
From what I have seen, CGLib uses no-args constructor if no constructor arguments have been passed, hence the fields have null values
I use Greenwich.SR1 train/release
Can you help me with that?

All CGLIB proxies have null fields. You shouldn't be using those. What is exactly your problem?

@marcingrzejszczak My problem is that ExecutorBeanPostProcessor creates proxy of DelegatingSecurityContextSchedulingTaskExecutor which during execution forwards call to yet another task executor. It cannot do so, because the delegate field is null

ok, can you create a small sample that replicates this issue? ALso can you check the latest snapshots, cause AFAIR I've added some fixes at some point

Hello,
I have the same issue, I notice the following log when I start my server:

o.s.aop.framework.CglibAopProxy          : Unable to proxy interface-implementing method [public final java.util.List org.springframework.security.concurrent.DelegatingSecurityContextExecutorService.invokeAll(java.util.Collection,long,java.util.concurrent.TimeUnit) throws java.lang.InterruptedException] because it is marked as final: Consider using interface-based JDK proxies instead!

In my code I do:
executorService.invokeAll(...)
I tried with an executorService which have an invokeAll method that is not final and it works.

We can't wrap final methods with cglib. Just try no to use them if possible. My request for a sample is still active

DelegatingSecurityContextAsyncTaskExecutor has such final methods; registering one as a bean and and then trying to use it anywhere in my app, I get the same issue.
@Configuration
public class AppConfig {
    @Bean
    public Executor executor(TaskExecutorBuilder: builder) {
        return new DelegatingAsyncTaskExecutor(builder.build());
    }
}

This is something that worked fine before 2.1.1. I need to use the above decorator, so I guess my only option is to not use spring-cloud-sleuth?

Your other option is to do your own decorator.
public class MyExecutorServiceDecorator implements ExecutorService {

    private final ExecutorService delegate;

    public OcpExecutorServiceDecorator(ExecutorService executorService) {
        this.delegate = executorService;
    }

    @Override
    public void shutdown() {
        delegate.shutdown();
    }

    @Override
    public List<Runnable> shutdownNow() {
        return delegate.shutdownNow();
    }

    @Override
    public boolean isShutdown() {
        return delegate.isShutdown();
    }

    @Override
    public boolean isTerminated() {
        return delegate.isTerminated();
    }

    @Override
    public boolean awaitTermination(long timeout, TimeUnit unit) throws InterruptedException {
        return delegate.awaitTermination(timeout, unit);
    }

    @Override
    public <T> Future<T> submit(Callable<T> task) {
        return delegate.submit(task);
    }
....

Can someone create a test that replicates this issue? I'd love to help but I need to have something to work on.

I replicate the problem in this repository
https://github.com/roll57/scs1336

I've opened a PR with a proposed fix for this.
I noticed that the wrapExecutor explicitly checked if the "execute" method is final or not, in addition to checking if the class if final, when determining whether or not to use a cglib proxy. All of the other relevant methods did not have this check at all, and instead only checked if the class is final.
The proposed fix will check if the bean has any final methods, and use the fallback jdk proxy if there are. The one issue I encountered was with ThreadPoolTaskExecutor, since it is not an interface, proxying won't really work at all if there are any final methods. Therefore I changed the code just to always fallback to the Sleuth wrapper implementation.


SPLIT_VARIABLE_DECLARATION assist to handle unreferenceable type

As hinted in the review of https://dart-review.googlesource.com/c/sdk/+/209962

It's possible for writeType to fail to write the type, such as when the type is a private type that can't be referenced in the current context. We haven't been as careful in the past as we should have been, but uses of writeType should be guarded similar to the way we did in analysis_server/lib/src/services/correction/dart/add_type_annotation.dart. Otherwise this will end up just deleting the return type, which isn't what we want.

This issue is related to SPLIT_VARIABLE_DECLARATION

https://dart-review.googlesource.com/c/sdk/+/210127

Closed by https://github.com/dart-lang/sdk/commit/c9d954efe7c7a71d2bf2c2ca385855b82fbfb379


[Feature] Improved JSON Schema support

Add some extra support for JSON schema, to work better with the langchain examples:

Allow definitions to be given in a definitions key, as well ad $defs
Allow for single-entry allOf blocks

@nopdive might have thoughts too

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 59.83%. Comparing base (06cc3f5) to head (ca5e477).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #787      +/-   ##
==========================================
+ Coverage   55.51%   59.83%   +4.31%
==========================================
  Files          55       55
  Lines        4071     4078       +7
==========================================
+ Hits         2260     2440     +180
+ Misses       1811     1638     -173

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

LGTM -- this really helps on supporting a wider variety of json schemas!


What is Otel ?

Interesting project. In the README i see mention of Otel, what is it ?

Otel is shorthand for opentelemetry, a set of open source libraries for traces/logging/metrics.


Can't compile

Not sure what I'm doing wrong but can't get this working:
when I run: esphome -v run thermostat-number-minimal.yaml
I get below
INFO Reading configuration thermostat-number-minimal.yaml...
Failed config

opentherm: [source thermostat-number-minimal.yaml:25]

  Component not found: opentherm.
number.opentherm: [source thermostat-number-minimal.yaml:28]

  Platform not found: 'number.opentherm'.
  platform: opentherm
  t_set:
    name: Boiler Control setpoint

Whatever I do, can't get opentherm to be found.
In the same folder as my thermostat-number-minimal.yaml
there is also this tree folder with stuff brought in from git:
.esphome\external_components\e2aecb28\components\opentherm\

So git kinda works to bring in the repo source, but after that don't know why it still complains about opentherm not being found.

Did you clone the repo, or did you copy thermostat-number-minimal.yaml into your own esphome folder? If the latter, did you replace the link to the external component with the GitHub link like this?
external_components:
  source: github://arthurrump/esphome-opentherm@main

Which version of esphome are you using?

I just tried compiling this configuration in a fresh and empty folder using the latest esphome v2022.12.4:
# An extremely minimal configuration which only enables you to set the boiler's
# water temperature setpoint as a number.

esphome:
  name: thermostat-number-minimal

external_components:
  source: github://arthurrump/esphome-opentherm@main

esp8266:
  board: d1_mini

logger:

api:
ota:
wifi:
  ap:
    ssid: "Thermostat"
    password: "MySecretThemostat"
captive_portal:

opentherm:

number:
  - platform: opentherm
    t_set:
      name: "Boiler Control setpoint"

This seems to work fine for me. The repo is indeed cloned into the .esphome\external_components\... folder and I also see the .h and .cpp files appear in the .esphome\build\thermostat-number-minimal\src\esphome\components\opentherm folder.

Tried in a new folder with the above mentioned example, esphome v2022.12.4.
The repo is brought in as a d4d3a138 folder inside .esphome/external_components
But that is it, no compilation takes place, because it complains of Component not found: opentherm.
If I remove the line with
opentherm: from config yaml file then I can see everything compiling (obvious without the component).
I also tried to run directly compile_all.py, the examples all reference directly components\opentherm folder, but I get the same error.

Then the problem might be with Python, that it is somehow unable to load the project and thus esphome is unable to find the component. What version of Python are you running? I'm on 3.10 locally and CI is running on 3.9, but I might well be using Python features that are not available in earlier versions.

Found the issue will trying to run generate_schema_docs.py
After running
pip install typing-extensions everything works now, I can compile successfully.
Don't know why this missing module is required and not flagged as such when trying to compile the config yaml files.

Seems this issue is rearing it's head again in ESPHome 2023.11. I rolled back to ESPHome 2023.10 and it works fine there.

Yes, I confirm, got the "Component not found: opentherm." after the update to 2023.11.0.
BTW never had that issue before.
I use ESPhome in docker on debian.
Installed the extension on OS level
sudo apt install python3-typing-extensions
Didn't help.
Please advise

Fixed in ESPHome 2023.11.2

@wildekek I've updated the esphome but the issue is still existing
Here is a validation error
INFO ESPHome 2023.11.2
INFO Reading configuration /config/014-wemos-d1-mini.yaml...
Failed config

opentherm: [source /config/014-wemos-d1-mini.yaml:45]

  Component not found: opentherm.
  ch_enable: True
  dhw_enable: True
output.opentherm: [source /config/014-wemos-d1-mini.yaml:49]

  Platform not found: 'output.opentherm'.
  platform: opentherm
  t_set:
    id: t_set
    min_value: 35
    max_value: 55
    zero_means_zero: True
sensor.opentherm: [source /config/014-wemos-d1-mini.yaml:65]

  Platform not found: 'sensor.opentherm'.
  platform: opentherm
  rel_mod_level:
    name: Gas Boiler Modulation
    icon: mdi:chart-bell-curve
  t_boiler:
    name: Gas Boiler Temperature
    icon: mdi:coolant-temperature
  t_dhw_set:
    name: Gas Boiler DWH Setpoint
    icon: mdi:hand-water
  dhw_flow_rate:
    name: Boiler Water flow rate in DHW circuit
  t_storage:
    name: Boiler Solar storage temperature
  t_flow_ch2:
    name: Boiler Flow water temperature CH2 circuit
  t_dhw_set_ub:
    name: Boiler Upper bound for adjustement of DHW setpoint
  t_dhw_set_lb:
    name: Boiler Lower bound for adjustement of DHW setpoint
  max_t_set_ub:
    name: Boiler Upper bound for adjustement of max CH setpoint
  max_t_set_lb:
    name: Boiler Lower bound for adjustement of max CH setpoint
  max_t_set:
    name: Boiler Maximum allowable CH water setpoint
binary_sensor.opentherm: [source /config/014-wemos-d1-mini.yaml:176]

  Platform not found: 'binary_sensor.opentherm'.
  platform: opentherm
  flame_on:
    name: Gas Boiler Flame
    icon: mdi:fire
  diagnostic_indication:
    name: Gas Boiler Diagnostic
    entity_category: diagnostic
switch.opentherm: [source /config/014-wemos-d1-mini.yaml:185]

  Platform not found: 'switch.opentherm'.
  platform: opentherm
  ch_enable:
    name: Gas Heating
    mode: restore_default_on
    icon: mdi:water-boiler
  dhw_enable:
    name: Gas Hot Water
    mode: restore_default_off
    icon: mdi:hand-water

And the config itself
substitutions:
  device_name: 014-wemos-d1-mini

esphome:
  name: ${device_name}
  comment: Gas Bolier

external_components:
  # Replace with a direct reference to GitHub in your own configuration
  source: github://arthurrump/esphome-opentherm@main
  #source:
  #  type: local
  #  path: ./opentherm/

esp8266:
  board: d1_mini
  restore_from_flash: True

# Enable logging
logger:
#  level: WARN
#  baud_rate: 0

# Enable Home Assistant API
api:

ota:
  password: "f5923c3172c4457c9facb9908a4cc5ae"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: ${device_name}
    password: !secret fallback_password

captive_portal:

#web_server:
#  port: 80

opentherm:
  ch_enable: true
  dhw_enable: true

output:
  - platform: opentherm
    t_set:
      id: t_set
      min_value: 35
#      auto_max_value: true
      max_value: 55
      zero_means_zero: true

#number:
#  - platform: opentherm
#    t_dhw_set:
#      name: "Gas Boiler DHW Setpoint"
#    max_t_set:
#      name: "Gas Boiler Max Setpoint"

sensor:
  - platform: opentherm
    rel_mod_level:
      name: "Gas Boiler Modulation"
      icon: mdi:chart-bell-curve
    t_boiler:
      name: "Gas Boiler Temperature"
      icon: mdi:coolant-temperature
    t_dhw_set:
      name: "Gas Boiler DWH Setpoint"
      icon: mdi:hand-water

#    ch_pressure:
#      name: "Boiler Water pressure in CH circuit"
    dhw_flow_rate:
      name: "Boiler Water flow rate in DHW circuit"
#    t_dhw:
#      name: "Boiler DHW temperature"
#    t_outside:
#      name: "Boiler Outside temperature"
#    t_ret:
#      name: "Boiler Return water temperature"
    t_storage:
      name: "Boiler Solar storage temperature"
#    t_collector:
#      name: "Boiler Solar collector temperature"
    t_flow_ch2:
      name: "Boiler Flow water temperature CH2 circuit"
#    t_dhw2:
#      name: "Boiler Domestic hot water temperature 2"
#    t_exhaust:
#      name: "Boiler Exhaust temperature"
#    burner_starts:
#      name: "Boiler Number of starts burner"
#    ch_pump_starts:
#      name: "Boiler Number of starts CH pump"
#    dhw_pump_valve_starts:
#      name: "Boiler Number of starts DHW pump/valve"
#    dhw_burner_starts:
#      name: "Boiler Number of starts burner during DHW mode"
#    burner_operation_hours:
#      name: "Boiler Number of hours that burner is in operation (i.e. flame on)"
#    ch_pump_operation_hours:
#      name: "Boiler Number of hours that CH pump has been running"
#    dhw_pump_valve_operation_hours:
#      name: "Boiler Number of hours that DHW pump has been running or DHW valve has been opened"
#    dhw_burner_operation_hours:
#      name: "Boiler Number of hours that burner is in operation during DHW mode"
    t_dhw_set_ub:
      name: "Boiler Upper bound for adjustement of DHW setpoint"
    t_dhw_set_lb:
      name: "Boiler Lower bound for adjustement of DHW setpoint"
    max_t_set_ub:
      name: "Boiler Upper bound for adjustement of max CH setpoint"
    max_t_set_lb:
      name: "Boiler Lower bound for adjustement of max CH setpoint"
    max_t_set:
      name: "Boiler Maximum allowable CH water setpoint"

    # Get the boiler setpoint in celcius
  - platform: template
    id: boiler_setpoint_temperature
    name: "Gas Boiler CH setpoint"
    lambda: |-
      return id(t_set).state;
    update_interval: 1s
    unit_of_measurement: "°C"
    device_class: "temperature"
    state_class: "measurement"
    accuracy_decimals: 2

  - platform: homeassistant
    id: ch_room_temperature
    entity_id: sensor.current_temp_gas
    filters:
      # Push room temperature every second to update PID parameters
      - heartbeat: 1s

  - platform: pid
    name: "PID Climate RESULT"
    type: RESULT

  - platform: pid
    name: "PID Climate ERROR"
    type: ERROR

  - platform: pid
    name: "PID Climate PROPORTIONAL"
    type: PROPORTIONAL

  - platform: pid
    name: "PID Climate INTEGRAL"
    type: INTEGRAL

  - platform: pid
    name: "PID Climate HEAT"
    type: HEAT

  - platform: pid
    name: "PID Climate KP"
    type: KP

  - platform: pid
    name: "PID Climate KI"
    type: KI

  - platform: uptime
    name: ${device_name} Uptime
    id: node_uptime
    unit_of_measurement: "s"

binary_sensor:
  - platform: opentherm
    flame_on:
      name: "Gas Boiler Flame"
      icon: mdi:fire
    diagnostic_indication:
      name: "Gas Boiler Diagnostic"
      entity_category: diagnostic

switch:
  - platform: opentherm
    ch_enable:
      name: "Gas Heating"
      mode: restore_default_on
      icon: mdi:water-boiler
    dhw_enable:
      name: "Gas Hot Water"
      mode: restore_default_off
      icon: mdi:hand-water
  - platform: template
    name: "PID Autotune"
    icon: mdi:tune-vertical-variant
    turn_on_action:
      - climate.pid.autotune:
          id: pid_climate
          noiseband: 0.1
  - platform: restart
    name: ${device_name} Restart

climate:
  - platform: pid
    id: pid_climate
    name: "Gas Boiler"
    heat_output: t_set
    default_target_temperature: 10
    sensor: ch_room_temperature
    icon: mdi:home-thermometer
    control_parameters:
      kp: 0.1
      ki: 0.0
      kd: 0.0

Works only in esphome:2023.9.3 for me.
docker run --rm --net host -v "${PWD}":/config -it ghcr.io/esphome/esphome:2023.9.3 run examples/thermostat-pid-basic.yaml

@andreaconfa @ymatsiuk I've got it working by switching to another repo
source: github://ov1d1u/esphome-opentherm@main

Hello, I have this error:
UnknownPackageError: Could not find the package with 'ihormelnyk/OpenTherm Library @ 1.1.3' requirements for your system 'linux_aarch64'

Hello, I have this error: UnknownPackageError: Could not find the package with 'ihormelnyk/OpenTherm Library @ 1.1.3' requirements for your system 'linux_aarch64'
with source: github://ov1d1u/esphome-opentherm@main

I have the same error.

@Slevinoo , use github://Bugracer/esphome-opentherm@main
I made the corrections

@Slevinoo , use github://Bugracer/esphome-opentherm@main I made the corrections

@Bugracer thx! That worked!
I can see a 1.1.5 version of the library is available, but your codebase uses 1.1.4. Maybe it makes sense to switch to the new version? I appreciate your efforts.

Can't compile "Component not found: opentherm." ESPHome Current version: 2024.10.0
sudo apt install python3-typing-extensions

Didn't help.
~$ python3 --version
Python 3.11.2
use
external_components:
source: github://arthurrump/esphome-opentherm@main


Fix missing local parameters in SwaggerToSdk

Fix typo in the file before committing it Friday...
The current version is broken.

Build failed in Node because the Node configuration file is not using the last configuration format.

https://github.com/Azure/azure-rest-api-specs/pull/249 is more recent


Question: Extra Nginx config not read from kong.yml?

Maybe I'm not doing it right, but from what I understood I could use nginx config block in kong.yml to add new sites to be served. Is this possible or I'm understanding it wrong and instead of trying to push stuff inside kong I should just link it with standalone nginx container? I'm using kong with docker, I've tried to add server just below the http clause, but it seems that it's not being read/working. I tried same config on pure nginx container and it works well... I point the service1.local on my host to docker ip, reload kong config and exposed ports on docker...
http {
server {
  listen 80;
  server_name service1.local;

  location / {
  	 root /usr/share/nginx/html/service1;
     index index.html;
  }

  location /nginx_status {
    internal;
    access_log off;
    stub_status;
  }

  location /robots.txt {
    return 200 'User-agent: *\nDisallow: /';
  }
}

This works locally so maybe Docker is not picking up your updated kong.yml file?

@TomSta did you get this going? Can it be closed?

Considering this answered.


refactor: part 2 of distinguish between Unique and UniqueIndex

[X] Do only one thing
[X] Non breaking API changes
[X] Tested

What did this pull request do?

It's part 2 of #6386 which is the part of rollback, see https://github.com/go-gorm/gorm/pull/6386#issuecomment-1820049165.
It will also fix the ci.
But note that it depends on

https://github.com/go-gorm/mysql/pull/123
https://github.com/go-gorm/postgres/pull/195
https://github.com/go-gorm/sqlite/pull/156
https://github.com/go-gorm/sqlserver/pull/106

After the above requests is merged, this pr still needs to update tests/go.mod to the corresponding commit id.
User Case Description

To unblock new PRs, can we just resolve the CI tests issue in a dedicated PR and then decide/proceed on merging this new feature?

I have tested this mr with the above dependency, and it is OK.
Then we need to merge the driver mrs , and update test/go.mod here.
@jinzhu

My God, I tested it as test/docker-composite.yml, and it missed mysql 5.6

My God, I tested it as test/docker-composite.yml, and it missed mysql 5.6

This is the benefit of our CI, to catch oversights in our daily development ;)

What a thrilling day, now we have fixed it 😭


Add: getty demo

add a demo so that we can test the framework when required, especially adding new features.

@AlexStocks @fangyincheng  fix import & merge latest, pls review again, tks~

excellent work.

@wongoo maybe we should delete the examples?


Apple M1 - Could not successfully bind to port 2181

Hi !
I cope with an issue when I try to run the docker image on my Apple M1 mac (see the command and error below).
At first, I tried to look for the port, which I was using because I have a zookeeper installation with brew, but after shutting it down, and even a restart, I still have this error.
And if I run : lsof -nP -iTCP -sTCP:LISTEN | grep 2181, i get nothing.
Now I'm thinking it's because of the new Apple M1 chips, because of the warning I get, but i'm not sure it's a common issue, and I'm not sure the actual error message can be related with ^^
Is there anything someone can think of that I can try ?
Thanks a lot !
$ docker run --rm --net=host lensesio/fast-data-dev

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
runtime: failed to create new OS thread (have 2 already; errno=22)
fatal error: newosproc

runtime stack:
runtime.throw(0x512269, 0x9)
	/usr/lib/go/src/runtime/panic.go:566 +0x95
runtime.newosproc(0xc420030000, 0xc42003ffc0)
	/usr/lib/go/src/runtime/os_linux.go:160 +0x194
runtime.newm(0x5203a0, 0x0)
	/usr/lib/go/src/runtime/proc.go:1572 +0x132
runtime.main.func1()
	/usr/lib/go/src/runtime/proc.go:126 +0x36
runtime.systemstack(0x593600)
	/usr/lib/go/src/runtime/asm_amd64.s:298 +0x79
runtime.mstart()
	/usr/lib/go/src/runtime/proc.go:1079

goroutine 1 [running]:
runtime.systemstack_switch()
	/usr/lib/go/src/runtime/asm_amd64.s:252 fp=0xc42002a768 sp=0xc42002a760
runtime.main()
	/usr/lib/go/src/runtime/proc.go:127 +0x6c fp=0xc42002a7c0 sp=0xc42002a768
runtime.goexit()
	/usr/lib/go/src/runtime/asm_amd64.s:2086 +0x1 fp=0xc42002a7c8 sp=0xc42002a7c0
Could not successfully bind to port 2181. Maybe some other service
in your system is using it? Please free the port and try again.
Exiting.

I have the same issue, also with Apple M1 chip. Did you maybe manage to fix it by yourself?

I have the same issue, also with Apple M1 chip. Did you maybe manage to fix it by yourself?

No, I didn't fix it. I'm still hoping an solution in this thread :)

No, I didn't fix it. I'm still hoping an solution in this thread :)

If you want a quick and dirty fix which works, you can comment this in setup-and-run.sh file (lines 500 to 504):
    elif ! /usr/local/bin/checkport -port "$port"; then
        echo "Could not successfully bind to port $port. Maybe some other service"
        echo "in your system is using it? Please free the port and try again."
        echo "Exiting."
        exit 1

And also remove duphard from Dockerfile. Then you can build this image locally and it works fine.
But still I'm waiting for a fix in this thread :)

As a suggestion to the authors, nginx-proxy had the same problems and here's the PR I can find that enabled multi-platform builds for that image: https://github.com/nginx-proxy/nginx-proxy/pull/1470/files

Leaving some investigation here based on what others have found in porting to M1.
fast-data-dev pulls down an AMD64 image
Here's an example with some of my own personal images to contrast:

I suspect getting the base Dockerfile to pull down the arm64 image should fix things?

Looking at the Dockerfile, looks like there's several things that need to be updated/ported to work for the M1's:

duphard
checkport
coyote
gotty
quickcert
caddy
normcat

Hi your fork wont't build for me. Is it still up to date?

https://github.com/lensesio/fast-data-dev/issues/182#issuecomment-1018131875

Created a fork with the required changes to run on arm64 / Apple M1.
Execute the following sequence of commands:
git clone https://github.com/faberchri/fast-data-dev.git
cd fast-data-dev
docker build -t faberchri/fast-data-dev .
docker run --rm -p 3030:3030 faberchri/fast-data-dev

I am having the same issue, I've tried to do this and it's not working.
As pictured below, you can see the error.
Any idea?

M1 Pro Chip
macOs monterey v.12.3.1
Thanks in advance :)

Created a fork with the required changes to run on arm64 / Apple M1.
Execute the following sequence of commands:
git clone https://github.com/faberchri/fast-data-dev.git
cd fast-data-dev
docker build -t faberchri/fast-data-dev .
docker run --rm -p 3030:3030 faberchri/fast-data-dev

@faberchri , Thanks a lot the changes made in dockerFile worked

Created a fork with the required changes to run on arm64 / Apple M1.
Execute the following sequence of commands:
git clone https://github.com/faberchri/fast-data-dev.git
cd fast-data-dev
docker build -t faberchri/fast-data-dev .
docker run --rm -p 3030:3030 faberchri/fast-data-dev

I built on this to create PR 185 which adds support for arm64 and amd64 at same time + along with how to build a multi-arch image using docker buildx.

This PR from dougdonohoe help me a lot and solved the problem of compiling an image for linux/arm64 architecture.

Created a fork with the required changes to run on arm64 / Apple M1.
Execute the following sequence of commands:
git clone https://github.com/faberchri/fast-data-dev.git
cd fast-data-dev
docker build -t faberchri/fast-data-dev .
docker run --rm -p 3030:3030 faberchri/fast-data-dev

I am having the same issue, I've tried to do this and it's not working.
As pictured below, you can see the error. Any idea?
M1 Pro Chip macOs monterey v.12.3.1 Thanks in advance :)

Hi
I am facing the same issue, have you found a solution for this yet?

Same issue here

Created a fork with the required changes to run on arm64 / Apple M1.
Execute the following sequence of commands:
git clone https://github.com/faberchri/fast-data-dev.git
cd fast-data-dev
docker build -t faberchri/fast-data-dev .
docker run --rm -p 3030:3030 faberchri/fast-data-dev

I am having the same issue, I've tried to do this and it's not working.
As pictured below, you can see the error. Any idea?
M1 Pro Chip macOs monterey v.12.3.1 Thanks in advance :)

Hi I am facing the same issue, have you found a solution for this yet?

same here

I think this is because archive.lenses.io is down.  It seems it has happened before, per this issue:  https://github.com/lensesio/fast-data-dev/issues/186

You can also just docker pull dougdonohoe/fast-data-dev and get the image I built prior to the issues with archive.lenses.io

I filed a ticket with lenses.io over the weekend and they seem to have restored archive.lenses.io.  It's working for me now.


JSPM can not install @uirouter/angularjs

$ jspm install @uirouter/angularjs
     Updating registry cache...

err  Repo jspm:@uirouter/angularjs not found.

warn Installation changes not saved.

I don't use JSPM but I think the correct command is:
 jspm install npm:@uirouter/angularjs


TypeError during cache lookup when loading image texture if source is BytesIO

I'm building a kivy app that works with images gathered from a camera. So, I need to use an in-memory image to provide the user a live view of what the camera sees. The library that supports the camera gives me a PIL.Image, so I use io.BytesIO to make a kivy image by doing this:
def update_canvas(self, **kwargs):
    if self._disp_image is not None:
        temp_image = self._disp_image
        image_bytes = io.BytesIO()
        temp_image.save('pil_image.png','PNG')
        temp_image.save(image_bytes, 'PNG')
        image_bytes.seek(0)
        im = KivyImage(ImageLoaderPIL(image_bytes))
        im.save('kivy_image.png')
        with self.canvas:
            Color(0,1,0,1)
            Rectangle(pos=(0,0),size=self._disp_image.size, texture=im.texture)

When I run the program, the pil_image.png and kivy_image.png files are a match. But, when I try to paint the texture, I get a type error that I've traced to line 233 of kivy/core/image/init.py.
The line where the failure occurs reads: uid = chr(u'%s|%d|%d') % (fname, self._mipmap, count)
That line throws a TypeError: 'str' does not support he buffer interface
gist is here: https://gist.github.com/jerickson-thorlabs/303934432bbf5ee8881cefbbe2402043

I could not reproduce your crash because the example is not runnable.  Here's a cleaner way of getting a kivy texture from a Pillow Image:
import io

from PIL import Image
from kivy.core.image import Image as CoreImage

image = Image.new('RGBA', (100, 100))
image_bytes = io.BytesIO()
image.save(image_bytes, 'png')
image_bytes.seek(0)
im = CoreImage(image_bytes, ext='png', size=(100, 100))
tex = im.texture