[Bug] Crash for Open my HoYoLAB Toolbox me Profile

Checklist

[x] My issue was not mentioned by others, and it is not a duplicate issue.

Description
When you click on my account, the app crashes
Reproduction Steps
Clicking on my profile and a crash occurs
Expected Behavior
No response
Screenshots

https://github.com/Scighost/Starward/assets/40138340/6e58830d-e8d0-4b90-af3e-50439082e42a
Starward Version
0.10.4
Windows Version
22631.2861
Log
[16:29:46.481] [INFO]
Welcome to Starward v0.10.4
System: Microsoft Windows NT 10.0.22631.0
Command Line: I:\Game\Starward\app-0.10.4\Starward.dll

[16:29:46.534] [INFO] Starward.Services.DatabaseService
Database path is 'I:\Game\Starward'

[16:29:46.557] [INFO] Starward.Services.DatabaseService
Database version is 7, target version is 7.

[16:29:46.606] [INFO] Starward.Pages.MainPage
Select game region is hk4e_global

[16:29:46.612] [INFO] Starward.Pages.MainPage
Navigate to "LauncherPage" with param hk4e_global

[16:29:46.911] [INFO] Starward.Pages.LauncherPage
Game install path hk4e_global: "I:\Game\GenshinImpact\Genshin Impact game"

[16:29:46.951] [INFO] Starward.Pages.LauncherPage
Game is running ("GenshinImpact", 14536)

[16:29:46.960] [INFO] Starward.Services.DownloadGameService
Local game version is "4.3.0" (gameBiz: hk4e_global)

[16:29:46.981] [WARN] Starward.Services.GameService
Game uninstalled path not found (hk4e_cn)

[16:29:46.981] [WARN] Starward.Services.GameService
Game uninstalled path not found (hk4e_cloud)

[16:29:46.982] [WARN] Starward.Services.GameService
Game uninstalled path not found (bh3_cn)

[16:29:46.982] [WARN] Starward.Services.GameService
Game uninstalled path not found (bh3_global)

[16:29:46.982] [WARN] Starward.Services.GameService
Game uninstalled path not found (bh3_jp)

[16:29:46.983] [WARN] Starward.Services.GameService
Game uninstalled path not found (bh3_kr)

[16:29:46.983] [WARN] Starward.Services.GameService
Game uninstalled path not found (bh3_overseas)

[16:29:46.983] [WARN] Starward.Services.GameService
Game uninstalled path not found (bh3_tw)

[16:29:47.507] [INFO] Starward.Services.UpdateService
Start to check update (Preview: False, Arch: X64)

[16:29:47.589] [INFO] Starward.Services.UpdateService
Current version: "0.10.4", latest version: "0.10.4", ignore version: "0.10.6-preview.1"

[16:29:52.794] [INFO] Starward.Pages.MainPage
Navigate to "HoyolabToolboxPage" with param hk4e_global

[16:29:52.805] [INFO] Starward.Services.GameRecordService
Change region to Global.

Additional Context
crash_20231224_163000.txt
No response

Thanks for your feedback. It may occur because of
https://github.com/Scighost/Starward/blob/3aed70b49deb10c8a8fc308cf3e2a7b9a680cc7d/src/Starward/Pages/HoyolabToolbox/SpiralAbyssPage.xaml#L495
In spiral abyss floor 9-12, every chamber has two battles. Please see spiral abyss records in HoYoLAB app, is there any record only has one-half battle in some chamber?

All floors have been passed

Please try again, and if it is still happen, send your StarwardDatabase.db to my email, I will check it.

The recent two abyss records of uid 70...54 have no battle data, it caused a crash. This may be an error in the data returned by HoYoverse's server at a specific time.
You should open StarwardDatabase.db with any database edit software, and then execute the following SQL, which will delete the last two record of the account.
DELETE FROM SpiralAbyssInfo WHERE Uid LIKE '70%54' AND ScheduleId IN (83, 84);

PS: This SQL is only used to solve this problem and cannot be used again in the future.

Thanks, everything worked
[image: image.png]
пн, 25 дек. 2023 г. в 18:39, Scighost @.***>:

PS: This SQL is only used to solve this problem and cannot be used again
in the future.
—
Reply to this email directly, view it on GitHub
https://github.com/Scighost/Starward/issues/554#issuecomment-1869031119,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJSHMZCBTYBMPL2B444E2YLYLGM4ZAVCNFSM6AAAAABBBRL4ASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRZGAZTCMJRHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Issue doesn't occur on 0.10.7-beta.1.


TypeError: Cannot read property 'catch' of undefined

when run react-static ...

yup got the same error when i ran react-static --help

got the same issue today. Is that a blocker to start working with react-static?

I got this issue as well, Fedora 30 and Node 10.16.0 installed from package manager. Other than the error message I haven't noticed any other issues with React Static, it's still usable.

Same with Node version 10.16.3.

I found the same problem. I've temporarily done this to avoid this useless error.
Comment the following lines in the react-static file
init().catch(e => {
  console.trace(e)
  process.exit(1)
})

and do this instead
init();


when i need Initialize middlewares something ,how do I do it?

I want to implement a middleware module this function need initialize ets:new.
because this middleware:execute has  ets:lookup/2 ets:delete/2, ets:insert/2

now i change cowboy.erl,
fix start_https/x start_http/x function
init_middleware(Middlewares) ->
Fun =
fun(Middleware) ->
Middleware:module_info(),
erlang:function_exported(Middleware, init, 1) andalso Middleware:init()
end,
lists:foreach(Fun, Middlewares).
can?

Middlewares are one function, surely you can do your ets:new at the start of the function?

my middleware module has session cache ets . so i need load this middleware then init ets

You can do this when you start your own application though? I don't understand why you think Cowboy should do it for you.

middleware, i think this is a like a plugin-in ,so i think the plugin-in initialization

ejaaberd gen_mod.erl

Middlewares are one function, as I mentioned earlier, so there's no initialization going on. They are also specific to a request. They can act as an entry point to other of your own processes, which can do their own initialization, but that's it. Closing, thanks!


Props with defaultProps of undefined show up.

Story definition:
<Checkbox
  onChange={onChange}
  value="yes"
  label="Check the Box"
/>

Storybook's JSX:
<Checkbox
  checked={false}
  color={undefined}
  id={undefined}
  label="Check the Box"
  name={undefined}
  onChange={action('onChange')}
  value="yes"
/>

Looking for a solution I noticed a PR that just got merged in react-element-to-jsx-string, but react-element-to-jsx-string is locked to ^14.0.3.
It allows for filterProps to be a function, so one could exclude props where the value is undefined.
14.3.0 was just released. There are no breaking changes since 14.0.3, but features that might benefit the community.

IMO this should be set as a default, or at least be added to the documentation.
For those looking how to solve this, set this in your storybook configuration file:
addParameters({
  jsx: {
    filterProps: val => val !== undefined,
  },
})

I'm okay with that. Make a PR and i'll merge it!


QT support

Hi, i'm trying to use localForage in a QT5.4 but although IndexedDB is available, the driver is not supported because QT user agent is understood as a Safari.
your test:
if (typeof self.openDatabase !== 'undefined' && self.navigator && self.navigator.userAgent && /Safari/.test(self.navigator.userAgent) && !/Chrome/.test(self.navigator.userAgent)
QT 5.4 passes the http://bl.ocks.org/nolanlawson/raw/c83e9039edf2278047e9/ test
Maybe you can use feature detection instead of relying on user agent.

We tried doing feature detection here, but unfortunately Safari would pass the feature test but fail in actual usage; the only feature test for this would be quite convoluted/slow and we didn’t want to implement it.
I suppose the fix would be whitelisting QT but that seems like quite the rabbit hole. It would be an okay test in my mind though if it broke nothing else, at least for now.

Unfortunately, Qt's user agent will probably not contain "Qt" as it's replaced by application name https://wiki.qt.io/How_to_set_user_agent_in_Qt_application. Crappy...

Another solution would be to be able to force a driver. This could allow shim usage. What do you think?

A custom driver that forced IndexedDB could work, yeah. I'd think QT usage is niche enough requiring a custom driver is okay.

There's no way to get a reference to localForage original drivers from a custom driver, is it?

You can using localforage.getDriver();, actually. I don't think it's an advertised API with docs yet though we should add them. If you wanted the IndexedDB driver, for instance, you could do:
localforage.getDriver(localforage.INDEXEDDB).then(function(driver) { console.log(driver); });

The contents of driver will be the original driver.


Termux Term And Service Violation

As in https://wiki.termux.com/wiki/hacking
Your already violated it, please delete this as possible to support termux developer
Thank you
From:

ZairullahDeveloper, Termux user

Hi @zairullahdev
I don't understand how onex can be a harmful thing if the only thing it does is to type git clone <link>, sudo apt install <something> or curl -o <link> (which installs/downloads something and doesn't even run it) for you. Why don't you read the source code?
If you find a harmful line of code, tell me beacuse I didn't.
If onex teached you how to use hacking tools I would say ok, but not even this.
There lot's of github repos that really could violate termux, why do you think it's only onex?
Even if I agree to remove this repository, this won't help at all because there still lot's of github users that uploaded onex as a repository or just forked it.
Why do you want to completely get rid of this tool only because of termux? Did you read the description about supported OS's? Would be better to just stop supporting termux.
And don't tell that I violated it beacuse as it says in About 'I am not responsible for any misuse caused by this tool and I'm not even the creator of this tool!'


MTDSA-15807: Update Play version to 2.8.18

It'd be worth doing the platops-pr-bot "uk.gov.hmrc.bootstrap-test-play-28" change as part of this (& any others where it has the same comment)


add ssr support

When I import vue-element-loading I get this error in ssr:
ReferenceError: document is not defined
    at /Users/denis/Documents/projects/project-ssr/node_modules/vue-element-loading/node_modules/vue-runtime-helpers/inject-style/browser.js:6:14
    at /Users/denis/Documents/projects/project-ssr/node_modules/vue-element-loading/lib/vue-element-loading.min.js:6:84
    at Object.<anonymous> (/Users/denis/Documents/projects/project-ssr/node_modules/vue-element-loading/lib/vue-element-loading.min.js:6:160)
    at Module._compile (internal/modules/cjs/loader.js:759:30)
    at Module._compile (/Users/denis/Documents/projects/project-ssr/node_modules/pirates/lib/index.js:99:24)
    at Module._extensions..js (internal/modules/cjs/loader.js:770:10)
    at Object.newLoader [as .js] (/Users/denis/Documents/projects/project-ssr/node_modules/pirates/lib/index.js:104:7)
    at Module.load (internal/modules/cjs/loader.js:628:32)
    at Function.Module._load (internal/modules/cjs/loader.js:555:12)
    at Module.require (internal/modules/cjs/loader.js:666:19)
    at require (internal/modules/cjs/helpers.js:16:16)
    at r (/Users/denis/Documents/projects/project-ssr/node_modules/vue-server-renderer/build.dev.js:9315:16)
    at eval (webpack-internal:///vue-element-loading:1:18)
    at Object.vue-element-loading (main.js:1566:1)
    at __webpack_require__ (main.js:21:30)
    at eval (webpack-internal:///../node_modules/babel-loader/lib/index.js!../node_modules/vue-loader/lib/index.js?!./vue/blog/index.vue?vue&type=script&lang=js&:14:49)

And in client:
500 | Internal Server Error
Fixed it all, please merge

Hello @biigpongsatorn @runyasak, please merge this working changes.

Hi, @Sitronik.
Sorry for lately response.
Thank you for amazing PR. However, there have some errors on build.
Please, resolve the errors and update to this PR. 😁

Hi, @Sitronik.
Sorry for lately response.
Thank you for amazing PR. However, there have some errors on build.
Please, resolve the errors and update to this PR. 😁

Hi, your are welcome
Build is works but in deploy app netlify have errors
I changed billi to rollup. You can download this code Then run and you will see everything works correctly

Hi, @runyasak
The errors were due to the uglifyjs library.
We need to come up with an alternative variant of minimizing the library

Fixed build netlify with rollup-plugin-uglify. Please merge and publish 😁


Ensure Dockerfile in context

Carry of #10513 to fix a very small error, but which made all tests to fail.

LGTM
Just noting here for posterity's sake:
This includes a breaking change for anyone using symlinks to link to a Dockerfile which is outside of the build context.

I just realized I'll need to do some changes in the test, but let's not hold this up.
For the record: https://gist.github.com/tiborvass/8cfec4a2500195e94fad
LGTM

LGTM


added cypress tests for critical-ui components

Description

[x] Resolves #109

Checklist

[x] I have followed the repository's contribution guidelines.
[x] I have added necessary documentation or updated existing documentation.
[x] My code follows the established code style and formatting of the project.
[x] I have tested my changes and they function as expected.
[x] I have added suitable unit tests (if applicable).

To be reviewed by: @Nasfame @techyNonso

1/5 Tests Passed :

Error I'm getting in notification.cy.js

Running:  notification.cy.js                                                              (
  Notifications Components
    1) should render Messages component with mock data
    2) should render ModalNotification component with mock data
  0 passing (25s)
  2 failing
  1) Notifications Components
       should render Messages component with mock data:
     AssertionError: Timed out retrying after 10000ms: Expected to find element: `[data-cy=messages]`, but never found it.
      at Context.eval (webpack://app.decenterai.com/./cypress/e2e/notification.cy.js:35:41)

  2) Notifications Components
       should render ModalNotification component with mock data:
     ReferenceError: avatarData is not defined
      at Context.eval (webpack://app.decenterai.com/./cypress/e2e/notification.cy.js:54:24)

Error I'm getting in repository.cy.js

Running:  repository.cy.js                                                                (
  Page Component
    1) should interact with the page elements and repository component

  0 passing (16s)
  1 failing

  1) Page Component
       should interact with the page elements and repository component:
     AssertionError: Timed out retrying after 10000ms: Expected to find element: `.h-full`, but never found it.
      at Context.eval (webpack://app.decenterai.com/./cypress/e2e/repository.cy.js:10:46)

Error I'm getting in settings.cy.js

  Settings Page
    1) should interact with the settings page elements

  0 passing (15s)
  1 failing

  1) Settings Page
       should interact with the settings page elements:
     AssertionError: Timed out retrying after 10000ms: Expected to find content: 'Profile' but never did.
      at Context.eval (webpack://app.decenterai.com/./cypress/e2e/settings.cy.js:10:11)

Error I'm getting in train.cy.js

Train Page Component
    1) "before each" hook for "should interact with the train page elements"

  0 passing (5s)
  1 failing

  1) Train Page Component
       "before each" hook for "should interact with the train page elements":
     CypressError: `cy.visit()` failed trying to load:

http://localhost:3000/dashboard/train

The response we received from your web server was:

  > 500: Internal Server Error

This was considered a failure because the status code was not `2xx`.

If you do not want status codes to cause failures pass the option: `failOnStatusCode: false`

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `Train Page Component`
      at <unknown> (http://localhost:3000/__cypress/runner/cypress_runner.js:131299:76)
      at visitFailedByErr (http://localhost:3000/__cypress/runner/cypress_runner.js:130707:12)
      at <unknown> (http://localhost:3000/__cypress/runner/cypress_runner.js:131282:13)
      at tryCatcher (http://localhost:3000/__cypress/runner/cypress_runner.js:1807:23)
      at Promise._settlePromiseFromHandler (http://localhost:3000/__cypress/runner/cypress_runner.js:1519:31)
      at Promise._settlePromise (http://localhost:3000/__cypress/runner/cypress_runner.js:1576:18)
      at Promise._settlePromise0 (http://localhost:3000/__cypress/runner/cypress_runner.js:1621:10)
      at Promise._settlePromises (http://localhost:3000/__cypress/runner/cypress_runner.js:1697:18)
      at _drainQueueStep (http://localhost:3000/__cypress/runner/cypress_runner.js:2407:12)
      at _drainQueue (http://localhost:3000/__cypress/runner/cypress_runner.js:2400:9)
      at Async._drainQueues (http://localhost:3000/__cypress/runner/cypress_runner.js:2416:5)
      at Async.drainQueues (http://localhost:3000/__cypress/runner/cypress_runner.js:2286:14)
  From Your Spec Code:
      at Context.eval (webpack://app.decenterai.com/./cypress/e2e/train.cy.js:5:11)

Please change to .ts

@utkarsh-1602 the CI is failing, deployment failing. Can u take a look. See if u can use typescript

@techyNonso can u look at the cypress issue?

@utkarsh-1602 update ur branch

@Nasfame what do you think about the task errors

@Sheriff-Oladimeji pnpm add -D wait-on

@techyNonso can u review?


Install Hello World but crashed with: Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]

System information (Please provide as much relevant information as possible)

Docker built with https://google.github.io/mediapipe/getting_started/install.html.
Device with Android 7.1.2.

Describe the problem:
I am using docker to build apps followed by https://google.github.io/mediapipe/getting_started/install.html.
I am trying to deploy helloworld application.
I tried to build app with :
bazel build -c opt --config=android_arm64 $APPLICATION_PATH:helloworld
and it worked.
Then I connect the device with adb connect.
Then I tried to install it with :
adb install bazel-bin/$APPLICATION_PATH/helloworld.apk
and it crashed.
Complete Logs:
$ adb install bazel-bin/$APPLICATION_PATH/helloworld.apk
adb: failed to install bazel-bin/mediapipe/examples/android/src/java/com/google/mediapipe/apps/basic/helloworld.apk: Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]

@zhiheng-ldj, Did you check this https://github.com/google/mediapipe/issues/1402


Add second folder

VSCode Version: 1.15.0 Insiders (56a5bf1, Date 2017-07-13T06:29:54.260Z)
OS Version: Windows 10

-- Sorry for the English, I used Google Translator --
Sorry for the question but ..
Question 1- But why am I forced to create a work area?
I simply want to add a second folder, without having to create a specific workspace.
Also when I create the work area it changes the color of the Status bar. (I do not think that would ask it to happen).
This window should have a third option, "Add only the folder".

That is, the options would be: "New Workspace", "Add only the folder", "Cancel".
Question 2 - What's more, why the "Close Folder" option changed "Close Workspace", even though a Workspace has not yet been created? The menu should change only when a workspace was created, right?

If you need to create a separate issue, please move one of them.

Reproduces without extensions: Yes

@Tekbr thanks for your feedback, this UI is very young and might change until the final bits are out. We want to make workspaces an explicit concept for multi root. You cannot have multiple folders in the classical single-folder views currently. Creating a workspace will bring you into a new experience (hence the status bar change).
I know this is different from how it works in stable currently, but we had lengthy design discussions around the flaws of the model in stable and decided to go with this approach.

@Tekbr see https://github.com/Microsoft/vscode/issues/396#issuecomment-315079618

-- Sorry for the English, I used Google Translator --
@bpasero Thanks for the quick response, for the attention and patience. Yes I know it's at the beginning, but I found it a bit strange. But I'll wait for the news (said by you in the #396 (comment))

-- My thought, perhaps the community has another vision --
I think a Workspace should be a project that has several folders. But sometimes we are upgrading the old project to a new project (or querying a similar project folder), and we want to add the old project folder, but without the need to bind.

Another note (which will probably change in the future): Unsaved workspace should not be placed in Recent Open until it is saved. By clicking "Close Workspace" and if it is not saved, it would be interesting to ask if you would like to save. If the user clicks No, it should not be placed in the menu.
Why that? Because the menu will be very polluted. In addition, you can not differentiate between "Untitled Workspace".

Yeah we think about asking you to save a untitled workspace once you close the window. Good point about the fact that untitled workspaces should not show up in the recent history 👍

-- Sorry for the English, I used Google Translator --

Yeah we think about asking you to save a untitled workspace once you close the window.

@bpasero I think the question should only remain when closing the Workspace, not when closing the window.
If I open another folder with VSCode (right button> Open With VSCode) - it can not be running - and if in the last session it was open an Untitled Workspce, maybe an alert asking if: I want to save the last Workspace before opening The new folder or discard the old Workspace and open the new folder or open last session before (and discard the current folder.)

@Tekbr our current thinking is to ask as soon as you close the window, otherwise we would need to introduce yet another way of dismissing a "Untitled Workspace".

-- Sorry for the English, I used Google Translator --
@bpasero I think it is best to discard only when we click on "Close Workspace", or the situation described above.
Recalling that within a Workspace there may be unsaved file and Untitled file. In this case it would be good to alert that modified and / or unsaved files (Untitled) could be lost. Or is there no such possibility? Once a workspace is saved, does it matter all the data (including files are saved)?
Or am I saying something silly? Sorry for anything...

@Tekbr sure, dirty files would also cause us to ask what to do (save), I would not change that behaviour.
If we decide to not cleanup an untitled workspace when you are not closing the window, we would still need to show all untitled workspaces in the "File > Open Recent" menu, how do you otherwise get back to them to close them? And we would need even more UI to dismiss an untitled workspace without opening it to manage them. I find that a lot of UI which can be avoided by just asking you to save the workspace when you close the window?

-- Sorry for the English, I used Google Translator --
@bpasero  By what I understand (and according to Google Translate) ...

If we decide to not cleanup an untitled workspace when you are not closing the window, we would still need to show all untitled workspaces in the "File > Open Recent" menu, how do you otherwise get back to them to close them?

(I do not know if it's possible) - thought
Currently if I close the VSCode with a folder, and when I open it again it returns no was it, correct?
If you close the VSCode with an untitled workspace when opening the VSCode again it should open as closed, that is, with the untitled workspace.
If it detects that a new folder has been opened (other than the workspace) it should say 'I want to save the last workspace before opening the new folder' or if 'I want to discard the workspace and open the new folder' or 'go back to the last workspace And discard the current folder '. (As I said earlier)
Or option would be:
Limit to 2 or 3 untitled workspace, when the next one is created (the 4 untittled) would ask what you want to save or warn that the oldest will be deleted and you want to continue.
Showing next to the name untitled the date / time it was created (DD / MM / YYYY - HH: MM: SS) in File recent

I find that a lot of UI which can be avoided by just asking you to save the workspace when you close the window?

In this case you are obliged to save something that is not definitive that has no bond, but that I will use again in some mometo of the day or for some days.
Another idea (even to get more organized) would be to create "File> Open Recent Workspace"

@Tekbr it depends on the OS: On Windows and Linux if you close the last window, we close VS Code and in that case we would not ask to save the workspace and simply restore it the next time you open. However, on macOS, closing the last Window does not quit the application so we would ask to save the workspace.
This feature should work in the same way as "hot exit" works for files today imho.
Good idea about showing the date for untitled workspaces. However, I am not even convinced yet that untitled workspaces should show up under the "Files > Open Recent" category...

All these changes landed, I suggest to retest this and give it individual issues when seeing something. The smooth transition from 1 to 2 folders is something we have on our backlog.

-- Sorry for the English, I used Google Translator --
@bpasero Sorry for the delay...

However, on macOS, closing the last Window does not quit the application so we would ask to save the workspace.

Well ... I've never used MacOS so far.
But from what I understand (according to Google Translate), if I want to close the VSCode window, in MacOS does it keep it open, closing like it's a folder in Windows or Linux? Is that it? Strange ...
So I suggested reopening works on Windows and Linux, but it does not work on MacOS. Would that be it?
It may be complex, but why not do it for Windows and Linux, since it works well for both? Some things have already been done where it only works for Mac or better on Mac.

Good idea about showing the date for untitled workspaces.

As for the date / time do not forget to use the format according to OS settings.

All these changes landed, I suggest to retest this and give it individual issues when seeing something. The smooth transition from 1 to 2 folders is something we have on our backlog.

Ok I'll check out the latest version of the Insiders


One way associations

Would love for people to test this out soon, I'll write up some of the changes needed.
Basically you need to define inverses (if they are defined), similar to how Ember Data works. Other than that things should work.

I'll test it once I have an example to follow 👍

@knownasilya here ya go! https://ember-twiddle.com/ec3a4c625c43e7a38f3c6c0c1b8232ec?openFiles=mirage.scenarios.default.js%2C

Hey this is really great!
Dropping into my GraphQL app Just Continued to Work
myManyRelationship.add( is a welcome addition
Doing this in my scenarios/default.js works as well!:
export default function(server) {
  server.createList('project', 2, {
    todos: server.createList('todo', 3)
  });
}

Nice work @samselikoff 👍

Wow that's great news! I'm writing a blog post now with more information.
One piece that's not in there right now is updating foreign keys after a delete, so you'll need to handle that logic yourself at the moment. I'm going to work it in soon though.

Dependents are now cleaned up after deletions (i.e. foreign key consistency)

@samselikoff I'm using 0.3.0-beta in a new project and it's working fine. Would be nice if you could release a beta6 dropping requirement of Object.assign().

@HeroicEric Thanks for fixing!

Will cut new beta release soon


Add issue types - tagging

Accommodation
non-food item
food item
legal advice

Multiple issue types per issue have been implemented and deployed.
The types of issues are editable in the admin interface.


in proto2, the generated validator does not invoke the validator of the nested required message

Given this proto:
syntax = "proto2";

import "validate/validate.proto";

message Person {
  message Location {
    required double lat = 1 [(validate.rules).double = { gte: -90,  lte: 90 }];
    required double lng = 2 [(validate.rules).double = { gte: -180, lte: 180 }];
  }

  required string email = 1 [(validate.rules).string.email = true];
  required Location home = 2;
  optional Location second_home = 3;
}

the generated PersonValidator does not invoke the LocationValidator for the home field
object PersonValidator extends scalapb.validate.Validator[Person] {
  def validate(input: Person): scalapb.validate.Result =
    scalapb.validate.Result.run(io.envoyproxy.pgv.StringValidation.email("email", input.email)) &&
    scalapb.validate.Result.optional(input.secondHome) { _value =>
      PersonValidator.LocationValidator.validate(_value)
    }

  object LocationValidator extends scalapb.validate.Validator[Person.Location] {
    def validate(input: Person.Location): scalapb.validate.Result =
      scalapb.validate.ComparativeValidation.rangeGteLte("lat", input.lat, -90.0, 90.0) &&
      scalapb.validate.ComparativeValidation.rangeGteLte("lng", input.lng, -180.0, 180.0)
  }
}

https://github.com/envoyproxy/protoc-gen-validate is Proto3 only, so none of the tests in the 900+ test case harness checks that required fields are handled correctly. I think we can still make required fields work in ScalaPB-validate - thanks for reporting.

Yes, that's a borderline feature...
Thanks a lot for this fix! May i ask you a new bump 🤞 ? I would be very please to test on our project and give you some feedbacks.

Sure, I just pushed 0.1.4

@thesamet we used scalapb-validate with proto2 for a while now without any issue.


Fix tideways-daemon init script

tideways-daemon 1.9.6 removed support for the --pidfile option [1], because tracking processes via their PID is inherently unreliable.
Migrate to start-stop-daemon’s --make-pidfile option as a short-term fix, until either adding a proper service manager to the image or using the official Tideways Daemon Docker Image [2].
[1] https://tideways.com/profiler/blog/changelog/daemon-1-9-6-released
[2] https://support.tideways.com/documentation/setup/installation/docker-with-compose.html#with-docker-compose

thank you so much for this
ill check it out next week :)


legend custom icon deformation

Version
4.8.0
Reproduction link
https://gallery.echartsjs.com/editor.html?c=xY58XMB6n3&v=2
Steps to reproduce
chart dom size changed，legend custom icon deformation
What is expected?
No deformation
What is actually happening?
deformation

because use icon path do not change color，and add fill in path can cause legend  collapse
symbolKeepAspect attribute only supported path icon

Seems to be a bug. Thank you for reporting!

Seems to be a bug. Thank you for reporting!

Because I closed the click event, in fact, when I triggered the click, it would be deformed

By now, I think it may be not a bug. Except using path type, if you have to take image as the type of legend, you'd better set itemWidth and itemHeight as real with and height of the image.
See https://gallery.echartsjs.com/editor.html?c=xY58XMB6n3&v=3

到目前为止，我认为这可能不是错误。除了使用path类型，如果你要image像传说中的类型，你最好设定itemWidth，并itemHeight与真正的和高度的图像。
参见https://gallery.echartsjs.com/editor.html?c=xY58XMB6n3&v=3

Thank you for your reply. I may fall into a mistake. I think we will get the width and height by default and define them. I didn't notice that the size of the image can be specified.

@JeffesJiang If your problem has been solved and this is not a bug, please consider closing the issue. Thanks.


Adapt policy import for IPFS storage

Problem description
Current implementation of policy import assumes local DB storage of all referenced material. This is no longer the case with the introduction of the decentralised IPFS storage.
Requirements

Parse blocks to identify all referenced schemas, 'dereference' them by loading the documents into cache (local DB)
Introduce 'creator' and 'owner' concepts for policies such that RootAuthority which imported schema is identified as an 'owner' (not 'creator') and thus could only create a new policy out of the imported one, but not  a new version (the latter is the prerogative of the 'creator')

DOD

Acceptance criteria fullfiled
Documentation and demo scripts are changed to reflect new user roles

Acceptance criteria

Policy importing and processing conforms to the creator/owner conceptual framework, published policies are immutable
UI displays the origin of the policy and enables only operations that are available (others are either greyed out or hidden)

API Needs to be commented and Demo Script needs to be updated.

Ticket is Done. It needs to be Documented by @anvabr . As per Andrey,  If @sergmetelin  asks to implement upload / download of files, we will do this as a separate ticket / task.


Breaks vi-delete function

Using rxvt-unicode (urxvt) v9.21, zsh 5.3.1 and zsh-autosuggestions v0.3.3:
Start a "clean" shell, go into vi mode, type something, press <Esc>, press d, press l, the last letter you type will be deleted. Now source zsh-autosuggestions, type something, do <Esc>dl, the last letter won't be deleted.
Something like this:
zsh -f
set -e vi
echo^[dl^C
source zsh-autosuggestions.zsh
echo^[dl

I've added a failing spec for this to the fixes/vi-delete branch: https://github.com/zsh-users/zsh-autosuggestions/blob/fixes/vi-delete/spec/integrations/vi_mode_spec.rb

Should be fixed now on develop. Will go out with the next release.


A ton of empty divs

I was trying out this package, and the page I added a popup to seems to have a ton of empty <div> elements in the DOM. This screenshot is the DOM while the popup hasn't been opened yet.

@AshotN  you have to either make prop destroyOnClose={true} or you need to call destroy  method
const { show, **destroy** } = await Modal.new(config)

        const { show } = await Modal.new({
            title: 'New Playlist',
            content: (
                <InputModal
                    inputLabel='New Playlist Name'
                    inputPlaceholder='Rock & Roll...'
                    submitButtonText='Create'
                />
            ),
            footer: null,
            popupStyle: {
                minWidth: 400
            }
        });
        const result = await show();

Here is one of my Modals. You can view the entire source code if it helps, it's on https://github.com/ampache/ampache/tree/react-client.

Overall very pleased with the package though. Thank You!

@AshotN  hey sorry i can't find the file, can you please reproduce it in codesandbox.

        const { show } = await Modal.new({
            title: 'New Playlist',
            content: (
                <InputModal
                    inputLabel='New Playlist Name'
                    inputPlaceholder='Rock & Roll...'
                    submitButtonText='Create'
                />
            ),
            footer: null,
            popupStyle: {
                minWidth: 400
            }
        });
        const result = await show();

Here is one of my Modals. You can view the entire source code if it helps, it's on https://github.com/ampache/ampache/tree/react-client.
Overall very pleased with the package though. Thank You!

@AshotN in this example you must pass destroyOnClose = false to confirm or call destroy method once you got the result
const { show } = await Modal.new({
           destroyOnClose: true, // do this
            title: 'New Playlist',
            content: (
                <InputModal
                    inputLabel='New Playlist Name'
                    inputPlaceholder='Rock & Roll...'
                    submitButtonText='Create'
                />
            ),
            footer: null,
            popupStyle: {
                minWidth: 400
            }
        });
        const result = await show();

OR
const { show, destroy } = await Modal.new({
            title: 'New Playlist',
            content: (
                <InputModal
                    inputLabel='New Playlist Name'
                    inputPlaceholder='Rock & Roll...'
                    submitButtonText='Create'
                />
            ),
            footer: null,
            popupStyle: {
                minWidth: 400
            }
        });
        const result = await show();
       destroy(); // do this

Sorry for my delay, I am going to try to pick back up the codebase that this issue was referencing, and if the issue still exists I will update this issue.


Issues Installing Docker on Mac OS X 10.11

Description of problem:
When trying to run
docker run hello-world
Cannot connect to the Docker daemon. Is 'docker -d' running on this host?
docker version: Docker version 1.8.3, build f4bf5c7
docker info:
➜  ~  docker info
Cannot connect to the Docker daemon. Is 'docker -d' running on this host?

uname -a:
Darwin Brads-MacBook-Pro.local 15.0.0 Darwin Kernel Version 15.0.0: Wed Aug 26 16:57:32 PDT 2015; root:xnu-3247.1.106~1/RELEASE_X86_64 x86_64
Environment details (AWS, VirtualBox, physical, etc.):
VirtualBox Version 5.0.8 r103449
How reproducible:
Steps to Reproduce:

Visit this url https://docs.docker.com/installation/mac/
Follow instructions for installing + running toolbox
Opened virtualbox and made sure that the "default" machine is running

Actual Results:
➜  ~  docker info
Cannot connect to the Docker daemon. Is 'docker -d' running on this host?
 Should it be included in my bash profile?

@BradRuderman it depends; if you have just one machine, you could add it to your profile, but otherwise running it is the best way. The "Docker Quickstart Terminal" should do that for you though, but if you're having issues with that, it's best to post those in the Docker Toolbox issue tracker; https://github.com/docker/toolbox/issues
I'm going to close this issue, because this is not a bug, but feel free to respond after I've closed


updated readme

Thanks for the contribution! Could you actually move the npm install to the getting started section? Since it applies to any way you want to run the app. Thanks!

done

thank you!


doom command doesnt work

yeah when i type the command it doesnt work :V

Make sure everything is installed properly, for example make sure you have the correct dependencies and versions.

this happened to me when i had a full copy of doom for the wad, not the shareware version


Jetty hangs occasionally for 30 seconds on some requests. Happens mostly on Windows

Looks like a real bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=452246

To solve upgrade Jetty


Add whenCmd

@MangelMaxime what do you think about this PR?

https://github.com/slaveOftime/Fun.Build/issues/31

It looks good in to me in term of code usage.
Do you have an example of the generated help message?

If you write this:
pipeline "cmd-info" {
    description "Check cmd info build style"
    stage "" {
        whenAny {
            whenCmd {
                name "-w"
                alias "--watch"
                description "watch cool stuff"
            }
            whenCmd {
                name "run"
                description "run cool stuff"
                acceptValues [ "v1"; "v2" ]
            }
        }
        echo "here we are"
    }
    runIfOnlySpecified
}

You can get help info like:
Description:
  Pipeline cmd-info (command only help information)
  Check cmd info build style

Usage:
  dotnet fsi .\demo.fsx -- -p cmd-info [options]
  dotnet fsi .\demo.fsx -- -p cmd-info -h
  dotnet fsi .\demo.fsx -- -p cmd-info -h --verbose

Options(collected from stages):
  run  (v1, v2)                   run cool stuff
  -w, --watch                     watch cool stuff
  -h, --help                      Show help and usage information
  -v, --verbose                   Make the help information verbose

When reading, the help message I don't know how to read the (...), I think I never saw parenthesis used in CLI documentation.
Here is how yargs represents choices:
~/projects/node-sx4ggg 6s
❯ node index.js
Options:
      --version     Show version number                                [boolean]
  -i, --ingredient  choose your sandwich ingredients
                        [choices: "peanut-butter", "jelly", "banana", "pickles"]
      --help        Show help                                          [boolean]

I think this is what I am most used to read in other CLI tools too.
In your case it would gives:
Description:
  Pipeline cmd-info (command only help information)
  Check cmd info build style

Usage:
  dotnet fsi .\demo.fsx -- -p cmd-info [options]
  dotnet fsi .\demo.fsx -- -p cmd-info -h
  dotnet fsi .\demo.fsx -- -p cmd-info -h --verbose

Options(collected from stages):
  run                             run cool stuff
                                  [choices: "v1", "v2"]
  -w, --watch                     watch cool stuff
  -h, --help                      Show help and usage information
  -v, --verbose                   Make the help information verbose

Or perhaps:
  run  [choices: "v1", "v2"]                           run cool stuff

What do you think?

Changed it to:
  run                             run cool stuff
                                  [choices: "v1", "v2"]

Awesome thank you


Token (NFT) metadata not visible if not suitable for image render

Description
I have created an NFT with metadata that doesn't resolve to an image (https://hashscan.io/testnet/token/0.0.4686859/1), given this, the NFT's metadata doesn't appear to be visible anywhere.
I would expect that in the event an image can't be rendered, the raw metadata would be available in the UI.
(maybe we should show the raw metadata and optionally an image if it can be rendered ?)
Steps to reproduce
Follow this link: https://hashscan.io/testnet/token/0.0.4686859/1
Additional context
No response
Hedera network
testnet
Version
v24.4.0-195
Operating system
None

Looking at token info returned by mirror node, I see:
   ...
    "metadata": "",
   ...

shouldn't it be initialized ?

I suggest to always show the content of the (raw) metadata property in the NFT.
So in the present case, we'll get this:


Compile error with zlib-ng 2.1.3 when included from other project

Hi.  Thanks for the lib-ng project; it's a really nice replacement for regular zlib.
When trying to update zlib-ng from 2.0.7 to 2.1.3 in C-Blosc2 library, I am getting this (new) error:
[ 27%] Building C object blosc/CMakeFiles/blosc2_static.dir/__/internal-complibs/zlib-ng-2.1.3/adler32.c.o
In file included from /Users/faltet/blosc/c-blosc2/internal-complibs/zlib-ng-2.1.3/adler32.c:7:
In file included from /Users/faltet/blosc/c-blosc2/internal-complibs/zlib-ng-2.1.3/functable.h:9:
/Users/faltet/blosc/c-blosc2/internal-complibs/zlib-ng-2.1.3/deflate.h:212:34: error: expected parameter declarator
    struct crc32_fold_s ALIGNED_(16) crc_fold;
                                 ^
/Users/faltet/blosc/c-blosc2/internal-complibs/zlib-ng-2.1.3/deflate.h:212:34: error: expected ')'
/Users/faltet/blosc/c-blosc2/internal-complibs/zlib-ng-2.1.3/deflate.h:212:33: note: to match this '('
    struct crc32_fold_s ALIGNED_(16) crc_fold;
                                ^
/Users/faltet/blosc/c-blosc2/internal-complibs/zlib-ng-2.1.3/deflate.h:212:37: error: expected ';' at end of declaration list
    struct crc32_fold_s ALIGNED_(16) crc_fold;
                                    ^
                                    ;
/Users/faltet/blosc/c-blosc2/internal-complibs/zlib-ng-2.1.3/deflate.h:212:25: error: field 'ALIGNED_' declared as a function
    struct crc32_fold_s ALIGNED_(16) crc_fold;
                        ^

We have been triggering the zlib-ng build process from C-Blosc2 since 1.0, and it worked well so far, but not anymore with 2.1.3.  Can you shed some light on what could be going on here?  Thanks in advance!

Looks like ALIGNED_ is defined from HAVE_ATTRIBUTE_ALIGNED which, maybe mean it possibly isn't detecting attribute(aligned(x)) properly.
I was looking at your CMake and I think in zlib-ng CMake we do target_include_directories(... PUBLIC ..) which makes this not necessary:
file(COPY
                ${CMAKE_CURRENT_BINARY_DIR}/internal-complibs/${ZLIB_NG_DIR}/zconf.h
                DESTINATION ${CMAKE_CURRENT_SOURCE_DIR}/internal-complibs/${ZLIB_NG_DIR}/)

There might be something to it that I'm not seeing though.

https://github.com/Blosc/c-blosc2/blob/main/CMakeLists.txt#L183C9-L183C61 is incorrect... It's missing second parameter.

Update:
I was able to resolve the issue by updating MSYS2 with Pacman -Syu.
I normally don't update MSYS2 regularly because they sometimes f*ck up.


How to installing gpar in windows systerm?

Dear senior,
I am a postgraduate of yunnan university,I recently research the paper about gpar and try to run the code which you write, however I meet some problems,I can't install the gpar ,my computer systerm is windows. If you can help me to cancel this problem,that's very nice for me.
Look forward to your reply.

I believe that pip install gpar within Cygwin should work. Could you try that?

OK，thank you


Add Shubham Sharma to Contributors list

first pull request

Hi  @shubham99999, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.


Pass **kwargs to super call in F000LevelControlCluster

Probably not needed because the call is not used but...

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

zhaquirks/tuya/ts110e.py
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
6231

Relevant Lines:
7526

💛  - Coveralls

Codecov Report
Base: 82.79% // Head: 82.79% // No change to project coverage :thumbsup:

Coverage data is based on head (b50f3a8) compared to base (249ec6d).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##              dev    #1871   +/-   ##
=======================================
  Coverage   82.79%   82.79%
=======================================
  Files         242      242
  Lines        7526     7526
=======================================
  Hits         6231     6231
  Misses       1295     1295

Impacted Files
Coverage Δ

zhaquirks/tuya/ts110e.py
64.44% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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

Thanks David


fix: [Session] Redis connect to protocol TLS

Description
Fixed #7178
Ref https://3v4l.org/kM3JD
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[x] Unit testing, with >80% coverage
[x] User guide updated
[x] Conforms to style guide

Thank you @ddevsr


Email validator documentation is inconsistent with behaviour

The documentation for the email validator clearly states that

Important! Besides null and undefined being valid empty strings and whitespace only strings are also valid..

However empty strings and whitespaces are not valid. The validator spec even has a test to that effect.

Please make documentation consistent with expected behaviour.

Fixed


Improve handling of filesystem paths that begin with /. Add tests for create and append.

Append was fixed here: https://github.com/IBM/GEDS/pull/96


[chore] Change workflow instance name from pd

Brief Summary of The Change

Change instance name from pd to workflow
Pull Request checklist
I confirm that the following checklist has been completed.

[x] Add/Change test cases for the changes.
[x] Add/Change the related documentation, should also change docs/source/config.rst when you change file default_config.yaml.
[x] (Optional) Add your change to UPDATING.md when it is an incompatible change.

Codecov Report

Merging #42 (67b6ef2) into main (85a1dfa) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #42   +/-   ##
=======================================
  Coverage   90.68%   90.68%
=======================================
  Files          59       59
  Lines        2073     2073
=======================================
  Hits         1880     1880
  Misses        193      193

Flag
Coverage Δ

unittests
90.68% <100.00%> (ø)

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

Impacted Files
Coverage Δ

src/pydolphinscheduler/core/workflow.py
81.86% <100.00%> (ø)

src/pydolphinscheduler/core/yaml_workflow.py
91.82% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Let people name their breakers!

Closes #4

Coverage increased (+0.02%) to 98.611% when pulling f880f5efd09282eb8b501d4c2b2ea9a9ef9489e7 on 4-named-breaker into 16d6d92d7f6df5191356951fdac56056d546c394 on master.


fix udp transport for stm32f767zi.

the bsp, freertos and lwip code is auto-generated by STM32CubeMX v6.4.0, with FirmwareF7_v1.16.0
known issue: #96
the code is based on https://github.com/ZhenshengLee/ros2_mcu/tree/master/libs/custom_stm32f767zi

Hi @ZhenshengLee, I believe you pushed some extra files to the commit 😃. I can see here that 451 files have changed.

Hi @ZhenshengLee, I believe you pushed some extra files to the commit smiley. I can see here that 451 files have changed.

Hi, @LiWeiAn
Actually, this PR of one commit consists of three parts:

edit the micro_ROS.iox and make the HAL&bsp config to meet the requirement of both serial and udp transport
regenerate the code of HAL+FreeRTOS+LWIP using STM32CubeMX v6.4.0 and FW_v1.16.0, this is to make sure that the basic software is up-to-date from official toolchain to avoid potential bugs.(this makes most of the changes)
adapt the code of UROS adapters(including memory manager, transport adapter, FreeRTOS_POSIX, and main function etc.) according to officially supported olimex_e407 project

this PR is basically from my personal maintained repo, threr are 3 commits
https://github.com/ZhenshengLee/ros2_mcu/commit/365608bdb60beb434e5f289b8e9e8dce3f7502d0
https://github.com/ZhenshengLee/ros2_mcu/commit/2499d039e3fd61e3579ff64eb5536aebd01692f7
https://github.com/ZhenshengLee/ros2_mcu/commit/6b35470367323d2b5770d74c0b3e3c22693e06b9

@pablogs9 could you give this a review?

due to no response, closing this.


Add theming support for hovered tabs

This adds a distinct theming possibility for tabs when hovered by the mouse.
Proposal: https://github.com/godotengine/godot-proposals/issues/6462
Comes with presets for the editor & default theme generators.
This change is compatible with 3.x, but the theme generators must be adapted for the 3.x styles.

Remember that your commits need to be squashed into one before the PR can be merged. Refer here: https://docs.godotengine.org/en/stable/community/contributing/pr_workflow.html#the-interactive-rebase


can I fine-tune on any language?

Self Checks

[X] I have searched for existing issues search for existing issues, including closed ones.
[X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
[X] Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.
for example, Brazilian Portuguese (PT-BR). without any phoneme or change any code, Just add the dataset and voilà?
2. Additional context or comments
No response
3. Can you help us with this feature?

[X] I am interested in contributing to this feature.

https://tts.byylook.com/ai/text-to-speech

You can refer tutorial


LDAP Support

Provide a method in the helm charts to configure LDAP with Nautobot.

Technically this could be achieved today with a custom image (to install the ldap dependencies) and custom nautobot_config.py.  With the implementation of https://github.com/nautobot/nautobot/pull/1073 we will no longer need a separate image.  However, the default nautobot_config.py does not currently contain ldap config settings.  I would suggest we get them added there to pull from the env and the helm chart just utilize those settings.

If issue 6234 of Nautobot is accepted and implemented. We won't need to update the whole nautobot_config.py file and could easily support LDAP through config maps.


Fix that prevents multiple listener calls when EXPANDED or COLLAPSED

Hi! Thanks for the lib. Cool that it's written in Kotlin!
I found it's not correct that listener triggers with Expanded/Collapsed state while it's already Expanded/Collapsed;
Tried to not use CMD + OPT + L to make PR keep small

Hey, thanks for the PR, but this library is not maintained at the moment, I don't have time to dedicate to it. Feel free to fork and change what you need :)


Copy Files task: Contents is marked as required but has a default

(Required) File paths to include as part of the copy. Supports multiple lines of match patterns.

But at the end of the section:
Default value: **

So either the contents are optional or there is no point in documenting a default value.

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

ID: 81f02378-b85b-d3a4-d3c8-f07d935367da
Version Independent ID: fab57f76-35d2-4024-6f7f-1740d7b24743
Content: Copy Files task - Azure Pipelines
Content Source: docs/pipelines/tasks/utility/copy-files.md
Product: devops
Technology: devops-cicd-tasks
GitHub Login: @steved0x
Microsoft Alias: sdanie

It is marked as required in the task source code for the task (they are open source) https://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/CopyFilesV2/task.json#L46
In this case, I believe you cannot specify an empty string for this parameter, so that is the logic for it being required.
Please check this task article in our new task reference which s now generated using the task source code and metadata from the task.json.
https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/copy-files-v2?view=azure-pipelines&tabs=yaml&viewFallbackFrom=azure-devops

Fair enough that it is not a documentation error, just nonsense on the part of the task, or I'm not understanding what required means and what a default value means. The v2 task still contains the same contradiction:
Contents - Contents
string. Required. Default value: **.

The file paths to include as part of the copy. This string supports multiple lines of match patterns.

I'll create an issue over on the task.


feat: add C implementation for math/base/special/asind

Resolves # .
Description

What is the purpose of this pull request?

This pull request:

add C implementation for math/base/special/asind

Related Issues

Does this pull request have any related issues?

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[X] Read, understood, and followed the [contributing guidelines][contributing].

@stdlib-js/reviewers

@Pranavchiku I have addressed all the issues you mentioned in your review. Please take a look at the changes


Document update for jsdoc installation, and also fixing the example path

ping @halton for this README update


state abcent instead of abcent

I think the module state should be called absent instead of abcent.

Yes of course, thanks!


feat: allow excluding files when zipping

Allows the user to exclude files when zipping the folder, real world use case for this would be excluding sourcemaps for example when using the sentry plugin you need to have them but when zipping the actual extension I don't want to have them to not "expose" the structure of my codebase.
I didn't add the include option since you can do that using the public folder
I am not quite sure about the JSDoc, had to escape it like this, anyone know a proper fix for that?

JSDoc looks fine. When you add an option, you also need to add it to resolve-config.ts: https://github.com/wxt-dev/wxt/blob/36cfcd0acb57a1958f605ff14f2310cae3645ae7/packages/wxt/src/core/utils/building/resolve-config.ts#L36
See the failing checks, just fix the type errors and this will be good to go.

Oh I actually did that but I think I removed that by accident before pushing, my bad

Released in v0.19.5


Develop/alex

Kudos, SonarCloud Quality Gate passed!
  0 Bugs   0 Vulnerabilities   0 Security Hotspots   2 Code Smells
 82.1% Coverage  0.0% Duplication

About the code smells:

Replace this "Map.get()" and condition with a call to "Map.computeIfAbsent()". won't work with complex objects where I need to set properties in it
18 IFs out of 15 allowed: This is a logic and not fixable unless I have to move my code to another service class. Should I?


Stop marketing the .app packaging method on osx as official

We have pyinstaller, which does not have any outstanding issue documented, people seem to be using it with success.
We are well aware that the .app method is not a real solution for packaging in its current state, it lacks many features pyinstaller has, and the output also depends on the target system's python.
If pyinstaller is indeed something that should be avoided on osx, I would like to see issues being opened for our repo, documenting how and why packaging with it does not work. Maybe we can find fixes for those problems and resume recommending a real, established packager.

https://github.com/kivy/kivy/issues/1908

@dessant I guess this assigned to you since you think this is solvable with pyinstaller there ws a bounty of 50$ plus people ready to offer 500$, best of luck.

I don't think it is solvable, but I do believe in listing our problems and documenting them.

I do think this is solvable. Here is a proof of concept:
https://www.dropbox.com/s/8q770mccsv57dkp/ogg_test.zip?dl=1
Packaged with pyinstaller using homebrew dependencies.

@cbenhagen does ogg work (can't test)? What was missing on #1908 when packaging?

Yes it does. It plays an ogg file from wikipedia. Hard to tell what went wrong there. But it will be straightforward in the future.

You can have binary clash at any moment if you mix our Kivy.app release and your own dependencies with homebrew. That's what happened on few computer. There is people that actually use Kivy.app and drag&drop, others use brew.
There is no point to remove Kivy.app, not all developers use brew as the only way to package. And it's not because the documentation is not finished that it must be killed, i completely disagree here.
And no, i'm also having trouble to have a correct package with pyinstaller, and it's using me too much time than just copy&paste for fast release to a customer. And my last point: it's more newbie friendly (in the concept). If we are not here yet, it's mostly just a documentation issue, which can be resolved easily.
Let's don't kill the concept.

@cbenhagen did you test the app on another sys than the one you packaged on? The test.app does not work for me. I hear no sound.

ogg playback works for me on 10.10.5, I don't have any relevant libraries installed with brew etc

My system is 10.10.5 too I don't have brew installed. No Sound :/

I don't think we should drop any of the two concepts. They both have their advantages and disadvantages. As @tito said: It's a question of Documentation. I think that is what we should do. Improve it for both ways. Maybe someone even finds a third solution which has its own advantages in some situation.
@akshayaurora yes sure I tested it on several systems. 10.11 and 10.10. Also on two that i have never touched and have no homebrew or gstreamer on them. What OS X version do you have? And what is the output of
ogg_test.app/Contents/MacOS/ogg_test

or
GST_DEBUG=4 ogg_test.app/Contents/MacOS/ogg_test

ok, the ogg file is playing after waiting for 10 seconds,  I was closing the app before that.

by the way this is the the testscript i packaged
#!/usr/bin/env python
from kivy.app import App
from kivy.core.audio import SoundLoader
from kivy.uix.button import Button

def play(*args):
    sound = SoundLoader.load('https://upload.wikimedia.org/wikipedia/commons/c/c8/Example.ogg')
    if sound:
        print("Sound found at %s" % sound.source)
        print("Sound is %.3f seconds" % sound.length)
        sound.play()

class TestApp(App):
    def build(self):
        return Button(text='Hello OGG World', on_release=play)

TestApp().run()

@akshayaurora: there might be a network issue on your or wikipedias side then.

Let's not discuss about the ogg issue here please

@tito I agree, they are both needed dependeing on the use case. The .app method is awesome for quick sharing during development, or deployment in some cases, but as packaging features go, it is in alpha state.
As kivy caters both to hobbists and businesses, it would be good to not label it as official, because it is not there yet.
The other goal of the issue is to trigger new bug reports about pyinstaller on osx, because we seem to discourage people from using it, without having documented reasons (issues that are still open and notes in the packaging docs).

The osx packaging doc has been made more clear, the danger is over and the realms are protected. :princess:


Make CallableMaker internal

I would want to use this trait in most libraries built using amp; it's really useful. Moving it to internal would prevent that 😞

@bwoebi Once we require 7.1, this trait doesn't have any point anymore.

@kelunik Once we require 7.1, every library using Amp will also want to drop use of this trait - if they don't remove it by then, they would anyway end up with legacy artifacts.

@bwoebi The difference is that we need a new major version then.

We anyway should use a new major version when increasing the base PHP version.

@bwoebi Why?

Because we'll use functionality of that new language (a BC break) - which will be the whole point of bumping constraints?

@bwoebi Which is totally fine. Users not meeting the runtime requirement will just get the older version without new features.

 In theory that sounds fine … until some people develop e.g. on an a bit newer version of PHP and push an incompatible build or similar things.
I honestly wouldn't do that.

How is that related?

Even when we require 7.1 we can leave this trait in place… it doesn't hurt anything and provides BC. We can remove it on a major version, whenever that may be.


#14 Include(...) after AsExpandable()

Fixed

Hello @doboczyakos,
Thanks for this PR.
Is it possible that you create a console app which identifies this problem? And make a new PR for this on master.
Then we are sure that this PR does fix the issue.
And is there also some documentation which needs to be updated?

We identified the problem in our enterprise application and tested this fix with a forked package.
Are you sure you want a console application or would it be better to add a new testcase for this?
The only thing you have to document is that .AsExpandable().Include() is working with EF Core from now on... but it uses internal API, there's no other option to fix it, so it can cause build error with future versions of EF Core if they modify this API. Anyway it's the same in all EF Core versions until 6 so I don't expect breaking change.

Are you sure you want a console application or would it be better to add a new testcase for this?
If a unit-test would be possible, that is preferred.

Microsoft.EntityFrameworkCore.Query.Internal is being used since 2016 in LinqKit so I don't think it's something we should be afraid of.
I'm committing a testcase to this PR today

Sorry, I create a new branch for the test to be able to test is with both versions

@doboczyakos, WithExpressionExpanding is not suitable for you?

@sdanyliv, although optionsBuilder.WithExpressionExpanding() works properly with .Include(); however we have several places where we use explicit .AsExpandable() in common code. In these common code we cannot apply optionsBuilder.WithExpressionExpanding(), because we do not have access to the concrete DbContext class there. Still, the common code use .Invoke() heavily, so .AsExpandable() is necessary; and we should not assume that the code that uses it is going to use optionsBuilder.WithExpressionExpanding().
Moreover, the situation now is very fragile, because as soon as a developer writes .AsExpandable().Include() explicitly in the code, then the .Include() behavior will not work, regardless the use of optionsBuilder.WithExpressionExpanding().

You are right. I don‘t know why Include code i so restrictive to IQueryable implementation.

@StefH https://github.com/scottksmith95/LINQKit/pull/165

@StefH , how is the merge of the pull request going? Can we help anything?

@davidnemeti
I'll first merge the unit-test PR and then this one.

What's going on with .netcoreapp 2.1?
"Testhost process exited with error: It was not possible to find any compatible framework version
The framework 'Microsoft.NETCore.App', version '2.1.0' (x64) was not found."

https://github.com/dotnet/core/issues/6640

@doboczyakos
I see.
I'll remove this test and replace it by other frameworks.


[Bug]: Can't submit a ValidatedForm from a modal

Which packages are impacted?

[X] remix-validated-form
[ ] @remix-validated-form/with-zod
[ ] @remix-validated-form/with-yup
[ ] zod-form-data

What version of these packages are you using?

remix-validated-form: 4.6.10

Please provide a link to a minimal reproduction of the issue.
https://github.com/haines/remix-validated-form-submit-from-modal-repro
Steps to Reproduce the Bug or Issue
When a ValidatedForm is submitted by a button in a modal that is unmounted from the DOM on submit, it fails with an uncaught error. The same problem does not exist in Remix's standard Form.

git clone https://github.com/haines/remix-validated-form-submit-from-modal-repro.git
cd remix-validated-form-submit-from-modal-repro
npm install
npm run dev
Open http://localhost:3000
Enter a value in the unvalidated form, click "Save" and "Yes".
See the submitted value logged in the server console, and no error in the browser console.
Enter a value in the validated form, click "Save" and "Yes".
See no value logged in the server console, and an error in the browser console

Uncaught (in promise) Error: Cannot submit a <button> or <input type="submit"> without a <form>
    at getFormSubmissionInfo (node_modules/react-router-dom/dom.ts:196:13)
    at node_modules/react-router-dom/index.tsx:954:48
    at handleSubmit (node_modules/remix-validated-form/src/ValidatedForm.tsx:356:9)

Expected behavior
ValidatedForm behaves the same as Remix's standard Form.
Screenshots or Videos
No response
Platform

OS: macOS
Browser: Chrome
Version: 111.0.5563.64

Additional context
I guess this may be due to async submit. When Remix's Form calls React Router's submit hook, the submitter (the button element) has form set (because the button hasn't been removed from the DOM yet?). When ValidatedForm calls submit, the submitter's form property is null.

This is interesting. It's a little bit related to #117. Like you said, it's because of the async submit.
When I implement this pattern, I usually leave the modal present in the dom and show my loading state on the modal button instead of closing the modal. But both patterns should be considered valid, I think.
I believe useSubmit and fetcher.submit can both accept FormData directly instead of an element, so maybe the solution is to submit the data that we validated rather than the submitter or form elements. I'm not sure if this would miss some edge-cases that can only be handled by submitting the elements though. It could theoretically open us up to behavior that doesn't match the native / no-js behavior.

Could you test this again with v5? I updated when we capture the form data to avoid weird race conditions caused by the async submit. So this might be fixed now.

RVF v6 has been released 🎉
This should now longer be an issue in v6. If it's still a problem in that version, please feel free to open a new issue.
You can find the documentation here and the migration guide here.


how set log_level of fluentbit ?

Describe the bug
installed fluent-operator in only fluent-bit mode，but can not set log_level.
the default log_level is info which can not debug.
To Reproduce
i want set log_level=debug.
Expected behavior
i want set log_level=debug.
Your Environment
- Fluent Operator version: v1.0.0
- Container Runtime: docker
- Operating system: CentOS Linux release 7.5.1804 (Core)
- Kernel version: 3.10.0-862.3.3.el7.x86_64

How did you install fluent operator?
kubectl apply set-up.yaml
What happened?
level=info msg="Fluent bit started"
Fluent Bit v1.8.11

Copyright (C) 2019-2021 The Fluent Bit Authors
Copyright (C) 2015-2018 Treasure Data
Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
https://fluentbit.io

Your Error Log
i want set log_level=debug.

Additional context
i want set log_level=debug.

In fluentbit its configuration is this : https://docs.fluentbit.io/manual/v/1.8/pipeline/inputs/syslog#fluent-bit-configuration
You can configure these parameters in the fluent-operator:
https://github.com/fluent/fluent-operator/blob/master/apis/fluentbit/v1alpha2/clusterfluentbitconfig_types.go#L35
like this
spec:
  service:
    parsersFile: parsers.conf
    logLevel : debug
....

oh , tks very much.
i set log_Level: DEBUG，not work.


UserAgent setting is being ignored in CONNECT requests.

I am trying to get an URL through a proxy and with a custom user agent:
    ro := &grequests.RequestOptions{
      RequestTimeout: s.httpTimeout,
      UserAgent:      uaString,
      Proxies: map[string]*url.URL{
        "http":  proxyOne,
        "https": proxyTwo,
      },
    }
    resp, err := grequests.Get("http://someurl.com", ro)

But if I look at a network traffic dump - I see two types of requests:

GET requests with my custom UA.
CONNECT requests with Go-http-client/1.1 UA.

Could you please fix UA handling in CONNECT calls? Thanks.

because you use go program connect proxy, but you doesn't set the user-agent for proxy server.
so you get the bug, I spent 20 hours to fix this.  you could read the golang/net source code, "defaultUserAgent" ,  search this code, you will find why. It's not a bug.

socket connect ssl server will use default client user agent.


[Feature Request] Add only option to external

Feature Use Case
At now, the only option passed into node-resolve plugin will not add corresponding external to the rollup config/options object, so, when we do build, there will be many warnings like "Treating [module] as external dependency"(https://rollupjs.org/guide/en/#warning-treating-module-as-external-dependency) which tell us to add modules below to the external option. Although that's not a problem but indeed is a little annoying so I think we should fix it.
Feature Proposal
Add only option to the rollup external option

From the docs:

Set to an array of strings and/or regexps to lock the module search
to modules that match at least one entry. Modules not matching any
entry will be marked as external

With that in mind, this could actually be considered a bug. The IMO correct way to do this, though, would be to return false from the resolveId hook instead of patching the options: https://rollupjs.org/guide/en/#resolveid
This should prevent warnings emitted by Rollup as well.

Thanks for your response. The doubt here is that if I add a extra option(like resolveId you said above), then IMO there is no need to add the only option, because when I add a only option, I want to tell node-resolve treat them as dependencies and all others as external, this should be a default behavior.
If we have to add extra option to archive this, I think maybe I can just only use the external option of rollup rather than use the only option of node-resolve. So, given this option has been provided by node-resolve, I think maybe we can "fix" it?
By the way, the case I encountered is when the only is '[/project-name/src/i], seems something like @babel/runtime-corejs3` will emit the warning, hope this info helps!

I think you misunderstood my response, I am talking about how to implement it. resolveId is not an option but a plugin hook that is already used by this plugin to do its thing. Please check the link I added. This is meant for someone who wants to fix this.

sorry, I didn't look up that carefully, now I get what you mean, thanks!

@lukastaegert does this need to be transferred to rollup/plugins?

Closing for now. Please re-create and reference this issue in https://github.com/rollup/plugins if it needs to be discussed more.


Puts code in chat instead of editor

Describe the bug
once in a while when generating code the bot continues in chat instead of implementing the actual code
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-htid5y
Steps to reproduce
visit: https://bolt.new/~/sb1-htid5y
start generating code.
it's not always updating code
Expected behavior
When the ai is generating code i expect the ai to update the files in the editor and not prompt out the ocde in the chat window
Screen Recording / Screenshot
No response
Platform
Browser name = Firefox
Full version = 132.0
Major version = 132
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:132.0) Gecko/20100101 Firefox/132.0
performance.memory = undefined
Username = lassecapel
Chat ID = 6b885a983a21

Additional context
No response

This was happening to me yesterday too

Appreciate the feedback! Prompting LLMs to achieve the desired behavior is an area of active research. Some helpful insights on how to use Bolt most effectively while maximizing token efficiency can be found here. At times, the model does not fully understand the request and manual intervention may be required. Something else that might help is if you select a block of text in a file in the Bolt code editor and then click "Ask Bolt" the AI's focus will be directed to that specific section of code. We appreciate your patience as improvements to continue to be made towards consistently achieving desired model behavior!


Suggestion: echo config data back to console to allow for self-troubleshooting

A customer filed an issue through another channel, reporting that proxy config wasn't being picked up. It turned out to be misbehavior by Ansible - the hostname was being written down with quotes, making it an invalid hostname. If we had echo'd back the exact data we saw on ./config, the customer would likely have seen the problem sooner and not had to reach out to us for troubleshooting.
For consideration: in this specific instance, we also could have validated that it looked like a correctly-formatted hostname. I have some trouble with this, though - we catch the occasional stray issue like this one, at the risk of having incorrect validation logic that blocks someone else. The regex or validator could be fairly complex -- having to account for internationalized domains, IPv4 and IPv6 addresses, and probably more I'm not thinking of, while also being likely to catch an incorrect hostname.

I'll take a look at dumping the config data to stdout

Are we sure we want to do that?  The user could have dumped it to stdout for troubleshooting (use the automation system itself to troubleshoot the workflow).  Instead, having it always dumped out is taking time, perf, logs for everyone.  What else will we start dumping out?  For troubleshooting it could effectively become any machine / tool config state.

After spending a lot of time today looking through the code, I've come to a similar conclusion. Dumping out all the config data seems difficult to maintain as not all config information is kept in the same object  along with the performance implications you mentioned.
Something I have started looking down that path of, is can we let the user know on stdout that there is something interesting in the diag logs that they should take a look at. My initial approach was that if a Warning, Error or Critical message was written to Trace, we should mention something in the console output.
Thoughts?

Since it's in the diagnostic log, I can't push too hard to also dump it someplace else. Thanks for taking a look.

(Forgot to add - but the warning about "hey, go look at the diagnostics" is a good one.)


Update http dependancy to the latest version

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Use case
Your dependency is still relying on http: ^0.13.3. rive ^0.11.4 is still lagging behind
[bus_application_flutter] flutter pub get
Resolving dependencies...
Because rive >=0.7.17 depends on http ^0.13.3 and bus_application_flutter depends on http ^1.010, rive >=0.7.17 is forbidden.
So, because bus_application_flutter depends on rive ^0.11.4, version solving failed.
exit code 1
Proposal
Update your http dependency for rive_common: 0.1.0 and rive: ^0.11.4 to the latest version http ^1.1.0

This is not a flutter issue. This is from the rive package. This has been reported on their repo. See https://github.com/rive-app/rive-flutter/issues/321#issuecomment-1570032172
Closing from here as this is not a flutter issue.
Thank you


[MBL-1392] Add checkout Id to create payment intent call

📲 What
Added the checkout ID to the create checkout mutation
🤔 Why
Backend wanted it to track data and prevent multiple payments
🛠 How
Using the updated schema, added the field and provided it in the viewmodel
👀 See
{"operationName":"CreatePaymentIntent","variables":{"projectId":"UHJvamVjdC0xMjUxNDY0MjA5","amount":"20.0","paymentIntentContext":"POST_CAMPAIGN_CHECKOUT","checkoutId":"Q2hlY2tvdXQtMTk4MzM4MDI3"}
{"data":{"createPaymentIntent":{"__typename":"CreatePaymentIntentPayload","clientSecret":"pi_3PEGmK4VvJ2PtfhK0HfDKtmi_secret_J59hZt27pz0a8LU9DzjULYW4i"}}}
📋 QA
Go through the late pledge flow and confirm checkout works as expected and the new field is in the logs for the create checkout call
Story 📖
MBL-1392

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

Project coverage is 67.38%. Comparing base (89abc71) to head (c412d9e).
Report is 1 commits behind head on master.

Files
Patch %
Lines

...wmodels/projectpage/LatePledgeCheckoutViewModel.kt
0.00%
13 Missing :warning:

...com/kickstarter/models/CreatePaymentIntentInput.kt
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##             master    #2035      +/-   ##
============================================
- Coverage     67.39%   67.38%   -0.02%
- Complexity     2067     2068       +1
============================================
  Files           353      353
  Lines         21472    21478       +6
  Branches       3029     3030       +1
============================================
+ Hits          14471    14472       +1
- Misses         5389     5395       +6
+ Partials       1612     1611       -1

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


No optimized fast float implementation for Logistic

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
tf 2.15
Custom code
No
OS platform and distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
Commit https://gitlab.com/libeigen/eigen/-/commit/a30ecb7221a46824b85cad5f9016efe6e5871d69 of the third-party Eigen library disabled the fast float implementation of the Logistic (or sigmoid if you like) operator for most (all?) Tensorflow Lite backends.
The fallout of this is more severe than just the speed impact: relying on overflow behavior of exp(x) for large x, as used in the generic fallback implementation, triggers a bug on our embedded platform, causing glitches where logistic(x) in some cases becomes 0 instead of 1 for large x (around 88.9).
I would propose to bump the Eigen dependency if this gets fixed upstream (see also https://gitlab.com/libeigen/eigen/-/merge_requests/1576), as this effectively fixes the issue.
Standalone code to reproduce the issue
N/A

Relevant log output
No response

@dieterd-sentea Could you please update your build process to use the new Eigen version and let us know?
Thank you!

Hi @sushreebarsa,
I can confirm that TFLite built with the newest Eigen version, with https://gitlab.com/libeigen/eigen/-/merge_requests/1576 merged, does not exhibit the issue.
The workaround that we use at the moment, until the Eigen dependency in this repository gets bumped, is the following patch:
diff --git a/tensorflow/lite/tools/cmake/modules/eigen.cmake b/tensorflow/lite/tools/cmake/modules/eigen.cmake
index 93a63d280d8..f6b14b562b7 100644
--- a/tensorflow/lite/tools/cmake/modules/eigen.cmake
+++ b/tensorflow/lite/tools/cmake/modules/eigen.cmake
@@ -99,4 +99,5 @@ set(EIGEN_TEST_SYCL OFF CACHE BOOL "Disable Sycl test")
 set(EIGEN_SYCL_TRISYCL OFF CACHE BOOL "Disable triSYCL test")
 # Make sure only MPL2.0 or more permissively licensed code is included.
 add_compile_definitions(EIGEN_MPL2_ONLY)
+add_compile_definitions(EIGEN_GPU_CC)
 add_subdirectory("\${eigen_SOURCE_DIR}" "\${eigen_BINARY_DIR}")

Of course, this abuses the fact that EIGEN_GPU_CC is only relevant to enable the fast float logistic implementation again in the buggy Eigen versions (and is used nowhere else). In the newest Eigen version, this workaround is not needed anymore.

Correction on previous message: I have not explicitly tested if latest Eigen master (which might contain other unreleated changes) is working for us. I'll find out and let you know.

I can confirm that we experience no issues on tf-nightly with the following patch, which updates Eigen to latest master https://gitlab.com/libeigen/eigen/-/commit/b2c9ba2beef4b5fd61513d73911c678e93c8dd9d:
diff --git a/tensorflow/lite/tools/cmake/modules/eigen.cmake b/tensorflow/lite/tools/cmake/modules/eigen.cmake
index 1bb203388a0..f6cc23e578f 100644
--- a/tensorflow/lite/tools/cmake/modules/eigen.cmake
+++ b/tensorflow/lite/tools/cmake/modules/eigen.cmake
@@ -23,7 +23,7 @@ OverridableFetchContent_Declare(
   eigen
   GIT_REPOSITORY https://gitlab.com/libeigen/eigen.git
   # Sync with tensorflow/third_party/eigen3/workspace.bzl
-  GIT_TAG aa6964bf3a34fd607837dd8123bc42465185c4f8
+  GIT_TAG b2c9ba2beef4b5fd61513d73911c678e93c8dd9d
   # It's not currently (cmake 3.17) possible to shallow clone with a GIT TAG
   # as cmake attempts to git checkout the commit hash after the clone
   # which doesn't work as it's a shallow clone hence a different commit hash.
diff --git a/third_party/eigen3/workspace.bzl b/third_party/eigen3/workspace.bzl
index 027454e46dd..7065b289e04 100644
--- a/third_party/eigen3/workspace.bzl
+++ b/third_party/eigen3/workspace.bzl
@@ -7,8 +7,8 @@ def repo():

     # Attention: tools parse and update these lines.
     # LINT.IfChange
-    EIGEN_COMMIT = "aa6964bf3a34fd607837dd8123bc42465185c4f8"
-    EIGEN_SHA256 = "35ba771e30c735a4215ed784d7e032086cf89fe6622dce4d793c45dd74373362"
+    EIGEN_COMMIT = "b2c9ba2beef4b5fd61513d73911c678e93c8dd9d"
+    EIGEN_SHA256 = "9e0dbce1464f8e05f9e4ea66c0a92850c4aade71c330130f8960f3ab3592d5c4"
     # LINT.ThenChange(//tensorflow/lite/tools/cmake/modules/eigen.cmake)

     tf_http_archive(
diff --git a/third_party/xla/third_party/tsl/third_party/eigen3/workspace.bzl b/third_party/xla/third_party/tsl/third_party/eigen3/workspace.bzl
index 027454e46dd..7065b289e04 100644
--- a/third_party/xla/third_party/tsl/third_party/eigen3/workspace.bzl
+++ b/third_party/xla/third_party/tsl/third_party/eigen3/workspace.bzl
@@ -7,8 +7,8 @@ def repo():

     # Attention: tools parse and update these lines.
     # LINT.IfChange
-    EIGEN_COMMIT = "aa6964bf3a34fd607837dd8123bc42465185c4f8"
-    EIGEN_SHA256 = "35ba771e30c735a4215ed784d7e032086cf89fe6622dce4d793c45dd74373362"
+    EIGEN_COMMIT = "b2c9ba2beef4b5fd61513d73911c678e93c8dd9d"
+    EIGEN_SHA256 = "9e0dbce1464f8e05f9e4ea66c0a92850c4aade71c330130f8960f3ab3592d5c4"
     # LINT.ThenChange(//tensorflow/lite/tools/cmake/modules/eigen.cmake)

     tf_http_archive(

Funnily enough, the overflow issue that we observed does not appear on tf-nightly (but does occur on v2.14.0), but this is orthogonal to the this issue which is about the fast float implementation for Logistic.

So I've investigated this a bit further and we observe a nice speedup with the above patch (up to 10% for a certain model that contains a sigmoid layer).
Note btw that we do not use XNNPACK delegate, i.e., we configure the project with cmake -DTFLITE_ENABLE_XNNPACK=OFF . This is important to note, as otherwise float32 logistic goes through XNNPACK instead of Eigen, as can be seen here: https://github.com/tensorflow/tensorflow/blob/ade45358646f2c7ed2ce6792d0234d83ad2dca3f/tensorflow/lite/kernels/activations.cc#L1130

Hi @dieterd-sentea, can we say that this is resolved now on the master branch at least? Let me know if you disagree or if there is any other action needed from our side. Thanks.

@pkgoogle LGTM


hub meta

Change-type: patch
Signed-off-by: Phil Wilson<EMAIL_ADDRESS>

@balena-ci I self-certify!

@balena-ci I self-certify!


https://issues.jboss.org/browse/WFCORE-697 CLI does not handle paths …

…with a value of '/'
Thanks,
Alexey

Linux Build 1844 is now running using a merge of a9cb324667529d0e062503ec6348fe76c47445d2

Windows Build 1394 is now running using a merge of a9cb324667529d0e062503ec6348fe76c47445d2

Core - Full Integration Build 990 is now running using a merge of a9cb324667529d0e062503ec6348fe76c47445d2

Windows Build 1394 outcome was SUCCESS using a merge of a9cb324667529d0e062503ec6348fe76c47445d2
Summary: Tests passed: 3108, ignored: 69 Build time: 0:20:16

Linux Build 1844 outcome was SUCCESS using a merge of a9cb324667529d0e062503ec6348fe76c47445d2
Summary: Tests passed: 3108, ignored: 69 Build time: 0:22:58

Core - Full Integration Build 990 outcome was FAILURE using a merge of a9cb324667529d0e062503ec6348fe76c47445d2
Summary: Tests failed: 1 (1 new), passed: 2861, ignored: 374, muted: 1 Build time: 0:52:54
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.client.descriptor.EJBClientDescriptorTestCase.testEJBClientContextWithNoReceiversConfiguration: <no details avaliable>

retest this please!

Windows Build 1396 is now running using a merge of a9cb324667529d0e062503ec6348fe76c47445d2

Core - Full Integration Build 992 is now running using a merge of a9cb324667529d0e062503ec6348fe76c47445d2

Linux Build 1846 is now running using a merge of a9cb324667529d0e062503ec6348fe76c47445d2

Linux Build 1846 outcome was SUCCESS using a merge of a9cb324667529d0e062503ec6348fe76c47445d2
Summary: Tests passed: 3108, ignored: 69 Build time: 0:23:08

Windows Build 1396 outcome was FAILURE using a merge of a9cb324667529d0e062503ec6348fe76c47445d2
Summary: Tests failed: 7 (7 new), passed: 3101, ignored: 69 Build time: 0:23:31
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.manualmode.management.cli.CustomVaultInCLITestCase.testWrongVaultPassword: <no details avaliable>

org.jboss.as.test.manualmode.management.cli.CustomVaultInCLITestCase.testNonExistingVaultPassword: <no details avaliable>

org.jboss.as.test.manualmode.management.cli.CustomVaultInCLITestCase.testRightVaultPassword: <no details avaliable>

org.jboss.as.test.manualmode.vault.CustomVaultInModuleTestCase: <no details avaliable>

org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase.testWrongVaultPassword: <no details avaliable>

org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase.testRightVaultPassword: <no details avaliable>

org.wildfly.core.test.standalone.mgmt.HTTPSConnectionWithCLITestCase.testTrustedCLICertificate: <no details avaliable>

Core - Full Integration Build 992 outcome was SUCCESS using a merge of a9cb324667529d0e062503ec6348fe76c47445d2
Summary: Tests passed: 2863, ignored: 374 Build time: 0:52:32


refactor: move HD code from CWallet to LegacyScriptPubKeyMan

Issue being fixed or feature implemented
During backport bitcoin#17261 significant part of HD chain has been forgotten in CWallet due to our own implementation.
This PR do not change behaviour of HD wallets, it's just refactoring.
What was done?
This PR refactor HD wallets implementation:

key related stuff is moved from CWallet to LegacyScriptPubKeyMan (to follow-up bitcoin#17261)
refactored duplicated code between hdChain and hdCryptedChain
modules hdchain and bip39 related moved to wallet/ module

How Has This Been Tested?
Run unit/functional tests
Breaking Changes
N/A
Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation
[x] I have assigned this pull request to a milestone

@knst knst force-pushed the hd-1 branch from d0f309f to b5f4411

rebased to be on top of post-merged master to develop


1.x: show instructions to use 2.x when targeting 242

Describe the need of your request
Targeting 242 requires IntelliJ Platform Gradle Plugin 2.x
trying to use 1.x will fail with unclear errors
Proposed solution
Show clear instructions and fail the build
Alternatives you've considered
No response
Additional context
No response

Imo, a better approach would be to not have such an aggressive cutover to the new version in the first place. I see several problems:
Confusing messaging
The documentation has the following disconnected statements:

IntelliJ Platform Gradle Plugin 2.x (Beta) (currently in Early Access Preview) is going to replace this plugin in the future. Please note that production usage is currently not recommended yet.
Gradle: Minimum Plugin Versions

When targeting 2024.2 or later, IntelliJ Platform Gradle Plugin 2.x (Beta) is required.
When targeting 2022.3 or later, Gradle IntelliJ Plugin version 1.10.1 or higher is required (current: 1.17.3)

Analysis

It's an early access preview, but also tagged as beta
It's not recommended for production yet, but it will be required to target the next production release.

Open questions

What about 2024.2 makes it so different that it can't be supported in 1.x? Did something dramatically change for 2024.2?
When will 2.x be recommended for production use?

Why is the only path for supporting 2024.2 to use an early access preview that isn't recommended for production yet?

Is gradle-intellij-plugin (1.x) now considered abandonware? There was never any kind of announcement warning of this if so and the above requirements seem to suggest this.

Targeting 242 requires IntelliJ Platform Gradle Plugin 2.x
trying to use 1.x will fail with unclear errors

Agreed. It took me two and a half hours to figure it out. The problem is that I didn't even think to upgrade to newer version of 1.x 😕 I've just stumbled upon the 2.x requirement during the ordeal (#1638). Meaning that additional instructions in the output of 1.x wouldn't have helped me, unfortunately.

Please stick to the topic of this issue, a simple, unavoidable technical requirement to use 2.x when targeting 24.2 releases. Your feedback on 2.x is welcome in separate GH issues or join the Slack channel.

Lemme open a separate issue for tracking the high-level concerns

Fixed in https://github.com/JetBrains/intellij-platform-gradle-plugin/releases/tag/v1.17.4


Access to full GitLab.com database for analytics

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/55
Originally created by @joshlambert on 2018-06-06 01:33:57

The product team (@JobV) has stated it is a critical short term need have access to the full GitLab.com database to run analytics.
We are working on an ELT to solve this, but proper pseudonymization is hard and we'd like to iterate on low-risk groups prior to pulling larger data sets, due to the high sensitivity of the content. The work and general plan is outlined here: https://gitlab.com/meltano/meltano/issues/80
This issue is to explore alternative methods to solve the immediate need, while we gain confidence and maturity with the pseudonymization process.
Proposal

Set up a new GCP project, GCS bucket, bastion host and Cloud SQL instance.
Enable full statement logging on Cloud SQL, and audit logs on the bastion host as well, to stackdriver
Enable SSH access to the bastion host, for specific whitelisted users (no admin access)
Set up a nightly full GitLab.com ELT dump, written into the GCS bucket
Create a cron job on the bastion host to import from the GCS bucket to the Cloud SQL instance
Access to Cloud SQL could be through a simple console SQL client
If approved by security and as a further iteration, we could enable SSH port forwarding and run a VNC server, to allow a graphical SQL client to improve ease of use.

View 13 previous comments from the original issue on GitLab


The SymbolPackageFormat parameter is not documented

The parameter -SymbolPackageFormat used in the sample code is not documented.

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

ID: 2e18eb26-7a73-5e48-abd0-3d53476c6f91
Version Independent ID: 5469de95-4b00-2fbd-f3c0-1cde036f3c7f
Content: NuGet CLI pack command
Content Source: docs/tools/cli-ref-pack.md
Product: nuget
GitHub Login: @karann-msft
Microsoft Alias: karann

Sorry about that! I went ahead and added some documentation here, please let me know what you think.

@jozefizso thanks for catching that, @loic-sharma - thanks for fixing that.
The fix has now been merged.


Is there an option to force the conversion?

Is there an option for: call jukit#convert#notebook_convert() or call jukit#convert#notebook_convert("%") to set default answer for the next two prompts: Do you want to overwrite? And do you want to open?

Currently not, but I can easily add an option to do so. I'll most likely add it sometime this weekend.

You can now configure default options via the variables g:jukit_convert_open_default and g:jukit_convert_overwrite_default - see relevant section in readme

Thank you so very much ❤ , you have made my 🐍 python-dev experience so much better. I'm learning it through Udacity,
and it's heavily based on Jupiter NoteBooks web interface. As a (n)Vim user you can understand the frustration, so I
deeply 🙇 thank you!

Thank you, I'm glad you like it! :)


Add ban/unban commands

Fix #172: Add feature for admin to ban/unban user from playing the game.
Force join still work as normal if needed.

Please don't merge at this time, will do some enhancements in this PR


treat empty string as None for Option<?>

In case of
let r: Option<Any> = serde_json::from_str("").unwrap();
Why not return None? Currently it's an error.
I'm using actix-web, and there's an optional request body in json format. I'd like the Json<Option> to return None rather than an error when the body is empty.

Thanks for the suggestion! I would prefer not to make this change. Empty is not a valid JSON document and serde_json only deserializes input that is valid JSON. It would be better if you could implement this logic in your application, by checking whether the string is empty before deserializing it.


style-guide: Massage grammar for clarity.

Remove 'ever', which reads awkwardly.
Add commas and replace pronoun contraction for clarity.

Nice, thanks!


Add button to save peer address as a saved peer

Or maybe call it peer profile, or something like that.

https://github.com/yzernik/squeaknode/pull/1365


No definition about variable 'activations' used for getting heatmap and mask

Hi, I noticed that the variable 'activations' doesn't seem to be defined here. Could you update the code? Thanks!

Thank you for raising this issue. I have updated the trainer.py file. Please check if it works now.

Thanks! It works for me.
What's more, I'm curious why there is an img_tensor in addition to image_tensor here? In fact, the key of self.processor.image_processor.preprocess(image, return_tensors='pt') only has 'pixel_values' but no 'pixel'.
If I use img_tensor = image_tensor, then an error will be reported when saving ‘image.png’ because the dimension is (3, 224, 224). After I modify img_tensor to (224, 224, 3), the saved image below does not seem correct.

And at line 525, I guess we should compsite image and mask_pixels rather than mask?

In fact, 'img_tensor' and 'image_tensor' are not the same. The pixel key is manually added, to get image tensors before being rescaled and normalized. Please replace transformers/models/blip/image_processing_blip.py in your own python libary with src/image_processing_blip.py, a newly uploaded file.

Hi, @opanhw, thanks for your efforts! Now the code works fine.
However, I hope the code could be better. For example, self.args.preparation_path and self.cal_activations are not defined in src/trainer.py and open_source_model/LLaVA/llava_llama.py respectively. And some python packages are not listed in requirements.txt. I spent some effort to fix them while running the code.
Thanks again！