never increase the flow control limit for the crypto stream

When sending crypto stream data, we don't respect the flow control limit in
https://github.com/lucas-clemente/quic-go/blob/f78c0035b93ab0b76f0fcf4f07bcff440e826098/send_stream.go#L189-L192
Since there's no flow control for the crypto streams in IETF QUIC, and we didn't respect the flow control limit in gQUIC anyway, we might as well remove it now and simplify the code a bit.

Codecov Report

Merging #1519 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1519      +/-   ##
==========================================
+ Coverage    89.2%   89.22%   +0.02%
==========================================
  Files         122      122
  Lines        8620     8616       -4
==========================================
- Hits         7689     7687       -2
+ Misses        631      629       -2
  Partials      300      300

Impacted Files
Coverage Δ

send_stream.go
96.55% <ø> (ø)
:arrow_up:

receive_stream.go
96.05% <100%> (+0.03%)
:arrow_up:

window_update_queue.go
100% <100%> (ø)
:arrow_up:

session.go
72.44% <100%> (+0.27%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f78c003...8bd6168. Read the comment docs.


agent: Gracefully handle events for ignored claims

Seems simple enough that I can review this already. It would be interesting for me what happens with returned boolean. Who cares about them? I'm optimistic that this change can be merged like that.

They are used here: https://github.com/beamer-bridge/beamer/blob/5148323511c6c5c77e5a8914db683886a3d24027/beamer/chain.py#L162-L165=
But that something we need to clean up.


Fixed Project Name Conflict on Hex.pm

Fixed project name conflict on hex.pm and added image link in README.md to the project

I suppose you've forgotten to rebase since I've accepted the pr.
Then, we need to think about another solution, because, even if if works, technically, this app is already used in other projects (which should be updated) + the 'dbus' name has been chosen on purpose since D-Bus is a well known protocol.
-> let me contact https://github.com/aforward/dbus author

Ok. So, I suppose we wait for @aforward to change the name of his app then?
On Mon, Mar 7, 2016, 4:05 PM Jean Parpaillon<EMAIL_ADDRESS>wrote:

I suppose you've forgotten to rebase since I've accepted the pr.
Then, we need to think about another solution, because, even if if works,
technically, this app is already used in other projects (which should be
updated) + the 'dbus' name has been chosen on purpose since D-Bus is a well
known protocol.
-> let me contact https://github.com/aforward/dbus author
—
Reply to this email directly or view it on GitHub
https://github.com/lizenn/erlang-dbus/pull/14#issuecomment-193288197.

Would be nice, yes.
Wait & see :)

https://github.com/aforward/sadbus project has been renamed. There's no need for this pr anymore.

Great. I'm just waiting on him to give me add authority, so I can override the dbus on Hex.pm

Great. I'm just waiting on him to give me add authority, so I can override the dbus on Hex.pm


allow passing null to service scope, do not check domains on secretKey auth

#5728  👈 (View in Graphite)
main

How to use the Graphite Merge Queue
Add either label to this PR to merge it via the merge queue:

merge-queue - adds this PR to the back of the merge queue
hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.


feat(openui): update version to 0.3.35

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Current project status

Hi, what is the current status of this project? Is it still actively maintained or are you looking for maintainers?

I moved to https://github.com/s00d/webpack-shell-plugin-next to fix Tapable.plugin is deprecated


Menubar support

Hi, is it possible to create a menubar app via cacao? if so, is it documented?

Possible? Yes. As easy as it should be? No. Documented? Ish.
What I mean is this: you can absolutely use cacao to set up the application delegate cycle and write objc calls directly (or wrap your own pieces) to do the menu bar stuff. If the menu bar stuff feels good and you want to PR it, it'd absolutely be looked at for merging since it's a common enough need.

If the menu bar stuff feels good and you want to PR it, it'd absolutely be looked at for merging since it's a common enough need.

Unfortunately, I have only some experience with swift directly, I've never written a line of  objc 🙃... but I'll try anyway to implement it, is a nice weekend project :)


UseMeasure ref ts error

Reproduce:
import { useMeasure } from "@uidotdev/usehooks";
import React from "react";

const Test = () => {
  const [ref, rect] = useMeasure();
  return
Test
;
};

export default Test;

Fixed here. We'll cut a new release soon.


Panel Create/Remove Fix

Fixed an issue where the panel was not properly being removed with its
children from serverCreatedUI Directory.

Sorry, I can't merge this in, it doesn't make any sense.

Explanation - http://www.zuenstudio.com/?p=28


Error When adding zxing.net.mobile.forms to Project

When I Try and use zxing.net.mobile.android Init() in my main activity I get tons of Resource designer errors. only when i remove the zxing.net.mobile.froms from my droid file does the error go away and im able to make a build. But in doing so I cant get camera view for the scanner

@paranormal39 I had the same issue when trying to use this package in my Android project. This is a pretty big problem as evidenced by this bug. https://github.com/XLabs/Xamarin-Forms-Labs/issues/1125#issuecomment-222151930 The package needs to be compiled with the AppCombat for API 23. Until this is done, the package will have these Resource designer issues. Hopefully, the developer will address this soon.

Well That Sucks any other barcode scanner easy to implement with xamarin forms? Been stuck on this one problem for almost a week and scanner is important to the application. Considering I have the code implemented Would love to resolve this issue and use zxing

I'm using ZXing.Net.Mobile for Forms in my app that's targeting PCL 259. It's working great in iOS, but I'm having this issue as well as another (https://forums.xamarin.com/discussion/66403/xamarin-forms-android-app-crashing-due-to-xlabs-camera-code-after-upgrade-to-xamarin-forms-2-2-0-31#latest) in my Android app. Both issues are a result of Xamarin.Forms 2.0. As for your error, I found this bit of information, but I'm not sure how to use it. I've only been developing for less than a year and working with Xamarin for even less. What do you make of this? https://gist.github.com/rid00z/76906292010e080c7f5eadfb5ca7b107

Hey I actually solved the issue I just commented out zxing.net.mobile.forms.android.Int() to see if it was the zxingforms package and it build! Now the camera works and im able to scan !!!

Glad you got it working! So, you just installed the package and now it is working in your Android app.??? Are you referencing the ZXing.Net.Mobile for Forms anywhere in your MainActivity? I guess it might work for me too if I can just get the Camera working. I'm using the XLabs Camera and it won't work in my Xamarin.Forms <IP_ADDRESS> Android app.

This is fixed in master already and in the 2.1.0 release.


Update PAC and HAL crates

The underlying PAC and HAL crates have been updated with a new organization system. PAC crates that have the same product series and pin count have been collapsed into a single PAC (i.e. atsamd51j19a and atsamd51j20a are now atsamd51j).
The PAC crates should be updated to 0.9.0, and the HAL crate updated to 0.12.0. The feature names that map to each PAC should also be renamed to match the new PAC names.

Update is blocked on atsamd-rs/atsamd#377

Update is blocked on atsamd-rs/atsamd#377


Allow users to add an issue/PR to a board in a different organization

At present, this Action only supports adding an issue or pull request to a project in the same organization as the issue or pull request itself.
This removes that limitation. If the issue/pull request and project have different owners, then instead of directly creating a project item, we will instead create a "draft issue" which will be added to the board.
Fixes #74.
Note that there are pre-existing failing tests in this branch which fail even before my code changes - see #140 for details.

This removes that limitation. If the issue/pull request and project have different owners, then instead of directly creating a project item, we will instead create a "draft issue" which will be added to the board.

I don't believe this would be the right way to handle these cases, since draft issues aren't linked to their underlying content, so the actual issue/pr isn't linked directly.
I don't know, offhand, the origin of this limitation - but I think it's much more likely we'd want a holistic improvement to this in projects instead of attempting to workaround it in a non-intuitive way that might also be confusing.
Draft issues are also non-unique so this could potentially create multiple draft issues with the same content, for instance if a user applies a label, unapplies it, and then reapplies it 2 drafts for the same issue will have been created

@mattcosta7 Thanks for taking the time to review this PR. That's really interesting! I wasn't aware of those limitations - I just saw that you could paste the URL of an external issue into a project board and the title (etc.) showed up, and I thought that would do the trick 😓
Would you be open to having this as some kind of advanced, optional case - perhaps configured with a boolean option which defaults to "off"?  Being able to manage external issues using this workflow would be really valuable to me.
If it's a no (which I understand), then I'll fork this and create my own similar action which offers this functionality, but makes the trade-offs clear.

@mattcosta7 Thanks for taking the time to review this PR. That's really interesting! I wasn't aware of those limitations - I just saw that you could paste the URL of an external issue into a project board and the title (etc.) showed up, and I thought that would do the trick 😓
Would you be open to having this as some kind of advanced, optional case - perhaps configured with a boolean option which defaults to "off"? Being able to manage external issues using this workflow would be really valuable to me.
If it's a no (which I understand), then I'll fork this and create my own similar action which offers this functionality, but makes the trade-offs clear.

We can take a look.  urls do resolve when pasted - I'm not sure offhand whether the graphql api handles this, but if so, that makes sense, and wouldn't have the limitations I discussed!

We can take a look. urls do resolve when pasted - I'm not sure offhand whether the graphql api handles this, but if so, that makes sense, and wouldn't have the limitations I discussed!

I have tested this out extensively, and the URLs do resolve if you use the "create draft issue" GraphQL mutation. You seem to get the exact same result as pasting a URL onto the board.

@mattcosta7 Just to a reminder to take a look at this when you have a chance ❤ Thank you so much!

hey @timrogers sorry - had a really hectic week
I think we'll take this as is for now.  We'll eventually remove this in favor of a more direct way to manage cross-org work,  but for now unblocking this makes sense to me

https://github.com/actions/add-to-project/releases/tag/v0.3.0


Use node14 instead of lts for Travis test

node 16 became LTS version.
Use node14 to prevent Travis test fail
Enact-DCO-1.0-Signed-off-by: Jeonghee Ahn<EMAIL_ADDRESS>

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


allow boards to supply an rc.board init

So far this saves 4 KB of flash on fmu-v2.
TODO: DATAMAN_OPT is broken in master and still broken in this PR

fixes #10961

TODO (later): push pixracer i2c and spi resets (currently in fmu) into board init.

@dagar What would you say about this in http://dev.px4.io/en/hardware/porting_guide.html ?

What sorts of init is done at board level
Where does it have to live in the build tree?

@hamishwillee mainly used for starting things that only exist on that particular board (sensors), but it can also be used for board default parameters and any other special cases.
FMUv5 example - https://github.com/PX4/Firmware/blob/master/boards/px4/fmu-v5/init/rc.board
You can see all the pixhawk 4 sensors being started, but it also sets a larger LOGGER_BUF, and in fresh setups (AUTOCNF section) it sets the SYS_FMU_TASK parameter.
This file is automatically included in the startup scripts if in the board directory at init/rc.board.

@dagar this broke HIL as rc.sensors was only executed if SYS_HITL != 1

Thanks @bkueng I'll fix it.
We should get something simple on Jenkins testing HITL with Gazebo if it's working reasonably well.


Pull Request- main to main

This request is for adding a folder or working artifacts to the main repository.
This folder comprises of the artifacts as stated below-
-Flow Diagrams
-Python Source Code(Jupyter Notebook)
-Open points(with respect to current open issues related to listening time)
-PowerBI dashboard(researchers dashboard)
-Sample files

input file
per user intermediate file
Final CSV file

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

Thanks @kanch21! Does this PR replace PR https://github.com/CUTR-at-USF/muser-dashboard/pull/1? If so, could you please comment on that PR saying so and close it?

This was a draft Pull request which can be replaced by the latest PR. Hence closing this one!

Reopening this request as it was closed by mistake.


Update Footer Links

I fixed the links and added some styling. I think there may be site-wide (about.sourcegraph.com) changes on the footer that we may want to incorporate soon.

The new styles are looking great!


[K8s] [Tool] tools shuffle-files-cleaner

Why are the changes needed?
Add Kyuubi tools cache-file-cleaner on kubernetes.
This tools help to start daemonSet on Kubernetes to clean shuffle file and spark cache file.
By config some envs, cache-file-cleaner will help to check some old file(which depending on configuration) and delete them for free dist.
And after first cleaning, if the free capacity lower than threshold, cache file cleaner will start deep clean to help free dist.
With the cache-file-cleaner, add Dockerfile, entrypoint and daemonSet.yaml to help user to use this tool.
Using threadPool to help delete shuffle files.
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

please take  a look@ulysses-you @pan3793

I'd like to name this tool spark-block-cleaner, shuffle is a little narrow that the blockMgr dir include other blocks e.g. rdd

I'd like to name this tool spark-block-cleaner, shuffle is a little narrow that the blockMgr dir include other blocks e.g. rdd

Block sounds good, will rename in next commit.

About the build-cleaner-image.sh, i want to collect some suggestions. Under the circumstance that Dockerfile forbidden path outside the build context, how could we graceful build dokcer image.

Codecov Report

Merging #768 (4d80350) into master (819484f) will decrease coverage by 1.61%.
The diff coverage is 0.00%.

:exclamation: Current head 4d80350 differs from pull request most recent head 3c8b782. Consider uploading reports for the commit 3c8b782 to get more accurate results

@@             Coverage Diff              @@
##             master     #768      +/-   ##
============================================
- Coverage     79.39%   77.77%   -1.62%
- Complexity        4       10       +6
============================================
  Files           127      132       +5
  Lines          5051     5188     +137
  Branches        654      672      +18
============================================
+ Hits           4010     4035      +25
- Misses          685      792     +107
- Partials        356      361       +5

Impacted Files
Coverage Δ

...scala/org/apache/kyuubi/kubernetes/Constants.scala
0.00% <0.00%> (ø)

...yuubi/kubernetes/KubernetesSparkBlockCleaner.scala
0.00% <0.00%> (ø)

...uubi/engine/spark/operation/ExecuteStatement.scala
84.50% <0.00%> (-2.07%)
:arrow_down:

...cala/org/apache/kyuubi/jdbc/KyuubiConnection.scala
80.00% <0.00%> (ø)

...rg/apache/kyuubi/jdbc/KyuubiDatabaseMetaData.scala
70.58% <0.00%> (ø)

...in/scala/org/apache/kyuubi/jdbc/KyuubiDriver.scala
37.50% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 819484f...3c8b782. Read the comment docs.

thanks, merging to master for v1.3.0


PuTTY's manifest's website isn't the official one.

After some discussion here and here, I discovered PuTTY's website in its manifest isn't the official one.
I'd make a PR but I'm on my phone right now. I hope I can manage to do it later!

really appreciate the report. I've updated the manifest to point to the right place. just to give some context.
Appget's users were never exposed to the unofficial version of putty, the home field is used for informational purposes only. I've confirmed the download links have always pointed to the right place.

Sorry for the late reply. Couldn't get back to you sooner.
Thank you for update and the context as well!


[wip] Fix up scalars

@danking I started throwing this together, seems like it removes most of the foot guns.
Roughly:

ScalarValue is opaque (deprecated the accessor methods, burning them down)
Callers who used to use ScalarValue, should instead downcast a Scalar with Scalar::as_primitive(_opt) etc. and then extract the value using PrimitiveScalar::value etc.
PrimitiveScalar has a new as_<T>() accessor that performs a cast, this can sometimes be useful. Maybe it's unnecessary, and we should just cast the scalar? Not sure yet.
We can make an InnerScalarValue and turn ScalarValue into a unit struct to make it truly opaque.

Okay, I think this needs some fresh eyes in the morning. It's grown fairly large. I think everybody now interacts with a Scalar. The only appearance of ScalarValue should be in Metadata. It's essentially just a serialization shim for Scalar when you the DType is stored somewhere else.


Local per project slushes

I saw this on the readme
All slush-* packages should be installed globally (for now) to be found by the slush executable.
What are the thoughts on installing local?
Currently exploring the possibilities of having smaller custom generators based on a particular project (some already in development) conventions. In these situations, install the generators globally wouldn't be ideal for our case.

Duplicate of https://github.com/slushjs/slush/issues/5

Yes, see #5 for this.


Can you add a clear ReadMe file for both the client and server project

I am facing an issue running the server project, I did
npm i
npm run start
I got this error
MongooseError: The uriparameter toopenUri()must be a string, got "undefined". Make sure the first parameter tomongoose.connect()ormongoose.createConnection()` is a string.
whats the value of process.env.MONGODB_URL?

you should either create a mongodb server locally to give the database's credentials or create a mongodb atlas instance and paste its uri


<=XP Compatibility broke

Shell32 references (used for extracting zips) break compatibility.

oh no

Forgot to close this earlier.


OSError when OS doesn't support file operation

multistore.py uses LockedFile for managing the credential store.  However, if the operating system doesn't support the necessary open+lock file operation https://github.com/google/oauth2client/blob/master/oauth2client/locked_file.py#L338 that's used by the opener class, it will raise this exception (usually an OSError) and likely kill its caller.
At a minimum, multistore_file should probably just return that a credential couldn't be loaded from the store in this case.

Superseded by #470


[Feature]: Support enarx release-specific versions of enarx.dev

Is there an existing issue for this?

[X] I have searched the existing issues

Description
As there will be more documentation upcoming around features documented in enarx, it would be useful to have the site support multiple versions. This could also be helpful in installing the appropriate version in the install section, as well as help keeping the documentation in lock step with currently supported and unreleased enarx version. This would also allow the Install documentation to be different depending if you are installing from git or from published crates.
Acceptance Criteria

Design/proposal created
Buy in from team
Implementation of content
Update in release automation

Suggestions for a technical implementation
An example of this could be found here.

Thank you, Paul! Adding this as a reference of how Docusaurus supports versioning:
https://docusaurus.io/docs/versioning


[Order form] Not correct notification after changing the conditions for the order

Environment: Firefox 114.0.2 (64-bit)
Windows 11 IoT Enterprise, version 22H2
Reproducible: always
Preconditions
Through the admin account, change the minimum number of packages to the minimum amount of payment (500 UAH) for Kharkiv and Kharkiv region.
Steps to reproduce

Go to https://www.greencity.social/#/ubs
Click to order
Choose Kharkiv and Kharkiv region.

Actual result
Not correct notification -  "The minimum order amount must be 500 UAH
Please note that the minimum order must contain at least 500 packages of 120l"
Expected result
Correct notification - "The minimum order amount must be 500 UAH"

Labels to be added
"Bug", Priority ("pri: "), Severity ("severity:"), Type ("UI, "Functional"), "API" (for back-end bugs).

I checked on test and local databases and everything works fine.


Docker deployment

Integrate docker compilation into a single docker image for deployment to docker cloud or similar

[ ] Customized base Dockerfile to extend from

[ ] Base on Debian Jessie
[ ] Integrate nginx base with ability to read in vhost files from compiled source
[ ] Integrate forever for handling running the node app
[ ] Consider using supervisord to handle both runtimes OR context switching containers so a container can server browser or api, but not both. Not sure if a good idea

[ ] Pre-deploy testing by running locally with docker compose
[ ] Pushing to remote registry (use docker cloud for now)
[ ] After deploy, connect to updated container and check for migrations (!! this may warrant moving to another task)

Hi! May I help you doing this task?


More intelligible GUI for custom blocklist

So, the app indicates that you can customize the allowlist and blocklist, however it doesnt explain if the ones marked are going to be deleted, or the unmarked ones; it is a bit confounding. Either that should be explained, or there should be uninstall button below, so the ticked ones to be uninstalled.

Hello, check means to remove/disable it. Problem was closed here:
https://github.com/Sycnex/Windows10Debloater/issues/336#issuecomment-752812731

Hello, check means to remove/disable it. Problem was closed here:
https://github.com/Sycnex/Windows10Debloater/issues/336#issuecomment-752812731

I know what it means. I just think that it may be perplexing for newcomers and should redesigned.

I second this feature, or just to even add it to the README, but it seems it won't be happening soon, with the maintainers not being very active.

I second this feature, or just to even add it to the README, but it seems it won't be happening soon, with the maintainers not being very active.

Yeah, such a shame the project is deprecated.

Yeah, such a shame the project is deprecated.

I've been trying to fix this project up a bit, at least in management (over 100 fixed issues that are still marked as open because of non-GH regulars) and I've been trying to solve a myriad of them over this last week. I do believe in this project, but unless we wake one of the maintainers up from their deep sleep, PRs and fixes won't be happening anytime soon.

Added a label on the form in: #478


npm start

I use the npm start  in the ./ui dir,get the error:
Failed to compile
./src/index.css (./node_modules/css-loader/dist/cjs.js??ref--6-oneOf-3-1!./node_modules/postcss-loader/src??postcss!./src/index.css)
Error: Cannot find module<EMAIL_ADDRESS>

Please fill in the template when creating an issue. Without providing any context, all I can say is npm start does work for me :wink:
https://www.loraserver.io/lora-app-server/community/source/ contains some info when building from source.


net/http: TestTransportMaxConnsPerHost flakes

I've seen this a few times now. @fraenkel, could you take a look?
https://storage.googleapis.com/go-build-log/b6c795d5/android-amd64-emu_95c3cb1f.log
--- FAIL: TestTransportMaxConnsPerHost (0.05s)
    transport_test.go:638: request failed: Get https://<IP_ADDRESS>:34180: write tcp <IP_ADDRESS>:37680-><IP_ADDRESS>:34180: use of closed network connection
2019/05/01 16:13:25 http: TLS handshake error from <IP_ADDRESS>:45068: read tcp <IP_ADDRESS>:36221-><IP_ADDRESS>:45068: use of closed network connection
2019/05/01 16:13:25 http: TLS handshake error from <IP_ADDRESS>:45070: read tcp <IP_ADDRESS>:36221-><IP_ADDRESS>:45070: use of closed network connection
2019/05/01 16:13:25 http: TLS handshake error from <IP_ADDRESS>:45074: read tcp <IP_ADDRESS>:36221-><IP_ADDRESS>:45074: use of closed network connection
2019/05/01 16:13:25 http: TLS handshake error from <IP_ADDRESS>:45066: read tcp <IP_ADDRESS>:36221-><IP_ADDRESS>:45066: use of closed network connection
2019/05/01 16:13:25 http: TLS handshake error from <IP_ADDRESS>:45072: read tcp <IP_ADDRESS>:36221-><IP_ADDRESS>:45072: use of closed network connection
2019/05/01 16:13:25 http: TLS handshake error from <IP_ADDRESS>:45069: read tcp <IP_ADDRESS>:36221-><IP_ADDRESS>:45069: use of closed network connection
2019/05/01 16:13:25 http: TLS handshake error from <IP_ADDRESS>:45071: read tcp <IP_ADDRESS>:36221-><IP_ADDRESS>:45071: use of closed network connection
2019/05/01 16:13:25 http: TLS handshake error from <IP_ADDRESS>:45073: read tcp <IP_ADDRESS>:36221-><IP_ADDRESS>:45073: use of closed network connection
2019/05/01 16:13:25 http: TLS handshake error from <IP_ADDRESS>:45067: write tcp <IP_ADDRESS>:36221-><IP_ADDRESS>:45067: use of closed network connection
2019/05/01 16:13:25 http: TLS handshake error from <IP_ADDRESS>:45080: write tcp <IP_ADDRESS>:36221-><IP_ADDRESS>:45080: use of closed network connection
FAIL
exitcode=1go_android_exec: adb exec-out rm -rf /data/local/tmp/go_android_exec/http.test-20892

Oh, and ignore the http: TLS handshake error from spam. That's an unrelated issue that needs fixing. (Tests shouldn't spam)
The concerning part here is only:
--- FAIL: TestTransportMaxConnsPerHost (0.05s)
    transport_test.go:638: request failed: Get https://<IP_ADDRESS>:34180: write tcp <IP_ADDRESS>:37680-><IP_ADDRESS>:34180: use of closed network connection

on the plus side, I can reproduce it
$ ~/workspace/go/bin/go test -run TestTransportMaxConnsPerHost -count=100
--- FAIL: TestTransportMaxConnsPerHost (0.01s)
    transport_test.go:638: request failed: Get https://<IP_ADDRESS>:39561: write tcp <IP_ADDRESS>:36518-><IP_ADDRESS>:39561: use of closed network connection

another oddity that randomly appears when the other paases
$ ~/workspace/go/bin/go test -run TestTransportMaxConnsPerHost -count=100 -race
--- FAIL: TestTransportMaxConnsPerHost (0.03s)
    transport_test.go:662: Too many get connections (http2): 2
    transport_test.go:676: Too many get connections (http2): 3
--- FAIL: TestTransportMaxConnsPerHost (0.03s)
    transport_test.go:662: Too many get connections (http2): 2
    transport_test.go:676: Too many get connections (http2): 3
FAIL

@bradfitz I know how to make the test pass, but it is just papering over a potential issue.
The failing client is the 11th one. We have created a bit of a race between the current connection being closed and what connection the next client gets. It is quite a lot of code before MarkDead() is called in http2, and that window between Close() and MarkDead() allows any client to retrieve a connection that is closed.
The test case is simulating a network failure. I decided to try and make it cleaner by adding transport.CloseIdleConnections after the conn.Close(). Much to my surprise we end up in a hang at transport.go: line 1030.

I don't see how to fix the CloseIdleConnections which would have fixed the testcase.
The transport tracks host connection counts. When we close idle connections, the counts are not corrected for http2. We don't know the connect method key, nor do we know which connections are being closed on the http2 side.

I spoke too soon. We have the connection key and we can remove the host connection count. However, we really have no idea if the http2 connection is really closed or not.

I have a fix coming. The definition of MaxConnPerHost once you CloseIdleConnections for http/2 is not always exact but it does attempt to do the right thing.

still occurs in https://storage.googleapis.com/go-build-log/47ecde0e/linux-amd64-race_2b57df15.log
cc @bradfitz @fraenkel

@cuonglm This is a different issue. Its the one I saw here https://github.com/golang/go/issues/31784#issuecomment-488530006

@fraenkel do we have an issue to track it already?

Not that I know of.

@fraenkel I created one.


Statement more clear.

Thus we can know what kind data is passed in method

So what happens if the input isn't either an array or a string?


For odoo 17

For odoo 17: request session don't return company_id in session info

same problem. Need an update


Get javadoc deployed to GitHub project page

I've started this work on my fork, waiting for either the javabi-sizeof dependency to be removed or added to Maven Central.


Using Options BaseUrl assertion fails

Package
dio
Version
5.0.0
Output of flutter doctor -v
No response
Dart Version
No response
Steps to Reproduce
for example make a Dio client like this:
 static const String _baseURL = "https://example.com"

 final _http = Dio(
    BaseOptions(
      baseUrl: _baseURL,
      headers: {
        "accept": "application/json",
        "x-requested-With": "XMLHttpRequest",
        'content-type': 'application/json',
      },
    ),
  );

Expected Result
the client should send the request and it works normally.
Actual Result
Assertion failed:
options.dart:103
baseUrl.isEmpty || Uri.parse(baseUrl).host.isNotEmpty
is not true

@dafinoer Can you identify if this is valid and not being covered in the previous tests?

@dafinoer Can you identify if this is valid and not being covered in the previous tests?

well I didn't check the testing, however by changing the assertion from :
 assert(baseUrl.isEmpty || Uri.parse(baseUrl).host.isNotEmpty)
to :
assert(baseUrl.isEmpty || Uri.parse(baseUrl).host.isEmpty)
it works, fine , tested on web and mobile platforms , I have made a pull-request as well.

Sure, just called who authored this and see if additional information can be provided.

@dafinoer Can you identify if this is valid and not being covered in the previous tests?

well I didn't check the testing, however by changing the assertion from :
 assert(baseUrl.isEmpty || Uri.parse(baseUrl).host.isNotEmpty)
to :
assert(baseUrl.isEmpty || Uri.parse(baseUrl).host.isEmpty)
it works, fine , tested on web and mobile platforms , I have made a pull-request as well.

if you add isEmpty, then you set the URL like hallo world the result true we know the hallo world is an incorrect URL.
please check this unit test: link

@dafinoer Can you identify if this is valid and not being covered in the previous tests?

well I didn't check the testing, however by changing the assertion from :
 assert(baseUrl.isEmpty || Uri.parse(baseUrl).host.isNotEmpty)
to :
assert(baseUrl.isEmpty || Uri.parse(baseUrl).host.isEmpty)
it works, fine , tested on web and mobile platforms , I have made a pull-request as well.

When you add isEmpty, then you set the URL like hallo world the result true we know the hallo world is an incorrect URL.
please check this unit test: link

@dafinoer  I'm not really getting what you are saying:
here : https://github.com/cfug/dio/blob/ac252d876be138169d30731dae40ad1b2716d270/dio/test/options_test.dart#L391
the test is validating that the host empty, which is correct.
but in the implementation :
assert(baseUrl.isEmpty || Uri.parse(baseUrl).host.isNotEmpty)
we should fail if the host isEmpty , not if the host isNotEmpty?
or I'm missing something here?

@dafinoer Can you identify if this is valid and not being covered in the previous tests?

well I didn't check the testing, however by changing the assertion from :
 assert(baseUrl.isEmpty || Uri.parse(baseUrl).host.isNotEmpty)
to :
assert(baseUrl.isEmpty || Uri.parse(baseUrl).host.isEmpty)
it works, fine , tested on web and mobile platforms , I have made a pull-request as well.

When you add isEmpty, then you set the URL like hallo world the result true we know the hallo world is an incorrect URL.
please check this unit test: link

in the testing here: https://github.com/cfug/dio/blob/ac252d876be138169d30731dae40ad1b2716d270/dio/test/options_test.dart#L391
the host will be empty , hence this is correct:
expect(Uri.parse(opt6).host.isNotEmpty, false);
but it's confusing it should be expect(Uri.parse(opt6).host.isEmpty, true);
so now in the test we fail if the host is empty.
but in the implementation:
assert(baseUrl.isEmpty || Uri.parse(baseUrl).host.isNotEmpty)
we asserting/failing if the host is not empty , which is wrong , we should fail if it's empty, which mean we have no host!
or am I missing something here?

after deep investigations , the error was due to bad configurations on my end , it used to work with older version tho.
sorry for the inconvenience .

@dafinoer Could you help us to document this better to avoid such issues again?

@AbanoubNassem  What exactly was the bad configs, as I am having the same issue that worked before?


Install on linux without admin rights

I want to install this on my work computer.
Is there a way to install the zsh plugin in another directory?

Yeah, maybee it would be better to install it in another directory than /usr/share/. Maybee I'll change that. For the meantime, you can just clone this repo anywhere you want, source the fzf-help.zsh file, and set the binding:
source /some-directory/fzf-help/src/fzf-help.zsh
zle -N fzf-help-widget
bindkey "^A" fzf-help-widget


support tolerations + small improvements + bump chart version

include

add default amd architecture
support tolerations for code executor
https://github.com/tryretool/retool-helm/pull/130
https://github.com/tryretool/retool-helm/pull/169

any clue why updating your app deployment tolerations to its own node pool would cause postgres db timeouts?? Im reaching health EOF errors causing pods to restart


Mounts disappear with DISMOUNT command.

It doesn't happen every time, but sometimes when you do the SRC.DISMOUNT the mount just disappear (like .remove) but the owner still sees the mount in the follower list, I think it means that doesn't call the @FollowerUpdate trigger at all. If you have a custom Pet System like me it makes it very hard to restore the mount.

can confirm, just tested this and dismount made my horse disappear about 1 seconds after I used .dismount

Me also i confirm, this issuee is very old, is arount 1 yeah i see it..
Not sure if connected only whit shrink pet or is general one.

On my side I cant reproduce....
[plevel 1]
test

[FUNCTION test]
src.dismount

@cbnolok could you give me an update on this? It's really a problem when you have a customized experience system for Pets and after 1 month of farming the Pet just magically disappear. Players are getting upset about this.

Sadly i don't see me having time or energies for sphere in the near future, i read that perhaps someone fixed this for the time being via script?
Il giorno 21 gen 2022, 21:47, alle ore 21:47, Luxion @.> ha scritto:
@. could you give me an update on this? It's really a problem

when you have a customized experience system for Pets and after 1 month
of farming the Pet just magically disappear. Players are getting upset
about this.
--
Reply to this email directly or view it on GitHub:
https://github.com/Sphereserver/Source-X/issues/728#issuecomment-1018847691
You are receiving this because you were mentioned.
Message ID: @.***>

Oh, sorry to hear that, I don't know if someone fixed via script but if someone did would be lovely, do you have any idea about who can be? Thanks for your answer and collaboration anyway ;) @cbnolok

With help of @JulianUO , I achieve to make a partial "reprduction".
When you ride a mount, the real NPC stay there and is hidden next to you.  It's what happen to you @LuxionUO ?
If you want to test, you can see your hidden npc by activating .allshow + .debug ( only after this pull request is merge https://github.com/Sphereserver/Source-X/pull/829 )
https://user-images.githubusercontent.com/51728381/150624295-c7af2d91-eb36-49ba-b3fc-13c6eab90bd9.mp4

Posting here some teport on discord
`Hi, a bug is happening with me when the char is mounted (tested with llama and horses) and the shard saves when you are on the same tile of a field spell (Paralyze, Fire or Poison) that you cast. When you restart sphere, the mount dies and the body is changed to a random human.
Steps to trigger this bug:
1st: Cast a field type spell (Paralyze, Fire or Poison)
2nd: Step on the field with the same char that you cast the field.
3rd: Save the shard (The following message appears “mount_name_here appears to have decided that it is better off without a master!” and in the sphere console an error will appear “code=0x1103 (Ridden NPC not acting as such)".
4th: Close/Restart Sphere.
5th: When you enter your shard and tries do double click your char to dismount, the mount dies.
Tested with Sphere X - Aug 20 2022 11:52 am (But this is happening with old builds too).`

So, does it only happens when animal is dead, or happens if he is alive ?
I can't reproduce it.

Set a z Lower will probably prevent futur damage.
What aboit the poison or tick damage comming to the pet after you ride it.  Pet should become invul? If no,.we could make a check when NPC die if isridden, unmount and print a message npc is death.

looking back. It wasn't based on damage when I replicated this. It just doesn't always happen. I did not damage the mount at all when I confirmed this happened.
I dont think changing the Z level for an offline mount to keep it from getting damaged by AOE spells is the right solution here. That also would be one that is not quite complete in it's solution, since someone on a mountain top could potentially be at the highest possible z level.

I think a simply "patch" could be to peint a message to horse owner his  pet is death and force an unmount...  Not tested.

you probably should test those first

It will test, it is not real pull request is just to talk about the code. I prefer not to lost fime coding something that will never be accepted cos dosnt get into sphere's standards.
The z-127 fix is to avoid damage taken by t_fire or firefields. I Think as u, it dosnt look as the problem of the issue. Did not test but I someone told it were happening.
The last fix I added is to unmount char if mount dies and is being ridden.
Luxos or anyone able to reproduce, should add this event to mounts to see if it is caused by the mounts being dead or mounts can be damaged by.
On=@gethit
if (&staft_ridden)
serv.log takes damage while ridden Hits->  /  Damage->
endif
on=@death
if (&staft_ridden)
serv.log animal dead while ridden.
endif

I was able to replicate the results, but not consistently.
You dismount using .dismount, the mount disappears 1 seconds later.
no trace of the mount when it happens

I tried to reproduce this many times. I can't unless mount is dead

With @Tolokio PR https://github.com/Sphereserver/Source-X/pull/931
When your pet die you will know it.
I'm pretty certain this issue is link to a death horse but you know it only when you unmount. Now, youbwill unmount automatic and you will be able to modify @death trigger if you want.
Since we dont have more way to reproduce your bug, we should close this issue.

The message "mounts appear to have decided..." could be provoked because when u attack a pet it decides is better without you.  Ill try to test asap.

Could we close this?

I havent been able to recreate reliably. ill try again.
@drk84 may i have access to close out issues, for times when they are abandoned? ill go through my open ones this evening also ;)

I didn't experience this issue again honestly, if it will happen again I will reopen the ticket.

Re-open this issue plz
Somehow mounts can change their action. Probably by script.
Possible way to reproduce the bug: Just change action to a mount when it is ridden. Then do garbage collection, or save, or reset server (I did not test it)

You can try to add a serv log in the source when the action is changed from npcact_ridden, it might point to the script line involved

I just wonder how ridden horse change it's action, because there should be no way, even I am always mounting a horse all the time and it never changed it's action for me, but if there is a bug we should check it.
If you change it's action from script, this is totally script-side bug, honestly I totally disagree to add limits because other people can like to do other things with changing that actions, also you have never remove STATF_RIDDEN flag from ridden horse for any reason, STATF_RIDDEN means it's used by someone else so if you remove that flag by script, that makes Sphere count that npc is not ridden and remove it's linked objects from world.
But if the action changed by the server, we need more information about that for fixing it, because this never happened to me honestly so I have no idea how to reproduce it.

Sphere right now delete the mount if dont have the follower requirements:

If have the Statf_ridden, the Action need to be NPCACT_RIDDEN
Require a link mount item (t_figurine or t_eq_horse)

So please, need re-evaluation or we process to close the issue

Hi there. Sorry. I have no time for sphere and Im not checking emails, gits or discord.
This bug never happened to me and im not able to reproduce it. Until I know, someone reported that rarely some mounts still being removed in his living shard. I dont remember well, but he gave me info that allowed me to track his issue to one of the FixWeirdness() functions. So somehow skill still being changed.
As I said when I did the fix for the mounts system this system can be improved, have been untouched for many years until I did. And my programming skill are very bad for it.

honestly I totally disagree to add limits because other people can like to do other things with changing that actions

I totally agree with this. And told about this before. We should rework the system to let people use ACTION on mounted chars. In my case I would like to use this feature so I dont need to fake actions of ridden mounts during combats and let the mounts do the action itself.
Right now, the "mount status" is stored as: statflag->statf_ridden and by action->npc_act_ridden (or something like this)
There is no real need to have 2 places to store this info. For me it is duplicated information. I think I understand it is done like this for minimal optimization at certain point the of the code, but it dosnt worth to have two places with the same info for that minimal optimization. We should remove one of them and I propose we should free "action" to let players use it.
@cbnolok

You can try to add a serv log in the source when the action is changed from npcact_ridden, it might point to the script line involved
-As im not able to reproduce the issue, it would not help. But we could add a check to main to avoid the mount to be removed when it loses the action but it is being used by a char, and as u say add log always this happens. So this way Fixweridness() will fix automaticaly the problem instead just removing the problem.


Py38

Should help with https://github.com/conda-forge/kiwipy-feedstock/pull/15

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Thanks @ocefpaf !


[Bug]: next.config.js > redirects is not respected

Summary
Redirects defined via next.config.js#redirect are note respected when deployed to netlify using @netlify/plugin-next.
This happens in a Next.js v14 app using traditional pages/ (I have not tested with app/ directory routing). This also happens on Next.js v13 and has been an issue for some time. I know this used to work at some point, but it has been some time since it did work.
I suspect that generateRedirects should probably do something with routes-manifest.json#redirects.
Reference reports:

https://answers.netlify.com/t/next-config-js-redirects-works-correctly-on-local-and-vercel-but-not-on-netlify/84420
https://answers.netlify.com/t/nextjs-next-config-js-redirects-not-working/93077 (I posted this)

A link to a reproduction repository
https://github.com/dragons-library/next-netlify-redirect-issue
Expected Result
https://next-netlify-redirect-issue.netlify.app/next-redirect should redirect to https://next-netlify-redirect-issue.netlify.app/redirect-success
Actual Result
Does not redirect and 404s when deployed to netlify.
Steps to reproduce
Redirect failing on Netlify

visit https://next-netlify-redirect-issue.netlify.app
click either link
Netlify Redirect navigates to /netlify-redirect (defined in netlify.toml and works as expected)
Next Redirect navigates to /next-redirect (defined in next.config.js and does NOT work as expected)

Redirect working locally

then, checkout the reproduction repo locally and test...
git clone https://github.com/dragons-library/next-netlify-redirect-issue.git
cd next-netlify-redirect-issue
npm install
npm run dev
visit http://localhost:3000/next-redirect
if you deploy locally via netlify cli, the /next-redirect stops working locally

Next Runtime version
4.41.1
Is your issue related to the app directory?

[ ] Yes, I am using the app directory

More information about your build

[X] I am building using the CLI
[X] I am building using file-based configuration (netlify.toml)

What OS are you using?
None
Your netlify.toml file

`netlify.toml`
[build]
  command = "npm run build"
  publish = ".next"

[[plugins]]
  package = "netlify-plugin-cypress"

[[redirects]]
  from = "/netlify-redirect"
  to = "/redirect-success"

Your public/_redirects file

`_redirects`
# Paste content of your `_redirects` file here

Your next.config.js file

`next.config.js`
module.exports = {
  async redirects() {
    return [
      {
        source: '/next-redirect',
        destination: '/redirect-success',
        permanent: false,
      },
    ];
  },
};

Builds logs (or link to your logs)

Build logs
9:32:38 PM: Netlify configuration property "redirects" value changed to [
9:32:38 PM:   {
9:32:38 PM:     from: "/netlify-redirect",
9:32:38 PM:     query: {},
9:32:38 PM:     to: "/redirect-success",
9:32:38 PM:     force: false,
9:32:38 PM:     conditions: {},
9:32:38 PM:     headers: {}
9:32:38 PM:   },
9:32:38 PM:   { from: "/_next/static/*", to: "/static/:splat", status: 200 },
9:32:38 PM:   {
9:32:38 PM:     from: "/_next/image*",
9:32:38 PM:     query: { url: ":url", w: ":width", q: ":quality" },
9:32:38 PM:     to: "/_ipx/w_:width,q_:quality/:url",
9:32:38 PM:     status: 301
9:32:38 PM:   },
9:32:38 PM:   { from: "/_ipx/*", to: "/.netlify/builders/_ipx", status: 200 },
9:32:38 PM:   {
9:32:38 PM:     from: "/api/*",
9:32:38 PM:     to: "/.netlify/functions/___netlify-handler",
9:32:38 PM:     status: 200
9:32:38 PM:   },
9:32:38 PM:   {
9:32:38 PM:     from: "/favicon.ico",
9:32:38 PM:     to: "/favicon.ico",
9:32:38 PM:     conditions: { Cookie: [Array] },
9:32:38 PM:     status: 200
9:32:38 PM:   },
9:32:38 PM:   {
9:32:38 PM:     from: "/logo-netlify.svg",
9:32:38 PM:     to: "/logo-netlify.svg",
9:32:38 PM:     conditions: { Cookie: [Array] },
9:32:38 PM:     status: 200
9:32:38 PM:   },
9:32:38 PM:   {
9:32:38 PM:     from: "/*",
9:32:38 PM:     to: "/.netlify/functions/___netlify-handler",
9:32:38 PM:     status: 200,
9:32:38 PM:     conditions: { Cookie: [Array] },
9:32:38 PM:     force: true
9:32:38 PM:   },
9:32:38 PM:   {
9:32:38 PM:     from: "/_next/data/_UlOizIbfHuw31IzA8GOY/index.json",
9:32:38 PM:     to: "/.netlify/functions/___netlify-handler",
9:32:38 PM:     status: 200,
9:32:38 PM:     force: false
9:32:38 PM:   },
9:32:38 PM:   {
9:32:38 PM:     from: "/",
9:32:38 PM:     to: "/.netlify/functions/___netlify-handler",
9:32:38 PM:     status: 200,
9:32:38 PM:     force: false
9:32:38 PM:   },
9:32:38 PM:   {
9:32:38 PM:     from: "/_next/data/_UlOizIbfHuw31IzA8GOY/redirect-success.json",
9:32:38 PM:     to: "/.netlify/functions/___netlify-handler",
9:32:38 PM:     status: 200,
9:32:38 PM:     force: false
9:32:38 PM:   },
9:32:38 PM:   {
9:32:38 PM:     from: "/redirect-success",
9:32:38 PM:     to: "/.netlify/functions/___netlify-handler",
9:32:38 PM:     status: 200,
9:32:38 PM:     force: false
9:32:38 PM:   },
9:32:38 PM:   {
9:32:38 PM:     from: "/*",
9:32:38 PM:     to: "/.netlify/functions/___netlify-handler",
9:32:38 PM:     status: 200
9:32:38 PM:   }
9:32:38 PM: ].

Function logs

Function logs
# Paste logs here

.next JSON files

generated .next JSON files
.next/routes-manifest.json
{
  "version": 3,
  "pages404": true,
  "caseSensitive": false,
  "basePath": "",
  "redirects": [
    {
      "source": "/:path+/",
      "destination": "/:path+",
      "internal": true,
      "statusCode": 308,
      "regex": "^(?:/((?:[^/]+?)(?:/(?:[^/]+?))*))/$"
    },
    {
      "source": "/next-redirect",
      "destination": "/redirect-success",
      "statusCode": 307,
      "regex": "^(?!/_next)/next-redirect(?:/)?$"
    }
  ],
  "headers": [],
  "dynamicRoutes": [],
  "staticRoutes": [
    {
      "page": "/",
      "regex": "^/(?:/)?$",
      "routeKeys": {},
      "namedRegex": "^/(?:/)?$"
    },
    {
      "page": "/redirect-success",
      "regex": "^/redirect\\-success(?:/)?$",
      "routeKeys": {},
      "namedRegex": "^/redirect\\-success(?:/)?$"
    }
  ],
  "dataRoutes": [],
  "rsc": {
    "header": "RSC",
    "varyHeader": "RSC, Next-Router-State-Tree, Next-Router-Prefetch, Next-Url",
    "prefetchHeader": "Next-Router-Prefetch",
    "contentTypeHeader": "text/x-component"
  },
  "rewrites": []
}

This rough patch resolves my immediate use case (simple redirects), verified via patch-package and deployed to netlify. Probably needs to be fleshed out more to handle all of the NextJS redirect features (has, missing, etc).
<EMAIL_ADDRESS>diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 7002f41..8577698 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -180,7 +180,35 @@ const generateDynamicRewrites = ({ dynamicRoutes, prerenderedDynamicRoutes, midd
 exports.generateDynamicRewrites = generateDynamicRewrites;
 const generateRedirects = async ({ netlifyConfig, nextConfig: { i18n, basePath, trailingSlash, appDir }, buildId, apiLambdas, }) => {
     const { dynamicRoutes: prerenderedDynamicRoutes, routes: prerenderedStaticRoutes } = await (0, fs_extra_1.readJSON)((0, pathe_1.join)(netlifyConfig.build.publish, 'prerender-manifest.json'));
-    const { dynamicRoutes, staticRoutes } = await (0, fs_extra_1.readJSON)((0, pathe_1.join)(netlifyConfig.build.publish, 'routes-manifest.json'));
+    const { redirects, dynamicRoutes, staticRoutes } = await (0, fs_extra_1.readJSON)((0, pathe_1.join)(netlifyConfig.build.publish, 'routes-manifest.json'));
+
+    netlifyConfig.redirects.push(...redirects.reduce((redirects, redirect) => {
+        const { source: route, destination: to, statusCode: status, has, missing, internal } = redirect;
+        // TODO: confirm we should skip all `internal` routes
+        if (internal) {
+            return redirects;
+        }
+
+        // TODO: support missing / has
+        if (missing || has) {
+            console.warn('[skipping unsupported NextJS redirect]', redirect);
+            return redirects;
+        }
+
+        return [
+            ...redirects,
+            ...(0, utils_1.redirectsForNextRoute)({
+                route,
+                basePath,
+                to,
+                status,
+                buildId,
+                force: true,
+                i18n: null,
+            }),
+        ];
+    }, []));
+
     if (i18n && i18n.localeDetection !== false) {
         netlifyConfig.redirects.push(...generateLocaleRedirects({ i18n, basePath, trailingSlash }));
     }

bumping this, I need Next.js rewrites in order to redirect my API routes. Have used the patch in the time being but would much prefer this resolved in the package.

bumping this, I need Next.js rewrites in order to redirect my API routes. Have used the patch in the time being but would much prefer this resolved in the package.

I had this issue recently, I was told by support that Netlify is currently working to resolve known issues for their nextjs 13/14 runtimes, and was asked to use a _redirects or netlify.toml file instead.

bumping this, I need Next.js rewrites in order to redirect my API routes. Have used the patch in the time being but would much prefer this resolved in the package.

I had this issue recently, I was told by support that Netlify is currently working to resolve known issues for their nextjs 13/14 runtimes, and was asked to use a _redirects or netlify.toml file instead.

I tried both _redirects and a normally use a netlify.toml, but I think that API routes can't be mapped with these / I couldn't figure out how to get them to work with it.

Hi, I'm dealing with the same problem. Any solution?

When I was using Umami, I also encountered this issue. I hope Netlify can fix this issue

I think this is resolved with v5 of the plugin. I updated @netlify/plugin-nextjs to 5.0.0 and removed my workaround and all my redirects seem to be working as expected, including ones that previously didn't work.
If you're on Next.js >= 13.5 and node >= 18, give the v5 plugin a try and it should hopefully resolve your issues.

Fixed in v5.


It is not possible to edit the route

Netbird version  - v0.10.7
Screenshot: https://i.imgur.com/UVOoqhf.png

Hey @vitaleg
You must be running Management version 0.10.5 or below. There was a bug in the route API.
To check the version run:
 docker inspect <MANAGEMENT IMAGE> | grep 'org.opencontainers.image.version'

Could you please update your self-hosted Management service docker container if it is lower than v0.10.6?

Yes, you're right. I thought I had updated the version.


[Urls] Mobile Apps for Windows without installers (QField and Input)

Hi guys,
Description
Page URL: https://qgis.org/en/site/forusers/download.html#apps
MIssing installers in the  Windows apps URL links for Input and Qfield point to directories without installers.
Qfield - empty diretories:
https://download.opengis.ch/qfield/ci-builds/win/
https://download.opengis.ch/qfield/ci-builds/win/beta
Input - empty directory:
https://www.dropbox.com/s/7su0dvsg4qsgyiy/inputapp-win-x86_64-7fa4844736f549dc12e1def1ac26ad36a994c3ec.exe?dl=0
@m-kuhn and @saberraz.
Cheers

@jonnyforestGIS please create an issue on the Input and QField sites, or ping @mbernasocchi or @saberraz

Hi @rduivenvoorde  the QField link is working. Only Input is broken. If you want we can close this for now and I try to speak with @saberraz . Cheers


Update to closure-util 1.7.0

With this PR we change from closure-util 1.6.1 to 1.7.0. This is to use the latest version of Closure Compiler (v20150729). See https://github.com/openlayers/closure-util/pull/67.

+1, thanks

Thanks for the review @fredj.


Nadro/3686/file swapping while executing

closes https://github.com/KittyCAD/modeling-app/issues/3686
related to https://github.com/KittyCAD/modeling-app/issues/3470
Technical bits
I implemented a promise rejection on the pendingCommands which sends an error to the KCL code then we can catch it within the JS _executor function as well as propagating it through the executeAst call.

After we interrupt the executeAst don't run some scene setup since we will be immediately starting a new scene, only run the cleanup.
I detect the custom reject error within langHelper's executeAst to detect a KCL error that isn't actually a KCL error. It is my custom error. This allows me to say the commands will be interrupted.
TODO, sendSceneCommand had an uncaught promise handler. I've added a TODO one. This showed up because of my promise rejection code.

Benefits

When using the Project Files Pane you can switch between files that are big and small and it will cancel the previous load and start loading the new file you clicked.
When using a large file (lego 9x18) you will be able to edit within the codemirror pane and it will restart the entire rendering instead of waiting for the entire renderer to finish before using your new code input.
e.g.

// within the 9x18 lego file
const lbumps = 9 // number of bumps long
const wbumps = 18 // number of bumps wide

Try editing these values while in the main branch, you will see that the original code will still be executing. In my branch if you edit these they will kill the previous execution and start rendering the new dimensions. I think this is quite useful.

I still think there's a race condition, or at least one waiting to happen, where the Rust isn’t currently waiting on any promise in pendingCommands. It could be awaiting something else. Then rejecting everything in pendingCommands won’t stop the executor (because pendingCommands is empty).
Even if there's no such thing now, I don't think there's a guarantee that everything that the WebAssembly module could await is stored in pendingCommands.
This is why the idea came up of having sendModelingCommandFromWasm() check if executeIsStale is true, and if so, throw.

It could be awaiting something else

What else could it be awaiting? afaik sendModelingCommandFromWasm is the only way that rust interfaces with the typescript so I don't understand what else it could be awaiting on?
The executeIsStale ideas is to send that flag to rust yeah? how would that be done, like next time rust calls sendModelingCommandFromWasm we return the result plus the flag, in which case we're waiting on the next time rust makes the call, and I guess I don't see how that's much different from just rejecting all the promises?
I'm on board just don't understand the mechanics, and rejecting the promises is kinda a hack since it's just giving rust back something it doesn't expect as a way to stop the exectution.

This is why the idea came up of having sendModelingCommandFromWasm() check if executeIsStale is true, and if so, throw.

in which case we're waiting on the next time rust makes the call

I am open to other ideas for rejecting the promises but I think that waiting for another call to sendModelingCommandFromWasm to come in to cancel feels like it could cause problems as well?
What if it cannot send another command but the executor is still running? What if it takes X amount of time longer than expected?
I think in any solution we come up with, I feel as if we should be able to trigger a line of code that says please stop everything right now.

tl;dr: I think the PR is great as is. With 3 additional lines, I think it can also be robust to future changes that could cause subtle race condition bugs.

The executeIsStale ideas is to send that flag to rust yeah? how would that be done, like next time rust calls sendModelingCommandFromWasm we return the result plus the flag, in which case we're waiting on the next time rust makes the call, and I guess I don't see how that's much different from just rejecting all the promises?

To be clear, I'm not suggesting an alternative as much as an additional change.
The idea is to additionally modify sendModelingCommandFromWasm() in engineConnection.ts so that before it calls this.sendCommand(), it does something like this:
if (kclSingleton.executeIsStale) {
  return Promise.reject(new Error(...))
}

In the case that rejecting promises doesn't work, yes, we would be waiting on the next time that Rust calls sendModelingCommandFromWasm(). This approach is different from rejecting all promises because it would work even if there were no outstanding pendingCommands promises at the time when we reject them.
I think doing both would be good because rejecting promises prevents waiting when a promise exists. But the executeIsStale check guarantees that we don't try to send more commands to the engine when there weren't commands already sent.

I'm on board just don't understand the mechanics, and rejecting the promises is kinda a hack since it's just giving rust back something it doesn't expect as a way to stop the exectution.

I admit that this new idea is hacky too, in its own way.
I actually think the promise rejection approach is clever and fine because the Rust code already has a mechanism for handling rejected promises. It's just an Err of the Result enum. It must handle this case because there could always be a network I/O error.

What else could it be awaiting? afaik sendModelingCommandFromWasm is the only way that rust interfaces with the typescript so I don't understand what else it could be awaiting on?

I admit that I don't think it awaits anything else right now. But there's no guarantee that such a change won't happen in the future, so it makes me a little nervous.
But if you're sure @Irev-Dev that we don't have any other way to do anything async and we're not likely to ever do it, we can ignore this. I just don't like creating landmines for our future selves.

I feel as if we should be able to trigger a line of code that says please stop everything right now.

Ignoring WebWorkers, JavaScript is single threaded. So if we're in a click handler determining that the user switched files, that means Rust is blocked on an await.
That's why the promise rejection is a great approach, IMO. It's exactly a way to say "stop everything right now". The only potential problem is that we don't have a reference to the particular promise that Rust is awaiting, which is why I'm suggesting this additional change.
Does that make sense? Sorry if I'm worrying for nothing.

That's why the promise rejection is a great approach, IMO. It's exactly a way to say "stop everything right now". The only potential problem is that we don't have a reference to the particular promise that Rust is awaiting, which is why I'm suggesting this additional change.

I like this. Thanks for taking the time to explain your thought process. I agree that if we have both we are limiting the chances of a race condition or poor behavior. Your suggestion of both is great since either can trigger first and the expected out come should be the same.
In this comment above I'll write some detection logic to only stop the modeling commands from going through in both of these locations. We will want the scene commands to go through.
I really appreciate the discussion and suggestions, thanks Jon! I'll work on this tomorrow.

if (kclSingleton.executeIsStale) {
  return Promise.reject(new Error(...))
}

makes sense to me.

btw this to me seems like it's most likely a circular dependency issue. looking at it atm.


Question: Can customRender be the name of a function?

Can customRender be the name of a function instead of the full function?
I tried and it did not work, but I may have the syntax wrong.

Show me how you're implementing

}, {
name: "b",
options: {
filter: true,
customRender: handleRender (index, value, updateValue)
}
}

If handleRender is a function you defined just simply change it to
 {
name: "b",
options: {
filter: true,
customRender: handleRender
}


Use new Link component on inventory/people and location pages

Thanks Constanza!! We missed the batch details modal with link to accession id

This is the line we were talking about. It's already done:

the styling should actually be font-weight: 500, not 600! my bad 🥲

the styling should actually be font-weight: 500, not 600! my bad 🥲

i have a PR in flight, will update it.. good thing is we have just one place to update now.


No option to select node template when creating RKE2 cluster pool

Setup

Rancher version: 2.6.4
Browser type & version: Edge 101.0.1210.39

Describe the bug
When creating or editing a cluster, their is no option to choose a node template when setting up pools.
Creating this issue per request from @rak-phillip in response to comment https://github.com/rancher/dashboard/issues/3553#issuecomment-1134837914
To Reproduce
Create a new cluster, configure pool.
Result
No option to select node template.
Expected Result
Able to select a node template that was previously created.
Screenshots

Additional context
We are deploying using vSphere if that makes a difference.
Context
With it being unable to use a template, that we can update at a later time we have ran into the scenario of...
We updated our VM template in vSphere, which caused the (3) that was suffixed at the end of the template name to be incremented to (4). Now we can't increase our node count because it's pointing to a non-existing template name. I came to the cluster config to edit it to the new template name, but it will not update at all. How do I update the template in the cluster config? We're not expecting it to redeploy nodes with the new template, just use the new template on new nodes.

I'm a vSphere noob, but I think there's cross-over with https://github.com/rancher/dashboard/issues/5981. We should evaluate both issues at the same time

Yes, that seems to be what we are after. Also please note the scenario described at the end of the issue above, of needing to update the cluster's pool's vSphere template after a cluster is created.

How do I update the template in the cluster config? We're not expecting it to redeploy nodes with the new template, just use the new template on new nodes.

Because machine templates are immutable in CAPI, https://cluster-api.sigs.k8s.io/tasks/updating-machine-templates.html, it is not possible to update the existing machine template. The only way to change the machine configuration is to create a new machine template.
I think in this case, the best solution would be to create a new node pool that refers to the incremented template in VSphere.

I think you are confusing a machine template with what actually uses the machine template, like a machine set. It states directly in the link you provided that you can change a machine set to use a different machine config. In my case I'd need to create a new machine config using the new vsphere template name, then edit the machineset with the new machine config name. This is the part that is missing in rancher.

I don't think we can change the MachineSets directly. As I understand it, MachineSets aren't meant to be edited by humans. They are analogous to ReplicaSets in that they are used to keep track of how many items in are in each group as an update is getting rolled out, except instead of Pods they are tracking machines.

I states directly in the link you provided earlier on how to edit the MachineSet to point to a new template. Is a pool not a MachineSet?

For a MachineDeployment or MachineSet, users would need to modify the spec.template.spec.infrastructureRef.name field. In all cases, the name field should be updated to point to the newly-modified infrastructure machine template.

Yes, a MachineDeployment and MachineSet are different resources in CAPI and the docs are contradicting themselves, because on that page they mention editing a MachineSet, but on another page they say you should only edit the MachineDeployment because the MachineSets are managed by Kubernetes. Next week I'll open a documentation issue in the CAPI docs repo to that effect.


Lock Ray on <2.8.0

There seem to be some issues with the later version: https://github.com/apache/iceberg-python/pull/287

OOPS. Seems there is a conflict.

Fixed the conflicts, thanks @HonahX


[FEATURE-4451][API]After the workflow editing page is submitted, the user chooses whether to go online or not. 0 means not to go online, 1 means online.

The front end has not been written, only the back end has been written. At present, there is a default value of 0, which will not go online after editing by default.

Codecov Report

Merging #4437 (e41c960) into dev (d446e33) will increase coverage by 0.24%.
The diff coverage is 75.75%.

@@             Coverage Diff              @@
##                dev    #4437      +/-   ##
============================================
+ Coverage     43.22%   43.46%   +0.24%
- Complexity     3184     3206      +22
============================================
  Files           471      471
  Lines         21732    21834     +102
  Branches       2626     2648      +22
============================================
+ Hits           9393     9490      +97
+ Misses        11442    11432      -10
- Partials        897      912      +15

Impacted Files
Coverage Δ
Complexity Δ

...er/api/controller/ProcessDefinitionController.java
72.11% <75.75%> (-4.18%)
20.00 <11.00> (ø)

...heduler/api/controller/TaskInstanceController.java
82.35% <0.00%> (-17.65%)
3.00% <0.00%> (ø%)

...inscheduler/service/zk/CuratorZookeeperClient.java
60.97% <0.00%> (-4.88%)
7.00% <0.00%> (-1.00%)

...e/dolphinscheduler/remote/NettyRemotingClient.java
50.00% <0.00%> (-2.78%)
9.00% <0.00%> (-2.00%)

...inscheduler/api/controller/ExecutorController.java
9.52% <0.00%> (-1.59%)
2.00% <0.00%> (ø%)

...uler/api/service/impl/DataAnalysisServiceImpl.java
98.91% <0.00%> (-1.09%)
30.00% <0.00%> (+1.00%)
:arrow_down:

.../dolphinscheduler/api/service/ExecutorService.java
34.46% <0.00%> (-0.30%)
20.00% <0.00%> (ø%)

...he/dolphinscheduler/server/utils/AlertManager.java
0.86% <0.00%> (-0.05%)
1.00% <0.00%> (ø%)

.../org/apache/dolphinscheduler/api/enums/Status.java
100.00% <0.00%> (ø)
5.00% <0.00%> (ø%)

.../org/apache/dolphinscheduler/common/Constants.java
85.00% <0.00%> (ø)
1.00% <0.00%> (ø%)

... and 14 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d446e33...e41c960. Read the comment docs.

Codecov Report

Merging #4437 (e41c960) into dev (d446e33) will increase coverage by 0.24%.
The diff coverage is 75.75%.

@@             Coverage Diff              @@
##                dev    #4437      +/-   ##
============================================
+ Coverage     43.22%   43.46%   +0.24%
- Complexity     3184     3206      +22
============================================
  Files           471      471
  Lines         21732    21834     +102
  Branches       2626     2648      +22
============================================
+ Hits           9393     9490      +97
+ Misses        11442    11432      -10
- Partials        897      912      +15

Impacted Files
Coverage Δ
Complexity Δ

...er/api/controller/ProcessDefinitionController.java
72.11% <75.75%> (-4.18%)
20.00 <11.00> (ø)

...heduler/api/controller/TaskInstanceController.java
82.35% <0.00%> (-17.65%)
3.00% <0.00%> (ø%)

...inscheduler/service/zk/CuratorZookeeperClient.java
60.97% <0.00%> (-4.88%)
7.00% <0.00%> (-1.00%)

...e/dolphinscheduler/remote/NettyRemotingClient.java
50.00% <0.00%> (-2.78%)
9.00% <0.00%> (-2.00%)

...inscheduler/api/controller/ExecutorController.java
9.52% <0.00%> (-1.59%)
2.00% <0.00%> (ø%)

...uler/api/service/impl/DataAnalysisServiceImpl.java
98.91% <0.00%> (-1.09%)
30.00% <0.00%> (+1.00%)
:arrow_down:

.../dolphinscheduler/api/service/ExecutorService.java
34.46% <0.00%> (-0.30%)
20.00% <0.00%> (ø%)

...he/dolphinscheduler/server/utils/AlertManager.java
0.86% <0.00%> (-0.05%)
1.00% <0.00%> (ø%)

.../org/apache/dolphinscheduler/api/enums/Status.java
100.00% <0.00%> (ø)
5.00% <0.00%> (ø%)

.../org/apache/dolphinscheduler/common/Constants.java
85.00% <0.00%> (ø)
1.00% <0.00%> (ø%)

... and 14 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d446e33...e41c960. Read the comment docs.

this close #4451

this close #4451


Allow parameters to be IO

fixes #609
Previously, we would only allow responses to be IOSchemas, but Johan's issue shows that this parameter should be an IOSchema as well.
This is the output for signalr:

Note: When regenerating, I saw that the media types output has changed, but looking at what is returned to us by m4, I see that the two options for the parameter input are of type "binary" and "SourcePath", which is consistent with what I'm outputting. Let me know if this change is incorrect
m4 output for the two options for input in the media types swagger:

/azp run autorest.python - ci


Fixes #779 added s2i link

@cmoulliard @rhoads-zach - Please review, Added link for S2I process for missions and related procedures.

Yes, thank you
On Nov 21, 2017, 12:59 PM -0500, LaVern Witherspoon<EMAIL_ADDRESS>wrote:

@lavernw1 commented on this pull request.
In docs/topics/templates/document-attributes.adoc:

@@ -173,3 +173,6 @@

// WildFly Swarm repository (mostly for the Contribution Guide)
:link-repo-wildfly-swarm: https://github.com/wildfly-swarm/wildfly-swarm/
+
+// Link S2I process (primarily for guides mission interaction sections)
+:link-s2i-process: https://docs.openshift.com/container-platform/3.4/architecture/core_concepts/builds_and_image_streams.html#source-build
@astrong1 @rhoads-zach Did you see the Updates done per your suggestions.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@cmoulliard did you get a chance to look at the changes.

@rhoads-zach used link to the S2I appendix in these launcher related  files for references to S2I. Can you review to ensure thats ok.

docs/topics/launcher-review-update-booster-manual.adoc
docs/topics/getting-started-launchpad-update-booster-manual.adoc

@rhoads-zach removed extra "}"

merged: 872498fece678d6be1292dee76421d9de326b30f


AL_API and ALC_API cause warnings when building statically with MSVC

mojoAL version : https://github.com/icculus/mojoAL/commit/5db917fd9439f03a36705b4be8673885d8cc9336
compiler : MSVC in VS 2019 16.11.18.
I am getting a bunch of messages like warning LNK4217: locally defined symbol alGetError and so on for thing in the API. The cause seems to be these lines below:
https://github.com/icculus/mojoAL/blob/5db917fd9439f03a36705b4be8673885d8cc9336/mojoal.c#L14-L17
Ideally when building statically, I would like to have empty defines instead.
#define AL_API
#define ALC_API

If there was some preprocessor definition (AL_DLL_EXPORTS or something) for when building mojoal.c as a dll, it could alternate between each possibility.
openal-soft handles this in CMake  instead - being a single c file, not sure we want this, but just as well being a single c file I imagine most people just add mojoAL directly in their projects.

(I actually also have other warnings too, but they are for different reasons)
mojoal.c(1200): warning C4244: '=': conversion from 'double' to 'float', possible loss of data
mojoal.c(1201): warning C4244: '=': conversion from 'double' to 'float', possible loss of data
mojoal.c(1202): warning C4244: '=': conversion from 'double' to 'float', possible loss of data
mojoal.c(1254): warning C4244: '=': conversion from 'double' to 'ALfloat', possible loss of data
mojoal.c(1276): warning C4244: '=': conversion from 'double' to 'ALfloat', possible loss of data
mojoal.c(1282): warning C4244: '=': conversion from 'double' to 'int', possible loss of data
mojoal.c(1294): warning C4244: '=': conversion from 'double' to 'ALfloat', possible loss of data
mojoal.c(1295): warning C4244: '=': conversion from 'double' to 'ALfloat', possible loss of data
mojoal.c(1303): warning C4244: '=': conversion from 'const float' to 'int', possible loss of data
mojoal.c(1331): warning C4244: '+=': conversion from 'double' to 'ALfloat', possible loss of data
mojoal.c(1335): warning C4244: '=': conversion from 'double' to 'ALfloat', possible loss of data
mojoal.c(1336): warning C4244: '=': conversion from 'double' to 'ALfloat', possible loss of data
mojoal.c(1348): warning C4244: '+=': conversion from 'double' to 'ALfloat', possible loss of data
mojoal.c(2935): warning C4028: formal parameter 1 different from declaration
mojoal.c(4260): warning C4244: '=': conversion from 'ALfloat' to 'int', possible loss of data
mojoal.c(4263): warning C4244: '=': conversion from 'ALfloat' to 'int', possible loss of data

Maybe we should #define AL_API only if it isn't already defined?

Wait, if you're using the headers included with mojoAL, you can just #define AL_LIBTYPE_STATIC before including, possibly on the compiler command line, and it'll do what you want; I'll fix mojoal.c to respect that, too.

Okay, latest in revision control should resolve this; build with AL_LIBTYPE_STATIC defined when compiling mojoal.c, and (I think) all the compiler warnings should be resolved.

Thank you so much! :)


ShortPixel image optimization

[x] Support for webp files

[x] Backup sync

[x] Improve sync

How to test:
Install WP-Stateless from here:

I did review the PR but I think we will have to move this issue to some of the next milestones because we have to wait for the approval from the ShortPixel team. Otherwise, the feature will not work.

How to test:
Install WP-Stateless from here: https://github.com/wpCloud/wp-stateless/tree/shortpixel
Insatall ShortPixel from here: https://github.com/wp-stateless/shortpixel-image-optimiser/tree/wp-stateless
Go to Settings >> ShortPixel, then enable Image backup from General tab and
enable WebP Images > Using the <PICTURE> tag syntax > Only via Wordpress hooks (like the_content, the_excerpt, etc) from Advanced tab.
Then create a Page/Post with a image and view on frontend. Check if the image used is WebP or not.
Review ShortPixel code before sending pull request to them:
I have added a bunch of new hooks to ShortPixel plugin.
wp-stateless/shortpixel-image-optimiser#1

First a HUGE thank you for getting this setup.
I've set a large busy website to CDN only to
"StatelessStore and serve media files with Google Cloud Storage only. Media files are not stored locally."
So with the updated version of the plugin;

will this be included with the next wp-stateless update?
will it now upload wepb images to GCS as well?
will there be support for serving wepb via .htaccess and,
how will I regenerated webp images as it's not stored on GCS so I have to somehow regenerate them?

Thank you in advance and again thank you for your hard work I really appreciate everything you are doing!

This update will be release after ShortPixel add our suggested hooks and do release. Hopefully they will add them in next release.
Yes, it will upload webp to GCS.
Not at the moment.
ShortPixel generates webp images when you reoptimize the image. So if you re-optimize your image webp image will be generated and WP Stateless will upload them to GCS.

Ok, so pull request has been merged and released in 4.14.0:

I've updated Shorpixel plugin to the latest version and used shortpixel branch of WP-Stateless in order to test the compatibility.
I've optimized 2 files and thumbnails have updated in the bucket as well:

1

2

The newly added images are also being optimized and pushed to the bucket.
@alimuzzaman can you confirm this is the complete test of the compatibility?

@antonkorotkov
Sorry I had some local changes forgot to pushed.
Please check in Stateless mode.
In Stateless mode:
The main purpose is when Shortpixel optimize image, we don't have to download the image to server. Now with shortpixel_image_urls filter we can make sure Shortpixel will use image directly from GCS.
We are converting GCS urls using shortpixel_image_urls() function from https://storage.googleapis.com/udx-ci-develop-alim/...
to https://udx-ci-develop-alim.storage.googleapis.com/
So that Shortpixel don't count all as  one domain (storage.googleapis.com).

Ok, I'll do one more test.

@alimuzzaman I need you to check this Missing Dependency

Looks like a bug in Shortpixel compatibility to me.

@alimuzzaman optimization works in Stateless mode with your latest changes as well. I think we are good to make a release if this after you fix the asset warning above.

@antonkorotkov Fixed.
Please check.

It is ok now. I think it is ready to be released.

@antonkorotkov Lets fix shortpixel_image_exists first.

Well, ShortPixel compatibility is not ready. Restore From Backup function does not work. Problem is that ShortPixel plugin developers did not add a shortpixel_image_exists filter to the specific place to handle backups. I think I'll need to create a new Pull Request to their plugin.

@alimuzzaman I see some changes to the SHortPixel plugin that were not pushed for the approval? I see there something related to backups. Can you explain what is that and if that is something that we need?

I'm talking about this changes https://github.com/short-pixel-optimizer/shortpixel-image-optimiser/compare/master...wp-stateless:wp-stateless

@antonkorotkov no it's not something we need.
It's just further improvement so that we don't make any unnecerry upload/download on GCS.

@antonkorotkov
Restore From Backup is working now.
You can test it with develop-alim branch.
As for shortpixel_image_exists function:
I have spent some time to find a better solution but wasn't able to find any. Just wrapped the function with short(10 minutes) transient cache.


cmd/compile: println(^uint(0)) fails to compile

What did you do?
https://play.golang.org/p/bIg5Wj5I4Q
In local builds
println(^uint(0))

Is a compile error
constant<PHONE_NUMBER>3709551615 overflows int64

In local tests and builds it prints -1
func TestOverflow(t *testing.T) {
	asd := ^uint(0)
	println(asd)
}

go test -test.run TestOverflow
-1

What did you expect to see?
4294967295
What did you see instead?
-1
System details
go version go1.9 linux/amd64
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/mmacdermaid/git/go"
GORACE=""
GOROOT="/home/mmacdermaid/goinstall/go"
GOTOOLDIR="/home/mmacdermaid/goinstall/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build297215887=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOROOT/bin/go version: go version go1.9 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.9
uname -sr: Linux 4.4.0-57-generic
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.2 LTS
Release:	16.04
Codename:	xenial
/lib/x86_64-linux-gnu/libc.so.6: GNU C Library (Ubuntu GLIBC 2.23-0ubuntu9) stable release version 2.23, by Roland McGrath et al.
gdb --version: GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1

I think the problem is specific to println(^uint(0)).  This fails:
package main

func main() {
	println(^uint(0))
}

Replacing println with fmt.Println works fine.

Use fmt.Println, the built-in println is a debugging feature which has
limited ability to print complex things.
On Fri, 15 Sep 2017, 02:45 Mike MacDermaid<EMAIL_ADDRESS>wrote:

What did you do?
https://play.golang.org/p/bIg5Wj5I4Q
In local builds
println(^uint(0))
Is a compile error
constant<PHONE_NUMBER>3709551615 overflows int64
In local tests and builds it prints -1
func TestOverflow(t *testing.T) {
asd := ^uint(0)
println(asd)
}
go test -test.run TestOverflow
-1
What did you expect to see?
4294967295
What did you see instead?
-1
System details
go version go1.9 linux/amd64
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/mmacdermaid/git/go"
GORACE=""
GOROOT="/home/mmacdermaid/goinstall/go"
GOTOOLDIR="/home/mmacdermaid/goinstall/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build297215887=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOROOT/bin/go version: go version go1.9 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.9
uname -sr: Linux 4.4.0-57-generic
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.2 LTS
Release:	16.04
Codename:	xenial
/lib/x86_64-linux-gnu/libc.so.6: GNU C Library (Ubuntu GLIBC 2.23-0ubuntu9) stable release version 2.23, by Roland McGrath et al.
gdb --version: GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/21887, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAcA65bqhY7tsnwy4njGzPxgLF4IGRRks5siVgrgaJpZM4PX31I
.

:+1: Good to know it's just println().  I can confirm using fmt.Println() over here correctly prints the right results.

I'm going to close this as there doesn't seem to be an issue. println isn't really part of the language spec, it's just a vestigial part of the bootstrapping process.
https://golang.org/ref/spec#Bootstrapping

Reopening this as there is a proper/code fix that @anfernee has up for review.


promenu: handle boolean menu entries, back functionality and scroll and use typescript

This PR:

Fixes promenu's display/overwriting of boolean menu items
Handle back functionality, both via .back and "< Back" items - an entry is displayed to go back and the setUI back widget is shown
Scroll support is also added

@Ronin0000 is this ok by you?

Don't merge - there's an issue with submenus

Don't merge - there's an issue with submenus

Solved, related to #3418

Yep, this is great. Thanks!

Thanks!


Note field is array of objects, not strings

The note field in each JSON object is an array of objects, like so:

  "UUID": "5db7ad80-c52a-012f-0a4c-3c075448cc4b",
  "databaseID": 3012441,
  "note": [
    {
      "type": "content",
      "text": "California shown as an island."
    },
    {
      "type": "content",
      "text": "Includes decorative cartouche showing native North Americans and ill. of animals in the body of the map."
    }
...

The current documentation incorrectly describes this field as an array of strings.

Thanks for catching that! We've updated the documentation.


Hover effect on logo [GSSOC'23]

Current Behavior
The current logo is very simple and static, we can give it a dynamic look by adding a hover effect making it more realistic and attractive.
Before -

After -

I want to work on this issue. Kindly assign me this under Gssoc'23
@HarshSharma0801

@riyaVerma1726 hello, I'm also a contributor in this project please contact the project admin

Oo really sorry for that.

Yes sure, go ahead @riyaVerma1726 and add this effect only when hovered

Sure,
Thankyou @akshathar-navada


Change computer name to AZUREADSSOACC

Fixed a typo where the computer account name was incorrectly stated to be AZUREADSSOACCT instead of AZUREADSSOACC.

@ghvanderweg : Thanks for your contribution! The author, @billmath, has been notified to review your proposed change.

#sign-off


Install dnsutils package in helios-solo

This includes dig which is useful for debugging dns issues.

@rohansingh

You'll want to bump the version in solo/base/version.txt.

Ah, ok. Bumped it to 0.3.

:+1:
After you merge it:

make push from the solo/base directory.
Bump the version in the FROM in solo/docker.


Added a rounds countdown timer to the sidebar

It shows the time remaining in the current round with a general
Countdown component, which AppAnonymous now uses for its countdown.
Fixes #122.

No conflicts from me!


Make local webserver port configurable. Resolves #40.

This PR contains the changes made by @ghenry22 to make the local webserver port configurable in https://github.com/ghenry22/cordova-plugin-ionic-webview and submitted as PR #41.
Since there seems to be reluctance to merge #41 due to the background mode changes, this PR isolates and includes only the configurable port changes to resolve issue #40.
All credit for the changes goes to @ghenry22.

Thanks! What are the keyWindow changes for?

@mlynch without the key window changes wkwebview still suspends when in the background


disable flycheck temporarily?

Sometimes I want to disable flycheck temporarily when I work on definitions that are hard for the elaborator. But when I un-check the "Enable on-the-fly-sytax-checking" in the FlyCheck menu, the flycheck button disappears completely. Could you change that such that the button is still there but flycheck deactivated?

@soonhokong
I believe the problem is flycheck (parsing the error messages).
If the machine has more than 1 core, then there is no reason to disable flycheck. We limit the amount of memory used by Lean. So, in principle, Lean should not affect the editor if it is running in the background.
Yesterday, I was performing some experiments, and noticed flycheck sometimes makes the system unresponsive. The problem can be reproduced by opening a file with many declarations (e.g., library/data/int/basic.lean). Then, introduce an error in a definition that is used by many other definitions (e.g., repr_mul). Now, many errors are generated, and it is hard even to edit the file. There is a delay after every keystroke. It seems flycheck blocks Emacs by trying to parse the error messages. This is really annoying.
@javra Is this similar to the problem you are having?
I use the following workarounds:
1- Add an exit after the definition I'm editing, OR
2- Reduce the maximum number of errors reported by flycheck. The default is 100, if I reduce to 10, then the system is usable again.
Anyway, I think we need to fix this.

@leodemoura, you're right. We had a similar problem when we first tried to use flycheck to show type information. We showed that when it has more than 200 - 300 messages, it started getting slower.

I see... even limiting to 100 is not enough sometimes.

Here is a discussion in the flycheck issue tracker:
https://github.com/flycheck/flycheck/issues/179
I tried (setq flycheck-highlighting-mode 'symbols), and it was still super slow.
I also tried (setq flycheck-highlighting-mode 'lines), and did not observe a significant improvement. I  still had a noticeable lag after each key stroke.
Now, I'm wondering if the problem is the regular expressions we use in lean-flycheck.el.
We use minimal-match there.

I have two cores, but flycheck often (always?) creats two lean processes that sometimes work at the same time.(One for the flychecking and for indexing?) The problem I have is more that the emacs processes slow down the entire computer.
I always put an exit below the definition I'm working on but often that's not enought becaus I often run into looping things (and right now I'm having at least two definitions that need 500000 unifier steps).

Jakob, I took a look in your files. You should try the cases tactic. cases F is much faster than using apply C.rec_on F. It also does the revert step (if needed). It also handles indexed families. The cases tactic is not perfect for HoTT mode (it still needs polishing), but it is already useful.
I rewrote dbl_functor_sigma_char (one of the definitions that were taking 500000 steps) using cases.
The new version can be processed using the default threshold. I also used the new nested begin-end blocks.
  definition dbl_functor_sigma_char (D E : Dbl_precat) :
    (Σ (catF : functor (cat D) (cat E))
       (twoF : Π ⦃a b c d : cat D⦄
         ⦃f : hom a b⦄ ⦃g : hom c d⦄ ⦃h : hom a c⦄ ⦃i : hom b d⦄,
         two_cell D f g h i → two_cell E (catF f) (catF g) (catF h) (catF i)),
       (respect_id₁_type D E catF twoF) ×
       (respect_comp₁_type D E catF twoF) ×
       (respect_id₂_type D E catF twoF) ×
       (respect_comp₂_type D E catF twoF)) ≃ (dbl_functor D E) :=
  begin
    fapply equiv.mk,
      begin
        intro S, fapply dbl_functor.mk,
        apply (S.1), exact (@S.2.1), exact (pr1 @S.2.2),
        exact (pr1 (pr2 @S.2.2)), exact (pr1 (pr2 (pr2 @S.2.2))),
        exact (pr2 (pr2 (pr2 @S.2.2)))
      end,
      begin
        fapply is_equiv.adjointify,
          {intro F, cases F,
           apply (sigma.mk catF (sigma.mk twoF
                   (respect_id₁ , (respect_comp₁, (respect_id₂, respect_comp₂)))))},
          {intro F, cases F, apply idp},
          {intro S,
           cases S   with (catF, S'),
           cases S'  with (twoF, S''),
           cases S'' with (respect_id₁, S'''),
           cases S''' with (respect_comp₁, S''''),
           cases S'''',
           apply idp}
      end
  end

Oh, thanks for the hint! I thought cases, destruct and apply (...rec_on x) would be the same in the case of products and sigmas.

For non-indexed families, here are the advantages.
1- apply does not "know" what a recursor is. That is, it treats it as any other function. In contrast,  cases "knows" how to synthesize the recursor implicit arguments more efficiently. It is customized for that.
2- cases F will automatically revert any hypothesis H that depends on F, apply the recursor, and then intros back all dependent hypothesis, and the constructor arguments.

Regarding the two processes in @javra's  comment, one process is used by flycheck. It starts a new process whenever the user modifies the file. This process uses the cache. Thus, if we put an exit command after the definition D we are working on, the time is roughly the time to process D.
The second process is a background process started by Emacs. We call it the "Lean server". This process is responsible for auto-completion and providing type information. For expensive files, I think it is more useful to disable the second process (auto-completion and type information).
@soonhokong What do you think?

We can have two lean-server processes (one with --hlean and another with --lean argument), if a user is editing both of standard and HoTT files together.

For expensive files, I think it is more useful to disable the second process (auto-completion and type information).

I think disabling eldoc-mode (automatically showing type information at point) should be enough. Once it's disabled, the lean-sever process is only activated by a user request -- either pressing C-c C-t for type information and tab for auto-completion.
I can create a key-binding for that, and also add it to the menu. @leodemoura, what do you think?

I can create a key-binding for that, and also add it to the menu. @leodemoura, what do you think?

I think it is a good idea.


A restart of the NDM daemon pod removes the user's applied labels and annotations.

What happened:
A restart of the NDM daemon pod removes the user's applied labels and annotations.
label
shovan@probot:~$ kubectl -n openebs get bd -l mylabel=test
NAME                                      NODENAME                                            SIZE          CLAIMSTATE   STATUS   AGE
sparse-c29aaae311cc075097c95780882ca6d4   gke-cstorpoolauto-test-default-pool-0ec02656-zxx6<PHONE_NUMBER>0   Unclaimed    Active   56m
sparse-e22a0cb50061282cfc9d6d8a29d223e2   gke-cstorpoolauto-test-default-pool-0ec02656-4jg2<PHONE_NUMBER>0   Unclaimed    Active   56m
shovan@probot:~$
shovan@probot:~$ kubectl -n openebs delete pod -l name=openebs-ndm
pod "openebs-ndm-2cg4h" deleted
pod "openebs-ndm-gxrxn" deleted
pod "openebs-ndm-q5p5q" deleted
shovan@probot:~$ kubectl -n openebs get bd -l mylabel=test
No resources found in openebs namespace.

annotation
shovan@probot:~$ kubectl -n openebs annotate bd sparse-c29aaae311cc075097c95780882ca6d4 myannotation=test
blockdevice.openebs.io/sparse-c29aaae311cc075097c95780882ca6d4 annotated

shovan@probot:~$ kubectl -n openebs get bd sparse-c29aaae311cc075097c95780882ca6d4 -o yaml

apiVersion: openebs.io/v1alpha1
kind: BlockDevice
metadata:
  annotations:
    myannotation: test
  creationTimestamp: "2020-03-17T11:25:27Z"
  generation: 9
  labels:
    kubernetes.io/hostname: gke-cstorpoolauto-test-default-pool-0ec02656-zxx6
    ndm.io/blockdevice-type: blockdevice
    ndm.io/managed: "true"
  name: sparse-c29aaae311cc075097c95780882ca6d4
  namespace: openebs
  resourceVersion: "39252"
  selfLink: /apis/openebs.io/v1alpha1/namespaces/openebs/blockdevices/sparse-c29aaae311cc075097c95780882ca6d4
  uid: d5f3c8aa-6713-4c20-9e0a-f6f030c62114
spec:
  capacity:
    logicalSectorSize: 0
    physicalSectorSize: 0
    storage:<PHONE_NUMBER>0
  details:
    compliance: ""
    deviceType: sparse
    firmwareRevision: ""
    model: ""
    serial: ""
    vendor: ""
  devlinks: []
  filesystem: {}
  nodeAttributes:
    nodeName: gke-cstorpoolauto-test-default-pool-0ec02656-zxx6
  partitioned: "No"
  path: /var/openebs/sparse/2-ndm-sparse.img
status:
  claimState: Unclaimed
  state: Active

shovan@probot:~$ kubectl -n openebs delete pod -l name=openebs-ndm
pod "openebs-ndm-9hrfg" deleted
pod "openebs-ndm-9xdmh" deleted
pod "openebs-ndm-lvzvt" deleted

shovan@probot:~$ kubectl -n openebs get bd sparse-c29aaae311cc075097c95780882ca6d4 -o
yaml

apiVersion: openebs.io/v1alpha1
kind: BlockDevice
metadata:
  creationTimestamp: "2020-03-17T11:25:27Z"
  generation: 11
  labels:
    kubernetes.io/hostname: gke-cstorpoolauto-test-default-pool-0ec02656-zxx6
    ndm.io/blockdevice-type: blockdevice
    ndm.io/managed: "true"
  name: sparse-c29aaae311cc075097c95780882ca6d4
  namespace: openebs
  resourceVersion: "39480"
  selfLink: /apis/openebs.io/v1alpha1/namespaces/openebs/blockdevices/sparse-c29aaae311cc075097c95780882ca6d4
  uid: d5f3c8aa-6713-4c20-9e0a-f6f030c62114
spec:
  capacity:
    logicalSectorSize: 0
    physicalSectorSize: 0
    storage:<PHONE_NUMBER>0
  details:
    compliance: ""
    deviceType: sparse
    firmwareRevision: ""
    model: ""
    serial: ""
    vendor: ""
  devlinks: []
  filesystem: {}
  nodeAttributes:
    nodeName: gke-cstorpoolauto-test-default-pool-0ec02656-zxx6
  partitioned: "No"
  path: /var/openebs/sparse/2-ndm-sparse.img
status:
  claimState: Unclaimed
  state: Active

What you expected to happen:
User's applied labels and annotations should present after restart
How to reproduce it (as minimally and precisely as possible):
Label or annotate any a block device delete ndm daemon pod

Fixed in #394 and #398