multiple enhancements

I used vagrant-scaleio to learn about multi-node Vagrant deployments and more. :)
While doing so I added some features and improvements:

added gateway with installation manager
added Light Installation Agent to nodes
typo fixed in installation files
heterogeneous box types: "chef/centos-6.6" and "chef/centos-7.0"
added update script
cleaned Vagrantfile
combined ScaleIO installation files
independent from minor version changes

Cheers, Chris

Good changes in here.  I'd like to see them merged!  With the latest CoprHD, the Gateway needs to be running in order to add a ScaleIO Storage Provider/System, so installing the GW is required if you want to use CoprHD+ScaleIO.  I'd probably run the GW on MDM1 and not install another VM, but that's just me.  :)


Added new exercise: Rail Fence Cipher

closes #922

Can you remove the platform specific (non-exercism) files that start with .DS_Store?

Thank you! This is a great addition :)

@SleeplessByte Thanks! Can you assign me #916?

Yes. Comment in that issue, so your name shows up in the assignees field.
Do you have Twitter? If yes, I'd like to shout you out for all the work you've been doing.

Sure, my Twitter account is @lpizzinidev
Thanks, I appreciate this 😄


Take backticks into account when removing links that are the same

[`tracing`][tracing] could just be [`tracing`].

Is this specific to rustdoc ? The following produces two different links:
[`a`][a] or [`a`].

[a]: https://github.com
[`a`]: https://docs.rs

And since intraconv doesn't have a lot of information about the links and their relationship between each other, I don't think this is feasible.

Oh I see - you don't know whether [a] is a reference link ([a]: example.com) or a shortcut link to the rust path a. Yeah I can see how that's hard.


fix: 27054 Conversations do not load if you interrupt the Internet connection when logging in

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/27054
PROPOSAL: https://github.com/Expensify/App/issues/27054#issuecomment-1717447113
Tests

Open a New Expensify app
Log in with HT account
Turn off the internet for 5 seconds when the download starts
Turn the internet back on
Verify that the app downloads the entire conversation history if online

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Open a New Expensify app
Log in with HT account
Turn off the internet for 5 seconds when the download starts
Turn the internet back on
Verify that the app downloads the entire conversation history if online

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://github.com/Expensify/App/assets/113963320/3d11991d-7c3f-4b82-a099-a874022a4bae

Mobile Web - Chrome

https://github.com/Expensify/App/assets/113963320/cd9b9f00-3b03-4ffc-959d-93174152ac34

Mobile Web - Safari

https://github.com/Expensify/App/assets/113963320/cbf18be0-9b45-4d3d-b30b-8424c1f61775

Desktop

https://github.com/Expensify/App/assets/113963320/0c942133-7bc1-4528-ba35-de2b697173cc

iOS

https://github.com/Expensify/App/assets/113963320/c8a5af4e-e3ed-4282-8a5f-1f43fcf0306d

Android

https://github.com/Expensify/App/assets/113963320/c8a5af4e-e3ed-4282-8a5f-1f43fcf0306d

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/deetergp in version: 1.3.72-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/thienlnam in version: 1.3.72-11 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Vue: Cannot create new workspace using preset due to missing @nx/js

Describe the bug
Vue preset fails to install @nx/js before creating the app (which then fails)
To Reproduce

Run npx create-nx-workspace with --preset=@nxext/vue
Give an app name when asked
Observe:  >  NX   Cannot find module '@nx/js' followed by a stack trace starting at create-application-files.js
You get a workspace without the app

Expected behavior
A new workspace containing the named app.
Additional context
This happens whether or not nx is installed globally

I'll close this because of the deprecation of the Vue plugin in favor of the official @nx/vue plugin


Copy the customized CRaC dockerfiles if they exist in the root

Previously, we allowed users to create Dockerfile and/or DockerfileCracCheckpoint in the root of their project and we then would attempt to use these for the image generation.
This doesn't work.  The Docker plugin requires all Docker content to be in the same file tree.
This PR copies checks for the existence of these files, and copies them to the correct location instead of building the dockerfiles.
Fixes #678

@melix can we merge this and release a new patch of the gradle plugin 🙏🏻


TZ ENV not avaialbe

Description of the feature
When I set DB_DUMP_BEGIN=0020, I was thinking it will be at 20 minutes past midnight my local time, I was surprised the next day it was not. It is on GMT local time, not mine.
There should be a TZ env set to have the dumping relative to that.
Benftits of feature
Makes dump scheduling more understandable and easy to configure
Additional context
N/A

See the README where it talks about the "other" variables available with the upstream base images. You'll find lots more switches to flick, including TIMEZONE


Clarify that hexadecimal literals are assumed to be positive values.

The documentation on numeric literals states the following:

The type of an integer literal is determined by its suffix as follows:
If the literal has no suffix, its type is the first of the following types in which its value can be represented: int, uint, long, ulong.

Now consider the literal 0x80000000. This literal does not have a suffix and the bit pattern fits into a 32-bit integer so this documentation may imply to some readers that this will be treated as a signed integer. (In other languages, PowerShell for instance, this kind of literal is indeed interpreted to be the same as System.Int32.MinValue.)
In C# the apparent rule is that hexadecimal literals are always assumed to be positive values, meaning the positive value 0x80000000 must be interpreted as an unsigned int since it is too large to fit into a signed integer.
This doesn't seem to be clearly documented and it would be good to make this more explicit.
---#### Document Details⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.* ID: 3a22464d-b60c-36c0-e4e8-b209a33b0219* Version Independent ID: cb500323-82a3-09ea-0468-dd16c9e13675* Content: Integral numeric types - C# reference* Content Source: docs/csharp/language-reference/builtin-types/integral-numeric-types.md* Product: dotnet-csharp* Technology: csharp-language-reference* GitHub Login: @BillWagner* Microsoft Alias: wiwagn

A note: any (decimal, hexadecimal, and binary) literal is assumed to be a positive value.

Thanks for noting this @Treit and thanks for the fix @pkulikov


Package manager icons

Is your feature request related to a problem?
N/A
Describe the solution you'd like
It'd be cool if it'd show icons next to the package managers, like on the Biome website https://biomejs.dev/guides/getting-started/#installation
Describe alternatives you've considered
Well, not having icons, but it's not as nice, right
Additional Context
No response

Oh, I love the idea, this looks super great!
Internally, this component relies on the Starlight built-in <Tabs> component and only builds on top of it to add syncing between the tabs. Unfortunately, the built-in component doesn't support this feature and only accepts a basic string as a tab label.
Replacing the built-in component with a custom one that would literally be 90% the same just to render an extra icon seems meh, so instead I just opened a new feature request in Starlight to add a new icon prop to the <TabItem> component that would accept the name of an icon from the Starlight icon set and render it next to the label.
If this is something of interest (I personally really like the idea), this would be a fairly easy addition, and I already have an unrelated opened PR that adds icons for npm, yarn, and pnpm. We could also add bun too and then this issue would be as good as solved.

All the pre-requisites Starlight PRs have been merged and released and the feature is now available in the new v0.4.0 of the package.

Thanks again for the great feature request :raised_hands:

Really cool, awesome work!


Cannot Access Newsletter Page

Hey everyone! First of all, as this is my first issue here, thank you for making this repository available for everyone, it's a pretty cool resource to help learning the ASP.NET Core framework 😅
I've cloned this repository, and changed the appsettings.json to use SqlServer. When I run the project, the database is succesfully created. However, as I'm exploring the project, when I click the "Newsletter" tab in the Admin Dashboard, I get this error:

Any thoughts on what happened? The only changes I've made is in the appsettings.json file, and the database appeared to be created succesfully.

First, check if you need to update Blogifier.Core nuget package - there should be migration adding columns to newsletters table.
Blogifier checks for migrations in the program.cs on app start and runs migrations automatically, so you can check with debugger if it finds any new migrations and if there any issues executing them.

Fix been applied with latest update, newsletter migration script should work with SQL Server now.

That does it. Thank you for the quick support! 😊


No error message when adding invalid log entry

When empty log entry is entered, there is no handling of the error, so the program just does nothing.

Error msg is only displaying on terminal


fixing filtered update performance

update with regex filter, matching 83 packages of 210, resulted in runtime of about 30 minutes, instead of the expected cca 30 seconds of full update
most of the time was spent in the filter function, constructing and compiling the regex for each nuget package dependency
issue was completely fixed by extracting the regex object creation to be done only single time

Thanks for looking into this, always wondered why this is slower then full update

OK, I have zero idea what happened in the Travis CI ...
Error in '/usr/bin/mono': realloc(): invalid next size: 0x00000000025e0a70


How to change an attendance status correctly?

I am trying to change my attendance status. I want to respond Going/Maybe/Decline to the specific, existing event.
I want to change only MY status, not other guests.
What's the proper way to do it?
Either nothing's changed or error:
https://github.com/builttoroam/device_calendar/issues/249
I noticed https://github.com/builttoroam/device_calendar/pull/276
This is what I do(all given data is correct for sure):
        final event = Event(
        model.calendarId,
        allDay: model.allDay,
        attendees: _attendees(existingAttendees),
        availability: availability,
        description: model.description,
        end: model.endDate,
        eventId: model.eventId,
        recurrenceRule: recurrenceRule,
        reminders: reminders,
        start: model.startDate,
        title: model.title,
      )..location = model.location;

      final result = await _calendarPlugin.createOrUpdateEvent(event);

  List<Attendee> _attendees(List<AttendeeModel> attendees) {
    return attendees
        .map(
          (item) => Attendee(
            emailAddress: item.emailAddress,
            isOrganiser: item.isOrganiser,
            name: item.name,
            role: AttendeeRole.None,
          )
        )

OK, for Android I used #276. It works fine. For iOS seems impossible now. Going to create additional func using https://developer.apple.com/documentation/eventkitui/ekeventeditviewcontroller


Bugfix: wrong design on error message when searching for DAO with valid ethereum address

Acceptance Criteria

The error message styling for when a valid Ethereum address is inputted that is not a valid Fractal DAO should match the error message styling for when an invalid Ethereum address is inputted.

Acceptance Criteria

When a


Bitcoin transaction not found on insight

Hi
I have sent BTC from my copay wallet on 19.12 and it still is not confirmed until now.
Today the Transaction is not found any more on insight blockchain.
(Transaction: https://insight.bitpay.com/tx/e6711761b06744676db33fcea95ec3da13ca2d205a454007b330b1a499b54f11)
I have payed separate 12.33% fee for this Transaction - much much more than in the past monts (below 3%)
Copay Shows me text: "This Transaction amount is too small compared to current Bitcoin network fees. Spending these funds will ned a Bitcoin Network fee cost comarable to the funde itselfl" and info text that "Transaction is not available at the Moment"
And now the coins are neither on on my site not on Receiver site!
Is there any possibility to get my coins back to my wallet?
Please fix this issue.

Also same Problem with Transaction
https://insight.bitpay.com/tx/b431208a945d9272815331d5f15f0ad33b6903efe526e645c3dbfbd59da5d1c4

Transaction (with 37.9% fee)
https://insight.bitpay.com/tx/b431208a945d9272815331d5f15f0ad33b6903efe526e645c3dbfbd59da5d1c4
TRANSACTION NOT FOUND IN BLOCKCHAIN


cookie not send with jquery ajax

1,set cookie before send ajax
$.cookie("example", "foo");
2,send ajax
$.ajax
url:	...
type:	"GET"
headers: ...
data:...
3,cookie "example" not sent,but cookie set by server has sent
4,alert document.cookie ,"example" is there,but server cookie not show up in the alert
does WebViewJavascriptBridge store cookie somewhere else?
how to send a cookie from the client

Hi @vontio,
Without a repro I won't be able to help you :(
If you create a failing test then I will definitely give you a hand (see https://github.com/marcuswestin/WebViewJavascriptBridge/blob/master/Tests/WebViewJavascriptBridgeTests/BridgeTests.m and https://github.com/marcuswestin/WebViewJavascriptBridge/blob/master/Tests/WebViewJavascriptBridgeTests/echo.html).
I'll close this in the meantime since there's nothing I can do. Feel free to reopen with a repro or more information.
Cheers!


Filters don't show any labels

As you can see in the attached image, if I have multiple filters then there's no way to differentiate between them, there's no label or anything to indicate what each one does.
Furthermore, if I select a value for one filter and then click again to change it, the dropdown menu doesn't open, I have to click on the clear button to make it work again.

Hi @amrnn,
This is fixed for our next release (1.2.1), which you can test on the 1.2 branch.


Add Year slider to Filters & Sorting Options

enhancement request:
add a year slider (similar to Duration, Size, Resolution, Star sliders) to Filters & Sorting Options.
It would be great to have a slider so that you can select a range of years to filter on (e.g. 2015 to 2017).  the slider could start at the minimum year of your hub and end at the max year.

I'm thrilled to hear someone is using the year feature 😅
Adding a slider for it is doable, I'll be happy to accept a PR (code contribution) for this feature. In the codebase there's already a pattern for adding sliders, and it wouldn't be too complicated.
I'm currently a bit busy for the next few months. Afterwards I'll want to do some work on face recognition. I'll keep this suggestion open for future development 🤝

@whyboris I am working on this one, but getting some errors I cant figure out, maybe you can take a look when you get a chance. I tried updating to most recent node js and installing. Im not familiar with typescript so it might be something obvious im missing.
Generating browser application bundles (phase: building)...node/main-ipc.ts:73:15 - error TS2339: Property 'openItem' does not exist on type 'Shell'.
73         shell.openItem(path.normalize(fullFilePath)); // normalize because on windows, the path sometimes is mixing \ and /
~~~~~~~~
node/main-ipc.ts:156:17 - error TS2339: Property 'openItem' does not exist on type 'Shell'.
156           shell.openItem(savePath);
~~~~~~~~
node_modules/electron/electron.d.ts:6642:21 - error TS2694: Namespace 'NodeJS' has no exported member 'Require'.
6642     require: NodeJS.Require;

Thank you for working on this 😁
Try merging in #648 (I'll be putting it on the main branch soon) - this has the latest Electron and fixes the openItem API change: https://github.com/whyboris/Video-Hub-App/pull/648/files#diff-0b4a13d876020b09b600e6a8fb04f755f6d531ecb9c9a7335510da545bbe9d7bR73

@whyboris quick question on desired behavior for this.
The year is a bit unique in that people will have to add the year to their videos, they might have a huge amount of videos that have no value for this attribute.
The way I have it currently is that the min value on the slider is the lowest year they have in their library with max being the highest.
But this means that turning on this year filter immediately filters to only the videos that have set a value for the year.
Any thoughts on that?

I'm unsure how the app should behave 😅
It might make sense to not show any videos that are not already tagged 🤔 but I'm open to any other alternative you propose.
One benefit of hiding videos - is that I think that's the easiest behavior from the code perspective (right?), and also it seems easy to grasp from the user's perspective 🤔
I'm open to suggestions for anything different 🤝

Yeah I like the hiding approach because it limits the slider to only the available years. Rather than sliding from "Year 0" all the way to 2021 😅


WSL extension "open folder in container" results in error "bad option: --ms-enable-electron-run-as-node"

Type: Bug

Create a dockerfile as "FROM python:3" in a test folder.
open the folder is VSCode Insiders (windows)
now using the MS WSL extension choose "reopen in container"
select "from existing dockerfile"

log results:
C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe: bad option: --ms-enable-electron-run-as-node
Exit code 9

Note that all existing WSL based projects show similar results. This is just an example of how to reproduce. This also worked correctly prior to today's update.
VS Code version: Code - Insiders 1.86.0-insider (fb769554405bee9be16e21ceb0a496bd29126941, 2024-01-09T09:57:14.563Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12 x 2592)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
31.77GB (7.20GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (41)

Extension
Author (truncated)
Version

armview
ben
0.4.6

gotemplate
cas
0.4.0

gitlens
eam
14.6.1

go
gol
0.40.1

vscode-graphql-syntax
Gra
1.2.2

azure-pipelines
ms-
1.228.0

azure-dev
ms-
0.8.0

vscode-azureappservice
ms-
0.25.1

vscode-azurecontainerapps
ms-
0.6.1

vscode-azurefunctions
ms-
1.13.1

vscode-azureresourcegroups
ms-
0.8.3

vscode-azurestaticwebapps
ms-
0.12.2

vscode-azurestorage
ms-
0.15.3

vscode-azurevirtualmachines
ms-
0.6.5

vscode-bicep
ms-
0.24.24

vscode-cosmosdb
ms-
0.20.0

vscode-docker
ms-
1.28.0

csharp
ms-
2.14.8

vscode-dotnet-runtime
ms-
2.0.0

isort
ms-
2023.11.13191009

python
ms-
2023.23.13541005

vscode-pylance
ms-
2023.12.1

jupyter
ms-
2024.1.2024010901

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

remote-containers
ms-
0.330.0

remote-ssh
ms-
0.107.1

remote-ssh-edit
ms-
0.86.0

remote-wsl
ms-
0.81.8

vscode-remote-extensionpack
ms-
0.25.0

azure-account
ms-
0.11.6

azurecli
ms-
0.5.0

live-server
ms-
0.4.13

remote-explorer
ms-
0.4.1

remote-server
ms-
1.5.0

vscode-node-azure-pack
ms-
1.2.0

azurerm-vscode-tools
msa
0.15.11

LiveServer
rit
5.7.9

jinja
who
0.0.8

Full output:
[8572 ms] Dev Containers 0.330.0 in VS Code 1.86.0-insider (fb769554405bee9be16e21ceb0a496bd29126941).
[8571 ms] Start: Run: docker version --format {{json .}}
[8750 ms] {"Client":{"Platform":{"Name":""},"CloudIntegration":"v1.0.31","Version":"20.10.23","ApiVersion":"1.41","DefaultAPIVersion":"1.41","GitCommit":"7155243","GoVersion":"go1.18.10","Os":"windows","Arch":"amd64","BuildTime":"Thu Jan 19 17:43:10 2023","Context":"default","Experimental":true},"Server":{"Platform":{"Name":"Docker Desktop 4.17.1 (101757)"},"Components":[{"Name":"Engine","Version":"20.10.23","Details":{"ApiVersion":"1.41","Arch":"amd64","BuildTime":"Thu Jan 19 17:32:04 2023","Experimental":"false","GitCommit":"6051f14","GoVersion":"go1.18.10","KernelVersion":"<IP_ADDRESS>-microsoft-standard-WSL2","MinAPIVersion":"1.12","Os":"linux"}},{"Name":"containerd","Version":"1.6.18","Details":{"GitCommit":"2456e983eb9e37e47538f59ea18f2043c9a73640"}},{"Name":"runc","Version":"1.1.4","Details":{"GitCommit":"v1.1.4-0-g5fd4c4d"}},{"Name":"docker-init","Version":"0.19.0","Details":{"GitCommit":"de40ad0"}}],"Version":"20.10.23","ApiVersion":"1.41","MinAPIVersion":"1.12","GitCommit":"6051f14","GoVersion":"go1.18.10","Os":"linux","Arch":"amd64","KernelVersion":"<IP_ADDRESS>-microsoft-standard-WSL2","BuildTime":"2023-01-19T17:32:04.000000000+00:00"}}
[16876 ms] Start: Run: C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe --ms-enable-electron-run-as-node c:\Users\jrstrome\.vscode-insiders\extensions\ms-vscode-remote.remote-containers-0.330.0\dist\spec-node\devContainersSpecCLI.js templates apply --workspace-folder C:\Users\jrstrome\AppData\Local\Temp\tmp-output-dir-1704821043622 --template-id ghcr.io/devcontainers/templates/docker-existing-dockerfile:latest --template-args {} --features [] --tmp-dir C:\Users\jrstrome\AppData\Local\Temp\tmp-dir-1704821043622
[16918 ms] C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe: bad option: --ms-enable-electron-run-as-node
[16927 ms] Exit code 9

The same is happening for me on OSX bad option: --ms-enable-electron-run-as-node
[127030 ms] Start: Run: docker version --format {{.Server.APIVersion}}
[127076 ms] 1.43
[127108 ms] Start: Run: /Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Code - Insiders Helper (Plugin).app/Contents/MacOS/Code - Insiders Helper (Plugin) --ms-enable-electron-run-as-node /Users/dnshio/.vscode-insiders/extensions/ms-vscode-remote.remote-containers-0.329.0/dist/spec-node/devContainersSpecCLI.js read-configuration --workspace-folder /Users/dnshio/coolproject --log-level debug --log-format json --config /Users/dnshio/coolproject/.devcontainer/devcontainer.json --include-merged-configuration --mount-workspace-git-root
[127191 ms] /Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Code - Insiders Helper (Plugin).app/Contents/MacOS/Code - Insiders Helper (Plugin): bad option: --ms-enable-electron-run-as-node
[127193 ms] Exit code 9

seems related to: https://github.com/microsoft/vscode/commit/fb769554405bee9be16e21ceb0a496bd29126941

@deepak1556 I will remove '--ms-enable-electron-run-as-node' as option from the scripts in WSL, but it might be better to only show a warning, and not result in an error.

The WSL extension does not use ms-enable-electron-run-as-node. It's with dev containers...

/fixedWith https://github.com/microsoft/vscode-remote-containers/pull/714
Please try with the latest pre-release of the containers extension.

Fixed in Dev Containers 0.331.0-pre-release.

Thanks for the speedy fix! Upgrading Dev containers to the pre-release version (today) fixed the issue for me.

Dev Container v0.331.0 and Nightly VSCode update has resolved this for me as well.

Had same issue - switching to pre-release version of extension also fixed it for me. Thx.

wow I almost lost a day of work due to this... started to fail from one moment to the other...
time to...
"update.enableWindowsBackgroundUpdates": false

never again.

@bandinopla Sorry to hear that, note that the setting you mention doesn't turn off automatic updates, it only changes how updates are applied on Windows. The setting to turn automatic updates for VS Code itself off is "update.mode": "none".
If you want to give the new version another try, make sure you also update the Dev Containers extension to its latest version. (This should have happened automatically, but automatic updates for extensions can also be turned off in the settings.)

For anyone stumbling on this after applying an update, sometimes all you need to do is go to the extensions tab, check if 'reload required' for the extension exists, if so, click on it to reload VS Code. I ran into this issue after a recent sudo apt-get upgrade, and just need to reload VS code after this error came up, giving time for the extension to get up to date.
Get:2 https://packages.microsoft.com/repos/code stable/main amd64 code amd64 1.86.1-1707298119 [99.8 MB]
Preparing to unpack .../0-code_1.86.1-1707298119_amd64.deb ...


Remove this package

Deprecated in https://github.com/ijnek/soccer_object_msgs/pull/13, (released in https://github.com/ros/rosdistro/pull/35101).
Should:

[ ] deprecate in I-turtle
[ ] remove in J-turtle


Play again not working

getting issue when trying to play again same file.

@bilawal-liaqat bhai, can you explain the issue further.

What issue are you getting?
Is the file you are trying to play is local or remote?
If possible, provide with some sample project, I'll try to help if I could.


Dynamically Changing 'displayInput' Option

I am having trouble with displayInput updating correctly. The code I have written has two knobs within each other. and as you change the outer knob the value should show. It does not however. The code can be found here. In an unrelated note, of which I really haven't explored, the font is of different sizes for the 2 knobs.

The way you wrote it you're trying to modify the HTML input element only. Look at the knob documentation in the 'Hook' section.  Functions like change/release get certain things passed to them. And you probably want to use 'this.o' -- see docs.


fix(nargo): Prevent errors when compiling workspaces including libraries

Description

Problem*

Resolves #2608
Summary*
We're currently not being explicit in how we handle different package types which results in unwanted behaviour (We only distinguish between contracts vs binaries, but not libraries).
This PR adds an explicit match to handle different package types. Due to #2608, I've made calling a command with an incompatible package type just skip it. We should handle this a little more intelligently once we have #2606
Documentation

[ ] This PR requires documentation updates when merged.

[ ] I will submit a noir-lang/docs PR.

[ ] I will request for and support Dev Rel's help in documenting this PR.

Additional Context

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

I'm still thinking this over. On first glance it feels wrong to silently skip things when people should be targeting specific packages they want to build.

We should skip over libraries when compiling the full workspace otherwise workspace features are unusable if you have a library in the workspace. imo we should only error if you're explicitly selected a library to compile i.e. nargo compile --package my-lib.
People should be able to compile their workspace in one command rather than needing to select packages individually.


Support all numerical instructions

Problem: we support very few numerical operations. We need moar.
Solution:

Supported all integer binary operations.
Namely add, sub, mul, div_s, div_u, rem_s, rem_u, and, or, xor, shl, shr_s, shr_u, rotl, rotr
Supported all integer unary operations.
Namely clz, ctz, popcnt
Supported all integer relational operations.
Namely eqz, eq, ne, lt_u, lt_s, gt_u, gt_s, le_u, le_s, ge_u, ge_s

Also added some support for some float numerical instructions, but for now it's a lost cause as Lean's implementation of Floats is utterly unsuitable for Wasm.

L
G
T
M


Invisible signature

Hello! May I ask if the signatures are all invisible?

The signatures are recognized and displayed by Acrobat as digital signatures. Currently you can't create a "visible" signature, see also #20.

Thank you! I hope you can do better.


How to use grapesjs-export plugin

Hi, thanks for this amazing project. I need to use this project along with GrapesJs export plugin. how can I do that?

@rainerregan Glad you like it.
It's not possible at the moment and the project is moving in a different direction. See #62 for more info.
What you can do:

Create the exported zip file from the created json files in the data folder without directly using the export plugin.
Fork Destack and enable support for the plugin yourself.


Disable main button drag and drop

hey,
once the upload button is loaded,
clicking and dragging any image on the same page will trigger a drag and drop functionality.
the cursor changes to a green plus sign, and the upload button changes to a drop area.
documentation doesn't seem to mention this, is it intentional?
is there any known way to turn this off, workaround or config setting? its undesirable for us.
thank you.

it works perfect! thanks a lot!


[MM-20529] Migrate 'components/file_attachment' module to TypeScript

Summary
This PR migrates components/file_attachment module and associated tests to TypeScript.
Some changes on component/file_preview were necessary.
Ticket Link
Fixes https://github.com/mattermost/mattermost-server/issues/13711

/update-branch

/update-branch


How can docusaurus' 404 page be adapted to other language pages?

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Description
How can docusaurus' 404 page be adapted to other language pages?
When I switch to other languages, such as French, I find that the 404 page cannot be switched to French, and the language switch box does not respond. Is there any way to make the 404 page change with the language switch?
Self-service

[ ] I'd be willing to address this documentation request myself.

Which 404 page gets served depends on your server. Most servers send /404.html whenever they receive a request to a nonexistent route. If you want to make it serve /fr/404.html, you have to configure your server to redirect all /fr/* to /fr/404.html. For example, check out https://github.com/facebook/docusaurus/blob/main/website/static/_redirects. This is going to be different for each server.
Maybe we can add this to the docs.

Which 404 page gets served depends on your server. Most servers send /404.html whenever they receive a request to a nonexistent route. If you want to make it serve /fr/404.html, you have to configure your server to redirect all /fr/* to /fr/404.html. For example, check out https://github.com/facebook/docusaurus/blob/main/website/static/_redirects. This is going to be different for each server.
Maybe we can add this to the docs.

What should I do if I don't use a hosting service?

What are you using?

What are you using?

I deployed docusaurus directly on my local machine without using a web hosting service.

Yes we should document this. Not easy though because we can't write a full guide to all the existing hosting platforms. But we can give a few generic hosting recommendations.
I also want to give a few tips like setting caching headers for assets, leveraging Webpack persistent caching etc... Not sure where to put that, the deployment page is already quite messy and long. Maybe we need a whole sidebar category just for deployment?

I deployed docusaurus directly on my local machine without using a web hosting service.

What does "deployed" mean, you must be running something on your local machine. docusaurus serve CLI is a possibility but there are many others including Apache, Nginx, arnish, http-server, serve...
You should read the doc of the tool you use, and see if it's possible to redirect 404 reponses to the /<locale>/404.html file.

Note that docusaurus serve is not particularly the best option, as we document here: https://docusaurus.io/docs/deployment#self-hosting
I don't think we expose any way to serve the localized 404 page, but that could be an interesting thing to add automatically. This is the lib we use under the hood and it supports rewrites: https://github.com/vercel/serve-handler

If you use something else, you'd have to figure it out because we don't provide support for anything else than docusaurus serve.

Yes we should document this. Not easy though because we can't write a full guide to all the existing hosting platforms. But we can give a few generic hosting recommendations.
I also want to give a few tips like setting caching headers for assets, leveraging Webpack persistent caching etc... Not sure where to put that, the deployment page is already quite messy and long. Maybe we need a whole sidebar category just for deployment?

I deployed docusaurus directly on my local machine without using a web hosting service.

What does "deployed" mean, you must be running something on your local machine. docusaurus serve CLI is a possibility but there are many others including Apache, Nginx, arnish, http-server, serve...
You should read the doc of the tool you use, and see if it's possible to redirect 404 reponses to the /<locale>/404.html file.
Note that docusaurus serve is not particularly the best option, as we document here: https://docusaurus.io/docs/deployment#self-hosting
I don't think we expose any way to serve the localized 404 page, but that could be an interesting thing to add automatically. This is the lib we use under the hood and it supports rewrites: https://github.com/vercel/serve-handler
If you use something else, you'd have to figure it out because we don't provide support for anything else than docusaurus serve.

OK, I understand. I use docusaurus. I will follow your advice and adjust my website according to the deployment section in the document. Thank you!
Maybe you can consider adding why you need a hosting service and the advantages of using a hosting service in the deployment document. This is just a suggestion.
Thanks for your reply!

The _redirects file is something specific to your host. Afaik only Netlify and Cloudflare Pages support this
Other hosts expose other ways to achieve the same, but you'll have to read your host docs for that. I don't know anything about GitPage. If you meant "GitHub Pages", it doesn't have a way to do server redirects so it's technically not possible on this host (I don't particularly recommend it, others are better).

The _redirects file is something specific to your host. Afaik only Netlify and Cloudflare Pages support this
Other hosts expose other ways to achieve the same, but you'll have to read your host docs for that. I don't know anything about GitPage. If you meant "GitHub Pages", it doesn't have a way to do server redirects so it's technically not possible on this host (I don't particularly recommend it, others are better).

Yes, I mean GitHub Pages. Thank you for letting me know it! I will keep it as it is now.


FEATURE REQUEST

Would you like have a tool or script added? Please include a link
Priv escalation tools like Watson - https://github.com/rasta-mouse/Watson and
juicy potato - https://github.com/ohpe/juicy-potato

Will add these to the roadmap and get them added! Thank you!

Added with 1.3 release


Bug: routing option ['subdomain' => '*'] doesn't match www

PHP Version
8.2
CodeIgniter4 Version
4.4.3
CodeIgniter4 Installation Method
Composer (as dependency to an existing project)
Which operating systems have you tested for this bug?
Windows
Which server did you use?
apache
Database
MariaDB 10
What happened?
I have a site with a wildcard subdomain, where I use for the subdomains for localization.  I was having difficulties getting the subdomains to work as they don't match the base_url.  I saw a post suggesting using an option in the routing to allow any domain to match  ['subdomain => '*'].
If you try to set the option ['subdomain => '*'] on a route, it works for all subdomains except www.  There it generates an error saying it could not find a route for the path.
I looked into the code and found the following at  line 1649 in RouteCollection.php
if ($host[0] === 'www') {
unset($host[0]);
}
This explicitly sets a special case for www and removes it as the subdomain and I can't see why!
If I comment these lines out it works as I would expect.
I assume that this code was added for some use-case where there is an extra www in front of the 'proper' subdomain.
However, since www may be the actual subdomain, this is a bug.  ['subdomain => '*'] should match ANY subdomain, not any subdomain except www.
Steps to Reproduce
Setup a route as follows:
$routes->get ('/', 'PublicPages::index', ['subdomain' => '*'] );
try accessing the page as
https://sub.mydomain.com/  -  loads the correct page
try accessing the page as
https://www.mydomain.com/  -  404 Can't find a route for 'get: /'.
Expected Output
Normal page loading, not a 404 Can't find a route for 'get: /'.
Anything else?
No response

Looking at the code this would also fail for ['subdomain' => 'www'] since the 'www' is removed from the host array before any comparison with the subdomain option value.

Thank you for reporting.
The current subdomain determination is quite lax.
Also, I'm not sure what a subdomain means there in the first place.

Important
The system is not perfect and should be tested for your specific domain before being used in production. Most domains should work fine but some edge case ones, especially with a period in the domain itself (not used to separate suffixes or www) can potentially lead to false positives.
https://codeigniter4.github.io/CodeIgniter4/incoming/routing.html#limit-to-subdomains

I assume that this code was added for some use-case where there is an extra www in front of the 'proper' subdomain.

The code was there from the beginning:
https://github.com/codeigniter4/CodeIgniter4/commit/13259443c8d#diff-7fc8cb2cff68c2c83b13a33474230889ec109fffda6fc0a732910a76c5ad8ec7R835
I'm not sure, but something like this?
www.example.com: the main server, not subdomain
foo.example.com: subdomain
I believe this hostname/subdomain features (and the routing data structure) should be rewritten.
There is also issue #7214.
If you can try, please send a PR.
https://github.com/codeigniter4/CodeIgniter4/blob/develop/contributing/pull_request.md

As a workaround, I recommend you extend RouteCollection.
https://codeigniter4.github.io/CodeIgniter4/extending/core_classes.html

It doesn't appear to be that simple.
1, Although the example you linked (very conveniently) shows how to replace the RouteCollection class.  The docs are out of date and show the wrong parameter list for the constructor.
2, The functions I needed to change are declared private (rather than protected) so I can't simply extend RouteCollection and replace one function.  If there's no particular reason to set something as private they should be protected, especially when you're clearly expecting people to extend the base classes. This should be fixed.
3, I tried to make a new RouteCollection by implementing the RouteCollectionInterface as in the docs.  However, when I tried this I got type mismatch errors.  This is because at various points variables/parameters have been coded with type 'RouteCollection' rather than 'RouteCollectionInterface'.
e.g., CodeIgniter\Routes\DefinedRouteCollector, CodeIgniter\Shield\Auth
It rather defeats the point of setting-up the interfaces if they're not used polymorphically.  This should be fixed.
I guess the easiest thing to do will be to extend RouteCollection but by replacing a larger chunk of it until I get back to a public or protected function that I can override.

With regard to setting functions to protected.  I just believe that in classes you expect to be extended the default for non-public functions should be protected not private.  It just gives more flexibility in extending the classes.
In the current situation I've had to copy 5 functions across from the original version of RouteCollection in order to override a protected function rather than just the 1 private function I needed to change.  This exposes me to more work merging changes during future updates.  Also, changing functions from private to protected is a non-breaking change.  I won't raise a PR as its more of a comment on general coding policy rather than anything specific to this one class.
I have a working solution to my original problem, so I'll close this issue here.

I don't want people to extend core class personally.
I think we should use interfaces, but some of them are broken...
We use private as the default visibility. Because the private method in core classes was a part of a public method originally, and we do not intend to change the API of the class.
If there is a clear reason to make it protected, we consider it.
Frankly, CI4's APIs are not mature or stable, we need to change them for fixing bugs, but if it is protected, we cannot change it easily because it will be a breaking change.


Add support for .start and .end attributes on Range objects

This is an attempt to implement .start and .end on range objects to fix issue #60.

VAR_NUM((double)(range->from));

Here ths casting isn't required since the range->from is already a double, but that's okay ill merge and remove it myself.
Thanks!

Ooh, I didn't realized we're already using end as a keyword and we can not use it as an attribute.
And make sure to add some tests at core.pk for issues like this and catching regressions in the future.

// We can't use '.start', '.end' since 'end' in pocket lang is a
// keyword. Also we can't use '.from', '.to' since 'from' is a keyword
// too. So, we're using '.first' and '.last' to access the range limits.

@xSavitar

Thanks @ThakeeNathees, so did you already do the edit? And also, which attribute are we going to use to replace .end? :)

@xSavitar I've added Here as .first and .last

@xSavitar I've added Here as .first and .last

Awesome! Thank you!


Markdown text inside backticks should not produce grammar issues

Backticks are usually used to mark keywords, thus we cannot change their form. Look at the below false positive report, which has no way to clean the false error.

Adding the articles would make the text incorrect in this case. In the absence of the backticks the suggestion would have being correct, but because the terms/keywords are backticked.
Am I right here?

Here's a related example where backticks cause an issue. In the example, the code block is followed by "which". The suggestion is to add a comma before "which", but the quick action also adds another backtick inside the existing code block
Example:
So, I calculate `$300 * 0.5 = $150` which is the impact of my risk, and I can see that that this is 15x more than the $10 cost of the mitigation.

Expected (a comma added after the backtick):
So, I calculate `$300 * 0.5 = $150`, which is the impact of my risk, and I can see that that this is 15x more than the $10 cost of the mitigation.

Actual (a backtick is added before "$150" and the comma is added after the backtick:
So, I calculate `$300 * 0.5 = `$150`, which is the impact of my risk, and I can see that that this is 15x more than the $10 cost of the mitigation.

Also double backticks for rST.


Multiple FIDO2 identities and logon behavior with Windows 10?

Can we add documentation on the expected behavior with multiple FIDO2 token identities for interactive Windows logon?  If you enroll multiple identities with a FIDO2 token, it will allow you to pick which identity one to use when doing web authentication.  If you take the same token and use it to logon a Windows 10 PC, it does not give you an option of which identity to use.  It will automatically use the last registered FIDO2 identity on the token.  Can we be sure this gets added to the article?  It's not uncommon (especially for admins) to have multiple accounts and this could cause some confusion with FIDO2 Windows 10 logons.

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

ID: 78c66f8a-1c40-e31c-5c7e-7870b7d65e0c
Version Independent ID: 3e8301bc-8e4d-ee23-8770-2f75e170e01a
Content: Enable passwordless security key sign in for Azure AD (preview) - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-authentication-passwordless-security-key.md
Service: active-directory
Sub-service: authentication
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@tomdan-MSFT, Thank you for the query. I am requesting the Author to review and make the changes accordingly.


[NTR] tuft cell of colon

Note - please check that the term does not already exist (check OLS: https://www.ebi.ac.uk/ols/ontologies/cl)
Preferred term label:
tuft cell of colon
Synonyms
Definition (free text, please give PubMed ID in format PMID:XXXXXX)
Tuft cell that is a part of the colon.
Parent cell type term (check the hierarchy here https://www.ebi.ac.uk/ols/ontologies/cl):
intestinal tuft cell http://purl.obolibrary.org/obo/CL_0019032
What is the anatomical structure that the cell is a part of? Please check Uberon: https://www.ebi.ac.uk/ols/ontologies/uberon
colon http://purl.obolibrary.org/obo/UBERON_0001155
Your nano-attribution (ORCID)
0000-0003-3440-1876
Any additional notes or concerns

Note to self,

[ ] 'tuft cell of appendix' should no longer reason under 'tuft cell of colon' after Uberon release and ingest

@sfexova
CL_0009041 (tuft cell of colon)


review: Reverse Compilation Techniques [30h]

C. Cifuentes, Reverse Compilation Techniques. PhD thesis, Queensland University of Technology, 1994.

Read everything up until "The Back-end" (section 7, page 163). This paper is a treasure and I have every intention of reading the rest of it. Marked as a future ambition, closing for now.


[CTCP-1354] renamed the collection to movements and added movementType to this collection

renamed Departure to Movement to support both arrival and departure
renamed the collection to movements
added movementType to this collection to flag whether something is an arrival or departure
Updated the departure queries to filter on departures

They'll have the same form (16 character hex), as far the the DB is concerned they'll look the same. With that in mind, DeparturesRepository should become MessagesRepository as well, as it's one collection we'll be adding to.

I don't see anything else wrong with this, I'm just gonna try the regression tests myself and see what happens (plus see if I can trigger the intermittent test you were getting).

Just gonna give it a quick whirl locally!

Ah... commit signing... right.

Superseded by #34


MAJOR UPDATE: 1:n category:sale

cat_id now in sale table. Category is found with and updated with cat_id.
To change a sale's category, do so through update sale.
select statements return category name via a join

MAJOR DATABASE UPDATE!!

Some filter URLs have been removed, as they are now handled through the sales' URLs

/add-sale now expects a catId value.
/get-sale-filter no longer accepts an array, only a single value for catId
/update-sale now has an optional catId value for updating the category

/set-filters and /remove-filters are no longer available.

autoapproved


Invalid numbering of smoke tests

Running Smoke Test==================================================================
1/3....  Configure Cluster Prerequisites                                        [OK]
2/3....  Update Hosts File                                                             [OK]
3/3....  Smoke test Master Nodes                                                [OK]
4/3....  Smoke test Master Nodes                                                [OK]

Thanks @swade1987. This is a duplicate of https://github.com/apprenda/kismatic/issues/67


build: Allow proper build with Visual Studio out-of-the-box

Hi,
This attempts to add proper support out-of-the box for building Graphene using Visual Studio, so that we can make use of it with Visual Studio builds of the upcoming GTK+-4.x (for GSK), as most of the code is ready for building and usage under Visual Studio 2008+ (!), but a build system that would support the MSVC toolchain is not yet in place.
As a result, updates are needed for the meson build files to support the toolchain properly, and a few minor changes are needed for the code so that things will work in the Visual Studio versions that we support for GTK+ (the code changes I will post later).  Note that on 32-bit builds, Visual Studio 2013 or later is required to enable SSE2 support due to x86/32-bit ABI limitations.
With blessings, thank you!

Hi,
Updated the files to go back to using pkg-config for all builds, plus some small changes for pre-2015 Visual Studio.
With blessings, thank you!


Generating test case for rhel-84-aarch64-rhel-edge-commit - FAIL

I tried to generate test cases for RHEL-8.4 and came across this failure:
2021-09-21 14:15:43,438 [ERROR] - aarch64-Runner: Generating test case for rhel-84-aarch64-rhel-edge-commit - FAIL
retcode: 1
stdout: generating test case for rhel-edge-commit
generating test case for rhel-edge-commit-rt

stderr: usage:  setfiles [-diIDlmnpqvFW] [-e excludedir] [-r alt_root_path] spec_file pathname...
usage:  setfiles [-diIDlmnpqvFW] [-e excludedir] [-r alt_root_path] spec_file -f filename
usage:  setfiles -s [-diIDlmnpqvFW] spec_file
usage:  setfiles -c policyfile spec_file
ostree config get core.mode --repo=/var/tmp/tmpyedn13uc/root/repo
ostree refs --repo=/var/tmp/tmpyedn13uc/root/repo
ostree rev-parse rhel/8/aarch64/edge --repo=/var/tmp/tmpyedn13uc/root/repo
ostree checkout --force-copy 3f588a26259cc0fa5e28a9cca7a534340fc5b8b0f8bf6899c35c600f050383ea /var/tmp/tmp8in9qfw8/tree --repo=/var/tmp/tmpyedn13uc/root/repo
No match for argument: kernel-rt
panic: Could not depsolve: DNF error occured: MarkingErrors: Error occurred when marking packages for installation: Problems in request:
missing packages: kernel-rt

goroutine 1 [running]:
main.main()
        /root/tmp.TGWKyC1DP7/sources/cmd/osbuild-pipeline/main.go:127 +0x1088
exit status 2

It seems that kernel-rt for aarch64 does not exist in any repository.

This is a duplicate of #1478.


Cannot Copy file from AWS S3 Buckets

Which version of the AzCopy was used?
10.1.2
Note: The version is visible when running AzCopy without any argument
Which platform are you using? (ex: Windows, Mac, Linux)
Windows
What command did you run?
azcopy cp "https://s3.amazonaws.com/thomasmaurerimages" "https://tomsazureaccount.blob.core.windows.net/?sv=somesastoken" --recursive=true
What problem was encountered?
Copy of items from AWS bucket to Azure Blob fails. Strangely the same command worked 3 weeks ago. In the log I get the following error:
INFO: Scanning...
INFO: AWS S3 to Azure Blob copy is currently in preview. Validate the copy operation carefully before removing your data at source.
INFO: trying to copy the source as bucket/folder/list of files
INFO: source is bucket and destination is an Azure service endpoint, bucket with name "thomasmaurerimages" will be created in destination to store data
Job e8663afe-06be-4749-7826-74563e5ff28c has started
Log file is located at: C:\Users\thmaure/.azcopy/e8663afe-06be-4749-7826-74563e5ff28c.log
0 Done, 0 Failed, 33 Pending, 0 Skipped, 33 Total,
Job e8663afe-06be-4749-7826-74563e5ff28c summary
Elapsed Time (Minutes): 0.0334
Total Number Of Transfers: 33
Number of Transfers Completed: 0
Number of Transfers Failed: 33
Number of Transfers Skipped: 0
TotalBytesTransferred: 0
Final Job Status: Failed
The log files has marked the following:
2019/06/11 15:14:21 INFO: [P#0-T#3] Starting transfer: Source "https://s3.amazonaws.com/thomasmaurerimages/images/HJymwQA - Copy (2).png" Destination "https://tomsazureaccount.blob.core.windows.net/thomasmaurerimages/images/HJymwQA - Copy (2).png?se=2019-06-11t23%3A07%3A16z&sig=REDACTED&sp=rwXXXX". Specified chunk size 8388608
2019/06/11 15:14:21 INFO: [P#0-T#13] Starting transfer: Source "https://s3.amazonaws.com/thomasmaurerimages/images/CjKfteT - Copy (2).png" Destination "https://tomsazureaccount.blob.core.windows.net/thomasmaurerimages/images/CjKfteT - Copy (2).png?se=2019-06-11t23%3A07%3A16z&sig=REDACTED&sXXXX6-11t15%3A07%3A16z&sv=2018-03-28". Specified chunk size 8388608
2019/06/11 15:14:21 ==> REQUEST/RESPONSE (Try=1/479.1841ms, OpTime=479.1841ms) -- RESPONSE STATUS CODE ERROR
PUT https://tomsazureaccount.blob.core.windows.net/thomasmaurerimages/images/8h0LEDm - Copy (2).png?XXXXXX
Content-Length: [0]
User-Agent: [S3Import AzCopy/10.1.2 Azure-Storage/0.6 (go1.10.8; Windows_NT)]
X-Ms-Client-Request-Id: [80fa0cbb-3b3a-41f5-7dd3-692ebf7034f8]
X-Ms-Copy-Source: [https://thomasmaurerimages.s3.dualstack.eu-central-1.amazonaws.com/images/8h0LEDm - Copy (2).png?x-amz-algorithm=aws4-hmac-sha256&x-amz-credential=akiajcXXXXXquest&x-amz-date=20190611t151420z&x-amz-expires=604800&x-amz-signature=REDACTED&x-amz-signedheaders=host]
X-Ms-Source-Range: [bytes=0-374443]
X-Ms-Version: [2018-11-09]
RESPONSE Status: 400 The copy source must be an Azure resource.
Content-Length: [233]
Content-Type: [application/xml]
Date: [Tue, 11 Jun 2019 15:14:20 GMT]
Server: [Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0]
X-Ms-Error-Code: [CannotVerifyCopySource]
X-Ms-Request-Id: [2d675b22-301e-006f-5b68-201d65000000]
X-Ms-Version: [2018-11-09]
goroutine 60 [running]:
How can we reproduce the problem in the simplest way?
Run the mentioned command
Have you found a mitigation/solution?
No

Hi @thomasmaurer, thanks for reaching out! And sorry for the inconvenience.
It looks like a configuration issue on the service side. I'll involve the service folks and update this thread accordingly.

Hi @thomasmaurer, it was indeed a configuration issue. It should be fixed now. Please let me know if you are still encountering issues.

hi  @zezha-msft, I just tried again. I still have the issue:
2019/06/12 15:29:46 ERR: [P#0-T#2] COPYFAILED: https://s3.amazonaws.com/thomasmaurerimages/8h0LEDm - Copy.png : 400 : 400 The copy source must be an Azure resource.. When Staging block from URL. X-Ms-Request-Id: e377d22e-201e-003e-2f33-2180e9000000

@thomasmaurer really sorry for the inconvenience. There was a minor hiccup in the configuration. It should be fixed now. Really appreciate your patience.

Same issue, seems to still be happening?


reconsider version binding with MMIF spec

Because
The problem with SDK version, while using three digits in the version string, indeed having only one digit-space as its actual versioning scheme ("major" and "minor" digits are tied to MMIF spec version) has been raised in multiple occasions (https://github.com/clamsproject/mmif/issues/14#issuecomment-847478079, https://github.com/clamsproject/mmif/issues/228#issuecomment-2226406193) and there are more pending issues (#292 #295 #296 ) that are destined to "break" from older versions. So I don't think we can further operate under the current versioning scheme.
A few possible solutions to the problem

total separation of MMIF version digits and mmif-python version digits at least in formal way (we can keep some "convention" to sync up two versions to a reasonable extent)
use four-digit version scheme for mmif-python to give a wider room to "break" things.
stop "minor" digit sharing and keep three digit versioning - this is in the middle between the above two. A "minor" bump in the MMIF spec won't "break" anything (it just add more features while not changing any existing behaviors), so keeping the "major" digit sync will still indicate that all mmif-python==1.* will work with MMIF files (<2.0).

Any input is welcome. Please share your thoughts.
Done when
No response
Additional context
No response

So, looping back to the "meaing" of those digits (https://github.com/clamsproject/mmif/issues/23) based on the sem-ver scheme, there are different types of changes we make to code.

(pb) publicly breaking changes (deletion of a public API, changes of signature or behavior of a public API, etc)
(pa) publicly adding changes (adding a new method, feature, etc)
(b) privately breaking changes (breaking changes in a private functionality of the code)
(a) privately adding changes (adding a private method, class, etc)
(f) fixing public and private bugs (https://xkcd.com/1172/)

(of course any of these types can be eventually breaking, but let's pretend we're in an ideal world)
Now, sem-ver suggests that only pb type of changes are real "breakage", so it suggests

major digit goes for pb changes
minor digit goes for pa changes
all other changes go with patch digit

Now applying the same to the spec, we can roughly think of

(spb) publicly breaking changes (deletion of a public spec, scheme, vocan defs, changes of behavior of them, (adding a new required field to scheme*)
(spa) publicly adding changes (adding an optional field, adding a new type, etc)
(sb) privately breaking changes (everything is public in the spec, so probably no such changes in spec?)
(sa) privately adding changes (everything is public in the spec, so probably no such changes in spec?)
(sf) fixing public and private bugs (fixing types in spec, defs, etc.)

So now, let's talk about the SDK. Since SDK is "tied" to MMIF spec versions, there are two different sources of the breaking changes (pb in the SDK code itself, and spb from changes in the spec)

I don't think four-digit scheme (as proposed above by me) won't work, as long as we use x.y.a.b digits where

x is tied to spb changes (BREAKING!)
y is tied to spa changes
a is tied to pb changes (BREAKING!)
b is tied to other changes in the code
because, sorting of version strings will mix and mess up the concept of breakages, and nuke the way we specify the dependency.

To that end, I'm now thinking among these three schemes

a.b.c - no tie to the MMIF spec version at all
x.a.b - only tied to major spec version
x.a.y.b - four-digit scheme, but re-ordered to work with sorting


Expand CC0006 (change for into a foreach)

Currently CC0006 is only raised on a specific pattern, with a for, and an assignment happening with the indexer like this:
var array = new [] {1};
for (var i = 0; i < array.Length; i++)
{
    var item = array[i];
}

And it's code fix changes it to a foreach, like this:
var array = new [] {1};
foreach (var item in array)
{
}

It is not currently able to deal with more array accessors, like this:
var array = new [] {1};
var count = 0;
for (var i = 0; i < array.Length; i++)
{
    var item = array[i];
    count += array[i];
    Console.WriteLine(array[i]);
}

This could be changed to:
var array = new [] {1};
var count = 0;
foreach (var item in array)
{
    count += item;
    Console.WriteLine(item);
}

This issue will expand both the analyzer and the code fix.
VB does not have this analyzer yet, so this would only be C#.

@giggio It´s very interesting. I tested two samples now and second one do not fire analyzer.


Happy New Year!

Happy new year to you all.
Do we actually need to update these each year.  This is something we could do as part of the release process isn't it?

Do we actually need to update these each year. This is something we could do as part of the release process isn't it?

Not sure.


Moment not reading JS variable

Hi guys,
I'm stuck with a problem inside my jade template when using moment. I have a json value which I can read with mustache, and I simply can't use it with moment.
Example (inside my jade template):

var teste = "{{myDate}}";

{{myDate}} - #{teste} - #{moment("2016-05-24T17:39:28.000Z", "YYYY-MM-DD HH:mm").format("DD[/]MM[/]YYYY HH:mm")} - #{moment(teste.toString(), "YYYY-MM-DD HH:mm").format("DD[/]MM[/]YYYY HH:mm")} - #{moment(teste, "YYYY-MM-DD HH:mm").format("DD[/]MM[/]YYYY HH:mm")}
This returns me: 2016-05-24T17:39:28.000Z - 2016-05-24T17:39:28.000Z - 24/05/2016 17:39 - Invalid date - Invalid date
Can anyone help?
Cheers

Can you try this out on the JS console and show us exactly? You should be able to do something like:
moment("some string").format("DD[/]MM[/]YYYY HH:mm") //=> Invalid date

That'll make it easier for us to help without thinking about Jade templates and such.

Oops, didn't mean to close that.

Ok, I think my original post wasn't clear enough.
moment("2016-05-24T17:39:28.000Z", "YYYY-MM-DD HH:mm").format("DD[/]MM[/]YYYY HH:mm") //=> 24/05/2016 17:39
That's just fine. It's working as expected. But if I create a JavaScript's variable and try to use it with moment, it doesn't work.
As in:

var myTestDate = "2016-05-24T17:39:28.000Z";
moment(myTestDate, "YYYY-MM-DD HH:mm").format("DD[/]MM[/]YYYY HH:mm") //=> Invalid Date

I just pasted those last two lines into my JS console and it printed "24/05/2016 17:39".  Moment doesn't even know if it's in a variable or is just a string literal; it just takes a parameter.
I suspect that in your application, the variable doesn't contain quite what you think it contains. That's why I want you to isolate the problem to two lines of code. I strongly suspect that in the process, you'll find out what's wrong with your code.

Ok, you got me there. So maybe the problem only occurs when using moment with jade.
I'm iterating over some data inside a table. For each table row, I've got this:
https://gist.github.com/mcpenchel/37de96b6009bd3e9aa88f8ef6e259925
This returns me, in the first row, for example, the following:
2016-05-24T17:39:28.000Z - Invalid date
This is bugging me. The problem isn't with mustache, because the myTestDate variable is printed accordingly. But it simply isn't evaluated by moment when inside the #{}.

It's been a long time since I've used Jade, so I don't know how helpful I can be. Maybe try switching it to a console.log() and see if it prints what you expect?
I just know this works:
var myTestDate = '2016-05-24T17:39:28.000Z';
moment(myTestDate, "YYYY-MM-DD HH:mm").format("DD[/]MM[/]YYYY HH:mm")
"24/05/2016 17:39"

Not the problem here, but it's also worth noting that you're not really using the right parsing string; the date you're passing in doesn't look like "YYYY-MM-DD HH:mm", but it's working because the parser is pretty liberal. Because the string is ISO-8601, you can actually just do moment(myTestDate).
Since I can't figure out how to help, and because I'm confident there's no Moment issue here, i'm going to  close this out. You might have more luck on SO where people more familiar with Jade can pitch in.


Bug: Flyout does not display when apps are in fullscreen mode

Bug: Flyout does not display when apps are in fullscreen mode. Please fix.

Duplicate of #32.
Please refer #32 for future updates.
I'll now close this issue as a duplicate.

Thank you!


chore(examples): Add starter example

I think this is outdated since we have the "basic" example, reopen if I'm wrong :)


Configuration:  no longer hardcode mesh certs

Addresses #11984
Changes in vendor are a stand-in for https://github.com/istio/api/pull/828
Follow-on to #12142 (closed)

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: drichelson
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: rshriram
If they are not already assigned, you can assign the PR to them by writing /assign @rshriram in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS
vendor/istio.io/api/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @drichelson. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

You are missing changes to cluster.go (istio mtls setting client side)

@drichelson: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
3dc15309c08569bce29e9060aa09234ffc7c8320
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@drichelson: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
3dc15309c08569bce29e9060aa09234ffc7c8320
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
3dc15309c08569bce29e9060aa09234ffc7c8320
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@drichelson: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
3dc15309c08569bce29e9060aa09234ffc7c8320
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
3dc15309c08569bce29e9060aa09234ffc7c8320
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
3dc15309c08569bce29e9060aa09234ffc7c8320
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram

You are missing changes to cluster.go (istio mtls setting client side)
I've updated the PR comments noting that this only covers TLSSettings_MUTUAL mode.

Based on my reading of cluster.go: when in TLSSettings_MUTUAL mode we always pull mTLS client cert paths from DestinationRules. Based on this the client certs are already configurable, so we're covered.
Only in when in TLSSettings_ISTIO_MUTUAL mode do we use the hardcoded client certs when building clusters.
Does this make sense? It looks like wiring in the client cert paths for ISTIO_MUTUAL mode will be a bit more gnarly.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: drichelson
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ymesika
If they are not already assigned, you can assign the PR to them by writing /assign @ymesika in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@drichelson: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
3dc15309c08569bce29e9060aa09234ffc7c8320
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
3dc15309c08569bce29e9060aa09234ffc7c8320
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
55b93ab9f6dde8386a537a980956d6c98f1af90d
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@drichelson: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
3dc15309c08569bce29e9060aa09234ffc7c8320
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
55b93ab9f6dde8386a537a980956d6c98f1af90d
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
55b93ab9f6dde8386a537a980956d6c98f1af90d
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@drichelson: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
55b93ab9f6dde8386a537a980956d6c98f1af90d
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
55b93ab9f6dde8386a537a980956d6c98f1af90d
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
55b93ab9f6dde8386a537a980956d6c98f1af90d
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@drichelson: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
55b93ab9f6dde8386a537a980956d6c98f1af90d
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
55b93ab9f6dde8386a537a980956d6c98f1af90d
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
e208d82399c5695aacdc13840ecd59355d7a1aef
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@drichelson: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
55b93ab9f6dde8386a537a980956d6c98f1af90d
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
55b93ab9f6dde8386a537a980956d6c98f1af90d
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
5aac66d519edae14ed9e2b06c7ddda14040d52f4
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@drichelson: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
55b93ab9f6dde8386a537a980956d6c98f1af90d
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
5aac66d519edae14ed9e2b06c7ddda14040d52f4
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
5aac66d519edae14ed9e2b06c7ddda14040d52f4
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@drichelson: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
55b93ab9f6dde8386a537a980956d6c98f1af90d
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
5aac66d519edae14ed9e2b06c7ddda14040d52f4
link
/test istio-integ-k8s-tests

prow/e2e-simpleTests-cni.sh
593f2032b81b780debafc6e3a40be5f4445774b9
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@drichelson: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
55b93ab9f6dde8386a537a980956d6c98f1af90d
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
593f2032b81b780debafc6e3a40be5f4445774b9
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
593f2032b81b780debafc6e3a40be5f4445774b9
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@drichelson: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
593f2032b81b780debafc6e3a40be5f4445774b9
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
593f2032b81b780debafc6e3a40be5f4445774b9
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
593f2032b81b780debafc6e3a40be5f4445774b9
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Do you need to customize the names of the files, or just the directory ? I can see the use case for using a different dir - that's why we have the base dir. ( and watching the base dir is indeed needed - again, the base was mostly intended for local testing - with the plan to move to SDS ).
It feels far too complicated for something that will soon be dead code - and our tradition of paying technical debt and removing dead code is not so great.  In general the entire watching business has
major problems - it would be much better to just spend less effort writing a small SDS server that watches files, which will address the reload-without-restart problem as well.

@costinm

Do you need to customize the names of the files, or just the directory ?

The path to each cert/key is custom. This includes separate keys/certs for client and server connections.
I can see the use case for using a different dir - that's why we have the base dir. ( and watching the base dir is indeed needed - again, the base was mostly intended for local testing - with the plan to move to SDS ).

It feels far too complicated for something that will soon be dead code - and our tradition of paying technical debt and removing dead code is not so great. In general the entire watching business has
major problems -

it would be much better to just spend less effort writing a small SDS server that watches files, which will address the reload-without-restart problem as well.

A small SDS server makes sense  to simplify Pilot-Agent and envoy hot restarts. The changes I made here to watcher code and agent config will be useful and needed for our use case if/when that happens.

@rshriram any thoughts on these changes?

@drichelson: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
593f2032b81b780debafc6e3a40be5f4445774b9
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
593f2032b81b780debafc6e3a40be5f4445774b9
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
ad78c109e0c20be65f84864de9a6a525e0c0b9af
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@drichelson: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
593f2032b81b780debafc6e3a40be5f4445774b9
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
593f2032b81b780debafc6e3a40be5f4445774b9
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
29eb175f67c43598bf04d779981b9586817031a1
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@drichelson: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
593f2032b81b780debafc6e3a40be5f4445774b9
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
29eb175f67c43598bf04d779981b9586817031a1
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
29eb175f67c43598bf04d779981b9586817031a1
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@drichelson: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
29eb175f67c43598bf04d779981b9586817031a1
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
29eb175f67c43598bf04d779981b9586817031a1
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
29eb175f67c43598bf04d779981b9586817031a1
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram Is there any chance of getting this in 1.1.0? probably not. If not, what do I need to do to get it in 1.1.1?

I think there is a definite chance of getting this into 1.1.1. We simply want to minimize any untested (out in wild) code changes in the last moment. But once 1.1 is out, you can cherry pick this PR and submit it to release-1.1 branch, and it will automatically land in 1.1.1

/approve
/lgtm

@rshriram: changing LGTM is restricted to assignees, and assigning you to the PR failed.

In response to this:

/approve
/lgtm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: drichelson, rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@drichelson @rshriram I just noticed the code in pilot-agent that sets proxy.Metadata.
I'm not seeing where it's used in this context, however, since the global role variable is never passed into any functions, nor is its Metadata field read.
Any thoughts?

Thanks @nmittler I'm now noticing this too when running locally. Expect a follow-up PR soon


Add a github workflow to periodically autobuild and autopush to docker hub

Geerlingguy's build github workflow is an excellent guide: https://github.com/geerlingguy/kubernetes-101/blob/master/.github/workflows/build-episodes.yml


Update docstring

The method name changed but the docstring doesn't change accordingly. I copied the docstring from the corresponding module level function with the same name, which is already corrected.

I have a further idea to use functools.wraps on all the module level functions (every, run_pending, run_all, clear, cancel_job, next_run and idle_seconds), so they'll always have the same doctring as their class method counterparts. If that also sounds good to you, I'll move on and implement it.

Thank you @qobilidop, good catch :)

I have a further idea to use functools.wraps on all the module level functions (every, run_pending, run_all, clear, cancel_job, next_run and idle_seconds), so they'll always have the same doctring as their class method counterparts. If that also sounds good to you, I'll move on and implement it.

Mmh, that's an interesting idea! I'm not 100% convinced using functools.wraps just for copying the docstring is worth it.
Alternatively we could change the module level docstrings to say something like "Calls xyz() on the default scheduler instance." (with a Sphinx link to the corresponding method on the Scheduler class.
To be honest I'm leaning towards the "lo-tech" solution of just updating the module level docstrings to link to Scheduler – but if you want to give the wraps implementation a try so we can see what it looks like then please go ahead.

Hi @dbader, I changed the module level docstrings as you suggested. I haven't thought of this solution before. I agree that this might be a better solution in that we don't have to introduce another complexity of functools.wraps.


[ASv2] implement FederatedAttestations CK wrapper methods

TODOs

[ ] logic needed for writing, accessing attestations
[ ] CK wrapper tests

closed by #9918


{bintools-wrapper,cc-wrapper}: export Darwin SDK variables

514b00cf08702b31cdf873a798f1ff100d4f2cf7 exposed another bug in the existing wrapper logic: Darwin SDK variables are only exported by the SDK package hook, so if those variables aren’t already exported inside the wrappers, the modified versions are not passed down to the compiler tools, breaking the fallback SDK logic. This was previously partially masked by passing down a normally‐redundant -isysroot to the compiler, but now we fix it at the source.
This broke e.g. running clang(1) without any environment, something the GHC binary package installCheckPhase does indirectly to verify that there’s nothing missing from the wrapped GHC $PATH. It may also have caused issues building for the build platform inside a Darwin‐to‐non‐Darwin cross‐compilation build.

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Going to test this and https://github.com/NixOS/nixpkgs/pull/351531 together.

I have confirmed that this fixes the GHC binary package.

Randy said it looked good and it fixed the bug, so merging.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/title-the-darwin-sdks-have-been-updated/55295/1

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/the-darwin-sdks-have-been-updated/55295/26


release: 1.3.6

[1.3.6] (Mar 25 2024)
Feat:

Dismiss mobile keyboard after sending a message

/bot create ticket


Node MCU FLASH ISSUE

Hello, i recently used your nodemcu firmware program and it did not work. When it first downloaded i put in my nodemcu and it came up as COM4 for a com port operation which was a good thing, then I went to config and put in the file I downloaded from spacehuhn, after that every thing was going how it needs to be. BUT THEN... shit hit the fan and the flash didnt work when I press flash.. sofar since i hit flash (1 hour ago) it still has not found my AP Mac and STA Mac but it says its ready. also my node mcu is not damaged as its led light still works like usual.

SAME PROBLEMS


Remove unnecessary lines from bundler/setup

What was the end-user problem that led to this PR?
These lines in the bundler/setup file are not necessary.
What was your diagnosis of the problem?
Bundler no longer needs to be in the $LOAD_PATH once a version of itself has been loaded.
In any case, the Metadata source takes care of adding bundler to the index:
https://github.com/bundler/bundler/blob/e70643c1be3a4417bd537d7e63470265465e693e/lib/bundler/source/metadata.rb#L13-L30
and then that spec is added to the resolution here:
https://github.com/bundler/bundler/blob/e70643c1be3a4417bd537d7e63470265465e693e/lib/bundler/definition.rb#L180-L184
And from the resulting set of specs, the $LOAD_PATH is setup:
https://github.com/bundler/bundler/blob/e70643c1be3a4417bd537d7e63470265465e693e/lib/bundler/runtime.rb#L25-L38
So bundler will be present in the $LOAD_PATH anyways, and the lines being removed here will never be useful.
What is your fix for the problem, implemented in this PR?
My fix is to remove these lines to make the code easier to follow.

@bundlerbot merge


error when building docker image

---> Running in 00f407df5098
/bin/sh: 1: /install.sh: Permission denied
The command '/bin/sh -c /install.sh && rm -r /root/.cabal' returned a non-zero code: 126
I get the above error when trying to build docker image as explained
docker build -t haskell-vim .
any ideas ?

This error is resolved by giving the exec rights to the install.sh
chmod +x install.sh

I ran into the same issue. I updated my Dockerfile as follows:
FROM haskell:7.8

# install vim tooling
RUN apt-get update \
 && apt-get install -y git vim curl build-essential wget tmux\
      # for vim extensions
      exuberant-ctags libcurl4-openssl-dev \
 && apt-get clean

# Haskell Vim setup
ADD https://raw.githubusercontent.com/begriffs/haskell-vim-now/master/install.sh /install.sh
RUN chmod +x /install.sh
RUN /install.sh && rm -r /root/.cabal

Note that besides adding the chmod I also added the wget package (as this stopped some warning messages that popped up when hoogle was being built) and the tmux package (because, tmux is awesome in a development environment).
Everything seems to be working well now.

ASIDE: Thank you Joe Nelson for putting this project together. Just reading through the install.sh file has helped me learn about both Vim and Haskell (which is good as I'm relatively new to both).

this is fixed and can be closed


Stop updating

Issue Type: Bug
Not a bug, but please stop trying to "improve" VSCode, in particular, the design and layout.
Microsoft has a habit of ruining things and VSC, along with Excel, is already going down that path.  Please, stop. Let us enjoy something for a while.
Whatever changes were made in the latest update...not good. I don't need a purple bottom., weird windows, unexpected theme and setting changes.  It's frustrating.  I'll happily stop using VSCode if it goes the way of Visual Studio since there are a lot of great competitors out there.
VS Code version: Code 1.40.0 (86405ea23e3937316009fc27c9361deee66ffbf5, 2019-11-06T17:02:13.381Z)
OS version: Windows_NT x64 10.0.16299

I think you can fork VS Code and build the old Version.

@DiamondYuan Thanks, Yuan! I'll try that.
I don't mind a lot of the updates, but MS rendered VS Community pretty much unusable for me and I wish there would be a "required and optional" selection list for each update.  Probably not feasible now, but maybe down the line.

@MarkMoretto
Can you please file separate issues for the problems you mention above:

Whatever changes were made in the latest update...not good. I don't need a purple bottom., weird windows, unexpected theme and setting changes.


Have a way to clean up experimental features once they are no longer experimental

Summary of the new feature / enhancement
In order to improve performance and reduce clutter, there should be a way to get rid of any "old" or "previously" experimental  features configurations.
Proposed technical implementation details (optional)
Have a parameter for Disable-ExperimentalFeature that would clean up all experimental features that are no longer available via Get-ExperimentalFeature. Something like Disable-ExperimentalFeature -Clean, open to suggestions on better wording or syntax on how to do this?
Another possible option is for when someone does Enable-ExperimentalFeature <name> we can do a behind the scenes check on features that may be in configurations but not experimental features any more and then remove them.

cc @JamesWTruher

See also:

#18970


Configure image components

-sharp
-transformer-sharp
-gatsby-plugin-image
-source-sanity with images

Optimize for astro


Media 'Image Editor' button missing

When developing my WebSite using VS2015 or WebMatrix I'm able to edit my images:
Admin --> Media --> clicking an image --> Image Editor
HOWEVER, as soon as I deploy my Site the 'Image Editor' button won't appear anymore.
Following Modules (and its prereq's) are enabled:
Media.Library
Media.Library.Search
Media.Library.Processing
Image.Editor
I'm running 1.9.2; are there any updates needed/available for these relevant modules!?
(I'm NOT on Azure)
Thanks for any hint, ed

my first comment isn't true anymore:
I.E. the next morning : the  'Image Editor' button disappeared again!
quote
When developing my WebSite using VS2015 or WebMatrix I'm able to edit my images:
Admin --> Media --> clicking an image --> Image Editor
end quote

well, after testing some more (2 days):
the results on my systems (WebMatrix, VS2015 and the deployed (non-Azure) sites:
the results   seem unpredictable. Sometimes the 'Image Button' appears, the next time it's not
there anymore. (Also, I'm not able to find any hints in the log files or when tracing)
I appreciate any hint you might have. thanks, ed

I am having exactly the same problem. I am running on 1.9.1 on IIS on Server 2012

As you see I closed that issue due to  strange behaviour on this subject i.e. the behaviour was not predictable anymore - therefore I closed it and did some more 'investigation' --> without success! That's the reason I opened a new one again:  "Media ImageEditor button not showing  #6285" in GitHub AND in the old forum!? Reason for that: PS:
PS: As a GitHub novice I (re)placed  - probably  erroneously - this same issue again on GitHub (#6285)!
I (only) understand that GitHub is firstly an App for distributed revision control using (local) repositories. After Orchard introduced GitHub: where is the correct place to report issues like this? I see reported issues also on GitHub - are all of them based on local repositories contributing to fix Orchard development / design errors?
Which forum is the correct one for issues like this?
Thanks for a clarification on this and the issue itself ? ed