Update KES Errors to resolve permissions on February 2023+ releases

Minio is currently not starting in our environment after upgradeing to the newest release in combination with KES
Error: not authorized: insufficient permissions (kes.Error)
We are unable to find out if there was a change in minio which needs more permissions to use KMS?

API-Documentation of KES did not change since 2022, and we've upgraded from a Jan 23 release to the newest
https://github.com/minio/kes/wiki/Server-API#api-overview

These endpoints we're the only one needed before and it seems like minio needs more with newer releases?

   - /v1/key/create/*
   - /v1/key/generate/*
   - /v1/key/decrypt/*

Expected Behavior

Minio should start as usual

Current Behavior
Mär 28 13:51:57 minio2 minio[13835]: Documentation: https://min.io/docs/minio/linux/index.html
Mär 28 13:51:57 minio2 minio[13835]: API: SYSTEM()
Mär 28 13:51:57 minio2 minio[13835]: Time: 11:51:57 UTC 03/28/2023
Mär 28 13:51:57 minio2 minio[13835]: DeploymentID: e425c60c-3de5-42d3-81c5-09a620eaf8c6
Mär 28 13:51:57 minio2 minio[13835]: Error: not authorized: insufficient permissions (kes.Error)
Mär 28 13:51:57 minio2 minio[13835]:        5: internal/logger/logger.go:258:logger.LogIf()
Mär 28 13:51:57 minio2 minio[13835]:        4: cmd/api-errors.go:2280:cmd.toAPIErrorCode()
Mär 28 13:51:57 minio2 minio[13835]:        3: cmd/api-errors.go:2305:cmd.toAPIError()
Mär 28 13:51:57 minio2 minio[13835]:        2: cmd/healthcheck-handler.go:134:cmd.LivenessCheckHandler()
Mär 28 13:51:57 minio2 minio[13835]:        1: net/http/server.go:2109:http.HandlerFunc.ServeHTTP()

Possible Solution

After removing the "policy" section in kes config and enable admin identity minio is working again.

Steps to Reproduce (for bugs)

Upgrade to RELEASE.2023-03-24T21-41-23Z
restarting minio service results in error above
upgrade KES to 2023-02-15T14-54-37Z did not fix it

Context

Upgraded MINIO from a release of january to:

minio version RELEASE.2023-03-24T21-41-23Z (commit-id=74040b457b50417b58eae7cb17c63428a0e2dd44)
kes 2023-02-15T14-54-37Z (commit=8ce403b264e3c6fafb94577dd1c59ae811963e43)

Your Environment
We have set the following Env vars for minio regaring KES:
MINIO_KMS_KES_ENDPOINT
MINIO_KMS_KES_ENDPOINT
MINIO_KMS_KES_CERT_FILE
MINIO_KMS_KES_KEY_FILE
MINIO_KMS_KES_CAPATH
MINIO_KMS_KES_KEY_NAME

This was our kes-config before the upgrade

address: <IP_ADDRESS>:7373

admin:
  identity: disabled

root: disabled

tls:
  key:  /minio/certs/private.key
  cert: /minio/certs/public.crt

policy:
  minio-kes:
    allow:
    - /v1/key/create/*
    - /v1/key/generate/*
    - /v1/key/decrypt/*
    identities:
    - ABCD

log:
  error: on
  audit: on

keystore:
  vault:
    endpoint: https://vault:8200
    engine: "minio-kes"
    version: "v2"
    approle:
      id: "YYYYYYY"
      secret: "ZZZZZZZ"
      retry: 15s
    status:
      ping: 10s

This is our kes-config AFTER the upgrade to fix the issue

address: <IP_ADDRESS>:7373

admin:
  identity: ABCD

root: disabled

tls:
  key:  /minio/certs/private.key
  cert: /minio/certs/public.crt

log:
  error: on
  audit: on

keystore:
  vault:
    endpoint: https://vault:8200
    engine: "minio-kes"
    version: "v2"
    approle:
      id: "YYYYYYY"
      secret: "ZZZZZZZ"
      retry: 15s
    status:
      ping: 10s

@tsohst just to confirm, what January release were you using?

We came from RELEASE.2023-01-02T09-40-09Z

admin:
identity: ABCD

This is also the correct way to do it, calling MinIO connection as 'admin:' is the correct approach if you don't want to play around with allow: policies.

So we'll do two things here:

Update the policy guidance to include the recommended admin approach and the more constrained policy approach
Use this as a chance to do the API-key approach and simplify the setup further

It looks like the February release forward is where this change happens.. That recency is probably why we are not seeing more of this in the wild. Updating the docs here will help.

You need to add
allow:
    - /v1/key/create/*
    - /v1/key/generate/*
    - /v1/key/decrypt/*
    - /v1/key/list*
    - /v1/status
    - /v1/metrics

Can confirm it is working with these permissions.

The remainder of this work is covered in #912


ignore no dataToken error

updates the query path to not set the dataToken to the response if it doesn't exist.  It will only not exist on a brand new system, where no data has been loaded into Kaskada.
After skipping setting the dataToken field, the code correctly returns the failed compilation instead, including helpful fenl diagnostics.
Old Behavior:
> ./kaskada_cli table list
(empty set)
> ./kaskada_cli query run Purchase
9:01PM FTL  error="rpc error: code = NotFound desc = data_token not found"

New Behavior:
> ./kaskada_cli query run Purchase

state: STATE_FAILURE
config: {}
analysis: {}
fenlDiagnostics:
  fenlDiagnostics:
  - severity: SEVERITY_ERROR
    code: E0006
    message: Unbound reference
    formatted: |+
      error[E0006]: Unbound reference
        --> Query:1:1
        |
      1 | Purchase
        | ^^^^^^^^ No reference named 'Purchase'
        |
        = No formulas, tables, or let-bound names available

  numErrors: "1"
metrics: {}
requestDetails:
  requestId: aaafdf41a2604f771e38207568455cce

fixes #326


[Bug] Copy Selelctor hides Image Preview options

Describe the Bug
Right-click options are gone when "Copy Selector" is enabled.
To Reproduce
Turn on "Developer Mode" and "Copy Selector", and right-click an image popup.
Expected Behavior
Options to copy/save image previews, copy/open links, in addition to Copy Selector.
Screenshots

Discord Version
Stable, Mac OS X 10.11.6

I can recreate this, but it is low on the priority list.

This feature has been sunset and will be discontinued in the restructure.


Fastnlight: Watch jun88tc.com

Fastnlight requests the watch of the watch_keyword jun88tc\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

jun88tc\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


ENH: Update session

This PR has the following changes:

Now session should be passed to task classes. Else, empty session is created.
Deprecated session.get_task

Codecov Report

Merging #79 (b77a356) into master (05861b7) will decrease coverage by 0.01%.
The diff coverage is 91.66%.

@@            Coverage Diff             @@
##           master      #79      +/-   ##
==========================================
- Coverage   91.10%   91.09%   -0.02%
==========================================
  Files          88       88
  Lines        4339     4344       +5
==========================================
+ Hits         3953     3957       +4
- Misses        386      387       +1

Impacted Files
Coverage Δ

rocketry/core/task.py
93.01% <87.50%> (+0.05%)
:arrow_up:

rocketry/core/schedule.py
89.65% <100.00%> (-0.35%)
:arrow_down:

rocketry/session.py
91.53% <100.00%> (+0.03%)
:arrow_up:

rocketry/utils/dependencies.py
84.00% <100.00%> (ø)

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


Secrets are mismatched with readme

I can also alter the readme; not sure if there is a specific preference.

This was indeed wrong, this is due to the slight difference between the DuckDB maintained once that fetch their secret from the organization. There's a chance this will break the deploy on the ci of this repo now, but that I can solve tomorrow by updating the key in this repo's secrets


Add back xgboost.rabit in 1.7

Closes #8406 by making xgboost.rabit available in 1.7. Also add a warning to direct users to use xgboost.collective instead.

@trivialfis @rongou Can I get a review for this?

@hcho3 the problem is this won't work for xgboost any more since the c++ code depends on the communicators. If we have to keep the existing api, one option is to delegate everything to the xgboost.collective module.

@rongou Doesn't xgboost.collective fall down to Rabit in the default setting? For example, xgboost.collective.init() calls rabit::Init internally.

Yes but it needs to set up the RabitCommunicator.

@rongou I see. Do you have bandwidth to set up the delegation to xgboost.collective? I can give it a try, but I'm afraid I'd get it wrong, given the substantial difference between xgboost.collective.init (takes in dictionary) and xgboost.rabit.init (takes in list of strings)

Ok I'll take a look.

Thanks! Let me know if there's anything I can help. Also, feel free to file a new pull request when you're done.

Do we just want to add back init/finalize to fix modin, or do you want to add all other functions too?

@rongou Let's try to add all functions.


btcpayserver: optional altcoin support

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

In use on https://github.com/fort-nix/nix-bitcoin/pull/369

@GrahamcOfBorg build btcpayserver

Very interesting, I'm getting /build/source/BTCPayServer/BTCPayServer.csproj : error NU1101: Unable to find package Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation. No packages exist with this id in source(s): tmpsrc when running with a deps.nix generated by update.sh without /p:RazorCompileOnBuild=false, see for yourself with this test. /p:RazorCompileOnBuild=false seems unnecessary in the default.nix though, see for yourself with this test. Removed there and added comment.

Very interesting, I'm getting /build/source/BTCPayServer/BTCPayServer.csproj : error NU1101: Unable to find package Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation. No packages exist with this id in source(s): tmpsrc when running with a deps.nix generated by update.sh without /p:RazorCompileOnBuild=false, see for yourself with this test.~/p:RazorCompileOnBuild=false seems unnecessary in the default.nix though, see for yourself with this test. Removed there and added comment.~
EDIT: Needed in both test failing with fail: Configuration: This build of BTCPay Server does not support altcoins

Actually, now I'm not sure. The error might be due to the test script. Running fine with the nix-bitcoin test suite based on https://github.com/nixbitcoin/nixpkgs/commit/50fc1b2b2bcb3438431a2c3c03b6c29e00e940db without RazorCompileOnBuild=false in the default.nix.


Problems geting 3D fix when using dynamic mode

I am having trouble getting a 3D fix on u-center when using my own user motion file in lat, lon, height format.
However I have no issues getting a fix when testing using the circle_llh.csv present in the source folder.
Are there any requirements when creating your own user motion file that I am missing such as minimum time required etc. ?
I am also using the latest brdc file as of today but could not get the fix.
Any help would be appreciated, thank you.

I think it is probably the oscillator source. Which SDR are u using ?

I'm currently using a HackRF One

Ok, try using a better oscillator source instead of driving from native oscillator on it.

any update?

Did you try using a better oscillator source ? Also,  did u use satgen software to create your own user motion file ? Are you able to get a fix for static co-ordinates ?

I cant get a stable 3d fixed with static mode.
for pluto SDR i replaced the crystal with a 0.5ppm model: DSB321SDN 40M 40.000MHZ 3225 TCXO XTW40000PBA.
Receiver is U-Blox M8030 72ch.
but my iphone 8 and iphone 14 can’t be spoofed. The phone with SIM and 4g turned on.
for dynamic mode, I didn’t test yet

Ok, I understand that you are trying to get a static fix. I too have tried with Adalm, but didn't get much success. Then I switched to BladeRF & also disciplined the clock using an external Oscillator : http://www.leobodnar.com/shop/index.php?main_page=product_info&cPath=107&products_id=301&zenid=00f38f6a4772c583eec624ecc6cbb773

Thank you very much for your information sharing.
Now the reason is clearly because of the accuracy of the oscillator, maybe use an external vctxco or ocxo just like https://www.mictronics.de/posts/ADLAM-Pluto-OCXO-Mod/, with a higher accuracy 0.01ppm. But I don’t test it yet.
my idea is, can we add some software filter to I/Q to improve the output signal quality with current 0.5 ppm oscillator?

Sorry, I wasn't able to access the link that you have provided. Yet, like you have said, the accuracy is better, so you should give it a try. But I am not sure of the RF pad & track for the oscillator in Pluto i.e., if you provide signal from an external oscillator , I am not sure of the attenuation of the signal. However, in boards like USRP, there is an external connector for the clock which can maintain the impedance.
I think the signal generation from the transmitter is good enough, as it depends upon the RF front end which is an AD9363/64 on the Pluto and therefore we only need to concentrate upon the input clock. However, I might be wrong on this & it will be nice in case some experts comment upon this.

@wthiam002 Regarding your motion file issue, this may help: https://github.com/osqzss/gps-sdr-sim/issues/301

That means you locked the frequency with an external clock source. Then signal quality improved and worked with the receiver devices. I will try to do that. Thank you.


Copycat on Google Play

Hi @calintat
I found this app: https://play.google.com/store/apps/details?id=com.applicationlab.android.bestunitconverter on the Google Play Store. This guy just took your source code, added some ads in it and put it on the Store, without warning this is free software...
As you are the owner of the source code, feel free to open a request to google here to remove this copy from the Store, if it's your wish ;)
Don't forget to tell Google that:

The app is licensed under Apache v2 license and this guy is violating it;
He is falsely claiming he made the app;
Provide some screenshots of your own app.

This copycat is down now, I'm closing this Issue.
Please report here in the future if you find other copycats.


TUIO 2.0

Hi @nosuchtim, I am the developer of the TUIO protocol, and I recently got back working on TUIO 2.0, which may be relevant for the Sensel Morph device, since it also supports the necessary pressure attributes for example. I am thinking about getting such a device, since it would be a great example platform taking advantage of the new TUIO2 capabilities.
http://www.tuio.org/?tuio20
There is already some example code here, which could be integrated into your app instead of TUIO11 https://github.com/mkalten/TUIO20_CPP
Since I'd be also interested in testing the device, are you in any way affiliated to Sensel Morph?

Hi Martin,
The Morph is indeed fantastic.
I've used TUIO heavily for many years, thank you for developing it.  I've given the 2.0 version a look, thanks for the pointer to the example code.  I love TUIO for cursor information, and I found it natural to use the 'z' value in a 25D profile to represent the Morph's pressure.  When I needed (years ago) to send lots and lots of data (e.g. the contours of many large objects, 60fps), I ended up doing it with shared memory in order to make it faster.  This TUIO3D_Sensel app supports either TUIO or the shared memory interface.  I'm very content with TUIO, so my motivation to add TUIO2 support is low, but perhaps someone can use this app as a starting point for TUIO2 support.
I'm not affiliated with Sensel, I'm just a very grateful customer.
 ...Tim...

Thanks for the clarification @nosuchtim !
Although it's quite easy to extend or circumvent missing TUIO 1.1 features through custom OSC messages, or the "alternative" use of attributes, TUIO 2.0 actually intends to represent these new features such as Pressure and Blob Contour in a proper way. While I understand that these modifications work fine for personal use, this unfortunately also breaks the compatibility with standard TUIO layers.
Since I am planning to get one of those Sensel Morph devices, I will probably have a look at porting your code to the new TUIO 2.0 protocol generation, since its seems to be a nice use case for its extended features.
I'll keep you posted ... Martin.K


Fails to build with autoconf 2.70

I haven't had a chance to reproduce this myself and come up with a patch, but in case you are preparing a new release soon, it might be worth trying it with autoconf 2.7.0 since it appears to be broken with that version: https://bugs.debian.org/978877

Also, FYI, if you'd like 0.22 in the next stable versions of Debian and Ubuntu, the deadline is Feb 2nd.

Also, FYI, if you'd like 0.22 in the next stable versions of Debian and Ubuntu, the deadline is Feb 2nd.

@fmarier Thanks for the head's up, I'm still rocking AC 2.69 locally.  I'll have to pluck down the latest, test this out, and see if I can fix it, thanks again.

@fmarier Thanks for the head's up, I'm still rocking AC 2.69 locally.  I'll have to pluck down the latest, test this out, and see if I can fix it, thanks again.

@fmarier I've created an updated configure and configure.ac.  I think/hope this solves the issue that Debian is experiencing.
https://github.com/enferex/pdfresurrect/tree/fix-config

@fmarier I've created an updated configure and configure.ac.  I think/hope this solves the issue that Debian is experiencing.
https://github.com/enferex/pdfresurrect/tree/fix-config

I'm having problems reproducing the build failure with autoconf 2.70. My apologies, I should have tried that first before filing this bug :/ Were you able to see the current version of pdfresurrect fail to build with 2.69?
With respect to your fix, I think the following will be problematic on distros that use an earlier version of autoconf:
-AC_PREREQ(2.61)
+￼AC_PREREQ([2.70])

Let me ask the Debian reporter more information and let's park this issue until he gets back to me. With respect to the next stable version of Debian/Ubuntu, it's not a big deal anyways because they're going to ship with autoconf2.69. So if you've got other fixes you'd like to see in these distros, feel free to release without addressing any autoconf2.70 issues.

I'm having problems reproducing the build failure with autoconf 2.70. My apologies, I should have tried that first before filing this bug :/ Were you able to see the current version of pdfresurrect fail to build with 2.69?
With respect to your fix, I think the following will be problematic on distros that use an earlier version of autoconf:
-AC_PREREQ(2.61)
+￼AC_PREREQ([2.70])

Let me ask the Debian reporter more information and let's park this issue until he gets back to me. With respect to the next stable version of Debian/Ubuntu, it's not a big deal anyways because they're going to ship with autoconf2.69. So if you've got other fixes you'd like to see in these distros, feel free to release without addressing any autoconf2.70 issues.

No worries! I still think it's good to at least be prepared for the autoconf update.

Were you able to see the current version of pdfresurrect fail to build with 2.69?

I have no issues building with 2.69.  I do have one change for the upcoming debian update, which I plan on cutting a release the next two weeks.

No worries! I still think it's good to at least be prepared for the autoconf update.

Were you able to see the current version of pdfresurrect fail to build with 2.69?

I have no issues building with 2.69.  I do have one change for the upcoming debian update, which I plan on cutting a release the next two weeks.

Another datapoint: I am able to build pdfresurrect 0.23 with no problems on macOS 10.15.7, both as shipped with its autoconf-2.69-generated configure script and if I autoreconf with autoconf 2.71.


MP3 support

when sending multimedia files, for example .mp3 and accessed from the shared url the server responds by sending the headers
the problem is in this line
https://github.com/claudiodangelis/qr-filetransfer/blob/master/main.go#L56
http.ServeFile starts the data transmission but when it is a large file it does it in the background and the connection closes in the line
https://github.com/claudiodangelis/qr-filetransfer/blob/master/main.go#L65
that's why the file is never sent completely

If you could add some more info that would be great! For example, do you get an error? Does the QR show up? Could you post the exact command?
Thanks

You know what?  I don't want to see you report another issue ever again.

I've reported @cIaudiodangeIis to Twitter as an abusive account.
Do not confuse this user with @claudiodangelis. Although the names look the same on GitHub.com, this is a troll account. The second letter is an upper case "i" rather than a lower case "l".

Sorry @jerson, as promptly pointed out by @bvaughn, the person who replied to you is a troll account managed by a person with a weird sense of humor.
As per the problem you report, I will look into it later today!

@jerson I'm closing this issue as there is another thread where a solution to this problem is being discussed: https://github.com/claudiodangelis/qr-filetransfer/issues/13
Let's continue there, thank you!


Refactor CHURN to disentangle its mainloop from the proxy's

Currently, the main logic of CHURN runs in the churn-pipe module, but every message is passed to the Churn object for dispatching, and this object runs in the same thread as SocksToRtc or RtcToNet.  As a result, UDP and TCP packets end up fighting for a single thread, resulting in enormous queueing delays and other misbehaviors.  This design may be responsible for the disconnections seen under high load, when CHURN is unable to process a packet for more than 5 seconds (the WebRTC disconnect timeout).
To improve behavior under load, we should move Churn and churn-pipe into a single module, separate from the SocksToRtc/RtcToNet module.  This will also reduce CPU intensity by removing two inter-module IPC calls per packet.

Note to self: use code from
https://github.com/uProxy/uproxy-networking/tree/trevj-remove-churn-pipe-module


How to run the app in Mac

The documents mentions:
cd app
./start.sh
But there is no start.sh file in the app folder. Please help.

This is the series of steps I took:
cd frontend
npm install
npm run build
cd ../backend
pip install -r requirements.txt
python app.py

Getting following exception. Please help:
aiohttp.client_exceptions.WSServerHandshakeError: 404, message='Invalid response status', url=URL('wss://gpt-4o-realtime-preview-testtt.openai.azure.com/realtime?api-version=2024-10-01')


[CHALLENGE SUBMISSION] - Power Automate/Microsoft Flow

Please provide the following information for your submission:
What is your name? (First, Last)
Locksley Kolakowski
Where is your GitHub Repo ?(Link to your challenge solution)
https://github.com/LocksleyLK/seasons-of-serverless/tree/master/Challenge-5
What Challenge is this for? (Challenge number between 1 and 7)
5
(Optional) Anything else we should know? e.g., language used, location, blog post, tell us how you solved this solution, including any challenges you faced solving it.
My solution utilizes Microsoft Flow in Power Automate. According to my research, Microsoft Flow runs on top of Azure Logic Apps 😃.
In my GitHub Repo, I have provided steps on how to recreate my solution and provided some images/gifs demonstrating how it works.
If you would like to test it yourself, I could share my solution with you in Power Automate via email!

thank you for this submission!

thank you for this submission!


Uh-oh! An error occurred in Toolkit for YNAB

Name of Defective Feature

Localization of YNAB

System Settings (Required)

ToolKit Version: 2.8
Operating System (Mac/Windows/Etc): MacOS High Sierra
Browser (Chrome/Firefox/Safari): Chrome
Browser Version: Latest
Other Extensions: 1Password, Adbloker

Export of Toolkit Settings (Bottom Left of Settings Page)

Settings Export
[{"key":"AccountsDisplayDensity","value":"0"},{"key":"AccountsEmphasizedOutflows","value":false},{"key":"AccountsStripedRows","value":false},{"key":"AdjustableColumnWidths","value":false},{"key":"AutoDistributeSplits","value":false},{"key":"BetterScrollbars","value":"0"},{"key":"BudgetCategoryFeatures","value":true},{"key":"BudgetProgressBars","value":"0"},{"key":"BudgetQuickSwitch","value":false},{"key":"CalendarFirstDay","value":"0"},{"key":"CategoryActivityCopy","value":false},{"key":"CategoryActivityPopupWidth","value":"0"},{"key":"ChangeEnterBehavior","value":false},{"key":"CheckCreditBalances","value":false},{"key":"CheckNumbers","value":false},{"key":"ClearSelection","value":false},{"key":"CollapseSideMenu","value":false},{"key":"ColourBlindMode","value":false},{"key":"CompactIncomeVsExpense","value":false},{"key":"CreditCardEmoji","value":false},{"key":"CurrentMonthIndicator","value":false},{"key":"CustomFlagNames","value":false},{"key":"DaysOfBuffering","value":false},{"key":"DaysOfBufferingHistoryLookup","value":"0"},{"key":"DisableToolkit","value":false},{"key":"DisplayTargetGoalAmount","value":"0"},{"key":"DisplayTotalMonthlyGoals","value":false},{"key":"DisplayUpcomingAmount","value":false},{"key":"EasyTransactionApproval","value":false},{"key":"EditAccountButton","value":"0"},{"key":"EnlargeCategoriesDropdown","value":true},{"key":"EnterToMove","value":false},{"key":"GoalIndicator","value":false},{"key":"GoalWarningColor","value":false},{"key":"GoogleFontsSelector","value":"0"},{"key":"HideAccountBalancesType","value":"0"},{"key":"HideAgeOfMoney","value":false},{"key":"HideHelp","value":false},{"key":"HideReferralBanner","value":false},{"key":"HighlightNegatives","value":false},{"key":"ImportNotification","value":"0"},{"key":"IncomeFromLastMonth","value":"0"},{"key":"IncomeVsExpenseHoverHighlight","value":true},{"key":"LargerClickableIcons","value":false},{"key":"MonthlyNotesPopupWidth","value":"0"},{"key":"NavDisplayDensity","value":"0"},{"key":"Pacing","value":"0"},{"key":"PrintingImprovements","value":true},{"key":"PrivacyMode","value":"0"},{"key":"QuickBudgetWarning","value":false},{"key":"ReconciledTextColor","value":"0"},{"key":"RemovePositiveHighlight","value":false},{"key":"RemoveZeroCategories","value":false},{"key":"ResizeInspector","value":false},{"key":"RightClickToEdit","value":true},{"key":"RowHeight","value":"0"},{"key":"RowsHeight","value":"0"},{"key":"RunningBalance","value":"0"},{"key":"SeamlessBudgetHeader","value":false},{"key":"ShowCategoryBalance","value":false},{"key":"ShowIntercom","value":true},{"key":"SpareChange","value":false},{"key":"SplitKeyboardShortcut","value":true},{"key":"SplitTransactionAutoAdjust","value":false},{"key":"SquareNegativeMode","value":false},{"key":"StealingFromFuture","value":false},{"key":"SwapClearedFlagged","value":false},{"key":"TargetBalanceWarning","value":false},{"key":"ToBeBudgetedWarning","value":false},{"key":"ToggleMasterCategories","value":false},{"key":"ToggleSplits","value":false},{"key":"ToggleTransactionFilters","value":"0"},{"key":"TransactionGridFeatures","value":true},{"key":"ViewZeroAsEmpty","value":false},{"key":"l10n","value":"spanish"},{"key":"options.dark-mode","value":false},{"key":"reports","value":true}]

Steps to Reproduce the Behavior

Change localization to "Spanish 83%"
Reload YNAB

Expected Behavior

Use YNAB in Spanish
Actual Behavior

  Error ocurre and cat use YNAB until I set localization back to default .

Thanks for the report! I'm currently rewriting how localization works so this should go away once that's done. Hadn't noticed this once I started though I'll see if I can reproduce and get a fix out for ya.

Thank you so much Josh. Let me know you need something reproducing the issue.
Regards
On Jun 26, 2018, 6:24 PM +0200, Josh Madewell<EMAIL_ADDRESS>wrote:

Thanks for the report! I'm currently rewriting how localization works so this should go away once that's done. Hadn't noticed this once I started though I'll see if I can reproduce and get a fix out for ya.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I encountered this as well, and would love to see a fix pushed out before the full rework of the translation system.

Hey @ATG1209 @mkaito the fix for this should be in our current release! If you notice the issue still exists and you're definitely running the newest version of the toolkit, please reopen! Thanks!
Please note, all browser can take up to an hour to provide updates to all users. You can force an update if it's available for you by going to chrome://extensions and clicking the "Update" button. Firefox users can go to about:addons, click the setting cog, and click "Check for updates...".

It works! Praise be to you!
El 3 de julio de 2018 22:57:35 GMT+01:00, Josh Madewell<EMAIL_ADDRESS>escribió:

Hey @ATG1209 @mkaito the fix for this should be in our current
release!
If you notice the issue still exists and you're definitely running the
newest version of the toolkit, please reopen! Thanks!
Please note, all browser can take up to an hour to provide updates to
all users. You can force an update if it's available for you by going
to chrome://extensions and clicking the "Update" button. Firefox
users can go to about:addons, click the setting cog, and click "Check
for updates...".
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/1371#issuecomment-402303862

--
Enviado desde mi dispositivo Android con K-9 Mail. Por favor, disculpa mi brevedad.

@joshmadewell it now works perfectly, thank you


build fails on master

Os : win 10 pro
Commit : 37b9f896e756411698f4a56bb3877057e77c9b61 on master branch
steps to reproduce :
yarn
npm run build
npm  run test
App fails .
log is attached
npm_log_16_07_2018.txt

I am seeing this on the yarn log
`
./node_modules/electron-debug/index.js 101:45-58
0:0  warning  Critical dependency: the request of a dependency is an expression
./node_modules/electron-debug/index.js 102:61-74
0:0  warning  Critical dependency: the request of a dependency is an expression`

I also have this same error. Although the install does not halt. npm run dev can still be run and npm run test passes all tests. However, after I run npm run dev, I am getting a "unknown service lnrpc.Lightning" error, even though I have the custom lnd executable in resources/bin/linux

Closed with #564


Update LICENSE.md so GitHub reports Apache 2.0 license

Just like https://github.com/AnalyticalGraphicsInc/cesium/pull/5470

Thanks.  As mentioned in the linked issue, this does not change the terms of the license, it just makes it so that GitHub shows the correct license icon.


Android Build failed after upgrade from 0.68.2 to 0.73.4

Old Version
0.68.2
New Version
0.73.4
Description
I have updated the React Native version, but after that, my Android build is failing due to the libraries I have installed. Please tell me how to resolve it.
Steps to reproduce
yarn install
npx react-native run-android
Affected Platforms
Runtime - Android
Output of npx react-native info
System:
  OS: macOS 12.6.1
  CPU: (8) arm64 Apple M1
  Memory: 121.09 MB / 16.00 GB
  Shell:
    version: 5.8.1
    path: /bin/zsh
Binaries:
  Node:
    version: 18.19.0
    path: /opt/homebrew/bin/node
  Yarn:
    version: 1.22.17
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.2.3
    path: /opt/homebrew/bin/npm
  Watchman: Not Found
Managers:
  CocoaPods:
    version: 1.14.3
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 22.2
      - iOS 16.2
      - macOS 13.1
      - tvOS 16.1
      - watchOS 9.1
  Android SDK: Not Found
IDEs:
  Android Studio: 2023.1 AI-231.9392.1.2311.11330709
  Xcode:
    version: 14.2/14C18
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 21.0.2
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.4
    wanted: 0.73.4
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

Stacktrace or Logs
Execution failed for task ':react-native-community_async-storage:compileDebugJavaWithJavac'.
> Could not resolve all files for configuration ':react-native-community_async-storage:androidJdkImage'.
   > Failed to transform core-for-system-modules.jar to match attributes {artifactType=_internal_android_jdk_image, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.

Reproducer
https://github.com/ladybirdweb/faveo-support-app
Screenshots and Videos
No response

react-native-community_async-storage

Please report this to https://github.com/react-native-async-storage/async-storage/issues


HTTP: Debug should show transformed response body instead of original body

I'm using transformResponse to decode a binary response. Although when there is a check error and running in debug mode the original binary body is printed instead of the better readable transformed response body. This makes debugging hard. It makes more sense to print the transformed response body
(version 3.0.3)

Thanks for reporting!

The fix for this seem to allow transforming response time again:
.transformResponse {
  (session, response) =>
    response.copy(endTimestamp = newEndTimestamp)
  }
}

That worked with 2.3.x, but got ignored in 3.0.x. Fortunately it seems to work after this fix.


Rename application.conf to reference.conf

Closing this one as the functionallity was included in https://github.com/input-output-hk/etc-client/pull/105


Can you please migrate to version 8.x and higher?

Hi,
I'm having problems with authenticating admins. If I use client.admins.authviaemail (what is the only way to sign in as an admin to my knowledge), I get the error: Not Found..
The issue is fixed in this GitHub issue.
But, -because I'm using the JS SDK- I still get the issue.
And because I use pockethost I can't downgrade at this moment.

Sorry I see that you already did that.


This addon has gave up to update？

It seems that not any valid update in this year

Well you are in luck, because now there is a new update :)


Code coverage is skipping Azure core

Coverage is not combining all source paths so it skips installed azure core modules
coverage is updated to run for current package
Fixed misc fixes to refer correct arg parser

Can one of the admins verify this patch?

/azp run python - core - ci

/azp run python - keyvault - ci

/azp run python - eventhub - ci


Add Rushi's SSH keys

please test this

please test this

please test this

please rebase

@rushiagr needs to be rebased

@rushiagr ping - please rebase

please test this

builds passed, merging.


Update readme with latest CR changes

Update readme with latest CR changes.
/cc @sjenning

/retest

Not able to reproduce this locally.
/retest

/retest


object out of paper will not draw the line

How can I handle this problem?

If this is related to a library issue please follow the guidelines.


⚠ Bofrost.de has degraded performance

In 8b625d2, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 913 ms

Resolved: Bofrost.de performance has improved in 10130e8.


Setup continuous deployment

Setup continuous deployment so that pushes to master are deployed to https://thenewboston.network
TODO:

[DONE] Publish docker image to github registry
[IN PROGRESS] Shell script to deploy Core manually
[DONE] Provision an EC2 instance
Github actions to use that script and deploy to https://thenewboston.network

Relates to:

[DONE] Dockerize Project
Configure thenewboston.network domain with HTTPS

https://github.com/thenewboston-developers/Core/pull/51

https://github.com/thenewboston-developers/Core/pull/52

@buckyroberts manually deployed to http://<IP_ADDRESS>/ . We continue to work to setup automatic deployment

https://github.com/thenewboston-developers/Core/pull/53

@buckyroberts also available with ssh<EMAIL_ADDRESS>-i core-keypair.pem and http://thenewboston.network/

https://github.com/thenewboston-developers/Core/pull/54

@buckyroberts autodeploys from master now. TLS will be configured in https://github.com/thenewboston-developers/Core/issues/5


Connection Indicator [feature request]

Would be great to have a connection indicator in this boilerplate so users can be notified that they are offline (and let them know what is going to happen with their data).
I believe this is a nice feature and pretty common UX requirement for any interactive app.
But this will require implementing another feature like Notifications, i.e. flash messages generally used as confirmation of some action result (success/error).

Hey @dalerka, Thanks for your idea! It's possible to do this, I can think about this but All contributions are also welcome 😄


[BUG] not working

The activity panel is not showing at all. Running the latest version from chrome web store.

Showed up again today. Not sure what changed


[FEAT] Maintenance indicator on site cards at Dashboard panel

If the site is in maintenance mode, it should not be visible in the dashboard as being in maintenance

Utilizar paleta de bg-gray
El texto es un orange-500


Game of drones leaderboard link

The link to the game of drones leaderboard leads nowhere, you forgot an 's'.

Sorry I missed this issue. CG oddly uses a different name for Game of Drones (game-of-drone for API, game-of-drones for URL). Anyway this should be fixed now. Thanks for reporting. :)

Try to parse the Tron contest leaderboard, if you want to see strange URLs :stuck_out_tongue:


An index for fp-ts libraries. Does it exist?

Is there a place where libraries that follow the fp-ts coding conventions are gathered? I was also thinking if it would make sense to follow a certain naming scheme, using fp-ts as a prefix or postfix.
In the end they're just typescript libraries but on the other hand people may want to search for them specifically as they work well together. Another question would be what those "coding conventions" actually are. If not done yet, it would be interesting to have them documented somewhere. There's this document but is more about how to understand fp-ts and would miss some points that would be helpful for library writers.
Any way, yesterday I gave it a try to see what it would take to write and document a fp-ts "compatible" library. The outcome was this small port of an existing purescript pseudo random generator: https://github.com/no-day/lcg
It uses docs-ts for the documentation, too.
So, I'd be curious to hear if there's a place to gather, announce, discuss new releases in the fp-ts eco system.

Is this not covered by the ecosystem docs page?

Hi @thought2,

using fp-ts as a prefix or postfix

a prefix should be good (examples: fp-ts-contrib, fp-ts-rxjs, fp-ts-laws)

There's this document but is more about how to understand fp-ts and would miss some points that would be helpful for library writers

Yeah, if you feel like it we could chat here about what would be helpful for library writers and enrich/amend that document

if there's a place to gather, announce, discuss new releases in the fp-ts eco system

gather: I'd say the "ecosystem" docs page
announce, discuss: check out the fp-ts channel on FP slack

Thanks for the answers! Did not know about the ecosystem page, the fp-ts slack channel. Will make a PR for the ecosystem page.
Regarding the documentation, here are my suggestions. I can prepare a PR for this if there is agreement

Adding a link to the slack channel. E.g. in "README.md/community" or "docs/learning-resources.md"
enhance Coding Conventions

Explain the argument structure of a pipeable function. Something like (...instances) => (...args) => (dataType) => dataType

Adding a link to the slack channel. E.g. in "README.md/community" or "docs/learning-resources.md"

Already added to the README (branch 2.10)

Explain the argument structure of a pipeable function

:+1:


Support min_gain_to_split and max_delta_step

These are two useful parameters in LightGBM that we are using in our non-spark models. max_delta_step controls the maximum output of a tree leaf. min_gain_to_split sets the minimal gain to perform split. Both can be useful for regularization purposes.

More generally, is there some way to support the full range of LightGBM parameters in pyspark by just passing through a parameters dictionary? Many of these parameters don't affect (I think!) the sparkification and parallelization and I wonder if mmlspark can avoid replicating the full parameters API.

hi @tbenthompson  sorry about the issue you are having.  There is a hacky way to add parameters by putting them on any of the string fields (pass the original value, then a space, followed by param_name=param_value).  However, for now I would prefer to actually have users tell me what parameters should be on the learner since LightGBM is still relatively new.  I do agree it would be nice to add optional parameters through a parameter dictionary at some point, but I'm not sure if that point is now.

I just found max_bin_by_feature to be missing and it would be a useful parameter for me

@tbenthompson @chris-smith-zocdoc PR has been merged to add min_gain_to_split, max_delta_step and max_bin_by_feature, thank you for the feedback!

Thanks so much!

Hi, all I want to know how I can set these parameters (max_bin_by_feature, min_gain_to_split) when using mmlspark LightGBM. Looking at the docs here: https://mmlspark.blob.core.windows.net/docs/0.18.1/pyspark/mmlspark.lightgbm.html, none of those parameters are listed.


Create a new and interactive Login and Signin pages

I would like to create a login in page and signin page to this project. A website like this must have this two page so that the registered people can have access to courses and project.
I propoes a clean and user friendly pages which also matches with the main page theme and design.
Would u assign me this task under gssoc-ext tag.

@yeshwanth-ds solution is Good.
But could share the screenshot of which one you are gonna update.
So that i can look and assign the issue to you.

@vivekvardhan2810 I would add new li in the nav bar and name it "Login" and another as "Signin"
on click on any one of this would take you the respective login and signin page
I will add next to the contact block

Okay @yeshwanth-ds assigning this issue.
make sure to complete this issue for next 3 days.

@yeshwanth-ds why did you close the issue.

@vivekvardhan2810 This task hwas been compled and i was look to added new feture for this project to redue the risk of conflits i closed it.

Okay, can I close the PR also @yeshwanth-ds

@vivekvardhan2810 ok i shall work on new feature You can close

Yes


"containingStateGroup" property missing from types.

containingStateGroup is not documented anywhere in the API docs, or types. Missing from FrameInfo documentation, as well as in the types.
Another noteworthy mention, is the inconsistent casing in containing_frame. The rest of the response values are snake_case, while the properties inside containing_frame are camelCase.
ex:
"containing_frame": {
  "name": "Button",
  "nodeId": "10:1360",
  "pageId": "0:1",
  "pageName": "Page 1",
  "backgroundColor": "rgba(0, 0, 0, 0)",
  "containingStateGroup": {
    "name": "Button",
    "nodeId": "10:1360"
  }
}

Thanks for filing this issue! containingStateGroup is intentionally omitted from the documentation as this property was accidentally exposed quite a while back and is not officially supported.
As for inconsistent casing, this is correct -- there are a bunch of other places in the API with inconsistent casing as well. The goal of this project was to document the API as-is and not make any breaking changes to the API itself.


Challenge category & tag pie charts

Currently I am running a CTFd instance with all Juice Shop challenges imported to make a screenshot every now and then of the current distribution of challenge categories. This image appears in the eBook as well as the intro presentation slides:

It would be nice to have such a pie chart on https://stats.owasp-juice.shop instead. The necessary data should be pulled from https://github.com/OWASP/www-project-juice-shop/blob/master/_data/challenges.yml - that copy of the challenges.yml from the Juice Shop main repo is updated automatically on every release.
Another chart showing challenges by their tags would also be nice to have. Important: Other than with categories challenges can have multiple tags!

Both the category and tag information from that https://github.com/OWASP/www-project-juice-shop/blob/master/_data/challenges.yml is already read and presented in tabular form here: https://owasp.org/www-project-juice-shop/#div-challenges - The pie-chart presentation with % instead of absolute numbers would be a nice extra general information plus a screenshot source for the ebook and intro slide deck.

I got something like this. Is this the correct distiribution

Google has a wonky way of ordring the slices, but the Top 5 match in % value at least. Well done! 👍


Added a shadow to the PostCard component.

Added a shadow to the PostCard component, so that the card has visible defined boundary in light theme.
PR Fixes:

1 - Added some shadow to the PostCard component, for a better visibility in light theme.

The above image is the old one, the changed one looks like this;

@devsargam

Thanks


Add MustExec option

What do you want to change?
Hiya,
I would like to ask for an option to dictate when a generated method should panic rather than return an error. Basically an equivalent to the golang regex MustCompile version.
What database engines need to be changed?
No response
What programming language backends need to be changed?
No response

Thanks for the feature request and sorry for the slow response.
This isn't something that we're looking to add to sqlc. If you'd like this functionality, I'd suggest forking github.com/sqlc-dev/sqlc-gen-go to add a :mustexec query tag.


Make RSS guid use the post ID

Even though it's not a valid URL. Changing the post slug shouldn't create a new entry in people's RSS readers.

Good morning


Quiet a clang warning about a Qt memory leak.

The comment in the code explains more about why we need this.
This gets rid of one more clang static analysis warning.
Signed-off-by: Chris Lalancette<EMAIL_ADDRESS>

CI:

Linux
Linux-aarch64
macOS
Windows


fix error on issue #583

Is it a bugfix ?

Yes
fix issue #583

Is it a new feature ?

No

Description :

Sometimes there is an error popup and show "undefined is not an object (evaluating'_this.internals.offset[dir]')" message. I add some scripts to prevent that error appear again, based on @yoyo0427 does.

when will it be merged?

@leecade any chance to merge this PR?

i wiil use the branch to test, hope to fix this problem as soon as possible


FLEX-3850 ~ Removes logging of organization for incoming OSLP messages.

messageReceived() calls logMessage()
logMessage() determines the owner organization or authorized
organization and logs it
the organization identification is only relevant for outgoing OSLP messages, not for
incoming messages

SonarQube analysis reported 6 issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 OslpChannelHandler.java#L132: The Cyclomatic Complexity of this method "isOslpResponse" is 22 which is greater than 10 authorized.
 OslpChannelHandler.java#L133: Reduce the number of conditional operators (21) used in the expression (maximum allowed 3).
 OslpChannelHandler.java#L132: The Cyclomatic Complexity of this method "isOslpResponse" is 18 which is greater than 10 authorized.
 OslpChannelHandler.java#L133: Reduce the number of conditional operators (17) used in the expression (maximum allowed 3).
 OslpChannelHandler.java#L35: Make the "logger" logger private static final and rename it to comply with the format "LOG(?:GER)?".
 OslpChannelHandler.java#L35: Make the "logger" logger private static final and rename it to comply with the format "LOG(?:GER)?".

All is well.


Custom entity templates

Set custom templates to entities. For example, in a entity that represent events, show a calendar instead of the table.
Suggest ideas if you have

Not really sure where you are going exactly with this one, but in terms of calendars http://fullcalendar.io/ is my goto. looks like it's been ported over a bit here: https://atmospherejs.com/rzymek/fullcalendar
But the callbacks for fullcalendar are totally documented it's a really solid solution for calendars

@iamkevingreen You talking about presentation or event entry form? entry is orionjs but for presentation it is out of scope of this project. So please clarify question

Instead of showing the table, you can choose. An example was the calendar, same functionality that the actual table has but a different way to display it. It can be other things, like showing entity items like in the files tab.

@nicolaslopezj you are right about using the fullcalendar this needs a robust solution. I also think he may be asking how to display it to visitors  (non-login guest). This is why I wanted to know the usecase

@timfam, you are right. This is only for the admin, anything is its out of the scope


pre-transfer-leader: use log term instead of term

What have you changed?
raft-rs forbids setting term for MsgTransferLeader, so use log term
instead.
What is the type of the changes?

Bugfix

How is the PR tested?

Manual test

Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No.
Does this PR affect tidb-ansible?
No.

/test

/test


Out of memory

Hi, i have tried the model gpt-neox-20b, but i encounter a problem is that the python process will be killed by system,  because the python code as follows consumes too much memory
        int8_model = Int8OPTForCausalLM.from_float(model, decoder_layer_scales)

How can i fix this problem
thanks

Hi, I also encountered a similar problem, did you solve it? If it is solved, could you please tell me how to fix it? Thank you so much!


Release null objects from MemoryPoolBase

In Unity MemoryPool entries can become null through calls to Object.Destroy(entry).
When the MemoryPool returns a value, which has been destroyed, this will cause problems. This is in particular problematic for MonoMemoryPool which can hold references to objects in a scene which is unloaded. I've added a minor addition to MemoryPoolBase which will release items which are null. It now pops items until it finds one which is not null and expands the pool whenever the last item had been popped (e.g. all items are destroyed because they belonged to an unloaded scene)

If that happens isn't that a mistake?  Like shouldn't the fix be to not delete objects that have been added to the pool instead of fixing it inside the memory pool class?

@svermeulen this usually is a problem in indirect scenarios where Unity does destroy the object and not the user via Object.Destroy , e.g. a scene change, which destroys all gameobjects part of the scene. The user could like work around this by ensuring that pooled objects are move to the DontDestroyOnSceneLoad scene.
However - at least I believe so - it would be very difficult to keep all memory pools clean when you unload a scene. If there is e.g. a class SceneSystem which handles loading/unloading it would require a reference to all memory pools which spawn objects in any scene it potentially unloads, s.t. it can despawn all items from all pools before unloading the scene?
In other scenarios I guess it should be really the best way to keep the pool clean in the first place, e.g. spawn, delete and never despawn deleted object.

You're saying that you might want to continue using the memory pool when the scene changes?  So it is bound in the project context?

@svermeulen ProjectContext or a SceneContext of a scene in multi-scene (additive loading, scene parenting) scenarios which is not unloaded.

In that case though, shouldn't the inactive pooled objects already be placed in the same scene where the pool is bounded?  I don't understand why they are being deleted.   One thing that does occur to me is that the old version of MonoMemoryPool was not resetting the parent automatically during despawn (but it is now in zenject 6), could that be related?

Sure no problem


Next-intl incompatibility with Vercel

Description
Hi guys. I recently encountered a problem when deploying my website using Vercel. I did some tests to confirm that the issue was due to an incompatibility between next-intl and Vercel. The following error was thrown by Vercel:
TypeError: Cannot read properties of undefined (reading 'pathname')
    at Object.n [as prefixHref] (/var/task/apps/web/.next/server/chunks/198.js:1:94172)
    at /var/task/apps/web/.next/server/chunks/198.js:1:89785
    at nt (/var/task/node_modules/.pnpm/next@14.2.17_@babel+core@7.26.0_react-dom@18.3.1_react@18.3.1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:38746)
    at Object.useState (/var/task/node_modules/.pnpm/next@14.2.17_@babel+core@7.26.0_react-dom@18.3.1_react@18.3.1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:40703)
    at t.useState (/var/task/node_modules/.pnpm/next@14.2.17_@babel+core@7.26.0_react-dom@18.3.1_react@18.3.1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:110091)
    at /var/task/apps/web/.next/server/chunks/198.js:1:89729
    at nj (/var/task/node_modules/.pnpm/next@14.2.17_@babel+core@7.26.0_react-dom@18.3.1_react@18.3.1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:46251)
    at nM (/var/task/node_modules/.pnpm/next@14.2.17_@babel+core@7.26.0_react-dom@18.3.1_react@18.3.1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:60839)
    at nN (/var/task/node_modules/.pnpm/next@14.2.17_@babel+core@7.26.0_react-dom@18.3.1_react@18.3.1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:64546)
    at nI (/var/task/node_modules/.pnpm/next@14.2.17_@babel+core@7.26.0_react-dom@18.3.1_react@18.3.1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:47010) {
  digest: '41004656'
}

I ran the application in production mode locally and no issues were noticed. After I noticed the problem was with Vercel, I tried changing the matcher config, but the problem still persists.
import createMiddleware from 'next-intl/middleware';

import { routing } from './i18n/routing';

export default createMiddleware(routing, {
  localeDetection: true,
});

export const config = {
  // Match only internationalized pathnames
  matcher: [
    '/',
    '/((?!api|_next|_vercel|.*\\..*).*)',
    '/(en-US|es|pt-BR)/:path*',
  ],
};

Finally, I deployed my app on Netlify, and it worked smoothly.
My environment is:
Node v18.17.1
PNPM 9.0.6
Next 14.2.17
Next-Intl 3.21.1
Turborepo 2.2.3

It is worth mentioning that I am also using a PRO account on Vercel. So there is no limit to serverless functions.
Verifications

[X] I've verified that the problem I'm experiencing isn't covered in the docs.
[X] I've searched for similar, existing issues on GitHub and Stack Overflow.
[X] I've compared my app to a working example to look for differences.

Mandatory reproduction URL
https://portfolio-qk5xrn87z-wallacesfs-projects.vercel.app/pt-BR
Reproduction description
Steps to reproduce:

Clone my repo: https://github.com/wallace-sf/portfolio.
Deploy on vercel with branch master.
See error in the deploy logs.

Expected behaviour
To run without errors in the Vercel environment.

Can you see if the error persists when you upgrade to the latest version of next-intl and switch to createNavigation?

Can you see if the error persists when you upgrade to the latest version of next-intl and switch to createNavigation?

Sure, I'll give it a try and then post the result here.


(SP: 1) Fix sonar issues for notifications service

Fix sonar issues for notifications and make tests working in proper way

not relevant


updating test_data parameters

Values passed in the arguments were static, causing the algorithm to run every time on the same dataset.
Updating default input argument in ImputationDataset class, previously initialized with train_dataset = 'pbmc_data' and filetype = 'h5'. Now changed to  train_dataset = params.train_dataset and filetype = params.filetype
Also removed test_dataset and hiddem_dim arguments from arg_parser

Closing since it is out of date


fix Fix index for none key column of unique mor table

Proposed changes
Issue Number: close #xxx
Add back support index for none key column of unique mor table.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Wrong address from XPUB

I've included your bitcoin libraries into my codeigniter 3 project and when I try to generate wallet addresses from the Electrum's XPUB, it gives me the right results most of the time, but sometimes it doesn't.
For example with the XPUB provided in the code, results for "m/0/2" and "m/0/14" are wrong, everything else is OK.
In case of "m/0/2" your code gives me 1B3RQ4QKocRE7MFVDpMMmgyswF2DeMEfS6 and Electrum gives me 16wjYM9D46xPYHHUQp7XwotgLwT56ZPZux
In case of "m/0/14" I'm getting 1JEKgyHAb4tx5EkPpMhWzACxTVGsW2Z7Xo but Electrum gives me 14tk9sYRDXXbya6Q2ZJLs1hHZ2mcpRbybS
<?php
$xpub = 'xpub661MyMwAqRbcGtMQDiA8n7E15sH2cA6qdE1kdiQuMjdnNoCwbFMuenQh29mrER4txDBDsuJUPAUZSd9J4qpxFtNBFEzep2cJVDku9UVVAfY';

$address = BIP32::build_address($xpub, "0/2");

echo $address[0]; // Outputs 1B3RQ4QKocRE7MFVDpMMmgyswF2DeMEfS6

I tried different PHP servers (OSX, ubuntu) because I thought it's perhaps an issue with php5-gmp library but it gives me the same wrong results.
I also tried using BitcoinLib and BIP32 to generate addresses for multisig wallets (of course with different XPUBs) and there are much more wrong results (~4 out of every 20 addresses).
BTW results with XPUB from my TREZOR wallet were OK. I also checked with http://bip32.org and it shows me same addresses as Electrum does, so it seems there are some issues with your code.

Hey, thanks for posting!
This is actually an old project, I can't attest to it's reliability for anything right now. Most of the code it uses can be found in this library: https://github.com/Bit-Wasp/bitcoin-lib-php available through composer.
Testing the code you posted above against this library produces the correct address!
I wouldn't advise relying on the code in this bit-wasp/multisig repository as it's not maintained, and didn't see much use back in the day. The bitcoin-lib-php library has been maintained since then, and has some of the soft-fork requirements that have come about since I wrote this!
With all that said, using Bit-Wasp/bitcoin-php might be best. It's far more complete/tested, and probably easier to develop applications around.

I switched to bitcoin-lib php since, but a multisig wallet code gives me wrong results as well. "m/0/i" seems ok for 3 tested XPUBs so far though.
I will try bitcoin-php for multisig to check if it's ok. Performance wise it seems the same. Thank you for the reply.

OK, so I switched to Bit-Wasp/bitcoin-php and after brief testing I think it works correctly with numerous XPUBs being tested. I also get correct addresses for my multisig wallet.
Btw the only reason I wanted to use Bit-Wasp/multisig is because it takes only 30ms to generate an address. It takes about 4x more to do the same with Bit-Wasp/bitcoin-php but I guess that extra time is because it's much more reliable.
Anyway thank you again.
I'm closing the issue as you're no longer maintaining this code.

Indeed it was for a reason - Point multiplication now run at constant time, instead of leaking information about the private key.
Good luck!


Improve backup performance with faster compression algorithm and multiple threads

Longhorn/longhorn#5189

To be honest, the naming and layering of the backup part are a little bit hard-to-understand. Not sure if we can improve it...

Do you mean the whole backup layer?

I mean all functions including the functions you already mentioned and the new functions you introduced...

I mean all functions including the functions you already mentioned and the new functions you introduced...

For the new functions
backup: backupMappings->backupMapping->backupBlock->isBlockBeingProcessed->updateBlocksAndProgress
restore: restoreBlocks->restoreBlock->fillZeros or restoreBlockToFile

For the exsting functions, for example, we can merge RestoreDeltaBlockBackupIncrementally and RestoreDeltaBlockBackup in another refactoring ticket.

I like the refactoring and error message clean up, let's move them into a prerequisite separate PR that we can wave through quickly so we can keep the PR and review focused on the actual backup compression changes.

Move the refactoring codes to https://github.com/longhorn/backupstore/pull/95. Thank you.

@derekbit merged the refactoring you can rebase -i to drop the duplicate refactoring commits. Thanks for moving them out into it's own PR :)

LGTM. Maybe we can re-organize deltablock.go in the future. For now let's focus on the feature itself.

ref: https://github.com/longhorn/longhorn/issues/5247 If anything we would like to improve, just create an issue for that.

BTW, lz4 lib is interesting. It uses assembly code for each different arch to compile together.
https://github.com/pierrec/lz4/blob/v4/internal/lz4block/decode_amd64.s
However, it seems not to support the s390x arch. Will this be a concern? or can we just fallback to gzip for unsupported arches?

https://github.com/pierrec/lz4/blob/v4/internal/lz4block/decode_other.go which should be a fallback.

https://github.com/pierrec/lz4/blob/v4/internal/lz4block/decode_other.go which should be a fallback.

Interesting.
Original Lz4 is implementaed by C codes https://github.com/lz4/lz4.
The user (pierrec) wrote a ASM version. Is the binary compiled from GO is too slow?

<EMAIL_ADDRESS>which should be a fallback.

Interesting. Original Lz4 is implemented by C codes lz4/lz4. The user (pierrec) wrote a ASM version. Is the binary compiled from GO too slow?

yeah, not sure if this is related to cgo overhead concern or cross-compile, so use asm instead. https://github.com/golang/go/issues/42469#issuecomment-753979705
You can also see go has systemcall for different arches, so this makes it can be cross-compiling for different arches.

Anyway, this is out of the topic, but it's good to know about lz4 package implementation :slightly_smiling_face:


Option to give region variable for s3 bucket for lambda code in s3 integration

Issue
By default s3 bucket for lambda zip code is configured to get the region from the data block, which means that lambda itself has to be created in that region.
In a situation where the organization uses for example ap-east-1 and has to create lambda there only that case the data block fails as the s3 bucket "coralogix-serverless-repo-ap-east-1" doesn't exist and the region is being fetched from data blog can't be overridden
Ref - https://github.com/coralogix/terraform-coralogix-aws/blob/master/modules/s3/main.tf#L76
What we can use instead
We should give the option to pass a variable such as "coralogix_serverless_repo_region" so that people using ap-east-1 or other regions have the option to choose what region they want to use to fetch lambda code from
Or
The Coralogix team will have to create a bucket in all the region with lambda code

raising a pr for the same soon

can we support the ap-east-1 region as well here ?? not sure how that works when we deploy coralogix-aws integration with cloud formation but with terraform lambda and lambda code repo is supposed to be in the same region.
In our case, we are using ap-east-1 but the coralogix-serverless-repo doesn't exist in ap-east-1 rather it's in eu-central-1 thus terraform throws an error

relates to issues/90

This is Solved


Need help in reproducing the results

Hi,
Thank you for this interesting work. We wanted to reproduce the results, but we are unable to match the results reported in the paper. We used iSAID as training dataset. First, we tried with cat_seg/cat_seg_model_ours.py  and cat_seg/modeling/transformer/model_ours.py and got the following results:
ISAID val: 83.60
DLRSD: 22.58
Potsdam: 15.4
Vaihingen: 13.4
Next, we noticed SAU module was not present in cat_seg/modeling/transformer/model_ours.py, so we integrated necessary changes from cat_seg/modeling/transformer/model_attention.py file. This yields the following results:
ISAID val: 81.44
DLRSD: 23.33
Potsdam: 15.40
Vaihingen: 14.98
These models are trained for 100K iterations. Is there any other change that we need to do for reproducing the results?
Thanks in advance.

hi，do you have an email so that I will send you with my log.txt

Hi @saikatdutta,
I am trying to evaluate the model as well. Did you encounter this issue when evaluating the model with iSAID? It was training fine until I encountered this error.
@caoql98 do you have any insights on this? Thanks!
[12/16 17:10:38 d2.utils.events]:  eta: 12:55:10  iter: 4879  total_loss: 0.001177    time: 0.6196  last_time: 0.6171  data_time: 0.0036  last_data_time: 0.0018   lr: 0.00019817  max_mem: 19774M
[12/16 17:10:51 d2.utils.events]:  eta: 12:55:11  iter: 4899  total_loss: 0.000974    time: 0.6196  last_time: 0.6297  data_time: 0.0045  last_data_time: 0.0100   lr: 0.00019816  max_mem: 19774M
[12/16 17:11:03 d2.utils.events]:  eta: 12:54:59  iter: 4919  total_loss: 0.001061    time: 0.6196  last_time: 0.6238  data_time: 0.0025  last_data_time: 0.0017   lr: 0.00019814  max_mem: 19774M
[12/16 17:11:15 d2.utils.events]:  eta: 12:54:46  iter: 4939  total_loss: 0.0008647    time: 0.6196  last_time: 0.6206  data_time: 0.0029  last_data_time: 0.0016   lr: 0.00019812  max_mem: 19774M
[12/16 17:11:28 d2.utils.events]:  eta: 12:54:13  iter: 4959  total_loss: 0.001091    time: 0.6196  last_time: 0.6138  data_time: 0.0023  last_data_time: 0.0017   lr: 0.00019811  max_mem: 19774M
[12/16 17:11:40 d2.utils.events]:  eta: 12:53:50  iter: 4979  total_loss: 0.001044    time: 0.6196  last_time: 0.6183  data_time: 0.0032  last_data_time: 0.0018   lr: 0.00019809  max_mem: 19774M
[12/16 17:11:53 fvcore.common.checkpoint]: Saving checkpoint to ./output/model_0004999.pth
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
[12/16 17:11:56 d2.data.datasets.coco]: Loaded 6363 images with semantic segmentation from /home/user/LISA-dataset/RS-datasets/OVS_datasets/iSAID_split/val/imgs
[12/16 17:11:56 d2.data.dataset_mapper]: [DatasetMapper] Augmentations used in inference: [ResizeShortestEdge(short_edge_length=(640, 640), max_size=2560, sample_style='choice')]
[12/16 17:11:56 d2.data.common]: Serializing the dataset using: <class 'detectron2.data.common._TorchSerializedList'>
[12/16 17:11:56 d2.data.common]: Serializing 6363 elements to byte tensors and concatenating them all ...
[12/16 17:11:56 d2.data.common]: Serialized dataset takes 1.52 MiB
[12/16 17:11:56 d2.data.datasets.coco]: Loaded 6363 images with semantic segmentation from /home/user/LISA-dataset/RS-datasets/OVS_datasets/iSAID_split/val/imgs
[12/16 17:11:56 d2.evaluation.evaluator]: Start inference on 1591 batches
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/timm/models/layers/__init__.py:48: FutureWarning: Importing from timm.models.layers is deprecated, please import via timm.layers
  warnings.warn(f"Importing from {__name__} is deprecated, please import via timm.layers", FutureWarning)
Traceback (most recent call last):
  File "/home/user/OVRS/train_net.py", line 317, in <module>
    launch(
  File "/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/detectron2/engine/launch.py", line 69, in launch
    mp.start_processes(
  File "/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/torch/multiprocessing/spawn.py", line 198, in start_processes
    while not context.join():
  File "/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/torch/multiprocessing/spawn.py", line 160, in join
    raise ProcessRaisedException(msg, error_index, failed_process.pid)
torch.multiprocessing.spawn.ProcessRaisedException:

-- Process 1 terminated with the following error:
Traceback (most recent call last):
  File "/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/torch/multiprocessing/spawn.py", line 69, in _wrap
    fn(i, *args)
  File "/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/detectron2/engine/launch.py", line 123, in _distributed_worker
    main_func(*args)
  File "/home/user/OVRS/train_net.py", line 311, in main
    return trainer.train()
  File "/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/detectron2/engine/defaults.py", line 520, in train
    super().train(self.start_iter, self.max_iter)
  File "/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/detectron2/engine/train_loop.py", line 156, in train
    self.after_step()
  File "/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/detectron2/engine/train_loop.py", line 190, in after_step
    h.after_step()
  File "/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/detectron2/engine/hooks.py", line 556, in after_step
    self._do_eval()
  File "/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/detectron2/engine/hooks.py", line 529, in _do_eval
    results = self._func()
  File "/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/detectron2/engine/defaults.py", line 489, in test_and_save_results
    self._last_eval_results = self.test(self.cfg, self.model)
  File "/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/detectron2/engine/defaults.py", line 653, in test
    results_i = inference_on_dataset(model, data_loader, evaluator)
  File "/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/detectron2/evaluation/evaluator.py", line 172, in inference_on_dataset
    evaluator.process(inputs, outputs)
  File "/home/user/anaconda3/envs/RRSIS/lib/python3.9/site-packages/detectron2/evaluation/sem_seg_evaluation.py", line 138, in process
    self._conf_matrix += np.bincount(
ValueError: cannot reshape array of size 2304 into shape (16,16)


Nuget and MVC 6

In the new MVC 6 project client slide libraries like this are no longer meant to be delivered via Nuget. At some point the Nuget packages should be discontinued in favor of bower deliver (somewhat ironically given my previous comments about not using bower).
I want to continue to support older projects and I'm sure the number of early adopters will be much fewer in number than those who use Nuget for everything.
That said, is there any reason why we could not put an End of Life date on the Nuget packages?
.Net devs do you use nuget outside of MVC?

Hi - nuget is the standard delivery tool for pacages using Visual Studio.

I know that. I'm a .Net developer. However, as I said, MVC 6 won't use (or will have diminished used) for delivering front-end scripts like this.

Hi
I'm using Nuget for backend libraries(EF,Autofac,AutoMapper, etc ..), bower for frontend libraries(bootstrap, jquery, datatables, this library, etc..) and npm for validate CSS,JS and build for deploy

@fchiumeo then your process will not change at all

"fit" for what's coming with the new visual studio and it turned me more comfortable having separate the frontend and backend libraries

Nuget really sucks for client-side libraries. I think most of asp.net devs already use bower.

I think an EoL for the nuget packages should be next year or 2+ major version (7) which ever comes first

I think you're overthinking it. Just stop updating it for the new v5. People will find a way to get the library, since most of the stuff is not on nuget anyways.

You're probably right, I probably am overthinking it.

Well, I think it would be nice if devs could take unsupported libraries off nuget. There are too many stale packages.

i do use nuget for everything, i think if this is the road mvc is taking i will take it too, actually i hope bower will solve some issues i have using tfs and all the libraries files getting checkedin and getting me crazy.

@TrabacchinLuigi I have all front end components in bower, use gulp for task, i.e. validate js, css and one task copy necessary files from bower_components to js/lib folder and check in lib folder to tfs

i've tried that, and i lost so much time trying to make it work i think i will just download and put the files where the hell i want

@TrabacchinLuigi Try it

Thats what I do, only a little bit different. (Will fail if packages changes their folder structure...)
	gulp.task('copyJs', function () {
		var requirejsOptimize = require('gulp-requirejs-optimize');
		return gulp.src([
			'node_modules/eonasdan-bootstrap-datetimepicker/src/js/bootstrap-datetimepicker.js',
			'node_modules/eonasdan-bootstrap-datetimepicker/build/js/bootstrap-datetimepicker.min.js'])
			.pipe(gulp.dest('Scripts'));
	});

It seems that I have messed something. MVC 6 (actually ASP.NET Core) is under the RC1 version (not RELEASE yet). Actually from November 2015 (https://github.com/aspnet/Home/wiki/Roadmap)
So I want to know what will be with the ASP.NET 4.5 projects? Which is actually the latest version could be used for the Production.

@sguryev You can use gulp already in visual studio, and I recommend it. Its the way forward, and one thing less to learn when you eventually are going to use MVC 6.

@Jogai I support 3 projects on ASP.NET 4.5. They are worked on PROD. Are you really suggesting me to switch them to the Bower and Gulp? Am I right that Gulp is "the streaming build system" and Nuget is a package manager (like Bower for example).
Do you know that Bower package manage UI works incorrectly in the VS2015U2 (black unrecognizable font for the dark theme + poor packages info + wrong package versions). This is my first experience with the Gulp+Bower in the ASP.NET Core.

And this problem not only with the Bootstrap package. You can check yourself.

The decision is made. The nuget packages won't be updated to the next major release. Either use a CDN, v4, bower or npm.

@sguryev My suggestion is to learn the tools and gain the skills. Using it in existing projects is entirely up to you, and depends on a lot of other factors.
In my current project I'm only using NPM + Gulp, and I dont use the extenstion to manage the packages via the UI (that would be https://github.com/madskristensen/PackageInstaller/ I think)
And its not about switching from Nuget. I like to use Nuget for server-side technologies, and npm for front-end libs. In my experience there are more front-end libraries on npm, and they're more up-to-date.

and no one will agree to switch

No one in your team I presume?
Further info:
https://www.google.com/trends/explore#q=Bower%2C NuGet%2C Npm
http://webtooling.visualstudio.com/
https://www.simple-talk.com/dotnet/asp.net/introduction-to-bower,-grunt,-and-gulp-in-visual-studio/
http://blog.chrisbriggsy.com/Migrate-from-nuGet-to-Bower/
Keep in mind, always choose and pick what is best in your own situation, as I said, I'm not even using bower or the package manager extension as mentioned in some articles.

@Jogai thank you for your suggestion. But enterprise projects are not the place for learning.

No one in your team I presume?

No one from enterprise project managers.
I'm new to  all this stuff and use what default template suggest me (ASP.NET Core I mean). NPM for utils package management, Bower for client-side package management, Gulp - just a tool to make some transformations over static files. Have never seen how to use the NPM for the client-side packages instead of the Bower. Thank you for the URLs I will review them.

I'm not even using bower or the package manager extension as mentioned in some articles.

And in the start post from @Eonasdan


Intellisense type of class-property lost when adding a new class-method via prototype

VSCode Version: 1.44.2
OS Version: macOS Catalina v10.15.4

Steps to Reproduce:

in a .ts file, define a class that has a typed property - e.g. result: number
define a new method for that class via interface+prototype - e.g. ClassName.prototype.add = ...
inside the new method's definition, this.result is detected with type any, instead of e.g. number. Furthermore, attempting to set a non-existent property of that class seems to work just fine - e.g. this.invalidProp = 'xyz' (again it's detected with type any).

This issue can be reproduced in VS Code and on www.stackblitz.com

However, on www.typescriptlang.org/play/ it detects this.result as having the correct type - e.g.number - and an error is triggered, as expected. Likewise, this.invalidProp triggers the appropriate error, as that property does not exist.

Sample code:
class Algebra {
    result: number = 0;
    multiply() {
        // this triggers a type error, as expected
        this.result = 'xyz';
    };
}
interface Algebra {
    add(): void;
}
Algebra.prototype.add = function() {
    // this does NOT trigger an error re: Type '"abc"' is not assignable to type 'number'
    // -- it detects "this.result" with type "any" instead of "number"
    this.result = 'abc';
    // this does NOT trigger an error re: Property 'invalidProp' does not exist on type 'Algebra'
    // -- it detects "this.invalidProp" as a valid property with type "any"
    this.invalidProp = 'abc';
}

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

The difference seems to be that the TS playground has noImplicitThis enabled

Oh, thanks for that! I could've sworn I tried toggling each setting from Compiler-options on the TS playground, before raising the issue here. My bad.


Instable

I'm surprise that you make difficult to copy the error message require to send you a picture:
Usability issue plus crashing too often when you try to remove dead docker from the GUI or try to run two in parallel.

"Cannot connect to the Docker daemon. Is 'docker -d' running on this host?" Looking in the settings of running container without doing any change make me lose the running container

@VelizarVESSELINOV Why the need to run 2 Kitematic apps in parallel? Or did you mean 2 container apps?
Can you provide the output of the following commands:
docker-machine ls
docker-machine env dev (unless the above ls command showed kitematic)
eval "$(docker-machine env dev)" | docker version
Thanks

2 Docker containers running in parallel, not 2 Kinematic apps.
I will give you theres details next time I'm playing with Kitematic. The version was downloaded last Friday afternoon, if this help you about the version identification.

Yup I suspect a couple of things - Can you provide the output of the different docker versions too?
docker version
docker-machine version
And if you login to your VM, the docker version there too? Thanks!

Please find the requested information:
docker version:
Client version: 1.7.0
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 0baf609
OS/Arch (client): darwin/amd64
Server version: 1.7.0
Server API version: 1.19
Go version (server): go1.4.2
Git commit (server): 0baf609
OS/Arch (server): linux/amd64
docker-machine --version:
docker-machine version 0.3.0-rc2 (6f939a8)
docker-machine ls
NAME   ACTIVE   DRIVER       STATE     URL                         SWARM
dev    *        virtualbox   Running   tcp://<IP_ADDRESS>:2376
docker-machine env dev
export DOCKER_TLS_VERIFY="1"
export DOCKER_HOST="tcp://<IP_ADDRESS>:2376"
export DOCKER_CERT_PATH="/Users/VV/.docker/machine/machines/dev"
export DOCKER_MACHINE_NAME="dev"
Thanks

Can you verify that the docker version within the VM is the same as the one on your Mac?
I was sort of expecting a x509 certificate error, but this doesn't seem to be the case

labelling as a docker-machine issue for when we troubleshoot

Is this happening on Kitematic 0.8 as well? Installed through Docker Toolbox

I just installed Docker Toolbox, thank you for the post, Kinematics didn't give me notification that a new version is available. I will test again at let you know.

Looks like working better, I have other UX and docker stability issues but I will close this one


[stdlib] prevent buffer overflows when String-from-C-string initializers are called via array conversion

The family of String initializers that convert from C strings (null-terminated byte buffers) could until now be called with Swift arrays. When the array violates the C string precondition of containing a zero byte, this could result in a buffer overflow. This is unexpected when the entirety of the code is pure Swift. Adding the @_nonEphemeral attribute applied to their UnsafePointer parameters is not a sufficient solution (it only adds a warning,) so this also adds overloads that take arrays, and prevent reads past the end of the array buffers. Note that String conversion is not affected by this bug, since it always appends a trailing null. Inadvertent uses of String conversion will, however, benefit from the warning from @_nonEphemeral.

Resolves rdar://90336023.

@swift-ci Please Test Source Compatibility

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

I'm tempted to mark these new overloads as deprecated, but that probably requires evolution approval.

@swift-ci please test

@swift-ci please smoke test

@swift-ci please test

@swift-ci please smoke test linux platform

Changes look good to me. I think some of the API here requires evolution however.

@swift-ci please smoke test

Note: the added overloads are not new API, in the sense that their type parameters are refinements of those of the existing calls.

I'd like feedback on my deprecation messages, including the empty ones.

@ swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please test Windows platform

The linux failure seems like a problem with stdlibunittest; it seems to not be doing the right thing with expectCrashLater(withMessage:).

@swift-ci please smoke test

@glessard I believe this PR introduced an issue where before 5.7 this would work:
var path: (CChar, CChar, CChar, CChar, CChar) = [47, 118, 97, 114, 0]
print(String(cString: &path.0))

but with this change in 5.7 it does not.
I believe it is because there is a new String(cString nullTerminatedUTF8: inout CChar) which incorrectly checks for the first element is zero (nullTerminatedUTF8 == 0), when in reality it should find the last element in memory which is zero.
The inout API takes precedence over the UnsafePointer<CChar> API that existed before (which continues to work), which makes all usage of this API fail with the preconditionFailure, and returns empty strings. I tested precedence  with this example:
func something(_ c: UnsafePointer<UInt8>) {
  print("from unsafe pointer", c)
}

//func something(_ c: inout UInt8) {
//  print("from inout", c)
//}

var pointer: (UInt8, UInt8, UInt8) = (1, 2, 0)
something(&pointer.0)

Is it expected that this API would change in this way? Are previous usages of this API wrong?
It feels off that the deprecation warning states to change the API, and that the resulting behavior is at the same time changed. At least, it should be a compilation error to prevent people who don't usually fix deprecation warnings as quickly from building code that will start to fail under 5.7 (meaning probably macOS Ventura and 5.7 linux images)
Found this while running the tests of git@github.com:swhitty/FlyingFox.git on macOS ventura (22A5295i) and Xcode 14 beta 4 (14A5284g)

Hi @sergiocampama!
Unfortunately, this:
var path: (CChar, CChar, CChar, CChar, CChar) = [47, 118, 97, 114, 0]
print(String(cString: &path.0))

never actually worked before. (It will have happened to "work" and produce the desired result on accident occasionally, but it steps outside of the language model, and would have suddenly stopped working with a new language version or compiler optimization). In particular, the pointer created by &path.0 only points to a single CChar with value 47; any bytes that follow that are undefined. This code was never correct, and that is now being diagnosed.
@glessard can help you with an appropriate workaround.

@sergiocampama Your initial example exploited an explicit out-of-bounds read: your are passing in an inout CChar, that type has a memory size of 1. Yet you were reading 4 bytes. That's a bug! Furthermore, in the example as written, the pointer you get from this conversion points to the value in path.1, but advancing that by 1 is not guaranteed to point to path.1. It just so happens that it generally does, and will if that tuple comes from an imported C api.
The workaround you identified is appropriate. Note that the fact that there is no proper bounds checking is made explicit by the fact that you are using withUnsafePointer(to:). That is intentional.

Thanks @glessard and @stephentyrone for the additional context. I do understand that this is unsafe and a bug and should be updated. Just merely pointing out that in this new version it is not being diagnosed, it does changes behavior for current bad users of the cString API, where before it used to erroneously work, and now it crashes.
IMO it should be marked as unavailable and not a deprecation, since there could be code out there that (erroneously) compiled and worked and now will crash, especially for a minor release (changing from 5.6 to 5.7, unclear if Swift itself follows semver). (Also, the initializer as is does nothing of value, so it's unclear why it would even stay.)
This crash will appear either when running previously compiled apps which are now running on Swift 5.7 (such as Ventura or newer linux images, not sure how to mitigate this case) or when compiling old code and disregarding deprecation notices (which a non trivial amount of people do).
Finally, just pointing this out as mismatched expectations on changing behavior, if you say this is expected then that's that.
ps: Thanks for your work in making Swift safer :)

The behavior of previously compiled apps is unchanged here; the pre-existing symbol has the same behavior as before (please confirm, @glessard). This only changes the behavior for apps that are recompiled, at which point one would hope that the resulting binary is tested.
I do think that we should consider simply making the inout CChar version unavailable in a future release, as it can really only be used in error.

Oh, right, it's emitted into the client, missed that.

Right, but the existence of the new symbol doesn't change which symbol existing code uses. You have to recompile to get the new behavior.


Disable seo metabox for specific cpt

Enhance the cpt seo settings so you can disable the seo metabox for certain post types.

Hey! If a CPT is non-public it won't add the metaboxes. Are there other usescases where it should not be there? After all: if it can be found on the front end, wouldn't you always want to optimize for SEO?

Ah, great. Works as expected. And your right about wanting to optimise if public. Thanks.


Ensure that other geographies don't receive links

Not been able to test as there are no documents in the databse with these geographies on yet.
But here is the database table so you can test by inspection:
 id  | display_value | value |          type          | parent_id | slug
-----+---------------+-------+------------------------+-----------+------
 216 | No Geography  | XAA   | ISO-3166 CPR Extension |       215 | xaa
 217 | International | XAB   | ISO-3166 CPR Extension |       215 | xab

Neat. LGTM


[utils][test] Remove unnecessary ref param

Part of https://github.com/mui/material-ui/issues/42381
Extracted from https://github.com/mui/material-ui/pull/42824/files#r1715334482

Nice small scoped PR 👍


Publish to maven using pom with jar packaging

IMPORTANT: We should review the implications of this change before merging. DONT MERGE YET.
Solves #170
Description of changes:
Changes the artifact that is resolved from a dependency created to software.amazon.opentelemetry:aws-opentelemetry-agent to the jar.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #228 (6afc962) into main (0ac0c0b) will increase coverage by 85.71%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main     #228       +/-   ##
===========================================
+ Coverage        0   85.71%   +85.71%
- Complexity      0       19       +19
===========================================
  Files           0        3        +3
  Lines           0       49       +49
  Branches        0        5        +5
===========================================
+ Hits            0       42       +42
- Misses          0        3        +3
- Partials        0        4        +4

Impacted Files
Coverage Δ

...roviders/AwsAgentPropertiesCustomizerProvider.java
100.00% <0.00%> (ø)

...elemetry/awspropagator/AwsCompositePropagator.java
87.87% <0.00%> (ø)

...vaagent/providers/AwsTracerCustomizerProvider.java
66.66% <0.00%> (ø)

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

After discussion we deliberated that this change is backwards compatible for existing cases:

users resolving with the dependency with the @ for the extension.
new users that will opt to use the dependency without specifying the extension.