fix webflow for LPPE

Fixes an error in the webflow that prevented correct handling of password expiration.

Should this be fix be backported into 4.2?

Yes, I'm experiencing it at least as far back as 4.3.0-SNAPSHOT from shortly after the 4.2.0 release.

Great! Thanks.

Done. 4.2.2 shall have it.


changing header style

Is your feature request related to a problem? Please describe.
the colour theme of the header is very bad i can't see live events & join discord and it's also unorganised.
Describe the solution you'd like
changing colour theme as well as organising the header too.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

this is the current header style.


Deformations of PVR textures on iOS

I am using latest MoltenVK version 1.0.31 and do:

load texture in buffer with vkCreateBuffer;
create image with vkCreateImage and type VK_FORMAT_PVRTC1_4BPP_UNORM_BLOCK_IMG;
copy buffer to image with vkCmdCopyBufferToImage;
No validation errors on IOS, but texture looks without vertical synchronization.

If I add code in MVKCmdTransfer.mm:787
#if MVK_IOS
if (mvkMTLPixelFormatIsPVRTCFormat(mtlPixFmt)) {
bytesPerRow = 0;
}
#endif
and disable Metal validation, texture looks right.
If I enable Metal validation, I got error:
-[MTLDebugBlitCommandEncoder validateCopyFromBuffer:sourceOffset:sourceBytesPerRow:sourceBytesPerImage:
sourceSize:toTexture:destinationSlice:destinationLevel:destinationOrigin:options:]:524:
failed assertion `sourceBytesPerRow(0) must be >= (2048).'

I've now posted this to Apple's bug reporter.

This workaround doesn't work on Iphone XR and Iphone XS
Print screen:

New workaround:

Add check for compressed texture format in MVKImage::updateMTLTextureContent
and set bytesPerRow = 0
VkDeviceSize bytesPerRow = (imgType != VK_IMAGE_TYPE_1D ? imgLayout.rowPitch : 0);
if (_mtlPixelFormat == MTLPixelFormatPVRTC_RGB_4BPP)
{
bytesPerRow = 0;
}
[getMTLTexture() replaceRegion: mtlRegion
mipmapLevel: imgSubRez.mipLevel
slice: imgSubRez.arrayLayer
withBytes: pImgBytes
bytesPerRow: bytesPerRow
bytesPerImage: (imgType == VK_IMAGE_TYPE_3D ? imgLayout.depthPitch : 0)];

In Vulkan code:
vkCreateImage()
vkAllocateMemory() with type VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT
vkMapMemory()
memcpy - compressed data
vkBindImageMemory()
vkUnmapMemory()

In this case compressed texture loads without deformations on Iphone XS and Iphone XR too.

@abeyn
Thanks for the update. I should update the MoltenVK code you identify.
How is your new workaround different than your previous workaround? Both seem to just be setting bytesPerRow to zero.

This workaround doesn't use vkCmdCopyBufferToImage and changes other source
MVKImage::updateMTLTextureContent.
In this case no validation errors from Metal

Apple has confirmed @jamesd9's suspicion about MTLBlitOptionRowLinearPVRTC expecting the buffer content to be untwiddled.
Here is Apple's response from the recent bug report I posted about this:

So basically the sample tries to use pre-twiddled data for [blitEncoder copyFromBuffer] instead of linear strided data, which is incorrect behavior. Replacing copyFromBuffer with replaceRegion fixes the issue (as expected when using pre-twiddled texturedata). Untwiddling the inputdata before creating the buffer also fixes them problem (as copyFromBuffer expects linear strided data). The reason that using a stride 0 works is an unexpected side effect that only works on devices that don’t support tiling (as the driver copies the pre-swizzled data as-is and creates a swizzled texture using this data). On hardware that does support tiling, the data is copied as-is and then used for a tiled view, which causes tiles to be incorrect. Suggested fix is to either use [texture replaceRegion] or to unswizzle the data before creating the buffer.

PR #539 includes @abeyn's fix to allow host-memory mapped PVRTC image content to be loaded correctly...and documentation to the effect that staging-buffers cannot be used with PVRTC content.
@abeyn Please test the latest MoltenVK without your patch above...to ensure that it fixes the issue for you...and close this issue if it does.

Thank you very much. It work's.


Change datasource type names

This issue suggests to change the datasource types "lidar" and "route" to "pointcloud" and "trajectory", respectively. We already have sensor types, so we may want to use consistent names.

ok


UI Styles: Implement 'box-shadow'

For box-shadow, we'll want to add a Style property, something like:
Style.make(~boxShadow=BoxShadow(-5., -5., 10., 10., Color.rgba(0., 0., 0., 0.5), ..., ())

The box-shadow properties would mirror the properties from CSS: https://developer.mozilla.org/en-US/docs/Web/CSS/box-shadow
(in order)

xOffset - the horizontal offset of the shadow
yOffset - the vertical offset of the shadow
blur radius
spread radius
color

Note that the box shadow won't impact Layout, so we don't need to worry about passing it to layout (like we did for flex properties!)
The way I would think about tackling this is splitting it up into a few parts:
Part 1: Set up the types
For part 1 - I'd just look at adding the types in Style.re, and plumbing them through.
We'd need to:

Add a BoxShadow type
Add a boxShadow property to the Style record / make fucntions

Part 2: Render a solid shadow
For part 2, I'd skip the blur / spread to simplify things - we can just render a quad the same size as the view node, but offset based on the values of xOffset and yOffset.
The place we'd want to look at drawing this is in the ViewNode - this is the code that draws the background of a node:
https://github.com/bryphe/revery/blob/4a52028176aad32f81973a3a0bbc651299359dda/src/UI/ViewNode.re#L48
Prior to drawing that - we'd want to draw the 'shadow' quad. Right now, our rendering looks like this:

Set uWorld for background quad - this is the transform matrix
Set uColor for background quad - this sets the color in the shader

With our shadow, we'd want to do this in two passes:

Render shadow

Set uWorld for shadow - this is like the transform for the background quad, but with an extra translation to set the xOffset/yOffset.
Set uColor for the shadow - this would be based off the shadow color
Draw via Geometry.draw(_quad, solidShader)

Render background

Set uWorld for background (same as today)
Set uColor for background (same as today)
Draw via Geometry.draw(_quad, solidShader)

So our shadow would add an extra draw call
Part 3: Render the blurred edges
For part 3, we'd take into account the spread and blurRadius.
I think the easiest way to handle this (at least in a quick way) would be to add additional quads for the edges, and render those edges with a shader that handles the gradient. At the 'core' of our shadow, the opacity would be 1.0 x the shadow color. At the edge of the shadow, it'll fall off to 0 - becoming more transparent as it spreads out. We could use additional quads around the core shadow, along with a shader that models this fall-off to get a smooth gradient.
There might be better ways to handle this, too.

I'll have a look at this @bryphe, any tips?

@bryphe re. setting the uWorld for the shadow does that mean creating a similar function like getWorldTransform in Node.re ?

@bryphe re. setting the uWorld for the shadow does that mean creating a similar function like getWorldTransform in Node.re ?

Essentially we'd have to do something like this:
let shadowTransform = Mat4.create();
Mat4.fromTranslation(shadowTransform, Vec3.create(shadowOffsetX, shadowOffsetY));

let worldShadowTransform = Mat4.create();
worldShadowTransform = Mat4.multiply(worldShadowTransform, _this#getWorldTransform(), shadowTransform);

And then we'd set uWorld to do that. The worldTransform is all of the parent transforms applied (any animations, offsets, etc), and then the shadowTransform is just the transform we need for the shadow. Essentially what this is saying is 'First, move my shadow quad based on the shadowOffsetX, shadowOffsetY. Then, apply each parent transform in turn'. Parent transforms might include rotations, scales, etc - they would all get applied in this case.
Hope that helps! Reading through the transforms section here might help too

@bryphe thanks that helped a lot :+1:,got another question now I've actually drawn the shadow, I'm not sure I followed the strategy you suggested about  using more quads with lessening opacity to draw the blur?

What are your thoughts on named parameters for the BoxShadow? Right now I think it's a little confusing if you don't already know the order of arguments for BoxShadow. I think it would benefit to either have a record/object represent the shadow's parameters or a labelled function that could optionally be used to allow for named/out-of-order parameters.

@OhadRau - I'd be open to it, and I think it's a great way to 'use the language'. I never remember the order of those parameters, have to look it up every time 😄
The BoxShadow.make seems consistent with how we use Style's at least.
@Akin909 - what do you think?

@bryphe @OhadRau sounds like a great suggestion to make things less error prone, I can tweak what I'm working on to use the BoxShadow.make version :+1:

@bryphe thanks that helped a lot 👍,got another question now I've actually drawn the shadow, I'm not sure I followed the strategy you suggested about using more quads with lessening opacity to draw the blur?

Sweet I just pulled the branch and saw the shadow coming through! 😍
I actually don't think we'll actually need more quads with this strategy, if we handle the gradients all in the shader with that 'cutoff'. Seems like it'd all be doable in the pixel shader - just need to handle the other directions!

Implemented with #107 - thank you @Akin909 !


Move onThreadStart execution hook after check that wrapping thread timed out

In Netflix production testing, this fix resolved #509

Hystrix-pull-requests #235 FAILURE
Looks like there's a problem with this pull request


Field-level Validation

Allows for things like:
const required = value => value == null ? 'Required' : undefined

<Field name="firstName" component="input" validate={required}/>

Current coverage is 100% (diff: 100%)

Merging #2245 into master will not change coverage

@@           master   #2245   diff @@
=====================================
  Files          58      59     +1
  Lines        1148    1196    +48
  Methods         0       0
  Messages        0       0
  Branches        0       0
=====================================
+ Hits         1148    1196    +48
  Misses          0       0
  Partials        0       0

Powered by Codecov. Last update c679dd2...4e670cc

Why is validate prop passed down to Field's component? Let's see this example:
<Field
  name="email"
  component={Input}
  validate={[isRequired, isEmail]}
  normalize={value => `%${value}%`}
  format={value => (value ? value.slice(1, -1) : '')}
/>

Now as a props of Input field I get name, input, meta and validate. Why si validate passed down? As a matter of fact I don't understand why is name passed down either as it's part of input object anyways. On the other hand component, format and normalize are not passed down which makes sense.
The reason why I'm asking is because people usually do something like this in their Input component:
const Input = (input, meta, ...rest) => {
  return (
      <input {...input} {...rest} />
  );
};

This alows them to be able to pass down placeholder, type, maxLength, className and any other valid input attribute. React 15 will have a warning if they pass something that doesn't belong to input tag:
<Field
  name="email"
  component={Input}
  validate={[isRequired, isEmail]}
  normalize={value => `%${value}%`}
  format={value => (value ? value.slice(1, -1) : '')}
  placeholder="Input placeholder"
  type="text"
  maxLength="30"
  className="myInput"
/>

With this new version we need to expect validate and make sure we don't assign it to input field. Maybe it doesn't make sense to pass down any of these props that Field component expects to be passed to it? I personally use ...rest spread operator as I don't want to expect every single valid input attribute inside Iput component.


wrapper.setSelected() triggers a change event even if the option is already selected

Version
1.0.0-beta.29
Reproduction link
https://codepen.io/vvanpo/pen/MWWroOK
Steps to reproduce

Mount a component with a <select> element.
Call setSelect() multiple times on one of the select element's options.
Observe the <select> element wrapper's emitted('change').length is equal to the number of times setSelect() was called.

What is expected?
A <select> element emits a change event only when the element value has actually changed.
What is actually happening?
setSelected() triggers a change event every time it is called, regardless of whether the underlying value was changed.

I hesitated to open this as a bug, as the documentation is explicit in saying that trigger('change') is called every time: https://github.com/vuejs/vue-test-utils/blob/v1.0.0-beta.29/docs/api/wrapper/setSelected.md
However, I believe setSelected() is generally used to mimic user interaction, not programmatic interaction. So it follows that setSelected() should behave in the same way as a user interacting with a <select> element's <option>s, which I believe will only ever fire a change event if the selection has been modified.

You are correct, it only emits change event if select another option. It shouldnt be hard to see if an option is selected.

@vvanpo as you said and the docs explicitly state it triggers the change event  every time I don't think this is a bug. I don't think the test-utils should keep track of data and know if something has changed between two calls. If setSelected() gets called multiple times, it's fair that it does it job multiple times.

@codebryo I am a but split here. I agree with you on that one, yet I saw that selecting the same option does not trigger an event... Do we want to emulate a user action or explicitly do what the action states.. hmmmm @afontcu @JessicaSachs @lchanmann Opinions here?

I just noticed that in setChecked we're not sending the event if the element is already checked https://github.com/vuejs/vue-test-utils/blob/950763fe07eb1eceadd6e37c6e8b07d87b075a14/packages/test-utils/src/wrapper.js#L356-L357
...even though docs say the exact same thing regarding it being an alias of setting the right value and emitting the event.
I'd say all setXXXX methods to behave the exact same way. We could make them emulate the user or not, but in a consistent way. For the record, I'd like them to stay closer to the users.

@afontcu good find, it seems clear to me that emulating user actions is the most intuitive and useful behaviour, here.
Interestingly, that same is not true when calling setChecked() on an <input type="radio" />. It used to be, but was removed in ef66c261, which looks to me like a regression.

If there are no objections, I'll open a PR for this.

Yes please, @vvanpo


 box broken in Chrome 53

Newest version of Chrome has made the display of the dropdowns ugly.  Look at the bottom of this page:
https://predixdev.github.io/px-forms-design/

looks like it's fixed in the latest version.  closing.

Hey @gstroup - I saw this in Chrome 54 and made this fix for it: f1b2db8231c22575b78bd48f65c91674fd6a62f9
No idea why it the same fix didn't solve things in 53 though!?!?!
http://i.imgur.com/Q3cUg29.gif

No worries, I think it was my dumb mistake!  (I was using an old version.)
Also found that the problem is visible in the new polymer seed app, since we're using an old version of this component.

or maybe the github pages branch needs to be updated too?  Not sure.


Some fields in client inappropriately bring up autofill suggestions

In Chrome, when adding a client some fields bring up the browsers autofill functionality when they should not.
STEPS TO REPRODUCe

Go to clients page
click Add Client
Click in ethnicity field (email and phone too. But check all fields though )

RESULTS
Expected - No auto fill comes up
Actual - the browser suggests YOUR address for that field

Closing because #330 already cover this


os-bind allow specifying port in forwarders

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[ ] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
[ ] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
[ ] When the request is meant for an existing plugin, I've added its name to the title.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Currently the GUI only allows forwarders on port 53, syntax like <IP_ADDRESS>:5335 and <IP_ADDRESS> port 5335 are both not allowed. In named.conf I can specify port using <IP_ADDRESS> port 5335, however.
Describe the solution you'd like
A clear and concise description of what you want to happen.
(e.g. I would like an input field in the /ui/firewall/alias which would add .... to ....)
Either a mapping from <IP_ADDRESS>:5335 to the proper bind syntax in the config or simply the option to enter the syntax manually in the GUI
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Manually editing the config file
Additional context
Add any other context or screenshots about the feature request here.

https://github.com/opnsense/plugins/issues/1715 already has a PR, but needs work.


Make linter forward compatible to next SL4

SublimeLinter is heading towards SL4. We have noticed that the current implementation will break on SL4.
Reason: Although you subclassed PythonLinter your code actually opted out of any specific python handling in SL3. E.g. you don't specify "mypy@python" or set module to something. The net result is, that your linter always uses the first mypy executable in PATH it can find. To get this behavior, it is better to just use the base Linter.
Note that you don't have to 'fix' build_cmd then as well.

Iirc I mostly subclassed PythonLinter to get all the default attributes regarding inline parsing and stuff, but since all of that will be gone with SL4 there probably isn't any reason not to just subclass the main Linter until the SL4 stable is released, in which case we can probably switch to the new linter to get the new env resolving logic.
I'll take a look into this (and test it properly) once I do something notable with Python again.

Re-added support for inline settings. 😉
Note: Inline-settings are not a special feature of the PythonLinter in SL3. They're triggered just by setting comment_re appropriately.


Context menus win registry entries not removed if entries already exist from alternate install

VS Code Version: 1.53.2
OS Version: Win10 Pro, 1909, build 18363.1316

Steps to Reproduce:

Install both system and user installer with context menu actions enabled
Uninstall either, or both.
Check context menus and registry for unremoved entries

Does this issue occur when all extensions are disabled?: Yes

After accidentally installing both the user and system installers with context menu items enabled, neither uninstaller is able to remove any of the context menu items, leaving the corresponding registry entries in a hard-to-recover-from state; I have to manually search for every instance and remove them.

You really can only reproduce this if you install both?

I haven't checked to see if the registry changes persist after a normal uninstall. I should probably have mentioned the breaking issue with this is that when the system installer is run while the user install is active, the context menu items still reference the user install location, and then if you uninstall the user installation, those context menu items still persist and point to a non-existant install location.

The thing is: the system and user context menu items all live in separate places in the registry. So I wonder if, when you've managed to install both, shouldn't those items just appear as duplicates in the context menu?


Feature/nextflow dag extension

This fixes the nextflow dag parsing to properly connect processes based on dependencies. It does not take into account any channels edited by operations.
Also gets the default docker container from the nextflow config if it is defined.

Coverage decreased (-0.2%) to 67.113% when pulling b78c7d12211d588b18e0dd695b7aa84a33662f92 on feature/nextflowDagExtension into b0ea911580426783a196a4e554104ad8c331f81f on develop.


Cannot invote 'new' on Nanobar using require

I am unable to invoke a new Nanobar object when using RequireJS. Here is an example implementation:
var Nanobar = require('nanobar')
var nanobar = new Nanobar();
nanobar.go(50)

The result is Uncaught TypeError: Nanobar is not a constructor
However the following will correctly render nanobar:
var Nanobar = require('nanobar')
Nanobar.go(50)

With this implementation, however, I am unable pass options to it (need to set the target)

I'm not close to my computer right now, can you try changing line 138 in nanobar source please?
Instead:
    define([], Nanobar)

try:
    define([], function () {return Nanobar})

Ah, yes. This seems to fix the issue just fine. Thanks a million @jacoborus

Fixed in v0.4.2  17b4e1c3db1e2a54010961d59ce65f78baf0d3cf

@westonkjones  you can upgrade now. Thanks for pointing the bug


Adjust spatial filtering (hard buffer)

Current problems:

Long loops outside buffer area are included, but not wanted
Shapes should be removed, when there are no matches.

Solution:

Make spatial filtering stop_times -based:

Find the longest in[-out-in]-in stretch of stop times (within soft bufffer distance). If all in -> do nothing. If all out (remove the trip_I and its stop_times). If partially out (before or after) remove the excess tendrils .
For the pre-filtered trip, check that no stops reside outside hard buffer. If some stops are, filter them out -> The trip gets splitted into multiple trips (but on the same route). Adjust stop_times.txt, trips.txt and shapes.txt accordingly

Finally: Remove all stops which are not referenced in stop_times (and are not parent_stops). Continue then as usual with the "cascading" filtering of the data.
If a trip is worth only 1 stop_times entry, remove the whole trip.

This should be sorted out now in commit #2dee920


App crashes after the 16th screen

I'm using welcome-android to create a slideshow gathering all the things my wife loves.
There are 36 pages, and I'm using almost all page example model included in welcome-android.
Until now, I used only photo.png provided in welcome-android https://github.com/stephentuso/welcome-android/blob/master/sample/src/main/res/drawable/photo.png, and I could see the whole slideshow without any issue.
Now, I replace "photo.png" with resized photos/clipart (500x500px & transparent background), and here is my problem/issue : App crashes after the 16th screen.
Here is my logcat : http://pastebin.com/LfDkGTag

Glad you brought this up, I've never tested it with that many pages. The crash is because it's running out of RAM:
Throwing OutOfMemoryError "Failed to allocate a 12250012 byte allocation with 8930112 free bytes and 8MB until OOM"
However, that could be due to the size of your images (that's 12 MB), I think loading a bitmap is the only thing that would take up that much space after the app has already started, make sure all your images are resized/optimized correctly. This was more intended to be used with SVGs and simpler PNGs, if these are photographs they will probably need to be compressed quite a bit. Within the next week I can look into optimizing it to use memory more efficiently though.

Thank you for your answer Stephen Tuso

I was having this problem too until I read this answer: https://stackoverflow.com/questions/19196616/is-there-a-way-to-create-xxhdpi-xhdpi-hdpi-mdpi-and-ldpi-drawables-from-a-lar
Steps to reproduce:

PNG image (88 KB, 1920x1080)
PNG located inside the default "drawable" folder
App would crash because of OutOfMemoryError when moving welcome screen

Solution:

Moved the PNG files to the "drawable-xxhdpi" folder

Closing this, task added as #54


replace linked_hash_map with hashlink

cc https://github.com/contain-rs/linked-hash-map/issues/97

it seems that linked-hash-map is quite stable (and used by several popular crates), and we have no reason the switch to a new crate.

linked-hash-map triggers UB (detected by miri). See the issue you linked and this issue at rustbreak(which has linked-hash-map only as a transitive dependency through this crate and already triggers UB in the testsuite).

Since linked_hash_map is broken on rust 1.48.0, and this is affecting downstream projects, this is pressing.

I am getting the following error when attempting to deserialise some YAML using serde:
thread 'test::simple' panicked at 'attempted to leave type `linked_hash_map::Node<yaml::Yaml, yaml::Yaml>` uninitialized, which is invalid', /home/martin/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/mem/mod.rs:658:9
stack backtrace:
   0: rust_begin_unwind
             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:483
   1: core::panicking::panic_fmt
             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/panicking.rs:85
   2: core::panicking::panic
             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/panicking.rs:50
   3: core::mem::uninitialized
             at /home/martin/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/mem/mod.rs:658
   4: linked_hash_map::LinkedHashMap<K,V,S>::ensure_guard_node
             at /home/martin/.cargo/registry/src/github.com-1ecc6299db9ec823/linked-hash-map-0.5.2/src/lib.rs:174
   5: linked_hash_map::LinkedHashMap<K,V,S>::insert
             at /home/martin/.cargo/registry/src/github.com-1ecc6299db9ec823/linked-hash-map-0.5.2/src/lib.rs:304
   6: <serde_yaml::ser::SerializeMap as serde::ser::SerializeMap>::serialize_entry
             at /home/martin/.cargo/registry/src/github.com-1ecc6299db9ec823/serde_yaml-0.8.11/src/ser.rs:342
   7: <serde::private::ser::FlatMapSerializeStruct<M> as serde::ser::SerializeStruct>::serialize_field
             at /home/martin/.cargo/registry/src/github.com-1ecc6299db9ec823/serde-1.0.118/src/private/ser.rs:1282

Any movement on this? This has been preventing projects from using newer rust versions for 2 months now.


feat(testing): adding playwright as dependancy

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Can you rebase this against main and also while you are rebasing, modify the commits to conform to conventional commits.


[Functional] Implement KeyStoring protocol

Implement the KeyStoring Protocol
protocol KeyStoring {
    func importBirthday(_ height: BlockHeight) throws
    func exportBirthday() throws -> BlockHeight
    func importPhrase(bip39 phrase: String) throws
    func exportPhrase() throws -> String
    func areKeysPresent() throws -> Bool
    /**
    Use carefully: Deletes the seed phrase from the keychain
    */
    func nukePhrase()

    /**
    Use carefully: deletes the wallet birthday from the keychain
    */
    func nukeBirthday()

    /**
    There's no fate but what we make for ourselves - Sarah Connor
    */
    func nukeWallet()

    var keysPresent: Bool { get }
}

enum KeyStoringError: Error {
    case alreadyImported
    case uninitializedWallet
    case storageError(Error)
}

So that the wallet recovery phrase and birthday can be stored to keychain.
KeyStoring is an interface abstracted from the SeedManager class of the ECC Reference wallet
https://github.com/zcash/zcash-ios-wallet/blob/master/wallet/wallet/Utils/SeedManagement.swift
It uses the dependency KeychainSwift as a wrapper for they keychain C API.
This is a key component to the wallet's security. The PR closing this issue must be reviewed and approved by @defuse  in addition to the usual iOS reviewers

Update:
Given the suggestions that @ccjernigan made in the PR.
some approach could be (this is totally for reference, please apply your best judgement)
struct StoredPhrase {
   var version: Int
   var phrase: String
   var birthday: BlockHeight? //Int
}
protocol KeyStoring {
    func importPhrase(_ phrase: StoredPhrase) throws
    func exportPhrase() throws -> StoredPhrase
    func areKeysPresent() throws -> Bool
    func updateBirthday(_ height: BlockHeight) throws

    /**
    There's no fate but what we make for ourselves - Sarah Connor
    */
    func nukeWallet()
}

enum KeyStoringError: Error {
    case alreadyImported
    case uninitializedWallet
    case storageError(Error)
    case unsupportedVersion(Int)
}


BUG: optimize.linprog fails with list type integrality containing only zeros

Describe your issue.
The code pasted below causes a runtime error. It is simply a modification of the test problem added in https://github.com/scipy/scipy/pull/17513, where all variables have been changed to continuous ones.
I have conducted a local check, and I believe that a modification similar to the one shown in https://github.com/scipy/scipy/compare/main...hitonanode:scipy:fix-linprog-integrality might resolve the issue.
Reproducing Code Example
from scipy.optimize import linprog

linprog([1, 1], A_ub=[[-1, 0]], b_ub=[-2.5], integrality=[0, 0])

Error message
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/user/Library/Caches/pypoetry/virtualenvs/test-D9Qlf53g-py3.11/lib/python3.11/site-packages/scipy/optimize/_linprog.py", line 644, in linprog
    _check_result(sol['x'], sol['fun'], sol['status'], sol['slack'],
  File "/Users/user/Library/Caches/pypoetry/virtualenvs/test-D9Qlf53g-py3.11/lib/python3.11/site-packages/scipy/optimize/_linprog_util.py", line 1496, in _check_result
    valid_bounds |= (integrality > 1) & np.isclose(x, 0, atol=tol)
                     ^^^^^^^^^^^^^^^
TypeError: '>' not supported between instances of 'list' and 'int'

SciPy/NumPy/Python version and system information
>>> import sys, scipy, numpy; print(scipy.__version__, numpy.__version__, sys.version_info)
1.13.0 1.26.4 sys.version_info(major=3, minor=11, micro=8, releaselevel='final', serial=0)

I'll submit a PR shortly.


[33, 36, 37, 38] Various improvements

Resolves #33 - added language selector
Resolves #36 - rebranded to Control Panel
Resolves #37 - removed Dashboard route
Resolves #38 - updated favicon and app icon

 Začistit UI kontrolního panelu


feat: support constructing arrays from iterators (PROOF-913)

Rationale for this change
Add a constructor to support creating a managed_array from two iterators. This is a convenience constructor and matches what's available in other standard containers such as std::vector.
What changes are included in this PR?

Adds new constructor to managed_array that takes two iterators.

Are these changes tested?
Yes

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


Add favicon

hi all,
i wonder how can i add a favicon.
thank...
vlw fwi, Holmes :)

solved!
default.html edited the file and add two parameters to see:
==============================

{% if page.title %}{{ page.title }} – {% endif %}{{ site.name }} – {{ site.description }}
{% include meta.html %}

<!--[if lt IE 9]>
  <script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->

<link rel="stylesheet" type="text/css" href="{{ site.baseurl }}/style.css" />
<link rel="alternate" type="application/rss+xml" title="{{ site.name }} - {{ site.description }}" href="{{ site.baseurl }}/feed.xml" />

**<link rel="shortcut icon" type="image/x-icon" href="/favicon.ico?">**

<link href='//fonts.googleapis.com/css?family=Lato:400,700|Raleway:400,700|Comfortaa:700' rel='stylesheet' type='text/css'>

<!-- Created with Jekyll Now - http://github.com/barryclark/jekyll-now -->

**<!-- Fav and touch icons -->
<!-- Update these with your own images -->
  <link rel="shortcut icon" href="images/favicon.ico">**
        </head>

==============================
add the favicon.ico file in user.github.io.
ready!
vlw fwi, Holmes :)

I just noticed this @holmeslinux , good you got it.

@holmeslinux since you got this solved, could you close the issue? I don think this would be something @barryclark could like to add since not every user will have a favicon to add to their site and other wise may cause issues. Even though we could do an if favicon then show it kind of check. That would be up to Barry Clark.

ok, close!
thank...
vlw fwi, Holmes :)

I think it would be a great thing to implement in Jekyll. Favicons are free and easy to create! gh-pages is always looking for one! Anyway, thanks @holmeslinux for sharing your discovery!

@holmeslinux Thanks so much for that. I spent a while trying to add it but realised I must place it in the default.html so I had to clone the default.html from the theme I am using and place it in the _layouts folder then appending the line to add the favicon. Finally placing the favicon.ico in the root of the repo.

I was expecting it to be available in config.

When I go to my "About" page, the favicon just disappear. Do you guys know how to resolve it?


⚠ Cioos National CKAN has degraded performance

In 87fb298, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 6125 ms

Resolved: Cioos National CKAN performance has improved in 50c55a9 after 1 hour, 11 minutes.


ci: Add setup-dependencies action and refactor workflows

Description
This pull request introduces a new GitHub Action for setting up dependencies, streamlining the CI/CD process. The changes include:

Created a new composite action setup-dependencies to centralize dependency installation.
Updated code-quality.yml and code-test.yml workflows to use the new setup-dependencies action.
Improved the pull-request-checks.yml workflow by adding a name to the labeller job.
Enhanced the main function in __main__.py with a docstring.
Added a return type annotation to the test_main function in test__main__.py.

These changes aim to reduce duplication in workflow files, improve code documentation, and enhance type safety in the test suite.
fixes #72

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#71  👈
#68
#67
#63
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @JackPlowman and the rest of your teammates on  Graphite

Merge activity

Oct 5, 4:32 PM EDT: @JackPlowman merged this pull request with Graphite.


add azure serverless meetup cologne

HI @FlonairLenz , can you please add your event details to the index.md file?
Thanks!


Remove ManageIQ::Password alt-keys usage from FixAuth

We want to bump to manageiq-password 1.0 both for currency and in order to fix #21042. However, we need to remove the usage of alt-keys since that interface changed with the major release of manageiq-password.
I had this branch from a long time ago, but for some reason never made a PR.  It works with the 1.0 release of manageiq-password.
Depends on

[x] https://github.com/ManageIQ/manageiq-loggers/pull/37

[x] and subsequent release (v0.7.0)

[x] https://github.com/ManageIQ/manageiq-smartstate/pull/161

[x] and subsequent release (v0.8.1)

[x] https://github.com/ManageIQ/manageiq-postgres_ha_admin/pull/26

[x] and subsequent release (v3.1.3)

[x] https://github.com/ManageIQ/manageiq-appliance_console/pull/171

[x] and subsequent release (v0.7.2)

[x] https://github.com/ManageIQ/manageiq-gems-pending/pull/524
[x] https://github.com/ManageIQ/manageiq-schema/pull/579

Only dependent for build purposes:

[ ] https://github.com/ManageIQ/manageiq-appliance/pull/340

cc @kbrock
Hoping this can fix some of the issues in https://github.com/ManageIQ/manageiq/issues/21042

I'm on the fence about the plaintext fields.  On one hand, you argument about automate fields has me worried we'd break automate, but on the other hand, that part of automate is in much better shape, and should properly decrypt the keys now.  I think I'm going to leave it as is and let it encrypt the plaintext fields.

@miq-bot cross-repo-test including manageiq-password@master

@miq-bot cross-repo-test manageiq#21178 including manageiq-password@master

I pushed out a new manageiq-password 1.0, gem, but when I went to update this PR, there are depedency references in a number of other gems that I will have to deal with first (manageiq-schema, manageiq-gems-pending, manageiq-smartstate, manageiq-postgres-ha_admin, manageiq-appliance_console (and technically vmware_web_service)

Yeah, I plan to get back to this one next - I'm just going to upgrade all of the repos' manageiq-password.

@Fryguy I came here from https://github.com/ManageIQ/manageiq-appliance/pull/340 and don't understand the WHY for that or this change.  Is there a link to a manageiq-password PR that demonstrates the why?  I'm not sure what alt-keys are and there's lots of comments here but not much detail at the top of this PR.

Yeah I guess it's not clear reading with fresh eyes.
So, we want to bump to manageiq-password 1.0 b order to fix #21042.  However, we need to remove the usage of alt-keys since that interface changed with the major release of manageiq-password.  Most of the other PRs were loosening the restriction

There are no more dependent PRs, so this should go green directly and be using 1.0 of manageiq-password.

Wait, it failed in travis.

There were a couple of methods that were merged to master after the original PR, that had calls to fix_passwords...incoming fix.

Fixed.  I also decided to not change https://github.com/ManageIQ/manageiq/pull/21178#pullrequestreview-637148954, so that comment thread can be ignored.

LGTM

Looks like some failures in manageiq-automation_engine after this https://app.travis-ci.com/github/ManageIQ/manageiq-automation_engine/jobs/546790556#L2043-L2057


%Object% after localize pipe

This code in template:

{{ '/news ' | localize }}

{{ '/news' | localize }}

{{ '/newsa' | localize }}

{{ '/about ' | localize }}

{{ '/about' | localize }}

working as:

/en/news%20

/en/[object Object]

/en/newsa

/en/about%20

/en/about

in package.json i have "localize-router": "^1.0.0-rc.4",

What json are we talking about? package.json?

Your translations (en.json for example)

But I don't use it here, see template in first message.
Only localize pipe

If you set the prefix of localise router to empty string and you have an en.json with a value like
{ "news": { "test": "test value" } }, the localize pipe will automaticaly take the value of "news" ([object Object] in this case).
This is how localize-router works.

Your advice about empty string possibly made useful, I will check this version
Thank you! =)

Thank you @gilsdav for the support!


Some data csv files could not be found

Some data csv files could not be found, 15minute_data_california/15minute_data_california.csv, /metadata.csv

Hello,
This is intentional. These CSV files are only needed to generate resi_load.csv, as shown in resi_data.py. However, the main focus of this repo is in the optimization of dispatch as indicated by the README. Thank you.


Bug: I think it is possible to select a RootArrangement????

Somehow I am able to select something that is on a screen without any children. I guess the workspace has a m_selectedWindow = null. But when I then move that something it appears that somehow a vertical arrangement or something appears. Not quite sure what happenes...


credentials not working

credentials not working.
endpoint connect fails.
new verion:

old version:

What type of credential are you using, encrypted in db, private key etc?  Send a screen shot of editing the credential.

I suspect username is not getting stored correctly because after clicking edit username is not prefilled even it is saved earlier.

The encryption of the userid and password are done by the deployment engine.  I think this maybe related to #45.


GitHub: Update issue templates to make users copy Windows version from settings

Validation
How did you test these changes?
My own fork with issue template on

On second thought, the about page doesn't actaully show the Windows version. It's only after pressing the copy button.

What would you like to be displayed there instead?

We could theoretically explain that the copy button copies the Windows version as well, but I'm concerned that'll just confuse the issue authors. It might be best to just leave the template as is.

We could theoretically explain that the copy button copies the Windows version as well, but I'm concerned that'll just confuse the issue authors. It might be best to just leave the template as is.

Or also add a further button to copy the Windows version

It's not high priority but #4635 will make it a lot easier.

Do we really need specific windows version in the first place? Why not we make dropdown for the selection of Windows 10/11, and of Dev/Preview/Stable, and of 21H1/21H2/22H1…?

A dropdown is a good idea, can you open a PR for this?


Preview packages go backwards in version from released packages

This led me to believe visually that there was no preview to try. It also confuses NuGet tooling when you ask for prerelease updates.
Ordinarily, the version would be 1.2.1-x. I use a build script that autoincrements the csproj/props version based on git tags so that manual commits are not needed to achieve this. (https://github.com/Techsola/InstantReplay/blob/main/build.ps1#L17-L20)

Oops, usually I manually upgrade minor after each release, but forgot to this time.


Renaming local vars following tips from golint

I have mixed feelings. While many of the names of local variables can be corrected without issue, for the ones that are exported, we can't make those changes. This would make the code inconsistent - using both Id and ID. If we can't be consistent, I am not sure it's worth it.

Local consistency is more important than golint in this case.


QUESTION: Can I make a subquery for a nested array

This is more of a question than an issue. Is there a way to write a query that returns a nested array for a related item? For example, if I have Persons and Pets the result might be:
[
  {
    name: 'Sam',
    pets: [
      { name: 'Nugget' },
      { name: 'Fluffy' },
    ],
  },
];

I know in Postgres I can use array_to_json(array_agg(row_to_json(data))) for something like this:
SELECT
  person.name,
  ( SELECT array_to_json(array_agg(row_to_json(pet)))
    FROM (
      SELECT
        name
      FROM
        pet
      WHERE
        pet.owner = person.id
    ) AS pet
  ) AS pets
FROM
  person

I've tried a relatedQuery() that selects everything, but I get the error: "subquery must return only one column"

Objection is a query builder so anything is possible. That exact query can be built like this:
const fromSubQuery = Pet.query()
  .select('name')
  .where('pet.owner', ref('person.id'))
  .as('pet')

const petsSubQuery = Pet.query()
  .from(fromSubQuery)
  .select(raw('array_to_json(array_agg(row_to_json(pet)))'))
  .as('pets')

const result = await Person.query().select('person.name', petsSubQuery)

But there's a much easier ways to get the same result:
const result = await Person.query().withGraphFetched('pets')

or
const result = await Person.query().withGraphJoined('pets')

You can find information about the differences between withGraphFetched  and withGraphJoined in the docs.

Objection is a query builder so anything is possible. That exact query can be built like this:
const fromSubQuery = Pet.query()
  .select('name')
  .where('pet.owner', ref('person.id'))
  .as('pet')

const petsSubQuery = Pet.query()
  .from(fromSubQuery)
  .select(raw('array_to_json(array_agg(row_to_json(pet)))'))
  .as('pets')

const result = await Person.query().select('person.name', petsSubQuery)

But there's a much easier ways to get the same result:
const result = await Person.query().withGraphFetched('pets')

or
const result = await Person.query().withGraphJoined('pets')

You can find information about the differences between withGraphFetched  and withGraphJoined in the docs.

Ok. I figured there was a way. I even tried using withGraphedFetch, but I must have done something wrong. I'll give that another go.
Thanks!

Ok. I figured there was a way. I even tried using withGraphedFetch, but I must have done something wrong. I'll give that another go.
Thanks!

The documentation and the examples are quite useful. I suggest you take a look at them. withGraphFetched should be familiar to you if you even glanced at the documentation 😉

The documentation and the examples are quite useful. I suggest you take a look at them. withGraphFetched should be familiar to you if you even glanced at the documentation 😉

Thanks. I actually did look through the documentation quite thoroughly. I tried an approach with all these before posting:
https://vincit.github.io/objection.js/recipes/subqueries.html
https://vincit.github.io/objection.js/recipes/relation-subqueries.html
https://vincit.github.io/objection.js/api/query-builder/eager-methods.html#withgraphfetched
https://vincit.github.io/objection.js/api/query-builder/eager-methods.html#withgraphjoined
Your example above worked well. I was missing the ref in my implementation. So I'll have to give the withGraphedJoin another try.

Thanks. I actually did look through the documentation quite thoroughly. I tried an approach with all these before posting:
https://vincit.github.io/objection.js/recipes/subqueries.html
https://vincit.github.io/objection.js/recipes/relation-subqueries.html
https://vincit.github.io/objection.js/api/query-builder/eager-methods.html#withgraphfetched
https://vincit.github.io/objection.js/api/query-builder/eager-methods.html#withgraphjoined
Your example above worked well. I was missing the ref in my implementation. So I'll have to give the withGraphedJoin another try.


Support relative page header links

Relative page links  like
https://github.com/tajmone/pandoc-goodies/tree/master/templates/html5/github#primer-css
or
https://github.com/tajmone/pandoc-goodies#gnu-general-public-license
would be awesome.

I'm not sure I understand, where are these supposed be available? in the GitHub previews of the documentation?

You mean like this?

https://htmlpreview.github.io/?https://github.com/tajmone/pandoc-goodies/blob/master/templates/html5/github/GitHub-Template-Preview.html#githubs-primer-css-features

Exactly.
I use a local website generated with pandoc. Atleast file links like
file:///home/user/site/index.html#Notes do jump and links like
file:///home/user/site/exercises#Exercise%20II..html do not work at all.

Pandoc has some options to control how the headings anchor IDs  in the final document are generated, and these will always be linkable. I don't remember the various options out of my head (I'll look them up), but you should be able to look at the generated HTML source and extract those anchors.
You should also be careful about case-sensitiveness, for usually anchors are converted to lowercase.
Let me check Pandoc docs and I'll be back with some options discussion...

http://pandoc.org/MANUAL.html#extension-auto_identifiers
http://pandoc.org/MANUAL.html#heading-identifiers

Thanks I'll look into it!

There are various options regarding the algorithms used to produce a valid anchor.
What I find strange is that it doesn't mention the HTML output for those extensions, but I know as a fact that it supports it.
If you tell pandoc to autogenerate a TOC for the html docs/web-pages you can easily test how these links work.
Let me know if you managed to solve it.

Hi, thanks for your help again!
I managed to use the header identifiers. I initally used vimwikis nameing convention, which does not work with pandoc. Maybe I will look into writing a converter, for now I just look the identifer up or just write simpler headers :laughing:
The .html problem was fixed by writing a filter. My is
sed 's/\(jpg\|pdf\).html/\1/g' | sed -e 's/\(href=".*\)\.html/\1/g'


request can not finished for big response

But curl can fetch data.

If I read this right that you are talking about Swagger UI cannot handle big payloads then the issue is not in utoipa but in the Swagger UI itself. Moreover the utoipa is only a metadata generative library and has nothing to do with networking.
Perhaps looking for solutions from Swagger UI related forums first and then if there is a fix in some version of Swagger UI which is newer than the one utoipa has, then come  back with PR that updates the Swagger UI or with the request to do so.

Closing as non actionable.


1.21.2 port?

This will not get a ‘port’ as the tooltip renderer has been completly rewritten, such that core shaders are no longer required. A new version will be made when time allows.


typo on suggest for leafs/lessphp

I think it should be less.php

The packagist package appears to be leafo/leasphp though.

oh wonder if i was thinking of oyejorge/less.php which I had used in the past (and always thought the *.php was odd...


GPU extension not installed while it's installed

I just submitted issue #1337 without realizing this issue already existed. It has a bit more detail. Here's a set of screenshots that includes the Extension Manager showing that the extension is installed:

Thanks Hailey

@LittleLittleCloud The issue seems to be that we can't load the GPU service in AutoMLServiceFactory.CreateAutoMLServiceAsync. The failure is "Could not load file or assembly 'Microsoft.ML.ModelBuilder.AutoMLService.dll' or one of its dependencies. The system cannot find the file specified. (ErrorKind: Error HResult: 80131500)"
I see that you changed the AutoMLService to an executable in 869. Is this the problem? Do we just need to change it to .exe here? I've tried it locally and it can't find the .exe either. Am I on the right track?

Looks like the right track to me!

Might be!

I changed the gpu service hub config... it didn't work but I just realized that I changed the root path too. Trying again now.

@LittleLittleCloud I tried a few different combos and none worked...

I also tried ...
"assemblyPath": "Microsoft.ML.ModelBuilder.AutoMLService.exe",
"fullClassName": "Microsoft.ML.ModelBuilder.AutoMLService.ServiceFactory.AutoMLService"
Is there another place I need to change something? Do you remember from your previous work? Or was it just the exe change?

Any updates on the fix? @beccamc


Remove ::Mixin from Synopsis

Why :
When we copy and paste the class definition of the synopsis section, it shows a warning message
[DEPRECATED] Use Dry::Initializer instead of its alias Dry::Initializer::Mixin. The later will be removed in v2.1.0

Thank you!


how you do  histogram matching

Hi：
In your code, I did not find where you apply histogram matching.Could you tell me how you do histogram matching?

Yes, I have the same question. Can you please tell how you are doing histogram matching?

Hi:
The artical says how to use HM.You can check it.
------------------ 原始邮件 ------------------
发件人:                                                                                "JunMa11/HM_DataAug"                                                                                @.>;
发送时间: 2021年3月16日(星期二) 凌晨4:04
@.>;
<EMAIL_ADDRESS>主题: Re: [JunMa11/HM_DataAug] how you do  histogram matching (#2)
Yes, I have the same question. Can you please tell how you are doing histogram matching?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Sorry I am a beginner. How do I train from scratch? What is your command line during training? （python run_training.py .......???......）

Hello, thank you for sharing your code, however, I am also unable to find the code for histogram matching, would you be able to upload that code as well?

I also have the same question...


Issue #SB-20599 fix: Publish pipeline issue fix

@PradyumnaNagendra @amitpriyadarshi @maheshkumargangula please add the test cases before it is pushed to prod and merging with 3.3


Add jQuery 3.0.0 compat layer

In this PR:

$#bind and $#unbind are deprecated in jQuery 3, so I added on and off aliases to MicroEvent#bind and #unbind for consistency sake

More details:
https://github.com/jquery/jquery-migrate/blob/master/warnings.md#jqmigrate-jqueryfnbind-is-deprecated

I don't think you've done the aliases properly

Indeed, @spmason! Thanks for pointing that out. Funny enough the tests were passing... I took the opportunity to add a deprecation warning, assuming we want to eventually sync up with jQuery 3 anyway...

@grahamscott / @spmason rebased!

Why is this not updated to on? https://github.com/BrandwatchLtd/frontend/blob/integration/public/src/extensions/signals/filtersPopup/CategoryFilterPopupView.js#L83

Went through all the bind unbind things in the code to see if all were caught. Looks like it. I'd say this is a minor version release as discussed as we only deprecate things before eventually they will be removed.


ERC20-Balance-of-Percent for Factor Weighted Strategy

Fixes # .
Changes proposed in this pull request:

Balance Weighted Strategy based on % as discussed on Discord
Not quite familiar with TS, hacked some code together, please verify.

Since we have an urgent vote to put up, we are delaying this PR until the new vote gets over.

Closing this PR, i've added the strategy in another commit here: https://github.com/bonustrack/snapshot.js/commit/75851ba89c9e61e8549b59e296b33a29bf58aff0


Fix typo in AMM ledger_entry API example

The amm_info request was missing a comma - this adds it back :)
(Confirmed this new transaction was well-formed using the Websocket API tool)

(Feel free to just merge this in if it looks good and has enough approvals - I may be slow to respond since I don't have notifications for this repo)


Report from publicapis.dev - Numbers

Name: Numbers
URL: http://numbersapi.com
Category: Science & Math
Issue: Broken link
This report was sent from publicapis.dev.

It seems to be working.


Records not showing on page

The records are not showing on page, but if a search nothing and press Enter all records show.
Why?

I solved the problem.
The error was put primary column and also add column for the same db column.


Solution to Indentation Issue while auto fixing files

Current Issue with auto fixing yaml files :
After applying the security changes,

The original indentation is ignored and uniform indentation is applied across the file.
Empty lines are excluded too.

Consequences of this issue

After fixing files, some test cases might fail due to the changes in indentation.
The fixed YAML files will not be consistent with the rest of the repository.
When Kubescape creates a PR of fixes using GitHub Actions, security changes could not be clearly presented.

Prerequisite knowledge to understand this PR

The decoded YAML file is represented in a tree-like structure by yaml library.
Node types in the tree structure:

Sequence Node : List (Type 2)
Mapping Node : Group of Key-Value Pairs (Type 4)
Scalar Node (Type 8)

Scalar Node will not have any child nodes.
Mapping and Sequence Nodes should have child nodes.
Mapping Node will have even number of children. The odd child is key and even child is value.

Examples:
Example 1 &2

Example 3 & 4

How fix-command works in the background

Decode the original YAML file using yaml package and generate the tree structure of YAML
Make necessary changes to the tree representation by inserting, removing or replacing nodes in the tree using yqlib package.
Encode the fixed tree representation using yaml package.

Root Cause of the issue:

The issue is with the encoder yqlib is using. The presentation details are adjusted on purpose by the encoder to bring uniformity.  For more details, visit this link

No straightforward solution
The straightforward solution could be to find another encoder which doesn't alter the presentation details. Unfortunately, I couldn't find any.
Solution

In essence, the solution is to determine where to apply changes(Line numbers) and what changes to apply(Content of Lines) and apply those changes to the existing YAML file.
First, we get a tree representation of the YAML node with all the fixes done using the yqlib package. Then, we use this tree to identify the changes.

Change Types:
To make changes to any tree structure, there are three options:

Insert new node/s
Remove existing node/s
Replace existing node/s

Note: Rearranging the tree is another option. But, that could be represented as a sequence of remove and insert operations.
How to Identify change types:
Insertion Scenario:

yqlib package sets the Line and Column number of inserted nodes to 0

Removal and Replacement scenario:

we cannot identify the removed nodes just by using the fixed tree of YAML. To identify removed and replaced nodes, we need to compare the fixed tree with the original tree.
Replaced nodes will have same Line and Column but different content.
Removed node will be found in the original tree but not in the fixed tree.

How to deal with change types:
Insertion scenario:

Determine the line to insert. It is the Line before the Line number of the next node in the order.
construct the content to insert(Including indentation with respect to the base) using yaml.Encode

Removal Scenario:

Determine the beginning line to remove. It is the Line number of the Removed Node.
Determine the end Line to remove. It is the Line before the Line number of the next node in the order excluding empty lines and comment lines.

Replacement Scenario:

This is a combination of removal and insertion. Remove the node in the original tree and Insert the node in the fixed tree.

How to Compare Original Tree & Fixed Tree

Comparing two tree structures is way more trickier than comparing flat structures like lists.
It would be simple if we could flatten the tree structure  without losing the essence of the tree structure.
Depth-first search (DFS) traversal is the perfect choice for this scenario.
Traverse through the tree, store Parent Node first and then the contents of each child(including their children) in order in a list. For more info on DFS traversal, visit this link
Since this is the order in which nodes are encoded, the Line numbers will be increasing order.
We can determine the next node in order which is crucial for determining line numbers to add and remove.

@vladklokun, Thank you as always for the detailed review.


(Aborted (core dumped)) - Check failed: GetOpGradFactory()->insert({op, func}).second Duplicated gradient for MapAccumulate

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):  Stock example script.
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): CentOS Linux release 7.6.1810 (Core)
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: On my laptop,
TensorFlow installed from (source or binary): From source for c++ application.
TensorFlow version (use command below): v1.8.0
Python version: 2.7
Bazel version (if compiling from source): 0.15.1
GCC/Compiler version (if compiling from source): g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)
CUDA/cuDNN version: CPU only
GPU model and memory: None.

Describe the current behavior
I have a Standalone c++ build process for ubuntu and it works fine with my own code as well as with the c++ example code on tensorflow.
But when i run the same code on CentOS platform. I get following runtime error message and the executable core dumps:
2019-07-11 10:20:42.027023: F tensorflow/core/framework/function.cc:1329] Check failed: GetOpGradFactory()->insert({op, func}).second Duplicated gradient for MapAccumulate
Aborted (core dumped)

My compilation command is as:
g++ -std=gnu++11 -Wl,-rpath='$ORIGIN/lib' -fPIC -Iinclude -Llib  example.cc -ltensorflow_cc -ltensorflow_framework   -o example

Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
Please follow the steps provided on blog.

@milinddeore Can you please confirm whether you are getting runtime error with your code or c++ code on tensorflow ,with CentOS platform.Thanks!

@ravikyram I got this issues using both my code as well as with c++ code on Tensorflow.

@milinddeore Sorry for missing this issue. Can you please check with most recent version of TF like TF1.15.2 or TF2.2 (preferred). Thanks!

@jvishnuvardhan Thanks for your reply. I'm also facing this issue on TF1.12.0, when I'm trying to include a deps of //tensorflow/core/kernels:lookup. Do you have any idea how to avoid this core issue?

@icoffeebeans can you please check with latest version and let us know? Thanks!

1.12 is not supported.

I am closing this issue as TF1.12 is not supported. Please use recent stable versions. Thanks!

the same coredump as @milinddeore


NullPointerException tagging a VM

ISSUE TYPE

Bug Report

COMPONENT NAME
API

CLOUDSTACK VERSION
<IP_ADDRESS>

CONFIGURATION
N/A
OS / ENVIRONMENT
N/A
SUMMARY
When attempting to tag a VM, we're getting a NullPointerException in TaggedResourceManagerImpl. This NPE is happening in informStoragePoolForVmTags when the volume does not have a Pool ID associated with it. This issue is blocking our upgrade to <IP_ADDRESS>.
2022-10-27 13:51:55,695 ERROR [c.c.a.ApiServer] (qtp1026055550-5193:ctx-3abf03c9 ctx-b53aa077 ctx-cca24aa6) (logid:847d7482) unhandled exception executing api command: [Ljava.lang.String;@7e515dd1
java.lang.NullPointerException
	at com.cloud.tags.TaggedResourceManagerImpl.informStoragePoolForVmTags(TaggedResourceManagerImpl.java:321)
	at com.cloud.tags.TaggedResourceManagerImpl$1.doInTransactionWithoutResult(TaggedResourceManagerImpl.java:225)

The issue appears to be that volume.getPoolId() returns a Long with a null value and dataStoreMgr.getDataStore(long storeId, DataStoreRole role) accepts a long (which cannot be null).
https://github.com/apache/cloudstack/blob/main/server/src/main/java/com/cloud/tags/TaggedResourceManagerImpl.java#L321.
Adding a null check for volume.getPoolId() before calling dataStoreMgr.getDataStore() should take care of it.
STEPS TO REPRODUCE
Tag a VM with a volume which does not have a pool id.

EXPECTED RESULTS
VM is tagged
ACTUAL RESULTS
NPE when tagging

Fixed in https://github.com/apache/cloudstack/pull/6879


mean init: doesn't find 'git'

root@850a7ee94c4b:~# mean-init
? What would you name your mean app? mean
? Do you prefer grunt or gulp as a taskrunner? grunt
    Prerequisite not installed: git
root@850a7ee94c4b:~# which git
/usr/bin/git
root@850a7ee94c4b:~# echo $PATH | grep '/usr/bin'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin
root@850a7ee94c4b:~# mean -v
0.9.8
root@850a7ee94c4b:~#

Hi Sergei,
Mean was changed to explicitly avoid being running as root.
The only thig you need to install as root (With sudo) is mean-cli, gulp and
bower.
Everytime you run mean using gulp (or node server.js) you should be doing
so with normal non-root permissions.
You can run chown -R whoami ~/.npm and on your mean installation (As
root) to fix the permissions.
Good luck
Lior
On Mon, Apr 6, 2015 at 9:20 PM, Sergei Fedorenko<EMAIL_ADDRESS>wrote:

I'm also running script as root and have similar problem ((
root@wordshome:/opt# mean init wordshome
? What would you name your mean app? wordshome
Installation of mean should not be done as root! bailing out
/usr/local/lib/node_modules/mean-cli/node_modules/inquirer/node_modules/rx/dist/rx.js:580
throw e;
^
RUNNING AS ROOT
I have remote ubuntu 14.04
@fyockm https://github.com/fyockm Thank you for support!
—
Reply to this email directly or view it on GitHub
https://github.com/linnovate/mean-cli/issues/69#issuecomment-90183480.

--
Lior Kesos - http://www.linnovate.net
Linnovate - Community Infrastructure Care
mail<EMAIL_ADDRESS>office: +972 722500881
cell: +972 524305252
skype: liorkesos

@liorkesos  Thank you!
I created new user on server but instead "chown -R whoami ~/.npm" I simply deleted ~/.npm
"rm -rf  ~/.npm"
I can run Mean.io on remote ubuntu! All OK! ))) Thank You!!
Several moments for my situation
1 - when I run mean project I got only small warning from console

[Error: /home/admin/wordshome-com/node_modules/mongoose/node_modules/mongodb/node_modules/bson/build/Release/bson.node: invalid ELF header]
js-bson: Failed to load c++ bson extension, using pure JS version
2 - I not found full article with installation mean.io on remote Ubuntu with advices about root user and .etc
Same article will be fine for new users


Update logging with latest generator and GAX.

@garrettjonesgoogle @michaelbausor

Coverage remained the same at 82.357% when pulling<PHONE_NUMBER>4ac9800c7e539fd43824d267dfa6e5 on shinfan:logging-alpha into 1ea7a7774c73401b53278a99e285a20ee7e992c2 on GoogleCloudPlatform:logging-alpha.

We should also add gcloud-java-logging to the parent pom so that tests are triggered.

I have updated the parent pom and addressed all the comments. PTAL.

Coverage remained the same at 82.357% when pulling 2c9b46e64f53c190f7b6bf1032c2c37d3421b533 on shinfan:logging-alpha into 1ea7a7774c73401b53278a99e285a20ee7e992c2 on GoogleCloudPlatform:logging-alpha.

I believe that this PR should also remove gax-related directories (see issue #939).
For what concerns LocalLoggingImpl and LocalLoggingHelper they should live in the com.google.cloud.logging.testing package rather than com.google.cloud.logging.spi.v2.testing. However LocalLoggingImpl seems a rather simple implementation which is missing several features (support for Config and Metrics sub-services, for instance). I am not sure that we should expose it to users in its current state. @aozarov thoughts?
Are there plans to make LocalLoggingImpl a more complete stub or are you waiting for the emulator (see issue #472)? Is there an ETA for the emulator? /cc @jgeewax
Also just let me remind that there are a bunch of logging-related issues that resulted from previous Arie's thorough reviews and that still need to be addressed. If you believe that some of them have already been fixed feel free to close them.

Coverage remained the same at 82.357% when pulling 1fe17bb38c1336184d882b3eec0b57be09fad546 on shinfan:logging-alpha into 1ea7a7774c73401b53278a99e285a20ee7e992c2 on GoogleCloudPlatform:logging-alpha.

PTAL
I have removed the gax related files and thanks for the reminders. For the LocalLoggingImpl I believe we are waiting for a more scalable testing plan (e.g. emulator but I am sure about the ETA at this point)
Now this PR addressed the following issues:
https://github.com/GoogleCloudPlatform/gcloud-java/issues/943
https://github.com/GoogleCloudPlatform/gcloud-java/issues/771
https://github.com/GoogleCloudPlatform/gcloud-java/issues/939


Selections with COISS give large number of thumbnails

Select the first COISS image:
https://tools.pds-rings.seti.org/opus#/instrumentid=Cassini+ISS&view=browse&browse=gallery&colls_browse=gallery&page=1&gallery_data_viewer=true&limit=100&order=time1&cols=ringobsid,planet,target,phase1,phase2,time1,time2&widgets=instrumentid,planet,target&widgets2=&detail=
Go to the Selections tab. A large number of thumbnails are displayed.

No, I only see one thumbnail.  -Matt
On Mar 7, 2018, at 4:57 PM, Robert French<EMAIL_ADDRESS>wrote:

Select the first COISS image:
https://tools.pds-rings.seti.org/opus#/instrumentid=Cassini+ISS&view=browse&browse=gallery&colls_browse=gallery&page=1&gallery_data_viewer=true&limit=100&order=time1&cols=ringobsid,planet,target,phase1,phase2,time1,time2&widgets=instrumentid,planet,target&widgets2=&detail= https://tools.pds-rings.seti.org/opus#/instrumentid=Cassini+ISS&view=browse&browse=gallery&colls_browse=gallery&page=1&gallery_data_viewer=true&limit=100&order=time1&cols=ringobsid,planet,target,phase1,phase2,time1,time2&widgets=instrumentid,planet,target&widgets2=&detail=
Go to the Selections tab. A large number of thumbnails are displayed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/SETI/pds-opus/issues/279, or mute the thread https://github.com/notifications/unsubscribe-auth/AR3CBt4sBN9P946WDa-Ozsax3PZaxaZoks5tcIIDgaJpZM4Sh74h.

Matthew S. Tiscareno, Senior Research Scientist
SETI Institute, 189 Bernardo Avenue #200, Mountain View CA 94043

Sometimes it's a little hard to reproduce. You have to select and deselect things a few times and hop between the Selections tab and the Browse tab. Here are some examples of what I see:

Deferred waiting for a complete rewrite of Selections.

This may not happen anymore with the various fixes to the gallery view.

This seems to be fixed. Will close for now.


imageUrl()/image() used with lorempixel generating wrong image url with $randomie = false param

Currently, call imageUrl() method with 4th param (randomize) set to false generate url as below:
https://lorempixel.com/196/196/people/?36161
"Randomize" function working wrong.
According to current info on https://lorempixel.com/ for get static image number should be in range 1-10 and need to be placed in url.
call example:
$this->faker->imageUrl(196, 196, 'people', false);

current result:
https://lorempixel.com/196/196/people/

desired return:
https://lorempixel.com/196/196/people/[1-10]

ex:
https://lorempixel.com/196/196/people/8

In addition, static number in url should be places before word param value.

Fixing PR: https://github.com/fzaninotto/Faker/pull/1785


README.md does not show how to load the HTMLtoDOCX function

The README.md currently contains:

Installation
Use the npm to install foobar.
npm install html-to-docx

Usage
await HTMLtoDOCX(htmlString, headerHTMLString, documentOptions, footerHTMLString)

But this has two problems. First, the package isn't called foobar ("Use npm to install html-to-docx"), but more importantly, it's missing the code that shows how to get HTMLtoDOCX: is it import { HTMLtoDOCX } from "html-to-docx"? Is it import HTMLtoDOCX from "html-to-docx"? Is it something else?
It would be good to update the README.md to address this omission.

Hi @Pomax
You can see how to use the library in React in the example.
https://github.com/privateOmega/html-to-docx/blob/master/example/react-example/src/App.js#L5

I know, this issue is to get that information surfaced in the README.md instead, because that's where people expect to find it =)


Preserve newlines in text

This will not change anything for current users, but exposes a new option: preserveNewlines, which causes newlines in text to be retained by the output.

Thanks for your contribution :)
Could you add a unittest and some documentation for the README.md please.

Will have updated shortly. Thank you for the quick turnaround on feedback :)

Alright sir, readme documentation has been expanded, unit test is written, and code corrections have been made.

Also, rebased down to a single commit, to avoid polluting your commit history unnecessarily.

Thank you very much :) Will be released in version 1.6.0.


Fix ulimit for Xenial

set systemd default open file limit and reloads it
set the ulimit for monit and its parent processes in pre-start script
remove deprecated trusty limits.conf copying

Co-authored-by: Kai Hofstetter<EMAIL_ADDRESS>

Some more interesting findings:

On trusty we noticed that during update instance the monit process doesn't get new PIDs (e.g. being restarted) for pre-start and start and simple prlimit adjustment sets the new limit settings correctly for the time being. But if monit is killed it gets the fall-back settings from parent processes, e.g. systemd->runsvdir->runsv. (this will be fixed with this proposal)
On xenial during 'update instance' the monit process is recreated for pre-start and start and it loses the original setting set by prlimit. That is why we decided to set the limits to all of its parents in process chain. The systemd gets it via systemctl daemon-reload from /etc/systemd/system.conf for its children, in case of runsvdir, runsv or monit get killed.
Open question: Should we consider setting the limits on parent processes only if their NOFILE limits are lesser?

We will implement it in another fork to os-conf-release:
https://github.com/s4heid/os-conf-release/tree/add-limits-job
Closing this PR.


cmd/go: get fails to provide sensible error message for private vcs repos

What did you do?
I have a project that imports a private git repository. When setting it up with vgo get or similar commands, the resolving process will stop abruptly, not writing anything to the disk.
The command succeeds if git credentials are properly set up (*_ASKPASS, global config or the repo is already cloned with the right config, etc.).
What did you expect to see?
An error message, or some indication of what went wrong
What did you see instead?
No error message, just an exit code 1.
System details
go version go1.10.3 linux/amd64 vgo:2018-02-20.1
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/exploser/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/exploser/go"
GORACE=""
GOROOT="/usr/lib/go"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build534162883=/tmp/go-build -gno-record-gcc-switches"
GOROOT/bin/go version: go version go1.10.3 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.10.3
uname -sr: Linux 4.16.14-2-MANJARO
LSB Version:	n/a
Distributor ID:	ManjaroLinux
Description:	Manjaro Linux
Release:	17.1.10
Codename:	Hakoila
/usr/lib/libc.so.6: GNU C Library (GNU libc) stable release version 2.27.
gdb --version: GNU gdb (GDB) 8.1

I was playing around with modules and ran into an error like this. Here is the error I got below:
go: converting vendor/manifest: stat github.com/foo/bar@1234sha: git fetch -f --depth=1 origin 1234sha:refs/dummy in /Users/vito-c/code/go/src/mod/cache/vcs/456sha: exit status 128:
	fatal: could not read Username for 'https://github.com': terminal prompts disabled

This also failed for me while running 1.11beta2, not sure if it's related.
$ go1.11beta2 build
go: finding github.com/org/repo v6.9.0
go: errors parsing go.mod:
/foo/bar/go.mod:31: invalid module version "v6.9.0": unknown revision v6.9.0

Just to confirm @wayneashleyberry you're expecting that to succeed because a git clone for, say, github.com/overhq/over-stories-api succeeds?
Are you using ssh-based authentication here or some other?

@myitcv hi 👋

you're expecting that to succeed because a git clone for, say, github.com/overhq/over-stories-api succeeds?

absolutely correct

ssh-based authentication here or some other?

ssh auth
cat ~/.ssh/config
Host *
 AddKeysToAgent yes
 UseKeychain yes
 IdentityFile ~/.ssh/id_rsa

Hi indeed @wayneashleyberry!
Do you also have an insteadOf config for git? Something like url.git@github.com:.insteadof=https://github.com/?

nope, what I pasted above is the only config I use for github

Just read https://golang.org/doc/faq#git_https and that fixes things for me! Thanks for pointing me in the right direction @myitcv

👍 @wayneashleyberry - we could/should also add to that FAQ section details of how to use keychains (on any platform).

So just to summarise what I think the action is here, we need any of the go commands that end up doing anything with a VCS remote (via the corresponding tool), e.g. git ls-remote -q https://github.com/overhq/over-stories-api, to print to stderr the output  from the tool in case of a non-zero exit code.
go get is not currently silent (I'll update the issue title) it's just that its output is misleading.
So, taking the example of github.com/overhq/over-stories-api, the current behaviour is:
$ go get github.com/overhq/over-stories-api
go get github.com/overhq/over-stories-api: cannot find module providing package github.com/overhq/over-stories-api

We should instead see something like:
$ go get github.com/overhq/over-stories-api
remote: Repository not found.
fatal: repository 'https://github.com/overhq/over-stories-api/' not found

@bradfitz tells me that the "silent exit 1" fix fixed private repos that worked with "old go get". We can address even better support in Go 1.12.

In non-module mode I see:
$ go get github.com/overhq/over-stories-api
# cd .; git clone https://github.com/overhq/over-stories-api /Users/rsc/src/github.com/overhq/over-stories-api
Cloning into '/Users/rsc/src/github.com/overhq/over-stories-api'...
fatal: could not read Username for 'https://github.com': terminal prompts disabled
package github.com/overhq/over-stories-api: exit status 128
$

In module mode I see:
$ go get github.com/overhq/over-stories-api
go get github.com/overhq/over-stories-api: git ls-remote -q origin in /Users/rsc/pkg/mod/cache/vcs/35b63ced1d50599254b07b2a3912fa8f48350519db24e14283e93ce370969e20: exit status 128:
	fatal: could not read Username for 'https://github.com': terminal prompts disabled
$

It's possible that we should recognize this failure (maybe 'terminal prompts disabled') and print a pointer to https://golang.org/doc/faq#git_https.

This was a release blocker for Go 1.11 when it was a silent exit, and we fixed that. The extra doc pointer does not block Go 1.12

Commenting here since I just opened a duplicate.
Could the sorts of issues we see in this ticket be due in part to how the current code is not handlin the r.refsErr after line 298 in the below snippet?
https://github.com/golang/go/blob/f1980efb92c011eab71aa61b68ccf58d845d1de7/src/cmd/go/internal/modfetch/codehost/git.go#L298-L336
It looks like that field is being set in loadRefs here
https://github.com/golang/go/blob/f1980efb92c011eab71aa61b68ccf58d845d1de7/src/cmd/go/internal/modfetch/codehost/git.go#L179-L198
So ISTM that we should check if it was set after every call to r.loadRefs. Of course, that may only be part of the problem. I'm open to opening a PR to resolve the above if it would be productive.

Commenting here since I just opened a duplicate.
Could the sorts of issues we see in this ticket be due in part to how the current code is not handlin the r.refsErr after line 298 in the below snippet?
https://github.com/golang/go/blob/f1980efb92c011eab71aa61b68ccf58d845d1de7/src/cmd/go/internal/modfetch/codehost/git.go#L298-L336
It looks like that field is being set in loadRefs here
https://github.com/golang/go/blob/f1980efb92c011eab71aa61b68ccf58d845d1de7/src/cmd/go/internal/modfetch/codehost/git.go#L179-L198
So ISTM that we should check if it was set after every call to r.loadRefs. Of course, that may only be part of the problem. I'm open to opening a PR to resolve the above if it would be productive.


2.1.0 Robotic Hand / Construct Digits issue

Construct Digits (BLD_BUI_HAND): snap point incorrectly placed, hand oriented opposite to placement in game; in other words, hand placed facing palm-up in game results in palm-down orientation in Blender, and vice versa.

Try this: https://github.com/djmonkeyuk/nms-base-builder/releases/tag/v2.1.1


OCI360 docker install

Hi,#Rodrigo Jorge
Please help with this , i am trying install OCI36 in Oracle linux 7.9 and linux 8, i have below issue after running some time.
where as python is already installed

--> Finished Dependency Resolution
Error: Package: python36-dateparser-1.0.0-1.0.1.el7.noarch (ol7_developer)
Requires: python36-regex > 2019.02.19
Error: Package: python36-dateparser-1.0.0-1.0.1.el7.noarch (ol7_developer)
Requires: python36-tzlocal
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
+++ trap_err 33
+++ echo 'Error on line 33 of "setup_oci360.sh".'
Error on line 33 of "setup_oci360.sh".
+++ exit 1
Error while creating the oci360-tool container. Check docker logs.

Regards
Srini

Hi Srini. I will check it out and get back soon.

Hi Srini. I will check it out and get back soon.

Sure thanks much Jorge, will wait for your reply.
this option where i am trying to install using Docker(https://github.com/dbarj/oci360/wiki/Install-OCI360) , stopped at after running around 20 min to 30 min, below is the issue. even after installing those packages package: python36-dateparser-1.0.0-1.0.1.el7.noarch & Package: python36-dateparser-1.0.0-1.0.1.el7.noarch, does not work.

--> Processing Dependency: python36-tzlocal for package: python36-dateparser-1.0.0-1.0.1.el7.noarch
---> Package python36-ply.noarch 0:3.9-2.0.1.el7 will be installed
---> Package python36-pymeeus.noarch 0:0.3.6-2.0.1.el7 will be installed
--> Finished Dependency Resolution
Error: Package: python36-dateparser-1.0.0-1.0.1.el7.noarch (ol7_developer)
Requires: python36-regex > 2019.02.19
Error: Package: python36-dateparser-1.0.0-1.0.1.el7.noarch (ol7_developer)
Requires: python36-tzlocal
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
+++ trap_err 33
+++ echo 'Error on line 33 of "setup_oci360.sh".'
Error on line 33 of "setup_oci360.sh".
+++ exit 1
Error while creating the oci360-tool container. Check docker logs

Thank you
Srini

Hi Sri. I've updated to the next release and fixed this issue. Please let me know if you still face any problem there.

Thanks much for your reply Rodrigo Jorge.
That went fine and success till the end.
but some where i see error like no such container : oci360-tool not sure if this is expected error
and i have other issue while test oci-cli using root user or oci360 user from the instance ,
more details below
1st issue ) ****************

cd -
/root
docker stop oci360-tool
Error response from daemon: No such container: oci360-tool
true
docker rm oci360-tool
Error: No such container: oci360-tool
true
docker run --name oci360-tool --restart unless-stopped -d -p 1521:1521 -e ORACLE_CHARACTERSET=AL32UTF8 -e OCI360_BRANCH=master -e OCI360_UID=54322 -v /u01/oci360_database/oradata:/opt/oracle/oradata -v /u01/oci360_database/setup:/opt/oracle/scripts/setup -v /u01:/u01 oracle/database:18.4.0-xe
09e59cea07001b31f2c15e53a91ad42cdc4ce97dc105b7489ed5ccc799713f84

I have proceeded with next steps

Setup oci-cli - in this step i went with Instance_principal method
have updated vi /u01/.oci/config with my tenancy OCID id : and my region name
then i have ran below command login to my OCI web-console with account. Open the Cloud Shell and run , hopefully my account is admin account.
bash -c "$(curl -L https://raw.githubusercontent.com/dbarj/oci360/master/container/oci360_oci_cli_access.sh)"
result :
OCI360 Instance OCID: given my created oci360 instance ocid
Dynamic Group Name for OCI360 [OCI360_DG]:
Policy Name for OCI360 [OCI360_Policy]:
Script finished without any error

2nd issue:
so now when i test oci-cli with below command running from my instance with root/oci360 user , have the same issue
issue :
[root@oci360-19358 ~]# docker exec -it --user oci360 oci360-tool bash -c 'export OCI_CLI_AUTH=instance_principal; cd /tmp/; /u01/oci360_tool/app/sh/oci_json_export.sh Comp-Instances'
oci-cli not able to run "oci --cli-rc-file /dev/null iam region-subscription list". Please check error:
HTTPConnectionPool(host='<IP_ADDRESS>', port=80): Max retries exceeded with url: /opc/v2/identity/cert.pem (Caused by NewConnectionError('<oci._vendor.urllib3.connection.HTTPConnection object at 0x7f134b548be0>: Failed to establish a new connection: [Errno 113] No route to host',))
[root@oci360-19358 ~]#

Regarding the 1st container error, you can safely ignore it. When you run the setup script, it will drop/remove the previous containers before creating new ones. As the previous execution failed, you won't have any do drop/remove. This line of code was basically inserted if you want to redeploy/upgrade the oci360.
Regarding the "No route to host", this seems to be related with your compute instance or container not having route/egress rule/etc to the internal OCI REST API. Try to ping from the container and from the host and see if it works on both:
[root@rj-oci360-259 ~]# ping <IP_ADDRESS>
[root@rj-oci360-259 ~]# docker exec -it --user oci360 oci360-tool bash
[oci360@94423ba89f5e /]$ ping <IP_ADDRESS>
Regards,
RJ

Thank you RJ , its worked.
but when i access web page using server ip https://x.x.x.x./oci360/ ,
first page showing as :
Index of /oci360
Parent Directory
and then when i click on parent directory  it saying below
It works!  - thats it.
so how can i get full GUI webpage page to see all my OCI resources.
however i dont find any zip file generated at /u01/oci360_tool/out
Thank you
Srini

Hey man. Now you need to wait for a full execution. Add the crontab entry and wait or force a manual execution (check the wiki steps). The logs will be available in /u01/oci360_tool/log/run.*.log


Avoid multiple copies of bb.js being loaded

Today aztec.js depends on both types and circuits.js, and types also depends on circuits.js. It can happen that npm or yarn decides to install a copy of circuits.js within aztec.js and another within types, in case there's already a circuits.js in the root of node_modules with a different version. This has led to serialisation issues (see #1826), and can lead to multiple copies of the circuits wasm being loaded, which can have an impact on memory usage.
We should explore whether removing the dependency from aztec.js to circuits.js (and instead having types re-export everything that's needed) would solve the issue. This also requires analysing all other dependencies to circuits.js.

Updating the issue since this now may happen with foundation and circuits.js both importing bb.js


Log in button in the login view

The log in button in the login view is not displayed correctly. The button could be white instead.

That's because the button is disabled until you enter your user and password.
Doesn't it turn white once you enter them?

It became white when I've typed my username and password. Thank you!


Expansion of env in scripts?

Features Description
Make it possible to expand variables in script:

Expecting to return text: something.
Rationale
My makefiles usually look like:
...

# Build overrides
BUILD ?= "$(PWD)/build/"
VENDOR ?= "$(PWD)/vendor/"
SRC_DIR ?= "$(PWD)/src"
CACHE_DIR ?= "$(HOME)/.cache"

...

#& Build with linux kernel as backend
build-linux-standalone: vendor-linux
	@ [ -d "$(BUILD)" ] || "$(MKDIR)" "$(BUILD)"
	@ [ -d "$(BUILD)/$(PROJECT_NAME)/linux" ] || "$(MKDIR)" "$(BUILD)/$(PROJECT_NAME)/linux"
	@ scripts/deployment/filesystem.sh "$(BUILD)/$(PROJECT_NAME)/linux/standalone" --fsh3_0
	@ [ -d "$(BUILD)/$(PROJECT_NAME)/linux/standalone/bedrock" ] || "$(CP)" -r "$(SRC_DIR)/slash-bedrock" "$(BUILD)/$(PROJECT_NAME)/linux/standalone/$(PROJECT_NAME)"
	@ [ -s "$(BUILD)/$(PROJECT_NAME)/linux/standalone/run/init" ] || "$(CP)" "$(SRC_DIR)/init/init" "$(BUILD)/$(PROJECT_NAME)/linux/standalone/run/init"
	@ make -C "$(VENDOR)/linux" localmodconfig
	@ make --jobs "$$(nproc || printf 1)"
	@ INSTALL_PATH="$(BUILD)/$(PROJECT_NAME)/linux/standalone" make install

...

Which is one of the main reasons to use makefiles for the repository management for me and thus proposing it to be implemented.
Concern about env expansion in scripts
It was mentioned in https://github.com/sagiegurari/cargo-make/issues/461#issuecomment-701922500

scripts do not support env expansion. i'm not going to do that since that would lead to bugs. for example you wrote a bash where you define a var and than use it. if i expanded before invocation, it has the wrong value. @Sagie Gur-Ari

from my point of view the expansion prior to invocation is expected and to avoid conflicts alike bash expanding variables ${var} this is done on for example makefile as $${var} that escapes the dollar sign.

cargo-make doesn't work with internal variables, it works with env variables.
so setting
[env]
MESSAGE = "something"

Sets an env var. That env var is available in all child processes like ecl scripts and you can pick them up from the env.
replacing that with your request is

going to break backwards compatibility in a really critical way
can cause lots of issues in terms of breaking the scripts - for example what is the variable has "word1 word2"? it might break the script invocation of that line. that doesn't happen in env expansion for commands.
scripts will become less readable as they will be a mix of their respective lang syntax + cargo-make behaviour.

In general, cargo-make is not gnu make.
It doesn't aim to be and the approach is meant to be a lot more declarative and simple.

That works for me, thanks for info


Customise the spring cloud plugin's selector modal.

Since generic configuration methods do not meet demand,customization is required.
Here is the spring cloud plugin selector's  handle json：
{
    "serviceId":"test",
    "gray":false,
    "divideUpstreams":[
        {
            "protocol":"http://",
            "upstreamUrl":"<IP_ADDRESS>:8089",
            "weight":50,
            "status":true,
            "timestamp":0,
            "warmup":50
        }
    ]
}

I'll handle it


Assess whether the new platform is worse than the old

Spoiler: it is not worse.

This change is

@pboothe  is this ready to be reviewed?

Almost. Fixing the last dangling bugs, updating the text in the notebook.  Should be ready by 4pm

Part of https://github.com/m-lab/dev-tracker/issues/440


LRP: Fix loopback in per packet LB mode

This PR fixes cases with the local redirect policy datapath behavior with per-packet LB resulting in loopback. The loopback occurs when the request originates from the node local backend and the local redirect service translation in the bpf program at the LXC interface causes the request to be redirected back to itself. This PR extends the fix in #26144 to work for per-packet LB mode.
Fixes: #30558
Fix loopback with LRP when per-packet LB is used.

@pravk03 thanks for the fix! Please make sure to sign off your commits per the comment from the bot above before marking PRs ready for review.

/test

Smoke tests are just highlighting some style/linting issues. I've kicked off the broader testsuite which should bring back results in the next hour or so. I suggest waiting until all the tests provide feedback before addressing any issues raised by the CI.

Nice work! 🚀 Good to see the BPF tests as well. Please see inline comments from the first pass.

I presume you've tested this e2e on a GKE cluster? Can you add details of the testing along with packet traces showing LRP service LB getting skipped as expected?
Please extend the LRP doc with the GKE Cloud DNS deployment setup - https://docs.cilium.io/en/latest/network/kubernetes/local-redirect-policy/#use-cases.

I verified this on a kind cluster with a same setup as in #30558. We do not have cilium with your changes (#https://github.com/cilium/cilium/pull/26144) available on GKE yet :).

/test

/test

@pravk03 It's good that you've added a BPF unit test, but can we also add an e2e test as there are some minor differences with respect to NETNS cookie retrieval? We already have one - https://github.com/cilium/cilium-cli/blob/main/connectivity/builder/local_redirect_policy.go#L43, and it's currently run with socket-LB enabled. I would suggest running it with socket-LB disabled flag as well. I'm okay if you want to do this in a separate PR, but it'll be great to do this in 1.16 so that we can also mark this PR for backporting to 1.16. Feel free to ping me or @ysksuzuki on cilium slack channels (#sig-datapath or #testing) if you have any questions.

/test

I'm unable to assign the issue to you for some reason. Can you self-assign this issue?

For contributors who are not members of the Cilium organization, they will need to post a comment onto the issue first and then a committer/reviewer should be able to assign them.

Hi @pravk03 , please rebase against the main branch to drop the merge commits, and force push to update the PR here.

Thanks for the reviews and suggestions @aditighag. I have left comments on https://github.com/cilium/cilium/issues/33918 on https://github.com/cilium/cilium/issues/33916 so that you could assign them to me. I havn't been able to spend too much time on adding E2E tests and i will take @ysksuzuki's help with adding them.
@joestringer I have rebased main and updated this PR.

/test

CI got a bit confused, closed and reopened the PR to reset the state.

/test

@pravk03 Sorry, I forgot to mention. You need to push a branch to cilium/cilium repo and open a pull request from there to test a workflow change. I can test it with a separate PR. Could you drop it on this PR?

@pravk03 Sorry, I forgot to mention. You need to push a branch to cilium/cilium repo and open a pull request from there to test a workflow change. I can test it on a separate PR. Could you drop it on this PR?

Thanks @ysksuzuki. Done.

/test

ci-l4lb is consistently failing. I think https://github.com/cilium/cilium/commit/809ce56bdfdeef2dddf49188a577cd56412358c9 fixes this falure. @pravk03 Could you rebase your branch?
time="2024-07-31T12:04:37Z" level=fatal msg="failed to start: daemon creation failed: CRD Identity allocation mode requires k8s to be configured\nfailed to stop: unable to find controller ipcache-inject-labels" subsys=daemon

@ysksuzuki rebased.

/test

I will add e2e test before backporting the PR to v1.16.


Fix some compile errors.

The pull request #1 has diffs to support i18n written by JavaScript. But, the original code set was re-written by TypeScript. It seems that the merging #1 was not enough to migrate JavaScript to TypeScript, therefore, some compile errors occur.
By this pull request, I would like to fix the compile errors. Also, it is necessary to copy the locales directory to the dist directory where compiled files are put, thus, I would like to add the cp command to the build command.

@Fleker Could you review this pull request?

Thanks for making these adjustments.

I modified some lines at f6f53c0:

Change to the setLocale instead of the locale property in the example code: here
Introduce the type definition for the i18n JavaScript library: here
Change to the import from require to load the i18n module: here
Use the type i18n.Replacements instead of the raw type definition {[key: string]: string;}: here

@Fleker @atulep Could you review them again?


Revert vision changes

The recent vision improvements are technically breaking, additionally they unfortunately still have the underlying bug where orientation data is messed up (due to orientation issues in Webots),
They do however fix an issue where markers sometimes can't be seen (which is actually a result of the orientation data being messed up). If we're going to do breakage it would be nice to do it all in one go, once we've fixed the orientation data.
This PR reverts the recent vision changes so we can put out a release with the other changes separately.
Note: I haven't tested this at all -- it's just a revert of the commits I'm aware touched vision stuff, plus a small fix for CI.

I did a few checks of X/Y orientation on a marker in a few orientations, and cartesian distances, it seems like the measurements are the same as pre-vision changes (commit 64d5994) tag: sr2023.3