text:
Documentation Update

Hi Folks!
Looking to open this issue to track some potential changes, wanted to get the go ahead first.

In the README for the consul-cluster module, there is a module definition that references the gruntworks repo path for the consul cluster.
Reference: https://github.com/hashicorp/terraform-google-consul/tree/master/modules/consul-cluster
Error:

Could not download module "consul_cluster" (cluster.tf:1) source code from
"github.com/gruntwork-io/consul-gcp-module?ref=v0.0.1": error downloading
'https://github.com/gruntwork-io/consul-gcp-module.git?ref=v0.0.1':
/usr/bin/git exited with 128: Cloning into
'.terraform/modules/consul_cluster'...
remote: Repository not found.
fatal: repository 'https://github.com/gruntwork-io/consul-gcp-module.git/' not
found

When I try to point the URL to the path to the module, there are now new vars that need to be defined.

The argument "cluster_name" is required, but no definition was found.
The argument "machine_type" is required, but no definition was found.
The argument "gcp_project_id" is required, but no definition was found.
The argument "gcp_region" is required, but no definition was found.
The argument "cluster_size" is required, but no definition was found.

After defining those variables, reinitializing and rerunning cleanly, the following errors come up:

Error: "instance_template": this field cannot be set on .terraform/modules/consul_cluster/modules/consul-cluster/main.tf line 16, in resource "google_compute_region_instance_group_manager" "consul_server":
  16: resource "google_compute_region_instance_group_manager" "consul_server" {

Error: "version": required field is not set on .terraform/modules/consul_cluster/modules/consul-cluster/main.tf line 16, in resource "google_compute_region_instance_group_manager" "consul_server":
  16: resource "google_compute_region_instance_group_manager" "consul_server" {

This is due to consul-cluster module having definitions for both servers and clients.  One recommendation could be to restructure those into two different modules for increased granularity.

The instance_template error in point 3 is fixed in #49

authors: jsosulska nimajalali

repo: hashicorp/terraform-google-consul


text:
Add to Stackage

Having ghcide in Stackage is super useful for company's that base their package set on Stackage. Could it please be added? I'm happy to be the point person and add it myself, if you wish.
Note that adding it right now might not be the best timing since Stackage just rolled to GHC 8.8 and consequently everything is in flux. But in a few weeks it's a definitely useful step.

Sure, happy to add it once the deps are back in nightly.

Everything is now back in nightly.

We’ll need a new release before we can add it to stackage. I was hoping to include a bump to a newer hie-bios release in the next release but given that this seems to be taking longer than I initially thought, I’ll probably make one without that.

Releasing to stackage would be great! Plans on doing that soon?

For the vast majority of users running a docker container is easier, than getting familiar with Nix. With the vscode extension Remote Development this has become the fastest way to get started!
So until there is a great solution for binaries for stackage, a docker image is maybe the most user-friendly option?
Nix has other problems as well! It only  works with bash, it has problems with xattrs on NFS, ZFS, btrfs, etc ...

@v217 - adding ghcide to Stackage is useful, independent of anything else you've said. Perhaps you want to create another ticket to advocate including another option? It's certainly not an either/or situation - we can be on Stackage and have binaries, a Nix script, a homebrew installation etc.

@ndmitchell Absolutely agree, just wanted to mention this option!

Btw, its likely that specific forms of distribution (including binary) will be done through https://github.com/haskell/haskell-language-server rather than ghcide, and that project will bundle ghcide plus plugins.

Once https://github.com/digital-asset/ghcide/pull/429 gets merged we'll be in a state to add it. Furthermore, it's just a few days before the next Stackage LTS cutoff, so that's convenient.

I can confirm that everything builds fine and all tests pass locally with lts-15.0. However, a new release (0.2.0?) is needed to allow stack install ghcide to work outside the project.

#464 was caused by not yet being in Stackage.

You know, it would make a huge amount of sense for ghcide to be in Stackage.
In the top directory of any stack.yaml-based project, you could just $ stack exec --package ghcide ghcide -- --lsp and then ghcide would be locally compiled with the same version of GHC that project uses, and executed.

I think we could merge this with https://github.com/haskell/haskell-language-server/issues/400

source: gharchive/issue

authors: cocreature ejconlon jamesdbrock jneira ndmitchell turion v217

repo: haskell/ghcide

license_type: permissive

license_source: github-api


text:
Caret ranges in npm specifiers do not work properly

caret ranges seem not to work properly:
molt updates the version in the following import declaration:
import ora from 'npm:ora@^7.0.1';

like this:
📦 ora ^7.0.1 => 8.0.1
...

i reproduced this issue with:

deno 1.39.2
molt 0b14e3e820ff669692041fb451041538199a263f
on arch linux

See also #111

Fixed with #128.
Tilde or caret ranges are no longer targeted by molt.

authors: hasundue masnagam

repo: hasundue/molt

license: MIT


text:
How do I delete/unpublish?

Add more meat to the publish section?

Hello. Is there any update on this? How can I uninstall? Thank you.

repo: hasura/docs

license: mit

license_source: bigquery


text:
🛑 Code Guide is down

In 6c27024, Code Guide (https://cg.arash-hatami.ir) was down:

HTTP code: 504
Response time: 15857 ms

Resolved: Code Guide is back up in 0ab5747 after 24 minutes.


text:
[BUG] hauler version does not retrieve/output the correct information

Environmental Info:

N/A

Hauler Version:

N/A

Describe the Bug:

In Hauler v1.0.5, when you run hauler version does not retrieve and output the correct information due to the code references back to rancherfederal/hauler
Once we complete and close Issue (#266), then hauler version should be able to retrieve and output the correct information...

Hauler v1.0.5:
 __    __       ___       __    __   __       _______ .______
|  |  |  |     /   \     |  |  |  | |  |     |   ____||   _  \
|  |__|  |    /  ^  \    |  |  |  | |  |     |  |__   |  |_)  |
|   __   |   /  /_\  \   |  |  |  | |  |     |   __|  |      /
|  |  |  |  /  _____  \  |  `--'  | |  `----.|  |____ |  |\  \----.
|__|  |__| /__/     \__\  \______/  |_______||_______|| _| `._____|
hauler: Airgap Swiss Army Knife

GitVersion:    devel
GitCommit:     unknown
GitTreeState:  unknown
BuildDate:     unknown
GoVersion:     go1.21.12
Compiler:      gc
Platform:      darwin/arm64

Hauler v1.0.4:
 __    __       ___       __    __   __       _______ .______
|  |  |  |     /   \     |  |  |  | |  |     |   ____||   _  \
|  |__|  |    /  ^  \    |  |  |  | |  |     |  |__   |  |_)  |
|   __   |   /  /_\  \   |  |  |  | |  |     |   __|  |      /
|  |  |  |  /  _____  \  |  `--'  | |  `----.|  |____ |  |\  \----.
|__|  |__| /__/     \__\  \______/  |_______||_______|| _| `._____|
hauler: Airgap Swiss Army Knife

GitVersion:    1.0.4
GitCommit:     05e67bc
GitTreeState:  clean
BuildDate:     2024-06-26T03:29:02Z
GoVersion:     go1.21.11
Compiler:      gc
Platform:      darwin/arm64

Steps to Reproduce:

zackbradys@Zacks-MacBook-Pro hauler % curl -sfL https://get.hauler.dev | sudo bash

zackbradys@Zacks-MacBook-Pro hauler % hauler version

Expected Behavior:

hauler version retrieves and outputs the correct information

Actual Behavior:

hauler version does not retrieve and output the correct information

Additional Context:

N/A

Closing as resolved per PR https://github.com/hauler-dev/hauler/pull/283!
Thanks @dweomer!

repo: hauler-dev/hauler


text:
chore: add xhr2 package

This should fix the error described in https://github.com/haveno-dex/haveno/issues/1482.
To use:
npm install
npm pack
and install the packaged file in sample app
npm install haveno-ts-0.0.30.tgz
npm run start
You will not see the XMLHttpRequest is not defined error anymore

Thanks for your submission. In the end, this solution provided everything we were looking for: https://github.com/haveno-dex/haveno-ts/pull/338

Uses node-xmlhttprequest which is currently used in the jest tests
Only imports types to the global object if not present
Exports the types for clients to use without additional imports
Ignores type warnings
Doesn't introduce vulnerabilities (actually fixes the current high severity vulnerability).

source: gharchive/pull-request

authors: im-adithya woodser

repo: haveno-dex/haveno-ts


text:
[HxSideBar] Sidebar remains collapsed horizontally when the window is resized

When a Sidebar is horizontally collapsed by toggler and then the window is made narrower which causes the Sidebar to collapse vertically to its header and then the Sidebar is expanded vertically by the hamburger expader it remain collapsed horizontally. There is no way how to expand the sidebar horizontally in this situation (the toggler is hidden).

Steps to reproduce

Open the documentation site https://havit.blazor.eu/
Toggle the Sidebar
Make the window narrower to make Sidebar to collapse to up
Expand the Sidebar

Solution
A solution is probably quite simple the navbar toggler (hx-sidebar-navbar-toggler) should expand the sidebar also horizontally.
The onclick is added:
          <HxButton OnClick=@(async () => await SetCollapsed(false))
                CssClass="@CssClassHelper.Combine("hx-sidebar-navbar-toggler ms-auto", GetResponsiveCssClass("d-??-none"))"

and the function:
   private async Task SetCollapsed(bool state)
    {
	Collapsed =state;
	await InvokeCollapsedChangedAsync(Collapsed);
    }

@crdo Can you please check the proposed solution?

That is unfortunately not enough.
We need to get rid of the collapsed class on HxSidebar and if this is suppose to be a real solution, it has to happen on the window resize event and also take in an account the responsive settings of the Sidebar.
That being said makes it a way more complicated than the proposed solution

The presence of collapsed  css class is controlled by Collapsed property.
    private string GetCollapsedCssClass() => Collapsed ? "collapsed" : null;

and onclik handler sets the property whenever the hamburger button is pressed.
Afte the window resize sidebar is horizontally collapsed  (disapears) and shows only after clicking the hamburger button which expands it horizontally too and there is no need for reaction to window resize.
I apologize - it is difficult to explain it clearly.

I think there is a better solution. Working on it...

@hakenr i decided to link WIP PR as I am not making any progress.

cleaned some CSS and moved utility classes to CSS isolation
implemented what @TPIvan is suggesting, but I consider it to be more a work-around than a real fix as is has some known issues (SidbarBrand text shows after clicking on hamburger menu, not after resizing window, collapse animation of mobile menu is not happening on the first click)
moved some logic of showing/hiding of elements when collapsed/expanded from CSS to Blazor using CascadeParamterer

From my POV, points 1 and 3 are merging worthy. Not sure about the 2. Real solution as I see it after messing around with the implementation for couple of hours is to separate rendering of SidebarItems in desktop and mobile view. Yes, it would duplicate presence of the items in the DOM, but it would solve this issue and simplify the implementaiton.

... is was hoping for a CSS only solution, but the with the possibility to set Responsivity of rendering the desktop/mobile version in Blazor and with missing SASS maps in the CSS isolation, it is simply not possible.

I think that a CSS only solution will be difficult (if possible), because after the sidebar is horizontally collapsed its state is changed and this state has to be responsively ignored.
I agree that proposed solution is more a workaround than a solution, but it respects the changed state and reverts it after pressing the vertical expand button.

@crdo Do you have any idea for a permanent solution?
We're currently thinking about overriding all the sidebar css classes with media queries in our SCSS.
So basically inverting the root classes to have no width limitation on the collapsed state, and for the media query classes to have a set width instead.

That is only a half of the problem.
Even if you remove the fixed width of the collapsed Sidebar, fixing the layout problem, you end up with correct layout but still missing the content of the SidebarItems, which is not rendered at all if ParentSidebar.Collapsed == true.

I have an idea of permanent solution which is to separate rendering of the nav content for mobile/desktop.
The mobile item is a simple NavItem with no logic whatsoever contrary to desktop item that has tooltips, dropdowns, expanded/collapsed variant etc.
I am giving you guys a hads-up that we are currently focused on activities related to Havit.Blazor.Premium as part of our monetisation efforts tracked in #798 so if anyone giving it a shot I can support you with my ideas.

@crdo:
I believe that categorizing navigation strictly into mobile and desktop views might be a bit limiting. For instance, a desktop window can be resized to a narrow width, and mobile devices can switch orientations, altering their display between mobile and desktop views.

@TPIvan what I propose is that both of the views will be always rendered in the DOM and its visibility will be managed by responsive utility classes set on the Sidebar.
The key take-away is that the mobile nav would not be anyhow affected by the collapse state of the desktop nav.

@crdo Sounds like the best approach to be honest. I had a look at the Bootstrap 5.3 docs page, and they handle this issue similiar,  but a bit different (the menu becomes an offcanvas there).
Some design questions regarding the proposed solution:

How should the files/classes/components be organized? Separate components for the "sidebar" and "topbar" states, or everything in HxSidebar?
For the small screen size: should it always be a "topbar", or optional the "offcanvas" approach?

There are probably multiple ways to approach this, either with breaking changes or without.

@StefanOverHaevgRZ @TPIvan good news, finally found some time to fix this. We will cleanup the solution with @hakenr next week and release it.

@StefanOverHaevgRZ @TPIvan you can validate the fix in 4.7.2-pre01.

@crdo AddHxMessageBoxHost is gone?

@crdo Mostly working fine 👍 Some minor "issue", maybe with the same root issue:

Setting the Collapsed property to true does not affect the small screen navigation.

Have navigation expanded in large and small screen state.
In large screen state, set Collapsed to true.

Large screen nav is collapsed

Reduce window size to small screen.

Small screen nav is still expanded, even though Collapsed is true

Having the small screen nav will stay open when switching between large and small screen state.

In small screen state, open the top navigation.
Switch between small and large screen size.

Whenever switching to small screen size, the navigation is still open.
From a UX, I kinda expect the navigation to be closed.

Maybe both things are by design and not real issues. 😄

@StefanOverHaevgRZ thanks for the feedback. I think what you describe is related to https://github.com/havit/Havit.Blazor/issues/529 and that have not been addressed yet.

@crdo I have tested HxSidebar on the documentation website, and it works mostly well. However, I have noticed two minor issues:

When the issue was initially reported, the main documentation sidebar was collapsible. Currently, I cannot find a toggle button, so I had to add a custom toggler.
When the window is resized, the collapsed sidebar becomes wider just before it disappears.

@TPIvan Probably the new default width of 300px instead of 250px playing a part here? I could not observe this issue however.

@TPIvan
The collapse toggle is there, but in a slightly more minimalistic fashion.

I am aware of the second point, but that is bug in the docs, not in the Sidebar component itself.

@crdo I apologize for the confusion earlier.

I now see the toggle button. Thanks for pointing that out!
I deleted my clone and downloaded it again. The issue no longer appears, so it seems the code was not properly synchronized before.

I fixed the docs in the meantime. It will be part of the next release.

authors: StefanOverHaevgRZ TPIvan crdo hakenr


text:
Unexpected token '='

Hey,
Currently having an issue with favicons-webpack-plugin via  the favicons package.
Here's my error;
SyntaxError: Unexpected token =
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:373:25)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (C:\...\node_modules\favicons-webpack-plugin\node_modules\favicons\helpers-es5.js:18:15)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (C:\...\node_modules\favicons-webpack-plugin\node_modules\favicons\es5.js:11:15)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (C:\...\node_modules\favicons-webpack-plugin\lib\favicons.js:3:16)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at DependenciesBlock.loadPitch (...\node_modules\webpack\node_modules\webpack-core\lib\NormalModuleMixin.js:193:17)
    at DependenciesBlock.doBuild (...\node_modules\webpack\node_modules\webpack-core\lib\NormalModuleMixin.js:241:4)

However, I can't see why it's happening, as helpers-es5.js:18 is this line
var path = require('path'),
    fs = require('fs'),
    _ = require('underscore'),
    color = require('tinycolor2'),
    cheerio = require('cheerio'),
    colors = require('colors'),
    jsonxml = require('jsontoxml'),
    sizeOf = require('image-size'),
    async = require('async'),
    mkdirp = require('mkdirp'),
    Jimp = require('jimp'),
    svg2png = require('svg2png'),
    File = require('vinyl'),
    Reflect = require('harmony-reflect'),
    NRC = require('node-rest-client').Client,
    PLATFORM_OPTIONS = require('./config/platform-options.json');

I can't build on Windows, or Heroku, but OS X seems to build fine.

Hey @alexdrans, what version of Node are you running?

v4.5.0

If you're running the ES6 version (likely) then you should probably be jumping on Node 5 or 6+

Thanks for the rapid reply. Let me check whether v6.5.0 fixes it!

Yep, all working! 🎈 Thanks @haydenbleasel. Awesome module also.

@alexdrans No worries homie 👍

@haydenbleasel this is still an issue in projects that use e.g. favicons-webpack-plugin and cannot upgrade to Node 6.x. Don't you have any plans to support older versions of Node than 6?

@crisu83 If you read our docs, we compile an ES5 version of Favicons. All you need to change in Webpack Favicons is require('favicons') to require('favicons/es5').
However, Node 0.10 is only maintained until October and 0.12 until December. I suggest upgrading to v4 or v6.

@haydenbeasel I did read your docs, but I encounted this issue on Node 4.x.

I'm using favicons in my Ember.js app via the ember-cli-favicon addon and am experiencing the same issue. Everything worked fine with Node v4.3.1 until my last commit from 2 days ago.
That commit didn't change anything regarding versions, it only contained some simple modifications in an ember template and some extra rules in a less stylesheet.
Switching to Node 6 is currently not an option. I especially stick with Node 4 as that is the current, supported LTS version of Node.
Moreover, everything worked fine with this setup until my last commit, so I think it's not directly related to the version of Node.
Note: I had similar issues in the past, where the cause was apparently an es5 compilation issue: https://github.com/haydenbleasel/favicons/issues/147

FYI: ember-cli-favicons relies on broccoli-favicons, which in turn relies on the favicons library.
As you can see in the code, the broccoli-favicons library already uses the es5 version: https://github.com/davewasmer/broccoli-favicon/blob/master/index.js

Fixed by pull request https://github.com/haydenbleasel/favicons/pull/154

repo: haydenbleasel/favicons


text:
Idea: a guide for incremental adoption of pothos in a nexus/typegraphql project

Hey @hayes 👋🏼, hope you're doing well.
I'm a member of The Guild, we've been using Pothos for quite some time now and we really admire it but unsurprisingly we get a lot of questions from people asking us about the same thing which is:

Can I use my Nexus/Typegraphql setup in conjunction with an incremental adoption of Pothos?

It's painful to rewrite an entire production app from one framework to another esp when they differ a lot like Typegraphql -> Pothos migration(I did a Nexus -> Pothos migration recently and it took me a whole painful month to do it). I've started investigating a number of ways we can achieve that and I've got this minimal example which is a usage of two graphql schema builders that work internally entirely different, my goal is to make that approach as agnostic as possible literally using any graphql framework in conjunction with Pothos. The idea there is that every setup defines its own types and resolvers like:
Typegraphql -> defines Recipe object type and its resolver
Pothos -> defines Person object type and its resolver
in that particular use case where the two work on their own, it's easy to just use the mergeSchemas utility from the @graphql-tools/schema package to get a single schema from both at the end before passing it to whatever gql server we're using. The issue is that the nexus/typegraphql/etc.. setup is gonna always have all of application's types and the Pothos setup is gonna always has insufficient types, an example as in here where it gets interesting is when we wanna add a new field to our People object type to reference Recipe which is in the typegraphql setup, the issue is that even that we're very sure that the Recipe object type is gonna exist when the schemas are merged but the Pothos builder isn't aware of that and throws an error because of missing object refs and refuses to build the schema. So the challenge here that I faced is making Pothos not complain about missing types because we know they’re gonna exist when we merge the schemas, so is this a limitation from the GraphQLSchema object that gets built or is it a layer that's extensible at Pothos level? because my thinking was towards adding an option for Pothos to skip erroring bc of missing object refs if that's achievable.
Even one of the core engineers for Nexus shared this thread in which he says that he was very very impressed with the approach of Pothos after playing with it and is also thinking of what we're headed for.
Wanted to share with you this process and get your thoughts on it and hear the possible ways I'm not aware of to support such a behavior/feature.

This is definitely something I want to support, and something I am actively working on.  I've been talking with @tgriesser as well, and he is also interested in helping these kinds of migrations easier.

So the challenge here that I faced is making Pothos not complain about missing types because we know they’re gonna exist when we merge the schemas, so is this a limitation from the GraphQLSchema object that gets built or is it a layer that's extensible at Pothos level? because my thinking was towards adding an option for Pothos to skip erroring bc of missing object refs if that's achievable.

At it's core this is an issue with GraphQLSchema.  Issue may not be the right term here, but fields in a GraphQLSchema don't reference type names, the reference actual instantiated types.  This means that we need to build a type in order for a field to be able to reference that type as a return or argument type.  We can't just make up a placeholder, because we don't know if the type is an Object, Interface or whatever.
Fortunately this is actually very easy to work around, you can just create an empty object type with no fields and Pothos should build the schema with no issues, then mergeSchemas should be able to merge the type definitions without any issues.
To make migrations easier, there are 2 things I am working on:
A new plugin for adding types from existing graphql schemas to pothos: https://github.com/hayes/pothos/pull/700
This isn't really documented yet, and only has some of the features speced out, but the goal is to let you add types defined externally to a Pothos schema.  It will support adding types on at a time (and automatically pulling other types that get referenced), but should also allow you to just pull in an entire schema, or list of types from a schema to make this a less granular process for big migrations.
The other thing I am working on is an interactive migration tool that will let you pull in an existing schema, and/or resolvers and codegen pothos definitions.  The goal is to produce something that can directly reference revolvers from the existing schema, so that if you pass in a schema from something like nexus, the generated code would automatically run with the existing resolvers and be fully functional.
It should also be incremental, and work with the plugin mentioned above, so you can slowly generate/pull in more types and always have a working schema as you go through the migration process.
This is still fairly early in my exploration of these ideas and there is a lot of work left to do, but would love to collaborate on making migrations easier!

authors: YassinEldeeb hayes

repo: hayes/pothos

license: ISC


text:
Light travel time correction in the flare list?

Hi @hayesla, Hi @hannahc243,
First of all, congratulations on the great flare list! We've been waiting for a list like this for so long, and it's wonderful that you're working on it. Thank you so much.
I have a quick question. I'm using the flare list to automatically find combined events with Hinode and IRIS. However, the csv file created at the end has no information regarding light travel time correction. I was wondering if it would make sense to add this information to the table. We could extract it from the header of each cpd file for each flare (without passing through the SPICE kernel).
What do you think?

Hi Andrea,
Yes I think that this is possible to do from the cpd file as you said. It can be added to the next version.

This is now included in PR #9!


text:
byte array support

It looks like in TypeIDS.h there is missing support for:
getHazelcastTypeId(const std::vector *object)
and also within ObjectDataInput.h there is missing support for:
template<>
void ObjectDataInput::readInternal(int typeId, std::vector *object)
It looks like all the other functions necessary exist (ObjectDataInput::readByteArray), so I'm curious if this was intentional or not.

Hello,
What do you mean by ObjectDataInput::readInternal(int typeId, std::vector *object) ? What is the type of the vector template? Can you please provide a concrete example on what you want to achieve?
There are already the supported vector serialisations like here: https://github.com/hazelcast/hazelcast-cpp-client/blob/master/hazelcast/include/hazelcast/client/serialization/ObjectDataInput.h#L191
And also for toObject method here:
https://github.com/hazelcast/hazelcast-cpp-client/blob/master/hazelcast/include/hazelcast/client/serialization/pimpl/SerializationService.h#L243
These should normally be OK.

So if you have a
TransactionalQueue<std::vectorhazelcast::bytes> queue
and you do queue.poll();
It calls into this readInternal: https://github.com/hazelcast/hazelcast-cpp-client/blob/master/hazelcast/include/hazelcast/client/serialization/ObjectDataInput.h#L239
Because there does not exist a ObjectDataInput::readInternal(int typeId, std::vector< byte >* object) specialization
It then throws an exception because there is no serializer registered to process.
I also believe there is a compiler error that occurs when you try to compile the same above queue:
queue.poll();
Because it compiles until this line: https://github.com/hazelcast/hazelcast-cpp-client/blob/master/hazelcast/include/hazelcast/client/serialization/ObjectDataInput.h#L207
And TypeIDS.h does not define a getHazelcastTypeId(const std::vector< byte > *object)
Sorry for the confusion, I didn't realize that my above comment dropped the T = byte in my std::vector

Ok, i see the problem. Can you try using TransactionalQueue<std::vector > ? This will be pretty much the same.
Meanwhile, I will add
            template<>
            HAZELCAST_API Data SerializationService::toData<std::vector<byte> >(const std::vector<byte> *object);

specialisation in SerializationService. This should solve the problem.
Thanks for reporting.

repo: hazelcast/hazelcast-cpp-client


text:
Yahoo validation is not working now

Hi,
Recently, the yahoo validation is not working but it was working before, could you check it ?

doesn't work for gmail also though it used too.

`    private function get_yahoo_cookies(){
$this->debug[] = 'Attempting to get the cookies from the sign up page...';
if($this->yahoo_signup_page_content !== false){
$this->debug[] = 'Extracting cookies from headers...';
$cookies = array();
foreach ($this->yahoo_signup_page_headers as $hdr) {
if (preg_match('/^(Set-Cookie|set-cookie):\s*(.?;).?$/', $hdr, $matches)) {
$cookies[] = $matches[2];
}
}
    if(count($cookies) > 0){
      $this->debug[] = 'Cookies found: '.implode(' ', $cookies);
      return $cookies;
    }
    else{
      $this->debug[] = 'Could not find any cookies.';
    }
  }`

      if (preg_match('/^(Set-Cookie|set-cookie):\s*(.*?;).*?$/', $hdr, $matches)) {
        $cookies[] = $matches[2];

Replace line 278 and 279 with this.

@v1ra1  It still doesn't work! can you help?

Fixed. see v1.0.8

repo: hbattat/verifyEmail


text:
third party libs used in 100DaysOfJava

Information about third party libs used in the code snippet.

@Viniberaldo is this PR ready for review? If not, you can revert it to draft while you're working on it.

@Viniberaldo is this PR ready for review? If not, you can revert it to draft while you're working on it.

Hi @hbelmiro ! After fix some typos, it looks good to me.

authors: Viniberaldo hbelmiro


text:
Rewrite homepage to particular page

Hello , Is there a way to use the docs module as the Index page and blog module as a Blog page , like in Docusaurus.

You can customize the homepage to be a landing page, and write any content you want.
// content/_index.md
---
layout: landing
# full_width: true
---

Use Markdown and shortcodes to generate any content.

Example
Source code

https://docker.hugomods.com/
https://github.com/hugomods/site/blob/main/docker/content/_index.md

https://images.hugomods.com/
https://github.com/hugomods/site/blob/main/images/content/_index.md

https://echarts.hugomods.com/
https://github.com/hugomods/site/blob/main/echarts/content/_index.md

...

thanks for the help but what if i dont want to include the landing page and use a docs page as a index.

Not sure if this what you want, specify the type as docs on homepage.
// content/_index.md
---
type: docs
---

I meant like,  assume that i have a doc page named "page1" and i want set that page as the index page.

Hmm, are you meant to reuse the content and layout (left sidebar, right sidebar and so on) as same as the "page1_" on homepage? If so, I don't have good idea.

Yes that is what I wanted to do .

I see, I have an idea now, but naming is difficult, what should we naming this functionality?

Anything you want .

Available since github.com/hugomods/base v0.6.0, check out the hugomods/base#43 to learn how to use it.

Yep

repo: hbstack/theme-cards


text:
Request to incorporate ideas from another Edge Removal script to work with "ie_to_edge_stub.exe" for use with URL redirection projects

Desired outcome:
The ability to apply for instance @AveYo's OpenWebSearch.cmd or
@rcmaehl's MSEdgeRedirect which rely on "ie_to_edge_stub.exe" to redirect URLs to a default non-Edge replacement browser.
Code developing resource
My hope is that it's easy for you to incorporate whatever "ie_to_edge_stub.exe tricks" are done by @AveYo's Edge_Removal.bat to achieve the desired outcome. I would offer more concrete code suggestions if my PowerShell skills were better.
Thanks

Thanks for https://github.com/AveYo/LeanAndMean/pull/7#issue-1632807668.
Your improved RunAsTI.reg file fixed the Issue I raised on that project https://github.com/AveYo/LeanAndMean/issues/16

I'll consider this for a future release, although initially as an experimental option
Thank you

I believe there's a discussion on an issue thread on AveYo's repo in regard to ie_to_edge_stub. I haven't messed with my implementation for a while because ItJustWorks™
If I remember correctly:

There is a set list of locations it can be at to be trusted
Interception is done via Image File Execution Options registry keys
ie_to_edge_stub is used because the application is checked for specific Extended EV Certificates

authors: espanafly he3als rcmaehl

license: Unlicense


text:
using multibytes in collection breaks label's for and input's id attributes

$ uname -a
Darwin mbp 14.5.0 Darwin Kernel Version 14.5.0: Tue Sep  1 21:23:09 PDT 2015; root:xnu-2782.50.1~1/RELEASE_X86_64 x86_64

$ ruby -v
ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin14]

created a repo to test.
https://github.com/github0013/simple_form_check_boxes
# app/views/users/create.html.erb

<%= simple_form_for User.new do |f| %>
  <%= f.input :tags, as: :check_boxes, collection: %w[tag1 tag2 tag3] %>
  <%= f.input :tags, as: :check_boxes, collection: %w[タグ１ タグ２ タグ３] %>
  <%= f.input :tags, as: :check_boxes, collection: Hash[*(%w[タグ１ タグ２ タグ３]).zip(1..3).flatten] %>
  <%= f.input :tags, as: :check_boxes, collection: Hash[*(%w[タグ１ タグ２ タグ３]).zip(%w[タグ１ タグ２ タグ３]).flatten] %>
<% end %>

While collection: %w[tag1 tag2 tag3] works as expected, collection: %w[タグ１ タグ２ タグ３] doesn't work properly when clicking on labels.
If you check the source, you will see the label for and input id are all same.  They are missing suffix part which should have been each of the collection text since the %w[タグ１ タグ２ タグ３] collection consists of multibytes.
Is there a way to fix this with some options?
NOTE: tag texts itself should be sent to server, not some ids

this was fixed in Rails https://github.com/rails/rails/commit/d656097734928e1f6b3c3bd884e128c4e299f2ec


text:
How to transform rectagle box coordinate to original coordinate

How to transform rectagle box coordinate to original coordinate

@ranyaphat29 Please, check this docs: https://labelstud.io/guide/predictions.html#Units-of-image-annotations ?

@ranyaphat29 have you solved your issue?

repo: heartexlabs/label-studio


text:
Make more compatible with windows

Change a few path functions to make it more compatible with windows. Remove redundant output path handling also
Also could you update the version for composer so that the latest fixes are being used

Coverage decreased (-56.4%) to 21.348% when pulling 2a9903ff08001364197cc2bfc1b12f9f712b8d34 on garhbod:master into f9a822da8245486a775df319b5afb90a96537094 on heiglandreas:master.

+1

Thanks for the PullRequest. As I‘m on holiday ATM it
will take a day or two until I get around to actually getting some stuff done, but I will definitely see to it to get this fixed ASAP

Okay @heiglandreas Let me know how it goes.

Hey garhbod. Thanks for your PullRequest! I didn't merge it but took the content and implemented it in a slightly different way in #12. With the new release (coming every minute now) you should be able to run the library on windows as well.
Thanks for your input!

Thanks @heiglandreas updated composer with your latest and everything is working fine

authors: MisterDuval coveralls garhbod heiglandreas


text:
Getting ReferenceError: TextEncoder is not defined when used in Node.js v10

Buffer.js makes reference to TExtEncoder, but never imports it:
https://github.com/heineiuo/rippledb/blob/b88520491ef89a7025c5a67fd02845aad09a77c0/src/Buffer.ts#L95
This causes an exception on Node.js
I was using the following script to try and convert a Level DB to a Ripple DB:
#!/usr/bin/env node

const fs = require('fs');
const path = require('path');
const level = require('level');
const { Database } = require('rippledb');

// https://github.com/heineiuo/rippledb/issues/148
global.TextEncoder = require("util").TextEncoder;

if(process.argv.length !== 4) {
  console.error("Usage: node level-convert.js <path_to_level_db> <path_to_ripple_db>");
  process.exit(1)
}

let levelDbPath = process.argv[2];
let rippleDbPath = process.argv[3];

try {
  const stats = fs.statSync(levelDbPath);
  if(!stats.isDirectory()) {
    console.error("No such leveldb database");
    process.exit(1);
  }
} catch(e) {
  console.error("No such leveldb database");
  process.exit(1);
}

try {
  const levelDb = level(levelDbPath, {valueEncoding: 'json'});
  const rippleDb = new Database(path.resolve(__dirname, rippleDbPath));
  const stream = levelDb.createReadStream();
  stream.on('data', function({ key, value }) {
    rippleDb.put(key, value);
    console.log(key, value);
  })
  stream.on('end', function() {
    process.exit(0);
  })
} catch(e) {
  console.error("Could not open leveldb database");
  process.exit(1);
}

It looks like I'll have to do the same workaround as you do for tests, but shouldn't the library handle this internally?
https://github.com/heineiuo/rippledb/blob/52b8d0dd77bba75c310203b23293604461d34413/tests/filter.test.ts#L5

@lehni Thanks!  I appreciate your mentioning that.
To enable this project support both node.js and Deno(WIP), I removed all node.js modules. The line in rippledb/tests/filter.test.ts was added just because jest did not have TextEncoder in global object.
This was my mistake, and I will add global TextEncoder at /port/node folder if node.js version is under v11.

@heineiuo while we're at it: Is it a bug or a feature that I can't seem to be able to put a new value over an existing key?

@lehni It's absolutely a bug. Could you please open a new issue for that?

@heineiuo while we're at it: Is it a bug or a feature that I can't seem to be able to put a new value over an existing key?

Ok, I'll investigate!

My bad, it was an async issue…

My bad, it was an async issue…

haha :), nevermind, any issue will be welcomed!

:) BTW, why do I need to use new TextDecoder().decode() on the stored values even when they were stored as strings? Shouldn't I get the same thing back that I put in? And did you consider supporting a feature like { valueEncoding: 'json' } on level?

(apologies for keep writing off-topic message here, but I just switched from level to rippledb, and this is just amazing: added 1 package from 1 contributor, removed 21 packages from 12 contributors 🎉 )

:) BTW, why do I need to use new TextDecoder().decode() on the stored values even when they were stored as strings? Shouldn't I get the same thing back that I put in? And did you consider supporting a feature like { valueEncoding: 'json' } on level?

RippleDB is more like leveldown which does not have encoding option either.
RippleDB was designed to be a low level engine for data writing and reading, and use Uint8Array as standard data type.
In original design, It should only use Uint8Array type params. However, in most situation, string is a first choice for key's encoding. So string was also supported in RippleDB. If user pass string type key or value, RippleDB will recognize it and convert it to Uint8Array. RippleDB doesn't store data's original encoding and cannot distinguish the right value type when reading data. so it just returns Uint8Array :(.
Here is a simple example of wrapping RippleDB to support valueEncoding:
import { Database } from "rippledb";

class CustomDatabase extends Database {
  constructor(dbpath: string, options = {}, extraOptions = {}) {
    super(dbpath, options);
    this.extraOptions = extraOptions;
  }

  async customPut(key, value) {
    if (this.extraOptions.valueEncoding === "json") {
      return await this.put(key, JSON.stringify(value));
    }
    return await this.put(key, value);
  }

  async customGet(key) {
    if (this.extraOptions.valueEncoding === "json") {
      const value = await this.get(key);
      return JSON.parse(value);
    }
    if (this.extraOptions.valueEncoding === "utf8") {
      const value = await this.get(key);
      return new TextDecorder().decode(value);
    }

    return await this.get(key);
  }
}

(apologies for keep writing off-topic messageshere, but I just switched from level to rippledb, and this is just amazing: added 1 package from 1 contributor, removed 21 packages from 12 contributors 🎉 )

I'm super glad to hear that!! 🎉  Any issues and messages are welcomed!!

@heineiuo this makes a lot of sense, thank you for the explanations! I think it's worth putting the above 1:1 into the README, no?

@lehni Very cool! I think i can put that in Q&A.

/home/inba/Desktop/node/mongodb/node_modules/whatwg-url/lib/encoding.js:2
const utf8Encoder = new TextEncoder();
^
please solve the error in node 10 version*******
ReferenceError: TextEncoder is not defined
at Object. (/home/inba/Desktop/node/mongodb/node_modules/whatwg-url/lib/encoding.js:2:21)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Object. (/home/inba/Desktop/node/mongodb/node_modules/whatwg-url/lib/url-state-machine.js:5:34)
at Module._compile (internal/modules/cjs/loader.js:778:30)

/home/inba/Desktop/node/mongodb/node_modules/whatwg-url/lib/encoding.js:2 const utf8Encoder = new TextEncoder(); ^ please solve the error in node 10 version*******
ReferenceError: TextEncoder is not defined at Object. (/home/inba/Desktop/node/mongodb/node_modules/whatwg-url/lib/encoding.js:2:21) at Module._compile (internal/modules/cjs/loader.js:778:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Module.require (internal/modules/cjs/loader.js:692:17) at require (internal/modules/cjs/helpers.js:25:18) at Object. (/home/inba/Desktop/node/mongodb/node_modules/whatwg-url/lib/url-state-machine.js:5:34) at Module._compile (internal/modules/cjs/loader.js:778:30)

It seems like throw from whatwg-url, not rippledb

This problem is caused by an incompatible version of Node.js. You must upgrade your node.js version to v14 or above.
I came across this video that goes into great detail about the problem and how to solve it: https://youtu.be/li9eZtfekl0

const utf8Encoder = new TextEncoder();
^
ReferenceError: TextEncoder is not defined
I need solution for this error please?

@Codeur16 It seems like you are using node.js < 10? You can add this polyfill to your entry js file:

global.TextEncoder = require('util').TextEncoder

However I must say upgrade your node.js to 10+ is better.

authors: Codeur16 codetycon heineiuo lehni selvalr

repo: heineiuo/rippledb


text:
Add support for persistent connections

This adds support for persistent connections for the Interbase driver (supported via ibase_pconnect)

Looking at the diff, this modification and cleanup obviously created many not visible changes g
BTW..., after the new protected $persistent attribute there is an empty doc-block now. Did you reserve this space for something?
And many thanks for all the improvments you provide. I hope firebird will finally find it's way in the head.
Andreas

Hi Andreas.
I've reset the commits to one without formatting the entire file, and removed the empty doc-block (it had no purpose, sorry).
If you are aware of any outstanding issues that needs to be solved before this can be merged back into the Doctrine project, you can open them as issues and I'll gladly help out.
Thanks for your input and the work you put into this implementation.
// Daniel

authors: ancpru renklaf

repo: helicon-os/doctrine-dbal


text:
14-CURRENT: Asus K40IN stuck at boot screen

Describe the bug
stuck at boot screen.
Screenshots

Version (please complete the following information):

Live ISO
FreeBSD version 14
helloSystem build 0H277
Running in a virtual machine: no

Computer (please complete the following information):

Device: K40in asus

In 0H278 13.1

Please open a separate issue, since this looks like a different error.

0.9.0 successfully started normally.

repo: helloSystem/ISO


text:
使用CDN引入的，直接使用</控制台报错

A description of the problem, steps to reproduce, or with code samples, can be hosted on a GitHub repository with a link to the repository. (问题说明，重现步骤，或附上代码示例，可存放 GitHub 仓库并提供仓库链接。)

图裂了.
小弟用 https://unpkg.com/quarkd@1.0.52/umd/index.js 没看到什么问题.

顾北_
@.***
 测试用例
------------------ 原始邮件 ------------------
发件人:                                                                                "hellof2e/quark-design"                                                                                @.>;
发送时间: 2023年4月12日(星期三) 晚上8:17
@.>;
@.@.>;
主题: Re: [hellof2e/quark-design] 使用CDN引入的，直接使用<quark-list></<quark-list>控制台报错 (Issue #245)
可以提供一个demo么？这边没看到什么问题
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

顾北_ @.***  测试用例
…
------------------ 原始邮件 ------------------ 发件人: "hellof2e/quark-design" @.>; 发送时间: 2023年4月12日(星期三) 晚上8:17 @.>; @.@.>; 主题: Re: [hellof2e/quark-design] 使用CDN引入的，直接使用<quark-list></<quark-list>控制台报错 (Issue #245) 可以提供一个demo么？这边没看到什么问题 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

是否方便将你本地文件压缩下，发送到我们邮箱，我们排查下

demo.zip

Fixed in #255


text:
adding tests for proxy get and delete handlers

EES-4223

👍

authors: aleksandrzhiliaev s-radyuk

repo: hellofresh/kangal


text:
[stable/mariadb] Add volume subPath for master

What this PR does / why we need it:
Then specifying a existingClaim for the master it would be useful to be able to change the subPath within the existingClaim. This PR adds the option to add a subPath for the master's volume mount.
Which issue this PR fixes
To my knowledge there is no issue for this.
Special notes for your reviewer:
None
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/rebuild

/retest

/lgtm

authors: gouglhupf tompizmor

repo: helm/charts


text:
[k8s-spot-termination-handler] Updating OWNERS file.

Signed-off-by: Alexey Shabalin alexey.shabalin@fairfaxmedia.com.au

What this PR does / why we need it:
Adding myself to the OWNERS file.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @egeland

/lgtm

/approved

/ok-to-test

authors: axozoid egeland


text:
[incubator/azuremonitor-containers] - update with latest agent image version

Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
This PR has following changes

update to latest agent image version
health feature bug fixes
revert API version to extensions/v1beta1 to get the chart working. We will update the API version once subsequent PR along with changes to add the support for 1.16 version.

Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @vishiy

/assign @vishiy

@lachie83, @jlegrone,@vishiy, can you guys help on reviewing this PR?

@zanhsieh, can you please help on reviewing and merging this PR?

@lachie83 @ganga1980
My LGTM won't take effort. I am not the OWNER of this chart. Only OWNER could merge.

@lachie83, @jlegrone , Appreciate if you guys can help on merging this PR.

/retest

@lachie83 @jlegrone , Appreciate if you guys can help on reviewing and merging this PR.

Hi, @zanhsieh, can you please help on pinging the owners to get this PR reviewed and merged?

/assign @antongorkovenko

Looks good to me

@lachie83, @jlegrone , @zanhsieh , I would like to get this PR since few of our customers are waiting on this so I appreciate if you guys can help on getting this PR merged.

Hi, @zanhsieh, No response from either @lachie83  or @jlegrone . Is anyone else can help on merging this PR since the updates added by @antongorkovenko broke the current version of the chart ?

Hi, @zanhsieh , @lachie83 , @jlegrone , We need to get this PR merged asap since the changes from @antongorkovenko  broke the current version of the chart. We really appreciate if you guys can help on merging this PR asap since we got couple of customers reported this issue.
If you guys are busy, can you guys help on adding other people who can help on to merge this PR?

@lachie83 , Appreciate your help on merging this PR since the current version is broken.

/verify-owners

Approving this in the interest of getting it fixed

/lgtm
/approve

@ganga1980
Let's get adding additional owner PR pass please. Hope you volunteer. See:
https://github.com/helm/charts/issues/13867

@ganga1980
Let's get adding additional owner PR pass please. Hope you volunteer. See:
#13867
@zanhsieh ,  beyond adding owner file, do I need to add anything else?

@ganga1980
What is your owner file PR?


text:
[stable/prometheus-pushgateway] Follow the Call for maintainers

As this Chart is bad/not maintained and also buggy I would like to take
ownership for this Chart as my team relies on this Chart.
Signed-off-by: cstaud christian.staude@staffbase.com

Is this a new chart
No
What this PR does / why we need it:
The actual maintainer seems not to be active anymore and there are a lot of things which should be improved about this Chart.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #13867

Special notes for your reviewer:
There was already some discussion in #18187
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @gianrubio
/assign @zanhsieh

/assign @maorfr

@cstaud See "Owning and Maintaining A Chart" at https://github.com/helm/charts - please add the OWNERS file to .helmignore

/assign

/verify-owners

/verify-owners

/ok-to-test

/lgtm

authors: cstaud davidkarlsen


text:
[stable/nginx-ingress] Remove duplicated hostPorts entries in psp

There are duplicated hostPorts entries in pspwhich make previous fine-grained policy doesn't
work as expected.
Signed-off-by: Yu Chih secret104278@gmail.com

Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

No
What this PR does / why we need it:
There are duplicated hostPorts entries in pspwhich make previous fine-grained policy doesn't work as expected.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test

/assign
/lgtm


text:
[stable/nginx-ingress] fix service selector

Which issue this PR fixes

fixes #21508

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @tahara

/assign @taharah

/lgtm
/ok-to-test

/retest

authors: skomma taharah


text:
[stable/openebs] update openebs to latest 0.8.0 release

Updated README
Updated chart version
Updated values.yaml
Added analytics env var in maya-apiserver deployment

Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

Signed-off-by: prateekpandey14 prateekpandey14@gmail.com

/ok-to-test

@prateekpandey14 PTAL - the tag seems to be missing

/test pull-charts-e2e


text:
Broken Scroll Behaviour on Documentation on Mobile

When browsing helm.sh I am unable to scroll properly. The page allows me to "peek" at content below the fold but bounces back up as if there is no further content on the page. If I try repeatedly I can sometimes get it to scroll but it will then "stick" at the new location. The JavaScript on the page is fighting with the default browser scroll behaviour.
I am running iOS 17.1.2 and I tried on the latest versions of both safari and chrome although I suspect this issue will affect other mobile devices and possibly browsers.

thanks, yes. @z4ce / @scottrigby (iirc) have been discussing how to improve/fix Helm docs on mobile.
(fwiw, doc issues should be over on helm-www)

repo: helm/helm


text:
Introduce Codit Helm chart repo

Signed-off-by: Tom Kerkhove kerkhove.tom@gmail.com
Relates to https://github.com/CoditEU/charts/issues/2

The Artifact Hub, a CNCF sandbox project, is another place you can list your repos. To do that, you login (or create an account), create an organization, and list your repository. You can link it to a user or organization.

The Artifact Hub, a CNCF sandbox project, is another place you can list your repos. To do that, you login (or create an account), create an organization, and list your repository. You can link it to a user or organization.

Already did! Thanks.

authors: mattfarina tomkerkhove

repo: helm/hub


text:
add bug to exempt labels on git stale.yml

labels bug and wontfix don't go well together
shutting down comments on bug issues is something intended?
changing the stale label from wontfix to stale is less confusing. (wont)fix reminds of bugs. wontfix on e.g. questions and enhancements is kind of strange to me.
plus... https://github.com/helmfile/helmfile/issues/893 (bug issue):

🤣

changing the stale label from wontfix to stale is less confusing. (wont)fix reminds of bugs. wontfix on e.g. questions and enhancements is kind of strange to me.
could you guys give your thoughts on this one?

TL;DR I am proposing wontfix -> stale (or something else) as the stale label.

@lucasfcnunes Yeah maybe stale is more natural...? I loved wontfix for more explicitly saying it won't be fixed/addressed; stale is the cause of something getting considered wontfix; but yeah, fix doesn't make sense on anything other than bugs so...
WDYT @yxxhero?

authors: lucasfcnunes mumoshu

repo: helmfile/helmfile


text:
React 18 Compatibility Issue with @helsenorge/refero

The issue is @helsenorge/refero package is currently incompatible with React 18. While trying to install the package in a project that uses React 18.3.1, I encountered a dependency conflict.
Steps to Reproduce

Create a new project with React 18.3.1.
Run npm install @helsenorge/refero.

NPM throws the following error:
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: ccbw@0.1.0
npm error Found: react@18.3.1
npm error node_modules/react
npm error   react@"^18.3.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^17.0.2" from @helsenorge/refero@16.0.0-beta21
npm error node_modules/@helsenorge/refero
npm error   @helsenorge/refero@"*" from the root project

Can you please consider updating the peer dependency to support React 18 or release a version compatible with React 18.
Thanks

support for react18 will come in the next major version

repo: helsenorge/refero


text:
Update "No transactions" and "Not connected" states in transaction history

See designs on figma for "no transactions" and for "not connected"

Closed by #524

repo: hemilabs/ui-monorepo


text:
No example of placing something on the shared world map?

I just compiled this demo to two iOS devices. Tracking and connection seems to work, but how do you access the shared worldMap to place objects? I'm surprised this example doesn't show anything done in AR once it's connected. Any advice would be greatly appreciated.

I think there's some confusion. CaptainsMess is just a networking library. There is no concept of a "world map" and no AR component.

Got it... I was trying to get this demo working
https://github.com/Unity-Technologies/SharedSpheres
Sorry - I 'issued' the wrong github. Feel free to close.

authors: RobbieOnGithub hengineer

repo: hengineer/CaptainsMess


text:
Avoid deleting backup files from backup storage

I'm playing around with ark to protect our cluster in case of a disaster. I followed the examples for setting up in the google cloud and created a Schedule to backup hourly. With that in place I wanted to verify what happens when an operator deletes the cluster or necessary resources by accident manually. I tested such a scenario by deleting the heptio-ark namespace containing the CRD objects. It took me quite by surprise that deleting the namespace also emptied the google buckets containing the actual backup files.
I guess this would also happen when someone deletes the cluster? Is there a supported way in ark to avoid deleting any files from the backup storages or do you suggest another approach to protect against operator errors?
I'm using ark 0.7.1.

If you do anything that results in the deletion of a backup from Kubernetes, such as:

ark backup delete my-backup
kubectl -n heptio-ark delete backup/my-backup
kubectl delete ns/heptio-ark

this will trigger the full backup deletion process, including removing backup tarballs from object storage, persistent disk snapshots created by ark, and any associated restores.
We have an RFE to mark backups so they aren't deleted when they're past their expiration date (#251), but that would only affect expiration, not deletion.
We added the backup deletion functionality in v0.7.0. Prior to that, you had to manually delete everything from backup storage and use kubectl to delete the backup from Kubernetes. We had several people ask for a way to delete backups, so we added this to v0.7.0.
We are working on designing a new feature called "backup targets" that is going to allow for backup data to be replicated to multiple backup storage destinations. Perhaps we could evolve the deletion aspect as part of this.
Do you have any suggestions for how to make this better while still allowing people to delete backups?
cc @jbeda @skriss

I think it would be good to have an option to disallow any deletion from the bucket storage. Cleaning up the backup files can be configured by TTLs of the bucket itself (at least in GCP, but I guess this is true for AWS/Azure as well) and it protects against manual operator errors in regards to using ark or kubectl. AFAIU ark should be able to recover from just that.
Making this option opt-in would still allow people to usually delete their backups manually. WDYT, does that make sense in the broader view of ark as well?

I think we can address #376 as well as this if we change the logic for how we delete backups.
Right now we use a finalizer so that when ark backup delete and kubectl delete backup issue a DELETE request, it sets the deletionTimestamp and waits for the finalizer to be removed. The Ark server sees the deleted backup, deletes everything associated with the backup (files in object storage, PV snapshots, restores in kube/etcd), and then removes the finalizer, which allows the kube apiserver to finally delete it.
As I pointed out above, this happens for ark backup delete, kubectl delete backup, and kubectl delete namespace/heptio-ark.
Instead of this, we can have ark backup delete POST a new DeleteBackupRequest resource. The Ark server code that currently watches for backups with a deletionTimestamp will instead watch for DeleteBackupRequest objects, then perform the deletion logic.
If you kubectl delete -n heptio-ark backup/foo, it will only remove the backup from kube/etcd. The next time the backup sync controller runs its sync loop, assuming foo is still in object storage, the backup resource will be readded to kube/etcd.
@skriss @rdodev @rbankston @jpweber @jbeda @nrb wdyt?

Seeing as this affects PV snapshots as well, I'm all for erring on the side of having more data mysteriously show up than unexpectedly deleted. 👍

We have a couple of options for how this is implemented and what kind of output we show to the user. This is what kubectl does when deleting multiple items:
$ kubectl delete configmap -l x=y
configmap "a1" deleted
configmap "a2" deleted
configmap "a3" deleted
configmap "a4" deleted
configmap "a5" deleted

kubectl issues a GET request to retrieve all items matching the label selector x=y. For each item, it issues an individual DELETE request and prints that the item was deleted.
For Ark, we'll be POSTing a DeleteBackupRequest. Here is where we have a choice:

GET all matching backups and then send 1 request per backup, just like kubectl does above
Send 1 request containing either a list of backup names, or the label selector, and let the Ark server figure out what to delete. Instead of printing out each backup to be deleted, it would print out a more generic Request to delete backup(s) sent to the Ark server. Check to see if they've been deleted by running 'ark backup get'.

I think I am leaning toward option 1. We can record the deletion status on each DeleteBackupRequest and the user could inspect that if desired.
Any strong feelings one way or another?

One way to think about this is perhaps as separate controllers.  Have one controller responsible for creating backups and another for deleting/GCing backups.  Having clear semantics about how these hand off would help make ark more flexible and this stuff more obvious.
Separate question -- if you delete a backup through kubectl (and don't POST the DeleteBackupRequest) won't ark just scan the storage and recreate the backup?
It seems to me that there is really 2 modes here:

Backup bucket is plan of record -- In the resources in the cluster are a shadow of what is going on in the bucket.  Interactions with the shadow don't impact the real stuff unless explicit.  The "right" way to model deleting a backup would be to delete the underlying bucket storage and let the shadow reflect it.
Kube resources are plan of record -- in this scheme if it doesn't exist in k8s then it shouldn't exist in the bucket.  Deleting the resource naturally deletes the bucket.

I think the problem is that we aren't clear about the modal nature and are trying to have it both ways.
Brainstorming a model here:

A backup-read-sync controller -- this reads from a bucket and puts stuff in a k8s cluster.
A backup-finalizer controller -- this looks for finalizers and deletes stuff from a bucket
A set of tools to perhaps run the read-sync in a one-shot mode or to manage buckets directly.  Not sure about creds for those.

You'd run these controllers in different configurations to get the modes above.  Would also provide a way to fix things up or bootstrap stuff with one shot tools.
Let me know if you want to get together and walk through this.  Or if I'm just crazy :)

We do have separate controllers:

A backup controller that creates backups
A GC controller to handle deletions, either because the user explicitly asked for a deletion, or because a backup has expired based on its TTL
A backup sync controller that reads from the bucket and creates the backup object in kube/etcd if it doesn't exist

Our operating mode is the bucket is the plan of record.
We have had a request for the ability to run the backup sync in a one shot mode (#104) but we haven't implemented it yet.
I'm suggesting we change how we implement a user-requested delete. Instead of using a finalizer and sending a DELETE backup request, we get rid of the finalizer and send a POST delete-backup request.
The alternative is we remove backup deletion entirely from the Ark server & cli and instead have some other external tool or helper to deal with this. I still think I prefer the delete-backup request if that works for you.

Having data in the bucket only deleted when you do an explicit ark backup delete or kubectl delete backups.ark.heptio.com ... sounds reasonable to me.

The problem with kubectl delete backup/foo is that that is effectively what is called when you delete a namespace. The only way to fix this is to make it so DELETE /apis/ark.heptio.com/v1/namespaces/heptio-ark/backups/foo does not delete from object storage. Instead, we'll do POST /apis/ark.heptio.com/v1/namespaces/heptio-ark/deletebackuprequests (and this is what ark backup delete will do).

I like the DeleteBackupRequest model, and displaying each backup to be deleted individually. IMO, it's worth being explicit here so as to reduce user surprises.
We do have the bucket as a source of truth documented at https://github.com/heptio/ark/blob/master/docs/about.md#object-storage-sync. Perhaps that could be surfaced better.

Huge proponent of explicit over implicit in general. Implicit deletes are almost never a good idea -- but specially when we're talking about backups and data volumes, IMO.

Hey @ncdc, big thanks from my side for taking my concerns seriously, and providing great support for a great tool!! :cake:

authors: jbeda marco-jantke ncdc nrb rdodev

repo: heptio/ark


text:
Fulfil license obligations

[ ] Create SBOM and copy license obligation artifacts to 3RD-PARTY-LICENSES folder (see Carbynestack repositories for automation script)
[ ] Provide archive with license obligation artifacts (including source when required) as attachment to GitHub Releases
[ ] Add URL to archive to herdstat command help

See #57.

See here and here for ideas on how to integrate the URL into the version command.

repo: herdstat/herdstat


text:
fead:added bookmark notes feature

Description
The changes made in this pull request aim to enhance the functionality related to bookmarked notes
Resolves: #51
Checklist
Before submitting this pull request, kindly verify that the ensuing checkpoints have been reached.

[x] Have you adhered to the repository's defined coding convention rules?
[x] Have you updated the 'documentation.md' file with the method/function documentation?
[x] Have you sent a message along with the result or response?
[x] Have you used the try-catch technique?
[x] Has the method/class been added to the documentation (md file)?

Screenshots
Uploading a screenshot illustrating the approach developed for validation is required. (Please attach the screenshot)

I certify that I have carried out the relevant checks and provided the requisite screenshot for validation by submitting this pull request.

@Sahilll15 hey I can you please change the bookmark icon if the note is book marked
Make it appear filled
And also if a fill bookmark is clicked it should be removed from bookmarks

@Sahilll15 hey I can you please change the bookmark icon if the note is book marked Make it appear filled And also if a fill bookmark is clicked it should be removed from bookmarks

the removal of the bookmark already works ill make the icon change

@hereisSwapnil have a look at the commit

repo: hereisSwapnil/ExamTime


text:
WIP: Add Unit Tests for versioned layer client with version 0 in constructor.

Add Unit Tests for versioned layer client with version 0 in constructor.
Remove deprecation for methods getversion and withVersion of Partitionsrequest.
Update coverage for VersionLayerClient class.
Resolves: OLPEDGE-1617
Signed-off-by: Drapak Iryna Angelica ext-iryna.drapak@here.com

Codecov Report

Merging #198 into master will increase coverage by <.1%.
The diff coverage is 100%.

@@           Coverage Diff            @@
##           master    #198     +/-   ##
========================================
+ Coverage    68.2%   68.3%   +<.1%
========================================
  Files          56      56
  Lines        1520    1521      +1
  Branches      179     179
========================================
+ Hits         1038    1039      +1
  Misses        437     437
  Partials       45      45

Impacted Files
Coverage Δ

...k-dataservice-read/lib/client/PartitionsRequest.ts
100% <ø> (ø)
:arrow_up:

...ataservice-read/lib/client/VersionedLayerClient.ts
96% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

repo: heremaps/here-olp-sdk-typescript


text:
Caching partitions metadata in memory.

This CR adds LRU cache support for the partitions metadata for the
versioned and volatile layers.
The user is able to set for each partition request param: "online-only" and "online if not found in cache".
By default for each request uses mode "online if not found in cache".
This mode decreases the count of requests to the services.
Disabling some tests. The tests will be enabled on the next CRs.
Resolves: OLPEDGE-1667
Signed-off-by: Oleksii Zubko ext-oleksii.zubko@here.com

Codecov Report

Merging #287 into master will decrease coverage by 2.7%.
The diff coverage is 48.2%.

@@           Coverage Diff            @@
##           master    #287     +/-   ##
========================================
- Coverage    89.5%   86.9%   -2.7%
========================================
  Files          59      61      +2
  Lines        1757    1835     +78
  Branches      218     236     +18
========================================
+ Hits         1573    1594     +21
- Misses        102     144     +42
- Partials       82      97     +15

Impacted Files
Coverage Δ

...dataservice-read/lib/client/VolatileLayerClient.ts
76.1% <9.1%> (-20.7%)
:arrow_down:

...ataservice-read/lib/client/VersionedLayerClient.ts
77.8% <16.7%> (-15.4%)
:arrow_down:

...aservice-read/lib/cache/MetadataCacheRepository.ts
50.0% <50.0%> (ø)

...k-dataservice-read/lib/client/PartitionsRequest.ts
89.5% <60.0%> (-10.5%)
:arrow_down:

...olp-sdk-dataservice-read/lib/client/QueryClient.ts
77.8% <62.5%> (-9.4%)
:arrow_down:

...lp-sdk-dataservice-read/lib/cache/KeyValueCache.ts
88.9% <83.3%> (-11.1%)
:arrow_down:

@here/olp-sdk-dataservice-read/lib/cache/index.ts
100.0% <100.0%> (ø)

...lp-sdk-dataservice-read/lib/client/FetchOptions.ts
100.0% <100.0%> (ø)

...k-dataservice-read/lib/cache/ApiCacheRepository.ts
87.5% <0.0%> (-12.5%)
:arrow_down:

... and 5 more

Continue to review full report at Codecov.

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

authors: OleksiiZubko codecov-io


text:
README: Add a Travis CI build badge

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

authors: mnonnenmacher sschuberth

repo: heremaps/oss-review-toolkit


text:
Implement ci4 softDelete compatibility

if i've a model with softDelete enabled, the query not skipts this items automatically.
https://codeigniter.com/user_guide/models/model.html#usesoftdeletes

i dont know this is correct answer. but i change of code on construction function inside Datatables.php like this
public function __construct($builder)
{
    if (is_subclass_of($builder, '\CodeIgniter\BaseModel') && method_exists($builder, 'builder')) {
        if ($builder->tempUseSoftDeletes) {
            $builder->where($builder->table . '.' . $builder->deletedField, null);
        }
        $builder = $builder->builder();
    }
    $this->query      = new DataTableQuery($builder);
    $this->columnDefs = new DataTableColumnDefs($builder);
}

authors: kangzul nicojmb


text:
Running template in RISC-V

Hi,
I'm trying to use the template inside a emulated RISC-V Qemu Ubuntu 22.04.4
I was able to compile the project via cargo build --target riscv64gc-unknown-hermit inside the vm, but now I want to run the image.
Should I use qemu inside the vm, that's gonna be a terrible experience, or can I use the image on my host system via a qemu command directly?
On my x86_64 host I used qemu-system-x86_64     -cpu qemu64,apic,fsgsbase,fxsr,rdrand,rdtscp,xsave,xsaveopt     -smp 1 -m 128M     -device isa-debug-exit,iobase=0xf4,iosize=0x04     -display none -serial stdio     -kernel release/hermit-loader-x86_64     -initrd x86_64-unknown-hermit/debug/hermit-rs-template to succesfully run the HelloWorld example
Thanks

Thanks for raising this issue!

Should I use qemu inside the vm, that's gonna be a terrible experience, or can I use the image on my host system via a qemu command directly?

You can use qemu-system-riscv64 on any host.
I have added some instructions to the loader's README in https://github.com/hermit-os/loader/pull/345. Is this sufficient for a newcomer such as you, or should we be more explicit about other architectures in this project's README too?

repo: hermit-os/hermit-rs-template


text:
Highlight the security benefits of file-based configuration

Since the publishing of the twelve-factor app manifesto, the
recommendation for environment-variable configuration has confused many
people. There are many recommendations that file-based configuration can
be much safer in various situations:

https://diogomonica.com/2017/03/27/why-you-shouldnt-use-env-variables-for-secret-data/
https://www.reddit.com/r/ruby/comments/2r38xr/a_counterpoint_to_the_twelve_factor_apps/
https://gist.github.com/telent/9742059
https://blog.doismellburning.co.uk/twelve-factor-config-misunderstandings-and-advice/

Sorry, I don't have the other languages updated. What's the procedure for that?


text:
Error on deploy

When I deploy this repo, with no changes, to a Heroku app, I get a build failure (logs below). This is surprising, since it was meant to be deployed in exactly this way.
-----> Python app detected
-----> Installing python-2.7.9
     $ pip install -r requirements.txt
       Collecting sasl (from -r requirements.txt (line 1))
         Downloading sasl-0.2.1.tar.gz
       Collecting psycopg2 (from -r requirements.txt (line 2))
         Downloading psycopg2-2.6.1.tar.gz (371kB)
       Obtaining airflow[postgres,crypto] from git+git://github.com/airbnb/airflow@ba35124d75a3ad23266c324d729e80d5267e161f#egg=airflow[postgres,crypto] (from -r requirements.txt (line 3))
         Cloning git://github.com/airbnb/airflow (to ba35124d75a3ad23266c324d729e80d5267e161f) to ./.heroku/src/airflow
         Could not find a tag or branch 'ba35124d75a3ad23266c324d729e80d5267e161f', assuming commit.
       Collecting rauth (from -r requirements.txt (line 4))
         Downloading rauth-0.7.2.tar.gz
       Collecting flask-sslify (from -r requirements.txt (line 5))
         Downloading Flask-SSLify-0.1.5.tar.gz
       Collecting six (from sasl->-r requirements.txt (line 1))
         Downloading six-1.10.0-py2.py3-none-any.whl
       Collecting alembic<0.9,>=0.8.0 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading alembic-0.8.6.tar.gz (961kB)
       Collecting celery<4.0,>=3.1.17 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading celery-3.1.23-py2.py3-none-any.whl (520kB)
       Collecting chartkick<0.5,>=0.4.2 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading chartkick-0.4.2.tar.gz
       Collecting dill<0.3,>=0.2.2 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading dill-0.2.5.tgz (60kB)
       Collecting flask<0.11,>=0.10.1 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Flask-0.10.1.tar.gz (544kB)
       Collecting flask-admin==1.2.0 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Flask-Admin-1.2.0.tar.gz (790kB)
       Collecting flask-cache<0.14,>=0.13.1 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Flask-Cache-0.13.1.tar.gz (45kB)
       Collecting flask-login<0.3,>=0.2.11 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Flask-Login-0.2.11.tar.gz
       Collecting flower<0.8,>=0.7.3 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading flower-0.7.3.tar.gz (2.5MB)
       Collecting future<0.16,>=0.15.0 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading future-0.15.2.tar.gz (1.6MB)
       Collecting gunicorn<20.0,>=19.3.0 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading gunicorn-19.4.5-py2.py3-none-any.whl (112kB)
       Collecting jinja2<3.0,>=2.7.3 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Jinja2-2.8-py2.py3-none-any.whl (263kB)
       Collecting markdown<3.0,>=2.5.2 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Markdown-2.6.6.zip (412kB)
       Collecting pandas<1.0.0,>=0.15.2 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading pandas-0.18.0.tar.gz (7.1MB)
       Collecting pygments<3.0,>=2.0.1 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Pygments-2.1.3-py2.py3-none-any.whl (755kB)
       Collecting python-dateutil<3,>=2.3 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading python_dateutil-2.5.3-py2.py3-none-any.whl (201kB)
       Collecting requests<3,>=2.5.1 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading requests-2.9.1-py2.py3-none-any.whl (501kB)
       Collecting setproctitle<2,>=1.1.8 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading setproctitle-1.1.9.tar.gz
       Collecting sqlalchemy<0.10,>=0.9.8 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading SQLAlchemy-0.9.10.tar.gz (4.3MB)
       Collecting statsd<4.0,>=3.0.1 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading statsd-3.2.1-py2.py3-none-any.whl
       Collecting thrift<0.10,>=0.9.2 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading thrift-0.9.3.tar.gz
       Collecting cryptography>=0.9.3 (from airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading cryptography-1.3.1.tar.gz (383kB)
       Collecting Mako (from alembic<0.9,>=0.8.0->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Mako-1.0.4.tar.gz (574kB)
       Collecting python-editor>=0.3 (from alembic<0.9,>=0.8.0->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading python-editor-1.0.tar.gz
       Collecting kombu<3.1,>=3.0.34 (from celery<4.0,>=3.1.17->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading kombu-3.0.35-py2.py3-none-any.whl (240kB)
       Collecting pytz>dev (from celery<4.0,>=3.1.17->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading pytz-2016.4-py2.py3-none-any.whl (480kB)
       Collecting billiard<3.4,>=3.3.0.23 (from celery<4.0,>=3.1.17->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading billiard-3.3.0.23.tar.gz (151kB)
       Collecting Werkzeug>=0.7 (from flask<0.11,>=0.10.1->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading Werkzeug-0.11.9-py2.py3-none-any.whl (306kB)
       Collecting itsdangerous>=0.21 (from flask<0.11,>=0.10.1->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading itsdangerous-0.24.tar.gz (46kB)
       Collecting wtforms (from flask-admin==1.2.0->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading WTForms-2.1.zip (553kB)
       Collecting tornado>=3.2.0 (from flower<0.8,>=0.7.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading tornado-4.3.tar.gz (450kB)
       Collecting MarkupSafe (from jinja2<3.0,>=2.7.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading MarkupSafe-0.23.tar.gz
       Collecting numpy>=1.7.0 (from pandas<1.0.0,>=0.15.2->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading numpy-1.11.0-cp27-cp27m-manylinux1_x86_64.whl (15.3MB)
       Collecting idna>=2.0 (from cryptography>=0.9.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading idna-2.1-py2.py3-none-any.whl (54kB)
       Collecting pyasn1>=0.1.8 (from cryptography>=0.9.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading pyasn1-0.1.9-py2.py3-none-any.whl
       Collecting enum34 (from cryptography>=0.9.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading enum34-1.1.4-py2.py3-none-any.whl (61kB)
       Collecting ipaddress (from cryptography>=0.9.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading ipaddress-1.0.16-py27-none-any.whl
       Collecting cffi>=1.4.1 (from cryptography>=0.9.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading cffi-1.6.0.tar.gz (397kB)
       Collecting anyjson>=0.3.3 (from kombu<3.1,>=3.0.34->celery<4.0,>=3.1.17->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading anyjson-0.3.3.tar.gz
       Collecting amqp<2.0,>=1.4.9 (from kombu<3.1,>=3.0.34->celery<4.0,>=3.1.17->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading amqp-1.4.9-py2.py3-none-any.whl (51kB)
       Collecting backports.ssl-match-hostname (from tornado>=3.2.0->flower<0.8,>=0.7.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading backports.ssl_match_hostname-3.5.0.1.tar.gz
       Collecting singledispatch (from tornado>=3.2.0->flower<0.8,>=0.7.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading singledispatch-3.4.0.3-py2.py3-none-any.whl
       Collecting certifi (from tornado>=3.2.0->flower<0.8,>=0.7.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading certifi-2016.2.28-py2.py3-none-any.whl (366kB)
       Collecting backports-abc>=0.4 (from tornado>=3.2.0->flower<0.8,>=0.7.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading backports_abc-0.4-py2.py3-none-any.whl
       Collecting pycparser (from cffi>=1.4.1->cryptography>=0.9.3->airflow[postgres,crypto]->-r requirements.txt (line 3))
         Downloading pycparser-2.14.tar.gz (223kB)
       Installing collected packages: six, sasl, psycopg2, sqlalchemy, MarkupSafe, Mako, python-editor, alembic, anyjson, amqp, kombu, pytz, billiard, celery, chartkick, dill, Werkzeug, jinja2, itsdangerous, flask, wtforms, flask-admin, flask-cache, flask-login, backports.ssl-match-hostname, singledispatch, certifi, backports-abc, tornado, flower, future, gunicorn, markdown, python-dateutil, numpy, pandas, pygments, requests, setproctitle, statsd, thrift, idna, pyasn1, enum34, ipaddress, pycparser, cffi, cryptography, airflow, rauth, flask-sslify
         Running setup.py install for sasl: started
           Running setup.py install for sasl: finished with status 'error'
           Complete output from command /app/.heroku/python/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-1eO0Xp/sasl/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-eDjHFH-record/install-record.txt --single-version-externally-managed --compile:
           running install
           running build
           running build_py
           creating build
           creating build/lib.linux-x86_64-2.7
           creating build/lib.linux-x86_64-2.7/sasl
           copying sasl/__init__.py -> build/lib.linux-x86_64-2.7/sasl
           running egg_info
           writing requirements to sasl.egg-info/requires.txt
           writing sasl.egg-info/PKG-INFO
           writing top-level names to sasl.egg-info/top_level.txt
           writing dependency_links to sasl.egg-info/dependency_links.txt
           warning: manifest_maker: standard file '-c' not found

           reading manifest file 'sasl.egg-info/SOURCES.txt'
           reading manifest template 'MANIFEST.in'
           writing manifest file 'sasl.egg-info/SOURCES.txt'
           copying sasl/saslwrapper.cpp -> build/lib.linux-x86_64-2.7/sasl
           copying sasl/saslwrapper.h -> build/lib.linux-x86_64-2.7/sasl
           copying sasl/saslwrapper.pyx -> build/lib.linux-x86_64-2.7/sasl
           running build_ext
           building 'sasl.saslwrapper' extension
           creating build/temp.linux-x86_64-2.7
           creating build/temp.linux-x86_64-2.7/sasl
           gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -Isasl -I/app/.heroku/python/include/python2.7 -c sasl/saslwrapper.cpp -o build/temp.linux-x86_64-2.7/sasl/saslwrapper.o
           cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default]
           In file included from sasl/saslwrapper.cpp:254:0:
           sasl/saslwrapper.h:22:23: fatal error: sasl/sasl.h: No such file or directory
            #include <sasl/sasl.h>
                                  ^
           compilation terminated.
           error: command 'gcc' failed with exit status 1

           ----------------------------------------
       Command "/app/.heroku/python/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-1eO0Xp/sasl/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-eDjHFH-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-1eO0Xp/sasl/
 !     Push rejected, failed to compile Python app

This is caused when you try to deploy the app the typical way (directly from a GitHub repo) instead of via heroku docker:release.

repo: heroku/heroku-airflow

license: isc


text:
Create a HEROKU_RELEASE_ID file with a UUID4

I humbly think Heroku should do this by default in every buildpack; the
choice of UUID4 was borderline arbitrary, any unique ID will be fine.
Quoting http://www.12factor.net/build-release-run
"Every release should always have a unique release ID, such as a
timestamp of the release (such as 2011-04-06-20:32:17) or an
incrementing number (such as v100). Releases are an append-only ledger
and a release cannot be mutated once it is created. Any change must
create a new release."

Currently, every release does have an incrementing number. Take a look:

Currently, every release does have an incrementing number. Take a look:

OK, how can running app code know which release it is running at?
(for example, to display it in debug output, or decide on caching
invalidation)
(and thanks for the lightning quick response!)
On Sun, Jan 1, 2012 at 8:35 AM, Kenneth Reitz <
reply@reply.github.com

wrote:

Currently, every release does have an incrementing number. Take a look:

Reply to this email directly or view it on GitHub:
https://github.com/heroku/heroku-buildpack-python/pull/20#issuecomment-3323905

OK, how can running app code know which release it is running at?
(for example, to display it in debug output, or decide on caching
invalidation)
(and thanks for the lightning quick response!)
On Sun, Jan 1, 2012 at 8:35 AM, Kenneth Reitz <
reply@reply.github.com

wrote:

Currently, every release does have an incrementing number. Take a look:

Reply to this email directly or view it on GitHub:
https://github.com/heroku/heroku-buildpack-python/pull/20#issuecomment-3323905

Interesting. The only way that comes to mind at the moment is hitting the API. You can use heroku.py to do that pretty easily: https://github.com/heroku/heroku.py

Interesting. The only way that comes to mind at the moment is hitting the API. You can use heroku.py to do that pretty easily: https://github.com/heroku/heroku.py

Hmm, OK, that's not a bad idea. But still, it's easier and "less moving
parts" to have a file / environment variable.
Would you accept a pull request so the buildpack will hit the API so as to
create a HEROKU_RELEASE_ID file with the correct ID?
On Sun, Jan 1, 2012 at 8:44 AM, Kenneth Reitz <
reply@reply.github.com

wrote:

Interesting. The only way that comes to mind at the moment is hitting the
API. You can use heroku.py to do that pretty easily:
https://github.com/heroku/heroku.py

Reply to this email directly or view it on GitHub:
https://github.com/heroku/heroku-buildpack-python/pull/20#issuecomment-3323925

Hmm, OK, that's not a bad idea. But still, it's easier and "less moving
parts" to have a file / environment variable.
Would you accept a pull request so the buildpack will hit the API so as to
create a HEROKU_RELEASE_ID file with the correct ID?
On Sun, Jan 1, 2012 at 8:44 AM, Kenneth Reitz <
reply@reply.github.com

wrote:

Interesting. The only way that comes to mind at the moment is hitting the
API. You can use heroku.py to do that pretty easily:
https://github.com/heroku/heroku.py

Reply to this email directly or view it on GitHub:
https://github.com/heroku/heroku-buildpack-python/pull/20#issuecomment-3323925

I like the idea of an environment variable. I'm sure type of thing has been discussed before, but I'll bring it up internally.

To be honest, I wouldn't accept that pull request. A change like that shouldn't be limited to only the python build pack.

I like the idea of an environment variable. I'm sure type of thing has been discussed before, but I'll bring it up internally.

To be honest, I wouldn't accept that pull request. A change like that shouldn't be limited to only the python build pack.

Fair enough on both accounts,I'll be happy if you let me know how this
evolves.
Thanks for the speedy reply, you're a 24/7 overlord! :)
On Sun, Jan 1, 2012 at 8:59 AM, Kenneth Reitz <
reply@reply.github.com

wrote:

I like the idea of an environment variable. I'm sure type of thing has
been discussed before, but I'll bring it up internally.

To be honest, I wouldn't accept that pull request. A change like that
shouldn't be limited to only the python build pack.

Reply to this email directly or view it on GitHub:
https://github.com/heroku/heroku-buildpack-python/pull/20#issuecomment-3323948

Fair enough on both accounts,I'll be happy if you let me know how this
evolves.
Thanks for the speedy reply, you're a 24/7 overlord! :)
On Sun, Jan 1, 2012 at 8:59 AM, Kenneth Reitz <
reply@reply.github.com

wrote:

I like the idea of an environment variable. I'm sure type of thing has
been discussed before, but I'll bring it up internally.

To be honest, I wouldn't accept that pull request. A change like that
shouldn't be limited to only the python build pack.

Reply to this email directly or view it on GitHub:
https://github.com/heroku/heroku-buildpack-python/pull/20#issuecomment-3323948

Hehe, my pleasure. I'll update this thread if/when anything comes of the discussion.
Happy new year!

Hehe, my pleasure. I'll update this thread if/when anything comes of the discussion.
Happy new year!

authors: kennethreitz yaniv-aknin

repo: heroku/heroku-buildpack-python


text:
Add supports to make up for missing values

This pull request is to Add support to make up for missing values.

Create a new module Compensable
Introduce replace_with(booleans, replacements) => vector

Using Arrow's ternary function replace_with_mask
Accepts Vector, Array, Arrow::Array for booleans and replacements
Scalar value in replacements is broadcasted
Up cast by replacements

Introduce new VectorArgumentError, VectorTypeError

This will be a general case for compensating operations.

Add assertion helper for the arrays with NAN

Because Float::NaN != Float::NAN

Introduce Vector#fill_nil_backward/fill_nil_forward to replace nil with adjacent elements.

Add capability to replace with nil to Vector#replace_with

vector = RedAmber::Vector.new(['A', 'B', 'NA'])
vector.replace_with(vector == 'NA', nil)
# =>
#<RedAmber::Vector(:string, size=3):0x000000000000f8ac>
["A", "B", nil]

Use arguments as replace_with(boolean, replacements = nil)


text:
🛑 Software Center - Test 1 is down

In 3793cea, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 7c7d979.

repo: herrphon/upptime


text:
🛑 Software Center - Test 1 is down

In 7649e85, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 91236a3.


text:
🛑 Software Center - Test 1 is down

In 688688d, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 520c9c3.


text:
🛑 Auth-Bridge - Test 1 is down

In 38c7da7, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in b5d9be0.


text:
🛑 Software Center - Test 1 is down

In 6b07263, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in f59ba5b after 672 days, 17 hours, 42 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In fa2853e, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 06e52b0 after 54 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In 15d7c5d, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in c80d8b5 after 20 minutes.


text:
🛑 Software Center - Test 1 is down

In a6a77f7, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 463fbfb after 19 minutes.


text:
🛑 Software Center - Test 1 is down

In a6ff1c9, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in ba9e201.


text:
🛑 Software Center - Test 1 is down

In a5f3c9d, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in b0bc5ba.