YOLOv8 - classes invertion in data.yaml

Hello,
I'd like to report a minor bug. I've annotated a dataset with Roboflow. I exported my data in YOLOv8 format but 2 classes are inverted in data.yaml. The model have been trained sucessfully but when I display the labels on images, they are inverted...
train: ../train/images
val: ../valid/images
test: ../test/images

nc: 9
names: ['Bibendum', 'Casquette', 'Dunlop', 'Goodyear', 'Michelin bibendum', **'Michelin logo carre', 'Michelin logo',** 'Michelin sept', 'Pneu']

roboflow:
  workspace: tmf
  project: michelin-gt
  version: 11
  license: CC BY 4.0
  url: https://universe.roboflow.com/tmf/michelin-gt/dataset/11

I expected :
names: ['Bibendum', 'Casquette', 'Dunlop', 'Goodyear', 'Michelin bibendum', 'Michelin logo', 'Michelin logo carre' 'Michelin sept', 'Pneu']
Here are the augmentations / preprocessing steps I choose in Roboflow before exporting :
PREPROCESSING
Resize: Stretch to 640x640
Modify Classes: 4 remapped, 3 dropped
AUGMENTATIONS
Outputs per training example: 3
Rotation: Between -15° and +15°
Saturation: Between -25% and +25%
Brightness: Between -25% and +25%
Exposure: Between -25% and +25%

Hi @erwanlenagard , thanks for opening an issue. Could you please add<EMAIL_ADDRESS>to your workspace?

Hi @FrancescoSaverioZuppichini, It's done. The error is related to "Michelin GT" project. By the way, there is also an error when I unzip the dataset archive on Windows manually or through the API : the file path is too long.

@erwanlenagard thanks 🙏 keep in mind these are your file so you can change their names to whatever works for you. Let me know if this helps 😄

@erwanlenagard it looks like it may be caused by the fact that one is a substring of another, we are not 100% sure yet. In the meantime, feel free to try and change the class name and see if the order is correct


Problems when map is added to a dialog

From directory:

When I load the add-on on a Dialog the behavior is changed:

marker.addDragEndEventListener() (event) is never executing,
polygon.addClickListener() (event) is never executing,
info window is not shown

But, when I load the add-on on main application's window all the above issues are solved.

This issue is related to issues #51 & #49

I was able to reproduce this. First time opening the dialog it all works ok. Second time all things mentioned above stop working as expected.


[SPARK-41372][CONNECT][PYTHON] Implement DataFrame TempView

What changes were proposed in this pull request?

Implement DataFrame TempView (which is createTemView and createOrReplaceTempView). This is a session local temp view which is different from the global temp view.
Why are the changes needed?

API coverage.
Does this PR introduce any user-facing change?

NO
How was this patch tested?

UT

Can one of the admins verify this patch?

Merged to master, thanks!


Could you support nextjs?

I really like this plugin anyway! it made me frustrated finding this auto-import feature. I have read so many articles but none of them would work. But it would be even better if you could support nextjs, please (?

Given:
export default function Home() {
  return (

                                                         {/*  Cursor on the word `Head`. */}
        <title>Create Next App</title>
        <link rel="icon" href="/favicon.ico" />

Got:
import Head from "../node_modules/next/dist/shared/lib/head";

export default function Home() {
  return (

        <title>Create Next App</title>
        <link rel="icon" href="/favicon.ico" />

      ...

But I expect:
import Head from "next/head";

export default function Home() {
  return (

        <title>Create Next App</title>
        <link rel="icon" href="/favicon.ico" />

Is this next folder from the 2nd screenshot in node modules or in the root?

Yes, the node_modules/ is a children folder of my project folder.

This plugin ia not really able to handle node module files. You should be able to handle this with LSP auto import.


fix getupdatedserverurl

Fix problem getting updated server url if context is not the same name as the cluster.

cancel, did not fix issue


Add SVGExplorerExtension 1.0

Microsoft Reviewers: Open in CodeFlow

Indeed it's a know issue: https://github.com/tibold/svg-explorer-extension/issues/74


A white line at the top of the window on macOS Monterey

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:版本:
1.65.0
提交: b5205cc8eb4fbaa726835538cd82372cc0222d43
日期: 2022-03-02T11:13:50.741Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin arm64 21.3.0

OS Version: macOS 12.2.1 (21D62)

Steps to Reproduce:

As long as the system is in light mode and vscode is in a dark theme, a white line will appear on the top of the vscode window. When the system switches to dark mode, it will disappear. This white line is really distracting. Hope you can fix this.

Not sure whether this may be from our custom title or a general Electron / OS issue.

The issue reproduces in Big Sur on the Insiders and Exploration builds, as well as on Electron Fiddle.

@rzhao271 can you try with vscode PWA application.

@rzhao271 can you try with vscode PWA application.

I installed vscode PWA application from chrome, and there seems to be no white line.

I have confirmed the issue has been in Electron since version 9.

@rzhao271 Is there any progress on this?

Can confirm. Also a few screenshots of how the borders look in light/dark mode, hoping they help (I think you can just about see the side borders):

I noticed that in dark mode, it becomes more of a uniform border along the edge of the whole window, whereas in light mode, the borders on the side and bottom are almost gone, and the border on the top (wrapping around the rounded corners a little) are significantly brighter

Upvote for solving this issue.

It's so annoying and catches my eyes every time I see the VSCode windows.
Maybe the issue is related to Electron and I think there are solutions for this.

https://github.com/electron/electron/issues/13164
https://github.com/electron/electron/issues/15008

Here are some Electron apps that resolve the white top border. They have light (no white) border surrounding the window, or even without border.
Cron

Slack

MongoDB Compass

Figma

Here are some Electron apps that also suffer from white top border like VSCode.
VSCode

GitKraken

Trello

Notion

Spark

And lastly here are macOS native apps.
Clock

Final Cut Pro

iTerm

KakaoTalk

I am trying to reproduce the behaviour but for me VS Code (1.79.x) seems to show the same border color, irrespective if my macOS theme is set to dark or light?
Here are my results in both OS themes:

This is with macOS ventura 13.4.1 (22F82)

That's weird. Here are what it looks like on my machine (27-inch, 4K). Are you using retina display? It looks like your screenshots are low resolutions. Maybe the antialiasing on your display makes the results look similar.
Light Mode

Dark Mode

I am on a Dell U2515H with a resolution of 2560x1440.

Any update on this issue? as the latest release (1.94.x) breaks the https://github.com/drcika/apc-extension


Add able to select scene camera in editor viewport. (3.0)

Port of https://github.com/godotengine/godot/pull/12705 for master branch

What's the point of this feature, given that there is already a "preview" button in all viewports when you select a Camera in the SceneTree? When you press it, that Camera is set as the preview for that viewport, and it's persistent.
So the feature you're implementing already exists.

@akien-mga  The preview mode does't make it possible to apply any modifiers to the objects of the scene. In my opinion, it's worth letting game designers edit the scene from the game camera.

Maybe there could be a toggle to enable editing when a viewport is assigned a Camera in preview mode?

@akien-mga I think complicate preview mode interface is a bad idea.

Well adding another interface for the same feature doesn't seem like a good idea either :)

Current preview interface is fine IMO, we did not have much complaints about it.
What doesn't work and it should is probably editing while in preview mode..

Closing this, as there is not much agreement. I think it may be more desirable to allow editing from the camera previwe


feat(blogposts): Build a Blog with Scully and Webiny

This blog is taken care in separate PR and the blog is live at https://www.webiny.com/blog/build-blog-scully-webiny-headless-cms Thus closing this PR.


Mock history is not cleared when running with concurrent

Describe the bug
Given a basic.ts file:
import { randomUUID } from 'crypto';

export function genUUID() {
  return randomUUID();
}

export function noop() {}

and the basic.test.ts test:
import { describe, expect, it, vi, afterEach } from 'vitest';
import { genUUID, noop } from './basic.js';
import { randomUUID } from 'crypto';

vi.mock('crypto', () => ({ randomUUID: vi.fn() }));

// doesn't work
describe.concurrent('concurrent', () => {
  describe('noop', () => {
    it('noop 1', () => {
      noop();
    });

    it('noop 2', () => {
      noop();
    });

    it('noop 3', () => {
      noop();
    });
  });

  describe('genUUID', () => {
    afterEach(() => {
      // None of the following works
      vi.clearAllMocks();
      vi.resetAllMocks();
      vi.restoreAllMocks();
    });

    it('genUUID 1', () => {
      genUUID();
      expect(randomUUID).toHaveBeenCalledOnce();
    });

    it('genUUID 2', () => {
      genUUID();
      // AssertionError: expected "spy" to be called once, but got 2 times
      expect(randomUUID).toHaveBeenCalledOnce();
    });

    it('genUUID 3', () => {
      genUUID();
      expect(randomUUID).toHaveBeenCalledOnce();
    });
  });
});

// works
describe('serial', () => {
  describe('noop', () => {
    it('noop 1', () => {
      noop();
    });

    it('noop 2', () => {
      noop();
    });

    it('noop 3', () => {
      noop();
    });
  });

  describe('genUUID concurrent', () => {
    afterEach(() => {
      vi.clearAllMocks();
      vi.resetAllMocks();
      vi.restoreAllMocks();
    });

    it('genUUID 1', () => {
      genUUID();
      expect(randomUUID).toHaveBeenCalledOnce();
    });

    it('genUUID 2', () => {
      genUUID();
      expect(randomUUID).toHaveBeenCalledOnce();
    });

    it('genUUID 3', () => {
      genUUID();
      expect(randomUUID).toHaveBeenCalledOnce();
    });
  });
});

All 3 vi.clearAllMocks, vi.resetAllMocks, and vi.restoreAllMocks do not clear the mock history as expected when the tests are run with concurrent.
 RUN  v1.2.2 /home/projects/vitest-dev-vitest-34zo9k

 ❯ src/basic.test.ts (12)
   ❯ concurrent (6)
     ✓ noop (3)
       ✓ noop 1
       ✓ noop 2
       ✓ noop 3
     ❯ genUUID (3)
       ✓ genUUID 1
       × genUUID 2
       ✓ genUUID 3
   ✓ serial (6)
     ✓ noop (3)
       ✓ noop 1
       ✓ noop 2
       ✓ noop 3
     ✓ genUUID (3)
       ✓ genUUID 1
       ✓ genUUID 2
       ✓ genUUID 3

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 FAIL  src/basic.test.ts > concurrent > genUUID > genUUID 2
AssertionError: expected "spy" to be called once, but got 2 times
 ❯ eval src/basic.test.ts:39:26
     37|       genUUID();
     38|       // AssertionError: expected "spy" to be called once, but got 2 times
     39|       expect(randomUUID).toHaveBeenCalledOnce();
       |                          ^
     40|     });
     41|

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯

 Test Files  1 failed (1)
      Tests  1 failed | 11 passed (12)
   Start at  02:13:20
   Duration  2.05s (transform 103ms, setup 0ms, collect 91ms, tests 10ms, environment 0ms, prepare 262ms)

Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-34zo9k?file=src%2Fbasic.ts,src%2Fbasic.test.ts&initialPath=__vitest__/
System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.14.0 - /usr/local/bin/pnpm
  npmPackages:
    vite: latest => 5.0.12
    vitest: latest => 1.2.2

Used Package Manager
npm
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 reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

They are called at the same time, how would you expect them to be cleared? If you rely on a state outside of the test function, don't use concurrency.

Sorry, I am not sure what should be mentioned. Since tests are running at the same time, it would make sense that test hooks are also running at the same time, what other implementations are possible?

Sorry, I am not sure what should be mentioned. Since tests are running at the same time, it would make sense that test hooks are also running at the same time, what other implementations are possible?

@sheremet-va To provide some context, my motivation for raising this issue come from helping atlowChemi/vite-svg-2-webfont with upgrading their Vite and Vitest to the latest version.
One of their test cases, which is nearly identical to the sample code in the issue description, as you can see here: https://github.com/atlowChemi/vite-svg-2-webfont/blob/031a17fcd12d0514cbff8253dd3bf3f75ff36478/src/optionParser.test.ts#L29-L64. The test uses concurrent but toHaveBeenCalledOnce() works as expected. This functioned correctly with Vitest 0.26.3.
However, upgrading Vitest to 1.2.2 caused the test to fail, as shown in https://github.com/atlowChemi/vite-svg-2-webfont/pull/14#discussion_r1470543936.
I then tried each Vitest version from 0.26.3, and found that the test starts failing since 0.27.2. Despite examining the changes between, 0.27.1...0.27.2, I couldn't pinpoint the exact change causing afterEach to malfunction compared to previous versions. This led me to question if there have been any undocumented changes to the interaction between concurrent and Setup and Teardown functions.

Maybe it works sometimes, but not always?

I rerun the test for a dozen times, it seems like it always works in 0.26.3
https://github.com/vitest-dev/vitest/assets/20135478/c54e5519-82c8-4cbe-8c6d-f84121b0554b


V6.1.0

Bringing in changes to main I like them but tomorrow need to finish up what I'm doing and delete anything I was displaying to the UI for my own sake. Also need to update the website.


Fix tooltip showing on disabled buttons

PR Checklist
Please check all that apply to this PR using "x":

[x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[x] I have checked that this PR does not introduce a breaking change
[ ] This PR introduces breaking changes and I have provided a detailed explanation below

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting)
[ ] Refactoring (no functional changes)
[ ] Documentation changes
[ ] Other - Please describe:

Fixes
Issue Number: #196
What is the current behavior?
Disabled buttons on the toolbar shows tooltips on hover
What is the new behavior?
Tooltips are not shown on hover of a disabled button, only when it's enabled
Other information

First is firefox, then chrome then brave, all on linux

I think I see what you meant with the issue now, you want the tooltip to show up even if it's disabled, it's just that it's not hiding consistently when you move the mouse off of it, right? Initially I thought that you didn't want it to show up on disabled buttons, hence the initial solution.

Yes, I want it to also work on disabled components.
See https://github.com/reakit/reakit/issues/471

Ok after some testing and searching I managed to find a workaround.
The problem is that the mouse events don't fire on disabled elements, I guess firefox handles it a bit diffrently than chromium which is why the problem is happening.
What can be done and that I tested and it works, is that we could wrap the element (the button in this case) in a span or div, and we have to set the pointer-events css property of the disabled button to none. This way the events are handled by the parent and it works fine on chromium and firefox.
If that's fine with you I can make that change.

It seems like this is also the solution suggested by bootstrap which also uses popper.
https://getbootstrap.com/docs/4.0/components/tooltips/#disabled-elements

I submitted the changes in another PR (#200) so the commits are cleaner, closing this one


Editing cells with null values

Original author<EMAIL_ADDRESS>(February 08, 2011 19:42:08)
What steps will reproduce the problem?

click "edit" on a cell with a null value
change the value and apply to all identical cells

What is the expected output? What do you see instead?
One would expect all cells with null values to update. Instead no cells are changed, including the cell from which the edit was made.
What version of Google Refine are you using?
Version 2.0 [r1836]
What operating system and browser are you using?
Windows XP SP3, Chrome 9.0.597.84
Is this problem specific to the type of browser you're using or it happens
in all the browsers you tried?
Same issue using FF 3.6.13
Please provide any additional information below.
Dealing with nulls is generally problematic. Using any of the scripting tools to access null values produces errors. And it would be helpful to be able to differentiate nulls from blanks in the actual grid view of the data.
Original issue: http://code.google.com/p/google-refine/issues/detail?id=332

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Has there been any progress on this yet? Using OpenRefine 2.7 and still see the same behavior described by @tfmorris. When trying using the "Apply to All Identical Cells" it does not fill that cell, or any of the other identical cells when they are null, and it says Mass edit 0 cells in column X in the history.

Just to clarify, none of these posts are from me. I just did the import from Google Code. The original author of each message is in the first line of the message (look for italics and From ...)

Fixed in #1539 and #1598

This is still a problem in 3.0 Beta
Editing a cell which contains either a null or a zero length string, and then clicking "Apply to all identical cells" leads to NO edits being made (including the cell you started from).

Just an update - I'm working on this and work in progress is at https://github.com/ostephens/OpenRefine/tree/mass-edit-fix
tl/dr fix #1631 is relatively straightforward, but I'm trying to make tests and fix #1632, #180 and #332 at the same time which is proving more complicated and taking more time

Fixed by #1642


20190610 change #3: Added a new CSR (mclicbase) to specify the base address of CLIC memory mapped registers

Draft 20190610 – separating multiple changes as individual issues to enable change tracking/approval from draft-20190610 doc upload.

20190610 change #3: Added a new CSR (mclicbase) to specify the base address of CLIC memory mapped registers to give SW a consistent programming environment.

Can be tracked as separate issue: "Some general issues #57"

location
I want to reiterate the issue around knowing where a hart's CLIC M/S/U regions are located - I'd like to suggest that we probably need not just mclicbase but sclicbase/uclicbase (where appropriate) too - they're cheap because they're read-only

Closing here.


[Bug]: SharewithResult always returning null in Android

Platform
Android 11
Plugin
share_plus
Version
4.0.8
Flutter SDK
3.0.2
Steps to reproduce

use shareFilesWithResult and check the result. result.raw returns null

Code Sample
No response
Logs
[+54664 ms] Observatory URL on device: http://<IP_ADDRESS>:34899/7ETFkDQwO_Q=/
[   +2 ms] executing: /Users/vgts/Library/Android/sdk/platform-tools/adb -s emulator-5554 forward tcp:0 tcp:34899
[  +34 ms] 52673
[        ] Forwarded host port 52673 to device port 34899 for Observatory
[  +11 ms] Caching compiled dill
[ +295 ms] Connecting to service protocol: http://<IP_ADDRESS>:52673/7ETFkDQwO_Q=/
[ +659 ms] Launching a Dart Developer Service (DDS) instance at http://<IP_ADDRESS>:0, connecting to VM service at
http://<IP_ADDRESS>:52673/7ETFkDQwO_Q=/.
[ +288 ms] DDS is listening at http://<IP_ADDRESS>:52682/LB1yIN6BQhk=/.
[ +103 ms] Successfully connected to service protocol: http://<IP_ADDRESS>:52673/7ETFkDQwO_Q=/
[ +173 ms] DevFS: Creating new filesystem on the device (null)
[  +75 ms] DevFS: Created new filesystem on the device (file:///data/user/0/io.flutter.plugins.shareexample/code_cache/exampleWMUXHN/example/)
[   +4 ms] Updating assets
[ +214 ms] Syncing files to device sdk gphone x86...
[   +3 ms] <- reset
[        ] Compiling dart to kernel with 0 updated files
[        ] Processing bundle.
[   +1 ms] <- recompile package:share_example/main.dart 260be2e5-1266-4797-b78b-e46ac513b004
[        ] <- 260be2e5-1266-4797-b78b-e46ac513b004
[   +3 ms] Bundle processing done.
[ +513 ms] Updating files.
[        ] DevFS: Sync finished
[   +2 ms] Syncing files to device sdk gphone x86... (completed in 523ms)
[        ] Synced 0.0MB.
[   +4 ms] <- accept
[   +5 ms] Connected to _flutterView/0xf52865e0.
[   +5 ms] Flutter run key commands.
[   +2 ms] r Hot reload. 🔥🔥🔥
[   +1 ms] R Hot restart.
[        ] h List all available interactive commands.
[        ] d Detach (terminate "flutter run" but leave application running).
[        ] c Clear the screen
[        ] q Quit (terminate the application on the device).
[        ] 💪 Running with sound null safety 💪
[   +1 ms] An Observatory debugger and profiler on sdk gphone x86 is available at: http://<IP_ADDRESS>:52682/LB1yIN6BQhk=/
[+2073 ms] The Flutter DevTools debugger and profiler on sdk gphone x86 is available at:
http://<IP_ADDRESS>:9100?uri=http://<IP_ADDRESS>:52682/LB1yIN6BQhk=/
[+3299 ms] I/AssistStructure(26783): Flattened final assist data: 532 bytes, containing 1 windows, 3 views
[+4850 ms] I/TextInputPlugin(26783): Composing region changed by the framework. Restarting the input method.
[  +13 ms] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[   +6 ms] W/IInputConnectionWrapper(26783): getSelectedText on inactive InputConnection
[   +3 ms] W/IInputConnectionWrapper(26783): getTextAfterCursor on inactive InputConnection
[   +6 ms] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[   +2 ms] W/IInputConnectionWrapper(26783): getSelectedText on inactive InputConnection
[   +3 ms] W/IInputConnectionWrapper(26783): getTextAfterCursor on inactive InputConnection
[  +30 ms] W/IInputConnectionWrapper(26783): beginBatchEdit on inactive InputConnection
[   +4 ms] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): endBatchEdit on inactive InputConnection
[   +5 ms] W/IInputConnectionWrapper(26783): beginBatchEdit on inactive InputConnection
[   +2 ms] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[   +1 ms] W/IInputConnectionWrapper(26783): endBatchEdit on inactive InputConnection
[ +113 ms] I/TextInputPlugin(26783): Composing region changed by the framework. Restarting the input method.
[        ] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[   +2 ms] W/IInputConnectionWrapper(26783): getSelectedText on inactive InputConnection
[   +7 ms] W/IInputConnectionWrapper(26783): getTextAfterCursor on inactive InputConnection
[  +24 ms] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): getSelectedText on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): getTextAfterCursor on inactive InputConnection
[  +34 ms] W/IInputConnectionWrapper(26783): beginBatchEdit on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): endBatchEdit on inactive InputConnection
[ +210 ms] I/TextInputPlugin(26783): Composing region changed by the framework. Restarting the input method.
[   +3 ms] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[   +3 ms] W/IInputConnectionWrapper(26783): getSelectedText on inactive InputConnection
[  +13 ms] W/IInputConnectionWrapper(26783): getTextAfterCursor on inactive InputConnection
[   +1 ms] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): getSelectedText on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): getTextAfterCursor on inactive InputConnection
[  +51 ms] W/IInputConnectionWrapper(26783): beginBatchEdit on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[   +2 ms] W/IInputConnectionWrapper(26783): endBatchEdit on inactive InputConnection
[   +7 ms] W/IInputConnectionWrapper(26783): beginBatchEdit on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[  +19 ms] W/IInputConnectionWrapper(26783): endBatchEdit on inactive InputConnection
[  +81 ms] I/TextInputPlugin(26783): Composing region changed by the framework. Restarting the input method.
[   +2 ms] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[   +3 ms] W/IInputConnectionWrapper(26783): getSelectedText on inactive InputConnection
[   +9 ms] W/IInputConnectionWrapper(26783): getTextAfterCursor on inactive InputConnection
[+1078 ms] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[   +7 ms] I/AssistStructure(26783): Flattened final assist data: 524 bytes, containing 1 windows, 3 views
[        ] W/IInputConnectionWrapper(26783): getSelectedText on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): getTextAfterCursor on inactive InputConnection
[ +723 ms] I/TextInputPlugin(26783): Composing region changed by the framework. Restarting the input method.
[   +8 ms] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[   +2 ms] W/IInputConnectionWrapper(26783): getSelectedText on inactive InputConnection
[   +3 ms] W/IInputConnectionWrapper(26783): getTextAfterCursor on inactive InputConnection
[   +3 ms] W/IInputConnectionWrapper(26783): beginBatchEdit on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[   +9 ms] W/IInputConnectionWrapper(26783): endBatchEdit on inactive InputConnection
[ +173 ms] I/TextInputPlugin(26783): Composing region changed by the framework. Restarting the input method.
[  +12 ms] W/IInputConnectionWrapper(26783): getTextAfterCursor on inactive InputConnection
[   +3 ms] W/IInputConnectionWrapper(26783): beginBatchEdit on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): endBatchEdit on inactive InputConnection
[  +12 ms] W/IInputConnectionWrapper(26783): setComposingRegion on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): getSelectedText on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): getTextAfterCursor on inactive InputConnection
[ +313 ms] I/TextInputPlugin(26783): Composing region changed by the framework. Restarting the input method.
[   +6 ms] W/IInputConnectionWrapper(26783): getSelectedText on inactive InputConnection
[   +6 ms] W/IInputConnectionWrapper(26783): getTextAfterCursor on inactive InputConnection
[  +11 ms] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[   +4 ms] W/IInputConnectionWrapper(26783): getSelectedText on inactive InputConnection
[  +14 ms] W/IInputConnectionWrapper(26783): getTextAfterCursor on inactive InputConnection
[  +31 ms] W/IInputConnectionWrapper(26783): beginBatchEdit on inactive InputConnection
[   +2 ms] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[   +2 ms] W/IInputConnectionWrapper(26783): endBatchEdit on inactive InputConnection
[+1244 ms] I/TextInputPlugin(26783): Composing region changed by the framework. Restarting the input method.
[  +49 ms] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[  +13 ms] W/IInputConnectionWrapper(26783): getSelectedText on inactive InputConnection
[  +15 ms] W/IInputConnectionWrapper(26783): getTextAfterCursor on inactive InputConnection
[ +195 ms] W/IInputConnectionWrapper(26783): beginBatchEdit on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[  +13 ms] W/IInputConnectionWrapper(26783): endBatchEdit on inactive InputConnection
[+1079 ms] I/TextInputPlugin(26783): Composing region changed by the framework. Restarting the input method.
[  +13 ms] W/ListenableEditingState(26783): a listener was added to EditingState while a batch edit was in progress
[  +89 ms] W/IInputConnectionWrapper(26783): endBatchEdit on inactive InputConnection
[  +76 ms] W/IInputConnectionWrapper(26783): setComposingRegion on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[   +3 ms] W/IInputConnectionWrapper(26783): getSelectedText on inactive InputConnection
[  +20 ms] W/IInputConnectionWrapper(26783): getTextAfterCursor on inactive InputConnection
[  +88 ms] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): getSelectedText on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): getTextAfterCursor on inactive InputConnection
[  +90 ms] W/IInputConnectionWrapper(26783): beginBatchEdit on inactive InputConnection
[        ] W/IInputConnectionWrapper(26783): getTextBeforeCursor on inactive InputConnection
[  +19 ms] W/IInputConnectionWrapper(26783): endBatchEdit on inactive InputConnection
[+8172 ms] I/System.out(26783): onReceuve
[   +2 ms] I/System.out(26783): null
[ +254 ms] I/flutter (26783): ShareResultStatus.success
[        ] I/flutter (26783): null

Flutter Doctor
[✓] Flutter (Channel stable, 3.0.2, on macOS 12.2.1 21D62 darwin-x64, locale en-IN)
    • Flutter version 3.0.2 at /Users/vgts/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision cd41fdd495 (11 days ago), 2022-06-08 09:52:13 -0700
    • Engine revision f15f824b57
    • Dart version 2.17.3
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/vgts/Library/Android/sdk
    • Platform android-31, build-tools 30.0.3
    • ANDROID_HOME = /Users/vgts/Library/Android/sdk
    • ANDROID_SDK_ROOT = /Users/vgts/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)

[✓] VS Code (version 1.68.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.42.0

[✓] Connected device (3 available)
    • sdk gphone x86 (mobile) • emulator-5554 • android-x86    • Android 11 (API 30) (emulator)
    • macOS (desktop)         • macos         • darwin-x64     • macOS 12.2.1 21D62 darwin-x64
    • Chrome (web)            • chrome        • web-javascript • Google Chrome 102.0.5005.115

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

having the same issue with the latest package version. @santhoshvgts 4.0.4 of share_plus is working properly for me, but the current one isnt

Hi there,
are you really seeing ShareResult.raw == null?
The definition of the raw property is as follows:
final String raw;

The dart null safety guarantees that the raw property cannot be null.
Please explain your issue a bit clearer :)

@Coronon
https://github.com/fluttercommunity/plus_plugins/pull/800#issue-1175203282
shareWithresult fallback to share if the result is null

I am currently very short on time but will probably find some at the end of the month. When I last tried this I wasn’t able to reproduce this. Would you guys mind sharing a sample project for me to be on the same page? I am only able to test with the android emulator as I am not in possession of a real android device.

I had the same problem when running on Android 11, but Android 10 was normal

print(result.raw == "null");//true
its not null its string "null"

@Coronon
intent.getParcelableExtra<ComponentName>(Intent.EXTRA_CHOSEN_COMPONENT)
returns null

I have the same problem in version 4.4.0
final res = await Share.shareWithResult('some text',subject: title);
print(res.status);
print(res.raw);

@aakash-pamnani Thanks for your hint. Sadly, my PC broke and I was unable to work on this with my old Macbook. I expect to be able to look into the issue this weekend. As I don’t have an android device the hint that the new Android version might have something to do with it is greatly appreciated :)

@Coronon PendingIntent.FLAG_IMMUTABLE is the problem, changing it to PendingIntent.FLAG_MUTABLE returns the package name of the app clicked.
Is it ok using PendingIntent.FLAG_MUTABLE then i wil create a PR.

@aakash-pamnani If I remember correctly, there was a problem with the MUTABLE option. Something else in the code broke back then - I'll have to look into the old PRs. What's interesting is that I was not able to find anything in the change logs between Android v10 and v11 that would hint at any change in behaviour...

Finally got around to look into this and was able to reproduce it - now looking into a fix.

Okay, so I finally got a fix working that resolves the issue and cleans up the little callback-hell while still using FLAG_IMMUTABLE to ensure Intent integrity.
It is really late at night for me, so I'll clean up my changes tomorrow to then submit a PR :)
Sorry again for the huge delay, I was sadly really busy :/

As I just submitted my PR, I would love for everyone to try out the changes to see if they fix the issue outside my simulator.
As always, I provide share_plus_example as a pre-setup example project for this PR.
You may also try out this PR in your own projects using these dependency overrides in your pubspec.yml:
dependency_overrides:
  share_plus:
    git:
      url: https://github.com/Coronon/plus_plugins
      ref: eee78eafc4324509470cfdfb6b872f443706b5a0
      path: packages/share_plus/share_plus
  share_plus_platform_interface:
    git:
      url: https://github.com/Coronon/plus_plugins
      ref: eee78eafc4324509470cfdfb6b872f443706b5a0
      path: packages/share_plus/share_plus_platform_interface

Its working @Coronon


focus till StopIteration

#4816
I think the focus has the significance till it stops iterating between widgets on pressing tab and shift+tab.
The  _get_focus_next method returning none for current is self which is not good according to me. So the method should return none only at current is StopIteration.
If this is true than this method will not be required to make public as well.
Please tell if any other changes needed as well.

The code is correct the way it currently is. Focus cycling should stop either when we hit the widget again, because otherwise we'll keep walking focus_next/previous in an infinite loop or if it's StopIteration, as documented.
I also don't understand how this will affect having to make the method public. That should be required either way.


Pull requests here won’t count toward Hacktoberfest.

Hi there,
Thank you for your interest in Hacktoberfest and in helping others make their first contributions to open source.
While we agree that it's important to help others, this repository does not do this in a way that is in line with the Hacktoberfest values. Please read the part that talks about high-quality contributions to understand why we are reaching out and taking action. Due to this, we've added this repository to the list of excluded repositories which means pull requests here will not count toward Hacktoberfest 2020.
This is not a DigitalOcean decision, it's one that is inspired by the community of maintainers and contributors who all agree that quality is more important than quantity when it comes to engagement in the Open Source community. The values remind us to shift the focus from contributions to repositories that encourage folks to quickly create and gain a pull request to contributions that will help people level-up their skills and contribute to open-source projects that are in need of help.
If you feel that this repository is an effective learning resource, we encourage you to keep running it since a core part of the aim for Hacktoberfest is to encourage new folks to get involved with open-source.
However, if you are interested in having contributions to this repo count toward Hacktoberfest we encourage you to take a look at this list of Hacktoberfest issues for inspiration and make the necessary changes to focus on enabling people to make meaningful contributions to open source projects.
If you have any questions about this or participating in Hacktoberfest, please contact our team via email<EMAIL_ADDRESS>or join our community Discord server.
Happy Hacking,
The Hacktoberfest Team
Hacktoberfest is presented by DigitalOcean, Intel and DEV.

sad  😥


relevance sort tag added

Fixes #679 .
Changes proposed in this PR:

relevance sort tag added

The issue on aqua is not a prio now, so this will not be merged for some time now

Noticed that implicit sorting  which closes sorting by _score was merged, so I thought the problem is resolved. Just after that I saw your comment. I'll leave it as a draft until stable aqua release.

made obsolete by #837 which includes this change too


Port to ROS 2

It's a heavy refactor of the original code following the proposal in #42.
This is a work-in-progress, but opening for visibility and early feedback.
Some things still to do:

Add feedback publisher + API to interactive marker client.
Add liveliness check between server and client.
Port Python code
Revisit some TODOs I left in the code
More tests

Before polishing this, I plan to get it working with the RVIz display and write a standalone node showing how we can bridge with ROS 1.
Resolves #42

It doesn't seem we need to use liveliness to detect server disconnects, instead we rely on the service client API service_is_ready().

Linux
Linux-aarch64
macOS
Windows

Attempt to resolve various compiler warnings on macOS and Windows:

Linux
Linux-aarch64
macOS
Windows

I think this is pretty much ready for review, while I debug the Windows warnings and try to figure out why Clang and GCC disagree on what type something is.

I think I've worked out all the issues with the Windows build :crossed_fingers:

Linux
Linux-aarch64
macOS
Windows

I was so close... but an expected test error message is being picked up as a MSBuild warning :disappointed:

The latest MSBuild warning is a false positive; an instance of https://github.com/ros2/ci/issues/316.

Windows:


Add Protobuf v23.1

Add protobuf v23.1.
This also adds upb 0.0.0-20230516-61a97ef https://github.com/protocolbuffers/upb/commit/61a97efa24a5ce01fb8cc73c9d1e6e7060f8ea98 which cyclic depends with protobuf.

Thank you very much for working on this, it will unblock a migration I had planned for a while now.
Looks like upb is missing a patch to bring in the module file.

@fmeum There seems to be something wrong with the test:
cd modules/upb/0.0.0-20230516-61a97ef
mkdir test && cd test && git init
git apply ../patches/module_dot_bazel.patch ../patches/utf8_range.patch
diff MODULE.bazel ../MODULE.bazel

doesn't report any changes between the MODULE.bazel checked in and the one created with the patches.

Marking as draft as I don't understand the failures in the tests. Any help appreciated.

Looks like this variable (https://github.com/protocolbuffers/upb/blob/e7430e66d6e51def2a88f0b66fdab62b0d9492c1/upbc/bootstrap_compiler.bzl#L23) somehow ends up pointing to external/com_google_protobuf rather than external/protobuf~.... Not sure why though.

Looks like this variable (https://github.com/protocolbuffers/upb/blob/e7430e66d6e51def2a88f0b66fdab62b0d9492c1/upbc/bootstrap_compiler.bzl#L23) somehow ends up pointing to external/com_google_protobuf rather than external/protobuf~.... Not sure why though.

@fmeum Thanks, this was the hint I needed! It was hardcoded in the used version so I backported this line from the latest one.


Failed to start the concentrator

Hi everyone,
I am trying to setup a new ic880a (SPI version) gateway using a raspberry pi 3 and the latest version of the raspbian https://www.raspberrypi.org/downloads/raspbian/ (lite version). After downloading the lora_gateway and packet forwarder and compiling them I get the following error (see picture below). Do you have any idea what might be going wrong?
Thank you in advance.

I'm going to close this issue as it is not related to the LoRa Server codebase. Please use https://forum.loraserver.io for support questions :-) Hint: your question might already been answered: https://forum.loraserver.io/t/lora-packet-forwarder-doesnt-start/231.

Hi @sokolbiba,
before running the packet forwarder you have to bring the iC880A Concentrator in an initial state (reset).
I made this by running  shell script running prior executing the packet forwarder.
#!/bin/bash
echo "17" > /sys/class/gpio/export
echo "out" > /sys/class/gpio/gpio17/direction
echo "1" > /sys/class/gpio/gpio17/value
sleep 5
echo "0" > /sys/class/gpio/gpio17/value
sleep 1
echo "0" > /sys/class/gpio/gpio17/value
After that the packet forwarder should run without any problems. You can find some more information about preparing the reset pin control in the iC880A doc under https://wireless-solutions.de/images/stories/downloads/Radio Modules/iC880A/iC880A-SPI_QuickStartGuide.pdf starting at the end of page 9.

Hi @maximilianschwab
I tried waht you suggested me and I still get the same error. I do not understand why but while using the ttn packetforwarder it is performing very well.

@maximilianschwab  I was misconfiguring the reset pin. Thank you for your help :)


mcumgr: Fix build when CONFIG_THREAD_MONITOR=n

When CONFIG_THREAD_MONITOR is disabled the function
os_mgmt_impl_task_info will not be compiled. But we are still using it
from os_mgmt.c
Add an ifdef to resolve this missing reference error.
Signed-off-by: Sebastian Bøe<EMAIL_ADDRESS>

I am not familiar with this code.
It needs to be reviewed/confirmed that it makes sense to not invoke this function when THREAD_MONITOR is disabled.
I have not checked if this bug exists in more instances either.
Perhaps there are more places we need to ifdef on THREAD_MONITOR.

One small request, If you do not mind: can you add commit that would modify the https://github.com/zephyrproject-rtos/zephyr/blob/main/samples/subsys/mgmt/mcumgr/smp_svr/prj.conf smp_svr sample configuration to enable the taskstat by default?

@de-nordic: Done


Question regarding OS

Hey,
Is it also possible to implement windows servers?

Unfortunately, this is not possible.

Not possible as docker shares the host kernel.


Fix "set username" screen

Pull Request Description

Fixes the "set username" screen erroring because the backend defaults to the local backend, which does not support setting username.
Also fixes an error when trying to list a directory for a user that cannot access the cloud dashboard

Important Notes
None
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

1 min, there's a bug when logging in after a refresh

Note: This branch has been merged into #6668. This PR should be closed if that PR is merged first.


Keyboard controls?

It seems a pointer device is needed to use the microui interfaces.
I'd be interested in keyboard control, I suppose this would also mean tab order would be useful.
Thanks for all your work!

This isn't something I plan to support in the base library at the moment, as you can imagine given the goals of the project the addition of features is typically avoided. I did experiment a little with tab-moves-to-next-control in the past but for what it added in code it didn't yield results I was happy with. Anything more complex than this (eg, being able to use arrow keys to navigate between buttons/sliders, enter to select) would be a huge change in both lines of code and complexity.
This being said microui should be able to act as a foundation for these kinds of additions, eg. in projects I use it in I typically use it as a base to many additional controls and features specific to the application. Keyboard controls would be one of these application-specific features.

Hey, I understand this is not something to be part of the library, since it's good it's really tiny and easy to understand, but I wanted to use it in a game.
So, I understand that for some rustic way of using arrow keys/d-pad to move a cursor on the "cells" (comparing a bunch of rows with a table), I would need to know the position/dimensions of these cells. But I think that these only exist fleetingly, between the BeginWindow and EndWindow, with things getting popped out of the stack - so a new window on the same frame would "overwrite" the stacked layouts and there goes my positional information.
In this way, I think the only possible way would be store that the player had intention to move cursor right (a boolean key_right or something) and then when it's the control in the position of where the cursor is now, mark somewhere this, and then on layout next advance the cursor.
Are there other simpler strategie? Or is there a way to recover the position of controls on screen I am not seeing?


Fix of issues #94 and #165

The error can be reproduced easily by turning off the flycheck-mode.

Pull Request Test Coverage Report for Build 293

1 of 2 (50.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 69.331%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cmake-ide.el
1
2
50.0%

Totals

Change from base Build 292:
-0.1%

Covered Lines:
373

Relevant Lines:
538

💛  - Coveralls


Unsafe error handling in Orchestrator

Original Issue
Surfaced from @informalsystems audit of Althea Gravity Bridge at commit 19a4cfe
severity: High
type: Implementation bug
difficulty: Intermediate
Involved artifacts

Orchestrator

Description
The codebase has generous use (hundreds) of panic-causing statements: unwrap(), panic!(), assert, assert_eq, assert_ne and expect. In some cases they are safe, but we have identified many cases for which it is unclear whether the asserted condition is always true, or can be violated due to e.g. network errors or misbehavior/bugs in other Gravity Bridge components.
Below we provide some examples of those statements, characterized into three categories:
Assertions that depend on other Gravity Bridge components
These assertions may be fine as soon as the other Gravity components behave correctly. Checking whether this is indeed true is an extremely complex and time-consuming process. Also, even if those components do behave correctly, there is always a possibility of some bug, or a malicious action.
orchestrator/gravity_utils/src/types/valsets.rs#L151
       for member in self.members.iter() {
           if let Some(eth_address) = member.eth_address {
               if let Some(sig) = signatures_hashmap.get(&eth_address) {
                   assert_eq!(sig.get_eth_address(), eth_address);
                   assert!(sig.get_signature().is_valid());

This is probably safe as the valset updates are coming from trusted validators. Now the question is:

what if due to some bug an invalid signature is included?
what if a malicious validator intentionally includes a wrong signature? This will lead to all other Orchestrators stopping, and all other validators being slashed.

orchestrator/gravity_utils/src/types/valsets.rs#L167

       // the go code verifies signatures, if we ever see this it means
       // that something has gone horribly wrong with our parsing or ordering
       // in the orchestrator, therefore we panic.
       panic!(
           "Found invalid signature for {} how did this get here?",
           sig.get_eth_address()
       )

Same as above.

orchestrator/relayer/src/find_latest_valset.rs#L93

       if cosmos_valset != *ethereum_valset {
           // if this is not true then we have a logic error on the Cosmos chain
           // or with our Ethereum search
           assert_eq!(cosmos_valset.nonce, ethereum_valset.nonce);

If, as the comment says, there is indeed some logic error, is this the valid reason for all Orchestrators stopping and validators being slashed?

orchestrator/relayer/src/valset_relaying.rs#L49-53

       let valset = get_valset(grpc_client, latest_nonce).await;
       if let Ok(Some(valset)) = valset {
           assert_eq!(valset.nonce, latest_nonce);

This is probably safe, because the rpc calls ask for the specific nonce; but what if there is a bug in the RPC call?

orchestrator/ethereum_gravity/src/utils.rs#L144

orchestrator/ethereum_gravity/src/utils.rs#L168

orchestrator/ethereum_gravity/src/utils.rs#L119

orchestrator/ethereum_gravity/src/utils.rs#L94

       // the go represents all nonces as u64, there's no
       // reason they should ever overflow without a user
       // submitting millions or tens of millions of dollars
       // worth of transactions. But we properly check and
       // handle that case here.
       let real_num = Uint256::from_bytes_be(&val);
       Ok(downcast_uint256(real_num).expect("Valset nonce overflow! Bridge Halt!"))

This depends on the correct behavior of the Solidity contract, and on the nonces never overflowing 64 bits. While unlikely, both conditions still could be violated.
Assertions in the initialization phases or in the client code
ignores CosmosGRPCError which can happen because of reasons not related to balance or requesting batch.

orchestrator/gbt/src/client/cosmos_to_eth.rs#L59

orchestrator/gbt/src/client/cosmos_to_eth.rs#L109

ignores Web3Error which can happen without incorrect gravity address or ERC20 queries.

orchestrator/gbt/src/client/eth_to_cosmos.rs#L25

orchestrator/gbt/src/client/eth_to_cosmos.rs#L32

orchestrator/gbt/src/client/eth_to_cosmos.rs#L39

There are other expects in the code. But we do not mention them as they are at the initialization phase or due to user specific errors.

Failed to create directory or write to file.

Failed to load cosmos or eth keys.

These errors probably won't lead to severe consequences, such as validator slashing. But they will definitely occur many times, and the error will be communicated to the user via panicing and printing a stack trace. This is not the best way to communicate errors to the user, and should be improved.
Vacuously true assertions
These assertions are guaranteed to be safe due to the code structure, and can thus be removed. Keeping them in the code makes code inspection exceptionally difficult, as we spend time on false positives. Minimizing the usage of them would be helpful for future code inspections. Here are a couple of examples:

orchestrator/gravity_utils/src/types/batches.rs#L59-L60

safe because of the Vecs are populated in a same length loop.

orchestrator/ethereum_gravity/src/valset_update.rs#L26

safe as the check is done before reaching this call.

Problem Scenarios
As there is a very large number (hundreds) of panic-resulting statements, it is close to impossible to enumerate all possible problem scenarios. Here are a few example ones:

Due to a bug in other Gravity Bridge component, an input comes to the Orchestrator that triggers one of the panic-statements;

The input triggering a panic is maliciously crafted (this may happen even from a validator side);

A network error occurs, which propagates to one of the panic statements.

The effect depends on in the part of the Orchestrator in which the panic occurs. A panic in the initialization code will probably result only in the user inconvenience and annoyance. If the panic occurs a long time after the Orchestrator has been started, it will stop, and this may lead to validators being slashed without malicious actions from their part.
It should be noted that Orchestrator is a single binary responsible for all kinds of operations: a panic triggered during any of those (even seemingly unimportant) will cause the whole processing to stop, with the aforementioned severe consequences.
Recommendation
Short term
We recommend different course of action depending of the panic category:

Assertions that depend on other Gravity Bridge components:

Carefully inspect the code in the other components on which the assertion depends;

Move error-handling code in the Orchestrator to the input-receiving boundary;

For the cases when this is not possible, propagate the errors using Results to the top level;

At the top level, implement a uniform error handling with alerts issued to validators;

Do not stop processing of other legitimate, non-erroneous requests.

Assertions in the initialization phases or in the client code:

Move error-handling code to the input-receiving boundary or propagate errors to the top level;

At the top level, implement a uniform error handling with meaningful error messages issued to the user.

Vacuously true assertions:

Inspect the code, and if the assertion proves to be vacuously true, remove it.

Long term
Refactor the Orchestrator into independent binaries each responsible for different operation kind. Ensure that all binaries responsible for possible validator slashing adhere to the highest possible security standards; they should not stop under any circumstances, and should employ defensive programming techniques against possible failures in other components.

Update: Refactored error handling in the relayer crate and requested feedback. Also did some general code cleanup as I went.

Crates

[x] relayer
[ ] orchestrator
[ ] gravity_utils
[ ] register_delegate_keys
[ ] ethereum_gravity
[ ] cosmos_gravity

These wait_for_next_block() calls return a Result, but instead of handling the error they will just panic. Since it only runs at startup, we don't really care about it crashing, but should we at least provide some feedback about the error in the event that it occurs?


Enhancement/Proposal: Entities of all datasources within a project cannot be easily exported

Currently you need to repeat the command per one datasource, so you end like:
export entities:products entities:categories entities:... ...
There should be a more efficient and comfortable way to export all entities and transfer them with the complete content to another stage (e.g. export from PROD and import to DEV).
There are several possible ways we could achieve this:

use the syntax as it exists for other elements like
export entities:ALL
and extend the current existing export entities:<content2_id> logic.

implement a more general cmd function "execute_script" which executes a Script/Class that must exist inside the current server as FSM/project script and do a subprocess call for generating the cmd arguments of the "export" call automatically

or by a custom command like "export_all_entities"

the above logics could also use an e.g. configurable regular expression, so you can configure by the uid/uid-path of the content2-element if it should be exported or not.

Hi :)
Thank you for your proposal - I'm afraid that the export of all entities is something that we don't want to officially support or encourage with the external sync feature. That's the reason why export entities:ALL is not implemented by us on purpose.
Regards,
Hannes


Replace api_password in Camera.Push

Description:
Remove api_password, and changes to using access_token/user provided token accordingly to https://github.com/home-assistant/home-assistant/issues/15376#issuecomment-417373618
This is a breaking change for most users pushing camera images through cURL scripts
Related issue (if applicable): #15376
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#6130
Example entry for configuration.yaml (if applicable):
camera:
  - platform: push
    name: cam1
    timeout: 10
    cache: 5
    token: 12345678

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

https://github.com/home-assistant/home-assistant/blob/a5d95dfbdcf0d9ca3da93f44e2cbb5d162ac3272/tests/components/http/test_auth.py#L158-L163
https://github.com/home-assistant/home-assistant/blob/a5d95dfbdcf0d9ca3da93f44e2cbb5d162ac3272/tests/components/conftest.py#L43-L44

tests added 👍

Maybe we should wait until the long time tokens are implemented and we can switch to this common version. Otherwise it going to a edge case for handling auth.

I'm all in favor of using long time tokens.
But I was under the impression from https://github.com/home-assistant/home-assistant/issues/15376#issuecomment-405109636 that long time tokens would not become an option and that the current api_password would be dropped soon.

@pvizeli we don't want to use long lived access tokens for this because an access token would allow full access. For these one off access, just allowing an auth token to be hard coded is fine.

This is ok to merge once the token has been changed in the schema to be required.

I see this PR as a stop-gap, what we need are long lived access tokens that are limited to given API's
The preferred authentication and authorisation method should be that of HA, and that is why I keep the option of uploading the camera images using HA auth.

Putting this in the 0.78 release as example how to do auth both ways.
As far as I can see, this is not a breaking change as people can still authenticate with API password via legacy API password provider, or even use new auth.

It you don't remove legacy_api that is true :)
I was afraid that it was going out in 0.78 already...

Oh no, that beast will probably be around for a looooooooong time. Eventually it will become opt-in instead of opt-out.

But first we need long lived access tokens, which will come this release.


fix: ignore pod not found errors when removing kube specs

Cause: The module uses the podman kube play --done command to remove
the pod specified by the kube spec, but does not check if the pod has
already been removed.  That is, it is not idempotent.  The command
gives an error if the pod is not found.  This only happens with
podman 4.4.1 on EL8.8 and EL9.2.
Consequence: The podman role gives an error that the pod specified
by the kube spec cannot be found when removing.
Fix: The role ignores the 'pod not found' error when removing
a kube spec.
Result: The role does not give an error when removing a kube
spec.
NOTE: This has been fixed in the containers.podman.podman_play
module upstream but has not yet been released.
https://github.com/containers/ansible-podman-collections/pull/863/files#diff-6672fb7f52e2bec3450c2dd7ed9a4385accd9bab8429ea6eecf4d56447f5a1b8R304
Signed-off-by: Rich Megginson<EMAIL_ADDRESS>

[citest]


ADD

ADD

@aquilardo Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

@aquilardo You might miss my previous comment. Please react.

@aquilardo I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


Remove test for local version matching

There is only one known use case that you would care that the local
version is different than the pkg_resource distribution version. This
would only occur if you were in the pylmod directory and using python
from there. In this case you would get the globally installed version
instead of the checked out version after this commit.
On the other hand, readthedocs.org does exactly this (and gets the
wrong version), and it is much more likely that we would forget to
update the version in multiple places (i.e. docs/conf.py and setup.py)
so we have chosen to accept the narrower error case.

I have verified this fixes the rtfd problem: http://pylmod.readthedocs.org/en/feature-cg-apidoc-debug/

Coverage remained the same at 100.0% when pulling 44d7030e506c16100ffde6be435f16a4a0c02cef on feature/remove_local_version_check into f1d6beb04791bb832f7deceb838657abd0fb55bd on master.

works for me


[VIZ] add plotly imshow node

https://plotly.com/python/imshow/
For displaying images in the CTRL panel and as nodes
Related:
https://github.com/flojoy-io/studio/issues/341
https://github.com/flojoy-io/studio/issues/340
https://github.com/flojoy-io/nodes/issues/18
https://github.com/flojoy-io/studio/pull/249

(cc: @trbritt @dstrande)


openpilot offroad apk - It does not work

Install the application today on /openpilot/apk/ai.comma.plus.offroad.apk
It does not work. An error appears and it closes.
Why? Thanks.

It is not designed to be installed on normal Android, only NEOS.


Revert addition of should_full_refresh macro

Reverting this file added in https://github.com/community-tech-alliance/dbt-cta/pull/270/files. It forces dbt to run full refresh if a table does not contain the field _airbyte_ab_id. Rude!

YOLO-merging to fix a bug affecting syncs in prod.


Proposed additions

Per a Discord conversation instead of pulling my forms solution out of its project I refactored the project to use cerebral-module-forms because I liked its overall design more. However, the module is missing some features I need so here is an attempt at adding them.
I am aware that some or all of this may not make it or may need a second revision. Hopefully this PR will be a spring board for discussions. Sorry all of theses features are jammed into one PR, I have to go live with my project by the end of the week so I hacked together what I needed all at once :smile: That said, I tried my best to make one commit per feature.
@christianalfoni Let me know if you are not ready for PRs like this. I don't want to step on your new module too much!
What's in the PR
Bug Fixes:

equalsField was missing a .value

New Features

Added a "Checkout" demo. It is based on one of the forms that inspired this PR.

Created an HOC. The checkout demo uses the HOC.

All the field's state becomes props of the wrapped component.

Added array field values to support multiple value inputs like <select multiple>

For an example see "How did you hear about us? (test select multiple)" of the Checkout demo

Added a defaultValue state key and provided a reset action and reset signal.

For an example see the reset buttons on all the demos.

Added a form validate action and signal.

For an example see the validate buttons on all the demos. Particularly the checkout demo.

Changed isTouched to only set for on blur and forced validations. We talked a little about this on Discord. I think it improves the UX.

Actually, I added a touched input key to the fieldChanged signal and then made the react parts do the right thing. There is probably a better solution.
For an example see any of the fields on all the demos. Particularly the checkout demo.

Added dependent fields for validation.

That is, when a field changes it causes a set of other fields in the form to re-validate.
Currently you can only specify what other fields to re-validate when the current field changes. You can not configure a field to re-validate when a one of a list of other fields change.
You can use relative paths, i.e., ., .., etc, or absolute paths to the dependent fields.
For an example see, "Email", "Verify Email", and "Verify Email, again..." of the checkout demo.

New Features I Wanted To Get To But Ran Out Of Time, For Now...

Custom errors

Enable validators to returns error codes rather then just true/false. Use an object to configure the validator in state so that the developer can specify an error string for each error code. For example, 'isEmail' might return: 'invalid', 'missingAt', 'missingHost', etc.

Form({
  email: {
    value: '',
    isRequired: true,
    validations: [{
      type: 'isEmail',
      errors: {
        invalid: 'Email is invalid',
        missingAt: 'Email is missing the required \'@\' sign',
        missingHost: 'Email s missing a host'
      }
    }
  }
})

i18n libraries could be used at this level.

Normalize functions.

A set of functions that take in the current value of field and then returns a new value. Right now I'm thinking they run before validation. This is mainly for formatting field values automatically, e.g., phone numbers, credit cards, etc. I think the function signature is something like function (value, previousValue, cursor, form, parameter). This could get somewhat complicated because the cursor position needs to be considered and updated appropriately too.

Updating the view based on form values. For example, show a picture of the credit card type as soon as it can be determined from the numbers entered. Change the label of the "CVV" field to "CID" for American Express, etc.

I don't think this requires any changes to the cerebral-module-forms. I just wanted the demo to include it so we have an example of how one could do it.
That said, in my uses cases the information needed to dynamically update/configure the view is also calculated by the relevant validators/normalizers. It could be nice to somehow let the validators/normalizers save its "meta" data to the state. Maybe validators/normalizers can return an object like:

{
  valid: true,
  meta: { /* ... */ }
}

and
{
   value: newValue,
   meta: { /* ... */ }
}

where the object at meta is stored in the field's state under a meta key. I want to avoid allowing the validators/normalizers to arbitrarily change a fields state because I think that is asking for trouble/abuse.

Update the README for the new features. I will wait to do that until it the various features are merged.

Figure out what the Cerebral style guide ended up being and apply it here.

Need to add tests.

Open Questions/Thoughts:

Should we be suggesting to use cerebral-module-forms as a page sub-module and let the form state be owned by the cerebral-module-forms instance. Would/could that make the signals easier to use? We would avoiding having to register all the custom validators for an entire application in one place. However, then some rules might be included more than once across various forms.

Should add/remove field/form be signals? Should we instead just offer helper functions and let custom signals change the form state. At minimum people should be using the Form() function. Adding and removing fields/forms requires a custom view anyways.

I really want to bring this in, though it would be nice to review it together maybe? Let me know when you have some spare time @abalmos. Would be cool to get it to a publishable version :)

@christianalfoni Let me see if I can find a few hours this week to finish this up. I have some notes that I need to review from when I used it in a project.

@abalmos After resetting the Form options.map will be null when trying to render a select. options is undefined after reset. See Select/index.js

@abalmos We need to check the reset.js I think.

Thanks for review @edgesoft ! I will wait for @abalmos final pull request before official release :)

These changes (including fixes for the comments left by @edgesoft, thanks @edgesoft!) are now in the branch misc-features. I'm too chicken to update the branch this PR is based on because I don't want to break my production app :smiley:
I didn't merge into master because I know I will have trouble being around to support the code for a few weeks. The branch also lacks updated documentation (although there is a complete demo form). I will let @christianalfoni decide if he just wants to pull the trigger and merge or wait for some PRs on that branch to add docs.

@abalmos can you aslo make a rebase on top of latest master?

@Guria the misc-features branch is this PR + a few commits rebased onto master

@abalmos ahh then we should open new pr instead of this one I suppose?

I am closing this PR to avoid further confusion. Please track the misc-features branch for these changes. Unfortunately I can't update this PR because the current master uses cerebral API too new for my production application.

@Guria I suppose we could. No semantic versioning here yet so I can just merge the branch into master when ready. The point of moving it into a branch on this repo was to enable some PRs on the feature branch from others in the meantime.

@abalmos @Guria @christianalfoni I'm using this in production now and It works great. No bugs so far. Could we pull misc-features into master branch or what is stopping us?

@edgesoft probably the only thing that is stopping it is me not yet writing documentation on the new stuff. There is a breaking change or two. For example,touched changed meaning slightly.
I'll get doing this on my to-do list


feat: Introduce boot-lib and http-lib modules

As described in #4028 and #4029 this PR introduces the boot-lib and http-lib modules. Specifically:

It breaks the cyclic dependency between connector-core and Junit by moving EdcHttpClientImpl into the http-lib modules and getFreePorts() to a utility method in the core util module.
Moves the InMemoryVault implementation to the boot-lib module so that it can be referenced without exposing visibility to core services
Starts to clean up dependencies on connector-core. These will be refined in subsequent PRs.

Linked Issue(s)
Closes #4029
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

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

Project coverage is 62.28%. Comparing base (7f20ba5) to head (0bf4621).
Report is 159 commits behind head on main.

Files
Patch %
Lines

...l/src/main/java/org/eclipse/edc/util/io/Ports.java
83.33%
1 Missing and 3 partials :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##               main    #4030      +/-   ##
============================================
- Coverage     71.74%   62.28%   -9.47%
- Complexity        0     4240    +4240
============================================
  Files           919      989      +70
  Lines         18457    20053    +1596
  Branches       1037     1126      +89
============================================
- Hits          13242    12490     -752
- Misses         4756     7136    +2380
+ Partials        459      427      -32

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


Security

Hey xoity.
Thank you for the pull request and your valuable support to the project!
-q I appreciate your idea of adding exit options and real-time monitoring features. However, I ran into some problems when trying to install the curses module required to use the interface. Terminal type Even though I tried my best to install it. But I encountered a bug in the installation process. This makes moving forward with the deployment challenging…
However, I still find the original idea very useful and would like to integrate real-time checking and the -q exit function into the project. I plan to use these features without relying on the curses module, which avoids installation complexity to provide the functionality you're looking for...
Thank you again for your feedback. I will continue to integrate these features and keep you posted on

``

hey xoity.
Thank you for the pull request and your valuable support to the project!
-q I appreciate your idea of adding exit options and real-time monitoring features. However, I ran into some problems when trying to install the curses module required to use the interface. Terminal type Even though I tried my best to install it. But I encountered a bug in the installation process. This makes moving forward with the deployment challenging…
However, I still find the original idea very useful and would like to integrate real-time checking and the -q exit function into the project. I plan to use these features without relying on the curses module, which avoids installation complexity to provide the functionality you're looking for...
Thank you again for your feedback. I will continue to integrate these features and keep you posted on

hey xoity.
Thank you for the pull request and your valuable support to the project!
-q I appreciate your idea of adding exit options and real-time monitoring features. However, I ran into some problems when trying to install the curses module required to use the interface. Terminal type Even though I tried my best to install it. But I encountered a bug in the installation process. This makes moving forward with the deployment challenging…
However, I still find the original idea very useful and would like to integrate real-time checking and the -q exit function into the project. I plan to use these features without relying on the curses module, which avoids installation complexity to provide the functionality you're looking for...
Right now, you can test the tool again with the changes I made. I added the real-time monitor, an interval for refreshing depending on how many seconds you want to wait between updates, and the ability to quit using Ctrl+C.
Thank you again for your feedback. I will continue to integrate these features and keep you posted on

hey tobias, i understand your concerns and validity of not having to use the cursors library, i will look into your changes and will continue to follow along.
if you don't mind i hope to still be a contributor to this project, as contribution is the driving factor to open source development.

Thanks for understanding my concerns, and I appreciate you looking into the changes. I agree, contribution is essential to the growth of open-source projects, and I’m glad to hear that you’d like to continue contributing.
I’ve also sent you an invitation to be a collaborator on the project. I’m definitely open to collaborating, and I’m sure we can work together to make the project even better.

Thanks for understanding my concerns, and I appreciate you looking into the changes. I agree, contribution is essential to the growth of open-source projects, and I’m glad to hear that you’d like to continue contributing.
I’ve also sent you an invitation to be a collaborator on the project. I’m definitely open to collaborating, and I’m sure we can work together to make the project even better.

sounds great, ill keep opening some pull requests but ill keep everything small scale, feel free to give any more concerns there or suggestions for the code in the review section.
again like i said i will keep everything small scale instead of big changes with +200 diffs lmao. excited to work with you and thanks for the collaborator invite.

Thanks for the update! That sounds like a good plan keeping things small scale will definitely help with easier reviews and faster iterations. I'll make sure to provide feedback in the review section as we go.


Wrong Word, Misleading - tutorials - Start a Relay Chain - /tutorials/v3/cumulus/start-relay

Feedback

We have included three set of chain spec files in this tutorial that you can use without modification for a local test network:

It seems like "three" should have been "the". Link to the paragraph: https://docs.substrate.io/tutorials/v3/cumulus/start-relay/#pre-configured-chain-spec-files

Looks like @NukeManDan will be merging this 🔜 👀  ! Thanks @Fahrrader for pointing this out 🙏🏻 .


Skip list for A770

The tests cases mentioned in #983 have been added to A770 skip list.
Fixes #1579.

Why do so many tests get skipped? Do we not want to try fixing them?

Some test cases are coming from #983, others from the default skip list.

Successful run: https://github.com/intel/intel-xpu-backend-for-triton/actions/runs/9862830436/job/27234267692
Pass rate: 96.75%


Semihosting stdio fds

Renumber the stdio file descriptors so that there is a better fit with POSIX.  OpenOCD behaves the same.
See discussion here #1515

/azp run

Btw, what C library are you using?

Btw, what C library are you using?

I'm using picolib.  Toolchain is built with https://github.com/ARM-software/LLVM-embedded-toolchain-for-Arm


Added support for the --retry-interval command line option.

Added support for the --retry-interval command line option.
It is intended as a broker exception retry interval and is specified as number of seconds.
By default, if there is an exception while communicating with the broker, celery-exporter exits with a stack trace.
It is not uncommon to temporarily lose connectivity to redis for a very short amount of time. With the default behavior, the
exporter will need a restart thus losing all accumulated metrics.
With the new --retry-interval options specified, one can specify and optional retry interval (i.e. 5 seconds) and
celery-exporter will restart the celery EventReceiver for that broker.
The default is 0, (i.e. do not retry) in order to keep compatibility (and expected behavior) with the current
celery-exporter.

Hi @danihodovic, I initially had a prototype with the interval hard coded to 5, but that may not be good for everyone. I've implemented it now with a --retry-interval cli option.
Keeping this as Draft. If this approach is acceptable to you, I'll update the README, add tests, then un-draft.
Thanks.

The PR looks good to me.
I haven't had this problem since I usually run the program in a container with a restart policy. How are you running the celery-exporter and where have you encountered this error?

Thanks!! I'm running in our OCP 4.10 cluster in OpenShift Dedicated, my deployment strategy also has the restartPolicy set to Always and celery-exporter does restart as expected, it's just that if there's a short hiccup with the network to our redis instance, the pod restart causes it to lose all previously collected metrics.

Makes sense :+1: You can undraft the PR and proceed

Hi @danihodovic, minor update to include doc and test update.  PR is un-drafted, Thanks!!

Rebase and I'll merge.


MINOR: AdminClient consumer group domain objects should have public constructors

These constructors should be public to allow users to write test cases using them. We follow a similar pattern for the other domain objects that we expose in AdminClient (e.g. TopicDescription).
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Tests pass locally. Going to go ahead and merge.


feature: optmize scrollbar style

Description
optmize scrollbar style both in light and dark mode.
here is the result:

This looks awesome @ohplz 🙏

This looks awesome @ohplz 🙏

This is my first time to contribute in a open source project, my pleasure!


first Japanese translation

Description of Issue (if Applicable)
The first Japanese translation.

 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.

Thank you Kifumi!


Store container network in etcd

Container network should be stored in etcd by openshift-sdn master and read by openshift-sdn minions from there.

Closed via #38


AttributeError: 'NoneType' object has no attribute 'items'

Hi,
when I run the code from ubuntu 20 python 3.6 I got this error
File "src/main.py", line 88, in
config_dict = recursive_dict_update(config_dict, alg_config)
File "src/main.py", line 56, in recursive_dict_update
for k, v in u.items():
AttributeError: 'NoneType' object has no attribute 'items'

me,too

Do you Solved it

Hi
I run the code on linex and it work but windows still have a lot of issues.
Best regards
Suleiman
On Dec 18, 2022, at 4:54 PM, 8uttonwoodRL @.***> wrote:

Do you Solved it
—
Reply to this email directly, view it on GitHubhttps://github.com/oxwhirl/pymarl/issues/129#issuecomment-1356680549, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AP6S2HJDNUFWNAUMUKP3H3DWN2RH3ANCNFSM5OMYAYVA.
You are receiving this because you authored the thread.Message ID: @.***>

Learn about the sys.argv command from this website: https://blog.csdn.net/Kim_Weir/article/details/103875186
You can think of argv as a list, the first element is the location of main.py, followed by the external parameters.
params = deepcopy(sys.argv)
This command receives parameters entered from the terminal, for example
python3 src/main.py --config=qmix --env-config=sc2 with env_args.map_name=2s3z
So, when you click the debug or run button directly in pycharm, there is only one element in the argv list, which is the location of main.py. So params is wrong at this time.
So the result of env_config = _get_config(params, "sc2", "envs") is also wrong.
So the input parameter "env_config" of config_dict = recursive_dict_update(config_dict, env_config) is also wrong.
So the recursive_dict_update function will report an error.
I changed it to the following form. This form needs to be changed in the corresponding position in the code when changing the environment, map, and algorithm.
env_config = _get_config(params, "sc2", "envs")
def _get_config(params, arg_name, subfolder):
config_name = arg_name
if config_name is not None:
with open(os.path.join(os.path.dirname(file), "config", subfolder, "{}.yaml".format(config_name)), "r") as f:
try:
config_dict = yaml.load(f)
except yaml.YAMLError as exc:
assert False, "{}.yaml error: {}".format(config_name, exc)
return config_dict


Use pipeline to fetch all jobs at once

In my testing this had a massive perfomance benefit for high-latency environments
with lots of cron jobs.
For my production environment with 1350 cron jobs, it took 287s to run Job.all - almost five minutes. By removing the unnecessary existence check and pipelining
the hgetall commands, this sped up to under a second.

@stormsilver wow, do you see any potential drawback?

Nope. We have been running this in production for 6 weeks with no problems.


feat(helm): make long listing default for helm list

This removes --long and adds --short,-q
The default listing is now the long listing, which matches the behavior
of all of the other listing commands.
Closes #1215

This change is

manually tested


Use Fasttext model to handle OOV words

Currently the gensim method does not support OOV words.
https://stackoverflow.com/questions/78540836/fasttext-pre-trained-model-is-not-producing-oov-word-vectors-when-using-gensim-d

https://fasttext.cc/docs/en/crawl-vectors.html

Fasttext does not compile, so we keep using gensim.
Download .bin vectors from: https://fasttext.cc/docs/en/crawl-vectors.html
Load it by following: https://radimrehurek.com/gensim/models/fasttext.html

Need to add a process to:

Download language vectors from: https://dl.fbaipublicfiles.com/fasttext/vectors-crawl/cc.en.300.bin.gz
Unpack the .gz and get the .bin (or maybe get it from another place, hugginface?)
Save it and delete the rest

We also need to test on cc.en.300.bin load_facebook_vectors("data/cc.en.300.bin"), as this does support OOV

We should also try the .bin from https://dl.fbaipublicfiles.com/fasttext/vectors-english/wiki-news-300d-1M-subword.bin.zip.

Maybe look for a huggingface repo that has all these files or do it ourselves?

But when we read "data/imageability/fasttext_embeddings.parquet" we get this for a:
word     score     emb_1     emb_2     emb_3     emb_4  ...   emb_295   emb_296   emb_297   emb_298   emb_299   emb_300
0            a  0.282421 -0.007921 -0.095293  0.031266  0.017734  ...  0.027889  0.014730  0.014651 -0.008444 -0.066989  0.025416

Using embedding_model = KeyedVectors.load("models/fasttext.model") does not support OOV words.
We should use embedding_model = load_facebook_vectors("data/wiki-news-300d-1M-subword.bin") instead which returns a FastTextKeyedVectors object

type of api.load("fasttext-wiki-news-subwords-300") is <class 'gensim.models.keyedvectors.KeyedVectors'>

We should test speed difference between FastTextKeyedVectors.load and load_facebook_vectors

Results of the current (first) fasttext embeddings:
Model Performances:
Model       MSE  R2 Score
0    Linear Regression (OLS)  0.017588  0.504339
1           Ridge Regression  0.017382  0.510155
2  Support Vector Regression  0.017559  0.505167
3              Random Forest  0.018158  0.488285
4          Gradient Boosting  0.016865  0.524708
5                    XGBoost  0.017417  0.509160
6                   LightGBM  0.015981  0.549622

If we regenerate the embeddings we get different results, something might have gone wrong when generating or the eval is wrong.
This might be due to the use of multi-threading for generating the results.
The eval results of the new embeddings:
Model Performances:
                       Model       MSE  R2 Score
0    Linear Regression (OLS)  0.037865 -0.067097
1           Ridge Regression  0.037254 -0.049888
2  Support Vector Regression  0.039038 -0.100151
3              Random Forest  0.035878 -0.011092
4          Gradient Boosting  0.036322 -0.023619
5                    XGBoost  0.043815 -0.234785
6                   LightGBM  0.038205 -0.076691

First fasttext embedding .npz was generated with: https://github.com/StephanAkkerman/FluentAI/commit/cf846057b995528d9f9dcd085c64498d587f1611
Second .npz: https://github.com/StephanAkkerman/FluentAI/commit/90e821f0c334497772719f284b103b9f49000b5d
Parquet: https://github.com/StephanAkkerman/FluentAI/commit/0237a4383aba181f5f876c1a58114f32c1a7cf0d

Can use the following to save the model using OOV words:
embedding_model = load_facebook_vectors("data/wiki-news-300d-1M-subword.bin")
embedding_model.save("models/fasttext2.model")
embedding_model = FastTextKeyedVectors.load("models/fasttext2.model")

We need to test performance between loading the .bin and the saved model

Results of the current (first) fasttext embeddings:
Model Performances:
                       Model       MSE  R2 Score
0    Linear Regression (OLS)  0.017588  0.504339
1           Ridge Regression  0.017382  0.510155
2  Support Vector Regression  0.017559  0.505167
3              Random Forest  0.018158  0.488285
4          Gradient Boosting  0.016865  0.524708
5                    XGBoost  0.017417  0.509160
6                   LightGBM  0.015981  0.549622

Results of the wiki news OOV .bin embeddings
Model Performances:
Model       MSE  R2 Score
0    Linear Regression (OLS)  0.019800  0.441990
1           Ridge Regression  0.019189  0.459208
2  Support Vector Regression  0.019535  0.449464
3              Random Forest  0.019066  0.462678
4          Gradient Boosting  0.017468  0.507718
5                    XGBoost  0.019049  0.463160
6                   LightGBM  0.016137  0.545224
Best Model: LGBMRegressor with 'MSE' of 0.0161

cc.e.300
Model Performances:
                       Model       MSE  R2 Score
0    Linear Regression (OLS)  0.018594  0.475993
1           Ridge Regression  0.018404  0.481340
2  Support Vector Regression  0.018693  0.473204
3              Random Forest  0.017677  0.501824
4          Gradient Boosting  0.016014  0.548687
5                    XGBoost  0.017322  0.511841
6                   LightGBM  0.015197  0.571716

Best Model: LGBMRegressor with 'MSE' of 0.0152

It is better to save the model and load it than load the .bin all the time

Check if cc.en.300.bin is in /data, if not download it: https://dl.fbaipublicfiles.com/fasttext/vectors-crawl/cc.en.300.bin.gz
Load and save the model
Use the saved model for all the fasttext stuff

Could also upload the .bin file to huggingface?


[  ERROR ] raknet-native

I installed before and it was normal, but after I reinstalled with the new version I got an error like this, even though before it worked fine, without any errors.
 Error: Could not locate the bindings file. Tried:
npm ERR!  → /home/container/node_modules/raknet-native/build/node-raknet.node
npm ERR!  → /home/container/node_modules/raknet-native/build/Debug/node-raknet.node
npm ERR!  → /home/container/node_modules/raknet-native/build/Release/node-raknet.node
npm ERR!  → /home/container/node_modules/raknet-native/out/Debug/node-raknet.node
npm ERR!  → /home/container/node_modules/raknet-native/Debug/node-raknet.node
npm ERR!  → /home/container/node_modules/raknet-native/out/Release/node-raknet.node
npm ERR!  → /home/container/node_modules/raknet-native/Release/node-raknet.node
npm ERR!  → /home/container/node_modules/raknet-native/build/default/node-raknet.node
npm ERR!  → /home/container/node_modules/raknet-native/compiled/16.19.0/linux/x64/node-raknet.node
npm ERR!  → /home/container/node_modules/raknet-native/addon-build/release/install-root/node-raknet.node
npm ERR!  → /home/container/node_modules/raknet-native/addon-build/debug/install-root/node-raknet.node
npm ERR!  → /home/container/node_modules/raknet-native/addon-build/default/install-root/node-raknet.node
npm ERR!  → /home/container/node_modules/raknet-native/lib/binding/node-v93-linux-x64/node-raknet.node
npm ERR!     at bindings (/home/container/node_modules/bindings/bindings.js:126:9)
npm ERR!     at Object.<anonymous> (/home/container/node_modules/raknet-native/binding.js:30:33)
npm ERR!     at Module._compile (node:internal/modules/cjs/loader:1165:14)
npm ERR!     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1219:10)
npm ERR!     at Module.load (node:internal/modules/cjs/loader:1043:32)
npm ERR!     at Function.Module._load (node:internal/modules/cjs/loader:878:12)
npm ERR!     at Module.require (node:internal/modules/cjs/loader:1067:19)
npm ERR!     at require (node:internal/modules/cjs/helpers:103:18)
npm ERR!     at checkIfPrebuildExists (/home/container/node_modules/raknet-native/buildChecks.js:7:22)
npm ERR!     at Object.<anonymous> (/home/container/node_modules/raknet-native/buildChecks.js:20:7) {
npm ERR!   tries: [
npm ERR!     '/home/container/node_modules/raknet-native/build/node-raknet.node',
npm ERR!     '/home/container/node_modules/raknet-native/build/Debug/node-raknet.node',
npm ERR!     '/home/container/node_modules/raknet-native/build/Release/node-raknet.node',
npm ERR!     '/home/container/node_modules/raknet-native/out/Debug/node-raknet.node',
npm ERR!     '/home/container/node_modules/raknet-native/Debug/node-raknet.node',
npm ERR!     '/home/container/node_modules/raknet-native/out/Release/node-raknet.node',
npm ERR!     '/home/container/node_modules/raknet-native/Release/node-raknet.node',
npm ERR!     '/home/container/node_modules/raknet-native/build/default/node-raknet.node',
npm ERR!     '/home/container/node_modules/raknet-native/compiled/16.19.0/linux/x64/node-raknet.node',
npm ERR!     '/home/container/node_modules/raknet-native/addon-build/release/install-root/node-raknet.node',
npm ERR!     '/home/container/node_modules/raknet-native/addon-build/debug/install-root/node-raknet.node',
npm ERR!     '/home/container/node_modules/raknet-native/addon-build/default/install-root/node-raknet.node',
npm ERR!     '/home/container/node_modules/raknet-native/lib/binding/node-v93-linux-x64/node-raknet.node'
npm ERR!   ]
npm ERR! }
npm ERR! [raknet] need to build
npm ERR! Build checks are passing! Building...
npm ERR! [
npm ERR!   '/home/container/node_modules/node/bin/node',
npm ERR!   '/home/container/node_modules/.bin/cmake-js',
npm ERR!   'compile'
npm ERR! ]
npm ERR! info TOOL Using Unix Makefiles generator.
npm ERR! info DIST Downloading distribution files to: /home/container/.cmake-js/node-x64/v16.19.0
npm ERR! http DIST 	- https://nodejs.org/dist/v16.19.0/SHASUMS256.txt
npm ERR! http DIST 	- https://nodejs.org/dist/v16.19.0/node-v16.19.0-headers.tar.gz
npm ERR! info REP Build has been failed, trying to do a full rebuild.
npm ERR! ERR! OMG CMake executable is not found. Please use your system's package manager to install it, or you can get installers from there: http://cmake.org.
npm ERR! node:internal/errors:857
npm ERR!   const err = new Error(message);
npm ERR!               ^
npm ERR!
npm ERR! Error: Command failed: cmake-js compile
npm ERR!     at checkExecSyncError (node:child_process:861:11)
npm ERR!     at Object.execSync (node:child_process:932:15)
npm ERR!     at /home/container/node_modules/raknet-native/buildChecks.js:52:10
npm ERR!     at processTicksAndRejections (node:internal/process/task_queues:96:5) {
npm ERR!   status: 1,
npm ERR!   signal: null,
npm ERR!   output: [ null, null, null ],
npm ERR!   pid: 58,
npm ERR!   stdout: null,
npm ERR!   stderr: null
npm ERR! }

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/container/.npm/_logs/2023-01-19T11_31_01_361Z-debug-0.log

As per the error, your computer is missing cmake which must be installed and available in the path. Without cmake build tools installed raknet-native cannot be compiled.
Alternatively you can look at using the raknet-node raknet backend, as explained in the docs.

As per the error, your computer is missing cmake which must be installed and available in the path. Without cmake build tools installed raknet-native cannot be compiled.
Alternatively you can look at using the raknet-node raknet backend, as explained in the docs.

but I use hosting like hosting on pterodactly, is there a way to do it?

I can't comment on your specific situation, but here is a link to installing cmake on Linux systems, required for the default raknet-native backend:
https://robots.uc3m.es/installation-guides/install-cmake.html
You can get it with your systems package manager. Alternatively per our docs you can use raknet-node backend (explained in docs) which should have prebuilds for Linux.

I can't comment on your specific situation, but here is a link to installing cmake on Linux systems, required for the default raknet-native backend:
https://robots.uc3m.es/installation-guides/install-cmake.html
You can get it with your systems package manager. Alternatively per our docs you can use raknet-node backend (explained in docs) which should have prebuilds for Linux.

Only on root ?


Layout issue on product page in case of display mode "list" in arabic locale.

Framework Version: 0.1.5

Framework Version: 0.1.5
Fixed


In Telegram Apps DAO, minimal vote amount display error

Description
In Telegram Apps DAO, minimal vote amount display error
Steps To Reproduce

Enter Telegram Apps DAO https://test.tmrwdao.com/dao/telegram-apps-dao

Current Behavior

Minimal vote amount display error

Expected Behavior

Minimal vote amount display correctly

Environment

Platform: PC
Node: v18.18.0
Browser: Chrome 126.0.6478.56

fixed confirm


Export QR Code as blob data

Allow exporting the QR Code from canvas to a blob data using the HTMLCanvasElement.toBlob() method.
The canvas.js renderer will export new method renderToBlob() which will wrap the toBlob() implementation.

Implemented and released.
<EMAIL_ADDRESS>


How do you fade out inactive slides and keep the opacity at 1 for the active slide?

This is a (multiple allowed):

[ ] bug

[ ] enhancement

[x] feature-discussion (RFC)

Swiper Version: EXACT RELEASE VERSION OR COMMIT HASH, HERE.

Live Link or JSFiddle/Codepen or website with isssue: PREFERABLY (IF YOU WANT YOUR ISSUE TO BE RESOLVED ASAP).

Expected Behavior
EXPLAIN WHAT IS TO BE EXPECTED, HERE.
Actual Behavior
EXPLAIN WHAT IS ACTUALLY HAPPENING, HERE.
P.S. Remember, an issue is not the place to ask questions. You can use Stack Overflow
for that.
Before you open an issue, please check if a similar issue already exists or has been closed before.

Your issue is closed because it is not filled correctly. Before you open an issue please review the contributing guideline.
Please fill the issue template correctly and:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with isssue

It will save a lot of time for other contributors to check your issue and fix it.