Error: valid package.json not found

This action produces the following error when used like shown in the example:
Run scottbrenner/generate-changelog-action@master
/usr/bin/docker run --name e87b520ef943f0bed24d3f9c56c6777de8a64d_2dadf6 --label e87b52 --workdir /github/workspace --rm -e REPO -e HOME -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e RUNNER_OS -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/ansible-role-packages-test/ansible-role-packages-test":"/github/workspace" e87b52:0ef943f0bed24d3f9c56c6777de8a64d
Error: valid package.json not found
    at /usr/lib/node_modules/generate-changelog/lib/package.js:18:11
    at tryCatcher (/usr/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/usr/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/usr/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/usr/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/usr/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/promise.js:725:18)
    at _drainQueueStep (/usr/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/usr/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/usr/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/usr/lib/node_modules/generate-changelog/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (internal/timers.js:439:21)

Error: valid package.json not found

Do you .. have a package.json file in the repository where you're running this?

No I have not. Should I?

I believe it is required, suggest opening an issue in the "upstream" repository - https://github.com/lob/generate-changelog - can't do much about it here.

Can you then maybe update your readme that this action uses a linter tool which is primarly for npm package development (and therefore needs a package.json )
So other people will know before implementing the action themselves just to run into the same issue

Totally, had no idea! Thanks for bringing this to my attention.

https://github.com/lob/generate-changelog/issues/38


Nested array doesn't work in react strict mode

Describe the bug
An error is thrown on component mount when using an array inside an object and the app is inside React.StrictMode
The component is not rendered.
Your minimal, reproducible example
https://stackblitz.com/edit/tanstack-form-an5lkt?file=package.json,src%2Findex.tsx
Steps to reproduce

Have a nested structure like in the MRE
Have your react app on strict mode
Mount the component

Expected behavior
The component loads
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
macOS but also on stackblitz
TanStack Form adapter
react-form
TanStack Form version
v0.18.0
TypeScript version
No response
Additional context
The error message is
Uncaught TypeError: Cannot convert undefined or null to object
    at Function.keys

If I'm not mistaken, it seems that during the duplicate render caused by strict mode, state.value is undefined here:
https://github.com/TanStack/form/blob/39848e3654e6b47acbf91e30858fb183493e5041/packages/react-form/src/useField.tsx#L93

This issue should be fixed with the newest version of TanStack Form


Updated the compatibility status for iOS and macOS

Hello @yiszza ,
I'm sorry for the delay, I got sick and until now I was able to review it. Please find below a PR with the updated status of the compatibility for iOS and macOS. Along with some screenshots where I tested them.

Thanks for this fantastic work! I hope somebody can bring some help with the missing elements 🙏🏻

Thanks!🥳


Lock Labels for Storage Service Authorization

Fixes #23805
This PR locks labels that should never be translated.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 11129.

Availability update: We will publish a fix for this issue in the next update for release 22.
Build ID to track: 57808.


Mandatory: Security analysis of own repo

Report should be included in exam

@EraxterCodes create small report and put link to it in https://github.com/itu-devops/lecture_notes/blob/master/misc_urls.py

PR made for link to our analysis in a HTML package.


feat(mux): Support splitting Kitty multiplexer panes

Fixes #205
How to test
Ensure you've run post-install hooks for kitty; I think you can do this via :Lazy sync<cr>

Use following config in a Kitty multiplexer session:

-- the actual keys `<M-C-k>` can be whatever you'd like
vim.keymap.set("n", "<M-C-k>", function()
    mux.split_pane("up")
end)
vim.keymap.set("n", "<M-C-j>", function()
    mux.split_pane("down")
end)
vim.keymap.set("n", "<M-C-h>", function()
    mux.split_pane("left")
end)
vim.keymap.set("n", "<M-C-l>", function()
    mux.split_pane("right")
end)

Use the keymaps, they should create kitty splits

Looks like there is one Luacheck warning that needs to be resolved, but looks good other than that. https://github.com/mrjones2014/smart-splits.nvim/actions/runs/9360568332/job/25782345774?pr=206#step:6:15


RFC: Add Procfile as stand-alone buildpack to Tiny builder

Readable

It looks like the Procfile buildpack sets the Procfile process up as a direct process if it's being run on the Tiny stack. I tried using our Procfile sample. The build succeeds:
pack build procfile-tiny --builder paketobuildpacks/builder:tiny --buildpack gcr.io/paketo-buildpacks/procfile

But running the container fails with:
docker run --tty --publish 8080:8080 procfile-tiny
ERROR: failed to launch: path lookup: exec: "FOLDER=web": executable file not found in $PATH

It seems that the format of a valid Procfile is different on the Tiny stack. I'd like to see an example laid out in this RFC of a valid Procfile for the tiny stack. And I think documenting this subtlety and/or adding a sample should be part of implementing the RFC.

@fg-j The following PR has an updated version of the Procfile sample app that is compatible to run on Tiny.

We should probably also relocate this to https://github.com/paketo-buildpacks/builder since that's where other builder RFCs live.

The RFC has been opened in the builder repo. Closing this PR in favor of the one in the top level builder repo.


issues when installing requirements in Cloud Community

when pip installing requirements in cloud community, it fails. Works well when running local.

Especifying versions in requirements is a solution for cloud community.
streamlit>=1.28
langchain>=0.0.217
openai>=1.2
duckduckgo-search
anthropic>=0.3.0
trubrics>=1.4.3
streamlit-feedback


[D2] 8.3 Update Github

Update Github Project Board
To be completed everytime until week 13

Github Project Board
The link to our GitHub lies here. This is where the team can keep track of one another to see if we have completed our assigned task on time.

Review and closed on: 31/3/2023


Failure to verify a twitter account

I have no idea what the problem is. The app consistently fails to verify the twitter account.
This is the link to the verification tweet: https://twitter.com/macosxguru/status/909941977122185216
You guys might be overwhelmed with sign ups.
macosxguru

@macosxguru The bit.ly link looks strange.

Twitter made that link. I didn't.

It is verified now. Sorry my mistake.


FillConsole on the final cell in a line moves the internal cursor

Environment
Windows build number: 10.0.18363.657
Windows Terminal version (if applicable):  0.8.10261.0

Steps to reproduce
Here's a repro program.  I've tried to make this as simple as I can, but the way the visual cursor location is not the same as the reported cursor location makes this strangely confusing:
#include <windows.h>
#include <stdio.h>

int main(int argc, char * argv[])
{
    CONSOLE_SCREEN_BUFFER_INFO StartScreenInfo;
    CONSOLE_SCREEN_BUFFER_INFO PostFillScreenInfo;
    CONSOLE_SCREEN_BUFFER_INFO PostWriteScreenInfo;
    HANDLE ConHandle;
    DWORD NumberWritten;

    ConHandle = GetStdHandle(STD_OUTPUT_HANDLE);
    GetConsoleScreenBufferInfo(ConHandle, &StartScreenInfo);

    // Set the console mode to some consistent value.
    SetConsoleMode(ConHandle, ENABLE_PROCESSED_OUTPUT);

    // Move the cursor to the rightmost cell in the line, and sleep to show
    // that as far as the user is concerned, that's where it is.  If this is
    // any cell except the rightmost one, the following test case will behave
    // correctly.
    StartScreenInfo.dwCursorPosition.X = StartScreenInfo.dwSize.X - 1;
    SetConsoleCursorPosition(ConHandle, StartScreenInfo.dwCursorPosition);
    Sleep(3000);

    // Fill the final cell.  This API should not move the cursor.  In conhost,
    // the cursor does not appear to move, but in WT, it visually moves.
    // Sleep for a bit to show that the cursor location displayed to the user
    // has changed.
    FillConsoleOutputCharacter(ConHandle, 'X', 1, StartScreenInfo.dwCursorPosition, &NumberWritten);
    Sleep(3000);

    // Check the location of the cursor according to the API.  This shows that
    // the cursor has not moved.
    GetConsoleScreenBufferInfo(ConHandle, &PostFillScreenInfo);

    // Write to the current cursor location.  This shows that the visual
    // display is right and the API is wrong - the cursor has moved.  In
    // conhost, this Y should overwrite the previous X.  In WT, the Y goes
    // off into the ether.
    WriteConsole(ConHandle, "Y", 1, &NumberWritten, NULL);
    GetConsoleScreenBufferInfo(ConHandle, &PostWriteScreenInfo);

    // According to the API, the cursor was in the same place the whole time.
    printf("\nCursor before fill at %i,%i; after fill at %i,%i; after write at %i,%i\n",
           StartScreenInfo.dwCursorPosition.X,
           StartScreenInfo.dwCursorPosition.Y,
           PostFillScreenInfo.dwCursorPosition.X,
           PostFillScreenInfo.dwCursorPosition.Y,
           PostWriteScreenInfo.dwCursorPosition.X,
           PostWriteScreenInfo.dwCursorPosition.Y);

    return 0;
}

Expected behavior
With the attached repro program, the cursor should move to the right of the line; X should be displayed, and the cursor should not move; Y should overwrite X; and the program should complete that indicates each of the three cursor locations are identical.  Note that changing the dwCursorPositionValue to be anything except the rightmost character will generate this behavior.
Actual behavior
With WT, the repro displays X, but the visual cursor moves even though the reported cursor location does not.  The next character written is presumably written to the visual cursor location, meaning that it is not displayed.  The reported cursor locations suggest the cursor has not moved, which is clearly not what is happening internally.

So, I just gave this a test on the 0.9 prereleases (you're on the selfhost program, right?) and it looks like it works properly. I suspect it was related to #4403. Thoughts?

(and in the intermediate phase, the cursor is still on top of the X)

Agree this looks fixed in 0.9.  Closing.


Handle xlogy limit

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 70.92%. Comparing base (4da44dd) to head (495a797).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

:exclamation:  There is a different number of reports uploaded between BASE (4da44dd) and HEAD (495a797). Click for more details.
HEAD has 1 upload less than BASE

Flag
BASE (4da44dd)
HEAD (495a797)

2
1

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1615       +/-   ##
===========================================
- Coverage   96.30%   70.92%   -25.39%
===========================================
  Files           8       31       +23
  Lines         406    12710    +12304
===========================================
+ Hits          391     9014     +8623
- Misses         15     3696     +3681

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

@vchuravy I apparently can't do extension packages right. Is there something obvious here setupwise i did wrong?


Chocolatey package

Hi @erri120 !
I made a chocolatey package. If you want to add it to your Readme file, it may help people.
Thanks for this software :D

nice c9ceb742372aa5aaec3f4d4232ef8d09ca6225c1


Add boolean parse

Hello, I see that many flutter users complain that they don't have a native parse for boolean, so I decided to create this feature.

Syntax Java
import java.lang.*;

public class Program {

   public static void main(String[] args) {
      System.out.println(Boolean.parseBoolean("true")); //true
      System.out.println(Boolean.parseBoolean("false")); // false
      System.out.println(Boolean.parseBoolean("TRUE")); //true
      System.out.println(Boolean.parseBoolean("FALSE")); // false
      System.out.println(Boolean.parseBoolean("0")); //false
      System.out.println(Boolean.parseBoolean("1")); // false
      System.out.println(Boolean.parseBoolean("y")); // false
      System.out.println(Boolean.parseBoolean("n")); // false
   }
}

Syntax CSharp
using System;

public class Program
{
	public static void Main()
	{
		Console.WriteLine(bool.Parse("true")); // True
		Console.WriteLine(bool.Parse("false")); // False
		Console.WriteLine(bool.Parse("TRUE")); // True
		Console.WriteLine(bool.Parse("FALSE")); // False
		Console.WriteLine(bool.Parse("0")); // FormatException
		Console.WriteLine(bool.Parse("1")); // FormatException
		Console.WriteLine(bool.Parse("y")); // FormatException
		Console.WriteLine(bool.Parse("n")); // FormatException
	}
}

Syntax Dart proposal

class Program
{
	static void Main()
	{
		print(bool.parse("true")); // True
		print(bool.parse("false")); // False
		print(bool.parse("TRUE")); // True
		print(bool.parse("FALSE")); // False
		print(bool.parse("0")); // FormatException
		print(bool.parse("1")); // FormatException
		print(bool.parse("y")); // FormatException
		print(bool.parse("n")); // FormatException
	}
}
``

/cc @lrhn

It's a valid addition. I'm not sure it's really valuable enough, but it's also very low-cost (static method, easily tree-shaken if not used).
I'd probably want the case-insensitivity to be optional, so
  external static bool parse(String source, {bool caseInsensitive = false});
  external static bool? tryParse(String source, {bool caseInsensitive = false});

Documentation should be clear that the only accepted inputs are the ASCII letter sequences "true" and "false", optionally allowing upper case letters as well as lower case, in any combination.
The important case is to recognize precisely the output of bool.toString(). Case insensitivity isn't important to me at all, and I'd be happy to not have it. If your input isn't from bool.toString(), it's custom input that could be anything.
On the other hand, without case insensitivity, it's so trivial a function that it's not particularly valuable.
The FormatException being thrown is not going to have a position, since being either true or false isn't really something that fails at a specific position (if input is "talse", where is the error?). So, not as helpful as you'd expect, unless we want to recognize case-differences and report them in case-sensitive mode.

@lrhn Thank you, I will make the suggested changes and add your caseInsensitive suggestion.
Just confirms me about the caseInsensitive  is that what you imagine?

class Program
{
	static void Main()
	{
              if(bool.parse("true")){
                //.. ok
              }

              //FormatException
              if(bool.parse("FalSe", caseInsensitive: true)){

              }
	}
}

@lrhn Thank you, I will make the suggested changes and add your caseInsensitive suggestion.
Just confirms me about the caseInsensitive  is that what you imagine?
dart
class Program
{
static void Main()
{
if(bool.parse("true")){
//.. ok
}
          //FormatException
          if(bool.parse("FalSe", caseInsensitive: true)){

          }
}

}

I'd expect no format exception when caseInsensitive is true.
It's a little iffy, because "case-insesitive" is a negative-like word, so it probably should be
bool caseSensitive = true as the default instead.
But a default of true that you change to false is also less than optimal.
I guess in this case, it's a trade-off. The more I look at it, I think I prefer
  external static bool? tryParse(String source, {bool caseSensitive = true});

@lrhn Could you check the new implementation?
Syntax Dart proposal

void main() {

  print(bool.parse("true")); // true
  print(bool.parse("false")); //false
  print(bool.parseBool("TRUE")); // FormatException
  print(bool.parseBool("FALSE")); //FormatException
  print(bool.parseBool("True", caseSensitive: false)); // true
  print(bool.parseBool("False", caseSensitive: false)); // false

}

Please add tests.
There are tests for other primitive classes, e.g. tests/corelib/double_parse_test.dart and tests/corelib/double_try_parse_test.dart.
This suggests tests/corelib/bool_parse_test.dart and tests/corelib/bool_try_parse_test.dart but I think it would be reasonable to test both methods in one file.
int.parse and double.parse are tolerant of surrounding whitespace. Should bool.parse be tolerant too?
I do not think that this function needs to have implementations specialized to the different runtimes.
Without a clear benefit (like using JavaScript number parsing on the web) this just adds maintenance burden.
Something like the following should be sufficient:
// sdk/lib/core/bool.dart

class bool {
  /// doc here
  bool parse(String source, {bool caseSensitive = true}) {
    return tryParse(source, caseSensitive: caseSensitive) ??
        (throw FormatError(...));
  }
  /// doc here
  bool? tryParse(String source, {bool caseSensitive = true}) {
    if (source == 'true') return true;
    if (source == 'false') return false;
    if (caseSensitive) return null;
    return tryParse(source.toLowerCase());
  }
}

I am not totally convinced that we should have case-insensitive parsing, but we do have case-insensitive parsing of numbers i.e. accepting numbers that would not be produced by some variant of toString().

@rakudrama , I particularly like the C# implementation a lot, it works very well.
I believe that in dart we can do something like the example below:
void main() {

      print(bool.parse("true")); // true
      print(bool.parse("false")); //false
      print(bool.parse("TRUE")); // true
      print(bool.parse("FALSE")); // false
      print(bool.parse("  True  ")); // true
      print(bool.parse("  False  ")); // false
      print(bool.parse("0")); // false
      print(bool.parse("1")); // true
      print(bool.parse(" 0 ")); // false
      print(bool.parse(" 1 ")); // true
      print(bool.parse("")); // FormatException
      print(bool.parse("truee")); //FormatException
      print(bool.parse("falsee")); // FormatException
      print(bool.parse("y")); // FormatException
      print(bool.parse("n")); // FormatException
      print(bool.parse("a")); // FormatException
      print(bool.parse("b")); // FormatException
}

About the example:
void main() {
      print(bool.parse("true")); // true
      print(bool.parse("false")); //false
      print(bool.parse("TRUE")); // true
      print(bool.parse("FALSE")); // false
      print(bool.parse("  True  ")); // true
      print(bool.parse("  False  ")); // false
      print(bool.parse("")); // FormatException
      print(bool.parse("t r u e")); //FormatException
      print(bool.parse("truee")); //FormatException
      print(bool.parse("y")); // FormatException
      print(bool.parse("0")); // FormatException
      print(bool.parse("1")); // FormatException
}

My experience from int.parse tells me that allowing leading and trailing whitespace is unnecessary and complicates the fast paths.
We have String.trim to remove the whitespace if you think you might have some, but if the parse method checks for whitespace, that's an extra overhead you can't avoid.
The one place where I'd have done something else for int.parse was that I'd allow it to parse inside an existing string, without having to create a substring. The latter is unnecessarily inefficient if you already know where the integer starts and ends in the string, which you need to know to create the substring.
That's not as important for bool.parse, because if you already know that you have a boolean substring, then just checking whether the length is 4 or 5 should tell you which one. For bool.parse, it's more likely that you will be using it on inputs that are already tokenized, and passing in the start/end in another string is not what you need.
(For performance, that would be bool parseInPlace(String source, int start, int end) => end == start + 4 ? source.startsWith("true", start) : source.startsWith("false", start);, which is a different thing.)
I'm a little split on whether case sensitivity should default to true or false. I'd like to say false to be as restrictive as possible by default, because being permissive can hide errors. But in this case, it's not like we will accept radically different inputs, and accepting True over true is only going to be a problem if you use the bool parser to validate something, like JSON, and why would you ever do that instead of using a proper tool for it like jsonDecode.
So true is probably OK.

@rakudrama , @lrhn    https://github.com/dart-lang/sdk/pull/51026/commits/779da89e5d9a85ad04760264b6033d1a6b0965c4 add the tests, sorry for the delay.

Your last comment made me sweat and it's not even sunny in Brazil 😂😂, I made the commits, could you check? thanks.

The PR is based on the dev branch, we won't be able to merge it that way. Please change this to be based of the main branch (just make sure you backup your current state in case something goes wrong):
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request

@athomas I changed.

Thanks! Gerrit CL: https://dart-review.googlesource.com/c/sdk/+/279746

@athomas, sorry I had to make an adjustment.

@athomas I changed.

@srburton please see additional feedback in https://dart-review.googlesource.com/c/sdk/+/279746


Add MIT license field

@dbrock oh woops, looks like this was added 9 months ago.
can you make a 1.0.0 release plz?


Add Signify LWS003

Device information

Philips Hue LWS003 - PAR38 White Lamp
Home Assistant Device information

Hue white lamp (LWS003)
by Signify Netherlands B.V.
Checklist

[x] I have created a single PR per device. When you have multiple submissions please create separate PR's.
[x] For lights - I have only included the gzipped files (*.gz), not the raw CSV files.
[x] For lights - I have provided a CSV file per supported color mode. Look that up in Developer Tools -> States

Additional info

I had to measure standby with a dummy load.  Philips says it's max 0.2 W in standby, I measured 0.25 W.  Part of me would default to the Philps number but I'll leave it up to you.

Thanks a lot for your contribution. LGTM! let's keep with 0.25


As a network operator, I want to experiment with Charging a % fee for a bounty that's been fulfilled

As a network operator, I want to experiment with Charging a % fee for a bounty that's been fulfilled
Ideally this could be configured on a contract by contract basis (1%, 2.5%, etc) and i would be able to specify a network operator payout address either when the bounty is posted or fulfilled.

https://github.com/gitcoinco/web/issues/959#issuecomment-385930250


Adding atomic technique/test creation functions

I've never personally found it to be easy or scalable to write atomic techniques/tests in YAML. I added the following functions to invoke-atomicredteam so that atomic techniques/tests can be developed in pure PowerShell:

New-AtomicTechnique
New-AtomicTest
New-AtomicTestInputArgument
New-AtomicTestDependency

The output of these functions are designed to be piped directly to ConvertTo-Yaml.
These functions solve the following problems for me:

Writing YAML by hand is prone to errors
The only other existing atomic YAML generation code is in the atomic-red-team repo which just generates a template YAML stub.
Previously, there existed no option to write atomic technique/tests in pure code. This allows that and validation is performed before any object is returned so that there is a relatively sage guarantee that generated YAML is conformant to the atomic schema.

Looks amazing Matt, I'll try it out tomorrow!


Changing the login wallpaper

Is your feature request related to a problem? Please describe:
In the current UI there is a box to customize the wallpaper. There is no hint about the path to the file. Ideally, this would be the homebridge storage path by default e.g. /homebridge.  it appears the default installation looks at: /usr/local/lib/node_modules/homebridge-config-ui-x/public/assets Using the storage path separates user customizations from the default install which could be overwritten during updates.
If there is a way to set the path to the storage to the storage path it isn't clear.
I also notice that even putting an image in /usr/local/lib/node_modules/homebridge-config-ui-x/public/assets and then using the ui to set an image filename doesn't seem to work. Maybe there is something that just isn't obvious about how to make this work properly.
Describe the solution you'd like:

Put some text to let the user know how to customize. Since you know the storage path, you could note that everything will go from there (i.e. include their actual storage path in the instructions). So if the user wants to just drop the image in there all they need to do is put the name (with no path). If they want it under a directory within their storage path they could put /foldername/image.jpg
Update the wiki to explain how this works.

Describe alternatives you've considered:

Another option would be to just let the user drop a file into their storage directory. If it is there, use is as wappaper. e.g. /homebridge/wallpaper.jpg would override the default wallpaper without requiring the user to set it.
Lastly, provide a filepicker to let the user choose the file and use that to set the file so users don't have to worry about relative vs absolute paths, etc.

Additional context:

Thanks. I'm probably going to go with option 2 and allow the user to upload a file.

Another option would be to just let the user drop a file into their storage directory. If it is there, use is as wappaper. e.g. /homebridge/wallpaper.jpg would override the default wallpaper without requiring the user to set it.

The wallpaper will load from <homebridge-storage-path>/ui-wallpaper.jpg if it exists. eg. /homebridge/ui-wallpaper.jpg

https://github.com/oznu/homebridge-config-ui-x/wiki/How-To-Test-Upcoming-Changes
Uploading a file will come later, it's a bit tricky to add at the moment as I'm using the automatically generated settings for for the UI still.

SWEET! Thank you. Working perfectly.


Error: environment variable not found

generated a new project with cargo generate esp-rs/esp-idf-template cargo
added rs-matter as a dependency
copied the onoff_light example code into it
used the provided command from the README.md
export MCU=esp32; export CARGO_TARGET_XTENSA_ESP32_ESPIDF_LINKER=ldproxy; export RUSTFLAGS="-C default-linker-libraries"; export WIFI_SSID=ssid;export WIFI_PASS=pass; cargo build --no-default-features --target xtensa-esp32-espidf -Zbuild-std=std,panic_abort

expected: successful build
outcome: error: failed to run custom build command for rs-matter v0.1.1
Error: environment variable not found
quite not sure which env variable is not set

Do you have the build.rs file in the root of your binary crate, as generated by esp-idf-template?
Can you paste the full build log here (please do export RUST_BACKTRACE=1 before running the build)

yeah I have the generated build.rs In my root file
// Necessary because of this issue: https://github.com/rust-lang/cargo/issues/9641
fn main() -> Result<(), Box<dyn std::error::Error>> {
    embuild::build::CfgArgs::output_propagated("ESP_IDF")?;
    embuild::build::LinkArgs::output_propagated("ESP_IDF")?;
    Ok(())
}

$ export RUST_BACKTRACE=1
$ export MCU=esp32; export CARGO_TARGET_XTENSA_ESP32_ESPIDF_LINKER=ldproxy; export RUSTFLAGS="-C default-linker-libraries"; export WIFI_SSID=ssid;export WIFI_PASS=pass; cargo build --no-default-features --target xtensa-esp32-espidf -Zbuild-std=std,panic_abort

Compiling core v0.0.0 (/Users/nick/.rustup/toolchains/esp/lib/rustlib/src/rust/library/core)
   Compiling bindgen v0.63.0
   Compiling portable-atomic v1.4.3
   Compiling embuild v0.31.3
   Compiling esp-idf-sys v0.33.2
   Compiling rs-matter v0.1.1 (/Users/nick/dev/matter/rs-matter/rs-matter)
   Compiling test-simple-api v0.1.0 (/Users/nick/dev/matter/test-simple-api)
error: failed to run custom build command for `rs-matter v0.1.1 (/Users/nick/dev/matter/rs-matter/rs-matter)`

Caused by:
  process didn't exit successfully: `/Users/nick/dev/matter/test-simple-api/target/debug/build/rs-matter-f3dfdfb42f092a00/build-script-build` (exit status: 1)
  --- stderr
  Error: environment variable not found
warning: build failed, waiting for other jobs to finish...

Make sure to have a direct dependency on esp-idf-sys and on embuild in your binary crate - even if you don't use esp-idf-sys directly.

ok finally, got it working
thanks for your work
# didnt touched things above from the template in the Cargo.toml file
[dependencies]
log = { version = "0.4.17", default-features = false }
embassy-futures = "0.1" #use embassy
async-io = { version = "=1.12" } #use async-io
esp-idf-sys = { version = "0.33", optional = true, default-features = false, features = [
    "native",
] }
esp-idf-hal = { version = "0.41", optional = true, features = [
    "embassy-sync",
    "critical-section",
] }
esp-idf-svc = { version = "0.46", optional = true, features = [
    "embassy-time-driver",
] }
embedded-svc = { version = "0.25", optional = true }
rs-matter = { path = "../rs-matter/rs-matter", default-features = false, features = [
    "esp-idf", # use needed features
] }

[target.'cfg(target_os = "espidf")'.dev-dependencies]
esp-idf-sys = { version = "0.33", default-features = false, features = [
    "binstart",
] }

[build-dependencies]
embuild = "0.31.2"

# For compatibility with ESP IDF
[patch.crates-io] # Patch crates
polling = { git = "https://github.com/esp-rs-compat/polling" }
socket2 = { git = "https://github.com/esp-rs-compat/socket2" }

only use export WIFI_SSID=ssid;export WIFI_PASS=pass; cargo build
sadly I have an out of memory error
E (902) pthread: Failed to create task!
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 12, kind: OutOfMemory, message: "Not enough space" }', src/main.rs:51:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Try to build in --release
Increase a little bit the memory in main, by 10 - 20K

Oh and one more thing: since you've created a separate binary crate - put in your Cargo.toml:
[profile.release]
opt-level = 3

[profile.dev]
debug = true
opt-level = 3

... and delete the existing ones. You really need opt-level = 3 for all the memory optimizations to kick-in. And by default, the esp-idf-template uses z and s which are not good enough. The above would also allow you to stick to debug builds.

thanks a lot, changed opt-level and after some testing, set it to .stack_size(140 * 1024) what worked now
but the search is going on 🙈
I (8259) rs_matter::transport::core: Comissioning started
I (8259) rs_matter::transport::core: Creating queue for 1 exchanges
I (8269) rs_matter::transport::core: Creating 8 handlers
I (8269) rs_matter::transport::core: Handlers size: 9992
I (8279) rs_matter::transport::core: Transport: waiting for incoming packets
I (8289) rs_matter::transport::udp::async_io: Listening on [::]:5353
I (8299) rs_matter::transport::udp::async_io: Joined IPV6 multicast ff02::fb/2
I (8299) rs_matter::transport::udp::async_io: Joined IP multicast <IP_ADDRESS>/<IP_ADDRESS>
I (8319) rs_matter::mdns::builtin: Broadcasting mDNS entry to <IP_ADDRESS>:5353
I (8329) rs_matter::mdns::builtin: Broadcasting mDNS entry to ff02::fb:5353
W (8329) rs_matter::transport::udp::async_io: Error on the network: Os { code: 118, kind: HostUnreachable, message: "Host is unreachable" }
Error: Error::Network

You are hitting #100. To workaround it, temporarily downgrade to esp idf v4.4.

After that, if you are using a Google Controller, you'll likely hit #102 as well, which we are analyzing right now.

Ok, thanks.
I tried the onoff_light example on my Host and yeah with the chip-tool everything works fine, but with Alexa I also got an error.

@Zercerium Can you try if #107 fixes the provisioning issue for you? Note that provisioning might still generate an error at the end (device not found - that's an old issue because we don't properly implement true subscriptions) but the device should afterwards be nevertheless visible.

OK the culprit is this one:
[2023-10-03T15:07:59Z ERROR rs_matter::secure_channel::case] Certificate Chain doesn't match: Invalid:
... which means it fails just before it can establish a valid CASE session, and this is very different from the problem I fixed in my branch
Can you open a new issue for this? Something like "Provisioning with Alexa/Echo Hub fails with Invalid Cert error during the Case3 step".
I still don't have an Echo device, but I'll order soon. Perhaps other folks can shed some light (@kedars?).

yeah, opened an issue for it. #109


add helper function to wait for blocks

in our current e2e tests there are cases where multiple execute messages are submitted too close to each other which causes account sequence mismatch.
to avoid that, we can poll the chain for a block height delta and block execution until some number of blocks had passed.
lets expose a wait_for_blocks method on chain/rb which will take in a u64 and sleep until that block height delta had passed.

This is necessary.
How about consider adding optional timeout parameter to the wait_for_blocks method to prevent infinite waiting when there is network issues or unexpected delays in block production?
Exactly, timeout handling is very important to implement that feature, I think


[Error] After upgrade to MediatR 9.0.0 : Unable to cast object of type 'System.Collections.Generic.IEnumerable'

I build a Web API with Asp.Net Core 5.0 and everything working fine!
But when I upgrade from MediatR version 8.0.1 to 9.0.0, I get this issue:
Error: Unable to cast object of type 'System.Collections.Generic.IEnumerable`1[MediatR.IPipelineBehavior`2[Ettip.Domain.Queries.Admin.OfficialStoryRequest.PagingStoriesByTopicsRequest,Ettip.Domain.Queries.Responses.Admin.OfficialStoriesResponse]][]' to type 'System.Collections.Generic.IEnumerable`1[MediatR.IPipelineBehavior`2[Ettip.Domain.Queries.Admin.OfficialStoryRequest.PagingStoriesByTopicsRequest,Ettip.Domain.Queries.Responses.Admin.OfficialStoriesResponse]]' - StackTrace :    at MediatR.ServiceFactoryExtensions.GetInstances[T](ServiceFactory factory)
   at MediatR.Internal.RequestHandlerWrapperImpl`2.Handle(IRequest`1 request, CancellationToken cancellationToken, ServiceFactory serviceFactory)
   at MediatR.Mediator.Send[TResponse](IRequest`1 request, CancellationToken cancellationToken)
   at Ettip.Api.Controllers.OfficialStoriesController.PagingStoriesByTopics(PagingStoriesByTopicsRequest request) in /Users/tamtang/Documents/Source Code/Ettip-Api/Ettip.Api/Controllers/OfficialStoriesController.cs:line 124
   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfIActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask`1 actionResultValueTask)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeNextActionFilterAsync>g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()
--- End of stack trace from previous location ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|24_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()
--- End of stack trace from previous location ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Logged|17_1(ResourceInvoker invoker)
   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
   at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.<Invoke>g__Awaited|6_0(ExceptionHandlerMiddleware middleware, HttpContext context, Task task)

After I check a lot of things from MediatR's wiki and search this issue from Google but I found nothing.
Finally, I have to revert my Web API to MediatR version 8.0.1 to make my Web API working again.
Does anyone know any clues to resolve this issue?
Here is my code
 public async Task<IActionResult> PagingStoriesByTopics(PagingStoriesByTopicsRequest request)
        {
            var result = await _mediator.Send(request);
       }

 public class PagingStoriesByTopicsRequest : IRequest<OfficialStoriesResponse>
    {
        public List<int> TopicIds { get; set; }
        public List<Guid> AuthorIds { get; set; }
        public int PageSize { get; set; }
        public int PageIndex { get; set; }
        public string OrderBy { get; set; }
        public string ThenBy { get; set; }
    }

public class OfficialStoriesResponse
    {
        public List<OfficialStoryModel> Data { get; set; }
        public bool CanPrev { get; set; }
        public bool CanNext { get; set; }
    }

 public async Task<OfficialStoriesResponse> Handle(PagingStoriesByTopicsRequest message,
            CancellationToken cancellationToken)
        {
             //The request could not come here after it was sent
        }

Almost identical problem here.  Did you ever solve this problem?

Today, I come back to this issue and I find out I made a very old configuration when adding MediatR on the startup file (but it's still working on MediatR 8.0.1)
Just remove these lines (if you already have them) on the startup file (when we add MediatR).
I got this issue because I was set up this project from the time .NET Core 1.0 was released (more than 5 years ago ^^)
        services.AddScoped<IMediator, Mediator>();
        services.AddTransient<ServiceFactory>(sp => sp.GetService);
        services.AddTransient<ServiceFactory>(sp => sp.GetServices);

Here is the change from my project.

Hopefully, I can help you @pathfinder8008


Helper function for analytics

Sometimes a directive isn't sufficient to capture complex analytics.  A helper function that sends the appropriate analytics attributes would be useful,

Could you provide more details?
For custom analytics I have used the avAnalytics.trackEvent function.

Below is the onEvent handler from the directive.  Notice that it defaults the level to info.  Maybe all we need is some sensible defaults in avAnalytics.trackEvent and we have a good helper function.
 onEvent(event, element, options) {

    const properties = angular.extend(
      {
        level: 'info',
        label: element.text()
      },
      {
        event: event.type
      },
      options
    );

    if (this.av.avAnalyticsUtils.isExternalLink(properties)) {
      event.preventDefault();
      event.stopPropagation();
    }

    const promise = this.av.avAnalytics.trackEvent(properties);

  }

Default values or validation make sense, but not sure what they should be other than level for splunk, which is implemented in the service.
  properties.url = $location.$$absUrl || 'N/A';
  properties.level = properties.level || 'info';

we should be good then.


[Snyk] Upgrade @elastic/elasticsearch from 7.11.0 to 7.17.14

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade @elastic/elasticsearch from 7.11.0 to 7.17.14.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 12 versions ahead of your current version.

The recommended version was released on 23 days ago.

Release notes

Package name: @elastic/elasticsearch

7.17.14 - 2024-07-02Changelog

7.17.13 - 2023-09-26

7.17.12 - 2023-07-14

7.17.11 - 2023-06-28

7.17.11-patch.1 - 2023-06-29

7.17.0 - 2022-02-02

7.16.0 - 2021-12-15

7.15.0 - 2021-09-23

7.14.1 - 2021-08-30

7.14.0 - 2021-08-11

7.13.0 - 2021-05-31

7.12.0 - 2021-03-24

7.11.0 - 2021-02-11

    from @elastic/elasticsearch GitHub release notes

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

breaking


removes max-length from profile name

What does this PR do?
Fixes #2830
Which TC components are affected by this PR?

[ ] Documentation
[ ] Grove
[ ] Traffic Analytics
[ ] Traffic Monitor
[ ] Traffic Ops
[ ] Traffic Ops ORT
[x] Traffic Portal
[ ] Traffic Router
[ ] Traffic Stats
[ ] Traffic Vault
[ ] Other _________

What is the best way to verify this PR?
Open up TP and create a new profile. There is no max-length constraint on the Name anymore.
Or try cloning a profile with a long name (45+ characters). There should be no problem anymore with the clone as indicated in #2830 .
Check all that apply

[ ] This PR includes tests
[ ] This PR includes documentation updates
[ ] This PR includes an update to CHANGELOG.md
[ ] This PR includes all required license headers
[ ] This PR includes a database migration (ensure that migration sequence is correct)
[ ] This PR fixes a serious security flaw. Read more: www.apache.org/security

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/2821/
Test FAILed.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/2928/
Test FAILed.


Support for northbound Redfish interface

Add ability to interaction to with Device Manager via a Redfish interface.  Minimal support would include

Chassis, Systems
AccountService, SessionService, TaskService, EventService

Use cases:

Obtain inventory with the Chassis and Systems resource
The AccountService, SessionService, TaskService, EventService is to pass the Redfish Service Validator (I will confirm)

Please ensure that the northbound interface should conform to the OpenRMC v1.0 profile first.  Once OpenRMC v1.1 comes out, need conformance to it as well later.

2/22 meeting - open separate issue for OpenRMC v1.0 conformance.

issue for group operations
issue for firmware update
issue for authorization of manager and managed node

Issue scoped and approved

The Redfish Protocol Validator is the test that looks for AccountService, SessionService and EventService.  TaskService is not tested.
The Protocol Validator also tests for the CertificateService, but it is arguable that belongs in the minimum set.

DM Meeting  (Mar 8):
Request Arch review for proposed code to be added to the branch.
Tests to run prior to pull request: OCP Conformance Test Suite (Service Validator, Interop Validator w/Baseline Profile, Conformance Validator) and Device Manager tests prior to pull request.

The branch 'redfishapi' has been created for a code submission.

This was fixed with #52


_exchange_table_creation_ref missing renewables

I'm guessing these may get defined elsewhere (or that renewables are not found as exchange flows in the baseline), but just checking to make sure these commented out dictionaries in upstream_dict.py are supposed to be undefined in the long if-loop checking fuel types. I'd like to remove these undefined variables and I think a quick in-line comment would suffice for their removal. Let me know and I can add it.
https://github.com/USEPA/ElectricityLCI/blob/2232c41f2cb4fd333ad59c8710aa55906e6a7ed3/electricitylci/upstream_dict.py#L116

I was going to say these seem like things I should've implemented in issues/150, but I forgot about them it seems. There's probably a thought here that implementing these commented flows would be the "right" answer, but I'm okay with something that just works right now. I say right answer because as of now, the way branch 150 works is to just add another input flow into the generation mixes that points to Construction - WIND - , resulting generation mixes with more than 100% input if that makes sense. FWIW, I'm okay leaving it as-is in favor of getting a new set of data out sooner.


install patched pgrx failed

Hi,
I can't find the issue page from https://github.com/tensorchord/pgrx so I create the related issue here.
Below is the error that I hit while install patched pgrx by cargo install --git https://github.com/tensorchord/pgrx.git --branch v0.12.0-alpha.1-patch cargo-pgrx
error[E0658]: use of unstable library feature 'proc_macro_byte_character'
   --> /home/liyang/.cargo/registry/src/index.crates.io-6f17d22bba15001f/proc-macro2-1.0.81/src/wrapper.rs:871:21
    |
871 |                     proc_macro::Literal::byte_character(byte)
    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: see issue #115268 <https://github.com/rust-lang/rust/issues/115268> for more information
    = help: add `#![feature(proc_macro_byte_character)]` to the crate attributes to enable
    = note: this compiler was built on 2024-03-26; consider upgrading it if it is out of date

error[E0658]: use of unstable library feature 'proc_macro_c_str_literals'
   --> /home/liyang/.cargo/registry/src/index.crates.io-6f17d22bba15001f/proc-macro2-1.0.81/src/wrapper.rs:898:21
    |
898 |                     proc_macro::Literal::c_string(string)
    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: see issue #119750 <https://github.com/rust-lang/rust/issues/119750> for more information
    = help: add `#![feature(proc_macro_c_str_literals)]` to the crate attributes to enable
    = note: this compiler was built on 2024-03-26; consider upgrading it if it is out of date

Did you try using --locked? It looks like a upstream issue.

Can you please try rustup update to get a 2024-04-09 compiler? And see if the problem still exists?

I met same problem yesterday,  It work for me to install pgrx using cargo install  --force<EMAIL_ADDRESS>with nightly toolchain.


Cannot cargo-install 0.10

Hi, with the recent update to 0.10, cargo install (and by extension, cargo install-update) fails:
❯ cargo install jaq
    Updating crates.io index
  Installing jaq v0.10.0
   Compiling jaq v0.10.0
error[E0106]: missing lifetime specifier
   --> /Users/knut/.cargo/registry/src/github.com-1ecc6299db9ec823/jaq-0.10.0/src/main.rs:454:58
    |
454 | fn report(e: chumsky::error::Simple<String>) -> ariadne::Report {
    |                                                          ^^^^^^ expected named lifetime parameter
    |
    = help: this function's return type contains a borrowed value, but there is no value for it to be borrowed from
help: consider using the `'static` lifetime
    |
454 | fn report(e: chumsky::error::Simple<String>) -> ariadne::Report<'static> {
    |                                                                +++++++++

For more information about this error, try `rustc --explain E0106`.
error: could not compile `jaq` due to previous error

However, running cargo build and cargo build --release from the repo works.
This might be related to https://github.com/zesterer/ariadne/pull/44 where Report got a lifetime parameter and this was just released as 0.1.6. This is arguably an issue with ariadne, I opened an issue with them: https://github.com/zesterer/ariadne/issues/69

Thanks for reporting this breaking change! Indeed, it looks like you are right about ariadne 0.1.6 being a breaking change.
In the meanwhile, you can install jaq via cargo install --locked jaq --- but note that you will not be able to use named capture groups; see here.


Missing backtick in script under Create an Image Version

The script under Create an Image Version is missing a backtick at the end of the line of the option called PublishingProfileEndOfLifeDate

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

ID: e5d2237c-1349-91a3-fefa-7f9b8f836dcd
Version Independent ID: f7cc3eb0-dbb6-a4c0-14b7-e12fd7778ff3
Content: Create an image from a VM (Preview) - Azure Virtual Machines
Content Source: articles/virtual-machines/image-version-vm-powershell.md
Service: virtual-machines
Sub-service: imaging
GitHub Login: @cynthn
Microsoft Alias: cynthn

@cesar-younes Thanks for catching that! I filed a pull request to add in the back-tick. Thanks!
https://github.com/MicrosoftDocs/azure-docs-pr/pull/113964

#please-close


Problem with PyJWT 2.10: Subject must be a string

Bug description
When setting up a fresh sandbox environment, PyJWT 2.10 gets installed, released on Nov 17, i.e. three days ago. That breaks a little integration test suite we are running [^1]. This is the exception being raised:
AssertionError: {'msg': 'Subject must be a string'}

When downgrading to use pyjwt<2.10, the test suite succeeds again.
You may want to accompany this by potentially adjusting dependencies or code in Apache Superset?
[^1]: ... which orchestrates CLI invocations of the superset program and HTTP calls to the Superset API, in order to validate it works well together with CrateDB.
Superset version
3.x and 4.x
Additional context
The software test suite maintained here can be used to reproduce the problem.

https://github.com/crate/cratedb-examples/tree/main/application/apache-superset

We added relevant details to this ticket, where we started to investigate this issue.

https://github.com/crate/cratedb-examples/issues/741

Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

We just found this is most likely the root cause.

https://github.com/jpadilla/pyjwt/issues/1017

The canonical recommendation is to downgrade to PyJWT in the meanwhile.
pip install 'pyjwt<2.10'

That patch submitted by Dependabot also demonstrates the problem.

https://github.com/crate/cratedb-examples/pull/744

@jkogut: Do you have any idea why only we might be affected, but Superset's test suite seems to still succeed, and nobody else seems to be tripped? Is it related to the value of the SECRET_KEY maybe?

@amotl yes indeed that was caused by the incorrect SECRET_KEY. Happened during test migration of superset instance. So indeed please double check SECRET_KEY. 🙏

@amotl actually I was wrong, correct SECRET_KEY only allowed me to get access token but cannot proceed further with getting chart list for instance:
def get_chart_list():
    headers = {
        'Authorization': f"Bearer {get_bearer_token()}"
    }
    response = requests.get(f"{base_url}/chart/", headers=headers, verify=False)
    return response.json()

problem observed as reported on Superset 3.1.3, and fixed as recommended with installing PyJWT==2.9.0.
So still looks like new PyJWT 2.10.0 release can cause some problems with Superset API access.

We re-generated the value for SECRET_KEY using openssl rand -base64 42, but it did not improve the situation.

Summary

Relevant change: https://github.com/jpadilla/pyjwt/pull/1005
Problem report: https://github.com/jpadilla/pyjwt/issues/1017
Solution: https://github.com/vimalloc/flask-jwt-extended/issues/556
Downstream reports:

https://github.com/vimalloc/flask-jwt-extended/issues/561
https://github.com/yunojuno/django-request-token/issues/65

Downstream patches:

https://github.com/vimalloc/flask-jwt-extended/pull/562

Evaluation
Because Apache Superset is based on Flask-AppBuilder, which in turn pulls in Flask-JWT-Extended, we guess the most recent release 4.7.1 resolves this problem already.

We can still observe the problem, even after upgrading to Flask-JWT-Extended 4.7.1.
$ uv pip install --upgrade "Flask-JWT-Extended>=4.7.1" "flask<3"
 - flask-jwt-extended==4.7.0
 + flask-jwt-extended==4.7.1

pytest -k api

            response = requests.delete(resource_to_delete, headers=get_auth_headers())
>           assert response.status_code in [200, 404], response.json()
E           AssertionError: {'msg': 'Subject must be a string'}
E           assert 422 in [200, 404]
E            +  where 422 = <Response [422]>.status_code

conftest.py:74: AssertionError

/cc @jlucier, @vimalloc

Have you configured flask-jwt-extended to not verify the sub claim. 'JWT_VERIFY_SUB=False'?

Thank you so much for your quick response, @jlucier. Actually, we are just approaching this problem as users of Apache Superset, not having any knowledge about its code base and its dependencies at all, other than knowing a bit about Flask.
We found that Flask-JWT-Extended is being used by Flask-AppBuilder, so this is probably the right spot to address this configuration update needed for the most recent PyJWT library? In this spirit, we figure creating a corresponding issue over there makes sense?

https://github.com/dpgaspar/Flask-AppBuilder/issues/2287

/cc @dpgaspar

Since my patch, this isn't a problem with flask-jwt-extended anymore.  That's your choice to make, not the library's.

As a user of Apache Superset, I am not touching JWT concerns at all, so I can't make any choices about how JWT is used by its ingredients. In this case, I guess it will be the concern of Flask-AppBuilder to configure Flask-JWT-Extended correctly, that's why I created a ticket there, but I may be wrong.

All right, I wasn't aware that JWT_VERIFY_SUB = False could easily be configured within the Flask application configuration file, which is effectively the superset_config.py file in our case.
After getting it right, this update perfectly resolves the problem we have been observing.

https://github.com/crate/cratedb-examples/pull/749

Thank you so much! 💯

@amotl are we good to close this then, if your problem is solved? If you think there's a good way/place to capture this in the docs, let us know or open a PR, it'd be appreciated!

Hi Evan. Thanks for your reminder. I guess it will be good to close. As it turned out it might have only been a niche thing tripping us, I think having it documented on behalf of this very ticket will be good enough to support others being tripped by the same thing.
Thanks for and keep up your excellent work on Superset and Preset.

Even after downgrading the pyJWT version to 2.9.0 ,I'm still facing this issue.
{'msg': 'Subject must be a string'}. @amotl

Hi , by any chance do we have steps documented for solution. how and where we can set configure 'JWT_VERIFY_SUB' to be False


Add stop command for docker.

Is your feature request related to a problem? Please describe.
There is no stop command for docker operator.
Describe the solution you'd like
Added stop command for docker.
Describe alternatives you've considered
None
Additional context
None

@alifiratari
Your PR was merged. I am closing this issue as completed.
Again, thanks for the PR.


lifecycle events as attributes?

I've been thinking about this a bit lately. The only reason you would ever need a class-based component (with a redux-style architecture) is if you need the lifecycle events.
The lifecycle events seem awfully similar to the onClick, onMouseDown event handlers, so I'm wondering if it would be possible to include those events like onMount as attributes on the vnodes?
Maybe they would only work on the component level, but with mutation observers, I think they could work on any element. Here's some repos I've used in the past for the mutation events:

mount: https://github.com/component/inserted
unmount: https://github.com/component/removed

Hey Matt,
Been thinking about this myself a bit too! It's probably not worth noting that the ref prop can be used as a mount lifecycle hook (though obviously the signature is slightly different). The timing semantics are pretty much a perfect match :o

Just thought up an implementation that works using a standard vnode hook:
import { options } from 'preact';

let hook = options.vnode;
options.vnode = vnode => {
  let attr = vnode.attributes;
  if (typeof vnode.nodeName==='string' && attr && (attr.onMount || attr.onUnmount)) {
    attr.ref = createMountRef(attr.ref, attr.onMount, attr.onUnmount);
  }
  hook && hook(vnode);
};

function createMountRef(oldRef, onMount, onUnmount) {
  let prev;
  return c => {
    if (prev && prev!==c && onUnmount) onUnmount(prev);
    if ((prev=c) && onMount) onMount(c);
    if (oldRef) oldRef(c);
  };
}

It would invoke onMount and onUnmount with the mounted/unmounted element or component instance:
const Foo = () => (

 console.log('mounted: ', div) }
      onUnmount={ div => console.log('un-mounted: ', div) }
    />
    <Bar
      onMount={ bar => console.log('mounted: ', bar) }
      onUnmount={ bar => console.log('un-mounted: ', bar) }
    />

);

render(<Foo />);

The nicest part about this is that there is no observers or DOM stuff needed.  Preact just invokes the ref hooks when adding and removing elements/components, so we can hijack that for the purpose of lifecycle events.

@matthewmueller also: I wonder if it would be better to just steal the corresponding lifecycle method names from the Web Components spec?

 console.log('instantiated') }
  attachedCallback={ () => console.log('mounted') }
  detachedCallback={ () => console.log('unmounted') }
/>

Then we could really start to look into making Preact a mechanism for building and shipping Web Components...

hahaha awesome! i literally was writing something like this, walking the vnodes:
gah, i think i understand the options.vnode thing now too, so it's called by core preact before preact renders to dom or to string? if i'm understanding that properly, i think that could clean up this: render(mountables(effects(styles(App({ url }), css))), document.body)
this is so great cause you can also do things like, apply all styling right before rendering and insert your redux dispatchers in all event handers :-D

couldn't have said it better myself ;)
options.vnode is crazy, and maybe scary, but also insanely powerful. It gives you absolute control over every virtual dom node preact creates.

ahh cool yah, those names are pretty goofy, but i definitely think it's better to use a standard name vs something arbitrary.

Here's a HOC that implements the above (no classes still!):
import { cloneElement } from 'preact';

const On = ({ create, mount, unmount, children }) => {
  if (create) create();  // this one might be silly actually
  let inst;   // tracks current element/component
  return cloneElement(children[0], {
    // we just render the child (HOC style) but override `ref`:
    ref(c) {
      if (inst && unmount) unmount(inst);
      if ((inst=c) && mount) mount(inst);
    }
  });
};

render(
  <On mount={()=>log('mounted')} unmount={()=>log('unmounted')}>

I'm passed to mount/unmount!

  </On>
);

ahh sweet, i wonder if that would muck with inputs at all? i don't really use the ref stuff that much  anyway though.
so it's standalone if they're composed functions that walk & transform the vnodes.
function clickable (vnode) {
  walk(vnode, function (node) {
    if (node.attributes && node.attributes.onClick) {
      let original = node.attributes.onClick
      node.attributes.onClick = function (e) {
        original(e, (l) => console.log('here!', l))
      }
    }
  })
  return vnode
}

function walk (vnode, fn) {
  if (!vnode.children) return fn(vnode)
  for (let child of vnode.children) {
    walk(child, fn)
  }
  fn(vnode)
}

one thing to consider that is probably not a big deal with the options thing, is that it's a singleton affecting all instances of render. i think the most flexible is either the HOC or something like this:
const transform = compose(mountables(), effects(), styles(css))
render(transform(App({ url })), document.body)

Yep - the singleton thing is for sure the drawback.  It's possible to use a global flag to enable your hook only during a render (since render itself is synchronous).  I'm definitely liking the HOC, it seems pretty clean.  Shouldn't be any trouble with inputs that I'm aware of.
I like the separation you're able to achieve with the transform() step, just thinking it'd be able to support subtree re-rendering if done via the HOC or hook.

ahh i haven't gotten that far yet haha, yah that's a big problem. definitely liking the HOC approach the most then!

insane thing to try: replace a vnode with a vnode that contains that vnode 😈

@matthewmueller yeah, you can reach into the original props and invoke it:
const On = ({ mount, unmount, children:[child] }) => {
  let inst, oldRef = child.attributes && child.attributes.ref;
  return cloneElement(child, {
    ref(c) {
      if (inst && unmount) unmount(inst);
      if ((inst=c) && mount) mount(inst);
      if (oldRef) oldRef(c);
    }
  });
};

awesomeee. so i think this is best left outside of core, despite it being pretty great. i also sort of think that the class stuff could actually be moved to preact-compat :-P
closing! unless you'd like to keep it open :-)

for what it's worth, this is what I settled on for functional components:
  return function mounts (node) {
    let attrs = node.attributes
    if (!attrs) return
    else if (!attrs.onMount && !attrs.onUnmount) return

    // create a mount using the ref
    let ref = node.attributes && node.attributes.ref

    node.attributes.ref = (el, send) => {
      const parent = el && el.parentNode

      if (attrs.onMount && el && !parent) {
        // when initially mounted, el will
        // exist but there won't be a parent
        // we want to defer to ensure that
        // the dimensions have been calculated
        defer(function () { attrs.onMount(el, send) })
      } else if (attrs.onUnmount && !el && !parent) {
        // when unmounting, both el and
        // the parent will be null.
        defer(function () { attrs.onUnmount(null, send) })
      }

      // call original ref, if there is one
      ref && ref(el, send)
    }
  }

The problem I ran into with the previous approaches in the functional case was that inst would get reset and onMount would get called every re-render. By checking the actual element, it will only get called when the element is added and removed.

Just thought up an implementation that works using a standard vnode hook:
import { options } from 'preact';

let hook = options.vnode;
options.vnode = vnode => {
  let attr = vnode.attributes;
  if (typeof vnode.nodeName==='string' && attr && (attr.onMount || attr.onUnmount)) {
    attr.ref = createMountRef(attr.ref, attr.onMount, attr.onUnmount);
  }
  hook && hook(vnode);
};

function createMountRef(oldRef, onMount, onUnmount) {
  let prev;
  return c => {
    if (prev && prev!==c && onUnmount) onUnmount(prev);
    if ((prev=c) && onMount) onMount(c);
    if (oldRef) oldRef(c);
  };
}

It would invoke onMount and onUnmount with the mounted/unmounted element or component instance:
const Foo = () => (

 console.log('mounted: ', div) }
      onUnmount={ div => console.log('un-mounted: ', div) }
    />
    <Bar
      onMount={ bar => console.log('mounted: ', bar) }
      onUnmount={ bar => console.log('un-mounted: ', bar) }
    />

);

render(<Foo />);

The nicest part about this is that there is no observers or DOM stuff needed. Preact just invokes the ref hooks when adding and removing elements/components, so we can hijack that for the purpose of lifecycle events.
Even more interesting: if you pass onMount / onUnmount to a Pure Functional Component, it still functions perfectly, and your lifecycle handlers are given a reference to the created DOM element (even for deeply nested high order functional components!).

Just thought up an implementation that works using a standard vnode hook:
import { options } from 'preact';

let hook = options.vnode;
options.vnode = vnode => {
  let attr = vnode.attributes;
  if (typeof vnode.nodeName==='string' && attr && (attr.onMount || attr.onUnmount)) {
    attr.ref = createMountRef(attr.ref, attr.onMount, attr.onUnmount);
  }
  hook && hook(vnode);
};

function createMountRef(oldRef, onMount, onUnmount) {
  let prev;
  return c => {
    if (prev && prev!==c && onUnmount) onUnmount(prev);
    if ((prev=c) && onMount) onMount(c);
    if (oldRef) oldRef(c);
  };
}

It would invoke onMount and onUnmount with the mounted/unmounted element or component instance:
const Foo = () => (

 console.log('mounted: ', div) }
      onUnmount={ div => console.log('un-mounted: ', div) }
    />
    <Bar
      onMount={ bar => console.log('mounted: ', bar) }
      onUnmount={ bar => console.log('un-mounted: ', bar) }
    />

);

render(<Foo />);

The nicest part about this is that there is no observers or DOM stuff needed. Preact just invokes the ref hooks when adding and removing elements/components, so we can hijack that for the purpose of lifecycle events.
Even more interesting: if you pass onMount / onUnmount to a Pure Functional Component, it still functions perfectly, and your lifecycle handlers are given a reference to the created DOM element (even for deeply nested high order functional components!).

Hi @developit , i am using below code in our project:-
import { options } from 'preact';

let hook = options.vnode;
options.vnode = vnode => {
let attr = vnode.attributes;
if (typeof vnode.nodeName==='string' && attr && (attr.onMount || attr.onUnmount)) {
attr.ref = createMountRef(attr.ref, attr.onMount, attr.onUnmount);
}
hook && hook(vnode);
};

When i check the options.js in Preact library, there is only export default { //some comments }. Now we have decided to move from preact to react, but there is no options.js in react library. Any suggestion how i can come over this problem?? Any alternative to options.vnode?


WIP: PWN-4121 - "Cannot send the selected token" error fix

Jira Ticket
https://p2pvalidator.atlassian.net/browse/PWN-4121
Description of Work
[ what work was done in this ticket ]
Screenshots (Optional)

Screenshot #1
Screenshot #2
Screenshot #3

[Paste Pic 1]
[Paste Pic 2]
[Paste Pic 3]

done in other pull request


tot_dfs() got an unexpected keyword argument 'confidence_threshold'

Getting few errors likes this, should I fix it?
tree-of-thoughts\tree_of_thoughts\treeofthoughts.py", line 45, in solve
result = self.tot_dfs(initial_prompt, num_thoughts, max_steps, value_threshold,
TypeError: tot_dfs() got an unexpected keyword argument 'confidence_threshold'

@claudiobottari I have got bunch of those, too :( Basically self.tot_dfs and self.tot_bfs have a set of different arguments and no unified wrapper around them, so I edited the TreeofThoughts class source file in my conda environment

Yeah changed 1, can you go deeper on number 2?

Hi, I'm the first author of ToT paper. please note the official implementation to replicate paper results is https://github.com/ysymyth/tree-of-thought-llm


"Block of text" formatting object

Similar to #3, embedding a block of text free from any particular question.
#4 particularly important for such an object

Wrong repo


Evaluate mobile experience in manager

Describe requirements
Manager is mobile responsive but in portrait mode Tablets and in smaller devices the experience is pretty basic, Tables tools are not available, wondering if we can look into adding the table tools for mobile device use.
We will need design from IA team for this

Alternatives
No response
Other Relevant Info
No response
Impact
No response

cc @sarahmcdonald7


idx.dev @url referencing fails

Which API Provider are you using?
OpenRouter
Which Model are you using?
Claude 3.5 Sonnet
What happened?
Unable to reference URL's on idx.dev enviroment. Following error is thrown:
Error fetching content for https://github.com/X/X/blob/main/custom_components/X/config_flow.py: Failed to launch the browser process! /home/user/.codeoss-cloudworkstations/data/User/globalStorage/saoudrizwan.claude-dev/puppeteer/.chromium-browser-snapshots/chromium/linux-1366715/chrome-linux/chrome: error while loading shared libraries: libglib-2.0.so.0: cannot open shared object file: No such file or directory TROUBLESHOOTING: https://pptr.dev/troubleshooting
Steps to reproduce

Start idx.dev enviroment
Install Cline, config Cline.
Try to reference URL in the chat with @URL command.

Relevant API REQUEST output
No response
Additional context
No response

Thanks for reporting, will look into this!

This started happening to me today, however, everything was working fine yesterday. Using Gemini-flash-002. At first it couldn't access anything for context including local files. After reopening the project in idx, it was able to see the project/local files, but still can't access URL's.


XFA - Remove empty pages

it aims to fix #13583;
because hidden subform and breakBefore some pages can be empty so remove them;
don't fail when there is horizontal overflow (except in lr-tb);
fix a typo in radial gradient first argument.

/botio test

There is a regression with imm1344e.pdf.

/botio test

The differences for xfa_bug1716816 are expected.

/botio test

/botio test

/botio test

/botio makeref


Missing model_best.pth.tar???

hello, when I run this command: python run/pose2d/valid.py --cfg experiments-local/mixed/resnet50/256_fusion.yaml
I meet this error : FileNotFoundError: No such file ro directory, 'output/mixed/multiview_pose_resnet_50/256_fusion/model_best.pth.tar.
could you tell me why? Thank you very much.

You can download the model for resnet152/320_fusion.yaml here

Hello,
The download link seems invalid. It appears to be visible to a closed group of people so anonymous download is not possible.
Any chance of fixing this? I have the same error.

you can download by the link : https://drive.google.com/file/d/1TsjMOXUEZc-goGRqdS891ZgzltDR9_Yc/view?usp=sharing
At 2020-10-05 00:45:52, "rhljajodia"<EMAIL_ADDRESS>wrote:
Hello,
The download link seems invalid. It appears to be visible to a closed group of people so anonymous download is not possible.
Any chance of fixing this? I have the same error.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

you can download by the link : https://drive.google.com/file/d/1TsjMOXUEZc-goGRqdS891ZgzltDR9_Yc/view?usp=sharing At 2020-10-05 00:45:52, "rhljajodia"<EMAIL_ADDRESS>wrote: Hello, The download link seems invalid. It appears to be visible to a closed group of people so anonymous download is not possible. Any chance of fixing this? I have the same error. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

Hi，I downloaded the file. But it seems to be corrupted and I cannot unzip it. Could you please check the file?

Hello,
The download link seems invalid. It appears to be visible to a closed group of people so anonymous download is not possible.
Any chance of fixing this? I have the same error.
@ChenConnie have you managed to fix this? any chance you could help me?

Did you download the file in the new link?  Is it normal? I can't unzip it.

This link also seems to be invalid, can you please provide another one? Thanks!


flip relationship by predicate

run a predicate function to flip parent child relationships

I think this is now possible with #5


PYIC-7207: Remove context for F2F enabled/disabled

DO NOT MERGE UNTIL WELSH TRANSLATIONS ARE DONE
Proposed changes
What changed
Change routing to page-multiple-doc-check so it is the same whether f2f is enabled or not. Change routing from page-multiple-doc-check so it goes to the PYI escape page if F2F is disabled.
Why did it change
New designs from UCD to simplify the flow
Issue tracking

PYIC-7207

Looks good, HOLD until we add Welsh translations

Yes, I think so. The change in this PR is to initially go to a page that works whether F2F is disabled or not. That page then routes the user based on whether F2F is disabled or not. So we're not removing the check, we're just moving it.


Create Listening History

This should probably be stored on backend

Yea if you guys track this stuff you can build a log that you send to backend once every couple of http reuqesrs


Problem with Server

Everything works fine with my server, i port forwarded it, and everything and set exceptions for the firewall and everything. EVRYTHING WORKS FINE... BUT... MY FRIENDS CANT JOIN AND EVEN MY BROTHER IN THE SAME HOUSE!!! it worked fine without rocket, and when installed rocket (new folder and game files) only i can join my server and noone else!
Any solutions/comments i appreciate!!

I dont believe that this is a rocket issue, do you have any plugins setup?

Same for me. But when I turn off windows firewall players can join the server, I have all exeptions...

Well then please make sure to forward all ports (27015,27016,27017)

...

Ok guys, I've fixed it. I just turned off and then turn on windows firewall and it's fixed lol :D


[Event request] Codeunit 90 PostSalesTaxToGL

To migrate a NAV ISV add-on to BC:
In the function PostSalesTaxToGL, we need an event right before “GenJnlPostLine.RunWithCheck(GenJnlLine);” that passes the GenJnlLine variable.
OnPostSalesTaxBeforePost(GenJnlLine);

Some of my issues newer than this one have been looked at/addressed, so i just want to check if this one is still going to be looked at.  We're hoping to be able to release our app for the May release.


Visualization cytoscape

this is the visualization class of PySB models. To run the models it is necessary to have cytoscape open

There are some files that depend on earm being installed. Maybe you can use the earm from examples?
Also there is a place where you set parameters from your local directory path. Will default parameters work?

@JamesPino Thanks for the comments.  I changed the code to use earm1.0 and the default parameters. What do you mean that i need to helper_functions to path?

I thought the previous travis test showed that it failed because there wasn't a module 'helper_functions'. You might have already changed it to pysb.tools.helper_functions. I can't seem to find the error in the output anymore.
I do see that it failed with no module PIL.
 File "/home/travis/build/LoLab-VU/pysb/build/lib/pysb/tools/model_visualization.py", line 15, in <module>     from PIL import ImageFont ImportError: No module named PIL
I'll keep looking. Maybe that was something else

You were right. I already fixed the PIL ImportErro, the error that throws now is related to cytoscape, as it needs to be open to run the code. I think @alubbock said that it is not possible to get rid of that error because there is no a headles cytoscape. However, i found this version: https://github.com/cytoscape/cytoscape-headless-distribution should i try to use it?

It looks like it isn't being developed any more. I wonder if turning of tests for that in Travis is the short term solution? Since it is specific for a tool.


Don't use a flowchart image; it's misleading

Please reconsider the use of a flowchart as the image choice for this markdown reference page. Many systems actually support flowcharting within markdown, most often Mermaid.
Demo page
Mermaid
It would be better if you supported it, but in the meantime, the image makes it look like you handle that when you don't.
-Mat

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

ID: fa622358-f5bb-1f5c-177a-081a37b6acef
Version Independent ID: 72f7fd16-a822-66c8-3a34-8905645ce5f2
Content: Syntax usage for Markdown files, widgets, wikis, and pull requests - VSTS & TFS
Content Source: docs/project/wiki/markdown-guidance.md
Product: devops
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@matchavez  - Thank you for the feedback. I've updated the image accordingly.

Unfortunately, it has not changed. I gave it a few hours, but it still appears to show a flowchart as an image... I wouldn't consider this closed.


Add [LGTM] service

This PR adds the lgtm.com alerts count for a particular project, using the public-facing API.
Full disclosure, I work at Semmle on lgtm.com.

Messages

:book:

:sparkles: Thanks for your contribution to Shields, @samlanning!

:book:

Thanks for contributing to our documentation. We :heart: our documentarians!

  Generated by :no_entry_sign: dangerJS

Addressed comments :)

nice one - thanks


eBPF programs require kernel config

Describe the bug
In order to determine whether or not eBPF (or particular versions of eBPF) is supported, software typically checks a few places to discover a kernel configuration: /proc/config.gz, /boot/config, etc...
AFAICT, this is not available in the VM Orbstack creates for Docker.
To Reproduce

Run https://github.com/parca-dev/parca-agent on Orbstack (I'm deploying it via Kubernetes/kind).
Observe this error message: parca-agent-rsrl4 parca-agent level=warn name=parca-agent ts=2023-08-22T16:15:43.268816409Z caller=main.go:395 msg="failed to determine if eBPF is supported, host kernel might not support eBPF" err="kernel config not found, tried paths: /proc/config.gz, /boot/config, /boot/config-6.4.10-orbstack-00066-ga79fe089e66c"

Expected behavior
I think it makes the most sense that /proc/config.gz but present because it's both gzipped and in the /proc fs. /boot doesn't exist in the Docker VM created by Orbstack, so that's probably not the best one to be available.
Diagnostic report (required)
OrbStack info:

Version: 0.16.1 (160100)
Commit: 4235b341267c814080ec0e117d1e680d8f8f8676 (v0.16.1)

System info:

macOS: 13.5 (22G74)
CPU: arm64, 10 cores
CPU model: Apple M1 Max

Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2023-08-22T16-36-25.144116Z.zip

Screenshots and additional context (optional)
No response

Added for the next version.

Released in v0.17.0.

level=info name=parca-agent ts=2023-08-30T21:59:46.820024717Z caller=main.go:397 msg="eBPF is supported and enabled by the host kernel" 💥
Thanks for the super quick response time!


All questions mandatory

All question are marked as mandatory in the JSON and on the the Website with * but there is no warning or error when leaving questions blank.  It counts as 0.

Need to look at overall behavior desired. Marked as mandatory was when we required all questions to be so.  Introducing a back and forth user navigation and a by page display required to bypass the mandatory flags. Logic to be reviewed.

Suggested behaviour: can't see results unless all questions in section are answered. This way submit fully answered section only.

Incorporate in #50


Student Voice

A page where students can anonymously share good stuff or pain points that they experience at Stamford.
Others can read, upvote, downvote, and comments.

can this be somehow integrated with https://bananagram.vercel.app


Aliases mess up coverage

Using aliases messes up the coverage.
In load_files the table name is not the same for catalog & manifest, as such when doing manifest.XXX.get(table_name, {}) it returns nothing.
This comes from the fact that in Table.from_node() the Table is initialized with the alias instead of the model name.
One simple solution would be to use the unique_id as identifier.
It means:

changing Manifest.full_table_name to return table["unique_id"].lower()
changing Table.from_node to return Table(node["unique_id"], ...)

Thanks for the suggestion @Mavtti!
@sweco I guess this is something worth thinking about for the future -- aliases are a pretty nice feature worth supporting 🙂

@Mavtti I believe with the new release, we should be closer to this than ever. Would you be up for sending a quick PR that would refactor the behaviour of Table.from_node()?
Thanks!


[ZEPPELIN-2708][DOCS] feat: Add v scroll to setup, usage menus in navbar

What is this PR for?
Added v scroll to setup, usage menus in the navbar.
Because some users are experiencing trimmed menus (not sure exact OS, browser versions, See the JIRA issue)
What type of PR is it?
[Bug Fix | Improvement]
Todos
DONE
What is the Jira issue?
ZEPPELIN-2708
How should this be tested?

cd docs/
run: bundle exec jekyll serve --watch

Screenshots (if appropriate)
Before (no scrollbar)

After

Questions:

Does the licenses files need update? - NO
Is there breaking changes for older versions? - NO
Does this needs documentation? - NO

Now it works perfectly 👍
LGTM!

@tae-jun Thanks for the quick review!
Merge if no more discussion.

Cool! it looks better than before. LGTM


Typo-fix: ascii command

This should now be right. If it’s not correct me please ^^

Looks great, good change :)


Cannot compile the package

I download the "convenience-pkgs" in my catkin space and try to compile it. But I got the following error:
[ 43%] CMakeFiles/mesh_converter.dir/src/converter.cpp.o: In function convert(std::string const&, std::string const&, std::string const&)': converter.cpp:(.text+0x48c): undefined reference to Assimp::Importer::Importer()'
converter.cpp:(.text+0x49f): undefined reference to Assimp::Importer::ReadFile(char const*, unsigned int)' converter.cpp:(.text+0x4b5): undefined reference to Assimp::Exporter::Exporter()'
converter.cpp:(.text+0x4cd): undefined reference to Assimp::Exporter::Export(aiScene const*, char const*, char const*, unsigned int)' converter.cpp:(.text+0x50d): undefined reference to Assimp::Exporter::~Exporter()'
converter.cpp:(.text+0x517): undefined reference to Assimp::Importer::~Importer()' converter.cpp:(.text+0x74c): undefined reference to Assimp::Importer::~Importer()'
converter.cpp:(.text+0x76c): undefined reference to `Assimp::Exporter::~Exporter()'
collect2: error: ld returned 1 exit status
make[2]: *** [/home/administrator/wspace/devel/lib/assimp_mesh_converter/mesh_converter] Error 1
make[1]: *** [convenience-pkgs/assimp_mesh_converter/CMakeFiles/mesh_converter.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
Did I do something wrong or miss some steps?
Thank you!

Hi,
This is because a new dependency of the new package assimp_mesh_converter. Installation instructions will be updated shortly.
Meanwhile, you can either install assimp (ubuntu package assimp-dev) or remove  the folder assimp_mesh_converter from the cloned repo.
Cheers
Jennifer

Oh, just saw it is a linker error. I'll check on this again when I get to my laptop.

Hey,
I'm guessing it is a search path missing in the Findassimp.cmake, because you must have the assimp-dev package (otherwise the compiler would complain before the linker)... essentially, the path to the library is probably not in the cmake variable ASSIMP_LIBRARIES on your system.
Can you please post the output of locate libassimp.so? Which Linux OS are you using, e.g. which ubuntu version?
If you don't need the assimp_mesh_converter, just delete the directory. I'll probably move it somewhere else some time soon anyway, it's new and I have just put it in convenience-pkgs for now. Anyway, it would still help me fix the issue if you let me know which system you are using, thanks!
Jennifer

I am using Ubuntu 14.04 and here is the output of locate libassimp.so:
/usr/lib/libassimp.so
/usr/lib/libassimp.so.3
/usr/lib/libassimp.so.3.0.1264

Ok, that's odd. I have the same system configuration so I've done a complete fresh re-build to see if I can reproduce it, and then got the same issue. Compiling a second time then fixed it. But that's not how it should be, so I fixed the problem in the cmake files.
The problem was that on the first compiler run, ASSIMP_LIBRARIES was not set, only ASSIMP_LIBRARY. Then on the second compile run, both variables were set. Another one of my packages must cache the cmake variable, not sure how the whole process works, but that's the only explanation I have at this point ;)
I've added both variables to the link target and now it compiles on the first run as well.
Can you try again and let me know if it works for you as well now?
Cheers
Jennifer

Assuming this has been fixed, please re-open if not.


chore(deps): update module github.com/onsi/gomega to v1.36.2

This PR contains the following updates:

Package
Type
Update
Change

github.com/onsi/gomega
require
patch
v1.36.1 -> v1.36.2

Release Notes

onsi/gomega (github.com/onsi/gomega)
v1.36.2
Compare Source
Maintenance

Bump nokogiri from 1.16.3 to 1.16.5 in /docs by @dependabot in https://github.com/onsi/gomega/pull/757
Bump github.com/onsi/ginkgo/v2 from 2.20.1 to 2.22.1 by @dependabot in https://github.com/onsi/gomega/pull/808
Bump golang.org/x/net from 0.30.0 to 0.33.0 by @dependabot in https://github.com/onsi/gomega/pull/807
Bump google.golang.org/protobuf from 1.35.1 to 1.36.1 by @dependabot in https://github.com/onsi/gomega/pull/810

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 58.885%

Totals

Change from base Build<PHONE_NUMBER>9:
0.0%

Covered Lines:
1246

Relevant Lines:
2116

💛  - Coveralls


Bluetooth connection without using an app (IDFGH-11013)

Is your feature request related to a problem?
I want to connect my esp32 with cell phone without using an app. I don't want to exchange any data, i just only want to connect it. Is this possible?
Describe the solution you'd like.
If yes, kindly elaborate how can i achieve this task?
Describe alternatives you've considered.
No response
Additional context.
No response

@Talha-Babar
Hi,ESP32 supports classic Bluetooth and low-energy Bluetooth. Do you want to use classic Bluetooth or low-energy Bluetooth?
If you are using BLE, you can refer to esp-idf/examples/bluetooth/bluedroid/ble/gatt_security_server. With an Android phone, you can directly discover the device and initiate a connection.

Thanks for reporting, will close due to inactivity, feel free to reopen with more updates.


SSL mode is not being parsed

Hi,
I'm struggling to set up a connection to a Postgresql database that requires ssl.
I've configured the JDBC URL as: jdbc:postgresql://localhost:5432/datahub?sslmode=require
However, the app fails with the following error:
[info] com.github.mauricio.async.db.postgresql.exceptions.GenericDatabaseException: ErrorMessage(fields=Map(Line -> 481, File -> auth.c, SQLSTATE -> 28000, Routine -> ClientAuthentication, Message -> SSL connection is required. Please specify SSL options and retry., Severity -> FATAL)) [info] 	at com.github.mauricio.async.db.postgresql.PostgreSQLConnection.onError(PostgreSQLConnection.scala:175) [info] 	at com.github.mauricio.async.db.postgresql.codec.PostgreSQLConnectionHandler.channelRead0(PostgreSQLConnectionHandler.scala:206)
This is strange, because the implementation of ParseURL seems correct. I've created a small test class with this line of code:
val configuration = com.github.mauricio.async.db.postgresql.util.URLParser.parse("postgresql://localhost:5432/datahub?sslmode=require")
^ this will parse the ssl mode correctly.
I've run a debugger session in IntelliJ and put a breakpoint on com.github.mauricio.async.db.postgresql.util.URLParser in the assembleConfiguration.
But it seems this method is never invoked.
I put another breakpoint in PostgreSQLConnectionHandler, method initChannel (line 89) where I can view the parsed configuration. It turns out that database = Some(datahub?sslmode=require) and SSLConfiguration = (disable,None).
Can it be, that some other Parse method is being used? Can this be configured somewhere?
I spend quite some time debugging this, but I am unsure where to look further.
Versions:
val akkaVersion = "2.5.3"
"com.typesafe.akka" %% "akka-persistence" % akkaVersion,
"com.okumin" %% "akka-persistence-sql-async" % "0.4.0",
"com.github.mauricio" %% "postgresql-async" % "0.2.21",

@rolanddb This looks to be related to #19.
If you need SSL support soon, would you give me PR?

@okumin
We needed a quick solution/workaround, so we have set up stunnel. Unfortunately we cannot invest time in a PR at this time.


execute AsNoFilter then  How to enable specified filter

hello,
I want to start the specified filter after AsNoFilter execution.
like this
var query = DbSet.AsNoFilter();
foreach (var filterString in filterStrings)
 {
        //TODO   Enable  the  filter
       query.Enable(filterString);
}

I want to know if it is supported.  thank you
Environment:
.NET Core 2.1
Microsoft.EntityFrameworkCore 2.1.2
Z.EntityFramework.Plus.EFCore 1.8.8

Yes, I would think so.
Have you got an error?
Best Regards,
Jonathan

Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Entity Framework Classic • Bulk Operations •  Dapper Plus •  LinqToSql Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function

You can also enable it this way:
query.Enable(filterStrings.ToArray());

Sorry, maybe I didn't describe my problem clearly.
query.Enable() is not supported.
IQueryable There is no Enable extension method.
I would like to know if there is such an expansion method or way to deal with this demand.
Thanks very much.

Thank you very much for your reply.
I processed it in the following way. I think he is feasible and passed my test.
`
///
///     AsWorkDataNoFilter
///
///
///
///
///
///
public static IQueryable AsWorkDataNoFilter(this DbSet query, DbContext context,
params object[] filterStrings) where T : class
{
var asNoFilterQueryable = query.AsNoFilter();
        object query1 = asNoFilterQueryable;
        var items = CacheGenericDynamicFilter.Where(x => filterStrings.Contains(x.Key));

        query1 = items.Select(key => context.Filter(key.Key))
            .Where(item => item != null)
            .Aggregate(query1, (current, item) => (IQueryable) item.ApplyFilter<T>(current));
        return (IQueryable<T>) query1;
    }

`

Thank you very much for your reply.
I processed it in the following way. I think he is feasible and passed my test.
public static IQueryable AsWorkDataNoFilter(this DbSet query, DbContext context,params object[] filterStrings) where T : class {         var asNoFilterQueryable = query.AsNoFilter();         object query1 = asNoFilterQueryable;         var items = CacheGenericDynamicFilter.Where(x => filterStrings.Contains(x.Key));         query1 = items.Select(key => context.Filter(key.Key))             .Where(item => item != null)             .Aggregate(query1, (current, item) => (IQueryable) item.ApplyFilter<T>(current));         return (IQueryable<T>) query1;     }

Thank you very much for your reply.
I processed it in the following way. I think he is feasible and passed my test.
` public static IQueryable AsWorkDataNoFilter(this DbSet query, DbContext context,
params object[] filterStrings) where T : class
{
var asNoFilterQueryable = query.AsNoFilter();
        object query1 = asNoFilterQueryable;
        var items = CacheGenericDynamicFilter.Where(x => filterStrings.Contains(x.Key));

        query1 = items.Select(key => context.Filter(key.Key)).Where(item => item != null)
            .Aggregate(query1, (current, item) => (IQueryable) item.ApplyFilter<T>(current));
        return (IQueryable<T>) query1;
    }`

Hello @wulaiwei ,
My bad, the method should be Filter and not Enable.
var query = DbSet.AsNoFilter();
query = query.Filter(filterStrings.ToArray())

Let me know if this one work ;)
Best Regards,
Jonathan

Hello  @JonathanMagnan

He still can't work.
But ,I have achieved my needs by extending ApplyFilter.
Thank you very much for your reply.

That's weird but let close it if you solved it ;)


Update stable version in repo from 1.0.3 to 1.1.0

Think about update stable version to 1.1.0
Version: stable=1.0.3 (1209 days old) => latest=1.1.0 (15 days old)
Installs: stable=516 (87.16%), latest=34 (5.74%), total=592
Click to use developer portal
Click to edit
Do not close this issue manually as a new issue will be created if condition for update still exists.
Please drop a comment if any reason exists which blocks updating to version 1.1.0 at this time.
Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

@GermanBluefox
@Apollon77
Is there any reason to delay updating stable any longer?
Please drop a commit if you know any reason to refrain from updating.
If there is no response until 28.5.2024 we could decide to update anyway.

This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 1.1.0 but the current stable version is already 1.1.0.
So this issue should be closed.
@mcm1957 for evidence


Outbound Foreign Key Heuristics

This PR addresses #247.
Merging this PR will break some of the chaise test cases in record as we're validating the value of some foreign key columns.

The update looks fine to me.


configuration {{hostname}} doesn't work

configuration {{hostname}} doesn't work, it always be an empty character

.

No, I didn't, my them are so dark that I didn't notice the input box.
But if I don't set it, won't there be a default value?

It's working on my side. Did you specify the replacement of {{hostname}} in the setting below?

No, I didn't, my them are so dark that I didn't notice the input box.
But if I don't set it, won't there be a default value?

No there isn't any default. See here for an explanation.

No there isn't any default. See here for an explanation.

I got it, thanks.


VNNN Ecosystem contracts should be able to withdraw/burn tokens from users without Approve/TransferFrom

Needs some means of allowing VNNN Ecosystem contracts to withdraw/burn users' VNNN tokens without requiring the user to first Approve and then trigger the contract to TransferFrom their account. VNNN token contract should allow approved contract addresses to spend users' balances (sounds like a bad idea now it is written out).  Maybe users could approve a contract to do this (i.e. unlimited allowance)?

Suggest the following:

Owner can approve a contract as a VNNN Contract using addVNNNContract and revoke using revokeVNNNContract.
Users will need to use vnnnAllow once per VNNN Contract to allow it to burn tokens from their account (with unlimited allowance)
VNNN Contracts will be able to use the vnnnBurnFrom function to burn tokens from the user's account (This improves user experience)

In this way only contracts allowed by the owner can use vnnnBurnFrom, and users would have a choice to allow this experience on a per-user basis.
Should a VNNNTransfer function be added to allow contracts to transfer users' tokens in a similar way?

Implemented vnnnPermit and vnnnPermitRevoke to allow this. Only contracts approved by the owner using addVNNNContract (and revokeVNNNContract to revoke) can use vnnnTransferFrom and vnnnBurnFrom to remove tokens from the balance of users that have used vnnnPermit to allow them to do so.


Update website for Kubeflow v0.7.1

kfctl v0.7.1 is now available:
https://github.com/kubeflow/kubeflow/releases

/assign