Setup/GitHub actions tests

What is the change?
added coverage tests with jest in local with command yarn test:ci
Is it bug?
No
*Dev Tested?

[ x ] Yes

Before / After Change Screenshots

@isVivek99 build is failing

https://jasonraimondi.com/posts/testing-a-typescript-react-app-using-ts-jest-not-create-react-app/


Fix webgl CMakeLists.txt setup

It looks like #7 didn't update CMakeLists.txt properly - defines
specified with -D have to be added as compile definitions.
Additionally, -O3 must be specified redundantly as a compile option and
as a link option - compile option makes .wasm bits small & fast, and
link option enables JS minifier.
After this fix CMake build results in minimal js/wasm files as well.

Could this pull request be reviewed? Improvements to the emscripten build of the transcoder (#26) are blocked on it. Thanks!

Ok, I’ll merge this in early today.


Adding note about disabledFeatures static property

12130

 Quality gate: NA
Details

 Quality gate: NA
Details

 Quality gate: NA
Details

 Quality gate: NA
Details

 Quality gate: NA
Details


To transformation should be able to write nulls

from REPL:
> data = "#datatype,string,long,string,string,string,dateTime:RFC3339,double
#group,false,false,true,true,true,false,false
#default,_result,,,,,,
,result,table,_measurement,_field,t0,_time,_value
,,0,m1,f1,server01,2018-12-19T22:13:30Z,-61.68790887989735
,,0,m1,f1,server01,2018-12-19T22:13:40Z,-6.3173755351186465
,,0,m1,f1,server01,2018-12-19T22:13:50Z,
,,0,m1,f1,server01,2018-12-19T22:14:00Z,114.285955884979
,,0,m1,f1,server01,2018-12-19T22:14:10Z,16.140262630578995
,,0,m1,f1,server01,2018-12-19T22:14:20Z,29.50336437998469
,,1,m1,f1,server02,2018-12-19T22:13:30Z,
,,1,m1,f1,server02,2018-12-19T22:13:40Z,49.460104214779086
,,1,m1,f1,server02,2018-12-19T22:13:50Z,-36.564150808873954
,,1,m1,f1,server02,2018-12-19T22:14:00Z,34.319039251798635
,,1,m1,f1,server02,2018-12-19T22:14:10Z,
,,1,m1,f1,server02,2018-12-19T22:14:20Z,41.91029522104053"
> import "csv"
> csv.from(csv: data) |> to(bucket:"test", org:"root")
Error: point without fields is unsupported

The error gets returned here: https://github.com/influxdata/influxdb/blob/582ed6834c4e7c465f3b02f742f3977eed467d7c/models/points.go#L1382.
When to is writing points: https://github.com/influxdata/influxdb/blob/d18c6e5ffe8d2d025875a4cb3d21c82d88751ab3/query/stdlib/influxdata/influxdb/to.go#L591

The storage engine does not have a way of writing null values. We can make the to function not error on nulls but it will only be able to ignore them, not write them.
Does that sound like an reasonable solution?

Yeah, I see your point.
The problem emerges when we are running e2e tests for flux.
We use to to store input data and then we extract it with a from. If that input data doesn't have nulls, then the expected result would be different.
We should somehow add a map transformation after from that adds nulls (however, we cannot express it in flux right now) or keep skipping tests that contains nulls in input data.


Fibaro devices not always correctly shown

See threat I created here: https://github.com/home-assistant/core/issues/51844
I use ZwaveJS integration in Homeassistant (core-2021.6.4) on a raspberry PI 4 with an AEONlabs USB zwave stick (gen5). I have the strange behaviour that some Fibaro devices are shown correctly and others not, like in the example below

All three have the same type of Fibaro plug, but only one is showing correctly Fibaro. I have done reconfigure, remove nodes and adding again, but no luck.
Here the log files of the integration within Home Assistant:
zwave_js_dump.log

Please use the bug report template and fill it out completely.


Build failure with Nix

I maintain the Nixpkgs derivations/packages for nCAT and nDAX.
When trying to update the nCAT package from 0.1-20220505.0 to 0.1-20221007.0 (cf. https://github.com/illdefined/nixpkgs/blob/ncat/pkgs/applications/radio/flex-ncat/default.nix) I am experiencing a build failure:
this derivation will be built:
  /nix/store/z117xx19rd5dsp8dhj444v560229ldss-flex-ncat-0.1-20221007.0.drv
building '/nix/store/z117xx19rd5dsp8dhj444v560229ldss-flex-ncat-0.1-20221007.0.drv'...
unpacking sources
unpacking source archive /nix/store/xqj89s46g4lg89j7xb8y6r2qaz6zi3nl-source
source root is source
patching sources
configuring
building
Building subPackage .
internal/itoa
internal/goos
internal/nettrace
unicode/utf8
internal/goarch
internal/unsafeheader
internal/cpu
math/bits
internal/goexperiment
unicode
sync/atomic
runtime/internal/atomic
runtime/internal/syscall
internal/race
unicode/utf16
encoding
internal/abi
runtime/internal/math
runtime/internal/sys
internal/bytealg
math
runtime
internal/reflectlite
sync
internal/testlog
internal/singleflight
math/rand
runtime/cgo
errors
sort
io
internal/oserror
path
vendor/golang.org/x/net/dns/dnsmessage
strconv
syscall
strings
bytes
reflect
bufio
internal/syscall/unix
internal/syscall/execenv
time
context
internal/poll
io/fs
os
internal/fmtsort
encoding/binary
github.com/hb9fxq/flexlib-go/sdrobjects
encoding/base64
golang.org/x/sys/unixThe
github.com/hb9fxq/flexlib-go/vita
internal/godebug
io/ioutil
os/signal
fmt
internal/intern
net/netip
# golang.org/x/sys/unix
vendor/golang.org/x/sys/unix/syscall.go:83:16: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)
vendor/golang.org/x/sys/unix/syscall_linux.go:2255:9: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)
vendor/golang.org/x/sys/unix/syscall_unix.go:118:7: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)
vendor/golang.org/x/sys/unix/sysvshm_unix.go:33:7: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)
net
flag
encoding/json
github.com/rs/zerolog/internal/json
github.com/rs/zerolog
github.com/rs/zerolog/log
error: builder for '/nix/store/z117xx19rd5dsp8dhj444v560229ldss-flex-ncat-0.1-20221007.0.drv' failed with exit code 1;

This build is performed with Go 1.18.6 and these build scripts: https://github.com/illdefined/nixpkgs/blob/ncat/pkgs/build-support/go/module.nix
The issue appears to be related to a change in the compiler https://go-review.googlesource.com/c/go/+/324369 that makes the use of unsafe.Slice an error when compatibility with Go 1.16 or earlier was requested.
Being unfamiliar with Go and its native build environment, I am unsure how to address this problem. I can’t tell if it is something that needs fixing upstream and I would appreciate any help I can get. It also affects the build of nDAX in the same manner.

Thanks. Should be fixed in the latest release. I did the same for nDAX as well.

Thanks. Should be fixed in the latest release. I did the same for nDAX as well.

Thank you for the quick fix!


Replace argh library with fire library.

Fire is slightly more straightforward for minigo's usage
since everything can be passed directly to the fire.Fire()
rather than indirectly through argh.add_commands().
argparse usage is also hidden and doesn't need to be
imported separately and used as a proxy.

Looks good other than the one imported method.

/ok-to-test

It looks like the presubmit bots don't have the fire library installed. How can we update them?

I think if you add fire to requirements.txt, the docker image will pick up the changes.

I guess updating requirements.txt doesn't work if it's part of the same patch? I'll try pulling in the fire dependency into requirements.txt as a separate patch first.

Added fire to requirements.txt here: https://github.com/tensorflow/minigo/pull/449

/ok-to-test

/retest


There is no drfill branch

The README mentions a drfill branch, but I only see a master branch on GitHub.

Hey this is a WIP let us merge this in soon!

Just added it


Use WP_Filesystem methods

Instead of file_put_contents, file_get_contents, etc, WP_Filesystem methods should be used
Ref: https://codex.wordpress.org/Filesystem_API
Check following:

includes/plugins/timber-library/vendor/twig/twig/test/Twig/Tests/EnvironmentTest.php line 50
includes/plugins/timber-library/vendor/twig/twig/lib/Twig/Environment.php line 1281
includes/plugins/timber-library/vendor/twig/twig/lib/Twig/Test/IntegrationTestCase.php line 41
includes/plugins/timber-library/vendor/twig/twig/lib/Twig/Loader/Filesystem.php line 130
includes/plugins/timber-library/lib/timber-image-helper.php line 282

All come from the Timber plugin which is no longer embedded.


Enhancement: Add code-server 4.17.0 variants

Signed-off-by: The Oh Brothers Bot<EMAIL_ADDRESS>

Waiting for package to be on https://www.npmjs.com/package/code-server

Seems like package wasn't published because of CI bug https://github.com/coder/code-server/actions/runs/6280878223. Probably it will only be published on 4.17.1, in a few days.

4.17.1 in #105


New splash screen for onboarding

Can we please link to designs and scoping for this?

Removing from the roadmap until we have navigation in place @nishantmonu51


Quick fix to correct crashing upon parse error.

Looking into more elegant solution later

Also includes forgotten .gitignore files from private repo.


编译出错”unable to resolve action p3terx/debugger-action@master, repository not found“

您好，
安照您的教程，我几次编译都出现以下错误提示：
unable to resolve action p3terx/debugger-action@master, repository not found
请教怎么解决。感谢

Solved by forking the latest repository. Somrthing changed there.

Solved by forking the latest repository. Somrthing changed there.


Add continuous error output option to delta classify

Fixes #86

Hey @bcoltin , I've left a lot of the development comments in the code atm in case I need to make any changes (hence the pylint failure). If everything looks good I'll clean them up and commit a version to merge.
I separated out the refactoring of LabelPredictor._process_block() (which was a fairly substantial change) into commit ebde8e9 if you want to take a look at that.
The actual continuous error implementation itself is in the final commit 4cade2e. I did run into a little oddity that doesn't affect the functionality of the code itself but required me to add a numpy squeeze in just to handle the array dimension for the test cases. The extra dimension doesn't get added when running through wv images, but does when calling predict from the test cases. Do you have any insight into that?

Thanks @mvonpohle!


Cleaned up the types for validation. Added a base IValidator interfac…

…e that specifies the base interface for a regular or composite validator (validate or getErrorCount). Renamed the existing one to ISimpleValidator

Note, utilities will now require a minor version change.


Mac build throws an error message in Mac OS 11 - Big Sur 11.2.3

Description of the problem: When opening the application in Big Sur 11.2.3, a message pops up that states: "You can’t open the application “PicoToolkit” because it may be damaged or incomplete." - The app doesn't launch.

Oh no! Thanks for reporting the issue. Any chance you could try out an older release or two to see if they work? I suspect that it has to do with the GitHub actions automatic build system but I don't have a Mac to test it on. If you could try the original Mac update https://github.com/jordanfb/PicoCADToolKit/releases/tag/v0.3.1 which was actually built by someone manually on a Mac I would be really grateful. If that works then I suspect it’s the automatic build setup. If you wanted to you could try the https://github.com/jordanfb/PicoCADToolKit/releases/tag/v0.4 version to see if it works but I suspect it won’t. In the meantime I’ll poke around to see if I can figure out the issue on my end.
If this is particularly urgent for whatever reason you can always run the code yourself since it all works on OSX but that’s obviously much less useful than a nicely built application!

I checked and can confirm that the first version linked (the Mac release) works fine for me so if you want to use that version temporarily while I we figure this out that works.

Perfect, I'll use that build. Thanks for the help!

Alright! I think I fixed the issue with the release of v0.5, turns out what I thought was an application was just a folder that I had named .app... oops! The release also fixes a few issues with dark mode on OSX not showing the text on buttons. Once it's confirmed to work I'll close the issue.

The latest build is working for me & the dark mode fixes are most welcome! Thanks again for the great tool!


n_lfom_orifices function lfom_dict_test.py is not working

Here is the error:

There seems to be an issue with the n[i] = ... statement, but I could not figure out how to fix it. I don't see how this is invalid syntax.

There was a missing parenthesis on the line above which caused the error. Fixed now


feat: parsed post contains author

Codecov Report

Merging #86 (b82831b) into master (b3642ed) will increase coverage by 0.13%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #86      +/-   ##
==========================================
+ Coverage   89.09%   89.23%   +0.13%
==========================================
  Files          27       27
  Lines         642      650       +8
  Branches      107      108       +1
==========================================
+ Hits          572      580       +8
  Misses         70       70

Flag
Coverage Δ

unittests
89.23% <100.00%> (+0.13%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/command/post-manager/producer.ts
100.00% <100.00%> (ø)

src/command/qq/consumer-handler.ts
100.00% <100.00%> (ø)

src/services/rss/snowball/message.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


about code

thank you for nice work. I would greatly appreciate it if you could provide code examples that align with the functionality described in the paper.
❤

+1

Can you publish the code? thank you！

When will the code be released?

+1

any update on code release?


Anything with {id,type} should be recoverable by vault.get(..)

This is one of a few issues raised by experimenting with vault for this: https://tomcrane.github.io/scratch/cp/tree.html
In making that demo I found that some resources can be obtained by vault.get but others cannot. For example, this seems to be true for objects that are members of arrays, but not all arrays - it doesn't happen for Canvases. If an object is a member of an array, retrieving it via vault.get({id, type}) just returns the ref not the object. I'm having to walk up the tree, obtain the parent object, get the property whose value is the array, then re-find the object in that array.
Even if Vault doesn't do any special normalisation on a resource, I don't necessarily know that.

Since it will either de-reference it, or return what you passed it.

This wasn't all that intuitive - it took me a while to work out what was happening because I always got something back even if the ref isn't in Vault's store, so I assumed to had the full object.
On the way down the tree, this line never reduced the amount of information, because for calls where it would I had the full object in hand (e.g., as a property of an object I'm iterating over), it gave me back what I'd passed in if Vault has no entry for it:
iiifResource = vault.get(iiifResource);

https://github.com/tomcrane/scratch/blob/eded1f7314a6e0b3f3e1427fd41ab49eefb3a222/cp/tree.html#L159
But what is apparently the same call when clicking on a tree node always returns something - but for some things it's just the ref. So I had to test:
https://github.com/tomcrane/scratch/blob/eded1f7314a6e0b3f3e1427fd41ab49eefb3a222/cp/tree.html#L345

I think the fromRef() used to return null or similar if it could not find it in the Vault. If I remember, this broke sometimes when writing UIs for resources that you'd fetch - like Annotation Pages or Manifests. The UI might look like:
const page = vault.get(annoPageRef);

if (!vault.requestStatus(page.id)) {
  vault.load(page.id);
}

if (page.items) {
  // render thing..
}

So the value of page enhances over time from a ref (from the returned self) to the vault-returned object.


Added the unit tests for the getNetDevicesFromPci function

Signed-off-by: Abdallah Yasin<EMAIL_ADDRESS>

recheck

rebuild


🐞[Bug]: Adding of a 404-Error Page

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
To ensure a positive user experience, a custom 404 error page should be created and displayed when a user navigates to a non-existent or incorrect web address. This page should provide a friendly message and useful navigation links.
Expected behavior
Mentioned above.
Add ScreenShots
No response
What browsers are you seeing the problem on?
No response
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Thank you for creating this issue! 🎉 We'll look into it as soon as possible. In the meantime, please make sure to provide all the necessary details and context. If you have any questions or additional information, feel free to add them here. Your contributions are highly appreciated! 😊
You can also check our CONTRIBUTING.md for guidelines on contributing to this project.

I just wanted to let you know I don't need it now.


(GH-96) Check for presence of vmId file

Check for the presence of the vmId file once at the start of each test
execution.  If not present, then don't attempt to change the TEMP folder
location, or attempt image capture.  This should allow correct startup
of VM after a complete refresh of the system, including removal of VM.
Fixes #96

Going to need to look deeper at this. This certainly doesn't simplify things. What I suggested was create a special value that can be unique and use it instead of vmid.

edited above comment for readability.

Based on the conversation that we had, I didn't think that moving to another unique id was what was required, I thought it was a case of getting things working using the vmId.
From the testing that I did, the reason that this was failing was due to the fact it was attempting to access the vmId before the call to this:
var prepSuccess = _testService.prep();

Which sets up the new VM and adds the required files.  Once this is done, I think we can rely on it being there.


[BUG] 'sendMessage' not working properly

Error: Failed to send chat message. Request failed with status code 403
let tiktokLiveConnection = new WebcastPushConnection(targetUsername, {
    processInitialData: false,
    sessionId: sessionID
});
tiktokLiveConnection.on('chat', data => {
  comment = data.comment;

  log(chalk.bold(`${data.uniqueId}`, chalk.white(': '), chalk.green(`${comment}`)));

  // testing
  setTimeout(() => {
    tiktokLiveConnection.sendMessage(getRandomElement(messages)).catch(err => log(error(err)));
  }, 3000);
});

However, there was cases where it did actually work and I got a lot of messages sent in sequence...
There must be issue somewhere.
When I think about it, maybe the execution time needs to be synced or more cookie variables?

the same issue

same for me

I got the same issue

same here

Hey @DEMORALIZ3D , did you find anything around it? I am in the same quest!


Pitometer Score is not available in log nor dynatrace event

Describe the bug
A key capability of Pitometer is to come up with a total score, e.g: 50 out of 100 potential points. Right now this information is not available anywhere. Neither in the keptns bridge nor the Dynatrace Event.
In order to know WHY an artifact was promoted or not promoted I need to at least know the total score of Pitometer. I want to see it in both the log and as a property in the Dynatrace Info Event
To Reproduce
Run a build that either fails or gets promoted. Try to find the Pitometer score!
Expected behavior
See the score
Screenshots

The latest version of the bridge in Keptn 0.5.0 now shows the complete output of pitometer


[stable/chartmuseum] Allow using initContainer to set volume permissions

What this PR does / why we need it:
Some cloud providers, such as IBM cloud, require permissions to be set explicitly on persistent volumes. Using an initContainer that runs chown on the mounted volume is a common practice to do it.
Additional changes:

Use persistence.path variable instead of hard-coded /storage mount path

Special notes for your reviewer:

The initContainer configuration has been taken from stable/ghost chart.

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @yurrriq

/ok-to-test

/assign @jdolitsky

/lgtm


60m interval returning presplit values?

ticker = "AAPL"
stock = yf.Ticker(ticker)
data = stock.history(start=start_date, end=end_date, interval="60m").drop ["Dividends", "Stock Splits"], axis=1)

This returns incorrect open/closing/high values - these are presplit AAPL values, not post split.
Datetime,Open,High,Low,Close,Volume
2019-01-02 09:30:00-05:00,154.74000549316406,156.2100067138672,154.25,155.6999969482422,8165060
2019-01-02 10:30:00-05:00,155.77999877929688,158.41000366210938,155.4499969482422,157.66439819335938,5404475
2019-01-02 11:30:00-05:00,157.6999969482422,157.85000610351562,156.94000244140625,157.3800048828125,3092806
2019-01-02 12:30:00-05:00,157.36000061035156,158.61000061035156,157.32000732421875,158.35000610351562,3187170
2019-01-02 13:30:00-05:00,158.3699951171875,158.85000610351562,157.77000427246094,158.25999450683594,2761874
2019-01-02 14:30:00-05:00,158.3000030517578,158.69000244140625,156.8300018310547,157.14500427246094,3289360
2019-01-02 15:30:00-05:00,157.11000061035156,157.97500610351562,156.75,157.92999267578125,2805298
2019-01-03 09:30:00-05:00,144.00999450683594,144.94000244140625,142.80999755859375,144.00999450683594,31073059

As shown above, on 2019-01-02 AAPL was $155? When it looks to be around $76 on yahoo finance.

I just noticed the exact same issue. Have you found a work around?

I just noticed the exact same issue. Have you found a work around?

If this still happens, re-submit issue using new bug template.


Correct insignificant typos in README.md

Fixed a few typos throughout the README, none of which where impacting the correctness of the content.

Thanks for the fixes! Could you swap this to target the release branch?
Thanks!


PHPDoc in Session incorrect?

In https://github.com/yiisoft/yii2/blob/master/framework/web/Session.php isn't the @property-read declaration for $cookieParams and $cacheLimiter incorrect? Shouldn't it be just @property?
I didn't check the other properties. There might be further ones. Just stumbled over it.

Indeed this is incorrect. Could you please prepare PR fixing it?

It should be fixed in https://github.com/yiisoft/yii2/blob/master/build/controllers/PhpDocController.php since this part of phpdoc is generated.

@samdark this trash can't work correctly

Yes it can if fixed :)

@samdark it's already fixed in yii\apidoc\models\Context::handlePropertyFeature()

If it doesn't work properly then it's not fixed.

@samdark i mean method in api more better because check setters/getters only in classes extended BaseObject


Ability to control scale/font size of code blocks on a global level

Is your feature request related to a problem? Please describe.
I was giving out a presentation and received a pretty valid feedback that people in the back couldn't see the code examples.
Describe the solution you'd like
A way to control the scale/font size of text inside code blocks.
Describe alternatives you've considered
An alternative solution was found here.

You can override the CSS selector or CSS variables - it's web - you have all the freedom you need :)

The solution was discussed at https://github.com/slidevjs/slidev/discussions/1443. The remaining problem is that we have to use children:h-15 !children:text-2xl to control the style, instead of h-15 !text-2xl. At first, I thought we could just apply the classes to the inner pre of the code block, but it seems to be not a perfect idea because then we can't control the outer div's style.

You can override the CSS selector or CSS variables - it's web - you have all the freedom you need :)

Absolutely agree. Just thought providing a convenient way to do it globally might be useful?
P.S. I tried zooming in the browser but that did not work either 🤔

https://github.com/slidevjs/slidev/blob/5480829fdb2a8b8fa1820713a1d5cec364db72bd/packages/client/styles/vars.css#L6-L7
You can overrides CSS vars with these, isn't that convenient enough?

Looked all over and couldn't find that. Thanks, it is convenient enough. :)

We could definitely improve the docs tho :)

I would love to contribute.


Recommendation when dealing with a create request

Hey PMunch,
Thanks for taking the time to create this library and document it! One question I had from trying to play around with it is, how would you suggest using this library to handle creating an object? As an example, imagine that there was a create user request that would require you to parse a user from the Jester request object. How would you suggest doing that in a way that doesn't conflict with the getUser proc that uses the user id? If you try defining an additional proc that converts a request to a user, then you end up with it conflicting with the existing proc if I understand it correctly?
My current approach is to only use this for readonly workloads, and not for doing any writes - that logic goes in my routes, but I'm curious if you have any ideas. Thanks!

Well, the most obvious way to do it all within the system would be to create a type alias for a newly created user. This would let Nim differentiate between them and allow it to run the correct procedure.
However I never really intended this to be used for anything but reading. The concept is that given some collection of state, and some input object, you should be able to extract and mould the data to your liking. Adding data would go in a route that takes something like a Username and an Email which are both distinct strings with verification methods to them. And then you'd have the logic in your route to actually do anything with the data and return some reasonable result. Of course in the future I plan to create a third library that uses this and autotemplates, to have routes simply be procedures with a pragma and all the type conversion back and forth is done by these two libraries.


foreColorStyle - Styles applying but not "saving"?

Hi Guys,
I'm a long time wysihtml5 user, now migrated over to this for a new project. It's possible I'm doing something wrong, but I'm using a textarea, and I've created a colour picker for setting the text color.
I'm using the documented foreColorStyle function i.e.
// color picker change event
change: function(color){
    self.editor.composer.commands.exec("foreColorStyle", color);
}

The colour applies correctly to the visible editor, however if I then get the textarea value, there's no styles setting the colour (although b, i etc. are all there as expected).

This means that when I submit my form, it doesn't have all of the styling. I figured that this was maybe just an issue with doing it in a textarea (but it's the same if it's a div), and perhaps the .getValue() method would be fine, however it also doesn't contain the foreColor styles;

Any assistance would be much appreciated!

I needed to add the parser rules to get this working as per; https://github.com/Voog/wysihtml/wiki/Supported-Commands#foreColorStyle


feat(cmd_all): support override args for each node

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Also decouple single_node and standalone mode.
Subsequent PRs will also include profiles.
Related: https://github.com/risingwavelabs/risingwave/issues/14997

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Look at https://github.com/risingwavelabs/risingwave/pull/15577 instead.


Cant create new c# class or interface

When i press new class or new interface nothing happens.Do i need to do something else before i press create new c# class?

When i press new class or new interface nothing happens.Do i need to do something else before i press create new c# class?

Are you using it in a project json project. If not this won't work
On Sun, 20 Nov 2016 at 14:00, Mkayxx<EMAIL_ADDRESS>wrote:

When i press new class or new interface nothing happens.Do i need to do
something else before i press create new c# class?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jchannon/csharpextensions/issues/9#issuecomment-261780013,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGapq7ttJhZmPCSWcC9JOpwJrcgb9emks5rAFJ3gaJpZM4K3ix2
.

how do i use it in a json project ? do i need to create it? im confused.

This extension only works for a dotnet core project. That type of project
has a project.json file as the project file which contains the packages and
meta data about the project you are working on. To get started visit dot.net
On Sun, 20 Nov 2016 at 21:20, Mkayxx<EMAIL_ADDRESS>wrote:

how do i use it in a json project ? do i need to create it? im confused.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jchannon/csharpextensions/issues/9#issuecomment-261806625,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGapj-8QRN-1gwOVyRs0WrelMPegyfQks5rALmJgaJpZM4K3ix2
.

ok thanks


Media type hints & overrides

Occasionally it's been asked how $ref should work when targeting an arbitrary location not known to be a JSON Schema or JSON, or when found in an arbitrary location not known to be a JSON Schema. Should you be able to point to an arbitrary document?
This question comes up because sometimes it's useful to host a document at places where you can't completely configure the media type (specified in HTTP using the Content-Type header).
In Web architecture, the target document gets to determine its own media type, not the source of the link. This provides important security guarantees, so that even if a document appears to be valid in multiple interpretations (a "polyglot document"), only the interpretation intended by the origin server will be used, and not a potentially malicious one.
The other benefit is that the server can return a variety of media types. A server might return a YAML document instead, and the client can still make use of that, rather than producing a syntax error as it tries to parse the document as JSON. The server may even return different media types depending on what the client supports. When the source of the link assumes the target is JSON, these features are not possible.
Links can define a hint "type" attribute, which may be used for optimization purposes, or to request a specific media type when multiple are available.
If there are cases where this is insufficient, it may be possible to "override" the media type specified by the target document, but this has the noted disadvantages.
Also note that this issue really only concerns use in HTTP (and compatible protocols that use media types... email...) and doesn't concern local filesystem access. Or rather, if you have local filesystem access, then you're also the one specifying the media type of the files on that filesystem. (That is: This issue is only relevant when there is a boundary that must be crossed: when the target is hosted by a different party than the source.)
Given this, I'm not sure this requires any action. Or I'd suggest describing $ref as a link. Then all you have to do is say "$ref forms an embedded link to the target document".

I feel like overriding the media type declared by the Content-Type response header would be a violation of the HTTP specification. I'm not sure that the spec actually says that applications can't ignore Content-Type, but it's at least understood that they shouldn't do that even if it's just for security reasons. In the JRef proposal, I spell out that implementations MUST respect the declared media type, but I'm not sure a spec really needs to say that. It should be implied just by supporting HTTP requests/responses.
However, it's worth noting that most JSON Schema implementations and other $ref tooling that use HTTP requests ignore Content-Type and assume the media type is what they expect. I think that's at least a bad security practice and possibly a violation of the HTTP spec. In any case, any spec that comes out of this effort should not have language that explicitly allows or recommends ignoring media types.
What could make sense is to add support for some feature that sets an Accept header on the request to signal to the server what media type(s) they need. For example, a property in an AsyncAPI document that expects an XML Schema can use that feature to specifically request an XML Schema media type response. The implementation would still have to fail if the response media type was not an XML Schema rather than trying to parse whatever they get.


chore: remove extraneousChangelog header

I thought this was generated? Does the new release tool have a different format? Could you please link details in PR description?

Sorry, the format was correct. Just wanted to remove the extraneous footer.


Allow disabling flash

Is your feature request related to a problem? Please describe.
When I use vit and perform an action like "start a task" and "stop a task" the task I'm working on flashes.
I believe the internal function used for this is flash_focus.
Describe the solution you'd like
Ideally, I would like to disable flashing completely via config option or similar.
Additional context
I'd like vit to be as fast as possible so I don't like waiting for flashes.

Probably the most robust way to handle this is to provide two configuration options in the [vit] section of config.ini:

flash_focus_repeat_times
flash_focus_pause_seconds

There would be some necessary refactoring for those config options to be properly passed down, with the current defaults kept.
I would consider a PR for this feature, but probably will not implement it myself.

For anyone looking for a super quick solution that doesn't mind running vit from source, here's a patch that disables blinking:
diff --git a/vit/task_list.py b/vit/task_list.py
index 8b7e28d..485fd8a 100644
--- a/vit/task_list.py
+++ b/vit/task_list.py
@@ -151,10 +151,10 @@ class TaskTable(object):
             position = self.listbox.focus_position
         self.list_walker[position].row.set_attr_map({None: attr})

-    def flash_focus(self, repeat_times=2, pause_seconds=0.1):
+    def flash_focus(self, repeat_times=0, pause_seconds=0.1):
         if self.listbox.focus:
             position = self.listbox.focus_position if self.listbox.focus_position is not None else self.listbox.previous_focus_position if self.listbox.previous_focus_position is not None else None
-            if position is not None:
+            if position is not None and repeat_times > 0:
                 self.update_focus_attr('flash on', position)
                 self.draw_screen()
                 for i in repeat(None, repeat_times):

I think I have some idea of what would need to be done for a PR here; I'll see if I can manage to find the time to clean it up and do it right and submit that in the next days.


AQGridView does not handle translucent nav bar correctly

If you put an AQGridView in an AQGridViewController with a black translucent navigation bar, the view should be laid out so that it extends underneath the nav bar, and have a negative contentOffset.y value to show a blank area which is shown under the nav bar when scrolled to the top. This situation is not being accounted for in the layout code.

I don’t think we must support an initial negative content offset, although the code not working correctly under this case is a bug; here are a few solutions that will probably work:

Wrap the entire grid view in another view, with a 44-pixel space between the grid view’s top margin and the enclosing view’s top margin

Increase the top content inset of the grid view (it’s a scroll view after all).

Good things about the second solution: a) I like it; b) I use it a lot; and c) when you tell the grid view to scroll to CGPointZero, it scrolls to the correct position, and inertial scrolling will bounce the entire view back to the correct position too.

Closing as Workaround Provided.  Feel free to re-open this issue :)


Texture objects?

Hi, I'd like to ask if support for texture objects like those introduced with CUDA 6.5 is planned - dedicated access to the HW linear texture filtering routines, and variable texture object count accessible from within kernels. I could findno such thing in the docs, is this somewhere on the roadmap?

I believe these are known as images in opencl land. Images are not supported yet.

Image support is being planned for the OpenCL LC implementation. Are you referring to OpenCL image support or support in another programming model?

Thanks. What is "OpenCL LC", may I ask ?

OpenCL LC is AMDs OpenCL implementation that uses what is known as the lightning compiler. It is the only implementation of OpenCL that is supported on ROCm.

Cool. Where can I learn more about this compiler?  Can you comment on stability and performance?

The compiler is actually distributed as HCC. The OpenCL implementation uses parts of HCC to enable kernel compilation.

The LC compiler is actually a part of HCC. Please look at this link for details: https://github.com/RadeonOpenCompute/hcc

Great. Thanks for the info.  I have an application that makes heavy use of opencl images, so really looking for this to arrive for ROCm.

Ah sorry, I would maybe better have placed this in the hcc issue tracker. I'm interested in using images with hcc.
CUDA originally had support for textures (their analog to images in OCL), and they were directly related to texture units, i.e. you had to have a static amount of textures. They relaxed this later (I think wirh CUDA 6)  so that you could use texture objects and wouldn't need to (e.g.) pack a dynamic number of images into an atlas. So texture objects (or whatever one would call them in the ROCm world) rather than mere images are what I'm interested in.

On Feb 22, 2017, at 6:26 PM, James Edwards<EMAIL_ADDRESS>wrote:
Image support is being planned for the OpenCL LC implementation. Are you referring to OpenCL image support or support in another programming model?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

We are planning to provide image support in a future version of hcc.  Please open a new issue under hcc if you are interested in tracking it.  Thanks,


Better Documentation for Actions

when creating my own pager,
i incidentally pass dataSource = true to pagerActions.setPageIndexAsync.
i received the following error from core.js (redux-logger), "uncaught typeError: cannot read property 'type' of undefined".
i looked into your source code, and in this function you check if the dataSource is a function.
could you add an else clause and throw a proper error?

Hmm, the documentation shows that dataSource is either a function or a string. I feel like that should be enough?

when i check your source code, this function only check if dataSource is a function, otherwise, do nothing. the other function setPageAsync, uses the string option.

Hmm yeah -- I think what we really need here is better documentation for all of the exposed ACTIONS. I will mark this issue as a feature request for better docs on actions,

I'm going to try help with this... this morning I was trying to look into how to call the selectAll/deselectAll actions which the selection reducer supports... I'll start to document them in that new sample I started.
We need a USING_ACTIONS.md in the main library which should list and briefly define what the actions for the grid, selection, pager, etc can do...

@headwinds that would be a huge help!

For instance...
this is a bit of mess I have in my project because I sorta know react-redux-grid but not as much as I'd like to..
import { Actions } from 'react-redux-grid';

uncheckAllSelectedRows(event){
    const rows = document.getElementsByClassName("react-grid-row");
    const gridMap = this.props.selection.get("workbench");

    const getAllIds = () => {
      let allIds = [];
      _.times( this.props.datasetOpen.limit, rowIndex => { allIds.push(rowIndex) })
      return allIds;
    }

    const selectedIds = (this.props.datasetOpen.allRowsSelected) ? getAllIds() : gridMap.get("indexes");

    // only click the checkbox of selected rows
    if ( undefined !== selectedIds && !this.state.uncheckingRows ) {
      this.state.uncheckingRows = true;
       _.each(selectedIds, selectedId => {
          let selectedRow = rows[selectedId];
          if (typeof selectedRow !== "undefined"){
            const checkboxColumn = selectedRow.getElementsByTagName("TD")[0];
            if (typeof checkboxColumn !== "undefined"){
              const input = checkboxColumn.getElementsByTagName("INPUT");
              input[0].checked = false;
            }
          }
        });

         // give it 2 seconds to ensure all the rows are unchecked
        setTimeout( ()=>{
         this.state.uncheckingRows = false;
         this.props.allRowsUnchecked();
         const stateKey = "workbench";
         this.props.deselectAll(stateKey);
        }, 2000);
    }
  }

const mapDispatchToProps = (dispatch) => {
  return {
    allRowsUnchecked: () => {
      dispatch(actionsTag.allRowsUnchecked());
    },
    deselectAll: stateKey => {
      dispatch(Actions.SelectionActions.deselectAll(stateKey))
    },
  }
}

Do you have this in a public repo?
Rather than using a querySelector to get the actual divs, you should be connecting the component to this slice of the grid state, so you will know what is selected/unselected at all times.

not yet - I have the day off today - which means I get to work on open source! I'll put it together this morning within a new branch for to review.
But this feedback is exactly what I'm looking for - I knew some of what I was decent; the other was crap; especially that timeout I used! bad code smell.
By using selection, I can see the selected indexes within the map if I selected them individually but when I check the select all check box, that indexes array isn't available anymore and its replaced by a list of keys which I wasn't sure how to use.
If I dispatch an action to deselectAll, I want the react-redux-grid to both clear any selected indexes and uncheck the selected checkboxes without me having to touch the query selectors. So I'll setup this scenario in my example and share it with you as a new branch.

Sounds good. Upon selectAll, if the indices array is empty or missing, that's a bug that should be logged/fixed.


Testing: integration test refactoring

Summary
As our codebase grows, we want to make working with integration tests easier!
Components

[x] Make serial, integration tests parallelized (integration-grouped) tests
[x] Use inlined configuration over file(s) #485
[ ] Set RPC/HTTP ports to 0 in test configurations and have the OS choose an unused port for all RPC/HTTP servers (via @QuinnWilton). Note: TCP listeners in Rust do this automatically with bind and using the TcpListenerStream -> https://github.com/hyperium/tonic/blob/master/tests/integration_tests/tests/timeout.rs#L79.
[ ] Use :memory DB configuration name in integration tests to remove the need for named setup/teardown. This should be isolated per test due to be running within a child proc.

We've decided to punt on the last two checkboxes here. We may return to them in the future.


Completed targets do not persist their states, on Void Linux

Hello.
In case if there is an interest in fixing: I found a bug, when working on Void .
Looks like after some set of task ran by Ninja re-running the same top-level task starts the whole process again, even despite that compiled/linked output is present.
Current version of Ninja is 1.10.2

Please debug what's going on using ninja -d explain.

Please debug what's going on using ninja -d explain.

Here you go:
https://www.reddit.com/r/voidlinux/comments/kq5gx8/ninja_1102_does_not_save_states_of_successfully/
https://drive.google.com/file/d/1w-DNRsMu8DdxMxGg2Gh9YgaPOR82a1UW/view?usp=sharing
https://drive.google.com/file/d/1c75dHlSBIrZ7DdFrDlw2_0Yh9WEletQL/view?usp=sharing
https://drive.google.com/file/d/1DrNNLwui-qSmzWWH2uwx_52f4l_Rf7Cl/view?usp=sharing

Here you go:
https://www.reddit.com/r/voidlinux/comments/kq5gx8/ninja_1102_does_not_save_states_of_successfully/
https://drive.google.com/file/d/1w-DNRsMu8DdxMxGg2Gh9YgaPOR82a1UW/view?usp=sharing
https://drive.google.com/file/d/1c75dHlSBIrZ7DdFrDlw2_0Yh9WEletQL/view?usp=sharing
https://drive.google.com/file/d/1DrNNLwui-qSmzWWH2uwx_52f4l_Rf7Cl/view?usp=sharing

Looks like a duplicate of #1330 to me.

Looks like a duplicate of #1330 to me.


Panel onResize not called if there is no onLayout

For the initial render, if the layout is restored from local storage, the Panel's onResize function is only called if the PanelGroup has a onLayout. This is not expected and I assume was not intentional?
In this PR I just removed the if (onLayout) check in favor of a onLayout?.(sizes) later on.

Published as 0.0.52!

I think this change caused a regression, though I'm not sure how yet.
I tried updating to this version in Replay (https://github.com/replayio/devtools/pull/9381) and here is a recording of a failed end to end test:
https://app.replay.io/recording/affac99d-d290-4cc6-91db-6c542545ef12

Woa, nice work tracking that down. Sorry this PR introduced that issue!

No worries ☺
On Sun, Jun 25, 2023 at 2:17 PM Rijk van Wel @.***>
wrote:

Woa, nice work tracking that down. Sorry this PR introduced that issue!
—
Reply to this email directly, view it on GitHub
https://github.com/bvaughn/react-resizable-panels/pull/161#issuecomment-1606209140,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAHHHIDQX6KIUYHBZLCRYLXNB6E5ANCNFSM6AAAAAAZQIH36Y
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


[BUG] Null value if the field has an alias

Describe the bug
A model defined by a field with an alias gives a null value in the response.
To Reproduce
Steps to reproduce the behavior:

Create the following files using the template full-stack-fastapi-postgresql

models/test.py

from typing import List
from pydantic import BaseModel, Schema

class metadata(BaseModel):
    title: str = None

class baseType(BaseModel):
    metadata_: List[metadata] = Schema(None, alias="metadata")

class testSummary(baseType):
    tid: str = ...

class testCollection(BaseModel):
    tests: List[testSummary] = None

class TestBase(testSummary):
    pass

class TestCreate(TestBase):
    pass

# Properties shared by models stored in DB
class TestInDBBase(TestBase):
    id: int = None
    owner_id: int

    class Config:
        orm_mode = True

# Properties to return to client
class Test(TestInDBBase):
    pass

db_models/test.py

from sqlalchemy import Column, ForeignKey, Integer, String
from sqlalchemy.dialects import postgresql
from sqlalchemy.orm import relationship

from app.db.base_class import Base

class Test(Base):

    __tablename__ = 'test'

    id                 = Column(Integer, primary_key=True, index=True)
    tid                = Column(String, index=True)
    title              = Column(String, index=True)
    metadata_          = Column(postgresql.JSONB, default=[])
    owner_id           = Column(Integer, ForeignKey("user.id"))
    owner              = relationship("User", back_populates="tests")

Add a path operation function with

from fastapi import APIRouter, Depends, HTTPException
from sqlalchemy.orm import Session

from app import crud
from app.models.test import testCollection, TestCreate, Test
from app.api.utils.db import get_db
from app.api.utils.security import get_current_active_user
from app.db_models.user import User as DBUser

router = APIRouter()

import logging

logging.basicConfig(level=logging.INFO)
logger = logging.getLogger(__name__)

@router.get(
    "/tests/",
    operation_id="getTests",
    response_model=testCollection,
    status_code=200
)
def read_wps_tests(
    db: Session = Depends(get_db),
    skip: int = 0,
    limit: int = 100,
):
    """
    Retrieve available tests.
    """
    tests = crud.test.get_multi(db, skip=skip, limit=limit)
    if not tests:
        logger.info(f"======> The test collection is empty")
        tests = []
    return {"tests": tests}

@router.post(
    "/tests/",
    operation_id="createTest",
    response_model=Test,
    status_code=201,
    include_in_schema=True
)
def create_wps_test(
    *,
    db: Session = Depends(get_db),
    test_in: TestCreate,
    current_user: DBUser = Depends(get_current_active_user),
):
    """
    Create new wps test.
    """
    if not crud.user.is_superuser(current_user):
        raise HTTPException(
            status_code=403,
            detail="You are not allowed to register tests"
        )
    elif crud.test.get_by_tid(db_session=db, tid=test_in.tid):
        raise HTTPException(
            status_code=422,
            detail="The test has been already created"
        )
    test = crud.test.create(
        db_session=db,
        test_in=test_in,
        owner_id=current_user.id
    )
    return test

Make a POST with a payload of

{
  "metadata": [
    {
      "title": "my title"
    }
  ],
  "tid": "pippo”
}

Make GET request and see error

Expected behavior
Before 0.30.0 I've seen it working but the response had "metadata": null
Environment:

OS: template with containers
FastAPI 0.30.0

@francbartoli I think the problem is that you are specifying an alias metadata for an attribute metadata_, so the model will now expect to receive metadata as one of the things to validate/serialize, but your SQLAlchemy model has metadata_ too instead of metadata.
I guess the first thing to try is to change the metadata_ in your SQLAlchemy model to metadata.

@tiangolo I cannot use metadata cause it's a reserved name for SQLAlchemy with declarative_base

I see, then you can try allow_population_by_alias: https://pydantic-docs.helpmanual.io/#model-config (which actually means allow population by name and alias)

@tiangolo I've tried but now the field is populated with an empty list:
Body request:
{
  "metadata": [
    {
      "title": "thistle"
    }
  ],
  "tid": "thistle"
}

Response is 201 with
{
  "metadata": [
    {
      "title": "thistle"
    }
  ],
  "tid": "thistle",
  "owner_id": 1,
  "id": 3
}

But effectively the record has metadata_ = [] in postgresql

@francbartoli I'm reading this from mobile and still haven't tested it but I think (as suggested by @tiangolo) you could try and define you model like
‘‘‘python
class BaseType(BaseModel):
metadata : List[metadata] = Schema (None, alias="_metadata")
class Config:
    allow_population_by_alias = True

‘‘‘
This way your model's ‘metadata‘ property should be populated both by metadata and _metadata, but should be json encoded to the alias "_metadata".

@stefanondisponibile Applying your changes would end up with the following error:
backend_1        | Traceback (most recent call last):
backend_1        |   File "/usr/local/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
backend_1        |     self.run()
backend_1        |   File "/usr/local/lib/python3.7/multiprocessing/process.py", line 99, in run
backend_1        |     self._target(*self._args, **self._kwargs)
backend_1        |   File "/usr/local/lib/python3.7/site-packages/uvicorn/main.py", line 305, in run
backend_1        |     loop.run_until_complete(self.serve(sockets=sockets))
backend_1        |   File "uvloop/loop.pyx", line 1451, in uvloop.loop.Loop.run_until_complete
backend_1        |   File "/usr/local/lib/python3.7/site-packages/uvicorn/main.py", line 312, in serve
backend_1        |     config.load()
backend_1        |   File "/usr/local/lib/python3.7/site-packages/uvicorn/config.py", line 182, in load
backend_1        |     self.loaded_app = import_from_string(self.app)
backend_1        |   File "/usr/local/lib/python3.7/site-packages/uvicorn/importer.py", line 20, in import_from_string
backend_1        |     module = importlib.import_module(module_str)
backend_1        |   File "/usr/local/lib/python3.7/importlib/__init__.py", line 127, in import_module
backend_1        |     return _bootstrap._gcd_import(name[level:], package, level)
backend_1        |   File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
backend_1        |   File "<frozen importlib._bootstrap>", line 983, in _find_and_load
backend_1        |   File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
backend_1        |   File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
backend_1        |   File "<frozen importlib._bootstrap_external>", line 728, in exec_module
backend_1        |   File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
backend_1        |   File "./app/main.py", line 5, in <module>
backend_1        |     from app.api.api_v1.api import api_router
backend_1        |   File "./app/api/api_v1/api.py", line 4, in <module>
backend_1        |     from app.api.api_v1.endpoints import (
backend_1        |   File "./app/api/api_v1/endpoints/login.py", line 7, in <module>
backend_1        |     from app import crud
backend_1        |   File "./app/crud/__init__.py", line 2, in <module>
backend_1        |     from . import user, process, job, test
backend_1        |   File "./app/crud/test.py", line 7, in <module>
backend_1        |     from app.models.test import TestCreate
backend_1        |   File "./app/models/test.py", line 9, in <module>
backend_1        |     class baseType(BaseModel):
backend_1        |   File "./app/models/test.py", line 10, in baseType
backend_1        |     metadata: List[metadata] = Schema(None, alias="metadata_")
backend_1        |   File "/usr/local/lib/python3.7/typing.py", line 251, in inner
backend_1        |     return func(*args, **kwds)
backend_1        |   File "/usr/local/lib/python3.7/typing.py", line 626, in __getitem__
backend_1        |     params = tuple(_type_check(p, msg) for p in params)
backend_1        |   File "/usr/local/lib/python3.7/typing.py", line 626, in <genexpr>
backend_1        |     params = tuple(_type_check(p, msg) for p in params)
backend_1        |   File "/usr/local/lib/python3.7/typing.py", line 139, in _type_check
backend_1        |     raise TypeError(f"{msg} Got {arg!r:.100}.")
backend_1        | TypeError: Parameters to generic types must be types. Got Schema(alias: 'metadata_', extra: {}).
backend_1        | INFO: Stopping reloader process [1]

I guess the problem is with the name metadata which cannot be applied in pydantic to a field and a model at the same time

🤔 I'm not sure
from sqlalchemy import create_engine
from sqlalchemy import Column, Integer, String
from sqlalchemy.ext.declarative import declarative_base
from sqlalchemy.orm import sessionmaker
from pydantic import BaseModel
from pprint import pprint
from typing import Any
from fastapi.encoders import jsonable_encoder

Base = declarative_base()

class SomeClass(Base):
    __tablename__ = 'some_table'
    id = Column(Integer, primary_key=True)
    metadata_ =  Column(String(50))

class Test(BaseModel):
    id: int = 42
    metadata: Any = ...

    class Config:
        orm_mode = True
        fields = {"metadata": {"alias": "metadata_"}}

engine = create_engine('sqlite://')
Base.metadata.create_all(engine)

Session = sessionmaker(bind=engine)
session = Session()
c_in = Test(**{"metadata_": "foo"})
c_in = jsonable_encoder(c_in, by_alias=True)
c = SomeClass(**c_in)
session.add(c)
session.commit()
for t in session.query(SomeClass).all():
    pprint(vars(t))
    print()
    print("ORM MODE:")
    print(Test.from_orm(t).json())
    print(jsonable_encoder(Test.from_orm(t), by_alias=False))
    print("\nSTARRED:")
    print(Test(**vars(t)).json())
    print(jsonable_encoder(Test(**vars(t)), by_alias=False))

{'_sa_instance_state': <sqlalchemy.orm.state.InstanceState object at 0x1103fa4e0>,
 'id': 42,
 'metadata_': 'foo'}

ORM MODE:
{"id": 42, "metadata": "foo"}
{'id': 42, 'metadata': 'foo'}

STARRED:
{"id": 42, "metadata": "foo"}
{'id': 42, 'metadata': 'foo'}

Hi @stefanondisponibile, sorry perhaps I didn't explain my use case properly. I was meaning this situation which would be required to be consistently conforming with the models' name of my OpenAPI definition.
from sqlalchemy import create_engine
from sqlalchemy import Column, Integer, String
from sqlalchemy.dialects import postgresql
from sqlalchemy.ext.declarative import declarative_base
from sqlalchemy.orm import sessionmaker
from pydantic import BaseModel
from pprint import pprint
from typing import Any, List
from fastapi.encoders import jsonable_encoder

Base = declarative_base()

class SomeClass(Base):
    __tablename__ = 'some_table'
    id = Column(Integer, primary_key=True)
    metadata_ =  Column(postgresql.JSONB, default=[])

class metadata(BaseModel):
    title: str = None

class Test(BaseModel):
    id: int = 42
    metadata: List[metadata] = ...

    class Config:
        orm_mode = True
        fields = {"metadata": {"alias": "metadata_"}}

engine = create_engine('postgresql://')
Base.metadata.create_all(engine)

Session = sessionmaker(bind=engine)
session = Session()
c_in = Test(**{"metadata_": [{"title": "foo"}]})
c_in = jsonable_encoder(c_in, by_alias=True)
c = SomeClass(**c_in)
session.add(c)
session.commit()
for t in session.query(SomeClass).all():
    pprint(vars(t))
    print()
    print("ORM MODE:")
    print(Test.from_orm(t).json())
    print(jsonable_encoder(Test.from_orm(t), by_alias=False))
    print("\nSTARRED:")
    print(Test(**vars(t)).json())
    print(jsonable_encoder(Test(**vars(t)), by_alias=False))

Oh yes, sorry, I hadn't read properly.
However, I tried plugging example into a fastAPI app and it looks like working to me:
docker run --name tmp-postgres -p 5432:5432 -e POSTGRES_PASSWORD=foo -e POSTGRES_USER=foo postgres

from sqlalchemy import create_engine
from sqlalchemy import Column, Integer, String
from sqlalchemy.dialects import postgresql
from sqlalchemy.ext.declarative import declarative_base
from sqlalchemy.orm import sessionmaker
from pydantic import BaseModel
from pprint import pprint
from typing import Any, List, Dict
from fastapi.encoders import jsonable_encoder
from fastapi import FastAPI

Base = declarative_base()

class SomeClass(Base):
    __tablename__ = 'some_table'
    id = Column(Integer, primary_key=True)
    metadata_ =  Column(postgresql.JSONB, default=[])

class Metadata(BaseModel):
    title: str = None

class Test(BaseModel):
    metadata_: List[Metadata] = ...

    class Config:
        orm_mode = True
        fields = {"metadata_": {"alias": "metadata"}}
        allow_population_by_alias = True

engine = create_engine('postgresql://foo:foo@localhost:5432')
Base.metadata.create_all(engine)

Session = sessionmaker(bind=engine)
session = Session()

app = FastAPI()

@app.get("/test", response_model=List[Test])
def read_tests():
    tests = session.query(SomeClass).all()
    return tests

@app.post("/test")
def create_test(test_in: Test, response_model=Test):
    test_in = jsonable_encoder(test_in, by_alias=False)
    test = SomeClass(**test_in)
    session.add(test)
    session.commit()
    session.refresh(test)
    return test

curl -X POST -H "Content-Type: application/json" -d '{"metadata": [{"title": "foo"}, {"title": "bar"}]}' http://localhost:8000/test

{
    "metadata": [
        {
            "title": "foo"
        },
        {
            "title": "bar"
        }
    ]
}

curl -X GET http://localhost:8000/test

[
    {
        "metadata": [
            {
                "title": "foo"
            },
            {
                "title": "bar"
            }
        ]
    }
]

Is this the output you would expect @francbartoli ?
One thing I noticed, though, is that adding session.refresh(test) to the app POST method would mess things up in this example. I'm sorry I can't really understand if this could be an issue and would rely more on @tiangolo or others for this.

So I noticed some errors in my code (don't know why the heck hadn't put the response model into the decorator, sorry about that), so I decided to cut to the chase and set up a little app for it.
Looks ok to me, try that out: git clone https://gitlab.com/stefanondisponibile/fastapi_327

Thanks for all your help here @stefanondisponibile !
@francbartoli It might be the case that the problem is related to https://github.com/tiangolo/fastapi/issues/332 if that's the case, you could try with 0.29.1 and see if it works.
Otherwise, the best would be to write a simple/minimal example program, possibly copying from the SQL tutorial, and replicating your error. That way it would be easier to debug what is happening and what you would expect to happen.

@tiangolo thanks, it is related to that issue. I'm going to test with Pydantic 0.30 if that solves the issue

closed by 0.33.0

Thanks for reporting back and closing the issue @francbartoli ! :tada:


[BugzillaBridge] Add new bridge

closes #2722
Should the other two bridges be deleted (MozillaBugTrackerBridge, KernelBugTrackerBridge)?

So the two other bridges are concrete bugzilla bridges. Maybe keep them around but add a comment to them about this. We should ideally hide them from the web UX.

Yes, we really need to create a better way to deal with deprecated bridges/content.


Cannot reset password for user using /opt/nginx-proxy-manager/bin/reset-password

Hello!
On NPM docker with sqlite db:
After a password loss, i tried to run the reset command as stated in the documentation to reset the password:
https://github.com/jlesage/docker-nginx-proxy-manager#password-reset
Docker command return:
OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "/opt/nginx-proxy-manager/bin/reset-password": stat /opt/nginx-proxy-manager/bin/reset-password: no such file or directory: unknown
I tried to find this binary in container without luck - Please find this search attached as list.txt
list.txt
How can i reset a password then? Has this binary been removed or renamed?
Thanks for your work on NPM and for your help.
Regards - Tonton Jo

wrong container :-)

docker exec nginx-proxy-manager /opt/nginx-proxy-manager/bin/reset-password user1

OCI runtime exec failed: exec failed: unable to start container process: exec: "/opt/nginx-proxy-manager/bin/reset-password": stat /opt/nginx-proxy-manager/bin/reset-password: no such file or directory: unknown
I also accessed the running container using bash and was unable to find the reset-password script
docker exec -ti nginx-proxy-manager bash

find / -name reset-password

Which Docker image are you using ?

I found that if I was signed in as admin, then it was possible for me to set another users password, without having their original (current) password.
Thanks for responding @jlesage


Create Sample App Requests Slice

Requests slice
Receives the destination from try it out screen and perform the requests
Implementation described in #116


Add defaultProject (whose default is head of projects)

Surprises are worse than at least 10 LoC I'd say, but as I've said before, maybe the odds do work out favorably.
You could save 2 user LoC by having an option for specifying which project is the default. What remains then is defaultHaskellProject = "haskell-template";

Originally posted by @roberth in https://github.com/srid/haskell-template/pull/22#discussion_r884926799

Let's get rid of it entirely; see #10
I cannot find a way to make it work reliably with other modules.


support deferred libraries in polymer

To support deferred libraries we would need a way to annotate what is intended to be loaded in a deferred fashion.
This could be a special attribute in html imports, or an annotation in deferred imports.

So is this dead or just deferred (sorry couldn't help the pun)?

Definitely not dead, just haven't had the time to invest into it yet.

moving to https://github.com/dart-lang/polymer-dart/issues/79
(although I wonder if this will purely be a fix on smoke/html_imports sides?)

This issue has been moved to dart-lang/polymer-dart#149.


Parallel upload of code coverage files.

I would like to start a conversation about improving the performance of upload of code coverage files in Azure Pipelines. The Azure SDK team has a number of mono-repos where the client libraries for each of the Azure services is present. When we do a full test pass there is a very large amount of code-coverage data collected and it can take 7-9 minutes to upload the files from a full test pass.
After looking at the code coverage publishing task, and following the implementation I found that there is code within the agent code base which uploads the content to the file container service. The code is serialized.
public async Task PublishCodeCoverageFilesAsync(IAsyncCommandContext context, Guid projectId, long containerId, List<Tuple<string, string>> files, bool browsable, CancellationToken cancellationToken)
{
    var publishCCTasks = files.Select(async file =>
    {
        var browsableProperty = (browsable) ? bool.TrueString : bool.FalseString;
        var artifactProperties = new Dictionary<string, string> {
            { ArtifactUploadEventProperties.ContainerFolder, file.Item2},
            { ArtifactUploadEventProperties.ArtifactName, file.Item2 },
            { ArtifactAssociateEventProperties.ArtifactType, ArtifactResourceTypes.Container },
            { ArtifactAssociateEventProperties.Browsable, browsableProperty },
        };

        FileContainerServer fileContainerHelper = new FileContainerServer(_connection, projectId, containerId, file.Item2);
        await fileContainerHelper.CopyToContainerAsync(context, file.Item1, cancellationToken);
        string fileContainerFullPath = StringUtil.Format($"#/{containerId}/{file.Item2}");

        Build.BuildServer buildHelper = new Build.BuildServer(_connection, projectId);
        var artifact = await buildHelper.AssociateArtifact(_buildId, file.Item2, ArtifactResourceTypes.Container, fileContainerFullPath, artifactProperties, cancellationToken);
        context.Output(StringUtil.Loc("PublishedCodeCoverageArtifact", file.Item1, file.Item2));
    });

    await Task.WhenAll(publishCCTasks);
}

I'd like to propose that we allow for greater parallelism in this upload process. It might be as easy as doing a Parallel.ForEach(...) over the set of files, or more involved (requires more investigation). However before I go an put any effort into doing this and submitting a PR I wanted to flag the issue here to see whether there would be any concerns.
The one that I do think we need to look at is whether parallelism would cause issues for on-premises Azure DevOps Server installations which can't spread the requests across a larger pool of ATs (so could result in request queuing for unrelated requests).
My mitigation for that would be to have the degree of parallelism controllable and for on-premises based builds set the parallelism to 1.

/cc @acesiddhu

@TingluoHuang your thoughts on this? does Filecontainerserver supports uploading file in parallel. i assume it should

@mitchdenny what's the size of those code coverage files? and how many are they?
@acesiddhu the FileContainerServer will do parallel upload (2 thread uploading) when you request it to upload a folder.

@TingluoHuang we have ~6500 files being uploaded per leg of the run. There are 7 legs that publish code coverage so we are uploading about 45,500 files in total, but because of parallelism its the 6500 we are trying trying to optimize. I wonder whether this could be cut over to use the same back-end as Pipeline Artifacts?

@mitchdenny of course we can switch to use ArtifactService, we just need someone change the agent and the service.

Do you think the service could handle greater parallelism on FCS today (quick fix?)

@mitchdenny FCS should be fine since lots of people are still using the old upload/down task that using FCS

OK - I'll look at creating a PR that does more parallelism. I was thinking making it parallel to the number of cores on the agent?

OK - I'll look at creating a PR that does more parallelism. I was thinking making it parallel to the number of cores on the agent?

Hi @mitchdenny, did you get around to creating a PR for this?
PS: You can keep parallelism = cores on agent / 2

@karanjitsingh I didn't. We ended up restructuring our pipelines to build less which resulted in less coverage files per pipeline run so this became less of an issue for us. From my point of view this can be closed, but you could certainly take on optimizing the upload of these files if you wanted to :)


[BUG]:

How are you running AnythingLLM?
Docker (local)
What happened?
i am not seeing the website up and running after  docker-compose up -d --build is completed at localhost:3001
Are there known steps to reproduce?
go to docker folder, copy .env.example to .env, changing the environment variables
And then running  docker-compose up -d --build

What are the logs you see for why the container can not boot? Are the ports already in use?


Include Dashdb (DB2) drivers in the node.js (and other) runtimes

We're developing a customer solution on Bluemix that need to access a Dashdb database. Our current workaround is to create a docker image with the drivers (not sure whether license allows that), but the cold start time is absolutely horrible (20secs).
Please include the DB2 driver binaries (and Node modules) in the standard Node.js Openwhisk runtime.

@mpuittinen Have you looked at bundling up the drivers in a zipped package?
http://jamesthom.as/blog/2016/11/28/npm-modules-in-openwhisk/

@jthomas this particular set of libraries seem to be too large for a zipped action (in the order of 100MB).
@mpuittinen it is probably not feasible to include all the possible client libraries in a single base image.. maybe if you base your image on a standard OpenWhisk image, pulling it from docker hub should attempt reusing the previous layers - making the cold start potentially shorter (and potentially happen only once for any action using this particular set of client libraries).

With the latest simplifications of action "kinds", I expect we can add a new kind eg nodejs:6-dashb as a deployment configuration. This will intersect with work that @csantanapr has started to publish runtime images to dockerhub. I imagine that we can setup individual repos for various runtimes, push them to dockerhub, and point the runtime manifest at these to extend the runtime support in a particular deployment.

What kind of caching mechanism is there for the images from dockerhub? i.e. does that introduce a delay for cold starts with large images? I’ve entered another ticket to have support for Bluemix Container Service registries, would that improve cold start times?

@csantanapr FYI.
Closing as won't fix. Base packages are specific to a deployment.


Update servo-glutin to 0.13

This change is

@bors-servo: r+

:pushpin: Commit 290ee74 has been approved by jdm

:hourglass: Testing commit 290ee74e893523ac16674866eeec80f009d724b7 with merge 91bf89215b4e9f3b2f8a51c9bb707ac99a1f05f2...

:sunny: Test successful - status-travis
Approved by: jdm
Pushing 91bf89215b4e9f3b2f8a51c9bb707ac99a1f05f2 to master...


Added Minimum Edit Distance Algorithm

Description of Change

Checklist

[ ] Added description of change
[ ] Added file name matches File name guidelines
[ ] Added tests and example, test must pass
[ ] Added documentation so that the program is self-explanatory and educational - Doxygen guidelines
[ ] Relevant documentation/comments is changed or added
[ ] PR title follows semantic commit guidelines
[ ] Search previous suggestions before making a new one, as yours may be a duplicate.
[ ] I acknowledge that all my contributions will be made under the project's license.

Notes:

Code is not up to the repository standards.
Please read them carefully and follow them.

Hi, Please check now. I have added the required changes. Hope this is now according to the guidelines.

You can see the typical structure of a program to see how to make your program as per the repository standards. 🙂

Yeah I have updated the code and included all the structures that are defined on the guidelines. Separate namepsace section, a test section. I have have also studied other codes of the repo and they are also like this.

Please rename the file to minimum_edit_distance.cpp.

Ok. But actually I had changed that. Don't know why does it still the same after the second commit and I will add extra documentation and let you know thanks.

👍 Good work.
Please enable GitHub Actions in your repository of this fork in this link: https://github.com/Nirzak/C-Plus-Plus/actions

Yeah I enabled it

Please fix clang-tidy warnings.

Don't know why does it showing return non-zero exit status but I have clearly defined return value 0 and the code is returning exit status 0 on my end.

Please fix clang-tidy warnings.

Code is just fine I have just checked the code in my PC with clang-tidy. I think -std=c++11 is causing the error. But I don't know why. The code works fine on my PC even when I used c++11 compiler. But from clang-tidy when I choose -std=c++14 instead of c++11 the errors were gone.

@Panquesito7 Oh! It's because I used arrays for the Dynamic approach. Now when I have used vector instead of arrays, the Code Formatter check has been passed! Haha.

Any more changes, brother?

Hi, check now, please.

Ok check now please 😓

Hi, Please check now. I hope now at least the documentation will be ok.

Amazing work; I like how you've made & improved the code so well. 😄 🎉
Code and documentation are pretty good and refined; LGTM. 👍

Thanks brother for the proper guidance.


When does it support  yolo2?

Sorry it does not support yolo v2. I encourage you to use the code as a reference and make your own implementation that supports yolo v2.
Cheers


What was the reasoning for using .Scratch variables instead of custom $var := for initialize and $var = for assignment

These features have been in Hugo since v0.48 so I'm curious as to why .Scratch is being used?
https://gohugo.io/templates/introduction/#variables

Hello @gaetawoo
This is how we code, is there any issue you are facing? we would love to solve it if there is any issue. thank you

With Hugo v0.47.0 and earlier you had to use a Scratch because you could not assign a new value to a variable after it had been initialized.
The underlying Go limitation was removed over 3 years ago with https://github.com/golang/go/issues/10608.
Using $var :=   and then $var = results in modern syntax for Hugo templates, and cleaner, more readable templates. Might want to consider it. Thank you for the response.


use oauthenticator 17.2 for pkce-experiment (jupyter-health)

enables refreshing auth tokens, used in jupyter-health

@GeorgianaElena thanks! Looks like it deployed successfully and things are working (I see in the Hub logs that my token was expired, but rightly refreshed using a refresh token when I launched my server), but the health check failed. I don't see any information about the health check or its failure, though.
I suspect it's due to refresh_auth not succeeding for the fake deployment-service-check user and the fact that refresh_pre_spawn is True. I think OAuthenticator may need some handling of these fake users to bypass refresh_auth. Disabling refresh_pre_spawn altogether is one workaround.

@minrk, I've disabled refresh_pre_spawn and re-ran the test. It still fails.
With refresh_pre_spawn True, it failed to start the server, now it fails to start the kernel here
And the actual error is:
    async def ensure_kernel(self, kernel_spec=None):
        kernel_specs = await self.list_kernel_specs()
        if kernel_spec is None:
>           kernel_spec = kernel_specs["default"]
E           KeyError: 'default'

Looking at the oauthenticator PR now.

Okay, I think that makes sense, actually.
If we want to be able to use OAuthenticator with users that aren't actually users, I think we need an explicit bypass of the refresh_user machinery somewhere.
It is a generic issue, I suppose, but perhaps the fix belongs in OAuthenticator for now to somehow bypass either for specific users or some property of users, e.g. having no auth_state at all.

Agree! I was leaning towards the same solution. I think I will revert this PR for now, if that's ok and we can test it again once we have the oauthenticator bypass implemented.

@GeorgianaElena actually, can I point the health check to another user rather than the fake one? Then the health check should work and we can keep testing.

Ah, I guess I can't really do that because the test hardcodes the username and makes quite a few assumptions about how users are handled by the Authenticator and that invalid users won't have any problems, which isn't necessarily the case, as seen here.


CCE Turbo Clusters and CCE Clusters

Issue on page:        https://github.com/opentelekomcloud-docs/cloud-container-engine/blob/main/umn/source/clusters/cluster_overview/cce_turbo_clusters_and_cce_clusters.rst
Please remove "QingTian" as naming of the architecture.

It's the name of Huawei architecture we use so we can't remove it. Description of the technology is publicly available.


[WFLY-10204] Upgrade openjdk-orb to 8.1.1.Final

Fix for correct openjdk-orb sources JAR generation

@kabir sorry - forgot about it - will remember next time :)


Iee add serach to removed rmid

relevant to https://www.pivotaltracker.com/story/show/188402011

@amcates ready for review

@Ito-Eta is there a story to reference with this one?

updated original comment with that


Allow guests to use source control diffing features in VS and VS Code

Note that developers starting the collaboration session (hosts) do not have this limitation. It is specific to guests joining a session.

Currently source control features like those found in the VS Team Explorer and the VS Code Source Control tabs do not function for guests joining a collaboration session as they rely on local files to work.  In addition, source control diffing features suffer from similar problems regardless of where they are initiated.
We should consider doing the extra work required to allow guests to use source control diffing in VS and VS Code to help owners isolate issues if there is sufficient interest in the scenario.

This has now been addressed in the latest Live Share release! 🔥In VS Code, this works out of the box, and in VS, you'll need to use VS2019 Preview + the Pull Requests extension. Let us know if you have any questions/issues. Thanks again for the feedback!

I see that this feature was released in https://github.com/MicrosoftDocs/live-share/releases/tag/v0.3.1011 however the feature either isn't available, or it's unclear how to enable it.  I don't see any configuration option to enable this.  Do I need to (further) RTFM, or is this not working?
I'm writing an article on remote collaboration with VSCode today and I'd love to be able to include this feature!

@rojopolis We just realized that we forgot to move this feature out of the experimental stage. We're going to update this now and release a fix. In the meantime, if you set the liveshare.features setting to experimental, then you'll see the list of changed files + diffs show up on the guest side via the Source Control tab. Apologies for the confusion on our end!

@rojopolis We just shipped the update to the marketplace that enables shared source control state with guests. Apologies for that mistake, and let us know if you run into any other issues. Thanks!

I noticed that the guest source control does not update while the host is inactive. I was testing the diffing behavior using a remote host via remote desktop. Specifically, the guest source control did not reflect updates while:

the vscode window on the host was minimized in an active remote desktop session
the host vscode window remained open but another window was active
the remote desktop window to the host computer was minimized/closed

It did work when

the host vscode window remained selected in an open (but not selected) remote desktop window

steps:

open remote desktop and start live share session
connect from local pc
create one of the above scenarios
change file from local pc and save -> source control panel does not change
select vscode window on remote -> source control panel on local pc changes

I'm trying to use this as a stopgap method for remote collaborative editing until #2128 is implemented, and it'd be great to see diffs without having a remote desktop session open all the time.
Thanks!


Flaky test: JobScheduleControllerTest

The ScheduleSpecFormat does not use a clock but writes
Json.obj("nextRunAt" -> o.nextExecution(DateTime.now(o.timeZone)))
That eventually fails when the test is run close to the end of a minute. A clock should be used somewhow.

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-1584. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.


Add node20 support

Addresses issue #4

Add a code and unit tests for node20 JS type
Fix security warnings reported by NPM

Hi! Thanks for the contribution. Well done, can't nitpick to your PR :)


Allow record type definitions to be specified in runtime

Clients need to adjust to what a server can respond with. This is something that can be done on a per-adapter basis without breaking anything, just an optional feature.
store.adapter.mutate({
  [type]: { ...definition }
})

It turns out that mutating record types already works, it just wasn't tested. Done https://github.com/fortunejs/fortune/commit/a4260d8ee90aba3589b8b727f1043a62be2c8bd2.
Also decided that having another method for this isn't necessary.


[Bug]: Investigate 502 GPT API errors

Bug Description
Also improve logging for them, it’s not great at identifying what’s going on.
Expected Behavior
Gracefully fail, with more information
Steps to Reproduce (Optional)
No response

This no longer seems to be happening, will reopen if it happens again.