Rng should rate limit to avoid draining entropy before it is added by the hardware

See https://github.com/espressif/esp-idf/blob/9106c43accd9f5e75379f62f12597677213f5023/components/esp_hw_support/hw_random.c#L46-L88

Do we have some better information about how the RNG works, than the TRM? The TRM implies that the peripheral is always TRNG, but we're using it as though it acted as a PRNG when it doesn't have enough entropy.
Porting the C code wouldn't be too hard, although I have some worries about multi-core concurrent access.

If none of the above conditions are true, the output of the RNG should be considered pseudo-random only.

I would be more comfortable seeing this in a TRM, but okay 😅


making this a little more clear - dynamically applying stylesheet to document

this all looks very promising, and I am very familiar with RequireJS at this point. But what's not clear to me about your lib is how to actually dynamically add the stylesheet once it's JS memory on the front-end. So ok, say I have this:
define(['css!my_stylesheet_path',function(sss){

 //how do I apply the stylesheet 'sss' to the document?  <<<<

});

We can dynamically add stylesheets to the document like this:
<html>
    <head>
        <link rel="stylesheet" href="stylesheet.css" type="text/css" />
    </head>
    <body>
</html>

$(document).ready(function () {
    $("a").click(function () {
        $('head').append('<link rel="stylesheet" href="style2.css" type="text/css" />');
    });
});
```html

Perhaps this is the answer:
http://www.w3.org/wiki/Dynamic_style_-_manipulating_CSS_with_JavaScript
var sheet = document.createElement('style')
sheet.innerHTML = "div {border: 2px solid black; background-color: blue;}";
document.body.appendChild(sheet);

This should be in your examples, no? It took me an hour to determine that it was just a matter of appending a string like.

This lib loads and inserts the CSS into the page automatically....  It doesn't go into "JS memory"
See line 129

you mean this line:
var link = document.createElement('link');

are you aware that you can do this:
var sheet = document.createElement('style');  //1
sheet.innerHTML = "div {border: 2px solid black; background-color: blue;}"; //2
document.body.appendChild(sheet); //3

as per
http://www.w3.org/wiki/Dynamic_style_-_manipulating_CSS_with_JavaScript
'link' uses AJAX behind the scenes, so it won't work with the r.js optimizer
if you don't see what I am saying I can try to explain more, but basically what I am suggesting is to use the above 3 lines of JS to add stylesheets to the page without having to re-retrieve the stylesheet from the server.
hope it makes sense

In development, it always retrieves from the server, the same as it does with your JS. When optimized, the CSS is included in the JS file (like with any other dependency), along with a helper script that will insert the CSS into a style tag. So it actually does everything you talk about already.

And link doesn't use ajax behind the scenes. It's a plain old request, same as adding an image.


Using the tagbar in a window like fzf or rg has

What is your expect?
I am not sure this is possible but it could be awsome if we can show the tagbar or Vista in a window like we are currently using for fzf and ripgrep.
i.e:  + tb can show a listing off class attributes etc. What ever the result of tagbar or vista.

fzf and denite support outline .

Please try :Denite outline

Hi @taigacute thx for the reply. But i did not understand how this can work. But anyway i gave it a try and saw that:
[denite] sqlite3.OperationalError: unable to open database file
[denite] Please execute :messages command.```

How can i create an sqlite db? I mean where should i create.

But even if i create i think it will not cover what i thought. You know the tagbar pane on the right, i wish to have it like a window of FZF or RG, so is this `:Denite outline` do this?

why you got this. i comment todoapp.vim this plugin. because the todoapp.vimneed sqlite databse . please check plugins.yaml .  Denite outline  will got the outline in floatwindow

Weird it is still in my plugins.yaml
  on_cmd: [TodoAdd,TodoImport]
  on_source: denite.nvim

comment it .

Perfect. One thing more, when i try to update my fork with your current master, it shows me many conflicts i am solving all of them but the readme file is always appearing as a new conflict. It is super interesting.

i found a interesting setting. used vista and fzf can do this

Wovvv thats better perfect. <leader> + fv works perfect. Thanks @taigacute


feat: add xmind every group

Background
I add some xmind with those content, it would be preview this complete comprise.

Thank you very much for your contribution!


Versioned broadcast

BroadcastMinVersion and BroadcastMaxVersion broadcast only to peers that are of at least or at most the specified version, respectively. This is necessary for the upcoming header broadcast PR which will need to broadcast blocks to older peers and headers to newer peers. It is also useful for general backwards compatibility considerations. As an example use, RelayTransactionSet is now only broadcast to peers that are at least v0.4.7, so as to limit the number of conflicting calls to the colliding old RPC name RelayTransaction.
I'm not too sure about the names, as BroadcastMinVersion makes it sound like it's broadcasting some version number.

I'm not sure if this has any present use, but it might be cool to add a Version method to PeerConn. Then you could write version-branching code inside RPCs.

Adding two new methods is the easiest way to implement this functionality, but I'm not sure it's the best. Here's one alternative:
// in modules:
type Peer struct {
    NetAddress NetAddress
    Version    string
}

// in gateway:
func (g *Gateway) Broadcast(name string, obj interface{}, peers []modules.Peer) {
    if peers == nil {
        peers = g.Peers()
    }
    //...broadcast logic
}

// in transaction pool:
var peers []modules.Peer
for _, p := range gateway.Peers() {
    if build.VersionCmp(p.Version, "0.4.7") >= 0 {
        peers = append(peers, p)
    }
}
go tp.gateway.Broadcast("RelayTransactionSet", ts, peers)

Not saying this is the best solution -- it complicates things by introducing a new type -- but it does allow you to write arbitrarily complex Broadcasts outside the Gateway rather than inside. Generally speaking, I think I would prefer one extensible Broadcast to multiple specific Broadcasts. Thoughts?

I'm not sure if this has any present use, but it might be cool to add a Version method to PeerConn. Then you could write version-branching code inside RPCs.

I'd be worried that this would overly complicate RPCs. With that said, it would allow us to maintain backwards compatibility without adding additional RPCs or changing their names to include a version (such as RelayTx2 we talked about offline last week). Since backwards compatibility is hard, I like this idea.

Adding two new methods is the easiest way to implement this functionality, but I'm not sure it's the best. Here's one alternative:
...

:+1:

I think it makes sense. Especially if your logic is more complex, like 'send it to 045 and 047 but not 046' or something like that. Or if you've got a blacklist that the consensus set is maintaining, or some other reason. I'm in favor of nixing the range call in favor of letting the module figure out which peers deserve a message.

Broadcast is interesting in that it could easily be implemented outside the gateway, since it only calls exported functions. I suppose it's a useful helper though, and the implementation may become more complex, or we may wish to add metrics to Broadcast

Done. As a side effect of returning []modules.Peer from Gateway.Peers() instead of []modules.NetworkAddress, siac was printing out peers in as the raw modules.Peer structs ({address, version}), so I updated the command to print the address and version in a table like so
$ siac gateway list
1 active peers:
Address              Version
  <IP_ADDRESS>:9981  0.5.1

Oops thought you were talking about something different, I'll fix this up tomorrow when I'm not dead tired.

Should be all set.

All testing except siac testing should be complete. The only commits left for review are commits 10bb440 and onward (the commits that add testing). I rebased so it's not clear that those are the only commits different from last time.

branch is out of date with master, otherwise looks pretty good. Two non-blocking nits

(siac aside, code coverage looks good)

Done (added more test cases for TestAcceptConnRejects and TestConnectRejects and rebased).

ok, needs rebase. Then we're good.


Add monadic operations for std::optional, p0798

See p0798Rx
See also optional-fun-lite.

See also PR 60 and PR 61 of expected-lite for C++11 implementation ideas.


Copy speed calculation error — 0 MB/s avg

Something is wrong with average copy speed calculation in logs:
Started copy to S:\plot-k32-2021-06-21-21-14-hash.plot
Copy to S:\plot-k32-2021-06-21-21-14-hash.plot finished, took 621.73 sec, 0 MB/s avg.

https://github.com/madMAx43v3r/chia-plotter/issues/484

should be fixed now


hub init -g does not actually create the project

The docs state regarding the -g option to hub init:
       -g     After  initializing the repository locally, create a "USER/REPO"
              repository on GitHub and add it as the "origin" remote.

However see https://github.com/github/hub/blob/c60ca203c9ecfdb8e0693a0fc0edfa9d58dd00d1/commands/init.go#L72-L88
It only adds the url of the remote as if the project were to exist.

Our documentation was stale. We fixed it, but it hasn't yet been released: #1810

I think it's super useful to just be able to create a repository instantly and have the remote initialized and have it created on github. Do you think we could see a flag somewhere to do this in one step?

Please let me know if there is any page with example workflows explaining how this chaining works.
I get all kinds of unexpected errors such as "must be called in a
repository" or needing to call "git push --set-upstream origin master"
which then actually doesn't work smoothly.
Example: a public key vs. user password. When is which one used? It seemed to be different depending on if I created a repository on GitHub or with "hub create -p". And also depending on if it was created with or without original readme on GitHub. Hard to know what made the difference.
The git=hub aliasing you propose backfires I think because it makes it complicated and confusing to google for workflows.

It would be great to have an end-to-end list of required commands.
Starting from nothing till having a new directory, which is a git repository linked to a GitHub repository including being able to call git push without any further difficulties or requirements.

To create a new repository on GitHub from the command-line:
cd my-project
git init
git add . && git commit -m "It begins."
hub create -d "My new project"
git push -u origin master
# after this you can use simple `git pull/push`

To push to a repository that was initialized on GitHub with a README, you first have to clone it:
hub clone my-project
cd my-project
# ... make some changes ...
git push

Notes:

The reason why git init, hub create, and git push steps are separate is because different people's project creation needs are different and a single workflow wouldn't cover everyone's use case. Since people generally don't create multiple new GitHub projects per day, I'm hoping that executing a few short commands manually isn't too large of a task for a regular user.

You don't need to alias hub as git. In fact, I don't do it on my machine.

Example: a public key vs. user password. When is which one used?

Git will want to use ssh keys for clone/pull/push operations for repositories cloned over the ssh:// protocol (sometimes also recognizable by urls starting with git@), which is the default protocol for hub operations unless you opt into HTTPS mode: git config --global hub.protocol https.
Hub commands will always ask you for username/password on first run because they need to authenticate to the GitHub API, which is completely separate authentication from git clone/pull/push operations. See https://github.com/github/hub/issues/1644#issuecomment-359002547

which then actually doesn't work smoothly.

It sounds like you are expecting hub to work smoothly for your workflow, but you haven't really described your workflow. If there is a bug in hub, please tell us about the bug and about your hub version. If hub did something that you didn't expect, or if you have ideas how to have it work better, then please suggest some! But it would be helpful to talk in more detail and with more precision. For instance, if I run hub <command> <args>, what exactly should happen?

Thanks for writing in! Sorry that this is still a bit of a mess. Hub is hard because git is hard.


⚠ Fortnite has degraded performance

In 70f4682, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1514 ms

Resolved: Fortnite performance has improved in 0d060ee.


Added parameter validation and install instructions

Resolves #43 and #42

@kfprugger, Let me know if this is enough checks for the issues you raised.


"Multiple URIs for a single entity" Downloads

Please consider adding  support for aria2's "multiple URI for a single entity" downloads.
TLDR: A single line with URIs seperated by a TAB character.
Excerpt from manual:
-i, --input-file=<FILE>
          Downloads  the  URIs  listed  in  FILE. You can specify multiple
          sources for a single entity by putting multiple URIs on a single
          line  separated by the TAB character.  Additionally, options can
          be specified after each URI line. Option lines must  start  with
          one  or more white space characters (SPACE or TAB) and must only
          contain one option per line.  Input files can use gzip  compres‐
          sion.   When  FILE  is specified as -, aria2 will read the input
          from stdin.  See the Input File  subsection  for  details.   See
          also  the  --deferred-input option.  See also the --save-session
          option.

duplicate with #608


PyMDE getting stuck on "Computing quadratic initialization"

Hi.
I have had some on and off luck with using pymde. I am trying the embedding on a dataset of images and the way I have been working on my experiment is as follows:

Extract images from folders and save them as a numpy array
Convert images using a CNN-AutoEncoder (CAE) model to 1x1x8 code
Use pymde to calculate the embeddings
Use HDBSCAN to cluster the embeddings

The experiment works great when i use images from 2 folders (2list.npy). But when I increase the number of images (3list.npy, 10list.npy), the code gets stuck at "Computing quadratic initialization".
In the google drive link below, you will find the following:

Jupyter Notebook
requirements.txt
Numpy array files
CAE model

The code in the notebook is self explanatory. To duplicate the issue, first use "2list.npy", which should run successfully. Then try "3list.npy" and "10list.npy", which should get stuck at "Computing quadratic initialization".
https://drive.google.com/file/d/17kktp6W1Lq_7PjxCiEQBEAk_u-kbDLEN/view?usp=sharing

Hey, thanks for trying out PyMDE!
Computing the quadratic initialization can take some time if the number of items is large.
I assume you're using the preserve_neighbors function. Can you try the following? Pass in init='random' to the function. That will bypass the quadratic initialization computation.
So, something like
pymde.preserve_neighbors(data, init='random')

The init strategy is explained in the docs here: https://pymde.org/api/index.html#pymde.preserve_neighbors
Let me know if that works?

Thanks! That did help. However, I did notice that at times the quadratic initialization for a large dataset would run very quickly (this happens totally at random and I am not able to reproduce this consistently) .
Additionally, the files I have loaded do not have much difference in number of data rows. "2list.npy" has ~25K rows and the quadratic initialization with this dataset runs almost immediately after running the embedding function with preserve_neighbors. But when I do the same with "3list.npy", which has ~38K rows, it takes anywhere from 30-40 minutes to compute the quadratic initialization. My assumption was that for additional 13K rows the code would relatively run faster.
Does duplicate items have an impact on computing quadratic initialization?

Wow, 30-40 minutes is way longer than I would expect! Computing a quadratic embedding on MNIST (70k items) takes just a few minutes. Thanks for letting me know.
Generally you shouldn't have duplicate items when using PyMD, but I wouldn't expect the presence of duplicates to increase runtime.
I'll take a look at your data later this week.

@akshayka,
This time apologies from my side for a late response. Here is the new link with the requested encoded files:
https://drive.google.com/file/d/1nNjBfK5q6_sZrGj3IHnlku93SPwKEJCw/view?usp=sharing

https://drive.google.com/file/d/1nNjBfK5q6_sZrGj3IHnlku93SPwKEJCw/view?usp=sharing

Closed the issue by mistake. Have reopened it.


GEODE-6588: Cleanup static analyzer warnings.

This is a very deep cleaning around all things bucket related.

The 1 new LGTM alert, 'Inefficient output stream', is a false positive, reported https://github.com/github/codeql/issues/7610. LGTM suppression is also not working correctly.

If it's not too much hassle, it would be really helpful to have a list of the automatic clean-up tasks that were applied in this PR, to get an idea of what the scope of the changes are.

If it's not too much hassle, it would be really helpful to have a list of the automatic clean-up tasks that were applied in this PR, to get an idea of what the scope of the changes are.

All of them. This PR follows a path through all the places we use Bucket Ids and cleans them up completely refactoring to come later.

I feel conflicted about changes of this size and the fact that it would take me a very long time to properly review this.

It is either 1 PR with 100 commits or 100 PR with 1 commit. I think this approach should be faster. Unfortunately we chose to take human decision making out of our review process so all of you are required for review even though a few humans could have determined these are all analyzer cleanups.

A few nitpicks, but nothing that should hold up the PR, especially if there's a plan to do a second pass to refactor stuff.

Second, third, fourth... This should be an ongoing effort by everyone.

Sorry for the rebase force push but our PR pipeline doesn't like merges... yet..


Add ability to use SRA as sample input

This will let users easily include datasets offline for context and will aid in the creation of test datasets (https://github.com/nf-core/pathogensurveillance/issues/35)

done


Torus connector doesn't work

You can test Torus login here: https://demo.snapshot.page Somehow when user login using Torus the request to get accounts or network from the provider aren't resolving. Something must be wrong in the integration. More info here: https://github.com/snapshot-labs/lock/pull/2

thanks for opening this @bonustrack


Upload on PyPI & repo ownership

Is this something we want to upload on PyPI under the name fpm we have reserved now? Also, should this repo live in Fortran-lang?
cc @gnikit @certik @milancurcic @lkedward

Yes but we need to make some minor  adjustments. I have a MWE but I'll get to it when I get back to London. Is that okay?

I was about to message you today.
I have a cmake build that requires a lot less boiler-plate, just a single
file.
I was planning on copying the cibuildwheel either from here or cmake.
My long term solution and a non working prototype I have was to mimic
Cargo's (I think) use of setuptools.
How do you feel about the cmake build instead of Meson?
On Sat, 4 Mar 2023, 09:43 Sebastian Ehlert, @.***>
wrote:

Is this still something we want to do?
—
Reply to this email directly, view it on GitHub
https://github.com/awvwgk/fpm-on-wheels/issues/1#issuecomment-1454680489,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD3FKZBFLOH3GBAFNMOBST3W2MFFFANCNFSM6AAAAAATNV223Y
.
You are receiving this because you were mentioned.Message ID:
@.***>

The advantage of meson is that it is a pure Python package and simplifies installation via pip if no binary distribution is available, our only non-Python dependency would be a compiler and ninja, which are both pretty robustly handled in meson-python from my experience so far.
I don't believe that any solution in setuptools, CMake or meson will be cleaner and preferable, we are hacking around the wheel format in any case to distribute a binary on PyPI. However, I would strongly recommend against setuptools, because the compiler handling is quite difficult to get right since Fortran not being well supported there.
Feel free to share your CMake solution here and we can make a decision.

I am porting things from my MWE and I will open a Draft PR.
I don't have a problem with meson (I have little experience with it though). The plan I had in mind was to use scikit-build + cmake

PR #2 is in main, we have wheels for all major platforms and architectures with parallel compilation (on the fpm side), next steps should be
Next Steps

I will be merging this today around 14:00 GMT
@awvwgk Can we move this repo to fortran-lang
I will then upload the PyPi tokens and credentials
I will backport older versions of fpm and issue releases and upload the wheels to pypi
Issue Announcement on Discourse

Gentlemen, we are live on on PyPi https://pypi.org/project/fpm/. I will make an announcement on Discourse.
I am closing this issue now, feel free to reopen if there are any issues.


Using vision transformers for different image resolutions

Hi, I ma working on using vision transformers not only the vanilla ViT, but different models on UMDAA2 data set, this data set has an image resolution of 128*128 would it be better to transform the images into the vit desired resolution like 224 or 256 or it is better to keep the 128 and try to update the other vision transformer parameters to this resolution like the dim,depth,heads ?

@Oussamab21 you can keep the 128, but can lower the patch size to have more patch tokens


Add upload to imgur, dropbox, Google Drive option

It would be great to record the screen, and the gif could be automatically uploaded to any of these following services and give us a direct link to that gif

imgur
Dropbox
Google Drive

I am using this app mac2imgur this app takes the screen capture we do on Mac and uploads it to imgur and gives back a direct link to that image on imgur it's open-source maybe you can look at the source and use it to get an idea.

We're working on a feature that will open up for things like this, we're planning on shipping it as part of the 2.0 project. Leaving this issue open to help avoid duplicates.

Support for plugins is on master! You can find the docs here https://github.com/wulkano/kap/blob/master/docs/plugins.md

An Imgur plugin will be available in Kap 2.0! You can check out the work @kevva has done on it at https://github.com/kevva/kap-imgur. Suggest narrowing the scope of this issue to Imgur only (but keep it open to avoid duplicates until launch), and create new plugin request issues for Dropbox and Google Drive.

The Imgur plugin is available in the Kap 2.0 Beta!

This feature is so cool, but it'd be nice to upload the gifs to the users account. I know it's possible because a tool called Share X do it. It lets you add your account and they images uploads directly to you account.

There's an issue for it here https://github.com/kevva/kap-imgur/issues/3.


CDPSDX-4157 Fixed "remote_admin is undefined" error on database backup

JIRA: CDPSDX-4157 - the root cause of this jira is the database backup failed (but it showed successful). This PR will fix the issue that cause the database backup fail.
ISSUE: Get this error when running DB backup: [{"outputter":"highstate","data":{"dl-9go86ufc7i-master0.sdx-quas.xcu2-8y8x.dev.cldr.work":["Rendering SLS 'base:postgresql.disaster_recovery.backup' failed: Jinja variable 'remote_admin' is undefined"]}}]}
FIX: Renamed pg_username (which is never used) to remote_admin

Can one of the admins verify this patch?


fix: update UCC UI to v1.27.1

Related PR: https://github.com/splunk/addonfactory-ucc-base-ui/issues/401

Codecov Report

Merging #785 (10ec146) into main (7f8d846) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main     #785   +/-   ##
=======================================
  Coverage   77.74%   77.74%
=======================================
  Files          41       41
  Lines        2184     2184
  Branches      417      417
=======================================
  Hits         1698     1698
  Misses        458      458
  Partials       28       28


fix smoke test for HB

I already had a PR for it, but since you added one more file I will cancel mine and we take yours.

Sorry, I still have to wake up fully ;-)

My bet is that readme.v requires no "sed line" in order to work if HB is installed system wide, let's see if CI agrees.

Well you anyway know best which files to pick - I more or less throw dice when picking smoke test files.
I thought about having something in opam to denote a "look at this first example file". I think it would in general be useful information for users.

I think you did a good job and I did advertise your script to a jscoq dev wanting to do a smoke test as well.
W.r.t. HB you picked the hardest example, which is ok. The one I've added, readme.v, is the one we use for the README.md: it is much simpler but we try to keep it up to date.

@gares : I think we need something like:
TEST_FILES[coq-hierarchy-builder]='demo2/classical.v demo2/stage10.v demo2/stage11.v'
COQ_OPTION[coq-hierarchy-builder]='-Q . demo2'

Yes, but I also adjusted the regexp.

Ah ok, I forgot about teh AWK script. I think one or the other should be good enough (either coq options or patching the requires).

finally ok


Update utils.py

The HTTPNotModified exception of aiohttp correctly [1] does not set the location attribute in the response.
This causes an AttributeError in aiohttp_debugtoolbar/middlewares.py, at line "if response.status in REDIRECT_CODES and response.location:".
The proposed solution is removing the 304 code from the following line in the utils.py file and using the HTTP codes constants [2], i.e. from:
REDIRECT_CODES = (301, 302, 303, 304)
to:
from http.client import (
MOVED_PERMANENTLY,  # 301
FOUND,  # 302
SEE_OTHER)  # 303
REDIRECT_CODES = (MOVED_PERMANENTLY, FOUND, SEE_OTHER)
I'm against a change like the following one in middlewares.py, from
"if response.status in REDIRECT_CODES and response.location:"
into
"if response.status in REDIRECT_CODES and getattr(response, 'location', None):"
because http.client.NOT_MODIFIED (304) responses do not make provision for a "Location" Response header.
[1] http://www.w3.org/Protocols/HTTP/HTRESP.html
[2] https://docs.python.org/3.5/library/http.html#http-status-codes

+1 for dropping 304 status code.
-1 for using constants from http package. Numeric values are very well known and wide spread.
Full list of codes with location header is [300, 301, 302, 303, 305, 307, 308] according to source code.

+1 adding also 305, 307, 308 ([300, 301, 302, 303, 305, 307, 308]) !
Let's hope it will be merged soon ;)

Merged. Thanks!


Math magicians: events

In this PR I have:

Created a new directory called logic inside my project
Copied the files calculate.js and operate.js into my logic/ directory
Import calculate.js in your Calculator.js component
Implement click event handlers using the math logic from calculate.js and operate.js in my React component
Made all calculator buttons work according to their functionality

@roodjinocherilus
The key Features section of the ReadMe is not filled. Kindly add 1 -3 features of your app in the ReadMe. Asap pls!

@roodjinocherilus
Key Features section is still empty


Uncaught (in promise) SyntaxError: import not found: default

Hi, I had read your note.
I have a problem when I used both @googlemaps/markerclusterer and nuxt 3, and I don't know where the error comes from.
When I write import { MarkerClusterer } from "@googlemaps/markerclusterer"; then browser show error:
Uncaught (in promise) SyntaxError: import not found: default [index.esm.js:2:7]
the bug in the line of code: import equal from '/_nuxt/node_modules/fast-deep-equal/index.js?v=fafab82c';
Thanks for reading.

I have the same issue.

Same issue here as well. Also with Nuxt 3.
Full error here:
Uncaught SyntaxError: The requested module '/_nuxt/node_modules/fast-deep-equal/index.js?v=86369042' does not provide an export named 'default' (at index.esm.js?v=86369042:1:8)

any changes? who can fix it?

Any updates?

How can i help to somebody fix this?

@websitevirtuoso @chaule97 Here's a fix for you guys
In your nuxt.config.ts file
export default defineNuxtConfig({
	// ...other config keys
	vite: {
		optimizeDeps: {
			include: [
				'fast-deep-equal',
			],
		},
	}
});

The issue is because the dependency fast-deep-equal is not supporting esm build and is currently exporting a cjs version. Check here - https://github.com/epoberezkin/fast-deep-equal/pull/105.
Vite being an esm only tool requires extra config to process cjs packages.

We know how to fix it. but them problem that this is patch. It should be applied in the lib. We just need to wait while fast-dee-equal lib will have ESM version

This problem also happens if one is importing MarkerClusterer in vanilla js and without using Nuxt. For example I'm trying to import it in my script using a relative path to my node_modules folder like this:
import { MarkerClusterer } from<EMAIL_ADDRESS>
And I get this error in browser console:
Uncaught TypeError: Failed to resolve module specifier "fast-deep-equal". Relative references must start with either "/", "./", or "../".
It's annoying and wasted couple of hours of my time!


We forgot 4.3-released case

What does this PR change?
While reviewing sumaform's code with Julio, we noticed those two places where 4.3-released case has apparently been forgotten. This PR fixes that.
Note: to avoid this problem in the future, it could be a good idea to refactor, testing contains(..., '-released') to cover all 4.x-released cases, while taking care of the fact that uyuni-released also exists.

Waiting for Can's approval to merge.


Implement Golden ATX

Motivation

Closes #2174

Changes

Implement Golden ATX
Adjust unit tests for Golden ATX

Test Plan

[x] Unit tests

[x] System tests

TODO

[X] Implement Golden ATX for PrevATX field
[X] Implement Golden ATX for PositioningATX field
[x] Adjust unit tests for Golden ATX
[x] Ensure that system tests pass.


2022 hero background video

home page hero banner updated with new video

Hi @DmytroPopovSSA, here are the issues I found:

[ ] The old placeholder image of the Bay Bridge is still visible. It flashes for a brief moment while the page loads. Please replace with the new JPG of the "Reactathon in the park" hero image
[ ] The video does not fit the frame. Please update parameters so that it fits.

Note: please preview your deploys (under "checks" above, the "deploy/netlify - Deploy Preview Ready!". Click the "Details" button and you'll see the deploy preview.
Here's a video of what I'm seeing:
https://www.loom.com/share/6cb9d41a4e1f4dc797e47334e2f4e85c

the issues are fixed


freshrss: 1.23.1 -> 1.24.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/FreshRSS/FreshRSS/releases.
meta.description for freshrss is: FreshRSS is a free, self-hostable RSS aggregator
meta.homepage for freshrss is: https://www.freshrss.org/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 1.24.0 with grep in /nix/store/g7ryvfa6d5290mmda5ql2q0pjnjwa6l4-FreshRSS-1.24.0
found 1.24.0 in filename of file in /nix/store/g7ryvfa6d5290mmda5ql2q0pjnjwa6l4-FreshRSS-1.24.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

freshrss

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/g7ryvfa6d5290mmda5ql2q0pjnjwa6l4-FreshRSS-1.24.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A freshrss https://github.com/r-ryantm/nixpkgs/archive/10178dce6197b1f1e1295ba406d3f85bdadcf29b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/10178dce6197b1f1e1295ba406d3f85bdadcf29b#freshrss

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/g7ryvfa6d5290mmda5ql2q0pjnjwa6l4-FreshRSS-1.24.0
ls -la /nix/store/g7ryvfa6d5290mmda5ql2q0pjnjwa6l4-FreshRSS-1.24.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

freshrss

Maintainer pings
cc @etu @Stunkymonkey for testing.

Result of nixpkgs-review pr 314000 run on x86_64-linux 1

1 package built:

freshrss


style: fix center alignment

Description
Center align the layout , and reformat code
Related issues
Fixes #4861
Screenshots

Before

After

Thank you @pratyaksh1610! :tada:


Revert changes to scope inspector window

VSCode Version: 1.43.1
OS Version: macOS 10.13.6

I noticed that recently the layout and styling have changed for the window that is displayed when you run the Developer: Inspect Editor Tokens and Scopes command. I believe the format is now much less readable than it used to be.
Here's what the window used to look like:

I don't have an apples to apples comparison, but here are a couple examples of what it looks like now.

Observations:

The json object in the foreground information at the bottom of the window often gets wrapped in awkward ways, especially if you're near the right edge of the editor.
The nested TextMate scopes are much easier to read if they are left justified instead of right justified. I find the the bulleted list with left-justification in the original design to be much more readable.
In the new layout, the TextMate scopes section and the foreground section blur together, because the dividing horizontal lines that were in the old layout have been removed.

My examples may be a little contrived, but I've seen similar display issues during my normal workflow.

I believe this is the same issue, but currently the scope inspector sometimes looks like this:

Which is essentially unusable. Even on an ultrawide monitor it doesn't always fit.

The sizing issue has been tackled by https://github.com/microsoft/vscode/issues/95936.
We have no plans to revert the changes. With the semantic token information to be shows as well, it was necessary to make things more compact (and more consistent)


ARROW-13812: [C++] Fix Valgrind error in Grouper.BooleanKey test

Essentially, this failure boils down to: when generating the array of uniques for booleans, we pack 8 bytes at a time into one byte. The bytes are packed from what turns out to be a scratch array allocated by TempVectorStack, which does not initialize its memory. So when we have a non-multiple-of-8 number of bytes, we may end up packing initialized bytes and uninitialized bytes together into a single garbage byte, resulting in Valgrind complaining.

@github-actions crossbow submit test-conda-cpp-valgrind

@github-actions crossbow submit test-conda-cpp-valgrind

@ursabot please benchmark


DNEXT-23525: Fix the failed sample on the Docker container.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: raghu-madat:x: Shaik Nayab RasoolShaik Nayab Rasool seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Union operator

This is currently lacking. Possibly it could be as simple as:
from employees
union
from managers

What about other set operators? It seems like difference and intersect aren't discussed as well.

for the "union", we may need to consider both "union" and "union all".

Hi,
I have been thinking about this have a proposal which may be a bit of a departure from SQL but which I think could get us some benefits.
SQL allows table expressions/subqueries in a number of places, like on either side of a JOIN, UNION and in (correlated) subqueries. Leaving the correlated subqueries aside for the moment, I think that part of the reason may be that these were available before the introduction of CTEs. Coming at it from a more modern perspective I question whether we still need that flexibility.
My understanding (mostly from responses to issues rather any look a the compiler code) is that the PRQL compiler works by applying successive transformation functions to frames and producing new frames. By the sounds of it this follows the Fluent Interface data api pattern akin to how you would construct a pipeline in Pandas or Ibis.
I think this is quite a good choice and propose that we stick to this fluent interface API because I because it keeps the flow simple and linear. I also think that there is no loss of generality because what we're giving up can be achieved with CTEs.
So rather than
from employees
union
from managers

we have
table t2 = (
    from managers
)

from employees
union t2

or simply
from employees
union managers

(I have more, just posting this as running out of battery.)

The way I think of it is that you essentially have one main pipeline and any other sub-pipelines that you require you need to factor out into table expressions/CTEs.
I think this is also a place where we could innovate a bit over SQL and introduce some additional ergonomics. For example one nuisance with UNIONs is that you have to have compatible columns. With some knowledge of the table and column types we could generate unions or intersections of column names automatically.
table t1 = (
   from X
   select a, b
)

table t2 = (
   from X
   select b, c
)

from t1
union all:true columns:intersection t2

could be translated to
(SELECT b FROM t1)
UNION ALL
(SELECT b from t2)

and
table t1 = (
   from X
   select a, b
)

table t2 = (
   from X
   select b, c
)

from t1
union all:false columns:intersection t2

could be translated to
(SELECT a, b, NULL as c FROM t1)
UNION
(SELECT NULL as a, b, c from t2)

Lastly, perhaps the columns parameter could also take an explicit list of column names, like
from employees_america
union all:false columns:[uuid] employees_europe employees_asia employees_africa

gets transpiled to
(SELECT uuid FROM employees_america)
UNION
(SELECT uuid FROM employees_europe)
UNION
(SELECT uuid FROM employees_asia)
UNION
(SELECT uuid FROM employees_africa)

This might be useful for unioning together partitioned tables, especially if the table identifiers could be generated with some sort of glob or regex expression.
Perhaps we should rather apply the YAGNI principle and wait until someone actually requests these extensions. I don't have a use case for them personally myself. We do need to have a union operator though with some priority, as it's needed for recursive CTEs (see #407). The recursive CTE requirement might need some refinement of this union proposal but I'll address that separately.

@zopieux I think intersect and difference can be achieved with sem joins and anti joins. I'm not sure how widely supported those are but there are correlated subquery patterns with EXISTS that can work around this. This will require backend adaptor specific code though so I think we should rather address this in a separate issue in order to keep the union implementation simple. I will open an issue for those.

https://github.com/prql/prql/issues/656#issuecomment-1174713630 has some good suggestions.
The UNION operation is fairly different from most operations in SQL, so it makes sense that it feels a bit foreign.
I don't have strong views between

from employees
union
from managers

and

from employees
union managers

...probably with a mild preference for the second.
Ideally we can still have an inline pipeline with
from employees
union (
  from managers
  derive x = foo
)

I think we can have a single positional parameter for all / distinct / intersect (which means a bare union won't work).
Does that seem like a reasonable first implementation? (Without having strong views on the more advanced suggestions in the later comments)

Just realizing that union would be a function that can take two tables as arguments, which means that it can also be called as:
union (
  from employees
) (
  from managers
  derive x = foo
)

or more concise:
union (from employees) (from managers | derive x = foo)

Do you think it should be more a function that takes two parameters[^1] — or like a transform like join is, connecting the pipeline above?
[^1]: or a list

I'm saying that these two things are the same :smile: !
from employees
union (from managers | derive x = foo)

... is equivalent to:
union (from managers | derive x = foo) (from employees)

Yes, great point!
Technically, we can't then have a list; we'd need exactly two parameters (or to change how we do parameters).

Closed by #894
Related work continues on #761


Add "epsilon DNA polymerase complex" as child of "replisome"

I realise this has been discussed before:
https://github.com/geneontology/go-ontology/issues/14691
and the decision was to remove this 'part of' relationship:
id: GO:0008622
name: epsilon DNA polymerase complex
relationship: part_of GO:0043601 ! nuclear replisome
But every recent review/paper I've read asserts that DNApol epsilon is part of the replisome, for example:
Jain et al 2018 (PMID: 30005324)
Yeeles et al 2017 (PMID: 27989442)
Burgers & Kunkel  2017 (PMID: 28301743)
Bai et al 2017 (PMID: 29357060)
Yurieva and O'Donnell 2016 (PMID: 27416113)
It was noted in #14691 that the Burgers & Kunkel review says "Collectively, these results strongly suggest that in undamaged yeast cells, the leading strand is primarily replicated by Pol ε".  I think just reflects that there's evidence that both POL delta and epsilon can act as the leading strand polymerase, and that the cell may switch between the two depending on circumstances.  I don't believe there's any debate that POL epsilon is part of the so-called "replisome" - but we could always write to couple of experts if we need to check.
@mah11
@krchristie
@hattrill

The linked ticket acknowledges that eukaryotic replisomes usually contain Pol ε, but also notes that Pol ε can be found elsewhere. That was, and remains, the reason why we can't add back GO:0008622 part_of GO:0043601.
The comment thread also revealed what appeared at the time to be the possibility that eukaryotic replisomes lacking Pol ε could exist. If that possibility can be reliably excluded, then the link replisome GO:0043601 has_part Pol ε GO:0008622 could be added. I'm happy to take expert input on this point.

@sjm41 - @mah11 has said pretty much what I would have said. Do you have any info that there are replisomes that lack Pol ε? If it is true that ALL replisomes contain Pol ε, then as @mah11 said, we could add a has_part relationship to say that
nuclear replisome (GO:0043601 ! )
has_part: epsilon DNA polymerase complex (GO:0008622)
If you have found evidence to support this statement, please provide the PMID of the reference. Otherwise, I really don't think there is anything we can do because we can only add either a has_part or a part_of relationship to the ontology if either statement is ALWAYS true.

Thanks both.
I provided 5 recent PMIDs in my original post that assert that Pol ε is a canonical member of the 'replisome'.  (A researcher using 'nuclear replisome' as as search term would certainly expect to find annotations to Pol ε, IMO.)  So I still think adding the has_part of relationship is the right thing to do.
It would be very hard to find evidence that Pol ε is ALWAYS part of the replisome, no exceptions.  But if there was clear evidence that functional replisomes lacking Pol ε exist, then I guess that would settle the issue.  Do we know of any PMIDs clearing stating that point?

Stephen has a good point that researchers would expect to find pol E under "replisome"
but has_part won't help either, because annotations are not transitive over has_part.
This is a general issue.
So at pombase we have 95 gene products annotated to nuclear replication and I think most  of these would be considered "replisome" - but only 18 annotated to "replisome"
Are there any plans to address inconsistencies of this type through inference?
@pgaudet
@cmungall

Nuclear replisome currently has the children

Child Term
Relationship to GO:0043601

GO:0005662    DNA replication factor A complex
part_of

GO:0043599    nuclear DNA replication factor C complex
part_of

GO:0005658    alpha DNA polymerase:primase complex
part_of

GO:0043625    delta DNA polymerase complex
part_of

Is the same not true of these?

The same problem will exist for all multi-component terms?
Also since polE is essential  for replication mustn't it always be a component of the replisome?

Nuclear replisome currently has the children

GO:0005662    DNA replication factor A complex 	part_of
GO:0043599    nuclear DNA replication factor C complex 	part_of
GO:0005658    alpha DNA polymerase:primase complex 	part_of
GO:0043625    delta DNA polymerase complex 	part_of

Is the same not true of these?

None of those complexes have been observed in a DNA repair complex instead of a replisome, whereas Pol ε has. At least, that's what the current ontology structure implies. If any of the other complexes do turn up in a repair complex or any other non-replisome context, then its 'part_of replisome' link would have to be removed.

Also since polE is essential for replication mustn't it always be a component of the replisome?

This question is ambiguous regarding which direction "always" applies.
The question under consideration in earlier comments (https://github.com/geneontology/go-ontology/issues/17723#issuecomment-522782703, https://github.com/geneontology/go-ontology/issues/17723#issuecomment-522888422) is whether any normal replisomes exist without Pol ε. If not, then the replisome always contains Pol ε, and the has_part link can be added.
As for Pol ε existing outside a replisome, see above re DNA repair.

None of those complexes have been observed in a DNA repair complex instead of a replisome, whereas Pol ε has.

OK I missed this part!
Anyway if this is essential for replication the has_part can be added. However ,this won't help us to get this complex included in the replisome annotation set.

Anyway if this is essential for replication the has_part can be added. However ,this won't help us to get this complex included in the replisome annotation set.

The criterion for adding has_part is whether or not a replisome ALWAYS contains Pol ε, not whether Pol ε is essential for replication.

Sounds like Pol ε always is always part of the replisome - ie being a canonical part should be sufficient?
I usually ask @bmeldal about this kind of issue.
Pascale

Thank for the vote of confidence, @pgaudet ! Unfortunately, I am not the "almighty See" and don't know every complex's function ;-)
I can't add much more here. If you look at the human entry in UniProt you see a long list of Reactome reactions including the DNA repair pathway, which lets me to conclude that it certainly exists away from the replisome. Whether it's a obligate constituent of of the replisome I can't tell and don't have the time to read into it. Whoever annotated those complexes in CP didn't add much detail (yeast entry).
has_part - probably
part of - definitely not
Sorry.

This may come down to viruses....at least, DNA viruses that replicate in a host cell nucleus (like SV40).
As mentioned, everything I've read says that Pol epsilon is present and required at nuclear (eukaryotic) replication forks.
Here are two more recent reviews (to add to my previous list):
The Eukaryotic Replisome Goes Under the Microscope 2016 (PMID: 27003891)
DNA polymerase epsilon - more than a polymerase. 2003 (PMID: 12806123)
However, that second reference has a section called "POL ε IS INVOLVED IN REPLICATION OF CELLULAR DNA" that says "The SV40 replisome can be considered the prototypic core replication apparatus in the eukaryotic cell" and the SV40 system only needs Pols alpha and delta (no epsilon). It then goes on to say "The validity of the SV40 DNA replication system as a model of cellular DNA replication is challenged by research done with cellular systems. The catalytic subunit of Pol ε is essential for viability in budding and fission yeast, and temperature-sensitive mutants fail to replicate chromosomal DNA at the restrictive temperature".
A review I found specifically on SV40 replication (PMID: 19101707) says two things of interest:
i) DNA polymerase epsilon is important for chromosomal replication (Seki et al., 2006; Shikata et al., 2006), but SV40 replication does not utilize it in vivo or in vitro (Pospiech et al., 1999; Zlotkin et al., 1996).
ii) though Fig 7 shows "a minimal set of replication proteins at a eukaryotic fork", which includes Pol epsilon.
So...if "nuclear replisome" (GO:0043601) is meant to include SV40-like replisomes, then Pol epsilon should not be part of it.
But if "nuclear replisome" is meant to refer to regular, eukaryotic/nuclear/cellular-based replisomes, then it should, AFAIK.

Hmmm...
If we DO need to represent any possible "nuclear replisome", including the ones that include SV40 virus, then as you say we couldn't add Pol epsilon as a part_of "nuclear replisome".
While we could have an upper level term for any "nuclear replisome" and then have more specific terms for an "SV40 type nuclear replisome" and a "eukaryotic nuclear replisome", e.g.
-- nuclear replisome
--- eukaryotic nuclear replisome
--- SV40 type nuclear replisome
However, this is often problematic with respect to annotations since annotators who want to annotate a regular, i.e. non-viral eukaryotic nuclear replisome, are unlikely to even notice the child term for "eukaryotic nuclear replisome". If we did this, I think we might want to mark the term "nuclear replisome" as a "Do NOT annotate" term so that people couldn't use it. Otherwise, we'd end up with all/most of the "regular" eukaryotic annotations made to the top level term.
So, as @sjm41 pointed out, resolution hinges on whether we need to make the term "nuclear replisome" broad enough to include SV40 type nuclear replisomes.
thoughts?? @pgaudet @ukemi  anyone else?

Disscussed in Ontology Editors' call on 9/9/19
It was brought up that we have a division between a "regular" cell and a host cell. Looking at the ontology, we have terms for nucleus and host cell nucleus; there is no relationship between nucleus and host cell nucleus because it causes problems, if I recall correctly. Thus a term that would need to accodomate the composition of an SV40 viral replisome, would be related to the host cell nucleus term, while the term under discussion nuclear replisome is defined with respect to the term nucleus. With this in mind, and having just looked at the ontology, I think that we can add this relationship:
nuclear replisome
has_part epsilon DNA polymerase complex
@pgaudet - Do you still want to tag Patrick for additional input?

Hi @krchristie
I think the viral replisome should be annotated to 'replisome' and 'host cell nucleus' separately  - @pmasson55 is that OK ? I find no viral annotations to 'replisome' or children.
BTW this is a nice recent review for the composition of the different replisomes:
PMID:31273608, figure 1. We should add it as a cross-reference.
Pascale

Hi,
We actually never used the term viral replisome, instead we used bidirectional double-stranded viral DNA replication for example for herpes viruses or SV40 viral proteins involved in replication.  I'm fine with removing the term viral replisome. Concerning the host proteins that could be of importance for viral replication, they should be tagged with their physiological function I guess and not with viral terms (there are taxonomic constraints anyway, right?)... Maybe host-virus interaction if there is a relevant interaction...Hope this helps.
Patrick.

Thanks for the input @pgaudet and @pmasson55
There is no go term for viral replisome, just for replisome, cytoplasmic replisome, and nuclear replisome. It sounds like there is an effective strategy for annotating viral proteins involved in replication, and also that the term nuclear replisome is intended specifically for the normal complex that occurs in cells with nuclei, without needing to deal with viral replication complexes.
Thus, I can go ahead and add this relationship:
nuclear replisome
has_part epsilon DNA polymerase complex

Thanks Karen!


Add option to choose installation directory for nbdev_install_hooks

When trying to run nbdev_install_hooks, I get
PermissionError: [Errno 13] Permission denied: '/home/azureuser/.jupyter/jupyter_notebook_config.py'
The reason is that I work in an Azure Machine Learning workspace, where no users have access to their home directory.
I think this could open up nbdev to a large user-base that really needs it. 🙏
Proposed solution:

Add hook_install_path option to the settings.ini-file.

Where do you store your own jupyter_notebook_config.py? Do you use Jupyter-specific environment variable(s) to set that? I'd prefer if we made nbdev_install_hooks use the same environment variables instead of adding another setting.


finish cleaning up the staging stuff

The main stage UI was removed as obsolete, but much plumbing remains in the client that ought to be cleaned up.

IT IS DONE.


Engine -> FW Roller tests pending for 2 days

see: https://github.com/flutter/flutter/pull/91946

Related to: https://github.com/flutter/flutter/issues/92107


Recursion when importing cv2 from debugger

Expected behaviour
No recursion
Actual behaviour
ImportError: ERROR: recursion is detected during loading of "cv2" binary extensions.
Steps to reproduce

pip install "opencv-python>=4.6" (works with 4.5)
ipython
%debug import cv2
n

Python 3.9.12 (main, Mar 26 2022, 15:52:10)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.34.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: %debug import cv2
NOTE: Enter 'c' at the ipdb>  prompt to continue execution.
> <string>(1)<module>()

ipdb> n
['/usr/local/bin'<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>'', '/usr/local/lib/python3.9/site-packages', '/Users/quentinpeter/pyscripts/spyder', '/Users/quentinpeter/pyscripts/spyder/external-deps/qdarkstyle', '/Users/quentinpeter/pyscripts/spyder-kernels', '/usr/local/lib/python3.9/site-packages/IPython/extensions', '/Users/quentinpeter/.ipython']
ImportError: ERROR: recursion is detected during loading of "cv2" binary extensions. Check OpenCV installation.
> <string>(1)<module>()

ipdb>

example code
operating system
architecture (e.g. x86)
opencv-python version

Issue submission checklist

[x] This is not a generic OpenCV usage question (looking for help for coding, other usage questions, homework etc.)

[x] I have read the README of this repository and understand that this repository provides only an automated build toolchain for OpenCV Python packages (there is no actual OpenCV code here)

[ ] The issue is related to the build scripts in this repository, to the pre-built binaries or is a feature request (such as "please enable this additional dependency")

[x] I'm using the latest version of opencv-python

See https://github.com/spyder-ide/spyder/issues/18581

Hello @impact27!
I see that this problem happens only with ipython. I've reproduced it in ipython even not in a debug mode, but if to use just python interpreter, it doesn't happen.
If to say about the line in opencv with l_vars = locals(), it was the same even in the previous release.
Maybe something wrong with locals(), it's different in python interpreter and ipython.

python interpreter:

>>> print(locals())
{'__name__': '__main__', '__doc__': None, '__package__': None, '__loader__': <class '_frozen_importlib.BuiltinImporter'>, '__spec__': None, '__annotations__': {}, '__builtins__': <module 'builtins' (built-in)>}

ipython:

{'__name__': '__main__', '__doc__': 'Automatically created module for IPython interactive environment', '__package__': None, '__loader__': None, '__spec__': None, '__builtin__': <module 'builtins' (built-in)>, '__builtins__': <module 'builtins' (built-in)>, '_ih': ['', 'print(locals())'], '_oh': {}, '_dh': [PosixPath('/')], 'In': ['', 'print(locals())'], 'Out': {}, 'get_ipython': <bound method InteractiveShell.get_ipython of <IPython.terminal.interactiveshell.TerminalInteractiveShell object at 0x7f081aac3c70>>, 'exit': <IPython.core.autocall.ExitAutocall object at 0x7f081aabdfd0>, 'quit': <IPython.core.autocall.ExitAutocall object at 0x7f081aabdfd0>, '_': '', '__': '', '___': '', '_i': '', '_ii': '', '_iii': '', '_i1': 'print(locals())'}

Promotion to 4.x: https://github.com/opencv/opencv/pull/22305


Use 3 letters month prefix in default date format

Using 3-letters month name is clear enough and allows for a smaller and even x axis margin on line charts.

Codecov Report

Merging #4693 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #4693      +/-   ##
==========================================
+ Coverage   71.52%   71.53%   +<.01%
==========================================
  Files         190      190
  Lines       14927    14929       +2
  Branches     1102     1102
==========================================
+ Hits        10677    10679       +2
  Misses       4247     4247
  Partials        3        3

Impacted Files
Coverage Δ

superset/assets/javascripts/modules/dates.js
86.04% <100%> (+0.68%)
:arrow_up:

Continue to review full report at Codecov.

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


Does not appear to work correctly with vim-tup

I'm trying to use this with vim-tup to put license headers on my Tupfiles. However, when I use a license-adding command (such as :Gpl), it gives C-style comments instead of tup comments. Syntax highlighting for comments works correctly, and the filetype is set to tup correctly. I'm using the latext Neovim (--version gives v0.2.0).

This is probably caused by the comments setting not set in this vim-tup plugin.
Try setting it to see if it fixes the issue.
You might want to use an autocmd or make a pull request in this plugin.

@antoyo I'm not surprised, given its age. I don't know exactly how to set this setting - what exactly does it have to say?

I don't know this tup format, but try something like this:
set comments=s1:{-,mb:-,ex:-}

where {- is the start of a comment, - is the middle (inserted at every line) and -} is the end of a comment.
For a language supporting only single-line comment, try something like that:
set comments=:--

where -- is the start of a single-line comment.

I have sent a PR for this upstream. Thank you for your help - will close this.


Help tags (WIP)

Changes proposed in this pull request:

help tags for toolbar
help tags for column properties

fixes #62

@Stephen-Gates
From what i can see the tooltip directive doesn't seem to respond to style. May have to just add in bind style to vue property. If you want this in for this release, I can do but without style changes for now and updated mixins for style after

@mattRedBox add as is and we'll fix later


[WIP] Fixed #30974 -- Use wait in favor of assert in Selenium tests

https://code.djangoproject.com/ticket/30974

buildbot, test on selenium.

buildbot, test on selenium.

buildbot, test on selenium.

OK, I see where you're going with this. Not 100% convinced we can't reasonably assert, perhaps being more careful with our waits… (to discuss).

Yes, I did kind of fall into a rabbit hole here. Then again, we would consider race conditions bugs in any other part of the code base. Maybe the wisest approach is to fix the places where if fails often.
The once I fixed so far are the once that failed for me every often when running locally on and GitHub actions.

Can you fix the TypeError failures?

Done

I'm going to close this assuming that we'll go with #12152. (But shout there if you have more input!) Thanks for the effort on all these tickets!


[MXNET-9704] An assertion check for invalid layout

Description
a fix for issue #9704
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[X] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
I don't know how to test for this one. A nasty testing script is posted downside.
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
This link is broken. Please update it.
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] assertion check for invalid layout of conv and pooling layers.

Comments
Assertion check for conv and pooling with documents updates. The pooling assertions was added by someone else before. I'm not sure if other layouts are supported too.
@gianlucacorrado @zhreshold @anjishnu
a nasty debug script is posted here. feel free to modify it.
import sys
sys.path.insert(0,'../incubator-mxnet/python')
from mxnet import nd
from mxnet.gluon import nn
from mxnet import gluon

a = nd.zeros((5,2,10))
conv1 = nn.Conv1D(5,1)
conv1t = nn.Conv1DTranspose(5,1)
pool1_ave = nn.AvgPool1D()
pool1_max = nn.MaxPool1D()
pool1_ave_g = nn.GlobalAvgPool1D()
pool1_max_g = nn.GlobalMaxPool1D()
conv1.initialize()
conv1t.initialize()
print(conv1(a).shape)
print(conv1t(a).shape)
print(pool1_ave(a).shape)
print(pool1_max(a).shape)
print(pool1_ave_g(a).shape)
print(pool1_max_g(a).shape)

a = nd.zeros((5,2,10,10))
conv2 = nn.Conv2D(5, (1,1))
conv2t = nn.Conv2DTranspose(5,(1,1), layout='NHWC')
pool2_ave = nn.AvgPool2D()
pool2_max = nn.MaxPool2D()
pool2_ave_g = nn.GlobalAvgPool2D()
pool2_max_g = nn.GlobalMaxPool2D()
conv2.initialize()
conv2t.initialize()
print(conv2(a).shape)
print(conv2t(a).shape)
print(pool2_ave(a).shape)
print(pool2_max(a).shape)
print(pool2_ave_g(a).shape)
print(pool2_max_g(a).shape)

a = nd.zeros((5,2,10,10,10))
conv3 = nn.Conv3D(5, (1,1,1))
conv3t = nn.Conv3DTranspose(5,(1,1,1), layout='NDHWC')
pool3_ave = nn.AvgPool3D()
pool3_max = nn.MaxPool3D()
pool3_ave_g = nn.GlobalAvgPool3D()
pool3_max_g = nn.GlobalMaxPool3D()
conv3.initialize()
conv3t.initialize()
print(conv3(a).shape)
print(conv3t(a).shape)
print(pool3_ave(a).shape)
print(pool3_max(a).shape)
print(pool3_ave_g(a).shape)
print(pool3_max_g(a).shape)

@szha I am not quite sure about current supported formats. Do you have any source?

Needs to check for the used operators. For convolution: https://github.com/apache/incubator-mxnet/blob/master/src/operator/nn/convolution-inl.h#L99-L103

@zhreshold The conv layers have a second round layout check, so I added the assertion according to that check. However, the pooling layers seems don't have that check.

LGTM.


⚠ Processors has degraded performance

In f0d0a9c, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 54 ms

Resolved: Processors performance has improved in f2c55c3.


Update new-winuserlanguagelist.md

Fixed typo
Resolves issue #526

@doctordns - thank you for fix, much appreciated!


formatCardNumber is allowing 19 characters

I am using version 2.0.3
Payment is allowing 19 characters for visa type card numbers.

And that is correct according to:
https://en.wikipedia.org/wiki/Payment_card_number
Visa lengths: 13, 16, 19

Ah thank you @Yottster , I did not know that.


Prototype docker-based importers for Go and JS

I don't know docker that well, but I have a feeling that there exists (or could be made) a "golang+git" docker container that allows one to do something like:
docker run https://github.com/attic-labs/noms/samples/go/url-fetch http://data.gov/foo.csv http://localhost:8000::foo/data

... and what it would do is clone that repo with git, build it as a go binary, and run it with the arguments specified.
If we had this, it would form the basis of generic 3rd-party importers.

You want something like:
$ echo 'FROM golang:alpine

RUN apk add --no-cache git
ENV SAMPLE url-fetch
RUN go get -u github.com/attic-labs/noms/cmd/noms
RUN go get -u github.com/attic-labs/noms/samples/go/${SAMPLE}

ENTRYPOINT ["url-fetch"]' | docker build -t noms/import -
...
Successfully built dc8a89534ed1

to use: (warning will consume 130MB down)
$ docker volume create --name nomsdata
$ docker run -ti noms/import \
    -v /data
    "https://s3.amazonaws.com/ed-college-choice-public/Most+Recent+Cohorts+(All+Data+Elements).csv" \
    ldb:///data::foo

then you can followup with volume:

Cool, thanks for the start.

@zcstarr - this might be relevant to your interests.

I'm going to close this in favor of more specific things.


If the script does not load, the elements stay hidden

Is it possible that the elements will not hide if the script is not loaded?

It looks like AOS will apply a .aos-init when it is loaded, so you could likely apply the initial hidden style to .element-to-animate.aos-init (much like the fine completed animation state is applied to .element-to-animate.aos-animate).
Here's an example from my SCSS:
.row--plates {   &.aos-init {     opacity: 0;     transition-property: transform, opacity;     transform: scale(.6);     transition-duration: 3s;   }   &.aos-animate {       opacity: 1;       transform: translate(0, 0) scale(1);     }   } }

Elements are being hidden right away in css @sylvaindev to not cause weird flashing of those elements. Otherwise they would appear for a second or so, then disappear and after that animate - which would look strange. If you need to show them on start I suggest you simply check AOS styles, and override them or write your own ;)


fail on console.error

PR to fix #255
Help wanted :)

I tried working on these tests a little earlier today but I couldn't get them to pass. Need more time or insight to debug.

@nylira I did a git bisect, found that the first bad commit is
2492fa6e777602abadc4aa9fc2203a9112c4212e.
On Wed, Dec 20, 2017 at 9:36 AM, Peng Zhong<EMAIL_ADDRESS>wrote:

I tried working on these tests a little earlier today but I couldn't get
them to pass. Need more time or insight to debug.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/cosmos/cosmos-ui/pull/256#issuecomment-353130942, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAYTzdp2Z84TPrPxX5nkitddFrlY83rnks5tCUWagaJpZM4RHHlj
.

@mappum thanks Matt, managed to resolve the issue with that commit id. I should learn how to use git bisect to narrow down the offender.

@faboweb @nylira nice changes! The tests are now passing without issues


CAMEL-11491: Remove mandatory nature of Amazon Clients when accessKey…

… and secretKey are provided

Thanks for the PR it has been merged. Do you mind closing this?


Feature: Mandatory wireguard

According to the docs https://docs.projectcalico.org/security/encrypt-cluster-pod-traffic if a node doesn't support wireguard traffic to/from it won't be encrypted.
I'd like the option to configure calico in such a way that if a node doesn't support wireguard then it's not able to send traffic to other nodes, I'd rather have the network break than send the traffic un-encrypted.
Also it looks like in IPIP mode BGP is made outside of the wireguard tunnel, although I don't actually know if BGP is needed with wireguard as traffic appeared to be routing even though I had a broken peer (it had an RFC1918 IP), Wireguard was working because when it reached out to the public IP of one of the other nodes wireguard updated the endpoint ip address (which it will do if a peer connects with a valid keypair)
Use case is I have a K3s cluster for personal use/learning that spans low end VPS hosts, therefore I want to encrypt all my cluster internal traffic as it's going over the internet rather than a private network.

Yes, I agree this would be nice. We should have a way to say "If you can't send traffic over wireguard, then don't send it at all".
@robbrockbank maybe you could comment on what would be required to make this happen?

We are trying to have the same setup, use wireguard for all in cluster configuration and if wireguard is not running in a node we want the node to break and not send traffic (all our nodes are capable of wg, so for us it would be a matter of debugging why).
The only configuration that allowed us to "hack" such behaviour is to use bird as networking backend, but disable bgp nodeToNodeMeshEnabled config like:
apiVersion: crd.projectcalico.org/v1
kind: BGPConfiguration
metadata:
  name: default
spec:
  logSeverityScreen: Error
  nodeToNodeMeshEnabled: false
  asNumber: 64512

Then we make sure that we do not have any BGPPeer and thus calico cannot discover any peer and any route via bgp.
Ofc, we tune felix to use wireguard with a very simple configuration, like:
apiVersion: crd.projectcalico.org/v1
kind: FelixConfiguration
metadata:
  name: default
spec:
  ipipEnabled: true
  logSeverityScreen: Info
  reportingInterval: 0s
  wireguardEnabled: true

The result is that on each node we have the calico interfaces created for pods and the wg route table seems up to date to provide our routing. For example:
ip route show table 1
<IP_ADDRESS>/24 dev wireguard.cali scope link
<IP_ADDRESS> dev wireguard.cali scope link
<IP_ADDRESS>/24 dev wireguard.cali scope link
<IP_ADDRESS> dev wireguard.cali scope link
<IP_ADDRESS>/24 dev wireguard.cali scope link
<IP_ADDRESS> dev wireguard.cali scope link
<IP_ADDRESS>/24 dev wireguard.cali scope link
<IP_ADDRESS> dev wireguard.cali scope link
<IP_ADDRESS>/24 dev wireguard.cali scope link
<IP_ADDRESS> dev wireguard.cali scope link
throw <IP_ADDRESS>/24

That seems to cover the functionality described in this issue. Are we missing anything or trying to use calico in an unintended setup? @caseydavenport
Finally, it would be nice to be able to just select wireguard as networking backend and not have to do any of the above ^

At a glance, it's not obvious to me why that is working the way that it is, but I don't see anything fundamentally wrong with doing that!
I still think we can do better with a Wireguard mode that doens't require jumping through extra hoops.

Ohh yes @caseydavenport that would be VERY NICE :) - for now we're also trying to "atleast make it work" - this way :)


K3d config file formating

Hi
Im trying to pass a k3d config file but it looks like im not getting the formatting correct looking to pass, any ideas on what the formatting would look like?
k3d: # k3d runtime settings
wait: true # wait for cluster to be usable before returning; same as --wait (default: true)
timeout: "6m0s" # wait timeout before aborting; same as --timeout 60s
disableLoadbalancer: true # same as --no-lb
disableImageVolume: false # same as --no-image-volume
disableRollback: false # same as --no-Rollback
k3s: # options passed on to K3s itself
extraArgs: # additional arguments passed to the k3s server|agent command; same as --k3s-arg
- arg: --disable=servicelb
nodeFilters:
- server:*
- arg: --disable=traefik
nodeFilters:
- server:*
- arg: --tls-san=<IP_ADDRESS>
nodeFilters:
- server:*
- arg: --disable-network-policy
nodeFilters:
- server:*
- arg: --flannel-backend=none
nodeFilters:
- server:*
kubeconfig:
updateDefaultKubeconfig: true # add new cluster to your default Kubeconfig; same as --kubeconfig-update-default (default: true)
switchCurrentContext: true # also set current-context to the new cluster's context; same as `--kubeconfig-switch-

did you look at the example? https://github.com/tilt-dev/ctlptl/blob/main/examples/k3d-config.yaml
when you say "im not getting the formatting correct", can you be more specific about what you tried, what you expected to happen, and what happened instead?

Hey Nicks thank you for the reply, I took a look at the example, I tried several variations of this config file:
`# k3d with an embedded config
apiVersion: ctlptl.dev/v1alpha1
kind: Cluster
name: k3d-testing
product: k3d
k3d:
v1alpha4Simple:
network: custom-network
wait: true # wait for cluster to be usable before returining; same as --wait (default: true)
timeout: "6m0s" # wait timeout before aborting; same as --timeout 60s
disableLoadbalancer: true # same as --no-lb
disableImageVolume: false # same as --no-image-volume
disableRollback: false # same as --no-Rollback
k3s: # options passed on to K3s itself
extraArgs: # additional arguments passed to the k3s server|agent command; same as --k3s-arg
- arg: --disable=servicelb
nodeFilters:
- server:*
- arg: --disable=traefik
nodeFilters:
- server:*
- arg: --tls-san=<IP_ADDRESS>
nodeFilters:
- server:*
- arg: --disable-network-policy
nodeFilters:
- server:*
- arg: --flannel-backend=none
nodeFilters:
- server:*
kubeconfig:
updateDefaultKubeconfig: true # add new cluster to your default Kubeconfig; same as --kubeconfig-update-default (default: true)
switchCurrentContext: true # also set current-context to the new cluster's context; same as --kubeconfig-switch-context (default: true)`
Depending on the variation I get the following error type:
visiting k3d-config.yaml: decoding {Cluster ctlptl.dev/v1alpha1}: yaml: unmarshal errors:
line 14: field k3s not found in type api.Cluster
I would expect it to accept the k3s arguments.

the error message:
visiting k3d-config.yaml: decoding {Cluster ctlptl.dev/v1alpha1}: yaml: unmarshal errors:
line 14: field k3s not found in type api.Cluster

is telling you that you got the indentation wrong and is telling you the exact line to fix. It should look something like:
apiVersion: ctlptl.dev/v1alpha1
kind: Cluster
name: k3d-testing
product: k3d
k3d:
  v1alpha4Simple:
      k3s:
        extraArgs:
            ...

the error message is telling you which fie

Awesome thanks for pointing me in the right direction that worked.


Please support 1.14.4 (Forge)

Any plans?

The update process is incremental and I work mostly on this mod alone. I have seen a pull request with some work towards a 1.13 update, but it is very large and so I haven't been able to review it. 1.14 and later are not yet considered.
Directly from the FAQ:

Q: Where should I make suggestions?
A: The issue tracker is the best place to do so, and you can add the "suggestion" label to make it clear. Suggestions about updating to Minecraft version X are likely to go ignored.

I'd love to see this for 1.14.4 myself since I've moving away from 1.12.2 in favor of 1.14.4 (over 1.13.2) due to the lack of dev support on most of the mods since Forge was not prepared for the massive changes.

I too am interested in 1.14.4 forge update!


为什么不能提供和prometheus 集成的能力

⚠ Please verify that this question has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
可以参考http-runner,https://httprunner.com/docs/user-guide/load-test/monitor/
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.10.0
💻 Operating System and Arch
centos7.6
🌐 Browser
chrome
🖥 Deployment Environment

Runtime:
Database:
Filesystem used to store the database on:
number of monitors:

You forgot to ask a question.
Our prometheus documentation is avaliable here: https://github.com/louislam/uptime-kuma/wiki/Prometheus-Integration


osd: drop filestore support

filestore is about to be removed.
This commit removes the filestore support in ceph-ansible.

jenkins test centos-container-lvm_batch

jenkins test centos-container-all_in_one

jenkins test centos-non_container-collocation

jenkins test centos-container-external_clients

jenkins test centos-container-purge

jenkins test centos-non_container-update

jenkins test centos-non_container-subset_update

jenkins test centos-container-collocation

jenkins test centos-non_container-all_in_one


Use jetty-ee10 instead of jetty-ee9

Follow up for #1392

@liga-oz: Can you please have a look at this PR? This is a follow up of my PR were I migrated to Jetty 12. With this change the latest EE Version is now also used with Jetty 10, enabling Servlet 6 APIs (as is the case with Spring Boot 3)


fix(build): Drop support for Node 0.10 and 0.12.

Updated docs.
Updated engines matcher in package.json.
Updated places where node-0.1-specific code was noted in comments.

Looks like travis was already updated.

Done, please take another look.

Thank you :octocat:


Postgres support: query placeholders, backend detect, error handling.

Use postgres dollar-n placeholders in queries. Also removed some unnecessary Prepare calls.
Postgres support detected by DB file-name prefix: "postgres://user:password@localhost/gigawallet" - Includes error handling for Postgres constraint violation and concurrent-transaction conflicts.
Removed NTx field which Core doesn't return (RpcBlock)

I had to make dbErr helper function a method of the Store so it can find out which backend we're using.
This meant changing every single call site!
But now we support both SQLite and Postgres backends. We probably should rename the store.


support @CustomSerializer of struct types

use for HideFlags to be able to make mValue member private and still serialize correctly

also use for instanceId to make it less verbose in the files


"invalid css" when using SubredditStylesheet.update with minified CSS

Issue Description
I've been trying to create a script that can automatically update the subreddit CSS after minifying it but it seems that it thinks minified CSS is invalid and won't upload it. I'm not sure what the issue is
sub = reddit.subreddit('dota2')
stylesheet = dota.stylesheet

with open('stylesheet.css.mini', 'r') as m:
	newSheet = m.read()
	stylesheet.update(newSheet)

System Information
PRAW Version: 4.0.0

Python Version: 2.7
Operating System: Windows

Does the minified CSS work when saving directly to Reddit?

Yes it does.
On Sat, Dec 3, 2016 at 2:22 AM, Bryce Boe<EMAIL_ADDRESS>wrote:

Does the minified CSS work when saving directly to Reddit?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/praw-dev/praw/issues/681#issuecomment-264625459, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHUZMw5weez3Eh2yaZNtut8PGm3CqV3Jks5rESaqgaJpZM4LDOv3
.

I see that you responded via email. I had edited my previous comment. Can you provide some examples as I've asked for? What exception are you getting?

Ah so it seems like even the normal CSS doesn't work, when the normal CSS does work on the subreddit. The error I am getting is praw.exceptions.APIException: BAD_CSS: 'invalid css' on field 'stylesheet_contents'

Can you please provide as simple as possible example of CSS that doesn't work in PRAW but works through the website? BAD_CSS indicates that Reddit's end is rejecting it, so maybe it's a problem with how you're putting it into python.

Any response to my questions @Vatyx?

Closing due to inactivity. @Vatyx feel free to reopen along with the requested examples.

I think i'm having the same issue. This one-liner won't go through. I think the issue may be with how python, reddit, or whatever handles the ">" as it's the only html artifact in the string.
div#thing_t1_digal4v > div.entry .md:before{ content:'THIS COPYPASTA IS OLDER THAN WUMBO'; color:red; font-style: italic}


Resolve window / app close prompt structure

I implemented a much better structure for close prompts in the commits above, which allows you to call AddCloseDialog to easily add a customizable close prompt that works at the scene level. This makes close prompts much nicer, as you can see in the Cogent Code commit above.


vitepress build error: search function is not working after build

It's working on vitepress dev
when run pnpm run  build
then pnpm run preview
the search is not working, and show these error on console：

app.b342ef59.js:1 Hydration completed but contains mismatches.

online project demo

 "vitepress-plugin-search": "1.0.4-alpha.17",

https://stackblitz.com/edit/vitejs-vite-amht1g?file=src%2Fcomponents.js,docs%2F.vitepress%2Fconfig.js

I have the same problem. When I updated the latest dependency, the error disappeared, but I still could not search in the build environment.

I couldn't replicate this error!
could you share an repo? (couldn't make the stackblitz to work...)

Hi I got the same error. My repo is https://github.com/httpyac/httpyac.github.io#51 but you need to revert commit https://github.com/httpyac/httpyac.github.io/commit/3796c70c97dbfccb681776c1505de41736dc6b97. Maybe it helps.

Hi I got the same error. My repo is https://github.com/httpyac/httpyac.github.io#51 but you need to revert commit httpyac/httpyac.github.io@3796c70. Maybe it helps.

but you try to set it up in docs/.vitepress/config.js ..
it should be in docs/vite.config.ts
it seams the above cases are the same!

@emersonbottero thx. That did the trick. It is some kind of unexpected that configuration also works in config.ts, but only in dev build. Maybe highlight this issue in your readme or add some kind of build warning (if possible) to prevent this issue.

Hi I got the same error. My repo is https://github.com/httpyac/httpyac.github.io#51 but you need to revert commit httpyac/httpyac.github.io@3796c70. Maybe it helps.

but you try to set it up in docs/.vitepress/config.js ..
it should be in docs/vite.config.ts
it seams the above cases are the same!

wow, It works!
 docs/.vitepress/config.ts
 docs/vite.config.ts

But what is the difference between the two settings?

The first one is vitepress configuration specific..
The second one is a vite configuration and uses roll-up lifecycle to change behavior.

@emersonbottero thx. That did the trick. It is some kind of unexpected that configuration also works in config.ts, but only in dev build. Maybe highlight this issue in your readme or add some kind of build warning (if possible) to prevent this issue.

Both versions should work. Is a vite feature.

@emersonbottero thx. That did the trick. It is some kind of unexpected that configuration also works in config.ts, but only in dev build. Maybe highlight this issue in your readme or add some kind of build warning (if possible) to prevent this issue.

I think I can warn! 😁

It works! Thx!!!


[CONTROLLER/SERVICE] add domain-additional-resources api check

This PR is for:

Server

add domain-additional-resources api check
Checklist

[ ] Added unit test.

Backport to branches

main

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.zhengya seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Update fmt.Print to log.Info as well as error output

Updates the logging output that we missed when revamping the UI.
This is the progress in solving the issue: https://github.com/redhat-developer/odo/issues/1102

:white_check_mark: odo build 808 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/50d9c884e9 by @cdrage)

@cdrage Gofmt check failed :)

:white_check_mark: odo build 812 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/b2b65444a1 by @cdrage)

:white_check_mark: odo build 813 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/a449fc9659 by @cdrage)

LGTM let’s wait for CI to complete(I re-triggered a failed job)

@anmolbabu time to review https://github.com/redhat-developer/odo/pull/1134 to get rid of the flake :P

@anmolbabu time to review #1134 to get rid of the flake :P

@geoand Done🙂

@anmolbabu time to review #1134 to get rid of the flake :P

@geoand Done

Thanks!


Stickto right slider not fully opening

Just noticed that when using a sticked to the right sliding layer it never opens completely (check sample app for confirmation). After clicking open and the layer slided to the left you are always able to drag it a bit further to the left. This means on a "pixel-perfect layout" there will always be a little gap visible...
This does not happen on sticked to the left layers.

Hi vincentsys, thanks for your comment!
I'm not really sure about what you mean. The size of the layer depends on the width specified in the layout. If I try to reproduce the steps you mention I'm not able to slide the layer any further. A video or screenshot would help.
Thanks again,
Jose L

Hi Jose,
it seems this effect is only visible on larger screens (tablets). Tested it wis a Galaxy Tab 10" and 7" (KitKat). On a Galaxy S5 (Lollipop) the effect was not visible. It may be tiny but unpleasent.
I've put a red layer of the same size (300dp) behind the sliding layer for better visibility. As mentioned above the red area is fully covered if setup for "stickto left". On the right side insted: If you open the sliding layer and slightly touch/slide it to the left it will move a view pixels. It might be purely screen size dependent as this effect is also visible using ADS virtual devices.

It also seems the same effect appears if stickto bottom ist used. Left and top are alright...

This is very helpful. We'll check that out. Do you want to give it a look as well?

I'll also take a look at it.

Havent't had the time to take a closer look but also noticed this:
stick-to-top and stick-to-left: slider does not fully close
stick-to-bottom and stick-to-right: slider does not fully open
(as mentioned above noticable on larger screens/tablets)

That's valuable information. Thanks @vincentsys

Hi @vincentsys. This is issue should be fixed in upcoming version 1.2.0. Feel free to give it a test to see if it also fixes it in your case.

looks good on first short tests. Thanks!

Good! Thanks to you! This will be closed when further tests are done (either by you or anybody else) and results are acknowledged.


No Endpoints in Interface

Hello, I'm trying to connect my Alesis Keyboard to my computer and see if I can grab the keys being pressed. However, while I can claim the first interface ( interfaces[ 0 ] ), there are no endpoints within that interface. However, the second interface ( interfaces[ 1 ] ) has both InEndpoint and OutEndpoint.  But if I try to claim said interface, it gives me the following error:

Error: LIBUSB_ERROR_NOT_SUPPORTED                                                                                at Interface.claim (D:\Piano Interface\node_modules\usb\usb.js:280:14)                                                  at Object. (D:\Piano Interface\index.js:7:30)                                                                at Module._compile (internal/modules/cjs/loader.js:778:30)                                                              at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)                                                at Module.load (internal/modules/cjs/loader.js:653:32)                                                                  at tryModuleLoad (internal/modules/cjs/loader.js:593:12)                                                                at Function.Module._load (internal/modules/cjs/loader.js:585:3)                                                         at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)                                                      at startup (internal/bootstrap/node.js:283:19)                                                                          at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

I'm not sure how to diagnose this, and was wondering if maybe it has to do with how Zadig recognizes and installs the driver? Within Zadig, the device appears as "Alesis Recital (Interface 0)".
Thanks in advance!

LIBUSB_ERROR_NOT_SUPPORTED usually means that the device does not have the WinUSB driver attached properly (e.g. with Zadig). For composite devices it's a little tricky. There will be multiple entries for the device in Zadig, and you'll need to install it for all the interfaces, or the composite parent representing the device as a whole.
If the default driver is a generic class like HID or MIDI, there may be a more specific library that can access the device without needing to replace the driver.


SocketError

SocketError: Hostname not known: lagotto.local

again, you want this repo https://github.com/lagotto/lagotto/issues


Implemenatation of ReportingBasics class that creates a part of a report

Class is to implement in en.py module that is a reporting component of reporting basics.

Done


Implement enemies AI

Enemies should:
If player is in sight (the same floor), shoot.
If player is not in sight, find elevator in the same floor.
If no elevator in a floor, wait.
If elevator on the same floor, go to elevator.
Once in an elevator, stop moving and based on player Y coordinate, move this elevator up or down.
If player not available (in the red doors) wait.

Done, Elevator class need some refactoring though


[Improvement] Try it online

I have recently added 'try it online badge' for proposed boost.di:
http://krzysztof-jusiak.github.io/di/cpp14/boost/libs/di/doc/html/
I think hana would benefit from this approach as well, especially just before the review.
Possibly more people would be eager to test it and Wandbox is an awesome tool for it (it has clang-trunk and gcc-trunk, boost etc...)
You can find the example with boost.di here:
http://melpon.org/wandbox/permlink/O3ABWKU3VBV3WG8J

This is a great idea. I want this. How do you generate your boost/di.hpp header?

I just found it at pp.sh, right?  I'll try to tweak it for my own use.

Yep, that's the one ;) hehehe, the script was 5 line in the beginning, so couldn't be asked using anything more powerful, but oh well ;) anyway I adopted the script for hana and it actually works, so here you go
main() {
    generate_pph() {
        echo $1 >> $2/tmp.hpp
        cat $1 | egrep "^#include" | grep "boost\/hana" | while read include; do
            file=`echo $include | sed "s/[^<^\"]*[\"<]\([^>\"]*\)[\">].*/\1/"`

            if [[ "`cat $2/tmp.hpp | grep $file`" == "" ]]; then
                generate_pph $file $2
                cat $file | egrep "^#include" | grep -v "boost\/hana" >> $2/includes.hpp
                echo >> $2/pph.hpp
                cat $file | egrep -v "^#include" | cat -s >> $2/pph.hpp
            fi
        done
    }

    tmp_dir=`mktemp -d`

    echo "#ifndef BOOST_HANA_PPH_HPP"
    echo "#define BOOST_HANA_PPH_HPP"
    generate_pph "boost/hana.hpp" "$tmp_dir"
    cat $tmp_dir/includes.hpp | sort -u
    cat $tmp_dir/pph.hpp
    echo "#endif"

    rm -rf $tmp_dir
}

cd "`readlink -f \`dirname $0\``/../include" && main "boost/hana.hpp" > "boost/hana_pph.hpp"

just run pph.sh and it will produce boost/hana_pph.hpp

Awesome, thanks! I tried to tweak it myself and it almost worked, but I had some weird problems. Anyway, the above works almost out-of-the box on OS X, except you must replace mktemp -d by mktemp -d -t something. So now I can generate the header, but I have a question for you. Ideally, I'd like to have a link in my README pointing to Wandbox, with this header included. However, I'd like this header to be generated automatically and the link to be updated in my README whenever I push to master. Are you handling this in DI? Otherwise, I'll try to set up something like that if I want to have this in the long term.

Because I'll inevitably forget to update the link at some point, and I don't want to have to think about it.

Well, I haven't done it yet, but I would like to have exactly the same. Fortunately, Wandbox has a public API - https://github.com/melpon/wandbox/blob/master/kennel2/API.rst, which, I guess, might be used to achieve that, but yea, for now, I just copied the header to check it out. Will keep you informed tho.

Same here, I'll let you know if I do it. Thanks a lot!

Actually, it seems to be very easy, basically works out of the box :)
test.json
{
  "codes": [
	  { "file": "di.hpp", "code": "#include <iostream>\nint main() { int x = 0; std::cout << \"hoge\" << std::endl; }" }
  ],
  "code" : "",
  "options": "warning,gnu++1y",
  "compiler": "gcc-head",
  "compiler-option-raw": "-Dx=hogefuga\n-O3",
  "save": true
}

curl -H "Content-type: application/json" -d "cat test.json"  http://melpon.org/wandbox/api/compile.json 2>&1 | grep url

I was looking at the same thing :-). One problem I have is that the generated header for boost/hana.hpp seems to be to big; it does not work. I can't even share a link to it. (the header spans 33k lines lol)

hmm, you may try to remove some doxygen comments or maybe with multiple "codes" in json. Although, the latter may not work, because wandbox seems not to be able to create directories :/

Yeah, I'm witnessing precisely the same thing. Unfortunately, removing comments only trims the header by a couple of KLOCs, but I fear that's not enough.


feat(services): Implement huaweicloud obs signer

Hi! I have implemented the Huawei Cloud Signer, and test it locally, PTAL.
I'm not sure how to write integration tests for the new signer, and where to store ak / sk for test.

writing integration tests now.

@eastfisher unit test failure should be addressed.


Post release automated changes for communication releases

Post release automated changes for azure-rest-communication-job-router

API change check
API changes are not detected in this pull request.


[KOGITO-3874] - Allow configuration of readiness and liveness probes

Many thanks for submitting your Pull Request :heart:!
Jira issue : https://issues.redhat.com/browse/KOGITO-3874
Please make sure that your PR meets the following requirements:

[x] You have read the contributors' guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains a link to the JIRA issue
[x] Pull Request contains a description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[x] Your feature/bug fix has a unit test that verifies it
[x] You've tested the new feature/bug fix in an actual OpenShift cluster

Should we provide a support in CLI too?

/jenkins test

Otherwise works as expected

Should we provide a support in CLI too?

This fine tune can be done by editing the resource after being deployed. It's an edge case. What we could do is to provide some parameters in the CLI, not the entire probe object. Like the 'initial delay seconds', for example.

@sutaakar merging, but would be nice to have a JIRA to follow up your suggestion.

Created https://issues.redhat.com/browse/KOGITO-3898 to track the CLI changes.