fix fix memory leak for insert transaction

Proposed changes
Issue Number: close #xxx
Problem summary
cherry-pick from: #17512
void CsvReader::_split_line_for_proto_format(const Slice& line) {
    PDataRow** ptr = reinterpret_cast<PDataRow**>(line.data);
    PDataRow* row = *ptr;
    for (const PDataColumn& col : (row)->col()) {
        int len = col.value().size();
        uint8_t* buf = new uint8_t[len];
        memcpy(buf, col.value().c_str(), len);
        _split_values.emplace_back(buf, len);
    }
    delete row;
    delete[] ptr;
}

  void PInternalServiceImpl::send_data(google::protobuf::RpcController* controller,
                                       const PSendDataRequest* request, PSendDataResult* response,
                                       google::protobuf::Closure* done) {
      bool ret = _heavy_work_pool.try_offer([this, request, response, done]() {
          brpc::ClosureGuard closure_guard(done);
          TUniqueId load_id;
           load_id.hi = request->load_id().hi();
           load_id.lo = request->load_id().lo();
          // On 1.2.3 we add load id to send data request and using load id to get pipe
          auto stream_load_ctx = _exec_env->new_load_stream_mgr()->get(load_id);
          if (stream_load_ctx == nullptr) {
              response->mutable_status()->set_status_code(1);
              response->mutable_status()->add_error_msgs("could not find stream load context");
          } else {
              auto pipe = stream_load_ctx->pipe;
              for (int i = 0; i < request->data_size(); ++i) {
                  PDataRow* row = new PDataRow();
                  row->CopyFrom(request->data(i));
                  pipe->append_and_flush(reinterpret_cast<char*>(&row), sizeof(row),
                                         sizeof(row) + row->ByteSizeLong());
              }
              response->mutable_status()->set_status_code(0);
          }
      });
      if (!ret) {
          LOG(WARNING) << "fail to offer request to the work pool";
          brpc::ClosureGuard closure_guard(done);
          response->mutable_status()->set_status_code(TStatusCode::CANCELLED);
          response->mutable_status()->add_error_msgs("fail to offer request to the work pool");
      }
  }

There are two problems when using begin, insert into, and commit operations.

The memory of buf(uint8_t* buf = new uint8_t[len]) in _split_line_for_proto_format function didn't be released when clear _split_values.
The memory of PDataRow may leak when the load fails.   The memory of row(PDataRow* row = new PDataRow()) in the send_data function can't be released when some error occurs.

Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


chore: test bundler module resolution

This is a 'canary' pull request. It aims to ensure that the ecosystem is ready for a shift in the default Nuxt TypeScript module resolution from 'Legacy' to 'Bundler': https://github.com/nuxt/nuxt/pull/24837. You'll need to run your build + type checking tests to verify that things still work; I'm hoping that CI will do that for us so we get an immediate indication of whether there's anything to investigate further here.
'Bundler' module resolution is recommended by Vue and by Vite, but unfortunately there are still many packages that do not have the correct entries in their package.json.
This might include this module or packages that are used by this module. You can see, for example: https://arethetypeswrong.github.io/?p=@sidebase/nuxt-pdf. The initial red X for node10 needs to be fixed in https://github.com/nuxt/module-builder; you can ignore that for now.
If there are any errors reported in CI for this PR, it would be good to fix them for the sake of any users of this module who enable the Bundler module resolution. Feel free to ping me or others on the Nuxt Discord if you need any help resolving any issues discovered by this PR - and feel free to check out https://github.com/nuxt/nuxt/pull/24837 for any feedback or comments from others affected.
Checklist:

[ ] issue number linked above after pound (#)

replace "Closes " with "Contributes to" or other if this PR does not close the issue

[ ] manually checked my feature / checking not applicable
[ ] wrote tests / testing not applicable
[ ] attached screenshots / screenshot not applicable

Added in  #26 and will merge via that PR. Thanks! ❤


Release/v0.6.0

This release includes a number of improvements to the overall developer experience and testability of the code base.
Acceptance Tests Improvements
Tests Converted to Standard CucumberJS & Chai
The previous version had a custom testing framework to support abstracting repetitive inputs, answer mocks, and assertions. The tests now run BDD style acceptance tests using the CucumberJS framework with chai supporting assertions.
The tests still leverage the mocks delivered with azure-pipelines-task-lib to mock inputs and answers.
E2E Debug Support for Acceptance Tests / No Child Process Spawn
The azure-pipelines-task-lib traditionally executes the task within a child process to perform unit testing. In this version however, the task is now run within the same process as the test which has the following primary benefits.

The task can be debugged when running unit tests
Environment variables set by the task can be inspected and asserted.

Loose Coupling to azure-pipelines-task-lib
The task is now only dependent on the task lib in only a few key areas. This allows for easier execution of the entire task code base without requiring sophisticated mocking

ITaskContext -> AzureTaskContext. Used to resolve task inputs. (use MockTaskContext for tests)
ITaskAgent -> AzureTaskAgent. Used to invoke ADO REST API operations. (use MockTaskAgent for tests)
IToolFactory > AzureToolFactory. Used to resolve executables/binaries on the agent. (use MockToolFactory for tests).

Developer Experience Improvements
The code-base has been more deeply integrated into VSCode's task and launch configurations. Several tasks have been setup to make the essential dev tasks faster to run.

build - tasks/terraform-cli - compile terraform cli source
test - tasks/terraform-cli - run all acceptance tests for terraform cli
test scenario - tasks/terraform-cli - run single or subset of acceptance tests for terraform cli
start - tasks/terraform-cli - execute the task (uses .env file for task configuration)

F5 Debug for both Acceptance Tests and Running Task (The F5 Contract)

debug - tasks/terraform-cli - start and debug terraform cli (uses .env file for task configuration)
debug:test - tasks/terraform-cli - start and debug a single or subset of acceptance tests. Debugger will step through both the tests and task code (before couldnt attach to task code while debugging tests)
debug:tests - tasks/terraform-cli - start and debug all acceptance tests

Standard HotKey Integration
CTRL+SHIFT+B - runs build - tasks/terraform-cli
CTRL+R,T - runs acceptance test tasks
CI/CD Improvements
YAML-Based Multi-Stage Pipelines
The ci/cd pipeline previously was built using the classic UI editor for Azure DevOps Builds and Releases. This restricted contributors ability to modify and test changes to the pipeline. This also provides examples of how to use the tasks via the test stage of the pipeline.
Improved CI Execution Time
Jobs are now executed in parallel where possible which has cut the CI time from ~10 minutes to ~3 minutes.
New E2E Test Scenarios Added to Pipeline
The test stage provides parameter where contributes can inject new yaml definitions that perform e2e testing against the task. The pipeline will iterate through each scenario provided. All these scenarios must pass for new versions to be published to marketplace.
Overview Includes Sample YAML Configurations
Several yaml code samples have been added to show how the features can be used from yaml-based multi-stage pipelines.

Sorry man, just got to this, looks good of course :) and well, you're the boss here :)

Sorry man, just got to this, looks good of course :) and well, you're the boss here :)

Thanks for taking the time to review @favoretti. Just wanted to get this finished up while I have time to do it. If you or @alex-goncharov see anything later, feel free to reach out!
Planning on publishing this today. Just working through some issues on the new pipeline that only run during tagged releases then should have it published.

Sorry man, just got to this, looks good of course :) and well, you're the boss here :)

Thanks for taking the time to review @favoretti. Just wanted to get this finished up while I have time to do it. If you or @alex-goncharov see anything later, feel free to reach out!
Planning on publishing this today. Just working through some issues on the new pipeline that only run during tagged releases then should have it published.

wow, this is quite a change!
Looks good too.

wow, this is quite a change!
Looks good too.


Add rule for missing process block when command supports the pipeline

PR Summary
This PR adds a rule to warn when a function has at least one parameter that supports the pipeline but doesn't implement a process block. This feature is detailed in issue #1368.
I still need to add tests and docs, but wanted to get this out there to take any feedback on overall approach or general details such as rule naming, messages, etc.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[ ] Make sure all .cs, .ps1 and .psm1 files have the correct copyright header
[x] Make sure you've added a new test if existing tests do not effectively test the code changed and/or updated documentation
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

Awesome, let me know if you need help with writing the test. Is the code for the rule already working and ready for review? In case you encounter issues with the build we are there for you as well, the first goal would be to have at least 1 of the 4 build environments green, I'm happy to help getting the edge cases for other environments right as I've got a bit of experience in it already.
In the meantime, I've re-targeted the PR to the master branch as the development branch is just there for legacy purposes

Awesome, let me know if you need help with writing the test. Is the code for the rule already working and ready for review? In case you encounter issues with the build we are there for you as well, the first goal would be to have at least 1 of the 4 build environments green, I'm happy to help getting the edge cases for other environments right as I've got a bit of experience in it already.
In the meantime, I've re-targeted the PR to the master branch as the development branch is just there for legacy purposes

@bergmeister yes the code appears to be working as-is - I just didn’t get a chance to write tests yet. I’ll take a look later today to see if there are any compatibility quirks that trip me up, but I think this one is pretty straight-forward. Thanks!

Because you added strings to the .resx files of the rules project the strongly typed classes file needed to be updated to fix the build, I've just pushed a change for that. If you need to change those resource strings again, you can automatically get them re-created by running .\New-StronglyTypedCsFileForResx.ps1 Rules

Because you added strings to the .resx files of the rules project the strongly typed classes file needed to be updated to fix the build, I've just pushed a change for that. If you need to change those resource strings again, you can automatically get them re-created by running .\New-StronglyTypedCsFileForResx.ps1 Rules

@bergmeister thanks for all your input on this! I'm refactoring based on your style suggestions, but after your change in 1ad72e7 I'm getting the error:
Invoke-ScriptAnalyzer : Could not find any resources appropriate for the specified culture or the neutral culture.
Make sure "Microsoft.Windows.PowerShell.ScriptAnalyzer.BuiltinRules.Strings.resources" was correctly embedded or
linked into assembly "Microsoft.Windows.PowerShell.ScriptAnalyzer.BuiltinRules" at compile time, or that all the
satellite assemblies required are loadable and fully signed.

I'm sure I'm missing somethings, but don't see exactly what it is.

Ok, sorry for that, I pushed another commit where I used Visual Studio for the auto-generation, maybe the script doesn't work any more. In the long term view we plan to move to .Net Core 3, which would handle that for us.

I also noticed you had a big diff on the whole resx file, so I reverted the change and re-added your entries for a clean diff. Out of interest, which editor are you using?

I also noticed you had a big diff on the whole resx file, so I reverted the change and re-added your entries for a clean diff in that file. Out of interest, which editor are you using?

using visual studio 2019 - think that was a line endings or encoding issue?

I think this is ready to merge now. Let me know what you think about the refactor, tests and the help doc. Again, thanks for your help with this - I'm new to the project so getting started was a bit of a hurdle.

Ok, I think that’s all set now. My test are passing, but I’m still seeing several test failures. One test appears to be counting rules, so naturally that failed. 12 others seem to have returned a null reference exception. Not sure about that yet. I’ll leave this be for today and look at it again tomorrow.

@bergmeister Well I think I got most of the tests working, but now there is one failing in the Helper tests:
Expected the actual value to be less than or equal to 11, because Number of Runspaces should not exceed size of runspace pool cache (10) plus the the default runspace pool (1) in CommandInfoCache, but got 14.

at <ScriptBlock>, C:\projects\psscriptanalyzer\Tests\Engine\Helper.tests.ps1: line 33
33:             (Get-Runspace).Count | Should -BeLessOrEqual 11 -Because 'Number of Runspaces should not exceed size of runspace pool cache (10) plus the the default runspace pool (1) in CommandInfoCache'

I'm not sure I can troubleshoot that one, otherwise I think this is ready. Thanks!

That sounds great. You can ignore that one test about runspaces, it is a known, new flaky test, for which we already have a fix in another PR. Thanks so far, I'll try to review the recent changes in the next days

Awesome work, looks good. I only added a couple of minor code style enhancement suggestions that you can apply but otherwise the code looks really good.

Thanks! Just sorry it took so many changes to get up to snuff!

The only last thing that came to my mind is that maybe UseProcessBlockForPipelineCommand might be a better name than UseProcessBlockForPipelineCommands, similar to the PowerShell design rule to use single nouns and user's will get a warning for a single command at a time and not commands. I do realize though that some of the other existing rules use a pluralized noun, therefore PSScriptAnalyzer rules already use a mix of styles where it wouldn't matter too much. I'leave that up to your judgement what you think/prefer, especially, since renaming the rule would also require a fair bit of work like renaming the files, etc.

That's fine - I'm always up for any improvements you can suggest. I'm making one more commit with your suggestions and the rule name change so hopefully this is all good now. Find and replace should do the trick!

P.S. VS 2019 is fine, I use it as well and never had issues editing the resx (just remember to press the save all button so that it updates the *.designer.cs file), not sure if it was an encoding issue but at least it's resolved now :-)

Yeah, not sure what happened there. Anyway, since I renamed the command I also modified the strings.resx. This seemed fine and the designer file was updated as well. After I pushed my changes it looks like the entire resx file was diffed, rather than just the changes. That didn't appear to be the case locally prior to pushing. Thoughts?

@bergmeister Should I be worried that the rule doesn't highlight the parameter in VSCode:

I removed any installations I had of the module and copied the built module into my module path. It appears to be highlighting the existing variable rule, but not mine. The rule does trip on Invoke-ScriptAnalyzer though.

In VS-Code not all rules are turned on by default, you can do that either by pointing it to a PSSA settings file or for your purposes just use the PowerShell: Select ScriptAnalyzer Rules command, which can enable other rules (but the choice of settings does not persist, i.e. goes back to the default after you close VS-Code)

I made the diff clean again, but I cannot see a difference in encoding or newlines, maybe you have a non-standard VS or git setting. Getting the diff clean is important here because otherwise other people would get an immediate merge conflict in their existing PRs that is not even easy to resolve.

I made the diff clean again, but I cannot see a difference in encoding or newlines, maybe you have a non-standard VS or git setting. Getting the diff clean is important here because otherwise other people would get an immediate merge conflict in their existing PRs that is not even easy to resolve.

Yeah, not sure what's going on there, but it must be git because it looked fine until I pushed!

@rjmholt @bergmeister just checking in to see if there is anything else you need from me on this PR? Thanks!

From my side it is a yes. If Rob is happy as well with the recent changes that he requested, then I'd merge it.

LGTM!


Run Category Scenario Models in stages

Add a run parameter to stop after N stages are complete, or to run a base model but not its scenarios, or stop after N scenarios.
Double-check the "continue" operation to ensure that missing stages are restarted even if not at the end of the scenarios.
If categories are changed, should it invalidate all scenarios?

Some sub-issues to approach here:

"continue" should scan all stages in order and pick up with the first that did not complete successfully, or that is missing. All subsequent stages should be "reset"
Add parameter to run up to stage N, starting from the first incomplete stage. (N can be a number/numeric position, a string that can be either a stage name of some later incomplete stage, or a "+N" that will continue from the first incomplete stage and process N more stages).
Could apply N to just the category scenarios.

Workaround (using "limit" parameter on model$run, along with named stage start).


Fixed when not working without plugin reload

premiumType can be null, checking for premiumType in change listener

For some reason Discord sets premiumType multiple times but plugin does it only once (because user.id == lastUserId, but user.premiumType changed by Discord)
https://user-images.githubusercontent.com/62172116/215272635-ed4e1768-fff3-43e8-b6ba-e8eb0da7b079.mp4


Docs: add a page with a list of key features

It would be helpful for newcomers to describe Mull key features in a documentation.

Thank you @ligurio, I like the list. I have an impression that the testing framework support is a bit misleading (i.e. Mull supports any framework, though there are nice features when we know specifics of a test framework), but I'll write a separate tech note to clarify what a testing framework support means :)


Support --include_source_info in native proto_library

It's useful to be able to specify an optional inclusion of source_code_info in the proto descriptors generated by proto_library, for the purpose of documentation generation tools etc. I was working on an aspect that used the proto_library output descriptors, and this is stripped away. It's useful to strip by default, but it would be also good to have a param to native.proto_library that allows us to specify targets that provide the source code info.

Duplicating into bazelbuild/bazel#9337
TL;DR: Bazel introduced --experimental_proto_descriptor_sets_include_source_info which passes --include_source_info when compiling the descriptor set of proto_library targets. It may become the default in the future.


FixCursorHold is no longer needed with Neovim v0.8.0.

https://github.com/nvim-neotest/neotest/blob/fee5ce9bdc3dff4706a29b012e75025ab376becb/README.md?plain=1#L34-L35
Per the linked issue, this was fixed upstream.

Only one of the issues solved by the plugin was addressed so the recommendation still stands https://github.com/antoinemadec/FixCursorHold.nvim/issues/13

Maybe it makes sense to copy the remaining functionality to neotest? I mean FixCursorHold is clearly not maintained. It is under MIT so with a thank you in README, copying the needed stuff over,  and we could just remove the extra dependency. It is really not that big in terms of line of code. What do you think?

For what reason though? Removing a dependency isn't a reason in itself. It hasn't had commits in a while but also hasn't had any issues because it is stable, even complete.

I would say it's better for the UX, because it's less hussle for the user and also reduces the risk that something break in the future, especially if anything this plugin used of it is already feature compete. But this is only my opinion.

Closing as I don't wish to integrate the functionality into neotest at this time

Quick question, if I use vim.opt.swapfile = false then I don't need FixCursorHold.nvim at all, right?


[boost-url] build failure

Operating system
win10
Compiler
vs2015Community
Steps to reproduce the behavior
.\vcpkg install boost-url[core]:x64-windows

Failure logs
Computing installation plan...
The following packages will be built and installed:
boost-url[core]:x64-windows -> 1.82.0#1
Detecting compiler hash for triplet x64-windows...
Restored 0 package(s) from C:\Users\top\AppData\Local\vcpkg\archives in 121 us. Use --debug to see more details.
Installing 1/1 boost-url:x64-windows...
Building boost-url[core]:x64-windows...
-- Using cached boostorg-url-boost-1.82.0.tar.gz.
-- Cleaning sources at D:/vcpkg2015/vcpkg/buildtrees/boost-url/src/ost-1.82.0-125968c34f.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source D:/vcpkg2015/vcpkg/downloads/boostorg-url-boost-1.82.0.tar.gz
-- Using source at D:/vcpkg2015/vcpkg/buildtrees/boost-url/src/ost-1.82.0-125968c34f.clean
-- Getting CMake variables for x64-windows
-- Configuring x64-windows
-- Building x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
Command failed: "C:/Program Files/CMake/bin/cmake.exe" --build . --config Debug --target install -- -v -j25
Working Directory: D:/vcpkg2015/vcpkg/buildtrees/boost-url/x64-windows-dbg
See logs for more information:
D:\vcpkg2015\vcpkg\buildtrees\boost-url\install-x64-windows-dbg-out.log
Call Stack (most recent call first):
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
installed/x64-windows/share/boost-build/boost-modular-build.cmake:140 (vcpkg_cmake_install)
ports/boost-url/portfile.cmake:17 (boost_modular_build)
scripts/ports.cmake:147 (include)
error: building boost-url:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest port files with git pull and vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+boost-url
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?title=[boost-url]+Build+error&body=Copy+issue+body+from+D%3A%2Fvcpkg2015%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md
Additional context
“ Command failed: "C:/Program Files/CMake/bin/cmake.exe" --build . --config Debug --target install -- -v -j25”
is this normal ?  " ... --target install -- -v -j25 "

Could you please provide us with D:\vcpkg2015\vcpkg\buildtrees\boost-url\install-x64-windows-dbg-out.log? Thank you!

using VisualStudio2019Community , " boost-url[core]:x64-windows -> 1.82.0#1" can be installed successfully.

I'm glad to hear that this issue has been resolved on higher versions of VS.


node_modules/@angular/core/index"' has no exported member 'NgIterable'.

hii,
i Update my ionic version than I facining a this error
node_modules/@angular/core/index"' has no exported member 'NgIterable'.
node_modules/@angular/core/index"' has no exported member 'TrackByFunction'.
node_modules/@angular/core/index"' has no exported member 'InjectionToken'.
this is my ionic info
cli packages: (F:\mobileApp\DrivekoolApp\node_modules)
@ionic/cli-plugin-cordova       : 1.6.2
@ionic/cli-plugin-ionic-angular : 1.4.1
@ionic/cli-utils                : 1.7.0
ionic (Ionic CLI)               : 3.7.0
global packages:
Cordova CLI : 7.0.1
local packages:
@ionic/app-scripts : 2.1.4
Cordova Platforms  : android 6.1.2
Ionic Framework    : ionic-angular 3.6.1
System:
Node : v6.11.3
OS   : Windows 10
npm  : 3.10.10
please help me to get out soltion

What is in the dependencies section of your package.json file?

dependencies.txt
please find the attachment.

Your Angular versions are inconsistent.  Currently, you have:

"@angular/common": "4.1.3",
"@angular/compiler": "4.1.3",
"@angular/compiler-cli": "4.1.3",
"@angular/core": "4.1.3",
"@angular/forms": "4.1.3",
"@angular/http": "4.1.3",
"@angular/platform-browser": "4.1.3",
"@angular/platform-browser-dynamic": "4.1.3",
"@angular/platform-server": "4.1.3",

Note that the version is pinned at `4.1.3` (no '^' or '~').

Did making your dependencies consistent with what<EMAIL_ADDRESS>expects solve your issue? Please let me know. In the meantime, I am going to close this issue, but will be happy to reopen it if need be.


feat: add CI pipeline tests for network node helm installation

Description
This pull request changes the following:

enhance GitHub workflow to run helm test with direct install and NMT install

Related Issues

Closes #202

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


update pipeline to support 1.12 now that it is out

Seems like the pipeline dynamic-metalink resource is going to need a bit of an update since 1.12 shipped.
cc @dpb587-pivotal

Might be required to configure GOCACHE when adding 1.12 support (requested in #12). I saw the following error from my binary's packaging script when it was trying to autoupgrade go (patch).

build cache is required, but could not be located: GOCACHE is not defined and neither $XDG_CACHE_HOME nor $HOME are defined

We'd be keen to see this added to golang-release as soon as possible as we are planning to bump to Golang 1.12 this month if possible. We would happily contribute although we don't know the process.
cc @jimbo459

Services Enablement are also keen to see 1.12 added here. We would like to release soon with go-1.12 so would like an idea of if / when 1.12 will be added, so we can manually add a go-1.12 tarball if necessary.

1.12 is now added. For future reference, everything is pipelined so the work is largely a find and replace as shown here (there was also some GoCache stuff). I'm waiting on getting added to this repo to close this issue.


Add template and scaffold for ExpressJS APIs

📦 Pull Request
✨ New Template✨

Add template and scaffold for ExpressJS APIs

✅ Fixed Issues

NA

🚨 Test instructions

N/A

⚠ Don't forget to add a semver label!

minor: Add express-api template

Add template and scaffold for ExpressJS APIs

Can I get a better high-level explanation of these changes?

As a rule, don't add lock files to templates, we can remove this:

This template spins a node server and provides the following endpoints:

HTTP verbs
Endpoint
Description

GET
http://localhost:8080
unsecured

GET
http://localhost:8080/secret
secured with Magic

GET
http://localhost:8080/api/todos
unsecured - list of todos

GET
http://localhost:8080/api/todos/:id
unsecured - displays single todo based on id

POST
http://localhost:8080/api/todos
secured - create a todo

PUT
http://localhost:8080/api/todos/:id
secured - update a todo based on id

DELETE
http://localhost:8080/api/todos/:id
secured - delete a todo based on id


[FEATURE REQUEST] Add back the Clip to bounding box option from the original app

As the title says, by default, the web version has the toggle to clip sprites to their bounding boxes enabled.
I, personally, dislike this, as when exporting individual PNGs can cause issues like the frame being abruptly cut or the image not maintaining the same position and being off-center.
Hopefully we get this option back so we can disable it.

I've added it now in the latest version


For the {{DOMPoint}} interface, setting the
    {{DOMPoint/x}} attribute must set the x coordinate to the new value.

    The <dfn>y</dfn> attribute, on getting, must return the y
    coordinate value. For the {{DOMPoint}} interface, setting the
    {{DOMPoint/y}} attribute must set the y coordinate to the new value.

    The <dfn>z</dfn> attribute, on getting, must return the z
    coordinate value. For the {{DOMPoint}} interface, setting the
    {{DOMPoint/z}} attribute must set the z coordinate to the new value.

    The <dfn>w</dfn> attribute, on getting, must return the w
    perspective value. For the {{DOMPoint}} interface, setting the
    {{DOMPoint/w}} attribute must set the w perspective to the new value.

Now all attributes start linking to the arguments of the DOMPoint constructor instead of their definitions and I get the following errors:
WARNING: Multiple elements have the same ID 'dom-domrectreadonly-y'.
Deduping, but this ID may not be stable across revisions.
WARNING: Multiple elements have the same ID 'dom-domrectreadonly-x'.
Deduping, but this ID may not be stable across revisions.
WARNING: Multiple elements have the same ID 'dom-domrectreadonly-height'.
Deduping, but this ID may not be stable across revisions.
WARNING: Multiple elements have the same ID 'dom-domrect-y'.
Deduping, but this ID may not be stable across revisions.
WARNING: Multiple elements have the same ID 'dom-domrect-x'.
Deduping, but this ID may not be stable across revisions.
WARNING: Multiple elements have the same ID 'dom-dompointreadonly-x'.
Deduping, but this ID may not be stable across revisions.
WARNING: Multiple elements have the same ID 'dom-dompointreadonly-y'.
Deduping, but this ID may not be stable across revisions.
WARNING: Multiple elements have the same ID 'dom-dompointreadonly-z'.
Deduping, but this ID may not be stable across revisions.
WARNING: Multiple elements have the same ID 'dom-dompointreadonly-w'.
Deduping, but this ID may not be stable across revisions.
WARNING: Multiple elements have the same ID 'dom-domquad-p1'.
Deduping, but this ID may not be stable across revisions.
WARNING: Multiple elements have the same ID 'dom-domquad-p3'.
Deduping, but this ID may not be stable across revisions.
WARNING: Multiple elements have the same ID 'dom-domquad-p2'.
Deduping, but this ID may not be stable across revisions.
WARNING: Multiple elements have the same ID 'dom-domquad-p4'.
Deduping, but this ID may not be stable across revisions.
WARNING: Multiple elements have the same ID 'dom-domrect-height'.
Deduping, but this ID may not be stable across revisions.
WARNING: Multiple elements have the same ID 'dom-domrectreadonly-width'.
Deduping, but this ID may not be stable across revisions.
WARNING: Multiple elements have the same ID 'dom-domrect-width'.
Deduping, but this ID may not be stable across revisions.
LINK ERROR: Multiple possible 'idl' local refs for 'x'.
Arbitrarily chose the one with type 'attribute' and for 'DOMPoint' or 'DOMPointReadOnly'.
{{DOMPoint/x}}
LINK ERROR: Multiple possible 'idl' local refs for 'y'.
Arbitrarily chose the one with type 'attribute' and for 'DOMPoint' or 'DOMPointReadOnly'.
{{DOMPoint/y}}
LINK ERROR: Multiple possible 'idl' local refs for 'z'.
Arbitrarily chose the one with type 'attribute' and for 'DOMPoint' or 'DOMPointReadOnly'.
{{DOMPoint/z}}
LINK ERROR: Multiple possible 'idl' local refs for 'w'.
Arbitrarily chose the one with type 'attribute' and for 'DOMPoint' or 'DOMPointReadOnly'.
{{DOMPoint/w}}
LINK ERROR: Multiple possible 'idl' local refs for 'x'.
Arbitrarily chose the one with type 'argument' and for 'DOMRect'.
{{DOMRect/x}}
LINK ERROR: Multiple possible 'idl' local refs for 'y'.
Arbitrarily chose the one with type 'argument' and for 'DOMRect'.
{{DOMRect/y}}
LINK ERROR: Multiple possible 'idl' local refs for 'width'.
Arbitrarily chose the one with type 'argument' and for 'DOMRect'.
{{DOMRect/width}}
LINK ERROR: Multiple possible 'idl' local refs for 'height'.
Arbitrarily chose the one with type 'argument' and for 'DOMRect'.
{{DOMRect/height}}
 ✔  Successfully generated, with 8 linking errors

Yup, dupe of #1519. I need to make Bikeshed aware of the new constructor method. Haven't been able to due to TPAC/etc.

Ah yes! Thanks.


Data table extension: Filtering

Data table extension: Filtering
Brief description
This issue will deliver the data table extension for filtering.
Details
Link to design
Links to other materials
e.g. sketch files, icons, images, prototypes
Design Maintainer(s)

Marion Brülls
Johanna Koval

Tasks
Before starting work on this epic, please review and complete the following.

[ ] Initial review of design/existing code

Working in Carbon for IBM Products package

[ ] Have you reviewed our
contribution guidelines?
[ ] Have you noted our
code guidelines?
[ ] Did you use the CLI to scaffold your new component?

Link to Sketch file with curated screens for dev to reference


An error occured: Failed processing format-parameters; Python 'pyquery' cannot be converted to a MySQL type

i want to store the result in Mysql，  but  when i use that：
@config(priority=3)
def detail_page(self, response):
    for each in response.doc('.video-flash-cont').items():
        print each
    return {
        "url": response.url,
        "title":response.doc('.title-name').text(),
        "game-name":response.doc('span > .game-name').text(),
        "users2":response.doc('.icon-users2').text(),
        "flash-cont":each,
        }
def on_result(self, result):
    if not result or not result['title']:
        return
    sql = SQL()
    sql.replace('douban_db',**result)

it tell me ：An error occured: Failed processing format-parameters; Python 'pyquery' cannot be converted to a MySQL type！
How to type conversion, I did not see the relevant description in the manual。
thanks for any  answers ！！

each is a pyquery object and cannot be converted to a MySQL type!
How do I know how to convert if you don't tell me what information you want from each?

i'm sorry, according to use print each，i get a object:

i just want  to insert those contents into mysql,  what should i do ?

https://pythonhosted.org/pyquery/api.html#pyquery.pyquery.PyQuery.html

that is what i need ,  thank you very much ~


Toolbar pt 2

Let us know when this is ready

Looking good, the redundant eyeDropperColor state needs to be removed then its good to be added


pkg/k8s: add support for multi-stack

Kubernetes has introduced support for multi-stack environments. This
commit adds the missing integration with k8s for multi-stack.
Signed-off-by: André Martins<EMAIL_ADDRESS>Fixes: https://github.com/cilium/cilium/issues/9214

This change is

test-me-please

Coverage decreased (-0.03%) to 44.29% when pulling 71cdc4ac5a2e11ff680b07a3fb179415cac626cb on pr/adding-multi-stack-support into 728c79e427438ab6f8d9375b62fccd6fed4ace3a on master.


adding myself to Contributing.md

ghinks recommended I open a PR here, I'd love to help with triage.

David is another first rate addition from Our organization 😀

So @wesleytodd are you still inclined to land and enable these things, or should we document the process and try to expand it out to more folks?

As discussed on the call, I am unable at this time to be the sole person managing this and we want to open it up.  I added @davidmashe for now, but we need a better solution.  I started the discussion in the triage team board, partly to test out that feature, so when we get a decision we can post it publicly.

Closing out PR as I confirmed that @davidmashe is in the group and we are working to pull membership data directly from the GitHub team.


history(period="5y", end=end_date) returns no data

yfinance version = 0.1.81
import datetime as dt
import yfinance as yf
import pandas as pd

end_date = dt.datetime.today()
y_data = yf.Ticker("^FTSE")
df_yf = y_data.history(period="5y", end=end_date)

...no data returned, and no error message.
Removing end=end_date fixes it. I can filter afterwards by end_date, but was hoping to benefit from built-in functionality in yfinance.

Correction: there is an error message: "- ^FTSE: No data found for this date range, symbol may be delisted"

The issue seems to be that only a parameter value for "end" is given, but not for "start", i.e. the following code would work:

Problem is this is ambiguous:
y_data.history(period="5y", end=end_date)

First though is user wants 5 years of data ending at end_date. But @dr1ver1 wants 5 years of data starting 5 years ago then capped by end_date.
Yahoo resolves this by ignoring period. My PR #1031 proposes ignoring dates instead. Not urgent so I forgot about it.

Good point. I guess your PR solves the issue.


Bind click doesn't work on dynamic element created inside a directive (if wrapped on label)

I have created a directive to clear an input text by show an icon (basically same functionality a search box has).
Turns out that the if I wrap the input element inside a label, the bind I create on the "clean icon" doesn't work for the click event  (dblcick and other events work fine)
If I wrap my element with a DIV, everything works
I have created a plunker to show the issue
http://plnkr.co/OxB9wGZNNV3rRqSJjhgo
Please, notice that the directive works correctly if I use the ionic version 1.0.0-beta.5

Greetings @militellovincenzo!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

This is because we use labels to set focus the the input.
Any click/taps/touches that happen with a label element will attempt to set focus to a child input.
For what you need, using a div instead of a label will work fine.


setWaveColor(int color) doesn't work

Just as the title says, setWaveColor(int color) doesn't work

This was fixed in version 0.9.1 of the library. If you still have this issue feel free to reopen this issue. Closing this for now. Thanks!


Verbosity and Logging

Implemented the --verbosity command flag and correct logging with log levels.
I had to alter the --verbosity flag a bit. I could not get Clap's parse(from_occurrences) to work correctly.
The log level is no longer increased with -v, -vv, ..., but instead by writing the log level as a String (for example --verbosity debug).

I found this https://github.com/clap-rs/clap-verbosity-flag which implements standard behaviour for verobosity flag. What do you guys think?

I found this https://github.com/clap-rs/clap-verbosity-flag which implements standard behaviour for verobosity flag. What do you guys think?

Ah that should propably work. I personally like the variant with the log level as string more, but i can change it to use this variant if you prefer that.

Alright, then i will try out the clap_verbosity_flag


Philips HUE app finds ha-bridge as HUE Bridge, but asks for me to press "the button in the center" to connect...

So, it does found ha-bridge correctly, but I can't proceed because I don't know how to simulate this "button in the center" press.
Does anyone had this problem before? any insight on how to proceed?
I tried to add it as a HUE Bridge V1 on the Alexa app, but that doesn't work... alexa can't find it.
To add in Alexa as a HUE Bridge V2, I need the Philips HUE app to add it successfully, but It never does because it requires me to "press the button in the center"... quite frustrating...

The ha-bridge is always in the push the button state. There is no testing against the philips hue app so I can't say it will work.

Same issue for me, would you please give the file where link is implemented ?
Philips doesn't use a new protocol (upnp ?) to link the hue ?

It's the same with me. The Philips HUe app did find the bridge, but asks to press a button. In third party apps, the bridge automatically connects.


Updating from 0.9 to 0.11 -- unresolved imports MemoryMap and MemoryRegionType

Blog_OS V2 provided a memory.rs module, which contains the following code:
use bootloader::boot_info::{MemoryMap, MemoryRegionType};

...

/// A FrameAllocator that returns usable frames from the bootloader's memory map.
pub struct BootInfoFrameAllocator {
    memory_map: &'static MemoryMap,
    next: usize,
}

...

impl BootInfoFrameAllocator {
    /// Create a FrameAllocator from the passed memory map.
    ///
    /// This function is unsafe because the caller must guarantee that the passed
    /// memory map is valid. The main requirement is that all frames that are marked
    /// as `USABLE` in it are really unused.
    pub unsafe fn init(memory_map: &'static MemoryMap) -> Self {
        BootInfoFrameAllocator {
            memory_map,
            next: 0,
        }
    }

    /// Returns an iterator over the usable frames specified in the memory map.
    fn usable_frames(&self) -> impl Iterator<Item = PhysFrame> {
        // get usable regions from memory map
        let regions = self.memory_map.iter();
        let usable_regions = regions.filter(|r| r.region_type == MemoryRegionType::Usable);
        // map each region to its address range
        let addr_ranges = usable_regions.map(|r| r.range.start_addr()..r.range.end_addr());
        // transform to an iterator of frame start addresses
        let frame_addresses = addr_ranges.flat_map(|r| r.step_by(4096));
        // create `PhysFrame` types from the start addresses
        frame_addresses.map(|addr| PhysFrame::containing_address(PhysAddr::new(addr)))
    }
}

And the initialization occurs in kernel_main of main.rs:
let phys_mem_offset = VirtAddr::new(boot_info.physical_memory_offset);
let mut mapper = unsafe { kernel::memory::init(phys_mem_offset) };

After upgrading to v0.11 and replacing the kernel crate with bootloader_api, MemoryMap and MemoryRegionType are no longer found. What is the appropriate way to update these structs?

The second edition of blog os depends on bootloader 0.9. Bootloader 0.11 doesn't just have a different api, but also requires building the kernel in a significantly different way. If you want to use bootloader 0.11, you have to use the work in progress third edition of blog os.


devimint cleanup

important change is reducing build.sh and now beautiful typed env variables.
for a dev env prespective:
you can now enter the devimint environment.
say you want to run integration tests with real fixtures. You can do:
devimint -d /tmp/foo external-daemons
and in a different shell:
eval "$(devimint -d /tmp/foo env)"
and then cargo test

This is pretty cool:
** devimint  env
export FM_FED_SIZE="4"
export FM_TMP_DIR="/var/folders/fw/ysg6g9jn3kv8hb7_jvxwyb0r0000gn/T/nix-shell.4M2Rqj/fm-unJC"
...
export FM_TEST_BITCOIND_RPC="http://bitcoin:bitcoin@<IP_ADDRESS>:18443"
export FM_BITCOIND_RPC="http://bitcoin:bitcoin@<IP_ADDRESS>:18443"**

LGTM. Needs rebase.

Needs rebase :(

this changes code from #2377 significantly


This is a test

This is a test

https://github.com/lgs-games/memorize/blame/master/proj/agile-scrum/index.md#L10-L16

https://github.com/lgs-games/memorize/blame/master/proj/agile-scrum/index.md#L10-L16
Originally posted by @QuentinRa in https://github.com/lgs-games/memorize/issues/13#issuecomment-907659130

https://github.com/lgs-games/memorize/pull/13/files#diff-f39d307a8cfeccd5cfbca1896b53c9a1bcc006f26e65f776a61b24b6aa522368R1-R8

https://github.com/lgs-games/memorize/blob/40b2e9daedfe80075c09d513622ecfc31c4672f1/info/api/index.md#L2-L24


Stuck inline suggestion

This has happened a couple times today so it must be a new thing. Both times when I had an inline suggestion or copilot suggestion and triggered the suggest widget manually. The only way to get it to go away is to switch editors

.
Pressing escape didn't do anything

Something on the console? I'd expect this to be some kind of error/exception case which leads to failure in clean-up and not frequent asking of inline suggestions

Yes, this is most likely a decoration that is not removed. I'll investigate.

Happened again, and the suggest widget was not involved

Do you have reproduction steps?
I cannot explain this bug...
As soon as the cursor leaves the line, all decorations should be cleaned up.

Nope. Just have seen it randomly a few times. If it would help to debug after it's in this state, you can tell me where to set a breakpoint

I’ve been experiencing this with Copilot pretty frequently. Unfortunately I can’t quite figure out how to reproduce reliably, but it seems to be most likely to happen when I’m moving back and forth between lines a lot, editing mid-expression, as opposed to typing linearly.

It’s on a roll right now. It feels like maybe there’s sometimes a conflict between the completions preview and the decoration added by Copilot?

Can you hover over both inline suggestions? What happens?
Also, can you check the dev tool logs? Thanks :)

I’ll check if I see it happen again. I believe at the time I hovered them and nothing happened, but I can’t be 100% sure.

Were you able to reproduce? We did some changes that might have fixed this.

I haven’t seen it since I last chimed in. Would guess it’s fixed 👍

Closed by https://github.com/microsoft/vscode/commit/1c8ffe98e90c8c9d17eebd6321418d484e323b72.


Removed some unused and global variables

Some tiny fixes. There are a lot more unused variables around but it's not obvious for me how to fix them. E.g. there are a lot of unused error messages (local ok, err = ...; err is then unused) which should probably be reported instead of simply being removed.

Thanks! Did you check unused variables using a tool? Could you generate a list so I could go through them?

I used luacheck, here is the list: https://gist.github.com/mpeterv/13457c89e5113d418c14

Thank you! I'll look into it. BTW, I just integrated luacheck into my text editor :)
https://github.com/hishamhm/dit/tree/master/scripts

Awesome!


Do not use a disabled-option in the docs

Updates rust-lang/cargo#5717
Since people tend to copy/paste, the docs should not use the option which will disable curls low-speed-limit. Rather use a value lower than the default of 10
Also reverts removal of default low-speed-time (30s) in case no timeout is configured

@bors: r+
Thanks!

:pushpin: Commit f88adb05148d1e702fca3302df07d2fe3521d049 has been approved by alexcrichton

@bors: r+

:pushpin: Commit 189f14fe03eb2ffefcd8a111dad0501364e0e9b5 has been approved by alexcrichton

:hourglass: Testing commit 189f14fe03eb2ffefcd8a111dad0501364e0e9b5 with merge 57e6b3a84ad8601d2865c31eb2e051c5c6970a37...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 57e6b3a84ad8601d2865c31eb2e051c5c6970a37 to master...


Fallback to wrong language preference when the top preference is unavailable

I have the following configuration in my Startup.cs
var options = new RequestLocalizationOptions
{
    SupportedCultures = new List<CultureInfo>
    {
        new CultureInfo("zh-Hans"),
        new CultureInfo("en-US")
    }
};

app.UseRequestLocalization(options);

Then I set my language preference in IE with the following priorities (from highest to lowest):

ja (Japanese)
zh-Hans (Simplified Chinese)
en-US (English, United States)

However, the page fallback to en-US even when zh-Hans is available and has higher priority:

This is happen because if the requested culture is not available in the supported cultures that you already define then the current implementation is looking for the DefaultRequestCulture which is the CultureInfo.CurrentCulture, BTW i'm trying to get a fix for this issue ASAP

@ChengTian can you try the fix that I made in my fork https://github.com/hishamco/Localization and let me know if it's solve the issue

@ChengTian I'm asking if the issue got fixed or not

@hishamco , if you already test your changes, please send a PR. The owner of this repo will do some verification before merging your PR.

Ok @ChengTian, I will send it ASAP

I made this PR #50 to solve this issue

@kirthik can you re-verify the fix in https://github.com/aspnet/Localization/pull/50, merge it, and add any extra tests that we need?

I actually think this should be fixed in AcceptLanguageHeaderRequestCultureProvider. Essentially, after it validates a culture, it should compare the result and if it's not using the culture that was passed in, it should move on to the next culture in the list (it already loops through the cultures, it just isn't doing the check).
https://github.com/aspnet/Localization/blob/dev/src/Microsoft.AspNet.Localization/AcceptLanguageHeaderRequestCultureProvider.cs#L58

merged 7b53bdd43e2e605a8eb686f22ceb558f46a1c4f5

@kirthik mark as 3 - Done?

Changed it.


Gamma's Froggy Hunt cutscene

It looks like SA1 has a lighting change in the cutscene where Eggman talks to the Egg Carrier crew.

Unless there is some magic involving SL files, I think the base palette is being temporarily overwritten with dark gray until the moment the lights turn on, or the base palette's brightness is lowered.
Recreating this effect will also help #26.

Here's a savegame that starts Gamma's story right on the cutscene.

I implemented it in DC_EggCarrier using the following:
sub_6F4577 loads an object (ObjectMaster at dword_3C85138) that is supposed to turn off the lights.
sub_6F4620 destroys that object right before Eggman starts speaking.
I loaded a modified PL file that has a grey diffuse palette (FF646464) and hooked the above functions to blend into this palette when the lights are off, and disable blending when the lights turn on.


Upgrade to Node v16

Currently the docs engine uses Node v14. Let's upgrade to v16.
See this comment for context.

I don't think Vercel has a per-branch nodejs version option. The easy route would be to test locally with 16 (pref 16.16) as Vercel automatically rolls out minor/patch versions. If all looks good, we just switch the nodejs version and watch the deploy. Worst case scenario its down for a few minutes while we roll back. I don't see this are particularly dangerous so I'm in favor of just flippin the switch. Up to you!

@avatus That sounds good to me!

We've started getting EOL logs for Node 14.x in the Vercel deploy logs. The deadline to upgrade is Aug 15, 2023. The log messages also recommend Node 18 (https://vercel.com/goteleport/docs/3S9GdToztceSP8m68Q7JBTN331rq). @avatus Should we try Node 18.x, or is it okay to go with Node 16.x? Either way, I can look into upgrading this week

I've just upgraded the docs site to Node 16 in Vercel

Thanks. lets bump to 18 after a bit of testing

👍 I opened an issue for that here: https://github.com/gravitational/docs/issues/316


Proposition: Remove duplicated first line (short type info) in ghd-mod hints

As I understand first line is short type info and second, third, etc are description. My proposition is if "short description" is literally contained inside "full type information" to remove it (first line), so only full description is left. This will minimize type information clutter and will normalize information inside it a bit.

I understand where you're coming from, but there are two reasons for having it this way:

Fixing this would introduce unnecessary complexity into code that's complex enough as it is
There are cases where getting type might not work, while getting full info works fine. It's useful to be able to differentiate at a glance if it's that. Hiding instantiated type will make this nigh impossible.

For the second point - it could be enabled in Debug mode to visualize both. But in normal non-debug to remove duplicate. By removing duplicate, I mean just search for first line in full text information literally - infix search. Not more complex than that.

Implemented in v2.2.1

Works great! Thanks a lot!


Marc 260/264 Update

Edit the MARC processing code to handle supporting both 260 and 264 fields.

The code we use tries to strip out anything that doesn't look like a date, but it isn't going to support all the variations that the field is documented to support in MARC.
https://www.loc.gov/marc/bibliographic/bd260.html
https://www.loc.gov/marc/bibliographic/bd264.html
That support would be a larger project, and would be better done as part of an enhancement of BlackLight MARC or other community project rather than custom CRKN code.


[kernels] fix usage of C stdlib abs (#863)

The EwUnary kernel used the C stdlib abs function which instead of the appropriate C++ std::abs function. This caused a bug where calling abs with floating point values were cast to integer values during conversion.
Closes #863

would it make sense to also add a test case when we spot a bug like this?

would it make sense to also add a test case when we spot a bug like this?

yes ofc! I already have them locally but forgot to push them with the PR and just want to let the CI run finish before I push again :)

I tested it, works fine


Change back transition animation

Version

react-native-router-flux v3.37.0
react-native v0.38.1

I am using react-native-router-flux for navigation. Is there a way to change the type of transition animation when I go back from a scene to previous scene. If you look carefully, there's a small white space above the navbar which I would like to get rid of. I am thinking if the same animation as transitioning to a new scene can be used to the back transition animation.

@vnshgrg https://github.com/aksonov/react-native-router-flux/issues/1202


update tutorials for fixed page property

@argelius please take a look if it is fine, merge it.

Thanks!

Looks good!


Cannot run flask on app engine

File "/Users/aksonov/PycharmProjects/issuengine/flask/app.py", line 289, in init
instance_path = self.auto_find_instance_path()
File "/Users/aksonov/PycharmProjects/issuengine/flask/app.py", line 577, in auto_find_instance_path
prefix, package_path = find_package(self.import_name)
File "/Users/aksonov/PycharmProjects/issuengine/flask/helpers.py", line 532, in find_package
filename = loader.archive
AttributeError: 'HardenedModulesHook' object has no attribute 'archive'
INFO     2012-01-16 12:52:07,534 dev_appserver.py:2832] "GET / HTTP/1.1" 500

Which version of Flask is that?

Thanks for the traceback. I'll fix it.
On Jan 16, 2012 7:53 AM, "aksonov" <
<EMAIL_ADDRESS>wrote:

File "/Users/aksonov/PycharmProjects/issuengine/flask/app.py", line 289,
in init
instance_path = self.auto_find_instance_path()
File "/Users/aksonov/PycharmProjects/issuengine/flask/app.py", line 577,
in auto_find_instance_path
prefix, package_path = find_package(self.import_name)
File "/Users/aksonov/PycharmProjects/issuengine/flask/helpers.py", line
532, in find_package
filename = loader.archive
AttributeError: 'HardenedModulesHook' object has no attribute 'archive'
INFO     2012-01-16 12:52:07,534 dev_appserver.py:2832] "GET / HTTP/1.1"
500

Reply to this email directly or view it on GitHub:
https://github.com/mitsuhiko/flask/issues/380

latest one, i've just used http://f.souza.cc/2010/08/flying-with-flask-on-google-app-engine/ as guide.
Here is project attached
On 16 янв. 2012, at 14:57, Armin Ronacher wrote:

Which version of Flask is that?

Reply to this email directly or view it on GitHub:
https://github.com/mitsuhiko/flask/issues/380#issuecomment-3510306

It's master. I see now that App Engine has a loader with a slightly
different API. I have the fix, will apply shortly.
On Jan 16, 2012 8:01 AM, "aksonov" <
<EMAIL_ADDRESS>wrote:

latest one, i've just used
http://f.souza.cc/2010/08/flying-with-flask-on-google-app-engine/ as
guide.
Here is project attached
On 16 янв. 2012, at 14:57, Armin Ronacher wrote:

Which version of Flask is that?

Reply to this email directly or view it on GitHub:
https://github.com/mitsuhiko/flask/issues/380#issuecomment-3510306

Reply to this email directly or view it on GitHub:
https://github.com/mitsuhiko/flask/issues/380#issuecomment-3510356

@aksonov I pushed a fix to master.  Could you try it?  If it works, I'll add a test.  If not, I'll have to get to know Google App Engine's import loader.
We use topic branches for new development, but sometimes we don't catch Google App Engine issues until we are closer to a Flask release.  You can always drop back to the latest Flask release where there are GAE issues with master.
Thanks for reporting this!
Ron

Works well now, thanks!


Integrate OPUS with PDS planetary viewer tools

We could integrate OPUS with the existing Saturn/Jupiter/Uranus/Neptune Viewer Tools to show the user what objects were in the field of view during an observation. The tools will need to be upgraded to handle the spacecraft pointing and the camera rotation.

Idea from Mitch: Overlay marking of objects in FOV on mouse-over.


types(runtime-core): Allow InjectionKey to be used as a valid PropertyKey

This allows the InjectionKey to be used as a PropertyKey, useful for the OptionsAPI.
const key = Symbol() as InjectionKey<number>

defineComponent({
 provide: {
   // this now works
   [key]: 'foo'
 }
}

This also affects VTU, since the user needs to provide it's own overrides if needed:
const colorKey = Symbol() as InjectionKey<string>

// before
mount(A, { globals: { provide: { [colorKey as symbol]: ref('#999999') } }

// after : No need to cast the symbol
mount(A, { globals: { provide: { [colorKey]: ref('#999999') } }

There's a small issue that this change brings, with this change a Symbol cannot be inferred as an InjectionKey
// before worked
const key: InjectionKey<string> = Symbol(); // worked because `InjectionKey` extended `Symbol`

// after
const key = Symbol() as InjectionKey<string>; // it need to be changed to a more lenient casting

This should lay down some work to support typed injections on the defineComponent when using Options API
Ref: https://github.com/microsoft/TypeScript/issues/46956

This would technically be a (type) breaking change though, it would break existing apps using const key: InjectionKey<string> = Symbol();?
This probably needs to be put in a minor.

This would technically be a (type) breaking change though, it would break existing apps using const key: InjectionKey<string> = Symbol();?

Yes

Just want to point out that this casting also (as of my knowledge) is required when using the function mount() in your tests. An example can be found in https://github.com/auth0/auth0-vue/issues/228 and https://test-utils.vuejs.org/api/#global. Please let me (or the author of auth0) know if exporting your key as type InjectionKey<Auth0VueClient> is bad to begin with.

/ecosystem-ci run

Looks like the constraint of not being able to use const k: InjectionKey<T> = ... is quite disruptive, but I managed to find out a compatible fix in 321d80758.


grpcJsonTranscoder: add match_unregistered_custom_verb

Signed-off-by: Xuyang Tao<EMAIL_ADDRESS>Commit Message: mainly update the grpcJsonTranscoder to include the latest path matcher filter change for always checking custom verb no matter if it is registered or not.
Risk Level: Low
Testing: added the unit test
Docs Changes: None
Release Notes: Yes

@qiwzhang Hi Wayne, PTAL


Backdrop ignoreTouchAnimation

I have global tap animations enabled and noticed, that they will also apply to the backdrop of the modal.

I tried disabling them using the ignoreTouchAnimation="true" attribute on the drawer, but that didn't have any effect. Is there a way to disable the touch animations?
Which platform(s) does your issue occur on?

Android + iOS, Nativescript 8.6
tested on emulator, but probably everywhere

Versions

CLI + runtimes: 8.6.x
Plugin version: 0.1.23

Code to enable global touch animations
import { TouchManager, CoreTypes } from '@nativescript/core'

TouchManager.enableGlobalTapAnimations = true
TouchManager.animations = {
    down: {
        scale: { x: 0.95, y: 0.95 },
        duration: 200,
        curve: CoreTypes.AnimationCurve.easeInOut
    },
    up: {
        scale: { x: 1, y: 1 },
        duration: 200,
        curve: CoreTypes.AnimationCurve.easeInOut
    }
}

It's working in the latest version. Muchas gracias.


✨ NEW: Add ref-type option to button-ref directive

Codecov Report

Merging #19 (968ad2e) into main (b258e89) will decrease coverage by 0.07%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##             main      #19      +/-   ##
==========================================
- Coverage   88.90%   88.82%   -0.08%
==========================================
  Files          10       10
  Lines         856      859       +3
==========================================
+ Hits          761      763       +2
- Misses         95       96       +1

Flag
Coverage Δ

pytests
88.82% <80.00%> (-0.08%)
:arrow_down:

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

Impacted Files
Coverage Δ

sphinx_design/badges_buttons.py
89.28% <80.00%> (-0.63%)
:arrow_down:

Continue to review full report at Codecov.

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


UnboundLocalError: local variable 'timedelays' referenced before assignment

Where can I find/gettimestamps.json for --path_timestamps?
https://github.com/princeton-computational-imaging/SeeingThroughFog/blob/5de1c423e0239eef3e84fa402885e7f2a5b0a10e/tools/DatasetViewer/DataViewer_V2.py#L25
Problem when reading matching file for AdverseWeather2Algolux!
python-BaseException
Traceback (most recent call last):
  File "/scratch_net/hox/mhahner/apps/pycharm-2020.1.2/plugins/python/helpers/pydev/pydevd.py", line 1448, in _exec
    pydev_imports.execfile(file, globals, locals)  # execute the script
  File "/scratch_net/hox/mhahner/apps/pycharm-2020.1.2/plugins/python/helpers/pydev/_pydev_imps/_pydev_execfile.py", line 18, in execfile
    exec(compile(contents+"\n", file, 'exec'), glob, loc)
  File "/scratch_net/hox/mhahner/repositories/SeeingThroughFog/tools/DatasetViewer/DataViewer_V2.py", line 886, in <module>
    main(args)
  File "/scratch_net/hox/mhahner/repositories/SeeingThroughFog/tools/DatasetViewer/DataViewer_V2.py", line 867, in main
    DatasetViewer(root_dir, topics, timedelays, can_speed_topic, can_steering_angle_topic,
UnboundLocalError: local variable 'timedelays' referenced before assignment

Have exactly the same problem! Did anyone find a solution?

Hi,
the missing timestamps.json has been uploaded and the code has been slightly adapted to load the new timestamps.json. Can you check if this fixes the problem on your side?
Thank you in advance, Mario

@MarioBijelic yep, now it works!

Thanks!


Move fakeflac to Python 3

Move script to Python 3
Fix flake8 issues
Replace deprecated scipy.log10
Fix minor spelling issue

Thank you very much!


Doc draft PRs for WIP, private forks for CI-bashing

See commit messages for details.

I'll give others a chance to review.


Add brain functions table for overview

This PR is a follow-up of #6460(comment) and adds a RST overview table from a functional point of view.
In my opinion, such a table improves visibility on the refactor/advancement of mayavi-based features of the Brain object.
I put all the functions I could find as a first step but it may be more useful to resize to the subset of functions used in practice and prioritize the tasks maybe as an ordered TODO list. Any feedback is welcome.

no need to reimplement 100% of the API of pysurfer. See what breaks in the
doc
build with pyvista and you'll see what people have actually a chance to use.

no need to reimplement 100% of the API of pysurfer.

I agree with you @agramfort , we need only what's used of course.

See what breaks in the doc build with pyvista and you'll see what people have actually a chance to use.

I like the idea and this was also suggested by @larsoner in this comment I think.
But as the refactor is not yet completed, would you be okay to start with this version of the table and refine it during the process?

sure as long as the objective is not to tick all boxes

The objective is to tick the boxes we need.


Prevent double note

Url hash handling method now blocks user from going directly to the "detail" page without setting a location marker. That marker and associated address objects are cleared once the POI is posted. The Url hash resets them immediately up loading the "done" page confirmation .

Fix for post call failure while running in a Firefox browser.
Minor refactoring

The Italian fork added a second page (active.html) and mixed the assets together. I wanted to split them into separate trees. Each based on the html they are associated with. It will make it easier to manage any changes to files required by the libraries we use when they get upgraded. The problem is that most being use been considered deprecated.

Replacing with #128 which is a cleaner version of this PR


A11y_AzureToolsStorageExplorer_Attachtolocalemulator_Attachtolocalemulator_Screenreader : NVDA is not announcing the editable content along with display name.

" Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing aster and easier.”
GitHubTags: #A11y_AzureToolsStorageExplorer; #A11yMAS; #A11YTCS; #DesktopApp; #MAS1.3.1; #NVDA; Win10;3
Environment Details:
Application Name: Azure Tools Storage Explorer
Application Version: 1.10.0
Windows10
Repro Steps:

Launch Storage Explorer
Navigate to "Open Connect Dialog" pane present on left side of screen and hit enter.
Select "Attach to local emulator" radio button and hit enter on Next button.
"Attach to Local Emulator" screen gets opened.
Verify that all the elements of "Attach to Local Emulator" screen are accessible and MAS Compliant.
6.Start NVDA and navigate using the tab key.Observe the NVDA readings.

Actual:
NVDA is not announcing the editable content along with display name.
Similar issue is observed for below scenarios:
Use a SAS URL : Attach with SAS URL:

Launch Storage Explorer
Navigate to "Open Connect Dialog" pane present on left side of screen and hit enter.
Select "Use a SAS URL" radio button and hit enter on Next button.
"Attach with SAS URL" screen gets opened.
Verify that all the elements of "Attach with SAS URL" screen are accessible and MAS Compliant.

Expected:
NVDA should  announce the editable content along with display name.
User Impact:
Screen readers user will get unnecessarily get information three times.
Recommendation:
https://microsoft.sharepoint.com/teams/msenable/mas/Pages/browse-fixes.aspx
MAS Reference:
MAS1.3.1
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}
Attachment for Reference

This is related to #1891 and will be fixed when the PR for that is merged. 😀

Fix merged into master.

Verified this issue on:Azure Tools Storage Explorer (Version: 1.12.0)
The issue is no longer to reproduces, Hence closing this bug.

GithubTags:#Closed;

GitHubTags:#BM-TCS-StorageExplorer-Win32-Sep2019;


Rename GDAX to CoinbasePro

Expected Behavior
Lean should reference Coinbase Pro instead of GDAX.
Actual Behavior
The brokerage, fee, market refers to GDAX.
Potential Solution
Rename the classes using CoinbasePro.
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

Also include the GDAXOrderProperties class


Updating CODEOWNERS Communication NetworkTraversal

Updating owners for ACS NetworkTraversal after current owner left.

/check-enforcer override


fix(cmp): properly set cmp group_index

nvim-cmp has a group_index property that we used incorrectly in LazyVim, resulting in only showing entries from the first group that had entries.
This lead to several issues with different sources like copilot.
Probably fixes a number of issues at copilot-cmp:

[x] https://github.com/zbirenbaum/copilot-cmp/issues/93
[x] https://github.com/zbirenbaum/copilot-cmp/issues/75
[x] https://github.com/zbirenbaum/copilot-cmp/issues/86

group_index docs
For instance, you can set the buffer's source group_index to a larger number
if you don't want to see buffer source items while nvim-lsp source is available:
    cmp.setup {
      sources = {
        { name = 'nvim_lsp', group_index = 1 },
        { name = 'buffer', group_index = 2 },
      }
    }

You can also achieve this by using the built-in configuration helper like this:
    cmp.setup {
      sources = cmp.config.sources({
        { name = 'nvim_lsp' },
      }, {
        { name = 'buffer' },
      })
    }

I had questioned the choice of group_index = 2 in a previous PR (that was closed when codeium.nvim was originally archived), but never got an answer about the choice made, so I brushed it off as personal preference. In my personal spec I had it in the same group as nvim_lsp. Not using it any more in favor of codeium.vim, since I found that nvim-cmp had become quite sluggish for my old pc with the addition of codeium.nvim.

My bad, I blindly copied the group_index from https://github.com/zbirenbaum/copilot-cmp#source-definition
And we used cmp.sources() that sets a different group_index for each source, which is obviously never something someone actually wants.

From my understanding cmp.config.sources() doesn't set a different group_index for each source. It sets a different group_index for each subtable it contains. For example in this snippet
 sources = cmp.config.sources({
                    { name = 'nvim_lsp' },
                    { name = 'luasnip' },
                }, {
                    { name = 'buffer' },
                }),

nvim_lsp and luasnip will have group_index = 1 and buffer group_index = 2. But I also prefer using the first method with just table_insert and specifically declaring group_index.

oh, I see, that does make sense :)