neovim: support mini.base16

mini.base16 provides greater plugin support than base16-nvim & generally looks nicer IMO. It would be nice to be able to select which plugin system to be used, or switch entirely to mini.base16.

Never used mini.nvim before but I can test the PR if you decide to work on this


SPFX extension navigation events bug on SharePoint sites with latest features

We use SPFX extension ApplicationCustomizer to display breadcrumbs in top header and this is working very well. However, we have noticed navigatedEvent doesn't fire on SharePoint sites with latest features e.g. where a search box appears in middle of top header.
This issue is having serious impact on our users as breadcrumbs displayed in top placeholder aren't updating when users browse from one library to another. Please fix this otherwise clients are going to start losing trust in these solutions.
Below is a screenshot of top header taken from a SharePoint modern group connected site where this issue is occurring.

Can you share some code that demonstrates how this works and isn't working to help with reproducing the issue?

Please find the code below...Again this works fine for some modern site and problem only manifests itself for a site where 'search box' appears in the middle of header as per previous screenshot.
`import * as React from "react";
import * as ReactDom from "react-dom";
import { override } from "@microsoft/decorators";
import { Log } from "@microsoft/sp-core-library";
import {
BaseApplicationCustomizer,
PlaceholderContent,
PlaceholderName
} from "@microsoft/sp-application-base";
import { Dialog } from "@microsoft/sp-dialog";
import * as strings from "SiteNavApplicationCustomizerStrings";
const LOG_SOURCE: string = "SiteNavApplicationCustomizer";
/**

If your command set uses the ClientSideComponentProperties JSON input,
it will be deserialized into the BaseExtension.properties object.
You can define an interface to describe it.
*/
export interface ISiteNavApplicationCustomizerProperties {
message: string;
}

//https://www.eliostruyf.com/things-to-check-in-your-spfx-application-customizer-after-page-transitions/
interface NavigationEventDetails extends Window {
isNavigatedEventSubscribed: boolean;
}
declare const window: NavigationEventDetails;
/** A Custom Action which can be run during execution of a Client Side Application */
export default class SiteNavApplicationCustomizer
extends BaseApplicationCustomizer {
private topPlaceholder: PlaceholderContent | undefined;
@override
public onInit(): Promise {
Log.info(LOG_SOURCE, Initialized ${strings.Title});
//Subscribe to navigatedEvent only once
if (!window.isNavigatedEventSubscribed) {
  this.context.application.navigatedEvent.add(this, () => {
    this.startReactRender("navigatedEvent");
  });
  window.isNavigatedEventSubscribed = true;
}

this.renderPlaceHolders();
return Promise.resolve();

}
private renderPlaceHolders(): void {
console.log("SiteNavApplicationCustomizer.renderPlaceHolders");
// Handling the top placeholder
if (!this.topPlaceholder) {
  //Create a new topPlaceholder element
  this.topPlaceholder = this.context.placeholderProvider.tryCreateContent(
    PlaceholderName.Top, { onDispose: this._onDispose }
  );

  // The extension should not assume that the expected placeholder is available.
  if (!this.topPlaceholder) {
    console.error("The expected placeholder (Top) was not found.");
    return;
  }

  //Render React component
  this.startReactRender("renderPlaceHolders");
}

}
private startReactRender(message) {
console.log("startReactRender", message);
//Exit if topPlaceholder element does not exist
if (!this.topPlaceholder || !this.topPlaceholder.domElement) {
  return;
}

//Delay rendering of react component
let self = this;
setTimeout(() => {
  self.createReactElement();
}, 200);

}
//ListId and ItemId properties are there to detect navigation change and refresh the mounted component.
private createReactElement() {
console.log("createReactElement");
const element: React.ReactElement = React.createElement(
SiteNavContainer,
{
context: this.context,
listId: this.context.pageContext.list && this.context.pageContext.list.id ? this.context.pageContext.list.id : null,
itemId: this.context.pageContext.listItem && this.context.pageContext.listItem.id ? this.context.pageContext.listItem.id : null
}
);
ReactDom.render(element, this.topPlaceholder.domElement);
}
private _onDispose(): void {
console.log('[SiteNavApplicationCustomizer._onDispose] Disposed custom top and bottom placeholders.');
this.context.application.navigatedEvent.remove(this, this.startReactRender);
window.isNavigatedEventSubscribed = false;
}
}
`

Further to above...below is the console log when user clicks links on quick launch.
/**
 *	Start of log when 'Documents' link is clicked in quick launch
 *	Entire page is loaded
 */
Initialized ClientSideExtensionHelper
spofiles-mini-340e7fde.js:1 Defined clientSidePlaceholders: DialogContainer,Top,Bottom
site-nav-application-customizer_2ca9895902343e0452404c0d5304c620.js:15 startReactRender navigatedEvent
site-nav-application-customizer_2ca9895902343e0452404c0d5304c620.js:15 SiteNavApplicationCustomizer.renderPlaceHolders
site-nav-application-customizer_2ca9895902343e0452404c0d5304c620.js:15 startReactRender renderPlaceHolders
site-nav-application-customizer_2ca9895902343e0452404c0d5304c620.js:15 createReactElement

**
 *	Log when 'Pages' link is clicked in quick launch
 *	Partial page load where pages library is loaded
 */
site-nav-application-customizer_2ca9895902343e0452404c0d5304c620.js:15 startReactRender navigatedEvent
site-nav-application-customizer_2ca9895902343e0452404c0d5304c620.js:15 createReactElement

**
 *	No further events are raised when 'Documents' link is clicked again
 *	Partial page loads where Documents library is loaded.
 */

same as #4054 which is being fixed soon

According to MS eng, it's a dupe of another issue so flagging as such. Monitor #4054...


To compile and run the new exe, remember to unzip and add the thdtimer

Quite obvious for delphi programmer.  Never did any Pascal one, other than Turbo Pascal for Bridge in 1980s, I guess ... and it works.  Still not sure about the TCP.  But this is also needed for the original source.  Just in case someone else also find the issue.
The full process is

get the delphi 5 from archive.org
there is a serial number in the .ISO
I successfully install delphi 5 onto a w7 bottle under crossOver
also remember to let the crossOver ready (or the control panel to run
if you run with exception to 0000000 must need those other files (like rom etc.)
For es, it should be like this (and ai1000 need more ... etc. and MD100 ...)
For em, it seems the generated pb2000c.exe cannot run on its own.  Copy and write over the runable es version.

Hi there - yes to all of the above, build instructions are the same as per Piotr's original version. But you don't need to compile this yourself, there are already compiled binaries under "releases": https://github.com/wowczarek/pb2000em/releases

I have some issues need to go immediately to hosiptal.  Will read those later.
Quickly on top of the above, i tried to use md100.c and ramtran2.c.  It turns out I need to under osx (arm m2) a few minor issues.  But it works (sort of; seems so far ramtran2 does not report real time unlike the md100; still it can read the ram after minor updates):
listX07.c:523:12: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Wimplicit-int]
    static colon_pending = FALSE;
    ~~~~~~ ^
    int
listX07.c:524:12: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Wimplicit-int]
    static remark_pending = FALSE;

i.e. listX07 2 lines have to be changed for md100.c to compile under osx gcc (somehow )
    static bool colon_pending = FALSE;
    static bool remark_pending = FALSE;

...
files:=	$(TARGET)/wav2raw $(TARGET)/wav2wav	\
	$(TARGET)/wave730 \
	$(TARGET)/wave850 $(TARGET)/waveX07	\
	$(TARGET)/list702 $(TARGET)/list730	\
	$(TARGET)/list850 $(TARGET)/list8000	\
	$(TARGET)/listX07 $(TARGET)/list74  	\
	$(TARGET)/bas702  $(TARGET)/bas730	\
	$(TARGET)/bas850  $(TARGET)/basX07	\
	$(TARGET)/md100 \
	$(TARGET)/ramtran2
...
$(TARGET)/ramtran2:	ramtran2.c
	$(CC) $(CCOPTS)	ramtran2.c
...

/


dump modify command syntax change

The syntax for dump_modify format has been changed. A new keyword line must be included for input files generation.  For example, old format
'dump_modify     aiida format "%16.10f %16.10f %16.10f"\n'

should be updated to
'dump_modify     aiida format line "%16.10f %16.10f %16.10f"\n'

such as in combinate script

Thank you.
 So I will merge development
branch to master soon after a little testing including this issue.

That will be great. Do you have any estimate of the merge?
It would be great if there is some documentation included as well.
I will be happy to contribute to this repo in any possible way.

I'm a little busy these days and I have not much time to work on this.
I will try to do it next week. If you want you are welcome to try the development
branch in which dump_modify format is already fixed .
You are very welcome to contribute, I recently changed job and I really don't have
much time for adding new potentials and support additional features of LAMMPS.
So just let me know in which degree of implication you would like to contribute.
(testing/coding/etc..)
If you are interested in some particular feature I can focus on it.


marginal likelihood of testing?

Hi guys,
It seems that the objective of the model is the negative log marginal likelihood calculated on training data. Is there any existing function to calculate the marginal likelihood in the testing period?
If not, where can we get the covariance matrix to calculate it?
Thanks in advance

Hi, you can use model.inference_method.inference method;
For example:
def test_log_likelihood(model, X_test, y_test):
_, test_log_likelihood, _ =  model.inference_method.inference(model.kern, X_test, model.likelihood, y_test, model.mean_function, model.Y_metadata)
return test_log_likelihood
Note that you need normalize y_test as y_train. (You can use model.normalizer.normalize if you define normalize=True in model parameters.)


[requirements] Upgrade netdiff to 0.6.0

Coverage remained the same at 100.0% when pulling 67c0b886f4ce280739474ea69c65af239f02edd1 on netdiff into e67286e0c48e3f2278c24e08eff72f813f6e6253 on master.

Coverage remained the same at 100.0% when pulling d470fe2cdf6f1ac32890a39c8103419f2407e7b8 on netdiff into e67286e0c48e3f2278c24e08eff72f813f6e6253 on master.


Redirect to ?next path on login

If a ?next query param is provided, redirect to it upon successful login (for oath)

@keithjgrant and I walked through this and confirmed that the flow is working.  The only gotcha was that the UI's proxy isn't letting /o requests through.  Once we tweaked the proxy we were able to follow the entire flow through from creating an application to authorizing and generating a token.


[Bug]: TransportOpenUserCancelled: Access denied to use Ledger device in chrome extension

Impacted Library name
@ledgerhq/hw-transport, @ledgerhq/hw-transport-webhid
Impacted Library version
6.28.1
Describe the bug
When attempting to connect using webHID (and really any transport type) in a chrome extension the error "Error: TransportOpenUserCancelled: Access denied to use Ledger device" appears, despite the device selection popup never showing.
The exact same logic works no problem from a webpage, this used to work no problem in the extension but since about a month and a half ago it has stopped working.

Expected behavior
To work as it used to, connecting to the ledger the same as from a webpage.
Additional context
Firmware is up to date, currently testing on osx chrome version 111.0.5563.110 (Official Build) (arm64)

After a bit more debugging, I changed TransportWebHID.create() to TransportWebHID.request()

It now throws "Error: TypeError: Cannot read properties of undefined (reading 'open')" - it does not open the device selection popup - while the same code on the web version works.
Highlighted line is what is throwing the error

Seems to be something rotten in here in extension contexts.

I tried to call transportWebHID.list(), and got the following:
On website:

On extension:

Looks like this may be a chrome issue
calling await navigator.hid.requestDevice({
filters: [],
});
from website, displays popup as expected:

from extension it just instantly returns an empty array:

Visit the official page to initiate a chat with an agent on the live chat to report this for review and for further assistance via Ledger chat

damn, phishing on github, never seen that before

I got the same issue, let me know if I can help with any testing.

I got the same issue, let me know if I can help with any testing.

Hi @injectedfusion  visit the official Ledger page to initiate a chat with the support team on the live chat to report your errors for review and for further assistance via Ledger Support


Emit ABI to working directory (again)

I accidentally changed ABI output path to config.outDir from cliArgs.workingDirPath in the big refactor.
And then I wrote tests to make sure the bad behaviour is preserved :P
This PR should fix it.

...why cjs files are being removed from SDK dir? Were they leftovers? If yes then maybe we need to ensure to delete SDK dir and regenerate it entirely before running tests?

Yes, exactly. I'll add rm ./sdk before end-to-end tests start.


Behavior is reversed for Log and Native Docks - Hide Log keybindings

Describe the bug
Keybindings for Log hide the log widget. Keybindings for Native Docks - Hide Log toggle the log widget's visibility.
To Reproduce
Steps to reproduce the behavior:

Go to 'Keybindings'
Search for 'Log'
Bind a key to 'Log'
Bind a key to 'Native Docks - Hide Log'
Close Keybindings
Ensure log widget is visible (View > Native Docks > Show Log)
Press key bound to 'Log' and observe that log widget is hidden.
Press key bound to 'Log' again and observe that log widget remains hidden.
Press key bound to 'Native Docks - Hide Log' and observe that log widget becomes visible.
Press key bound to 'Native Docks - Hide Log' again and observe that log widget becomes hidden.

Expected behavior
Swap the underlying actions identified with 'Log' and 'Native Docks - Hide Log' in Keybindings.
'Log' action should make the Log view both visible and have input focus.
Desktop (please complete the following information):

OS: macOS Big Sur
Version 11.3.1

This issue is OBE with the log/console global area refactor.


Update service-bus-event-hubs-get-started-send-c.md

The Qpid Proton 0.7 tar.gz file was moved under archive path on Apache org. The previous link isn't available anymore so the user can't finish this guide in the right way.

Hi @ppatierno, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

@sethmanheim - Could you review this update proposed by @ppatierno in the public repo?

@tysonn OK to merge, @ppatierno thanks for the contribution!

@sethmanheim you're welcome ! Happy to help ;)


Create PR Deck

create a slide deck for PR purposes to share with media outlets.

https://hackmd.io/@DAOMasons/B1wMnywEp/edit
"Evolutionizing" Grant Funding on Arbitrum
Grant Ships is Empowering Community Through Innovative Grant Gaming

What is Grant Ships?

Evolutionary grants game within the Arbitrum ecosystem.
Designed to reward players for providing positive impact for the ecosystem.
Incorporates gamification to surface the skilled and effective operators.

The Future with Grant Ships

Self-sustaining, community-driven system.
Reduced need for centralized control.
Enhances awareness of initiatives on Arbitrum.
Beta testing with first live rounds of Grants begins in February### "Evolutionizing" Grant Funding on Arbitrum

Grant Ships is Empowering Community Through Innovative Grant Gaming

What is Grant Ships?

Evolutionary grants game within the Arbitrum ecosystem.
Designed to reward players for providing positive impact for the ecosystem.
Incorporates gamification to surface the skilled and effective operators.

The Future of Grant Ships

Self-sustaining, community-driven system
Decreased reliance on centralized control
Improved visibility of initiatives on Arbitrum
Beta testing for Grants commences in February 2024

Book DAO Masons for an Apperance!
We would love the opportunity to spread the message about Grant Ships and the opportunities available to developers and the Arbitrum Community.

X
Telegram
email

https://docs.google.com/presentation/d/1BcF5DpSzvVqHxwLfaxE3Px5JK2Cj1EkhftOhYUvzmqc/edit?usp=sharing

Dear [Recipient's Name],
I hope this message finds you well. My name is [....], and I was referred to you by Shawn from Plurality Labs. I represent DAO Masons, a dynamic and forward-looking DAO currently collaborating with Plurality Labs.
We are excited to announce the launch of a beta program titled "Grant Ships," an initiative designed to foster innovation and community engagement. Currently, our team is diligently working towards a mid-February rollout. An essential aspect of this program's success hinges on community awareness and participation.
To this end, we are actively seeking opportunities to showcase our program across various platforms. We believe that participating in community calls, Twitter Spaces, and podcasts, especially within the Arbitrum community, would be instrumental in generating the necessary buzz and engagement.
We are keen on exploring any avenues where our DAO can contribute and share insights about the Grant Ships program. If you see potential for collaboration or can assist us in reaching a broader audience, we would be delighted to discuss this further.
Thank you for considering our request. I look forward to the possibility of working together to make this initiative a success.
Warm regards,
[..name..]
[Your Position]
DAO Masons

closing for now. Have rough deck prepared, can fine tune/perfect as needed.


[Feature]Add "View Password" Functionality on Login Page

Description
Feature Request: Add "View Password" Functionality on Login Page
Description
We propose adding a "View Password" functionality to the login page. This feature will allow users to toggle the visibility of their password, enhancing the usability of the login form.
Details

Feature Name: View Password Toggle
Purpose: Improve user experience by allowing users to see their password while typing
Functionality:

Add an eye icon (or similar) inside the password input field.
Clicking the icon will toggle the password visibility between hidden (••••••) and visible (plaintext).
Ensure the icon is intuitive and its function is clear to the user.

Implementation Steps

Design:

Add an eye icon within the password input field.
Ensure the design is consistent with the overall theme of the login page.

Development:

Modify the HTML structure of the password input field to include the eye icon.
Implement JavaScript to handle the toggle functionality:

Change the input type from password to text and vice versa.
Update the icon to reflect the current state (e.g., open eye for visible password, closed eye for hidden password).

Ensure the implementation is accessible and works across all supported browsers and devices.

Example of Current Design

Benefits

Enhances user experience by allowing users to confirm their password input.
Reduces the likelihood of password entry errors.

Additional Context

Ensure the feature adheres to accessibility standards, allowing users with disabilities to benefit from the new functionality.
Consider adding a tooltip or helper text to explain the purpose of the eye icon for users who may be unfamiliar with this feature.

Screenshots
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)

Congratulations, @Sahilll15! 🎉 Thank you for creating your issue. Your contribution is greatly appreciated and we look forward to working with you to resolve the issue. Keep up the great work!We will promptly review your changes and offer feedback. Keep up the excellent work! Kindly remember to check our contributing guidelines


Increase OSLC_TRESHOLD a bit

I know we could shuffle this value ad infinitum and never find a perfect match, but based on some observations when investigating #9 I think increasing it a bit shouldn't do any harm.

LGTM, hopefully, we won't miss any real licenses.


Update documentation for --clean

The code (added in 8.0.1554) that excludes the home directory from
'runtimepath' is specific to --clean. One of the differences from -u
DEFAULTS is already described in this :help, so adding this difference
in, too.
Steps to reproduce:

vim -u DEFAULTS
set runtimepath?
:q
vim --clean
set runtimepath?

Thanks, I'll include it.

Reading it again, I've realised the item I edited is already covered by the other item, earlier in the list, so it can actually be removed entirely. Apologies for the runaround.


Add smoke test project

Adds a simple smoke test project that will get the latest unreleased libraries and attempts to build an app that imports them all. In this way, we can identify incompatibilities before releasing.

So just a general question. Is the idea to now have the pipeline also build the new target "AzureSDKSmokeTest" and look for failures when building calling?

So just a general question. Is the idea to now have the pipeline also build the new target "AzureSDKSmokeTest" and look for failures when building calling?

So just a general question. Is the idea to now have the pipeline also build the new target "AzureSDKSmokeTest" and look for failures when building calling?

The idea right now is that we'll run this before a release and then, when we have a release pipeline, it will be a required gate on proceeding with that pipeline.

So just a general question. Is the idea to now have the pipeline also build the new target "AzureSDKSmokeTest" and look for failures when building calling?

The idea right now is that we'll run this before a release and then, when we have a release pipeline, it will be a required gate on proceeding with that pipeline.

Starting point for release documentation is here: https://github.com/Azure/azure-sdk-for-ios/wiki/Release-Process

Starting point for release documentation is here: https://github.com/Azure/azure-sdk-for-ios/wiki/Release-Process

/azp run

/azp run


Specify client protocol in config

When running behind a reverse proxy, SSL may be available, so HTTPS URLs should be able to be generated automatically.

tegola sniffs for TLS on the capabilities endpoint. Are you saying that you have TLS between the proxy and the client, but not tegola and the proxy and therefore need a way to "force" https urls in the capabilities endpoint?

Correct. X-Forwarded-Proto is one way (implemented in #135), but an alternate method would be useful if that header isn't being passed.


Session wide preload script

We need this implementation to accomplish preloading the script in .
Wait for upstream: https://github.com/electron/electron/issues/2605

Looks like we are gonna have this implemented. 😄


navbar now stacks on mobile

navbar now stacks on mobile

Coverage remained the same at 54.098% when pulling d329245051a6cf2e6a9bc3c86f0365d3eab2de79 on menuToMobileStackable into 1e2ab0355768b2c78eb58a1093a14b1fef385253 on master.


travis: test on Windows

Fixes: https://github.com/nodejs/node-core-utils/issues/313

Let's see if it works

I think adding these to .gitattributes should fix the Windows issue?
# auto detect text files
* text=auto

# we don't have actual binary files in this repo
*.* text eol=lf

I changed the matrix and created .gitattributes: https://github.com/nodejs/node-core-utils/pull/314/checks

I cannot reproduce on my Windows machine

Rebased. @joyeecheung do you think we still need the .gitattributes?

There seems to still be issues with CRLF

Can you rebase and force push to see if Travis can pick the other fix up?


Most components don't support theme/dark mode theme color changes

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
Even though the current release is only in alpha, the dark mode/theming support is quite suboptimal and it hurts much more than how much it solves.
Defining default theme colors by default should flow through to dark mode.
Components don't respect theme colors correctly when switching to dark mode. Cards, for example, don't use the theme's CSS variables, they use the color's SCSS variables directly, thus the colors defined in _variables-dark don't even matter. This prevents users from defining a dark mode alternative theme, and further, it prevents users from defining additional themes altogether.
The above, for example, can be attributed to the following compiled CSS:
.text-bg-primary {
    color: #fff!important;
    background-color: RGBA(13,110,253,var(--bs-bg-opacity,1))!important;
}

This comes from _color-bg.scss. These rules should always refer to CSS variables instead of the raw SCSS values so they can be overridden at runtime.
The problem is non-fully systematic and inconsistent. bg-#{$color} and text-#{$color} work correctly. text-bg-#{$color} works incorrectly. link-#{$color} is correct, although link-#{$color}:hover and link-#{$color}:active are incorrect.
Reduced test cases
The issue is visible on the Bootstrap docs page.
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Microsoft Edge
What version of Bootstrap are you using?
5.3.0-alpha1

I found the following problems that don't respect the current theme:

Emphasis, subtle and border-subtle are derived from the theme colors themselves. Defining them as SCSS variables only causes problems downstream. Should be calculated and set in CSS vars only.
"Light" and "Dark" don't really make sense in light, dark or whatever themes at all, especially seeing how they can be considered their own themes. I suggest these to be removed altogether from the theme colors.
"Primary" is used pretty consistently as an accent and an active color. Secondary, on the other hand, is used almost interchangeably with shades of gray. "Secondary", thus, shouldn't be available to configure either.

Wherever $primary is referenced for example in CSS rules, it won't respect the current theme. Some very serious culprits here are $component-active-bg: $primary !default; and $focus-ring-color: rgba($primary, $focus-ring-opacity) !default;. These should refer to var(--#{prefix}primary) instead, but it'll cause some additional problems, such as $input-focus-border-color: tint-color($component-active-bg, 50%) !default; - this expects a value at build time to function correctly.

Different, but related I think: setting something like $headings-color doesn't work as expected.
Imagine setting $body-color to, say, $gray-700, and $headings-color to $gray-900. You end up with the wrong heading color in, for example, active list group items:

Card titles seems to escape the problem, but only because a) .card-title has higher specificity than h1, etc., and b) the .card-title color is "wrong" — i.e., the same as $body-color rather than darker:

Setting $card-title-color to $headings-color fixes that, but breaks other things:

If I'm doing things the wrong way, obviously I don't know what the right way is. :-)
This isn't a theming issue per se; all of these examples fall into the "light" theme. But. But it seems like some concept is missing. I can't define one universal headings color when that color will be used on various backgrounds?
It seems like anywhere you can define a color — at least, a text color — you need to be able to define two: one for use on "light" backgrounds, and one for use on "dark" backgrounds. The contrast ratio helper would then choose which one to use. Or something like that.

please sir assign this issue me i want to solve this issue

@sanjaygupta972004 We don't assign issues in this repository. You can directly create a PR if you can fix this issue.

ok sir

"Light" and "Dark" don't really make sense in light, dark or whatever themes at all, especially seeing how they can be considered their own themes. I suggest these to be removed altogether from the theme colors.

I think I'd prefer them to just swap over. If you design/layout in light mode and use .bg-dark. It'll switch to the .bg-light color in dark mode.

"Light" and "Dark" don't really make sense in light, dark or whatever themes at all, especially seeing how they can be considered their own themes. I suggest these to be removed altogether from the theme colors.

I think I'd prefer them to just swap over. If you design/layout in light mode and use .bg-dark. It'll switch to the .bg-light color in dark mode.

Dark and light should have the names changed but still exist. Generally speaking light is a slightly different color from the background color and dark is higher contrast from the background color. I'd really like to see them keep some color like those two but name them something more appropriate.


ETA is 4 minutes for over 5 hours

Environment info

Version: 2.8.2-dc9d106
Deployment: **AZURE **
Customer: demo

Actual behavior

stopped most of the node, but left enough nodes to handle the data. ETA is 4 minutes for over 5 hours.
Even if there are no available nodes, we should indicate it instead of such ETA.
I checked each one of the nodes, all seems healthy.

Might be part of Jacky's next task, so low priority for now
Expected behavior

Steps to reproduce

Screenshots or Logs or other output that would be helpful

UI no longer supported


Get the test suite working inside the rustc test suite

I had to weave some env vars over from rustc, but it works now both within rustc and here.

What exactly is it that used to not work and works with this? I don't understand what "inside the rustc test suite" means.

Ah, I see. This is for https://github.com/rust-lang/rust/pull/43628. Looks good!

Of course, eventually, we will want to run miri on the entire rustc testsuite itself, not just on in its rather small testsuite. :)

Of course, eventually, we will want to run miri on the entire rustc testsuite itself, not just on in its rather small testsuite. :)

for that we need a way to mark tests as "miri will always fail on this"


Will there be newer versions of chrome-mobile and android images?

Hello,
I see that the latest version chrome-mobile:79.0 uses android 9 and android version goes up to 10.
I was wondering if there will be newer version updates!
Thank you.

@shj941013 will do soon.


How skywalking can trace nginx ， h5 ,andorid

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?

Bug

Which version of SkyWalking, OS and JRE?

Which company or project?

What happen?
If possible, provide a way for reproducing the error. e.g. demo application, component version.

Requirement or improvement

Please describe about your requirements or improvement suggestions.

Simple answer, currently no. Similar discussions happen on mail list<EMAIL_ADDRESS>


Minor refactoring in wysiweb

I have just forked the repo and I am familiarizing myself with the code. As part of that I have been refactoring as I go. One question I had regarding the 'wysiweb' code was about the special case of the '.' and '_' characters. Are these being used to indicate hidden files/directories? I am familiar with the use of  the period on linux but not the underscore. If they are being used for this I am intending to make that a named class variable and some documentation to indicate that but I wanted to check first.

I don't normally maintain this repo, but I do work here at the Center and couldn't help but notice that your PR hasn't been addressed. I sincerely apologize for that!
wysiweb actually exists as a separate project now; perhaps your changes would be best applied there?
For what it's worth, after briefly reviewing your changes I see nothing where I disagree with them. You've reduced complexity and increased readability in every instance.

Hi @lyndsysimon, thanks for getting back to me. After this length of time I suspect that the small changes I made are probably not relevant now, so I will discard the PR.


Fix an issue when using the initialSlide option

Without parsing this, the internals of slick.js get confused and no option ends up showing up until you scroll/click.

Can this be merged please ?

Ping @vasyabigi on whether you want to merge this (or if you're still maintaining this library)


can-serve Allow port to auto increment to next un-used port

If a port such as 8080 is already being used, can-serve should auto increment to next un-used port

After some discussion we decided that jumping around ports might be confusing for the end user. We are now just giving a better error message.


ignore otel patch updates

opening this as a possible solution and to discuss if we want to make the matching more greedy, but this implements a suggestion by @walldiss last week to have dependabot be less aggressive with suggesting EVERY patch release for all dependencies, only limiting to major and minor updates as suggestion.
Arguably, we could expand the wildcard to more than *otel* and apply to everything, but maybe we just let it run on otel for a bit and see what the consequences are before considering applying it more broadly.
Also, i think we should review the security alert configuration side of dependabot as a companion to this to ensure we DO get security alerts if a CVE or issue is patched. But that will be separate

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (fae3024) 50.88% compared to head (90e52f2) 50.94%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2988      +/-   ##
==========================================
+ Coverage   50.88%   50.94%   +0.05%
==========================================
  Files         176      176
  Lines       11193    11193
==========================================
+ Hits         5696     5702       +6
+ Misses       4992     4987       -5
+ Partials      505      504       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Add a Play]: Custom Dropdown Component

What's the Play about?
A React Custom Dropdown component with searchable and multi selectable featues
What ReactJS concept will be used to create this play?
Components, hooks
Are you willing to take it up for implementation?
Yes
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@Jisan-mia @priyankarpal What's the update on this issue ? Is anyone working on it ?

hey @TejasShekar
I had worked for this issue created by me
and the pr for this issue  #1169
The pr has automatically been closed for no activity
please, can you review the pr and let me know what I can do

Not sure about the next steps.
@Angryman18 @Amyx000 need help with this issue


ci: Update the latest version when the main branch is updated

Free Text
Update the latest version when the main branch is updated.

https://github.com/suzuki-shunsuke/lock-action/pull/35


add jobs for test-cmd and test-go

Didn't we run these already as part of the existing jobs?

break them out for speed

ack


Team Recruitment efforts

Overview
We need to have a viable recruitment strategy so that we always have a full team working on the project.
Action Items

[ ] Document all of the recruiting platforms, including

[ ] location
[ ] rules

[ ] Document all current recruitment posts on various platforms
[ ] Annotate issue with posts filled
[ ] Annotate issue when making posts to keep history up to date
[ ] Write template language that can be used so that its easy for new pms to know what to post

Resources/Instructions
Places to post
HfLA engineering Community of Practice open roles board
Current posts
Backend engineer

Post on Engineering Community of Practice open roles board
Project Name: Civic Tech Index
Volunteer Opportunity:  Needs someone to continue extending Django + Django Rest Framework site to support React frontend. Skills desired or skills to learn: Django, pytest, AWS, Terraform. Mentoring available.
Duration: Open-ended
Who to communicate your interest to

Slack channel link: #civic-tech-index
Slack name of person to contact in the channel: Levi or Kevin Phan

Public Website
Development website
Current API
Front End Repository
Back End Repository

I posted the opportunity above in the engineering channel

Posted in engineering channel to recruit for backend developer.


Configurable Middle-click paste in terminal on non-Linux

It would be nice to be able to configure middle-click-paste on Mac and Windows, too. #136633 was rejected for this, but after #3130 is implemented (hopefully soon), this can be revisited by providing an action that can be mapped to middle click in terminal.

Let's track this in https://github.com/microsoft/vscode/issues/3130, note that some work has happened there and it's looking like we'll be able to support your ask in a mousebindings.json file or similar.


inputAccessoryView space between keyboard

This is a space between keyboard and toolbar in iOS 16.1
CocoaTextField(text: $text)
            .inputAccessoryView(
                HStack {
                    Spacer()
                    Button("Done") {

                    }
                   .padding(.trailing, 16)
                }
                .frame(height: 48)
            )

The same issue is in https://github.com/SwiftUIX/SwiftUIX/issues/351

@hapton this should now be fixed. If my work with SwiftUIX helps you, please consider funding my OSS work on Patreon.

@vmanot  Fixed on the latest dev branch, please release the tag as soon as possible.Thanks.

@hapton released 0.1.5.


What advantage does this have over the underlying library?

Hi there!
When looking at this library, I don't think I understand what it provides over the underlying library - can you please elaborate?
Especially if I want to use kemal-redis, and the underlying lib had progressed beyond 1.2.1, so there ought to be some version relaxing there.
Thanks!

Actually, not much! I've just made these helpers to easily integrate redis as a middleware

Thanks - I don't know if I truly understand the differentiation - and I've opened up PR #2 to relax the dependency constraints.


[CD] Add job that runs a localnet with assertor on merge

If it fails, we should send an alert to slack.
Should we send something if it passes too?

As discussed async, this task will be tackled after #952 and #953. The idea is to have a comprehensive set of checks that would run only on merging to main, this test will take more time and will need to inform the runs status (specially on errors) through slack.


ImportError: DLL load failed: The specified module could not be found. Failed to load the native TensorFlow runtime.

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution: Windows 10
Mobile device : none
TensorFlow installed from): through Pycharm package installer
TensorFlow version: 2.1.0
Python version: 3.6
Installed using: pip

I cant import any tensorflow or keras libraries. I get this error.
I tried importing these:
import tensorflow as tf
from keras.layers import Dense, Activation, Dropout
from keras.models import Sequential
from keras.utils import to_categorical
Traceback (most recent call last):
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\tensorflow_core\python\pywrap_tensorflow.py", line 58, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Program Files\JetBrains\PyCharm Community Edition 2019.3.3\plugins\python-ce\helpers\pydev_pydev_bundle\pydev_import_hook.py", line 21, in do_import
module = self._system_import(name, *args, **kwargs)
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\tensorflow_core\python\pywrap_tensorflow_internal.py", line 28, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\tensorflow_core\python\pywrap_tensorflow_internal.py", line 24, in swig_import_helper
_mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
File "C:\Users\uvide\Anaconda3\lib\imp.py", line 243, in load_module
return load_dynamic(name, filename, file)
File "C:\Users\uvide\Anaconda3\lib\imp.py", line 343, in load_dynamic
return _load(spec)
ImportError: DLL load failed: The specified module could not be found.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "C:\Program Files\JetBrains\PyCharm Community Edition 2019.3.3\plugins\python-ce\helpers\pydev_pydev_bundle\pydev_umd.py", line 197, in runfile
pydev_imports.execfile(filename, global_vars, local_vars)  # execute the script
File "C:\Program Files\JetBrains\PyCharm Community Edition 2019.3.3\plugins\python-ce\helpers\pydev_pydev_imps_pydev_execfile.py", line 18, in execfile
exec(compile(contents+"\n", file, 'exec'), glob, loc)
File "C:/Users/uvide/PycharmProjects/demo/test.py", line 4, in
from Potentiostat import Pot
File "C:\Program Files\JetBrains\PyCharm Community Edition 2019.3.3\plugins\python-ce\helpers\pydev_pydev_bundle\pydev_import_hook.py", line 21, in do_import
module = self._system_import(name, *args, **kwargs)
File "C:\Users\uvide\PycharmProjects\demo\Potentiostat.py", line 5, in
from keras.layers import Dense, Activation, Dropout
File "C:\Program Files\JetBrains\PyCharm Community Edition 2019.3.3\plugins\python-ce\helpers\pydev_pydev_bundle\pydev_import_hook.py", line 21, in do_import
module = self.system_import(name, *args, **kwargs)
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\keras_init.py", line 3, in
from . import utils
File "C:\Program Files\JetBrains\PyCharm Community Edition 2019.3.3\plugins\python-ce\helpers\pydev_pydev_bundle\pydev_import_hook.py", line 21, in do_import
module = self.system_import(name, *args, **kwargs)
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\keras\utils_init.py", line 6, in
from . import conv_utils
File "C:\Program Files\JetBrains\PyCharm Community Edition 2019.3.3\plugins\python-ce\helpers\pydev_pydev_bundle\pydev_import_hook.py", line 21, in do_import
module = self._system_import(name, *args, **kwargs)
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\keras\utils\conv_utils.py", line 9, in
from .. import backend as K
File "C:\Program Files\JetBrains\PyCharm Community Edition 2019.3.3\plugins\python-ce\helpers\pydev_pydev_bundle\pydev_import_hook.py", line 21, in do_import
module = self.system_import(name, *args, **kwargs)
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\keras\backend_init.py", line 1, in
from .load_backend import epsilon
File "C:\Program Files\JetBrains\PyCharm Community Edition 2019.3.3\plugins\python-ce\helpers\pydev_pydev_bundle\pydev_import_hook.py", line 21, in do_import
module = self._system_import(name, *args, **kwargs)
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\keras\backend\load_backend.py", line 90, in
from .tensorflow_backend import *
File "C:\Program Files\JetBrains\PyCharm Community Edition 2019.3.3\plugins\python-ce\helpers\pydev_pydev_bundle\pydev_import_hook.py", line 21, in do_import
module = self._system_import(name, *args, **kwargs)
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\keras\backend\tensorflow_backend.py", line 5, in
import tensorflow as tf
File "C:\Program Files\JetBrains\PyCharm Community Edition 2019.3.3\plugins\python-ce\helpers\pydev_pydev_bundle\pydev_import_hook.py", line 21, in do_import
module = self.system_import(name, *args, **kwargs)
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\tensorflow_init.py", line 101, in
from tensorflow_core import *
File "C:\Program Files\JetBrains\PyCharm Community Edition 2019.3.3\plugins\python-ce\helpers\pydev_pydev_bundle\pydev_import_hook.py", line 21, in do_import
module = self.system_import(name, *args, **kwargs)
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\tensorflow_core_init.py", line 40, in
from tensorflow.python.tools import module_util as _module_util
File "C:\Program Files\JetBrains\PyCharm Community Edition 2019.3.3\plugins\python-ce\helpers\pydev_pydev_bundle\pydev_import_hook.py", line 21, in do_import
module = self.system_import(name, *args, **kwargs)
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\tensorflow_init.py", line 50, in getattr
module = self.load()
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\tensorflow_init.py", line 44, in _load
module = importlib.import_module(self.name)
File "C:\Users\uvide\Anaconda3\lib\importlib_init.py", line 126, in import_module
return _bootstrap.gcd_import(name[level:], package, level)
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\tensorflow_core\python_init.py", line 49, in
from tensorflow.python import pywrap_tensorflow
File "C:\Program Files\JetBrains\PyCharm Community Edition 2019.3.3\plugins\python-ce\helpers\pydev_pydev_bundle\pydev_import_hook.py", line 21, in do_import
module = self._system_import(name, *args, **kwargs)
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\tensorflow_core\python\pywrap_tensorflow.py", line 74, in
raise ImportError(msg)
ImportError: Traceback (most recent call last):
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\tensorflow_core\python\pywrap_tensorflow.py", line 58, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Program Files\JetBrains\PyCharm Community Edition 2019.3.3\plugins\python-ce\helpers\pydev_pydev_bundle\pydev_import_hook.py", line 21, in do_import
module = self._system_import(name, *args, **kwargs)
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\tensorflow_core\python\pywrap_tensorflow_internal.py", line 28, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Users\uvide\PycharmProjects\demo\venv\lib\site-packages\tensorflow_core\python\pywrap_tensorflow_internal.py", line 24, in swig_import_helper
_mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
File "C:\Users\uvide\Anaconda3\lib\imp.py", line 243, in load_module
return load_dynamic(name, filename, file)
File "C:\Users\uvide\Anaconda3\lib\imp.py", line 343, in load_dynamic
return _load(spec)
ImportError: DLL load failed: The specified module could not be found.
Failed to load the native TensorFlow runtime.

@uvinidesilva
What is make/model of your cpu?
I suspect your cpu model does not support AVX instructions sets.See hardware requirements
Make sure to download the latest microsoft visual c++ redistributable from here.
.Also, please follow the instructions from to install from pip Tensorflow website.
Please, check Your CPU/Python is on 32 bits?Please, refer #36167 and see if it helps you. Thanks!

@ravikyram I had the same issue and fixed it by downloading the microsoft visual c++ redistributable package. Shouldn't this information be present in the install instructions on the official website?

Closing as duplicate.
https://github.com/tensorflow/tensorflow/issues/36167#issuecomment-577886156
#36167 #36151 #36138 #36054 #36045 #36020 #36003 #35988 #35903 #35880 #35865 #35805 #35789 #35773 #35772 #35767 #35766 #35749 #35721 #35618 #35204


Improve dll export/import definition

Follow-up to #178

Update API naming for clarity and consistency by renaming UNSHIELD_DLLEXPORT to UNSHIELD_API. This change enhances naming clarity, making the purpose of the macro more intuitive and aligned with common naming conventions in cross- platform libraries.

Optimize performance with export/import directives. By differentiating between __declspec(dllexport) and __declspec(dllimport) in Windows builds, this adjustment improves the performance of dynamic linking, ensuring efficient symbol resolution and potentially reducing binary size.

Enhance flexibility in CMake configuration. Applying PRIVATE and PUBLIC specifiers in target_compile_definitions ensures that UNSHIELD_EXPORT is used internally within the library, while UNSHIELD_DYNAMIC_LIBRARY is propagated to clients of the library. This distinction prevents macro leaks and provides users with the appropriate definitions based on their linking method, offering greater flexibility and ease of integration in diverse build configurations.

Substitute _MSC_VER with _WIN32 to broaden compatibility, ensuring that the library correctly handles DLL exports and imports across various Windows compilers, not just MSVC, thereby facilitating cross-platform builds. Indeed, __declspec(dllexport) and __declspec(dllimport) is a Windows convention instead of a Visual Studio one.

Would like a review/test from @elasota in case I missed or broke something.

Mad CMake skills @bwrsandman !

Seems okay to me


sizeFull breaks flex containers

Hi! I'm using this with the Grid component and running into an issue. When I use the Grid--withGutter modifier, I have to add u-sizeFull to the container or else it overflows, which is normally fine, but since switching to the flexbox-based grid, u-sizeFull forcibly sets display to block.
Am I doing something wrong or is there a workaround?

What is the issue you're trying to resolve by having sizeFull on the Grid container?

given the following code:

    hello

    world

I am left with a Grid that is causing the page to scroll horizontally. adding style="width: 100%;" to the Grid corrects this problem. Is that clear?

Hmm, are you sure nothing else is effecting the grid? I modified the Grid tests in devtools to simulate and it seems fine:

content

content

If you remove the padding on the .Test fixture, you will see the overflow:

Looking okay here, with minimal styles - http://codepen.io/simonsmith/full/LGEBqO/
What browser are you using?

same issue - firefox aurora.

Looking okay here, with minimal styles - http://codepen.io/simonsmith/full/LGEBqO/
What browser are you using?
I am able to reproduce the issue. The fixture-Box is overflowing (see the right edge of of Grid-cell)

Okay, so the tests may need a tweak as those elements don't need width: 100% on them. Presuming you don't set that on your content I'm still not sure what the issue is. Tweaked example from before, but with background color http://codepen.io/simonsmith/pen/LGEBqO
I'm also using the Grid on my site with no visible overflow. I might be missing something though, so do you have a test example that reproduces your issue @VinSpee?

Busy week - I will get you a minimal codepen example first thing tomorrow.
Sent from my iPhone

On Dec 8, 2015, at 15:43, Simon Smith<EMAIL_ADDRESS>wrote:
Okay, so the tests may need a tweak as those elements don't need width: 100% on them. Presuming you don't set that on your content I'm still not sure what the issue is. Tweaked example from before, but with background color http://codepen.io/simonsmith/pen/LGEBqO
I'm also using the Grid on my site with no visible overflow. I might be missing something though, so do you have a test example that reproduces your issue @VinSpee?
—
Reply to this email directly or view it on GitHub.

@simonsmith Here's a fork of your pen. It seems that having margin: 0 on body is what's causing the issue. Any ideas?

maybe it's related to Grid--withGutters?

I think this is expected behaviour.
Using Grid--withGutter on a full width element is always going to exceed it's bounds based on the fact it using negative margins. Typically you'd always have a Container element of some description that had appropriate margin or padding each side. Most grid systems require this (bootstrap springs to mind).
It's worth noting that the same issue happens on the 2.x version of the Grid as well, so this doesn't seem related to Flex.
What's your use case that is causing this issue?


Azure VNET Max IP

Azure ARM VNET Max IP is now ~16000.  You mention multiple times that it is ~4000.  Still true for Classic VNETs, but not ARM.  https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits#networking-limits

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

ID: 22ad4873-c73d-4b90-2063-927a1060d2a2
Version Independent ID: 8e6643ad-7333-a786-8712-3d17291e12a7
Content: Network configuration in Azure Kubernetes Service (AKS)
Content Source: articles/aks/networking-overview.md
Service: container-service
Product: unspecified
GitHub Login: @mmacy
Microsoft Alias: marsma

@markgar I am still seeing it at 4096 in the subscription quota and limits doc
https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits#networking-limits
@mmacy are you able to confirm this new limit? I can update both docs if that is the case.

I believe this is an AKS-specific limit, but adding @slack and @aanandr for confirmation or correction.

The VNet limit has indeed gone up to 16k but need to find out if AKS has any checks to retrict to 4096. I am checking.

@aanandr any update on this?

Hi - I checked with the AKS team and learnt that there arent any checks to restrict the no. of IPs to 4096. So you should be able to use the entire range of 16K. However, a few things to keep in mind

16K is default, so new VNets will automatically get it. Existing ones should also get it but customers whose quote was bumped to 8K will have to move to new default.
The max pods you can have in a node is 256. So please keep this in mind when designing the cluster.
As you probably know, the pods/node and nodes per cluster are configurable through templates only, today.

I will be updating the documentation to reflect the 16K limit.

thanks @aanandr !

Hey @MicahMcKittrick-MSFT, this was fixed along with some other items in azure-docs-pr 46699--this issue can be closed. Thanks! -MM
#please-close


Add new file tests to OdkWebserverServiceTest

cc @wbrunette @Lamouresparus

Instead of using "File" class use the URI style

@permission-error let's chat about this PR during your meeting

While your refactor of code improves the code, you still need to switch to the URI format


Can't log in!

Hi, trying to use codetime but when I try to sign up with GitHub I get this error:
{"code":-1,"message":"Error 1290: The MySQL server is running with the LOCK_WRITE_GROWTH option so it cannot execute this statement"}

We appreciate your support and would like to inform you that our service has now been fully restored to normal. We acknowledge that we may not have performed up to our best in the past, but moving forward, we will make every effort to ensure the stability of our service.


Large parquet metadata swamps small workers

I was working with @birdsarah on a problem she was having with parquet where saving to parquet caused her workers to die.  The issue seemed to be that the metadata results of each write_parquet task were decently large (she had 2500 columns) and she had many partitions (10k) and so accumulating these in memory was causing issues (her workers only had a couple gigs of memory).  We eventually found two short-term solutions to this:

Use pyarrow because it doesn't currently handle writing metadata
Use Xarray because the metadata is shared and handled in only one spot

I'd like to record this issue though.  I think that as we add metadata support to PyArrow we should be cognizant of these costs.  In the future I'd like to see ...

metadata that was smallish in memory
the option to intermediately store only the data that changes between partitions (I'm not sure if there is a substantial difference here though)
maintain the ability to not handle metadata writes

cc @wesm @xhochy

The main steps to be taken here is to better expose the C++ classes in https://github.com/apache/arrow/blob/master/cpp/src/parquet/metadata.h in Python and adding the ability to write a Parquet file just from this classes without any data again.

@xhochy Do you mean the Builder classes such as ColumnChunkMetaDataBuilder, RowGroupMetaDataBuilder, FileMetaDataBuilder need to be exposed to Python? I'd be happy to take any pointers on what is needed for resolving ARROW-1983.

@pearu Yes. In the end to create the _metadata we would need to collect the RowGroupMetaData instances from all files, pickle them, send them to a single worker and then create out of all of them a single FileMetaData that is stored as part of an empty Parquet file named _metadata.

This issue is still relevant, but partly covered by the conversation in https://issues.apache.org/jira/browse/ARROW-1983
Consider, though, that it may well still be useful to have an option not to make column statistics, partly to speed up writing and partly to decrease the metadata size. Fastparquet has this option in https://github.com/dask/fastparquet/pull/259 (which is py3 only, and so not merged), but it is not surfaced.

@jorisvandenbossche @enpiar to make you aware of this issue


Overlay should be on top of body elements except the sidebar.

I'm trying to override .bm-overlay by add extra z-index to it. I'm not able to add my extra styling. I guess this is probably because .bm-overlay will be added when the menu is open. Is there anyway to add my style to it?

Simple I just want to display logo behind overlay. Whenever it is present.

Note that if you are styling within a scoped style tag you are not going to achieve what you want.
In your component (header.vue I suppose ) you could add another <style> block besides <style scoped> block with the vue-burger-menu classes.

Well, that works I can override the css class, but the issue is, overlay is adding to the body tag because of which elements or on top of it (which should be the opposite). Overlay should be on top of other elements except the sidebar. Sorry for miss guiding I have updated the issue.


Update entity health on mount

missed 1.20 packet fixes

Addresses #372

Heh, this just reminded me I had a stash change to fix the same thing. I've attached the patch file (in a zip because Github didn't let me upload the raw patch file). I have a slightly different tactic of leaning on NMS as much as possible, instead of creating a new ProtocolLib packet.
MountHealthBug.patch.zip

@MrJeremyFisher could you fix the merge conflicts here please? Then we can get this merged

Resolved, I think.


Update ABIs

Update the protocol generated ABIs to reflect these changes.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 72.15%. Comparing base (2ac27f5) to head (6a2ea5e).

Additional details and impacted files
@@           Coverage Diff           @@
##             dev     #567    +/-   ##
=======================================
  Coverage       ?   72.15%
=======================================
  Files          0       19    +19
  Lines          0      158   +158
  Branches       0        4     +4
=======================================
+ Hits           0      114   +114
- Misses         0       44    +44

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Tobin gh2374 mock query

Updated mock icd to handle extension feature and properties queries down the GPDP2 and GPDF2 paths.

This all seems copacetic, once the status board is all green.

The fails are because DevSim doesn't yet report the extended properties or features.
DevSim needs to have similar updates made so that it can report extension properties and features that are read in from json. I started to do it myself but it wasn't immediately obvious how to read what I need from the JSON so created VulkanTools GH389 and hoping @mikew-lunarg can run with what I started.

Extension support is currently being added to DevSim, so this is good timing for the feature request.

Great catch, @jzulauf-lunarg. The exclusion was un-intentional and I've pushed an update to add the missing extension.

@tobine, this repository will close for write access on Sunday, 5/13/2018.  If it is pushed before that time it will be present in the follow-on Vulkan-ValidationLayers repository on Monday, otherwise a new PR will be required in the new repo.


PDCT-716/Make-library-for-alembic-db-schema

Description
Please include:

a summary of the changes
links to any related issue/ticket
any additional relevant motivation and context
details of any dependency updates that are required for this change

Type of change
Please select the option(s) below that are most relevant:

[ ] Bug fix
[ ] New feature
[ ] Breaking change

How Has This Been Tested?
Please describe the tests that you added to verify your changes.
Reviewer Checklist

[ ] The PR represents a single feature (small driveby fixes are also ok)
[ ] The PR includes tests that are sufficient for the level of risk
[ ] The code is sufficiently commented, particularly in hard-to-understand areas
[ ] Any required documentation updates have been made
[ ] Any TODOs added are captured in future tickets
[ ] No FIXMEs remain

Hey @asacristani, is this a draft or ready for review? If ready, please could you update the PR description summarising what you've changed/tested?

Create a new branch for too many conflicts


Codegen: avoid enum value clashing with the getter field

Reproducer:
enum Foo {
  field
}

Because field is the backing field in the context of the getter, we need to scope the identifier better.

Thanks for this!


Update dependencies and Ember

📖 Description
It’s been a while since the last time we updated the dependencies! So... sorry for the big diff 😬 I’ll try and explain everything that’s changed so that you can review things more efficiently:

Update dependencies in package.json
Format files with new Prettier version. I also changed the config to avoid changing to much things and keep our defaults
Update ember-cli-typescript and TypeScript itself, some types and configs had to be changed to make this work
Update the graphQL stack: apollo-client and friends become @apollo/client
Update node.js and npm versions
I sneaked a little code change: rename session/fetcher to session to get rid of the pattern of splitting services by action since we don’t do it anymore!

🦀 Requesting reviewers for this pull request:

@remi (contributor with 0 commits in the last 90 days and 69 commits overall)


feat: Explicit loading of Metadata Schema

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

#1014  👈
#1013
main

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

Join @Cobalt0s and the rest of your teammates on  Graphite


[Bug report] fileset commet meet garbled data

Version
main branch
Describe what's wrong
Create or update fileset comment，when inputting Chinese, the data taken out is garbled.
example:
input: 这是fileset中文描述
output: ??fileset????
Error message and/or stacktrace
no
How to reproduce
create fileset:

get fileset:

data in mysql:

Additional context
No response

@hanwxx can you please help to fix this issue?

I tracked some logs, and it seems that when it was requesting the server, garbled code had appeared.

So seems like some string codec issue happens between client and server.

I have found the source problem, will open a PR to fix this later.


Modal Form closes when pressing enter key on Search Box

Hi,
When trying to input some text in search box of the bootgrid and press enter. The entire modal form closes.
How can enter key be disabled when searching.
Thanks,
/gmr

Got it!
$("input:text").keypress(function(event) {
if (event.keyCode == 13) {
event.preventDefault();
return false;
}
});


compile option/static loading

I can understand if this is beyond the scope of antibody/not the design goal of antibody but...
In an effort to make antibody even faster than it already is, what do you think about having an option to "compile"/statically load your current bundles?
For example, if you had a plugins.txt that looked like:
caarlos0/jvm
djui/alias-tips
caarlos0/zsh-mkc
zsh-users/zsh-completions
caarlos0/zsh-open-github-pr
zsh-users/zsh-syntax-highlighting
zsh-users/zsh-history-substring-search

and then had antibody bundle < plugins.txt in your ~/.zshrc; this "compile" option would simply create a file with all the full paths to source and would look something like:
source /full/path/to/jvm.plugin.zsh
source /full/path/to/jvm.sh
source /full/path/to/alias-tips.plugin.zsh
source /full/path/to/mkc.plugin.zsh
...

and then in antibody.zsh it would first check for the presence of this file and if it was found it would just do source name_of_this_file.zsh instead of doing what it does now (i.e. running the go binary and sourcing the necessary files)
However, something that would have to be figured out would be if the user has a ~/.zshrc like:
antibody bundle zsh-users/zsh-syntax-highlighting
antibody bundle zsh-users/zsh-history-substring-search
antibody bundle foo
antibody bundle bar

instead of the faster way of doing antibody bundle < plugins.txt it would be tricky to know when to do source name_of_this_file.zsh, because you wouldn't want to do source name_of_this_file.zsh for every bundle <some repo> in ~/.zshrc... That is, unless antibody compile was a completely separate command from antibody bundle.
or am I missing something and this would not actually improve the speed of antibody? (not saying that antibody is slow by any means though...)
I guess my motive is to make my dotfiles completely modular in the sense that I would use antibody to bundle just about everything in my dotfiles. The only downside to doing this is that antibody would, I imagine, inherently be slower than just directly sourcing the files how I normally do in my dotfiles. (As well as it won't add things to fpath, if I am not mistaken, but that would be a separate issue...)

Hi @mkwmms,
Sorry, but I have no plans of adding this to the project mostly because of the issues you cited above...
Thanks!

I just realized a good way of doing that, it's kind of hacky, but will work just fine ;)

@mkwmms please check the Hacking session of the readme, that should do the trick.
https://github.com/caarlos0/antibody#hacking
Let me know if it doesn't. Thanks!

@caarlos0 clever hack! I like it. :smile:

@mwilliammyers check version v0.9.1. A --static flag was added to the bundle command =)

@caarlos0 will do, thanks!

@mwilliammyers just now I read your previous comment about fish support.. I guess we can do that, yes.
Maybe some --fish global option or something... will require some changes in design... but, yeah, would work 👍

let me know if you still interested =)


Add translation about stub in layout

What kind of changes does this PR include?

Translated content
Changes to the docs site code

Description
Add translation about stub. Please see this issue about why I create this PR

Looks like the getTranslation throws an error when the key is not found in that language:
https://github.com/withastro/docs/blob/main/src/i18n/util.ts#L59-L70
So we might need to add all translations before mergin!
/cc @sarah11918 @Yan-Thomas @delucis

~Looks like the getTranslation throws an error when the key is not found in that language:~
~https://github.com/withastro/docs/blob/main/src/i18n/util.ts#L59-L70~
~So we might need to add all translations before mergin!~
~/cc @sarah11918 @Yan-Thomas @delucis~
My bad, didn't saw the  || translations[fallbackLang][key] x.x LGTM!

Yep, I tested that when there is no translation for that language, it will fall back to English :)

Sorry, I just broke my main branch by mistake. So I force-pushed it to fix it. Everything is the same as when Alynva approved these changes

Hi @imbant, we had a team meeting about this one (and, my apologies, I forgot we'd already a long time ago had a discussion months ago!) and our translators at the time decided that it's better NOT to translate this content. In fact, it was my mistake to mark the stubs as i18n:true in the first place!
Most of our stub pages are really quite small, with little text to translate, so there's not lot of extra benefit from translating them. And then, if we receive an English contribution to make a more full guide, there would be a big difference between the English language page and a not-yet-updated translated page. We think it's better to have those pages fall-back to English rather than have a time where we display a stub for non-English pages when there is actually good content on the English page.
Keeping the stubs untranslated means that they will default to English, and we will only mark them as i18n:true when there is a full guide. That way, this problem never happens.
Thank you for starting these translations, even though we can't use them.  :sweat_smile: We look forward to more contributions from you!  :raised_hands:

Oops, apparently I missed a meeting!
I think we're going to fix the issue a different way, and so we CAN use this!  So I'm going to stay out of this and let @Yan-Thomas finish this off. Reopening at this point, since we think we can use it!

OK. Thanks for the detailed explanation. Just let me know when there is something that I need to change😀


Document routing option.

What does this mean?

@mafintosh there is apparently a way to route commands, so that you can for instance restart an instance running in only one dock instead of restarting all instances. But that's not documented anywhere.

AHH i though you wanted to route based on "documents"


Handle missing run for leading br tag

(Issue #37)
When the HTML to parse begins with a
 tag, an error is thrown because self.run is not defined. This is a simple fix to handle the error.

Can you use this to recreate a real line break?
try:
    self.run.add_break()
except AttributeError: #If
 is the first element parsed, self.run will not be defined
    self.paragraph = self.doc.add_paragraph()
    self.run = self.paragraph.add_run()
    self.run.add_break()

Yes, you could add a line break in that way. However, adding the paragraph itself creates a new line and so you would end up with the appearance of two new lines, I believe.


nested routes keep rerendering

Version
Please replace this sentence with the React Router version that you are using.
^5.0.1
Test Case
https://github.com/sibelius/nested-rerender
https://codesandbox.io/s/github/sibelius/nested-rerender
Steps to reproduce
Go to codesanbox demo, click on Nested Tab A link, then click on Nested Tab B, and you will see that both Main and Nested components will rerender, but they should not.
You can also clone the github repo, and run yarn start
Expected Behavior
It should not rerender "parent" components of nested routes
Actual Behavior
It is rerender all components that match the nested path
I think this is caused because <Route> subscribe to ReactRouter context, keep all Route rerendering
We need something similar to react-redux approach to only rerender components that needs to be rerender
My idea is to avoid rerender is to only rerender Route when match state change
I've tried something like this:
const hasMatch = (props) => {
  const location = props.location || location;
  const match = props.computedMatch
    ? props.computedMatch // <Switch> already computed the match for us
    : props.path
    ? matchPath(location.pathname, props)
    : false;

  return match;
};

export default memo(Route, (
  prevProps, nextProps
) => {
  const prevMatch = hasMatch(prevProps);
  const nextMatch = hasMatch(nextProps);

  console.log('memoRoute: ', prevMatch, nextMatch, nextProps.location, nextProps.path);
  return prevMatch === nextMatch;
});

It is breaking because I can't access context on memo

You sure this is new in 5.0? I get the same console output when I change the version to 4.3.1 in your sandbox.
I also don't think the additional rerenders qualify as a bug. It should not cause any issues whatsoever. Even performance impact should be negligible, since route changes don't happen very frequently.

@StringEpsilon Yes and no. Performance is the one side, but think about related actions on mounting. Maybe there are AJAX requests or similar, that take some time, and that get started on every path change.

@MeiKatz They should not remount, just rerender. React pretty much takes care of that if you have class component or memoized functional component.

This is causing a delay of 2/3 seconds in our app, when moving from one route to another
this codesanbox solves the problem using shouldComponentUpdate: https://codesandbox.io/s/nested-rerender-cv7g9?fontsize=14
import React, { Component } from "react";
import equal from "fast-deep-equal";

const propsWithoutLocation = props => {
  const { location, ...rest } = props;
  return rest;
};

export default WrappedComponent => {
  class HOC extends Component {
    shouldComponentUpdate(nextProps) {
      if (
        equal(propsWithoutLocation(nextProps), propsWithoutLocation(this.props))
      ) {
        return false;
      }
      return true;
    }
    render() {
      return <WrappedComponent {...this.props} />;
    }
  }
  return HOC;
};

This is the expected behavior in a React application; the Router is informed of the navigation and schedules an update. Barring update blockers (sCU, memo) or React's internal optimizations (skipping re-rendering the same element), the entire tree will be re-built.
Have you tried using the React Dev Tools profiler to see which components take so long during the navigation? A delay of 0.6 seconds seems astronomical; I can't picture a situation where this delay is caused by React Router's components.

@StringEpsilon My mistake. I read "remount" instead of "rerender".

Correct, this isn't a React Router issue. You have performance issues elsewhere if it's taking hundreds of milliseconds to render your component. Unfortunately, that's not something we can assist with.


Added Rod Cutting [Python]

Fixes #210
By submitting this pull request I confirm I've read and complied with the below declarations.

[x] I have read the Contribution guidelines and I am confident that my PR reflects them.
[x] I have followed the coding guidelines for this project.
[x] My code follows the skeleton code structure.
[x] This pull request has a descriptive title. For example, Added {Algorithm/DS name} [{Language}], not Update README.md or Added new code.
[x] This pull request will be closed if I fail to update it even once in a continuous time span of 7 days.

@aashutoshrathi Please check this code with PEP8Bear and PyLintBear.

Linter's first message says it doesn't comply with PEP8 while it does.
and not able to understand last message @mohitkyadav

Actually, it does comply with PEP8, but the code you are pasting doesn't have a newline at the end.
The last message is about variable namen, change it to  size or number.

@mohitkyadav @aashutoshrathi Should we have PyLintBear in .coafile ?

@aviaryan I think that'll be good to have PyLintBear, it suggests about argument names and Docstring.

@aviaryan  Yes, I think we should. Should I add it with HaskellLintBear in same PR ?

@mohitkyadav one serious doubt, I know Linter is recommending to add module docstring , but since both function have their docstring and have all information, Is there need of Module Docstring ? If Yes, what should I add in it?

@aashutoshrathi If you wish to make a python program to test all algorithms in this repository, you use rod_cutting.py as a module to import rod_cutting() function in another code, then it's a module with no module docstring.

@mohitkyadav take look now

@singhpratyush take a look

Take a look now @singhpratyush

@singhpratyush Sir, Take a look


How to benchmark TFLite object detection model

It seems that only classification models can be benchmarked. There is no explanation for how to run benchmarking on TFLite object detection models under https://github.com/tensorflow/tensorflow/tree/master/tensorflow/lite/tools/benchmark. Could anybody point me into the right direction to get the modifications needed to run the TFLite benchmark on my custom TFLite object detection model?
After running:
➜  tensorflow git:(master) adb shell am start -S \
  -n org.tensorflow.lite.benchmark/.BenchmarkModelActivity \
  --es args '"--graph=/data/local/tmp/my_custom_object_detection_float32.tflite \
  --num_threads=4"'

When I check logcat:
➜  tensorflow git:(master) adb logcat | grep "Inference timings in us"

I see:
03-15 14:00:51.294 12836 12836 I tflite  : Inference timings in us: Init: 36618, First inference: 1530248, Warmup (avg): 1.53025e+06, Inference (avg): 1.49712e+06
03-15 14:13:43.409 13393 13393 I tflite  : Inference timings in us: Init: 33412, First inference: 307818, Warmup (avg): 297955, Inference (avg): 333826

Basically, my model inference fails and it falls back onto the classification model
Click to expand!
Issue Type
Support
Have you reproduced the bug with TF nightly?
No
Source
source
Tensorflow Version
2.11.0
Custom Code
No
OS Platform and Distribution
Linux Ubuntu 18.04
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Standalone code to reproduce the issue
The app falls back onto the classification model once the object detection one fails:

03-15 14:00:51.294 12836 12836 I tflite  : Inference timings in us: Init: 36618, First inference: 1530248, Warmup (avg): 1.53025e+06, Inference (avg): 1.49712e+06
03-15 14:13:43.409 13393 13393 I tflite  : Inference timings in us: Init: 33412, First inference: 307818, Warmup (avg): 297955, Inference (avg): 333826

Relevant log output
No response

@mikel-brostrom Thanks for reporting the issue.
The benchmarking tool can be used with any tflite model. The example of Performance benchmark numbers for starter model with SSD Mobilenet are generated with the tool described here. Please refer to this section for the same.
The Model Customization section provides the information about choosing the choosing the model to customize and fine tuning the models on custom data.
Thanks

Is there any tutorial on how to convert standard object detector output shape (bs, N, 5 + nr of classe) to what basically all the TFLite tools in this repo expects?

Hi @mikel-brostrom
The TFLite provides a way to use custom models and benchmark them.
Please check the Model Customization and also a way of TF2 object detection models to convert into TF Lite here and let us know if it helps.
Feel free to close the issue if it is resolved.
Thanks.

Please check the Model Customization and also a way of TF2 object detection models to convert into TF Lite here and let us know if it helps.

Thanks. This was really helpful @pjpratik. I think it is unclear whether the App support different type of models or not. I would suggest that you add the customization information under https://github.com/tensorflow/tensorflow/tree/master/tensorflow/lite/tools/benchmark

@mikel-brostrom Glad it helped. Feel free to create a PR if you are interested.
Can you please close the issue if it is resolved?
Thanks.


Move italian translation to submodule

Repo: https://github.com/dlang-tour/italian/pull/1
CC @lodo1995

(I will just merge this before we run into more merge conflicts)


[FEATURE REQUEST] custom cache name

please add option cache name. prevent too many cache generated each commits, which currently github limiting cache sizes and total each repository.

I don't really understand what you're asking. Are you suggesting that a custom cache name could prevent caches growing too large?
There is a lot of information about caching documented here: https://github.com/gradle/gradle-build-action#caching-build-state-between-jobs

I don't really understand what you're asking. Are you suggesting that a custom cache name could prevent caches growing too large?
There is a lot of information about caching documented here: https://github.com/gradle/gradle-build-action#caching-build-state-between-jobs

cache name start with v8 there too many caches with it. wait, ill re-run my previous ci to reproduce the caches. i was cleaned them and disabling gradle-build-action from my workflow yml config

I don't really understand what you're asking. Are you suggesting that a custom cache name could prevent caches growing too large?
There is a lot of information about caching documented here: https://github.com/gradle/gradle-build-action#caching-build-state-between-jobs

add custom cache name to prevent duplicate caches each commit like this

Unfortunately that won't work. Each GitHub Actions cache entry is immutable, so we cannot use a fixed name and update the contents. Instead, each time the entry contents change, it is uploaded with a different name.
BUT, you'll notice that those "duplicated" entries are quite small. We extract common things like dependencies and wrapper zips so that they will be cached once and reused until the underlying contents change.

now iam using actions/cache to solve gradle caching system https://github.com/dimaslanjaka/android-traffic-exchange/blob/a3ba8c74008206a404511b563b4dd482326345e0/.github/workflows/android.yml#L67-L75
then add jvm arg --gradle-user-home to rootProject/.gradle https://github.com/dimaslanjaka/android-traffic-exchange/blob/a3ba8c74008206a404511b563b4dd482326345e0/.github/workflows/android.yml#L107-L118
The result all downloaded jars, build cache, etc in rootProject/.gradle
and the build with cache task working like charm

now iam using actions/cache to solve gradle caching system https://github.com/dimaslanjaka/android-traffic-exchange/blob/a3ba8c74008206a404511b563b4dd482326345e0/.github/workflows/android.yml#L57-L75

You are using a fixed cache key. From my understanding the cache entry for this key will be written ONCE ONLY and will never be updated. So over time this cache entry will be become more and more out of date, and less useful.
From the cache documentation:

You cannot change the contents of an existing cache. Instead, you can create a new cache with a new key.

now iam using actions/cache to solve gradle caching system https://github.com/dimaslanjaka/android-traffic-exchange/blob/a3ba8c74008206a404511b563b4dd482326345e0/.github/workflows/android.yml#L57-L75

You are using a fixed cache key. From my understanding the cache entry for this key will be written ONCE ONLY and will never be updated. So over time this cache entry will be become more and more out of date, and less useful.
From the cache documentation:

You cannot change the contents of an existing cache. Instead, you can create a new cache with a new key.

yeah but not created new caches every push. it will make my github account experience limited github actions because the total cache exceeds the 10GB limit.


Default OVA VMs firmware to EFI

When no firmware is provided by the OVF of the imported OVA, default the firmware to EFI.

@liranr23 please backport


Update architecture.rst

fixed typo
-_-
Also wondering about real-time vs real time (both appear here)

Good point about real-time vs. real time. I've done some Googling and either one is acceptable so it's better to have consistency and in that respect our docs seem to lean more toward real-time.
I suggest using real-time. @lieut-data might have more insight into this though?

@justinegeffen, I'd probably lean towards real-time if you want to make that change, if only because that term seems to be used most consistently in various Mattermost documentation.

Done. Thanks @lieut-data and @justinegeffen


1.47.1 Release introduces hydration errors

Describe the bug
When upgrading to the latest version, 1.47.1 at the time, hydration errors are introduced for ssr.
Latest working versions are
"@tanstack/react-router": "1.46.8",
"@tanstack/router-devtools": "1.47.1",
"@tanstack/router-plugin": "1.47.0",
"@tanstack/start": "1.47.0",
Your Example Website or App
https://tanstack.com/router/latest/docs/framework/react/examples/basic-ssr-file-based
Steps to Reproduce the Bug or Issue

Open the basic-ssr-file-based example.
Refresh the app
Check console for hydration errors

Expected behavior
No hydration errors
Screenshots or Videos

Platform

OS: macOS
Browser: Edge

Additional context
No response

@SeanCassiere  @mta-trackunit please have a look

Tanner is aware of this and looking into it.
@idonov for the time being please stick to 1.47.0.


HEDA Trigger Implementation

Switch to using HEDA Trigger framework. Currently the INT_InteractionProcessor.cls is being called from a standard Salesforce Trigger, it would be more beneficial to use the HEDA Trigger framework.

Hey @detonation0 ! Could you share a little bit more about this Issue?
FYI - @debbieduran @karamcintyre

Gotcha @detonation0, thanks for the extra details and clarification!

We did this at WGU, and I would be happy to submit as a pull request if you want to take the package that direction. @ninita-gomez  @debbieduran  @karamcintyre


Plugin crash Volkswagen App

Hi
I have a problem with the plugin, it works, but after 2-3 hours it crashes the Volkswagen app, and I have to wait around 24 hours. Here's a photo of my app when it crashes (it's only on the car tab, not the location. I also have the problem on the Volkswagen site, I can't access consumption of my vehicle during the accident. Do you have any ideas?
Log Homebridge with "BUG":
[4/20/2024, 9:44:48 PM] [We Connect ID] Error: Invalid protocol: weconnect:
at Request.init (/usr/local/lib/node_modules/homebridge-vwconnectid/node_modules/request/request.js:458:31)
at Redirect.onResponse (/usr/local/lib/node_modules/homebridge-vwconnectid/node_modules/request/lib/redirect.js:149:11)
at Request.onRequestResponse (/usr/local/lib/node_modules/homebridge-vwconnectid/node_modules/request/request.js:986:22)
at ClientRequest.emit (node:events:518:28)
at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:698:27)
at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17)
at TLSSocket.socketOnData (node:_http_client:540:22)
at TLSSocket.emit (node:events:518:28)
at addChunk (node:internal/streams/readable:559:12)
at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
[4/20/2024, 9:44:48 PM] [We Connect ID] Login successful
[4/20/2024, 9:44:48 PM] [We Connect ID] START getPersonalData()
[4/20/2024, 9:44:48 PM] [We Connect ID] START getVehicles
[4/20/2024, 9:44:49 PM] [We Connect ID] getVehicles: {"data":[{"vin":"WVWZZZAUZJW801122","role":"PRIMARY_USER","userRoleStatus":"ENABLED","enrollmentStatus":"COMPLETED","brandCode":"V","model":"Golf GTE","nickname":"Golf 7.5 GTE","capabilities":[],"images":{},"coUsers":[],"devicePlatform":"MBB","tags":[]}]}
[4/20/2024, 9:44:49 PM] [We Connect ID] START getIdStatus
[4/20/2024, 9:44:49 PM] [We Connect ID] END getIdStatus
[4/20/2024, 9:44:49 PM] [We Connect ID] START getIdParkingPosition
[4/20/2024, 9:44:49 PM] [We Connect ID] END getIdParkingPosition
[4/20/2024, 9:44:49 PM] [We Connect ID] Found WeCharge connection
[4/20/2024, 9:44:49 PM] [We Connect ID] Failled wall charger login
[4/20/2024, 9:44:49 PM] [We Connect ID] 429
[4/20/2024, 9:44:49 PM] [We Connect ID] get id parking position Failed
[4/20/2024, 9:44:49 PM] [We Connect ID] getIdStatus: {}
[4/20/2024, 9:44:50 PM] [We Connect ID] getData END
[4/20/2024, 9:44:50 PM] [We Connect ID] Active VIN successfully set to .
[4/20/2024, 9:44:50 PM] [We Connect ID] Restoring existing charging accessory from cache: Charging
[4/20/2024, 9:44:50 PM] [We Connect ID] Restoring existing remaining range accessory from cache: Remaining km
[4/20/2024, 9:44:50 PM] [We Connect ID] Restoring existing climatisation accessory from cache: Climatisation
[4/20/2024, 9:44:50 PM] [We Connect ID] Restoring existing accessory from cache: Home
[4/20/2024, 9:44:50 PM] [We Connect ID] Restoring existing accessory from cache: Home
[4/20/2024, 9:44:50 PM] [We Connect ID] Restoring existing accessory from cache: Work
[4/20/2024, 9:44:50 PM] [We Connect ID] Restoring existing accessory from cache: Work
[4/20/2024, 9:44:50 PM] [We Connect ID] Restoring existing event motions sensor accessory from cache: Car unsafe state
[4/20/2024, 9:44:50 PM] [We Connect ID] Restoring existing setting switch accessory from cache: Reduced AC
[4/20/2024, 9:44:50 PM] [We Connect ID] Restoring existing setting switch accessory from cache: Plug Unlock
[4/20/2024, 9:44:50 PM] [We Connect ID] Restoring existing setting switch accessory from cache: Climatization at unlock
[4/20/2024, 9:44:50 PM] [We Connect ID] Restoring existing setting switch accessory from cache: Window Heating
[4/20/2024, 9:44:50 PM] [We Connect ID] Restoring existing setting switch accessory from cache: Front Left Zone
[4/20/2024, 9:44:50 PM] [We Connect ID] Restoring existing setting switch accessory from cache: Front Right Zone
[4/20/2024, 9:45:19 PM] [We Connect ID] START getIdStatus
[4/20/2024, 9:45:19 PM] [We Connect ID] END getIdStatus
[4/20/2024, 9:45:19 PM] [We Connect ID] START getIdParkingPosition
[4/20/2024, 9:45:19 PM] [We Connect ID] END getIdParkingPosition
[4/20/2024, 9:45:19 PM] [We Connect ID] 429
[4/20/2024, 9:45:19 PM] [We Connect ID] get id parking position Failed
[4/20/2024, 9:45:19 PM] [We Connect ID] Token Refresh started
[4/20/2024, 9:45:19 PM] [We Connect ID] Token Refresh successful
[4/20/2024, 9:45:19 PM] [We Connect ID] getIdStatus: {}
[4/20/2024, 9:45:19 PM] [We Connect ID] Current car state not (correctly) received from VW backend.
[4/20/2024, 9:45:19 PM] [We Connect ID] TypeError: Cannot read properties of undefined (reading 'data')
at VwWeConnect.runEventEmitters (/usr/local/lib/node_modules/homebridge-vwconnectid/node_modules/npm-vwconnectidapi/index.js:1611:37)
at Request._callback (/usr/local/lib/node_modules/homebridge-vwconnectid/node_modules/npm-vwconnectidapi/index.js:1743:26)
at Request.self.callback (/usr/local/lib/node_modules/homebridge-vwconnectid/node_modules/request/request.js:185:22)
at Request.emit (node:events:518:28)
at Request. (/usr/local/lib/node_modules/homebridge-vwconnectid/node_modules/request/request.js:1154:10)
at Request.emit (node:events:518:28)
at Gunzip. (/usr/local/lib/node_modules/homebridge-vwconnectid/node_modules/request/request.js:1076:12)
at Object.onceWrapper (node:events:632:28)
at Gunzip.emit (node:events:518:28)
at endReadableNT (node:internal/streams/readable:1696:12)
[4/20/2024, 9:45:20 PM] [We Connect ID] Found WeCharge connection
[4/20/2024, 9:45:20 PM] [We Connect ID] No able to Login in WeCharge
[4/20/2024, 9:45:49 PM] [We Connect ID] START getIdStatus
[4/20/2024, 9:45:49 PM] [We Connect ID] END getIdStatus
[4/20/2024, 9:45:49 PM] [We Connect ID] START getIdParkingPosition
[4/20/2024, 9:45:49 PM] [We Connect ID] END getIdParkingPosition
[4/20/2024, 9:45:49 PM] [We Connect ID] 429
[4/20/2024, 9:45:49 PM] [We Connect ID] get id parking position Failed
[4/20/2024, 9:45:49 PM] [We Connect ID] Token Refresh started
[4/20/2024, 9:45:49 PM] [We Connect ID] Token Refresh successful
[4/20/2024, 9:45:49 PM] [We Connect ID] getIdStatus: {}
[4/20/2024, 9:45:50 PM] [We Connect ID] Found WeCharge connection
[4/20/2024, 9:45:50 PM] [We Connect ID] No able to Login in WeCharge
[4/20/2024, 9:46:19 PM] [We Connect ID] START getIdStatus
[4/20/2024, 9:46:19 PM] [We Connect ID] END getIdStatus
[4/20/2024, 9:46:19 PM] [We Connect ID] START getIdParkingPosition
[4/20/2024, 9:46:19 PM] [We Connect ID] END getIdParkingPosition
[4/20/2024, 9:46:19 PM] [We Connect ID] 429
[4/20/2024, 9:46:19 PM] [We Connect ID] get id parking position Failed
[4/20/2024, 9:46:19 PM] [We Connect ID] Token Refresh started
[4/20/2024, 9:46:19 PM] [We Connect ID] Token Refresh successful
[4/20/2024, 9:46:20 PM] [We Connect ID] getIdStatus: {}
[4/20/2024, 9:46:20 PM] [We Connect ID] Found WeCharge connection
[4/20/2024, 9:46:20 PM] [We Connect ID] No able to Login in WeCharge
Picture of myvolkswagen

picture Volkswagen app for ios

I think i have too much request (error 429)

Good to hear you solved it!


feat(parser): expand parsing of double braces {{ and attributes

Description

Expands replacement of {{content}} to cover all current Roam markup
Cleans up Roam attributes - :: is replaced by a single :

Codecov Report

Merging #22 (c8e649a) into main (fab5f6c) will increase coverage by 0.02%.
The diff coverage is 100.00%.

:exclamation: Current head c8e649a differs from pull request most recent head 9f69fb0. Consider uploading reports for the commit 9f69fb0 to get more accurate results

@@            Coverage Diff             @@
##             main      #22      +/-   ##
==========================================
+ Coverage   96.35%   96.37%   +0.02%
==========================================
  Files          28       28
  Lines         575      577       +2
  Branches      131      131
==========================================
+ Hits          554      556       +2
  Misses         19       19
  Partials        2        2

Impacted Files
Coverage Δ

src/translator/regex.js
100.00% <ø> (ø)

src/translator/common.js
91.12% <100.00%> (+0.42%)
:arrow_up:

src/translator/doubleBraces.js
100.00% <100.00%> (ø)


feat: tablegpt kernel setups

We should add the custom TableGPT agent IPython kernel to run our code.
This will address the bug related to custom built-in functions not being found (issue: https://github.com/tablegpt/tablegpt-agent/issues/74).
This feature can be merged once both https://github.com/tablegpt/tablegpt-agent/pull/79 and https://github.com/edwardzjl/pybox/pull/29 are merged and published.

The reason for the CI failure is that PyBox has not yet merged the code and released the latest version.

Pybox 0.0.14 was published

Maybe specify pppybox>=0.0.14 in pyproject.toml and try again?

Update：

Added a missing dependency: langchain-openai.
Configure the installation of local kernel dependencies as optional.
pppybox version upgraded to 0.0.14
Align hatch fmt and pre commit ruff configuration.
lint

LGTM, but does tablegpt-agent actually require langchain-openai? It seems to be used only in the documentation and examples for illustration purposes.

LGTM, but does tablegpt-agent actually require langchain-openai? It seems to be used only in the documentation and examples for illustration purposes.

Oh, I didn't consider that. I should add the installation guide for this dependency langchian-openai to the doc.


NotImplementedException in change feed handler

Using the 3.35.3 nuget package, I'm getting this in my logs;
System.NotImplementedException: The method or operation is not implemented. at
Microsoft.Azure.Cosmos.ChangeFeed.ChangeFeedEstimatorIterator.ChangeFeedEstimatorEmptyFeedResponse.get_Headers() at
Microsoft.Azure.Cosmos.OpenTelemetryResponse`1..ctor(FeedResponse`1 responseMessage) at
Microsoft.Azure.Cosmos.ChangeFeed.ChangeFeedEstimatorIterator.<>c.<ReadNextAsync>b__20_1(FeedResponse`1 response) at
Microsoft.Azure.Cosmos.ClientContextCore.RunWithDiagnosticsHelperAsync[TResult](String containerName, String databaseName, OperationType operationType, ITrace trace, Func`2 task, Func`2 openTelemetry, String operationName, RequestOptions requestOptions)

Thrown from here;
https://github.com/Azure/azure-cosmos-dotnet-v3/blob/258d960ae3caa3ad989f60d5e656544c35006d0a/Microsoft.Azure.Cosmos/src/ChangeFeedProcessor/ChangeFeedEstimatorIterator.cs#L405

@mortenbock The stack trace points to OpenTelemetry, are you using 3.35.3 or 3.35.3-preview?

@sourabh1007 Is OpenTelemetry in this case always accessing the Headers? This will never work on the Estimator, the responses are not Network responses.

@ealsur We were using it, but I'm migrating away from the -preview packages now to disable it, because it was incredibly chatty, but that is a discussion for a separate issue :)

@mortenbock Please provide feedback about OpenTelemetry integration in a separate Issue, it's very valuable to us.

@mortenbock Looking at this more in detail:
https://github.com/Azure/azure-cosmos-dotnet-v3/blob/455656753e115d1667bbaa0ae8689a2f3686a6d2/Microsoft.Azure.Cosmos/src/ChangeFeedProcessor/ChangeFeedEstimatorIterator.cs#L169-L174
This only happens if there is no Change Feed Processor running, is this expected in your case?

@ealsur I think in our case, the code for the Change Feed Processor was active, but the container that it was listening for changes from was empty/new, so there were no documents in there.
I don't know if that covers the same case?

@mortenbock No, the condition for this to happen is the Lease Container is empty. This means, a Processor was never running/never started on that Lease Container. Leases are created when the Processor starts for the first time. The above if happens if there are no lease documents at all.
Which means either there is a misconfiguration (your estimator is not pointing to the lease container used by your Processor) or there is a fundamental failure (you are using the Estimator without a Processor to monitor).
This does not remove the need to solve the exception in Open Telemetry, but it is pointing to something not being correct in the way you are using the Estimator.

@ealsur Thanks you for the feedback. Looking at our code, we are starting the estimator before the processor like this:
await _changeFeedEstimator.StartAsync();
await _changeFeedProcessor.StartAsync();

So I guess I could swap the order of those two, so the estimator does not start before the processor has created a lease document the first time the application deploys?
If we were to deploy the estimator separately, would there be a good way to check if a lease exists before starting the estimator?

There's no correlation between when you start the processor or estimator and when the lease/checkpoint document/item is written - i.e., one doesn't wait for the other, and there is no guaranteed max time that one could sleep for.
Question: If the estimator is left running, will it work once a lease has been established, or does the absence of one prevent it from starting its normal cycle?
... And a bump for the programmatic way to trigger deletion or rewinding of the checkpoint request: https://github.com/Azure/azure-cosmos-dotnet-v3/issues/510