readline.ListenRemote and telnet connection

Hi,
I'm using readline.ListenRemote to create remote accessible shell with readline but I've noticed it does not really play nice with telnet - when I make new telnet connection I'm not getting predefined prompt by just a default telnet welcome screen:
Trying <IP_ADDRESS>...
Connected to localhost.
Escape character is '^]'.

The same is with netcat. I can connect to it only using readline.DialRemote :(
I really appreciate any help ...


How to install pre-release versions of Helm charts using Flux?

I have versions 1.0.19 & 1.0.20-qa of a Helm chart in my Helm repo. I tried setting version in my HelmRelease to *-qa & x.x.x-qa but 1.0.20-qa is not installed; 1.0.19 is installed.
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: guacamole
  namespace: eks-fresh-install
spec:
  releaseName: guacamole
  chart:
    spec:
      chart: guacamole
      version: x.x.x-qa
      sourceRef:
        kind: HelmRepository
        name: eaa-charts
        namespace: flux-system
  valuesFrom:
  - kind: ConfigMap
    name: helm-values
  interval: 5m
  install:
    disableWait: true
    remediation:
      retries: 3
  upgrade:
    disableWait: true
    remediation:
      retries: 3

$ kubectl get hr guacamole -o yaml

apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  creationTimestamp: "2022-02-17T12:39:27Z"
  finalizers:
  - finalizers.fluxcd.io
  generation: 3
  labels:
    kustomize.toolkit.fluxcd.io/name: eks-fresh-install-eaa-ecp-guacamole
    kustomize.toolkit.fluxcd.io/namespace: flux-system
  name: guacamole
  namespace: eks-fresh-install
  resourceVersion: "59022703"
  uid: 87997b21-5a1c-48fb-b77e-7a3b2715c122
spec:
  chart:
    spec:
      chart: guacamole
      reconcileStrategy: ChartVersion
      sourceRef:
        kind: HelmRepository
        name: eaa-charts
        namespace: flux-system
      version: x.x.x-qa
  install:
    disableWait: true
    remediation:
      retries: 3
  interval: 5m
  releaseName: guacamole
  upgrade:
    disableWait: true
    remediation:
      retries: 3
  valuesFrom:
  - kind: ConfigMap
    name: helm-values
status:
  conditions:
  - lastTransitionTime: "2022-02-17T12:52:00Z"
    message: Release reconciliation succeeded
    reason: ReconciliationSucceeded
    status: "True"
    type: Ready
  - lastTransitionTime: "2022-02-17T12:41:30Z"
    message: Helm upgrade succeeded
    reason: UpgradeSucceeded
    status: "True"
    type: Released
  helmChart: flux-system/eks-fresh-install-guacamole
  lastAppliedRevision: 1.0.19
  lastAttemptedRevision: 1.0.19
  lastAttemptedValuesChecksum: 9537a99634ebbb55df0d9d88e0b8a60628f80fb7
  lastReleaseRevision: 2
  observedGeneration: 3

$ kubectl describe hr guacamole

Name:         guacamole
Namespace:    eks-fresh-install
Labels:       kustomize.toolkit.fluxcd.io/name=eks-fresh-install-eaa-ecp-guacamole
              kustomize.toolkit.fluxcd.io/namespace=flux-system
Annotations:  <none>
API Version:  helm.toolkit.fluxcd.io/v2beta1
Kind:         HelmRelease
Metadata:
  Creation Timestamp:  2022-02-17T12:39:27Z
  Finalizers:
    finalizers.fluxcd.io
  Generation:  3
  Managed Fields:
    API Version:  helm.toolkit.fluxcd.io/v2beta1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:labels:
          f:kustomize.toolkit.fluxcd.io/name:
          f:kustomize.toolkit.fluxcd.io/namespace:
      f:spec:
        f:chart:
          f:spec:
            f:chart:
            f:sourceRef:
              f:kind:
              f:name:
              f:namespace:
            f:version:
        f:install:
          f:disableWait:
          f:remediation:
            f:retries:
        f:interval:
        f:releaseName:
        f:upgrade:
          f:disableWait:
          f:remediation:
            f:retries:
        f:valuesFrom:
    Manager:      kustomize-controller
    Operation:    Apply
    Time:         2022-02-17T12:41:28Z
    API Version:  helm.toolkit.fluxcd.io/v2beta1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:finalizers:
          .:
          v:"finalizers.fluxcd.io":
      f:status:
        f:conditions:
        f:helmChart:
        f:lastAppliedRevision:
        f:lastAttemptedRevision:
        f:lastAttemptedValuesChecksum:
        f:lastReleaseRevision:
        f:observedGeneration:
    Manager:         helm-controller
    Operation:       Update
    Time:            2022-02-17T13:14:03Z
  Resource Version:  59076013
  UID:               87997b21-5a1c-48fb-b77e-7a3b2715c122
Spec:
  Chart:
    Spec:
      Chart:               guacamole
      Reconcile Strategy:  ChartVersion
      Source Ref:
        Kind:       HelmRepository
        Name:       eaa-charts
        Namespace:  flux-system
      Version:      x.x.x-qa
  Install:
    Disable Wait:  true
    Remediation:
      Retries:   3
  Interval:      5m
  Release Name:  guacamole
  Upgrade:
    Disable Wait:  true
    Remediation:
      Retries:  3
  Values From:
    Kind:  ConfigMap
    Name:  helm-values
Status:
  Conditions:
    Last Transition Time:          2022-02-17T13:14:03Z
    Message:                       Release reconciliation succeeded
    Reason:                        ReconciliationSucceeded
    Status:                        True
    Type:                          Ready
    Last Transition Time:          2022-02-17T12:41:30Z
    Message:                       Helm upgrade succeeded
    Reason:                        UpgradeSucceeded
    Status:                        True
    Type:                          Released
  Helm Chart:                      flux-system/eks-fresh-install-guacamole
  Last Applied Revision:           1.0.19
  Last Attempted Revision:         1.0.19
  Last Attempted Values Checksum:  9537a99634ebbb55df0d9d88e0b8a60628f80fb7
  Last Release Revision:           2
  Observed Generation:             3
Events:
  Type    Reason  Age                From             Message
  ----    ------  ----               ----             -------
  Normal  info    35m                helm-controller  Helm install has started
  Normal  info    35m                helm-controller  Helm install succeeded
  Normal  info    33m                helm-controller  Helm upgrade has started
  Normal  info    33m                helm-controller  Helm upgrade succeeded

$ flux logs --since 30m | grep guacamole

2022-02-17T13:20:06.589Z info Kustomization/eks-fresh-install-eaa-ecp-guacamole.flux-system - server-side apply completed
2022-02-17T13:20:06.601Z info Kustomization/eks-fresh-install-eaa-ecp-guacamole.flux-system - Reconciliation finished in 117.639979ms, next run in 2m0s
2022-02-17T13:20:06.601Z info Kustomization/eks-fresh-install-eaa-ecp-guacamole.flux-system - Discarding event, no alerts found for the involved object

Can you please try version: ">1.0.0-0"

Thanks @stefanprodan, it worked!

it doesn't work if we use version: version: ">=1.0.0-0 <10.10.10-10"
we have version 1.20.0-2
but the log shows it still uses 1.20.0
"msg":"artifact up-to-date with remote revision: '1.20.0'"

1.20.0-2 < 1.20.0


Add blog post on new ML resources

Adds a blog post to highlight the recent work on notebooks and docs for ML
✨ RENDERED ✨

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @aijamalnk @rezarokni

LGTM. Do you want to rerun the tests or want to skip the failed ones?

LGTM. Do you want to rerun the tests or want to skip the failed ones?

I think that was a legitimate failure (I introduced some bad whitespace with my last edit and missed the failing check). Its fixed now.
This should be ready to merge now


Combining a lambda function resolver with field level authentication produces wrong resolver

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v14.16.1
Amplify CLI Version
4.52.0
What operating system are you using?
Mac
Amplify Categories
api
Amplify Commands
codegen, push
Describe the bug
My GraphQL model has a type with a field, that is resolved by a lambda function and has field level authentication set. The generated resolver tries to read the data from the $ctx.source.<fieldname> instead of $ctx.prev.result
schema:
type Club
  @model
  @auth(rules:[
…  ]){
  id: ID!
  tenantAdminGroup: String!

…
  admins: [Admin] @function(name: "genericResolver-${env}")
                  @auth(rules:[{allow: groups,   provider: userPools, groupsField: "tenantAdminGroup",   operations: [read]}])

…
}

amplify/backend/api/clubs/build/resolvers/Club.admins.res.vtl
## [Start] Checking for allowed operations which can return this field **
#set( $operation = $util.defaultIfNull($context.source.operation, "null") )
#if( $operation == "Mutation" )
$util.toJson(null)
#else
  $util.toJson($context.source.admins)
#end
## [End] Checking for allowed operations which can return this field **

Without the @auth directive in the schema, the resolver correctly shows:
$util.toJson($ctx.prev.result)

Expected behavior
Resolver amplify/backend/api/clubs/build/resolvers/Club.admins.res.vtl should be
## [Start] Checking for allowed operations which can return this field **
#set( $operation = $util.defaultIfNull($context.source.operation, "null") )
#if( $operation == "Mutation" )
$util.toJson(null)
#else
  $util.toJson($ctx.prev.result)
#end
## [End] Checking for allowed operations which can return this field **

Reproduction steps

combine @auth and @function on a field in a graphql schema
generate code with amplify api gql-compile

GraphQL schema(s)

type Club
  @model
  @auth(rules:[
…  ]){
  id: ID!
  tenantAdminGroup: String!

…
  admins: [Admin] @function(name: "genericResolver-${env}")
                  @auth(rules:[{allow: groups,   provider: userPools, groupsField: "tenantAdminGroup",   operations: [read]}])

…
}

Log output

# Put your logs below this line

Additional information
No response

@AndreasEK this use case is not supported in transformer. The  field level auth works under the assumption that fields are already present in the model. I am marking this as an enhancement.


chore: make samples depend on the current version

Auto-fixing samples dependency.

Codecov Report

Merging #16 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #16   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines           4      4
=====================================
  Hits            4      4

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1cc3325...f3a2e26. Read the comment docs.


feat: add tokens and component classes

This is an attempt to join our 3 repos in one.
What is added:
https://github.com/warp-ds/component-classes
https://github.com/warp-ds/tokens
Result after build now:

QUESTION Do we want to separate files into folders, like /dist/tokens/finn-no.css etc. Why do I ask? It is a matter which url we will produce here.
Do we like 👇
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>or 👇
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>I'm leaning towards putting only the tokens files to the tokens folder in dist. And leave others as is, as resets/resets.css is not adding any value imho. But not a strong opinion though
TODO:

[ ] update README:s
[ ] we will now start publish to npm, double check if everything is added

Nice! I agree that keeping token-related files under /tokens path makes sense.
Would we remove files like README and CHANGELOG from folders and keep just one for all on the root level?

Nice! I agree that keeping token-related files under /tokens path makes sense. Would we remove files like README and CHANGELOG from folders and keep just one for all on the root level?

Yea, I think so. Let's clean them up. I'll remove CHANGELOG:s and update the root README with everything we have under local README:s and then I'll delete them too


port: remove Cortana from Channels enum (#3730)

The changes in fix: remove Cortana from Channels enum (#3730) may need to be ported to maintain parity with microsoft/botbuilder-js.

Fixes microsoft/botbuilder-js#3603
Targeting cloud-adapter to avoid future merge conflicts
Specific Changes

Remove Cortana from Channels enum in botframework-schema, see https://github.com/microsoft/botbuilder-js/issues/3603#issuecomment-856311472
Hidden public helper hasMessageFeed() always returns true (no change on visibility in declarations)
supportsCardActions() no longer has Channels.Cortana case (will use default false for 'cortana' channelId).
remove/update Cortana specific tests in choices_channel.test.js and choices_choiceFactory.test.js
OAuthPrompt.channelSupportsOAuthCard() no longer has Channels.Cortana case (will use default true for 'cortana' channelId).

Please review and, if necessary, port the changes.

closing it should be done as part of https://github.com/microsoft/botframework-sdk/issues/6448


Multiple instances

Is it possible to modify the plugin so that it can create an array of bittrex instances?
Momentarily, only one user can use the application at the same time.

This is in the newest release


add isDataURI validator

Coverage increased (+0.01%) to 99.087% when pulling 40c730d816e216ee70d6303c48a4b23620f447c7 on voronianski:master into f80ef0204026bbd3c323bfbb955d2ac1c6deaeb6 on chriso:master.

Thanks!


Requires Java 21

The class files are actually compiled in Bytecode-version 65.0 (Java 21) , so there's probably some configuration error in the gradle. I am not sure why exactly but personally I back away from "jvmToolchain" in current gradle version, because it does not seem to do what I wanted it to do.

Release v2.1.0 should fix this. It should be available shortly on Maven Central. I intended to reduce the JVM target to 11 a while back, but it fell into my backlog for a while.

Seems to work nicely with Java 11 now, thanks. :+1:


Initial rendered data

Can we feed initial content data for initialization? If so, does it accept html as a format?
The reason is that I am seeking to find answers on how to convert an already existing project that was made with tinymce and access a possible migration to draft-js.

#55 asks about this as well. I think we'll reuse the paste handler to offer some basic support for this.


refine test output for FastDateParserTest

FastDateParserTest fails on openjdk-ea
Hi.
I updated my local java 15 to newest version and reproduced the error.
This error is caused by a new added locale (in the latest versions of java15) called "ff_LR_#Adlm".
Unfortunately I found no documents about it, and I have no idea about why it happened, as I am not a "ff_LR_#Adlm" user.
(I doubt if there really exist any "ff_LR_#Adlm" user actually)
And I have a feeling that this is not a bug by commons-lang, but a bug by jdk15, as we are using SimpleDateFormat to format a Date to a String, and use SimpleDateFormat to parse that String, and caused an error. SimpleDateFormat is a class from JDK.
So what I can do is just refine output for tests, for showing what locale caused what error, and wait for oracle guys to fix it.
So, should we do something to inform openjdk guys about this buggy thing we found? And how?
@garydgregory

Coverage remained the same at 94.897% when pulling 5b350aa33b1ec01d65c54b765d6f2ebe2dc61728 on XenoAmess:fix_FastDateParserTest into 6363fced4b3837afb8a36ed109264b016097d8d8 on apache:master.

see the new added java15BuggyLocaleTest.
It errors in line 733, means sdf.parse(formattedDate.toUpperCase(buggyLocale));
Seems this locale in jdk-15 cannot process a UpperCase date String.

@XenoAmess - regarding informing the OpenJDK guys, I would think we would contact Rory O'Donnell as a response to: https://lists.apache.org/thread.html/rd619f4bc54e6d85cd84d7b9ac5628000c5d787543fe8b01c21c1c9c5%40<dev.commons.apache.org>
I'm happy to do that if you want.

Done


lineHeight display issue

Environment
react-native 0.64.0:
npm ls react-native-macos: 0.64.13
node: 17.0.1
npm: 8.1.0
yarn: N/A
xcodebuild: 13A1030d

Steps to reproduce the bug
Create a TextInput and set the lineHeight to 40, and the text gets pushed too far down but if you focus the field the cursor remains at the top of the field.
<TextInput style={[{lineHeight: 40}]} placeholder='Search...' autoCompleteType={'off'} autoCorrect={false} underlineColorAndroid='transparent' />
Workaround is to use padding but this will cause inconsistent results depending on the font used by the client.
Expected Behavior
It's expected that the text and cursor will be centered in the lineHeight.
Actual Behavior
Text gets pushed too far down but cursor is at the top of the field.

Reproducible Demo
No response
Additional context
No response

We've hit line height issues across all platforms. Does this expo snack match the behavior you're seeing?

I'm closing this issue cause it's low priority, and RN Windows yields the same result as RN macOS.
Easy enough workaround is to either use padding or justifyContent which works consistently on all platforms.


Inheritance security rule violation while initializing Xpand.ExpressApp.Chart.Win.XpandChartWinModule

We have migrated our XAF project from DX 20.1.4 to 20.2.5 and eXpand to the according versions, when doing so we also changed dependencies from referencing assemblies directly to Nuget packages.
When we now deploy the software to client machines, it throws an error during start up:
10.02.21 09:30:43.479	================================================================================
10.02.21 09:30:43.574	Trace Log for myApp.Win.exe is started
10.02.21 09:30:43.574	================================================================================
myApp.Win.exe Error: 0 : 10.02.21 09:31:01.674	================================================================================
The error occurred:
Type:       AggregateException
Message:    Mindestens ein Fehler ist aufgetreten.
Data:       0 entries
Stack trace:

at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at DevExpress.ExpressApp.Win.WinApplication.SetupCore(String applicationName, IList`1 objectSpaceProviders, ApplicationModulesManager modulesManager, ISecurityStrategyBase security)
at DevExpress.ExpressApp.XafApplication.Setup()
at myApp.Win.Program.Main(String[] arguments)
----------------
InnerException:
		Type:       InvalidOperationException
		Message:    Exception occurs while initializing the 'Xpand.ExpressApp.Chart.Win.XpandChartWinModule' module: Inheritance security rules violated by type: "DevExpress.XtraCharts.ChartControl". Derived types must either match the security accessibility of the base type or be less accessible.
		Data:       0 entries
		Stack trace:

at Xpand.XAF.Modules.Reactive.ReactiveModuleBase.SetupModules(ApplicationModulesManager applicationModulesManager)
at Xpand.XAF.Modules.Reactive.ReactiveModuleBase.SetupModulesPatch(ApplicationModulesManager __instance)
at DevExpress.ExpressApp.ApplicationModulesManager.SetupModules_Patch1(ApplicationModulesManager this)
at DevExpress.ExpressApp.ApplicationModulesManager.Load(ITypesInfo typesInfo, Boolean loadTypesInfo)
at DevExpress.ExpressApp.XafApplication.SetupCore(String applicationName, IList`1 objectSpaceProviders, ApplicationModulesManager modulesManager, ISecurityStrategyBase security)
at DevExpress.ExpressApp.Win.WinApplication.<>c__DisplayClass77_0.b__0()
at System.Threading.Tasks.Task.Execute()
----------------
InnerException:
				Type:       TypeLoadException
				Message:    Inheritance security rules violated by type "DevExpress.XtraCharts.ChartControl". Derived types must either match the security accessibility of the base type or be less accessible.
				Data:       0 entries
				Stack trace:

at System.Reflection.RuntimeAssembly.GetType(RuntimeAssembly assembly, String name, Boolean throwOnError, Boolean ignoreCase, ObjectHandleOnStack type)
at System.Reflection.RuntimeAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
at Xpand.XAF.Modules.ModelMapper.Services.PredefinedMapService.GetListViewConfiguration(PredefinedMap predefinedMap, Assembly controlAssembly, String listEditorTypeName, String gridViewTypeName, String gridColumnTypeName)
at Xpand.XAF.Modules.ModelMapper.Services.PredefinedMapService.GetModelMapperConfiguration(PredefinedMap predefinedMap)
at Xpand.XAF.Modules.ModelMapper.Services.PredefinedMapService.ModelMapperConfiguration(PredefinedMap predefinedMap, Action1 configure)    at Xpand.XAF.Modules.ModelMapper.Services.PredefinedMapService.Extend(ApplicationModulesManager modulesManager, PredefinedMap map, Action1 configure)
at Xpand.ExpressApp.Chart.Win.XpandChartWinModule.Setup(ApplicationModulesManager moduleManager)
at Xpand.XAF.Modules.Reactive.ReactiveModuleBase.SetupModules(ApplicationModulesManager applicationModulesManager)
InnerException is null
What is a possible cause for this error and how can we solve it?
Thanks for your support.

can u repro it in an empty XAF solution having installed and register the XpandChartWinModule?

Unfortunately not, application compiled from the sample project attached is starting up.
Do you have any idea for what to check in the project not working?
inheritance_Security_violation_repro.zip

the exception is about a version missmtach i would start by clearning the nuget cache and the temp dirs. If does not start by that u haave to make sure that your dependecies are correct e.g. use the container packages only and remove any binding redirections from your app.config
let me know

also I totally suggest u use the DX nugets rather than Gac refererences

although u spoke about the client app does not start is not clear does it start in your dev machine?

can u repro it in an empty XAF solution having installed and register the XpandChartWinModule?

add the XpandSystemWin module to it please and try again

or even better if u still fail to repro it add all the modules u have in your main app and try again.

we need to trace it down in a repro sample, so we can tell what to blame and act accordingly

Closing issue for age. Feel free to reopen it at any time.
.Thank you for your contribution.


Blockscout header:  Indexing Tokens

After deploying Blockscout it shows the next header:

This header gives a sense of inaccuracy, and would be nice if we can reduce/improve this process or at least track the process to control what is happening.

I would say that seems that after Blockscout index all the blocks (which usually takes a few minutes), we need to restart the indexer app to get the header removed faster.


Address OS.request_permissions() bug when a non-platform permission is included

Fixes https://github.com/GodotVR/godot_oculus_mobile/issues/102

cc @NeoSpark314

I force pushed an amend to fix the include style as I want to merge this now and cherry-pick for 3.2.2 beta 2.
See #38474 for a proposal to improve the Java import grouping.

Thanks!

Cherry-picked for 3.2.2.


Add Module Loader runtime objects

Based on the W3C Module Loader spec:
https://whatwg.github.io/loader
Includes more or less complete implementations of the runtime objects:
%Registry%
%RegistryPrototype%
%Loader%
%LoaderPrototype%
%ModuleStatus%
%ModuleStatusPrototype%
Includes a stub implementation of %Module%.
Most of the abstract operations in the spec are implemented completely but
we are missing some key ones such as SatisfyInstance. The next step will
be to merge the existing ModuleRecord implementation with the ModuleStatus
object and set of abstract operations.
In particular, this pull request does not plug-in any of the dependency
graph resolution or export name resolution because a refactor of existing
ModuleRecord code is required.
There are some open issues with the code in this change. For example, it's
not clear from the spec what we should do if transforming a promise object
with a fulfillment handler returns a non-promise object. It seems possible
that user code could replace the constructor property on the promise
instance which could cause the transformed promise to be anything. Should
we throw here? Should we just wrap whatever the object is in a resolved
promise? It's not clear. Most of the machinery in the spec requires
promise objects so I have taken the approach that we should throw anytime
an object is not a promise when we expect it should be.

@Yongqu Please take a look over this one, thanks! 😀

:shipit:

Followed up with @boingoing offline. Seems some design change might render this PR obsolete but salvageable. Adding Waiting label.

Closing this for now, it doesn't appear that we will be implementing this in the near future.


Is it possible to move the cursor away while generating?

I have a split buffer and asking ChatGPT the questions, and at the meanwhile I want do some viewing or editing work at another buffer.
Currently it will lead to an error if I move my cursor away from the gpt-writing buffer

@LintaoAmons Hey, try the latest version please. It's not perfect - when you move to other window, it breaks undojoin (which joins together all write/delete operations so, the full response can be undone with single u) into two parts (so you'd have to hit u twice to erase response), but otherwise it seems to work.

Super cool!


Can't install on Windows

Expected Behavior

Running "npm install -g ethereumjs-testrpc" in Windows CMD, Powershell, GitBash installs testrpc.
Current Behavior

Get error while installing and install doesn't work.
Possible Solution

Don't know....
Steps to Reproduce (for bugs)

Run npm install -g ethereumjs-testrpc

Context

Can't install
Your Environment

Version used: Newest?
Environment name and version (e.g. PHP 5.4 on nginx 1.9.1): Windows 10 64
Server type and version: Windows 10 64
Operating System and version: Windows 10 64
NodeJs Version: Node 6.7.0

Hi @Alonski. When writing an issue that results in an error, please include the error. We can't help you otherwise.
That said, have you followed our Windows install instructions? I'm going to close this ticket. Please reopen after you've followed these instructions and are still receiving an error. Please post the full error message in the issue or else there's nothing we can do to help.
Thanks!

Sorry I forgot to add my Log!
Anyways yes I did try the Windows install instructions. Still couldn't get it to work.

Not against reopening, but I'm going to need the error message you're receiving in order to help.

Hmm, I didn't realize you added the log at the top of the issue. Can you give the error message you're receiving as well? That log is very verbose - hard to track down whee to start.

I included npm-debug at the top. Anything else?
On Oct 6, 2016 7:47 AM, "Tim Coulter"<EMAIL_ADDRESS>wrote:

Not against reopening, but I'm going to need the error message you're
receiving in order to help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ethereumjs/testrpc/issues/175#issuecomment-251866117,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbmZwrXUSahKOcm_Cn2D5jkSZ2bA9bKks5qxH1ggaJpZM4KNwte
.

@tcoulter
Added a screenshot of my errors... Hope this helps.

Helps a lot. From this link it appears you just need to run npm -g install npm@next, or follow what other people have tried there.


MB-14207-Display-Scheduled-Delivery-Date

Jira ticket for this change
Summary
This ticket populates the 'scheduled delivery date' field on shipments in the quality assurance report. The 'scheduled delivery date' parameter was added to MTOShipment.yaml swagger definition. The MTOShipment payload has  been updated, and the parameter was added to the ShipmentShape.

Setup to Run Your Code

💻 You will need to use three separate terminals to test this locally.
Terminal 1
Start the Storybook locally.
make storybook

Terminal 2
Start the UI locally.
make client_run

Terminal 3
Start the Go server locally.
make server_run

Additional steps

Navigate in the app to this spot:
Log in to the office app as a QAE/CSR user
Navigate to a move (move code: EVLRPT works locally)
Click on Quality Assurance in the navigation bar under the customer info and header
Click on ‘view report’ on any of the reports with that link
https://user-images.githubusercontent.com/37859033/197006249-53b1233e-7a72-43fd-aa20-4ba64d768790.mov
Verification
Steps for Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Backend

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

Messages

:book:
:link: MB-14207

  Generated by :no_entry_sign: dangerJS against 6295b9d76731450364718ff6776a39ce4ec28bbd

Changes look good in code and working well in the app. Scheduled delivery date displaying as expected, nice work!

Thanks, Leia!


BJData optimized binary array type

See https://github.com/NeuroJSON/bjdata/pull/6 for further information.
Introduces a dedicated B marker for bytes.
This is used as the strong type marker in optimized array format to encode binary data such that it can also be decoded back to binary data (instead of wrongly decoding as an integer array).
Draft while awaiting the release of BJData draft 3.
Would a legacy_binary flag be desirable to continue supporting draft 2 expectations of uint8 typed arrays for binary?

Pull request checklist
Read the Contribution Guidelines for detailed information.

[x]  Changes are described in the pull request, or an existing issue is referenced.
[x]  The test suite compiles and runs without error.
[x]  Code coverage is 100%. Test cases can be added by editing the test suite.
[x]  The source code is amalgamated; that is, after making changes to the sources in the include/nlohmann directory, run make amalgamate to create the single-header files single_include/nlohmann/json.hpp and single_include/nlohmann/json_fwd.hpp. The whole process is described here.

coverage: 99.648% (+0.001%) from 99.647%
when pulling 646a609a65b27e12fbd20cfc6d655281d707875d on nebkat:develop
into ee32bfc1c263900d5c31cf8a8c5429048719e42a on nlohmann:develop.

Please run make amalgamate with AStyle 3.1.

draft3_binary parameter added to to_bjdata, defaulting to false, along with tests for both versions.
from_bjdata previously wasn't able to parse uint8 binary arrays so it has just gained the ability to parse byte arrays as binary with no parameter.
Would it make sense to introduce a to_bjdata_draft3() function and deprecate to_bjdata() to encourage use of the newer version?

Thanks a lot! Feels much better without a breaking change!
Regarding the draft version - would it make sense to add an int parameter draft to the function and defaulting it to 2 and allow to set it to 3 instead of the boolean? Then we have some room for the future there.
Regarding deprecation - adding a new function to the API just for the sake of deprecating another feels odd. I think we should rather deprecate the default parameter for the mentioned draft parameter and force client to choose the value in the future.
What do you think?

I like it, didn't think of that, much better solution!
So perhaps something like this?
/// how to encode BJData
enum class bjdata_version_t
{
    draft2 JSON_HEDLEY_DEPRECATED_FOR(3.12.0, draft3),
    draft3,
};

...

static std::vector<std::uint8_t> to_bjdata(const basic_json& j,
        const bool use_size = false,
        const bool use_type = false,
        const bjdata_version_t version = bjdata_version_t::draft2)
{
    std::vector<std::uint8_t> result;
    to_bjdata(j, result, use_size, use_type, version);
    return result;
}

Could technically even put ubjson as a version as they are so close and use it internally.

Could technically even put ubjson as a version as they are so close and use it internally.

You mean using BJData as parameter for UBJSON output/input?

Yes, internally.
json/include/nlohmann/detail/output/binary_writer.hpp:
    // json/include/nlohmann/detail/output/binary_writer.hpp
    void write_ubjson(const BasicJsonType& j, const bool use_count,
                      const bool use_type, const bool add_prefix = true,
-                      const bool use_bjdata = false)
+                      const bjdata_version_t version = bjdata_version_t::ubjson) // or "draft0", which could be argued is equivalent
    {

Then we can do:
include/nlohmann/json.hpp:
    /// @brief create a UBJSON serialization of a given JSON value
    /// @sa https://json.nlohmann.me/api/basic_json/to_ubjson/
    static void to_ubjson(const basic_json& j, detail::output_adapter<std::uint8_t> o,
                          const bool use_size = false, const bool use_type = false)
    {
-        binary_writer<std::uint8_t>(o).write_ubjson(j, use_size, use_type);
+         binary_writer<std::uint8_t>(o).write_bjdata(j, use_size, use_type, bjdata_version_t::ubjson); // Or defaulted as above
    }

    /// @brief create a BJData serialization of a given JSON value
    /// @sa https://json.nlohmann.me/api/basic_json/to_bjdata/
    static void to_bjdata(const basic_json& j, detail::output_adapter<std::uint8_t> o,
-                         const bool use_size = false, const bool use_type = false)
+                         const bool use_size = false, const bool use_type = false, const bjdata_version_t version = bjdata_version_t::draft2)
    {
-        binary_writer<std::uint8_t>(o).write_ubjson(j, use_size, use_type, true, true);
+        binary_writer<std::uint8_t>(o).write_ubjson(j, use_size, use_type, true, version);
    }

Would cut down on the amount of if (use_bjdata && bjdata_version == ...) and instead just be if (version == ...).

Yes, what I meant: would this be something that could - in the long run - be exposed to the customer? As in: deprecating to_bjdata in favor of to_ubjson with a version parameter.

Ah right - yes, but if anything I would deprecate to_ubjson in favour of to_bjdata considering UBJSON has not seen any meaningful updates in ~8 years. If we can play our part in moving people towards BJData that seems like a positive thing in the long run!


Create zh_cn.json

@chronosacaria can you please review this when you have a chance? thank you!

Yep. I'll take a look once I get back to my PC


Compare Machine Learning algorithms

Machine learning techniques are diverse and we must find a suitable technique for malicious document detection

Malicious Docx (363 files)
Benign Docx (363 files)
Num of Total Feature : 1285
Compare Machine Learning : LogisticRegression, DecisionTreeClassifier, SVM, GaussianNB, KNeighborsClassifier, RandomForestClassifier, GradientBoostingClassifier


Can't call RetroRuntime::is_joypad_button_pressed

Commit 9b4c3f0 ("various cleanups and improvements") changed the first argument of RetroRuntime::is_joypad_button_pressed from u32 to RetroDevicePort, but RetroDevicePort doesn't have a public constructor.

Emulators don't need to query for buttons though.. right? 😅


[super] Tutorial: CSV + ...

[ ] Validating CSV - maybe covered by #240
[ ] A Schema for CSV -> JSON Table Schema

[ ] Inferring it automatically

[ ] Piping CSV between tools ...

@rgrp "A Schema for CSV -> JSON Table Schema + Inferring it automatically" covered here:
http://frictionlessdata.io/guides/creating-tabular-data-packages-in-python/#inferring-a-csv-schema

This issue was moved to frictionlessdata/frictionlessdata.io#55


Self Signed Certificates accepts certificate validity config option that is longer than CA certificate validity

Bug Description
The charm should go to blocked status if the certificate validity time > ca certificate validity time and should never generate certificates in those cases.
To Reproduce

juju deploy self-signed-certificates --config root-ca-validity=1 --config certificate-validity=2
juju deploy tls-certificates-requirer
juju integrate self-signed-certificates tls-certificates-requirer

Environment
Revision 190 (edge)
Relevant log output
N/A

Additional context
No response

Fixed by #242


Showcase: Add Baby Feeds

By analyzing the blame information on this pull request, we identified @brentvatne and @manonthemat to be potential reviewers.

Looks good to me. Can you rebase to master @jondot ?

Hey, I'm really sorry for the churn, but we are changing up how the showcase works, and just focusing on apps that have some media presence or technical blog posts / other content. So I appreciate the spirit behind this pull request but I think we should close it.


[BUG] plugins/lsp omnisharp settings use incorrect case/structure

Field
Description

Plugin
lsp

Nixpkgs
unstable

Home Manager
unstable

Description
The omnisharp lsp server expects options to be directly set using snake_case_lower, yet we provide them as a nested settings table using camelCase.

Minimal, Reproducible Example (MRE)

programs.nixvim = {
  plugins.lsp {
    enable = true;
    servers.omnisharp = {
      enable = true;
      settings.enableRoslynAnalyzers = true;
    };
  };
}

I'm pretty keen to contribute and fix this myself, just wondering if someone could point me in the right direction to idiomatically map props from settings.enableRoslynAnalyers -> enable_roslyn_analyzers

Are you sure this is repercuted in the init.lua? Most plugins have a mapping from camelCase to snake_case

@traxys
Here is the contents of options (using print(vim.inspect(server.extraOptions))) before the call to require('lspconfig')[server.name].setup(options)
{
  cmd = { "/nix/store/zpvg8d9zwwxj6g344cdqv3grpldcxvxz-omnisharp-roslyn-1.39.11/bin/OmniSharp" },
  settings = {
    omnisharp = {
      enableEditorConfigSupport = true,
      enableImportCompletion = true,
      enableMsBuildLoadProjectsOnDemand = true,
      enableRoslynAnalyzers = true,
      organizeImportsOnFormat = true,
      sdkIncludePrereleases = false
    }
  }
}

For anyone stumbling across this looking for a dirty hack/workaround and a way to get omnisharp_extended working, see below:
          omnisharp = {
            enable = true;
            extraOptions = {
              enable_rosyln_analyzers = true;
              enable_import_completion = true;
              organize_imports_on_format = true;
              enable_editorconfig_support = true;
              analyze_open_documents_only = true;
              handlers."textDocument/definition".__raw =
                #lua
                "require('omnisharp_extended').handler";
            };
          };

I'm pretty keen to contribute and fix this myself, just wondering if someone could point me in the right direction to idiomatically map props from settings.enableRoslynAnalyers -> enable_roslyn_analyzers

There is already a converter in helpers.toSnakeCase, although mapping over the keys will be a little more involved.


Swift 4 and RxSwift 4 update

Updated RxStarscream to Swift 4 and RxSwift 4 updates. Including the Sample App.

Hey @pedrommcarrasco , Thanks for this !
Do you mind rebasing on top of master?
Since the CI was fixed since and I want to make sure the RxSwift 4 updates doesn't break the tests.
Thanks !

@freak4pc was nothing :)The following week will be a busy one, but sure, I would do it as soon as possible.

@pedrommcarrasco
It should be as easy as a
git rebase master
git push -fu origin

No rush though !

@freak4pc according to the following image seems that nothing broke. (Went to my fork's rxstarscream folder and ran both commands).

Excuse me if was not what you meant.

You need to pull RxSwiftCommunity's master to your master before rebasing - you have an outdated master. Another option (easier), just add this file to your root folder: https://github.com/RxSwiftCommunity/RxStarscream/blob/master/circle.yml

@pedrommcarrasco Do you mind opening a new PR instead of this one? I'm not sure why but there is something weird going on and it's not triggering the CI. Would make both our lives easier :) Thanks.

@freak4pc Sure


Tests: Bluetooth: tester: change of L2CAP listen() API

L2CAP listen() command was extended by adding security and key_size
fields. It can be used to configure security requirements for L2CAP
connection to be accepted. This is required for tests
L2CAP/ECFC/BV-{11, 13, 15}-C - normally (in corrsponding L2CAP/LE/CFC/BV
tests) requirements are defined by PSMs, but in ECFC EATT PSM is always
used.
Signed-off-by: Krzysztof Kopyściński<EMAIL_ADDRESS>

FYI @sjanc


Compatibility with 2021 QNED models

I'd like to use the calibration function with a 2021 QNED model, more specifically a 65" QNED919PA, to upload LUTs generated with DisplayCal. Due to the risk of bricking the mainboard, I wanted to ask if there are any known compatibility issues or if someone already has successfully done it.
The QNED919PA supports auto-calibration (CalMan) with LUT access and uses an Alpha7 Gen4 Processor 4K according to the data sheet).
Here is the output of some of the info methods:
system_info:  {'returnValue': True, 'features': {'dvr': False}, 'receiverType': 'DVB', 'modelName': '65QNED919PA', 'serialNumber': '<redacted>', 'programMode': True}
software_info:  {'returnValue': True, 'product_name': 'webOSTV 6.0', 'model_name': 'HE_DTV_W21U_AFADATAA', 'sw_type': 'FIRMWARE', 'major_ver': '03', 'minor_ver': '30.10', 'country': '<redacted>', 'country_group': '<redacted>', 'device_id': '<redacted>', 'auth_flag': 'N', 'ignore_disable': 'N', 'eco_info': '01', 'config_key': '00', 'language_code': '<redacted>'}

It seems that the calibration_support_info method needs to be updated for QNED models.
Apart from the general question of compatibility, I also have some questions concerning the calibration itself:

Does it make sense to set color temperature and saturation as well as gamma in calibration mode before performing the calibration to bring the basic picture closer to the intended target or are they redundant since LUTs also affect them?

What about the local dimming feature? Should I turn it off in calibration mode or does the calibration mode set it in some way?

Alpha7 requires 17pt 3dlut, and I guess DoVi the new 2019 config format.
You can try bscpylgtv, it works with chip type instead of.model name, although yours is not supported, but you can override it easily with -c option. Read through the calibration part of.the readme.
Once you confirmed it's working, you can do a small PR for you W21U chip type.
https://github.com/chros73/bscpylgtv

yes
I don't know

Thanks for the info, I'll take a look when I have more time.
Regarding my first question, does your yes mean that it's advisable to set color temperatur and saturation as well as gamma in calibration mode before performing the calibration?

Yes.


Actually fix Stale Bumper

Last time I "fixed" https://github.com/AnalyticalGraphicsInc/cesium-concierge/issues/116 it was because of line endings. I confirmed that the cron script was running, called it a day, and moved on with my life.
The cron script is running, but since the system initiates the cron script, not the root user, it has a different environment, so all the AWS environment settings aren't available to the cron script. To remedy this without having to manually specify the secret key somewhere, this PR makes it dump the environment on deploy into a file, which the cron script can then grab when running.
I believe this is the easiest/most automated way.

Thanks for the pull request @OmarShehata!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:sparkles: :sparkles: :sparkles:I'm the Cesium Concierge and I'm here to test things. :sparkles: :sparkles: :sparkles:

Just tested this, but the Docker command to dump the env runs too early, and the env doesn't include the variables from AWS. Looking for a better way.

Ok, I'm pretty confident this should work @ggetz . It writes out the env from the application to ensure it's actually the same settings. I'm also fairly confident this is secure because if someone has access to the disk, then they already have access to the environment variables on that system.

@OmarShehata Should we do any cleanup of the environment file at the end? I'm still not thrilled at saving all the environment variables to the system and leaving them there...

It must remain there every time the cron script runs, since the cron script always runs with a barebones environment.
I have been digging and I don't see any potential issue with this scheme. I think the more traditional approach would be to store them in ~/.bashrc and have the cron script get its environment variables from there, but that's the same thing (except the file lives somewhere else). Security-wise I can't see any situation where someone would have access to the filesystem and not to the environment variables.

OK, let's merge and give this a try.


Update sugar for multi-dex

I use sugar-ORM in my project, when I enable multi-dex, not all the tables will be created. So I did some research on it and this pull request might be a solution. I tested it in my project and it works well.

I added some missed imports

Coverage decreased (-0.21%) to 70.69% when pulling d75766c5b40549db7dd147c196583bb857adb1ed on tracytheron:master into 85d5f3e663aa9b160d58d47115388d5407dcfd87 on satyan:master.

@tracytheron could fix the conflits please?

@sibeliusseraphini  fixed

How can I get this fix? I like SugarORM but his this MultiDex issue drives me nuts.

You can get the master version and use it as a module in your project

Could you give me a .jar? Something it's not working for me...

I've uploaded a .jar from master here: https://www.dropbox.com/s/9z85lrud4lgiv6e/sugar-<IP_ADDRESS>405082137.jar?dl=0


Gist description not being set on Github

🐛 Describe the bug
Gist description not being set on Github
🌴 Visual Studio Code Version : [ 1.37.1 ]
🌴 Code Settings Sync Version : [ 3.4.2 ]
🌴 Standard or Insiders : [ standard ]
🌴 Portable or Installed : [ installed ]
🌴 OSS or Official Build : [ Official ]
🌴 Operating System : [ Windows 10 ]
🌴 Occurs On: [Upload ]
🌴 Proxy Enabled: [ No ]
📰 To Reproduce
Steps to reproduce the behavior:

Command Palette > Sync Advanced Options > Sync Edit Extension Local Settings
Verify that default "gistDescription": "Visual Studio Code Settings Sync Gist", is present
Modify some User setting in VSCode
SHIFT ALT U to upload settings to GitHub
Open the Gist in Github and very description.

💪 Expected behavior
Expected behavior is that the Gist's description would be updated.
It does not get updated

Git Description is one time only you cant change the description after creating the Gist.
In order to change the Description you need to create new Gist.

Reset the settings.
Change the value of askGistName to true
Upload the settings. Upon uploading, it will ask you to write the description of Git.

If it still doesnt work, let me know i will reopen this issue.

I understand the premise.
Unfortunately askGistName on true doesn't work for me either, as described by another user here
https://github.com/shanalikhan/code-settings-sync/issues/1023

Yes, i will look into it.
Thanks!


cluster-bench: CI benchmark

turn the workbench-smoke-test/workbench-ci-analysis into a generic derivation
extend the topology generator to generates plain lines and circles
clean up profile definitions wrt. fund specification
clean up the derivation nomenclature in the Nix layer
workbench-ci-test / workbench-ci-analysis derivations, as parallel to smoke.
refactor the workbench Nix code a bit

bors r+

bors r+

bors r+

bors r+

bors r+


Update azure monitor opentelemetry exporter readme version

1.0.0-beta.24 is released now

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


Patch 2.1.1

I suggest the following as the new default INI:
[General]
; Menu toggle key for keyboard
ToggleKey = f1
; Menu toggle key for Gamepad
ToggleKeyGP = None
; 0 = Single Press, 1 = Hold, 2 = Double Press
ToggleMode = 0
FreezeTimeOnMenu = true
BlurBackgroundOnMenu = true
MenuStyle = Skyrim
;MenuStyle = Modern
;MenuStyle = Default


How to store graph for further use ?

Want to save generated graph but I can't find needed functionality in docs :(

The model is pickleable (or should be), so that's one approach. If you just care about the graph then you can simply save the numpy arrays of neighbor_graph, or convert to a scipy sparse adjacency matrix representation and save that. If you are interested more in the latter approach then the PyNNDescentTransformer is probably a better approach as that will give the adjacency matrix directly.

Thanks for answer.
What do you mean by neighbor_graph ?
By storing I meant something that faiss has, write_index and read_index functions where's you can save and restore entire index

Ah, if you want the whole index saved then just pickle the entire object, and load is back later.

Thank you !


Remove citations that we don't use normatively

I can't find any reference to ISO 19101-1, ISO 19105 throughout the GML encoding files, nor would I really expect to. (I can't find them in the CItyGML-3.0CM repository either)
MIME, URI, 19103, 19111 are used quite a bit; ISO 19109 for "AnyFeature" in core.xsd;
ISO 19107 Spatial schema & others (ISO 19108, 19111, 19109, 19123) are mentioned in Chuck's "initial population" of a data dictionary of ISO-Classes. The data dictionaries are not currently included in the draft document. Are they needed, or are they better 'by reference' to the Conceptual Model?
ISO 19108 is mentioned in Annex G, but I don't see that as a normative mention leading to a normative reference.
If the Data Dictionary is not part of this GLM encoding standard, the perhaps an informative reference (bibliography or Annex G.1) to at least ISO 19107 would be helpful.
ISO 19123 was only mentioned here, in the ISO-Classes data dictionary, and in "clause_5_conventions" (discussion of <>) - and yesterday we discussed removing the Clause 5 UML description.
ISO 19156 was only mentioned here & in the Glossary (as source of a couple of terms that are not actually used)
ISO 19775 is X3D, and we actually cite the W3C/COLLADA standard, not the ISO one.
I have left in ISO 19136-1 and 19136-2 although arguable we could just cite OGC GML 3.2 & 3.3 (the latter, not normatively?)

Peter, thanks a lot for checking the references.
ISO 19101-1 is referenced in Chapter 4 Terms and Definitions, but I assume from your comment that this does not count to include ISO 19101-1 as normative reference?
Does this mean that only when the normative parts in our standard reference other standards these referenced standards are considered normative references and should be included in Chapter 3?
We removed the data dictionary. It was a 1:1 copy from the Conceptual Model standard and we decided that it is not necessary to include it in the Encoding standard as well.
Yes, it would then definitely be useful to add ISO 19107 to the bibliography.
For Annex G.1 I'm also not sure, whether we need all the terms there. The annex is currently also a 1:1 copy from the Conceptual Model standard.
I actually wanted to add OGC GML 3.2 and 3.3 first, but then switched to the ISO standards, I thought that's maybe preferred? But I can change that again, that's also good.
GML 3.3 would then rather also be added to the bibliography?

Terms/normative references:
The introductory text of the clause is "The following normative documents contain provisions that, through reference in this text, constitute provisions of OGC". I don't think that just being the source of a definition fits that description.
Other recent OGC standards have the same clause & text as ISO: "Normative references" / "The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document" - again, I don't think that ISO 19101 as source of a term fits that description. I have examples of ISO standards that cite another standard as the source of a term but don't give that other standard as a normative reference or even in the bibliography.
OGC or ISO citations:
I don't know whether OGC prefers citing its own standards or ISO ones when they are "technically identical"; I guessed OGC would prefer to OGC citation, in the same way that ISO prefers the ISO citation!


Config search

[ ] Bugfix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)

Proposed changes
It would be useful (occasionally) to be able to find which nodes are using a particular config node. This PR does that by making the number field to the right of the node identifier in the config node window into a button that opens the search window with the result of the search for that config node id.
Checklist

[X] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
[X] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage remained the same at 76.364% when pulling 6cd6a61a0ddfc91f490b8d62e37eb53705993b36 on config-search into 0529eed0c9c1f9c0d60b1f2a1c88fe7c1b6e0d75 on dev.


Adding Custom Plugin

Sorry I could not find any information anywhere else about how to go about adding ckeditor plugins to this setup.
What is the suggested and/or best way to go about adding additional custom ckeditor plugins to this strapi plugin? (i.e. add toolbar button to trigger simple plugin)
Any information would be greatly appreciated.
Thanks in advance.

I'm also lookin for this feature.
As far as I know, you need to build your own CK editor from it's source plus dependencies this strapi plugin uses (strapi upload plugin, etc)

Me too, I want the footnotes plugin.

Currently there is no way of adding additional plugins in this build. As @darmanovic said you need to build your own build of ckeditor for this and paste your build into this plugin.
Some links that may help:
https://ckeditor.com/docs/ckeditor5/latest/installation/getting-started/frameworks/react.html
https://ckeditor.com/docs/ckeditor5/latest/installation/getting-started/predefined-builds.html
https://ckeditor.com/docs/ckeditor5/latest/installation/getting-started/quick-start-other.html
https://ckeditor.com/docs/ckeditor5/latest/framework/guides/plugins/package-generator.html
https://ckeditor.com/docs/ckeditor5/latest/installation/advanced/alternative-setups/dll-builds.html

@nshenderov
Sorry for going off topic, but In rough terms what would be easiest way to add responsive columns capability, or inserting predefined custom HTML element at button click? At the moment i'm writing custom HTML by hand, but that would be unacceptable for the end non technical user.

@darmanovic
You can use headings with custom css class for this. Check this:
https://ckeditor.com/docs/ckeditor5/latest/features/headings.html
https://ckeditor.com/docs/ckeditor5/latest/features/general-html-support.html
But I prefer to use strapi components for complicated html


fix: pyc files in Meson mesonbuild repo causing rebuilds

Fixes #1342
It seems that pyc files appear in the Meson repo between the first and second time a python toolchain is used and if these are not excluded, the new pyc files invalidate dependent rules, forcing a rebuild.
For more context, see #1342 and Slack 🧵.

I force-pushed the same commit to re-trigger the checks but they all seem to be failing for some reason :(  I'll investigate and see if I can fix it in another PR!

Its because CI has upgraded to bazel 8 - I've started fixing it here: https://github.com/bazel-contrib/rules_foreign_cc/pull/1340 but need to wait for bazel 8.0.1 as theres a regression with respect to handling of $(location) that is returning more than one file now.

The fix seems sensible to me though, although like you I'd like to know why its necessary!

The fix seems sensible to me though, although like you I'd like to know why its necessary!

Yeah, totally 😅
From what I gathered, there's a bunch of issues with the pyc files but what really surprises me is the Python version in those files... the fact that it seems to be compiled with the standalone interpreter and not with the Python version that's selected in the toolchain.
But alas, I think this is as good as it gets! Maybe when I learn more about how Bazel & some of the rules work I'll have an aha! moment 😄


Invalid styl file forces server to not responde

How to repeat:

With a project-stub (or yo bem-stub) make a common.blocks/page/page.styl with mixed tabs and spaces as indent.
Force to render page

Result: Timeout + error mess in stderr?;
Expected result: Stack trace in the response + error mess in stderr.

I think there are two problems: 1 in styl tech, and the second — in the server itself. So I'll file the same issue in styl tech repo.
Ref: https://github.com/enb-make/enb-stylus/issues/29

Bug was`t reproduced — https://github.com/enb-make/enb-stylus/issues/29


chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-k8s-30-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4982

Questions ?
Please refer to the Backport tool documentation


[Fix](inverted index) fix wrong no need read data when need_remaining_after_evaluate

Proposed changes
When using an equal predicate on a column that applies an inverted index with a parser, it requires remaining_after_evaluate. In this situation, we cannot optimize the column without reading the data.

run buildall

run buildall

run buildall


LookUp columns for Rules and Prompt Rules display an unhelpful autonumber field

When specifying Rules in the Prompt Rule intersection table, specifying rules only displays the Rule's Autonumber field and not the text of the rule. This is not helpful when adding new prompt rules:

Hey @sgtsnacks-64 I have made the changes to this. I have left the Rule table pretty much as is, except I have renamed the Rule Ref column to Rule Text, and changed it from an autonumber to Text.  There is now a flow that will run and update the Rule's primary field to the Rule Text field (original)


MacOS binaries - retain compatibility with MacOS 10.9

Until some versions ago, installing with macbrew run without problems. Latest versions were not anymore compatible with Mavericks.
Would it be possible to retain compatibility with this old version of MacOS?

I generally don't like to support older platforms that Chromium no longer supports because that increases our maintenance burden (which slows down releases). However, if you manage to create or find some patches that allow us to maintain compatibility, let us know over at ungoogled-software/ungoogled-chromium-macos. Thanks.


Vim or nano?

Currently, we install only vim in all base images. I'm perfectly fine with vim, but I'm not sure if most ML researchers are.
Maybe we should ask our users during cookiecutting? :smile:
full_name [Your name]:
email [Your email address (e.g. you@example.com)]:
project_name [Name of the project]:
project_slug [name-of-the-project]:
project_short_description [A short description of the project]:
code_directory [modules]:
vim_or_nano [vim]:
...

both are there, no need to overcomplicate such things, imo


Missing sample policies

[Enter feedback here]
The introduction states that there are "three levels of sample policy: cloud-native, enterprise, and cloud-design-principle-compliant" I see the cloud-native example, but not the others. Where can I find them?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b0adac86-b138-d165-6c8c-4caf9ba00a6e
Version Independent ID: 649a6874-879b-3915-d59c-a260005271f7
Content: Cloud-native Security Baseline policy - Cloud Adoption Framework
Content Source: docs/govern/security-baseline/cloud-native-policy.md
Service: cloud-adoption-framework
Sub-service: govern
GitHub Login: @BrianBlanchard
Microsoft Alias: brblanch

Thanks for reporting - this issue is under review.  This is a Microsoft Internal DevOps Bug ID AB#319121

@NaomiOooo - Please review.

The wording was incorrect/vague and changed to reflect that there was only an example of cloud-native.


Restricted Lists validation and indicators

Currently, there are two restricted lists (RL) in effect for tournament play - one for the Melee format, and one for Joust.
Thronesdb needs indicate RL violations in the deck builder, the deck/decklist detail views, and in the "decklists" and "my decks" list views.
Out of scope are API changes, and search form additions (e.g. "exclude restristed lists").
We can start by using NetrunnerDB as a model for displaying RL compliance status:

For what it's worth, we already maintain the restricted list data:
https://github.com/throneteki/throneteki-json-data/blob/master/restricted-list.json
I'm not sure how that format compares to what was done with NetrunnerDB, but it's been enough for us to validate decks on Throneteki.


Integrate LLVM at llvm/llvm-project@70ac46667613

Bump LLVM to include features necessary for GEN_PASS_CLASSES updates (#120).

This matches the latest LLVM commit in tensorflow/mlir-hlo at the moment of writing: https://github.com/tensorflow/mlir-hlo/commit/20905fb29dfbf0ba5a6c952d8914cf78f1671f13. LGTM.


validating D:\superset\superset\docker-compose.yml: services.db.env_file.0 must be a string

Bug in setup superset
when i make a clone from git clone --depth=1  https://github.com/apache/superset.git
and make a cd to project and
try docker compose up
get this error
validating D:\superset\superset\docker-compose.yml: services.db.env_file.0 must be a string
Screenshots/recordings

Superset version
master / latest-dev
Python version
Not applicable
Node version
18 or greater
Browser
Chrome
Additional context
i don't have python on my device but i install docker desktop and it's work
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

after a change docker-compose.yml with the above code
get this error
parsing D:\superset\superset\docker-compose.yml: yaml: unknown anchor 'common-build' referenced

can you tell me steps to setup superset and all tools need

Hey there, @ahmedkhederali! 👋 I'm here to help you with any bugs, questions, or contributions you have for the project. I'm looking forward to assisting you!
I found a similar unsolved discussion: "must be a string" error when running docker compose [1].
To resolve the error "services.db.env_file.0 must be a string" in the docker-compose.yml file, you need to change the env_file entries from objects to strings. The env_file should be a list of file paths, not objects with path and required properties.
Here is the corrected version of the docker-compose.yml file:
services:
  redis:
    image: redis:7
    container_name: superset_cache
    restart: unless-stopped
    volumes:
      - redis:/data

  db:
    env_file:
      - docker/.env # default
      - docker/.env-local # optional override
    image: postgres:15
    container_name: superset_db
    restart: unless-stopped
    volumes:
      - db_home:/var/lib/postgresql/data
      - ./docker/docker-entrypoint-initdb.d:/docker-entrypoint-initdb.d

  superset:
    env_file:
      - docker/.env # default
      - docker/.env-local # optional override
    build:
      <<: *common-build
    container_name: superset_app
    command: ["/app/docker/docker-bootstrap.sh", "app"]
    user: "root"
    restart: unless-stopped
    ports:
      - 8088:8088
    depends_on: *superset-depends-on
    volumes: *superset-volumes

  superset-init:
    container_name: superset_init
    build:
      <<: *common-build
    command: ["/app/docker/docker-init.sh"]
    env_file:
      - docker/.env # default
      - docker/.env-local # optional override
    depends_on: *superset-depends-on
    user: "root"
    volumes: *superset-volumes
    healthcheck:
      disable: true

  superset-worker:
    build:
      <<: *common-build
    container_name: superset_worker
    command: ["/app/docker/docker-bootstrap.sh", "worker"]
    env_file:
      - docker/.env # default
      - docker/.env-local # optional override
    restart: unless-stopped
    depends_on: *superset-depends-on
    user: "root"
    volumes: *superset-volumes
    healthcheck:
      test:
        [
          "CMD-SHELL",
          "celery -A superset.tasks.celery_app:app inspect ping -d celery@$$HOSTNAME",
        ]

  superset-worker-beat:
    build:
      <<: *common-build
    container_name: superset_worker_beat
    command: ["/app/docker/docker-bootstrap.sh", "beat"]
    env_file:
      - docker/.env # default
      - docker/.env-local # optional override
    restart: unless-stopped
    depends_on: *superset-depends-on
    user: "root"
    volumes: *superset-volumes
    healthcheck:
      disable: true

volumes:
  superset_home:
    external: false
  db_home:
    external: false
  redis:
    external: false

This change should resolve the error by ensuring that the env_file entries are strings, as required by Docker Compose [2][3].
To continue talking to Dosu, mention @dosu.

@ahmedkhederali the solution suggested by @dosu is solving the issue for me, but the provided file is missing the first part.
You can test it by taking the original docker-compose.yml file and replacing the services: block with the bot's suggestion.
@dosu, can you open a Pull Request with the change you suggested?

Dosu doesn't open pull requests, but it would be awesome if you can :D


Set the ownerReferences field for managing dependencies/ownership

Binding implicitly creates Secret and PodPreset objects.
We need to set the ownerReferences meta field to link those objects with parent Binding. We should also check this link before updating the existing Secret/PodPreset object.

There should also be the ownerReferences link between Instance and Binding, ServiceClass and Instance, Broker and ServiceClass and so on.

The fix for Binding↔Secret merged in https://github.com/kubernetes-incubator/service-catalog/issues/977
For other cases separate issues should be created as needed.


[Snyk] Security upgrade io.netty:netty-common from 4.1.71.Final to 4.1.115.Final

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.
Snyk changed the following file(s):

master/pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue
Score
Upgrade

Denial of Service (DoS) SNYK-JAVA-IONETTY-8367012
  175
io.netty:netty-common:  4.1.71.Final -> 4.1.115.Final  Proof of Concept

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

:tada: Snyk checks have passed. No issues have been found so far.
:white_check_mark: code/snyk check is complete. No issues have been found. (View Details)


Refactored code into smaller files

Refactored the existing file MainAppGUI and MainApp, into smaller class files.
Fixed some of the errors such as removing couple of dependencies and earlier we had two 'main method' one from original code and the one we made. Now its simplified to one main method.

MainDriver.java - main method.
Content from MainApp.java now in ButtonActions.java
Looks of buttons and actionlisteners in ButtonPanel.java
other classes refactored into individual classes such as logger.java, customFormatter.java


Provide basic Dockerfile

Example with mvn build through docker.
This allows users to easily start experimenting with no other dependencies than Docker.

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

Not that I need this merged, just wanted to push what I had to do locally. But you should setup some schedule for checking (and merging) PR's more often ;) I don't have a green button to press!

Sorry for the delay. Thanks for contributing to uReplicator :)

It would probably be nice to add mention of docker support & how to run the docker image in the README. I actually missed this until I was searching something in the issues list and came across this, granted I should have looked at the files in the root of the repo.
Also, looking at this Dockerfile & my initial issue building for docker, makes me curious whether the maven build process heap memory constraints is only limited to Docker, because I notice this Dockerfile sets specific memory requirements, and I hit the memory error compiling uReplicator-Controller, following the link it referenced mentioned to adjust the memory settings for maven, and that fixed my issue. Wonder if it would ever happen locally on a non-Docker maven build. If possible for non-Docker, might want to mention it. If only for docker, might want to mention it for docker.


re-Adding lookups

I moved @hero78119 's work into a new branch and rebased for the most recent version of dev branch.
Rather than having V2 I moved things into its own file lookup_ppsnark.rs.
Ran clippy.

Longer discussion can be found here:
https://github.com/lurk-lab/arecibo/pull/48

rebased and PRed here #386

Hi @wyattbenno777 thanks for continuing this work and glad this can help somewhere ❤
For memory consistency check protocol, https://eprint.iacr.org/2024/325.pdf propose more efficient protocol which eliminate the work of commit the whole table in the final compress snark. Please refer Appendix A for full protocols.
I believe once introduce this enhancement in compression snark then it will make this solution more robust.


Problems with flex on Safari

Hey, I'm having the following structure:

   <ScrollBars></Scrollbars>

#main uses display: flex;, while #content has the size of flex:1;. The content within ScrollBars isn't visible on Safari (the div has no height). I can only fix this if I set #content also to display:flex; and the ScrollBars element to flex:1;, while removing the standard width:100%; height:100%.

+1
@dnish I tried your suggestion but the nested (absolutely positioned) divs have no height :(

Just throwing my two cents in here.
Safari is known for it's issues with flex, therefore, if you didn't add the following, give it a try:
display: -webkit-flex;
display: flex;

As for the flex: 1 try:
-webkit-flex: 1;
flex: 1;
/* or use flex-grow */
-webkit-flex-grow: 1;
flex-grow: 1;

+1

Greetings,
I'm having the same issue. I'm using cssnext autoprefixer so all prefixes have been applied (I also confirmed this is so).

@dnish && @edi thank you for the solution :+1:
P.S. @malte-wessel can you please add this to the documentation as a Safari walk-around?


mouse gestures not drawn on second monitor

This has been happening since June.  I thought I reported it but I guess not.

Thank you for reporting this! I rarely use multiple monitors, so I did not realize this issue so far. I'll look into this in the coming days.

Actually, this turns out to be easier than expected. I've pushed a fix in the fix-multi-output branch. Let me know if you can test and if you see any issues. Thanks!

hey thanks for the quick fix.   i checked out fix-multi-output branch but getting a build error
ninja: Entering directory `build'
[6/30] Compiling C object toplevel-grabber/tl_grabber_test.p/toplevel-grabber-test.c.o
../toplevel-grabber/toplevel-grabber-test.c: In function ‘tl_cb’:
../toplevel-grabber/toplevel-grabber-test.c:29:25: warning: unused parameter ‘data’ [-Wunused-parameter]
29 | static void tl_cb(void* data, struct tl_grabber* gr) {
|                   ^~
[23/30] Compiling C++ object libwstroke.so.p/easystroke_gestures.cpp.o
FAILED: libwstroke.so.p/easystroke_gestures.cpp.o
c++ -Ilibwstroke.so.p -I. -I.. -I/usr/include/cairo -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/sysprof-4 -I/usr/include/pixman-1 -I/usr/include/pango-1.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/libdrm -I/usr/include/libevdev-1.0 -I/usr/include/libxml2 -I/usr/include -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c++17 -O0 -g -fPIC -pthread -DBOOST_ALL_NO_LIB -Wno-unused-parameter -Wno-format-security -DWAYFIRE_PLUGIN -DWLR_USE_UNSTABLE -MD -MQ libwstroke.so.p/easystroke_gestures.cpp.o -MF libwstroke.so.p/easystroke_gestures.cpp.o.d -o libwstroke.so.p/easystroke_gestures.cpp.o -c ../easystroke_gestures.cpp
../easystroke_gestures.cpp: In lambda function:
../easystroke_gestures.cpp:497:71: warning: invalid use of incomplete type ‘class wf::seat_t’
497 |                                 if(needs_refocus2) wf::get_core().seat->focus_view(initial_active_view);
|                                                                       ^~
In file included from /usr/include/wayfire/output.hpp:7,
from ../easystroke_gestures.cpp:18:
/usr/include/wayfire/scene-input.hpp:11:7: note: forward declaration of ‘class wf::seat_t’
11 | class seat_t;
|       ^~
../easystroke_gestures.cpp: In member function ‘void wstroke::check_focus_mouse_view()’:
../easystroke_gestures.cpp:571:68: error: ‘class wf::window_manager_t’ has no member named ‘focus_raise_view’
571 |                                         wf::get_core().default_wm->focus_raise_view(mouse_view);
|                                                                    ^~~~~~~~~~~~~~~~
../easystroke_gestures.cpp: In member function ‘bool wstroke::start_stroke(int32_t, int32_t)’:
../easystroke_gestures.cpp:583:66: error: invalid use of incomplete type ‘class wf::seat_t’
583 |                         initial_active_view = wf::get_core().seat->get_active_view();
|                                                                  ^~
/usr/include/wayfire/scene-input.hpp:11:7: note: forward declaration of ‘class wf::seat_t’
11 | class seat_t;
|       ^~~~~~
../easystroke_gestures.cpp: In member function ‘void wstroke::handle_input_move(int32_t, int32_t)’:
../easystroke_gestures.cpp:637:86: error: invalid use of incomplete type ‘class wf::seat_t’
637 |                                                 if(needs_refocus) wf::get_core().seat->focus_view(target_view);
|                                                                                ^~
/usr/include/wayfire/scene-input.hpp:11:7: note: forward declaration of ‘class wf::seat_t’
11 | class seat_t;
|       ^~~~~~
../easystroke_gestures.cpp:638:81: error: ‘class wf::window_manager_t’ has no member named ‘focus_raise_view’
638 |                                                 else wf::get_core().default_wm->focus_raise_view(target_view);
|                                                                                ^~~~~~~~~~~~~~~~
../easystroke_gestures.cpp: In member function ‘void wstroke::cancel_stroke()’:
../easystroke_gestures.cpp:769:61: error: invalid use of incomplete type ‘class wf::seat_t’
769 |                         if(target_mouse) wf::get_core().seat->focus_view(initial_active_view);
|                                                             ^~
/usr/include/wayfire/scene-input.hpp:11:7: note: forward declaration of ‘class wf::seat_t’
11 | class seat_t;
|       ^~~~~~
../easystroke_gestures.cpp: In instantiation of ‘void wstroke::set_idle_action(CB&&) [with CB = wstroke::visit(const SendKey*)::<lambda()>]’:
../easystroke_gestures.cpp:347:20:   required from here
../easystroke_gestures.cpp:497:73: error: invalid use of incomplete type ‘class wf::seat_t’
497 |                                 if(needs_refocus2) wf::get_core().seat->focus_view(initial_active_view);
|                                                    ~~~~~~~~~^~
/usr/include/wayfire/scene-input.hpp:11:7: note: forward declaration of ‘class wf::seat_t’
11 | class seat_t;
|       ^~
../easystroke_gestures.cpp: In instantiation of ‘void wstroke::set_idle_action(CB&&) [with CB = wstroke::visit(const Ignore*)::<lambda()>]’:
../easystroke_gestures.cpp:369:20:   required from here
../easystroke_gestures.cpp:497:73: error: invalid use of incomplete type ‘class wf::seat_t’
497 |                                 if(needs_refocus2) wf::get_core().seat->focus_view(initial_active_view);
|                                                    ~~~~~~~~~^~
/usr/include/wayfire/scene-input.hpp:11:7: note: forward declaration of ‘class wf::seat_t’
11 | class seat_t;
|       ^~
../easystroke_gestures.cpp: In instantiation of ‘void wstroke::set_idle_action(CB&&) [with CB = wstroke::visit(const Button*)::<lambda()>]’:
../easystroke_gestures.cpp:397:19:   required from here
../easystroke_gestures.cpp:497:73: error: invalid use of incomplete type ‘class wf::seat_t’
497 |                                 if(needs_refocus2) wf::get_core().seat->focus_view(initial_active_view);
|                                                    ~~~~~~~~~^~
/usr/include/wayfire/scene-input.hpp:11:7: note: forward declaration of ‘class wf::seat_t’
11 | class seat_t;
|       ^~
../easystroke_gestures.cpp: In instantiation of ‘void wstroke::set_idle_action(CB&&) [with CB = wstroke::call_plugin(const std::string&)::<lambda()>]’:
../easystroke_gestures.cpp:542:19:   required from here
../easystroke_gestures.cpp:497:73: error: invalid use of incomplete type ‘class wf::seat_t’
497 |                                 if(needs_refocus2) wf::get_core().seat->focus_view(initial_active_view);
|                                                    ~~~~~~~~~^~
/usr/include/wayfire/scene-input.hpp:11:7: note: forward declaration of ‘class wf::seat_t’
11 | class seat_t;
|       ^~
../easystroke_gestures.cpp: In instantiation of ‘void wstroke::set_idle_action(CB&&) [with CB = wstroke::call_plugin_for_view(const std::string&, bool)::<lambda()>]’:
../easystroke_gestures.cpp:554:19:   required from here
../easystroke_gestures.cpp:497:73: error: invalid use of incomplete type ‘class wf::seat_t’
497 |                                 if(needs_refocus2) wf::get_core().seat->focus_view(initial_active_view);
|                                                    ~~~~~~~~~^~
/usr/include/wayfire/scene-input.hpp:11:7: note: forward declaration of ‘class wf::seat_t’
11 | class seat_t;
|       ^~
../easystroke_gestures.cpp: In instantiation of ‘void wstroke::set_idle_action(CB&&) [with CB = wstroke::end_stroke()::<lambda()>]’:
../easystroke_gestures.cpp:689:21:   required from here
../easystroke_gestures.cpp:497:73: error: invalid use of incomplete type ‘class wf::seat_t’
497 |                                 if(needs_refocus2) wf::get_core().seat->focus_view(initial_active_view);
|                                                    ~~~~~~~~~^~
/usr/include/wayfire/scene-input.hpp:11:7: note: forward declaration of ‘class wf::seat_t’
11 | class seat_t;
|       ^~
[27/30] Compiling C++ object wstroke-config.p/actiondb.cc.o
ninja: build stopped: subcommand failed.

Great to hear! I'll merge the fix to the main branch and close this issue unless you run into more problems


IdentityServer4.AccessTokenValidation is Not Strongly-Named

Hello,
We're trying to use the latest IdentityServer4.AccessTokenValidation NuGet package (2.7.0) in a strongly-named .NET Core application and we get the following error:

FileLoadException: Could not load file or assembly 'IdentityServer4.AccessTokenValidation, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)

So it seems the assembly in the package is not strongly-named and my only option (please, correct me if I'm wrong) seems to be disabling the signing of the application and any other projects that reference it.
According to a Strong Name Signing document by the CoreFX team:

Because of the viral nature of strong-naming, it is recommended that publicly published .NET libraries are strong-named. Not strong-naming a .NET library excludes anyone who does need to strong-name their application or library from using it.

So, is there a reason for the IdentityServer4.AccessTokenValidation output not to be strongly-named or is it an issue worth addressing?
Thank you! :)

I hope you are not strong naming for security reasons - because it is not a security feature.
That being said - we will strong name the upcoming 3.0 release. Probably beginning next year.

Strong-naming is a common policy for all projects included in our build process in order to prevent accidental drop-in replacements and enable registration of assemblies in the GAC.
Of course, there are projects signing doesn't make much sense (such as web or console apps) but once we decide to reference a non strong-named assembly from our own class library, in run into an issue like this one.

I can't remember if we ever did that - but this library is deprecated in favour of this superior and more flexible approach:
https://leastprivilege.com/2020/07/06/flexible-access-token-validation-in-asp-net-core/


feat: enable v2_dev flag

@pcattori cross-env is still needed in the test:e2e:run script, so that one can't be removed


VSCode debugger cannot load call stack / dart source during exception handling on macOS with Flutter 3.3.x

Steps to Reproduce

Create a new flutter project using version 3.3.x
Run & debug it in VSCode
Throw an exception somewhere during execution
Try to use the vscode dubugger to step within the stack trace

Observe that the source is not available:
Could not load source 'dart:ui/hooks.dart': <source not available>.
Could not load source 'dart:isolate-patch/isolate_patch.dart': <source not available>.
Conditions necessary to reproduce:

Flutter version at or above 3.3.x
Build app for macOS

Making any of these changes will not reproduce the issue:

Downgrade flutter to 3.0.5
Build for iOS or Android instead of macOS
Create a pure dart project with the same dart sdk version (2.18.2)

I found these related issues but could not find a solution among them:
https://github.com/flutter/flutter/issues/24912
https://github.com/Dart-Code/Dart-Code/issues/2519
https://github.com/dart-lang/sdk/issues/19227
https://github.com/dart-lang/sdk/issues/35820
https://stackoverflow.com/questions/54390922/could-not-load-source-dartcore-runtime-libobject-patch-dart-source-not-avai
https://stackoverflow.com/questions/72385991/could-not-load-source-dartcore-patch-errors-patch-dart-source-not-available
Output of flutter doctor:
flutter doctor -v
[✓] Flutter (Channel stable, 3.3.4, on macOS 12.6 21G115 darwin-arm, locale
    en-US)
    • Flutter version 3.3.4 on channel stable at
      /Users/andrew/fvm/versions/stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision eb6d86ee27 (2 weeks ago), 2022-10-04 22:31:45 -0700
    • Engine revision c08d7d5efc
    • Dart version 2.18.2
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/user/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14A400
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      11.0.13+0-b1751.21-8125866)

[✓] VS Code (version 1.72.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.50.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 12.6 21G115 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Google Chrome 106.0.5249.119

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

This may be a duplicate of https://github.com/flutter/flutter/issues/111189
Does this still happen on the current Flutter master branch?

@point-source
Please confirm if same happens on latest master or not.
flutter channel master
flutter upgrade

Sure enough, appears to be fixed on master branch. I'll hold out for the next stable release. Thanks

Thanks for the update. Closing based on above comment.


Translate UX

Hello is it possible to translate UX ? (using for a multilangue system)

Hello,
That would be a good idea but I got no time to work on this for now. Feel free to send a pull request if you do it :)

A dommage i didn't this sckill level


Failing test will show diff

If test in make test-cmd is failing, now it will show diff so that
it will be easy to debug.
for example,
===> Starting test <===
convert::expect_success_and_warning: Running: 'kompose -f /home/snarwade/go/src/github.com/kubernetes-incubator/kompose/script/test/fixtures/service-name-change/docker-compose.yml convert --stdout -j' expected_output: '/home/snarwade/go/src/github.com/kubernetes-incubator/kompose/script/test/fixtures/service-name-change/output-k8s.json' expected_warning: 'Unsupported root level volumes key - ignoring'
WARN Unsupported root level volumes key - ignoring
WARN Unsupported depends_on key - ignoring
103c103
<                     "value": "bitnami_wordpres"
---
>                     "value": "bitnami_wordpress"
FAIL: converted output does not match

resolves #604

Awesome! This LGTM.

@surajssd @kadel review please :)


Deleted redundant code in MIQ Policy Controller / Alerts

Check for generated flash messages no longer needed with the code fix in https://github.com/ManageIQ/manageiq/pull/6525
New begin/rescue block in ci_processing/process_elements generates flash messages

@dclarizio @h-kataria Redundant code removal, please review.

LGTM


Removed grafana dashboards

Removed grafana dashboards as they are now in the https://github.com/DFE-Digital/childrens-social-care-cpd-grafana repo

:tada: This PR is included in version 2.0.0-next.42 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix compatibility issue with PowerShell

The previous PR #8 introduces a regression issue (PowerShell not working) so this commit fixes the issue by changing the process creation flag to CREATE_NEW_CONSOLE.

Excellent, thanks again.


New name

Opening thread to agree on and act on changing the name of the project since we don't do a lot of veg :-)

My vote goes to "Python Earth Engine Pipelines" (aka peep)

Sounds good to me! I would say we do the name changing after we finish the first round of development for the larger scale test (issues #5, #8, #15, #22).  There is a few things that would have to go with the name change:

Name change package but also modules
Remove all the code not relevant for us
Update documentation.


Update MD file on new branch 2017-21-17_07-11-49

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


incorrect name validation/restrictions

Expected Behavior
The name values described in https://docs.tigera.io/calico/latest/reference/resources/globalnetworkpolicy are accepted.
Current Behavior
Creating a new GlobalNetworkPolicy where the name contains _ will fail with an error: "name must consist of lower case alphanumeric characters or '-'" even though the docs say "Alphanumeric string with optional ., _, or -."
An underscore was accepted in Version 1 but from what I can tell in the code, it is no longer supported and the docs were not updated
https://github.com/projectcalico/calico/blob/cf7fa35475eba84f5afcd7f53ac7d07dcb403202/libcalico-go/lib/validator/v3/validator.go#L57
Possible Solution

Change the validator or change the docs
Steps to Reproduce (for bugs)

Use caclicoctl to create a new GlobalNetworkPolicy with a name containing _

Context

We are working to upgrade some v1 objects to v3 and are hitting problems.
Your Environment

Calico version v3.26.1
Orchestrator version (e.g. kubernetes, mesos, rkt):
Operating System and version:
Link to your project (optional):

@merickso Thanks for taking the time to open this ticket. Next step is to verify the fix. Depending on how many docs are affected, I may open a ticket to ensure we fix this in multiple places and versions.

@bmckercher123 do you know if this was ever fixed in the docs?


Unable to start application via npm start

Description
I am not able to start application via npm start
Expected Behavior
I am able to start application and visit in my iPhone.
Observed Behavior
Application does not start.
Full terminal output is:
$ npm start

><EMAIL_ADDRESS>start /home/phracek/work/programming/Ruzenec_iOS
> react-native-scripts start

10:35:25 AM: Unable to start server
  See https://git.io/v5vcn for more information, either install watchman or run the following snippet:
    sudo sysctl -w fs.inotify.max_user_instances=1024
    sudo sysctl -w fs.inotify.max_user_watches=12288

npm ERR! Linux 4.13.11-200.fc26.x86_64
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "start"
npm ERR! node v6.11.5
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `react-native-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'react-native-scripts start'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the Ruzenec_iOS package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     react-native-scripts start
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs Ruzenec_iOS
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls Ruzenec_iOS
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/phracek/work/programming/Ruzenec_iOS/npm-debug.log

Environment
Please run these commands in the project folder and fill in their results:

npm ls react-native-scripts:

<EMAIL_ADDRESS>/home/phracek/work/programming/Ruzenec_iOS
└──<EMAIL_ADDRESS>

npm ls react-native:

<EMAIL_ADDRESS>/home/phracek/work/programming/Ruzenec_iOS
└──<EMAIL_ADDRESS>

npm ls expo:

<EMAIL_ADDRESS>/home/phracek/work/programming/Ruzenec_iOS
└─┬<EMAIL_ADDRESS>  └── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>

node -v: v6.11.5
npm -v: 3.10.10
yarn --version:

bash: yarn: command not found...
Packages providing this file are:
'hadoop-yarn'
'cmdtest'

watchman version:

Also specify:

Operating system: Linux
Phone/emulator/simulator & version:

Reproducible Demo
Please provide a minimized reproducible demonstration of the problem you're reporting.
I went through documentation mentioned here https://facebook.github.io/react-native/docs/getting-started.html

have you tried both commands:
sudo sysctl -w fs.inotify.max_user_instances=1024
sudo sysctl -w fs.inotify.max_user_watches=12288
they did work for me

Wow, it works

@kajm what does those commands actually do?

@farmcp This link helped me out! https://github.com/react-community/create-react-native-app/issues/382

these two command worked for me :
sudo sysctl -w fs.inotify.max_user_instances=1024
sudo sysctl -w fs.inotify.max_user_watches=12288

and if you are on a windows environment?

I tried the above mentioned 2 commands. It still didnt work for me.
It waits for infinite time after "Starting packager..."
Please help

Running following worked for me on mac high sierra:
sudo sysctl -w kern.maxfiles=5242880
sudo sysctl -w kern.maxfilesperproc=524288


There is a vulnerability in  log4j 1.2.17 ,upgrade recommended

https://github.com/IBM/Selmate-a-customizable-test-automation-tool/blob/c3858662eab67cabc64a392e43398e056c53d689/source/selmate/pom.xml#L30
CVE-2019-17571 CVE-2020-9488
Recommended upgrade version：
2.13.2

upgraded to 2.17.1


Scaffolding for the script importing Spotify data to Firebase

Still waiting for the actual Spotify data dump, it can take up to 30 days to generate it supposedly. I may need to check the internet for some samples :/

Nice!


users_list: Fix updating of users list on reactivate/deactivate.

User is added to deactivated users list when user is deactivated from
active users list and it remains in the active users for re-toggle
(in case of mistake) and same happens for reactivating users from
deactivated users list.
Whenever user enters any of the list from somehwhere else, list is
up-to-date.
Fixes #14165
Currently, the last active on reactivation gives Unknown as some change is needed in presence code and issue is opened currently #14279.
I am working on that issue and will soon make a PR.

Testing Plan:  This is manually tested.
GIFs or Screenshots:

@sahil839 Can you give an update on the status of this PR?  I know this issue sort of sent us down the rabbit hole of making sure that we weren't showing the wrong "active" date for users after we reactivated them, but is that actually a blocker for this commit?

@showell The only problem is that this will show Unknown on reactivation of a user.

@timabbott I have made the changes.
Circle CI failure is unrelated to my changes and is being discussed on CZO.

I'm working on a deeper fix here.  I'll probably close this PR once I get to a pretty solid point on my branch.  Thanks for working on this @sahil839 -- reading your code here has been helpful for me to understand where we can clean this up a bit.

I haven't quite fixed this yet, but you can see that my recent commits are leading up to a fix here:
https://github.com/zulip/zulip/commits?author=showell

In particular the below commit is sort of a preview of how I will split up handling of Users and Deactivated Users, which should help fix this issue:
https://github.com/zulip/zulip/commit/5c16bb9c990daad26d9d14b9e406c33aaeeed078
There's a little bit of extra work to do, though.


Fix metadata reflection for DECIMAL columns - with test

JDBC describes that COLUMN_SIZE for a DECIMAL type should reflect its total number of digits, whereas DECIMAL_DIGITS describes it numeric scale.
See: https://docs.oracle.com/javase/7/docs/api/java/sql/DatabaseMetaData.html#getColumns(java.lang.String, java.lang.String, java.lang.String, java.lang.String)
This does the right thing for all other types (where numeric_precision is null), except for INTEGER and LONG, where currently in DuckDB this reports 32 and 64, resp, where it should report 10 and 19. That's for another PR, I think.

Thanks!