Use upcoming 'pkgBin' feature from nixpkgs to set entrypoints

Suggested by @zimbatm:
Nixery should use information about the primary binary of a derivation to set the entrypoint of a built image. This information is not currently easily queryable from Nix, but NixOS/nixpkgs#67392 is working towards that.
The main question on the Nixery side of things is which derivation should be picked for this.
Given an image like shell/nginx/nmap/stunnel we'd be faced with two services that could potentially be intended to serve as long-running processes. Which one would be appropriate?
My gut feeling is that the first non-meta package (i.e. nginx in this case) should be chosen, as people are likely to "pile on" stuff like debugging tools at the end of the image.

FWIW, I've been experimenting with this a little bit (but, since I don't know Nix very well, the way I did it was extremely naive: just use the name of the first package as the entrypoint; so in an image like foo/bar/baz the entrypoint is just foo). I found that it "works" but that it's actually not very helpful, because:

for servers, it's very rare that we can just run the server binary as-is without adding more options, or a config file;
for tools used from a shell (e.g. "docker run -ti nixery.dev/shell/stuff/morestuff") I found that it was easier to give a shell by default;
for tools used in CI pipelines or initContainers, I always need to provide a script, or extra arguents anyway.

So at the end of the day, I found that setting a smarter entrypoint (or cmd) wouldn't really help me much (that's why I settled on the simpler option of setting CMD to "bash" when the "shell" metapackage is used, because I found that one helpful in practice).
That's just an observation on my personal workflow (and seeing some students use Nixery images, too) though; so I'd love to see what others think!


Server.properties file rewritten on every startup

Hi guys, I'm not sure if this might be an actual issue but since I don't find anything on this specific topic I thought I might as well ask here and see if you know how this comes about:
I'm running two separate worlds in MSCS on ports 25565 (#1) and 25566 (#2). After a reboot of my Ubuntu-Server one of the worlds wouldn't start (I set up mscs start @reboot via cron). I turns out, the server.properties file of world #2 had been overwritten with a new one. So the level name, motd, servername and the port were all set to default. Alle the other files were untouched and - besides a new "world" folder the old world-folder was still there.
On further investigation I noticed, that the server.properties file hat a timestamp in it's headline that seems to change with every reboot of my machine. After the last reboot however the properties were not overwritten and everything works as it should. The file still had a new timestamp in the headline which tells me, that the file had indeed been touched, but this time at least not completely messed up.
My question: It rewriting the server.properties file on startup of mscs a (wanted) feature and how can I make sure that my settings won't be overwritten with default ones?
PS: In the mscs.defaults I set at least a non-default value for the "default world". So the newly generated "world" and the generic motd are not invoked by the default (although in my view the default file shouldn't overwrite world-specific settings anyhow).
Thanks for any reply and help on this topic guys!

I actually do use EssentialsX, but only on the world that didn't get messed up. So world #1 is running on Paper 1.16.5 with Essentials X and world #2 is running Vannila 1.15.2. And #2 was the one that got messed up and reset to port 25565 which let it collide with world #1 on startup.

Hi @RudiKleinert. MSCS only writes to the server.properties file in the createWorld function. This function is called when mscs create  (aka mscs new) or when mscs import (aka mscs copy and mscs cp) is used.  Make sure that your startup sequences is not using one of these options to mscs.

Hi @RudiKleinert. MSCS only writes to the server.properties file in the createWorld function. This function is called when mscs create (aka mscs new) or when mscs import (aka mscs copy and mscs cp) is used. Make sure that your startup sequence is not using one of these options to mscs.

Hi @sandain, thanks for your reply. I'm not calling the functions you mention in my cronjob. But I will further investigate to see if I can reproduce the problem. Maybe I just made some mistake while setting up and that led to the explained behaviour.

Any luck tracking this down @RudiKleinert? If you post the console.out file for the affected world, maybe I can help.

It looks like this issue is resolved. Closing.


Add plugin bundle to default config

insomnia-plugin-kong-bundle installed by default, and shouldn't show document action or config generator plugins for collections.
Note: I have not marked insomnia-plugin-kong-bundle as unlisted; meaning, it will still appear on the website. Should it be unlisted?
Additionally, should the previous, manually installed insomnia-plugin-kong-bundle, be deleted when migrating from Designer to Core?

Note: I have not marked insomnia-plugin-kong-bundle as unlisted; meaning, it will still appear on the website. Should it be unlisted?

Right now, the plugin hub doesn't respect these flags yet, so no need.
However, what I would like to do instead of unlisting them is to mark them as something like bundled so we can still show them on the website, perhaps in their own section, so we can still get SEO and visibility for them. Perhaps inspiration for others as well, demonstrating how core functionality is also plugin based.

However, what I would like to do instead of unlisting them is to mark them as something like bundled so we can still show them on the website, perhaps in their own section, so we can still get SEO and visibility for them. Perhaps inspiration for others as well, demonstrating how core functionality is also plugin based.

They already are :) https://github.com/Kong/insomnia/blob/eb4ae99f8428e99b8322e5c1b4125ddc14d316fb/plugins/insomnia-plugin-kong-bundle/package.json#L9

❗ blocked because I can't figure out why unrelated tests are failing

❗ This is a blocker.
Inso fails because insomnia-send-request attempts to load all plugins that are pre-installed in Insomnia. We've pre-installed insomnia-plugin-kong-bundle, and inso can't find the plugin.

Easy, we can fix that by installing insomnia-plugin-kong-bundle in the insomnia-inso package. But then it fails because window cannot be found.
I think we may need to extend the networking calls used by insomnia-send-request to override loading plugins, because inso doesn't work with plugins right now anyway.


pascal-case isn't declared in dependencies

It looks like pascal-case is used in this module, but not declared in the dependencies.
This is in theory not allowed when using npm (although npm allows it) and Yarn 3 (with PnP) throws the following error:
/project-directory/.pnp.cjs:23499
      Error.captureStackTrace(firstError);
            ^

Error: @oak-digital/types-4-strapi-2 tried to access pascal-case, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.

Required package: pascal-case
Required by: @oak-digital/types-4-strapi-2@npm:0.5.4 (via /project-directory/.yarn/cache/@oak-digital-types-4-strapi-2-npm-0.5.4-3c62e81210-f8c7673a72.zip/node_modules/@oak-digital/types-4-strapi-2/lib/program/)

Require stack:
- /project-directory/.yarn/cache/<EMAIL_ADDRESS>- /project-directory/.yarn/cache/<EMAIL_ADDRESS>- /project-directory/.yarn/cache/<EMAIL_ADDRESS>    at require$$0.Module._resolveFilename (/project-directory/.pnp.cjs:23499:13)
    at require$$0.Module._load (/project-directory/.pnp.cjs:23349:42)
    at Module.require (node:internal/modules/cjs/loader:1105:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at Object.<anonymous> (/project-directory/.yarn/cache/@oak-digital-types-4-strapi-2-npm-0.5.4-3c62e81210-f8c7673a72.zip/node_modules/@oak-digital/types-4-strapi-2/lib/program/InterfaceManager.js:70:21)
    at Module._compile (node:internal/modules/cjs/loader:1218:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1272:10)
    at require$$0.Module._extensions..js (/project-directory/.pnp.cjs:23543:33)
    at Module.load (node:internal/modules/cjs/loader:1081:32)
    at require$$0.Module._load (/project-directory/.pnp.cjs:23380:14)

Node.js v18.13.0

This should be easily fixable by adding pascal-case to the package dependencies.

Thanks for reporting this. I think that it is weird that it has worked fine this far. We do actually use change-case which contains the pascalCase function, so it might just be swapping the dependencies.
I have also thought about writing some tests to find all these small bugs, but I haven't had the time.

This should be fixed in the latest patch v0.5.5.
Please reopen this issue if you are still experiencing this issue


Add global commands for pip and pip3

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem?
DDEV 1.22 adds projects types for django4 and python as well as ships with pip and pip3 installed. On the other hand DDEV already provides for package managers in php and javascript global commands. it would be a reasonable reasonable to add global commands for the python based package manager as well.
Describe your solution
see https://github.com/ddev/ddev/pull/5162
Describe alternatives
No response
Additional context
No response

In

#5162

decided not to accept this improvement, but thanks as always for suggesting (and implementing) it. When we get some more momentum with the Python community it will be time to look at it again.


Better argument preparation for distributions in stats package.

This code improves the preparation of arguments by argsreduce as discussed in [#13589]. This had significant performance impact, most benchmarks are faster, some are slower and a few are dramatically (50 times) faster. This is probably needs discussion and further work.
Reference issue

Addresses 13589
What does this implement/fix?

This is primarily a change to argsreduce, so that scalars remain scalars instead of being expanded, flattened and masked as before.
Most distributions handle arguments in the new form by automatic broadcasting but few had to be modified to accept arguments in the new form.
Additional information
All tests in the stats testsuite pass.
benchmark-my_lazywhere.txt

I pushed some minor style cleanups, it looks good to go aside from those.

Looks like there's a Homebrew issue, it is building OpenBLAS and suitesparse from source. Ignoring - in it goes.

Git bisect shows that commit 2233802 is the cause of https://github.com/scipy/scipy/issues/13791.


Having trouble with while loop inside oandapy.streamer

Hi,
I am trying to use your ForexSystem.py code for trading. For my strategy I wanted to use ATR indicator, the ATR code is;
#Average True Range   def ATR(df, n):       i = 0       TR_l = [0]       while i < df.index[-1]:           TR = max(df.get_value(i + 1, 'high'), df.get_value(i, 'close')) - min(df.get_value(i + 1, 'low'), df.get_value(i, 'close'))           TR_l.append(TR)           i = i + 1       TR_s = pd.Series(TR_l)       ATR = pd.Series(TR_s.rolling(window=12,min_periods=12,center=False).mean(), name = 'ATR_' + str(n))       df = df.join(ATR)       return df
which i modified for your code as;
#Average True Range       def ATR(self,data):           i = 0          TR_l = [0]           while i < len(self.resampled_prices.index): #THIS IS WHERE I THINK THE PROBLEM IS BUT DON'T                                                                             #KNOW HOW TO SOLVE              TR = max(self.resampled_prices.get_value(i + 1, 'high'), self.resampled_prices.get_value(i, 'close')) - min(self.resampled_prices.get_value(i + 1, 'low'), self.resampled_prices.get_value(i, 'close'))               TR_l.append(TR)               i = i + 1           TR_s = pd.Series(TR_l)           ATR = pd.Series(TR_s.rolling(window=4,min_periods=4,center=False).mean(), name = 'ATR_' + str(4))           self.resampled_prices = self.resampled_prices.join(ATR)           return self.resampled_prices
By the way this resampled price is made using your self.prices as ;
  self.resampled_prices =  self.prices.resample('10s').ohlc().ffill()
Also, i am running this ATR function after having few ticks, All the code  is inside your "def parse_tick_data" function,
SHALL I SEND YOU MY VERSION OF YOUR CODE?
Thanks,
Mahbub khan
   `   `

Hi,
I put the code in my forked repo of yours, in chapter 08 codes, as ForexSystem 0.2, could you please have a look at it.
Thanks,
Mahbub

Please indent your code if you want somebody to read it.
def ATR(self,data):
    i = 0 TR_l = [0]
    while i < len(self.resampled_prices.index):
        #THIS IS WHERE I THINK THE PROBLEM IS BUT DON'T
        # KNOW HOW TO SOLVE
       TR = max(self.resampled_prices.get_value(i + 1, 'high')

Python relies on indentation to get your code working.

Managed to find your code and looked through it, seems to be syntactically correct. What was the problem or error message you got?

Many thanks for your reply, there were a lot of outputs, with last line "Keyerror: "High"
Also,
File "C:/Users/Mahbub/Documents/PythonTrading/ForexSystem 0.2.py", line 81, in ATR
TR = max(self.resampled_prices.get_value(i + 1, 'high'), self.resampled_prices.get_value(i, 'close')) - min(self.resampled_prices.get_value(i + 1, 'low'), self.resampled_prices.get_value(i, 'close')
above line were one of the outputs.
That's how I guessed some how the loop is not working, and df.get_value is not getting the high column values.
Could you please run it on your side, my credentials are there, i will change it later, plus it's practice account.
Thanks

I just tried df.loc instead of df.get_value for resampled prices and got this error : KeyError: 'the label [high] is not in the [index]'

Afraid I'm unable to afford the luxury of time to work on other stuffs now.
You can try using PyCharm's built-in debugger to perform step-by-step debugging.
The last line of your error is pretty intuitive - there is no column high as the index for self.resamepled_prices.
If I recall correctly, this Oanda API provides only bid and ask values, not high and low. You might want to consult Oanda's docs for that.


On runtime error, report exit code (like: SIGSEGV)

I tried it with Python. For me it's more important to see not the exit code but rather the STDERR/STDOUT results to catch the "index out of bounds" and plain typos.  Without it debugging script becomes impossible.

For showing stderr output, the following issue is related: https://github.com/dj3500/hightail/issues/29


Swarm mode: Election delay on startup with single manager

Using docker master.
Steps to reproduce the issue:

Start a single node Manager.
Restart it.

Describe the results you received:
It will wait for the whole ElectionTick delay to reelect itself and accept new requests. This is due to the node going down and assuming it is part of a multi-node cluster waiting for a message from a possible new leader.
Describe the results you expected:
The node restarts and elects itself instantly as it is the only member in the raft memberlist.
Solution:
Artificially advance the state machine for the number of steps to trigger an Election when we restart and the Manager is the only member of the raft.
/cc @icecrime @aaronlehmann

Fixed by docker/swarmkit#1125 awaiting next swarmkit vendoring to close.
/cc @tiborvass @thaJeztah

#23312 includes the fix. Closing.


Add ExHentai

Checklist:

[ ] Updated extVersionCode value in build.gradle for individual extensions
[ ] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[ ] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[ ] Added the isNsfw = true flag in build.gradle when appropriate
[ ] Have not changed source names
[ ] Have explicitly kept the id if a source's name or language were changed
[ ] Have tested the modifications by compiling and running the extension through Android Studio
[ ] Have removed web_hi_res_512.png when adding a new extension

login with webview dont always work

the code was took from eh-hentai extension i only add the searchable tag and the cookie support

maybe i will only add exhentai support to the eh-hentai extension and delete this new extension


Custom search providers not appearing as commands

After editing the default search providers in settings, I cannot use them. This is because the old fixed search engines are listed as commands in command pallette.
Running the fixed commands will result in error:
Command 'Web Search: Google' resulted in an error (command 'websearch.google' not found)

I see, do you feel like doing a fix PR?
If not I am taking care of this. Thanks for reporting!

I see, do you feel like doing a fix PR?
If not I am taking care of this. Thanks for reporting!

Sorry, unfortunately I cannot do this.

I'm having the same issue, has this been fixed yet?

Hello @bveldkamp I refactored a lot the code in master but I have not created a release, unfortunately it is not possible yet to have this feature as commands in vscode cannot be dynamically created by user configurations, but they must be hardcoded in the extension package. That is as much as I know, at least.
Even new version cannot fix this, unfortunately.

Oh, that's too bad.
Something that would help me a lot is if I could open a configured URL based on the current file extension. That way, no extra commands would need to be added. My goal is to open a page with context sensitive help, e.g. if I have a C# file open, it would open a specific MSDN page, if I have a Python file open, it would go to python.org and so on.


LICENSE

I suggested GPL2 or GPL3

I’m ready to contribute, requires license first please.

On Aug 19, 2018, at 6:19 PM, Konstantin Nosov<EMAIL_ADDRESS>wrote:
Never. MIT or BSD. One day. Later.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Expansion delay

Currently it is only possible to set the collapse delay.
Would've been nice to set some small delay for expand on hover as well, in order to prevent unintended motion when the pointer just happens to pass by briefly.
Example:
I send the mouse pointer to the top left corner of the screen in order to switch to the first tab. I overshoot, and now I have to do much longer travel to collapse the sidebar and reach the tab slowly.
Also a bug:
If the pointer leaves the area before expand animation finishes, the sidebar doesn't collapse.
Otherwise, awesome plugin. Checks both "why I haven't thought about this before" and "this should be available in the app itself" boxes.

Hmm, that's a pretty good idea! I had wanted to tackle accidental overshoots like that, and this is a pretty simple but effective way to deal with it 🙂↕
As for the bug: Turns out when I was testing 8f5daccb9c583a035b8ca22613766b6f88947dfe I left the old .js file in my test vault. Oops 😬
Should now be fixed in the new version ^^


Change clojure linter to clj-kondo

Clj-kondo is a much more full-featured and actively developed linter compared to Joker, and is set as the (recommended) default on Spacemacs and the VScode Calva plugin.

Makes sense to me. Thanks!


Initialize Jenkins client which comes from jenkins-zh/jenkins-cli

What this PR dose

[x] Initialize Jenkins client which comes from jenkins-zh/jenkins-cli
[x] Add support for GitHub action
[x]  Provide Makefile

Why we need it
If we separated Jenkins client from Jenkins cli, other projects outside would lightly introduce Jenkins client and interact with Jenkins easily.

hi @LinuxSuRen , the GitHub Action dose not work for this PR. Please have a check for action settings of jenkins-client repository.

For GitHub checks result, please check here.


Add option to always focus certain applications

I need this for Little Snitch, which cannot be focused with kwm active and thus cannot be controlled using keyboard shortcuts. Screenshot with Accessibility Inspector open that shows how Little Snitch is not focused despite it being the frontmost window and the cursor being on it:

kwmc config float Little Snitch does not help here.

Looke like #40

Tried this with both AXUnknown, AXWindow and AXStandardWindow - neither of them works.
What I really need is a way to force kwm to have Little Snitch Configuration stay at the top whenever it is active. Trying the same with Little Snitch doesn't work either.
kwmc config add-role AXUnknown Little Snitch Configuration
kwmc config float Little Snitch Configuration

right click the .app folder and click "show package contents".
Open the Info.plist file and locate the string "Bundle Name"

Make sure you pass the proper name. If the method aboves does not work ,there is nothing I can do about it either.

That's what I did, the value for "Bundle Name" is "Little Snitch Configuration".
I guess I'll leave the issue open for now?

Does it appear in the list returned by kwmc read windows ?

Nope.

Add this to window.cpp:69 and run a debug build from the terminal, on the space that has the Little Snitch window open. Then do ´kwmc read windows` again.
else
{
    DEBUG("Role Mismatch: " << KWMTiling.FocusLst[WindowIndex].Owner)
}

Monitored both stdout and stderr with tail -f, doesn't show up.
However, the window does get highlighted for a split second when I click on it.

Try comment out window.cpp:307, this should be the reason.

Yes, that fixed it.

Yes, that fixed it.

Alright, can you print the value of "Window->Layer"

1490 for "Little Snitch", 0 for everything else.

No idea what the "CGWindowLevelForKey(kCGPopUpMenuWindowLevelKey);" constant for this ID is, but adding 1490 to the layer values checked in the function "ShouldWindowGainFocus()" should do the trick.
I have no idea if this causes problems for other applications such as popclip, so it would be nice if you can test this change locally, and report back on how it works out.

Addind Window->Layer == 1490 to the checked Layer IDs did the trick for me.
Do you know if there is a list of all CGWindowLevelKey constants?

I have no idea if this causes problems for other applications such as popclip, so it would be nice if you can test this change locally, and report back on how it works out.

Me neither, since I don't own any other applications that behave like this. Can someone that owns PopClip or any similar application confirm the behaviour did not change?

I have popclip. What should I do to test it?

Seems to work fine with PopClip. I'll keep monitoring but I think this is solved for now.

I'm having the same issue with the Fantastical 2 menu bar window. It's a normal AXStandardWindow, but kwm closes it whenever the cursor moved over it.

Have you tried kwmc config float Fantastical 2? Basically I'd try all the things I went through above, and if that does not work, try to find the layer ID of the window.

If a window does not get tiled, and does not gain focus, the problem is related to #40
If a window does get tiled, but can not get focused, it's related to the ShouldWindowGainFocus() function and you need to identify the layer of the window.

kwmc config float Fantastical 2 worked for me. However fantastical comes with a menu bar version that is always docked. I want kwm to only ignore this window (let it float) but when I open the full fantastical, it should tile it like all the other applications. Is this possible?

Also @dominiklohmann, what were your final settings to deal with little snitch? I am having the same problems you described with kwm 3

I just made it float in my kwmrc, that works for me.

So kwmc rule owner="Fantastical 2" properties={float="true"} works for the Fantastical full calendar window, but not for the menu bar pop-up. When I pop that up KWM freaks out and struggles to figure out how to resize it into my panes.
Any known good rules for that pop-up?


Should /page/ work just like /page ?

I am using Google Search Console to inspect my website. When adding a website it automatically adds a "/" to the end of the url, therefore www.website.com/page becomes www.website.com/page/
In the case of next page called 'page' this would not work. There are 2 workarounds

create /page/index.js on the filesystem
use a custom server to solve this "/" thing

Regarding 2 this is what i have done
req.url = req.url.replace(/\/$/, "")
if (req.url == "") { req.url = "/" }
handle(req, res)

I wonder wether it makese sense to fix this in next.js itself making it more generic.

For me this makes sense.
Personally, I think having this workflow would make sense.

page.js exists -> /page & /page/ works and goes to same place
page/index.js exist, page.js does not -> /page would 404, /page/ would resolve at index.js
page.js exists, as does page/index.js -> /page would go to page.js, /page/ would go to page/index.js

kind of related #619

I mostly agree with your reasoning @krhome83 but your statement in point 2 (/page would 404) is not logically consistent

In point 1) you suggest that a trailing slash in the URL (/page/), which typically indicates a directory, should resolve when the underlying representation is a file (page.js)
In point 2) you suggest the opposite. That /page, which typically indicates a file_, should 404 when the underlying representation is a folder.

Let me know if I'm off base, but otherwise, I think I'd like to add a "smart default" for this scenario (since we also have a custom server override for https://zeit.co), provided that we can turn it off in config (smartSlashes: false ?)

Also, I wonder if this should warn or be an error, since it's kind of not obvious

page.js exists, as does page/index.js -> /page would go to page.js, /page/ would go to page/index.js

IMHO in that case we should probably error unless you turn off smartSlashes, and most people would probably use ./pages/index for what they otherwise wanted to handle in ./page

I think the best option is to do a 301 redirect to /page/ to /page

301 would mean permanent, so maybe not a good idea

Yep 301 I mean it.
Do we need /page/ to serve in some different way in the future?
I guess we don't.

Agree with the 301 redirect. Nice and simple.
You want to use 301 instead of 302 because of SEO. Makes sure that google does not see two links as equivalent.
https://moz.com/learn/seo/redirection
Need to maintain that link juice!

Many people use trailing slash and many dont, however its better to only keep one version of it as per SEO otherwise it will create serious issues as per google.
We maintain a trailing slash and I am not sure how I can do it in next js.
Any ideas?

@harshmaur you can create a custom server to handle urls with a trailing slash or you can create pages/my-page/index.js, that way your URL (with the default router) will be /my-page/

@sergiodxa Thanks a lot, I was thinking of using server.js to create custom routes for all of my pages instead of using the default router. But I am not sure how that would work on the client side. I need to check.

@harshmaur check the custom server example specially how to use next/link

I believe I'm currently running into something like this right now.
Using a next/link instance, the rendered anchor element to /foo, and the static element points to /foo, but the prefetcher is taking me to /foo/, which my analytics team says is a no-go. My server is configured to serve up the /foo page perfectly.  (I'm using the next export feature as well).
I believe this is the relevant line in _rewriteUrlForNextExport() https://github.com/zeit/next.js/blob/cc9b1d6ce071bc40b52326f7bb01ecb8ff0657be/lib/router/index.js#L101
@rauchg would that be the target of your proposed smartSlashes flag?

SEO-wise 301 redirect is definitely preferred, but should trailing slash in the end be stripped or instead enforced is a question.
Note, that besides already mentioned differences above, those paths will work differently with relative urls:
/foo/ with href=`test` will be `/foo/test`
/foo with href=`test` will be `/test`

That's because for browsers, no matter what you think and how servers resolves resources, any url with trailing slash is a directory, while without one — a document. Thus, resolution for relative resources will be different. This means that by enforcing certain behavior (trailing slash or lack of one) you effectively removing a way to treat relative urls in different ways.
This shouldn't be a real issue, since, as far as I remember, in react-router relative paths are not even supported. But still worth mentioning.
Besides, unfortunately, SEO-wise 301 redirect is quite recommended thing for ending slashes. Or, otherwise, at least, canonical urls have to be specified.

I have been looking at this issue too. One thing worth to mention is that when exporting a page as an html endpoint such as the following causes an extra backslash:
{
  exportPathMap: () => ({
          "/about.html": { page: "/about" }
  })
}

This makes simple things like an anchor not to work properly since
http://localhost:8080/about.html#contact
is not the same as
http://localhost:8080/about.html/#contact

@arunoda @sergiodxa would you guys consider a PR for avoiding the extra backslash in _rewriteUrlForNextExport if the path ends with .html?

I have the same issue. I'm applying "with-apollo-and-redux" official example. https://github.com/zeit/next.js/tree/master/examples/with-apollo-and-redux
I created a pages/test. If i browse localhost:3000/test all it's okey. But if i browse localhost:3000/test/
GET http://localhost:3000/test/ 404 (Not Found)
client.js?ecc360b:67 [HMR] connected
warning.js?1713c82:35 Warning: Failed prop type: The prop `serverState` is marked as required in `WithData(Test)`, but its value is `undefined`.
    in WithData(Test) (created by Container)
    in Container (created by App)
    in div (created by App)
    in App

Maybe a temp fix.
server.js
const { createServer } = require('http')
const { parse } = require('url')
const next = require('next')

const port = parseInt(process.env.PORT, 10) || 3000
const dev = process.env.NODE_ENV !== 'production'
const app = next({ dev })
const handle = app.getRequestHandler()

app.prepare()
.then(() => {
  createServer((req, res) => {
    const parsedUrl = parse(req.url, true)
    const { pathname, query } = parsedUrl

    if (pathname.length > 1 && pathname.slice(-1) === '/') {
      app.render(req, res, pathname.slice(0, -1), query)
    }
    else {
      handle(req, res, parsedUrl)
    }

  })
  .listen(port, (err) => {
    if (err) throw err
    console.log(`> Ready on http://localhost:${port}`)
  })
})

package.json
...
"scripts": {
    "dev": "node server.js",
    ...
  },
....

Now this works good except for an error in the first render.
process-update.js?0be4961:122 [HMR] Update check failed: Error: Manifest request to /_next/webpack/53918e2236aadcc582cd.hot-update.json timed out.
    at XMLHttpRequest.request.onreadystatechange (http://localhost:3000/_next/1504017609143/manifest.js:68:22)

@hmontes But this won't be a fix for static exports.

I would love an internal fix for this that works with next-routes.

Fixed in next 5 / canary

url with a trailing slash results in a 404 error using<EMAIL_ADDRESS> was it supposed to be fixed in this version?

@timneutkens Should this be reopened?

Please see https://github.com/zeit/next.js/issues/3876#issuecomment-384709274, where I've shared a minimal example where trailing slashes don't seem to be working.

For reference:
https://zeit.co/blog/new-static-deployments

Isn't that just for static / next export though?

I filed a new issue with minimal reproducible repository in #5214

What is the status on this issue? It's been open for quite some time. I've just noticed that /page/ will still result in a 404. I'm using v7.0.1.

This is a disaster! Its hurting big time for SEO. page shows up in google search as '/contact/' and returns 404. Whats the fix??

ping @timneutkens it seems many people are upvoting to reopen. What do you think?

@rap2hpoutre What is the status of this issue?

@dryleaf  Still no answer. Maybe we should open a new issue.

@rap2hpoutre it is already opened #5214

Seams fixed.
The page is accessible with or without trailing slash. Both returning HTTP 200

Seams fixed.
The page is accessible with or without trailing slash. Both returning HTTP 200.
I am using Next.js v9.3.0

I am using Next.js v9.3.0 and not works

@javiercno see #5214

Can we reopen this?
I still can not match route with trailing slash.
Using 9.3.1 with custom server.
@timneutkens is there a hope this could be fixed any time soon?

@untitledlt see #5214

Seams fixed.
The page is accessible with or without trailing slash. Both returning HTTP 200.
I am using Next.js v9.3.0

I am using Next.js v9.3.0 and not works.can we reopen this bug?

@iamstarkov i saw your issue. There's even my comment 3 days ago.

As said this is already open in #5214


How to get the current online user?

How to get the current online user?

Please check: https://github.com/emqtt/emqttd/wiki/Presence.
Could subscribe the $SYS topics to trace clients.

need wait 0.9.0? I download 0.8.2, it return "Not found."

@roytan883, HTTP API will be supported in 0.9.0, and you could subscribe the $SYS topics to record all presence messages.

@kansifang, @roytan883, this feature has been released in 0.10.0. Pls check issue #230.


[8.x] Allow serializing custom casts when converting a model to an array

This PR allows serializing custom value objects when a model is converted to an array even if the value object does not implement the Arrayable interface. There are no breaking change, new functionality is covered with tests.
Reasoning
Consider a custom caster that casts the value to a value object, say a BigDecimal instance. When calling $model->toArray(), the value is not serialized to a primitive type like a string - it remains a BigDecimal object instance:
$model->toArray(); // ["price" => Brick\Math\BigDecimal {#2254}]

This is inconsistent with dates, which are cast to Carbon instances, but serialized when converting the model to an array:
$model->toArray(); // ["created_at" => "2020-10-05T07:49:06.000000Z"]

A comment suggests that the value object should implement the Arrayable interface to serialize the value. However, there are cases where this may not be possible,  feasible or would not make sense for the class itself.

If the value object is an instance of a 3rd party class that is declared final.
Since final classes cannot be extended, the only way would be to use composition to create a custom wrapper around the final class. This might work fine for simpler classes, but for something like BigDecimal, the maintenance overhead and code duplication would make it non-feasible (some 30+ methods), especially for smaller projects and teams.
This issue was brought up in laravel/deas as well: https://github.com/laravel/ideas/issues/2152
Creating a toArray() method for a value object that represents basically a scalar value makes little sense. What would be the expected return value of (new Decimal(123.45))->toArray()?

Furthermore, dates already have special handling serializeDate in core (see below) - why not allow custom serialization for custom casts?
https://github.com/laravel/framework/blob/576dd3d3cfbd4ef5239eb277c4d6bd315d7503bd/src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php#L226-L241
What's the use case? Why do we need the values to be serialized in the array at all?

Consistency with how dates are handled
Being able to produce a raw array of primitive model attributes with factories: Product::factory()->make(['price' => 12.345]);
 // ['price' => '12.345' ] instead of ["price" => Brick\Math\BigDecimal {#2254}]

Why not simply use Jsonable / JsonSerializable like suggested in https://github.com/laravel/ideas/issues/2152 ?
This would probably work fine for most cases - but custom serialization adds more flexibility. If dates already allow custom serialization/formats why not make it possible for custom casts as well?
Why not cast the model to JSON and the decode it back to an array?
I thought about it and while it's possible to do a little encoding dance:
json_decode($model->toJson()); // ['price' => '123.45']

... it's far from elegant, adds extra overhead (including mental) and just feels ... meh.
Conclusion
I think custom casts is a really powerful feature, especially if it's possible to ease the adoption when casting to 3rd party library classes.
This is my first PR to Laravel, so please go easy on me :) I've tried to follow the core naming and code structure conventions, however feel free to make edits or suggestions there.
If you think this contribution would be worthwhile but needs a different implementation, just let me know. I'm open to all ideas and suggestions.

🙌

Thanks @ragulka for this PR :)


Avoid overwriting settings by storing them separately on the configuration context

I've gone ahead and changed the way ConfigurationContext stores its cache, manifest, updater and versioner so it doesn't have to overwrite settings variables, which can cause a lot of confusion when debugging ("Why is my boolean variable suddenly an instance of some class I've never header of?").
I had to move the support for absolute paths in manifests (I think?) from scripts.py to the ConfigurationContext, which I think is the more correct behaviour, but I don't completely understand what that code does, so it'd be good if you could double-check it.
I need this to be able to update the settings handling in django-assets, I hope this doesn't affect any of the other framework integrations.
To make this run on my travis I also had to completely take apart the travis configuration. A lot of requirements seemed to be not necessary anymore to make the tests pass, so I've removed them, it's quite possible though that they're needed for local development that I didn't touch. Let me know if that's the case and I'll try and restore them.
Some of them caused trouble, libsass for example needs to be compiled (which travis doesn't like on the new docker containers).

I'm only now seeing the appveyor thing and I'm not sure what that is, let me know if you want me to look into it please!

Thanks, this looks really good. Fixing this particular issue with the settings is something I wanted to do for a long time.
I've sort of given up on on making the Travis builds work, because I've run repeatedly into issues that seemed to be related to environment changes, and trying to fix them via guessing what adjustments to make to travis.yml is a huge pain. It seems you fixed them, which is amazing. AppVeyor I used at one time to test on Windows.
About the code code you moved from the CLI module to the Environment - here is what's going on:

The API of FileManifest is this: If the string is "file:/srv/foo", write to /srv/foo, but if it is "file:foo", write to ${envdir}/foo.

The API of the --manifest option in the CLI was supposed to support an extended format. --manifest foo is supposed to write to $(cwd)/foo - i.e. it is not necessary to provide a format prefix like "file" or "json".

Before, settings "manifest" to "foo" without any prefix was an error. With your change, the manifest option supports the same behaviour as was the case on the command line. Which is not a big problem, but I think I don't like the change.

I have no problem forcing the developer to be explicit about the manifest they want.
We might want to change the default manifest written by the CLI to say "json". Changing the CLI behaviour is one thing, changing the behaviour of a core builtin class is quite different.
The thinking behind these strings is such that the path is the optional part. That is can say the manifest should be "file", and only if I want to change the default file (.webassets-manifest) do I write file:foo.

You say this change what necessary, but why?

I'm cool with leaving the core API as it is and moving that special format behaviour back to the CLI, I wasn't sure how to do it nicely though - before my change the manifest was instantiated in the CLI, but now it's just the settings value that get passed the along, so the value error only occurs when actually accessing the manifest.
Should I just remove the error handling code from the environment and make the CLI default to json then?

My suggestion would be that the code in script.py can remain as is, that is, get_manifest is used to validate the value provided by the user, and the manifest instance is then assigned to environment.manifest. That is, the property does not receive a string value in this case, which should be a valid use case.
Admittedly I had issues in the past with a custom settings backend that only support string values, but that strikes me as a separate problem; env.manifest = some_instance seems like it should be supported.

I can try and come up with a way of allowing to pass an instance of the manifest to the environment, but it is a bit awkward: passing in an instance would bypass the settings without changing them, resulting in a mismatch between setting and instance, making confusing-to-debug problems possible.
If the setters are instead treated as interfaces to the settings variables then the settings are the single source of truth and everything derives from them.
Side note: I keep concentrating on the manifest, but I'm guessing any behaviour will need to be mirrored for the cache, updater and versioner, to keep the interfaces symmetric.

Maybe I'm not thinking this through completely, but in my mind:
env.manifest = instanceOfAManifest()

would write this instance to the settings backend. The manifest property getter would realize that the settings backend already stores an instance, rather than a string, and wouldn't need to transform it. In fact, my suspicion is that the get_manifest (or get_cache etc helpers) already pass through an instance, so no further change would be required.
We would still accomplish the goal of not replacing stuff in the settings object without the users knowledge. It would only happen if the user purposefully wants to us an instance.
Whether we should use this ability to assign an instance the user-facing parts of webassets itself (like the script interface) is a different question - the problem I ran into a while ago was that I wanted to use a string-only settings backend. But it might also be a question for another time.
For now, the current behaviour could be maintained as-is, and there is a single instance in the CLI interface where webassets wants to use a manifest instance.


Retain backward compatibility

The full config is not necessary for the CLITool class.
This could potentially break any tool previously created using more than one ctor argument.
I suggest to remove this new initialization parameter.
One can still create multiple connections with more subsections having their own config passed using the create_workers method.

@pcmarmotte thanks for sending this over. Did you hit this as a bug in a PyPI or DEB package per chance? I'd hoped not to ship any packages with API breaking changes, especially this new 'multi-connect' behavior.

No I was experimenting with the github version.


got http error 500

It's works when yarn tauri dev , after build and install , run app got http error 500

my fault, I was set wrong distDir


Implement functions with multiple return values.

Functions in Move use a second-class tuple-like expression to bind, return, and destructure multiple values.
On exit from a function, we generate LLVM IR to wrap them up into a struct, which is returned as a single IR value. Similarly, when a callee that returns such a value is used in an expression, we generate IR to extract each actual value from the struct.
Also deduplicated load_call and load_call_store, as the former is just and instance the latter with no return values passed.
Added a move-ir-test and a runtime rbpf test to cover above.

Awesome.


Helm Chart Wishlist

Tell us about your request
I'd like Karpenter to have an idiomatic Helm chart with all of the components in the correct place and the standard integration points available.
I'd also like to see the chart published to aws/eks-charts.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I'd like to install Karpenter but the current Helm chart doesn't have the right configuration exposed and the CRD is directly in the chart.
Are you currently working around this issue?
n/a
Additional context
I'd be more than happy to open a PR to update the chart.
Attachments
n/a

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Hey Steve,
We're definitely interested in expanding our helm chart's capabilities. So far, we've expanded functionality on an as needed basis. I'm not sure what you mean by

components in the correct place and the standard integration points available.

Is there any thing you had in mind? Contributions are absolutely welcome.
I'm not sure about the move to aws/eks-charts. Not all AWS charts live there, and it's becoming a bit of a monolith to maintain. Serving the karpenter chart from here helps keep everything nicely in sync with our release process. I'm open minded to proposals for alternatives.

@ellistarn the chart doesn't follow idiomatic Helm patterns, but the big issue is having a CRD inside the chart. CRDs should be inside the special ./crds folder so they can (and should) be ignored via the helm upgrade --install --skip-crds.
Regarding the aws/eks-charts repo, it's a good discovery point. If it's becoming a monolith to maintain that's a problem with the process not something inherent to a central repo; I like the current release push model for things like the NTH chart but the actual chart release could be made independent to a repo tag.

Are you able to swing by our working group to discuss eks-charts?
It should be straightforward to point our CRD codegen to ./charts/karpenter/crds

@ellistarn I'll try and join next week.

This is now in. Please reopen (or a new issue) if there are more features you'd like added to the chart,


Preprocessing of the MulRan Dataset

Hello! I apologize for bothering you again! We've encountered an issue in our recent research project on global registration based on the MulRan map. We suspect the problem lies in directly using the raw bin data without applying any distortion corrections or similar preprocessing. I would like to know if you performed any preprocessing on the MulRan dataset during your research? Apart from semantic labeling, that was our previous question (haha). I look forward to your response!

Hello, no we did not.

Thank ！

Welcome, and it would be wonderful if you give a star to our repo :)


Not lock to the resolved revision when I use git with branch

When I use git dependency:
dependencies = [
  "awesomemodule @ git+https://github.com/org/repo@main",
]

rye outputs requirements.lock which describes branch name but not resolved revision:
awesomemodule @ git+https://github.com/org/repo@main

For reproducible build, I think that the resolved revision should be written in a lock file and, for example, Poetry does.

You can actually use -rev to specify the git revision.

Oh, I understand, that's really what should be done. But I suspect pip-tools used by rye will become a limitation, need to verify that.

Currently "rye sync --no-lock" also seems to pull and reinstall any git dependencies, but with this feature, that could be avoided if they are up to date, I think.


Automator: update proxy@master in istio/istio@master

Generated by Automator - 2024-11-18T14:47:09+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
b66674c620ae8ff89b6451cc24421bb5ac77a0da
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/retest


fatal: unable to deflate new object

I am getting following strage error when running blueprint for first time in Ubuntu. Any thoughts?
[root@server:~]# blueprint create my-first-blueprint
# [blueprint] using cached blueprintignore(5) rules
# [blueprint] searching for Python packages
# [blueprint] searching for PEAR/PECL packages
# [blueprint] searching for npm packages
# [blueprint] searching for Yum packages
# [blueprint] searching for software built from source
# [blueprint] searching for APT packages
# [blueprint] searching for configuration files
# [blueprint] searching for Ruby gems
# [blueprint] searching for service dependencies
fatal: unable to deflate new object f49ced87bacbe1d5c65390f0b4a6b3bbe734bf3a (-2)
Traceback (most recent call last):
  File "/usr/local/bin/blueprint-create", line 56, in <module>
    b = blueprint.cli.create(options, args)
  File "/usr/local/lib/python2.6/dist-packages/blueprint/cli.py", line 31, in create
    b.commit(options.message or '')
  File "/usr/local/lib/python2.6/dist-packages/blueprint/__init__.py", line 373, in commit
    git.git('update-index', '--add', os.path.abspath(filename))
  File "/usr/local/lib/python2.6/dist-packages/blueprint/git.py", line 83, in git
    raise GitError(p.returncode)
blueprint.git.GitError: 128

This is an error within Git that we're not able to recover from.  Is there a temporary directory like /tmp/blueprint-XXXXXX that you can inspect.  If it's there, you should be able to find a tarball in that directory.  Is it corrupted or otherwise unique?


fix: Additional exception handling for google life sciences executor

Basically mirrors existing exception handling in _retry_request to retry another request to google rather than crashing out with an exception.
It deals with this issue: https://github.com/snakemake/snakemake/issues/983
Description
Basically mirrors existing exception handling in _retry_request to retry another request to google rather than crashing out with an exception.
QC
You can use this repo to test for SSL errors before and after: https://github.com/mw55309/crash_gcp
No changes to documentation are needed

Thanks a lot!


ComplexWarning in VJP when using complex matrix multiplication

Description
Consider a function $f(a) = a b$ with $b$ some complex parameter and $a$ real. I want to compute the vector-Jacobian product $t^* \partial f(a)$. When $a b$ represents matrix multiplication, a warning is raised about an imaginary part being discarded.
For $a$, $b$ scalar it works as expected and without warning (imported jax, jax.numpy as jnp, and warnings):
a = jnp.array(1.0)
b = jnp.array(1.0j)
t = jnp.array(1.0j)

with warnings.catch_warnings():
  warnings.simplefilter("error", jnp.ComplexWarning)

  _, vjp_fn = jax.vjp(lambda x: x * b, a)
  vjp_fn(t)

However, if we promote $a$ and $b$ to matrices, this raises a ComplexWarning:
a = jnp.array([[1.0]])
b = jnp.array([[1.0j]])
t = jnp.array([[1.0j]])

with warnings.catch_warnings():
  warnings.simplefilter("error", jnp.ComplexWarning)

  _, vjp_fn = jax.vjp(lambda x: x @ b, a)
  vjp_fn(t)

ComplexWarning: Casting complex values to real discards the imaginary part

I would not expect a complex warning in the latter case. Although the output is the same in both cases (up to shapes), the warning suggests something could go wrong. Unless I'm missing something, the two behaviors are at least inconsistent.
The warning is not raised when $a$ is a matrix but $b$ is not (matrix-scalar multiplication), but it also occurs when using einsum.
System info (python version, jaxlib version, accelerator, etc.)
Tested on CPU:
jax:    0.4.23
jaxlib: 0.4.23
numpy:  1.26.3
python: 3.9.9 (v3.9.9:ccb0e6a345, Nov 15 2021, 13:06:05)  [Clang 13.0.0 (clang-13<IP_ADDRESS>)]
jax.devices (1 total, 1 local): [CpuDevice(id=0)]
process_count: 1

as well as on Colab (jax 0.4.26 both on CPU and GPU).

Thanks for the clear report! I'll take a look, though my initial guess is that this is a spurious warning we should suppress.

Yes, that would be a good resolution. I'm also unaware of anything going wrong. But the warning made me waste some time searching for what I might be doing wrong, so I thought fixing this might be useful.


Updating a cover results in all entities becoming unavailable

System Health details
System Information

version
core-2024.3.0

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.12.2

os_name
Linux

os_version
6.6.20-haos

arch
x86_64

timezone
America/New_York

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
4999

Installed Version
1.34.0

Stage
running

Available Repositories
1411

Downloaded Repositories
68

HACS Data
ok

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 12.1

update_channel
beta

supervisor_version
supervisor-2024.03.0

agent_version
1.6.0

docker_version
24.0.7

disk_total
468.7 GB

disk_used
108.8 GB

healthy
true

supported
failed to load: Unsupported

board
generic-x86-64

supervisor_api
ok

version_api
ok

installed_addons
Z-Wave JS UI (3.4.1), MariaDB (2.6.1), Mosquitto broker (6.4.0), Nginx Proxy Manager (1.0.1), Overseerr (1.33.2), Portainer (2.19.4-3), Home Assistant Google Drive Backup (0.112.1), MQTT Explorer (browser-1.0.1), Radarr (<IP_ADDRESS>12), Sonarr (<IP_ADDRESS>2), Network UPS Tools (0.13.0), ESPHome (2024.2.2), Prowlarr NAS (nightly-<IP_ADDRESS>18-ls127), Zigbee2MQTT (1.36.0-1), Matter Server (5.4.1), Silicon Labs Multiprotocol (2.4.4), Scrypted (18-jammy-full.s6-v0.93.0), AdGuard Home (5.0.4), Mylar3 (0.7.8), Readarr (<IP_ADDRESS>2), Calibre (7.6.0), Studio Code Server (5.15.0), InfluxDB (5.0.0), Grafana (9.2.0), qBittorrent (4.6.3-4), rtlamr2mqtt (2.3.4), Piper (1.5.0), WeatherFlow to MQTT (3.2.2)

Husqvarna Automower

can_reach_server
ok

Dashboards

dashboards
5

resources
37

views
31

mode
storage

Recorder

oldest_recorder_run
February 13, 2024 at 10:41 PM

current_recorder_run
March 13, 2024 at 10:56 AM

estimated_db_size
4616.44 MiB

database_engine
mysql

database_version
10.6.12

Checklist

[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
After changing some properties during a 'reconfigure' and saving, all the entities end up becoming unavailable.
Reproduction steps

Change some configuration on an existing cover
Hit save
all devices show unavailable
...

Diagnostics dump
Logger: homeassistant.config_entries
Source: config_entries.py:672
First occurred: 2:10:36 PM (1 occurrences)
Last logged: 2:10:36 PM
Error unloading entry Tilt Great Room Blinds for switch
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 672, in async_unload
result = await component.async_unload_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/switch/init.py", line 105, in async_unload_entry
return await component.async_unload_entry(entry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 198, in async_unload_entry
raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!

Sorry I keep finding these, I do love what you're doing though :)

Need to investigate that more. Does a restart work? I can remember that the sensors came back alive after a restart in my dev-env.

I guess I've found a fix. Will be releasing it soon, just needs some more testing


cant connect

Nomatter what I try in the config I keep getting:
Error while connecting to Bazarr.
I use a docker container with 6767:6767
I tried my ip of the server where it is running, localhost, <IP_ADDRESS>, <IP_ADDRESS>.
It never can connect?

Hi @huuub,
Can you please try to connect to your bazarr instance using cURL or a similar http client?
For example:
curl -X 'GET' \
  'http://<IP_ADDRESS>:6767/api/system/health' \
  -H 'accept: application/json'

should return the response:
"message": "The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn't understand how to supply the credentials required."}
If you don't get this response, then the machine you are trying to run bazarr-bulk on cannot communicate with the machine that is running Bazarr on the IP:PORT that you expect it to.

Exactly what I get:
➜  bazarr-bulk curl -X 'GET'
'http://<IP_ADDRESS>:6767/api/system/health' \
-H 'accept: application/json'
{"message": "The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn't understand how to supply the credentials required."}

I found my mistake. I needed to empty the optional parameter BASEURL.

I was getting an "unauthorized request" error and doing this fixed it for me as well. Thanks!

As it was optional I thought it would not break anything maybe adjust the documentation to avoid this confusion?

Thanks for your feedback. I've updated the README file with Configuration option section which holds explanations of what each configuration option represents. I've also updated the example config.json file to have an empty string as a default baseUrl.


ChargingThemeUI

This is An App where you can see the live battery status like whether it is charging or not. It also displays the charge percent of your current system. It is fully animated You can check it out below the video. This is built using Javascript and Frontend Technologies.
Below you can check the video? Can I add this?
https://user-images.githubusercontent.com/87573175/163221350-950d9402-249f-4a7b-bc64-4a03f83fc10e.mp4

@swapnilsparsh  Please kindly assign this issue


⚠ Bofrost.at has degraded performance

In 840a6e2, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1244 ms

Resolved: Bofrost.at performance has improved in dfa14e4 after 13 minutes.


feat: restore mysql database source

Restores the MySQL connection with a new read-only user that can be used by operators to create new reports

Thanks for the pull request, @Ian2012!  Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

What if we hide it in a setting ASPECTS_ENABLE_MYSQL_CONNECTION disabled by default?

The information for the following reports is not in Clickhouse:

Total unique users
Course approval rate (approved users / total users)

The first one is hard to make for the whole platform as there can be very old users and it's not suitable to perform a big backfill for this data. Or we can create a sink for user profiles and user anon id to be able to join user information
For the second one, I'm not so sure if there is a course approval xAPI event

@Ian2012 Even though your pull request wasn’t merged, please take a moment  to answer a two question survey so we can improve your experience in the future.


chore: add CLI flags for enabling and disabling Gateway API controllers

What this PR does / why we need it:
This introduces 3 new CLI flags for enabling/disabling Gateway API controllers:
      --enable-controller-gwapi-gateway                   Enable the Gateway API Gateway controller. (default true)
      --enable-controller-gwapi-httproute                 Enable the Gateway API HTTPRoute controller. (default true)
      --enable-controller-gwapi-reference-grant           Enable the Gateway API ReferenceGrant controller. (default true)

It's needed for https://github.com/Kong/kubernetes-ingress-controller/pull/4968 which will remove the Gateway feature flag (the only way of controlling whether the Gateway API controllers are enabled as of today).
Additionally it adjusts the envtest suite.
In #4968 the controller enablement conditions
Enabled: c.GatewayAPIHTTPRouteController && featureGates[featuregates.GatewayFeature]

will look like this
Enabled: c.GatewayAPIHTTPRouteController

PR Readiness Checklist:
Complete these before marking the PR as ready to review:

[x] the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

@programmer04 PTAL. I forgot to generate CLI reference doc.


webpack now precompiles templates in production, in dev mode behaviou…

…r as usual for better debugging
Adds pre-compiled templates in production mode.

http://jenkins01:8080/view/PR/job/arangodb-matrix-pr/10072/

Tests blue except unrelated failure.


Cask2 issue

I have a13 iPhone and it on 14.3 when I open settings it crashes I hope you can fixit and thx

I have a13 iPhone and it on 14.3 when I open settings it crashes I hope you can fixit and thx


mesa: restructure driver selection to be more architecture-neutral

Motivation for this change
Allows Mesa to build on non-x86, non-ARM platforms like ppc64(le).
Part of my roadmap to bring NixOS to OpenPower platforms.
The new logic should be logically equivalent for x86 and ARM platforms (but might cause rebuilds due to reordered list elements).
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

I don't see this very readable.
What you could do is just a separate case for x86 and then an else case which just adds the safest option (which is presumably only virgl).

The point was that "generic" architectures (like Power) that have PCIe support but no integrated GPUs get all drivers for GPUs widely available as PCIe cards by default, while drivers for integrated GPUs are only built for their platforms (ARM ⇒ freedreno, etnaviv, x86 ⇒ Intel drivers), so when following your suggestion I would need to add a specific path for ppc64(le) for each variable …

Makes sense. Maybe have the else case then just list all the drivers for the PCI(-E) cards.

Note that adding support for a new platform is something that should go through the RFC process (since it may introduce a non-trivial maintenance burden for other contributors).

New design that more clearly shows the reasoning.

@edolstra Where can I access that process? FWIW, the initial platform enablement PR was marked as [RFC] …

@CrystalGamma https://github.com/NixOS/rfcs

I see discussion on NixOS/rfcs#31 has largely concluded without major unaddressed objections …
Maybe we should just (squash &) merge this (even though the RFC hasn't been merged)?

I still think this is helpful - the old way basically just had static lists for each system. We should think more in capabilities - what driver works and doesn't work with each system.

@grahamcofborg build mesa


Fix unit test

The existing voucher and device creds were using older public
key constant resulting in unit test failure. Added new voucher and
device creds to fix the tests.

Signed-off-by: Darshini Parikh<EMAIL_ADDRESS>

Line23: import org.junit.jupiter.api.Disabled;
Please remove.


media-time-range duration discrepancy when duration is a float

This line truncates the duration value to its floor before setting the time range max. When duration value is a float, this can cause the seek position to reach the end before the video ends. In cases where duration - Math.floor(duration) >= 0.5s, this is creates a perceptible discrepancy between player and controlbar states.
It would be great if the max value for the time range is rounded to the nearest 250 or 500ms instead. In this case, stepping can perhaps be set to Math.min(currentTime + 1, duration)?

Thanks @reckoner165 ! We might not need to do the floor anymore. I suspect that might be a relic from before this change: https://github.com/muxinc/media-chrome/pull/271
We'll have a look, thanks for opening the issue!

thanks for reporting Sumanth! I think I've seen this issue one time. will get a fix in soon.


Python 3.12 patch

This should fix Python 3.12 though not without serious wrinkles.   The new PyLong mutates a field in such a way that it will break anything that wants to add memory to the tail of the object to save a few bytes.   I though that given that we were following the exact mechanism that Python requires for its own structures that we would be safe.  The mutation is entirely in private parts of Python so I can't just use the private symbols so we track with any changes.   It doesn't just break our code but also the dictoffset and weakoffset fields in the Python base class, so I can't see that it will remain in the current state.  Thus this is at best a version that will work until the repair to the memory model is done, and then we likely have to rework another time.
Changes include:

switch to mallinfo2 to avoid deprecation warning.
change to PyLong model
A shift in PyBuffer models that came in 3.9 but didn't burn us until now.
Fix for wstr which may not be well covered
Disable part of the doc system until I can figure out what Java 17 did
Update the tests to avoid deprecation warnings

Looks like it may be this change which started a Python 3.7 nightly test to fail. Example in https://gitlab.cern.ch/scripting-tools/pyjapc/-/jobs/34505253.
I'm pinned back right now, but can investigate later next week if needed.

Okay I can roll that back.   I will have to investigate which systems have mallinfo vs mallinfo2.


Support specifying checking forUpdateTS in prewrite

Ref: https://github.com/tikv/tikv/issues/14311
Requires:

https://github.com/pingcap/kvproto/pull/1096
https://github.com/tikv/tikv/pull/14492
https://github.com/pingcap/tidb/pull/42843

/merge


Suggestion: Citation support via Jekyll-Scholar

Is the static site generated by GibHub-Pages? If you generate it yourself, I suggest using the Jekyll-Scholar plugin for citations/references by adding the following line to the Gemfile:
gem 'jekyll-scholar', group: :jekyll_plugins

The jekyll-scholar plugin can now be used to add citations to the markdown documents


Annotation values should be quoted

Kubernetes will error out if the annotation values are not quoted.  The examples in README should be updated.

Valid YAML (http://www.yamllint.com/) shown below:
apiVersion: v1
kind: Service
metadata:
  name: nc-pod2-svc
  labels:
    name: nc-pod2-svc
    app: nc-pod2
    version: 0.1.0
  annotations:
    kubernetes.io/loadbalancer-class: loadbalancer-lbex
    loadbalancer.lbex/port: 9090
    loadbalancer.lbex/service-pool: netcat
    loadbalancer.lbex/upstream-type: pod
spec:
  selector:
    app: nc-pod2
  ports:
  - name:
    port: 9090

Is rejected by Kubernetes kubectl create -f ...
$ kubectl create -f nc-pod2-svc.yaml
Error from server (BadRequest): error when creating "nc-pod2-svc.yaml": Service in version "v1" cannot be handled as a Service: [pos 144]: json: expect char '"' but got char '9'


Support for service accounts in user related fields/flags/headers is under documented

This is a Feature Request
How service accounts are identified in:

The SubjectAccessReview API User field
The AdmissionReview APIs UserInfo field
The ImpersonateUser header
kubectl --as

..is under documented.
In all cases, service accounts can be referenced via system:serviceaccount:{service account username}:{service account name}.
https://kubernetes.io/docs/reference/access-authn-authz/authentication/ is the best documentation I could fine. It points out that Service accounts authenticate with the username system:serviceaccount:(NAMESPACE):(SERVICEACCOUNT). But it took me quite a while to find this, and it still wasn't obvious that user fields all accept

https://kubernetes.io/docs/concepts/security/service-accounts/
https://kubernetes.io/docs/reference/access-authn-authz/authorization/ (has one example of --as which helps signficantly)

What would you like to be added
All API "user" fields/flags/headers also somehow document that service accounts are supported.
Why is this needed
It takes way to long to figure out what is supported by use fields/flags/headers without this documentation. I ended up figuring it out mostly by searching the public web and by trying things out on a cluster.
Comments

/assign

/sig auth
/language en
https://kubernetes.io/docs/concepts/security/service-accounts/ should at least signpost to the right page
We could add a “users and groups” concept page that explains the nebulous way we, uh, don't really define these!
(BTW https://kubernetes.io/docs/concepts/security/service-accounts/ is a first-pass, we only added that concept page very recently and its absence had been noted for a while).

/triage accepted

Is anyone in SIG-Auth interested in picking this up?  I've dropped this due to worload and it might be a while before I can circle back.

/triage accepted


Add Book Abbreviations to catalog.js

In scripts/convertBooks.ts, src/lib/data/catalog.js is generated. Include the book abbreviation so that it can be used in the book selector.

The book abbreviation is included in catalog.js


[full_inu] Armor Pack 01 SSE not recognized by wabbajack

I downloaded the file and it does not recognize in wabbajack

Wrong place for reports; please read the readme.


fix: update cronbackup without updating next schedule time

Signed-off-by: Liucw<EMAIL_ADDRESS>
What type of PR is this?
/kind bug

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes https://github.com/kubeclipper-labs/kubeclipper/issues/84
Special notes for reviewers:
@x893675 @zhuzhenfan

Does this PR introduced a user-facing change?

None

Additional documentation, usage docs, etc.:

/cc @lixd @zhuzhenfan

/milestone v1.1.0

/approve


Large Shadow phantom braking

Describe the bug
Tall vehicles when casting a shadow into the adjacent lane cause openpilot to mis-identify the shadows as vehicles, and abruptly brake even with no actual vehicle in front of you in your lane
How to reproduce or log data
Very Large Vehicle or Semi in Right Lane, openpilot vehicle in Left Lane,  sun casting shadow of the Semi onto majority of left lane
Expected behavior
Not doing this
Device/Version information (please complete the following information):

Device: Comma 2
Dongle ID: 9d8c378664ae56f2
Route: No Longer Have, multiple instances on April 12th throughout my 14 hour drive.
Timestamp: N/A, after Noon
Version: Release2-staging
Car make/model: 2019 Toyota Corolla Hatchback

Additional context
Other users reporting this issue on the discord, hopefully one of them can provide a better example

Without a route this is pretty hard to look into for us. Let us know when you have an example.

I've noticed similar behavior on the latest KL model. It's super eager at picking out leads, when coming up on stopped traffic in multiple lanes it will quickly switch between the adjacent lanes until I get close enough. This also happens when there's no traffic in my lane, so it will brake for a moment until it realizes there's no lead.

Closing this due to inactivity. Let us know if you have a route for us to look into.

Closing this due to inactivity. Let us know if you have a route for us to look into.

I reported a shadow bridge braking example on discord some 4 weeks or so ago. I tried to find the bridge that it happened at, but with so many to pick from and no readily easily available brake logs on cabana, I was not able to find it. It broke from 70 to 65... so minor... but still a braking event for no reason.
This even was a braking event after a street light and into the shadow behind it (best I can tell, that is what I think it was braking for at least). The set speed was 40 and sometime around the streetlight or the shadow, OP broke to 35.
comma 3
master-ci 0.8.10
dfb993cc43ba69dc|2021-09-09--21-50-02--18 and 19
22:08::57 Local time
2020 Toyota Corolla Hatchback
Please reopen this, as it does happen from time to time and I'd like to log them better. It would be helpful to know if this is a VOACC or a radar issue?


GraphQL Fetch

Is your feature request related to a problem? Please describe.

I'm using Nuxt + Strapi on a medium-sized web application(I haven't used this module in any real project yet, but willing to). The issue I currently face is most of the time I'm using REST, but for some parts of the app a GraphQL query will do the job better(multiples queries in just 1 HTTP request for example), but making fetch/axios request to a GraphQL API without Apollo seems to require a lot of boilerplate.
Describe the solution you'd like

I would love to have a method to perform graphql queries like:
const data = await $strapi.graphql(query, vars);
Describe alternatives you've considered

const request = await this.$strapi.$http.$post('/graphql', {query, vars});
const {data} = await request.json();

The alternative seems a little bit verbose?
Additional context
Let me know what do you guys think, If you think this feature is good to have I could help with a PR.

@benjamincanac 👀

This could be a killer feature!

This could be a killer feature!

I already sent a pull request, waiting for someone to review it 😄