Zero recall value while evaluating on LMO dataset

Hello @wangg12
I tried to evaluate the GDR-Net model on LMO dataset using the pretrained models you shared on OneDrive.
I used following command to run the valuation:
python core/gdrn_modeling/main_gdrn.py --config-file configs/gdrn/lmo/a6_cPnP_AugAAETrunc_BG0.5_lmo_real_pbr0.1_40e.py \
 --num-gpus 1 \
--eval-only  \
--opts MODEL.WEIGHTS=output/gdrn/lmo/a6_cPnP_AugAAETrunc_BG0.5_lmo_real_pbr0.1_40e/gdrn_lmo_real_pbr.pth

However, it is showing zero recall values. Please see the screenshot below.
Could you please help?
Thank you,
Supriya

Maybe you should check your full running log to see where the problem is.

The features from the backbone is a tensor of zeros.
tensor([[[[0., 0., 0.,  ..., 0., 0., 0.],
          [0., 0., 0.,  ..., 0., 0., 0.],
          [0., 0., 0.,  ..., 0., 0., 0.],
          ...,
          [0., 0., 0.,  ..., 0., 0., 0.],
          [0., 0., 0.,  ..., 0., 0., 0.],
          [0., 0., 0.,  ..., 0., 0., 0.]]]], device='cuda:0')

The log says all weights (backbone, pnp_net and rot_head) from the checkpoint are loaded correctly. Still the output of backbone is zero tensor.
Did you encounter such error before? Do you know what might be causing it?
See below the log
20221204_124725|fvcore.common.checkpoint@152: [Checkpointer] Loading from D:/research/data/gdrnet_data/gdrn/lmo/a6_cPnP_AugAAETrunc_BG0.5_lmo_real_blender_160e/model_final_wo_optim.pth ...
20221204_124728|d2.checkpoint.c2_model_loading@324: Following weights matched with model:
| Names in Model                        | Names in Checkpoint                                                                       | Shapes                         |
|:--------------------------------------|:------------------------------------------------------------------------------------------|:-------------------------------|
| backbone.bn1.*                        | backbone.bn1.{bias,num_batches_tracked,running_mean,running_var,weight}                   | (64,) () (64,) (64,) (64,)     |
| backbone.conv1.weight                 | backbone.conv1.weight                                                                     | (64, 3, 7, 7)                  |
| backbone.layer1.0.bn1.*               | backbone.layer1.0.bn1.{bias,num_batches_tracked,running_mean,running_var,weight}          | (64,) () (64,) (64,) (64,)     |
| backbone.layer1.0.bn2.*               | backbone.layer1.0.bn2.{bias,num_batches_tracked,running_mean,running_var,weight}          | (64,) () (64,) (64,) (64,)     |
| backbone.layer1.0.conv1.weight        | backbone.layer1.0.conv1.weight                                                            | (64, 64, 3, 3)                 |
| backbone.layer1.0.conv2.weight        | backbone.layer1.0.conv2.weight                                                            | (64, 64, 3, 3)                 |
| backbone.layer1.1.bn1.*               | backbone.layer1.1.bn1.{bias,num_batches_tracked,running_mean,running_var,weight}          | (64,) () (64,) (64,) (64,)     |
| backbone.layer1.1.bn2.*               | backbone.layer1.1.bn2.{bias,num_batches_tracked,running_mean,running_var,weight}          | (64,) () (64,) (64,) (64,)     |
| backbone.layer1.1.conv1.weight        | backbone.layer1.1.conv1.weight                                                            | (64, 64, 3, 3)                 |
....
| pnp_net.fc1.*                         | pnp_net.fc1.{bias,weight}                                                                 | (1024,) (1024,8192)            |
| pnp_net.fc2.*                         | pnp_net.fc2.{bias,weight}                                                                 | (256,) (256,1024)              |
| pnp_net.fc_r.*                        | pnp_net.fc_r.{bias,weight}                                                                | (6,) (6,256)                   |
| pnp_net.fc_t.*                        | pnp_net.fc_t.{bias,weight}                                                                | (3,) (3,256)                   |
.....
| rot_head_net.features.0.weight        | rot_head_net.features.0.weight                                                            | (512, 256, 3, 3)               |
| rot_head_net.features.1.*             | rot_head_net.features.1.{bias,num_batches_tracked,running_mean,running_var,weight}        | (256,) () (256,) (256,) (256,) |
| rot_head_net.features.10.weight       | rot_head_net.features.10.weight                                                           | (256, 256, 3, 3)               |

Thank you,
Supriya

Hi @wangg12,
Could you please tell which version of detectron2 you have used?
The detectron2 website link that you shared in README.md (link) is for detectron2 version 0.6.
Circled in red in the image below

Yes. But I installed from source. It seems you were running on windows, could you run the code on Ubuntu?

Thank you for the suggestion @wangg12.
I figured out the issue.
The features from backbone were zero because the weights of backbone were zero.
The checkpoint was getting loaded correctly but for some unknown reason, Line 550 in gdrn_evaluator.py was resetting the weights to zero.
I resolved this issue by loading the checkpoint again after line 550.
I got the following result.
Could you please tell me what does each metric in the first column stand for, i.e. what does ad_2, rete_2, re_2, te_2, proj_2, re, te stand for?

Thank you,
Supriya

Here https://github.com/THU-DA-6D-Pose-Group/GDR-Net/blob/main/core/gdrn_modeling/gdrn_custom_evaluator.py#L772 you can find what those metrics mean.


fix(connectors): lnbits incoming payments shows outgoing ones as well

Describe the changes you have made in this PR
lnbits payments api shows outgoing and incoming payments. Negative ones are outgoing and need to be filtered out for our incoming txs.
Link this PR to an issue [optional]
Fixes #1631
Type of change

fix: Bug fix (non-breaking change which fixes an issue)

Screenshots of the changes [optional]

How has this been tested?
Manually by sendign sats back and forth

did you test it (potentially with different lnbits installations)?

Isn't the API behaving the same among lnbits installations? Where else could I test it?

is the ordering correct (maybe also add the sorting there?)?

Sorting looks good, no? See screenshot above.

if you tested it and everything works, then merge it.
I'd still add the sorting (which you added also for lnd)?

if you tested it and everything works, then merge it.

Tested with our lnbits account form the e2e tests.

I'd still add the sorting (which you added also for lnd)?

The sort takes care of an API flaw which doesn't exist in the lnbits API. So I would not add it.


Reverting latest commit

The latest commit #71 seems to have broken the build, reverting for the time bing.

cc @ueshin


module update

Update tflite-micro to a version compatible with CMSIS-NN v6.0.0

Turns out main is the branch kept up to date, not zephyr, so this PR was targeting the wrong place.
See #6


Convert robot_ws package to ROS2

Convert all the launch files, package.xml, and nodes to be ROS2 dashing compatible.
The launch files are now equivalent to the ROS1 versions, so you can specify LAUNCH_ID or ROS_AWS_REGION environment variables which will do equivilant overrides and you can specify the same aws_metrics_namespace or log_group_name parameters, and they fall back to the config file if unset (using sample app config file if it's set, or CE config file otherwise).
Requires these PR's to be merged to work correctly:
https://github.com/aws-robotics/cloudwatchlogs-ros2/pull/6
https://github.com/aws-robotics/cloudwatchmetrics-ros2/pull/8
https://github.com/aws-robotics/health-metrics-collector-ros2/pull/3
I'll publish simulation_ws changes in a separate PR to make them not so overwhelming. simulation_ws changes are still WIP.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Nice! Have we verified that this works as expected in regards to parameter passing?
A good way to test it might be to launch the app with aws_region parameter set to eu-west-1 (anything other than us-west-2) and verify the nodes' parameters, following up with verification in CloudWatch console (that the metrics/logs were indeed emitted to eu-west-1).

To get the CI build passing could you please adjust the travis.yml like we did in https://github.com/aws-robotics/aws-robomaker-sample-application-helloworld/blob/ros2/.travis.yml ? You can put a COLCON_IGNORE in simulation_ws if that isn't ready yet.

Nice! Have we verified that this works as expected in regards to parameter passing?

Yep tested with ros2 launch cloudwatch_robot monitoring.launch.py aws_region:=ap-northeast-1 and it correct sent all logs and metrics to that region.

To get the CI build passing could you please adjust the travis.yml

done


[DRC-755] [Feature] Compare Renamed Columns

Describe the feature
is there a way to compare columns if one is renamed in the PR? Example: Column A gets renamed to Column B, but we want to compare the values in Column A in the old model to Column B in the new model
Describe alternatives you've considered
Have looked into using a macro from audit_helper but it would be great to use this within Recce
Who will this benefit?
Column names are frequently changed for clarity, sometimes in tandem with a logic update. Having this functionality available will allow as to validate that the column values have not changed unexpectedly, even though the original column has been replaced.
Are you interested in contributing this feature?
No response
Anything else?
No response
DRC-755

Hi @tkrishna-equip , thanks for your feedback.
Since it's quite difficult to determine in Recce whether two columns are originally the same, do you think comparing A and B using different queries would solve your problem?
Base query:
select
 customer_id,
 name as user_name,
 life_time_value
from customers

Current query:
select
 customer_id,
 user_name,
 life_time_value
from customers

The limitation is that both query results need to have the same columns. This is very similar to the audit_helper's solution

@popcornylu are you proposing using the ordinal position of the column as an option for Recce to compare values? I support that idea!

Idea: Provide a way to way SQL for the base and current separately in query diff.

(Bonus) Model renaming can be covered as well
In the future, we may support advanced diffs.


Add overview of all transactions in 'Streeplijst'

Currently the streeplijst allows only for viewing the last 5 transactions. For checking the correctness of your streeplijst it is easier if an overview is provided of all your transactions, similar to how banking software does it. Either by extending the current screen:

Or by adding a button: All transactions. Thanks in advance :)

I overlooked the feature that literally does this haha, well done!


Merge middleware repo into bitbox-base

See individual commit messages for explanation of the changes here, and what they achieve.
If the concept looks good, I'd be happy to update documentation to describe the current build process after this change (either in this PR or a follow-up).

I like the overall approach.

Thanks!

When looking at this solution as a new user that has set up Go as recommended and wants to build the project, however, I'm a bit lost.

Okay. I responded to your find that a user without $GOPATH specified or one that has checked out the repo outside of their ${GOPATH}/src would hit build errors, and I'll address that.

I think, either further documentation of all necessary steps, or interactive error messages with pointers would help. At the moment I would not be able to get it up and running without trial & error.

Yup, as mentioned above I'll address the flaw you pointed out.
I mentioned the documentation aspect in the PR description:

If the concept looks good, I'd be happy to update documentation to describe the current build process after this change (either in this PR or a follow-up).

Since you seem to have said that the concept looks good at this point, let me know your preference for updating docs; should that be done in this PR, or can it be a follow-up?

We'd want to ideally support a user that has go installed but no ${GOPATH} and/or has checked out the repository outside ${GOPATH} too, though. At the very least, we should detect this case and give a friendly hint as to what to change.
I'll think about how to best achieve this and push another commit that addresses this flaw.

Sounds good. looking forward to that. Otherwise I thinks it's fine for the moment.

We'd want to ideally support a user that has go installed but no ${GOPATH} and/or has checked out the repository outside ${GOPATH} too, though. At the very least, we should detect this case and give a friendly hint as to what to change.
I'll think about how to best achieve this and push another commit that addresses this flaw.

Sounds good. looking forward to that. Otherwise I thinks it's fine for the moment.

See new commit abc6fafc5e096eaedd784086a44262a05e11dec1 which achieves that.
Thanks for the review earlier @Stadicus. PTAL.
Bad environment; no GOPATH set
In a clean checkout of abc6fafc5e096eaedd784086a44262a05e11dec1 in /tmp/bitbox-base:
$ cd /tmp/bitbox-base/middleware
$ echo $GOPATH
$
$ make
./scripts/check-env.sh "/tmp/bitbox-base/middleware/.."

================================================================================
fatal: ./scripts/check-env.sh:
  ${GOPATH} needs to be set to build Go programs, and the repository
  needs to checked out inside ${GOPATH}/src.

  Your current ${GOPATH} is:
  ""

  Your repository is checked out at:
  "/tmp/bitbox-base/middleware/.."

  For more information, see:
  https://github.com/golang/go/wiki/GOPATH#vendor-directories-ignored-outside-of-gopath
================================================================================

make: *** [Makefile:5: check-env] Error 1
$

Bad environment; REPO_ROOT outside GOPATH
In a clean checkout of abc6fafc5e096eaedd784086a44262a05e11dec1 in /tmp/bitbox-base:
$ cd /tmp/bitbox-base/middleware
$ export GOPATH=~/
$ make
./scripts/check-env.sh "/tmp/bitbox-base/middleware/.."

================================================================================
fatal: ./scripts/check-env.sh:
  ${GOPATH} needs to be set to build Go programs, and the repository
  needs to checked out inside ${GOPATH}/src.

  Your current ${GOPATH} is:
  "/home/user/"

  Your repository is checked out at:
  "/tmp/bitbox-base/middleware/.."

  For more information, see:
  https://github.com/golang/go/wiki/GOPATH#vendor-directories-ignored-outside-of-gopath
================================================================================

make: *** [Makefile:5: check-env] Error 1
$

Bad environment; ${REPO_ROOT} inside ${GOPATH} but not inside ${GOPATH}/src
In a clean checkout of abc6fafc5e096eaedd784086a44262a05e11dec1 in /tmp/bitbox-base:
$ cd /tmp/bitbox-base/middleware
$ export GOPATH=/tmp
$ make
./scripts/check-env.sh "/tmp/bitbox-base/middleware/.."

================================================================================
fatal: ./scripts/check-env.sh:
  ${GOPATH} needs to be set to build Go programs, and the repository
  needs to checked out inside ${GOPATH}/src.

  Your current ${GOPATH} is:
  "/tmp"

  Your repository is checked out at:
  "/tmp/bitbox-base/middleware/.."

  For more information, see:
  https://github.com/golang/go/wiki/GOPATH#vendor-directories-ignored-outside-of-gopath
================================================================================

make: *** [Makefile:5: check-env] Error 1
$

Good environment; ${REPO_ROOT} inside ${GOPATH}/src
In a clean checkout of abc6fafc5e096eaedd784086a44262a05e11dec1 in /tmp/src/bitbox-base (note, now under /tmp/src, i.e under ${GOPATH}/src if GOPATH=/tmp):
$ cd /tmp/src/bitbox-base/middleware/
$ export GOPATH=/tmp
$ make
./scripts/check-env.sh "/tmp/src/bitbox-base/middleware/.."
GOARCH=arm64 go build -o /tmp/src/bitbox-base/middleware/../build/base-middleware ./src/
$ echo $?
0
$

utACK https://github.com/digitalbitbox/bitbox-base/commit/abc6fafc5e096eaedd784086a44262a05e11dec1


Verb conjugation consistency with related articles

@shsagir - can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@Ana-AlonsoCanizares Thanks for the feedback. The topic needs to be refreshed in general fr which I've created an internal work item. We'll consider your suggestion when that happens. For now, I'm closing this PR without accepting the proposed changes.
#please-close


Recent JSON Marshal/Unmarshal commit broke JSON body parsing

Problem statement
I have an API that pulls login credentials from a JSON body payload.  It works fine with 0.12.0 but with master (commit dbc9b97 at this time) it breaks.  Calling the endpoint yields a 400 with the message
{
  "code": 400,
  "message": "parsing credentials body from \"\" failed, because json: cannot unmarshal object into Go value of type *models.Credentials"
}

Binding in my code is done via:
api.AuthenticationPostLoginHandler = authentication.PostLoginHandlerFunc(login)
with function defnition:
func login(params authentication.PostLoginParams) middleware.Responder { ... }
If I checkout tag 0.12.0 everything works.
Swagger specification
Relevant portions of my swagger.yml:
paths:
  /login:
    post:
      summary: Login endpoint
      description: 'Login here'
      security: []
      consumes:
        - application/json
      produces:
        - application/json
      parameters:
        - name: credentials
          in: body
          schema:
            $ref: '#/definitions/Credentials'
      responses:
        '200':
          description: Success
          schema:
            $ref: '#/definitions/Login'
        '400':
          description: Bad Request
          schema:
            $ref: '#/definitions/Message'
        '401':
          description: Invalid credentials
          schema:
            $ref: '#/definitions/Message'

and
definitions:
  Credentials:
    properties:
      username:
        type: string
      password:
        type: string
      token:
        type: string

Steps to reproduce
If it would help I can try to construct a minimal codebase that induces the error, but I'm hoping this is simple enough that the fix will be obvious to @EleanorRigby and won't require that.
Environment
swagger version: master branch
go version: 1.9
OS:   Linux (CentOS 7)

@EleanorRigby I think this comes from golangs json library using the textmarshaler interfaces itself too.
As such what we didn't isn't very helpful and will break more applications than the fix it's trying to provide.
We should revert this commit and look at why redirects aren't being respected instead

The pull request to back out the change has been  created  #1178

Thanks, I'm back to normal now!


Delete clusters (s3 or dir or yaml files) - fix code

To support all flows of cluster deletion from s3 bucket / directory or s3 bucket from yaml files:

do not call clusters_from_directories
fix call to submit

/verified


Add ability to change exit code

What should be done:

[ ] Exit with the code 1 If there is at least one warning;
[ ] Add the command line argument: -exit CODE --exit-code CODE;
[ ] Add a validation to ensure that the code is a number;
[ ] If a user uses this argument and there is at least one warning - exit with the user code;
[ ] Add usage information to README.

Hey, I think it would be better if the tool is failing with an exit code when at least one warning exists by default and not with an additional argument.
This is default behavior of a linter in my opinion.

@mstruebing Good catch! Thank you. I've updated this issue.

One question, why should the user be capable of manually choosing which exit code is used when failing occurs?
As far as I understand exit codes, and used them, it is totally up to the tool to decide which exit code to use.
Every exit code has a meaning, so it shouldn't be user decidable.
I.e you could use an exit code 1 for example to indicate wrongly used arguments and exit code 2 for errors in the .env-files.
So in short: Exit code has meaning, shouldn't be customizable by user input.

@mstruebing I think you're right.
But I have another question - Should we give the user the ability to change the exit code from 1 to 0 if dotenv-linter finds at least one warning?
For example, golangci-lint lets do it like that:
$ golangci-lint run --issues-exit-code=0

Or another example - golint sets the exit status to 1 if any issues are found like that:
$ golint -set_exit_status

I don't think this is a good idea. I run the linter to catch issues and get notified, this is done best by an exit code != 0.
What would make sense, in my opinion, is, if we would make a difference between warnings and errors (which we don't do at the moment, and I don't know if it would be cool) and give the user the option to decide if warnings would produce an exit code != 0 and errors always produce an exit code != 0.

Updated.

I have made a pull request that should solve this issue.
See #58 .
Feedback is appreciated


Check status code of grafana response

#8

Thanks, looks good. I will merge it when I have a change. Hopefully soon.

A similar fix was introduced by an earlier PR and merged in ed04c53d60f8686c038b6ddf6ebfe1bf9a7e02d6.


Add -keepalive option to enable or disable connection pooling

Every BenchmarkMode has a default how to deal with connection pooling. In mode "latency" the connection pooling is disabled, why the DisableKeepAlives() function returns true.
The mode "burst" returns false, to enable connection pooling.
With this commit the user can explicitly enable or disable the connection pooling by specifying the -keepalive cli option.
Usage:
storage-benchmark -keepalive enabled
storage-benchmark -keepalive disabled
If -keepalive is not set the selected BenchmarkMode (-mode) decides.

Sorry. Have to redo it.


Add BOOL type to DATA_TYPE_TO_CPP map

Description
This PR adds DataType.BOOL => bool to the DATA_TYPE_TO_CPP map in gt_backends.py.

This is such a trivial change that is of course fine to merge, but have you actually tested that bool fields work properly in actual stencils? Do they work for all internal backends? And for dawn backends?

Thank you @egparedes, the Dawn backends already had bool in their mapping:
_DATA_TYPE_TO_CPP = {
    gt_ir.DataType.BOOL: "bool",
    gt_ir.DataType.INT8: "int",
    gt_ir.DataType.INT16: "int",
    ...
}

I have also added a stencil to stencil_definitions.py to test boolean fields.


Change while to while-do

Since changing how blocks and bindings work, you can no longer create a temporary binding inside a while loops condition. I also am not a huge fan that the while loop block now has hidden meaning, rather than just being an expression.
I'm thinking about the following:
fn main() {
    0 while {
        as [i] i
        i 10 <
     } do {
        as [i]
        i println
        1 +
    }
}

while true do {
    "loop" println
}


Unable to download videos from YouTube

~ $ youtube-dl http://www.youtube.com/watch?v=c1VD1D1hLsQ[youtube] Setting language
[youtube] c1VD1D1hLsQ: Downloading video webpage
[youtube] c1VD1D1hLsQ: Downloading video info webpage
[youtube] c1VD1D1hLsQ: Extracting video information
ERROR: no fmt_url_map or conn information found in video info
just installed from extras-testing, any suggestions?
at least one other had the same issue in this thread http://talk.maemo.org/showthread.php?t=65290&page=6

As documented in the FAQ, this error occurred after youtube switched up its interface, and has been fixed shortly thereafter in youtube-dl. Update youtube-dl with youtube-dl -U (depending on your installation, you may need root privileges for that).
If the problem persists, please post the output of youtube-dl --version and reopen this bug (or open a new one).

thank you


Allow @log_api_call decorator to be applied to multiple routes

I may be mistaken, but if the @log_api_call decorator follows the @app.route decorator the view function mapping overwrites the log_api_call_wrapper.  I discovered this when I tried to add the decorator to a new route.
If this is incorrect, please advise.

Thanks!


remove mongo secret from production.js

removed secrets in mongo URI from production.js

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Revert "Revert "Don't write to standard err""

Reverts vespa-engine/vespa#17078
Should be ok after https://github.com/vespa-engine/system-test/pull/1435

HierarchicDistributionTest::test_no_ready_copies started failing after this went in. Consider reverting or annotating/fixing test


[go_router_builder] [shellroute] Add support

Use case
As of 5.0.0 GoRouter release, ShellRoute API was added to implement nested navigation. However, go_router_builder still does not support this one.

Proposal
Implement ShellRoute using another annotation.

@hawkkiller Thanks for the report! This is a known issue being tracked at #111909
I also see your PR for this, so please re-link the PR to #111909. Thanks!

@hawkkiller Thanks for the report! This is a known issue being tracked at #111909
I also see your PR for this, so please re-link the PR to #111909 then I will close this issue as a duplicate. Thanks for your contribution!

@huycozy made it.


[Feat] Gpu data filter 2

Step. 2 GPU Data filtering feature (#328)

refactor filterData to filterDataset
filter dataset based on gpu or cpu mode
set gpuChannel in filter and gpuFilter in dataset to be passed to layer

Curious, have we tried this out on mobile?

Curious, have we tried this out on mobile?
This should be no difference between gpu filtering and brushing. All we are doing is sending additional uniforms and attributes to shader. I tested the brushing example that I built for deck.gl example, works on mobile


Let cargo handle the compilation of RISC-V assembly

This adds a binary crate courtesy of @perlindgren which allows us to use cargo to compile the provided RISC-V assembly.
The solution is really funky, via Commands we copy the source file and linker script into the ./riscv_asm binary crate, compile it with cargo build --release , then move the compilation results back into ./ .
The binary crate consists of basically global_asm!(include_str!("<ASM_SOURCE_FILE_PATH>")), and a rustc flag to use the linker script.
I tried making it Windows compatible, but am unable to test it, so would appreciate some help there.

During compilation the asm.s and memory.x is copied to the riscv_asm folder and run there to generate the binary to execute. This is behavior is currently hardcoded, we can think of improving this procedure when the RISC simulator is compiled as a standalone binary.


Calendar should output month and week headers

[x] Just before a month, output the month date/name
[ ] At the beginning of each month inject weekdays header (if organized by month)

Currently:

day template is not coming through
passed in day templates may not be parsing bindings.


fix: swiftlint configuration file

Summary of Changes
Only SwiftLint config file changes.

excluded some rules that will force us to introduce breaking changes;
fixed commented_out_code rule. It was triggered by // swiflint:... comments that are used to enable/disable SwiftLint rules in code.

Test Data or Screenshots
By submitting this pull request, you are confirming the following:

I have reviewed the Contribution Guidelines.
I have performed a self-review of my own code.
I have updated my repository to match the develop branch.
I have included test data or screenshots that prove my fix is effective or that my feature works.
I have checked that all tests work and swiftlint is not throwing any errors/warnings.

@cclauss This and one additional PR with changes created only by swiftlint --fix will be part of the SwiftLint fixes "epic".

@cclauss @janndriessen .swiftlint.yml rules and excluded files reordered + aligned opt_in_rules.


ValidationMigrationTask won't migrate matches-regex

Mule3 API with the following validation
<validation:matches-regex message="[API Message]: Status is #[flowVars.httpStatusFromPayload]. Expected 200" exceptionClass="java.lang.Exception" value="#[flowVars.httpStatusFromPayload]" regex="200" doc:name="Throw Exception Message"/>
Mule4 API after the migration.
 <validation:matches-regex message="[API Message]: Status is #[flowVars.httpStatusFromPayload]. Expected 200" exceptionClass="java.lang.Exception" value="#[vars.httpStatusFromPayload]" regex="200" doc:name="Throw Exception Message" />
Message is not migrated

Hi, @holiday-sunrise! This looks like a known gap: the message attribute uses a template (text with embedded expressions). Templates in Mule 4 are supported by a handful of components like the logger and parse template, but not the matches-regex operation.
We will review the feasibility of supporting the migration of templates. If it helps, the migrated value should be:
message="#['[API Message]: Status is $(vars.httpStatusFromPayload). Expected 200']"

It works fine if we migrate it by hand


Check for gha updates daily with dependabot

This will check any github action which this project uses for updates on a daily basis using dependabot in order to keep packages up-to-date.
https://docs.github.com/en/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot

LGTM


Failed to auto configure default logger context

When I use sbt running hello-world project, it was occur:
Failed to auto configure default logger context
Reported exception:
ch.qos.logback.core.joran.spi.JoranException: Problem parsing XML document. See previously reported errors.
at ch.qos.logback.core.joran.event.SaxEventRecorder.recordEvents(SaxEventRecorder.java:67)
at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:134)
at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:99)
need I implement slf4j myself?

Beside, port 9990 report a 404:
Some endpoints are only available when the correct dependencies are added to your class path.
For more information, please see the twitter-server docs or return to /admin.

See https://github.com/twitter/finatra/pull/285.


where is mobile  ssd model?

where is mobile  ssd model? where is it.where  is  mobile net model??

Perhaps you're looking for:
https://research.googleblog.com/2017/06/mobilenets-open-source-models-for.html
https://github.com/tensorflow/models/blob/master/research/slim/nets/mobilenet_v1.md
https://github.com/tensorflow/tensorflow/tree/master/tensorflow/examples/android
For future reference, this type of question is better asked on  StackOverflow since it is not a  bug or feature request. There is also a larger community that reads questions there. Thanks!


[python][bug] GradingPrimary.saturation broken when used in solo.

Hello,
I have noticed that when using a GradingPrimary instance with only the saturation modified, when ported to a GradingPrimaryTransform and then applied to an image, the saturation change is not registered and the output image is unchanged.
Now if I only modified by a very little another attribute like GradingPrimary.exposure, the saturation is registered and applied to the input.
You can find a demo in the following snippet, where the test_sat_only will be the only one to fail.
(only the TestGradingPrimaryTransform.config_path need to be updated with any valid OCIO config)
# python>3
import unittest
from pathlib import Path
from typing import Tuple

import PyOpenColorIO as ocio
import numpy
import numpy.testing

def make_img(color: Tuple[float, float, float]):
    """Create a 64x64 RGB image with the given color."""
    return numpy.full((64, 64, 3), color, dtype=numpy.float32)

class TestGradingPrimaryTransform(unittest.TestCase):

    config_path = Path(
        r"YOURCONFIGPATH\config.ocio"
    )

    def setUp(self) -> None:
        self.config: ocio.Config = ocio.Config().CreateFromFile(str(self.config_path))
        self.img1 = make_img((0.5, 0.1, 0.1))
        self.gp: ocio.GradingPrimary = ocio.GradingPrimary(ocio.GRADING_LIN)
        return

    def tearDown(self) -> None:
        self.config = None
        self.img1 = None
        return

    def _apply_gp_on_img(self):

        tsfm_gp = ocio.GradingPrimaryTransform(
            self.gp,
            ocio.GRADING_LIN,
            False,
        )

        proc: ocio.Processor = self.config.getProcessor(tsfm_gp)
        proc: ocio.CPUProcessor = proc.getDefaultCPUProcessor()

        proc.applyRGB(self.img1)

        return

    def test_sat_only(self):

        # MODIFY
        p_sat = 2.0

        self.gp.saturation = p_sat

        self._apply_gp_on_img()

        expected = make_img((0.815, 0.015, 0.015))
        numpy.testing.assert_almost_equal(
            self.img1,
            expected,
            4,
            f"img1 is actually {self.img1[1][1]} while expected is {expected[1][1]}",
        )

    def test_sat_expo(self):

        # MODIFY
        p_sat = 2.0
        p_expo = 0.02  # in "stops", passthrough is 0

        self.gp.saturation = p_sat
        self.gp.exposure = ocio.GradingRGBM(0, 0, 0, p_expo)

        self._apply_gp_on_img()

        expected = make_img((0.82637, 0.01521, 0.01521))
        numpy.testing.assert_almost_equal(
            self.img1,
            expected,
            4,
            f"img1 is actually {self.img1[1][1]} while expected is {expected[1][1]}",
        )

    def test_offset_only(self):

        # MODIFY
        p_offset = 0.4

        self.gp.offset = ocio.GradingRGBM(0, 0, 0, p_offset)

        self._apply_gp_on_img()

        expected = make_img((0.9, 0.5, 0.5))
        numpy.testing.assert_almost_equal(
            self.img1,
            expected,
            4,
            f"img1 is actually {self.img1[1][1]} while expected is {expected[1][1]}",
        )

    def test_clampwhite_only(self):

        # MODIFY
        p_clampwhite = 0.4

        self.gp.clampWhite = p_clampwhite

        self._apply_gp_on_img()

        expected = make_img((0.4, 0.1, 0.1))
        numpy.testing.assert_almost_equal(
            self.img1,
            expected,
            4,
            f"img1 is actually {self.img1[1][1]} while expected is {expected[1][1]}",
        )

if __name__ == "__main__":
    unittest.main()

CONTEXT: Windows10, OCIO 2.1.0
Cheers.
Liam.

As a workaround for now I am detecting if GradingPrimary has been modified from default value and if only the saturation
is non-default I am simply doing settings an extreme value for clampBlack (which trigger the saturation) :
        gp = ocio.GradingPrimary(self.grading_space)
        gp.contrast = to_rgbm_ocio(self.contrast)
        gp.lift = to_rgbm_ocio(self.lift)
        gp.offset = to_rgbm_ocio(self.offset)
        gp.pivot = self.pivot
        gp.saturation = self.saturation

        # HACK saturation :
        # https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/1642
        if self.is_modified_sat_only:
            gp.clampBlack = -150

Disclaimer: I don't speak C++, I can't unfortunately make a MR for this
So I had a look at the source code, I don't know if this is intentional but seems saturation is excluded from the localBypass
checks where value affecting it are only clampBlack, clampWhite, contrast, exposure, offset.
https://github.com/AcademySoftwareFoundation/OpenColorIO/blob/b00877959f4497f9b8e5a08859d0ef8059fdd8e5/src/OpenColorIO/ops/gradingprimary/GradingPrimary.cpp#L195-L197
This is of course for the GRADING_LINEAR mode which from the doc state :

Linear controls: Exposure, Contrast, Pivot, Offset, Saturation, Black Clip, White Clip.

So indeed saturation which is supported seems to be forgotten.
This seems to also be valid for GRADING_LOG and GRADING_VIDEO.
Cheers.
Liam.

Thank you @MrLixm for your thorough work investigating this issue.  We will make sure to look into this!

We ran into this while using GradingPrimary to implement a CDL with only saturation adjustment.
Looks like we missed the GradingPrimary fixes on the latest round of patch releases.


Failed to install tools under analysis tools of GoLang

I got problem when installing the analysis tools for GoLang when using vscode.
What version of Go are you using (go version)?
<go version go1.13.5 windows/amd64>
Does this issue reproduce with the latest release?
Yes, the problem still exists in the latest release.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
<set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\gordo\AppData\Local\go-build
set GOENV=C:\Users\gordo\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\gordo\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=c:\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\gordo\AppData\Local\Temp\go-build859780870=/tmp/go-build -gno-record-gcc-switches>
What did you do?

What did you expect to see?
Those tools failed to install should be succeed without any problems!
What did you see instead?
Installing github.com/mdempsky/gocode FAILED
Installing github.com/uudashr/gopkgs/cmd/gopkgs FAILED
Installing github.com/ramya-rao-a/go-outline FAILED
Installing github.com/stamblerre/gocode FAILED
Installing github.com/rogpeppe/godef FAILED
Installing github.com/sqs/goreturns FAILED
Installing golang.org/x/lint/golint FAILED
7 tools failed to install.

Hello , unlike other projects, we do not use the issue tracker for questions such as these. It is only used for bugs and feature proposals. I will close this issue, but please feel free to ask it in any of these forums below:

Stack Overflow with questions tagged "go"

The Go Forum, a web-based forum

Gophers Slack, use the invite app for access. The #general channel is a good starting point.

Go Community on Hashnode with questions and posts tagged with "go"

The golang-nuts mailing list

IRC channel #go-nuts on Freenode

Thanks

@GordonHK: I would also recommend filing an issue on the VS Code Go repository for issues with VS Code (https://github.com/microsoft/vscode-go/issues).


Refactor patient experience API interactions to use REST

Related Issue or Background Info

Resolves #559
Resolves #864
Resolves #849 (also has a separate PR, #874)
Resolves #761

Changes Proposed

Removes from the GraphQL schema queries and mutations that would be used by the Patient Experience
Adds a PatientExperienceController for the relevant endpoints
Adds CORS configuration for local development
Adds a PxpApiService in the front end for these API interactions
Refactors GraphQL interactions in the Patient Experience to use the new REST endpoints

@jeskew-gov This looks ready-to-merge except for the Security Hotspot, which is due to the fact that CORS is enabled and CSRF are disabled in the dev security config. Can we mark that as reviewed in SonarCloud, or should I just merge this as-is despite the failing gate?

@jeskew-gov This looks ready-to-merge except for the Security Hotspot, which is due to the fact that CORS is enabled and CSRF are disabled in the dev security config. Can we mark that as reviewed in SonarCloud, or should I just merge this as-is despite the failing gate?

SonarQube just requires a manual review whenever the security configuration is updated, and I don't think we have a way to suppress that on the DevSecurityConfiguration class.


Feature Request: Ask A111 to add this as an extension

A111 now has the ability to have scripts and javascript to be added as an extension without having to have scripts and javascript populate outside of [basedir]/extensions/extension-name
It also offers the ability to update from github from inside A111.
I've done a quick test of your script loaded as an extension and as far as I can tell it all works like normal.
You might want to consider asking Automatic1111 to add your script to the list located at: https://raw.githubusercontent.com/wiki/AUTOMATIC1111/stable-diffusion-webui/Extensions-index.md

Yeah, I added support for extension installation around a week ago and have it as the recommended install method in the README (at least the English one).
I guess I can ask him to put it there as well, true.

Done, thanks for the reminder.
https://github.com/AUTOMATIC1111/stable-diffusion-webui/wiki/Extensions#booru-tag-autocompletion


how can write widget with the blade in sage 9

Submit a feature request or bug report

[x] I've read the guidelines for Contributing to Roots Projects
[ ] This is a feature request
[x] This is a bug report
[x] This request isn't a duplicate of an existing issue
[x] I've read the docs and NPM Debugging Guidelines post and followed them (if applicable)
[ ] This is not a personal support request that should be posted on the Roots Discourse forums

What is the current behavior?
how can write widget with the blade in sage 9
my widget folder in sage 9
framework -> widget -> widget.php
I need to change this widget to be by the blade

As this is a personal support request and not a bug, please ask this on Discourse: https://discourse.roots.io/


Exercise 2.2

The result of action-value estimates maybe error. Sample-average action-value estimate is used to estimate it.

Can you more concretely explain what you mean?

in book, the author use Q_t(a) = (sum of rewards when a taken prior to t) / (numer of times a taken prior to t), so, when t = 4, Q_4(a_1) = (1 * 1) / 1 = 1, and Q_4(a_2) = (1 * 1 + 2 * 1) / (1+1) = 3 / 2, right?

Exercise 2.4 don't exist, can you store it again? Thank you!

You are correct. Thanks for spotting it out. I had incorrectly calculated the Q-values with the sum of the previous scores, and forgot to divide them in order to get the average instead.
I have submitted a fix:
https://github.com/diegoalejogm/Reinforcement-Learning/blob/master/2. Multi-Armed Bandits/README.md

Exercise 2.4 solution is found as a link in the markdown file.
You can directly access the solution here

Closing this issue. Feel free to re-open if something is not clear


Improve the documentation

As an user
I to start using the tool without having to watch a  demo/training
So that I can make use of the tool on my own pace

Thank @rogeralmeida for your feedback.
What do you think to have something like:

one idp configure
one login <SSO Provider>
Make sure your project contains the file one.yaml set in your project.
one workspace change
Execute terraform commands with one terraform <command>

hey @arthurbdiniz , they all sound like good ideas.
But I believe we are missing real boring documentation. Something like:

https://www.terraform.io/docs/index.html
https://docs.spring.io/spring/docs/current/spring-framework-reference/
https://help.ubuntu.com/lts/ubuntu-help/getting-started.html.en

manpages and https://tldr.sh are necessary as well IMHO


MWPW-130540: add commerce OST UI tests

Closing for now due to inability to run these tests outside vpn


Integration with PyTorch/XLA

In the last few weeks, we've been having active conversations with @shauheen and @miladm, and we're working on a plan for adoption of StableHLO in PyTorch/XLA. Will keep this ticket posted about our progress!

Thanks for creating this ticket @burmako. I am working on a RFC for integrating StableHLO in PyTorch/XLA.
CC @shauheen, @JackCaoG

We now have a more clear plan of how TorchXLA and StableHLO interact. And we now have several APIs in TorchXLA to export StableHLO: TorchXLA > stablehlo.md.
Given this, I am closing this ticket. If additional support is needed, this should be done using finer grained tickets.


Login with social network account and cannot save account information cos no password has been set up before

Because i register the account using social network account, that means i dnt need to set up password. but when i try to update the account information, i saw the update password function there. it looks like you cannot set up a new password without current password.
i think it is a bug which you cannot recognize whether a current password is necessary in case user is registered by social network account.

This is not a bug. Password for user registered via network is generated automatically and sent via email message on the registration step.


Terraform and Ansible for paws deploy

Bug: T326435
Currently does not run the
kubectl apply -f manifests/psp.yaml
step as the dev env went down before I could create something for this. This is probably mostly ok, as the first deploy of this is likely to be the removal of psp (hopefully in a move to k8s 1.25), so it would have been removed regardless if that is the case. If not it can be added. For now it is in the DEPLOY file, so it is still noted on how to use it.
Also we cannot create a trove db in codfw1dev, though this is probably not a terraform thing:
https://phabricator.wikimedia.org/T333364
We can create a trove db in eqiad1, though cannot create a magnum template:
https://phabricator.wikimedia.org/T333703
maybe I've got the variables for image or flavor incorrect? Same does work in codfw1dev.

https://phabricator.wikimedia.org/T333364 is resolved, so this now works, with the noted exception of deploying k8s, in codfw1dev. We can merge and continue work as this is put into use.


Is there logo/icon for Mini SSG

I like writing about frontend developing in my blog. So, I put the icons in blog's home.
The icon also good for branding.

Thanks for the suggestion, will let it open, until we have one :)


Update sbt-pgp to 2.1.2

Updates com.jsuereth:sbt-pgp from 1.1.2-1 to 2.1.2.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.jsuereth", artifactId = "sbt-pgp" } ]

labels: sbt-plugin-update, semver-major

https://github.com/sbt/sbt-pgp


feat(k8s-test): Try login and obtain API token

Simple "give me login page" is not enough. It should be possible to log in to the working application.
This PR add test for:

simple login
simple API test - get token

Added based on #10490

It looks like there has not been any activity here for a while. In order to keep the list of pull requests in a manageable state, we are closing this one for now. If we are making a mistake here, please reopen the pull request, and leave us a note 😄


Fix users update route

A non-admin user cannot update other users, the route must return a 401 HTTP status (unauthorized) today it's returning a 500 (internal server error)

Hi! May I work on this one?

@m-pereira

Hi! May I work on this one? @m-pereira

For sure, go for it!


Compile game back for Playstation

Game is already can be compiled with modern converted Psy-Q, but it doesn't run.
Ideally next tasks should be performed:

[x] Select preferred methods to compile PSX version (Original or converted modern Psy-Q SDK)
[x] Make memory regions/sections mapping (for malloctab, frontend overlay buffer, data buffer, replay buffer)
[x] Make necessary scripts to build ISO file
[x] Make it running

All items has been completed - game now can be built for PSX and it runs.
Notes:

many frontend bugs and crashes
have problems with controls on some emulators
crashes
no language text support yet (have built-in or PC-like table?)
slow CD loading times due to FileExists
sound reverberation doesn't deactivate properly
screen frame adjustment is incorrect for NTSC
possibly lower performance


fp32 vs bf16 training performance?

I train the openfold in both fp32 and bf16, it seems bf16 performs better than fp32 or the fp32 config is not properly set by me?
The command for bf16 is
python3 train_openfold.py mmcif_dir/ alignment_dir/ template_mmcif_dir/ output_dir/
2021-10-10 \
--template_release_dates_cache_path mmcif_cache.json \
--precision bf16
--gpus 8 --replace_sampler_ddp=True
--seed 4242022 \ # in multi-gpu settings, the seed must be specified
--deepspeed_config_path deepspeed_config.json
--checkpoint_every_epoch
--resume_from_ckpt ckpt_dir/
--train_chain_data_cache_path chain_data_cache.json
--obsolete_pdbs_file_path obsolete.dat
The command for fp32 is
python3 train_openfold.py mmcif_dir/ alignment_dir/ template_mmcif_dir/ output_dir/
2021-10-10 \
--template_release_dates_cache_path mmcif_cache.json \
--precision 32
--gpus 8 --replace_sampler_ddp=True
--seed 4242022 \ # in multi-gpu settings, the seed must be specified
--deepspeed_config_path deepspeed_config.json
--checkpoint_every_epoch
--resume_from_ckpt ckpt_dir/
--train_chain_data_cache_path chain_data_cache.json
--obsolete_pdbs_file_path obsolete.dat
and enable the bfloat16 flag in 'deepspeed_config.json'

OF training seems to have two different modes, which you've observed here. I don't think this has anything to do with precision, because other people using OF have gotten stuck in the lower mode while using bfloat16 and successfully converged with fp32. I suspect that if you fiddle with the seed you'll be able to induce the fp32 model into the higher mode too. I've never seen the lower mode in my personal training setup, so I don't think it's inevitable, but I have yet to isolate exactly what's causing it.
This is good data, though: I've only previously seen this phenomenon in runs also using the self-distillation set. In that case, the two modes seem to be at ~0.81 and ~0.35, rather than the ~0.7 and ~0.4 you're getting here.

OF training seems to have two different modes, which you've observed here. I don't think this has anything to do with precision, because other people using OF have gotten stuck in the lower mode while using bfloat16 and successfully converged with fp32. I suspect that if you fiddle with the seed you'll be able to induce the higher mode in the fp32 model too.
For what it's worth, runs that get stuck in the lower mode eventually undergo what I can only describe as a "phase transition" and rocket up to the accuracy of the normal runs. When that phase transition occurs seems to vary dramatically, as one might expect, and I've seen it happen anywhere from 7k global steps to about 20k (using a batch size of 120). It does occur very consistently, however: I've only seen a single run get permanently stuck on the lower lDDT-Ca plateau.
What you've shared here is good data. I've only previously seen this bimodal phenomenon in runs that also use the self-distillation set. In that case, the two modes seem to be at ~0.81 and ~0.35, rather than the ~0.7 and ~0.4 you're getting here. Granted, that discrepancy might also have to do with the fact that you're using a very small effective batch size of 8 (in the standard AF training setup it's ~120).
Unfortunately, I've never seen the lower mode in my personal training setup, so I don't think it's inevitable, but I have yet to isolate exactly what's causing it. If anyone has the insight/compute to figure out what's happening here, that would be very much appreciated.

Thanks for your reply, i will try to run the fp32 model again and check the result. The commit id for my previous training is 3fb643e92d6f80a468a8fd2a41a8808c369074c9. The random seed for fp32 and bfloat16 model is also same, the only difference is that the bfloat16["enabled"] flag set true for bf16 and false for fp32.


Protractor hangs indefinitely when running hundreds of tests which takes more than 6 hrs to execute

Protractor hangs indefinitely when running hundreds of tests which takes more than 6 hrs to execute. Sometimes(very rarely) we are seeing this behavior with jobs which takes 30 minutes to complete as well.
We have configured jenkins job to run around 1000 tests with shardTestFiles enabled and max instances set to 10. Job always gets stuck saying 1 or 2 instances of webdriver still running.
If we connect to remote windows machine running tests, we will see 2 or 3 nodejs processes running with 0% CPU. On killing these process job completes without generating Junit xml.
Hanging issue is being seen consistently for the all the jobs which run for more than 6hrs. Please suggest solution for this.
Using windows 2012R2 and windows 2016 server machines with protractor 4.0.14, nodejs 6.9.5 and firefox 41.0.2. Seeing same behavior with latest protractor 5.0.0 as well.
we have set below parameters in conf file,
1. jasmineNodeOpts: {
showColors: true,
defaultTimeoutInterval: 600000
}
2. allScriptsTimeout: 600000
3. ignoreUncaughtExceptions: true
4. capabilities: {
'browserName': 'firefox',
'version': 'ANY',
shardTestFiles: true,
maxInstances: 10,
}
5. browser.ignoreSynchronization: true
6. restartBrowserBetweenTests: true

Hi! This looks like a support question. Please ask your support questions on StackOverflow, Google Group discussion list, or Gitter. For more information please reference https://github.com/angular/protractor/blob/master/CONTRIBUTING.md#questions
Thank you!

We have a similar issue. Where did you ask this question? We'd be interested in the answer.

Please refer below links,
http://stackoverflow.com/questions/42172909/protractor-hangs-indefinitely-when-running-hundreds-of-tests-which-takes-more-th
https://groups.google.com/forum/?fromgroups#!topic/angular/cwsTKzIl3fA

Please refer below links,
http://stackoverflow.com/questions/42172909/protractor-hangs-indefinitely-when-running-hundreds-of-tests-which-takes-more-th
https://groups.google.com/forum/?fromgroups#!topic/angular/cwsTKzIl3fA


Combining with futures seems problematic

I have a difficulty in combining promises with futures.
Here is a minimal program which reproduces my issue:
import concurrent.futures
from promise import Promise
executor = concurrent.futures.ThreadPoolExecutor(max_workers=40000);

def combine(r,n):
  print "Completed promise_factorial({})={}*promise_factorial({})".format(n,n,n-1)
  return r*n

def promise_factorial(n):
  print "Inside promise_factorial({})".format(n)
  if n < 2 :
    return 1
  print "Schedulling promise_factorial({})".format(n-1)
  a = executor.submit(promise_factorial,n-1)
  print "Making a promise promise_factorial({})".format(n-1)
  return Promise.promisify(a).then(lambda r:  combine(r,n))

def done(r):
  print "Done all computations! Results is {}".format(r)

promise_factorial(10).then(lambda r: done(r))

When I run it with python concurrency_test.py it non-deterministically either fully succeeds, or fails silently like this:
$ python concurrency_test.py
Inside promise_factorial(10)
Schedulling promise_factorial(9)
Inside promise_factorial(9)
Schedulling promise_factorial(8)
 Making a promise promise_factorial(9)
Inside promise_factorial(8)
 Making a promise promise_factorial(8)
Schedulling promise_factorial(7)
$ echo $?
0

My machine has 64 cores.
I am not skilled in reasoning about concurrent processes and race conditions like that, but I suspect that there are some problems when the promise is not fulfilled before I return from the thread main function - am I right? If so: is there any way to block and wait till the promise is fulfilled before exiting a thread?

I was desperate enough to look into the source code and found undocumented methods wait and get and tried another approach in which I block the thread until the p.get() finishes:
import concurrent.futures
import threading
from promise import Promise

executor = concurrent.futures.ThreadPoolExecutor(max_workers=20)

def worker(foo,arg):
  try:
    return foo(arg).get()
  except Exception as ex:
    print ex;

def my_executor(foo,arg):
  try:
    return Promise.promisify(executor.submit(worker,foo,arg))
  except Exception as ex:
    print ex;

def combine(r,n):
  try:
    print("Completed promise_factorial({})={}*promise_factorial({}) inside thread {}".format(n,n,n-1,threading.current_thread().ident))
  except Exception as ex:
    print ex
  return r*n

def promise_factorial(n):
  print("Inside promise_factorial({})".format(n))
  if n < 2 :
    return Promise.resolve(1)

  return my_executor(promise_factorial,n-1).then(lambda r:  combine(r,n))

def done(r):
  print("Done all computations! Results is {}".format(r))

p = promise_factorial(30).then(lambda r: done(r))

unfortunatelly this approach seems to always end with a deadlock.

I was able to make some progress by ditching the idea of using futures / threadpools entirely and by using a more low level approach:
import threading
from promise import Promise
from Queue import Queue

def worker(foo,arg,resolve,reject):
  p = foo(arg);
  try:
    resolve(p.get())
  except Exception as ex:
    reject(ex)

def my_executor(foo,arg):
  def promiseConfig(resolve,reject):
    t = threading.Thread(target=worker,args=(foo,arg,resolve,reject))
    t.start();

  p = Promise(promiseConfig)
  return p

def combine(r,n):
  try:
    print("Completed promise_factorial({})={}*promise_factorial({}) inside thread {}".format(n,n,n-1,threading.current_thread().ident))
  except Exception as ex:
    print ex
  return r*n

def promise_factorial(n):
  print("Inside promise_factorial({})".format(n))
  if n < 2 :
    return Promise.resolve(1)

  return my_executor(promise_factorial,n-1).then(lambda r:  combine(r,n))

def done(r):
  print("Done all computations! Results is {}".format(r))

p = promise_factorial(30).then(lambda r: done(r))

this one always succeeds.

Thanks for the detailed examples, taking a look now.

I got your example working.
import time
import concurrent.futures
from promise import Promise
executor = concurrent.futures.ThreadPoolExecutor(max_workers=40000);

def combine(r,n):
    return r * n

def promise_factorial(n):
    time.sleep(.01)
    if n < 2:
        return 1
    a = executor.submit(promise_factorial, n - 1)
    return Promise.promisify(a).then(lambda r: combine(r, n))

def test_factorial():
    p = promise_factorial(10)
    assert p.get() == 3628800

Please let me know if works for you too, reopen the issue if not :)

If I understand correctly your example differs by two things:

added time.sleep(.01)
added p.get()
I can confirm that this example works.

I've tested that you can remove the time.sleep(.01) from it and it still works. The important part seems to be calling p.get() in the main thread. My understanding is that it prevents the main program from exiting before all the computations are done: which resulted in the truncated ouput I originally reported.


docs: Clean up README and config.toml

I noticed a few gotchas that might trip up newcomers to the project, so I tried to make things as clear as possible:

Changed the name of the theme in the installation instruction from themes/codex to themes/hugo-theme-codex to stay consistent
Be explicit as to where the exampleSite/config.toml file is located
The 1 mandatory line that needs to be addressed in exampleSite/config.toml has been moved to the very top

oh this looks good!


When can I get the chinese version or english version ?

Hi, I am a reader of your books, I have read DL from scrach 1st and 2nd edition, but I can not read japan laguage. I hope read this book as soon as possible. Your book help me a lot in deep learning, thank you very much!

also would like to get english version

I believe the translation to the Chinese version is currently underway.
There are no plans to translate the English version of the third book in this series.
However, you can read part of it in English for free as a trial version.
https://koki0702.github.io/dezero-book/en/step00.html

簡体字版
https://www.ituring.com.cn/search/result?q=斋藤康毅
https://www.ituring.com.cn/book/2863
繁体字版
http://books.gotop.com.tw/booklists.aspx?Types=v&Query=Deep+Learning
http://books.gotop.com.tw/v_A657

I believe the translation to the Chinese version is currently underway. There are no plans to translate the English version of the third book in this series. However, you can read part of it in English for free as a trial version. https://koki0702.github.io/dezero-book/en/step00.html
There is an English translation of the first book in this series: https://www.amazon.com/dp/B08ZNT3JXC/ref=cm_sw_r_tw_dp_MKDZ1KGE44YN3ZPFYDJF

Thank you for the links! I have already read the sample. It's a shame such a unique book is not being translated!

簡体字版 https://www.ituring.com.cn/search/result?q=斋藤康毅 https://www.ituring.com.cn/book/2863
繁体字版 http://books.gotop.com.tw/booklists.aspx?Types=v&Query=Deep+Learning http://books.gotop.com.tw/v_A657

Thanks, but the 3rd edition doesn't release the chines version yet. I cannot waiting for that.


ResolveEndpointV2 error when trying to connect to MSK via IRSA

Creating this issue referencing a bug originally reported in the main dapr repo: https://github.com/dapr/dapr/issues/8122
Issue seems to be a version mismatch in AWS modules
Expected Behavior
PubSub component for kafka (connecting to MSK using IRSA) should just work.
Actual Behavior
time="2024-09-18T17:09:53.885787767Z" level=fatal msg="Fatal error from runtime: process component my-msk-irsa-componen error: [INIT_COMPONENT_FAILURE]: initialization error occurred for my-msk-irsa-componen (pubsub.kafka/v1): [INIT_COMPONENT_FAILURE]: initialization error occurred for my-msk-irsa-componen (pubsub.kafka/v1): error validating iam credentials failed to load credentials: unable to assume role, arn:aws:iam::000000000000:role/my-dapr-role: not found, ResolveEndpointV2\nfailed to load declarative subscriptions: rpc error: code = Canceled desc = context canceled" app_id=my-dapr-app instance=my-dapr-app-7876c8ffb-5l8kx scope=dapr.runtime type=log ver=1.14.4
Steps to Reproduce the Problem
Most likely trying to access MSK using IRSA would result in a repro.
Release Note

RELEASE NOTE:
UPDATE github.com/aws/aws-sdk-go-v2/credentials [v1.17.0]
UPDATE github.com/aws/aws-sdk-go-v2/feature/rds/auth [v1.4.0]
UPDATE github.com/aws/aws-sdk-go-v2/config [v1.27.0]

/remove-lifecycle stale

/remove-lifecycle stale


Fix propagation of namespace labels to CEP labels

Currently (*namespaceUpdater).oldLabels is never updated with the namespace's labels after they have been synced to endpoints. This can e.g. lead to updates mistakenly being skipped. This in turn can lead to situations as described in https://github.com/cilium/cilium/issues/27626 where namespace derived labels are not removed from CEPs when the corresponding label is removed from the namespace.
Fix this by always updating (*namespaceUpdater).oldLabels on successful
endpoint label update.
Review by commit: The first two commits are preparatory cleanups. The third commit is the actual bug fix.
Fixes: #27626

/test

/test

Force pushed to fix a linter warning about unnecessary assignment to _.

/test


Issue with Pastebin

Hello I'm having issues uploading the loader.txt to pastebin!
the file is about 47mb big and because of that I get a 413 error when trying to upload it.
Did I do something wrong? I just opended the txt doc and copied all.
Please help

I don't  think that's you could even  use your own server


PSR-12 Hookup

Coverage remained the same at 99.364% when pulling 0366721e341a5e5d2504c35ab4e90ba0e488ca19 on c-harris:PSR12hookup into 9f13d4bfe1b8d5bd86fea0f55295da25bd2633a1 on Algo-Web:master.

Coverage remained the same at 99.364% when pulling 0366721e341a5e5d2504c35ab4e90ba0e488ca19 on c-harris:PSR12hookup into 9f13d4bfe1b8d5bd86fea0f55295da25bd2633a1 on Algo-Web:master.


Fixed content floating on mobile view.

Description
Content floating right side on mobile view for orders view page on admin panel.

@papnoisanjeev
Please resolve the conflicts.


Laravel signed URLs are getting corrupted in Mail view

Describe the bug
When you click on a button, like the one for email verification, you always get a 403 error - invalid signature. Seems like the "=" sign is getting dropped.
Versions
Ray version (you can see this in "About Ray"):  2.7.5
You can use composer show to get the version numbers of:

spatie/ray package version: 1.41.1
spatie/laravel-ray package version (if applicable): 1.36.1

PHP version: 8.3
Laravel version: 11.4
To Reproduce
Steps to reproduce the behavior:

Send default Fortify email verification message.
Click on Confirm button (or even on link in the footer).
403 - Invalid signature

Expected behavior
There should't be any error.
Desktop (please complete the following information):

OS: MacOS
Version: 14.4.1 (23E224)

I've tried to reproduce this using our demo app.
It contains a mailable with a link containing =
https://github.com/spatie/laravel-ray-demo-app/blob/6bb9f8d9e1c8758d3fbedfe354ab129d5a585003/resources/views/mails/test.blade.php#L6
You can send that mail to Ray using php artisan mail
When clicking the "View order" button in the mail, the correct link (https://spatie.be/?hey=yo&option=value) opens in the browser.
So, it seems to be working. Could you PR a link that does not work to our demo app?

Sure!
https://github.com/spatie/laravel-ray-demo-app/pull/3

I get this too, only w/ signed urls

This is fixed in the latest version.


Added transparent Get call when fetching latest version of flyte objects [task | launchplan | workflow]

Signed-off-by: Prafulla Mahindrakar<EMAIL_ADDRESS>TL;DR
Since the closure objects could be quiet heavy , We would want the list query in the admin to be light and not return the entire object with the closure but just the Identity object including the version.
Currently the task and launplan list API's include the entire object and would be good for consistency to now have them also return only identity objects and have the client query using GET call if he needs the full data for a paritcular object from the list.
In case of get latest version  in flytectl  [task | workflow | launchplan] , we now do the following

call the List api returning the identity objects
pick the top object from the list since default sort order is desc on created_at
do another get api with the version and project, domain, name

Type

[X] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[X] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
How did you fix the bug, make the feature etc. Link to any design docs etc
Tracking Issue
https://github.com/flyteorg/flyte/issues/1053
Follow-up issue
NA

Before making changes to admin to make it consistent across all flyte objects would be good to know if any clients like flytekit rely on the full object from the List call . cc : @katrogan

@pmahindrakar-oss do we need to make things consistent? for example, executions require a separate call to fetch their data (inputs & outputs) if a launch plan closure is lightweight enough to return inline i think we should do it and only depart from that model when closure data is large

@katrogan / @pmahindrakar-oss I do not follow the discussion? why do we need to make any changes to admin?

@kumare3/ @pmahindrakar-oss  I'm not sure either, I think we should leave admin as is and just have flytectl fetch the individual workflow in a Get call

@kumare3 @katrogan I have kept this flytectl PR to do a transparent get only for workflow --latest version.


add an entry for running Open-OCR on the Azure Kubernetes Service

Hi -
This adds an entry on running Open-OCR on the Azure Kubernetes Service - AKS.
Thanks,
dcasati

closed by mistake.

missed one file for this PR. I'll reopen this in a bit.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/96383

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/96613

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/102221

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/104625

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/111513


[WIP] Implemented user search

@pengwynn I have implemented the user search. Please have a look.

PTAL.
Also, I'm just curious as to why the service is initialized to a single URL. Won't that prevent the service from being reused? Also, why is it the responsibility of the user code to fill in the placeholders in the URL? Shouldn't it be parameters to the respective service calls (like UserSearch, CodeSearch, etc.)?

Also, I'm just curious as to why the service is initialized to a single URL. Won't that prevent the service from being reused?

@dhruvsinghal It's a tradeoff. By accepting URLs, the client promotes passing around Hypermedia link relations, like those we get from the API root.

Shouldn't it be parameters to the respective service calls (like UserSearch, CodeSearch, etc.)?

I think we've got the same params for all four search flavors: q, page, sort, and order. Those could be named parameters or a SearchParameters struct I suppose.

@dhruvsinghal This is looking good. I'm tempted to implement another search type on this same branch before merging, just to see how our pattern will emerge.
@jingweno: any feedback?

@pengwynn Sure, I'll implement another search, or if you want I can implement all the four searches on this branch itself.

@pengwynn PTAL. I've implemented issue search as well.

@pengwynn @jingweno, I propose the following restructuring of the SearchService Go API:

Given a Client object, obtain a SearchService object by calling Search()
Now, depending on the type of search (user, code, issues, or repositories) call the appropriate method e.g. UserSearch on the SearchService object.
The specific search object will take in the query, order and sort parameters (or nil if either of the latter two is not specified). This function will be responsible for expanding the URL that is defined at the top of this package.

Does thais sound reasonable?

In general it looks good except some minor issues. Cheers!

@jingweno Thanks for your comments!
@jingweno and @pengwynn PTAL.

:+1: :shipit:

@jingweno Should I merge this branch into master?

Gonna go ahead and merge this since it follows the same pattern as the other API methods.
@jingweno I'd like to explore how we can better support query params in methods like this. /cc https://github.com/octokit/go-octokit/issues/72

@pengwynn

I'd like to explore how we can better support query params in methods like this. /cc #72

Yeah, this is a miss in the current design. Let's chat more about it on #72.


Assignment 2

Assignment 2
PDF Version of documentation and screenshots:
Geo-Caching Assignment 2975e59489874c84b5117922ef89350a.pdf
Video Explanation:
https://drive.google.com/file/d/1MdVXl_apbt-Ky5X96HByfWFIuuzvKiqm/view?usp=sharing
GeoCoding and Reverse GeoCoding
Forward Geocoding
Forward geocoding is the process of converting human-readable addresses (like street addresses) into geographic coordinates (latitude and longitude). It helps in pinpointing locations on a map.

Forward Geocoding (JSON API):

http://localhost:8080/geocoding?address=${value}

Forward Geocoding (UI):

http://localhost:8080/geocodingUI?address=${value}

Reverse Geocoding
Reverse geocoding is the opposite process. It involves converting geographic coordinates (latitude and longitude) into a human-readable address format. This is useful for finding out the address of a given set of coordinates.

Reverse Geocoding (JSON API):

http://localhost:8080/reverse-geocoding?lat=${value}&lon=${value}

Reverse Geocoding (UI):

http://localhost:8080/reverse-geocodingUI?lat=${value}&lon=${value}

Replace ${value} with the appropriate values.
Both forward and reverse geocoding are commonly used in mapping applications, navigation systems, and location-based services.
This repository contains test cases for the GeoCoding service implemented in the com.caching.service package. These tests cover various scenarios to ensure the correctness and robustness of the GeoCoding functionality.
Test Cases
Negative Test Case for Reverse GeoCoding Endpoint
This test case checks the behavior of the reverse geocoding endpoint when provided with invalid latitude and longitude coordinates. The expected behavior is to receive a client error response (4xx). This test verifies that the endpoint handles invalid input gracefully.
Positive Test Case for GeoCoding Endpoint
This test case verifies the correctness of the forward geocoding endpoint by providing a valid address ("delhi") and comparing the received response with a pre-saved mock response. It ensures that the service correctly converts the address to geographic coordinates.
Positive Test Case for Reverse GeoCoding Endpoint
Similar to the forward geocoding test, this case validates the reverse geocoding endpoint by providing valid latitude and longitude coordinates and comparing the returned address with a pre-saved mock response.
GeoCoding Cache Hit Test with Endpoint
This test case verifies the caching mechanism of the forward geocoding endpoint. It makes two requests with the same address ("delhi"). The first request is expected to miss the cache, while the second request should hit the cache, indicating that the service correctly caches previously fetched results.
GeoCoding Cache Eviction Test
This test ensures that the caching mechanism evicts entries after a specified duration. It first populates the cache with an address ("goa"), waits for a specified delay, and then performs another request with a different address ("delhi"). The test verifies that the entry for "goa" is evicted from the cache while the entry for "delhi" remains.
Reverse GeoCoding Cache Hit Test with Endpoint
Similar to the forward geocoding cache hit test, this case verifies the caching mechanism of the reverse geocoding endpoint. It makes two requests with the same latitude and longitude coordinates. The second request is expected to hit the cache, indicating that the service correctly caches previously retrieved addresses.
Negative Test Case for GeoCoding Endpoint
This negative test case checks the behavior of the forward geocoding endpoint when provided with an invalid address. The expected behavior is to receive a client error response (4xx). This test ensures that the service handles invalid addresses appropriately.
GeoCoding Cache Miss Test
This test case verifies that the caching mechanism works by checking that the cache misses when a specific address is requested for the first time.
Notes

The tests have been modified to use the https://geocode.maps.co/ API instead of the provided API.
Although the API source has changed, the essence of the test cases remains the same. Only the logic has been modified according to the new API.
The use of Thread.sleep in the setup and teardown methods is to adhere to the API's rate limiting policy, which allows only one request per second.
External API requests are mocked to save time during testing. The responses used for comparison have been pre-saved for both forward and reverse geocoding.
The tests are designed to ensure the correctness, reliability, and efficiency of the GeoCoding service.


Know which twig files are called

Hello everyone,
We are using Sculpin at my company for our designers.
We would like to know if there is an easy way to know which twig files are called on the website (a little bit like the webprofilerbundle for symfony :-).

@dupuchba I'm not sure exactly what you are asking but I think the answer is "no." At least not using Sculpin directly? You could use some sort of javascript analytics thingy to track page hits possibly? Or read webserver logs? I don't think that is exactly what you are asking, though. Let me know if you can be more specific. :)

@simensen If I understand correctly, what he was asking is designers don't know which twig file was rendered on a certain page. He likes to know which twig file was used to render to get a particular page.
Eg : about.html => which twig files are used .

@harikt that's it, thank you. I was a bit tired yesterday :-) !
e.g : on a certain page, for example the homepage http:localhost:8000/ we want him to know easily which twig/html file has been called !

@simensen any idea ? :-)
Did you understand my problem ?

@dupuchba I think I better understand your problem (thanks to @harikt for helping to clarify!) but I don't know if I have an easy answer for you. I'd have to see how the web profiler is currently doing that and try to find a way to do it in Sculpin as well.  I don't know if/when we'll get that implemented, though. Would you be interested in taking a crack at it? I think it would be a great candidate for third-party extension.

@simensen I don't know, but I have a feeling it should work without much trouble for sculpin works with the http kernel.

@harikt Unfortunately we aren't really using HTTP Kernel in the usual way. It would be my preference to not have to use HTTP Kernel at all, to be honest. We are not using Symfony's core Templating component, for example.
It is possible it will work out of the box so if someone wants to try, that would be great. However, if it is being served up via a controller it isn't going to work with Sculpin for the foreseeable future. We do not execute controllers and there is nothing in Sculpin that even knows about routes.

@simensen I was exactly looking at webprofiler bundle. I will let you know what I can do about this one :-)

@simensen I started to work on it, it looks like the newly Profiler extension in twig does a pretty good job at profiling your twig file.
I am still working on it but I will need your advice for this usecase :

with the profiler I detect all the twig files that are used to render an html in dist
Now I need to generate for each of my sculpin's pages an html that contain all the (non tokenised/parsed/compiled) twig files :-)

Any idea how I can do it simply ?

Not at the moment, no. :-/ I'm not sure in what context the profiler works so I don't know how you'll know which "page" you are on. I haven't used the Profiler extension at all yet.
So you are getting data but not sure what to do with it, right?

@simensen I didn't not have the time to work on it as I changed company ^_^. Thanks for you help though, it was really usefull


update broken gitlab yaml for cgo targets on alpine

Update broken alpine image in CI

Tested ACK:
https://gitlab.com/mdr0id/lightwalletd/-/jobs/295720103


FR: A new YAML timestamp type called "Date Updated" which acts like the to-be-deprecated "Date Modified" timestamp

@pjkaufman Hi, I saw the pull request #245 is going to change how metadata Date Modified would function:

Date modified is updated if file changed time is more than 5 seconds away from the value in the yaml.

If my understanding is correct, it means Date Modified could update automatically. That's a nice feature which I would definitely use, but I still hope to keep the deprecated way to update Date Modified manually. The reason is that I use Date Modified to track version update date and I don't treat typo correction as an "update". For now this could be done by closing note without pressing Ctrl+S after correcting typo, but it would be hard to do so if Date Modified could update automatically.
Therefore it would be nice to add a new "Date Updated" YAML timestamp that allows users refresh its value manually.
Or maybe, just rename the old Date Modified option to Date Updated and add a new option called Date Modified. Not sure if this makes any difference, might affect the new feature "updated on format change"?
BTW I'm not sure if this is the best name, Date Revised or Date Reviewed may be better.

Hey @XDcedar , the Date Modified rule will not be automatically updated without the user manually triggering the lint rule. So it will work the same with a coupke of changes. That 5 second difference is used during a manually triggered lint to see if the last time the file was listed as modified is greater than 5 seconds ago. It means that linting in quick sucession will not update date modified unless the date modified metadata for the file is more than a 5 second difference from the value at the top of the file in the YAML.
Does that make sense?

Oh, great, so it's a debounce feature, not a auto-update feature. That makes sense. I'm sorry I misunderstood your pull request. I'll close the issue. Thanks a lot!


Gobuster not working with connection reset

I am auditing a network equipment with an ugly web server which reset connection instead of returning a 404 Not found when probing for a non existing resource.
Gobuster does not seems to handle such case and fails :
Error: error on running gobuster: Get http://<IP_ADDRESS>/5c3677c0-56e6-465a-bc9c-1554464e6c78: EOF
Can the gobuster architecture easily handle this case ?

sadly not. We can only detect the connection request but not why it happened. If we would treat a EOF as 404 this would cause a lot false positives when there is a real connection reset


⚠ Jenkins Plugins Artifactory has degraded performance

In 9c1ee33, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1640 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 6ff9ab3 after 14 minutes.


linalg::norm not working (does not compile) for std::complex<float>

The linalg::norm(...) function does not build with with std::complex<float>. It does work with std::complex<double>,
To repro, add the following test:
TEST(xblas, normCplxFloat) {
  xt::xarray<std::complex<float>> a = {std::complex<float>({1., 2.}), std::complex<float>({3., 4.})};
  auto res = linalg::norm(a);

  EXPECT_NEAR(res.real(), 5.4772, 1e-3);
  EXPECT_NEAR(res.imag(), 0.0, 1e-3);
}

with double instead of the float it does build (and pass). This is similar to #128, but I think that one was fixed.

Thank you for the report. Looking into it!


enhancewhen drop temp partition, not trigger materialized view refresh

when drop temp partition, not trigger materialized view refresh

run buildall


Update apache-client, kinesis, sqs to 2.25.6

About this PR
📦 Updates

software.amazon.awssdk:apache-client
software.amazon.awssdk:kinesis
software.amazon.awssdk:sqs

from 2.23.21 to 2.25.6
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #828.


Set the creation time of an item

I want to use this library to import from a different format to KeePass. I'd like to keep the creation times. Being new to Rust, I am not sure if this is my mistake, but I can't seem to figure out how to set the creation date:
error[E0603]: module `types` is private
  --> src/main.rs:15:5
   |
15 | use kpdb::types::times::Times;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^

and
error[E0599]: no method named `set_creation_time` found for type `kpdb::Entry` in the current scope
  --> src/main.rs:55:15
   |
55 |         entry.set_creation_time(utc);
   |               ^^^^^^^^^^^^^^^^^
   |
   = help: items from traits can only be used if the trait is in scope
help: the following trait is implemented but not in scope, perhaps add a `use` for it:
   |
9  | use kpdb::types::times::Times;
   |

Any suggestions?

Hi @miracle2k,
Like explained in the commit message of d2e1344 I forgot to export the Times trait. I just pushed version 0.4.0, that fixes this problem, to crates.io.

That works great, thanks!


feat: complete schema manager in its own directory

Automatically bootstraps schema from file structure:

|-- lib
     |-- models
        |-- {dbName}-db
            |-- {collectionName}-schema.ts

User can override/customize default lib/models path by passing --schemaroot="my/custom/path"

suffixes -db and -schema.ts are required to mark these as DB/Collection files

The schema file can only contain one schema, similar to lib/models/catalog-db/products-schema.ts

Vercel deploy failing because Tigris env is not yet configured, as soon as it is configured. It will create a generic catalog named DB in shared Tigris showcase account, just want to make sure it is ok (and won't get overriden) 😝

Sample

What about this directory structure?
|-- models
    |-- {dbName}
        |-- {collectionName}.ts

i.e. models as a top-level directory, dbname is a directory inside models, and then collection name is the file with the model.

What about this directory structure?
|-- models
    |-- {dbName}
        |-- {collectionName}.ts

i.e. models as a top-level directory, dbname is a directory inside models, and then collection name is the file with the model.

I have seen this pattern of declaring models inside \lib in next 13 official example, vercel mongo starter. But there are examples that define a top level directory, I'll change it to ./models.
On the directory names as {dbName} and {collectionName}.ts. It is possible that a user has non-database directories inside models, we do want to avoid creating those databases and unnecessary scanning the files to lookup Schema. For example:
models/utils/converter.ts, models/some-frontend-model.js. Ideally they shouldn't have but there is no restrcition, hence using those marker suffixes. Also, next.js creates routes for everything inside /app unless it is marked as [name] or (name). Similarly, we are marking files using -db, -schema.ts suffix. But I am open to opinions here as well.

What about this directory structure?
|-- models
    |-- {dbName}
        |-- {collectionName}.ts

i.e. models as a top-level directory, dbname is a directory inside models, and then collection name is the file with the model.

I have seen this pattern of declaring models inside \lib in next 13 official example, vercel mongo starter. But there are examples that define a top level directory, I'll change it to ./models.
On the directory names as {dbName} and {collectionName}.ts. It is possible that a user has non-database directories inside models, we do want to avoid creating those databases and unnecessary scanning the files to lookup Schema. For example: models/utils/converter.ts, models/some-frontend-model.js. Ideally they shouldn't have but there is no restrcition, hence using those marker suffixes. Also, next.js creates routes for everything inside /app unless it is marked as [name] or (name). Similarly, we are marking files using -db, -schema.ts suffix. But I am open to opinions here as well.

Good point, Ovais's suggestion looks good by adding /tigris inside models, that will solve it.

Moved to #2


Running turtle feature

Description
A short summary of what is included in your Pull Request.
Fixes #(issue_no)

[ ] Issue_no: <insert your issue no here>
[ ] Not applicable

Type of change
Choosing one or more options from the following as per the nature of your Pull request.

[ ] New project insert
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Documentation Update

Project

Your Project Name:

Short Description: Provide a short desctiption of your Python project

Checklist:
Please tick all the boxes that are fulfilled by your Pull Request.

[x] I have named my files and folder, according to this project's guidelines.
[x] My code follows the style guidelines of this project.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have created a helpful and easy to understand README.md, according to the given README_TEMPLATE.
[x] My changes do not produce any warnings.

I added the Running Turtle Game python folder with a python file and readme file depending on the rules

please do not alter the master README.md


[DRAFT] Adding methods now for (conditional) mutual information

Signed-off-by: Adam Li<EMAIL_ADDRESS>Fixes #17
Changes proposed in this pull request:

Add functions to estimate entropy, which will be useful for augmenting the CI submodule

TODO:

Add working tests for entropy estimation

Before submitting

[ ] I've read and followed all steps in the Making a pull request
section of the CONTRIBUTING docs.
[ ] I've updated or added any relevant docstrings following the syntax described in the
Writing docstrings section of the CONTRIBUTING docs.
[ ] If this PR fixes a bug, I've added a test that will fail without my fix.
[ ] If this PR adds a new feature, I've added tests that sufficiently cover my new functionality.

After submitting

[ ] All GitHub Actions jobs for my pull request have passed.

Closing because we will migrate these kinds of tests into pywhy-stats.


SNMP table individual metrics do not preserve defined metadata.

For example, you poll a device which has this defined in configuration:
    user_tags:
        env: stg

When you look at the data in NewRelic, this (and other metadata) is available for simple SNMP counters, for example kentik.snmp.Uptime
However, any counters which are part of the SNMP table do not have this attributes, for example kentik.snmp.ipIfStatsHCInOctets - only carry device_name as usable metadata.
This creates issues when designing custom dashboards which try to filter on tags instead of individual host names.
Required behavior - any SNMP counter visible in NewRelic should have full set of metadata available.

What version of ktranslate are you running? This should have been fixed as of Nov 10 build.

I was using image tagged latest but it was downloaded before Nov 10th.
I pulled latest image and I now see metadata sent with SNMP tables.
Although there was another breaking change - tags are now "tags.<tag_name>" instead of just "<tag_name>" good, but need to fix few custom dashboard...

Great. tags.<tag_name> is something NR asked for.


Unable to filter user lists

For the last few days I have been unable to filter neither the user list, or the user dropdown from the identity overrides section
On the user list, it will type in 1 character, but then this gets cleared before I can type the next character
I can see a request going out
https://api.flagsmith.com/api/v1/environments/gpjCB9cLrFxKj26vcKVh9S/identities/?q=t&page_size=10
but as I type more it still sends the same request without the full filter string

Reproduced in production.

https://github.com/Flagsmith/flagsmith/pull/226


Image license

Hi, I'm not so interested in the theme, but I am interested in the background image you ship with the theme.
Do you own the copyright? Could I use it on its own? Is it a stock photo which I can purchase somewhere?
Thanks!

I've found the original on http://deathtothestockphoto.com/. Sorry for the noise.


Browser Sync not working

I love this, just one question, I have set it up, and modified the path to my localhost, and my SASS path. It creates the proper css file, but does not auto reload the browser. Thanks for this cool software.

Glad you liked it. I'll need much more info then this. You have to use the bug report template template of issue and answer all questions.
What did you do, what changes you made, etc. What tools you used.

Closing it, kindly file with the bug template.


Add additional tests for ReadCsv

Additional tests for #2713.

I just saw this PR. Tagging @eerhardt and myself as reviewers.


Make exported headers C++14 (or at least C++17)-friendly across compilers

Right now C++20 has to be used under MSVC because of some struct initialization patterns that aren't all that important. Ideally you should be able to build the artifacts as C++17 and include them in a C++14 build, or at least a C++17 build. Would require breaking up bitstream.hh at least.

Should be C++17-friendly with ec5059d2785dc47201a2c75edff431052d36f699, still working on C++14. Outside of Clang, use of if constexpr without warnings requires flipping from C++14 to C++17. To support C++14 consumers we need to use std::enable_if patterns instead.

The SFINAE versions I was playing with were horrible. Everything works fine in gnu++14, if constexpr only warns under c++14. Just disable that warning where appropriate.


[Release-1.28] - Incorrect warning message for expiring K3s CA certificates

Backport fix for Incorrect warning message for expiring K3s CA certificates

#10270

Reproduced using VERSION=v1.28.10+k3s1
Validated using COMMIT=7de7adb2e40ab18deb1fc30950e688f162c6dee3
$ sudo mkdir -p /var/lib/rancher/k3s/server/tls/etcd;
$ sudo openssl genrsa -out /var/lib/rancher/k3s/server/tls/root-ca.key 4096;
$ sudo openssl req -x509 -new -nodes -sha256 -days 360 -subj "/CN=k3s-root-ca@test" -key /var/lib/rancher/k3s/server/tls/root-ca.key -out /var/lib/rancher/k3s/server/tls/root-ca.pem;
$ curl -sL https://github.com/k3s-io/k3s/raw/master/contrib/util/generate-custom-ca-certs.sh | sudo bash -;
$ COMMIT=7de7adb2e40ab18deb1fc30950e688f162c6dee3
$ sudo INSTALL_K3S_COMMIT=$COMMIT INSTALL_K3S_EXEC=server ./install-k3s.sh

Results before fix in place showing 90 days expiry against a 365 day valid certificate
$ kg events --field-selector involvedObject.kind==Node
LAST SEEN   TYPE      REASON                           OBJECT                  MESSAGE
9m17s       Warning   CACertificateExpirationWarning   node/ip-ip   Certificate authority certificates require attention - check k3s documentation and begin planning rotation: certificate-authority/server-ca.crt: certificate CN=k3s-root-ca@test will expire within 90 days at 2025-05-30T18:59:06Z, certificate-authority/client-ca.crt: certificate CN=k3s-root-ca@test will expire within 90 days at 2025-05-30T18:59:06Z, certificate-authority/request-header-ca.crt: certificate CN=k3s-root-ca@test will expire within 90 days at 2025-05-30T18:59:06Z, certificate-authority/peer-ca.crt: certificate CN=k3s-root-ca@test will expire within 90 days at 2025-05-30T18:59:06Z, certificate-authority/server-ca.crt: certificate CN=k3s-root-ca@test will expire within 90 days at 2025-05-30T18:59:06Z

Attention to the correct days now being printed for the pre-baked certificates
$ kg events --field-selector involvedObject.kind==Node
LAST SEEN   TYPE      REASON                           OBJECT                  MESSAGE
90s         Warning   CACertificateExpirationWarning   node/ip-ip   Certificate authority certificates require attention - check k3s documentation and begin planning rotation: certificate-authority/server-ca.crt: certificate CN=k3s-root-ca@test will expire within 365 days at 2025-05-30T22:26:47Z, certificate-authority/client-ca.crt: certificate CN=k3s-root-ca@test will expire within 365 days at 2025-05-30T22:26:47Z, certificate-authority/request-header-ca.crt: certificate CN=k3s-root-ca@test will expire within 365 days at 2025-05-30T22:26:47Z, certificate-authority/peer-ca.crt: certificate CN=k3s-root-ca@test will expire within 365 days at 2025-05-30T22:26:47Z, certificate-authority/server-ca.crt: certificate CN=k3s-root-ca@test will expire within 365 days at 2025-05-30T22:26:47Z


nginx: Flag to build with debugging and parallel builds

In order to use nginx's `debug log level, such as
https://docs.nginx.com/nginx/admin-guide/monitoring/debugging/

as described on
	https://docs.nginx.com/nginx/admin-guide/monitoring/debugging/

nginx needs to be compiled with --with-debug.
As mentioned there, upstream "nginx PLUS" packages bring two different nginx
binaries (nginx and nginx-debug); for nixpkgs we at least want to at least
add a convenient flag to enable it.

A second commit enables parallel building.

CC @globin @fpletz


start recording keypresses earlier

I often do "ctrl+R "
but now I have to wait for hishstory to load before I can type
so either make it load faster (and maybe not show all history)
or capture types characters earlier and then pass them to hishtory
ctrl+r foobar
Search Query: > bar

Just to confirm, what version of hishtory are you using (you can check from hishtory status)? Hishtory's control-r got a lost faster in 94722941cfab4f79ba71e98c2ff9349e259859dd so I'm wondering if you have a recent enough version to include that commit.
Regardless, leaving this issue open since this does seem like a good further optimization.

I installed latest via brew on nov 27th so that commit would have been in there afaik

👍  If you go ahead and upgrade (via hishtory update) you'll get the latest version which should be significantly faster. Please reopen this if you are still experiencing any latency issues!

it's better now, but if you can start listening to stdin even earlier that would be great :)


feat: updates for new location of application.env in ubi-init docker containers

Description
This pull request changes the following:

updates for new location of application.env in ubi-init docker containers

Related Issues

Required by #https://github.com/hashgraph/solo/issues/110

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 67.17%. Comparing base (1ed70bb) to head (87e09da).

Additional details and impacted files

@@            Coverage Diff            @@
##               main     #797   +/-   ##
=========================================
  Coverage     67.17%   67.17%
  Complexity      339      339
=========================================
  Files            64       64
  Lines          1319     1319
  Branches        157      157
=========================================
  Hits            886      886
  Misses          370      370
  Partials         63       63

:tada: This PR is included in version 0.25.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix parsing of arguments in constant expressions

Fixes #8006
Also, remove some somewhat-dead code left after #8217.
Test script which now works:
const a = deg2rad(90.0) # 1.57..
const b = sin(a) # 1
const c = sin(1.57) + cos(1.57) # 1.0..
const d = sin(deg2rad(90.0)) # 1
const e = 32 # 32
const f = pow(2, e) # 2^32
const g = 3.14 # 3.14
const h = sin(1.57) + cos(g) # 0.0...
const i = -1 # -1
const j = sin(1.57) + i # 0.0...
const k = Vector2(i, j) # -1, 0.0...

Thanks!