[Storage FileShare/Datalake Service] x-ms-client-request-id header

how is this different from https://github.com/Azure/azure-sdk-for-cpp/issues/423?

Will only leave #423 to track.


Avoid #steps boilerplate by prepending on #call

We get rid of the necessity to wrap the operations' flow with the #steps's block by prepending a module that decorates the #call method.
If before we had to do:
class CreateUser < Dry::Operation
  def call(input)
    steps do
      attributes = step validate(input)
      step create(attributes)
    end
  end

  # ...
end

Now we can do:
class CreateUser < Dry::Operation
  def call(input)
    attributes = step validate(input)
    step create(attributes)
  end

  # ...
end

We want to provide that as the default behavior to improve the ergonomics of the library. However, we also want to provide a way to customize or opt out of this magic behavior. Users can inherit from, e.g., Dry::Operation[prepend: :run] to decorate the #run method (multiple methods are allowed by passing an array), or Dry::Operation[prepend: false] to disable the behavior:
class CreateUser < Dry::Operation[prepend: :run]
  def run(input)
    attributes = step validate(input)
    step create(attributes)
  end

  # ...
end

class CreateUser < Dry::Operation[prepend: :false]
  def call(input)
    steps do
      attributes = step validate(input)
      step create(attributes)
    end
  end

  # ...
end

Notice that as a consequence of this change, we're "polluting" the ancestry chain of the descendant classes with the prepender logic:
Class.new(Dry::Operation).ancestors
# [#<Module:0x00007f8e523c1698>, <- Actual prepender
#  #<Class:0x00007f8e523c1918>, <- Descendant
#  #<Dry::Operation::Prepender:0x00007f8e523c17d8>, <- Stateful module keeping the prepender options
#  Dry::Operation,
#  Dry::Operation::Mixin,
# ...]

When creating a descendant from a descendant, the prepender logic is duplicated to override the decorated method from the nested descendant (which goes before the first prepender in the ancestry):
Class.new(Class.new(Dry::Operation)).ancestors
# [#<Module:0x00007f8e52331408>, <- Actual prepender
#  #<Class:0x00007f8e52331688>, <- Nested descendant
#  #<Dry::Operation::Prepender:0x00007f8e52331548>, <- Stateful module keeping the prepender options
#  #<Module:0x00007f8e52331868>, <- Previous prepender
#  #<Class:0x00007f8e52331ae8>, <- Descendant
#  #<Dry::Operation::Prepender:0x00007f8e523319a8>, <- Previous stateful module keeping the prepender options
#  Dry::Operation,
#  Dry::Operation::Mixin,
#  ...]

Also, notice that Dry::Operation[] will return an anonymous Class so it can be inherited from, so Dry::Operation won't appear in the ancestry chain:
Class.new(Dry::Operation[prepend: false]).ancestors
# [#<Class:0x00007f8e5233eec8>, <- Descendant
#  #<Class:0x00007f8e5233f328>, <- Anonymous class returned by Dry::Operation[]
#  Dry::Operation::Mixin,
#  ...]

To accomodate the above, the steps logic has been moved to a Dry::Operation::Mixin module so it can be reused both by descendants from Dry::Operation and Dry::Operation[].
It's worth it to highlight all that complexity, although it should be transparent to the user. As said, it's a trade-off we consider worth it to improve developer experience.

Thanks for this, @waiting-for-dev! I hope to get onto this sometime in the coming week, but I did want to give some early feedback on one aspect: I'd rather we avoid the whole dynamic subclassing pattern here.
class MyClass < ParentClass[args, go, here] is clever (and yes, I know rom-repository does it), but ultimately I think it's not a very ergonomic developer experience (as soon as you need more than one or two args, or you want a descriptive keyword argument name, it gets very lengthy and unwieldy), and it completely conflicts with tools like Sorbet, which will want statically resolvable constants for superclass names.
If you want to look for an analog within the dry-rb ecosystem for API inspiration, perhaps dry-struct is a good one, in that it offers a couple of class-level methods for controlling its overall behaviour.
Keen to hear your thoughts :)

Thanks for your feedback, @timriley :raised_hands:
I get your points and they make a lot of sense. However, we're in a tricky situation here, as I see no way to use dry-operation through inheritance + defaulting to decorate #call + still allow people to configure or opt out of the prepended behavior. That's because once you do class MyClass < Dry::Operation, the .inherited hook will be called, and once a module has been prepended there's no way to unprepend it. We can maybe find a middle-ground solution somewhere:

Keep using the dynamic subclassing pattern only for this specific behavior. I.e., use DSL methods to configure things like the monad type or ORM extensions. That would be bad for Sorbet.
Default to not prepending the module, and instead use a DSL method for that. Bad for ergonomics.
Use Dry::Operation through the anonymous module pattern, still defaulting to prepend the module. That would affect expectations on Hanami, where different layers work through inheritance. However, we could easily work around that by creating a Hanami::Operation class in the framework that would just include the Dry::Operation module.

I think 3 is the best solution, but I'm very interested in hearing your thoughts :slightly_smiling_face:

We could even have .method_added undef itself after it finds the relevant method (which will usually the first user-defined method in typical usage).

Those are great calls, @timriley!

I think .new is probably too late

I think that wouldn't be too late, as we can always use Object#extend to modify the singleton for the instance. It's something I tried while working on kwork and it did the trick. However, I didn't want to go down that path because, unless Ruby has changed and I didn't notice, that would invalidate the method cache and therefore could have severe performance issues.

.method_added feels almost perfect

I agree! I'll give it a try and get back with my findings :slightly_smiling_face:

@timriley, one thing that could be very surprising is having the class-level method ignored when called after the method definition. E:g.:
class CreateUser < Dry::Operation
  def run
    # ...
  end
  wrap :run
end

We don't have that problem either with anonymous inheritance or mixin inclusion. IMO that's a big trade-off, as shipping a DSL that depends on global (load order) state is quite brittle. What are your thoughts on that?

@waiting-for-dev I'm not personally concerned about this. We can document this limitation. And most people would never run into this anyway, since "the top of the class" is where class-level configuration tends to go anyway.
We could also possibly combine this with a check at the time of the first .new to determine whether the expected module has been prepended.

@waiting-for-dev I'm not personally concerned about this. We can document this limitation. And most people would never run into this anyway, since "the top of the class" is where class-level configuration tends to go anyway.

Just came to my mind we can also check "Object.instance_method(:call)" and avoid .method_added if already defined.

@timriley, please, see #11 for the implementation via class-level methods. Closing this one.


Clean up the texts of examples on demo site

Update the label text for our demo examples

@Pessimistress @heshan0131


Update submodule pointers for contributed demos

Signed-off-by: Gaurav Aggarwal<EMAIL_ADDRESS>
Description
Update submodule pointers for Partner Contributed Demos and Community Contributed Demos repos.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This PR is covered by later PR.


Freezes on Quest : On launch or after few seconds when waering the headset.

Hello Chris,
I saw that the other similar issue was closed, and the Unity forum take ages to approve my post ^^
Little problem :
The headset freezes at load time.
But actually when I don't use it for a little while and I take it again the scene works for few seconds (with hand tracking on the Quest side) and then freeze again.
On the computer (Editor) nothing happens, and its hard to debug anyways since the quest is freezing.
Here is the quest log  :
cd C:\Program Files\Unity\Hub\Editor\2019.2.6f1\Editor\Data\PlaybackEngines\AndroidPlayer\SDK\platform-tools
adb logcat -v brief
Complete adb logcat (brief) in the text file : Oculus Quest adb logcat brief.txt
Here I paste a part, similar to yours :
I/VrApi  ( 5468): FPS=72,Prd=45ms,Tear=0,Early=72,Stale=0,VSnc=1,Lat=1,Fov=0,CPU4/GPU=2/2,1651/414MHz,OC=FF,TA=0/0/0,SP=N/N/N,Mem=1804MHz,Free=1678MB,PSM=0,PLS=0,Temp=27.0C/0.0C,TW=1.61ms,App=0.42ms,GD=0.00ms,CPU&GPU=1.70ms,LCnt=1,GPU%=0.15,CPU%=0.02(W0.05),DSF=1.00
E/Unity   ( 5468): SocketException: The requested address is not valid in this context
E/Unity   ( 5468):   at System.Net.Sockets.Socket.Bind (System.Net.EndPoint localEP) [0x00043] in <0e1afc3ce03d4e2ab478056348d6a9e9>:0
E/Unity   ( 5468):   at Assets.RemoteHandsTracking.HandsDataReceiver.Start () [0x00032] in <d2c4b3c0a45248e7a331cb3544dfe565>:0
E/Unity   ( 5468):
E/Unity   ( 5468): (Filename: <0e1afc3ce03d4e2ab478056348d6a9e9> Line: 0)
E/Unity   ( 5468):

What I don't get, is why is freezing, at least I could understand that the data could not be send through the Network so nothing happens in the Editor.
But that the Oculus Quest freezes, its like overreacting ^^
Hope this helps,
Don't hesitate to ask more info if  you need.
Cheers :)

Hi Satolas,
Thanks, that helps.
I've recreated that and it'll be down to wrong IP in HandsDataSender. Or if you're certain that's correct IP then Quest can not reach, eg. due to FW / network setup.
I'll push a fix later this afternoon so it doesn't freeze when that happens - but that freeze is not cause of your issue.


Can a list option be added to the command.

Sometimes I just want to list the roles I have access to via SAML (e.g. to programmatically create aliases), could you add a --list to the command line options.
Looking at the code it doesn't look too difficult, it looks like the list is already there, in this code:
            debug("Asking user to choose role");
            questions.push({
                name: "role",
                message: "Role:",
                type: "list",
                choices: _.map(roles, "roleArn"),
                default: defaultRoleArn
            });

You just need to print it out.

I'm in the same situation as well, I need to know which account is which, would be really useful if I could see the role description that you'd see in the gui


Problem with caret position

Hi, I have tried to implement autocomplete widget and there is a problem with input's caret positioning. When you assign oninput event and fire it on each character change, sometimes caret jumps out of correct position. This situation occurs when you add a long string, then press and hold backspace key. After deletion input element still have some characters left after the cursor.

Hello @neriusmika ,
you can try two solutions:

setup the parameter parameter update_interval=0, to make a synchronous messaging between browser and remi server,
handle a different event, linke keyup, allowing less messaging traffic during typing

Tried 1st solution, the problem still remains.

Actually the problem is with input element updates. I need to update only sibling dropwdown element and keep input the same. But it seems I can't prevent that. If some child element is changed, then all parent's children are receiving updates. I'm new to Remi and don't know the internals well, maybe I'm doing something wrong. How to prevent updates on input element, but receive them for sibling elements in onchange event handler? Btw, my onchange handler is in input parent widget (but I think that should not cause the problems).

@dddomodossola element properties are not synchronized with attributes, maybe we can handle them differently? In such cases updates will not be triggered. I have seen in snabbdom virtual dom library, they have separate dictionaries for properties and attributes. If you don't update attributes, there is no need to replace the element. It should speed up the rendering part too.

Solution to my problem is not to store received value to attributes dictionary. But I think that attributes and properties should be updated separately anyway.

@neriusmika yeah of course it could be feasible to update only and attributes avoiding to replace the widget. However is not that simple, that is a really sensible part. It's really important to get a solid correspondance between webview and application data.
Just review the problem: you are trying to handle an onchange event emitted by a textinput, in order to make an autocompletion. the problem you are getting is that, during typing caret gets moved in a wrong position. is this correct?

it could be feasible to update only attributes avoiding to replace the widget

I mean update properties not attributes. Attributes can be kept the same. In static html, when you write something to input element, it's value property changes, but value attribute remains unchanged. They are different things. Now we don't have the possibility to update properties without changing attributes. And when you change attribute, you introduce expensive dom updates instead of simple property update.

Just review the problem: you are trying to handle an onchange event emitted by a textinput, in order to make an autocompletion. the problem you are getting is that, during typing caret gets moved in a wrong position. is this correct?

Correct. Because when I try to store received value (eg. for later use) in attributes, it updates element immediately and probably misses some events (even with update_interval=0). Actually when you write something to the input element, there is no need to update value attribute, but we must store received value somewhere anyway. And attributes dictionary is not the right place, because we receive value property, not attribute.

@dddomodossola I will try to implement some prototype with properties in my fork.

Can you share the script you are getting problem with? Maybe I can review it. I'm probably misunderstanding something.

My script is not directly related to that problem. You can read more about properties and attributes here: https://stackoverflow.com/a/6004028 and https://blog.fullstacktraining.com/html-attributes-vs-dom-properties/ We don't always need to update attributes and thus recreate dom elements, but change element (dom object) properties instead. For example you can look at snabbdom virtual dom implementation (used by vue.js etc). It can speed up rendering and in those situations (like changing input value), object will not be recreated, events will not be reassigned, element will not loose focus, etc. So indirectly there will be no such problems with cursor positions because it will stay where it should be without any caret manipulations.

Remi in all places where I looked is retrieving properties via sendCallbackParam (eg. param['value'] = document.getElementById('123').value <- it gets value property here, not an attribute) and then in callback handlers setting and updating html attributes (self.set_value(new_value)) which I think is wrong. Probably there should be 4th message type to update only changed properties without recreating the whole element. Of course I can leave such elements unchanged without storing the received value to Remi's Tag attributes dictionary. But it will be just workaround not a complete solution.

Btw, you can look at https://github.com/snabbdom/snabbdom/blob/master/src/modules/props.ts the code to update properties is quite simple, but Remi must allow (and track?) property updates in addition to attributes. Probably there should be no difference from a higher level widget code, not every developer should know about those internals. But in situations like reading and updating input value, there is no need to recreate the element.

@neriusmika thank you for the information. I will look into it soon. today I'm busy. however I'm pretty sure that this would not solve the problem. I wi try to make a working example for you.

@neriusmika the problem is this:

during text editing, the remi server receives the new textinput value (i.e. "some value|");
in the mean time, further changes happens on the textinput (i.e. "some va|");
the remi server sends the updated value to the browser (i.e. "some value");
the caret (that was moved in another position) now gets placed in a wrong position  "some va|lue";
the user continue deleting but the caret position it no more at the end "|lue".

What's the cause? the problem is that, during editing, you are changing (implicitly or explicitly) the value of textinput. The problem would persist also if you don't replace the html element.


Added search filter using substring match strategy

Just add a filter option to filter by substring of any filed on the document.
String _searchText = 'match me';
FirestorePagination(
.....
    searchFilter: FilterModel(
        fieldName: 'title',
        searchValue: _searchText,
    ),
.....
)

Hi @delwar36, can you explain the need for this PR? I believe this can be achieved by just adding a filter in the itemBuilder itself.
e.g.
FirestorePagination(
  itemBuilder: (context, snapshot, index) {
    final title = snapshot[index].get('title');

    if (!title.contains('match me')) {
      return SizedBox.shrink();
    }

    // return your widget here
  },
),

Hi @delwar36, can you explain the need for this PR? I believe this can be achieved by just adding a filter in the itemBuilder itself.
e.g.
FirestorePagination(
  itemBuilder: (context, snapshot, index) {
    final title = snapshot[index].get('title');

    if (!title.contains('match me')) {
      return SizedBox.shrink();
    }

    // return your widget here
  },
),

It works on list type. But in grid type it leaves blank spaces as grid dilegates dynamically creates items sizes. We maybe solve this problem using custom deligates though.

@delwar36 got it. I'll review the changes when I get some free time.


feat: [M3-7119] - Showcase VPC feedback

Description 📝
Address Showcase feedback
VPC Create

Added remove X icon to default subnet label input.
Changed button text from “Add Subnet” to “Add Another Subnet”.
Button text is “Add a Subnet” when there are no subnets added.

VPC Details - Subnets

Added Unassign Linode inline button to the Subnets table row which will open the Unassign Linodes drawer with the Linode pre-selected and the Linode select hidden.

Added helper text to the Unassign Linode drawer per the UX mocks and hide the helper text if the drawer is opened via inline Unassign Linode

Updated Subnets table empty state text
Pluralize Subnet action menu item text “Assign Linode” -> “Assign Linodes” and “Unassign Linode” -> “Unassign Linodes”.

Preview 📷

VPC Create
VPC Details - Subnets

How to test 🧪
With a properly-tagged account or with the VPC feature flag on:

Go to /vpcs/create and check the Subnets flow

You should be able to delete the first Subnet now

Go to a VPC's details page

Create a Subnet and assign Linodes to it if you don't already have one

Expand the collapsible table row and you should see Unassign Linode in the row
Clicking that should bring up the Unassign Linodes drawer with that Linode pre-selected
Unassign the Linode and ensure the Subnets table updates as normal

yarn test MultipleSubnetInput
yarn test SubnetNode
yarn test VPCCreate
yarn test SubnetLinodeRow

@coliu-akamai Just pushed up fixes for the hover state and autocomplete multi-select warning.
I don't think we'd want the Unassign Linode button to nowrap for smaller viewports bc then it would take up too much space. I asked Andrew about shortening the button text to just Unassign but he thinks the text should be consistent with  the Assign Linode naming convention.


Release 2.0.4

Questions
Answers

Description?
Release 2.0.4, needed for https://github.com/PrestaShop/PrestaShop/issues/22668

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?
N/A

How to test?
Please perform a standard testing campaign for module release. Only significant change should be https://github.com/PrestaShop/ps_customersignin/pull/15

Thanks @sarahdib & @matks


Bugfix/allow dead attachment links in new search

Checklist

[x] the contributor license agreement is signed
[x] commit message follows commit guidelines
[x] tests are included
[x] screenshots are included showing significant UI changes

Description of change
#3045
This PR is to address that if "dead" attachments appear within a search, the search would break.
This was because the search2 endpoint was not handling the case of dead attachments, and would return a 500 error to the frontend when this happened, ruining the search.
To fix this I have added an extra step to the convertToAttachment function for search2, which is to check for broken attachments.
This function checks the following cases:

File attachments not present/accessible from the filestore
Resource attachments pointing at non-existent attachments
Resource attachments pointing at non-existant item summaries
Nested resource attachments where the end of the chain fits the above three cases
All other cases (bad URLs, etc) are not covered and will not be marked as dead attachments

https://user-images.githubusercontent.com/24543345/120590631-2d4ee280-c47e-11eb-9121-8c76fb8eeca6.mp4
The output of this check becomes a flag in the returned SearchResult called brokenAttachment. On the frontend, this is handled by:

Displaying a tooltipped warning icon rather than the attachment icon
Rendering the attachment as just the filename rather than a clickable link
Preventing selection in Selection sessions of this item, including via the Select All Attachments button which now only selects intact attachments and if there are none, the button will not show at all

https://user-images.githubusercontent.com/24543345/120590456-e9f47400-c47d-11eb-87c8-49a88a27dd56.mp4
I have also added Jest Tests, both for the frontend code and for the search2 endpoint.
Also of note:

stopPropagation of clicks on broken attachments - so it doesn't toggle the surrounding accordion closed
Default thumbnnail is displayed when the dead attachment would be the thumbnail provider
The thumbnail step of convertToAttachment is skipped in the event that the attachment is marked broken, it just returns None.

Gah - codebuild found a few tests that don't include brokenAttachment. Fixing up.


field of type resource with no referenced RT does not work when embedded in another RT

on development, the template test:resource:noRT has one field, which is type = resource, with no other resource templates specified, therefore expects a URI. This template works fine, but when embedded in another template:
test:embed:resource:noRT, when you try to add the field, it kicks you to a blank screen.

The broken RT is test:embed:resource:noRT.


fix editor's loading state

closes https://github.com/TryGhost/Ghost/issues/9582
fix editor's loading bug by deleting the loading template

[X] Commit message has a short title & issue references
[X] Commits are squashed
[X] The build will pass (run ember test from the repo root - will be core/client if working from the submodule in Ghost).

Hey @evexoio 👋 Thanks for looking into this but I'm not sure this is the correct fix, the loading template is still required for transitions from a non-editor route to the editor route.
I think the bug is a bit more subtle in that it's only apparent when directly transitioning from one post to another with an async load. You'd need to use the search box to find and select a post whilst already in the editor to see the problem.

Coverage decreased (-0.1%) to 72.126% when pulling 319038bfc61194e8113f49725a33e6b47a6884c0 on evexoio:9582-fix-editor-glitch into 38ae7bf73841837ccc49a710610752e08651a1d9 on TryGhost:master.

@evexoio the correct fix here would be to add this to the editor/edit route:
...
export default AuthenticatedRoute.extend({
    beforeModel() {
        this._super(...arguments);
        let editor = this.controllerFor('editor');
        editor.set('post', null);
        editor.reset();
    },
    ...

The reason the editor/edit-loading.hbs template was causing problems in the edit->edit transition was that it was being rendered into the {{outlet}} in editor.hbs. If you have a look in that template you'll see we have a {{#if post}} conditional at the top as well as the {{outlet}} at the bottom. In the edit->edit transition the editor route's willTransition hook isn't called so the controller doesn't get reset meaning we end up with both the old post and the loading template being rendered at the same time.

@kevinansfield that makes sense, I'll fix the PR and push again.
Thanks for reviewing

@kevinansfield PR is fixed, thanks for the instructions

@evexoio I had to add a little extra logic to avoid the reset on the new->edit transition where we don't want to blow out the editor model. Without the guard if an autosave triggered a save on a new post it was causing a re-render of the editor which throws off the cursor positioning


Upgrade to swagger-spec-validator 2.3.1 (fixes #612)

Master is boken because of an update to swagger-spec-validator. This upgrades to the latest version and should fix the build.
Changes proposed in this pull request:

upgrade to swagger-spec-validator 2.3.1
debug=true will no longer continue if an operation has invalid defaults (change was in swagger-spec-validator)

Is there any way to get the debug=true behavior back? It's pretty useful for quick iterations during development when the spec is being changed and temporarily (partly) broken.

@hjacobs I can hard-pin (==) to 2.0.1 instead to preserve the previous behavior if you prefer that.
The only real change here is that default validation happens earlier. Personally I'd prefer for it to crash as early as possible when the spec is wrong, because then you know the problem is unrelated to connexion, and there are several tools available for debugging invalid specs.
The previous behavior would have avoided crashing in Operation.validate_defaults(), which also made sense given the lack of functionality in the spec validator.
Another way to handle you request would be to ignore all validation errors in apis/abstract.py, but that seems like a recipe for heaps of stack traces :slightly_smiling_face: .

:+1:

:+1:


Adding the new pascals triangle

Every thing is OK

This is looking good :+1: I want somebody else to review this too before we merge it though. @ryanplusplus @palisaide @wolf99 ?

The input is a string because we can handle NULL and "" empty input , inputs quietly as described in x-common , test data!.. , also if its a integer input , if i input NULL it thinks its 0 and returns 0 rows instead of a error as required in x-common test data...

and also , as mentioned in canonical-data.json , it requires the function to return -1 as a sort of error , is returning NULL a good idea ? , or should i return -1 instead ?

@DeathSec I think that having the input be a string is a bit odd and will be off-putting for someone doing this exercise. The x-common tests call out a null input, but that doesn't really work in C since integers (the natural type) are not nullable. So I think we should just omit that test here.

Sorry for the delay in reviewing this.
Overall the solution looks good. Just a few remaining nitpicks then I'm happy to merge. Thanks for your extra effort in improving the solution.

sure do.

LGTM, good work 👍

LGTM, thanks for your contribution!


Migrate from iptables-legacy to iptables-nft

Related #77
Currently BurmillaOS is using iptables-legacy for everything which is deprecated. On 2.0.x versions we should migrate to iptables-nft.
That needs update to:

Buildroot: https://github.com/burmilla/os-initrd-base/blob/132880d2837dc5c7630cd73c87fc88c8275715df/scripts/package#L18
Console: https://github.com/burmilla/os/blob/9bf414362507914bb2d427183c9f2f8226e43a70/images/02-console/Dockerfile#L11-L12

https://github.com/moby/moby/pull/43373 is needed for proper nftables support.


Getting started documentation

@russellgill or @DominicParent, since you too are most familiar now can either of you create a Getting Started document in artemis/docs/getting-started.rst. Minimum is

Create a conda environment for developing
Get the required dependencies
Add / build fwfr from Kira's github version
Run the test suite
Run one of the examples

I'll take a crack at it, I'm currently working on getting the whole thing working properly on readthedocs.


fixes min/max macro conflict in dragonbox.hpp

undef original min & max definitions before redefinition in detail namespace,
use parentheses to prevent macro expansion in detail::stdr::numeric_limits::max()

Thanks for this! I'll submit an issue with the dragonbox repository concerning this next week. I'll merge this into main for now.


Allow pass options directly in babelOptions rather than a config file

Is it possible to allow babel options in eslint config like:
module.exports = {
    parser: "babel-eslint",
    parserOptions: {
        babelOptions: {
            presets: [
                '@babel/env',
                '@babel/typescript',
            ],
        },
    },
};

In this case we can simply wrap configurations in a common module other than placing a standalone babel config file.
This results in a "No Babel config file detected" error currently.

we strongly need that before version 11.0, we don't have a babelrc file in our projects. Its all configured within webpack babel loader config

any other thoughts here?

Rather than duplicating this configuration, would it be possible to create a separate module for the Babel config that is then imported into the Webpack config and is pointed to in the ESLint config?
The motivation behind the change is to have Babel’s parser have the same configuration during the parsing step for both Babel and ESLint.

That is exactly what I try to achieve, I now have 3 tools that need a babel config, webpack, jest and eslint. The problem is, that babel in webpack is configured slightly different than in jest. So I already have a custom js file that exports all different kinds of babel config we need in our projects. But to get this approach to work with babel-eslint, I need this feature :)
ATM we're unable to use private class methods proposal because of babel-eslint.

Do you mind explaining why giving the path to the config file doesn't work? It seems like what is being proposed here is the opposite of what you described - i.e. having to duplicate your config in the .eslintrc file.

Thats the key, I don't have a duplicate config ;)
I' have a shared custom config file
// babel-configs.js (simple pseudo example)
const common = {}
const webpackModernBrowsers = {}
const webpackLegacyBrowsers = {}
const jest = {}

module.exports = {
    jest: { ...common, ...jest },
   webpackModern: { ...common, ...webpackModernBrowsers },
   webpackLegacy: { ...common, ...webpackLegacyBrowsers },
}

I'm curious: why don't you use a normal babel.config.js with an env block to override, for example, jest-specific plugins?

Because we use grunt and pass runtime specific options from grunt to the config (debug flag, browserlist)
// babel-configs.js (next simple pseudo example)
const common = {}
const webpackModernBrowsers = {}
const webpackLegacyBrowsers = {}
const jest = {}

module.exports = {
    jest: { ...common, ...jest },
   webpackModern: (options)  => { ...common,  ...webpackModernBrowsers, ...options },
   webpackLegacy: (options)  => { ...common,  ...webpackLegacyBrowsers, ...options },
}

We are encapsulating babel, jest, webpack, rollup, eslint and tslint in a universal cli tool for internal use, we don't allow engineers to modify babel config themselves in order to archive high consistent architecture through apps, so we don't really want to expose a babel config file which can be modified.

For anyone who's interested, I made a PR that does exactly what is requested by this issue: #784

Thank you for the issue. Now that @babel/eslint-parser has been released, we are making this repository read-only. If this is a change you would still like to advocate for, please reopen this in the babel/babel monorepo.


raidboss: renew varis-ex timeline

I have renewed a timeline for Varis Extreme. As I said in #1322 , I am not sure what skills Varis would use at phase 5.
What I wrote in the timeline file was supported by my good friend in Ixion(JP), she doesn't know about programming, but listed all the skills name for me.
If someone has more detailed logs, I am glad to see it would be fixed.

I pushed an empty timeline file here.  Hopefully you can resolve the conflicts and incorporate your changes on top of what's there from @KiroKai.  Thanks for the contributions, and sorry for the conflicts.  I think this is the first time we've had two contributors pushing new raidboss stuff for new content at the same time.

@quisquous I have fixed all the conflict and add other translation since the original one has not.
Hope it works.

Thanks so much for taking the time to put this together. Making timelines can be a painful process sometimes. Quisquous will probably have more to say about this, but I think everything I mentioned should cover what I would do when making a timeline.

Thanks for taking the time to review my stuff and point out those. If you have a complete log including entirely phase 5, could you please test it and ensure if it works? I can only enter this trial with party finder, so I have no many data about it after the second Fortius.

No problem! We all want this to be as useful and accurate as possible.
When you get a chance, could you look through the trigger file and see what changed from KiroKai's pull request? Anywhere that you see stuff you removed from their triggers, you will probably want to undo that. (For instance, the tank buster should not be a simple Responses.tankBuster() as you wrote it, since it requires somewhat special handling.) I should have reviewed all that in-line, sorry!

Yeah, you and KiroKai are right. I thought that Tanks should understand this mechanic, but the response.js seems told the Sub-Tank to Swap, so that is a wrong notice. I would review that and undo those wrong one.
But on the other hand, there would leave some other i18n things to do. So it may not be perfect.

You're right that it leaves a few more things to be localized, but that is fine. Eventually people will come along and add them. Additionally, you have already added all the JA/CN localizations, and the DE/FR ones should be relatively fast.
I think that should all take care of what I have. I'm sure quisquous will have a few more things to suggest once they have time to look it over, but I'm very pleased with what you put together here.

Didn't want to make a new pull request to create more conflicts, but if you change the delaySeconds in this trigger
      id: 'VarisEx Loaded Gunshield',
      regex: Regexes.ability({ source: 'Varis Yae Galvus', id: '4CD8', capture: false }),
      regexDe: Regexes.ability({ id: '4CD8', source: 'Varis yae Galvus', capture: false }),
      regexFr: Regexes.ability({ id: '4CD8', source: 'Varis yae Galvus', capture: false }),
      regexJa: Regexes.ability({ id: '4CD8', source: 'ヴァリス・イェー・ガルヴァス', capture: false }),
      delaySeconds: function(data) {
        if (data.phase == 'phase2')
          return 13;
        if (data.phase == 'phase3')
          return 21;
        return 16;
      },
      response: Responses.spread(),

and add this to this trigger
      id: 'VarisEx Magitek Spark',
      regex: Regexes.startsUsing({ source: 'Gunshield', id: '4E50', capture: false }),
      regexDe: Regexes.startsUsing({ id: '4E50', source: 'Gewehrschild', capture: false }),
      regexFr: Regexes.startsUsing({ id: '4E50', source: 'bouclier-canon', capture: false }),
      regexJa: Regexes.startsUsing({ id: '4E50', source: 'ガンシールド', capture: false }),
      response: Responses.spread(),
      run: function(data) {
        data.phase = 'phase3';
      },

it will make the spread callouts a lot more precise. Sorry about not putting it before, but needed more time to test it.

I have fixed the bugs found by you guys and myself, it might work better than ever.
But I don't know why GitHub action CI was not triggered.

Thanks for all of this.  I'm going to merge this now and give it a few tests and any last minute fixes so I can do a cactbot release.


Cloud Delivered Protection Level Setting

Hello, in this article there is a warning, recommending not to set the setting to HIgh, however in the block at first sight article, it's actually recommended to set it to high.
https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-antivirus/configure-block-at-first-sight-windows-defender-antivirus

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

ID: 65f0f5a3-f095-3fa4-90dd-7dee8ccb49ad
Version Independent ID: 1bec5d66-a92a-4b0d-b9d8-f43c9eab4a50
Content: Specify cloud-delivered protection level in Windows Defender Antivirus
Content Source: windows/security/threat-protection/windows-defender-antivirus/specify-cloud-protection-level-windows-defender-antivirus.md
Product: w10
GitHub Login: @andreabichsel
Microsoft Alias: v-anbic

@officedocsbot assign @mypil

@alexverboon  - Thank you for submitting feedback.
I will get this issue over to the Win10 ITPro writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

@alexverboon - From our understanding, the issue has been resolved but it may take a few days for the merged content to appear in the article. If you feel it hasn't been resolved, please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!

@officedocsbot close


Add port NAT

A port-NAT is requested to allow un-privileged ports in application pods while exposing priviledged, like 80 -> 8080 for http.
Note to reviewers
The nft operations in a transaction (before nftables.Flush()) are atomic. Meaning that an updated address set can safely be flushed before adding the updated addresses. There is no need for a clumsy and error-prone add-new-remove-leftovers procedure.

I will add tests, but the code is more-or-less done.

I have updated, rebased and removed the xcluster tests. I will att the xcluster tests in another PR (without review).


PytorchClassifier is not trained from examples/get_started/pytorch.py

Hi,
ART team,
I was trying to play with the examples included in examples. I tried to started with Pytorch. I got error  as :
TypeError: cross_entropy_loss(): argument 'input' (position 1) must be Tensor, not NoneType
I was trying to execute the file : https://github.com/Trusted-AI/adversarial-robustness-toolbox/blob/main/examples/get_started_pytorch.py
Pytorch version: 1.13.1+cu116
Platform: google colab
Thank You.

Hi @brrbaral I'm not able to reproduce your error, can you provide more information?


[Godot 4 Beta 4 C#] Godot Editor Crashes to Desktop when Loading Project with "System Error - Exception Processing Message 0xc0000005 - Unexpected parameters"

Godot version
4.0.beta4.mono
System information
Windows 10, AMD RX 6600 GPU, Intel 10400 CPU
Issue description
Godot editor crashes when loading the project. Sometimes the editor loads in the background, sometimes I just see the error message box. When the editor does load in the background, I can click on buttons in the editor but nothing works and clicking on buttons freezes the editor. Closing the error message closes Godot.

I suspect this is happening because of Godots source generators not regenerating code properly and it might have something to do with the generics I added in this commit. Note that if this commit is reverted, this issue no longer happens.
Deleting the .godot folder fixes this, but the issue comes back again when modifying the MovingEntity.cs script with enough significant changes to trigger Godot source generators.
This issue was discussed in the Godot discord in the #csharp channel. The first message that started the discussion can be found here.
Steps to reproduce

Clone the fix-225 Sankari branch
Make enough changes to the MovingEntity.cs script to trigger Godot source generators (It is important that you modify the MovingEntity.cs script, modifying any other script will not trigger this error after relaunching Godot again)

This is the code I added to trigger Godot source generators (sometimes a simple // comment change to the script won't be enough). The green marked lines are the new lines of code I added.

Launch Sankari project through Godot
Notice the error message and you will be forced to close Godot
Delete .godot folder in the project directory
Launch Sankari project through Godot
Notice how everything works fine now
Repeat steps 2 to 4 to get the error again

Minimal reproduction project
I was not able to reproduce this issue in a blank Godot project.

This commit resolves this issue. The reason I was making MovingEntity<T> a generic in the first place was to avoid the hassle of adding a new property every time I create a new animation type class. (see the changes in the commit I linked to see what I'm talking about)
I will keep this issue open because it took a good chunk out of my day (4 hours). As of writing this it is 3:19 AM, I am just glad I was able to narrow down the issue to the point where I can live without it if I wanted to.
By keeping this issue open I hope that someone will look into the Godot source generators and find any weird things going on revolving around generics so maybe in the future I will be able to bring these changes back that this latest commit reverted for my project.

I don't see how this could be related to source generators. If it's related to generics it's more likely an issue with reflection where the type is unbound.
It might be helpful to see the output in the console when the error happens, try opening Godot in verbose mode:
godot4.exe --verbose --path [Path to Godot project]

I ran Godot with --verbose flag and I spotted an error that happened right during the crash / popup error message. Full logs attached below as a gist.

Full logs: https://gist.github.com/valkyrienyanko/0094d7639d1804dac8b60adf35deeb71

Sounds like https://github.com/godotengine/godot/issues/67537

I had a different problem but with the exact same crash log as @valkyrienyanko
The editor would crash upon trying to open the project. My fix was to delete the mono Debug folder:
projectname.godot\mono\temp\bin\Debug

similar console log error in #67140.

Closing as Godot 4 Beta 8 seems to have fixed this. I hope this issue never comes back fingers crossed!

Nvm the issue came back after these 2 commits. Exact same popup / error in --verbose console. 😭
https://github.com/Valks-Games/sankari/commit/190aac79cfc4587fffcf21499538da95fc4e60d4
https://github.com/Valks-Games/sankari/commit/cb2897896535f3e27fcb82d33ae714efff8448e1

This bug has returned for me as well, I was free of it for a month 😢
Now it is caused by some conflict between building the project and plugins. I try and build the project, it fails because of an ExportPlugin (I only have one plugin and it is an inspector plugin). Then a bunch of errors appear in the MSBuild console, sometimes when I try and open these errors, it gives me the old 'Attempted to read or write protected memory'.

Linking this issue as has similar error to mine https://github.com/godotengine/godot/issues/67140


Bump knative/pkg to 1.10

Changes
This comes with a challenge, which is k8s.io dependencies, and thus replace is coming
back in the picture (sadly). This will have to be fixed once knative/pkg k8s.io
dependencies are up-to-date or at least compatible with the rest of the library we use
(go-containerregistry is the example today).
This is tracked in knative/pkg here : https://github.com/knative/pkg/issues/2759.
This should help unblocking the rest of the dependabot PRs as well.
It also doesn't change the kubernetes min version if I am not mistaken.
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>/kind misc

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[ ] Has Tests included if any functionality added or changed
[X] Follows the commit message standard
[X] Meets the Tekton contributor standards (including functionality, content, code)
[X] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[ ] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
knative/pkg is updated to v1.10

/cc @afrittoli @lbernick @jerop @JeromeJu


Specify job name via run/schedule

To make API more RESTful
Remove duplicate job

Arbitrary job name in RESTful API resource may mess up everything; while job duplication could be removed as now job submission is in POST method, not PUT.
https://github.com/retz/retz/commit/0177d18f8176441c60dbd8295078da406f5ca7d3


Big Idea 1 Sprint 4 Reflection, Team Grading, and Individual Grading

Team GRADING:
Team Grade out of 1:        0.8
While we covered the requirements of the content and length of the video, it wasn’t very efficiently done and put together. The editing was done a bit sloppy, and we tried to cram too much information into the segments, making it overwhelming and less engaging. By attempting to cover every single detail, we lost focus on the most important aspects of our work. As a result, the video lacked clarity and could have been more impactful with better planning and execution.
Team Improvements

Prioritize Key Content
Polish the Editing
Simplify Explanations
Making sure that things aren’t done last minute
Get Feedback Early

Individual Grades:
Ahaan:https://github.com/Ahaanv19/LitConnect/issues/3.
Arnav: https://github.com/Ahaanv19/LitConnect/issues/8.
Noah: https://github.com/Ahaanv19/LitConnect/issues/5.
Francis: https://github.com/Ahaanv19/LitConnect/issues/6.
Jacob: https://github.com/Ahaanv19/LitConnect/issues/4.

It would be nice if all the grades were listed at top with your individual link aways.

Fixed with feedback, hopefully is better now


Added CardanoCity to NFT project

Proposal to add CardanoCity to NFT Platforms and Projects
Platform: https://cardanocity.io/
Twitter: https://twitter.com/CardanoCity

Proposal to add CardanoCity to NFT Platforms and Projects.
Platform: https://cardanocity.io/
Twitter: https://twitter.com/CardanoCity

Thanks @nahern, but i don't see it added into the list

Thanks!


how can I add the alpha channel as input, maybe even a depth map or segmentation.

Hi there,
first, I'd like to thank you guys for sharing this with us. it's probably the cleanest deep learning repo on all of github.
I'm trying to train a paired image to image translation model using this, the input is the image of an object with a transparent background and the goal is to train it to add a specific background.
for this I generated ~10k images of different objects without and with the background I want,
I trained it but it really struggled with removing the old background,
I'm not a python/DL developer so my attempt at adding another channel as input or even adding another image as input didn't work at all.
I'm hoping you could give me some pointers as to how I can achieve this.
thanks in advance!

here's an example:
input:

expected result:

actual result:

this is after 20k+ steps


vulcan-i18n: New function formatMessage(id, values, locale)

Get a localized i18n string on the server side

I just realized that getString() accomplishes the same thing, so I am closing this pull request


Fix summary error message flashing test

Short Description

We test for the content of the message, which locally results in an error because we are compiling the babel identifiers to their actual strings. On GitHub it didn't occur because we do not run babel before running the tests. (My bad to not run the tests locally when I was implementing this)

Changes

Mock the used babel functions.

Feedback

Does that make sense to you?

I think I get it: Because we test for 'warn' we need to mock it? Couldn't we directly test for the correct babel text and it wouldn't fail in both cases?

Yes we could, but then we'd have to change the test every time we adapt the text?

We talked about it, cleared the differences, so this is ready to merge now^^


The player is over the thumbnail with YouTube

Describe the Bug
I'm using astro-embed with Starlight. When I click to play video, the player will be over the thumbnail.

Link to Minimal Reproducible Example
https://github.com/AREA44/starlight-tailwind-template/tree/71b3e7a57568f8be1b871f07637e2585011a7f25

This issue has disappeared when I updated astro-embed-youtube to v0.4.4.


Small bugsquash

Integrated all adjusts from rwfalcao, Closes #3 #4 #5, adjust the reference to logo in login page, and improve install instructions, Closes #7

Thanks @filhocf @rwfalcao


Diff-based editing

Currently, SSHEdit sends the entire file back to the host. Large files (or slow networks, such as satellite links or dial-up) can mean the file takes a long time to transfer both to the editor and back to the host.
Instead of transferring the entire file, we should only transfer the difference in the file made by the editor. Most edits are likely to be small (a few lines) compared to the size of the file (probably hundreds of lines, though unlikely for this scenario to be thousands). Although it means more processing on both sides, transferring just the diff is likely to result in significantly less network traffic, faster response times, and therefore a better user experience.

Take a look at difflib from the Python standard library. It looks like it'll fit our purposes quite nicely.

https://github.com/lengau/sshed/commit/2408a614ecfe012e9d4d7d39c624e21e40f9b90d gets us basic differential editing using unidiff.


ansible-operator: ignore existing resources at startup or conditional watches in watches.yaml

Feature Request
Describe the problem you need a feature to resolve.
I have an ansible operator that wants to reconcile its CRs when new namespaces are added to the cluster. I do this by adding this to watches.yaml:
# Watching new namespaces so the operator can automatically reconcile CRs as new namespaces come online
- version: v1
  group: ""
  kind: Namespace
  playbook: playbooks/new-namespace-detected.yml
  reconcilePeriod: "0s"
  manageStatus: False
  watchDependentResources: False
  watchClusterScopedResources: False
  watchAnnotationsChanges: False

new-namespace-detected.yml is very small - it just "touches" the CRs that exist (just sets an annotation on them) so the operator then reconciles them (the operator has "watchAnnotationsChanges: true" for the CR Kind in the same watches.yaml).
The issue is - for clusters with hundreds or thousands of namespaces, this means when the operator starts up, it will run this playbook hundreds/thousands of times. While the playbook takes at most 1 to 2 seconds to complete,  multiply that by hundreds or thousands and it will potentially spin the operator for a long period of time at startup (e.g. for every 600 namespaces, the operator will run this playbook multiple times for a total of about 10 to 20 minutes). Not only that, but I don't  even need to be told about all of these namespaces because (a) usually, when the operator starts, there are no CRs in the cluster anyway, so there is nothing for my operator to do when processing all the namespaces at startup and (b) even if there are CRs in the cluster, the first time the CRs are reconciled, the operator will process all of the cluster's existing namespaces. Thus, I really only want to be told about namespaces that are created AFTER the operator starts.
Describe the solution you'd like.
I have 2 ideas about how to avoid the long startup processing. The first is the ideal solution; if that cannot be implemented, the second is an alternative (though not the best one).
Solution Idea 1: Do NOT trigger a reconciliation at all for any resources of the watched Kind that already exist at the time the operator starts up (i.e. do not run the playbook for all namespaces that already exist at the time the operator starts). So this solution would have a flag in watches.yml (something like ignoreExistingResourcesAtStartup: true) - when this is true, all resources of the given Kind that already exist at the time the operator starts up will be ignored. Do NOT trigger the ansible playbook to run. Instead, only run the playbook when resources of the given Kind (in my example, Namespace) are created AFTER the operator starts up.
Solution Idea 2: Alternatively, I would like a conditional placed in the watches.yaml just to be able to tell the operator NOT to watch for new namespaces if a particular "setting" is detected (say, an environment variable placed on the operator Pod). In other words, ignore that particular list item in the watches.yaml - do not watch resources of the given Kind. This will be a "cutoff switch" for customers who have very large clusters (as in a large number of namespaces). Those customers would install the operator with this special setting so they can tell the operator to NOT watch for new namespaces thus saving the operator from having to consume a lot of CPU/resources at startup. The drawback would mean the customer would need to manually touch the  CR so it can reconcile when a new namespace is added. But this would just be a known drawback that you get in exchange for reducing startup time and resource consumption of the operator.

/language ansible
Workaround
A workaround would be to require the user to put a label on the namespaces that you want the operator to automatically detect. When doing this, I would be able to use the already existing "selector" feature of watches.yaml (see https://sdk.operatorframework.io/docs/building-operators/ansible/reference/watches/). But this would require the user to know ahead of time that their namespaces should be labeled properly, it would require the user to have permission to label namespaces, and it would require users to "pollute" their namespace labels sets just for supporting the operator (this is something that customers may not want to do). So, while the workaround is viable, it is not ideal.

For the record, here's what my little ansible playbook looks like that gets invoked when new namespaces are found:
https://github.com/kiali/kiali-operator/blob/master/playbooks/kiali-new-namespace-detected.yml
All it does is:

Find all instances of CRs in the cluster (there can be more than one, or there can be none at all)
For all instanaces of the found CRs, simply "touch" each one by adding/modifying an annotation with the current time, but ONLY do this if the namespace was created after the last time the CR was reconciled.

Notice a trick here where this playbook will actually throttle the annotation modification to once every minute. Thus, if you create 100 namespaces within under 60 seconds, only one time will the CR's annotation be touched and thus only one reconciliation will happen. This helps avoid modifying the CR 100 times (and potentially triggering multiple reconciliations of the CR).

@jmazzitelli this was brought up during the community meeting and we had concerns on having watches on namespaces. Could you elaborate more on the use case of having watch on namespace. Having watch on namespaces is unnecessary because: say you have to reconcile an object X (of a particular GVK, assuming namespace scoped for this context). If you set watches on that GVK, the controller will automatically queue in the events coming for them across namespaces in the cluster. Watching the entire namespace and its contents is not necessary.

Could you elaborate more on the use case of having watch on namespace.

I will try to be as brief as I can to explain what my operator is doing (this is the Kiali operator BTW).
Kiali is the UI console for Istio and OpenShift Service Mesh. The service mesh consists of microservices deployed in some namespaces in a cluster (not necessarily all namespaces). Kiali needs to observe those namespaces so it can do various things (manage and observe resources such as pods and Istio-specific CRs, etc in those namespaces).
For security purposes, many users of Kiali DO NOT want to grant cluster-wide access to Kiali. Instead, they only want to grant access to those namespaces that are participating in the service mesh - any other namespaces should be off-limits to Kiali. For this reason, there is a setting in the Kiali CR called deployment.accessible_namespaces (see some documentation on this setting here). deployment.accessible_namespaces is a list of regexes that indicate which namespaces are part of the mesh and that Kiali should be able to access. If a namespace in the cluster does not match one of those regexes, Kiali will not be granted access to see that namespace.
When a user creates a Kiali CR, the Kiali operator reconciles it. The Kiali operator will examine the list of namespace regexes specified in deployment.accessible_namespaces and for each namespace in the cluster that matches one of the regexes in this list, the Kiali operator will create a Role/RoleBinding which gets assigned to the Kiali Service Account.  Thus, each namespace that matches a regex in deployment.accessible_namespaces will be accessible to Kiali.
Now, suppose someone ADDS a new namespace to the cluster which becomes part of the mesh. The Kiali Operator needs to add the Role/RoleBinding to the namespace to grant Kiali access to that new namespace. But there is no way for the Kiali Operator to know about the new namespace (if it isn't watching for them) because the Kiali CR does not necessarily have to be touched (the new namespace might match one of the regexes already defined in the Kiali CR). The user will have to, minimally, manually "touch" the Kiali CR (change a spec setting, or add/modify a dummy annotation so the Kiali operator can be triggered to run a reconciliation). At that point, the reconciliation will be triggered and the Role/RoleBinding will be created.
 Well, the deletion will have removed the Role/RoleBinding that the Kiali operator originally created. Adding the namespace back in will do nothing to bring that Role/RoleBinding back - so essentially, that namespace is no longer accessible to Kiali, even though it originally was, and even though that namespace was brought back into the mesh.
In each case, having the Kiali Operator be notified that a new namespace has been created will allow it to automatically re-reconcile the Kiali CR and handle the Role/RoleBinding creation automatically without the user having to worry about (or even being aware this needs to be done) manually "touching" the Kiali CR to kick off the reconciliation.

/assign
I need to dig a bit deeper into potential limitation as it was brought to my attention that something like this has been discussed in the past and had performance limitations. Will do some research and update with my findings.

/remove-lifecycle stale


Change dexsearchhelp

I want to make it clear that "/ds nfe" doesn't find all not-fully-evolved Pokemon, only those that aren't in another tier, like NU or LC.

Has this been tested?
Unrelatedly, is this a bug in the other direction? The previous documentation certainly implies so. I vaguely remember someone intentionally changed it to search all NFE Pokémon and not just NFE-tier Pokémon.


Store hardware serial numbers in non-volatile storage.

Please take the time to describe the issue in detail, so that other contributors can pick it up and implement or declare it done/obsolete in case if was completed out of band.
What has to be done
Demonstrate the recording of hardware serial numbers in EEPROM, OTP, or similar non-volatile storage.
How do you know it has to be done
Follow up from https://github.com/RespiraWorks/pcbreathe/issues/31. It is more expedient to serialize in software than hardware.
Code pointers
Give some thoughts on roughly where in code do you think the necessary changes might be located.
Other
Link the issue with a milestone, add appropriate labels, and mention dependent/blocked issues if any.

This information can be stored in the flash memory of the STM32, or in the small OTP memory area as long as we definitely don't want to ever change it.

@asmodai27 implemented non-volatile storage. There is memory reserved for unit serial, but it needs to be entered manually. Maybe this could be part of the deployment scripts for when the vent is run for the first time.

We could run a sanity check in the debug scripts, which identify the serial number during initial communication with the controller, and ask the user to specify a value if the serial number is 0 (default value)
On a slightly different note, we may want to store alphanumerical values instead of simply a number.


Frequencies

Coverage decreased (-0.3%) to 95.902% when pulling 959dc1cf18eefb4a5532f6a9e248b6d8ee1124ee on frequencies into 606dc37ca1400ec625f08b857c196e79745cb420 on master.

Coverage decreased (-0.7%) to 95.486% when pulling e1587515c0cf3ea21965d28343cc767752116963 on frequencies into 606dc37ca1400ec625f08b857c196e79745cb420 on master.

Coverage decreased (-1.01%) to 95.156% when pulling ee1f092d930f76c87f7667c85a62dbeaa5f71021 on frequencies into 606dc37ca1400ec625f08b857c196e79745cb420 on master.

Coverage decreased (-1.01%) to 95.156% when pulling ec35f4a7a4047e74b5a9bbfdd8e2ea5bad61d898 on frequencies into 606dc37ca1400ec625f08b857c196e79745cb420 on master.

Coverage decreased (-0.4%) to 95.761% when pulling 1788ca084b890388a16fbf62a4a9f6000b6284d8 on frequencies into 606dc37ca1400ec625f08b857c196e79745cb420 on master.


/usr/bin/env: node no such file on Amazon Linux

Amazon Linux AMI release 2015.09
sudo forever-service install -s server.js --start test

returns saying the service was provisioned successfully but then I get
Starting machinetest
/usr/bin/env: node: No such file or directory
Service could not be started

node is installed at /usr/local/bin
And /usr/local/bin appears to be on the $PATH for both the user, sudoers and root.
Also just calling forever server.js appears to work
Any ideas?

I stand corrected. /usr/local/bin was not in root's PATH.  I only thought it was because I had set the paths available for sudoers earlier using sudo visudo.
Since /usr/local/bin is not part of the path for a default Amazon Linux image, the workaround was to set an environment variable when calling forever-service install -e "PATH=/usr/local/bin:$PATH"

this worked with Amazon AMI.
Thanks a lot.

Awesome, this solved it for me under latest Amazon AMI.

still not working forme I'm using nvm I trying this:
sudo "$(which forever-service)" install validex-cron -f " --watchDirectory ./src -w -o out.log -e err.log -c /home/ubuntu/.nvm/versions/node/v14.16.1/bin/node " -e "PATH=/home/ubuntu/.nvm/versions/node/v14.16.1/bin:$PATH" --script ./src/index.js

but not working

this can install the service but can't run the process =,(
sudo env "PATH=$PATH" forever-service install validex-cron -f " --watchDirectory ./src -w -o out.log -e err.log -c /home/ubuntu/.nvm/versions/node/v14.16.1/bin/node" --script ./src/index.js


Problem to match two wiki links on the same line

In md:
[[logo1.png]]    [[logo2.png]]

Will render in html
logo1.png]]     [[logo2.png

Equal when including images:
![[logo1.png]]    ![[logo2.png]]

renders:

Easy to workaround when you know .

will be fixed with next version

Thanks .
Just tried. It worked for the reference link   transformImageReferenceString
I guess   transformImageString and obsidianImageRegex needs also to be updated ?
![[logo1.png]]    ![[logo2.png]]

Still does not wok.
Cheers and great work again.

Ahhh yeah, will fix it later, thx for your testing effort :-)

done


batchInsert, batchUpdate and in clauses?

Can we have the features of batchInsert, batchUpdate and IN clauses ?

Could you elaborate, please.


Update allowed-locations.md

New-AzPolicyAssignment fails if the Name is longer than 24.
"New-AzPolicyAssignment : InvalidPolicyAssignmentName : The policy assignment name 'allowed-locations-assignment' is invalid. The policy assignment name length must not exceed '24' characters."
The Portal allows the Name to be 128 long. I have created an iszsue for this:
https://github.com/Azure/azure-powershell/issues/9464

@theheatDK : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@theheatDK The sample is correct as-is since the scope defined is a resource group, which does allow for the longer Name property on a policy assignment. The information provided by the engineer in the azure-powershell repo should probably be added to the Ref Doc for that cmdlet. I'd recommend submitting a PR to update it there.  You can find it here: https://github.com/Azure/azure-powershell/blob/master/src/Resources/Resources/help/New-AzPolicyAssignment.md
#please-close


Grammatical error

Duplicate letter "A" under "Planning your capacity size in advance" section, last paragraph, 5th sentence.

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

ID: f728b16f-4072-f818-5b3d-9ce27968e7df
Version Independent ID: f728b16f-4072-f818-5b3d-9ce27968e7df
Content: Manage Microsoft Power BI Premium Gen2 capacities - Power BI
Content Source: powerbi-docs/enterprise/service-premium-capacity-manage-gen2.md
Service: powerbi
Sub-service: powerbi-premium
GitHub Login: @KesemSharabi
Microsoft Alias: kesharab

Thanks for your comment, @tolarianNZ. This issue has been assigned to the doc author for review.

Hi @tolarianNZ,
Thank you for spotting this typo and for letting us know.
The typo was fixed - see Planning your capacity size in advance.
Thanks again for getting involved.
Kesem


Translated Component from Legacy APIs

Added the translation of the Component md file, from the legacy APIs section.
The route is src\content\reference\react\Component.md

I translated all the text information available that renders to the users and informs them about the Component section in the Legacy APIs. The titles are the same, but the explanations are now in spanish.
Translated string messages in some parts of the code fragments, so the messages make more sense to spanish speakers. But I didn't change all the text words there because it's hard to doing it correctly without changing much of the original code fragments.

Gracias Mateo, se me habían pasado muchos errores. Ahí ya hice commit de tus sugerencias.


Add delete address command

Close https://github.com/neo-project/neo-node/issues/814#issuecomment-900130847

@shargon Merge?

Maybe we can delete the file if it was empty? otherwise the code looks good

Never mind. He can still import private key.


feat: add environment::listen

Description
The upside of this approach is that this makes the implementation of environments cleaner IMO.
close #18264

I tried this API here: https://github.com/sapphi-red/daienjo-architecture/blob/966c60a5a94dcc388ba163ddbe9f2ba3435b2cbb/environment-pkgs/workerd/index.ts#L89-L290
I had to pass in hot always even if it might be false later. I'm making hot noop when it should be hot: false. (previous code)
Other than that, the API worked fine.

Thanks for exploring the different options for the API @sapphi-red!


StringName and NodePath are not highlighted when preceded by self

Godot version
4.0 e69b708
System information
Windows 10 x64
Issue description

Magic.
Steps to reproduce
Just see above.
Minimal reproduction project
No response

On it.


fpocket fails to run on a mmcif file with customized fields

Describe the bug
When I add custom fields to an mmcif file, fpocket is not able to discover pockets anymore (it was able to discover pockets in the mmcif file downloaded from the PDB: 4gfo)
To Reproduce
Steps to reproduce the behavior:

Run fpocket on the attached file
4gfo_customized.cif.gz

Expected behavior
Detect pockets
Desktop (please complete the following information):

OS: ubuntu
Version 22.04

fixed with https://github.com/Discngine/fpocket/pull/121


Question about the validation step during training

Hello, I checked the trainer function of the glass class used for the training, and I am a bit confused about how you validate the model during training. Do you validate the model directly on the real test data of each class (e.g. from MVTec) and then save the ckpt with the best performance?

Yes, this is a common paradigm in anomaly detection tasks. We borrowed the code for this part from SimpleNet. Since there are relatively few anomalous samples in the dataset and no separate validation set is provided, the test set is directly used as the validation set.


Density Matrix Simulator ActOn migration

Fixes #3825
Sparse and Clifford simulators both have a proper ActOnXXXStateArgs where simulator state is maintained and acted upon by various operations. This was first added in #3019 with the act_on protocol.
DensityMatrix and MPS simulators were never updated with the new protocol, leaving the codebase inconsistent and the migration unfinished. This PR finishes the task for DensityMatrix. A separate PR for MPS simulator hopefully will follow.
Aditionally, this PR introduces an ActOnArgs base class to eliminate the code duplication and type checking that was required in MeasurementGate (it had grown to four if isinstance blocks, each with duplicate bitshift/logging code), and replace it all with a single function call back into the args object.

@tonybruguier here is a template if you want to do the same for mps

Can you please add a detailed summary of the change in the PR description?
For someone with lesser context, either a reviewer or someone revisiting this PR later via git blame, it's easier to follow the code if there's a summary that we can go through.
Unless the code is very trivial or there's a detailed design discussion elsewhere (eg: RFC), I think we should have detailed summaries of the change in the PR.

@tanujkhattar I updated the description, can you TAL?

can you remove the two png files that were generated?

Done

Wait, it looks like those png files were there already, but perhaps got corrupted on my machine somehow. I'll see if I can restore them to their original state.

Done

Thanks for your hard work on this @daxfohl!

@tonybruguier Will you have time to migrate MPS or do you want me to take it?

Either way is fine. I can't get to it until this weekend, so if it's urgent, please go ahead

No, not urgent at all. This PR contained a lot of infra plumbing so it should be a smaller change on MPS side. You should be able to more or less follow what I did here for density_matrix_simulator and act_on_density_matrix_args.

I sent #3943 for review. I tried to follow your patterns, but I wasn't sure.


Add oblt-cli/setup action

@v1v can we merge this for now. I can then add the other oblt-cli actions and test it


[WIP] Update modal window

Updated modal window

Added buttons
Added text fields

@bond95 should that be like src/app/cluster/modals/AddClusterModal thing?

@bond95 should that be like src/app/cluster/modals/AddClusterModal thing? Or modals directory is unneeded?

Modal directory is needed only in case if there will be more than one modals for clusters.

@bond95 fixed

@andyvesel needs rebase

@eriknelson done


Documentation!

There's a lot to document here and I haven't done any of it :)
Not sure what the tool of choice here is... git storybook looks cool, github pages would be nice, maybe docsify? Either way, should pick one and get started!

Hi @nick-thompson
First, many thanks for this project, looks very promising.
I think the easiest for documentation is probably Github Pages + Doxygen. I'm doing it in a couple of my public repositories. See tobanteAudio/modEQ & Docs or tobanteAudio/taetl. The docs get build after every push via Travis CI. I can create a pull request with the .travis.yml & Doxyfile.in config if you want to. CI wouldn't be a bad idea anyway. :)

Hi @tobanteAudio! Apologies for the slow reply, I'm going through your comments now, thanks so much for writing.
I'm definitely interested in github pages, I think that's the smart move there. I love the idea of CI to build and publish the docs too (and just in general), but I'm a little bit unsure of Doxygen. Would Doxygen support documenting both the C++ API (like ReactApplicationRoot) and the JavaScript API (like the different View types exported by default) in a cohesive way? I think whatever tool we choose would ideally cover both seamlessly, but maybe that's too much to ask

Hi @nick-thompson I think something like Docusaurus could help here as it allows to get OOTB a nice and easy website where you can document the project. It does not generate documentation based on your source but it's flexible enough so that you can document the api and usages with markdown as you go - https://docusaurus.io/ - and then deploy to github pages || netlify.com || now.sh

Thanks @codenakama ! I definitely like the looks of Docusaurus, I think we can go ahead with it.
My time is tight right now but I started trying to put better docs in the Wiki: https://github.com/nick-thompson/blueprint/wiki. There's so much more to write there but it's a start, and at least should hopefully help kickstart a transition to docusaurus.

Writing back to report that documentation has now been moved into the repository at docs/, built with Docsify, and hosted at https://nick-thompson.github.io/blueprint/#/. Should hopefully be a much more fluid process now that documentation changes can be made right in the repo and with pull requests 🙌

@nick-thompson, This is really cool. Hadn't heard of Docsify. Be cool to add the vscode debugger setup stuff to this. Also keen to sort out documentation for the Canvas API implementation etc.

Totally! I hadn't heard of it either, but it was wiiicked simple to set up, and looks really nice. There's a lot of documentation still to write, hopefully this change makes it easier

[ ] task

** The below is a list of topics we need to document under the new Docsify system to close this issue **

[ ] Update "Getting Started" with CMake/Projucer guide.

[ ] Add VSCode Debugger guide,

[ ] Add Typescript "Getting Started" guide.

[ ] Add hot-reload workflow guide (beforeBundleEval, afterBundleEval) etc.

[ ] Add data/event flow guide (dispatchEvent, registerNativeMethod)

[ ] Add style props / layout guide (Flexbox, ViewProps etc.)

[ ] Add "Custom View" guide (registerViewType)

[ ] Add Canvas drawing guide.


[CARBONDATA-2266] Fixed All Examples are throwing Exception in current master branch

Fixed All Examples are throwing Exception in current master branch
Problem: Running all examples are showing same exception
Exception in thread "main" java.util.NoSuchElementException: spark.carbon.common.listener.register.classname
Solution: initialise the property CARBON_COMMON_LISTENER_REGISTER_CLASSNAME with empty value when creating carbon session n example within its  config object
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[x] Any interfaces changed?

[x] Any backward compatibility impacted?

[x] Document update required?

[x] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[x] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@manishgupta88  @dhatchayani please review problem come after pr #2031

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/3242/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/4474/

retest this please

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/3244/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/4476/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/3247/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/4478/

retest this please

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3990/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/3251/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/4481/

LGTM

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3993/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3994/


Event rename files

Is there any event to watch a rename of a file?

Check out these docs: https://atom.io/docs/api/v1.0.7/File#instance-onDidRename. Hope this helps.


WIP: Add github actions

Github actions pipeline prototype.

To work, PACKAGES_ACCESS_TOKEN secret needs to be set up on Github repo. That's because the pipeline as is is leveraging Github Packages product for docker image persistence which is free for public Github projects.

Image layers are cached per pull request / branch. First commit to new branch will be the slowest, subsequent should be way faster.

Docker buildkit is used - this makes it possible to use different dockerignore files per different dockerfile. That's important because when you modify libvcx, you wouldn't want to invalidate docker layer caches for libindy image. See https://github.com/moby/moby/issues/12886#issuecomment-533195318

Job assure-image-indypool builds indy_pool image (reusing layer in GIthub Packages)

Job build-image-ubuntu16-libindy builds image ubuntu16-libindy with compiled libindy (reusing layer in GIthub Packages).

Job build-image-ubuntu16-libvcx - builds image ubuntu16-libvcx with compiled libindy, libnullpay and libvcx

Job build-image-ubuntu16-vcxagency builds image with dummy cloud agency binary.

Job test-libindy runs unit tests for libindy against local pool

Job test-libindy-wrapper-rust runs unit tests for libindy rust wrapper

Job test-vcxagency runs unit tests for dummy cloud agency

Job test-libvcx - runs unit tests for libvcx against local pool

Job build-libindy-run-unittests compiles libindy on host Github Actions machine and runs unit tests. This is bit experimental, it might be bettter to run unit tests within image built in build-image-ubuntu16-libindy. The upside of this host-approach is that we can stay consistent when testing on MacOS and Windows as Github Actions offers hosts on OSX Catalina and Windows Server 2019 as well.

Missing:

Python, Java, NodeJS Libindy wrapper testing
Libvcx wrapper testing
Builds on operating systems other than Ubuntu 16.04
Probably some more?

Also there's surely stuff to refactor, there's quite a bit of repetition in this GA definition right now.
As I realized doing this, minor but cool thing about Github Actions is that people could actually run pipeline in their own forks without doing PR first. Also, it's easier for someone to propose modifications to GA definition.

@jovfer there's still work left to do here, but can we experimentally merge this to enable collaboration on Github Actions? To have these actions working, secret PACKAGES_ACCESS_TOKEN needs to be set for this repo.
I was thinking we could use   https://github.com/sovbot user to generate him an access token with  read:packages, write:packages rights, then use that for that secret. What do you think?


Disallow 1d cosine

(first commit is unrelated, just something that bugged me while i was going through the code)

@jbellis I realised after approving this that this doesn't include the change to VectorMemtableTest that prompted this change in the first place. We need to change dimensionCount = getRandom().nextIntBetween(1, 2048) to start at 2.


Failed to download SlimeVR Server

Works for me. The GitHub Certificate is valid and was not changed in this days. Seems to be on your side (check your System Date, Firewall, Antivirus).
It try to download following file in that step:
https://github.com/SlimeVR/SlimeVR-Server/releases/latest/download/SlimeVR-win64.zip


update install_using_binaries.md

Codecov Report

Merging #373 into develop will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #373   +/-   ##
========================================
  Coverage    52.90%   52.90%
========================================
  Files          244      244
  Lines        23044    23044
========================================
+ Hits         12191    12192    +1
+ Misses        9442     9440    -2
- Partials      1411     1412    +1

Impacted Files
Coverage Δ

bfe_util/fixed_pool.go
83.33% <0.00%> (-16.67%)
:arrow_down:

...e_modules/mod_trust_clientip/mod_trust_clientip.go
42.85% <0.00%> (-3.30%)
:arrow_down:

bfe_http2/server.go
71.50% <0.00%> (ø)

bfe_spdy/server_conn.go
78.98% <0.00%> (+0.88%)
:arrow_up:

bfe_spdy/frame_write.go
50.50% <0.00%> (+1.01%)
:arrow_up:

Continue to review full report at Codecov.

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


1433 trigger process cleanup

There is still a race condition lurking here I suspect, but this should fix the main problem. Will need to revisit this.

Looks good!


Git session Update Firstname_Lastname.md

Great job, just create another commit along with a filename with you name and delete the previous file!

Also your the first person to hit a merge conflict so you got to learn something new :)


Internals: various fixes for memory safey and reduce static analysis complaints

jpeg output: Extra memory check
TS: batch texture call fixed to handle any number of channels
TS: assert to guard against possible null pointer dereference
oiiotool printinfo: clarify assertion for the sake of static analysis
jpeg2000 reader: assertion to ensure we don't dereference a null pointer

Some explanation:
I think the place in texturesys.cpp where we switch from allocating 4 components of those variables to using OIIO_ALLOCA ws a "real bug", though one that nobody will likely ever have encounterd since you'd need to make a texture call asking for >4 texture channels to be returned. (OSL, which is how most people end up with the TS in their lives, won't ever ask for more than 4 texture channels.)
The other changes here are, as far as I know, "not real bugs". The added assertions merely (a) confirm the guarantees we believe the code already makes, though it's nice to have the extra verification, and (b) will cause the static analysis to stop marking bugs there. What I mean by that is:
int func(Foo* bar) {
    return bar->baz;
}

might flag in static analysis that we could be dereferencing a null pointer, because it can't tell what pointer might be passed to func, which just blithely dereferences it. But if we change it to
int func(Foo* bar) {
    OIIO_DASSERT(bar != nullptr);
    return bar->baz;
}

then there is no more static analysis error because it sees (in the macro expansion of OIIO_DASSERT) that if bar is nullptr, it will take a different code path to error and abort, and so there are no code paths that get to bar->baz that allow bar to be null. We run the static analysis on a debug build, so those assertions are fully active. In release/optimized builds, the OIIO_DASSERT goes away, so there is no runtime penalty for the extra checks in production code, but there is in CI, analysis, and debug builds.

No objections -> merge


Update to released version of ember-cli-page-object v2

Upgrades the version of ember-cli-page-object from the beta version (~v2.0.0-beta.3) to the stable released version (^2.1.0) so that it is compatible with a wider range of ember-cli-page-object versions. Additionally, updates
the engines specification to match the compatibility of ember-cli-page-object.

Awesome. Yeah IIRC the reason this was pinned to the beta was because the dependency had dropped support for a version of Ember still supported by Ember Table (and used by Addepar at the time).
Happily that is no longer the case, and we will be cutting a new major of Ember Table https://github.com/Addepar/ember-table/issues/995 with support for only Ember 3.28+ in the coming weeks.
Let me check if this seems like it is unblocked, and if so I could merge this and cut a new minor  version (non beta) with this change.

Thanks @mixonic for taking a look and for the explanation on compatibility. Fortunately it looks like we're already on a compatible version of Ember, so If this can make it into a pre-release version of the next release, that would help us out, too.


[Core][Minor][Test] Fix comment and unnecessary code in DAGSchedulerSuite

What changes were proposed in this pull request?
Fix comment and unnecessary code in DAGSchedulerSuite
How was this patch tested?
N/A

Test build #77598 has started for PR 18165 at commit 0a71150.

Test build #77598 has finished for PR 18165 at commit 0a71150.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77598/
Test PASSed.

Merged build finished. Test PASSed.

This honestly doesn't seem like the kind of thing worth opening a PR for

Ok, I'll close this and merge that in my next PR.


fix grf bug

What type of PR is this：

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

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

when pipeline_dop is times of instance_num,  drastic data skew occurrs when input data is partitioned among PipelineDrivers, in such cases, when constructing GRF,  the HashJoinBuildOperator whose hash table exceeds 1024000 keys arre fail to construct GRF, but merge_bloom_filters function constructs invalid GRFs.

We need test the execution engine in scenarios that :

Extreme data skew, contains large partition, large bucket
Arbitrary DOP
A larger cluster with the same hardware resource

[FE PR Coverage check]
:disappointed: fail : 0 / 2 (00.00%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/planner/HashJoinNode.java
0
1
00.00%

:large_blue_circle:
com/starrocks/planner/PlanNode.java
0
1
00.00%


docs(policies): rework intro page and add concepts

Have a central concepts page to link from there to different other pages.
Change pages to make policies intro docs simpler

Adds page: https://deploy-preview-1956--kuma.netlify.app/docs/dev/introduction/concepts/
Add merge the policy reference to just be: https://deploy-preview-1956--kuma.netlify.app/docs/dev/policies/targetref/

@Automaat @michaelbeaumont I think we're good. If you can take another look. With the reintro of Vale I ended up having to do a lot of unrelated changes...


Switch to Python 3 (only)

This repo is pretty outdated and obviously unmaintained atm.
The below changes (while not fixing all of #26) are IMHO an important step towards proper Python 3 support and where done by @dheatovwil.
In an effort to update this codebase for the requirements of a future py-ipfs implementation, I would therefor kindly ask for this GitHub organization (and ideally also the corresponding PyPI packages) to be handed over to more active members of the community attempting to build a usable version of py-ipfs.
I'd suggest the following people to take over these projects:

@AliabbasMerchant: Has already helped out in several IPFS Python related projects and continues to provide good code when he has time.
@alexander255 (me): While I'm myself not active in building py-ipfs I ended up being its project coordinator for now (a job I like quite a bit more, than actual coding anyways), I'd mostly use my position to add other team members and necessary/sensible.
@dheatovwil (if he's still around): Initiated the work on this repo half a year ago, I'll have to see if he's still around / interested in this through.

I know this may come somewhat unexpected, but since you literally have withdrawn from almost all development for almost 3 years @jbenet, I thought confronting you like this may be more effective than weaseling around. 😉

It would be nice to see new maintenance of the datastore library and python 3 support.
I've tested this updated version a little bit on python 3, and got an error using the filesystem backend:
  File "datastore/core/serialize.py", line 200, in put
    self.child_datastore.put(key, value)
  File "datastore/filesystem/__init__.py", line 184, in put
    self._write_object(path, value)
  File "datastore/filesystem/__init__.py", line 140, in _write_object
    f.write(value)
TypeError: write() argument must be str, not bytes

It can be fixed by changing the open() calls to be binary:
with open(path, 'wb') as f:
...

with open(path, 'rb') as f:

I was quite inactive in the past few months, but I guess I'm back, will need some time to keep up since I'm quite out of the loop actually.
My time is kinda limited now, but AFAIK the primary goal is all about resolving compatibility issue with the dependents, which I think I still can handle.
Just feel free to inform me if this is actually something much bigger than I thought, I'll see what I can do.

It would be nice to see new maintenance of the datastore library and python 3 support.
I've tested this updated version a little bit on python 3, and got an error using the filesystem backend:
  File "datastore/core/serialize.py", line 200, in put
    self.child_datastore.put(key, value)
  File "datastore/filesystem/__init__.py", line 184, in put
    self._write_object(path, value)
  File "datastore/filesystem/__init__.py", line 140, in _write_object
    f.write(value)
TypeError: write() argument must be str, not bytes

It can be fixed by changing the open() calls to be binary:
with open(path, 'wb') as f:
...

with open(path, 'rb') as f:

It seems that str is expected internally.  For now I've changed it to r/w in byte mode, and convert to byte when writing if str is given, but I will look deeper into this issue.

Taking a quick look I'd definitely think that values should be binary strings only (encoding left up the application), while key names should be Unicode-strings (internally encoded to UTF-8 or UTF-16) if required by the given backend.

Hello
@alexander255 Thank you for tagging me!
I would definitely like to contribute.
I will take some time to go through the repo, but after that, I will definitely contribute.
@dheatovwil  or @alexander255  (or someone else for that matter), It would be better if you assign me some task (preferably something not so urgent, so that I can first go through properly and then start off).
(PS: I have been working on something quite similar to the concept of "datastore-agnostic, allowing datastores to be swapped seamlessly", so I think I can properly fit in here. You can check it out here: https://github.com/spaceuptech/ (Especially the python API and the main repo, "space-cloud")

@alexander255 @dheatovwil
Seeing that this is quite a small project, why don't we just make a new copy of it, directly intended for Python 3?
I think I can do it in approx a month

@alexander255 @dheatovwil
Seeing that this is quite a small project, why don't we just make a new copy of it, directly intended for Python 3?
I think I can do it in approx a month

I have no problem with that.  I can provide some help if you need.

Your're right of course! I was hoping to continue this project as-is, but I guess it's not happening so let's yield to reality here. :slightly_smiling_face:
I've created an “official” fork here: https://github.com/ipfs/py-datastore
Please send all PRs to that repository instead, so that we may actually get some work done.
I also forked off https://github.com/ipfs/py-datastore.leveldb which will need to read go-ipfs management data; the other backends do not look useful at this time.

@AliabbasMerchant: I've missed your PS unfortunately. Since that thing is written in Go we cannot replace the datastore API itself with this. It may be suitable as a backend through.


How to handle lazy loading on table

I have question how to handle go to last scroll position?how to get last scroll position also. because i want to create lazy loading on table

Hi, for now you can get the ref for the scrollbars container and then use the normal native scroll access functions?


Added doctr to travis build.

Let's see if this works.

@ericdill @parente Not entirely sure why the sphinx stuff is moaning.

@mariusvniekerk Try adding a blank line between "Complete Reference (API)" and the line above it.
If you make your PR writable, I can experiment if that newline doesn't solve it.

The whitespace fix has to go in the bash readme hack script. There's other problems after that as well.
I tried to push to your branch but can't.  Can you check the access permissions?

There's various deps missing that are causing imports to fail: pandas, pyyaml.

Looks like we're green now.   Anything else we want to add here ?

Is it posting to RTFD properly? If so, :shipit:

Well it pushes to gh pages.  But should be fine.

https://travis-ci.org/MaxPoint/spylon/jobs/160656977#L758
Looks like the hackery we do with index.rst confuses it.  I'll make a follow-on

Follow on in #17


Configure GitHub to set 'master' as the default branch

The default branch on GitHub is main.
But all the code is on branch master.
Result: the repository appears to be almost empty... until we manually select the master branch.

Apparently master has been now renamed to main, so there is no more issue.

Development moved to generics branch.
master branch has been abandoned. Early commits can be found by tags though.


Remove i686 install docs and fix x86_64 install command

Description

The installation documentation for i686 has been removed because Nodex Agent does not build binaries for the i686 architecture.
The commands in the installation documentation for x86_64 were incorrect and have been corrected.

LGTM!


[rv_core_ibex, sival] Extend rv_core_ibex testplan with SiVal tests

This moves the rv_core_ibex testplan into a seperate file, extends it with new tests and the extra SiVal test information fields. Additionally features have been added to the rv_core_ibex hjson data.

Note I've put all the Ibex tests into SiVal stage 1. The reason for this is Ibex is obviously heavily used in all of the other tests, so this set of tests should be considered initial tests to check Ibex itself is working correctly before we test other things.
In particular we'll need a way to load/run these tests by injecting them into SRAM via JTAG, ideally before the mask ROM can execute at all (uncertain if we can actually halt that initial execution even on the DEV/UNLOCKED life cycle state)

That said, CI looks like it's failing at the moment. Can you try running the quick lint locally:? It might show what's come unstuck!

CHANGE AUTHORIZED: hw/ip/rv_core_ibex/data/rv_core_ibex.hjson

CHANGE AUTHORIZED: hw/ip/rv_core_ibex/data/rv_core_ibex.hjson