How to timeout captureException

Maybe there is another solution to this problem.
We have a django view that in some part of the code has a:
try:
...
except Exception:
    # we want the view to log to sentry but continue since the code inside the `try` block is not essential
    sentry_client.captureException()

We had a bug that caused an exception on every new request. I might be wrong, but it seems like captureException locks until a previous captureException call is done. This causes all requests to delay and end up adding up to absurd response times.
Is there a way to set a timeout the captureException or defer that to a celery task?
We are running raven 6.0.0.
Would really appreciate some guidance on how to solve this problem.
Thanks!

I ran into this problem today, it would be great if we could set a timeout. The same call can hang for hours.


Pinch zoom problem while ink annotation is on

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version: Chrome & Safari
Operating system and its version: Android & IOS
PDF.js version: 4.0.269
Is a browser extension: No

Steps to reproduce the problem:

Click Ink annotation and draw something.
Use finger to pinch zoom in or out, it draw some mess.

What is the expected behavior? zoom in or out without drawing mess.
What went wrong?

Should we just end Ink-drawing when more than one touch-point is present?

Yes I think we should do something like that:

on pointerdown (one touch), save the point and it only if it's follow by pointermove or pointerup
on pointerdown (two touches or one touch followed by a second one) followed by a pinch, trigger a zoom.


inputs problem

fix inputs to change disabled state when user changes them nit when user clicks away

fixed it.


When running TopHat, use TopHat-Recondition to fix the unmapped.bam file.

Currently the "missing 0x8 bit" problem that unmapped.bam files have
is fixed using a home-grown solution.  Instead, use TopHat-Recondition,
which fixes this problem as well as two additional problem classes.
The issues are described in detail here:
Homepage:  https://github.com/cbrueffer/tophat-recondition
Publication   http://bmcbioinformatics.biomedcentral.com/articles/10.1186/s12859-016-1058-x
Since this requires an external program, how to ensure it is installed (it is available through bioconda)? Is cloudbiolinux contrib/flavor/ngs_pipeline_minimal/packages-conda.yaml the right place?

Hi Christian,
Thanks for the pull request, I'm not against calling out to another tool that does the job better. The tool would need to get installed via bioconda, I can help you make a recipe for that if one doesn't exist already. We'll also need to find the tophat-recondition program by looking it up, like             tophat_recondition = config_utils.get_program("tophat-recondition", data), since it might exist in a couple different places.

Hi Rory,
a bioconda recipe already exists. Would contrib/flavor/ngs_pipeline_minimal/packages-conda.yaml  in cloudbiolinux be the right place to add it? I'll test the lookup line you suggested tomorrow and update the pull request. Thanks!

Hi Christian,
Yup, that's the place. Thanks!

Updated per suggestion by @roryk

Thanks Christian, this seems to work ok for me. The Tophat folks are also pointing people to use hisat2 instead of Tophat going forward, do you have much experience comparing the two? We've been delaying a little bit while hisat2 worked out some of its issues but things are looking more stable as of late.

Thanks for the merge! I just started looking at hisat2 (hence the recent index fixes), can't really give an opinion yet; we've used TopHat up until now.


Error: model/params.json not found

Hi,
I'm running the below and getting this error:
singularity run deepconsensus_0.3.1.sif deepconsensus run ... [per the quick start guidelines]
...
tensorflow.python.framework.errors_impl.NotFoundError: model/params.json; No such file or directory

Nevermind. I saw that in the quick start there is a separate step to download the model.


Shouldn't prevent default on forms.

Since action="" is invalid HTML5 markup, and Angular.js prevents the default submit when action attribute is not set, there is no way of using the document address with valid html5 markup when using angular.
Please create a property that must be set on the forms to enable this preventDefault behavior.

I'm not sure what you are trying to do actually. Can you elaborate?

I'm trying to submit the form to the document address. Angular adds a preventDefault and the form is not submited, which makes it impossible to use the valid markup.
valid markup
<form>
</form>

invalid markup
<form action="">
</form>

Ah okay I see. Well, that's inconvenient. Does it work, for purpose of validation and submission, if you put in a # into the action property?

There is an easy work-around if anyone is interested:
Since the condition for preventing the default form action is $attrs not having an action property, you can manually put an action property on the Attributes object without adding an action attribute on the element.
E.g. to have this work-around automatically applied on all forms with a method attribute:
.directive('method', function () {
  return {
    priority: 1,   // To run before the default `form` directive
    restrict: 'A',
    compile: function (_, tAttrs) { tAttrs.action = undefined; }
  };
})

Demo

Of course, @Narretz's suggestion of having action="#" (or even action="?") does work, but messes with your URL, so might not be appropriate for some usecases.

if you put in a # into the action property?

Actually the HTML5 specification says that:

The action and formaction content attributes, if specified, must have a value that is a valid non-empty URL potentially surrounded by spaces.

action="#" and action="?" and  action="" are all invalid markup
You must either set a valid url, or do not use the attribute at all.

So basically the problem is that a HTML validator will say that the document is invalid, yes?
I rather not make "no prevent default" the default behavior, because most people don't use html form submission with angular, but ajax requests. Suggestion: allow default form submission behavior even if no action attribute is set.

Default form submission should definitely not be the default.
How about not preventing the default only if there is a method attribute.
The truth is though, that I would prefer having an explicit flag attribute foralliwing the default behaviour.

I don't think angular should mess with how forms are submitted by default at all. The best approach is to create a new attribute like "data-ng-form" and people that want the forms to be handled by angular set it.
The problem isn't the validation itself, but that may be other frameworks being used (which is exactly what is happening to me) that are HTML5 compliant, and then you're creating an incompatibility between those frameworks by not following the standard.
Good code, usually do nothing that changes the default behavior unless explicit configured to do so.

Good code, usually do nothing that changes the default behavior unless explicit configured to do so.

But AngularJS was designed for SPAs where not submitting forms is a default behaviour.... So I guess it really comes down to what one means by "default" and what are the expectations.
While I understand that people might want to have this "default" to be configurable, I don't think we should change the current behaviour "default" behaviour.

Being designed for SPA doesn't necessarily mean it needs to force behaviors. These behaviors might still be optional and being optional is always an advantage. By adding a form attribute ppl will still be able to achieve the same behavior, but with the advantage of not affecting ppl that doesn't want that behavior.

Being designed for SPA doesn't necessarily mean it needs to force behaviors.

I think we all agree on that; that's why we are trying to figure out the best way to allow the developer to choose their preferred behaviour.

These behaviors might still be optional and being optional is always an advantage. By adding a form attribute ppl will still be able to achieve the same behavior, but with the advantage of not affecting ppl that doesn't want that behavior.

This also applies to the other (non-spa default) behaviours.
--
The question is what should be an Angular default and what should be an opt-in alternative.
Considering that:

The great majority of people building SPAs, does not want the default submit

Angular is not a general purpose JS lib, it is a SPA framework, so just including it in the page you are making an explicit choice. It should support the most common behaviour out of the box and be configurable for edgecases (not the other way around)

It would be a major breaking change, affecting almost every app and possibly third-party dependencies

I believe that the default form behaviour remains unchanged and we add a way to opt-out (e.g. either by explicitly adding a special attribute or by automatically detecting a method attribute (indicating the users intention to use the default submit behaviour)).

+1 @gkalpak

Hi, I see this conversation being fruitless, just stating that this is not valid html markup is really not a good reason. All browsers fail to follow the standard in one way or another and this does not prevent people from using and libraries like Angular to have to workaround their limitations.
If you want the form directive not to prevent the default behavior and keep the markup valid, then just do <form x-action=""></form> there is no need to argue that X is more or less /pure/.
I think the current behavior is the right one and that this issue should be closed as wont fix.
BTW

action="#" and action="?" and action="" are all invalid markup

action="?" is a valid markup
http://www.w3.org/TR/html5/forms.html#attributes-for-form-submission reads
The action and formaction content attributes, if specified, must have a value that is a valid non-empty URL potentially surrounded by spaces.
A string is a valid non-empty URL potentially surrounded by spaces if, after stripping leading and trailing whitespace from it, it is a valid non-empty URL.
A string is a valid non-empty URL if it is a valid URL but it is not the empty string.
A URL is a valid URL if it conforms to the authoring conformance requirements in the URL standard. [URL]
The W3C URL specification defines the term URL, various algorithms for dealing with URLs, and an API for constructing, parsing, and resolving URLs. Developers of Web browsers are advised to keep abreast of the latest URL developments by tracking the progress of https://url.spec.whatwg.org/
Then https://url.spec.whatwg.org/ reads
4.1. URL writing
[...]
A relative URL must be either a scheme-relative URL, an absolute-path-relative URL, or a path-relative URL that does not start with a scheme and ":", optionally followed by a "?" and a query.
A path-relative URL must be zero or more path segments separated from each other by a "/".
This is, the string "?" is not the empty string, it has zero path segments and is followed by a "?"

Despite the ? and # being valid URLs, the point here is that angular is using action=""  as opt-out, which is invalid markup and this is clear.
Also it makes much more sense to enable some behavior than disable it. If you can have angular features working in non-SPA, why not avoid creating behaviors that change the default html one?
Couldn't you guys consider this change for the next major and create a new opt-out attribute in this release?
Imagine i have a full application with thousands of forms and they're all using document address as form action (with no action attribute). Then i want to migrate some parts of my application to angular and this part has for example 1 form. Then now i have to add a unnecessary attribute or action to every single form in my application just to avoid some default behavior of angular. These other forms have nothing to do with angular.
Now i'll have to add this action or attribute to every single form i have, just to make sure their default behavior will not be prevented by angular.

Imagine i have a full application with thousands of forms and they're all using document address as form action (with no action attribute). Then i want to migrate some parts of my application to angular and this part has for example 1 form.

There are ways for limiting Angular to specific parts of your page. Angular will not parse the whole page, just the parts you specify as part of the Angular app.

Then now i have to add a unnecessary attribute or action to every single form in my application just to avoid some default behavior of angular.

Speaking for myself, of course, but I would rather have you add an "unnecessary" attribute to every single form, than have you (once fully migrated) and every other regular Angular user add an "unnecessary" attribute to every single form to get the reasonable (for SPAs) behaviour.
--
Anyway, as @lgalfaso pointed out, this discussion isn't going anywhere.
And with the x-action/data-action alternatives in place, I too vote for closing as won't fix.

And with the x-action/data-action alternatives in place,

data-action is valid, but i wasn't able to validate x-action. Also, this is used to create attributes that are not part of the HTML5 standard. In this case, we're discussing the erroneous change of some attribute behavior that is part of HTML5.

but I would rather have you add an "unnecessary" attribute to every single form, than have you (once fully migrated) and every other regular Angular user add an "unnecessary"

In this case since i'm using the default HTML5 behavior, i shouldn't need to add anything. But since you're modifying the form behavior, then you have to enable a feature. Comparing my app to the SPA world is like comparing the SPA world to non-SPA world. Its almost the same to say that the default HTML5 document address behavior when no action attribute is set should be removed because there are some SPA applications that do not use it.
Couldn't you guys consider this change for the next major and create a new opt-out attribute in this release (2.0)?
You're viewing this change as a bc break, but forgetting that it would be a nice improvement, allowing non SPA applications to use angular (without dividing parts of the application or resetting default behaviors).

Hi, I am sorry that the current behavior will make you work on migrating your application to Angular, but the current behavior is considered the right one. Closing this issue


Sidebar appear from the side when zoom level changed on the browser

When i zoom out with browser ,sidebar appears from the corner,is this problem fixed with the v2 ?

do you have any custom css rules? Or did you set the width of the sidebar manually? Also note that v2 is a different mechanism than v1 as it's a collapsible sidebar.

I set the width manually,its fixed when i used original.Thanks


Check casper theme in directly

For this to work on Heroku, casper (or whatever theme you're using) needs to get checked in directly to the themes folder.
https://github.com/fission-suite/heroku-ipfs-ghost/tree/master/content/themes
Delete the casper symlink, and check in the theme directly into this folder.

I didn't encounter any problems leaving the symlink as it was.  I'm not sure if it was a version 2.x problem, but for the time being, I can't replicate the problem.
I did encounter something very similar with the storage adapter though.  It seems to pass the Build stage but fails during Deploy.
The specific error looks like this:
app[web.1]: /app/content/adapters/storage/ghost-storage-adapter-ipfs:1
app[web.1]: ../../../node_modules/ghost-storage-adapter-ipfs/
app[web.1]: ^
app[web.1]:
app[web.1]: SyntaxError: Unexpected token '.'
app[web.1]: at Module._compile (internal/modules/cjs/loader.js:895:18)
# stack trace...

If this problem re-emerges, we can re-open the issue and hopefully address it with a similar approach.


Datepicker on forms with nested resources

When adding a record through AA's form, if that the resource of that record has associated children, the datepicker attribute for those associations do not work (only on the add form, edit works fine). From what it looks like, the datepicker event in the js file is called at the beginning but not when an association is added through the AJAX buttons.
Ideas on the best solution for this? My thinking is having the datepicker event called when the AJAX "Add new [child]' button is clicked.

I have the same issue.


updates to stashcp and ES index

Plus Derek's changes from Friday's pull request

Why is there another pull request?  Why is this not in #6 ?


Teach cadence server to bind on any IP specified in configuration

In some environments (to satisfy difference between local laptop environment and CI) we need to make sure cadence binds on all interfaces

Our internal integration framework creates isolated docker network and during local development it is exporting ports back to host system - here we need to make sure cadence server binds on external IP of docker container (docker is not exporting binds on localhost of container), when we run same test inside CI environment - we're not exporting anything to host machine and run test in that isolated network and here we need cadence to bind on <IP_ADDRESS>. Binding on all interfaces will satisfy both environments and it is defaul behavior of yarpc apps (afaik).

@artms -  Just a ping - Where are you with this PR ? Do you still need the changes in this PR ?

@artms - Just a ping - Where are you with this PR ? Do you still need the changes in this PR ?
Sorry, last week was very busy didn't have time to sit and do it, I'm keeping this change in mind :)

@venkat1109 - change is ready

@venkat1109 - gentle nudge.

Closing this PR in favor of https://github.com/uber/cadence/pull/1471


Android sets release channel to default if releaseChannel has a dot in the value.

Build/Submit details page URL
No response
Summary
When the release channel has a dot in the name Android builds do not use it and instead set the channel to default.
Managed or bare?
eas build
Environment
npmPackages:
expo: ^44.0.0 => 44.0.5
expo-dev-client: ~0.8.2 => 0.8.2
expo-updates: ~0.11.5 => 0.11.5
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-web: 0.17.1 => 0.17.1
Project workflow: managed
Error output
No response
Reproducible demo or steps to reproduce from a blank project
This is when building via eas build and pushing OTA updates via expo publish.
To test is pretty easy.
Create a build with the release channel set to 1.0.
It will not take OTAs published to release channel 1.0. But, push an OTA to default and it will be picked up.
Create a build with release channel set to 1_0.
It will take OTAs published to release channel 1_0.
The behavior was not this way when we were using expo-cli for builds and, I think things were working for a while in eas-cli. But now there is definitely an issue.
note: iOS builds work as expected.

@GollyJer - to be totally clear, you are using expo publish ("Classic updates") and not EAS Update, right?

@brentvatne Yes. That is correct.
But, to be more direct. expo publish is not the problem.
eas build choking on the dot in the releaseChannel name is the issue.

PS - The way I discovered the issue was to pull in this and display it on a screen in the builds.
import { releaseChannel } from 'expo-updates';

Thanks for reporting this @GollyJer! I'll take a look!

@GollyJer it should work now

💪


[tiff] Build error

Host Environment

OS: [e.g. Windows/Linux etc...]
Compiler: revision

To Reproduce
Steps to reproduce the behavior:
./vcpkg install xxxx
Failure logs
-Cut and paste the appropriate build messages from the console output.
-Please attach any additional failure logs mentioned in the console output.
Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.

@amirabahram Thanks for posting this issue. Could you please describe the process of your failure and provide a detailed error log?

@amirabahram Is still work for this issue?

We don't have enough information to solve this issue, unfortunately; if you have any more information to help us solve this, please reopen!


⚠ Processors has degraded performance

In 6d2cb34, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 46 ms

Resolved: Processors performance has improved in c00bf51.


Jittery images after 3-4 generations

Hi team,
We are trying to generate pest-infused plant images. While the 1st and 2nd generations work well. After the third one, we start to get noisy and jittery images.

The actual background looked something similar to this, to the same, but similar.

Is there a solution/ insight that you can provide for the aforementioned problem?

Based on the information from your post, it's hard to identify your issue. I suggest checking the background image and bounding box mask that you inputted.

Each image grid here represents the background foreground and mask and then 2 generations in sequence. We utilised the generated image as the background image for the next generation that we have in queue. The following generation represents the 0th, 6th and 8th iteration of blending different pests onto the modified background. While the generation quality is not something I am concerned about, what I don't understand is the jittery nature of the generated image. This starts to happen generally after the 3rd image that we blend iteratively.

I see. Since the background reconstruction of the diffusion model tends to have errors and can degrade details from the original real images, repeatedly using generated images as backgrounds may indeed result in a deterioration of image quality. If you're interested in achieving multi-subject composition, I suggest referring to related work at: https://github.com/ali-vilab/AnyDoor.

I see. Since the background reconstruction of the diffusion model tends to have errors and can degrade details from the original real images, repeatedly using generated images as backgrounds may indeed result in a deterioration of image quality. If you're interested in achieving multi-subject composition, I suggest referring to related work at: https://github.com/ali-vilab/AnyDoor.

Another alternative method is to replace the background region of each generated image with a real background, and then feed into the model again.

Thank you for taking the time to provide your suggestions. I appreciate your insights and will definitely check them out. If you have any further suggestions, please let me know. Just to provide some context, we are currently working on training object detection models using large-scale synthetic image datasets. Our focus is on plant backgrounds and pest-based foregrounds.


Can't remove record in tree-like grid

Hello!
I tried to remove children record: w2ui.grid.remove('21'). Row hides, but when I collapse and expand parent row, my removed row return again.
try here
http://w2ui.com/web/demos/#!grid/grid-7
Expand second row ("Motzart"), type in console:

w2ui.grid.remove("21");

collapse and expand second row ("Motzart"). Deleted row will be here again.

w2ui.grid.delete() also has no effect - entry is restored after collapse/expand parent.

we have the same problem..try to reload table it will remove the child row..but i think its seems like a bug


Fixed secrets when release calling test

#3  👈
main

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

Join @CatChen and the rest of your teammates on  Graphite


Cannot post news in em-be-threefold-token

app_ids is empty
service =<EMAIL_ADDRESS>supported apps = em-be-threefold-token
[XX-OFFLOADv1]{"function":"/common/news","status":true,"request_data":{"broadcast_on_facebook":false,"title":"*****","image":"*****","tag":"news","order_items":[],"broadcast_on_twitter":false,"broadcast_type":"News","role_ids":[...],"app_ids":[],"message":"*****","type":1},"timestamp":1528449714.7334099,"response_data":"****","type":"web","user":"5c31adac01cad92a435c44f514798d88"}

The problem is that cities map is enabled, and the app name is not a city itself. So when getting selected apps/cities from the map, it gives an empty list.
Now this service has two apps that don't have the name of a city, should we just select them by default or add another method to select non-city apps?

According to the changes in #955, local news (current active apps of the service) will be mandatory and cannot be unset.
So, we should select all available for a service by default.

I don't know yet which logic we would add best in this case.
Services in apps like be-fairphone, be-foxtown, em-be-threefold-token, em-be-threefold-staging, ... shouldn't be able to post in regional news. They're actually enterprise apps, but the app's type is set to CITY_APP so we can (ab)use the shop for this.
Quick workaround could be to change the country of the threefold service to Dubai. But that won't solve the underlying issue.

But for actual city apps, we should select all the app of the service by default (as local news), and allow to select other city apps? and in this case, a merchant for example cannot deselect his own city (default app).

Sort off fixed now with the checkboxes, but we'll have to change it so it doesn't show the checkboxes at all when the app's type != city app.


isRegExp: instanceof + check for properties

In a project I am involved in, an Express application is under quite high load. What we discovered, is the app sporadically does not return CORS headers.
If it was misconfigured, I guess, that misbehaviour would be ever present. We use list of RegExps for allowed origins. The only suspicious thing I can potentially blame is instanceof RegExp check. This PR changes it to a slightly more complicated property-based check.
Background for why instanceof RegExp could be flaky:

https://github.com/micromatch/anymatch/issues/48
https://github.com/jonschlinkert/kind-of/blob/master/index.js#L88

Ah, thanks. After I posted that, a thought crossed my mind: this bug should be reported to Node.js or V8 as many things test for RegExp and if it randomly will fail, this would create unknown code paths thoughout your app. There are many implications if this is the case and really needs to get reported to the platform and resolved there.  Trying to patch every module on npm is going to be a never-ending task. If at leaat the Node.js doc are updated to state do not use this check, we can follow their guidelines.
I mean, did you deply this change at all to your production and at least verify that it resolves your problem? We'd want to at the very least do that. But ultimately without a test for this code path, the change ia unlikely to be accepted as there is no way to prevent regression of behavior that someone may now be reliant on.

Okay, I see your point. I have prepared a local modified version of the package. When we hit the high enough load again, and experience the bug, we'll deploy the change. If it actually resolves the issue, IMO, it might be a good enough signal to convince you, that the patch here is important, even if as you noticed, it is an underlying issue lurking beneath the surface. For now, please, let the PR hang for a couple of weeks.

No problem, I would definitely ask that you at least also file an issue with the platform so they are aware to look into the issue. If not, please add code to your reploy that logs what the regular expression is that fails the instanceof check.

This is an excellent change. Not sure why the library owner's wouldn't just approve.

It was the first comment: need tests added that fail without this change otherwise it is just regress. No tests have surfaced in all this time, I think the PR may be abandoned. I'm going to close this, but anyone, including OP can always open a new one with tests included.
I have tried and tried but never have been able to reproduce the reported issue and the OP didn't provide any instructions, either. It could very well have been a bug in the platform that isn't even a bug any longer.

Sorry I added a comment from the code view without looking at the comments here. @dougwilson  the repro for me is very simple, and honestly not sure if this PR actually fixes it or not, which is why I asked for test.
 // This does not work
 const corsOptions: CorsOptions = {
    origin: [/vercel\.app$/],
  }

 // This works
 const corsOptions: CorsOptions = {
    origin: [new RegExp('vercel.app$')],
  }

Something in the recursive call is switching the type of the regex.


When the window is reduced, the scroll doesn't appear to move the page left-to-right.

The VM creation window is not fully displayed

TBD in #43


bug: Venv-selector extra does not work without Telescope.nvim

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.10.0
Operating system/version
Windows 10
Describe the bug
This is ultimately an upstream issue (I am going to try and make a PR for them tonight if I can) because linuxcultist/venv-selector has telescope hard coded as a picker. Therefore, it doesn't seem like it can be easily extended to fzf-lua at the moment like how you have been gobbling up all the other needed picker refactors over the last 24-48 hours.  In the mean time, we could throw telescope as a dependency for anyone that has that extra installed otherwise it will bomb and error out.
Steps To Reproduce

Install Python Extra
Open Python project or dir that has a virtual env in it.
Try to activate the venv with cv and behold error.

Expected Behavior
A picker should pop up that lets you select the desired venv.
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  "folke/LazyVim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

I'd rather have a proper solution in place instead of just adding telescope.
venv-selector should ideally implement a fallback using vim.ui.select.
In case fzf-lua is installed, that would then be used as the ui.

I'd rather have a proper solution in place instead of just adding telescope.
venv-selector should ideally implement a fallback using vim.ui.select.
In case fzf-lua is installed, that would then be used as the ui.

No problem! I thought you might feel that way and I do appreciate the input for how to do it. I look forward to trying to doing something that can contribute to both projects.

Closing, since venv-selector will now only be installed if telescope is available


Render fail

I get on the xml file the following errors:

Failed to instantiate one or more classes:
The following classes could not be instantiated:
- com.joanzapata.iconify.widget.IconTextView (Open Class, Show Exception, Clear Cache)
Tip: Use View.isInEditMode() in your custom views to skip code or show sample data when shown in the IDE.

Render problem: Failed to find the style corresponding to the id -1
Render problem: Asset not found: iconify/android-iconify-material.ttf

they are all related to com.joanzapata.iconify which is no more supported I guess
waiting for your response and thank you for the great work

Hi, thanks for the issue. Also @FareehaRqzaq in the issue #14 had the same behavior. Can you please tell me what base app theme do you use in the styles.xml?

I have a same problem and use


silent notification (no title, no message, no icon, no sound, etc.)

Expected Behaviour
completely silent notification while delivering a payload in background: no sound, no notification shown on phone's homescreen, etc.
Actual Behaviour
whatever i tried to build a background notification as per the docs I still have a notification displayed on the phone's homescreen, with a title which is the name of my app, which i did not configured anywhere
Reproduce Scenario (including but not limited to)
send the simple notification i've noted down below
Steps to Reproduce
use of ionic push service to send the notification
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
tested on Android 4.4 and Android 6
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
Samsung GS6 & HTC One
Cordova CLI version and cordova platform version
cordova --version                                    6.1.1
cordova platform version android            android 5.1.1

Plugin version
cordova plugin version | grep phonegap-plugin-push   1.6.3

Sample Push Data Payload
I've adapted a little bit the actual payload since i'm using the ionic push service, but it comes down to this when stripped all the ionic semantic
            "data": {
                "info": "super secret info",
                "content-available": "1"
            }

Sample Code that illustrates the problem
my push init & register code  (i'm using the plugin through the ionic $angular wrapper)
        push = $ionicPush.init({
            'debug': true,
            'onNotification': onNotification,
            'onRegister': onRegister,
            'pluginConfig': {
                'ios': {
                    'badge': true,
                    'sound': true
                },
                'android': {
                    'senderID': 'xxxxx',
                    'sound': true
                }
            }
        });

            $ionicPush.register();

Logs taken while reproducing problem

@ebarault yes, it is possible but you aren't giving me much to go on here. Please follow the issue reporting guidelines. I need to know what platform you are testing on what your push payload is etc. Please re-open when you provide those details.

I have updated the issue as per the provided guidelines, may you reopen it?

I've updated the issue, i can't reopen it myself i guess
2016-05-14 2:44 GMT+02:00 Simon MacDonald<EMAIL_ADDRESS>
@ebarault https://github.com/ebarault yes, it is possible but you
aren't giving me much to go on here. Please follow the issue reporting
guidelines. I need to know what platform you are testing on what your push
payload is etc. Please re-open when you provide those details.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/phonegap/phonegap-plugin-push/issues/886#issuecomment-219189973

@ebarault can you not strip out the Ionic semantics? I have a feeling their service adds in some defaults that keep this from being a silent push. If you reproduce the issue when running adb logcat | grep PushPlugin it would help diagnose.

so I read between the lines that the notification i send should result in a trully silent (and background) notification.
In that case i do believe too that the ionic rewriting is faulty in several cases. I opened 2 issues for ionic push here and there.
the first one exactly describes the issue we're discussing here.
the incriminated payload is the following, which is the only correct set-up i found to make a notification that the app receives in background without requiring to action it.
curl -X POST -H "Authorization: Bearer XXXXX" -H "Content-Type: application/json" -d '{
    "tokens": ["myToken"],
    "profile": "ZZZZZ",
    "notification": {
        "android": {
            "payload": {
                "info": "super secret info"
            },
            "data": {
                "title": "",
                "message": "",
                "content-available": "1"
            }
        },
        "ios": {
            "content_available": 1
        }
    }
}' "https://api.ionic.io/push/notifications"

I will post later the adb log, but i can already confirm that there should be some faulty rewriting somewhere at ionic side since a non-empty notification title is added on the fly, and received by the app, and thus shown to the user.
You should definitely give a go to my write-up on ionic push github about the handling of the native notification payloads, your comments would be much appreciated there to sort things out.
I

ok, @macdonst, here is the debug info from adb, so yes: we can see a 'myApp' title being inserted, coming from ionic most probably
D/PushPlugin_GCMIntentService(20101): onMessage - from: 44xxxxxxxx956
D/PushPlugin_GCMIntentService(20101): normalize extras
D/PushPlugin_GCMIntentService(20101): key = payload
D/PushPlugin_GCMIntentService(20101): replace key payload with payload
D/PushPlugin_GCMIntentService(20101): key = data
D/PushPlugin_GCMIntentService(20101): extracting nested message data from key = data
D/PushPlugin_GCMIntentService(20101): key = data/message
D/PushPlugin_GCMIntentService(20101): key = data/content-available
D/PushPlugin_GCMIntentService(20101): key = data/title
D/PushPlugin_GCMIntentService(20101): replace key data with data
D/PushPlugin_GCMIntentService(20101): key = title
D/PushPlugin_GCMIntentService(20101): replace key title with title
D/PushPlugin_GCMIntentService(20101): key = collapse_key
D/PushPlugin_GCMIntentService(20101): replace key collapse_key with collapse_key
D/PushPlugin_GCMIntentService(20101): background
D/PushPlugin_GCMIntentService(20101): message =[]
D/PushPlugin_GCMIntentService(20101): title =[myApp]
D/PushPlugin_GCMIntentService(20101): contentAvailable =[1]
D/PushPlugin_GCMIntentService(20101): create notification
E/PushPlugin_GCMIntentService(20101): Number format exception - Error parsing notId: Invalid int: "null"
D/PushPlugin_GCMIntentService(20101): stored icon=ic_notification
D/PushPlugin_GCMIntentService(20101): stored iconColor=#e52a4b
D/PushPlugin_GCMIntentService(20101): stored sound=true
D/PushPlugin_GCMIntentService(20101): stored vibrate=true
D/PushPlugin_GCMIntentService(20101): using icon from plugin options
D/PushPlugin_GCMIntentService(20101): create actions
D/PushPlugin_GCMIntentService(20101): send notification event
D/PushPlugin(20101): convert extras to json
D/PushPlugin(20101): key = content-available
D/PushPlugin(20101): key = payload
D/PushPlugin(20101): key = data
D/PushPlugin(20101): key = title
D/PushPlugin(20101): key = message
D/PushPlugin(20101): key = collapse_key
D/PushPlugin(20101): key = foreground
V/PushPlugin(20101): extrasToJSON: {"message":"","additionalData":{"data":{"message":"","content-available":"1","title":""},"payload":{"info":"super secret info"},"collapse_key":"do_not_collapse","content-available":"1","foreground":false},"title":"myApp"}

@ebarault yeah, this is an issue with Ionic Push for sure. I will comment on the issue that you opened and I will be seeing some of the Ionic guys this week so I'll talk to them about it. Going to close this issue for now unless there is something for me to do on my end.

thanks Simon, appreciate that.
2016-05-16 16:24 GMT+02:00 Simon MacDonald<EMAIL_ADDRESS>
@ebarault https://github.com/ebarault yeah, this is an issue with Ionic
Push for sure. I will comment on the issue that you opened and I will be
seeing some of the Ionic guys this week so I'll talk to them about it.
Going to close this issue for now unless there is something for me to do on
my end.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/phonegap/phonegap-plugin-push/issues/886#issuecomment-219437862

Any news on this?


wrong EDE code returned when system time is significantly wrong

Describe the bug
When I have wrong date on the system and ask for name on validating resolver, it does not provide detailed EDE code describing the problem accurately. It says DNSSEC Bogus, where there are explicitly defined codes for wrong timestamps in validation process. One for not yet valid, one for expired. I would expect to see them.
To reproduce
Steps to reproduce the behavior:

Set system date 14 days back (VM suggested)
start unbound with dnssec validation enabled
dig @localhost 2.fedora.pool.ntp.org gives ; EDE: 6 (DNSSEC Bogus), but I would expect EDE code 8 | Signature Not Yet Valid.
dig @localhost +cd 2.fedora.pool.ntp.org returns correct answer, so this is just validation problem

Expected behavior
I think EDE would tell me whether there were problem with keys and signatures or just wrong date used during validation. If the problem is only in date, please report it so. Might be used by time synchronization service to do extra workarounds.
System:

Unbound version: unbound-1.17.1-2.fc38.x86_64
OS: Fedora 38 beta
unbound -V output:

Version 1.17.1

Configure line: --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --runstatedir=/run --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-pythonmodule --with-pyunbound PYTHON=/usr/bin/python3 --enable-dnstap --with-libnghttp2 --with-libevent --with-pthreads --with-ssl --disable-rpath --disable-static --enable-relro-now --enable-pie --enable-subnet --enable-ipsecmod --with-conf-file=/etc/unbound/unbound.conf --with-pidfile=/run/unbound/unbound.pid --enable-sha2 --disable-gost --enable-ecdsa --with-rootkey-file=/var/lib/unbound/root.key --enable-linux-ip-local-port-range
Linked libs: libevent 2.1.12-stable (it uses epoll), OpenSSL 3.0.8 7 Feb 2023
Linked modules: dns64 python ipsecmod subnetcache respip validator iterator

BSD licensed, see LICENSE in source package for details.
Report bugs to<EMAIL_ADDRESS>or https://github.com/NLnetLabs/unbound/issues

Additional information
Add any other information that you may have gathered about the issue here.

This has to do with when Unbound errors out in the DNSSEC code path.
Logging information may reveal more information.
I see an explicit testcase for EDE: 8 in the testsuite, so the code is used by Unbound.


Choose how missing translations are returned

When using i18n.formatMessage("system.hello") to get a translation, it currently returns translation missing: en, system.hello if the translations does not exist.
My feature request is to be able to just return the key if a translation is missing.
E.x.:
i18n.formatMessage("system.hello") would return system.hello if the translation does not exist.
A possible solution is to add a config parameter that let's you define if you want missing translations to return a key, or the current error message.

i have made a pull request with the changes proposed: https://github.com/adonisjs/i18n/pull/124

Closing in favor of the PR.


Update script to account for 241 schema changes

Supersedes #106
I'm not sure what's up with a few new commands in various extensions...

This PR had to conditionally disable VK_EXT_discard_rectangles and VK_NV_scissor_exclusive for older headers; this is unavoidable to keep volk working with older SDK headers, I filed https://github.com/KhronosGroup/Vulkan-Docs/issues/2060 to clarify the status here.

VK_EXT_discard_rectangles and VK_NV_scissor_exclusive are pre-existing extensions from 2018. As such this may actually break existing users of these extensions. vk.xml doesn't contain information about which entrypoint was added in which extension version, so this probably requires hardcoded ifdefs or just living with the breakage :-/

The PR should now be neutral on compatibility to the best of my understanding: building against headers 240 or earlier just doesn't expose the three new entrypoints. This seems extremely undesirable and unsatisfactory so I'll wait for official Khronos communication on this before merging this.


need to detect current os, during setup to download appropriate GemStone product tree

right now, we're assuming ubunutu ...

nodejs  (apparently) cannot handle unpacking .dmg file, so have to rely on the calling job to do the download of mac product tree ... setup-superDoit outputs the information needed to run a shell-based download script .. we'll call this v2, since the superDoit project itself had breaking changes which will end up on masterV2.0 branch


[Backport 2.5] Suppress unwanted error notification (#456)

Description
[Backport 2.5] Suppress unwanted error notification (#456)
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #480 (c67d911) into 2.5 (6c37601) will increase coverage by 0.02%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##              2.5     #480      +/-   ##
==========================================
+ Coverage   15.53%   15.55%   +0.02%
==========================================
  Files         111      111
  Lines        2962     2963       +1
  Branches      458      459       +1
==========================================
+ Hits          460      461       +1
  Misses       2463     2463
  Partials       39       39

see 1 file with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Filter corpus on annotations

We still need to plug the logic into methods that operate on files, then hook it up to the cli and we should be good!


window is not defined error

Hi there; recently picked this up as I wanted to play about with some audio generation - so.
I assume from the error I am getting, this is made to run in the browser? As running it via node gives me the above error. Is there anything I can do for this?
Thank you in advance.

I also encountered this error
.../node_modules/tone/build/Tone.js:633
	            var hasAudioContext = window.hasOwnProperty('AudioContext') || window.hasOwnProperty('webkitAudioContext');
	                                  ^

ReferenceError: window is not defined

hope to get your help.  thanks

@Tylertron1998 .
had try version 0.11.2. it's running well

Crudely fixed in 1.0.0-alpha.2


Xvfb failed to start within 10 seconds
Xvfb failed to start
entry file
#!/bin/bash
set -e

# Check if Xvfb is already running and kill it
if pgrep -x "Xvfb" > /dev/null; then
    echo "Stopping existing Xvfb instance..."
    pkill -f "Xvfb"
    sleep 2  # Wait a moment for it to terminate
fi

# Start Xvfb on display :99
echo "Starting Xvfb..."
Xvfb :99 -screen 0 1024x768x16 -ac > /tmp/xvfb.log 2>&1 &
sleep 5  # Wait for Xvfb to start

# Check if Xvfb started successfully
if ! pgrep -x "Xvfb" > /dev/null; then
    echo "Xvfb failed to start."
    echo "Xvfb Log Output:"
    cat /tmp/xvfb.log  # Print the log for debugging
    exit 1
fi

# Set the DISPLAY environment variable
export DISPLAY=:99

# Start other services
./start_all.sh
./novnc_startup.sh

# Start the HTTP server
python http_server.py > /tmp/server_logs.txt 2>&1 &

# Start Streamlit
STREAMLIT_SERVER_PORT=8501 python -m streamlit run computer_use_demo/streamlit.py > /tmp/streamlit_stdout.log &

# Display messages
echo "✨ Computer Use Demo is ready!"
echo "➡  Open http://localhost:9090 in your browser to begin"

# Keep the container running
tail -f /dev/null

Plz fixit i want this on ubuntu arm 64 bit wayland support ok port 9090 not fkin 8080 i use that for other things like most ppl !!

what type of noob are you, that you cant even change a number in the docker command.

fix your trash system. for everyone its working like a charm. and stop beeing so poor to trying to use it on kiddy sistems like raspberry. buy decent hardware you noob.

Hopefully Anthropic will soon evolve their agentware to automatically remove spam-issues from lazy/stupid/disrespectful users. Anything greedy/needy/ALL-CAPS. These users should be blacklisted.


About Innovation Points

Thank you very much for your excellent article. I would like to ask which lines of code are the innovative points of the model in segmentation. Looking forward to your reply!

The main contribution of this paper is LoDA (Locality-Driven Alignment) that enables a vanilla CLIP to produce interpretable text-to-image similarity maps.
Then we implement the SimSeg framework to transform the similarity maps into segmentation maps.


"Poor compliance" graph extends farther than "strict compliance" or "available hospital beds"

summary: The graphs don't line up on the right side.  See screenshot.
environment (device, browser, mobile / web): chrome desktop (macOS)
link: https://staging.covidactnow.org/state/WA/county/king_county
screenshot (you can copy/paste images directly in):

It now seems to have inverted itself!

Obsolete.


cmake build system: test data files, use CONFIGURE_DEPENDS to glob?

Normal globs are executed once at configure time.
So if you add a new data file, it will not be picked up by our cmake build system unless you explicitly reconfigure.
Newer cmake (3.12+) provides CONFIGURE_DEPENDS to address this.

@cyrush you mean this particular glob in tools/data/datagen/CMakeLists.txt...
https://github.com/visit-dav/visit/blob/9ab516d533f4f84a007eed7c97732104a721caf0/src/tools/data/datagen/CMakeLists.txt#L153

Yes, it might be a band aid, but maybe it could help?
The alternative is to add all of the files in an explicit list, then cmake will know about them always.
I actually prefer this b/c I know cmake glob causes disconnect, but CONFIGURE_DEPENDS might be a low effort thing to try before moving to an explicit list.

@cyrush I am trying to put in #17473
To test it, I used this CMakeLists.txt logic...
FILE(GLOB ARCHIVED_TARGETS RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} CONFIGURE_DEPENDS *test_data*.tar.xz)

ADD_CUSTOM_COMMAND(
    OUTPUT _list_archives
    COMMAND ${CMAKE_COMMAND} -E echo ${ARCHIVED_TARGETS}
    WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR})
ADD_CUSTOM_TARGET(list_archives DEPENDS _list_archives)

The new list_archives target allows me to see what make thinks the list of archives is. Based on my understanding of CONFIGURE_DEPENDS I would expect that if I add a new .tar.xz file there, the command make list_archives would show it without having to re-cmake. It doesn't do that however. Am I misunderstanding? Any ideas?

Whoops! I am wrong. That GLOB is for the pattern *test_data*.tar.xz and the test filename I tried was zzzz.tar.xz. Ok, it works!


How to run packaged EXE with hidden command prompt

Hi,
I am bale to package node application and can run exe by opening command prompt and running exe.
I want to run this node app(as an exe) silently in windows i.e. command prompt should not be visible. Any idea how to achieve this?
Thanks,
Pooja

This is not specific to pkg nor nodejs, I think. There are various programs made for that.

Hi,
I am bale to package node application and can run exe by opening command prompt and running exe.
I want to run this node app(as an exe) silently in windows i.e. command prompt should not be visible. Any idea how to achieve this?
Thanks,
Pooja

Hi, @psaxena @dd-pardal I have built executable file for all 3 platforms. Its works fine on Linux and macOS, but it doesn't run on windows. can you please help me with this?
Is there any specific way to run on windows?
NodeJS:- v10.16.2
Pkg :- v4.4.0
Platform :- Linux

Hi,
I am bale to package node application and can run exe by opening command prompt and running exe.
I want to run this node app(as an exe) silently in windows i.e. command prompt should not be visible. Any idea how to achieve this?
Thanks,
Pooja

@psaxena you can write a shell script for this.

Hi, @psaxena @dd-pardal I have built executable file for all 3 platforms. Its works fine on Linux and macOS, but it doesn't run on windows. can you please help me with this?
Is there any specific way to run on windows?
NodeJS:- v10.16.2
Pkg :- v4.4.0
Platform :- Linux

Got this working with powershell script.

Hi, @psaxena @dd-pardal I have built executable file for all 3 platforms. Its works fine on Linux and macOS, but it doesn't run on windows. can you please help me with this?
Is there any specific way to run on windows?
NodeJS:- v10.16.2
Pkg :- v4.4.0
Platform :- Linux

I was able to run by typing exe name on command prompt. You may check if you've any logs for failure

I also found. It was node.js version issue.

I also found. It was node.js version issue.

Can you be more specific? Which versions is do support and which versions doesn't

"pkg": "4.3.7" support with node-10. I was using node10 with Pkg :- v4.4.0 so I was not compatible.


Allow for '_id' for Mongo users

Thanks so much for making this! It's working great for us. However one thing - when using MongoDB the choice.id will be undefined for data being returned from our db.  Right now we're forced to using a computed property in our JS-Data implementation to add an id field.
Would be nice if the this.encode function looked like this:
  this.encode = function (choice) {
    return '@[' + this.label(choice) + ':' + choice.id || choice._id + ']';
  };

Would you accept a PR for this?

No. The point of the library is it's so simple that you should be able to hack on it. Think of the controller like a base class. You should just extend it and override the method with your own implementation. That's why all the methods are publicly exposed.
Unfortunately, I don't have a super streamlined way to do this outside of what's illustrated in the docs.

@ProLoser Makes sense...thanks again for making this!


Add a solution to auto-connect to last used wallet if session exists

Auto-connect is session exists
It is a common pattern and may improve UX to have FCL automatically use a wallet and login a user if a valid wallet connect session exists.

Hi @gregsantos, currently, each time a new browser tab is opened, users must reconnect their wallet.
Is this issue going to address this functionality, or should I open a new one?

Hey @cybercent. Not exactly, as this is WalletConnect specific and would utilize sessions stored via WC client.
I think you are looking for a solution to persist FCL currentUser across browser tabs. That can be done by injecting your own storage strategy via config.
Something like this should work for you:
const isServerSide = () => typeof window === "undefined"
const LOCAL_STORAGE = {
  can: !isServerSide(),
  get: async key => JSON.parse(localStorage.getItem(key)),
  put: async (key, value) => localStorage.setItem(key, JSON.stringify(value)),
}

fcl.config.put("fcl.storage", LOCAL_STORAGE)

@gregsantos thanks for the tip I've been looking the fcl documentation since a while and I've never seen any mention of the "fcl.storage" key...!


[Feature] Integrate with data integration framework

Search before asking

[X] I had searched in the feature and found no similar feature requirement.

Feature Description (功能描述)
The amount of graph data is generally large, so HugeGraph needs to cooperate with the data integration framework to facilitate data import.

Seatunnel
Kafka-connect
Flink-CDC-connector
...

Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

expected wrap data in hg to adapt data integration framework,  or directly implement connector  in flink cdc?


[OSF-4581]

Email notifications for comments/file uploads now contain a link to user settings.

Also, something to keep in mind for future PRs -- It's helpful to have commit messages that describe what was changed in the commit: http://cosdev.readthedocs.org/en/latest/style_guides/git.html?highlight=commit

Pass complete @MerlinZhang! :cookie:

Pass complete @MerlinZhang! :fallen_leaf:

Failing test not related to code changes

Pass finished. There's a lot of noise in the history for this PR. @MerlinZhang to clean up the history and avoid unintended changes to develop, can you please send a new PR containing only your changes?


Update Factory.php

Use https everywhere.

Great PR :)
I'll get this merged over the weekend.

Cool!


Disabled optional weak dependencies end up in Cargo.lock

Problem
Lets say I have two crates, with these contents of Cargo.toml. The Rust code does not matter here.
# foo/Cargo.toml

[dependencies]
serde = {version = "1.0.133", optional = true, default-features = false}
time = {version = "=0.3.10", optional = true, default-features = false}
chrono = {version = "=0.4.18", optional = true, default-features = false}

[features]
serialization = ["dep:serde", "time?/serde-well-known"]

# bar/Cargo.toml

[dependencies]
foo.features = ["serialization"]
foo.path = "../foo"

# time = "=0.3.11"
# chrono = "=0.4.19"

As you can see, bar depends on foo and enables the serialization feature, but it does not enable the time nor the chrono feature.
This results in the following bar/Cargo.lock file:

bar/Cargo.lock
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
version = 3

[[package]]
name = "app"
version = "0.1.0"
dependencies = [
 "foo",
]

[[package]]
name = "foo"
version = "0.1.0"
dependencies = [
 "serde",
 "time",
]

[[package]]
name = "itoa"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "112c678d4050afce233f4f2852bb2eb519230b3cf12f33585275537d7e41578d"

[[package]]
name = "libc"
version = "0.2.126"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "349d5a591cd28b49e1d1037471617a32ddcda5731b99419008085f72d5a53836"

[[package]]
name = "num_threads"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2819ce041d2ee131036f4fc9d6ae7ae125a3a40e97ba64d04fe799ad9dabbb44"
dependencies = [
 "libc",
]

[[package]]
name = "serde"
version = "1.0.137"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "61ea8d54c77f8315140a05f4c7237403bf38b72704d031543aa1d16abbf517d1"

[[package]]
name = "time"
version = "0.3.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "82501a4c1c0330d640a6e176a3d6a204f5ec5237aca029029d21864a902e27b0"
dependencies = [
 "itoa",
 "libc",
 "num_threads",
 "serde",
]

The relevant snippet is at the end:
[[package]]
name = "time"
version = "0.3.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "82501a4c1c0330d640a6e176a3d6a204f5ec5237aca029029d21864a902e27b0"
dependencies = [
 "itoa",
 "libc",
 "num_threads",
 "serde",
]

Here the dependency time is declared, even though it is an optional dependency and nothing enabled the corresponding feature on foo. The time dependency even has serde listed as one of its dependencies too.

I think this is problematic in a couple of ways.
It bloats the Cargo.lock and makes it imply that changes are larger than they actually are. In the above example adding foo will also add time even if that is not necessary.
Dependency management tools will get confused by this. I mean tools like dependabot or cargo audit, which use the Cargo.lock as source of truth. Since these tools will see an entry for time, even if it is unused, they will create pull requests or warn about security vulnerabilities which do not exists.
This prevents using two crates with conflicting version requirements. You can see what happens if you uncomment the lines in bar/Cargo.toml.
Uncommenting time will fail, since now two conflicting version constraints (=0.3.10 != =0.3.11) exist.
However, uncommenting chrono works with the conflicting versions (=0.4.18 != =0.4.19).
Steps

Create project foo with the above content for Cargo.toml.
Create project bar with the above content for Cargo.toml.
Observe how the Cargo.lock of bar contains an entry for time and even a transitive serde dependency in time.

Possible Solution(s)
Disabled optional dependencies should not be tracked in Cargo.lock, even if there is a weak dependency linking to it. This brings it in line with "normal" optional dependencies.
Notes
While the time entry exists in the Cargo.lock, it appears cargo correctly ignores it when building the code. There is neither a Compiling time ... log line nor are there any artifacts in the target folder associated with time.
I checked various issues and documentation entries, but I couldn't find if this is a bug or intended.
The tracking issue (https://github.com/rust-lang/cargo/issues/8832) and documentation (https://doc.rust-lang.org/nightly/cargo/reference/features.html#dependency-features) do not mention any changes in to Cargo.lock. Neither does the implementation PR (https://github.com/rust-lang/cargo/pull/8818), which does not even seem to have any lock files.
Version
cargo 1.62.0 (a748cf5a3 2022-06-08)
release: 1.62.0
commit-hash: a748cf5a3e666bc2dcdf54f37adef8ef22196452
commit-date: 2022-06-08
host: x86_64-unknown-linux-gnu
libgit2: 1.4.2 (sys:0.14.2 vendored)
libcurl: 7.80.0-DEV (sys:0.4.51+curl-7.80.0 vendored ssl:OpenSSL/1.1.1n)
os: OracleLinux 36.0.0 [64-bit]

FYI: My OS is Fedora 36, but this is the output of `cargo version --verbose`.

Note that this bug also affects the output of the metadata subcommand, but not the tree subcommand. Weak dependencies are resolved in the resolve.nodes map even if they haven't been enabled by the crate feature.

I'm not sure but I think I ran into this issue in:

https://github.com/BurntSushi/bstr/issues/130

I found it unexpected that serde appears in the lockfile since I am specifically enabling and disabling features such that I avoid pulling in serde. I was extra confused that serde does not appear in cargo tree.

I've noticed this as well when cargo update caused the lockfile to balloon more than I expected; it was caused by one of the indirect dependencies having introduced a [target.'cfg(target_os = "haiku")'.dependencies] section.

@lopopolo indeed, it's that dependency; however, since I'm not building on an applicable target, I'd expect it to not show up in my lockfile just as much as if it were an optional (and disabled) dependency.

This also happens with sea-orm which pulls chrono and time when you use the with-json flag.
https://github.com/SeaQL/sea-orm/blob/master/Cargo.toml#L75
This is really wrong.

@jonasbb

I checked various issues and documentation entries, but I couldn't find if this is a bug or intended.

I believe this is a known limitation of the resolver/lockfile generation that is intended to be improved eventually. From https://github.com/rust-lang/cargo/issues/5655#issuecomment-408633070,

lockfile generation requires the assumption that all possible features are enabled. Generating a lockfile without optional features is covered by #5133

While #5133 mentions --minimal-cargo-lock, it doesn't appear to be implemented yet. This should also help with offline usage #10352 and platform specific vendoring #7058
From https://github.com/rust-lang/cargo/issues/7058#issuecomment-539845446,

Cargo currently requires that the lock file is platform-independent, meaning that the lock file (and generating the lock file) always has to locate all crates for all possible platforms. [...] There's a tracking issue for this at #5133 which is a possible way to pass a flag to Cargo and say "please generate a minimal lock file", and with that we can safely delete all the dependencies for other platforms.

@memoryruins

I checked various issues and documentation entries, but I couldn't find if this is a bug or intended.

I believe this is a known limitation of the lock file generation that is intended to be improved eventually. From #5655 (comment),

This only applies to the root crate (the one you are working on) but not the dependencies. When you depend on serde without extra features, then the optional serde_derive and any proc-macro dependencies are not included, since the feature is not enabled.

Cargo.toml
[package]
name = "foobar"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
serde = "1.0.147"

Cargo.lock
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
version = 3

[[package]]
name = "foobar"
version = "0.1.0"
dependencies = [
 "serde",
]

[[package]]
name = "serde"
version = "1.0.147"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d193d69bae983fc11a79df82342761dfbf28a99fc8d203dca4c3c1b590948965"

From #7058 (comment),

Cargo currently requires that the lock file is platform-independent, meaning that the lock file (and generating the lock file) always has to locate all crates for all possible platforms. [...] There's a tracking issue for this at #5133 which is a possible way to pass a flag to Cargo and say "please generate a minimal lock file", and with that we can safely delete all the dependencies for other platforms.

This issue is not comparable to platform dependent Cargo.lock. The issue presented here covers dependencies which are never used, on no platform and also not if using --all-features.
In my original posts in the bar/Cargo.lock snippet, you find chrono to be missing, while time is included. Here you see again that optional dependencies are already excluded from Cargo.lock. The only difference between these two is the existence of the weak dependency time?/serde-well-known. So I would put the blame here on the implementation of weak features. But as explained in the original post, I could find no comments on if these Cargo.lock changes are intentional or not.

@jonasbb
I understand what you mean with weak features now. I'll see if I can find anything mentioned in the past.

This issue is not comparable to platform dependent Cargo.lock.

Apologies for any confusion, I forgot to add an @ mention to the platform specific part of my comment, which was meant to be in response to @ljedrz https://github.com/rust-lang/cargo/issues/10801#issuecomment-1277842065

since I'm not building on an applicable target, I'd expect it to not show up in my lockfile just as much as if it were an optional (and disabled) dependency.

The issue with platforms should be be a separate issue, this is really for the issue where a dependency is truly never used but still included. Let's keep it on topic 👍

@Sytten

The issue with platforms should be be a separate issue

Indeed, I linked to those earlier in https://github.com/rust-lang/cargo/issues/10801#issuecomment-1320376112 so that related discussion can move there.

Another side-effect of this problem is that cargo vendor vendors extra unnecessary dependencies.

Users are running into situations where cargo can no longer resolve their dependencies due to this bug. For example, this issue https://github.com/jonasbb/serde_with/issues/550 where a pinned chrono version together with this bug results in error: failed to select a version for chrono..

Not sure if issue is the same but here is my case:
I started a project using actix-web 3.3.3 which has strong dependency to actix-http ^2.2.0. And actix-http 2.2.2 has strong dependency to base64 ^0.13 (resolved to 0.13).
Bump to actix-web 4.3.1, I now have strong dependency to actix-http 3.3.0 which has optional dependecy to base64 ^0.21.
However, as I don't depend explicitly to base64 I would have expected this transitive dependency to be removed. As base64 0.21 require 2021 edition instead of 2018 (use by my project and Actix components). I can't build my project due to:
error: failed to download `base64 v0.21.0`

Caused by:
  unable to get packages from source

Caused by:
  failed to parse manifest at `/home/loganmzz/.cargo/registry/src/github.com-1ecc6299db9ec823/base64-0.21.0/Cargo.toml`

Caused by:
  feature `edition2021` is required

  this Cargo does not support nightly features, but if you
  switch to nightly channel you can add
  `cargo-features = ["edition2021"]` to enable this feature

Any solution to clean the Cargo.lock ?

Filed a PR: #11938

Is there a champion for this fix in the cargo WG? It is a bug that has been lingering for more than a year now and the current proposed resolution is stuck as per https://github.com/rust-lang/cargo/pull/11938#issuecomment-1623769819. It's clear the community has expressed this is a concern and a blocker for adoption of the weak dependencies.

Right now this is causing a bit of an advisory spam, https://rustsec.org/advisories/RUSTSEC-2023-0071.html impacts the rsa crate, which is used by sqlx-mysql, but this is getting detected on every crate that uses sqlx even without mysql because of the weak-dependency-features pulling it into the lockfile.

This is blocking for me as I know no workaround that doesn't involve forking one or more crates that conflict.  Here is an example repo (basically just two dependencies): https://github.com/matthewgapp/rust-lang-issue-10801). The sqlx crate doesn't actually depend on sqlite (note the weak references) but cargo thinks it does.
I'm running into the below error which has no workaround unless fork the sqlx repo and remove the sqlite dependency from the Cargo.toml there.
error: failed to select a version for `libsqlite3-sys`.
    ... required by package `sqlx-sqlite v0.7.3`
    ... which satisfies dependency `sqlx-sqlite = "=0.7.3"` (locked to 0.7.3) of package `sqlx v0.7.3`
    ... which satisfies dependency `sqlx = "^0.7.3"` (locked to 0.7.3) of package `rust-lang-issue-10801 v0.1.0 (/Users/matthewgapp/code/scratchpad/rust-lang-issue-10801)`
versions that meet the requirements `^0.27.0` (locked to 0.27.0) are: 0.27.0

the package `libsqlite3-sys` links to the native library `sqlite3`, but it conflicts with a previous package which links to `sqlite3` as well:
package `libsqlite3-sys v0.26.0 (https://github.com/trevyn/rusqlite?branch=wasm32-unknown-unknown#463090d3)`
    ... which satisfies git dependency `libsqlite3-sys` of package `sqlsync v0.2.0 (https://github.com/matthewgapp/sqlsync#c34cb11f)`
    ... which satisfies git dependency `sqlsync` of package `rust-lang-issue-10801 v0.1.0 (/Users/matthewgapp/code/scratchpad/rust-lang-issue-10801)`
Only one package in the dependency graph may specify the same links value. This helps ensure that only one copy of a native library is linked in the final binary. Try to adjust your dependencies so that only one package uses the links ='libsqlite3-sys' value. For more information, see https://doc.rust-lang.org/cargo/reference/resolver.html#links.

failed to select a version for `libsqlite3-sys` which could resolve this conflict

I just had this problem when trying to vendor code in mozilla-central. One of the crate has massive dependencies which were pulled in for vetting and vendoring while not being used. I had to fork the create to manually remove the unused dependencies but that's not really sustainable.

This issue is causing GitHub to create incorrect Dependabot security alerts. I am using sqlx with the mysql feature disabled, but sqlx-mysql shows up in the lock file, and one of its dependencies is rsa which has a known security vulnerability. While these alerts can be dismissed, one can assume that the Rust ecosystem will appear less secure on the whole than it actually is. This also means that it's impossible to accurately determine the impact of security vulnerabilities on the Rust ecosystem.

Coming from https://github.com/launchbadge/sqlx/issues/2911 from the exact same thing: cargo audit mistakenly reports a vulnerability in the rsa package even though it is not in cargo tree.

Soo... ring isn't in my 'cargo tree', but it is still trying and failing to compile. I think this bug has worsened.

Soo... ring isn't in my 'cargo tree', but it is still trying and failing to compile. I think this bug has worsened.

@lilith  Optional dependencies shouldn't compile if not activated. It might be something enabling ring and cargo-tree has a bug not reporting it. Please open a separate issue with reproduction and we can investigate then.

The Firefox WebGPU team is running into this issue transitively because of once_cell's optional dependency on the sizable portable-atomic crate (see https://github.com/matklad/once_cell/pull/265#discussion_r1783125334. This is particularly painful for us because of a strict cargo vet policy for dependencies in the Mozilla monorepo.
CC @jimb.

Would that be a bug to fix in cargo vet?

@epage We've presented this to the cargo vet maintainers, and they said:

This isn't us, the dependency edge appears in cargo metadata
{
  "id"<EMAIL_ADDRESS>  "dependencies": [
<EMAIL_ADDRESS>  ],
  "deps": [
    {
      "name": "portable_atomic",
      "pkg"<EMAIL_ADDRESS>      "dep_kinds": [
        {
          "kind": null,
          "target": null
        }
      ]
    }
  ],
  "features": [
    "alloc",
    "default",
    "race",
    "std"
  ]
},

There is perhaps some dependency feature unification across multiple targets which is causing this feature to be enabled
There's nothing we can do about that on the cargo-vet side because of the data we get from cargo metadata

In addition to cargo vet, this also causes cargo vendor to incorporate the unused crate into the tree. There are a lot of tools that depend on cargo metadata getting this right.

As explained in my (failed) PR #11938, cargo has two resolvers, and only one of the two has this problem. The other resolver doesn't. I wonder if one could add a mode to cargo metadata to use the "dependency resolver" instead of the "feature resolver".


Fast move feature.

Hi,
Your tool is awesome now. It is more useful than LabelMe (MIT-CSAIL format).
It will be better if there is a feature to move to an image fast. Such as I am in 1000.jpg, but I want to come back 500.jpg to edit. Or already created 500 images, computer is shutdown or close application, next time?
Now, it seems you must to click back or next 500 times.

Do you have idea or suggestions or example about how to move fast? Like add a search bar to jump quickly?

how about add a QComboBox to list the image names?

I think a progress bar or a list of images name is OK.

Fix it  f2712d4

Hi @ck196 @lzx1413 ,
What do you think about this change?

@tzutalin it is awesome.

@tzutalin  good job


MacOS deployment target issue

Thanks for this template -- it's very helpful.
When I ran the Standalone app on Mac OS 10.14.6., I got the error: You have macOS<EMAIL_ADDRESS>The application requires macOS %@ or later. Not sure what's up with the version string there. But adding this to the top of CMakeLists.txt fixed it:
set(CMAKE_OSX_DEPLOYMENT_TARGET "10.13" CACHE STRING "Minimum OS X deployment version")

@jacobweber Thanks for this! I'm guilty of not having tried to build the standalone on this repo, I appreciate the contribution.


Import of icons from @spectrum-icons/workflow fails v3.0.2

🐛 Bug Report
Importing an icon fails in @adobe/react-spectrum v3.0.2
import Airplane from '@spectrum-icons/workflow/Airplane';

🤔 Expected Behavior
Not get an exception at build time.
😯 Current Behavior
When I try to import any icon from '@spectrum-icons/workflow I get an exception:
ERROR in ./node_modules/<EMAIL_ADDRESS>Module not found: Error: Can't resolve '@react-spectrum/provider' in '/Users/smacdona/code/adobeio/devrel/parliament-ui-components/node_modules/@spectrum-icons/ui/node_modules/@react-spectrum/icon/dist'
 @ ./node_modules/<EMAIL_ADDRESS>1:0-55 83:17-28 117:17-28
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS> @ ./src/__stories__/layout.stories.js
 @ ./src/__stories__ sync nonrecursive ^\.\/(?:(?!\.)(?=.)[^/]*?\.stories\.(?:\[tj\]|[tj])s)$
 @ ./.storybook/generated-entry.js
 @ multi<EMAIL_ADDRESS><EMAIL_ADDRESS>./.storybook/config.js ./.storybook/generated-entry.js (webpack)-hot-middleware/client.js?reload=true&quiet=true

💁 Possible Solution
In the react-spectrum/icon component should:
import {useProvider} from '@react-spectrum/provider';

be:
import {useProvider} from '@adobe/react-spectrum';

If I make that change the error goes away but it's replaced by a new one:
ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve '@react-spectrum/provider' in '/Users/smacdona/code/adobeio/devrel/parliament-ui-components/node_modules/@react-spectrum/textfield/dist'
<EMAIL_ADDRESS>2:0-60 57:10-26 166:10-26 215:10-26
<EMAIL_ADDRESS> @ ./src/__stories__/layout.stories.js
 @ ./src/__stories__ sync nonrecursive ^\.\/(?:(?!\.)(?=.)[^/]*?\.stories\.(?:\[tj\]|[tj])s)$
 @ ./.storybook/generated-entry.js
 @ multi<EMAIL_ADDRESS><EMAIL_ADDRESS>./.storybook/config.js ./.storybook/generated-entry.js (webpack)-hot-middleware/client.js?reload=true&quiet=true

🔦 Context
Was trying to move away from including components one by one.
💻 Code Sample
git clone https://github.com/adobe/parliament-ui-components
cd parliament-ui-components
git fetch
git checkout rsv3.0.2
npm install
npm run storybook

You'll see the stack trace.
🌍 Your Environment

Software
Version(s)

@adobe/react-spectrum
3.0.2

@spectrum-icons/workflow
3.0.2

Browser
Chrome

Operating System
MacOS

🧢 Your Company/Team
Adobe I/O
🕷 Tracking Issue (optional)
https://github.com/adobe/parliament-ui-components/issues/10

For anyone who finds this issue because they have a similar problem, the root cause of mine was a package-lock.json file.
Recommended way to get out of this:
npm uninstall @react-spectrum/provider // etc.
rm -rf node_modules package-lock.json
npm install @adobe/react-spectrum @spectrum-icons/workflow


Suggested Solution
I have noticed that the prompt requests messages not exceed 74 characters. Would it be sensible to implement a check that, if a message is longer than 74 characters, prompts the chat to shorten it until it meets this character limit?
Alternatives
No response
Additional Context
No response

reopening, will take a look at this

@Nianmi do you want to send a PR with revised prompt? we should not rely on an LLM, we should just add a line break to the output and structure commit message programatically
@malpou @sebastienfi maybe you guys want to tackle this?

I couldn't find an official standard, but GitKraken provides some guidelines. I don't think this can be achieved with just a line break.
To be honest, LLM development has been progressing at such a rapid pace. Since the introduction of Copilot X, this repo has become somewhat obsolete for me personally. So, please don't feel pressured to fix this on my account. However, I wish you all the best of success.


[ERROR] watcher error unable to decode an event from the watch stream

rancher/rancher:stable   2.3.2
cluster create successful
but  Errors have been reported in the log
2019/11/28 16:12:35 [ERROR] watcher error unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body)
2019/11/28 16:12:35 [ERROR] watcher error unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body)
2019/11/28 16:12:35 [ERROR] watcher error unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body)
Why the above problems ？？？？

Fixed in https://github.com/rancher/rancher/issues/23957


TypeError: a float is required

Dear Zipline Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment

Operating System: Linux 4.4.0-57-generic #78-Ubuntu SMP Fri Dec 9 23:50:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Python Version: Python 2.7.12
Python Bitness: 64
How did you install Zipline: pip
Python packages:

alembic==0.8.9
bcolz==0.12.1
beautifulsoup4==4.5.1
Bottleneck==1.2.0
cachetools==2.0.0
click==6.6
contextlib2==0.5.4
cyordereddict==1.0.0
Cython==0.25.2
decorator==4.0.10
empyrical==0.2.2
funcsigs==1.0.2
intervaltree==2.1.0
Logbook==1.0.0
Mako==1.0.6
MarkupSafe==0.23
mock==2.0.0
multipledispatch==0.4.9
networkx==1.11
numexpr==2.6.1
numpy==1.11.3
pandas==0.16.1
pandas-datareader==0.2.1
patsy==0.4.1
pbr==1.10.0
python-dateutil==2.6.0
python-editor==1.0.3
pytz==2016.10
requests==2.12.4
requests-file==1.4.1
scipy==0.18.1
six==1.10.0
sortedcontainers==1.5.7
SQLAlchemy==1.1.4
statsmodels==0.6.1
stockbot==0.2.0
TA-Lib==0.4.10
toolz==0.8.2
zipline==1.0.2
Now that you know a little about me, let me tell you about the issue I am
having:
I ran the demo example in Stockbot's README, which is:
#!/usr/bin/env python

from logbook import Logger
from stockbot.algo.core import (
    adx_init,
    trade_di,
    trade_so,
)
from stockbot.core import get_sp500_list

def initialize(context):
    return adx_init(
        context,
        name='adx_di_so',
        top_rank=5,
        bot_rank=5,
        di_window=14,
        symbols=get_sp500_list(),
        log=Logger('Stockbot'),
    )

def handle_data(context, data):
    # increment counter and log datetime
    context.i += 1
    context.adx['log'].info('processing %s' % context.get_datetime())

    # trade trending S&P500 stocks using the DI system
    trade_di(
        context,
        data,
        window=context.adx['di_window'],
        portfolio=[i for (i, adx) in context.adx['top']],
        capital_ppi=1.0/(len(context.adx['top'])+len(context.adx['bot'])),
        log=context.adx['log'],
    )

    # trade oscillating S&P500 stocks using the SO system
    trade_so(
        context,
        data,
        window=context.adx['di_window'],
        portfolio=[i for (i, adx) in context.adx['bot']],
        capital_ppi=1.0/(len(context.adx['top'])+len(context.adx['bot'])),
        log=context.adx['log'],
    )

and that I launched through Zipline with:
zipline run -f stockbot_example.py --start 2010-01-01 --end 2016-12-12

However, Zipline dies midway through the download with the following traceback:
Traceback (most recent call last):
  File "/myproject/.env/bin/zipline", line 11, in <module>
    load_entry_point('zipline==1.0.2', 'console_scripts', 'zipline')()
  File "/myproject/.env/local/lib/python2.7/site-packages/click/core.py", line 716, in __call__
    return self.main(*args, **kwargs)
  File "/myproject/.env/local/lib/python2.7/site-packages/click/core.py", line 696, in main
    rv = self.invoke(ctx)
  File "/myproject/.env/local/lib/python2.7/site-packages/click/core.py", line 1060, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/myproject/.env/local/lib/python2.7/site-packages/click/core.py", line 889, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/myproject/.env/local/lib/python2.7/site-packages/click/core.py", line 534, in invoke
    return callback(*args, **kwargs)
  File "/myproject/.env/local/lib/python2.7/site-packages/zipline/__main__.py", line 97, in _
    return f(*args, **kwargs)
  File "/myproject/.env/local/lib/python2.7/site-packages/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/myproject/.env/local/lib/python2.7/site-packages/zipline/__main__.py", line 240, in run
    environ=os.environ,
  File "/myproject/.env/local/lib/python2.7/site-packages/zipline/utils/run_algo.py", line 180, in _run
    overwrite_sim_params=False,
  File "/myproject/.env/local/lib/python2.7/site-packages/zipline/algorithm.py", line 688, in run
    for perf in self.get_generator():
  File "/myproject/.env/local/lib/python2.7/site-packages/zipline/gens/tradesimulation.py", line 220, in transform
    for capital_change_packet in every_bar(dt):
  File "/myproject/.env/local/lib/python2.7/site-packages/zipline/gens/tradesimulation.py", line 133, in every_bar
    handle_data(algo, current_data, dt_to_use)
  File "/myproject/.env/local/lib/python2.7/site-packages/zipline/utils/events.py", line 184, in handle_data
    dt,
  File "/myproject/.env/local/lib/python2.7/site-packages/zipline/utils/events.py", line 203, in handle_data
    self.callback(context, data)
  File "/myproject/.env/local/lib/python2.7/site-packages/zipline/algorithm.py", line 459, in handle_data
    self._handle_data(self, data)
  File "test_stockbot.py", line 50, in handle_data
    log=context.adx['log'],
  File "/myproject/.env/local/lib/python2.7/site-packages/stockbot-0.2.0-py2.7.egg/stockbot/algo/core.py", line 192, in trade_so
    'high': data.history(i, 'high', window + 4, '1d'),
  File "zipline/_protocol.pyx", line 124, in zipline._protocol.check_parameters.__call__.assert_keywords_and_call (zipline/_protocol.c:3193)
  File "zipline/_protocol.pyx", line 626, in zipline._protocol.BarData.history (zipline/_protocol.c:8338)
  File "/myproject/.env/local/lib/python2.7/site-packages/zipline/data/data_portal.py", line 777, in get_history_window
    field)
  File "/myproject/.env/local/lib/python2.7/site-packages/zipline/data/data_portal.py", line 646, in _get_history_daily_window
    assets, days_for_window, end_dt, field_to_use
  File "/myproject/.env/local/lib/python2.7/site-packages/zipline/data/data_portal.py", line 667, in _get_history_daily_window_data
    extra_slot=False
  File "/myproject/.env/local/lib/python2.7/site-packages/zipline/data/data_portal.py", line 909, in _get_daily_window_for_sids
    extra_slot)
  File "/myproject/.env/local/lib/python2.7/site-packages/zipline/data/history_loader.py", line 377, in history
    is_perspective_after)
  File "/myproject/.env/local/lib/python2.7/site-packages/zipline/data/history_loader.py", line 280, in _ensure_sliding_windows
    asset, prefetch_dts, field, is_perspective_after)
  File "/myproject/.env/local/lib/python2.7/site-packages/zipline/data/history_loader.py", line 211, in _get_adjustments_in_range
    ratio)
  File "zipline/lib/adjustment.pyx", line 263, in zipline.lib.adjustment.Float64Adjustment.__init__ (zipline/lib/adjustment.c:5414)
TypeError: a float is required

I'm having the same issue.  date, 2006-12-20 and many others in 2006 quantopian-quandl data

It looks like there's data issues in 2012.  >= 2012 to present, this error doesn't show up.

I have had this problem both with the quantopian-quandl bundle, and my own personal bundles.  After some digging on my personal bundles, I traced the problem down to writing a NaN into the dividend values.  There is a check in the OHLCV section which will not allow NaNs to be written but for some reason the behavior is different with the adjustments writer.  The differences cause this bug to show up only when you are trying to get data from the bundle.


bug: getting AwsSolutions-IAM4 reported even when using managed policy

What is the problem?
AwsSolutions-IAM4 expects that AWS managed policies are not attached to IAM Groups, Users and Roles
When creating a customer managed policy in a stack and assigning it to a role, cdk_nag still gives below error
[Error at RESOURCEID] AwsSolutions-IAM4: The IAM user, role, or group uses AWS managed policies.
Reproduction Steps
#!/usr/bin/env python3
import aws_cdk as cdk
from aws_cdk import aws_iam as iam
from aws_cdk import aws_logs as logs
from aws_cdk import Aspects
from cdk_nag import AwsSolutionsChecks
from constructs import Construct

class IAM4ReplicationStack(cdk.Stack):
    def __init__(self, scope: Construct, construct_id: str, **kwargs) -> None:
        super().__init__(scope, construct_id, **kwargs)

        function_lg = logs.LogGroup(
            self, "rFunctionLogGroup", retention=logs.RetentionDays.SIX_MONTHS
        )

        lambda_custom_policy = iam.ManagedPolicy(
            self,
            "rLambdaCustomPolicy",
            statements=[
                iam.PolicyStatement(
                    effect=iam.Effect.ALLOW,
                    actions=[
                        "logs:CreateLogGroup",
                        "logs:CreateLogStream",
                        "logs:PutLogEvents",
                    ],
                    resources=[function_lg.log_group_arn],
                )
            ],
        )
        iam.Role(
            self,
            "rFunctionRole",
            description="Function role",
            assumed_by=iam.ServicePrincipal("lambda.amazonaws.com"),
            managed_policies=[lambda_custom_policy],
        )

app = cdk.App()
IAM4ReplicationStack(app, "IAM4ReplicationStack")
Aspects.of(app).add(AwsSolutionsChecks())
app.synth()

What did you expect to happen?
CDK synth to not produce any errors
What actually happened?
Got below error
[Error at /IAM4ReplicationStack/rFunctionRole/Resource] AwsSolutions-IAM4: The IAM user, role, or group uses AWS managed policies.
cdk-nag version
2.7.9
Language
Python
Other information
Generated Cfn resource for the role. The cdk_nag source code only works if the ARN of the policy is resolved, in this case it will be a Token.
"rFunctionRoleD438F3B7": {
      "Type": "AWS::IAM::Role",
      "Properties": {
        "AssumeRolePolicyDocument": {
          "Statement": [
            {
              "Action": "sts:AssumeRole",
              "Effect": "Allow",
              "Principal": {
                "Service": "lambda.amazonaws.com"
              }
            }
          ],
          "Version": "2012-10-17"
        },
        "Description": "Function role",
        "ManagedPolicyArns": [
          {
            "Ref": "rLambdaCustomPolicy8309CF07"
          }
        ]
      },
      "Metadata": {
        "aws:cdk:path": "IAM4ReplicationStack/rFunctionRole/Resource"
      }
    }

Thanks for reporting! The rule is incorrectly expecting all non AWS Managed policies to have a 12 digit account number or an AWS::AccountId reference.  {Ref: rLambdaCustomPolicy8309CF07 } would create a false positive.
On another note, this rule should support granular findings. Might as well do both at the same time!


KDBX/argon2 support breaks importer use on Windows

Seems that running the importer doesn't work on Windows as argon2 fails to build correctly.

See buttercup/buttercup-desktop/issues/796 and ranisalt/node-argon2/issues/216


Current master sends change to the input address with avatar mode disabled

An exchange reported that change is (maybe only sometimes) sent to the input address while avatar mode is not enabled. The problem would be present in commit 650ea5f, but not in 6219e88. I can't verify that right now.

I can verify this issue. Coming from our wallet with no avatar mode set in the config file
31968e024cc4a29a3890a2832e4c04fe5f0096c69a630398869d004b68a4fc65
Sent its change back to the input address.

I made PR #97 which seems to fix the issue.
Can someone else try and confirm?

Looks like it's coming from here ;)
https://github.com/glv2/peerunity/commit/364fa630

Fixed in #97 by glv2.


Implement std::error::Error for OscError

Among other things, this allows OscError to be used with the ?
operator in functions that return Result<_, Box<dyn Error>>. It also
makes ? work with functions that use the Error type from the popular
anyhow crate.

I had to lookup why source() was only matching two variants, but of course, the other variants do now wrap any external error 😅
Looks fine to me and clippy had zero complaints, good work 👍🏻
This will get released as rosc 0.5.1.


lapack/gonum: add Dlauu2 and Dlauum

Please take a look.
Updates #746

The bug in GemvT was unexpected but it is fixed now.

Nice bug finding.


Error: No host port found for host IP

Expected Behaviour
Container should start up.
Actual Behaviour

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Error: No host port found for host IP
 ❯ resolveHostPortBinding ../../node_modules/.pnpm/testcontainers@10.11.0/node_modules/testcontainers/src/utils/bound-ports.ts:74:9
 ❯ ../../node_modules/.pnpm/testcontainers@10.11.0/node_modules/testcontainers/src/utils/bound-ports.ts:55:46
 ❯ Function.fromInspectResult ../../node_modules/.pnpm/testcontainers@10.11.0/node_modules/testcontainers/src/utils/bound-ports.ts:54:41
 ❯ GenericContainer.startContainer ../../node_modules/.pnpm/testcontainers@10.11.0/node_modules/testcontainers/src/generic-container/generic-container.ts:177:35
 ❯ processTicksAndRejections node:internal/process/task_queues:95:5
 ❯ createNewReaper ../../node_modules/.pnpm/testcontainers@10.11.0/node_modules/testcontainers/src/reaper/reaper.ts:84:28
 ❯ ../../node_modules/.pnpm/testcontainers@10.11.0/node_modules/testcontainers/src/reaper/reaper.ts:38:14
 ❯ withFileLock ../../node_modules/.pnpm/testcontainers@10.11.0/node_modules/testcontainers/src/common/file-lock.ts:14:12
 ❯ getReaper ../../node_modules/.pnpm/testcontainers@10.11.0/node_modules/testcontainers/src/reaper/reaper.ts:29:12

Testcontainer Logs
  testcontainers [TRACE] Container runtime info:
  testcontainers {
  testcontainers   "node": {
  testcontainers     "version": "v20.16.0",
  testcontainers     "architecture": "arm64",
  testcontainers     "platform": "darwin"
  testcontainers   },
  testcontainers   "containerRuntime": {
  testcontainers     "host": "localhost",
  testcontainers     "hostIps": [
  testcontainers       {
  testcontainers         "address": "::1",
  testcontainers         "family": 6
  testcontainers       }
  testcontainers     ],
  testcontainers     "remoteSocketPath": "/var/run/docker.sock",
  testcontainers     "indexServerAddress": "https://index.docker.io/v1/",
  testcontainers     "serverVersion": "27.1.1",
  testcontainers     "operatingSystem": "Docker Desktop",
  testcontainers     "operatingSystemType": "linux",
  testcontainers     "architecture": "aarch64",
  testcontainers     "cpus": 12,
  testcontainers     "memory":<PHONE_NUMBER>,
  testcontainers     "runtimes": [
  testcontainers       "io.containerd.runc.v2",
  testcontainers       "runc"
  testcontainers     ]
  testcontainers   },
  testcontainers   "compose": {
  testcontainers     "version": "2.29.1-desktop.1",
  testcontainers     "compatability": "v2"
  testcontainers   }
  testcontainers }

Steps to Reproduce
  const postgresContainer = await new PostgreSqlContainer().start();

  process.env.DB_PORT = postgresContainer.getPort().toString();
  process.env.DB_USER = postgresContainer.getUsername();
  process.env.DB_PASS = postgresContainer.getPassword();
  process.env.DB_NAME = postgresContainer.getDatabase();

Environment Information

Operating System: MacOS 14.5
Docker Version: 4.33.0 (160616)
Node version: 20.16.0
Testcontainers version: "@testcontainers/postgresql": "10.11.0"

This is a co-worker's environment. I've checked their MacOS network settings - nothing seems out of the ordinary. They have an IPv4 setup with IPv6 set to automatic. Their docker configuration settings are the default for a docker desktop installation. We also tried stopping all existing containers before re-running without any luck.
One thing I noticed between my own working environment and theirs, is the following:
  testcontainers   "containerRuntime": {
  testcontainers     "host": "localhost",
  testcontainers     "hostIps": [
  testcontainers       {
  testcontainers         "address": "::1",
  testcontainers         "family": 6
  testcontainers       },
  testcontainers       {
  testcontainers         "address": "<IP_ADDRESS>",
  testcontainers         "family": 4
  testcontainers       }
  testcontainers     ],

Mine has an IPv4 recognized while theirs do not:
  testcontainers   "containerRuntime": {
  testcontainers     "host": "localhost",
  testcontainers     "hostIps": [
  testcontainers       {
  testcontainers         "address": "::1",
  testcontainers         "family": 6
  testcontainers       }
  testcontainers     ],

We found a workaround:
TESTCONTAINERS_HOST_OVERRIDE=<IP_ADDRESS>

Testcontainers for Node should support IPv6 port mappings since a long time.
Interestingly, we just closed this IPv6 related PR in tc-go yesterday (https://github.com/testcontainers/testcontainers-go/pull/2403), because Docker/Moby now supports consistent IPv4/IPv6 port mappings (since Docker 27, see https://github.com/moby/moby/pull/47871).
Do you have an idea what is happening here @cristianrgreco? Given the upstream change in Moby, does it maybe make sense to remove the conditional IPv4/IPv6 logic from tc-node, to simplify the code?

Meet same issue in Windows with node 22.12.0 . It comes from https://github.com/nodejs/node/issues/56137. Temporary downgrade to 22.11.0 and wait for fix is released to LTS.


Purchasing a subscription on openiab results in an error

I'm not very familiar with gdx-pay, but it looks like there's an issue with purchasing a subscription on android/openiab. When purchasing an Offer with type OfferType.SUBSCRIPTION it results in the following error:
IabResult: -1008, IAB returned null purchaseData or dataSignature (response: -1008:Unknown error)

this link suggests that this line should call helper.launchSubscriptionPurchaseFlow instead when its type is subscription.

This might be fixed with the latest pull request. Please verify! Thanks.

Thanks. It looks like it hasn't been fixed with latest pull request.

It was not, I didn't work on it.

Ok, i'll go ahead and reopen this then.


⚠ Bofrost.fr has degraded performance

In 9967076, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 3932 ms

Resolved: Bofrost.fr performance has improved in 2b53813 after 7 minutes.