Add property wrapper-based model definitions

This PR currently has the implementation of this but no tests. I've been testing it by modifying the existing test suite to use the new declarations and disabling all the tests which aren't applicable, but that's not a great solution so I've started on a new test suite. I figure that we can talk about the name and review the implementation while that's in progress.
Currently the property wrapper is named @Managed. I don't like this name very much because it's only somewhat aligned with how we're currently using the word "managed". We have managed and unmanaged objects which refers to objects in a Realm and standalone objects which aren't in a Realm, and while I'm not quite sure what "unmanaged properties" would refer to it's clearly not an analogue of unmanaged objects.
Some other ideas I had that I don't like:

@ManagedProperty: all the downsides of Managed but longer and worse.
@Property: already taken for something different.
@realm: too clever? Results in really nice looking class definitions but having both Realm and realm as types in the API is very confusing.
@RealmProperty: awfully long.
@Persisted: we very thoroughly ripped out the "persisted" term from everything and it'd be weird to use it just here.
@Field: not really a term used in Swift.
@R or @P: Too short?
@ℜ or @ℜ𝔢𝖆𝖑𝖒: I hope the problem is obvious

Things left to do:

[ ] Bikeshed the name
[ ] Add a new test suite for this
[ ] Do final perf testing to verify that it's still faster and check if @inlineable is actually doing anything
[ ] Changelog entry etc.
[ ] Do we actually need to be creating managed accessor subclasses? Could save a little bit of memory and startup time if not.

Not sure if my opinion weighs a lot considering I'm not a Swift developer, but I do find Persisted to be a more appropriate name than Managed. On one hand, managing a property is not really a thing, and then what does having a "managed" property on an "unmanaged" object mean.
Persisted is reasonably straightforward to understand and is a good juxtaposition to the "ignored" terminology we are currently using. Seeing a swift model where half the properties are annotated with @Persisted makes it immediately clear that those will be stored in the database, while the rest will be ignored.
@RealmProperty could also work despite the length - it does seem in line with the length of some of the SwiftUI property wrappers. @RealmValue is tangentially shorter but might be confusing in combination to AnyRealmValue which I believe is what the Swift version of Core's Mixed is called.

Persisted does feel like the option I have the weakest argument against.
It's a pretty silly criterion, but length-wise it'd be nice to have something shorter than @objc dynamic so that updating existing models to this feels like it's getting less verbose rather than the hot new thing being more clunky than what it's replacing.

Regarding the property wrapper name:

Of the existing options, @realm is the best.

As a longtime Apple dev, "managed"-anything simply screams "Core Data". A large portion of folks new to Realm are probably coming from a decade+ of Core Data, so this word is loaded. I'd avoid it.


Sprint 12/PI - 138] Logger Package

Jira Link: https://ichiro-its.atlassian.net/browse/PI-138
Description
Write Program in C++
Save data in JSON format
Use verbosity level
Type of Change

[ ] Bugfix
[ ] Enhancement
[x] New feature
[ ] Breaking change (fix or feature that would cause the existing functionality to not work as expected)

How Has This Been Tested?

[ ] New unit tests added.
[x] Manual tested.

Checklist:

[x] Using Branch Name Convention

feature/JIRA-ID-SHORT-DESCRIPTION if has a JIRA ticket
enhancement/SHORT-DESCRIPTION if has/has no JIRA ticket and contain enhancement
hotfix/SHORT-DESCRIPTION if the change doesn't need to be tested (urgent)

[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have made the documentation for the corresponding changes.

add GitHub Action, and follow CMakeLists and package.xml from other project

.vscode should be added to the .gitignore

I think adding the gh action in this PR won't do anything, it needs to be on the master branch instead, you can add it via another PR or directly add it to master

@azharanas17 https://github.com/ichiro-its/kiroku/actions

the check is failed @azharanas17

the check is failed @azharanas17


howto gpt-4-32k ?

This project rocks !!!

You can use gpt --config to permanently set a different model or gpt --model gpt-4-32k "your prompt here" to do it for one-off requests.
This requires your OpenAI account to have been granted access, though (I don't have yet). Let me know if any issues.


HIVE-27549 : Backport of HIVE-22219 to branch-3

JIRA link : https://issues.apache.org/jira/browse/HIVE-27549

Taken care of https://github.com/apache/hive/pull/4530


Generate mock for external library

Hi, I am wondering if it's possible to generates mock for external library, if it's possible how to do it ?

In some cases, I used type aliases for this use case like this:
package myreader

import "io"

//go:generate moq -out reader_mock.go . Reader

type Reader = io.Reader

thanks @breml - another option is to copy the interface into your own project. This isn't a hack per se, some people like to do this anyway as it allows them to provide multiple implementations of something in their project.


fixed issue #118

Fixed issue with latest boost (#118)
Fixed compilation warnings

@ksergey This works on my environment (gcc 9.4.0, boost 1.77.0)
Thanks


[l10n] Unlocalized strings in Preview > View document source in Google Drive

Description
Unlocalized "View document source" and "Copy" strings in Preview > View document source in Google Drive.
To Reproduce
Steps to reproduce the behavior:

Install AEM sidekick extension to Chrome browser https://chrome.google.com/webstore/detail/aem-sidekick/ccfggkjabjahcjoljmgmklhpaccedipo
Go to project folder in Google Drive
Right Click on extension icon > Add this project
Left click on extension icon
Select any word  document > Preview > OK
Copy Preview URL and follow the link
Right click on extension icon > View document source

Expected behavior
Strings are localized:
View document source
Copy
Additional context
"View document source" is localized in Aladdin.
"Copy" is not present in Aladdin.
Screenshots

"Copy" is still unlocalized. though string in localized in Aladdin


DNS not working on all networks

I have been in some networks were the DNS is not working properly. When I use the hostname it can not find it but with the IP it is accessible. I assume that it does not always use the DNS from the network but from google. Can this be?

ConnectBot uses the system's resovler.


Write script to generate signing certs

Write scripts to generate signing certs for their respective binaries:

macosx64
macosarm64
mingwx64
mingwx86

Using https://github.com/achow101/signapple for macOS codesigning
Using https://github.com/mtrojnar/osslsigncode for windows codesigning
See https://github.com/05nelsonm/kmp-tor-binary/issues/66#issuecomment-1472234445
See https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md#codesigning

See https://github.com/indygreg/PyOxidizer/issues/681#issuecomment-1484062375


Re-Jailbreak is impossible

After reboot dopamine crashs and my phone start to showing a black screen with no response and I forced to reboot again only by power buttons
Dopamine works only when I delete environment

I have find the cause of crash
( dynamicpeninsula ) tweak is the cause of crash
Before dopamine get reboot userspace I've closed it and open filza ( via trollstore ) and tried to delete dynamicpeninsula's dylibs and then I reboot userspace and issue fixed

Its a simple solution in the future, hold volume up while jailbreaking to enter safemode then disable or remove the bad tweak


Add whatsapp share button

I'll probably make a PR to add this feature. Should I do it from your dev branch? @MurhafSousli

@jcao02 yupp it's fine 👍

@MurhafSousli the branch doesn't seem to be stable right now. I get an error when compiling with angular-cli:
ERROR in Error encountered resolving symbol values statically. Could not resolve ng2-sharebuttons relative to ...

Is it a problem if I use you master branch for the PR?

@jcao02 in root dir, do gulp build then gulp link then gulp demo, ofcourse don't forget to npm install in demo first

@jcao02 in case it didn't work for you, copy src to demo/src/share and import from there temporary, but don't include these changes in the PR

@jcao02 It seems that whatsapp button is not working in 2.0.0@beta, have you tried it?

Yes. I'm using this package while you release the last version. The button only works from a smartphone, though (The link opens the native app)

This need to be fixed for the web too


Jumeg v2.0 compatible with MNE 0.15.

The changes in this PR includes the following latest updates by @fboers :

new epocher classes.
modifications to jumeg filter.
preprocbatch - batch preprocessing utilities with epocher and other related base classes.
Modified - jumeg_export_4D_to_fif.pl
Updated jumeg template.
Updated - jumeg_merge_meeg.py to combine EEG data from Brainvision recorder to MEG.

The above changes are compatible with MNE 0.15, but some of the older modules still use pre MNE 0.15 filter APIs and need to be updated.
Thanks @fboers , if you could also include some examples on how to use the meeg merger and epocher classes under jumeg/examples that would be great.

@fboers , also, do we still need the jumeg/jumeg_preproc_data.py file or are the functions now included under preprocbatch?

jumeg/jumeg_preproc_data.py  -> do not need it


Create some examples on the GitHub Wiki

As a newcomer, it's very difficult to figure out what this framework can do. That's why I'd love to see some examples listed on the GitHub wiki.
Currently, the README file only shows the Maven dependencies, which plays the role of an Instalation Guide. Check out how I designed the documentation for FlexyPool to get a better picture of what I'm talking about.

Thanks for the feedback Vlad. What a coincidence, I am working on exactly that right at this moment ^^
Hope you can give me some more feedback when I add the first steps 😄

Of course. Looking forward to reading more about this framework.

@vladmihalcea Have you found the ASCII doc in the repository? At least for CTE queries there is quite some information there. For EntityViews there is a bit as well. Obviously it could use a lot more examples, but from your description it seems you haven't found this documentation yet. The documentation is stored in the repository https://github.com/Blazebit/blaze-persistence/tree/master/documentation/src/main/asciidoc . I assume further amendments to the documentation will also go there. You can also look at the issues labeled as question.

I haven't noticed it. Very interesting that you offer support for CTE. That's really great! Does it support Recursive CTE as well?

Yes it does! See for example this testcase.


pnpm installation - Cannot find sharp module in Alpine Linux container

Hi!
I'm getting Cannot find module '../build/Release/sharp-linuxmusl-x64.node' exception when I try to use sharp. All installation questions are answered below. First, my description of the issue:
My setup:

using pnpm
I run my pnpm i command in Ubuntu in WSL
My Astro app runs in an Alpine Linux container - specifically based on node:21-alpine. My local directory is mounted to the container.

Everything is working okay, if I switch the base image form node:21-alpine to node:21. I can't get Sharp to work in Alpine Linux, even though I've configured the supportedArchitectures:
  "pnpm": {
    "supportedArchitectures": {
      "libc": [
        "glibc",
        "musl"
      ]
    }
  }

and Vite build options:
rollupOptions: {
   external: ['sharp'],
}

I've tried running:

rm pnpm-lock.yaml
sudo rm -rf node_modules
pnpm store prune
pnpm i --force
docker compose up --build astroapp

But I'm still getting the Cannot find module '../build/Release/sharp-linuxmusl-x64.node' error.
I suspect that the error is in sharp rather than in pnpm, because during pnpm i --force, I can see that some musl packages are being downloaded:
 WARN  using --force I sure hope you know what you are doing
Downloading registry.npmjs.org/typescript/5.4.3: 5.82 MB/5.82 MB, done
Progress: resolved 213, reused 72, downloaded 120, added 0
Downloading<EMAIL_ADDRESS>6.40 MB/6.40 MB, done
Downloading<EMAIL_ADDRESS>6.21 MB/6.21 MB, done
Downloading<EMAIL_ADDRESS>7.10 MB/7.10 MB, done
Downloading<EMAIL_ADDRESS>7.06 MB/7.06 MB, done
Downloading<EMAIL_ADDRESS>7.20 MB/7.20 MB, done
Downloading<EMAIL_ADDRESS>8.36 MB/8.36 MB, done
Downloading<EMAIL_ADDRESS>7.07 MB/7.07 MB, done
Downloading<EMAIL_ADDRESS>8.40 MB/8.40 MB, done
Downloading<EMAIL_ADDRESS>7.02 MB/7.02 MB, done
Progress: resolved 485, reused 172, downloaded 291, added 0

The error occurs when Astro tries to load sharp:
sharpImport = (await import("sharp")).default;

It throws the Cannot find module '../build/Release/sharp-linuxmusl-x64.node' exception.

Possible install-time or require-time problem

[x] I have read and understood all of the documentation relating to installation.
[x] I have searched for known bugs relating to this problem in my choice of package manager.

Are you using the latest version of sharp?

[x] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.

[x] I am using Node.js with a version that satisfies ^18.17.0 || ^20.3.0 || >=21.0.0
[ ] I am using Deno
[ ] I am using Bun

I've tried Node 20.12.0 and 21.7.1. Same issue.
Are you using a supported package manager and installing optional dependencies?

[ ] I am using npm >= 9.6.5 with --include=optional
[ ] I am using yarn >= 3.2.0
[x] I am using pnpm >= 7.1.0 with --no-optional=false
[ ] I am using Deno
[ ] I am using Bun

What is the complete error message, including the full stack trace?
astroapp-1  | Something went wrong installing the "sharp" module
astroapp-1  |
astroapp-1  | Cannot find module '../build/Release/sharp-linuxmusl-x64.node'
astroapp-1  | Require stack:
astroapp-1  | -<EMAIL_ADDRESS>astroapp-1  | -<EMAIL_ADDRESS>astroapp-1  | -<EMAIL_ADDRESS>astroapp-1  |
astroapp-1  | Possible solutions:
astroapp-1  | - Install with verbose logging and look for errors: "npm install --ignore-scripts=false --foreground-scripts --verbose sharp"
astroapp-1  | - Install for the current linuxmusl-x64 runtime: "npm install --platform=linuxmusl --arch=x64 sharp"
astroapp-1  | - Consult the installation documentation: https://sharp.pixelplumbing.com/install
astroapp-1  |     at Object.<anonymous> (/app/node_modules/.pnpm/sharp@0.32.6/node_modules/sharp/lib/sharp.js:37:9)
astroapp-1  |     at Module._compile (node:internal/modules/cjs/loader:1368:14)
astroapp-1  |     at Module._extensions..js (node:internal/modules/cjs/loader:1426:10)
astroapp-1  |     at Module.load (node:internal/modules/cjs/loader:1205:32)
astroapp-1  |     at Module._load (node:internal/modules/cjs/loader:1021:12)
astroapp-1  |     at Module.require (node:internal/modules/cjs/loader:1230:19)
astroapp-1  |     at require (node:internal/modules/helpers:179:18)
astroapp-1  |     at Object.<anonymous> (/app/node_modules/.pnpm/sharp@0.32.6/node_modules/sharp/lib/constructor.js:11:1)
astroapp-1  |     at Module._compile (node:internal/modules/cjs/loader:1368:14)
astroapp-1  |     at Module._extensions..js (node:internal/modules/cjs/loader:1426:10)

What is the complete output of running npm install --verbose --foreground-scripts sharp in an empty directory?
It's too long for GitHub, so I've uploaded it to JumpShare: https://jmp.sh/9jppp81J
What is the output of running npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp?
Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y)
  System:
    OS: Linux 5.15 Ubuntu 20.04.5 LTS (Focal Fossa)
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
    Memory: 10.51 GB / 15.49 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 20.8.1 - ~/.nvm/versions/node/v20.8.1/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 10.2.1 - ~/.nvm/versions/node/v20.8.1/bin/npm
    pnpm: 8.15.6 - ~/.local/share/pnpm/pnpm
    bun: 1.0.7 - ~/.local/share/pnpm/bun

astroapp-1  | -<EMAIL_ADDRESS>
This log is not from the latest version, which is currently v0.33.3, please upgrade.

Thanks. The source of the issue was that Astro (my dependency) was specifying version 0.32.6 in it's optional dependencies, so even though I've had 0.33.3 in my package.json, version 0.32.6 was used by Astro.
Adding this setting to package.json solved the issue and sharp is now working for me in Alpine Linux:
"pnpm": {
    "supportedArchitectures": {
      "libc": [
        "musl"
      ]
    },
    "overrides": {
      "sharp": "0.33.3"
    }
  }


Only store non-empty routes in Individual

This PR:

[x] Removes empty routes from Individual.
[x] Adds and passes relevant tests.
[x] Has well-formatted code and documentation.

Benchmark
On VRPTW.
This PR (e25d6c35501095d17a90621dfa91be64ed4a7ad4; job ID 2530076; 10x seeds/1h with configs/vrptw.toml):
 Avg. objective: 333241.4 (min: 333117, max: 333411)
Avg. iterations: 115161.3 (min: 103903, max: 128743)

This does not seem done to me yet. What about:

SREX: sort asc angle no need to check empty
greedyRepair: numRoutes is just routes.size() (?)
Individual::evaluate: break unnecessary
Docstrings on e.g. Individual::numRoutes, ::getRoutes, and ::routes_, and possibly other places.

(there might be other places, but a search for e.g. num_routes/numRoutes and similar should turn that up)

You were right this was done a bit quick, thanks for the suggestions. I checked for num_routes/numRoutes and empty so I think all should be covered now. Note in the crossover greedy repair we may still have empty routes before repairing.

Since this "routes have length data.numVehicles() thing has been an assumption for a very long time, I'm running a benchmark to be sure we got every odd corner case. Results should be in in 3h. If everything looks good I think we can merge it, no problemo.

Looks good, slightly better objective than what we've seen on average so far, and around 10% more iters. Both are very nice to have! @wouterkool will you do the honours?


[BUG] Exception when support RWX in longhorn v1.0.1

Describe the bug

Get execption for the pod longhorn-nfs-provisioner when add support for RWX in longhorn v1.0.1 under kubenetes v1.16.15. it's installed through Kubectl inside of AWS EC2
The status of pod 'longhorn-nfs-provisioner-xxx' is always under **ContainerCreating**
When I look at the details of the pod through kubectl describe pod xxx I got below exception

To Reproduce
Steps to reproduce the behavior:

Follow this link to support RWX: https://longhorn.io/docs/1.0.1/advanced-resources/rwx-workloads/
Use this command to get the pod status: kubectl get pods -n longhorn-system

Expected behavior
The pod status is running successfully
Log
Additional context
Add any other context about the problem here.

Can you provide kubectl describe of the PVC?

It seems that you don't have enough node/disk to schedule replicas for the underlying volume.
Can you check Longhorn UI to see if all replicas are scheduled.
How many nodes do you have in your cluster? How many replicas does the Longhorn volume have?


Add async to _RuleDispatcherWrapper

Hello, thanks for your great project.
I actually want to write a function to respond to each received message. Then I found that the on_rule decorator will throw the error RuntimeWarning: coroutine 'function' was never awaited. And this PR fixes it.
BTW, I can help add some examples if you like.

Hello, thanks for your PR. This is a known issue and has been fixed in the dev version.
Modifying the _RuleDispatcherWrapper class is not a good option. My fix in the dev version is to judge the return value of MessageDispatcher in MessageEvent and wait for the coroutine to complete.
For related changes, see MessageEvent.__default_handler__ in dev
At the same time, thank you for reminding me, I will release this development version soon. Of course, if you are willing to add some examples for this, I will be very grateful.

Thanks for your reply!


Collect and join OpenAire data to enable is_eu to show if EU funded

Open Access Infrastructure for Research in Europe
sparql endpoint: http://lod.openaire.eu/sparql

Blocked as the endpoint is down since Friday. Emailed support

Returning this to the backlog with lower priority after discussion with @jaklinger . The API may be an alternative to using the SPARQL endpoint - certainly for a quick option to populate the is_eu flag - but we will wait for further data requirements to come out of EURITO before committing to an approach


Show the /doc command in /help

Is your feature request related to a problem? Please describe.
Currently, the /doc command is hidden, because it was "broken". Now, it's fixed. I suggest to show it again.
Describe the solution you'd like
Show the /doc command by change the hidden attribute of the command in the decorator.
Describe alternatives you've considered
No alternative.
Additional context
@commands.command(
        name='doc',
        usage='/doc {query}',
        aliases=['documentation'],
        description=_('Shows 4 or fewer links referring to a documentation on readthedocs.io :D'),
        hidden=True # I want this line to change
)

Will be fixed in disnake-migration branch!


Module 4 exercises [BAKO Mamane]

WS2_M4E1_Template_Bako.docx

Well done, Bako. You clearly grasped the material outlined in Module 4 and successfully applied it to these exercises. Thank you for your participation! Please be sure to fill out the post-Module survey before you begin the next Module.


Paginated mode blocks reading a book on Windows at least

reading is blocked after few pages in paginated mode (approximatively 2 pages) depending on the os that is used.
with MacOS and Ubuntu 16.04 no problem, but on Windows 10 and Ubuntu 18.04 the reader doesn't work like it should.

What is the exact source / build of the app (develop branch, or prebuilt installer?) I need to see/check the precise navigator version in package-lock.json to make sure the Electron/Chromium fix for left-right arrow keys is included.

the source is develop branch and navigator version is 1.0.26

Hello,
I think this issue is related to a second display glitch
On reader :

When I lower the height of the window, then I raise it to the same height as before.

That display the previous "page" of book and not the same.
I think we can lost the postion in book.
What do you think ?

Ubuntu lts 18.04
r2-navigator in 1.0.26

To narrow down the problem, is there some log we could add to the software, so we can check something?

I am not able to reproduce this on Windows 10.

PS: I am using the develop branch (well, this actually: https://github.com/readium/readium-desktop/pull/323 )

the paginated mode issue seems fixed on Windows 10.
Now, it's the scrollable mode on Windows 10 that blocked book reading.
I am using the develop branch

On ubuntu lts 18, it's opposite of the Manuel answer.
Paginated mode is blocked at each new chapter
whereas it doesn't blocked in scrollable mode

I cannot reproduce (scroll or paginated) on Linux (Lubuntu 18.04)

I test with various EPUBs, usual suspects: Wasteland, AccessibleEPUB3, ChildrensLitterature ...
What EPUBs are problematic in your tests?

Regarding "loosing the reading location": yes, this is a problem we had in Readium1 as well. Because we track the upper-left corner of the document text in order to estimate the user's reading position, when the window is resized there is a side effect of "walking backwards". Note that we also track the reading location when the user interacts with the mouse or keyboard in the document, but this isn't related.

I posted a separate issue: https://github.com/readium/r2-navigator-js/issues/43

I used this epub: https://bibliothequenumerique.tv5monde.com/download/epub/470

in my case i used this epub: https://github.com/IDPF/epub3-samples/releases/download/20170606/moby-dick.epub

https://bibliothequenumerique.tv5monde.com/download/epub/470
=>
504 Gateway Time-out - nginx

daniel.tar.gz

Dumas - Le Comte de Monte Cristo-37.epub => works fine too in my tests (scroll and paginated)

It's works now. I just removed and added the epub.
Sorry for the inconvenience

No problems. Weird though!

On MacOS I have observed a pagination bug (CSS Columns) which sounds very similar to this! When I shring the window to a smaller size, there comes a threshold point at which the reported number of columns/spreads is completely wrong (usually a very small number). It is easy to see in debug/development mode (npm run start:dev) thanks to the verbose console messages coming from the navigator (Locator notifications). Very strange bug. I suspect this is a weird edge case with Chromium-in-Electron (not the first one, not the last one ... :( )

Sorry but finally I still have this issue.
The behavior is very strange on all epub that I check. (include le comte de monte cristo).
When i click on the arrow in reader. inevitably it hangs


Array type prompt exception

Bug Report

🔎 Search Terms

🕗 Version & Regression Information

This is a crash
This changed between versions ______ and _______
This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
I was unable to test this on prior versions because _______

⏯ Playground Link

Playground link with relevant code
💻 Code

type type1 = ['a', 'a1'] | ['b', 'b1'];

export const demo1: type1 = ['a','']  // Here is a prompt for b1

🙁 Actual behavior

🙂 Expected behavior

Duplicate of #46457


Add missing const to BorderRadius.circular

Description
Adds const keyword to BorderRadius.circular constructor which in turn uses the already const BorderRadius.all constructor.
My own use case:
Widget build(BuildContext context) {
  const shape = RoundedRectangleBorder(borderRadius: BorderRadius.circular(12));
  return Card(
    shape: shape,
    child: InkWell(
      customBorder: shape
    )
  );
}

Workarounds
Using BorderRadius.all(Radius.circular(x)) which are both already declared const.
Related Issues
None reported (could open one).
Tests
None (could add with some guidance)
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: Replace with a link to your migration guide

I did see https://github.com/flutter/flutter/pull/52309 but the main problem noted there was Radius.circular not being const, which it is https://github.com/flutter/engine/blob/master/lib/ui/geometry.dart#L900

I see now that the Flutter analyzer complains about Radius.circular but as far as I can see, it has been declared const ever since its inception (https://github.com/flutter/engine/pull/2820/files#diff-551f8e8bf77581b0737426421e6a2c5aR686)

Radius.circular is const constructor, but radius might not be.

@chunhtai You're right, just very confused why it doesn't work in a constructor setting.


[blend2d] Fix core build

Fixes #33467, fix blend2d[core] build.
Integrate futex into blend2d's core instead of default-features, missing it in core will cause the following error:
G:\vcpkg\buildtrees\blend2d\src\ce84a75da8-8739d68a35.clean\src\blend2d\threading\futex.cpp(34): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
G:\vcpkg\buildtrees\blend2d\src\ce84a75da8-8739d68a35.clean\src\blend2d\threading\futex.cpp(34): error C2146: syntax error: missing ';' before identifier 'futexWinAPI'
G:\vcpkg\buildtrees\blend2d\src\ce84a75da8-8739d68a35.clean\src\blend2d\threading\futex.cpp(42): error C2039: 'futexWinAPI': is not a member of 'BLFutex'
G:\vcpkg\buildtrees\blend2d\src\ce84a75da8-8739d68a35.clean\src\blend2d\threading\futex.cpp(34): note: see declaration of 'BLFutex'
G:\vcpkg\buildtrees\blend2d\src\ce84a75da8-8739d68a35.clean\src\blend2d\threading\futex.cpp(42): error C2065: 'futexWinAPI': undeclared identifier
G:\vcpkg\buildtrees\blend2d\src\ce84a75da8-8739d68a35.clean\src\blend2d\threading\futex.cpp(42): error C2039: 'FutexWinAPI': is not a member of 'BLFutex'
G:\vcpkg\buildtrees\blend2d\src\ce84a75da8-8739d68a35.clean\src\blend2d\threading\futex.cpp(34): note: see declaration of 'BLFutex'
...

All features are tested successfully in the following triplet:
x86-windows
x64-windows
x64-windows-static

The usage test passed on x64-windows (header files found):
blend2d provides CMake targets:

    find_package(blend2d CONFIG REQUIRED)
    target_link_libraries(main PRIVATE blend2d::blend2d)

[x] Changes comply with the maintainer guide
[ ] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Thanks for the fix!


Add C++ message descriptors helper

Zero-overhead. Allows creating simpler general nanopb C++ wrappers by
examining variable type and not needing macro magic.

Hmm, perhaps this should go behind some option. Either on compiler command line, or a message-specific option.
I've been considering moving other rarely used stuff like protoc insertion points behind separate options also, because while they're zero overhead when compiled, they clutter the generates files quite a bit.

(The travis check fail is also valid: // is not a valid comment in C89, you have to use /* */)

Got it. Will hide it behind a command. Reorganizing can be deferred once you've figured out how you want to organize that stuff?

Yeah. It wouldn't be any problem for me to add an option for it later, but as this is a new feature it might make sense to have it behind an option to start with.
Otherwise it looks mergeable. I still kind of wish there was a native C++ protobuf library for embedded, but in the absence small helpers like this are useful :)

Well nanopb is a great spot for that :D. Do you have any pointers on how I can write some unit tests for this?

Well, you can use .cxx files in unittests quite the same way as .c files.
Something quite basic should suffice, i.e. just access the template with the name it should have and check that code compiles and the values returned are correct. Doesn't even have to encode or decode anything. The "enum_to_string" testcase might be a reasonable template, it also tests just a few simple functions.
As for enabling the option, use NANOPBFLAGS variable in SConscript: https://github.com/nanopb/nanopb/blob/master/tests/regression/issue_203/SConscript

That doesn't seem to work. The test runs with both environments appended to each other

--nanopb_out=--cpp-descriptor--strip-path:.

NVM. Figured it out.

OK. I made some more changes vs the last thing you reviewed:

Hide the descriptor behind namespace nanopb
Add support for C++ versions between C++03 & C++17
Add tests for C++03, C++11, C++14, & C++17 versions of the generated code (maybe there's a cleaner way you'd like me to do it?
Fix regression 203 SConscript to not adjust the global env.

Hmm yeah, looks good otherwise than the duplication of code in the tests.
Perhaps it could be done in single SConscript like this:
 env_cpp03 = env.Clone()
 env_cpp03.Append(CXXFLAGS = '-std=c++11')
 p = env_cpp03.Program('test_cpp03', ['message_descriptor.cc', 'message.pb.c'])
 env_cpp03.Run(p)

 env_cpp11 = env.Clone()
 env_cpp11.Append(CXXFLAGS = '-std=c++11')
 p = env_cpp03.Program('test_cpp11', ['message_descriptor.cc', 'message.pb.c'])
 env_cpp11.Run(p)

So that the source code doesn't need to be duplicated. Easier to add extra checks later.

Sounds good.

Not familiar enough with scons. How do I modify my PR to skip if the compiler doesn't support the flag?
I tried
    e.Append(CXXFLAGS = '-std={}'.format(std))

    conf = Configure(e)
    if not conf.CheckCXX():
        print("Skipping {} test - compiler doesn't support it".format(std))
        continue

but then SCons just exits with an error but no message about what I'm doing wrong:
Checking whether the C++ compiler works... yes

scons: ***

Hacked something together that works - not sure if that's the cleanest way to write it. Let me know.

Thanks, merged!


feat(card): add Webhooks-card 008#223

issue number :#223
Checklist
I have read and followed the contributing guidelines.
I have developed the component according to the requirements.
I have tested the component across different browsers and screen sizes.
I have documented the component for future reference.
I have submitted a pull request with appropriate labels and referenced this issue number.
All done ...

hey @hari @sudhashrestha review my card.

Please make this responsive.

Alright @hari

🚀 Preview deployed to:

🚀 Preview deployed to:

🚀 Preview deployed to: https://51ff48c0.animata.pages.dev

🚀 Preview deployed to: https://dev-dev.animata.pages.dev


Controller as 'vm'

Hi John,
I'm not seeing the benefits of declaring 'ExampleCtrl as vm'. What is the intention by prefixing all template bindings with the same prefix, although their origin differs from each other ?
What do you think about declaring it semantically useful like 'ExampleCtrl as example' ? This way I can quickly identify the controller in use for the current html template just by looking at it. (Useful for example when maintaining multiple views and their respective controllers in multiple tabs).

I don't mean to bring up another question, and I assume I'm having a blonde moment with this idea. But in the actual HTML for binding you should use controllerAs: exVm for one and controllerAs: whoaVm for another. Correct? You don't want all controllers to have vm as the alternate syntax because that can get confusing but in the JS itself you can use var vm = this; for each one?

That is correct. In the html you would want to name them differently. Which means you won't have conflicts if you have the same property in both controllers for example.
However like you say in the controller itself that is not the case so then you can use var vm = this; in each of them. Which would be nice since then everything will look uniform. And in the html it is easy to identify which controller you are using by the different names.

Awesome thanks for clearing that up!
And pertaining to directives... Should I even use the link function? There doesn't seem to be much of a reason besides the functionality of obtaining attributes, how would I get around this issue by using controllerAs in a  directive?

This worth noting in the styleguide? regarding nested controllers and using controller as? I can provide the PR if needed,


Cannot open picker on version 1.0.0

I create sample to check version 1.0.0. But cannot open picker in iOS and Android.
 const handleButtonPress = async () => {
    MultipleImagePicker.openPicker();
  };

On terminal
Possible Unhandled Promise Rejection (id: 2):
TypeError: undefined is not an object (evaluating '_reactNativeMultipleImagePicker.default.openPicker')

Package.json
  "@baronha/react-native-multiple-image-picker": "^1.0.0",

Please update "Usage" section on "https://www.npmjs.com/package/@baronha/react-native-multiple-image-picker/v/1.0.0?activeTab=readme" with import { openPicker } from '@baronha/react-native-multiple-image-picker';


[AzureMonitorExporter] fix SDK version

Fixes: #37775
User reported an unusual dotnet version string. The SDK version field exceeded max length and telemetry cannot be ingested.
Changes

check for unusual dotnet version strings.

API change check
API changes are not detected in this pull request.


rename "scope" into "how"

Hi this ticket is not a bug, it's a suggestion
It might be just my opinion, but the syntax scope = tt.scope.origin() a bit long and also a bit complex.
Would you consider to rename scope into "how" - as in pandas join
how ?

is to define how to apply aggregation formula?
how to pivot data before applying the aggregation formula?
how to organize data before applying the aggregation formula?

for example,
how = "cumulative", along = [lvl['AsOfDate']] or by=lvl[AsOfDate]
how = "simple", along = [lvl['AsOfDate']]
how = "siblings", for_each = lvl[AsOfDate]

Hi Anastasia, we're not planning on making this renaming as it would complexify the signature of all the aggregation functions.


Add 'Using Events' to Intercom

Suggested by @tangentfairy - This will make it easier to check if a Dojo is using Events for CDF Admins.
Unsure of how this would work as intercom is filled with individual users but could work better so that we can see if individual users have been checking in.

Could put it on the champion/founder account to show the Dojo is using it, and then the check in flag would be a separate flag on a per user basis.

For more information on creating test data, see this doc. The main readme file is here.

The intercom service is here and is initialised here.
We need to tell the Intercom service if a person with a user type of champion in the cd_usersdojos join table on the dojos database has used an event. So we need to look up if any of the dojos that user is in has an event.
Separate to this, when any user is logged in and they have been checked in to an event before, we need to let Intercom know. So we'll need to do a lookup when they log in to see the last time they were checked in to an event.

So there are three fields we want in Intercom:

champion_using_events (boolean)
last_event_created (timestamp)
user_last_checked_in (timestamp)

Note: We do not want to store every timestamp for event created/last check in, because this would be overkill! We just want to store the latest value.
Let me know if you have any questions, usually around on the Gitter!


Simple Markdown fails with Unexpected view type nested under text node

Hello, I've tried all markdown libraries and all of them seem to have an error parsing basic markdown due to how react native Android renders components. The error seems to occur when you try nesting components in your markdown, for example something like this (view it raw since github parses it)

[Leetcode Problem] (https://google.com)
A general classification of the topics, and a summary of the problem-solving ideas for each type of question.

or

[I. Basic Concepts] (#1 - Basic Concept)

URL

I get the following error
Unexpected view type nested under text node: class com.facebook.react.uimanager.LayoutShadowNode
a simple list with a nested list of links fails... Would anyone have a simple and elegant solution to this problem?
I guess the best solution would be to convert the text tag into a view and wrap the text in a text tag?

I've been hunting for a decent mobile markdown editor for days now. No luck they are all broken.

here is a quickfix, you'll need to add a patch:
patch-package
--- a/node_modules/react-native-simple-markdown/rules.js
+++ b/node_modules/react-native-simple-markdown/rules.js
@@ -141,7 +141,7 @@ export default (styles) => ({
   },
   paragraph: {
     react: (node, output, state) => {
-      return createElement(View, {
+      return createElement(Text, {
         key: state.key,
         style: styles.paragraph
       }, output(node.content, state))

I ended up using Quill.
It's excellent and has lots of nice UI/Formatting automations.


Ask for credentials when configured bytebin returns HTTP 401 (Unauthorized)

Alright this is a feature request meant to allow a custom bytebin to require authentification for security. Primarily if that bytebin connected directly to the storage and generates the data itself.
Now when the bytebin URL returns the HTTP status code 401 the editor (and possibly verbose and tree viewer too) should ask the user for credentials. After they were provided the URL is requested again this time with the credentials. When the data is saved the credentials should be provided as well.
I'm not sure what's the best way to send the credentials, as the connection may be unsecured.
Also ideally there's a checkbox that stores the credentials for that specific bytebin URL. Not for others as the same bytebin might require authentification for some URLs but not for others.

The underlying idea is that I create an addon for LuckPerms that runs a faked Bytebin. So that when a specific URL is requested it sends the permission data directly instead of uploading it to a separate server. Also when the editor saves data it is applied directly, if the auth is correct.
However it still needs to function as a normal bytebin for verbose and tree. That's why normal URLs will not require auth.
As a convinciece feature it would be awesome if the editor had a configuration option to always open a specific bytebin URL by default (if none is given).

My opinion is that this isn't something that we should officially support - the stakes are much higher if we get something wrong security wise, and I also don't think it's likely to be a popular feature & therefore not worth spending time supporting.


Support for Summary collector

Currently gauge, counter and history support is available but summary is missing.
I've already developed this collector and currently running it on some production servers.
It currently only has support for Redis, as we don't use APC and I don't have the time to integrate it.
It would be super-duper if parts of it could be merged or extended.
https://github.com/buffcode/prometheus_client_php/commits/summary-collector
If accepted I will create a PR.

I would love to have summary support, thumbs up!

buffcode change is great. I'm waiting for merge request and merge 👍

bump would be great to have :D

I think there might be a better chance at getting a PR accepted in this fork by @NoelDavies.
This project seems to be completely dead.

Yeah I've got an active fork going with 7.4 support

Submit a PR to https://github.com/endclothing/prometheus_client_php and I'll get it approved. It's available at https://packagist.org/packages/endclothing/prometheus_client_php


LanguageTranslation Service Constants

The LanguageTranslation service API in the Java SDK does not define any constants for supported languages. For example, right now you have to write:
service.translate("hello", "en", "es");

Rather, having a set of pre-defined constants (an enum most likely) of languages supported by the service would be more helpful:
service.translate("hello", Language.EN, Language.ES);

fixed


Add auto-generated error messages to element's and condtion's methods.

Now all method's like element(), domElement(), button() and etc. throw org.openqa.selenium.TimeoutException without human readable message.
Add to message: method name which fail, locator(if exist).

Fix for conditions in #34


Astro SST is broken

I keep getting this useless error message when trying to deploy my Astro app to AWS
Error: Could not find build meta file at dist/sst.buildMeta.json. Update your 'astro-sst' package version and rebuild your Astro site.

Don't know if it is just me but I think this might be reproducible across machines.
Repo steps:

pnpm create astro (then change directory into the newly Astro directory)
Run sst init and double check that your SST config's all good. Make sure it's set up for AWS.
Run sst deploy

Expected:
My site should be deployed to AWS and that a generated Cloudfront URL should actually be working without fail. No random issues. More importantly, it should not return null. At the end of day, it should just work. Please.
/// <reference path="./.sst/platform/config.d.ts" />

export default $config({
  app(input) {
    return {
      name: "dark-debris",
      removal: input?.stage === "production" ? "retain" : "remove",
      home: "aws",
      providers: {
        aws: {
          profile: "dev",
        },
      },
    };
  },
  async run() {
    new sst.aws.Astro("MyWeb");
  },
});

{
  "name": "dark-debris",
  "type": "module",
  "version": "0.0.1",
  "scripts": {
    "astro": "astro",
    "build": "astro check && astro build",
    "dev": "sst dev astro dev",
    "preview": "astro preview",
    "start": "astro dev"
  },
  "dependencies": {
    "@astrojs/check": "^0.7.0",
    "astro": "^4.10.1",
    "astro-sst": "2.43.0",
    "sst": "ion",
    "typescript": "^5.4.5"
  }
}

astro.config.mjs
import { defineConfig } from "astro/config";

// https://astro.build/config
export default defineConfig({});

when you ran sst init did it not print instructions to add that adapter?


Don't skip creation of new user if DoNotOverwriteNonLdapUsers is true.

Fixes #177

Thanks for the fix! I have added some tests to verify that it works as expected and it works indeed like a charm!
The new release has been tagged and deployed.


Windows - When clicking the icon in the top left script errors

When clicking the icon in the top left script errors.
I then must close application via Task Manager

Fixed.


Invalid path is generated when the point behind the vehicle is set as a goal

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
Hi team,
I'm currently running Autoware version 20240115 with prebuilt docker on Carla, and I found that the invalid path is generated when the point behind the vehicle is set as a goal.
Here's the [image] for the situation.
I set the goal point as the point behind the vehicle after spawning the ego vehicle, but the vehicle cannot move even though the routing was successful(I could press the button "AUTO" in RViz)
I also checked the [launch.log] file, and I could see the log below,
1709580193.0063493 [component_container-73] [motion_utils] calcLongitudinalOffsetToSegment: Longitudinal offset calculation is not supported for the same points. Return NaN since no_throw option is enabled. The maintainer must check the code.
1709580193.0078657 [component_container-73] [ERROR] [1709580193.007519306] [control.control_validator]: predicted_trajectory size is less than 2. Cannot validate.

which states there's an error on calculating a longitudinal offset.
Expected behavior
I want the vehicle to drive forward successfully to the goal point.
Actual behavior
But the vehicle does not move at all.
Steps to reproduce

Run Autoware of version 20240115, prebuilt docker with the maps here: [lanelet2 map], [pointcloud map]
Spawn ego vehicle, and set the goal point as a point behind the vehicle which is on the same lane.

Or here's a ros2bag file I recorded.
Versions

Autoware: 20240115, prebuilt docker
Carla: 0.9.13
OS (host): Ubuntu 20.04
OS (docker): Ubuntu 22.04

Possible causes
According to the error message, I think the function related to the issue is this:
https://github.com/autowarefoundation/autoware.universe/blob/7ef61a96008eafc466c315f01a889540335787f1/common/motion_utils/include/motion_utils/trajectory/trajectory.hpp#L401
Additional context
I thought this and this could be the same issue, but current issue occurs after fixing the first one, and for the latter one, I think it is not related to the backward path.

@Kim-mins
Hello,
Thank you so much for the report!
In the current start_planner module the reported situation is not supported and explained here and implemented here
If you have solution for this problem we are happy to discuss here and if you make PR me or other member can review the PR!
By the way what's the motivaiton for setting goal?
If my understanding is correct, backward driving on the road is necessary :thinking:

Thank you for the response @kyoichi-sugahara!!
Maybe I should have investigated more information for this issue.. sorry for bothering. I didn't know this is a known issue.
I'll let you know if I have any idea for this!
For the motivation, I just wanted to check if the vehicle could drive 'forward' and come back to the starting point well.
In my opinion, driving forward is correct, even though there's no other vehicles on the road, since that is the right direction of the road.
But I also think it's necessary to go backward when the vehicle is at a parking lot or alley, since there's no right direction.

Parking area can be represented in the lanelet map, in which case the freespace planner should take over and allow backward driving.
For the alley case, I imagine a case where a one lane alley is blocked and the ego vehicle needs to reverse to take another route. This case is currently not handled by Autoware.

@Kim-mins
You're welcome and we all appreciate the feedback!! Thanks.

I didn't know this is a known issue.

In my opinion, this is not the issue and it's not supported.

But I also think it's necessary to go backward when the vehicle is at a parking lot or alley,

Same with maxime san's comment, for parking lot, parking lot information should be added in the current autoware and backward driving can be achieved.
Backward driving in alley case is not supported currently :bow:  Basiccaly direction of travel must be linked to a lane information.
In conclusion, autoware currently does not support the functionality to move in the opposite direction of the lane direction. However, if you feel there is a need for this, it would be a good idea to create a new issue regarding this matter and close this issue.(or update this issue) How does that sound?

Thank you for the kind responses @maxime-clem and @kyoichi-sugahara!
What I wanted to know from this issue was "why the vehicle cannot drive forward when the goal is at behind". So, I think it is ok for the vehicle not to drive backward.
And, for backward driving, after reading comment from you two, I got to know it is not supported for now and it is tricky to handle.
So, as @kyoichi-sugahara summarized, I agree to closing this issue, and open another issue for the feature for backward driving, but I think it is not too late to handle backward driving when needed, since I think the situation in alley(@maxime-clem noted above) would be not that frequent.
So.. may I close this issue for now?

I just installed autoware and I am getting this same error when vehicle reaches the destination, how can I fix it? Do I need to change any property related to 2D goal pose?

@ahsan155 There is no workaround for this issue yet apart from splitting the route (instead of doing A -> C, first do A ->B, then B -> C).

@ahsan155 There is no workaround for this issue yet apart from splitting the route (instead of doing A -> C, first do A ->B, then B -> C).

thanks for the quick response. I am not even setting point behind vehicle as destination. I am just trying to move the vehicle on a straight path. why does it still gives error

These messages are just warning messages. This PR will prevent them from displaying in the terminal: https://github.com/autowarefoundation/autoware.universe/pull/6955
Otherwise I don't think there is any issue in your case.

Hello @Kim-mins . I think you can open discussion in feature request section for this request. If it is convenient for you, we can close this issue this way. @maxime-clem

Hello @meliketanrikulu!
I just opened the feature request here!
Please feel free to close this issue or keep it open.
Thanks!


Use a with statement to read the file

For exception safety

Can you elaborate on exception safety? Won't the same errors be raised in both scenarios?

If read() (for whatever reason) were to throw an exception, you'd leave an open file descriptor (.close() would not be called).  Though this is unlikely, it's best to write the (simpler) code which does this for you.  with statements are a best practice in python when dealing with file objects (or other closables).
You can read more about them at their PEP (introduced in py25, standard in py26): https://www.python.org/dev/peps/pep-0343/

Ah, right. Good catch :+1: I will land this now.

This has been merged/released in 0.14.3. Thanks for the fix!

No problem :) Thanks for the merge :D


Bug: cellpadding attribute not working when executing code

Try running this code. You won’t be able to see the padding
<!doctype html>

<title>Title</title> <meta charset="utf-8">

Hello World

hello	 bye

good	 nice

I am unable to reproduce this. There seems to be a typo in the ending title tag. Please make sure the syntax is right.

Hey there, thanks for checking I tried to check to again multiple times..
After sometime, tried to click on reload for the safari run browser and seems to update and work fine. Seem to be a cache issue perhaps..


Custom stringify/transform option for static content in sfc compiler and loader

What problem does this feature solve?
When you write a non DOM environment custom renderer, you need to implement all required nodeOps of the renderer.
Most of opts are actually unaware of the runtime enviroment an long as the structure looks like a tree and have method for manipulate node.
However, insertStaticContent is used to insert a HTML string to reduce the overhead of create elements.
Which may not exist in the environment of other non dom target (if any).
You end up need to embed a parser to parse the html back to ast again and process it. Which cause more overhead instead.
For example, when you are rendering to something like fixed size canvas.
You will probably want to just pre-render the static tree into image directly if you can.
But you now need to parse the html and render to image again during runtime, which is double overhead.
What does the proposed API look like?
An option in the vue-compiler to override how static content should be handled.
Receive a argument for the content vue want to insert as static content (in either html or v-dom tree format (provide as object may reduce the overhead during compile but harm future compatibility if the internal structure is going to change)).
Returns a serializable object that vue will feed into the insertStaticContent when rendering.
Or accept null so the compiler do not generate static node at all.
const compilerOptions = {
  serializeStatic (domOrHTML) {
    return {
      'this': 'object will be send to insertStaticContent during rendering'
    }
  }
}

You don't need to implement insertStaticContent - it's only used if the accompanying compiler for your target platform leverages static string transforms:

compiler-core by default doesn't perform stringify optimizations
compiler-dom implements an extra transform adjacent static content into Static nodes, and runtime-dom implements insertStaticContent to handle these nodes.

So as long as you didn't implement the same stringify logic in your custom compiler, you don't need to implement insertStaticContent in your custom renderer.

So, the proper way to do this is.
Create your own compiler like compiler-dom, and inject the compiler into vue template loader via the vue.config.js?


bug: webpack error

bug

reduex: 3.5.2
webpack: 1.12.14

What is the current behavior?

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar.
when i remove es dir which in redux root dir, can build success
What is the expected behavior?
build success

Why are you using redux/es/* build with Webpack? Can you give more details? I’m afraid we won’t be able to help without a project reproducing the problem.

@gaearon
I use redux like this
import { createStore, applyMiddleware } from 'redux';
I don't know why used redux/es/*
build command
cross-env NODE_ENV=production webpack --config internals/webpack/webpack.prod.babel.js --colors --progress -p

webpack.prod.babel.js
const path = require('path');
const webpack = require('webpack');
const HtmlWebpackPlugin = require('html-webpack-plugin');

module.exports = require('./webpack.base.babel')({
  // In production, we skip all hot-reloading stuff
  entry: [
    path.join(process.cwd(), 'app/app.jsx'),
  ],

  // Utilize long-term caching by adding content hashes (not compilation hashes) to compiled assets
  output: {
    filename: '[name].[chunkhash].js',
    chunkFilename: '[name].[chunkhash].chunk.js',
  },

  plugins: [
    // OccurrenceOrderPlugin is needed for long-term caching to work properly.
    // See http://mxs.is/googmv
    new webpack.optimize.OccurrenceOrderPlugin(true),

    // Merge all duplicate modules
    new webpack.optimize.DedupePlugin(),

    // Minify and optimize the JavaScript
    new webpack.optimize.UglifyJsPlugin({
      compress: {
        warnings: false, // ...but do not show warnings in the console (there is a lot of them)
      },
    }),

    // Minify and optimize the index.html
    new HtmlWebpackPlugin({
      template: 'app/index.html',
      minify: {
        removeComments: true,
        collapseWhitespace: true,
        removeRedundantAttributes: true,
        useShortDoctype: true,
        removeEmptyAttributes: true,
        removeStyleLinkTypeAttributes: true,
        keepClosingSlash: true,
        minifyJS: true,
        minifyCSS: true,
        minifyURLs: true,
      },
      inject: true,
    }),
  ],
});

webpack.base.babel.js
const path = require('path');
const webpack = require('webpack');

module.exports = (options) => ({
  entry: options.entry,
  output: Object.assign({ // Compile into js/build.js
    path: path.resolve(process.cwd(), 'build'),
    publicPath: './', // support fileUrl, default is set '/'
  }, options.output), // Merge with env dependent settings

  module: {
    loaders: [
      {
        test: /\.(js|jsx)$/,
        loader: 'babel',
        exclude: /node_modules/,
        query: options.babelQuery,
      }, {
        // Do not transform vendor's CSS with CSS-modules
        // The point is that they remain in global scope.
        // Since we require these CSS files in our JS or CSS files,
        // they will be a part of our compilation either way.
        // So, no need for ExtractTextPlugin here.
        test: /\.css$/,
        exclude: /node_modules/,
        loader: 'style-loader!css-loader?importLoaders=1',
      }, {
        test: /\.(eot|svg|ttf|woff|woff2)$/,
        loader: 'file-loader',
      }, {
        test: /\.(jpg|png|gif)$/,
        loader: 'url-loader?limit=8192',
      }, {
        test: /\.json$/,
        loader: 'json-loader',
      },
    ],

  },

  plugins: options.plugins.concat([
    new webpack.optimize.CommonsChunkPlugin('common.js'),
    // Always expose NODE_ENV to webpack, in order to use `process.env.NODE_ENV`
    // inside your code for any environment checks; UglifyJS will automatically
    // drop any unreachable code.
    new webpack.DefinePlugin({
      'process.env': {
        NODE_ENV: JSON.stringify(process.env.NODE_ENV),
      },
    }),
  ]),

  resolve: {
    modules: ['app', 'node_modules'],
    extensions: [
      '',
      '.js',
      '.jsx',
      '.react.js',
    ],
    packageMains: [
      'jsnext:main',
      'main',
    ],
  },

  devtool: options.devtool,
  target: 'web', // Make web variables accessible to webpack, e.g. window
  stats: false, // Don't show stats in the console
  progress: true,
});

I’m afraid we can’t help unless you provide a project reproducing the issue. It’s likely not an issue with Redux so I’m closing. For help with the Webpack build configuration, please refer to StackOverflow or support forums. Redux is a library; it doesn’t force you to use Webpack, and Redux users aren’t Webpack experts this is probably a wrong place to ask for help.


[GLUTEN-5252] Fix condition eliminate for Iceberg/delta scan with filter rel

What changes were proposed in this pull request?
There is an optimization that eliminate common expression between scan and filter, but it doesn't apply on IcebergScanTransformer/DeltaScanTransformer  as they are not inherited from BasicScanExecTransformer. This PR will address this issue.
How was this patch tested?
CI
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@liujiayi771 @YannByron Can you help review on this change? Thanks.

@liujiayi771 @YannByron I found the existing case match can work for iceberg/delta because of recent PR so current patch not needed any more. Sorry for your time.


Polygon/Multipolygon fix

Fixed it so polygons and multipolygons correctly display holes.

Looks great, Thanks!
I didn't  know about any specific loop direction for complex polygons.

Someone pointed out to me that my commits were not as clear as they should have been.
The GeoJSON specification does not currently have a direction for polygons. It looks like it may be under consideration in revision 1.1 but I am not sure when or how it will work. It does specify the first ring is the exterior and all other that follow are interior. So my commits abide by the second but make an assumption on the first. This assumption is that the program that generates the GeoJSON will use the same direction for all rings. I dont see this ever being a problem but I guess I should have mentioned it, just encase this is not always the case.
Sorry my comment has now become longer than my commit.

First of all, thanks for the great software!  Very well written and easy to read.  I've tested it out on a few PostGIS generated GeoJSON objects and it works great!  Relating to your previous comment, I think the standard does need to address the direction to use.  I've been using PostGIS and the ST_AsGeoJSON function and I have noticed that if a polygon has a hole, it uses the opposite direction than you chose for generating holes.  I used your example to paste in my polygon with a hole and it won't display with a hole unless I remove the ".reverse()" method when appending the path to the paths structure.
I wonder if ST_AsGeoJSON always uses the same direction?  Here is my example
{"type":"Polygon","coordinates":[
[
[-157.756,21.4],[-157.756,21.402],[-157.756,21.402],[-157.756,21.404],[-157.756,21.404],[-157.756,21.406],[-157.756,21.406],[-157.756,21.408],[-157.754,21.408],[-157.754,21.408],[-157.752,21.408],[-157.752,21.408],[-157.75,21.408],[-157.75,21.408],[-157.748,21.408],[-157.748,21.406],[-157.748,21.406],[-157.748,21.404],[-157.748,21.404],[-157.748,21.402],[-157.748,21.402],[-157.748,21.4],[-157.75,21.4],[-157.75,21.4],[-157.752,21.4],[-157.752,21.4],[-157.754,21.4],[-157.754,21.4],[-157.756,21.4]
],[
[-157.754,21.404],[-157.754,21.404],[-157.754,21.402],[-157.752,21.402],[-157.752,21.402],[-157.75,21.402],[-157.75,21.404],[-157.75,21.404],[-157.75,21.406],[-157.752,21.406],[-157.752,21.406],[-157.754,21.406],[-157.754,21.404]
]
]}

Yeah that is definitely a problem. Right now you can not know for sure if the software you used to generate the GeoJSON has already reversed them or they still need to be reversed. Im glade you mentioned it though because I am switching to PostGIS and I am going to be relying heavily on the ST_AsGeoJSON function. I will try and create a better solution to the problem.

https://github.com/gmccrackin/GeoJSON-to-Google-Maps/commit/265c31a8ab18a81bf0fc75a81bba805d2c6e4d40
Now the polygon and multipolygon will check the direction before they reverse any interior rings. It works with the current example, the one you provided, and some others I created on the fly. If you see any example it does not work with please tell me. It only checks the first interior ring to determine the direction of all interior rings. I did this because I didnt want to slow down huge polygons. It does however check every polygon in a multipolygon.
Here is an example where the first two polygons are reversed. The code has to reverse the third though.
{"type":"MultiPolygon","coordinates":[
[[
[-157.756,21.4],[-157.756,21.402],[-157.756,21.402],[-157.756,21.404],[-157.756,21.404],[-157.756,21.406],[-157.756,21.406],[-157.756,21.408],[-157.754,21.408],[-157.754,21.408],[-157.752,21.408],[-157.752,21.408],[-157.75,21.408],[-157.75,21.408],[-157.748,21.408],[-157.748,21.406],[-157.748,21.406],[-157.748,21.404],[-157.748,21.404],[-157.748,21.402],[-157.748,21.402],[-157.748,21.4],[-157.75,21.4],[-157.75,21.4],[-157.752,21.4],[-157.752,21.4],[-157.754,21.4],[-157.754,21.4],[-157.756,21.4]
],[
[-157.754,21.404],[-157.754,21.404],[-157.754,21.402],[-157.752,21.402],[-157.752,21.402],[-157.75,21.402],[-157.75,21.404],[-157.75,21.404],[-157.75,21.406],[-157.752,21.406],[-157.752,21.406],[-157.754,21.406],[-157.754,21.404]
]],[[
[-157.856,21.4],[-157.856,21.402],[-157.856,21.402],[-157.856,21.404],[-157.856,21.404],[-157.856,21.406],[-157.856,21.406],[-157.856,21.408],[-157.854,21.408],[-157.854,21.408],[-157.852,21.408],[-157.852,21.408],[-157.85,21.408],[-157.85,21.408],[-157.848,21.408],[-157.848,21.406],[-157.848,21.406],[-157.848,21.404],[-157.848,21.404],[-157.848,21.402],[-157.848,21.402],[-157.848,21.4],[-157.85,21.4],[-157.85,21.4],[-157.852,21.4],[-157.852,21.4],[-157.854,21.4],[-157.854,21.4],[-157.856,21.4]
],[
[-157.854,21.404],[-157.854,21.404],[-157.854,21.402],[-157.852,21.402],[-157.852,21.402],[-157.85,21.402],[-157.85,21.404],[-157.85,21.404],[-157.85,21.406],[-157.852,21.406],[-157.852,21.406],[-157.854,21.406],[-157.854,21.404]
]],[[
[-157.856,21.41],[-157.856,21.412],[-157.856,21.412],[-157.856,21.414],[-157.856,21.414],[-157.856,21.416],[-157.856,21.416],[-157.856,21.418],[-157.854,21.418],[-157.854,21.418],[-157.852,21.418],[-157.852,21.418],[-157.85,21.418],[-157.85,21.418],[-157.848,21.418],[-157.848,21.416],[-157.848,21.416],[-157.848,21.414],[-157.848,21.414],[-157.848,21.412],[-157.848,21.412],[-157.848,21.41],[-157.85,21.41],[-157.85,21.41],[-157.852,21.41],[-157.852,21.41],[-157.854,21.41],[-157.854,21.41],[-157.856,21.41]
],[
[-157.854,21.414],
[-157.854,21.416],
[-157.852,21.416],
[-157.852,21.416],
[-157.85,21.416],
[-157.85,21.414],
[-157.85,21.414],
[-157.85,21.412],
[-157.852,21.412],
[-157.852,21.412],
[-157.854,21.412],
[-157.854,21.414],
[-157.854,21.414]
]]
]}


ClojreScript + re-frame

Repo: https://github.com/jacekschae/conduit
Demo: https://jacekschae.github.io/conduit/
Todo:

[x]  🏁 Fork the starter repo & post the link in this issue
[x]  🎨 Create logo for repo & update issue status (@EricSimons)
[x]  🔨 Implement all of Conduit's functionality per the spec & API
[ ]  👀 Move repo to main org & Peer review final codebase by admins/community (RFC)
[ ]  🎉 Tag v1 release and officially list it on the README!

I saw that there is #74 but felt like starting from scrach

Hi @EricSimons, what would be the next step here? Is there anything else you would expect me to do here?

@jacekschae incredible work!! So sorry about my delay here, I'm just seeing this now 😅  I just spun up the official repo and added you to it: https://github.com/gothinkster/clojurescript-reframe-realworld-example-app
Listing on the main readme now— thanks so much for all your hard work here & congrats sir!  🍻

@EricSimons thanks for RealWorld! All of this wouldn't be possible without this project.


Formatting imports jumps between prettier formatting

Describe the bug
Auto Imports seems to be interfering with prettier formatting still. Might be related to https://github.com/daidodo/format-imports-vscode/issues/39
To Reproduce
Format this file:
import { HttpClient, HttpErrorResponse, HttpHeaders, HttpParams, HttpResponse } from '@angular/common/http';

// use the imports to avoid removal
console.log('HttpResponse', HttpResponse);
console.log('HttpParams', HttpParams);
console.log('HttpHeaders', HttpHeaders);
console.log('HttpErrorResponse', HttpErrorResponse);
console.log('HttpClient', HttpClient);

with following VS Code settings:
  "tsImportSorter.configuration.autoFormat": "off",
  "tsImportSorter.configuration.development.enableDebug": false,
  "tsImportSorter.configuration.wrappingStyle": "prettier",

  "[typescript]": {
    "editor.codeActionsOnSave": [
      "source.addMissingImports",
      "source.organizeImports.sortImports",
      "source.formatDocument",
      "source.fixAll.eslint"
    ]
  },

Expected behavior
TS Import sorter should allow prettier to handle the formatting for line length.
Actual behavior
Formatting for long lines jumps between formatted an unformatted.
Screenshots

OS (please complete the following information):

OS: Mac
Version: v7.5.1

VS Code (please complete the following information):
Version: 1.72.0-insider (Universal)
Commit: 64bbfbf67ada9953918d72e1df2f4d8e537d340e
Date: 2022-10-04T23:18:32.134Z
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 21.6.0
Sandboxed: Yes

Installed VS Code extensions
rohit-gohri.format-code-action: https://github.com/rohit-gohri/vscode-format-code-action

.prettier.yml
tabWidth: 2
semi: true
singleQuote: true
printWidth: 100
trailingComma: none

.eslintrc.json
{
  "root": true,
  "ignorePatterns": [
    "projects/**/*",
    "!**/*.ts",
    "!**/*.html"
  ],
  "overrides": [
    {
      "files": [
        "*.ts"
      ],
      "parser": "@typescript-eslint/parser",
      "parserOptions": {
        "ecmaVersion": 2018,
        "project": [
          "tsconfig.json"
        ],
        "createDefaultProgram": false
      },
      "plugins": [
        "ban"
      ],
      "extends": [
        "plugin:@angular-eslint/recommended",
        "eslint:recommended",
        "plugin:@typescript-eslint/recommended",
        "plugin:@typescript-eslint/recommended-requiring-type-checking",
        "plugin:@angular-eslint/template/process-inline-templates",
        "plugin:@angular-eslint/recommended--extra"
      ],
      "rules": {
        "@angular-eslint/component-class-suffix": "error",
        "@angular-eslint/contextual-lifecycle": "warn",
        "@angular-eslint/directive-class-suffix": "error",
        "@angular-eslint/no-conflicting-lifecycle": "warn",
        "@angular-eslint/no-forward-ref": "off",
        "@angular-eslint/no-host-metadata-property": "warn",
        "@angular-eslint/no-input-rename": "warn",
        "@angular-eslint/no-output-native": "warn",
        "@angular-eslint/no-output-on-prefix": "warn",
        "@angular-eslint/no-output-rename": "error",
        "@angular-eslint/use-lifecycle-interface": "error",
        "@typescript-eslint/adjacent-overload-signatures": "warn",
        "@typescript-eslint/await-thenable": "warn",
        "@typescript-eslint/ban-ts-comment": "warn",
        "@typescript-eslint/ban-types": "warn",
        "@typescript-eslint/explicit-module-boundary-types": "off",
        "@typescript-eslint/indent": [
          "error",
          2
        ],
        "@typescript-eslint/member-ordering": "warn",
        "@typescript-eslint/naming-convention": [
          "error",
          {
            "selector": "class",
            "format": [
              "PascalCase"
            ]
          }
        ],
        "@typescript-eslint/no-empty-function": "error",
        "@typescript-eslint/no-empty-interface": "warn",
        "@typescript-eslint/no-explicit-any": "warn",
        "@typescript-eslint/no-floating-promises": "warn",
        "@typescript-eslint/no-inferrable-types": "off",
        "@typescript-eslint/no-misused-promises": "warn",
        "@typescript-eslint/no-namespace": "warn",
        "@typescript-eslint/no-shadow": "error",
        "@typescript-eslint/no-this-alias": "warn",
        "@typescript-eslint/no-unnecessary-type-assertion": "warn",
        "@typescript-eslint/no-unsafe-assignment": "warn",
        "@typescript-eslint/no-unsafe-call": "warn",
        "@typescript-eslint/no-unsafe-member-access": "warn",
        "@typescript-eslint/no-unsafe-return": "warn",
        "@typescript-eslint/no-use-before-define": [
          "warn",
          {
            "functions": false,
            "classes": false,
            "typedefs": true
          }
        ],
        "@typescript-eslint/no-var-requires": "warn",
        "@typescript-eslint/prefer-regexp-exec": "warn",
        "@typescript-eslint/require-await": "off",
        "@typescript-eslint/restrict-plus-operands": "warn",
        "@typescript-eslint/restrict-template-expressions": "warn",
        "@typescript-eslint/type-annotation-spacing": "error",
        "@typescript-eslint/unbound-method": "warn",
        "ban/ban": [
          "error",
          {
            "name": "fit",
            "message": "Don't keep jasmine focus methods"
          },
          {
            "name": "fdescribe",
            "message": "Don't keep jasmine focus methods"
          }
        ],
        "brace-style": [
          "error",
          "1tbs"
        ],
        "curly": "error",
        "eol-last": "error",
        "eqeqeq": [
          "error",
          "always",
          {
            "null": "ignore"
          }
        ],
        "getter-return": "warn",
        "id-blacklist": "off",
        "id-match": "off",
        "indent": "off",
        "keyword-spacing": "error",
        "max-len": [
          "error",
          {
            "ignorePattern": "^import [^,]+ from |^export | implements | ('|\")(http|https):",
            "code": 140
          }
        ],
        "no-bitwise": "error",
        "no-caller": "error",
        "no-console": "error",
        "no-debugger": "error",
        "no-duplicate-imports": "error",
        "no-empty": "error",
        "no-empty-pattern": "warn",
        "no-eval": "error",
        "no-extra-boolean-cast": "warn",
        "no-fallthrough": "warn",
        "no-irregular-whitespace": "error",
        "no-new-wrappers": "error",
        "no-prototype-builtins": "warn",
        "no-redeclare": "warn",
        "no-restricted-imports": [
          "error",
          {
            "paths": [
              {
                "name": "@synerg/components",
                "message": "Please specify full Synerg component path starting with @synerg/components/"
              },
              {
                "name": "rxjs/Rx",
                "message": "No import from rxjs/Rx"
              },
              {
                "name": "rxjs/src",
                "message": "No import from rxjs/src. Import from rxjs"
              },
              {
                "name": "rxjs/internal/operators",
                "message": "No import from rxjs/internal/operators. Import from rxjs/operators"
              },
              {
                "name": "rxjs/internal",
                "message": "No import from rxjs/internal. Import from rxjs"
              },
              {
                "name": "rxjs/index",
                "message": "No import from rxjs/index. Import from rxjs"
              },
              {
                "name": "node_modules",
                "message": "No import from node_modules"
              }
            ],
            "patterns": ["rxjs/internal/*"]
          }
        ],
        "no-trailing-spaces": "error",
        "no-underscore-dangle": "off",
        "no-unused-expressions": "warn",
        "no-unused-vars": [
          "error",
          {
            "argsIgnorePattern": "^_"
          }
        ],
        "no-useless-escape": "warn",
        "no-var": "warn",
        "object-curly-spacing": [
          "error",
          "always"
        ],
        "prefer-const": "warn",
        "prefer-rest-params": "warn",
        "semi-spacing": "error",
        "quotes": [
          "error",
          "single",
          {
            "allowTemplateLiterals": true,
            "avoidEscape": true
          }
        ],
        "semi": "error",
        "semi-style": [
          "error",
          "last"
        ],
        "space-before-function-paren": [
          "error",
          {
            "anonymous": "never",
            "named": "never",
            "asyncArrow": "always"
          }
        ],
        "space-in-parens": "error",
        "spaced-comment": "error"
      }
    },
    {
      "files": [
        "*.html"
      ],
      "extends": [
        "plugin:@angular-eslint/template/recommended"
      ],
      "parser": "@angular-eslint/template-parser",
      "rules": {
        "@angular-eslint/template/no-negated-async": "warn",
        "@angular-eslint/template/eqeqeq": "warn"
      }
    }
  ]
}

Thanks for the feedback!
You can set line wrapping style to be compatible with Prettier. More details: https://github.com/daidodo/format-imports/wiki/Line-Wrapping-Style#prettier-compatibility
Please tell me if you still have questions.

I already have this setting enabled: "tsImportSorter.configuration.wrappingStyle": "prettier" and it doesn't seem to fix the problem.

The correct output should be having those imports split across several lines. If I disable this extension and let prettier handle formatting, the code is formatted properly.
If I disable prettier and let this extension format the code, the output is incorrect with all of the imports on a single line.

I had the "jumping around on every save" issue, and setting "tsImportSorter.configuration.wrappingStyle": "prettier" fixed it for me. Thank you.

I had the "jumping around on every save" issue, and setting "tsImportSorter.configuration.wrappingStyle": "prettier" fixed it for me. Thank you.

In the above, I already have this setting and it hasn't fixed the issue.

The real fix here would be to remove formatting responsibilities from this extension and have it purely handle sorting.

actually I think I found a problem maybe? see: https://github.com/daidodo/format-imports/blob/a60a7fe8eb727f9e9856591ef12dd278fbc8a9da/src/lib/config/prettier.ts#L18C1-L27C16
the config values don't match prettier, for example:
prettier uses printWidth not maxLineLength.  So when you say have 120 for the printWidth config in prettier, you see the inconsistency in formatting.
It seems I fixed it by adding maxLineLength to my prettier config file (which is not ideal but does seem to solve the issue for now).

I'm having this issue too and it's very frustrating.

remove formatting responsibilities

@Nxt3 How?

I don't have an answer to that. Someone needs to submit a PR with those changes. There isn't a fix for this currently.

Sorry for the late response!
The long-term solution is to migrate the extension to a Prettier plugin. But I don't have time ATM. I'd appreciate if anyone want to help.
Another workaround is to add the following settings with help of this extension:
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.codeActionsOnSave": [
    "source.formatDocument",
    "source.organizeImports.sortImports"
  ],

Unfortunately that doesn't solve the problem as it just makes TS Importer/Sorter the formatter for imports; if someone else working in your project doesn't have this VS Code extension, their Prettier will undo the formatting changes causing an unnecessary diff.

    "editor.codeActionsOnSave": [
      "source.addMissingImports",
      "source.organizeImports.sortImports",
      "source.formatDocument", // prettier
      "source.fixAll.eslint"
    ]
    ```

It still causes the imports to change formatting on every save.

[This is referenced in the OP](https://github.com/daidodo/format-imports-vscode/issues/91#issue-1553501453)

I think I fixed this by adding another prettier call:
    "editor.codeActionsOnSave": [
      "source.addMissingImports",
      "source.organizeImports.sortImports",
      "source.formatDocument",
      "source.formatDocument",
      "source.fixAll.eslint"
    ],

I not longer have the jump in formatting.

It's frustrating. Thinking of uninstalling this extension, I'm afraid.

I think I came up with a better solution when compared to running formatDocument twice.
Download this extension: stereokai.vscode-run-commands-as-code-actions
It allows us to add delays to code actions run on save so you can "waterfall" the commands.
Add this to your settings.json:
  "run-commands-as-code-actions.jsTsFormatAndLint": [
    {
      "command": "tsImportSorter.command.sortImports",
      "delay": 100
    },
    {
      "command": "prettier.forceFormatDocument",
      "delay": 150
    },
    {
      "command": "eslint.executeAutofix",
      "delay": 200
    },
    {
      "command": "workbench.action.files.saveWithoutFormatting",
      "delay": 250
    }
  ],
    "[typescript]": {
    // here's the magic
    "editor.codeActionsOnSave": ["source.addMissingImports", "source.runCommandsAsCodeActions.jsTsFormatAndLint"],
    "editor.defaultFormatter": "esbenp.prettier-vscode",
    "editor.formatOnSave": false,
  },

This will add missing imports, then run the actions defined under jsTsFormatAndLint: Sort imports, format using prettier, eslint fix, and then save the file. This has been working great for me for a couple of weeks now.

Thanks for sharing, still a problem with the delays of 100, 150 or 200 - how will you know the previous action did really complete before starting the next one? Especially in large code bases.

Thanks for sharing, still a problem with the delays of 100, 150 or 200 - how will you know the previous action did really complete before starting the next one? Especially in large code bases.

The extension author could probably answer that better.

After months of working fine, I got this again (after moving some eslint config files around). Very frustrating. But then I restarted VSCode and it worked again. Shrug.

....and it happened again. I had to restart a couple of times before it worked correctly. My guess is that every time you start VS Code, the 'order' of extensions that can format-on-save changes, and you just have to keep restarting until Prettier beats this (or vv, which ever you prefer)


support for rustup componenets

Hi,
I would like to request if in the next version when you lock the nightly version if you could try to aim for a nightly that contains also these components:  clippy, rls, rust-analysis, rust-src
(You can check via rustup component list )
Thanks,
Elichai.

Thanks!

Hi @elichai , I notice that some nightly builds do not provide clippy (cannot find it in rustup component list). Do you know if there is a list to see what date it is available? Thanks!

Just found this
https://rust-lang.github.io/rustup-components-history/
Do you have any idea about what nightly date we should use (to support built-in clippy)?

It actually doesn't look so good right now.
Clippy seems to fall a apart a bit right now https://github.com/rust-lang/rust/pull/59617
And if this is correct then 23-3  :(
https://rust-lang-nursery.github.io/rust-toolstate/

@dingelish If I understand correctly everything is fixed now :)
https://github.com/rust-lang/rust/pull/59810
https://rust-lang-nursery.github.io/rust-toolstate/


Label doesn't work in Ubuntu wallet 1.4.3

Label in newest wallet doesn't work. (tested on ubuntu)
When renaming the account in wallet 1.4.3, after wallet restart it still showing label with an address as a name.
Also, when u create new accounts in wallet, it disappear from the list after the wallet restart.

Weird, I've tried myself and I couldn't reproduce the problem. @slydamus could you provide us with additional information?

Someone on ark slack offered a solution.
I removed version 1.4.3 and leave ~/.config/ArkClient directory intact (ubuntu 16.04), and then installed version 1.2.2 that "fixed" the problem, and then I installed again latest 1.4.3 and now it's working fine.
So, now I don't have problematic config files to send it to you, but I will try to recreate the bug and if I will be successful I will contact you.


Ser resource limits when deploying the chart

Hi!
Thanks for such a great 5g chart!
Following your tutorial, I can successfully deploy the k8s 5g and test its performance.
I have an extra need to set the resource limits that can be used by each pod.
Could you please give me some suggestions on how to add these resource parameters when deploying the charts using value.yaml?
Thanks a lot!

I find the solution myself.
Just add
resources:
limits:
cpu: 100m
memory: 128Mi
f
for the target NF in the value.yaml.


Bump minimum Swift version to 5.7

Motivation:
Now that Swift 5.9 is GM we should update the supported versions and remove 5.6
Modifications:

Update Package.swift
Remove #if swift(>=5.7) guards
Delete the 5.6 docker compose file and make a 5.10 one
Update docs

Result:
Remove support for Swift 5.6, add 5.10

@swift-server-bot add to allowlist

@yim-lee can we remove the 5.6 builder?

@swift-server-bot test this please

CI updated. @swift-server-bot test this please


Open ModSim is returning an incorrect exception code.

It's a more technical error.
Open ModSim is returning an incorrect exception code.
For example:
If you ask for function 01 (coil) and in ModSim there is only function 03 (holding), OpenModSim returns "invalid address" instead of "invalid function".

It looks like this error is returned by modbus stack qt.

I understand, in this case you have to wait for the QT library to be fixed.


[Question]: error at parsing files uploaded in demo

Describe your problem
I tired to use the demo at demo.ragflow.io.
And when I click green triangle button (between "Parsinf status" and "Action") parsinf fails.
I can only see "Process Begin At:
Fri, 20 Sep 2024 13:43:04 GMT
Process Duration:
16.00 s
Progress Msg:
2
ERROR: Task is abandoned after 3 times attempts."
This happens with different files and file formats.
Chunk Method is "Knowledge graph"

Can you chat with the default LLM that is in system settings?
Make sure your API-key is valid for your choosen LLM.