yaml_cpp_0_3: 0.3.0-0 in 'indigo/distribution.yaml' [bloom]

Increasing version of package(s) in repository yaml_cpp_0_3 to 0.3.0-0:

upstream repository: https://github.com/stonier/yaml_cpp_0_3.git
release repository: https://github.com/yujinrobot-release/yaml_cpp_0_3-release.git
distro file: indigo/distribution.yaml
bloom version: 0.5.16
previous version for package: null

yaml_cpp_0_3
* renamespaced library and headers (yaml->yaml-0.3) to avoid system v0.5 conflict

We usually try not to re-add third party and try to use the upstream ones. I'll let @tfoote take a decision on that one.

Of course - I usually try and do the same.
The why of it - system yaml_cpp (v0.5) now uses boost. This was rather controversial as yaml_cpp was  a favourite for very embedded projects. The author ultimately decided to keep the boost dependency, but still maintains a v0.3 release for embedded projects.
We use yaml_cpp in cross-compiled projects (via catkin) that do not use boost (nor roscpp and beyond). There is simply not any way to do this with the system yaml cpp.
Note that this package has headers and libraries namespaced appropriately to avoid conflicts.

Totally makes sense. Wouldn't creating a libyaml-cpp0.3 key in rosdep work ? Pointing to http://packages.ubuntu.com/trusty/libyaml-cpp0.3

No - that one can't be installed alongside (isn't renamed). i.e. it conflicts with the 0.5 version. And it doesn't help with a cross compiled project either - having it as a simple catkin project lets us build a deb for it when testing on the desktop and also provides sources that catkin cross compilations can consume with ease.

It's unfortunate, but I think this might be the best approach. With the full renamspacing it should not collide with symbols.


Can I use precompiled binaries on windows?

Hello friends, I see in the releases page that there's a precompiled binary (?) for windows. However, when I try to install {:exqlite, "~> 0.16"}, I get:
could not compile dependency :exqlite, "mix compile" failed. Errors may have been logged above. You can recompile this dependency with "mix deps.compile exqlite --force", update it with "mix deps.update exqlite" or clean it with "mix deps.clean exqlite"
==> hellosqlite3
** (Mix) "nmake" not found in the path. If you have set the MAKE environment variable, please make sure it is correct.

meaning it tries to compile it and doesn't use the precompiled binaries. I tried passing config :exqlite, make_force_build: false to my config.exs but nothing changed. What am I doing wrong?

@cocoa-xu would you happen to know why the precompiled binary is not being picked up in the Windows environment?

Hi @spapas, as the error message prompted, it appears that nmake is not found on your system. There are 2 possible reasons that I can think of for now:

make, ships with Visual Studio, is not installed
you're not in the Visual Studio developer command prompt

So, for the first case, if you haven't installed any version of Visual Studio, you'll need to download and install one (community version is okay).
But if you already have Visual Studio installed, you need to be in the Visual Studio developer command prompt. Basically, it will update the PATH environment variable so that nmake can be found. Reference link: https://learn.microsoft.com/en-us/cpp/build/building-on-the-command-line?view=msvc-170

Oh, one more reason is that maybe you're using OTP 26 on Windows, and the precompiled version isn't available yet.

@cocoa-xu thank you for the tips. Yes, I am using otp-26.
Any idea when the precompiled binaries for otp-26 will be available?
Thank you

@spapas It should be there once adding OTP 26 to the precompile.yml and then releasing a minor update. :)
/cc @warmwaffles

Fix has been released under v0.16.1

Hello, unfortunately I still get the same behavior; the pre-compiled binaries aren't used.
Here's my elixir/erlang version:
Erlang/OTP 26 [erts-14.1.1] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [jit:ns]
Interactive Elixir (1.15.6) - press Ctrl+C to exit (type h() ENTER for help)

Also here's the exqlite package:
* exqlite (Hex package) (mix)
  locked at 0.16.1 (exqlite) 4d40bbb6

However I still see the same when compiling:
C:\progr\elixir\robbin>mix deps.compile exqlite
==> exqlite
could not compile dependency :exqlite, "mix compile" failed. Errors may have been logged above. You can recompile this dependency with "mix deps.compile exqlite --force", update it with "mix deps.update exqlite" or clean it with "mix deps.clean exqlite"

** (Mix) "nmake" not found in the path. If you have set the MAKE environment variable, please make sure it is correct.

Hello, unfortunately I still get the same behavior; the pre-compiled binaries aren't used.

Ahh, I missed this line in mix.exs. It should be changed to
Enum.member?(["2.16", "2.17"], nif_version)

bah okay I'm on it

Okay this time, I hope @spapas. Fix released with v0.16.2.

@warmwaffles yes! Finally it works:
==> exqlite
Downloading precompiled NIF to c:/Users/serafeim/AppData/Local/Cache/exqlite-nif-2.17-x86_64-windows-msvc-0.16.2.tar.gz

Thank you!

No problem @spapas, please open more tickets if you run into any windows specific issues. I don't use windows regularly and do not have a dev environment set up for it. Feedback on that experience is greatly appreciated.


Conditional return types for collections

Resolves #158
This adds conditional return types for collections so that phpstan knows which collection type is being returned (DataCollection, PaginatedDataCollection, CursorPaginatedDataCollection)
There is an issue and that is that it doesn't seem to properly work with interfaces, so (for now) it checks for the CursorPaginator and Paginator classes rather than interfaces.
Once that bug has been fixed we can update the conditional return type to check for the contracts, but it still might be worth getting this in before that.

I think it's fine to support just Laravel's native paginators for now as that will resolve this issue for the majority of the users.

Is the types/collection.php file required?

@rubenvanassche it's not required for the functionality. It's kind of like a test file for types that gets checked by phpstan to ensure that it works and keeps working in the future. It's similar to how Laravel does this: https://github.com/laravel/framework/tree/9.x/types

Didn't know about that one, great! Thanks!


Overlayering is no longer possible on version 10.*

Please add a clarification to which versions allow overlayering. My understanding is 10.* does not support overlayering. Nothing on this page indication that. This page contradicts the page 2 levels up:
https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/extensibility-home-page
Thanks!

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

ID: e561707c-b588-dd5a-6f90-ffa99cc3a824
Version Independent ID: 8d54840a-d5df-0e5f-2765-dbccf044acce
Content: Customize through extension and overlayering - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/extensibility/customization-overlayering-extensions.md
Service: dynamics-365-cross-app
Product: ****
Technology: ****
GitHub Login: @gianugo
Microsoft Alias: gianura

Bug 759261 has been logged to address this issue.

Thanks for your feedback. We are closing this issue because we are either unable to find relevant information or reproduce this. If you're still experiencing the issue described here, please reopen or create a new issue.


Wondering if the proxy nca is just the softmax loss

In the experiment of proxy NCA, the number of proxies is set to the number of classes of training set. So what is the difference between proxy NCA and pure softmax loss?

They are related, but not the same. See https://arxiv.org/pdf/1909.05235.pdf, p. 4, remark 3 for a detailed comparison between both losses.


Fix: Listeners not honoring multiple failures for subscription

Problem:

If a call fails when subscribing, the caller will get an error back.
However if they call again, then the caller will see success despite the listener never actually getting set.

Fix:

Remove the listener from promise list if failure

:tada: This PR is included in version 3.0.0-next.11 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Initial draft of cloud configuration requirements

General guidelines to address #663. I've left exact implementation details out and tried to stay with general requirements (which I suspect will be controversial enough in some cases).

Superceded by #987


core: create esm build for js

Other packages, like Button, do esm and cjs alongside.  Core does not.  It should.  This will allow treeshaking through their module bundlers.
Once esm/cjs builds adjusted, make sure to adjust main/module fields in package.json.
Best case, the dist matches the format of other components.
~Changes to dist paths in this package may mean a breaking change.  This is because teams often are referencing node_modules path or unpkg paths if they don't have something like postcss-import setup.~
I actually don't think this is a breaking change, because the style field is what's used in postcss-import.

Non issue.  module points to js/index.js in src, esm, already.


Add new canonical metamodel and converter from current specification

This PR adds a new canonical metamodel for API specifications, and the tools to convert it from the existing specification.
Usage:
cd ./specification
npm run generate-schema
...
Schema generated in ../output/schema/schema.json

This reads the TypeScript spec definition in spec and writes its JSON representation.
Note that not all types are output as the converter starts from the endpoints and recursively traverses type definitions from the endpoint's request and response definitions. There are some type declarations in spec that are not in this graph, and they're left out of the generated schema.
Benefits of this new model:

no redundancy: every piece of information only exists once
simplified data model: some data structures were flattened, some types removed as they can be expressed by means of other types (e.g. string and number aliases)
can be serialized as JSON! This means code generators don't have to be written in TypeScript.

Main differences with the existing specification model:

InstanceOf and ValueOf have their names swapped to better match the actual semantics of "instance" (instance of a particular type) and "value" (some value that can have many different forms).
SingleKeyDictionary is renamed to NamedValue because it's really a (string, <value>) tuple and not a dictionary with arbitrary keys constrained to contain only a single entry.
StringAlias and NumberAlias are merged within TypeAlias which can also be used for arbitrary type aliases.
UnionAlias is renamed to Union.
UserDefinedValue is replaced by the internal object type, like what is generated for any. I'm not sure that we really need UserDefinedValue in addition to any and generic request/response parameters. If needed, it would be better represented as an additional internal type rather than a first-class metamodel construct.
descriptions found in the Rest API spec are moved to type and property definitions.

@Mpdreamz can you point me to examples in the .Net client?
I understand that this is for situations where the user-defined type is in deeply nested structures where bubbling the generic parameter up to the top-level type would be impractical? Or in a dynamic context such as collections where each item can accept a different user-defined type?
Why do we lose semantics compared to object (or any in TS)? Can't we just say that any field of type object should be generated in a form that allows the user to provide either an object and the serializer/deserializer or just raw JSON?

understand that this is for situations where the user-defined type is in deeply nested structures where bubbling the generic parameter up to the top-level type would be impractical? Or in a dynamic context such as collections where each item can accept a different user-defined type?

Both

Why do we lose semantics compared to object (or any in TS)? Can't we just say that any field of type object should be generated in a form that allows the user to provide either an object and the serializer/deserializer or just raw JSON?

Sometimes a string is just a string and object is just an object but I think the spec benefits from type aliases to both in most cases.
I don't want folks reaching for object/any and call it job done.

I don't want folks reaching for object/any and call it job done.

Ok, so the semantics is more about psychology, like "think twice before writing UserDefinedValue" compared to just throwing in any when you don't want to put more thinking in a non trivial situation, right?
So I'm ok with reintroducing UserDefinedValue but then we should forbid any in the specs. WDYT?

I'm down with that :)
Forcing type aliases also promotes reuse of concepts and the types can be documented.
A property is never anything it's always something :badadoom:

Great, I added back UserDefinedValue!
I'd love @delvedor's opinion too 😉

I added a commit to rename _kind to kind. I initially used a _ prefix to denote a technical attribute since it allows disambiguating the type, but as an interchange format it becomes a first-class citizen of the semantics. Plus the _ prefix is often used to indicate private fields, which isn't the case.

I would like to change the request body definition to something more explicit like this:
export class Request extends BaseType {
  // ...
  body?: ValueBody | PropertiesBody;
}

export class ValueBody {
  kind: "value";
  value: ValueOf;
}

export class PropertiesBody {
  kind: "properties";
  properties: Property[];
}

When implementing the model in Java, I found out that the current definition as body?: ValueOf | Property[] makes serialization and deserialization a bit complex. The Jackson library can distinguish variants based on a property value, but not from the "shape" of the JSON (an object or array) and I had to write custom (de)serializers for this.
The same problem will happen in Rust and probably other strongly typed languages.
@delvedor are you ok with this?

I've rebased the PR on master and updated the body definition.

What are everyone's thoughts on having a generated instance of the spec living in the repository rather than only housing the tools to create the JSON spec?
I know it's typically bad form to store artifacts that are generate-able, however if the end goal of this spec is to be taken by many different languages it'd be simpler to grab the spec at a certain URL/path and use rather than running the generator each on our own for each spec update.
To make sure the spec stays up to date could add a unit test that ensures that the committed spec matches what would be generated by the generator.

@sethmlarson +1, and that was actually my intention. I did not do it while the format definition was still in flux, but will add it before merging the PR.
+1 for the unit test, and we can also have a commit hook that prevents forgetting to update the generated JSON version.
Having the spec as JSON is indeed important for tools in other repos that use it as a starting point, and can then use the same approach as what we do with the ES Rest specs, i.e. download a specific tag/branch/sha1 from the ES git repo without having to include the translation tool in their own build system.


Various improvements to docs

Adds section on Globus Auth
Adds section on Datatypes, validation, caching, and flask helpers
Better transitions/guiding in docs
Make graphics fit webpages better
Merges info pre-existing docs with new docs

To build the docs locally to view via browser:
cd docs/
poetry run make html
open build/html/index.html

@jimPruyne this PR is pretty much docs only. While not exactly touching on Flows, it does help round out some of the documentation on ActionProviders (mainly adds sections on Globus Auth to readthedocs)

@urimandujano How much of this is new, and how much is refactoring of older docs? There's a lot here, particularly in the changeset, so I want to make sure I"m focusing on the most important bits in reviewing.
Thanks for any pointers that help me narrow it down.

Good question - most of the content was already in the README.rst under different sections. What this PR does is break the content out into their own RST files and include those new files in the readthedocs source tree.  I merged sections in the README.rst with other docs that were lying around, as well as generally updating and making sure descriptions/instructions were up to date.  The more substantial files are:

docs/source/setting_up_auth.rst
docs/source/toolkit.rst
docs/source/toolkit/authentication.rst
docs/source/toolkit/caching.rst
docs/source/toolkit/data_types.rst
docs/source/toolkit/flask_helpers.rst
docs/source/toolkit/validation.rst

Thanks for the review/contribution! This will hopefully be one of the last dense diffs for the repo.


Unable to amplify mock if developer opted to not make changes to backend during initial amplify pull

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
yarn
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
7.6.12
What operating system are you using?
n/a
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Amplify Categories
function, api
Amplify Commands
Not applicable
Describe the bug
Amplify Command: mock (option isn't in dropdown)
Running amplify mock fails if the developer selected NO to modifications on backend on initial amplify pull
Expected behavior
running amplify mock api should work
Reproduction steps

run amplify pull initially
select No for do you plan on modifying this backend
run amplify mock api
failure

GraphQL schema(s)
No response
Log output
No response
Additional information
No response

Workaround:
delete contents of amplify folder, run amplify pull, answer YES for modifying a backend

Hi @mauerbac
I don't this is a bug . This is the case where Cx have multiple frontends and they want to use the same backend. You can find the details here : https://docs.amplify.aws/cli/teams/multi-frontend/
Choosing  N when asked do you plan on modifying this backend will only generate the frontend definations based on type of frontend selected i.e. aws-exports.js  or amplifyconfiguration.json using the same backend.
Choosing Y will also download the amplify folder where backend definitions are stored and ay attempt to modify backend or using mock with give an error that amplify folder doesnt exist.
Let me know if this answers your question?

\cc @renebrandel @swaminator for flow considerations on DX for when we choose not to modify backend on pull


Do a deep dive into Luminal

https://github.com/jafioti/luminal
From-scratch framework in Rust. Mentioned on the TinyGrad discord.

There is not enough time... Priorities for backends and inspirations: tinygrad, triton, xla.


The example screenshot vanished?

The example screenshots at Visual Studio Marketplace was vanished?
https://marketplace.visualstudio.com/items?itemName=tobiasalthoff.atom-material-theme

Thanks for the reminder. I had yet to release a new version :-)


docs(README): fix typo & update instructions

Fixed a typo in "respective" on line 24

Looks great!


Explain how to customize pages that are not compatible with Login/template.tsx

// This piece of code has no use is some pages, if then how to customize these parts of page
<div id="kc-header" className={getClassName("kcHeaderClass")}>
 </div>

All i need is how to remove that logo from the page :^)

Hello @useEffects, (cool GitHub handle btw)
What page are you talking about specifically?  login-reset-password.ftl?
I assume not but just to be sure...

Well, just remove this block, the logo will disapear:
https://github.com/keycloakify/keycloakify-starter/blob/a18a51d4fd816940d64a5e8513aceab0e6701e76/src/keycloak-theme/login/Template.tsx#L60-L75
It's this line in particular:  https://github.com/keycloakify/keycloakify-starter/blob/a18a51d4fd816940d64a5e8513aceab0e6701e76/src/keycloak-theme/login/Template.tsx#L71


Updated license link

Current coverage is 33.64%

Merging #15 into master will not affect coverage as of b6d615c

@@            master     #15   diff @@
======================================
  Files            1       1
  Stmts          211     211
  Branches         0       0
  Methods
======================================
  Hit             71      71
  Partial          0       0
  Missed         140     140

Review entire Coverage Diff as of b6d615c

Powered by Codecov. Updated on successful CI builds.


Add security policy and corresponding issue template

Ref. #660

@treiher Added email address to report security vulnerabilities. Please have a look.

Left the [no ci] tag in the commit message so the checks wouldn't run. @treiher please approve again.


Shortcut icons aren't "adaptives"

The four shortcuts (Scan, History…) icons have two problems:

Their backgrounds should be white (the same as the app icon)
They should be "adaptive", just like the app icon

Fixed by #4572


Post idea - Using git as objects

Using git as objects
Walk thru using git in PowerShell (with full object pipeline support)

Are you offering to write the post [Y/N]: Y
Proposed title: Using Git in PowerShell
Links to related posts: ugit
Description of the problem/scenario/question you want covered:

git basics
Using git in PowerShell
Piping output from git

@StartAutomating Looking forward to your PRs.


Try to keep proper timestamps in WriteSample.

Use

PacketTimestamp
Timestamp
Duration
PrevDroppedPackets

of Sample to figure out RTP timestamp of next sample.
Tested with livekit-cli publishDemo. Please suggest more testing scenarios.

Going to merge this and tag it. And update livekit-cli with it.

Ingress would be affected by this change fairly significantly. It should allow us to remove the code that paces sending the packets to the SDK based on the timestamps, but we need to test this thoroughly in that use case.


Fix CI plz

Hacking about with https://github.com/lwm/tasty-discover/issues/119.


Demonstrate OpenTelemetry + dependency injection

Hi Temporal folks! Here's a doc change for something I figured out that I wish was called out in the docs. Feel free to reword this as you wish.
What was changed

Add an example of configuring OpenTelemetry with dependency injection to src/Temporalio.Extensions.OpenTelemetry/README.md.
Why?

src/Temporalio.Extensions.OpenTelemetry/README.md doesn't contain an example of how to configure OpenTelemetry when using dependency injection. It's pretty easy to figure out how to configure the client by also reading the src/Temporalio.Extensions.Hosting/README.md, but if one uses a hosted worker, it typically has to be configured separately. This is a common pitfall (according to
https://temporalio.slack.com/archives/C012SHMPDDZ/p1699016782885319?thread_ts=1698974629.231319&cid=C012SHMPDDZ at least), so document this.
Checklist

Closes

NA

How was this tested:

NA

Any docs updates needed?

NA

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Glen seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Updated and removed some cruft from the project I copy-pasted from.


[Feature request / Question] Alternative way to notify end users about issues

Hi,
Thanks for developing this gem, I found this gem very useful.
To my mind log file is a good way to communicate issues.
I wanted to improve the management of reported issues (like resolving, skipping, UI)
I was able to implement is by parsing a log file and storing them in database.
It would be nice to have something like ActiveSupport::Notifications for the reporting purpose.
In my case it will replace log file parsing (which is not scalable) and maybe will allow to ignore issues I'm not intended to fix (like some things in layout, that are common to many pages)
What do you think?
Thanks

Hi, I'm happy you find it useful!

I wanted to improve the management of reported issues (like resolving, skipping, UI)

Can you give more details about your use case?

In development mode I want to build an UI with following features

ability to list distinct issues
ability to sort / filter issues
mark issue as resolved or ignored

Based on your work I created the following model
  create_table :column_trace_records do |t|
      t.string :action
      t.integer :count
      t.string :model
      t.text :used
      t.text :unused
      t.text :backtrace
      t.boolean :resolved
      t.index [:model, :used, :backtrace], name: 'issue_idx', unique: true
    end

And ability to subscribe to events stream and create / update these records would simplify my implementation

I think, ActiveSupport::Notifications is not necessarily needed in this case. I can create something like "reporters", where you can specify your custom reporter. It will be passed all the details like backtrace, used/unused columns etc. With the logger reporter as a default one, to mimic the current behaviour.
I did something similar in my other gem - https://github.com/fatkodima/data_checks/tree/master/lib/data_checks/notifiers. In that case it is named "notifiers", but the concept is the same.
Wdyt?

I like this concept.

Ok, I will look then into it. If you would like to work on a PR by yourself, please let me know.

Release a new version with this change.


fix build and test failures on windows

Coverage decreased (-0.01%) to 81.32% when pulling 8ef35137b165453bedc4e4ab0691d05630ea5e68 on j/windows into b062d055613506f4e3d13c8aa631c753d383575c on master.


Add NonPositiveInt scalar

Add NonPositiveInt scalar type to HotChocolate.Types.Scalars

#3026

Part of #2927

Merged, Thanks for the Contribution


Properly generate secrets files

This allows for the new secrets variables to be added to the
existing secrets files without leaving any of the new secrets
ungenerated. This is necessary because we introduce new secrets
in Mitaka. The old method would just leave out the new ones
causing errors.
Connects https://github.com/rcbops/u-suk-dev/issues/475
(cherry picked from commit 01d08b82dd972554e352036af83dd7f9f18c170d)

backport looks clean, good if passing

tempest failure -- recheck_upgrade

recheck_upgrade

00:58:18 TASK: [os_tempest | Locate archives] ******************************************
00:58:18 failed: [jrpcaioiad-5cb_utility_container-1732d4da] => {"changed": true, "cmd": "ls -1 /opt/images | grep '.gz'", "delta": "0:00:00.005732", "end": "2016-12-06 00:58:18.055305", "rc": 1, "start": "2016-12-06 00:58:18.049573", "warnings": []}
00:58:18
00:58:18 FATAL: all hosts have already failed -- aborting
recheck_upgrade

@cloader89 Gate is currently broken until https://github.com/rcbops/jenkins-rpc/pull/684 merges. If you get the chance, could you merge that?

recheck_upgrade


Support specify property arguments variables for mount points

Is your feature request related to a problem? Please describe.
We should support specify system properties for mount points, so that each ufs can have different envirenment.
Describe the solution you'd like
Support specify system property for mount command
Something like

bin/alluxio fs mount /alluxio hdfs://ns1/ --property key=value

Describe alternatives you've considered
Modify the mount info
Urgency
Yeah
Additional context
Not sure

@kuszz Would you like to take a look at this PR?

@kuszz Would you like to take a look at this PR?

ok

What‘s the difference from the existing command alluxio fs mount xxx --option key=value

What‘s the difference from the existing command alluxio fs mount xxx --option key=value

Hello, I think the --option is used for AlluxioConfiguration, and --propertry will be used for System.property, as line 174 in HdfsUnderFileSystem.java. And we find the System.pros is sharing between different HdfsUnderFileSystem object, it seems wrong at line 174, do you have some good ideas?
 ClassLoader currentClassLoader = Thread.currentThread().getContextClassLoader();
    try {
      Thread.currentThread().setContextClassLoader(hdfsConf.getClassLoader());
      if (mUfsConf.isSet(PropertyKey.HADOOP_SECURITY_AUTHENTICATION)) {
        hdfsConf.set(HADOOP_AUTH_METHOD,
                mUfsConf.getString(PropertyKey.HADOOP_SECURITY_AUTHENTICATION));
      }
      if (mUfsConf.isSet(PropertyKey.HADOOP_KRB5_CONF_FILE)) {
        **System.setProperty(KRB5_CONF_FILE,
                mUfsConf.getString(PropertyKey.HADOOP_KRB5_CONF_FILE));** // line 174
      }

public static String setProperty(String key, String value) {
        checkKey(key);
        SecurityManager sm = getSecurityManager();
        if (sm != null) {
            sm.checkPermission(new PropertyPermission(key,
                SecurityConstants.PROPERTY_WRITE_ACTION));
        }

        return (String) **props**.setProperty(key, value);
    }


Export code static labeling to documentation

A rough draft on exporting the codes dataframes to documentation. Notable questions/changes/issues include:

Restructured the dictionaries in metadata.codes.py into one dictionary called CODES_METADATA mainly because it made iterating through and using each of the codes easier. Not sure if this was really the thing to do. It got a little messy.
The codes dataframes are made into CSV's before being rendered in the RST format. I checked the CSV directory in for the sake of debugging but ultimately think this should probably be a temp or cleaned up directory
I need to clean up the jinja template to handle paragraph blocks better in the descriptions
tox -e docs is failing for me (in dev and main) because of an issue importing addfips which seems like it might be a new issue that maybe I remember Trenton working on. Or maybe it's something to do with the new pudl-dev environment.
I was generally confused about Sphinx and wanted to see if the tox tests still passed so I commented out the call tostatic_dfs_to_rst in the setup in conf.py. Not entirely sure this was even the right place to call it. Need to look more into this

General To Do

[x] Figure out how Sphinx works and call static_dfs_to_rst during build
[x] Clean up CSV directory after the RST has been created
[ ] Clean up strings in CODE_DESCRIPTIONS dictionary (need to better handle paragraph breaks in RST file)
[ ] Need an assertion for the new Encoder constructor in case a code name is passed that is not in the CODES_METADATA dictionary?
[ ] Move description and doc_name field in Encoder - use Resource instead and the encoder field inside of Resource? Resource isn't necessarily built to just hold one field/code? - UPDATE: Resource is pretty equipped to hold description, doc_name, and encoder already but it already has a to_rst method so I chose to use a list of Encoders instead.
[x] Remove the generated codes_and_labels.rst file in cleanup_rst once the build is finished?

Anyways, just wanted to get some eyes on it because I felt like a lot of stuff happened in the process of me learning about the docs.

Main changes in latest commits:

Switched to using the Encoder class so now the CodeMetadata class basically holds a list of Encoders.
Added to_rst method to the Encoder class. to_rst in the CodeMetadata class just iterates through the Encoders and calls to_rst for each of them.
Added two variables to the Encoder class - description and doc_name. Instead of doing this, I thought about just using the Resource class which already has variables for description, title, and encoder but the Resource class already has its own to_rst method and generally is used to serve a different purpose.
I think I did the calls to static_dfs_to_rst and cleanup correctly with Sphinx in conf.py but it's hard to test because I don't have a fully functional environment on this borrowed computer.
Added code_fixes dictionary into the RST.

Left To Do:

[ ] Fix the jinja template so that it generates a nicely formatted RST. There are some errors right now with the RST
[ ] Get descriptions from RESOURCE_METADATA instead of writing them into CODES_METADATA
[ ] Clean up block strings of the code descriptions (need to better handle paragraph breaks in RST file)


Device recognised as unknown

Hi,
I have purchased this device:
https://www.bgelectrical.uk/smart-sockets
After a bit of digging, I found out that they use a broadlink chip:
https://community.home-assistant.io/t/uk-wifi-smart-socket-screwfix-testing/119995/5
So I though I would try using your broadlink-mqtt
Kind of works:
pi@piup:~/broadlink-mqtt $ pi@piup:~/broadlink-mqtt $ python mqtt.py
[2019-10-09 10:27:40,822] DEBUG Connected to 'Unknown' Broadlink device at '<IP_ADDRESS>' (MAC c8:f7:42:fc:e5:45) and started listening for commands at MQTT topic having prefix 'broadlink/'
[2019-10-09 10:27:40,834] DEBUG Connected to MQTT broker, subscribing to topic broadlink/#

So, it connects to the device but it is unknown
It has two sockets so I tried to force the config as an MP1 device. No dice
It tried as a single socket SP1 and then SP2. No dice
It connects, so there must be a way.
I have a spare device that I can send by post
I can also send debug logs or whatever is needed
Thanks

I think it's better to ask this question at the issue tracker of the parent project
https://github.com/mjg59/python-broadlink
If they will add support for this device then it shouldn't be a problem support it at broadlink-mqtt

Also could you please execute next command and post output here?
python
import broadlink
print hex(broadlink.discover(timeout=10)[0].devtype)

0x51e3

I have raised an issue on the broadlink repo:
https://github.com/mjg59/python-broadlink/issues/289

Thanks

There is a pull request on the base project for the device here: https://github.com/mjg59/python-broadlink/pull/290
I have a working version of your code working on my machine with the device added including a command for the LED brightness and I kept the same topic structure as the MP1 device
What do I do now?

Could you please create a pull request for your changes?
Also, it isn't clear what get_state method returns. Do you have an example of output? I need it to correctly implement sending current device state periodically

Committed reading of state parameters from BG1 device, please test

@eschava
Could you please create a pull request for your changes?
How do I do that?

@vzorglub You can just mail me your mqtt.py
<EMAIL_ADDRESS>

Done
Testing state

I don't know exactly what you added in the file so I can't add your state code in mine
I'll wait for a full version from you to test

Merged, please update

All working
Tested with json False and True
Both working
Thanks a lot

Welcome!


Subscription flips between platform management group and management management group.

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Versions

terraform: 1.0.4
azure provider: 2.71.0
module: 0.4.0
Description
Describe the bug
When using a subscription only on platform and not on management management group (and probably but not tested on the identity or connectivity) and you have set the subscription_id_management variable, the subscription flips by every apply. So when the subscription is on the platform management group the apply will move to the management management group.
Steps to Reproduce
In the module enable the management resources and set the subscription_id_management variable with the subscription needed to fill in the policies with platform subscription. In the subscription_id_overrides set the platform with the same subscription.
Then deploy the resources. All resources will be deployed and the policies that contain management resources information will contain the subscription.
Don't change the configuration and do either a plan or apply. The result will be that the subscription will be moved to the management management group.
If you apply the move and do the same the results will be to move the subscription back to platform.
Additional context
We only set subscriptions to platform and landing zone management groups and not to all the management groups separately. When I don't fill in the subscription_id_management, the policy assignments that contain linking to management resources will have the wrong subscription in the resource id. When create the assignments correctly, but the subscription flips. If there is another way to ensure the policies are created correctly it would help. Hope you can change, fix or advise.

Interesting issue... please can I confirm why you are trying to assign the management Subscription to the platform Management Group? I assume you have the association to platform declared via the subscription_id_overrides input variable?
By design, we have included logic to handle a race condition between connectivity, identity and management but not any others.

Just to add, if you are trying to implement the Trey Research scenario, we don't currently support this in the Terraform module but would be open to adding this to our backlog if this is what you are asking for?

Interesting issue... please can I confirm why you are trying to assign the management Subscription to the platform Management Group?
From an architectural perspective, the reason each Subscription has a dedicated Management Group is to ensure the correct policies are assigned to each Subscription in a way that the Subscription "Owners" cannot remove these policies unless they are also Owners of the parent Management Group(s). This is part of how the governance model is enforced.
By design, we have included logic to handle a race condition between connectivity, identity and management but not any others.

I am trying to get all the management, connectivity and identity resources in the subscription in the platform management group. Short the  Trey Research model you mentioned. It could change in the future so we chose to use platform as the placeholder for now and add relevant policies.

OK, that makes sense but isn't how we have built the logic.
If you are happy to follow our logic, simply specify the same Subscription ID in one or more of subscription_id_connectivity, subscription_id_identity and subscription_id_management and the module will place the Subscription in the expected Management Group. Do not use this in combination with subscription_id_overrides though.
Subscription placement is based on the following order or preference:

Management
Connectivity
Identity

If not, we currently don't have a mechanism to go up to Platform and I'm unsure whether this is something we plan to support as Trey Research (mentioned above) is a very specific implementation of Enterprise-scale.
Instead, my current thought is to add a mechanism (date TBC) which would ensure the archetypes from each "merged scope" are applied on the same Management Group as the Subscription. For example, if you have both management and connectivity resources in the same Subscription, we would merge the management and connectivity archetypes on the management Management Group. identity would continue to be a dedicated Management Group with the identity archetype applied.
This approach ensures that the correct governance settings are applied on the Subscription. For management, connectivity and identity these are all intentionally designed to be a 1-2-1 relationship as some Policy Assignments are specific to a single Subscription. We don't assign these to the Subscription directly though, as the inheritance based approach is more secure (a Subscription Owner cannot remove inherited policies).
I guess it may also make sense to remove the unused Management Groups, but I need to be careful not to implement "features" which are inconsistent with the architecture, or our non-Terraform based implementations.
Hope this helps?

Thank you @krowlandson. It makes sense to wait for Trey Research setup to come by. For now the deployment is not something we do on a daily basis so we can work with manual adjustments and have it documented.
One question though, will the Trey Research approach be added in this module or will it be created in a different module?

Nothing confirmed at this point regarding Trey Research, however I can look into the feasibility of adding an option to "roll-up to platform" when I look at providing a mechanism to consolidate archetype_definitions in a single platform Subscription deployment. No ETA on this though as currently focused on updating the Wiki docs to allow users to utilise the current capabilities more easily.

Re-categorising as feature request for the capabilities described in my last update.

This will be fixed when the following is implemented

#223


Q: epochs_ in evoked name

I used to create epochs from a bunch of event types, then do multiple manipulations on them ending with:
evoked = epochs['condition_1'].average()

This used to give me an evoked instance where evoked.name == 'condition_1', but now I get evoked.name == 'epochs_condition_1'. This seems like a backward-incompatible change, but somehow it has been around for over a year (git blame around line 1280 in epochs.py traces it back to @agramfort in January 2014). Is this intended behavior, or a bug? Should I just manually get rid of the epochs_ prefix for my use case?

looks like a bug to me. This epochs_ should not be there :(

Do you remember the logic you were going for? It basically sets the name of the selected object based on whether or not the orginal object had a name != 'Unknown' (but not incorporating the original name at all). I'll go ahead and fix it. Should we backport to 0.9?

yes please backport.

@agramfort done

Thx

On 3 juin 2015, at 17:24, Eric Larson<EMAIL_ADDRESS>wrote:
@agramfort done
—
Reply to this email directly or view it on GitHub.


[SPARK-32537][SQL][TEST] Add a CTEHintSuite for test coverage

What changes were proposed in this pull request?
Add a new test suite CTEHintSuite
Why are the changes needed?
This ticket is to address the below comments to help us understand the test coverage of SQL HINT for CTE.
https://github.com/apache/spark/pull/29062#discussion_r463247491
https://github.com/apache/spark/pull/29062#discussion_r463248167
Does this PR introduce any user-facing change?
No
How was this patch tested?
Add a test suite.

Test build #127092 has started for PR 29359 at commit 773eacd.

Merged build finished. Test PASSed.

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

Test build #127092 has finished for PR 29359 at commit 773eacd.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class CTEHintSuite extends PlanTest with SharedSparkSession with AdaptiveSparkPlanHelper

Merged build finished. Test PASSed.

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

cc @gatorsmile @cloud-fan

Test build #127134 has started for PR 29359 at commit 6f8a2cc.

Merged build finished. Test PASSed.

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

Test build #127135 has started for PR 29359 at commit ce94127.

Merged build finished. Test PASSed.

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

Test build #127134 has finished for PR 29359 at commit 6f8a2cc.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class CTEHintSuite extends PlanTest with SharedSparkSession

Merged build finished. Test PASSed.

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

Test build #127135 has finished for PR 29359 at commit ce94127.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class CTEHintSuite extends QueryTest with SharedSparkSession

Merged build finished. Test PASSed.

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

Test build #127176 has started for PR 29359 at commit 4256339.

Merged build finished. Test PASSed.

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

Test build #127176 has finished for PR 29359 at commit 4256339.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please

Test build #127187 has started for PR 29359 at commit 4256339.

Merged build finished. Test PASSed.

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

Test build #127187 has finished for PR 29359 at commit 4256339.

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

Merged build finished. Test PASSed.

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

Test build #127251 has started for PR 29359 at commit a7c4d32.

Merged build finished. Test PASSed.

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

Test build #127251 has finished for PR 29359 at commit a7c4d32.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

github action passed, merging to master, thanks!


Added missing "type" configuration for webhooks

Still trying each construct, I'm on the last: webhooks!
I copy/pasted the quick start to test webhooks and got an error:
  TypeError: Cannot read property 'class' of undefined
      at LiftPlugin.loadConstructs (/Users/afu/Workspaces/LiveCoding/Lift/4-webhook/node_modules/serverless-lift/dist/src/plugin.js:93:85)
      at new LiftPlugin (/Users/afu/Workspaces/LiveCoding/Lift/4-webhook/node_modules/serverless-lift/dist/src/plugin.js:83:10)
      at PluginManager.addPlugin (/Users/afu/Workspaces/LiveCoding/Lift/4-webhook/node_modules/serverless/lib/classes/PluginManager.js:112:28)
      at /Users/afu/Workspaces/LiveCoding/Lift/4-webhook/node_modules/serverless/lib/classes/PluginManager.js:158:33
      at Array.forEach (<anonymous>)
      at PluginManager.loadAllPlugins (/Users/afu/Workspaces/LiveCoding/Lift/4-webhook/node_modules/serverless/lib/classes/PluginManager.js:158:8)
      at Serverless.init (/Users/afu/Workspaces/LiveCoding/Lift/4-webhook/node_modules/serverless/lib/Serverless.js:206:30)
      at async Serverless.eventuallyFallbackToLocal (/snapshot/serverless/lib/Serverless.js:265:5)
      at async Serverless.init (/snapshot/serverless/lib/Serverless.js:194:5)
      at async /snapshot/serverless/scripts/serverless.js:441:7

I realized that the "type" property was missing for this construct, so here it is :wink:

Thank you again @Chtiadrien 😅


Error while trying to register an extension

As soon as I start Mechanic with the "Register" tab, I get this in the output window:
Exception in thread Thread-2:
Traceback (most recent call last):
  File "threading.pyc", line 808, in __bootstrap_inner
  File "threading.pyc", line 761, in run
  File "/Users/jens/Library/Application Support/RoboFont/plugins/Mechanic.roboFontExt/lib/mechanic/ui/windows/notification.py", line 20, in __init__
  File "/Users/jens/Library/Application Support/RoboFont/plugins/Mechanic.roboFontExt/lib/mechanic/ui/windows/notification.py", line 74, in get_updates
  File "/Users/jens/Library/Application Support/RoboFont/plugins/Mechanic.roboFontExt/lib/mechanic/update.py", line 25, in all
  File "/Users/jens/Library/Application Support/RoboFont/plugins/Mechanic.roboFontExt/lib/mechanic/update.py", line 39, in _fetch_updates
  File "/Users/jens/Library/Application Support/RoboFont/plugins/Mechanic.roboFontExt/lib/mechanic/extension.py", line 66, in should_update
  File "/Users/jens/Library/Application Support/RoboFont/plugins/Mechanic.roboFontExt/lib/mechanic/extension.py", line 58, in is_current_version
  File "/Users/jens/Library/Application Support/RoboFont/plugins/Mechanic.roboFontExt/lib/mechanic/extension.py", line 91, in version
  File "/Users/jens/Library/Application Support/RoboFont/plugins/Mechanic.roboFontExt/lib/mechanic/version.py", line 20, in __init__
  File "/Users/jens/Library/Application Support/RoboFont/plugins/Mechanic.roboFontExt/lib/site-packages/semversion.py", line 92, in __init__
VersionError: invalid version '2.0b2'```

Actually, I don't need to do anything, the crash occurs when Mechanic is only installed, no interaction required.

Do you know which extension has the version 2.0b2?

Ah, okay, it's an extension that is not in a public repository. It had a repository key for mechanic anyway. When I remove it, everything's fine.

I'm going to keep this open, so that I can do something in regards to capturing this error before it raises.
If you do want to use a beta flag on the version, you should be able to do so as long as it conforms to the semantic versioning spec: http://semver.org

E.g. 1.0.0-beta. You might have to also include the patch level version as well?

Thanks!

I've added a try/catch and a warning describing acceptable version numbers. Thanks or submitting the bug!


Extract common exception superclass

@bjeanes Great!
LGTM

Can you release a new version with this change?

@bjeanes Sure! I sended in few ago minutes. v1.0.3


Joining masters fails with EOF accessing the api server

When joining multiple masters to a cluster, sometimes the following error occurs:
I1128 04:49:00.720050   23875 states.go:35] === applying state kubeadm.join ===
[join] failed to apply join to node failed to apply state kubeadm.join: unable to configure path: could not get current cluster version: could not retrieve the kubeadm-config ConfigMap: Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-system/configmaps/kubeadm-config: EOF
F1128 04:49:00.743496   23875 join.go:62] error joining node caasp-master-94-caasp-jobs-e2e-caasp-v4-vmware-test-docker-2: failed to apply state kubeadm.join: unable to configure path: could not get current cluster version: could not retrieve the kubeadm-config ConfigMap: Get https://<IP_ADDRESS>:6443/api/v1/namespaces/kube-system/configmaps/kubeadm-config: EOF

This problem was detected in the CI but has also been reported from the field. BUG 1155593
The issue seems closely related to this upstream PR in kubeadm
In the CI it is affecting both openstack and VMware tests, but more severely VMware. It is well known VMware cluster has problems with the disk so it is likely the problem is related to etcd taking too long (or failing) to synchronize.
Initially, it was attributed to the rapid sequence of joining the masters, which didn't allow the new master to stabilize before the next master was joined. Different delays were introduced 9508f11 4df3a67 in this sequence to allow the new master to stabilize. However, the problem persisted.
Also doing health checks of the etcd and apiserser were introduced, but the problem persists as shown in this log extract.
I1128 04:47:18.891025   23623 cilium.go:162] successfully annotated cilium daemonset with current timestamp, which will restart all cilium pods
[join] node successfully joined the cluster
●  exiting node_join
Executing command
    cwd: /home/jenkins/workspace/caasp-jobs/e2e/caasp-v4-vmware-test_dockercaps-nightly
    env: {}
    cmd: ssh -oStrictHostKeyChecking=no -oUserKnownHostsFile=/dev/null -oConnectTimeout=60 -oBatchMode=yes  -i /home/jenkins/workspace/caasp-jobs/e2e/caasp-v4-vmware-test_dockercaps-nightly/skuba/ci/infra/id_shared<EMAIL_ADDRESS>-- 'sudo curl -Ls --cacert /etc/kubernetes/pki/etcd/ca.crt --key /etc/kubernetes/pki/etcd/server.key --cert /etc/kubernetes/pki/etcd/server.crt https://localhost:2379/health'
Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
{"health":"true"}
Executing command
    cwd: /home/jenkins/workspace/caasp-jobs/e2e/caasp-v4-vmware-test_dockercaps-nightly
    env: {}
    cmd: ssh -oStrictHostKeyChecking=no -oUserKnownHostsFile=/dev/null -oConnectTimeout=60 -oBatchMode=yes  -i /home/jenkins/workspace/caasp-jobs/e2e/caasp-v4-vmware-test_dockercaps-nightly/skuba/ci/infra/id_shared<EMAIL_ADDRESS>-- 'curl -Ls --insecure https://localhost:6443/healthz'
Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
ok
● entering node_join
Executing command
    cwd: /home/jenkins/workspace/caasp-jobs/e2e/caasp-v4-vmware-test_dockercaps-nightly/test-cluster
    env: {'SSH_AUTH_SOCK': '/tmp/3a1eca5c69aa1f2b0614882f0d948d75/ssh-agent-sock', 'PATH': '/home/jenkins/workspace/caasp-jobs/e2e/caasp-v4-vmware-test_dockercaps-nightly/py3venv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin'}
    cmd: /home/jenkins/go/bin/skuba -v 5 node join --role master --user sles  --sudo --target <IP_ADDRESS> caasp-master-94-caasp-jobs-e2e-caasp-v4-vmware-test-docker-2
** This is an UNTAGGED version and NOT intended for production usage. **
I1128 04:47:20.464253   23875 states.go:35] === applying state kubernetes.install-node-pattern ===
W1128 04:47:20.527498   23875 ssh.go:309]
The authenticity of host '<IP_ADDRESS>:22' can't be established.
ECDSA key fingerprint is 68:5e:f9:56:4f:72:be:b8:b7:67:d3:8d:ba:ed:af:e7.

Base on this evidence, it seems the issue is related to the way kubeadm checks the status of the new master node.

Moved to avant-garde https://github.com/SUSE/avant-garde/issues/1104


Use label and no label basemaps for layers

The idea here is to combine label and no label basemaps so that we can sandwich the image overlay preview maps with thumbnails between the two.
This will make it easier for users to place the location of the thumbnail when the thumbnail has black borders.

See https://carto.com/location-data-services/basemaps/ (at the bottom) for the different label/no-label maps


Glob file system to locate substitution variations

Closes #22
so @matthewp I have a couple of issues getting to work this:

In production mode, steal tries to load path and glob. I added them to npmIgnore but that doesn't seem to work;  here is a branch on the sample app https://github.com/m-mujica/steal-conditional-interpolation-example/tree/new-conditional, I wonder how can I prevent steal to try to load them

I get a different error when I use relative imports, for some reason steal doesn't look for the conditionally loaded modules in the bundles folder but in dist/{module_name} https://github.com/m-mujica/steal-conditional-interpolation-example/tree/relative-import

do you see anything in the code that might be easier to approach in a different way?

I've been also thinking about the scenario where someone imports a module like
import '#{foo}';

With my current changes, we'd glob for the root project folder and the number of matches will be pretty big. I guess we can document that doing this is a bad idea, can we do better?

So, I'm trying a slightly different approach for the string interpolation

Normalize the module name without the conditional ( if import 'foo/#{bar}', we normalize foo)
locate the normalized name adding "/", in our example, we'll locate({ name: "foo/" })
global the filesystem with the address returned in the previous step
Iterate over the files found above ^, replace the conditional part of the module with the file name and normalize that name
Add the normalized name variations to loader.bundle

This is working fine, I'm steal dealing with the problem of steal loading dist/glob on production mode when the app is minified, I noticed the error doesn't happen if minify is set to false.


(Not?) Duplicate Items

Hi!
Trying to use elfeed, but I think I've run into an issue that you maybe can help me resolve.
The simplified example showing my issue is this; I have two feeds, both pulling topics from hacker news but with different filters:
elfeed-feeds is a variable defined in ‘elfeed.el’.
Its value is
(("https://hnrss.org/newest?points=1000&count=100" 1000p)
 ("https://hnrss.org/newest?points=2000&count=50" 2000p))

One post that made it all the way above 2000p (and therefore is a part of both feeds above) is the one with title <![CDATA[ Bye, Amazon ]]>
In Elfeed I only get one entry for this, not two. I would expect the entry to show up once in each feed. Or at least be tagged with both tags and show up as unread when it "arrived" in the second feed, even if I've read it from the first feed since before.
Thoughts?

This is a feature. In the XML for each feed, entries in common between
feeds have the same GUID. In other words, because they have the same
identifier, they're supposed to be considered identical entries despite
coming from different feeds. This is really useful, for instance, if you
wanted to follow overlapping subsets of a website (category or tag
feeds). To Elfeed, that's like following a single feed that is the union
of the followed feeds.
Now, Elfeed actually sits on the middle ground because many feeds — or,
in the case of RSS, most feeds — are not well constructed. Case in
point, the hnrss.org GUIDs are just HN permalinks (despite the RSS
claiming that they are not). That's not actually globally unique, and
generally you don't want entries from different sites merging together
because those sites misuse the GUID field. So Elfeed only merges feeds
from the same domain. If you follow some other site's HN feed, you'll
see repeated entries even if they use the same GUIDs.

Okay, got it. So this feature is limiting my use case here then. No workaround that you can think of?


automatic compatibility suite

it should be mode in app, like pseudotesting, where all simple on-device in-app tests which doesn't require user interaction run on device to see if device is compatible with application.

or it may be used for first run of application


Update ES indices and search controller

Description

This PR

changes the ES mapping mode from dynamic (default) to false (so that any unmapped fields are stored but not indexed)
removes unnecessary schema mappings, changing them to purely stored fields
converts some fields from text+keyword to just keyword
moves hardcoded dictionary to external YAML files

This is an updated version of #684, which has diverged too much from main to salvage. Also many of the changes in that PR have been broken up and merged in chunks in other PRs.
Testing Instructions

Since CI is passing, there is little reason to worry that any core functionality is broken. Also there is a comprehensive deployment plan for this PR which will ensure that there is no downtime involved in the deployment.
To verify,

Delete all existing data and volumes: just down -v.
Check out the PR and bring up all services: just init
Verify endpoints for list, search and detail for audio and images.
Specifically verify that the information about extensions and filetypes is valid (that was a point of conflict during merge).

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@dhruvkb do you think this should be closed or picked back up?

@zackkrida picked up for sure, now that the ES utilisation is under control, deploying the new indices should be the next target.

@dhruvkb It looks like this may have diverged from main, does it still make sense to target this work soon? If not, should we close this PR?

Yep, I'll close it for now and we can reopen it when we prioritise this project.


refactor: :recycle: convert schedule from csv into Markdown table

Description
Using a CSV for the schedule doesn't actually make it easier to work with compared to a Markdown table, so I converted it over.
Checklist

[x] Ran spell-check
[x] Formatted Markdown
[ ] Rendered website locally

So nice! 🎉


Remove convert_links_to_integers from featuretools

Now that we support categorical dtypes within featuretools, this option to normalize entity is unnecessary

The change impacts the tests in test_last_time_index. In particular, test_parent and the test afterwards fail. Investigating now.

closing via #219


IOGX Integration

As part of the ongoing effort to build a Developer Platform for IOG, the smart-contracts-dev-empowerment team has releasing IOGX - a Flake Template for Haskell Projects at IOG
The vision of IOGX is to provide a JSON-like, declarative interface to Nix, so that developers unfamiliar with the language may independently maintain and add to the Nix sources with minimum effort and maximum pleasure.
The goal is to integrate with all Smart Contracts repositories, and maybe more.
There are currently several other repositories using this: marlowe-cardano, antaeus, quickcheck-dynamic, quickcheck-contractmodel, marconi, stablecoin-plutus
As developers nothing changes for you: you will enter nix develop and you will get into a new shell.
There might be some rough edges but we will be prompt to smooth them.

Since this PR was opened, the interface of IOGX changed:

./nix/iogx-config.nix renamed to -> ./nix/haskell.nix

iogx-config.nix:haskellCompilers -> ./nix/haskell.nix:supportedCompilers
iogx-config.nix:defaultHaskellCompiler -> ./nix/haskell.nix:defaultCompiler
iogx-config.nix:shouldCrossCompile -> ./nix/haskell.nix:enableCrossCompilation

./nix/haskell-project.nix renamed to -> ./nix/cabal-project.nix

./nix/pre-commit-check.nix renamed to -> ./nix/formatters.nix

./nix/hydra-jobs.nix renamed to -> ./nix/ci.nix

inputs and inputs' have been swapped.
inputs (no prime ') is now the original inputs, non-desystemised
inputs' (with prime ') is now the de-systemized inputs
Reason behind this is that inputs is universally understood to be the original, unmodified flake inputs.
While inputs' is "non-standard" and thus warrants a different name.
This is the same notation used by flake.parts

The flake exports aliases for your haskell executables only in outputs.apps.
For example, outputs.apps.marlowe-apps-exe-marlowe-finder-ghc8107 also has an
alias outputs.apps.marlowe-finder (the cabal package name and the exe infix have been stripped)
These can be access as usual with inputs'.self.apps.marlowe-finder

Summary by CodeRabbit
Release Notes

Refactor: Updated the IOGX template by changing the inputs and outputs of the flake in flake.nix.
New Feature: Added a new file .pre-commit-config.yaml to improve code quality checks before commits.
Refactor: Modified the runDockerImage function and added a new pushDockerImage function in nix/docker-files/docker.nix.
Chore: Removed large blocks of code related to various packages from multiple .plan.nix files, simplifying the project structure.

🎉 Here's to the changes that came our way,
Refactoring code, making our day.
With every line removed, a simpler path unfurled,
A cleaner, leaner codebase for the world! 🌍🚀

@coderabbitai How does it look now?

Note that the required statues have changed. From
ci/hydra-build:required.x86_64-darwin
ci/hydra-build:required.x86_64-linux

To
ci/hydra-build:x86_64-linux.required
ci/hydra-build:x86_64-darwin.required

Once merged, I'll update the required statuses in the Settings

CI is green. I'm going to merge @bogdan-manole @RSoulatIOHK


goland 173.3727.96 x64  debuger failed

the program crashed when i updated the goland to the latest version today,it can be started normally,but crashed in the debuger model.

I don't know what uses for the parameter -gcflags "-N -l" -a. I guess that's the cause of these parameters. Is there anybody helping to solve it?

Thank you for raising this issue. Unlike many projects on GitHub, the Go project does not use its bug tracker for general discussion or asking questions. We only use our bug tracker for tracking bugs and tracking proposals going through the Proposal Process.
The best place to ask is probably on the goland forums, /cc @dlsniper

This is actually a Go issue, not an editor issue.
To solve it, upgrade to Go 1.9.2 or newer, as discussed here https://golang.org/issues/14319

Furthermore, those parameters are needed in order to build the debugging binary, removing them would make debugging next to impossible / a really bad experience. The editor is doing the right thing here.

@dlsniper After the upgrade, the problem has been solved, Thank you very much

@davecheney I got it, thank you for your guidance


Expand documentation for g:gutentags_project_info

I'm trying to configure gutentags for a project with both Ruby and Javascript ES6+ source and I'm can't make it work.  I don't think there's an actual bug, but the documentation for g:gutentags_project_info isn't making sense to me and I think this is where my problem is.
Scenario:
I'm using exuberant ctags on Ubuntu.
I'm trying to use this setup to generate tags for the JS files: https://github.com/romainl/ctags-patterns-for-javascript
The out-of-the-box Ruby tag generation seems fine.
I have a shell alias: alias ctags_js="ctags --options="$HOME/.ctags_js" which uses romainl's options.
When I run ctags_js -f - /path/to/my/file.js I see good tags and when I run ctags -f - /path/to/my/file.js I see mostly worthless tags so I think my alias/config trick is working.
(I feel like there should be a way to specify a ctags option file per language, but if there is I don't understand how to do it.)

I assume that '-e', 'ctags' means that it's using ctags and not ctags_js like I expected. I think this is my issue and that I'm not adding to g:gutentags_project_info correctly.

I was also trying to find a way to do something like :echo gutentags#show_file_info("path/to/file.js") and have it spit out details like what project it thinks this file belongs to and what language it's configured to use.  I don't think this is implemented though.

This works fine for me:
let g:gutentags_project_info = []
call add(g:gutentags_project_info, { "type": "javascript", "glob": "frontend/*" })
let g:gutentags_ctags_executable_javascript='ctags_js'

When you open a file in your project, and if gutentags_trace is enabled, you should see something like:
gutentags: Scanning buffer '<file>' for gutentags setup...
gutentags: Setting project type to javascript

If you don't see it reporting that it detected a javascript project, you're probably not opening a file from a project whose root directory contains a frontend/ directory.
Note that this will mean gutentags will use ctags_js for all files in that project -- including the Ruby files. I'm not quite sure how to handle different ctags for different parts of a given project (without making it 2 projects), or even if that makes sense.


Advancements

Hunter has some ideas for these so I'm gonna let her work on it.

Taco Tuesday - Craft any of the tacos on a Tuesday

Taco Tuesday - Craft any of the tacos on a Tuesday


Feature: displayTopBar

(refs #17)
Note renderTopBar:
<PhotoBrowser
  mediaList={media}
  displayNavArrows={displayNavArrows}
  displayActionButton={displayActionButton}
  startOnGrid={startOnGrid}
  useCircleProgress
  renderTopBar={false}
  onSelectionChanged={this.onSelectionChanged}
  onBack={navigator.pop}
/>

Custom Header / TopBar:

Fullscreen and controls shown:

@halilb What do you think? :)

I might have accidentally removed itemPerRow

Thanks for your contribution @miclaus! Optional TopBar sounds like something people would need.
I wonder if we can use displayTopBar state to achieve something similar.

Take displayTopBar as a property
Set initial displayTopBar state of the index component to displayTopBar props:

this.state = {
  displayTopBar: props.displayTopbar
};

Prevent _toggleTopBar method displaying the top bar

_toggleTopBar(displayed: boolean) {
    if (this.props.displayTopBar) {
      this.setState({
        displayTopBar: displayed,
      });
    }
  }

What do you think?

@halilb Thought of that at first, but then I wasn't sure in the render functions, since there already was a displayTopBar :))
Let me give it a try, sounds good!

Is it just me, or is the picture further below?

When I say semicolon i mean ,
@halilb This should fix the above mentioned paddingTop problem.

@halilb We then experienced a minor issue concerning the selection button in fullscreen mode, on iOS, because of the +20px of the native StatusBar.
In our case the selection button would slightly disappear behind our own HeaderBar / TopBar.
We changed the default Photo component style fullScreenSelectionIcon.top to 80 it is looks fine again. However no Platform checking has been done, since it might also be needed for Android.
This is not included in this PR, but you can find it on my develop branch, which we are currently using: https://github.com/miclaus/react-native-photo-browser/tree/develop

I'm so sorry that it took too long to review this @miclaus . I'll pull the latest code and test it before merging asap.

@miclaus It looks like I've missed this and merged a later PR for displayTopBar property.
I'm sorry about my oversight. Closing this PR in favour of #30.

@halilb no problem !
however, it doesn't seem that all the issues mentioned here, are also considered in #30.

You're right @miclaus. I think we might also create a renderTopbar prop to let the parent component render it's custom top bar. It may also return a null component if it doesn't need any top bar.


Issue 194: limit message word length to 60

Calling out that there's a small chance we'll run into someone who wants to legitimately post a longer-than-60-char URL. I still think this is the right choice for now — I think "just use a URL shortener" is sub-par but fine.


feat: Add ARIMA Model

Is your feature request related to a problem?
The user should easily use an ARIMA model on TimeSeries to predict future values statiscally.
This is a "baseline" model, which will be used to test or certify the RNN peformance
Desired solution
Add ARIMA to statistical models (rn working on experimental branch)
Possible alternatives (optional)
No response
Screenshots (optional)
No response
Additional Context (optional)
No response

:tada: This issue has been resolved in version 0.21.0 :tada:
The release is available on:

v0.21.0
GitHub release

Your semantic-release bot :package::rocket:


Default DateTimeKind configuration

Description
This is so we can specify a DateTimeKind to the dates that are parsed. More details in the issue.
Fixes # (issue)
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] I have performed a self-review of my code
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have made corresponding changes to the documentation
[x] I have commented my code, particularly in hard-to-understand areas
[x] New and existing unit tests pass locally with my changes

I was not quite sure how to add a test here. Did not see a specific example to test a value type - if a test is required, feel free to give pointers or any examples and I will add it to this branch.
Since this was a bug that I was facing while using this library with postgres, I have a test in my code base that I did to ensure this works.

I forgot the tests, it is definitely required but please let me know if you couldn't add a few tests for these changes, I'll try to add it to your branch

I forgot the tests, it is definitely required but please let me know if you couldn't add a few tests for these changes, I'll try to add it to your branch

Hey - I mentioned in my commit comment, I was not sure how to add a test to verify that this is working in the Gridify solution. Essentially how do I test that the final parameters are the right DateTime Kind.
Could use your help here. I verified it on my solution and added tests to ensure that postgres dates filtering was working with Gridify to verify it.  You can feel free to add a test or send me pointers to do it and I am happy to add that.

Since you're dealing directly with these issues, I'd love to hear your feedback on whether supporting both CultureInfo and DateTimeStyles would be more effective. Isn't that the way to go?

Not sure if I know a use case on top of mind that would require CultureInfo to be specified. In Sql Server or Postgres I have not faced that requirement. I would say let's push this for now and if a future requirement of CultureInfo comes around, we can modify it then.


Crash with energonrelics-0.1.1+1.16.2.jar

MC: 1.16.2
Fabric: fabric-api-0.18.0+build.397-1.16.jar
Astromine: astromine-1.6.1+fabric-1.16.2.jar
magna-a7ee77a9.jar is included in astromine-1.6.1+fabric-1.16.2.jar, which is why I'm reporting this conflict here.
I'm reporting this at energonrelic's repo as well.
[main/WARN]: @Redirect conflict. Skipping energonrelics.mixins.json:MixinWorld->@Redirect::breakBlock(Lnet/minecraft/class_1937;ILnet/minecraft/class_2338;I)V with priority 1000, already redirected by magna.mixins.json:WorldMixin->@Redirect::cancelSyncWorldEvent(Lnet/minecraft/class_1937;ILnet/minecraft/class_2338;I)V with priority 1000

This is an issue caused by two mods doing a @Redirect on the same method to prevent block break particles from being displayed in specific situations. This would be fixed by https://github.com/FabricMC/fabric/pull/1023.

Great!  Thank you!
I look forward to playing with energon relics when the PR gets merged.

This is currently resolved on energon relic's side.

Thanks for the report, will close.


Investigate network algorithm solutions to contributor levels

Network centrality might be interesting?
Page-rank?
Look at Oindrilla and Hema's work on project network results in the Rappel repo for inspiration.

Some takeaways from https://drive.google.com/drive/folders/1VUDPWJCfjB1WJQeH0ajUge0B3MQF-IF9
Contributor GCPs (Global centrality patterns) using  the SNA properties of

Degree Centrality (Dc),
Betweenness Centrality (Bc), and
Closeness Centrality (Cc) for each OSS projects.

Using Kmeans (I/P params are DC, BC and CC)
Developers can be categorized into

Reflexive level (more coordination - more actors)
Plan level (less coordination -only core)
Aware level (core developers & active devs)

Evaluated network using Pagerank, Degree Centrality, Betweenness Centrality, and Closeness Centrality.
Compared scores (normalized) for top 20 contributors from each algorithm.

11 contributors appeared in all 4 top 20 lists.
20 contributors appeared in 3/4 top 20 lists.

notebook: https://colab.research.google.com/drive/193jHnC_WXCO9UymOTNitbLhBW9LBvows#scrollTo=ry7Sk6CKENZf

Closed as in "done" column


Cant compile

I get 9 errors if I try to compile (version 2.3.2)

Nevermind. Had to install the submodule with git submodule update --remote --init

However, I still get errors and cant build:

Nevermind, there is a bug in the Blackbone Sourcecode in the file "BlackBone\Process\ProcessModules.cpp" I had to insert the missing header #include <iterator> at the top:
#include "../Config.h"
#include "ProcessModules.h"
#include "Process.h"
#include "RPC/RemoteExec.h"
#include "../Misc/NameResolve.h"
#include "../Misc/Utils.h"
#include "../Symbols/SymbolData.h"
#include "../Asm/AsmFactory.h"

#include <memory>
#include <type_traits>
#include <iterator>
...

Nevermind, there is a bug in the Blackbone Sourcecode in the file "BlackBone\Process\ProcessModules.cpp" I had to insert the missing header #include <iterator>:
#include "../Config.h"
#include "ProcessModules.h"
#include "Process.h"
#include "RPC/RemoteExec.h"
#include "../Misc/NameResolve.h"
#include "../Misc/Utils.h"
#include "../Symbols/SymbolData.h"
#include "../Asm/AsmFactory.h"

#include <memory>
#include <type_traits>
#include <iterator>
...

hmm nice but folder blackbone is EMPTY


[SPARK-31710][SQL][FOLLOWUP] Allow cast numeric to timestamp by default

What changes were proposed in this pull request?

Set the SQL config spark.sql.legacy.allowCastNumericToTimestamp to true by default
Remove explicit sets of spark.sql.legacy.allowCastNumericToTimestamp to true in the cast suites.

Why are the changes needed?
To avoid breaking changes in minor versions (in the upcoming Spark 3.1.0) according to the the semantic versioning guidelines (https://spark.apache.org/versioning-policy.html)
Does this PR introduce any user-facing change?
Yes
How was this patch tested?
By CastSuite.

@brkyvz @bart-samwel @cloud-fan @HyukjinKwon Please, review this PR.

Test build #125076 has started for PR 29012 at commit 08a48c6.

Merged build finished. Test PASSed.

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

Test build #125076 has finished for PR 29012 at commit 08a48c6.

This patch fails to generate documentation.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please

Test build #125080 has started for PR 29012 at commit 08a48c6.

Merged build finished. Test PASSed.

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

Test build #125080 has finished for PR 29012 at commit 08a48c6.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

jenkins, retest this, please

Test build #125128 has started for PR 29012 at commit 08a48c6.

Merged build finished. Test PASSed.

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

Merged build finished. Test FAILed.

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

The PySpark test fails due to timeout.
Starting test(python3.6): pyspark.mllib.classification
Build timed out (after 500 minutes). Marking the build as aborted.
Build was aborted

jenkins, retest this, please

Hi, @gengliangwang and @gatorsmile .
SBT PRBuilder seems to be running serially and took 8 hr 26 min. Do you think something is changed inside Jenkins? It seems that SPARK-27460 is disabled currently for some reasons.
[SPARK-27460][TESTS] Running slowest test suites in their own forked JVMs for higher parallelism

Test build #125179 has started for PR 29012 at commit 08a48c6.

Merged build finished. Test PASSed.

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

When did we disable SPARK-27460 ? I'm not aware of it.

I think it's just that the Jenkins machine became extremely slow for an unknown reason.

Test build #125179 has finished for PR 29012 at commit 08a48c6.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please

Merged build finished. Test PASSed.

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

retest this please

Test build #125199 has started for PR 29012 at commit 08a48c6.

Merged build finished. Test PASSed.

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

Test build #125199 has finished for PR 29012 at commit 08a48c6.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

jenkins, retest this, please

Test build #125226 has started for PR 29012 at commit 08a48c6.

Merged build finished. Test PASSed.

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

Thank you, @MaxGekk and all. Merged to master.

Test build #125226 has finished for PR 29012 at commit 08a48c6.

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

Merged build finished. Test PASSed.

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


Not putting out .CSV file

The add on is not outputting a .CSV file instead it outputs a text file with semi colon delimiters ";". With that in mind it works just fine.

Perhaps someone has changed it from outputting a , to a ; ?

Thanks for sharing this tool.  Made my day. I am reformating a data base of fires burning in eastern washington so I can quickly calculate the distance from my home and which direction I will see smoke.

Hi,
you are right, the default csv seperator is a semilcolon.
Maybe a comma as the name csv implies would be better.
Most tools i use autodetect or let you choose the seperator on import,
so i actualy did not think to much about it.
Still good to hear that the addon could be useful to you.
Thank you kindly for the feedback.
I'll will change/update the seperator as you suggested shortly.
It makes the most sense.
Have a awesome day.

Add-on has been updated.
https://addons.mozilla.org/en-US/firefox/addon/tbl2csv/
The default seperator should now be a comma, as stated in RFC 4180
ref: RFC4180 (https://tools.ietf.org/html/rfc4180)

Add-on has been updated.
https://addons.mozilla.org/en-US/firefox/addon/tbl2csv/
The default seperator should now be a comma, as stated in RFC 4180
ref: RFC4180 (https://tools.ietf.org/html/rfc4180)


Fancy Zones Templates per Desktop

Description of the new feature / enhancement
I would like to be able to apply a template to a new desktop instance without changing the template being used in an existing desktop.
Scenario when this would be used?
When I start a new desktop, I'm focused on a particular task and need a different window layout to accomplish that.
Supporting information
No response

/dup #34040


Set controlledValues to RequestsOnly in vpa resources

How to categorize this PR?
/kind enhancement
What this PR does / why we need it:

Changes VerticalPodAutoscaler resources to use RequestsOnly instead of RequestsAndLimits to prevent the VPA mechanism from proportionally changing the limits, which doesn't make sense.

Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

To use controlledValues: RequestsOnly, all VPA resources are upgraded from autoscaling/v1beta2 to autoscaling/v1.
Since Hvpa resources are based on autoscaling/v1beta2, they can't be changed without an API change. I wanted to avoid API changes in this PR, so Hvpa resources are not touched.

Release note:
VPA resources now use `controlledValues: RequestsOnly` to prevent the VPA mechanism from proportionally changing the limits, which doesn't make sense.

/test pull-gardener-integration
/test pull-gardener-unit

/test pull-gardener-integration
/test pull-gardener-unit

/test pull-gardener-integration
/test pull-gardener-unit

/test pull-gardener-integration
/test pull-gardener-unit

How does this v1beta2 -> v1 migration work? VPA is managed as CRD and I don't see a new CRD or any conversion webhook or something?

I tested this locally and it simply worked. On my test setup at least, it seems the autoscaling.k8s.io/v1 CRD was already in use even before my changes, so changing the version of the resources used by the code was straightforward. I will double check that this is the case also on our landscapes.

Ah, interesting, I see that we already create the VPA CRD with v1 version in https://github.com/gardener/gardener/blob/3d0d818e213eec89d225d71aa6bf574b48c4b7cc/charts/seed-bootstrap-crds/charts/vpa/templates/verticalpodautoscalers.yaml#L26-L73
v1 is even used as storage version. And probably v1 and v1beta2 are compatible, that's why no conversion webhook is needed?

/retest

Can we really do that already? You know, I dislike VPA's default (RequestsAndLimits) very much and agree with you wholeheartedly that it's dumb, but our goal was to remove limits where reasonable (avoid failing our components, especially essential components should not be resource-constrained), but RequestsOnly is actually more restrictive. This paired with the fact the memory limits are/were not removed is basically breaking us, is it not?
/hold unless I am wrong in my assessment, of course
If I am right, wouldn't it make more sense to:

Transform this PR into one that only introduces autoscaling.k8s.io/v1 without the (61x) RequestsOnly changes (the majority of this PR is about the version change/prep step anyway)
Have a mass or many individual changes that combine larger/appropriate max memory limits with RequestsOnly (this would have the additional advantage, that then the reviewer could also check that also the CPU limits were removed, which is probably the case with #5627, but we are touching so many components here that I cannot say for sure that we have really covered all CPU limits where this PR now would set RequestsOnly)

I would rather not touch this PR, from my perspective it does something that makes sense, and we all agree about it. It also does it in a consistent and self-contained way. There is no reason to go to /v1 unless we would like to use /v1 features. There is also no reason to split it into many smaller PR - it would only make it harder for people to assess / review.

This paired with the fact the memory limits are/were not removed is basically breaking us, is it not?

I don't think so in general, I would say this is a far fetched assumption at best. It is of course intended to be a part of a larger change that is split among several other PRs. It can be introduced now or a bit later, after these other PRs are merged, which is hopefully very soon.

we are touching so many components here that I cannot say for sure that we have really covered all CPU limits where this PR now would set RequestsOnly)

We are touching the same components, actually a subset of them, this is not so difficult to check.

/test pull-gardener-e2e-kind

/hold until https://github.com/gardener/gardener/pull/5627 and the PR adjusting memory limits (not yet created) are merged.

There is no reason to go to /v1 unless we would like to use /v1 features.

I just wanted to say that this change is valuable, whether the switch happens within this PR or within another (or even theoretically not at all), because:

It gives us the option to do it, when we need it
The beta API will probably expire one day anyway
That's all.

There is also no reason to split it into many smaller PR - it would only make it harder for people to assess / review.

I wasn't. I was writing:

Have a mass or many individual changes that combine larger/appropriate max memory limits with RequestsOnly

My main point was that it feels "right" to lgtm RequestsOnly only if CPU and memory limits were removed or comfortably increased. That's all. I am not arguing for smaller changes. And your comment https://github.com/gardener/gardener/pull/5638#issuecomment-1080325488 is already great/doing that/adding this hint. Thank you.

I would say this is a far fetched assumption at best.

???
It is a far fetched assumption that we will cause outages/break stuff if we introduce RequestsOnly w/o removing or comfortably increasing the limits?

We are touching the same components, actually a subset of them, this is not so difficult to check.

Well, it isn't trivial either. So let's find someone who can help double-check that we have pushed away/out all limits where we have set VPA to RequestsOnly, so that we do not break anything, please.

@vlerenc I am not sure what else you expect of me in terms of explanation or additional changes. I have of course double checked what needs to be double-checked. You can of course do it yourself as well or ask other people to help. I can also completely drop this PR if you don't feel comfortable with it, just let me know.

@voelzmo As discussed, I played a bit with https://github.com/kubernetes/autoscaler/blob/master/vertical-pod-autoscaler/examples/hamster.yaml to double-check what is the effect of setting controlledValues for a workload that has limits that have been proportionally scaled together with requests. As you suspected, simply updating the VPA resource doesn't have any immediate effect, the scaled limits on the pods stay until the deployment is next rolled out, or the pods are recreated for another reason (e.g. manually). Only at that points are the scaled limits on the pods replaced with the original ones from the deployment.
All this means that while this PR could be merged and released later than #5689, releasing both of them together will have the effect that the newly adapted limits will take effect immediately and in a more deterministic way, rather than later and less deterministic.

/rebase

/hold

@vlerenc @rfranzke Now that both #5627 and #5689 have been merged, I think it should be ok to merge this one as well.
/unhold

/rebase
I'm fine merging this one, waiting for @vlerenc's final /lgtm since there were some discussions (see above)

/lgtm
@stoyanr @rfranzke Sure, my concern was with #5689 and that's now merged. Thank you very much.

/lgtm


ci: enabling auto-publish with semantic release

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add bootstrap

First of all thanks for this life saver with most awesome domain ever. Now, Bootstrap recently announced their lts plans and didn't see any PR on it here. Let me know what you think.

:100: I didn't even know Bootstrap had a EoL policy.
Thanks a lot!


Indeces，labels data tree not show.

plugin version: 0.2.1
Neo4j version: 3.5.26
IDEA version: 2022.2.3 Ultimate
Connected test successfully...

Thank you @Mashull for reporting this issue. I suspect it is due to the version of Neo4j. Is upgrading to 4.4+ or 5.x an option?
In any case, if there is still a use base for Neo4j 3.x, this needs to be fixed. I will fix it in a new release.

Hi，@albertoventurini
Our products are based on neo4j 3.x, upgrading may bring some unnecessary problems. If possible, I except the plugin can adapt to this version.^-^

Hi @Mashull
I created a new bugfix release which should address this issue. Please see https://github.com/albertoventurini/graphdb-intellij-plugin/releases/tag/v0.2.2 if you want to download and install the plugin as a zip file.
The new release should be available from JetBrains marketplace later today or tomorrow.

It worked ! Thank you @albertoventurini
But indexes is also miss, like that:

And plugin console is empty.

Thank you @Mashull. Yes, for older versions of Neo4j, indices are retrieved in a different way. Supporting that will require more work. I've created a separate issue (#22) to track that work.
The release I just created (v0.2.2) should at least allow you to retrieve labels and relationships, and use them for Cypher autocompletion. I thought this is an important feature, and I wanted to get it fixed it for Neo4j 3.x as soon as possible.
I will work on indices, constraints, and procedures at a different time.

Hah, you are so kind! @albertoventurini
In the fact, cypher autocompletion is always work well, this feature not very urgent for me, but what you do now will bring us great convenience.
Best wish for you!

No worries, thank you for using the plugin @Mashull. I'll go ahead and close this issue for now.


04/23/2018 18:25 : Create Pull Request for branch master -> prTesting1_2018042318

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

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


fixing landscape issue

fixes #20

Closing this as a dupe of PR #29 without the extra whitespace changes.


ToolbarAndroid

how would one go about using ToolbarAndroid globally?
I'm wanting to use the actions aspect of ToolbarAndroid but I'm not really sure how to go about implementing this
@callmephilip can you maybe offer a suggestion to this question?

globally as in you want omnipresent in all the parts of the app? if it's the case you probably need 1 navigation reducer setup in the app and rely on it for all the nav scenarios. does this make sense?

yes thanks

i guess what im trying to do is something like this just no sure how to implement it
https://gist.github.com/mmazzarolo/d4f2c9855ec723ec228f8958e43b13f6
https://gist.github.com/mmazzarolo/5a4f235b6b07fa14247c0fb081b1f13f