Feature/cubed sphere parallel meshgen

This PR implements the multi-PE cubed-sphere mesh generator with halos.
The mesh generator internally treats the tiles of the cubed-sphere as separate overlapping meshes. Halos are added at tile boundaries and at partition boundaries on tile interiors.
In addition to the usual mesh.cells() and mesh.nodes() fields, the following the fields are added to mesh cells/nodes objects:

xy. The xy positions of owned data follow the conventions give in the Tiles class. The xy projection of halo data is contiguous with the formal xy projection of the owned data. This should will make interpolation significantly simpler. Cells and nodes both have xy fields.

lonlat. Cells receive lonlat coordinates as well as nodes.

ijt. Cells and nodes have fields giving the (i, j, t) coordinates of the data. Halo (i, j, t) indices are extrapolated from the owned data, i.e. i and j can be less than zero and greater than N for tile-boundary halos. This information can be used to construct a structured CubedSphere function space, similar to StructuredColumns.

Utility classes were written for the mesh generator in src/atlas/meshgenerator/detail/cubedsphere/CubedSphereUtility.h, CubedSphereUtility.cc. The main class is NeighbourJacobian. This handles the xy and ij coordinate transforms between a tile and its four neighbours. I've put it here for the time being, but there's probably a better home for it. It's indispensable for finding the ij and xy positions of halos. I also believe it will be useful for the interpolation of vector fields.
Fig. 1. The xy projection for an N12 cubed sphere mesh with cubed_sphere partitioner and halo = 3 on 8 PEs. Some of the halos overlap in this projection and are not visible in the figure.

Fig 2. The mesh on PE 7 from Fig. 1. Note that the xy projection of the halos is contiguous with owned data projection.

Fig. 3. As Fig. 2, but projected into xyz space using the lonlat coordinates. Note that "gaps" in the cross shaped halo distribution in Fig. 2 do not exist in 3D space.

I've added test executable src/tests/mesh/test_cubedsphere_meshgen.cc
This performs two tests.

The first test makes sure the NeighbourJacobian can correctly place halo points around an N2 grid.
The second test runs the cubed sphere mesh generator with different partitioner and halo-size configurations. It ensures that a simple test field (see below) can be written to owned nodes/cells and distributed to halo nodes cells via the Atlas halo-exchange methods.

Fig 4. A simple test field with f(lon, lat) = sin(3 * lon) * sin(2 * lat)

This PR is enormous. So feel free to arrange a meeting with me if you need to discuss anything!

For completeness, the same as Figs. 1, 2 and 3, but with the equal_regions partitioner.

Hi @wdeconinck,
Just an update that I've added your exception handling suggestions to this JCSDA-internal/atlas PR. It think @MarekWlasak will need to submit ecmwf/atlas PRs for his periodicity class and cubed sphere partitioner before I can create an ecmwf/atlas PR for the mesh generator.
The final mesh generator became a bit of a beast, but at least it's not as big as StructuredMeshGenerator.cc! 😅

https://github.com/ecmwf/atlas/pull/70 is merged so ready when you are  =)

This has been superseded by https://github.com/ecmwf/atlas/pull/73 and https://github.com/JCSDA-internal/atlas/pull/64.


Remove TestConf.configure_network

Because it is skewing the tests, completely bypassing the registry.
https://github.com/bosagora/agora/blob/6b59d77a4bb8231b3b86304ad4aed4c182a36c08/source/agora/test/Base.d#L2050-L2051

I gave a shot to this, and it slows the test down quite a bit. Trying to come up with a solution that doesn't add 50% runtime.


Cache isn't merging newly received data

React version (e.g., 16.8.5)
16.13.1
Concurrent mode yes
Rest Hooks version (e.g., 4.5.9)
5.0.0-k.3 (also tested with latest version)
Describe the bug
Rest-hooks cache isn't merging newly received data. Specifically a boolean property.
The property that isn't being updated:
readonly rejected?: boolean = false;

This property is only returned from the API when rejected:true, otherwise it will be undefined.
To Reproduce
Steps to reproduce the behavior:

Initially fetch a list of resources (no resources have the property "rejected" yet).
State change on the BE to update rejected=true.
Invalidate resource, re-fetch is triggered, new data is fetched and one resource on the list is displaying the "rejected" flag (works as expected).
State change on the BE to update rejected=false.
Invalidate resource, re-fetch is triggered, BUT resource/item isn't updated and still displays rejected.

Expected behavior
The newly fetched data should be merged in and take priority over the stale data in the cache.
Additional context
I've provided two things below: 1) everything I've attempted to fix/workaround the issue; and 2) debugging logs from rest-hooks.
What I've attempted

useResource() + invalidate() (the optimal/expected way)
Imperatively fetch data
Rendering - I modified and attempted all solutions with a refresh control in RN to ensure the list is rendered
Updated how we declare rejected in the resource to be null/false/undefined. Also cleared storage + uninstalled the app, reinstalled to ensure it refreshed the schema.
Invalidated every endpoint registered in the cache
Removed any additional logic in getUrl() within resource so there wasn't any difference in cache keys
Updated to the latest rest-hooks (the mergeDeepCopy functionality has additional logic in the later version).
[Worked] useResetter() - deletes the rest-hooks state. I considered this as the absolute last resort BUT this proved that something was going wrong within rest-hooks and was the only thing that I tried which worked.

Debugging rest-hooks
The goal of logging in the rest-hooks lib was to understand at which point between HTTP response (with fresh data which we observed in the network requests) and the rest-hooks cache.

SimpleRecord.merge() when we pass the new "incoming" data (which actually has rejected:false), the rejected property/value gets stripped after passing it through this.toObjectDefined(). This is why when we merge the two we're using the existing "rejected:true" value.
The difference between the existing and incoming objects in this func is DefinedMemberKeys (here) - so somehow when we look up what the keys are and iterate through them, on the new object we don't have "rejected" in the defined keys (so actually a difference in length of 1 for these arrays - the rejected key).

Can you provide your full Resource and Endpoint definition? Including any classes in the hierarchy that aren't from rest hooks itself?

Have you tried https://resthooks.io/docs/guides/debugging if so can you screenshot the receive action for when you expect the update?

SimpleRecord.merge() when we pass the new "incoming" data (which actually has rejected:false), the rejected property/value gets stripped after passing it through this.toObjectDefined(). This is why when we merge the two we're using the existing "rejected:true" value.
The difference between the existing and incoming objects in this func is DefinedMemberKeys (here) - so somehow when we look up what the keys are and iterate through them, on the new object we don't have "rejected" in the defined keys (so actually a difference in length of 1 for these arrays - the rejected key).

This sounds like the data being sent is not actually including the rejected, and thus if you use the default merge function it will persist the old one. If you simply want to replace the entire copy (which only works if you always return full data - never partial data), you can use the following merge function:
  static merge<T extends typeof SimpleRecord>(
    this: T,
    existing: AbstractInstanceType<T>,
    incoming: AbstractInstanceType<T>,
  ) {
    return this.fromJS(incoming);
  }

@lachiet did this approach work for you?

Closing as no response indicates it worked. If this is not true please report new issue.


Flake: not ok 14 iptables: Ncat: Connection refused.

On multiple occasions this test fails with Ncat: Connection refused..  I noticed in the resource-graphs, there is a giant spike in memory usage up to 5+gig suggesting perhaps the OOM-killer is taking action.  Example failures:

https://cirrus-ci.com/task/4555929878790144
https://cirrus-ci.com/task/5530635595415552
https://cirrus-ci.com/task/5927662238040064

Already tracked in https://github.com/containers/netavark/issues/433

Thanks Paul.


Depth implementation

Great. If that's really how simple the depth algorithm is in its most basic form, then I guess that's good news.
I have two suggestions related to things to keep in the repository, which will be useful for our long-term sanity:

Let's not include "intermediate" files. In this case, this means .og files that we generate from .gfa files. The "source of truth" is in the original .gfa file, and the .og file is derived, so keeping it around is (a) redundant and (b) error-prone if it gets out of date. (This is analogous to the advice never to check in .o files that are the result of compiling C programs.) Instead, let's include some sort of recipe for generating these files. Maybe a Makefile or even just a README saying how to create them.
This is a less hard-and-fast rule, but let's mostly avoid checking in "other people's data." In this case, that means the .gfa files. They are available elsewhere on the Internet, so no need to include them in our repository. Instead, as with the previous bullet point, we can just provide a recipe (either machine-executable or human-readable) for obtaining them.

I'll try to briefly show y'all what I mean in an upcoming PR…

(BTW, including the extremely tiny k.gfa file is probably an exception to the second item, because it is so incredibly tiny…)


Use inside picture tag

Hi,
I am wondering if your plugin is able to handle picture tag ?
<picture>     <source type="image/webp" srcset="/webp/image.webp">     <img src="/img/image.png" alt="Logo"> </picture>

@hugsbrugs were you able to make it work?


pull request for e2e test at 12/23/2016 13:15:11

: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.


Push constants do not get bound to the right resource and overlaps with others when converting to HLSL

When using push constants, they do not get bound to the right resource, and they overlap with other resources that are already bound by other Uniform Buffers. If you try to compile the generated HLSL, you get this error:
error: resource DrawData at register 0 overlaps with resource CanvasData at register 0, space 0
GLSL (Vulkan):

layout(push_constant, binding = 0, std430) uniform DrawData {
	vec2 world_x;
	vec2 world_y;
	[...]
} draw_data;

layout(set = 2, binding = 0, std140) uniform CanvasData {
	mat4 canvas_transform;
	mat4 screen_transform;
	[...]
} canvas_data;

HLSL:
cbuffer DrawData : register(b0)
{
    float2 draw_data_world_x : packoffset(c0);
    float2 draw_data_world_y : packoffset(c0.z);
    [...]
};

cbuffer CanvasData : register(b0)
{
    row_major float4x4 canvas_data_canvas_transform : packoffset(c0);
    row_major float4x4 canvas_data_screen_transform : packoffset(c4);
    [...]
};

You'll need to use the reflection API to assign a DecorationBinding for the push constant block, otherwise it ends up at "b0".

Even if it ends at b0, i don't see why other cbuffers will collide with it. Is there any reason why it can't be treated as any other cbuffer?

Push constants are translated into cbuffers in HLSL, and thus the binding space for UBOs and push constants will collide in some way. DecorationBinding is used to figure out which "b#" binding to use, and you can override those, even for the push constant block before calling compile() to get a consistent mapping. If you're targeting SM 5.1+/DX12, descriptor set decoration will be translated into register(b#, space#) as well.

they do not get bound to the right resource

What is the "right" resource here?

@HansKristian-Work I don't know, I don't personally care unless it does not collide. Reflection can be used afterwards to check what as assigned, so the problem here is that, per OP, both structures are assigned b0. It would be easily fixed if they were assigned different ones.

For the "I don't care" approach, an option to simply not emit any register bindings in HLSL would work in that case. Then you can reflect the HLSL output later. That can be added.

Another weird quirk here is that you should never use "binding = N" on push constant blocks, as it's meaningless in Vulkan. That's why the push constant block is declared with a register declaration to begin with.

Added support to omit any register() declarations per-resource type, so you can rely on d3d compiler for resource assignment.


fix(number-input): use required prop iconDescription in CarbonX icons

Closes #1974
Use required prop iconDescription if it is provided (similar to: https://github.com/IBM/carbon-components-react/blob/master/src/components/NumberInput/NumberInput.js#L334)
Changelog
Changed

use iconDescription or Carbon X icons
updated this.props.iconDescription to iconDescription

Thank you for the suggestions @asudoh! 🎉


What replaces directScroller?

I saw directScroller was gone, but I'm not sure what replaces it? Here's my code:
const scroller = Scroll.directScroller;

class MyComponent extends Component {

...

  scrollToTop() {
    scroller.scrollTo("content", {
      duration: 0,
      smooth: false
    });
  }

...

}

Yes, you are right.
This should do the trick.
const scroller = Scroll.scroller;

class MyComponent extends Component {

...

  scrollToTop() {
    scroller.scrollTo("content", {
      duration: 0,
      smooth: false
    });
  }

...

}

Perfect, thanks!


Build issue for Apollo 3.0 in Build and Release your Docker Container step

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information
Dell XPS 15
Intel Core i7 7700 HQ
16 GB RAM
GTX 1050 4GB

OS Platform and Distribution : Linux Ubuntu 16.04 LTS on VMWare Player on Windows:
Apollo installed from source:
Apollo version trying to install: 3.0:

Steps to reproduce the issue:
I am trying to follow instructions to Build and Release as on this page: https://github.com/ApolloAuto/apollo/blob/master/docs/howto/how_to_build_and_release.md
And at the bash apollo.sh build command I receive the following error:
ERROR: /apollo/modules/calibration/lidar_ex_checker/BUILD:5:1: C++ compilation of rule '//modules/calibration/lidar_ex_checker:lidar_ex_checker_lib' failed (Exit 4).
gcc: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
INFO: Elapsed time: 132.634s, Critical Path: 119.60s

I have also tried the other two commands bash apollo.sh build_cpu and bash apollo.sh build --local_resources 2048,1.0,1.0 and gotten the same error.
Can someone help me with this? I have not installed Apollo ever before. Do I need to install the previous versions first before I can go to 3.0
Also, I'm installing without hardware. Thank you
Supporting materials (screenshots, command lines, code/script snippets):

Please try to give more memory to your VM(8G would be better for -j4, the more, the better) or reduce the job number to save memory usage.

How to reduce the job number?

@natashadsouza


Fix for IndexError in Manage Form test case. Also, added Request API directory

We were getting IndexError in Manage Form test case when there were no normal forms available.
To resolve this issue we added few steps where we are checking if normal forms are available or not and if they are not, we are restoring archive forms and then verifying the test case.
Also, added Request API directory as it was not present in my code.

Looks good -- feel free to merge!


Did you have this error msg when importing project in AS?

when import project in my AS, gradle compiled with error:
Error:Execution failed for task ':mylibrary:transformResourcesWithMergeJavaResForRelease'.

com.android.build.api.transform.TransformException: com.android.builder.packaging.DuplicateFileException: Duplicate files copied in APK META-INF/DEPENDENCIES
File1: /home/sage/Documents/android/CoolMusicPlayer/mylibrary/libs/httpcore-4.4.3.jar
File2: /home/sage/Documents/android/CoolMusicPlayer/mylibrary/libs/httpclient-4.5.1.jar

did you run into this error in import project in AS? any solution with you? thanks.
ps, this project looks like cool, I will keep attention with it.

I'm really sorry to be late.
My environment was not a problem in the AS2.1 beta2.
What's your version?


[STIX-web] text-italic used instead of math-italic

(Moving this here from another thread.)
@dpvc wrote:

MathJax v2 maps the MathML variants to the font files via a list of fonts to search sequentially, and for mathvariant="italic", it starts with STIXMathJax_Main-Italic followed by STIXMathJax_Normal-Italic.  That means that if you use <mi>f</mi> (or <mi mathvariant="italic">f</mi>), the "f" will be taken from STIXMathJax_Main-Italic, which is the text italic version, whereas <mi>𝑓</mi> will be taken from STIXMathJax_Normal-Italic, the Plane1 version.  The MathML spec says these should be treated the same, so this is technically an error.

This has to do with the font data for the STIX-Web font.  You can use the remapping facilities in MathJax to adjust this.

	MathJax.Hub.Register.StartupHook("SVG Jax Ready", function () {
	  var SVG = MathJax.OutputJax.SVG;
	  SVG.Augment({
	    FONTDATA: {
	      VARIANT: {
	        italic: {
	          offsetA: 0x1D434,
	          remap: {0x1D455: 0x210E}
	        },
	        'bold-italic': {
	          offsetA: 0x1D434,
	          remap: {0x1D455: 0x210E}
	        }
	      }
	    }
	  });
	});

This will add a remapping of the alphabetic characters to the Plane1 positions, and remap the lower-case "h" back to the letter-like symbols (since unicode leaves some holes in Plane1 when there are similar glyphs elsewhere).  This code can be added to mathjax-node so that you can use it there.  Note that this does mean all the alphabetic characters in the italic and bold-italic fonts will be mapped to the Pane1 versions, which are slightly different, so you may notice some different layout.  In addition to the "f", the "j" will also be noticeably affected, and this should help with "j" in superscripts, for example (there was an issue about this at one point, and I didn't think about the real issue, which is the incorrect use of text-italic for math-italic in the STIXMathJax fonts).

Technically, we should be mapping the normal and bold variants to their math counterparts as well, and also the greek letters, but I think that is probably overkill for your needs, but something to get right in v3.

I didn't check but I'm assuming this affects HTML-CSS as well and a similar patch can be applied (not that that matters for v3).

@dpvc any chance a fix could make it into 2.7.5?

@pkra, OK, I've made the fix.  It took a bit of fiddling to get the Greek to work, but I found an error in the mappings while doing it, so this fixes that as well.

==> In testsuite
MathMLToDisplay/Characters/issue1923.html

Thank you very much!

Just FYI, this has greatly improved spacing with STIX-web -- thank you again for pulling it into 2.7.5.


Please help me with loadmore .I am using volley

Do we have to give the progessbar view or by default it will display the progress bar? I could not see progressbar.

You can use  ultimateRecyclerView.enableLoadmore(); to add default progress bar .
You can also use          simpleRecyclerViewAdapter.setCustomLoadMoreView(LayoutInflater.from(this)                 .inflate(R.layout.custom_bottom_progressbar, null));  to customize your view.

#276 this should be done for the load more issue.  @raviteja83


Add embed dynamic font data support

This should fix #4600 - it's my first PR, so even if it's a small change, I think someone should double-check :blush:

The code looks fine :) Is this enough to properly generate the .tres format for DynamicFontData?
@reduz Can you check this one, as you just wrote this piece of code, so you likely know if it was just an omission or if there was a reason not to bind these methods.

This PR now has merge conflicts since recent work done DynamicFont. Is it still relevant, and if so could you rebase it on top of the current master branch?

This way implemented in a similar but slightly different way by @reduz in 0bbb0d0, so closing. Thanks for your PR though and issue though :)


16394 add ack functionality

This PR adds ACK functionality to the waters and report submission endpoints.
Test Steps:

Run ReportStream
Submit the following HL7. Ensure the content type header has been specified as "application/hl7-v2"

MSH|^~\&|Epic|Hospital|LIMS|StatePHL|20241003000000||ORM^O01^ORM_O01|4AFA57FE-D41D-4631-9500-286AAAF797E4|T|2.5.1|||AL|NE

The response body should be HL7

Changes

New ACK functionality
Ability to pick apart more MSH header segments

Checklist
Testing

[x] Tested locally?
[x] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[x] Added tests?

Linked Issues

Fixes #16394

@arnejduranovic
Just looked this up. Are we want to handle the SU value as well?

Are any tests required for the fields that have been "widened" or are our existing tests sufficient?

I tested locally with the test data in the PR description and got this response when I set the ignore.ignore-etor-ti sender's hl7AcknowledgementEnabled to true:
MSH|^~\&|ReportStream|CDC|Epic|Hospital|20241202194106.427+0000||ACK|372acc8a-8b21-4d6f-a78e-4f13dbabc920|T|2.5.1|||NE|NE
MSA|CA|4AFA57FE-D41D-4631-9500-286AAAF797E4

@brick-green FYI


Added Lup Yuen Lee to contributors

Summary
Added myself (Lup Yuen Lee) as PMC and Committer to the list of contributors. Sorry I missed this earlier.
Impact
Updated the list of contributors.
Testing
None

One momento sorry @lupyuen.. build fails.. and that is done to update website.. I can see that previous builds also failed and so the website is not updated o_O
@btashton could you please take a look as https://github.com/apache/nuttx-website/actions/runs/4975335982/jobs/8902681849?pr=95? I think https://github.com/apache/nuttx-website/pull/94 did not do the trick.. and there are no special characters now in the username.. and HEAD contains Your commit that also has no special characters in the username.

Can this be caused by GitHub blocking vulnerable ActiveSupport GEM? We have <IP_ADDRESS>. patched version is <IP_ADDRESS> and the version 7 is already out. See Security tab at the top (https://github.com/apache/nuttx-website/security/dependabot). On my BSD box I was not able to setup this environment :-(
Or CI script using node12 instead node16 calls as reported here:

build
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2, actions/setup-python@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.

Thanks @btashton.. can you see that "All checks have failed" here?
Looking at the "Build Site" part:

0s
##[debug]Evaluating condition for step: 'Build Site'
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: Build Site
##[debug]Loading inputs
##[debug]Loading env
Run export GEM_HOME=$HOME/.gem
  export GEM_HOME=$HOME/.gem
  export PATH=$PATH:$GEM_HOME/bin
  username="`git log -1 --pretty=format:'%an'`"
  email="`git log -1 --pretty=format:'%ae'`"
  git config --global user.name $username
  git config --global user.email $email
  ./publish.sh
  shell: /usr/bin/bash -e {0}
  env:
    pythonLocation: /opt/hostedtoolcache/Python/3.8.16/x64
    LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.8.16/x64/lib
##[debug]/usr/bin/bash -e /home/runner/work/_temp/b2a7b350-874a-4137-b8f2-3d611c0679e3.sh
usage: git config [<options>]

Config file location
    --global              use global config file
    --system              use system config file
    --local               use repository config file
    --worktree            use per-worktree config file
    -f, --file <file>     use given config file
    --blob <blob-id>      read config from given blob object

Action
    --get                 get value: name [value-pattern]
    --get-all             get all values: key [value-pattern]
    --get-regexp          get values for regexp: name-regex [value-pattern]
    --get-urlmatch        get value specific for the URL: section[.var] URL
    --replace-all         replace all matching variables: name value [value-pattern]
    --add                 add a new variable: name value
    --unset               remove a variable: name [value-pattern]
    --unset-all           remove all matches: name [value-pattern]
    --rename-section      rename section: old-name new-name
    --remove-section      remove a section: name
    -l, --list            list all
    --fixed-value         use string equality when comparing values to 'value-pattern'
    -e, --edit            open an editor
    --get-color           find the color configured: slot [default]
    --get-colorbool       find the color setting: slot [stdout-is-tty]

Type
    -t, --type <type>     value is given this type
    --bool                value is "true" or "false"
    --int                 value is decimal number
    --bool-or-int         value is --bool or --int
    --bool-or-str         value is --bool or string
    --path                value is a path (file or directory name)
    --expiry-date         value is an expiry date

Other
    -z, --null            terminate values with NUL byte
    --name-only           show variable names only
    --includes            respect include directives on lookup
    --show-origin         show origin of config (file, standard input, blob, command line)
    --show-scope          show scope of config (worktree, local, global, system, command)
    --default <value>     with --get, use default value when missing entry

Error: Process completed with exit code 129.
##[debug]Finishing: Build Site

Should I just Merge this one and next checks will use updated scripts?

@lupyuen you do not have my change, can you try a rebase so we know if that resolves the issue here?

Sure I'll rebase later when I'm back at my computer. Thanks everyone :-)

Thank you @btashton !! :-)

My next PR have "All checks passed" so the fix is working. I will merge this PR now. Thank you for verification @btashton :-)


Bump all Cargo.toml versions to v0.10.1

Codecov Report

Merging #463 (84ef474) into main (d04c39d) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 84ef474 differs from pull request most recent head 8b34701. Consider uploading reports for the commit 8b34701 to get more accurate results

@@           Coverage Diff           @@
##             main     #463   +/-   ##
=======================================
  Coverage   90.82%   90.82%
=======================================
  Files         159      159
  Lines        9246     9246
=======================================
  Hits         8398     8398
  Misses        848      848

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 d04c39d...8b34701. Read the comment docs.


Bug- handle sentence input

Handle a sentence input from user
Description
To accept sentence input from the user for encryption
Resources
https://www.geeksforgeeks.org/vigenere-cipher/

** Bounty points alloted : 50 **
Any further improvements along with bug fixes will be given brownie points. If the
countributor
sees any further inprovements that can be done to this project ,raise an issue.

Hey, could I please be assigned to this?

You've been assigned to the issue! Go ahead and work on it!

Hey could i please be assigned to this?

Hey, I'm so sorry for the late reply, you've been assigned to the issue. Hope you have fun working on it!:)

Can you please assign me this?

Is it possible to reassign me this?


Update Simple Icons Version

From the next major release of simple-icons (v11, releasing on May 26, 2024), We will begin removing third-party extensions from our README list that are not up to date with at least the previous major release.
For example, when v11 is released, we will remove any extensions that don't support v10.0.0 or higher.
How do I keep my package up to date?
There are two methods that prove most popular among other maintainers. It is up to you which you implement.
Using @latest from a CDN
Projects that use the CDN version of the project (jsDelivr/unpkg) can keep up to date simply by changing the version number in their code to @latest. That way - you're always using the most up to date version of the icon package.
Running a weekly CRON
Many of our third party contributors make use of GitHub actions, and a weekly CRON job to query that the version number of the main package has changed, and then update and build their own package. A great example of this is the DrawIO package by mondeja. The main package is released consistently on a Sunday - so we recommend running your CRON job on a Monday or Tuesday.

When you've got your extension running one of the above methods, drop us a Pull Request to update your version number on the README.
If you're in need of any support in implementing one of the above - please feel free to start a discussion or ask us on Discord.

@sachinraja it would be awesome to get a new release of this library :) missing couple icons already

Heads up @sachinraja - as of v12 releasing on Sunday 26th May, this package is no longer listed under the Simple Icons extensions. If you bring it in line with the notes above we can look to re-add it to the list.


[AIRFLOW-3099] Complete list of optional airflow.cfg sections

Make sure you have checked all steps below.
Jira

[x] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-XXX
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

This PR just completes the list of optional airflow.cfg sections added by https://github.com/apache/incubator-airflow/pull/3934 - feel free to add more if I missed any.
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Simple change to logging.
Commits

[x] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[x] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

Merging #4002 into master will increase coverage by <.01%.
The diff coverage is 20%.

@@            Coverage Diff            @@
##           master   #4002      +/-   ##
=========================================
+ Coverage    75.5%   75.5%   +<.01%
=========================================
  Files         199     199
  Lines       15947   15948       +1
=========================================
+ Hits        12040   12041       +1
  Misses       3907    3907

Impacted Files
Coverage Δ

airflow/bin/cli.py
64.48% <20%> (+0.04%)
:arrow_up:

Continue to review full report at Codecov.

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

LGTM


Upgrade to JUnit 4

JUnit version 5 has been out for a while so it's time to upgrade from version 3 to 4, right? ;)
My end goal with this is to remove AbstractFlowExecutionTests's inheritance on JUnit 3's TestCase which cases all sorts of weirdness in my tests using Spring Webflow with JUnit 4 (need to use @RunWith(JUnit4.class)). This prevents my flow tests from using JUnit 5.

I've already signed Pivotal's CLA, by the way.

Also filed as SWF-1738 on jira.spring.io.

@edysli, thanks for the contribution!
I think internal tests should go directly to JUnit 5 while the flow test support should make it optional to upgrade to either JUnit 5 or 4. That way we could get this into a maintenance release without waiting for another minor or major release.
I've also split this into two parts, SWF-1739 and SWF-1740 with some initial thoughts. If you'd like to rework the PR accordingly that would be much appreciated!

Hey @rstoyanchev, thanks for sharing your thoughts! :) That makes sense, I'll split this PR in two then.


Move Commandtypes API to Commands

We have not discussed it but I think it is reasonable

It is more logically to have the same first level API point to commands related requests
It is consistent with Notifications https://github.com/tananaev/traccar/blob/master/src/org/traccar/api/resource/NotificationResource.java#L52
We removing some code duplication

PS: Do not know how to treat with Gabor Somogyi copyright in this case

You can probably add copyright line to the CommandResource class. Otherwise looks great.

Added copyright to CommandResource

Merged, thanks.


🚀 Feature: Add light mode to microsite(backstage.io)

🔖 Feature description
Our Microsite is built on top of Docusaurus which supports both dark and light mode. Documentation and other generated pages already look good/alright when light mode is enabled but our custom pages is does not currently support light mode and therefore those pages remain dark with a light menu bar which does not look very pleasing.
It would be fantastic if anyone from the community with CSS skills would be willing to help out updating our styles to support both light and dark mode 🙏
More info can be obtained at
https://docusaurus.io/docs/api/themes/configuration
https://docusaurus.io/docs/styling-layout
🎤 Context

✌ Possible Implementation
No response
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, I don't have time to work on this right now

This is the only remaining task from the previous meta issue #12019


[BUG] MINIMUM_GCC_VERSION is incorrect

Environment
Operating System: Linux
Version / Commit SHA: 11.0
Other: gcc
Describe the bug
MINIMUM_GCC_VERSION is currently too high, with value 9.3.1.
As the comment above in cmake/config/OpenVDBVersions.cmake states:
  # @Note  Compiler versions are not really a hard and fast rule, you just need
  # a compiler with complete support for our MINIMUM_CXX_STANDARD (currently 17).
  # What's usually important is that the version of libstdc++ and glibc in use
  # matches. Compilers other than GCC should provide options to ensure this
  # targetting e.g. --gcc-toolchain and -fgnuc-version with Clang.

I've been modifying the value to 8.4.0 and it works fine.

Hi @mwestphal,
We're working off the following comment in the C++ 17 status page from the GCC manual https://gcc.gnu.org/projects/cxx-status.html:

Some C++17 features are available since GCC 5, but support was experimental and the ABI of C++17 features was not stable until GCC 9.

The minor/patch version numbers were chosen to match the VFX platform, but strictly speaking this version could indeed by 9.0.0. From the comment quoted above, I don't think we want to drop it further. You're welcome to use earlier versions and can define the -D DISABLE_DEPENDENCY_VERSION_CHECKS=OFF to suppress these requirements, but these are the minimum versions we guarantee support for

-D DISABLE_DEPENDENCY_VERSION_CHECKS=OFF I missed this, indedd, an acceptable fix.


config: yaml_parser: Handle $log_level element for special case

Which issue(s) this PR fixes:
Closes https://github.com/fluent/fluentd/issues/4463.
What this PR does / why we need it:
This is because @log_level is invalid for YAML.
Instead, we should interpret $log_level as @log_level on YAML parser.
Docs Changes:
Needed. Will handle on it.
Release Note:
Same as title.

Thanks! I will check this tomorrow!

I confirmed that it works fine.
config:
  - source:
      $type: tail
      tag: sample
      path: /tmp/test.log
      pos_file: /tmp/tail-test.pos
      $log_level: debug
      parse:
        $type: none

  - match:
      $tag: '**'
      $type: stdout

$ bundle exec fluentd -c /Users/config.yaml
2024-05-02 12:19:15 +0900 [info]: init supervisor logger path=nil rotate_age=nil rotate_size=nil
2024-05-02 12:19:15 +0900 [info]: parsing config file is succeeded path="/Users/config.yaml"
2024-05-02 12:19:15 +0900 [info]: gem 'fluentd' version '1.16.5'
2024-05-02 12:19:15 +0900 [warn]: define <match fluent.**> to capture fluentd logs in top level is deprecated. Use <label @FLUENT_LOG> instead
2024-05-02 12:19:15 +0900 [info]: using configuration file: <ROOT>
  <source>
    @type tail
    @log_level "debug"
    tag "sample"
    path "/tmp/test.log"
    pos_file "/tmp/tail-test.pos"
    <parse>
      @type "none"
      unmatched_lines
    </parse>
  </source>
  <match **>
    @type stdout
  </match>
</ROOT>
2024-05-02 12:19:15 +0900 [info]: starting fluentd-1.16.5 pid=36950 ruby="3.3.0"
2024-05-02 12:19:15 +0900 [info]: spawn command to main:  cmdline=["/opt/homebrew/Cellar/ruby/3.3.0/bin/ruby", "-r/opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/bundler/setup", "-Eascii-8bit:ascii-8bit", "/opt/homebrew/lib/ruby/gems/3.3.0/bin/fluentd", "-c", "/Users/nakayamashingo/Desktop/desktop/fluentd/config.yaml", "--under-supervisor"]
2024-05-02 12:19:15 +0900 [info]: #0 init worker0 logger path=nil rotate_age=nil rotate_size=nil
2024-05-02 12:19:15 +0900 [info]: adding match pattern="**" type="stdout"
2024-05-02 12:19:15 +0900 [info]: adding source type="tail"
2024-05-02 12:19:15 +0900 [warn]: #0 define <match fluent.**> to capture fluentd logs in top level is deprecated. Use <label @FLUENT_LOG> instead
2024-05-02 12:19:15 +0900 [info]: #0 starting fluentd worker pid=36953 ppid=36950 worker=0
2024-05-02 12:19:15 +0900 [debug]: #0 Compacted entries: ["/tmp/test.log"]
2024-05-02 12:19:15 +0900 [debug]: #0 Remove missing entries. existing_targets=["/tmp/test.log"] entries_after_removing=["/tmp/test.log"]
2024-05-02 12:19:15 +0900 [debug]: #0 tailing paths: target = /tmp/test.log | existing =
2024-05-02 12:19:15 +0900 [info]: #0 following tail of /tmp/test.log
2024-05-02 12:19:15 +0900 [info]: #0 fluentd worker is now running worker=0
2024-05-02 12:19:15.954638000 +0900 fluent.info: {"pid":36953,"ppid":36950,"worker":0,"message":"starting fluentd worker pid=36953 ppid=36950 worker=0"}
2024-05-02 12:19:15.955250000 +0900 fluent.debug: {"message":"Compacted entries: [\"/tmp/test.log\"]"}
2024-05-02 12:19:15.955269000 +0900 fluent.debug: {"existing_targets":["/tmp/test.log"],"entries_after_removing":["/tmp/test.log"],"message":"Remove missing entries. existing_targets=[\"/tmp/test.log\"] entries_after_removing=[\"/tmp/test.log\"]"}
2024-05-02 12:19:15.955695000 +0900 fluent.debug: {"message":"tailing paths: target = /tmp/test.log | existing = "}
2024-05-02 12:19:15.955829000 +0900 fluent.info: {"message":"following tail of /tmp/test.log"}
2024-05-02 12:19:15.955898000 +0900 fluent.info: {"worker":0,"message":"fluentd worker is now running worker=0"}
^C2024-05-02 12:19:18 +0900 [info]: Received graceful stop
2024-05-02 12:19:18 +0900 [info]: #0 fluentd worker is now stopping worker=0
2024-05-02 12:19:18.996849000 +0900 fluent.info: {"worker":0,"message":"fluentd worker is now stopping worker=0"}
2024-05-02 12:19:18 +0900 [info]: #0 shutting down fluentd worker worker=0
2024-05-02 12:19:18 +0900 [info]: #0 shutting down input plugin type=:tail plugin_id="object:cf8"
2024-05-02 12:19:18 +0900 [info]: #0 shutting down output plugin type=:stdout plugin_id="object:cd0"
2024-05-02 12:19:19 +0900 [info]: Worker 0 finished with status 0

@Shingo-Nakayama Thanks!

Thanks!

BTW, Which versions will this feature be enabled? 1.17.1 or 1.16.6?

I will backport this to 1.16.6 if there is no objection.

OK. I don't have any objections. Let's backport this to v1.16.6.


Workbench documents - Sections 12 & 13 of issue 862

Here are the workbench documents from https://github.com/nimbella-corp/nimbella-cli/pull/327
Per @joshuaauerbachwatson, request, I have created a new pull request in this repo.

Since we are in phase of just getting some missing documents drafted, I'm not going to pick a lot of nits.  All of our documents will likely be wordsmithed and revised going forward.
But, I'd like to see two things corrected before I merge this:

There are broken image links in workbench-playground-1-intro.md.   The images should be in the repo and the links should be relative.
The document workbench-playground-3-deploy-from-github.md is misnamed.   It is about a workbench feature but not a playground feature.

I also note (@JamieDawson, you don't have to fix this prior to merge) that these documents are not connected to the top-level structure in the sidebar.  I will do something about that after the merge.  I believe all of our documents should be connected to "the structure" even though we are pretty likely to revise that structure extensively as the work progresses.

@joshuaauerbachwatson

There are broken image links in workbench-playground-1-intro.md. The images should be in the repo and the links should be relative.

Lately, I've just been uploading my images to Flickr and then getting the links from there.  Do you believe we should create an images folder and collectively start adding the images there?

We should put the images into our repo - is there a reason to use flickr? If not our repo then i would use a nimbella bucket instead, which is also something we control.

Lately, I've just been uploading my images to Flickr and then getting the links from there. Do you believe we should create an images folder and collectively start adding the images there?

There would be no need to create another images folder.   There already is one in static/img in this repository.   When @niks3089 moved things over from newdoc and established the new structure, he put the images from some of my documents there, alongside some docusaurus ones, so I just assumed we'd continue that convention.
In fact, I am open to other possibilities but the links you have there now don't work (at least they didn't for me).   And I think it is important to be consistent.  So, I believe you should put your images in static/img for now and we can separately discuss alternatives as things evolve.

There are broken image links in workbench-playground-1-intro.md. The images should be in the repo and the links should be relative.

Images added to static/img. Thank you for addressing that. I will no longer us Flickr.

The document workbench-playground-3-deploy-from-github.md is misnamed. It is about a workbench feature but not a playground feature.

Renamed file.

@JamieDawson please link these docs to the side bar.

Documents are linked in the sidebar.
A git rebase and git diff --origin workbench-documents was applied to this repo for completion.

Document ready for review.

All image fixes Rodric requested have been applied.
Pending review.

Hey @rabbah , I believe I made a mistake with this.
After fixing the error "GitHub this branch has conflicts that must be resolved" which was above this post. I clicked the "Squash and merge" button not realizing I could do that on my own. I was under the impression that it would need a 2nd person to ok the merge request.

It's OK. If there are remaining issues, you can handle them in another PR.
(We haven't enabled checks yet for convenience and you have write privileges and why you can merge your own PRs at this time.)


feat: Sanitize iframe URL

What it solves
Sanitize iframe URL for avoid any JS execution

I don't think you need HTML entity unescaping. React isn't inserting the iframe URL in HTML, it sets it as a DOM property.
So if someone passes a URL in HTML encoding, it will be inserted as is.

I don't think you need HTML entity unescaping. React isn't inserting the iframe URL in HTML, it sets it as a DOM property. So if someone passes a URL in HTML encoding, it will be inserted as is.

Yeah I can remove it. I took the script from a library and is working with more cases than our concrete one

It would be nice to show an error straight away.

After N seconds:

The isSameURL() check will fail here as your comparing the sanitized URL with the original appUrl. It's probably best to santiize inside useSafeAppUrl(). What do you think?

I did it. Moved to the hook. I changed the location of the function itself and added the tests

Redirecting to Apps IMHO would be no bueno, as it will not alert the user and hide the problem.
If they stay on that page and see an error, they will be aware of potential phishing attempts.

Redirecting to Apps IMHO would be no bueno, as it will not alert the user and hide the problem.
If they stay on that page and see an error, they will be aware of potential phishing attempts.

I like the error approach. Take a look now. I'm throwing an error if the sanitize call detect a javascript: injection warning the user

It crashes the app immediately now, good 👍
The error is generic tho, something we could improve. But good enough for now.

@JagoFigueroa did you test this?

Excelente implementación camarada, looks good to me as well.
Un saludo ;)


IAudioClient "System.MissingMethodException"

Hi There,
This is triggered on dev build 00969 when connecting to gateway. OS this is being debugged on is Ubuntu 16.04 & is targeting netcore 2.1. Previous build used was 00957 which is fine. Reason for updating to latest build was to see if anything was new.
13:16:37 Hidden Ex    Detected Hidden Exception!:
System.AggregateException: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread. (WebSocket connection was closed) ---> System.Exception: WebSocket connection was closed ---> System.MissingMethodException: Method not found: 'System.Threading.Tasks.Task`1<Discord.Audio.IAudioClient> Discord.IAudioChannel.ConnectAsync(System.Action`1<Discord.Audio.IAudioClient>)'.
   at Discord.WebSocket.DiscordSocketClient.ProcessMessageAsync(GatewayOpCode opCode, Nullable`1 seq, String type, Object payload)
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
   at Discord.WebSocket.DiscordSocketClient.ProcessMessageAsync(GatewayOpCode opCode, Nullable`1 seq, String type, Object payload)
   at Discord.EventExtensions.InvokeAsync[T1,T2,T3,T4](AsyncEvent`1 eventHandler, T1 arg1, T2 arg2, T3 arg3, T4 arg4)
   at Discord.API.DiscordSocketApiClient.<.ctor>b__24_0(Byte[] data, Int32 index, Int32 count)
   at Discord.Net.WebSockets.DefaultWebSocketClient.RunAsync(CancellationToken cancelToken)
   --- End of inner exception stack trace ---
   at Discord.ConnectionManager.WaitAsync()
   at Discord.WebSocket.DiscordSocketClient.OnConnectingAsync()
   at Discord.WebSocket.DiscordSocketClient.OnConnectingAsync()
   at Discord.ConnectionManager.ConnectAsync(CancellationTokenSource reconnectCancelToken)
   at Discord.ConnectionManager.<>c__DisplayClass28_0.<<StartAsync>b__0>d.MoveNext()
   --- End of inner exception stack trace ---
---> (Inner Exception #0) System.Exception: WebSocket connection was closed ---> System.MissingMethodException: Method not found: 'System.Threading.Tasks.Task`1<Discord.Audio.IAudioClient> Discord.IAudioChannel.ConnectAsync(System.Action`1<Discord.Audio.IAudioClient>)'.
   at Discord.WebSocket.DiscordSocketClient.ProcessMessageAsync(GatewayOpCode opCode, Nullable`1 seq, String type, Object payload)
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
   at Discord.WebSocket.DiscordSocketClient.ProcessMessageAsync(GatewayOpCode opCode, Nullable`1 seq, String type, Object payload)
   at Discord.EventExtensions.InvokeAsync[T1,T2,T3,T4](AsyncEvent`1 eventHandler, T1 arg1, T2 arg2, T3 arg3, T4 arg4)
   at Discord.API.DiscordSocketApiClient.<.ctor>b__24_0(Byte[] data, Int32 index, Int32 count)
   at Discord.Net.WebSockets.DefaultWebSocketClient.RunAsync(CancellationToken cancelToken)
   --- End of inner exception stack trace ---
   at Discord.ConnectionManager.WaitAsync()
   at Discord.WebSocket.DiscordSocketClient.OnConnectingAsync()
   at Discord.WebSocket.DiscordSocketClient.OnConnectingAsync()
   at Discord.ConnectionManager.ConnectAsync(CancellationTokenSource reconnectCancelToken)
   at Discord.ConnectionManager.<>c__DisplayClass28_0.<<StartAsync>b__0>d.MoveNext()<---

This is all I can provide.

Looks like you didn't update properly, we removed the overload for ConnectAsync which takes an action.

Just updating the myget version should work yes?

It should do.

Just performed restore and same exception.

Do you have anything listening to UserVoiceStateUpdated/VoiceServerUpdated event?

UserVoiceStateUpdated for Music Auto-Join functionality. Does not execute unless a user is detected going into a voice channel.

What's the code? You're calling an overload which should not exist, so maybe you should try recompiling your code.

        private async Task UserVoiceUpdatedAsync(SocketUser sUser, SocketVoiceState before, SocketVoiceState after) {
            if (sUser.IsBot || sUser.IsWebhook) return;

            IGuildUser user = (IGuildUser)sUser;
            IGuild guild = user.Guild;

            if (playerManager.IsCreated(guild.Id) || user.VoiceChannel == null)
                return;

            GD_Music gMusic = await vgMusic.GetAsync(guild.Id);

            if (gMusic == null) return;

            IVoiceChannel vc = user.VoiceChannel;
            ITextChannel tc = (gMusic.AutoTextChannel != 0) ? await guild.GetTextChannelAsync(gMusic.AutoTextChannel) : null;

            if (vc.Id == gMusic.AutoVoiceChannel && tc != null)
                await playerManager.CreatePlayerAsync(user, vc, tc, true);
        }

And the source for CreatePlayerAsync? I'm guessing somewhere you're calling ConnectAsync() and didn't make sure it was compiled against the latest version so it ended up calling an overload which no longer exists.

        private async Task ConnectToVoiceAsync()
            => client = await VoiceChannel.ConnectAsync();

This is the only connectasync line.

Yeah, recompile your code and it should work.

That's a no-go. Performed dotnet clean & dotnet build and same issue.

Try deleting your project.assets.json (it's in the obj folder for the project) and re-restore, and rebuild. It appears like it's running against the latest version, while it compiles against an older version.

In the most extreme case, you may want to do the follwing: While VS is closed, delete the project's bin and obj entirely, then go to Users\%USERNAME%\.nuget and delete (some/all) of the Discord.Net packages you have there.

Followed both cases and both failed. However, I did notice that upon restoring after deleting all data from .nuget, it begun downloading 00957. Only the WS4Net downloaded as 00969.

My apologies, I figured it out. I've done a Herper McDerpington. Turned out the csproj file didn't have the right build number.
Closing due to no longer a problem.


Upgrade to actions/upload-artifact@v4

Description
Upgrade to actions/upload-artifact@v4
Modeled after https://github.com/opensearch-project/job-scheduler/pull/702
Related Issues
Resolves https://github.com/opensearch-project/index-management/issues/1304
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] API changes companion pull request created.
[ ] Commits are signed per the DCO using --signoff.
[ ] Public documentation issue/PR created.

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

@Hailong-am Sorry I meant to close this PR. This change is included on https://github.com/opensearch-project/index-management/pull/1311 and that PR will fix all CI checks.


Scripts for PancakeSwap pool deployment

Similar to uniswap scripts, the folder scripts/pancakeswap has the required scripts to deploy bSOV token, multisig contract and a Binance bSOV pool through the PancakeRouter2 contract. Scripts has been tested on binance-testnet.

Pool deployment w/ multisig:
$ brownie run scripts/pancakeswap/deploy_pool.py --network binance-testnet
Brownie v1.12.4 - Python development framework for Ethereum
SovrynSmartContractsProject is the active project.
Running 'scripts/pancakeswap/deploy_pool.py::main'...
Enter the password to unlock this account:
Transaction sent: 0xc2720991d332469fe0af1c8fd0724d981bf05c7690010ea8f8f2ab19acd0da78
Gas price: 20.0 gwei   Gas limit: 6800000   Nonce: 13
Transaction confirmed - Block: 9521592   Gas used: 22501 (0.33%)
=============================================================
Interaction Parameters (Token Transfer)
Receiver:                 0xae866B73dF2406487288A7E51a0cB23C9C5dc549
bSOV Amount:<PHONE_NUMBER>0.0
Transaction sent: 0x1d340512f75d4b7985ea0adb784602ecf9a45fe310aa374d8fea43ff97d92785
Gas price: 20.0 gwei   Gas limit: 6800000   Nonce: 14
SOV.transfer confirmed - Block: 9521594   Gas used: 51082 (0.75%)
Transaction was Mined
Tx Hash: 0x1d340512f75d4b7985ea0adb784602ecf9a45fe310aa374d8fea43ff97d92785
From: 0x10a1d67dCeF9Fd6095E1A918578D6f996fA5E376
To: 0xDC709C7880cd2034651855D4E21C8413b99aa7A8
Value: 0
Function: SOV.transfer
Block: 9521594
Gas Used: 51082 / 6800000 (0.8%)
Events In This Transaction
└── Sovryn Token (0xDC709C7880cd2034651855D4E21C8413b99aa7A8)
└── Transfer
├── from: 0x10a1d67dCeF9Fd6095E1A918578D6f996fA5E376
├── to: 0xae866B73dF2406487288A7E51a0cB23C9C5dc549
└── value:<PHONE_NUMBER>0
=============================================================
Interaction Parameters (Token Transfer Approval)
Spender Address:              0xD99D1c33F9fC3444f8101754aBC46c52416550D1
Amount approved:<PHONE_NUMBER>0.0
Encoded Data:                 0x095ea7b3000000000000000000000000d99d1c33f9fc3444f8101754abc46c52416550d10000000000000000000000000000000000000000000000000000000ba43b7400
Transaction sent: 0x18aba5b8cc9de4d3237e89f41a8ef44c97878f2f809e9d4d17b1a200a3952a8f
Gas price: 20.0 gwei   Gas limit: 6800000   Nonce: 15
MultiSigWallet.submitTransaction confirmed - Block: 9521597   Gas used: 234241 (3.44%)
=============================================================
Return Parameters (Multisig Submission)
Transaction ID:           0
Transaction was Mined
Tx Hash: 0x18aba5b8cc9de4d3237e89f41a8ef44c97878f2f809e9d4d17b1a200a3952a8f
From: 0x10a1d67dCeF9Fd6095E1A918578D6f996fA5E376
To: 0xae866B73dF2406487288A7E51a0cB23C9C5dc549
Value: 0
Function: MultiSigWallet.submitTransaction
Block: 9521597
Gas Used: 234241 / 6800000 (3.4%)
Events In This Transaction
├── MultiSigWallet (0xae866B73dF2406487288A7E51a0cB23C9C5dc549)
│   ├── Submission
│   │   └── transactionId: 0
│   └── Confirmation
│       ├── sender: 0x10a1d67dCeF9Fd6095E1A918578D6f996fA5E376
│       └── transactionId: 0
│
├── Sovryn Token (0xDC709C7880cd2034651855D4E21C8413b99aa7A8)
│   └── Approval
│       ├── owner: 0xae866B73dF2406487288A7E51a0cB23C9C5dc549
│       ├── spender: 0xD99D1c33F9fC3444f8101754aBC46c52416550D1
│       └── value:<PHONE_NUMBER>0
│
└── MultiSigWallet (0xae866B73dF2406487288A7E51a0cB23C9C5dc549)
└── Execution
└── transactionId: 0
=============================================================
Interaction Parameters (Pool Creation)
bSOV Token:                   0xDC709C7880cd2034651855D4E21C8413b99aa7A8
amountTokenDesired:<PHONE_NUMBER>0.0
amountTokenMin:<PHONE_NUMBER>0.0
amountBNBMin:<PHONE_NUMBER>.0
to:                           0xae866B73dF2406487288A7E51a0cB23C9C5dc549
deadline:<PHONE_NUMBER>
Encoded Data:                 0xf305d719000000000000000000000000dc709c7880cd2034651855d4e21c8413b99aa7a80000000000000000000000000000000000000000000000000000000ba43b74000000000000000000000000000000000000000000000000000000000ba43b7400000000000000000000000000000000000000000000000000000000003b9aca00000000000000000000000000ae866b73df2406487288a7e51a0cb23c9c5dc5490000000000000000000000000000000000000000000000000000000060bdfd2d
Current Timestamp:<PHONE_NUMBER>
Transaction sent: 0x496fd2b1dd66a04bba056887246510b4f99c7ef6c5443ea9e88a186ea90313e0
Gas price: 20.0 gwei   Gas limit: 6800000   Nonce: 16
MultiSigWallet.submitTransaction confirmed - Block: 9521599   Gas used: 455759 (6.70%)
=============================================================
Return Parameters (Multisig Submission)
Transaction ID:           1
Transaction was Mined
Tx Hash: 0x496fd2b1dd66a04bba056887246510b4f99c7ef6c5443ea9e88a186ea90313e0
From: 0x10a1d67dCeF9Fd6095E1A918578D6f996fA5E376
To: 0xae866B73dF2406487288A7E51a0cB23C9C5dc549
Value: 0
Function: MultiSigWallet.submitTransaction
Block: 9521599
Gas Used: 455759 / 6800000 (6.7%)
Events In This Transaction
├── MultiSigWallet (0xae866B73dF2406487288A7E51a0cB23C9C5dc549)
│   ├── Submission
│   │   └── transactionId: 1
│   └── Confirmation
│       ├── sender: 0x10a1d67dCeF9Fd6095E1A918578D6f996fA5E376
│       └── transactionId: 1
│
├── Sovryn Token (0xDC709C7880cd2034651855D4E21C8413b99aa7A8)
│   ├── Transfer
│   │   ├── from: 0xae866B73dF2406487288A7E51a0cB23C9C5dc549
│   │   ├── to: 0x0A206481DB6B64Ba8227492a7BC697a329478599
│   │   └── value:<PHONE_NUMBER>0
│   └── Approval
│       ├── owner: 0xae866B73dF2406487288A7E51a0cB23C9C5dc549
│       ├── spender: 0xD99D1c33F9fC3444f8101754aBC46c52416550D1
│       └── value: 0
│
├── 0xae13d989daC2f0dEbFf460aC112a837C89BAa7cd
│   ├── Deposit
│   │   ├── sender: 0xD99D1c33F9fC3444f8101754aBC46c52416550D1
│   │   └── value:<PHONE_NUMBER>
│   └── Transfer
│       ├── from: 0xD99D1c33F9fC3444f8101754aBC46c52416550D1
│       ├── to: 0x0A206481DB6B64Ba8227492a7BC697a329478599
│       └── value:<PHONE_NUMBER>
│
├── 0x0A206481DB6B64Ba8227492a7BC697a329478599
│   ├── Transfer
│   │   ├── from: 0x0000000000000000000000000000000000000000
│   │   ├── to: 0xae866B73dF2406487288A7E51a0cB23C9C5dc549
│   │   └── value:<PHONE_NUMBER>
│   ├── (unknown)
│   │   ├── topic1: 0x1c411e9a96e071241c2f21f7726b17ae89e3cab4c78be50e062b03a9fffbbad1
│   │   └── data: 0x000000000000000000000000000000000000000000000000016345789924ca000000000000000000000000000000000000000000000000004563918de92f7400
│   └── (unknown)
│       ├── topic1: 0x4c209b5fc8ad50758f13e2e1088ba56a560dff690a1c6fef26394f4c03821c4f
│       ├── topic2: 0x000000000000000000000000d99d1c33f9fc3444f8101754abc46c52416550d1
│       └── data: 0x000000000000000000000000000000000000000000000000000000003b9aca000000000000000000000000000000000000000000000000000000000ba43b7400
│
└── MultiSigWallet (0xae866B73dF2406487288A7E51a0cB23C9C5dc549)
└── Execution
└── transactionId: 1
=============================================================
BNB Before Balance:<PHONE_NUMBER>00000000
BNB After Balance:<PHONE_NUMBER>00000000
Gas Used:<PHONE_NUMBER>0000000


Not Loading on Windows or Linux?

Hi! Very excited about this plugin!
I can't seem to get it to load on my graphs though- here's the error in the console

I just cloned the repo and then unpacked it. Am I missing something?
Thanks!

You have to download the GitHub release, not clone the pro. It should also be up in the marketplace soon so that you can install from there.
On 29 Mar 2022, 1:12 AM +0400, bezark @.***>, wrote:

Hi! Very excited about this plugin!
I can't seem to get it to load on my graphs though- here's the error in the console
I just cloned the repo and then unpacked it. Am I missing something?
Thanks!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

oh duh.
thanks!


Fatal Exception when trying to view a Unicode string in the Watch window

[Window Title]
Fatal Exception

[Content]
A fatal exception (code 0xc0000005) occurred. The process is terminating.

Press Ctrl+C to copy this text to clipboard, then create a new issue in
https://github.com/EpicGames/raddebugger/issues

Call stack:
1. [0x7ff7983633a7] df_symbol_name_from_binary_voff +471, df_core.c line 3215
2. [0x7ff798363502] df_symbol_name_from_process_vaddr +146, df_core.c line 3232
3. [0x7ff798360632] df_single_line_eval_value_strings_from_eval +1538, df_gfx.c line 6936
4. [0x7ff798347e49] df_eval_viz_windowed_row_list_from_viz_block_list +1513, df_gfx.c line 7290
5. [0x7ff79834c8e5] df_eval_watch_view_build +9109, df_views.c line 1163
6. [0x7ff7982e553c] df_view_ui_Watch +140, df_views.c line 6747
7. [0x7ff79838e71c] df_window_update_and_render +152060, df_gfx.c line 5744
8. [0x7ff7983f46b4] update_and_render +4708, raddbg.c line 282
9. [0x7ff798399e76] entry_point +5830, raddbg.c line 552
10. [0x7ff7983f6cf2] WinMain +930, raddbg_main.cpp line 347
11. [0x7ff7983fec4e] __scrt_common_main_seh +262, exe_common.inl line 288
12. [0x7ffb9f45257d] KERNEL32
13. [0x7ffba11aaa58] ntdll

Version: 0.9.8 [7c9f127]

[Close]

I believe the following should reproduce it:

Use the following C source file

#include <stdlib.h>
#include <string.h>
#include <locale.h>

int main()
{
	char *s6 = "Ｕｎｉｃｏｄｅ! 🅤🅝🅘🅒🅞🅓🅔‽ 🇺🇳🇮🇨🇴🇩🇪! 😄 The very name strikes fear and awe into the hearts of programmers worldwide. We all know we ought to “support Unicode” in our software (whatever that means—like using wchar_t for all the strings, right?). But Unicode can be abstruse, and diving into the thousand-page [Unicode Standard](http://www.unicode.org/versions/latest/) plus its dozens of supplementary [annexes, reports](http://www.unicode.org/reports/), and [notes](http://www.unicode.org/notes/) can be more than a little intimidating. I don’t blame programmers for still finding the whole thing mysterious, even 30 years after Unicode’s inception.";

    printf("%s\n", s6);

	return 0;
}

Try to watch s6 in the Watch window

Should be fixed as of 642acdf4745e796c191cf0e0c1babaa7fb6baa17.


test: Automatically clean default workspace before each test

Fix #153
This PR introduces a test listener that automatically cleans up the default workspace before each test. It is therefore now safe to use the default workspace for all tests, and all tests that previously interfered with each other now don't.
The listener in question is located in src/test/sorald/WorkspaceCleaner.java, and is registered as a test service in src/test/resources/META-INF/services/org.junit.platform.launcher.TestExecutionListener.

Thanks @slarse!


enhance: remove ssr warnings

Close: https://github.com/arco-design/arco-design/issues/199

Avatar component SSR not work:
react_devtools_backend.js:4026 Warning: Prop style did not match. Server: "null" Client: "font-size:"


add dimension method for Indicator

guess who forgot to add a method definition for IndicatorSet

Is this needed for JuMP?
The MOI tests worked fine without it.

yes it seems not to be tested / enforced but is in the MOI interface for sets


Fix small screen filters panel opening

The filter panel in the IDE is not opening up because the hook is being called after the if block.
Test plan
Test opening filters in idea.

Changelog

@thenamankumar can you please update cody web version here (web/package.json) and add an entry in the CHANGELOG.md (web/CHANGELOG.md), once this merged I will update Cody Web version again.
But note that this fix will be included only in the next 5.11 patch release


Fix silences negative filtering

We changed the alerting filtering logic to be consistent with prometheus https://github.com/prometheus/alertmanager/issues/1060.
This PR makes the same change to the silence filtering, and extract the filtering logic which is equal no matter if an alert, or silence. This way is easier for a new change to be effective cross alertmanager, without having to change two different places.

fix the merge conflicts and it's good to go

@stuartnelson3 Done. I've rebased the master commits. Thanks.


Unable to resolve file system provider with relative file path

when i try to create a new scratch i got this error message:
 (traduction: Unable to resolve file system provider with relative file path)
I tryed to debug it without succes, i change the "/" at  getWorkspaceScratchPath() by a "\" but nothing change... help me

one without any modification:


⚠ ETF has degraded performance

In 070cbd7, ETF (https://markets.hankyung.com/equity-product/etf) experienced degraded performance:

HTTP code: 200
Response time: 6463 ms

Resolved: 한경주요지수-코스피 performance has improved in 9f5d902.


snp_defs: add missing fields for SevFeatures

Add several missing bits for SevFeatures:

bit 8: VMPL Supervisor Shadow Stack (VmplSSS).
bit 9: Secure TSC (SecureTscEn).
bit 14: VMSA Register Protection (VmsaRegProt).
bit 15: SMT Protection (SmtProtection).

other than the small nit, change looks fine to me! Thanks for your contribution!

@microsoft-github-policy-service agree [company="SUSE"]

@microsoft-github-policy-service agree company="SUSE"

@chris-oo updated with your suggestion

Thanks! I've gone ahead and enabled automerge. Do you need a release on crates.io with this change?

Thanks! I've gone ahead and enabled automerge. Do you need a release on crates.io with this change?

I think at some point we will want this but it's not urgent, so I'd say not for now.


do you plan to allow multi language support or the layout?

Hello
do you plan to provide multi language support for the layout , and also for the RTL (Right to left) languages.
can I help with that?

I may not understand you correctly, but project is already multi-language. Language is taken from your browser regional settings (maybe this will change in the future, if users prefer to be able to select the language manually too)
You can find translations here: https://github.com/manusa/isotope-mail/tree/master/client/assets/locales
I personally maintain English and Spanish. PR for other languages or outdated language files are welcome ;)
Regarding RTL support, not planned yet, as some parts of the MVP are missing. But will be considered for sure in future releases.

Hello @manusa , I will work on Arabic translation.
and it is adviced to support RTL. for Arabic ,Persian and Hebrew language.
Also it is good to allow user to manually change the layout language.


Why the software history was not kept?

Hi there,
I'm a researcher studying software evolution. As part of my current research, I'm studying the implications of open-sourcing a proprietary software, for instance, if the project succeed in attracting newcomers. However, I observed that some projects, like ChakraCore, deleted their software history when transitioning to open-source.
https://github.com/Microsoft/ChakraCore/commit/5d8406741f8c60e7bf0a06e4fb71a5cf7a6458dc
Knowing that software history is indispensable for developers (e.g., developers need to refer to history several times a day), I would like to ask ChakraCore developers the following four brief questions:

Why did you decide to not keep the software history?
Do the core developers faced any kind of problems, when trying to refer to the old history? If so, how did they solve these problems?
Do the newcomers faced any kind of problems, when trying to refer to the old history? If so, how did they solve these problems?
How does the lack of history impacted on software evolution? Does it placed any burden in understanding and evolving the software?

Thanks in advance for your collaboration,
Gustavo Pinto, PhD
http://www.gustavopinto.org

Hi Gustavo,
Interesting research you’re doing! Hopefully the following will help you.

Why did you decide to not keep the software history?
The ChakraCore history could not be easily brought from the proprietary source control system in which the sources resided for almost all of their existence. We moved to Git a couple of months before opening up the repo. During that time, we did extensive cleanup of the sources to make them ready to share. We cleaned out embarrassing or inappropriate comments, brought the code up to Microsoft OSS standards, and generally improved code hygiene, robustness, and security. We removed that bit of history because the point of those changes were to remove things that we explicitly didn’t want to share.
Do the core developers faced any kind of problems, when trying to refer to the old history? If so, how did they solve these problems?
The bulk of the history of the sources is still available to the project owners, and we do indeed use that history in some circumstances, such as performing root cause analysis of bugs.
Do the newcomers faced any kind of problems, when trying to refer to the old history? If so, how did they solve these problems?
This has not been a problem that newcomers have raised.
How does the lack of history impacted on software evolution? Does it placed any burden in understanding and evolving the software?
As I mentioned, when performing RCA on issues of interest, like security issues, having the history helps us look for other places in which we may have introduced bugs at the time the root issue was introduced. We don’t have other sources of documentation that may compensate for lack of history. Not having history would most definitely be limiting and reduce our understanding of why the code looks the way it does today.

Ed

Closing question as answered, but feel free to comment if you'd like to discuss further.

Hi @dilijev and @EdMaurer,
thanks once again for answering our research inquiries. We were able to collect 35 responses and we drafted a research paper with the results. The paper was submitted and accepted for the 14th International Conference on Open Source Systems (http://oss2018.org/). You can find the paper here. Hope you enjoy reading the paper!
Thanks again,
Gustavo


Fixed a couple of bugs with Sliced paths

See issue for explanations https://github.com/arl/go-detour/issues/24#issuecomment-575602717

I updated the master branch with a new travis-ci configuration which should be exempt of false positives.
Can you update or rebase your PR over the new master please?
I'm sure the build will pass and then I'll merge.
Sorry for the delay on that

@CodeSpartan There seems to be some compilations errors: https://travis-ci.com/github/arl/go-detour/builds/160831821

Don't have go right now, switched to another project a long time ago. Trying to fix errors blindly, relying on travis...

Pull Request Test Coverage Report for Build 265

2 of 19 (10.53%)  changed or added relevant lines in 1 file are covered.
144 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-2.6%) to 61.437%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

detour/query.go
2
19
10.53%

Files with Coverage Reduction
New Missed Lines
%

detour/query.go
3
48.11%

detour/polyquery.go
4
65.0%

detour/status.go
4
18.18%

detour/navmeshcreate.go
31
64.68%

detour/mesh.go
102
66.12%

Totals

Change from base Build 248:
-2.6%

Covered Lines:
2420

Relevant Lines:
3939

💛  - Coveralls

All good? I'm not sure what this coveralls thingy is, but doesn't look like a real issue.

That's great. thanks. dont worry about coveralls


[CF] New: Add default bitsandvolts vs code profile

Let me know if you have extensions that you want to be part of our default profile.


Added an exception catch and another get/set RAPID symbol data method

Added catching of the POCO InvalidArgumentException
Added another get/set RAPID symbol data method (mainly for convenience)

@gavanderhoorn I have fixed some typos, and clarified a few comments. But there are more cleaning up to do in future PRs :)

Could you open some issues on the tracker for the things we'd like to do in future PRs?
Like passing std::string args by-ref, etc?

@jontje?

Sorry for the slow reply, I had to prioritize a few other tasks. And yes, I will open some issues.

Thanks for logging the issues @jontje :+1:


Custom HumanoidAppearanceSystem for Thanatophobia

About the PR

Modified markings and the humanoid appearance system to use the body parts on the player for the humanoid sprites.
This also adds support for markings with two completely seperate layers (for example, you can have one "head" layer and another "hand" layer for one marking). This is especially useful for having two sided markings, which I will show in some images in a bit.
Why / Balance

I disliked upstream's version of this for a while, so I really wanted to make my own.
Also should make certain traits work better.
Technical details

Media

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

BEFORE:

AFTER:

Notice how the tail doesn't go over the shoes here.
Additionally, it doesn't affect the back.

Breaking changes

Changelog

I'm almost finished with this :D
I may be able to finish this tomorrow, and if not, I can do it over the weekend.

I'm almost finished with this :D I may be able to finish this tomorrow, and if not, I can do it over the weekend.

I did not finish it over the weekend.

Okay I think this is done now. Gonna have to wait for tests to finish tho.


I think we should add version information to the interface.

I think we should add version information to the interface.
Otherwise it may forget the current version, and whether you need to upgrade.

Also, whether the site title can be customized, for example: DOUBI - Files, DOUBI - Profile Settings, DOUBI - Video.
Some interesting little details suggestion ~

Thanks for the suggestions! I'll probably do them 😄


rerender feedstock

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged) First render failed. NA
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [47]

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


feat(redash): add ability to filter redash metadata by database

Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[x] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@DantasB thanks, now there are a few mypy validation error ->
https://github.com/datahub-project/datahub/runs/5984956469?check_suite_focus=true#step:6:1126
src/datahub/ingestion/source/redash.py:503: error: Argument 1 to "_get_database_name_based_on_datasource" of "RedashSource" has incompatible type "Optional[Any]"; expected "Dict[Any, Any]"
src/datahub/ingestion/source/redash.py:552: error: Argument 1 to "allowed" of "AllowDenyPattern" has incompatible type "Optional[str]"; expected "str"
src/datahub/ingestion/source/redash.py:674: error: Argument 1 to "allowed" of "AllowDenyPattern" has incompatible type "Optional[str]"; expected "str"

Please, can you fix those as well?

@DantasB hey, let me know if you need help resolving these mypy issues:
src/datahub/ingestion/source/redash.py:551: error: Argument 1 to "allowed" of "AllowDenyPattern" has incompatible type "Optional[str]"; expected "str"
src/datahub/ingestion/source/redash.py:673: error: Argument 1 to "allowed" of "AllowDenyPattern" has incompatible type "Optional[str]"; expected "str"

Hey @treff7es sorry for taking too long to fix this linter, it's just because the college activities return back recently so it's beeing quite hard to handle a lot of things hahaha! I'll try to fix that today, if it's beeing to hard i'll ask you for help, ok?
Thanks!

@treff7es now i think that mypy will not fail again.

We are closing the PR due to dormancy.
We've not heard this feature request for the Redash source since this was opened.
Thanks for the awesome contribution @DantasB! Please reach out if you'd like to start up this thread again, and we'll work with you to figure it out.
Cheers
John


feat: implement loan deletion functionality

Add DELETE /api/loans/{id} endpoint
Add comprehensive test coverage for deletion:

Successful loan deletion
Non-existent loan handling

Update API routes with delete endpoint

Test Coverage:

Verify successful deletion from database
Validate proper 404 handling for non-existent loans

Verified.


Japanese translations for 3.1/usingthymeleaf.md and thymeleaf31whatsnew.md

I'm one of the Japanese translators of "Using Thymeleaf (ja)" for Thymeleaf 3.0.
I'd like to contribute again to the Japanese translation of Thymeleaf 3.1 documents.
I'm translating 3.1/usingthymeleaf.md and thymeleaf31whatsnew.md and @bufferings is reviewing them.
(repository -> https://github.com/thymeleaf-docs-ja/thymeleaf-docs/tree/docs-ja-develop )
I'd like you to publish 3.1/usingthymeleaf_ja.md in thymeleaf.org as same as 3.0 after finishing the translation.
But, how about thymeleaf31whatsnew_ja.md? Can you publish it in thymeleaf.org as same as usingthymeleaf_ja.md?
If you cannot, can I publish it in my own blog?
Japanese translation of this migration guide will be very helpful for Japanese developers.
Please give it some consideration.

Hi there, sorry for taking so long to get back to you, but yes we would be happy to host a Japanese translation of both of these documents on thymeleaf.org
Feel free to submit a pull request with the translation when you're ready, and I can merge that then generate all the necessary HTML files to add to the Thymeleaf website 😊

Thank you so much!
We'll send a PR after finishing translation😃

Sorry for being late! We finally finished the translation and sent a PR.
Please take a look😃


Poco:x64-windows-dbg Build Failed

git Hash: 6a5056773a938daa1195698839074a8b57bb0b80
CMake Error at scripts/cmake/vcpkg_build_cmake.cmake:175 (message):
Command failed: E:/vcpkg/downloads/tools/cmake-3.12.4-windows/cmake-3.12.4-win32-x86/bin/cmake.exe;--build;.;--config;Debug;--target;install;--;-v;-j1
Working Directory: E:/vcpkg/buildtrees/poco/x64-windows-dbg
See logs for more information:
E:\vcpkg\buildtrees\poco\install-x64-windows-dbg-out.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_install_cmake.cmake:24 (vcpkg_build_cmake)
ports/poco/portfile.cmake:42 (vcpkg_install_cmake)
scripts/ports.cmake:71 (include)
Error: Building package poco:x64-windows failed with: BUILD_FAILED

it's fixed after install opesnssl


Programmatically reset ix-date-picker selection

Prerequisites

[x] I have read the Contributing Guidelines.
[X] I have not leaked any internal/restricted information like screenshots, videos, code snippets, links etc.

Suggestion / feature request
Add ability to reset date selections on ix-date-picker programmatically
For instance if user selected 23rd of March previously and when we need to reset form inputs programmatically, we need to reset date picker to default version as well(without having previous date as marked - 23rd of March in this case)

Thanks for your input! Currently you can reset the date if you set 'from' to null or ''. I have prepared a small example here:
https://stackblitz.com/edit/s92ja4?file=src%2Fdatepicker-range.tsx - If you have any further questions, don't hesitate to ask.

got it, thanks for code 👍


Build "new" modal

On launch, we'll need a "this is a new site" modal that tells people that this is new and asks them to sign up for our email list (google docs form).

Leaflet conditional modal
Session storage

First: don’t show the modal if there’s an existing session and it’s been less than 24 hours since the session started; else show the modal:
if (sessionStorage) {
  var session = sessionStorage.getItem(SESSION_KEY);
  // open the dialog only every 24 hours
  if (session && Date.now() - session < ONE_DAY_MILLI_SEC) {
    return; // stops eval
  }
}

Second: Set a session storage value with the current date and time, and some key:
if (sessionStorage) {

  sessionStorage.setItem(SESSION_KEY, Date.now());

}

So we just wrap the modal code in a function like here, then call it on every page (maybe by adding to head.html or baseof.html?), and we should be set.

attn @mmontesanonyc
Not working correctly on pages that are not the home page. The page is darkening, but the dialog isn't popping up. But, it works as intended on the home page.

Thanks for getting this started! I tweaked the modal text.
What's the best way to test this given the session storage thing - just change that to a small value for testing?
Strange that it doesn't work on other pages from baseof. I tried sticking it into the js_bottom partial to see if that would work either but it doesn't.

Another thing to think about for the modal is to wrap it in a Hugo environment variable, so that it builds one way for dev ("This is our staging site, click here for production.") and another way for production ("Welcome to our new site, sign up for our email list.")

@mmontesanonyc It works! And it tells you in the console why it's showing or hiding the modal. Solution ended up just using the previous modal, with some bootstrap-modal-specific JavaScript.

Awesome! wtg. I'm going to tweak styles a tiny bit.

re: environment variables, we could just wrap conditional-modal.html in an environment variable (like this) to create environment-specific modals. No need to do that now but it's probably something we should do in the coming month or so.

This is all set, right? All in here?

Yep, all there. Not sure I've merged the changes into main / prod.

Yep, all there. Not sure I've merged the changes into main / prod.

That's fine. We don't really need to 'assemble' main/prod at this point. When we get closer to launch, we can, but for now we can basically ignore it while we finalize using development.

I want to enable closing the modal on esc or enter

This is the modal from the older version - esc closes it. I think I had pulled this specifically from a source on accessible modals. The different is (just, I think) that button in modal-header with the data-dismiss="modal" attribute.

This is a prototype.

  <button type="button" class="close" data-dismiss="modal" aria-label="Close">
  ×
  </button>

Welcome to the new Environment & Health Data Portal. This prototype is a work in progress. That means that not all of the information, data, or content is final.

But, feel free to click around and explore.

  <button type="button" class="btn btn-secondary" data-dismiss="modal">Close</button>

Turns out it already works on esc. Maybe I had dev tools open. It would be nice for it to work on enter, but that's not really important. Closing this again.


Frontend and Backend markdown processing results in different rendering

When sending a message with the following example markdown text, the frontend engine will display the links as expected but once the message is processed by the backend and sent to the front end the markdown appears to not work as expected.

@aero31aero want to investigate this one?

@zulipbot claim

@zulipbot abandon
I got lost in a lot of assignments and end sem exams, so had to stop work. What I found so far, in case someone else picks it up before I am free again:

Our custom links processor overrides the python-markdown(py-md)'s so we lose the reference based syntax completely.
Somewhere in its codepath, py-md generates a list of references as a name, link pair and that is used by the link processor to search for and replace the regex based matches into actual HTML.
The simplest fix is to read the py-md code and duplicate some parts of it into our links processor code.

Relevant code in py-md:

class ReferenceInlineProcessor(LinkInlineProcessor): in https://github.com/Python-Markdown/markdown/blob/master/markdown/inlinepatterns.py

class ReferencePreprocessor(Preprocessor): in https://github.com/Python-Markdown/markdown/blob/master/markdown/preprocessors.py

@zulipbot claim I guess Rohit is travelling so taking this issue


Outdated Korean contents in dev-1.22-ko.2 branch

This is a Bug Report
Problem
Outdated files in the upstream/dev-1.22-ko.2 branch.
Report generated by the following command.
scripts/diff_l10n_branches.py ko upstream/dev-1.22-ko.1 upstream/dev-1.22-ko.2
71 files to be modified

[ ] M1.  content/en/blog/_posts/2021-08-04-kubernetes-release-1.22.md  | 1(+XS) 1(-)
[ ] M2.  content/en/docs/concepts/architecture/nodes.md  | 76(+M) 46(-)
[ ] M3.  content/en/docs/concepts/cluster-administration/logging.md  | 1(+XS) 1(-)
[ ] M4.  content/en/docs/concepts/cluster-administration/manage-deployment.md  | 1(+XS) 1(-)
[ ] M5.  content/en/docs/concepts/cluster-administration/networking.md  | 1(+XS) 22(-)
[ ] M6.  content/en/docs/concepts/configuration/configmap.md  | 5(+XS) 0(-)
[ ] M7.  content/en/docs/concepts/configuration/manage-resources-containers.md  | 12(+S) 2(-)
[ ] M8.  content/en/docs/concepts/configuration/overview.md  | 2(+XS) 28(-)
[ ] M9.  content/en/docs/concepts/configuration/secret.md  | 24(+S) 13(-)
[ ] M10.  content/en/docs/concepts/containers/container-environment.md  | 1(+XS) 1(-)
[ ] M11.  content/en/docs/concepts/containers/images.md  | 73(+M) 15(-)
[ ] M12.  content/en/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation.md  | 4(+XS) 4(-)
[ ] M13.  content/en/docs/concepts/extend-kubernetes/api-extension/custom-resources.md  | 6(+XS) 6(-)
[ ] M14.  content/en/docs/concepts/extend-kubernetes/operator.md  | 1(+XS) 0(-)
[ ] M15.  content/en/docs/concepts/extend-kubernetes/service-catalog.md  | 1(+XS) 1(-)
[ ] M16.  content/en/docs/concepts/overview/components.md  | 1(+XS) 1(-)
[ ] M17.  content/en/docs/concepts/overview/working-with-objects/kubernetes-objects.md  | 4(+XS) 5(-)
[ ] M18.  content/en/docs/concepts/overview/working-with-objects/namespaces.md  | 4(+XS) 1(-)
[ ] M19.  content/en/docs/concepts/scheduling-eviction/kube-scheduler.md  | 1(+XS) 1(-)
[ ] M20.  content/en/docs/concepts/scheduling-eviction/resource-bin-packing.md  | 20(+S) 20(-)
[ ] M21.  content/en/docs/concepts/security/controlling-access.md  | 1(+XS) 1(-)
[ ] M22.  content/en/docs/concepts/security/overview.md  | 1(+XS) 0(-)
[ ] M23.  content/en/docs/concepts/services-networking/connect-applications-service.md  | 3(+XS) 3(-)
[ ] M24.  content/en/docs/concepts/services-networking/dns-pod-service.md  | 2(+XS) 2(-)
[ ] M25.  content/en/docs/concepts/services-networking/network-policies.md  | 2(+XS) 1(-)
[ ] M26.  content/en/docs/concepts/services-networking/service.md  | 27(+S) 5(-)
[ ] M27.  content/en/docs/concepts/storage/persistent-volumes.md  | 26(+S) 14(-)
[ ] M28.  content/en/docs/concepts/storage/volumes.md  | 11(+S) 11(-)
[ ] M29.  content/en/docs/concepts/workloads/controllers/cron-jobs.md  | 25(+S) 17(-)
[ ] M30.  content/en/docs/concepts/workloads/controllers/daemonset.md  | 16(+S) 1(-)
[ ] M31.  content/en/docs/concepts/workloads/controllers/deployment.md  | 16(+S) 14(-)
[ ] M32.  content/en/docs/concepts/workloads/controllers/job.md  | 22(+S) 5(-)
[ ] M33.  content/en/docs/concepts/workloads/controllers/replicaset.md  | 11(+S) 0(-)
[ ] M34.  content/en/docs/concepts/workloads/controllers/replicationcontroller.md  | 8(+XS) 3(-)
[ ] M35.  content/en/docs/concepts/workloads/controllers/statefulset.md  | 16(+S) 8(-)
[ ] M36.  content/en/docs/concepts/workloads/pods/_index.md  | 9(+XS) 2(-)
[ ] M37.  content/en/docs/concepts/workloads/pods/init-containers.md  | 10(+S) 6(-)
[ ] M38.  content/en/docs/concepts/workloads/pods/pod-topology-spread-constraints.md  | 17(+S) 13(-)
[ ] M39.  content/en/docs/contribute/new-content/_index.md  | 60(+M) 0(-)
[ ] M40.  content/en/docs/home/_index.md  | 2(+XS) 2(-)
[ ] M41.  content/en/docs/reference/_index.md  | 2(+XS) 0(-)
[ ] M42.  content/en/docs/reference/access-authn-authz/authorization.md  | 22(+S) 11(-)
[ ] M43.  content/en/docs/reference/access-authn-authz/service-accounts-admin.md  | 1(+XS) 1(-)
[ ] M44.  content/en/docs/reference/command-line-tools-reference/feature-gates.md  | 9(+XS) 15(-)
[ ] M45.  content/en/docs/reference/command-line-tools-reference/kube-proxy.md  | 1(+XS) 1(-)
[ ] M46.  content/en/docs/reference/issues-security/security.md  | 4(+XS) 4(-)
[ ] M47.  content/en/docs/reference/kubectl/overview.md  | 26(+S) 0(-)
[ ] M48.  content/en/docs/reference/scheduling/config.md  | 1(+XS) 1(-)
[ ] M49.  content/en/docs/reference/setup-tools/kubeadm/_index.md  | 1(+XS) 1(-)
[ ] M50.  content/en/docs/reference/tools/_index.md  | 5(+XS) 2(-)
[ ] M51.  content/en/docs/reference/using-api/health-checks.md  | 1(+XS) 1(-)
[ ] M52.  content/en/docs/setup/best-practices/certificates.md  | 47(+M) 3(-)
[ ] M53.  content/en/docs/setup/learning-environment/_index.md  | 3(+XS) 1(-)
[ ] M54.  content/en/docs/setup/production-environment/_index.md  | 1(+XS) 1(-)
[ ] M55.  content/en/docs/setup/production-environment/tools/kubeadm/control-plane-flags.md  | 3(+XS) 3(-)
[ ] M56.  content/en/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md  | 5(+XS) 26(-)
[ ] M57. content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md  | 768(+XL) 1138(-)
[ ] M58.  content/en/docs/tasks/access-application-cluster/web-ui-dashboard.md  | 22(+S) 16(-)
[ ] M59.  content/en/docs/tasks/administer-cluster/access-cluster-api.md  | 1(+XS) 1(-)
[ ] M60.  content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md  | 1(+XS) 1(-)
[ ] M61.  content/en/docs/tasks/administer-cluster/highly-available-control-plane.md  | 9(+XS) 2(-)
[ ] M62.  content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md  | 41(+M) 42(-)
[ ] M63.  content/en/docs/tasks/configure-pod-container/pull-image-private-registry.md  | 1(+XS) 1(-)
[ ] M64.  content/en/docs/tasks/configure-pod-container/static-pod.md  | 8(+XS) 1(-)
[ ] M65.  content/en/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md  | 3(+XS) 1(-)
[ ] M66.  content/en/docs/tasks/run-application/horizontal-pod-autoscale.md  | 1(+XS) 10(-)
[ ] M67.  content/en/docs/tasks/tools/install-kubectl-windows.md  | 4(+XS) 4(-)
[ ] M68.  content/en/docs/tutorials/_index.md  | 2(+XS) 0(-)
[ ] M69.  content/en/docs/tutorials/hello-minikube.md  | 10(+S) 4(-)
[ ] M70.  content/en/docs/tutorials/stateful-application/basic-stateful-set.md  | 1(+XS) 1(-)
[ ] M71.  content/en/docs/tutorials/stateful-application/zookeeper.md  | 1(+XS) 1(-)

0 files to be renamed
1 files to be deleted

[ ] D1.  content/en/docs/contribute/new-content/overview.md

Proposed Solution
Use git diff to check what is changed in the upstream. And apply the upstream changes manually
to the content/ko of upstream/dev-1.22-ko.2 branch.
For example:
# checkout `upstream/dev-1.22-ko.2`
...
# check what is updated in the upstream
git diff upstream/dev-1.22-ko.1 upstream/dev-1.22-ko.2 -- content/en/blog/_posts/2021-08-04-kubernetes-release-1.22.md
# apply changes to content/ko
vi content/ko/blog/_posts/2021-08-04-kubernetes-release-1.22.md
...
# commit and push
...
# make PR to `upstream/dev-1.22-ko.2`

Pages to Update
Pages in content/ko

/milestone dev-1.22-ko.2
/language ko
/help

M1 은 가급적 신규 컨트리뷰터께 할당하도록 하겠습니다.. ^^

M58-M71 : @seokho-son

M52-M53, M57 은 제가 해보겠습니다~

[Tasks assigned]
M1 : @lifeoncloud
M2 : @gochist
M3-M5: @seokho-son
M6-M35: @gochist
M36-M41: @seokho-son
M42-M49 : HEEEEEEEEEEEEEEELP
M50-M51 : @lifeoncloud
M52-M53 : @yoonian
M54-M56 : @seokho-son
M57 : @yoonian
M58-M71 : @seokho-son
D1 : @seokho-son
@yoonian 감사합니다. M57은 분량이 많아서, 혹시 이번에 처리가 어려운 경우, 다음 브랜치에서 처리 가능한 것으로 예외 처리 하였습니다..^^
나머지는 가급적 일정에 맞춰 진행하려 합니다.

M42 해보겠습니다~

M43-M49 제가 처리하겠습니다~~

@lifeoncloud  ko.2 마감 일정이 임박하여, M50은 제가 빠르게 처리하도록 하겠습니다...^^ 양해 부탁드립니다.

@seokho-son ㅠㅠ 감사합니다! 'fatal: bad revision'나와서 애먹고 있었어요ㅠㅠ

아닙니다~~ 브랜치 관리에 도움주셔서 감사합니다~~ :)

/close
but #30364 needs to be resolved ;)


Update EMF/WMF record type definitions

Necessary to fill out the definition of EmfPlusRecordType

build

@marek-safar fixed the build failure :)


Issue379 Requirements

Fixes #379; Adds basic requirement statements into Umple, including documentation in manual files and generating a requirement document.

This is a Beta version of the requirements feature in Umple.
Currently it can do the following actions:
 Process requirements at the top most level and output them whenever there is an "implementsReq" keyword in the code
 Generate a basic requirements document

A description for requirements has been added to the user manual page

To do:
 Create error codes - there are System.out.println("ERROR") messages instead of the error codes in the cruise.umple/src/class/UmpleInternalParser_CodeClass.ump : 221, 238 analyzeImplementReq() function
 Add syntax highlighting
 Add requirements to "User Manual Basics: List of Umple Keywords" and "Grammar to Define Umple" sections in user manual
 Add style to the requirements document (cruise.umple/src/generators/Generator_CodePlainRequirementsDoc.ump)
 Sort requirements in alphabetical order. Further instructions on line 57 of Generator_CodePlainRequirementsDoc.ump
 Add tests to the requirement doc generator
 Modify Mixsets to contain a HashMap of requirements (just like the Umple Model) and alter methods analyzeRequirement() line 203 and analyzeImplementReq() line 221, 238 in UmpleInternalParser_CodeClass.ump to add or take requirements from the appropriate spot (e.g. if stored in mixset, get from mixset and otherwise from the model).
 Modify function translateToHTML() at cruise.umple/src/Umple_Code.ump : 889 to account for requirement language styles (like markdown) in the generated requirements doc
 For requirements to appear as a tooltip in the GV Class Diagram, modify or create a similar function to appendTooltipComment() found in cruise.umple/src/generators/Generator_SuperGvGenerator.ump : 137
 Add a generate plain requirements doc option to UmpleOnline


Make watch.js respect paths in .dockerignore

This reduces CPU consumption of the node process running watch.js in cases where we have many files that don't need watching, eg. we have a large node_modules folder.

Approved!


HHH-16110 - MERGE for optional table update PostgreSQL

Rebased, squashed and manually applied to main and 6.2 branches

Awesome!


🫡

🫡🙋

Sorry, I don't know what this is supposed to mean.

I think he's thanking you for making the program and working on it.

Please do not post in closed issues.


[mlx-ui] Add kubeflow-userid header

mlx-ui needs to carry kubeflow userid header when sending
request to mlx-api. Then mlx-api can use it to access
ml-pipeline.
Signed-off-by: Yihong Wang<EMAIL_ADDRESS>

@ckadner mlx-api needs kubeflow userid header to know who is accessing the API and also uses it to access ml-pipeline in multi-user env. However, in our case, it's always admin user for now.

In mlx-ui, the session validator already adds kubeflow userid header for all of the external traffics to the underlying kubeflow except paths starting with /mlx. For paths starting with /mlx and proxy to mlx-api, there is no kubeflow user id. This change fixes it.

Thanks @yhwang this looks good to me. I'll give @ckadner a chance to look before merging.

/lgtm


Correction for raw affiliation Schulich School of Medicine and Dentistry, Western University

Correction needed for raw affiliation Schulich School of Medicine and Dentistry, Western University
raw_affiliation_name: Schulich School of Medicine and Dentistry, Western University
new_rors: 02grkyz14
previous_rors: 02agqkc58
works_examples: W4360620733;W4390574503;W4386414933;W4380989175
contact: a8934cc11b8a50a70d4e73c46c5a6853:de14c48015b8f7cc @ uwo.ca

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Added integration with beta lsp in buf

Buf language server as separate project was frozen, so I made integration with beta function 'lsp' of buf utility.

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

Thanks for this contribution! However, because this is an area that we're actively working on, we won't be able to accept this PR.