Does not work with obfuscator vite plugin

Describe the bug
Enabling the vite obfuscator plugin in wxt causes the content script to not work.
I found that the vite plugin in wxt with apply:'build' configured was still being run with pnpm dev, There are no issues with this vite plugin and works just fine in normal vite projects.
To Reproduce
wxt-test.zip

Install dependencies: pnpm i
Start dev mode: pnpm dev

Screenshots
https://github.com/wxt-dev/wxt/assets/650444/a92cbcf3-fbc8-4ec2-bced-760de4211690
Environment

  System:
    OS: Windows 11 10.0.23601
    CPU: (12) x64 AMD Ryzen 5 3600 6-Core Processor
    Memory: 17.65 GB / 31.93 GB
  Binaries:
    Node: 20.6.1 - C:\soft\nodejs\node.EXE
    npm: 9.8.1 - C:\soft\nodejs\npm.CMD
    pnpm: 8.12.0 - ~\AppData\Local\pnpm\pnpm.EXE
  Browsers:
    Edge: Chromium (120.0.2210.61)
    Internet Explorer: 11.0.23601.1000

It's being applied because content scripts are built using library mode during development. If you only want to apply it during the dev command, you'll have to manually choose when it's applied. Something like this should work fine:
vite: ({ command }) => ({
  plugins: [
    command === "dev" ? Obfusticator() : [],
  ],
}),

But if it doesn't work in development, I doubt it will work in production...

The CLI is reporting some kind of error, but I can't figure out what they are since the obfuscation plugin doesn't support source maps, and the error message is swallowed. I also can't log anything in the service worker when running the dev command, and none of the logs I'd expect to see are printed. I imagine the obfustication plugin is also responsible for that somehow, but I didn't look into it too much.
Can confirm, the production build of the extension doesn't work either. So I don't know what's going on... I would just recommend not using the plugin and relying on the default minification settings for now. I won't have time to debug this any further today, and the plugin doesn't make it easy. So yeah, this will probably be in limbo for a while.

Ok, glad you found one that works!


Last batch always pad up to the batch size and cause error "logits and labels must be broadcastable"

I'm using tensorflow 2.4.1 on Win 10 and Python 3.8.6.
When I use data generator and reach the last batch of training, the model will always pad up to the full batch size even if the real size is less than that.
This will cause an error "logits and labels must be broadcastable", which is basically a mismatch of my label size (13x24) and predication size (32x24), which 32 is my batch size and 24 is number of classes.
BATCH_SIZE = 32
NUM_EPOCHS = 1
NUM_CLASSES = 24
TIME_STEPS = 1000

def build_model():
    total = ((len(tr_idx) + BATCH_SIZE - 1) // BATCH_SIZE) * NUM_EPOCHS

    inp1 = layers.Input(shape=(TIME_STEPS, 12))
    # inp2 = layers.Input(shape=2)

    out = layers.BatchNormalization(axis=1)(inp1)
    out = layers.Conv1D(filters=64, kernel_size=50, strides=10, activation='relu')(out)
    out = layers.Conv1D(filters=64, kernel_size=50, strides=10, activation='relu')(out)
    out = layers.MaxPool1D(pool_size=2)(out)
    out = layers.Flatten()(out)
    out = layers.Dense(NUM_CLASSES*2, activation='relu')(out)

    out1 = layers.Dense(NUM_CLASSES, activation='softmax')(out)
    out2 = layers.Dense(NUM_CLASSES, activation='softmax')(out)
    out3 = layers.Dense(NUM_CLASSES, activation='softmax')(out)

    model = models.Model(inp1, [out1, out2, out3])
    model.compile(loss='categorical_crossentropy', optimizer=optimizers.Adam(learning_rate=keras.experimental.LinearCosineDecay(5e-4, total)))
    # model.summary()
    return model

model = build_model()

Here is my data generator
class datagen:
    def __init__(self, data, batch_size = BATCH_SIZE, branch='train'):
        self.data = data.reset_index(drop=True)
        self.batch_size = batch_size
        self.branch = branch
        self.steps = len(self.data) // self.batch_size
        if len(self.data) % self.batch_size !=0:
            self.steps += 1

    def __len__(self):
        return self.steps

    def __iter__(self):
        while True:
            if self.branch == 'train':
                self.data = self.data.sample(frac=1).reset_index(drop=True)
            for i in range(self.steps):
                batch_data = self.data[i * self.batch_size: (i+1) * self.batch_size]
                batch_image_ids = batch_data['ID'].tolist()
                with zipfile.ZipFile('record_step1k.zip', 'r') as zipf:
                    tmp = np.zeros((self.batch_size, TIME_STEPS, 12))
                    for cnt, id in enumerate(batch_image_ids):
                        x = zipf.read(id)
                        tmp[cnt] = np.frombuffer(x).reshape((12, -1)).transpose()
                if self.branch == 'train':
                    yield tmp, [keras.utils.to_categorical(batch_data['Dx_1'], NUM_CLASSES),
                                keras.utils.to_categorical(batch_data['Dx_2'], NUM_CLASSES),
                                keras.utils.to_categorical(batch_data['Dx_3'], NUM_CLASSES)]
                else:
                    yield tmp

Found the issue. In the data generator should change  tmp = np.zeros((self.batch_size, TIME_STEPS, 12)) to  tmp = np.zeros((len(batch_data), TIME_STEPS, 12))


Remove file upload performance warning

This warning is intrusive and we have direct blockstore uploads available for users, so it can be removed. A note in the docs will be added in a follow-up.

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

Comparison is base (98a5a39) 88.50% compared to head (749b51a) 88.29%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #146      +/-   ##
==========================================
- Coverage   88.50%   88.29%   -0.21%
==========================================
  Files           6        6
  Lines         400      393       -7
  Branches       57       55       -2
==========================================
- Hits          354      347       -7
  Misses         27       27
  Partials       19       19

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


Setting up CI/CD processes & actions

automated testing needed after pushes to main

I have created this test file to test the Gradio interface (with LaVague!).
Might be some issues with timing of the sleep time to make sure we wait until LaVague finishes generating code and executing it, before moving to the next action.
import time

from selenium import webdriver
from selenium.webdriver.chrome.service import Service
from selenium.webdriver.common.by import By
from selenium.webdriver.chrome.options import Options
from selenium.webdriver.common.keys import Keys
import os.path

chrome_options = Options()
chrome_options.add_argument("--headless") # Ensure GUI is off
chrome_options.add_argument("--no-sandbox")
chrome_options.add_argument("--window-size=1600,900")

homedir = os.path.expanduser("~")
chrome_options.binary_location = f"{homedir}/chrome-linux64/chrome"
webdriver_service = Service(f"{homedir}/chromedriver-linux64/chromedriver")

driver = webdriver.Chrome(service=webdriver_service, options=chrome_options)

# Specify the remote debugging address

# Now you can control the existing Chrome session

# Let's proceed step by step.
# First we need to identify the text area where we need to enter the URL, then we can click on it and press 'Enter'.

# Based on the HTML provided, we need to find the text area that is associated with entering the URL.
# The text area can be identified using the data-testid attribute "textbox" and the preceding text "Enter URL and press 'Enter' to load the page."
# We can use an XPath expression to find the text area that follows the specific span element containing the instructions.

# First, we find the span element that contains the instructions.
instructions_span = driver.find_element(By.XPATH, "//span[contains(text(), 'Enter URL and press')]")
# Then, we find the text area that is a following sibling of the span element.
url_text_area = instructions_span.find_element(By.XPATH, "following-sibling::textarea")

# Click on the text area to focus on it.
url_text_area.click()

# Now we can simulate pressing the 'Enter' key.
from selenium.webdriver.common.keys import Keys
url_text_area.send_keys(Keys.ENTER)# Let's proceed step by step.
time.sleep(10)

# First we need to identify the first example under the 'Examples' section, then we can click on it.

# Based on the HTML structure, we can see that the examples are buttons with the class "gallery-item svelte-13hsdno".
# We need to find all elements with this class and then click on the first one.

# Find all elements with the class name
examples = driver.find_elements(By.XPATH, "//button[contains(@class, 'gallery-item')]")

# Click on the first example
examples[0].click()
# Let's proceed step by step.
# First we need to identify the text area, then we can click on it and press 'Enter'.

# Based on the HTML provided, we need to devise the best strategy to select the text area.
# The text area can be identified using the data-testid "textbox", but we should also use the parent elements to ensure uniqueness.
# We can use the ancestor div with class "block" and id "component-17" to make sure we are selecting the correct text area.

text_area = driver.find_element(By.XPATH, "//div[@id='component-17' and contains(@class, 'block')]//textarea[@data-testid='textbox']")

# Click on the text area
text_area.click()

time.sleep(30)

# Now we can press the 'Enter' key
from selenium.webdriver.common.keys import Keys
text_area.send_keys(Keys.ENTER)

# Let's proceed step by step.
# First we need to identify the second example under the 'Examples' section, then we can click on it.

# Based on the HTML provided, we can see that each example is a button with the class "gallery-item svelte-13hsdno".
# We need to find all the buttons with this class and then click on the second one.

# Find all elements with the class "gallery-item svelte-13hsdno"
gallery_items = driver.find_elements(By.XPATH, "//button[contains(@class, 'gallery-item svelte-13hsdno')]")

# Check if we have at least two items to avoid IndexError
if len(gallery_items) >= 2:
    # Click on the second item
    gallery_items[1].click()
else:
    print("There are not enough gallery items to perform the action.")

# Let's proceed step by step.
# First we need to identify the text area, then we can click on it and press 'Enter'.

# Based on the HTML provided, we need to devise the best strategy to select the text area.
# The text area can be identified using the data-testid "textbox", but we should also use the parent elements to ensure uniqueness.
# We can use the ancestor div with class "block" and id "component-17" to make sure we are selecting the correct text area.

text_area = driver.find_element(By.XPATH, "//div[@id='component-17' and contains(@class, 'block')]//textarea[@data-testid='textbox']")

# Click on the text area
text_area.click()

time.sleep(30)

# Now we can press the 'Enter' key
from selenium.webdriver.common.keys import Keys
text_area.send_keys(Keys.ENTER)

# Let's proceed step by step.
# First we need to identify the third example under the 'Examples' section, then we can click on it.

# Based on the HTML provided, the examples are buttons with the class "gallery-item svelte-13hsdno".
# We need to find all elements with this class and then click on the third one.

# Find all elements with the class "gallery-item svelte-13hsdno"
gallery_items = driver.find_elements(By.XPATH, "//button[contains(@class, 'gallery-item svelte-13hsdno')]")

# Check if we have at least three items
if len(gallery_items) >= 3:
    # Click on the third item
    gallery_items[2].click()
else:
    print("There are less than three gallery items available.")

# Let's proceed step by step.
# First we need to identify the text area, then we can click on it and press 'Enter'.

# Based on the HTML provided, we need to devise the best strategy to select the text area.
# The text area can be identified using the data-testid "textbox", but we should also use the parent elements to ensure uniqueness.
# We can use the ancestor div with class "block" and id "component-17" to make sure we are selecting the correct text area.

text_area = driver.find_element(By.XPATH, "//div[@id='component-17' and contains(@class, 'block')]//textarea[@data-testid='textbox']")

# Click on the text area
text_area.click()

# Now we can press the 'Enter' key
from selenium.webdriver.common.keys import Keys
text_area.send_keys(Keys.ENTER)


Unexpected token o in JSON at position

Reposting issue by @zy445566:

Maybe not use "toString" but "JSON.stringify"?
report this error when jsipfs daemon

@alanshaw I believe that was fixed in this series of issues/PRs:

https://github.com/ipfs/js-ipfs-api/pull/825
https://github.com/ipfs/js-ipfs-api/issues/822
https://github.com/ipfs/go-ipfs/issues/5335


CONSOLE-3303: Move plugin template to the openshift GitHub org - add artifects for screenshots and videos

Adding the artifects for screenshots and videos to help figure out  the failing tests issue and verify if the console-plugin-template installation is successfully in CI env.

/assign @jhadvig PTAL

@cyril-ui-developer is not really clear to me why we need all those resources ?

@cyril-ui-developer is not really clear to me why we need all those resources ?

@jhadvig To verify if the plugin-template is installed before the test runs


--sort-by CLI argument doesn't work

I ran it copypasta as in the README:
src $ eslint -f summary . -- --sort-by rule

Oops! Something went wrong! :(

ESLint: 6.8.0.

No files matching the pattern "--sort-by" were found.
Please check for typing mistakes in the pattern.

After reading the ESLint docs on Custom Formatters it doesn't seem like this is even supported by ESLint. Am I missing something?
Is there another way to sort output? Currently it appears random / nondeterministic.
It's not a major problem since piping to | sort -k 2 (for example) does what I want, albeit without the fancy colors.
Thanks for the awesome package :)

thanks @rrrix I'm looking into this issue to see if there's a fix for that

Right, so the CLI options --sort-by etc. suggested in the README apparently don't work anymore, we'll need to find another way to provide this functionality
Currently the recommended way in the ESLint docs on Custom Formatters is to use env vars, which is quite awkward imo 😕
I think the non-determinism of the listed failing rules in the output is due to how ESLint is giving us the list of files and their errors.
I think both the colours and the sorting functionality is helpful especially in bigger projects, so I'll have a look if there are other options than the env vars otherwise I'll update the formatter to use them instead of the CLI options.

Same issue here. May you could consider about applying a default sorting, for example by rule

Same issue here. Maybe you could consider about applying a default sorting, for example by rule

thanks for the suggestion, I'll have a look and come back to you @Camo30

@rrrix fyi the sorting has been fixed now using env vars in #31
@Camo30 fyi default sorting has been added in #32
both features have been released in v1.1.0 🎉


Update search layout fields and compact layouts

Critical Changes
Changes

Updated the Search Layouts on the following objects

Program Engagements
Program Cohorts
Services
Service Deliveries
Service Schedules

Added and assigned Compact Layouts to the following objects

Program Engagements
Programs
Program Cohorts
Services
Service Deliveries
Service Schedules

Issues Closed
New Metadata
Deleted Metadata
Definition of Done
Refer to Asteroids DoD document to see any additional details for the items below
Any net new LWC work has Sa11y tests & 50% or above lines JEST test coverage
CRUD/FLS is enforced in Apex
Permission sets are updated to account for CRUD|FLS|Tab|Classes
Field sets are updated to account for new fields

[ ] UX approval or UX not necessary
[ ] Link the pull request and work item by PR comment and Chatter post respectively, e.g. GUS: W-0000000: Work Name (https://github.com/SalesforceFoundation/PMM/pull/303)
[ ] All acceptance criteria have been met

[ ] Developer
[ ] Code Reviewer
[ ] QA

[ ] PR contains draft release notes
[ ] QE story level testing completed

@lbeller - Most likely the compact layouts will be pushed to the orgs, but I do not believe the assignment of the compact layout will be updated nor will the search layouts.

@lbeller - Most likely the compact layouts will be pushed to the orgs, but I do not believe the assignment of the compact layout will be updated nor will the search layouts.

W-8351050

W-8351050


[e2e]: delegator-generic workflow_dispatch main checkout slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7647944778
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Thu Jan 25 00:18:39 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7662100925
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.delegator-generic.workflow_dispatch.main.checkout.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Fri Jan 26 00:21:18 UTC 2024
Tests are passing now. Closing this issue.


K8containergroupadd

Added new fields for container groups: name, creation timestamp, resource version, restart policy and dns policy to summary page

Why are all these things being disabled?

@Fryguy They are being disabled because we aren't going to support them quite yet.  We will support them eventually.

Closed and blended into PR #2443


Adding git link for Aya Salama to README.md

Great job @Aya-S, thanks!

Ups, just realized that there is a space that it's breaking the README. Can you fix it in a new PR?
Thanks @Aya-S

@datapythonista  on it :D


Internationalisation of Impac angular

This is the work I have done so far for the internationalization of impac-angular.

Ok with the general principles. Each file must be tested one by one when we merge the feature branch to a version branch.


Can renderedMessage be used as the TraceTelemetry message?

Hi
We've just started using this library, and we're very happy with is so far, I do you a have question/change request.
We're writing to trace (I see it's a recent addition) and I was initially confused to find the message template as the trace message.
I assume it's by design with Events, but I was wondering if using the rendered message for trace would be the better option.
I'd be happy to submit a pull request if you agree, looking at the code I doubt it would be much work.
To give you an idea of why I think it's needed, here's what the trace messages look like in Azure.

Good evening James,
yep - I certainly agree that for Traces the rendered message would make much more sense. However there's a similiar problem with Trace telemetries as there is/was with Events: the message content is limited to 10kb. So while I am still not entirely happy with the way Events are handled (because that PR #3 didn't actually 'fix' that a mere 250chars limit) I wouldn't change the Event Sink at the moment but certainly would do it for Traces.
Application Insights drops / used to drop telemetries that went beyond those restrictions completely so I am going a bit back and forth what to do - throw an ArgumentException if the renderedMessage   is bigger than 10k or adding more logic that splits up the single logEvent into multiple AI Traces at sizes of 10k-1 each.
Throwing an ArgumentException might not be the best choice (assuming the worst case here that during development only smaller trace messages, therefore no-one might handle the ArgumentException in their code and then, one day in production in the middle of the night a random trace > 10k occurs and the application crashes).
What would you think / expect as a Sink user?

For me, truncating the message seems like a reasonable approach. Agreed that throwing exceptions from your logger is not exactly the most friendly thing to do.

Yeah good point @ndrochak :+1: I would / will update the parameter documentation explaining the 10k limit so devs know what's going on and why and can handle larger messages themselves if applicable.
Sounds good @JSkimming ?

Hi Jörg, Nick
Thanks both for replying.
I agree with Nick about the exceptions, logging should be very forgiving, and not throw exceptions, does Serilog provide a method for accessing internal errors?
As for the truncating or just leaving it to AI to drop the message. I'm not sure how/where you would choose to truncate, it may not be the rendered message, but a property that blows out the 10K limit. So I think you should just leave it to AI.
My personal opinion is, if someone is attempting to log in excess of 10K of data to AI, then they're doing it wrong. It is the wrong tool for their needs. I try to set-up several logging destinations, sinks in Serilog parlance (I'm new to Serilog BTW), and if I ever want to log such large about of data, I do it a different way, e.g. to a file, table or blob storage.
Does the PR #12 I raised work for you, are there any changes/additions you'd like. I can't do any more work this evening, my wife and I are watching GOT :european_castle: :smile:

I've just been trying the serilog / app insight integration this evening - it's worked perfectly for me apart from this issue. Having the rendered message come through as the trace message would make me very happy! :) And I really don't care whether it drops or truncates message over 10k - rather it didn't throw an exception though.

I've merged @JSkimming's PR #12 in as it is / was for now because this issue right here and #12 are about using the rendered message rather than the template and that was fixed in his PR :!
The topic regarding how to handle messages > 10k is better left in a separate issue. I'll give it a try over the weekend (I am a bit busy this week) and check how AI actually behaves for messages > 10k these days.
Thanks everyone and enjoy GOT @JSkimming ! 😄

:+1: :shipit:


NECO-165 added descriptions of new function.

Ticket
NECO-165
Changes

Added descriptions of new function. Details are in ticket.

How it looks
https://github.com/hishida/media-storage-swift/blob/feature/NECO-165/README.md
Test
None.

I reviewed all the changes and found nothing wrong. I'm going to merge this pull request.


Cannot find module '@schematics/angular/utility/project-targets

<EMAIL_ADDRESS>added 20 packages from 50 contributors and audited 34083 packages in 28.617s
found 82 vulnerabilities (12 low, 33 moderate, 37 high)
run npm audit fix to fix them, or npm audit for details
Installed packages for tooling via npm.
ERROR: Cannot find module '@schematics/angular/utility/project-targets'
ERROR: If you think that this error shouldn't occur, please fill up bug report here: https://github.com/maciejtreder/ng-toolkit/issues/new
INFO: stacktrace has been sent to tracking system.
Nothing to be done.

Closed for housekeeping purposes.


Manifest Override - Replace all node dependencies

Hi,
we have a problem with the new override buildpack for node. In an app's package.json "engines" could be defined e.g. with the value "8.x.x". With our current buildpack override.yml we change (or add) the node version 8.1.2 (binary) dependency and also set the buildpack's default version to 8.1.2. The default node buildpack on our CF landscape is 1.6.18 which already provides newer node (binary) versions (e.g. version 8.9.4). If we now try to push the app with cf v3-push <APP_NAME> -b <OVERRIDE_NODE_BP> -b <DEFAULT_NODE_BP>, it uses node version 8.9.4 instead of the changed version 8.1.2 because 8.9.4 is newer. If there are no "engines" defined within the app's package.json, it uses the version 8.1.2 as expected. This means that only the mentioned dependency gets overwritten.
But we need to overwrite or delete every other node version dependency from the default node buildpack with this override.yml buildpack (or at least the whole dependency lines like 8.x.x instead of only adding / replacing an exact dependency.
Could you please also provide a way to do so?
(This concern was already passed to @sclevine via Slack.)
Best regards,
Jonas

Any news or updates on that? ( @sclevine )

The new Cloud Native Buildpack API will support this natively via the "build plan" concept:
https://buildpacks.io
https://github.com/buildpack
We don't have immediate plans to improve the current interface for this in CF's libbuildpack, but we would consider a PR.


Combobox: Update menuItem to onRenderMenuItem

Fixes #1707
Additional description
Updated menuItem prop to onRenderMenuItem in such a way that the code base is backward compatible raising following warning in the console in the case using menuItem prop.

CONTRIBUTOR checklist (do not remove)
Please complete for every pull request

[x] First-time contributors should sign the Contributor License Agreement.  If you haven't before, wait a few minutes and a bot will comment on this pull request with instructions.
[x] npm run lint:fix has been run and linting passes.
[x] Mocha, Jest (Storyshots), and components/component-docs.json CI tests pass (npm test).
[ ] Tests have been added for new props to prevent regressions in the future. See readme.
[x] Review the appropriate Storybook stories. Open http://localhost:9001/.
[x] The Accessibility panel of each Storybook story has 0 violations (aXe). Open http://localhost:9001/.
[x] Review tests are passing in the browser. Open http://localhost:8001/.
[ ] Review markup conforms to SLDS by looking at DOM snapshot strings.

REVIEWER checklist (do not remove)

[ ] TravisCI tests pass. This includes linting, Mocha, Jest, Storyshots, and components/component-docs.json tests.
[ ] Tests have been added for new props to prevent regressions in the future. See readme.
[ ] Review the appropriate Storybook stories. Open http://localhost:9001/.
[ ] The Accessibility panel of each Storybook story has 0 violations (aXe). Open http://localhost:9001/.
[ ] Review tests are passing in the browser. Open http://localhost:8001/.
[ ] Review markup conforms to SLDS by looking at DOM snapshot strings.

Required only if there are markup / UX changes

[ ] Add year-first date and commit SHA to last-slds-markup-review in package.json and push.
[ ] Request a review of the deployed Heroku app by the Salesforce UX Accessibility Team.
[ ] Add year-first review date, and commit SHA, last-accessibility-review, to package.json and push.
[ ] While the contributor's branch is checked out, run npm run local-update within locally cloned site repo to confirm the site will function correctly at the next release.

At a quick glance, it looks good. I'll add this to my review backlog.

@interactivellama, I have removed the menuItem and pushed the changes.

Thank you @pradumangoyal for the contribution! This moves us toward better props alignment.


Remove compatibility hacks for Rollup >=2.0.0

Rollup 2.0.0 removed some old APIs, which might make it possible to improve our hacks around the additionalFilesDelay option.
We should investigate disabling the delay by default for Rollup >= 2.0.0

Released in v2.4.0


Unable to parse clang version

This code linked below will throw an exception (in my build environment, at least):
https://github.com/ubisoft/Sharpmake/blob/d20ebacbce2f3aff42ae1b478861ac4966e1ce04/Sharpmake.Platforms/Sharpmake.CommonPlatforms/Windows/ClangForWindowsSettings.cs#L52C40-L52C40
[ERROR]
Error:
Version string portion was too short or too long. (Parameter 'input')
        While running C:\Users\Jared\Documents\Git\lateralus\ThirdParty\Sharpmake\tmp\bin\Debug\net6.0\SharpMake.Application.exe
        @08/17/2023 20:34:22: Exception message (level 0):
        Error encountered while generating Lateralus.LunaSVGProject
        Inner exception message (level 1):
        Version string portion was too short or too long. (Parameter 'input')

        Stack trace:
        Inner exception stack trace (level 1):
   at System.Version.ParseVersion(ReadOnlySpan`1 input, Boolean throwOnFailure)
   at System.Version.Parse(String input)
   at Sharpmake.ClangForWindows.GetWindowsClangLibraryPath(String llvmInstallDir, String clangVersion, String libFolderName) in C:\Users\Jared\Documents\Git\lateralus\ThirdParty\Sharpmake\Sharpmake.Platforms\Sharpmake.CommonPlatforms\Windows\ClangForWindowsSettings.cs:line 60
   at Sharpmake.ClangForWindows.GetWindowsClangLibraryPath(String libFolderName) in C:\Users\Jared\Documents\Git\lateralus\ThirdParty\Sharpmake\Sharpmake.Platforms\Sharpmake.CommonPlatforms\Windows\ClangForWindowsSettings.cs:line 47
   at Sharpmake.Windows.BaseWindowsPlatform.SetupSdkOptions(IGenerationContext context) in C:\Users\Jared\Documents\Git\lateralus\ThirdParty\Sharpmake\Sharpmake.Platforms\Sharpmake.CommonPlatforms\Windows\BaseWindowsPlatform.cs:line 109
   at Sharpmake.Generators.VisualStudio.ProjectOptionsGenerator.GenerateCompilerOptions(IGenerationContext context, ProjectOptionsGenerationContext optionsContext) in C:\Users\Jared\Documents\Git\lateralus\ThirdParty\Sharpmake\Sharpmake.Generators\VisualStudio\ProjectOptionsGenerator.cs:line 492
   at Sharpmake.Generators.VisualStudio.ProjectOptionsGenerator.GenerateOptions(IGenerationContext context, ProjectOptionGenerationLevel level) in C:\Users\Jared\Documents\Git\lateralus\ThirdParty\Sharpmake\Sharpmake.Generators\VisualStudio\ProjectOptionsGenerator.cs:line 96
   at Sharpmake.Generators.VisualStudio.Vcxproj.GenerateConfOptions(GenerationContext context) in C:\Users\Jared\Documents\Git\lateralus\ThirdParty\Sharpmake\Sharpmake.Generators\VisualStudio\Vcxproj.cs:line 347
   at Sharpmake.Generators.VisualStudio.Vcxproj.GenerateImpl(GenerationContext context, IList`1 generatedFiles, IList`1 skipFiles) in C:\Users\Jared\Documents\Git\lateralus\ThirdParty\Sharpmake\Sharpmake.Generators\VisualStudio\Vcxproj.cs:line 360
   at Sharpmake.Generators.VisualStudio.Vcxproj.Generate(Builder builder, Project project, List`1 configurations, String projectFile, List`1 generatedFiles, List`1 skipFiles) in C:\Users\Jared\Documents\Git\lateralus\ThirdParty\Sharpmake\Sharpmake.Generators\VisualStudio\Vcxproj.cs:line 154
   at Sharpmake.Generators.GeneratorManager.Generate(Builder builder, Project project, List`1 configurations, String projectFile, List`1 generatedFiles, List`1 skipFiles) in C:\Users\Jared\Documents\Git\lateralus\ThirdParty\Sharpmake\Sharpmake.Generators\GeneratorManager.cs:line 107
   at Sharpmake.Builder.GenerateProjectFile(Object arg) in C:\Users\Jared\Documents\Git\lateralus\ThirdParty\Sharpmake\Sharpmake\Builder.cs:line 1311
        Root stack trace (level 0):
   at Sharpmake.Application.Program.CreateBuilderAndGenerate(BaseBuildContext buildContext, Argument parameters, Boolean generateDebugSolution) in C:\Users\Jared\Documents\Git\lateralus\ThirdParty\Sharpmake\Sharpmake.Application\Program.cs:line 463
   at Sharpmake.Application.Program.GenerateAll(BaseBuildContext buildContext, Argument parameters) in C:\Users\Jared\Documents\Git\lateralus\ThirdParty\Sharpmake\Sharpmake.Application\Program.cs:line 492
   at Sharpmake.Application.Program.Main() in C:\Users\Jared\Documents\Git\lateralus\ThirdParty\Sharpmake\Sharpmake.Application\Program.cs:line 325

To reproduce this I am building sharpmake with .NET 6.0 and I have LLVM 16.0.6 installed using the ClangPowerToys extension in visual studio.
The version 16 in this case will be parsed from a path like: C:\Users\Jared\AppData\Roaming\ClangPowerTools\LLVM\LLVM16.0.6\lib\clang\16.

I've worked around the issue locally with a change like this which I believe should do the trick:
        public static string GetWindowsClangLibraryPath(string llvmInstallDir, string clangVersion, string libFolderName = null)
        {
            if (libFolderName == null)
            {
                Console.WriteLine($@"llvmInstallDir: {llvmInstallDir} clangVersion: {clangVersion}");
                int version;
                if(!int.TryParse(clangVersion, out version))
                {
                    version = System.Version.Parse(clangVersion).Major;
                }
                // Starting with LLVM 15, runtime library structure changes.
                if (version >= 15)
                    libFolderName = "x86_64-pc-windows-msvc";
                else
                    libFolderName = "windows";
            }
            return Path.Combine(llvmInstallDir, "lib", "clang", clangVersion, "lib", libFolderName);
        }

Hello,
We will check this soon.

It looks from the callstack that you are using an old sharpmake version.
The System.Version.Parse call was removed in commit f6d15d. Could you retry without your changes using latest sharpmake version?


Skip creation of PR in pre-release stage if it contains no commits

If a release needs to be iterated upon due to issues that are encountered, it may be necessary to run the Pre-release stage multiple times. In that case, it's possible the PR that gets generated by Update security-partners-dotnet has already been merged. So when a subsequent run of the Pre-release stage occurs, it will still create the PR even though it contains no commits. I suggest that the PR creation be skipped if it contains no commits, and include a warning message instead.

FYI @MichaelSimons, @mthalman we will ask @ali-turan7 to help us with this and onboard him onto the project

The necessary control is applied by comparing the new and target branches to determine whether a new commit has been made as well as whether a new PR is necessary.


Future Architecture: Hybrid Routing + Minimal Hydration

As many of you have seen we have begun experimenting with future architecture, but there is still a lot of work to be done both to validate our results and generalize the approach so it is easily adoptable by developers. This issue is being made to lay out the body of our work and keep track of our progress in these areas.
This is a substantial task for an OSS project and it is our hope to expand efforts in this area. Both through OSS contributions and programs like Solid Fellowships. We believe that through this effort we can improve the overall quality of the web both for end users and for developers. And in so we are looking for help. Your help.

This issue describes future work that is independent of any SolidStart 1.0 release and represents patterns that still leverage core SolidStart structures like its FileSystem routing, Data Functions, and Progressive Enhanced Forms.

Motivation
It is no secret the size of JavaScript on websites has been increasing at a steady state over the past decade. Driven by our desire for more interactivity, and frankly a web architecture that has mostly disregarded this cost. And it is a cost especially felt on slower networks and devices. The web is for everyone and this is largely unacceptable.
Single Page App architecture, the one most often used when building SolidJS applications, is one where the assumption is where all UI processing will eventually make it to the browser. What can be on the client will be on the client. Attempts to mitigate this have had some amount of success. Server-side rendering has improved the speed in which we display these applications. Smaller and performant frameworks like Preact, Solid, and Svelte have been able to deliver amazing experiences with a smaller footprint. But ultimately these do not scale any better. At a certain complexity of application, any wins by the framework get offset by the sheer amount of end-developer code. This is not those developers' fault but an architecture that doesn't allow them to achieve their goals.
Opportunity
Solid's novel approach to reactivity and reactive rendering has caused a bit of a renaissance in frontend the past years influencing projects like Vue Vapor, Preact Signals, Marko 6's Sub-Component Hydration and Resumability, Qwik's Finer-Grained Template-less hydration, and even new proposals for upcoming versions of Angular. The reason is it abandons the runtime Component model popularized by React and used in most frameworks for one that scales on interactivity rather than view size.
This approach to optimizing client rendering which has made Solid formidable in most benchmarks over the past 5 years, may also our salvation for solving the next set of problems regarding hydration and reducing our JavaScript footprint. I spent the past year exploring, talking with creators, and reverse engineering solutions across the ecosystem to understand the state of the art. I've worked with different framework authors benchmarking and raising awareness for the problem space. Netlify came on board to sponsor my efforts to improve relations and build a better web in OSS. I think it is vitally important to continue this work to realize this future architecture.
Overview
If things are to move more to the server it starts with the understanding we need to not have everything in the browser. The most redundant things are what we often refer to as the double data problem. The modern server-rendered JavaScript app sends the data both encoded in the final HTML output and as JSON data in a script tag so that it can hydrate. It also ships the "template" code both in the realized HTML and in the JavaScript bundle. These are important places we should be looking at reducing our overhead.
Converse to recent popular opinion this means reducing the surface area of isomorphic code. If most of the code only needs to be run on the server we eliminate both examples of "double data". Isomorphic code is still very important because depending on the server for all interactions is equally a recipe for poor site performance.
And performance is a big concern here. We've seen server-driven hybrid's in the past but many have been branded as feeling clunky. Too much reliance on servers for interactivity. Too much back-and-forth serialization to maintain app and view state. There have been versions of this dating back through things like ASP.NET UpdatePanels to things like Turbo. And in our opinion, we are yet to see a solution that fully succeeds at this marriage of user experience and developer experience goals.
We have newer metrics like INP(Interaction to Next Paint) that are giving us a better idea of the latency of our app experiences and we need to ensure that we aren't only improving TTI (Time to Interactive) and sacrificing other metrics.
Approach
We see that we need to address this through a few key areas that need to work all in tandem. If any area is not optimal enough it could undermine the viability of the whole effort.
Hybrid Routing
The focus of this work is leveraging the server more to save client-side costs. This revolves around rethinking the routing paradigm of modern frameworks. The router is the backbone of any web architecture, as the web itself is just a giant router. Every generational improvement in architecture has been accompanied by an evolution in routing. The early document web was based on file system routing. This evolved into the dynamic web which saw the advent of server routers to field requests and send back the appropriate resources. The Single Page App is defined by its client-side routing. History API enabled isomorphic server-rendered SPAs. And the next stage is no different.
The idea being presented is to serve future navigations with HTML partials. These partials should be able to be streamed in and represent only the parts of the page that need to change. The pattern we've been investigating so far is using Nested Routing (as popularized by Ember.js). We have prototyped a modified version of Solid's router that on the server only sends parts of the route that have changed, and a minimal client router that intercepts anchor clicks and is responsible for swapping these portions on navigation.
An additional consideration is "reload" or "refresh" actions where changes happen on the same route. In these cases state needs to be preserved. It is not enough to just replace the HTML. This requires some level of diffing against the existing page to ensure state preservation.
Hydration Reduction
If we wish to keep client routing we need to rethink all adjacent technologies. Things that had narrower scope previously return to having greater importance. Hydration for instance is now something felt on every navigation instead of only the initial load. This means that not only are we concerned with how to navigate and but how we establish interactivity in our application.
The easiest entry into this is using "Island" or manually defined (isomorphic)hydrated zones. With this approach, the code outside is assumed server-only and does not require being sent to the browser. This has the convenient side effect that only data that data that is passed directly to these Islands needs to be serialized, and any data fetched and used outside can be skipped.
This approach has been used at eBay for almost a decade and has been shown to yield savings of 60-80% on pages. Combining with Hybrid Routing does add a bit of overhead but the bigger concern is whether this experience is sufficiently smooth for future navigation after the page has already loaded.
Progress
As of Nov 4th 2022:
We have created early prototypes of Hybrid Routing and Islands.
Initial Routing Demo
Hackernews
Start Docs
Movies App
Work Done So Far

Serialized HTML partials
Asset partials
innerHTML hybrid nested routing
DOMDiff hybrid nested routing (thanks to micromorph)
Partial Hydrated Islands (support for Eager, and Idle Hydration
Island preservation
Code split Islands based JavaScript Entries
Dynamic import Islands
"use client" annotated islands

Work Left to Do

Support for streaming HTML Partials
Conventions around defining Client Islands
Reduce Server rendering on partials (Today it fully re-renders on server)
Server Context
Reactive graph serialization and restoration
Closure reversing compiler
Benchmarks

Determine impact on Hydration Time
Determine impact on INP
Compare between HTML diff vs Replace with Island preservation
Evaluate impact of Resumability

Just saw this, what does Closure reversing compiler mean?


fix: ensure ExecCommand obeys timeout

fixes the problem in the utils.ExecCommand where the timeout argument
was not being honored.
This patch uses the provided timeout to enrich the rest.Config, and to create
a timed context to pass to the newly available StreamWithContext.
Signed-off-by: Jaime Silvela<EMAIL_ADDRESS>

/test

/test

/test

/test

/test

/test

/test


chore(sdk-trace-web): fix lint warnings

related to #1093,
Which problem is this PR solving?

This PR fixes lint warnings in sdk-trace-web package.

Short description of the changes

Fix lint warnings

@dyladan It appears the cla is broken, do you know how to fix this ?

/easycla

@vmarchaud ^ like that


Running out of memory during simultaneous training and evaluation

While training on the KITTI data set, I seem to run out of memory when I try to run both evaluation scripts simultaneously (scripts/eval_train.sh and scripts/eval_val.sh):
Internal: failed initializing StreamExecutor for CUDA device ordinal 1: Internal: failed call to cuCtxCreate: CUDA_ERROR_OUT_OF_MEMORY;
Is this just a matter of me needing to adjust my batch size to allow all 3 processes enough memory to simultaneously run? I have ~24GB of VRAM across 2 Titan XPs - since this implementation does not seem setup to support multiple GPUs, I've tried using GPU 0 for training and GPU 1 for running the two evaluation scripts, I still run out of memory though.
Thanks!

Hi,
When you launch a train or eval thread, tensorflow by default accesses all the GPUs that is visible to it. To compleletly seperate them, you need to set the evironment variable CUDA_VISIBLE_DEVICES to be the GPU you want to use for each task. Say, in session-1, set visible device to 0, then launch training. In session-2, set visible device to 1, and launch eval. In my experiment, I assign each train/eval_train/eval_val to a different GPU instance.
Hope that helps.


[hi] Localize en/docs/contribute/review/for-approvers.md

[hi] Localize en/docs/contribute/review/for-approvers.md
Prerequisites:

If this is your first contribution, visit Contribute to K8s docs for information on how to get started.
Review a few examples of localized glossary entries to see which content you change and which you live unchanged.

Procedure:

Check out dev-1.22-hi.1 and create a working branch called for-approvers.
Create a file called content/hi/docs/contribute/review/for-approvers.md.
Copy the content of https://github.com/kubernetes/website/blob/main/content/en/docs/contribute/review/for-approvers.md to the file you created.
Localize the content.
Push your change and create a pull request.

Completing this feature issue fixes part of :-https://github.com/kubernetes/website/issues/36455

Note:- Self-assign only one issue at one time

Note:- To know about the preferred localization of common Kubernetes related terms, check this spreadsheet

/assign

/assign

@bishal7679 I have started working on localizing the content

Hey bandya! It's a good practice to always ask the assignee before working
on an issue which has already been assigned.
I'm currently working on this issue and will raise a PR soon
Please find some other issue to look for:)
Thank you!
On Fri, 2 Sep, 2022, 8:11 pm bandya2003, @.***> wrote:

@bishal7679 https://github.com/bishal7679 I have started working on
localizing the content
—
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/website/issues/36474#issuecomment-1235586460,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUQQSLVSGNO3JT5YMUNXTDDV4IGZTANCNFSM6AAAAAAQBU3OS4
.
You are receiving this because you were mentioned.Message ID:
@.***>

@NitishKumar06 ok fine ,I'll work on some other issue then

sure thanks a lot @bishal7679

/assign

@SuperAayush can go ahead with working with this issue.
/unassign

/remove-lifecycle rotten

/remove-lifecycle stale
/triage accepted


test(bezier-react): Improved array test coverage

Self Checklist

[x] I wrote a PR title in English and added an appropriate label to the PR.
[x] I wrote the commit message in English and to follow the Conventional Commits specification.
[ ] I added the changeset about the changes that needed to be released. (or didn't have to)
[x] I wrote or updated documentation related to the changes. (or didn't have to)
[x] I wrote or updated tests related to the changes. (or didn't have to)
[x] I tested the changes in various browsers. (or didn't have to)

Windows: Chrome, Edge, (Optional) Firefox
macOS: Chrome, Edge, Safari, (Optional) Firefox

Related Issue

Summary

changed isLastIndex -> isArrayLastIndex
Improved array test coverage

Details

TO-BE

AS-IS

Breaking change? (Yes/No)

References

@yangwooseong 해당 PR도 머지 부탁드립니다!


Pattern: Update the CTA section functional specifications based on visual designs provided by Lila

User Story

As a [user role below]:
DDS developer

I need to:
have the CTA section functional specs

so that I can:
so that I can properly code the CTA section component that meets the Solution template requirements

Additional information

The visual designs were provided by Lila in Sprint 20-08.  This issue is to account for the work to review the functional specs created in Sprint 20-07 and make any changes needed to align with the designs provided by Lila.
Design Issue (#2031 )
Development issue (#1852 )

Acceptance criteria

[x] Reviewed the CTA section functional specifications
[ ] Additional stories are created, if needed, for any work to be done in future sprints.
[ ] If no changes are needed, sent a message to Jeff to let him know that the functional specs are ready for a developer by tagging him in the dev issue.

@photodow @kathysaraf @mbarry325 We missed this unassigned issue during the mid-sprint review meeting earlier today.  I created this issue as a reminder to check the functional specs created last sprint against the designs Lila delivered on Monday.

Just looked it over. Looks good, and will move to done.

Reopened this issue to capture the changes decided in the April 21 visual specs review meeting with Lila.  The Content block pattern will not be separate, but included in the Content section pattern.

updates done and ready


Recipe Removal Auto Complete Issue

Heya Way,
Is there any way you could edit the auto-complete for "recipes.remove(, );" and remove the comma? Most removal recipes won't need that extra comma :)
Thank you!
Darkosto

Just dumping a link that is kinda related to this :p
https://github.com/jaredlll08/RecipeStages/blob/master/src/main/java/com/blamejared/recipestages/handlers/Recipes.java

@Darkosto is this still an issue?


feat: subnetSelector-enhancement

Signed-off-by: smcavallo<EMAIL_ADDRESS>

Fixes #
Description
Support comma separated tag values in subnetSelector - (wildcard search is not flexible enough.)
Consider the use case where Private1,Private2 subnets should be used but Private3 excluded.
This is a simple enough change to split the string and supported by the ec2 tag filters.
It is done this same exact way for aws-ids searches.
How was this change tested?

Unit tests

Does this change impact docs?

[X ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[ ] No

Release Note

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Looks like this is failing tests: https://github.com/aws/karpenter/actions/runs/3489726900/jobs/5841741532

There is something wrong with the tests.  I am running this test with the original code and it is failing for the same reason.
The below should 100% have worked with the original code.
	It("should discover subnets by tag", func() {
		provider.SubnetSelector = map[string]string{"Name": "subnet-test2"}
		ExpectApplied(ctx, env.Client, test.Provisioner(coretest.ProvisionerOptions{Provider: provider}))
		pod := ExpectProvisioned(ctx, env.Client, recorder, controller, prov, coretest.UnschedulablePod())[0]
		ExpectScheduled(ctx, env.Client, pod)
		createFleetInput := fakeEC2API.CalledWithCreateFleetInput.Pop()
		Expect(fake.SubnetsFromFleetRequest(createFleetInput)).To(ConsistOf(
			"subnet-test2",
		))
	})

Looking into why....and will submit a fix....

@ellistarn - thank you!!!!  Should be all fixed now and the tests should all be passing.  My confusion was from how close the subnet Name and id are.  I tried to add a comment in the tests to help anyone else who is debugging.  It took a bit to figure out where the fixture info was coming from, but all set now.

One last thing @smcavallo, can you make an integration test in github.com/aws/karpenter/test/suites/integration/subnet_test.go.
You can verify the test by running FOCUS="testname from It() block" make e2etests, which will run your singular test against a local cluster. Make sure you have your kubeconfig setup to point to somewhere where this test can execute correctly.

@ellistarn - thanks!!!  I took a shot at writing an integration test if you can please take a look.

@smcavallo, can you put the output of a successful test run in the PR description?

Looks like it's just a go-lint issue renaming Id to ID is all that's remaining.

thanks @tzneal!!!! It has been updated.

I just rebased off master to fix the tests which were referencing deprecated properties

Hey @smcavallo , let me know if you want me to take over this PR to get it across the finish line.

@ellistarn - YES PLEASE, that would be great - thank you so much!!!!

Closed in favor of #3080


Support references to homepage and sections with ref/relref

Ref/relref should support linking to homepage and sections (at least when _index.md exists).

Have you checked that this issue does not already exist?

Yes, I have.

+1

One example where it would be useful: I enabled "defaultContentLanguageInSubdir" on my website -> Boom, instantly dozens of deadlinks that I had to fix manually.

(copied from description of #4725, which I closed as a dupe of this issue)
The raison d'être of the ref/relref shortcodes is to enable pages to link to other pages without knowing in advance their eventual publish URL. This is not only important from a separation of concerns perspective, but it is critical given that the publish URL can be arbitrarily modified a number of ways: by Hugo permalink configuration, or by url or slug front matter params, or switching between pretty and ugly URLs.
Prior to v0.33, the url front matter param was only supported for regular pages. The ref/relref shortcodes weren't necessary for links to section or taxonomyTerm pages. But v0.33 changed this:

Hugo now respects the url value in front matter for all page types, including sections.  Also, you can now configure uglyURLs per section.

Currently there is no way to link to a section or taxonomyTerm page independent of final publish URL. The fix is to update ref/relref shortcodes to support all page kinds. This also lends to greater API consistency.
Related Forum topic: How to link to section pages with ref/relref shortcodes?
Pull request with my implementation forthcoming...

I've implemented this, but the pull requests is pending some questions I need answered. See the the discussion on the forum.


nodejs 14

update required to nodejs 10.x to 12/14 for C9BootstrapProviderframework

Looks like this is from CDK. Updating the CDK version and deploying a new release should resolve.


Update Dockerfile (#43)

Updates the Dockerfile with changes suggested by @GWnbsp  in https://github.com/Lissy93/web-check/issues/43#issuecomment-1719212234
Summary of Changes

ARG Statements: Introduced ARG statements for Node.js and Debian versions, making the Dockerfile more customizable.
SHELL Command: Changed the default shell to Bash with certain options enabled, improving robustness.
Chromium Installation: Updated Chromium installation to use Google's signing keys and repositories, aiming for more secure and up-to-date packages.
Chromium Version: Added a step to save Chromium's version into /etc/chromium-version for reference.
Directory Creation: Added a new directory /app/data in the container's filesystem.
CMD Change: Changed the CMD to start Node.js server (server.js) instead of using yarn serve.
General Cleanup and Comments: Code has been refactored for better readability and detailed comments have been added for clarity.
Dependency Installation: Kept yarn install and the removal of the Yarn cache, but the command is more streamlined.
Other Minor Changes:

Added flags like -qq and --no-install-recommends for quieter and optimized installation.
Enhanced cleanup with rm -rf /var/lib/apt/lists/*.

Thanks @ChrisCarini, merged your PR in #91 ✅
Sorry about this one, @DyroxOne is just a spam bot duplicating random PRs on GitHub. Closing this one.


Test suite failure with GHC 8

This is due to hlint failing, I'm not sure if it's related to GHC 8:
> /tmp/stackage-build8/ed25519-<IP_ADDRESS>$ runghc -clear-package-db -global-package-db -package-db=/home/stackage/work/builds/nightly/pkgdb Setup configure --enable-tests --package-db=clear --package-db=global --package-db=/home/stackage/work/builds/nightly/pkgdb --libdir=/home/stackage/work/builds/nightly/lib --bindir=/home/stackage/work/builds/nightly/bin --datadir=/home/stackage/work/builds/nightly/share --libexecdir=/home/stackage/work/builds/nightly/libexec --sysconfdir=/home/stackage/work/builds/nightly/etc --docdir=/home/stackage/work/builds/nightly/doc/ed25519-<IP_ADDRESS> --htmldir=/home/stackage/work/builds/nightly/doc/ed25519-<IP_ADDRESS> --haddockdir=/home/stackage/work/builds/nightly/doc/ed25519-<IP_ADDRESS> --flags=
Configuring ed25519-<IP_ADDRESS>...
> /tmp/stackage-build8/ed25519-<IP_ADDRESS>$ runghc -clear-package-db -global-package-db -package-db=/home/stackage/work/builds/nightly/pkgdb Setup build
Building ed25519-<IP_ADDRESS>...
Preprocessing library ed25519-<IP_ADDRESS>...
[1 of 1] Compiling Crypto.Sign.Ed25519 ( src/Crypto/Sign/Ed25519.hs, dist/build/Crypto/Sign/Ed25519.o )
Preprocessing test suite 'properties' for ed25519-<IP_ADDRESS>...
[1 of 1] Compiling Main             ( tests/properties.hs, dist/build/properties/properties-tmp/Main.o )
Linking dist/build/properties/properties ...
Preprocessing test suite 'hlint' for ed25519-<IP_ADDRESS>...
[1 of 1] Compiling Main             ( tests/hlint.hs, dist/build/hlint/hlint-tmp/Main.o )
Linking dist/build/hlint/hlint ...
Preprocessing test suite 'doctests' for ed25519-<IP_ADDRESS>...
[1 of 1] Compiling Main             ( tests/doctests.hs, dist/build/doctests/doctests-tmp/Main.o )
Linking dist/build/doctests/doctests ...
> /tmp/stackage-build8/ed25519-<IP_ADDRESS>$ dist/build/properties/properties
Signature roundtrip                     : +++ OK, passed 100 tests.
Detached signature roundtrip            : +++ OK, passed 100 tests.
Detached signature length               : +++ OK, passed 100 tests.
Detached signature length (#2)          : +++ OK, passed 100 tests.
Passed 400 tests!
> /tmp/stackage-build8/ed25519-<IP_ADDRESS>$ dist/build/hlint/hlint
src/Crypto/Sign/Ed25519.hs:391:1: Warning: Eta reduce
Found:
  sign' sk xs = dsign sk xs
Why not:
  sign' = dsign

src/Crypto/Sign/Ed25519.hs:406:1: Warning: Eta reduce
Found:
  verify' pk xs sig = dverify pk xs sig
Why not:
  verify' = dverify

2 hints

Oi, strange. I thought I told hlint to ignore eta reduction warnings, though.
I'll take a look. I need to do a release of <IP_ADDRESS> with newer documentation and fix up the CI to include 8.0.1, etc.

I haven't seen this with GHC 8.0.1 or anything, and as I said, I told HLint to ignore eta reduction warnings, so maybe this is just a random ghost?
Closing, due to inability to reproduce.


Importing Chota core from CDN using CSS @import does not work

The docs show the "quick start" method of using Chota without installing locally, by referring to the CSS file on a CDN-
<link rel="stylesheet" href="https://unpkg.com/chota@latest">
When I tried to do the same thing by using an @import statement at the head of my local CSS file, I could not get it to work.
Having done some searching on the net, I found a similar issue discussed here-
The discussion on Stackexchange indcates that the issues is caused by the CDN delivering the CSS file with the wrong MIME type (in their case as text/plain instead of text/css). I have not been able to verify that this is what's happening with Chota, but something similar seems likely.

@colin-e-nhsd  Hello, can you make a Codepon for this?

Hmm, I set up a codepen, which works as expected. So I then went back to my code and re-set up the @import, and that works to...
Must have been an error in my original setup somewhere. Sorry for the inconvenience.


Update pre-commit repos

Switch to quarterly updates and manually updated via:
import yaml
import subprocess

file = ".pre-commit-config.yaml"

with open(file, "r") as f:
    data = yaml.safe_load(f)

repos = []
for repo in data['repos']:
    if 'mirrors-prettier' not in repo['repo']:
        repos.append("--repo")
        repos.append(repo['repo'])

command = ['pre-commit', 'autoupdate', '--freeze'] + repos
subprocess.call(command)

Work around to avoid updating to an alpha version of https://github.com/pre-commit/mirrors-prettier.

What does that Python script do?
The patch looks fine.

It runs this:
pre-commit autoupdate --freeze --repo https://github.com/pre-commit/pre-commit-hooks --repo https://github.com/psf/black --repo https://github.com/adamchainz/blacken-docs --repo https://github.com/asottile/pyupgrade

If you run
pre-commit autoupdate --freeze

it updates mirrors-prettier to an alpha release.

I then just updated the mirrors-prettier repo by hand.

Ah, OK, but the quarterly run still has the alpha-inducing behavior?

Yes, I am hoping there will be a stable release soon. If not, we will only have PRs to close 4 times a year.


investigate new kubectl plugin mechanism

https://github.com/kubernetes/kubernetes/pull/66876

currently no way to determine if running as a plugin (may be env var?)

written up doc: https://github.com/cppforlife/knctl/blob/master/docs/kubectl-plugin.md


Bug: heading-blank-lines does not work properly if the line preceding a header has a #

[x] I have verified that I am on the latest version of the Linter

Describe the Bug
With heading-blank-lines on, the linter does not add an empty space above the header if in the line preceding the header contains a hashtag.
How to Reproduce
Example to reproduce issue with
# Heading 1
Lorem ipsum.

## Heading 2
Woah, cool text here. #reallycool
## Heading 3

My bet would be that the cause is with the heading-blank-lines rule.
Expected Behavior
I expect an empty line to be inserted inbetween Woah, cool text here. #reallycool and ## Heading 3
Expected output if applicable:
# Heading 1
Lorem ipsum.

## Heading 2
Woah, cool text here. #reallycool

## Heading 3

Device

[x] Desktop
[ ] Mobile

Additional Context
It didn't seem to matter where the # is placed. At the beginning of the sentence, middle of it, at the end, with a tag, without a tag -- the linter doesn't seem to add a line.

Thanks for reporting this @kndshein . I believe I have a fix for this. The regex that was handling this update was not allowing any instance of # in the text. I will create a PR for this and it should go out in the next release.

I went ahead and merged in the change. So it should be available on master and in the next release. Please let us know if either is not the case.


Entity Store: update() by entityId not working as expected

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior
The following Entity Store, is attached to a local component named "EditableListComponent".
editable-list-item.store.ts
export interface EditableListItemsState extends EntityState<EditableListItem> {
}

export class EditableListItemStore extends EntityStore<EditableListItemsState> {
	constructor() {
		super({}, {name: `EditableListItemStore-${guid()}`});
	}
}

editable-list-item.query.ts
@Injectable()
export class EditableListItemQuery extends QueryEntity<EditableListItemsState> {
	constructor(protected store: EditableListItemStore) {
		super(store);
	}
}

editable-list-item.ts
export class EditableListItem {
	id: string;
	label: string;
	selected: boolean;
	value: string;

	constructor(
		id: string,
		label: string,
		value: string,
		selected: boolean,
	) {
		this.id = id;
		this.label = label;
		this.value = value;
		this.selected = selected;
	}
}

In the EditableListComponent, i'm trying to update an entity in the store by entityId like this:
this.editableListItemStore.update(selectedItem.id, {selected: event.target.checked});
Unfortunately, the entity is updated in the store in a strange way.
The entity with the id "entityId" looks like this now:

It is also happening in Entity Stores which are not related to local components.

Expected behavior
As far as i understood in here. The "selected"
property should had changed to "true" preserving the rest of the entity state.

You're using a class as your model. Read this please:
https://datorama.github.io/akita/docs/additional/class

Thank you Netanel, i haven't read this section of the documentation. Great library.


arduino-hal: Add panic-halt feature

For most beginners, the panic handler will be a simple one. Like the one from the panic-halt crate. It's usage has already been established in most exmaples.
Thus, it would be less boilerplate for beginner projects, if the panic-halt handler would just be a feature. Similar to how the uefi-rs crate handles this.

I am quite torn about doing this.  Yes, it is less boilerplate but on the other side it hides essential parts of a bare-metal rust program.
Users will quickly run into situations where they will want a more complex panic handler to get notice of their code crashing.  And all online docs will tell them to replace their default panic handler with a custom one.
If the default panic handler gets hidden behind another layer of crate indirection, this will be more difficult to grasp than having the very explicit use panic_halt as _; line right there, in the code.
In general, I am very wary of hiding complexity from the downstream user.  Yes, it may make things easier in the beginning, but it creates friction later on when the complexity surfaces in one way or another...

That said, if we can write a general purpose debugging panic handler (e.g. one that prints to the default serial after it was configured), making that available via optional feature would indeed be quite nice.

That makes sense, maybe I'll look into a proper debugging panic handler :)

I created issue #596 to track addition of such a debugging panic handler.  I also wrote down some of my thoughts on the design there.  Feel free to discuss and/or ask questions :)


Load only a single AudioWorklet

This PR changes the worklet loading code to expect only a single module and not a module per AudioWorklet. Before the code was expecting a module for each AudioWorklet but in fact only one module is used. This caused the bug reported here: #1038.
As always, please let me know if there is anything I should change.

thanks!

Hi @tambien and @chrisguttandin. Any progress on this being released into the main branch. Still seeing the issue. Many thanks.
Pete


[Hub Generated] Review request for Microsoft.AzurePlaywrightService to add version preview/2023-10-01-preview

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see Getting help section below.
Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[ ] New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
[x] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[x] Other, please clarify:

We had just introduce this api-version for our public preview release on 27th September, there's a small data type bug which we want to fix within this api-version before it goes into public preview.
Previous PR- https://github.com/Azure/azure-rest-api-specs/pull/25445
Swagger ModelValidation is failing due to known issue referred in the old PR.
There's no usage or traffic of this api-version in prod as the manifest rollout has just been triggered and not rolled out completely yet.

HttpIncomingRequests
| where PreciseTimeStamp > ago(30d)
| where targetUri contains "Microsoft.AzurePlaywrightService"
| where apiVersion contains "2023-10-01-preview"
// Removing dev subs
| where subscriptionId !contains "9fd9eff4-f386-452e-9893-06417ff6e808" and subscriptionId != ""

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.

Breaking changes review (Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

ARM API changes review (Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
Getting help

For general PR approval workflow, see the diagram at the top of this comment.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

/pr RequestMerge

Hey, I see that you have removed BreakingChangesReviewRequired, but it won't let me merge this PR without you getting that approval for breaking changes on this PR.

Please reach out to<EMAIL_ADDRESS>for Breaking Changes Review.

/pr RequestMerge


After account is created the header doesn't update to show link to Account

the same happens after keys import


Setup Wizard ended Prematurely

Hello, how do I fix this?

If you are running on Apple M1 chip through Parallels with ARM version of Windows then there is no solution so far.
I dug the whole night on how to solve it the other day. No solutions yet.
This SW is designedfor Win 32 and 64 bit versions only.
If you prove me wrong I would be so glad!

But I use windows, Win 64 bit

Thanks for ignoring everything that could've been even remotely necessary to help you.


cmake: warn if a Zephyr library is empty instead of CMake failure

Several driver libraries uses:
zephyr_sources_ifdef()

instead of
zephyr_library()
zephyr_library_sources_ifdef()

This results in a messy Zephyr lib as described in: #8825
One reason for drivers to use the first approach is because an empty
Zephyr library results in a CMake build failure which again leads to
twister issues when just enabling a driver and build for all known
boards and then process the DTS result.
Secondly, a CMake build failure prevents the user from launching
menuconfig and disable the driver that creates the empty library.
See #9573 for extra details.
This commit verifies all Zephyr libraries, and if a library is found to
have no source files it will be excluded from the build and a warning
will be printed to the user.
Printing a warning instead of a hard failure ensures that:

menuconfig can still be opened
CMake does not fail which allows twister to advance in the test case
Makes it possible to cleanup CMakeLists driver files

Signed-off-by: Torsten Rasmussen<EMAIL_ADDRESS>

An empty Zephyr lib on master will result in the following CMake error:
CMake Error at ../../cmake/extensions.cmake:416 (add_library):
  No SOURCES given to target: drivers__regulator
Call Stack (most recent call first):
  ../../cmake/extensions.cmake:393 (zephyr_library_named)
  ../../drivers/regulator/CMakeLists.txt:4 (zephyr_library)

this PR changes that into the following warning, and excludes the library from the default ALL target.
CMake Warning at ../../CMakeLists.txt:699 (message):
  No sources in Zephyr library drivers__regulator, excluding target from
  build.

PR is created based on https://github.com/zephyrproject-rtos/zephyr/pull/34232 discussions.

@gmarull FYI, related to the issue you were seeing with the out of tree driver


Share test functions between e2e and multicluster e2e package

Main changes:

Export some functions from /test/e2e.TestData so that they can be reused by multi-cluster e2e pkg.
Changed some util functions' receiver from k8sUtils to TestData so that they can be reused by multi-cluster e2e pkg.
In multi-cluster e2e pkg, instantiate a new MCTestData which has copies of TestData of each cluster, instead of creating an entirely new TestData struct.

Signed-off-by: Yang Ding<EMAIL_ADDRESS>

Codecov Report

Merging #3424 (c310540) into main (431291f) will decrease coverage by 6.60%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3424      +/-   ##
==========================================
- Coverage   42.41%   35.80%   -6.61%
==========================================
  Files         200      106      -94
  Lines       24296    14551    -9745
==========================================
- Hits        10305     5210    -5095
+ Misses      12929     8852    -4077
+ Partials     1062      489     -573

Flag
Coverage Δ

integration-tests
35.80% <ø> (?)

unit-tests
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/agent/flowexporter/exporter/certificate.go

pkg/apiserver/handlers/featuregates/handler.go

pkg/apiserver/handlers/webhook/mutation_labels.go

pkg/agent/controller/networkpolicy/allocator.go

pkg/clusteridentity/clusteridentity.go

...ticluster/commonarea/remote_common_area_manager.go

pkg/agent/multicast/mcast_socket_linux.go

...ulticluster/cmd/multicluster-controller/options.go

pkg/controller/egress/controller.go

pkg/ovs/openflow/ofctrl_builder.go

... and 296 more

/test-multicluster-e2e

/test-all

/test-all-features-conformance

/cc @enhaocui as this might conflict with #3286. Specifically, that PR might need to be rebased on the current one

/test-all

/test-e2e /test-multicluster-e2e /test-windows-e2e

/test-all /test-multicluster-e2e

/test-all /test-multicluster-e2e

/test-e2e

Hi @tnqn Could you help to take a look at this PR, let us know if there is any other test need to be verified beside test-all and test-multicluster-e2e? thanks.

Rebase and resolved merge conflicts /test-all

/test-all /test-multicluster-e2e

Rebase and resolved merge conflicts /test-all /test-multicluster-e2e

Rebase and resolved merge conflicts /test-all /test-multicluster-e2e

I didn't see test being triggered, trigger them again.
/test-all
/test-multicluster-e2e

/test-multicluster-e2e

/test-multicluster-e2e

/test-all /test-multicluster-e2e

In commit message title: s/andd/and/

/test-all /test-multicluster-e2e

/skip-integration change doesn't affect integration test


[Quantum] [DRAFT] Left align histogram

The left-align string-formatting option "<" was applied to histogram rows in the job-results console output.

This checklist is used to make sure that common guidelines for a pull request are followed.

Quantum


Update azure sdk to latest version

Azure SDK latest version fixes couple of bug fixes and adds transactional MD5 to stageblock API

The diff of the go.mod still looks odd.  There are some strange extra dependencies and the version is still 0.0.0.  I have to say I'm still learning go mod so not sure why that is!

The diff of the go.mod still looks odd. There are some strange extra dependencies and the version is still 0.0.0. I have to say I'm still learning go mod so not sure why that is!

 I'm also still trying to figure out go mod, not sure about additional strange dependencies.

Well if you think you've got the new code then we should merge this as-is and worry about go mod later!

OK. I'm happy for you to merge this when you are satisfied :-)

go.mod has some updates related to tools like lint, mod, errcheck. I don't know why,  as far as azure changes concerned, it pull all changes as part of v.0.2.0 which is the tip today and locally tested changes, I believe its safe to merge.

OK I'll merge this now then :-)


Smoothen the interface

Description
I'm going to call endstate correction from asfe. This PR, I will try to smooth the interface to make it easier to be called and easier to read.

I'm changing the protocol.lam from pd.series to float and it makes things easier.

Todos
Notable points that this PR has either accomplished or will accomplish.

[ ] TODO 1

Questions

[ ] Question1

Status

[ ] Ready to go

Codecov Report

Merging #59 (65efe32) into main (32ba18f) will not change coverage.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files

@wiederm Initially, I thought that I need a more complex interface, now I think a float is enough for this purpose.


Route Segmentation

In looking at the LCWIPs I have encountered several with segmented routes. For example West of England Combined Authority has most of its routes split into segments with some description of what will happen to each segment:

This also include in places alternatives where the route could go one or more ways depending on future information. There is also the question of pre-existing infrastructure. So we might have a route which is conceptually 1 route, but has multiple segments of different styles of path, that might be existing, or new, or existing but to-be-upgraded.
So I think there is a need for us to consider the UX and data format required to capture these sorts of things. We should be able to define a route and segments of that route. We should also allow for segments to be optional with alternatives.
This raises another question of conceptually distinct routes which share segments with another route. This is nicely exemplified by an example in Peterborough where there are 3 routes noted which all share the majority of their route, as seen here:

So additionally we may want to support segments being shared by different routes. At the very least a way to visually show multiple routes along the same path might be necessary.
All of these probably want some discussion with Sustrans and ATE folks with more experience in the field.

In the first WECA example, somebody could individually map each of those segments and fill out the descriptions, or map one big long piece, use the split tool, and fill out the description for each segment.
Per segment, maybe we have a "is this the preferred/main option or an alternative?" question. Do we need to ask people what it's an alternative to or fill that out in the data, or can we can figure it out later manually or algorithmically?
For the last shared segment question, can we just map the shared segment once and describe it adequately? Is the problem that it might belong to multiple sub-schemes at a time?
In general, can we ask people to map segments exactly once and fill out enough detail on them? Do we need as output any concept of the full route, or can we stitch that together by joining adjacent segments?

These are all great questions and I'd rather ask ATE folks and the people who are gonna be mapping what they reckon than answer them myself 😅

In a call with Robin, Katie, Andre, and I, I think we're settling on the approach of just mapping the entire route as one object, then mapping the entire alternative, and ticking a checkbox to indicate it's an alternative. No splitting or figuring out common segments. This lets us calculate the metric of total length of the planned network by just filtering out is_alternative=false, and reduces the decisions the mapper has to make about where/how to split.


Device Name is not displaying on M5StickC [Bug]:

What happened?
Device name is not showing on the screen of the M5StickC, but it does on M5StickC Plus.  Everything else seems to be working fine.
Version
3.0.1
Distribution
Docker
OS
Linux
What browsers are you seeing the problem on?
No response
If applicable, What Listener Clients are You Using?
M5 Stick
TallyArbiter configuration
No response
Relevant log output
No response
Error stacktrace (if applicable)
No response

I'll have a look at the code and see if I can find the issue.

@commputethis are you compiling the M5StickC code using the Arduino IDE? Or are you downloading and flashing the bin file to the device?

I'n actually having the opposite problem - the latest downloadable bin of the m5stickc build works fine after flashing, but flashing the bin to the m5stickc plus seems to work in regards to the AP and connection, but the screen is just a garbled mess. redownloaded, reflashed, confirmed issue still existed on the plus but displays fine on the regular m5stickc.

The device name is shown. This was earlie fixed. One key thing is the that the image is hardware version specific so using a m5stickc plus bin on a m5stickc doesn't work. I haven't tracked backward to when it was fixed but it works on the listener built on v3.0.10 tag.


Provide IM documentation as top level service

Summary
Provide IM documentation as top level service

Related issue : #405

Hi @gwarf,
I have addressed your suggestions.

Hi @micafer OK, I will look and resolve the discussions so that we can merge.
(Thanks for the manual fixes, but for the record I created comments as suggestions so that you could include them in a click and have the discussions be resolved automatically.)

@thebe14 any comments on this one?

I'd like to see a better overview of that IM is, the top page should contain a one-paragraph "What is it?" that resumes that.
Lift content from here https://docs.google.com/document/d/1ycq076_SQ6pIH3MabruDpCviIERWVQ_l/edit#heading=h.gu82qyy9aq1r
Then we need to find a better place for it than in the root. I just made some related changes in PR #409


[SPARK-32422][SQL][TESTS] Use python3 executable instead of python3.6 in IntegratedUDFTestUtils

What changes were proposed in this pull request?
This PR uses python3 instead of python3.6 executable as a fallback in IntegratedUDFTestUtils.
Why are the changes needed?
Currently, GitHub Actions skips pandas UDFs. Python 3.8 is installed explicitly but somehow python3.6 looks available in GitHub Actions build environment by default.
[info] - udf/postgreSQL/udf-case.sql - Scalar Pandas UDF is skipped because pyspark,pandas and/or pyarrow were not available in [python3.6]. !!! IGNORED !!!
...
[info] - udf/postgreSQL/udf-select_having.sql - Scalar Pandas UDF is skipped because pyspark,pandas and/or pyarrow were not available in [python3.6]. !!! IGNORED !!!
...

It was chosen as python3.6 for Jenkins to pick one Python explicitly; however, looks we're already using python3 here and there.
It will also reduce the overhead to fix when we deprecate or drop Python versions.
Does this PR introduce any user-facing change?
No, dev-only.
How was this patch tested?
It should be tested in Jenkins and GitHub Actions environments here.

Merged build finished. Test PASSed.

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

Test build #126468 has started for PR 29217 at commit c70e29f.

I reverted 826689a36efbf1b73a0744824080ac01da3a5f60 here and get it back again to confirm IntegratedUDFTestUtils and pandas related tests are not being skipped.

Merged build finished. Test PASSed.

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

Test build #126472 has started for PR 29217 at commit d72c4c1.

It is now tested properly: https://github.com/apache/spark/runs/905415145
...
[info] - udf/udf-inner-join.sql - Scalar Pandas UDF (527 milliseconds)
...
[info] - udf/udf-special-values.sql - Scalar Pandas UDF (747 milliseconds)

Test build #126472 has finished for PR 29217 at commit d72c4c1.

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

Test build #126468 has finished for PR 29217 at commit c70e29f.

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

Merged build finished. Test FAILed.

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

retest this please

Merged build finished. Test FAILed.

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

Test build #126483 has started for PR 29217 at commit d72c4c1.

Merged build finished. Test PASSed.

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

Test build #126483 has finished for PR 29217 at commit d72c4c1.

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

Merged build finished. Test PASSed.

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

I think it's okay. Installing Python 3.8 in GitHub Actions overwrites python3. So, we won't face the tests being skipped even when we backport as long as the explicit Python 3 installation.
I wouldn't say this is a GitHub specific issues. It was python3.6 in the codes for Jenkins environment when I added. It was to explicitly pick a Python version but we're already using python3 to pick Python 3 in many places in our script.
It fixes the issue in GitHub Actions but also keep the codes consistent with other places. Plus, it will reduce overhead of maintenance when we drop or deprecate minor Python version.

Thank you @dongjoon-hyun

Just a question. Is this used in R test, too?

Nope it isnt. I believe this is irrelacent with R test results.

Nope it isnt. I believe this is irrelevant with R test results.

Thank you for confirmation~


[List] Drag preview not covering full width for large rows

What package is this for?

[x] React
[ ] Angular

Describe the bug
The drag preview is not covering full width for large rows. This is true for all components using the List.
To Reproduce
Steps to reproduce the behavior:

Go to https://next.carbon-addons-iot-react.com/?path=/story/1-watson-iot-hierarchylist--with-nested-reorder
Enable knob isLargeRow
Drag an item
Notice how the Drag preview (the blue line) and Drop target indications (blue border around other items that accepts drop) are not full width

Please create a reduced test case in CodeSandbox:
https://codesandbox.io/s/github/carbon-design-system/carbon-addons-iot-react/tree/next/packages/react/examples/codesandbox

Expected behavior
Blue line is full width
Environment/versions:

OS: [e.g. MacOS, Windows]
Browser: [e.g. chrome, safari]
carbon-addons-iot-react version: [e.g. v2.60.0]

Additional context
Screenshot from TableColumnCustomizationModal showing the same problem:

Specific timeline issues / requests
Do you want this work within a specific time period? Is it related to an
upcoming release?
NB: The core contributors will try to work with your timeline, but it's not
guaranteed. The earlier you make a request in advance of a desired delivery
date, the better!

@dianatran18 Just verifying with you that this is a bug right?

Yes that looks like a bug. It should span the full width like the other single row examples.


2.x client fixes

client interestChannel now evict older entries once new channel is available
AbstractClientChannel properly handle connection lifecycle

NetflixOSS » eureka » eureka-pull-requests #87 SUCCESS
This pull request looks good


Android Quit State not receiving notifications / notifee data

 await messaging().sendMulticast({
      tokens: [
        "e6tsH1DPTX6nQQaoMeflEn:APA91bHRqP0tm35YT4Psq3NFyfdswpS5oGMyvKXpGnM71ywvOreUniV6rgnYat8WKGYTSt5j6gOD7uYFKqPV7xBu5Lf4ybt2PdfjPJhoTKzmNDYr-gKYD385caL4D6cOHmz9YOb0M6O3",
      ],
      data: {
        notifee: JSON.stringify({
          body: "This message was sent via FCM!",
          android: {
            channelId: "default",
            actions: [
              {
                title: "Mark as Read",
                pressAction: {
                  id: "read",
                },
              },
            ],
          },
        }),
      },
      android: {
// Including notification will work but no data parsed from notifee
        notification: {
          priority: "high",
        },
        priority: "high",
      },
    });

Foreground and background works, but quit state on android doesn't. setting priority high on notiifcation will show in quit state but notifee no longer parses data, thus just showing an naked notification

fixed. damn this package needs a docs revamp.. will do it in my free time.

@Darren120 would you mind sharing how you managed to have Android data notifications in Quit Mode ?


#P18. As Participant, I want to sync my profile with my profile on Slack.

Doesn't this happen by default when enrolling to the app, or am I being daft? 🤔

Yes it does, but maybe they want to re-sync it if they changed something?


adds optional serde support for error struct

Signed-off-by: Sean Bruton<EMAIL_ADDRESS>

Thanks for your pull request.


[BUG] Light and dark theme switching.

Description
The switching between light and dark themes works fine on the home page. However, as soon as we navigate through sub-categories and try to switch the theme, the body theme takes more time to load than its div, resulting in asynchronous visuals.
https://github.com/rupali-codes/LinksHub/assets/139853292/5d1dfba9-e436-4ddb-ae62-ac89b7efc93f
the sub-categories.mp4 demonstrates the asynchronous switching.
Screenshots
No response
Any additional information?
No response
What browser are you seeing the problem on?
Chrome, Microsoft Edge
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)

@Sahil-106
I have assigned you the issue. Please proceed with it, and don't hesitate to tag any of the maintainers if you need any help.


haven

would be great to show the class how to use haven since many of the students might find this useful

I added resources but I think we could cover the basics in a lecture at some point


Update scalameta to 4.3.16

Updates org.scalameta:scalameta from 4.3.15 to 4.3.16.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalameta" } ]

labels: library-update, semver-patch

Codecov Report

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

@@           Coverage Diff           @@
##           master     #702   +/-   ##
=======================================
  Coverage   81.20%   81.20%
=======================================
  Files          78       78
  Lines        5197     5197
  Branches      139      139
=======================================
  Hits         4220     4220
  Misses        977      977

Continue to review full report at Codecov.

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


How can access mongodb remotely in mlab.com?

I tried  to connect mongodb  remotely mlab.com with laravel.
Mongodb version: 3.6
Laravel version: 5.2
    'mongodb' => [
        'driver'   => 'mongodb',
        'host'     => env('DB_HOST', 'localhost'),
        'port'     => env('DB_PORT', 27017),
        'database' => env('DB_DATABASE', ''),
        'username' => env('DB_USERNAME', ''),
        'password' => env('DB_PASSWORD', ''),
        'options' => [
            'database' => env('DB_DATABASE', '') // sets the authentication database required by mongo 3
        ]
    ],

I used this one.
In local, it works fine. but when access remotely, it says authenticaton failed.
How can i solve this issue?

@borysfranko11 @divine  did you find an answer to this problem?


Login page not loading : 504 Gateway Time-out

My actions before raising this issue

[yes ] Read/searched the docs
[yes ] Searched past issues

I am trying to host a cvat server on a machine to acces it over a network, the docker compose up seems to start the containers but i cannot acces it on the host or outside.
Also not sure why but if i try to docker compose up without giving a cvat version i will get an error response from the docker daemon that there is no such file or directory on the init-merged generated docker folder
Steps to Reproduce (for bugs)

1.git clone https://github.com/opencv/cvat.git
1.export CVAT_HOST=<host_ip>
1.CVAT_VERSION=v2.6.0 docker compose up -d
Expected Behaviour
accessing through http://host_ip:8080 and loading the ui
Current Behaviour

Get a page
504 Gateway Time-out The server didn't respond in time.

Operating System and version (e.g. Linux, Windows, MacOS):Ubuntu 20.04
Code example or link to GitHub repo or gist to reproduce problem:
Other diagnostic information / logs:
Logs from `cvat` container

-network : i am behind a proxy, i have set up the .docker/config.json to take it into account but i am unsure if i need to setup an env variable for cvat to point to it
I have then tried with pulling git version 2.6.0, and checked :
docker logs traefik
time="2023-09-26T17:33:48Z" level=info msg="Configuration loaded from flags."
time="2023-09-26T17:33:48Z" level=error msg="entryPoint \"websecure\" doesn't exist" routerName=grafana_https@file entryPointName=websecure
time="2023-09-26T17:33:48Z" level=error msg="no valid entryPoint for this router" routerName=grafana_https@file
time="2023-09-26T17:33:48Z" level=error msg="entryPoint \"websecure\" doesn't exist" routerName=grafana_https@file entryPointName=websecure
time="2023-09-26T17:33:48Z" level=error msg="no valid entryPoint for this router" routerName=grafana_https@file
time="2023-09-26T17:33:50Z" level=error msg="entryPoint \"websecure\" doesn't exist" routerName=grafana_https@file entryPointName=websecure
time="2023-09-26T17:33:50Z" level=error msg="no valid entryPoint for this router" routerName=grafana_https@file
time="2023-09-26T17:33:50Z" level=error msg="entryPoint \"websecure\" doesn't exist" entryPointName=websecure routerName=grafana_https@file
time="2023-09-26T17:33:50Z" level=error msg="no valid entryPoint for this router" routerName=grafana_https@file
time="2023-09-26T17:33:52Z" level=error msg="entryPoint \"websecure\" doesn't exist" entryPointName=websecure routerName=grafana_https@file
time="2023-09-26T17:33:52Z" level=error msg="no valid entryPoint for this router" routerName=grafana_https@file
time="2023-09-26T17:33:52Z" level=error msg="entryPoint \"websecure\" doesn't exist" routerName=grafana_https@file entryPointName=websecure
time="2023-09-26T17:33:52Z" level=error msg="no valid entryPoint for this router" routerName=grafana_https@file

But i am unsure why traefik cannot find any entry point, and i do not find in the documentation if there is a need for setting entrypoints manually.

1.git clone https://github.com/opencv/cvat.git
1.export CVAT_HOST=<host_ip>
1.CVAT_VERSION=v2.6.0 docker compose up -d

You are trying to use the compose configuration from the develop branch (v2.7.2+) to run v2.6.0. This will most likely not work.
The versions must be the same.
The first step is to make sure that the cvat_server container is started and running


Bellman-ford Algorithm

Best algorithm for finding shortest path having negative edges.

Hey @Paawan9700  please assign me this task , i am new to open source and would like to make my first contribution.