Support for runtime context object?

Issue type

Bug Report:
Feature Request:
Question: yes
Not an issue:

Prerequisites

Can you reproduce the issue?: yes
Did you search the repository issues?: yes
Did you check the forums?: yes
Did you perform a web search (google, yahoo, etc)?: yes

Description
Is there any reason that context data can only be set at compile time?
I see many situations where the compiled grammar would need to access a context that changes at runtime.
Compiling the grammar for every use case doesn't seem to be a viable solution.
Unless I'm missing something....
Example code:
I'm using PEG for a decorator in ExpressJS that controls access to endpoints:
@Auth('role(admin) || adgroup(ACME_Developer)')
myEndpointMethod() {
}

The grammar relies on a profile variable that is supposed to contain the current user's profile containing roles and adgroups.
The profile is only available when the endpoint is hit.
I'd expect the compiled grammar to work something like this:
const isAuthorised = myAuthGrammar.parse('role(admin) || adgroup(ACME_Developer)', {
    profile : {
          roles : ['tester'],
          adgroups : ['ACME_Tester']
    }
});

Software

PEG.js:

This might be a good place for a & {predicate} block.  Parse a token with something like $[a-z_]i+, then check it in a list of valid tokens in the predicate.  Here is an intentionally-simplified example (no paren grouping) that parses your inputs and rejects invalid roles/adgroups:
'use strict'

const pegjs = require('pegjs')

const src = `
authorized
  = perm:perm rest:(_ o:op _ p:perm { return [o, p]})* { rest.unshift(perm); return rest }

perm
  = role
  / adgroup

op
  = $"||"
  / $"&&"

role = "role"i _ "(" _ role:rolename _ ")" { return { role } }
adgroup = "adgroup"i _ "(" _ adgroup:adgroupname _ ")" { return { adgroup } }

rolename = name:$[a-z_]i+ & { return options.roles.includes(name) } {
  return name
}
adgroupname = name:$[a-z_]i+ & { return options.adgroups.includes(name) } {
  return name
}

_ = $[ \t]*
`
const parser = pegjs.generate(src)

for (const a of process.argv.slice(2)) {
  console.log(parser.parse(a, {
    roles: ['admin'],
    adgroups: ['ACME_Developer']
  }))
}

Thanks @hildjj.
Are you saying that the options object is available in the grammar and it contains whatever I pass in as a second parameter of parser.parse()?
That's not clear from the docs. Is it a "hack" or is it going to be working in future versions of PEG?
I ended up creating a grammar that outputs and AST that then is interpreted by my code.
{
   "any": [
      {
         "all": [
            {
               "adgroup": "ACME_Developer"
            },
            {
               "role": "admin"
            }
         ]
      },
      {
         "adgroup": "supergod"
      }
   ]
}

Yes, the docs are a little unclear about this, but it's supported behavior. I'll create a bug on peggyjs/peggy to improve the docs.


Expose feature flags to LSP client

The reason behind the rust-analyzer feature flags is to separate the LSP configuration (which may be specific to a client) from the rust-analyzer settings. This is reasonable, but the user experience could be improved, since the client has no knowledge about the available flags.
We should probably expose LSP settings for the feature flags, and do the translation inside the extension. The package.json entries could be generated automatically from the list in crates/ra_ide_api/src/feature_flags.rs.

Some things to look at:

here's how we do a similar thing for assists: https://github.com/rust-analyzer/rust-analyzer/blob/d222608a45d53ca7a1bbc9f0126a092fda48503c/xtask/src/codegen/gen_assists_docs.rs

I think I've seen some sort of include-like thing for package.json. We should investigate this, to make sure we cleanly separate hand-written part of package.json from a generated one.

Now that the feature flags are to be exposed to the LSP client, does this still hold?

Note that we purposefully use run-time checked strings, and not something checked at compile time, to keep things simple and flexible.

I'm also wondering about whether the FeatureFlags type still makes sense in this scenario or if we should just add the flags as fields of some other type (ServerConfig maybe?)

@martskins without looking too closely that makes sense to me. We really need to implement the LSP configuration requests.


No way to go back, if you lose the mnemonic but have the seed?

It gives random mnemonic code -> seed functionality,
but no way to go back, if you lose the mnemonic but have the seed?
We need seed -> mnemonic code functionality on the page, or is it there an I'm not seeing it?

Any particular reason for closing this?
I think it's a good feature and could be implemented similarly to brainwallet.org, which can generate an address using several different sources.

@iancoleman I read into this, and thought it was impossible.

Yeah sorry I confused the hex encoding of mnemonics with the BIP32 seed that comes from it. You're right that BIP32 seed cannot be reversed into a BIP39 seed.


feat(api): Add top-level API for getting scopes

Adding get_current_scope(), get_isolation_scope() and get_global_scope() to the top-level API to make them easier to use. It'll also simplify our migration guide(s).
It's also part of the RFC and JS has it.

General Notes
Thank you for contributing to sentry-python!
Please add tests to validate your changes, and lint your code using tox -e linters.
Running the test suite on your PR might require maintainer approval. Some tests (AWS Lambda) additionally require a maintainer to add a special label to run and will fail if the label is not present.
For maintainers
Sensitive test suites require maintainer review to ensure that tests do not compromise our secrets. This review must be repeated after any code revisions.
Before running sensitive test suites, please carefully check the PR. Then, apply the Trigger: tests using secrets label. The label will be removed after any code changes to enforce our policy requiring maintainers to review all code revisions before running sensitive tests.

Shelving this for now to keep the top level API minimal. This is something only advanced users will need to use. We can reevaluate at a later point if this should be added to the top-level API.


APIView - Get status REST API to take reviewId as optional parameter

GetStatus API in APIView returns status of automatic API review only and this doesn't work if caller is trying to get status of a review created from PR.  We need to change this API to add an optional review ID param which will return status of review with given review ID.
REST API entry point for GetStatus. https://github.com/Azure/azure-sdk-tools/blob/main/src/dotnet/APIView/APIViewWeb/Controllers/AutoReviewController.cs#L52

FYI @chidozieononiwu  once this change is deployed into APIView, we need to communicate it to Wei Dong so he can start consuming it in the SDK automation flow

@praveenkuttappan could you please send me the details of the rest api? I have tried it by rest api https://apiview.dev:443/AutoReview/GetReviewStatus?reviewId=922523946df54b758ce808d3afca8353, but get 401 Unauthorized. How can I pass the authorization? thanks


Forward Alamofire failures

This includes timeouts, which by default seem to be after 60 seconds.
Since I'm working with larger models on an older system, I expect requests that can take up to 25 minutes to complete, so this makes the UI unworkable (timeout failure without any indication, just isFinished).

Hi, @malicious! Thanks for the PR! 🫡


Link Updates & Remove MediaElement sample

Description

Added, removed, updated a bunch of links to align with the docs. Also removed the MediaElement sample.
Motivation and Context

Aligns the Gallery with the docs.
How Has This Been Tested?

Manual testing
Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Just noticed that ContentDialog's Guidelines link goes to https://docs.microsoft.com/windows/uwp/design/controls-and-patterns/dialogs-and-flyouts/index. Should we link to https://docs.microsoft.com/windows/uwp/design/controls-and-patterns/dialogs-and-flyouts/dialogs instead, seeing as that's the Gallery page the user came from?

Just noticed that ContentDialog's Guidelines link goes to https://docs.microsoft.com/windows/uwp/design/controls-and-patterns/dialogs-and-flyouts/index. Should we link to https://docs.microsoft.com/windows/uwp/design/controls-and-patterns/dialogs-and-flyouts/dialogs instead, seeing as that's the Gallery page the user came from?

Yes, I agree @YuliKl

Just noticed that ContentDialog's Guidelines link goes to https://docs.microsoft.com/windows/uwp/design/controls-and-patterns/dialogs-and-flyouts/index. Should we link to https://docs.microsoft.com/windows/uwp/design/controls-and-patterns/dialogs-and-flyouts/dialogs instead, seeing as that's the Gallery page the user came from?

Good catch, updated.


Direct link to download Azul Zulu is broken

Under "Download the 64-bit Azul Zulu JDK 8" the first link "zulu-8-azure-jdk_<IP_ADDRESS>-8.0.242-..." seems to be broken. Nothing happens when I click it. I had to right click and "open in another tab" and then it downloaded the file. This applies to the same links under the three sections Windows, Mac, and Linux

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

ID: 733d4a97-401b-afe5-cf02-325e5e7286ef
Version Independent ID: f31fe3ee-ddba-5da3-e158-0da3c8af8cc7
Content: Install the Azul Zulu JDK for Azure and Azure Stack
Content Source: articles/java/fundamentals/java-jdk-install.md
Service: azure-java
GitHub Login: @bmitchell287
Microsoft Alias: brendm

@KarlErickson - Karl, would you please take a look at this issue? Thanks.

@ninarn thanks for letting us know about this issue. It appears to be a browser security issue. The link works directly in Edge, but in Chrome it doesn't. We will investigate and update the doc to make this clear.


Supporting the Turkmen language for Cupertino/Material widgets

Creating this issue to track interest for adding Turkmen as a supported language for Material/Cupertino widgets.
Related to an attempt to add Cupertino Turkmen translations and an attempt to add Material Turkmen translations.
cc/ @kea2288

Do you have any news about this issue?  If possible, I could solve it myself, by creating new language, but I hope that this issue will be solved in new update of flutter and will be possible to use it in from the box)) In addition I found, that google translate now have support for Turkmen language))) How much time should we wait for update? Thanks, for attention)

Hi! It will likely not be supported until Android supports it, and I'm not sure if that'll change anytime soon.

su 6.12.2020 klo 0.22 Mickey A Mouse<EMAIL_ADDRESS>kirjoitti:

Do you have any news about this issue? If possible, I could solve it
myself, by creating new language, but I hope that this issue will be solved
in new update of flutter and will be possible to use it in from the box))
In addition I found, that google translate now have support for Turkmen
language))) How much time should we wait for update? Thanks, for attention)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/46710#issuecomment-739424039,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ4UBVJAJP2ZGMSK4E5OYHLSTKXDJANCNFSM4JZDALZA
.

Hi! It will likely not be supported until Android supports it, and I'm not sure if that'll change anytime soon.

Bad news(( Anyway, thanks a lot for reponse!

For those who are interested, there is a package in pub.dev: https://pub.dev/packages/turkmen_localization_support


vcpkg branch is 42 commits behind the master

vcpkg branch was created so that VS 2017 users can easily build packages for themselves, but it has some bugs like seeking video closes e.t.c, I think those bugs are fixed in latest master branch. but vcpkg branch is 42 commits behind , so please update it to latest branch and keep it updating with the master in future, or just enable vs 2017 building on the master branch

Updated for VS2017.

can you please guide me how can I now build for vs 2017? should I use the same method you already described in issue with vs 2017? or should I build with master branch? or should I build with following branch ?
https://github.com/Microsoft/FFmpegInterop/tree/gillesk/vcpkg


Convert framework to use TypeScript 2.0 style typings

As TSD is deprecated (https://github.com/Definitelytyped/tsd), will future SPFx be moved over to Typings (https://github.com/typings/typings) for TypeScript definitions.

This is in our todo list already along with moving to TypeScript 2.0.

@wictorwilen @chakkaradeep Typings is basically deprecated too.  @types is the recommended path forward.  I don't believe you have to use TS 2.0.  vscode and sublime already know how to act right.  Not sure about atom though.  The @types packages may not be ready for primetime yet, but it might be worth investigating.  One less moving part.  👍
Reference: The Future of Declaration Files
Notes and Acknowledgements
For those wondering, DefinitelyTyped will still be the place to author new declaration files. We’ll soon be providing a greatly expanded set of documentation aimed at .d.ts authors in the near future. Tools like Typings and tsd will continue to work, and we’ll be working alongside those communities to ensure a smooth transition.

@mike-morrison - awesome info. As long as the dependency is taken on something that is not in a beta state.

FYI we are starting work now to upgrade our Developer Preview to use TypeScript 2.0 Beta.  2.0 has some important features that we would certainly want to incorporate before we freeze our API signatures (e.g. read-only properties, private constructors, strict null checks, etc).  If we do encounter any incompatibilities, it will be easier for the compiler team to fix them before the 2.0 release rather than after.
The aforementioned typings issue is very important to me.  My team works on around 40 TypeScript projects that export/import each others typings, and the old model seems to require (1) an extra build step to strip the typings from a library's exports, and then (2) for each consuming project to have the superset of all typings exposed by its dependencies, even if it doesn't use them directly.  This is not very scalable.  I believe the @types feature that Mike linked above should be a huge improvement.  AFAIK it does require the TypeScript 2.0 compiler, though.

VSO 239959

Update: David has completed the TypeScript 2.0 upgrade for the underlying gulp-core-build system, and @lahuey is now working on converting sp-build-web.

This has been converted.


feature: upgrade Fabric version to v2.5 LTS

Changes are needed in the Go version to keep compatibility with Fabric 2.5 (Go v1.20) and also changes in the base image from Alpine to Ubuntu as Fabric did in the v2.5
https://github.com/hyperledger/fabric/releases/tag/v2.5.4
Dependant to the CLI changes here: #https://github.com/hyperledger/firefly-cli/issues/268

Hi @torrespro. I don't think any changes are required in the FireFly Core codebase itself to be compatible with Fabric 2.5 specifically. Is there something that you have discovered in FireFly Core that is not compatible?

@nguyer It seems to me that the ff deploy fabric dev asset_transfer.zip firefly asset_transfer 1.0 fails when running the fabric tutorial (https://hyperledger.github.io/firefly/tutorials/custom_contracts/fabric.html).
installing chaincode
Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: docker image build failed: docker build failed: Error returned from build: 2 "go: downloading github.com/hyperledger/fabric-contract-api-go v1.2.1


Some changes

Ok done.
Notable changes:
Hashlib was removed as hashing the messages isn't necessary.
By default messages will not be filtered in studio. If you want to debug set IS_DEBUG to true.

Looks good. I’ll accept it when I get back on my computer again.

Also, we don’t need the HashLib script anymore, right?

Yeah. I removed it in the pull request.

Will the pull be merged in the future?

Hey sorry for the delay.
The project is active again now.
I'll merge this and keep working.
Thanks for all your help!


added minemalia and fixed versions list and added arcade to types

The "Arcade" gamemode needs to be added to server.schema.json


[Event Hubs] Convert tests to use identity auth

Summary
The focus of these changes is to convert the Event Hubs live tests to use identity-based authorization by default. Connection strings will continue to have test coverage and appear in "Hello World" samples and in legacy samples for the migration guide.

API change check
API changes are not detected in this pull request.

/azp run net - eventhub - tests

/azp run net - eventhub - tests

/azp run net - eventhub - tests

Local live test runs are stable.  Seeing a number of timeouts in the pipelines, but I don't believe that they're related to the changes - at least not in a way that we can influence.  It is entirely possible that the service auth checks have slowed things down, since we isolate each test in an ephemeral Event Hub, so even though our credential is cashed, we're creating a high number of new connections in parallel.

/azp run net - eventhub - tests

/azp run net - eventhub - tests

/azp run net - eventhub - tests


with-astro example PostCSS exception at build

Building the example on code sandbox (and locally), I receive:
(node:57) UnhandledPromiseRejectionWarning: Error: Loading PostCSS Plugin failed: The argument 'filename' must be a file URL object, file URL string, or absolute path string. Received undefined

(@undefined)
    at load (/sandbox/node_modules/postcss-load-config/src/plugins.js:28:11)
    at /sandbox/node_modules/postcss-load-config/src/plugins.js:53:16
    at Array.map (<anonymous>)
    at plugins (/sandbox/node_modules/postcss-load-config/src/plugins.js:52:8)
    at AsyncFunction.transformAsync (/sandbox/node_modules/@snowpack/plugin-postcss/worker.js:20:17)
    at MessagePort.<anonymous> (/sandbox/node_modules/workerpool/src/worker.js:125:27)
    at MessagePort.[nodejs.internal.kHybridDispatch] (internal/event_target.js:399:24)
    at MessagePort.exports.emitMessage (internal/per_context/messageport.js:18:26)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:57) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:57) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Ooops, sorry, dupe of #248


What does this send to Supabase?

Hi,
what does this send to Supabase?
https://github.com/yashs662/rust_kanban/blob/main/src/constants.rs#L47-L48

The JSON board data is stored in supabase to allow for syncing between devices along with a user id that is generated once you sign up. currently, this is NOT ENCRYPTED!!! so I (the admin) will be able to see your data so please do not put anything sensitive up there. I am working on end-to-end encryption for this data and it will be coming soon. so only you will be able to decode your own data and I would not be able to see anything.

There is RLS in place. so rest assured once encryption is in place your data will be safe and only you will be able to access it


Group by support array and json const expression

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

run starrocks_fe_unittest

run starrocks_fe_unittest


Angular 1.5.8 - flickering related to ng-show/hide

I've updated my app written in Angular 1.4.1 to Angular 1.5.8 and in some places some weird things started to happen.
Mostly it is about flickering of directives with ng-show / ng-hide used on them. I read here #13974 about similiar issue but I can't fix it with any solution posted there.
You can see the demo here - it's about that red indicators below each input:

More info - in these inputs I'm using typeahead directive from AngularUI Bootstrap. Typeahead popup template is being fetched from external file (not inlined).

Looks similar to https://github.com/angular/angular.js/issues/14015 for which I wrote a pach, but never opened a PR :/

Unfortunately I tried to use patch from this issue you've attached and no difference :/
And all of this looks similar to @garycuthbert comment:

another issue we were seeing with our directives, we use a lot of nested directives that use templateUrl and, with the latest angular release, we started to see some fairly ugly transient rendering on initial page loads & view transitions.

Same here :/

I wonder if this is also related to https://github.com/angular/angular.js/issues/15426#issuecomment-263688327. @psmyrdek, does it happen on a specific browser or not? Could you create a live reporduction (e.g. using CodePen, Plnkr etc)?

It has been tested on Chrome, Safari and Firefox - the same problems on every mentioned browser.
@gkalpak your reply from #15426 looks promising (when speaking about solving this issue). I do have some places with ng-show initialized with falsy values (don't ask me why) and before migration to 1.5.8 it was working ok (at least from the user's perspective). Now there's a blink when ng-show="falsy value" turns into ng-hide.

@psmyrdek, your demo shows something different: The flickering is caused by the element being shown before angular takes over and hides it. Issues such as this can be solved with ngClock (and the appropriate styles - if necessary).
Can you try the following directive and see if the flickering goes away in your route changes:
.directive('ngShow', function() {
  return function(scope, elem, attrs) {
    var doShow = scope.$eval(attrs.ngShow);
    elem[doShow ? 'removClass' : 'addClass']('ng-hide');
  };
})

@psmyrdek, your demo shows something different: The flickering is caused by the element being shown before angular takes over and hides it

My question is why places like that worked well in 1.4.1 but now I see flickering.
Of course I agree that places with ng-show="falsy value" are vulnerable to this kind of issues, and I agree that there should be used ng-cloak with "css styles fallback" to prevent these problems, but as I said - in my case it wasn't possible to reproduce this issues in 1.4.1. Is newer Angular slower a bit in terms of initialization, or what?
This is just one of two - the second problem is still related to places with heavier route changes. My friend @jerry23 is also involved in this project and he say something more about it..

@psmyrdek I can reproduce the initial flickering in your codepen even in 1.4.1 in Chrome.

@psmyrdek, this has nothing to do with being heavier. A bad network for example can have a dramatic impact on how long it takes for the script to load. This can definitely be an issue with older versions. But just to be clear, flickering on elements that are included in your index.html (as in your demo) are totally different than flickering on elements that are included inside templates (such as those related to your routes).
So, it is this second category (flickering inside templates) that we need to investigate and if necessary address. Can you try my directive and report back if route flickering keeps appearing and if it has any unwanted side effects (e.g. in terms of initial animations etc)?
It would also be tremendously useful, if you could put together a minimal reproductionof the flickering (e.g. using CodePen, Plnkr etc).

I tried to use this directive but in some cases, it doesn't work correctly.
Now in some places, I'm seeing elements which should be hidden e.g dropdowns list,  content messages, error messages in forms.
Adding ngCloak in all places where the problem exists will be painful and it can be impossible in some cases (external directive).

I tried to use this directive but in some cases, it doesn't work correctly.

Any pattern regarding the "some cases" that it does or doesn't work? We can't really do much without a reproduction or more insight on the exact usecase that is affected by the issue 😞
--

Now in some places, I'm seeing elements which should be hidden e.g dropdowns list, content messages, error messages in forms.

Now, that is weird. If you could share a repro of that, it would be very helpful too. But I understand it is usually difficult to reproduce a corner case in a minimal demo.
--

Adding ngCloak in all places where the problem exists will be painful and it can be impossible in some cases (external directive).

Once again, I only suggest ngClock for elements that appear in the original (static) HTML in your index.html.

Unfortunately, it's so far impossible to reproduce this issue in apps of that scale:
http://plnkr.co/edit/DZdAYxk836dDtoGRQgI7?p=preview
That's kind of 1:1 reproduction of situation from GIF from 1st post. We're using typeahead, which contains typeahead-popup directive inside. Template of this directive is being fetched from external file. It also contains that problematic warning element, with ng-show set to falsy value at the beginning. And that's the place where flickering/blinking occurs.
But on plnkr works good so far...

Maybe there's some css / styles that's causing problems? For example, a css transition on an element with show / hide could cause issues.

As we've just noticed, entirely removed ngAnimate restored our app back to normal.
Tries with Angular 1.5.8 + angular-animate 1.4.1 failed, tries with angular 1.5.9 with latest animate failed, the same with 1.6.0-rc2.
Of course that's not end for us, we have to handle missing angular-animate now.

Unfortunately, it is really hard to tell without a repro. I am also still surprized that the directive abov does not work (but it might depend on the implementation of the involved directives). Can you check what happens if you add the ng-hide class (in the HTML) to the problematic elements?
(BTW, is this app publicly available by any chance?)

Since we haven't heard back from the OP and most importantly we don't have a reproduction, I am going to close this for now. Similar flickering problems are already tracked in other open issues anyway.
(Happy to reopen as soon as there is some reproduction or verification that this is a different/new issue.)

Working for me.
.directive('ngShow', function() {
return function(scope, elem, attrs) {
var doShow = scope.$eval(attrs.ngShow);
elemdoShow ? 'removeClass' : 'addClass';
};
})


update_with_buffer() can cause buffer overflow's

Filing this as discussed. Issue is that update_with_buffer() can cause a overflow and start reading into random heap memory.
This was first discovered on Windows. Will test Linux and update the issue. If it also happens on Linux either it's happening at the OS API level or not.
If possible add checking to update_with_buffer() to prevent reading data outside of the set valid range.

Thanks! Yeah this makes sense to check. I will try to do this during the weekend it also relates a bit to #38 to make sure it doesn't read outside and such.

So I'm thinking about the design for this. Should update_with_buffer return aResult<> that the user can check or should it return a bool if it failed to update? That is less intrusive or should it just println! that it failed. I'm not sure what the best way is here.
Any thoughts?

I think Result<> is the "most Rusty" way to do it if following the guidelines from the book.

Agreed. It's a breaking change for anyone using the library but as it's not 1.x+ yet I guess that can be expected.

It's not exactly breaking per se I guess (but it will generate a warning)

I think it's worth the change, just bump it to 0.10 :)

Yeah will do! Thanks.

The change will be now that applications that uses unwrap on the result from the update_with_buffer call can get this.
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: UpdateFailed("Update failed because input buffer is too small. Required size for 1280 x 724 window (2x scale) is 926720 bytes but the size of the input buffer has the size 921600 bytes")', src/libcore/result.rs:860

Hopefully that error should be good enough


Allow run to be shut down and restarted w/ knowledge of positions, e.g. "save/restore"

requires https://github.com/AsyncAlgoTrading/aat/issues/102

simple CLI in #106, closing until I have a better idea of how to implement


Allow chocolatey package for installation on windows

As the Chocolatey package manager for windows is gaining popularity I wonder if you would accept the creation of an Archi Chocolatey package.
I have created it locally and it works perfectly fine. The chocolatey package will simply call the download link and execute the setup with /VERYSILENT option.
When the package is published on chocolatey.org you can install Archi on windows by calling:
choco install Archi

This outputs:
Chocolatey (v<IP_ADDRESS>) is installing 'Archi' and dependencies. By installing you accept the license for 'Archi' and each dependency you are installing.
Archi v3.1.1
Downloading archi 32 bit  from 'http://archimatetool.com/downloads/latest/Archi-win32-Setup-3.1.1.exe'
Installing archi...
archi has been installed.
archi has finished successfully! The chocolatey gods have answered your request!

Finished installing 'Archi' and dependencies - if errors not shown in console, n
one detected. Check log for errors if unsure.
I put the code to create this in a gist https://gist.github.com/FilipDeVos/24c6179313639ea96932
I am happy to maintain this chocolatey package, but I don't want to publish anything without your permission.

Hi, to be honest I hadn't heard of Chocolatey until now. It seems there are quite a few big apps available already. So, OK, why not. :-)
If you can maintain it, even better!
Regards,
Phil

I submitted the package, it is under review for now.
https://chocolatey.org/packages/Archi/3.1.1

Package is approved and published. See https://chocolatey.org/packages/Archi

Well done! :-)

Is there a way that we can keep "old" versions of the setup available on the current url? Otherwise I need to "cloak" older versions of the package.
Currently I use: http://archimatetool.com/downloads/latest/Archi-win32-Setup-3.1.1.exe
Placing new releases next to the old ones would keep things clean.

Not really. I always use the http://archimatetool.com/downloads/latest/ prefix for URLs.

No worries, I'll manage.

Updated package for the 3.2.1 release. Currently awaiting moderation.
See: https://chocolatey.org/packages/Archi/3.2.1

Updated package for the 3.3.1 release. Currently awaiting moderation.
See: https://chocolatey.org/packages/Archi/3.2.1

Archi 3.3.1 is now approved: https://chocolatey.org/packages/Archi/

Archi 3.3.2 is now approved https://chocolatey.org/packages/Archi

Updated package for the 4.0.0-pr1 release. Currently awaiting moderation.
See: https://chocolatey.org/packages/Archi/4.0.0-pr1

Archi 4.0.2 is now approved https://chocolatey.org/packages/Archi/4.0.2


In item edition, children edition: fix: non visible children get removed at save

Overview
For the moment, we get the list of children, allow the user to update it and then save the whole list of children. The problem is that we might have some children which are not visible by the current user, and as they are not returned to UI, on save they are being removed from the child list at save.
Acceptance criteria

[ ] Use the new "show_invisible_items" parameter on the "itemChildrenView" service to receive to include the items which are not visible by the current user. That might require to create a different function in the service which returns a different type, so that most attributes do not become optional for other usage of this service.
[ ] If the item is not visible, just display something like (in italic or grey or ?) "Non-visible item (<id>)" (without link) to allow the re-ordering and removal of the item if needed.
[ ] make sure the other usages of the service are not impacted (the list of children for chapters/skills should not display invisible items)
[ ] test it properly, if you need some data to be created to test, let me know

blocked by bug https://github.com/France-ioi/AlgoreaBackend/issues/774

The bug in backend has been fixed.


Improve documentation for HTTP basic authentication

Description
This pull request updates the documentation with examples for configuring the provider to use HTTP basic authentication. I classified this under the "static credentials" section but I'm happy to reorganize things. The example is particularly useful because request signing is enabled by default and will result in mysterious HTTP 403 errors, ie
│ Error: HTTP 403 Forbidden: Permission denied. Please ensure that the correct credentials are being used to access the cluster.

Issues Resolved
#107
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Please take a look at my comment here https://github.com/opensearch-project/terraform-provider-opensearch/pull/117#issuecomment-1789702879.

LGTM based on this comment https://github.com/opensearch-project/terraform-provider-opensearch/pull/117#issuecomment-1791415942, merging this PR, thanks @Sovietaced.


Fix unhandled exception

This PR catches an unhandled exception from http module that causes node to crash if network is not present during a request.

Thanks!


Should pyLODE be able to parse ontologies specified in JSON LD?

I'm having some issue trying to process an internal ontology written in JSON LD.
The error I get is   File "C:\Users\filip\anaconda3\Lib\site-packages\pylode\cli.py", line 72, in <module>     main()   File "C:\Users\filip\anaconda3\Lib\site-packages\pylode\cli.py", line 47, in main     od = OntDoc(args.input)   File "C:\Users\filip\anaconda3\Lib\site-packages\pylode\ontdoc.py", line 111, in __init__     self.ns = get_ns(self.ont)   File "C:\Users\filip\anaconda3\Lib\site-packages\pylode\utils.py", line 97, in get_ns     prefix = ont.compute_qname(default_iri, True)[0]   File "C:\Users\filip\anaconda3\Lib\site-packages\rdflib\graph.py", line 1048, in compute_qname     return self.namespace_manager.compute_qname(uri, generate)   File "C:\Users\filip\anaconda3\Lib\site-packages\rdflib\namespace\__init__.py", line 532, in compute_qname     self.__cache[uri] = (prefix, namespace, name) UnboundLocalError: local variable 'name' referenced before assignment
I got the idea that it should be able to parse ontologies such as this (by adding a necessary label), from https://www.gs1.org/voc/, since it uses rdflib. Did I get something wrong or is something missing from the ontology that is necessary?

It turns out that when specifying the @id for the ontology, using a prefix to reference the IRI from the context doesn't get expanded. The solution for me was to include explicitly the full namespace IRI instead of using just the prefix from the context.


        predict_boxes_tran = tf.transpose(predict_boxes_tran, [1, 2, 3, 4, 0])

https://github.com/leeyoshinari/YOLO_v1/blob/4af24bb2986cf115f4cb668cd96dd2349e5eeaee/yolo/yolo_net.py#L150

this code make predict_box_tran's shape from [batch_size,cell_size,cell_size,boxes_per_cell,4] to shape [cell_size,cell_size,boxes_per_cell,4,batch_size],then calculate iou with label-boxes,but label-boxes shape is [batch_size,cell_size,cell_size,boxes_per_cell,4].
Is this a mistake?

sorry,this is my falut, i print result shape, find my mistake.


Add JSON support

What kind of change does this PR introduce?
If the user has no loader specified for a file that ends on .json, webpack now automatically applies the json-loader.
Did you add tests for your changes?
Yes, tests have been updated
If relevant, did you update the documentation?
Yes, updated docs and examples. This change needs to be added to the migration guide on webpack.js.org
Summary
Motivation see https://github.com/webpack/webpack/issues/3363
Does this PR introduce a breaking change?
No

Looks good to me.


Add SLURM check in ddp_train() and init_ddp_connection()

Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure to update the docs?
[ ] Did you write any new necessary tests?
[x] If you made a notable change (that affects users), did you update the CHANGELOG?

What does this PR do?
Fixes #1345  .
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

changelog need to be rebased on new release #1419


Primary component shouldn't be removed from khash

After assigning primary component it is removed from list. Not sure why this is needed. There was a glitch that the removal tested for equal list length which is not guaranteed for optional items resulting in wrong association.

Done with cleanup. Substantially reduced code


[Feature requests] Add PKEYs out for IB, AN, SSH

If not already present, output of PKEYS on the VM:
cat /sys/class/infiniband/mlx5_0/ports/1/pkeys/*
Is there a direct test to check if Accelerated Networking is enabled vs not? Not sure if this is in the VM metadata. Though indirectly, this is discernible through lspci, ibv_devinfo etc.
Additionally (unrelated to this ask), how can we add info if the VM is publicly accessible (over SSH, public IP, port 22 open)? This may be relevant to know if we can have direct access to VM (with customer consent) or will need to coordinate VM access with customer.

For the pkeys: see #19
For the Accelerated Networking, in a comment on this PR:  #24 @jithinjosepkl brings up potential issues AN will bring, so that will likely be its own Issue soon
For SSH, I don't think it would be too hard to check is sshd is running locally and whatever else is local to the system, but there would be other obstacles like network security rules that would block the connection. I'm also not sure I understand the proper protocol going on between Azure engineers and the customer in that scenario well enough to design the feature without some more direction.

For the pkeys: see #19
For the Accelerated Networking, in a comment on this PR:  #24 @jithinjosepkl brings up potential issues AN will bring, so that will likely be its own Issue soon
For SSH, I don't think it would be too hard to check is sshd is running locally and whatever else is local to the system, but there would be other obstacles like network security rules that would block the connection. I'm also not sure I understand the proper protocol going on between Azure engineers and the customer in that scenario well enough to design the feature without some more direction.

I agree. The 3rd ask is a bit tricky to cover adequately with external factors making it complicated. Perhaps best to leave this out.
On 2nd, I guess we'll take lspci etc. as proxies for AN.
Thanks for #1.

I agree. The 3rd ask is a bit tricky to cover adequately with external factors making it complicated. Perhaps best to leave this out.
On 2nd, I guess we'll take lspci etc. as proxies for AN.
Thanks for #1.


Perform Batch Updates in Swift 4 Crashes When Updated

Goals

Perform Batch Updates API in CollectionView without crashing
Expected Results

Success
Actual Results
Invalid update: invalid number of items in section 0.  The number of items contained in an existing section after the update (8) must be equal to the number of items contained in that section before the update (8), plus or minus the number of items inserted or deleted from that section (1 inserted, 0 deleted) and plus or minus the number of items moved into or out of that section (0 moved in, 0 moved out).
Steps to Reproduce

1.) Create a instance of Realm Results<T> like var item : Results<T>?
2.) Create a addNotification block in viewDidLoad
3.) Call performBatchUpdates(_:) with deletions, insertions & modifications params in viewDidLoad
4.) Call items.count in collectionView like guard let items = items?.count else { return }
return items
Also followed this and several other tickets. Not sure if the merge from last year was modified or is a bug when converting to Swift 4.
Code Sample
// Set up realm
var realm : Realm!

var items : Results<Article>?

var notificationToken: NotificationToken!`

private func setUpRealm() {
    DispatchQueue.main.async {

        // Acknowledge the user and access the realm on the main thread
        self.realm = try! Realm(configuration: exampleConfig(user: SyncUser.current!))

        self.items = self.realm.objects(Article.self).sorted(byKeyPath: "created", ascending: false)

        // Observe notifications and update the UI when the underlying data has been changed
        self.notificationToken = self.items?.addNotificationBlock { [weak self] (changes: RealmCollectionChange) in

            guard (self?.collectionView) != nil else { return }

            switch changes {
            case .initial:
                self?.collectionView.reloadData()
                break

            case .update(_, let deletions, let insertions, let modifications):
                self?.collectionView.performBatchUpdates({
                    self?.collectionView.deleteItems(at: deletions.map({ IndexPath(row: $0, section: 0)}))
                    self?.collectionView.insertItems(at: insertions.map({ IndexPath(row: $0, section: 0)}))
                    self?.collectionView.reloadItems(at: modifications.map({ IndexPath(row: $0, section: 0)}))

                }, completion: nil)
                break

            case .error(let error):
                print(error.localizedDescription)
                break
            }
        }
    }
}

func collectionView(_ collectionView: UICollectionView, numberOfItemsInSection section: Int) -> Int {
    guard let items = items?.count  else { return 0 }
        return items
}

Version of Realm and Tooling

Realm framework version: ?
Realm Swift 2.10.1
Realm Object Server version: ?
RMP Release 1.8.3
Xcode version: ?
Xcode 9
iOS/OSX version: ?
iOS 11
Dependency manager + version: ?
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.3.1/lib/cocoapods.rb

We are trying to reproduce the problem with a code similar to the code snippet that you indicated, but we can not reproduce it yet.
Could you please share a reproducible sample project, or more information such like model  definitions and the actual data when an error occurs?
Thank you for reporting.

Yes. My model definitions are as follows
final class Item: Object {
@objc dynamic var username =  String()
@objc dynamic var title =  String()
@objc dynamic var text =  String()
@objc dynamic var place =  String()
@objc dynamic var favorite = Int()
@objc dynamic var created = Date()
}

NOTE I can send either a sample project or my own project to<EMAIL_ADDRESS>I believe with discretion? Need to finish work here and can have it over by late tonight (EST) if nothing below makes sense:
The actual data is the above error. I have two view controllers, call them First View and Second View, unlike with the Realm Tasks Sample project. One view is for reading and the other for posting.
I am able to successfully present First View at runtime.
Next, I can present Second View via modelPresentationStyle = .overCurrentContext and begin crafting my post. When I go to post via a simple button, First View presents but then freezes and crashes with the above error
Invalid update: invalid number of items in section 0. The number of items contained in an existing section after the update (8) must be equal to the number of items contained in that section before the update (8), plus or minus the number of items inserted or deleted from that section (1 inserted, 0 deleted) and plus or minus the number of items moved into or out of that section (0 moved in, 0 moved out).
The underlying data is added and I can see it update in the Realm Browser, which is really cool. My first thought is I am updating faster than the UI can count. But how is that possible? I tested my theory with a timer object but this was hacky, error prone and it got me no where.
For the record, this works fine with the Mobile Database. My troubles began when I started using the Object Server. Again, if my project is required, I have no issue sending it over.

Hi, @kishikawakatsumi
Having a few issues reproducing a sample project, namely creating the exact conditions on my end for you to get the best look at what I'm struggling with, here. May I provide a link to the repo? I can further share our results and success here for others.

This seems pretty simple. I can do this in Swift 3 with the Realm Database but not with the Object Server (although I'm certain that has nothing to do with it). I have tried adding and subtracting the number of articles in my numberOfItemsInSection e.g. articles -= 1.
This raises the exception Left side of mutating operator isn't mutable: 'articles' is a 'let' constant
Here's what I am trying to accomplish:
Second VC
 //  Write article to the realm
func publishToRealm() {
    DispatchQueue.main.async {
        let article = Article()
        self.realm = try! Realm(configuration: myConfig(user: SyncUser.current!))
        article.username = self.usernameLabel.text!
        article.text = self.editorTextView.text
        article.title = self.editorTitleTextField.text!
        try! self.realm.write {
            self.realm.add(article)
        }
    }
}

First VC
These are my variables
// Set up realm
var realm : Realm!
var articles : Results<Article>?
var notificationToken: NotificationToken!

This is what I call in viewDidLoad e.g. setUpRealm()
 // Open realm using the Daily configuration
private func setUpRealm() {
    DispatchQueue.main.async {
        // Acknowledge the user and access the realm on the main thread
        self.realm = try! Realm(configuration: myConfig(user: SyncUser.current!))
        self.articles = self.realm.objects(Article.self).sorted(byKeyPath: "created", ascending: false)

        // Observe notifications and update the UI when the underlying data has been changed
        self.notificationToken = self.articles?.addNotificationBlock { [weak self] (changes: RealmCollectionChange) in

            guard (self?.collectionView) != nil else { return }

            switch changes {
            case .initial:
                self?.collectionView.reloadData()
                break

            case .update(_, let deletions, let insertions, let modifications):
                self?.collectionView.performBatchUpdates({
                    self?.collectionView.deleteItems(at: deletions.map({ IndexPath(row: $0, section: 0)}))
                    self?.collectionView.insertItems(at: insertions.map({ IndexPath(row: $0, section: 0)}))
                    self?.collectionView.reloadItems(at: modifications.map({ IndexPath(row: $0, section: 0)}))

                }, completion: nil)
                break

            case .error(let error):
                print(error.localizedDescription)
                break
            }
        }
    }
}

This is my data source
/// Data Source Methods
extension DailyViewController: UICollectionViewDataSource {

func numberOfSections(in collectionView: UICollectionView) -> Int {
    return  1
}

func collectionView(_ collectionView: UICollectionView, numberOfItemsInSection section: Int) -> Int {
    guard let articles = articles?.count  else { return 0 }
        return articles
}

func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell {

    let cell = collectionView.dequeueReusableCell(withReuseIdentifier: reuseIdentifier, for: indexPath) as! ArticleCell

    let dateFormatter = DateFormatter()
    dateFormatter.dateStyle = .medium

    if (articles?.count) != nil {
        let article = articles?[indexPath.item]
        cell.usernameLabel.text = article?.username
        cell.articleTitleLabel.text = article?.title
        cell.articleTextView.text = article?.text
    }
}

Apologies for the delay. Thank you, again, for your help.

UPDATE
Not sure if this is best practice with this API (or collection views, for that matter), but after several interactions with the application my solution was to simply remove Dispatch.main.async from the function. Perhaps because once logged into the Realm Object Server there is no need to continue updating the collection view on the main thread.
I think  this is because Realm's RealmCollectionChange API takes care of a lot of what we are used to doing manually with UICollectionView. Best practice is to always update the UI on the main thread but I believe the Collection Change API handles this, viz; "Reactive programming just means reacting to the changes that are happening, and trying to minimize the number of different code paths they have to maintain to notify interested parties that changes have happened."via @jpsim https://academy.realm.io/posts/meetup-jp-simard-mastering-realm-notifications/?
Closing this issue for now unless anyone has anything further to contribute.


Stratify splits by Gleason score, not y_label

Model performance achieves similar standard, as expected, but may be more consistent from
run to run.  Input 25 changed stratify = y will revert the code if this proves not to be the case.


[FlatButton] Are you open to have a labelColor for the FlatButton

With the latest stable version, I see that RaisedButton have a labelColor prop, but FlatButton don't.
Are you open to have this prop added for FlatButton? Open for a PR?

I see that RaisedButton has a labelColor prop, but FlatButton don't

That's still true on the master branch. That's not good. We need to be coherent. We have two options:

Remove the current labelColor from the <RaisedButton /> component and let users use the labelStyle property.
Add a labelColor property to the < FlatButton />.

It's a really an API decision. I'm fine the option 2. as it's also in the muiTheme context.
@callemall/material-ui What do you think?

@oliviertassinari @MoOx : I think adding a labelColor would not make any harm. Since for a Flat Button the only thing that makes it distinguishable in the layout is its label color. I think we can go ahead with adding a property to it.

IMHO, since we have labelStyle, we don't also need labelColor. Less props = less complexity.
However at some point we should probably document what object keys the style props take, so users don't have to go digging through the code.

@MoOx : Does using labelStyle not solve your problem?

Kind of. But I think you should still make things more consistent here.

@MoOx - we're working on it, but it's a big project that has evolved over time so has lots of inconsistencies in both API and code internals.
For the API, we're trying to avoid adding unneeded props, but stripping out props from existing components also has to be done with due consideration for availability of alternatives, and impact on current deployments, so takes time.
Closing this for now, as it sounds like you're sorted.

Light API is a good choice ;)

+1 for standardizing API for buttons.


Please upload the package to PyPI

Most python packages (currently more than 200 thousand) can be easily installed with pip, making it easier to integrate new packages like yours into large existing python development environments.
This however would require uploading your package to PyPI, which I think will be easy with this package, given that it's already bundled into an .egg format.

yes, you are right, we are going to upload our package to pypi. we are still working on this pypi package to polish the python code. just wait for a while.


Add Active Directory for login / credentials

using readlmd / sssd  to enable better workflow in existing environments. Also need to add LDAP for the same reasons.

not supporting

Re open and target support before 2016/12/E

Digging into this a bit more it requires 2 things

nginx ldap auth module
https://github.com/kvspb/nginx-auth-ldap

ssh libpam hooked to ldap
fairly straight forward / standard thing to do. shouldnt cause too much greif.

Biggest question is how generate nginx config file. As theres now user configurable item (ldap URIs) which may/may not be present. Probably easiest to run a script before launching nginx that generates the config file

can update setup_nginx.lua to generate config file before launching

configuration file needs to be
/opt/fmadio/etc/ldap_nginx.conf
example is, can be configured freely based on the org.
ldap_server ldap_server0 {
url "ldap://<IP_ADDRESS>:389/DC=fmadio?uid?sub";
binddn "CN=admin,DC=fmadio";
binddn_passwd "LDAPpassword1234";
group_attribute uniquemember;
group_attribute_is_dn on;
require valid_user;
}
ldap_server ldap_server1 {
url "ldap://<IP_ADDRESS>:389/DC=fmadio?uid?sub";
binddn "CN=admin,DC=fmadio";
binddn_passwd "LDAPpassword1234";
group_attribute uniquemember;
group_attribute_is_dn on;
require valid_user;
}
To enable LDAP requires ssh login to modify
/opt/fmadio/etc/time.lua
set LDAPAuth to "enable"


Document translation preference is not passed while changing

Document translation preference is not being passed in preferences while changing it in Immersive Reader options menu. Which makes impossible saving the value and persisting the document translation after changing the text.
Received preferences are:  {"displayOptionsState":{"textSize":20,"fontFamily":"Sitka","textSpacing":24,"formattingEnabled":true,"theme":"Sepia","themeSetByUser":true,"syllabificationEnabled":false,"nounHighlightingEnabled":false,"nounHighlightingColor":"MiddleMagenta","verbHighlightingEnabled":false,"verbHighlightingColor":"MiddleRed","adjectiveHighlightingEnabled":false,"adjectiveHighlightingColor":"MiddleGreen","adverbHighlightingEnabled":false,"adverbHighlightingColor":"MiddleYellow","pictureDictionaryEnabled":true,"posLabelsEnabled":false},"readAloudState":{"readAloudSpeed":1,"voice":"Female"},"translationState":{"shouldTranslateWords":false,"translationLanguage":"%7B%22text%22%3A%22Armenian%22%2C%22key%22%3A%22Armenian%22%2C%22data%22%3A%7B%22tlc%22%3A%22hy%22%7D%7D"}}
Expected behaviour: get the {shouldTranslateDocument: true} in translationState.

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

ID: 542be97f-9816-ca16-3f2a-4d53b22c878d
Version Independent ID: af9b1128-642a-b941-aad4-c06560e990dd
Content: Immersive Reader SDK Reference - Azure AI services
Content Source: articles/ai-services/immersive-reader/reference.md
Service: applied-ai-services
Sub-service: immersive-reader
GitHub Login: @rwallerms
Microsoft Alias: rwaller

@Merkost
Thanks for your feedback! We will investigate and update as appropriate.

@Merkost
Thank you for bringing this to our attention.
I've delegated this to content author @eric-urban, who will review it and offer their insightful opinions.

@eric-urban
Could you please review add comments on this, update as appropriate.

It have been two weeks with no answer. Any updates? @eric-urban

@rwallerms @nitinme - Sorry I'm not the author or subject matter expert for Immersive Reader. How do you recommend we proceed? Thanks!

#assign: cristobal-buenrostro
Cristobal, can you please take a look?

#assign: rwallerms
#assign: sharad-sharma-msft

#assign: sharad-sharma-msft

Hi @Merkost, this is actually By Design that the Document Translation is not stored as a User settings preference. The Reader will always open in the default document language. Document Translation requires the User to toggle that on each launch.
If the Host app has scenarios where it would like to launch in Translated mode, it can override these User settings and launch into Translated mode by using our TranslationOptions.
Please let us know if you have any questions!

Looks like the issue was resolved.
#please-close


How to use fonttools to create a new OTF/TTF font?

Hello. I hope it is OK to ask such a question here. If not, please point to where I can do that.
I want to do something like:
from fonttools import TTFont
newfont = TTFont()
g1 = newfont.addglyph()
g1.addChar(<unicode-codepoint1>)
g1.addChar(<unicode-codepoint2>)
g1.moveTo(<p1>)
g1.quadTo(<c>,<p2>)
g1.lineTo(<p3>)
g1.closePath()
g1.moveTo(<p4>)
...
g2 = ...
...
newfont.write("myfont.ttf")

And likewise using cubicTo() or such for OTFont.
Is this currently possible using fonttools? If so, kindly provide a simple guide as to how this can be done.
Thanks!

hello!
the short answer is no, I'm afraid.
Or rather, you could... but fontTools is very low level library to work with, if you're not familiar with the structure of OpenType fonts.
You could programmatically build a UFO using tools like defcon, and then pass this object to a compiler like ufo2ft, which internally uses fontTools to build up the various OpenType tables from the source data contained in the UFO.
You can look at ufo2ft code to see how it calls fontTools to build the open type font from scratch.
Or you could just pass the UFO path to a command-line tool like fontmake, which will use ufo2ft to build the OTF or TTF font.

Thank you for your kind reply. That is very clear now. I will ask any further questions on the relevant forums (defcon etc).


Refresh token doesn't get returned in $client->fetchAccessTokenWithRefreshToken($refreshToken)

While running this example
https://developers.google.com/sheets/quickstart/php
I noticed after the AccessToken expires it uses refresh_token to fetch a new token however it returns creds without the refresh_token included. As a result, subsequent attempts to fetch a new accessToken (after the expire) fail because the refresh_token is not saved and thus not able to be passed back to fetchAccessTokenWithRefreshToken again.
Should this be reinserted back into the creds?
/vendor/google/apiclient/src/Google/Client.php   2016-09-27 15:13:43.178769896 -0700
@@ -271,6 +271,7 @@
     $creds = $auth->fetchAuthToken($httpHandler);
     if ($creds && isset($creds['access_token'])) {
       $creds['created'] = time();
+      $creds['refresh_token'] = $refreshToken;
       $this->setAccessToken($creds);
     }

Just ended up here as a result of a search after finding the same thing.

Also seeing the same problem

@LetterboxDelivery is right - the refresh token is only delivered the first time an application is authorized.
We could add the refresh token back to the in-memory access token, but this is not a guaranteed fix, as the access token can be cached at the auth level. I do think it would be an improvement, however.

The important point for me is, I had setup access to the Calendar API back in January, and downloaded this library, and that version of the API, when the access token has expired, renews and passes back both the new token and the (original) refresh token, for saving / caching the file off for use after the next expiration, using:
// Refresh the token if it's expired.
if ($client->isAccessTokenExpired()) {
$client->refreshToken($client->getRefreshToken());
file_put_contents($credentialsPath, $client->getAccessToken());
}
Has this behavior intentionally changed in this version?  The current version calls (by way of example in the quick start):
// Refresh the token if it's expired.
if ($client->isAccessTokenExpired()) {
$client->fetchAccessTokenWithRefreshToken($client->getRefreshToken());
file_put_contents($credentialsPath, json_encode($client->getAccessToken()));
}
Which no longer includes the refresh token.  Meaning, doing nothing different using the same API, under the new scripts, you can only maintain access for 2 hours (original token, followed by refresh token), but when the third attempt occurs, since the refresh token is no longer present, you're DOA.
I certainly understand how to extract and save off the refresh token manually for later use, but one did not have to do this manually using the library a short time ago, so the behavior has changed (intentional?).
Rolanyang's suggestion makes sense from my perspective and resolves the "issue".

Perhaps at some point in the past,  the refresh token was being returned but is no longer now.  I wonder if there is logic on the server side that might have stopped the return of refresh tokens if the oauth permissions were revoked.  If that is the case and, in the future, the server does start returning refresh tokens again, then this might be better:
    if (!isset($creds['refresh_token']) {
        $creds['refresh_token'] = $refreshToken;
    }

In case the behavior was intentionally changed, then the documentation/quickstart needs to be updated accordingly, otherwise everybody will be induced in error...

Be sure to add $client->setAccessType('offline');. I've also came across this 'error'

I have $client->setAccessType('offline'); doesn't make the refresh token to be returned, at least not for me.

I too am having the same issue I think it is definitely a server side issue

I am facing the same problem the problem here is that the call for refreshing token using the refresh token doesn't set the refresh token and sends only the access token.  Complete description written in #1102
Seems that the library is not considering the accessType when refreshing the token.
Thanks,
Sadashiv.

I am also facing the same issue , 'refresh token must be passed in or set as part of setAccessToken'
Not sure what wrong /how to resolve it .
Has anyone found the solution . it was working good for first time , after 6 hrs its giving me the above error

Everyone please take a look at #1121

Besides
$client->setAccessType('offline');
Need to include force prompt to Google return the refresh token:
$client->setApprovalPrompt('force');
Works for me.

The initial oauth sequence must include the line of code below -
$client->setApprovalPrompt('force');
Without this, when accessToken expires, there will be no refreshToken available - the getRefreshToken() function will return null, which in turn causes fetchAccessTokenWithRefreshToken to fail.
I don't know if this setApprovalPrompt setting is a legitimate requirement of what I'm trying to do, or relates to an issue elsewhere within the Google Client PHP API.  I just know it fixes the problem of the various quickstart.php samples published by Google that fail to refresh expired access tokens.

It looks like a member of our great community answered your questions. Thanks Community! Please feel free to reopen if you have any more questions.

As an issue, isn't this still open? getRefreshToken() should, well, get a refresh token, yes?
If the API is behaving as intended (which would require some explanation), then the code on the Google Sample for PHP needs to be amended.

After set
$client->setAccessType('offline');
$client->setApprovalPrompt('force');
Don't forget to delete your previous credential token.

This was it for me. The refresh token was returned the very first time I authorized my account on my app. Subsequent re-authorizations without revoking the existing token first only gave me the access token. So I added a small piece of code to check for refresh tokens on client authorizations. If it is empty, I revoke the current access token and tell the user to re-authorize.

I was also seeing the same problem with offline access.
However it looks like we actually needed to store the original refresh_token given to us at first authorisation to be reused later on. I had assumed a new refresh_token would be generated so kept overwriting the returned access token data stored in the DB.
I am now simply appending the original refresh_token back into the access token array and storing it again.

Besides $client->setAccessType('offline'); Need to include force prompt to Google return the refresh token: $client->setApprovalPrompt('force'); Works for me.

This worked for me too


Let's use our node

Don't triage available or fast nodes, just use our node
Reason: Our node is the most reliable.
If we triage, we would need to

Retry with another node on each failed transaction
Re-triage in this case also

The way we do it right now, it doesn't work well (failed transactions)

Fixed in #132

Closing as a legacy issue.


[NEMO-87] Remove unused BlockStates

JIRA: NEMO-87: Remove unused BlockStates
Major changes:

READY, LOST_BEFORE_COMMIT, LOST, REMOVED => NOT_AVAILABLE
SCHEDULED => IN_PROGRESS
COMMITTED => AVAILABLE

Minor changes to note:

N/A

Tests for the changes:

N/A (no new feature)

Other comments:

N/A

resolves NEMO-87

@seojangho Thanks for the catch. I've fixed the typo.


fix: 🐛 enforce lower and upper file size limit when triggering analysis [ROAD-799][ROAD-814]

also increase retries for upload to 10

We forgot changelog update

Can't merge due to Code environment :(


pyproject.toml remaining support

The common cases for pyproject.toml are supported, but there are some edge cases to support.
Base

Support optional-dependencies https://www.python.org/dev/peps/pep-0631/#optional-dependencies

Poetry

Support expanded syntax https://python-poetry.org/docs/dependency-specification/#expanded-dependency-specification-syntax

optional-dependencies support added in <IP_ADDRESS>


error logging (v6)

Related https://github.com/ExpressionEngine/ExpressionEngine-User-Guide/pull/576
I think we had additional changes in that one.

@intoeetive please see https://github.com/ExpressionEngine/ExpressionEngine-User-Guide/pull/575#issuecomment-1423145230


Failing to provide returnType() statement for a multivariate custom distribution r function throws you into a browser

The title says it all.
Catching this earlier would be very helpful - in registerDistributions?
library(nimble)

dDist <- nimbleFunction(
    run = function(x = double(1), log = integer(0, default = 0)) {
        returnType(double())
        return(0)
    }
)

rDist <- nimbleFunction(
    run = function(n = integer()) {
        ##returnType(double(1))   ## FAILED TO PROVIDE
        return(rep(1,2))
    })

registerDistributions(list(
    dDist = list(
        BUGSdist = 'dDist()',
        types = c('value = double(1)'))))

code <- nimbleCode({ x[1,1:2] ~ dDist()})

Rmodel <- nimbleModel(code)

Cmodel <- compileNimble(Rmodel)  ## drops you in a browser in size processing

I've added a check in checkDistributionFunctions that the returnType for the r function matches that for d.


Error launching Anypoint Code Builder Web IDE

Describe the bug
Error launching Anypoint Code Builder Web IDE
To Reproduce
Steps to reproduce the behavior:

Go to Anypoint Code Builder
Click on Launch Web IDE
See error: Something went wrong while preparing your web IDE.  Something went wrong, you may want to try to launch it later.  You can try to re-launch it later. Or report an issue with instance URL

Same error on URL:  https://eu1.anypoint.mulesoft.com/codebuilder/


feat(helm): Add Files.AsSecrets, Files.AsConfig, path functions

This PR adds a number of useful utilities for working with files and file paths.

Several of the StdLib path functions have been exposed to templates for working with file paths
The Files type learned to serialize itself to valid YAML maps for both config maps and secrets via Files.AsConfig() and Files.AsSecrets()

A few possible edits I was unsure on:

AsConfig() and AsSecrets() could instead return maps intended to be passed to toYaml or toJson(does that exist?) to support either use case. I chose YAML because I think that's probably the most commonly used language, but I know there are people out there using JSON.
This could be more composable. For example, {{ Files.Glob "secrets/*" | secretMap | flattenDir | toYaml }}.
I'm not attached to the method names at all. There may be more semantic/evocative names for what these methods do. I just didn't want to overdo it with ToKubeConfigMapYAMLKeys() or some such nonsense. :smile:

This change is

Other than discussing the possibility of moving the path functions to Sprig, I am on board with doing this.

I don't suppose I can coerce you into also doing this one too, could I? ;-) https://github.com/kubernetes/helm/issues/1548

Manually tested


[KOGITO-1946] Set test default config to 0.10.0-rc2

https://issues.redhat.com/browse/KOGITO-1946
Many thanks for submiting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster

will delete once 0.10.0 is released

Tests ok with rc2 images


[E2E] Automate Misc Test case: Test to update a vsan policy which doesn't exist

Details in issue #1010
Test - 2: Test to update a vsan policy which doesn't exist

Try updating a vsan policy which doesn't exist

Setting to spiderman, may not be a critical test case to verify hence to spiderman.


Add snapshot test for storage format

Run pageserver with small checkpoint distance, generate and store some tenant data inside the github repo (< 100KB zipped). Then write test that loads the data and answers some queries. The goal is to notice backwards-incompatible changes.
If there's a need for larger datasets we can think about external storage. But for now 100KB is not that much. layered_repository.rs is about 100KB, and so is Cargo.lock.

See also issue #1607, cc @MMeent

closing as a dup of https://github.com/neondatabase/neon/issues/1607 , added @bojanserafimov comments


Add return codes to Ip6::HandleDatagram.

This change provides feedback to the client when something fails in Ip6::HandleDatagram and equivalently otSendIp6Datagram.  When operating in NCP mode, the error code will also be passed back via spinel.

LGTM :+1:

LGTM 👍

LGTM 👍


Panzoom hides mousedown event of sub-items on latest Chrome

I used this awesome plugin with jquery.draggable to pan/zoom diagram with draggable nodes,
but after latest Chrome update nodes become undraggable.
Little investigation showed that Chrome changed something with it's pointerdown event,
so now panzoom plugin respond for pointerdown event of child node before it's mousedown event fired.
Panzoom suppress pointerdown event and for some reason there is no mousedown event after that, so dragging does not start.
jquery.panzoom.js v3.2.2
jquery 3.1.0 or v1.11.3
jqueryui  1.12.0 or 1.10.3
Chrome 55.0.2883.75 (64-bit) Ubuntu 16.04
Here is a demo
http://codepen.io/yurigor/pen/yVjeGB
I added option 'ignoreChildrensEvents' to fix this issue
I am not sure should I make pull request with this changes.

I am having the same issue, chrome v55. I have draggable window, and i want to get mousedown events for children What did you do to fix this? do you have a branch with the change, I'm stuck for now.

found your branch and it fixes my problem very very nicely. Thanks YuriGor this is wonderful

Happy to help!
Anybody, who also need it, here is a direct link:
https://github.com/YuriGor/jquery.panzoom/tree/ignoreChildrensEvents/dist
@timmywil, if you wish to merge my changes, help me with grunt please.
I start livereload by
grunt watch:dev
but it doesn't work.
At http://localhost:35711/ I have
{"tinylr":"Welcome","version":"0.2.1"}
and at
http://localhost:35711/test/index.html
or
http://localhost:35711/demo/index.html
I have
{"error":"not_found","reason":"no such route"}

Thanks a lot. this fix was not enough for me but i added some myself to fix it for my case. (i has multiple nested children some of them should be ignored and others should not)

@timmywil Is it possible to release a new version with this option?

what i do is to comment out the preventDefault at line 969. preventDefault will block the event from reaching its children.

@akhnaz,
From my understanding, preventDefault will prevent the default action associated with an element (a child or the panzoom element itself), and stopPropagation will stop events from bubbling up to a parent element.
There is a simple and elegant solution in the FAQ:

How do I make links work if they're within a Panzoom element? example

Event propagation is stopped for mousedown and touchstart events in order to allow for Panzoom elements within Panzoom elements. To fix the links, bind an event handler that prevents the event from reaching the Panzoom handler:

$('.panzoom a').on('mousedown touchstart', function( e ) {
  e.stopImmediatePropagation();
});

This requires no changes to the library itself.

Hi @glen-84
Yes, preventDefault will prevent the default action.  But,  it will also prevent mouseDown from the child when pointerDown is being dispatched and listened.
In chrome 55 pointerDown is now dispatched and microsoft edge is already implement pointerDown from beginning.
In my case, panzoom is listened to pointerDown, and the children is listen to mouseDown.

Here is my jsbin for it:
https://jsbin.com/yozotuxina/edit?js

Hi,
I improved your feature a little. I override your option to a possible array of class. The goal is to only ignore events if childs have one of the listed class. Of course, just setting the value to true work as you implemented it.
I don't have really time to fork properly and make a pull request. Please include that small improvement and request for a pull into the main repository.
Here is the code updated from your fork lines 959:
`if (!options.disablePan || !options.disableZoom) {
events[ str_start ] = function(e) {
if(options.ignoreChildrensEvents) {
if($.isArray(options.ignoreChildrensEvents)) {
if(options.ignoreChildrensEvents.find(function(c){return $(e.target).hasClass(c);})) {
return;
}
}
else if(e.target !== this){
return;
}
}
	var touches;
            /* rest of code */

`
The the ignoreChildrensEvents option can be defined as true, false or ['child-class1', 'child-class2'].
Regards


Not working with latest React Version

Error Verbose Output
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/react-fa-icon-picker
npm ERR!   react-fa-icon-picker@"*" from the root project

My package.json
{
  "name": "Secret-Project",
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "@apollo/client": "^3.3.21",
    "@testing-library/jest-dom": "^5.14.1",
    "@testing-library/react": "^11.2.7",
    "@testing-library/user-event": "^12.8.3",
    "apollo-cache-inmemory": "^1.6.6",
    "apollo-link-http": "^1.5.17",
    "bootstrap-icons": "^1.5.0",
    "classnames": "^2.3.1",
    "country-state-city": "^3.0.1",
    "debounce-promise": "^3.1.2",
    "graphql": "^15.5.1",
    "jquery": "^3.6.0",
    "prop-types": "^15.7.2",
    "react": "^17.0.2",
    "react-bootstrap": "^1.6.1",
    "react-dom": "^17.0.2",
    "react-router-dom": "^5.2.0",
    "react-scripts": "4.0.3",
    "react-select": "^4.3.1",
    "react-transition-group": "^4.4.2"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  },
  "eslintConfig": {
    "extends": [
      "react-app",
      "react-app/jest"
    ]
  },
  "browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  }
}

The only Working solution was downgrading React & NodeJS


sig#809: API Enhancement OSP Customer Management -  GET /api/administration/registration/network/companies Endpoint

Description:
The current endpoint GET /api/administration/registration/network/companies requires enhancements to both the response body and functionality. The following changes need to be implemented:

Response Body Enhancements:

Add externalID field to the response body to represent the external identifier of the company.
Add dateCreated field to the response body to represent the creation date of the company record.

New Search Functionalities:

Implement the ability to search by companyName to allow users to find companies more efficiently.
Implement the ability to search by externalID to facilitate lookup using external identifiers.

New Sort Functionalities:

Implement sorting by dateCreated in both ascending (ASC) and descending (DESC) order.

Acceptance Criteria:

The response body should include the new fields externalID and dateCreated.
The API should support query parameters for searching by companyName and externalID.
The API should support query parameters for sorting by dateCreated in both ASC and DESC order.
Ensure that all existing functionalities are maintained and that the new features do not introduce any regressions.
Update the API documentation to reflect the new changes.
Write unit tests to cover the new functionalities and update existing tests as necessary.

Response Body Example (updated):
{
  "meta": {
    "totalElements": 0,
    "totalPages": 0,
    "page": 0,
    "contentSize": 0
  },
  "content": [
    {
      "companyId": "uuid",
      "externalID": "string",
      "applicationId": "uuid",
      "applicationStatus": "CREATED",
      "applicationDateCreated": "2024-06-24T19:43:59.670Z",
      "dateCreated": "2024-06-24T19:43:59.670Z",
      "lastChangedDate": "2024-06-24T19:43:59.670Z",
      "companyName": "string",
      "companyRoles": [
        "ACTIVE_PARTICIPANT"
      ],
      "identityProvider": [
           {
              "id": "uuid",
              "name": "aliasName"
          }
       ],
      "bpn": "string",
      "activeUsers": "{countActiveOrCreatedCompanyUsers}",
    }
  ]
}

Implementation Notes:

Ensure to follow the existing coding standards and architecture.
Review the existing endpoint to understand current functionalities.

@AnuragNagpure  please ensure to create a new PR for this that enables @lavanya-bmw  to proceed with her frontend adjustments based on the previos ticket from you.

to change the sorting-order a new optional query-parameter 'dateCreatedOrderFilter' (Values 'ASC', 'DESC') has been introduced

to change the sorting-order a new optional query-parameter 'dateCreatedOrderFilter' (Values 'ASC', 'DESC') has been introduced

Thanks Norbert for this new sorting order


SSLCertVerificationError

Describe the bug
Not able to run the script
The collection you were trying to download
Any Random collection for test
Expected behavior
It should download
Terminal output (please show the error that the console showed)
(Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)')))

@santosh-kumar-kaushal Are you on macOS?


Require statement

I'm migrating a mod from pd2hook to BLT where many scripts require another one that isn't a class but more like a json object with a bit of logic. This doesn't seem to work though, whenever running a keybind script that uses any of the required scripts the game crashes. I've tested a simple one in a mods folder called custom, however nothing seems to work. I've tried the following:
mods/custom/script
custom/script
script
each again but with the .lua extension suggested by someone else
There is no documentation on this type of statement with the BLT docs. It works perfectly with pd2hook and is a native lua feature, so I'm not sure what I'm doing wrong.

Example script for a keybind:
local arrItems = require 'mods/custom/spiral_staircase'

function spawnArr()
  local pos = managers.player:player_unit():position()

  for i=1,#arrItems do
    local unit = World:spawn_unit( Idstring(arrItems[i].type.id), pos + arrItems[i].location, arrItems[i].rotation )
    if unit and unit:interaction() then
      unit:interaction():set_active(true, true)
    end
  end
end

spawnArr()

Required script:
local gold = {
  id = "units/payday2/pickups/gen_pku_gold/gen_pku_gold",
  dimensions = Vector3(34, 60, 17)
}

local arrItems = {
  {
  location = Vector3(30,0,0),
  rotation = Rotation(0,0,-0),
  type = gold
  }
  --And so on, too many chars to post on reddit
}

return arrItems

another one that isn't a class but more like a json object with a bit of logic.

That is a perfectly normal Lua file that will return the arrItems table and assign it to the arrItems variable. In fact you can embed this file into the example script code:
local arrItems = {
  location = Vector3(30,0,0),
  rotation = Rotation(0,0,-0),
  type = gold = {
	id = "units/payday2/pickups/gen_pku_gold/gen_pku_gold",
	dimensions = Vector3(34, 60, 17)
	}
  }
  --And so on, about 2k lines
}

function spawnArr()
  local pos = managers.player:player_unit():position()

  for i=1,#arrItems do
    local unit = World:spawn_unit( Idstring(arrItems[i].type.id), pos + arrItems[i].location, arrItems[i].rotation )
    if unit and unit:interaction() then
      unit:interaction():set_active(true, true)
    end
  end
end

spawnArr()

You can probably replace the require with dofile which should work just the same. Or try to require an empty existing file to see if the function itself is bugged.

The function isn't bugged, had it requiring and working just fine with pd2hook. I was never able to get a working require going, even with something simple.
I'm aware I could embed, but it was a large file that was mostly data, the function itself was to use multiple of those data based lua files that I was writing via python scripts. Making a change to that function should be done via a single file, not requiring me to alter all duplicates of the function if it were embedded in each one.
I got around the issue some time ago by wrapping the data lua files as classes(persist) for keybinds to call.


Add missing libs

Oops! Seems like we forgot to add some mamba libs.
@JohanMabille

Hum! I don't get why this test is failing: https://github.com/TheSnakePit/mamba/runs/1037744655
Is it because we were waiting for segfault and because we didn't have the lib imported correctly it was segfaulting maybe?

test failure seems unrelated :)


Implement Default Model Parameters in VSCode Settings

This PR addresses the execution failures that occur when the input length to a model exceeds its default limits in VSCode, as noted in issue #248. To resolve this, we've added a functionality that allows users to set default model parameters, specifically maximum input token limits, thus enhancing user experience and preserving the model’s operation integrity.
The implementation ensures that the input length is checked prior to model execution. If it surpasses the set limits, the user is immediately notified, preventing execution errors associated with input length overflow.
Key features added:

Model-specific max_input_tokens configuration to prevent overflow errors.
Default token limits settings for each model configuration.
Integration of default parameter setup within the activation process of the model.

With these changes, users should now experience fewer execution interruptions and improved reliability when working with different models within VSCode.
Closes devchat-ai/devchat#248

/analyze


Fix click event not bound for router-link (fix #707)

Fix click event not bound for <router-link> when tag is not <a> and doesn't have child <a>

LGTM

Yeah this fallback is a good solution.

Any change this can be merged soon?

@marcvdm We totally let this aside. @fnlctrl Can you add a test for this?

Yeah, will add it tomorrow... been really busy lately
On Tue, Oct 11, 2016, 01:37 Eduardo San Martin Morote <
<EMAIL_ADDRESS>wrote:

@marcvdm https://github.com/marcvdm We totally let this aside. @fnlctrl
https://github.com/fnlctrl Can you add a test for this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vue-router/pull/708#issuecomment-252688165, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFTLl9Ls60tCw_1I9eEdV7mFP5Nq8P08ks5qynfAgaJpZM4KLtte
.

@posva @yyx990803 Done.

LGTM

LGTM

i want back 2.0.0 😭

how to breaks navigation now?


Document for setting up Azure Redis is incorrect

See: https://github.com/Azure/open-service-broker-azure/tree/master/contrib/cf#create-an-azure-redis-cache
This guidance sets up an Azure Redis cache with Basic tier, which is insufficient in production, see here. We have suffered a data loss using Basic tier cache.

Had a quick look on k8s guidance and didn't find any section for creating Azure Redis cache. It should be a CF-only doc error.

This is a definite lethal. We should add a conspicuous note. @krancour @jeremyrickard is the helm chart aware of it?

I notice that the embedded Redis can't be used in production: https://github.com/Azure/open-service-broker-azure/tree/master/contrib/k8s/charts/open-service-broker-azure#configuration. Is it still recommended to create an Azure Redis for production?


Tivimate Support

Can you provide a way to generate a m3u8 which is compatible with Tivimate? The generation can still be done from inside Kodi and a path can be given in settings for the generated file. Kodi is great but the TV ui is sluggish compared to Tivimate.
Also suggest any workarounds or hacks already possible

It's on way. Try beta version and let me know if you are facing any problem with tivimate. #apply-for-beta


Support more customization options?

Currently graphiql only support several view customization options(children: Logo, ToolBar, Menu,...etc),  but I can't find a direct way to hide or show some elements, such as the whole toolbar, the resultviewer, or the docs panel, it would be great if there are options to control the visibility of some elements, and change the style of those elements.
Thanks!

+1

With the release of graphiql@2 last year, we also published a new package called @graphiql/react. This new package solves this issue, but not quite in the expected way. Let me explain.
Building in more customization options into GraphiQL would ever increase the API surface and maintenance complexity, which isn't something we wanted to do. Instead, GraphiQL is what we call the "reference implementation for a GraphQL IDE". It's merely using all the building blocks from @graphiql/react and sticks them together in a particular way.
If you want to customize GraphiQL, you have several options. Instead of reciting them here, here's a link to the section of the README that goes into more detail. If these customization options do not solve your use-case, we encourage you to take the GraphiQL component as a template, create your own component and customize it to your needs.
As a final note, there might be things (state, UI components, ...) that are not exposed yet through @graphiql/react. If you find something that you'd need, feel free to open a new issue specifically for that thing.


Fix infinite "view" event triggers upon network change error

To verify this we can change the endpoint to regetest which currently throws 500 error for that api.
We get an infinite spinner in the web wallet app which is expected
But Segment keeps throwing view/ events this will pretty much fill up our logs with tons of events so we want to fix this asap.

Actually it is not firing infinitely and is not caused by the absent regtest endpoint. The analytics is firing 4 events whenever user changes the route. I will fix it.


Move over progress icons to Fontawesome 5

and list FA as (optional) peer-dependency

Eliminating need for FontAwesome Font entirely, using unicode arrow instead.


Output as esm format

low priority, as I don't personally use type: 'module' that much yet.

Be careful here - there are still fundamental issues with ESM in Node, such as -

__dirname and__filename are undefined and have to be mocked.
Importing dependencies that provide both ESM and CJS is unreliable, can result in two instances of the same lib at runtime, which can cause subtle bugs if the dependency keeps an internal state.
Import filename must be full path to the file with the extension. A lot of CJS code relies on the convention of index.js (so that require('./module') === require('./module/index.js')), or CJS hooks for importing .json files etc.

These issues can be resolved, and each developer can make their app compatible with both ESM and CJS, but if this library chooses to output as ESM it will likely break a lot of existing code and slow down the adoption.

@eugene1g yeah this will only be an option, not the default behavior.  ideally, it should output esm only when type: 'module' is present in package.json.


[pigment-css] Support cross-referencing components

Summary
One of the "killer features" of styled-components, IMO, is the ability to reference one component's class within another component definition.
For example:
const Figure = styled.figure`...`

const Link = styled.a`
  color: blue;

  ${Figure} & {
    color: inherit;
  }
`

It would be great if we could do the same thing in Pigment CSS!
Here's what I tried to do:
export default function Home() {
  return (
    <>
      <Wrapper>
        <Button>Inside</Button>
      </Wrapper>

      <Button>Outside</Button>
    </>
  );
}

const Wrapper = styled('div')``;

const Button = styled('button')({
  color: 'red',

  [`${Wrapper} &`]: {
    color: 'blue',
  },
});

This doesn't work, because Wrapper gets stringified to [object Object].
I know that Linaria supports this behaviour, which also uses wyw-in-js, so I know this is possible, but I'm afraid I have no idea how they're accomplishing it 😬.
Repro
CodeSandbox • Github source
Motivation
I know that this might seem like a pretty niche concern, but this pattern is so so important.
A lot of teams solve this by creating a "variant" of a component. For example, maybe we create a FigureLink styled component:
const Link = styled('a')({
  color: 'blue',
});

const FigureLink = styled(Link)({
  color: 'inherit',
});

The problem is that this requires the developer to remember to use FigureLink each and every time they have a link inside a figure. It requires superhuman discipline. Most likely, we'll wind up with a mismatched UI, where some links use FigureLink and others use Link.
Alternatively, we could style based on tag, like:
const Figure = styled('figure')({
  '& a': {
    color: 'inherit',
  }
});

The trouble with this approach is that it "reaches in" to the Link component and meddles with its internal styles. It also means that the styles for the Link component will be sprinkled all across the codebase, making it very difficult to understand the ways in which styles can change.
With the "cross-reference" thing, all of the styles for Link are gathered in 1 place.
Search keywords: Pigment CSS

There is a workaround:
 const Button = styled('button')({
   color: 'red',

-  [`${Wrapper} &`]: {
+  [`.${Wrapper} &`]: {
     color: 'blue',
   },
 });

but I agree, we should change this, it's not following https://styled-components.com/docs/advanced#referring-to-other-components or https://emotion.sh/docs/styled#targeting-another-emotion-component.

You beat me to it, @oliviertassinari! I just inspected the compiled CSS and yeah, it injects abc123 .def456 instead of .abc123 def456.