Dynamic configuration of envoy for whitelisted IPs

Dynamic configuration of envoy for whitelisted IPs
Description:
I have a listener like this one below whitelisting some IPs using the RBAC filtering
`  listeners:

address:
socket_address:
address: <IP_ADDRESS>
port_value: 8080
filter_chains:
use_proxy_proto: true
filters:

name: envoy.tcp_proxy
config:
access_log:

name: envoy.file_access_log
config:
path: "/dev/stdout"
stat_prefix: ingress_tcp
cluster: my_service

name: envoy.filters.network.rbac
config:
stat_prefix: tcp.ip_restrictions.
rules:
action: ALLOW
policies:
"allow_trusted_ips":
permissions:
- any: true
principals:
- source_ip:
address_prefix: some.trusted.ip
prefix_len: 32
- source_ip:
address_prefix: <IP_ADDRESS>
prefix_len: 16`

Question:
Is there a way to dynamically update the envoy configuration with a new list of IPs without an envoy restart?
I guess LDS is my only option, but haven't seen a proper example of how to apply it.
Anyone working on a similar issue?

You would need to do this using LDS, which can be either GRPC/JSON-REST or file-based.
If you use a file for example, envoy will reload it every time it is modified. You could write something trivial to update the file periodically... or you can take a look at some of the control-plane libraries/implementations out there to provide the dynamic config via tcp.

https://blog.opstree.com/2020/04/07/preserve-source-ip-in-aws-classic-load-balancer-and-istios-envoy-using-proxy-protocol/


Fix RSA paramters check issue

Skip unused paramters checking in Non-CRT mode; since Non-CRT cares
about N, d, e only.

Hi @sliai, thanks for your contribution!
This issue was initially reported as https://github.com/ARMmbed/mbedtls/pull/474 and will be treated as part of PR #1060.
Also, note that due to the use of exponent-blinding in RSA, P,Q are necessary even when CRT is not used.
Kind regards,
Hanno

Hi @hanno-arm,
Thanks for your detail response.
As the code, the P, Q are necessary in NO_CRT on in condition "if( f_rng != NULL )".
And, in my case, we set f_rng as NULL.
Kind regards,
Edison

Hi @sliai,
note that with the changes of #1060 it will be possible to do CRT and/or blinding regardless of whether P,Q are passed when setting up the RSA context, so the issue is a temporary one.
You're right that as it stands, P,Q are not used when f_rng == NULL, and we'll consider making the check for P,Q conditional on that - thanks for pointing that out. Please note, though, that not providing a PRNG to the RSA private key primitive, and thereby disabling exponent blinding, comes at the risk of leaking information about the private exponent through side-channels.
Kind regards,
Hanno

Hi @hanno-arm,
The patch (#474 ) only add conditional check in mbedtls_rsa_check_privkey() function. Why not also add the parameter check which as I do in mbedtls_rsa_private(), it will be more stable. I am not sure if you have some reason for that in #1060.
Kind Regards,
Edison

Hi @hanno-arm,
Thanks for your remind.
We will add PRNG function to it at some later time.
Thanks for your help, I will close this PR.
Kind regards,
Edison

Hi @sliai,
I have adapted the code for #1060 to allow P,Q to not being set if CRT is not used and f_rng == NULL. Please note, though, that once this PR is merged, the recommended way to setup an RSA context is no longer by direct structure manipulation but instead via mbedtls_rsa_import and mbedtls_rsa_complete, and when using these functions, it is irrelevant whether P,Q are provided or not - they will be deduced if needed. In particular, should it have been the case that you called rsa_private without PRNG because it would require P,Q otherwise, you could change that after #1060 has been merged.
Thanks you for your contribution,
Kind regards,
Hanno


Drop label in HiddenSelect

🙋 Feature Request
If I understood correctly <HiddenSelect/> only needs a label so FireFox can "identify the <select>". Correct? That means it doesn't need be the actual label, but it could be a generated one? If yes this could help in adopting react-aria as tests like expect(result.getByText('Some Actual Label')).toBeInTheDocument(); don't need to be rewritten (this would currently fail with "You queried for ..., but two elements were found. Please use getAllByText().").

🤔 Expected Behavior
<HiddenSelect/> creates some randomized label for Firefox. Existing tests which query the actual label visible to the user will not be affected by adopting react-aria.

😯 Current Behavior

<HiddenSelect/> uses the same label which is also used for the frontend. This will likely create two <label/>'s with the same text content which might break tests which rely on just one label with that text content.
💁 Possible Solution

Create a randomized label.
Maybe there are other ways to easily hide the label during tests. (Or is it even save to not render <HiddenSelect/> in tests at all as it is just needed for browser form autofill, mobile form navigation, and native HTML form submission? This would at least help with unit tests, but E2E tests.)
🔦 Context

Adopting react-aria in an existing code base.

💻 Examples

🧢 Your Company/Team

🎁 Tracking Ticket (optional)

Thank you very much for looking into it.

The label usually does matter I think because it affects the behavior of autofill. Some browsers look for common labels like "email", "name", etc. and use this to inform how autofill behaves.


ASG Lifecycle Hook

What
A lambda that will respond to lifecycle events as worker nodes are removed from AutoScalingGroups
Why
To ensure that nodes are correctly cordoned and drained before before processes like the autoscaler or cloudformation can perform rolling updates safely.
Todo

[x] Implement a lambda func that can
[x] ...authenticate against the cluster
[x] ...cordon the node that triggered the scale-in event
[x] ...drain the node that triggered the scale-in event
[x] Build the lambda binary/zip in the release pipeline and upload to the github release
[ ] Terraform for lifecycle hooks to send cloudwatch events for the worker ASGs
[ ] Terraform to deploy the lambda zip from the release configured to watch events

update on my progress on Trello

Also need to change the CloudWatch Event Rule to filter for only this cluster's worker ASGs.

comments addressed and think I've sorted the event filtering


refactor RibbonCommand to an interface and factory

lays the groundworkd to implement an httpclient ribbon command
fixes gh-412

closed in favor of #498

Does that mean that SideCar now supports PATCH requests ?
If so which maven version should I use ?

@bogdatov this is a closed, out of date PR. See #498 which allows the possibility to create a client that supports PATCH.


Google+ counter sometimes has a dot, delimiting thousands.

This is not a float number. Sorry, I don't know how to use Grunt to minify the script.

Thanks!
“Sorry, I don't know how to use Grunt to minify the script” — please, never add any non-source code to pull requests.

OK. This sounds great!

Fixed in adce2e7.


LEAN-3911: remove ModelMap usages

Changes to import:
Old import used to do the following:

parse the front into models
parse the body into a node using jats-body-dom-parser
parse references and comments into models
encode the the body node into models
decode all the models into a manuscript node

New import:
Now we format the content we need from the article, and run it through the jats-dom-parser, preivously jats-body-dom-parser,
We now only need the decoder for jats-export on the api, technically the model map is our only source of truth as the document is always being updated. We can solve that by creating an originalDoc to use as a source of truth, and get rid of the decoder. (let me know your thoughts)
Changes to export:
I kept things simple, instead of looking for a specific model we look for the opposing node and fetch the content. I think ideally we'd use our serializer to transform all nodes, and then move the content as we like, but i wanted to keep it simple for now so we can easily debug it in case any errors are reported.
Please ignore the tests for now, i'll update these soon.

Regarding imports, can't we just replace json-schema types with their equivalent PM attrs type without extensive changes? e.g. replace BibliographyItem with the Attrs type in BibliographyNode.

Regarding imports, can't we just replace json-schema types with their equivalent PM attrs type without extensive changes? e.g. replace BibliographyItem with the Attrs type in BibliographyNode.

Just replace the types right? I think this applies to the manuscirpt, journal, and references models. I can change them but I'd like to confirm if that's what you meant.

Regarding imports, can't we just replace json-schema types with their equivalent PM attrs type without extensive changes? e.g. replace BibliographyItem with the Attrs type in BibliographyNode.

Just replace the types right and keep the original approach (format the article and send it through the parser)? Or do you want us to go with a different approach and generate the nodes directly?

Right, can we keep the logic and change the types?

I did recheck the comments and highlight nodes, and they do share the same ids in the older implementation.

The changes look generally OK, I'm guessing you're working on the tests.

The changes look generally OK, I'm guessing you're working on the tests.

Yeah, but i might move this to QA before finishing them up to speed things up if that's okay.

I feel this deserves a major release.

I feel this deserves a major release.

Sure, that feels right. I think Zax would merge all the PRs as major releases, so i'll do that manually.


Re-render on browser resize

First of all, thank you so much for the library. It's been invaluable in this project I'm working on. Thanks thanks.
I'm looking to have the sparkline be the entire width of the browser. The issue is when someone resizes the browser I have a function that is called that does a forceUpdate() on the React component. This doesn't re-render the component to the new div width. Only updating the data does that.
Any ideas?

shouldComponentUpdate() is the culprit. It causes a rerender only when the data changes.
Need to improve it to do so on any property change.

gotcha, so I’m guessing there’s no hacky trick I can do in the meantime?

On Sep 15, 2015, at 4:54 PM, Boris Yankov<EMAIL_ADDRESS>wrote:
shouldComponentUpdate() is the culprit. It causes a rerender only when the data changes.
Need to improve it to do so on any property change.
—
Reply to this email directly or view it on GitHub https://github.com/borisyankov/react-sparklines/issues/11#issuecomment-140583189.

Cool thing about React is, good solutions are usually easy to do.
I'll try to fix this today.
If you want to experiment, go to your node_modules folder find react-sparklines, open the .js file and remove the shouldComponentUpdate() and see if it works.

I published a new version, please try it out.

Hey Boris, thanks for looking into this. I've updated the files but it still doesn't update on resize.
var HeaderStats = React.createClass({
  getInitialState: function() {
      return {stats: []};
  },
  reRender: function(){
    this.forceUpdate();
  },
  componentWillMount: function() {
      window.addEventListener("resize", this.reRender);
  },
    render: function() {

        var headerHeight = document.getElementById('header').offsetHeight;
        var headerWidth = document.getElementById("header").offsetWidth;

        return(

          <Sparklines data={this.state.stats} width={headerWidth} height={headerHeight}>
            <SparklinesLine style={{ stroke: "#f00", fill: "none"}} />
            <SparklinesSpots size={0} style={{ stroke: "#f00", strokeWidth: 3, fill: "black" }} />
            <SparklinesReferenceLine type="mean" />
          </Sparklines>

        )

    }
});

Actually sorry, getting an error now within sparklines:
Uncaught TypeError: Cannot read property 'width' of nullshouldComponentUpdate @ index.js:143

which is:
 _createClass(Sparklines, [{
	        key: 'shouldComponentUpdate',
	        value: function shouldComponentUpdate(nextProps, nextState) {
	            var _this = this;

	            return nextProps.width != nextState.width || nextProps.height != nextState.height || nextProps.margin != nextState.margin || nextProps.data.some(function (d, i) {
	                return d !== _this.props.data[i];
	            });
	        }
	    }

@mbodge this is a separate issue #12 which is now fixed by #13 Please update to the latest version from npm.


BUG: dynamically changing of legend's position in options crashed chart.js

function isHorizontal is crashed if lineWidths - undefiened
** Test case** resize event change legend's position from "right" to "bottom" (dounaght) for less then XXXpx width.
if (isHorizontal) {
				cursor = {
					x: me.left + ((legendWidth - lineWidths[0]) / 2),
					y: me.top + labelOpts.padding,
					line: 0
				};
			}

TypeError: Cannot read property '0' of undefined
at ChartElement.draw (Chart.js:11785)
at Chart. (Chart.js:4382)
at Object.each (Chart.js:9899)
at Chart.draw (Chart.js:4381)
at Chart.render (Chart.js:4347)
at Object.callback (Chart.js:9876)
at Object.advance (Chart.js:3773)
at Object.startDigest (Chart.js:3746)
at Chart.js:3728
at nrWrapper (:10)

Why is lineWidths undefined? Can you include an interactive example (http://codepen.io/pen?template=JXVYzq)?

Closing due to lack of test case


Intended service reference text incorrectly omitted from rendered text description

Problem description

I saw a product documentation issue on the following URL:
https://www.pulumi.com/blog/managing-secrets-with-pulumi/

“This means when storing state with , we use a key managed by the service, specific to your stack”
The missing text, in two places, is a reference to the Pulumi backend service. It appears correctly in the github.com view, but not as rendered by Safari on iOS (at least).
Affected product version(s)

Suggestions for a fix
Format the service url differently. Test in Safari on iOS.

Thanks for pointing this out! I've submitted a PR to address this.


.gitignores for Microsoft Office

Reasons for making this change:
To exclude temporally files of Microsoft Office Applications.
Links to documentation supporting these rule changes:

Microsoft Word: .docx , .doc
Microsoft Excel: .xlsx , .xls
Microsoft PowerPoint: .pptx , .ppt

If this is a new template:

Link to application or project’s homepage: https://products.office.com/ja-jp/home

@smxshxishxad a Global/MicrosoftOffice.gitignore already exists - could you please open a fresh PR and add anything missing to that template?


Does it make sense to implement IntoFuture for js_sys::Promise?

As the title says: does it make sense to implement IntoFuture for js_sys::Promise? It seems that this would be a lot more ergonomic that having to manually write JsFuture::from(some_promise).await all the time.

I think it would make sense, but it's a bit technically difficult to pull off. js-sys would have to be the one to implement IntoFuture, which means we'd need to add a dependency on wasm-bindgen-futures to js-sys. But, wasm-bindgen-futures already depends on js-sys, which means we can't do that. We'd have to first change wasm-bindgen-futures to use custom bindings instead of js-sys, and then it'd be possible for js-sys to (probably optionally) depend on wasm-bindgen-futures and implement IntoFuture for Promise.

Right, for some reason I thought the IntoFuture could be defined inside of wasm-bindgen-futures but it is actually the js_sys crate that defines Promise...

Not to mention, it'll also increase the minimum supported Rust version for js-sys to when IntoFuture was stabilized


Updated Yahka to 0.12.0

RE-CHECK!

RE-CHECK!

Automated adapter checker
ioBroker.yahka

[ ] :heavy_exclamation_mark: [E150] No common.connectionType found in io-package.json
[ ] :heavy_exclamation_mark: [E152] No common.dataSource found in io-package.json
[ ] :heavy_exclamation_mark: [E502] "admin/img/info-big.png" not found, but selectID.js used in index_m.html
[ ] :heavy_exclamation_mark: [E300] Not found on travis. Please setup travis
[ ] :heavy_exclamation_mark: [E605] No actual year found in copyright. Please add "Copyright (c) 2016-2021 Jens Weigele<EMAIL_ADDRESS>at the end of README.md
[ ] :heavy_exclamation_mark: [E701] No actual year found in LICENSE. Please add "Copyright (c) 2016-2021 Jens Weigele<EMAIL_ADDRESS>at the start of LICENSE

Add comment "RE-CHECK!" to start check anew

Automated adapter checker
ioBroker.yahka

[ ] :heavy_exclamation_mark: [E150] No common.connectionType found in io-package.json
[ ] :heavy_exclamation_mark: [E152] No common.dataSource found in io-package.json
[ ] :heavy_exclamation_mark: [E502] "admin/img/info-big.png" not found, but selectID.js used in index_m.html
[ ] :heavy_exclamation_mark: [E300] Not found on travis. Please setup travis
[ ] :heavy_exclamation_mark: [E605] No actual year found in copyright. Please add "Copyright (c) 2016-2021 Jens Weigele<EMAIL_ADDRESS>at the end of README.md
[ ] :heavy_exclamation_mark: [E701] No actual year found in LICENSE. Please add "Copyright (c) 2016-2021 Jens Weigele<EMAIL_ADDRESS>at the start of LICENSE

Add comment "RE-CHECK!" to start check anew

@jensweigele Please see the checker comments from above for next release please!

@jensweigele Please see the checker comments from above for next release please!


remove jquery

Are you serious using jQuery for one simple thing? managing classes...
It can easily be replaced with this:
element.classList.contains("mdl-js-ripple-effect");
....
element.classList.add(html.join(' '))

its not only faster, but it also don't need to load a hole library that people don't use

Sounds reasonable...why not create a pull request?


Included JSON matching for body

Feature request:
Include JSON patch matching for request body in the withBody() matcher.
Like https://github.com/spotify/java-hamcrest#json-matchers

I guess you mean JSON path :)
HttpClientMock in current version works fine with json-matchers
  HttpClientMock mock = new HttpClientMock();
        mock.onGet("/aaa").withBody(isJsonStringMatching(
            jsonObject().where("foo", is(jsonInt(1)))
            )
        );

Do you need something more?

Yes, it works perfectly fine. My point was to include it inside library to make it more smooth :)

I've added a PR adding dependency to hamcrest-jackson.
However, the more I think about this "improvement", the less appealing whole idea seems to me...

Hi @jarst
Thanks for contributing to HttpClientMock.
I've looked at your PR. I agree that adding dependency is not a big improvement.
TBH I rather thought about adding a method like:
withBodyHavingJsonField('foo.bar', equal('some test'))
Before you start implementation please reach me and consult the proposition.


Update netty-buffer, netty-handler, ... to 4.1.115.Final

About this PR
📦 Updates

io.netty:netty-buffer
io.netty:netty-handler
io.netty:netty-transport

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

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

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

labels: library-update, commit-count:1

Superseded by #102.


Unable to access files in Shared storage for Windows Container

Hello Team,
First, a side note:

Please specify that Windows Containers, unlike App Service on Linux, is limited to Azure Files. And it does not support Azure Blob.

We're having an issue, although we're using Azure Files, we are unable to access (read/write) files after the path mapping, we see the directory but we can't cd into it.

Can we please get some information in regards to this issue?
And when would we be expecting a fix.
Thanks,

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bd52d297-e2d9-9a51-3ed6-05c33f521672
Version Independent ID: b9f21bef-4944-fbc1-c39c-7c2a0c939ce3
Content: Quickstart: Run a custom container on App Service - Azure App Service
Content Source: articles/app-service/quickstart-custom-container.md
Service: app-service
GitHub Login: @msangapu-msft
Microsoft Alias: msangapu

Hi @saifbadran9 , thank you for the detailed question. We are currently investigating and will update you when we have accurate information to provide.

Thank you @Grace, appreciated!

Hello @saifbadran9, did you see any errors when you tried to cd into the files? You can try running the AzFileDiagnostics script for Windows to detect what might be the issue. Also, could you please check if you have access to the storage account?

Hi @Grace, thanks a lot for following-up on this, and apologies for the delay in response.
Actually, no errors were seen, it just does not cd into the directory (stays on the same directory).
Anyways, we have been informed that this is a known platform issue related to Windows containers and shared storage, and it is fixed and being deployed globally (ETA: late December).
Thanks a lot for taking the time to look into this!
Only one thing related to the document, is to specify that Windows Containers, unlike App Service on Linux, is limited to Azure Files, and does not support Azure Blob.

Thanks for the update @saifbadran9!  I have submitted a PR to update the doc, the change will soon be merged internally and should go-live in the public docs shortly.


remove rapidjson, moved to main repo

It has been done in b59ae15120b9b75001ced9ad7fac9406064c5839. You need to run brew update to update your local tap.

Sorry...
I forgot that the diff of pull request in Github does not show the different between my branch and latest commit of master, so I didn't know this file had already be deleted.
Bitbucket does better in it :smile:  https://developer.atlassian.com/blog/2015/01/a-better-pull-request/


investigate netcdf load slowdown

See this comment
I don't think we need to worry about how this collides with the code refactors in   #6061 #6077
-- once we've worked out where it is + how to fix, that can probably be applied after the above changes land.

Closed by #6088


BUG in example .../evaluate_design/01_ten_bar_truss.py in posix

🐞 Description of the bug
Python node doesn't work:

FileNotFoundError: [Errno 2] No such file or directory: '/usr/ansys_inc/v232/optiSLang/slang/bin/slangMesa_x86_64'

📝 Steps to reproduce
Run example .../evaluate_design/01_ten_bar_truss.py on standart installation

(executable '/ansys_inc/v232/optiSLang/optislang')

Example works fine with standalone optiSLang though:

(executable '/opt/dynardo/ANSYS_optiSLang_2023R2dev/optislang')

💻 Which operating system are you using?
Linux
📀 Which ANSYS version are you using?
Version 23.2.0dev (3011)

[ ] remove mesa


Enabling labels creation support for instance creation method

Fixes #<issue_number_goes_here> (it's a good idea to open an issue first for discussion)

[ ] Tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

I signed it!
On Sat, May 12, 2018 at 8:46 AM, googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project (if not, look below for help).
Before we can look at your pull request, you'll need to sign a Contributor
License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here (e.g. I
signed it!) and we'll verify it.
What to do if you already signed the CLA Individual signers

It's possible we don't have your GitHub username or you're using a
different email address on your commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.

Corporate signers

Your company has a Point of Contact who decides which employees are
authorized to participate. Ask your POC to be added to the group of
authorized contributors. If you don't know who your Point of Contact is,
direct the Google project maintainer to go/cla#troubleshoot (Public
version https://opensource.google.com/docs/cla/#troubleshoot).
The email used to register you as an authorized contributor must be
the email used for the Git commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
The email used to register you as an authorized contributor must
also be attached to your GitHub account
https://github.com/settings/emails.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/googleapis/nodejs-bigtable/pull/133#issuecomment-388526075,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AlGVYaZG2OxM8wPLXBiRuhavkyxgLuAHks5txlQCgaJpZM4T8QVW
.

You should be able to remove the package-lock.json file from this PR. That's probably failing the lint task.


Improve node startup time

We have many tests to run, node startup was really slow, these changes speed it up:

Move sleep to end of client creation loop and reduce it to 100ms
Don't create wallet by default

It looks versions < 0.21 don't support this... And also I am afraid not creating the default wallet will break too much users code:
I would suggest:

A standalone PR with only the non-controversial "Move sleep to end of client creation loop and reduce it to 100ms" which I would merge right away
Another PR with a new configuration parameter like skip-default-wallet-creation, which is false by default so it keeps current behavior but that you can use in your tests to speed things up

It looks versions < 0.21 don't support this... And also I am afraid not creating the default wallet will break too much users code:
I would suggest:

A standalone PR with only the non-controversial "Move sleep to end of client creation loop and reduce it to 100ms" which I would merge right away
Another PR with a new configuration parameter like skip-default-wallet-creation, which is false by default so it keeps current behavior but that you can use in your tests to speed things up

I see, I didn't realize versions < 0.21 didn't support this. I'll modify this PR to include the changes you suggested!

There are still some issue in the CI, note I created a separated MR #83  for just the sleep thing (I think I am going to release a version soon, so I thought to include the easy part in the release)


Contact us content

Perform the following tasks for the Contact us page:

[x] Review for content design principles
[x] Get final accuracy approval from Christina/Alex
[x] Load into CMS

This may be a duplicate ticket. It's definitely done.


SASS Mixins

Es hora de actualizar ED-GRID para incluir los mixins de SASS.

Closed due lack of interest.


bug/<TypeError: unstructured.partition.common.add_element_metadata() got multiple values for keyword argument 'coordinates'>

Describe the bug
/app $ python3 docker_test/langchain_unstructured_test_pdf_to_text.py
INFO: pikepdf C++ to Python logger bridge initialized
INFO: Reading PDF for file: /app/example-docs/pdf/2409.12431v1.pdf ...
Traceback (most recent call last):
  File "/app/docker_test/langchain_unstructured_test_pdf_to_text.py", line 19, in <module>
    docs = load_and_process_pdf_structured(pdf_path)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/docker_test/langchain_unstructured_test_pdf_to_text.py", line 11, in load_and_process_pdf_structured
    for doc in loader.lazy_load():
  File "/home/notebook-user/.local/lib/python3.11/site-packages/langchain_unstructured/document_loaders.py", line 178, in lazy_load
    yield from load_file(f=self.file, f_path=self.file_path)
  File "/home/notebook-user/.local/lib/python3.11/site-packages/langchain_unstructured/document_loaders.py", line 212, in lazy_load
    else self._elements_json
         ^^^^^^^^^^^^^^^^^^^
  File "/home/notebook-user/.local/lib/python3.11/site-packages/langchain_unstructured/document_loaders.py", line 231, in _elements_json
    return self._convert_elements_to_dicts(self._elements_via_local)
                                           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/notebook-user/.local/lib/python3.11/site-packages/langchain_unstructured/document_loaders.py", line 249, in _elements_via_local
    return partition(
           ^^^^^^^^^^
  File "/home/notebook-user/.local/lib/python3.11/site-packages/unstructured/partition/auto.py", line 342, in partition
    elements = partition_pdf(
               ^^^^^^^^^^^^^^
  File "/home/notebook-user/.local/lib/python3.11/site-packages/unstructured/documents/elements.py", line 605, in wrapper
    elements = func(*args, **kwargs)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/home/notebook-user/.local/lib/python3.11/site-packages/unstructured/file_utils/filetype.py", line 731, in wrapper
    elements = func(*args, **kwargs)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/home/notebook-user/.local/lib/python3.11/site-packages/unstructured/file_utils/filetype.py", line 687, in wrapper
    elements = func(*args, **kwargs)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/home/notebook-user/.local/lib/python3.11/site-packages/unstructured/chunking/dispatch.py", line 74, in wrapper
    elements = func(*args, **kwargs)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/home/notebook-user/.local/lib/python3.11/site-packages/unstructured/partition/pdf.py", line 205, in partition_pdf
    return partition_pdf_or_image(
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/notebook-user/.local/lib/python3.11/site-packages/unstructured/partition/pdf.py", line 307, in partition_pdf_or_image
    elements = _partition_pdf_or_image_local(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/notebook-user/.local/lib/python3.11/site-packages/unstructured/utils.py", line 217, in wrapper
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/home/notebook-user/.local/lib/python3.11/site-packages/unstructured/partition/pdf.py", line 720, in _partition_pdf_or_image_local
    elements = document_to_element_list(
               ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/notebook-user/.local/lib/python3.11/site-packages/unstructured/partition/common.py", line 657, in document_to_element_list
    add_element_metadata(
TypeError: unstructured.partition.common.add_element_metadata() got multiple values for keyword argument 'coordinates'

To Reproduce
def load_and_process_pdf_structured(file_path: str):
    # Doesn't work
    from langchain_unstructured import UnstructuredLoader
    loader = UnstructuredLoader(
        file_path=file_path,
        strategy="hi_res",
        partition_via_api=False,
        coordinates=False, # doesn't matter true or false
    )
    docs = []
    for doc in loader.lazy_load():
        docs.append(doc)

    return docs

if __name__ == "__main__":
    pdf_path = "/app/example-docs/pdf/2409.12431v1.pdf"

    docs = load_and_process_pdf_structured(pdf_path)
    for doc in docs:
        print(f"\n{doc.page_content}")

Expected behavior
To run the code without error
Environment Info
I used the official unstructured docker image, in Windows 11, WSL 2

Hi - were you able to find the cause of this bug?

Ok - I figured it out. You have to remove coordinates=False from the code.  coordinates doesn't exist in the API for the constructor.
I was using Langhcain's Unstructured Docs and seems like they haven't updated it. It uses coordinates=True argument in the UnstructuredLoader Constructor while in the Langchain python API  for UnstructuredLoader constructor there isn't a mention of coordinates parameter.


Error Reading Skin Settings Json with Liquid Crystal Theme

Starting up GarlicPress gives me an error and I cannot see any roms from my device.
Error says:
CFW/skin/settings.json skin settings can not be loaded.
Preview will not display text position skin settings tool will not function.
Please report the skin you are using to issues in the About.
Error Text:
""" is invalid after a value. Expected either ',', '}', or ']'. Path: $ | LineNumber: 6 | BytePositionInLine: 1.
image

Windows 11
GarlicOS version: 1.4.9
Liquid Crystal theme (https://www.patreon.com/posts/83760135)

I might have edited my settings.json to fit images better. This is what is in my settings.json file:
{
"color-guide": "#1e2329",
"color-inactive": "#747870",
"color-active": "#1e2329",
"color-favorite-inactive": "#3f7fa0",
"color-favorite-active": "#1e2329"
"main-menu-text-visibility": true,
"guide-button-text-visibility": true,
"text-alignment": "left",
"text-margin": 352,
"recent-label": "~",
"favorites-label": "~",
"consoles-label": "~",
"retroarch-label": "~",
"rtc-label": "RTC",
"navigate-label": "~",
"open-label": "~",
"back-label": "~",
"favorite-label": "~",
"remove-label": "~",
"on-label": "ON",
"off-label": "OFF",
"am-label": "AM",
"pm-label": "PM",
"year-label": "YY",
"month-label": "MM",
"day-label": "DD",
"hour-label": "HH",
"minute-label": "MM",
"meridian-time-label", "MT",
"title-label": "%s"
"empty-label": "Should you favorite games? Yeah man!",
}

GarlicOS seems very insensitive for json structure and will let you break all sorts of JSON rules which garlicpress can't support.
based on the JSON you have posted I think you are missing a  "  ,  "  on the second to last line
if you replace this line with
"title-label": "%s",
does that fix the issue?

on second viewing  line 5 is also missing a ,
it should be
"color-favorite-active": "#1e2329",

Yes that fixed the error. There were a couple other things like
"meridian-time-label", "MT", → meridian-time-label": "MT",
and taking out the last comma in the second to last line.

awesome!
I will close this issue as its working now.


Existing Project

Everything is fine without any error...but I have a Question , Should I have to add something in activity.main.xml of my existing project or only write in main.java...as in README There is  code only for MainActivity.java, gradle,

Sorry, could you clarify. Is this issue about licensing?

There is error in my mainactivity.xml (my existing project) what i should write there?????

simple i have problem in launching chat sdk From my Existing project.....(If i skip launch on a button click will it Directly launch??)


Search text in strings resources with custom name (xxx-strings.xml)

I'm so sorry to be late review 🙇
And also so thank you for your contribution!!!
Looks good to me!


Fix #1047 - Properly escape newlines in multi-line strings

I converted \r\n|\n|\r all to \n. It seems like the right thing to do.

We should consider the CoffeeScript behavior for a compat flag eventually. Preserving the input might be wanted but I'll wait until someone actually asks for it.


D&D 5e Mancer Level+ : UC-10 - Bard, College of Lore needs to be able to select all Class Spells

Changes / Comments
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Closing this PR as I had to fix merge conflict #5510


Incorrect position of references count fo *.cs

VSCode Version: 1.7.1
OS Version: Windows 10 1607.14393.351

Steps to Reproduce:

Open any *.cs file and see that references counts are displayed at wrong position.

Sidebar is placed on left and closed

Sidebar is placed on right and closed

Sidebar is placed on left and opened

My user setting:
"editor.fontFamily": "Fira Mono",
"window.zoomLevel": 3,

I can agree, it happens on zoom:

When i go to normal zoom it is fine:

Same here, only on zoom (in or out)

I can reproduce also with pflannery.vscode-versionlens (any code lens)
@joaomoreno This was first introduced with ea8e2792723f8cc84507a877fd37420e6123139d
I think the issue is in contentWidgets.addWidget:
I believe the new logic needs to be better guarded. i.e. a content widget should get the new fixed treatment when:

configuration.editor.viewInfo.fixedOverflowWidgets is true
and the content widget must allow of overflow (widgetData.allowEditorOverflow).

Absolutely right, @alexandrudima !

cc @egamma @chrisdias @kieferrm


update relative links in readme to be absolute

relative links dont work when referenced by automated marker. using absolute links will fix this

Links to images and external resources in readme updated to absolute paths.


refactor: Jest configuration is now decoupled from package.json and can be easily customized and maintainable.

Description 📝
Decoupled jest configurations from package.json.
This improves maintainability of jest configurations.
How to test 🧪

Validate running unit test
Validate building the app and packages.
Validate running cypress tests

How do I run relevant unit or e2e tests?
yarn test
yarn cy:run

Nice!
Did using jest.config.ts not work? Our jest version might be too old to understand a .ts config file

I think .ts may need ts-node package to run the tests. May be that's due to older version.

I think .ts may need ts-node package to run the tests. May be that's due to older version.

Yea we'll need ts-node to run TypeScript files directly. You will also need ts-jest for this as well.
import type { Config } from '@jest/types';

const config: Config.InitialOptions = {
 // Configs...


fix: fromGraphQLToDart handler annotation

Currently the function names to convert the scalar are not consistent.
For the configuration
          scalar_mapping:
            - custom_parser_import: "package:my_app/graphql/custom_scalars.dart"
              graphql_type: timestamptz
              dart_type: DateTime

I get the generated code:
@JsonKey(
      fromJson: fromGraphQLDateTimeToDartDateTime,
      toJson: fromDartDateTimeToGraphQLtimestamptz)

I would expect to get:
      fromJson: fromGraphQLtimestamptzToDartDateTime,
      toJson: fromDartDateTimeToGraphQLtimestamptz

I think this is a breaking change, sorry about that.

Thank you for your work 👍

Please use latest beta to have less bugs.
Is seems to be fixed already there
https://github.com/comigor/artemis/blob/beta/lib/generator.dart#L465

Hey @abumalick!
Sorry for having those critical fixes only on beta branch, but we're still migrating a lot of stuff there and there will be a lot of breaking changes that we want to land on master at once!
I know how hard surpass those breaking changes can be on some projects, but eventually they'll need to be done once we merge beta on master.
So, could you try to use beta branch? I think there's a configuration that would make the transition easier:
targets:
  $default:
    builders:
      artemis:
        options:
          schema_mapping:
            - output: lib/.../output.dart
              schema: lib/schema.graphql <- Your schema needs to be converted to AST (if you're on  v5+, you're probably doing this already!)
              naming_scheme: simple # <- This naming scheme!
              queries_glob: lib/.../query.graphql

OK, thank you very much


[Bug] Players can't scroll to open doors

As a dm I am able to scroll to open a door but when my players try to nothing happens. There are no errors/warnings in console for me or my players when they attempt to

Could you send me a Screenshot of the error?

I don't get any errors on the dm side or the player side. It just doesn't do anything for them. It does stop the canvas from zooming though

Sorry misread that, can you send me screen shot of the doors setting. Also, did you make sure, that the players token is within the set interaction distance?

This might be a module conflict. I will run Find the Culprit before getting back to you

The issue is with the arms reach setting. The player is within the range of the door to open it but it stops the door from scrolling open

This happens as long as the arms reach option is selected. I set arms reach to use 10 which is perceptive's default and it still doesn't work but the 10 does work without arms reach

Just released v1.4.2 which should fix that bug

Thanks for being so responsive on these! It is working now


Add table of contents to Quick Start Guide

Quick start guide has TOC in notebooks, but not in the documentation.

This is not true:

Ok, for some reason it didn't seem like TOC in my head.


Cleanup pb packages

Need to simplify those pb types/names.

Done in the threading-model-refactoring branch


Add check suggesting permission macros

Probably needs some tweaking.

There is one catch: it cannot parse the original Refpolicy permission macros yet due to
https://github.com/SELinuxProject/refpolicy/blob/a7a327a9215bb8128a92be1fc46955149a47c75c/policy/support/obj_perm_sets.spt#L153-L156

Edit:
Can parse the original Refpolicy permission macros.
Current Refpolicy findings:
evolution.te:       420: (S): Suggesting permission macro: rw_inherited_fifo_file_perms (replacing { read write }, would add { ioctl getattr lock append }) (S-010)
xen.te:             132: (S): Suggesting permission macro: rw_inherited_fifo_file_perms (replacing { read write }, would add { ioctl getattr lock append }) (S-010)
systemd.te:         484: (S): Suggesting permission macro: relabel_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
systemd.te:        1164: (S): Suggesting permission macro: relabel_dir_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
systemd.te:        1167: (S): Suggesting permission macro: relabel_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
systemd.te:        1171: (S): Suggesting permission macro: relabel_dir_perms (replacing { relabelfrom relabelto }, would add { getattr }) (S-010)
systemd.te:        1172: (S): Suggesting permission macro: relabel_file_perms (replacing { relabelfrom relabelto }, would add { getattr }) (S-010)
init.te:            248: (S): Suggesting permission macro: create_blk_file_perms (replacing { create getattr }, would add (none)) (S-010)
init.te:            249: (S): Suggesting permission macro: create_chr_file_perms (replacing { create getattr }, would add (none)) (S-010)
virt.te:            463: (S): Suggesting permission macro: relabel_fifo_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
courier.te:         142: (S): Suggesting permission macro: rw_inherited_file_perms (replacing { read write }, would add { ioctl getattr lock append }) (S-010)
postgresql.te:      269: (S): Suggesting permission macro: read_lnk_file_perms (replacing { getattr read }, would add (none)) (S-010)
dbus.te:            229: (S): Suggesting permission macro: rw_inherited_file_perms (replacing { getattr read write }, would add { ioctl lock append }) (S-010)
boinc.te:           185: (S): Suggesting permission macro: rw_inherited_file_perms (replacing { read write }, would add { ioctl getattr lock append }) (S-010)
tpm2.te:             26: (S): Suggesting permission macro: rw_inherited_fifo_file_perms (replacing { read write }, would add { ioctl getattr lock append }) (S-010)
files.te:           222: (S): Suggesting permission macro: exec_file_perms (replacing { map execute execute_no_trans }, would add (none)) (S-010)
files.te:           223: (S): Suggesting permission macro: relabel_lnk_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
files.te:           224: (S): Suggesting permission macro: relabel_sock_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
files.te:           225: (S): Suggesting permission macro: relabel_fifo_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
files.te:           226: (S): Suggesting permission macro: relabel_blk_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
files.te:           227: (S): Suggesting permission macro: relabel_chr_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
devices.te:         384: (S): Suggesting permission macro: relabel_blk_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
devices.te:         385: (S): Suggesting permission macro: relabel_chr_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
devices.te:         386: (S): Suggesting permission macro: exec_file_perms (replacing { map execute execute_no_trans }, would add (none)) (S-010)
filesystem.te:      329: (S): Suggesting permission macro: exec_file_perms (replacing { map execute execute_no_trans }, would add (none)) (S-010)
filesystem.te:      330: (S): Suggesting permission macro: relabel_lnk_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
filesystem.te:      331: (S): Suggesting permission macro: relabel_sock_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
filesystem.te:      332: (S): Suggesting permission macro: relabel_fifo_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
filesystem.te:      333: (S): Suggesting permission macro: relabel_blk_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
filesystem.te:      334: (S): Suggesting permission macro: relabel_chr_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
storage.te:          58: (S): Suggesting permission macro: relabel_blk_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
storage.te:          59: (S): Suggesting permission macro: relabel_chr_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
kernel.te:          512: (S): Suggesting permission macro: relabel_dir_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
kernel.te:          513: (S): Suggesting permission macro: relabel_lnk_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
kernel.te:          514: (S): Suggesting permission macro: exec_file_perms (replacing { map execute execute_no_trans }, would add (none)) (S-010)
kernel.te:          516: (S): Suggesting permission macro: relabel_dir_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
kernel.te:          517: (S): Suggesting permission macro: exec_file_perms (replacing { map execute execute_no_trans }, would add (none)) (S-010)
kernel.te:          521: (S): Suggesting permission macro: exec_file_perms (replacing { map execute execute_no_trans }, would add (none)) (S-010)
kernel.te:          522: (S): Suggesting permission macro: relabel_lnk_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
kernel.te:          523: (S): Suggesting permission macro: relabel_sock_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
kernel.te:          524: (S): Suggesting permission macro: relabel_fifo_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
kernel.te:          525: (S): Suggesting permission macro: relabel_blk_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
kernel.te:          526: (S): Suggesting permission macro: relabel_chr_file_perms (replacing { relabelfrom relabelto }, would add (none)) (S-010)
gpg.if:              40: (S): Suggesting permission macro: rw_inherited_fifo_file_perms (replacing { read write }, would add { ioctl getattr lock append }) (S-010)
logging.if:         503: (S): Suggesting permission macro: relabel_file_perms (replacing { relabelfrom relabelto }, would add { getattr }) (S-010)
logging.if:         541: (S): Suggesting permission macro: relabel_dir_perms (replacing { relabelfrom relabelto }, would add { getattr }) (S-010)
logging.if:        1122: (S): Suggesting permission macro: relabel_dir_perms (replacing { relabelfrom relabelto }, would add { getattr }) (S-010)
sysnetwork.if:      464: (S): Suggesting permission macro: relabel_file_perms (replacing { relabelfrom relabelto }, would add { getattr }) (S-010)
init.if:           1289: (S): Suggesting permission macro: relabel_dir_perms (replacing { relabelfrom relabelto }, would add { getattr }) (S-010)
init.if:           2375: (S): Suggesting permission macro: rw_inherited_fifo_file_perms (replacing { read write }, would add { ioctl getattr lock append }) (S-010)
init.if:           2499: (S): Suggesting permission macro: rw_chr_file_perms (replacing { rw_term_perms lock append }, would add (none)) (S-010)
init.if:           2518: (S): Suggesting permission macro: rw_inherited_term_perms (replacing { getattr read write ioctl }, would add { append }) (S-010)
init.if:           2762: (S): Suggesting permission macro: write_file_perms (replacing { getattr open write }, would add { ioctl lock append }) (S-010)
init.if:           2855: (S): Suggesting permission macro: relabel_file_perms (replacing { relabelfrom relabelto }, would add { getattr }) (S-010)
userdomain.if:     3185: (S): Suggesting permission macro: relabel_dir_perms (replacing { relabelto relabelfrom }, would add (none)) (S-010)
userdomain.if:     3205: (S): Suggesting permission macro: relabel_file_perms (replacing { relabelto relabelfrom }, would add { getattr }) (S-010)
userdomain.if:     3304: (S): Suggesting permission macro: relabel_dir_perms (replacing { relabelfrom relabelto }, would add { getattr }) (S-010)
authlogin.if:       903: (S): Suggesting permission macro: relabel_file_perms (replacing { relabelfrom relabelto }, would add { getattr }) (S-010)
firstboot.if:       118: (S): Suggesting permission macro: rw_inherited_fifo_file_perms (replacing { read write }, would add { ioctl getattr lock append }) (S-010)
xserver.if:          73: (S): Suggesting permission macro: rw_inherited_fifo_file_perms (replacing { getattr read write ioctl }, would add { lock append }) (S-010)
xserver.if:         156: (S): Suggesting permission macro: relabel_file_perms (replacing { relabelfrom relabelto }, would add { getattr }) (S-010)
xserver.if:         159: (S): Suggesting permission macro: relabel_file_perms (replacing { relabelfrom relabelto }, would add { getattr }) (S-010)
xserver.if:         454: (S): Suggesting permission macro: rw_inherited_fifo_file_perms (replacing { getattr read write ioctl }, would add { lock append }) (S-010)
xserver.if:         737: (S): Suggesting permission macro: relabel_fifo_file_perms (replacing { getattr relabelfrom relabelto }, would add (none)) (S-010)
xserver.if:         810: (S): Suggesting permission macro: rw_inherited_fifo_file_perms (replacing { getattr read write }, would add { ioctl lock append }) (S-010)
postgresql.if:      334: (S): Suggesting permission macro: read_lnk_file_perms (replacing { getattr read }, would add (none)) (S-010)
dbus.if:            354: (S): Suggesting permission macro: relabel_dir_perms (replacing { relabelfrom relabelto }, would add { getattr }) (S-010)
fail2ban.if:        105: (S): Suggesting permission macro: rw_inherited_file_perms (replacing { read write }, would add { ioctl getattr lock append }) (S-010)
afs.if:              57: (S): Suggesting permission macro: rw_inherited_file_perms (replacing { read write }, would add { ioctl getattr lock append }) (S-010)
cron.if:             83: (S): Suggesting permission macro: rw_inherited_file_perms (replacing { getattr read write ioctl }, would add { lock append }) (S-010)
cron.if:            164: (S): Suggesting permission macro: rw_inherited_file_perms (replacing { getattr read write ioctl }, would add { lock append }) (S-010)
cron.if:            246: (S): Suggesting permission macro: rw_inherited_file_perms (replacing { getattr read write ioctl }, would add { lock append }) (S-010)
postfix.if:         262: (S): Suggesting permission macro: rw_inherited_fifo_file_perms (replacing { getattr write append lock ioctl read }, would add (none)) (S-010)
dirmngr.if:          32: (S): Suggesting permission macro: rw_inherited_fifo_file_perms (replacing { read write }, would add { ioctl getattr lock append }) (S-010)
ssh.if:             533: (S): Suggesting permission macro: rw_inherited_fifo_file_perms (replacing { write read getattr ioctl }, would add { lock append }) (S-010)
kernel.if:          273: (S): Suggesting permission macro: rw_inherited_fifo_file_perms (replacing { read write }, would add { ioctl getattr lock append }) (S-010)
kernel.if:         3100: (S): Suggesting permission macro: relabelfrom_file_perms (replacing { getattr relabelfrom }, would add (none)) (S-010)
kernel.if:         3119: (S): Suggesting permission macro: relabelfrom_lnk_file_perms (replacing { getattr relabelfrom }, would add (none)) (S-010)
kernel.if:         3138: (S): Suggesting permission macro: relabelfrom_fifo_file_perms (replacing { getattr relabelfrom }, would add (none)) (S-010)
kernel.if:         3175: (S): Suggesting permission macro: relabelfrom_sock_file_perms (replacing { getattr relabelfrom }, would add (none)) (S-010)
files.if:          5467: (S): Suggesting permission macro: relabel_dir_perms (replacing { relabelfrom relabelto }, would add { getattr }) (S-010)
files.if:          5772: (S): Suggesting permission macro: relabel_dir_perms (replacing { relabelfrom relabelto }, would add { getattr }) (S-010)
files.if:          7099: (S): Suggesting permission macro: add_entry_dir_perms (replacing { open getattr search write add_name }, would add { ioctl lock }) (S-010)
files.if:          7112: (S): Suggesting permission macro: rw_dir_perms (replacing { open read write remove_name add_name }, would add { ioctl getattr lock search }) (S-010)
terminal.if:        709: (S): Suggesting permission macro: rw_chr_file_perms (replacing { rw_term_perms lock append }, would add (none)) (S-010)
terminal.if:        768: (S): Suggesting permission macro: rw_chr_file_perms (replacing { rw_term_perms lock append }, would add (none)) (S-010)
terminal.if:        968: (S): Suggesting permission macro: rw_chr_file_perms (replacing { rw_term_perms lock append }, would add (none)) (S-010)
terminal.if:       1047: (S): Suggesting permission macro: delete_chr_file_perms (replacing { getattr unlink }, would add (none)) (S-010)
filesystem.if:     4740: (S): Suggesting permission macro: relabelfrom_lnk_file_perms (replacing { getattr relabelfrom }, would add (none)) (S-010)
Found the following issue counts:
S-010: 89

I'm looking over this and definitely excited to get this feature.
As a meta comment that I'm making here for lack of a better place to make it, I've been wanting to make a 1.1 release for a while.  I'd like to get this in it, because I think it will add a ton of value, and so I'm thinking about making sure everything looks good after this is merged and then calling it 1.1.0.  That would leave #130 for post 1.1 merge.  Anything else you want to get in before making a line in the sand?  Any significant bugs you're aware of that need fixing?

One small note: for the unit test I imported the original Refpolicy policy/support/obj_perm_sets.spt file (to tests/sample_policy_files/perms.spt) and added a GPL-2+ header to it.
One comment regarding 1.1.0:
I am thinking about whether the configure option to disable should be named --without-check instead --disable-check (autotools macro AC_ARG_WITH instead of AC_ARG_ENABLE).
Also should make check unconditionally fail in that case?

On the GPL topic, I'd prefer to avoid GPL licensed code in the repo.  Here's the Apache Foundations statement on Apache/GPL license compatibility: https://www.apache.org/licenses/GPL-compatibility.html
Does the specific situation of pulling in a test file apply there?  I'm not a lawyer and I'm not sure, but I think it's better safe than sorry.  I'd rather just write a handful of "define(foo', { read write }')" sorts of lines as needed for the test and avoid licensing concerns.
I agree that the convention on AC_ARG_WTIH fits our case better.  Are you planning on submitting a PR for that, or should I?
I would prefer to fail make check immediately if possible.  I haven't looked into what would be needed in the automake syntax to make that happen.

It's quite hard to come up with something else than the Refpolicy implementation:

the macro must end with _perms to be recognized as a permission macro
the class name (or an class alias) must stay before the _perms suffix to be applied to the correct class (e.g. chr_file_perms)
and writing define(`foo_chr_file_perms',`{ getattr open read write append ioctl lock }') instead of rw_chr_file_perms doesn't make sense

My impression is that the elements that are inherent to the problem are not-copyrightable (again, very much not a lawyer).  Would it make sense to come up with some new macros that aren't in refpolicy?  Something like define(\write_exec_file_perms', `{ append getattr open write ioctl lock }')`?

I'm satisfied.  Do you want to rebase the last two commits?


Cosmetic fixes

I made some cleanups. Code readability is an important thing to me. A method named display2() really doesn't mean much to someone reading this come who isn't familiar, or to even you or me when we read it 5 years from now. However displayFooter() makes it much more obvious what the code does.


Removed from system still came back

Nm i figured out I am a ding dong.

What are the steps you are taking to remove the software?
What operating system are you on?

nm I figured out sorry. lol


fix[numberText]: fix alignment in number text

Make it possible to have left aligned text that is vertically centered in the NumberText component.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Added dashboards for datastore stats and vm stats.

Added dashboards for datastore stats and vm stats. Also modified the original esx.json to make all three dashboards similar

Codecov Report

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

@@           Coverage Diff           @@
##           master      #99   +/-   ##
=======================================
  Coverage   91.64%   91.64%
=======================================
  Files           4        4
  Lines         455      455
=======================================
  Hits          417      417
  Misses         38       38

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 679e6e4...2d7236b. Read the comment docs.

Can you post a couple screenshots of these?

@pryorda  - Sure. Where do i post it though? (First time contributing to a project on git)

I would just add them to the readme. Describe them under graphs and monitoring or something?

Will do. I need to santize the dashboards though (bur out hostnames etc.). I will finish it and re-submit a PR, with the modified readme tomorrow.

I would just add them to the readme. Describe them under graphs and monitoring or something?

@pryorda - On second thought, i probably wont be able to post screenshots, because i dont have a test VMware cluster i can legitimately use for this purpose. Sry bout that.
But if anyone else from the community can help out here, that would be wonderful!

How come you removed get bool env?

How come you removed get bool env?

I dont recall removing it. Not sure how it got lost. But i have put it back again.
Also, regarding the dot Notation, my IDE does not seem to like it.
I get this error
Exception has occurred: ImportError attempted relative import with no known parent package   File "/Users/vkadudas/code/py/vmware_exporter/vmware_exporter/vmware_exporter.py", line 34, in <module>     from .helpers import batch_fetch_properties, get_bool_env   File "/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/runpy.py", line 85, in _run_code     exec(code, run_globals)   File "/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/runpy.py", line 96, in _run_module_code     mod_name, mod_spec, pkg_name, script_name)   File "/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/runpy.py", line 263, in run_path     pkg_name=pkg_name, script_name=fname)
I am using VS Code and Python v3.7.3. Any thoughts on how i can make my IDE accept the relative imports?

@cybervedaa Feel free to seperate them out. I feel I would be able to approve the landing pages faster then i can the dashboard.


Dio Smart Retry 6.0.0 not working; version 5.0.0 works fine

I updated dio_smart_retry to version 6.0.0 and retries stopped working, so I reverted back to version 5.0.0 — which works just fine.
By the way, I'm also using MultipartFileRecreatable due to multipart uploads.
See below how we are instantiating RetryInterceptor objects:
    List<Duration> retryDelays = const [
      Duration(seconds: 1), // waits 1s before the first retry.
      Duration(seconds: 2), // waits 2s before the second retry.
      Duration(seconds: 4), // waits 4s before the third retry.
      Duration(seconds: 8), // waits 8s before the fourth — and last — retry.
    ],
    final dio = Dio(BaseOptions(baseUrl: Env.url()));
    dio.interceptors.add(
      RetryInterceptor(
        dio: dio,
        logPrint: logger.warn,
        retries: retryDelays.length,
        retryDelays: retryDelays,
     ),
   );

ps: the dio version in pubspec.yaml is 5.6.0.

I think it was solved by #42. Fill free to reopen it if it's not.

Ok, I will check it out.


Sync master with release-4.15 branch

A few commits were not cherry-picked from 4.15 to master, I don't think this
was intentional.

One of these commits is also part of https://github.com/crc-org/snc/pull/872#issuecomment-2040210293 , I only saw this comment now ^^

/cherry-pick release-4.16


UNC/CIFS Share paths not working in linux version?

Steps to reproduce
#linux powershell
PS /> Set-Location //server/folder/
Set-Location : Cannot find path '//server/folder/' because it does not exist.
At line:1 char:1
+ Set-Location //server/folder/
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : ObjectNotFound: (//server/folder/:String) [Set-Location], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.SetLocationCommand

PS /> Set-Location \\server\folder\
Set-Location : Cannot find path '\\server\folder\' because it does not exist.
At line:1 char:1
+ Set-Location \\server\folder\
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : ObjectNotFound: (\\server\folder\:String) [Set-Location], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.SetLocationCommand

Expected behavior
#windows powershell 6.0
PS C:\Program Files\PowerShell\6.0.2> Set-Location \\server\folder\
PS Microsoft.PowerShell.Core\FileSystem::\\server\folder>
PS Microsoft.PowerShell.Core\FileSystem::\\server\folder> ls

    Directory: \\server\folder

PS Microsoft.PowerShell.Core\FileSystem::\\server\folder>

Actual behavior
its not connecting to the UNC/CIFS share on the linux version of powershell
Environment data

My CentOS 7 box does have the cifs-util installed to perform a mount -t cifs installed andIi can mount locally but looking to see if we can just open the connection to the share without having to mount anything.
#bash
[root@centos7 powershell]# dnf list installed | grep cifs
cifs-utils.x86_64                       6.2-10.el7                       @System

#powershell
> $PSVersionTable

PS /> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.1.0-preview.1
PSEdition                      Core
GitCommitId                    v6.1.0-preview.1
OS                             Linux 3.10.0-693.21.1.el7.x86_64 #1 SMP Wed Mar 7 19:03:37 UTC 2018
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

PS Microsoft.PowerShell.Core\FileSystem::\\server\folder> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.0.2
PSEdition                      Core
GitCommitId                    v6.0.2
OS                             Microsoft Windows 10.0.14393
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Think this is known issue posted sometime ago.  I think it was posted as an issue with the New-PSDrive cmdlet no able to work with CIFS settings or something.
:)

I wasn't able to find that issue or i would have posted there. your welcome to combine the issues. I have a PowerShell script I tried running on the Linux version that pointed didn't save the file into the network share like it suppose.

I'm looking for it because I mention it long time ago.  I'm using CIFS shared folders outside of PowerShell.
:)

Well! I guess I never did post nor comment about it.
:(
This feature could be useful if you can use the New-PSDrive to connect to an existing Shared folder.

Well! Circling back to this issue.
I notice this issue has been open since 2016 from the original issue which has been close without resolution.
Any idea now that we are reaching RC status? This should have been fixed by now.
:)

So, why not allowing the following: (At least for "smbfs")
New-PSDrive -Name "Linux/UnixfolderToMount" -Root "\\Server\ShareFolder" -PSProvider "smb"  -Credentials UserID@Hostname

:)

I'm currently trying to make our existing PowerShell 5 scripts compatible with PowerShell Core/6 and have ran into this issue on Mac. Windows PowerShell Core is able to connect to UNC (Samba) paths, but Mac PowerShell Core 6.2 cannot. It appears this issue has either been forgotten or is just not a priority. Has there been any work done to make this work?

@SteveL-MSFT I pinged Chris Bergmeister in slack to see if this might be something that would be resolved in PS 7. He suggested I ping you on this issue to ask.
My team is looking to leverage PS 7 on linux to migrate our PS 5.1 code and build servers over to PS 7 running on Linux. This is one of the issues I've ran into hindering us from migrating off of PS 5.1.

@Midacts the problem is that the Windows file system inherently handles SMB/CIFS paths so there's no special handling by PowerShell.  Linux/macOS does not.  One option is to leverage smbclient on Linux.  Or install OpenSSH on Windows and use SCP or SFTP across all your operating systems.

It makes sense. I've used smbclient on linux machines before.
Thanks for the reply.

It may be possible to enable this by calling out to smbclient but would require that command to be installed.

So the year passed without any implementation

Just ran into this now as well. I have been using Powershell Core 7 as a way to get my scripts to run cross-platform, so this is a bit of a snag. :(

To bad this isnt implemented.. needed this for copying some file from a share in linux and to some work with it. now i need more tooling

On top of it being very unfortunate that this ability doesn't exist for the mac and linux versions, but there is nary a mention of this in the documentation for New-PSDrive. We were moving forward with an implementation that used powershell on Linux and one of our use cases is mounting temporary windows shares. Imagine my surprise that it doesn't think any of our shares exist.

And now we're yet another year later. No mention of a fix, and nothing in the documentation to say it doesn't work for non-windows platforms.

what's the point of bringing powershell to linux if you can't even use literally the most common task for system administrators to do inside of a org.
Even if it is a supper janky and very slow method of copying files, it would be great. having nothing is a joke.

OK i figured out a way to copy items from the powershell 7.2 linux to a windows smb share but it's hacky. Better than no option at all.
$D = "/mnt/win_share"
$Files2Copy = ((get-childitem /home/administrator)) | where-object{$_.LastWriteTime -lt ((get-date).AddDays(-30))}

#running bash command inside of a .ps1 file
"mount -t cifs -o username=Administrator@domain.com,password=123 //<IP_ADDRESS>/smb_share /mnt/win_share" | bash

foreach($file in $Files2Copy){
  copy-item ($file).FullName $D
}

"umount /mnt/win_share" | bash

basically we are piping a command line argument string into bash. This is not the intended way of normally doing things since new-psdrive is off the table, but at least we can get some milage.
I think the default behavior to map a drive in linux should do a synthetic mapping of the /mnt drive, just so system administrators don't need to research for hours to come up with a solution.

Any updates?


Migrations: Scaffold MaxLength

When I apply
[StringLength(60, MinimumLength = 3)] //nvarchar(MAX) to nvarchar(60)

to my existing model, EF doesn't pick up this change.
To repro:

Create a model with string and no DataAnnotations.
add migrations/update
apply [StringLength(60)0

EF doesn't detect the change.
#5224 <-- NOT NULL is detected but not enforced

Tested this with nightly builds
The generated migration file does not have string length changes
    public partial class StringLength : Migration
    {
        protected override void Up(MigrationBuilder migrationBuilder)
        {
            migrationBuilder.AlterColumn<string>(
                name: "Name",
                table: "Entity",
                nullable: true);
        }

        protected override void Down(MigrationBuilder migrationBuilder)
        {
            migrationBuilder.AlterColumn<string>(
                name: "Name",
                table: "Entity",
                nullable: true);
        }
    }

On the other hand model snapshot is updated to account for change in length.
                    b.Property<string>("Name")
                        .HasAnnotation("MaxLength", 50);

Also the generated migration script has alter column statement.
ALTER TABLE [Entity] ALTER COLUMN [Name] nvarchar(50);
GO
INSERT INTO [__EFMigrationsHistory] ([MigrationId], [ProductVersion])
VALUES (N'20160429195756_StringLength', N'1.0.0-rc3-20747');

Interesting... I guess we are reading the length information out of the target model snapshot... we should stop doing that 😄

@Rick-Anderson this means that everything should work... but it's obviously super confusing that the length isn't in the generated code. We'll keep this open to address that, but it shouldn't block you.

@rowanmiller  it's not blocking, I just thought you might want to know. I've finished all the scaffolding and have everything working with RC2.

We'll discuss when @bricelam is back

Could this be related to #4146?

@rowanmiller, @bricelam  I have looked into this and the problem seems to be that the MigrationsAnnotations.For(target) in this line returns an empty enumerable as the provider implementation does not include the max length:
public override IEnumerable<IAnnotation> For(IProperty property)
        {
            if (property.SqlServer().ValueGenerationStrategy == SqlServerValueGenerationStrategy.IdentityColumn)
            {
                yield return new Annotation(
                    SqlServerFullAnnotationNames.Instance.ValueGenerationStrategy,
                    SqlServerValueGenerationStrategy.IdentityColumn);
            }
        }

Maybe the correct thing would be to yeild the core annotations in the default implementation and then iterate over them in the provider specific versions?
To allow custom annotations to "flow through", is the recommended way then to override the For() methods, include the new whitelisted annotations, and then replace the SqlServerMigrationsAnnotationProvider when setting up DI?

... and while you are at it, In MigrationsModelDiffer, could you insert CopyAnnotations(MigrationsAnnotations.For(target), operation); right after the creation of the DropTableOperation() here :-) I need it to control whether a table should be dropped or not.

@rowanmiller said:

Interesting... I guess we are reading the length information out of the target model snapshot... we should stop doing that 😄

Correct. The column builder API does not include any facets. Instead, the property (or just its CLR type) is passed to the provider's type mapper where it decides what metadata to look at.

Check that hard coded data types are also written to the scaffolded migration

We decided to add maxLength, unicode & timestamp to the Migrations APIs.

@bricelam will that make it with the RTM preview tooling ?

@Rick-Anderson Yes, a PR is out for review now.


Syntax highlighting not working after comment

Adding a comment like the following
--   𝕁 = Obj : Context Type

confuses agda-mode completely. For example,

I can confirm that the syntax highlighting works for the same code under Emacs' agda-mode.

Issue reproduced, thanks for reporting this.

Related issues:

https://github.com/microsoft/vscode/issues/34497
https://github.com/microsoft/language-server-protocol/issues/376
https://github.com/github/semantic/pull/580


add PPHumanSeg from paddlehub conversion

[x] PPHumanSeg and demo implementation
[ ] Benchmark support and results for PPHumanSeg

cc @kaingwade @zihaomu

@wjj19950828 Thanks for the review. Changes have been done for your comments.


python310Packages.inquirer: 3.1.1 -> 3.1.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.inquirer is: A collection of common interactive command line user interfaces, based on Inquirer.js
meta.homepage for python310Packages.inquirer is: https://github.com/magmax/python-inquirer
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.1.2 with grep in /nix/store/yss20s7yfn4rr359yhyv4pr515w44f2b-python3.10-inquirer-3.1.2
found 3.1.2 in filename of file in /nix/store/yss20s7yfn4rr359yhyv4pr515w44f2b-python3.10-inquirer-3.1.2

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

11 total rebuild path(s)

11 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.chalice
python310Packages.inquirer
python310Packages.strawberry-graphql
python310Packages.toggl-cli
python310Packages.translatepy
python311Packages.chalice
python311Packages.inquirer
python311Packages.strawberry-graphql
python311Packages.toggl-cli
python311Packages.translatepy
translatepy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/yss20s7yfn4rr359yhyv4pr515w44f2b-python3.10-inquirer-3.1.2 \
  --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 python310Packages.inquirer https://github.com/r-ryantm/nixpkgs/archive/112a1cffabce7afb9fed5da89a87a80f50854c24.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/yss20s7yfn4rr359yhyv4pr515w44f2b-python3.10-inquirer-3.1.2
ls -la /nix/store/yss20s7yfn4rr359yhyv4pr515w44f2b-python3.10-inquirer-3.1.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages failed to build:

python311Packages.chalice
python311Packages.strawberry-graphql
python311Packages.toggl-cli

7 packages built:

python310Packages.chalice
python310Packages.inquirer
python310Packages.strawberry-graphql
python310Packages.toggl-cli
translatepy (python310Packages.translatepy)
python311Packages.inquirer
python311Packages.translatepy

Maintainer pings
cc @mmahut for testing.

@ofborg build python311Packages.toggl-cli


dummy

To check whether #5149 worked...

INFO:	Deployment bundle does not include PodSecurityPolicies (PSPs).
INFO:	This is incompatible with pre-v1.25 Kubernetes installations having the PodSecurityPolicy Admission Controller plugin enabled.
INFO:	Use --enable-pod-security-policies if PodSecurityPolicies are required for your Kubernetes environment.

Looks good.


Support for Apple Silicon (aarch64)

The script bin/dockerized isn’t set up to be able to build for Apple Silicon. Modifying the architectures should probably include a detection for ~aarch64~ arm64, the arm64 / aarch64 target for GO.
https://github.com/datastack-net/dockerized/blob/master/bin/dockerized#L55-L63

diff --git c/bin/dockerized i/bin/dockerized
index aafa2b86b370..105ebd4f4764 100755
--- c/bin/dockerized
+++ i/bin/dockerized
@@ -59,7 +59,9 @@ x86_64)
 i*86)
   DOCKERIZED_COMPILE_GOARCH=386
   ;;
-
+arm64 | aarch64)
+  DOCKERIZED_COMPILE_GOARCH=arm64
+  ;;
 esac

 if [ "$DOCKERIZED_COMPILE" ] || [ ! -f "$DOCKERIZED_BINARY" ]; then

Hi, thank you for reporting! Would you mind to make a PR for your suggested change?
If it works on your system then I can just merge it right away. Not able to do it myself right now as I'm out.


Support logging to file

Let people configure logging to file (with rotation) instead of stdout/stderr.

assigned me

May I summit a PR and add log4j configuration for the project?

@spacewander Already submit  PR #214 , does anything else we need to do for supporting logging to file.


NIST data source clarification: DOIs "NBS.CS.eNNN-NN" are not all correct

The "NBS.CS.eNNN-NN" documents are not all correct.

DOI
Title

NBS.CS.e104-43
Warm-air furnaces equipped with vaporizing pot-type oil burners

NBS.CS.e106-43
Boys' pajamas (made from woven fabrics)

NBS.CS.e107-43
Commercial electric-refrigeration condensing units

NBS.CS.e119-45
Dial indicators (for linear measurements)

NBS.CS.e124-45
Master disks

NBS.CS.e15-43
Men's pajamas (made from woven fabrics) second edition

A "CS" standard means "Commercial Standard".
A "CS(E)" standard means "Commercial Standard (Emergency)". These were made during wartime.

The URLs are incorrect.
e.g.

Link from metadata: https://nvlpubs.nist.gov/nistpubs/Legacy/CS/cse104-43.pdf
Correct link https://nvlpubs.nist.gov/nistpubs/Legacy/CS/cs104-43.pdf

The "Emergency" status is more like a type of draft status.

Given that in MR style, "NIST SP(2PD) 1800-13B" is "NIST.SP.2PD.1800-13B", a "NBS.CS.eNNN-NN" document should probably be called "NBS.CS-E.NNN-NN".

We should fix these ourselves, for now.


Some improvements.

Aiii iaa!
In fact in your case, you must use == since it automatically converts the
LHS which is a string to an int [1]. Am I right to say that the LHS is a
string? At least it seems to me that year_format must return a string.
Thus, the alternative you'd have to write would be:
parseInt(year_format()) - year + 1 === 0
M.
[1] -
http://stackoverflow.com/questions/359494/which-equals-operator-vs-should-be-used-in-javascript-comparisons
On Thu, Nov 10, 2016 at 12:54 PM, A.Lukjanenkovs<EMAIL_ADDRESS>wrote:

@MrAlexDeluxe commented on this pull request.
In zeeguu/static/js/DIST-zeeguu_learner_graph_module.js
https://github.com/mircealungu/Zeeguu-API/pull/76:

+var month_names = ['Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'];
+var week_days = ['Mon', 'Tue', 'Wed', 'Thu', 'Fri', 'Sat', 'Sun'];
+
+var input_data;
+
+// function convert_day_of_week_from_sun_to_mon
+var convert_day_of_week_from_sun_to_mon = function (date) {

return (date.getDay() + 6) % 7;
+};

+function week_number(date) {

var result, week_count_in_displayed_interval;
var days_in_month = 31;

if ((year_format(date) - year + 1) == 0) {

I don't see a need to do that. For me it is more convenient to use "==" .
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mircealungu/Zeeguu-API/pull/76, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAcWh46lf1u72S_mDGoD2QCGx1Ky6KGwks5q8wXbgaJpZM4KtqMf
.


Closed typeclass doesn't work, but it works in Coq

Me and Catalin tried the following code but it fails with an error:
module Test

type is_ml : Type -> Type0 =
| ML_unit : is_ml unit
| ML_bool : is_ml bool
| ML_int : is_ml int
| ML_string : is_ml string
| ML_arrow : a:Type -> b:Type -> is_ml a -> is_ml b -> is_ml (a -> b)
// | ML_pair : a:Type -> b:Type -> is_ml a -> is_ml b -> is_ml (a & b)    // fails for this one too

Error:
(Error) Failed to solve universe inequalities for inductives

Are we doing something wrong or is it a bug?
The same thing works fine in Coq :
Inductive is_ml : Type -> Prop :=
| ML_unit : is_ml unit
| ML_nat : is_ml nat
| ML_pair : forall (a b:Type), is_ml a -> is_ml b -> is_ml (a*b).

This was tested on FStar branch master: 35343f0c1d235fb7b67fd73a4e4a9ee5b908bf4c (14 July)
Thank you!

This was just a misunderstanding from our side of how universes work. The only reason it worked in Coq is that we were using Prop, which is impredicative.


Validation warning for the valid resource.

The validation test for the AllergyIntolerance resource returns an incorrect warning related to the terminology.
For example, we can use this resource:
{
    "resourceType": "AllergyIntolerance",
    "id": "wasp",
    "meta": {
        "versionId": "1",
        "lastUpdated": "2024-03-06T15:30:47.422+00:00",
        "profile": [
            "http://hl7.org.au/fhir/core/StructureDefinition/au-core-allergyintolerance"
        ]
    },
    "clinicalStatus": {
        "coding": [
            {
                "system": "http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical",
                "code": "active",
                "display": "Active"
            }
        ]
    },
    "verificationStatus": {
        "coding": [
            {
                "system": "http://terminology.hl7.org/CodeSystem/allergyintolerance-verification",
                "code": "unconfirmed",
                "display": "Unconfirmed"
            }
        ]
    },
    "category": [
        "environment"
    ],
    "code": {
        "coding": [
            {
                "system": "http://snomed.info/sct",
                "code": "256440004",
                "display": "Wasp venom"
            }
        ]
    },
    "patient": {
        "reference": "Patient/dan-harry"
    },
    "recordedDate": "2023-09-05",
    "asserter": {
        "reference": "PractitionerRole/bobrester-bob-gp"
    },
    "reaction": [
        {
            "substance": {
                "coding": [
                    {
                        "system": "http://snomed.info/sct",
                        "code": "256440004",
                        "display": "Wasp venom"
                    }
                ]
            },
            "manifestation": [
                {
                    "coding": [
                        {
                            "system": "http://snomed.info/sct",
                            "code": "247472004",
                            "display": "Hives"
                        }
                    ]
                },
                {
                    "coding": [
                        {
                            "system": "http://snomed.info/sct",
                            "code": "418363000",
                            "display": "Itching of skin"
                        }
                    ]
                },
                {
                    "coding": [
                        {
                            "system": "http://snomed.info/sct",
                            "code": "76067001",
                            "display": "Sneezing"
                        }
                    ]
                }
            ]
        }
    ]
}

At the current time, the validator returns these problems related to the resource:

AllergyIntolerance/wasp: AllergyIntolerance.reaction[0].manifestation[0]: ValueSet https://healthterminologies.gov.au/fhir/ValueSet/clinical-finding-1 not found
AllergyIntolerance/wasp: AllergyIntolerance.reaction[0].manifestation[1]: ValueSet https://healthterminologies.gov.au/fhir/ValueSet/clinical-finding-1 not found
AllergyIntolerance/wasp: AllergyIntolerance.reaction[0].manifestation[2]: ValueSet https://healthterminologies.gov.au/fhir/ValueSet/clinical-finding-1 not found
AllergyIntolerance/wasp: AllergyIntolerance.reaction[0].substance: ValueSet https://healthterminologies.gov.au/fhir/ValueSet/adverse-reaction-agent-1 not found
AllergyIntolerance/wasp: AllergyIntolerance.code: ValueSet https://healthterminologies.gov.au/fhir/ValueSet/indicator-hypersensitivity-intolerance-to-substance-2 not found
AllergyIntolerance/wasp: AllergyIntolerance: Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation)

But if we check this code: 247472004 (which is used in the AllergyIntolerance.reaction[0].manifestation[0]), we will find it is correct because it exists in the SNOMED CT refset.
@StephThaoOng originally reported the issue.

There was an issue with an expired NCTS token/secret on the server which got fixed. Is this test still failing?

sue with an e

Hi @mjosborne1 I've just run the AllergyIntolerance 1.13.09 test again and the same validation warnings are still displayed.

These ValueSets are all present on the tx.dev server, but there are multiple active ValueSets with the same URL and different versions. Would thi pose a problem for the tests?
e.g.

Same warnings are returned on testing Using the FHIR Validator Locally with tx.dev, and on a AU Core 0.4.0-ci-build qa report.
This means it is likely a tx.dev issue or validator issue, and not due to Inferno.

Grahame will look at it...https://chat.fhir.org/#narrow/stream/179167-hapi/topic/External.20Terminology.20server

Grahame confirmed on Zulip that there's a bug in the validator code and it will be fixed in the next release.

Need to ensure that Inferno uses the latest FHIR validator.

The latest version of the FHIR Validator has now been released (6.3.11) with a fix for this issue.
I have confirmed via Validator CLI that it correctly uses tx.dev.hl7.org.au to validate valuesets
java -jar validator_cli.jar AllergyIntolerance.json -tx http://tx.dev.hl7.org.au/fhir/ -version 4.0 -txLog txLog.txt
Success: 0 errors, 1 warnings, 5 notes   Information @ AllergyIntolerance.code (line 32, col4): None of the codings provided are in the value set 'Indicator of Hypersensitivity or Intolerance to Substance' (https://healthterminologies.gov.au/fhir/ValueSet/indicator-hypersensitivity-intolerance-to-substance-2|2.1.0), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#256440004)   Information @ AllergyIntolerance.reaction[0].substance (line 50, col8): None of the codings provided are in the value set 'Adverse Reaction Agent' (https://healthterminologies.gov.au/fhir/ValueSet/adverse-reaction-agent-1|1.1.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#256440004)   Information @ AllergyIntolerance.reaction[0].manifestation[0] (line 60, col10): None of the codings provided are in the value set 'Clinical Finding' (https://healthterminologies.gov.au/fhir/ValueSet/clinical-finding-1|1.0.2), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#247472004)   Information @ AllergyIntolerance.reaction[0].manifestation[1] (line 69, col10): None of the codings provided are in the value set 'Clinical Finding' (https://healthterminologies.gov.au/fhir/ValueSet/clinical-finding-1|1.0.2), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#418363000)   Information @ AllergyIntolerance.reaction[0].manifestation[2] (line 78, col10): None of the codings provided are in the value set 'Clinical Finding' (https://healthterminologies.gov.au/fhir/ValueSet/clinical-finding-1|1.0.2), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#76067001)   Warning @ AllergyIntolerance (line 1, col2): Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation)

@StephThaoOng Hello Steph
I asked the Inferno team about the validator, and they informed me that it's not just a simple configuration change. However, we know how to fix it, and it will be resolved.

It may be a problem related to caching the first validation result.
Details are available in the email from July 15th.


[Snyk] Security upgrade node from 8-alpine to 20.1-alpine

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR

Dockerfile

We recommend upgrading to node:20.1-alpine, as this image has only 6 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:

Severity
Priority Score / 1000
Issue
Exploit Maturity

714
Out-of-bounds Read SNYK-ALPINE311-APKTOOLS-1534687
No Known Exploit

614
Integer Overflow or Wraparound SNYK-ALPINE311-OPENSSL-1075738
No Known Exploit

714
Buffer Overflow SNYK-ALPINE311-OPENSSL-1569451
No Known Exploit

714
Buffer Overflow SNYK-ALPINE311-OPENSSL-1569451
No Known Exploit

714
Out-of-bounds Write SNYK-ALPINE311-ZLIB-2977081
No Known Exploit

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

fix


Store multiple cluster configs in kube-spawn-dir

Right now all the configs related to a set of machines that form our cluster go into <kube-spawn-dir>/default.
Once the config refactoring for #137 is finished we want to be able to namespace them by a cluster name/identifier.

We can provide a flag like --cluster-name=. If this is unset we should put everything under default like right now.

Resolved with #161


Sc large txns

Committing very large graphs to amber will now batch the marshaling of graph elements (vertices and edges and their properties) to prevent the object creation involved with marshaling from using too much memory.
It also slightly improves the speed of committing in many cases through the creation of indexes on the session tables which get used by queries during commit, and modification to the queries themselves to ensure the indexes get used.
The big commit threshold has been set to 50000 vertices+edges. This is somewhat arbitrary and just based on past experience of where commits have failed due to running out of memory. I don't think it's necessary to make it configurable (yet).
You can call the commitBig method explicitly (ie: it's public) but the existing commit methods will automatically use it if the threshold conditions are met.
I updated the snapshot version due to the significance of the change - rolling back from it could cause processes that rely on this feature to fail.

I haven't committed tests for this feature, as they do take a very long time to actually test the cases where it is useful. It has been tested for 190000 elements (which have 1000000+ properties altogether) in an otherwise empty jvm. I recognise that this is a pretty artificial case, and normally alot more would be going on.

This looks really handy.  Looking over the changes now

Awesome from the first impression, just wondering whether it's a good idea to have checkpoints also for such large transactions to swiftly recover from runtime disruption.

Cheers for the feedback Shuang. The checkpoint idea is good too, but for sake of simplicity I won't do that yet - the complexity of figuring out where to recover from is too much for me at the moment :-) It already does do some backoff retries if the writing to the actual amberdb tables fails, and if the writing to session tables fails it's simpler just to redo them as it won't pollute the real graph tables (although admittedly it could leave a bunch of useless entries in the session tables)


remove usage of copytree from distutils

Description

This PR fixes the issue arising from the newer version of setuptools==75.0.0.
Removes the usage of distutils copy_tree.
GitHub Issues

https://github.com/zappa/Zappa/issues/1349

@monkut @souravjamwal77 can you have a look at this?
Let me know if anything else needs to be done.

@monkut @souravjamwal77 can you have a look at this?
Let me know if anything else needs to be done.

You may need to tag it with "needs review", been a minute since I have contributed though. Since this bug is breaking folks CI/CD seems like a pretty important PR to merge.

coverage: 74.648% (-0.02%) from 74.668%
when pulling 71d834a60a4af8e62d2795f17093798af66914b0 on sridhar562345:master
into 39f75e76d28c1a08d4de6501e6f794fe988cbc98 on zappa:master.


Images table DnD: header stuck in the "dnd" state

https://user-images.githubusercontent.com/3659196/190881374-b774fe63-5ec7-4c37-9b6f-6a9e6dc38dd3.mov
I would also expect for ESC to cancel the operation and return everything into its initial state

If this is what I think, it might not be super easy to fix. I looked into it for half a day and gave up because it seemed like a bug inside the drag and drop API itself and would only happen 1/3 of the time. I'll look into it soon, and even if it is what I think I might have a solution.


storage: Missing res.Body.Close

For unknown reasons we encounter a lot of objects with unparseable content length headers.
The problem is that there seems to be a memory leak due to a missing res.Body.Close() in the cloud/storage package.
Please see https://github.com/GoogleCloudPlatform/google-cloud-go/blob/master/storage/storage.go#L548. IMHO there should be also a res.Body.Close() as with the previous error returns in the same method.

For unknown reasons we encounter a lot of objects with unparseable content length headers.

What's the error message you get? Is it an empty string in there ("") or some non-decimal value?

IMHO there should be also a res.Body.Close() as with the previous error returns in the same method.

Looks like it. But I'm more concerned about the error in the first place.
/cc @jba

The error returned by NewReader is storage: can't parse content length "": strconv.ParseInt: parsing "": invalid syntax.
I just realized that we may be requesting non-existing objects, but in that case I'd expect an storage.ErrObjectNotExist and not a strconv.ParseInt failure. I'll try to verify if we indeed request invalid objects and comment if I find something interesting.

If it's a 404, we already returned storage.ErrObjectNotExist up above that line. That error message is only returned on a 2xx response. I'm not sure which 2xx response would not have a X-Goog-Stored-Content-Length response header. I suppose we need to talk to the GCS folk and figure that out.

I've sent out a fix to the unclosed-body, but I agree with @bradfitz that we should only encounter an error like that in exceptional circumstances. I'm chasing up with the GCS team.

For finding the full size, I think we should be using the response Content-Range header instead.

https://code-review.googlesource.com/7850

@dominikschulz, do you have any details of which objects get that error? For a given object, do you see it sometimes work and sometimes not, or is it only for certain objects?
What's your caller code look like? Are you using ObjectHandle.NewRangeReader? Or only ObjectHandle.NewReader?

The caller code is using ObjectHandle.NewReader as we're only interested in complete objects.
So far I haven't been able to get any details on the failing objects, and I can't give an ETA due to personal circumstances, but if I find something I'll report back to this issue.


README: Fix typo, markdownlint, punctuation, backticks and steps

This PR is made of 3 step-wise (yet simple) commits, with slightly detailed commit messages:

Fix typo and markdownlint issues in VSCode.
Fix punctuation and few missing backticks.
Make the build steps a numbered steps list.

Signed-off-by: Marco Miller<EMAIL_ADDRESS>

Not an eclipse project... yet. I'm designating Marco to be a committer.


fix(mediacontrol): fix getSettings method (fix iOS fullscreen button)

Fixes #1410.

Coverage remained the same at 71.966% when pulling f3e189617ead196f116fda1818b72a85d3af0102 on kslimani:fix-ios-fullscreen-btn into e4c82cb44b4289e851ba15a73a836c7ae6ba70ee on clappr:master.


Further improvement of the diagnostic select_variables_for_tigramite.py

Currently, the diagnostic diag_scripts/galytska23/select_variables_for_tigramite.py calculates variables related to Arctic-midlatitude teleconnections (based on  Galytska et al., 2023) and saves the output in .nc files and provides the optional plotting.
I am searching the guidance on how to improve the script in case more variables are added to the recipe (or a totally different recipe calls this diagnostic) and make the script "more flexible" to those changes.
The general purpose of the script is to pre-process the data, which is later read into Tigramite https://github.com/jakobrunge/tigramite

@egalytska I've not forgotten about this, and my apologies for dragging my feet - I promise I'll find a bit of time look at it start next week 🍺

hi @egalytska - good news (or bad, depending how you look at it :laughing: ) - I have started on the slight refactoring of your diag here https://github.com/ESMValGroup/ESMValTool/pull/3298 - please hop over there, when you got time :beer: