App redirects to /home route, which 404s

Describe the bug
If I leave the webapp open for some time and return to it later, I usually find it sitting on a 404 page at the /home route (which does not exist). It seems that something must redirect here after some timeout?
Reproduced in Firefox on mac, and Safari on iOS.
Steps to reproduce

Open memos in a tab at the root route (home page)
Leave this tab open in the background for some time (I don't know the minimum, but a day should definitely work)
Return to the tab, find it on a 404 page

The version of Memos you're using.
v0.22.4
Screenshots or additional context
No response

@murrayju, I tried to replicate but couldnt.
Shot in the dark, memo < v0.22.4 use to have a lastVisited local storage variable stored. This value would be /home or /timeline
Can you see if you still have it in your browser local storage, if so, clear it out and see if your redirect still happens

Appears to be fixed, thanks!


[web] Multiview support

Duplicate of https://github.com/dart-lang/sdk/issues/53875

Duplicate of https://github.com/dart-lang/sdk/issues/53875


SVG printing issue

C3 version:0.4.17
D3 version:3.5.17
Browser:IE 11, Chrome 62, Firefox 54
OS:Windows 10

Charts with lines do not print lines properly. In all browsers tested, in print preview the path is closed and filled with black.
This can be easily fixed using this css, per this question:
path {
	fill:none;
}

I'm not sure what knockon effects this will have for area charts, but presumably prefixing with .c3-line would solve the issue.

Have you included c3.css in your page?


⚠ ClamAV has degraded performance

In 94cd58a, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 94 ms

Resolved: ClamAV performance has improved in 7bd0f07.


workflows: Update Nix actions

Prior versions used deprecated GitHub Actions features which are now removed.

@dwightguth This is ready for your review.


highlight properties limited to be used in yield(rather than in WHERE for now)

This should be highlighted before the next release.

[ ] en doc lift

https://discuss.nebula-graph.com.cn/t/topic/6803/4
https://discuss.nebula-graph.com.cn/t/topic/6696/2

Just noticed that we have examples of using properties in GO/LOOKUP queries, we should consider reverting them in the 2.6.1 branch.

These problems are in the document, but the WHERE clause in the GO statement can use properties. Maybe this is a bug?

@nevermore3 could you please kindly help clarify that the limitation in 2.6.1 that properties() cannot be used in where clause applies on MATCH only, that is, it's already supported on GO/LOOKUP expressions?

Consult the developer to confirm that the above problem is an unexpected situation, and we will change the documentation.

Consult the developer to confirm that the above problem is an unexpected situation, and we will change the documentation.

Got it, thanks @cooper-lzy!


Incorrect parsing of sample string slices containing commas

Describe the bug
Incorrect parsing of sample string slices containing commas.
To Reproduce
When I defined the following structure and generate swagger using swag init.
type Example struct {
    Messages []string `json:"Messages" example:"\"a,b,c\",\"a,b,c\""`
}

Outputted  like this.
definitions:
  main.Example:
    properties:
      Messages:
        example:
        - '"a'
        - b
        - c"
        - '"a'
        - b
        - c"
        items:
          type: string
        type: array
    type: object

Expected behavior
I expect  to output like
definitions:
  main.Example:
    properties:
      Messages:
        example:
        - "a,b,c"
        - "a,b,c"
        items:
          type: string
        type: array
    type: object

Your swag version
v1.6.9

I think, It will be able to fix by modify the code to use csv reader alternative to use strings.Split.
https://github.com/swaggo/swag/blob/master/parser.go#L1278

I'm not sure how much is this going to be used, but if it helps you please write a PR.


ansible/v1: add new marker to add the name of the molecule task

Description of the change:
For Ansible-based operators, add a new marker to add the name of the molecule task in failure cases.
Motivation for the change:
https://github.com/operator-framework/operator-sdk/issues/4311
Blocked by

Upstream PR get merged: https://github.com/kubernetes-sigs/kubebuilder/pull/1907
SDK repo be updated with the new commit and these change

I am closing this one after a deeper check on it I realized that the variable is no longer defined for the new molecule tests and that the existent one (ansible_failed_result)  will return all data indeed the task name.


Add Spell Effects to Circle of Protection

Fixes https://github.com/foundryvtt/pf2e/issues/2307

I'm ok with the actual changes to Protection. You need to clean up the files tab though, as there are a lot of superflous changes. Maybe rebase?

I had rebased on master prior to starting work on it again last night, and it wound up pulling all the commits in, which caused all the other files to be added.

There we go; now showing only 18 files changed:

Removed the 4 previous Protection Spell Effects
Added new Protection Spell Effect
Added the link to the new spell effect to the Protection and Circle of Protection spells
Replaced the 4 previous spell effects with the new spell effect on 11 NPCs in various compendiums that had Protection as a spell


migrate permissioning ATs to junit 5

Add dependency for junit.jupiter (junit5)
Migrate per https://blogs.oracle.com/javamagazine/post/migrating-from-junit-4-to-junit-5-important-differences-and-benefits
Remove dependency on junit 4
Here's an example https://github.com/hyperledger/besu/pull/5525/files

parking this until we move to GHA. seems this is at least partially circle CI specific


Bug

[ ] Should request + estimation (time, price) of Trip first, then requesting map direction => Sometimes the destination is too far away, uber API will return error.

[ ] Annotation of Pickup and Driver point are incorrectly (wrong data, layout and missing ETA)

[ ] Support personal place (home/work)

[ ] After canceling the current trip successfully, Current position mark is vanished!

[ ] Should draw dotted-line from "Pickup point" to "The latest segment of routes". Checkout IMG_6628@2x in UberRef folder for detail.

[ ] If request Uber Observable is failed => Cause stop steam and never emit again.

[ ] Properly handle invalid Uber Token


Change to user's home directory on startup

Requires

https://github.com/RedHatInsights/yggdrasil/pull/85

Error: SA1019: "io/ioutil" has been deprecated since Go 1.16: As of Go 1.16, the same functionality is now provided by package io or package os, and those implementations should be preferred in new code. See the specific function documentation for details.  (staticcheck)

Well, that's nice, but we're still building it with go 1.15.

Well, that's nice, but we're still building it with go 1.15.

Run staticcheck with the -go 1.15 flag so that it only makes suggestions that are valid for Go 1.15.

Closing this in favor of #12


Documentation references unreleased version

Describe the bug
The Quick Start clearly references "App.xaml (v2.0.0 and newer)" in the "Styling the window" section.
Latest actual version is 1.6.n.  This is highly misleading.
To Reproduce
Steps to reproduce the behavior:

Go to https://mahapps.com/guides/quick-start.html#styling
Observe

Expected behavior
Instructions dealing with a default install first.

@richbryant If you scroll down then you will see there is also the old v1.6.5 section with the resources instructions.


[SPARK-46941][SQL] Can't insert window group limit node for top-k computation if contains SizeBasedWindowFunction

What changes were proposed in this pull request?
Don't insert window group limit node for top-k computation if contains SizeBasedWindowFunction.
Why are the changes needed?
Bug fix, Insert window group limit node for top-k computation contains SizeBasedWindowFunction will cause wrong result of the SizeBasedWindowFunction`.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
New UT. Before this pr UT will not pass.
Was this patch authored or co-authored using generative AI tooling?
No.

cc @beliefer @cloud-fan

Merged to master.

Thanks, @cloud-fan @beliefer @HyukjinKwon


CLI confirm-what-if doesn't recognize dependent resources

Bicep version
3.1
Describe the bug
Using series of Modules that have dependencies on each other via outputs. (i.e. App service plan pass plan ID to app service).
When running -c at the end of a az deployment sub create command it doesn't recognize the dependencies in the what if scenario.  Confirm after running my deployment everything was created; however, does not match the plan.  This deployment is at the subscription scope.
Not sure if this is a bug with the azure cli as I haven't tested this with other ARM templates but figured start here.
To Reproduce
Steps to reproduce the behavior:
Try running a what if against a bicep file with dependencies between modules.

I think it is this issue: https://github.com/Azure/arm-template-whatif/issues/157. Can you take a look?

Agreed, provided feedback on what happens for redeployment.

Closing and tracking with the what-if issue


Use sybpydb for Sybase access on Py3

Use sybpydb for Sybase access on Py3

Sounds fine.

My thought was that at least #11 and possibly #12 could go in a Ska.DBI release with this (maybe release 4.0?).


Make it possible to configure so we can mute the log to the console

This is needed when we run BT from sitespeed.io and we test with TAP & JUnit and don't want to output any logs to the console.

Hi,
Do you have any plans for this summer? I think I found something really interesting here http://sutarymo.walleyeonestop.com/xydhnhjd
Wishes<EMAIL_ADDRESS>


[Bug] NPM Build Script - 'ENVIRONMENT' is not recognized as an internal or external command

Hey guys,
There seems to be a bug when running npm build. I have confirmed that rollup is infact installed and made sure it matches the same version as the one in package.json.
Below is the error given when attempting to run: npm run build
><EMAIL_ADDRESS>build D:\Work\mparticle-web-sdk
> ENVIRONMENT=prod BUILDALL=true rollup --config rollup.config.js

'ENVIRONMENT' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `ENVIRONMENT=prod BUILDALL=true rollup --config rollup.config.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Is there a solution to this? Thanks!

It appears this this may be related to the OS you are using. Are you on windows?  It looks like a package like cross-env may help with this. I can add this to our backlog, but you can also feel free to test this out locally and see if you can get a PR going
also. We love open source contributions!

PR #118  fixes this


Added table for all checklist items; UI for this and button to upload…

… documents with this each item
Description

Please include a summary of the change and, if applicable, which issue is fixed. Please also include relevant motivation, context, and screenshots.
This includes the adding of a table to view all checklist items and a template with it that has an upload document button (no functionality yet) included.

Testing

Please briefly note how you tested and verified your changes.
Have not tested my changes yet, will later today with Katie.

Reviewers

Tag one or two teammates to review your code. Ideally, you should tag people who have worked on the same files or similar features to notify them of your changes. If you pair programmed with someone, please indicate that here as well.

@ivanesmeral98 after you've gone through and fixed the comments, make sure to merge the master branch into your branch!
You can do this by trying:
git checkout master
git pull origin master
git checkout <your_branch_name>
git merge master


module gonum.org/v1/plot.New() function signature mismatch

myproject/vendor/github.com/milosgajdos/go-estimate/sim/plot.go:35:9: assignment mismatch: 2 variables but plot.New returns 1 values
myproject/vendor/github.com/milosgajdos/go-estimate/sim/plot.go:43:14: assignment mismatch: 2 variables but plot.NewLegend returns 1 values

Link to file https://github.com/milosgajdos/go-estimate/blob/master/sim/plot.go#L35
Running go mod tidy does not fix it. I'm on go version go1.16.3 linux/amd64.

Strange. I'm on the same version of Go and everything seems to work just fine:
$ go version
go version go1.16.3 darwin/amd64
$ go get ./...
$ go build ./...

Note, this project pins gonum/plot to the following commit. If you browse the plot module code tree pointing to this commit you'll discover that plot.New() indeed returns 2 values see here which makes me think you must've gotten your dependencies upgraded somehow.
Please remove your build cache and make sure you get the right dependencies by running make dep.

Closing as per https://github.com/milosgajdos/go-estimate/pull/9#issuecomment-850848571


vkcube hangs with runtime layer enabled on ubuntu 22.04

This is under docker & lavapipe.
The other layers don't hang vkcube.

Running a debug build shows an assertion failure:
root@61641fa5d3ce:/build# timeout 5s /performance-layers/docker/test_performance_layers.sh .
Selected GPU 0: llvmpipe (LLVM 13.0.1, 256 bits), type: Cpu
WARNING: lavapipe is not a conformant vulkan implementation, testing use only.
vkcube: /performance-layers/layer/layer_data.h:237: auto performancelayers::LayerData::GetNextDeviceProcAddr(DispatchableDeviceHandleT, TFuncPtr) const [DeviceHandleT = VkCommandBuffer_T *, TFuncPtr = VkResult (*VkLayerDispatchTable_::*)(VkDevice_T *, VkQueryPool_T *, unsigned int, unsigned int, unsigned lounsigned long, unsigned int)]: Assertion `device_dispatch_iter != device_dispatch_map_.end()' failed.

#5  0x00007fa1f260071b in __assert_fail_base (fmt=0x7fa1f27b5150 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
    assertion=0x7fa1e8a738f6 "device_dispatch_iter != device_dispatch_map_.end()", file=0x7fa1e8a74e4b "/performance-layers/layer/layer_data.h",     line=242, function=<optimized out>) at ./assert/assert.c:92
#6  0x00007fa1f2611e96 in __GI___assert_fail (assertion=0x7fa1e8a738f6 "device_dispatch_iter != device_dispatch_map_.end()",
    file=0x7fa1e8a74e4b "/performance-layers/layer/layer_data.h", line=242,
    function=0x7fa1e8a6a505 "auto performancelayers::LayerData::GetNextDeviceProcAddr(DispatchableDeviceHandleT, TFuncPtr) const [DispatchableDeviceHandledBuffer_T *, TFuncPtr = VkResult (*VkLayerDispatchTable_::*)(Vk"...) at ./assert/assert.c:101#7  0x00007fa1e8addffa in performancelayers::LayerData::GetNextDeviceProcAddr<VkCommandBuffer_T*, VkResult (* VkLayerDispatchTable_::*)(VkDevice_T*, VkQuensigned int, unsigned int, unsigned long, void*, unsigned long, unsigned int)> (    this=0x7fa1e8bda7f0 <(anonymous namespace)::GetLayerData()::layer_data>, device_handle=0x55591ca5bfa0,     func_ptr=&VkLayerDispatchTable_::GetQueryPoolResults) at /performance-layers/layer/layer_data.h:242
#8  0x00007fa1e8add268 in performancelayers::RuntimeLayerData::LogAndRemoveQueryPools (    this=0x7fa1e8bda7f0 <(anonymous namespace)::GetLayerData()::layer_data>) at /performance-layers/layer/runtime_layer_data.cc:68
#9  0x00007fa1e8acaeb1 in (anonymous namespace)::RuntimeLayer_DeviceWaitIdle (device=0x55591cb3fa50) at /performance-layers/layer/runtime_layer.cc:313
#10 0x000055591b004c6c in ?? ()
#11 0x00007fa1f2601d90 in __libc_start_call_main (main=main@entry=0x55591b002cb0, argc=argc@entry=3, argv=argv@entry=0x7ffcf7ef6228)
    at ../sysdeps/nptl/libc_start_call_main.h:58
#12 0x00007fa1f2601e40 in __libc_start_main_impl (main=0x55591b002cb0, argc=3, argv=0x7ffcf7ef6228, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7ffcf7ef6218) at ../csu/libc-start.c:392
#13 0x000055591b005c0a in ?? ()


[Feature] - Allow admins to review their own plot

Is your feature request related to a problem? Please describe.
I dont think im the only one faced with this but your a admin building on the plot system and you submit and realize you gotta ask another admin to get online to approve your build
Describe the solution you'd like
Allow people with the plotsystem.review.* permission node to review their own plots.
Describe alternatives you've considered
NIL
Additional context
NIL

We disabled this because we want a fair Plotsystem for everyone. You are way too biased reviewing your own plot. Waiting for another admin/reviewer really is not a problem.

We could enable self-reviewing for admins, if the dev-mode is true, dont think I want to enable this for production use tho

We could add a config option, but I also think that the dev-mode is the better solution..

Absolutely. For testing purposes it could be quite handsome

Implemented in https://github.com/AlpsBTE/Plot-System/commit/ce2311684eda4b3947085fa7f6c3349ef84129da


React Native module

Hey @lokimeyburg! This library is really neat and I think it aligns really well with React Native - if implemented properly, users would not have to write a single line of native code to leverage this functionality. Just wanted to put that on your radar!

@brentvatne I'm watching React Native very closely - it's very rad! Haven't thought about creating a module - thanks for the idea - I'll definitely take a look.


Feature: [settings/plugins] Add live search filter to plugins

Now Saltcorn has a lot of plugins (as minimum 43) so the live search will help to navigate.

yes, and pagination

yes, and pagination

implemented in #526

implemented in #526


Select network address based on type

Currently we use <IP_ADDRESS> a lot when a bind address is required, and as a result we end up binding to all addresses.  This is both confusing and potentially an issue if we can't more closely control which address types to use (e.g. we may end up binding compute nodes to public addresses unintentionally).
This PR provides functionality to iterate the addresses available on the current host and to filter them based on network type.  This means we can filter on public, private, local or linklocal addresses for various use-cases.
It also changes the configuarion getter for Server API Host to allow the address type to be specified in place of an IP address.  This means we can set Server.API.Host to an IP address as currently, or "public" to get a public address, or "private" to get a private address. Care must be taken as most dev laptops won't have a public address and as the 'production' environment is the default, we can't (and this PR doesn't) default to 'public'.    It also only uses the first address of a type it finds, and so does not handle special cases which may have multiple public addresses.
This should resolve #3322 by allowing us to specify an address type rather than <IP_ADDRESS> once we are using the appropriate env.
Future changes should allow for a comma separated list to also support:

"public,private"
"public,<IP_ADDRESS>"

Do we know how other similar systems handle this?

Mostly by being explicit about the IP you want to bind to, k3s for instance auto binds to the first public address unless you specify an explicit address.  I think we've been over-using <IP_ADDRESS> so that we don't have to think too much about which address to use.
This really only gets us an easy way to get the first public, or private address for various uses, the best solution would be to be explicit on which IP to bind to.


doc: fix JSON example

Parsing the JSON example threw an error during the github.io doc build because of the ... content.  I removed the ... to remove the error. (You could also remove the JSON language name so it's not parsed as JSON.)

@lkk12014402 @chensuyue @lvliang-intel  Error in JSON example is causing the github.io doc build to throw an error

@chensuyue How do I fix this failed UnitTest?  This is a doc-only change PR.

file was moved from evals/auto_tuning/README.md to evals/benchmark/auto_tuning/README.md after this PR was submitted, so closing this and opening a new one.  Sigh.


Readonly problem with Typescript 2.7

TypeScript Version:  2.7.1
Search Terms:
Readonly
Code

class SuperMyClass {
    test: Readonly<Test>;
    constructor() {
        this.test = {a:"a", b: "b"};
    }
}

class MyClass extends SuperMyClass {
    constructor() {
        super();
        this.test.a = ""; // don't work but KO, I'm in contructor
                          // Error TS : Cannot assign to 'a' because it is a constant or a read - only property
        this.test = {a:"a", b: "b"}; // Work
    }
    aMethod(): void {
        this.test.a = ""; // don't work but OK, I'm not in contructor
    }
}

interface Test {
    a?: string;
    b?: string;
}

Expected behavior:
I want to initialize only props 'a' in the constructor of the child class.
Actual behavior:
Error typescript:
Cannot assign to 'a' because it is a constant or a read - only property
Playground Link:
https://www.typescriptlang.org/play/index.html#src=
class SuperMyClass {
    test%3A Readonly<Test>%3B
    constructor() {
        this.test %3D {a%3A"a"%2C b%3A "b"}%3B
    }
}

class MyClass extends SuperMyClass {
    constructor() {
        super()%3B
        this.test.a %3D ""%3B %2F%2F don't work but KO%2C I'm in contructor
                          %2F%2F Error TS %3A Cannot assign to 'a' because it is a constant or a read - only property
        this.test %3D {a%3A"a"%2C b%3A "b"}%3B %2F%2F Work
    }
    aMethod()%3A void {
        this.test.a %3D ""%3B %2F%2F don't work but OK%2C I'm not in contructor
    }
}

interface Test {
    a%3F%3A string%3B
    b%3F%3A string%3B
}

var myClass %3D new MyClass()%3B

console.log(myClass.toString())%3B%20%2F%2FKenobi
Related Issues:

It would be a bad idea to allow that because we don't know that test is "owned" by the class containing it -- it could be a reference to an object elsewhere, and we don't want to allow you to mutate that external object via a Readonly reference. Consider this example:
interface Point { readonly x: number; readonly y: number };
const ORIGIN: Point = { x: 0, y: 0 };
class A { constructor(p: Point) {} }
class B extends A { constructor(p: Point) { super(p); p.x = 1; } }
new B(ORIGIN);

In order to ensure that the original object isn't modifier, but to avoid changing the values of other properties, you could use the spread operator: this.test = { ...this.test, a:"" };.


Add Link to repo in the about section

@eddiejaoude I think only you can do this.

@eddiejaoude a friendly reminder :)

Thank you @schmelto 👍
Should be done now...


Will Cotton, U1S4: Statistical Tests and Experiments

Great job on the assignment from Monday. Your code looks good and you did a great job of completing the t-tests required. You could add further comments to help understanding of the process. Keep up the good work!

Excellent work on the assignments from Tuesday and Wednesday. Your code is great and your comments and use of markdown blocks makes it very easy to understand and follow your processes. You did a great job on your charts as well. Your analyses were also spot on. Awesome job so far this week!


SSR rendering

Raising this as it would be an awesome feature to be able to generate the initial render of the chart on the server.

https://github.com/kirjs/react-highcharts/blob/master/recipes.md#rendering-react-highcharts-on-node


Arnold 5.4 support

New Arnold Features

New clip_geo shader
New aov_read_* shaders
Added enable checkbox to assignments in set_parameter operator

SItoA specific enhancements

Export Nref (#78)
Added expressions from Arnold light shaders to the Softimage primitive so some parameters can be shown in the viewport.

Bugfixes

Fixed bug that shaders defined in ArnoldShaderDef.js couldn't be rendered with xsibatch (#77)
Fixed build system bug that made Arnold plugins not update properly (#69)

Known Issues
SItoA still crashes when trying to get a license from Autodesk License Manager (FlexLM). RLM licenses work fine. See #74 for details.

5.4 doesn't change much so I think this is it for v5.4.0.
@sjannuz Is there an Arnold core bugfix release in the pipe soon? If there is, maybe we merge after that?

5.4 doesn't change much so I think this is it for v5.4.0.
@sjannuz Is there an Arnold core bugfix release in the pipe soon? If there is, maybe we merge after that?

Yes, a <IP_ADDRESS> is expected soon.

So I think I'm done with this one now so you can merge it @sjannuz.


Openpifpaf and OFM Classifier ONNX models added, they are needed for generating TensorRT on Jetson devices

@undefined-references can you please resolve the conflict and resubmit?


LCFS - Standardization of Label Management in Frontend

Describe the task:
Develop and implement a systematic approach for managing labels in the frontend application. This involves creating a well-organized structure for label constants, considering various user roles and workflow states.
Purpose:
To streamline the process of managing and updating labels, ensuring consistency and ease of maintenance across the application. This will also aid in localization efforts and improve the flexibility of the UI to adapt to different user roles and workflow states.
Acceptance Criteria:

[ ] Review the current implementation of labels in the application.
[ ] Design a structure for organizing label constants. This could involve grouping labels by features, user roles, workflow states, or a combination of these.
[ ] Create a centralized system for label management, such as a dedicated directory with multiple files or a single file with structured sections.
[ ] Implement a naming convention for labels and groups of labels to enhance readability and ease of access.
[ ] Create a plan to refactor the application to utilize this new structure for label management and review the strategy with the dev team.
[ ] Ensure that the new system supports easy addition or modification of labels as the application evolves.
[ ] Document the structure and usage guidelines for the label management system.
[ ] Test the application thoroughly to ensure all labels display correctly for various user roles and workflow states.

Additional context:

Coordinate with UI/UX and development teams to ensure that the new label management system meets all requirements and is scalable.

Hey team! Please add your planning poker estimate with Zenhub @AlexZorkin @hamed-valiollahi @kevin-hashimoto @prv-proton

Nothing for PO/SME to test


Targeting at the GM makes all targets show the icon of the last token used to target for players

If you select Token A and target Token Z, players will see Token Z targeted by Token A (and the GM, but that's another bug). If the GM then users Token B to target Token Y, both Token Y and Token Z will be shown to the players as targeted by token B. The GM will see it correctly.

As an update, this bug is still there but slightly different in the new version. As the GM if you target a token with Target portraits turned on, then whoever you have selected will have their portrait displayed. However, if you select someone else and target, it ADDs their picture to the list of portraits rather than replaces the existing portraits. So, eventually every token on the map is displayed when you target as they accumulate.

Please, @Zamrod , do you mind confirming that this is the same bug I reported recently?
https://github.com/eadorin/target-enhancements/issues/43
I didnt see this issue before posting mine.


training input shape changed after v2.7.0

https://github.com/tensorflow/tensorflow/blob/92a6bb06549e74a8bd8cdb8e28552496e5520007/tensorflow/python/keras/engine/training.py#L798
There is a expand operation for 1d input data, but this op is missed in v2.7.0. I'd like to know why and how can i keep compatibility

@wiyr
In order to expedite the trouble-shooting process here,Could you please fill the issue template,
Thanks!

This is keras issue. I will close it and opend in keras repo. Thanks


Add oobabooga/text-generation-webui support as a llm

Add oobabooga/text-generation-webui support as an LLM.  Currently, supports using text-generation-webui's non-streaming API interface.  Allows users who already have text-gen running to use the same models with langchain.
Before submitting
Simple usage, similar to existing LLM supported:
from langchain.llms import TextGen
llm = TextGen(model_url = "http://localhost:5000")

Who can review?
@hwchase17 - project lead

lets add an example notebook as well

Thanks for the review. I've fixed the Black formatting and have added an example notebook.

Can a maintainer kick off the workflows?  I believe I've fixed the previous errors.

@hwchase17 can you help kick off the workflows for this PR? I believe I've fixed up all of the errors.


VScode not connecting to ipykernel

VSCode Version: 1.48.2
OS Version: macOS Catalina 10.15.6

Steps to Reproduce:

create a new folder test. Run pipenv to install packages (jupyter, ipykernel)
Open folder in VSCode and create a new notebook using the interpreter 'test'.
Error message : Unable to start session for kernel Python 3.8.3 64-bit ('test': pipenv). Select another kernel to launch with.

Note: preexisting pipenv interpreters are working fine. For example selection pre-existing env in step 2.

Does this issue occur when all extensions are disabled?: NA. Python extension is needed for notebooks.

I have exactly the same problem.  VS Code Version 1.48.2, macOS Catalina 10.15.6.  Cannot connect to kernels created by pipenv.

/extPython

Just for information. I resolved the issue following the steps here.


WDI-Melville-Robert-King: Fundamentals Code Submission

Submitting RPS code for review.

Looks great, good job. Think about thoughtful naming. Given that you have var playerWins, use var playerMove instead of var pMove. It is more consistent, and gives more explanation about what the variable is describing. Looking forward to meeting you Monday1


[PRO]: Possible to change placeholder text programmatically after initial load

Describe the bug
We are trying to find a way to change the Placeholder text programmatically after the editor has already loaded. It shouldn't clear the text in the editor, just change the default messages shown if the box is emptied.
It doesn't seem like this is possible at the moment (apologies if we missed it), is this something that could be added in a future release (Pro or otherwise)?

Hi! Update an extension configuration after initialization looks hard, but we got a couple of requests for that feature and we are going to keep it as a free feature :)
here is the PR, we will try to merge soon:
https://github.com/10play/10tap-editor/pull/213

@GuySerfaty I tried out the latest release (05.23), and I see the new setPlaceholder method on the editor bridge.  But for some reason, it always appears to be undefined when I try to call it?
I rebuild my embedded editor and everything appears to type-check, but it fails at runtime.  Any thoughts?
  const editor = useEditorBridge({
    // DO NOT USE avoidIosKeyboard, it is a trap.
    dynamicHeight: true,
    bridgeExtensions: [
      ...TenTapStartKit,
      CoreBridge.configureCSS(editorCss),
      PlaceholderBridge.configureExtension({
        placeholder: placeholder ?? t`Send a message...`,
      }),
      ...

Here is how I'm initializing my bridge.

Thank you so much, I see this is now fixed and released in 0.5.23 and its working great.


Vercel not picking up env variables with sveltekit

Hi,
I'm trying to implement dotenvx into our main app. Which is sveltekit, deployed on vercel.
I followed the guide but when I deploy the app to production no env variable is picked up.
Upon building the app I can clearly see
> dotenvx run -f .env.production -- ./node_modules/.bin/vercel

<EMAIL_ADDRESS>injecting env (28) from .env.production
Vercel CLI 34.2.8

But it fails to deploy because of missing env variables.
For now I can still manually keep the vercel env variables up to date in vercel itself and use dotenvx locally.
Do you have any insights to how I might solve this issue?
PS: Is there btw a way to decrypt env variables after they have been encrypted :P? I might have by accident removed my original copy. I thought I read somewhere it wasn't possible. Which makes total sense. Just confirming if that is the case.
PPS: is there a way to exclude certain variables from being encrypted with for example adding a certain comment?
Thanks for your time.

Do you have any insights to how I might solve this issue?

Vercel has inconsistencies in how they respect environment variables. i'll dig in some more, but i vaguely remember it was a difference in their serverless functions vs their traditional hosting.
is there are a difference there? do you know which you are using? (i'm not too familiar with Vercel)

PS: Is there btw a way to decrypt env variables

coming in 1.6.0 (probably will be released tomorrow) 🎉 https://github.com/dotenvx/dotenvx/pull/294
$ dotenvx decrypt
decrypted .env

of
$ dotenvx decrypt --stdout > filename.txt

there's probably a way to pipe stdout directly to vercel's cli to automate updating envs - not sure.

PPS: is there a way to exclude certain variables from being encrypted with for example adding a certain comment

sort of. it's the inverse. you can choose which keys you want.
dotenvx encrypt -k KEY1 -k KEY2 -k KEY4

a comment might be a good move to make this easier. can you elaborate on your use case here?

PPS: is there a way to exclude certain variables from being encrypted

also, you can currently optionally use set instead of encrypt to individually encrypt envs. dotenvx set KEY value

Ok so I found the solution.
For the vercel part, there is a Project Settings tab and a Build Command override option.
I've added dotenvx run -f .env.production -- vite build instead of the vite build and that obviously solves my issue.
It's maybe an idea to include this in the docs as well.
Now for the decrypt i basically console logged them all injected them back into vercel, to just find out 1min later that there was that build override option 👍🏼 🤣 .
Anyway. Thanks for your creation. I have to admit that I like this approach a lot.. compared to all the other methods I've tried so far. 🙏🏼
Cheers

Oh no, in the heat of the moment I wanted to send you an update, I saw successful deployement but apparently they are still not being injected.. Sorry for that.

thanks for the additional info. i'll duplicate the problem tomorrow with a helloworld sveltekit guide and see if I can debug the issue. today celebrating the 4th of July over here in the states! 🇺🇸🎆 cheers!

I've successfully deployed a SvelteKit project on Vercel, but not in the setup I want.
There are two dimensions of interest:

SvelteKit env variables: SvelteKit distinguishes between static and dynamic env variables. Static env variables are inlined at built time.
Vercel deployment methods: You can deploy a Vercel app using the git integration or by building locally (or in CI/CD) and running vercel deploy --prebuilt.

The dotenvx documentation for Vercel covers a case equivalent to using static env variables and deploying with the git integration. Similarly, I was able to get it working with static env variables and manual deployment.
However, my ideal setup is:

Build the app locally, somehow include .env.production in the bundle
Add only DOTENV_PRIVATE_KEY_PRODUCTION as a secret in the Vercel Dashboard
Have a custom Vercel entrypoint that loads the env variables using dotenvx

This approach would avoid sending a bundle with inlined secrets to Vercel, enhancing security. Unfortunately, there doesn’t seem to be a straightforward way to implement a custom Vercel entrypoint that accomplishes this.

You'd expect the command dotenvx run -f .env.production -- vite build to do all the required work on vercel's side since the .env.production is available inside the repository and the .env.keys production key variable is stored on vercel as well?
Because of the way dotenvx exposes the env variables before starting the actual build one would expect it to be irrelevant how sveltekit handles env variables at buildtime? I have little experience with the inner workings of buildtools etc so forgive my ignorance :).
I've used the sveltekit env variables both static and dynamic import variables in certain parts of the codebase, but also use basic process.env.XXX variables within certain parts so that those functions can be called by standalone scripts with tsx for example. All of this works as expected when populating all of the required env variables in the vercel dashboard settings, but as soon as I delete them, it can't find the variables supposedly injected at buildtime by dotenvx

Because of the way dotenvx exposes the env variables before starting the actual build one would expect it to be irrelevant how sveltekit handles env variables at buildtime

indeed, that is reasonable, and what I would expect as well, but Vercel has been known to have very unexpected quirks around this:

https://github.com/vercel/vercel/issues/10607
https://github.com/vercel/next.js/discussions/39705

trying to get to this ticket today but might not be until later this weekend. apologies for this.

I've run into a minor issue again today where I forgot to add an env in vercel and it crashed prod. 😆  This is of course my bad, but it made me remember this ticket more vividly :P.
Were you able to find some time to dig this one out?

i haven't. seems like sveltekit's environment variable handling is pretty complicated: https://github.com/sveltejs/kit/discussions/6718#discussioncomment-3614188
so i guess my first question is - do you have any backend code or is this all front-end "built" code you are referring to?

I don't know if this is the right issue to add this to but I can't seem to get decrypting vars working in Vercel middleware whether I prebuild or not, though I can see them being injected in the build process on Vercel, they don't appear to be in the runtime, can't tell if it's just middleware or serverless functions too.
Was thinking this might be a good solution if it is indeed a problem: https://github.com/marketplace/actions/vercel-set-environment-variables literally just overwrite all vercel ends with an api on push

do you have any backend code or is this all front-end "built" code you are referring to?

Ok, so this is what I know. I'm using sveltekit as a fullstack solution. Therefor it has both client side code and server side code. The server side code uses env variables which have to be injected at runtime (ie dynamic values, prefixed with PRIVATE. The client side code, is public code, and can contain public env variables which are allowed to be exposed publicly. This is why they differentiate in the docs between the 2 types of env variables. The public vars can be compiled with the code at build time. The server side part reads it's secret env values from the server environment which hosts the app. As a side note, we can never expose a PUBLIC var to the client side code, because it's literally included in the bundle.
So to conclude, the only reason the example in the docs works (I think) is because the env var is pre-packed statically with the client side code at build time. Instead of exposing the env value to the vercel backend, so that it is actually available at runtime on vercel itself.
One would expect vercel to take these injected variables at build time and sync them over in some way, but this doesn't appear to be the case. What I don't understand is why the build command I've entered in the vercel dashboard does not actually use the .env.production variables. It seems to be only building the app, and discarding any env's exposed at build time to use at runtime. They seem to be only using their own env store to supply the server functions with the actual PRIVATE_ env variables.
This is what I was able to figure out. But I can't look at what vercel is cooking so ... many assumptions.

I ran into (what I think is) the same problem, but with nextjs + vercel, and found 2 basic workarounds. The discussion @motdotla linked above at https://github.com/vercel/next.js/discussions/39705 describes the solutions as well. It seems the basic problem in vercel is that we cannot control the runtime startup process to be able to inject variables at runtime, but I could be wrong.
The solutions seem to be:

Add a webpack plugin to next.config.js to inject the dotenvx vars at build time.
Push the env vars into vercel with a script (not ideal but does work)

Here is the webpack plugin that works:
const { execSync } = require('node:child_process');
const { DefinePlugin } = require('webpack');

/** @type {import('next').NextConfig} */
module.exports = {
  // other config here

  // https://github.com/vercel/next.js/discussions/39705
  webpack: (config, { nextRuntime }) => {
    if (nextRuntime === 'edge' || nextRuntime === 'nodejs') {
      const env = JSON.parse(execSync(`yarn dotenvx get -f .env.${process.env.VERCEL_ENV}`).toString());

      const defines = {};

      for (const [key, value] of Object.entries(env)) {
        defines[`process.env.${key}`] = JSON.stringify(value);
      }

      config.plugins.push(
        new DefinePlugin(defines)
      );
    }

    return config;
  },
};

Here is a script to sync the env vars:
#!/usr/bin/env bash

set -euo pipefail

export NODE_NO_WARNINGS=1

env_json=$(yarn dotenvx get -f $1)

variable_names=$(echo "$env_json" | jq -r 'keys[]')

function delete_env_variable {
  echo "[$1] removing $2"
  yarn vercel env rm $2 $1 -y || echo "No env variable to remove"
}

function create_env_variable {
  echo "[$1] adding $2 = $3";
  echo -n "$3" | yarn vercel env add $2 $1
}

for variable in $variable_names; do
  # skip system variables
  if [[ "$variable" == 'ENABLE_EXPERIMENTAL_COREPACK' ]]; then continue; fi
  if [[ "$variable" == 'NODE_ENV' ]]; then continue; fi
  if [[ "$variable" == 'NX_DAEMON' ]]; then continue; fi
  if [[ "$variable" =~ ^VERCEL.* ]]; then continue; fi
  if [[ "$variable" =~ ^TURBO.* ]]; then continue; fi

  value=$(echo $env_json | jq --arg k "$variable" -r '.[$k]');

  delete_env_variable $2 $variable
  create_env_variable $2 $variable "$value"
done


Bug: stop watching unless viewportSpy=true is passed to modifier

close #256

This isn't technically a breaking change but I am worried about the implications for users that were relying on the modifier not stoping it's observer behaviour (infinite lists) after first "enter into viewport"...


flyctl: fix ldflags date parsing

Description of changes
currently flyctl panics as it isn't able to parse the date: https://github.com/superfly/flyctl/blob/master/internal/buildinfo/version.go#L30
ping @rgarza, my apologies for not testing thoroughly enough.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

A passthru version test or a installChechPhase would have caught this

@Artturin ah, good idea. I've just sent a PR to do exactly that: https://github.com/NixOS/nixpkgs/pull/172428


System tray task

How do I create a system tray task?

FYI - System Tray is not in scope, see the closed issue: #171

I find it, but how can I hide the window? The Photino does not support hidden windows.

In your Program.cs when the main window is being created & instantiated you can try the following.
Set the size of the window to 0 x 0 with the SetSize(0,0) call.
// at the bottom of Program.cs right before the event loop is started (before WaitForClose() is called
        .Load("wwwroot/index.html"); // Can be used with relative path strings or "new URI()" instance to load a website.
window.SetSize(0,0);
window.WaitForClose(); // Starts the application event loop

This is a workaround, but it will cause the window to be 0 pixels by 0 pixels and if the user clicks on the taskbar icon then no window will show.  Not perfect, but may get you to your solution.


Failed to activate the html2jade package

[Enter steps to reproduce below:]

...
...

Atom Version: 0.190.0
System: Mac OS X 10.10.2
Thrown From: html2jade package, v0.7.0
Stack Trace
Failed to activate the html2jade package
At Cannot read property 'command' of undefined

TypeError: Cannot read property 'command' of undefined
    at Object.module.exports.activate (/Users/yzg/.atom/packages/html2jade/lib/html2jade.coffee:8:32)
    at Package.module.exports.Package.activateNow (/Applications/Atom.app/Contents/Resources/app/src/package.js:225:19)
    at /Applications/Atom.app/Contents/Resources/app/src/package.js:206:30
    at Package.module.exports.Package.measure (/Applications/Atom.app/Contents/Resources/app/src/package.js:152:15)
    at Package.module.exports.Package.activate (/Applications/Atom.app/Contents/Resources/app/src/package.js:199:14)
    at PackageManager.module.exports.PackageManager.activatePackage (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:435:21)
    at /Applications/Atom.app/Contents/Resources/app/src/package-manager.js:419:29
    at Config.module.exports.Config.transact (/Applications/Atom.app/Contents/Resources/app/src/config.js:302:16)
    at PackageManager.module.exports.PackageManager.activatePackages (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:414:19)
    at PackageManager.module.exports.PackageManager.activate (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:395:46)

Commands

Config
{
  "core": {
    "ignoredNames": [
      ".git"
    ],
    "disabledPackages": [
      "autocomplete"
    ]
  }
}

Installed Packages
# User
Sublime-Style-Column-Selection, v1.2.3
autocomplete-plus, v2.9.0
cut-line, v0.10.0
highlight-selected, v0.9.1
html2jade, v0.7.0
language-jade, v0.3.0

# Dev
No dev packages

+1

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
GideonFr, @Chiuuu0209, @jonyzhang2023, @songw, @thowell, @atsuhiro, @farzaaaan, @intrinsicvardhan, @vahbuna, @hornbillw, @chenyao36, @LaxmanSinghTomar, @AmeerArsala, @kevzos, @narek-am, @themichaelusa, @joaorafaelm, @coffice12, @PatrickJS, @jekahamster


[ShadowDOM] Modal doesn't work well with ShadowRoot

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior 🤔
Everything works well.
Current Behavior 😯
With 3 hacks, it partially works. But all events lost (like onClick)
(In this example, CSS also lost too but it is not the key problem. I have resolved this problem in my context, by implementing a custom JSS renderer to render the style into the ShadowRoot)
Steps to Reproduce 🕹

Context 🔦
I'm developing a crypto-related browser extension. I need to render everything in ShadowRoot to prevent the host webpage get any info from my extension.
Your Environment 🌎

Tech
Version

Material-UI
latest

React
16

Browser
Chrome 74

TypeScript
N/A

And ReactDOM.createPortal works well.

We have a similar issue in #16191.

Okay, I resolved this by more hacks. But still nice to see this problem get resolved.

It's related to #17473

Having this issue right now. Got trouble understanding and applying the solution of @Jack-Works . Would appreciate any form of help

@Dizzzmas Hi, my example is cheating on the ShadowRoot DOM object and let it behave like a normal HTMLElement so the React will accept to render on it. Which part you don't understand?

@Jack-Works
Here's the code that I'm trying to use:
const MyDialog = () => {
  const classes = useStyles()

  const portalhost = document.createElement('div')
  portalhost.setAttribute('id', 'portalhost')
  document.body.prepend(portalhost)

  const portal = portalhost.attachShadow({ mode: 'open' })

  React.useEffect(() => {
    const modal = document.getElementsByClassName('MuiDialog-root')[0]

    if (modal) {
      const style = document.getElementById(`main-head-clone`)
      if (style) {
        const stylesClone = style.cloneNode(true)

        portal.append(modal)
        portal.append(stylesClone)

        const hackingEvents = new WeakMap()
        function hack(eventName: string, shadowRoot: ShadowRoot) {
          debugger
          portal.addEventListener('click', (e: any) => {
            debugger
            if (hackingEvents.has(e)) return
            const path = e.composedPath()
            debugger
            const e2 = new e.constructor(e.type, e)
            debugger
            hackingEvents.set(e2, path)
            shadowRoot.dispatchEvent(e2)
            e.stopPropagation()
            e.stopImmediatePropagation()
          })
        }
        // call hack with parameter1 = Event name you want to make it work with ShadowRoot
        // parameter2 = the shadow root

        hack('click', portal)

        const target = Object.getOwnPropertyDescriptor(Event.prototype, 'target')

        if (target) {
          const nativeTarget = target.get
          Object.defineProperty(Event.prototype, 'target', {
            get() {
              if (hackingEvents.has(this)) {
                return hackingEvents.get(this)[0]
              }
              if (nativeTarget) return nativeTarget.call(this)
            },
          })
        }
      }
    }
  })

  return (
    <Dialog open disableBackdropClick disableEscapeKeyDown onClick={(e) => console.log('dialog', e)}>
      <DialogContent className={classes.dialogContent}>
        <ErrorOutline className={classes.errorIcon} />
        <DialogContentText className={classes.dialogContentText}>

              My Extension

            Please click the button.

          <Button onClick={(e) => console.log('TEST', e)}>Click me</Button>
        </DialogContentText>
      </DialogContent>
    </Dialog>
  )
}

The Dialog is properly placed into the shadow-root and from the debugger window I can see that hackingEvents weakMap is being filled.
I didn't use


restore doc builds

Codecov Report

Merging #17 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #17   +/-   ##
=======================================
  Coverage   96.39%   96.39%
=======================================
  Files          13       13
  Lines         555      555
  Branches       92       92
=======================================
  Hits          535      535
  Misses         10       10
  Partials       10       10

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 b657183...f2005a0. Read the comment docs.

@ewjoachim it does not work for the moment. It's in progress :)

Oh, ok then.


Count Inversions problem in C

💥 Proposal
(A clear and concise description of what the proposal is.)
I would like to add the code for the Count Inversions problem in C. Please assign this issue to me[GSSOC'21].
Have you read the Contributing Guidelines on Pull Requests?
Yes.

/assign


Implement getter API for users (Postgres)

Create a User API to return JSON from Postgres, following the basic pattern used for Cases, Methods, and Organizations

Done in PR #34


profiles: Trigger UsernameChanged event when setting username

As the title says. The official farming timer plugin and the bitwarden plugin from the plugin hub subscribe to this event. I have confirmed both to be working as expected with the necessary changes. I could make a PR, but not with the version with password support.

I have prepared a working version here: https://github.com/kmarius/runelite-plugins/tree/profiles

The event is now automatically fired after setting username.

The event is now automatically fired after setting username.


[PE-D][Tester B] UG not updated for v1.3

UG is nor updated for v1.3, and as assignments seem to be one of the most important features, due to its capability to link student and tasks, this may be a big problem for readers to use the product to the fullest potential

Labels: severity.High type.DocumentationBug
original: JasonCP14/ped#26

Duplicate of #187


Feature/migrate blockchain connector to desmos

Delete Blockchain Connector Helm Chart
Delete Broker Adapter Helm Chart
Update Readme.md
Add Desmos Helm Chart

Hi  @oriolcanadesin2 ,
please don't add the helm-chart to the repo. It should be added as a dependency to the access-node chart and the two old charts can be removed completely.


doesn't build

Starting Performing "debug" build using /usr/bin/dmd for x86_64.
Building bc-string 1.3.3: building configuration [default]
/home/user/.dub/packages/bc-string-1.3.3/bc-string/source/bc/core/demangle.d(917,37): Error: returning `this.parseTypeFunction(name, IsDelegate.no)` escapes a reference to parameter `this`
/home/user/.dub/packages/bc-string-1.3.3/bc-string/source/bc/core/demangle.d(782,12):        perhaps change the `return scope` into `scope return`
/home/user/.dub/packages/bc-string-1.3.3/bc-string/source/bc/core/demangle.d(2036,14): Error: template instance `bc.core.demangle.Demangle!(NoHooks)` error instantiating
Error /usr/bin/dmd failed with exit code 1.

On Line 782, transposing scope and return removes the failure

https://github.com/tchaloupka/bc-string/pull/6


If we expose the SSL port, why does nntp use_ssl fail?

The pynntp test_nntp_client_with_ssl() pytest still xfails.

greenbender/pynntp#30
https://github.com/greenbender/pynntp/blob/15815ec71080f05c0baf49575e27742c8d2f4123/tests/integration/inn2/test_inn2.py#L67

inn does not have ssl enabled by default - this can be fixed.
Though since it wll be using a self signed cert we have have to add an env var to pynntp to support disabling cert validation, or pynntp could supply a key/cert to inn via a bind mount and add the cert to the host cert store. There are options.

Resolved in #9

Release https://github.com/greenbender/inn-docker/releases/tag/0.9.1 will support TLS.


Drag and drop elements in the outline to rearrange code

It would be very practical to be able to drag and drop let's say a function in the outline panel to change its position in the file.

This is a duplicate. Unfortunately, I don't recall the exact issue number nor its title :flushed: Anyways, searching for issues with the same labels will likely help you :point_right:
https://github.com/microsoft/vscode/issues?utf8=✓&q=is%3Aopen+label%3A"outline"

Thanks @jrieken! I had a look at the issues with the "outline" tag and found this one: https://github.com/microsoft/vscode/issues/131948
It's also about moving items in the outline but specifically for notebook cells.
I was thinking more about any code file, e.g. moving JavaScript functions/variable declarations around directly from the outline (instead of having to manually select all the corresponding lines of code in the editor, copy, scroll to another spot, paste)
But if that other issue also covers that then it's all good!

This is the one: #68353
It got closed as out of scope.

You can still vote on closed issues


Upon receiving an fload request, player/file servers should broadcast the total length of the file, not just the fact a file was loaded.

Fairly self explanitory, I figure clients need some kind of way of knowing the total length of a file. I'm not sure exactly how this would be best implemented, but I might try throwing something together in playd.

Agreed.  It's something we've always wanted in playd.
Sent from my iPhone

On 28 Jan 2017, at 11:42, Samuel Hand<EMAIL_ADDRESS>wrote:
Fairly self explanitory, I figure clients need some kind of way of knowing the total length of a file. I'm not sure exactly how this would be best implemented, but I might try throwing something together in playd.
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


cmd/vet: builtin calls now return hasSideEffects false

https://golang.org/cl/111416 made hasSideEffects return false when CallExpr.Fun has a true IsValue, but "Builtins are not considered values."
This showed up in https://golang.org/cl/112255, where a call to len started being recognized as having no side-effects. len indeed has no side effects, and it's probably a useful change as shown by the spotted new issue.
However, I suspect not all built-ins are side-effects free.
/cc @griesemer @mvdan

Thanks for noticing so quickly! This was indeed unintended behavior. I'll send a fix right away.


Get the Awesome status bar rendering in wlroots

Thanks to the work from @psychon on implementing parts of #389 and #388, the parts of Way Cooler that host the Lua libraries now run far enough to draw the status bar correctly.
A good first step to porting Way Cooler over to wlroots is to render that bar which will ensure that the pipeline from Lua -> wlroots will work fine and that the wlroots-rs API is usable.
There will be more work necessary to get it ready for real use, but this is a fun, relatively easy first step.

Note: this probably won't utilize surface layers at the onset, as that seems fairly complicated and is very volatile right now in wlroots. This is purely getting a cairo surface and rending it on the screen every frame.

TL;DR: The hard part of this is figuring out the communication between threads.
Since it's closely related: Here is a patch for latest master that makes awesome's wibar show up with wlc: https://gist.github.com/psychon/354551ddd101494f361ecf6f8f2d3117
Most of this is relatively straight-forward. The hard part is figuring out how to share the cairo surface between the Lua thread and the main thread. This hack really tries to share things and wraps it in an Arc and a Mutex. That's a bad idea for many reasons. Thus, I would actually suggest that Drawable::refresh() somehow copies the surface's contents over. No idea into what it should copy things.

Copying the surface over could work, though it does seem a little silly to have to do that...
I'll probably do it the "dumb" way first just to get it working and then try to come up with a better system where the compositor thread needs to read it and the Lua thread needs to write to it and the compositor only reads from it once the Lua thread writes to it and then the Lua thread can't touch it until it's read from...maybe?
So you could do it that way which remove all the locks, but I think a lot of it comes down to how expensive such an operation is too. The entire bar isn't going to change often, only small things like e.g the time.
But yeah that's step 2. Step 1 is doing this in wlroots, which will be slightly more involved than wlc.

and then the Lua thread can't touch it until it's read from...maybe?

Problem is, the Lua code has direct access to the cairo_surface_t* and doesn't believe in synchronisation... Wrapping a lock around all places that could run Lua code brings us back to "older times" and doesn't work anymore since Lua can directly register callbacks with the GLib main loop thanks to LGI.

Oh right I forgot about that check... And yes you're right, I didn't consider Lua being able to modify it.
Whelp, looks like I'll just copy the whole buffer each time then. Not a massive deal I hope, but it is a shame.


Additional rounding patch: round element widths before checking width parity

We forgot to round the element widths before checking their width parity (since elements' widths are usually not always integers)
https://codepen.io/anon/pen/aQVVwO

@FezVrasta any reason this wasn't merged before 1.14.6? All variation placements are properly rounded in 1.14.6, but without this patch, the centering can sometimes be off due to decimal width/height because the parity check doesn't work.

Sorry I forgot about this


Datepicker Appear Buggy

I think it's a little bit buggy when I open datepicker, there's a blue border, but when I click on another area it will be disappear.

Please recreate this issue in a codepen so we can confirm the issue

Here I wrote on jsfiddle, but a little bit messy.
http://jsfiddle.net/rizkiandrianto/n910uLjs/1/

Your date picker has lots of custom  styling which may be causing this. Even so, I did not see the big you described

I am also getting this issue. Using ember-cli-materialize though, not simple to re-recate.

But I also got this issue even when I disable the custom style for calendar (look at the picture) @Dogfalo

I also have this same issue when put the datepicker with container option

same here

I have the exact same problem, I've been trying to figure it our the whole day. What framework are you using, I'm on Rails and I'm using the Materialize-Sass gem. How about you guys?

@Dogfalo It is a little bit annoying when the calendar repop up back when i switch back and forth workspaces even though i have closed them before I switch. I would rather argue it as a bug rather than a feature. Hope to solve it asap. Thanks!

@kimyu92 after seeing the documentation page for the underlying datepicker javascript library; pickadate, it looks like the issue is with the library not with the materialize-css styling. You can see the issue with the blue line and the auto-popup happening right there on the documentation page. I will see the issues there and possibly link the solutions here.

this issue is because of outline of some container div so i solved it by giving "outline:none" to parent.

@JimishF thank you so much for the fix, it works :+1:


charset: fix Encoding.Encode() and add some tests

What problem does this PR solve?
Required by https://github.com/pingcap/tidb/pull/27875
What is changed and how it works?

Make FindNextCharacterLength only be used in the decoding process.
Add some test for Encoding.

Check List
Tests

Unit test
Integration test

Code changes
NA
Side effects
NA
Related changes
NA

This PR should be merged together with pingcap/tidb#27875.

/merge


LPE Variance Dependent Publication

LPE was relying on timeout (of last measurement with good stats) to govern when it should publish its estimates of position. However, this didn't work well for temporary errors in sensor stats that are resolved. For instance, #4909.
To handle this. I am making the timeouts be the time since a last valid measurement (not necessarily with good stats, such as EPH). However, the publication is now dependent on the estimator estimate of the state precision using the variance. This I hope will resolve #4909 but I still have to test it.

Here is a plot of the related standard deviations that I"m using to determine if data is valid:

This! This should fix the last open issue we found with our test flights here.

@jgoppert Any chance of getting a test flight in today? We will be out flying tomorrow. @tumbili FYI

@jgoppert Have you considered adding another hysteresis at 2x the threshold? I think we need that in addition. Once you're in the air you really want to continue GPS control even if the accuracy is bad.
That's how INAV is doing it and what works really reliably in practice. Not using a hysteresis is just really asking for fly-aways.

Note that the hysteresis cannot be replaced with the variance based approach, because the concept behind the hysteresis is to accept a higher noise ratio once airborne, while this PR only handles transients.
The estimator as it stands here would give up position control entirely even if it had reasonably useful GPS measurements.

Have done a lot of test flights of this, working on tuning process noise. Here is the result from the iris:

qav-r (baro only): http://logs.uaventure.com/view/RT5WXHEKKaeDWSPddsifLZ
iris: http://logs.uaventure.com/view/xzxfKgZj7Eh3BNScHaCzum
I had to reduce the z axis process noise so that the baro only flight was smooth enough. I also had to increase the xy axis process noise so that the estimate didn't diverge, but it is working for both vehicles now.

Here are some more flight test results that I just received, note here that the bias estimation blows up, need to investigate further:
F330 LPE:
http://logs.uaventure.com/view/Lb2EyY2yyZNZQxgYb5nkVU
F330 INAV:
http://logs.uaventure.com/view/pWcMPLtZB5v7JPjZKCEHmR

Here is a plot of the bias estimation with a 3dr iris with the same exact firmware, I have no idea how they could be so different @LorenzMeier any ideas?

@LorenzMeier  Added 4th order integration scheme and also lowpass filter on estimator outputs, default cut frequency is 10 hz. Here is a flight log with my iris.
http://logs.uaventure.com/view/ik78ZNXubcwjywHNenkwqQ

More plots:

Here is a plot of the filtering at 10 Hz, it gets even smoother at 5 Hz, but some degraded performance with high speed spinning, bias drifts off.
10 Hz (only cuts out very rapid changes, but little phase lag)

5 Hz (too much phase lag, but very smooth)

What I dislike about this strategy is that you're now low passing the accel predictions as well, which makes us loose phase margin. Just distributing position updates would delay the corrections, but not the overall estimate and prediction.
So it doesn't sound like this is a good choice on the conceptional level - is there a particular reason you went into this direction rather than smoothing the update step?

I think you are talking about the velocity publication to attitude_estimator_q, correct? With the low pass cut frequency at 10 hz, I would argue that it is likely more accurate to have the low pass filter on, if you look at what attitude_estimator_q is doing and the plot above:
_pos_acc = _q.conjugate_inversed((vel - _vel_prev) / vel_dt);

For the sudden jumps due to the correction, without a low pass filter, this would cause large acceleration spikes to go to attitude_estimator_q. This really should have a low pass filter on it anyways. When I tested bias wind up by flying full yaw and full forward stick for 10 seconds, it doesn't cause an issue at 10 Hz.
Also, when I started to implement the distribution of correction term, I didn't see how it was significantly different from using a low pass filter. If you calculate at t=0 that gps wants to correct 1 m north, then if you distribute that over the next 10 steps (assuming that we are running at 100 hz, that would mean you would get a 10 cm step at each update (but every step that you don't apply the full correction you are introducing lag), that would also influence the velocity through the correction and also through gps velocity update distribution if you went that route. The low pass filter, on the other hand, would approach the 1m correction as an exponential as you see in the plots, but the behavior is still similar to the distributed correction.
Also, this distributed correction approach seemed like a nightmare to implement since I have 4 different position estimate sources and I would have to do this for everything to be consistent.  Implementing the low pass filter was much cleaner and if you look internally the low pass filter doesn't modify the internal estimator states at all, it is just on the output to the rest of the system. Also for each publication I have the option of publishing the raw state or the low pass state, which might be helpful. The raw state and low pass state are both being logged as well since the raw state is sent to the estimator status message.

@tumbili  @LorenzMeier ekf2 is also low pass filtering if I'm understanding the code correctly: https://github.com/PX4/ecl/blob/master/EKF/ekf.cpp#L780
The gains here are just the low pass filtering constant. It is not applying the full correction, but a correction proportional to the magnitude of the error, so it is a low pass filter unless I'm missing something.

Within attitude_estimator_q I disabled the gyro bias estimation during high speed turns, this works very well. Here is a video of me trying to wind up the gyro bias, and you can see the position is rock solid after I release the stick.
video:
https://www.youtube.com/watch?v=4HA6X7V2gXs
log:
http://logs.uaventure.com/view/vJhZtKxeQNERoTyKbgZHsX

From the log you can see that the smoothing is working very well at 5 Hz and that the lag relative to the velocity dynamics is negligible:

Going to fly on qav-r so I get the full range of vehicle natural frequencies and make sure it works.

QAV-R flies great. @LorenzMeier I can confirm the baro is messed up on v4 boards on master. It worked fine on v2 boards if that helps. I just set baro noise to 300 m and it actually worked with just GPS.
QAV-R position hold without baro:
http://logs.uaventure.com/view/aALFJDMw6r6dEivXc488YQ
Video:
https://www.youtube.com/watch?v=DgPkecUOjFI

What does the baro signal look like on fmu-v2? Significantly lower noise?
On Wed, Jun 29, 2016 at 12:18 PM James Goppert<EMAIL_ADDRESS>wrote:

QAV-R flies great. @LorenzMeier https://github.com/LorenzMeier I can
confirm the baro is messed up on v4 boards on master. It worked fine on v2
boards if that helps. I just set baro noise to 300 m and it actually worked
with just GPS.
QAV-R position hold without baro:
http://logs.uaventure.com/view/aALFJDMw6r6dEivXc488YQ
Video:
https://www.youtube.com/watch?v=DgPkecUOjFI
[image: image]
https://cloud.githubusercontent.com/assets/473772/16463532/31266e7e-3e04-11e6-86f8-9c9b2aed3466.png
[image: image]
https://cloud.githubusercontent.com/assets/473772/16463579/6448cb30-3e04-11e6-9f1a-6d620c1a8bd8.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PX4/Firmware/pull/4914#issuecomment-229442952, or mute
the thread
https://github.com/notifications/unsubscribe/ACMZPYhdxxGl5PeCRz02e7MLHzcHZqdJks5qQrcMgaJpZM4I-rq5
.

@kd0aij
Iris (v2):
{'SENS_BaroAlt_dt': 0.094999825024302181,
'SENS_BaroAlt_mean':<PHONE_NUMBER>4879203,
'SENS_BaroAlt_noise_power': 0.14919326482628734,
'SENS_BaroAlt_stddev': 1.2531792815762062,
'SENS_BaroAlt_variance': 1.5704583117718562}

qavr (v4):
{'SENS_BaroAlt_dt': 0.071060881566904627,
'SENS_BaroAlt_mean':<PHONE_NUMBER>6413857,
'SENS_BaroAlt_noise_power': 0.10695588502978866,
'SENS_BaroAlt_stddev': 1.2268375142913472,
'SENS_BaroAlt_variance': 1.5051302864725717}

@jgoppert So there's actually less noise with pixracer...
I guess my Skype messages got lost, but I've independently verified that turning off acceleration compensation (the way Bill P. does in Matrixpilot; and imitated by Cleanflight) eliminates the errors due to flying coordinated turns. I completely disabled acceleration compensation for my test to show that GPS should also not be necessary.

The pixracer has more baro noise, but the baro is messed up on master, so not sure what we can tell from that.
If you are suggesting we don't need GPS for alt, that is true. This PR includes a fix for attitude_estimator_q that stops estimating gyro bias during fast turns, this solves a lot of issues with high performance flight.

@LorenzMeier @tumbili  are we ready to merge this? I'm happy with it.

I meant that the GPS-based acceleration compensation in attitude_estimator_q is not necessary.
And didn't you show less baro noise power for v4 than v2 in your comment above?

@kd0aij Ah, ok. That is good to know. It would be interesting to see if the gyro bias fix help you as well.
I kept repasting the analysis, I tried to find a section of stable hover for both, but currently the qavr(with pixracer) has twice the noise as the iris (with pixhawk)

Baro works fine on master for EKF2. Could you be a bit more specific what part of it is messed up? Variance? Update Rate?

Do you see the 8m spike in the plot above?

Could have been a bit due to mounting, had foam over baro port bUT not sure it was in place, can try again later.

Also variance is larger.

@jgoppert I was just looking at the noise stats; but spikes would be expected if you didn't have a light shield over the baro. I don't remember clearly, but I thought we demonstrated reduced noise compared to v2 after we moved the baro over to the FRAM SPI bus. OTOH, the ALTCTL surges I was seeing during initial testing could have been due to large noise spikes, but I don't recall finding anything wrong with the baro data from those runs.

I had electrical tape wrapped it around it before and removed it when messing with gps so that might be it.

Added subscription throttling on all topics, and really saved a lot of cpu. It took me awhile to track that down, but it flies well, going to try to get some flight videos and logs tomorrow.
Here are some flight log comparisons. The main difference in the missions is that I set the max takeoff altitude to 3 for LPE at the end, forgout about that. Hopefully will get some better comparisons tomorrow.

Still the logging is dropping out at times, I would like to resolve that.

Comparison is awesome already. Looks like we should put in some decent flight testing now.

@LorenzMeier I think we should go ahead and merge this, so people can test it on master, what do you think?


Slayer requirements are not shown for many crafting recipes

I noticed that for many slayer items, the crafting recipe does not show its slayer requirement.
For some of these items, such as REVENANT_SWORD, the slayer_req field is set, but not crafttext.
For others, like REVENANT_LEGGINGS, crafttext is set but not slayer_req.
For others, like WARDEN_HEMET, both are set.
slayer_req present but crafttext empty or missing appears to be the most common case.  It includes the droplet wisp items, tarantula armor, and the voidling minion, to name a few.
I'm willing to go through and standardize it, but which field should be the canonical source of slayer requirement info?  I think a good solution would be slayer_req, in addition to a change to the mod to autogenerate the craft text if slayer_req exists, is valid, and no crafttext is specified.

I noticed that for many slayer items, the crafting recipe does not show its slayer requirement. For some of these items, such as REVENANT_SWORD, the slayer_req field is set, but not crafttext. For others, like REVENANT_LEGGINGS, crafttext is set but not slayer_req. For others, like WARDEN_HEMET, both are set.
slayer_req present but crafttext empty or missing appears to be the most common case. It includes the droplet wisp items, tarantula armor, and the voidling minion, to name a few.
I'm willing to go through and standardize it, but which field should be the canonical source of slayer requirement info? I think a good solution would be slayer_req, in addition to a change to the mod to autogenerate the craft text if slayer_req exists, is valid, and no crafttext is specified.

Hey, thanks for the report. Regarding your question about which field should be used: at the moment, only the crafttext field is used in our mod, although slayer_req is being using by third-party sites (e.g., Cofl) for easier parsing. So, for now, both fields should be filled.


ruleselector not obeying labels and pulling in all configmaps

What did you do?
Had an issue in prometheus where rules could not be viewed from the web UI.
Killed one of the prometheu-k8s pods to see if reloading would work.
Pod failed to start (crashlooping) because of config.
Investigated and found that every configmap in that namespace was being pulled in as a 'rule'.
Other configmaps include grafana dashboard files (json) etc, so loading was failing.
What did you expect to see?
I expected to see only the rules files pulled into the shared volume of the pod.
Prometheus Deployment:
apiVersion: monitoring.coreos.com/v1
kind: Prometheus
metadata:
  labels:
    prometheus: k8s
  name: k8s
  namespace: monitoring
spec:
  alerting:
    alertmanagers:
    - name: alertmanager-main
      namespace: monitoring
      port: web
  externalUrl: https://something.awesome.com/prometheus
  replicas: 2
  resources:
    requests:
      memory: 1Gi
  retention: 168h
  ruleSelector:
    prometheus: k8s
    role: prometheus-rulefiles
  serviceAccountName: prometheus-k8s
  serviceMonitorSelector:
    matchExpressions:
    - key: k8s-app
      operator: Exists
  storage:
    volumeClaimTemplate:
      metadata:
        annotations:
          annotation1: prometheus
      spec:
        resources:
          requests:
            storage: 40Gi
        storageClassName: ssd
  version: v2.0.0

Configmap:
apiVersion: v1
data:
  alertmanager.rules: ""
  custom.rules: ""
  ....
kind: ConfigMap
metadata:
  labels:
    prometheus: k8s
    role: prometheus-rulefiles
  name: prometheus-k8s-rules
  namespace: monitoring

What did you see instead? Under which circumstances?
Instead what I seen was that I had the following configmaps in the monitoring namespace:
NAME                                         DATA      AGE
grafana-dashboard-definitions-0              10        10d
grafana-dashboard-definitions-1              2         4h
grafana-dashboards                           1         28d
grafana-datasources                          1         10d
ingress-controller-leader-nginx-monitoring   0         10d
prometheus-k8s-rules                         9         40m

Upon looking in the prometheus-config-reloader, I seen I have as many rules-X directories as configmaps . and in them... were the contents of all said configmaps:
/etc/prometheus/rules $ ls -ltr
total 24
drwxr-sr-x    2 1000     2000          4096 Feb 23 17:57 rules-4
drwxr-sr-x    2 1000     2000          4096 Feb 23 17:57 rules-3
drwxr-sr-x    2 1000     2000          4096 Feb 23 17:57 rules-2
drwxr-sr-x    2 1000     2000          4096 Feb 23 17:57 rules-1
drwxr-sr-x    2 1000     2000          4096 Feb 23 17:57 rules-0
drwxr-sr-x    2 1000     2000          4096 Feb 23 17:57 rules-5
/etc/prometheus/rules $ ls -ltr rules-5/
total 44
-rw-r--r--    1 1000     2000           366 Feb 23 17:57 prometheus.rules
-rw-r--r--    1 1000     2000          1980 Feb 23 17:57 node.rules
-rw-r--r--    1 1000     2000          6332 Feb 23 17:57 kubernetes.rules
-rw-r--r--    1 1000     2000          1854 Feb 23 17:57 kubelet.rules
-rw-r--r--    1 1000     2000           805 Feb 23 17:57 kube-apiserver.rules
-rw-r--r--    1 1000     2000          1787 Feb 23 17:57 general.rules
-rw-r--r--    1 1000     2000          4853 Feb 23 17:57 etcd3.rules
-rw-r--r--    1 1000     2000          1801 Feb 23 17:57 custom.rules
-rw-r--r--    1 1000     2000          1358 Feb 23 17:57 alertmanager.rules

/etc/prometheus/rules $ ls -ltr rules-[1-4]
rules-4:
total 0

rules-3:
total 4
-rw-r--r--    1 1000     2000           159 Feb 23 17:57 prometheus.yaml

rules-2:
total 4
-rw-r--r--    1 1000     2000           215 Feb 23 17:57 dashboards.yaml

rules-1:
total 68
-rw-r--r--    1 1000     2000         51074 Feb 23 17:57 prometheus-dashboard.json
-rw-r--r--    1 1000     2000         12876 Feb 23 17:57 elixir-dashboard.json

This resulted in the prometheus configuration calling all these files:
rule_files:
- /etc/prometheus/rules/rules-0/*
- /etc/prometheus/rules/rules-1/*
- /etc/prometheus/rules/rules-2/*
- /etc/prometheus/rules/rules-3/*
- /etc/prometheus/rules/rules-4/*
- /etc/prometheus/rules/rules-5/*

I had tried manually editing the prometheus-k8s secret object after I discovered the value of the configmaps.json within. However even if the edit is accepted, it just seems to stay as it was previously.
I tried deleting secret and prometheus operator deployment, but it always returned to the same scenario.
My only way to get the seconds prometheus pod running was to manually shell into both prometheus-config-reloader pod and manually remove files that should not have been there under:
/etc/prometheus/rules/rules-X directories. This won't be permanent as if the pods die or reschedule, then the entire configmap stuff is still held within the secret.
Environment
GKE - production cluster.
Staging environment has near identical config (size and disks vary etc) but I have not seen this issue there.
Entire kube-prometheus stack (slightly customised) deployed into monitoring namespace.

Kubernetes version information:
Client Version: v1.8.6
Server Version: v1.7.12-gke.1

Nodes 1.7.6 and 1.7.11-gke1

Kubernetes cluster kind:
GKE - prometheus

Manifests:
Please see above description. All manifests are based on those in kube-prometheus.

ts=2018-02-23T17:57:38Z caller=main.go:204 component=volume-watcher msg="Updating rule files..."
ts=2018-02-23T17:57:40Z caller=main.go:209 component=volume-watcher msg="Rule files updated."
ts=2018-02-23T17:57:40Z caller=main.go:212 component=volume-watcher msg="Reloading Prometheus..."
ts=2018-02-23T17:57:40Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=352.163896ms
ts=2018-02-23T17:57:41Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=787.814611ms
ts=2018-02-23T17:57:42Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=1.47376298s
ts=2018-02-23T17:57:44Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=1.55973565s
ts=2018-02-23T17:57:46Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=2.896316082s
ts=2018-02-23T17:57:49Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=4.787193274s
ts=2018-02-23T17:57:54Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=6.324759399s
ts=2018-02-23T17:58:00Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=11.100763399s
ts=2018-02-23T17:58:12Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=8.473107892s
ts=2018-02-23T17:58:21Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=12.022517606s
ts=2018-02-23T17:58:33Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=35.677861325s
ts=2018-02-23T17:59:09Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=1m0.066682793s
ts=2018-02-23T18:00:10Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=45.181130263s
ts=2018-02-23T18:00:55Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=1m23.787724581s
ts=2018-02-23T18:02:19Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=39.638838397s
ts=2018-02-23T18:02:59Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=1m12.516138868s
ts=2018-02-23T18:04:12Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=1m22.633140392s
ts=2018-02-23T18:05:35Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=58.82090375s
ts=2018-02-23T18:06:34Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=54.700158804s
ts=2018-02-23T18:07:29Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=1m25.742281412s
ts=2018-02-23T18:08:55Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=40.28604965s
ts=2018-02-23T18:09:36Z caller=main.go:214 component=volume-watcher msg="Reloading Prometheus temporarily failed." err="Post http://localhost:9090/-/reload: dial tcp [::1]:9090: getsockopt: connection refused" next-retry=1m0.492895063s
ts=2018-02-23T18:10:39Z caller=main.go:219 component=volume-watcher msg="Prometheus successfully reloaded."

Not available because of the crashloops (it was on restart number 22)
Other useful things
The configmaps.json stil currently holds reference to all configmaps in the namespace:
{"items":[{"key":"monitoring/grafana-dashboard-definitions-0","checksum":"10687070fe3bdafe75ce84ecffe07124ae4fc707961eadbfa4a8f36d3af3b99a"},{"key":"monitoring/grafana-dashboard-definitions-1","checksum":"5b48e519850dd66a4ba379507b048224b5a7e804653333bc37593e53920fd525"},{"key":"monitoring/grafana-dashboards","checksum":"9c3522a9f51f11b520e7ed209104f1c5eb3b1f7aad878874264a4a3bc16fd457"},{"key":"monitoring/grafana-datasources","checksum":"2651109af43c5d433332d1e9402955591aefc66f21546040d08a1979651f70bb"},{"key":"monitoring/ingress-controller-leader-nginx-monitoring","checksum":"ca3d163bab055381827226140568f3bef7eaac187cebd76878e0b63e9e442356"},{"key":"monitoring/prometheus-k8s-rules","checksum":"da8715e3af6b026475d5698bd007933facb6ca30bfb9cc5bbc87fc716a04d3c3"}]}

eg. it matches the configmaps described earlier on.

Is there any way to override the operator and set the configmaps.json and prometheus.yaml keys in the prometheus-k8s secret?
Or how can I enforce / ensure that prometheus(operator?) respects the ruleSelector set to only pickup the correct configmap?

Thanks for the elaborate report, very useful!
I think this is because the ruleSelector should be a full selector, not a map of labels. Could you try adapting it to be like this?
  ruleSelector:
    matchLabels:
      prometheus: k8s
      role: prometheus-rulefiles

I believe what we are seeing is that it gets unmarshaled into an "empty" selector, which by default selects everything in Kubernetes.

@brancz - thank you for your suggestion. Indeed this was something I missed in translating the yaml document into a python dictionary. I didn't see it in staging as that must have been applied from the original yaml file.
Just out of interest, is this intended behaviour? Defaulting to mounting all configmaps (in namespace)?
Perhaps its something that could be a warning in the application of the resource? Or possibly log which configmaps the operator will load for a given prometheus specification.

An empty selector selecting everything is just how Kubernetes works, I don't think we should change that for our case.
I think the big thing to take away here is that validations saying that the fields that you had do not exist in a type Selector. That way the object would not have been create-able, and therefore the error couldn't have happened in the first place.


k3s can not run pods on CentOS 7.9

Environmental Info:
K3s Version:

k3s version v1.24.3+k3s1 (990ba0e8)
go version go1.18.1

Node(s) CPU architecture, OS, and Version:

single node with CentOS 7.9
Linux localhost.localdomain 3.10.0-1160.el7.x86_64 #1 SMP Mon Oct 19 16:18:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Cluster Configuration:

1 server
Describe the bug:

Following the installation guide on the rancher website, I created a single node cluster setup. But after running the install.sh, the calico pod could not be created and logged:
kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: open /proc/sys/net/ipv4/ip_unprivileged_port_start: no such file or directory: unknown

Steps To Reproduce:

install k3s using the air-gap way
get the pods status

Expected behavior:

K3s can start successfully.
Actual behavior:

Calico pod could not be created.
Additional context / logs:

k3s turned on unprivileged ports and ICMP by default in this PR: https://github.com/k3s-io/k3s/pull/5538 . It seems that containerd has some problems on this kernel version (maybe unprivileged ports are not supported on it) and these two unprivileged flags are disabled in containerd by default. After adding a config template to /var/lib/rancher/k3s/agent/etc/containerd/config.toml.tmpl and turning off these two flags, pods were created successfully.
Backporting

[ ] Needs backporting to older releases

just encounter this issue, it help me figure out. thanks

This will be fixed in our next release.

Validated on master branch using commit id 30fc909581ba8395da0860c22830d9db3913f7b1
Environment Details
Infrastructure
Cloud EC2 instance
Node(s) CPU architecture, OS, and Version:
Ubuntu 20.04
Cluster Configuration:
Single node
Config.yaml:
$ cat config,yaml
selinux: true

$ sudo mkdir -p /etc/rancher/k3s && sudo cp config.yaml /etc/rancher/k3s

Steps to reproduce the issue  and validate the fix

Copy config.yaml
Install k3s

To reproduce:
[centos@ip-172-31-4-213 ~]$ curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=v1.24.3+k3s1 sh -
[centos@ip-172-31-4-213 ~]$ kubectl get pods -A -w
NAMESPACE     NAME                                      READY   STATUS              RESTARTS   AGE
kube-system   helm-install-traefik-crd-tml8t            0/1     ContainerCreating   0          6s
kube-system   helm-install-traefik-6z599                0/1     ContainerCreating   0          6s
kube-system   coredns-b96499967-pnx4j                   0/1     ContainerCreating   0          5s
kube-system   metrics-server-668d979685-j2qbf           0/1     ContainerCreating   0          5s
kube-system   local-path-provisioner-7b7dc8d6f5-mb87c   0/1     ContainerCreating   0          5s

From the logs:

Aug 11 22:48:55 ip-172-31-4-213.us-east-2.compute.internal k3s[5925]: E0811 22:48:55.129876    5925 kuberuntime_sandbox.go:70] "Failed to create sandbox for pod" err="rpc error: code = Unknown desc = failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: open /proc/sys/net/ipv4/ip_unprivileged_port_start: no such file or directory: unknown" pod="kube-system/local-path-provisioner-7b7dc8d6f5-mb87c"

To validate:
[centos@ip-172-31-4-213 ~]$curl -sfL https://get.k3s.io | INSTALL_K3S_COMMIT=30fc909581ba8395da0860c22830d9db3913f7b1 sh -s - --selinux
[centos@ip-172-31-4-213 ~]$ cat /etc/redhat-release
CentOS Linux release 7.9.2009 (Core)
[centos@ip-172-31-4-213 ~]$ k3s -v
k3s version v1.24.3+k3s-30fc9095 (30fc9095)
go version go1.18.1
[centos@ip-172-31-4-213 ~]$ kubectl get nodes
NAME                                         STATUS   ROLES                  AGE   VERSION
ip-172-31-4-213.us-east-2.compute.internal   Ready    control-plane,master   71s   v1.24.3+k3s-30fc9095
[centos@ip-172-31-4-213 ~]$ kubectl get pods -A
NAMESPACE     NAME                                      READY   STATUS      RESTARTS   AGE
kube-system   local-path-provisioner-7b7dc8d6f5-g7jrz   1/1     Running     0          62s
kube-system   coredns-b96499967-khx2p                   1/1     Running     0          62s
kube-system   helm-install-traefik-crd-v7hbg            0/1     Completed   0          62s
kube-system   svclb-traefik-70288344-fxxhb              2/2     Running     0          46s
kube-system   helm-install-traefik-8kr6q                0/1     Completed   1          62s
kube-system   metrics-server-668d979685-ln5m4           1/1     Running     0          62s
kube-system   traefik-7cd4fcff68-htb2r                  1/1     Running     0          47s
[centos@ip-172-31-4-213 ~]$


Call to String#sum is causing weird results

Amnesia kept giving me output like this, which didn't feel right (note I have tweaked the views slightly, but hadn't changed the non-view code prior):

So I dove into the code and made this change
And now the results look more like this:

Which feels much more correct. String#sum doesn't seem to do anything helpful in this context, so I'm not sure why it was being included. Please let me know if I've overlooked something! Otherwise I'll be happy to make a pull request.

resolved with #11. can be closed.


Docs for tenant specific environments

Adds docs that should be sufficient for everyone
to start using their own tenants for development
and stop using the jenkins tenant.

@anshprat I went ahead and added some tenant specific docs to the README, not sure how you want to merge these with the ones you have on the wiki. please review!

looks good. will point wiki to this page till we ve folks up and running/consolidated it all. TODO - script it all up.


大佬 有兴趣 来一个 chat2claude 么？ 逆向 claude 网页变成 api

如题
claude 在代码方面能力强于 gpt

可以用付费账户
On Mon, Dec 23, 2024 at 11:44 PM LanQian @.***> wrote:

claude用不了几次啊
—
Reply to this email directly, view it on GitHub
https://github.com/lanqian528/chat2api/issues/219#issuecomment-2559929177,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BEN2BBDJHTANDHVRVFBF4FL2HAVXPAVCNFSM6AAAAABT2FGVYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJZHEZDSMJXG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

有fuclaude


ERROR 247

Describe the bug
Then start first migration on a docker production server instalation
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Apply migrations
Screenshots

Deployment Method
Docker
Version Information
Latest

This was because my VPS didn't have enough power=)


Mail2event

Create a vevent from email content to support services that manage calendars with email endpoints.

Subject -> summary
Body -> description
Parse description for date
Attachments

Some online services use predictable mail formatting to make it easier for precise parsing

Microformats are good candidate for email enrichment


Redrew doctopus holding docs

Doctopus now holds docs, rather than appearing to float. Recolored docs to pop a little more/blend in less with the figure.
1000px PNG + multilayer SVG

How about we add a new folder like "Compositions," for a place to put such things?

I'll move this over and add this to the list.
FWIW, the fact that the doctopus wasn't "holding" the docs has bugged my ND brain :)

@ryanmacklin , just as a reminder, can you change your commit so that you add your icons in addition to the existing one rather than replacing one? Was that what we agreed? Can't remember. :)


We're a repo now, no longer a fork attached to rails/acts_as_list

Yay!

Good 👍

Haha! No more embarrassing accedental PR's on rails/acts_as_list! :) Thanks @swanandp for sorting this out. Closes #224.


Missing pause button?

Is your feature request related to a problem? Please describe.
It's not a problem we just need pause and play button for skills just like konduits features. I was only trying to take break to eat my lunch and want my grind to stay. But couldn't.
Describe the solution you'd like
A play and a pause button to stop calcuating.
Describe alternatives you've considered
N/A
Additional context

I've got an implementation in progress that also handles mine too #3113
Last is refining some display niceties.