pnpm leaves broken packages in the store after crash

pnpm version: 0.43.2
Code to reproduce the issue:
Run an install that will fail.
Expected behavior:
No half-installed packages will be added to the store
Actual behavior:
All packages are being written to the store immediately and when there's a crash they are left there broken. Next installation will try to reuse them and will fail.

good catch


Thing1Thing2: Update PPP and AboutUs Page

Updated PPP (removed extra details and kept minimally required ones), and
updated description and profile picture in AboutUs page.
Closes #13

Seems like there's some checkstyle errors e.g., trailing whitespaces, which is also what's causing the CI to fail. Just need to correct them, otherwise LGTM


Escaping required for promotion tags

Rn promotions tags look like rf#prod. # requires escaping in some shells. Is there a better alternative? Need to check @ also.

Since we released it with # already, I don't think we need to change this anytime soon.
Still, when we print a git push suggestion, we need to escape those characters I believe (how this will work in shells where you don't need to escape them? Won't it break there?)
e.g.
$ gto assign xx --stage prod
Created git tag 'xx#prod#1' that assigns stage to version 'v0.0.1'
To push the changes upstream, run:
    git push xx#prod#1

One more things with this: git push xx#prod#1 miss remote name. E.g. it should be git push origin xx#prod#1 or something. Not sure how to print this in CLI output. git push origin xx#prod#1 or git push <remote> xx#prod#1 to avoid blindly copy-pasting and running the suggestion?


Add graceful exit feature as a callback

Supersedes #2481.
Using a sentinel file seems to be a fine option for non MPI jobs. Can we merge this for now and open an issue on making this MPI-friendly?

Can you add a comment or two on how this works? i.e. what should the file be named, how it should work? MPI limitations?


feat: v0.12

This is a PR for the base branch of some new changes involving config updates. Currently, there's nothing to be reviewed here. I'll open a few PRs against this branch so we can keep things moving without merging to main.
Requirements from @alexbouchardd:
Scope:

[ ] Remove --api-key flag
[ ] Change hookdeck ci to take the project api key as param so hookdeck ci some-key (we can keep --api-key on this command just for backward compatibility, not document it and print a warning)
[ ] Change hookdeck login to accept an optional cli key as param so hookdeck login some-key
[ ] Add a warning when using --cli-key  thats it’s deprecated and login with hookdeck login some-key and remove it from the documentation
[ ] Change config terminology from api_key to cli_key and  workspace_ to project_
[ ] Fix the issue with hookdeck login --cli-key abcxyz if already logged in. It should replace your current credentials for the current profile

Other tasks related to project management that may or may not be included in this PR:
CLI

[ ] Support a --project_id flag
[ ] Allow non-interactive use of hookdeck project use by allowing passing a project id hookdeck project use tm_123

Dashboard (not related to this PR)

[ ] Expose the project_id in the project settings
[ ] Add CLI key management UI

Prefer flags over optional args
This means login should take a cli-key flag and not an optional arg. ci should take an api-key (see next point). We don't presently have a CLI style guide, but there's the reasoning: https://devcenter.heroku.com/articles/cli-style-guide#flags
project use <project_id> may be different because the use terminology implies another parameter is effectively required, as does the following interactive functionality currently in place.
Consistent flag casing
project_id should be project-id as a flag. project_id is probably accurate for the config file.
hookdeck ci still takes an API Key
AFAICT hookdeck ci still takes an API Key, not a CI Key. It then uses the API Key to generate a CI Key. So, we should keep the api-key flag and terminology because it is accurate.
Discussion: CI Key management in the CLI?
hookdeck ci allows for the creation of a CLI key. Why not more directly support the creation (and eventual deletion) of CI Keys from the CLI using an API Key.
This also removes the dependency on the UI change but may require an API endpoint that supports CLI Key deletion (which would be required by the UI change anyway).

Thanks for writing these out, super clear and we're on the same page but you make things very clear here!

hookdeck ci allows for the creation of a CLI key. Why not more directly support the creation (and eventual deletion) of CI Keys from the CLI using an API Key.

This is a very interesting idea. I do want to clarify that we may want to manage not just "ci key" but general "cli key" as there's a slight difference between the 2. But I do think it may make a lot of sense that we support this functionality from the CLI.
Is this a sufficient solution for the security audit, @alexbouchardd?

Thanks for writing these out, super clear and we're on the same page originally but you make things very clear here!

hookdeck ci allows for the creation of a CLI key. Why not more directly support the creation (and eventual deletion) of CI Keys from the CLI using an API Key.

This is a very interesting idea. I do want to clarify that we may want to manage not just "ci key" but general "cli key" as there's a slight difference between the 2. But I do think it may make a lot of sense that we support this functionality from the CLI.
Is this a sufficient solution for the security audit, @alexbouchardd?

Ah, sorry, I do mean "CLI Keys".

Given that you'd be authenticated with specific CLI keys, doesn't it seem odd that you could delete other keys with it?
There are two distinct considerations here:
hookdeck ci generated keys are not bound to any user. From a user perspective they are not aware that any CLI keys exist and that leads me to think we shouldn't be generating CLI keys at all and use the actual API key as credential
hookdeck login assigns a CLI key, which shouldn't grant you access to delete other CLI keys. That seems better suited to the UI where you can generate a CLI client (which gives a key) and delete clients (which invalidates the key)

I think of it more like $ hookdeck login is an authentication mechanism. CLI key is just implementation details. After a user has logged in, their requests using the CLI key are operations made by the user. And as a user, they should be able to revoke other sessions (delete other CLI keys), and therefore I don't see that as a problem.
It's the same when folks use session tokens or something like that for the web, right? Once logged in, using one session token, a user can delete other session tokens.

CLI Key management would need to be authenticated with an API Key. This is the same way that hookdeck ci has to take an API Key in order to generate a CLI key. Or, that's my understanding of how it works. So, hookdeck ci is effectively generating a CLI Key and doing a hookdeck cli-key create (made-up command for effect) already.

CLI Key management would need to be authenticated with an API Key.

I don't think this is the right model because we're mixing scope here.
API key: project scope, it only knows about 1 project and manage resources of that project
CLI key: user scope, it has access to everything the user has access to, so if a user is in multiple organizations with multiple projects, it can manage all of those
Why would API key be able to manage CLI key?
Regarding hookdeck ci:
API key: project scope
CI key: also project scope, so only manage resources from that project. It can be used to make a few extra calls that API keys can't. Those endpoints are related to CLI like creating CLI sessions, for example.
But because the auth context is the same, API key can manage the CI key.

@alexluong - do we need to re-write some of the issue description to reflect the above discussions?
Scope:

[ ] Remove --api-key flag

I think we're good with the above.

[ ] Change hookdeck ci to take the project api key as param so hookdeck ci some-key (we can keep --api-key on this command just for backward compatibility, not document it and print a warning)

Despite my comment about preferring flags over args, I think this is a required arg so makes sense.

[ ] Change hookdeck login to accept an optional cli key as param so hookdeck login some-key
Add a warning when using --cli-key thats it’s deprecated and login with hookdeck login some-key and remove it from the documentation

If we add this, it should be a flag.
However, I'm actually unsure how this works and where it's used. Does it set the cli_key in the config (see below) and then perform a login with it to get the CI key?

[ ] Change config terminology from api_key to cli_key and workspace_ to project_

All good.

[ ] Fix the issue with hookdeck login --cli-key abcxyz if already logged in. It should replace your current credentials for the current profile

I don't know of this problem, but makes sense.


Fixed issue #1

Thanks for your PR! :+1:
Looks like the docs suggest one should simply call readline_callback_handler_install() again in order to redraw the prompt and the readline_callback_handler_remove() call can be avoided: http://php.net/manual/en/function.readline-callback-handler-install.php
I'd love to get this in, can you confirm this / update your PR and fix the indentation? :shipit:

Ping @davidwdan, any updates? :+1:

@clue sorry, I missed your comment.  I'll take a look at this later tonight.

ping @clue

Unfortunately, the new array syntax break compatibility with PHP 5.3 (yeah, I know…).
Can you revert this to use the explicit array syntax instead and squash all changes into a single commit? :shipit:

done

Much appreciated! :shipit:


Output to a new tab crashes browser

When there are many images (about 25 and more), output to a new tab doesn't work. Instead, browser crashes (chrome).
Browser crashes in both cases:
doc.output('dataurlnewwindow');
and
var string = doc.output('datauristring');
var x = window.open();
x.document.open();
x.document.location=string;

Seeing as this bug is still present in Chrome, your recommended solution works very well.
var blob = pdf.output("blob");
window.open(URL.createObjectURL(blob));

This doesn't work for me at all @Samyoul & @diegocr . I've built a "converter engine"  that converts to a Uint8Array and then directly with btoa to a base64 image so I don't need to load the heavy canvas. However it is still too heavy for like 60+ pages and the whole thing crash now and then.
I'm handling a lot of data and the frustrating part is that things work fine when you start developing with just a few pages and the more you get, the more problems you have.

If html has a image that src is 'data:image/svg+xml;base64,' then the browser will be crash.

I was having the same issue but found a solution in issue #359.  As that issue suggests, Chrome doesn't crash is you use JPEG instead of PNG.  The only issue that I ran into with using JPEG is that there is no transparency so I had to be sure to change the canvas background to white in order to avoid a black background.
This was easily done by following @Nd60's suggestion in issue #247.
Hope this helps somebody in the future.


FOR-34: Implement response piping for Web SDK

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix upcast -> downcast

Should be "downcast" instead of "upcast".
Thanks for building Matchstick!

Hey, thanks for the PR. Although you are generally correct about upcasting being casting to a parent and downcasting being casting to a child, the reason we have left it as upcasting in the docs is because the common error people run into in their subgraphs is when they try to cast in the following way: let newGravatarEvent = newMockEvent() as NewGravatar which although technically downcasting throws the following error in AssemblyScript: Mapping aborted with message: unexpected upcast. And we want people to associate that part of the docs with this error.

Thanks for the explanation! Yeah, apparently AssemblyScript is making the same mistake.
I created an issue there (https://github.com/AssemblyScript/assemblyscript/issues/2422) and made a PR to fix it (https://github.com/AssemblyScript/assemblyscript/pull/2423).

The AssemblyScript compiler has been fixed, including the error message: https://github.com/AssemblyScript/assemblyscript/pull/2423.

The AssemblyScript compiler has been fixed, including the error message: AssemblyScript/assemblyscript#2423.

Great, the only thing remaining is that the new version with this fix crashes the wasm file compilation. I'll try to check it out next week.

Great, the only thing remaining is that the new version with this fix crashes the wasm file compilation

Do you have exported mutable globals in such wasm modules? Binaryen introduced new pass which has one minor issue with such globals. It should be fixed in new version of Binaryem:
https://github.com/AssemblyScript/assemblyscript/pull/2461

I'm closing this PR 😐 The reason is because this change will only be helpful for people using AssemblyScript 0.20.x+ and as of now that doesn't seem like the direction the Graph is heading in. My guess is that unless something extremely useful or necessary for the Graph is added in future versions of AS, they will probably just stick to version 0.19.10.
The reason the version is such a big problem is that parts of graph-ts do not compile with the newer versions of AS which will force all subgraph developers to have their AS version be inherited from graph-ts.
Needless to say if they decide to update their AS version this change will be enacted.
Thanks for the PR again.


Allow creating Button with attached Menu

Feature Request
Allow creating Button with attached Menu. The functionality should follow ARIA Navigation Menu example with regards to the rendered DOM structure and keyboard handling. The only difference is that the menu should not be opened on hover, but on click.
Requirements

menu open on enter/space and focus goes to first item in menu
-(Optional) Down Arrow: opens the menu and moves focus to the first menu item.
-(Optional) Up Arrow: opens the menu and moves focus to the last menu item.
menu is closed on esc key and focus goes back to the button
if he press TAB key, focus goes naturally to next focusable element after menu and menu is closed
if he press shift+tab key focus goes naturally to previous focusable element and menu is closed.
able to do position of menu the same as for popup

DOM structure

  <button id="menubutton"
          aria-haspopup="true"
          aria-controls="menu2">
    WAI-ARIA Quick Links
  </button>

        W3C Home Page

Based on the discussions, providing reasons why we should use Button and Menu component for this use case and not a Dropdown:

Dropdown in our case renders a List (role list) and ListItem (role listitem). Dropdown is used when you need to select a value. In this case, you do not select a value, but you choose an item from the menu.

Styling from dropdown also does not apply - the menu should look exactly like the Menu that we already have. It should not look like the options that are rendered by Dropdown.

From focus handling point of view, Dropdown is not focusing the items, the focus stays on the List. For Menu, we need to focus the menu items.

Menu also allows us to use submenu. Dropdown does not have this possibility.

For accessibility, Dropdown is adding logic to announce the selected item and the amount of selected items. This should not be the case for the Menu inside of the Button.


Updates to TCGA Classify Module

Three files are changed (including the utility file) and two files are added. The first new file performs the analysis on raw gene expression data (for cancer-type and gene predictions). The second file is the bash script that runs the full pipeline.
The largest change is fixing a bug that leaked copy number info into non oncogene and tumor suppressor genes. This fixes the bug. Another big change is that I am now saving the classification metrics per gene or cancer-type. This allows a user to restart analyses without having to worry about losing too much data

I couldn't really follow from the script how you are checking to make sure that you have fixed this leak?

The addition of this function argument


test: output_strictly_contains check leads to non-deterministic test failures

Which jobs are failing:
tests/integration-static
Which test(s) are failing:
stdout_output_strict, stdout_output_json_strict
Test link:
https://github.com/falcosecurity/falco/blob/2a8c0e8bb7ba5ea2d4fa99913257fc32955d718d/test/falco_tests.yaml#L675
https://github.com/falcosecurity/falco/blob/2a8c0e8bb7ba5ea2d4fa99913257fc32955d718d/test/falco_tests.yaml#L686
Reason for failure:
The output_strictly_contains check ensures that the expected output (read from a file) is contained in the actual Falco's output by using simple string inclusion comparison (if expected not in actual: self.fail(...)). As such, the test is fragile and can fail if even a single character in the actual output breaks the pattern of the expected string.
Since merging https://github.com/falcosecurity/falco/pull/1451, alerts are written on the outputs by an additional worker thread. While running integration tests, it may happen that the main thread terminates before the last alert has been emitted by the working thread. As such, Falco's termination message Events detected: ... Rule counts by severity: ... may be written on stdout before the last alert.
In this specific scenario, output_strictly_contains fails because the termination message appears in the middle of the output, thus not matching the expected string. This only happens while checking the stdout output. This is not deterministically reproducible, and happens in execution environments with poor computation resources.
Anything else we need to know:
The tests/integration-static job occasionally fails on CircleCI. Failures related to this issue have an error message like the following:
Output 'stdout' does not strictly contains the expected content 'output_files/single_rule_with_cat_write.json'

An example of this failure is visible in: https://app.circleci.com/pipelines/github/Spartan-65/falco/3/workflows/44b81732-5123-47f5-9642-d56708092bd2/jobs/37/parallel-runs/0/steps/0-103
The log lines containing the corrupted output, and the error, are reported below:
04:21:35 DEBUG| [stdout] {"output":"2016-08-04T16:17:57.881781397+0000: Warning An open was seen (command=cat /dev/null)","priority":"Warning","rule":"open_from_cat","time":"2016-08-04T16:17:57.881781397Z", "output_fields": {"evt.time.iso8601":1470327477881781397,"proc.cmdline":"cat /dev/null"}}
04:21:35 DEBUG| [stdout] {"output":"2016-08-04T16:17:57.881785348+0000: Warning An open was seen (command=cat /dev/null)","priority":"Warning","rule":"open_from_cat","time":"2016-08-04T16:17:57.881785348Z", "output_fields": {"evt.time.iso8601":1470327477881785348,"proc.cmdline":"cat /dev/null"}}
04:21:35 DEBUG| [stdout] {"output":"2016-08-04T16:17:57.881796705+0000: Warning An open was seen (command=cat /dev/null)","priority":"Warning","rule":"open_from_cat","time":"2016-08-04T16:17:57.881796705Z", "output_fields": {"evt.time.iso8601":1470327477881796705,"proc.cmdline":"cat /dev/null"}}
04:21:35 DEBUG| [stdout] {"output":"2016-08-04T16:17:57.881799840+0000: Warning An open was seen (command=cat /dev/null)","priority":"Warning","rule":"open_from_cat","time":"2016-08-04T16:17:57.881799840Z", "output_fields": {"evt.time.iso8601":1470327477881799840,"proc.cmdline":"cat /dev/null"}}
04:21:35 DEBUG| [stderr] Driver Events:0
04:21:35 DEBUG| [stderr] Driver Drops:0
04:21:35 DEBUG| [stderr] Elapsed time: 0.001, Captured Events: 14, 13397.13 eps
04:21:35 DEBUG| [stderr] Syscall event drop monitoring:
04:21:35 DEBUG| [stderr]    - event drop detected: 0 occurrences
04:21:35 DEBUG| [stderr]    - num times actions taken: 0
04:21:35 DEBUG| [stdout] Events detected: 8
04:21:35 DEBUG| [stdout] Rule counts by severity:
04:21:35 DEBUG| [stdout]    WARNING: 8
04:21:35 DEBUG| [stdout] Triggered rules by rule name:
04:21:35 DEBUG| [stdout]    open_from_cat: 8
04:21:35 DEBUG| [stdout] {"output":"2016-08-04T16:17:57.882003104+0000: Warning An open was seen (command=cat /dev/null)","priority":"Warning","rule":"open_from_cat","time":"2016-08-04T16:17:57.882003104Z", "output_fields": {"evt.time.iso8601":1470327477882003104,"proc.cmdline":"cat /dev/null"}}
04:21:35 DEBUG| [stdout] {"output":"2016-08-04T16:17:57.882008208+0000: Warning An open was seen (command=cat /dev/null)","priority":"Warning","rule":"open_from_cat","time":"2016-08-04T16:17:57.882008208Z", "output_fields": {"evt.time.iso8601":1470327477882008208,"proc.cmdline":"cat /dev/null"}}
04:21:35 DEBUG| [stdout] {"output":"2016-08-04T16:17:57.882045694+0000: Warning An open was seen (command=cat /dev/null)","priority":"Warning","rule":"open_from_cat","time":"2016-08-04T16:17:57.882045694Z", "output_fields": {"evt.time.iso8601":1470327477882045694,"proc.cmdline":"cat /dev/null"}}
04:21:35 DEBUG| [stdout] {"output":"2016-08-04T16:17:57.882054739+0000: Warning An open was seen (command=cat /dev/null)","priority":"Warning","rule":"open_from_cat","time":"2016-08-04T16:17:57.882054739Z", "output_fields": {"evt.time.iso8601":1470327477882054739,"proc.cmdline":"cat /dev/null"}}
04:21:35 INFO | Command '/build-static/release/userspace/falco/falco -r /source-static/falco/test/rules/single_rule.yaml   -c /source-static/falco/test/confs/stdout_output.yaml -e /build-static/release/test/trace_files/cat_write.scap -o json_output=True -o json_include_output_property=True -o priority=debug -v -o time_format_iso_8601=true' finished with 0 after 0.20952129364013672s
04:21:35 DEBUG| Expected warning rules: set()
04:21:35 DEBUG| Actual warning rules: set()
04:21:35 ERROR|
04:21:35 ERROR| Reproduced traceback from: /root/.local/lib/python3.7/site-packages/avocado/core/test.py:844
04:21:35 ERROR| Traceback (most recent call last):
04:21:35 ERROR|   File "/source-static/falco/test/falco_test.py", line 684, in test
04:21:35 ERROR|     self.check_output_strictly_contains(res)
04:21:35 ERROR|   File "/source-static/falco/test/falco_test.py", line 414, in check_output_strictly_contains
04:21:35 ERROR|     output['actual'], output['expected']))
04:21:35 ERROR|   File "/root/.local/lib/python3.7/site-packages/avocado/core/test.py", line 1030, in fail
04:21:35 ERROR|     raise exceptions.TestFail(message)
04:21:35 ERROR| avocado.core.exceptions.TestFail: Output 'stdout' does not strictly contains the expected content 'output_files/single_rule_with_cat_write.json'

@jasondellaluce: There is not a label identifying the kind of this issue.
Please specify it either using /kind <group> or manually from the side menu.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/kind failing-test

Fixed by: https://github.com/falcosecurity/falco/pull/1724


Update geometry attribute names

Status:

Right now we use: "index", "positions", "normals", "texcoords".
ThreeJS uses: "index", "position", "normal", "uv".

I think we should be consistent about singular vs plural form. But I prefer plural for the names of the buffers/attributes, and singular inside the shader. This is also more intuitive when using such a buffer as a storage buffer, where in the shader you actually sample from the buffer.
I also prefer "texcoords" over "uv", we're also not calling position "xyz".
This should be quick fix, but Leaving this open for a bit so others can respond.

To be clear, my suggestion is: "indices", "positions", "normals", "texcoords".

Any idea what terms gltf uses?

Any idea what terms gltf uses?

From the big gltf overview image, it looks like they use "indices", and "attributes", and then POINT and NORMAL are accessors (pointers?) to the data for points and normals. Its a bit centric to how the data is stored. Anyway, they use plural "indices" ...


Modified CVE-2015-1236

Edited CVE-2015-1236

Please make sure travis tests pass otherwise the PR can't be merged.

5 upvotes for CVE-2015-1236


Feat/table

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Vim errors out on opening the file

Get the following when trying to run vim:
same happens when no file specified.
gvim also errors out.
$ vim .\service-worker.js
Program 'vim.exe' failed to run: Access is deniedAt P:\Scoop\shims\vim.ps1:3 char:68
+ ... ion.expectingInput) { $input | & $path @args } else { & $path @args }
+                                                           ~~~~~~~~~~~~~.
At P:\Scoop\shims\vim.ps1:3 char:68
+ ... ion.expectingInput) { $input | & $path @args } else { & $path @args }
+                                                           ~~~~~~~~~~~~~
+ CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
+ FullyQualifiedErrorId : NativeCommandFailed

My bet is that you either have an eager anti-virus or something caused ACL corruption for the file entries affected. I tried to reproduce this and I cannot.

you might be correct, after fresh reinstall, it errored out in a different way, this time pointing out the antivirus as a possible cause, I am closing the Issue


Vizzu logo on the chart should point to ipyvizzu github repo

will point to vizzuhq.com. should be changed in vizzu-lib

done


rspec route_to in routing specs

I have been trying to integrate this SO post https://stackoverflow.com/questions/11436924/rspec-add-some-header-requests-inside-routing-specs/16467507#16467507 but no matter what I try this does not work.  Do you have any ideas?
# frozen_string_literal: true

require 'rails_helper'

RSpec.describe 'Status Routes', type: :routing do
  context 'v1' do
    it '/status-api' do
      expect(get('/status-api')).to route_to('v1/monitors#status')
    end
  end

  context 'v2' do
    before do
      ActionDispatch::TestRequest::DEFAULT_ENV.dup
      ActionDispatch::TestRequest::DEFAULT_ENV['X-API-VERSION'] = 2
    end

    it '/status-api' do
      expect(get('/status-api')).to route_to('v2/monitors#status')
    end

    after do
      ActionDispatch::TestRequest::DEFAULT_ENV.delete('X-API-VERSION')
    end
  end
end

  api_version(module: 'v1', header: { name: 'X-API-VERSION', value: '1' }, default: true) do
    get '/status-api', to: 'monitors#status'
  end

  api_version(module: 'v2', header: { name: 'X-API-VERSION', value: '2' }) do
    get '/status-api', to: 'monitors#status'
  end

@chrishough as you'll note in that example on SO, headers within Rack get translated internally. They get uppercased, underscored, and prefixed with HTTP. So for example in the versionist specs, we test custom headers like so:
https://github.com/bploetz/versionist/blob/master/spec/api_routing_spec.rb#L316
https://github.com/bploetz/versionist/blob/master/spec/api_routing_spec.rb#L338
So try changing your ActionDispatch::TestRequest::DEFAULT_ENV['X-API-VERSION'] to ActionDispatch::TestRequest::DEFAULT_ENV['HTTP_X_API_VERSION'] and see if that does the trick?

1st, thank you so much for your help on this.  I truly appreciate it.
If I try with @headers["HTTP_API_VERSION"]  I get...
Failures:

  1) Status Routes v2 /status-api
     Failure/Error: @headers["HTTP_API_VERSION"] = 2

     NoMethodError:
       undefined method `[]=' for nil:NilClass
     # ./spec/routing/status_routes_spec.rb:19:in `block (3 levels) in <top (required)>'

Top 2 slowest examples (0.04982 seconds, 20.2% of total time):
  Status Routes v1 /status-api
    0.03431 seconds ./spec/routing/status_routes_spec.rb:7
  Status Routes v2 /status-api
    0.01551 seconds ./spec/routing/status_routes_spec.rb:18

Finished in 0.24634 seconds (files took 17.69 seconds to load)
2 examples, 1 failure

If I try with ActionDispatch::TestRequest::DEFAULT_ENV['HTTP_X_API_VERSION'] I get...
Failures:

  1) Status Routes v2 /status-api
     Failure/Error: expect(get('/status-api')).to route_to('v2/monitors#status')

       The recognized options <{"controller"=>"v1/monitors", "action"=>"status"}> did not match <{"controller"=>"v2/monitors", "action"=>"status"}>, difference:.
       --- expected
       +++ actual
       @@ -1 +1 @@
       -{"controller"=>"v2/monitors", "action"=>"status"}
       +{"controller"=>"v1/monitors", "action"=>"status"}
     # ./spec/routing/status_routes_spec.rb:19:in `block (3 levels) in <top (required)>'

Thoughts?

@chrishough sorry, didn't mean to confuse the situation by pointing you at the @headers thing (that's a request spec thing I believe), I only wanted to point out the API-VERSION -> HTTP_API_VERSION translation there.
Anyhoo, with the ActionDispatch::TestRequest::DEFAULT_ENV change, it looks like it's returning your default API version, which is why your spec is failing, so clearly that's not working either. Honestly I've never tried to use HTTP headers routing specs before, so I'm not sure how to do this. Some quick googling seems to indicate this may not even be possible?
Worst case, maybe just move your routing specs to request specs where you CAN specify headers?

not a problem @bploetz, I was wondering if there was a way to make this work.  More of an experiment before changing these specific specs to request specs, or skipping the route specs all together in this exercise. thoughts?

I mean, given the power of Ruby there's GOTTA be a way to make this work in routing specs, but I'd have to spend some time playing with it to find the secret sauce.
Regardless, this doesn't sound like a problem with versionist per se, so I'm going to close this issue, but feel free to keep updating this issue if/when you figure out how to get it working so others may benefit in the future.

For others coming across this, I moved the specs to request specs and just tested the status codes.
Example...
# frozen_string_literal: true

require 'rails_helper'

RSpec.describe 'Monitors', type: :request do
  before { get '/status-api', headers: { 'X-API-VERSION': '2' } }

  it 'renders status' do
    expect(response.body).to include(JSON.generate(version: '2', status: 'online'))
  end

  it 'schema' do
    expect(response).to match_response_schema('app_monitors_status')
  end

  it 'renders 200 status code' do
    expect(response.status).to be(200)
  end
end


Replay not working

I'm playing RTMP URL, after the video completion, when I click re-play button, the player is not replaying the video.

can u give the url ?

This is the URL I'm trying to play
rtmp://streamtube.streamhash.com:1935/vodst2/8a7948b4db40f4c766278f2dce83792f1ad31d1b.mp4

it seems the seek action does not work,but there is another way to fix the promble
videoView.setPlayerListener(new DefaultPlayerListener() {
            @Override
            public void onCompletion(GiraffePlayer giraffePlayer) {
                giraffePlayer.release();
            }
        });

this code will release the player when completion，and create a new player when restart playing

Thanks it works..!!


New version: GMT v0.30.1

Registering package: GMT
Repository: https://github.com/GenericMappingTools/GMT.jl
Created by: @joa-quim
Version: v0.30.1
Commit: d1fd42c9e24cc76fd56051a8b3f3812eca31cb21
Reviewed by: @joa-quim
Reference: https://github.com/GenericMappingTools/GMT.jl/issues/532

@joa-quim :point_up: Also,
[noblock]

Superseded by #30927


camera entity state "idle" when printer is off

Version of the moonraker integration
0.9.0
Describe your setup
Klipper+Mainsail running on RPIZero with CR10S-Pro
Describe the bug
The camera entity in the integration is always reporting "idle" status even if the printer (and the RPIZero) is off.
Moonraker Logs

What would you expect to get as a value?

@marcinbauer85 What would you expect to get as a value?


Encapsulate the internal mutation of the type checker

Most methods of the type checker are mutating because nearly all operations are lazy, to deal with forward and recursive references. Unfortunately, that makes the type checker harder to use and reason about.
If we look more closely at the checker's implementation, we distinguish two kinds of methods.

The checkXXX methods take an AST node and verify if it is well typed. Those are eventually called on every node as the AST is walked.
Other methods compute some properties about a node or a type.

All of these methods may update the property maps of the type checker (i.e., the type annotations that are attached to a program once type checking/inference is done) as well as some internal memoization caches. That's why they are all mutating.
It is not immediately obvious why a method like conformedTraits(of:in:) has to be mutable. It's only after we look at its body and notice that it is initiating type checking of some declarations to compute its result, thus causing internal mutation. Further, the caller does not care whether or not the checker updated its state; it only wants a set of traits. So the fact that computing such a set causes mutation is arguably an implementation detail. That is in contrast with a method like check(module:) which promises to update property maps.
Another important observation is that property maps are modified monotonically. For example, declTypes is only changed by extending it with new key-value pairs. So I think it's actually possible to reason about "concurrent" mutation of these property maps, which is encouraging because it means there's likely a sane and principled way to parallelize the type checker.
It also means that property maps could be implemented as shared mutable objects (e.g., with Dave's Utils.SharedMutable) so that the checker's methods no longer have to be mutating. The only property that has to be upheld is that all nodes must be eventually checked, thus ensuring that the property maps are "complete".

Using SharedMutable instead of treating these property maps as parts and just using mutation directly would probably create a large efficiency hit, as closures need to be created, passed to dispatch, and potentially queued, for every access.  The uniqueness checks currently in play are comparatively very cheap.  SharedMutable is only reasonable for files because we don't create new files from their names all that often.
Also, the property maps are associated with a particular set of modules, so it's not like they can be shared globally; that implies an additional layer of lookup.
We don't yet have a great way to model fine-grained access to shared resources in a value-semantic universe, and I wouldn't be too sanguine about our ability to hide the mutation that's actually there, at least not without some new ideas.  Remember that encoding mutation in the type system is part of the glue holding the soundness of the system together.
Incidentally, this is the sort of thing Swift actors are supposed to encode, but then you have to buy into the whole async/await package.

I think there's a way to make shared monotonic mutation fit the model, but I do think the model needs to be extended to do that. I wonder how many of the well-understood cases of shared mutation are (or can be viewed as) monotonic. Also note those closures are non-escaping so costs might not be as bad as I presume. We should measure of course!

Implemented by #845.


Rename HasSchematic

HasSchematic and HasSchematicImpl should be renamed to something more indicative of their function.

Fixed by #226


magma build failure on x86_64-linux as of 98d778f0

Issue description
Build of magma failed on x86_64-linux as of 98d778f0151f93ea9bf58c17917cc41dc9f535ac. This is currently breaking python3Packages.wandb.
error: builder for '/nix/store/pbsidzrp3apddiydhzds7m8hh3zsiczj-magma-2.7.2.drv' failed with exit code 1;
       last 10 log lines:
       > FAILED: CMakeFiles/magma.dir/control/abs.cpp.o
       > /nix/store/kp1ds8v0igyma875qf08fi26i4vxv7k2-gcc-wrapper-12.3.0/bin/c++  -I/build/magma-2.7.2/build/include -I/build/magma-2.7.2/include -I/build/magma-2.7.2/control -I/build/magma-2.7.2/magmablas -I/build/magma-2.7.2/sparse/include -I/build/magma-2.7.2/sparse/control -I/build/magma-2.7.2/testing -std=c++11 -fopenmp -Wall -Wno-unused-function -O3 -DNDEBUG -MD -MT CMakeFiles/magma.dir/control/abs.cpp.o -MF CMakeFiles/magma.dir/control/abs.cpp.o.d -o CMakeFiles/magma.dir/control/abs.cpp.o -c /build/magma-2.7.2/control/abs.cpp
       > In file included from /build/magma-2.7.2/include/magma_lapack.h:14,
       >                  from /build/magma-2.7.2/control/magma_internal.h:64,
       >                  from /build/magma-2.7.2/control/abs.cpp:8:
       > /build/magma-2.7.2/include/magma_mangling.h:32:10: error: #error "One of ADD_, NOCHANGE, or UPCASE must be defined to set how Fortran functions are name mangled. For example, in MAGMA, add -DADD_ to CFLAGS, FFLAGS, etc. in make.inc. If using CMake, it defines MAGMA_GLOBAL instead."
       >    32 |         #error "One of ADD_, NOCHANGE, or UPCASE must be defined to set how Fortran functions are name mangled. For example, in MAGMA, add -DADD_ to CFLAGS, FFLAGS, etc. in make.inc. If using CMake, it defines MAGMA_GLOBAL instead."
       >       |          ^~~~~
       > [7/3430] Building CXX object CMakeFiles/magma.dir/control/constants.cpp.o
       > ninja: build stopped: subcommand failed.
       For full logs, run 'nix log /nix/store/pbsidzrp3apddiydhzds7m8hh3zsiczj-magma-2.7.2.drv'.
error: 1 dependencies of derivation '/nix/store/cfv8602mp11cs1z58v3z4wnkq4blajmg-python3.11-torch-2.1.2.drv' failed to build
error: 1 dependencies of derivation '/nix/store/11j9azay3m8dmqnkg4nap32pnhj1mjpc-python3.11-wandb-0.16.0.drv' failed to build

full build log
python3Packages.wandb maintainers cc: @samuela
magma maintainers cc: @connorbaker
Other cc: n/a
Steps to reproduce

Checkout nixpkgs at commit 98d778f0151f93ea9bf58c17917cc41dc9f535ac
Run nix-build -A magma

Technical details
 - system: `"x86_64-linux"`
 - host os: `Linux 6.2.0-1018-azure, Ubuntu, 22.04.3 LTS (Jammy Jellyfish), nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.16.1`
 - nixpkgs: `/nix/store/ikf487a0fs41s20x64jhgv2a2rl40zf3-source`

Contents of ~/.config/nixpkgs/config.nix:
{ allowUnfree = true; cudaSupport = true; cudaCapabilities = ["8.0"]; }

Misc.
This issue was automatically generated by nixpkgs-upkeep.

CI workflow that created this issue.
Internal tags:<PHONE_NUMBER>741765930<PHONE_NUMBER>58869953

dup of https://github.com/NixOS/nixpkgs/issues/281656


P2505: Add monadic inteface extensions for std::expected

Is your feature request related to a problem? Please describe.
P0323 is currently missing P2505 which is considered as a bug. (Relevant discussions: https://github.com/cplusplus/papers/issues/1161)
Describe the solution you'd like
Expand STL implementation to support P2505.
Additional context
For example, given the following:
using time_expected = expected<boost::posix_time::ptime, std::string>;

time_expected from_iso_str( std::string time )
{
  try {
    ptime t  = boost::posix_time::from_iso_string( time );
    return t;
  }
  catch( std::exception& e )
  {
     return unexpected( e.what() + " str was: "s + time);
  }
}

// for use with transform
ptime next_day( boost::posix_time::ptime t )
{
   return t + boost::gregorian::days(1);
}

// for use with or_else
void print_error( std::string error )
{
   cout << error << endl;
}

//valid iso string
const std::string ts ( "20210726T000000" );

Before the change we'd write this:
time_expected d = from_iso_str( ts );
if (d)
{
   ptime t = next_day( *d );
}
else
{
   print_error( d.error() );
}

And after, this:
// chain a series of functions until there's an error
auto d = from_iso_str ( ts )
               .or_else( print_error )
               .transform( next_day ) ;

Er... what? Have you got the right repo? muu doesn't have std::expected implementation O_O

Unless you're suggesting I add one, in which case, let me introduce you to: tl::expected 😄

Er... what? Have you got the right repo? muu doesn't have std::expected implementation O_O

Oops, I was in a hurry and just noticed that the original text was deleted! This is a feature request to add muu::expected following the default implementation ( so no deviation like tl ) but with P2505 adapted :)

so no deviation like tl

This one is cited in the paper as being a 'standard' implementation of both proposals, might be closer to what you want: https://github.com/RishabhRD/expected

so no deviation like tl

This one is cited in the paper as being a 'standard' implementation of both proposals, might be closer to what you want: https://github.com/RishabhRD/expected

That's really neat! Sound like a good replacement

Closing in favor of rd, reopen if necessary ( :


Use cheaper line driver IC, e.g. 74ALVC164245DGG

Describe the issue
Consider using the 74ALVC164245DGG as a line driver IC.
It can sink/source 50mA, but this value is probably for the whole chip and not a single I/O.
Instead of 8 I/Os it has 16 I/Os, that means less chips are needed.
When producing the boards at JLCPCB the chips cost around 0,50 Euro each (https://jlcpcb.com/parts/componentSearch?isSearch=true&searchTxt=74ALVC164245DGG)
This reduces the chip cost from 4x3=12 Euro to 2x0,50=1 Euro
They do level shifting.
I'm not sure if they are electrically appropriate.

started work here in this branch: https://github.com/nospam2000/RASCSI/tree/fix_issues
still work in progress, just finished component placement so that autorouter works

Unfortunately SCSI needs a Open Drain (Open Collector) driver but 74ALVC164245DGG is push/pull, so this will not work.


chore(build): use fixed version of yarn

Use fixed versoin of Yarn v3 in the project. See #70

this is doing a similar thing as in #70 , right?

@lhein This is what I think should be done instead of #70.

See comment here -> https://github.com/hawtio/hawtio-next/pull/70#issuecomment-1413355143


[Enhancement] (nereids)implement CreateRoleCommand in nereids

Search before asking

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

Description
CreateRoleCommand is supported in legacy planner but not in nereids(new doris fe planner). you need implement it in nereids.
The DorisParser.g4 has the syntax definition already(see bellow). And you can check CreateRoleStmt.java in legacy planner to see what the command does and migrate it to nereids planner
 unsupportedCreateStatement: CREATE ROLE (IF NOT EXISTS)? name=identifier (COMMENT STRING_LITERAL)?
Solution
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

i will pick it


allow boto3 as a HTTP data (range) provider

If the httpx client to S3 compliant bucket as abstracted just a bit and its own class,
AWS boto3 could be swapped in when needed.
I am starting working on such an abstraction in the repo / branch
https://github.com/candrsn/sqlite-s3-query/tree/feature/boto3_client
It is not ready for a merge, but I want to start discussions before I a am ready for a PR.
The abstraction would move the current S3 API elements into a class that had minimal symmetry with the boto3 S3 client API
x = boto3.client('S3')
and also
session = boto3.Session()
s3 = session.client('s3')
That would simplifiy S3 API access methods

I'm very tempted to not make it so boto3 cannot be swapped in via an abstraction layer. This is a fairly low level library (at least as a lot of Python libraries go I think?), with what I hope is a minimal set of dependencies, and I would like to keep it that way for flexibility and performance reasons. I know it's very typical for boto3 to be required for Python code to talk to AWS, but for S3 (or an S3-compatible service), I think it's fairly unnecessary.
(I've even been thinking even about how to remove the http client as a dependency... but realistically that won't happen, at least any time soon)
But... if you really want to use this library with boto3 right now, you probably can. You just need to present an httpx-like interface via get_http_client, and convert

HEAD requests-> head_object
GET requests, extracting the versionId in its query string parameters -> get_object


feat: add function get unnamed arguments from name

Description
Follow up from https://github.com/snakemake/snakemake-wrapper-utils/pull/38#pullrequestreview-1724460262

QC

[ ] The PR contains a test case for the changes or the changes are already covered by an existing test case.
[x] The documentation (docs/) is updated to reflect the changes or this is not necessary (e.g. if the change does neither modify the language nor the behavior or functionalities of Snakemake).

Name changed nas requested. Do I need to write a test case?

Name changed nas requested. Do I need to write a test case?

That would be awesome!


AcceptDragDropPayload can't be checked for nil

AcceptDragDropPayload will return a "nil" Payload if the currently dragged item is not of the expected type. There's currently no way to check this.
Either AcceptDragDropPayload should return a nil object if the payload is nil, or the Payload type should have a way to check for nil
I.e. from the client code:
if AcceptDragDropPayload("Node") != nil {
  // handle drop
}

OR
if !AcceptDragDropPayload("Node").IsNil() {
  // handle drop
}

Confirmed as working! 🎉

hreat to hear!
But I accidently removed Payload.Data()  :smile: - will fix soon

Yeah, that didn't work before for me anyway, so my local hack was just to keep drag data in a global variable 😄

now should work


fix typo in reference for service create

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "reference_service_create_typo" git@github.com:trapier/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.


Add download/view json button in lens ui

Feature:
The regular UI has a download/view JSON button which shows you the JSON representation of the current trace. Lens doesn't have such thing.
Rational
It's super useful when debugging UI issues and it's also one of the only ways to share traces in a ticket (unless you want to manually curl the /trace endpoint)

+1 The "Upload JSON" button is less useful when there's no way to download the json.


Circular dependency?

What version of HonoX are you using?
<EMAIL_ADDRESS><EMAIL_ADDRESS>What steps can reproduce the bug?
bun create hono my-app
// select x-basic
cd my-app
bun run build

What is the expected behavior?
No warnings.
What do you see instead?
Export "use" of module "node_modules/hono/dist/jsx/hooks/index.js" was reexported through module "node_modules/hono/dist/jsx/dom/index.js" while both modules are dependencies of each other and will end up in different chunks by current Rollup settings. This scenario is not well supported at the moment as it will produce a circular dependency between chunks and will likely lead to broken execution order.
Either change the import in "node_modules/honox/dist/client/runtime.js" to point directly to the exporting module or reconfigure "output.manualChunks" to ensure these modules end up in the same chunk.

Additional information
No response

This might be a hono matter.

Regression caused by https://github.com/honojs/hono/pull/2241 changes.


Suggestion to make it easier

An option to make the process easier is to add the following code to the end of instagramhelper.js:
`chatId = window.location.href.split('/')[5]; // Gets the direct message chat id from the url
var ig  = new InstagramHelper();
ig.startUnsending(chatId);`
Then it will automatically start unsending messages for the current DM.


Rewrite most of the shell detection stuff

The goal is to fix https://github.com/pypa/pipenv/issues/915#issuecomment-387138350

Manually tested on cmd.exe, Powershell (pwsh.exe, but powershell.exe should work), and Bash in WSL. This needs more testers.

Some explaination.
I did some process-digging and it turns out there is not a trace of Cmder.exe anywhere in the process tree when _win_utils.get_shell() is called, so I removed it from SHELL_NAMES. It is not useful anyway, since we really need to know not only we’re running Cmder, but also what shell it is spawning for us.
There are quite a few variants of subshell-spawning, each requiring a different call:

Non-bash shells on non-Windows (simplest to handle).
Bash (not including Msys Bash, which never worked).
Bare cmd or Powershell (including pwsh)
cmd in Cmder
Powershell in Cmder

The logic gets complicated pretty quickly, so I decided to refactor them into five classes (plus an intermediate for the Cmder cases). _detect_shell now returns an instance of Shell (or its subclass) for shell to use.

Overall these changes make sense.  I think we are maintaining 2 lists of windows compatible shells, we should consolidate those.  Otherwise I think we can schedule this for 11.11

Note:

[ ] Make sure this does not overwrite #2168.
[ ] Generate patch.

Comment on #915


Syncing takes a long time

I just started an atuin sync after the first atuin import auto and it's been running for minutes, to sync about 10K entries.
I'd expect this to take <1 second.
I apologise for the load of issues all at once, I'm just excited (and I'd be happy to help!) :D
EDIT: Every sync request actually takes minutes, not just the first one.
I recommend you use something like a rust equivalent of  appendful, because if I understand this source (and I definitely don't claim to), the entire history is sent over on every sync.

We aren't syncing the whole history every time, we essentially maintain two cursors into history. One for the last item we have, and another for when we last synced. History is listed based on that!
It does occasionally have issues though, and I haven't been able to narrow down why. I've been meaning to replace the current sync with something more calendar-based, which would be much more reliable! Just need to get the time 😅
It's probably doing this because there's more on the remote than you have locally, so it's trying to resolve it. Maybe try passing the --full flag to a sync and see if that resolves it?

This has taken much longer to sort than I expected, but it should now be resolved as of the latest main. I've deployed this to the public server too, so you should notice improvement there! I'll be continuing to work on this to ensure syncing is rapid :D


Websocket connection does not work between envoy sidecars

Hi, I am trying to do a simple WS example which includes front-envoy and service1. The service1 is a WS server coupling with an envoy sidecar. front-proxy is for passing through the WS request to service1. I use the new version to configure WS with upgrade_type: websocket. It works when a WS client sends a request to the envoy sidecar of service1, but it does not work when sending request to front-proxy. It return handshake status 503. Below are the envoy files, and I use the envoy-alpine:lastest image.
Config envoy for front-proxy:
static_resources:
  listeners:
  - address:
      socket_address:
        address: <IP_ADDRESS>
        port_value: 80
    filter_chains:
    - filters:
      - name: envoy.http_connection_manager
        config:
          upgrade_configs:
          - upgrade_type: websocket
          codec_type: auto
          stat_prefix: ingress_http
          route_config:
            name: local_route
            virtual_hosts:
            - name: backend
              domains:
              - "*"
              routes:
              - match:
                  prefix: "/service1"
                route:
                  cluster: service1
          http_filters:
          - name: envoy.router
            config: {}
  clusters:
  - name: service1
    connect_timeout: 0.25s
    type: strict_dns
    lb_policy: round_robin
    http2_protocol_options: {}
    hosts:
    - socket_address:
        address: service1
        port_value: 80
admin:
  access_log_path: "/dev/null"
  address:
    socket_address:
      address: <IP_ADDRESS>
      port_value: 8001

Config envoy for service1:
static_resources:
  listeners:
  - address:
      socket_address:
        address: <IP_ADDRESS>
        port_value: 80
    filter_chains:
    - filters:
      - name: envoy.http_connection_manager
        config:
          upgrade_configs:
          - upgrade_type: websocket
          codec_type: auto
          stat_prefix: ingress_http
          route_config:
            name: local_route
            virtual_hosts:
            - name: service
              domains:
              - "*"
              routes:
                - match:
                    prefix: "/service1"
                  route:
                    cluster: local_service
          http_filters:
            - name: envoy.router
              config: {}
  clusters:
  - name: local_service
    connect_timeout: 0.25s
    type: strict_dns
    lb_policy: round_robin
    hosts:
    - socket_address:
        address: <IP_ADDRESS>
        port_value: 8888
admin:
  access_log_path: "/dev/null"
  address:
    socket_address:
      address: <IP_ADDRESS>
      port_value: 8001

I have run into a similar issue.
I have a WebSocket service that I want to access from a frontend server.
My envoy.yaml have this config:
admin:
  access_log_path: "/dev/null"
  address:
    socket_address:
      address: <IP_ADDRESS>
      port_value: 8002

static_resources:
  listeners:
  - address:
      socket_address:
        address: <IP_ADDRESS>
        port_value: 443
    filter_chains:
    - filters:
      - name: envoy.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager
          codec_type: auto
          stat_prefix: ingress_http
          route_config:
            name: local_route
            virtual_hosts:
            - name: backend
              domains:
              - "*"
              routes:
              - match:
                  prefix: "/history/"
                route:
                  cluster: service1
                  prefix_rewrite: "/"
              - match:
                  prefix: "/api/"
                route:
                  cluster: api
                  prefix_rewrite: "/"
              - match:
                  prefix: "/feed/"
                route:
                  cluster: ws
                  prefix_rewrite: "/"
                  upgrade_configs: [{upgrade_type: websocket}]

              cors:
                allow_origin:
                - "*"
                allow_methods: GET, PUT, DELETE, POST, OPTIONS
                allow_headers: authorization,keep-alive,user-agent,cache-control,content-type,content-transfer-encoding,x-accept-content-transfer-encoding,x-accept-response-streaming,x-user-agent,x-grpc-web
                max_age: "1728000"
                expose_headers: grpc-status,grpc-message
                enabled: true
          http_filters:
          - name: envoy.grpc_web
          - name: envoy.cors
          - name: envoy.router
            typed_config: {}
      tls_context:
        common_tls_context:
          alpn_protocols: "h2"
          tls_certificates:
            - certificate_chain:
                filename: "xx"
              private_key:
                filename: "xx"

  clusters:
  - name: service1
    connect_timeout: 25s
    type: LOGICAL_DNS
    lb_policy: ROUND_ROBIN
    http2_protocol_options: { }
    hosts: [{ socket_address: { address: history, port_value: 50051 }}]

  - name: api
    connect_timeout: 25s
    type: LOGICAL_DNS
    lb_policy: ROUND_ROBIN
    hosts: [{ socket_address: { address: apirest, port_value: 3030 }}]

  - name: ws
    connect_timeout: 25s
    type: LOGICAL_DNS
    lb_policy: ROUND_ROBIN
    http2_protocol_options:
      allow_connect: true
    hosts: [{ socket_address: { address: apiws, port_value: 4040 }}]

I want to connect to my websocket using wss.
The other two services are working fine, but the ws service response with
503 Service Unavailable
I dive into the logs and the logs related to the error are this:
[2019-03-31 06:56:58.688][12][debug][router] [source/common/router/router.cc:320] [C22][S6344712873306105893] cluster 'ws' match for URL '/feed/?encoding=text'
[2019-03-31 06:56:58.689][12][debug][router] [source/common/router/router.cc:381] [C22][S6344712873306105893] router decoding headers:
':authority', 'example.com'
':path', '/?encoding=text'
':method', 'GET'
':scheme', 'http'
'connection', 'Upgrade'
'pragma', 'no-cache'
'cache-control', 'no-cache'
'upgrade', 'websocket'
'origin', 'https://www.websocket.org'
'sec-websocket-version', '13'
'user-agent', 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36'
'accept-encoding', 'gzip, deflate, br'
'accept-language', 'es-US,es-419;q=0.9,es;q=0.8,en;q=0.7'
'sec-websocket-key', 'EHTUJx53Lz4ZwXFsPcYsuw=='
'sec-websocket-extensions', 'permessage-deflate; client_max_window_bits'
'content-length', '0'
'x-forwarded-proto', 'https'
'x-request-id', '64545a37-98e8-404e-8b90-bbac994c1668'
'x-envoy-expected-rq-timeout-ms', '15000'
'x-envoy-original-path', '/feed/?encoding=text'

[2019-03-31 06:56:58.690][12][debug][client] [source/common/http/codec_client.cc:26] [C23] connecting
[2019-03-31 06:56:58.690][12][debug][connection] [source/common/network/connection_impl.cc:644] [C23] connecting to <IP_ADDRESS>:4040
[2019-03-31 06:56:58.691][12][debug][connection] [source/common/network/connection_impl.cc:653] [C23] connection in progress
[2019-03-31 06:56:58.691][12][debug][http2] [source/common/http/http2/codec_impl.cc:735] [C23] setting stream-level initial window size to 268435456
[2019-03-31 06:56:58.691][12][debug][http2] [source/common/http/http2/codec_impl.cc:757] [C23] updating connection-level initial window size to 268435456
[2019-03-31 06:56:58.691][12][debug][pool] [source/common/http/conn_pool_base.cc:20] queueing request due to no available connections
[2019-03-31 06:56:58.691][12][debug][connection] [source/common/network/connection_impl.cc:517] [C23] connected
[2019-03-31 06:56:58.691][12][debug][client] [source/common/http/codec_client.cc:64] [C23] connected
[2019-03-31 06:56:58.691][12][debug][pool] [source/common/http/http2/conn_pool.cc:96] [C23] creating stream
[2019-03-31 06:56:58.691][12][debug][router] [source/common/router/router.cc:1165] [C22][S6344712873306105893] pool ready
[2019-03-31 06:56:58.715][12][info][client] [source/common/http/codec_client.cc:118] [C23] protocol error: The user callback function failed
[2019-03-31 06:56:58.715][12][debug][connection] [source/common/network/connection_impl.cc:101] [C23] closing data_to_write=34 type=1
[2019-03-31 06:56:58.715][12][debug][connection] [source/common/network/connection_impl.cc:183] [C23] closing socket: 1
[2019-03-31 06:56:58.715][12][debug][client] [source/common/http/codec_client.cc:82] [C23] disconnect. resetting 1 pending requests
[2019-03-31 06:56:58.715][12][debug][client] [source/common/http/codec_client.cc:105] [C23] request reset
[2019-03-31 06:56:58.715][12][debug][pool] [source/common/http/http2/conn_pool.cc:237] [C23] destroying stream: 0 remaining
[2019-03-31 06:56:58.715][12][debug][router] [source/common/router/router.cc:644] [C22][S6344712873306105893] upstream reset: reset reason connection termination
[2019-03-31 06:56:58.715][12][debug][http] [source/common/http/conn_manager_impl.cc:1265] [C22][S6344712873306105893] encoding headers via codec (end_stream=false):
':status', '503'
'content-length', '95'
'content-type', 'text/plain'
'access-control-allow-origin', 'https://www.websocket.org'
'access-control-expose-headers', 'grpc-status,grpc-message'
'date', 'Sun, 31 Mar 2019 06:56:58 GMT'
'server', 'envoy'
'connection', 'close'

I'm using the envoyproxy/envoy-dev:latestimage.


fix inconsistency in exercise topics

Are there other topics that need changes?
fix #329

Other topic fixes I noticed:
"mathematics" should be "math"
"data_structure" should be "data_structures" (plural)
You need to run bin/fetch-configlet && bin/configlet fmt . to reformat the config.json file before we can merge it.
Also if you have the time, adding a brief pointer to the topics file in the README under 'Adding an Exercise' would be very useful :)
Thanks!

Oh, i missed those two. Thanks for spotting them!
Oh, didn't know configlet is needed to update the topics as well. Travis is happy now :)
I updated the README as suggested. What do you think about it?


Use inner module for non-public coders.

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify.
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @aaltay

Coverage decreased (-0.01%) to 70.487% when pulling f15518e13f53890a7bb8e087c7e4e71d81bc340a on robertwb:interval-window into 86e1fab69f296247624d7799f151ff25c3b7243a on apache:master.

LGTM


Emulate directories when calling has()

If the object doesn't exist, try to list objects under it. If there are items then assume directory and return true.
This is the same logic as their StreamWrapper::url_stat.
Déjà vu :laughing: :busts_in_silhouette:

@frankdejonge I need your advice on this.
I'm now seeing many methods that expect files: has, getMetadata, getVisibility, getSize, getTimestamp.
The Local adapter supports all of these with directories (except for size).
So there is a gap here and it would be nice to work out these inconsistencies somehow. Maybe the local adapter should be restricted to match filesystems that don't support directories.
On the otherhand, I know S3 can work around has and getMetadata (at least to return type).
Thoughts?

@CarsonF Hi, sorry for the late response, life is not always generous in the amount of time it gives me for OSS. The philosophy for flysystem is that it tries to return as much information about with the least amount of resources, when a call is expensive, make the most of it. So this is why the adapter interface allows returning metadata on has calls, which is dealt with in the Filesystem. Wouldn't a better approach for this problem be the old doesObjectExist call, if false do the dir check? This way that function doesn't explode and you still get the benefit of the less expensive doesObjectExist call when the object does exist.

This is what we're doing in Drupal to emulate directories.
http://cgit.drupalcode.org/flysystem_s3/tree/src/Flysystem/Adapter/S3Adapter.php?h=8.x-1.x

I'd be more in favour of that, also @twistor is that a fork?

@twistor btw, I don't think that handles the case which is address here though. In that case a dir actually needs to exist.

doesObjectExist just calls headObject and casts to boolean. Checking for an object, "foo/", could be false, but listing objects under that key could return items.
Also getMetadata makes the assumption that it's a directory, which I don't want to do

@CarsonF the initial call could still be the doesObjectExist call though, right? I don't really see a clear benefit of using constructing the command ourselves. Am I missing something? The second part I think is good btw.

That was a quick hack to get it to work.
@frankdejonge, it's just a sublcass, while I wait for this issue to shake out.
If I remember, I just looked at what the AWS stream wrapper did, but I could be mistaken.

Just trying to be consistent with the rest of the code. It looked like it was changed to use getCommand so I followed suit. Let me see if there was another reason

@CarsonF I'll just merge this as is, I'll do some small refactoring before bagging and tagging it 👍

Schweet! Thanks Frank! 👍 🎉

@CarsonF I've changed the first part of the implementation back to the doesObjectExist call (because the method was quite big and I like easy calls). Extracted the rest into a doesDirectoryExist method, tagged the whole thing as 1.0.10. The version should be available on packagist shortly.

👍


Quick Fix: add @@schema attribute to model / enum

Goal: Multi-Schema GA
subtask of #1300

Where to get started: engines//code_actions.rs

Can we add some explicit tests for this here? Just to confirm it works.

I'm not sure what you mean, this does have explicit tests added as part of the same PR @janpio


Fix Date of birth ,branch and gender is required error handling with formik on touch component in signup page

In client side it show user is not 18+, gender is required and branch is required with formik touch

hi, I would like to contribute to your project

I am assigning this Task

Thank You very much. I will work on it

I already fixed the issue with the branch field.

@dineshigdd

Default branch is master
In birth date you have to check person should be greater than 18+ warning

ok..sorry, when I was asking about the branch, I mean the branch (university branch in the app) in the application. Anyway, I fixed the issue regarding the "select" field.

Actually there is no default branch you can ard initial value  length 0 after that see whether is more than 0 if not then show error

Do you want me to make PR after I fixed everything or after I fixed a particular control on the form?

2nd option will be better

I added functions to display error msg for branch and gender controls on the signup page.  I make my PR to the beta branch

nice work @dineshigdd

Thank you . I will work on birthday issue too. Hopefully I can make a PR on Tuesday.

@dineshigdd  nice you are doing great work

I sent a new PR for Birthday error msgs

@dineshigdd  thank you for contributing


Simplify TurboModule setup

Summary:
By introducing a RCTAppDelegate base class, we can simplify the migration step to supports TM
Changelog
[iOS][Changed] - Simplified migration steps for TM
Differential Revision: D38509891

@cipolleschi If we have a base class now, would it make sense to extract all the other methods and vars out as well? That would result in a much smaller app delegate.

@danilobuerger Yes, but I wanted to tackle in another PR not to have too big changes and to clearly separate TM and FC

Awesome!


Possible fix for math.ceil and math.floor

Fixes the problem described in #1584 where rustpython's math.ceil and math.floor aren't consistent with cpython's.

Should I remove the added test in the math_module?

It seems something went wrong with merge.
when RustPython/RustPython is remote upstream, running this command will help to fix the branch
$ git fetch upstream
$ git rebase upstream/master

Alright I ran the commands and fast forwarded the branch as @youknowone advised. Thank you for the advice.

One last thing @adolfogonzalez3, could you put all the tests for this feature into tests/snippets/stdlib_math.py rather than tests/snippets/math_module.py? That's where we keep the tests for the math module.

Okay I will move the test code into tests/snippets/stdlib_math.py and make another commit. It looks like tests/snippets/math_module.py was deleted from the master branch so should I remove the entire file or just remove the test?

Removing the entire file would be great, thanks. I think it was renamed in #1530, which was probably after you started working on this.

Thanks for contributing and seeing this through!


React/feat/270

Footer component implemented, please review.

@wc-lei also it looks like there's a rollup error to do with importing an svg, I can take a look at that.

@wc-lei, apologies, one more thing is that we need to add tests for this component.

Also and finally, we need to create a minor version bump for this. You can do that by running npx changest let me know if you want to do this together the first time.

For LocalNav, I put in a very basic toggle handler but it doesn't seem to work, see if you can spot anything. Thanks.


[Toolkits] Code area height calculation is off in Safari

E.g.

I think the font is genuinely larger which is interesting.

Notes from Friday:
Font size is md in Chrome from some Chakra class .css-393tye (surrounding Box, I think).
Font size is 1rem in Safari from ".ͼz .cm-content".
But md is 1rem... so that makes no sense that there's a visual difference.

Setting the :root { font-size: 16px } mostly fixes the font size issue. I have no idea why. All the other font sizes are right so it’s not like some preference I have.
Then there’s still a glitch due to https://bugs.webkit.org/show_bug.cgi?id=225695
This means Safari uses 22px line height vs ~22.3 from the 1.4 line height in CM. I've switched to 1.375 line height to get us 22px in both, which looks OK to me in Explore. I didn't do it in the main editor as it looks noticeably more cramped.


Bugfix settings machine vars not persisting on subsequent data writes

This PR fixes a bug that would occasionally (okay, often) forget saved machine vars and cause operator-configured settings to reset to default. After much digging and consternation, I believe I've figured out the cause and it's a simple fix.
The Background
When MPF initializes, it first reads all machine variables from the machine_vars.yaml file and then appends those with the (default) variables from the machine_variables: config section. All settings values are backed under-the-hood by machine variables, so this logic covers operator-adjustable settings as well.
The Bug
While the code flow for loading machine vars from config section includes the configuration of a persist value, loading machine vars from the data file does not, which means all saved settings are defaulted to persist: False. Which is okay for a short while, but eventually something else is going to write an update to the persisted data (a new setting adjustment, or a player score, or something).
The Impact
The way the logic of writing the data works is that the code looks through all the machine vars, finds all of the ones that are persist: True, and writes a complete new data file with those values. Remember from before that values previously loaded from the data file are persist: False, so all of those values get wiped.
The Fix
This PR tweaks the flow for loading persisted values from a data file, explicitly flagging them each as persist: True in the machine variables controller. After all, if the value was persisted before, it should be persisted still, right?
The updated persistence logic takes place after data validation and expiration checks, so it shouldn't impact data retention policies, and it fixes the issue of saved settings being forgotten on subsequent data writes.

@avanwinkle Seeing that tests fail now.    But values that are expected to not persist are being set to true on the load with this change.  I didn't want to just go fudge the data to pass the tests in case there is an edge case that is not being caught.


Bucket Sort [Algorithm] C++

Bucket Sort Algorithm
Bucket sort is mainly useful when input is uniformly distributed over a range. For example, Sort a large set of floating point numbers which are in range from 0.0 to 1.0 and are uniformly distributed across the range. Here we can use bucket sort to solve the problem efficiently.
The program would be implemented in C++ language.
I request mentors to assign me this issue for GSSOC '21.

I am a participant in GSSOC 2021 I would love to do this using c or java. Please assign this to me!

Hello sir , I want  to solve this issue please assign me.


Handle request(0) in ObservableToProducer

The Async driver doesn't support any requests less than one.
RxJava 1.x supports requesting zero elements, so we must short circuit request(0)
JAVARX-34

lgtm

lgtm


Failed compiling bevy-glsl-to-spirv v0.2.1 to target x86_64-pc-windows-gnu from Ubuntu 20.04 (WSL2)

Bevy version
0.5.0
Operating system & version
Ubuntu 20.04 WSL2
What you did
Tried to build this example for target x86_64-pc-windows-gnu on Linux. I have every dependency installed.
What you expected to happen
To compile properly.
What actually happened
Build failed for bevy-glsl-to-spirv v0.2.1 as it is Missing target support x86_64-pc-windows-gnu
Additional information
error: failed to run custom build command for `bevy-glsl-to-spirv v0.2.1`

Caused by:
  process didn't exit successfully: `/root/dev/rust/bevy-shaders-test/target/debug/build/bevy-glsl-to-spirv-ea21dca2a4b6ae86/build-script-build` (exit code: 101)
  --- stderr
  thread 'main' panicked at 'Missing target support x86_64-pc-windows-gnu', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy-glsl-to-spirv-0.2.1/build/build.rs:24:9

This should be fixed on git main since #1819 got merged, could you check?

This should be fixed on git main since #1819 got merged, could you check?

Tried main from git (had to install cmake, which should be listed as dependency btw) but still got error

In this case it's trying to build shaderc which is a little harder to setup... You can download a prebuilt version, or follow instructions here: https://github.com/google/shaderc#getting-and-building-shaderc

So there is no "simple" way of building bevy for Windows? If no I still consider this an issue.

The simple way is to use the MSVC toolchain on Windows directly and not use WSL2 I think.

The simple way is to use the MSVC toolchain on Windows directly and not use WSL2 I think.

^this
Using it with WSL2 is more difficult to setup/configure since its a linux VM running on windows.
I've been developing on Windows using the MSVC toolchain and haven't run into any problems (just as an example)

The simple way is to use the MSVC toolchain on Windows directly and not use WSL2 I think.

It doesn't change a fact that building for Windows from Linux is not possible the way it should work. That just a workaround and for time until fixing I will of course use it this way.

bevy-glsl-to-spirv is no longer needed


abseil-cpp: 20200923.3 -> 20210324.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/abseil/abseil-cpp/releases.
meta.description for abseil-cpp is: "An open-source collection of C++ code designed to augment the C++ standard library"
meta.homepage for abseil-cpp is: "https://abseil.io/"
meta.changelog for abseil-cpp is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 20210324.0 with grep in /nix/store/gvm965xdan3na87lfnvwxz12h4v4wf5v-abseil-cpp-20210324.0

found 20210324.0 in filename of file in /nix/store/gvm965xdan3na87lfnvwxz12h4v4wf5v-abseil-cpp-20210324.0

directory tree listing: https://gist.github.com/d188cabeb689aac5193fbd6f289378c7

du listing: https://gist.github.com/790cfd7841aa41b13f24bc0f3f1d96b6

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

654 total rebuild path(s)

186 package rebuild(s)

186 x86_64-linux rebuild(s)
159 i686-linux rebuild(s)
149 x86_64-darwin rebuild(s)
160 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
abseil-cpp
beancount
bear
deja-dup
duplicity
duply
dvc-with-remotes
fava
fcitx5-mozc
gcalcli
google-cloud-cpp
grpc
kmymoney
ledger2beancount
lieer
linuxPackages-libre.sysdig
linuxPackages.sysdig
linuxPackages_4_14.sysdig
linuxPackages_4_19.sysdig
linuxPackages_4_4.sysdig
linuxPackages_4_9.sysdig
linuxPackages_5_10.sysdig
linuxPackages_5_11.sysdig
linuxPackages_5_4.sysdig
linuxPackages_hardened.sysdig
linuxPackages_hardkernel_4_14.sysdig
linuxPackages_hardkernel_latest.sysdig
linuxPackages_latest-libre.sysdig
linuxPackages_latest.sysdig
linuxPackages_latest_hardened.sysdig
linuxPackages_latest_xen_dom0.sysdig
linuxPackages_latest_xen_dom0_hardened.sysdig
linuxPackages_lqx.sysdig
linuxPackages_testing_bcachefs.sysdig
linuxPackages_xen_dom0.sysdig
linuxPackages_xen_dom0_hardened.sysdig
linuxPackages_zen.sysdig
lndmanage
murmur
or-tools
python38Packages.arviz
python38Packages.baselines
python38Packages.beancount
python38Packages.beancount_docverif
python38Packages.chirpstack-api
python38Packages.cirq
python38Packages.dm-sonnet
python38Packages.edward
python38Packages.goobook
python38Packages.google-api-core

Instructions to test this update (click to expand)

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

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

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

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @andersk for testing.

This might be worthwhile to check:
https://github.com/Profpatsch/nixpkgs/blob/ee1aa3985792944ba13f2e0c18d42e2ed0f3f4ba/pkgs/tools/inputmethods/fcitx5/fcitx5-mozc.nix#L12-L22

@andersk Would you like me to have r-ryantm skip this?

Okay, done and deployed https://github.com/ryantm/nixpkgs-update/commit/c1537fbba57e61ada042863b39c3616529691475


speedup loading of large touchstone files

Growing numpy arrays is slow for large touchstone files.
Replaces numpy array with list.

Thanks for your contribution!


优化 LRUCache读取性能

LRUCache
问题
查询可以加共享锁，更新时才需要加排他锁。因此可以使用信号量替代排他锁提高查询操作的性能。
思路：
1. 必须使用公平锁：由AQS和Semaphore源码可知非公平锁在高并发情况下会导致更新操作难以执行；
2. 信号量初始值为Integer.MAX_VALUE，读取操作则将状态值减1，更新操作则将状态值减Integer.MAX_VALUE，以此来实现查询操作加共享锁，更新操作加排他锁。
主要修改：
//1. 排他锁ReentrantLock替换成信号来能Semaphore；

//2.size()->super.size()父类方法不需要获取许可，且仅在put类操作中被调用
    @Override
    protected boolean removeEldestEntry(java.util.Map.Entry<K, V> eldest) {
        return super.size() > maxCapacity;
    }

参考：

《java并发编程实战》14.5 和 14.6 小节
信号量测试

@dugenkui03 looks like your implementation fails the unit tests.

@beiwei30 @dugenkui03
I think it is a good idea.
Thx for your issue and pr. But if there are some performance tests, it will be more convincing.
:)

@dugenkui03 why close the pull request?

should we try out ReadWriteLock if semaphore has problem?

should we try out ReadWriteLock if semaphore has problem?

Yes, we can. I considered ReadWriteLock, it seems the same effect with semaphore.
I will help him to fix ci problem.

should we try out ReadWriteLock if semaphore has problem?

Yes, we can. I considered ReadWriteLock, it seems the same effect with semaphore.
I will help him to fix ci problem.

thx,replace ReentrantLock with ReadWriteLock is easy,i finished this  noon.tough part is performance tests,because i need to consider the effects of the gc、jit especially the hit rate.details in here.
failed in designing of the perfect solution，this simple demo can demonstrate that  ReadWriteLock is faster than ReentrantLock .i have add some functional tests in PR.

should we try out ReadWriteLock if semaphore has problem?

bed PR, get() in linkedmap is not threadSafe,because it will update the position of visited key.thx for review.


Fix participant indexing when participant aliases are configured

Rationale
The filter to select participants for full-text search indexing is too strict when a participant alias dataset is configured.
When the PTID list is null we should select all participants. Currently, however, when an alias table is present, we're adding an overly restrictive condition about modified aliases. Instead, we should add this condition only if we're selecting specific participants (i.e., the lastIndexedClause is not empty).
Related Pull Requests

https://github.com/LabKey/platform/pull/4577

All previously failing search tests are now passing on this FB:

https://teamcity.labkey.org/buildConfiguration/LabKey_237Release_Community_DailySuites_DailyEPostgres/2547256?buildTab=tests
https://teamcity.labkey.org/buildConfiguration/LabKey_237Release_Community_ModuleSuites_SearchPostgres/2547258?buildTab=tests
https://teamcity.labkey.org/buildConfiguration/LabKey_237Release_Community_ModuleSuites_SearchSqlserver/2547260?buildTab=tests


Update docs to the show cli commands rather than --flags

This is a sibling to https://github.com/lumeland/lume/pull/34.
Updating the lumeland site to show the command format implemented there.
Only merge this if/after that is merged.

Fantastic, thank you!
I'll merge it after release the new version

Fantastic, thank you!
I'll merge it after release the new version

v0.14.0 released, so I merge this.


Bug

We have written the needed data into your clipboard because it was too large to send. Please paste.

代码叠起来后,无法展开,就像消失了,需要重启VScode才可以

代码叠起来后,无法展开,就像消失了,需要重启VScode才可以


Simple Browser crashes (black window) when clicking "go forward" button

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.70.1
OS Version: Windows 11

Steps to Reproduce:

Visit URL: https://nodejs.org/de/blog/announcements/v18-release-announce/
Click "go back" button
Click "go forward" button
You will see a black window because the Simple Browser crashed (see video)

Video:
https://user-images.githubusercontent.com/469989/184127552-878d27d2-2575-437b-809a-8c98cced5382.mp4

Doesn't repo for me
Does this reproduce in the latest VS Code insiders build with all extensions disabled?

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Implement exponential map for translator

The logarithm of a translator is a line with only degenerate components (e01, e02, e03). I called it an Ideal Line (name is taken from klein) as it is a line at infinity (a translation is a rotation around a line at infinity). The exponential of an Ideal Line is a translator again. Implementing Ln and Exp for Translator and IdealLine allows to write code generic over motor-like types.
#[test]
fn foo() {
    let b = ppga3d:: IdealLine { g0: simd::Simd32x3 {
        f32x3: [1.0, 2.0, 3.0]
    } };

    // A translator by 1 e1 units, 2 e2 units and 3 e3 units.
    let t = b.exp();

    // A translator by 0.5 e1 units, 1 e2 units and 1.5 e3 units.
    let t_half = t.powf(0.5);

    let b_half = t_half.ln();

    unsafe { assert_eq!(
        b_half.g0.f32x3,
        [0.5, 1.0, 1.5]
    ) };
}

Sorry for answering late, just saw it, did not receive a notification for some reason.
Anyway, thanks for the contribution. I suspect a similar thing is possible for ppga2d as well, right?


remove some format hardenings

Motivation for this change
Fixing fallout from #28029 and continuing #39463.
Things done

[X] Everything built before rebase.

Success on x86_64-linux (full log)
Attempted: a52dec, libgdiplus, tinyxml
Partial log (click to expand)
post-installation fixup
moving /nix/store/wrfqv2j2z9jzrgp2jln0k9q246lzir3s-a52dec-0.7.4p4/man to /nix/store/wrfqv2j2z9jzrgp2jln0k9q246lzir3s-a52dec-0.7.4p4/share/man
shrinking RPATHs of ELF executables and libraries in /nix/store/wrfqv2j2z9jzrgp2jln0k9q246lzir3s-a52dec-0.7.4p4
shrinking /nix/store/wrfqv2j2z9jzrgp2jln0k9q246lzir3s-a52dec-0.7.4p4/bin/a52dec
shrinking /nix/store/wrfqv2j2z9jzrgp2jln0k9q246lzir3s-a52dec-0.7.4p4/bin/extract_a52
gzipping man pages under /nix/store/wrfqv2j2z9jzrgp2jln0k9q246lzir3s-a52dec-0.7.4p4/share/man/
strip is /nix/store/92d2ifxcni4n3zx9s8wnkcjlvnx5ajlc-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/wrfqv2j2z9jzrgp2jln0k9q246lzir3s-a52dec-0.7.4p4/lib  /nix/store/wrfqv2j2z9jzrgp2jln0k9q246lzir3s-a52dec-0.7.4p4/bin
patching script interpreter paths in /nix/store/wrfqv2j2z9jzrgp2jln0k9q246lzir3s-a52dec-0.7.4p4
checking for references to /build in /nix/store/wrfqv2j2z9jzrgp2jln0k9q246lzir3s-a52dec-0.7.4p4...

@GrahamcOfBorg build linuxPackages.perf haskellPackages.ghc802

Success on x86_64-linux (full log)
Attempted: linuxPackages.perf
The following builds were skipped because they don't evaluate on x86_64-linux: haskellPackages.ghc802
Partial log (click to expand)
/nix/store/xmissrgpzr4nmypcmphgf2mn5ni0xpzx-perf-linux-4.14.44/libexec/perf-core/scripts/perl/bin/rw-by-file-report: interpreter directive changed from "/bin/bash" to "/nix/store/m47apl3hq3i52fzy2cz24378p0xn4lyx-bash-4.4-p19/bin/bash"
/nix/store/xmissrgpzr4nmypcmphgf2mn5ni0xpzx-perf-linux-4.14.44/libexec/perf-core/scripts/perl/rwtop.pl: interpreter directive changed from "/usr/bin/perl -w" to "/nix/store/kag4rrbjj5hih61dlagry62v82l0gscw-perl-5.24.3/bin/perl -w"
/nix/store/xmissrgpzr4nmypcmphgf2mn5ni0xpzx-perf-linux-4.14.44/libexec/perf-core/scripts/perl/wakeup-latency.pl: interpreter directive changed from "/usr/bin/perl -w" to "/nix/store/kag4rrbjj5hih61dlagry62v82l0gscw-perl-5.24.3/bin/perl -w"
/nix/store/xmissrgpzr4nmypcmphgf2mn5ni0xpzx-perf-linux-4.14.44/libexec/perf-core/perf-with-kcore: interpreter directive changed from "/bin/bash" to "/nix/store/m47apl3hq3i52fzy2cz24378p0xn4lyx-bash-4.4-p19/bin/bash"
checking for references to /build in /nix/store/xmissrgpzr4nmypcmphgf2mn5ni0xpzx-perf-linux-4.14.44...
moving /nix/store/xmissrgpzr4nmypcmphgf2mn5ni0xpzx-perf-linux-4.14.44/lib64/* to /nix/store/xmissrgpzr4nmypcmphgf2mn5ni0xpzx-perf-linux-4.14.44/lib
shrinking RPATHs of ELF executables and libraries in /nix/store/929f5q1zbf6gwa4l4bq4kra9w0rg3jx5-perf-linux-4.14.44-debug
patching script interpreter paths in /nix/store/929f5q1zbf6gwa4l4bq4kra9w0rg3jx5-perf-linux-4.14.44-debug
checking for references to /build in /nix/store/929f5q1zbf6gwa4l4bq4kra9w0rg3jx5-perf-linux-4.14.44-debug...
/nix/store/xmissrgpzr4nmypcmphgf2mn5ni0xpzx-perf-linux-4.14.44

Success on aarch64-linux (full log)
Attempted: linuxPackages.perf
The following builds were skipped because they don't evaluate on aarch64-linux: haskellPackages.ghc802
Partial log (click to expand)
/nix/store/phi6j1ybq9xkbrl64yj48c4acxsng7az-perf-linux-4.14.44/libexec/perf-core/scripts/perl/rw-by-file.pl: interpreter directive changed from "/usr/bin/perl -w" to "/nix/store/0cicmg6kkz0r056kxhcfwgmf4wjr3ham-perl-5.24.3/bin/perl -w"
/nix/store/phi6j1ybq9xkbrl64yj48c4acxsng7az-perf-linux-4.14.44/libexec/perf-core/perf-with-kcore: interpreter directive changed from "/bin/bash" to "/nix/store/vnb8q2h7951gd551nm2vq2g6n8296g5b-bash-4.4-p19/bin/bash"
/nix/store/phi6j1ybq9xkbrl64yj48c4acxsng7az-perf-linux-4.14.44/libexec/perf-core/perf-archive: interpreter directive changed from "/bin/bash" to "/nix/store/vnb8q2h7951gd551nm2vq2g6n8296g5b-bash-4.4-p19/bin/bash"
/nix/store/phi6j1ybq9xkbrl64yj48c4acxsng7az-perf-linux-4.14.44/libexec/perf-core/tests/attr.py: interpreter directive changed from " /usr/bin/python" to "/nix/store/1xkxxrd2sd8q78icm687ac8si9miak45-python-2.7.15/bin/python"
checking for references to /build in /nix/store/phi6j1ybq9xkbrl64yj48c4acxsng7az-perf-linux-4.14.44...
moving /nix/store/phi6j1ybq9xkbrl64yj48c4acxsng7az-perf-linux-4.14.44/lib64/* to /nix/store/phi6j1ybq9xkbrl64yj48c4acxsng7az-perf-linux-4.14.44/lib
shrinking RPATHs of ELF executables and libraries in /nix/store/3wi0hsdx5yhqjm53nx5s6086ks5p4nz8-perf-linux-4.14.44-debug
patching script interpreter paths in /nix/store/3wi0hsdx5yhqjm53nx5s6086ks5p4nz8-perf-linux-4.14.44-debug
checking for references to /build in /nix/store/3wi0hsdx5yhqjm53nx5s6086ks5p4nz8-perf-linux-4.14.44-debug...
/nix/store/phi6j1ybq9xkbrl64yj48c4acxsng7az-perf-linux-4.14.44

@GrahamcOfBorg build haskell.compiler.ghc802

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: haskell.compiler.ghc802
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: haskell.compiler.ghc802
Partial log (click to expand)
strip is /nix/store/92d2ifxcni4n3zx9s8wnkcjlvnx5ajlc-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/vnzhm68hg3minr68ckcflndhfiphkgsd-ghc-8.0.2-man
checking for references to /build in /nix/store/vnzhm68hg3minr68ckcflndhfiphkgsd-ghc-8.0.2-man...
shrinking RPATHs of ELF executables and libraries in /nix/store/m7wrj3pfgjxnw62pq924ba8jwasdbxm6-ghc-8.0.2-doc
/nix/store/92d2ifxcni4n3zx9s8wnkcjlvnx5ajlc-binutils-2.30/bin/strip is /nix/store/92d2ifxcni4n3zx9s8wnkcjlvnx5ajlc-binutils-2.30/bin/strip
strip is /nix/store/92d2ifxcni4n3zx9s8wnkcjlvnx5ajlc-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/m7wrj3pfgjxnw62pq924ba8jwasdbxm6-ghc-8.0.2-doc
/nix/store/m7wrj3pfgjxnw62pq924ba8jwasdbxm6-ghc-8.0.2-doc/share/doc/ghc/html/libraries/gen_contents_index: interpreter directive changed from "/bin/sh" to "/nix/store/m47apl3hq3i52fzy2cz24378p0xn4lyx-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/m7wrj3pfgjxnw62pq924ba8jwasdbxm6-ghc-8.0.2-doc...
/nix/store/f7jhkc1frnqb37l7h3gi51y4vc8qnwry-ghc-8.0.2

Success on aarch64-linux (full log)
Attempted: a52dec, libgdiplus, tinyxml
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/g2ws2p2qggz29l3m9klymln4i67k2ch4-libgdiplus-2.10.9
shrinking /nix/store/g2ws2p2qggz29l3m9klymln4i67k2ch4-libgdiplus-2.10.9/lib/libgdiplus.so.0.0.0
strip is /nix/store/8yfik687kfccisxnad42j19lfb7ij9b4-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/g2ws2p2qggz29l3m9klymln4i67k2ch4-libgdiplus-2.10.9/lib
patching script interpreter paths in /nix/store/g2ws2p2qggz29l3m9klymln4i67k2ch4-libgdiplus-2.10.9
checking for references to /build in /nix/store/g2ws2p2qggz29l3m9klymln4i67k2ch4-libgdiplus-2.10.9...
/nix/store/ff9wqbmjbi4dfbfjxlpnqgpamfh1blhb-a52dec-0.7.4p4
/nix/store/g2ws2p2qggz29l3m9klymln4i67k2ch4-libgdiplus-2.10.9
/nix/store/sx89pf3psyxxrn8zdq155ds3aa4jdj20-tinyxml-2.6.2

libgdiplus: see also #41187

How about haskell.packages.ghc842.ghc? It also seems to have trouble with the new hardening features: https://hydra.nixos.org/build/75026569. Or is that not related?

libgdiplus

Identical change, rebased.

How about haskell.packages.ghc842.ghc?

Likely related, fixed.

Success on aarch64-linux (full log)
Attempted: a52dec, linuxPackages.perf, tinyxml
The following builds were skipped because they don't evaluate on aarch64-linux: haskell.compiler.ghc802, haskell.compiler.ghc842
Partial log (click to expand)
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

/nix/store/ff9wqbmjbi4dfbfjxlpnqgpamfh1blhb-a52dec-0.7.4p4
/nix/store/phi6j1ybq9xkbrl64yj48c4acxsng7az-perf-linux-4.14.44
/nix/store/sx89pf3psyxxrn8zdq155ds3aa4jdj20-tinyxml-2.6.2

Success on x86_64-linux (full log)
Attempted: a52dec, haskell.compiler.ghc802, haskell.compiler.ghc842, linuxPackages.perf, tinyxml
Partial log (click to expand)
/nix/store/92d2ifxcni4n3zx9s8wnkcjlvnx5ajlc-binutils-2.30/bin/strip is /nix/store/92d2ifxcni4n3zx9s8wnkcjlvnx5ajlc-binutils-2.30/bin/strip
strip is /nix/store/92d2ifxcni4n3zx9s8wnkcjlvnx5ajlc-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/s2fmlbgfydj5pf2pgb75l91d80cmk9f9-ghc-8.4.2-doc
/nix/store/s2fmlbgfydj5pf2pgb75l91d80cmk9f9-ghc-8.4.2-doc/share/doc/ghc/html/libraries/gen_contents_index: interpreter directive changed from "/bin/sh" to "/nix/store/m47apl3hq3i52fzy2cz24378p0xn4lyx-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/s2fmlbgfydj5pf2pgb75l91d80cmk9f9-ghc-8.4.2-doc...
/nix/store/wrfqv2j2z9jzrgp2jln0k9q246lzir3s-a52dec-0.7.4p4
/nix/store/f7jhkc1frnqb37l7h3gi51y4vc8qnwry-ghc-8.0.2
/nix/store/qqpj7di0zjbfwpziz5bn8w2kf9cyn42c-ghc-8.4.2
/nix/store/xmissrgpzr4nmypcmphgf2mn5ni0xpzx-perf-linux-4.14.44
/nix/store/ps9drs0ya9l81nk3kida9hkd5qcfamli-tinyxml-2.6.2

ghc-7.10.3 and ghc-head are also broken. :-(
I committed a246b6e6f8a33622d0be001391a9087820030134 and 8d36f159fa3dcdb2b8f4872787a4bf67748fd7db to the haskell-updates branch to fix.

ghc-7.10.3 and ghc-head are also broken. :-(
I committed a246b6e6f8a33622d0be001391a9087820030134 and 8d36f159fa3dcdb2b8f4872787a4bf67748fd7db to the haskell-updates branch to fix.

ghc-7.10.3 and ghc-head are also broken. :-(
I committed a246b6e6f8a33622d0be001391a9087820030134 and 8d36f159fa3dcdb2b8f4872787a4bf67748fd7db to the haskell-updates branch to fix.

Okay. Do you want me to do anything else with this?
Ofborg clearly shows that this doesn't make things worse, so I would just merge so that master would hopefully start to build again.


Compilation error on video_framework library

Hi guys,
First of all, thanks for the great job and for sharing the code, I am really excited about using it for my project. However, after successfully installing (not without pain) all the dependencies, when I tried to compile seg_tree_sample in the way indicated on the RADME, I got the following error from the video_framework library:
video_framework/libvideo_framework.a(video_writer_unit.cpp.o): In function video_framework::VideoWriterUnit::OpenStreams(std::vector<std::shared_ptr<video_framework::DataStream>, std::allocator<std::shared_ptr<video_framework::DataStream> > >*)': video_writer_unit.cpp:(.text+0x474): undefined reference to avformat_alloc_output_context2'
collect2: error: ld returned 1 exit status
CMakeFiles/seg_tree_sample.dir/build.make:115: recipe for target 'seg_tree_sample' failed
make[2]: *** [seg_tree_sample] Error 1
CMakeFiles/Makefile2:68: recipe for target 'CMakeFiles/seg_tree_sample.dir/all' failed
make[1]: *** [CMakeFiles/seg_tree_sample.dir/all] Error 2
Makefile:75: recipe for target 'all' failed
make: *** [all] Error 2
It might be some dependency error, but it seems more like a small bug on the library. Is there any way to fix it?
Thanks in advance!
Tanis

Hey Tanis,
This seems to be an issue with how you installed ffmpeg.
See https://github.com/ZoneMinder/ZoneMinder/issues/249 for a similar issue.
Try to uninstall it and compile it from source, also make sure you uninstall any old headers from past installations.
Let me know how that goes.

Tried removing ffmpeg (and as I learned libav-tools too, to avoid incompatibilities), and installed everything from source using the following guide ( I am working on Ubuntu 14.10:
https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu.
Now I get the following errors...
Building CXX object video_framework/CMakeFiles/video_framework.dir/video_capture_unit.cpp.o
/home/icub/icubTanis/video_segment/video_framework/video_writer_unit.cpp: In member function ‘virtual bool video_framework::VideoWriterUnit::OpenStreams(video_framework::StreamSet*)’:
/home/icub/icubTanis/video_segment/video_framework/video_writer_unit.cpp:127:53: error: ‘avformat_alloc_output_context2’ was not declared in this scope
video_file_.c_str());
^
/home/icub/icubTanis/video_segment/video_framework/video_writer_unit.cpp:144:32: error: ‘CODEC_ID_H264’ was not declared in this scope
codec_context_->codec_id = CODEC_ID_H264;
^
/home/icub/icubTanis/video_segment/video_framework/video_writer_unit.cpp:163:35: error: ‘CODEC_ID_MPEG2VIDEO’ was not declared in this scope
if (codec_context_->codec_id == CODEC_ID_MPEG2VIDEO) {
^
/home/icub/icubTanis/video_segment/video_framework/video_writer_unit.cpp:167:35: error: ‘CODEC_ID_MPEG1VIDEO’ was not declared in this scope
if (codec_context_->codec_id == CODEC_ID_MPEG1VIDEO) {
^
/home/icub/icubTanis/video_segment/video_framework/video_writer_unit.cpp:171:35: error: ‘CODEC_ID_H264’ was not declared in this scope
if (codec_context_->codec_id == CODEC_ID_H264) {
^
/home/icub/icubTanis/video_segment/video_framework/video_reader_unit.cpp: In member function ‘video_framework::VideoFrame* video_framework::VideoReaderUnit::ReadNextFrameImpl(const AVPacket&)’:
/home/icub/icubTanis/video_segment/video_framework/video_reader_unit.cpp:380:72: error: ‘av_rescale_q’ was not declared in this scope
format_context_->streams[video_stream_idx_]->time_base);
^
/home/icub/icubTanis/video_segment/video_framework/video_reader_unit.cpp: In member function ‘virtual bool video_framework::VideoReaderUnit::SeekImpl(int64_t)’:
/home/icub/icubTanis/video_segment/video_framework/video_reader_unit.cpp:411:33: error: ‘av_rescale_q’ was not declared in this scope
source_timebase);
^
video_framework/CMakeFiles/video_framework.dir/build.make:126: recipe for target 'video_framework/CMakeFiles/video_framework.dir/video_writer_unit.cpp.o' failed
make[2]: *** [video_framework/CMakeFiles/video_framework.dir/video_writer_unit.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
video_framework/CMakeFiles/video_framework.dir/build.make:103: recipe for target 'video_framework/CMakeFiles/video_framework.dir/video_reader_unit.cpp.o' failed
make[2]: *** [video_framework/CMakeFiles/video_framework.dir/video_reader_unit.cpp.o] Error 1
CMakeFiles/Makefile2:268: recipe for target 'video_framework/CMakeFiles/video_framework.dir/all' failed
make[1]: *** [video_framework/CMakeFiles/video_framework.dir/all] Error 2
I tried removing ffmpeg again and installing from PPA (http://www.noobslab.com/2014/12/ffmpeg-returns-to-ubuntu-1410.html), but I still get the same errors.
I assume this is an error with the FFMPEG installation too, but I cant tell where it went wrong :(


replace .boxplot()with .plot.box()

Replacing df.groupby('split').boxplot() with df.groupby('split').plot.box() in tests/test_weighted_pandas.py::test_BoxPlot() seems to avoid the problem where the plots in the later test_AreaPlot() non-deterministically believe their axes to be shared, which prevents them from setting the lower y limit to 0. The original tests only fail when this happens to only one of the two.
Seeing as this is occurring for unmodified pandas.DataFrames, I don't think this is something we can fix easily in anesthetic

[x] Check that this doesn't reduce coverage
[x] @williamjameshandley @lukashergt do you think it's appropriate to explicitly check that the lower y limit is 0? (they do not)

Let's see if this fixes the default in the next few PRs. Please squash and merge