When I train this network on my own dataset, the detector_regr loss suddenly becomes NAN after several iterations

When I train this network on my own dataset, the detector_regr loss suddenly becomes NAN after several iterations

I wonder how to solve this issue, if it is possible to skip the detector regression process during the training

Hey how did you change the path to your own dataset
what modifications did you did in the code


Enable Travis container infra & cache maven deps

See https://github.com/travis-ci/travis-ci/issues/1441 for caching maven deps, https://docs.travis-ci.com/user/workers/container-based-infrastructure for container infra.
Also delete the notifications stanza since google-guice-dev@ doesn't exist anymore.

Hello,
Sorry, I know it's been a long time ago, but I am curious bundler caching was available since December 17, 2014, but I see you just enabled it in this pull request (which is in 2016). Any reasons, please?
Thanks.

This is when it was brought to our attention and/or we had the time research what Travis offered, and/or the time to do anything about it.

I see. Thanks, @sameb, for your response.


Add option to strip sourceURL from scripts injected by puppeteer

I have ported the puppeteer-extra-plugin-stealth package to PuppeteerSharp, with the exception of the sourceURL evasion:
https://github.com/berstend/puppeteer-extra/blob/master/packages/puppeteer-extra-plugin-stealth/evasions/sourceurl/index.js
The other evasions rely on evaluateOnNewDocument and can easily be port (I recommend EnqueueAsyncMessages = true).
This evasion relies on monkey-patching page._client.send, which can't easily be ported. A flag would come in handy here.
The relevant file is ExecutionContext.cs
private Task<RemoteObject> EvaluateExpressionInternalAsync(bool returnByValue, string script)
    => ExecuteEvaluationAsync("Runtime.evaluate", new Dictionary<string, object>
    {
        ["expression"] = _sourceUrlRegex.IsMatch(script) ? script : $"{script}\n{_evaluationScriptSuffix}",
        ["contextId"] = _contextId,
        ["returnByValue"] = returnByValue,
        ["awaitPromise"] = true,
        ["userGesture"] = true
    });

private Task<RemoteObject> EvaluateFunctionInternalAsync(bool returnByValue, string script, params object[] args)
    => ExecuteEvaluationAsync("Runtime.callFunctionOn", new RuntimeCallFunctionOnRequest
    {
        FunctionDeclaration = $"{script}\n{_evaluationScriptSuffix}\n",
        ExecutionContextId = _contextId,
        Arguments = args.Select(FormatArgument),
        ReturnByValue = returnByValue,
        AwaitPromise = true,
        UserGesture = true
    });

What if the connection could raise some event to patch the JSON that is about to be sent?

I suppose that could work.

Actually, I would rather patch the CDPSession than the Connection.

Closed due to inactivity. Feel free to reopen it if needed.


1.0.3

Pull Request Test Coverage Report for Build 8114

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 8109:
0.0%

Covered Lines:
1355

Relevant Lines:
1355

💛  - Coveralls


Supporting image size larger than 64*64

Hello, I would like to know whether there is a specific reason for preventing image size from varying. if not so, do you know what kind of modifications would be required to support, say 512*512 images ?

I have the same question that how to adjust the model to make it support large images?

Hi, sorry for the late reply.
You can vary the size of image resolution by modifying the architecture(BetaVAE_H) defined in model.py(https://github.com/1Konny/Beta-VAE/blob/master/model.py#L32) so that it can handle the image size you want.

@1Konny Thanks so much! I will try this.


[Enhancement Request] Quest Reward Stash Rows

General information
Project issue is for:
Server
/Server/src/branch/master/project/src/helpers/QuestHelper.ts
https://dev.sp-tarkov.com/SPT-AKI/Server/src/commit/42db0aca0bf19772778d2608dfdea7410afa9cc5/project/src/helpers/QuestHelper.ts#L943
Would be a nice-to-have feature in the QuestHelper if the QuestRewardType.STASH_ROWS was implemented. Would be a low priority request and not important but would be a good enhancement for custom Quest makers. I also believe this was a reward type for some of the event quests from live.

Originally written by acidphantasm

Created a PR to add this functionality. Tested by adding a reward to "Shooting Cans" to give 2 stash rows. Requires a client restart after completion.
https://dev.sp-tarkov.com/SPT-AKI/Server/pulls/316#issue-5876

Originally written by acidphantasm


Add ability to turn off LED without locking submit button in calibrator

Some people want to submit calibration values while the LED is off so they can verify the zero value reading. At the moment, the submit button is locked while the LED is off. We want a way to have the submit button available for these people.

Closed with c4d43091f5acdaaaf76a01bf7331537cdd5cbaec


Issues running the VMM

I get this error when trying to run the DMA cheat any solutions for it?

Did you got leechcore.dll aswell in your directory ?

One of the DLLs were bugged I redownloaded it and everything is working great again


Terragrunt catalog command clones repos on every invocation

Describe the bug
According to the Medium article on terragrunt catalog the command should only clone the configured repos on the first invocation.

Note: the catalog command will git clone the repos locally, so the first run may take a little while if you have lots of repos, but it should be much faster on all re-runs.

The docs are a little more vague as they just say the repos are cloned into a temporary folder.
Steps To Reproduce
Using the example from the Medium article above, if I add the catalog config to the root terragrunt file in our infra repo
catalog {
  urls = [
    "https://github.com/gruntwork-io/terragrunt-infrastructure-modules-example",
    "https://github.com/gruntwork-io/terraform-aws-utilities",
    "https://github.com/gruntwork-io/terraform-kubernetes-namespace"
  ]
}

The results I'm seeing are that the repos are cloned (into the same temporary folder) on each catalog invocation.
❯ tg catalog
10:35:12.380 INFO   Cloning repository "git::https://github.com/gruntwork-io/terragrunt-infrastructure-modules-example.git" to temporary directory "/var/folders/s3/zm9trzfs4cd6900ws1qhvfdh0000gp/T/catalog5a5f7a556b6a764d7757384d7a55516e437742456d616f6f413577/terragrunt-infrastructure-modules-example"
10:35:13.762 INFO   Found 5 modules in repository "https://github.com/gruntwork-io/terragrunt-infrastructure-modules-example"
10:35:13.762 INFO   Cloning repository "git::https://github.com/gruntwork-io/terraform-aws-utilities.git" to temporary directory "/var/folders/s3/zm9trzfs4cd6900ws1qhvfdh0000gp/T/catalog4e5732674b627567715f364f6947554c45717a7a4132514766714d/terraform-aws-utilities"
10:35:16.613 INFO   Found 11 modules in repository "https://github.com/gruntwork-io/terraform-aws-utilities"
10:35:16.613 INFO   Cloning repository "git::https://github.com/gruntwork-io/terraform-kubernetes-namespace.git" to temporary directory "/var/folders/s3/zm9trzfs4cd6900ws1qhvfdh0000gp/T/catalog69625338504b4c684c66353434305f45594d486c74495a4d725959/terraform-kubernetes-namespace"
10:35:17.728 INFO   Found 4 modules in repository "https://github.com/gruntwork-io/terraform-kubernetes-namespace"
❯
❯ tg catalog
10:35:20.898 INFO   Cloning repository "git::https://github.com/gruntwork-io/terragrunt-infrastructure-modules-example.git" to temporary directory "/var/folders/s3/zm9trzfs4cd6900ws1qhvfdh0000gp/T/catalog5a5f7a556b6a764d7757384d7a55516e437742456d616f6f413577/terragrunt-infrastructure-modules-example"
10:35:23.323 INFO   Found 5 modules in repository "https://github.com/gruntwork-io/terragrunt-infrastructure-modules-example"
10:35:23.323 INFO   Cloning repository "git::https://github.com/gruntwork-io/terraform-aws-utilities.git" to temporary directory "/var/folders/s3/zm9trzfs4cd6900ws1qhvfdh0000gp/T/catalog4e5732674b627567715f364f6947554c45717a7a4132514766714d/terraform-aws-utilities"
10:35:27.127 INFO   Found 11 modules in repository "https://github.com/gruntwork-io/terraform-aws-utilities"
10:35:27.127 INFO   Cloning repository "git::https://github.com/gruntwork-io/terraform-kubernetes-namespace.git" to temporary directory "/var/folders/s3/zm9trzfs4cd6900ws1qhvfdh0000gp/T/catalog69625338504b4c684c66353434305f45594d486c74495a4d725959/terraform-kubernetes-namespace"
10:35:29.149 INFO   Found 4 modules in repository "https://github.com/gruntwork-io/terraform-kubernetes-namespace"

Expected behavior
On second catalog invocation the repositories should not be cloned again (into the same temporary folder).
Either the Medium article is incorrect, I'm doing something wrong, or this is a bug.
Versions

Terragrunt version: v0.68.4

Hey @tgeijg ,
Thanks for submitting this issue! At the very least, our logs will need updating if we're avoiding the secondary clone, but reporting it as another clone.
Marking this issue as preserved so that it doesn't go stale. Definitely worth addressing.

Hi @yhakbar
Just to add some more info: Out of curiosity I ran some test with a few more repos - 40 to be exact - in the catalog config. Results below:
❯❯ time tg catalog
09:59:07.375 INFO   Cloning repository<EMAIL_ADDRESS>to temporary directory "/var/folders/s3/zm9trzfs4cd6900ws1qhvfdh0000gp/T/catalog78364c3256384b62486c507854427165422d37756e37585

...

"/var/folders/s3/zm9trzfs4cd6900ws1qhvfdh0000gp/T/catalog55674a5f734835564d4c2d7773333952467078646f525a48625045"
10:00:36.775 INFO   Found 1 modules in repository "git@gitlab.com:rivian/dc/platform/terraform-modules/lakeformation.git//."

terragrunt catalog  7.64s user 13.29s system 22% cpu 1:31.57 total

❯❯ time tg catalog
10:00:41.944 INFO   Cloning repository<EMAIL_ADDRESS>to temporary directory "/var/folders/s3/zm9trzfs4cd6900ws1qhvfdh0000gp/T/catalog78364c3256384b62486c507854427165422d37756e37585

...

"/var/folders/s3/zm9trzfs4cd6900ws1qhvfdh0000gp/T/catalog55674a5f734835564d4c2d7773333952467078646f525a48625045"
10:02:07.977 INFO   Found 1 modules in repository "git@gitlab.com:rivian/dc/platform/terraform-modules/lakeformation.git//."

terragrunt catalog  7.30s user 12.55s system 22% cpu 1:27.07 total

❯❯ time tg catalog
10:02:15.978 INFO   Cloning repository<EMAIL_ADDRESS>to temporary directory "/var/folders/s3/zm9trzfs4cd6900ws1qhvfdh0000gp/T/catalog78364c3256384b62486c507854427165422d37756e37585

...

"/var/folders/s3/zm9trzfs4cd6900ws1qhvfdh0000gp/T/catalog55674a5f734835564d4c2d7773333952467078646f525a48625045"
10:03:41.321 INFO   Found 1 modules in repository "git@gitlab.com:rivian/dc/platform/terraform-modules/lakeformation.git//."

terragrunt catalog  7.32s user 12.40s system 22% cpu 1:26.63 total

Or in short, three consecutive runs ran within a few seconds of each other. It sure doesn't seem to be significantly faster on the second run
1. - 7.64s user 13.29s system 22% cpu 1:31.57 total
2. - 7.30s user 12.55s system 22% cpu 1:27.07 total
3. - 7.32s user 12.40s system 22% cpu 1:26.63 total

I believe you that we have a bug preventing re-use of already cloned modules.
My guess as to the origin of this bug is that we initially cloned once, but users wanted to allow catalogs to update without changing URLs. We could have introduced logic to use git ls-remote to check if the ref moved, but instead we just cloned each time.
Again, this is just a guess, but it would be plausible to me if that was the case.
I think a solution that would be better than saving a stashed clone of each ref would be to use something like this:
https://github.com/yhakbar/cln
The problem with storing a stashed clone of each ref is that there would be no space savings between updates. If you are using the default branch of a Catalog URL as the source of your catalog, then changing one file in your repo would result in an almost entirely duplicate copy of your repo on disk.
I would assume that most users would prefer a Content Addressable Store (CAS) to store an immutable read-only copy of every object in the repo, and to use that when perusing the catalog.
Would you agree with that? If so, I'm not sure when we would get to that, but that's the design we'd use for the final implementation.

That's a pretty neat idea @yhakbar. And yes, I do think that would be a better approach in this case.


Trigger Builder-Base update for EKS Go 1.18

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Develop a REST API service to Show all items in the shopcart

As a User
I need a way to show all items in the shopcart
So that I can easily check what I have in the shopcarts now
Assumptions

The base url is /shopcarts/<cartName>
The method of this API should be GET
Url should return all the products in the shopcart in a list

Acceptance Criteria:
Given the service is available
When I call the URL `GET /shopcarts/<cartName>`
Then it should return a list of items that are in the shopcarts

This issue is part of issue #7, so I closed this issue to avoid duplicated work.


wrong number of arguments in validates_attachment_size during upload

Hi,
When I try to upload a new asset, I get the below an error message
I have an older application running on

Papercliped version unknown...
Paperclip version 2.3.1 (vendorized)
Radiant version 0.8.2
Rails version 2.3.4
Ruby version 1.8.7 (i686-darwin11.0.0)
RubyGems version 1.4.2
Rack version 1.0

I am wondering whether there is an incompatibility between the version of rails/radiant/paperclip/paperclipped?
I can't' find out what version of paperclipped I am running, how can I tell?  Looking at paperclipped_extension.rb the version says 0.8.0, but looking at the latest release of paperclipped the version is still 0.8.0
What version of paperclip do I need to run with paperclipped for Radiant 0.8.2?
Thanks,
Dave
The error message is:
/Users/dave/code/app/vendor/extensions/paperclipped/vendor/plugins/paperclip/lib/paperclip.rb:229:in `validates_attachment_size'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:284:in `[]'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:284:in `allow_validation?'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:274:in `validate'
/Users/dave/code/app/vendor/extensions/paperclipped/vendor/plugins/paperclip/lib/paperclip.rb:229:in `inject'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:272:in `each'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:272:in `inject'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:272:in `validate'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:93:in `assign'
/Users/dave/code/app/vendor/extensions/paperclipped/vendor/plugins/paperclip/lib/paperclip.rb:204:in `asset='
/Users/dave/code/app/vendor/radiant/vendor/rails/activerecord/lib/active_record/base.rb:2744:in `send'
/Users/dave/code/app/vendor/radiant/vendor/rails/activerecord/lib/active_record/base.rb:2744:in `attributes='
/Users/dave/code/app/vendor/radiant/vendor/rails/activerecord/lib/active_record/base.rb:2740:in `each'
/Users/dave/code/app/vendor/radiant/vendor/rails/activerecord/lib/active_record/base.rb:2740:in `attributes='
/Users/dave/code/app/vendor/radiant/vendor/rails/activerecord/lib/active_record/base.rb:2438:in `initialize'
/Users/dave/code/app/vendor/extensions/paperclipped/app/controllers/admin/assets_controller.rb:22:in `new'
/Users/dave/code/app/vendor/extensions/paperclipped/app/controllers/admin/assets_controller.rb:22:in `create'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:1331:in `send'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:1331:in `perform_action_without_filters'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/filters.rb:617:in `call_filters'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/filters.rb:610:in `perform_action_without_benchmark'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
/Users/dave/code/app/vendor/radiant/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms'
/Users/dave/.rvm/rubies/ruby-1.8.7-p352/lib/ruby/1.8/benchmark.rb:308:in `realtime'
/Users/dave/code/app/vendor/radiant/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/rescue.rb:160:in `perform_action_without_flash'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/flash.rb:146:in `perform_action'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:532:in `send'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:532:in `process_without_filters'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/filters.rb:606:in `sass_old_process'
/Users/dave/code/app/vendor/radiant/vendor/plugins/haml/lib/sass/plugin/rails.rb:19:in `process'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:391:in `process'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:386:in `call'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/routing/route_set.rb:437:in `call'

The request attributes are:
{"commit"=>"Create Asset",
 "format"=>"html",
 "authenticity_token"=>"2TOdLSQ/KEnE6IR0VVxd2OlfhoAH+9OqGUvj3TIPYGs=",
 "asset"=>{"title"=>"moving-house-image",
 "caption"=>"",
 "asset"=>#<File:/var/folders/yd/c5x54_ps3j1dmwzmd7drdtbh0000gn/T/RackMultipart20111202-45084-8paokl-0>}}

Hi Dave,
I think you need stick to older versions of paperclip. 2.3.1 will not work. I am not sure, as Paperclipped is no longer supported and I have not used it in some time, but I think 2.0.8 or so should work.
I highly encourage you to update to Clipped, it is the replacement for Paperclipped and now a part of the basic Radian package.
Keith
On Dec 1, 2011, at 11:13 PM, Dave Harris wrote:

Hi,
When I try to upload a new asset, I get the below an error message
I have an older application running on

Papercliped version 2.2.8
Paperclip version 2.3.1 (vendorized)
Radiant version 0.8.2
Rails version 2.3.4
Ruby version 1.8.7 (i686-darwin11.0.0)
RubyGems version 1.4.2
Rack version 1.0

I am wondering whether there is an incompatibility between the version of rails/radiant/paperclip/paperclipped?
What version of paperclip do I need to run with paperclipped v2.2.8?
Thanks,
Dave
The error message is:
/Users/dave/code/app/vendor/extensions/paperclipped/vendor/plugins/paperclip/lib/paperclip.rb:229:in `validates_attachment_size'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:284:in `[]'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:284:in `allow_validation?'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:274:in `validate'
/Users/dave/code/app/vendor/extensions/paperclipped/vendor/plugins/paperclip/lib/paperclip.rb:229:in `inject'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:272:in `each'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:272:in `inject'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:272:in `validate'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:93:in `assign'
/Users/dave/code/app/vendor/extensions/paperclipped/vendor/plugins/paperclip/lib/paperclip.rb:204:in `asset='
/Users/dave/code/app/vendor/radiant/vendor/rails/activerecord/lib/active_record/base.rb:2744:in `send'
/Users/dave/code/app/vendor/radiant/vendor/rails/activerecord/lib/active_record/base.rb:2744:in `attributes='
/Users/dave/code/app/vendor/radiant/vendor/rails/activerecord/lib/active_record/base.rb:2740:in `each'
/Users/dave/code/app/vendor/radiant/vendor/rails/activerecord/lib/active_record/base.rb:2740:in `attributes='
/Users/dave/code/app/vendor/radiant/vendor/rails/activerecord/lib/active_record/base.rb:2438:in `initialize'
/Users/dave/code/app/vendor/extensions/paperclipped/app/controllers/admin/assets_controller.rb:22:in `new'
/Users/dave/code/app/vendor/extensions/paperclipped/app/controllers/admin/assets_controller.rb:22:in `create'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:1331:in `send'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:1331:in `perform_action_without_filters'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/filters.rb:617:in `call_filters'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/filters.rb:610:in `perform_action_without_benchmark'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
/Users/dave/code/app/vendor/radiant/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms'
/Users/dave/.rvm/rubies/ruby-1.8.7-p352/lib/ruby/1.8/benchmark.rb:308:in `realtime'
/Users/dave/code/app/vendor/radiant/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/rescue.rb:160:in `perform_action_without_flash'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/flash.rb:146:in `perform_action'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:532:in `send'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:532:in `process_without_filters'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/filters.rb:606:in `sass_old_process'
/Users/dave/code/app/vendor/radiant/vendor/plugins/haml/lib/sass/plugin/rails.rb:19:in `process'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:391:in `process'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:386:in `call'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/routing/route_set.rb:437:in `call'

The request attributes are:
{"commit"=>"Create Asset",
"format"=>"html",
"authenticity_token"=>"2TOdLSQ/KEnE6IR0VVxd2OlfhoAH+9OqGUvj3TIPYGs=",
"asset"=>{"title"=>"moving-house-image",
"caption"=>"",
"asset"=>#<File:/var/folders/yd/c5x54_ps3j1dmwzmd7drdtbh0000gn/T/RackMultipart20111202-45084-8paokl-0>}}

Reply to this email directly or view it on GitHub:
https://github.com/kbingman/paperclipped/issues/40

Hi Keith,
Thanks for the quick response!
I will look into those things on Monday, but I think downgrading
paperclip will be the best solution in this instance
I will let you know how it goes
Dave
On 2/12/2011, at 9:19 PM, Keith Bingman
<EMAIL_ADDRESS>wrote:

Hi Dave,
I think you need stick to older versions of paperclip. 2.3.1 will not work. I am not sure, as Paperclipped is no longer supported and I have not used it in some time, but I think 2.0.8 or so should work.
I highly encourage you to update to Clipped, it is the replacement for Paperclipped and now a part of the basic Radian package.
Keith
On Dec 1, 2011, at 11:13 PM, Dave Harris wrote:

Hi,
When I try to upload a new asset, I get the below an error message
I have an older application running on

Papercliped version 2.2.8
Paperclip version 2.3.1 (vendorized)
Radiant version 0.8.2
Rails version 2.3.4
Ruby version 1.8.7 (i686-darwin11.0.0)
RubyGems version 1.4.2
Rack version 1.0

I am wondering whether there is an incompatibility between the version of rails/radiant/paperclip/paperclipped?
What version of paperclip do I need to run with paperclipped v2.2.8?
Thanks,
Dave
The error message is:
/Users/dave/code/app/vendor/extensions/paperclipped/vendor/plugins/paperclip/lib/paperclip.rb:229:in `validates_attachment_size'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:284:in `[]'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:284:in `allow_validation?'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:274:in `validate'
/Users/dave/code/app/vendor/extensions/paperclipped/vendor/plugins/paperclip/lib/paperclip.rb:229:in `inject'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:272:in `each'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:272:in `inject'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:272:in `validate'
/Users/dave/code/app/vendor/gems/thoughtbot-paperclip-2.3.1/lib/paperclip/attachment.rb:93:in `assign'
/Users/dave/code/app/vendor/extensions/paperclipped/vendor/plugins/paperclip/lib/paperclip.rb:204:in `asset='
/Users/dave/code/app/vendor/radiant/vendor/rails/activerecord/lib/active_record/base.rb:2744:in `send'
/Users/dave/code/app/vendor/radiant/vendor/rails/activerecord/lib/active_record/base.rb:2744:in `attributes='
/Users/dave/code/app/vendor/radiant/vendor/rails/activerecord/lib/active_record/base.rb:2740:in `each'
/Users/dave/code/app/vendor/radiant/vendor/rails/activerecord/lib/active_record/base.rb:2740:in `attributes='
/Users/dave/code/app/vendor/radiant/vendor/rails/activerecord/lib/active_record/base.rb:2438:in `initialize'
/Users/dave/code/app/vendor/extensions/paperclipped/app/controllers/admin/assets_controller.rb:22:in `new'
/Users/dave/code/app/vendor/extensions/paperclipped/app/controllers/admin/assets_controller.rb:22:in `create'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:1331:in `send'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:1331:in `perform_action_without_filters'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/filters.rb:617:in `call_filters'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/filters.rb:610:in `perform_action_without_benchmark'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
/Users/dave/code/app/vendor/radiant/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms'
/Users/dave/.rvm/rubies/ruby-1.8.7-p352/lib/ruby/1.8/benchmark.rb:308:in `realtime'
/Users/dave/code/app/vendor/radiant/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/rescue.rb:160:in `perform_action_without_flash'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/flash.rb:146:in `perform_action'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:532:in `send'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:532:in `process_without_filters'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/filters.rb:606:in `sass_old_process'
/Users/dave/code/app/vendor/radiant/vendor/plugins/haml/lib/sass/plugin/rails.rb:19:in `process'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:391:in `process'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:386:in `call'
/Users/dave/code/app/vendor/radiant/vendor/rails/actionpack/lib/action_controller/routing/route_set.rb:437:in `call'

The request attributes are:
{"commit"=>"Create Asset",
"format"=>"html",
"authenticity_token"=>"2TOdLSQ/KEnE6IR0VVxd2OlfhoAH+9OqGUvj3TIPYGs=",
"asset"=>{"title"=>"moving-house-image",
"caption"=>"",
"asset"=>#<File:/var/folders/yd/c5x54_ps3j1dmwzmd7drdtbh0000gn/T/RackMultipart20111202-45084-8paokl-0>}}

Reply to this email directly or view it on GitHub:
https://github.com/kbingman/paperclipped/issues/40

Reply to this email directly or view it on GitHub:
https://github.com/kbingman/paperclipped/issues/40#issuecomment-2987504

Hi Keith,
I have tired replacing paperclip but couldn't find the version 2.0.8 you say.
Looking at the https://github.com/thoughtbot/paperclip/tags page, I have tried both versions 2.0.2 and 2.1.0, but they both fail.
2.0.2 fails before the file upload process even starts with a
NameError: uninitialized constant Tempfile
~/code/app/vendor/radiant/vendor/rails/activesupport/lib/active_support/dependencies.rb:443:in load_missing_constant'   ~/code/app/vendor/radiant/vendor/rails/activesupport/lib/active_support/dependencies.rb:80:in const_missing'
~/code/app/vendor/radiant/vendor/rails/activesupport/lib/active_support/dependencies.rb:92:in `const_missing'
~/code/app/vendor/gems/thoughtbot-paperclip-2.0.2/lib/paperclip/thumbnail.rb:72
2.1.0 seems to work with the app, but when attempting to upload an image I get
undefined method call' for #<Array:0x109d3e668>     app/vendor/gems/thoughtbot-paperclip-2.1.0/lib/paperclip/attachment.rb:179:in validate'
app/vendor/radiant/vendor/rails/activerecord/lib/active_record/attribute_methods.rb:211:in `collect'
I probably shouldn't be asking you, but do you have any ideas?
Dave


Subscribing to topics

Thanks for you amazing project!
Im wondering if this is a normal behaviour:
Every time I open https://my.domain.com i have to Re-Subscribe to all of my topics in order to see previous or future notifications. On android app it always stays subscribed so im wondering if that could be done on PC too. Can it be turned on in settings or somewhere so that all of the topics are always shown once I go to the webpage of my server? Thanks in advance!

I assume this is a question about the web app. The web app is supposed to keep your subscriptions and messages stored locally in the browser's IndexedDB. Normal browsers support that, but the incognito mode does not.

My bad, i had automatical removal of cookies so thats why the notification topics had to be added every single time.


incorporating python hashseed in pyproject.toml

I really don't think this will work - PYTHONHASHSEED setting has to happen before the python process has started, and not by using os.environ (by which time its already too late). Is there a way for us to verify if this is actually working? (by writing a test that works only when this is working, and fails otherwise, like the set/list experiments we were doing on the command line, nothing to do with CLM).
If it appears to work for the CLM tests, it may just be that they just work without PYTHONHASHSEED anyway (which could be another quick test).


HNC: Move subnamespace creation to HNSR and simplify HCR

Part of #457
We will move the subnamespace creation from HierarhyConfig Reconciler (HCR) to HierarchyicalNamespace Reconciler (HNSR) to simplify the logic and make it easier to understand.
The HNSR will take care of the subnamespace creation/deletion based on the HNS instances. When HNSR creates a subnamespace, it will set correct owner annotation on the subnamespace.
We will use the namespace annotation as the source of truth for the ownership, since modifying a namespace has higher privilege than what HNC users can do.
The implementation detail of this change will be:
Source of truth: Owner annotation on the subnamespace
Conditions/states to report:

Namespace condition: HNS_MISSING
(If the HNS is missing in the owner NS or the owner NS is missing)
HNS state: Conflict
(If the owned namespace is missing)

Forest:

Add a list of names of the HNSes in the namespace: ns.HNSes
(This will be updated in each HCR by an api list)
Remove ns.Owner field and add ns.isOwned bool field, since the parent will always be the owner in the annotation.

HCR:

Additionally watch HNS instances. Map it only to the parent HC (since the child NS will be created/deleted by HNSR and thus will be reconciled by HCR naturally). This makes it easier for cascading deletion to remove HC finalizers when there's no HNS instances in the namespace.
onMissingNamespace(): remove the namespace creation of the previous RequiredChild.
syncOwner() sets parent to owner. Look through the owner’s ns.HNSes in the forest, if not found, set HNS_MISSING condition.
syncParent() unchanged.
syncChildren(): Will remove SubnamespaceConflict condition and only update the children list from forest to spec since any existing owned namespace always has owner as its parent and if the owned ns is missing, the HNS will have Conflict state.
Add syncHNSes(): It will update HNS list in the syncWithForest(): ns.SetHNSes(hnsnms).

HNSR:

Additionally watch NS instances. Map it only to its owner (parent) HNS, e.g. {Name: ns.name, Namespace: ns.getAnnotation()[owner]}. If anything's changed with the owned namespace (creation/deletion/annotation change), the HNS will be reconciled.
If subnamespace doesn't exist, it will create one with correct owner annotation.
Update hns.status.state accordingly.

(The cascading deletion part is not included in this change)

The only thing left here is:
Remove ns.Owner field and add ns.isOwned bool field, since the parent will always be the owner in the annotation.


P2P trade bugs

delete this style
.ant-input, .ant-select-selection__rendered {
/* line-height: 40px!important; */
}
delete margins
.row {
/* margin-right: -15px; /
/ margin-left: -15px; */
}
this is how it currently looks

this is how it should look like

PR here https://github.com/dexlab-io/DexEx/pull/34
@dimarconicola


Improve the Existing Lazy Loading and Error Handling of TensorFlow-Keras Integration In Tools Compat Template V1

This Pull Request refines the inter operation between TensorFlow and Keras by paying special attention to the enhancement of lazy initialization and the enhancement of error handling. The variable TF_USE_LEGACY_KERAS is now handled in a more permissive way to handle case sensitivity issues properly. Also, the script adaptively changes module paths based on the usage of legacy or standard version of Keras, thus making it compatible with multiple TensorFlow configurations.
The changes outlined above make the script much better for use and more stable. With improvements in the lazy loading feature and the incorporation of more explicit and detailed exception handling the script has the ability to handle a wider range of TensorFlow and Keras configurations thereby reducing the chances of encountering runtime exceptions. The changes also make the script more compatible across the versions of TensorFlow and help in making it more suitable for different environments.

This pull request introduces several key enhancements to the TensorFlow-Keras integration:This pull request introduces several key enhancements to the TensorFlow-Keras integration:

Improved Lazy Loading: The lazy loading mechanism has been improved especially on how Keras modules and submodules are to be loaded depending on the TF_USE_LEGACY_KERAS environment variable. This will make the integration easier irrespective of whether one is using the legacy or the current Keras.

 This improvement is beneficial in making the script less prone to errors and in case of occurrence, it is easy to identify.

Dynamic Path Configuration: There are also new features which include, the script now adapts module paths making it compatible with different TensorFlow and Keras configurations.

These updates taken together enhance the stability, compatibility and the usability of the TensorFlow-Keras integration in the module. These changes should help prevent runtime errors and should make it easier to switch between different environments with no problems.