Theme updates through wordpress interface

Is it possible to add functionality to FoundationPress so that themes that we produce can be updated via the wordpress interface, so users will be alerted that an update is available and they can action the update, instead of having to upload a new zip file.
I have to admit I don't know anything about this process and it may not be relevant to FoundationPress at all, so apologies if it isn't.
How can this bug be reproduced?
Not a bug, just a question

I don't think so as the purpose of FoundationPress is to be a skeleton theme, that you customise every time you make a new website...
I have used this theme more than 20 times and each time the theme ends up very different from website to website...
This theme allow you to be very picky performance wise, so updating through "regular" wordpress theme would remove this possibility...
That's my point of view... :)

Thanks but I was thinking more in terms of after you have customised it and you are making later updates to the same site, not rolling out to other websites. Packaging, logging onto the site, navigating to themes, uploading zip, activating new theme... it can be a bit of a ball ache.
Just didn’t know if part of the packaging process could handle uploading or making it available for updating somehow

I agree with @dantahoua, this is not the type of theme where you would update through the WordPress interface. Besides the fact that FP is not a parent/child theme setup, it doesn't make sense.
@nitrokevin your workflow for updating is kind of inefficient. Why don't you just overwrite/merge the theme folder from your local copy to the remote server via FTP? That way you don't have to package anything, and you don't even have to touch the dashboard. You can set your FTP software to ignore the node_modules directory which will make everything fast.
I personally have never even used the package task, besides testing it when I wrote it lol. It's useful for some situations, like passing theme off to another person, but there's better ways to update.
Another fast way to update is through git. Remove the line from .gitignore that ignores the dist directory. Then commit the dist directory to the repo. Add your hosting server as a remote on your local repo, and then push local changes after you commit. Make sure you build as production before pushing.

Great thanks, I knew there must be a better way. Thanks again


Take Advantage Of "Hardware Accelerated" Components?

Is this request related to a missing driver support for a particular hardware platform, SoC or board? Please describe.
Describe in details the hardware support being requested and why this support benefits Zephyr.
There are hardware features that appear not to be taken advantage of.
The one thing that brought it to light for me was the CRC/Checksum capability of the STM32.
Describe why you are asking for this support?
It'd be nice to take full advantage of a SOC's abilities.
Additional context
EG. HAL CRC Generic Driver Drivers_en.DM00105879.pdf: pg.141
I recognize the complexity of what boards/soc/arch supports what, but that's already been dealt with by the function/purpose of this project.
Reference to a project that appears to have done just that (at least for STM32 CRC): https://github.com/nanoframework/metadata-processor/blob/acacc000e3cff87d902ed347c9c9e7e55e5ade3d/native/nf-interpreter/targets/CMSIS-OS/ChibiOS/nf-overlay/os/hal/ports/STM32/LLD/CRCv1/crc_lld.h

Closing with the correct reason as this was unproperly marked as "completed".


Privacy Masking

Is your feature request related to a problem? Please describe.
I would like to be able to block out my camera feed with a toggle switch in Home Assistant
Describe the solution you'd like
You can create privacy masks directly on that camera, accessed under "PrivacyMasking"
I was wondering if you could add this feature?

Thank you!
Released in https://github.com/rroller/dahua/releases/tag/0.9.49


pyarrow won't cast date32 to date64

Describe the bug, including details regarding any error messages, version, and platform.
I'm trying to build a tool to confirm that a given parquet file conforms to an expected schema with our metadata format. There appears to be a bug with how pyarrow converts dates, however.

I have a dummy dataset, called test.csv (expand to view)

my_int
animal
my_email
my_datetime
my_date

16
NA
<EMAIL_ADDRESS>2013-01-14 15:54:20
1993-09-27

13
cat
<EMAIL_ADDRESS>2006-12-16 01:44:21
1989-04-08

13
dog
<EMAIL_ADDRESS>1972-06-19 11:22:59
2006-10-01

18
NA
<EMAIL_ADDRESS>2009-07-11 00:45:28
1992-07-24

10
fish
<EMAIL_ADDRESS>1970-09-11 22:26:13
2011-11-30

13
cat
<EMAIL_ADDRESS>2018-09-18 16:18:37
1979-01-22

16
dog
<EMAIL_ADDRESS>2002-08-26 10:25:03
1981-03-27

11
dog
<EMAIL_ADDRESS>1989-02-26 16:33:37
2012-06-19

19
chicken
<EMAIL_ADDRESS>1974-07-25 04:41:22
2003-11-06

11
chicken
<EMAIL_ADDRESS>1992-04-03 09:47:30
1972-07-06

I have a user-generated schema that resolves to this:
my_int: int64
animal: string
my_email: string
my_datetime: timestamp[s]
my_date: date64[ms]

However, the last column seems to be read by pyarrow as date32[day], and won't cast otherwise:
import pyarrow as pa
import pyarrow.parquet as pq

table = pa.csv.read_csv("test.csv")
table.cast(my_custom_schema)
pq.write_table(table, "test.parquet")
table_arrow_schema = pq.read_schema("test.parquet")
table_arrow_schema

gives
my_int: int64
animal: string
my_email: string
my_datetime: timestamp[ms]
my_date: date32[day]

Component(s)
Parquet, Python

pyarrow.parquet doesn't round trip all types right now. Right now, the only other example I know of is is dictionary types. They always come back with int32 indices, regardless of the original index type. See also: https://lists.apache.org/thread/rv29cwf4208jh73s0gyrzpw5l87pf7pb
date64 type only exists for compatibility with systems that use milliseconds to represent dates. That representation doesn't exist in the Parquet format. It's also not a sensible representation of a date, because the logical resolution is a day, so the milliseconds information isn't used.
But it looks like we handle this for nearly every other type, including Large* variants of string, binary, and list, different timestamp resolutions, and unsigned integers. So maybe it's worth fixing these last few types.

Python code to check type roundtripping
import pyarrow as pa
import pyarrow.parquet as pq
from decimal import Decimal

def check_parquet_roundtrip(arr):
    tab = pa.table({"x": arr})
    pq.write_table(tab, "test.parquet")
    schema = pq.read_schema("test.parquet")
    assert schema.field(0).type == arr.type

# These fail
check_parquet_roundtrip(
    pa.array([1, 2, 3], pa.date64())
)

check_parquet_roundtrip(
    pa.array(["a", "b"], pa.dictionary(pa.int8(), pa.string()))
)

# All these work
check_parquet_roundtrip(
    pa.array([1, 2, 3], pa.timestamp('ms'))
)

check_parquet_roundtrip(
    pa.array([1, 2, 3], pa.timestamp('us'))
)

check_parquet_roundtrip(
    pa.array(["a", "b"], pa.dictionary(pa.int32(), pa.string()))
)

check_parquet_roundtrip(
    pa.array([Decimal("10.000")], pa.decimal128(19, 3))
)

check_parquet_roundtrip(
    pa.array([Decimal("10.000")], pa.decimal256(19, 3))
)

check_parquet_roundtrip(
    pa.array(["a", "b"], pa.large_string())
)

check_parquet_roundtrip(
    pa.array([["a", "b"]], pa.large_list(pa.large_string()))
)

check_parquet_roundtrip(
    pa.array([["a", "b"]], pa.large_list(pa.large_string()))
)

check_parquet_roundtrip(
    pa.array([1, 2, 3], pa.uint32())
)


Get Loxone binding into HA

Have you considered re-opening https://github.com/home-assistant/core/pull/9706 now that you seem to be back using Home Assistant (and are probably more used to git)?

I had so much trouble and no help from the Home-assistant folks that I not go to integrate it in the main branch. I think with the possibility to to install it with hacs there is no real advantage. And for a serious integration in Home-assistant the binding should complete separated from the loxone communication.


Nonce error while transferring token between tokens

Environment:Testnet
User send Stella token from account #1 to account #2-test passed
User send Stx from account# 1 to account #2-failed with error below.
attaching Video recording for perusal
https://user-images.githubusercontent.com/38872890/123159943-9ef5cd00-d43b-11eb-9814-a26f103fb7e2.mov

I'm getting a very similar nonce error. But instead of "Nonce conflict, try again soon." I'm getting "Incorrect nonce."
Can't do anything with my funds right now. Hope this helps

@Eshwari007 I just tested this with latest, and I cannot reproduce. Can you confirm that you find this same issue in https://github.com/blockstack/stacks-wallet-web/actions/runs/1004532397

I'm still running into the "Incorrect nonce." error. I've deleted and re-downloaded the extension on both Chrome and Brave -- error persists.
Is there another way to ensure I'm using the most updated version?
Happy to answer any questions or provide other details that would be helpful.

I'm still running into the "Incorrect nonce." error. I've deleted and re-downloaded the extension on both Chrome and Brave -- error persists.
Is there another way to ensure I'm using the most updated version?
Happy to answer any questions or provide other details that would be helpful.

Can you walk me through how you're getting the error?
If you're interested in trying out an unreleased version to test, you can download the assets here: https://github.com/blockstack/stacks-wallet-web/actions/runs/1004532397 and follow these steps: https://github.com/blockstack/stacks-wallet-web#install-from-source. We are still doing some final QA on it, but it has been working well for me.

Just tried the version you provided, and the error remains.
I don't have any tokens in my wallet besides STX, so I can't do the Stella token test like @Eshwari007 did in testnet.
But, what she does in the second half of the video she attached (0:40-1:01) is exactly what I'm doing. The only difference is the error message I'm getting. "Incorrect nonce."
Let me know what you'd like to test next and I'm happy to help.

Just tried the version you provided, and the error remains.

hmm -- can you walk me through step by step what you're doing? and provide your address if possible?
eg:

sign in
hit send
enter address "SPsdfsdf"
etc

Happy to. Could we email or message via discord privately?

sure, add me on discord -> aulneau#8426

Would you mind momentarily allowing friend requests?

@aulneau @thisMonkeyBytes could one of you provide an update about what you learned via messaging privately?

@markmhx I was never able to get in touch privately with @aulneau because his Discord doesn't allow others to add him as a friend.

Feel free to message me there with the same requested details: Mark Hendrickson#3708

@markmhx sent you a friend request

I must have accepted it since I don't see any pending. Can you message me the information there now?

Related to https://github.com/blockstack/stacks-wallet-web/issues/934
check if this issue gets closed once #934 is resolved

I just tested, this is working fine. To be tested along with https://github.com/blockstack/stacks-wallet-web/issues/934

Is this related I am on an account that has no transactions pending.
a. I log into account 2, with the web wallet, and copy the address.
b. Switch to account 3 and send 5 stx to account 2.
Account 3 is on nonce 2
Account 2 is on nonce 8
--> The transaction from account 2 is (5 stx to account 2) is send with nonce 9 and ofc can not be mined.
Will this be resolved too with #934?
What about offering an option to web wallet users to edit the nonce (as a sort of advanced setting) that way we can always work around this kind of issues?

@beguene may be able to comment on whether the scenario you describe should be solved by #934.
Please open a separate issue for tracking the possible enhancement in which users can edit their own nonce values manually 🙏

@markmhx Yes it should be fixed by #934.


[BUG] Xcode 15 Beta failing to compile with WindowsAzureMessaging dependency

Describe the bug
Whilst testing our project with Xcode 15/iOS17 using the first Xcode 15 beta, we have found that we are unable to compile the app as it complains about a missing header file in the WindowsAzureMessaging dependency, which is adding using SPM.
Obviously, a quick investigation can see that the file is there and nothing has changed between Xcode 14 and 15
Xcode 14.3.1 builds without issue
Exception or Stack Trace
Showing All Messages
/Users/user/Library/Developer/Xcode/DerivedData/EFOS-gkiizosydfslxzfdkuthkpfxczum/SourcePackages/checkouts/azure-notificationhubs-ios/WindowsAzureMessaging/WindowsAzureMessaging/Helpers/SBURLConnection.m:5:9: 'ANHAsync.h' file not found
To Reproduce

Open a workspace or project that is using WindowsAzureMessaging in Xcode 15 beta
Clean and Build
Notice the build error.

Code Snippet
Just failing to find the file
Expected behavior
Should build
Screenshots

Setup (please complete the following information):

OS: MacOS Venture 13.4/iOS 17.0 target
IDE : Xcode 15 Beta
Version of the Library used: 3.1.5

Additional context
We are unable to test our application against iOS 17 without removing the package
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Bug Description Added
[x] Repro Steps Added
[x] Setup information Added

@tomkrikorian No i haven't, but i've been busy with other work so i haven't had time to investigate further.

I can confirm this is still and issue in Beta 2

@tomkrikorian I have managed to work round this by adding the WindowsAzureMessaging.xcframework directly to my project instead of using SPM.

any update on this topic\package? Thx

Just installed Xcode 15 beta 5 and its now complaining about a different file instead of the original one i logged

Just installed Xcode 15 Beta 5 and its the same as Beta 4.

Any workaround?

@tomkrikorian I have managed to work round this by adding the WindowsAzureMessaging.xcframework directly to my project instead of using SPM.

@learnwithgabbar  the above is the only work around

FYI with Xcode 15 beta 6 it just works as expected

I can confirm that is is now resolved in Xcode 15 Beta 6

This issue is back in Xcode 16 beta 1

I can confirm we have the same issue as before in Xcode 16 Beta 1

Issue is also present in Xcode 16.0 GM.


[Docs] Consider having separate API reference from Components guide

Ref: https://github.com/callemall/material-ui/issues/2435#issuecomment-163043486
@newoga wrote:
"We currently don't have 1-to-1 mapping between material design components and material-ui components. And even though it may be something to strive for, I think it will simply be impossible or impractical. For example, things like tool tips are easier to implement as props of other components and may never really need a publicly exposed React component.
Because of this, it might be nice to have a collapsable API reference that in one flat list shows all the exported Components, regardless of how they were designed to be used."
/* Sample list */
+-- API Reference
|   +-- <AppBar />
|   +-- <FloatingActionButton />
|   +-- <RaisedButton />
|   +-- <FlatButton />
|   +-- <Menu />
|   +-- <MenuItem />

Notice Menu and MenuItem are not cascaded. This is meant to be used by a developer who knows what they are looking and wants a reference. Links to source code might be useful on these pages.
Note: This is actually how it is done at https://material.angularjs.org/.  They have a separate Demos section that would similar to our Component guide and a separate API reference.

Just a quick initial note, I think that another level of organization would definitely help. Right now there is no way to navigate around those huge pages that have multiple components and lots of demos.

The one advantage of having the demos an API reference on the same page is that it makes it easier to cross reference the props used in the examples with their usage.
Perhaps if the was a popover when hovering over a prop in the example god that showed the relevant section of the API reference, we could move the reference elsewhere.

Perhaps if the was a popover when hovering over a prop in the example god that showed the relevant section of the API reference, we could move the reference elsewhere.

I think that would be cool. Though for the records, I wasn't originally suggesting removing the table of props/API reference from the demos. Since it's now automatically generated, we don't have to worry about it being inconsistent if we put it in two places. I just think that it'd be nice to find and look up the  component name, not the material design pattern if that makes sense.

A h, right. Well maybe we could do both. :smile:

Fixed in next.


Create learn.txt

The district homepage is www.hohschools.org
The high school is http://www.hohschools.org/Domain/10
Student emails end in @learn.hohschools.org
Thanks

@ndstreet It seems to me that the description in the file has to be different to reflect an actual scope of the email domain: "Hastings-on-Hudson Union Free School District". Please modify the description and add .group as a second line because this email domain belongs to a group of schools.

Updated!  Hope it's correct now.

@ndstreet Yes, now everything is correct. Thank you! Pull request merged.


chore(release): v0.24.0 🎉

:robot: I have created a release beep boop
0.24.0 (2024-09-01)
Features

serde: cache deserialize in memory since deterministic (ed9787c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ehmpathy/domain-objects/releases/tag/v0.24.0 :sunflower:


docs(sg) add rules for active/passive voice

Thoughts on using multiple examples?

@nijikokun the more, the merrier. We should have one that does not include the subject since that example slips by more often.

This level of granularity will make for difficult PRs - IMHO the Stye Guide should be reserved for Kong Enterprise specific terms, and other suggestions like this (and some others currently in the Style Guide) should be moved to the Technical Writing guide.
The idea being that while we may not go through and change a PR's sentence structure, it is a tip for better writing

@levfishbluefish I feel it would be easier to link to a specific rule than saying, "Go read the writing tips in the technical writing guide." It's a use case for having a reference rather than an explanation.
The reality is that most contributors do not have access to the Chicago Manual, which is the style we assume in our copyedits. As a result, we need to be explicit about the rules that matter, which exceed product terms. @nijikokun recently had a case where, because he couldn't refer to this rule, the suggestion was moot.
Having general tips in the writing guide is great--and having a central source of truth (with discreet, linkeable rules) doesn't conflict with that goal. In fact, it supports it.

Before adding this then I would like us to review the Style Guide as a whole and add any other grammar points like this all together

@levfishbluefish I think that's out of scope, maybe we can create a ticket. There are other usage and style rules already in the Style Guide.


Different Cache Key Per Server (Pod)

Brief Description of the Bug
I just used the Redis cache-handler as I have an app that gets deployed on multiple containers/pods/servers. The issue is that when we fetch data from an endpoint, it ends up with multiple cache keys for the same endpoint per running container. The cache stays on the Redis server till the expiresAt date which is good, but this way it's kind of useless as it's a centralized cache, but, each server generates it's own cache key!
I have configured a cache key prefix, and also I have a fixed buildId that reads it's value from the Git Hash. So, I'm not sure what's the root cause for this!
Severity
Critical
Frequency of Occurrence
Always
Steps to Reproduce
cache-handler.mjs:
import { CacheHandler } from '@neshca/cache-handler';
import createLruHandler from '@neshca/cache-handler/local-lru';
import createRedisHandler from '@neshca/cache-handler/redis-stack';
import { createClient } from 'redis';

CacheHandler.onCreation(async () => {
  let client;

  try {
    // Create a Redis client.
    client = createClient({
      url: process.env.REDIS_DSN ?? 'redis://redis:6379',
      socket: {
        connectTimeout: 1000,
      }
    });

    // Redis won't work without error handling.
    client.on('error', () => {});
  } catch (error) {
    console.warn('Failed to create Redis client:', error);
  }

  if (client) {
    try {
      if (process.env.REDIS_AVAILABLE) {
        console.info('Connecting Redis client...');

        // Wait for the client to connect.
        // Caveat: This will block the server from starting until the client is connected.
        // And there is no timeout. Make your own timeout if needed.
        await client.connect();
        console.info('Redis client connected.');
      }
    } catch (error) {
      console.warn('Failed to connect Redis client:', error);

      console.warn('Disconnecting the Redis client...');
      // Try to disconnect the client to stop it from reconnecting.
      client
        .disconnect()
        .then(() => {
          console.info('Redis client disconnected.');
        })
        .catch(() => {
          console.warn('Failed to quit the Redis client after failing to connect.');
        });
    }
  }

  /** @type {import("@neshca/cache-handler").Handler | null} */
  let handler;

  if (client?.isReady) {
    // Create the `redis-stack` Handler if the client is available and connected.
    handler = await createRedisHandler({
      client,
      keyPrefix: process.env.REDIS_PREFIX ?? '__',
      timeoutMs: 1000,
    });
  } else {
    // Fallback to LRU handler if Redis client is not available.
    // The application will still work, but the cache will be in memory only and not shared.
    handler = createLruHandler();
    console.warn('Falling back to LRU handler because Redis client is not available.');
  }

  return {
    handlers: [handler],
  };
});

export default CacheHandler;

Expected vs. Actual Behavior
Describe what you expected to happen and what actually happened.
Screenshots/Logs

Environment:

@neshca/cache-handler version: 1.3.1
next version: 14.1.4

Hello @khal3d, I noticed that every key has the same prefix - nxt_. The remaining part of the key, for example, 9bc6f6daaf28afbc730ff4d50a0ae355750654724dbe262553a4f2b061f386cc, represents the fetch cache key created by the Next.js server. In this screenshot, there are nine different fetch cache keys that share the same prefix, and everything seems okay to me.
You are on the right track as long as the process.env.REDIS_PREFIX remains the same in every pod environment.
Some deep dive into the Next.js fetch cache: 9bc6f6daaf28afbc730ff4d50a0ae355750654724dbe262553a4f2b061f386cc is a SHA256 of the combination of the resource and options parameters of the fetch(resource, options) function call.

Hi @better-salmon Yes, I have a cache key prefix set to nxt_, and at that time 9 containers were running for the same build, and all the 9 cache keys were for the same fetch request (nothing extra in the request), which I was expecting them to end up with only one cache key, not 9 cache keys.
The cache keys grow as we scale the production containers, which means they are not using the same cache key.
To be honest, I'm not sure if it's a NextJS issue as it generates a cache key per running container, or if it's an issue with @neshca/cache-handler setup.

Could you please check the values. Make sure that the the url, headers and the body is the same for every key.
You can use atob() to parse base64 data from the body.

@khal3d hello! Is this issue still relevant?

I'm closing this issue due to inactivity.


Only use true/false in default config to reduce confusion

Describe your PR, what does it fix/add?
Hello,
I think it would be a good idea to standardize the format of all the boolean values in the example configuration file in order to always use true/false.
I think the different true/false/on/off/yes/no leads to more confusion for the new users even if the values in themselves are perfectly valid.
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
Is it ready for merging, or does it need work?
It is ready if you think the changes are a good idea :smile:

fair, thanks!


merge development into master

Merge contains several fixes:

Replaces blanket with istanbul.
Fix several linting issues.
Fix badge links.

Changes Unknown when pulling 607d1f922d4a74233c8eebcb38f02460c7f23469 on development into ** on master**.


Add tabindex attribute binding

This enables simple keyboard-based accessible sorting via  a keyUp handler.
For example:
  {{#each myItems as |item idx| }}
    {{#sortable-item tabindex=0 keyUp=(action 'keyUp' idx) model=item }}
      {{item.name}}
    {{/sortable-item}}
  {{/each}}

actions: {
  keyUp(index, evt) {
    switch(evt.key) {
      case "ArrowDown":
        // move item at `index` back one
        break;
      case "ArrowUp":
        // move item at `index` forward one
        break;
      default:
        return;
    }
  }
}

This is complementary to #154 which provides a more "batteries included" button-based approach to accessibility.
There's also a twiddle highlighting the basic idea.

This looks great to me. The only tiny tweak I’d make is to remove the onDragStart="dragStarted" onDragStop="dragStopped" from the example snippet in the readme. Just so readers focuses on the pertinent attribute.
Thanks!

@hjdivad I took the liberty of rebasing this against 1.x and making the small README change I mentioned. I’ll try to cut a release later today.

@jgwhite ah i was about to follow up on your excellent suggestion re the README change but I see you've already done it. ^_^

@jgwhite The example that @hjdivad posted that includes the implementation of keyUp is great. However, the official documentation does not include the keyUp implementation. I was unsure of how tabindex alone allows us to implement sortable-item in an accessible way until I stumbled upon this PR.
I can send a PR to update the documentation to include the example implementation of keyUp in the documentation or perhaps a blurb describing how keyUp should be implemented to support reordering in an accessible way. Do you think that's a good idea?

@alanwguo that sounds fantastic. Thanks!


Adding missing backslash in dvc run commands

Copy and paste files without the addition of the backslash on first line.

You may disregard these recommendations if you used the Edit on GitHub button from dvc.org to improve a doc in place.

❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.
🐛 Please make sure to mention Fix #issue (if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.
Please choose to allow us to edit your branch when creating the PR.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏

thanks @brightsparc !!

Oops, that was a big multi-typo. Thanks again @brightsparc !


Error listing challenges

Error listing challenges when no one exists (0 challenge):
This case need to be handle.
[?] > What do you want to do ?
4

Challenges:
	bugbounty:
Traceback (most recent call last):
  File "py_chall_factory.py", line 112, in <module>
    menu(dispatcher, options_parser)
  File "py_chall_factory.py", line 94, in menu
    dispatcher_call(dispatcher, options_parser, OPTIONS[choice-1][0])
  File "py_chall_factory.py", line 54, in dispatcher_call
    dispatcher.call(opt)
  File "/home/noraj/py_chall_factory/core/dispatcher.py", line 29, in call
    self.dispatch.get(key, not_implemented)(kwargs)
  File "/home/noraj/py_chall_factory/core/functions.py", line 130, in list_challenges
    for chall in os.listdir(os.path.join(root, category)):
FileNotFoundError: [Errno 2] No such file or directory: 'challenges/bugbounty'

That's right there is a little glitch here :+1:
I'll correct that when I have some time.
Thank you very much!


Is this package still maintained?

Is this package still maintained?

:wave: @nelsyeung, @fsandx
After much consideration, I've decided to take the best parts of this library and create:
https://github.com/preposterous/twitter-lite

591B of source files
promise first (via Async / Await)
up to date
maintained for the foreseeable future

Let me know what you think!

@peterpme: So glad to see someone rewrite the Twitter client from scratch using modern async/await, promises and cross-fetch! Would love to kick its tires as soon as streams support is added. CC @Frizz925.

I just opened a PR for stream support 😄 https://github.com/Preposterous/twitter-lite/pull/13

Woo! Looking over it now :)

Streams are now part of twitter-lite thanks to @tylerbuchea  😄

FYI @peterpme
According to Twitter, the User and Site stream APIs will be discontinued in June to make way for the Account Activity API:

The Account Activity API will replace the User streams and Site streams APIs. Additionally, we plan to sunset those APIs on Tuesday June 19, 2018.

https://developer.twitter.com/en/docs/accounts-and-users/subscribe-account-activity/overview

Thanks for the heads up @loljoho I just signed up for the beta https://developer.twitter.com/en/apply you should to @peterpme

awesome thanks for sharing!!!


How to highlight the whole buffer

I am trying to use ctrl+a to highlight the whole buffer.
Here is my zle widget.
autoload -Uz region_highlight
zle -N region_highlight

_ctrl-a() {
  ((CURSOR = 0))
  ((MARK = $#BUFFER))
  zle region_highlight
}

zle -N _ctrl-a
bindkey '^A' _ctrl-a # Ctrl+A

When i press ctrl+a , it says _zsh_autosuggest_invoke_original_widget:9: region_highlight: function definition file not found
What is the issue here?

This isn't really a zsh-syntax-highlighting question, but region_highlight is an array in ZLE widgets not a function. For further questions on ZLE widgets, you might try the users mailing list or the IRC channel on libera.


Request verification using SHA1 and secret fails

I tried using this to handle webhook requests and I kept seeing 400 Bad Request responses:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>400 Bad Request</title>

Bad Request

Invalid signature

After a bit of investigation I found out that this fails because request.data is empty:
https://github.com/bloomberg/python-github-webhook/blob/61e713c3781e2de6e327554be54095df2d666604/github_webhook/webhook.py#L56-L59
And what should be used instead is request.get_data(), since it returns value regardless off payload format used:

Request.get_data(cache=True, as_text=False, parse_form_data=False)
This reads the buffered incoming data from the client into one bytestring. By default this is cached but that behavior can be changed by setting cache to False.
https://tedboy.github.io/flask/generated/generated/flask.Request.get_data.html

Not sure how this worked before...

Thanks, @ jakubgs, this worked for me!


Version 1.0.0

I'm preparing a long overdue 1.0.0 release that will address some of the largest concerns myself and others have had regarding the design of this module;

removed singleton design
use a simple class to wrap child process and stdout / stderr streams

I'm looking for feedback with regards regards to the new implementation and some real-world scenarios and use-cases that were hard or impossible to implement with the older module design.
Anything is up for discussion 😉
/cc @tiff @cauli @iniq @evancohen @RobQuistNL

Hey @gillesdemey ! Cool to see you're still working on it.
I'm going to have to test this lateron - I'm not working as much on the project that used this as I used to, so a review from me might be coming a lot later.

@gillesdemey thanks so much for the big maintenance release! People like you are part of the reason open source rocks!


Getting error

Hi
i am trying to install the page speed module on nginx 1.18.0 and ubuntu 20.04 , after done everything i am getting an error below
About to configure nginx with:    ./configure --add-module=/root/incubator-pagespeed-ngx-latest-stable y Does this look right? [Y/n] y ./configure: error: invalid option "y" Error: Failure running './configure --add-module=/root/incubator-pagespeed-ngx-latest-stable y', exiting.
How can I fix the issue?

About to configure nginx with: ./configure --add-module=/root/incubator-pagespeed-ngx-latest-stable y Does this look right? [Y/n] y ./configure: error: invalid option "y" Error: Failure running './configure --add-module=/root/incubator-pagespeed-ngx-latest-stable y', exiting.

From where comes this "y" in stable y Does ?


Mark SE-0145 and SE-0082 as implemented

Thanks @BasThomas. Please keep them in numerical order. While you're at it, could you update 0082?
@ddunbar is it correct that these are implemented for 3.1 and not 4?

Yes these are implemented for 3.1

Oops, fixed!

Updated 0082 as well.


Adding GetPrivateIpInstance(s) AWS helper functions

Issue: https://github.com/gruntwork-io/terratest/issues/211
Test Pass Gist: https://gist.github.com/drmmarsunited/d95744bbc049d040b1b17b3c90eda796
This PR adds the following helper functions to the ec2.go file in the aws module:

GetPrivateIpOfEc2Instance
GetPrivateIpOfEc2InstanceE
GetPrivateIpsOfEc2Instances
GetPrivateIpsOfEc2InstancesE

It also updates the existing tests for the basic SSH example to use the newly created GetPrivateIpOfEc2Instance function to grab the private instance's IP address, instead of using the output from Terraform.
There was also a reversal of the public/private IP order in the string interpolation, where the public instance's IP address was being written into a string where the private instance's IP should have gone.  I've updated that as well.

https://github.com/gruntwork-io/terratest/releases/tag/v0.13.18


docs: improve and simplify codespaces guide, use separate script

The Issue

described in https://github.com/ddev/ddev/issues/5288

How This PR Solves The Issue

remove "configure devcontainer" section, since it only adds this bare minimum template:

remove ddev config --omit-containers=ddev-router (https://github.com/ddev/ddev/issues/5288#issuecomment-1687151750)

use separate bash script for postCreateCommand since users may want to add more commands

Manual Testing Instructions

[x] test guide with non-codespaces repository - thanks very much @tyler36
[x] ran docs generation locally

Here is a demo repo for following the guide:
https://github.com/mandrasch/ddev-codespaces-demo
Automated Testing Overview

no

Related Issue Link(s)

https://github.com/ddev/ddev/issues/5288
https://github.com/ddev/ddev.com-front-end/pull/86

Release/Deployment Notes
no

Thanks for this.

HTTP (forwarded 8080) opens HTTPS version of site.
Xdebug works when you install the extension, add the launch snippet. It automatically forwards the port which is nice.
Mailhog page opens and correctly captured/displayed mail
400 error when trying to access the forwarded HTTPS version (port 8443)
404 error when use the ddev launch command.

400 error when trying to access the forwarded HTTPS version (port 8443)

I'm not sure which https port you're talking about here @tyler36 , but in general, the Codespaces router can't trust DDEV's https because there's no way to inject a CA into it. As a result, it can't decode information coming from any DDEV-based https port.

Great, thanks very much for clarification @rfay! (I assumed this a while ago, but was never sure)
(Background:
There is automatically a port created when ddev start is called within codespaces:

We could also label the http port and https port differently to avoid confusion, but don't know what good label titles would be?
    "8080": {
      "label": "web http"
    },
    "8443": {
      "label": "web https"
    },
 ```)

 In general this PR is good to go from my perspective, thanks so much @tyler36 for testing it with a fresh set of eyes 🙂

In general this PR is good to go from my perspective, thanks so much @tyler36 for testing it with a fresh pair of eyes 🙂 👍

Mh ... quick update: In my tests the ddev site could also be opened via port 8443 🤔
https://github.com/mandrasch/ddev-codespaces-demo

Yes, I guess you're right; they must be ignoring cert failure I guess? Even curl doesn't work here:
$ curl -I https://localhost:8443
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

However, I can curl -I -k https://localhost:8443:
$ curl -I -k https://localhost:8443
HTTP/1.1 200 OK
Server: nginx
Date: Tue, 22 Aug 2023 22:21:29 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding

I can't even get curl to work with mkcert -install being done and all.  Perhaps they don't let you install a system CA, etc.

I actually think we're doing too much here. IMO it should just be:
{
  "image": "mcr.microsoft.com/devcontainers/universal:2",
  "features": {
        "ghcr.io/ddev/ddev/install-ddev:latest": {}
  }
}

And perhaps we should tell them about ddev config and such. Advanced users can go farther and do fancy things. But my experience with this is just fine.

However, studying this I discovered:

https://github.com/ddev/ddev/issues/5292
https://github.com/ddev/ddev/issues/5291

I actually think we're doing too much here. IMO it should just be: ... And perhaps we should tell them about ddev config and such. Advanced users can go farther and do fancy things. But my experience with this is just fine.

Very happy to follow your lead! No hard feelings if this PR get's closed for now. 😉
Just my assumption:

devs most likely also want the extra bash script, because the current one liner gets way to big: "postCreateCommand": "chmod +x .devcontainer/setup_project.sh && .devcontainer/setup_project.sh"
for me it was a pain to set it up, because you need time-consuming (full) rebuilds to test it
when we remove postCreateCommand a lot of the awesomeness of codespaces + ddev is gone imho

So my suggestion would be to at least link to an "official" reference where the separate bash script is explained which setups an existing ddev project in the repository automatically? Maybe in the "Extending" docs section? 🤔
Regarding this PR: Should I change something here?

However, studying this I discovered:

ddev start downloads traefik image when router is excluded #5292
ddev describe shows router: traefik when no router.  #5291

Oh. Can this be fixed within ddev or should I re-add ddev config global --omit-containers=ddev-router?  (if we follow through with this PR)

None of this is about the traefik router's use... that part is working fine. I just noticed that it's pre-downloading the traefik docker image (which doesn't get used), so it shouldn't be doing that.

As far as how much we should tell people to do, I'm in favor of just telling them to add the one line (about the ddev feature) and then giving them a link showing how they can do other things, like running a script.

Just fiy:
Since today I noticed this error with this setup:
2023-08-24 05:35:45.006Z: Status: Downloaded newer image for traefik:v2.10
2023-08-24 05:35:45.026Z: docker.io/library/traefik:v2.10
2023-08-24 05:36:00.913Z:  Network ddev-hello-world_default  Created 2023-08-24 05:36:00.914Z:
2023-08-24 05:36:01.159Z:  Container ddev-hello-world-web  Created
2023-08-24 05:36:01.188Z:  Container ddev-hello-world-db  Created
2023-08-24 05:36:02.375Z:  Container ddev-hello-world-db  Started
2023-08-24 05:36:02.604Z:  Container ddev-hello-world-web  Started 2023-08-24 05:36:02.606Z:
2023-08-24 05:36:03.780Z: Failed waiting for web/db containers to become ready: web container failed: log=, err=container /ddev-hello-world-web unhealthy:  2023-08-24 05:36:03.785Z:
2023-08-24 05:36:03.791Z: Something is wrong with docker or colima and /mnt/ddev_config is not mounted from the project .ddev folder. This can cause all kinds of problems.
2023-08-24 05:36:04.295Z: Failed to start hello-world: container(s) failed to become healthy before their configured timeout or in 120 seconds. This may be just a problem with the healthcheck and not a functional problem. (container 'web' exited, please use 'ddev logs -s web' to find out why it failed) 2023-08-24 05:36:04.297Z:
2023-08-24 05:36:04.319Z: postCreateCommand failed with exit code 1. Skipping any further user-provided commands.

2023-08-24 05:36:04.347Z: Error: Command failed: /bin/sh -c chmod +x .devcontainer/setup_project.sh && .devcontainer/setup_project.sh

ddev start manually works fine after this. Could be related to latest additions to docker-in-docker (integrated in universal image), https://github.com/devcontainers/features/issues/660.
I asked the maintainers here how to get the image and docker-in-docker-version for debug info: https://github.com/devcontainers/features/issues/634#issuecomment-1682620353

Hey @rfay, thanks very much for feedback!
My updated quick proposal for simplifying it:
https://ddev--5290.org.readthedocs.build/en/5290/users/install/ddev-installation/
I updated the one liner from
"postCreateCommand": "bash -c 'ddev debug download-images && ddev poweroff'"
to
"postCreateCommand": "bash -c 'ddev debug download-images && ddev poweroff'"
But after seeing the preview: It would also be an option to completely move the postCreateCommand one liner to the advanced section as well, like you already proposed. Guess it does not add very much benefit for first-time users who just want to checkout ddev in a cloud environment.

Something is wrong with docker or colima and /mnt/ddev_config is not mounted

This basically means that there is a significant problem; this normally only happens on Colima, which is why the code is there. I guess the ddev start -y is what failed here. Is it possibly the whole same problem with docker not running yet? Do we need to do a docker wait loop here as well?

"postCreateCommand": "bash -c 'ddev debug download-images && ddev poweroff'"

I'm not at all sure that the ddev debug download-images is offering value in this context either. I know the ddev poweroff is important for restarting Codespaces instances.

My updated quick proposal for simplifying it: https://ddev--5290.org.readthedocs.build/en/5290/users/install/ddev-installation/

I like the way you're clearing the way for a quick start and leaving the complicated stuff for later. This will work for me. Consider removing the postCreateCommand if we don't absolutely need ddev poweroff in the normal case.
Overall, this is very welcome and your maintenance of it is so much appreciated. When you say it's ready I'll pull it.

Looks like https://github.com/devcontainers/features/issues/634#issuecomment-1692306977 relates to the problem you saw, so maybe docker isn't really up before it lets things go forward. So strange that they're struggling with these things:

Important Note: /usr/local/share/docker-init.sh which starts/retries dockerd is added to the entrypoint command. This command runs in the background and is not a blocking script for the container startup. Since it's in the background, onCreateCommand/postCreateCommand/postStartCommand could all start executing before docker is fully running. If it takes docker too long, that could introduce flakiness in those lifecycle scripts.

Thanks very much @rfay for information and appreciation, very happy to help here (and hope that there are robust ways of using this technology in future, kind of a wild ride in the past weeks 😄 ).
I moved the postCreateCommand to advanced usage because of the issues.
Test repository for only using the most simple config, if anyone wants to test it in Codespaces:
https://github.com/mandrasch/ddev-codespaces-demo/tree/ddev-codespaces-simple
{
  "image": "mcr.microsoft.com/devcontainers/universal:2",
  "features": {
    "ghcr.io/ddev/ddev/install-ddev:latest": {}
  },
}

I'll let you know when this is PR finished for review, should be in the next days.

Hi @rfay, I added some additional information below the simplified starting guide which I found to be important for working with Codespaces.
Ready for review,
Happy to implement any change / removal / edit requests!  🙂  Cheers!

Ooops, just a bit more work to do in the spellcheck. If DDEVs was meant to be DDEV's (possessive) then change that too.

(Oh, was not aware of the automatic spell check. Nice workflow! :+1:)
Fixed.


Alt + key not working

I am working in OSX 10.13.6, tmux 2.7
I updated the following code to my .tmux.config file
        bind -n M-Left select-pane -L  # move left
        bind -n M-Down select-pane -D  # move down
        bind -n M-Up select-pane -U  # move up
        bind -n M-Right select-pane -R  # move right

It is not working smooth. Sometimes on pressing Alt+Left, it selects left pane and sometime it writes text "OD" on the terminal and the latter one is more frequent. Similarly for others.

Hello @gpakosz
Yes, the bindings do work in tmux. Actually it also work with your configuration.
But the problem is that in 1 of 10 attempts it actually change pane. In rest 9 attempts nothing happened.
While in the case that I make a normal .tmux.conf file and apply changes then Alt + key works absolutely fines in 10/10 attempts.

I have no idea, my configuration does nothing to existing select-pane bindings.
I tried your bindings and it works just fine here on macOS with iTerm 2

In my iTerm 2 holding the Alt key and using the arrow keys (OA,OB,OC,OD) are typed. May be some system issue. I will check it once. Thanks for your help @gpakosz :)

Do you still reproduce the problem when you set setw -g xterm-keys off?

Yes. No effect.

Same here. No solution to this? I've tried adding window switching with Alt+<num> but it doesn't have any effect.
# switch windows alt+number
bind-key -n M-1 select-window -t 1
bind-key -n M-2 select-window -t 2
bind-key -n M-3 select-window -t 3
bind-key -n M-4 select-window -t 4
bind-key -n M-5 select-window -t 5
bind-key -n M-6 select-window -t 6
bind-key -n M-7 select-window -t 7
bind-key -n M-8 select-window -t 8
bind-key -n M-9 select-window -t 9

Same here. No solution to this? I've tried adding window switching with Alt+<num> but it doesn't have any effect.
# switch windows alt+number
bind-key -n M-1 select-window -t 1
bind-key -n M-2 select-window -t 2
bind-key -n M-3 select-window -t 3
bind-key -n M-4 select-window -t 4
bind-key -n M-5 select-window -t 5
bind-key -n M-6 select-window -t 6
bind-key -n M-7 select-window -t 7
bind-key -n M-8 select-window -t 8
bind-key -n M-9 select-window -t 9

Hi,
I know it's been a long time, but I got the same problem and solved it.
Go to terminal menu File > Preferences > Shortcuts > Tab 1 then edit the shortcut or just hold a modifier (like Shift) and it should be deleted. The key binding in tmux should work.

I met similar issue, i.e. my configs using Alt keys start to fail, using Mac's native terminal. After some debugging, it turns out that we need to check the Use Option as Meta Key under Terminal's Edit menu, then we could use the Option key for Meta keybindings. Just to share my personal experience, to same some time for other Mac users with the same issue...

I met similar issue, i.e. my configs using Alt keys start to fail, using Mac's native terminal. After some debugging, it turns out that we need to check the Use Option as Meta Key under Terminal's Edit menu, then we could use the Option key for Meta keybindings. Just to share my personal experience, to same some time for other Mac users with the same issue...

Works like a charm! Thank you!


model.json is not created

Hi Guys,
I am not sure if I am the only one. My model json is not created when measuring. I'm not sure if it's because the measurement stopped in the middle and resumed?
Cheers

I also did run into this. Not clear why this is, it's in the code to skip model generation if resumed:
https://github.com/bramstroker/homeassistant-powercalc/blob/ac0b00e4244c93ae7dabc1b39447991c838b0181/utils/measure/runner/light.py#L187
Would (also) be nice if the model generation can be done from CLI without the full measurement cycle

Skip create model after resume was introduced with OCR support here, https://github.com/bramstroker/homeassistant-powercalc/commit/4fd3e0e652a6eb86da75e70ac5a3baf83eaec135. I'll try if model is generated properly after resume

I think the reason might be to prevent duplicate measurement of standby_power, as that happened in the beginning of the measure session previously.
But with a big refactor some time ago this happens at the end of the session now, so I don't foresee any issues.

I don't understand - then why is this happening? Maybe I didn't understand it correctly.
Is there any way around it (other than manually creating the model.json. Anyway, if I create it manually, I don't know what the standby power is - so in reality, "resuming" the measurement is not really useful since it actually causes more problems than it helps. (with exception of the shorter measurement time)
Translated with www.DeepL.com/Translator (free version)

Behavior is changed in latest version.
For now, yes you'll have to create model.json yourself. But you can just copy paste another and replace values. For the standby power. Toggle the light off manually in HA. And look in Shelly app how much power the plug reports.

I thought I'm using the latest version (or is the latest version not yet released?).
However - thx for the hint with the standby-power (I'm used to thinking too complicated from time to time 😄 ).


fix: fixed lookup subject request

Added a validation rule on subject_reference field , as it was not required till now

@tolgaOzen can you please review this regarding issue #Missing Validation in Lookup Subject

There are conflict in generated file , will re open


[FEATURE] API to flush indices out of cache

Is your feature request related to a problem?
Details in https://github.com/opendistro-for-elasticsearch/k-NN/issues/68

@naveentatikonda what is the method that we are using to clear the cache here?

hi @navneet1v @vamshin  any update on this ticket ? I read it from the ticket linked above it is to be released with  2.12 ?

hi @navneet1v @vamshin any update on this ticket ? I read it from the ticket linked above it is to be released with 2.12 ?

@alexworkorb The feature is ready. But, might not be released in 2.12 as the security review is still pending. We will prioritize this and try to get it released asap. Thanks!

Closing this issue as this feature will be released in v2.14.0


Simplify test setup

They are many duplicated setup code required for any new modules, mostly config system::Trait. There must be a way to avoid duplicate this code all over the places.
It also make any modification to system::Trait tedious as it have to change every single module test setup.
I am not sure what is the best way, but at least a macro can avoid most of the duplications.
All those code are duplicated and irrelevant for most of the tests
https://github.com/paritytech/substrate/blob/9b3e9f32cd5243d2eeff3d5d8337033aa64c091b/srml/aura/src/mock.rs#L35-L63

I cannot agree more. The system::Trait is becoming a bottleneck.
Ideally, I imagine this as the least that we can do:

Each module must expose its default Trait implementation and types.
When module x with runtime Test wants to have tests, it can implement Trait for Test or fallback to the default.

With a bit more effort we can also probably generalize the Builder() pattern with proc-macros to enable all tests to have it.
At some point if I have the time, I would really like to work on this.

I have a vague guess that maybe @KiChjang would be interested in this.

Indeed, it looks to me that a derive macro like DefaultTestSetup could generate all the necessary code for the default test framework setup. Let me see what I can do here.

Re-posting my suggestion https://github.com/paritytech/substrate/issues/12130#issuecomment-1282123683 since I think it might be a good starting point for this.

The vision in https://github.com/paritytech/substrate/issues/12130#issuecomment-1282123683 can also be achieved with something like this:

#[pallet::genesis_config] is structurally very similar to a pallet's hypothetical ExtBuilder.
Why not have #[pallet::genesis_config] generate a basic ExtBuilder for you, that you can extend?
crucially, this ExtBuilder would have a given fn build_and_execute(..) that can automatically call into try_state and such for you.


Merge/concat observers/objects

Version
2.6.11
Reproduction link
https://stackoverflow.com/questions/63016518/vue-js-javascript-objects-assign-not-working
Steps to reproduce
I need to merge or concatenate two observers/objects and order the result by date prop. But I always get an empty object. I have already used many methods like Object.assign() and obj: { ...obj1, ...obj2 } but nothing is working.
What is expected?
An object merge/concat
What is actually happening?
Get empty object after Object.assign()

Question is related in https://stackoverflow.com/questions/63016518/vue-js-javascript-objects-assign-not-working.
    methods: {
        getAllMessages: function () {
            // console.log(this.myID);
            let distinct = '';

            firebase.firestore().collection('private-messages').where('memberID', '==', `${this.myID}`)
                .orderBy('date').onSnapshot(res => {

                    let members = [];
                    res.forEach(doc => {
                        members.push(doc.data().uid);
                    });
                    distinct = Array.from(new Set(members));
                    // console.log(distinct);

                    this.getUserToTalk(distinct);
                });
        },
        getMyMessages: function (memberID) {
            let myMessages = [];
            firebase.firestore().collection('private-messages').where('uid', '==', `${this.myID}`).where('memberID', '==', `${memberID}`)
                .orderBy('date').onSnapshot(res => {
                    res.forEach(doc => {
                        myMessages.push(doc.data());
                    });
                });
            // this.myMessages = myMessages;
            return myMessages;
        },
        getMessages: function (memberID) {

            let messages = [];
            firebase.firestore().collection('private-messages').where('uid', '==', `${memberID}`).where('memberID', '==', `${this.myID}`)
                .orderBy('date').onSnapshot(res => {
                    res.forEach(doc => {
                        messages.push(doc.data());
                    });
                });

            // this.memberMessages = messages;
            return messages;

        },
        getUserToTalk: function (memberID) {

            axios.post('http://localhost/backend/getMemberToTalk.php', {
                "token": token,
                "whoToTalkTo": memberID,
            }).then(response => {
                if (response.data != "Error getting user data and tour") {

                    let joinedData = []
                    // console.log(response.data);

                    response.data.forEach(res => {

                        let id = res.memberID;

                        let messages = this.getMessages(id);
                        // console.log(messages);

                        let myMessages = this.getMyMessages(id);
                        // console.log(myMessages);

                        // if I use below assignment I can get the messages, but I need to concat them.
                        // so, if I use Object.assign({}, messages, myMessages);
                        // or let conversation =  { ...messages, ...myMessages }
                        // the result is always empty.

                        let talk1 = Object.assign(messages);
                        let talk2 = Object.assign(myMessages);
                        console.log(talk, talkmy);

                        let data = {
                            memberID: res.memberID,
                            memberProfileImg: res.memberProfileImg,
                            memberName: res.memberName,
                            memberLastname: res.memberLastname,
                            memberCity: res.memberCity,
                            memberState: res.memberState,
                            memberMessages: messages,
                            myMessages: myMessages,
                            // messages: conversation
                        }

                        joinedData.push(data);
                    });
                    // console.log(joinedData);

                    this.memberData = joinedData;
                    // console.log(this.memberData);
                } else {
                    console.log(response.data);
                }
            }).catch(error => {
                console.log(error);
            });
        },
}

If I return this.messages and this.myMessages the same thing happens. Is that possible to merge observers using vue.js?

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server or StackOverflow.

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server or StackOverflow.

Observers merging could be a feature request? Because I could not find this in docs or anywhere else.

You have two arrays, so you should spread them in an array: [...myMessages, ...messages]. You should also wait for the variables to be populated. It's not about merging observable objects, that is just the same as regular JS


chore(master): release git-jira-branch 2.1.0

:robot: I have created a release beep boop
2.1.0 (2024-08-29)
Features

add command to delete jira branches (#432) (2d92606)
create-command: add type option for custom branch types (#449) (9f0ca8d)
create-command: add support for task tickets and branches (9f0ca8d)
drop requirement on Jira env vars in non jira dependent commands (ed6ab33)
log errors on stderr instead of stdout (7ac511c)

Bug Fixes

deps: bump the production-dependencies group with 3 updates (#424) (1934f60)
deps: bump the production-dependencies group with 3 updates (#436) (07ace2e)
deps: bump the production-dependencies group with 3 updates (#447) (68f0503)
deps: bump the production-dependencies group with 4 updates (#426) (3c79191)
deps: bump the production-dependencies group with 7 updates (#430) (5b86cc3)
deps: bump the production-dependencies group with 7 updates (#438) (e3a564e)
deps: bump the production-dependencies group with 7 updates (#440) (73d6623)
deps: bump the production-dependencies group with 7 updates (#445) (bb0b123)
deps: bump the production-dependencies group with 7 updates (#451) (4f6eaf8)
deps: bump the production-dependencies group with 7 updates (#454) (f2e008b)
deps: bump the production-dependencies group with 7 updates (#457) (e27cfeb)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ccntrq/git-jira-branch/releases/tag/git-jira-branch-v2.1.0 :sunflower:


multiple values for a single key

... if the request is with files.
fixed: issue #48: Urllib3 doesn't allow multiple values for a single key if the request is with files. by adding list support for encode_multipart_formdata
by adding list support for encode_multipart_formdata

I ended up reimplementing this fix in a different way, does this work for you? d1d5fd1

Now the list of tuples is supported. It seems great! Thank you!

Excellent. :) Happy to help.


Question about Tracking

Hi, thanks for your excellent work!
When I try to use tools of tracking with data V2X-SIM-v2.0-mini, I don't know where is the “det_data_path" (the path of the preprocessed detection dataset.) Could you give me some guidance?

Hi @fanyimeng0 , please preprocess the V2X-Sim-2 mini detection dataset by running make create_data in tools/det on it.
Then when running the tracking task, set det_data_path to the processed dataset (the dataset you created using the command above).
This process is going to take a relatively short period of time, so I didn't upload the preprocessed mini dataset like what I did for the full dataset.

Thanks for your response!


[hotfix] [docs] Fix call wrong method as doc says in Joining documentation

What is the purpose of the change
fix call wrong method as doc says in Joining documentation.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)

@libenchao, thanks for contribution. not typo, you can see org.apache.flink.streaming.api.windowing.time.Time

fix call error method as doc says is better, not typo.

+1 for merging

Thanks for the PR @libenchao !
LGTM.
Merging...

Fixed in master: 946c6bb6bcb20dd2c539ecdcd43844bcbd91bb3b
Fixed in release-1.7: 30e0a8d64fe5e1d13d3a82064affa17439fc2d65


Post release automated changes for standbypool releases

Post release automated changes for azure-arm-standbypool

API change check
API changes are not detected in this pull request.


Allow number values for aliases

@micahgodbolt I found a regression was introduced in #46 - can you please have a look? I wrote a failing test to help you.

Sweet. Good catch. Got a bit of refactoring I want to do.
On Fri, Dec 16, 2016, 3:59 PM Kaelig Deloumeau-Prigent <
<EMAIL_ADDRESS>wrote:

@micahgodbolt https://github.com/micahgodbolt I found a regression was
introduced in #46 https://github.com/salesforce-ux/theo/issues/46 - can
you please have a look? I wrote a failing test to help you.
You can view, comment on, or merge this pull request online at:
https://github.com/salesforce-ux/theo/pull/72
Commit Summary

Test if aliases can have numerical values

File Changes

M test/props/prop-set.js
https://github.com/salesforce-ux/theo/pull/72/files#diff-0 (17)

Patch Links:

https://github.com/salesforce-ux/theo/pull/72.patch
https://github.com/salesforce-ux/theo/pull/72.diff

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/salesforce-ux/theo/pull/72, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABXlTGetDJmhx4U_TykETSzLWbY25MKDks5rIyXUgaJpZM4LPtE-
.

Yup...I was testing for "if string" rather than "if not object".
I fixed that, and did it in ONE place, by converting all non object aliases to objects. This'll make the code more consistent (no more alias value checking).


Adds rings for publish artifacts

Please @juanpedromoreno could you review? Thanks

Codecov Report

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

@@           Coverage Diff           @@
##           master      #62   +/-   ##
=======================================
  Coverage   85.82%   85.82%
=======================================
  Files          27       27
  Lines         402      402
  Branches        3        3
=======================================
  Hits          345      345
  Misses         57       57

Continue to review full report at Codecov.

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


Some new Sampling methods are missing

Today a friend asked me how you like the new Sampling methods dpx++ 3m sde ?  I looked and I don’t have it in the lists or settings.

I have this now .

And so on a friend’s PC
@TheLastBen  Please fix this.

@TheLastBen  Will you fix this?

I'll investigate the issue

I invite you to please consider it, as this is one of the features of version 1.6.0.
I decided to check it on other notebooks and it’s there.

try test running the notebook without the first cell and see if they're still missing, to make sure the issue is indeed in the notebook

try test running the notebook without the first cell and see if they're still missing, to make sure the issue is indeed in the notebook
I always run it this way without connecting Google Drive.

run pip install k-diffusion -U
I'll add it to the deps later

in a new cell, run
!rm -r /content/gdrive/MyDrive/sd/stablediffusion/src/k-diffusion
%cd /content/gdrive/MyDrive/sd/stablediffusion/src
!git clone https://github.com/crowsonkb/k-diffusion

I'll add it later


MetroAnimatedTab.SelectionChanged event fires whenever any control in any TabItem changes selection

Describe the bug
MetroAnimatedTab.SelectionChanged shall change only when the active selected TabItem changes. The actual behaviour is such that the event is fired when any control within any child (e.g. a selectedItem in a Combobox in a Grid in a TabItem) changes selection.
Steps to reproduce
Instantiate a MetroAnimatedTab with one TabItem, instatiate a Grid, and instatiate a Combobox within, having at least two items.
Changing the SelectedItem in the Combobox fires the MetroAnimatedTab.SelectionChanged
Expected behavior
MetroAnimatedTab.SelectionChanged shall fire only when the selected TabItem changes
Actual behavior
MetroAnimatedTab.SelectionChanged always fires for any changed selection
Environment
MahApps.Metro version: v2.3.4
Windows build number: Win10 20H2
Visual Studio: 2019 16.8.0
Target Framework: .Net fw, v4.8.2)

@Padanian Thx for reporting this issue, but it's not related to MahApps itself. If you use a normal TabControl then you will get exact the same result.

WpfApp6.zip


Icon submission: MEXC

URL of the site or app
https://www.mexc.com/
Logo / icon info
https://www.mexc.com/images/full-logo-dark.svg
Background color info
I used the logo color at bg and bg color at logo. Didin't change the color palette. Used same ones.
https://www.mexc.com/images/full-logo-dark.svg
Upload icon(s)

Anything else?
I'm GitHub noob. Opening PR is a really complicated thing for me. Sorry for opening as issue.
Confirmation

[X] I have read and carefully followed CONTRIBUTING document during the creation of the icon.

Logo needs to be in one path

Divine the line part with rest of the logo

I would make the logo slightly smaller, 600 px width is good number.

For 1st one, I'm using affinity photo (not designer) so I have no idea how to do it.
For 2nd one, I made it little bit smaller:

Fine, but I will not accept icons made with Affinity Photo after these ones.
Affinity Photo isn't proper vector graphics program, even if has some of the vector features.
I'm updating CONTRIBUTING document related to this and editing / adding icons to pack later.

Sorry, I just wanted to help project but I didn't use vector editing programs before. 🥲

Added to the repo!


[Storage] Refactor Blob download to address Unicode issues

This change refactors StorageStreamDownloader to address issues with Unicode decoding like #34065 along with some general refactoring. Essentially, this change introduces a chars keyword to the StorageStreamDownloader.read method that allows for reading a specific number of chars iff encoding is specified on download_blob. Behind the scenes we now use an IncrementalDecoder to handle the decoding of the bytes as they are streamed down and, when reading in text mode, stream one chunk at a time into the decoder.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-storage-blob

/azp run python - storage - tests


Improve sub-plot titles

A couple of improvements to the sub-plot titles for model and observation:

[x] Ability to specify a short name for the model instead of the full case name. The best place is probably the python parameter file.

[x] Add climatology years for model data. This information is available from a global attribute in the climatology netcdf files generated by ncclimo, for example:

                :yrs_averaged = "61-70" ;

[ ] Add climatology years for obs data, also read from a global attribute in the netcdf file.

[ ] Ideally, the obs name should also come from a global attribute in the netCDF file rather than being specified in the json file. This will minimize the chance of future mistakes.

For model names, it's basically done, https://github.com/ACME-Climate/acme_diags/pull/109

added a new parameter 'short_test_name' for user defined model name, todo: update documentation to reflect this new parameter change.
added 'year_averaged' to print out as part of the subtitle.

For observational data names, it depends on the processes of generating data. Will be done in a follow up fix.


Add commitlint action

I've added this action that lints Pull Request commit messages with commitlint to make sure a repo follows conventional changelog pattern :rocket:

@wagoid your changes have been merged, thanks for your contribution 👍


Remove extra unnecessary allocations

Reuse the same result buffer for scf.for
Handle subtensor inserts that alise result buffer.

I am surprised this just worked! Lets land this. I am going to dig into this a bit more to see how this actually ended up working :)

Will see how long this will hold as we move things up to tensors before bufferization, so far on the small scale example I am doing (tile-and-pad, tile, vectorize, bufferize) it seem to work so far :).


examples: enhance incremental_learning/helmet_detection_incremental_train

tracking the issues of the incremental learning example .

the namespace sedna-test should be renamed, default is recommanded.

in step 2: download base model, actually there are two models: initial-model for training and deploy-model for inference.

[ ] we should doc which fields should be updated, before just starting the incremental-job, such as the trigger/nodename
[ ] should download the dataset after starting the incremental job.

[ ] update workerSpec to podTemplate in the incremental job crd.
[ ] fix lib dataset relative-path issue

In above case eval-worker should report low precision/recall instead of raiseing exception.

[ ] remove the Prepare Worker Image section

inference worker continuous saved examples, result to disk diffusion

inference worker continuous saved examples, result to disk diffusion

[ ] need to test hard-example-mining algorithm

train worker consumed lot of memory(about 4GB)

[ ] alleviate this memory usage


Formatting issue with Jupyter Notebook dataframe rendered through nbconvert

The theme doesn't work well with dataframes generated by the Python library "pandas". The text in the column headers is squeezed together such that it's hard to read. Here's an example: https://jss367.github.io/blog3/df_test.html
Would it be possible to make the formatting work with these tables? This one, for example, works well with these types of tables: https://github.com/artemsheludko/flexible-jekyll

Hi!
It seems you are using some kind of converter to create markdown pages that would work with jekyll from a Jupyter Notebook.
I am not familiar with that tool, I guess to make it work you should try to change some of the options. Or try to look at:
https://github.com/Sylhare/Type-on-Strap/blob/master/_posts/2014-08-08-Markup- Syntax Highlighting.md
For how the markup and syntax coloring work on this theme.
If you can send me more information on what tool you are using, I would be able to troubleshoot with you.
Thanks

Correct, I'm using nbconvert. I'll read up on the link you posted.

I have done a couple of tests. It seems that the dataframe from the convertion is rendered through a table. And unfortunately this table is way too big to be rendered properly in the length of a normal screen using the default theme css.
So what could be done is to use the dataframe keyword to build a custom css to fit your need.
I don't see any dataframe on the link you sent me, but if you have a link how you'd want it to look like. I could help you with it.

Here's an example of the same tables I sent you, but using the flexible jekyll theme: https://jss367.github.io/blog2/df_test.html
I think this works well for moderately sized tables.

ok i'm working on a fix

Should look good now 😉

It looks great. Thanks so much!


Add workspaces to spotlight for easier project discovery

These would appear in spotlight with CodeEdit's icon and the workspace name, on clicking them they would open the corresponding workspace.Adding individual files to Spotlight is unnecessary as files are already indexed. Folders are also index in spotlight, but adding our own items would allow those folders to be opened directly in CodeEdit rather than Finder.Core Spotlight: https://developer.apple.com/documentation/corespotlight

Closing, duplicate of #1407


Update Gambit, Gerbil, Glow

Description of changes
Update Gambit, Gerbil (after a few years), and add Glow.
Previous PR to update Gerbil was rejected a few years back, because I imported a new object system POP to replace or complement the Nix extension system. I have wholly removed POP from this PR, because the fight was not worth the benefits.

Things done
Update the packaging and the packages for the Gerbil ecosystem.

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@7c6f434c


Update flir, stereo, laser3d, hyperspectral extractors

fullfield extractor

split out thumbnail vs full version

prioritize hyperspectral

clip to plot level
get pushed into BETYdb
accessing from THREDDs server

https://github.com/terraref/extractors-multispectral/pull/32/files
https://github.com/terraref/extractors-stereo-rgb/compare/update-fieldmosaic-2018

I think that the bin2tif is ready for review. Branch is issue-533 in extractors-stereo-rgb.

laser3d is on the list but I am not a member of that repository.

All 4 of these have been updated.


Create list of warnings that need to be added.

I need to have a list of warnings put together so that I can incorporate them into the program.

So far, I have the following incorporated into the code:

DNS Offline

Intruder Alert

The amish have acquired 3 keys

Just added a news alert and DNS back online message. Checking for more w/ team.

And there's also the fact that rugs are on sale at Walmart. Can't miss that.

Finished adding warnings for regionals.


@conda-forge-admin, please rerender

Additional comment:
No response

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I rerendered the recipe in conda-forge/perl-package-deprecationmanager-feedstock#2.


[Bug] Cant import Proxmox VMs NOR connect to VMs

General

[X] I have updated to the latest version of Nexterm.
[X] My bug has not been reported yet.

The Bug
I deployed the container.
Added 2FA.
Imported Proxmox Server. VMs not showing up?
Added Windows Server VMs. Cant connect. Connection screen opens and then closes instantly.
Tried it with a new deployment. Same error.
What device are you using to access the page?
In the browser
Which operating system is your Nexterm instance running on?
Linux

Possible duplicate of #76

It seems to be the same problem as #76. I'll create a PR to fix this issue. If your issue still occurs in the next version (1.0.2), feel free to re-open this issue.


Add includeOnce directive

When false it only includes the targeted include
When true it does a recursive include (default if not specified)

Instead of a flag introduce


Generate go code from multiple thrift files into the same directory

Currently compiler puts all generated Go code into two files - ttypes.go and constants.go. Because of that you can't compile multiple thrift files with the same namespace. They will just overwrite each other.
This PR fixes two things that closely related to each other:

Allow compiler to put generated Go code into the files with the same names as original thrift files. That mimics behaviour of other language generators. Types and services will be put into [thrift file name].go and constants will be put into [thrift file name]-consts.go. As a bonus, if you put everything into one file result will be basically the same as before.
The only difference is I put GoUnusedProtection__ variable into it's own .go file to prevent redefinition.

Prevent importing self package. Before this compiler would put self package into import section which Go doesn't support. Now compiler will recognize that types are from the same namespace. Without this you can't generate working Go code from multiple thrift files.

This PR doesn't add new compiler flag for this.

Looks like failed tests are not relevant to this PR


PublishValidator checks should consider message type

Currently, the PublishValidator verifies that a set of attributes for a Publish message contains either a source or a sink attribute.
However, based on https://github.com/eclipse-uprotocol/up-core-api/issues/104 it should instead verify that a Publish message either has a source only (Publish message) or both source and sink (Notification).

fixed via 6fcb81c320e9081847cf9e688cdd0493ca7e0ac7


feat: added clusterdeployment list per managedclustergroup

Oops, wrong target.
Once done, I will link the new PR to the proper target.


Fix for the NicVO.java regression.

Renamed set*() methods to correct naming.

The updateBuilder will check if the DAO has changed based on the set*() methods. When it can't resolve one, it won't update. After learning this I changed the set*() method names to reflect the names of the variable fields.

LGTM

Tested it in a new environment. The nics are correctly put in the db again.

@remibergsma @karuturi Please review!

LGTM. lets wait for travis and other jenkins verifications.
In future, can you club all refactoring work in a branch and merge them together? That way, we can test it once(giving bigger time window for everyone to verofy) and merge
Also, I think this refactoring is a candidate for 4.7. We are already close to RC on 4.6(once 4.5.2 is done) and cannot afford regressions at this stage.

@karuturi I came to that conclusion in the previous pr. I will stack all refactoring work in a branch. And send a PR when done.

@borisroman Thanks! I'll run some tests later tonight. Travis is green, didn't see an Apache build reporting results (yet?).

LGTM Verified that a new cloud deployment had working system VMs again.

cloudstack-pull-analysis 296 failed due to: Expected exactly 2 but it took more than 3 microseconds between 2 consecutive calls to System.nanoTime(). Seems not related.

I think we have to disable this test, enlarging the period even more beats every intention of its use. not related indeed

Check, as far as I can tell everything is OK. And since master is broken now anyway, I think it's time to merge this to fix it.

hm, you shouldt merge anything to a broken master that isn't hellbound on fixing it.

@DaanHoogland It does fix the problem, I just feel a bit blind sometimes by the builds that seem less reliable lately so then it's hard to be sure.
But anyway, when looking back we should have quickly reverted the initial PR that introduced the problem. Next time we should do that. Benefit is master is stable again, plus there is time to work on a fix that can then be send as a PR along with the original commits.


Short solution needed: "Inserting data into table example" (clickhouse)

Please help us write most modern and shortest code solution for this issue:
Inserting data into table example (technology: clickhouse)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

Inserting data into table example


BAEL-3018

Guide to R2DBC

Hi Mark,
Sure you want to downgrade from 1.0 to 0.8?
On Fri, Jul 5, 2019 at 8:44 AM Mark Paluch<EMAIL_ADDRESS>wrote:

@mp911de commented on this pull request.
In spring-5-data-reactive/pom.xml
https://github.com/eugenp/tutorials/pull/7230#discussion_r300668001:

@@ -53,6 +53,20 @@
io.reactivex.rxjava2
rxjava

<groupId>org.springframework.boot</groupId>

<artifactId>spring-boot-starter-webflux</artifactId>

<groupId>org.springframework.data</groupId>

<artifactId>spring-data-r2dbc</artifactId>

<version>1.0.0.M1</version>

<groupId>io.r2dbc</groupId>

<artifactId>r2dbc-postgresql</artifactId>

<version>1.0.0.M6</version>

Please upgrade to 0.8.0.M8
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/eugenp/tutorials/pull/7230?email_source=notifications&email_token=AAHP3PD2IZZOYKX62MZVZKTP5464PA5CNFSM4H4SXX3KYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB5TKH4A#pullrequestreview-258384880,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHP3PA6KWW6DBAGQBCWP3LP5464PANCNFSM4H4SXX3A
.

--
Rodrigo Graciano
<EMAIL_ADDRESS>

That's not a downgrade. R2DBC has renumbered releases between milestone releases. M7 was 1.0 M7, M8 was 0.8 M8. See https://r2dbc.io/2019/05/13/r2dbc-0-8-milestone-8-released for the full explanation.

Understood. If I upgrade to M2 and 0.8 M8 there are errors.
java.lang.NoSuchMethodError: org.springframework.transaction.reactive.TransactionSynchronizationManager.currentTransaction()Lreactor/core/publisher/Mono;
at org.springframework.data.r2dbc.connectionfactory.ConnectionFactoryUtils.doGetConnection(ConnectionFactoryUtils.java:88)
at org.springframework.data.r2dbc.connectionfactory.ConnectionFactoryUtils.getConnection(ConnectionFactoryUtils.java:70)
TransactionSynchronizationManager.currentTransaction does not exists at spring-tx:5.2.0.M3
If M1 and 0.8 errors:
java.lang.NoClassDefFoundError: io/r2dbc/spi/Blob
at io.r2dbc.h2.codecs.DefaultCodecs.<init>(DefaultCodecs.java:35)

I found a workaround. Need to use spring-tx:5.2.0.M2.
H2 .199 would not work with M1 and I was using .197. Seems okay with M2.
Will submit the new PR in a few

As there's a dependency to MongoDB reactive, my repository is trying to be resolved to MongoDB and tests will fail.
Cannot register bean definition [Root bean: class [org.springframework.data.mongodb.repository.support.ReactiveMongoRepositoryFactoryBean
Any way to avoid it Mark?

Currently, you need to scope class path scanning of MongoDB and R2DBC repositories because of a bug in Spring Data R2DBC, see spring-projects/spring-data-r2dbc#145.


Symbolizing arguments passed to Uglifier from _config.yaml

The Jekyll Utils helper method for symbolizing hash keys does not deeply symbolize keys. Therefore, the following configuration in _config.yaml results in an error:
javascript:
  uglifer:
    harmony: true

This is the error, raised by a call to Uglifier.new(config[:uglifer]):

Conversion error: Jekyll::Converters::Js encountered an error while converting 'assets/js/main.js':
Invalid option: harmony

My solution uses Jekyll::Utils.symbolize_hash_keys(config[:uglifer]) for the argument to Uglifier.new() to work around the issue.

Thanks @NotDaveLane, I ended up creating a deep_symbolize_keys Hash extension to take care of this in the javascript_config method so the work wasn't duplicated in convert.


Set up CI with Azure Pipelines

[skip ci]

 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.:x: ashish1682Git sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Feature list: bugs in filter conditions

I went to Borrelia feature list, by default it shows PATRIC CDS.
Searched for keyword glycolysis, it shows ALL genes matching glycolysis, previous filters for PATRIC and CDS are not applied, even though they are still displayed on the page.
Next, I clicked X next to keyword to remove it, it ended up removing other filters as well.
Below are the series of screenshots.
-Maulik

Fixed, will be on alpha shortly.

Thanks. Verified the fix on alpha.


[Feature request] - More detailed documentation/info

FAQ page. You need to give more information about how to use this and fees applied, votes etc
Using the free credits to post - OK. But after posting those, it doesn't say how much I need to pay for a new post.
It should be also available the option to just pay a LN invoice for a new paid post, if I do not have enough funds in wallet

Thanks for popping my Issues.
As for 1 and 2, every action (posting/commenting/upvoting) is 1 sat and I don't intend to ever change this on the main page. I agree though that this should be made clear. I have this planned as part of my work for the upcoming week which I usually post of twitter https://twitter.com/k00bideh/status/1410650020454572037
For 3, if it's just 1 sat to post, do you still want this mechanic? The fees might be higher than the action cost if you don't have a channel with my node.

Fair enough. Thanks for answering

Tooltip now shows dust cost of actions. Going to close. If this is insufficient please let me know

I've also written a FAQ to make things clearer.

Thank you @huumn! Perfect wording: "These will never cost more than 1 sat." ! Yes!

lol, by accidentally linking this issue in #566, I realized that

It should be also available the option to just pay a LN invoice for a new paid post, if I do not have enough funds in wallet

was apparently one of the first issues and we finally did that in #336


Doesn't work with TypeScript's Rename Symbol

Steps to Reproduce

Select a camelCased token in a TypeScript file
Select Rename Symbol from the Command Palette
Hit ctrl+left or ctrl+right to navigate to a subword

Expected Results
It works just like it would if I wasn't in the Replace widget.
Actual Results
Nothing if when: "editorTextFocus" is set.  Replace widget closes if it is not set.

Yeah I know. I wish this was possible, but alas, the the rename widget, and other inputs like search boxes, are as of this writing implemented as a straight up HTMLInputElements. And with, as far as I can tell, no extension points.
renameInputField.ts
However, I noticed once that whatever is selected when Rename Symbol is initiated is pre-selected in the rename widget. So what I have trained myself to do instead is to select the part of the word I want to change before hitting F2 when subword navigation is still possible. It's not optimal, but it's what we've got right now.


Fixes #1388

just a little one, but without it the code doesn't build with the old version of visual studio that conda uses for python 2.7

Silly windows...

Yeah, there is another problem with the tests using that old compiler; I will try and get it cleared up before the actual release, but it doesn't seem critical


Replace reference to Wyam with Statiq

Statiq.Web repository does not exist yet so just guessing this will be the name based on the old name.
Given Powershell is prevalent and cross-platform, I added example commands for it as well.

Thanks! I'll probably need to keep adjusting this file as we go, but it's a great start.


[SPARK-15819][PYSPARK] Add KMeanSummary in KMeans of PySpark

What changes were proposed in this pull request?
Add python api for KMeansSummary
How was this patch tested?
unit test added

Test build #60157 has started for PR 13557 at commit 711c26e.

Test build #60157 has finished for PR 13557 at commit 711c26e.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KMeansSummary(JavaWrapper):

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/60157/
Test FAILed.

Test build #60160 has started for PR 13557 at commit 72634c7.

Test build #60160 has finished for PR 13557 at commit 72634c7.

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/60160/
Test FAILed.

Test build #60163 has started for PR 13557 at commit aacc4db.

Test build #60163 has finished for PR 13557 at commit aacc4db.

This patch fails Python style 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/60163/
Test FAILed.

Test build #60167 has started for PR 13557 at commit d1d2222.

Test build #60167 has finished for PR 13557 at commit d1d2222.

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

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

Merged build finished. Test FAILed.

Test build #60171 has started for PR 13557 at commit 73bfb05.

Test build #60171 has finished for PR 13557 at commit 73bfb05.

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/60171/
Test FAILed.

Test build #60175 has started for PR 13557 at commit 003af9f.

Test build #60175 has finished for PR 13557 at commit 003af9f.

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

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

Merged build finished. Test FAILed.

Test build #60236 has started for PR 13557 at commit d2fd75a.

Test build #60236 has finished for PR 13557 at commit d2fd75a.

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/60236/
Test PASSed.

@jkbradley  Could you help review it ? Thanks

Sorry for the delay!  I'll try to review it as soon as QA for 2.0 is done.

PR rebased, ping @jkbradley  Please help review when you have time.

Test build #63600 has started for PR 13557 at commit 099d42d.

Test build #63600 has finished for PR 13557 at commit 099d42d.

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

Merged build finished. Test PASSed.

Test build #67048 has started for PR 13557 at commit 19f871f.

Test build #67048 has finished for PR 13557 at commit 19f871f.

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/67048/
Test PASSed.

Test build #67127 has started for PR 13557 at commit c11b6a0.

Test build #67127 has finished for PR 13557 at commit c11b6a0.

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/67127/
Test PASSed.

ping @jkbradley @holdenk

jenkins test this please.

Test build #67585 has started for PR 13557 at commit c11b6a0.

Test build #67585 has finished for PR 13557 at commit c11b6a0.

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

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

Merged build finished. Test PASSed.

I created SPARK-18282 and the PR: https://github.com/apache/spark/pull/15777 to implement this interface for GMM and BisectingKMeans. These two PRs will affect one another, I'm not sure it matters too much which gets merged first, but whichever one does get merged first needs to implement a parent class ClusteringSummary which will have (for now) three child classes for KMeans, BisectingKMeans, and GMM. This is a result of https://github.com/apache/spark/pull/15555.

ping @zjffdu Could you address @jkbradley 's comment, then I can help to get this in. It's better we can merge this into Spark 2.1. Thanks.

ping @zjffdu - @sethah's PR for the GMM and BKM has gone in it might be good to update this PR now then?

Test build #69245 has started for PR 13557 at commit f94564e.

Test build #69245 has finished for PR 13557 at commit f94564e.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KMeansSummary(ClusteringSummary):

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

Merged build finished. Test FAILed.

Test build #69246 has started for PR 13557 at commit b3a8068.

Test build #69246 has finished for PR 13557 at commit b3a8068.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KMeansSummary(ClusteringSummary):

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/69246/
Test PASSed.

Test build #69291 has started for PR 13557 at commit 99b03be.

Test build #69291 has finished for PR 13557 at commit 99b03be.

This patch fails Python style 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/69291/
Test FAILed.

Test build #69292 has started for PR 13557 at commit cfd2212.

Test build #69292 has finished for PR 13557 at commit cfd2212.

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/69292/
Test PASSed.

@sethah Thanks for the review, I have updated the PR.

Test build #69302 has started for PR 13557 at commit 01c6da9.

Test build #69302 has finished for PR 13557 at commit 01c6da9.

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/69302/
Test PASSed.

Thanks for updating this @zjffdu, it looks good to me now that @sethah's comments have been addressed maybe we can get @davies or @MLnick to take a final pass?

Test build #69368 has started for PR 13557 at commit 032bb9d.

Test build #69368 has finished for PR 13557 at commit 032bb9d.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KMeansSummary(ClusteringSummary):

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

Merged build finished. Test PASSed.

LGTM, merged into master and branch-2.1. Thank you all.


Add backoff policy

Added 6 new properties to control back off policies:

kafka.retry.backoff.ms -  Kafka retry backoff in milliseconds
gcs.retry.backoff.initial.delay.ms - Initial retry delay in milliseconds
gcs.retry.backoff.max.delay.ms - Maximum retry delay in milliseconds
gcs.retry.backoff.delay.multiplier - Retry delay multiplier
gcs.retry.backoff.total.timeout.ms - Retry total timeout in milliseconds
gcs.retry.backoff.max.attempts - Retry max attempts

move it to draft so far. and will re-open it after command new version has been released