Initialize the memory pool with it's "real" values

Use BAP to read memory from various constant pools, e.g. .rodata (and possibly others) in order to avoid some false positives.
It seems that the best way to do this is to use Bap.Std.Image, along with the Ogre.Query.select functionality over Scheme.section (or is it Scheme.named_region?), to actually collect all those bytes and assert the relevant memory constraints.
Note that this probably conflicts with some of our existing options (notably rewrite-addresses) so we need to provide this functionality as a flag.
I'm also not sure what to do if the data differs between the binaries in the comparative mode.

Tagging @nickroess for interest.

First remark: The only way to implement this (it seems) without doing horrible hacks is to ingest a Project.t instead of what we currently ingest, i.e. a pair of program term * Target.t.
This requires a rewrite to the front end of CBAT.
In addition, the reason we work with programs rather than projects is because loading the project multiple times in our large-scale analyses is very slow.
We propose the following solution: if the whole poject info is not needed (init-rodata flag not set), we create a dummy project, with only the program and target filled in, and cache that if needed.
This could be a bit finicky, since there's no easy way to know if we're loading a cached "fat" project or a cached "thin" one without trying to read some fields. Not sure what the right behavior is (probably check that we are reading from an "expected" cache).


[Feature] Create new configuration abstraction for a Project

Is your feature request related to a problem? Please describe.
Currently, dbt-loom does not have a good way to leverage a dbt project's restrict-access configuration. This config is important for limiting cross-project access to protected and private nodes. Since this is an entirely new file to load, we do not currently have a defined path for loading this information.

flowchart LR

  subgraph project_a
    dbt_project.yml
    manifest.json
  end

  subgraph project_b
    project_b_project[dbt_project.yml]
    project_b_manifest[manifest.json]
    dbt_loom.config.yml

    subgraph dbt-loom

      ManifestLoader

      Plugin

    end
  end

  manifest.json --> ManifestLoader

  ManifestLoader --> Plugin

  dbt_loom.config.yml --> Plugin

  dbt-core

  Plugin --> dbt-core
  project_b_project --> dbt-core
  project_b_manifest --> dbt-core

Describe the solution you'd like
I'd like to be able to define a Project, and with this project a location for its dbt_project.yml file and an associated manifest.json file. This should support all of our existing artifact sources where possible.

flowchart LR

  subgraph project_a
    dbt_project.yml
    manifest.json
  end

  subgraph project_b
    project_b_project[dbt_project.yml]
    project_b_manifest[manifest.json]
    dbt_loom.config.yml

    subgraph dbt-loom

      ManifestLoader
      ProjectLoader
      Plugin

    end
  end

  dbt_project.yml --> ProjectLoader
  manifest.json --> ManifestLoader

  ProjectLoader --> Plugin
  ManifestLoader --> Plugin

  dbt_loom.config.yml --> Plugin

  dbt-core

  Plugin --> dbt-core
  project_b_project --> dbt-core
  project_b_manifest --> dbt-core

To configure this, we can introduce a new optional top-level concept of a Project.
dependencies:

  - name: core
    description: All common core dependencies across our `n` base projects.
    artifacts:
      - type: s3
        config:
          bucket_name: com.example.dbt_artifacts
          object_prefix: latest/

   - name: revenue
     description: A proof-of-concept local-only revenue reporting project.
     artifacts:
        - type: file
          config:
            path: path/to/manifest.json
        - type: file
          config:
            path: path/to/dbt_project.yml

Describe alternatives you've considered

Have restrict-access configured in the dbt_loom.config.yml file instead.
Don't support restruct-access at all.

Additional context

It would be ideal to keep the door open for bulk loading of artifacts, as described in #31

Isn't it dbt's job to enforce this behavior? Why should a plugin author need to do this? Provided you set this in your dbt_project yml, my expectation would be that the manifest json stores this information and it is respected in dbt core while managing refs. Otherwise it's N times the repeated work for every plugin author to respect the restrict-access setting -- since the only surface area of plugins is either adding nodes or dumping artifacts AFAIK, it should be baked in. Which BTW [the extremely shallow plugin API implementation] sort of points to dbt-core teams narrow focus on enabling cloud/enterprise features and not innovating on their OSS software from a resourcing/engineering standpoint.

Some thoughts here, @z3z1ma.
The mechanism for respecting/enforcing the restrict-access parameter of a project is baked into dbt-core. Rather, the data flow for this information in injected in at invocation. Based on what I can tell from the dbt-core source (eh 🤷🏻), it looks like dbt Cloud may be injecting the dbt_project.yml from upstream projects into downstream projects during invocation, thereby allowing dbt-core to run the check. In our case, we are coming into the party late and need to artificially inject this dbt_project.yml via patched wrappers.
So, we have a common need for downstream projects to KNOW this configuration value for upstream projects. This means that we either load the upstream project's dbt_project.yml file (which is what I suspect dbt Cloud is doing, since it already has all the code), or we have devs manually configure this value, which isn't ideal as we've both pointed out above.
I recommend re-reading the proposal again and dig deep into how this solution might work!

Thanks @nicholasyager!
I totally get how what your saying will work. I'm saying that PluginNodes in dbt-core is missing critical info (such as an optional dict of parent project info). And no matter how I dice it up, having to traverse an MRO across like 10 different files in dbt-core starting from the is_invalid_*_ref functions just to figure out where runtime_config is originally generated (which is where the dependencies mapping lives that is currently mutated via monkey patch) is not great. So the people forced to tackle the complexity are plugin authors, including dbt's own private plugin which is services the capabilities in cloud... So when I say it should be in dbt-core. I mean, more broadly, it shouldn't require monkey patching to get injected nodes to respect their parent/source project's configuration. Or to respect private/protected as a concept from 'plugin nodes' which is literally the primary concept introduced by dbt core coupled to the existence/creation of this plugin interface.
So TLDR
Speculating the solution is simple enough
MeshRunnableConfig needs to be replaced with a native dbt Project object. We can use a global/nonlocal dict of project_name -> Project
The implications however are that we are exposing a (in my opinion a hard to miss) gap in the upstream codebase that surprises me was not thought through in this way.

Speculating the solution is simple enough
LoomRunnableConfig needs to be replaced with a native (or duck typed) dbt Project object. We can use a global/nonlocal dict of project_name -> Project

Cool. This is aligned with my thinking. I'll ponder some reasonable stepping stones that get loom's configuration working in this direction in a backwards compatible manner.
Regarding the complexities of managing plugins using the interfaces provided, I totally understand -- you're commenting on an issue thread for a dbt-core plugin 😉🤣  Let's be charitable to the devs working on dbt-core, and operate with an understanding that they are working under similar resource, timing, and commercial pressures as the people who work for dbt Labs' competitors who happen to leverage dbt-loom. We're very much operating on the fringes of what dbt Labs intended folks to do, and that is what makes this all the more interesting an exercise.

Agreed. Don't mean to come off the wrong way. I am as much a contributor to OSS as I am a critic to software. They go hand in hand sometimes and have nothing to do with any company as much as it does a collection of python files which comprise the software. I would definitely PR these opinions upstream if I was still using dbt at work lol
Appreciate you @nicholasyager and all you've done here. Dbt folks too.


operators [CI] multicluster-operators-subscription (0.3.0)

Signed-off-by: Xiangjing Li<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.
Updates to existing Operators

[X] Did you create a ci.yaml file according to the update instructions?
[X] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[X] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[X] Have you tested an update to your Operator when deployed via OLM?
[X] Is your submission signed?

Your submission should not

[X] Modify more than one operator
[X] Modify an Operator you don't own
[X] Rename an operator - please remove and add with a different name instead
[X] Modify any files outside the above mentioned folders
[X] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[X] Description about the managed Application and where to find more information
[X] Features and capabilities of your Operator and how to use it
[X] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[X] Human readable name and 1-liner description about your Operator
[X] Valid category name1
[X] One of the pre-defined capability levels2
[X] Links to the maintainer, source code and documentation
[X] Example templates for all Custom Resource Definitions intended to be used
[X] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

@J0zi @mvalarh  The PR has passed all the tests. And I have added my name to ci.yaml as reviewer. But the PR is not merged automatically.  Could you help check what is wrong here, and help merge the PR is possible?
The PR is required in our coming release. The new RC build will be on Wednesday. Could you help merge the PR with higher priority? Thanks For your help as always.

/merge possible


Plan initial content for website

The raison d'être for this organization: building a quick and easy website for people to be able to find information about COVID-19 and how to find resources for their open source ecosystem problems.
This website needs to have the following minimally:

What the mission of the website is: "Helping the open source community weather the coronavirus"
Where to find information on Coronavirus: (elsewhere)
What sort of resources we offer:

Reverse scholarships
Why you should cancel your meetup / conference / gathering
Resources for holding remote conferences

Remote hackathons?

Resources for working remotely or at home
Identifying organizations that need funding which normally comes from conferences to continue their work
Identifying at-risk individuals and projects
Help facilitiating aid within your OSPO or company
Tech resources for health workers working on coronavirus

A way to get in touch publicly
A way to get in touch privately
How to get involved with this WG
Sponsors
A standard CoC for this space
License and legal liability waiver

I think we could streamline the content even further in order to get to a faster MVP.

Mission
External Resources
Contact Options (open an issue or google form)
Get Involved

We could seed Issue Templates to handle the different kinds of help requests (Help Organizing Virtual Events, Release/Developer Support, Individual Financial Relief, Organizational/Project Financial Relief, etc) with a fairly open ended Google Form for people to raise more discrete requests.
If we start here, we can expand on the external resources and break them into distinct categories, peeling non-MVP content off into separate issues.

I believe this issue can now be closed.

Thanks.


Implicit file.name and path fallback in Stack.__upload() leads to errors

The upload syntax doesn't work very nice with files as the second argument.

with Stack(username='foo', password='bar', hostname='stack.example.com') as stack:
    stack.mkdir('/music')
    stack.upload(file='foo/bar.txt', path='/music/foo.txt')  # Maps to: '/music/foo.txt/foo/bar.txt'

Rewrote API to be Stack.upload(file=..., remote=...)


DeleteTagCommand functionality update

Addendum to #104
Previously, DeleteTagCommand accepted inputs like the following:
tag-del-p 1 t/friend
in order to delete the tag friend from the first person (index 1) in the contact list.
Updated functionality
DeleteTagCommand no longer requires the tag qualifier /t in order to add tags.
tag-del-p 1 friend now does the same thing that tag-del-p 1 t/friend did previously.

Codecov Report

Merging #105 (ef2e87d) into master (1443d73) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #105      +/-   ##
============================================
+ Coverage     76.78%   76.81%   +0.02%
  Complexity      824      824
============================================
  Files           121      121
  Lines          2421     2424       +3
  Branches        280      280
============================================
+ Hits           1859     1862       +3
  Misses          474      474
  Partials         88       88

Impacted Files
Coverage Δ

...va/seedu/address/logic/commands/AddTagCommand.java
83.33% <ø> (ø)

...u/address/logic/parser/DeleteTagCommandParser.java
100.00% <100.00%> (ø)

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Rename AssistiveText to SupportingText on the M3 controls

We are excited to announce that we are working on a new generation of controls based on Material Design V3, which we will be releasing soon.
This ticket has been included/fixed in the upcoming version of this NuGet package, which will include both current and new generations of controls.


Temporarily mapping d-pad to LS

Hi there. So, I have a couple old games that only pay attention to the left stick, as well as games where it would benefit to be able to use either method. The impression I got from the documentation is that I should be able to load a profile to do this, something like this:
gamepad.left = -left_x
gamepad.right = +left_x
gamepad.up = -left_y
gamepad.down = +left_y

If I echo load profiles from dpad_to_ls, the log indicates it does do that, but testing the controller in antimicro shows the dpad is still sending dpad inputs and not left stick inputs. Am I doing this wrong?
In addition, I'm not clear on how I would revert these changes when I'm done playing a game that would use this.
Thanks for everything, I've been trucking along with zero trouble since the last time I came here. :D

That looks good. Does the remapping work for other output events? Or is just the stick mapping giving issues?
My guess is that you are using a controller that doesn't have four digital dpad events (left,right,up,down), but instead has two axes ("leftright" and "updown"). You should set all six events in order to handle both devices with four dpad events and devices with two dpad axes.
gamepad.left = -left_x
gamepad.right = +left_x
gamepad.up = -left_y
gamepad.down = +left_y
gamepad.leftright = left_x
gamepad.updown = left_y

I felt that trying to automagic axes into separate digital events would be a bit too much.
To reset, just set them back to their original mappings:
gamepad.leftright = (left,right)
gamepad.left = left
# ... etc.
When in doubt, use print profile <device> to see the profile in use, after you've done the mappings above. Based on aliasing, it might differ from the "gamepad" profile.

Thanks for replying.
I haven't tried remapping other stuff, just the d-pad because it's the only practical application for my use cases at the moment.
Adding in the leftright and updown entries makes it work... kinda. The inputs don't stay active when I hold a dpad direction down. In antimicro I see the direction light up for a few milliseconds then immediately go off.
Reverting the mapping change works fine, though.
Also, tangentially related: I remembered that I have to chmod the fifo in order to send commands to it. I'd like the fifo to be world-writeable so that normal users can configure it at runtime; can we make a config option for that? I can make a separate issue for that if you'd like.

I think the not staying active issue might be it being clobbered. A thumb stick might be having some jitter near zero, and those new near zero values overwrite the events the dpad.
The current devel branch reworked how thumb sticks are processed, including filtering out spurious near zero events in the deadzone. The new filtering should be present when the profile looks like
gamepad.left_x = nothing
gamepad.left_y = nothing
gamepad.(left_x,left_y) = stick(left_x,left_y)

which is the new default. Note that the two raw axes are unmapped, and instead there is a translator that works on them jointly.
As for FIFO permissions, the devel branch also changed the umask so that the created FIFO has group-write permissions. I think that is good enough for the usability/complexity trade-off, and for now the user can just directly add more permissions after creation.
If there is a strong reason for adding config options for the permissions, I'd be willing to reconsider that decision.

The devel branch fixes all my problems once again, haha! After building devel, my dpad-to-left-stick profile works just fine with some cursory testing. I also think group write for the FIFO is an absolutely sensible default. I've added my normal user to the gamepad group and that works just fine too, without letting the normal user see the original gamepads.
Thanks again. I imagine the profile(s) I've made for this use case will be useful to multiple users; want me to make a pull request against MG-Files?

Glad to hear it. The devel branch should be reaching master "soon". There's still some kinks in the syntax I'd like to work out about the whole translating-events-jointly thing where the left side needs multiple input events..
Yes, please submit that PR.


[DC-734] Create an Integration Test Cleaning Rule Example

creates a base class that handles test setup and teardown
creates an inheriting class that can be used by rules that drop rows
creates an example of a class that uses the drop rows cleaning rule

@calbach I've left three conversations unresolved.  Please review and respond.

Have a look.

I had to rebase due to conflicts in curation/data_steward/utils/bq.py.  Nothing big.  Just comment changes.


Support AOT deployment

In production pipeline, when I train a AI model to deploy on my device, I also need physics sumulation work with it. AOT deployment will be better way to use this framework into production.

Hi @yangfengzzz , can you elaborate on what you would need for AOT deployment?
Is the problem compiling kernels after deployment? It is possible to collect the kernel cache (see location printed at wp.init()), and then distribute those with your app.
You would just need to manually update the warp.config.kernel_cache_dir to read them from your desired location.
Let me know if you need something else.

It is possible to include the warp.dll inside engines like Unity/Unreal - there is a native interface to this lib.:
https://github.com/NVIDIA/warp/blob/main/warp/native/warp.h
You can use this to load the pre-compiled kernels, access mesh functions, etc.


pull request for e2e test at 01/10/2017 15:45:10

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


Enhancement suggestion: inherit attributes for components/widgets

Hi,
Components appear to be extremely great stuff. However, as I already mentionned in #1454, they are  IMHO crippled by one detail. One of the main pitfalls for components is that they don't behave like "normal" html dom nodes. You can't set <widget style="width:200px" /> except if it's specifically defined in the template. This, in turn, leads to component templates like this:
<a href='{{href}}' media='{{media}}' target='{{target}}' type='{{type}}' id='{{id}}' class='{{class}}' style='{{style}}' draggable='{{draggable}}' {{#hidden}}hidden{{/hidden}} title='{{title}}' onclick='{{onclick}}' ondblclick='{{ondblclick}}' onmouseover='{{onmouseover}}' onmouseout='{{onmouseout}}' ondrag='{{ondrag}}' ...

...even for trivial components you have huge chunks of "attribute forwarding". It is definitely impractical and error-prone.
The enhancement suggestion would be a flag
inheritAttributes: true/false
When set, all top level elements would inherit all default html attributes, except if it's overriden by some other value in the template itself. If it helps in any way, restricting components to a single DOM element would be ok too in my opinion. This would drastically help making simple components/widgets.
Cheers

@dagnelies  it'd be nice to have something like this already implemented, but it's not so easy to design, i can image. What if I want to set an attribute jut for the component and not for the first node of the template? or maybe i have 10, and want just half? Someone said about a switch in the options, but I think it can be done as said before using some kind of decorator.
Implementation:
<widget style="width:200px" config1="12345" />
Template:
<a href='{{href}}' media='{{media}}' target='{{target}}' type='{{type}}' id='{{id}}' class='{{class}}' style='{{style}}' draggable='{{draggable}}' {{#hidden}}hidden{{/hidden}} title='{{title}}' onclick='{{onclick}}' ondblclick='{{ondblclick}}' onmouseover='{{onmouseover}}' onmouseout='{{onmouseout}}' ondrag='{{ondrag}}' ...
I dont want config1 to be as attribute in my , so I can see two ways to implement this:

Have a list of reserved keywords for attributes, exactly those standard for html elements, so they get automagically "copied".
Have a prefix for anything else you need copied but it will get things a bit ugly. :(

I like number 1. this way forces developer not to use html keywords as variable names.
Anyting like, data- , id, class, style, and so on, gets transferred to the first element of the template, heck, i can imagine setting the index for that, so I might wrap the template in a  for example and set the index=1 on my ractive instance, so it wont copy the attributes to the div, but to the first child node.
And of course, anything else not defined as "standard keyword attribute" wont be copied, but instead go straight "data".
What you think?

I'd make it even more simply: every binding that's not used in the template is inherited as regular attribute.
In this example:
...template: '{{yield}}
everything besides {{type}}, {{class}} and obviously {{yield}} would be inherited. So that:
<btn type="primary" href="myurl" style="padding:100px">My linked button</btn>
Would be translated into:
My linked button</btn>

And how would you have an attribute in  skipped from being added to the element?
Like i said before, if I have parameter that are not html related, but something like a config value for my component, why would it be translated to my element? it will just pollute it.

I would favor the verboseness of having to manually forward the attributes instead of implicitly inheriting attributes. Too magical, might bite back.
There was a discussion somewhere that talks about forwarding an object as a whole as a binding to the component. Not sure if it was implemented, I couldn't find the tests.:
// Parent binding. Imagine "." had href, text and target
<Component this="{{.}}" />

// Child template.
{{ text }}

I would imagine, for this case, you'd want the template side to do the same thing:
// Parent binding. Imagine "." had href, text and target
<Component this="{{.}}" />

// Child template. Unrolls href and target onto
{{ text }}

unrelated div gets nothing

The above would satisfy "spreading" the data as attributes selectively. However, note that there's text in the data. Should Ractive do this spreading behavior, it should know what attributes are valid and what aren't.
My 2c.

What if you could specify a list of non-element attributes for your component, and ractive automatically collected everything else up and made it available as a partial? That way you could easily control what's relevant for config/data and where whatever is left over is actually rendered.
Ractive.extend({
  template: `

attribute-content}}>...
`,
  configAttributes: [ 'foo', 'baz', 'data-my-special-unicorn', 'value' ]
}); // this will be a component named cmp

var otherTemplate = `<cmp value="{{yeah}}" class="big and purple" foo="{{foo}}" />`

I haven't looked at it in depth, but I don't know how combing through the template for top-level refs would work out. Explicit feels safer, and it would make having "required" attributes in another property a bit more natural feeling. Required attributes would be any mappings/config attributes that a component needs in order to accomplish something, where a warning would automatically be emitted if absent.
Would all of that be better left to library functions or baked into ractive? This falls into the category of template manipulation, which is handy, but ractive currently provides no tools to do so. It's all manual at this point, but aside from navigating a terse template structure, it's not difficult at all.

@evs-chris I like this approach. 👍 specially the warning part.
If you think it will have an impact on performance then would be better off in a library, but otherwise baked for sure.

What if you could specify a list of non-element attributes for your component, and ractive automatically collected everything else up and made it available as a partial?

That would be fine with me.

Just to be sure I interpreted it correctly, the result of your example would be:

...

right?

Sounds good to me, but I'd prefer a more lightweight syntax though:
Ractive.extend({
  template: `

attributes}}>...
`,
  bindings: [ 'foo', 'baz', 'data-my-special-unicorn', 'value' ]
});

The {{>attributes}} partial would then contain everything except the bindings. Or, if you want to follow your required/optional parameters logic:
Ractive.extend({
template: `
attributes}}>...`,
  required: [ 'foo', 'value' ],
  optional: ['baz', 'data-my-special-unicorn']
});

@dagnelies yes, you correctly interpreted my example :smile:. Sorry, I typed that message on my phone, so it was a bit short.
After a question on the mailing list about nested components, my own experience putting together container-like components, and some other issues that seem to point in the same direction, I think helpers for manipulating template would be useful. Things like grabbing the top-level elements from a content partial and massaging them into their own data structure a la https://jsfiddle.net/L9rvx5Ly/1/ would be much cleaner with a little bit of library support. It should handle this case more generally by allowing access to the component attributes more easily to make a partial. It could also cover #1786 and #2001.
I'll see what I can put together for an RFC.

Moving extra attributes to an element is now possible in edge.


which version to use

May I ask the difference of this pipeline and https://github.com/artic-network/fieldbioinformatics? It seems the later one updated more frequently, but this version is the one used in ARTIC network SOP https://artic.network/ncov-2019/ncov2019-bioinformatics-sop.html
Any suggestions? Thanks.

Hi @Shaokang123
That's a good question! In terms of differences between this repo and the one at fieldbioinformatics repo, the ARTIC pipeline itself is developed at the fieldbioinformatics repo - this is where the code lives and where you can download the development version or one of the releases.
This repository (artic-ncov2019) is more of a timestamped collection of resources for performing the ARTIC Network SOP. It is essentially just a conda environment which contains the ARTIC pipeline, as well as a few other resources (such as RAMPART).
The version of the ARTIC pipeline in the SOP will be periodically updated when we are happy with the latest pipeline changes. So in a few days/weeks we will update this repository to use the latest release of the ARTIC pipeline found at fieldbioinformatics repo.
As a side note -  if you just want the latest ARTIC pipeline, you can now install direct from conda:
conda create -n artic-env
conda activate artic-env
conda install -c bioconda -c conda-forge artic

Hi @Shaokang123
That's a good question! In terms of differences between this repo and the one at fieldbioinformatics repo, the ARTIC pipeline itself is developed at the fieldbioinformatics repo - this is where the code lives and where you can download the development version or one of the releases.
This repository (artic-ncov2019) is more of a timestamped collection of resources for performing the ARTIC Network SOP. It is essentially just a conda environment which contains the ARTIC pipeline, as well as a few other resources (such as RAMPART).
The version of the ARTIC pipeline in the SOP will be periodically updated when we are happy with the latest pipeline changes. So in a few days/weeks we will update this repository to use the latest release of the ARTIC pipeline found at fieldbioinformatics repo.
As a side note -  if you just want the latest ARTIC pipeline, you can now install direct from conda:
conda create -n artic-env
conda activate artic-env
conda install -c bioconda -c conda-forge artic

@will-rowe great, thanks for your reply. Appreciate your help.

@will-rowe great, thanks for your reply. Appreciate your help.

Hi @will-rowe, if possible, may I ask for when will the SOP version of artic be updated?

Hopefully soon - just waiting on a code review from Nick before we make the next release and then update all the envs/SOPs across artic. Sorry I can't be more exact.

@will-rowe great, thanks so much, look forward to trying the new version


[BUG] After the node reconnects, the restoring volume sometimes becomes faulted.

Describe the bug (🐛 if you encounter this issue)
In restore-volume-node-down , case1 step3:
I try to simulate a power off on the volume-attached node using a disconnect network script for 5, 100, 400, and 1200 seconds. After disconnecting for 400 seconds, I found that the restoring volume sometimes became faulted after the node reconnected. I was able to reproduce this issue on v1.4.1. Therefore, I believe that I should create a ticket to have this behavior checked to determine whether it is expected or not.

To Reproduce
Steps to reproduce the behavior:

Create a volume, pv and pvc vol-0
Launch a pod with Longhorn volume.
kubectl apply -f pod_mount_1vol.yaml

pod_mount_1vol.yaml
kind: Pod
apiVersion: v1
metadata:
  name: ubuntu-mountvol0
  namespace: default
spec:
  containers:
    - name: ubuntu
      image: ubuntu
      command: ["/bin/sleep", "3650d"]
      volumeMounts:
      - mountPath: "/data/"
        name: vol-0
  volumes:
    - name: vol-0
      persistentVolumeClaim:
        claimName: vol-0

Write 1.2G data to the volume and create a backup.
kubectl exec -it ubuntu-mountvol0 -- /bin/bash -c "dd if=/dev/urandom of=/data/1.2g bs=1M count=1200 oflag=direct status=progress && md5sum /data/1.2g"
Create a restore volume from the backup.
Disconnect the network of the node that the volume attached to for 400 seconds during the restoring.
Wait for the Longhorn node down.
Wait for the restore volume being reattached and starting restoring volume with state Degraded.
Wait for the restore complete.
Attach the volume and verify the restored data.
Verify the volume works fine.

Expected behavior
The volume restore should be completed.
Log or Support bundle
longhorn-support-bundle_c15ffec2-0b12-496f-b7c6-aa3f64af6826_2023-03-27T06-23-28Z.zip
Environment

Longhorn version:
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:

Number of management node in the cluster: 1
Number of worker node in the cluster:3

Node config

OS type and version:
CPU per node:4
Memory per node: 16g
Disk type(e.g. SSD/NVMe): SSD
Network bandwidth between the nodes:

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): AWS
Number of Longhorn volumes in the cluster: 1

Additional context
https://confluence.suse.com/pages/viewpage.action?spaceKey=LON&title=Negative+Testing
https://longhorn.github.io/longhorn-tests/manual/pre-release/backup-and-restore/restore-volume-node-down/

@roger-ryao did this only happen in the master/1.4.x? how about 1.3?

@c3y1huang Could you help with this? we have a similar one https://github.com/longhorn/longhorn/issues/5658#issuecomment-1484626576 but the context is probably different.
cc @derekbit @shuo-wu @PhanLe1010

@roger-ryao did this only happen in the master/1.4.x? how about 1.3?

I could reproduce this on 1.3.3-RC2 and 1.4.1, but I don't test it on master yet.

@roger-ryao was the volume able to salvage and turned back to a healthy state? and actually, the restored volume worked as expected w/o data intact.

Hi @innobead :
I didn't disable Automatic Salvage ; it was enabled. However, the volume's robustness status remained "faulted" and did not return to a healthy state.

@roger-ryao did this only happen in the master/1.4.x? how about 1.3?

I could reproduce this on 1.3.3-RC2 and 1.4.1, but I don't test it on master yet.

I was able to reproduce the issue on the master-head.
supportbundle_ae12f40a-8c91-42e6-93e0-f5ee6f57b315_2023-03-28T04-28-23Z.zip

@roger-ryao one more request , is it able to reproduce in 1.3.2?

@roger-ryao one more request , is it able to reproduce in 1.3.2?

Hi @innobead :
I was able to reproduce the issue not only on v1.3.2, but also on v1.4.0. Here is the support bundle for your reference.

Version
Snapshot

1.3.2
132-longhorn-support-bundle.zip

1.4.0
140-longhorn-support-bundle.zip

2023-03-27T06:19:46.872651899Z [vol-0-e-d874c274] time="2023-03-27T06:19:46Z" level=error msg="Backend tcp://<IP_ADDRESS>:10000 monitoring failed, mark as ERR: ping failure: replica state closed"
2023-03-27T06:19:46.872666912Z time="2023-03-27T06:19:46Z" level=info msg="Setting replica tcp://<IP_ADDRESS>:10000 to mode ERR"
2023-03-27T06:19:46.872671904Z time="2023-03-27T06:19:46Z" level=info msg="Monitoring stopped tcp://<IP_ADDRESS>:10000"
2023-03-27T06:19:46.883844032Z [vol-0-e-d874c274] time="2023-03-27T06:19:46Z" level=error msg="Backend tcp://<IP_ADDRESS>:10000 monitoring failed, mark as ERR: ping failure: replica state closed"
2023-03-27T06:19:46.883857971Z time="2023-03-27T06:19:46Z" level=info msg="Setting replica tcp://<IP_ADDRESS>:10000 to mode ERR"

According to the  Node disconnection test, this behavior is expected.
Ref:

https://github.com/longhorn/longhorn/issues/5476
https://github.com/longhorn/longhorn/issues/5464

cc @derekbit @shuo-wu @innobead

So need to check why it's not salvaged in this case.

https://github.com/longhorn/longhorn-manager/blob/master/controller/volume_controller.go#L1322

@roger-ryao could you help to confirm the behavior when restoring(revert) the existing volume's backup(snapshot) ?

Hi @c3y1huang :
I was not able to reproduce the issue when restoring (reverting) the existing volume's backup (snapshot).
Steps to reproduce the behavior:

Create a volume, persistent volume (PV), and persistent volume claim (PVC) with the name vol-0
Launch a pod with a Longhorn volume by applying the configuration in the file pod_mount_1vol.yaml using the command kubectl apply -f pod_mount_1vol.yaml.

pod_mount_1vol.yaml
kind: Pod
apiVersion: v1
metadata:
  name: ubuntu-mountvol0
  namespace: default
spec:
  containers:
    - name: ubuntu
      image: ubuntu
      command: ["/bin/sleep", "3650d"]
      volumeMounts:
      - mountPath: "/data/"
        name: vol-0
  volumes:
    - name: vol-0
      persistentVolumeClaim:
        claimName: vol-0

Write 1.2 GB of random data to the volume using the command kubectl exec -it ubuntu-mountvol0 -- /bin/bash -c 'dd if=/dev/urandom of=/data/1.2g bs=1M count=1200 oflag=direct status=progress && md5sum /data/1.2g', and create a backup of the volume.
Write 12 MB of random data to the volume.
Delete the pod to ensure that the volume is detached.
Attach the volume to a node with maintenance mode enabled.
Revert the volume's backup from step 3
Disconnect the network of the node that the volume is attached to for 400 seconds.
Wait for the Longhorn node down.
Wait for the volume to be reattached.
Detach the volume.
Launch pod with the volume, and verify that the restored data is present.
Verify the volume works fine.

@c3y1huang could u update the test cases with clarified info mentioned above, then we can close w/o any fixings, since this is expected.

@c3y1huang could u update the test cases with clarified info mentioned above, then we can close w/o any fixings, since this is expected.

https://github.com/longhorn/longhorn-tests/pull/1296/files

@c3y1huang could u update the test cases with clarified info mentioned above, then we can close w/o any fixings, since this is expected.

https://github.com/longhorn/longhorn-tests/pull/1296/files


Camera stuck in  "Resetting device..."

Required Info

Camera Model
D435i

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 22.04

Kernel Version (Linux Only)
5.15.0-72-generic

Platform
PC.

SDK Version
v2.54.1

ROS driver
RealSense ROS v4.54.1

I rebuild the librealsense using the RSUSB backend. It works well. But now when I use it with the ROS driver and I have initial_reset: true the driver stays stuck in the  "Resetting device..." message forever. If I set the initial_reset: false it starts normally.  It didn't use to do this with the V4L backend.
For the moment I'm setting initial_reset: false but any idea why this may happen?

Hi @martinakos  I have seen a RealSense ROS case like this before. I believe that all that you can do is not use initial_reset.  The reset is not a compulsory option anyway and only needs to be used if there is a problem with the launch that a reset helps to resolve.

Ok, thanks. I'll keep the initial_reset: false then.


Plants scream mutation now have more scream variety

About the PR
More scream sounds. Scream volume quieter.

Why / Balance

Technical details

Media
https://github.com/user-attachments/assets/8c96fdb5-31ac-40ff-a569-e45fc91d0f22

Requirements

[x] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

add: Plant's scream mutation now have 10+ scream varieties.

Well, it's now scarier💀

Would be cool to add some species screams

Would be cool to add some species screams

maybe as separate mutations


Eliah Kagan: Watch zitamovie.com

Eliah Kagan requests the watch of the watch_keyword zitamovie\.com. See the MS search here and the Stack Exchange search here.

zitamovie\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


Add OpenShift Client 4.16.9

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@RickJWagner can you review this?

Thank you for your quick and thorough work, @al-lac.
The PR looks good, thanks again for your efforts.


My code looks like this:
Server:
newItem() {
   if (!this.userId)
     throw new Meteor.Error('unauthorized', 'User must be logged-in to insert an item');

   return Items.insert({ ownerId: this.userId, title: 'New Item' });
}

Client:
MeteorObservable.call('newItem').subscribe({

  next: () => {
    //get _id
  },
  error: (e: Error) => {
    console.log("Error: " + e);
  }

});

Can you please tell me how to get the _id?
I also posted here: http://stackoverflow.com/questions/41040730/ionic2-meteor-get-id-of-new-inserted-item

Ok, error was on the server-side. Items.collection.insert(...) is correct. So not a problem of MeteorObservable, sorry.


ability to omit compound unique from typegraphql types

Is your feature request related to a problem? Please describe.
assume you have this model:
model MyModel {
  id String
  organizationId String

  @@unique([id, organizationId])
}

there doesn't seem to be a way to hide the generated id_organizationId field in typegraphql-generated types (if there is please let me know) :)
Describe the solution you'd like
The clearest way I can think of is to make /// @TypeGraphQL.omit(input: true) work for @@unique
Describe alternatives you've considered
???

You need this field in inputs in order to properly find unique records in db via graphql api.

You need this field in inputs in order to properly find unique records in db via graphql api.

sorry, my example should have marked the id as @unique as well
in my case, i want to expose id as the only unique the caller is allowed to use for input, despite prisma allowing id | id_organizationId

to make this more clear, i can hide regular @uniques but not @@uniques -- as long as i leave at least one of the regular @uniques available to the caller that should still work with findUnique right?

@MichalLytek -- here's a clearer example:
model MyModel {
  id String @unique
  /// @TypeGraphQL.omit(output: true, input: true)
  organizationId String

  @@unique([id, organizationId])
}

this currently generates:
export declare class MyModelWhereUniqueInput {
    id?: string | undefined;
    id_organizationId?: MyModelIdOrganizationIdCompoundUniqueInput | undefined;
}

but what i want to generate instead is:
export declare class MyModelWhereUniqueInput {
    id?: string | undefined;
}

that still has at least one unique field (id) so it would still be usable as input to findUnique

@MichalLytek see clarification above


Migration fails in oidcng 4.0.2

This issue is imported from pivotal - Originaly created at Dec 9, 2020 by Bart Geesink
Two issues in this migration:
@ChangeSet(order = "006", id = "dropValueIndexes", author = "Okke Harsta")
public void dropValueIndexes(MongockTemplate mongoTemplate) {
Arrays.asList("access_tokens", "refresh_tokens").forEach(collection -> {
IndexOperations indexOperations = mongoTemplate.indexOps(collection);
indexOperations.dropIndex("value_unique");
indexOperations.ensureIndex(new Index("jwtId", Sort.Direction.ASC).unique());
});
}
value_unique does not exist, so cannot be dropped
then the jwtId index fails:
"errmsg" : "E11000 duplicate key error collection: oidcng.access_tokens index: jwtId_1 dup key: { : null }",
That is because the jwtId is not present yet for existing access_tokens, so they all get null value assigned, leading to duplicates (not allowed because of the unique constrait)

The following indexes are present on acc + prod:
access_token:
value_unique
refresh_token:
innerValue_unique (Bart Geesink - Dec 15, 2020)


Question: What trigger the generation of the PartitionId on protocol API Generation

I've noticed that some times Graph Engine Code Gen includes the parameter "PartitionId" and then it does not and I don't know what I might be doing in the TSL to cause such behavior.
Steps to get things started!

Here I am calling the generated API "PostTripleToServer" and it the RPC method only has one parameter:

I can follow the same workflow and design pattern in writing TSL yet in a separate project and the GE will generate an RPC method call that requires two parameters: int PartitionId in position 1 and then the Writer Request message in the second parameter. In any case, the later RPC method always fails no matter what value is in for PartitionId - I've tried 0 and 1 so far and I'm only testing with a single server instance.
Perhaps the most important difference is that the call to RegisterCommunicationModule does not expose all of the RPC methods; I can call GetCommunicationModule and then I can see the missing methods but those methods require the PartitionId.

Okay, I found the problem; it is the scope of the using statement. In Visual Studio 2019 by default, the using statement did not include the class that implements the RPC methods.


add pnpm condition to yarn/npm branches in blueprint files

this is similar to #68 but intentionally omit GitHub actions as it's more complicated and error prune hence simpler to get as separate PRs


STGのMySQLのシークレット参照先切替

Description

devクラスター切替に伴い、シークレットの参照先を切り替えました
Type of change

[ ] Document update or simple typo fix
[ ] Maintenance/update components
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?

[ ] I have checked backward/forward compatibility that may cause regarding this change.

別ブランチで対応してたのでクローズ
https://github.com/cloudnativedaysjp/dreamkast-infra/tree/dreamkast_us


⚠ Bofrost.es has degraded performance

In 7d79342, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1990 ms

Resolved: Bofrost.es performance has improved in 481dd23 after 7 minutes.


Invoke-CMApplyDriverPackage.ps1 AdminService command line TargetOSName fails

I'm getting an argument error on TargetOSName...... -TargetOSName "Windows 10" -TargetOSVersion "21H2".
I've looked through the PS script to see if there was a typo but I couldn't find one....It appears the command line is correct...

We had this issue also, I redeployed the package and it worked again.
This was after applying the latest SCCM update last week.
I use ' not " in the commandline, maybe try that if your still having issues.

the single quote worked for me as well
Hudy Scott
IT Technician | Community Choice Financial
Direct:<PHONE_NUMBER>
<EMAIL_ADDRESS>PLEASE NOTE:  Speedy Cash, Rapid Cash and Avio are now part
of the Community Choice Financial family of companies
[cid:ed978629-a5fe-4b81-8263-1da610d2e271]

From: DJ12220 @.>
Sent: Thursday, September 22, 2022 10:00 AM
To: maurice-daly/DriverAutomationTool @.>
Cc: hudyscott @.>; Author @.>
Subject: [External]Re: [maurice-daly/DriverAutomationTool] Invoke-CMApplyDriverPackage.ps1 AdminService command line TargetOSName fails (Issue #388)
CAUTION: External Email
This email has originated from outside of the organization. Do not click any links or open any attachments unless you have verified the sender and know the content is safe.
CAUTION: This email was sent from outside the organization @.***). Do not click links or open attachments unless you recognize the sender and know the content is safe.
We had this issue also, I redeployed the package and it worked again.
This was after applying the latest SCCM update last week.
I use ' not " in the commandline, maybe try that if your still having issues.
—
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmaurice-daly%2FDriverAutomationTool%2Fissues%2F388%23issuecomment-1255154746&data=05|01|hscott%40ccfi.com|8725521835d14c3eafa708da9cab409f|1773e9f4954c4747a4534bd6405b5a14|0|0|637994556602062375|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=zm9UJq5oTw5OgISyZFIekZr3Maj86ffD9KRbC72qXMQ%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAP3I2S52CJNYLNBGUNYJMCDV7RYCHANCNFSM6AAAAAAQNN3B5Q&data=05|01|hscott%40ccfi.com|8725521835d14c3eafa708da9cab409f|1773e9f4954c4747a4534bd6405b5a14|0|0|637994556602062375|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=rIIPqTkxmF00RbMFrwOJBHF25x90zDmcufte1JiRvaE%3D&reserved=0.
You are receiving this because you authored the thread.Message ID: @.***>


Updating to 2018 edition of rust

Changing the edition of rust to 2018 and making necessary changes to use statements.
I also removed the now unnecessary extern crate statements

Merged into testing for now


Improve Common Properties TitleEditor

Updated design for the title component of Common Properties RHS flyouts, with support for an optional icon/label.

The edit icon should sit next to the title instead of at the end on the right. Editing the title should cause the edit icon to disappear, and editing should end on loss of focus.

@aqtang is it safe to assume we will have truncation made available for when the title is too long?

@quarryboy Yes, we'll want that behavior


Cannot validate argument on parameter 'Hashtable'.

Bug description
we are running fortigate version 7.4.1 and getting the following error. I have done tests and put together a whole document testing the different versions for the company i work for. i will attach that document. but we have noted at one of our clients that it does not work on their 7.4.1.
Command-line input
$Username = 'Redacted'\n$Password_un = 'Redacted'\n$Server = 'Redacted'\n$Port = Redacted\n\n$password = ConvertTo-SecureString $Password_un -AsPlainText -Force\n\nConnect-FGT -Server $Server -Username $Username -Password $password -Port $Port -SkipCertificateCheck\n\nNew-AsBuiltReport -Report Fortinet.FortiGate -Target $Server -Username $Username -Password $Password_un -Format Word -OutputFolderPath 'C:\AsBuilt' -Timestamp -ReportConfigFilePath 'C:\AsBuilt\AsBuilt.json' -AsBuiltConfigFilePath 'C:\AsBuilt\parameters.json' -StyleFilePath 'C:\AsBuilt\StyleFilePath.ps1' -Filename '[Redacted] Fortinet FortiGate As Built Report (fmDQ)'
Steps to reproduce
FortiGate As-Built Program Debug 2.docx
Expected behaviour
As Built to be generated
Screenshots
No response
Operating System
Windows 11
PowerShell Version
Name                           Value

PSVersion                      5.1.22621.2506
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.2506
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
PowerShell Modules
Name                             Version

AsBuiltReport.Core               1.3.0
AsBuiltReport.Fortinet.FortiGate 0.2.2
PowerFGT                         0.7.0
PScribo                          0.10.0
Additional Context
Redacted Logging.log
Before submitting

[X] I have read and followed the bug reporting guidelines.
[X] I have read the documentation, and referred to the known issues before submitting this bug report.
[X] I have checked for previously opened & closed issues before submitting this bug report.

Hi Connor(Hess)
Can you enable report with -verbose and attach the output ?
i will for try to look for reproducte

ok will attach now

WARNING: The names of some imported commands from the module 'PowerFGT' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.

Name                           Value
----                           -----
server                         **Redacted**
version                        7.4.1
invokeParams                   {UseBasicParsing, DisableKeepAlive, TimeoutSec}
headers                        {X-CSRFTOKEN}
port                           **Redacted**
httpOnly                       False
session                        Microsoft.PowerShell.Commands.WebRequestSession
serial                         **Redacted**
vdom
VERBOSE: Loading As Built Report configuration from 'C:\AsBuilt\parameters.json'.
VERBOSE: Populating RepositorySourceLocation property for module AsBuiltReport.Fortinet.FortiGate.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\AsBuiltReport.Fortinet.FortiGate\0.2.2\AsBuiltReport.Fortinet.FortiGate.psm1'.
VERBOSE: Loading AsBuiltReport.Fortinet.FortiGate report configuration file from path 'C:\AsBuilt\AsBuilt.json'.
VERBOSE: Setting report filename to '[**Redacted**][V0.1] Fortinet FortiGate As Built Report (S8VM) - 2024-01-15_11.04.39'.
VERBOSE: [ 11:04:39:297 ] [ Document ] - Document '[**Redacted**][V0.1] Fortinet FortiGate As Built Report (S8VM) - 2024-01-15_11.04.39' processing started.
VERBOSE: [ 11:04:39:539 ] [ Document ] - Executing report style script from path 'C:\AsBuilt\StyleFilePath.ps1'.
VERBOSE: [ 11:04:39:586 ] [ Document ] - Setting global document options.
VERBOSE: [ 11:04:39:589 ] [ Document ] - Enabling section/heading numbering.
VERBOSE: [ 11:04:39:597 ] [ Document ] - Setting default font(s) to 'Arial'.
VERBOSE: [ 11:04:39:599 ] [ Document ] - Setting page top margin to '25.05'mm.
VERBOSE: [ 11:04:39:601 ] [ Document ] - Setting page right margin to '25.05'mm.
VERBOSE: [ 11:04:39:603 ] [ Document ] - Setting page bottom margin to '25.05'mm.
VERBOSE: [ 11:04:39:605 ] [ Document ] - Setting page left margin to '25.05'mm.
VERBOSE: [ 11:04:39:607 ] [ Document ] - Setting page size to 'A4'.
VERBOSE: [ 11:04:39:609 ] [ Document ] - Setting page orientation to 'Portrait'.
VERBOSE: [ 11:04:39:611 ] [ Document ] - Setting page height to '297'mm.
VERBOSE: [ 11:04:39:613 ] [ Document ] - Setting page width to '210'mm.
VERBOSE: [ 11:04:39:615 ] [ Document ] - Setting document style 'Title'.
VERBOSE: [ 11:04:39:618 ] [ Document ] - Setting document style 'Title2'.
VERBOSE: [ 11:04:39:623 ] [ Document ] - Setting document style 'Title3'.
VERBOSE: [ 11:04:39:627 ] [ Document ] - Setting document style 'Heading1'.
VERBOSE: [ 11:04:39:649 ] [ Document ] - Setting document style 'Heading2'.
VERBOSE: [ 11:04:39:654 ] [ Document ] - Setting document style 'Heading3'.
VERBOSE: [ 11:04:39:657 ] [ Document ] - Setting document style 'Heading4'.
VERBOSE: [ 11:04:39:661 ] [ Document ] - Setting document style 'NOTOCHeading4'.
VERBOSE: [ 11:04:39:664 ] [ Document ] - Setting document style 'Heading5'.
VERBOSE: [ 11:04:39:669 ] [ Document ] - Setting document style 'NOTOCHeading5'.
VERBOSE: [ 11:04:39:672 ] [ Document ] - Setting document style 'Normal'.
VERBOSE: [ 11:04:39:674 ] [ Document ] - Setting document style 'Caption'.
VERBOSE: [ 11:04:39:678 ] [ Document ] - Setting document style 'Header'.
VERBOSE: [ 11:04:39:680 ] [ Document ] - Setting document style 'Footer'.
VERBOSE: [ 11:04:39:684 ] [ Document ] - Setting document style 'TOC'.
VERBOSE: [ 11:04:39:687 ] [ Document ] - Setting document style 'TableDefaultHeading'.
VERBOSE: [ 11:04:39:692 ] [ Document ] - Setting document style 'TableDefaultRow'.
VERBOSE: [ 11:04:39:696 ] [ Document ] - Setting document style 'Critical'.
VERBOSE: [ 11:04:39:700 ] [ Document ] - Setting document style 'Warning'.
VERBOSE: [ 11:04:39:705 ] [ Document ] - Setting document style 'Info'.
VERBOSE: [ 11:04:39:710 ] [ Document ] - Setting document style 'OK'.
VERBOSE: [ 11:04:39:715 ] [ Document ] - Setting table style 'TableDefault'.
VERBOSE: [ 11:04:39:720 ] [ Document ] - Setting table style 'Borderless'.
VERBOSE: [ 11:04:39:740 ] [ Document ] - Processing document header started.
VERBOSE: [ 11:04:39:805 ] [ Document ] - Processing paragraph 'Fortinet FortiGate As Built Report -[..]'.
VERBOSE: [ 11:04:39:865 ] [ Document ] - Processing document header completed.
VERBOSE: [ 11:04:39:870 ] [ Document ] - Processing document footer started.
VERBOSE: [ 11:04:39:887 ] [ Document ] - Processing paragraph 'Page <!# PageNumber #!>'.
VERBOSE: [ 11:04:39:895 ] [ Document ] - Processing document footer completed.
VERBOSE: [ 11:04:39:902 ] [ Document ] - Processing blank line.
VERBOSE: [ 11:04:39:905 ] [ Document ] - Processing paragraph 'Fortinet FortiGate As Built Report'.
VERBOSE: [ 11:04:39:911 ] [ Document ] - Processing blank line.
VERBOSE: [ 11:04:39:913 ] [ Document ] - Processing paragraph '**Redacted**'.
VERBOSE: [ 11:04:39:916 ] [ Document ] - Processing blank line.
VERBOSE: [ 11:04:39:939 ] [ Document ] - Processing table 'Cover Page'.
VERBOSE: [ 11:04:39:985 ] [ Document ] - Processing page break.
VERBOSE: [ 11:04:39:991 ] [ Document ] - Processing table of contents 'Table of Contents'.
VERBOSE: [ 11:04:39:995 ] [ Document ] - Processing page break.
VERBOSE: [ 11:04:40:940 ] [ Document ] - Connect to **Redacted** : FG101F (**Redacted**)
VERBOSE: [ 11:04:40:952 ] [ Document ] - Processing section 'Implementation Report **Redacted**' started.
VERBOSE: [ 11:04:40:980 ] [ Document ] - Processing paragraph 'The following section provides a sum[..]'.
VERBOSE: [ 11:04:40:983 ] [ Document ] - Processing blank line.
VERBOSE: [ 11:04:40:993 ] [ Document ] - Discovering FortiCare settings information from **Redacted**.
VERBOSE: [ 11:04:41:117 ] [ Document ] - Processing section 'FortiCare' started.
VERBOSE: [ 11:04:41:145 ] [ Document ] - Processing paragraph 'The following section details FortiC[..]'.
VERBOSE: [ 11:04:41:148 ] [ Document ] - Processing blank line.
VERBOSE: [ 11:04:41:164 ] [ Document ] - Processing table 'FortiCare'.
VERBOSE: [ 11:04:41:212 ] [ Document ] - Processing paragraph 'The following section details suppor[..]'.
VERBOSE: [ 11:04:41:216 ] [ Document ] - Processing blank line.
VERBOSE: [ 11:04:41:232 ] [ Document ] - Processing table 'Support'.
VERBOSE: [ 11:04:41:247 ] [ Document ] - Processing section 'FortiCare' completed.
VERBOSE: [ 11:04:41:507 ] [ Document ] - Processing paragraph 'The following section details firmwa[..]'.
VERBOSE: [ 11:04:41:509 ] [ Document ] - Processing blank line.
VERBOSE: [ 11:04:41:540 ] [ Document ] - Processing table 'Firmware'.
WARNING: [ 11:04:41:708 ] [ Document ] - Cannot bind argument to parameter 'Rows' because it is an empty collection.
VERBOSE: [ 11:04:41:826 ] [ Document ] - Document '[**Redacted**][V0.1] Fortinet FortiGate As Built Report (S8VM) - 2024-01-15_11.04.39' processing completed.
VERBOSE: [ 11:04:41:834 ] [ Document ] - Total processing time '2.63' seconds.
Fortinet FortiGate As Built Report '[**Redacted**][V0.1] Fortinet FortiGate As Built Report (S8VM) - 2024-01-15_11.04.39' has been saved to 'C:\AsBuilt'.

[ERROR] - Table : Cannot validate argument on parameter 'Hashtable'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.
At C:\Program Files\WindowsPowerShell\Modules\AsBuiltReport.Fortinet.FortiGate\0.2.2\Src\Private\Get-AbrFgtFortiCare.ps1:187 char:32
+             $tab_upgradePath | Table @TableParams
+                                ~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Table], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Table

Ok, i have reproduce the issue (with 7.4.0), i will look for a fix

i push a fix https://github.com/AsBuiltReport/AsBuiltReport.Fortinet.FortiGate/pull/64 if you want to try

I will need to do that tomorrow, I am out of the office now👍 will pull and try first thing in the morning. On 15 Jan 2024, at 15:16, Alexis La Goutte @.***> wrote:
i push a fix #64 if you want to try
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

it is good ?

I am not very proficient with ps scripts, is it possible to get a reference to a guide on how to update the package to this version?


fix(build): updates buildscript to generate driver image

This commit fixes the build script to generate csi-driver image.
There are few other fixes at:
- Dockerfile metadata
- Makefile

Vendoring changes are due to:
- dep ensure
- make kubegen

does this take care of verifying license headers?


More Build System Changes

Changelist

fully moves away from C++
update docker cubemx for quintuna
cmakefile tweaks

Testing Done

Resolved Tickets

LGTM


Typo at README.md

https://github.com/databricks/spark-csv/commit/cacd8c490d1e656bf9f5cd520bcec0354b3750fd#comments
I added a comment here.
optins should be options. :)

Want to submit a pr?

Well, sure.

Fixed in https://github.com/databricks/spark-csv/pull/210


Contextual Help and Tips Using KoBERT

Implement contextual tips for language learners by analyzing their input and performance using KoBERT

Maybe use other language model from HF?


HDDS-4228: add field 'num' to ALLOCATE_BLOCK of scm audit log.

What changes were proposed in this pull request?
The scm audit log for ALLOCATE_BLOCK is as follows:
2020-09-10 03:42:08,196 | INFO | SCMAudit | user=root | ip=<IP_ADDRESS> | op=ALLOCATE_BLOCK {owner=7da0b4c4-d053-4fa0-8648-44ff0b8ba1bf, size=268435456, type=RATIS, factor=THREE} | ret=SUCCESS |

One might be interested about the num of blocks allocated, better add field 'num' to  ALLOCATE_BLOCK of scm audit log.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4228
Please replace this section with the link to the Apache JIRA)
How was this patch tested?
CI

LGTM. +1

LGTM! Thanks!

Merging


Argument "s" isn't numeric in numeric eq... Vault.pm line 462

Verifying availability of vault 'foo' (https://vault.lab.mydomain.com/)...Argument "s" isn't numeric in numeric eq (==) at /Users/fflintstone/lab/deployments//.geese/lib/Genesis/Vault.pm line 462.
	my ($out,$rc) = $self->query({stderr => "&1"}, "vault", "status");
	if ($rc != 0) {
		$out =~ /exit status ([0-9])/;
		return "sealed" if $1 == 2;     <<<<---- line 462
		return "unreachable";
	}

	return "u

This results when the user has multiple safe targets (~/.saferc) pointing at the same vault url:
version: 1
current: foo
vaults:
  foo:
    url: https://vault.lab.mydomain.com
    token: s...
    skip_verify: true
  bar:
    url: https://vault.lab.mydomain.com
    token: s...
    skip_verify: true

What command were you running that caused this error?  When genesis queries the vault for the first time, it usually responds with an error on duplicate entries, such as the following:
$ genesis mylab.yml deploy
[ERROR] Cannot find unique vault configuration at https://vault.lab.mydomain.com in your .saferc

Problem was due to the repo using "legacy" secrets provider mode, which bypassed the duplicate URL check.  Resolved by fixing the selection of the default vault.


Make max history days configurable in Profile and QA results

Is your feature request related to a problem? Please describe.
Currently user can see Profiles and QA results only for interval: 3, 7, 14, 30 or 60 days. This doesn't give enough context for the data updated monthly, quarterly or even yearly.

Describe the solution you'd like
There are two ideas coming to mind:

Make intervals and max history days configurable. For example filter with options: 30, 60, 90, 120 means INTERVAL=30 days and MAX_HISTORY_DAYS=120. If also make definition configurable (MINUTES, DAYS, YEARS), then user can setup this according to data updating intervals. Then profiling and QA results will become more valuable
Instead of date/time intervals, display certain number or latest runs in dropdown selection: 100, 200, 300, 400. Approach can be the same like with dates: INTERVAL=100 results, MAX_NUMBER_OF_RESULTS=400.

Similar issue https://github.com/orgs/open-metadata/projects/18/views/5?filterQuery=is%3Aopen++assignee%3AShaileshParmar11&pane=issue&itemId=20196867

@JahJajaka will be closing this issue as we already have one open 👉 https://github.com/open-metadata/OpenMetadata/issues/10187


Footer hover effect

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
The footer icons do not have any hover effect on the website and also no colour. I would like to add both these things and also enhance it.
Please assign it to me under lgm-soc.

@Khushi-agarwal All the website-related issues will be taken only on Community.
You may list this issue there.

@yashsehgal , can you please assign this to me.


[Spanish] localize 'Canary Deployment'

Localize the content/en/canary_deployment.md document to Spanish

please assign this to me


chore: upgrade strapi and related dependencies, remove pleb config

Upgrade Strapi and its plugins to the latest versions, ensuring compatibility and improved features. Remove the pleb configuration.

I see errors in these files:

data-api.tsx
footer.tsx
about/route.tsx
Are they ok? They do not appear in main.

Unfortunately this is happening also in main but still: Do we want an About page with nothing in it? Also clicking on Contact opens nothing on browser. And clicking on Projects does nothing.

is it a regression? if not, then lets open an issue about it but lets not include it in this pr, as im not trying to fix issues here.

It is a regression.
Who opens the issue?


Implement continue on failure (fix #161)

This could be further improved by also catching this: https://github.com/mamba-org/boa/blob/9369513ca4e5119cdbc50975dd0d123aae7bc871/boa/core/solver.py#L180

I think without catching that exit it will quite quickly fail down-the-line, won't it? Since if we didn't build a dependency before due to some failure it will then fail where that failed dep is required.
I think we can just throw an error that we catch somewhere else and then either exit with an error code or just ignore.

This works nicely, many thanks for the additional changes @wolfv!


kconfig: drivers: spi: Remove duplicated dependencies

The two redundant SPI dependencies are from 'source'ing a file within an
'if SPI' and then adding another 'depends on SPI' within it.
'if FOO' is just shorthand for adding depends on FOO to each item within
the 'if'. There are no "conditional includes" in Kconfig, so 'if FOO' has
no special meaning around a source. Conditional includes wouldn't be
possible, because an if condition could include (directly or indirectly)
forward references to symbols not defined yet.
Tip: When adding a symbol, check its dependencies in the menuconfig
('ninja menuconfig', then / to jump to the symbol). The menuconfig also
shows how the file with the symbol got included, so if you see
duplicated dependencies, it's easy to hunt down where they come from.

Codecov Report

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

@@           Coverage Diff           @@
##           master   #14175   +/-   ##
=======================================
  Coverage   52.68%   52.68%
=======================================
  Files         307      307
  Lines       45473    45473
  Branches    10530    10530
=======================================
  Hits        23956    23956
  Misses      16640    16640
  Partials     4877     4877

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 1f74e0b...99e9883. Read the comment docs.


HDFS-17410. [FGL] Client RPCs that changes file attributes supports fine-grained lock

There are some client RPCs are used to change file attributes.
This ticket is used to make these RPCs supporting fine-grained lock.

setReplication
getStoragePolicies
setStoragePolicy
unsetStoragePolicy
satisfyStoragePolicy
getStoragePolicy
setPermission
setOwner
setTimes
concat
truncate
setQuota
getQuotaUsage
modifyAclEntries
removeAclEntries
removeDefaultAcl
removeAcl
setAcl
getAclStatus
getEZForPath
listEncryptionZones
reencryptEncryptionZone
listReencryptionStatus
setXAttr
getXAttrs
listXAttrs
removeXAttr

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
6m 44s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ HDFS-17384 Compile Tests _

+1 :green_heart:
mvninstall
31m 48s

HDFS-17384 passed

+1 :green_heart:
compile
0m 46s

HDFS-17384 passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
compile
0m 41s

HDFS-17384 passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
checkstyle
0m 38s

HDFS-17384 passed

+1 :green_heart:
mvnsite
0m 46s

HDFS-17384 passed

+1 :green_heart:
javadoc
0m 43s

HDFS-17384 passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m  4s

HDFS-17384 passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
1m 48s

HDFS-17384 passed

+1 :green_heart:
shadedclient
20m 53s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 34s

the patch passed

+1 :green_heart:
compile
0m 38s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javac
0m 38s

the patch passed

+1 :green_heart:
compile
0m 37s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
javac
0m 37s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 29s

the patch passed

+1 :green_heart:
mvnsite
0m 39s

the patch passed

+1 :green_heart:
javadoc
0m 32s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m  2s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
1m 37s

the patch passed

+1 :green_heart:
shadedclient
20m 35s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
211m  6s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 29s

The patch does not generate ASF License warnings.

305m 40s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestQuota

hadoop.hdfs.server.datanode.TestLargeBlockReport

hadoop.hdfs.protocol.TestBlockListAsLongs

hadoop.hdfs.server.balancer.TestBalancerWithHANameNodes

hadoop.hdfs.tools.TestDFSAdmin

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6634/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6634

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux c87e1102468f 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
HDFS-17384 / a47bbfd3bdb8bbe84eaa87ebea8674bb7cf709e8

Default Java
Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6634/1/testReport/

Max. process+thread count
3945 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6634/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

failed cases seem related to this PR.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 46s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ HDFS-17384 Compile Tests _

+1 :green_heart:
mvninstall
63m  7s

HDFS-17384 passed

+1 :green_heart:
compile
1m 23s

HDFS-17384 passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
compile
1m 12s

HDFS-17384 passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
checkstyle
1m 13s

HDFS-17384 passed

+1 :green_heart:
mvnsite
1m 25s

HDFS-17384 passed

+1 :green_heart:
javadoc
1m 12s

HDFS-17384 passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m 44s

HDFS-17384 passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
3m 18s

HDFS-17384 passed

+1 :green_heart:
shadedclient
40m 17s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 14s

the patch passed

+1 :green_heart:
compile
1m 16s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javac
1m 16s

the patch passed

+1 :green_heart:
compile
1m 11s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
javac
1m 11s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m  0s
/results-checkstyle-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs-project/hadoop-hdfs: The patch generated 1 new + 136 unchanged - 0 fixed = 137 total (was 136)

+1 :green_heart:
mvnsite
1m 16s

the patch passed

+1 :green_heart:
javadoc
0m 56s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m 37s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
3m 20s

the patch passed

+1 :green_heart:
shadedclient
40m 44s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
263m 39s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 45s

The patch does not generate ASF License warnings.

433m 36s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestRollingUpgrade

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6634/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6634

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 42ace5baffa9 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
HDFS-17384 / 9e2abae70c1b0c964b68fb52715dd53b5d873e82

Default Java
Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6634/3/testReport/

Max. process+thread count
2988 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6634/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 46s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ HDFS-17384 Compile Tests _

+1 :green_heart:
mvninstall
49m 39s

HDFS-17384 passed

+1 :green_heart:
compile
1m 25s

HDFS-17384 passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
compile
1m 17s

HDFS-17384 passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
checkstyle
1m 14s

HDFS-17384 passed

+1 :green_heart:
mvnsite
1m 25s

HDFS-17384 passed

+1 :green_heart:
javadoc
1m  8s

HDFS-17384 passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m 44s

HDFS-17384 passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
3m 19s

HDFS-17384 passed

+1 :green_heart:
shadedclient
40m 15s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 11s

the patch passed

+1 :green_heart:
compile
1m 17s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javac
1m 17s

the patch passed

+1 :green_heart:
compile
1m  7s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
javac
1m  7s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m  3s

the patch passed

+1 :green_heart:
mvnsite
1m 15s

the patch passed

+1 :green_heart:
javadoc
0m 55s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m 39s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
3m 18s

the patch passed

+1 :green_heart:
shadedclient
40m 40s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
262m 12s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 47s

The patch does not generate ASF License warnings.

418m 30s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6634/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6634

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 35958051c223 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
HDFS-17384 / 7a54a91e0cd8ced983698956cf73cd61eff8a2d9

Default Java
Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6634/4/testReport/

Max. process+thread count
3169 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6634/4/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Thanks for contribution. Merged.


Error TS2665: Invalid module name in augmentation.

Hi
I am trying to get plugin to compile on my Mac Ionic Project version, but i am getting following error message:
[ng] ERROR in node_modules/@capacitor-community/bluetooth-le/dist/esm/config.d.ts:1:16 - error TS2665: Invalid module name in augmentation. Module '@capacitor/cli' resolves to an untyped module at<EMAIL_ADDRESS>which cannot be augmented.
Has anyone had this issue before?

I have never seen this problem before. Can you create a minimal repository that reproduces this problem?

HI
I updated the Angular version, and it seems to have solved the issue.


Problem with MariaDB connection

Hello,
We are using now 21.1.1 ans several of my colleagues have the same problem while trying to connect to a MariaDB database :
Current charset is windows-1252. If password has been set using other charset, consider using option 'passwordCharacterEncoding'"
And even with charSET = UTF-8 or paswordCharacterEncoding = UTF-8 they are not able to connect.
On my system I connect to MariaDB, MSSSQL without any problem : Windows is OK Linux in VirtualBox OK.
Will be glad to understand what is the root cause of the problem.
Regards
JP Pozzi

I forgot to say that MariaDB databases are on Centos systems with MariaDB 10.4.18

@jppo could you provide logs? Also, please provide what error appears. Which dbeaver versions and OS versions are used?

Hello,
The exact message (from my colleaques on Teams) is :
"Access denied for user 'xyz@'abcd' (using password: YES)
Current charset is windows-1252. If password has been set using other charset, consider using option 'passwordCharacterEncoding'"
Regards
JP Pozzi
De: "Yvan GODARD" @.>
À: "dbeaver/dbeaver" @.>
Cc: "jppo" @.>, "Mention" @.>
Envoyé: Mercredi 23 Juin 2021 10:37:10
Objet: Re: [dbeaver/dbeaver] Problem with MariaDB connection (#12944)
[ https://github.com/jppo | @jppo ] could you provide [ https://github.com/dbeaver/dbeaver/wiki/Log-files | logs ] ? Also, please provide what error appears. Which dbeaver versions and OS versions are used?
—
You are receiving this because you were mentioned.
Reply to this email directly, [ https://github.com/dbeaver/dbeaver/issues/12944#issuecomment-866645205 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/ABSPJK6KSI33T7OCTN3VYKLTUGMLNANCNFSM47DYR3VQ | unsubscribe ] .

Hello @jppo
Can you please tell me more about how exactly you are connecting to databases in DBeaver?
Video or screenshots can be also very helpful.

there is no update on the issue for a long time.
If it is still actual for you - feel free to reopen it with additional info that could help to reproduce an issue

Hello,
I did not reproduce The erroneous behaviour, and it was with an old version ...
So closing it is good thing.
Regards
JP P
De: "Yvan GODARD" @.>
À: "dbeaver/dbeaver" @.>
Cc: "jppo" @.>, "Mention" @.>
Envoyé: Mardi 14 Septembre 2021 15:39:24
Objet: Re: [dbeaver/dbeaver] Problem with MariaDB connection (#12944)
there is no update on the issue for a long time.
If it is still actual for you - feel free to reopen it with additional info that could help to reproduce an issue
—
You are receiving this because you were mentioned.
Reply to this email directly, [ https://github.com/dbeaver/dbeaver/issues/12944#issuecomment-919160711 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/ABSPJK77H2KMZKLSMC2FADTUB5GAZANCNFSM47DYR3VQ | unsubscribe ] .
Triage notifications on the go with GitHub Mobile for [ https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 | iOS ] or [ https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub | Android ] .


locally installed readthedocs

Details

Project URL:
Build URL (if applicable):
Read the Docs username (if applicable):

Expected Result
I've installed readthedocs locally accorging to this manual: http://docs.readthedocs.io/en/latest/install.html#installing-read-the-docs
This manual is completed by me on Debian VM, up to and including "building documentation for pip"
(I've managed to download it as epub and it seems correct)
BUT!
I was expecting (don't know why, but it is not mentioned explicitly that this will not be working) that the "Search" function will be .. functioning.
Actual Result
Actually, I get an error like this:

ConnectionError at /projects/pip/search/

ConnectionError(<urllib3.connection.HTTPConnection object at 0x7f33d42e5710>: Failed to establish a new connection: [Errno 111] Connection refused) caused by: NewConnectionError(<urllib3.connection.HTTPConnection object at 0x7f33d42e5710>: Failed to establish a new connection: [Errno 111] Connection refused)

Request Method:     GET
Request URL:    http://<IP_ADDRESS>:8000/projects/pip/search/?q=Pypa
Django Version:     1.8.3
Exception Type:     ConnectionError
Exception Value:

ConnectionError(<urllib3.connection.HTTPConnection object at 0x7f33d42e5710>: Failed to establish a new connection: [Errno 111] Connection refused) caused by: NewConnectionError(<urllib3.connection.HTTPConnection object at 0x7f33d42e5710>: Failed to establish a new connection: [Errno 111] Connection refused)

Exception Location:     /home/marchuk/rtd/local/lib/python2.7/site-packages/elasticsearch/connection/http_urllib3.py in perform_request, line 85
Python Executable:  /home/marchuk/rtd/bin/python
Python Version:     2.7.8
Python Path:

['/home/marchuk/rtd/checkouts/readthedocs.org',
 '/home/marchuk/rtd/lib/python2.7',
 '/home/marchuk/rtd/lib/python2.7/plat-x86_64-linux-gnu',
 '/home/marchuk/rtd/lib/python2.7/lib-tk',
 '/home/marchuk/rtd/lib/python2.7/lib-old',
 '/home/marchuk/rtd/lib/python2.7/lib-dynload',
 '/usr/lib/python2.7',
 '/usr/lib/python2.7/plat-x86_64-linux-gnu',
  '/usr/lib/python2.7/lib-tk',
  '/home/marchuk/rtd/local/lib/python2.7/site-packages',
  '/home/marchuk/rtd/checkouts/readthedocs.org']

Server time:    Fri, 1 Jul 2016 04:44:27 -0500

every time I try to perform a search

Sounds like you aren't running elasticsearch. The error looks odd, I'd expect port numbers there. Can you edit with error pasted as a code block, not a quoted comment?

Also:
This bug is being marked as community effort. The core team will try to facilitate resolution with this issue, but without the resources to support external installations outside of our production environment, we must rely on the community to help.
You can read more information on our philosophy around supporting Read the Docs as an open source and volunteer run effort here:
http://docs.readthedocs.io/en/latest/open-source-philosophy.html

Sounds like you aren't running elasticsearch

Should I ? It is not mentioned on the page. Maybe the docs are lacking..

@62mkv To build the project locally, you will need to pip install the requirements.txt file -- see README pip install -r requirements.txt https://github.com/rtfd/readthedocs.org/blob/master/requirements/pip.txt and requirements file.
This file includes elasticsearch among the dependencies.

I think the documentation should explicitly mention Elasticsearch, Redis (and possibly PostgreSQL too). It would also be good to add a link to http://docs.readthedocs.io/en/latest/rtfd.html?highlight=elasticsearch#elastic-search-setup
This could be a good task for new contributors.

Hey, can I take up this bug? I am a newbie

Is this still an issue? I can take it.

Hi @JosemyD, yes, this is still needs to be addressed. You find the installation document at https://github.com/rtfd/readthedocs.org/blob/master/docs/install.rst.

Hello! I have installed the project locally according to docs.readthedocs.io/en/latest/install.html#installing-read-the-docs.
I am still getting this as an issue whenever I use search from home page.
The exact error is something like this:
Request Method: GET
Request URL: http://<IP_ADDRESS>:8000/search/?q=python

File "/home/shubham/virtualenv/rtd/local/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
  149.                     response = self.process_exception_by_middleware(e, request)

File "/home/shubham/virtualenv/rtd/local/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
  147.                     response = wrapped_callback(request, *callback_args, **callback_kwargs)

File "/home/shubham/virtualenv/rtd/checkouts/readthedocs.org/readthedocs/search/views.py" in elastic_search
  49.                 request, user_input.query, language=user_input.language)

File "/home/shubham/virtualenv/rtd/checkouts/readthedocs.org/readthedocs/search/lib.py" in search_project
  49.     return ProjectIndex().search(body)

File "/home/shubham/virtualenv/rtd/checkouts/readthedocs.org/readthedocs/search/indexes.py" in search
  208.                               body=body, **kwargs)

File "/home/shubham/virtualenv/rtd/local/lib/python2.7/site-packages/elasticsearch/client/utils.py" in _wrapped
  69.             return func(*args, params=params, **kwargs)

File "/home/shubham/virtualenv/rtd/local/lib/python2.7/site-packages/elasticsearch/client/__init__.py" in search
  504.             params=params, body=body)

File "/home/shubham/virtualenv/rtd/local/lib/python2.7/site-packages/elasticsearch/transport.py" in perform_request
  307.                 status, headers, data = connection.perform_request(method, url, params, body, ignore=ignore, timeout=timeout)

File "/home/shubham/virtualenv/rtd/local/lib/python2.7/site-packages/elasticsearch/connection/http_urllib3.py" in perform_request
  85.             raise ConnectionError('N/A', str(e), e)

Exception Type: ConnectionError at /search/
Exception Value: ConnectionError(<urllib3.connection.HTTPConnection object at 0x7f7718481c90>: Failed to establish a new connection: [Errno 111] Connection refused) caused by: NewConnectionError(<urllib3.connection.HTTPConnection object at 0x7f7718481c90>: Failed to establish a new connection: [Errno 111] Connection refused

I am a newbie here trying to understand the code so that I can contribute. Thanks for the help!

@shubham76 you need to setup elasticsearch to get the search working (this isn't mandatory to start contributing or for your builds)
You can check this PR with some improvements on the installation guide https://github.com/rtfd/readthedocs.org/pull/3631

@stsewd Okay! I don't think I am going to use search for now. I will leave this aside then!
Thanks for your help! :)


ComboBox searching not works properly for data containing space in ComboBox

Describe the bug
We have faced an issue with ComboBox. searching does not work correctly in ComboBox.
Sample:
SuggestionSample.zip
Steps to reproduce the bug

Run the attached sample.
Open dropdown and focus the combobox text box region.
Type 'f' letter and give the datasource in ComboBox with space in prefix like below
this.SocialMedias.Add(" Facebook");

It appends Facebook text with the whole selection and again types the 'a' letter the selection text gets removed.
Expected behavior
No response
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.3.1: 1.3.230502000
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

Any update on this?

The issue appears to be that when the combo box searches for a string it strips leading spaces off the front of each combobox item.  But, it does not use that information when doing the selection for the "autocomplete".  Hence although it finds the "F" in the second position of the of the item string " Facebook" (because the first position is a space), it will start its selection assuming it found the string in the first position.  This causes it to keep the space and the selection consists of the second position on (which includes the F).
I don't know where this will fit on the priority list, but it can be worked around by trimming the leasing spaces of the items used to populate the combobox.