Add a high-level API

An API which actually does end-to-end key derivation, ECDSA, Schnorr signatures, ....
it will probably need a accept a struct with function pointers for generating random bytes, hashing, ...
From #26, this needs support for deterministic signing.

I think this is done.


Errno 11 in FreeRTOS_errno_TCP.h is used twice

Errno 11 is used twice: https://github.com/FreeRTOS/FreeRTOS-Plus-TCP/blob/d7003598726cfaa4205f1a72e0546d1627d9b27e/source/include/FreeRTOS_errno_TCP.h#LL48C1-L48C1

Thanks for taking the time t o report this, but it is intentional and as expected - search for EAGAIN on https://man7.org/linux/man-pages/man3/errno.3.html.


Lazzy loading through loadChildren not working for child routes.

Issue:-
Routing is not happening in lazy loaded modules through loadChildren route configuration.
environment:-
angular-cli: 1.0.0-beta.24
node: 6.4.0
os: win32 x64
@angular/router: 3.4.2
@angular/compiler-cli: 2.4.2
localize-router: ^0.4.0,
ng2-translate: ^4.0.0,
main app routing:-
export const routes: Routes = [
{ path: '', redirectTo: 'login', pathMatch: 'full' },
{ path: 'login', component: LoginComponent }
{ path: 'web', loadChildren: 'app/modules/web/web.module#WebModule' }
];
web routing in WebModule:-
export const routes: Routes = [
{  path: 'web', component: WebComponent, children: [
{ path: 'home', component: HomeComponent }
]
}
];
Observed:-

When try to redirect to '/web'. WebModule file gets fetched from server in network and url changed to 'en/web'  but  blank page gets displayed with no error in console.
When try to redirect to '/web/home' :-  Uncaught (in promise): Error: Cannot match any routes. URL Segment: 'en/web/home'

Expected:- There should not be any error in console and child module should get fetched lazily with working child routes in url.

This is duplicate of #3


Moved imports into functions that use them

Changes to be committed:
modified: pandas/io/gbq.py
Moved google api imports into functions that call them, removed unused imports. This fixes #9713

cc @jreback @jacobschaer
I've tested this change and successfully pulled data from and pushed to GBQ with it.

@jreback good point. I've moved the Python3 check into the function that checks for compatibility with the google API

can you rebase
pls add a release note to 0.16.1

cc @jacobschaer
can you give a test out pls.

Rebase done and release note added.

@cgrin looks like you merged in something else.
see instruction on git-fu here

Alright, that should take care of that. Not sure what happened yesterday. This closes #9713 and #8327

@cgrin the _test_imports is still called somewhere (and is failing)

@jreback Looks like it's called in the test suite. Since the _test_imports function itself gone due to the imports happening on demand, should we remove this test? It's the test_requirements function (lines 32-36 of pandas/io/tests/test_gbq.py) raising the error, which is in turn called by each class in the file.

We could also bring that function into test_gbq.py, removing the imports that are no longer necessary.

you can change the tests. The idea is to have a series of tests:

that will allow importing of gbq and not call anything (e.g. to test that if the deps are not installed simply importing will not fail)
use to/read_gbq with deps installed (which IIRC the ci does), but since we don't have credentials, they skip gracefully (e.g. the expected expections happen)
'real' testing, currently done offline only (as credentials are necessary) that actually tests functionaility

Thanks. I opted to move this function into the test suite and remove the no longer needed imports. (Also rebased again as there has been some movement on the upstream repo). Hopefully this gets us where we need to be!

Looks like I missed a couple imports there. Apologies, I'm having issues getting the tests to run at all locally. 686ee7e should fix the compatibility tests.

@cgrin ok, looks good. if you could squash to a single commit would be gr8.
anything beyond the release note for #8327. e.g. would a user seeing this need to do anything?
this is prob not back-compat, but 0.16.0 is broken anyhow.....

Rebased one more time and squashed everything.
Regarding #8327, the run function has been deprecated since at least June 2013, so it's very unlikely that anyone would need to take any action. google-api-python-client already has a version requirement of 1.2.0, which was released in July 2013 and includes the run_flow function, so this is more of a cleanup to get rid of the warning on auth than anything else.

merged via https://github.com/pydata/pandas/commit/2cf4132c6c30d0a26dd4fa316aaa7579a4fcc1d3
thanks!


Add prepared statement caching for SQLite

This is the first pass at adding prepared statement caching to Diesel.
The query builder will still run, as we are using the SQL string as the
key. Eventually this will be replaced with a type identifier, but we're
not there yet.
Most of the groundwork is laid to apply this to PG as well, but to start
it only applies to SQLite. The cache is placed at the top of the struct
instead of the end to ensure that the statements are dropped before the
raw connection. I'm still trying to determine if the order that fields
are dropped is something we can rely on. We may need to come up with an
alternate implementation for that part of this.
The prepared statements are stored in a hash map, and not some sort of
LRU cache. This means that the memory growth here could be unbounded if
left unchecked. In practice though, there is an upper bound as long as
we exclude certain types of queries from the cache. In particular, we
need to exclude queries that can generate different SQL without the type
changing. Therefore, we apply the following rules:

ASTs containing the Many node are not cached (WHERE foo IN (?, ?, ?) type queries)
ASTs containing a SqlLiteral node are not cached
Insert statements are not cached
Update statements are not cached

There's an argument for allowing SqlLiteral nodes to be cached, but I
am erring on the side of caution here. We can't tell if you're
dynamically generating the SQL in that node or not, and allowing them to
be cached would require exposing controls to care about internals that I
want to keep internal for the time being.
This results in a healthy performance improvement across the board.
Before
test bench_selecting_0_rows_with_medium_complex_query         ... bench:      43,125 ns/iter (+/- 12,545)
test bench_selecting_0_rows_with_trivial_query                ... bench:       5,755 ns/iter (+/- 2,063)
test bench_selecting_10k_rows_with_medium_complex_query       ... bench:  22,090,236 ns/iter (+/- 7,078,394)
test bench_selecting_10k_rows_with_medium_complex_query_boxed ... bench:  20,322,178 ns/iter (+/- 5,829,031)
test bench_selecting_10k_rows_with_trivial_query              ... bench:   2,980,795 ns/iter (+/- 1,046,410)
test bench_selecting_10k_rows_with_trivial_query_boxed        ... bench:   2,894,526 ns/iter (+/- 829,044)

After
test bench_selecting_0_rows_with_medium_complex_query         ... bench:      16,414 ns/iter (+/- 4,357)
test bench_selecting_0_rows_with_trivial_query                ... bench:       1,187 ns/iter (+/- 296)
test bench_selecting_10k_rows_with_medium_complex_query       ... bench:  19,490,094 ns/iter (+/- 4,403,771)
test bench_selecting_10k_rows_with_medium_complex_query_boxed ... bench:  18,980,924 ns/iter (+/- 3,537,891)
test bench_selecting_10k_rows_with_trivial_query              ... bench:   2,873,268 ns/iter (+/- 1,174,266)
test bench_selecting_10k_rows_with_trivial_query_boxed        ... bench:   2,891,690 ns/iter (+/- 1,012,551)

We can probably structure this a little bit more "unsafely" to eliminate
the overhead of Rc and RefCell. A statement will never have more
than one reference at a time (and this is enforced by RefCell, since
basically every method on Statement requires &mut self). We could in
theory just "copy" the Statement struct instead. The code is
encapsulated to allow this, but the overhead of Rc<RefCell<>> isn't
high enough to justify it.

Review? @samphippen @mcasper @mfpiccolo

Your tests here seem legit, but you've got like a billion fiddly little boolean cases, are there any important ones that are missing?

I don't think so. The only important cases are the ones that return the literal false. The tests there were more to drive implementation than enforce anything specific. Perhaps I need to change the implementation to make this more clear, but all the "fiddly" cases are basically saying "I'm safe to cache if all of my components are safe to cache"


Remove version: Jackett.Jackett version 0.21.1451

404 - release deleted
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/Jackett/Jackett/releases/download/v0.21.1451/Jackett.Installer.Windows.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 918)


[$500] No tooltip on 3 dots for long workspace report name in settings->name

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.3.79-3
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1696842196883869
Action Performed:

Open the app
Open any long name workspace request money report or raise one and open
Click on header to open details page
Hover on 3 dots and observe that it displays complete workspace report name in tooltip
Click on settings
Hover on 3 dots in Name and observe that now no tooltip is displayed

Expected Result:
App should display tooltip on hover on 3 dots of long name workspace request money report in settings->name as it does on hover on 3 dots of name on details page
Actual Result:
App does not display tooltip on hover on 3 dots of long name workspace request money report in settings->name
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/38435837/71a68286-d622-4910-b65d-24edbacbcf0a
https://github.com/Expensify/App/assets/38435837/d0ca2682-e047-4cbc-9b7e-59444a0be73d

MacOS: Desktop

https://github.com/Expensify/App/assets/38435837/e3ec2504-2557-4df4-8274-366d13cdc3d5

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01232e8f9165a258c0
Upwork Job ID:<PHONE_NUMBER>169665024
Last Price Increase: 2023-10-09

Proposal
Please re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
in the following code we use the Text which doesn't place a tooltip whenever we have ellipsis
https://github.com/Expensify/App/blob/main/src/pages/settings/Report/ReportSettingsPage.js#L115-L120
https://github.com/Expensify/App/blob/main/src/pages/settings/Report/ReportSettingsPage.js#L165-L170
What changes do you think we should make in order to solve the problem?
As we do in the details page we should use the DisplayNames which has a property to set the tooltip on ellipsis:
the name:
<DisplayNames
  fullTitle={reportName}
  tooltipEnabled
  numberOfLines={1}
  textStyles={[styles.optionAlternateText, styles.pre]}
  shouldUseFullTitle
/>

the workspace field:
<DisplayNames
  fullTitle={linkedWorkspace.name}
  tooltipEnabled
  numberOfLines={1}
  textStyles={[styles.optionAlternateText, styles.pre]}
  shouldUseFullTitle
/>

POC

Forgot to mention that by making those changes, the full name will be shown only on hovering over the 3 dots

This looks like a simple bug, and I imagine the solution will be simple as well, so I decreased the bounty

@roryabraham bump!

Sorry for the delay, was mostly OOO

PR is ready!

Payouts due:
Issue Reporter: $50 @dhanashree-sawant
Contributor: $250 + $125 bonus @abzokhattab
Contributor+: $250 + $125 bonus @hoangzinh
Eligible for 50% #urgency bonus? Yes
Upwork job is here.

@hoangzinh please don't forget about the checklist!


Use cterm colors instead of gui colors

One advantage of of the original base16 is that it's possible to use with terminals that don't support true color (for example mosh). This implementation enables termguicolors, which breaks mosh. Is there a hard dependency on termgui or can the theme use ctermfg/bg instead?

cterm is not implemented and I don't have plans on implementing. I'm open to PRs which add it and I'll review.

Hey, this breaks colors if using base16-shell from tinted-theming
with this commit:

the commit before this one (3c6a56016cea7b892f1d5b9b5b4388c0f71985be):

or am I missing something here?

Try adding set termguicolors in your init file.

oh, thanks @RRethy, that fixed it for me! (used vim.o.termguicolors=true on lua for anyone wondering about that)

For lua, you should use vim.opt.termguicolors=true. As a general rule of thumb, vim.opt is preferred in init files.


Simultaneously create a file to copy to clipboard

As I understand it, it is currently impossible to create a file and copy it to a clipboard at the same time. Is this a limitation of Slilicon or is it just the way the plugin is designed?
If it's not a limitation of Slilicon itself, it would be great to be able to create an image and copy it to a clipboard at the same time.

Hi Ivan,
this is a limitation of silicon itself. If you supply the --to-clipboard and -o test.png flags, the output file is not written. Sure, one could work around that by calling the silicon command two times in sequence, but I think then it might be easier to just setup two keybindings in neovim for each use case and decide which one to use or both after one another. The end result will be the same.
But thank you for your suggestion and best wishes from Germany!
Michael.

Hi, thank you for your quick response.
Well, I see. In this case, I will choose what I need in a particular situation, whether to save to a file or to the clipboard.


Add International Journal of Pavement Engineering to _journal.tab

... link it to the style taylor-and-francis-harvard-v as described in their manuscript guidelines.
I hope this update is in the correct form and at the correct place.
(See https://forums.zotero.org/discussion/40818/style-request-internationa-journal-of-pavement-engineering/#Item_2)

I just updated generate_styles_from_data.rb (https://github.com/citation-style-language/utilities/commit/c761d679248a8927ca5a4b53908a825d7d8a9318). I haven't test it very heavily, but it seems to work just fine.
You can now create an optional "_extra.tab" file. It requires the same header and column order as "_journals.tab". Skipping and renaming work just as before (e.g., a title that exist in "_journals.tab", "_extra.tab" and "_skip.txt" is still skipped; same for renaming with "_rename.tab").
The output shows the number of overwritten styles, e.g.:
Generating styles...
Generated 9			Overwrote 2	aacr

excellent, thanks!
On Mon, Jan 19, 2015 at 10:13 PM, Rintze M. Zelle<EMAIL_ADDRESS>wrote:

I just updated generate_styles_from_data.rb (c761d67
https://github.com/citation-style-language/utilities/commit/c761d679248a8927ca5a4b53908a825d7d8a9318).
I haven't test it very heavily, but it seems to work just fine.
You can now create an optional "_extra.tab" file. It requires the same
header and column order as "_journals.tab". Skipping and renaming work just
as before (e.g., a title that exist in "_journals.tab", "_extra.tab" and
"_skip.txt" is still skipped; same for renaming with "_rename.tab").
The output shows the number of overwritten styles, e.g.:
Generating styles...
Generated 9         Overwrote 2 aacr
—
Reply to this email directly or view it on GitHub
https://github.com/citation-style-language/utilities/pull/14#issuecomment-70602125
.

--
Sebastian Karcher, PhD
Department of Political Science
Northwestern University

The main remaining limitation I see is that the "--replace" flag currently only works in combination with "--directory". It would be nice to use "-r" by itself so we can quickly see if the "utilities" repo is in sync with the "styles" repo.

Also, this is getting off-topic, but we still have a bunch of Elsevier styles that once upon a time were generated, but which are absent from the current metadata set: https://gist.github.com/rmzelle/d6bb971948077a78cdc7. It looks like some but not all are on Carles's list.

The documentation at https://github.com/citation-style-language/utilities/blob/master/generate_dependent_styles/README.mdown is now up-to-date as well.

I added the "International Journal of Pavement Engineering " style in https://github.com/citation-style-language/utilities/commit/fb424bd94d730f2785819764da3dc7233245d9b2 and https://github.com/citation-style-language/styles/commit/04023dffa627aeb79570c2db7dd4d5b8059c1293 . I changed the parent to "taylor-and-francis-harvard-x", since that's the parent of "taylor-and-francis-harvard-v".


[Refactor] Change layout to match docker img & create AutoNode lib

Needed for faster iteration and open source development.

Doing refactor, and migration off docker. Will PR after.


docs(cloud_firestore): Fixed docs typo

Description
No behavior was changed. Document was spelled as "documnent" in the description of the update method for the DocumentReference class. This was changed to the correct spelling of "document"
Related Issues
No related issues.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[X] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[X] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
[X] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[X] All existing and new tests are passing.
[X] I updated/added relevant documentation (doc comments with ///).
[X] The analyzer (flutter analyze) does not report any problems on my PR.
[X] I read and followed the Flutter Style Guide.
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[ ] I updated CHANGELOG.md to add a description of the change.
[X] I signed the CLA.
[X] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[X] No, this is not a breaking change.

Thank you :)


Add IntX and FloatX Converting Clamp Methods

Motivation
Comparable#clamp is fantastic, and it works very well. However, its signature allows any types for the clamp boundaries (implicitly requiring that self defines #< against the boundary types), and it returns the boundary directly if the boundary is non-nil and self is "outside" the clamping boundary.
This explanation is basically exactly the current implementation:
def clamp(min, max)
  return max if !max.nil? && self > max
  return min if !min.nil? && self < min
  self
end

source
I was recently messing with Float64#clamp, and found that it returns a union when the boundaries are integer literals:
a = (5.0).clamp(0,10)

puts typeof(a) # => (Float64 | Int32)

What I expected and desired was that the return type of #clamp would be the type of the value that was clamped.
Proposed Feature
I propose that we add custom clamping methods to each IntX and FloatX type. However, the Int subtype methods would have slightly different behavior from the Float subtype methods.
The Int subtype methods would take other integer types as the boundaries and, if self is outside of a boundary, return the boundary converted to self's type. So, for instance, for Int32:
def clamp(min : Int?, max : Int?) : Int32
  return max.to_i32 if !max.nil? && self > max
  return min.to_i32 if !min.nil? && self < min
  self
end

(Note: I'm retaining the nil semantics from the normal implementation, but I'm not mentioning them in my overall argument, since they should be irrelevant.)
I don't think we have to worry about overflow here if #clamp is called correctly because the boundary check will restrict the #to_X call to values that will fit in that type. I suppose that overflow is possible if you pass in a min that is larger than max, though.
Float subtypes, on the other hand, can be assigned to integer values as well, so they will take Number boundaries and return the boundary converted to self's type. So, for instance, for Float64:
def clamp(min : Number?, max : Number?) : Float64
  return max.to_f32 if !max.nil? && self > max
  return min.to_f32 if !min.nil? && self < min
  self
end

Problems with the Proposed Feature
The most obvious problem with the proposal is that it removes the possibility of intentionally using #clamp to change the type of a numeric value to a different numeric type. I don't know if this is an intended use case, but removing that behavior is a breaking change (a much bigger concern now that we're past 1.0).
The other problem is that there's a question of whether this is worthwhile at all. In my example at the beginning of this issue, I could just change the boundaries to floating point literals, and everything will work exactly as desired. That's not a huge hassle, and while the proposed implementation is very straightforward, it's also quite a lot of code overall that would not only need to be written but also need to be maintained.
Conclusion
I do think this would be a good standard library "ergonomics"/convenience feature, but I want to know what others think. The downsides aren't huge, but I'm not sure how widely useful this would be, either.

Yes, I think it should be expected that T#clamp(X, Y) returns T. X or Y are just boundaries meant for comparison. We can't enforce this generically for any type that is comparable with other types. But at least for number types this is easy to do.
The implementation can make use of self.class.new(min) for a generic solution. So no need for individual methods per type.

What if you clamp an int between two floats?

The motivation is to remove unintended union types. I suppose an alternative approach would be to cast the range values to the clamped type at the call side.
So, yeah maybe this doesn't need action.
Essentially it comes down to detailed semantics of a call like 1.clamp(1.5, 3):
Does it mean restricting a value on the scale of the data type to fit in the given range? Or does it mean to restrict a value to the given range and map out-of range values to the range boundaries? The current behaviour is the latter, but I'd assume that's mostly an implementation detail.
Is there any use case for the behaviour that in-range values and out-of-range values are different data types?

This seems to work fine:
module Comparable(T)
  def clamp(min : Number, max : Number)
    result_type = typeof(self + min + max)

    return result_type.new(max) if !max.nil? && self > max
    return result_type.new(min) if !min.nil? && self < min
    result_type.new(self)
  end
end

p!(
  typeof(1.clamp(2, 3)),
  typeof(1.5.clamp(2, 3)),
  typeof(1.5.clamp(2, 3.5)),
  typeof(1.clamp(2.5, 3)),
  typeof(1.clamp(2.5, 3.5)),
  typeof("good".clamp("hello", "wrong"))
)

Output:
typeof(1.clamp(2, 3))                  # => Int32
typeof(1.5.clamp(2, 3))                # => Float64
typeof(1.5.clamp(2, 3.5))              # => Float64
typeof(1.clamp(2.5, 3))                # => Float64
typeof(1.clamp(2.5, 3.5))              # => Float64
typeof("good".clamp("hello", "wrong")) # => String

Another alternative is to define clamp like def clamp(min : self, max : self) so there's no confusion: you always have to pass the same type everywhere.

Uses the already established type promotion strategy for the addition operator with typeof(self + min + max) is pretty neat. That looks like the best solution.

It might be good to define this just in Number, just in case.


Got syntax error when run lorri shell

Describe the bug
$ lorri shell
error: syntax error, unexpected ',', expecting ')', at /nix/store/lf7dqzyc68qm4d8q98dkilci7gfzzn2i-wrapped-project-nix-shell.drv:1:15

To Reproduce
Steps to reproduce the behavior:

install lorri service with home-manager
create a sample project
lorri init
lorri shell

Expected behavior

Metadata

$ lorri info --shell-file shell.nix
lorri version: 1.0
gc roots do not exist, shell_gc_root: "/home/qiaowan/.cache/lorri/gc_roots/2c1e7ca1c608aaf7b83417fb94f52595/gc_root/shell_gc_root"

$ uname -a
Linux NixOS 5.0.0-1032-azure #34-Ubuntu SMP Mon Feb 10 19:37:25 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Additional context

what is your nix version? This looks like a bug that existed in an older nix version (the .drv file is parsed as if it were a .nix file)

$ nix --version
nix (Nix) 2.3.1

you might be running into this issue: https://github.com/target/lorri/issues/159
Can you update to nix 2.3.2?

Update nix to 2.3.3
Jump to project folder, got
direnv: loading /data/development/haskell-realworld-example/.envrc
Mar 25 03:57:56.483 INFO lorri has not completed an evaluation for this project yet, expr: /data/development/haskell-realworld-example/shell.nix
direnv: export +IN_NIX_SHELL

and run lorri shell got same error.

@nodew
what happens if your run
nix-build /nix/store/lf7dqzyc68qm4d8q98dkilci7gfzzn2i-wrapped-project-nix-shell.drv

$ lorri shell
lorri: building environment... done
Mar 25 09:11:29.570 ERRO Build failed. No cached environment available.
Build error: Nix process returned exit code 1.
$ "nix-build" "--out-link" "/tmp/.tmpLP2wey/result" "--" "/tmp/.tmpYD6sbl/result"
error: syntax error, unexpected ',', expecting ')', at /nix/store/v6grdqrmszzyzax53qlakxfbz1ygrbam-lorri-wrapped-project-nix-shell.drv:1:15

$ nix-build  /nix/store/v6grdqrmszzyzax53qlakxfbz1ygrbam-lorri-wrapped-project-nix-shell.drv
error: syntax error, unexpected ',', expecting ')', at /nix/store/v6grdqrmszzyzax53qlakxfbz1ygrbam-lorri-wrapped-project-nix-shell.drv:1:15

$ nix-store --realise /nix/store/v6grdqrmszzyzax53qlakxfbz1ygrbam-lorri-wrapped-project-nix-shell.drv
these derivations will be built:
  /nix/store/v6grdqrmszzyzax53qlakxfbz1ygrbam-lorri-wrapped-project-nix-shell.drv
building '/nix/store/v6grdqrmszzyzax53qlakxfbz1ygrbam-lorri-wrapped-project-nix-shell.drv'...
warning: you did not specify '--add-root'; the result might be removed by the garbage collector
/nix/store/a3dr24qy7wj7fzs07rrcmqr1va58y0yq-lorri-wrapped-project-nix-shell

Interesting, so the bug in nix-build is still not fixed. I thought it was.
whoa, we had this on macOS a while ago: https://github.com/target/lorri/issues/179
But since you are on NixOS this means it’s not just a problem on macOS.
@nodew Can you upload the .drv file so we have an example of something that nix mistakes as a .nix file?

To be clear here, this is a bug we can fix by using nix-store internally, but because the original bug report in #179 seemed to have gone away, we didn’t prioritize this refactor.

I created an issue with a description of what needs to be done in order to fix this: https://github.com/target/lorri/issues/362

NixOS is indeed the machine name, not a nixos distribution, it's a Ubuntu server with nix shell.

whoa. :boom:


Is there any plans for support URI query parameters in DSN?

As described in https://www.rabbitmq.com/uri-query-parameters.html only Erlang client has ability to parse additional parameters in DSN. Quick look into code of golang client confirms that it really parses only base DSN (described in https://www.rabbitmq.com/uri-spec.html). Is there any plans for support additional URI parameters in golang client?

If someone contributes it, we would consider it.


after I keyed dotnet run, 4 'info' appeared and hung forever. windows 10

Problem encountered on https://dotnet.microsoft.com/learn/aspnet/hello-world-tutorial/run
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

As both the tutorial and the output of the command explain, to see the web app, you should navigate to http://localhost:5000 in your browser. Did you try that?

Let me show you fully:
Select the text that says: http://localhost:5000 and press Ctrl+Insert or just copy the URL that shows in your command prompt as shown in the image. (marked 1), paste the URL in your browser and voila, you will see your first .NET Core app running!
If you want to shut down the running server, press Ctrl+C

@TJ-beginner does this help?

yes. see attached.
thank you very much.
[image: image.png]
Regards,
TJ Foo
On Wed, Aug 26, 2020 at 4:24 AM Dan Moseley<EMAIL_ADDRESS>wrote:

@TJ-beginner https://github.com/TJ-beginner does this help?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/core/issues/5093#issuecomment-680251077, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQWB7XNIWXXRMCMORHZQZFLSCQMZHANCNFSM4QG2R2AA
.

Ok I'll close then. Thanks for confirming


Pipeline automation?

Hi there, Francesca Mancini sent a link to this repo and looks very interesting.
I was wondering if you're looking to implement any sort of automation to the pipeline? Eg. with the R package targets. There was a paper out recently which looked at the use of worklow management software (WMS) https://besjournals.onlinelibrary.wiley.com/doi/full/10.1111/2041-210X.14113 but there's loads of other tools out there (snakemake, airflow, galaxy etc.)
Basically, in our work we're also considering these tools and weighing up pros and cons of all the different tools out there for biodiversity analyses so would be interested if you're intending on automating and if you're planning on using any particular WMS?

Hi Simon, thanks for your interest! This project is in its infancy, but I'm trying to design it so that it can be automatically run from the command line, or even just automatically run monthly with the only thing we interact with being a run diagnostics report that lands in our emails. We haven't thought about any specific packages yet, but we'll give the paper and targets a look!


Update House committee membership using House XML data

Probably some review needed here, especially around subcommittees and joint committee handling.  Refs #276
committee_membership_sanity_check.py
HLIG    : 22
 HLIG01 : 10
 HLIG02 : 10
 HLIG03 : 10
 HLIG04 : 10
HSAG    : 46
HSAP    : 52
HSAS    : 62
HSBA    : 60
HSBU    : 33
HSED    : 39
HSFA    : 47
HSGO    : 38
 HSGO06 : 9
 HSGO24 : 14
 HSGO25 : 8
 HSGO27 : 10
 HSGO28 : 6
 HSGO29 : 8
HSHA    : 9
HSHM    : 30
HSIF    : 55
 HSIF02 : 17
 HSIF03 : 31
 HSIF14 : 31
 HSIF16 : 29
 HSIF17 : 22
 HSIF18 : 22
HSII    : 42
HSJU    : 41
 HSJU01 : 13
 HSJU03 : 26
 HSJU05 : 13
 HSJU08 : 17
 HSJU10 : 8
HSPW    : 61
 HSPW02 : 30
 HSPW05 : 37
 HSPW07 : 14
 HSPW12 : 48
 HSPW13 : 13
 HSPW14 : 32
HSRU    : 13
HSSM    : 18
 HSSM23 : 3
 HSSM24 : 4
 HSSM25 : 6
 HSSM26 : 6
 HSSM27 : 5
HSSO    : 9
HSSY    : 31
HSVR    : 21
 HSVR03 : 12
 HSVR08 : 8
 HSVR09 : 6
 HSVR10 : 9
HSWM    : 38
 HSWM01 : 11
 HSWM02 : 17
 HSWM03 : 11
 HSWM04 : 16
 HSWM05 : 15
 HSWM06 : 11
JCSE    : 13
JSEC    : 17
JSLC    : 9
JSPR    : 8
JSTX    : 9
SCNC    : 6
SLET    : 6
SLIA    : 15
SLIN    : 19
SPAG    : 17
SSAF    : 21
 SSAF13 : 0
 SSAF14 : 0
 SSAF15 : 0
 SSAF16 : 0
 SSAF17 : 0
SSAP    : 31
 SSAP01 : 13
 SSAP02 : 19
 SSAP08 : 7
 SSAP14 : 13
 SSAP16 : 18
 SSAP17 : 15
 SSAP18 : 20
 SSAP19 : 17
 SSAP20 : 16
 SSAP22 : 18
 SSAP23 : 11
 SSAP24 : 19
SSAS    : 27
 SSAS13 : 13
 SSAS14 : 15
 SSAS15 : 10
 SSAS16 : 12
 SSAS17 : 9
 SSAS20 : 11
 SSAS21 : 11
SSBK    : 23
 SSBK04 : 17
 SSBK05 : 11
 SSBK08 : 19
 SSBK09 : 13
 SSBK12 : 11
SSBU    : 23
SSCM    : 27
 SSCM01 : 0
 SSCM20 : 0
 SSCM22 : 0
 SSCM24 : 0
 SSCM25 : 0
 SSCM26 : 0
SSEG    : 23
 SSEG01 : 18
 SSEG03 : 18
 SSEG04 : 14
 SSEG07 : 14
SSEV    : 21
 SSEV08 : 0
 SSEV09 : 0
 SSEV10 : 0
 SSEV15 : 0
SSFI    : 26
 SSFI02 : 8
 SSFI10 : 19
 SSFI11 : 20
 SSFI12 : 16
 SSFI13 : 12
 SSFI14 : 3
SSFR    : 21
 SSFR01 : 11
 SSFR02 : 11
 SSFR06 : 11
 SSFR07 : 11
 SSFR09 : 11
 SSFR14 : 11
 SSFR15 : 11
SSGA    : 15
 SSGA01 : 11
 SSGA18 : 9
 SSGA19 : 11
SSHR    : 23
 SSHR09 : 15
 SSHR11 : 15
 SSHR12 : 19
SSJU    : 20
 SSJU01 : 9
 SSJU04 : 15
 SSJU21 : 9
 SSJU22 : 9
 SSJU23 : 11
 SSJU25 : 15
SSRA    : 19
SSSB    : 19
SSVA    : 15
There are 157 total entries, 47 committees and 110 subcommittees.

cc @danielschuman - Would you be up for :eyes:-ing this?

I did a couple of spot checks of committee membership totals and the script seems to have parsed the House Clerk's XML correctly, but the House Clerk's site seems to have some differences.  House Budget has 35 memberships currently while XML has 33.

Could it be that not everyone has been named to the committees yet? Happy
to check although Derek seems to have it in hand?
On Thu, Feb 16, 2017 at 7:44 PM, Derek Willis<EMAIL_ADDRESS>wrote:

I did a couple of spot checks of committee membership totals and the
script seems to have parsed the House Clerk's XML correctly, but the House
Clerk's site seems to have some differences. House Budget
http://clerk.house.gov/committee_info/index.aspx?comcode=BU00 has 35
memberships currently while XML has 33.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/unitedstates/congress-legislators/pull/436#issuecomment-280513863,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC0a0PMEtPGCGElPm1lEwx8zJ2Um7Nseks5rdO1qgaJpZM4MB83O
.

Weird.  Looks like there are 35 in the clerk XML now, even though the last updated date is still 2/10.  The senate's site is throwing a 404 for some of the XML's now, I'll run it again tomorrow and see...

Re-ran the script...
diff /tmp/before.txt /tmp/after.txt
< HSAS    : 62
---
> HSAS    : 61
11c10
< HSBU    : 33
---
> HSBU    : 35
14c13
< HSGO    : 38
---
> HSGO    : 41
22a22,27
>  HSHM05 : 8
>  HSHM07 : 8
>  HSHM08 : 11
>  HSHM09 : 8
>  HSHM11 : 12
>  HSHM12 : 8
30c35,40
< HSII    : 42
---
> HSII    : 43
>  HSII06 : 21
>  HSII10 : 21
>  HSII13 : 19
>  HSII15 : 11
>  HSII24 : 14
32,33c42,43
<  HSJU01 : 13
<  HSJU03 : 26
---
>  HSJU01 : 12
>  HSJU03 : 25
45c55
< HSSM    : 18
---
> HSSM    : 21
52,53c62,68
< HSSY    : 31
< HSVR    : 21
---
> HSSY    : 38
>  HSSY15 : 9
>  HSSY16 : 14
>  HSSY18 : 10
>  HSSY20 : 11
>  HSSY21 : 7
> HSVR    : 24
55,56c70,71
<  HSVR08 : 8
<  HSVR09 : 6
---
>  HSVR08 : 10
>  HSVR09 : 8
58c73
< HSWM    : 38
---
> HSWM    : 39
65,69c80,84
< JCSE    : 13
< JSEC    : 17
< JSLC    : 9
< JSPR    : 8
< JSTX    : 9
---
> JCSE    : 7
> JSEC    : 20
> JSLC    : 5
> JSPR    : 5
> JSTX    : 5
159c174
< There are 157 total entries, 47 committees and 110 subcommittees.
---
> There are 173 total entries, 47 committees and 126 subcommittees.

How are we handling joint committees? I see it's TODO'd in the code.
(Also if we're not using the old scraper code anymore, let's delete the function.)

thanks @konklone, cleaned those up and reran.
this is the changes from last time, some senate subcommittees got populated...
<  SSAF13 : 0
<  SSAF14 : 0
<  SSAF15 : 0
<  SSAF16 : 0
<  SSAF17 : 0
---
>  SSAF13 : 15
>  SSAF14 : 13
>  SSAF15 : 15
>  SSAF16 : 13
>  SSAF17 : 13
125,130c125,130
<  SSCM01 : 0
<  SSCM20 : 0
<  SSCM22 : 0
<  SSCM24 : 0
<  SSCM25 : 0
<  SSCM26 : 0
---
>  SSCM01 : 25
>  SSCM20 : 19
>  SSCM22 : 17
>  SSCM24 : 15
>  SSCM25 : 19
>  SSCM26 : 27

I did some more cleanup, and changed sorting to be by chamber if its a joint committee.
I tried using the download function instead of requests but can't see to get it to do the encoding properly.
-- name: Nanette Diaz Barragán
+- name: Nanette Diaz BarragÃ¡n

I added a printout of what leadership roles were found for a committee to help with sanity checking.  There is probably some cleanup needed like house members saying 'chair' versus senate saying 'chairman'
HLIG    : 22 | Chair, Ranking Member
 HLIG01 : 10 | Chair, Ranking Member
 HLIG02 : 10 | Chair, Ranking Member
 HLIG03 : 10 | Chair, Ranking Member
 HLIG04 : 10 | Chair, Ranking Member
HSAG    : 46 | Chair, Ranking Member
HSAP    : 52 | Chair, Ranking Member
HSAS    : 61 | Chair, Ranking Member
HSBA    : 60 | Chair, Ranking Member
HSBU    : 35 | Chair, Ranking Member
HSED    : 39 | Chair, Ranking Member
HSFA    : 47 | Chair, Ranking Member
HSGO    : 41 | Chair, Ranking Member
 HSGO06 : 9  | Chair, Ranking Member
 HSGO24 : 14 | Chair, Ranking Member
 HSGO25 : 8  | Chair, Ranking Member
 HSGO27 : 10 | Chair, Ranking Member
 HSGO28 : 6  | Chair, Ranking Member
 HSGO29 : 8  | Chair, Ranking Member
HSHA    : 9  | Chair, Ranking Member
HSHM    : 30 | Chair, Ranking Member
 HSHM05 : 8  | Chair, Ranking Member
 HSHM07 : 8  | Chair, Ranking Member
 HSHM08 : 11 | Chair, Ranking Member
 HSHM09 : 8  | Chair, Ranking Member
 HSHM11 : 12 | Chair, Ranking Member
 HSHM12 : 8  | Chair, Ranking Member
HSIF    : 55 | Chair, Ranking Member
 HSIF02 : 17 | Chair, Ranking Member
 HSIF03 : 31 | Chair, Ranking Member
 HSIF14 : 31 | Chair, Ranking Member
 HSIF16 : 29 | Chair, Ranking Member
 HSIF17 : 22 | Chair, Ranking Member
 HSIF18 : 22 | Chair, Ranking Member
HSII    : 43 | Chair, Ranking Member
 HSII06 : 21 | Chair, Ranking Member
 HSII10 : 21 | Chair, Ranking Member
 HSII13 : 19 | Chair, Ranking Member
 HSII15 : 11 | Chair, Ranking Member
 HSII24 : 14 | Chair, Ranking Member
HSJU    : 41 | Chair, Ranking Member
 HSJU01 : 12 | Chair, Ranking Member
 HSJU03 : 25 | Chair, Ranking Member
 HSJU05 : 13 | Chair, Ranking Member
 HSJU08 : 17 | Chair, Ranking Member
 HSJU10 : 8  | Chair, Ranking Member
HSPW    : 61 | Chair, Ranking Member
 HSPW02 : 30 | Chair, Ranking Member
 HSPW05 : 37 | Chair, Ranking Member
 HSPW07 : 14 | Chair, Ranking Member
 HSPW12 : 48 | Chair, Ranking Member
 HSPW13 : 13 | Chair, Ranking Member
 HSPW14 : 32 | Chair, Ranking Member
HSRU    : 13 | Chair, Ranking Member
HSSM    : 21 | Chair, Ranking Member
 HSSM23 : 3  | Chair
 HSSM24 : 4  | Chair
 HSSM25 : 6  | Chair
 HSSM26 : 6  | Chair
 HSSM27 : 5  | Chair
HSSO    : 9  | Chair, Ranking Member
HSSY    : 38 | Chair, Ranking Member
 HSSY15 : 9  | Chair
 HSSY16 : 14 | Chair
 HSSY18 : 10 | Chair
 HSSY20 : 11 | Chair
 HSSY21 : 7  | Chair
HSVR    : 24 | Chair, Ranking Member
 HSVR03 : 12 | Chair, Ranking Member
 HSVR08 : 10 | Chair, Ranking Member
 HSVR09 : 8  | Chair, Ranking Member
 HSVR10 : 9  | Chair, Ranking Member
HSWM    : 39 | Chair, Ranking Member
 HSWM01 : 11 | Chair, Ranking Member
 HSWM02 : 17 | Chair, Ranking Member
 HSWM03 : 11 | Chair, Ranking Member
 HSWM04 : 16 | Chair, Ranking Member
 HSWM05 : 15 | Chair, Ranking Member
 HSWM06 : 11 | Chair, Ranking Member
JCSE    : 7  | Cochairman
JSEC    : 20 | Chair, Vice Chairman
JSLC    : 5  | Chairman
JSPR    : 5  | Vice Chairman
JSTX    : 5  | Vice Chairman
SCNC    : 6  | Chairman
SLET    : 6  | Chairman, Vice Chairman
SLIA    : 15 | Chairman, Vice Chairman
SLIN    : 19 | Chairman, Ex Officio, Ex Officio, Ex Officio, Ex Officio, Vice Chairman
SPAG    : 17 | Chairman, Ranking Member
SSAF    : 21 | Chairman, Ranking Member
 SSAF13 : 15 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSAF14 : 13 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSAF15 : 15 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSAF16 : 13 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSAF17 : 13 | Chairman, Ex Officio, Ex Officio, Ranking Member
SSAP    : 31 | Chairman
 SSAP01 : 13 | Chairman, Ranking Member
 SSAP02 : 19 | Chairman, Ranking Member
 SSAP08 : 7  | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSAP14 : 13 | Chairman, Ranking Member
 SSAP16 : 18 | Chairman, Ex Officio, Ranking Member
 SSAP17 : 15 | Chairman, Ranking Member
 SSAP18 : 20 | Chairman, Ex Officio, Ranking Member
 SSAP19 : 17 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSAP20 : 16 | Chairman, Ex Officio, Ranking Member
 SSAP22 : 18 | Chairman, Ex Officio, Ranking Member
 SSAP23 : 11 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSAP24 : 19 | Chairman, Ex Officio, Ex Officio, Ranking Member
SSAS    : 27 | Chairman, Ranking Member
 SSAS13 : 13 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSAS14 : 15 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSAS15 : 10 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSAS16 : 12 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSAS17 : 9  | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSAS20 : 11 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSAS21 : 11 | Chairman, Ex Officio, Ex Officio, Ranking Member
SSBK    : 23 | Chairman, Ranking Member
 SSBK04 : 17 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSBK05 : 11 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSBK08 : 19 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSBK09 : 13 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSBK12 : 11 | Chairman, Ex Officio, Ex Officio, Ranking Member
SSBU    : 23 | Chairman, Ranking Member
SSCM    : 27 | Chairman, Ranking Member
 SSCM01 : 25 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSCM20 : 19 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSCM22 : 17 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSCM24 : 15 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSCM25 : 19 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSCM26 : 27 | Chairman, Ex Officio, Ex Officio, Ranking Member
SSEG    : 23 | Chairman, Ranking Member
 SSEG01 : 18 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSEG03 : 18 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSEG04 : 14 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSEG07 : 14 | Chairman, Ex Officio, Ex Officio, Ranking Member
SSEV    : 21 | Chairman
 SSEV08 : 0  |
 SSEV09 : 0  |
 SSEV10 : 0  |
 SSEV15 : 0  |
SSFI    : 26 | Chairman, Ranking Member
 SSFI02 : 8  | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSFI10 : 19 | Chairman, Ex Officio, Ranking Member
 SSFI11 : 20 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSFI12 : 16 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSFI13 : 12 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSFI14 : 3  | Chairman, Ranking Member
SSFR    : 21 | Chairman, Ranking Member
 SSFR01 : 11 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSFR02 : 11 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSFR06 : 11 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSFR07 : 11 | Chairman, Ex Officio, Ex Officio, Ranking Member, Ranking Member
 SSFR09 : 11 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSFR14 : 11 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSFR15 : 11 | Chairman, Ex Officio, Ex Officio, Ranking Member
SSGA    : 15 | Chairman, Ranking Member
 SSGA01 : 11 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSGA18 : 9  | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSGA19 : 11 | Chairman, Ex Officio, Ex Officio, Ranking Member
SSHR    : 23 | Chairman, Ranking Member
 SSHR09 : 15 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSHR11 : 15 | Chairman, Ex Officio, Ex Officio, Ranking Member
 SSHR12 : 19 | Chairman, Ex Officio, Ex Officio, Ranking Member
SSJU    : 20 | Chairman, Ranking Member
 SSJU01 : 9  | Chairman, Ranking Member
 SSJU04 : 15 | Chairman, Ranking Member
 SSJU21 : 9  | Chairman, Ranking Member
 SSJU22 : 9  | Chairman, Ranking Member
 SSJU23 : 11 | Chairman, Ranking Member
 SSJU25 : 15 | Chairman, Ranking Member
SSRA    : 19 | Chairman, Chairman, Ranking Member
SSSB    : 19 | Chairman, Ranking Member
SSVA    : 15 | Chairman, Ranking Member
There are 173 total entries, 47 committees and 126 subcommittees.

This still needs some work, it doesn't appear the clerk xml has Ex Officio members listed for some committees.  Its possible the xml publishing lags behind the website updating, but I'll try to reach out and ask.
The XML contains what it says on the website, Chairman / Chairwoman / Vice Chairman, while the current file contains Chair / Vice Chair.  Any concerns if we make the file match the website?

The House rules were updated a few years back to update chairman and
chairwoman should be changed to chair, etc.
On Fri, Mar 3, 2017 at 9:28 AM, Joel Collins<EMAIL_ADDRESS>wrote:

This still needs some work, it doesn't appear the clerk xml has Ex Officio
members listed for some committees. Its possible the xml publishing lags
behind the website updating, but I'll try to reach out and ask.
The XML contains what it says on the website, Chairman / Chairwoman / Vice
Chairman, while the current file contains Chair / Vice Chair. Any concerns
if we make the file match the website?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/unitedstates/congress-legislators/pull/436#issuecomment-283966752,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC0a0IYV2QTw42WHkmjBvSWucqlY0tiqks5riCN9gaJpZM4MB83O
.

I have a preference for normalizing to gender-neutral terms, but I'm also ok either way. If the strings change I may need to make a corresponding change on GovTrack, fyi, but that's ok.

Since the Clerk's site has a mix of Chair/Chairman/Chairwoman I thought it was the member's preference, like it is for Congressman/woman.
I reached out via the contact link on the clerk website about the ex oficio members being missing.  I compared the output of this with the master branch (needed to re-run in master branch since there are updates since 2 days ago) and the only differences i can find now are the ex oficio members.  So once this is resolved this should be good to go.

I just realized that the subcommittees that are missing the ex-oficio members have this in their description: "The chairman and ranking minority member are ex officio members of all subcommittees".  Ugh.  So, I guess the XML is accurrate after all, i just need to account for this.

There's also a few unusual circumstances of ex-officio. For example, the
speaker and minority leader are ex-officio members of the House Intel
Committee. Don't know whether that's captured in the data, too.
On Fri, Mar 24, 2017 at 12:14 PM, Joel Collins<EMAIL_ADDRESS>wrote:

I just realized that the subcommittees that are missing the ex-oficio
members have this in their description: "The chairman and ranking minority
member are ex officio members of all subcommittees". Ugh. So, I guess the
XML is accurrate after all, i just need to account for this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/unitedstates/congress-legislators/pull/436#issuecomment-289068796,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC0a0KpNSO6TIOV9xCZVmCQaPXityy3oks5ro-v8gaJpZM4MB83O
.

I just want to add this here since Issue #455 was closed in reference to this issue. But there is a minor inconsistency relative to Vice Chairs. Currently there is "Vice Chair", "Vice Chairman", and "Vice-Chair"

@dwillis ^

I've brought this branch up to date and it is probably ready to merge.
For a while the House Clerk website was missing committee information and so the XML member data file (which this PR tried to switch us to four years ago) was the only way to update the data. While bringing this PR up to date, I realized that the House Clerk site's pages at https://clerk.house.gov/committees/AG00 started showing membership information, and we could have continued scraping, but this is probably better in the long run.
The only issue is that we're guessing that minority-party rank 1 members are Ranking Members, since this is not indicated in the XML.
The diff is large. Using git show --minimal on the command line reduces the noise by half.


Allow reloading file from disk

This reads the currently displayed file from disk which is helpful for
files that change while being displayed in ov.
Reloading a file by default is bound to the R key.
Additionally when jumping to the end of the document it will always be
reloaded as well. This is similar to the behaviour of less.
Closes: #32

I thought rereading as is would be a problem for large files.
Therefore, we need to proceed more carefully.
Also, this pull request has other changes in it and cannot be merged.
Please separate pull requests by function.

It will be implemented in #139, so close it.
Thank you very much.


chore: upgrade to gradle 8.2

Issue #

N/A
Description of changes

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

closing in favor of https://github.com/awslabs/smithy-kotlin/pull/1013


added spacing so you can scroll all the way down

Before you couldn't scroll all the way down on any page because of the red footer. Now you can. Also cleaned up a little spacing on the contributors page so it looks a little cleaner.

Hey nice! Can you fix the conflicts

Looks like you have som issues with commits and files, Closing this but feel free to open a new pull request once you fixed this :)


The documentation website is down

Describe the bug
Time marches forward and things change in github it seems. Something has changed that causes the website to not render correctly. The github pages deployment action runs successfully, but the site doesn't render.
Not quite sure yet what the problem is.

Fixed by updating the doc-website.yml to point to the correct archive output directory


Bootstrap 4 - Selectpicker Dropdown/Dropup tiny

I've got the following code populating a select box from a mysql table...
<select class="form-control selectpicker" id="nominal" name="nominal" data-size="5" >
<?php
$nc_sql = "SELECT * from nom_code order by id";

$nc_result = $link->query($nc_sql) or die(mysqli_error($link));

while($row_nc = mysqli_fetch_array($nc_result))
 {
print '<option value='.$row_nc['id'].'>'.$row_nc['fulltext'].'</option>';
 }
?>
</select>

But this is the result...

I know Bootstrap 4 is in Beta and they've changed a bunch of code, but it seems somewhere the height is being overridden to just 18px. Is this an easy fix?

Nevermind, found the discussion about Bootstrap 4 not being supported yet.

bootstrap 4 is not supporting selectpicker, right?

Bootstrap 4 support has officially been added as a part of v1.13.0-beta, available here: https://github.com/snapappointments/bootstrap-select/releases/tag/v1.13.0-beta. Please post any issues in that repo from now on.

Bootstrap 4 support has officially been added in v1.13.0!


Responsive Components

I'm opening this issue to track the progress about responsive design. Adding mixins like suggested here is a good starting point. I'll be editing this issue to have a list of next actions. Help is very welcome.

[ ] Use drawer as navigation element with the chance of being always opened

AWESOME :)
@javivelasco When you next get a chance i'd like to ask you a couple of Qs about your plans moving forward

Great, reach me though Discord!

@javivelasco @soyjavi exciting to know you are making all components responsive in the future release, may I ask if this is still on track? roughly when you think this will be available? cheers

Yes it is @pixiez, but personally I'm not having too much time lately. Hopefully this week I'll try to open a new branch to work on it. It shouldn't take too long

@javivelasco thats would be very exciting features to have! thanks!

Any progress?

Not too much... Sadly I'm not having too much time to dedicate to the project lately, sorry :(

I'm sorry to ask again, but... is there any progress?

Nope, sorry. During time I can spend on React Toolbox these days I'm mostly fixing bugs and small feature requests. I need help to deal with this

Great work on the package so far, it's the best material implementation I've seen so far.
I've spent a little time looking at this. Any more thoughts on how his could be done? I noticed you have the break points already setup. Were you thinking global or module media queries?

Thanks for the time you're spending on it! :) I did not think too much about it but the breakpoints are already specified because they are documented in Material Design Spec. The best would be to get advantage of those variables and try to make every component look good on each screen size. But again, I did not think too much about it actually.

Hi everyone,
I think this would be great for implement in react toolbox:

It's really easy to implement a responsive layout only need add a S, M or L letter and a number between 1 and 12 like the google grid specification, as follow:
<div class="s12 m6 l4">
   some content or component
</div>

It mean have a div that use all 12 columns at small screen(100%), use 6 in medium screem(50%) and use 4 on large screem(33.3%). As you can see it's really easy and usefull.
Best regards!

any progress on responsive break points ?

We already have break points but there are no definitions to make all components look good into smaller screens. Since I'm not using the project in a responsive environment, contributions about this are very welcome!

@javivelasco  Need to do touch handling for NavDrawers, for closing them in mobile environments.

@sai-prasanna this should be easy. Check the CSS next implementation that has a complete rewrite of the Layout and check out to add a handler different from Click

What is the current status of this? Can responsiveness be expected in the near future or should we use different implementation of material design for React instead?


Add EventHanders to Page and ScrollView

Just added a couple of EventHandlers I'm currently missing.

Page.OnAppearing
Page.OnDisappearing
ScrollView.OnScrolled

Thank you again @Dreamescaper !

Thank you again @Dreamescaper !


Issue with Coinbase API grabbing Quote Currency

Hi all, I recently was using Coinbase Pro API and tried to switch over to the regular Coinbase API (Coinbase Advanced) and it appears to take the price of whatever crypto I'm trying to buy/sell, divide that by the funds in my Coinbase wallet, then tell me whatever the result is as my actual. (for example, $200 in wallet, with ETH $1600 per token, it will tell me that 200/1600 = 0.125 is my actual, and that my minimum is $200 when it's set to something else).
Is this because they updated the API? Is there a fix to this?

Coinbase API (Coinbase Advanced) is just not working it needs to be fixed :

scanner.py line 37 still getting api keys from configuration
scanner line 46 get_markets_24hr_stats function does not exist for coinbase AuthAPI
AppState.py line 223 is getting the min as the total (your case)
coinbase pro valid urls must be updated and refactored (same array too many places)
matplotlib must be updated to latest version and also the used styles
logbuysellinjson even when you set it to 1 it does not log orders into a json file

With  AppState.py line 223 is getting the min as the total (your case)  fixed by replacing the line with base_min = float(0) the app seems to work but guess what  no order is being fulfilled  it tells you that an order has been made but nothing actually happened
Basically I listed all bugs that i found in the hope that they will be fixed soon 😄


prevent compiler test to make exe out of DDS-client

Signed-off-by: Wim Van Loocke<EMAIL_ADDRESS>To make it possible to build the DDS via cmake's ExternalProject_Add as static library, it is necessary to run the compiler test only as a static library. This is possible via the CMAKE_TRY_COMPILE_TARGET_TYPE option.
This customisation allows you to add that option to the project.

Build status:

Linux
Windows

Build status:

Linux
Windows


Create hello-world-cl.c

Good copy-paste work! PR my repo.

I didn't copy paste...
Sent via the Samsung GALAXY S® 5, an AT&T 4G LTE smartphone
-------- Original message --------
From: Matthew Johnson<EMAIL_ADDRESS>Date: 10/21/2015  15:24  (GMT-08:00)
To: VJohnson1202/hello<EMAIL_ADDRESS>Cc: VJohnson1202<EMAIL_ADDRESS>Subject: Re: [hello] Create hello-world-cl.c (#1)
Good copy-paste work! PR my repo.
—
Reply to this email directly or view it on GitHub.


Add output with site info

In addition to the actual WQP data it would be good for each chl, doc, tss, etc... pipeline to have a chl_sites file or something that contains a simplified site index basically just siteid, lat, long and any other info that comes down from whatWQPdata queries.
Originally posted by @matthewross07 in https://github.com/rossyndicate/AquaMatch_harmonize_WQP/issues/84#issuecomment-2025336141

Addressed by https://github.com/AquaSat/AquaMatch_harmonize_WQP/pull/86


feat: add displayAsGrid props

Fixes #6

Please center the column and row labels vertically

In the Well picker controlled story, there is an option "Pick mode" which I think should be removed. It's probably left from before when the library exported only one component


docs: Update e2e-security demo diagrams

Needs additional textual description of what's to see in the pics

They will follow at some point of time when I find the time... :/

docs/modules/demos/images/end-to-end-security/overview.svg
needs polishing prio to publication

Any suggestions on what to polish? Eg:

Color scheme,
Boxes with rounded corneres,
Legend using icons or colored text instead of colored background
Dimensions/Aspect Ratio

Use this: https://stackable.tech/wp-content/uploads/2024/05/end2endsecuritydemo.png

@stackfab I pulled the new version from the slides. I did however export the png from google slides directly as it has a much better resolution. I hope that's ok

Could you add alt text to the images please? :innocent:


Update utils.py

On Windows, the file encoding 'utf8' has to be specified explicitly.

@offermann I never tested this library on Windows. Thanks you very much!
P.S If you find any more problems on your platform, then let me know, please.


Create PvMTickCounter

Adds total damage dealt for the local player/session
Also calculates combat ticks based on weapons used for local player as well as others in same instance.

Hello Would be possible to also tell how many times you did a max hit?.

Hello Would be possible to also tell how many times you did a max hit?.

Yes, I've was able to modify the code to do this. Not sure if I should wait for review in order to push this.

Made too many modifications, will resubmit when ready


Use hammerhead's native clearTimeout and clearInterval methods

Replace in code:
window.clearTimeout
window.cleartInterval

to
hammerhead.nativeMethods.clearTimeout
hammerhead.nativeMethods.clearInterval

Duplicate: https://github.com/DevExpress/testcafe/issues/431


Error seeding the database

Describe the bug
EF complains the databases does not exist. -Migrations should be applied before seeding.
Also the the index on Identity.Roles [NormalizedName] is Unique and will prevent same RoleName even per Tenant when seeding the db.
To Reproduce
Steps to reproduce the behavior:

run 'update-database'

Suggestion
Remove index on NormalizedName and add unique index on {normalizedname,tenantId}

I am currently making some changes to migrations..can you pull the latest code and try? Also, please remove any existing databases. It should work fine now.
As of indexing on Normalized Name & TenantId, could add your changes to the new code and raise a PR?

sure


Keypress/Keyrelease events on windows

handle_keydown and handle_keyup keyboard events handling in windows

Looks good to me

I've changed the event structure, so you will need to rebase the changes.

Going to close this since we now already have Windows keyboard events and this is pretty far behind master now, but the contribution is appreciated.


Update _fab.scss

Updated the mud-fab-extended classes width and height to match the one in the normal mud-fab class.

Description

Currently a FAB with a Label set, i.e. a mud-fab-extended, will not match the sizing of the standard, non-extended, FAB.

The height, min-width, and border-radius of an extended FAB should be equal to the standard FAB's height, width, and border-radius respectively.
How Has This Been Tested?
This is a visual change it's pretty straightforward. See below for screenshots.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Before:

After:

Checklist

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added relevant tests.

Probably requires feedback from @Garderoben

https://m3.material.io/components/extended-fab/overview

https://mui.com/material-ui/react-floating-action-button/

I'll defer this decision to @Garderoben

This was definitely an intentional design decision to align with Material Design 2 so I'll close this as Garderoben doesn't have the time to review


Graphics path not working on macOS

On macOS, the slides won't compile for me with the current graphicspath set. Therefore a / at the end of each path is needed (\graphicspath{{../pics/logos/}{../pics/uulm/}{../pics/nature/}} instead of \graphicspath{{../pics/logos}{../pics/uulm}{../pics/nature}}).

I just saw that this problem just exists on the main branch and is already fixed on release.


tests: Don't sleep in KillIntegrationTest

There was a sleep(100) to wait for the query which should be killed to
start executing.
Instead of that it will now always wait for a sys.jobs entry to
appear.
That was already the case anyway for tests using KILL <jobId> instead
of KILL ALLL.

@seut please review

lgtm


DBZ-2301 Hide internal config fields

https://issues.redhat.com/browse/DBZ-2301

Test failure unrelated.


⚠ Samsung has degraded performance

In f0c9af6, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2305 ms

Resolved: Samsung performance has improved in 55fafd8.


cassandra unittests assert decoded value

The removed test was removed because its now duplicated with the functionality of the improved tests.

Just rebased it incase there were any problems due to the other cassandra changes.


Docker image for JRE

Thanks for all the work on producing solid Docker containers for OpenJDK. 🙌🏼
Will there be Docker images for JRE based on JDK 17? I used to rely on JRE and eclipse-temurin:11-jre specifically, but for JDK 17 there are only images that include full JDK. Will it be up to users to rely on jlink and build their own containers for JRE?

Will there be Docker images for JRE based on JDK 17? I used to rely on JRE and eclipse-temurin:11-jre specifically, but for JDK 17 there are only images that include full JDK. Will it be up to users to rely on jlink and build their own containers for JRE?

Yes. See https://github.com/adoptium/temurin-build/issues/2683 Specifically: https://github.com/adoptium/temurin-build/issues/2683#issuecomment-905540240
Documentation: https://blog.adoptium.net/2021/08/using-jlink-in-dockerfiles/

@jerboaa Hey, thanks for sharing the tutorial. If possible, you should write a second tutorial that shows users how they can use ALL-MODULE-PATH to quickly make their own JRE within five minutes. At first, I was really struggling to get all the available modules, but still saving on space by cutting out all the sdk related components.
Image from my work
# Java runtime that we'll use to create a JRE
FROM eclipse-temurin:17-centos7 as jre-build

# Create a custom Java runtime
RUN $JAVA_HOME/bin/jlink \
         --add-modules ALL-MODULE-PATH \
         --strip-debug \
         --no-man-pages \
         --no-header-files \
         --compress=2 \
         --output /javaruntime

# Build custom JRE image on top of same base
FROM centos:7

# Insert our custom JRE
ENV JAVA_HOME=/opt/java/openjdk
ENV PATH "${JAVA_HOME}/bin:${PATH}"
COPY --from=jre-build /javaruntime $JAVA_HOME

# Apply other application details
[...]

This had a great impact on our completed application image. It went from 414 Mb too 272 Mb without sacrificing on any functionality. If you could add a second tutorial, and hightlight how great these minor changes are, then many people will stop asking for a JRE-17 build.

At first, I was really struggling to get all the available modules, but still saving on space by cutting out all the sdk related components.

@KevinAtSesam did you use jdeps? The modules listed in the far right column are those needed for your application.
./jdk-17+35/Contents/Home/bin/jdeps HelloWorld.class
HelloWorld.class -> java.base
   <unnamed>                                          -> java.io                                            java.base
   <unnamed>                                          -> java.lang                                          java.base

./jdk-17+35/Contents/Home/bin/jdeps HelloWorldGUI.class
HelloWorldGUI.class -> java.base
HelloWorldGUI.class -> java.desktop
   <unnamed>                                          -> java.awt                                           java.desktop
   <unnamed>                                          -> java.lang                                          java.base
   <unnamed>                                          -> javax.swing                                        java.desktop

Nah, I saved myself the fiddling and I just added all modules using ALL-MODULE-PATH. I must find a balance between the time it takes to maintain, and the effect it has on the size, and this solution gave me a simple middle ground.


Enable running tests on Helix (distributed workload platform)

Currently, running all ASP.NET Core tests can take hours, even with assembly parallelization. Other large .NET repos have used Helix, a platform for distributing and running workloads in parallel. We should setup our PRs and CI builds to use this.
Scenarios

Running tests without helix.
This must continue to work so contributors do not need to run tests on Helix. This should work via dotnet test for most projects (and/or Visual Studio Test Explorer).

Microsoft developers: running tests on Helix. Those with an access token to Helix should be able to run tests on Helix with a few simple parameters, such as build.cmd -helixTest /p:HelixApiToken=xyz123

CI: by default, PRs and CI builds run tests on Helix. build.cmd -ci.

Configuring Helix test settings can be done in the test's .csproj file.

<!-- MyTests.csproj -->
<Project Sdk="Microsoft.NET.Sdk">

    <PropertyGroup>
        <TargetFramework>netcoreapp3.0</TargetFramework>

        <!-- Projects can opt-out of Helix -->
        <DisableDistributedTests>true</DisableDistributedTests>

        <!-- By default, all test projects would run on the same set of platforms, as defined in $(DefaultTestPlatforms). Exact platform names TBD. -->
        <DefaultTestPlatforms>Windows10.x64;macOS.x64;Ubuntu16.x64</DefaultTestPlatforms>
    </PropertyGroup>

    <ItemGroup>
        <!-- Most projects should not need to specify. This would be set by default for all test projects. $(DisableDefaultTestPlatforms) can be used to opt-out. -->
        <DistributedTestPlatform Include="$(DefaultTestPlatforms)" Condition=" '$(DisableDefaultTestPlatforms)' != 'false' " />

        <!-- For special cases, projects can configure additional platforms -->
        <DistributedTestPlatform Include="Windows10.x86" />

        <!-- Projects can also Include/Exclude to filter the defaults -->
        <DistributedTestPlatform Include="$(DefaultTestPlatforms)" Exclude="macOS.x64" />
    </ItemGroup>

</Project>

cref https://github.com/aspnet/AspNetCore-Internal/issues/981 - additional details for the implementer

Note: currently submitting the helix job with the 92 work items for extensions (test projects * net461/netcore20/21) just on windows takes 20 minutes.  Each publish directory is around 15megs so that's around 1.3gigs which might account for why it takes so long :/

That number is likely to be even higher on aspnet/AspNetCore. We should coordinate with the Helix and corefx guys to see if there are tricks we can use to reduce the size of payloads.

Yeah, each target queue is another multiple too, so if we are targeting mac/linux/windows queues that's already an hour just to publish the 3 jobs for extensions :(

@natemcmaster good to close this or do we want this open to track further helix work?  There are a lot of projects/tests disabled (individual issues are tracking them but there's no meta issue tracking the full set), and there's also the open question of next steps, as keeping helix green is going to be a constant battle in the short term (between new tests that just don't work, and sporadic flaky tests which I've mostly skipped already)

There are still important action items on this. I wouldn't close it yet. From my perspective, the remaining work is

[ ] stabilize tests on Helix. This doesn't me @HaoK fixes them. Skipping + opening issues seems to be the only reasonable approach.
[ ] Merge the 'helix-test' definition with the main CI. Implication: this makes Helix tests required to pass to merge PRs/produce a release
[ ] Stop running tests on the CI build agents altogether.
[ ] Add docs in docs/ explaining how developers can run Helix locally.

Checklist for BuildHelixPayload = false projects

[ ] Authentication.AzureAd.FunctionalTests
[ ] DefaultBuilder FunctionalTests
[ ] Hosting functional tests
[ ] ServerCOmparision.FunctionalTests
[ ] MVC.Analyzers.Test
[ ] MVC.Api.Analyzers.Test
[ ] MVC.FunctionalTests
[ ] Identity.FunctionalTests
[ ] CORS FunctionalTests
[ ] Music Store FunctionalTests
[ ] AuthSamples FunctionalTests
[ ] IISExpress.FunctionalTests
[ ] dotnet-watch
[ ] Kestrel InMemory FunctionalTests
[ ] Components.Server.Tests
[ ] Components.E2E.Tests
[ ] ProjectTemplates

Files with skipped tests

[ ] src/Identity/test/Identity.Test/IdentityUIScriptsTest.cs
[ ] src/Identity/ApiAuthorization.IdentityServer/test/Configuration/ConfigureSigningCredentialsTests.cs
[ ] src/Identity/ApiAuthorization.IdentityServer/test/Configuration/SigningKeysLoaderTests.cs
[ ] src/Servers/Kestrel/Kestrel/test/GeneratedCodeTests.cs
[ ] src/Servers/Kestrel/test/Interop.FunctionalTests/H2SpecTests.cs
[ ] src/DataProtection/Extensions/test/DataProtectionProviderTests.cs
[ ] src/Components/Blazor/Build/test/RuntimeDependenciesResolverTest.cs
[ ] src/Components/Components/test/RendererTest.cs
[ ] src/Hosting/Hosting/test/WebHostTests.cs
[ ] src/Tools/FirstRunCertGenerator/test/CertificateManagerTests.cs
[ ] src/Servers/Kestrel/test/BindTests/AddressRegistrationTests.cs
[ ] src/Servers/HttpSys/test/FunctionalTests/HttpsTests.cs

@HaoK / @aspnet/build / @ajcvickers - what milestone should this be in?

Moved it to 6 for now.

@natemcmaster do we still need this meta issue open?  Moving to preview7 for now since preview6 is done

There are a bunch of checkbox lists in the comments above. If there are individual issues tracking those work, then I guess we could close this. I've been tracking this issue as I haven't seen any other issues open tracking the work get make Helix the default method of testing. Right now it's still an optional check that only runs on PRs.

Okay sounds like this is still the main issue tracking helix to be the default then

@HaoK we keep pushing this down the road without making changes to the issue. What is the current status?
If much is left open, especially if too much is on your plate to make further progress, suggest creating smaller issues and spreading them to team members with the most context in each test area.
/cc @anurse @mkArtakMSFT @ajcvickers @Pilchie

Since I think we have tracking items for all of the tests that aren't running on helix yet, this issue is mostly about making helix required for merging PRs, which is somewhat subjective.  The build team probably has more overall insight on how consistently the helix tests have been green.  But for my own personal PRs in the past month or so, helix runs have still almost always been red, which leads me to conclude its not ready to be a required check yet.
I will spend some time this week gathering more info and seeing what's causing the consistent failures (last time I looked it was a high amount of helix tests timing out due to queue contention)

Okay I think the issue with helix checks showing as red when tests pass with an automatic retries, for example in this PR today https://dev.azure.com/dnceng/public/_build/results?buildId=266896
Two tests passed on retry and the overview of the job shows green for these two tests (since they passed on rerun), but if you go to the individual work items you see the failures
All green overview:
https://mc.dot.net/#/user/aspnetcore/pr~2Faspnet~2Faspnetcore/ci/20190715.58.x64.1
Fireballs (even though they passed on rerun):
https://mc.dot.net/#/user/aspnetcore/pr~2Faspnet~2Faspnetcore/ci/20190715.58.x64.1/workItem/Sockets.FunctionalTests~2Fnetcoreapp3.0
https://mc.dot.net/#/user/aspnetcore/pr~2Faspnet~2Faspnetcore/ci/20190715.58.x64.1/workItem/IIS.NewHandler.FunctionalTests~2Fnetcoreapp3.0
I'll follow up with the helix folks to figure out how to ignore the failures if they pass on retry

@dougbu Has Helix become a priority again? My last understanding was that we were not prioritizing Helix currently.

@ajcvickers I commented because it wasn't clear whether the empty checkboxes were a true reflection of the current state nor whether this was now irrelevant given other issues. I didn't say we should change the issue's priority.
In any case, I don't remember exactly how we left Helix. I would be very interested in the technology if

it were more reliable
we partitioned the tests to use multiple agents per OS and sped things up significantly, making it a viable way to shorten our pipeline times
flaky tests were better supported

Side note: The Helix tests have found a few platform-specific issues we'd have otherwise missed.
A topic for our sync this afternoon…

@dougbu We do need to move to Helix; that is the plan. It's just not currently something we are spending time on.

Moving out of 3.0

Parked in backlog (not sure if 3.1 is more appropriate)

Closing this in favor of smaller tracking items now that helix is part of the required checks for builds


Live map shows stored caches only

It seems that the behaviour of the live map has changed recentöy:

It shows only the stored caches.
It shows found caches although I selected "Exclude own and found caches".

Do you see smiles on live map? If not you are not logged in!

Yes, I see the smilies on the live map (little smilies upon the normal cache icons).

I have just try it and it works with 31.10.2011 version.
Check your settings again and try to deselect and reselect the box again (don't forget to save changes by pressing back)

I am also using the "ver. 31.10.2011" and I deselected (+ press back) and selected (+ press back) the "Exclude own and found caches" box.
Still I have the two described problems.
The first problem bothers me a lot more than the second one.

Oh boy. A great feature with terrible misuse.
Press menu, enable live on live map.

Many thanks !!!
It seems, that "live" has been disabled either implicitely or accidentially.


Stopping an instance does not detach the disk

Description
It seems like when you stop an instance, the disk is still flagged as being "in use" (by itself).
This means that you can't start it again, without first running stop -f to detach the disk...

Is it Happening always ??
I tried normal flow (limactl start & limactl stop) and it was working fine the disk was detached

It happens with my "ceph" instance, probably related to it not doing a normal mount of the disk device?

[   15.183858] cloud-init[4431]: + sfdisk --label gpt /dev/vdb
[   15.189290] cloud-init[4431]: Checking that no-one is using this disk right now ... FAILED
[   15.189479] cloud-init[4431]: This disk is currently in use - repartitioning is probably a bad idea.
[   15.189785] cloud-init[4431]: Umount all file systems, and swapoff all swap partitions on this disk.
[   15.189944] cloud-init[4431]: Use the --no-reread flag to suppress this check.
[   15.190062] cloud-init[4431]: sfdisk: Use the --force flag to overrule all checks.
[   15.193441] cloud-init[4431]: LIMA| WARNING: Failed to execute /mnt/lima-cidata/boot/05-lima-disks.sh


Add link to spectrum chat

Checklist:

[x] Documentation
[ ] Tests N/A
[x] Ready to be merged

Deploy preview for govuk-react processing.
Building with commit ce66d2998ae8f8a79466ce8acd3902003584f5a8
https://app.netlify.com/sites/govuk-react/deploys/5c71456622be63000785a9af

Codecov Report

Merging #565 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #565   +/-   ##
=======================================
  Coverage   99.58%   99.58%
=======================================
  Files          88       88
  Lines         485      485
  Branches       38       38
=======================================
  Hits          483      483
  Misses          2        2

Continue to review full report at Codecov.

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


Feat/movieflix ui

Designed siginpage,signup page and Home page.
-Jithin

Designed signin,signup and home pages

Completed the project with localstorage as the storage data in angularjs.


Fix or disable erroring tests and enable FHIRPathSpecTest in the build

In  #374 I introduced a new TestNG test class for invoking the spec-provided FHIRPath tests.
I added skips for the easy stuff (e.g. when we throw UnsupportedOperationException), but we still have about 166 test cases failing.
FHIR does not use all of FHIRPath and so getting to 100% passing is a non-goal for our 4.0.0 release.
However, there are definitely some things in here that need to get cleaned up.
test-output.zip

Are #387 or #388 started yet?
I checked out master and I see that our results are looking pretty good:
Tests run: 679, Failures: 0, Skips: 206
However, there are a few test cases commented out in tests-fhir-r4.xml.
I assume tests-fhir-r4-old.xml was the original test file and we've updated it based on what we support.
I recommend removing tests-fhir-r4-old.xml altogether (git has the history) and adding comments to the commented out test cases to indicate why they are commented out.
For example, I see a few with comments like <!-- testWrong(patient(), "Encounter.name.given"); -->...does that mean if it doesn't have this comment then the test is likely valid?
What does it mean when we remove the "expected output" (output element) from the test xml?  Does that just cause us to skip the test?

I didn't add tests-fhir-r4-old.xml. I don't know where that file came from but I'm happy to remove it.

I don't know the meaning of Grahame's comments.

The skipped tests(skip=199, total=678) at this time are due to unsupported functionality that will come post R1.


Add cors support

Make the backend able to handle cors requests

curious why you are adding this? we already added cors access to all websites to handle this


A philosophical addition to the tale

Hi! Thanks for your submission.
Unfortunately it seems that there were changes in the main that conflict with yours.
Could you please perform a merge as described in Tutorial 2 slides 102-114 and integrate those changes?
Read the theory in slides 102-104 and then start the practice
by synchronizing your local and remote main with my upstream main as described in slide 105.
We do not want to lose any existing content, so you should keep what others have written and add yours.
You're free to reorganize the content blocks so that it still makes a story, but please do minimal changes
to the content of what others have written to integrate them with yours.
You have time until the 5th of October at 10:00am.
If you can't make it by that time or you are done before the deadline,
please add a comment in GitHub so that I can progress with another student.

Hi! I have resolved the conflict. Let me know if anything else is needed!

Thanks for your contribution! Task 2 completed! See canvas for results