Upgrade to net7

Upgrade to .net 7.0 most of projects in solution
Update of many packages (but not all: some are not compatible and/or require adaptations)
Partial reformatting and partial code cleaning
Slight modernization of the code (but much remains to be done)

Thanks for submitting this! A massive PR!!! If anyone is watching this PR please comment with any feedback. I will try and review and merge it within the next week.

@RaynaldM You forgot to link your issue #1640 in Development section (right side).
I would love to review the PR if you add me to Reviewers please.

@RaynaldM You forgot to link your issue #1640 in Development section (right side). I would love to review the PR if you add me to Reviewers please.

I don't know why, but I cannot modify my issue

For a some reason Tom did not assign me this PR.
@RaynaldM Are you able to assign me this PR (add to Reviewers)? You're the author, so, I believe you should be able to make me as reviewer.
Otherwise, you need to add me as collaborator to your forked repo RaynaldM/Ocelot: .NET core API Gateway via repo Settings -> Access -> Collaborators page.
The problem is that a reviewer should have Write access for a PR to review it and finally having reviewing result as green checkmark. Only green checkmarks allow to merge PR.
More about PR permissions here:  About pull request reviews - GitHub Docs.
Read the Tips plz!

I had to add you to the team! I'm just trying to get the build working with dotnet 7

Hi @TomPallister ! Thanks for adding to the team! 😍
Hope we will make Ocelot better. 😄
Just having a nice weekend spending!

@TomPallister  While you are fighting with builds (CI-CD, Circle CI ?)... Here is the first review result regarding tests.
I've done some comparison of solutions stability from both branches. After running all tests in Test Explorer:

Left side, source branch solution (RaynaldM:upgrade-to-net7)
Right side, target branch solution (ThreeMammals:develop)
It seems everything is fine, I have ran multiple times. So, the behavior is pretty stable in both solutions. Nothing got worse, possibly, from the point of view of building pipeline.
But the number of tests has been decreased: 813 down to 808. +1 skipped test. So, total 5 tests were removed.
I have no list of removed tests. Should we make the list and review them, and why were they removed?
I guess that some tests are failing after the upgrading. That's why Raynald had removed them from test projects.
@RaynaldM Could you help us the extract the list of removed tests please? Did they turn red?

I went through all the files and fixed the build...it probably wont work but I will mess around until it does then release a new package from main branch!

@TomPallister What about tests?
Too late! You did it! 😄 PR has been merged.

the skipped test was a theory so I think thats why 5 were missing

I didnt see any tests that had been deleted


step-functions-send-to-sns

Description:
step-functions-send-to-sns example does not use step functions at all. Misleading name

Steps to reproduce the issue:
1.
2.
3.
Observed result:
Expected result:

The example contains a lambda function that can be used as a component of step functions.


python3Packages.siosocks: disable blocking tests

Motivation for this change
Fix build (https://hydra.nixos.org/build/163902565, https://hydra.nixos.org/build/165229756)
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 156729 run on x86_64-linux 1

8 packages built:

python310Packages.aioftp
python310Packages.parfive
python310Packages.siosocks
python310Packages.sunpy
python39Packages.aioftp
python39Packages.parfive
python39Packages.siosocks
python39Packages.sunpy


Cluster a GeoJSON Source component

Is it possible to generate clusters / grouping from a <Source> component, like this example by the official mapbox documentation? https://www.mapbox.com/mapbox-gl-js/example/cluster/
I can only figure out how to make clusters using <Marker> and <Cluster>
Is there a way I can pass cluster, clusterMaxZoom and clusterRadius to a <Source> component.
I know that <Layer> has a layerOptions prop, that will be passed directly to the component, is there a way I do the same with <Source>, like the example below?
<Source cluster={true} clusterMaxZoom={14} clusterRadius={50} />

This is what I have so far (without clustering)
return (

        <Source
          id='spots_source'
          geoJsonSource={{
            type: 'geojson',
            data: this.props.spots
          }}
          circlePaint={{
            'circle-color': 'green',
            'circle-radius': 10
          }} />
        <Layer
          id='spots_layer'
          sourceId='spots_source'
          paint={{
            'circle-color': 'green',
            'circle-radius': 10
          }}
          type='circle' />

    )

Hey @viktorstrate, you can cluster Source and Layer components yes, you will need to play with layerOptions and sourceOptions props to match the implementation of this example on MapboxGL assuming that each addLayer is a new Layer component. Don't hesitate to share your implementation I can help you if needed too.

Thank you for your response @alex3165 , I managed to get it to work, but I had to change <Source> to <GeoJSONLayer>, because <Source> doesn't have a sourceOptions prop. I don't know if there is any reason for that?
Nevermind, it isn't a problem in my case, because the source is already formatted as GeoJSON.
This is what I came up with.
return (

    <GeoJSONLayer
      id='source_id'
      data={this.props.geoJson}
      sourceOptions={{
        cluster: true,
        clusterMaxZoom: 14,
        clusterRadius: 50
      }}
    />
    // Layer of clustered spots
    <Layer
      id='cluster_layer'
      sourceId='source_id'
      layerOptions={{
        filter: [
          'has', 'point_count'
        ]
      }}
      paint={{
        'circle-color': {
          property: 'point_count',
          type: 'interval',
          stops: [
            [0, '#51bbd6'],
            [100, '#f1f075'],
            [750, '#f28cb1']
          ]
        },
        'circle-radius': {
          property: 'point_count',
          type: 'interval',
          stops: [
            [0, 20],
            [100, 30],
            [750, 40]
          ]
        }
      }}
      type='circle'
    />
    // Layer of unclustered spots
    <Layer
      id='unclustered_layer'
      sourceId='source_id'
      layerOptions={{
        filter: [
          '!has', 'point_count'
        ]
      }}
      paint={{
        'circle-color': 'green',
        'circle-radius': 10
      }}
      type='circle' />

)


When using Branches: and PR is merged, rebase detection can fail and cause pr to be re-created

Upload change from branch A but target other branch B with Branches:. When change merges and you fetch B again, revup continues to upload the PR to B, does the cherry-pick, finds that it succeeds and produces an empty commit, then finds the patch-id of the empty commit, compares against original, and mistakenly finds that it changed and thus re-uploads.

this seems to only happen for relative chains that get targeted to a different branch. possibly only when the relative change forces a push of the parent


Support pythonPath from user input saved in workspace setting with ${workspaceFolder}

is this implemented? If so, the documentation on the webpage is outdated


AAB export fails

Godot version:
3.3.stable
OS/device including version:
Linux 64 bit (GitHub actions )
Issue description:
Export with AAB and custom export template fails with error Thread exit status: 126
Steps to reproduce:
Open the editor
Download android custom build
Activate AAB and custom build
Export the project
Reproduction project:
Crystal Bit Godot Game Template (before exporting for android follow the steps to reproduce)

I've tested this with both 3.3.stable and 3.3.2.stable, and I'm unable to reproduce the reported error. It builds a perfectly good .aab file.
The exit code 126 suggests that you don't have execute permissions on the gradlew file in the android/build directory. Check the execute permissions or simply delete the android folder and reinstall the Android Build Template.

Closing due to inability to reproduce the issue and lack of responses. @Andrea-Miele Feel free to re-open if this is still an issue.


Inability to eat

Steps to Reproduce (as best as you can)
During use, you can find that it never eats, even if its hunger value is very low.
Expected Behavior
It never eats
Actual Behavior
It never eats, even if its health is low
Crashlogs and Screenshots (if applicable)
(you may drag + drop text logs and images here, thanks GitHub)
Other mods (if applicable)
Discord username (if you want updates)
Developer Notes (leave this blank)
Difficulty: __
Estimated Time Required: __
Once development starts.

I thought this was fixed. Did you check hunger settings to make sure they are set properly? Or are you using default values?


class_generator: Get metadta from spec - 2058

[Auto generated]
Number: [#2058]

openshift-python-wrapper[pull_request][5d63-11ef-9b51-c99e30bcbcf3][PR 2058]: Closing issue for PR: class_generator: Get metadta from spec.
PR was closed.


Do not download any videos vimeo.com.

Do not download any videos vimeo.com. ""ERROR: No video formats found;"

Duplicate of #7460.


List the JVM-only extensions in the docs

A followup of https://github.com/apache/camel-quarkus/pull/895

I think we should not use the term JVM only but we should probably document what is the support level for the different targets i.e. a table like

Compilation Target
Support Level

JVM
supported

Native
experimental

I find the data model useful, let's discuss how we could present it.
I have not planned to generate a per-extension doc page, so the only place where we could present this is the list of extensions: https://camel.apache.org/camel-quarkus/latest/list-of-camel-quarkus-extensions.html
Adding two columns sounds a bit too much. How about one column?
Current

Component
Since
Description

ActiveMQ (camel-quarkus-activemq)activemq:destinationType:destinationName
1.0.0-M5
The activemq component allows messages to be sent to (or consumed from) Apache ActiveMQ. This component extends the Camel JMS component.

Proposed:

Component
Target Level
Since
Description

ActiveMQ (camel-quarkus-activemq)activemq:destinationType:destinationName
Native stable
1.0.0-M5
The activemq component allows messages to be sent to (or consumed from) Apache ActiveMQ. This component extends the Camel JMS component.

Where the "Target Level" values could wrap under each other so that they take less horizontal space.
Btw. I find stable/preview better than supported/experimental because they are shorter.


publishing messages

I just pushed an updated version of the CLI. I'd like to raise two issues;
First; Right now publish method does not allow extra arguments.
While this might be the desired use. I think it should not fail to publish, rather

either mark the extra columns and publish, or
split these columns, publish the fixed template part, and report back the extra fields to the user.
Manipulations in the publish class can be made see here

Second, I think the snews_pt is meant for users to interact with the system without having to deal with any backend tools. The publishing tools are already nice and usable, however, we should also carry the means to subscribe to alert channel, and I think this subscription should also allow downloading the received alerts in json or some other format. I don't think users would monitor the terminal all the time.
I also would like to suggest starting using python config files for broker, channel, token, etc (basically replacing the env file). This way later, we can either ask users to put their experiments once in the config file or try to fetch it from hop.auth. I can work on that if agreed.

About allowing extra arguments without crashing we can refer to this

About allowing extra arguments without crashing we can refer to this

fixed.


[doc] conda export instructions reference the root environment

The instructions for exporting a conda environment state that the user should

use conda env export -n root to print the environment

But the "user" dependencies (i.e. those not related to Binder) seem to be installed in the notebook environment (or maybe any environment referenced by $CONDA_DEFAULT_ENV?)
Should the export instructions be updated to print the dependencies for the $CONDA_DEFAULT_ENV environment?

Thanks for finding the outdated docs.
The right answer is a bit tricky. When a repository requests version 3 of Python there is only one environment in which the user's dependencies and the notebook server are. When the repo requests Python 2 there are two environments: one for the notebook and one for the kernel (this is where the user dependencies go).
This means that the command to run is conda env export -p $KERNEL_PYTHON_PREFIX, which should always work (I think).


Need to be update cakephp-cart-plugin!!!

The plugin cakephp-cart-plugin is good, i'm very excited if it could be upgrade ASAP.

You should be opening an issue on that plugin's repo not here.


how to use initializeMiddleware of oas tools to add customized properties to the http request?

I am trying to replace the existing swagger tools in my project with oas-tools.
source code shown as follows
const express = require('express');
const swaggerTools = require('swagger-tools');
const oasTools = require('oas-tools');
const { errorHandler } = require('errorHandlerPackage');

/**
 * takes paths to controllers folder and swagger route config file and returns swagger router
 * @method swaggerMiddleware
 * @param {config.swaggerDoc} - path to the swagger api spec json/yaml
 * @param {config.controllers} - path to the folder containing the controllers associated
 *                                 to above swagger api spec json/yaml
 * @param {config.useOasTools} - bool, optional, a flag to determine if oas-tools is used or not
 * @returns swagger router associated to the paths in the swaggerDoc
 */
const swaggerRouterFactory = ({ controllers, swaggerDoc, useOasTools }) => {
    const router = express.Router({ mergeParams: true });
    const options = {
        controllers,
        useStubs: true
    };
    const _addCustomizedPropToRequest = () => {
        router.use((req, res, next) => {
            const { a, b } = req.headers;
            req.a = a;
            req.b = b;
            next();
        });
    }
    const _addSwaggerSettings = (middleware) => {
        router.use(middleware.swaggerMetadata());
        router.use(middleware.swaggerValidator());
        router.use(middleware.swaggerRouter(options));
        router.use(middleware.swaggerUi());
        router.use(errorHandler);
    }
    if (useOasTools) {
        oasTools.configure({
            controllers,
            strict: true,
        })
        oasTools.initializeMiddleware(swaggerDoc, router, (middleware) => {
            oasTools.initializeMiddleware(swaggerDoc, router, (middleware) => _addCustomizedPropToRequest());
            _addSwaggerSettings(middleware);
        });
        return router;
    }

    swaggerTools.initializeMiddleware(swaggerDoc, (middleware) => {
        swaggerTools.initializeMiddleware(swaggerDoc, (middleware) => _addCustomizedPropToRequest());
        _addSwaggerSettings(middleware);
    });
    return router;
};

module.exports = swaggerRouterFactory;

I can get the req.a and the req.b when I called my API through swagger-tools, but when I tried to call the API through oas-tools, I got undefined for the a and b. According to the oas-tools doc, to migrate from swagger-tools to oas-tools, I only need to pass the app as the second parameter to use the initializeMiddleware function. But this seems doesn't work for the _addCustomizedPropToRequest, the router.use(middleware.swaggerRouter(options)) works well.
Could anyone tell me what have I missed?

Hello, what are you trying to do? I can see you have created a factory that returns the express router with the middleware registered depending on the useOasTools option. I assume you use that router in other file to start a server.
The initializeMiddleware() function is useful when you want to migrate without modifying almost anything in the code, but with a couple of lines you can initialize it normally.
Besides, a new version has come out recently, which may suit your interests when initializing an oas-tools server. I leave you here a minimal initialization example, using the same options you are setting for oas-tools:
const oasTools = require('@oas-tools/core'); // The new version has been renamed

const cfg = {
    middleware: {
        oasFile: swaggerDoc,
        router: { controllers: controllers },
        validator: { strict: true }
     }
 }
oasTools.initialize(router, cfg).then(() => {
   _addCustomizedPropToRequest();
  /* Initialize your server here */
 });

Take into account that the initialize function is asyncronous and if you try to return the router right after the oas-tools initialization it may not have all the routes registered. The same happens to initializeMiddleware( ) function in your code, it is asyncronous and therefore the _addCustomizedPropToRequest( ) is not being called before the server initialization. If you want to return the express router, make the parent function async and use await on the oas-tools initialization, then you can execute the rest of the code sequentally.


The Duke of the Evals

Three Evals for the Elven-kings under the sky,
Seven for the Dwarf-lords in their halls of stone,
Nine for Mortal Men doomed to die,
One for the Pull Requester on his dark fork
In the Land of Klasa where the Shadows lie.
One Eval to rule them all, One Eval to find them,
One Eval to bring them all and in the darkness bind them
In the Land of Klasa where the Shadows lie.
This is not that Eval, but it's still a good one.
New features:

Know the exact type of what you evaled

Notes when a promise has been awaited, and what its resolved value is

Know how long the eval took to execute

Unit may be seconds, milliseconds, or microseconds, depending on the scale of the duration, for enhanced readability
Shows time taken to await promises separately

If the output is too long to send (>2000 chars), it is uploaded as a file

Fixes:

The eval command silently erring if the output is more than 2000 characters

Come to think of it, getNiceDuration and roundTo3 should probably be moved to util, and reused for the ping command.

Refactor and added timeout for promises coming soon (see Pieces PR)

I am not completely happy with getTypeStr function. I am not entirely sure exactly what I am looking for, except a more professional type? Something closer to Promise<string[]> sort of syntax, at the same time not making the command over the top (it's kinda getting that way) Perhaps, putting that function in util. I need to do more research.

Oh, good idea, on the type format. I'm not sure there'd be much use for it outside eval, though.

@bdistin I made the requested changes. I just need to move some of the functions to util yet.

Discussed moving much of this code to util in chat. (typings check, pretty duration, ect)

@bdistin tested in fresh bot, and confirmed working.
https://user-images.githubusercontent.com/25398066/31800479-305f6c9c-b50f-11e7-9992-ec422210f81c.png
https://user-images.githubusercontent.com/25398066/31800480-36ce7ee2-b50f-11e7-90f6-a09d6dea87dc.png
https://user-images.githubusercontent.com/25398066/31800483-3cd250d4-b50f-11e7-962c-c0ecf40fa007.png
https://user-images.githubusercontent.com/25398066/31800489-44640cc0-b50f-11e7-87b3-e817b730e706.png
https://user-images.githubusercontent.com/25398066/31800493-49e6b1c0-b50f-11e7-9404-5f550dba0987.png
https://user-images.githubusercontent.com/25398066/31800509-5d5229b0-b50f-11e7-988f-21e995d86dab.png

Optional parameters are not counted in function arity, due to them not being included in function.length.

I still need to change to using the Stopwatch class. I'm also not sure what to do about the complexity warning in Util.getDeepType. I guess I could separate it out into functions to handle values-only objects, key&value objects, and functions.
Also, sorry, looks like I accidentally leaked one of my branches into another again. I thought I hard reset that commit, but I guess I didn't go back far enough.

I'll look into it when I get a chance. I did have a class, but I changed it because I was able to work out the logic better that way.
I use JSON.parse(JSON.stringify()) at one point to clone a deepType. I'm not sure if returning b directly, without cloning, could have any side effects (which is why I cloned it in the first place). If I still use JSON to clone, I'll have to make custom JSON stringification and instantiation for a DeepType class. Unless I make a recursive method to clone, but that's why I used JSON, for simplicity.
Or maybe I don't have to clone at all, but I was worried about not finding odd edge cases.

Suggestion: add a hastebin flag

@MrJacz That won't be included in the core version, but the klasa-pieces version.

Oh i see...

This PR should target the v0.5.0-dev branch now. Feel free to change it when you're ready.

On the 7th day of christmas, my github gave to me, 7 merge conflicts, 6 Travis Builds, 5 Broken Languages, 4 requested changes, 3 dirigeant devs, 2 discord frameworks, 1 Merged PR.
 Might be easier to start a new branch, based on latest master, And copy your eval/util changes from here to the new branch, then open a new pr from the new branch...

Hutch's other PR will have the same "fucked up-ness" as this PR as well

As discussed in the server, I will copy this to a new branch


How to see serverless function log

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

Expected Behaviour

See function log somewhere.
Current Behaviour

Can't see function log in Nuclio dashboard. Only build log is provided.
Possible Solution

Steps to Reproduce (for bugs)

No steps.
Context

Both Nuclio and CVAT documentation is vague about logging for serverless function.
 No
Operating System and version (e.g. Linux, Windows, MacOS): Lubuntu 20.04
Code example or link to GitHub repo or gist to reproduce problem: Not needed
Other diagnostic information / logs: None

Next steps
You may join our Gitter channel for community support.

@nvmnghia , thanks for the report. You can use docker logs <container for a function>. To understand which containers you have run docker ps.
Does it answer the question?

@nmanovic I've just figured it out, thanks for your support. I thought I had to install Kibana or something just to see the log.


Store emails in all lowercase

Added simple zod transform to store all emails in lowercase to prevent duplicate emails with different casing as discussed in Issue #20

Already resolved


Realise end to end  data pipeline - POC

Realise End to End POC – From Data upload to Data View via Athena

Request a presigned URL for a data file

Upload that data to s3 using the presigned URL (Murdo has some code which can help with this)

Check that the glue job which transforms the data and registers it on glue is triggered

The data uploaded should then be accessible as part of the glue catalog

Check the data is queryable via Athena

If any part of the end to end pipeline is broken, fix it so the end to end flow works.

Hey team! Please add your planning poker estimate with Zenhub @murdo-moj @hemeshpatel-moj @bogdan-mania-moj @LavMatt

https://github.com/ministryofjustice/modernisation-platform-environments/pull/2476


ModuleInterface: Wrap synthesized extensions in swiftinterfaces with feature guards

When printing synthesized extensions, we need to be sure to guard them with required features if applicable. Not doing so can result in broken interfaces that do not typecheck because, for instance, a conformance can refer to a nominal type that is only declared when certain features are enabled.
Also, fix a typo where #elsif was printed into interfaces instead of #elseif.
Resolves rdar://91509673

@rjmccall I think this may have regressed with https://github.com/apple/swift/pull/41399, would you mind reviewing?

@swift-ci please test

@swift-ci please test

@swift-ci please test Linux

@swift-ci please test

@swift-ci please test


Emmet: "Wrap Individual Lines" wraps once instead of for each line

First-time caller, long-time user. 😄
Running into an issue where it seems like Emmet's "Wrap Individual Lines" feature may not be functioning as expected -- it appears to wrap a block of text rather than the actual lines, in the exact same way that "Wrap with Abbreviation" currently works.
I think (but am not 100%) that my understanding of the expected functionality is confirmed by #33703 and #38338.
Animated Reproduction

Steps to Reproduce

Take a selection that's wrapped in a <ul> and contains multiple lines (e.g. to add li to)
Highlight the lines that you'd like to individually wrap with li
Select the "Wrap Individual Lines" emmet functionality from the command palette
Enter li and hit enter

Expected: Each individual line is wrapped with <li>
Actual: Only one <li> wrapping is added
Versioning / Installs

VSCode Version: Code 1.18.0 (dcee2202709a4f223185514b9275aa4229841aa7, 2017-11-08T21:22:49.932Z)
OS Version: Windows_NT x64 10.0.15063
Extensions:

Extension
Author (truncated)
Version

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

jshint
dba
0.10.15

gitlens
eam
6.1.0

Ionide-fsharp
Ion
3.12.2

azure-account
ms-
0.2.2

csharp
ms-
1.13.1

PowerShell
ms-
1.5.0

debugger-for-chrome
msj
3.5.0

vscode-docker
Pet
0.0.22

code-spell-checker
str
1.4.12

quokka-vscode
Wal
1.0.79

(1 theme extensions excluded)

I found the tests are for the Emmet functionality; haven't pulled / built the source before but if this needs confirmation I can try to get a failing test in place.

Shouldn't it be li* instead of li?

@usernamehw that may be the case and I'll try it. My understanding was that if "wrap with abbreviation" allowed me to wrap an overall selection using li, then wrap individual lines would apply that same behavior to each individual line.
Not in front of vs code now but I'll check that ASAP. Do you happen to have a reference as to why I should expect li* to work but not li in this case? I dug for a little bit but didn't see anything.

Seems reasonable. Perhaps, it's using the same parser.
https://github.com/Microsoft/vscode/issues/31814#issuecomment-319569894
Atom and Sublime Text handles this situation according to Emmet Docs. Still wondering if in vscode this is considered a workaround or a permanent solution.

@usernamehw is right. For wrapping individual lines you need to provide li* instead of li
@SeanKilleen https://docs.emmet.io/actions/wrap-with-abbreviation/#wrapping-individual-lines is the Emmet documentation for the "wrap individual lines" feature.
The Emmet library when asked to wrap given text with an abbreviation uses the * to make the call if the whole text should be wrapped in the abbreviation or the repeater should be used to wrap individual lines.
Hope this helps.

@ramya-rao-a it totally does help, thanks! Not sure how I missed it in the docs the first time around. Much appreciated!

No problem, Happy Coding!

May I ask what is the point of a separate command (Wrap Individual Lines with Abbreviation) if you still need to include the asterisk?

@KucharczykL
The reason for a separate command is described in https://github.com/Microsoft/vscode/issues/31814#issuecomment-319569894
For wrapping individual lines, the lines are passed to the emmet module as an array. See text under expand options
For the simple wrap command, in order to support multi cursor well (your cursors can be on lines that have totally different text, and the wrap command will work just fine), we pass $TM_SELECTED_TEXT to the emmet module and not the actual text.
PRs are welcome, if anyone wants to give combining the 2 commands a try.


Schema upgrade demo

TBD

I'd advise not to try to introduce "locked / dead" document concepts. No matter how you do it, it will have gaps, unless you bake these concepts into core of runtime. For example, any client that reconnects always sends pending ops no matter what the state of the document is. Even without disconnects, any client who checks for such state will have a race the next moment as such state can change unless you use proposal mechanisms (instead tasks). And with proposals, you have other side of the problem - if client proposing lock dies, someone needs to clear the lock. It will be a mess with a bunch of bugs one way or another.
Given these complexities, I'd advice to just implement export functionality without any locking.
I personally do not see a reason for doing file lock. If you really need it, I would rather see that kind of functionality implemented at storage level, not fluid.
Note that we do not have notion of immutable document revisions, so any async operations need to also be wrapped with ops pausing to avoid document state changing underneath you (while export is running).

It will probably be easiest to have the design discussion on #9049 which tracks this more broadly.  No matter what tools/techniques/design we use we'll need a demo, so we should get this checked in to iterate upon.

@ChumpChief, are you going to make this example work correctly in presence of connectivity issues? For example, volunteerForDestruction() will throw if connection is lost right before that.
People will be copying our examples; they should be demonstration of how to write correct code.

@ChumpChief, are you going to make this example work correctly in presence of connectivity issues? For example, volunteerForDestruction() will throw if connection is lost right before that.

Yes, I have it noted in #9717.


rollouts cli: use "default" value for namespace and minor cleanups

This PR addresses the review comments from the PR https://github.com/GoogleContainerTools/kpt/pull/3807

Can we also update the PR title to be something a bit more descriptive? This will end up in the release notes, but it is not very informative.

Can we also update the PR title to be something a bit more descriptive? This will end up in the release notes, but it is not very informative.

Done.


Biundo/kafka

@mkaufmaner
Forgive this clumsy pull request.  I didn't mean to drag in all the commits since you created your branch. I'm not a super git expert, but if you welcome the suggestions and would prefer I try to package them up as a diff only against your branch, I'll go back and do that.
Also, forgive me just jumping in with suggestions... I've been doing a lot of work on the Nest docs -- both some original writing, and a lot of stylistic cleanup.  I thought I'd offer my input if you would like it.
In addition to the PR, I noticed a couple of other things in reading the docs.  Here are those observations:

The second code example (approx. line 106) uses the type ClientKafka.  I wondered whether you might have meant to say KafkaClient here?
In the text just below that same code example, it says "There is a small difference to the previous examples" and mentions ClientProxy, but I didn't see any other references to ClientProxy, so I wonder if this might be confusing?
In the section describing how partitions are rebalanced, the sentence However, using this partitioning method, a new consumer could join the consumer group and fall where within the sorted list of consumer names because the consumer name is randomly set on application launch. was a little confusing to me.  I wasn't sure what the fall where within part was referring to.

@johnbiundo No need for apologies, your input and changes are appreciated!  I merged your changes and elaborated further on the Message Pattern.  Also, all references to KafkaClient were changed to ClientKafka, was a bit clumsy there.  Too much context switching on my side as of recent so thanks again for the review!

Cool, glad it helped!  Looking forward to using this feature.  Very welcome addition to Nest!


Validating biomaterials are linked to upstream biomaterials in ingest

As a wrangler, I want to be able to validate that my cell suspensions are linked to upstream biomaterials with species information so that CGMs display properly in the browser.
There are multiple paths which are covered in the slack conversation below, but the generally agreed method is to do this by creating ingest-graph-validator validation rules
** Acceptance Criteria / Definition of Done **

Given a project in ingest-prod that has a cell suspension that is:

linked to a file
not linked to an upstream specimen

When we try to validate this in the ingest-graph-validator
It outputs an error that the cell suspension is not linked to an upstream biomaterial

This is related to: https://embl-ebi-ait.slack.com/archives/C9XD6L0AD/p1630917382029200?thread_ts=1630713676.022700&cid=C9XD6L0AD
There are a couple of scoping questions with whether this should be extended to cover more cases (not only cell suspensions). This will be determined when this ticket gets picked up.
There is a lot of detail in slack here: https://embl-ebi-ait.slack.com/archives/C016R78CDV1/p1630923788142400

See also: https://app.zenhub.com/workspaces/operations-5fa2d8f2df78bb000f7fb2b5/issues/ebi-ait/hca-ebi-wrangler-central/420
These projects each demonstrate problems in the browser due to missing links as described above; once this user story is complete, we would expect to be able to detect these projects as being in error during submission


Workaround for the webview positioning bug

This is a small, hacky fix for #110450.
The webview can often end up in the incorrect position, because it's position is computed before the animation of the underlying view is finished, which results in the webview ending up where the animation started, not where it finished.
See a demo of the issue here:

A good solution would involve either animating the overlay webview in the same way (tricky since we don't have information as to where the webview should end up) or moving the webview to be a child of the view container, so it's position is updated automatically.
As a more temporary fix, this CL adds a hack that simply asks the webview position to be updated every 40ms (25fps) for the next 200ms (length of the animation) which will cause the webview to "appear" to animate correctly into the correct position.
The works smoothly for me whilst testing, but there is a chance that it might be a bit slow on older hardware, however, even in that case, it would still be better than the current system which leaves the webview in the wrong place.
This should not be considered a fix for #110450, but will at least improve the situation and will never be worse than the current situation.

Hi, @mjbvz - just a quick bump for this PR - was wondering if you might have some time to look into this?

Sorry for the delay
This looks like a pretty hacky/brittle fix. I'm not sure what the proper fix is here but I don't think we can check this in as is

Hi,
Yeah, it's definitely not clean, but we have been running it for a few months without an issues.
There is a slightly less brittle version which moves it once after the animation is complete, but this version "appears" smoother to the user. I would suggest that whilst it isn't pretty, it is better than leaving the code base as-is since if a user ends up in a situation where this bug occurs there is no workaround and no way out of it, other than reloading vscode each time you want to expand or collapse the view.
In terms of the best solution, the cleanest option may be to remove the floating iframes used by webviews and instead position them as child elements of the view. However, I am not sure if there is historically a reason why they are floating instead of being children.
The other option could be to somehow share the animation with the webview before hand, rather than reactively moving it as we do currently. This is something I am happy to look into further, but I would rather know what kind of solutions you'd be interested before investing time in it.

Yes the floating frames are required. They let us avoid having the iframes be re-parented, which destroys the frame contents

@a-stewart @mjbvz  Since a simple resize / refresh fixes the position, can it not be triggered automatically once after an expansion/contraction is finished? (200 ms after an expand/contract)
This would not animate smoothly, but at least when finished animating, the position would be corrected abruptly and somehow at least it would be somewhat fixed!
Just wondering... Thanks!
(Sorry not familiar enough yet with vscode's codebase to provide a pull request)

Since a simple resize / refresh fixes the position, can it not be triggered automatically once after an expansion/contraction is finished? (200 ms after an expand/contract)

Yes, that is what this PR did (I then updated it to do the same refresh a few times so it would "appear" to animate).
Rather than doing this (as it currently is):
			for (let i = 40; i <= 240; i += 20) {
				setTimeout(() => {
					this.layoutWebviewOverElement(element, dimension, /*animated*/ false);
				}, i);
			}

We can simply do:
			setTimeout(() => {
				this.layoutWebviewOverElement(element, dimension, /*animated*/ false);
			}, 200);

This will cause a reposition to be triggered 200ms later (after the animation is complete).

Yes I like that second approach better, even if it's still a hack. Can you update the PR to do that instead (but also make to cancel the timeout if the webview view is closed)

@mjbvz Thanks for your consideration and approval of this suggestion! I'll let @a-stewart do the correction as I'm not knowledgable enough in vscode's code base to do so myself!
Thanks again! :)

Updated as suggested.
This will result in there being a single "correction" made after the animation. So the underlying view and headers will move smoothly to the new position with the webview remaining where it is, and then once the animation is complete, the webview will jump in one step to the new location of the view.


Add support for Vessel

Post an example URL.

Sorry, here you go: https://www.vessel.com/videos/JYZEYDYx0

Thank you for the report. Support for vessel.com has been added and should be available in the next release of youtube-dl. Note that the provided URL requires subscription, so, assuming you are a subscriber, you would need to specify your Vessel username and password to youtube-dl in order to download it.

Thank you!


Migrate to context 1.0

Todo

[x] Basic resume and yield facilities

[x] block_with mechanism

[x] ~Move the callback function of Coroutine onto its own stack.~ FnBox() Is being used for now since alloca() is hard and generics lead to code bloat.

[x] Move the block_with callback out of its stack

[x] Test on major platforms (x86, x86_64 / Linux, OS X, Windows (MSVC, MinGW32, Cygwin)) - NOTE: Is this necessary though? We might want to verify the functionality of context-rs instead.

[x] Test with Valgrind to fix #15

[x] Cannot run on Linux x86. It crashes when the callback() in coroutine_initialize returns.

[ ] Squash all commits before merging? Yes/No? (optionally)

Issue: #40

Don't merge this until all dust is settle.

I think all the necessary job to make coio run with context-rs v1.0 is already done.
The crash on x86 platform may related to a bug in context-rs v1.0, so it won't be solve here.
We would squash all commits into one before we actually merge it.


Updating tox.ini to latest Django versions, updated docs for JSONField

Most importantly, the 1.7 references were to the 'b3' prelease.

Thanks !


Link for ASP.NET Core SDK is old

Current link is pointing https://github.com/Microsoft/ApplicationInsights-aspnetcore, but it seems to be moved to https://github.com/Microsoft/ApplicationInsights-dotnet.

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

ID: 401d2997-0fbd-7966-8996-edbaab1819ff
Version Independent ID: c3ee3318-4c69-8ded-a8d5-5059d699351b
Content: Application Insights API for custom events and metrics - Azure Monitor
Content Source: articles/azure-monitor/app/api-custom-events-metrics.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@NewGyu Thanks for the question! We're investigating this and will get back to you shortly.

@mrbullwinkle Should/Can this be referenced just yet? I gather from this issue that work is in progress.

@BhargaviAnnadevara-MSFT, @NewGyu is correct we should swap the links, but thank you so much for double-checking to confirm.
I have updated the doc and the changes are merged internally. The changes will go-live in the public repo between 10 AM - 11 AM (UTC-7).

#assign:mrbullwinkle

#please-close

@mrbullwinkle Sure, thanks for the updates!


findCustomScalarOption but for repeated options?

It is valid to define a repeated options for a message such as:
extend google.protobuf.MessageOptions {
    repeated string bar = 10001;
}

message FooMessage {
   option(bar) = "hello";
   option(bar) = "world;
   ...
}

However, the function findCustomScalarOption could be used only to retrieve the first option since it was implemented as:
function createBinaryReader(desc, extensionNumber) {
    const opt = desc.proto.options;
    let reader = undefined;
    if (opt !== undefined) {
        const unknownFields = protobuf_1.proto3.bin.listUnknownFields(opt);
        /*
           This `unknownFields` contains all the repeated options attached to a message, with a same number.
           But only the first matched one will be returned
        */
        const field = unknownFields.find((f) => f.no === extensionNumber);
        if (field) {
            reader = new protobuf_1.BinaryReader(field.data);
        }
    }
    return reader;
}

How about to provide a new function, maybe named findCustomRepeatedOptions, to retrieve all the matched options?
For example:
function createRepeatedBinaryReaders(desc, extensionNumber) {
  const opt = desc.proto.options;
  let readers = undefined;
  if (opt !== undefined) {
    const unknownFields = protobuf_1.proto3.bin.listUnknownFields(opt);
    readers = unknownFields
      .filter((f) => f.no === extensionNumber)
      .map(f => new protobuf_1.BinaryReader(field.data))
  }
  return readers;
}

Hi @Jayatubi. You can retrieve repeated options using a message wrapper and the findCustomMessageOption function. For example:
// custom_options.proto
extend google.protobuf.MethodOptions {
  optional FooOptions foo_method_option = 50007;
}

message FooOptions {
  repeated string many = 1;
}

// foo_service.proto
import "custom_options.proto";

service FooService {
  rpc Get(GetRequest) returns (GetResponse) {
    option (foo_method_option) = {
        many: ["a", "b", "c"],
    };
  }
}

You can retrieve the options using a generated type by first generating the file which defines the custom option type. Then, import and pass this type to the findCustomMessageOption function.
import { FooOptions } from "./gen/proto/custom_options_pb.js";

const option = findCustomMessageOption(method, 50007, FooOptions)

console.log(option);
/*
 * {
 *     many: ["a", "b", "c"],
 * }
 */

For more info, check out our plugin docs

Hi @Jayatubi. You can retrieve repeated options using a message wrapper and the findCustomMessageOption function. For example:
// custom_options.proto
extend google.protobuf.MethodOptions {
  optional FooOptions foo_method_option = 50007;
}

message FooOptions {
  repeated string many = 1;
}

// foo_service.proto
import "custom_options.proto";

service FooService {
  rpc Get(GetRequest) returns (GetResponse) {
    option (foo_method_option) = {
        many: ["a", "b", "c"],
    };
  }
}

You can retrieve the options using a generated type by first generating the file which defines the custom option type. Then, import and pass this type to the findCustomMessageOption function.
import { FooOptions } from "./gen/proto/custom_options_pb.js";

const option = findCustomMessageOption(method, 50007, FooOptions)

console.log(option);
/*
 * {
 *     many: ["a", "b", "c"],
 * }
 */

For more info, check out our plugin docs

The wrapper message option looks like but I think a plain repeated options should also be useful.
No need to change any of current interfaces. Just add a new one would be better.

Yeah, understood. We actually explicitly opted against this for now to keep the API simpler and feel that the message wrapper is a viable alternative. Going to close this for now, since I don't see us implementing this anytime soon, but we will definitely reopen if we decide to revisit.

@Jayatubi, the next release will support extensions. They can be used to retrieve repeated custom options as well. See https://github.com/bufbuild/protobuf-es/pull/666 and https://github.com/bufbuild/protobuf-es/pull/669.


Component props are not correctly updated

Version
1.0.0-beta.30
Reproduction link
https://github.com/JFGHT/vue-test
Steps to reproduce
yarn
yarn test:unit
What is expected?
Tests should pass.
What is actually happening?
Test do not pass.

This test was passing in beta 29.

Hey mate, I dont see in that test you setting props.
Second, why accessing raw DOM nodes instead of using the test utils helpers?
Third the library is now async, so you should await wrapper.vm.$nextTick() after changes, so the DOM re-renders.
Try that and let us know.

Thanks. The awaiter worked. I'm also introducing the utils helpers now.
Closing.


[USERSNAP] Unable to register

Taken at: https://gov.tools/dashboard
Fields:

Add a comment: Unable to register

Browser: Chrome 129 (Windows 10)
Screen size: 1920x1080
Open #141 in Usersnap
Powered by Usersnap.

This doesnt have enough details. Any more info/screenshot in usersnap @l-br1 @kickloop ?

Closed as it doenst have sufficient information and is too vague.


minimal interactive shell

User should be able to prompt an interactive shell with at least one command or check the status of a program

requires #25


remote sync controller

Some logic that handles checking all remote repositories, merges the info and updates the contact store

what do you mean by "checking all the remote repositories"? is that just the database locations?

yes exactly. I'll improve the description. A basic implementation is already done. Needs some testing though before closing the issue. And then we need some sort of background service that triggers the sync controller now and then.


handle mouse on decorations

handles mouse actions inside decorations, to allow further decoration integration and avoid future duplicated code
don't think will cause any new issues since it mostly moves the code

decided to remove onEndDragWindow final nesting with grouped windows
now each decoration can do what it wishes when a window gets dragged onto it
haven't found any issues yet, but probably needs more testing


Yaml mistaken for Markdown

As the title states pastey keeps thinking my yaml is markdown. Is there something I can put to make it detect it properly?

I think this may be because of the current version of guesslang in the requirements.txt. Currently it's set to version 2.0.1, while 2.2.1 is the latest. I'm not sure when they added YAML support (among several other languages), but it's not available in v2.0.1, but is in v2.2.1.


class Configure not found

Fatal Error (1): Class 'Burzum\UserTools\Model\Configure' not found in [..\vendor\burzum\cakephp-user-tools\src\Model\UserValidationTrait.php, line 203]

Coverage remained the same at 43.051% when pulling 8e4298cf3c0033867da4d96a72e9c3f3f7d180ff on Adnan0703:master into b7b4caccc5c01430feb2c594a67848f22bb599ae on burzum:develop.

This has been fixed 28 days ago?
https://github.com/burzum/cakephp-user-tools/commit/76edc7033df868536c1855787d90c7dce86ad0d7

I've tagged 1.0.6 make sure your composer file is set up correctly to get that updated. It includes the fix.


Falling Balls iOS crash

Compose 1.4.0, Kotlin 1.8.20, Compose Multiplatform repo commit 4c225aa, iPhone 11 simulator

run examples/falling-balls on iOS
click "start"
wait 4 min
Crash iOS 2023-04-13.txt

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Update the repo with changes brought by Transformers 4.19.1

What does this PR do?

Make the repo up to date with Transformers 4.19.1.
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

Regis, what's the test result? can we have sth like shared document to track test result for each release?

I'm going to launch the regression tests manually on this branch to be sure that we keep the same performance. You'll be able to see if these tests have passed here (in the "Actions" tab).

@libinta You can see here that all the regression tests passed.

@regisss is albert xxl running over saturday? what's the result?

The CI run of Saturday skipped all regression tests since examples are not up to date in the main branch (checking if examples are up to date is the first test and if it fails all the following tests are skipped). But I ran it manually and it gave me the exact same results as before. Actually you can check it in the log files I sent you on Slack.


Containerize using Docker

This PR adds a basic Dockerfile to containerize Slashboard-pulsar.
One important thing to note is that the key is not generated automatically using this setup, it must be entered as an environment variable (PULSAR_AUTH_KEY currently) at container startup.
I am happy to make any changes necessary to make this work for the project.

I have improved a couple of things :

the key is now generated when the container is launched for the first time, and will be kept until deletion
the docker image is automatically deployed to Docker Hub on push for the main branch

However, a big issue remains : once run in the container instance, I have no idea how to allow node to access hardware data from the actual machine and not the container instance.
Any ideas ?

All of the CI/CD stuff looks good, but the changes to docker_init.sh should be reversed in favor of a different solution.
The reason it was originally setup to be entirely user defined was because key.txt resets to the default value every time the container starts. This is due to how containers work and is not a problem specific to this setup. A potential solution that ensures that the key is still generated by Pulsar is to allow users to generate a key using the docker container, which they then can put in the environment variable by themselves. An example of the command to do this from the user's side would be docker run slashboard-pulsar genkey, which would then output the key for the user to copy and paste. To implement this, docker_init.sh would check for the genkey argument, and if it was present, output a new key to STDOUT and exit.
As for the hardware data issue, my Linux machine reports everything just fine. What's your testing environment like?

Actually, this would work if instead of running docker run each time we fire up Pulsar, we'd use docker start to reuse the previously created container. I just feel like this is an easier way of doing it, but if you think this is better, let's stick to it.
When it comes to the wrong hardware readings, I have tested this on linux and windows, and the results are the same : the hostname shows up as a meaningless alphanumeric string (the id of the container probably) and the disks and network interfaces are all messed up, because the node js app is retrieving hardware data from the container, not the host machine.

I just feel like this is an easier and more logical way of doing it

Yeah I think #18 is the real answer to this which is unfortunate, because it'll probably be a while until that is ready. Also, docker start isn't going to keep key.txt around either, the image is read every time. The only way to persist files across starts is with volumes or bind mounts. I'm going to implement the genkey system since it's a nice compromise and will only be around for a little while.
I was mostly looking at CPU usage for my "tests", but you are correct that the info for the network and disks is container specific. I'm not too sure what the fix is, but I'll start looking into it.

I just tested it on two computers

Sorry, that's a missclick

Also, docker start isn't going to keep key.txt around either, the image is read every time.

I just tested that on two separate devices running windows and linux, and both seem to keep the content of the key.txt file tough. I suggest that you try it yourself :

run the image, check if the client can retrieve the data
stop the container
start it again, the client clearly still works, which implies that the key hasn't changed

Okay, you are correct. Using docker start retains the key after stopping the container. However, I still don't believe that trusting the users to run Pulsar one way, which is less common, is a good fix. Plus, docker-compose down does remove the containers, thus erasing the key, so anyone who uses that, will be out of luck.
On another note, I have a solution to the hostname/network adapters/disks problem. The fix is to add some options on container creation.

--network host fixes the network adapters and hostname by binding the container to the host's network instead of the docker virtual one. There is a small downside of port mappings being ignored, but it's not like the port can be changed when run natively anyway.
--volume /dev/sda:/dev/sda mounts the /dev/sda device to the container so that it can see it. This can be repeated by the user as many times as they like so that any disks they want to monitor are mounted. I'm not sure how well this works on Windows, but I did find a Medium post talking about setting up traditional bind mounts which may or may not allow for the kind of inspection Pulsar needs.

Awesome work! I'm fixing this, updating the readme and this PR should be good to go 😁

I am starting to doubt of the feasibility of a dockerized performance monitor, there are just too many problems that come with it. Temp readings, live disk display and OS type are completely container-specific, which greatly limit the dashboard's capabilities, if we can't find a way to somehow easily communicate with the machine running docker, it might be better to just drop the idea.

I don't necessarily have a preference either way since it's not my project, although it would be a shame if the time already put in went to waste :man_shrugging:.
I do think that a dockerized machine monitor is possible as long as the user is willing to spend the time to set it up. Once everything is mounted, it'll probably just work, but getting to that point would be a pain depending on the system and the competence of the user.
@DarthUdp I know that you were interested in a docker version. Do you think it's worth it to go forward or should the docker effort be dropped?

I was thinking about this Earlier I have two suggestions, move pulsar to a compiled language or find a way to package the current code in a self contained binary if electron exists I'm pretty sure a similar thing should exist for pure node.

Well, I'm all for moving to Go (shameless fanboying), but Nexe doesn't look like a bad option for a single executable while keeping the project JavaScript based.
Another solution to the node setup problem is to use distribution packaging methods (.deb, .rpm, etc) plus a Windows installer for that crowd.

I'll try some of these solutions out, but for now, I need to do some further research concerning communication between the machine and its hosted containers. @BrenekH can you open a new PR so we can merge this branch into docker ?

The base for this has been changed to docker so it can be merged whenever you're ready.

That's even better, I didn't know you could do that to be honest.

Well, I'm all for moving to Go (shameless fanboying), but Nexe doesn't look like a bad option for a single executable while keeping the project JavaScript based.
Another solution to the node setup problem is to use distribution packaging methods (.deb, .rpm, etc) plus a Windows installer for that crowd.

I like the idea of nexe, it seems nice, however distro packaging would present it's own host of possible issues.


SIGTERM hot-loop

Great to see a plugin for the old ATAG One. I tried installing it, but Homebridge runs into a SIGTERM and restarts.
The Home app will on and off show the ATAG One, so I think your plugin finds the IP of the One, but some other problem occurs.
[2/13/2022, 3:08:22 PM] Homebridge v1.4.0 (HAP v0.10.0) (Homebridge 5264) is running on port 52808.
[2/13/2022,
3:08:22 PM] [Hue] Philips hue: event stream connected to https://<IP_ADDRESS>/eventstream/clip/v2
[2/13/2022, 3:08:22 PM] [Hue] warning: latest version: homebridge-hue v0.13.38
12/13/2022,
3:08:23 PM] [ATAG One] Error getting serial: Error: Base url is undefined!
[2/13/2022,
3:08:26 PM] Error: EACCES: permission denied, open
'device-config.json'
at Object.openSync (node: fs:585:3)
at Object.writeFileSync (node: fs:2155:35)
at updateDeviceConfig (/homebridge/node modules/homebridge-atag-one/src/files.ts:11:6)
at AtagOne.handleBroadcastMessage(/homebridge/nodemodules/homebridge-atag-one/src/AtagOne.ts:151:271
at
Socket.<anonymous> (/homebridge/node modules/homebridge-atag-one/src/AtagOne.ts:161:331
at
Socket.emit (node:events:520:28)
at
UDP.onMessage (node:dgram: 939: 8)
[2/13/2022,
3:08:26 PM] Got SIGTERM, shutting down Homebridge..
[2/13/2022,
3:08:31 PM] (Hue] goodbye
12/13/2022,
3:08:31 PM] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
12/13/2022,
3:08:36 PM] [HB Supervisor] Restarting Homebridge...
[2/13/2022,
3:08:36 PM] [HB Supervisor] Starting Homebridge with extra flags:
-I
-P /homebridge/node modules
[2/13/2022,
3:08:36 PM] [HB Supervisor] Started Homebridge v1.4.0 with PID:
764
[2/13/2022,
3:08:37 PM] Loaded config.json with 1 accessories and 2 platforms.
[2/13/2022,
3:08:37 PM] Loaded 0 cached accessories from cachedAccessories.
12/13/2022,
3:08:37 PM1
==-
[2/13/2022,
3:08:38 PM] Loaded plugin<EMAIL_ADDRESS>[2/13/2022,
3:08:38 PM] Registering accessory
'homebridge-atag-one.Atagone'
12/13/2022,
3:08:38 PM1
---
[2/13/2022,
3:08:38 PM] Loaded plugin<EMAIL_ADDRESS>[2/13/2022,
3:08:38 PM] Registering accessory
'homebridge-dummy.DummySwitch'

The problem is that HomeBridge can't acces device-config.json.  This file is used to store the base url (IP-address of your Atag One + port 10000) of your Atag One between reboots of HomeBridge.
Because there is no error catching for this error, HomeBridge crashes. And because the base url is stored in the first 10 seconds this plug-in starts up, HomeBridge keeps crashing.
I fixed this error in the latest version, and in addition, I added an option to disable the storing of the base url.

Great, thanks for the fix!


Box-ordinal-group:

Hello, can you add this CSS3 feature please? I'd like to compare to what version of browser it is supported. Default version of this is:box-ordinal-group: [number]and you can also modify it like this: -webkit-box-ordinal-group: [number] or -moz-box-ordinal-group: [number] etc.
What does it do? It's really simple and amazing. When you need change ordinal of HTML elements but you don't want to change the HTML code, you can use this. Basicly the element with lowest number will be loaded first, element with highest number will be loaded last (even shown, it changes positions of elements, it actually swap places between them, it doesn't matter how HTML is written).
You have to create container around as well and set this divs or elements to "display:block" too.
Thank you,
student John

The box-ordinal-group property was part of the old flexbox specification and should no longer be used. It's been replaced by the new flexbox spec's order property, which has support tracked at https://caniuse.com/#feat=flexbox
For more information see https://developer.mozilla.org/en-US/docs/Web/CSS/box-ordinal-group


[PROPOSAL] Add support for API versioning

What/Why
What are you proposing?
Every version of OpenSearch has its own version of the API and therefore the API specs should reflect that.
What users have asked for this feature?
In https://github.com/opensearch-project/opensearch-clients/issues/58 we plan to auto-generate clients. Therefore we need a way to both version API specs and a way to know the exact API spec for a given version of server.
What problems are you trying to solve?

Easily identify the exact spec for an exact version of OpenSearch.
Ability to generate specs for flavors of deployments of OpenSearch, such as the Amazon managed service, which may have APIs added or removed.

What is the developer experience going to be?
I see several options.
a) The specs tag when APIs were added/removed/changed, see #80, and publish a single version of specs with the options/tags.
b) The repo is branched in ways that follows OpenSearch and each branch publishes a version of the specs.
What is the user experience going to be?
I'd like to be able to say "where's the 2.7.0 version of OpenSearch specs" and consume it directly.

I would propose that the API spec include version ranges as a field for a method. A given client should be able to speak with multiple servers, and by knowing which server version we're talking to, or by specifying it in the request, a single client with a multi-version spec could handle that situation.

a) The specs tag when APIs were added/removed/changed, see https://github.com/opensearch-project/opensearch-api-specification/issues/80, and publish a single version of specs with the options/tags.

I kind of like this approach: continuously evolving the spec. I would like to suggest a combined approach, keep one spec for a release line (1.x, 2.x, 3.x). Why is that: within the release line, the spec should evolve in a backward compatible way but not between major releases. I have difficulties expressing the API in spec that was introduced in 1.3.7, deprecated in 2.7.0 and removed in 3.0.0 (we could only express the latter essentially). The only option with single spec I see is when we always evolve the spec in backward compatible way.
For cases where there is a need to have multiple clients, non issue in scope of same release line, but if the support of multiple major versions is needed, several clients could be generated easily (one for 2.x and one for 3.x fe).
What do you think?

I think if the spec can span as wide a range of versions as possible, it becomes more capable of generating a client that "just works." The challenge of migrating across major versions is the place where a multi-version client makes the biggest difference. The minor version changes, assuming semver is getting followed, introduce changes that are unlikely to lead to heartache of a user. If the client had a feature missing in a server, a lot of unlikely things would have to come together for an engineer to build an application that relied on those features because they exist in the client but didn't want to upgrade their server to enable the feature. The more constrained engineer is the one contending with major version changes and old codebases of working code. That's who benefits from a more capable multi-major-version client.

You cannot evolve a spec in backwards compatible ways across major semver versions because of breaking changes in parameters. For example, imagine an API that takes a field called name of type String. If we change name to be Integer, we cannot express "name was added in 1.0 as String, but became Integer in 2.0". The easiest way is to branch specs the same way as the product, and tag releases.

@wbeckler A client that can talk to any server version is nice but it might be more troublesome than it's worth. It will drastically increase the complexity of the code generator, increase performance overheads for the client (from server version checking and guards for different versions of the server when a request is executed). On the other hand, there are very few use cases where an application has to talk to multiple OS clusters of different major versions.

That's actually not true.

Any live upgrade requires a client to be able to talk to at least 2 major versions of OpenSearch.
Clients such as opensearch-hadoop want to be able to talk to multiple major versions of OpenSearch from a single installation of Hadoop.

Thanks @VachaShah , to me the Approach 1 presents the best balance of the usability and maintainability

With the publishing mechanism in #211 we can publish builds from multiple branches and thus track multiple versions of OpenSearch that aren't compatible.

https://github.com/opensearch-project/opensearch-api-specification/issues/120 is related

overall +1 on approach 1) which basically following https://semver.org/.
@dblock what's our plan to start some beta versioning release first as starting point? what are the blockers?

I like this minus the "beta" terminology that is not necessary imo.
The spec today tests against 2.17 (released) and 3.0 (unreleased). I think we should publish two versions today: <IP_ADDRESS>011 (October 11, 2024), after removing anything added in 3.0, and <IP_ADDRESS>011 with everything. I'd merge a PR that enabled that kind of versioning, but also maybe that's not necessary as the current latest release off main is working well for everyone?

beta is for if we are not fully ready, if not concern of following the regular release, then yeah, we don't need "beta".
what's the purpose of keeping the date here? what if there's any breaking change in Spec itself which would very likely happen as Core <> Spec not forcefully in-sync at this moment.
Having date in version, imo, not really helpful in terms of if there's incompatible spec api change or if it's following the backward compatible manner. Unless, you are proposing the plan that it can always introduce breaking change?

Let's backup. What are we trying to solve? I think I'm confused.
The spec today supports versioning via OpenAPI extensions.

x-version-added: OpenSearch version when the operation/parameter was added.
x-version-deprecated: OpenSearch version when the operation/parameter was deprecated.
x-version-removed: OpenSearch version when the operation/parameter was removed.

Furthermore, the spec merger supports --opensearch-version: An optional target version of OpenSearch, checking values of x-version-added and x-version-removed.
I renamed this issue to "publish versioned API specs". The intent is that we would use the x- extensions and the --opensearch-version and publish an OpenAPI spec that is for a given version as part of CI/CD and give that output a version number (that was my suggestion wrt dates). So that one could consume a 2.x spec for OpenSearch easier, without having to look at those x-version options.
Is there something else that you're looking for @amberzsy?

Let's backup. What are we trying to solve? I think I'm confused.

@dblock I think the issue is a bit different (and if it is not, than I am confused as well). The API spec is reverse engineered at the moment. What it practically means, despite the best effort, we could have added API elements (schema, properties, endpoints, etc) which deviate from the current "real" API. Correcting those makes sense but the API spec could be altered in a way that makes it incompatible with the previous one.
I think this is perfectly fine for the time being, but could be disruptive for the folks that are building on top of it since there is no "sticky" / "stable" published version to point to.

I think I understand having heard @amberzsy on Slack too.
Does publishing a 0.1.0 work? We would publish 0.2.0 when we introduce a breaking change, and 0.2.1 when we don't?

Does publishing a 0.1.0 work? We would publish 0.2.0 when we introduce a breaking change, and 0.2.1 when we don't?
sg, +1

0.2.1 when we don't?
typo? 0.1.1 i guess.

@amberzsy Take a look at https://github.com/opensearch-project/opensearch-api-specification/pull/635.

With #635 merged I will try and do a 0.1.0 release this week.

I published 0.1.0, https://github.com/opensearch-project/opensearch-api-specification/releases/tag/v0.1.0.


WIP: DO_NOT_MERGE: debug ci tests

Let's make sure that ci/prow/ci-index-gcp-filestore-csi-driver-operator-bundle succeeds.

/test ci-index-gcp-filestore-csi-driver-operator-bundle

/test ci-index-gcp-filestore-csi-driver-operator-bundle

/test ci-index-gcp-filestore-csi-driver-operator-bundle

/test ci/prow/operator-e2e
/test ci/prow/operator-e2e-extended

/test operator-e2e-extended
/test operator-e2e

/test operator-e2e
/test operator-e2e-extended

/test operator-e2e
/test operator-e2e-extended

/test operator-e2e-extended

/test operator-e2e-extended

This PR proves that ci/prow/operator-e2e-extended is perma failing. Closing.


Long tap popup items

Hi there,
thanks for the great tabbar controller! Would it be possible to add something like the popup item feature of Tweetbot to it? Like when you press a tabbar item it pops up more items?
If this isn't something you want to do, can you point me in the right direction how to best do it?
Thanks again,
Shukuyen.

This is a cool idea, I'd start by subclassing BCTab, you could use a
long press gesture recognizer to catch the long press. I haven't
thought about it much further, I don't have time to do something like
this at the moment, unfortunately :(
On 11 December 2011 08:41, Shukuyen
<EMAIL_ADDRESS>wrote:

Hi there,
thanks for the great tabbar controller! Would it be possible to add something like the popup item feature of Tweetbot to it? Like when you press a tabbar item it pops up more items?
If this isn't something you want to do, can you point me in the right direction how to best do it?
Thanks again,
Shukuyen.

Reply to this email directly or view it on GitHub:
https://github.com/briancollins/BCTabBarController/issues/10


Only allows one key to watch in hive_flutter dev

Steps to Reproduce
It seems in the hive_flutter dev version we only can listen to one key whereas before we could listen to multiple keys. I'm not sure if this is intended or not but it's a bummer anyhow.
Code sample
// hive_flutter (not dev)
return WatchBoxBuilder(
  box: Hive.box('myBox'),
  watchKeys: ['firstName', 'lastName'],
  builder: (context, box) {
    return Text(box.get('firstName') + ' ' + box.get('lastName'));
  }
)

// hive_flutter (dev)
return ValueListenableBuilder(
  valueListenable: box.listenable(key: ""),
  builder: (context, Box<Assignment> box, child) {
    ...
  }
);

Version

Platform: Android, iOS
Flutter version: 1.12.3
Hive version: 1.2.0
Hive Flutter version: 0.3.0-dev

I published a new version and there is now an additional keys parameter.
return ValueListenableBuilder(
  valueListenable: box.listenable(keys: ['firstName', 'lastName']),
  builder: (context, Box<Assignment> box, child) {
    ...
  }
)

Why is there both a key and a keys parameter? Won't that cause issues if a user were to fill both out or put the same key in both? Wouldn't it be simpler to just have just the keys parameter?

I thought it would be nice to have an option to only listen to a single key. Maybe you are right...

If you want that option, at least make an assert that only one of the parameters can have value.

If you want that option, at least make an assert that only one of the parameters can have a value.

I already have one but I think you are right, it is confusing.

I removed the key parameter.


Hide restore column when completed

Summary
PR Checklist

Is this a multi-tenancy feature/bug?

[ ] Yes, the relevant RBAC changes are at:

Do we need to backport changes to the old Rancher UI, such as RKE1?

[ ] Yes, the relevant PR is at:

Are backend engineers aware of UI changes?

[ ] Yes, the backend owner is:

Related Issue https://github.com/harvester/harvester/issues/6195

Occurred changes and/or fixed issues

Technical notes summary

Areas or cases that should be tested

Test Snapshot restores.
Test Backups restores.

Areas which could experience regressions

Screenshot/Video

@mergify backport release-harvester-v1.3 release-harvester-v1.4


fix login failure on interop tests with error: x509

Signed-off-by: anandrkskd<EMAIL_ADDRESS>What type of PR is this:
/kind bug
/kind tests
What does this PR do / why we need it:
This PR fixes failing interop tests on 4.11/4.12.
Tests are failing as it doesn't contain changes from PR which was implemented on v2 branch.
Which issue(s) this PR fixes:
Fixes #NA
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

How to test changes / Special notes to the reviewer:

/retest

/retest

@anandrkskd Can you rebase this branch onto main? Tests on Prow should be fixed with https://github.com/redhat-developer/odo/issues/6291

Tests passing on Prow, but not on IBM Cloud, with similar errors (net/http: TLS handshake timeout):
[odo]  •  Downloading starter project "nodejs-starter"  ...
    [odo]  ✗  Downloading starter project "nodejs-starter" [10s]
    [odo]  ✗  unable to download starter project "nodejs-starter": Get "[https://github.com/odo-devfiles/nodejs-ex.git/info/refs?service=git-upload-pack":](https://github.com/odo-devfiles/nodejs-ex.git/info/refs?service=git-upload-pack%22:) net/http: TLS handshake timeout
    [odo] the command failed, the devfile has been removed from current directory
    Deleting project: cmd-add-binding-test253onx
    Running kubectl with args [kubectl delete namespaces cmd-add-binding-test253onx --wait=false] and odo env: []
    [kubectl] namespace "cmd-add-binding-test253onx" deleted
    Setting current dir to: /go/odo_1/tests/integration
    Deleting dir: /tmp/1748382796
    Deleting dir: /tmp/2598565857
  << End Captured GinkgoWriter Output

  No future change is possible.  Bailing out early - after 14.022s.
  Running odo with args [odo init --name mynode --devfile-path /go/odo_1/tests/examples/source/devfiles/nodejs/devfile.yaml --starter nodejs-starter] and odo env: []
  Expected
      <int>: 1
  to match exit code:
      <int>: 0
  In [BeforeEach] at: /go/odo_1/tests/helper/helper_cmd_wrapper.go:101

Let's try again..

/override OpenShift-Integration-tests/OpenShift-Integration-tests
E2E Tests failing on net/http: TLS handshake timeout when fetching starter project from GitHub. Previous run passed.


Add Edit Profile Screen

Implements profile editing. From your own profile, click the pencil.
https://openedx.atlassian.net/browse/MA-1295

@1zaman @miankhalid Please review

Closing in favor of squashed PR: https://github.com/edx/edx-app-android/pull/405


[1.12.1] [neoforge] [+ curious compat layer] game crashed randomly, brought me to servers

im assuming this is an issue with this mod after looking through the logs, but i could be entirely wrong. i was using cuisine delight and trying to put something i cooked into my backpack when my game crashed and said that i disconnected from the server. it brought me to the servers menu. this is a completely singleplayer world without LAN or anything, im also not using any multiplayer mods like essential. now i cant open the world, i instantly get greeted with the same message. here is the log, this is what it tells me when i try to connect to the world

First error to occur is something with Distant Horizon:
	[20Oct2024 12:48:05.681] [Server thread/ERROR] [DistantHorizons-com.seibel.distanthorizons.core.api.internal.ServerApi/]: ServerTickEvent error: Cannot invoke "net.minecraft.client.player.LocalPlayer.blockPosition()" because the return value of "loaderCommon.neoforge.com.seibel.distanthorizons.common.wrappers.minecraft.MinecraftClientWrapper.getPlayer()" is null
java.lang.NullPointerException: Cannot invoke "net.minecraft.client.player.LocalPlayer.blockPosition()" because the return value of "loaderCommon.neoforge.com.seibel.distanthorizons.common.wrappers.minecraft.MinecraftClientWrapper.getPlayer()" is null
	at TRANSFORMER/distanthorizons@2.2.1-a/loaderCommon.neoforge.com.seibel.distanthorizons.common.wrappers.minecraft.MinecraftClientWrapper.getPlayerBlockPos(MinecraftClientWrapper.java:206) ~[DistantHorizons-2.2.1-a-1.21.1-neo-fabric.jar%23288!/:?]
	at TRANSFORMER/distanthorizons@2.2.1-a/com.seibel.distanthorizons.core.level.DhClientServerLevel.doWorldGen(DhClientServerLevel.java:119) ~[DistantHorizons-2.2.1-a-1.21.1-neo-fabric.jar%23288!/:?]
	at java.base/java.lang.Iterable.forEach(Unknown Source) ~[?:?]
	at TRANSFORMER/distanthorizons@2.2.1-a/com.seibel.distanthorizons.core.world.DhClientServerWorld.doWorldGen(DhClientServerWorld.java:153) ~[DistantHorizons-2.2.1-a-1.21.1-neo-fabric.jar%23288!/:?]
	at TRANSFORMER/distanthorizons@2.2.1-a/com.seibel.distanthorizons.core.api.internal.SharedApi.worldGenTick(SharedApi.java:115) ~[DistantHorizons-2.2.1-a-1.21.1-neo-fabric.jar%23288!/:?]
	at TRANSFORMER/distanthorizons@2.2.1-a/com.seibel.distanthorizons.core.api.internal.ServerApi.serverTickEvent(ServerApi.java:73) ~[DistantHorizons-2.2.1-a-1.21.1-neo-fabric.jar%23288!/:?]
	at TRANSFORMER/distanthorizons@2.2.1-a/com.seibel.distanthorizons.neoforge.NeoforgeServerProxy.serverTickEvent(NeoforgeServerProxy.java:79) ~[DistantHorizons-2.2.1-a-1.21.1-neo-fabric.jar%23288!/:?]
	at MC-BOOTSTRAP/net.neoforged.bus/net.neoforged.bus.EventBus.post(EventBus.java:350) ~[bus-8.0.2.jar%23148!/:?]
	at MC-BOOTSTRAP/net.neoforged.bus/net.neoforged.bus.EventBus.post(EventBus.java:315) ~[bus-8.0.2.jar%23148!/:?]
	at TRANSFORMER/neoforge@21.1.71/net.neoforged.neoforge.event.EventHooks.fireServerTickPost(EventHooks.java:1002) ~[neoforge-21.1.71-universal.jar%23262!/:?]
	at TRANSFORMER/minecraft@1.21.1/net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:943) ~[client-1.21.1-20240808.144430-srg.jar%23261!/:?]
	at TRANSFORMER/minecraft@1.21.1/net.minecraft.client.server.IntegratedServer.tickServer(IntegratedServer.java:110) ~[client-1.21.1-20240808.144430-srg.jar%23261!/:?]
	at TRANSFORMER/minecraft@1.21.1/net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:707) ~[client-1.21.1-20240808.144430-srg.jar%23261!/:?]
	at TRANSFORMER/minecraft@1.21.1/net.minecraft.server.MinecraftServer.lambda$spin$2(MinecraftServer.java:267) ~[client-1.21.1-20240808.144430-srg.jar%23261!/:?]
	at java.base/java.lang.Thread.run(Unknown Source) [?:?]

Can you try removing such at all first?

Furthermore it seems that my packets maybe getting messed up as a decode call has failed:
[20Oct2024 13:01:30.684] [Netty Server IO #1/ERROR] [dev.xkmc.l2serial.serialization.codec.CodecAdaptor/THROWING]: Throwing
java.lang.IllegalStateException: [CodecAdaptor::encode] Unknown ops type with empty ops: E(OPTIONAL, Optional.empty)
	at TRANSFORMER/l2serial._4@3.0.9+4/dev.xkmc.l2serial.serialization.codec.CodecAdaptor.encode(CodecAdaptor.java:106) ~[l2serial-3.0.9+4.jar%23429!/:3.0.9+4]
	at MC-BOOTSTRAP/datafixerupper@8.0.16/com.mojang.serialization.Encoder.encodeStart(Encoder.java:14) ~[datafixerupper-8.0.16.jar%23112!/:?]
	at TRANSFORMER/minecraft@1.21.1/net.minecraft.util.EncoderCache$Key.resolve(EncoderCache.java:53) ~[client-1.21.1-20240808.144430-srg.jar%23261!/:?]
	at TRANSFORMER/minecraft@1.21.1/net.minecraft.util.EncoderCache$1.load(EncoderCache.java:25) ~[client-1.21.1-20240808.144430-srg.jar%23261!/:?]
	at TRANSFORMER/minecraft@1.21.1/net.minecraft.util.EncoderCache$1.load(EncoderCache.java:22) ~[client-1.21.1-20240808.144430-srg.jar%23261!/:?]
	at MC-BOOTSTRAP/com.google.common@32.1.2-jre/com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3571) ~[guava-32.1.2-jre.jar%23154!/:?]
	at MC-BOOTSTRAP/com.google.common@32.1.2-jre/com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2313) ~[guava-32.1.2-jre.jar%23154!/:?]
	at MC-BOOTSTRAP/com.google.common@32.1.2-jre/com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2190) ~[guava-32.1.2-jre.jar%23154!/:?]
	at MC-BOOTSTRAP/com.google.common@32.1.2-jre/com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2080) ~[guava-32.1.2-jre.jar%23154!/:?]
	at MC-BOOTSTRAP/com.google.common@32.1.2-jre/com.google.common.cache.LocalCache.get(LocalCache.java:4012) ~[guava-32.1.2-jre.jar%23154!/:?]
	at MC-BOOTSTRAP/com.google.common@32.1.2-jre/com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:4035) ~[guava-32.1.2-jre.jar%23154!/:?]
	at MC-BOOTSTRAP/com.google.common@32.1.2-jre/com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:5013) ~[guava-32.1.2-jre.jar%23154!/:?]
	at MC-BOOTSTRAP/com.google.common@32.1.2-jre/com.google.common.cache.LocalCache$LocalLoadingCache.getUnchecked(LocalCache.java:5020) ~[guava-32.1.2-jre.jar%23154!/:?]

It seems something to do with l2serial so I assume the L2 line of mods

logs for without distant horizons

Try removing the L2 series of mods for the time being

what are the L2 series of mods if you dont mind me asking?

Mods from this dev and/or using this https://www.curseforge.com/minecraft/mc-mods/l2library

this works! thank you very much! i love farmers delight but for some strange reason the addons people make for that mod are insanely buggy, ive had to remove 3 now due to crashes because of them. i wonder how a small cooking mod becomes so destructive. ill go report this issue to them, thanks!


Travis seems to be blocking certain pull requests [potentially not an issue]

I just noticed a large backlog of Pull Requests.
Various errors from LuaCheck, but it's in a high number of pull requests.
Checking lua/entities/gmod_wire_expression2/core/debug.lua 1 error
    lua/entities/gmod_wire_expression2/core/debug.lua:7:2: expected expression near '*'

Checking lua/wire/client/text_editor/wire_expression2_editor.lua 354 warnings

Can someone merge this pull request, just to get other pull requests closed/rejected, as necessary?
https://github.com/wiremod/wire/pull/1369

#1369 needs reviewing before it can be merged.


Credit other contributors properly

Until now, most of the code was mine. Increasingly, other people are contributing. I should include something somewhere to say that prominently, and perhaps have links to the Github contributors graphs (so everyone gets credited even if they did a little, and I don't need to update in future).

I've added a link to other contributors on the front page.


raft: make raft configurable

The first step is to make raft itself configurable, then i will go ahead to make node configurable.
@bdarnell what is your opinion?
/cc @yichengq

LGTM

lgtm


Add E223 quick fix

fix #20 for warning code E223

Closing in favor of https://github.com/microsoft/vscode-flake8/pull/206


validate config

Fixes https://github.com/Quansight/qhub/issues/7
Should we create a github-action for validate ?
I am unable to comment on PR with the errors found.

Better solution: https://github.com/Quansight/qhub/pull/119


some question about screenPosition

I saw screenPosition can change the hand.palmPosition into hand.screenPosition use the method--screenPosition in the demo, can it be used in gsetures?(such as keyTap.position/screenTap.position)

yes, it can.  Simply pass your desired vec3 as the first argument in the method:
hand.screenPosition(keyTap.position)


Define Emscripten syscall146 for writev, and a few other stubs.

This was enough to get the zlib benchmark working, still lots to do.

Can you make this portable? AFAICT there isn't a Windows equivalent to writev, though.

An attempt has been made to get this working on Windows, but it is not tested. Can you take it from here?

Sure, although just from looking at it I think you need to wrap the #include in an #ifdef. Can you also add the zlib benchmark to the Test folder, or something else that calls it?

Fixed the include, added the zlib benchmark. ptal

Looks good, thanks! I added bounds checking for the buffers, and made it use vmFile so whenever that works the fd parameter will work.


How to get completion category?

Hello,
User @oantolin has created the packages embark, which allows using commands similar to Ivy or Helm actions. Different commands are made available, depending on what is being completed (file, buffer, etc.).
To do this, they use the following expression to detect what kind of completion is happening:
(completion-metadata-get
  (completion-metadata (minibuffer-contents)
                       minibuffer-completion-table
                       minibuffer-completion-predicate)
   'category)

In Selectrum, this returns that buffer names are being completed, even in commands like find-file or amx. I do not have this problem with normal Emacs completion.
Why does this happen, and is there a way to get the actual completion category?
Thank you.

After thinking about it a better approach could be to allow passing the table as an argument to selectrum-read. Functions like selectrum-read-file-name and selectrum-read-buffer still need to pass the dynamic collection but need a way to pass the original table to query the metadata from.
Note that the metadata returned by the table can depend on the current input and the predicate so we really need access to the original table within selectrum-read only passing the metadata wouldn't suffice.

What's wrong with just let-binding those variables? If you did something recursively, wouldn't they be let-bound recursively to the correct values?

If you did something recursively, wouldn't they be let-bound recursively to the correct values?

Only for the cases where they are let bound. This can be done for the selectrum functions which integrate with the completion API but not for custom commands written by users or for example selectrum-read-library-name. One could let bind them back to nil but that would have to done every time you use selectrum-read directly.

Okay... so I guess then your PR seems fine, but it should have logic in selectrum-read to translate that keyword argument into a let-binding, right?

Aren't minibuffer-completion-table and minibuffer-completion-predicate correctly bound for the function body of selectrum-read when passed like that?

Using a named variable as a function argument creates a lexical binding, not a dynamic one (thank goodness). You need to invoke let explicitly to create dynamic bindings.

Yes but it should be a lexical one sorry if I expressed that confusingly.

Wait a moment I have to check something.

Sorry now I was confused they should be dynamically bound but I think they are because minibuffer-completion-table and minibuffer-completion-predicate are special vars.

;;; selectrum.el --- Easily select item from list -*- lexical-binding: t -*-

(defvar special-var nil)

(cl-defun check (&key special-var)
  (check2))

(defun check2 ()
  (message "is see %s" special-var))

(check :special-var "this")

Actually, I did that test too. But I did it without &key, silly me. I guess cl-defun turns &key into a let, whereas regular defun doesn't do any of that. So, what you have works. I'll take another look.

Interesting I did not thought about that and just assumed special vars are always dynamically bound even when passed as function arguments.

This seems to be fixed now, so I'm closing this issue.

I will also soon add instructions to the wiki how to setup embark for selectrum.


Make a chatbot

Is your feature request related to a problem? Please describe.
A chatbot to give answers depending upon their questions.
Describe the solution you'd like.
I will make a chatbot using

HTML
CSS
Javascript
It will be able to answer different questions like Who are you, What can I do for you etc.

Describe alternatives you've considered.
.
Add any other context or screenshots about the feature request here.
No response

@swapnilsparsh please assign his issue to me

@swapnilsparsh please assign me this issue


Nickname completion of displaynames is broken

Action:

Type first three letters of someone's displayname

Expected result:

After a few seconds, see a popup with possible completions

Actual result:

Nothing happens

Affected versions:

Latest lazyloading build

With lazyloading enabled
With lazyloading disabled

Apparently the latest version released to F-Droid/Google is also affected

Completion of matrix IDs works as expected. (@bla...)

Seems to work fine for me on G-b2381 with lazyloading disabled

Hi @Matrixcoffee ,
Thanks for reporting.
I'll check this
Benoît

Ok, the fix is merged


Fix Broken "Run in Postman" Links in IS REST API Documentation

Is your suggestion related to a missing or misleading document? Please describe.
It's been identified that some "Run in Postman" links within the IS documentation for REST APIs are not functioning as expected. For an example: https://is.docs.wso2.com/en/6.0.0/apis/idp-rest-api/.
The underlying issue appears to be that these Postman collections were hosted on personal developer accounts, which are now inaccessible.
Describe the improvement
To rectify this, we have a couple of options:

Move the Postman collections to a common WSO2 repository.
Remove the broken links from the documentation until a more permanent solution is found.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Update: Report and Dashboards use Denali buttons

Description
Move report and dashboard buttons over to denali
Screenshots

License
I confirm that this contribution is made under an MIT license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

Changes look good, are you going to do the widget buttons in this PR too?

@jkusa Yea I'll fix those (but not dedup) and the report view overlay as well

Changes look good, are you going to do the widget buttons in this PR too?

@jkusa Yea I'll fix those (but not dedup) and the report view overlay as well


Reusable validators. How?

One option is to use HKT https://github.com/idkjs/hkt-fakenickels (thanks @idkjs for recovering this sketch)

It'll be something else and simpler soon. I'll create an issue unifying things.


[Enhancement] Provide a  method to query the subscription group info of the topic.

Before Creating the Enhancement Request

[X] I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary
I am trying to find a way to query the  subscription consumer group info of the specific topic.However , I didn't find the right method to do it .
Motivation
I am trying to find a way to query the  subscription group info of the specific topic. And the only way I found is like this https://help.aliyun.com/zh/apsaramq-for-rocketmq/cloud-message-queue-rocketmq-4-x-series/developer-reference/api-ons-2019-02-14-onstopicsubdetail?spm=a2c4g.11186623.0.i2
And it is not recommended to do this when send and receive message. So how could  subscription consumer group info of the topic . If there is any exist way ,please tell me ,thanks.
Describe the Solution You'd Like
.
Describe Alternatives You've Considered
.
Additional Context
No response

You can refer to this api https://github.com/apache/rocketmq/blob/develop/tools/src/main/java/org/apache/rocketmq/tools/admin/DefaultMQAdminExtImpl.java#L1042

If you want more information.For example consume offset, consume lag etc.You can refer to RocketMQ dashboard design:
https://github.com/apache/rocketmq-dashboard/blob/2fb0fce0b16fe04ff7ec0181d4127267e9c9af31/src/main/java/org/apache/rocketmq/dashboard/controller/ConsumerController.java#L103


Include error data from oauth provider in debug mode

Relates to #22

Something like this:
class BaseSocialAuthView:

    def respond_error(self, error):
        ...
        # TODO get message as string from error
        emgs = some_code_here(error)

        if default_settings.DEBUG:
            return Response(str(emsg), status=status.HTTP_400_BAD_REQUEST)
        return Response(status=status.HTTP_400_BAD_REQUEST)

Hey, @st4lk I managed to show error in response somehow. Gonna open PR for the same. Please check SS for confirmation.
Please validate it and let me know if I am correct. I just know about sending response, you will have better knowledge of should we do this or not.


Default value for application command options

Since registration is now entirely separated from listening, there's no nice way to allow for this. This story could be reopened in the future if there is demand for it though


MM-48607 Fix bug that caused the upgrade modal to not be shown when requesting an update

Summary

Fix a bug that caused the upgrade modal to not be shown when requesting an update.
The bug was caused because the click event that caused the modal to be shown was propagated and immediately triggered onHide of the upgrade modal which closed the modal.
Ticket Link

MM-48607
Checklist

[ ] Telemetry updated
[ ] Gated by experimental feature flag
[ ] Unit tests updated

I'm not sure how that change affected to it. Now the modal appears but doesn't properly work.
In the following video, I show first how it works in the case I'm a viewer, and then how it fails when I'm a participant. The modal opens correctly but it closes no matter where I click. Here are a few more details:
* It closes immediately, without the animation

* It closes even if I click on the start trial button

* it closes even if I click on the modal but not on the buttons

CleanShot.2022-12-19.at.10.08.27.mp4

Thanks for pointing out! I found out that the cause of the issues for participants is, that the RequestUpdateButton is in a Dropdown. This has the side-effect that closing the dropdown will cause the modal to be removed from the document and this caused the issues.
I've fixed this by moving the modal outside the dropdown.


Cannot find and install from package list

I cannot install this theme in my Sublime Text 3 build 3143.
I cannot find it in "Package Control: Install Package"
This link https://packagecontrol.io/packages/Nord doesn't work either.
Do I have to do it manually?

Sorry. I just saw the already closed duplicated issues. #7 #10 #11 #12


[BUG]profile-page--recovery phrase need to be hided in wallet

Describe the Bug
The test version is IOS development mode 2.0.4(7).
In wallet which in profile page, recovery phrase need to be hided.

Expected experience
Recovery phrase need to be hide.
Steps To Reproduce

Go to profile page.
Go to wallet.

Environment
-IOS:17.2.1

Already solved in IOS dev version 2.0.4(8).


⚠ Turnos 24x7 has degraded performance

In 29c6608, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 945 ms

Resolved: Turnos 24x7 performance has improved in b30b7b8.


[azservicebus] Fixing error check in recovery, adding some more tests

On recovery check for the specific errConnResetNeeded error rather than a cancellation error.
I've merged those code paths into one.
Update the empty sessions test to be more realistic, handle connection failures, etc..
Make the rapid open/close test do more rounds and more iterations.
Add in some logging for the "link error being upgraded to a connection error".

/azp run go - azservicebus