Fixed testing default value existence

Previous: #3649

tested locally looks good for me :)

Perfect, thanks again!

This fixes issue #665


Unable to complete - with correct solution

Challenge http://www.freecodecamp.com/challenges/waypoint-target-the-parent-of-an-element-using-jquery has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
with solution:
$("#target1").parent().css("background-color", "red");
The exercise will not complete.

I was able to return after completing a few more exercises and complete this exercise (same solution).


Pro API support

See #1 for the original closed PR to the main branch

Just gonna merge given it's already been reviewed in #1


CustomRW can't open device (Debian 9)

Required Info

Camera Model
D435

Firmware Version
<IP_ADDRESS>

Operating System & Version
Debian 9

Kernel Version (Linux Only)
4.19.0-5

Platform
PC

SDK Version
<IP_ADDRESS>

Language
CLI

Segment
Other

Issue Description
Hi
I'm trying to read the device calibration data of a Intel RealSense D435 using Intel.Realsense.CustomRW. The device is detected but I can't access the data:
$ Intel.Realsense.CustomRW -list
CustomRW for Intel RealSense D400, Version: <IP_ADDRESS>

Device Name                                  Serial Number       Firmware Version
Intel RealSense D435<PHONE_NUMBER>83        <IP_ADDRESS>
$ sudo Intel.Realsense.CustomRW -r -sn<PHONE_NUMBER>83
CustomRW for Intel RealSense D400, Version: <IP_ADDRESS>

Error: cannot find or open device with serial number<PHONE_NUMBER>83

The camera is well detected on the viewer and all the other utilities I tried.
CustomRW works perfectly on Windows 10 (same hardware). Any idea on what could solve this?
Thanks!

If the camera works normally except for calibration, I wonder if the calibration table inside the camera might be corrupted.  A 'gold reset' to factory defaults of the camera with CustomRW -g may correct this if the table is corrupted.

Same thing for Intel.Realsense.CustomRW -g: Error: cannot find or open device with serial number<PHONE_NUMBER>83
The same command works fine on Windows 10 (same computer, same camera), so it's not an hardware issue.
My kernel version is not supported for the librealsense2-dkms package so that probably causes this. I found instructions to patch the kernel manually for Ubuntu with other kernel versions but I'm on Debian and it doesn't work. Is there a workaround?

Kernel patching can be bypassed with the CMake customization flag -DFORCE_LIBUVC=true

I reinstalled and double-checked the udev-rules, but CustomRW still doesn't work.

Hi @belugum,
Link to the Debian packages for RealSense D400 Series Calibration Tools along with
installation instructions can be found here:
https://downloadcenter.intel.com/download/27415/Intel-RealSense-D400-Series-Dynamic-Calibration-Software-Tools
Please let us know if this has solved the issue.
Thank you!

Hi @belugum,
Do you need any further clarifications regarding this topic?


Emhancement suggestion

Display the address and size of the hex file after it is loaded, to make it easier to SAVE the loaded binary.
Have an option to SAVE the loaded binary to the filesystem.

I've added the option to save to the filesystem for both uart1 and vdp in the latest 1.1 release


Added Light theme

Codecov Report
Attention: Patch coverage is 69.56522% with 14 lines in your changes are missing coverage. Please review.

Project coverage is 79.03%. Comparing base (3cad656) to head (a333701).
Report is 11 commits behind head on master.

Files	Patch %	Lines
src/main/java/scm/address/ui/MainWindow.java	0.00%	10 Missing ⚠
.../java/scm/address/logic/commands/ThemeCommand.java	83.33%	0 Missing and 1 partial ⚠
...c/main/java/scm/address/model/theme/DarkTheme.java	83.33%	1 Missing ⚠
.../main/java/scm/address/model/theme/LightTheme.java	80.00%	1 Missing ⚠
.../java/scm/address/model/theme/ThemeCollection.java	90.90%	1 Missing ⚠
Additional details and impacted files
☔ View full report in Codecov by Sentry. 📢 Have feedback on the report? Share it here.

--
I cannot test MainWindow class as it is a UI class. @wilsonwid @sarjinius @ChuaZiLong can anyone approve my PR and merge?


How to use multiple js entry and only export functions

Description
I am using vite to build vue components and mount to old project dom by js entry file.
example:
a.js
import {createApp} from 'vue';
import AComponent from './AComponent.vue';

export function attachA(id) {
    createApp(AComponent).mount(id);
}

b.js
import {createApp} from 'vue';
import BComponent from './BComponent.vue';

export function attachB(id) {
    createApp(BComponent).mount(id);
}

vite config is:
import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'
import Components from 'unplugin-vue-components/vite'
import { NaiveUiResolver } from 'unplugin-vue-components/resolvers'

export default defineConfig({
	plugins: [
		vue(),
		Components({
			resolvers: [NaiveUiResolver()]
		})
	],
	build: {
		rollupOptions: {
			input: {
				a: 'a.js',
				b: 'b.js'
			},
			output: {
				entryFileNames: '[name].js',
				format: 'amd'
			}
		}
	}
})

But after build, dist/a.js and  dist/b.js lost exported functions, I can change export function to window.someFunc = function() {} to do this.
I think this because of treeshaking.
I have test rollupjs with vue plugin to build js entry file, and can save exported functions, how to do this in vitejs?
Suggested solution
Support js entry file and export something that not treeshaking.
Alternative
Library mode is not suitable for this scenario, because library mode is only allowed one entry, and can't support amd format and more.
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I found a way to do that is add build.rollupOptions.preserveEntrySignatures = 'exports-only' to config.
Links:
https://github.com/vitejs/vite/issues/4359
https://github.com/vitejs/vite/issues/3553
https://github.com/ice-lab/icestark/issues/346


Saving State in Preferences Store

Describe the bug
I am trying to to create an appPreferences extension and storing state in preferences-store. I based my code to telemetryPreferences but I am having a problem with configName.
Also, when I try to disable telemetry in app preferences it is not working. Basically that's my basis to create an app preferences extension.
To Reproduce
Steps to reproduce the behavior:

Recreate telemetry to create appPreferences extension
In name-store.ts
Scroll down to configName
See error

Expected behavior
No error, build success.
Screenshots

Environment (please complete the following information):

Lens Version: 4.0.0-beta.4
OS: Catalina
Installation method (e.g. snap or AppImage in Linux): dmg

Additional context
Disabling telemetry not working.

There was an issue regarding saving the state in preferences store. The value was saved but it does not reflect on UI. This is fixed in master now.

Thank you!


SASL OAuth is sometimes not refreshed and application gets stuck

Description
We are using SASL OAuth for authentication and most of the time it works fine. However occasionally the token will expire and the refresh function (passed into the SetOAuthBearerTokenRefreshHandler method) will not get fired, leading to the consumer getting stuck in an error state where the following message is emitted over and over:

SASL authentication error: {"status":"JWT_EXPIRED"} (after 5054ms in state AUTH_REQ, 6 identical error(s) suppressed)

When the consumer gets into this state, it never tries to recover by trying to refresh its token again and the consumer is basically dead, requiring the application to be restarted.
We have multiple environments and seemingly this only happens in some of the consumers in environments with low traffic in the topic - at least I have never seen the issue in the environments with plenty of traffic. So maybe this is an issue with too many partitions compared to the message throughput, causing the consumer to be stuck enough time in the Consume method call that the OAuth refresh function isn't called before it runs into the current token being expired? At least that is my guess, since once this issue happens, the partitions assigned to the now dead consumer are re-assigned to other consumers and then there is seemingly enough traffic on those consumers that they can keep running without having this issue. Originally we were using the Consume(CancellationToken) overload but tried using the Consume(TimeSpan) overload with a 30 second time out, but eventually the issue is still happening.
So there definitely seems to be some bug here causing the OAuth token fresh handler not to fire if  the Consume call is blocking for too long and actually I would also maybe expect that if the consumer starts getting the JWT_EXPIRED error, it should maybe default to trying to refresh its OAuth token instead of staying in an error state and never trying to recover.
We are using version 2.4.0 of the Confluent.Kafka nuget.
How to reproduce
I cannot tell you exactly how to produce it as I haven't been able to do so, but I can tell that this issue is happening in topics with a low amount of traffic where the consumer is spending a lot of time in the blocking Consume method.
Checklist
Please provide the following information:

[ ] A complete (i.e. we can run it), minimal program demonstrating the problem. No need to supply a project file.
[x] Confluent.Kafka nuget version.
[ ] Apache Kafka version.
[ ] Client configuration.
[ ] Operating system.
[x] Provide logs (with "debug" : "..." as necessary in configuration).
[ ] Provide broker log excerpts.
[x] Critical issue.

Can you please provide some debug logs during the time this issue happened

Callback to refresh oauth token not invoked at all if newly created consumer perform QueryWatermarkOffsets as the first operation.

Case1: builder.SetOAuthBearerTokenRefreshHandler -> builder.Build -> consumer.QueryWatermarkOffsets -> Confluent.Kafka.KafkaException : Local: All broker connections are down

Case2: builder.SetOAuthBearerTokenRefreshHandler -> builder.Build -> consumer.Consume -> consumer.QueryWatermarkOffsets -> work as expected

Case3: config.SaslOauthbearerMethod = SaslOauthbearerMethod.Oidc -> consumer.QueryWatermarkOffsets -> work as expected

Faced with the same issue.
AWS MSK cluster with IAM authorization.
Case 1 and Case 2 - the same
But Case 3  not working because for SaslOauthbearerMethod.Oidc required additional options, like sasl.oauthbearer.client.id and other


Add instructions for manual start of Docker daemon

Docker daemon did not automatically start for me; running sudo docker run hello resulted in the following error message:
docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
See 'docker run --help'.

After starting the docker daemon manually using dockerd, I saw the expected information.

Proposed changes

Unreleased project version (optional)

Related issues (optional)

It seems more likely it should be started via system service manager, no?  So in CentOS I'd expect that it's systemd and probably something like sudo systemctl start docker?

I'm more curious to know why it didn't start automatically for you. What version of Docker were you installing and what version of CentOS? I'd like to try to replicate this.
Also, if this really is an issue with CentOS not starting the daemon automatically, we need to just tell people to start it, rather than give them a cautionary thing to do if it doesn't start. I'd prefer to avoid it altogether though, so if you can get me that info, it would be great!

@mstanleyjones FWIW, IIRC some package managers won't start installed daemons / services automatically, so it's not unexpected to have to start them after the fact.

I agree we should verify it's out-of-the-box behavior before covering in docs though 👍

OK, verified that Docker does not start automatically on CentOS. Thank you bringing this up. I'm going to do the fix in a slightly different way than you have it, but I'll commit into your PR, if that's OK.


Fix and refactor few task in libvirt_up.yml

TestBos2: virt
Some of them was bug some of them change to be more ansible format and some of them changed to modules

retest

retest

recheck

I've seen an issue with the merge-queue job, I'll try to fix it separately, now that I've identified that.

I've seen an issue with the merge-queue job (not related to this change, but related to the code that the merge queue action has), I'll try to fix it separately, now that I've identified that.

Created this change to fix the issue with dci-merge: https://github.com/redhatci/ansible-collection-redhatci-ocp/pull/334, please hold on this change while that PR is reviewed, I'd prefer to fix that before trying to re-merge this to confirm the issue is fixed.

Found another issue with dci-merge, fixing it here: https://github.com/redhatci/ansible-collection-redhatci-ocp/pull/335

Change was merged, trying to merge this again.


“extensionsKeymap” doesn't let us redefine existing keymaps

Bug report
Packages affected

[ ] sandpack-client
[x] sandpack-react

Description of the problem
A few of my users have noticed that the tab-handling is a bit funny: "Tab" inserts a literal tab character (\t), but Shift + Tab removes 2 spaces.
I'd prefer to have Tab always add 2 spaces when no text is selected, so I updated my code to include a "Tab" keymap:
import { indentMore } from '@codemirror/commands';

<SandpackCodeEditor
  extensionsKeymap={[
    {
      key: 'Tab',
      run: ({ state, dispatch }) => {
        console.log('Test')
        return true;
      },
    },
  ]}
/>

My actual code tried to perform the tab operation, but I've simplified it here to the minimal code required to demonstrate the issue. When I hit "Tab", callback isn't called, and so nothing I do in this function works.
What steps can we take to reproduce the problem?
Check out the linked CodeSandbox. It defines keymaps for the lowercase "a" character and Tab, removing their default functionality and logging a console message.
It works for "a", I believe because there is no conflicting override. But it doesn't work for "Tab".
I wonder if the issue has to do with keymap.of; I wonder if it isn't merging them in the order provided. I tried digging into the codemirror code but couldn't find this method defined aaywhere.
Link to sandbox:
CodeSandbox Repro
Your Environment

Software
Name/Version

Sandpack-client version
1.1.0

Sandpack-react version
1.1.1

Browser
Chrome

Operating System
MacOS

For reference, here's the code I'm trying to run on Tab
<SandpackCodeEditor
  ref={codeMirrorGrabberRef}
  wrapContent
  showLineNumbers={showLineNumbers}
  extensionsKeymap={[
    {
      key: 'Tab',
      run: ({ state, dispatch }) => {
        console.log('Run tab');
        if (state.selection.ranges.some((r) => !r.empty))
          return indentMore({ state, dispatch });
        dispatch(
          state.update(state.replaceSelection('  '), {
            scrollIntoView: true,
            userEvent: 'input',
          })
        );
        return true;
      },
    },
  ]}
/>

Essentially inserting two spaces instead of \t. I feel like this might be a preferable UX for most people, since Tab tends to produce wonky results (anywhere from 1 to 8 spaces), and it's inconsistent with Shift + Tab.


fix: put back docstrings for launching sessions

/deploy

You can access the deployment of this PR at https://renku-ci-nb-1929.dev.renku.ch


Corey   game state game mode

Killing other players gets tracked and counted
Deaths get tracked and counted
Personal kill/deaths tracked
Team based kill/deaths tracked
Post-game Stat screen displayed
M.V.P calculated and displayed
Winning/loosing teams displayed
Basic re-spawn functionality
Damage Player system refactored, many errors removed

sounds good


Fix golangci-lint -fast warnings

The next series of PRs will aim to fix as many linter warnings as possible.
This one fixes:
golangci-lint.exe run --fast --exclude-use-default=false

This is the default linter integration with IDE like VSCode (https://github.com/golangci/golangci-lint#editor-integration)
Merging that PR means that, by default, the project compiles without warning.

@c-bata The goal is to avoid SA9003: empty branch (staticcheck) (https://staticcheck.io/docs/checks#SA9003)
I was looking for a noop and your prompt.dummyExecutor("") happened to fit the bill.


Error when opening code action window

Describe the bug
When opening the code action window with a lot of items, the following error appears:

Steps to reproduce

Install Lspsaga with the default settings.
Open a Rust file with rust_analyzer activated. Request code actions in the field of a struct.

Expected behavior
For there to be no error.
Neovim version (nvim -v)
v0.10.0-dev-684+g80cf0f3d2
lspsaga commit
adfd5533e4e5627f74bc9896ca8936cede3a26ce
Terminal name/version
kitty 0.28.1

there need give it max height i think...

there need give it max height i think...

But such bound would be set by this plugin right?

yep . there should give it an option code_action.max_height .I will fix it later.


Adopt superforms 2.0.0 changes

superforms v.2.0.0 has been released with numerous bigger changes. It would be nice to have these changes adapted.

@MrExplode Its already in progress. @huntabyte is working on it. superforms-v2 branch

oh thanks

Duplicate of #115 . Please search existing issues before creating a new one.


manual readme generator - updated structure

contains a script that generates the readme when it is run - same structure as on main at time of pull request creation

please remove the "library" subfolder, as we should have the BB tags right on the root of https://github.com/CSA-FEDERATE/Proposed-BuildingBlocks.
It is ok to shift the non-BB folders (like "figures") to a subfolder, however.


Add dark mode

Dark mode is enabled when the browser's color scheme preference is set to dark.
With color inversion + hue rotation providing most of the dark colors, it should be easy to maintain. One-off changes can be set with the dark: class prefix.

Closes #280.

interesting solution, looks good overall.
it follows system settings, should we add a toggle to force light/dark as well?

Oh, there is still no dark toggle yet...

Oh, there is still no dark toggle yet...

I think it should be System/Light/Dark, with system as default like in other websites.

I added a theme toggler that appears in the bottom-left corner in the footer:

Note that it has its own background color:

The theme is saved in local storage, following Tailwind's documentation for the most part. If a user's system dark mode preferences changes, Otterscan will automatically adapt to it.

I have some mixed feelings about the toggler:

The "sun" and the "gear" icons look similar if you don't pay enough attention (I think it is more the style of that specific "sun" is to blame though...).

if we don't find a "better" sun, maybe try a lightbulb? maybe regular lightbulb vs crossed lightbulb?

I think it draws too much attention in the home page, sure the user should be able to change the setting from there, I just think the whole toggle is too big and too distracting if you don't want to care about it.

Also in the regular pages, it feels it doesn't belong to where it is, i.e., it is between the page content and the footer, but it is not a footer neither page content. In this case I would hide it under the sandwich menu top-right.

What if we hide it in the sandwich menu top-right and make it (only the menu, not the entire header) appear in the home page? WDYT?

re: local storage, it seems fine to me

I think we can do that - hide it in the menu and add the menu to the home page.

Here's the new look:

And opened on the home page:

The app context is not available on the home page since it is housed in the <Main> element which includes the header, so the sourcify source option is hidden on the home page right now. We could potentially refactor it to give the app context to the home page.

I changed my mind :)
WDYT?

I think what I didn't like in the first attempt was the solid icons being too distracting, using the regular ones look better. Also using a display icon instead of the gear because the gear also feels like it is going to open a settings dialog.
import { faMoon, faSun } from "@fortawesome/free-regular-svg-icons";
import { faDisplay } from "@fortawesome/free-solid-svg-icons";

it also feel more like the menu in tailwindcss website:

the rounded icons still look too distracting and "heavy", I think we can turn them into standard menu items with icons, like in the tailwindcss site

I think switching to regular icons is fine, and I do like the sun/moon icons better. I think using standard menu items would look best if the theme buttons are in their own menu, like on the Tailwind website.

What about this? I reduced the padding, reduced the border, and faded the background color even more:

What about this? I reduced the padding, reduced the border, and faded the background color even more:

still don't like it, it looks busy (thick border + rounded corners + background color) and doesn't feel like it belongs the menu it is contained in (that "a component from another app got imported as-is here"-feeling)

Using standard menu items and title:

Then I moved Broadcast Transaction to the bottom:

I think we don't need to repeat the word "theme" since it has its own section now and call the items "Light/Dark/System".
And make it evident that the "Light/Dark/System" items are hierarchically contained in the "Theme" section, I feel like the current UI language doesn't feel like that because the "Theme" font is smaller. I think we can keep the font smaller (it is saying to the user that label is not important), but there is something missing (no ideas yet, maybe a different shade of gray/black?).
Also, make the "Data source" and "Theme" texts non-selectable, they are not "text".

What about a slight left margin to convey their hierarchical status as children of the groups?

I think it looks better without the left margin.
And I think only "System" instead of "System default" feels better (like in tailwind website). Less is more :)

Small glitch I found: the hamburger menu looks a little smaller (vertical) in the home page vs regular pages, probably due to be anchored to the height of search box.
Can we make it the same height in the home to be pixel perfect?

Fixed to use "System". And at most zoom levels, the height should now be identical.


banned from oblique

hi, people for oblique I'm really sorry for my behaver on your server I got peer pressured into getting a band. I'm really sorry about that and if you unbanned me ill behave and not be inappropriate
my user name is NoahBert_420
thanks

Though you seem to be somewhat genuine, I will be declining your appeal as you went to quite an extent in terms of being not just 'inappropriate' but extremely inappropriate and offensive. We have no tolerance for the kind of things you said shortly before getting banned, and I will not just let you be unbanned because you were simply being 'peer-pressured'.


Refactor encapsulate the command-line interface

As a developer
In order to be able to start the Ruby hooks server programatically
I want to keep all the Ruby hooks server business logic in a single directory
In order to to be able to improve its CLI independently
I want its CLI to be a first-class citizen among the code
See https://github.com/apiaryio/dredd-hooks-ruby/issues/13
This refactoring should allow to start using Thor to build the CLI with minimal disruption.
Using Thor would change the API (starting the server would require to dredd-hooks-ruby start instead of dredd-hooks-ruby) but would allow to build a properly documented CLI (dredd-hooks-ruby help and so on...) with minimal effort.

Note: using Thor was discarded, because it would break the hooks handler API. The encapsulation work done here still makes sense however.


Broken if app id changed

leaving id at default, eg "org.nativescript.someApp" everything is fine.
Changing to "com.xxxxx" (for submitting an update to playstore, makes no difference if just changed in the package.json or anywhere found) and the build goes fine but app crashes with:
"TypeError: Cannot read property 'pushplugin' of undefined File: ", line: 1, column: 265"
when the pushplugin is invoked.
Maybe i'm just missing something here or its not even pushplugin related but invested several hours now and i'm lost.
TIA

@baderth
This looks like the id is set in the package.json file. Some NS app projects also have an app.gradle file for Android in /App_Resources which should be the same as in the package.json file.
Could you please check this?

@AntonDobrev
thanks.
yeah, as I stated in OP -  i searched through the whole folder after doing a fresh "platform add android" and changed every occurrence of the "default" app id to mine, but gave me the error from the OP.

@AntonDobrev
Issue is resolved with latest 2.2 NS.

@baderth Thanks for specifying, closing this issue now. Happy coding!


Analyzer issue: All Packages have the same revision

Hello,
I am evaluating ORT using an Artsy Web App (https://github.com/artsy/artsy-wwwify) as my starting point. I analysed it using the latest master (122331e69d098820958869984a10023208990a7a) with ort/cli/build/install/ort/bin/ort analyze -i source -o ort.
I get this result where every package it found seems to have the same revision (fb5a6e3808c93edadfe93468522ec55b4fe255a7).
Doing the scanning it obviously fails because the revision in the repositories can not be found.
14:24:21.226 [ScanCode-1] WARN  org.ossreviewtoolkit.downloader.vcs.Git - Could not fetch with only a depth of 50: IOException: Running 'git checkout fb5a6e3808c93edadfe93468522ec55b4fe255a7' in 'ort/downloads/NPM/unknown/accepts/1.3.7' failed with exit code 128:
fatal: reference is not a tree: fb5a6e3808c93edadfe93468522ec55b4fe255a7

Falling back to fetching everything.

Is this a know issue or is there any workaround I could try?
Best,
Piet

Please note the line "Falling back to fetching everything". So, what fails is just the performance-optimization to shallow-fetch only recent Git history. Also, the third-to-last line in the analyzer result says has_issues: false, so all should be fine.

Please search for fb5a6e3808c93edadfe93468522ec55b4fe255a7 in the scan result and you will see what I mean: Every single NPM Package has the same vscRevision set.
The failing shallow clone is the first issue it encounters. It clones everything afterwards and fails to checkout the revision because it's not there.

I see. Also strange that we get "Unkown" in "Unmanaged::artsy-wwwify:fb5a6e3808c93edadfe93468522ec55b4fe255a7" but also "Yarn::artsy-wwwify:1.0.0" as projects. Maybe @fviernau has an idea?

Hi @pietbrauer
Could you please tell:

the NPM version you're using
if your log contains entries like: Resolving the package info for '$identifier' locally.

Sure, NPM version is 6.14.4.
If you meant the output of the analyze command.
$ cli/build/install/ort/bin/ort analyze -i source -o ort
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by retrofit2.Platform (file:/Users/pietbrauer/Projects/ort/cli/build/install/ort/lib/retrofit-2.9.0.jar) to constructor java.lang.invoke.MethodHandles$Lookup(java.lang.Class,int)
WARNING: Please consider reporting this to the maintainers of retrofit2.Platform
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
________ _____________________
\_____  \\______   \__    ___/ the OSS Review Toolkit, version 0.1.0-SNAPSHOT.
 /   |   \|       _/ |    |    Running 'analyze' under Java 12.0.2 on Mac OS X with
/    |    \    |   \ |    |    ORT_DATA_DIR = /Users/pietbrauer/.ort
\_______  /____|_  / |____|    SHELL = /bin/zsh
        \/       \/
More environment variables:
TERM = xterm-256color
JAVA_HOME = /Users/pietbrauer/.sdkman/candidates/java/current
GOPATH = /Users/pietbrauer/Documents/Projekte/go

The following package managers are activated:
	Bower, Bundler, Cargo, Conan, DotNet, GoDep, GoMod, Gradle, Maven, NPM, NuGet, PhpComposer, PIP, Pipenv, Pub, SBT, Stack, Yarn
Analyzing project path:
	source
Found 2 project(s) in total.
Writing analyzer result to 'ort/analyzer-result.yml'.

Hm, I have tried to reproduce it by

doing a fresh clone of https://github.com/artsy/artsy-wwwify
analyzing that clone directory

...without any success. Which were the exact steps you reproduced it with?

I did the exact same thing, just my copy was older (https://github.com/artsy/artsy-wwwify/commit/fb5a6e3808c93edadfe93468522ec55b4fe255a7).
I deleted the repository again, now I have a analyser-result where every revision is fe6795435276da85ed4ec8aa2f461bc2e8c47488.

Thanks! Could you also please share the operating system and whether you analyze the root directory of the repository?
It'd be useful to know whether entries like Resolving the package info for '$identifier' locally.
are contained in the debug log output, e.g. run ./cli/build/install/ort/bin/ort --debug analyze -i ...

Yes, it's full of these messages.

Thanks again. If I'm not missing anything there are just two root causes possible

your package directories inside the node_modules directory are all symbolic links
ORT's logic to determine whether a file is a symbolic link is broken

So could me do one more favor and run npm install in the directory containing the package.json and then tell whether the package directories within node_modules are actually symbolic links?

Just did a fresh yarn install (as there is a yarn.lock).
The node_modules just contain regular directories:

Thanks! Do you get symbolic links also when doing npm install (instead of yarn install)?
I'm asking for NPM as this is what ORT used when creating the buggy analyzer result, e.g. note that the identifiers of the packages all start with NPM:.

In case NPM also should not create symbolic links we could try #2707 as speculative fix.

I tried removing node_modules just to be super sure.

using the master version I still got the same result (revision broken)
using the npm-minor-improvements branch the --debug log changed, the revisions where found and the scanning commences

08:32:27.530 [Analyzer-1] DEBUG org.ossreviewtoolkit.analyzer.managers.Npm - Found a 'package.json' file in 'source/node_modules/acorn-globals/node_modules/acorn'.
08:32:27.531 [Analyzer-1] DEBUG org.ossreviewtoolkit.analyzer.managers.Npm - Resolving the package info for<EMAIL_ADDRESS>via NPM registry.

@pietbrauer great, thanks!
Then I'd just use my PR as fix for this, I just amended it slightly.
Just out of curiosity - regarding the path you passed to ort analyze -i as input directory: was any directory contained in that path a symbolic link by any chance?

I didn't find any directory that was a symbolic link, that's what is weird to me…

That's strange. I only have Linux available here so I cannot reproduce the OSX case unfortunately.

I didn't find any directory that was a symbolic link, that's what is weird to me…

Does macOS' Finder even display symbolic links differently from regular files? I.e. can it be that you simply didn't notice files to be links in reality?

Yes, they would look like this (with an arrow):


Update ONNX and ONNX  convert to MMIR

Onnx 1.2.1 is quite old .

This would be highly appreciated.


feat: Add driver location simulation for development

Implemented CSV parsing to simulate driver location updates.
Sends bus locations to Supabase every 5 seconds.
Includes latitude, longitude, bus number, type, and weather.

Closes #19


Conflict between Rails/FilePath and RSpec/FilePath

I haven’t debugged this at all, but it seems that a config entry for RSpec/FilePath is read by RuboCop v0.47.0 as config for the new Rails/FilePath cop. Are namespaces ignored by “master” RuboCop?
I’m using rubocop v0.47.0 and rubocop-rspec v1.10.0.

Damn I thought I helped fix this. Thanks for reporting

Solution in the pipeline. See all the commit noise above :laughing:

Sorry, your fix doesn’t resolve my issue. I’ll try to come up with a minimal reproducible example.

Sorry for the false alarm. Your fix works splendidly!

I have a project pulling its configuration from a gem that is exhibiting this issue. I’ll try to put together a simple reproduction case to tease apart what is happening. I’ll post it to the backus/rubocop issue once I have it.

@erikogan make sure to include your rubocop and rubocop-rspec versions. basically, if rubocop-rspec isn't required before RSpec/FilePath is referenced then it will cause a warning and undesired behavior. I think there are still edge cases where it still happens but most primary cases are fixed i think. partially an issue of rubocop-rspec being an unofficial extension

I'm still getting this on v0.61.1. When running rubocop --only "RSpec/FilePath" rubocop runs as if I'd specified rubocop --only "Rails/FilePath".
My config is this:
Rails/FilePath:
  Enabled: false

RSpec/FilePath:
  Enabled: true

Interestingly, when i simply run rubocop, the check is correct.


needs "rename" button in repository browsers

rename repository and models/actions.

solved by https://github.com/ReMobidyc/ReMobidyc/pull/137


Compile Node targets without -std=c++11 option

There is a -std=c++11 switch configured in Node modules here. I can imagine this was put there because of older compilers. Now we have C++17, this is a limiting option, not a better one. This PR removes this option in Node targets.

Thanks @tdcosta100.

Thanks @tdcosta100, this fixed some compilation issues I had recently!

Nice, @stefankarschti! It was giving me some errors too.


Update stress test template to handle Scenario name and group deployments

This contains incremental updates to the stress-test-addons helm library:

Adds an optionally injected scenario name to the global scope, to address unique resource naming conflicts when multiple jobs are deployed as part of a single stress test package
Changes the azure-deployer deployment model to use az deployment group instead of az deployment sub

Starting as a draft PR because I'm about to go on vacation and I don't want to lose track of changes that https://github.com/Azure/azure-sdk-for-js/pull/16689 is dependent on. However, there is currently a bug where the templates break if Scenario is not specified (I think the printf function is causing it to evaluate despite the use of default).

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

/check-enforcer override


More consistent naming

@JuliaRegistrator register

Error while trying to register: Register Failed
@bertrandkerres, it looks like you are not a publicly listed member/owner in the parent organization (terion-io).
If you are a member/owner, you will need to change your membership to public. See GitHub Help

@JuliaRegistrator register

Comments on pull requests will not trigger Registrator, as it is disabled. Please try commenting on a commit or issue.


AMBARI-23373. Fix formatZKFC

resource_management.core.exceptions.Fail: Script '/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HDFS/package/scripts/zkfc_slave.py' has no method 'format'

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1419/
Test FAILed.
Test FAILured.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1438/
Test FAILed.
Test FAILured.

Test failures are not related to change.


GreeterRow: Fix link clicks

GreeterRow: Fix link clicks
This update fixes the GreeterRow to ensure that clicks (and keyboard Enter
press) works as expected (which is that it performs like a regular link).

Pull Request Test Coverage Report for Build 2201

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 2200:
0.0%

Covered Lines:
10809

Relevant Lines:
10809

💛  - Coveralls


How to use 9-patch image for Android platform?

Hey there and thank you for using React Native!
React Native, as you've probably heard, is getting really popular and truth is we're getting a bit overwhelmed by the activity surrounding it. There are just too many issues for us to manage properly.
Do the checklist before filing an issue:

[ ] Is this something you can debug and fix? Send a pull request! Bug fixes and documentation fixes are welcome.
[ ] Have a usage question? Ask your question on StackOverflow. We use StackOverflow for usage question and GitHub for bugs.
[ ] Have an idea for a feature? Post the feature request on Product Pains. It has a voting system to surface the important issues. GitHub issues should only be used for bugs.

None of the above, create a bug report
Make sure to add all the information needed to understand the bug so that someone can help. If the info is missing we'll add the 'Needs more information' label and close the issue until there is enough information.

[ ] Provide a minimal code snippet / rnplay example that reproduces the bug.
[ ] Provide screenshots where appropriate
[ ] What's the version of React Native you're using?
[ ] Does this occur on iOS, Android or both?
[ ] Are you using Mac, Linux or Windows?

@facebook-github-bot stack-overflow

Hey @chenjsa and thanks for posting this! @damusnet tells me this issue looks like a question that would be best asked on StackOverflow. StackOverflow is amazing for Q&A: it has a reputation system, voting, the ability to mark a question as answered. Because of the reputation system it is likely the community will see and answer your question there. This also helps us use the GitHub bug tracker for bugs only. Will close this as this is really a question that should be asked on SO.

Try this npm package:
https://www.npmjs.com/package/react-native-image-capinsets
Thank you, madsleejensen


Alpha enumerators for lists (and headings?)

Currently, lists may be ordered (numbered) or unordered (bulleted). Headings may also be enumerated or not; they can be customized in the frontmatter, e.g.
---
numbering:
  heading_1: true
  enumerator: 4.%s
---

However, in neither case can we use letters as the enumerator. Might be good if we could!

Some prior art in pandoc is here: https://pandoc.org/MANUAL.html#extension-fancy_lists
Myst-parser in python just implemented this here:
https://github.com/executablebooks/MyST-Parser/pull/703/files#diff-a21e4da015958b8c67ffb5ad8204d681e8190da518b085c1a7b345b65d89aef6R798


Delete tag V1.1.1

It seems having two different tags that only differs on casing v1.1.1, V1.1.1 is not a good idea. Probably because tags are represented as files in the .git directory, and some file systems are case insensitive. The fact that they point to different commits does not help either 😅
Every time I pull now, I get these messages:
git pull
From github.com:n8jja/Pat-Vara
 * [new tag]         v1.1.1     -> v1.1.1
 * [new tag]         v1.1.1     -> v1.1.1

Maybe it's worth trying to delete the misspelled V1.1.1 tag (git push --delete origin V1.1.1) 🙂

Tag has been deleted and proper one applied!


Relax the rule in the context of COVID

The productivity of many MLPerf participants have been severely affected by COVID-19 situation. To accommodate this special situation, I propose to relax the rule in MLPerf 0.7 training round to:
As soon as the submitted model is mathematically equivalent with any closed category submission in MLPerf 0.6, it is considered compliant.
The reasoning behind it:

If a model is accepted by MLPerf 0.6, it's considered as compliant already
HP table is not implemented for MLPerf 0.7
There are models implemented in different frameworks (TF, Pytorch, MxNet, etc), validating every single bits of one framework to match another requires a lot of time and effort
This allows participants to just pull out an existing submission and tune it on their framework without spending significant engineering to validate its compliance, which does not help the company's core business. This is specifically important not only for large companies but also for small companies where resource is usually a constraint, especially in the COVID situation.

In the long run, after COVID situation is over, we can keep finalizing HP table, make all the models behave exactly the same between different frameworks and apply more strict compliance rule.

SWG:
AI(PM) start a thread

Agreed we need go forward and manage as best we can.


Update bodymovin extension in the Creative Cloud / Adobe Exchange

While trying to resolve #57 I tried to upgrade my bodymovin extension, but the Creative Cloud / Adobe Exchange is stuck on 5.7.1 (April 2019).
The latest version mentioned in git at the time of writing is 5.7.3 (September 2020; but I'm not sure if it's considered "released" yet).
I'm not sure about the changes in 5.7.2 and 5.7.3 but it would probably be good to have these changes in Adobe Exchange.

I've pushed a new version and it should be approved next week.


Enhancement: delay closeOnMouseLeave in dropdown

Added 1s delay on mouseleave event for dropdown to prevent closing in incedental mouseleave.

Prettier is complaining. npm run prettier to fix.


⚠ GitLab Server has degraded performance

In 3e499d8, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 6831 ms

Resolved: GitLab Server performance has improved in aa1186c.


error with unirest

Fatal error: Uncaught Error: Call to undefined function Unirest\curl_init() in /var/www/html/api/changelly-php/vendor/mashape/unirest-php/src/Unirest/Request.php:396 Stack trace: #0 /var/www/html/api/changelly-php/vendor/mashape/unirest-php/src/Unirest/Request.php(292): Unirest\Request::send('POST', 'https://api.cha...', '{"jsonrpc":"2.0...', Array, NULL, NULL) #1 /var/www/html/api/changelly-php/src/Changelly.php(142): Unirest\Request::post('https://api.cha...', Array, '{"jsonrpc":"2.0...') #2 /var/www/html/api/changelly-php/src/Changelly.php(46): Changelly\Changelly->post('getCurrencies') #3 /var/www/html/api/changelly-php/sample.php(12): Changelly\Changelly->getCurrencies() #4 {main} thrown in /var/www/html/api/changelly-php/vendor/mashape/unirest-php/src/Unirest/Request.php on line 396

Have you manually removed Unirest as dependency?
Try to reinstall package with composer require vittominacori/changelly-php

got resolved, thanks for prompt reply :)
On Thu, Jul 11, 2019, 2:51 AM Vittorio Minacori<EMAIL_ADDRESS>wrote:

Have you manually removed Unirest as dependency?
Try to reinstall package with composer require vittominacori/changelly-php
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vittominacori/changelly-php/issues/2?email_source=notifications&email_token=ABXICNMBD23KSYS4CCQM533P6ZHEBA5CNFSM4H7YHUA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZUYYDQ#issuecomment-510233614,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABXICNMXM67Q25LRC3D2FG3P6ZHEBANCNFSM4H7YHUAQ
.


Fixed overflow & docs issue

Fixed the checkbox overflow by adding a flex shrink to the container.  Also fixed an issue in the docs in ProgressCircle.
This fixes #203 and #204

Looks good!


OSS Fargate doc issues

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

lgtm


Fix for HA 2024.4.1

Updates to HA 2024.4.1

Fixes [https://github.com/loopj/home-assistant-vantage/issues/136]
Python 3.12
Versions bumped to HA 2024.4.1
Fixup using and types for config flow and entity

Merge a couple outstanding dependabot PR's to make pre-commit happy
Update devcontainer:

Debian Bookworm Python 3.12
Fixup VSCode extensions for Python 3.12 (deprecated, replaced, config change)

Follow up:

Linter warnings for missing abstracts defs and unused vars.
PyLance is unhappy unless manually selecting default interpreter, tried a couple settings for interpreter and default, no go?
Default HA log level changed debug, seems a typical step before running debug script.
Tests were not updated

Thanks so much for the fix @ptr727!

Thanks so much for the fix @ptr727!

No problem, happy to contribute, and thank you.
I know you selectively merge, if you create e.g. a dev or merge branch, then incoming PR's can go against that branch, and you can merge whatever you want to main, but your choice how you want to handle PR merging.


Cerebro doesn't start on Mint 21

[x] I am on the latest Cerebro.app version

[x] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: Linux Mint 21

Cerebro.app version: cerebro-0.3.1-x86_64.AppImage

Relevant information from devtools: N/A

Issue
Hey,
I am trying to start the Cerebro 0.3.1 AppImage, but I am getting the following errors in terminal:
** (AppImageLauncher:100556): WARNING **: 03:33:34.593: Pixbuf theme: Cannot load pixmap file /home/valtm/.themes/Adapta-Nokto/gtk-2.0/ProgressBar/trough-dark.png: Failed to load image “/home/valtm/.themes/Adapta-Nokto/gtk-2.0/ProgressBar/trough-dark.png”: Fatal error in PNG image file: bad parameters to zlib

(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

** (AppImageLauncher:100556): WARNING **: 03:33:34.593: Invalid borders specified for theme pixmap:
        /home/valtm/.themes/Adapta-Nokto/gtk-2.0/ProgressBar/trough-dark.png,
borders don't fit within the image

(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:100556): GdkPixbuf-CRITICAL **: 03:33:34.593: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

I tried with different themes, but to no avail.

Hi @ValTM
Version 0.3.1 is outdated, please try the last version of the app so we can check if this error persists.
Try with
https://github.com/cerebroapp/cerebro/releases/download/v0.5.0/Cerebro-0.5.0.AppImage
The main branch is now in v0.6.0 but no executables were published. If you want you can try to build it from source following the instructions in the readme file.
Thanks 🙌
David

Hey @dubisdev,
I downloaded 0.3.1, because that was what I found on the website. I thought it is the latest version. Sorry about that.
Anyways, with 0.5.0 AppImage I get a different error:
(electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
[18073:0810/020807.531162:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.

Failed to get crash dump id.
Report Id: --2022-08-10 02:

Failed to get crash dump id.
Report Id: --2022-08-10 02:
Illegal instruction (core dumped)

Specs are: 5900X, 64GB Ram, GTX1060 6GB, Linux Mint 21, Kernel 5.15.0-43-generic

I add it to the backlog. I'll try to reproduce it myself.
Thanks!

Sure, let me know if I can help in any way.

@ValTM could you validate in our latest version?

@oguhpereira
A JavaScript error occurred in the main process
Uncaught Exception:
Error: Config schema violation: `lastShownDonateDialog` must be number
    at e.exports._validate (/tmp/.mount_CerebrLzuBPF/resources/app.asar/main.js:2:45448)
    at get store [as store] (/tmp/.mount_CerebrLzuBPF/resources/app.asar/main.js:2:44169)
    at new T (/tmp/.mount_CerebrLzuBPF/resources/app.asar/main.js:2:41902)
    at new e.exports (/tmp/.mount_CerebrLzuBPF/resources/app.asar/main.js:8:31842)
    at 9641 (/tmp/.mount_CerebrLzuBPF/resources/app.asar/main.js:2:30510)
    at r (/tmp/.mount_CerebrLzuBPF/resources/app.asar/main.js:8:68066)
    at /tmp/.mount_CerebrLzuBPF/resources/app.asar/main.js:8:68576
    at Object.<anonymous> (/tmp/.mount_CerebrLzuBPF/resources/app.asar/main.js:8:68602)
    at Module._compile (node:internal/modules/cjs/loader:1120:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1175:10)

Cerebro-0.10.0.AppImage

We just uploaded a new version removing this view, can you check again @ValTM ?

Can you provide a compiled verison @oguhpereira ?

Check our last tag
https://github.com/cerebroapp/cerebro/releases/tag/v0.11.0

Ah, I was looking for the artifacts in the Releases.
Anyways, it appears to be working all right, no issues!
I'll close this ticket as it seems resolved.


Fixes LoadMultiViewImageFromFiles

Fixes a bug that prevents the use of LoadMultiViewImageFromFiles in data loading pipelines, see #227 for a bug report.
Is the new order of img = (rgb x h x w x rgb x multi_imgs) the desired one?
Any help is appreciated, I'm quite new to the framework.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @SimonDoll ,
Thanks for your kind PR. Would you like to add a unit test for the PR to test your case?

Hi @SimonDoll ,
Thanks for your kind PR. Would you like to add a unit test for the PR to test your case?

Hi @ZwwWayne, thanks for Your reply.
I can add a test case for this, but as far as I understand the "dataset" provided for test cases (tests/data/nuscenes/) does only provide lidar data and no camera images.
Do You have a script at hand to recreate this test dataset that I can modify to include camera images?
Is test_nuscene_dataset.py the correct location for the test?
Thanks for any help!

Hi @ZwwWayne, thanks for Your reply.
I can add a test case for this, but as far as I understand the "dataset" provided for test cases (tests/data/nuscenes/) does only provide lidar data and no camera images.
Do You have a script at hand to recreate this test dataset that I can modify to include camera images?
Is test_nuscene_dataset.py the correct location for the test?
Thanks for any help!

Hi @SimonDoll , I also faced this problem and understood the reason after some debugging. However, I think that it should be fixed by editing  loading.py , in particular  LoadMultiViewImageFromFiles  class, line number 44. This line is responsible for making image data for  results dict.  img  is not an instance of  list  there, but  numpy.ndarray .
np.stack creates 4-dimensional data, but in format.py it is checked against instance of list which is not correct. Maybe changing that  if  line is better option, for example something like:
if isinstance(results['img'], list) or len(results['img'].shape)>3:
      pass    # img has 4 dims => multi view
But anyway, your change might effect datasets having a single image (e.g.  Kitti)
I think the best way is creating  list  variable for results['img']  in LoadMultiViewImageFromFiles class.

This PR is fixed in #611

Hi
@SimonDoll
We are grateful for your efforts in helping improve this open-source project during your personal time.
Welcome to join OpenMMLab Special Interest Group (SIG) private channel on Discord, where you can share your experiences, ideas, and build connections with like-minded peers. To join the SIG channel, simply message moderator— OpenMMLab on Discord or briefly share your open-source contributions in the #introductions channel and we will assist you. Look forward to seeing you there! Join us ：https://discord.gg/UjgXkPWNqA
If you have a WeChat account，welcome to join our community on WeChat. You can add our assistant ：openmmlabwx. Please add "mmsig + Github ID" as a remark when adding friends：）
Thank you again for your contribution❤


Consider returning signature from GET /dids/:did

Currently, in order to independently verify that a DID Document was indeed produced and published by the controller of a did:dht, implementers have to resolve using pkarr relays as noted here:

Are there any technical reasons preventing us from being able to return the signature from GET /dids/:did? It would be nice to leverage the simplicity of resolving a did:dht using the gateway endpoint while also being able to independently verify that the resolved document hasn't been tampered with.
This would also be beneficial for historical resolution.
Personally feel like providing a means to perform an integrity check is important as it prevents folks from falling victim to a bad actor gateway

my main concern is mixing layers (signed BEP44 messages and DID Documents), since DID Documents can have an optional proof property. this could be confusing since the underlying data that you'd be verifying is not a DID Document. without doing a transformation yourself you're trusting the server. it is safest to use the relay API directly for this reason.
what do you think?

it seems like we're already mixing layers as per how PUT /dids/:did works yeah as per 6.3.2

you're right, though this is my biggest sticking point

without doing a transformation yourself you're trusting the server

I would be more OK with removing the API you call out and keeping the GET did API as a utility.

I wonder if there are approaches we can take that make it easier to adopt and use using a familiar REST API?
One option is simply to provide high-quality, complete implementations in every major language.
... but I am still left wondering if there's a benefit to interacting with the DHT Gateways in the context of create, update, and deactivate operations if Register/Update APIs aren't available?  Does it mean that all of those have to go through a Pkarr relay? (in practice, it seems that DHT Gateways would also be Pkarr relays?)
Is there any value to using the DID Resolution Options accept property to specify and return alternate representations of the DID document that might include data that isn't typically included?

I wonder if there are approaches we can take that make it easier to adopt and use using a familiar REST API?

that was the intention with the current API; though I'm concerned about adding a signature which could lead users into a false sense of trust since the DID data returned by the server pertaining to the data in the signature necessitates trusting the node, this is a problem.
Yes, it's true you need to trust the server for resolving a DID too, and publishing. However I think there is a larger risk of providing a false sense of security for a malicious node that return an altered DID Document state with a previously valid signature.
Until we can find a way to avoid this I'm not comfortable with this change proposal. I'm not sure adding a note warning to the contrary is good enough since it puts the burden on clients to decode the payload and compare it, and in that case what's the benefit of adding to this API?

but I am still left wondering if there's a benefit to interacting with the DHT Gateways in the context of create, update, and deactivate operations if Register/Update APIs aren't available?

the main benefit is the additional functionality you get around type indexing, retention proofs, and in the future, other types of indexing around aliases (maybe more too).

Does it mean that all of those have to go through a Pkarr relay? (in practice, it seems that DHT Gateways would also be Pkarr relays?)

DHT Gateways are Pkarr relays, so the answer is yes. This is true today will remain true.

Is there any value to using the DID Resolution Options accept property to specify and return alternate representations of the DID document that might include data that isn't typically included?

This is an interesting idea that we can/should explore...but may end up being more complex than sticking to something the spec itself defines.

that was the intention with the current API; though I'm concerned about adding a signature which could lead users into a false sense of trust since the DID data returned by the server pertaining to the data in the signature necessitates trusting the node, this is a problem.
Yes, it's true you need to trust the server for resolving a DID too, and publishing. However I think there is a larger risk of providing a false sense of security for a malicious node that return an altered DID Document state with a previously valid signature.

I could be wrong but I believe the motivation behind asking for the signature be returned in the GET /did:id response is precisely to allow for an additional level of verification so that the DHT gateway need not be trusted.  In other words, the caller could take the DID Document, sequence number, and signature ... convert the DID document to a DNS packet, encode, bencode, and then verify the signature.
It seems that the trust involved in resolving a DID to a DID document isn't any worse than calling GET /did/:id given that either way you don't know whether the DHT Gateway tampered with the results.  In many cases its sufficient to trust the gateway but there may be cases where additional measures are needed in high assurance scenarios.
Perhaps there should be a separate interface (or optional query property) that can be called to retrieve the signature information that would be needed to verify the returned DID document?  That way someone has to go out of their way to request this and may be more likely to understand the tradeoffs.
On a related topic, what about signature availability for Historical Resolution?  Since mainline DHT nodes don't keep the old state, it would seem that being able to verify signatures for what a Gateway claims is the historical state of a DID's keys would be crucial for any high assurance scenarios.

after further consideration I am on board with your assessment, and the original suggestion

I could be wrong but I believe the motivation behind asking for the signature be returned in the GET /did:id response is precisely to allow for an additional level of verification so that the DHT gateway need not be trusted. In other words, the caller could take the DID Document, sequence number, and signature ... convert the DID document to a DNS packet, encode, bencode, and then verify the signature.

I will add guidance saying that this is an obligation of a conformant client and add signature data to both the get and historical APIs

Going to implement this I realized that without also including the seq and v in original form the data cannot be verified properly.
This means that the DID API would turn into the Pkarr API and also return DID Documents.
So we have two options:

Keep things as-is, resulting in two fetches -- one for Pkarr info (verifiable), one for DID Docs (untrusted)
Amend the DID API to add in the content of the Pkarr API

My main problem, now, with (2) is that it makes returning the DID Document less meaningful. Why return it at all if it needs to be reconstructed from the Pkarr response? What utility is it really adding?
So...after even further consideration...I'm back to my original position to keep these APIs separate.
To @mistermoe 's original point

It would be nice to leverage the simplicity of resolving a did:dht using the gateway endpoint while also being able to independently verify that the resolved document hasn't been tampered with.

This can be accomplished today with two API calls. If the main benefit is returning strings instead of bytes, or requesting with a DID instead of a Pkarr ID, we can consider additional API endpoints.

After chatting with @frankhinek  -- as a convenience will provide a b64URL encoded Pkarr Get response (seq:sig:v) alongside the DID API, also for historical data.

#110


Adopt postgresql-api-plugin

Description

@cyrille-leclerc I would like to adopt this plugin to update the dependencies and likely add a dependency on it to database-postgresql plugin but I would like to be able to release those plugins together when needed.
https://github.com/jenkinsci/postgresql-api-plugin
Submitter checklist for adding or changing permissions

Always

[x] Add link to plugin/component Git repository in description above

When enabling automated releases (cd: true)

[ ] Add a link to the pull request, which enables continuous delivery for your plugin or component.
Follow the documentation to ensure, your pull request is set up properly.

When adding new uploaders (this includes newly created permissions files)

[ ] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[ ] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[ ] Make sure to @mention the users being added so their GitHub account names are known if they require GitHub merge access (see below).
[ ] All newly added users have logged in to Artifactory and Jira at least once

Reviewer checklist (not for requesters!)

[ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
[ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
[ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
[ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @Wadeck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

Thank you very much for your offer, I accept with great pleasure.


request: Use buttons a.k.a. "message components" for bot interaction instead of emotes

Is your feature request related to a problem? Please describe.
Discord has introduced buttons, which are intended to replace emotes when interacting with bot messages: https://discord.com/developers/docs/interactions/message-components .
Example 1:

Example 2:

Describe the solution you'd like
Use buttons instead of emotes for interacting with the bot where appropriate (i.e. moving through directories, queues, etc.).
Describe alternatives you've considered
Continuing to just use the emote reactions.
Additional context
Button implementation would be better for accessibility.

This is on the roadmap already. Currently it is blocked by the availability of Discordjs v13 however.


Pending invitations shown on channel home page

If the usage of Promises is pervasive, may be worth adding a shim for them.

RE: Promises https://github.com/fle-internal/content-curation/pull/274


Messes up already installed Textual 0.51.0

Prior to installing this package I had Textual version 0.51.0 installed and working OK.
Cloning, building and installing this (using pip install -e .. Correct?), caused all Textual examples to fail.
E.g. running py -3 examples/calculator.py:
Traceback (most recent call last):
  File "F:\gv\Python310\Lib\site-packages\Textual-Github\examples\calculator.py", line 11, in <module>
    from textual import events, on
ImportError: cannot import name 'on' from 'textual' (F:\gv\Python310\lib\site-packages\textual\__init__.py)

I assume it's this line:
https://github.com/hdb/baywatch/blob/747d9b2ed1f96a60ce27c612710382990307ace8/pyproject.toml#L23
that caused it.
From the above pip install -e ., I saw textual-0.1.18 textual-inputs-0.2.6 got installed.
I do not know much about pip, but why not "textual >=0.1.17"?
BTW. I'm on Win-10 Home, 22H2 (OS-build 19045.4046).

I would recommend installing baywatch to a virtual environment so that it doesn't mess with your existing textual installation. I built this using an earlier version of textual before there was a stable API so I think it is likely not compatible with the latest version of textual.

@hdb Okay, But I absolutely loath virt-envs. It's very easy (for me) to mess up some vital detail.
So could it be < 0.1.17 and >=0.1.17 compatible?


Krew Support

Hi there, it would be nice to be able to install this via Krew: https://github.com/kubernetes-sigs/krew

Thank you for reaching out.
I will support Krew!

Created the PR to add this plugin to krew-index🔥
https://github.com/kubernetes-sigs/krew-index/pull/1891

@DWSR
Supported kubectl krew install explore! Please try it😊

WFM. :)


Switch to http-client-0.5.*

If needed I can add CPP to allow http-client-0.4.* too.
I would love to see this fix released and added to Stackage. Thanks!

It appears that BOT_TOKEN and CHAT_ID environment variables are not defined.
I guess someone has to add them through CircleCI interface?

@fizruk Hi, thank you for contribution. It's not exposed due to security reasons. You can configure your CircleCI for your repository, but before merge I will run it on my CI anyway

I see the circle.yml looks at CIRCLE_PULL_REQUEST variable to not run integration tests, but Circle CI uses a different name — CI_PULL_REQUEST, so the build fails. Should I also fix that?

@klappvisor I've fixed the build for PRs. Did you have time to run integration tests on your CI?

Thank you!

@fizruk Thank you for contribution! uploaded newest version to hackage


Add options for provider and propquery in evp_test

This PR introduces two new command line options in evp_test to specify the provider and property query directly without configuration file. In cases when no configuration file is provided and no provider is specified, the default provider is used instead. These modifications are part of the ongoing expansion of the evp_test functionality, as discussed in issue #21424.

Ping @openssl/committers for the review

This pull request is ready to merge

Merged. Many thanks!


Create Glue Crawler is missed

Describe the bug
When creating a Glue Crawler from the console, the call to create the Crawler itself is missed.
Related Mapping
glue.CreateCrawler
Related Language
n/a
To Reproduce

Go to https://console.aws.amazon.com/glue/home?region=us-east-1#catalog:tab=crawlers
Click Add Crawler
Fill out required information
Click Add Crawler

Expected behavior
Glue Crawler would be created in the resulting code. Currently the secondary items are created successfully (Glue Connection, Glue Database) when using the same wizard, but not the Crawler itself.
Screenshots
n/a
Additional context
n/a

Hi Andrew,
Thanks for raising. I tried to reproduce but was only able to successfully create the crawler resource. Could you attempt to reproduce and check both the main.html and bg.js console logs to see if there is any obvious issues there?
Cheers,
Ian.

OK, I tried again today. I was able to narrow down the problem slightly. When I create a Glue Crawler with an S3 input source, it seems to work, but if I create one which has a JDBC datastore, it doesn't get captured.
Here is the bg.js logs from the successful S3 crawler creation:
{"actionResponses":[{"action":"com.amazonaws.console.glue.shared.UserPreferenceRequestContext.getUserPreference"}]}  bg.js:5398:13

{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AWSGlueContext.getSecurityConfigurations","data":{"securityConfigurations":[],"nextToken":""}}]}  bg.js:5398:13

{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AmazonS3Context.listBuckets","data":<redacted>]}  bg.js:5398:13

{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AWSGlueContext.getConnections","data":{"connectionList":[{"name":"test","description":"","connectionType":"JDBC","connectionProperties":{"JDBC_ENFORCE_SSL":"false","JDBC_CONNECTION_URL":"jdbc:postgres://something:5432/databasename","USERNAME":"username"},"physicalConnectionRequirements":{"subnetId":"subnet-<redacted>","securityGroupIdList":["sg-<redacted>"],"availabilityZone":"us-east-1b"},"creationTime":1554130760555,"lastUpdatedTime":1554130760555}]}}]}  bg.js:5398:13
{"actionResponses":[{"action":"com.amazonaws.console.glue.shared.IAMRequestContext.listRoles","data":[{"roleName":"AWSGlueServiceRole-Glue","roleId":"<redacted>","arn":"arn:aws:iam::<redacted>:role/service-role/AWSGlueServiceRole-Glue"}]}]}  bg.js:5398:13

{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AWSGlueContext.getCrawler","error":{"message":"{\"service\":\"AWSGlue\",\"statusCode\":400,\"errorCode\":\"EntityNotFoundException\",\"requestId\":\"e7f01c7f-548f-11e9-964b-05ff9084c187\",\"errorMessage\":\"Crawler entry with name s3-crawler does not exist\",\"type\":\"AwsServiceError\"}","code":400}}]}  bg.js:5398:13

{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AmazonS3Context.listBuckets","data":[<redacted>]}  bg.js:5398:13

{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AWSGlueContext.getDatabases","data":{"databaseList":[{"name":"default","description":"Default Hive database","locationUri":"hdfs://ip-172-20-79-123.ec2.internal:8020/user/hive/warehouse","createTime":1528479163000},{"name":"sampledb","description":"Sample database","parameters":{"CreatedBy":"Athena","EXTERNAL":"TRUE"},"createTime":1528479057000}]}}]}  bg.js:5398:13

Calling notify  bg.js:2022:5

Type error for parameter options (Property "buttons" is unsupported by Firefox) for notifications.create.  bg.js:2023

{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AWSGlueContext.createCrawler","data":{}}]}  bg.js:5398:13

{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AWSGlueContext.listCrawlers","data":{"crawlerNames":["s3-crawler"]}}]}  bg.js:5398:13

{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AWSGlueContext.getTaggedResources","data":{"paginationToken":"","resourceTagMappingList":[]}}]}  bg.js:5398:13

{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AWSGlueContext.batchGetCrawlers","data":{"crawlers":[{"name":"s3-crawler","role":"service-role/AWSGlueServiceRole-Glue","targets":{"s3Targets":[{"path":"s3://andlytle-test/","exclusions":[]}],"jdbcTargets":[],"dynamoDBTargets":[]},"databaseName":"default","classifiers":[],"schemaChangePolicy":{"updateBehavior":"UPDATE_IN_DATABASE","deleteBehavior":"DEPRECATE_IN_DATABASE"},"state":"READY","crawlElapsedTime":0,"creationTime":1554131284000,"lastUpdated":1554131284000,"version":1}],"crawlersNotFound":[]}}]}  bg.js:5398:13
{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AWSGlueContext.getCrawlerMetrics","data":{"crawlerMetricsList":[{"crawlerName":"s3-crawler","timeLeftSeconds":0.0,"stillEstimating":false,"lastRuntimeSeconds":0.0,"medianRuntimeSeconds":0.0,"tablesCreated":0,"tablesUpdated":0,"tablesDeleted":0}]}}]}  bg.js:5398:13

and here are the logs from the unsuccessful JDBC creation:
{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AWSGlueContext.getCrawler","error":{"message":"{\"service\":\"AWSGlue\",\"statusCode\":400,\"errorCode\":\"EntityNotFoundException\",\"requestId\":\"8b011b01-5490-11e9-bb13-8bbe5f181416\",\"errorMessage\":\"Crawler entry with name jdbc-crawler does not exist\",\"type\":\"AwsServiceError\"}","code":400}}]}  bg.js:5398:13
{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AmazonS3Context.listBuckets","data":[<redacted>]}  bg.js:5398:13

{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AWSGlueContext.getDatabases","data":{"databaseList":[{"name":"default","description":"Default Hive database","locationUri":"hdfs://ip-172-20-79-123.ec2.internal:8020/user/hive/warehouse","createTime":1528479163000},{"name":"sampledb","description":"Sample database","parameters":{"CreatedBy":"Athena","EXTERNAL":"TRUE"},"createTime":1528479057000}]}}]}  bg.js:5398:13

{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AWSGlueContext.createCrawler","data":{}}]}  bg.js:5398:13

{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AWSGlueContext.listCrawlers","data":{"crawlerNames":["jdbc-crawler","s3-crawler"]}}]}  bg.js:5398:13

{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AWSGlueContext.getTaggedResources","data":{"paginationToken":"","resourceTagMappingList":[]}}]}  bg.js:5398:13

{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AWSGlueContext.batchGetCrawlers","data":{"cra
wlers":[{"name":"s3-crawler","role":"service-role/AWSGlueServiceRole-Glue","targets":{"s3Targets":[{"path":"s3://andlytle-test/","exclusions":[]}],"jdbcTargets":[],"dynamoDBTargets":[]},"databaseName":"default","classifiers":[],"schemaChangePolicy":{"updateBehavior":"UPDATE_IN_DATABASE","deleteBehavior":"DEPRECATE_IN_DATABASE"},"state":"READY","crawlElapsedTime":0,"creationTime":1554131284000,"lastUpdated":1554131284000,"version":1},{"name":"jdbc-crawler","role":"service-role/AWSGlueServiceRole-Glue","targets":{"s3Targets":[],"jdbcTargets":[{"connectionName":"test","path":"%","exclusions":[]}],"dynamoDBTargets":[]},"databaseName":"default","classifiers":[],"schemaChangePolicy":{"updateBehavior":"UPDATE_IN_DATABASE","deleteBehavior":"DEPRECATE_IN_DATABASE"},"state":"READY","crawlElapsedTime":0,"creationTime":1554131558000,"lastUpdated":1554131558000,"version":1}],"crawlersNotFound":[]}}]}  bg.js:5398:13

{"actionResponses":[{"action":"com.amazonaws.console.glue.awssdk.shared.context.AWSGlueContext.getCrawlerMetrics","data":{"crawlerMetricsList":[{"crawlerName":"jdbc-crawler","timeLeftSeconds":0.0,"stillEstimating":false,"lastRuntimeSeconds":0.0,"medianRuntimeSeconds":0.0,"tablesCreated":0,"tablesUpdated":0,"tablesDeleted":0},{"crawlerName":"s3-crawler","timeLeftSeconds":0.0,"stillEstimating":false,"lastRuntimeSeconds":0.0,"medianRuntimeSeconds":0.0,"tablesCreated":0,"tablesUpdated":0,"tablesDeleted":0}]}}]}  bg.js:5398:13

Here's what I get as total output for my two crawlers:
# pip install boto3

import boto3

glue_client = boto3.client('glue', region_name='us-east-1')

response = glue_client.get_security_configurations()
response = glue_client.get_connections()

s3_client = boto3.client('s3', region_name='us-east-1')

response = s3_client.list_buckets()
response = s3_client.list_buckets()
response = glue_client.get_databases()
response = glue_client.create_crawler(
    Name='s3-crawler',
    Role='arn:aws:iam::<redacted>:role/service-role/AWSGlueServiceRole-Glue',
    DatabaseName='default',
    Classifiers=[],
    Schedule='',
    Configuration='{"Version":1}',
    TablePrefix='',
    SchemaChangePolicy={
        'UpdateBehavior': 'UPDATE_IN_DATABASE'
    },
    Targets={
        'S3Targets': [
            {
                'Path': 's3://andlytle-test/',
                'Exclusions': []
            }
        ],
        'JdbcTargets': [],
        'DynamoDBTargets': []
    }
)
response = glue_client.get_classifiers()
response = glue_client.get_classifiers()
response = glue_client.get_security_configurations()
response = glue_client.get_connections()
response = s3_client.list_buckets()
response = s3_client.list_buckets()
response = glue_client.get_databases()
response = glue_client.get_classifiers()

Hey Andrew,
Thanks for clarifying the difference between the S3 and JDBC Crawlers. It helped in tracing what I believe was the issue down to the use of a decodeURIComponent call within the initial data processing. This broke when we had a % symbol in the payload, which is likely in your Include Path for a JDBC connection.
I've released a new version, 0.3.24 which should fix the issue.


Do not bail-out when a static problem is found

A file can have a mix of dynamic and static fs.readFileSync, and when a dynamic read is found, throws and error and stops the build.
Simply, if a dynamic read is found, it should continue with the next one, as is not a terminal error actually.
I've modified static-eval.js it to achieve this with:

Is a ugly workaround, but I had to test if this works. It worked.
Maybe there's a better way to achieve this.

In my latest commit I tried to get this working, but unfortunately the current approach requires us to evaluate things like __dirname into actual string literals before we can determine whether the resulting call is dynamic or not. By the time the dynamic nature is caught, we've already transformed the AST, so if we continue onward you'll end up with bugs in your final source code since some things like __dirname will have been transformed when they shouldn't for dynamic calls.
The fix for this is to first clone the path, then evaluate, and only if it succeeds, then we replace the path with the cloned & modified/evaluated path. However, I can't for the life of me figure out how to clone a node in babel (t.cloneNode doesn't give us back a NodePath, just a bare object), and the docs are so sparse that I can't really do anything until somebody with more knowledge of babel's internals chimes in here.
Maybe @azu if you are familiar with the babel APIs?


Invalid behavior of MessageUpdateEvent

Describe the bug
Old message isn't passed in event and its required to fetch old message in event handler, but message is removed in event constructor so it isnt accessible in event handler making event useless
To Reproduce
-/-
Expected behavior
-/-
Screenshots
-/-
Desktop (please complete the following information):

OS: -/-
Dart version -/-
Nyxx version: 3.2.7

Additional context
Add any other context about the problem here.

This feature would need to create custom way for cloning an object since we are have to update message in place because discord doesn't send whole message but only parts that changed. Going to put this issue on hold for now


[Bug] Log-likelihood evaluation in SCANDAL leads to NaNs

Dear all,
I came across following problem, after I had trained my neural densitor estimator plus score supplement (SCANDAL) without any problems, I tried to evaluate the log-likelihood using the trained network with a separate test sample.
However, I always get an NaN inside the MAF code. After introspecting with a forward module hook I could track it down to be inside self.Ws of the ConditionalMaskedAutoregressiveFlow with PDB.
As far as I can tell you, the values in self.Ws are normally produced - no NaNs.
However, after an call to self.to the NaNs appear...
SCANDAL is not necessary for the associated physics project, however, it would be nice to have in comparison.
Cheers,
Simon

Thank you for reporting this issue, and sorry for this bug!
We have neglected debugging the MAF code somewhat, and in a perfect world we'd totally rewrite it e.g. based on the nflows (https://github.com/bayesiains/nflows) library. Unfortunately, in the near future I don't know if I'll have any time I can spend on MadMiner. Maybe some other team member has time to look at this?

Thanks, @johannbrehmer for looking into it. In that case, I will just keep my fingers off SCANDAL.
A little more information, it already seems to be an issue with the write-out after training (maybe, a from call)? I do not know for sure, but I will take my investigations on.
However, if you plan for a re-implementation, then this issue will be more or less a not-to-be-fixed.


Fix: rubocop-performance SafeMode deprecation version

Rubocop v0.74.0 changelog says:
Deprecate the SafeMode option. Users will need to upgrade rubocop-performance to 1.15.0+ before the SafeMode module is removed. ([@rrosenblum](https://github.com/rrosenblum))

But rubocop-performance version 1.15.0 does not exist. This was introduced in this PR
It should say 1.5.0 instead of 1.15.0.
According to rubocop-performance releases, SafeMode was removed in version 1.5.0

Thanks!


fix: useScript failed to remove script from cache when passing removeOnUnmount prop

The removeOnUnmount prop didn't remove the script from the cache. This created a side effect where if you try and render the same component by mounting -> unmounting -> mounting again, the useScript hook behaves as the script is loaded when in reality is has remove the script from the tree but failed to remove it from the cache.
Issue: https://github.com/juliencrn/usehooks-ts/issues/314

Any bump on this? Ran into this issue while trying to add a Hubspot calendar iframe and this definitely fixes it.

@scottwiw based on this issue, and the amount of PRs that has no activity I think this package is basically abandoned, I would suggest co locating the whole useScript and fixing it yourself.

@scottwiw based on this issue, and the amount of PRs that has no activity I think this package is basically abandoned, I would suggest co locating the whole useScript and fixing it yourself.

Thanks, I'll make do. Appreciate it!

Thank you @ShanSenanayake 👍


Question about initial setup

@AllanOricil
Hello,
I am extremely new to ESP, but would love to get this project working on my end.
If I were to purchase ESP32-2432S028, plug it into my computer and follow the instructions from https://allanoricil.github.io/esp32-mfa-authenticator to install the latest build, would that essentially be all there is to this? Other than formatting an SD card with the config.yml and keys.txt?
I was getting confused with the "Dev Environment Requirements" and "How to build" sections and if those steps were only needed if the website was not used to install the latest build.
Kindly let me know your thoughts - thank you!

Install the drivers on your computer.
Insert the SD card with the required files into your ESP32
Connect the ESP32 to your computer over USB
Open the site using Google Chrome. Some browsers aren't supported.
Read the tutorial and the README before installing the build on your ESP32. Pay attention to the steps where it explains about the calibration of the touch sensor. If you don't calibrate it right during the first launch, when the board asks you, you will have power off ESP32, remove the SD card from the board, plug the SD Card in your computer, change force_recalibration in config.yml, save it, put the SD card back to your ESP32, connect the ESP32 to your computer, go to the install website, connect it to the board,  this time click on the logs button, finally reboot your board, and wait for the touch calibration messages appear again.
Now that you are aware you will be prompted to calibrate the touch right after flashing the code into your board. Go to the install website, and follow the tutorial. Again, be ready for the calibration step, otherwise you will have to follow the steps from step 5.

@AllanOricil - your instructions are great and this is probably just me, as I have not done anything with an ESP32 yet.
Additional questions:
To clarify, in your response Step 1, the drivers you mean are the ones located here, right? https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers
If so, once I install those, I can set up my SD card with the two needed files, insert the card into the ESP32 and connect it to the computer, followed by your build install website.
Is that all correct?

@Son-Vegitto I'm not sure if those drivers will work for you. I don't know your OS and processor architecture. Try it and tell me later. 👍

@Son-Vegitto I saw that the site has drivers for other OS. Before installing those drivers, just plug the esp32 into your pc via USB, and check if it is recognized by opening my instal website, and the click on the start button to see if your browser can recognize the board. If it doesn't, then download the driver for your OS, and repeat the above steps. If that doesn't work, then Google esp32 driver and see if you find something that works for you. In my case, it worked after installing the driver for MacOS listed on that link.

@Son-Vegitto you should try v0.13.0
It now has a screen to help you configure the touch sensor upon first boot.


Add compliance:reports:export to both viewer roles

     3 | viewer            | Viewer            | chef-managed | {compliance:reports:export,infra:infraServers:list,infra:infraServers:get,secrets:*:get,secrets:*:list,infra:nodes:get,infra:nodes:list,infra:nodeManagers:get,infra:nodeManagers:list,compliance:*:get,compliance:*:list,event:*:get,event:*:list,ingest:*:get,ingest:*:list,iam:projects:list,iam:projects:get,applications:*:get,applications:*:list}
     7 | compliance-viewer | Compliance Viewer | custom       | {compliance:reports:export,compliance:*:get,compliance:*:list}

Ok so here's the problem: if compliance-viewer is not a chef-managed role, we should not be touching it after we've created it. We only created it conditionally on the role not already existing, so we're also potentially updating a role that a customer created but we didn't know about.

added do not merge, cause we are trying to figure out if we can change the action instead

fixed in #3623


[bug]: slect lags when use many options

Describe the bug
i've used next js 13 and fetched google fonts from api and used select, application starts lagging as soon as select is opend
Affected component/components
selec
How to reproduce

get google fonts from api
and use in select

Codesandbox/StackBlitz link
No response
Logs
No response
System Info
chrome browser

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

This is not library bug, just a common problem when you deal with render largest list in a website. Try to integration with a library like react-window to reduce number of html tag rendered

@Chetan-KK use something like Shadcn Virtualized Combobox to render large list in a virtualized manner, so that your select component doesn't lag


Api refacto

Codecov Report
Patch coverage: 65.51% and project coverage change: +1.71 :tada:

Comparison is base (1ecaa92) 35.55% compared to head (fe65b1b) 37.27%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #124      +/-   ##
==========================================
+ Coverage   35.55%   37.27%   +1.71%
==========================================
  Files           9        9
  Lines         644      676      +32
==========================================
+ Hits          229      252      +23
- Misses        391      399       +8
- Partials       24       25       +1

Impacted Files
Coverage Δ

pkg/wallet/wallet.go
0.00% <0.00%> (ø)

internal/handler/wallet/export.go
48.57% <50.00%> (ø)

internal/handler/wallet/sign.go
55.84% <50.00%> (ø)

internal/handler/wallet/get.go
68.65% <66.66%> (ø)

internal/handler/wallet/import.go
78.12% <78.12%> (+28.12%)
:arrow_up:

internal/handler/wallet/delete.go
67.50% <80.00%> (ø)

internal/handler/wallet/create.go
84.09% <83.33%> (ø)

internal/handler/wallet/api.go
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


fix for Python of version lower than 2.7

According to https://github.com/scisoft/autocmake/issues/64#issuecomment-129143029 .

Hi Miro please just change the commit message and the comments. This has in my understanding
nothing to do with Python 2.7 or lower but with the fact that your compilation
writes warnings to stderr.

Also if you fix an issue with a PR, please auto-close it with the commit message.

Good, after some playing with commit message and rebasing I imbue the change. Is it OK now ?

Do you need also the second assert removed? Compilation should write only to the first.

I fixed it, but where is "All checks have passed" ?

Ah, I see, it showed up after some while.


OwnCloud 8 RainLoop plugin will not let me log in after update

I originally had RainLoop working with the OwnCloud plugin on OwnCloud 7, after updating to 8 i can no longer log into my email (says:  authentication failure).  Log in still works fine when I go directly to the RainLoop web client, and only fails when I use the OwnCloud plugin.

I'm seeing the same problem.  I now understand that the OC7 -> OC8 upgrade actually resulted in installing a completely new Rainloop instance under the OC apps directory.  I went through the new instance's admin panel to configure things.  I was able to set the OC user's credentials in the OC Personal settings.   Everyhting seems to work until I try to actually log in as a user.  Then auth fails.
My username for Rainloop is not the same as my OC username, so I don't have that option set.
I'm not even sure where the Rainloop logs would be to check why auth is failing.

Try to check RainLoop's logs.
<rainloop-data-folder>/...../logs/

Config:
<rainloop-data-folder>/...../application.ini

[logs]
enable = On

Could you help me find the right folders/config files?
Assume I have owncloud in my root folder (so /var/www/owncloud).
My data folder contains 2 files: EMPTY and VERSION
/var/www/owncloud/apps/rainloop/app/data
I don't see an application.ini at all via find /var/www/owncloud application.ini

Yes, you may find it (RainLoop data folder) into ownCloud data folder.

mine is in my /var/www/rainloop/data/data.../default/
however my logs work when I log in via rainloop web app, from the owncloud app it doesn't seem to generate logs at all.  All I get is "Authentication Failed".  Again, I only experience this in the owncloud plugin, rainloop itself works fine.  The previous owncloud plugin, before I updated to owncloud 8, also worked fine.  I'll see if I can maybe find something in the owncloud logs.

The previous owncloud plugin, before I updated to owncloud 8, also worked fine.

@Luticus
Sorry, but new version works only with RainLoop ownCloud package.
Why do you use external RainLoop application?

I've enabled logging after finding the data directory in the owncloud storage, not in /var/www/owncloud
It looks like the login is trying to authenticate me with my domain email, which isn't my username on the IMAP server.  So I cleared the default domain setting, leaving it blank.  Now when I try to login rainloop thinks the login is not a valid email, so doesn't even try to authenticate with the IMAP server.
Maybe this is misconfigured, but how do I get rainloop to try authenticating with just the "username" provided into the "email" field?

Try to enable "Use short login" setting in domain popup.

Ah - that did it.  This was because I had the standalone rainloop install in OC7 configured.  When I updated to OC8 and installed the new owncloud rainloop app it already had some of my config, including valid domains.  I forgot to double check the domain settings.
Works great now - thanks!

You welcome :)

Alright I've figured out what the problem was.  Aparently I thought that the owncloud plug in just used the settings from the regular rainloop.  Now that I've figured out that they are decoupled and I saw the admin panel access in ownclouds settings, everything seems to work fine.
Well except for contacts, I'm getting an error when i tell it to connect to the database that says "Personal address book driver not allowed".  Let me know if you know a quick fix or if I should open a new issue.
Thanks for all your help :)

You do not need to configure the contact database in OC RainLoop. It just uses the users's OC contacts automagically.


Add repeat parameter to command line tool

Needed the repeat parameter because my device was detecting too many presses. Thought I'd contribute it back.

Rebased and merged.
See https://github.com/milaq/rpi-rf/commit/7db12c01b5046df775525cc478739ba1e244b263
Much appreciated, thank you :+1:


Improve search data file

The files generated by jekyll contain a lot of spaces and empty lines, especially all-translation.json used by the jQuery search script.
It could be minified with a Jekyll plugin or ruby script run by travis/rake.
Also, this file contain titles in all languages but the search script use only the current language.
So, we could generate a file by language and load only one at a time.
Search take care of accentuated char:

In french the search editeur return "Edition avancée", "Editer le Wiki OSM"
The search éditeur find "Éditer à distance…", "Éditeur iD", "Éditer avec JOSM"

:bulb: To "fix" this, I suggest to test a plugin with full text search capabilities like jekyll-lunr-js-search

Originates from https://github.com/hotosm/learnosm/issues/19#issuecomment-13016637
Discussed in https://github.com/hotosm/learnosm/issues/150
Need to assess the proposal from @pyrog with

:bulb: To "fix" this, I suggest to test a plugin with full text search capabilities like jekyll-lunr-js-search

See #328 to discuss how to use Travis.CI

Closing as stale. A champion willing to work on this is weL come to open it and work on it.


Create a unified WasmResult for all WASM error codes.

This will subsume MetadataResult.

Fixed in #133


Fabo/1533 show waiting for connection

Closes #1533
Description:
Will need a follow up:

[ ] Check all modal interactions for being disabled if offline
[ ] Add unit test for reconnection if node not reachable

❤ Thank you!

[ ] Added entries in CHANGELOG.md with issue # and GitHub username
[ ] Reviewed Files changed in the github PR explorer

need to fix conflicts and then we should be ok


[Refactor] Replace mockable FakeKeystore with real FakeEtherKeystore #5028

Closes #5028

To review? Remember the wip commit.

BTW, do you think we should keep the codeowner configuration which sets a default reviewer? Or does having it make it worse?

i don't know, up to you :)

BTW, do you think we should keep the codeowner configuration which sets a default reviewer? Or does having it make it worse?

i don't know, up to you :)

Ok, Created #5033. Let's see if the PR is done correctly and if it helps :)